IETF Logo Mail Archive

Re: [Wpack] Problem statement and scope for BoF

"Salz, Rich" <rsalz@akamai.com> Wed, 07 August 2019 18:46 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 2057C1202E1 for <wpack@ietfa.amsl.com>; Wed, 7 Aug 2019 11:46:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham 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 Qjw2kU146oQH for <wpack@ietfa.amsl.com>; Wed, 7 Aug 2019 11:46:52 -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 8BEEF120152 for <wpack@ietf.org>; Wed, 7 Aug 2019 11:46:50 -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 x77IW1OL014582; Wed, 7 Aug 2019 19:46:47 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=jan2016.eng; bh=pL55HUBUfTHqt/IrBPTwqDhuxWxLmbRbZgX7Y1JMMHQ=; b=EV2u2yXQQcA5sA4li5pZGrcoJ3eiEgpNTo2lnW38Dx+9WkrWqPcPlzCfhPYP+HcIC+de yIxYTDCimTMsBGnFQRqBbkyt3kSQi1FmCVD5HxukiF2yt3kvuTcco/qbhGuM7tN/n3Jy IDJ9IZZtfU+64bsGN0f3tBUSQH0ay5oukh27iGSkvw1u9ZoB7kLt8mBeCuDfyryoH0y2 67xt+Nj/UEQCDAt53kfd/zOk5ZO4BXM8p2U8+IA5Ht51jO02v7s9VJm+AbD7EFADM/Wl dvmBjfcAYcNar7LfKyf5XtptlV/7wekOhKBqKR2NGGzcoMRvONvQCWOJgXezzaCLzLbE Ag==
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 2u51t4ms3s-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 07 Aug 2019 19:46:46 +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 x77IX6HM022042; Wed, 7 Aug 2019 11:46:45 -0700
Received: from email.msg.corp.akamai.com ([172.27.123.33]) by prod-mail-ppoint5.akamai.com with ESMTP id 2u5888fhp2-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 07 Aug 2019 11:46:45 -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 14:46:44 -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 14:46:44 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Jeffrey Yasskin <jyasskin@google.com>
CC: "wpack@ietf.org" <wpack@ietf.org>
Thread-Topic: [Wpack] Problem statement and scope for BoF
Thread-Index: AQHVS7Y5soTKl9Q6r0ibFluHsp3M6KbtM1uAgAL8kAD//9mTAA==
Date: Wed, 07 Aug 2019 18:46:44 +0000
Message-ID: <245D3939-6FF6-47B4-A353-F394844BE0C5@akamai.com>
References: <CANh-dXkRGGVAzRPC5k8p0u6b7NuidkOt81in70eF3Nwe_BAZQw@mail.gmail.com> <C1E62FBD-28A5-4B1B-8C99-06397919E68C@akamai.com> <CANh-dX=Q6G0ArLhHA6K-DsW87QkgJPNmP25vj05LNcLmZEysJA@mail.gmail.com>
In-Reply-To: <CANh-dX=Q6G0ArLhHA6K-DsW87QkgJPNmP25vj05LNcLmZEysJA@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: multipart/alternative; boundary="_000_245D39396FF647B4A353F394844BE0C5akamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-08-07_05:, , 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=958 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1906280000 definitions=main-1908070170
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:5.22.84,1.0.8 definitions=2019-08-07_05: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=931 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-1908070170
Archived-At: <https://mailarchive.ietf.org/arch/msg/wpack/b1G4XdtotRKlNw9RX-xY-QUZALA>
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 18:46:54 -0000

> The use case is broader than just one framework or piece of search result UI, so it seemed wrong to call out particular brands.

I did not mention any brands in my note, I only mentioned two use cases.

>The inference I'm going for here is that, if users have turned off or run out of their data, even because of native-app misbehavior, they can't then browse to and install a web app. I'm having trouble coming up with wording that would make that clearer without being too wordy. Any ideas?

I think you just wrote it in the sentence above. :)

v2.23.0 | Report a Bug | By Email