|
1.
|
Clear description of the referenced document:
|
|
|
|
|
2.
|
Status of approval:
|
|
|
August 2010 as Internet Standard
|
|
3.
|
Justification for the specific reference:
|
|
|
Key data structure specified in this document (x.ibc-iot) uses the EncryptedData structure specified in IETF 5958
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding RFCs is available at: https://datatracker.ietf.org/ipr/search/.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Approved in August 2010 as standard.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
IETF RFC 5958 obsoletes RFC 5208; 1 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/
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC4648] Josefsson, S., "The Base16, Base32, and Base64 Data/
Encodings", RFC 4648, October 2006./
/
[RFC5652] Housley, R., "Cryptographic Message Syntax (CMS)", STD/
70, RFC 5652, September 2009./
/
[RFC5911] Hoffman, P. and J. Schaad, "New ASN.1 Modules for/
Cryptographic Message Syntax (CMS) and S/MIME", RFC 5911,/
June 2010./
/
[RFC5912] Hoffman, P. and J. Schaad, "New ASN.1 Modules for the/
Public Key Infrastructure Using X.509 (PKIX)", RFC 5912,/
June 2010./
/
[X.680] ITU-T Recommendation X.680 (2002) | ISO/IEC 8824-1:2002./
Information Technology - Abstract Syntax Notation One./
/
[X.681] ITU-T Recommendation X.681 (2002) | ISO/IEC 8824-2:2002./
Information Technology - Abstract Syntax Notation One:/
Information Object Specification./
/
[X.682] ITU-T Recommendation X.682 (2002) | ISO/IEC 8824-3:2002./
Information Technology - Abstract Syntax Notation One:/
Constraint Specification./
/
[X.683] ITU-T Recommendation X.683 (2002) | ISO/IEC 8824-4:2002./
Information Technology - Abstract Syntax Notation One:/
Parameterization of ASN.1 Specifications./
/
[X.690] ITU-T Recommendation X.690 (2002) | ISO/IEC 8825-1:2002./
Information Technology - ASN.1 encoding rules:/
Specification of Basic Encoding Rules (BER), Canonical/
Encoding Rules (CER) and Distinguished Encoding Rules/
(DER)./
/
Informative References/
/
[P12] RSA Laboratories, "PKCS #12 v1.0: Personal Information/
Exchange Syntax", June 1999./
/
[RFC2985] Nystrom, M. and B. Kaliski, "PKCS #9: Selected Object/
Classes and Attribute Types Version 2.0", RFC 2985,/
November 2000./
/
[RFC3447] Jonsson, J. and B. Kaliski, "Public-Key Cryptography/
Standards (PKCS) #1: RSA Cryptography Specifications/
Version 2.1", RFC 3447, February 2003./
/
[RFC5083] Housley, R., "Cryptographic Message Syntax (CMS)/
Authenticated-Enveloped-Data Content Type", RFC 5083,/
November 2007./
/
[RFC5208] Kaliski, B., "Public-Key Cryptography Standards (PKCS)/
#8: Private-Key Information Syntax Specification Version/
1.2", RFC 5208, May 2008./
/
[X.520] ITU-T Recommendation X.520 (2005) | ISO/IEC 9594-6:2005,/
Information technology - Open Systems Interconnection -/
The Directory: Selected attribute types./
/
[RFC5915] Turner, S. and D. Brown, "Elliptic Curve Private Key/
Structure", RFC 5915, 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.
|
|
