Token Binding for 0-RTT TLS 1.3 Connections
draft-nharper-0-rtt-token-binding-02

Document Type Replaced Internet-Draft (individual)
Last updated 2016-11-13
Replaced by draft-ietf-tokbind-tls13-0rtt
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Replaced by draft-ietf-tokbind-tls13-0rtt
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
https://www.ietf.org/archive/id/draft-nharper-0-rtt-token-binding-02.txt

Abstract

This document describes how Token Binding can be used in the 0-RTT data of a TLS 1.3 connection. This involves updating how Token Binding negotiation works and adding a mechanism for indicating whether a server prevents replay. A TokenBindingMessage sent in 0-RTT data has different security properties than one sent after the TLS handshake has finished, which this document also describes.

Authors

Nick Harper (nharper@google.com)

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