FYI...
The feedback from the IETF Meeting yesterday, on the AS#1 were:
-Make consistent throughout the reference to md5 and/or sha1 according
to new recommendations (sha1)
-Examples. Move all examples to Appendix of the requirements document.
Replace examples with a way to describe which RFC's and drafts go into
each scenario (like on the slide shown).
-Keep receipts example, because here we are actually recommending new
use.
-Take down to a bare minimum, any descriptions of S/MIME or PGP/MIME
that can be found in the referenced docs.
-2.3.2 - Clarify the request for receipt vs. signed receipt
-S/MIME: Use Multipat/signed instead of application/x-pkcs7-mime etc...
(1847 based. Makes S/MIME and PGP/MIME consistent)
These changes will be made as soon as possible, although I am on vacation
starting NOW. I'll work out with Chuck what can be done when.
Regards,
Mats
_____________________________________________________________
Mats Jansson, LiNK mjansson@agathon.com
2317 Broadway, Suite 330
Redwood City, CA 94063 v: +1-415-780-9039
http://www.agathon.com f: +1-415-780-9069
This archive was generated by hypermail 2.1.2 : Tue Jun 05 2001 - 22:37:48 EEST