Draft: draft-ietf-lamps-rfc5751-bis

Commentary: This is the problem that the examples are not real examples
S/MIME version 4.0 agents ought to attempt to have the greatest
interoperability possible with agents for prior versions of S/MIME.
S/MIME version 2 is described in RFC 2311 through RFC 2315 inclusive
SMIMEv2, S/MIME version 3 is described in RFC 2630 through RFC 2634
inclusive and RFC 5035 SMIMEv3, S/MIME version 3.1 is described in
RFC 3850, RFC 3851, RFC 3852, RFC 2634, and RFC 5035 SMIMEv3.1, and
S/MIME version 3.2 is described in SMIMEv3.2.  RFC 2311 also has
historical information about the development of S/MIME.
S/MIME version 4.0 agents ought to attempt to have the greatest
interoperability possible with agents for prior versions of S/MIME.
S/MIME version 2 is described in RFC 2311 through RFC 2315 inclusive
SMIMEv2, S/MIME version 3 is described in RFC 2630 through RFC 2634
inclusive and RFC 5035 SMIMEv3, S/MIME version 3.1 is described in
RFC 3850, RFC 3851, RFC 3852, RFC 2634, and RFC 5035 SMIMEv3.1, and
S/MIME version 3.2 is described in SMIMEv3.2.  RFC2311 also has
historical information about the development of S/MIME.
Section 7 : Moved references from HistoricMail to this section.
Updated references.  Added informational references to SMIMEv2,
SMIMEv3, and SMIMEv3.1.
V2Historic: Added Appendix B to move S/MIME v2 to Historic status.
Section 7: Moved references from HistoricMail to this section.
Updated references.  Added informational references to SMIMEv2,
SMIMEv3, and SMIMEv3.1.
V2Historic: Added V2Historic to move S/MIME v2 to Historic status.
Update the content encryption algorithms
(ContentEncryptionAlgorithmIdentifier): Add AES-256 GCM , remove
AES-192 CBC, mark tripleDES as historic.
Create Appendix B which deals with considerations for dealing with
historic email messages.
Update the content encryption algorithms
(ContentEncryptionAlgorithmIdentifier and UnknownCaps): Add
AES-256 GCM, add ChaCha200-Poly1305, remove AES-192 CBC, mark
tripleDES as historic.
Update the set of digest algorithms (DigestAlgorithmIdentifier:
Add SHA-512, mark SHA-1 as historic.
Update the size of keys to be used for RSA encryption and RSA
signing (CertProcessing).
Create HistoricMail which deals with considerations for dealing
with historic email messages.
Both ECDSA and EdDSA are included in the list of required algorithms
for political reasons.  NIST is unable to provide the seeds that were
used to create their standardized curves, this means that there is a
section of the community which believes that there might be a
backdoor to these curves.  The EdDSA curves were created in response
to this feeling.  However, there are still significant sections of
the industry which need to have NIST approved algorithms.  For this
reason, both sets of curves are represented in the recieving agent
list, but there is only a requirement for curve in the sending agent
list.
Both ECDSA and EdDSA are included in the list of required algorithms
for political reasons.  NIST is unable to provide the seeds that were
used to create their standardized curves, this means that there is a
section of the community which believes that there might be a
backdoor to these curves.  The EdDSA curves were, in part, created in
response to this feeling.  However, there are still significant
sections of the industry which need to have NIST approved algorithms.
For this reason, both sets of curves are represented in the recieving
agent list, but there is only a requirement for curve in the sending
agent list.
A registry for additional smime-type parameter values has been
defined in RFC7114.