|
1.
|
Clear description of the referenced document:
|
|
|
|
Name:
|
IETF RFC 9525
|
|
Title:
|
RFC 9525: Service Identity in TLS, IETF, November 2023
|
|
|
2.
|
Status of approval:
|
|
|
RFC 9525 was published as an IETF Proposed Standard in November 2023. It obsoletes RFC 6125. Finalized IETF document.
|
|
3.
|
Justification for the specific reference:
|
|
|
RFC 9525 defines procedures for verifying the identity of a TLS server by checking its certificate against the expected service identity (hostname validation). X.f2sp Section 7.2.1 contains a shall requirement: "shall perform a TLS server certificate check, as per [RFC9525]." This is a fundamental security requirement for all connections made by clients, authorization servers, and resource servers. Incorporation of the full text is inappropriate as only the certificate identity verification procedure is referenced. Freely available. No ITU-T or ISO/IEC equivalent.
|
|
4.
|
Current information, if any, about IPR issues:
|
|
|
No known patent claims. Freely available.
|
|
5.
|
Other useful information describing the "Quality" of the document:
|
|
|
Published November 2023 (obsoletes RFC 6125, published 2011). Universally applicable to all TLS implementations. Freely available at https://www.rfc-editor.org/rfc/rfc9525.
|
|
6.
|
The degree of stability or maturity of the document:
|
|
|
Stable, finalized IETF Proposed Standard. Most recent version of TLS service identity specification, having replaced RFC 6125.
|
|
7.
|
Relationship with other existing or emerging documents:
|
|
|
Applies to all TLS-based communications. Referenced in TLS security profiles across multiple SDOs. No ITU-T/ISO/IEC equivalent (ITU-T X.509 covers certificates but not TLS hostname validation procedures).
|
|
8.
|
Any explicit references within that referenced document should also be listed:
|
|
|
Normative references within RFC 9525: RFC 2119, RFC 4949, RFC 5280, RFC 6570, RFC 8174, RFC 8446. All IETF documents; IETF is qualified under Annex B.
|
|
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):
|
|
|
|
