Ecosystem Effects of Web Packaging
draft-yasskin-wpack-ecosystem-effects-00

Document Type Active Internet-Draft (individual)
Last updated 2019-10-07
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf htmlized bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
Network Working Group                                         J. Yasskin
Internet-Draft                                                    Google
Intended status: Informational                          October 07, 2019
Expires: April 9, 2020

                   Ecosystem Effects of Web Packaging
                draft-yasskin-wpack-ecosystem-effects-00

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].

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 9, 2020.

Copyright Notice

   Copyright (c) 2019 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Yasskin                   Expires April 9, 2020                 [Page 1]
Internet-Draft     Ecosystem Effects of Web Packaging       October 2019

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  General . . . . . . . . . . . . . . . . . . . . . . . . . . .   2
   3.  Aggregators . . . . . . . . . . . . . . . . . . . . . . . . .   3
   4.  Browsers  . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   5.  CDNs  . . . . . . . . . . . . . . . . . . . . . . . . . . . .   3
   6.  Content Producers . . . . . . . . . . . . . . . . . . . . . .   4
   7.  Other effects not necessarily related to centralization . . .   4
   8.  Security Considerations . . . . . . . . . . . . . . . . . . .   4
   9.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   4
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .   4
     10.1.  Informative References . . . . . . . . . . . . . . . . .   4
     10.2.  URIs . . . . . . . . . . . . . . . . . . . . . . . . . .   5
   Appendix A.  Change Log . . . . . . . . . . . . . . . . . . . . .   5
   Appendix B.  Acknowledgements . . . . . . . . . . . . . . . . . .   5
   Author's Address  . . . . . . . . . . . . . . . . . . . . . . . .   5

1.  Introduction

   Web Packaging, as currently defined in
   [I-D.yasskin-wpack-bundled-exchanges] and
   [I-D.yasskin-http-origin-signed-responses], is a system to allow
   content authored by one web origin to be retrieved in an optionally-
   trustworthy way from a peer or other intermediate server.  The ESCAPE
   conference [3] was chartered to (among other things) look for any
   increase in consolidation that might result from standardizing Web
   Packaging.  The known possible effects on centralization and power
   imbalances, arranged by the type of service provider, and not
   filtered by benefit, harm, or likelihood, follow.

2.  General

   o  The implementation of any new technology is a smaller fraction of
      a large organization's budget, which pushes toward centralization.

Yasskin                   Expires April 9, 2020                 [Page 2]
Internet-Draft     Ecosystem Effects of Web Packaging       October 2019

3.  Aggregators

   o  Aggregators' primary power comes from ranking: telling people that
      they probably want to visit particular URLs.  That's not affected
      by packaging.

   o  Aggregators already rank based on sites' content and technology
      choices. e.g.  Google's promotion of HTTPS sites.  Packaging can
      give the aggregator more certainty about the user's experience,
      which might lead to more intrusive requirements.

      For example, the Google Search Carousel might be able to insist on
Show full document text