Ecosystem Effects of Web Packaging
draft-yasskin-wpack-ecosystem-effects-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Jeffrey Yasskin | ||
| Last updated | 2020-04-09 (Latest revision 2019-10-07) | ||
| RFC stream | (None) | ||
| Intended RFC status | (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
This document analyzes how Web Packaging may affect the web ecosystem. Note to Readers This document has NOT been reviewed widely and probably contains lots of mistakes. Discussion of this draft takes place on the wpack mailing list (wpack@ietf.org), which is archived at https://www.ietf.org/mailman/listinfo/wpack [1]. The source code and issues list for this draft can be found in https://github.com/jyasskin/wpack-ecosystem-effects [2].
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)