Re: [Wpack] Problem statement and scope for BoF

"Salz, Rich" <rsalz@akamai.com> Wed, 07 August 2019 17:14 UTC

Return-Path: <rsalz@akamai.com>
X-Original-To: wpack@ietfa.amsl.com
Delivered-To: wpack@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64B5A1206F6 for <wpack@ietfa.amsl.com>; Wed, 7 Aug 2019 10:14:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level:
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=akamai.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id d2vPdA1zgO7c for <wpack@ietfa.amsl.com>; Wed, 7 Aug 2019 10:14:32 -0700 (PDT)
Received: from mx0a-00190b01.pphosted.com (mx0a-00190b01.pphosted.com [IPv6:2620:100:9001:583::1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A71291206E7 for <wpack@ietf.org>; Wed, 7 Aug 2019 10:14:18 -0700 (PDT)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id x77GwTge018589; Wed, 7 Aug 2019 18:14:18 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=83F9bNOxi9DzY9cQP/dTvVdjOwbYhJbEKxckw7DY4BU=; b=cAMcLfGB4kPhoGeTTTJO4HKwdD4LgDoF3P6QpYwxiQWaQk2zKR9wmWOzbYdS79oYNcMh fD89nkJIw3KbnYRd1stqocQJpX3hTskXyVsFzFN//TvswUAUywvWNp7nemQWAyFlnZKV SmJlSCsZsq9zb2Rbgo6h5tzFNEv6RJmbZTZScPtvcqQYLGrqBdSIMrTGEYHUME2UtslW qxP8uRaW6or9PqvtZ3bTD5T2SVDCoepqq47wnPctEJxqZnB9fgXj5FtS4L286wLhtqOs 6gyGKdeyTGQGUcm6lQypp9RcA3M+iDhq78kJSWuZFyhhz2KVeGhgnUm6qsWAJhdWwl0F cg==
Received: from prod-mail-ppoint5 (prod-mail-ppoint5.akamai.com [184.51.33.60] (may be forged)) by m0050095.ppops.net-00190b01. with ESMTP id 2u51t4mbq9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 07 Aug 2019 18:14:18 +0100
Received: from pps.filterd (prod-mail-ppoint5.akamai.com [127.0.0.1]) by prod-mail-ppoint5.akamai.com (8.16.0.27/8.16.0.27) with SMTP id x77H2Sbw021337; Wed, 7 Aug 2019 10:14:16 -0700
Received: from email.msg.corp.akamai.com ([172.27.123.32]) by prod-mail-ppoint5.akamai.com with ESMTP id 2u5888fdu4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 07 Aug 2019 10:14:16 -0700
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb4.msg.corp.akamai.com (172.27.123.104) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Wed, 7 Aug 2019 13:14:16 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com ([172.27.123.101]) by usma1ex-dag1mb1.msg.corp.akamai.com ([172.27.123.101]) with mapi id 15.00.1473.005; Wed, 7 Aug 2019 13:14:16 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Jeffrey Yasskin <jyasskin=40google.com@dmarc.ietf.org>, "wpack@ietf.org" <wpack@ietf.org>
Thread-Topic: [Wpack] Problem statement and scope for BoF
Thread-Index: AQHVS7Y5soTKl9Q6r0ibFluHsp3M6Kbv76eA
Date: Wed, 07 Aug 2019 17:14:15 +0000
Message-ID: <FE95EE3D-099E-4AF8-8E3D-AF8C99252098@akamai.com>
References: <CANh-dXkRGGVAzRPC5k8p0u6b7NuidkOt81in70eF3Nwe_BAZQw@mail.gmail.com>
In-Reply-To: <CANh-dXkRGGVAzRPC5k8p0u6b7NuidkOt81in70eF3Nwe_BAZQw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/10.1b.0.190715
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.33.97]
Content-Type: text/plain; charset="utf-8"
Content-ID: <858D4E825031D84AB486C168D14752D0@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-08-07_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1908070166
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:5.22.84,1.0.8 definitions=2019-08-07_04:2019-08-07,2019-08-07 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 lowpriorityscore=0 priorityscore=1501 mlxscore=0 mlxlogscore=999 spamscore=0 clxscore=1015 adultscore=0 phishscore=0 malwarescore=0 bulkscore=0 suspectscore=0 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1906280000 definitions=main-1908070166
Archived-At: <https://mailarchive.ietf.org/arch/msg/wpack/H5mcFDPq2a3fS479szjhH7K95Qs>
Subject: Re: [Wpack] Problem statement and scope for BoF
X-BeenThere: wpack@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Web Packaging <wpack.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/wpack>, <mailto:wpack-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/wpack/>
List-Post: <mailto:wpack@ietf.org>
List-Help: <mailto:wpack-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/wpack>, <mailto:wpack-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 07 Aug 2019 17:14:39 -0000

>    * Other users run out of paid-for data in their mobile plan part-way
    through a month, or aggressively disable mobile data to make sure it's
    not wasted.
  
Strike this item; there is *zero* data to indicate that it is because of users (inadvertently) loading web pages, as opposed to other reasons, such as push notifications, geo-tracking, and so on.
    
>    These users currently have to, at best, tell their browsers to
    pre-fetch sites when they have a cheap real-time connection available
    or wait until they find such a connection, and at worst, can't browse
    the content at all.
  
Yes, this characterizes the previous items.  HOWEVER, I strongly suggest that we need a new first item, and this paragraph then becomes diluted.  Some restructuring will be necessary.
  
>    Even users with highly-available internet connections want to be able
    to read and interact with web pages as quickly as possible after
    clicking a link. Needing to make extra connections in the critical
    path, and having multiple connections competing for bandwidth without
    the ability to prioritize, interfere with that goal.
  
I am not sure I agree with this.  There is a large body of user experience studies that show how long a delay can be and zero isn't it. :)

NEW FIRST ITEM.  I believe the following captures the real driver behind this work. So much so that this should be the first listed motivator of the problem statement. While the other use-cases are important, I am less sanguine -- or perhaps just more cynical -- that those things will ever be addressed.  The main driver has billions of dollars behind it after all.

* Third-party aggregators, such as social media and search engines, want to push external content to the user while the page is being loaded and/or displayed. This enables previews, or thumbnails, etc., to be displayed without the user committing to seeing the full content (and therefore without the origin getting notification). All three parties -- the user, the origin, and the aggregator -- want this content to be cryptographically secure and tamper-evident.

I prefer to have discussions on the mailing list for greater visibility, archiving, and because it's more IETF-like.