|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 6125 (2011)
|
|
Title:
|
Representation and Verification of Domain-Based Application Service
Identity within Internet Public Key Infrastructure Using X.509 (PKIX)
Certificates in the Context of Transport Layer Security (TLS)
|
|
|
2.
|
Status of approval:
|
|
|
Proposed Standard
|
|
3.
|
Justification for the specific reference:
|
|
|
This recommendation uses PKIX as defined in the reference
|
|
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:
|
|
|
Standards track RFC approved March 2011. Proposed Standard
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Standards track RFC approved March 2011.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
References within the referenced RFCs are listed under item (8). Obsoletes RFC 3921.
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
[DNS-CONCEPTS] Mockapetris, P., "Domain names - concepts and/
facilities", STD 13, RFC 1034, November 1987./
/
[DNS-SRV] Gulbrandsen, A., Vixie, P., and L. Esibov, "A DNS RR/
for specifying the location of services (DNS SRV)",/
RFC 2782, February 2000./
/
[IDNA-DEFS] Klensin, J., "Internationalized Domain Names for/
Applications (IDNA): Definitions and Document/
Framework", RFC 5890, August 2010./
/
[IDNA-PROTO] Klensin, J., "Internationalized Domain Names in/
Applications (IDNA): Protocol", RFC 5891,/
August 2010./
/
[KEYWORDS] Bradner, S., "Key words for use in RFCs to Indicate/
Requirement Levels", BCP 14, RFC 2119, March 1997./
/
[LDAP-DN] Zeilenga, K., Ed., "Lightweight Directory Access/
Protocol (LDAP): String Representation of/
Distinguished Names", RFC 4514, June 2006./
/
[PKIX] 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./
/
[SRVNAME] Santesson, S., "Internet X.509 Public Key/
Infrastructure Subject Alternative Name for/
Expression of Service Name", RFC 4985, August 2007./
/
[URI] Berners-Lee, T., Fielding, R., and L. Masinter,/
"Uniform Resource Identifier (URI): Generic Syntax",/
STD 66, RFC 3986, January 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.
|
|
