Web Bundles
draft-yasskin-wpack-bundled-exchanges-04
Document | Type |
Replaced Internet-Draft
(candidate for wpack WG)
Expired & archived
|
|
---|---|---|---|
Author | Jeffrey Yasskin | ||
Last updated | 2021-03-15 (Latest revision 2021-03-07) | ||
Replaces | draft-yasskin-dispatch-web-packaging | ||
Replaced by | draft-ietf-wpack-bundled-responses | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Call For Adoption By WG Issued | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-wpack-bundled-responses | |
Consensus boilerplate | Unknown | ||
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 request URLs and content negotiation that produced them, to transmit or store 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.)