I have a few comments.
TECHNICAL
The references are obsolete. The normative references are:
[CMS] Cryptographic Message Syntax, RFC 2630.
[PKIX] PKIX Certificate and CRL Profile, RFC 2459.
[SMIME-MSG] S/MIME Version 3 Message Specification. RFC 2633.
A new version of each of these documents has been published as a
standards-track RFC.
Please delete the following paragraphs from the Introduction prior to
submission to the IESG:
This draft is being discussed on the 'ietf-smime-examples' mailing list.
To join the list, send a message to
ietf-smime-examples-request(_at_)imc(_dot_)org
with the single word "subscribe" in the body of the message. Also,
there is a Web site for the mailing list at
<http://www.imc.org/ietf-smime-examples/>. Note that S/MIME itself is
discussed in the IETF's S/MIME Working Group; see
<http://www.imc.org/ietf-smime/> for more information.
To contribute an implementation of an unimplemented example listed in
this document, to verify that you got the same results as an example
listed here, or to suggest a new example that should be listed, please
contact the document author at the address listed near the end of the
document.
EDITORIAL
Section 1 says:
The examples shown here were created and validated by many different
people over a long period of time.
This seems like a good place to say something about the dates used in the
examples. I see no need to generate new examples will more recent dates;
however, the implementor should be warned about the dates used in the
examples. The certificates have very long lifespans to avoid having to
play with clock settings.
In section 2: s/in this spec./in this document./
Russ