Web Packaging
draft-yasskin-dispatch-web-packaging-00
| Document | Type | Replaced Internet-Draft (individual) | |
|---|---|---|---|
| Author | Jeffrey Yasskin | ||
| Last updated | 2018-01-01 (latest revision 2017-06-30) | ||
| Replaced by | draft-yasskin-http-origin-signed-responses, draft-yasskin-wpack-bundled-exchanges | ||
| Stream | (None) | ||
| Intended RFC status | (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 | Replaced by draft-yasskin-http-origin-signed-responses, draft-yasskin-wpack-bundled-exchanges | |
| Telechat date | |||
| Responsible AD | (None) | ||
| Send notices to | (None) | ||
This Internet-Draft is no longer active. A copy of
the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-yasskin-dispatch-web-packaging-00.txt
https://www.ietf.org/archive/id/draft-yasskin-dispatch-web-packaging-00.txt
Abstract
Web Packages provide a way to bundle up groups of web resources to transmit them together. These bundles can then be signed to establish their authenticity.
Authors
Jeffrey Yasskin (jyasskin@chromium.org)
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)