|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 5083 (2007)
|
|
Title:
|
Cryptographic Message Syntax (CMS) Authenticated-Enveloped-Data Content Type
|
|
|
2.
|
Status of approval:
|
|
|
November 2007 as Proposed Standard.
|
|
3.
|
Justification for the specific reference:
|
|
|
Rec. ITU-T X.pbact references IETF RFC 5083 to use additional specifications for the Cryptographic message syntax (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=5083
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Approved in November 2007 as Proposed Standard.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
IETF RFC 5083 updates RFC 3852. There are no errata 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/
[CMS] Housley, R., "Cryptographic Message Syntax (CMS)", RFC 3852, July 2004./
[STDWORDS] Bradner, S., "Key words for use in RFCs to Indicate Requirement Levels", BCP 14, RFC 2119, March 1997./
[X.208-88] CCITT. Recommendation X.208: Specification of Abstract Syntax Notation One (ASN.1). 1988./
[X.209-88] CCITT. Recommendation X.209: Specification of Basic Encoding Rules for Abstract Syntax Notation One (ASN.1). 1988./
[X.509-88] CCITT. Recommendation X.509: The Directory-Authentication Framework. 1988./
/
Informative References/
[AESALGS] Housley, R., "Using AES-CCM and AES-GCM Authenticated Encryption in the Cryptographic Message Syntax (CMS)", RFC 5084, November 2007./
[BDJR] Bellare, M., Desai, A., Jokipii, E., and P. Rogaway, "A Concrete Security Treatment of Symmetric Encryption: Analysis of the DES Modes of Operation", Proceedings38th Annual Symposium on Foundations of Computer Science, 1997./
[RANDOM] Eastlake, D., 3rd, Schiller, J., and S. Crocker, "Randomness Requirements for Security", BCP 106, RFC 4086, June 2005.
|
|
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.
|
