Web Bundles
draft-yasskin-wpack-bundled-exchanges-03
| Document | Type |
This is an older version of an Internet-Draft whose latest revision state is "Replaced".
Expired & archived
|
|
|---|---|---|---|
| Author | Jeffrey Yasskin | ||
| Last updated | 2021-01-28 (Latest revision 2020-07-27) | ||
| Replaces | draft-yasskin-dispatch-web-packaging | ||
| Replaced by | draft-ietf-wpack-bundled-responses | ||
| RFC stream | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
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.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)