|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
Draft Rec. X.cso refers to S/MIME Version 2 Message Specification, IETF RFC 2311, March 1998.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/. Specifically: https://datatracker.ietf.org/ipr/search/?option=rfc_search&rfc_search=2311
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Proposed Standard
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Proposed Standard
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item (8).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[3DES] W. Tuchman, "Hellman Presents No Shortcut Solutions To DES,"/
IEEE Spectrum, v. 16, n. 7, July 1979, pp40-41./
/
[CHARSETS] Character sets assigned by IANA. See/
ftp://ftp.isi.edu/in-notes/iana/assignments/character-sets./
/
[CONTDISP] Troost, R., Dorner, S and K. Moore, "Communicating/
Presentation Information in Internet Messages: The Content-/
Disposition Header Field", RFC 2183, August 1997./
/
[DES] ANSI X3.106, "American National Standard for Information/
Systems-Data Link Encryption," American National Standards Institute,/
1983./
/
[MD5] Rivest, R., "The MD5 Message Digest Algorithm", RFC 1321, April/
1992./
/
[MIME-SPEC] The primary definition of MIME./
/
Freed, N., and N. Borenstein, "MIME Part 1: Format of Internet/
Message Bodies", RFC 2045, November 1996./
/
Freed, N., and N. Borenstein, "MIME Part 2: Media Types", RFC 2046,/
November 1996./
/
Moore, K., "MIME Part 3: Message Header Extensions for Non-ASCII/
Text", RFC 2047, November 1996./
/
Freed, N., Klensin, J., and J. Postel, "MIME Part 4: Registration/
Procedures", RFC 2048, November 1996./
/
Freed, N., and N. Borenstein, "MIME Part 5: Conformance Criteria and/
Examples", RFC 2049, November 1996./
/
[MIME-SECURE] Galvin, J., Murphy, S., Crocker, S., and N. Freed,/
"Security Multiparts for MIME: Multipart/Signed and/
Multipart/Encrypted", RFC 1847, October 1995./
/
[MUSTSHOULD] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[PKCS-1] Kaliski, B., "PKCS #1: RSA Encryption Version 1.5", RFC/
2313, March 1998./
/
[PKCS-7] Kaliski, B., "PKCS #7: Cryptographic Message Syntax Version/
1.5", RFC 2315, March 1998./
/
[PKCS-10] Kaliski, B., "PKCS #10: Certification Request Syntax/
Version 1.5", RFC 2314, March 1998./
/
[RC2] Rivest, R., "Description of the RC2(r) Encryption Algorithm",/
RFC 2268, January 1998./
/
[SHA1] NIST FIPS PUB 180-1, "Secure Hash Standard," National/
Institute of Standards and Technology, U.S. Department of Commerce,/
DRAFT, 31 May 1994./
|
|
9.
|
Qualification of
ISOC/IETF:
|
|
|
9.1-9.6 Decisions of ITU Council to admit ISOC to participate in the work of the Sector (June 1995 and June 1996).
9.7 The Internet Engineering Steering Group (IESG) is responsible for ongoing maintenance of the RFCs when the need arises. Comments on RFCs and corresponding changes are accommodated through the existing standardization process.
9.8 Each revision of a given RFC has a different RFC number, so no confusion is possible. All RFCs always remain available on-line. An index of RFCs and their status may be found in the IETF archives at http://www.rfc-editor.org/rfc.html.
|
|
10.
|
Other (for any supplementary information):
|
|
|
None
|
|
