Attested TLS Token Binding
draft-mandyam-tokbind-attest-07

Document Type Expired Internet-Draft (individual)
Last updated 2019-07-28 (latest revision 2019-01-24)
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 Expired
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-mandyam-tokbind-attest-07.txt

Abstract

Token binding allows HTTP servers to bind bearer tokens to TLS connections. In order to do this, clients or user agents must prove possession of a private key. However, proof-of-possession of a private key becomes truly meaningful to a server when accompanied by an attestation statement. This specification describes extensions to the existing token binding protocol to allow for attestation statements to be sent along with the related token binding messages.

Authors

Giridhar Mandyam (mandyam@qti.qualcomm.com)
Laurence Lundblade (lgl@island-resort.com)
Jon Azen (jazen@qti.qualcomm.com)

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