|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 5280 (2008)
|
|
Title:
|
Internet X.509 Public Key Infrastructure Certificate and Certificate Revocation List (CRL) Profile.
|
|
|
2.
|
Status of approval:
|
|
|
Approved
|
|
3.
|
Justification for the specific reference:
|
|
|
This recommendation uses PKI as defined in the reference for authentication and verification of certificates.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
Information on IPR issues regarding document is available at: https://datatracker.ietf.org/ipr/search/.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Proposed Standard
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Widely used
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Updated by RFC 9549, RFC 9598, RFC 8398, RFC 8399, RFC 6818, RFC 9608, RFC 9618
Obsoletes RFC 4630, RFC 4325, RFC 3280
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
11.1. Normative References/
/
[RFC791] Postel, J., "Internet Protocol", STD 5, RFC 791, September/
1981./
/
[RFC1034] Mockapetris, P., "Domain Names - Concepts and Facilities",/
STD 13, RFC 1034, November 1987./
/
[RFC1123] Braden, R., Ed., "Requirements for Internet Hosts --/
Application and Support", STD 3, RFC 1123, October 1989./
/
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[RFC2460] Deering, S. and R. Hinden, "Internet Protocol, Version 6/
(IPv6) Specification", RFC 2460, December 1998./
/
[RFC2585] Housley, R. and P. Hoffman, "Internet X.509 Public Key/
Infrastructure: Operational Protocols: FTP and HTTP", RFC/
2585, May 1999./
/
Cooper, et al. Standards Track [Page 105]/
RFC 5280 PKIX Certificate and CRL Profile May 2008/
/
[RFC2616] Fielding, R., Gettys, J., Mogul, J., Frystyk, H.,/
Masinter, L., Leach, P., and T. Berners-Lee, "Hypertext/
Transfer Protocol -- HTTP/1.1", RFC 2616, June 1999./
/
[RFC2797] Myers, M., Liu, X., Schaad, J., and J. Weinstein,/
"Certificate Management Messages over CMS", RFC 2797,/
April 2000./
/
[RFC2821] Klensin, J., Ed., "Simple Mail Transfer Protocol", RFC/
2821, April 2001./
/
[RFC3454] Hoffman, P. and M. Blanchet, "Preparation of/
Internationalized Strings ("stringprep")", RFC 3454,/
December 2002./
/
[RFC3490] Faltstrom, P., Hoffman, P., and A. Costello,/
"Internationalizing Domain Names in Applications (IDNA)",/
RFC 3490, March 2003./
/
[RFC3629] Yergeau, F., "UTF-8, a transformation format of ISO/
10646", STD 63, RFC 3629, November 2003./
/
[RFC3986] Berners-Lee, T., Fielding, R., and L. Masinter, "Uniform/
Resource Identifier (URI): Generic Syntax", STD 66, RFC/
3986, January 2005./
/
[RFC3987] Duerst, M. and M. Suignard, "Internationalized Resource/
Identifiers (IRIs)", RFC 3987, January 2005./
/
[RFC4516] Smith, M., Ed., and T. Howes, "Lightweight Directory/
Access Protocol (LDAP): Uniform Resource Locator", RFC/
4516, June 2006./
/
[RFC4518] Zeilenga, K., "Lightweight Directory Access Protocol/
(LDAP): Internationalized String Preparation", RFC 4518,/
June 2006./
/
[RFC4523] Zeilenga, K., "Lightweight Directory Access Protocol/
(LDAP) Schema Definitions for X.509 Certificates", RFC/
4523, June 2006./
/
[RFC4632] Fuller, V. and T. Li, "Classless Inter-domain Routing/
(CIDR): The Internet Address Assignment and Aggregation/
Plan", BCP 122, RFC 4632, August 2006./
/
[X.680] ITU-T Recommendation X.680 (2002) | ISO/IEC 8824-1:2002,/
Information technology - Abstract Syntax Notation One/
(ASN.1): Specification of basic notation./
/
Cooper, et al. Standards Track [Page 106]/
RFC 5280 PKIX Certificate and CRL Profile May 2008/
/
[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).
|
|
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
|
|
