The Token Binding Protocol Version 1.0
RFC 8471
Revision differences
Document history
| Date | By | Action |
|---|---|---|
|
2026-05-20
|
(System) | Changed metadata: changed keywords to '['Token', 'cookie', 'TLS', 'export', 'replay']' from '[]' |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2026-05-20
|
(System) | Changed author "J. Hodges": changed name from "Jeff Hodges" to "J. Hodges", changed affiliation from "PayPal" to "Kings Mountain Systems", cleared country (was "USA") |
|
2026-05-20
|
(System) | Changed author "D. Balfanz": changed name from "Dirk Balfanz" to "D. Balfanz", cleared country (was "USA"), changed order from "2" to "3" |
|
2026-05-20
|
(System) | Changed author "M. Nystroem": changed name from "Magnus Nyström" to "M. Nystroem", cleared country (was "USA"), changed order from "1" to "2" |
|
2026-05-20
|
(System) | Changed author "A. Popov": changed name from "Andrei Popov" to "A. Popov", changed is_editor from "False" to "True", cleared country (was "USA"), changed order from … Changed author "A. Popov": changed name from "Andrei Popov" to "A. Popov", changed is_editor from "False" to "True", cleared country (was "USA"), changed order from "0" to "1" |
|
2026-05-20
|
(System) | Metadata update from RFC Editor |
|
2018-10-11
|
(System) | IANA registries were updated to include RFC8471 |
|
2018-10-08
|
(System) | Received changes through RFC Editor sync (created alias RFC 8471, changed abstract to 'This document specifies version 1.0 of the Token Binding protocol. The … Received changes through RFC Editor sync (created alias RFC 8471, changed abstract to 'This document specifies version 1.0 of the Token Binding protocol. The Token Binding protocol allows client/server applications to create long-lived, uniquely identifiable TLS bindings spanning multiple TLS sessions and connections. Applications are then enabled to cryptographically bind security tokens to the TLS layer, preventing token export and replay attacks. To protect privacy, the Token Binding identifiers are only conveyed over TLS and can be reset by the user at any time.', changed standardization level to Proposed Standard, changed state to RFC, added RFC published event at 2018-10-08, changed IESG state to RFC Published) |
|
2018-10-08
|
(System) | RFC published |