|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 5912 (2010)
|
|
Title:
|
New ASN.1 Modules for the Public Key Infrastructure Using X.509 (PKIX)
|
|
|
2.
|
Status of approval:
|
|
|
June 2010 as Informational.
|
|
3.
|
Justification for the specific reference:
|
|
|
X.CMS-prof uses the ASN.1 definitions of IETF RFC 5912
|
|
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=6268
|
|
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 6268 updates ASN.1 definitions of previous RFCs
|
|
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./
/
[RFC2560] Myers, M., Ankney, R., Malpani, A., Galperin, S., and C./
Adams, "X.509 Internet Public Key Infrastructure Online/
Certificate Status Protocol - OCSP", RFC 2560,/
June 1999./
/
[RFC2986] Nystrom, M. and B. Kaliski, "PKCS #10: Certification/
Request Syntax Specification Version 1.7", RFC 2986,/
November 2000./
/
[RFC3279] Bassham, L., Polk, W., and R. Housley, "Algorithms and/
Identifiers for the Internet X.509 Public Key/
Infrastructure Certificate and Certificate Revocation/
List (CRL) Profile", RFC 3279, April 2002./
/
[RFC3852] Housley, R., "Cryptographic Message Syntax (CMS)",/
RFC 3852, July 2004./
/
[RFC4055] Schaad, J., Kaliski, B., and R. Housley, "Additional/
Algorithms and Identifiers for RSA Cryptography for use/
in the Internet X.509 Public Key Infrastructure/
Certificate and Certificate Revocation List (CRL)/
Profile", RFC 4055, June 2005./
/
[RFC4210] Adams, C., Farrell, S., Kause, T., and T. Mononen,/
"Internet X.509 Public Key Infrastructure Certificate/
Management Protocol (CMP)", RFC 4210, September 2005./
/
[RFC4211] Schaad, J., "Internet X.509 Public Key Infrastructure/
Certificate Request Message Format (CRMF)", RFC 4211,/
September 2005./
/
[RFC5055] Freeman, T., Housley, R., Malpani, A., Cooper, D., and/
W. Polk, "Server-Based Certificate Validation Protocol/
(SCVP)", RFC 5055, December 2007./
/
[RFC5272] Schaad, J. and M. Myers, "Certificate Management over/
CMS (CMC)", RFC 5272, June 2008./
/
[RFC5280] Cooper, D., Santesson, S., Farrell, S., Boeyen, S.,/
Housley, R., and W. Polk, "Internet X.509 Public Key/
Infrastructure Certificate and Certificate Revocation/
List (CRL) Profile", RFC 5280, May 2008./
[RFC5480] Turner, S., Brown, D., Yiu, K., Housley, R., and T./
Polk, "Elliptic Curve Cryptography Subject Public Key/
Information", RFC 5480, March 2009./
/
[RFC5755] Farrell, S., Housley, R., and S. Turner, "An Internet/
Attribute Certificate Profile for Authorization",/
RFC 5755, January 2010./
/
[RFC5911] Hoffman, P. and J. Schaad, "New ASN.1 Modules for/
Cryptographic Message Syntax (CMS) and S/MIME",/
RFC 5911, 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.
|
|
