RFC 9525: Service Identity in TLS
In plain English — editorial summary, not part of the RFC
Many application technologies enable secure communication between two entities by means of Transport Layer Security (TLS) with Internet Public Key Infrastructure using X.509 (PKIX) certificates. This document specifies procedures for representing and verifying the identity of application services in such interactions. This document obsoletes RFC 6125.
Document record
- Document ID
- RFC9525
- Published
- November 2023
- Authors
- P. Saint-Andre; R. Salz
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 25
- Also known as
- —
- Obsoletes:
- RFC 6125
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9528Ephemeral Diffie-Hellman Over COSE (EDHOC)Current
March 2024
- RFC 9529Traces of Ephemeral Diffie-Hellman Over COSE (EDHOC)Current
March 2024
- RFC 9540Discovery of Oblivious Services via Service Binding RecordsCurrent
February 2024
- RFC 9509X.509 Certificate Extended Key Usage (EKU) for 5G Network FunctionsCurrent
March 2024
- RFC 9549Internationalization Updates to RFC 5280Current
March 2024
- RFC 9495Certification Authority Authorization (CAA) Processing for Email AddressesCurrent
October 2023
- RFC 9493Subject Identifiers for Security Event TokensCurrent
December 2023
- RFC 9483Lightweight Certificate Management Protocol (CMP) ProfileCurrent
November 2023
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?