RFC 6125: 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)
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 9525.
Current version: 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 Internet Public Key Infrastructure Using X.509 (PKIX) certificates in the context of Transport Layer Security (TLS). This document specifies procedures for representing and verifying the identity of application services in such interactions. [STANDARDS-TRACK]
Document record
- Document ID
- RFC6125
- Published
- March 2011
- Authors
- P. Saint-Andre; J. Hodges
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- —
- Pages
- 57
- Also known as
- —
- Obsoleted by:
- RFC 9525
Referenced by
One later RFC formally updates or obsoletes part of this document.
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?