Use Cases and Requirements for Web Packages
draft-yasskin-webpackage-use-cases-01
| The information below is for an old version of the document | |||
|---|---|---|---|
| Document | Type | Expired Internet-Draft (individual) | |
| Author | Jeffrey Yasskin | ||
| Last updated | 2018-09-06 (latest revision 2018-03-05) | ||
| Replaced by | draft-yasskin-wpack-use-cases | ||
| Stream | (None) | ||
| Formats |
Expired & archived
pdf
htmlized (tools)
htmlized
bibtex
|
||
| Stream | Stream state | (No stream defined) | |
| Consensus Boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
https://www.ietf.org/archive/id/draft-yasskin-webpackage-use-cases-01.txt
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 [1]. The source code and issues list for this draft can be found in https://github.com/WICG/webpackage [2].
Authors
Jeffrey Yasskin (jyasskin@chromium.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)