RFC 8472: Transport Layer Security (TLS) Extension for Token Binding Protocol Negotiation
In plain English — editorial summary, not part of the RFC
This document specifies a Transport Layer Security (TLS) extension for the negotiation of Token Binding protocol version and key parameters. Negotiation of Token Binding in TLS 1.3 and later versions is beyond the scope of this document.
Document record
- Document ID
- RFC8472
- Published
- October 2018
- Authors
- A. Popov; M. Nystroem; D. Balfanz
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- sec
- Pages
- 8
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8471The Token Binding Protocol Version 1.0Current
October 2018
- RFC 8473Token Binding over HTTPCurrent
October 2018
- RFC 8470Using Early Data in HTTPCurrent
September 2018
- RFC 8449Record Size Limit Extension for TLSCurrent
August 2018
- RFC 8701Applying Generate Random Extensions And Sustain Extensibility (GREASE) to TLS ExtensibilityCurrent
January 2020
- RFC 8940Extensible Authentication Protocol (EAP) Session-Id Derivation for EAP Subscriber Identity Module (EAP-SIM), EAP Authentication and Key Agreement (EAP-AKA), and Protected EAP (PEAP)Current
October 2020
- RFC 8996Deprecating TLS 1.0 and TLS 1.1Current
March 2021
- RFC 7919Negotiated Finite Field Diffie-Hellman Ephemeral Parameters for Transport Layer Security (TLS)Current
August 2016
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?