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

Document Type Active Internet-Draft (individual)
Last updated 2018-06-14
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         J. Yasskin
Internet-Draft                                                    Google
Intended status: Standards Track                           June 14, 2018
Expires: December 16, 2018

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

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.

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 December 16, 2018.

Yasskin                 Expires December 16, 2018               [Page 1]
Internet-Draft            Signed HTTP Exchanges                June 2018

Copyright Notice

   Copyright (c) 2018 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  . . . . . . . . . . . . . . . . . .   5
       3.1.1.  Examples  . . . . . . . . . . . . . . . . . . . . . .   6
       3.1.2.  Open Questions  . . . . . . . . . . . . . . . . . . .   8
     3.2.  CBOR representation of exchange headers . . . . . . . . .   8
       3.2.1.  Example . . . . . . . . . . . . . . . . . . . . . . .   9
     3.3.  Loading a certificate chain . . . . . . . . . . . . . . .  10
     3.4.  Canonical CBOR serialization  . . . . . . . . . . . . . .  11
     3.5.  Signature validity  . . . . . . . . . . . . . . . . . . .  12
       3.5.1.  Open Questions  . . . . . . . . . . . . . . . . . . .  15
     3.6.  Updating signature validity . . . . . . . . . . . . . . .  15
       3.6.1.  Examples  . . . . . . . . . . . . . . . . . . . . . .  16
     3.7.  The Accept-Signature header . . . . . . . . . . . . . . .  18
       3.7.1.  Integrity identifiers . . . . . . . . . . . . . . . .  19
       3.7.2.  Key type identifiers  . . . . . . . . . . . . . . . .  19
       3.7.3.  Key value identifiers . . . . . . . . . . . . . . . .  19
       3.7.4.  Examples  . . . . . . . . . . . . . . . . . . . . . .  20
       3.7.5.  Open Questions  . . . . . . . . . . . . . . . . . . .  20
   4.  Cross-origin trust  . . . . . . . . . . . . . . . . . . . . .  21
     4.1.  Stateful header fields  . . . . . . . . . . . . . . . . .  22
     4.2.  Certificate Requirements  . . . . . . . . . . . . . . . .  23
   5.  Transferring a signed exchange  . . . . . . . . . . . . . . .  24
     5.1.  Same-origin response  . . . . . . . . . . . . . . . . . .  24
       5.1.1.  Significant headers for a same-origin response  . . .  24
       5.1.2.  The Signed-Headers Header . . . . . . . . . . . . . .  25
     5.2.  HTTP/2 extension for cross-origin Server Push . . . . . .  26
       5.2.1.  Indicating support for cross-origin Server Push . . .  26
       5.2.2.  NO_TRUSTED_EXCHANGE_SIGNATURE error code  . . . . . .  26
Show full document text