draft-yasskin-http-origin-signed-responses-07

Light Dark Auto draft-yasskin-http-origin-signed-responses-07 Internet-Draft Title Signed HTTP Exchanges Document Document type This is an older version of an Internet-Draft whose latest revision state is "Expired". This document is an Internet-Draft (I-D). Anyone may submit an I-D to the IETF. This I-D is not endorsed by the IETF and has no formal standing in the IETF standards process. Select version 00 01 02 03 04 05 06 07 08 09 Compare versions draft-yasskin-http-origin-signed-responses-09 draft-yasskin-http-origin-signed-responses-08 draft-yasskin-http-origin-signed-responses-07 draft-yasskin-http-origin-signed-responses-06 draft-yasskin-http-origin-signed-responses-05 draft-yasskin-http-origin-signed-responses-04 draft-yasskin-http-origin-signed-responses-03 draft-yasskin-http-origin-signed-responses-02 draft-yasskin-http-origin-signed-responses-01 draft-yasskin-http-origin-signed-responses-00 draft-yasskin-dispatch-web-packaging-00 draft-yasskin-http-origin-signed-responses-09 draft-yasskin-http-origin-signed-responses-08 draft-yasskin-http-origin-signed-responses-07 draft-yasskin-http-origin-signed-responses-06 draft-yasskin-http-origin-signed-responses-05 draft-yasskin-http-origin-signed-responses-04 draft-yasskin-http-origin-signed-responses-03 draft-yasskin-http-origin-signed-responses-02 draft-yasskin-http-origin-signed-responses-01 draft-yasskin-http-origin-signed-responses-00 draft-yasskin-dispatch-web-packaging-00 Side-by-side Inline Author Jeffrey Yasskin Replaces draft-yasskin-dispatch-web-packaging RFC stream (None) Other formats txt xml bibtex bibxml Report a bug Network Working Group J. Yasskin Internet-Draft Google Intended status: Standards Track September 26, 2019 Expires: March 29, 2020 Signed HTTP Exchanges draft-yasskin-http-origin-signed-responses-07 Abstract This document specifies how a server can send an HTTP exchange--a request URL, content negotiation information, and a response--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. Note to Readers Discussion of this draft takes place on the HTTP working group mailing list (ietf-http-wg@w3.org), which is archived at https://lists.w3.org/Archives/Public/ietf-http-wg/ [1]. The source code and issues list for this draft can be found in https://github.com/WICG/webpackage [2]. Status of This Memo This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79. Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet- Drafts is at https://datatracker.ietf.org/drafts/current/. Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress." This Internet-Draft will expire on March 29, 2020. Yasskin Expires March 29, 2020 [Page 1] Internet-Draft Signed HTTP Exchanges September 2019 Copyright Notice Copyright (c) 2019 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 4 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 3. Signing an exchange . . . . . . . . . . . . . . . . . . . . . 5 3.1. The Signature Header . . . . . . . . . . . . . . . . . . 6 3.1.1. Examples . . . . . . . . . . . . . . . . . . . . . . 7 3.1.2. Open Questions . . . . . . . . . . . . . . . . . . . 9 3.2. CBOR representation of exchange response headers . . . . 9 3.2.1. Example . . . . . . . . . . . . . . . . . . . . . . . 10 3.3. Loading a certificate chain . . . . . . . . . . . . . . . 10 3.4. Canonical CBOR serialization . . . . . . . . . . . . . . 11 3.5. Signature validity . . . . . . . . . . . . . . . . . . . 12 3.5.1. Open Questions . . . . . . . . . . . . . . . . . . . 16 3.6. Updating signature validity . . . . . . . . . . . . . . . 16 3.6.1. Examples . . . . . . . . . . . . . . . . . . . . . . 17 3.7. The Accept-Signature header . . . . . . . . . . . . . . . 19 3.7.1. Integrity identifiers . . . . . . . . . . . . . . . . 20 3.7.2. Key type identifiers . . . . . . . . . . . . . . . . 20 3.7.3. Key value identifiers . . . . . . . . . . . . . . . . 20 3.7.4. Examples . . . . . . . . . . . . . . . . . . . . . . 21 3.7.5. Open Questions . . . . . . . . . . . . . . . . . . . 21 4. Cross-origin trust . . . . . . . . . . . . . . . . . . . . . 22 4.1. Uncached header fields . . . . . . . . . . . . . . . . . 23 4.1.1. Stateful header fields . . . . . . . . . . . . . . . 24 4.2. Certificate Requirements . . . . . . . . . . . . . . . . 25 4.2.1. Extensions to the CAA Record: cansignhttpexchanges Parameter . . . . . . . . . . . . . . . . . . . . . . 26 5. Transferring a signed exchange . . . . . . . . . . . . . . . 26 5.1. Same-origin response . . . . . . . . . . . . . . . . . . 26 5.1.1. Serialized headers for a same-origin response . . . . 27 5.1.2. The Signed-Headers Header . . . . . .