Use Cases and Requirements for Web Packages
draft-yasskin-wpack-use-cases-01

Document Type Active Internet-Draft (individual)
Author Jeffrey Yasskin 
Last updated 2020-07-27
Replaces draft-yasskin-webpackage-use-cases
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: Informational                              27 July 2020
Expires: 28 January 2021

              Use Cases and Requirements for Web Packages
                    draft-yasskin-wpack-use-cases-01

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
   (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 (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.

Copyright Notice

   Copyright (c) 2020 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Yasskin                  Expires 28 January 2021                [Page 1]
Internet-Draft Use Cases and Requirements for Web Packages     July 2020

   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
   2.  Use cases . . . . . . . . . . . . . . . . . . . . . . . . . .   4
     2.1.  Essential . . . . . . . . . . . . . . . . . . . . . . . .   4
       2.1.1.  Offline installation  . . . . . . . . . . . . . . . .   4
       2.1.2.  Offline browsing  . . . . . . . . . . . . . . . . . .   6
       2.1.3.  Save and share a web page . . . . . . . . . . . . . .   6
       2.1.4.  Privacy-preserving prefetch . . . . . . . . . . . . .   7
     2.2.  Nice-to-have  . . . . . . . . . . . . . . . . . . . . . .   7
       2.2.1.  Packaged Web Publications . . . . . . . . . . . . . .   8
       2.2.2.  Avoiding Censorship . . . . . . . . . . . . . . . . .   9
       2.2.3.  Third-party security review . . . . . . . . . . . . .   9
       2.2.4.  Building packages from multiple libraries . . . . . .  10
       2.2.5.  Cross-CDN Serving . . . . . . . . . . . . . . . . . .  10
       2.2.6.  Pre-installed applications  . . . . . . . . . . . . .  11
       2.2.7.  Protecting Users from a Compromised Frontend  . . . .  12
       2.2.8.  Installation from a self-extracting executable  . . .  13
       2.2.9.  Packages in version control . . . . . . . . . . . . .  13
       2.2.10. Subresource bundling  . . . . . . . . . . . . . . . .  13
       2.2.11. Archival  . . . . . . . . . . . . . . . . . . . . . .  14
   3.  Requirements  . . . . . . . . . . . . . . . . . . . . . . . .  15
     3.1.  Essential . . . . . . . . . . . . . . . . . . . . . . . .  15
       3.1.1.  Indexed by URL  . . . . . . . . . . . . . . . . . . .  15
       3.1.2.  Request headers . . . . . . . . . . . . . . . . . . .  15
       3.1.3.  Response headers  . . . . . . . . . . . . . . . . . .  15
       3.1.4.  Signing as an origin  . . . . . . . . . . . . . . . .  15
       3.1.5.  Random access . . . . . . . . . . . . . . . . . . . .  16
       3.1.6.  Resources from multiple origins in a package  . . . .  16
       3.1.7.  Cryptographic agility . . . . . . . . . . . . . . . .  16
       3.1.8.  Unsigned content  . . . . . . . . . . . . . . . . . .  16
       3.1.9.  Certificate revocation  . . . . . . . . . . . . . . .  16
       3.1.10. Downgrade prevention  . . . . . . . . . . . . . . . .  16
       3.1.11. Metadata  . . . . . . . . . . . . . . . . . . . . . .  17
       3.1.12. Implementations are hard to get wrong . . . . . . . .  17
     3.2.  Nice to have  . . . . . . . . . . . . . . . . . . . . . .  17
       3.2.1.  Streamed loading  . . . . . . . . . . . . . . . . . .  17
Show full document text