The Token Binding Protocol Version 1.0

Document Type Replaced Internet-Draft (tokbind WG)
Authors Andrei Popov  , Magnus Nystrom  , Dirk Balfanz  , Adam Langley 
Last updated 2015-10-14 (latest revision 2014-10-13)
Replaced by RFC 8471
Stream Internet Engineering Task Force (IETF)
Intended RFC status (None)
Expired & archived
plain text xml pdf htmlized bibtex
Stream WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG IESG state Replaced by draft-ietf-tokbind-protocol
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at


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 [RFC5246] 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 TLS Token Binding identifiers are only transmitted encrypted and can be reset by the user at any time.


Andrei Popov (
Magnus Nystrom (
Dirk Balfanz (
Adam Langley (

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)