|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 2510 (2001)
|
|
Title:
|
Internet X.509 Public Key Infrastructure Certificate Management Protocols, April 2001.
|
|
|
2.
|
Status of approval:
|
|
|
The referred RFCs were approved by IESG (Internet Engineering Steering Group).
|
|
3.
|
Justification for the specific reference:
|
|
|
10 Draft Rec. X.cso refers to Internet X.509 Public Key Infrastructure Certificate Management Protocols, IETF RFC 2510, April 2001.
|
|
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=2510
|
|
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:
|
|
|
[COR95] ISO/IEC JTC 1/SC 21, Technical Corrigendum 2 to ISO/IEC/
9594-8: 1990 & 1993 (1995:E), July 1995./
/
[CRMF] Myers, M., Adams, C., Solo, D. and D. Kemp, "Certificate/
Request Message Format", RFC 2511, March 1999./
/
[MvOV97] A. Menezes, P. van Oorschot, S. Vanstone, "Handbook of/
Applied Cryptography", CRC Press, 1997./
/
[PKCS7] RSA Laboratories, "The Public-Key Cryptography Standards/
(PKCS)", RSA Data Security Inc., Redwood City, California,/
November 1993 Release./
/
[PKCS10] RSA Laboratories, "The Public-Key Cryptography Standards/
(PKCS)", RSA Data Security Inc., Redwood City, California,/
November 1993 Release./
/
[PKCS11] RSA Laboratories, "The Public-Key Cryptography Standards -/
PKCS #11: Cryptographic token interface standard", RSA/
Data Security Inc., Redwood City, California, April 28,/
1995./
/
[RFC1847] Galvin, J., Murphy, S. Crocker, S. and N. Freed, "Security/
Multiparts for MIME: Multipart/Signed and Multipart//
Encrypted", RFC 1847, October 1995./
/
[RFC2104] Krawczyk, H., Bellare, M. and R. Canetti, "HMAC: Keyed/
Hashing for Message Authentication", RFC 2104, February/
1997./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2202] Cheng, P. and R. Glenn, "Test Cases for HMAC-MD5 and HMAC-/
SHA-1", RFC 2202, September 1997./
/
[X509-AM] ISO/IEC JTC1/SC 21, Draft Amendments DAM 4 to ISO/IEC/
9594-2, DAM 2 to ISO/IEC 9594-6, DAM 1 to ISO/IEC 9594-7,/
and DAM 1 to ISO/IEC 9594-8 on Certificate Extensions, 1/
December, 1996./
|
|
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
|
|
