Use Cases and Requirements for Web Packages
draft-yasskin-webpackage-use-cases-00

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Author Jeffrey Yasskin 
Last updated 2017-08-30
Replaced by draft-yasskin-wpack-use-cases
Stream (None)
Formats 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)
dispatch                                                      J. Yasskin
Internet-Draft                                                    Google
Intended status: Informational                           August 30, 2017
Expires: March 3, 2018

              Use Cases and Requirements for Web Packages
                 draft-yasskin-webpackage-use-cases-00

Abstract

   This document lists use cases for signing and/or bundling collections
   of web pages, and extracts a set of requirements from them.

Note to Readers

   Discussion of this draft takes place on the ART area mailing list
   (art@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/search/?email_list=art.

   The source code and issues list for this draft can be found in
   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 http://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 3, 2018.

Copyright Notice

   Copyright (c) 2017 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
   (http://trustee.ietf.org/license-info) in effect on the date of

Yasskin                   Expires March 3, 2018                 [Page 1]
Internet-Draft Use Cases and Requirements for Web Packages   August 2017

   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
   2.  Use cases . . . . . . . . . . . . . . . . . . . . . . . . . .   3
     2.1.  Essential . . . . . . . . . . . . . . . . . . . . . . . .   3
       2.1.1.  Offline installation  . . . . . . . . . . . . . . . .   3
       2.1.2.  Offline browsing  . . . . . . . . . . . . . . . . . .   5
       2.1.3.  Save and share a web page . . . . . . . . . . . . . .   5
     2.2.  Nice-to-have  . . . . . . . . . . . . . . . . . . . . . .   6
       2.2.1.  Packaged Web Publications . . . . . . . . . . . . . .   6
       2.2.2.  Third-party security review . . . . . . . . . . . . .   7
       2.2.3.  Building packages from multiple libraries . . . . . .   7
       2.2.4.  CDNs  . . . . . . . . . . . . . . . . . . . . . . . .   8
       2.2.5.  Installation from a self-extracting executable  . . .   8
       2.2.6.  Ergonomic replacement for HTTP/2 PUSH . . . . . . . .   9
       2.2.7.  Packages in version control . . . . . . . . . . . . .   9
   3.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .   9
     3.1.  Essential . . . . . . . . . . . . . . . . . . . . . . . .  10
       3.1.1.  Indexed by URL  . . . . . . . . . . . . . . . . . . .  10
       3.1.2.  Request headers . . . . . . . . . . . . . . . . . . .  10
       3.1.3.  Response headers  . . . . . . . . . . . . . . . . . .  10
       3.1.4.  Signing as an origin  . . . . . . . . . . . . . . . .  10
       3.1.5.  Random access . . . . . . . . . . . . . . . . . . . .  11
       3.1.6.  Resources from multiple origins in a package  . . . .  11
       3.1.7.  Cryptographic agility . . . . . . . . . . . . . . . .  11
       3.1.8.  Unsigned content  . . . . . . . . . . . . . . . . . .  11
       3.1.9.  Certificate revocation  . . . . . . . . . . . . . . .  11
       3.1.10. Downgrade prevention  . . . . . . . . . . . . . . . .  11
       3.1.11. Metadata  . . . . . . . . . . . . . . . . . . . . . .  11
       3.1.12. Implementations are hard to get wrong . . . . . . . .  12
     3.2.  Nice to have  . . . . . . . . . . . . . . . . . . . . . .  12
       3.2.1.  Streamed loading  . . . . . . . . . . . . . . . . . .  12
       3.2.2.  Cross-signatures  . . . . . . . . . . . . . . . . . .  12
       3.2.3.  Binary  . . . . . . . . . . . . . . . . . . . . . . .  12
       3.2.4.  Deduplication of diamond dependencies . . . . . . . .  12
       3.2.5.  Old crypto can be removed . . . . . . . . . . . . . .  12
       3.2.6.  Compress transfers  . . . . . . . . . . . . . . . . .  13
       3.2.7.  Compress stored packages  . . . . . . . . . . . . . .  13
Show full document text