Web Bundles
draft-yasskin-wpack-bundled-exchanges-03

Document Type Active Internet-Draft (individual)
Author Jeffrey Yasskin 
Last updated 2020-07-27
Replaces draft-yasskin-dispatch-web-packaging
Stream (None)
Intended RFC status (None)
Formats plain text html xml pdf htmlized (tools) htmlized 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                            27 July 2020
Expires: 28 January 2021

                              Web Bundles
                draft-yasskin-wpack-bundled-exchanges-03

Abstract

   Web bundles provide a way to bundle up groups of HTTP responses, with
   the URLs and request URLs that produced them, to transmit or store
   them together.  They can include multiple top-level resources with
   one identified as the default by a primaryUrl metadata, provide
   random access to their component exchanges, and efficiently store
   8-bit resources.

Note to Readers

   Discussion of this draft takes place on the wpack mailing list
   (wpack@ietf.org), which is archived at
   https://www.ietf.org/mailman/listinfo/wpack
   (https://www.ietf.org/mailman/listinfo/wpack).

   The source code and issues list for this draft can be found in
   https://github.com/WICG/webpackage (https://github.com/WICG/
   webpackage).

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 28 January 2021.

Yasskin                  Expires 28 January 2021                [Page 1]
Internet-Draft                 Web Bundles                     July 2020

Copyright Notice

   Copyright (c) 2020 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  . . . . . . . . . . . . . . . . . . . . . . . .   3
     1.1.  Terminology . . . . . . . . . . . . . . . . . . . . . . .   3
     1.2.  Mode of specification . . . . . . . . . . . . . . . . . .   3
   2.  Semantics . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Stream attributes and operations  . . . . . . . . . . . .   4
     2.2.  Load a bundle's metadata  . . . . . . . . . . . . . . . .   4
       2.2.1.  Load a bundle's metadata from the end . . . . . . . .   5
     2.3.  Load a response from a bundle . . . . . . . . . . . . . .   5
   3.  Format  . . . . . . . . . . . . . . . . . . . . . . . . . . .   6
     3.1.  Top-level structure . . . . . . . . . . . . . . . . . . .   6
     3.2.  Serving constraints . . . . . . . . . . . . . . . . . . .   7
     3.3.  Load a bundle's metadata  . . . . . . . . . . . . . . . .   7
       3.3.1.  Parsing the index section . . . . . . . . . . . . . .  10
       3.3.2.  Parsing the manifest section  . . . . . . . . . . . .  13
       3.3.3.  Parsing the signatures section  . . . . . . . . . . .  13
       3.3.4.  Parsing the critical section  . . . . . . . . . . . .  15
       3.3.5.  The responses section . . . . . . . . . . . . . . . .  15
       3.3.6.  Starting from the end . . . . . . . . . . . . . . . .  15
     3.4.  Load a response from a bundle . . . . . . . . . . . . . .  16
     3.5.  Parsing CBOR items  . . . . . . . . . . . . . . . . . . .  18
       3.5.1.  Parse a known-length item . . . . . . . . . . . . . .  18
       3.5.2.  Parsing variable-length data from a bytestring  . . .  19
       3.5.3.  Parsing the type and argument of a CBOR item  . . . .  19
     3.6.  Interpreting CBOR HTTP headers  . . . . . . . . . . . . .  20
   4.  Guidelines for bundle authors . . . . . . . . . . . . . . . .  21
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .  21
     5.1.  Version skew  . . . . . . . . . . . . . . . . . . . . . .  21
     5.2.  Content sniffing  . . . . . . . . . . . . . . . . . . . .  21
   6.  IANA considerations . . . . . . . . . . . . . . . . . . . . .  23
     6.1.  Internet Media Type Registration  . . . . . . . . . . . .  23
     6.2.  Web Bundle Section Name Registry  . . . . . . . . . . . .  24
   7.  References  . . . . . . . . . . . . . . . . . . . . . . . . .  25
Show full document text