Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification
RFC 3851

Note: This ballot was opened for revision 09 and is now closed.

(Russ Housley) Yes

(Harald Alvestrand) (was Discuss) No Objection

Comment (2004-05-13)
No email
send info
Formatting problem: No index. I cast a DISCUSS at first, because I couldn't find section 1.5, which describes changes since RFC 2633.....

No reference to RFC 2633.

No security considerations section (there is a section named "Security", however).

Reviewed by Michael Patton, Gen-ART

(Steven Bellovin) No Objection

Comment (2004-05-12)
No email
send info
Is it worth mentioning the need for good sources of randomness when doing DSA signatures?  It seems more appropriate for the CMS standard, but I'd think the same would apply to much of 4.1.

(Bill Fenner) No Objection

(Ted Hardie) No Objection

(Scott Hollenbeck) No Objection

(David Kessens) No Objection

(Allison Mankin) No Objection

(Thomas Narten) (was Discuss) No Objection

(Jon Peterson) No Objection

(Bert Wijnen) No Objection

Comment (2004-05-13)
No email
send info
$ idnits-v1.24 <drafts/draft-ietf-smime-rfc2633bis-09.txt
idnits 1.24, 16 Apr 2004, 07:05

  The document seems to lack an Authors' Addresses Section
  The document seems to use RFC 2026 boilerplate...
  The document seems to lack an 2026 Section 10.4(C) Copyright Notice
  The document seems to lack an RFC 2026 Section 10.4(C) Permission Grants Notice
  The document seems to lack an RFC 2026 Section 10.4(C) Disclaimer

  Warnings:
    The document seems to lack an RFC 2026 Section 10.4(A) Disclaimer
    The document seems to lack an RFC 2026 Section 10.4(B) IPR Disclosure Invitation

(Alex Zinin) No Objection