Signed HTTP Exchanges
draft-yasskin-http-origin-signed-responses-04

Document Type Expired Internet-Draft (individual)
Last updated 2018-12-16 (latest revision 2018-06-14)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html 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-yasskin-http-origin-signed-responses-04.txt

Abstract

This document specifies how a server can send an HTTP request/ response pair, known as an exchange, with signatures that vouch for that exchange's authenticity. These signatures can be verified against an origin's certificate to establish that the exchange is authoritative for an origin even if it was transferred over a connection that isn't. The signatures can also be used in other ways described in the appendices. These signatures contain countermeasures against downgrade and protocol-confusion attacks.

Authors

Jeffrey Yasskin (jyasskin@chromium.org)

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