|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 5911 (2010)
|
|
Title:
|
New ASN.1 Modules for Cryptographic Message Syntax (CMS) and S/MIME
|
|
|
2.
|
Status of approval:
|
|
|
June 2010 as Informational.
|
|
3.
|
Justification for the specific reference:
|
|
|
Rec. ITU-T X.pbact references IETF RFC 5911 for using the new ASN.1 modules for CMS.
|
|
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=5911
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Approved in June 2010 as Informational.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
IETF RFC 5911 is updated by RFC 6268; four Errata are available.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Not known.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative References/
[ASN1-2002] ITU-T, "ITU-T Recommendation X.680, X.681, X.682, and X.683", ITU-T X.680, X.681, X.682, and X.683, 2002./
[RFC3370] Housley, R., "Cryptographic Message Syntax (CMS) Algorithms", RFC 3370, August 2002./
[RFC3565] Schaad, J., "Use of the Advanced Encryption Standard (AES) Encryption Algorithm in Cryptographic Message Syntax (CMS)", RFC 3565, July 2003./
[RFC3851] Ramsdell, B., "Secure/Multipurpose Internet Mail Extensions (S/MIME) Version 3.1 Message Specification", RFC 3851, July 2004./
[RFC3852] Housley, R., "Cryptographic Message Syntax (CMS)", RFC 3852, July 2004./
[RFC4108] Housley, R., "Using Cryptographic Message Syntax (CMS) to Protect Firmware Packages", RFC 4108, August 2005./
[RFC4998] Gondrom, T., Brandner, R., and U. Pordesch, "Evidence Record Syntax (ERS)", RFC 4998, August 2007./
[RFC5035] Schaad, J., "Enhanced Security Services (ESS) Update: Adding CertID Algorithm Agility", RFC 5035, August 2007./
[RFC5083] Housley, R., "Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content Type", RFC 5083, November 2007./
[RFC5084] Housley, R., "Using AES-CCM and AES-GCM Authenticated Encryption in the Cryptographic Message Syntax (CMS)", RFC 5084, November 2007./
[RFC5275] Turner, S., "CMS Symmetric Key Management and Distribution", RFC 5275, June 2008./
[RFC5652] Housley, R., "Cryptographic Message Syntax (CMS)", RFC 5652, September 2009./
[RFC5912] Hoffman, P. and J. Schaad, "New ASN.1 Modules for the Public Key Infrastructure using X.509 (PKIX)", RFC 5912, June 2010.
|
|
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.
|
|
