RFC 9261: Exported Authenticators in TLS
In plain English — editorial summary, not part of the RFC
This document describes a mechanism that builds on Transport Layer Security (TLS) or Datagram Transport Layer Security (DTLS) and enables peers to provide proof of ownership of an identity, such as an X.509 certificate. This proof can be exported by one peer, transmitted out of band to the other peer, and verified by the receiving peer.
Document record
- Document ID
- RFC9261
- Published
- July 2022
- Authors
- N. Sullivan
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 14
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9258Importing External Pre-Shared Keys (PSKs) for TLS 1.3Current
July 2022
- RFC 9257Guidance for External Pre-Shared Key (PSK) Usage in TLSCurrent
July 2022
- RFC 9266Channel Bindings for TLS 1.3Current
July 2022
- RFC 9278JWK Thumbprint URICurrent
August 2022
- RFC 9244Distributed Denial-of-Service Open Threat Signaling (DOTS) TelemetryCurrent
June 2022
- RFC 9242Intermediate Exchange in the Internet Key Exchange Protocol Version 2 (IKEv2)Current
May 2022
- RFC 9284Multihoming Deployment Considerations for DDoS Open Threat Signaling (DOTS)Current
August 2022
- RFC 9237An Authorization Information Format (AIF) for Authentication and Authorization for Constrained Environments (ACE)Current
August 2022
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?