Re: A least a draft now exists for trust anchor key rollover requirements.
This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed
> Perhaps it is not an ideal situation that a requirements document
> is authored by the promoter of an alternative in the solution space.
> In this perspective, you are kindly invited to bring forward a
> better set of TAK requirement statements, and/or suggestions to
> improve the above one.[/color]
Thanks for your contribution but I would prefer if we could leave
this document shelved just a little while.
We have assigned editors to produce a requirement document for the
working group and I am still confident that they will deliver, albeit
the delay. At this moment we as a working group should not raise the
amount of entropy by having multiple requirement documents floating
around. On the other hand I see that you, and others (myself
included) are anxious to see output.
I propose that we wait for the assigned editors to produce. If the
editors fail to produce before the cutt-off we will have to use your
document as the basis for further discussion. I am not saying that
your contribution is out of scope for this group, by no means. But
I'd prefer if we could focus on just one document, that of the
I share frustration about the speed of this process and except for
the Vixie Beer Fund there are very few ways we can force/motivate
people to do work. On the other hand I do think a good set of
requirements is important so that we can then continue with selection
of the appropriate technology. Those technologies all seem pretty
Olaf M. Kolkman
content-type: application/pgp-signature; x-mac-type=70674453;
content-description: This is a digitally signed message part
content-disposition: inline; filename=PGP.sig
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (Darwin)
Comment: This message is locally signed.
-----END PGP SIGNATURE-----
to unsubscribe send a message to [email]email@example.com[/email] with
the word 'unsubscribe' in a single line as the message text body.