Attested TLS Token Binding
draft-mandyam-tokbind-attest-07
| Document | Type | Expired Internet-Draft (individual) | |
|---|---|---|---|
| Authors | Giridhar Mandyam , Laurence Lundblade , Jon Azen | ||
| Last updated | 2019-07-28 (Latest revision 2019-01-24) | ||
| Stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats |
Expired & archived
plain text
xml
pdf
htmlized
pdfized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
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
Laurence Lundblade
Jon Azen
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)