IETF Logo Mail Archive

Re: [Wpack] Problem statement and scope for BoF

"Salz, Rich" <rsalz@akamai.com> Mon, 05 August 2019 23:27 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 520561200E7 for <wpack@ietfa.amsl.com>; Mon, 5 Aug 2019 16:27:59 -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 AlDomXBrflMv for <wpack@ietfa.amsl.com>; Mon, 5 Aug 2019 16:27:58 -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 227F31200C1 for <wpack@ietf.org>; Mon, 5 Aug 2019 16:27:58 -0700 (PDT)
Received: from pps.filterd (m0122333.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id x75NR8qE027439; Tue, 6 Aug 2019 00:27:56 +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=OA4hkZFuTEAUNZMYtJ1JueQWWDFuzuml3mkTmXs2pnc=; b=lz2AEClRQrj/+3clx7khoD8c9czc5a4L2QBWw56km1ssEj8PqPJJLlk3UpXsjHWeReUg hESs02T25Wl3iljXPxknMk8XSXHfSe/OKsZgRFxnZG6S0toV6uq22VgMQf0vlqVgo4l4 icrHzCtQxTrhFUlf5ZRoL4T7nM93onT3Mov2/uidZrjOol4t2pyWmyc4N+a7rwx45DUL wz2fTkuA1UOk93SMxwg0bDIrcdUcB6xCnXZYGRu70MZZcs2HdnvoFiYvZTd94IITp2XX nyGlCrI16ln+k/nBQdSLn8B1KeLNDxFj5dRRqJ9IZGrfuQhM6FuJj2OD3cbx3JulmEZa PA==
Received: from prod-mail-ppoint3 (prod-mail-ppoint3.akamai.com [96.6.114.86] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 2u51h7kac9-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 06 Aug 2019 00:27:56 +0100
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.27/8.16.0.27) with SMTP id x75NI2se013251; Mon, 5 Aug 2019 19:27:55 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.53]) by prod-mail-ppoint3.akamai.com with ESMTP id 2u55m12tcp-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 05 Aug 2019 19:27:55 -0400
Received: from USMA1EX-DAG1MB1.msg.corp.akamai.com (172.27.123.101) by usma1ex-dag1mb6.msg.corp.akamai.com (172.27.123.65) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Mon, 5 Aug 2019 19:27:47 -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; Mon, 5 Aug 2019 19:27:47 -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: AQHVS7Y5soTKl9Q6r0ibFluHsp3M6KbtM1uA
Date: Mon, 05 Aug 2019 23:27:47 +0000
Message-ID: <C1E62FBD-28A5-4B1B-8C99-06397919E68C@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.40.163]
Content-Type: text/plain; charset="utf-8"
Content-ID: <2D610F5534DFCB48851B63F03B8A4E40@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-08-05_13:, , 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=770 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1908050235
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:5.22.84,1.0.8 definitions=2019-08-05_13:2019-07-31,2019-08-05 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 mlxscore=0 lowpriorityscore=0 impostorscore=0 mlxlogscore=740 spamscore=0 clxscore=1011 adultscore=0 phishscore=0 bulkscore=0 suspectscore=0 priorityscore=1501 malwarescore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1906280000 definitions=main-1908050237
Archived-At: <https://mailarchive.ietf.org/arch/msg/wpack/e0MMlkhD3EQHRtW15NQqBQHsLv8>
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: Mon, 05 Aug 2019 23:27:59 -0000

Commenting only on the "problem" part of your post; I reserve the right to comment on other parts later :)

I am surprised that search carousel and AMP isn't mentioned, as frankly it is the use-case with the most economic incentive/impact. Honesty compels us to explicitly mention it, plainly, and first.

>    * 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.
  
We have seen no evidence that this is done because of surfing, as opposed to tracking or other app activity.

v2.23.0 | Report a Bug | By Email