
From nobody Tue May  1 05:19:13 2018
Return-Path: <bkaduk@akamai.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DCD212711B for <quic@ietfa.amsl.com>; Tue,  1 May 2018 05:19:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Level: 
X-Spam-Status: No, score=-2.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 muTG6Dz9AWB3 for <quic@ietfa.amsl.com>; Tue,  1 May 2018 05:19:11 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::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 4BCD412D959 for <quic@ietf.org>; Tue,  1 May 2018 05:19:11 -0700 (PDT)
Received: from pps.filterd (m0050096.ppops.net [127.0.0.1]) by m0050096.ppops.net-00190b01. (8.16.0.22/8.16.0.22) with SMTP id w41CHr6x007459; Tue, 1 May 2018 13:19:08 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : content-transfer-encoding : in-reply-to; s=jan2016.eng; bh=PmK5kTMmiSQo/C9QqCMM4/5H9ZxIof2bK6SiYRIc2oA=; b=Bj2WHipfOH9rKuOiAw/bvDIoJq3luuPAhO4/PhxeERMQahiWuJkk13sQ3Sceeur2tTB0 /bl/TQAOQ6ZAfZFCkrQhGUC2B1rHEqkH4Ll+kQ99nB7XjmbE2SML59ju+zW6X6Sr9C8c Nl7sIyV+a6MbgAa5s4HdPRV/7fyJBkUikdUKDCGRbDSecMRKPuYp6uCdLDCOKQXnQJcg nR9FJN2VoChKwpldKCdZfEJqp7RAX4kv5PkMH6vXL80q/gvRKvq8w89i2ZXqRy2S8zoX xzuSgq1JjeabqGVP9+SRGc/ys/Xuy7OgmAtEbWzM8a2eRD7h512t/yR+eiPYm6+IPkGx Dg== 
Received: from prod-mail-ppoint3 ([96.6.114.86]) by m0050096.ppops.net-00190b01. with ESMTP id 2hmqgqev7q-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 01 May 2018 13:19:08 +0100
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w41CGQ8l001458; Tue, 1 May 2018 08:19:07 -0400
Received: from prod-mail-relay14.akamai.com ([172.27.17.39]) by prod-mail-ppoint3.akamai.com with ESMTP id 2hmm9wangq-1; Tue, 01 May 2018 08:19:07 -0400
Received: from bos-lpczi.kendall.corp.akamai.com (bos-lpczi.kendall.corp.akamai.com [172.19.17.86]) by prod-mail-relay14.akamai.com (Postfix) with ESMTP id A8C4982BA6; Tue,  1 May 2018 12:19:07 +0000 (GMT)
Received: from bkaduk by bos-lpczi.kendall.corp.akamai.com with local (Exim 4.86_2) (envelope-from <bkaduk@akamai.com>) id 1fDUFO-0004XA-Qz; Tue, 01 May 2018 07:19:06 -0500
Date: Tue, 1 May 2018 07:19:06 -0500
From: Benjamin Kaduk <bkaduk@akamai.com>
To: Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>
Cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Getting to consensus on packet number encryption
Message-ID: <20180501121906.GA5742@akamai.com>
References: <CANatvzwCYrOZULG3iVmDFp97nr=M5=Gufo8TZjOGQVFUpsn0bQ@mail.gmail.com> <CAAedzxqDcPXJUE83KVnDiU23PvqDcTCrc6rRMw09FexjJA-Y6Q@mail.gmail.com> <CANatvzwjYE6EdvFtOXJMVQnutbVQ4YY+=XsQFzKwHzqWzZ4U+w@mail.gmail.com> <d32ade7b56bf4651952659307c08893b@usma1ex-dag1mb5.msg.corp.akamai.com> <CANatvzwHtCn8rLB8npf3i7PGyYZhVDRd2uojh5hv3uxtFPEsSA@mail.gmail.com> <58447D8E-782C-431C-8FC3-71124B10A047@trammell.ch> <CACpbDcdfF9w3qqrH1eB0sGU_4vheD9aMP5EXnp1o3Y19N19NUg@mail.gmail.com> <e8b4931a-3931-5b8d-8dad-3ca1939d5542@huitema.net> <CAKcm_gPaj3o-VTdA_0+Kk+nTcVJrYcs_BMyOiDGXKub3gB=GLg@mail.gmail.com> <MWHPR21MB063869878060E850137210FEB6820@MWHPR21MB0638.namprd21.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <MWHPR21MB063869878060E850137210FEB6820@MWHPR21MB0638.namprd21.prod.outlook.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-01_06:, , 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=909 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805010124
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-01_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=893 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805010124
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/haxLbg7TVyItLQGvpGmq5zPoz4o>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2018 12:19:12 -0000

On Mon, Apr 30, 2018 at 09:55:31PM +0000, Praveen Balasubramanian wrote:
> I disagree that we need any more data for not doing PNE in the datacenter. Why would we add an extra encrypt-decrypt step for no obvious benefit? The cost of this operation will keep magnifying as UDP performance improves. We have several optimizations planned for UDP, but short of hardware offload, none for crypto – this is an important trend to account for performance wise. For short packets like ACKs an extra encrypt decrypt step can become a large fraction of CPU cost over time.

There is benefit in uniformity and simplicity of implementation; I concede that
the claimed potential benefits about the middlebox ecosystem are speculative,
but the simplicity seems clear to me.

With respect to the cost of the crypto, yes we have some numbers, but AFAICT we
don't have a great view for how they will fit into the broader picture as
implementations mature, so to some extent the estimate of the magnitude of
growing cost of crypto is also a speculative position.  (Also, who is the "we"
that has several optimizations planned?)

In other words, how do we know this is not premature optimization?  Shouldn't
we wait until we have actual performance numbers before doing lots of
optimization?  I was under the impression that QUIC versions were going to be
lightweight, so putting out v1 with mandatory PNE would not preclude quickly
following with a V3 that adapts to any discovered performance concerns, whether
for datacenter usage or otherwise.

-Ben


From nobody Tue May  1 05:24:33 2018
Return-Path: <rsalz@akamai.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C758612E8A9 for <quic@ietfa.amsl.com>; Tue,  1 May 2018 05:24:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Level: 
X-Spam-Status: No, score=-2.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 E4Y2XazV51yq for <quic@ietfa.amsl.com>; Tue,  1 May 2018 05:24:30 -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 158C012711B for <quic@ietf.org>; Tue,  1 May 2018 05:24:30 -0700 (PDT)
Received: from pps.filterd (m0122332.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w41CNOVU011173; Tue, 1 May 2018 13:24:25 +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 : content-id : content-transfer-encoding : mime-version; s=jan2016.eng; bh=Tb75ijHWIO0NLHaIDs8UYUWaOUXt+TChnaBg5DUG0UQ=; b=PLLEHz0TBeJlRPIp7TjGJtVD+BJt3J1YcRdv709gSTLT1/UeI22GjMO3Pvc7RGNqyrBJ ANrewSzcAWDKGl3N7KsWROFy8WPi5EdCdWaCQPkTvyttkSG4Rcc0DH+CZb2Y/MLBdxKG UkYgd2QRGS+X1qdFHQwHErpsU7rYq0s3AebErwOt6XMBOi+r02IvsKdtYPbmiPMIyNad v2I6u46+Tj0WNWGM8YsAy7fw8VXcOWQ4fB3g/D/NcNVdCIXttv1wwvL7MQ0PZFjJ9ijd XkzmX750KlxI1NC2UTXysfucvIej5fW7ZFwxjJ7+2EmN44ZyzV0jYcok7pJ7FClyFoGJ Vg== 
Received: from prod-mail-ppoint1 (prod-mail-ppoint1.akamai.com [184.51.33.18]) by mx0a-00190b01.pphosted.com with ESMTP id 2hmq3ppa35-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 01 May 2018 13:24:25 +0100
Received: from pps.filterd (prod-mail-ppoint1.akamai.com [127.0.0.1]) by prod-mail-ppoint1.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w41CGMsL006131; Tue, 1 May 2018 08:24:24 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.33]) by prod-mail-ppoint1.akamai.com with ESMTP id 2hpq2er765-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 01 May 2018 08:24:23 -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 Microsoft SMTP Server (TLS) id 15.0.1365.1; Tue, 1 May 2018 08:24:22 -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.1365.000; Tue, 1 May 2018 08:24:22 -0400
From: "Salz, Rich" <rsalz@akamai.com>
To: Benjamin Kaduk <bkaduk=40akamai.com@dmarc.ietf.org>, "Praveen Balasubramanian" <pravb=40microsoft.com@dmarc.ietf.org>
CC: IETF QUIC WG <quic@ietf.org>
Subject: Re: Getting to consensus on packet number encryption
Thread-Topic: Getting to consensus on packet number encryption
Thread-Index: AQHTy9GXSeU4f/oSSU2pFoD72eb3CKPwqlkAgAC4ugCAAARcAIAAG5CAgAAFCQCAAACJgIAAEVgAgACR+YCAB09lAIAFXyIAgAVK+oCAAJlSAIABxdSAgACOHYCAB/ExAIACo7YAgACiMICAAADPgIAAIs8AgAAm/YCAABEygIAABpIAgAAK6ACAAPIgAIAA5wYAgACzcYCAAHHMgIAEe1cAgAABEACAABWHgIAA8UgA//++awA=
Date: Tue, 1 May 2018 12:24:22 +0000
Message-ID: <F63059EA-BA14-4886-A4FB-AA5F04AC164B@akamai.com>
References: <CANatvzwCYrOZULG3iVmDFp97nr=M5=Gufo8TZjOGQVFUpsn0bQ@mail.gmail.com> <CAAedzxqDcPXJUE83KVnDiU23PvqDcTCrc6rRMw09FexjJA-Y6Q@mail.gmail.com> <CANatvzwjYE6EdvFtOXJMVQnutbVQ4YY+=XsQFzKwHzqWzZ4U+w@mail.gmail.com> <d32ade7b56bf4651952659307c08893b@usma1ex-dag1mb5.msg.corp.akamai.com> <CANatvzwHtCn8rLB8npf3i7PGyYZhVDRd2uojh5hv3uxtFPEsSA@mail.gmail.com> <58447D8E-782C-431C-8FC3-71124B10A047@trammell.ch> <CACpbDcdfF9w3qqrH1eB0sGU_4vheD9aMP5EXnp1o3Y19N19NUg@mail.gmail.com> <e8b4931a-3931-5b8d-8dad-3ca1939d5542@huitema.net> <CAKcm_gPaj3o-VTdA_0+Kk+nTcVJrYcs_BMyOiDGXKub3gB=GLg@mail.gmail.com> <MWHPR21MB063869878060E850137210FEB6820@MWHPR21MB0638.namprd21.prod.outlook.com> <20180501121906.GA5742@akamai.com>
In-Reply-To: <20180501121906.GA5742@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.c.0.180410
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.40.122]
Content-Type: text/plain; charset="utf-8"
Content-ID: <8FC6B80A79490D44B46BB25CCEC19CAE@akamai.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-01_06:, , 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=781 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805010124
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-01_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=724 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805010125
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Fdif1mFntANavCn7hP3_SVEwNFY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2018 12:24:33 -0000

ICAgID4gSSBkaXNhZ3JlZSB0aGF0IHdlIG5lZWQgYW55IG1vcmUgZGF0YSBmb3Igbm90IGRvaW5n
IFBORSBpbiB0aGUgZGF0YWNlbnRlci4gV2h5IHdvdWxkIHdlIGFkZCBhbiBleHRyYSBlbmNyeXB0
LWRlY3J5cHQgc3RlcCBmb3Igbm8gb2J2aW91cyBiZW5lZml0Pw0KDQpJIGFtIGNvbmNlcm5lZCB0
aGF0IHBlb3BsZSB3aWxsIG1pcy1pbnRlcnByZXQgdGhlIG1lYW5pbmcgb2YgYSBkYXRhY2VudGVy
LCBhbmQgdGhpbmsgdGhhdCBhIGJ1bmNoIG9mIHNlcnZlcnMsIG9yIGV2ZW4gYSByYWNrLCBpbiBh
biBvcGVuIGNvbG8gc3BhY2UgaXMgYSAiZGF0YWNlbnRlci4iICBDb21wdXRlcnMga2VlcCBnZXR0
aW5nIGZhc3Rlci4gDQoNCg==


From nobody Tue May  1 08:13:19 2018
Return-Path: <prvs=86592f1e95=fenix@fb.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 535F112DA15 for <quic@ietfa.amsl.com>; Tue,  1 May 2018 08:13:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=UKM14Zkc; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=Q54w0JGH
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 XY645ZhUZazI for <quic@ietfa.amsl.com>; Tue,  1 May 2018 08:13:16 -0700 (PDT)
Received: from mx0a-00082601.pphosted.com (mx0b-00082601.pphosted.com [67.231.153.30]) (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 F248812DA29 for <quic@ietf.org>; Tue,  1 May 2018 08:13:15 -0700 (PDT)
Received: from pps.filterd (m0001255.ppops.net [127.0.0.1]) by mx0b-00082601.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w41F7Bpp016471; Tue, 1 May 2018 08:13:11 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=facebook; bh=68T9qIQ1yrrFuls3hfbvW4W9RGWrFFpyfbQtnw3fik4=; b=UKM14ZkcGghLblFIdrEZFt5nzOytRIjCROkjMLhRg6s/rDQuuUfDv2KXN+l0mFplsFCv qepLNdlKM/pcksYvnR9byvyDFynC1QWTKDDTIXQA3UB6M1CT2cAq4iH9GyjM0RJDVLU6 xWXDTFVIcKPFghTUtb5ExtpHQfRUp1YKYUE= 
Received: from mail.thefacebook.com ([199.201.64.23]) by mx0b-00082601.pphosted.com with ESMTP id 2hp96qt3r2-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 01 May 2018 08:13:10 -0700
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (192.168.54.28) by o365-in.thefacebook.com (192.168.16.18) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 1 May 2018 08:13:09 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version;  bh=68T9qIQ1yrrFuls3hfbvW4W9RGWrFFpyfbQtnw3fik4=; b=Q54w0JGH48/JAcgqRX1UgsMSsRQxXBkhFjT1RrmFG3XrfWyCRLQerbJLaEmaFOI5PwxI4eHdr8kajXn88FB00w3IvkD8p7NtJFbDumeyHs7icwA9OsS4ueFbenDdbQXP6YWPfaje8Itv0cm226DtxBtmyLlsM+2fsYDyck4L2Xc=
Received: from BY2PR15MB0775.namprd15.prod.outlook.com (10.164.171.11) by BY2PR15MB0343.namprd15.prod.outlook.com (10.163.109.152) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.696.17; Tue, 1 May 2018 15:13:07 +0000
Received: from BY2PR15MB0775.namprd15.prod.outlook.com ([fe80::6c4c:bbf3:ec3b:d45e]) by BY2PR15MB0775.namprd15.prod.outlook.com ([fe80::6c4c:bbf3:ec3b:d45e%14]) with mapi id 15.20.0715.024; Tue, 1 May 2018 15:13:07 +0000
From: Roberto Peon <fenix@fb.com>
To: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, Benjamin Kaduk <bkaduk=40akamai.com@dmarc.ietf.org>, Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>
CC: IETF QUIC WG <quic@ietf.org>
Subject: Re: Getting to consensus on packet number encryption
Thread-Topic: Getting to consensus on packet number encryption
Thread-Index: AQHTy9GjyGQaKf4GI0anNhXTngANsKPwZ0sAgAC4ugCAAARcAIAAG5CAgAAFCACAAACJgIAAEVkAgACR+ICAAVFHAIALXUEAgAVKTpWAAJn+AIABxdSAgACOHICAB/EyAIACo7YAgACiL4CAAADQgIAAIs8AgAAm/YCAABExgIAABpIAgAAK6ACAAPIgAIAA5wYAgACzcoCAAHHMgIAEe1cAgAABEACAABWHgIAA8UgAgAABeQCAAC8lSQ==
Date: Tue, 1 May 2018 15:13:06 +0000
Message-ID: <BY2PR15MB07757EAB6A818F1D8D8CCED9CD810@BY2PR15MB0775.namprd15.prod.outlook.com>
References: <CANatvzwCYrOZULG3iVmDFp97nr=M5=Gufo8TZjOGQVFUpsn0bQ@mail.gmail.com> <CAAedzxqDcPXJUE83KVnDiU23PvqDcTCrc6rRMw09FexjJA-Y6Q@mail.gmail.com> <CANatvzwjYE6EdvFtOXJMVQnutbVQ4YY+=XsQFzKwHzqWzZ4U+w@mail.gmail.com> <d32ade7b56bf4651952659307c08893b@usma1ex-dag1mb5.msg.corp.akamai.com> <CANatvzwHtCn8rLB8npf3i7PGyYZhVDRd2uojh5hv3uxtFPEsSA@mail.gmail.com> <58447D8E-782C-431C-8FC3-71124B10A047@trammell.ch> <CACpbDcdfF9w3qqrH1eB0sGU_4vheD9aMP5EXnp1o3Y19N19NUg@mail.gmail.com> <e8b4931a-3931-5b8d-8dad-3ca1939d5542@huitema.net> <CAKcm_gPaj3o-VTdA_0+Kk+nTcVJrYcs_BMyOiDGXKub3gB=GLg@mail.gmail.com> <MWHPR21MB063869878060E850137210FEB6820@MWHPR21MB0638.namprd21.prod.outlook.com> <20180501121906.GA5742@akamai.com>, <F63059EA-BA14-4886-A4FB-AA5F04AC164B@akamai.com>
In-Reply-To: <F63059EA-BA14-4886-A4FB-AA5F04AC164B@akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2600:387:6:803::a0]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BY2PR15MB0343; 7:0a+aaAHxFrEDQ4zlFLz7c43v+/2pOyZpHFkwWin1gOSzsE9/8iLfqwVqrhA7Tosaiizj73G2KpQv7HygL783JdyIyGOxci/YKJOmYgtMFMBBn4p2B/bXB59Wi76p5DXsIbjF7FCBXjvLNj3DOPmXw36qbFeFN1FXGZZ/sLGVRhUyk6COpuEux5erWcmHriPXokNR8aaspHdqidpeeQV7jdHk3o55gPVFAAKkgpUWGyv+unGebDaxSzC5hFSEubgh; 20:Tn+krDfoJl+wPtMkrWj/nls6DxztiBITTf2Awc0L7N0lBoEI0y911/e2gta4YqaW/hHL/y149VynT6JUYkGR6wLn3xzgqfsbZKJOqH3PDpFNAqZYH4KXNvKvFLuS6BTYPm5XXDkAsfwSauLU06xbKNSJ2XOPiPr9ezE+gPotfDg=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(2017052603328)(7153060)(7193020); SRVR:BY2PR15MB0343; 
x-ms-traffictypediagnostic: BY2PR15MB0343:
x-microsoft-antispam-prvs: <BY2PR15MB0343500701CE0F25CCA69A67CD810@BY2PR15MB0343.namprd15.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(100405760836317);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3231254)(11241501184)(944501410)(52105095)(3002001)(10201501046)(93006095)(93001095)(6041310)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123564045)(6072148)(201708071742011); SRVR:BY2PR15MB0343; BCL:0; PCL:0; RULEID:; SRVR:BY2PR15MB0343; 
x-forefront-prvs: 06592CCE58
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(346002)(376002)(39380400002)(366004)(396003)(189003)(199004)(110136005)(6436002)(105586002)(55016002)(5250100002)(2906002)(5660300001)(33656002)(6116002)(7696005)(7736002)(93886005)(446003)(4326008)(68736007)(6246003)(106356001)(478600001)(102836004)(14454004)(476003)(99286004)(8936002)(486006)(97736004)(229853002)(76176011)(11346002)(316002)(8676002)(186003)(2900100001)(81156014)(3280700002)(86362001)(81166006)(3660700001)(9686003)(54896002)(53936002)(53546011)(6506007)(25786009)(74316002)(46003)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR15MB0343; H:BY2PR15MB0775.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: fb.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: PEl3Her0nZ8+LlU/AFPf6f9c77IX3isWmewYFlKPmcsPlFEdtr7j33DNa8rNrrV5+FPhVRfFALaqgRi/uOsZ80uCxnQUqoxVDwIIFuDDIgDvuGceyk7McOSrboFPA+RUSTTjglOrTmSbK+uMcRw9ieRgy4cv5evR7u1ac/E0N4HOnL4x3hQ2zD3Y1mVFdmHU
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BY2PR15MB07757EAB6A818F1D8D8CCED9CD810BY2PR15MB0775namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 37dc0776-46bf-4a35-dc1b-08d5af760b2a
X-MS-Exchange-CrossTenant-Network-Message-Id: 37dc0776-46bf-4a35-dc1b-08d5af760b2a
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 May 2018 15:13:06.9903 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR15MB0343
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-01_07:, , signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/zJp_mR0wJtFbGEWwAtAkBYbx8Co>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2018 15:13:17 -0000

--_000_BY2PR15MB07757EAB6A818F1D8D8CCED9CD810BY2PR15MB0775namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Also, Prism.

-=3DR


Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone


-------- Original message --------
From: "Salz, Rich" <rsalz=3D40akamai.com@dmarc.ietf.org>
Date: 5/1/18 5:25 AM (GMT-08:00)
To: Benjamin Kaduk <bkaduk=3D40akamai.com@dmarc.ietf.org>, Praveen Balasubr=
amanian <pravb=3D40microsoft.com@dmarc.ietf.org>
Cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Getting to consensus on packet number encryption

    > I disagree that we need any more data for not doing PNE in the datace=
nter. Why would we add an extra encrypt-decrypt step for no obvious benefit=
?

I am concerned that people will mis-interpret the meaning of a datacenter, =
and think that a bunch of servers, or even a rack, in an open colo space is=
 a "datacenter."  Computers keep getting faster.


--_000_BY2PR15MB07757EAB6A818F1D8D8CCED9CD810BY2PR15MB0775namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>Also, Prism.&nbsp;</div>
<div><br>
</div>
<div>-=3DR&nbsp;</div>
<div><br>
</div>
<div><br>
</div>
<div id=3D"x_composer_signature">
<div dir=3D"auto" style=3D"font-size:85%; color:#575757">Sent via the Samsu=
ng Galaxy S7, an AT&amp;T 4G LTE smartphone</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div>-------- Original message --------</div>
<div>From: &quot;Salz, Rich&quot; &lt;rsalz=3D40akamai.com@dmarc.ietf.org&g=
t; </div>
<div>Date: 5/1/18 5:25 AM (GMT-08:00) </div>
<div>To: Benjamin Kaduk &lt;bkaduk=3D40akamai.com@dmarc.ietf.org&gt;, Prave=
en Balasubramanian &lt;pravb=3D40microsoft.com@dmarc.ietf.org&gt;
</div>
<div>Cc: IETF QUIC WG &lt;quic@ietf.org&gt; </div>
<div>Subject: Re: Getting to consensus on packet number encryption </div>
<div><br>
</div>
</div>
<font size=3D"2"><span style=3D"font-size:11pt;">
<div class=3D"PlainText">&nbsp;&nbsp;&nbsp; &gt; I disagree that we need an=
y more data for not doing PNE in the datacenter. Why would we add an extra =
encrypt-decrypt step for no obvious benefit?<br>
<br>
I am concerned that people will mis-interpret the meaning of a datacenter, =
and think that a bunch of servers, or even a rack, in an open colo space is=
 a &quot;datacenter.&quot;&nbsp; Computers keep getting faster.
<br>
<br>
</div>
</span></font>
</body>
</html>

--_000_BY2PR15MB07757EAB6A818F1D8D8CCED9CD810BY2PR15MB0775namp_--


From nobody Tue May  1 08:47:43 2018
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BB68212E8AE for <quic@ietfa.amsl.com>; Tue,  1 May 2018 08:47:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 V2XE-VY0Jz4X for <quic@ietfa.amsl.com>; Tue,  1 May 2018 08:47:40 -0700 (PDT)
Received: from mail-yw0-x231.google.com (mail-yw0-x231.google.com [IPv6:2607:f8b0:4002:c05::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3980412DA70 for <quic@ietf.org>; Tue,  1 May 2018 08:47:40 -0700 (PDT)
Received: by mail-yw0-x231.google.com with SMTP id u83-v6so3653657ywc.4 for <quic@ietf.org>; Tue, 01 May 2018 08:47:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=NFz6QjGUF8b4FnTmChXGPpSiPm/ku9uMUI73nBMyqPo=; b=r5PrxJeItS+fWlz4BBP9fhhKb76aTcrRUOgtonyLCxvGXSPkHIVNEXAFF7XwSi4doR 0nWMG3ltsoyhvG7qg6HJyN/El/PJQvpiJFTshkM6Wyt65Se5pSQUYzWPO0eSTOJ05eq3 /FZ/Ef3a8TfKggG5zOIQPKfW/1Ssng4Noenz+sUERBhe2TpOF5UCtRgx+sMHj5Fj+Hbq BC+k0VXip40YeT/Z9W+nyyHPfnwe0hbJ6ZDJVMl4nuiCkKdmT5MvICCqP7VCF7DOUhNE eahzyZ5glx98JCfvdQ4trt8nKh1rESWIlE21WmXziJZn+LFxR2QILk+bwgCPLWy3PwUh vj8Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=NFz6QjGUF8b4FnTmChXGPpSiPm/ku9uMUI73nBMyqPo=; b=irOoAeAQNex79tCYMb+LpWRmlH4OmuSz68hhNS1cXfyE4v60dqGg2puz5i94HCN8wG 6zaDnR5uk8Nqwt4puoU5xVw5PqNdWDedT4mL9dY9zwOtuaKaZL5n0LGy4Lcb+wkNE+rL ljpEfkZChJfXwapnFonoIf071FY78Ke59j/wte7afObOZ+yjXmE+ep8LZPktV0KSs9ar GLd2IbB4fOz+usvqTCNrK96LYE8LZxfJoEud+dY4JG6ZbxD+AMjMccwDt0OarK6YxJ8l AdMQ0wzYICiPrfVDFW1M/J4lauIy9OBE5B/WMTTBW7BUPKMHmS9BM5uYmFO6b1m26+jM YiFw==
X-Gm-Message-State: ALQs6tBm6X8Q6WYr1B2aPRqgpy3Z2CAiZv4YdcjN/H0sLUiVfgcDd2IM YAEyKCk/Qd65DF02x9M4U8ssA580ykbAh7nCZCkH9w==
X-Google-Smtp-Source: AB8JxZp5/CDUEpUFATOaCbcDHa76GTMElMsvGqSEnkU4rpS2PrY4I1e364EY7n22somLiLWDHLxVYlGn37+Jfx+BKFM=
X-Received: by 2002:a81:788b:: with SMTP id t133-v6mr8282942ywc.19.1525189659189;  Tue, 01 May 2018 08:47:39 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a25:d014:0:0:0:0:0 with HTTP; Tue, 1 May 2018 08:47:38 -0700 (PDT)
In-Reply-To: <20180501121906.GA5742@akamai.com>
References: <CANatvzwCYrOZULG3iVmDFp97nr=M5=Gufo8TZjOGQVFUpsn0bQ@mail.gmail.com> <CAAedzxqDcPXJUE83KVnDiU23PvqDcTCrc6rRMw09FexjJA-Y6Q@mail.gmail.com> <CANatvzwjYE6EdvFtOXJMVQnutbVQ4YY+=XsQFzKwHzqWzZ4U+w@mail.gmail.com> <d32ade7b56bf4651952659307c08893b@usma1ex-dag1mb5.msg.corp.akamai.com> <CANatvzwHtCn8rLB8npf3i7PGyYZhVDRd2uojh5hv3uxtFPEsSA@mail.gmail.com> <58447D8E-782C-431C-8FC3-71124B10A047@trammell.ch> <CACpbDcdfF9w3qqrH1eB0sGU_4vheD9aMP5EXnp1o3Y19N19NUg@mail.gmail.com> <e8b4931a-3931-5b8d-8dad-3ca1939d5542@huitema.net> <CAKcm_gPaj3o-VTdA_0+Kk+nTcVJrYcs_BMyOiDGXKub3gB=GLg@mail.gmail.com> <MWHPR21MB063869878060E850137210FEB6820@MWHPR21MB0638.namprd21.prod.outlook.com> <20180501121906.GA5742@akamai.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 1 May 2018 10:47:38 -0500
Message-ID: <CAKKJt-dgPP8FbP0=tEpm5vf99C9qXKYRWN0PY3dzfphqdBGypw@mail.gmail.com>
Subject: Re: Getting to consensus on packet number encryption
To: Benjamin Kaduk <bkaduk=40akamai.com@dmarc.ietf.org>
Cc: Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d9e713056b26e36f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/xzZij3eekJ5d2ZDhqDbYA0Ct_Aw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2018 15:47:43 -0000

--000000000000d9e713056b26e36f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

FWIW,

On Tue, May 1, 2018 at 7:19 AM, Benjamin Kaduk <
bkaduk=3D40akamai.com@dmarc.ietf.org> wrote:

> On Mon, Apr 30, 2018 at 09:55:31PM +0000, Praveen Balasubramanian wrote:
> > I disagree that we need any more data for not doing PNE in the
> datacenter. Why would we add an extra encrypt-decrypt step for no obvious
> benefit? The cost of this operation will keep magnifying as UDP performan=
ce
> improves. We have several optimizations planned for UDP, but short of
> hardware offload, none for crypto =E2=80=93 this is an important trend to=
 account
> for performance wise. For short packets like ACKs an extra encrypt decryp=
t
> step can become a large fraction of CPU cost over time.
>
> There is benefit in uniformity and simplicity of implementation; I conced=
e
> that
> the claimed potential benefits about the middlebox ecosystem are
> speculative,
> but the simplicity seems clear to me.
>
> With respect to the cost of the crypto, yes we have some numbers, but
> AFAICT we
> don't have a great view for how they will fit into the broader picture as
> implementations mature, so to some extent the estimate of the magnitude o=
f
> growing cost of crypto is also a speculative position.  (Also, who is the
> "we"
> that has several optimizations planned?)
>
> In other words, how do we know this is not premature optimization?
> Shouldn't
> we wait until we have actual performance numbers before doing lots of
> optimization?


I can't speak to whether this optimization is premature, but I do suspect
that if more people were looking at more actual performance numbers, this
conversation might converge more quickly ...


> I was under the impression that QUIC versions were going to be
> lightweight, so putting out v1 with mandatory PNE would not preclude
> quickly
> following with a V3 that adapts to any discovered performance concerns,
> whether
> for datacenter usage or otherwise.
>

Yeah, about that ...

I've been asking in a few places - most recently, at
https://datatracker.ietf.org/meeting/101/materials/minutes-101-quic-00.html
- about version appearance rates, and I haven't heard answers that sounded
like the working group had strong agreement that versions were going to
roll out pretty quickly. For example, from that conversation, I got

Spencer (as AD): *[deleted first three points, to get to] *4. (as Spencer)
don't have a good feeling about version negotiating and how much we might
roll them.

mnot: not going to wait 5 years for v2.


So, the chairs can correct me (and should, and they have before on other
topics), but I think I've heard a lot of "we don't have to get everything
perfect in QUICv1, because there will be other versions", and not a lot of
"and the other versions will appear pretty quickly".

I don't know what all the participants are thinking, but that's what the
people who are talking have been saying to me.

IMO, of course.

Spencer, as individual


> -Ben
>
>

--000000000000d9e713056b26e36f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">FWIW,=C2=A0<div class=3D"gmail_extra"><br><div class=3D"gm=
ail_quote">On Tue, May 1, 2018 at 7:19 AM, Benjamin Kaduk <span dir=3D"ltr"=
>&lt;<a href=3D"mailto:bkaduk=3D40akamai.com@dmarc.ietf.org" target=3D"_bla=
nk">bkaduk=3D40akamai.com@dmarc.ietf.org</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px =
solid rgb(204,204,204);padding-left:1ex"><span class=3D"gmail-">On Mon, Apr=
 30, 2018 at 09:55:31PM +0000, Praveen Balasubramanian wrote:<br>
&gt; I disagree that we need any more data for not doing PNE in the datacen=
ter. Why would we add an extra encrypt-decrypt step for no obvious benefit?=
 The cost of this operation will keep magnifying as UDP performance improve=
s. We have several optimizations planned for UDP, but short of hardware off=
load, none for crypto =E2=80=93 this is an important trend to account for p=
erformance wise. For short packets like ACKs an extra encrypt decrypt step =
can become a large fraction of CPU cost over time.<br>
<br>
</span>There is benefit in uniformity and simplicity of implementation; I c=
oncede that<br>
the claimed potential benefits about the middlebox ecosystem are speculativ=
e,<br>
but the simplicity seems clear to me.<br>
<br>
With respect to the cost of the crypto, yes we have some numbers, but AFAIC=
T we<br>
don&#39;t have a great view for how they will fit into the broader picture =
as<br>
implementations mature, so to some extent the estimate of the magnitude of<=
br>
growing cost of crypto is also a speculative position.=C2=A0 (Also, who is =
the &quot;we&quot;<br>
that has several optimizations planned?)<br>
<br>
In other words, how do we know this is not premature optimization?=C2=A0 Sh=
ouldn&#39;t<br>
we wait until we have actual performance numbers before doing lots of<br>
optimization?=C2=A0 </blockquote><div><br></div><div>I can&#39;t speak to w=
hether this optimization is premature, but I do suspect that if more people=
 were looking at more actual performance numbers, this conversation might c=
onverge more quickly ...=C2=A0</div><div>=C2=A0</div><blockquote class=3D"g=
mail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204=
,204,204);padding-left:1ex">I was under the impression that QUIC versions w=
ere going to be<br>
lightweight, so putting out v1 with mandatory PNE would not preclude quickl=
y<br>
following with a V3 that adapts to any discovered performance concerns, whe=
ther<br>
for datacenter usage or otherwise.<br></blockquote><div><br></div><div>Yeah=
, about that ...=C2=A0</div><div><br></div><div>I&#39;ve been asking in a f=
ew places - most recently, at=C2=A0<a href=3D"https://datatracker.ietf.org/=
meeting/101/materials/minutes-101-quic-00.html">https://datatracker.ietf.or=
g/meeting/101/materials/minutes-101-quic-00.html</a> - about version appear=
ance rates, and I haven&#39;t heard answers that sounded like the working g=
roup had strong agreement that versions were going to roll out pretty quick=
ly. For example, from that conversation, I got=C2=A0</div><div><br></div></=
div></div><blockquote style=3D"margin:0px 0px 0px 40px;border:none;padding:=
0px"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div><div>Spence=
r (as AD): <i>[deleted first three points, to get to] </i>4. (as Spencer) d=
on&#39;t have a good feeling about version negotiating and how much we migh=
t roll them.</div><div><br></div><div>mnot: not going to wait 5 years for v=
2.</div></div></div></div></blockquote><div><br></div>So, the chairs can co=
rrect me (and should, and they have before on other topics), but I think I&=
#39;ve heard a lot of &quot;we don&#39;t have to get everything perfect in =
QUICv1, because there will be other versions&quot;, and not a lot of &quot;=
and the other versions will appear pretty quickly&quot;.=C2=A0<div><br></di=
v><div>I don&#39;t know what all the participants are thinking, but that&#3=
9;s what the people who are talking have been saying to me.<br><div><br></d=
iv><div>IMO, of course.=C2=A0</div><div><br></div><div>Spencer, as individu=
al=C2=A0<br><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div>=C2=
=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex">-Ben<br>
<br>
</blockquote></div><br></div></div></div></div>

--000000000000d9e713056b26e36f--


From nobody Tue May  1 08:55:40 2018
Return-Path: <ted.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 405D512E052 for <quic@ietfa.amsl.com>; Tue,  1 May 2018 08:55:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 5DtXHdTTWqlK for <quic@ietfa.amsl.com>; Tue,  1 May 2018 08:55:32 -0700 (PDT)
Received: from mail-ot0-x236.google.com (mail-ot0-x236.google.com [IPv6:2607:f8b0:4003:c0f::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EA3312DA4C for <quic@ietf.org>; Tue,  1 May 2018 08:55:32 -0700 (PDT)
Received: by mail-ot0-x236.google.com with SMTP id l13-v6so13365936otk.9 for <quic@ietf.org>; Tue, 01 May 2018 08:55:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=FfHpVB+epDr86TdlzajDQw+g26kUu22NoRo9Yq+uAZE=; b=VRiwlb+uKyKuRaTSRowOajgG4MtP0Y90EUg8cR9IEgpr4aiicw3XvzlwgvrGOHZWK6 3qijLGh3VciYM/b+zYSfB+oGDV8qdGEcxmXuNiBUks6w6ZoYWQ+7vtBBK+ei2mfIA4A8 B5vbx80BlbSKK7rjhBfBdGs7PPPqSGI9SFQHj75FtUZ1SXh7/h9WP88y7wQclrdq8GNW simEjk82yNGzTcPp+FekefiaA7XrEiRHSbwNElZnY9CWAkubT08/v/sA6ElWXfx9icXk v8B9F6nnuolfBgkxGfjyo0qni47D1ktLdlfjKdY7DLYpgdcVyJysJ4+2HEX+BefMGOrb ZuSw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=FfHpVB+epDr86TdlzajDQw+g26kUu22NoRo9Yq+uAZE=; b=IZpADnUM4NhO8JsJvR+lg56KRsDoe2+66+NbA7aWSN17FrptYwywJ5E/X/s3fY+8wW dYlzVY3+sXDbMemZ4hvRK8LQgnm5Raq/0/c+cE13mDkOZ2SdzgZtN+YnxlGtmASqw0/Q yosev71CavgRO6jZWFAvkmpblWH97D5r5JUGUgpzcD/KFsjbzxTiTa0UC9VJpKmF4UXl e/Ec4R0NnkpGa8MXI2sUuI7zh67PEHuhTGyDOvMeoWG+aTrGHiOeoHuEJEorrA8sCEPM TcFy0kcL4IQN2k1eWkmR3vSSa8l6/LNfmA0A3QTNwnG/Mh4Yd/meHxU6h/Cd9jkZlu+d rg5w==
X-Gm-Message-State: ALQs6tAwPVl8yAkdcHd5urmExi6T286C7sQSTWGZrtSBSeDBgBBqEKya jyHAx+LJC7VFbIAnAuwU8YNoYLDJuGeQPzn7fyk=
X-Google-Smtp-Source: AB8JxZpGsDARP1LJF8i1kIb+bikCiqKu8VfHsTSY+AvEp03NbvHrnr8k6Ytz6Jg/CErovXu9aTOKeUuOPuhvD5ugslc=
X-Received: by 2002:a9d:17c2:: with SMTP id j60-v6mr705066otj.329.1525190131444;  Tue, 01 May 2018 08:55:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.67.153 with HTTP; Tue, 1 May 2018 08:55:00 -0700 (PDT)
In-Reply-To: <BY2PR15MB07757EAB6A818F1D8D8CCED9CD810@BY2PR15MB0775.namprd15.prod.outlook.com>
References: <CANatvzwCYrOZULG3iVmDFp97nr=M5=Gufo8TZjOGQVFUpsn0bQ@mail.gmail.com> <CAAedzxqDcPXJUE83KVnDiU23PvqDcTCrc6rRMw09FexjJA-Y6Q@mail.gmail.com> <CANatvzwjYE6EdvFtOXJMVQnutbVQ4YY+=XsQFzKwHzqWzZ4U+w@mail.gmail.com> <d32ade7b56bf4651952659307c08893b@usma1ex-dag1mb5.msg.corp.akamai.com> <CANatvzwHtCn8rLB8npf3i7PGyYZhVDRd2uojh5hv3uxtFPEsSA@mail.gmail.com> <58447D8E-782C-431C-8FC3-71124B10A047@trammell.ch> <CACpbDcdfF9w3qqrH1eB0sGU_4vheD9aMP5EXnp1o3Y19N19NUg@mail.gmail.com> <e8b4931a-3931-5b8d-8dad-3ca1939d5542@huitema.net> <CAKcm_gPaj3o-VTdA_0+Kk+nTcVJrYcs_BMyOiDGXKub3gB=GLg@mail.gmail.com> <MWHPR21MB063869878060E850137210FEB6820@MWHPR21MB0638.namprd21.prod.outlook.com> <20180501121906.GA5742@akamai.com> <F63059EA-BA14-4886-A4FB-AA5F04AC164B@akamai.com> <BY2PR15MB07757EAB6A818F1D8D8CCED9CD810@BY2PR15MB0775.namprd15.prod.outlook.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 1 May 2018 08:55:00 -0700
Message-ID: <CA+9kkMCpxve3CKhQk45YKbvyOyQ6kvzyhpJhrTq1UM-QM+ms2Q@mail.gmail.com>
Subject: Re: Getting to consensus on packet number encryption
To: Roberto Peon <fenix@fb.com>
Cc: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>,  Benjamin Kaduk <bkaduk=40akamai.com@dmarc.ietf.org>,  Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000fff076056b26ff45"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Cu4ZdJ7HSEO6iCj8Fqg0HgWhIQc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2018 15:55:39 -0000

--000000000000fff076056b26ff45
Content-Type: text/plain; charset="UTF-8"

On Tue, May 1, 2018 at 8:13 AM, Roberto Peon <fenix@fb.com> wrote:

> Also, Prism.
>
> -=R
>
>
>
That's a little more succinct than I would be, but yes.  How does an
application know that the flow it is initiating will traverse a topology
that is deemed to be within a controlled environment?  You can say
"configuration" but I fear it will turn up on a post-it
<https://i.kinja-img.com/gawker-media/image/upload/s--Edu6LPu9--/c_scale,f_auto,fl_progressive,q_80,w_800/194thbtyencs0jpg.jpg>if
you do.  Loads shift, resources move, and suddenly you find that host which
used to be in the same rack, being down, has load-shifted to the next
instance,  in a datacenter 500 miles away across a very different network.

Many modern deployments are also in someone else's data center, so saying
"Data center networks" doesn't say much about why you're trusting the
network inside.

Ted


> Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
>
>
> -------- Original message --------
> From: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
> Date: 5/1/18 5:25 AM (GMT-08:00)
> To: Benjamin Kaduk <bkaduk=40akamai.com@dmarc.ietf.org>, Praveen
> Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>
> Cc: IETF QUIC WG <quic@ietf.org>
> Subject: Re: Getting to consensus on packet number encryption
>
>     > I disagree that we need any more data for not doing PNE in the
> datacenter. Why would we add an extra encrypt-decrypt step for no obvious
> benefit?
>
> I am concerned that people will mis-interpret the meaning of a datacenter,
> and think that a bunch of servers, or even a rack, in an open colo space is
> a "datacenter."  Computers keep getting faster.
>
>

--000000000000fff076056b26ff45
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, May 1, 2018 at 8:13 AM, Roberto Peon <span dir=3D"=
ltr">&lt;<a href=3D"mailto:fenix@fb.com" target=3D"_blank">fenix@fb.com</a>=
&gt;</span> wrote:<br><div class=3D"gmail_extra"><div class=3D"gmail_quote"=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex">





<div>
<div>
<div>Also, Prism.=C2=A0</div>
<div><br>
</div>
<div>-=3DR=C2=A0</div>
<div><br>
</div>
<div><br></div></div></div></blockquote><div><br></div><div>That&#39;s a li=
ttle more succinct than I would be, but yes.=C2=A0 How does an application =
know that the flow it is initiating will traverse a topology that is deemed=
 to be within a controlled environment?=C2=A0 You can say &quot;configurati=
on&quot; but I fear it will turn <a href=3D"https://i.kinja-img.com/gawker-=
media/image/upload/s--Edu6LPu9--/c_scale,f_auto,fl_progressive,q_80,w_800/1=
94thbtyencs0jpg.jpg">up on a post-it=C2=A0 </a>if you do.=C2=A0 Loads shift=
, resources move, and suddenly you find that host which used to be in the s=
ame rack, being down, has load-shifted to the next instance,=C2=A0 in a dat=
acenter 500 miles away across a very different network.=C2=A0 <br><br>Many =
modern deployments are also in someone else&#39;s data center, so saying &q=
uot;Data center networks&quot; doesn&#39;t say much about why you&#39;re tr=
usting the network inside.<br><br></div><div>Ted<br></div><div>=C2=A0</div>=
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex"><div><div><div>
</div>
<div id=3D"m_-3775552097582664562x_composer_signature">
<div dir=3D"auto" style=3D"font-size:85%;color:#575757">Sent via the Samsun=
g Galaxy S7, an AT&amp;T 4G LTE smartphone</div>
</div><span class=3D"">
<div><br>
</div>
<div><br>
</div>
<div>-------- Original message --------</div>
<div>From: &quot;Salz, Rich&quot; &lt;rsalz=3D<a href=3D"mailto:40akamai.co=
m@dmarc.ietf.org" target=3D"_blank">40akamai.com@dmarc.<wbr>ietf.org</a>&gt=
; </div>
<div>Date: 5/1/18 5:25 AM (GMT-08:00) </div>
<div>To: Benjamin Kaduk &lt;bkaduk=3D<a href=3D"mailto:40akamai.com@dmarc.i=
etf.org" target=3D"_blank">40akamai.com@dmarc.<wbr>ietf.org</a>&gt;, Pravee=
n Balasubramanian &lt;pravb=3D<a href=3D"mailto:40microsoft.com@dmarc.ietf.=
org" target=3D"_blank">40microsoft.com@dmarc.<wbr>ietf.org</a>&gt;
</div>
<div>Cc: IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank=
">quic@ietf.org</a>&gt; </div>
<div>Subject: Re: Getting to consensus on packet number encryption </div>
<div><br>
</div>
</span></div><div><div class=3D"h5">
<font size=3D"2"><span style=3D"font-size:11pt">
<div class=3D"m_-3775552097582664562PlainText">=C2=A0=C2=A0=C2=A0 &gt; I di=
sagree that we need any more data for not doing PNE in the datacenter. Why =
would we add an extra encrypt-decrypt step for no obvious benefit?<br>
<br>
I am concerned that people will mis-interpret the meaning of a datacenter, =
and think that a bunch of servers, or even a rack, in an open colo space is=
 a &quot;datacenter.&quot;=C2=A0 Computers keep getting faster.
<br>
<br>
</div>
</span></font>
</div></div></div>

</blockquote></div><br></div></div>

--000000000000fff076056b26ff45--


From nobody Tue May  1 09:34:35 2018
Return-Path: <pravb@microsoft.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 752A312DA6E for <quic@ietfa.amsl.com>; Tue,  1 May 2018 09:34:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level: 
X-Spam-Status: No, score=-2.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 f9UtZ852xnek for <quic@ietfa.amsl.com>; Tue,  1 May 2018 09:34:29 -0700 (PDT)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0092.outbound.protection.outlook.com [104.47.40.92]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C945F12DA4F for <quic@ietf.org>; Tue,  1 May 2018 09:34:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=80hOVRNXvzm32EgbqVmUSAabASfYpnzXDsmdKoNFZVk=; b=jVnbAtd7o0K2CEJmQdfS95B+kMPC/a/rklaDT3MOrdHZ2mnugLsNp5D2sZ9+iwBL55hfH2vDHCzgySXQRe9Gcpnd0wSrt1JQXeyrraiXtmQQXRf5sgH2pudc5Tf/hi2c6koIXw5/SpezP3vpkn/YF4WYr90EaISUiu6+oSdws5o=
Received: from MWHPR21MB0638.namprd21.prod.outlook.com (10.175.141.139) by MWHPR21MB0160.namprd21.prod.outlook.com (10.173.52.18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.735.5; Tue, 1 May 2018 16:34:28 +0000
Received: from MWHPR21MB0638.namprd21.prod.outlook.com ([fe80::6d48:f7af:d267:2021]) by MWHPR21MB0638.namprd21.prod.outlook.com ([fe80::6d48:f7af:d267:2021%7]) with mapi id 15.20.0735.006; Tue, 1 May 2018 16:34:28 +0000
From: Praveen Balasubramanian <pravb@microsoft.com>
To: Ted Hardie <ted.ietf@gmail.com>, Roberto Peon <fenix@fb.com>
CC: "Salz, Rich" <rsalz@akamai.com>, Benjamin Kaduk <bkaduk@akamai.com>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Getting to consensus on packet number encryption
Thread-Topic: Getting to consensus on packet number encryption
Thread-Index: AQHTy9GYaiUVNrU6h0aiyBQtEo3l9KPwZ0sAgAC4ugCAAARcAIAAFTbwgAALYgCAAAAgYIAAEcIAgACR+YCAB09lAIAFXyIAgAVK+oCAAJlSAIABxdSAgACOHICAB/EyAIACo7YAgACiMICAAADPgIAAIs8AgAAm/YCAABExgIAABpMAgAAK5wCAAPIgAIAA5wcAgACzcYCAAHHMgIAEe1cAgAABEACAABL8QIAA89MAgAABeQCAAC8kAIAAC7UAgAAHZZA=
Date: Tue, 1 May 2018 16:34:28 +0000
Message-ID: <MWHPR21MB063883F004E055CC91C153EBB6810@MWHPR21MB0638.namprd21.prod.outlook.com>
References: <CANatvzwCYrOZULG3iVmDFp97nr=M5=Gufo8TZjOGQVFUpsn0bQ@mail.gmail.com> <CAAedzxqDcPXJUE83KVnDiU23PvqDcTCrc6rRMw09FexjJA-Y6Q@mail.gmail.com> <CANatvzwjYE6EdvFtOXJMVQnutbVQ4YY+=XsQFzKwHzqWzZ4U+w@mail.gmail.com> <d32ade7b56bf4651952659307c08893b@usma1ex-dag1mb5.msg.corp.akamai.com> <CANatvzwHtCn8rLB8npf3i7PGyYZhVDRd2uojh5hv3uxtFPEsSA@mail.gmail.com> <58447D8E-782C-431C-8FC3-71124B10A047@trammell.ch> <CACpbDcdfF9w3qqrH1eB0sGU_4vheD9aMP5EXnp1o3Y19N19NUg@mail.gmail.com> <e8b4931a-3931-5b8d-8dad-3ca1939d5542@huitema.net> <CAKcm_gPaj3o-VTdA_0+Kk+nTcVJrYcs_BMyOiDGXKub3gB=GLg@mail.gmail.com> <MWHPR21MB063869878060E850137210FEB6820@MWHPR21MB0638.namprd21.prod.outlook.com> <20180501121906.GA5742@akamai.com> <F63059EA-BA14-4886-A4FB-AA5F04AC164B@akamai.com> <BY2PR15MB07757EAB6A818F1D8D8CCED9CD810@BY2PR15MB0775.namprd15.prod.outlook.com> <CA+9kkMCpxve3CKhQk45YKbvyOyQ6kvzyhpJhrTq1UM-QM+ms2Q@mail.gmail.com>
In-Reply-To: <CA+9kkMCpxve3CKhQk45YKbvyOyQ6kvzyhpJhrTq1UM-QM+ms2Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e8:7::316]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MWHPR21MB0160; 7:XN/LGoOK17O/2Ho7MdQqUwoNN45+rdA4gyS9bRB4t4v08CO2c5Bi3gXvxi3kqVtk4I3yBKnw+vdcHWVA2iZNPavUz+RbBscCddVjY+N0T6GlT/rDUKr8AqP7+P0QkYdcxSuAdtKlu4p6Zwgy0c7aCIk1fGisC+1BdXEn2g2wC+xTWrFehjHyz5SFaYDxbw2vu08s13LdJnGmJc5Dj2Ix5XTbyI9rV0MW5mQpKiHnAJ6v8K0OZZP6H/54jB2kuU4D; 20:by9yEJP23MFrGEueEuCBgopA0FticKMbMYeQ9pWXSoFyj0X6YLhi5+4wyKJYGia4YKalhAwNA8mp9oaix5DGcXjoyQ/pY05ZvSGuNG3pfHVSDp0jNG8TNgRMyQaolX2p9Cf94dmhgisYm5eT6wfVm3CGMlrfI68gmCMpW786B4E=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(2017052603328)(7193020); SRVR:MWHPR21MB0160; 
x-ms-traffictypediagnostic: MWHPR21MB0160:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pravb@microsoft.com; 
x-microsoft-antispam-prvs: <MWHPR21MB0160F54548D4B3B305E10B9EB6810@MWHPR21MB0160.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(89211679590171)(189930954265078)(85827821059158)(67672495146484)(100405760836317)(219752817060721)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3231254)(2018427008)(944501410)(52105095)(3002001)(10201501046)(93006095)(93001095)(6055026)(6041310)(20161123562045)(20161123560045)(20161123558120)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(6072148)(201708071742011); SRVR:MWHPR21MB0160; BCL:0; PCL:0; RULEID:; SRVR:MWHPR21MB0160; 
x-forefront-prvs: 06592CCE58
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(39860400002)(366004)(39380400002)(346002)(376002)(189003)(199004)(3280700002)(102836004)(476003)(11346002)(68736007)(2906002)(186003)(54906003)(3660700001)(46003)(316002)(110136005)(6506007)(86362001)(53546011)(59450400001)(6116002)(10290500003)(8936002)(99286004)(74316002)(22452003)(81166006)(81156014)(446003)(93886005)(486006)(5660300001)(7696005)(19609705001)(478600001)(790700001)(76176011)(6246003)(33656002)(53936002)(8990500004)(54896002)(236005)(6306002)(4326008)(229853002)(25786009)(2900100001)(9686003)(106356001)(10090500001)(8676002)(97736004)(105586002)(606006)(14454004)(7736002)(86612001)(6436002)(5250100002)(55016002)(39060400002); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR21MB0160; H:MWHPR21MB0638.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: psfL/PnSuQTGNsvtFh+zd53rYbniQU3rx/N6TqADuqJxKFAWRcUKwp748/7rIQy/TGhRqiT+HLKvTbWxegaKwbpDAufpOtx3wZvsm97qcPCl8gco6lkfVrbIVaHMrrGzNKhwe9a+tvxDW45m+MNsiL8Q9sHDwC+N8E4PZh73LmLT+jl/L4QITB0GzxF6i70c
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_MWHPR21MB063883F004E055CC91C153EBB6810MWHPR21MB0638namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 04c44440-719e-4fa2-4bbf-08d5af8168cb
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 04c44440-719e-4fa2-4bbf-08d5af8168cb
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 May 2018 16:34:28.4607 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR21MB0160
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/QqEr_iLbYuvHlbMgRNe7dQccqnA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2018 16:34:33 -0000

--_000_MWHPR21MB063883F004E055CC91C153EBB6810MWHPR21MB0638namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

VGhpcyBpcyBub3QgYWJvdXQgcHV0dGluZyBwbGFpbnRleHQgZGF0YSBvbiB0aGUgbmV0d29yaywg
dGhpcyBpcyBhYm91dCBub3QgYWRkaW5nIFBORSB3aGljaCBpcyBpbnRlbmRlZCBmb3IgcHJldmVu
dGluZyBvc3NpZmljYXRpb24uIFNvIEkgZG9u4oCZdCB1bmRlcnN0YW5kIHdoYXQgdGhlIHRydXN0
IGlzc3VlIGJlaW5nIHJlZmVycmVkIHRvIGlzIGluIGNhc2Ugb2YgdGhlIHJhcmUgbWlzY29uZmln
Lg0KDQpXaXRoaW4gYSBEQyBzZXZlcmFsIHRoaW5ncyBhcmUgZGlmZmVyZW50IOKAkyB0aGUgZGVw
bG95bWVudCBtYXkgbmVlZCBkaWZmZXJlbnQgY29uZ2VzdGlvbiBjb250cm9sIGxpa2UgRENUQ1As
IGRpZmZlcmVudCBzZXR0aW5ncyBmb3IgdmFyaW91cyB0cmFuc3BvcnQgcGFyYW1ldGVycyAobGlr
ZSBtaW5ydG8gYW5kIG1heCBBQ0sgZGVsYXkpLCBsYXJnZXIgZmxvdyBjb250cm9sIHdpbmRvdyBl
dGMuIFRoaXMgaXMgdHJ1ZSBmb3IgVENQIHRvZGF5LiBUaGUgb3V0IG9mIGJveCBkZWZhdWx0IHVz
ZXMgdGhlIGhhbmRzaGFrZSBSVFQgdG8gbWFrZSBhIGRldGVybWluYXRpb24gb2Ygd2hhdOKAmXMg
aW50cmEtREMgYnV0IHRoZXJlIGlzIHJpY2ggY29uZmlndXJhdGlvbiB0byBvdmVycmlkZSB0aGUg
ZGVmYXVsdCBhbmQgc2V0IGl0IGJhc2VkIG9uIDQtdHVwbGUgZmlsdGVycy4NCg0KQW5kIHRoZXJl
IHdvcmtsb2FkcyBsaWtlIGNsb3VkIHN0b3JhZ2UgYW5kIGxpdmUgbWlncmF0aW9uIHRoYXQgYXJl
IGJ5IHZpcnR1ZSBvZiBkZXBsb3ltZW50IGludHJhLURDLiBUaGVzZSBjYW5ub3QgYmUgbG9hZCBz
aGlmdGVkIGFzIHRoZXkgdXNlIHByaXZhdGUgSVAgYWRkcmVzcyBzcGFjZS4NCg0KRnJvbTogVGVk
IEhhcmRpZSBbbWFpbHRvOnRlZC5pZXRmQGdtYWlsLmNvbV0NClNlbnQ6IFR1ZXNkYXksIE1heSAx
LCAyMDE4IDg6NTUgQU0NClRvOiBSb2JlcnRvIFBlb24gPGZlbml4QGZiLmNvbT4NCkNjOiBTYWx6
LCBSaWNoIDxyc2FsekBha2FtYWkuY29tPjsgQmVuamFtaW4gS2FkdWsgPGJrYWR1a0Bha2FtYWku
Y29tPjsgUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gPHByYXZiQG1pY3Jvc29mdC5jb20+OyBJRVRG
IFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogR2V0dGluZyB0byBjb25zZW5z
dXMgb24gcGFja2V0IG51bWJlciBlbmNyeXB0aW9uDQoNCk9uIFR1ZSwgTWF5IDEsIDIwMTggYXQg
ODoxMyBBTSwgUm9iZXJ0byBQZW9uIDxmZW5peEBmYi5jb208bWFpbHRvOmZlbml4QGZiLmNvbT4+
IHdyb3RlOg0KQWxzbywgUHJpc20uDQoNCi09Ug0KDQoNCg0KVGhhdCdzIGEgbGl0dGxlIG1vcmUg
c3VjY2luY3QgdGhhbiBJIHdvdWxkIGJlLCBidXQgeWVzLiAgSG93IGRvZXMgYW4gYXBwbGljYXRp
b24ga25vdyB0aGF0IHRoZSBmbG93IGl0IGlzIGluaXRpYXRpbmcgd2lsbCB0cmF2ZXJzZSBhIHRv
cG9sb2d5IHRoYXQgaXMgZGVlbWVkIHRvIGJlIHdpdGhpbiBhIGNvbnRyb2xsZWQgZW52aXJvbm1l
bnQ/ICBZb3UgY2FuIHNheSAiY29uZmlndXJhdGlvbiIgYnV0IEkgZmVhciBpdCB3aWxsIHR1cm4g
dXAgb24gYSBwb3N0LWl0ICA8aHR0cHM6Ly9uYTAxLnNhZmVsaW5rcy5wcm90ZWN0aW9uLm91dGxv
b2suY29tLz91cmw9aHR0cHMlM0ElMkYlMkZpLmtpbmphLWltZy5jb20lMkZnYXdrZXItbWVkaWEl
MkZpbWFnZSUyRnVwbG9hZCUyRnMtLUVkdTZMUHU5LS0lMkZjX3NjYWxlJTJDZl9hdXRvJTJDZmxf
cHJvZ3Jlc3NpdmUlMkNxXzgwJTJDd184MDAlMkYxOTR0aGJ0eWVuY3MwanBnLmpwZyZkYXRhPTAy
JTdDMDElN0NwcmF2YiU0MG1pY3Jvc29mdC5jb20lN0M0ZGE0NGU4YWMxZGY0NzA4YWQ4ODA4ZDVh
ZjdiZmNhOCU3QzcyZjk4OGJmODZmMTQxYWY5MWFiMmQ3Y2QwMTFkYjQ3JTdDMSU3QzElN0M2MzY2
MDc4Njk0MTEyNTg5NzYmc2RhdGE9UHJvbFNIa2JGMlNnTUgzcWRRTiUyQlpGb2tYdnNFQmYlMkYz
bzlNYVVuaWwwZzglM0QmcmVzZXJ2ZWQ9MD4gaWYgeW91IGRvLiAgTG9hZHMgc2hpZnQsIHJlc291
cmNlcyBtb3ZlLCBhbmQgc3VkZGVubHkgeW91IGZpbmQgdGhhdCBob3N0IHdoaWNoIHVzZWQgdG8g
YmUgaW4gdGhlIHNhbWUgcmFjaywgYmVpbmcgZG93biwgaGFzIGxvYWQtc2hpZnRlZCB0byB0aGUg
bmV4dCBpbnN0YW5jZSwgIGluIGEgZGF0YWNlbnRlciA1MDAgbWlsZXMgYXdheSBhY3Jvc3MgYSB2
ZXJ5IGRpZmZlcmVudCBuZXR3b3JrLg0KDQpNYW55IG1vZGVybiBkZXBsb3ltZW50cyBhcmUgYWxz
byBpbiBzb21lb25lIGVsc2UncyBkYXRhIGNlbnRlciwgc28gc2F5aW5nICJEYXRhIGNlbnRlciBu
ZXR3b3JrcyIgZG9lc24ndCBzYXkgbXVjaCBhYm91dCB3aHkgeW91J3JlIHRydXN0aW5nIHRoZSBu
ZXR3b3JrIGluc2lkZS4NClRlZA0KDQpTZW50IHZpYSB0aGUgU2Ftc3VuZyBHYWxheHkgUzcsIGFu
IEFUJlQgNEcgTFRFIHNtYXJ0cGhvbmUNCg0KDQotLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0t
LS0tLS0tDQpGcm9tOiAiU2FseiwgUmljaCIgPHJzYWx6PTQwYWthbWFpLmNvbUBkbWFyYy5pZXRm
Lm9yZzxtYWlsdG86NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnPj4NCkRhdGU6IDUvMS8xOCA1
OjI1IEFNIChHTVQtMDg6MDApDQpUbzogQmVuamFtaW4gS2FkdWsgPGJrYWR1az00MGFrYW1haS5j
b21AZG1hcmMuaWV0Zi5vcmc8bWFpbHRvOjQwYWthbWFpLmNvbUBkbWFyYy5pZXRmLm9yZz4+LCBQ
cmF2ZWVuIEJhbGFzdWJyYW1hbmlhbiA8cHJhdmI9NDBtaWNyb3NvZnQuY29tQGRtYXJjLmlldGYu
b3JnPG1haWx0bzo0MG1pY3Jvc29mdC5jb21AZG1hcmMuaWV0Zi5vcmc+Pg0KQ2M6IElFVEYgUVVJ
QyBXRyA8cXVpY0BpZXRmLm9yZzxtYWlsdG86cXVpY0BpZXRmLm9yZz4+DQpTdWJqZWN0OiBSZTog
R2V0dGluZyB0byBjb25zZW5zdXMgb24gcGFja2V0IG51bWJlciBlbmNyeXB0aW9uDQoNCiAgICA+
IEkgZGlzYWdyZWUgdGhhdCB3ZSBuZWVkIGFueSBtb3JlIGRhdGEgZm9yIG5vdCBkb2luZyBQTkUg
aW4gdGhlIGRhdGFjZW50ZXIuIFdoeSB3b3VsZCB3ZSBhZGQgYW4gZXh0cmEgZW5jcnlwdC1kZWNy
eXB0IHN0ZXAgZm9yIG5vIG9idmlvdXMgYmVuZWZpdD8NCg0KSSBhbSBjb25jZXJuZWQgdGhhdCBw
ZW9wbGUgd2lsbCBtaXMtaW50ZXJwcmV0IHRoZSBtZWFuaW5nIG9mIGEgZGF0YWNlbnRlciwgYW5k
IHRoaW5rIHRoYXQgYSBidW5jaCBvZiBzZXJ2ZXJzLCBvciBldmVuIGEgcmFjaywgaW4gYW4gb3Bl
biBjb2xvIHNwYWNlIGlzIGEgImRhdGFjZW50ZXIuIiAgQ29tcHV0ZXJzIGtlZXAgZ2V0dGluZyBm
YXN0ZXIuDQoNCg==

--_000_MWHPR21MB063883F004E055CC91C153EBB6810MWHPR21MB0638namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6ZHQ9InV1aWQ6QzJGNDEwMTAtNjVC
My0xMWQxLUEyOUYtMDBBQTAwQzE0ODgyIiB4bWxuczptPSJodHRwOi8vc2NoZW1hcy5taWNyb3Nv
ZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy9UUi9S
RUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250
ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1ldGEgbmFtZT0iR2VuZXJhdG9yIiBj
b250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQgbWVkaXVtKSI+DQo8c3R5bGU+PCEt
LQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiQ2Ft
YnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9
DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2
Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250
LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGlu
aywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJs
dWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlw
ZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsN
Cgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAubXNvbm9ybWFsMCwgbGkubXNvbm9ybWFs
MCwgZGl2Lm1zb25vcm1hbDANCgl7bXNvLXN0eWxlLW5hbWU6bXNvbm9ybWFsOw0KCW1zby1tYXJn
aW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowaW47DQoJbXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGluOw0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1m
YW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7bXNvLXN0
eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2Vy
aWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlw
ZTpleHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpAcGFn
ZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGlu
IDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0K
LS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpl
eHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0
ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6
ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0t
Pg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUi
Pg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoaXMg
aXMgbm90IGFib3V0IHB1dHRpbmcgcGxhaW50ZXh0IGRhdGEgb24gdGhlIG5ldHdvcmssIHRoaXMg
aXMgYWJvdXQgbm90IGFkZGluZyBQTkUgd2hpY2ggaXMgaW50ZW5kZWQgZm9yIHByZXZlbnRpbmcg
b3NzaWZpY2F0aW9uLiBTbyBJIGRvbuKAmXQgdW5kZXJzdGFuZCB3aGF0IHRoZSB0cnVzdCBpc3N1
ZSBiZWluZyByZWZlcnJlZCB0byBpcyBpbiBjYXNlIG9mIHRoZSByYXJlIG1pc2NvbmZpZy4NCjxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5XaXRoaW4gYSBEQyBzZXZlcmFsIHRoaW5ncyBhcmUgZGlm
ZmVyZW50IOKAkyB0aGUgZGVwbG95bWVudCBtYXkgbmVlZCBkaWZmZXJlbnQgY29uZ2VzdGlvbiBj
b250cm9sIGxpa2UgRENUQ1AsIGRpZmZlcmVudCBzZXR0aW5ncyBmb3IgdmFyaW91cyB0cmFuc3Bv
cnQgcGFyYW1ldGVycyAobGlrZSBtaW5ydG8gYW5kIG1heCBBQ0sgZGVsYXkpLCBsYXJnZXIgZmxv
dyBjb250cm9sIHdpbmRvdyBldGMuIFRoaXMgaXMgdHJ1ZQ0KIGZvciBUQ1AgdG9kYXkuIFRoZSBv
dXQgb2YgYm94IGRlZmF1bHQgdXNlcyB0aGUgaGFuZHNoYWtlIFJUVCB0byBtYWtlIGEgZGV0ZXJt
aW5hdGlvbiBvZiB3aGF04oCZcyBpbnRyYS1EQyBidXQgdGhlcmUgaXMgcmljaCBjb25maWd1cmF0
aW9uIHRvIG92ZXJyaWRlIHRoZSBkZWZhdWx0IGFuZCBzZXQgaXQgYmFzZWQgb24gNC10dXBsZSBm
aWx0ZXJzLg0KPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFuZCB0aGVyZSB3b3JrbG9hZHMgbGlr
ZSBjbG91ZCBzdG9yYWdlIGFuZCBsaXZlIG1pZ3JhdGlvbiB0aGF0IGFyZSBieSB2aXJ0dWUgb2Yg
ZGVwbG95bWVudCBpbnRyYS1EQy4gVGhlc2UgY2Fubm90IGJlIGxvYWQgc2hpZnRlZCBhcyB0aGV5
IHVzZSBwcml2YXRlIElQIGFkZHJlc3Mgc3BhY2UuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxi
PkZyb206PC9iPiBUZWQgSGFyZGllIFttYWlsdG86dGVkLmlldGZAZ21haWwuY29tXSA8YnI+DQo8
Yj5TZW50OjwvYj4gVHVlc2RheSwgTWF5IDEsIDIwMTggODo1NSBBTTxicj4NCjxiPlRvOjwvYj4g
Um9iZXJ0byBQZW9uICZsdDtmZW5peEBmYi5jb20mZ3Q7PGJyPg0KPGI+Q2M6PC9iPiBTYWx6LCBS
aWNoICZsdDtyc2FsekBha2FtYWkuY29tJmd0OzsgQmVuamFtaW4gS2FkdWsgJmx0O2JrYWR1a0Bh
a2FtYWkuY29tJmd0OzsgUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gJmx0O3ByYXZiQG1pY3Jvc29m
dC5jb20mZ3Q7OyBJRVRGIFFVSUMgV0cgJmx0O3F1aWNAaWV0Zi5vcmcmZ3Q7PGJyPg0KPGI+U3Vi
amVjdDo8L2I+IFJlOiBHZXR0aW5nIHRvIGNvbnNlbnN1cyBvbiBwYWNrZXQgbnVtYmVyIGVuY3J5
cHRpb248bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIFR1ZSwgTWF5IDEsIDIwMTgg
YXQgODoxMyBBTSwgUm9iZXJ0byBQZW9uICZsdDs8YSBocmVmPSJtYWlsdG86ZmVuaXhAZmIuY29t
IiB0YXJnZXQ9Il9ibGFuayI+ZmVuaXhAZmIuY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48
L3A+DQo8ZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXIt
bGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2lu
LWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5BbHNvLCBQcmlzbS4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+LT1SJm5ic3A7PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij5UaGF0J3MgYSBs
aXR0bGUgbW9yZSBzdWNjaW5jdCB0aGFuIEkgd291bGQgYmUsIGJ1dCB5ZXMuJm5ic3A7IEhvdyBk
b2VzIGFuIGFwcGxpY2F0aW9uIGtub3cgdGhhdCB0aGUgZmxvdyBpdCBpcyBpbml0aWF0aW5nIHdp
bGwgdHJhdmVyc2UgYSB0b3BvbG9neSB0aGF0IGlzIGRlZW1lZCB0byBiZSB3aXRoaW4gYSBjb250
cm9sbGVkIGVudmlyb25tZW50PyZuYnNwOyBZb3UgY2FuIHNheQ0KICZxdW90O2NvbmZpZ3VyYXRp
b24mcXVvdDsgYnV0IEkgZmVhciBpdCB3aWxsIHR1cm4gPGEgaHJlZj0iaHR0cHM6Ly9uYTAxLnNh
ZmVsaW5rcy5wcm90ZWN0aW9uLm91dGxvb2suY29tLz91cmw9aHR0cHMlM0ElMkYlMkZpLmtpbmph
LWltZy5jb20lMkZnYXdrZXItbWVkaWElMkZpbWFnZSUyRnVwbG9hZCUyRnMtLUVkdTZMUHU5LS0l
MkZjX3NjYWxlJTJDZl9hdXRvJTJDZmxfcHJvZ3Jlc3NpdmUlMkNxXzgwJTJDd184MDAlMkYxOTR0
aGJ0eWVuY3MwanBnLmpwZyZhbXA7ZGF0YT0wMiU3QzAxJTdDcHJhdmIlNDBtaWNyb3NvZnQuY29t
JTdDNGRhNDRlOGFjMWRmNDcwOGFkODgwOGQ1YWY3YmZjYTglN0M3MmY5ODhiZjg2ZjE0MWFmOTFh
YjJkN2NkMDExZGI0NyU3QzElN0MxJTdDNjM2NjA3ODY5NDExMjU4OTc2JmFtcDtzZGF0YT1Qcm9s
U0hrYkYyU2dNSDNxZFFOJTJCWkZva1h2c0VCZiUyRjNvOU1hVW5pbDBnOCUzRCZhbXA7cmVzZXJ2
ZWQ9MCI+DQp1cCBvbiBhIHBvc3QtaXQmbmJzcDsgPC9hPmlmIHlvdSBkby4mbmJzcDsgTG9hZHMg
c2hpZnQsIHJlc291cmNlcyBtb3ZlLCBhbmQgc3VkZGVubHkgeW91IGZpbmQgdGhhdCBob3N0IHdo
aWNoIHVzZWQgdG8gYmUgaW4gdGhlIHNhbWUgcmFjaywgYmVpbmcgZG93biwgaGFzIGxvYWQtc2hp
ZnRlZCB0byB0aGUgbmV4dCBpbnN0YW5jZSwmbmJzcDsgaW4gYSBkYXRhY2VudGVyIDUwMCBtaWxl
cyBhd2F5IGFjcm9zcyBhIHZlcnkgZGlmZmVyZW50IG5ldHdvcmsuJm5ic3A7DQo8YnI+DQo8YnI+
DQpNYW55IG1vZGVybiBkZXBsb3ltZW50cyBhcmUgYWxzbyBpbiBzb21lb25lIGVsc2UncyBkYXRh
IGNlbnRlciwgc28gc2F5aW5nICZxdW90O0RhdGEgY2VudGVyIG5ldHdvcmtzJnF1b3Q7IGRvZXNu
J3Qgc2F5IG11Y2ggYWJvdXQgd2h5IHlvdSdyZSB0cnVzdGluZyB0aGUgbmV0d29yayBpbnNpZGUu
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UZWQ8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNw
OzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0
O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0KPGRpdj4NCjxkaXY+DQo8ZGl2
IGlkPSJtXy0zNzc1NTUyMDk3NTgyNjY0NTYyeF9jb21wb3Nlcl9zaWduYXR1cmUiPg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS41cHQ7Y29sb3I6
IzU3NTc1NyI+U2VudCB2aWEgdGhlIFNhbXN1bmcgR2FsYXh5IFM3LCBhbiBBVCZhbXA7VCA0RyBM
VEUgc21hcnRwaG9uZTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi0tLS0tLS0tIE9yaWdpbmFsIG1lc3NhZ2UgLS0t
LS0tLS08bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PkZyb206ICZxdW90O1NhbHosIFJpY2gmcXVvdDsgJmx0O3JzYWx6PTxhIGhyZWY9Im1haWx0bzo0
MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj40MGFrYW1haS5jb21A
ZG1hcmMuaWV0Zi5vcmc8L2E+Jmd0Ow0KPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5EYXRlOiA1LzEvMTggNToyNSBBTSAoR01ULTA4OjAwKSA8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRvOiBCZW5q
YW1pbiBLYWR1ayAmbHQ7YmthZHVrPTxhIGhyZWY9Im1haWx0bzo0MGFrYW1haS5jb21AZG1hcmMu
aWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj40MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmc8L2E+
Jmd0OywgUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gJmx0O3ByYXZiPTxhIGhyZWY9Im1haWx0bzo0
MG1pY3Jvc29mdC5jb21AZG1hcmMuaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj40MG1pY3Jvc29m
dC5jb21AZG1hcmMuaWV0Zi5vcmc8L2E+Jmd0Ow0KPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5DYzogSUVURiBRVUlDIFdHICZsdDs8YSBocmVmPSJt
YWlsdG86cXVpY0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPnF1aWNAaWV0Zi5vcmc8L2E+Jmd0
Ow0KPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5T
dWJqZWN0OiBSZTogR2V0dGluZyB0byBjb25zZW5zdXMgb24gcGFja2V0IG51bWJlciBlbmNyeXB0
aW9uDQo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+Jm5i
c3A7Jm5ic3A7Jm5ic3A7ICZndDsgSSBkaXNhZ3JlZSB0aGF0IHdlIG5lZWQgYW55IG1vcmUgZGF0
YSBmb3Igbm90IGRvaW5nIFBORSBpbiB0aGUgZGF0YWNlbnRlci4gV2h5IHdvdWxkIHdlIGFkZCBh
biBleHRyYSBlbmNyeXB0LWRlY3J5cHQgc3RlcCBmb3Igbm8gb2J2aW91cyBiZW5lZml0Pzxicj4N
Cjxicj4NCkkgYW0gY29uY2VybmVkIHRoYXQgcGVvcGxlIHdpbGwgbWlzLWludGVycHJldCB0aGUg
bWVhbmluZyBvZiBhIGRhdGFjZW50ZXIsIGFuZCB0aGluayB0aGF0IGEgYnVuY2ggb2Ygc2VydmVy
cywgb3IgZXZlbiBhIHJhY2ssIGluIGFuIG9wZW4gY29sbyBzcGFjZSBpcyBhICZxdW90O2RhdGFj
ZW50ZXIuJnF1b3Q7Jm5ic3A7IENvbXB1dGVycyBrZWVwIGdldHRpbmcgZmFzdGVyLg0KPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4N
CjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_MWHPR21MB063883F004E055CC91C153EBB6810MWHPR21MB0638namp_--


From nobody Tue May  1 09:56:44 2018
Return-Path: <ietf@trammell.ch>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3230C12E8C7 for <quic@ietfa.amsl.com>; Tue,  1 May 2018 09:56:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 oua5Gmf9ISvb for <quic@ietfa.amsl.com>; Tue,  1 May 2018 09:56:40 -0700 (PDT)
Received: from gozo.iway.ch (gozo.iway.ch [212.25.24.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C521C12DB6B for <quic@ietf.org>; Tue,  1 May 2018 09:56:38 -0700 (PDT)
Received: from gozo.iway.ch (localhost [127.0.0.1]) by localhost (Postfix) with ESMTP id 41CCF3404FB; Tue,  1 May 2018 18:56:36 +0200 (CEST)
Received: from localhost (localhost [127.0.0.1]) by localhost (ACF/6597.17276);  Tue,  1 May 2018 18:56:32 +0200 (CEST)
Received: from switchplus-mail.ch (switchplus-mail.ch [212.25.8.236]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by gozo.iway.ch (Postfix) with ESMTPS; Tue,  1 May 2018 18:56:32 +0200 (CEST)
Received: from [145.14.214.39] (account ietf@trammell.ch HELO [10.11.33.5]) by switchplus-mail.ch (CommuniGate Pro SMTP 6.1.18) with ESMTPSA id 53547195; Tue, 01 May 2018 18:56:31 +0200
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
Message-Id: <89893592-7135-4C24-BE1E-4B0FFD1A2E97@trammell.ch>
Content-Type: multipart/signed; boundary="Apple-Mail=_8BA129F7-4403-4266-AA50-27D45E26C871"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Subject: Re: Getting to consensus on packet number encryption
Date: Tue, 1 May 2018 18:56:30 +0200
In-Reply-To: <CA+9kkMCpxve3CKhQk45YKbvyOyQ6kvzyhpJhrTq1UM-QM+ms2Q@mail.gmail.com>
Cc: Roberto Peon <fenix@fb.com>, Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>, IETF QUIC WG <quic@ietf.org>, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, Benjamin Kaduk <bkaduk=40akamai.com@dmarc.ietf.org>
To: Ted Hardie <ted.ietf@gmail.com>
References: <CANatvzwCYrOZULG3iVmDFp97nr=M5=Gufo8TZjOGQVFUpsn0bQ@mail.gmail.com> <CAAedzxqDcPXJUE83KVnDiU23PvqDcTCrc6rRMw09FexjJA-Y6Q@mail.gmail.com> <CANatvzwjYE6EdvFtOXJMVQnutbVQ4YY+=XsQFzKwHzqWzZ4U+w@mail.gmail.com> <d32ade7b56bf4651952659307c08893b@usma1ex-dag1mb5.msg.corp.akamai.com> <CANatvzwHtCn8rLB8npf3i7PGyYZhVDRd2uojh5hv3uxtFPEsSA@mail.gmail.com> <58447D8E-782C-431C-8FC3-71124B10A047@trammell.ch> <CACpbDcdfF9w3qqrH1eB0sGU_4vheD9aMP5EXnp1o3Y19N19NUg@mail.gmail.com> <e8b4931a-3931-5b8d-8dad-3ca1939d5542@huitema.net> <CAKcm_gPaj3o-VTdA_0+Kk+nTcVJrYcs_BMyOiDGXKub3gB=GLg@mail.gmail.com> <MWHPR21MB063869878060E850137210FEB6820@MWHPR21MB0638.namprd21.prod.outlook.com> <20180501121906.GA5742@akamai.com> <F63059EA-BA14-4886-A4FB-AA5F04AC164B@akamai.com> <BY2PR15MB07757EAB6A818F1D8D8CCED9CD810@BY2PR15MB0775.namprd15.prod.outlook.com> <CA+9kkMCpxve3CKhQk45YKbvyOyQ6kvzyhpJhrTq1UM-QM+ms2Q@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/fdSW4ZB_M1mpwXGI2LiszZRgoOE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2018 16:56:42 -0000

--Apple-Mail=_8BA129F7-4403-4266-AA50-27D45E26C871
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

hi Ted, all,

At this point I've pretty much come around to the opinion we should just =
land 1079 and discuss the rest, but this conversation continues to have =
me worried that we're coming to consensus on a feature we do not fully =
understand the applicability and limitations of.

PNE's primary utility is anti-ossification. While it reduces the amount =
of information available to an attacker attempting to achieve =
linkability of flows across a purposeful path migration, or with a =
single-PN-space multipath design, it does not eliminate it, so expecting =
more than a marginal privacy benefit from the feature per se is setting =
oneself up for disappointment.

The reason to disable PNE in (admittedly ill-defined) "datacenter" =
environments is to trade off the (~1%ish) overhead for ossification =
protection you know you don't need because you didn't deploy anything =
that tries to abuse the packet number.

(on which, more below; and on preview, what Praveen said)

> On 1 May 2018, at 17:55, Ted Hardie <ted.ietf@gmail.com> wrote:
>=20
> On Tue, May 1, 2018 at 8:13 AM, Roberto Peon <fenix@fb.com> wrote:
> Also, Prism.
>=20
> -=3DR
>=20
>=20
>=20
> That's a little more succinct than I would be, but yes.  How does an =
application know that the flow it is initiating will traverse a topology =
that is deemed to be within a controlled environment?  You can say =
"configuration" but I fear it will turn up on a post-it  if you do.  =
Loads shift, resources move, and suddenly you find that host which used =
to be in the same rack, being down, has load-shifted to the next =
instance,  in a datacenter 500 miles away across a very different =
network.
>=20
> Many modern deployments are also in someone else's data center, so =
saying "Data center networks" doesn't say much about why you're trusting =
the network inside.

The "load-shifted to the next instance" example is an interesting one =
iff said load shifting causes the traffic that used to cross a private =
network to transit the open Internet instead. Is this a thing that ever =
happens in any of the environments that get called "datacenter" for =
networking technology purposes?

Cheers,

Brian

> Ted
>=20
> Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
>=20
>=20
> -------- Original message --------
> From: "Salz, Rich" <rsalz=3D40akamai.com@dmarc.ietf.org>
> Date: 5/1/18 5:25 AM (GMT-08:00)
> To: Benjamin Kaduk <bkaduk=3D40akamai.com@dmarc.ietf.org>, Praveen =
Balasubramanian <pravb=3D40microsoft.com@dmarc.ietf.org>
> Cc: IETF QUIC WG <quic@ietf.org>
> Subject: Re: Getting to consensus on packet number encryption
>=20
>     > I disagree that we need any more data for not doing PNE in the =
datacenter. Why would we add an extra encrypt-decrypt step for no =
obvious benefit?
>=20
> I am concerned that people will mis-interpret the meaning of a =
datacenter, and think that a bunch of servers, or even a rack, in an =
open colo space is a "datacenter."  Computers keep getting faster.
>=20
>=20


--Apple-Mail=_8BA129F7-4403-4266-AA50-27D45E26C871
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEkCTSTp2bIB6fBRHIihK3vwvqRqMFAlronD4ACgkQihK3vwvq
RqMAGxAAqtxJo6H4G/6Tc7yhCtRvflD2NJo3vgkoSwRgjLgMGac905TfFOfMJU/I
jXslv15T2D+uH7p3EZOAIT1tiSPnLcI5txasiJy5vb7tLSD19LMpB8oLFyHYS7Rn
ozupkAgS+pOAti5jhzzcf+6nnCcTcI1iYtAYw745qFYJciUGLEdcX8UahLtnDXrD
GwHRQsRzd1BMIoEvUfUU9JYuPtMw0tEK5q5pF8+jGGJQuvQG0RLCjSkwdEOJln2b
TtNfrasqmr/OJ/5sJX3NBxkzJcm7VQXTbx7THdBaFlJt/pnVhuDU/gORYaZredwz
P194A5d9a4f1n1C/aOWTOJ1pkUs4kk+wBo5VB5/yAfXj0/uMish60QiEEi2a/weW
LfZ9IhdynbLHMGdkpOucO7b87Qm2qJNebhgZxMAGf5GyXIxi0CpdL3ZXKTNmCzmb
7O6KnPsui34WJ3Vvo3R/MSG7/RN84TTfqGll1icH7gj8NoFvQF568zF9fA+E6PhI
XzoF+Vt6PFTnl0PzhZMlVvpLX4metAmHK2bWJjaw1RAA4Tm8l0nrYlEWngsv3/Rl
nqOxSWpjjBFlROdaJVcAbytHy16SHfCOBu7DldmK1dZTvIPod5FpDwSlMhNY3rxt
/IQv2ivMr7BgB2YGtnKbiZPCeA7zlrSvad/6fChdb+gIC627WCM=
=4L+V
-----END PGP SIGNATURE-----

--Apple-Mail=_8BA129F7-4403-4266-AA50-27D45E26C871--


From nobody Tue May  1 10:11:17 2018
Return-Path: <ilubashe@akamai.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 44D7B124D6C for <quic@ietfa.amsl.com>; Tue,  1 May 2018 10:11:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.709
X-Spam-Level: 
X-Spam-Status: No, score=-2.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 5HmAfvyKTEfk for <quic@ietfa.amsl.com>; Tue,  1 May 2018 10:11:12 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::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 9BF1A12DB6D for <quic@ietf.org>; Tue,  1 May 2018 10:11:11 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.22/8.16.0.22) with SMTP id w41H52k5012847; Tue, 1 May 2018 18:11:06 +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=OXlKVkrrEGARS4MF03su8+LjTDeG15/WflHlOZu7TS4=; b=QXj0hXA9R25q8koEGGU1lriUYVPHvY6eAcGAsmN5UCk/QtHsTJgeAUfhqYS7O8Y+KkTs ShOQ5QqNUIIYjVsUuEwedvH9e7smVIRhKm/n5f/bp9B3hpxNf9UQc7xBYdbUo7+Y30e+ +qLFqF36+bvb/k5QcvkpEWd1vmIpWFNzt38AvcWZP0VFqY716mxkDNhR8loTPOWWv4LF bUpTUa7Aa10MssmrZgXI11rpNcrSbNUC7oQ9dSocol65G08/vJLcboD/UKe/5UDjJ+6A W+JM3Ch4jxGnQm7TgImTh92jRLdy3bA9dTALlWw7jOJqN2qsoR+5DHOsw0Pod7I2YkdR dw== 
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19]) by m0050102.ppops.net-00190b01. with ESMTP id 2hmr65yf9a-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 01 May 2018 18:11:06 +0100
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w41H1l7H011951; Tue, 1 May 2018 13:11:05 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.53]) by prod-mail-ppoint2.akamai.com with ESMTP id 2hmm9uwrq4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 01 May 2018 13:11:05 -0400
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com (172.27.123.105) by usma1ex-dag1mb3.msg.corp.akamai.com (172.27.123.103) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Tue, 1 May 2018 13:11:04 -0400
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com ([172.27.123.105]) by usma1ex-dag1mb5.msg.corp.akamai.com ([172.27.123.105]) with mapi id 15.00.1365.000; Tue, 1 May 2018 13:11:04 -0400
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: Roberto Peon <fenix@fb.com>, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, Benjamin Kaduk <bkaduk=40akamai.com@dmarc.ietf.org>, Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>
CC: IETF QUIC WG <quic@ietf.org>
Subject: RE: Getting to consensus on packet number encryption
Thread-Topic: Getting to consensus on packet number encryption
Thread-Index: AQHTy9GWvgm/QKk890OIh9EYaPY3H6PwqlkAgAC4ugCAAARcAIAAG5CAgAAFCQCAAACJgIAAEVgAgACR+YCAB09lAIAFXyIAgAVK+oCAAJlSAIABxdSAgACOHYCAB/ExAIACo7YAgACiMICAAADPgIAAIs8AgAAm/YCAABEygIAABpIAgAAK6ACAAK10MIABK7IAgACzcYCAAHHMgIAEe1cAgAABEACAABWHgIAA8UgAgAABeQCAAC8lAP//zCFQ
Date: Tue, 1 May 2018 17:11:03 +0000
Message-ID: <bf9c39f6d92449289abd7995bbfff0db@usma1ex-dag1mb5.msg.corp.akamai.com>
References: <CANatvzwCYrOZULG3iVmDFp97nr=M5=Gufo8TZjOGQVFUpsn0bQ@mail.gmail.com> <CAAedzxqDcPXJUE83KVnDiU23PvqDcTCrc6rRMw09FexjJA-Y6Q@mail.gmail.com> <CANatvzwjYE6EdvFtOXJMVQnutbVQ4YY+=XsQFzKwHzqWzZ4U+w@mail.gmail.com> <d32ade7b56bf4651952659307c08893b@usma1ex-dag1mb5.msg.corp.akamai.com> <CANatvzwHtCn8rLB8npf3i7PGyYZhVDRd2uojh5hv3uxtFPEsSA@mail.gmail.com> <58447D8E-782C-431C-8FC3-71124B10A047@trammell.ch> <CACpbDcdfF9w3qqrH1eB0sGU_4vheD9aMP5EXnp1o3Y19N19NUg@mail.gmail.com> <e8b4931a-3931-5b8d-8dad-3ca1939d5542@huitema.net> <CAKcm_gPaj3o-VTdA_0+Kk+nTcVJrYcs_BMyOiDGXKub3gB=GLg@mail.gmail.com> <MWHPR21MB063869878060E850137210FEB6820@MWHPR21MB0638.namprd21.prod.outlook.com> <20180501121906.GA5742@akamai.com>, <F63059EA-BA14-4886-A4FB-AA5F04AC164B@akamai.com> <BY2PR15MB07757EAB6A818F1D8D8CCED9CD810@BY2PR15MB0775.namprd15.prod.outlook.com>
In-Reply-To: <BY2PR15MB07757EAB6A818F1D8D8CCED9CD810@BY2PR15MB0775.namprd15.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.36.2]
Content-Type: multipart/alternative; boundary="_000_bf9c39f6d92449289abd7995bbfff0dbusma1exdag1mb5msgcorpak_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-01_09:, , 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=964 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805010166
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-01_09:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=883 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805010166
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/rsa3Ukhdg_mJ0b7meRLGMl7HtSs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2018 17:11:15 -0000

--_000_bf9c39f6d92449289abd7995bbfff0dbusma1exdag1mb5msgcorpak_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Wait, the entire purpose of PNE is to make flow linking during connection m=
igrations harder.  A server in an "open colo" talking to another server in =
an "open colo" is a perfect example when PNE is not needed.

The "uniformity and simplicity of implementation" makes sense, but we certa=
inly did much weirder things (like a new transport) to gain performance.  P=
raveen's point is that a large portion of communication is between devices =
that are not mobile.  If PNE has a non-negligible cost (for example, HW acc=
eleration requires more ASIC and is costlier), is "uniformity and simplicit=
y" gained by the lack of the extra option worth it?

Another way of putting this is that QUIC's advantage over TCP is especially=
 evident for the 90th percentile of connections, and these are likely not t=
o be fixed server-to-server connections (within a DC or even between "open =
colos").  Any extra cost of QUIC over TCP (extra CPU-per-bit or server-cost=
-per-bit) will make it less likely that QUIC will be adopted for server-to-=
server connections.  Is the adoption risk and the extra costs risk worth th=
e simplicity gained by not having an extra option?


  *   Igor


From: Roberto Peon [mailto:fenix@fb.com]
Sent: Tuesday, May 01, 2018 11:13 AM
To: Salz, Rich <rsalz=3D40akamai.com@dmarc.ietf.org>; Benjamin Kaduk <bkadu=
k=3D40akamai.com@dmarc.ietf.org>; Praveen Balasubramanian <pravb=3D40micros=
oft.com@dmarc.ietf.org>
Cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Getting to consensus on packet number encryption

Also, Prism.

-=3DR


Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone


-------- Original message --------
From: "Salz, Rich" <rsalz=3D40akamai.com@dmarc.ietf.org<mailto:rsalz=3D40ak=
amai.com@dmarc.ietf.org>>
Date: 5/1/18 5:25 AM (GMT-08:00)
To: Benjamin Kaduk <bkaduk=3D40akamai.com@dmarc.ietf.org<mailto:bkaduk=3D40=
akamai.com@dmarc.ietf.org>>, Praveen Balasubramanian <pravb=3D40microsoft.c=
om@dmarc.ietf.org<mailto:pravb=3D40microsoft.com@dmarc.ietf.org>>
Cc: IETF QUIC WG <quic@ietf.org<mailto:quic@ietf.org>>
Subject: Re: Getting to consensus on packet number encryption

    > I disagree that we need any more data for not doing PNE in the datace=
nter. Why would we add an extra encrypt-decrypt step for no obvious benefit=
?

I am concerned that people will mis-interpret the meaning of a datacenter, =
and think that a bunch of servers, or even a rack, in an open colo space is=
 a "datacenter."  Computers keep getting faster.

--_000_bf9c39f6d92449289abd7995bbfff0dbusma1exdag1mb5msgcorpak_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
p.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	border:none;
	padding:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1712145785;
	mso-list-type:hybrid;
	mso-list-template-ids:-1704305354 1352456742 67698691 67698693 67698689 67=
698691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:"Times New Roman";
	mso-bidi-font-family:Calibri;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Wait, the entire purpose of PNE is to make flow link=
ing during connection migrations harder.&nbsp; A server in an &#8220;open c=
olo&#8221; talking to another server in an &#8220;open colo&#8221; is a per=
fect example when PNE is not needed.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The &#8220;uniformity and simplicity of implementati=
on&#8221; makes sense, but we certainly did much weirder things (like a new=
 transport) to gain performance.&nbsp; Praveen&#8217;s point is that a larg=
e portion of communication is between devices that are not
 mobile.&nbsp; If PNE has a non-negligible cost (for example, HW accelerati=
on requires more ASIC and is costlier), is &#8220;uniformity and simplicity=
&#8221; gained by the lack of the extra option worth it?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Another way of putting this is that QUIC&#8217;s adv=
antage over TCP is especially evident for the 90<sup>th</sup> percentile of=
 connections, and these are likely not to be fixed server-to-server connect=
ions (within a DC or even between &#8220;open
 colos&#8221;).&nbsp; Any extra cost of QUIC over TCP (extra CPU-per-bit or=
 server-cost-per-bit) will make it less likely that QUIC will be adopted fo=
r server-to-server connections.&nbsp; Is the adoption risk and the extra co=
sts risk worth the simplicity gained by not having
 an extra option?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l0 level1 =
lfo1">Igor<o:p></o:p></li></ul>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Roberto Peon [mailto:fenix@fb.com] <br>
<b>Sent:</b> Tuesday, May 01, 2018 11:13 AM<br>
<b>To:</b> Salz, Rich &lt;rsalz=3D40akamai.com@dmarc.ietf.org&gt;; Benjamin=
 Kaduk &lt;bkaduk=3D40akamai.com@dmarc.ietf.org&gt;; Praveen Balasubramania=
n &lt;pravb=3D40microsoft.com@dmarc.ietf.org&gt;<br>
<b>Cc:</b> IETF QUIC WG &lt;quic@ietf.org&gt;<br>
<b>Subject:</b> Re: Getting to consensus on packet number encryption<o:p></=
o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">Also, Prism.&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">-=3DR&nbsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div id=3D"x_composer_signature">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.5pt;color:#575757">Sent v=
ia the Samsung Galaxy S7, an AT&amp;T 4G LTE smartphone<o:p></o:p></span></=
p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">-------- Original message --------<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">From: &quot;Salz, Rich&quot; &lt;<a href=3D"mailto:r=
salz=3D40akamai.com@dmarc.ietf.org">rsalz=3D40akamai.com@dmarc.ietf.org</a>=
&gt;
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Date: 5/1/18 5:25 AM (GMT-08:00) <o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">To: Benjamin Kaduk &lt;<a href=3D"mailto:bkaduk=3D40=
akamai.com@dmarc.ietf.org">bkaduk=3D40akamai.com@dmarc.ietf.org</a>&gt;, Pr=
aveen Balasubramanian &lt;<a href=3D"mailto:pravb=3D40microsoft.com@dmarc.i=
etf.org">pravb=3D40microsoft.com@dmarc.ietf.org</a>&gt;
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Cc: IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org=
">quic@ietf.org</a>&gt;
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Subject: Re: Getting to consensus on packet number e=
ncryption
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">&nbsp;&nbsp;&nbsp; &g=
t; I disagree that we need any more data for not doing PNE in the datacente=
r. Why would we add an extra encrypt-decrypt step for no obvious benefit?<b=
r>
<br>
I am concerned that people will mis-interpret the meaning of a datacenter, =
and think that a bunch of servers, or even a rack, in an open colo space is=
 a &quot;datacenter.&quot;&nbsp; Computers keep getting faster.
<o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_bf9c39f6d92449289abd7995bbfff0dbusma1exdag1mb5msgcorpak_--


From nobody Tue May  1 10:44:20 2018
Return-Path: <ted.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F063412E8D7 for <quic@ietfa.amsl.com>; Tue,  1 May 2018 10:44:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 VWfwQgQjz4Im for <quic@ietfa.amsl.com>; Tue,  1 May 2018 10:44:15 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A904612E8D4 for <quic@ietf.org>; Tue,  1 May 2018 10:44:15 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id y15-v6so10671918oia.13 for <quic@ietf.org>; Tue, 01 May 2018 10:44:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=bmvh57zcYUEMjIbqo4l2C2VqrxYjl+NVVKffrggFwHU=; b=ujLFFW9hzfw4Odq3wYfUK7MOxyneoWjEG+vO5sRAP5j+ygF5GFFFPlFneR9u/ZIcxo ht9TXiQ0+AKCGAz1djvCt1gN5C5+pPMFUXsam7uWwVZw4x+eOCGiwKWEVIV+EYZ8h1ls 5PoCt35g19W9uC71F9TP5b9zw3WbQBA+fdthPRPwc4+s8QXZ6FUiecQEfAP1l4GEkfhQ yfdxVUdMJ7+87ipeaj6dE2nzM6QHYpQcH4PZsWuvWMPBmThHEacuWY+AsJnSDgMUdBsj 6rSJlmVaBdxbcVUDx5G8LTqc1tichKABG1fS7Xm+xBUjQFFLsQ0jv+jTTNEifMzGwRUn vwZw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=bmvh57zcYUEMjIbqo4l2C2VqrxYjl+NVVKffrggFwHU=; b=jisSyF+etvuLFndcq/y/W7gfIjD4cQGRuTcKMDnaZoUKGGqWk4Agz2HPAVPBRLjKa+ TJEnfGw2Zty5zZwe/3Axt7ZGlRHE1CiE95OK5PoYFKjEBooFY5ZwSdloASe+A1Sc9L0p 0+LPYjQm7EjJmQkZRIPFMUNaBT99PulJ4Z8FDPC6jfAVDrtssvmD7SQI0AvfvZvd0dEx J3eBwZ4NJ5gofw73Qjm8HNPWLTX0lNaRXarHxn6ESjM8sF/GTG5CkIvz6d9N3Pt39uuY KZaMsg842+CX/2DW9BhR5HObNVXga8YXO4Ea7DIdkgD+yxHkbUt4XDvNfTKS2K1wio4d /Ccw==
X-Gm-Message-State: ALQs6tAcuFVGgl4CeTIi2nxhA+fPiCAzvatvX7+jw2GDnRhgFdwawo+t pvMGqJIoOLS03iIMUhV0ccxRRV/JpolKRatqKaE=
X-Google-Smtp-Source: AB8JxZpwXtzHBXfhHY8EPOaaSEkBJ/HISuB3wKejr63m+m6xIZH6umHhzRO+yWCn0Rq38K27wHs22MxMMFK8gV7HxA4=
X-Received: by 2002:aca:d6c4:: with SMTP id n187-v6mr9683616oig.284.1525196654868;  Tue, 01 May 2018 10:44:14 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.67.153 with HTTP; Tue, 1 May 2018 10:43:44 -0700 (PDT)
In-Reply-To: <89893592-7135-4C24-BE1E-4B0FFD1A2E97@trammell.ch>
References: <CANatvzwCYrOZULG3iVmDFp97nr=M5=Gufo8TZjOGQVFUpsn0bQ@mail.gmail.com> <CAAedzxqDcPXJUE83KVnDiU23PvqDcTCrc6rRMw09FexjJA-Y6Q@mail.gmail.com> <CANatvzwjYE6EdvFtOXJMVQnutbVQ4YY+=XsQFzKwHzqWzZ4U+w@mail.gmail.com> <d32ade7b56bf4651952659307c08893b@usma1ex-dag1mb5.msg.corp.akamai.com> <CANatvzwHtCn8rLB8npf3i7PGyYZhVDRd2uojh5hv3uxtFPEsSA@mail.gmail.com> <58447D8E-782C-431C-8FC3-71124B10A047@trammell.ch> <CACpbDcdfF9w3qqrH1eB0sGU_4vheD9aMP5EXnp1o3Y19N19NUg@mail.gmail.com> <e8b4931a-3931-5b8d-8dad-3ca1939d5542@huitema.net> <CAKcm_gPaj3o-VTdA_0+Kk+nTcVJrYcs_BMyOiDGXKub3gB=GLg@mail.gmail.com> <MWHPR21MB063869878060E850137210FEB6820@MWHPR21MB0638.namprd21.prod.outlook.com> <20180501121906.GA5742@akamai.com> <F63059EA-BA14-4886-A4FB-AA5F04AC164B@akamai.com> <BY2PR15MB07757EAB6A818F1D8D8CCED9CD810@BY2PR15MB0775.namprd15.prod.outlook.com> <CA+9kkMCpxve3CKhQk45YKbvyOyQ6kvzyhpJhrTq1UM-QM+ms2Q@mail.gmail.com> <89893592-7135-4C24-BE1E-4B0FFD1A2E97@trammell.ch>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Tue, 1 May 2018 10:43:44 -0700
Message-ID: <CA+9kkMCUTRrM9SPEz=Q5GDgU7whryZ1cRdj-O3=GP=-vOr-X+A@mail.gmail.com>
Subject: Re: Getting to consensus on packet number encryption
To: "Brian Trammell (IETF)" <ietf@trammell.ch>
Cc: Roberto Peon <fenix@fb.com>,  Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>, IETF QUIC WG <quic@ietf.org>,  "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>,  Benjamin Kaduk <bkaduk=40akamai.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d37fc4056b28848d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/cSq-3NSoY0Fhypt-sjOaMe5Yel8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2018 17:44:19 -0000

--000000000000d37fc4056b28848d
Content-Type: text/plain; charset="UTF-8"

On Tue, May 1, 2018 at 9:56 AM, Brian Trammell (IETF) <ietf@trammell.ch>
wrote:

> hi Ted, all,
>
> At this point I've pretty much come around to the opinion we should just
> land 1079 and discuss the rest, but this conversation continues to have me
> worried that we're coming to consensus on a feature we do not fully
> understand the applicability and limitations of.
>
> I also think that just landing 1079 and moving on is the right thing to do.


> PNE's primary utility is anti-ossification. While it reduces the amount of
> information available to an attacker attempting to achieve linkability of
> flows across a purposeful path migration, or with a single-PN-space
> multipath design, it does not eliminate it, so expecting more than a
> marginal privacy benefit from the feature per se is setting oneself up for
> disappointment.
>
> The reason to disable PNE in (admittedly ill-defined) "datacenter"
> environments is to trade off the (~1%ish) overhead for ossification
> protection you know you don't need because you didn't deploy anything that
> tries to abuse the packet number.
>
> (on which, more below; and on preview, what Praveen said)
>
> > On 1 May 2018, at 17:55, Ted Hardie <ted.ietf@gmail.com> wrote:
> >
> > On Tue, May 1, 2018 at 8:13 AM, Roberto Peon <fenix@fb.com> wrote:
> > Also, Prism.
> >
> > -=R
> >
> >
> >
> > That's a little more succinct than I would be, but yes.  How does an
> application know that the flow it is initiating will traverse a topology
> that is deemed to be within a controlled environment?  You can say
> "configuration" but I fear it will turn up on a post-it  if you do.  Loads
> shift, resources move, and suddenly you find that host which used to be in
> the same rack, being down, has load-shifted to the next instance,  in a
> datacenter 500 miles away across a very different network.
> >
> > Many modern deployments are also in someone else's data center, so
> saying "Data center networks" doesn't say much about why you're trusting
> the network inside.
>
> The "load-shifted to the next instance" example is an interesting one iff
> said load shifting causes the traffic that used to cross a private network
> to transit the open Internet instead.


Well, a long-haul link, certainly.  That may or may not be "the open
Internet" and the chances of it traversing a completely unknown middlebox
are low.  The chances of it passing by an unknown observer, on the other
hand, are not currently known but are presumed to be high.


> Is this a thing that ever happens in any of the environments that get
> called "datacenter" for networking technology purposes?
>
>
So, the way I look at this boils down to:

If the linkability or ossification concerns with packet numbers in the
clear are justified, you either need to have it on all the time or have
very clear methods for determining when the concerns are not present.  The
protocol is not aware of the l2 or l3 topology between an initiator and its
peer, much less the management of that path.

So the clear methods for determination really boil down to "someone turns
this off when they think it is right to do so".  Flows entirely within the
domain of control of a single provider might be a case where folks think it
is right to do so.  A subset of that domain of control is when the flow has
no long-haul links (for however you want to define that), the shorthand for
which is "datacenter network" (though it might well also be a small complex
of datacenters, an enterprise campus, or similar).  But the key is that you
believe that the topology between peer A and peer B has no middleboxes
outside of the shared domain of control that might ossify the behavior and
no observers whose use of this data concerns you.

If you control both peers and the network between them, using a QUIC
version where this is always turned off might make sense.  But having  QUIC
negotiate this outside of the version does not make sense to me, because
there is no way for an initiator or a responding peer to judge whether the
other side's assertion of safety is well-founded or even well-meant.  If it
has no independent data on this (and the protocol provides none), this
allows one side or the other to unilaterally turn off an anti-ossification
and anti-linkability feature for whatever gain it wants.  Since we're
trying to optimize for the long-term flexibility of the protocol, allowing
that particular point optimization seems contrary to our interests, much
less the privacy interests of the peers.

regards,

Ted


> Cheers,
>
> Brian
>
> > Ted
> >
> > Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
> >
> >
> > -------- Original message --------
> > From: "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>
> > Date: 5/1/18 5:25 AM (GMT-08:00)
> > To: Benjamin Kaduk <bkaduk=40akamai.com@dmarc.ietf.org>, Praveen
> Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>
> > Cc: IETF QUIC WG <quic@ietf.org>
> > Subject: Re: Getting to consensus on packet number encryption
> >
> >     > I disagree that we need any more data for not doing PNE in the
> datacenter. Why would we add an extra encrypt-decrypt step for no obvious
> benefit?
> >
> > I am concerned that people will mis-interpret the meaning of a
> datacenter, and think that a bunch of servers, or even a rack, in an open
> colo space is a "datacenter."  Computers keep getting faster.
> >
> >
>
>

--000000000000d37fc4056b28848d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Tue, May 1, 2018 at 9:56 AM, Brian Trammell (IETF) <spa=
n dir=3D"ltr">&lt;<a href=3D"mailto:ietf@trammell.ch" target=3D"_blank">iet=
f@trammell.ch</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div clas=
s=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex">hi Ted, all,<br>
<br>
At this point I&#39;ve pretty much come around to the opinion we should jus=
t land 1079 and discuss the rest, but this conversation continues to have m=
e worried that we&#39;re coming to consensus on a feature we do not fully u=
nderstand the applicability and limitations of.<br>
<br></blockquote><div>I also think that just landing 1079 and moving on is =
the right thing to do.<br></div><div>=C2=A0</div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">
PNE&#39;s primary utility is anti-ossification. While it reduces the amount=
 of information available to an attacker attempting to achieve linkability =
of flows across a purposeful path migration, or with a single-PN-space mult=
ipath design, it does not eliminate it, so expecting more than a marginal p=
rivacy benefit from the feature per se is setting oneself up for disappoint=
ment.<br>
<br>
The reason to disable PNE in (admittedly ill-defined) &quot;datacenter&quot=
; environments is to trade off the (~1%ish) overhead for ossification prote=
ction you know you don&#39;t need because you didn&#39;t deploy anything th=
at tries to abuse the packet number.<br>
<br>
(on which, more below; and on preview, what Praveen said)<br>
<span class=3D""><br>
&gt; On 1 May 2018, at 17:55, Ted Hardie &lt;<a href=3D"mailto:ted.ietf@gma=
il.com">ted.ietf@gmail.com</a>&gt; wrote:<br>
&gt; <br>
&gt; On Tue, May 1, 2018 at 8:13 AM, Roberto Peon &lt;<a href=3D"mailto:fen=
ix@fb.com">fenix@fb.com</a>&gt; wrote:<br>
&gt; Also, Prism.<br>
&gt; <br>
&gt; -=3DR<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; That&#39;s a little more succinct than I would be, but yes.=C2=A0 How =
does an application know that the flow it is initiating will traverse a top=
ology that is deemed to be within a controlled environment?=C2=A0 You can s=
ay &quot;configuration&quot; but I fear it will turn up on a post-it=C2=A0 =
if you do.=C2=A0 Loads shift, resources move, and suddenly you find that ho=
st which used to be in the same rack, being down, has load-shifted to the n=
ext instance,=C2=A0 in a datacenter 500 miles away across a very different =
network.<br>
&gt; <br>
&gt; Many modern deployments are also in someone else&#39;s data center, so=
 saying &quot;Data center networks&quot; doesn&#39;t say much about why you=
&#39;re trusting the network inside.<br>
<br>
</span>The &quot;load-shifted to the next instance&quot; example is an inte=
resting one iff said load shifting causes the traffic that used to cross a =
private network to transit the open Internet instead.</blockquote><div><br>=
</div><div>Well, a long-haul link, certainly.=C2=A0 That may or may not be =
&quot;the open Internet&quot; and the chances of it traversing a completely=
 unknown middlebox are low.=C2=A0 The chances of it passing by an unknown o=
bserver, on the other hand, are not currently known but are presumed to be =
high.<br></div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"> Is this a t=
hing that ever happens in any of the environments that get called &quot;dat=
acenter&quot; for networking technology purposes?<br>
<br></blockquote><div><br></div><div>So, the way I look at this boils down =
to:<br><br></div><div>If the linkability or ossification concerns with pack=
et numbers in the clear are justified, you either need to have it on all th=
e time or have very clear methods for determining when the concerns are not=
 present.=C2=A0 The protocol is not aware of the l2 or l3 topology between =
an initiator and its peer, much less the management of that path.=C2=A0 <br=
><br>So the clear methods for determination really boil down to &quot;someo=
ne turns this off when they think it is right to do so&quot;.=C2=A0 Flows e=
ntirely within the domain of control of a single provider might be a case w=
here folks think it is right to do so.=C2=A0 A subset of that domain of con=
trol is when the flow has no long-haul links (for however you want to defin=
e that), the shorthand for which is &quot;datacenter network&quot; (though =
it might well also be a small complex of datacenters, an enterprise campus,=
 or similar).=C2=A0 But the key is that you believe that the topology betwe=
en peer A and peer B has no middleboxes outside of the shared domain of con=
trol that might ossify the behavior and no observers whose use of this data=
 concerns you.<br><br></div><div>If you control both peers and the network =
between them, using a QUIC version where this is always turned off might ma=
ke sense.=C2=A0 But having=C2=A0 QUIC negotiate this outside of the version=
 does not make sense to me, because there is no way for an initiator or a r=
esponding peer to judge whether the other side&#39;s assertion of safety is=
 well-founded or even well-meant.=C2=A0 If it has no independent data on th=
is (and the protocol provides none), this allows one side or the other to u=
nilaterally turn off an anti-ossification and anti-linkability feature for =
whatever gain it wants.=C2=A0 Since we&#39;re trying to optimize for the lo=
ng-term flexibility of the protocol, allowing that particular point optimiz=
ation seems contrary to our interests, much less the privacy interests of t=
he peers.<br></div><div><br></div><div>regards,<br><br></div><div>Ted<br></=
div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Cheers,<br>
<br>
Brian<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; Ted<br>
&gt; <br>
&gt; Sent via the Samsung Galaxy S7, an AT&amp;T 4G LTE smartphone<br>
&gt; <br>
&gt; <br>
&gt; -------- Original message --------<br>
&gt; From: &quot;Salz, Rich&quot; &lt;rsalz=3D<a href=3D"mailto:40akamai.co=
m@dmarc.ietf.org">40akamai.com@dmarc.<wbr>ietf.org</a>&gt;<br>
&gt; Date: 5/1/18 5:25 AM (GMT-08:00)<br>
&gt; To: Benjamin Kaduk &lt;bkaduk=3D<a href=3D"mailto:40akamai.com@dmarc.i=
etf.org">40akamai.com@dmarc.<wbr>ietf.org</a>&gt;, Praveen Balasubramanian =
&lt;pravb=3D<a href=3D"mailto:40microsoft.com@dmarc.ietf.org">40microsoft.c=
om@dmarc.<wbr>ietf.org</a>&gt;<br>
&gt; Cc: IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org">quic@ietf.org</a=
>&gt;<br>
&gt; Subject: Re: Getting to consensus on packet number encryption<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 =C2=A0&gt; I disagree that we need any more data for not =
doing PNE in the datacenter. Why would we add an extra encrypt-decrypt step=
 for no obvious benefit?<br>
&gt; <br>
&gt; I am concerned that people will mis-interpret the meaning of a datacen=
ter, and think that a bunch of servers, or even a rack, in an open colo spa=
ce is a &quot;datacenter.&quot;=C2=A0 Computers keep getting faster.<br>
&gt; <br>
&gt; <br>
<br>
</div></div></blockquote></div><br></div></div>

--000000000000d37fc4056b28848d--


From nobody Tue May  1 11:40:14 2018
Return-Path: <ilubashe@akamai.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E5E3F12E9DC for <quic@ietfa.amsl.com>; Tue,  1 May 2018 11:40:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.709
X-Spam-Level: 
X-Spam-Status: No, score=-2.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 SVLHYVVVVZQf for <quic@ietfa.amsl.com>; Tue,  1 May 2018 11:40:09 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::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 3C93B126B6D for <quic@ietf.org>; Tue,  1 May 2018 11:40:09 -0700 (PDT)
Received: from pps.filterd (m0122330.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w41IWhJ9031277; Tue, 1 May 2018 19:40:02 +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=ML4Agx84w8tnISQtp72rZpgjVQYJFHdS0F/t1vKPxUE=; b=fGnwTPqgs082ZzFxPzLUIBV9G9fpdz7It7ovDTyXezeNqD8Hi7Kfvjd/8JRzuGGi3k8T mT/FUq+z4t9e3td1Weojzpp9Lmdls6k+eRklLSddafvn8tsA3qySAauSSbwJY4o7iUrE qn1NTQCO4RJrYliCnfKOJwQ6AlJqnYFGBvH1jfKT739YHA85X0EKgnv1JfiBG9SdN40v 7bPUClcoaQM4BbwSyullvRtxuQFR6LDa5HoRQlvH4xNOPoMQOFL+Vqpo5N0NbHoV3a3I FIvSpfpyl8+0rFkKUHmV61EDciIRCK4bqzMByRBYjqTeylsPKPVV6pvdj6yjYUarP/ca Eg== 
Received: from prod-mail-ppoint3 ([96.6.114.86]) by mx0b-00190b01.pphosted.com with ESMTP id 2hmpb7q79q-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 01 May 2018 19:40:01 +0100
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w41IaIFC011987; Tue, 1 May 2018 14:40:00 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.31]) by prod-mail-ppoint3.akamai.com with ESMTP id 2hmm9wbukw-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 01 May 2018 14:40:00 -0400
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com (172.27.123.105) by usma1ex-dag1mb2.msg.corp.akamai.com (172.27.123.102) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Tue, 1 May 2018 14:39:59 -0400
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com ([172.27.123.105]) by usma1ex-dag1mb5.msg.corp.akamai.com ([172.27.123.105]) with mapi id 15.00.1365.000; Tue, 1 May 2018 14:39:58 -0400
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: Ted Hardie <ted.ietf@gmail.com>, "Brian Trammell (IETF)" <ietf@trammell.ch>
CC: Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>, "IETF QUIC WG" <quic@ietf.org>, Roberto Peon <fenix@fb.com>, "Salz, Rich" <rsalz=40akamai.com@dmarc.ietf.org>, Benjamin Kaduk <bkaduk=40akamai.com@dmarc.ietf.org>
Subject: RE: Getting to consensus on packet number encryption
Thread-Topic: Getting to consensus on packet number encryption
Thread-Index: AQHTy9GWvgm/QKk890OIh9EYaPY3H6PwqlkAgAC4ugCAAARcAIAAG5CAgAAFCQCAAACJgIAAEVgAgACR+YCAB09lAIAFXyIAgAVK+oCAAJlSAIABxdSAgACOHYCAB/ExAIACo7YAgACiMICAAADPgIAAIs8AgAAm/YCAABEygIAABpIAgAAK6ACAAK10MIABK7IAgACzcYCAAHHMgIAEe1cAgAABEACAABWHgIAA8UgAgAABeQCAAC8lAIAAC7QAgAARLwCAAA0zAP//y+oQ
Date: Tue, 1 May 2018 18:39:58 +0000
Message-ID: <ba56bca23f5747e5abdfec137de37481@usma1ex-dag1mb5.msg.corp.akamai.com>
References: <CANatvzwCYrOZULG3iVmDFp97nr=M5=Gufo8TZjOGQVFUpsn0bQ@mail.gmail.com> <CAAedzxqDcPXJUE83KVnDiU23PvqDcTCrc6rRMw09FexjJA-Y6Q@mail.gmail.com> <CANatvzwjYE6EdvFtOXJMVQnutbVQ4YY+=XsQFzKwHzqWzZ4U+w@mail.gmail.com> <d32ade7b56bf4651952659307c08893b@usma1ex-dag1mb5.msg.corp.akamai.com> <CANatvzwHtCn8rLB8npf3i7PGyYZhVDRd2uojh5hv3uxtFPEsSA@mail.gmail.com> <58447D8E-782C-431C-8FC3-71124B10A047@trammell.ch> <CACpbDcdfF9w3qqrH1eB0sGU_4vheD9aMP5EXnp1o3Y19N19NUg@mail.gmail.com> <e8b4931a-3931-5b8d-8dad-3ca1939d5542@huitema.net> <CAKcm_gPaj3o-VTdA_0+Kk+nTcVJrYcs_BMyOiDGXKub3gB=GLg@mail.gmail.com> <MWHPR21MB063869878060E850137210FEB6820@MWHPR21MB0638.namprd21.prod.outlook.com> <20180501121906.GA5742@akamai.com> <F63059EA-BA14-4886-A4FB-AA5F04AC164B@akamai.com> <BY2PR15MB07757EAB6A818F1D8D8CCED9CD810@BY2PR15MB0775.namprd15.prod.outlook.com> <CA+9kkMCpxve3CKhQk45YKbvyOyQ6kvzyhpJhrTq1UM-QM+ms2Q@mail.gmail.com> <89893592-7135-4C24-BE1E-4B0FFD1A2E97@trammell.ch> <CA+9kkMCUTRrM9SPEz=Q5GDgU7whryZ1cRdj-O3=GP=-vOr-X+A@mail.gmail.com>
In-Reply-To: <CA+9kkMCUTRrM9SPEz=Q5GDgU7whryZ1cRdj-O3=GP=-vOr-X+A@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.36.2]
Content-Type: multipart/alternative; boundary="_000_ba56bca23f5747e5abdfec137de37481usma1exdag1mb5msgcorpak_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-01_10:, , 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-1711220000 definitions=main-1805010180
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-01_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805010180
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/jluE52AjGXf5QRzKmWFy9CIhV-U>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2018 18:40:13 -0000

--_000_ba56bca23f5747e5abdfec137de37481usma1exdag1mb5msgcorpak_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

ICAqICAgQnV0IGhhdmluZyAgUVVJQyBuZWdvdGlhdGUgdGhpcyBvdXRzaWRlIG9mIHRoZSB2ZXJz
aW9uIGRvZXMgbm90IG1ha2Ugc2Vuc2UgdG8gbWUsIGJlY2F1c2UgdGhlcmUgaXMgbm8gd2F5IGZv
ciBhbiBpbml0aWF0b3Igb3IgYSByZXNwb25kaW5nIHBlZXIgdG8ganVkZ2Ugd2hldGhlciB0aGUg
b3RoZXIgc2lkZSdzIGFzc2VydGlvbiBvZiBzYWZldHkgaXMgd2VsbC1mb3VuZGVkIG9yIGV2ZW4g
d2VsbC1tZWFudC4NCg0KV291bGQgaXQgc2F0aXNmeSB5b3VyIGNvbmNlcm5zLCBpZiBfYm90aF8g
cGVlcnMgbmVlZCB0byBleHByZXNzIGludGVyZXN0IGluIGhhdmluZyBQTkUgb2ZmIGZvciB0aGUg
UE5FIHRvIGJlIOKAnG5lZ290aWF0ZWQgb2Zm4oCdPw0KDQoNCkZyb206IFRlZCBIYXJkaWUgW21h
aWx0bzp0ZWQuaWV0ZkBnbWFpbC5jb21dDQpTZW50OiBUdWVzZGF5LCBNYXkgMDEsIDIwMTggMTo0
NCBQTQ0KVG86IEJyaWFuIFRyYW1tZWxsIChJRVRGKSA8aWV0ZkB0cmFtbWVsbC5jaD4NCkNjOiBQ
cmF2ZWVuIEJhbGFzdWJyYW1hbmlhbiA8cHJhdmI9NDBtaWNyb3NvZnQuY29tQGRtYXJjLmlldGYu
b3JnPjsgSUVURiBRVUlDIFdHIDxxdWljQGlldGYub3JnPjsgUm9iZXJ0byBQZW9uIDxmZW5peEBm
Yi5jb20+OyBTYWx6LCBSaWNoIDxyc2Fsej00MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmc+OyBC
ZW5qYW1pbiBLYWR1ayA8YmthZHVrPTQwYWthbWFpLmNvbUBkbWFyYy5pZXRmLm9yZz4NClN1Ympl
Y3Q6IFJlOiBHZXR0aW5nIHRvIGNvbnNlbnN1cyBvbiBwYWNrZXQgbnVtYmVyIGVuY3J5cHRpb24N
Cg0KT24gVHVlLCBNYXkgMSwgMjAxOCBhdCA5OjU2IEFNLCBCcmlhbiBUcmFtbWVsbCAoSUVURikg
PGlldGZAdHJhbW1lbGwuY2g8bWFpbHRvOmlldGZAdHJhbW1lbGwuY2g+PiB3cm90ZToNCmhpIFRl
ZCwgYWxsLA0KDQpBdCB0aGlzIHBvaW50IEkndmUgcHJldHR5IG11Y2ggY29tZSBhcm91bmQgdG8g
dGhlIG9waW5pb24gd2Ugc2hvdWxkIGp1c3QgbGFuZCAxMDc5IGFuZCBkaXNjdXNzIHRoZSByZXN0
LCBidXQgdGhpcyBjb252ZXJzYXRpb24gY29udGludWVzIHRvIGhhdmUgbWUgd29ycmllZCB0aGF0
IHdlJ3JlIGNvbWluZyB0byBjb25zZW5zdXMgb24gYSBmZWF0dXJlIHdlIGRvIG5vdCBmdWxseSB1
bmRlcnN0YW5kIHRoZSBhcHBsaWNhYmlsaXR5IGFuZCBsaW1pdGF0aW9ucyBvZi4NCkkgYWxzbyB0
aGluayB0aGF0IGp1c3QgbGFuZGluZyAxMDc5IGFuZCBtb3Zpbmcgb24gaXMgdGhlIHJpZ2h0IHRo
aW5nIHRvIGRvLg0KDQpQTkUncyBwcmltYXJ5IHV0aWxpdHkgaXMgYW50aS1vc3NpZmljYXRpb24u
IFdoaWxlIGl0IHJlZHVjZXMgdGhlIGFtb3VudCBvZiBpbmZvcm1hdGlvbiBhdmFpbGFibGUgdG8g
YW4gYXR0YWNrZXIgYXR0ZW1wdGluZyB0byBhY2hpZXZlIGxpbmthYmlsaXR5IG9mIGZsb3dzIGFj
cm9zcyBhIHB1cnBvc2VmdWwgcGF0aCBtaWdyYXRpb24sIG9yIHdpdGggYSBzaW5nbGUtUE4tc3Bh
Y2UgbXVsdGlwYXRoIGRlc2lnbiwgaXQgZG9lcyBub3QgZWxpbWluYXRlIGl0LCBzbyBleHBlY3Rp
bmcgbW9yZSB0aGFuIGEgbWFyZ2luYWwgcHJpdmFjeSBiZW5lZml0IGZyb20gdGhlIGZlYXR1cmUg
cGVyIHNlIGlzIHNldHRpbmcgb25lc2VsZiB1cCBmb3IgZGlzYXBwb2ludG1lbnQuDQoNClRoZSBy
ZWFzb24gdG8gZGlzYWJsZSBQTkUgaW4gKGFkbWl0dGVkbHkgaWxsLWRlZmluZWQpICJkYXRhY2Vu
dGVyIiBlbnZpcm9ubWVudHMgaXMgdG8gdHJhZGUgb2ZmIHRoZSAofjElaXNoKSBvdmVyaGVhZCBm
b3Igb3NzaWZpY2F0aW9uIHByb3RlY3Rpb24geW91IGtub3cgeW91IGRvbid0IG5lZWQgYmVjYXVz
ZSB5b3UgZGlkbid0IGRlcGxveSBhbnl0aGluZyB0aGF0IHRyaWVzIHRvIGFidXNlIHRoZSBwYWNr
ZXQgbnVtYmVyLg0KDQoob24gd2hpY2gsIG1vcmUgYmVsb3c7IGFuZCBvbiBwcmV2aWV3LCB3aGF0
IFByYXZlZW4gc2FpZCkNCg0KPiBPbiAxIE1heSAyMDE4LCBhdCAxNzo1NSwgVGVkIEhhcmRpZSA8
dGVkLmlldGZAZ21haWwuY29tPG1haWx0bzp0ZWQuaWV0ZkBnbWFpbC5jb20+PiB3cm90ZToNCj4N
Cj4gT24gVHVlLCBNYXkgMSwgMjAxOCBhdCA4OjEzIEFNLCBSb2JlcnRvIFBlb24gPGZlbml4QGZi
LmNvbTxtYWlsdG86ZmVuaXhAZmIuY29tPj4gd3JvdGU6DQo+IEFsc28sIFByaXNtLg0KPg0KPiAt
PVINCj4NCj4NCj4NCj4gVGhhdCdzIGEgbGl0dGxlIG1vcmUgc3VjY2luY3QgdGhhbiBJIHdvdWxk
IGJlLCBidXQgeWVzLiAgSG93IGRvZXMgYW4gYXBwbGljYXRpb24ga25vdyB0aGF0IHRoZSBmbG93
IGl0IGlzIGluaXRpYXRpbmcgd2lsbCB0cmF2ZXJzZSBhIHRvcG9sb2d5IHRoYXQgaXMgZGVlbWVk
IHRvIGJlIHdpdGhpbiBhIGNvbnRyb2xsZWQgZW52aXJvbm1lbnQ/ICBZb3UgY2FuIHNheSAiY29u
ZmlndXJhdGlvbiIgYnV0IEkgZmVhciBpdCB3aWxsIHR1cm4gdXAgb24gYSBwb3N0LWl0ICBpZiB5
b3UgZG8uICBMb2FkcyBzaGlmdCwgcmVzb3VyY2VzIG1vdmUsIGFuZCBzdWRkZW5seSB5b3UgZmlu
ZCB0aGF0IGhvc3Qgd2hpY2ggdXNlZCB0byBiZSBpbiB0aGUgc2FtZSByYWNrLCBiZWluZyBkb3du
LCBoYXMgbG9hZC1zaGlmdGVkIHRvIHRoZSBuZXh0IGluc3RhbmNlLCAgaW4gYSBkYXRhY2VudGVy
IDUwMCBtaWxlcyBhd2F5IGFjcm9zcyBhIHZlcnkgZGlmZmVyZW50IG5ldHdvcmsuDQo+DQo+IE1h
bnkgbW9kZXJuIGRlcGxveW1lbnRzIGFyZSBhbHNvIGluIHNvbWVvbmUgZWxzZSdzIGRhdGEgY2Vu
dGVyLCBzbyBzYXlpbmcgIkRhdGEgY2VudGVyIG5ldHdvcmtzIiBkb2Vzbid0IHNheSBtdWNoIGFi
b3V0IHdoeSB5b3UncmUgdHJ1c3RpbmcgdGhlIG5ldHdvcmsgaW5zaWRlLg0KDQpUaGUgImxvYWQt
c2hpZnRlZCB0byB0aGUgbmV4dCBpbnN0YW5jZSIgZXhhbXBsZSBpcyBhbiBpbnRlcmVzdGluZyBv
bmUgaWZmIHNhaWQgbG9hZCBzaGlmdGluZyBjYXVzZXMgdGhlIHRyYWZmaWMgdGhhdCB1c2VkIHRv
IGNyb3NzIGEgcHJpdmF0ZSBuZXR3b3JrIHRvIHRyYW5zaXQgdGhlIG9wZW4gSW50ZXJuZXQgaW5z
dGVhZC4NCg0KV2VsbCwgYSBsb25nLWhhdWwgbGluaywgY2VydGFpbmx5LiAgVGhhdCBtYXkgb3Ig
bWF5IG5vdCBiZSAidGhlIG9wZW4gSW50ZXJuZXQiIGFuZCB0aGUgY2hhbmNlcyBvZiBpdCB0cmF2
ZXJzaW5nIGEgY29tcGxldGVseSB1bmtub3duIG1pZGRsZWJveCBhcmUgbG93LiAgVGhlIGNoYW5j
ZXMgb2YgaXQgcGFzc2luZyBieSBhbiB1bmtub3duIG9ic2VydmVyLCBvbiB0aGUgb3RoZXIgaGFu
ZCwgYXJlIG5vdCBjdXJyZW50bHkga25vd24gYnV0IGFyZSBwcmVzdW1lZCB0byBiZSBoaWdoLg0K
DQpJcyB0aGlzIGEgdGhpbmcgdGhhdCBldmVyIGhhcHBlbnMgaW4gYW55IG9mIHRoZSBlbnZpcm9u
bWVudHMgdGhhdCBnZXQgY2FsbGVkICJkYXRhY2VudGVyIiBmb3IgbmV0d29ya2luZyB0ZWNobm9s
b2d5IHB1cnBvc2VzPw0KDQpTbywgdGhlIHdheSBJIGxvb2sgYXQgdGhpcyBib2lscyBkb3duIHRv
Og0KSWYgdGhlIGxpbmthYmlsaXR5IG9yIG9zc2lmaWNhdGlvbiBjb25jZXJucyB3aXRoIHBhY2tl
dCBudW1iZXJzIGluIHRoZSBjbGVhciBhcmUganVzdGlmaWVkLCB5b3UgZWl0aGVyIG5lZWQgdG8g
aGF2ZSBpdCBvbiBhbGwgdGhlIHRpbWUgb3IgaGF2ZSB2ZXJ5IGNsZWFyIG1ldGhvZHMgZm9yIGRl
dGVybWluaW5nIHdoZW4gdGhlIGNvbmNlcm5zIGFyZSBub3QgcHJlc2VudC4gIFRoZSBwcm90b2Nv
bCBpcyBub3QgYXdhcmUgb2YgdGhlIGwyIG9yIGwzIHRvcG9sb2d5IGJldHdlZW4gYW4gaW5pdGlh
dG9yIGFuZCBpdHMgcGVlciwgbXVjaCBsZXNzIHRoZSBtYW5hZ2VtZW50IG9mIHRoYXQgcGF0aC4N
Cg0KU28gdGhlIGNsZWFyIG1ldGhvZHMgZm9yIGRldGVybWluYXRpb24gcmVhbGx5IGJvaWwgZG93
biB0byAic29tZW9uZSB0dXJucyB0aGlzIG9mZiB3aGVuIHRoZXkgdGhpbmsgaXQgaXMgcmlnaHQg
dG8gZG8gc28iLiAgRmxvd3MgZW50aXJlbHkgd2l0aGluIHRoZSBkb21haW4gb2YgY29udHJvbCBv
ZiBhIHNpbmdsZSBwcm92aWRlciBtaWdodCBiZSBhIGNhc2Ugd2hlcmUgZm9sa3MgdGhpbmsgaXQg
aXMgcmlnaHQgdG8gZG8gc28uICBBIHN1YnNldCBvZiB0aGF0IGRvbWFpbiBvZiBjb250cm9sIGlz
IHdoZW4gdGhlIGZsb3cgaGFzIG5vIGxvbmctaGF1bCBsaW5rcyAoZm9yIGhvd2V2ZXIgeW91IHdh
bnQgdG8gZGVmaW5lIHRoYXQpLCB0aGUgc2hvcnRoYW5kIGZvciB3aGljaCBpcyAiZGF0YWNlbnRl
ciBuZXR3b3JrIiAodGhvdWdoIGl0IG1pZ2h0IHdlbGwgYWxzbyBiZSBhIHNtYWxsIGNvbXBsZXgg
b2YgZGF0YWNlbnRlcnMsIGFuIGVudGVycHJpc2UgY2FtcHVzLCBvciBzaW1pbGFyKS4gIEJ1dCB0
aGUga2V5IGlzIHRoYXQgeW91IGJlbGlldmUgdGhhdCB0aGUgdG9wb2xvZ3kgYmV0d2VlbiBwZWVy
IEEgYW5kIHBlZXIgQiBoYXMgbm8gbWlkZGxlYm94ZXMgb3V0c2lkZSBvZiB0aGUgc2hhcmVkIGRv
bWFpbiBvZiBjb250cm9sIHRoYXQgbWlnaHQgb3NzaWZ5IHRoZSBiZWhhdmlvciBhbmQgbm8gb2Jz
ZXJ2ZXJzIHdob3NlIHVzZSBvZiB0aGlzIGRhdGEgY29uY2VybnMgeW91Lg0KSWYgeW91IGNvbnRy
b2wgYm90aCBwZWVycyBhbmQgdGhlIG5ldHdvcmsgYmV0d2VlbiB0aGVtLCB1c2luZyBhIFFVSUMg
dmVyc2lvbiB3aGVyZSB0aGlzIGlzIGFsd2F5cyB0dXJuZWQgb2ZmIG1pZ2h0IG1ha2Ugc2Vuc2Uu
ICBCdXQgaGF2aW5nICBRVUlDIG5lZ290aWF0ZSB0aGlzIG91dHNpZGUgb2YgdGhlIHZlcnNpb24g
ZG9lcyBub3QgbWFrZSBzZW5zZSB0byBtZSwgYmVjYXVzZSB0aGVyZSBpcyBubyB3YXkgZm9yIGFu
IGluaXRpYXRvciBvciBhIHJlc3BvbmRpbmcgcGVlciB0byBqdWRnZSB3aGV0aGVyIHRoZSBvdGhl
ciBzaWRlJ3MgYXNzZXJ0aW9uIG9mIHNhZmV0eSBpcyB3ZWxsLWZvdW5kZWQgb3IgZXZlbiB3ZWxs
LW1lYW50LiAgSWYgaXQgaGFzIG5vIGluZGVwZW5kZW50IGRhdGEgb24gdGhpcyAoYW5kIHRoZSBw
cm90b2NvbCBwcm92aWRlcyBub25lKSwgdGhpcyBhbGxvd3Mgb25lIHNpZGUgb3IgdGhlIG90aGVy
IHRvIHVuaWxhdGVyYWxseSB0dXJuIG9mZiBhbiBhbnRpLW9zc2lmaWNhdGlvbiBhbmQgYW50aS1s
aW5rYWJpbGl0eSBmZWF0dXJlIGZvciB3aGF0ZXZlciBnYWluIGl0IHdhbnRzLiAgU2luY2Ugd2Un
cmUgdHJ5aW5nIHRvIG9wdGltaXplIGZvciB0aGUgbG9uZy10ZXJtIGZsZXhpYmlsaXR5IG9mIHRo
ZSBwcm90b2NvbCwgYWxsb3dpbmcgdGhhdCBwYXJ0aWN1bGFyIHBvaW50IG9wdGltaXphdGlvbiBz
ZWVtcyBjb250cmFyeSB0byBvdXIgaW50ZXJlc3RzLCBtdWNoIGxlc3MgdGhlIHByaXZhY3kgaW50
ZXJlc3RzIG9mIHRoZSBwZWVycy4NCg0KcmVnYXJkcywNClRlZA0KDQpDaGVlcnMsDQoNCkJyaWFu
DQoNCj4gVGVkDQo+DQo+IFNlbnQgdmlhIHRoZSBTYW1zdW5nIEdhbGF4eSBTNywgYW4gQVQmVCA0
RyBMVEUgc21hcnRwaG9uZQ0KPg0KPg0KPiAtLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0t
LS0tDQo+IEZyb206ICJTYWx6LCBSaWNoIiA8cnNhbHo9NDBha2FtYWkuY29tQGRtYXJjLmlldGYu
b3JnPG1haWx0bzo0MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmc+Pg0KPiBEYXRlOiA1LzEvMTgg
NToyNSBBTSAoR01ULTA4OjAwKQ0KPiBUbzogQmVuamFtaW4gS2FkdWsgPGJrYWR1az00MGFrYW1h
aS5jb21AZG1hcmMuaWV0Zi5vcmc8bWFpbHRvOjQwYWthbWFpLmNvbUBkbWFyYy5pZXRmLm9yZz4+
LCBQcmF2ZWVuIEJhbGFzdWJyYW1hbmlhbiA8cHJhdmI9NDBtaWNyb3NvZnQuY29tQGRtYXJjLmll
dGYub3JnPG1haWx0bzo0MG1pY3Jvc29mdC5jb21AZG1hcmMuaWV0Zi5vcmc+Pg0KPiBDYzogSUVU
RiBRVUlDIFdHIDxxdWljQGlldGYub3JnPG1haWx0bzpxdWljQGlldGYub3JnPj4NCj4gU3ViamVj
dDogUmU6IEdldHRpbmcgdG8gY29uc2Vuc3VzIG9uIHBhY2tldCBudW1iZXIgZW5jcnlwdGlvbg0K
Pg0KPiAgICAgPiBJIGRpc2FncmVlIHRoYXQgd2UgbmVlZCBhbnkgbW9yZSBkYXRhIGZvciBub3Qg
ZG9pbmcgUE5FIGluIHRoZSBkYXRhY2VudGVyLiBXaHkgd291bGQgd2UgYWRkIGFuIGV4dHJhIGVu
Y3J5cHQtZGVjcnlwdCBzdGVwIGZvciBubyBvYnZpb3VzIGJlbmVmaXQ/DQo+DQo+IEkgYW0gY29u
Y2VybmVkIHRoYXQgcGVvcGxlIHdpbGwgbWlzLWludGVycHJldCB0aGUgbWVhbmluZyBvZiBhIGRh
dGFjZW50ZXIsIGFuZCB0aGluayB0aGF0IGEgYnVuY2ggb2Ygc2VydmVycywgb3IgZXZlbiBhIHJh
Y2ssIGluIGFuIG9wZW4gY29sbyBzcGFjZSBpcyBhICJkYXRhY2VudGVyLiIgIENvbXB1dGVycyBr
ZWVwIGdldHRpbmcgZmFzdGVyLg0KPg0KPg0KDQo=

--_000_ba56bca23f5747e5abdfec137de37481usma1exdag1mb5msgcorpak_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMg
MiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1
IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZp
c2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5
Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvTGlz
dFBhcmFncmFwaCwgbGkuTXNvTGlzdFBhcmFncmFwaCwgZGl2Lk1zb0xpc3RQYXJhZ3JhcGgNCgl7
bXNvLXN0eWxlLXByaW9yaXR5OjM0Ow0KCW1hcmdpbi10b3A6MGluOw0KCW1hcmdpbi1yaWdodDow
aW47DQoJbWFyZ2luLWJvdHRvbTowaW47DQoJbWFyZ2luLWxlZnQ6LjVpbjsNCgltYXJnaW4tYm90
dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
c2Fucy1zZXJpZjt9DQpwLm1zb25vcm1hbDAsIGxpLm1zb25vcm1hbDAsIGRpdi5tc29ub3JtYWww
DQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsN
CgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdp
bi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFs
LXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRv
d3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJ
Zm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJ
e3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpk
aXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi8qIExpc3QgRGVmaW5pdGlv
bnMgKi8NCkBsaXN0IGwwDQoJe21zby1saXN0LWlkOjE3MTkyODQ4NjE7DQoJbXNvLWxpc3QtdHlw
ZTpoeWJyaWQ7DQoJbXNvLWxpc3QtdGVtcGxhdGUtaWRzOjEwNDgyMDUwMDQgODM5OTY3MjE2IDY3
Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3Njk4
NjkxIDY3Njk4NjkzO30NCkBsaXN0IGwwOmxldmVsMQ0KCXttc28tbGV2ZWwtc3RhcnQtYXQ6MDsN
Cgltc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674OYOw0K
CW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVm
dDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzOw0KCW1zby1m
YXJlYXN0LWZvbnQtZmFtaWx5OkNhbGlicmk7DQoJbXNvLWJpZGktZm9udC1mYW1pbHk6IlRpbWVz
IE5ldyBSb21hbiI7fQ0KQGxpc3QgbDA6bGV2ZWwyDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0
OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0K
CW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJ
Zm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMDpsZXZlbDMNCgl7bXNvLWxldmVs
LW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwt
dGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1p
bmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMDpsZXZlbDQN
Cgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsN
Cgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxl
ZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBs
MDpsZXZlbDUNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10
ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3Np
dGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseToiQ291cmllciBO
ZXciO30NCkBsaXN0IGwwOmxldmVsNg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7
DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1s
ZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1m
YW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwwOmxldmVsNw0KCXttc28tbGV2ZWwtbnVtYmVyLWZv
cm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDpu
b25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1
aW47DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwwOmxldmVsOA0KCXttc28tbGV2ZWwt
bnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwtdGFi
LXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRl
bnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6bGV2ZWw5
DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7
DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjps
ZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0Kb2wN
Cgl7bWFyZ2luLWJvdHRvbTowaW47fQ0KdWwNCgl7bWFyZ2luLWJvdHRvbTowaW47fQ0KLS0+PC9z
dHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVk
aXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28g
OV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJl
ZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9o
ZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRp
diBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjx1bCBzdHlsZT0ibWFyZ2luLXRvcDowaW4iIHR5cGU9
ImRpc2MiPg0KPGxpIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBoIiBzdHlsZT0ibWFyZ2luLWxlZnQ6
MGluO21zby1saXN0OmwwIGxldmVsMSBsZm8xIj5CdXQgaGF2aW5nJm5ic3A7IFFVSUMgbmVnb3Rp
YXRlIHRoaXMgb3V0c2lkZSBvZiB0aGUgdmVyc2lvbiBkb2VzIG5vdCBtYWtlIHNlbnNlIHRvIG1l
LCBiZWNhdXNlIHRoZXJlIGlzIG5vIHdheSBmb3IgYW4gaW5pdGlhdG9yIG9yIGEgcmVzcG9uZGlu
ZyBwZWVyIHRvIGp1ZGdlIHdoZXRoZXIgdGhlIG90aGVyIHNpZGUncyBhc3NlcnRpb24NCiBvZiBz
YWZldHkgaXMgd2VsbC1mb3VuZGVkIG9yIGV2ZW4gd2VsbC1tZWFudC48bzpwPjwvbzpwPjwvbGk+
PC91bD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+V291bGQgaXQgc2F0aXNmeSB5b3VyIGNvbmNlcm5zLCBpZiBfYm90aF8g
cGVlcnMgbmVlZCB0byBleHByZXNzIGludGVyZXN0IGluIGhhdmluZyBQTkUgb2ZmIGZvciB0aGUg
UE5FIHRvIGJlIOKAnG5lZ290aWF0ZWQgb2Zm4oCdPw0KPG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+RnJvbTo8L2I+
IFRlZCBIYXJkaWUgW21haWx0bzp0ZWQuaWV0ZkBnbWFpbC5jb21dIDxicj4NCjxiPlNlbnQ6PC9i
PiBUdWVzZGF5LCBNYXkgMDEsIDIwMTggMTo0NCBQTTxicj4NCjxiPlRvOjwvYj4gQnJpYW4gVHJh
bW1lbGwgKElFVEYpICZsdDtpZXRmQHRyYW1tZWxsLmNoJmd0Ozxicj4NCjxiPkNjOjwvYj4gUHJh
dmVlbiBCYWxhc3VicmFtYW5pYW4gJmx0O3ByYXZiPTQwbWljcm9zb2Z0LmNvbUBkbWFyYy5pZXRm
Lm9yZyZndDs7IElFVEYgUVVJQyBXRyAmbHQ7cXVpY0BpZXRmLm9yZyZndDs7IFJvYmVydG8gUGVv
biAmbHQ7ZmVuaXhAZmIuY29tJmd0OzsgU2FseiwgUmljaCAmbHQ7cnNhbHo9NDBha2FtYWkuY29t
QGRtYXJjLmlldGYub3JnJmd0OzsgQmVuamFtaW4gS2FkdWsgJmx0O2JrYWR1az00MGFrYW1haS5j
b21AZG1hcmMuaWV0Zi5vcmcmZ3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBHZXR0aW5nIHRv
IGNvbnNlbnN1cyBvbiBwYWNrZXQgbnVtYmVyIGVuY3J5cHRpb248bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPk9uIFR1ZSwgTWF5IDEsIDIwMTggYXQgOTo1NiBBTSwgQnJpYW4gVHJhbW1l
bGwgKElFVEYpICZsdDs8YSBocmVmPSJtYWlsdG86aWV0ZkB0cmFtbWVsbC5jaCIgdGFyZ2V0PSJf
YmxhbmsiPmlldGZAdHJhbW1lbGwuY2g8L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxk
aXY+DQo8ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNv
bGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0
LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJn
aW4tYm90dG9tOjEyLjBwdCI+aGkgVGVkLCBhbGwsPGJyPg0KPGJyPg0KQXQgdGhpcyBwb2ludCBJ
J3ZlIHByZXR0eSBtdWNoIGNvbWUgYXJvdW5kIHRvIHRoZSBvcGluaW9uIHdlIHNob3VsZCBqdXN0
IGxhbmQgMTA3OSBhbmQgZGlzY3VzcyB0aGUgcmVzdCwgYnV0IHRoaXMgY29udmVyc2F0aW9uIGNv
bnRpbnVlcyB0byBoYXZlIG1lIHdvcnJpZWQgdGhhdCB3ZSdyZSBjb21pbmcgdG8gY29uc2Vuc3Vz
IG9uIGEgZmVhdHVyZSB3ZSBkbyBub3QgZnVsbHkgdW5kZXJzdGFuZCB0aGUgYXBwbGljYWJpbGl0
eSBhbmQgbGltaXRhdGlvbnMNCiBvZi48bzpwPjwvbzpwPjwvcD4NCjwvYmxvY2txdW90ZT4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIGFsc28gdGhpbmsgdGhhdCBqdXN0IGxhbmRpbmcg
MTA3OSBhbmQgbW92aW5nIG9uIGlzIHRoZSByaWdodCB0aGluZyB0byBkby48bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6
c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0
OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+UE5FJ3MgcHJp
bWFyeSB1dGlsaXR5IGlzIGFudGktb3NzaWZpY2F0aW9uLiBXaGlsZSBpdCByZWR1Y2VzIHRoZSBh
bW91bnQgb2YgaW5mb3JtYXRpb24gYXZhaWxhYmxlIHRvIGFuIGF0dGFja2VyIGF0dGVtcHRpbmcg
dG8gYWNoaWV2ZSBsaW5rYWJpbGl0eSBvZiBmbG93cyBhY3Jvc3MgYSBwdXJwb3NlZnVsIHBhdGgg
bWlncmF0aW9uLCBvciB3aXRoIGEgc2luZ2xlLVBOLXNwYWNlIG11bHRpcGF0aCBkZXNpZ24sIGl0
DQogZG9lcyBub3QgZWxpbWluYXRlIGl0LCBzbyBleHBlY3RpbmcgbW9yZSB0aGFuIGEgbWFyZ2lu
YWwgcHJpdmFjeSBiZW5lZml0IGZyb20gdGhlIGZlYXR1cmUgcGVyIHNlIGlzIHNldHRpbmcgb25l
c2VsZiB1cCBmb3IgZGlzYXBwb2ludG1lbnQuPGJyPg0KPGJyPg0KVGhlIHJlYXNvbiB0byBkaXNh
YmxlIFBORSBpbiAoYWRtaXR0ZWRseSBpbGwtZGVmaW5lZCkgJnF1b3Q7ZGF0YWNlbnRlciZxdW90
OyBlbnZpcm9ubWVudHMgaXMgdG8gdHJhZGUgb2ZmIHRoZSAofjElaXNoKSBvdmVyaGVhZCBmb3Ig
b3NzaWZpY2F0aW9uIHByb3RlY3Rpb24geW91IGtub3cgeW91IGRvbid0IG5lZWQgYmVjYXVzZSB5
b3UgZGlkbid0IGRlcGxveSBhbnl0aGluZyB0aGF0IHRyaWVzIHRvIGFidXNlIHRoZSBwYWNrZXQg
bnVtYmVyLjxicj4NCjxicj4NCihvbiB3aGljaCwgbW9yZSBiZWxvdzsgYW5kIG9uIHByZXZpZXcs
IHdoYXQgUHJhdmVlbiBzYWlkKTxicj4NCjxicj4NCiZndDsgT24gMSBNYXkgMjAxOCwgYXQgMTc6
NTUsIFRlZCBIYXJkaWUgJmx0OzxhIGhyZWY9Im1haWx0bzp0ZWQuaWV0ZkBnbWFpbC5jb20iPnRl
ZC5pZXRmQGdtYWlsLmNvbTwvYT4mZ3Q7IHdyb3RlOjxicj4NCiZndDsgPGJyPg0KJmd0OyBPbiBU
dWUsIE1heSAxLCAyMDE4IGF0IDg6MTMgQU0sIFJvYmVydG8gUGVvbiAmbHQ7PGEgaHJlZj0ibWFp
bHRvOmZlbml4QGZiLmNvbSI+ZmVuaXhAZmIuY29tPC9hPiZndDsgd3JvdGU6PGJyPg0KJmd0OyBB
bHNvLCBQcmlzbS48YnI+DQomZ3Q7IDxicj4NCiZndDsgLT1SPGJyPg0KJmd0OyA8YnI+DQomZ3Q7
IDxicj4NCiZndDsgPGJyPg0KJmd0OyBUaGF0J3MgYSBsaXR0bGUgbW9yZSBzdWNjaW5jdCB0aGFu
IEkgd291bGQgYmUsIGJ1dCB5ZXMuJm5ic3A7IEhvdyBkb2VzIGFuIGFwcGxpY2F0aW9uIGtub3cg
dGhhdCB0aGUgZmxvdyBpdCBpcyBpbml0aWF0aW5nIHdpbGwgdHJhdmVyc2UgYSB0b3BvbG9neSB0
aGF0IGlzIGRlZW1lZCB0byBiZSB3aXRoaW4gYSBjb250cm9sbGVkIGVudmlyb25tZW50PyZuYnNw
OyBZb3UgY2FuIHNheSAmcXVvdDtjb25maWd1cmF0aW9uJnF1b3Q7IGJ1dCBJIGZlYXIgaXQgd2ls
bCB0dXJuIHVwIG9uDQogYSBwb3N0LWl0Jm5ic3A7IGlmIHlvdSBkby4mbmJzcDsgTG9hZHMgc2hp
ZnQsIHJlc291cmNlcyBtb3ZlLCBhbmQgc3VkZGVubHkgeW91IGZpbmQgdGhhdCBob3N0IHdoaWNo
IHVzZWQgdG8gYmUgaW4gdGhlIHNhbWUgcmFjaywgYmVpbmcgZG93biwgaGFzIGxvYWQtc2hpZnRl
ZCB0byB0aGUgbmV4dCBpbnN0YW5jZSwmbmJzcDsgaW4gYSBkYXRhY2VudGVyIDUwMCBtaWxlcyBh
d2F5IGFjcm9zcyBhIHZlcnkgZGlmZmVyZW50IG5ldHdvcmsuPGJyPg0KJmd0OyA8YnI+DQomZ3Q7
IE1hbnkgbW9kZXJuIGRlcGxveW1lbnRzIGFyZSBhbHNvIGluIHNvbWVvbmUgZWxzZSdzIGRhdGEg
Y2VudGVyLCBzbyBzYXlpbmcgJnF1b3Q7RGF0YSBjZW50ZXIgbmV0d29ya3MmcXVvdDsgZG9lc24n
dCBzYXkgbXVjaCBhYm91dCB3aHkgeW91J3JlIHRydXN0aW5nIHRoZSBuZXR3b3JrIGluc2lkZS48
YnI+DQo8YnI+DQpUaGUgJnF1b3Q7bG9hZC1zaGlmdGVkIHRvIHRoZSBuZXh0IGluc3RhbmNlJnF1
b3Q7IGV4YW1wbGUgaXMgYW4gaW50ZXJlc3Rpbmcgb25lIGlmZiBzYWlkIGxvYWQgc2hpZnRpbmcg
Y2F1c2VzIHRoZSB0cmFmZmljIHRoYXQgdXNlZCB0byBjcm9zcyBhIHByaXZhdGUgbmV0d29yayB0
byB0cmFuc2l0IHRoZSBvcGVuIEludGVybmV0IGluc3RlYWQuPG86cD48L286cD48L3A+DQo8L2Js
b2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5XZWxsLCBhIGxvbmctaGF1
bCBsaW5rLCBjZXJ0YWlubHkuJm5ic3A7IFRoYXQgbWF5IG9yIG1heSBub3QgYmUgJnF1b3Q7dGhl
IG9wZW4gSW50ZXJuZXQmcXVvdDsgYW5kIHRoZSBjaGFuY2VzIG9mIGl0IHRyYXZlcnNpbmcgYSBj
b21wbGV0ZWx5IHVua25vd24gbWlkZGxlYm94IGFyZSBsb3cuJm5ic3A7IFRoZSBjaGFuY2VzIG9m
IGl0IHBhc3NpbmcgYnkgYW4gdW5rbm93biBvYnNlcnZlciwgb24gdGhlIG90aGVyIGhhbmQsIGFy
ZSBub3QgY3VycmVudGx5DQoga25vd24gYnV0IGFyZSBwcmVzdW1lZCB0byBiZSBoaWdoLjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFy
Z2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPklzIHRoaXMgYSB0aGluZyB0aGF0IGV2ZXIgaGFw
cGVucyBpbiBhbnkgb2YgdGhlIGVudmlyb25tZW50cyB0aGF0IGdldCBjYWxsZWQgJnF1b3Q7ZGF0
YWNlbnRlciZxdW90OyBmb3IgbmV0d29ya2luZyB0ZWNobm9sb2d5IHB1cnBvc2VzPzxvOnA+PC9v
OnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij5TbywgdGhlIHdheSBJIGxvb2sgYXQgdGhpcyBib2ls
cyBkb3duIHRvOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij5JZiB0aGUgbGlua2FiaWxpdHkgb3Ig
b3NzaWZpY2F0aW9uIGNvbmNlcm5zIHdpdGggcGFja2V0IG51bWJlcnMgaW4gdGhlIGNsZWFyIGFy
ZSBqdXN0aWZpZWQsIHlvdSBlaXRoZXIgbmVlZCB0byBoYXZlIGl0IG9uIGFsbCB0aGUgdGltZSBv
ciBoYXZlIHZlcnkgY2xlYXIgbWV0aG9kcyBmb3IgZGV0ZXJtaW5pbmcgd2hlbiB0aGUgY29uY2Vy
bnMgYXJlIG5vdCBwcmVzZW50LiZuYnNwOw0KIFRoZSBwcm90b2NvbCBpcyBub3QgYXdhcmUgb2Yg
dGhlIGwyIG9yIGwzIHRvcG9sb2d5IGJldHdlZW4gYW4gaW5pdGlhdG9yIGFuZCBpdHMgcGVlciwg
bXVjaCBsZXNzIHRoZSBtYW5hZ2VtZW50IG9mIHRoYXQgcGF0aC4mbmJzcDsNCjxicj4NCjxicj4N
ClNvIHRoZSBjbGVhciBtZXRob2RzIGZvciBkZXRlcm1pbmF0aW9uIHJlYWxseSBib2lsIGRvd24g
dG8gJnF1b3Q7c29tZW9uZSB0dXJucyB0aGlzIG9mZiB3aGVuIHRoZXkgdGhpbmsgaXQgaXMgcmln
aHQgdG8gZG8gc28mcXVvdDsuJm5ic3A7IEZsb3dzIGVudGlyZWx5IHdpdGhpbiB0aGUgZG9tYWlu
IG9mIGNvbnRyb2wgb2YgYSBzaW5nbGUgcHJvdmlkZXIgbWlnaHQgYmUgYSBjYXNlIHdoZXJlIGZv
bGtzIHRoaW5rIGl0IGlzIHJpZ2h0IHRvIGRvIHNvLiZuYnNwOyBBIHN1YnNldCBvZg0KIHRoYXQg
ZG9tYWluIG9mIGNvbnRyb2wgaXMgd2hlbiB0aGUgZmxvdyBoYXMgbm8gbG9uZy1oYXVsIGxpbmtz
IChmb3IgaG93ZXZlciB5b3Ugd2FudCB0byBkZWZpbmUgdGhhdCksIHRoZSBzaG9ydGhhbmQgZm9y
IHdoaWNoIGlzICZxdW90O2RhdGFjZW50ZXIgbmV0d29yayZxdW90OyAodGhvdWdoIGl0IG1pZ2h0
IHdlbGwgYWxzbyBiZSBhIHNtYWxsIGNvbXBsZXggb2YgZGF0YWNlbnRlcnMsIGFuIGVudGVycHJp
c2UgY2FtcHVzLCBvciBzaW1pbGFyKS4mbmJzcDsgQnV0IHRoZQ0KIGtleSBpcyB0aGF0IHlvdSBi
ZWxpZXZlIHRoYXQgdGhlIHRvcG9sb2d5IGJldHdlZW4gcGVlciBBIGFuZCBwZWVyIEIgaGFzIG5v
IG1pZGRsZWJveGVzIG91dHNpZGUgb2YgdGhlIHNoYXJlZCBkb21haW4gb2YgY29udHJvbCB0aGF0
IG1pZ2h0IG9zc2lmeSB0aGUgYmVoYXZpb3IgYW5kIG5vIG9ic2VydmVycyB3aG9zZSB1c2Ugb2Yg
dGhpcyBkYXRhIGNvbmNlcm5zIHlvdS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPklmIHlvdSBjb250cm9sIGJvdGggcGVlcnMgYW5kIHRoZSBuZXR3
b3JrIGJldHdlZW4gdGhlbSwgdXNpbmcgYSBRVUlDIHZlcnNpb24gd2hlcmUgdGhpcyBpcyBhbHdh
eXMgdHVybmVkIG9mZiBtaWdodCBtYWtlIHNlbnNlLiZuYnNwOyBCdXQgaGF2aW5nJm5ic3A7IFFV
SUMgbmVnb3RpYXRlIHRoaXMgb3V0c2lkZSBvZiB0aGUgdmVyc2lvbiBkb2VzIG5vdCBtYWtlIHNl
bnNlIHRvIG1lLCBiZWNhdXNlIHRoZXJlIGlzIG5vIHdheSBmb3INCiBhbiBpbml0aWF0b3Igb3Ig
YSByZXNwb25kaW5nIHBlZXIgdG8ganVkZ2Ugd2hldGhlciB0aGUgb3RoZXIgc2lkZSdzIGFzc2Vy
dGlvbiBvZiBzYWZldHkgaXMgd2VsbC1mb3VuZGVkIG9yIGV2ZW4gd2VsbC1tZWFudC4mbmJzcDsg
SWYgaXQgaGFzIG5vIGluZGVwZW5kZW50IGRhdGEgb24gdGhpcyAoYW5kIHRoZSBwcm90b2NvbCBw
cm92aWRlcyBub25lKSwgdGhpcyBhbGxvd3Mgb25lIHNpZGUgb3IgdGhlIG90aGVyIHRvIHVuaWxh
dGVyYWxseSB0dXJuIG9mZg0KIGFuIGFudGktb3NzaWZpY2F0aW9uIGFuZCBhbnRpLWxpbmthYmls
aXR5IGZlYXR1cmUgZm9yIHdoYXRldmVyIGdhaW4gaXQgd2FudHMuJm5ic3A7IFNpbmNlIHdlJ3Jl
IHRyeWluZyB0byBvcHRpbWl6ZSBmb3IgdGhlIGxvbmctdGVybSBmbGV4aWJpbGl0eSBvZiB0aGUg
cHJvdG9jb2wsIGFsbG93aW5nIHRoYXQgcGFydGljdWxhciBwb2ludCBvcHRpbWl6YXRpb24gc2Vl
bXMgY29udHJhcnkgdG8gb3VyIGludGVyZXN0cywgbXVjaCBsZXNzIHRoZSBwcml2YWN5DQogaW50
ZXJlc3RzIG9mIHRoZSBwZWVycy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij5yZWdhcmRzLDxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGVkPG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2Jv
cmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDtt
YXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PkNoZWVycyw8YnI+DQo8YnI+DQpCcmlhbjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxicj4NCiZn
dDsgVGVkPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFNlbnQgdmlhIHRoZSBTYW1zdW5nIEdhbGF4eSBT
NywgYW4gQVQmYW1wO1QgNEcgTFRFIHNtYXJ0cGhvbmU8YnI+DQomZ3Q7IDxicj4NCiZndDsgPGJy
Pg0KJmd0OyAtLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tPGJyPg0KJmd0OyBGcm9t
OiAmcXVvdDtTYWx6LCBSaWNoJnF1b3Q7ICZsdDtyc2Fsej08YSBocmVmPSJtYWlsdG86NDBha2Ft
YWkuY29tQGRtYXJjLmlldGYub3JnIj40MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmc8L2E+Jmd0
Ozxicj4NCiZndDsgRGF0ZTogNS8xLzE4IDU6MjUgQU0gKEdNVC0wODowMCk8YnI+DQomZ3Q7IFRv
OiBCZW5qYW1pbiBLYWR1ayAmbHQ7YmthZHVrPTxhIGhyZWY9Im1haWx0bzo0MGFrYW1haS5jb21A
ZG1hcmMuaWV0Zi5vcmciPjQwYWthbWFpLmNvbUBkbWFyYy5pZXRmLm9yZzwvYT4mZ3Q7LCBQcmF2
ZWVuIEJhbGFzdWJyYW1hbmlhbiAmbHQ7cHJhdmI9PGEgaHJlZj0ibWFpbHRvOjQwbWljcm9zb2Z0
LmNvbUBkbWFyYy5pZXRmLm9yZyI+NDBtaWNyb3NvZnQuY29tQGRtYXJjLmlldGYub3JnPC9hPiZn
dDs8YnI+DQomZ3Q7IENjOiBJRVRGIFFVSUMgV0cgJmx0OzxhIGhyZWY9Im1haWx0bzpxdWljQGll
dGYub3JnIj5xdWljQGlldGYub3JnPC9hPiZndDs8YnI+DQomZ3Q7IFN1YmplY3Q6IFJlOiBHZXR0
aW5nIHRvIGNvbnNlbnN1cyBvbiBwYWNrZXQgbnVtYmVyIGVuY3J5cHRpb248YnI+DQomZ3Q7IDxi
cj4NCiZndDsmbmJzcDsgJm5ic3A7ICZuYnNwOyZndDsgSSBkaXNhZ3JlZSB0aGF0IHdlIG5lZWQg
YW55IG1vcmUgZGF0YSBmb3Igbm90IGRvaW5nIFBORSBpbiB0aGUgZGF0YWNlbnRlci4gV2h5IHdv
dWxkIHdlIGFkZCBhbiBleHRyYSBlbmNyeXB0LWRlY3J5cHQgc3RlcCBmb3Igbm8gb2J2aW91cyBi
ZW5lZml0Pzxicj4NCiZndDsgPGJyPg0KJmd0OyBJIGFtIGNvbmNlcm5lZCB0aGF0IHBlb3BsZSB3
aWxsIG1pcy1pbnRlcnByZXQgdGhlIG1lYW5pbmcgb2YgYSBkYXRhY2VudGVyLCBhbmQgdGhpbmsg
dGhhdCBhIGJ1bmNoIG9mIHNlcnZlcnMsIG9yIGV2ZW4gYSByYWNrLCBpbiBhbiBvcGVuIGNvbG8g
c3BhY2UgaXMgYSAmcXVvdDtkYXRhY2VudGVyLiZxdW90OyZuYnNwOyBDb21wdXRlcnMga2VlcCBn
ZXR0aW5nIGZhc3Rlci48YnI+DQomZ3Q7IDxicj4NCiZndDsgPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwv
aHRtbD4NCg==

--_000_ba56bca23f5747e5abdfec137de37481usma1exdag1mb5msgcorpak_--


From nobody Tue May  1 11:59:38 2018
Return-Path: <pravb@microsoft.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C65F3126B6D for <quic@ietfa.amsl.com>; Tue,  1 May 2018 11:59:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level: 
X-Spam-Status: No, score=-2.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 IWuE4o09X8HK for <quic@ietfa.amsl.com>; Tue,  1 May 2018 11:59:29 -0700 (PDT)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0706.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe48::706]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E78E1201F2 for <quic@ietf.org>; Tue,  1 May 2018 11:59:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=CpqTmWbYUWjbm7QFCq6tj4UO4A6O/60HabWUwJOffL0=; b=HNMc/R6E5Vbi/Ah5x5KYCMQPM9oV1Bk7Xrahxc9kWj5MW8FQnAEW+c19FHn0XbMaMDLpFkgZ4ZyirOD4RVXQIx1IhcJPAXLhBFgAzfx97hbIbBtTT7Ym3WOli6ZOb0twS+Lp+2wdK0RfPDxuBHsFuON14vptjSzmEhhT5RdgIBo=
Received: from MWHPR21MB0638.namprd21.prod.outlook.com (10.175.141.139) by MWHPR21MB0157.namprd21.prod.outlook.com (10.173.52.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.735.5; Tue, 1 May 2018 18:59:27 +0000
Received: from MWHPR21MB0638.namprd21.prod.outlook.com ([fe80::6d48:f7af:d267:2021]) by MWHPR21MB0638.namprd21.prod.outlook.com ([fe80::6d48:f7af:d267:2021%7]) with mapi id 15.20.0735.006; Tue, 1 May 2018 18:59:27 +0000
From: Praveen Balasubramanian <pravb@microsoft.com>
To: "Lubashev, Igor" <ilubashe@akamai.com>, Ted Hardie <ted.ietf@gmail.com>, "Brian Trammell (IETF)" <ietf@trammell.ch>
CC: IETF QUIC WG <quic@ietf.org>, Roberto Peon <fenix@fb.com>, "Salz, Rich" <rsalz@akamai.com>, Benjamin Kaduk <bkaduk@akamai.com>
Subject: RE: Getting to consensus on packet number encryption
Thread-Topic: Getting to consensus on packet number encryption
Thread-Index: AQHTy9GYaiUVNrU6h0aiyBQtEo3l9KPwZ0sAgAC4ugCAAARcAIAAFTbwgAALYgCAAAAgYIAAEcIAgACR+YCAB09lAIAFXyIAgAVK+oCAAJlSAIABxdSAgACOHICAB/EyAIACo7YAgACiMICAAADPgIAAIs8AgAAm/YCAABExgIAABpMAgAAK5wCAAPIgAIAA5wcAgACzcYCAAHHMgIAEe1cAgAABEACAABL8QIAA89MAgAABeQCAAC8kAIAAC7UAgAARLwCAAA0zAIAAD7YAgAAE15A=
Date: Tue, 1 May 2018 18:59:26 +0000
Message-ID: <MWHPR21MB0638014E783CE63F5D30DE38B6810@MWHPR21MB0638.namprd21.prod.outlook.com>
References: <CANatvzwCYrOZULG3iVmDFp97nr=M5=Gufo8TZjOGQVFUpsn0bQ@mail.gmail.com> <CAAedzxqDcPXJUE83KVnDiU23PvqDcTCrc6rRMw09FexjJA-Y6Q@mail.gmail.com> <CANatvzwjYE6EdvFtOXJMVQnutbVQ4YY+=XsQFzKwHzqWzZ4U+w@mail.gmail.com> <d32ade7b56bf4651952659307c08893b@usma1ex-dag1mb5.msg.corp.akamai.com> <CANatvzwHtCn8rLB8npf3i7PGyYZhVDRd2uojh5hv3uxtFPEsSA@mail.gmail.com> <58447D8E-782C-431C-8FC3-71124B10A047@trammell.ch> <CACpbDcdfF9w3qqrH1eB0sGU_4vheD9aMP5EXnp1o3Y19N19NUg@mail.gmail.com> <e8b4931a-3931-5b8d-8dad-3ca1939d5542@huitema.net> <CAKcm_gPaj3o-VTdA_0+Kk+nTcVJrYcs_BMyOiDGXKub3gB=GLg@mail.gmail.com> <MWHPR21MB063869878060E850137210FEB6820@MWHPR21MB0638.namprd21.prod.outlook.com> <20180501121906.GA5742@akamai.com> <F63059EA-BA14-4886-A4FB-AA5F04AC164B@akamai.com> <BY2PR15MB07757EAB6A818F1D8D8CCED9CD810@BY2PR15MB0775.namprd15.prod.outlook.com> <CA+9kkMCpxve3CKhQk45YKbvyOyQ6kvzyhpJhrTq1UM-QM+ms2Q@mail.gmail.com> <89893592-7135-4C24-BE1E-4B0FFD1A2E97@trammell.ch> <CA+9kkMCUTRrM9SPEz=Q5GDgU7whryZ1cRdj-O3=GP=-vOr-X+A@mail.gmail.com> <ba56bca23f5747e5abdfec137de37481@usma1ex-dag1mb5.msg.corp.akamai.com>
In-Reply-To: <ba56bca23f5747e5abdfec137de37481@usma1ex-dag1mb5.msg.corp.akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e8:7::316]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MWHPR21MB0157; 7:34IBcNIGQO5pAv1Qykg1lGRPxOhlRS8L1eufbIvtMYG44fToMg6Geptq7UAe4GdR52NhdxMQAnawf1ljSv1TkxEOuhv41/f1qab/PrcUn2U3z+V00Yo+Ue+4Ba18bJbpw93f6qyMhpHEeP8vQxm4ZmzlWp/N+51lLWNSI7O9AGt5opMohQxaGmfgtFAmwhNsZxXkbn42bMhnfGZkkPmIZVbgIVxc9ORRUYxQwwQ4RfiACNeDaBhy64ZphOPPq0g5; 20:ZVGOZmyZBP8q2FtfJf0dJHYo+hL2pFv9aLrGPv8FR7xZB2sahZZegjfoRfkN+ZHqp8khlO2rNB7cCEXvvTthDeNGNoHcbwNs7Fc6Fwpzwrxbp7xShKYLKODFjL7IbwdXQQ/VM/KW23851nTUUtI+Vm52Jb1SS9/S73jnRBI7NGo=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(2017052603328)(7193020); SRVR:MWHPR21MB0157; 
x-ms-traffictypediagnostic: MWHPR21MB0157:
x-microsoft-antispam-prvs: <MWHPR21MB0157E276D0B3F3DDAC8860CEB6810@MWHPR21MB0157.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(89211679590171)(85827821059158)(67672495146484)(100405760836317)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(10201501046)(3231254)(2018427008)(944501410)(52105095)(3002001)(93006095)(93001095)(6055026)(6041310)(20161123562045)(20161123564045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(6072148)(201708071742011); SRVR:MWHPR21MB0157; BCL:0; PCL:0; RULEID:; SRVR:MWHPR21MB0157; 
x-forefront-prvs: 06592CCE58
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(39380400002)(396003)(376002)(366004)(39860400002)(199004)(189003)(99286004)(6506007)(53546011)(106356001)(76176011)(46003)(5250100002)(7696005)(59450400001)(93886005)(10090500001)(14454004)(74316002)(68736007)(110136005)(316002)(22452003)(54906003)(446003)(19609705001)(2900100001)(5660300001)(102836004)(11346002)(486006)(476003)(81166006)(8676002)(6306002)(7736002)(186003)(790700001)(6346003)(229853002)(33656002)(6116002)(55016002)(4326008)(6436002)(8936002)(81156014)(54896002)(53936002)(236005)(9686003)(86362001)(97736004)(39060400002)(86612001)(8990500004)(105586002)(3660700001)(3280700002)(2906002)(6246003)(10290500003)(25786009)(478600001); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR21MB0157; H:MWHPR21MB0638.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pravb@microsoft.com; 
x-microsoft-antispam-message-info: nidPNIIsKnHkdieyQ3nSssD++DRJdnXt3n3KbOq/dovuKb6zFyQetuVcIFwRPdF60RdpEQEE6MUwQcb0U29tZa9aw/hgu0LNq65uYZ6GhQuZAVL+CMj8NpXYXA9WUzuPrWC/xnwsXEFtNejrCI73kRQ/+Y7fLn3f30auvJsc+w3nKnJ0+aLxHt6ddYMQGk2x
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_MWHPR21MB0638014E783CE63F5D30DE38B6810MWHPR21MB0638namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 3bb5bf03-745c-4d1f-f372-08d5af95a974
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 3bb5bf03-745c-4d1f-f372-08d5af95a974
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 May 2018 18:59:27.0234 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR21MB0157
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/UEkDekfWKdK2Ns_taTuFHGoE2wA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2018 18:59:36 -0000

--_000_MWHPR21MB0638014E783CE63F5D30DE38B6810MWHPR21MB0638namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

WWVhaCB0aGlzIGRvZXNu4oCZdCBoYXZlIHRvIGJlIHVuaWxhdGVyYWwgYW5kIGlzIGEgbmVnb3Rp
YXRpb24uIEVpdGhlciBzaWRlIGlzIGZyZWUgdG8gdGVybWluYXRlIHRoZSBoYW5kc2hha2UgYW5k
IGZhbGwgYmFjayB0byBUQ1AgaWYgaXQgZG9lc27igJl0IHdhbnQgdG8gc3VwcG9ydCB0aGUgdHJh
bnNmb3JtcyBiZWluZyBvZmZlcmVkIGluIHRoZSBuZWdvdGlhdGlvbi4gVGhpcyB3b3JrcyBwZXJm
ZWN0bHkgZmluZSBmb3IgdGhlIGludHJhLURDIHVzZSBjYXNlcy4NCg0KRnJvbTogTHViYXNoZXYs
IElnb3IgW21haWx0bzppbHViYXNoZUBha2FtYWkuY29tXQ0KU2VudDogVHVlc2RheSwgTWF5IDEs
IDIwMTggMTE6NDAgQU0NClRvOiBUZWQgSGFyZGllIDx0ZWQuaWV0ZkBnbWFpbC5jb20+OyBCcmlh
biBUcmFtbWVsbCAoSUVURikgPGlldGZAdHJhbW1lbGwuY2g+DQpDYzogUHJhdmVlbiBCYWxhc3Vi
cmFtYW5pYW4gPHByYXZiQG1pY3Jvc29mdC5jb20+OyBJRVRGIFFVSUMgV0cgPHF1aWNAaWV0Zi5v
cmc+OyBSb2JlcnRvIFBlb24gPGZlbml4QGZiLmNvbT47IFNhbHosIFJpY2ggPHJzYWx6QGFrYW1h
aS5jb20+OyBCZW5qYW1pbiBLYWR1ayA8YmthZHVrQGFrYW1haS5jb20+DQpTdWJqZWN0OiBSRTog
R2V0dGluZyB0byBjb25zZW5zdXMgb24gcGFja2V0IG51bWJlciBlbmNyeXB0aW9uDQoNCg0KICAq
ICAgQnV0IGhhdmluZyAgUVVJQyBuZWdvdGlhdGUgdGhpcyBvdXRzaWRlIG9mIHRoZSB2ZXJzaW9u
IGRvZXMgbm90IG1ha2Ugc2Vuc2UgdG8gbWUsIGJlY2F1c2UgdGhlcmUgaXMgbm8gd2F5IGZvciBh
biBpbml0aWF0b3Igb3IgYSByZXNwb25kaW5nIHBlZXIgdG8ganVkZ2Ugd2hldGhlciB0aGUgb3Ro
ZXIgc2lkZSdzIGFzc2VydGlvbiBvZiBzYWZldHkgaXMgd2VsbC1mb3VuZGVkIG9yIGV2ZW4gd2Vs
bC1tZWFudC4NCg0KV291bGQgaXQgc2F0aXNmeSB5b3VyIGNvbmNlcm5zLCBpZiBfYm90aF8gcGVl
cnMgbmVlZCB0byBleHByZXNzIGludGVyZXN0IGluIGhhdmluZyBQTkUgb2ZmIGZvciB0aGUgUE5F
IHRvIGJlIOKAnG5lZ290aWF0ZWQgb2Zm4oCdPw0KDQoNCkZyb206IFRlZCBIYXJkaWUgW21haWx0
bzp0ZWQuaWV0ZkBnbWFpbC5jb21dDQpTZW50OiBUdWVzZGF5LCBNYXkgMDEsIDIwMTggMTo0NCBQ
TQ0KVG86IEJyaWFuIFRyYW1tZWxsIChJRVRGKSA8aWV0ZkB0cmFtbWVsbC5jaDxtYWlsdG86aWV0
ZkB0cmFtbWVsbC5jaD4+DQpDYzogUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gPHByYXZiPTQwbWlj
cm9zb2Z0LmNvbUBkbWFyYy5pZXRmLm9yZzxtYWlsdG86cHJhdmI9NDBtaWNyb3NvZnQuY29tQGRt
YXJjLmlldGYub3JnPj47IElFVEYgUVVJQyBXRyA8cXVpY0BpZXRmLm9yZzxtYWlsdG86cXVpY0Bp
ZXRmLm9yZz4+OyBSb2JlcnRvIFBlb24gPGZlbml4QGZiLmNvbTxtYWlsdG86ZmVuaXhAZmIuY29t
Pj47IFNhbHosIFJpY2ggPHJzYWx6PTQwYWthbWFpLmNvbUBkbWFyYy5pZXRmLm9yZzxtYWlsdG86
cnNhbHo9NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnPj47IEJlbmphbWluIEthZHVrIDxia2Fk
dWs9NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnPG1haWx0bzpia2FkdWs9NDBha2FtYWkuY29t
QGRtYXJjLmlldGYub3JnPj4NClN1YmplY3Q6IFJlOiBHZXR0aW5nIHRvIGNvbnNlbnN1cyBvbiBw
YWNrZXQgbnVtYmVyIGVuY3J5cHRpb24NCg0KT24gVHVlLCBNYXkgMSwgMjAxOCBhdCA5OjU2IEFN
LCBCcmlhbiBUcmFtbWVsbCAoSUVURikgPGlldGZAdHJhbW1lbGwuY2g8bWFpbHRvOmlldGZAdHJh
bW1lbGwuY2g+PiB3cm90ZToNCmhpIFRlZCwgYWxsLA0KDQpBdCB0aGlzIHBvaW50IEkndmUgcHJl
dHR5IG11Y2ggY29tZSBhcm91bmQgdG8gdGhlIG9waW5pb24gd2Ugc2hvdWxkIGp1c3QgbGFuZCAx
MDc5IGFuZCBkaXNjdXNzIHRoZSByZXN0LCBidXQgdGhpcyBjb252ZXJzYXRpb24gY29udGludWVz
IHRvIGhhdmUgbWUgd29ycmllZCB0aGF0IHdlJ3JlIGNvbWluZyB0byBjb25zZW5zdXMgb24gYSBm
ZWF0dXJlIHdlIGRvIG5vdCBmdWxseSB1bmRlcnN0YW5kIHRoZSBhcHBsaWNhYmlsaXR5IGFuZCBs
aW1pdGF0aW9ucyBvZi4NCkkgYWxzbyB0aGluayB0aGF0IGp1c3QgbGFuZGluZyAxMDc5IGFuZCBt
b3Zpbmcgb24gaXMgdGhlIHJpZ2h0IHRoaW5nIHRvIGRvLg0KDQpQTkUncyBwcmltYXJ5IHV0aWxp
dHkgaXMgYW50aS1vc3NpZmljYXRpb24uIFdoaWxlIGl0IHJlZHVjZXMgdGhlIGFtb3VudCBvZiBp
bmZvcm1hdGlvbiBhdmFpbGFibGUgdG8gYW4gYXR0YWNrZXIgYXR0ZW1wdGluZyB0byBhY2hpZXZl
IGxpbmthYmlsaXR5IG9mIGZsb3dzIGFjcm9zcyBhIHB1cnBvc2VmdWwgcGF0aCBtaWdyYXRpb24s
IG9yIHdpdGggYSBzaW5nbGUtUE4tc3BhY2UgbXVsdGlwYXRoIGRlc2lnbiwgaXQgZG9lcyBub3Qg
ZWxpbWluYXRlIGl0LCBzbyBleHBlY3RpbmcgbW9yZSB0aGFuIGEgbWFyZ2luYWwgcHJpdmFjeSBi
ZW5lZml0IGZyb20gdGhlIGZlYXR1cmUgcGVyIHNlIGlzIHNldHRpbmcgb25lc2VsZiB1cCBmb3Ig
ZGlzYXBwb2ludG1lbnQuDQoNClRoZSByZWFzb24gdG8gZGlzYWJsZSBQTkUgaW4gKGFkbWl0dGVk
bHkgaWxsLWRlZmluZWQpICJkYXRhY2VudGVyIiBlbnZpcm9ubWVudHMgaXMgdG8gdHJhZGUgb2Zm
IHRoZSAofjElaXNoKSBvdmVyaGVhZCBmb3Igb3NzaWZpY2F0aW9uIHByb3RlY3Rpb24geW91IGtu
b3cgeW91IGRvbid0IG5lZWQgYmVjYXVzZSB5b3UgZGlkbid0IGRlcGxveSBhbnl0aGluZyB0aGF0
IHRyaWVzIHRvIGFidXNlIHRoZSBwYWNrZXQgbnVtYmVyLg0KDQoob24gd2hpY2gsIG1vcmUgYmVs
b3c7IGFuZCBvbiBwcmV2aWV3LCB3aGF0IFByYXZlZW4gc2FpZCkNCg0KPiBPbiAxIE1heSAyMDE4
LCBhdCAxNzo1NSwgVGVkIEhhcmRpZSA8dGVkLmlldGZAZ21haWwuY29tPG1haWx0bzp0ZWQuaWV0
ZkBnbWFpbC5jb20+PiB3cm90ZToNCj4NCj4gT24gVHVlLCBNYXkgMSwgMjAxOCBhdCA4OjEzIEFN
LCBSb2JlcnRvIFBlb24gPGZlbml4QGZiLmNvbTxtYWlsdG86ZmVuaXhAZmIuY29tPj4gd3JvdGU6
DQo+IEFsc28sIFByaXNtLg0KPg0KPiAtPVINCj4NCj4NCj4NCj4gVGhhdCdzIGEgbGl0dGxlIG1v
cmUgc3VjY2luY3QgdGhhbiBJIHdvdWxkIGJlLCBidXQgeWVzLiAgSG93IGRvZXMgYW4gYXBwbGlj
YXRpb24ga25vdyB0aGF0IHRoZSBmbG93IGl0IGlzIGluaXRpYXRpbmcgd2lsbCB0cmF2ZXJzZSBh
IHRvcG9sb2d5IHRoYXQgaXMgZGVlbWVkIHRvIGJlIHdpdGhpbiBhIGNvbnRyb2xsZWQgZW52aXJv
bm1lbnQ/ICBZb3UgY2FuIHNheSAiY29uZmlndXJhdGlvbiIgYnV0IEkgZmVhciBpdCB3aWxsIHR1
cm4gdXAgb24gYSBwb3N0LWl0ICBpZiB5b3UgZG8uICBMb2FkcyBzaGlmdCwgcmVzb3VyY2VzIG1v
dmUsIGFuZCBzdWRkZW5seSB5b3UgZmluZCB0aGF0IGhvc3Qgd2hpY2ggdXNlZCB0byBiZSBpbiB0
aGUgc2FtZSByYWNrLCBiZWluZyBkb3duLCBoYXMgbG9hZC1zaGlmdGVkIHRvIHRoZSBuZXh0IGlu
c3RhbmNlLCAgaW4gYSBkYXRhY2VudGVyIDUwMCBtaWxlcyBhd2F5IGFjcm9zcyBhIHZlcnkgZGlm
ZmVyZW50IG5ldHdvcmsuDQo+DQo+IE1hbnkgbW9kZXJuIGRlcGxveW1lbnRzIGFyZSBhbHNvIGlu
IHNvbWVvbmUgZWxzZSdzIGRhdGEgY2VudGVyLCBzbyBzYXlpbmcgIkRhdGEgY2VudGVyIG5ldHdv
cmtzIiBkb2Vzbid0IHNheSBtdWNoIGFib3V0IHdoeSB5b3UncmUgdHJ1c3RpbmcgdGhlIG5ldHdv
cmsgaW5zaWRlLg0KDQpUaGUgImxvYWQtc2hpZnRlZCB0byB0aGUgbmV4dCBpbnN0YW5jZSIgZXhh
bXBsZSBpcyBhbiBpbnRlcmVzdGluZyBvbmUgaWZmIHNhaWQgbG9hZCBzaGlmdGluZyBjYXVzZXMg
dGhlIHRyYWZmaWMgdGhhdCB1c2VkIHRvIGNyb3NzIGEgcHJpdmF0ZSBuZXR3b3JrIHRvIHRyYW5z
aXQgdGhlIG9wZW4gSW50ZXJuZXQgaW5zdGVhZC4NCg0KV2VsbCwgYSBsb25nLWhhdWwgbGluaywg
Y2VydGFpbmx5LiAgVGhhdCBtYXkgb3IgbWF5IG5vdCBiZSAidGhlIG9wZW4gSW50ZXJuZXQiIGFu
ZCB0aGUgY2hhbmNlcyBvZiBpdCB0cmF2ZXJzaW5nIGEgY29tcGxldGVseSB1bmtub3duIG1pZGRs
ZWJveCBhcmUgbG93LiAgVGhlIGNoYW5jZXMgb2YgaXQgcGFzc2luZyBieSBhbiB1bmtub3duIG9i
c2VydmVyLCBvbiB0aGUgb3RoZXIgaGFuZCwgYXJlIG5vdCBjdXJyZW50bHkga25vd24gYnV0IGFy
ZSBwcmVzdW1lZCB0byBiZSBoaWdoLg0KDQpJcyB0aGlzIGEgdGhpbmcgdGhhdCBldmVyIGhhcHBl
bnMgaW4gYW55IG9mIHRoZSBlbnZpcm9ubWVudHMgdGhhdCBnZXQgY2FsbGVkICJkYXRhY2VudGVy
IiBmb3IgbmV0d29ya2luZyB0ZWNobm9sb2d5IHB1cnBvc2VzPw0KDQpTbywgdGhlIHdheSBJIGxv
b2sgYXQgdGhpcyBib2lscyBkb3duIHRvOg0KSWYgdGhlIGxpbmthYmlsaXR5IG9yIG9zc2lmaWNh
dGlvbiBjb25jZXJucyB3aXRoIHBhY2tldCBudW1iZXJzIGluIHRoZSBjbGVhciBhcmUganVzdGlm
aWVkLCB5b3UgZWl0aGVyIG5lZWQgdG8gaGF2ZSBpdCBvbiBhbGwgdGhlIHRpbWUgb3IgaGF2ZSB2
ZXJ5IGNsZWFyIG1ldGhvZHMgZm9yIGRldGVybWluaW5nIHdoZW4gdGhlIGNvbmNlcm5zIGFyZSBu
b3QgcHJlc2VudC4gIFRoZSBwcm90b2NvbCBpcyBub3QgYXdhcmUgb2YgdGhlIGwyIG9yIGwzIHRv
cG9sb2d5IGJldHdlZW4gYW4gaW5pdGlhdG9yIGFuZCBpdHMgcGVlciwgbXVjaCBsZXNzIHRoZSBt
YW5hZ2VtZW50IG9mIHRoYXQgcGF0aC4NCg0KU28gdGhlIGNsZWFyIG1ldGhvZHMgZm9yIGRldGVy
bWluYXRpb24gcmVhbGx5IGJvaWwgZG93biB0byAic29tZW9uZSB0dXJucyB0aGlzIG9mZiB3aGVu
IHRoZXkgdGhpbmsgaXQgaXMgcmlnaHQgdG8gZG8gc28iLiAgRmxvd3MgZW50aXJlbHkgd2l0aGlu
IHRoZSBkb21haW4gb2YgY29udHJvbCBvZiBhIHNpbmdsZSBwcm92aWRlciBtaWdodCBiZSBhIGNh
c2Ugd2hlcmUgZm9sa3MgdGhpbmsgaXQgaXMgcmlnaHQgdG8gZG8gc28uICBBIHN1YnNldCBvZiB0
aGF0IGRvbWFpbiBvZiBjb250cm9sIGlzIHdoZW4gdGhlIGZsb3cgaGFzIG5vIGxvbmctaGF1bCBs
aW5rcyAoZm9yIGhvd2V2ZXIgeW91IHdhbnQgdG8gZGVmaW5lIHRoYXQpLCB0aGUgc2hvcnRoYW5k
IGZvciB3aGljaCBpcyAiZGF0YWNlbnRlciBuZXR3b3JrIiAodGhvdWdoIGl0IG1pZ2h0IHdlbGwg
YWxzbyBiZSBhIHNtYWxsIGNvbXBsZXggb2YgZGF0YWNlbnRlcnMsIGFuIGVudGVycHJpc2UgY2Ft
cHVzLCBvciBzaW1pbGFyKS4gIEJ1dCB0aGUga2V5IGlzIHRoYXQgeW91IGJlbGlldmUgdGhhdCB0
aGUgdG9wb2xvZ3kgYmV0d2VlbiBwZWVyIEEgYW5kIHBlZXIgQiBoYXMgbm8gbWlkZGxlYm94ZXMg
b3V0c2lkZSBvZiB0aGUgc2hhcmVkIGRvbWFpbiBvZiBjb250cm9sIHRoYXQgbWlnaHQgb3NzaWZ5
IHRoZSBiZWhhdmlvciBhbmQgbm8gb2JzZXJ2ZXJzIHdob3NlIHVzZSBvZiB0aGlzIGRhdGEgY29u
Y2VybnMgeW91Lg0KSWYgeW91IGNvbnRyb2wgYm90aCBwZWVycyBhbmQgdGhlIG5ldHdvcmsgYmV0
d2VlbiB0aGVtLCB1c2luZyBhIFFVSUMgdmVyc2lvbiB3aGVyZSB0aGlzIGlzIGFsd2F5cyB0dXJu
ZWQgb2ZmIG1pZ2h0IG1ha2Ugc2Vuc2UuICBCdXQgaGF2aW5nICBRVUlDIG5lZ290aWF0ZSB0aGlz
IG91dHNpZGUgb2YgdGhlIHZlcnNpb24gZG9lcyBub3QgbWFrZSBzZW5zZSB0byBtZSwgYmVjYXVz
ZSB0aGVyZSBpcyBubyB3YXkgZm9yIGFuIGluaXRpYXRvciBvciBhIHJlc3BvbmRpbmcgcGVlciB0
byBqdWRnZSB3aGV0aGVyIHRoZSBvdGhlciBzaWRlJ3MgYXNzZXJ0aW9uIG9mIHNhZmV0eSBpcyB3
ZWxsLWZvdW5kZWQgb3IgZXZlbiB3ZWxsLW1lYW50LiAgSWYgaXQgaGFzIG5vIGluZGVwZW5kZW50
IGRhdGEgb24gdGhpcyAoYW5kIHRoZSBwcm90b2NvbCBwcm92aWRlcyBub25lKSwgdGhpcyBhbGxv
d3Mgb25lIHNpZGUgb3IgdGhlIG90aGVyIHRvIHVuaWxhdGVyYWxseSB0dXJuIG9mZiBhbiBhbnRp
LW9zc2lmaWNhdGlvbiBhbmQgYW50aS1saW5rYWJpbGl0eSBmZWF0dXJlIGZvciB3aGF0ZXZlciBn
YWluIGl0IHdhbnRzLiAgU2luY2Ugd2UncmUgdHJ5aW5nIHRvIG9wdGltaXplIGZvciB0aGUgbG9u
Zy10ZXJtIGZsZXhpYmlsaXR5IG9mIHRoZSBwcm90b2NvbCwgYWxsb3dpbmcgdGhhdCBwYXJ0aWN1
bGFyIHBvaW50IG9wdGltaXphdGlvbiBzZWVtcyBjb250cmFyeSB0byBvdXIgaW50ZXJlc3RzLCBt
dWNoIGxlc3MgdGhlIHByaXZhY3kgaW50ZXJlc3RzIG9mIHRoZSBwZWVycy4NCg0KcmVnYXJkcywN
ClRlZA0KDQpDaGVlcnMsDQoNCkJyaWFuDQoNCj4gVGVkDQo+DQo+IFNlbnQgdmlhIHRoZSBTYW1z
dW5nIEdhbGF4eSBTNywgYW4gQVQmVCA0RyBMVEUgc21hcnRwaG9uZQ0KPg0KPg0KPiAtLS0tLS0t
LSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tDQo+IEZyb206ICJTYWx6LCBSaWNoIiA8cnNhbHo9
NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnPG1haWx0bzo0MGFrYW1haS5jb21AZG1hcmMuaWV0
Zi5vcmc+Pg0KPiBEYXRlOiA1LzEvMTggNToyNSBBTSAoR01ULTA4OjAwKQ0KPiBUbzogQmVuamFt
aW4gS2FkdWsgPGJrYWR1az00MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmc8bWFpbHRvOjQwYWth
bWFpLmNvbUBkbWFyYy5pZXRmLm9yZz4+LCBQcmF2ZWVuIEJhbGFzdWJyYW1hbmlhbiA8cHJhdmI9
NDBtaWNyb3NvZnQuY29tQGRtYXJjLmlldGYub3JnPG1haWx0bzo0MG1pY3Jvc29mdC5jb21AZG1h
cmMuaWV0Zi5vcmc+Pg0KPiBDYzogSUVURiBRVUlDIFdHIDxxdWljQGlldGYub3JnPG1haWx0bzpx
dWljQGlldGYub3JnPj4NCj4gU3ViamVjdDogUmU6IEdldHRpbmcgdG8gY29uc2Vuc3VzIG9uIHBh
Y2tldCBudW1iZXIgZW5jcnlwdGlvbg0KPg0KPiAgICAgPiBJIGRpc2FncmVlIHRoYXQgd2UgbmVl
ZCBhbnkgbW9yZSBkYXRhIGZvciBub3QgZG9pbmcgUE5FIGluIHRoZSBkYXRhY2VudGVyLiBXaHkg
d291bGQgd2UgYWRkIGFuIGV4dHJhIGVuY3J5cHQtZGVjcnlwdCBzdGVwIGZvciBubyBvYnZpb3Vz
IGJlbmVmaXQ/DQo+DQo+IEkgYW0gY29uY2VybmVkIHRoYXQgcGVvcGxlIHdpbGwgbWlzLWludGVy
cHJldCB0aGUgbWVhbmluZyBvZiBhIGRhdGFjZW50ZXIsIGFuZCB0aGluayB0aGF0IGEgYnVuY2gg
b2Ygc2VydmVycywgb3IgZXZlbiBhIHJhY2ssIGluIGFuIG9wZW4gY29sbyBzcGFjZSBpcyBhICJk
YXRhY2VudGVyLiIgIENvbXB1dGVycyBrZWVwIGdldHRpbmcgZmFzdGVyLg0KPg0KPg0KDQo=

--_000_MWHPR21MB0638014E783CE63F5D30DE38B6810MWHPR21MB0638namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMg
MiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1
IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZp
c2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5
Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAuTXNvTGlz
dFBhcmFncmFwaCwgbGkuTXNvTGlzdFBhcmFncmFwaCwgZGl2Lk1zb0xpc3RQYXJhZ3JhcGgNCgl7
bXNvLXN0eWxlLXByaW9yaXR5OjM0Ow0KCW1hcmdpbi10b3A6MGluOw0KCW1hcmdpbi1yaWdodDow
aW47DQoJbWFyZ2luLWJvdHRvbTowaW47DQoJbWFyZ2luLWxlZnQ6LjVpbjsNCgltYXJnaW4tYm90
dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
c2Fucy1zZXJpZjt9DQpwLm1zb25vcm1hbDAsIGxpLm1zb25vcm1hbDAsIGRpdi5tc29ub3JtYWww
DQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsN
CgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdp
bi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE5DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFs
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7
fQ0Kc3Bhbi5FbWFpbFN0eWxlMjENCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJ
Zm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQou
TXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6
MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJn
aW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldv
cmRTZWN0aW9uMTt9DQovKiBMaXN0IERlZmluaXRpb25zICovDQpAbGlzdCBsMA0KCXttc28tbGlz
dC1pZDoxNzE5Mjg0ODYxOw0KCW1zby1saXN0LXR5cGU6aHlicmlkOw0KCW1zby1saXN0LXRlbXBs
YXRlLWlkczoxMDQ4MjA1MDA0IDgzOTk2NzIxNiA2NzY5ODY5MSA2NzY5ODY5MyA2NzY5ODY4OSA2
NzY5ODY5MSA2NzY5ODY5MyA2NzY5ODY4OSA2NzY5ODY5MSA2NzY5ODY5Mzt9DQpAbGlzdCBsMDps
ZXZlbDENCgl7bXNvLWxldmVsLXN0YXJ0LWF0OjA7DQoJbXNvLWxldmVsLW51bWJlci1mb3JtYXQ6
YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+DmDsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsN
Cgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0K
CWZvbnQtZmFtaWx5OldpbmdkaW5nczsNCgltc28tZmFyZWFzdC1mb250LWZhbWlseTpDYWxpYnJp
Ow0KCW1zby1iaWRpLWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iO30NCkBsaXN0IGwwOmxl
dmVsMg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6
bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9u
OmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7
fQ0KQGxpc3QgbDA6bGV2ZWwzDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCglt
c28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVs
LW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWls
eTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw0DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0
OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7
DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsN
Cglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWw1DQoJe21zby1sZXZlbC1udW1i
ZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3Rv
cDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDot
LjI1aW47DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMDpsZXZlbDYNCgl7
bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCglt
c28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7
DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBs
MDpsZXZlbDcNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10
ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBv
c2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9
DQpAbGlzdCBsMDpsZXZlbDgNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1z
by1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51
bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseToi
Q291cmllciBOZXciO30NCkBsaXN0IGwwOmxldmVsOQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1h
dDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25l
Ow0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47
DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwxDQoJe21zby1saXN0LWlkOjIxMDky
MzAyMDU7DQoJbXNvLWxpc3QtdGVtcGxhdGUtaWRzOjEzODMxMzUzMDI7fQ0KQGxpc3QgbDE6bGV2
ZWwxDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrv
grc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOi41aW47DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlv
bjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0
Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMTpsZXZlbDINCgl7bXNvLWxldmVsLW51
bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFi
LXN0b3A6MS4waW47DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5k
ZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OlN5
bWJvbDt9DQpAbGlzdCBsMTpsZXZlbDMNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0
Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6MS41aW47DQoJbXNv
LWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28t
YW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMTps
ZXZlbDQNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0
Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6Mi4waW47DQoJbXNvLWxldmVsLW51bWJlci1wb3Np
dGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6MTAu
MHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMTpsZXZlbDUNCgl7bXNvLWxldmVs
LW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwt
dGFiLXN0b3A6Mi41aW47DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQt
aW5kZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5
OlN5bWJvbDt9DQpAbGlzdCBsMTpsZXZlbDYNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVs
bGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6My4waW47DQoJ
bXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglt
c28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBs
MTpsZXZlbDcNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10
ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6My41aW47DQoJbXNvLWxldmVsLW51bWJlci1w
b3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6
MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMTpsZXZlbDgNCgl7bXNvLWxl
dmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2
ZWwtdGFiLXN0b3A6NC4waW47DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRl
eHQtaW5kZW50Oi0uMjVpbjsNCgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFt
aWx5OlN5bWJvbDt9DQpAbGlzdCBsMTpsZXZlbDkNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6
YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6NC41aW47
DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsN
Cgltc28tYW5zaS1mb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpvbA0K
CXttYXJnaW4tYm90dG9tOjBpbjt9DQp1bA0KCXttYXJnaW4tYm90dG9tOjBpbjt9DQotLT48L3N0
eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRp
dCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5
XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVk
aXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hl
YWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2
IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+WWVhaCB0aGlzIGRv
ZXNu4oCZdCBoYXZlIHRvIGJlIHVuaWxhdGVyYWwgYW5kIGlzIGEgbmVnb3RpYXRpb24uIEVpdGhl
ciBzaWRlIGlzIGZyZWUgdG8gdGVybWluYXRlIHRoZSBoYW5kc2hha2UgYW5kIGZhbGwgYmFjayB0
byBUQ1AgaWYgaXQgZG9lc27igJl0IHdhbnQgdG8gc3VwcG9ydCB0aGUgdHJhbnNmb3JtcyBiZWlu
ZyBvZmZlcmVkIGluIHRoZSBuZWdvdGlhdGlvbi4gVGhpcyB3b3JrcyBwZXJmZWN0bHkgZmluZSBm
b3INCiB0aGUgaW50cmEtREMgdXNlIGNhc2VzLiA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRl
cjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAw
aW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPkZyb206PC9iPiBMdWJhc2hldiwgSWdv
ciBbbWFpbHRvOmlsdWJhc2hlQGFrYW1haS5jb21dIDxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5
LCBNYXkgMSwgMjAxOCAxMTo0MCBBTTxicj4NCjxiPlRvOjwvYj4gVGVkIEhhcmRpZSAmbHQ7dGVk
LmlldGZAZ21haWwuY29tJmd0OzsgQnJpYW4gVHJhbW1lbGwgKElFVEYpICZsdDtpZXRmQHRyYW1t
ZWxsLmNoJmd0Ozxicj4NCjxiPkNjOjwvYj4gUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gJmx0O3By
YXZiQG1pY3Jvc29mdC5jb20mZ3Q7OyBJRVRGIFFVSUMgV0cgJmx0O3F1aWNAaWV0Zi5vcmcmZ3Q7
OyBSb2JlcnRvIFBlb24gJmx0O2Zlbml4QGZiLmNvbSZndDs7IFNhbHosIFJpY2ggJmx0O3JzYWx6
QGFrYW1haS5jb20mZ3Q7OyBCZW5qYW1pbiBLYWR1ayAmbHQ7YmthZHVrQGFrYW1haS5jb20mZ3Q7
PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJFOiBHZXR0aW5nIHRvIGNvbnNlbnN1cyBvbiBwYWNrZXQg
bnVtYmVyIGVuY3J5cHRpb248bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjx1bCBzdHlsZT0ibWFyZ2luLXRv
cDowaW4iIHR5cGU9ImRpc2MiPg0KPGxpIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbGlz
dDpsMCBsZXZlbDEgbGZvMyI+QnV0IGhhdmluZyZuYnNwOyBRVUlDIG5lZ290aWF0ZSB0aGlzIG91
dHNpZGUgb2YgdGhlIHZlcnNpb24gZG9lcyBub3QgbWFrZSBzZW5zZSB0byBtZSwgYmVjYXVzZSB0
aGVyZSBpcyBubyB3YXkgZm9yIGFuIGluaXRpYXRvciBvciBhIHJlc3BvbmRpbmcgcGVlciB0byBq
dWRnZSB3aGV0aGVyIHRoZSBvdGhlciBzaWRlJ3MgYXNzZXJ0aW9uIG9mIHNhZmV0eSBpcyB3ZWxs
LWZvdW5kZWQNCiBvciBldmVuIHdlbGwtbWVhbnQuPG86cD48L286cD48L2xpPjwvdWw+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPldvdWxkIGl0IHNhdGlzZnkgeW91ciBjb25jZXJucywgaWYgX2JvdGhfIHBlZXJzIG5lZWQg
dG8gZXhwcmVzcyBpbnRlcmVzdCBpbiBoYXZpbmcgUE5FIG9mZiBmb3IgdGhlIFBORSB0byBiZSDi
gJxuZWdvdGlhdGVkIG9mZuKAnT8NCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPkZyb206PC9iPiBUZWQgSGFyZGll
IFs8YSBocmVmPSJtYWlsdG86dGVkLmlldGZAZ21haWwuY29tIj5tYWlsdG86dGVkLmlldGZAZ21h
aWwuY29tPC9hPl0NCjxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCBNYXkgMDEsIDIwMTggMTo0
NCBQTTxicj4NCjxiPlRvOjwvYj4gQnJpYW4gVHJhbW1lbGwgKElFVEYpICZsdDs8YSBocmVmPSJt
YWlsdG86aWV0ZkB0cmFtbWVsbC5jaCI+aWV0ZkB0cmFtbWVsbC5jaDwvYT4mZ3Q7PGJyPg0KPGI+
Q2M6PC9iPiBQcmF2ZWVuIEJhbGFzdWJyYW1hbmlhbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOnByYXZi
PTQwbWljcm9zb2Z0LmNvbUBkbWFyYy5pZXRmLm9yZyI+cHJhdmI9NDBtaWNyb3NvZnQuY29tQGRt
YXJjLmlldGYub3JnPC9hPiZndDs7IElFVEYgUVVJQyBXRyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnF1
aWNAaWV0Zi5vcmciPnF1aWNAaWV0Zi5vcmc8L2E+Jmd0OzsgUm9iZXJ0byBQZW9uICZsdDs8YSBo
cmVmPSJtYWlsdG86ZmVuaXhAZmIuY29tIj5mZW5peEBmYi5jb208L2E+Jmd0OzsNCiBTYWx6LCBS
aWNoICZsdDs8YSBocmVmPSJtYWlsdG86cnNhbHo9NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3Jn
Ij5yc2Fsej00MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmc8L2E+Jmd0OzsgQmVuamFtaW4gS2Fk
dWsgJmx0OzxhIGhyZWY9Im1haWx0bzpia2FkdWs9NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3Jn
Ij5ia2FkdWs9NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnPC9hPiZndDs8YnI+DQo8Yj5TdWJq
ZWN0OjwvYj4gUmU6IEdldHRpbmcgdG8gY29uc2Vuc3VzIG9uIHBhY2tldCBudW1iZXIgZW5jcnlw
dGlvbjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gVHVlLCBNYXkgMSwgMjAxOCBh
dCA5OjU2IEFNLCBCcmlhbiBUcmFtbWVsbCAoSUVURikgJmx0OzxhIGhyZWY9Im1haWx0bzppZXRm
QHRyYW1tZWxsLmNoIiB0YXJnZXQ9Il9ibGFuayI+aWV0ZkB0cmFtbWVsbC5jaDwvYT4mZ3Q7IHdy
b3RlOjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9y
ZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4g
MGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0
OjBpbjttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
YXJnaW4tYm90dG9tOjEyLjBwdCI+aGkgVGVkLCBhbGwsPGJyPg0KPGJyPg0KQXQgdGhpcyBwb2lu
dCBJJ3ZlIHByZXR0eSBtdWNoIGNvbWUgYXJvdW5kIHRvIHRoZSBvcGluaW9uIHdlIHNob3VsZCBq
dXN0IGxhbmQgMTA3OSBhbmQgZGlzY3VzcyB0aGUgcmVzdCwgYnV0IHRoaXMgY29udmVyc2F0aW9u
IGNvbnRpbnVlcyB0byBoYXZlIG1lIHdvcnJpZWQgdGhhdCB3ZSdyZSBjb21pbmcgdG8gY29uc2Vu
c3VzIG9uIGEgZmVhdHVyZSB3ZSBkbyBub3QgZnVsbHkgdW5kZXJzdGFuZCB0aGUgYXBwbGljYWJp
bGl0eSBhbmQgbGltaXRhdGlvbnMNCiBvZi48bzpwPjwvbzpwPjwvcD4NCjwvYmxvY2txdW90ZT4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIGFsc28gdGhpbmsgdGhhdCBqdXN0IGxhbmRp
bmcgMTA3OSBhbmQgbW92aW5nIG9uIGlzIHRoZSByaWdodCB0aGluZyB0byBkby48bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxl
ZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1s
ZWZ0OjQuOHB0O21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0OjBpbjttYXJnaW4tYm90dG9t
OjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlBORSdzIHByaW1hcnkgdXRpbGl0eSBpcyBh
bnRpLW9zc2lmaWNhdGlvbi4gV2hpbGUgaXQgcmVkdWNlcyB0aGUgYW1vdW50IG9mIGluZm9ybWF0
aW9uIGF2YWlsYWJsZSB0byBhbiBhdHRhY2tlciBhdHRlbXB0aW5nIHRvIGFjaGlldmUgbGlua2Fi
aWxpdHkgb2YgZmxvd3MgYWNyb3NzIGEgcHVycG9zZWZ1bCBwYXRoIG1pZ3JhdGlvbiwgb3Igd2l0
aCBhIHNpbmdsZS1QTi1zcGFjZSBtdWx0aXBhdGggZGVzaWduLCBpdA0KIGRvZXMgbm90IGVsaW1p
bmF0ZSBpdCwgc28gZXhwZWN0aW5nIG1vcmUgdGhhbiBhIG1hcmdpbmFsIHByaXZhY3kgYmVuZWZp
dCBmcm9tIHRoZSBmZWF0dXJlIHBlciBzZSBpcyBzZXR0aW5nIG9uZXNlbGYgdXAgZm9yIGRpc2Fw
cG9pbnRtZW50Ljxicj4NCjxicj4NClRoZSByZWFzb24gdG8gZGlzYWJsZSBQTkUgaW4gKGFkbWl0
dGVkbHkgaWxsLWRlZmluZWQpICZxdW90O2RhdGFjZW50ZXImcXVvdDsgZW52aXJvbm1lbnRzIGlz
IHRvIHRyYWRlIG9mZiB0aGUgKH4xJWlzaCkgb3ZlcmhlYWQgZm9yIG9zc2lmaWNhdGlvbiBwcm90
ZWN0aW9uIHlvdSBrbm93IHlvdSBkb24ndCBuZWVkIGJlY2F1c2UgeW91IGRpZG4ndCBkZXBsb3kg
YW55dGhpbmcgdGhhdCB0cmllcyB0byBhYnVzZSB0aGUgcGFja2V0IG51bWJlci48YnI+DQo8YnI+
DQoob24gd2hpY2gsIG1vcmUgYmVsb3c7IGFuZCBvbiBwcmV2aWV3LCB3aGF0IFByYXZlZW4gc2Fp
ZCk8YnI+DQo8YnI+DQomZ3Q7IE9uIDEgTWF5IDIwMTgsIGF0IDE3OjU1LCBUZWQgSGFyZGllICZs
dDs8YSBocmVmPSJtYWlsdG86dGVkLmlldGZAZ21haWwuY29tIj50ZWQuaWV0ZkBnbWFpbC5jb208
L2E+Jmd0OyB3cm90ZTo8YnI+DQomZ3Q7IDxicj4NCiZndDsgT24gVHVlLCBNYXkgMSwgMjAxOCBh
dCA4OjEzIEFNLCBSb2JlcnRvIFBlb24gJmx0OzxhIGhyZWY9Im1haWx0bzpmZW5peEBmYi5jb20i
PmZlbml4QGZiLmNvbTwvYT4mZ3Q7IHdyb3RlOjxicj4NCiZndDsgQWxzbywgUHJpc20uPGJyPg0K
Jmd0OyA8YnI+DQomZ3Q7IC09Ujxicj4NCiZndDsgPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IDxicj4N
CiZndDsgVGhhdCdzIGEgbGl0dGxlIG1vcmUgc3VjY2luY3QgdGhhbiBJIHdvdWxkIGJlLCBidXQg
eWVzLiZuYnNwOyBIb3cgZG9lcyBhbiBhcHBsaWNhdGlvbiBrbm93IHRoYXQgdGhlIGZsb3cgaXQg
aXMgaW5pdGlhdGluZyB3aWxsIHRyYXZlcnNlIGEgdG9wb2xvZ3kgdGhhdCBpcyBkZWVtZWQgdG8g
YmUgd2l0aGluIGEgY29udHJvbGxlZCBlbnZpcm9ubWVudD8mbmJzcDsgWW91IGNhbiBzYXkgJnF1
b3Q7Y29uZmlndXJhdGlvbiZxdW90OyBidXQgSSBmZWFyIGl0IHdpbGwgdHVybiB1cCBvbg0KIGEg
cG9zdC1pdCZuYnNwOyBpZiB5b3UgZG8uJm5ic3A7IExvYWRzIHNoaWZ0LCByZXNvdXJjZXMgbW92
ZSwgYW5kIHN1ZGRlbmx5IHlvdSBmaW5kIHRoYXQgaG9zdCB3aGljaCB1c2VkIHRvIGJlIGluIHRo
ZSBzYW1lIHJhY2ssIGJlaW5nIGRvd24sIGhhcyBsb2FkLXNoaWZ0ZWQgdG8gdGhlIG5leHQgaW5z
dGFuY2UsJm5ic3A7IGluIGEgZGF0YWNlbnRlciA1MDAgbWlsZXMgYXdheSBhY3Jvc3MgYSB2ZXJ5
IGRpZmZlcmVudCBuZXR3b3JrLjxicj4NCiZndDsgPGJyPg0KJmd0OyBNYW55IG1vZGVybiBkZXBs
b3ltZW50cyBhcmUgYWxzbyBpbiBzb21lb25lIGVsc2UncyBkYXRhIGNlbnRlciwgc28gc2F5aW5n
ICZxdW90O0RhdGEgY2VudGVyIG5ldHdvcmtzJnF1b3Q7IGRvZXNuJ3Qgc2F5IG11Y2ggYWJvdXQg
d2h5IHlvdSdyZSB0cnVzdGluZyB0aGUgbmV0d29yayBpbnNpZGUuPGJyPg0KPGJyPg0KVGhlICZx
dW90O2xvYWQtc2hpZnRlZCB0byB0aGUgbmV4dCBpbnN0YW5jZSZxdW90OyBleGFtcGxlIGlzIGFu
IGludGVyZXN0aW5nIG9uZSBpZmYgc2FpZCBsb2FkIHNoaWZ0aW5nIGNhdXNlcyB0aGUgdHJhZmZp
YyB0aGF0IHVzZWQgdG8gY3Jvc3MgYSBwcml2YXRlIG5ldHdvcmsgdG8gdHJhbnNpdCB0aGUgb3Bl
biBJbnRlcm5ldCBpbnN0ZWFkLjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+V2VsbCwgYSBsb25nLWhhdWwgbGluaywgY2VydGFpbmx5
LiZuYnNwOyBUaGF0IG1heSBvciBtYXkgbm90IGJlICZxdW90O3RoZSBvcGVuIEludGVybmV0JnF1
b3Q7IGFuZCB0aGUgY2hhbmNlcyBvZiBpdCB0cmF2ZXJzaW5nIGEgY29tcGxldGVseSB1bmtub3du
IG1pZGRsZWJveCBhcmUgbG93LiZuYnNwOyBUaGUgY2hhbmNlcyBvZiBpdCBwYXNzaW5nIGJ5IGFu
IHVua25vd24gb2JzZXJ2ZXIsIG9uIHRoZSBvdGhlciBoYW5kLCBhcmUgbm90IGN1cnJlbnRseQ0K
IGtub3duIGJ1dCBhcmUgcHJlc3VtZWQgdG8gYmUgaGlnaC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0ND
Q0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21h
cmdpbi10b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0OjBpbjttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+SXMgdGhpcyBh
IHRoaW5nIHRoYXQgZXZlciBoYXBwZW5zIGluIGFueSBvZiB0aGUgZW52aXJvbm1lbnRzIHRoYXQg
Z2V0IGNhbGxlZCAmcXVvdDtkYXRhY2VudGVyJnF1b3Q7IGZvciBuZXR3b3JraW5nIHRlY2hub2xv
Z3kgcHVycG9zZXM/PG86cD48L286cD48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPlNvLCB0aGUgd2F5
IEkgbG9vayBhdCB0aGlzIGJvaWxzIGRvd24gdG86PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPklm
IHRoZSBsaW5rYWJpbGl0eSBvciBvc3NpZmljYXRpb24gY29uY2VybnMgd2l0aCBwYWNrZXQgbnVt
YmVycyBpbiB0aGUgY2xlYXIgYXJlIGp1c3RpZmllZCwgeW91IGVpdGhlciBuZWVkIHRvIGhhdmUg
aXQgb24gYWxsIHRoZSB0aW1lIG9yIGhhdmUgdmVyeSBjbGVhciBtZXRob2RzIGZvciBkZXRlcm1p
bmluZyB3aGVuIHRoZSBjb25jZXJucyBhcmUgbm90IHByZXNlbnQuJm5ic3A7DQogVGhlIHByb3Rv
Y29sIGlzIG5vdCBhd2FyZSBvZiB0aGUgbDIgb3IgbDMgdG9wb2xvZ3kgYmV0d2VlbiBhbiBpbml0
aWF0b3IgYW5kIGl0cyBwZWVyLCBtdWNoIGxlc3MgdGhlIG1hbmFnZW1lbnQgb2YgdGhhdCBwYXRo
LiZuYnNwOw0KPGJyPg0KPGJyPg0KU28gdGhlIGNsZWFyIG1ldGhvZHMgZm9yIGRldGVybWluYXRp
b24gcmVhbGx5IGJvaWwgZG93biB0byAmcXVvdDtzb21lb25lIHR1cm5zIHRoaXMgb2ZmIHdoZW4g
dGhleSB0aGluayBpdCBpcyByaWdodCB0byBkbyBzbyZxdW90Oy4mbmJzcDsgRmxvd3MgZW50aXJl
bHkgd2l0aGluIHRoZSBkb21haW4gb2YgY29udHJvbCBvZiBhIHNpbmdsZSBwcm92aWRlciBtaWdo
dCBiZSBhIGNhc2Ugd2hlcmUgZm9sa3MgdGhpbmsgaXQgaXMgcmlnaHQgdG8gZG8gc28uJm5ic3A7
IEEgc3Vic2V0IG9mDQogdGhhdCBkb21haW4gb2YgY29udHJvbCBpcyB3aGVuIHRoZSBmbG93IGhh
cyBubyBsb25nLWhhdWwgbGlua3MgKGZvciBob3dldmVyIHlvdSB3YW50IHRvIGRlZmluZSB0aGF0
KSwgdGhlIHNob3J0aGFuZCBmb3Igd2hpY2ggaXMgJnF1b3Q7ZGF0YWNlbnRlciBuZXR3b3JrJnF1
b3Q7ICh0aG91Z2ggaXQgbWlnaHQgd2VsbCBhbHNvIGJlIGEgc21hbGwgY29tcGxleCBvZiBkYXRh
Y2VudGVycywgYW4gZW50ZXJwcmlzZSBjYW1wdXMsIG9yIHNpbWlsYXIpLiZuYnNwOyBCdXQgdGhl
DQoga2V5IGlzIHRoYXQgeW91IGJlbGlldmUgdGhhdCB0aGUgdG9wb2xvZ3kgYmV0d2VlbiBwZWVy
IEEgYW5kIHBlZXIgQiBoYXMgbm8gbWlkZGxlYm94ZXMgb3V0c2lkZSBvZiB0aGUgc2hhcmVkIGRv
bWFpbiBvZiBjb250cm9sIHRoYXQgbWlnaHQgb3NzaWZ5IHRoZSBiZWhhdmlvciBhbmQgbm8gb2Jz
ZXJ2ZXJzIHdob3NlIHVzZSBvZiB0aGlzIGRhdGEgY29uY2VybnMgeW91LjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SWYgeW91IGNvbnRyb2wgYm90
aCBwZWVycyBhbmQgdGhlIG5ldHdvcmsgYmV0d2VlbiB0aGVtLCB1c2luZyBhIFFVSUMgdmVyc2lv
biB3aGVyZSB0aGlzIGlzIGFsd2F5cyB0dXJuZWQgb2ZmIG1pZ2h0IG1ha2Ugc2Vuc2UuJm5ic3A7
IEJ1dCBoYXZpbmcmbmJzcDsgUVVJQyBuZWdvdGlhdGUgdGhpcyBvdXRzaWRlIG9mIHRoZSB2ZXJz
aW9uIGRvZXMgbm90IG1ha2Ugc2Vuc2UgdG8gbWUsIGJlY2F1c2UgdGhlcmUgaXMgbm8gd2F5IGZv
cg0KIGFuIGluaXRpYXRvciBvciBhIHJlc3BvbmRpbmcgcGVlciB0byBqdWRnZSB3aGV0aGVyIHRo
ZSBvdGhlciBzaWRlJ3MgYXNzZXJ0aW9uIG9mIHNhZmV0eSBpcyB3ZWxsLWZvdW5kZWQgb3IgZXZl
biB3ZWxsLW1lYW50LiZuYnNwOyBJZiBpdCBoYXMgbm8gaW5kZXBlbmRlbnQgZGF0YSBvbiB0aGlz
IChhbmQgdGhlIHByb3RvY29sIHByb3ZpZGVzIG5vbmUpLCB0aGlzIGFsbG93cyBvbmUgc2lkZSBv
ciB0aGUgb3RoZXIgdG8gdW5pbGF0ZXJhbGx5IHR1cm4gb2ZmDQogYW4gYW50aS1vc3NpZmljYXRp
b24gYW5kIGFudGktbGlua2FiaWxpdHkgZmVhdHVyZSBmb3Igd2hhdGV2ZXIgZ2FpbiBpdCB3YW50
cy4mbmJzcDsgU2luY2Ugd2UncmUgdHJ5aW5nIHRvIG9wdGltaXplIGZvciB0aGUgbG9uZy10ZXJt
IGZsZXhpYmlsaXR5IG9mIHRoZSBwcm90b2NvbCwgYWxsb3dpbmcgdGhhdCBwYXJ0aWN1bGFyIHBv
aW50IG9wdGltaXphdGlvbiBzZWVtcyBjb250cmFyeSB0byBvdXIgaW50ZXJlc3RzLCBtdWNoIGxl
c3MgdGhlIHByaXZhY3kNCiBpbnRlcmVzdHMgb2YgdGhlIHBlZXJzLjxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRv
bToxMi4wcHQiPnJlZ2FyZHMsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5UZWQ8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBz
dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5n
OjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi10b3A6NS4wcHQ7bWFy
Z2luLXJpZ2h0OjBpbjttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PkNoZWVycyw8YnI+DQo8YnI+DQpCcmlhbjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxicj4NCiZn
dDsgVGVkPGJyPg0KJmd0OyA8YnI+DQomZ3Q7IFNlbnQgdmlhIHRoZSBTYW1zdW5nIEdhbGF4eSBT
NywgYW4gQVQmYW1wO1QgNEcgTFRFIHNtYXJ0cGhvbmU8YnI+DQomZ3Q7IDxicj4NCiZndDsgPGJy
Pg0KJmd0OyAtLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tPGJyPg0KJmd0OyBGcm9t
OiAmcXVvdDtTYWx6LCBSaWNoJnF1b3Q7ICZsdDtyc2Fsej08YSBocmVmPSJtYWlsdG86NDBha2Ft
YWkuY29tQGRtYXJjLmlldGYub3JnIj40MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmc8L2E+Jmd0
Ozxicj4NCiZndDsgRGF0ZTogNS8xLzE4IDU6MjUgQU0gKEdNVC0wODowMCk8YnI+DQomZ3Q7IFRv
OiBCZW5qYW1pbiBLYWR1ayAmbHQ7YmthZHVrPTxhIGhyZWY9Im1haWx0bzo0MGFrYW1haS5jb21A
ZG1hcmMuaWV0Zi5vcmciPjQwYWthbWFpLmNvbUBkbWFyYy5pZXRmLm9yZzwvYT4mZ3Q7LCBQcmF2
ZWVuIEJhbGFzdWJyYW1hbmlhbiAmbHQ7cHJhdmI9PGEgaHJlZj0ibWFpbHRvOjQwbWljcm9zb2Z0
LmNvbUBkbWFyYy5pZXRmLm9yZyI+NDBtaWNyb3NvZnQuY29tQGRtYXJjLmlldGYub3JnPC9hPiZn
dDs8YnI+DQomZ3Q7IENjOiBJRVRGIFFVSUMgV0cgJmx0OzxhIGhyZWY9Im1haWx0bzpxdWljQGll
dGYub3JnIj5xdWljQGlldGYub3JnPC9hPiZndDs8YnI+DQomZ3Q7IFN1YmplY3Q6IFJlOiBHZXR0
aW5nIHRvIGNvbnNlbnN1cyBvbiBwYWNrZXQgbnVtYmVyIGVuY3J5cHRpb248YnI+DQomZ3Q7IDxi
cj4NCiZndDsmbmJzcDsgJm5ic3A7ICZuYnNwOyZndDsgSSBkaXNhZ3JlZSB0aGF0IHdlIG5lZWQg
YW55IG1vcmUgZGF0YSBmb3Igbm90IGRvaW5nIFBORSBpbiB0aGUgZGF0YWNlbnRlci4gV2h5IHdv
dWxkIHdlIGFkZCBhbiBleHRyYSBlbmNyeXB0LWRlY3J5cHQgc3RlcCBmb3Igbm8gb2J2aW91cyBi
ZW5lZml0Pzxicj4NCiZndDsgPGJyPg0KJmd0OyBJIGFtIGNvbmNlcm5lZCB0aGF0IHBlb3BsZSB3
aWxsIG1pcy1pbnRlcnByZXQgdGhlIG1lYW5pbmcgb2YgYSBkYXRhY2VudGVyLCBhbmQgdGhpbmsg
dGhhdCBhIGJ1bmNoIG9mIHNlcnZlcnMsIG9yIGV2ZW4gYSByYWNrLCBpbiBhbiBvcGVuIGNvbG8g
c3BhY2UgaXMgYSAmcXVvdDtkYXRhY2VudGVyLiZxdW90OyZuYnNwOyBDb21wdXRlcnMga2VlcCBn
ZXR0aW5nIGZhc3Rlci48YnI+DQomZ3Q7IDxicj4NCiZndDsgPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwv
aHRtbD4NCg==

--_000_MWHPR21MB0638014E783CE63F5D30DE38B6810MWHPR21MB0638namp_--


From nobody Tue May  1 16:20:38 2018
Return-Path: <prvs=86592f1e95=fenix@fb.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 91FA812EB3C for <quic@ietfa.amsl.com>; Tue,  1 May 2018 16:20:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=OpxVTvFN; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=HsxFZ8VH
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 W1LRzoH_4CC6 for <quic@ietfa.amsl.com>; Tue,  1 May 2018 16:20:23 -0700 (PDT)
Received: from mx0a-00082601.pphosted.com (mx0a-00082601.pphosted.com [67.231.145.42]) (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 1E048127275 for <quic@ietf.org>; Tue,  1 May 2018 16:20:16 -0700 (PDT)
Received: from pps.filterd (m0044010.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w41NJdFR012089; Tue, 1 May 2018 16:20:12 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=facebook; bh=DjAURSKisKZR1kEDA9VuZeTL6gcHUQCn66OSOVWcIKk=; b=OpxVTvFNs/LWgNu1r2zp/s5dJlNUrszniVtsmZ/4te9wjiL9FSD5ZUk44wTJFAyp5aX0 knHCkmfC3yij2Pvfu/rj1vr0eFJRpPJrmql1vnjYpHSx3XP2+9IJsDAf2lQQ58L3k3dp t3+w2ULePKWtQLAl/+GyO4To7SQXZJBek8Y= 
Received: from mail.thefacebook.com ([199.201.64.23]) by mx0a-00082601.pphosted.com with ESMTP id 2hpxbnghge-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 01 May 2018 16:20:12 -0700
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (192.168.54.28) by o365-in.thefacebook.com (192.168.16.15) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 1 May 2018 16:20:11 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version;  bh=DjAURSKisKZR1kEDA9VuZeTL6gcHUQCn66OSOVWcIKk=; b=HsxFZ8VHEyjXFVbxGI1hRShaTegNKbW9mOWTzklgbd6xzBVPNMTp0O0g9RmVZgOuLt1vCAqrsXmVHJhV+urW9H/zC57lRK0iYN2cj6SndnJiUWVxOunnnbaXWMAj+VlNRbRWXZFrp8HnbAEcM+l9GpIegcGup2l+RpKXM0nN0ho=
Received: from BY2PR15MB0775.namprd15.prod.outlook.com (10.164.171.11) by BY2PR15MB0373.namprd15.prod.outlook.com (10.163.109.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.715.24; Tue, 1 May 2018 23:20:08 +0000
Received: from BY2PR15MB0775.namprd15.prod.outlook.com ([fe80::6c4c:bbf3:ec3b:d45e]) by BY2PR15MB0775.namprd15.prod.outlook.com ([fe80::6c4c:bbf3:ec3b:d45e%14]) with mapi id 15.20.0715.024; Tue, 1 May 2018 23:20:08 +0000
From: Roberto Peon <fenix@fb.com>
To: Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>, Ted Hardie <ted.ietf@gmail.com>
CC: "Salz, Rich" <rsalz@akamai.com>, Benjamin Kaduk <bkaduk@akamai.com>, "IETF QUIC WG" <quic@ietf.org>
Subject: Re: Getting to consensus on packet number encryption
Thread-Topic: Getting to consensus on packet number encryption
Thread-Index: AQHTy9GjyGQaKf4GI0anNhXTngANsKPwZ0sAgAC4ugCAAARcAIAAG5CAgAAFCACAAACJgIAAEVkAgACR+ICAAVFHAIALXUEAgAVKTpWAAJn+AIABxdSAgACOHICAB/EyAIACo7YAgACiL4CAAADQgIAAIs8AgAAm/YCAABExgIAABpIAgAAK6ACAAPIgAIAA5wYAgACzcoCAAHHMgIAEe1cAgAABEACAABWHgIAA8UgAgAABeQCAAC8lSYAAC7QAgAALBwD///v+gA==
Date: Tue, 1 May 2018 23:20:08 +0000
Message-ID: <AFD9317B-499C-4C56-A571-EDFEDC5093B9@fb.com>
References: <CANatvzwCYrOZULG3iVmDFp97nr=M5=Gufo8TZjOGQVFUpsn0bQ@mail.gmail.com> <CAAedzxqDcPXJUE83KVnDiU23PvqDcTCrc6rRMw09FexjJA-Y6Q@mail.gmail.com> <CANatvzwjYE6EdvFtOXJMVQnutbVQ4YY+=XsQFzKwHzqWzZ4U+w@mail.gmail.com> <d32ade7b56bf4651952659307c08893b@usma1ex-dag1mb5.msg.corp.akamai.com> <CANatvzwHtCn8rLB8npf3i7PGyYZhVDRd2uojh5hv3uxtFPEsSA@mail.gmail.com> <58447D8E-782C-431C-8FC3-71124B10A047@trammell.ch> <CACpbDcdfF9w3qqrH1eB0sGU_4vheD9aMP5EXnp1o3Y19N19NUg@mail.gmail.com> <e8b4931a-3931-5b8d-8dad-3ca1939d5542@huitema.net> <CAKcm_gPaj3o-VTdA_0+Kk+nTcVJrYcs_BMyOiDGXKub3gB=GLg@mail.gmail.com> <MWHPR21MB063869878060E850137210FEB6820@MWHPR21MB0638.namprd21.prod.outlook.com> <20180501121906.GA5742@akamai.com> <F63059EA-BA14-4886-A4FB-AA5F04AC164B@akamai.com> <BY2PR15MB07757EAB6A818F1D8D8CCED9CD810@BY2PR15MB0775.namprd15.prod.outlook.com> <CA+9kkMCpxve3CKhQk45YKbvyOyQ6kvzyhpJhrTq1UM-QM+ms2Q@mail.gmail.com> <MWHPR21MB063883F004E055CC91C153EBB6810@MWHPR21MB0638.namprd21.prod.outlook.com>
In-Reply-To: <MWHPR21MB063883F004E055CC91C153EBB6810@MWHPR21MB0638.namprd21.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.c.0.180410
x-originating-ip: [2620:10d:c090:200::6:ddb8]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BY2PR15MB0373; 7:te73HRSjQTCYNOXp8oeKque290GbNX4qAo1Zb065t02w5oEtK9QLy8nHNX6FZgVm/yaR8UYIAmWQ+VH786ZZvSs1dE2haEUOo2wvYtTxyhqjNYgl75n1CgbL6VpM38dyx4TULp7pqPV1rdFjnzKOZbfIs4GVcfu0uZZ4a9vguV/15U3hyZhw8ZONQzAOFn0HeEQmuVI4gz46qKdM1WDW1md+dZZDPId47GPknc6IGduhMSS/qKNKCH5Yzt98zNQE; 20:qGjtUXy69k6SxuIsyXe58/M/zRWctpjpyf7ebtEtsLyDBnLlBH7s9JXMu9WhCfF0PlprydH1tKcmuuTvoW4kF1svq+fioXKR/x3n0Ra/ZW1XYDGYWigGJqeFVfTx/R4m0QAccoGsYYKmtQeDGy3JIy5m/tWaU9Az0FupZ/ycJjo=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BY2PR15MB0373; 
x-ms-traffictypediagnostic: BY2PR15MB0373:
x-microsoft-antispam-prvs: <BY2PR15MB0373461ABFA5B5F3A6684692CD810@BY2PR15MB0373.namprd15.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(10436049006162)(89211679590171)(189930954265078)(85827821059158)(67672495146484)(100405760836317)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(10201501046)(3002001)(93006095)(93001095)(3231254)(11241501184)(944501410)(52105095)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123562045)(20161123564045)(20161123558120)(6072148)(201708071742011); SRVR:BY2PR15MB0373; BCL:0; PCL:0; RULEID:; SRVR:BY2PR15MB0373; 
x-forefront-prvs: 06592CCE58
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(39860400002)(39380400002)(346002)(376002)(396003)(199004)(189003)(82746002)(5660300001)(105586002)(11346002)(110136005)(81156014)(83716003)(58126008)(33656002)(606006)(81166006)(446003)(25786009)(6116002)(2906002)(46003)(6436002)(476003)(2616005)(106356001)(6486002)(54906003)(8676002)(36756003)(486006)(3660700001)(186003)(229853002)(6246003)(39060400002)(478600001)(7736002)(45080400002)(8936002)(6506007)(14454004)(102836004)(93886005)(3280700002)(86362001)(59450400001)(68736007)(53936002)(53546011)(54896002)(5250100002)(6306002)(236005)(6512007)(97736004)(99286004)(76176011)(316002)(4326008)(2900100001)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR15MB0373; H:BY2PR15MB0775.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: fb.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: rVbvK24khMo6df0jM548u/mui2YXSjx3jKHrmMNh1aUB61z/QBh4Xc+2sJM56Z1VBNcBx1xt89O8hQpeCVlCQQAO2HlXU48aJOPqkjFxFmmeCRI8D5o1Kn5Q1KHYNjzFtba7neZ+AMh98MN1lzCgxwEWlzYxCjplXSzrz/UNik49oHaC/UphNap/8HH5uhMt
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_AFD9317B499C4C56A571EDFEDC5093B9fbcom_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 4782d1e4-2834-4a6a-5941-08d5afba1460
X-MS-Exchange-CrossTenant-Network-Message-Id: 4782d1e4-2834-4a6a-5941-08d5afba1460
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 May 2018 23:20:08.1398 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR15MB0373
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-01_13:, , signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/bidkn1Fy8Qpk5SwdpdRdaIeZcZo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2018 23:20:27 -0000

--_000_AFD9317B499C4C56A571EDFEDC5093B9fbcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

WXVwLiBJIGtub3cuDQpQcmlzbSB3YXMgZXllLW9wZW5pbmcgcGFydGlhbGx5IGJlY2F1c2Ugb2Yg
dGhlIGZhY3QgdGhhdCB0aGUgcGFja2V0cyB3ZXJlIG5vdCBnb2luZyBhY3Jvc3MgdGhlIGludGVy
bmV0LCBidXQgcmF0aGVyIHdpdGhpbiBhIHNlY3VyZSBuZXR3b3JrLg0KDQpJIGJlbGlldmUgdGhh
dCBvc3NpZmljYXRpb24gYWxvbmUgaXMgYSBnb29kIGVub3VnaCByZWFzb24gdG8gZG8gUE5FLg0K
VGhlIGNoZXJyeSBmb3IgbWUgaXMgdGhhdCBpdCwgYWxvbmcgd2l0aCBvdGhlciBhY3Rpb25zL21p
dGlnYXRpb25zLCBtYWtlcyBsaW5rYWJpbGl0eSBtb3JlIGRpZmZpY3VsdCBmb3IgbWFsaWNpb3Vz
IGFjdG9ycy4NCkNSSU1FIGFuZCByZWxhdGVkIHdhcyBleWUtb3BlbmluZyBiZWNhdXNlIGl0IGV4
cG9zZWQgdGhlIHBvd2VyIG9mIHRoZSBvYnNlcnZhYmxlIHNpZGUtY2hhbm5lbC4NCg0KLT1SDQoN
CkZyb206IFFVSUMgPHF1aWMtYm91bmNlc0BpZXRmLm9yZz4gb24gYmVoYWxmIG9mIFByYXZlZW4g
QmFsYXN1YnJhbWFuaWFuIDxwcmF2Yj00MG1pY3Jvc29mdC5jb21AZG1hcmMuaWV0Zi5vcmc+DQpE
YXRlOiBUdWVzZGF5LCBNYXkgMSwgMjAxOCBhdCA5OjM1IEFNDQpUbzogVGVkIEhhcmRpZSA8dGVk
LmlldGZAZ21haWwuY29tPiwgUm9iZXJ0byBQZW9uIDxmZW5peEBmYi5jb20+DQpDYzogIlNhbHos
IFJpY2giIDxyc2FsekBha2FtYWkuY29tPiwgQmVuamFtaW4gS2FkdWsgPGJrYWR1a0Bha2FtYWku
Y29tPiwgSUVURiBRVUlDIFdHIDxxdWljQGlldGYub3JnPg0KU3ViamVjdDogUkU6IEdldHRpbmcg
dG8gY29uc2Vuc3VzIG9uIHBhY2tldCBudW1iZXIgZW5jcnlwdGlvbg0KDQpUaGlzIGlzIG5vdCBh
Ym91dCBwdXR0aW5nIHBsYWludGV4dCBkYXRhIG9uIHRoZSBuZXR3b3JrLCB0aGlzIGlzIGFib3V0
IG5vdCBhZGRpbmcgUE5FIHdoaWNoIGlzIGludGVuZGVkIGZvciBwcmV2ZW50aW5nIG9zc2lmaWNh
dGlvbi4gU28gSSBkb27igJl0IHVuZGVyc3RhbmQgd2hhdCB0aGUgdHJ1c3QgaXNzdWUgYmVpbmcg
cmVmZXJyZWQgdG8gaXMgaW4gY2FzZSBvZiB0aGUgcmFyZSBtaXNjb25maWcuDQoNCldpdGhpbiBh
IERDIHNldmVyYWwgdGhpbmdzIGFyZSBkaWZmZXJlbnQg4oCTIHRoZSBkZXBsb3ltZW50IG1heSBu
ZWVkIGRpZmZlcmVudCBjb25nZXN0aW9uIGNvbnRyb2wgbGlrZSBEQ1RDUCwgZGlmZmVyZW50IHNl
dHRpbmdzIGZvciB2YXJpb3VzIHRyYW5zcG9ydCBwYXJhbWV0ZXJzIChsaWtlIG1pbnJ0byBhbmQg
bWF4IEFDSyBkZWxheSksIGxhcmdlciBmbG93IGNvbnRyb2wgd2luZG93IGV0Yy4gVGhpcyBpcyB0
cnVlIGZvciBUQ1AgdG9kYXkuIFRoZSBvdXQgb2YgYm94IGRlZmF1bHQgdXNlcyB0aGUgaGFuZHNo
YWtlIFJUVCB0byBtYWtlIGEgZGV0ZXJtaW5hdGlvbiBvZiB3aGF04oCZcyBpbnRyYS1EQyBidXQg
dGhlcmUgaXMgcmljaCBjb25maWd1cmF0aW9uIHRvIG92ZXJyaWRlIHRoZSBkZWZhdWx0IGFuZCBz
ZXQgaXQgYmFzZWQgb24gNC10dXBsZSBmaWx0ZXJzLg0KDQpBbmQgdGhlcmUgd29ya2xvYWRzIGxp
a2UgY2xvdWQgc3RvcmFnZSBhbmQgbGl2ZSBtaWdyYXRpb24gdGhhdCBhcmUgYnkgdmlydHVlIG9m
IGRlcGxveW1lbnQgaW50cmEtREMuIFRoZXNlIGNhbm5vdCBiZSBsb2FkIHNoaWZ0ZWQgYXMgdGhl
eSB1c2UgcHJpdmF0ZSBJUCBhZGRyZXNzIHNwYWNlLg0KDQpGcm9tOiBUZWQgSGFyZGllIFttYWls
dG86dGVkLmlldGZAZ21haWwuY29tXQ0KU2VudDogVHVlc2RheSwgTWF5IDEsIDIwMTggODo1NSBB
TQ0KVG86IFJvYmVydG8gUGVvbiA8ZmVuaXhAZmIuY29tPg0KQ2M6IFNhbHosIFJpY2ggPHJzYWx6
QGFrYW1haS5jb20+OyBCZW5qYW1pbiBLYWR1ayA8YmthZHVrQGFrYW1haS5jb20+OyBQcmF2ZWVu
IEJhbGFzdWJyYW1hbmlhbiA8cHJhdmJAbWljcm9zb2Z0LmNvbT47IElFVEYgUVVJQyBXRyA8cXVp
Y0BpZXRmLm9yZz4NClN1YmplY3Q6IFJlOiBHZXR0aW5nIHRvIGNvbnNlbnN1cyBvbiBwYWNrZXQg
bnVtYmVyIGVuY3J5cHRpb24NCg0KT24gVHVlLCBNYXkgMSwgMjAxOCBhdCA4OjEzIEFNLCBSb2Jl
cnRvIFBlb24gPGZlbml4QGZiLmNvbTxtYWlsdG86ZmVuaXhAZmIuY29tPj4gd3JvdGU6DQpBbHNv
LCBQcmlzbS4NCg0KLT1SDQoNCg0KDQpUaGF0J3MgYSBsaXR0bGUgbW9yZSBzdWNjaW5jdCB0aGFu
IEkgd291bGQgYmUsIGJ1dCB5ZXMuICBIb3cgZG9lcyBhbiBhcHBsaWNhdGlvbiBrbm93IHRoYXQg
dGhlIGZsb3cgaXQgaXMgaW5pdGlhdGluZyB3aWxsIHRyYXZlcnNlIGEgdG9wb2xvZ3kgdGhhdCBp
cyBkZWVtZWQgdG8gYmUgd2l0aGluIGEgY29udHJvbGxlZCBlbnZpcm9ubWVudD8gIFlvdSBjYW4g
c2F5ICJjb25maWd1cmF0aW9uIiBidXQgSSBmZWFyIGl0IHdpbGwgdHVybiB1cCBvbiBhIHBvc3Qt
aXQgIDxodHRwczovL3VybGRlZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cHMtM0Ff
X25hMDEuc2FmZWxpbmtzLnByb3RlY3Rpb24ub3V0bG9vay5jb21fLTNGdXJsLTNEaHR0cHMtMjUz
QS0yNTJGLTI1MkZpLmtpbmphLTJEaW1nLmNvbS0yNTJGZ2F3a2VyLTJEbWVkaWEtMjUyRmltYWdl
LTI1MkZ1cGxvYWQtMjUyRnMtMkQtMkRFZHU2TFB1OS0yRC0yRC0yNTJGYy01RnNjYWxlLTI1MkNm
LTVGYXV0by0yNTJDZmwtNUZwcm9ncmVzc2l2ZS0yNTJDcS01RjgwLTI1MkN3LTVGODAwLTI1MkYx
OTR0aGJ0eWVuY3MwanBnLmpwZy0yNmRhdGEtM0QwMi0yNTdDMDEtMjU3Q3ByYXZiLTI1NDBtaWNy
b3NvZnQuY29tLTI1N0M0ZGE0NGU4YWMxZGY0NzA4YWQ4ODA4ZDVhZjdiZmNhOC0yNTdDNzJmOTg4
YmY4NmYxNDFhZjkxYWIyZDdjZDAxMWRiNDctMjU3QzEtMjU3QzEtMjU3QzYzNjYwNzg2OTQxMTI1
ODk3Ni0yNnNkYXRhLTNEUHJvbFNIa2JGMlNnTUgzcWRRTi0yNTJCWkZva1h2c0VCZi0yNTJGM285
TWFVbmlsMGc4LTI1M0QtMjZyZXNlcnZlZC0zRDAmZD1Ed01HYVEmYz01VkQwUlR0TmxUaDN5Y2Q0
MWIzTVV3JnI9QzBzVW8tTEZOQmFZZnlvYUNzZjZUQSZtPVR1VmZ6eXBvLUNaTG81MjJsZ01Sckxw
S3hjRmFIdlc5a2ROU0k1N2xYVDAmcz1CeTJkX3RvN1h6TEVnQUwzT3I5Y1pjMkF5a3llLVBaRWVu
RlFEdmlBVWx3JmU9PiBpZiB5b3UgZG8uICBMb2FkcyBzaGlmdCwgcmVzb3VyY2VzIG1vdmUsIGFu
ZCBzdWRkZW5seSB5b3UgZmluZCB0aGF0IGhvc3Qgd2hpY2ggdXNlZCB0byBiZSBpbiB0aGUgc2Ft
ZSByYWNrLCBiZWluZyBkb3duLCBoYXMgbG9hZC1zaGlmdGVkIHRvIHRoZSBuZXh0IGluc3RhbmNl
LCAgaW4gYSBkYXRhY2VudGVyIDUwMCBtaWxlcyBhd2F5IGFjcm9zcyBhIHZlcnkgZGlmZmVyZW50
IG5ldHdvcmsuDQoNCk1hbnkgbW9kZXJuIGRlcGxveW1lbnRzIGFyZSBhbHNvIGluIHNvbWVvbmUg
ZWxzZSdzIGRhdGEgY2VudGVyLCBzbyBzYXlpbmcgIkRhdGEgY2VudGVyIG5ldHdvcmtzIiBkb2Vz
bid0IHNheSBtdWNoIGFib3V0IHdoeSB5b3UncmUgdHJ1c3RpbmcgdGhlIG5ldHdvcmsgaW5zaWRl
Lg0KVGVkDQoNClNlbnQgdmlhIHRoZSBTYW1zdW5nIEdhbGF4eSBTNywgYW4gQVQmVCA0RyBMVEUg
c21hcnRwaG9uZQ0KDQoNCi0tLS0tLS0tIE9yaWdpbmFsIG1lc3NhZ2UgLS0tLS0tLS0NCkZyb206
ICJTYWx6LCBSaWNoIiA8cnNhbHo9NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnPG1haWx0bzo0
MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmc+Pg0KRGF0ZTogNS8xLzE4IDU6MjUgQU0gKEdNVC0w
ODowMCkNClRvOiBCZW5qYW1pbiBLYWR1ayA8YmthZHVrPTQwYWthbWFpLmNvbUBkbWFyYy5pZXRm
Lm9yZzxtYWlsdG86NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnPj4sIFByYXZlZW4gQmFsYXN1
YnJhbWFuaWFuIDxwcmF2Yj00MG1pY3Jvc29mdC5jb21AZG1hcmMuaWV0Zi5vcmc8bWFpbHRvOjQw
bWljcm9zb2Z0LmNvbUBkbWFyYy5pZXRmLm9yZz4+DQpDYzogSUVURiBRVUlDIFdHIDxxdWljQGll
dGYub3JnPG1haWx0bzpxdWljQGlldGYub3JnPj4NClN1YmplY3Q6IFJlOiBHZXR0aW5nIHRvIGNv
bnNlbnN1cyBvbiBwYWNrZXQgbnVtYmVyIGVuY3J5cHRpb24NCg0KICAgID4gSSBkaXNhZ3JlZSB0
aGF0IHdlIG5lZWQgYW55IG1vcmUgZGF0YSBmb3Igbm90IGRvaW5nIFBORSBpbiB0aGUgZGF0YWNl
bnRlci4gV2h5IHdvdWxkIHdlIGFkZCBhbiBleHRyYSBlbmNyeXB0LWRlY3J5cHQgc3RlcCBmb3Ig
bm8gb2J2aW91cyBiZW5lZml0Pw0KDQpJIGFtIGNvbmNlcm5lZCB0aGF0IHBlb3BsZSB3aWxsIG1p
cy1pbnRlcnByZXQgdGhlIG1lYW5pbmcgb2YgYSBkYXRhY2VudGVyLCBhbmQgdGhpbmsgdGhhdCBh
IGJ1bmNoIG9mIHNlcnZlcnMsIG9yIGV2ZW4gYSByYWNrLCBpbiBhbiBvcGVuIGNvbG8gc3BhY2Ug
aXMgYSAiZGF0YWNlbnRlci4iICBDb21wdXRlcnMga2VlcCBnZXR0aW5nIGZhc3Rlci4NCg0K

--_000_AFD9317B499C4C56A571EDFEDC5093B9fbcom_
Content-Type: text/html; charset="utf-8"
Content-ID: <468AB3A864257B4EB3DA1238584A79F6@namprd15.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1i
b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
IixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAubXNv
bm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1hbDANCgl7bXNvLXN0eWxlLW5hbWU6
bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowaW47
DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGluOw0KCWZvbnQt
c2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5F
bWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNh
bGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQpzcGFuLkVtYWlsU3R5bGUx
OQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJy
aSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21z
by1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29y
ZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBp
biAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwv
c3R5bGU+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1
cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
WXVwLiBJIGtub3cuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5QcmlzbSB3
YXMgZXllLW9wZW5pbmcgcGFydGlhbGx5IGJlY2F1c2Ugb2YgdGhlIGZhY3QgdGhhdCB0aGUgcGFj
a2V0cyB3ZXJlIG5vdCBnb2luZyBhY3Jvc3MgdGhlIGludGVybmV0LCBidXQgcmF0aGVyIHdpdGhp
biBhIHNlY3VyZSBuZXR3b3JrLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIGJlbGlldmUgdGhh
dCBvc3NpZmljYXRpb24gYWxvbmUgaXMgYSBnb29kIGVub3VnaCByZWFzb24gdG8gZG8gUE5FLjxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhlIGNoZXJyeSBmb3IgbWUgaXMg
dGhhdCBpdCwgYWxvbmcgd2l0aCBvdGhlciBhY3Rpb25zL21pdGlnYXRpb25zLCBtYWtlcyBsaW5r
YWJpbGl0eSBtb3JlIGRpZmZpY3VsdCBmb3IgbWFsaWNpb3VzIGFjdG9ycy48YnI+DQpDUklNRSBh
bmQgcmVsYXRlZCB3YXMgZXllLW9wZW5pbmcgYmVjYXVzZSBpdCBleHBvc2VkIHRoZSBwb3dlciBv
ZiB0aGUgb2JzZXJ2YWJsZSBzaWRlLWNoYW5uZWwuDQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxicj4NCi09UjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXIt
dG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtjb2xvcjpi
bGFjayI+RnJvbTogPC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtjb2xv
cjpibGFjayI+UVVJQyAmbHQ7cXVpYy1ib3VuY2VzQGlldGYub3JnJmd0OyBvbiBiZWhhbGYgb2Yg
UHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gJmx0O3ByYXZiPTQwbWljcm9zb2Z0LmNvbUBkbWFyYy5p
ZXRmLm9yZyZndDs8YnI+DQo8Yj5EYXRlOiA8L2I+VHVlc2RheSwgTWF5IDEsIDIwMTggYXQgOToz
NSBBTTxicj4NCjxiPlRvOiA8L2I+VGVkIEhhcmRpZSAmbHQ7dGVkLmlldGZAZ21haWwuY29tJmd0
OywgUm9iZXJ0byBQZW9uICZsdDtmZW5peEBmYi5jb20mZ3Q7PGJyPg0KPGI+Q2M6IDwvYj4mcXVv
dDtTYWx6LCBSaWNoJnF1b3Q7ICZsdDtyc2FsekBha2FtYWkuY29tJmd0OywgQmVuamFtaW4gS2Fk
dWsgJmx0O2JrYWR1a0Bha2FtYWkuY29tJmd0OywgSUVURiBRVUlDIFdHICZsdDtxdWljQGlldGYu
b3JnJmd0Ozxicj4NCjxiPlN1YmplY3Q6IDwvYj5SRTogR2V0dGluZyB0byBjb25zZW5zdXMgb24g
cGFja2V0IG51bWJlciBlbmNyeXB0aW9uPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxhIG5hbWU9Il9NYWlsT3JpZ2luYWxCb2R5Ij5UaGlzIGlz
IG5vdCBhYm91dCBwdXR0aW5nIHBsYWludGV4dCBkYXRhIG9uIHRoZSBuZXR3b3JrLCB0aGlzIGlz
IGFib3V0IG5vdCBhZGRpbmcgUE5FIHdoaWNoIGlzIGludGVuZGVkIGZvciBwcmV2ZW50aW5nIG9z
c2lmaWNhdGlvbi4gU28gSSBkb27igJl0IHVuZGVyc3RhbmQgd2hhdCB0aGUgdHJ1c3QgaXNzdWUg
YmVpbmcgcmVmZXJyZWQgdG8gaXMgaW4gY2FzZSBvZg0KIHRoZSByYXJlIG1pc2NvbmZpZy4gPG86
cD48L286cD48L2E+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1i
b29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdp
bmFsQm9keSI+V2l0aGluIGEgREMgc2V2ZXJhbCB0aGluZ3MgYXJlIGRpZmZlcmVudCDigJMgdGhl
IGRlcGxveW1lbnQgbWF5IG5lZWQgZGlmZmVyZW50IGNvbmdlc3Rpb24gY29udHJvbCBsaWtlIERD
VENQLCBkaWZmZXJlbnQgc2V0dGluZ3MgZm9yIHZhcmlvdXMgdHJhbnNwb3J0IHBhcmFtZXRlcnMg
KGxpa2UgbWlucnRvIGFuZCBtYXggQUNLIGRlbGF5KSwNCiBsYXJnZXIgZmxvdyBjb250cm9sIHdp
bmRvdyBldGMuIFRoaXMgaXMgdHJ1ZSBmb3IgVENQIHRvZGF5LiBUaGUgb3V0IG9mIGJveCBkZWZh
dWx0IHVzZXMgdGhlIGhhbmRzaGFrZSBSVFQgdG8gbWFrZSBhIGRldGVybWluYXRpb24gb2Ygd2hh
dOKAmXMgaW50cmEtREMgYnV0IHRoZXJlIGlzIHJpY2ggY29uZmlndXJhdGlvbiB0byBvdmVycmlk
ZSB0aGUgZGVmYXVsdCBhbmQgc2V0IGl0IGJhc2VkIG9uIDQtdHVwbGUgZmlsdGVycy4NCjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28t
Ym9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmln
aW5hbEJvZHkiPkFuZCB0aGVyZSB3b3JrbG9hZHMgbGlrZSBjbG91ZCBzdG9yYWdlIGFuZCBsaXZl
IG1pZ3JhdGlvbiB0aGF0IGFyZSBieSB2aXJ0dWUgb2YgZGVwbG95bWVudCBpbnRyYS1EQy4gVGhl
c2UgY2Fubm90IGJlIGxvYWQgc2hpZnRlZCBhcyB0aGV5IHVzZSBwcml2YXRlIElQIGFkZHJlc3Mg
c3BhY2UuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+Jm5ic3A7PG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFy
azpfTWFpbE9yaWdpbmFsQm9keSI+PGI+RnJvbTo8L2I+IFRlZCBIYXJkaWUgW21haWx0bzp0ZWQu
aWV0ZkBnbWFpbC5jb21dDQo8YnI+DQo8Yj5TZW50OjwvYj4gVHVlc2RheSwgTWF5IDEsIDIwMTgg
ODo1NSBBTTxicj4NCjxiPlRvOjwvYj4gUm9iZXJ0byBQZW9uICZsdDtmZW5peEBmYi5jb20mZ3Q7
PGJyPg0KPGI+Q2M6PC9iPiBTYWx6LCBSaWNoICZsdDtyc2FsekBha2FtYWkuY29tJmd0OzsgQmVu
amFtaW4gS2FkdWsgJmx0O2JrYWR1a0Bha2FtYWkuY29tJmd0OzsgUHJhdmVlbiBCYWxhc3VicmFt
YW5pYW4gJmx0O3ByYXZiQG1pY3Jvc29mdC5jb20mZ3Q7OyBJRVRGIFFVSUMgV0cgJmx0O3F1aWNA
aWV0Zi5vcmcmZ3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBHZXR0aW5nIHRvIGNvbnNlbnN1
cyBvbiBwYWNrZXQgbnVtYmVyIGVuY3J5cHRpb248bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxC
b2R5Ij4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+T24gVHVl
LCBNYXkgMSwgMjAxOCBhdCA4OjEzIEFNLCBSb2JlcnRvIFBlb24gJmx0Ozwvc3Bhbj48YSBocmVm
PSJtYWlsdG86ZmVuaXhAZmIuY29tIiB0YXJnZXQ9Il9ibGFuayI+PHNwYW4gc3R5bGU9Im1zby1i
b29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+ZmVuaXhAZmIuY29tPC9zcGFuPjxzcGFuIHN0eWxl
PSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPjwvc3Bhbj48L2E+PHNwYW4gc3R5bGU9
Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+Jmd0Ow0KIHdyb3RlOjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25l
O2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBw
dDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1yaWdodDowaW47bWFy
Z2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij5BbHNvLCBQ
cmlzbS4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5
Ij4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij4t
PVImbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij4m
bmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij4mbmJz
cDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2Nr
cXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29r
bWFyazpfTWFpbE9yaWdpbmFsQm9keSI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIu
MHB0Ij48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij5UaGF0J3Mg
YSBsaXR0bGUgbW9yZSBzdWNjaW5jdCB0aGFuIEkgd291bGQgYmUsIGJ1dCB5ZXMuJm5ic3A7IEhv
dyBkb2VzIGFuIGFwcGxpY2F0aW9uIGtub3cgdGhhdCB0aGUgZmxvdyBpdCBpcyBpbml0aWF0aW5n
IHdpbGwgdHJhdmVyc2UgYSB0b3BvbG9neSB0aGF0IGlzIGRlZW1lZCB0byBiZQ0KIHdpdGhpbiBh
IGNvbnRyb2xsZWQgZW52aXJvbm1lbnQ/Jm5ic3A7IFlvdSBjYW4gc2F5ICZxdW90O2NvbmZpZ3Vy
YXRpb24mcXVvdDsgYnV0IEkgZmVhciBpdCB3aWxsIHR1cm4NCjwvc3Bhbj48YSBocmVmPSJodHRw
czovL3VybGRlZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cHMtM0FfX25hMDEuc2Fm
ZWxpbmtzLnByb3RlY3Rpb24ub3V0bG9vay5jb21fLTNGdXJsLTNEaHR0cHMtMjUzQS0yNTJGLTI1
MkZpLmtpbmphLTJEaW1nLmNvbS0yNTJGZ2F3a2VyLTJEbWVkaWEtMjUyRmltYWdlLTI1MkZ1cGxv
YWQtMjUyRnMtMkQtMkRFZHU2TFB1OS0yRC0yRC0yNTJGYy01RnNjYWxlLTI1MkNmLTVGYXV0by0y
NTJDZmwtNUZwcm9ncmVzc2l2ZS0yNTJDcS01RjgwLTI1MkN3LTVGODAwLTI1MkYxOTR0aGJ0eWVu
Y3MwanBnLmpwZy0yNmRhdGEtM0QwMi0yNTdDMDEtMjU3Q3ByYXZiLTI1NDBtaWNyb3NvZnQuY29t
LTI1N0M0ZGE0NGU4YWMxZGY0NzA4YWQ4ODA4ZDVhZjdiZmNhOC0yNTdDNzJmOTg4YmY4NmYxNDFh
ZjkxYWIyZDdjZDAxMWRiNDctMjU3QzEtMjU3QzEtMjU3QzYzNjYwNzg2OTQxMTI1ODk3Ni0yNnNk
YXRhLTNEUHJvbFNIa2JGMlNnTUgzcWRRTi0yNTJCWkZva1h2c0VCZi0yNTJGM285TWFVbmlsMGc4
LTI1M0QtMjZyZXNlcnZlZC0zRDAmYW1wO2Q9RHdNR2FRJmFtcDtjPTVWRDBSVHRObFRoM3ljZDQx
YjNNVXcmYW1wO3I9QzBzVW8tTEZOQmFZZnlvYUNzZjZUQSZhbXA7bT1UdVZmenlwby1DWkxvNTIy
bGdNUnJMcEt4Y0ZhSHZXOWtkTlNJNTdsWFQwJmFtcDtzPUJ5MmRfdG83WHpMRWdBTDNPcjljWmMy
QXlreWUtUFpFZW5GUUR2aUFVbHcmYW1wO2U9Ij48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9N
YWlsT3JpZ2luYWxCb2R5Ij51cA0KIG9uIGEgcG9zdC1pdCZuYnNwOyA8L3NwYW4+PHNwYW4gc3R5
bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+PC9zcGFuPjwvYT48c3BhbiBzdHls
ZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij5pZiB5b3UgZG8uJm5ic3A7IExvYWRz
IHNoaWZ0LCByZXNvdXJjZXMgbW92ZSwgYW5kIHN1ZGRlbmx5IHlvdSBmaW5kIHRoYXQgaG9zdCB3
aGljaCB1c2VkIHRvIGJlIGluIHRoZSBzYW1lIHJhY2ssIGJlaW5nIGRvd24sIGhhcyBsb2FkLXNo
aWZ0ZWQNCiB0byB0aGUgbmV4dCBpbnN0YW5jZSwmbmJzcDsgaW4gYSBkYXRhY2VudGVyIDUwMCBt
aWxlcyBhd2F5IGFjcm9zcyBhIHZlcnkgZGlmZmVyZW50IG5ldHdvcmsuJm5ic3A7DQo8YnI+DQo8
YnI+DQpNYW55IG1vZGVybiBkZXBsb3ltZW50cyBhcmUgYWxzbyBpbiBzb21lb25lIGVsc2UncyBk
YXRhIGNlbnRlciwgc28gc2F5aW5nICZxdW90O0RhdGEgY2VudGVyIG5ldHdvcmtzJnF1b3Q7IGRv
ZXNuJ3Qgc2F5IG11Y2ggYWJvdXQgd2h5IHlvdSdyZSB0cnVzdGluZyB0aGUgbmV0d29yayBpbnNp
ZGUuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+VGVkPG86
cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+Jm5ic3A7PG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0
O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0OjBpbjttYXJn
aW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdiBpZD0ibV8tMzc3NTU1MjA5NzU4
MjY2NDU2MnhfY29tcG9zZXJfc2lnbmF0dXJlIj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjkuNXB0O2NvbG9yOiM1NzU3NTciPlNlbnQgdmlhIHRoZSBTYW1zdW5nIEdh
bGF4eSBTNywgYW4gQVQmYW1wO1QgNEcgTFRFIHNtYXJ0cGhvbmU8L3NwYW4+PG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij4mbmJzcDs8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij4mbmJzcDs8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij4tLS0tLS0tLSBPcmlnaW5hbCBt
ZXNzYWdlIC0tLS0tLS0tPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFs
Qm9keSI+RnJvbTogJnF1b3Q7U2FseiwgUmljaCZxdW90OyAmbHQ7cnNhbHo9PC9zcGFuPjxhIGhy
ZWY9Im1haWx0bzo0MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj48
c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij40MGFrYW1haS5jb21A
ZG1hcmMuaWV0Zi5vcmc8L3NwYW4+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdp
bmFsQm9keSI+PC9zcGFuPjwvYT48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2lu
YWxCb2R5Ij4mZ3Q7DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxC
b2R5Ij5EYXRlOiA1LzEvMTggNToyNSBBTSAoR01ULTA4OjAwKQ0KPG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1z
by1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+VG86IEJlbmphbWluIEthZHVrICZsdDtia2Fk
dWs9PC9zcGFuPjxhIGhyZWY9Im1haWx0bzo0MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmciIHRh
cmdldD0iX2JsYW5rIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5
Ij40MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmc8L3NwYW4+PHNwYW4gc3R5bGU9Im1zby1ib29r
bWFyazpfTWFpbE9yaWdpbmFsQm9keSI+PC9zcGFuPjwvYT48c3BhbiBzdHlsZT0ibXNvLWJvb2tt
YXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij4mZ3Q7LA0KIFByYXZlZW4gQmFsYXN1YnJhbWFuaWFuICZs
dDtwcmF2Yj08L3NwYW4+PGEgaHJlZj0ibWFpbHRvOjQwbWljcm9zb2Z0LmNvbUBkbWFyYy5pZXRm
Lm9yZyIgdGFyZ2V0PSJfYmxhbmsiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmln
aW5hbEJvZHkiPjQwbWljcm9zb2Z0LmNvbUBkbWFyYy5pZXRmLm9yZzwvc3Bhbj48c3BhbiBzdHls
ZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij48L3NwYW4+PC9hPjxzcGFuIHN0eWxl
PSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPiZndDsNCjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJt
c28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPkNjOiBJRVRGIFFVSUMgV0cgJmx0Ozwvc3Bh
bj48YSBocmVmPSJtYWlsdG86cXVpY0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPjxzcGFuIHN0
eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPnF1aWNAaWV0Zi5vcmc8L3NwYW4+
PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+PC9zcGFuPjwvYT48
c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij4mZ3Q7DQo8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij5TdWJqZWN0OiBSZTogR2V0
dGluZyB0byBjb25zZW5zdXMgb24gcGFja2V0IG51bWJlciBlbmNyeXB0aW9uDQo8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij4mbmJzcDs8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBzdHlsZT0ibXNv
LWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij4mbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyBJIGRp
c2FncmVlIHRoYXQgd2UgbmVlZCBhbnkgbW9yZSBkYXRhIGZvciBub3QgZG9pbmcgUE5FIGluIHRo
ZSBkYXRhY2VudGVyLiBXaHkgd291bGQgd2UgYWRkIGFuIGV4dHJhIGVuY3J5cHQtZGVjcnlwdCBz
dGVwIGZvciBubyBvYnZpb3VzIGJlbmVmaXQ/PGJyPg0KPGJyPg0KSSBhbSBjb25jZXJuZWQgdGhh
dCBwZW9wbGUgd2lsbCBtaXMtaW50ZXJwcmV0IHRoZSBtZWFuaW5nIG9mIGEgZGF0YWNlbnRlciwg
YW5kIHRoaW5rIHRoYXQgYSBidW5jaCBvZiBzZXJ2ZXJzLCBvciBldmVuIGEgcmFjaywgaW4gYW4g
b3BlbiBjb2xvIHNwYWNlIGlzIGEgJnF1b3Q7ZGF0YWNlbnRlci4mcXVvdDsmbmJzcDsgQ29tcHV0
ZXJzIGtlZXAgZ2V0dGluZyBmYXN0ZXIuDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+
Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9i
b2R5Pg0KPC9odG1sPg0K

--_000_AFD9317B499C4C56A571EDFEDC5093B9fbcom_--


From nobody Tue May  1 16:21:50 2018
Return-Path: <prvs=86592f1e95=fenix@fb.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4C1EE126DFB for <quic@ietfa.amsl.com>; Tue,  1 May 2018 16:21:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.73
X-Spam-Level: 
X-Spam-Status: No, score=-0.73 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=g74hDkyr; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=G8e4wK+y
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 O1xa8oacgxxV for <quic@ietfa.amsl.com>; Tue,  1 May 2018 16:21:45 -0700 (PDT)
Received: from mx0a-00082601.pphosted.com (mx0a-00082601.pphosted.com [67.231.145.42]) (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 8612B126BF6 for <quic@ietf.org>; Tue,  1 May 2018 16:21:45 -0700 (PDT)
Received: from pps.filterd (m0109333.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w41NKFdN015047; Tue, 1 May 2018 16:21:25 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=facebook; bh=nQ7rpEd2c1s87xk5OPPQjIj+S2TF9RPp2TCxJ4TIVlk=; b=g74hDkyrLrcM/UGps6SYhHhB7Q/aTyeYWFIGQscDxTfi7vheRw0wFkRCcH33Y3f3LlYq fDwXBs+zKnvrtUwjKEyIt6F91V/BQVfD8f+2ooPtC9L+XYQqDnOZ9Y2Hyiaz2GPcaJqG 5wNXlY7i1fnjA/uAcXW1aGM75QxhOt4Kx6M= 
Received: from maileast.thefacebook.com ([199.201.65.23]) by mx0a-00082601.pphosted.com with ESMTP id 2hq0jtg5ys-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 01 May 2018 16:21:25 -0700
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (192.168.183.28) by o365-in.thefacebook.com (192.168.177.25) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 1 May 2018 19:21:22 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version;  bh=nQ7rpEd2c1s87xk5OPPQjIj+S2TF9RPp2TCxJ4TIVlk=; b=G8e4wK+yGKxJAHE/3ULWLKchQ/fGwBhiOkhmn0EsFTjLTB5bmJ9rudffyAjRaFXmcqcS8B75F3RrmlQhzC8uK6LqoDM4MWbV8k6MKeh37DW5grTYPkMzC48tM59DthEanPtnTzBcgdjbCM/F/bfOpskhg8nv8VnmENmmn6hQ8vc=
Received: from BY2PR15MB0775.namprd15.prod.outlook.com (10.164.171.11) by BY2PR15MB0373.namprd15.prod.outlook.com (10.163.109.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.715.24; Tue, 1 May 2018 23:21:20 +0000
Received: from BY2PR15MB0775.namprd15.prod.outlook.com ([fe80::6c4c:bbf3:ec3b:d45e]) by BY2PR15MB0775.namprd15.prod.outlook.com ([fe80::6c4c:bbf3:ec3b:d45e%14]) with mapi id 15.20.0715.024; Tue, 1 May 2018 23:21:20 +0000
From: Roberto Peon <fenix@fb.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Benjamin Kaduk <bkaduk=40akamai.com@dmarc.ietf.org>
CC: Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>, "IETF QUIC WG" <quic@ietf.org>
Subject: Re: Getting to consensus on packet number encryption
Thread-Topic: Getting to consensus on packet number encryption
Thread-Index: AQHTy9GjyGQaKf4GI0anNhXTngANsKPwZ0sAgAC4ugCAAARcAIAAG5CAgAAFCACAAACJgIAAEVkAgACR+ICAAVFHAIALXUEAgAVKTpWAAJn+AIABxdSAgACOHICAB/EyAIACo7YAgACiL4CAAADQgIAAIs8AgAAm/YCAABExgIAABpIAgAAK6ACAAPIgAIAA5wYAgACzcoCAAHHMgIAEe1cAgAABEACAABWHgIAA8UgAgAA6QwCAAAlqgA==
Date: Tue, 1 May 2018 23:21:20 +0000
Message-ID: <02563F00-79ED-4116-9318-764F3DB94FA6@fb.com>
References: <CANatvzwCYrOZULG3iVmDFp97nr=M5=Gufo8TZjOGQVFUpsn0bQ@mail.gmail.com> <CAAedzxqDcPXJUE83KVnDiU23PvqDcTCrc6rRMw09FexjJA-Y6Q@mail.gmail.com> <CANatvzwjYE6EdvFtOXJMVQnutbVQ4YY+=XsQFzKwHzqWzZ4U+w@mail.gmail.com> <d32ade7b56bf4651952659307c08893b@usma1ex-dag1mb5.msg.corp.akamai.com> <CANatvzwHtCn8rLB8npf3i7PGyYZhVDRd2uojh5hv3uxtFPEsSA@mail.gmail.com> <58447D8E-782C-431C-8FC3-71124B10A047@trammell.ch> <CACpbDcdfF9w3qqrH1eB0sGU_4vheD9aMP5EXnp1o3Y19N19NUg@mail.gmail.com> <e8b4931a-3931-5b8d-8dad-3ca1939d5542@huitema.net> <CAKcm_gPaj3o-VTdA_0+Kk+nTcVJrYcs_BMyOiDGXKub3gB=GLg@mail.gmail.com> <MWHPR21MB063869878060E850137210FEB6820@MWHPR21MB0638.namprd21.prod.outlook.com> <20180501121906.GA5742@akamai.com> <CAKKJt-dgPP8FbP0=tEpm5vf99C9qXKYRWN0PY3dzfphqdBGypw@mail.gmail.com>
In-Reply-To: <CAKKJt-dgPP8FbP0=tEpm5vf99C9qXKYRWN0PY3dzfphqdBGypw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.c.0.180410
x-originating-ip: [2620:10d:c090:200::6:ddb8]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BY2PR15MB0373; 7:WdjgS6FMQ//u/qRs3zl0B6bI1VLBTS6finjaitu7obrRoU26WP6wbHn/t8LkZZ82tev6U9QO+LPV/u/2Tc2b7paJpdX16jmarxA3ukroXgj/Z6rJwj4ZVxdpuktI66J3oZ4Jwb9i6R4FYPO/cD5FBpuUqKaI43rIKqQS1knDbjfxa3II9WeCsTElBhX0RTHYDYaqIgxs8bGXWkND+EAe6+/d3l9i4q2FGQye/HAMTjSFS2HfOY5p30ta7kIYz8kQ; 20:bY1xwNNMLLmgq+aMtTzzqo2whrdXeL7cFjTpaYh+DQtKaY0JfDF+3yJgbHYL7LGubEuRdKhmtnGoLji2PsqExfy/M8hdc79DMNDBUU3fT8Dpu2iDJ+/dcTGqrrV1uAOeFuqkT+LyBwFgJ0kfxZCvNNYj7eSdzYwtsmvNgDul0bE=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BY2PR15MB0373; 
x-ms-traffictypediagnostic: BY2PR15MB0373:
x-microsoft-antispam-prvs: <BY2PR15MB03737AB6F13430AB9216422ECD810@BY2PR15MB0373.namprd15.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(10436049006162)(120809045254105)(85827821059158)(100405760836317)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(10201501046)(3002001)(93006095)(93001095)(3231254)(11241501184)(944501410)(52105095)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123562045)(20161123564045)(20161123558120)(6072148)(201708071742011); SRVR:BY2PR15MB0373; BCL:0; PCL:0; RULEID:; SRVR:BY2PR15MB0373; 
x-forefront-prvs: 06592CCE58
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(39860400002)(39380400002)(346002)(376002)(396003)(199004)(189003)(82746002)(5660300001)(105586002)(11346002)(110136005)(81156014)(83716003)(58126008)(33656002)(606006)(81166006)(446003)(25786009)(6116002)(2906002)(46003)(6436002)(476003)(2616005)(106356001)(6486002)(54906003)(8676002)(36756003)(486006)(3660700001)(186003)(229853002)(6246003)(39060400002)(478600001)(7736002)(966005)(8936002)(6506007)(14454004)(102836004)(93886005)(3280700002)(86362001)(59450400001)(68736007)(53936002)(53546011)(54896002)(5250100002)(6306002)(236005)(6512007)(97736004)(99286004)(76176011)(316002)(4326008)(2900100001)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR15MB0373; H:BY2PR15MB0775.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: fb.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: pY/+zMDjb/XMMczeUuWoGscoc1omI7bICoacjWUVpYN6y6v4Xs5CyncRVkt+V8nbyvcPgDTYPpXqPVjHoehyU4EnB2wiozq6evKLPj0Wvn2xIFIlBepPhBkV+z2uyTihhRMdsCasdUrUh5fzb82CWDKpizCg8m1ss48TuMfWx1YUHr/yykgy3CR4NZL8v/70
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_02563F0079ED41169318764F3DB94FA6fbcom_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 3f794111-d68b-4185-c869-08d5afba3fa0
X-MS-Exchange-CrossTenant-Network-Message-Id: 3f794111-d68b-4185-c869-08d5afba3fa0
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 May 2018 23:21:20.7197 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR15MB0373
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-01_13:, , signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/vy0t_3boSxyxuuy-B9tZEP0Ke7Q>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2018 23:21:48 -0000

--_000_02563F0079ED41169318764F3DB94FA6fbcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

R2l2ZW4gbXVjaCBvZiB3aGF0IEkgd2UgbmVlZCBmb3Igb3VyIGRlcGxveW1lbnRzIGZvciBwdWIt
c3ViIGFuZCB2aWRlbyB3aWxsIG5vdCBsaWtlbHkgYmUgaW4gVjEsIHlhLCBJ4oCZbSBhbHNvIGV4
cGVjdGluZyB2MiB0byBoYXBwZW4gcXVpY2tseS4NCi09Ug0KDQpGcm9tOiBRVUlDIDxxdWljLWJv
dW5jZXNAaWV0Zi5vcmc+IG9uIGJlaGFsZiBvZiBTcGVuY2VyIERhd2tpbnMgYXQgSUVURiA8c3Bl
bmNlcmRhd2tpbnMuaWV0ZkBnbWFpbC5jb20+DQpEYXRlOiBUdWVzZGF5LCBNYXkgMSwgMjAxOCBh
dCA4OjQ4IEFNDQpUbzogQmVuamFtaW4gS2FkdWsgPGJrYWR1az00MGFrYW1haS5jb21AZG1hcmMu
aWV0Zi5vcmc+DQpDYzogUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gPHByYXZiPTQwbWljcm9zb2Z0
LmNvbUBkbWFyYy5pZXRmLm9yZz4sIElFVEYgUVVJQyBXRyA8cXVpY0BpZXRmLm9yZz4NClN1Ympl
Y3Q6IFJlOiBHZXR0aW5nIHRvIGNvbnNlbnN1cyBvbiBwYWNrZXQgbnVtYmVyIGVuY3J5cHRpb24N
Cg0KRldJVywNCg0KT24gVHVlLCBNYXkgMSwgMjAxOCBhdCA3OjE5IEFNLCBCZW5qYW1pbiBLYWR1
ayA8YmthZHVrPTQwYWthbWFpLmNvbUBkbWFyYy5pZXRmLm9yZzxtYWlsdG86YmthZHVrPTQwYWth
bWFpLmNvbUBkbWFyYy5pZXRmLm9yZz4+IHdyb3RlOg0KT24gTW9uLCBBcHIgMzAsIDIwMTggYXQg
MDk6NTU6MzFQTSArMDAwMCwgUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gd3JvdGU6DQo+IEkgZGlz
YWdyZWUgdGhhdCB3ZSBuZWVkIGFueSBtb3JlIGRhdGEgZm9yIG5vdCBkb2luZyBQTkUgaW4gdGhl
IGRhdGFjZW50ZXIuIFdoeSB3b3VsZCB3ZSBhZGQgYW4gZXh0cmEgZW5jcnlwdC1kZWNyeXB0IHN0
ZXAgZm9yIG5vIG9idmlvdXMgYmVuZWZpdD8gVGhlIGNvc3Qgb2YgdGhpcyBvcGVyYXRpb24gd2ls
bCBrZWVwIG1hZ25pZnlpbmcgYXMgVURQIHBlcmZvcm1hbmNlIGltcHJvdmVzLiBXZSBoYXZlIHNl
dmVyYWwgb3B0aW1pemF0aW9ucyBwbGFubmVkIGZvciBVRFAsIGJ1dCBzaG9ydCBvZiBoYXJkd2Fy
ZSBvZmZsb2FkLCBub25lIGZvciBjcnlwdG8g4oCTIHRoaXMgaXMgYW4gaW1wb3J0YW50IHRyZW5k
IHRvIGFjY291bnQgZm9yIHBlcmZvcm1hbmNlIHdpc2UuIEZvciBzaG9ydCBwYWNrZXRzIGxpa2Ug
QUNLcyBhbiBleHRyYSBlbmNyeXB0IGRlY3J5cHQgc3RlcCBjYW4gYmVjb21lIGEgbGFyZ2UgZnJh
Y3Rpb24gb2YgQ1BVIGNvc3Qgb3ZlciB0aW1lLg0KDQpUaGVyZSBpcyBiZW5lZml0IGluIHVuaWZv
cm1pdHkgYW5kIHNpbXBsaWNpdHkgb2YgaW1wbGVtZW50YXRpb247IEkgY29uY2VkZSB0aGF0DQp0
aGUgY2xhaW1lZCBwb3RlbnRpYWwgYmVuZWZpdHMgYWJvdXQgdGhlIG1pZGRsZWJveCBlY29zeXN0
ZW0gYXJlIHNwZWN1bGF0aXZlLA0KYnV0IHRoZSBzaW1wbGljaXR5IHNlZW1zIGNsZWFyIHRvIG1l
Lg0KDQpXaXRoIHJlc3BlY3QgdG8gdGhlIGNvc3Qgb2YgdGhlIGNyeXB0bywgeWVzIHdlIGhhdmUg
c29tZSBudW1iZXJzLCBidXQgQUZBSUNUIHdlDQpkb24ndCBoYXZlIGEgZ3JlYXQgdmlldyBmb3Ig
aG93IHRoZXkgd2lsbCBmaXQgaW50byB0aGUgYnJvYWRlciBwaWN0dXJlIGFzDQppbXBsZW1lbnRh
dGlvbnMgbWF0dXJlLCBzbyB0byBzb21lIGV4dGVudCB0aGUgZXN0aW1hdGUgb2YgdGhlIG1hZ25p
dHVkZSBvZg0KZ3Jvd2luZyBjb3N0IG9mIGNyeXB0byBpcyBhbHNvIGEgc3BlY3VsYXRpdmUgcG9z
aXRpb24uICAoQWxzbywgd2hvIGlzIHRoZSAid2UiDQp0aGF0IGhhcyBzZXZlcmFsIG9wdGltaXph
dGlvbnMgcGxhbm5lZD8pDQoNCkluIG90aGVyIHdvcmRzLCBob3cgZG8gd2Uga25vdyB0aGlzIGlz
IG5vdCBwcmVtYXR1cmUgb3B0aW1pemF0aW9uPyAgU2hvdWxkbid0DQp3ZSB3YWl0IHVudGlsIHdl
IGhhdmUgYWN0dWFsIHBlcmZvcm1hbmNlIG51bWJlcnMgYmVmb3JlIGRvaW5nIGxvdHMgb2YNCm9w
dGltaXphdGlvbj8NCg0KSSBjYW4ndCBzcGVhayB0byB3aGV0aGVyIHRoaXMgb3B0aW1pemF0aW9u
IGlzIHByZW1hdHVyZSwgYnV0IEkgZG8gc3VzcGVjdCB0aGF0IGlmIG1vcmUgcGVvcGxlIHdlcmUg
bG9va2luZyBhdCBtb3JlIGFjdHVhbCBwZXJmb3JtYW5jZSBudW1iZXJzLCB0aGlzIGNvbnZlcnNh
dGlvbiBtaWdodCBjb252ZXJnZSBtb3JlIHF1aWNrbHkgLi4uDQoNCkkgd2FzIHVuZGVyIHRoZSBp
bXByZXNzaW9uIHRoYXQgUVVJQyB2ZXJzaW9ucyB3ZXJlIGdvaW5nIHRvIGJlDQpsaWdodHdlaWdo
dCwgc28gcHV0dGluZyBvdXQgdjEgd2l0aCBtYW5kYXRvcnkgUE5FIHdvdWxkIG5vdCBwcmVjbHVk
ZSBxdWlja2x5DQpmb2xsb3dpbmcgd2l0aCBhIFYzIHRoYXQgYWRhcHRzIHRvIGFueSBkaXNjb3Zl
cmVkIHBlcmZvcm1hbmNlIGNvbmNlcm5zLCB3aGV0aGVyDQpmb3IgZGF0YWNlbnRlciB1c2FnZSBv
ciBvdGhlcndpc2UuDQoNClllYWgsIGFib3V0IHRoYXQgLi4uDQoNCkkndmUgYmVlbiBhc2tpbmcg
aW4gYSBmZXcgcGxhY2VzIC0gbW9zdCByZWNlbnRseSwgYXQgaHR0cHM6Ly9kYXRhdHJhY2tlci5p
ZXRmLm9yZy9tZWV0aW5nLzEwMS9tYXRlcmlhbHMvbWludXRlcy0xMDEtcXVpYy0wMC5odG1sPGh0
dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRwcy0zQV9fZGF0YXRy
YWNrZXIuaWV0Zi5vcmdfbWVldGluZ18xMDFfbWF0ZXJpYWxzX21pbnV0ZXMtMkQxMDEtMkRxdWlj
LTJEMDAuaHRtbCZkPUR3TUZhUSZjPTVWRDBSVHRObFRoM3ljZDQxYjNNVXcmcj1DMHNVby1MRk5C
YVlmeW9hQ3NmNlRBJm09N2RrTWIyWVZYSDA3ODB2SXlvUndSTnJpWlV3aFVHNG42MUFiRW5VN1BU
ZyZzPXk1bElVMVEteWdCb09hR3M0RUluQ2hpMnJkLVpuWmtyQ3A4Mmc0ZHFEYVUmZT0+IC0gYWJv
dXQgdmVyc2lvbiBhcHBlYXJhbmNlIHJhdGVzLCBhbmQgSSBoYXZlbid0IGhlYXJkIGFuc3dlcnMg
dGhhdCBzb3VuZGVkIGxpa2UgdGhlIHdvcmtpbmcgZ3JvdXAgaGFkIHN0cm9uZyBhZ3JlZW1lbnQg
dGhhdCB2ZXJzaW9ucyB3ZXJlIGdvaW5nIHRvIHJvbGwgb3V0IHByZXR0eSBxdWlja2x5LiBGb3Ig
ZXhhbXBsZSwgZnJvbSB0aGF0IGNvbnZlcnNhdGlvbiwgSSBnb3QNCg0KU3BlbmNlciAoYXMgQUQp
OiBbZGVsZXRlZCBmaXJzdCB0aHJlZSBwb2ludHMsIHRvIGdldCB0b10gNC4gKGFzIFNwZW5jZXIp
IGRvbid0IGhhdmUgYSBnb29kIGZlZWxpbmcgYWJvdXQgdmVyc2lvbiBuZWdvdGlhdGluZyBhbmQg
aG93IG11Y2ggd2UgbWlnaHQgcm9sbCB0aGVtLg0KDQptbm90OiBub3QgZ29pbmcgdG8gd2FpdCA1
IHllYXJzIGZvciB2Mi4NCg0KU28sIHRoZSBjaGFpcnMgY2FuIGNvcnJlY3QgbWUgKGFuZCBzaG91
bGQsIGFuZCB0aGV5IGhhdmUgYmVmb3JlIG9uIG90aGVyIHRvcGljcyksIGJ1dCBJIHRoaW5rIEkn
dmUgaGVhcmQgYSBsb3Qgb2YgIndlIGRvbid0IGhhdmUgdG8gZ2V0IGV2ZXJ5dGhpbmcgcGVyZmVj
dCBpbiBRVUlDdjEsIGJlY2F1c2UgdGhlcmUgd2lsbCBiZSBvdGhlciB2ZXJzaW9ucyIsIGFuZCBu
b3QgYSBsb3Qgb2YgImFuZCB0aGUgb3RoZXIgdmVyc2lvbnMgd2lsbCBhcHBlYXIgcHJldHR5IHF1
aWNrbHkiLg0KDQpJIGRvbid0IGtub3cgd2hhdCBhbGwgdGhlIHBhcnRpY2lwYW50cyBhcmUgdGhp
bmtpbmcsIGJ1dCB0aGF0J3Mgd2hhdCB0aGUgcGVvcGxlIHdobyBhcmUgdGFsa2luZyBoYXZlIGJl
ZW4gc2F5aW5nIHRvIG1lLg0KDQpJTU8sIG9mIGNvdXJzZS4NCg0KU3BlbmNlciwgYXMgaW5kaXZp
ZHVhbA0KDQotQmVuDQoNCg==

--_000_02563F0079ED41169318764F3DB94FA6fbcom_
Content-Type: text/html; charset="utf-8"
Content-ID: <4ED98A80FF9D6E48B7E4355DE98FF433@namprd15.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1i
b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
IixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAubXNv
bm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1hbDANCgl7bXNvLXN0eWxlLW5hbWU6
bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowaW47
DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGluOw0KCWZvbnQt
c2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5n
bWFpbC0NCgl7bXNvLXN0eWxlLW5hbWU6Z21haWwtO30NCnNwYW4uRW1haWxTdHlsZTE5DQoJe21z
by1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5z
LXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxl
LXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlv
bjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGlu
O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT4N
CjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4N
CjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5HaXZlbiBt
dWNoIG9mIHdoYXQgSSB3ZSBuZWVkIGZvciBvdXIgZGVwbG95bWVudHMgZm9yIHB1Yi1zdWIgYW5k
IHZpZGVvIHdpbGwgbm90IGxpa2VseSBiZSBpbiBWMSwgeWEsIEnigJltIGFsc28gZXhwZWN0aW5n
IHYyIHRvIGhhcHBlbiBxdWlja2x5LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+LT1SPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRE
RiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2NvbG9yOmJsYWNrIj5Gcm9tOiA8L3Nw
YW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2NvbG9yOmJsYWNrIj5RVUlDICZs
dDtxdWljLWJvdW5jZXNAaWV0Zi5vcmcmZ3Q7IG9uIGJlaGFsZiBvZiBTcGVuY2VyIERhd2tpbnMg
YXQgSUVURiAmbHQ7c3BlbmNlcmRhd2tpbnMuaWV0ZkBnbWFpbC5jb20mZ3Q7PGJyPg0KPGI+RGF0
ZTogPC9iPlR1ZXNkYXksIE1heSAxLCAyMDE4IGF0IDg6NDggQU08YnI+DQo8Yj5UbzogPC9iPkJl
bmphbWluIEthZHVrICZsdDtia2FkdWs9NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnJmd0Ozxi
cj4NCjxiPkNjOiA8L2I+UHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gJmx0O3ByYXZiPTQwbWljcm9z
b2Z0LmNvbUBkbWFyYy5pZXRmLm9yZyZndDssIElFVEYgUVVJQyBXRyAmbHQ7cXVpY0BpZXRmLm9y
ZyZndDs8YnI+DQo8Yj5TdWJqZWN0OiA8L2I+UmU6IEdldHRpbmcgdG8gY29uc2Vuc3VzIG9uIHBh
Y2tldCBudW1iZXIgZW5jcnlwdGlvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGEgbmFtZT0iX01haWxPcmlnaW5hbEJvZHkiPkZX
SVcsJm5ic3A7IDxvOnA+PC9vOnA+PC9hPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij48bzpwPiZuYnNw
OzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+T24gVHVlLCBNYXkgMSwgMjAxOCBh
dCA3OjE5IEFNLCBCZW5qYW1pbiBLYWR1ayAmbHQ7PC9zcGFuPjxhIGhyZWY9Im1haWx0bzpia2Fk
dWs9NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+PHNwYW4gc3R5
bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+YmthZHVrPTQwYWthbWFpLmNvbUBk
bWFyYy5pZXRmLm9yZzwvc3Bhbj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2lu
YWxCb2R5Ij48L3NwYW4+PC9hPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5h
bEJvZHkiPiZndDsNCiB3cm90ZTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8YmxvY2txdW90ZSBz
dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5n
OjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdp
bmFsQm9keSI+PHNwYW4gY2xhc3M9ImdtYWlsLSI+T24gTW9uLCBBcHIgMzAsIDIwMTggYXQgMDk6
NTU6MzFQTSAmIzQzOzAwMDAsIFByYXZlZW4gQmFsYXN1YnJhbWFuaWFuIHdyb3RlOjwvc3Bhbj48
L3NwYW4+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+PGJyPg0K
PHNwYW4gY2xhc3M9ImdtYWlsLSI+Jmd0OyBJIGRpc2FncmVlIHRoYXQgd2UgbmVlZCBhbnkgbW9y
ZSBkYXRhIGZvciBub3QgZG9pbmcgUE5FIGluIHRoZSBkYXRhY2VudGVyLiBXaHkgd291bGQgd2Ug
YWRkIGFuIGV4dHJhIGVuY3J5cHQtZGVjcnlwdCBzdGVwIGZvciBubyBvYnZpb3VzIGJlbmVmaXQ/
IFRoZSBjb3N0IG9mIHRoaXMgb3BlcmF0aW9uIHdpbGwga2VlcCBtYWduaWZ5aW5nIGFzIFVEUCBw
ZXJmb3JtYW5jZSBpbXByb3Zlcy4gV2UgaGF2ZSBzZXZlcmFsDQogb3B0aW1pemF0aW9ucyBwbGFu
bmVkIGZvciBVRFAsIGJ1dCBzaG9ydCBvZiBoYXJkd2FyZSBvZmZsb2FkLCBub25lIGZvciBjcnlw
dG8g4oCTIHRoaXMgaXMgYW4gaW1wb3J0YW50IHRyZW5kIHRvIGFjY291bnQgZm9yIHBlcmZvcm1h
bmNlIHdpc2UuIEZvciBzaG9ydCBwYWNrZXRzIGxpa2UgQUNLcyBhbiBleHRyYSBlbmNyeXB0IGRl
Y3J5cHQgc3RlcCBjYW4gYmVjb21lIGEgbGFyZ2UgZnJhY3Rpb24gb2YgQ1BVIGNvc3Qgb3ZlciB0
aW1lLjwvc3Bhbj48YnI+DQo8YnI+DQpUaGVyZSBpcyBiZW5lZml0IGluIHVuaWZvcm1pdHkgYW5k
IHNpbXBsaWNpdHkgb2YgaW1wbGVtZW50YXRpb247IEkgY29uY2VkZSB0aGF0PGJyPg0KdGhlIGNs
YWltZWQgcG90ZW50aWFsIGJlbmVmaXRzIGFib3V0IHRoZSBtaWRkbGVib3ggZWNvc3lzdGVtIGFy
ZSBzcGVjdWxhdGl2ZSw8YnI+DQpidXQgdGhlIHNpbXBsaWNpdHkgc2VlbXMgY2xlYXIgdG8gbWUu
PGJyPg0KPGJyPg0KV2l0aCByZXNwZWN0IHRvIHRoZSBjb3N0IG9mIHRoZSBjcnlwdG8sIHllcyB3
ZSBoYXZlIHNvbWUgbnVtYmVycywgYnV0IEFGQUlDVCB3ZTxicj4NCmRvbid0IGhhdmUgYSBncmVh
dCB2aWV3IGZvciBob3cgdGhleSB3aWxsIGZpdCBpbnRvIHRoZSBicm9hZGVyIHBpY3R1cmUgYXM8
YnI+DQppbXBsZW1lbnRhdGlvbnMgbWF0dXJlLCBzbyB0byBzb21lIGV4dGVudCB0aGUgZXN0aW1h
dGUgb2YgdGhlIG1hZ25pdHVkZSBvZjxicj4NCmdyb3dpbmcgY29zdCBvZiBjcnlwdG8gaXMgYWxz
byBhIHNwZWN1bGF0aXZlIHBvc2l0aW9uLiZuYnNwOyAoQWxzbywgd2hvIGlzIHRoZSAmcXVvdDt3
ZSZxdW90Ozxicj4NCnRoYXQgaGFzIHNldmVyYWwgb3B0aW1pemF0aW9ucyBwbGFubmVkPyk8YnI+
DQo8YnI+DQpJbiBvdGhlciB3b3JkcywgaG93IGRvIHdlIGtub3cgdGhpcyBpcyBub3QgcHJlbWF0
dXJlIG9wdGltaXphdGlvbj8mbmJzcDsgU2hvdWxkbid0PGJyPg0Kd2Ugd2FpdCB1bnRpbCB3ZSBo
YXZlIGFjdHVhbCBwZXJmb3JtYW5jZSBudW1iZXJzIGJlZm9yZSBkb2luZyBsb3RzIG9mPGJyPg0K
b3B0aW1pemF0aW9uPyZuYnNwOyA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpf
TWFpbE9yaWdpbmFsQm9keSI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFp
bE9yaWdpbmFsQm9keSI+SSBjYW4ndCBzcGVhayB0byB3aGV0aGVyIHRoaXMgb3B0aW1pemF0aW9u
IGlzIHByZW1hdHVyZSwgYnV0IEkgZG8gc3VzcGVjdCB0aGF0IGlmIG1vcmUgcGVvcGxlIHdlcmUg
bG9va2luZyBhdCBtb3JlIGFjdHVhbCBwZXJmb3JtYW5jZSBudW1iZXJzLCB0aGlzIGNvbnZlcnNh
dGlvbiBtaWdodCBjb252ZXJnZSBtb3JlIHF1aWNrbHkgLi4uJm5ic3A7PG86cD48L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6
c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0
OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+SSB3YXMgdW5kZXIgdGhlIGltcHJl
c3Npb24gdGhhdCBRVUlDIHZlcnNpb25zIHdlcmUgZ29pbmcgdG8gYmU8YnI+DQpsaWdodHdlaWdo
dCwgc28gcHV0dGluZyBvdXQgdjEgd2l0aCBtYW5kYXRvcnkgUE5FIHdvdWxkIG5vdCBwcmVjbHVk
ZSBxdWlja2x5PGJyPg0KZm9sbG93aW5nIHdpdGggYSBWMyB0aGF0IGFkYXB0cyB0byBhbnkgZGlz
Y292ZXJlZCBwZXJmb3JtYW5jZSBjb25jZXJucywgd2hldGhlcjxicj4NCmZvciBkYXRhY2VudGVy
IHVzYWdlIG9yIG90aGVyd2lzZS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Jsb2NrcXVvdGU+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpf
TWFpbE9yaWdpbmFsQm9keSI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFp
bE9yaWdpbmFsQm9keSI+WWVhaCwgYWJvdXQgdGhhdCAuLi4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
bXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNv
LWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij5JJ3ZlIGJlZW4gYXNraW5nIGluIGEgZmV3IHBs
YWNlcyAtIG1vc3QgcmVjZW50bHksIGF0Jm5ic3A7PC9zcGFuPjxhIGhyZWY9Imh0dHBzOi8vdXJs
ZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRwcy0zQV9fZGF0YXRyYWNrZXIuaWV0
Zi5vcmdfbWVldGluZ18xMDFfbWF0ZXJpYWxzX21pbnV0ZXMtMkQxMDEtMkRxdWljLTJEMDAuaHRt
bCZhbXA7ZD1Ed01GYVEmYW1wO2M9NVZEMFJUdE5sVGgzeWNkNDFiM01VdyZhbXA7cj1DMHNVby1M
Rk5CYVlmeW9hQ3NmNlRBJmFtcDttPTdka01iMllWWEgwNzgwdkl5b1J3Uk5yaVpVd2hVRzRuNjFB
YkVuVTdQVGcmYW1wO3M9eTVsSVUxUS15Z0JvT2FHczRFSW5DaGkycmQtWm5aa3JDcDgyZzRkcURh
VSZhbXA7ZT0iPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPmh0
dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvbWVldGluZy8xMDEvbWF0ZXJpYWxzL21pbnV0ZXMt
MTAxLXF1aWMtMDAuaHRtbDwvc3Bhbj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3Jp
Z2luYWxCb2R5Ij48L3NwYW4+PC9hPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmln
aW5hbEJvZHkiPg0KIC0gYWJvdXQgdmVyc2lvbiBhcHBlYXJhbmNlIHJhdGVzLCBhbmQgSSBoYXZl
bid0IGhlYXJkIGFuc3dlcnMgdGhhdCBzb3VuZGVkIGxpa2UgdGhlIHdvcmtpbmcgZ3JvdXAgaGFk
IHN0cm9uZyBhZ3JlZW1lbnQgdGhhdCB2ZXJzaW9ucyB3ZXJlIGdvaW5nIHRvIHJvbGwgb3V0IHBy
ZXR0eSBxdWlja2x5LiBGb3IgZXhhbXBsZSwgZnJvbSB0aGF0IGNvbnZlcnNhdGlvbiwgSSBnb3Qm
bmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8YmxvY2tx
dW90ZSBzdHlsZT0ibWFyZ2luLWxlZnQ6MzAuMHB0O21hcmdpbi1yaWdodDowaW4iPg0KPGRpdj4N
CjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJt
c28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPlNwZW5jZXIgKGFzIEFEKToNCjxpPltkZWxl
dGVkIGZpcnN0IHRocmVlIHBvaW50cywgdG8gZ2V0IHRvXSA8L2k+NC4gKGFzIFNwZW5jZXIpIGRv
bid0IGhhdmUgYSBnb29kIGZlZWxpbmcgYWJvdXQgdmVyc2lvbiBuZWdvdGlhdGluZyBhbmQgaG93
IG11Y2ggd2UgbWlnaHQgcm9sbCB0aGVtLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01h
aWxPcmlnaW5hbEJvZHkiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxP
cmlnaW5hbEJvZHkiPm1ub3Q6IG5vdCBnb2luZyB0byB3YWl0IDUgeWVhcnMgZm9yIHYyLjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9j
a3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9v
a21hcms6X01haWxPcmlnaW5hbEJvZHkiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFp
bE9yaWdpbmFsQm9keSI+U28sIHRoZSBjaGFpcnMgY2FuIGNvcnJlY3QgbWUgKGFuZCBzaG91bGQs
IGFuZCB0aGV5IGhhdmUgYmVmb3JlIG9uIG90aGVyIHRvcGljcyksIGJ1dCBJIHRoaW5rIEkndmUg
aGVhcmQgYSBsb3Qgb2YgJnF1b3Q7d2UgZG9uJ3QgaGF2ZSB0byBnZXQgZXZlcnl0aGluZyBwZXJm
ZWN0IGluIFFVSUN2MSwgYmVjYXVzZSB0aGVyZSB3aWxsIGJlIG90aGVyDQogdmVyc2lvbnMmcXVv
dDssIGFuZCBub3QgYSBsb3Qgb2YgJnF1b3Q7YW5kIHRoZSBvdGhlciB2ZXJzaW9ucyB3aWxsIGFw
cGVhciBwcmV0dHkgcXVpY2tseSZxdW90Oy4mbmJzcDsNCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9N
YWlsT3JpZ2luYWxCb2R5Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWls
T3JpZ2luYWxCb2R5Ij5JIGRvbid0IGtub3cgd2hhdCBhbGwgdGhlIHBhcnRpY2lwYW50cyBhcmUg
dGhpbmtpbmcsIGJ1dCB0aGF0J3Mgd2hhdCB0aGUgcGVvcGxlIHdobyBhcmUgdGFsa2luZyBoYXZl
IGJlZW4gc2F5aW5nIHRvIG1lLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij5J
TU8sIG9mIGNvdXJzZS4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3Jp
Z2luYWxCb2R5Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2lu
YWxCb2R5Ij5TcGVuY2VyLCBhcyBpbmRpdmlkdWFsJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9w
Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+
PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6
c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0
OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1h
cmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2lu
YWxCb2R5Ij4tQmVuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3Jp
Z2luYWxCb2R5Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_02563F0079ED41169318764F3DB94FA6fbcom_--


From nobody Tue May  1 16:23:09 2018
Return-Path: <prvs=86592f1e95=fenix@fb.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81D8F126DFB for <quic@ietfa.amsl.com>; Tue,  1 May 2018 16:23:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=FHS6bSTO; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=UYpxShu9
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 7WNdETwz3_Eq for <quic@ietfa.amsl.com>; Tue,  1 May 2018 16:23:04 -0700 (PDT)
Received: from mx0a-00082601.pphosted.com (mx0a-00082601.pphosted.com [67.231.145.42]) (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 B2B7B127078 for <quic@ietf.org>; Tue,  1 May 2018 16:23:04 -0700 (PDT)
Received: from pps.filterd (m0109334.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w41NHqAe029910; Tue, 1 May 2018 16:22:30 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : content-type : mime-version; s=facebook; bh=ixBUHQH54IUOASaGCJpUUcnk2PHWRBwjlQ4aveBD2+c=; b=FHS6bSTO0v/3hOTGFAk5YhbIul26uTtulM+a5nQmFroQcXnSJ0UV72mvs3wr2UinOAGp TjSXhsrhskQ8663DyvepaluO0mUbkpXpBGX+o7Qpzsf8snhS+xf/ZEfAM/6GWow8xhRQ JA5l6kyLg+F6vRTUUzbQKzuRtt4IrFmiF7Q= 
Received: from maileast.thefacebook.com ([199.201.65.23]) by mx0a-00082601.pphosted.com with ESMTP id 2hpvw4ruf7-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 01 May 2018 16:22:30 -0700
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (192.168.183.28) by o365-in.thefacebook.com (192.168.177.29) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 1 May 2018 19:22:28 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version;  bh=ixBUHQH54IUOASaGCJpUUcnk2PHWRBwjlQ4aveBD2+c=; b=UYpxShu9nl82sfHcJ8Tvs6ewXmw+T0LeQrUCvDPEO/GVnu3n0fUpQ7CzlKFhTPbgtn9jF8KCPHAjzkhkIrFyAvc5UIfDWfiPZHbHp9zMLSD+z2P5ZYWFHH3o7erGzuG3VMEXhsIqGs9R1xR/lDC8mzWo1HxUidSLcqsZRWOat4c=
Received: from BY2PR15MB0775.namprd15.prod.outlook.com (10.164.171.11) by BY2PR15MB0373.namprd15.prod.outlook.com (10.163.109.158) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.715.24; Tue, 1 May 2018 23:22:26 +0000
Received: from BY2PR15MB0775.namprd15.prod.outlook.com ([fe80::6c4c:bbf3:ec3b:d45e]) by BY2PR15MB0775.namprd15.prod.outlook.com ([fe80::6c4c:bbf3:ec3b:d45e%14]) with mapi id 15.20.0715.024; Tue, 1 May 2018 23:22:26 +0000
From: Roberto Peon <fenix@fb.com>
To: Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>, Ted Hardie <ted.ietf@gmail.com>
CC: "Salz, Rich" <rsalz@akamai.com>, Benjamin Kaduk <bkaduk@akamai.com>, "IETF QUIC WG" <quic@ietf.org>
Subject: Re: [Potential Spoof] Re: Getting to consensus on packet number encryption
Thread-Topic: [Potential Spoof] Re: Getting to consensus on packet number encryption
Thread-Index: AQHT4aNDwsND+KyhPEGdsYUFiGhpMg==
Date: Tue, 1 May 2018 23:22:26 +0000
Message-ID: <01AE46C6-682C-4A21-84CD-1D8DAD6F49D9@fb.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.c.0.180410
x-originating-ip: [2620:10d:c090:200::6:ddb8]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BY2PR15MB0373; 7:kFfGahr4wPaMLx7KodNfmZz9u4yk/o9LAdqlcxmxJ4cka6gY8Ko910PtMumm/uDdPgCid9pO0FntAmGIwEC1Z2J0zLfVPUkV9VLwsMNap4+TJtqCBOze8jG4qdDsv6nBzI6kg1PdftIkxwtfpgV2iCh2lbulg0JIKg8GOV0qK8rDDRNd3bnvJf99U4Qo2VBuZ8ymyFL00RhJXbBch8dJy6lxGA3QfPlI2BrQF54w00Fl5udKEV2zXeLOELylHuB5; 20:D2n4Ew9CE3icH3qdXnOqvtxeX2TgneuUHOIhK3q5cBwr3yryztlEYA5CrB+8sfLj09yf5DEdNxORPCnM/2yoEgR1P87PeWAqNfe7UH9MU+iExFZhDRuEGArLtEV0YbgsyX3RSlRdsRXRjls5hdjwpqY07ukv3TiBn3LWrPQ7AUA=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BY2PR15MB0373; 
x-ms-traffictypediagnostic: BY2PR15MB0373:
x-microsoft-antispam-prvs: <BY2PR15MB0373E36267D564DDE9E259D8CD810@BY2PR15MB0373.namprd15.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(10436049006162)(89211679590171)(189930954265078)(85827821059158)(67672495146484)(100405760836317)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(10201501046)(3002001)(93006095)(93001095)(3231254)(11241501184)(944501410)(52105095)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123562045)(20161123564045)(20161123558120)(6072148)(201708071742011); SRVR:BY2PR15MB0373; BCL:0; PCL:0; RULEID:; SRVR:BY2PR15MB0373; 
x-forefront-prvs: 06592CCE58
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(376002)(346002)(39380400002)(39860400002)(366004)(189003)(199004)(102836004)(45080400002)(8936002)(6506007)(14454004)(86362001)(3280700002)(6246003)(39060400002)(478600001)(7736002)(236005)(6512007)(5250100002)(6306002)(4326008)(2900100001)(316002)(97736004)(99286004)(68736007)(59450400001)(54896002)(53546011)(53936002)(33656002)(606006)(6116002)(2906002)(25786009)(81166006)(5660300001)(58126008)(83716003)(81156014)(105586002)(110136005)(82746002)(54906003)(486006)(8676002)(36756003)(3660700001)(229853002)(186003)(2616005)(106356001)(6486002)(6436002)(46003)(476003)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR15MB0373; H:BY2PR15MB0775.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: fb.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: NtxvJdoD5XiqfmGJxh1FlIIeWCVxJ7ECPB6h4lLjhPK2m6f4POurc/ByIbecTvquHaw44KmuT0gubvh9i4Gcq7eGdPVZwv7VB2s4IVMfRSnDn87pgMY59+gHraessqSiYO4/VY691bKEgdHvF7FjSyVybN2GWpicxv2DoeWL+KCXMhnqt1E6qiOZ2SmpxTuB
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_01AE46C6682C4A2184CD1D8DAD6F49D9fbcom_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: fbb85b17-895b-431a-00cd-08d5afba669a
X-MS-Exchange-CrossTenant-Network-Message-Id: fbb85b17-895b-431a-00cd-08d5afba669a
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 May 2018 23:22:26.1064 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR15MB0373
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-01_13:, , signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2HXOUGwHQgjDC1h8-MvchaBhSyQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 01 May 2018 23:23:07 -0000

--_000_01AE46C6682C4A2184CD1D8DAD6F49D9fbcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SeKAmWQgc3VnZ2VzdCB3ZSBzdGFydCB3b3JraW5nIG9uIGl0IG5vdy4NClRoaXMgaXMgb25seSBw
YXJ0bHkgYSBqb2tlIOKYug0KLT1SDQoNCkZyb206IFFVSUMgPHF1aWMtYm91bmNlc0BpZXRmLm9y
Zz4gb24gYmVoYWxmIG9mIFJvYmVydG8gUGVvbiA8ZmVuaXhAZmIuY29tPg0KRGF0ZTogVHVlc2Rh
eSwgTWF5IDEsIDIwMTggYXQgNDoyMSBQTQ0KVG86IFByYXZlZW4gQmFsYXN1YnJhbWFuaWFuIDxw
cmF2Yj00MG1pY3Jvc29mdC5jb21AZG1hcmMuaWV0Zi5vcmc+LCBUZWQgSGFyZGllIDx0ZWQuaWV0
ZkBnbWFpbC5jb20+DQpDYzogIlNhbHosIFJpY2giIDxyc2FsekBha2FtYWkuY29tPiwgQmVuamFt
aW4gS2FkdWsgPGJrYWR1a0Bha2FtYWkuY29tPiwgSUVURiBRVUlDIFdHIDxxdWljQGlldGYub3Jn
Pg0KU3ViamVjdDogW1BvdGVudGlhbCBTcG9vZl0gUmU6IEdldHRpbmcgdG8gY29uc2Vuc3VzIG9u
IHBhY2tldCBudW1iZXIgZW5jcnlwdGlvbg0KDQpZdXAuIEkga25vdy4NClByaXNtIHdhcyBleWUt
b3BlbmluZyBwYXJ0aWFsbHkgYmVjYXVzZSBvZiB0aGUgZmFjdCB0aGF0IHRoZSBwYWNrZXRzIHdl
cmUgbm90IGdvaW5nIGFjcm9zcyB0aGUgaW50ZXJuZXQsIGJ1dCByYXRoZXIgd2l0aGluIGEgc2Vj
dXJlIG5ldHdvcmsuDQoNCkkgYmVsaWV2ZSB0aGF0IG9zc2lmaWNhdGlvbiBhbG9uZSBpcyBhIGdv
b2QgZW5vdWdoIHJlYXNvbiB0byBkbyBQTkUuDQpUaGUgY2hlcnJ5IGZvciBtZSBpcyB0aGF0IGl0
LCBhbG9uZyB3aXRoIG90aGVyIGFjdGlvbnMvbWl0aWdhdGlvbnMsIG1ha2VzIGxpbmthYmlsaXR5
IG1vcmUgZGlmZmljdWx0IGZvciBtYWxpY2lvdXMgYWN0b3JzLg0KQ1JJTUUgYW5kIHJlbGF0ZWQg
d2FzIGV5ZS1vcGVuaW5nIGJlY2F1c2UgaXQgZXhwb3NlZCB0aGUgcG93ZXIgb2YgdGhlIG9ic2Vy
dmFibGUgc2lkZS1jaGFubmVsLg0KDQotPVINCg0KRnJvbTogUVVJQyA8cXVpYy1ib3VuY2VzQGll
dGYub3JnPiBvbiBiZWhhbGYgb2YgUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gPHByYXZiPTQwbWlj
cm9zb2Z0LmNvbUBkbWFyYy5pZXRmLm9yZz4NCkRhdGU6IFR1ZXNkYXksIE1heSAxLCAyMDE4IGF0
IDk6MzUgQU0NClRvOiBUZWQgSGFyZGllIDx0ZWQuaWV0ZkBnbWFpbC5jb20+LCBSb2JlcnRvIFBl
b24gPGZlbml4QGZiLmNvbT4NCkNjOiAiU2FseiwgUmljaCIgPHJzYWx6QGFrYW1haS5jb20+LCBC
ZW5qYW1pbiBLYWR1ayA8YmthZHVrQGFrYW1haS5jb20+LCBJRVRGIFFVSUMgV0cgPHF1aWNAaWV0
Zi5vcmc+DQpTdWJqZWN0OiBSRTogR2V0dGluZyB0byBjb25zZW5zdXMgb24gcGFja2V0IG51bWJl
ciBlbmNyeXB0aW9uDQoNClRoaXMgaXMgbm90IGFib3V0IHB1dHRpbmcgcGxhaW50ZXh0IGRhdGEg
b24gdGhlIG5ldHdvcmssIHRoaXMgaXMgYWJvdXQgbm90IGFkZGluZyBQTkUgd2hpY2ggaXMgaW50
ZW5kZWQgZm9yIHByZXZlbnRpbmcgb3NzaWZpY2F0aW9uLiBTbyBJIGRvbuKAmXQgdW5kZXJzdGFu
ZCB3aGF0IHRoZSB0cnVzdCBpc3N1ZSBiZWluZyByZWZlcnJlZCB0byBpcyBpbiBjYXNlIG9mIHRo
ZSByYXJlIG1pc2NvbmZpZy4NCg0KV2l0aGluIGEgREMgc2V2ZXJhbCB0aGluZ3MgYXJlIGRpZmZl
cmVudCDigJMgdGhlIGRlcGxveW1lbnQgbWF5IG5lZWQgZGlmZmVyZW50IGNvbmdlc3Rpb24gY29u
dHJvbCBsaWtlIERDVENQLCBkaWZmZXJlbnQgc2V0dGluZ3MgZm9yIHZhcmlvdXMgdHJhbnNwb3J0
IHBhcmFtZXRlcnMgKGxpa2UgbWlucnRvIGFuZCBtYXggQUNLIGRlbGF5KSwgbGFyZ2VyIGZsb3cg
Y29udHJvbCB3aW5kb3cgZXRjLiBUaGlzIGlzIHRydWUgZm9yIFRDUCB0b2RheS4gVGhlIG91dCBv
ZiBib3ggZGVmYXVsdCB1c2VzIHRoZSBoYW5kc2hha2UgUlRUIHRvIG1ha2UgYSBkZXRlcm1pbmF0
aW9uIG9mIHdoYXTigJlzIGludHJhLURDIGJ1dCB0aGVyZSBpcyByaWNoIGNvbmZpZ3VyYXRpb24g
dG8gb3ZlcnJpZGUgdGhlIGRlZmF1bHQgYW5kIHNldCBpdCBiYXNlZCBvbiA0LXR1cGxlIGZpbHRl
cnMuDQoNCkFuZCB0aGVyZSB3b3JrbG9hZHMgbGlrZSBjbG91ZCBzdG9yYWdlIGFuZCBsaXZlIG1p
Z3JhdGlvbiB0aGF0IGFyZSBieSB2aXJ0dWUgb2YgZGVwbG95bWVudCBpbnRyYS1EQy4gVGhlc2Ug
Y2Fubm90IGJlIGxvYWQgc2hpZnRlZCBhcyB0aGV5IHVzZSBwcml2YXRlIElQIGFkZHJlc3Mgc3Bh
Y2UuDQoNCkZyb206IFRlZCBIYXJkaWUgW21haWx0bzp0ZWQuaWV0ZkBnbWFpbC5jb21dDQpTZW50
OiBUdWVzZGF5LCBNYXkgMSwgMjAxOCA4OjU1IEFNDQpUbzogUm9iZXJ0byBQZW9uIDxmZW5peEBm
Yi5jb20+DQpDYzogU2FseiwgUmljaCA8cnNhbHpAYWthbWFpLmNvbT47IEJlbmphbWluIEthZHVr
IDxia2FkdWtAYWthbWFpLmNvbT47IFByYXZlZW4gQmFsYXN1YnJhbWFuaWFuIDxwcmF2YkBtaWNy
b3NvZnQuY29tPjsgSUVURiBRVUlDIFdHIDxxdWljQGlldGYub3JnPg0KU3ViamVjdDogUmU6IEdl
dHRpbmcgdG8gY29uc2Vuc3VzIG9uIHBhY2tldCBudW1iZXIgZW5jcnlwdGlvbg0KDQpPbiBUdWUs
IE1heSAxLCAyMDE4IGF0IDg6MTMgQU0sIFJvYmVydG8gUGVvbiA8ZmVuaXhAZmIuY29tPG1haWx0
bzpmZW5peEBmYi5jb20+PiB3cm90ZToNCkFsc28sIFByaXNtLg0KDQotPVINCg0KDQoNClRoYXQn
cyBhIGxpdHRsZSBtb3JlIHN1Y2NpbmN0IHRoYW4gSSB3b3VsZCBiZSwgYnV0IHllcy4gIEhvdyBk
b2VzIGFuIGFwcGxpY2F0aW9uIGtub3cgdGhhdCB0aGUgZmxvdyBpdCBpcyBpbml0aWF0aW5nIHdp
bGwgdHJhdmVyc2UgYSB0b3BvbG9neSB0aGF0IGlzIGRlZW1lZCB0byBiZSB3aXRoaW4gYSBjb250
cm9sbGVkIGVudmlyb25tZW50PyAgWW91IGNhbiBzYXkgImNvbmZpZ3VyYXRpb24iIGJ1dCBJIGZl
YXIgaXQgd2lsbCB0dXJuIHVwIG9uIGEgcG9zdC1pdCAgPGh0dHBzOi8vdXJsZGVmZW5zZS5wcm9v
ZnBvaW50LmNvbS92Mi91cmw/dT1odHRwcy0zQV9fbmEwMS5zYWZlbGlua3MucHJvdGVjdGlvbi5v
dXRsb29rLmNvbV8tM0Z1cmwtM0RodHRwcy0yNTNBLTI1MkYtMjUyRmkua2luamEtMkRpbWcuY29t
LTI1MkZnYXdrZXItMkRtZWRpYS0yNTJGaW1hZ2UtMjUyRnVwbG9hZC0yNTJGcy0yRC0yREVkdTZM
UHU5LTJELTJELTI1MkZjLTVGc2NhbGUtMjUyQ2YtNUZhdXRvLTI1MkNmbC01RnByb2dyZXNzaXZl
LTI1MkNxLTVGODAtMjUyQ3ctNUY4MDAtMjUyRjE5NHRoYnR5ZW5jczBqcGcuanBnLTI2ZGF0YS0z
RDAyLTI1N0MwMS0yNTdDcHJhdmItMjU0MG1pY3Jvc29mdC5jb20tMjU3QzRkYTQ0ZThhYzFkZjQ3
MDhhZDg4MDhkNWFmN2JmY2E4LTI1N0M3MmY5ODhiZjg2ZjE0MWFmOTFhYjJkN2NkMDExZGI0Ny0y
NTdDMS0yNTdDMS0yNTdDNjM2NjA3ODY5NDExMjU4OTc2LTI2c2RhdGEtM0RQcm9sU0hrYkYyU2dN
SDNxZFFOLTI1MkJaRm9rWHZzRUJmLTI1MkYzbzlNYVVuaWwwZzgtMjUzRC0yNnJlc2VydmVkLTNE
MCZkPUR3TUdhUSZjPTVWRDBSVHRObFRoM3ljZDQxYjNNVXcmcj1DMHNVby1MRk5CYVlmeW9hQ3Nm
NlRBJm09VHVWZnp5cG8tQ1pMbzUyMmxnTVJyTHBLeGNGYUh2VzlrZE5TSTU3bFhUMCZzPUJ5MmRf
dG83WHpMRWdBTDNPcjljWmMyQXlreWUtUFpFZW5GUUR2aUFVbHcmZT0+IGlmIHlvdSBkby4gIExv
YWRzIHNoaWZ0LCByZXNvdXJjZXMgbW92ZSwgYW5kIHN1ZGRlbmx5IHlvdSBmaW5kIHRoYXQgaG9z
dCB3aGljaCB1c2VkIHRvIGJlIGluIHRoZSBzYW1lIHJhY2ssIGJlaW5nIGRvd24sIGhhcyBsb2Fk
LXNoaWZ0ZWQgdG8gdGhlIG5leHQgaW5zdGFuY2UsICBpbiBhIGRhdGFjZW50ZXIgNTAwIG1pbGVz
IGF3YXkgYWNyb3NzIGEgdmVyeSBkaWZmZXJlbnQgbmV0d29yay4NCg0KTWFueSBtb2Rlcm4gZGVw
bG95bWVudHMgYXJlIGFsc28gaW4gc29tZW9uZSBlbHNlJ3MgZGF0YSBjZW50ZXIsIHNvIHNheWlu
ZyAiRGF0YSBjZW50ZXIgbmV0d29ya3MiIGRvZXNuJ3Qgc2F5IG11Y2ggYWJvdXQgd2h5IHlvdSdy
ZSB0cnVzdGluZyB0aGUgbmV0d29yayBpbnNpZGUuDQpUZWQNCg0KU2VudCB2aWEgdGhlIFNhbXN1
bmcgR2FsYXh5IFM3LCBhbiBBVCZUIDRHIExURSBzbWFydHBob25lDQoNCg0KLS0tLS0tLS0gT3Jp
Z2luYWwgbWVzc2FnZSAtLS0tLS0tLQ0KRnJvbTogIlNhbHosIFJpY2giIDxyc2Fsej00MGFrYW1h
aS5jb21AZG1hcmMuaWV0Zi5vcmc8bWFpbHRvOjQwYWthbWFpLmNvbUBkbWFyYy5pZXRmLm9yZz4+
DQpEYXRlOiA1LzEvMTggNToyNSBBTSAoR01ULTA4OjAwKQ0KVG86IEJlbmphbWluIEthZHVrIDxi
a2FkdWs9NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnPG1haWx0bzo0MGFrYW1haS5jb21AZG1h
cmMuaWV0Zi5vcmc+PiwgUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gPHByYXZiPTQwbWljcm9zb2Z0
LmNvbUBkbWFyYy5pZXRmLm9yZzxtYWlsdG86NDBtaWNyb3NvZnQuY29tQGRtYXJjLmlldGYub3Jn
Pj4NCkNjOiBJRVRGIFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc8bWFpbHRvOnF1aWNAaWV0Zi5vcmc+
Pg0KU3ViamVjdDogUmU6IEdldHRpbmcgdG8gY29uc2Vuc3VzIG9uIHBhY2tldCBudW1iZXIgZW5j
cnlwdGlvbg0KDQogICAgPiBJIGRpc2FncmVlIHRoYXQgd2UgbmVlZCBhbnkgbW9yZSBkYXRhIGZv
ciBub3QgZG9pbmcgUE5FIGluIHRoZSBkYXRhY2VudGVyLiBXaHkgd291bGQgd2UgYWRkIGFuIGV4
dHJhIGVuY3J5cHQtZGVjcnlwdCBzdGVwIGZvciBubyBvYnZpb3VzIGJlbmVmaXQ/DQoNCkkgYW0g
Y29uY2VybmVkIHRoYXQgcGVvcGxlIHdpbGwgbWlzLWludGVycHJldCB0aGUgbWVhbmluZyBvZiBh
IGRhdGFjZW50ZXIsIGFuZCB0aGluayB0aGF0IGEgYnVuY2ggb2Ygc2VydmVycywgb3IgZXZlbiBh
IHJhY2ssIGluIGFuIG9wZW4gY29sbyBzcGFjZSBpcyBhICJkYXRhY2VudGVyLiIgIENvbXB1dGVy
cyBrZWVwIGdldHRpbmcgZmFzdGVyLg0KDQo=

--_000_01AE46C6682C4A2184CD1D8DAD6F49D9fbcom_
Content-Type: text/html; charset="utf-8"
Content-ID: <8EFA796418449148929E09B0CDF70910@namprd15.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJBcHBsZSBD
b2xvciBFbW9qaSI7DQoJcGFub3NlLTE6MCAwIDAgMCAwIDAgMCAwIDAgMDt9DQovKiBTdHlsZSBE
ZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0K
CXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29I
eXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1k
ZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93
ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29y
YXRpb246dW5kZXJsaW5lO30NCnAubXNvbm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25v
cm1hbDANCgl7bXNvLXN0eWxlLW5hbWU6bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDph
dXRvOw0KCW1hcmdpbi1yaWdodDowaW47DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJ
bWFyZ2luLWxlZnQ6MGluOw0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGli
cmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVy
c29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93
dGV4dDt9DQpzcGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCnNw
YW4uRW1haWxTdHlsZTIwDQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0No
cERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBw
dDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEu
MGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2Vj
dGlvbjE7fQ0KLS0+PC9zdHlsZT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJi
bHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5J4oCZZCBzdWdnZXN0IHdlIHN0YXJ0IHdvcmtpbmcgb24gaXQgbm93Ljxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhpcyBpcyBvbmx5IHBhcnRseSBh
IGpva2UgPHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FwcGxlIENvbG9yIEVtb2ppJnF1
b3Q7Ij4NCuKYujwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi09
UjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNCNUM0REYgMS4w
cHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtjb2xvcjpibGFjayI+RnJvbTogPC9zcGFuPjwv
Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtjb2xvcjpibGFjayI+UVVJQyAmbHQ7cXVp
Yy1ib3VuY2VzQGlldGYub3JnJmd0OyBvbiBiZWhhbGYgb2YgUm9iZXJ0byBQZW9uICZsdDtmZW5p
eEBmYi5jb20mZ3Q7PGJyPg0KPGI+RGF0ZTogPC9iPlR1ZXNkYXksIE1heSAxLCAyMDE4IGF0IDQ6
MjEgUE08YnI+DQo8Yj5UbzogPC9iPlByYXZlZW4gQmFsYXN1YnJhbWFuaWFuICZsdDtwcmF2Yj00
MG1pY3Jvc29mdC5jb21AZG1hcmMuaWV0Zi5vcmcmZ3Q7LCBUZWQgSGFyZGllICZsdDt0ZWQuaWV0
ZkBnbWFpbC5jb20mZ3Q7PGJyPg0KPGI+Q2M6IDwvYj4mcXVvdDtTYWx6LCBSaWNoJnF1b3Q7ICZs
dDtyc2FsekBha2FtYWkuY29tJmd0OywgQmVuamFtaW4gS2FkdWsgJmx0O2JrYWR1a0Bha2FtYWku
Y29tJmd0OywgSUVURiBRVUlDIFdHICZsdDtxdWljQGlldGYub3JnJmd0Ozxicj4NCjxiPlN1Ympl
Y3Q6IDwvYj5bUG90ZW50aWFsIFNwb29mXSBSZTogR2V0dGluZyB0byBjb25zZW5zdXMgb24gcGFj
a2V0IG51bWJlciBlbmNyeXB0aW9uPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPll1cC4gSSBrbm93LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+UHJpc20gd2FzIGV5ZS1vcGVuaW5nIHBhcnRpYWxseSBiZWNhdXNlIG9mIHRo
ZSBmYWN0IHRoYXQgdGhlIHBhY2tldHMgd2VyZSBub3QgZ29pbmcgYWNyb3NzIHRoZSBpbnRlcm5l
dCwgYnV0IHJhdGhlciB3aXRoaW4gYSBzZWN1cmUgbmV0d29yay48bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+SSBiZWxpZXZlIHRoYXQgb3NzaWZpY2F0aW9uIGFsb25lIGlzIGEgZ29vZCBlbm91Z2gg
cmVhc29uIHRvIGRvIFBORS48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRo
ZSBjaGVycnkgZm9yIG1lIGlzIHRoYXQgaXQsIGFsb25nIHdpdGggb3RoZXIgYWN0aW9ucy9taXRp
Z2F0aW9ucywgbWFrZXMgbGlua2FiaWxpdHkgbW9yZSBkaWZmaWN1bHQgZm9yIG1hbGljaW91cyBh
Y3RvcnMuPGJyPg0KQ1JJTUUgYW5kIHJlbGF0ZWQgd2FzIGV5ZS1vcGVuaW5nIGJlY2F1c2UgaXQg
ZXhwb3NlZCB0aGUgcG93ZXIgb2YgdGhlIG9ic2VydmFibGUgc2lkZS1jaGFubmVsLg0KPG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YnI+DQotPVI8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPGRpdiBzdHlsZT0i
Ym9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQg
MGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMi4wcHQ7Y29sb3I6YmxhY2siPkZyb206IDwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMi4wcHQ7Y29sb3I6YmxhY2siPlFVSUMgJmx0O3F1aWMtYm91bmNlc0BpZXRmLm9y
ZyZndDsgb24gYmVoYWxmIG9mIFByYXZlZW4gQmFsYXN1YnJhbWFuaWFuICZsdDtwcmF2Yj00MG1p
Y3Jvc29mdC5jb21AZG1hcmMuaWV0Zi5vcmcmZ3Q7PGJyPg0KPGI+RGF0ZTogPC9iPlR1ZXNkYXks
IE1heSAxLCAyMDE4IGF0IDk6MzUgQU08YnI+DQo8Yj5UbzogPC9iPlRlZCBIYXJkaWUgJmx0O3Rl
ZC5pZXRmQGdtYWlsLmNvbSZndDssIFJvYmVydG8gUGVvbiAmbHQ7ZmVuaXhAZmIuY29tJmd0Ozxi
cj4NCjxiPkNjOiA8L2I+JnF1b3Q7U2FseiwgUmljaCZxdW90OyAmbHQ7cnNhbHpAYWthbWFpLmNv
bSZndDssIEJlbmphbWluIEthZHVrICZsdDtia2FkdWtAYWthbWFpLmNvbSZndDssIElFVEYgUVVJ
QyBXRyAmbHQ7cXVpY0BpZXRmLm9yZyZndDs8YnI+DQo8Yj5TdWJqZWN0OiA8L2I+UkU6IEdldHRp
bmcgdG8gY29uc2Vuc3VzIG9uIHBhY2tldCBudW1iZXIgZW5jcnlwdGlvbjwvc3Bhbj48bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48YSBuYW1lPSJfTWFpbE9y
aWdpbmFsQm9keSI+VGhpcyBpcyBub3QgYWJvdXQgcHV0dGluZyBwbGFpbnRleHQgZGF0YSBvbiB0
aGUgbmV0d29yaywgdGhpcyBpcyBhYm91dCBub3QgYWRkaW5nIFBORSB3aGljaCBpcyBpbnRlbmRl
ZCBmb3IgcHJldmVudGluZyBvc3NpZmljYXRpb24uIFNvIEkgZG9u4oCZdCB1bmRlcnN0YW5kIHdo
YXQgdGhlIHRydXN0IGlzc3VlIGJlaW5nIHJlZmVycmVkIHRvIGlzIGluIGNhc2Ugb2YNCiB0aGUg
cmFyZSBtaXNjb25maWcuIDxvOnA+PC9vOnA+PC9hPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPiZuYnNwOzxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28t
Ym9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPldpdGhpbiBhIERDIHNldmVyYWwgdGhpbmdzIGFy
ZSBkaWZmZXJlbnQg4oCTIHRoZSBkZXBsb3ltZW50IG1heSBuZWVkIGRpZmZlcmVudCBjb25nZXN0
aW9uIGNvbnRyb2wgbGlrZSBEQ1RDUCwgZGlmZmVyZW50IHNldHRpbmdzIGZvciB2YXJpb3VzIHRy
YW5zcG9ydCBwYXJhbWV0ZXJzIChsaWtlIG1pbnJ0byBhbmQgbWF4IEFDSyBkZWxheSksDQogbGFy
Z2VyIGZsb3cgY29udHJvbCB3aW5kb3cgZXRjLiBUaGlzIGlzIHRydWUgZm9yIFRDUCB0b2RheS4g
VGhlIG91dCBvZiBib3ggZGVmYXVsdCB1c2VzIHRoZSBoYW5kc2hha2UgUlRUIHRvIG1ha2UgYSBk
ZXRlcm1pbmF0aW9uIG9mIHdoYXTigJlzIGludHJhLURDIGJ1dCB0aGVyZSBpcyByaWNoIGNvbmZp
Z3VyYXRpb24gdG8gb3ZlcnJpZGUgdGhlIGRlZmF1bHQgYW5kIHNldCBpdCBiYXNlZCBvbiA0LXR1
cGxlIGZpbHRlcnMuDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij4mbmJzcDs8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNv
LWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij5BbmQgdGhlcmUgd29ya2xvYWRzIGxpa2UgY2xv
dWQgc3RvcmFnZSBhbmQgbGl2ZSBtaWdyYXRpb24gdGhhdCBhcmUgYnkgdmlydHVlIG9mIGRlcGxv
eW1lbnQgaW50cmEtREMuIFRoZXNlIGNhbm5vdCBiZSBsb2FkIHNoaWZ0ZWQgYXMgdGhleSB1c2Ug
cHJpdmF0ZSBJUCBhZGRyZXNzIHNwYWNlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHki
PiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPjxiPkZyb206PC9iPiBUZWQg
SGFyZGllIFttYWlsdG86dGVkLmlldGZAZ21haWwuY29tXQ0KPGJyPg0KPGI+U2VudDo8L2I+IFR1
ZXNkYXksIE1heSAxLCAyMDE4IDg6NTUgQU08YnI+DQo8Yj5Ubzo8L2I+IFJvYmVydG8gUGVvbiAm
bHQ7ZmVuaXhAZmIuY29tJmd0Ozxicj4NCjxiPkNjOjwvYj4gU2FseiwgUmljaCAmbHQ7cnNhbHpA
YWthbWFpLmNvbSZndDs7IEJlbmphbWluIEthZHVrICZsdDtia2FkdWtAYWthbWFpLmNvbSZndDs7
IFByYXZlZW4gQmFsYXN1YnJhbWFuaWFuICZsdDtwcmF2YkBtaWNyb3NvZnQuY29tJmd0OzsgSUVU
RiBRVUlDIFdHICZsdDtxdWljQGlldGYub3JnJmd0Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTog
R2V0dGluZyB0byBjb25zZW5zdXMgb24gcGFja2V0IG51bWJlciBlbmNyeXB0aW9uPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29r
bWFyazpfTWFpbE9yaWdpbmFsQm9keSI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxP
cmlnaW5hbEJvZHkiPk9uIFR1ZSwgTWF5IDEsIDIwMTggYXQgODoxMyBBTSwgUm9iZXJ0byBQZW9u
ICZsdDs8L3NwYW4+PGEgaHJlZj0ibWFpbHRvOmZlbml4QGZiLmNvbSIgdGFyZ2V0PSJfYmxhbmsi
PjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPmZlbml4QGZiLmNv
bTwvc3Bhbj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij48L3Nw
YW4+PC9hPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPiZndDsN
CiB3cm90ZTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3Rl
IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRp
bmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXRvcDo1LjBwdDtt
YXJnaW4tcmlnaHQ6MGluO21hcmdpbi1ib3R0b206NS4wcHQiPg0KPGRpdj4NCjxkaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9y
aWdpbmFsQm9keSI+QWxzbywgUHJpc20uJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFy
azpfTWFpbE9yaWdpbmFsQm9keSI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpf
TWFpbE9yaWdpbmFsQm9keSI+LT1SJm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpf
TWFpbE9yaWdpbmFsQm9keSI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFp
bE9yaWdpbmFsQm9keSI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPiZuYnNwOzxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9y
aWdpbmFsQm9keSI+VGhhdCdzIGEgbGl0dGxlIG1vcmUgc3VjY2luY3QgdGhhbiBJIHdvdWxkIGJl
LCBidXQgeWVzLiZuYnNwOyBIb3cgZG9lcyBhbiBhcHBsaWNhdGlvbiBrbm93IHRoYXQgdGhlIGZs
b3cgaXQgaXMgaW5pdGlhdGluZyB3aWxsIHRyYXZlcnNlIGEgdG9wb2xvZ3kgdGhhdCBpcyBkZWVt
ZWQgdG8gYmUNCiB3aXRoaW4gYSBjb250cm9sbGVkIGVudmlyb25tZW50PyZuYnNwOyBZb3UgY2Fu
IHNheSAmcXVvdDtjb25maWd1cmF0aW9uJnF1b3Q7IGJ1dCBJIGZlYXIgaXQgd2lsbCB0dXJuDQo8
L3NwYW4+PGEgaHJlZj0iaHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3VybD91
PWh0dHBzLTNBX19uYTAxLnNhZmVsaW5rcy5wcm90ZWN0aW9uLm91dGxvb2suY29tXy0zRnVybC0z
RGh0dHBzLTI1M0EtMjUyRi0yNTJGaS5raW5qYS0yRGltZy5jb20tMjUyRmdhd2tlci0yRG1lZGlh
LTI1MkZpbWFnZS0yNTJGdXBsb2FkLTI1MkZzLTJELTJERWR1NkxQdTktMkQtMkQtMjUyRmMtNUZz
Y2FsZS0yNTJDZi01RmF1dG8tMjUyQ2ZsLTVGcHJvZ3Jlc3NpdmUtMjUyQ3EtNUY4MC0yNTJDdy01
RjgwMC0yNTJGMTk0dGhidHllbmNzMGpwZy5qcGctMjZkYXRhLTNEMDItMjU3QzAxLTI1N0NwcmF2
Yi0yNTQwbWljcm9zb2Z0LmNvbS0yNTdDNGRhNDRlOGFjMWRmNDcwOGFkODgwOGQ1YWY3YmZjYTgt
MjU3QzcyZjk4OGJmODZmMTQxYWY5MWFiMmQ3Y2QwMTFkYjQ3LTI1N0MxLTI1N0MxLTI1N0M2MzY2
MDc4Njk0MTEyNTg5NzYtMjZzZGF0YS0zRFByb2xTSGtiRjJTZ01IM3FkUU4tMjUyQlpGb2tYdnNF
QmYtMjUyRjNvOU1hVW5pbDBnOC0yNTNELTI2cmVzZXJ2ZWQtM0QwJmFtcDtkPUR3TUdhUSZhbXA7
Yz01VkQwUlR0TmxUaDN5Y2Q0MWIzTVV3JmFtcDtyPUMwc1VvLUxGTkJhWWZ5b2FDc2Y2VEEmYW1w
O209VHVWZnp5cG8tQ1pMbzUyMmxnTVJyTHBLeGNGYUh2VzlrZE5TSTU3bFhUMCZhbXA7cz1CeTJk
X3RvN1h6TEVnQUwzT3I5Y1pjMkF5a3llLVBaRWVuRlFEdmlBVWx3JmFtcDtlPSI+PHNwYW4gc3R5
bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+dXANCiBvbiBhIHBvc3QtaXQmbmJz
cDsgPC9zcGFuPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPjwv
c3Bhbj48L2E+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+aWYg
eW91IGRvLiZuYnNwOyBMb2FkcyBzaGlmdCwgcmVzb3VyY2VzIG1vdmUsIGFuZCBzdWRkZW5seSB5
b3UgZmluZCB0aGF0IGhvc3Qgd2hpY2ggdXNlZCB0byBiZSBpbiB0aGUgc2FtZSByYWNrLCBiZWlu
ZyBkb3duLCBoYXMgbG9hZC1zaGlmdGVkDQogdG8gdGhlIG5leHQgaW5zdGFuY2UsJm5ic3A7IGlu
IGEgZGF0YWNlbnRlciA1MDAgbWlsZXMgYXdheSBhY3Jvc3MgYSB2ZXJ5IGRpZmZlcmVudCBuZXR3
b3JrLiZuYnNwOw0KPGJyPg0KPGJyPg0KTWFueSBtb2Rlcm4gZGVwbG95bWVudHMgYXJlIGFsc28g
aW4gc29tZW9uZSBlbHNlJ3MgZGF0YSBjZW50ZXIsIHNvIHNheWluZyAmcXVvdDtEYXRhIGNlbnRl
ciBuZXR3b3JrcyZxdW90OyBkb2Vzbid0IHNheSBtdWNoIGFib3V0IHdoeSB5b3UncmUgdHJ1c3Rp
bmcgdGhlIG5ldHdvcmsgaW5zaWRlLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxP
cmlnaW5hbEJvZHkiPlRlZDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5h
bEJvZHkiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUg
c3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGlu
ZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tdG9wOjUuMHB0O21h
cmdpbi1yaWdodDowaW47bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXYg
aWQ9Im1fLTM3NzU1NTIwOTc1ODI2NjQ1NjJ4X2NvbXBvc2VyX3NpZ25hdHVyZSI+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdp
bmFsQm9keSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5LjVwdDtjb2xvcjojNTc1NzU3Ij5TZW50
IHZpYSB0aGUgU2Ftc3VuZyBHYWxheHkgUzcsIGFuIEFUJmFtcDtUIDRHIExURSBzbWFydHBob25l
PC9zcGFuPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFs
Qm9keSI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9k
eSI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+
LS0tLS0tLS0gT3JpZ2luYWwgbWVzc2FnZSAtLS0tLS0tLTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9v
a21hcms6X01haWxPcmlnaW5hbEJvZHkiPkZyb206ICZxdW90O1NhbHosIFJpY2gmcXVvdDsgJmx0
O3JzYWx6PTwvc3Bhbj48YSBocmVmPSJtYWlsdG86NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3Jn
IiB0YXJnZXQ9Il9ibGFuayI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFs
Qm9keSI+NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnPC9zcGFuPjxzcGFuIHN0eWxlPSJtc28t
Ym9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPjwvc3Bhbj48L2E+PHNwYW4gc3R5bGU9Im1zby1i
b29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+Jmd0Ow0KPG86cD48L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29r
bWFyazpfTWFpbE9yaWdpbmFsQm9keSI+RGF0ZTogNS8xLzE4IDU6MjUgQU0gKEdNVC0wODowMCkN
CjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPlRvOiBCZW5q
YW1pbiBLYWR1ayAmbHQ7YmthZHVrPTwvc3Bhbj48YSBocmVmPSJtYWlsdG86NDBha2FtYWkuY29t
QGRtYXJjLmlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFy
azpfTWFpbE9yaWdpbmFsQm9keSI+NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnPC9zcGFuPjxz
cGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPjwvc3Bhbj48L2E+PHNw
YW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+Jmd0OywNCiBQcmF2ZWVu
IEJhbGFzdWJyYW1hbmlhbiAmbHQ7cHJhdmI9PC9zcGFuPjxhIGhyZWY9Im1haWx0bzo0MG1pY3Jv
c29mdC5jb21AZG1hcmMuaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj48c3BhbiBzdHlsZT0ibXNv
LWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij40MG1pY3Jvc29mdC5jb21AZG1hcmMuaWV0Zi5v
cmc8L3NwYW4+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+PC9z
cGFuPjwvYT48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij4mZ3Q7
DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij5DYzogSUVU
RiBRVUlDIFdHICZsdDs8L3NwYW4+PGEgaHJlZj0ibWFpbHRvOnF1aWNAaWV0Zi5vcmciIHRhcmdl
dD0iX2JsYW5rIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij5x
dWljQGlldGYub3JnPC9zcGFuPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5h
bEJvZHkiPjwvc3Bhbj48L2E+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFs
Qm9keSI+Jmd0Ow0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9k
eSI+U3ViamVjdDogUmU6IEdldHRpbmcgdG8gY29uc2Vuc3VzIG9uIHBhY2tldCBudW1iZXIgZW5j
cnlwdGlvbg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+
Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBw
dCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+Jm5ic3A7Jm5i
c3A7Jm5ic3A7ICZndDsgSSBkaXNhZ3JlZSB0aGF0IHdlIG5lZWQgYW55IG1vcmUgZGF0YSBmb3Ig
bm90IGRvaW5nIFBORSBpbiB0aGUgZGF0YWNlbnRlci4gV2h5IHdvdWxkIHdlIGFkZCBhbiBleHRy
YSBlbmNyeXB0LWRlY3J5cHQgc3RlcCBmb3Igbm8gb2J2aW91cyBiZW5lZml0Pzxicj4NCjxicj4N
CkkgYW0gY29uY2VybmVkIHRoYXQgcGVvcGxlIHdpbGwgbWlzLWludGVycHJldCB0aGUgbWVhbmlu
ZyBvZiBhIGRhdGFjZW50ZXIsIGFuZCB0aGluayB0aGF0IGEgYnVuY2ggb2Ygc2VydmVycywgb3Ig
ZXZlbiBhIHJhY2ssIGluIGFuIG9wZW4gY29sbyBzcGFjZSBpcyBhICZxdW90O2RhdGFjZW50ZXIu
JnF1b3Q7Jm5ic3A7IENvbXB1dGVycyBrZWVwIGdldHRpbmcgZmFzdGVyLg0KPG86cD48L286cD48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+
DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6
X01haWxPcmlnaW5hbEJvZHkiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_01AE46C6682C4A2184CD1D8DAD6F49D9fbcom_--


From nobody Tue May  1 17:37:12 2018
Return-Path: <jri.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2BC9612D7EF for <quic@ietfa.amsl.com>; Tue,  1 May 2018 17:37:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 xL9cF3Rue8zC for <quic@ietfa.amsl.com>; Tue,  1 May 2018 17:37:06 -0700 (PDT)
Received: from mail-wr0-x244.google.com (mail-wr0-x244.google.com [IPv6:2a00:1450:400c:c0c::244]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACE7B12D77D for <quic@ietf.org>; Tue,  1 May 2018 17:37:05 -0700 (PDT)
Received: by mail-wr0-x244.google.com with SMTP id y15-v6so445804wrg.11 for <quic@ietf.org>; Tue, 01 May 2018 17:37:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=msdOv2txmb7Uxv/mDBEABFhzOuCrE/YqcfauFP8ujao=; b=apkRoSgZPzNq56zEQild1U3ki9KI/ylDsxopbRpvH5wqBvShQYXbGBt4ui6tzLVF7j kb+pAOcQ2eF2gRQR5yjkItgRHlXj4jlSZaNQMfjcB8/g6X9WOqussozLqVt8Lk8EfK+o ThhfnGvKjhpUgshPMkCrBpxgYtMLwOotrjLK/3Gj8EWDHv620bs1ikQPVhJijUz5uVlx qIp2yOTJEAI2P6mTfqX7dQNR7x943XCkSdvl9JdFGkH/5giY7R43PIeoEV3fI0jX3Lef 95DPdUA6zOzJUDgG+fzolNvIp5RT6bja0ksHuGgbIgnlAbMXEy3gfRhzewcHAVO+lmif k5/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=msdOv2txmb7Uxv/mDBEABFhzOuCrE/YqcfauFP8ujao=; b=NyfdfK5DiQiw09XbDtI9api5xQjnPfEBRmJgj/lCgkQtu4IaMO++5E/VXeF171Mu3o /MhoHz6vPwwThF6HUFlKzY59y3p/GOAqsJYizrQmaVVfquAByCUQyydyNSSBqQTCFzaK 4hRvecrZ/mk3omutKqy8pE3dMotDLVVWpp+Xi7o3QktxA3nq+Byv63X3byfvhdFEGum7 PdIv9JIhZ8Xj0HmE1y4t+O9zBvP1fuwXfMjFQdfIfT8U2GmAfFmTyw+jY7sfZ8XqnkSR QRlwCMheld1i1x9PSdd93Ak1qo2lIORkJmk4LcapF9JVcyn1jEdRlpzaLC7pq2JMaCu1 b8Kg==
X-Gm-Message-State: ALQs6tCVoujlpsFbJ4AV6iO5CGv2LERs3z4Ui0YjvJVFbzv1FS4IQLu+ Nw/V/Z160iXTapf6CufwzsSS6uu1PzATXpZ+nZ1Tsw==
X-Google-Smtp-Source: AB8JxZpmyKCAkduWsl0c9+VlfmZQr3PK4538oRiSo/vcZPwpL1h0OFMQ5cS9W+X9Eqgz6JMBEsyCph61byhdZqARLPw=
X-Received: by 2002:adf:84c3:: with SMTP id 61-v6mr13569717wrg.37.1525221424050;  Tue, 01 May 2018 17:37:04 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.223.187.9 with HTTP; Tue, 1 May 2018 17:37:03 -0700 (PDT)
In-Reply-To: <01AE46C6-682C-4A21-84CD-1D8DAD6F49D9@fb.com>
References: <01AE46C6-682C-4A21-84CD-1D8DAD6F49D9@fb.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Tue, 1 May 2018 17:37:03 -0700
Message-ID: <CACpbDcdnmHrWMCShYd1pEDBervRKfO1pMUM8hb4tkK9nqH1Mdw@mail.gmail.com>
Subject: Re: [Potential Spoof] Re: Getting to consensus on packet number encryption
To: Roberto Peon <fenix@fb.com>
Cc: Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>, Ted Hardie <ted.ietf@gmail.com>,  "Salz, Rich" <rsalz@akamai.com>, Benjamin Kaduk <bkaduk@akamai.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002f372d056b2e4942"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/aI3baRb7q8tlyxSIax_t6v8rTT4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 00:37:10 -0000

--0000000000002f372d056b2e4942
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I'll try to summarize my position on #1079. I see two points:
1. PNE will help against ossification and also, albeit to a limited extent,
linkability.
2. PNE has a CPU cost. While we can speculate, we still don't *know* what
this cost will be in the context of deployment, and whether this cost will
be the show-stopper. PNE's CPU cost may or may not be ameliorated by NIC
implementation. We should allow PNE negotiability when we have established
that this cost is worth saving.

My sense is that we agree on (1). This is what #1079 is doing, so we should
separate the two questions and get (1) done. Whether we do (2) or not is
being discussed on this thread, and I think we can continue, but #1079
should be independently submitted.

FWIW, I believe that we want to iterate on versions, and that we will want
to get a v2 out as soon as we have things to get deployed that left pending
in v1.


Thoughts on intra-DC QUIC, related to point (2) follow:

I don't think we'll reach a meaningful end to this discussion by getting
into security for intra-DC protocols. I understand that there may be
situations where one may have fair certainty about the deployment context
and given that the security tradeoff isn't the same as disabling TLS, the
bar will be substantially lower for disabling PNE.

On QUIC in intra-DC environments:
1. As Igor noted, the value of QUIC in the intra-DC environments is
uncertain, and I'm not yet sure that compromising on PNE for an unknown
cost in an uncertain deployment context is necessarily useful.
2. Separately, I remain unconvinced, based on my experience with trying to
get QUIC used for DC transport, that this cost is going to be an important
factor in QUIC adoption within DCs. I agree that CPU cost is a factor, but
there are much bigger things here that will need attention (segmentation
offload, smaller record sizes, userspace costs) that will dominate well
before this AES operation becomes a factor. This all remains speculation
though.

Praveen: Not making PNE optional right now does not mean we won't do it. It
just means that it's an open question. I'm not yet convinced that it's a
debilitating cost or one of the proverbial "million cuts" that will keep it
from getting deployed intra-DC. You are right that you'll want to
standardize PNE negotiation if you use multiple platforms, but surely you
will be just doing this between Windows systems for a while if you start
using QUIC inside the DC. That would be a great time to use versioning to
run your own version within the DC, and compare the cost to IETF v1, and
see if it is worth removing PNE. I hope you find other costs that are worth
eliminating or changes that are worth making to the protocol too, and that
they all become part of standard QUIC as a consequence. But in the
meanwhile, I don't see why making it optional is necessary right now to add
PNE at all.

On Tue, May 1, 2018 at 4:22 PM, Roberto Peon <fenix@fb.com> wrote:

> I=E2=80=99d suggest we start working on it now.
>
> This is only partly a joke =E2=98=BA
>
> -=3DR
>
>
>
> *From: *QUIC <quic-bounces@ietf.org> on behalf of Roberto Peon <
> fenix@fb.com>
> *Date: *Tuesday, May 1, 2018 at 4:21 PM
> *To: *Praveen Balasubramanian <pravb=3D40microsoft.com@dmarc.ietf.org>, T=
ed
> Hardie <ted.ietf@gmail.com>
> *Cc: *"Salz, Rich" <rsalz@akamai.com>, Benjamin Kaduk <bkaduk@akamai.com>=
,
> IETF QUIC WG <quic@ietf.org>
> *Subject: *[Potential Spoof] Re: Getting to consensus on packet number
> encryption
>
>
>
> Yup. I know.
>
> Prism was eye-opening partially because of the fact that the packets were
> not going across the internet, but rather within a secure network.
>
>
>
> I believe that ossification alone is a good enough reason to do PNE.
>
> The cherry for me is that it, along with other actions/mitigations, makes
> linkability more difficult for malicious actors.
> CRIME and related was eye-opening because it exposed the power of the
> observable side-channel.
>
>
> -=3DR
>
>
>
> *From: *QUIC <quic-bounces@ietf.org> on behalf of Praveen Balasubramanian
> <pravb=3D40microsoft.com@dmarc.ietf.org>
> *Date: *Tuesday, May 1, 2018 at 9:35 AM
> *To: *Ted Hardie <ted.ietf@gmail.com>, Roberto Peon <fenix@fb.com>
> *Cc: *"Salz, Rich" <rsalz@akamai.com>, Benjamin Kaduk <bkaduk@akamai.com>=
,
> IETF QUIC WG <quic@ietf.org>
> *Subject: *RE: Getting to consensus on packet number encryption
>
>
>
> This is not about putting plaintext data on the network, this is about no=
t
> adding PNE which is intended for preventing ossification. So I don=E2=80=
=99t
> understand what the trust issue being referred to is in case of the rare
> misconfig.
>
>
>
> Within a DC several things are different =E2=80=93 the deployment may nee=
d
> different congestion control like DCTCP, different settings for various
> transport parameters (like minrto and max ACK delay), larger flow control
> window etc. This is true for TCP today. The out of box default uses the
> handshake RTT to make a determination of what=E2=80=99s intra-DC but ther=
e is rich
> configuration to override the default and set it based on 4-tuple filters=
.
>
>
>
> And there workloads like cloud storage and live migration that are by
> virtue of deployment intra-DC. These cannot be load shifted as they use
> private IP address space.
>
>
>
> *From:* Ted Hardie [mailto:ted.ietf@gmail.com]
> *Sent:* Tuesday, May 1, 2018 8:55 AM
> *To:* Roberto Peon <fenix@fb.com>
> *Cc:* Salz, Rich <rsalz@akamai.com>; Benjamin Kaduk <bkaduk@akamai.com>;
> Praveen Balasubramanian <pravb@microsoft.com>; IETF QUIC WG <quic@ietf.or=
g
> >
> *Subject:* Re: Getting to consensus on packet number encryption
>
>
>
> On Tue, May 1, 2018 at 8:13 AM, Roberto Peon <fenix@fb.com> wrote:
>
> Also, Prism.
>
>
>
> -=3DR
>
>
>
>
>
>
>
> That's a little more succinct than I would be, but yes.  How does an
> application know that the flow it is initiating will traverse a topology
> that is deemed to be within a controlled environment?  You can say
> "configuration" but I fear it will turn up on a post-it
> <https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__na01.safelinks.pr=
otection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fi.kinja-2Dimg.com-252Fgaw=
ker-2Dmedia-252Fimage-252Fupload-252Fs-2D-2DEdu6LPu9-2D-2D-252Fc-5Fscale-25=
2Cf-5Fauto-252Cfl-5Fprogressive-252Cq-5F80-252Cw-5F800-252F194thbtyencs0jpg=
.jpg-26data-3D02-257C01-257Cpravb-2540microsoft.com-257C4da44e8ac1df4708ad8=
808d5af7bfca8-257C72f988bf86f141af91ab2d7cd011db47-257C1-257C1-257C63660786=
9411258976-26sdata-3DProlSHkbF2SgMH3qdQN-252BZFokXvsEBf-252F3o9MaUnil0g8-25=
3D-26reserved-3D0&d=3DDwMGaQ&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3DC0sUo-LFNBaYfyo=
aCsf6TA&m=3DTuVfzypo-CZLo522lgMRrLpKxcFaHvW9kdNSI57lXT0&s=3DBy2d_to7XzLEgAL=
3Or9cZc2Aykye-PZEenFQDviAUlw&e=3D>if
> you do.  Loads shift, resources move, and suddenly you find that host whi=
ch
> used to be in the same rack, being down, has load-shifted to the next
> instance,  in a datacenter 500 miles away across a very different network=
.
>
> Many modern deployments are also in someone else's data center, so saying
> "Data center networks" doesn't say much about why you're trusting the
> network inside.
>
> Ted
>
>
>
> Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
>
>
>
>
>
> -------- Original message --------
>
> From: "Salz, Rich" <rsalz=3D40akamai.com@dmarc.ietf.org>
>
> Date: 5/1/18 5:25 AM (GMT-08:00)
>
> To: Benjamin Kaduk <bkaduk=3D40akamai.com@dmarc.ietf.org>, Praveen
> Balasubramanian <pravb=3D40microsoft.com@dmarc.ietf.org>
>
> Cc: IETF QUIC WG <quic@ietf.org>
>
> Subject: Re: Getting to consensus on packet number encryption
>
>
>
>     > I disagree that we need any more data for not doing PNE in the
> datacenter. Why would we add an extra encrypt-decrypt step for no obvious
> benefit?
>
> I am concerned that people will mis-interpret the meaning of a datacenter=
,
> and think that a bunch of servers, or even a rack, in an open colo space =
is
> a "datacenter."  Computers keep getting faster.
>
>
>

--0000000000002f372d056b2e4942
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;ll try to summarize my position on #1079. I see two =
points:<div>1. PNE will help against ossification and also, albeit to a lim=
ited extent, linkability.</div><div>2. PNE has a CPU cost. While we can spe=
culate, we still don&#39;t *know* what this cost will be in the context of =
deployment, and whether this cost will be the show-stopper. <span style=3D"=
color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style=
:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:=
400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:n=
one;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);t=
ext-decoration-style:initial;text-decoration-color:initial;float:none;displ=
ay:inline">PNE&#39;s CPU cost may or may not be ameliorated by NIC implemen=
tation. We should allow PNE negotiability when we have established that thi=
s cost is worth saving.=C2=A0</span></div><div><br></div><div>My sense is t=
hat we agree on (1). This is what #1079 is doing, so we should separate the=
 two questions and get (1) done. Whether we do (2) or not is being discusse=
d on this thread, and I think we can continue, but #1079 should be independ=
ently submitted.</div><div><br></div><div>FWIW,=C2=A0<span style=3D"color:r=
gb(34,34,34);font-family:arial,sans-serif;font-size:small;font-style:normal=
;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;let=
ter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;whi=
te-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-dec=
oration-style:initial;text-decoration-color:initial;float:none;display:inli=
ne">I believe that we want to iterate on versions, and that we will want to=
 get a v2 out as soon as we have things to get deployed that left pending i=
n v1.</span></div><div><br></div><div><br></div><div>Thoughts on intra-DC Q=
UIC, related to point (2) follow:</div><div><span style=3D"color:rgb(34,34,=
34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-var=
iant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spaci=
ng:normal;text-align:start;text-indent:0px;text-transform:none;white-space:=
normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-s=
tyle:initial;text-decoration-color:initial;float:none;display:inline"><br><=
/span></div><div><span style=3D"color:rgb(34,34,34);font-family:arial,sans-=
serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-=
variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;=
text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;bac=
kground-color:rgb(255,255,255);text-decoration-style:initial;text-decoratio=
n-color:initial;float:none;display:inline">I don&#39;t think we&#39;ll reac=
h a meaningful end to this discussion by getting into security for intra-DC=
 protocols.<span>=C2=A0</span></span>I understand that there may be situati=
ons where one may have fair certainty about the deployment context and give=
n that the security tradeoff isn&#39;t the same as disabling TLS, the bar w=
ill be substantially lower for disabling PNE.=C2=A0</div><div><br></div><di=
v><div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:=
small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:nor=
mal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;=
text-transform:none;white-space:normal;word-spacing:0px;text-decoration-sty=
le:initial;text-decoration-color:initial">On QUIC in intra-DC environments:=
=C2=A0</div><div style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;=
font-size:small;font-style:normal;font-variant-ligatures:normal;font-varian=
t-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-i=
ndent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-deco=
ration-style:initial;text-decoration-color:initial">1. As Igor noted, the v=
alue of QUIC in the intra-DC environments is uncertain, and I&#39;m not yet=
 sure that compromising on PNE for an unknown cost in an uncertain deployme=
nt context is necessarily useful.=C2=A0</div><div style=3D"color:rgb(34,34,=
34);font-family:arial,sans-serif;font-size:small;font-style:normal;font-var=
iant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spaci=
ng:normal;text-align:start;text-indent:0px;text-transform:none;white-space:=
normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color=
:initial">2. Separately, I remain unconvinced, based on my experience with =
trying to get QUIC used for DC transport, that this cost is going to be an =
important factor in QUIC adoption within DCs. I agree that CPU cost is a fa=
ctor, but there are much bigger things here that will need attention (segme=
ntation offload, smaller record sizes, userspace costs) that will dominate =
well before this AES operation becomes a factor. This all remains speculati=
on though.</div></div><div><br></div><div>Praveen: Not making PNE optional =
right now does not mean we won&#39;t do it. It just means that it&#39;s an =
open question. I&#39;m not yet convinced that it&#39;s a debilitating cost =
or one of the proverbial &quot;million cuts&quot; that will keep it from ge=
tting deployed intra-DC. You are right that you&#39;ll want to standardize =
PNE negotiation if you use multiple platforms, but surely you will be just =
doing this between Windows systems for a while if you start using QUIC insi=
de the DC. That would be a great time to use versioning to run your own ver=
sion within the DC, and compare the cost to IETF v1, and see if it is worth=
 removing PNE. I hope you find other costs that are worth eliminating or ch=
anges that are worth making to the protocol too, and that they all become p=
art of standard QUIC as a consequence. But in the meanwhile, I don&#39;t se=
e why making it optional is necessary right now to add PNE at all.</div></d=
iv><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, May 1,=
 2018 at 4:22 PM, Roberto Peon <span dir=3D"ltr">&lt;<a href=3D"mailto:feni=
x@fb.com" target=3D"_blank">fenix@fb.com</a>&gt;</span> wrote:<br><blockquo=
te class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc so=
lid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_-1834203662092296185WordSection1">
<p class=3D"MsoNormal">I=E2=80=99d suggest we start working on it now.<u></=
u><u></u></p>
<p class=3D"MsoNormal">This is only partly a joke <span style=3D"font-famil=
y:&quot;Apple Color Emoji&quot;">
=E2=98=BA</span><u></u><u></u></p>
<p class=3D"MsoNormal">-=3DR<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:12.0pt;color:black">From=
: </span></b><span style=3D"font-size:12.0pt;color:black">QUIC &lt;<a href=
=3D"mailto:quic-bounces@ietf.org" target=3D"_blank">quic-bounces@ietf.org</=
a>&gt; on behalf of Roberto Peon &lt;<a href=3D"mailto:fenix@fb.com" target=
=3D"_blank">fenix@fb.com</a>&gt;<br>
<b>Date: </b>Tuesday, May 1, 2018 at 4:21 PM<br>
<b>To: </b>Praveen Balasubramanian &lt;pravb=3D<a href=3D"mailto:40microsof=
t.com@dmarc.ietf.org" target=3D"_blank">40microsoft.com@dmarc.<wbr>ietf.org=
</a>&gt;, Ted Hardie &lt;<a href=3D"mailto:ted.ietf@gmail.com" target=3D"_b=
lank">ted.ietf@gmail.com</a>&gt;<br>
<b>Cc: </b>&quot;Salz, Rich&quot; &lt;<a href=3D"mailto:rsalz@akamai.com" t=
arget=3D"_blank">rsalz@akamai.com</a>&gt;, Benjamin Kaduk &lt;<a href=3D"ma=
ilto:bkaduk@akamai.com" target=3D"_blank">bkaduk@akamai.com</a>&gt;, IETF Q=
UIC WG &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic@ietf.org=
</a>&gt;<br>
<b>Subject: </b>[Potential Spoof] Re: Getting to consensus on packet number=
 encryption<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<p class=3D"MsoNormal">Yup. I know.<u></u><u></u></p>
<p class=3D"MsoNormal">Prism was eye-opening partially because of the fact =
that the packets were not going across the internet, but rather within a se=
cure network.<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p class=3D"MsoNormal">I believe that ossification alone is a good enough r=
eason to do PNE.<u></u><u></u></p>
<p class=3D"MsoNormal">The cherry for me is that it, along with other actio=
ns/mitigations, makes linkability more difficult for malicious actors.<br>
CRIME and related was eye-opening because it exposed the power of the obser=
vable side-channel.
<u></u><u></u></p>
<p class=3D"MsoNormal"><br>
-=3DR<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:12.0pt;color:black">From=
: </span></b><span style=3D"font-size:12.0pt;color:black">QUIC &lt;<a href=
=3D"mailto:quic-bounces@ietf.org" target=3D"_blank">quic-bounces@ietf.org</=
a>&gt; on behalf of Praveen Balasubramanian &lt;pravb=3D<a href=3D"mailto:4=
0microsoft.com@dmarc.ietf.org" target=3D"_blank">40microsoft.com@dmarc.<wbr=
>ietf.org</a>&gt;<br>
<b>Date: </b>Tuesday, May 1, 2018 at 9:35 AM<br>
<b>To: </b>Ted Hardie &lt;<a href=3D"mailto:ted.ietf@gmail.com" target=3D"_=
blank">ted.ietf@gmail.com</a>&gt;, Roberto Peon &lt;<a href=3D"mailto:fenix=
@fb.com" target=3D"_blank">fenix@fb.com</a>&gt;<br>
<b>Cc: </b>&quot;Salz, Rich&quot; &lt;<a href=3D"mailto:rsalz@akamai.com" t=
arget=3D"_blank">rsalz@akamai.com</a>&gt;, Benjamin Kaduk &lt;<a href=3D"ma=
ilto:bkaduk@akamai.com" target=3D"_blank">bkaduk@akamai.com</a>&gt;, IETF Q=
UIC WG &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic@ietf.org=
</a>&gt;<br>
<b>Subject: </b>RE: Getting to consensus on packet number encryption</span>=
<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><a name=3D"m_-1834203662092296185__MailOriginalBody"=
>This is not about putting plaintext data on the network, this is about not=
 adding PNE which is intended for preventing ossification. So I don=E2=80=
=99t understand what the trust issue being referred to is in case of
 the rare misconfig. <u></u><u></u></a></p>
<p class=3D"MsoNormal"><span>=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span>Within a DC several things are different =E2=
=80=93 the deployment may need different congestion control like DCTCP, dif=
ferent settings for various transport parameters (like minrto and max ACK d=
elay),
 larger flow control window etc. This is true for TCP today. The out of box=
 default uses the handshake RTT to make a determination of what=E2=80=99s i=
ntra-DC but there is rich configuration to override the default and set it =
based on 4-tuple filters.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span>=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span>And there workloads like cloud storage and liv=
e migration that are by virtue of deployment intra-DC. These cannot be load=
 shifted as they use private IP address space.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span>=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span><b>From:</b> Ted Hardie [mailto:<a href=3D"mai=
lto:ted.ietf@gmail.com" target=3D"_blank">ted.ietf@gmail.com</a>]
<br>
<b>Sent:</b> Tuesday, May 1, 2018 8:55 AM<br>
<b>To:</b> Roberto Peon &lt;<a href=3D"mailto:fenix@fb.com" target=3D"_blan=
k">fenix@fb.com</a>&gt;<br>
<b>Cc:</b> Salz, Rich &lt;<a href=3D"mailto:rsalz@akamai.com" target=3D"_bl=
ank">rsalz@akamai.com</a>&gt;; Benjamin Kaduk &lt;<a href=3D"mailto:bkaduk@=
akamai.com" target=3D"_blank">bkaduk@akamai.com</a>&gt;; Praveen Balasubram=
anian &lt;<a href=3D"mailto:pravb@microsoft.com" target=3D"_blank">pravb@mi=
crosoft.com</a>&gt;; IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" targ=
et=3D"_blank">quic@ietf.org</a>&gt;<span class=3D""><br>
<b>Subject:</b> Re: Getting to consensus on packet number encryption<u></u>=
<u></u></span></span></p>
<p class=3D"MsoNormal"><span>=C2=A0<u></u><u></u></span></p>
<div>
<p class=3D"MsoNormal"><span>On Tue, May 1, 2018 at 8:13 AM, Roberto Peon &=
lt;</span><a href=3D"mailto:fenix@fb.com" target=3D"_blank"><span>fenix@fb.=
com</span><span></span></a><span>&gt;
 wrote:<u></u><u></u></span></p>
<div>
<div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-=
bottom:5.0pt">
<div>
<div>
<div>
<p class=3D"MsoNormal"><span>Also, Prism.=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>-=3DR=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0<u></u><u></u></span></p>
</div>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span>=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span>That&#39;s a li=
ttle more succinct than I would be, but yes.=C2=A0 How does an application =
know that the flow it is initiating will traverse a topology that is deemed=
 to be
 within a controlled environment?=C2=A0 You can say &quot;configuration&quo=
t; but I fear it will turn
</span><a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__na=
01.safelinks.protection.outlook.com_-3Furl-3Dhttps-253A-252F-252Fi.kinja-2D=
img.com-252Fgawker-2Dmedia-252Fimage-252Fupload-252Fs-2D-2DEdu6LPu9-2D-2D-2=
52Fc-5Fscale-252Cf-5Fauto-252Cfl-5Fprogressive-252Cq-5F80-252Cw-5F800-252F1=
94thbtyencs0jpg.jpg-26data-3D02-257C01-257Cpravb-2540microsoft.com-257C4da4=
4e8ac1df4708ad8808d5af7bfca8-257C72f988bf86f141af91ab2d7cd011db47-257C1-257=
C1-257C636607869411258976-26sdata-3DProlSHkbF2SgMH3qdQN-252BZFokXvsEBf-252F=
3o9MaUnil0g8-253D-26reserved-3D0&amp;d=3DDwMGaQ&amp;c=3D5VD0RTtNlTh3ycd41b3=
MUw&amp;r=3DC0sUo-LFNBaYfyoaCsf6TA&amp;m=3DTuVfzypo-CZLo522lgMRrLpKxcFaHvW9=
kdNSI57lXT0&amp;s=3DBy2d_to7XzLEgAL3Or9cZc2Aykye-PZEenFQDviAUlw&amp;e=3D" t=
arget=3D"_blank"><span>up
 on a post-it=C2=A0 </span><span></span></a><span>if you do.=C2=A0 Loads sh=
ift, resources move, and suddenly you find that host which used to be in th=
e same rack, being down, has load-shifted
 to the next instance,=C2=A0 in a datacenter 500 miles away across a very d=
ifferent network.=C2=A0
<br>
<br>
Many modern deployments are also in someone else&#39;s data center, so sayi=
ng &quot;Data center networks&quot; doesn&#39;t say much about why you&#39;=
re trusting the network inside.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>Ted<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0<u></u><u></u></span></p>
</div>
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-top:5.0pt;margin-right:0in;margin-=
bottom:5.0pt">
<div>
<div>
<div id=3D"m_-1834203662092296185m_-3775552097582664562x_composer_signature=
">
<div>
<p class=3D"MsoNormal"><span><span style=3D"font-size:9.5pt;color:#575757">=
Sent via the Samsung Galaxy S7, an AT&amp;T 4G LTE smartphone</span><u></u>=
<u></u></span></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>-------- Original message --------<u></u><u></=
u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>From: &quot;Salz, Rich&quot; &lt;rsalz=3D</spa=
n><a href=3D"mailto:40akamai.com@dmarc.ietf.org" target=3D"_blank"><span>40=
akamai.com@dmarc.<wbr>ietf.org</span><span></span></a><span>&gt;
<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>Date: 5/1/18 5:25 AM (GMT-08:00)
<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>To: Benjamin Kaduk &lt;bkaduk=3D</span><a href=
=3D"mailto:40akamai.com@dmarc.ietf.org" target=3D"_blank"><span>40akamai.co=
m@dmarc.<wbr>ietf.org</span><span></span></a><span>&gt;,
 Praveen Balasubramanian &lt;pravb=3D</span><a href=3D"mailto:40microsoft.c=
om@dmarc.ietf.org" target=3D"_blank"><span>40microsoft.com@dmarc.<wbr>ietf.=
org</span><span></span></a><span>&gt;
<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>Cc: IETF QUIC WG &lt;</span><a href=3D"mailto:=
quic@ietf.org" target=3D"_blank"><span>quic@ietf.org</span><span></span></a=
><span>&gt;
<u></u><u></u></span></p>
</div><span class=3D"">
<div>
<p class=3D"MsoNormal"><span>Subject: Re: Getting to consensus on packet nu=
mber encryption
<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0<u></u><u></u></span></p>
</div>
</span></div>
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span>=C2=A0=C2=A0=C2=
=A0 &gt; I disagree that we need any more data for not doing PNE in the dat=
acenter. Why would we add an extra encrypt-decrypt step for no obvious bene=
fit?<br>
<br>
I am concerned that people will mis-interpret the meaning of a datacenter, =
and think that a bunch of servers, or even a rack, in an open colo space is=
 a &quot;datacenter.&quot;=C2=A0 Computers keep getting faster.
<u></u><u></u></span></p>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<p class=3D"MsoNormal"><span>=C2=A0<u></u><u></u></span></p>
</div>
</div>
</div>
</div>

</blockquote></div><br></div>

--0000000000002f372d056b2e4942--


From nobody Tue May  1 19:02:46 2018
Return-Path: <pravb@microsoft.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3C9812778E for <quic@ietfa.amsl.com>; Tue,  1 May 2018 19:02:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 5wSITI0BWusv for <quic@ietfa.amsl.com>; Tue,  1 May 2018 19:02:40 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0123.outbound.protection.outlook.com [104.47.33.123]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 984FC12702E for <quic@ietf.org>; Tue,  1 May 2018 19:02:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=oddqDbI1fqJVzqKv9fh1HMk4DKWM9CFnjqVePjzYZP4=; b=HouUYVPtw7+ycdK9hVgTtxJaEDHfINRwWShlh0btFJbtCOYVoTDcTqxVOXsjLEziqHogTb/JADZjD7CCN+XcZizE7Bz7atFK9QK1GQsDWkudrr5TqtSTKObYlv1b1QdPdPnjYx+1lD1szMbnLrHGUA3PspvEixjX1dJSJMDPTFk=
Received: from MWHPR21MB0638.namprd21.prod.outlook.com (10.175.141.139) by MWHPR21MB0175.namprd21.prod.outlook.com (10.173.52.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.735.4; Wed, 2 May 2018 02:02:37 +0000
Received: from MWHPR21MB0638.namprd21.prod.outlook.com ([fe80::6d48:f7af:d267:2021]) by MWHPR21MB0638.namprd21.prod.outlook.com ([fe80::6d48:f7af:d267:2021%7]) with mapi id 15.20.0735.006; Wed, 2 May 2018 02:02:37 +0000
From: Praveen Balasubramanian <pravb@microsoft.com>
To: Jana Iyengar <jri.ietf@gmail.com>, Roberto Peon <fenix@fb.com>
CC: Ted Hardie <ted.ietf@gmail.com>, "Salz, Rich" <rsalz@akamai.com>, Benjamin Kaduk <bkaduk@akamai.com>, IETF QUIC WG <quic@ietf.org>
Subject: RE: [Potential Spoof] Re: Getting to consensus on packet number encryption
Thread-Topic: [Potential Spoof] Re: Getting to consensus on packet number encryption
Thread-Index: AQHT4aNDwsND+KyhPEGdsYUFiGhpMqQbmBqAgAAI4rA=
Date: Wed, 2 May 2018 02:02:37 +0000
Message-ID: <MWHPR21MB06386100B48E17A059B5A04EB6800@MWHPR21MB0638.namprd21.prod.outlook.com>
References: <01AE46C6-682C-4A21-84CD-1D8DAD6F49D9@fb.com> <CACpbDcdnmHrWMCShYd1pEDBervRKfO1pMUM8hb4tkK9nqH1Mdw@mail.gmail.com>
In-Reply-To: <CACpbDcdnmHrWMCShYd1pEDBervRKfO1pMUM8hb4tkK9nqH1Mdw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e8:9::5ef]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MWHPR21MB0175; 7:aQCmYpqeJWfyJQJK4P6AOZZFqWY8L01kG+0V+K972i0EvzcUJAv+b6lqPQfHOyOJOsyuArzt4xQu/CAyRQl2zKqbY/F0zJXaXVi3mbvO6lngGvNnfU+1GmXF8HS5jNol1HvclszV8eVRnPW9VyAbqnX3voS9svGwF4qBffop9KDPvexUndNsaq19P+8oIAP1qsDCv3F6hea9wL1A8M2rZZuDDqP8klASA1BFwtUWJZVUqP07VS1r331M4dbtDQ16; 20:v/2ofadtqOCe1mkBQRlsWSk2qwhWSLX40iyaqbsdPApMxOgbr+zfqU1LtWVxdT+83K2NuaLKIOkX7m+bkX0cKxvEkE8TUIehkgy/rwsJKYZDhUc6KyuU37Z5IIokFNYelY4VWPGXPGLvMGdtX2BT8UmpQ8pYfXd/z/Z/DprDti0=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7193020); SRVR:MWHPR21MB0175; 
x-ms-traffictypediagnostic: MWHPR21MB0175:
x-microsoft-antispam-prvs: <MWHPR21MB01750FD9A5B2AD78F844F7C1B6800@MWHPR21MB0175.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(89211679590171)(192374486261705)(189930954265078)(85827821059158)(67672495146484)(100405760836317)(219752817060721)(21748063052155)(17755550239193);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3002001)(10201501046)(3231254)(2018427008)(944501410)(52105095)(93006095)(93001095)(6055026)(6041310)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123562045)(20161123560045)(6072148)(201708071742011); SRVR:MWHPR21MB0175; BCL:0; PCL:0; RULEID:; SRVR:MWHPR21MB0175; 
x-forefront-prvs: 06607E485E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(366004)(346002)(39860400002)(396003)(39380400002)(189003)(199004)(86612001)(478600001)(3280700002)(106356001)(81166006)(3660700001)(4326008)(25786009)(81156014)(8676002)(2906002)(10290500003)(105586002)(6436002)(55016002)(8990500004)(19609705001)(10090500001)(8936002)(2900100001)(54896002)(54906003)(39060400002)(5250100002)(53936002)(110136005)(9686003)(33656002)(97736004)(6246003)(476003)(46003)(316002)(5660300001)(236005)(102836004)(99286004)(6306002)(74316002)(14454004)(186003)(790700001)(7696005)(76176011)(22452003)(11346002)(86362001)(446003)(606006)(59450400001)(53546011)(6116002)(6506007)(7736002)(486006)(68736007)(6346003)(229853002); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR21MB0175; H:MWHPR21MB0638.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pravb@microsoft.com; 
x-microsoft-antispam-message-info: BidrvMVlchJXiV5Lsb6LR5A6NDP0uPJekJMvaI6ywr2Cq0vHzp9KDf1s8HkdwL9ppEAtJw43JVC2DveXlaoqYfG2N4SYov+zV7Cn7yyqaBWouLR0lC18+4XmH+AiSTaTOqZ3IG9eyWTJwnArv4cLZPpjXPLX1JeKNrSGzR9pL77wfX3eVeK0cXX5Yw6tb06x
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_MWHPR21MB06386100B48E17A059B5A04EB6800MWHPR21MB0638namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: bac74528-72d5-4b8f-14c3-08d5afd0c752
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: bac74528-72d5-4b8f-14c3-08d5afd0c752
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 May 2018 02:02:37.2915 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR21MB0175
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/jeXkaebb9pZPGnkuqqilCzv1g1k>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 02:02:45 -0000

--_000_MWHPR21MB06386100B48E17A059B5A04EB6800MWHPR21MB0638namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

V2UgY2FuIGdldCAoMSkgZG9uZSBidXQgSSBkaXNhZ3JlZSB0aGF0IHdlIGNhbiBkZWNvdXBsZSAo
MikuIEl0IGRvZXNu4oCZdCBtYWtlIHNlbnNlIHRvIHJlcXVpcmUgcGVyZm9ybWFuY2Ugb3Zlcmhl
YWQgYWxsIHRoZSB0aW1lIHdpdGggbm8gYmVuZWZpdC4gRm9yIHRoZSBJbnRlcm5ldCwgUE5FIGNh
biBwcmV2ZW50IG9zc2lmaWNhdGlvbiBzbyBpdCBpcyBzZWVuIGFzIGEgcmVhc29uYWJsZSB0cmFk
ZS1vZmYuIEZvciB0aGUgZGF0YWNlbnRlciwgdGhlcmUgaXMgbm8ga25vd24gYmVuZWZpdCwgb25s
eSBjb3N0Lg0KDQpXZSBrbm93IHRoYXQgdGhlcmUgaXMgYSBDUFUgY29zdCwgdGhpcyBpcyBub3Qg
c3BlY3VsYXRpb24uIERvZXNu4oCZdCBtYXR0ZXIgaWYgdGhlIGNvc3QgaXMgMSUgb3IgMTAlLiBI
YXJkd2FyZSBpbXBsZW1lbnRlcnMgaGF2ZSBhbHNvIHJhaXNlZCBjb25jZXJucy4gRXZlcnkgQ1BV
IGN5Y2xlIHdlIHNwZW5kIG9uIHRoaW5ncyB0aGF0IGFkZCBubyB2YWx1ZSB0byB0aGUgdXNlciBz
aG91bGQgYmUgcXVlc3Rpb25lZC4gRXZlcnkgZXh0cmEgaW5zdHJ1Y3Rpb24gd2UgZXhlY3V0ZSBp
biB0aGUgaG90IGRhdGEgcGF0aCBsZWF2ZXMgbGVzcyBDUFUgZm9yIHdvcmtsb2FkcywgYnVybnMg
bW9yZSBwb3dlciBhbmQgbWFrZXMgZm9yIGEgd29yc2UgY29tcGFyaXNvbiB3aXRoIEhUVFBTIG92
ZXIgVENQLiBUaGUgc2FtZSBhcmd1bWVudCBhcyBwcml2YWN5IGhvbGVzIGhvbGRzIGhlcmUg4oCT
IGp1c3QgYmVjYXVzZSB0aGVyZSBhcmUgc29tZSBleGlzdGluZyBwZXJmIGJvdHRsZW5lY2tzIGRv
ZXNu4oCZdCBtZWFuIHdlIGFkZCBtb3JlLCBwYXJ0aWN1bGFybHkgb25lcyB3ZSBjYW5ub3QgbWl0
aWdhdGUuIEkgc2FpZCBpdCBiZWZvcmUgdGhhdCB0aGVyZSBhcmUgbG90cyBvZiB3YXlzIHdlIGNh
biBpbXByb3ZlIFVEUCBwZXJmIGJ1dCBJIGRvbuKAmXQga25vdyBvZiBhbnkgdGVjaG5pcXVlIGZv
ciByZWR1Y2luZyBjcnlwdG8gQ1BVIGNvc3Qgb3RoZXIgdGhhbiBoYXJkd2FyZSBvZmZsb2FkLg0K
DQpUaGUgY29zdCBpcyBjZXJ0YWlubHkgd29ydGggc2F2aW5nIHdpdGggc29tZXRoaW5nIGFzIHNp
bXBsZSBhcyBhIG5lZ290aWF0aW9uIG1lY2hhbmlzbS4gQW0gSSBtaXNzaW5nIHNvbWV0aGluZyBh
Ym91dCBhIHRyYW5zcG9ydCBwYXJhbWV0ZXIgYmVpbmcgY29tcGxpY2F0ZWQgdG8gaW1wbGVtZW50
PyBJbXBsZW1lbnRhdGlvbnMgYXJlIGZyZWUgdG8gc3VwcG9ydCBvbmx5IFBORSBhbmQgbm90IG5l
Z290aWF0ZSBhbnl0aGluZyBlbHNlLiBUaGVyZSBpcyBhY3R1YWxseSBhbiBldmVuIHNpbXBsZXIg
bWVjaGFuaXNtIGlmIGEgdHJhbnNwb3J0IHBhcmFtZXRlciBpcyBkZWVtZWQgYXMgY29zdGx5OiBp
ZiB0aGUgcGVlciBzZW5kcyBQTiA9IDAgaW4gdGhlIENJLCB0aGVuIGl0cyByZXF1ZXN0aW5nIG5v
IFBORSBhbmQgdGhlIHJlY2VpdmVyIGNhbiBjaG9vc2UgdG8gcHJvY2VlZCBvciBkcm9wIGFuZCBm
b3JjZSBUQ1AgZmFsbCBiYWNrLiBUaGlzIHNob3VsZCB0YWtlIG9ubHkgYW4gZXh0cmEgaWYgY2hl
Y2sgb24gdGhlIHJlY2VpdmVyIENJIHByb2Nlc3NpbmcgbG9naWMgdG8gaW1wbGVtZW50LiBJIGFt
IGFzc3VtaW5nIGhlcmUgdGhhdCBQTkUgb24gaW5wdXQgb2YgMCB3aWxsIG5vdCBwcm9kdWNlIDAg
c28gaXTigJlzIGEgc2FmZSBzZW50aW5lbCB2YWx1ZS4NCg0KRnJvbTogSmFuYSBJeWVuZ2FyIFtt
YWlsdG86anJpLmlldGZAZ21haWwuY29tXQ0KU2VudDogVHVlc2RheSwgTWF5IDEsIDIwMTggNToz
NyBQTQ0KVG86IFJvYmVydG8gUGVvbiA8ZmVuaXhAZmIuY29tPg0KQ2M6IFByYXZlZW4gQmFsYXN1
YnJhbWFuaWFuIDxwcmF2YkBtaWNyb3NvZnQuY29tPjsgVGVkIEhhcmRpZSA8dGVkLmlldGZAZ21h
aWwuY29tPjsgU2FseiwgUmljaCA8cnNhbHpAYWthbWFpLmNvbT47IEJlbmphbWluIEthZHVrIDxi
a2FkdWtAYWthbWFpLmNvbT47IElFVEYgUVVJQyBXRyA8cXVpY0BpZXRmLm9yZz4NClN1YmplY3Q6
IFJlOiBbUG90ZW50aWFsIFNwb29mXSBSZTogR2V0dGluZyB0byBjb25zZW5zdXMgb24gcGFja2V0
IG51bWJlciBlbmNyeXB0aW9uDQoNCkknbGwgdHJ5IHRvIHN1bW1hcml6ZSBteSBwb3NpdGlvbiBv
biAjMTA3OS4gSSBzZWUgdHdvIHBvaW50czoNCjEuIFBORSB3aWxsIGhlbHAgYWdhaW5zdCBvc3Np
ZmljYXRpb24gYW5kIGFsc28sIGFsYmVpdCB0byBhIGxpbWl0ZWQgZXh0ZW50LCBsaW5rYWJpbGl0
eS4NCjIuIFBORSBoYXMgYSBDUFUgY29zdC4gV2hpbGUgd2UgY2FuIHNwZWN1bGF0ZSwgd2Ugc3Rp
bGwgZG9uJ3QgKmtub3cqIHdoYXQgdGhpcyBjb3N0IHdpbGwgYmUgaW4gdGhlIGNvbnRleHQgb2Yg
ZGVwbG95bWVudCwgYW5kIHdoZXRoZXIgdGhpcyBjb3N0IHdpbGwgYmUgdGhlIHNob3ctc3RvcHBl
ci4gUE5FJ3MgQ1BVIGNvc3QgbWF5IG9yIG1heSBub3QgYmUgYW1lbGlvcmF0ZWQgYnkgTklDIGlt
cGxlbWVudGF0aW9uLiBXZSBzaG91bGQgYWxsb3cgUE5FIG5lZ290aWFiaWxpdHkgd2hlbiB3ZSBo
YXZlIGVzdGFibGlzaGVkIHRoYXQgdGhpcyBjb3N0IGlzIHdvcnRoIHNhdmluZy4NCg0KTXkgc2Vu
c2UgaXMgdGhhdCB3ZSBhZ3JlZSBvbiAoMSkuIFRoaXMgaXMgd2hhdCAjMTA3OSBpcyBkb2luZywg
c28gd2Ugc2hvdWxkIHNlcGFyYXRlIHRoZSB0d28gcXVlc3Rpb25zIGFuZCBnZXQgKDEpIGRvbmUu
IFdoZXRoZXIgd2UgZG8gKDIpIG9yIG5vdCBpcyBiZWluZyBkaXNjdXNzZWQgb24gdGhpcyB0aHJl
YWQsIGFuZCBJIHRoaW5rIHdlIGNhbiBjb250aW51ZSwgYnV0ICMxMDc5IHNob3VsZCBiZSBpbmRl
cGVuZGVudGx5IHN1Ym1pdHRlZC4NCg0KRldJVywgSSBiZWxpZXZlIHRoYXQgd2Ugd2FudCB0byBp
dGVyYXRlIG9uIHZlcnNpb25zLCBhbmQgdGhhdCB3ZSB3aWxsIHdhbnQgdG8gZ2V0IGEgdjIgb3V0
IGFzIHNvb24gYXMgd2UgaGF2ZSB0aGluZ3MgdG8gZ2V0IGRlcGxveWVkIHRoYXQgbGVmdCBwZW5k
aW5nIGluIHYxLg0KDQoNClRob3VnaHRzIG9uIGludHJhLURDIFFVSUMsIHJlbGF0ZWQgdG8gcG9p
bnQgKDIpIGZvbGxvdzoNCg0KSSBkb24ndCB0aGluayB3ZSdsbCByZWFjaCBhIG1lYW5pbmdmdWwg
ZW5kIHRvIHRoaXMgZGlzY3Vzc2lvbiBieSBnZXR0aW5nIGludG8gc2VjdXJpdHkgZm9yIGludHJh
LURDIHByb3RvY29scy4gSSB1bmRlcnN0YW5kIHRoYXQgdGhlcmUgbWF5IGJlIHNpdHVhdGlvbnMg
d2hlcmUgb25lIG1heSBoYXZlIGZhaXIgY2VydGFpbnR5IGFib3V0IHRoZSBkZXBsb3ltZW50IGNv
bnRleHQgYW5kIGdpdmVuIHRoYXQgdGhlIHNlY3VyaXR5IHRyYWRlb2ZmIGlzbid0IHRoZSBzYW1l
IGFzIGRpc2FibGluZyBUTFMsIHRoZSBiYXIgd2lsbCBiZSBzdWJzdGFudGlhbGx5IGxvd2VyIGZv
ciBkaXNhYmxpbmcgUE5FLg0KDQpPbiBRVUlDIGluIGludHJhLURDIGVudmlyb25tZW50czoNCjEu
IEFzIElnb3Igbm90ZWQsIHRoZSB2YWx1ZSBvZiBRVUlDIGluIHRoZSBpbnRyYS1EQyBlbnZpcm9u
bWVudHMgaXMgdW5jZXJ0YWluLCBhbmQgSSdtIG5vdCB5ZXQgc3VyZSB0aGF0IGNvbXByb21pc2lu
ZyBvbiBQTkUgZm9yIGFuIHVua25vd24gY29zdCBpbiBhbiB1bmNlcnRhaW4gZGVwbG95bWVudCBj
b250ZXh0IGlzIG5lY2Vzc2FyaWx5IHVzZWZ1bC4NCjIuIFNlcGFyYXRlbHksIEkgcmVtYWluIHVu
Y29udmluY2VkLCBiYXNlZCBvbiBteSBleHBlcmllbmNlIHdpdGggdHJ5aW5nIHRvIGdldCBRVUlD
IHVzZWQgZm9yIERDIHRyYW5zcG9ydCwgdGhhdCB0aGlzIGNvc3QgaXMgZ29pbmcgdG8gYmUgYW4g
aW1wb3J0YW50IGZhY3RvciBpbiBRVUlDIGFkb3B0aW9uIHdpdGhpbiBEQ3MuIEkgYWdyZWUgdGhh
dCBDUFUgY29zdCBpcyBhIGZhY3RvciwgYnV0IHRoZXJlIGFyZSBtdWNoIGJpZ2dlciB0aGluZ3Mg
aGVyZSB0aGF0IHdpbGwgbmVlZCBhdHRlbnRpb24gKHNlZ21lbnRhdGlvbiBvZmZsb2FkLCBzbWFs
bGVyIHJlY29yZCBzaXplcywgdXNlcnNwYWNlIGNvc3RzKSB0aGF0IHdpbGwgZG9taW5hdGUgd2Vs
bCBiZWZvcmUgdGhpcyBBRVMgb3BlcmF0aW9uIGJlY29tZXMgYSBmYWN0b3IuIFRoaXMgYWxsIHJl
bWFpbnMgc3BlY3VsYXRpb24gdGhvdWdoLg0KDQpQcmF2ZWVuOiBOb3QgbWFraW5nIFBORSBvcHRp
b25hbCByaWdodCBub3cgZG9lcyBub3QgbWVhbiB3ZSB3b24ndCBkbyBpdC4gSXQganVzdCBtZWFu
cyB0aGF0IGl0J3MgYW4gb3BlbiBxdWVzdGlvbi4gSSdtIG5vdCB5ZXQgY29udmluY2VkIHRoYXQg
aXQncyBhIGRlYmlsaXRhdGluZyBjb3N0IG9yIG9uZSBvZiB0aGUgcHJvdmVyYmlhbCAibWlsbGlv
biBjdXRzIiB0aGF0IHdpbGwga2VlcCBpdCBmcm9tIGdldHRpbmcgZGVwbG95ZWQgaW50cmEtREMu
IFlvdSBhcmUgcmlnaHQgdGhhdCB5b3UnbGwgd2FudCB0byBzdGFuZGFyZGl6ZSBQTkUgbmVnb3Rp
YXRpb24gaWYgeW91IHVzZSBtdWx0aXBsZSBwbGF0Zm9ybXMsIGJ1dCBzdXJlbHkgeW91IHdpbGwg
YmUganVzdCBkb2luZyB0aGlzIGJldHdlZW4gV2luZG93cyBzeXN0ZW1zIGZvciBhIHdoaWxlIGlm
IHlvdSBzdGFydCB1c2luZyBRVUlDIGluc2lkZSB0aGUgREMuIFRoYXQgd291bGQgYmUgYSBncmVh
dCB0aW1lIHRvIHVzZSB2ZXJzaW9uaW5nIHRvIHJ1biB5b3VyIG93biB2ZXJzaW9uIHdpdGhpbiB0
aGUgREMsIGFuZCBjb21wYXJlIHRoZSBjb3N0IHRvIElFVEYgdjEsIGFuZCBzZWUgaWYgaXQgaXMg
d29ydGggcmVtb3ZpbmcgUE5FLiBJIGhvcGUgeW91IGZpbmQgb3RoZXIgY29zdHMgdGhhdCBhcmUg
d29ydGggZWxpbWluYXRpbmcgb3IgY2hhbmdlcyB0aGF0IGFyZSB3b3J0aCBtYWtpbmcgdG8gdGhl
IHByb3RvY29sIHRvbywgYW5kIHRoYXQgdGhleSBhbGwgYmVjb21lIHBhcnQgb2Ygc3RhbmRhcmQg
UVVJQyBhcyBhIGNvbnNlcXVlbmNlLiBCdXQgaW4gdGhlIG1lYW53aGlsZSwgSSBkb24ndCBzZWUg
d2h5IG1ha2luZyBpdCBvcHRpb25hbCBpcyBuZWNlc3NhcnkgcmlnaHQgbm93IHRvIGFkZCBQTkUg
YXQgYWxsLg0KDQpPbiBUdWUsIE1heSAxLCAyMDE4IGF0IDQ6MjIgUE0sIFJvYmVydG8gUGVvbiA8
ZmVuaXhAZmIuY29tPG1haWx0bzpmZW5peEBmYi5jb20+PiB3cm90ZToNCknigJlkIHN1Z2dlc3Qg
d2Ugc3RhcnQgd29ya2luZyBvbiBpdCBub3cuDQpUaGlzIGlzIG9ubHkgcGFydGx5IGEgam9rZSDi
mLoNCi09Ug0KDQpGcm9tOiBRVUlDIDxxdWljLWJvdW5jZXNAaWV0Zi5vcmc8bWFpbHRvOnF1aWMt
Ym91bmNlc0BpZXRmLm9yZz4+IG9uIGJlaGFsZiBvZiBSb2JlcnRvIFBlb24gPGZlbml4QGZiLmNv
bTxtYWlsdG86ZmVuaXhAZmIuY29tPj4NCkRhdGU6IFR1ZXNkYXksIE1heSAxLCAyMDE4IGF0IDQ6
MjEgUE0NClRvOiBQcmF2ZWVuIEJhbGFzdWJyYW1hbmlhbiA8cHJhdmI9NDBtaWNyb3NvZnQuY29t
QGRtYXJjLmlldGYub3JnPG1haWx0bzo0MG1pY3Jvc29mdC5jb21AZG1hcmMuaWV0Zi5vcmc+Piwg
VGVkIEhhcmRpZSA8dGVkLmlldGZAZ21haWwuY29tPG1haWx0bzp0ZWQuaWV0ZkBnbWFpbC5jb20+
Pg0KQ2M6ICJTYWx6LCBSaWNoIiA8cnNhbHpAYWthbWFpLmNvbTxtYWlsdG86cnNhbHpAYWthbWFp
LmNvbT4+LCBCZW5qYW1pbiBLYWR1ayA8YmthZHVrQGFrYW1haS5jb208bWFpbHRvOmJrYWR1a0Bh
a2FtYWkuY29tPj4sIElFVEYgUVVJQyBXRyA8cXVpY0BpZXRmLm9yZzxtYWlsdG86cXVpY0BpZXRm
Lm9yZz4+DQpTdWJqZWN0OiBbUG90ZW50aWFsIFNwb29mXSBSZTogR2V0dGluZyB0byBjb25zZW5z
dXMgb24gcGFja2V0IG51bWJlciBlbmNyeXB0aW9uDQoNCll1cC4gSSBrbm93Lg0KUHJpc20gd2Fz
IGV5ZS1vcGVuaW5nIHBhcnRpYWxseSBiZWNhdXNlIG9mIHRoZSBmYWN0IHRoYXQgdGhlIHBhY2tl
dHMgd2VyZSBub3QgZ29pbmcgYWNyb3NzIHRoZSBpbnRlcm5ldCwgYnV0IHJhdGhlciB3aXRoaW4g
YSBzZWN1cmUgbmV0d29yay4NCg0KSSBiZWxpZXZlIHRoYXQgb3NzaWZpY2F0aW9uIGFsb25lIGlz
IGEgZ29vZCBlbm91Z2ggcmVhc29uIHRvIGRvIFBORS4NClRoZSBjaGVycnkgZm9yIG1lIGlzIHRo
YXQgaXQsIGFsb25nIHdpdGggb3RoZXIgYWN0aW9ucy9taXRpZ2F0aW9ucywgbWFrZXMgbGlua2Fi
aWxpdHkgbW9yZSBkaWZmaWN1bHQgZm9yIG1hbGljaW91cyBhY3RvcnMuDQpDUklNRSBhbmQgcmVs
YXRlZCB3YXMgZXllLW9wZW5pbmcgYmVjYXVzZSBpdCBleHBvc2VkIHRoZSBwb3dlciBvZiB0aGUg
b2JzZXJ2YWJsZSBzaWRlLWNoYW5uZWwuDQoNCi09Ug0KDQpGcm9tOiBRVUlDIDxxdWljLWJvdW5j
ZXNAaWV0Zi5vcmc8bWFpbHRvOnF1aWMtYm91bmNlc0BpZXRmLm9yZz4+IG9uIGJlaGFsZiBvZiBQ
cmF2ZWVuIEJhbGFzdWJyYW1hbmlhbiA8cHJhdmI9NDBtaWNyb3NvZnQuY29tQGRtYXJjLmlldGYu
b3JnPG1haWx0bzo0MG1pY3Jvc29mdC5jb21AZG1hcmMuaWV0Zi5vcmc+Pg0KRGF0ZTogVHVlc2Rh
eSwgTWF5IDEsIDIwMTggYXQgOTozNSBBTQ0KVG86IFRlZCBIYXJkaWUgPHRlZC5pZXRmQGdtYWls
LmNvbTxtYWlsdG86dGVkLmlldGZAZ21haWwuY29tPj4sIFJvYmVydG8gUGVvbiA8ZmVuaXhAZmIu
Y29tPG1haWx0bzpmZW5peEBmYi5jb20+Pg0KQ2M6ICJTYWx6LCBSaWNoIiA8cnNhbHpAYWthbWFp
LmNvbTxtYWlsdG86cnNhbHpAYWthbWFpLmNvbT4+LCBCZW5qYW1pbiBLYWR1ayA8YmthZHVrQGFr
YW1haS5jb208bWFpbHRvOmJrYWR1a0Bha2FtYWkuY29tPj4sIElFVEYgUVVJQyBXRyA8cXVpY0Bp
ZXRmLm9yZzxtYWlsdG86cXVpY0BpZXRmLm9yZz4+DQpTdWJqZWN0OiBSRTogR2V0dGluZyB0byBj
b25zZW5zdXMgb24gcGFja2V0IG51bWJlciBlbmNyeXB0aW9uDQoNClRoaXMgaXMgbm90IGFib3V0
IHB1dHRpbmcgcGxhaW50ZXh0IGRhdGEgb24gdGhlIG5ldHdvcmssIHRoaXMgaXMgYWJvdXQgbm90
IGFkZGluZyBQTkUgd2hpY2ggaXMgaW50ZW5kZWQgZm9yIHByZXZlbnRpbmcgb3NzaWZpY2F0aW9u
LiBTbyBJIGRvbuKAmXQgdW5kZXJzdGFuZCB3aGF0IHRoZSB0cnVzdCBpc3N1ZSBiZWluZyByZWZl
cnJlZCB0byBpcyBpbiBjYXNlIG9mIHRoZSByYXJlIG1pc2NvbmZpZy4NCg0KV2l0aGluIGEgREMg
c2V2ZXJhbCB0aGluZ3MgYXJlIGRpZmZlcmVudCDigJMgdGhlIGRlcGxveW1lbnQgbWF5IG5lZWQg
ZGlmZmVyZW50IGNvbmdlc3Rpb24gY29udHJvbCBsaWtlIERDVENQLCBkaWZmZXJlbnQgc2V0dGlu
Z3MgZm9yIHZhcmlvdXMgdHJhbnNwb3J0IHBhcmFtZXRlcnMgKGxpa2UgbWlucnRvIGFuZCBtYXgg
QUNLIGRlbGF5KSwgbGFyZ2VyIGZsb3cgY29udHJvbCB3aW5kb3cgZXRjLiBUaGlzIGlzIHRydWUg
Zm9yIFRDUCB0b2RheS4gVGhlIG91dCBvZiBib3ggZGVmYXVsdCB1c2VzIHRoZSBoYW5kc2hha2Ug
UlRUIHRvIG1ha2UgYSBkZXRlcm1pbmF0aW9uIG9mIHdoYXTigJlzIGludHJhLURDIGJ1dCB0aGVy
ZSBpcyByaWNoIGNvbmZpZ3VyYXRpb24gdG8gb3ZlcnJpZGUgdGhlIGRlZmF1bHQgYW5kIHNldCBp
dCBiYXNlZCBvbiA0LXR1cGxlIGZpbHRlcnMuDQoNCkFuZCB0aGVyZSB3b3JrbG9hZHMgbGlrZSBj
bG91ZCBzdG9yYWdlIGFuZCBsaXZlIG1pZ3JhdGlvbiB0aGF0IGFyZSBieSB2aXJ0dWUgb2YgZGVw
bG95bWVudCBpbnRyYS1EQy4gVGhlc2UgY2Fubm90IGJlIGxvYWQgc2hpZnRlZCBhcyB0aGV5IHVz
ZSBwcml2YXRlIElQIGFkZHJlc3Mgc3BhY2UuDQoNCkZyb206IFRlZCBIYXJkaWUgW21haWx0bzp0
ZWQuaWV0ZkBnbWFpbC5jb208bWFpbHRvOnRlZC5pZXRmQGdtYWlsLmNvbT5dDQpTZW50OiBUdWVz
ZGF5LCBNYXkgMSwgMjAxOCA4OjU1IEFNDQpUbzogUm9iZXJ0byBQZW9uIDxmZW5peEBmYi5jb208
bWFpbHRvOmZlbml4QGZiLmNvbT4+DQpDYzogU2FseiwgUmljaCA8cnNhbHpAYWthbWFpLmNvbTxt
YWlsdG86cnNhbHpAYWthbWFpLmNvbT4+OyBCZW5qYW1pbiBLYWR1ayA8YmthZHVrQGFrYW1haS5j
b208bWFpbHRvOmJrYWR1a0Bha2FtYWkuY29tPj47IFByYXZlZW4gQmFsYXN1YnJhbWFuaWFuIDxw
cmF2YkBtaWNyb3NvZnQuY29tPG1haWx0bzpwcmF2YkBtaWNyb3NvZnQuY29tPj47IElFVEYgUVVJ
QyBXRyA8cXVpY0BpZXRmLm9yZzxtYWlsdG86cXVpY0BpZXRmLm9yZz4+DQpTdWJqZWN0OiBSZTog
R2V0dGluZyB0byBjb25zZW5zdXMgb24gcGFja2V0IG51bWJlciBlbmNyeXB0aW9uDQoNCk9uIFR1
ZSwgTWF5IDEsIDIwMTggYXQgODoxMyBBTSwgUm9iZXJ0byBQZW9uIDxmZW5peEBmYi5jb208bWFp
bHRvOmZlbml4QGZiLmNvbT4+IHdyb3RlOg0KQWxzbywgUHJpc20uDQoNCi09Ug0KDQoNCg0KVGhh
dCdzIGEgbGl0dGxlIG1vcmUgc3VjY2luY3QgdGhhbiBJIHdvdWxkIGJlLCBidXQgeWVzLiAgSG93
IGRvZXMgYW4gYXBwbGljYXRpb24ga25vdyB0aGF0IHRoZSBmbG93IGl0IGlzIGluaXRpYXRpbmcg
d2lsbCB0cmF2ZXJzZSBhIHRvcG9sb2d5IHRoYXQgaXMgZGVlbWVkIHRvIGJlIHdpdGhpbiBhIGNv
bnRyb2xsZWQgZW52aXJvbm1lbnQ/ICBZb3UgY2FuIHNheSAiY29uZmlndXJhdGlvbiIgYnV0IEkg
ZmVhciBpdCB3aWxsIHR1cm4gdXAgb24gYSBwb3N0LWl0ICA8aHR0cHM6Ly9uYTAxLnNhZmVsaW5r
cy5wcm90ZWN0aW9uLm91dGxvb2suY29tLz91cmw9aHR0cHMlM0ElMkYlMkZ1cmxkZWZlbnNlLnBy
b29mcG9pbnQuY29tJTJGdjIlMkZ1cmwlM0Z1JTNEaHR0cHMtM0FfX25hMDEuc2FmZWxpbmtzLnBy
b3RlY3Rpb24ub3V0bG9vay5jb21fLTNGdXJsLTNEaHR0cHMtMjUzQS0yNTJGLTI1MkZpLmtpbmph
LTJEaW1nLmNvbS0yNTJGZ2F3a2VyLTJEbWVkaWEtMjUyRmltYWdlLTI1MkZ1cGxvYWQtMjUyRnMt
MkQtMkRFZHU2TFB1OS0yRC0yRC0yNTJGYy01RnNjYWxlLTI1MkNmLTVGYXV0by0yNTJDZmwtNUZw
cm9ncmVzc2l2ZS0yNTJDcS01RjgwLTI1MkN3LTVGODAwLTI1MkYxOTR0aGJ0eWVuY3MwanBnLmpw
Zy0yNmRhdGEtM0QwMi0yNTdDMDEtMjU3Q3ByYXZiLTI1NDBtaWNyb3NvZnQuY29tLTI1N0M0ZGE0
NGU4YWMxZGY0NzA4YWQ4ODA4ZDVhZjdiZmNhOC0yNTdDNzJmOTg4YmY4NmYxNDFhZjkxYWIyZDdj
ZDAxMWRiNDctMjU3QzEtMjU3QzEtMjU3QzYzNjYwNzg2OTQxMTI1ODk3Ni0yNnNkYXRhLTNEUHJv
bFNIa2JGMlNnTUgzcWRRTi0yNTJCWkZva1h2c0VCZi0yNTJGM285TWFVbmlsMGc4LTI1M0QtMjZy
ZXNlcnZlZC0zRDAlMjZkJTNERHdNR2FRJTI2YyUzRDVWRDBSVHRObFRoM3ljZDQxYjNNVXclMjZy
JTNEQzBzVW8tTEZOQmFZZnlvYUNzZjZUQSUyNm0lM0RUdVZmenlwby1DWkxvNTIybGdNUnJMcEt4
Y0ZhSHZXOWtkTlNJNTdsWFQwJTI2cyUzREJ5MmRfdG83WHpMRWdBTDNPcjljWmMyQXlreWUtUFpF
ZW5GUUR2aUFVbHclMjZlJTNEJmRhdGE9MDIlN0MwMSU3Q3ByYXZiJTQwbWljcm9zb2Z0LmNvbSU3
Q2M1MGY5MWJjM2VjNzQ0NTQ0MWRlMDhkNWFmYzRkNzllJTdDNzJmOTg4YmY4NmYxNDFhZjkxYWIy
ZDdjZDAxMWRiNDclN0MxJTdDMCU3QzYzNjYwODE4MjMzNTYzMzI4MiZzZGF0YT0lMkY2SkVidUNu
bFdiaVVZOHVhRXNPR2RHTldQc2IyS1ZPaVZLSDBVZ2RVOFUlM0QmcmVzZXJ2ZWQ9MD4gaWYgeW91
IGRvLiAgTG9hZHMgc2hpZnQsIHJlc291cmNlcyBtb3ZlLCBhbmQgc3VkZGVubHkgeW91IGZpbmQg
dGhhdCBob3N0IHdoaWNoIHVzZWQgdG8gYmUgaW4gdGhlIHNhbWUgcmFjaywgYmVpbmcgZG93biwg
aGFzIGxvYWQtc2hpZnRlZCB0byB0aGUgbmV4dCBpbnN0YW5jZSwgIGluIGEgZGF0YWNlbnRlciA1
MDAgbWlsZXMgYXdheSBhY3Jvc3MgYSB2ZXJ5IGRpZmZlcmVudCBuZXR3b3JrLg0KDQpNYW55IG1v
ZGVybiBkZXBsb3ltZW50cyBhcmUgYWxzbyBpbiBzb21lb25lIGVsc2UncyBkYXRhIGNlbnRlciwg
c28gc2F5aW5nICJEYXRhIGNlbnRlciBuZXR3b3JrcyIgZG9lc24ndCBzYXkgbXVjaCBhYm91dCB3
aHkgeW91J3JlIHRydXN0aW5nIHRoZSBuZXR3b3JrIGluc2lkZS4NClRlZA0KDQpTZW50IHZpYSB0
aGUgU2Ftc3VuZyBHYWxheHkgUzcsIGFuIEFUJlQgNEcgTFRFIHNtYXJ0cGhvbmUNCg0KDQotLS0t
LS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tDQpGcm9tOiAiU2FseiwgUmljaCIgPHJzYWx6
PTQwYWthbWFpLmNvbUBkbWFyYy5pZXRmLm9yZzxtYWlsdG86NDBha2FtYWkuY29tQGRtYXJjLmll
dGYub3JnPj4NCkRhdGU6IDUvMS8xOCA1OjI1IEFNIChHTVQtMDg6MDApDQpUbzogQmVuamFtaW4g
S2FkdWsgPGJrYWR1az00MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmc8bWFpbHRvOjQwYWthbWFp
LmNvbUBkbWFyYy5pZXRmLm9yZz4+LCBQcmF2ZWVuIEJhbGFzdWJyYW1hbmlhbiA8cHJhdmI9NDBt
aWNyb3NvZnQuY29tQGRtYXJjLmlldGYub3JnPG1haWx0bzo0MG1pY3Jvc29mdC5jb21AZG1hcmMu
aWV0Zi5vcmc+Pg0KQ2M6IElFVEYgUVVJQyBXRyA8cXVpY0BpZXRmLm9yZzxtYWlsdG86cXVpY0Bp
ZXRmLm9yZz4+DQpTdWJqZWN0OiBSZTogR2V0dGluZyB0byBjb25zZW5zdXMgb24gcGFja2V0IG51
bWJlciBlbmNyeXB0aW9uDQoNCiAgICA+IEkgZGlzYWdyZWUgdGhhdCB3ZSBuZWVkIGFueSBtb3Jl
IGRhdGEgZm9yIG5vdCBkb2luZyBQTkUgaW4gdGhlIGRhdGFjZW50ZXIuIFdoeSB3b3VsZCB3ZSBh
ZGQgYW4gZXh0cmEgZW5jcnlwdC1kZWNyeXB0IHN0ZXAgZm9yIG5vIG9idmlvdXMgYmVuZWZpdD8N
Cg0KSSBhbSBjb25jZXJuZWQgdGhhdCBwZW9wbGUgd2lsbCBtaXMtaW50ZXJwcmV0IHRoZSBtZWFu
aW5nIG9mIGEgZGF0YWNlbnRlciwgYW5kIHRoaW5rIHRoYXQgYSBidW5jaCBvZiBzZXJ2ZXJzLCBv
ciBldmVuIGEgcmFjaywgaW4gYW4gb3BlbiBjb2xvIHNwYWNlIGlzIGEgImRhdGFjZW50ZXIuIiAg
Q29tcHV0ZXJzIGtlZXAgZ2V0dGluZyBmYXN0ZXIuDQoNCg0K

--_000_MWHPR21MB06386100B48E17A059B5A04EB6800MWHPR21MB0638namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiU2Vnb2UgVUkgRW1vamkiOw0KCXBhbm9z
ZS0xOjIgMTEgNSAyIDQgMiA0IDIgMiAzO30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1z
b05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowaW47DQoJbWFy
Z2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNh
bGlicmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5
bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5l
O30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJp
b3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0K
cC5tc29ub3JtYWwwLCBsaS5tc29ub3JtYWwwLCBkaXYubXNvbm9ybWFsMA0KCXttc28tc3R5bGUt
bmFtZTptc29ub3JtYWw7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0
OjBpbjsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowaW47DQoJ
Zm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpz
cGFuLkVtYWlsU3R5bGUxOA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWls
eToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCnNwYW4uRW1haWxT
dHlsZTE5DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLWNvbXBvc2U7DQoJZm9udC1mYW1pbHk6
IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVmYXVs
dA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
c2Fucy1zZXJpZjt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJ
bWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFn
ZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxv
OnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtl
bmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJl
ZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0
PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJs
dWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPldlIGNhbiBnZXQgKDEpIGRvbmUgYnV0IEkgZGlzYWdyZWUgdGhhdCB3ZSBj
YW4gZGVjb3VwbGUgKDIpLiBJdCBkb2VzbuKAmXQgbWFrZSBzZW5zZSB0byByZXF1aXJlIHBlcmZv
cm1hbmNlIG92ZXJoZWFkIGFsbCB0aGUgdGltZSB3aXRoIG5vIGJlbmVmaXQuIEZvciB0aGUgSW50
ZXJuZXQsIFBORSBjYW4gcHJldmVudCBvc3NpZmljYXRpb24gc28gaXQgaXMgc2VlbiBhcyBhIHJl
YXNvbmFibGUgdHJhZGUtb2ZmLiBGb3INCiB0aGUgZGF0YWNlbnRlciwgdGhlcmUgaXMgbm8ga25v
d24gYmVuZWZpdCwgb25seSBjb3N0LiA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+V2Uga25vdyB0
aGF0IHRoZXJlIGlzIGEgQ1BVIGNvc3QsIHRoaXMgaXMgbm90IHNwZWN1bGF0aW9uLiBEb2VzbuKA
mXQgbWF0dGVyIGlmIHRoZSBjb3N0IGlzIDElIG9yIDEwJS4gSGFyZHdhcmUgaW1wbGVtZW50ZXJz
IGhhdmUgYWxzbyByYWlzZWQgY29uY2VybnMuIEV2ZXJ5IENQVSBjeWNsZSB3ZSBzcGVuZCBvbiB0
aGluZ3MgdGhhdCBhZGQgbm8gdmFsdWUgdG8gdGhlIHVzZXIgc2hvdWxkIGJlIHF1ZXN0aW9uZWQu
DQogRXZlcnkgZXh0cmEgaW5zdHJ1Y3Rpb24gd2UgZXhlY3V0ZSBpbiB0aGUgaG90IGRhdGEgcGF0
aCBsZWF2ZXMgbGVzcyBDUFUgZm9yIHdvcmtsb2FkcywgYnVybnMgbW9yZSBwb3dlciBhbmQgbWFr
ZXMgZm9yIGEgd29yc2UgY29tcGFyaXNvbiB3aXRoIEhUVFBTIG92ZXIgVENQLiBUaGUgc2FtZSBh
cmd1bWVudCBhcyBwcml2YWN5IGhvbGVzIGhvbGRzIGhlcmUg4oCTIGp1c3QgYmVjYXVzZSB0aGVy
ZSBhcmUgc29tZSBleGlzdGluZyBwZXJmIGJvdHRsZW5lY2tzDQogZG9lc27igJl0IG1lYW4gd2Ug
YWRkIG1vcmUsIHBhcnRpY3VsYXJseSBvbmVzIHdlIGNhbm5vdCBtaXRpZ2F0ZS4gSSBzYWlkIGl0
IGJlZm9yZSB0aGF0IHRoZXJlIGFyZSBsb3RzIG9mIHdheXMgd2UgY2FuIGltcHJvdmUgVURQIHBl
cmYgYnV0IEkgZG9u4oCZdCBrbm93IG9mIGFueSB0ZWNobmlxdWUgZm9yIHJlZHVjaW5nIGNyeXB0
byBDUFUgY29zdCBvdGhlciB0aGFuIGhhcmR3YXJlIG9mZmxvYWQuPG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPlRoZSBjb3N0IGlzIGNlcnRhaW5seSB3b3J0aCBzYXZpbmcgd2l0aCBzb21ldGhpbmcg
YXMgc2ltcGxlIGFzIGEgbmVnb3RpYXRpb24gbWVjaGFuaXNtLiBBbSBJIG1pc3Npbmcgc29tZXRo
aW5nIGFib3V0IGEgdHJhbnNwb3J0IHBhcmFtZXRlciBiZWluZyBjb21wbGljYXRlZCB0byBpbXBs
ZW1lbnQ/IEltcGxlbWVudGF0aW9ucyBhcmUgZnJlZSB0byBzdXBwb3J0IG9ubHkgUE5FIGFuZCBu
b3QgbmVnb3RpYXRlIGFueXRoaW5nDQogZWxzZS4gVGhlcmUgaXMgYWN0dWFsbHkgYW4gZXZlbiBz
aW1wbGVyIG1lY2hhbmlzbSBpZiBhIHRyYW5zcG9ydCBwYXJhbWV0ZXIgaXMgZGVlbWVkIGFzIGNv
c3RseTogaWYgdGhlIHBlZXIgc2VuZHMgUE4gPSAwIGluIHRoZSBDSSwgdGhlbiBpdHMgcmVxdWVz
dGluZyBubyBQTkUgYW5kIHRoZSByZWNlaXZlciBjYW4gY2hvb3NlIHRvIHByb2NlZWQgb3IgZHJv
cCBhbmQgZm9yY2UgVENQIGZhbGwgYmFjay4gVGhpcyBzaG91bGQgdGFrZSBvbmx5IGFuDQogZXh0
cmEgaWYgY2hlY2sgb24gdGhlIHJlY2VpdmVyIENJIHByb2Nlc3NpbmcgbG9naWMgdG8gaW1wbGVt
ZW50LiBJIGFtIGFzc3VtaW5nIGhlcmUgdGhhdCBQTkUgb24gaW5wdXQgb2YgMCB3aWxsIG5vdCBw
cm9kdWNlIDAgc28gaXTigJlzIGEgc2FmZSBzZW50aW5lbCB2YWx1ZS4NCjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48Yj5Gcm9tOjwvYj4gSmFuYSBJeWVuZ2FyIFttYWlsdG86anJpLmlldGZAZ21h
aWwuY29tXSA8YnI+DQo8Yj5TZW50OjwvYj4gVHVlc2RheSwgTWF5IDEsIDIwMTggNTozNyBQTTxi
cj4NCjxiPlRvOjwvYj4gUm9iZXJ0byBQZW9uICZsdDtmZW5peEBmYi5jb20mZ3Q7PGJyPg0KPGI+
Q2M6PC9iPiBQcmF2ZWVuIEJhbGFzdWJyYW1hbmlhbiAmbHQ7cHJhdmJAbWljcm9zb2Z0LmNvbSZn
dDs7IFRlZCBIYXJkaWUgJmx0O3RlZC5pZXRmQGdtYWlsLmNvbSZndDs7IFNhbHosIFJpY2ggJmx0
O3JzYWx6QGFrYW1haS5jb20mZ3Q7OyBCZW5qYW1pbiBLYWR1ayAmbHQ7YmthZHVrQGFrYW1haS5j
b20mZ3Q7OyBJRVRGIFFVSUMgV0cgJmx0O3F1aWNAaWV0Zi5vcmcmZ3Q7PGJyPg0KPGI+U3ViamVj
dDo8L2I+IFJlOiBbUG90ZW50aWFsIFNwb29mXSBSZTogR2V0dGluZyB0byBjb25zZW5zdXMgb24g
cGFja2V0IG51bWJlciBlbmNyeXB0aW9uPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5J
J2xsIHRyeSB0byBzdW1tYXJpemUgbXkgcG9zaXRpb24gb24gIzEwNzkuIEkgc2VlIHR3byBwb2lu
dHM6PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+MS4gUE5FIHdp
bGwgaGVscCBhZ2FpbnN0IG9zc2lmaWNhdGlvbiBhbmQgYWxzbywgYWxiZWl0IHRvIGEgbGltaXRl
ZCBleHRlbnQsIGxpbmthYmlsaXR5LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+Mi4gUE5FIGhhcyBhIENQVSBjb3N0LiBXaGlsZSB3ZSBjYW4gc3Bl
Y3VsYXRlLCB3ZSBzdGlsbCBkb24ndCAqa25vdyogd2hhdCB0aGlzIGNvc3Qgd2lsbCBiZSBpbiB0
aGUgY29udGV4dCBvZiBkZXBsb3ltZW50LCBhbmQgd2hldGhlciB0aGlzIGNvc3Qgd2lsbCBiZSB0
aGUgc2hvdy1zdG9wcGVyLg0KPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjIyMjIyO2JhY2tncm91bmQ6
d2hpdGUiPg0KUE5FJ3MgQ1BVIGNvc3QgbWF5IG9yIG1heSBub3QgYmUgYW1lbGlvcmF0ZWQgYnkg
TklDIGltcGxlbWVudGF0aW9uLiBXZSBzaG91bGQgYWxsb3cgUE5FIG5lZ290aWFiaWxpdHkgd2hl
biB3ZSBoYXZlIGVzdGFibGlzaGVkIHRoYXQgdGhpcyBjb3N0IGlzIHdvcnRoIHNhdmluZy4mbmJz
cDs8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPk15IHNlbnNlIGlzIHRoYXQgd2UgYWdyZWUgb24gKDEpLiBUaGlzIGlzIHdoYXQgIzEw
NzkgaXMgZG9pbmcsIHNvIHdlIHNob3VsZCBzZXBhcmF0ZSB0aGUgdHdvIHF1ZXN0aW9ucyBhbmQg
Z2V0ICgxKSBkb25lLiBXaGV0aGVyIHdlIGRvICgyKSBvciBub3QgaXMgYmVpbmcgZGlzY3Vzc2Vk
IG9uIHRoaXMgdGhyZWFkLCBhbmQgSSB0aGluayB3ZSBjYW4gY29udGludWUsIGJ1dCAjMTA3OSBz
aG91bGQgYmUgaW5kZXBlbmRlbnRseQ0KIHN1Ym1pdHRlZC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+RldJVywmbmJzcDs8c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOiMyMjIyMjI7YmFja2dyb3VuZDp3aGl0ZSI+SSBiZWxpZXZlIHRoYXQgd2Ugd2FudCB0
byBpdGVyYXRlIG9uIHZlcnNpb25zLCBhbmQgdGhhdCB3ZSB3aWxsIHdhbnQgdG8gZ2V0IGEgdjIg
b3V0IGFzIHNvb24gYXMgd2UgaGF2ZSB0aGluZ3MgdG8gZ2V0IGRlcGxveWVkIHRoYXQgbGVmdA0K
IHBlbmRpbmcgaW4gdjEuPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRob3VnaHRzIG9uIGludHJhLURDIFFVSUMsIHJlbGF0ZWQg
dG8gcG9pbnQgKDIpIGZvbGxvdzo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjIyMjIyO2JhY2tncm91bmQ6
d2hpdGUiPkkgZG9uJ3QgdGhpbmsgd2UnbGwgcmVhY2ggYSBtZWFuaW5nZnVsIGVuZCB0byB0aGlz
IGRpc2N1c3Npb24gYnkgZ2V0dGluZyBpbnRvIHNlY3VyaXR5IGZvciBpbnRyYS1EQyBwcm90b2Nv
bHMuJm5ic3A7PC9zcGFuPkkgdW5kZXJzdGFuZCB0aGF0IHRoZXJlIG1heQ0KIGJlIHNpdHVhdGlv
bnMgd2hlcmUgb25lIG1heSBoYXZlIGZhaXIgY2VydGFpbnR5IGFib3V0IHRoZSBkZXBsb3ltZW50
IGNvbnRleHQgYW5kIGdpdmVuIHRoYXQgdGhlIHNlY3VyaXR5IHRyYWRlb2ZmIGlzbid0IHRoZSBz
YW1lIGFzIGRpc2FibGluZyBUTFMsIHRoZSBiYXIgd2lsbCBiZSBzdWJzdGFudGlhbGx5IGxvd2Vy
IGZvciBkaXNhYmxpbmcgUE5FLiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4w
cHQ7Zm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMjIyMjIy
Ij5PbiBRVUlDIGluIGludHJhLURDIGVudmlyb25tZW50czombmJzcDs8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjEyLjBwdDtmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlm
O2NvbG9yOiMyMjIyMjIiPjEuIEFzIElnb3Igbm90ZWQsIHRoZSB2YWx1ZSBvZiBRVUlDIGluIHRo
ZSBpbnRyYS1EQyBlbnZpcm9ubWVudHMgaXMgdW5jZXJ0YWluLCBhbmQgSSdtIG5vdCB5ZXQgc3Vy
ZSB0aGF0IGNvbXByb21pc2luZyBvbiBQTkUgZm9yIGFuIHVua25vd24gY29zdCBpbiBhbiB1bmNl
cnRhaW4NCiBkZXBsb3ltZW50IGNvbnRleHQgaXMgbmVjZXNzYXJpbHkgdXNlZnVsLiZuYnNwOzxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1
b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzIyMjIyMiI+Mi4gU2VwYXJhdGVseSwgSSByZW1haW4gdW5j
b252aW5jZWQsIGJhc2VkIG9uIG15IGV4cGVyaWVuY2Ugd2l0aCB0cnlpbmcgdG8gZ2V0IFFVSUMg
dXNlZCBmb3IgREMgdHJhbnNwb3J0LCB0aGF0IHRoaXMgY29zdCBpcyBnb2luZyB0byBiZSBhbiBp
bXBvcnRhbnQgZmFjdG9yIGluDQogUVVJQyBhZG9wdGlvbiB3aXRoaW4gRENzLiBJIGFncmVlIHRo
YXQgQ1BVIGNvc3QgaXMgYSBmYWN0b3IsIGJ1dCB0aGVyZSBhcmUgbXVjaCBiaWdnZXIgdGhpbmdz
IGhlcmUgdGhhdCB3aWxsIG5lZWQgYXR0ZW50aW9uIChzZWdtZW50YXRpb24gb2ZmbG9hZCwgc21h
bGxlciByZWNvcmQgc2l6ZXMsIHVzZXJzcGFjZSBjb3N0cykgdGhhdCB3aWxsIGRvbWluYXRlIHdl
bGwgYmVmb3JlIHRoaXMgQUVTIG9wZXJhdGlvbiBiZWNvbWVzIGEgZmFjdG9yLiBUaGlzDQogYWxs
IHJlbWFpbnMgc3BlY3VsYXRpb24gdGhvdWdoLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5QcmF2ZWVuOiBOb3QgbWFr
aW5nIFBORSBvcHRpb25hbCByaWdodCBub3cgZG9lcyBub3QgbWVhbiB3ZSB3b24ndCBkbyBpdC4g
SXQganVzdCBtZWFucyB0aGF0IGl0J3MgYW4gb3BlbiBxdWVzdGlvbi4gSSdtIG5vdCB5ZXQgY29u
dmluY2VkIHRoYXQgaXQncyBhIGRlYmlsaXRhdGluZyBjb3N0IG9yIG9uZSBvZiB0aGUgcHJvdmVy
YmlhbCAmcXVvdDttaWxsaW9uIGN1dHMmcXVvdDsgdGhhdCB3aWxsIGtlZXAgaXQgZnJvbSBnZXR0
aW5nDQogZGVwbG95ZWQgaW50cmEtREMuIFlvdSBhcmUgcmlnaHQgdGhhdCB5b3UnbGwgd2FudCB0
byBzdGFuZGFyZGl6ZSBQTkUgbmVnb3RpYXRpb24gaWYgeW91IHVzZSBtdWx0aXBsZSBwbGF0Zm9y
bXMsIGJ1dCBzdXJlbHkgeW91IHdpbGwgYmUganVzdCBkb2luZyB0aGlzIGJldHdlZW4gV2luZG93
cyBzeXN0ZW1zIGZvciBhIHdoaWxlIGlmIHlvdSBzdGFydCB1c2luZyBRVUlDIGluc2lkZSB0aGUg
REMuIFRoYXQgd291bGQgYmUgYSBncmVhdCB0aW1lIHRvDQogdXNlIHZlcnNpb25pbmcgdG8gcnVu
IHlvdXIgb3duIHZlcnNpb24gd2l0aGluIHRoZSBEQywgYW5kIGNvbXBhcmUgdGhlIGNvc3QgdG8g
SUVURiB2MSwgYW5kIHNlZSBpZiBpdCBpcyB3b3J0aCByZW1vdmluZyBQTkUuIEkgaG9wZSB5b3Ug
ZmluZCBvdGhlciBjb3N0cyB0aGF0IGFyZSB3b3J0aCBlbGltaW5hdGluZyBvciBjaGFuZ2VzIHRo
YXQgYXJlIHdvcnRoIG1ha2luZyB0byB0aGUgcHJvdG9jb2wgdG9vLCBhbmQgdGhhdCB0aGV5IGFs
bCBiZWNvbWUNCiBwYXJ0IG9mIHN0YW5kYXJkIFFVSUMgYXMgYSBjb25zZXF1ZW5jZS4gQnV0IGlu
IHRoZSBtZWFud2hpbGUsIEkgZG9uJ3Qgc2VlIHdoeSBtYWtpbmcgaXQgb3B0aW9uYWwgaXMgbmVj
ZXNzYXJ5IHJpZ2h0IG5vdyB0byBhZGQgUE5FIGF0IGFsbC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gVHVlLCBNYXkgMSwgMjAxOCBhdCA0
OjIyIFBNLCBSb2JlcnRvIFBlb24gJmx0OzxhIGhyZWY9Im1haWx0bzpmZW5peEBmYi5jb20iIHRh
cmdldD0iX2JsYW5rIj5mZW5peEBmYi5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4N
CjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0ND
IDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2lu
LXJpZ2h0OjBpbiI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+SeKAmWQg
c3VnZ2VzdCB3ZSBzdGFydCB3b3JraW5nIG9uIGl0IG5vdy48bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0byI+VGhpcyBpcyBvbmx5IHBhcnRseSBhIGpva2UNCjxzcGFuIHN0eWxl
PSJmb250LWZhbWlseTomcXVvdDtTZWdvZSBVSSBFbW9qaSZxdW90OyxzYW5zLXNlcmlmIj7imLo8
L3NwYW4+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPi09UjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxk
aXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRk
aW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PGI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Y29sb3I6YmxhY2siPkZyb206DQo8L3NwYW4+PC9iPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2NvbG9yOmJsYWNrIj5RVUlDICZsdDs8YSBocmVm
PSJtYWlsdG86cXVpYy1ib3VuY2VzQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+cXVpYy1ib3Vu
Y2VzQGlldGYub3JnPC9hPiZndDsgb24gYmVoYWxmIG9mIFJvYmVydG8gUGVvbiAmbHQ7PGEgaHJl
Zj0ibWFpbHRvOmZlbml4QGZiLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmZlbml4QGZiLmNvbTwvYT4m
Z3Q7PGJyPg0KPGI+RGF0ZTogPC9iPlR1ZXNkYXksIE1heSAxLCAyMDE4IGF0IDQ6MjEgUE08YnI+
DQo8Yj5UbzogPC9iPlByYXZlZW4gQmFsYXN1YnJhbWFuaWFuICZsdDtwcmF2Yj08YSBocmVmPSJt
YWlsdG86NDBtaWNyb3NvZnQuY29tQGRtYXJjLmlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+NDBt
aWNyb3NvZnQuY29tQGRtYXJjLmlldGYub3JnPC9hPiZndDssIFRlZCBIYXJkaWUgJmx0OzxhIGhy
ZWY9Im1haWx0bzp0ZWQuaWV0ZkBnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj50ZWQuaWV0ZkBn
bWFpbC5jb208L2E+Jmd0Ozxicj4NCjxiPkNjOiA8L2I+JnF1b3Q7U2FseiwgUmljaCZxdW90OyAm
bHQ7PGEgaHJlZj0ibWFpbHRvOnJzYWx6QGFrYW1haS5jb20iIHRhcmdldD0iX2JsYW5rIj5yc2Fs
ekBha2FtYWkuY29tPC9hPiZndDssIEJlbmphbWluIEthZHVrICZsdDs8YSBocmVmPSJtYWlsdG86
YmthZHVrQGFrYW1haS5jb20iIHRhcmdldD0iX2JsYW5rIj5ia2FkdWtAYWthbWFpLmNvbTwvYT4m
Z3Q7LCBJRVRGIFFVSUMgV0cgJmx0OzxhIGhyZWY9Im1haWx0bzpxdWljQGlldGYub3JnIiB0YXJn
ZXQ9Il9ibGFuayI+cXVpY0BpZXRmLm9yZzwvYT4mZ3Q7PGJyPg0KPGI+U3ViamVjdDogPC9iPltQ
b3RlbnRpYWwgU3Bvb2ZdIFJlOiBHZXR0aW5nIHRvIGNvbnNlbnN1cyBvbiBwYWNrZXQgbnVtYmVy
IGVuY3J5cHRpb248L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1i
b3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0
b20tYWx0OmF1dG8iPll1cC4gSSBrbm93LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvIj5QcmlzbSB3YXMgZXllLW9wZW5pbmcgcGFydGlhbGx5IGJlY2F1c2Ugb2YgdGhlIGZh
Y3QgdGhhdCB0aGUgcGFja2V0cyB3ZXJlIG5vdCBnb2luZyBhY3Jvc3MgdGhlIGludGVybmV0LCBi
dXQgcmF0aGVyIHdpdGhpbiBhIHNlY3VyZSBuZXR3b3JrLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+SSBiZWxpZXZlIHRoYXQgb3NzaWZpY2F0aW9uIGFsb25lIGlzIGEgZ29vZCBlbm91Z2gg
cmVhc29uIHRvIGRvIFBORS48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
VGhlIGNoZXJyeSBmb3IgbWUgaXMgdGhhdCBpdCwgYWxvbmcgd2l0aCBvdGhlciBhY3Rpb25zL21p
dGlnYXRpb25zLCBtYWtlcyBsaW5rYWJpbGl0eSBtb3JlIGRpZmZpY3VsdCBmb3IgbWFsaWNpb3Vz
IGFjdG9ycy48YnI+DQpDUklNRSBhbmQgcmVsYXRlZCB3YXMgZXllLW9wZW5pbmcgYmVjYXVzZSBp
dCBleHBvc2VkIHRoZSBwb3dlciBvZiB0aGUgb2JzZXJ2YWJsZSBzaWRlLWNoYW5uZWwuDQo8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PGJyPg0KLT1SPG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPGRpdiBz
dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6
My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48Yj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEyLjBwdDtjb2xvcjpibGFjayI+RnJvbToNCjwvc3Bhbj48L2I+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Y29sb3I6YmxhY2siPlFVSUMgJmx0OzxhIGhyZWY9Im1h
aWx0bzpxdWljLWJvdW5jZXNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5xdWljLWJvdW5jZXNA
aWV0Zi5vcmc8L2E+Jmd0OyBvbiBiZWhhbGYgb2YgUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gJmx0
O3ByYXZiPTxhIGhyZWY9Im1haWx0bzo0MG1pY3Jvc29mdC5jb21AZG1hcmMuaWV0Zi5vcmciIHRh
cmdldD0iX2JsYW5rIj40MG1pY3Jvc29mdC5jb21AZG1hcmMuaWV0Zi5vcmc8L2E+Jmd0Ozxicj4N
CjxiPkRhdGU6IDwvYj5UdWVzZGF5LCBNYXkgMSwgMjAxOCBhdCA5OjM1IEFNPGJyPg0KPGI+VG86
IDwvYj5UZWQgSGFyZGllICZsdDs8YSBocmVmPSJtYWlsdG86dGVkLmlldGZAZ21haWwuY29tIiB0
YXJnZXQ9Il9ibGFuayI+dGVkLmlldGZAZ21haWwuY29tPC9hPiZndDssIFJvYmVydG8gUGVvbiAm
bHQ7PGEgaHJlZj0ibWFpbHRvOmZlbml4QGZiLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmZlbml4QGZi
LmNvbTwvYT4mZ3Q7PGJyPg0KPGI+Q2M6IDwvYj4mcXVvdDtTYWx6LCBSaWNoJnF1b3Q7ICZsdDs8
YSBocmVmPSJtYWlsdG86cnNhbHpAYWthbWFpLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPnJzYWx6QGFr
YW1haS5jb208L2E+Jmd0OywgQmVuamFtaW4gS2FkdWsgJmx0OzxhIGhyZWY9Im1haWx0bzpia2Fk
dWtAYWthbWFpLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmJrYWR1a0Bha2FtYWkuY29tPC9hPiZndDss
IElFVEYgUVVJQyBXRyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnF1aWNAaWV0Zi5vcmciIHRhcmdldD0i
X2JsYW5rIj5xdWljQGlldGYub3JnPC9hPiZndDs8YnI+DQo8Yj5TdWJqZWN0OiA8L2I+UkU6IEdl
dHRpbmcgdG8gY29uc2Vuc3VzIG9uIHBhY2tldCBudW1iZXIgZW5jcnlwdGlvbjwvc3Bhbj48bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PGEgbmFtZT0i
bV8tMTgzNDIwMzY2MjA5MjI5NjE4NV9fTWFpbE9yaWdpbmFsQm9keSI+VGhpcyBpcyBub3QgYWJv
dXQgcHV0dGluZyBwbGFpbnRleHQgZGF0YSBvbiB0aGUgbmV0d29yaywgdGhpcyBpcyBhYm91dCBu
b3QgYWRkaW5nIFBORSB3aGljaCBpcyBpbnRlbmRlZCBmb3IgcHJldmVudGluZyBvc3NpZmljYXRp
b24uDQogU28gSSBkb27igJl0IHVuZGVyc3RhbmQgd2hhdCB0aGUgdHJ1c3QgaXNzdWUgYmVpbmcg
cmVmZXJyZWQgdG8gaXMgaW4gY2FzZSBvZiB0aGUgcmFyZSBtaXNjb25maWcuDQo8L2E+PG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvIj5XaXRoaW4gYSBEQyBzZXZlcmFsIHRoaW5ncyBhcmUgZGlm
ZmVyZW50IOKAkyB0aGUgZGVwbG95bWVudCBtYXkgbmVlZCBkaWZmZXJlbnQgY29uZ2VzdGlvbiBj
b250cm9sIGxpa2UgRENUQ1AsIGRpZmZlcmVudCBzZXR0aW5ncyBmb3IgdmFyaW91cyB0cmFuc3Bv
cnQgcGFyYW1ldGVycyAobGlrZSBtaW5ydG8gYW5kDQogbWF4IEFDSyBkZWxheSksIGxhcmdlciBm
bG93IGNvbnRyb2wgd2luZG93IGV0Yy4gVGhpcyBpcyB0cnVlIGZvciBUQ1AgdG9kYXkuIFRoZSBv
dXQgb2YgYm94IGRlZmF1bHQgdXNlcyB0aGUgaGFuZHNoYWtlIFJUVCB0byBtYWtlIGEgZGV0ZXJt
aW5hdGlvbiBvZiB3aGF04oCZcyBpbnRyYS1EQyBidXQgdGhlcmUgaXMgcmljaCBjb25maWd1cmF0
aW9uIHRvIG92ZXJyaWRlIHRoZSBkZWZhdWx0IGFuZCBzZXQgaXQgYmFzZWQgb24gNC10dXBsZSBm
aWx0ZXJzLg0KPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5BbmQgdGhlcmUgd29ya2xvYWRz
IGxpa2UgY2xvdWQgc3RvcmFnZSBhbmQgbGl2ZSBtaWdyYXRpb24gdGhhdCBhcmUgYnkgdmlydHVl
IG9mIGRlcGxveW1lbnQgaW50cmEtREMuIFRoZXNlIGNhbm5vdCBiZSBsb2FkIHNoaWZ0ZWQgYXMg
dGhleSB1c2UgcHJpdmF0ZSBJUCBhZGRyZXNzIHNwYWNlLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+PGI+RnJvbTo8L2I+IFRlZCBIYXJkaWUgW21haWx0bzo8YSBocmVmPSJtYWlsdG86dGVk
LmlldGZAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+dGVkLmlldGZAZ21haWwuY29tPC9hPl0N
Cjxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCBNYXkgMSwgMjAxOCA4OjU1IEFNPGJyPg0KPGI+
VG86PC9iPiBSb2JlcnRvIFBlb24gJmx0OzxhIGhyZWY9Im1haWx0bzpmZW5peEBmYi5jb20iIHRh
cmdldD0iX2JsYW5rIj5mZW5peEBmYi5jb208L2E+Jmd0Ozxicj4NCjxiPkNjOjwvYj4gU2Fseiwg
UmljaCAmbHQ7PGEgaHJlZj0ibWFpbHRvOnJzYWx6QGFrYW1haS5jb20iIHRhcmdldD0iX2JsYW5r
Ij5yc2FsekBha2FtYWkuY29tPC9hPiZndDs7IEJlbmphbWluIEthZHVrICZsdDs8YSBocmVmPSJt
YWlsdG86YmthZHVrQGFrYW1haS5jb20iIHRhcmdldD0iX2JsYW5rIj5ia2FkdWtAYWthbWFpLmNv
bTwvYT4mZ3Q7OyBQcmF2ZWVuIEJhbGFzdWJyYW1hbmlhbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOnBy
YXZiQG1pY3Jvc29mdC5jb20iIHRhcmdldD0iX2JsYW5rIj5wcmF2YkBtaWNyb3NvZnQuY29tPC9h
PiZndDs7DQogSUVURiBRVUlDIFdHICZsdDs8YSBocmVmPSJtYWlsdG86cXVpY0BpZXRmLm9yZyIg
dGFyZ2V0PSJfYmxhbmsiPnF1aWNAaWV0Zi5vcmc8L2E+Jmd0Ozxicj4NCjxiPlN1YmplY3Q6PC9i
PiBSZTogR2V0dGluZyB0byBjb25zZW5zdXMgb24gcGFja2V0IG51bWJlciBlbmNyeXB0aW9uPG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9w
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+T24gVHVlLCBNYXkgMSwgMjAxOCBhdCA4
OjEzIEFNLCBSb2JlcnRvIFBlb24gJmx0OzxhIGhyZWY9Im1haWx0bzpmZW5peEBmYi5jb20iIHRh
cmdldD0iX2JsYW5rIj5mZW5peEBmYi5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4N
CjxkaXY+DQo8ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0
OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVm
dDo0LjhwdDttYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1yaWdodDowaW47bWFyZ2luLWJvdHRvbTo1
LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPkFsc28s
IFByaXNtLiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+LT1SJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21hcmdpbi1ib3R0b206MTIuMHB0
Ij5UaGF0J3MgYSBsaXR0bGUgbW9yZSBzdWNjaW5jdCB0aGFuIEkgd291bGQgYmUsIGJ1dCB5ZXMu
Jm5ic3A7IEhvdyBkb2VzIGFuIGFwcGxpY2F0aW9uIGtub3cgdGhhdCB0aGUgZmxvdyBpdCBpcyBp
bml0aWF0aW5nIHdpbGwgdHJhdmVyc2UgYSB0b3BvbG9neSB0aGF0IGlzIGRlZW1lZCB0byBiZSB3
aXRoaW4gYSBjb250cm9sbGVkDQogZW52aXJvbm1lbnQ/Jm5ic3A7IFlvdSBjYW4gc2F5ICZxdW90
O2NvbmZpZ3VyYXRpb24mcXVvdDsgYnV0IEkgZmVhciBpdCB3aWxsIHR1cm4gPGEgaHJlZj0iaHR0
cHM6Ly9uYTAxLnNhZmVsaW5rcy5wcm90ZWN0aW9uLm91dGxvb2suY29tLz91cmw9aHR0cHMlM0El
MkYlMkZ1cmxkZWZlbnNlLnByb29mcG9pbnQuY29tJTJGdjIlMkZ1cmwlM0Z1JTNEaHR0cHMtM0Ff
X25hMDEuc2FmZWxpbmtzLnByb3RlY3Rpb24ub3V0bG9vay5jb21fLTNGdXJsLTNEaHR0cHMtMjUz
QS0yNTJGLTI1MkZpLmtpbmphLTJEaW1nLmNvbS0yNTJGZ2F3a2VyLTJEbWVkaWEtMjUyRmltYWdl
LTI1MkZ1cGxvYWQtMjUyRnMtMkQtMkRFZHU2TFB1OS0yRC0yRC0yNTJGYy01RnNjYWxlLTI1MkNm
LTVGYXV0by0yNTJDZmwtNUZwcm9ncmVzc2l2ZS0yNTJDcS01RjgwLTI1MkN3LTVGODAwLTI1MkYx
OTR0aGJ0eWVuY3MwanBnLmpwZy0yNmRhdGEtM0QwMi0yNTdDMDEtMjU3Q3ByYXZiLTI1NDBtaWNy
b3NvZnQuY29tLTI1N0M0ZGE0NGU4YWMxZGY0NzA4YWQ4ODA4ZDVhZjdiZmNhOC0yNTdDNzJmOTg4
YmY4NmYxNDFhZjkxYWIyZDdjZDAxMWRiNDctMjU3QzEtMjU3QzEtMjU3QzYzNjYwNzg2OTQxMTI1
ODk3Ni0yNnNkYXRhLTNEUHJvbFNIa2JGMlNnTUgzcWRRTi0yNTJCWkZva1h2c0VCZi0yNTJGM285
TWFVbmlsMGc4LTI1M0QtMjZyZXNlcnZlZC0zRDAlMjZkJTNERHdNR2FRJTI2YyUzRDVWRDBSVHRO
bFRoM3ljZDQxYjNNVXclMjZyJTNEQzBzVW8tTEZOQmFZZnlvYUNzZjZUQSUyNm0lM0RUdVZmenlw
by1DWkxvNTIybGdNUnJMcEt4Y0ZhSHZXOWtkTlNJNTdsWFQwJTI2cyUzREJ5MmRfdG83WHpMRWdB
TDNPcjljWmMyQXlreWUtUFpFZW5GUUR2aUFVbHclMjZlJTNEJmFtcDtkYXRhPTAyJTdDMDElN0Nw
cmF2YiU0MG1pY3Jvc29mdC5jb20lN0NjNTBmOTFiYzNlYzc0NDU0NDFkZTA4ZDVhZmM0ZDc5ZSU3
QzcyZjk4OGJmODZmMTQxYWY5MWFiMmQ3Y2QwMTFkYjQ3JTdDMSU3QzAlN0M2MzY2MDgxODIzMzU2
MzMyODImYW1wO3NkYXRhPSUyRjZKRWJ1Q25sV2JpVVk4dWFFc09HZEdOV1BzYjJLVk9pVktIMFVn
ZFU4VSUzRCZhbXA7cmVzZXJ2ZWQ9MCIgdGFyZ2V0PSJfYmxhbmsiPg0KdXAgb24gYSBwb3N0LWl0
Jm5ic3A7IDwvYT5pZiB5b3UgZG8uJm5ic3A7IExvYWRzIHNoaWZ0LCByZXNvdXJjZXMgbW92ZSwg
YW5kIHN1ZGRlbmx5IHlvdSBmaW5kIHRoYXQgaG9zdCB3aGljaCB1c2VkIHRvIGJlIGluIHRoZSBz
YW1lIHJhY2ssIGJlaW5nIGRvd24sIGhhcyBsb2FkLXNoaWZ0ZWQgdG8gdGhlIG5leHQgaW5zdGFu
Y2UsJm5ic3A7IGluIGEgZGF0YWNlbnRlciA1MDAgbWlsZXMgYXdheSBhY3Jvc3MgYSB2ZXJ5IGRp
ZmZlcmVudCBuZXR3b3JrLiZuYnNwOw0KPGJyPg0KPGJyPg0KTWFueSBtb2Rlcm4gZGVwbG95bWVu
dHMgYXJlIGFsc28gaW4gc29tZW9uZSBlbHNlJ3MgZGF0YSBjZW50ZXIsIHNvIHNheWluZyAmcXVv
dDtEYXRhIGNlbnRlciBuZXR3b3JrcyZxdW90OyBkb2Vzbid0IHNheSBtdWNoIGFib3V0IHdoeSB5
b3UncmUgdHJ1c3RpbmcgdGhlIG5ldHdvcmsgaW5zaWRlLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5UZWQ8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAj
Q0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7
bWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tcmlnaHQ6MGluO21hcmdpbi1ib3R0b206NS4wcHQiPg0K
PGRpdj4NCjxkaXY+DQo8ZGl2IGlkPSJtXy0xODM0MjAzNjYyMDkyMjk2MTg1bV8tMzc3NTU1MjA5
NzU4MjY2NDU2MnhfY29tcG9zZXJfc2lnbmF0dXJlIj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS41cHQ7Y29sb3I6IzU3NTc1NyI+U2VudCB2
aWEgdGhlIFNhbXN1bmcgR2FsYXh5IFM3LCBhbiBBVCZhbXA7VCA0RyBMVEUgc21hcnRwaG9uZTwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdp
bi1ib3R0b20tYWx0OmF1dG8iPi0tLS0tLS0tIE9yaWdpbmFsIG1lc3NhZ2UgLS0tLS0tLS08bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+RnJvbTog
JnF1b3Q7U2FseiwgUmljaCZxdW90OyAmbHQ7cnNhbHo9PGEgaHJlZj0ibWFpbHRvOjQwYWthbWFp
LmNvbUBkbWFyYy5pZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPjQwYWthbWFpLmNvbUBkbWFyYy5p
ZXRmLm9yZzwvYT4mZ3Q7DQo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+RGF0ZTogNS8xLzE4IDU6MjUgQU0gKEdNVC0wODowMCkNCjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5UbzogQmVuamFt
aW4gS2FkdWsgJmx0O2JrYWR1az08YSBocmVmPSJtYWlsdG86NDBha2FtYWkuY29tQGRtYXJjLmll
dGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnPC9hPiZn
dDssIFByYXZlZW4gQmFsYXN1YnJhbWFuaWFuICZsdDtwcmF2Yj08YSBocmVmPSJtYWlsdG86NDBt
aWNyb3NvZnQuY29tQGRtYXJjLmlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+NDBtaWNyb3NvZnQu
Y29tQGRtYXJjLmlldGYub3JnPC9hPiZndDsNCjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5DYzogSUVURiBRVUlDIFdHICZsdDs8YSBocmVmPSJt
YWlsdG86cXVpY0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPnF1aWNAaWV0Zi5vcmc8L2E+Jmd0
Ow0KPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8i
PlN1YmplY3Q6IFJlOiBHZXR0aW5nIHRvIGNvbnNlbnN1cyBvbiBwYWNrZXQgbnVtYmVyIGVuY3J5
cHRpb24NCjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDph
dXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPGRpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bWFyZ2luLWJvdHRvbToxMi4wcHQiPiZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IEkgZGlzYWdy
ZWUgdGhhdCB3ZSBuZWVkIGFueSBtb3JlIGRhdGEgZm9yIG5vdCBkb2luZyBQTkUgaW4gdGhlIGRh
dGFjZW50ZXIuIFdoeSB3b3VsZCB3ZSBhZGQgYW4gZXh0cmEgZW5jcnlwdC1kZWNyeXB0IHN0ZXAg
Zm9yIG5vIG9idmlvdXMgYmVuZWZpdD88YnI+DQo8YnI+DQpJIGFtIGNvbmNlcm5lZCB0aGF0IHBl
b3BsZSB3aWxsIG1pcy1pbnRlcnByZXQgdGhlIG1lYW5pbmcgb2YgYSBkYXRhY2VudGVyLCBhbmQg
dGhpbmsgdGhhdCBhIGJ1bmNoIG9mIHNlcnZlcnMsIG9yIGV2ZW4gYSByYWNrLCBpbiBhbiBvcGVu
IGNvbG8gc3BhY2UgaXMgYSAmcXVvdDtkYXRhY2VudGVyLiZxdW90OyZuYnNwOyBDb21wdXRlcnMg
a2VlcCBnZXR0aW5nIGZhc3Rlci4NCjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_MWHPR21MB06386100B48E17A059B5A04EB6800MWHPR21MB0638namp_--


From nobody Tue May  1 20:48:42 2018
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7182A12D7F5 for <quic@ietfa.amsl.com>; Tue,  1 May 2018 20:48:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Wr7gvnqy1ygX for <quic@ietfa.amsl.com>; Tue,  1 May 2018 20:48:38 -0700 (PDT)
Received: from mail-yb0-x22b.google.com (mail-yb0-x22b.google.com [IPv6:2607:f8b0:4002:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC40412421A for <quic@ietf.org>; Tue,  1 May 2018 20:48:37 -0700 (PDT)
Received: by mail-yb0-x22b.google.com with SMTP id b14-v6so4821087ybk.1 for <quic@ietf.org>; Tue, 01 May 2018 20:48:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=2KQs59fxEVlQGKfcCFrrqD7KO7L2ndMvfoXjNVgCgtA=; b=dN3hnTJ7mZiggda5YtfauYa7WTv06hUMO5E/NI2aRz/IYy5v6Dee07bzaKrO4Kfv// lZIAeims0uzL6yJSmtcduY9f7TjeAJ/mEu9sAjEQEkp2339mw9gbcwusMiH8uuwD04ex H7LB1Axm1T/HoxtPLCwAEFdCcGJroatkN3XczJiUECsqrQB4LiApsADSiZHPTe28rMJE HCWXoQNPUQ4QIBEmBcGN0KUhaHeB0jtyYfowuOEDB3Q38VCryjaEFmfiMP5k7jVBCj68 l7ETH5JLVKp4rJGt160uG+FdM/JfoQTVEJYQC3ucgNjPXDY79XyU6ik4nr1ONTkyIm+P c5KQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=2KQs59fxEVlQGKfcCFrrqD7KO7L2ndMvfoXjNVgCgtA=; b=VUTQEnGu4cYxR0pPjKnRtUz3jjK2ttxUGO+MDJwGTRclHMNMk1KEt5ajsfokHhkO+f B7bZ/4wtmrwhK6eGt92QHXdm91ePgDdNrt+arGVwS4MFwZHvlCqvroPBX9KZtraKVNEG Q7tFaHyiv+5M808mvry+aVCL+ZPt9wmB672I7TuV5f4OVTbUhbN10m4oX+4t3BID9A8N 7vuTJwX8Cv+zsYsM9wPN92lKr7pDUwYPZguFa3CneJOJY0b8qappsClLYJ1VlrDShaX/ Sa/0Q2SFVyCd6kKZeXOe7Ly7e0ntYq1bzEEIReKo1TgrXe43hkRHpmAKa/yJJQdqLWC4 Yevw==
X-Gm-Message-State: ALQs6tDSkR/p8/rRh9AF8JPhNjVPGfGNh3t9IJs8b6yla0HYOmmbE+0l tJ6HH1HpiA1otTHbNJFzW89/dikqZiSifDwpWSg=
X-Google-Smtp-Source: AB8JxZqlNx/Ej0kw9MPwmePiPU029Z4CL8QFGC23UNCbgdGBIebbvQ/KF6npvKFKYPoLFqXUQfdwWXS+ch1ehap2Mt8=
X-Received: by 2002:a25:e08:: with SMTP id 8-v6mr4997356ybo.71.1525232916739;  Tue, 01 May 2018 20:48:36 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a25:d014:0:0:0:0:0 with HTTP; Tue, 1 May 2018 20:48:36 -0700 (PDT)
In-Reply-To: <MWHPR21MB0638014E783CE63F5D30DE38B6810@MWHPR21MB0638.namprd21.prod.outlook.com>
References: <CANatvzwCYrOZULG3iVmDFp97nr=M5=Gufo8TZjOGQVFUpsn0bQ@mail.gmail.com> <CAAedzxqDcPXJUE83KVnDiU23PvqDcTCrc6rRMw09FexjJA-Y6Q@mail.gmail.com> <CANatvzwjYE6EdvFtOXJMVQnutbVQ4YY+=XsQFzKwHzqWzZ4U+w@mail.gmail.com> <d32ade7b56bf4651952659307c08893b@usma1ex-dag1mb5.msg.corp.akamai.com> <CANatvzwHtCn8rLB8npf3i7PGyYZhVDRd2uojh5hv3uxtFPEsSA@mail.gmail.com> <58447D8E-782C-431C-8FC3-71124B10A047@trammell.ch> <CACpbDcdfF9w3qqrH1eB0sGU_4vheD9aMP5EXnp1o3Y19N19NUg@mail.gmail.com> <e8b4931a-3931-5b8d-8dad-3ca1939d5542@huitema.net> <CAKcm_gPaj3o-VTdA_0+Kk+nTcVJrYcs_BMyOiDGXKub3gB=GLg@mail.gmail.com> <MWHPR21MB063869878060E850137210FEB6820@MWHPR21MB0638.namprd21.prod.outlook.com> <20180501121906.GA5742@akamai.com> <F63059EA-BA14-4886-A4FB-AA5F04AC164B@akamai.com> <BY2PR15MB07757EAB6A818F1D8D8CCED9CD810@BY2PR15MB0775.namprd15.prod.outlook.com> <CA+9kkMCpxve3CKhQk45YKbvyOyQ6kvzyhpJhrTq1UM-QM+ms2Q@mail.gmail.com> <89893592-7135-4C24-BE1E-4B0FFD1A2E97@trammell.ch> <CA+9kkMCUTRrM9SPEz=Q5GDgU7whryZ1cRdj-O3=GP=-vOr-X+A@mail.gmail.com> <ba56bca23f5747e5abdfec137de37481@usma1ex-dag1mb5.msg.corp.akamai.com> <MWHPR21MB0638014E783CE63F5D30DE38B6810@MWHPR21MB0638.namprd21.prod.outlook.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Tue, 1 May 2018 22:48:36 -0500
Message-ID: <CAKKJt-e6WsXpvTRELUSCMRQJBgAsRFHPh9SHO6sH_LHEYY1VmQ@mail.gmail.com>
Subject: Re: Getting to consensus on packet number encryption
To: Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>
Cc: "Lubashev, Igor" <ilubashe@akamai.com>, Ted Hardie <ted.ietf@gmail.com>,  "Brian Trammell (IETF)" <ietf@trammell.ch>, "Salz, Rich" <rsalz@akamai.com>, Benjamin Kaduk <bkaduk@akamai.com>,  IETF QUIC WG <quic@ietf.org>, Roberto Peon <fenix@fb.com>
Content-Type: multipart/alternative; boundary="00000000000033bc18056b30f6b0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/u3c6MaJfG9rWzyiIH6LdydfJV5E>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 03:48:40 -0000

--00000000000033bc18056b30f6b0
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Speaking as a curious observer with no hat on ...

On Tue, May 1, 2018 at 1:59 PM, Praveen Balasubramanian <
pravb=3D40microsoft.com@dmarc.ietf.org> wrote:

> Yeah this doesn=E2=80=99t have to be unilateral and is a negotiation. Eit=
her side
> is free to terminate the handshake and fall back to TCP if it doesn=E2=80=
=99t want
> to support the transforms being offered in the negotiation. This works
> perfectly fine for the intra-DC use cases.
>

So, please help me understand whether I'm tracking this.

Most of the time, QUIC connections are expected to traverse something like
the public Internet, so a bunch of participants want PNE as an
anti-ossification thing in this case.

Sometimes, QUIC connections would traverse only a controlled network path
(which I THINK is the point of the conversation about datacenters), for
server-to-server connections. Some participants would like to avoid any
overhead they can avoid in those situations, and don't see any need for
PNE, only additional (single-digit percentage) costs, and would like to
negotiate not using PNE for those connections.

Is that about right, so far? Assuming so ...

Is it correct that those connections are using TCP today, and are seeing
sufficiently good performance with TCP to make additional overhead look
problematic?

Is it correct that if an implementation doesn't want to use QUIC with PNE
overhead, Plan A would be to refuse the QUIC connection and fall back to
TCP?

Thanks in advance for clues ...

Spencer

--00000000000033bc18056b30f6b0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Speaking as a curious observer with no hat on ...<div clas=
s=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, May 1, 2018 at 1:5=
9 PM, Praveen Balasubramanian <span dir=3D"ltr">&lt;<a href=3D"mailto:pravb=
=3D40microsoft.com@dmarc.ietf.org" target=3D"_blank">pravb=3D40microsoft.co=
m@dmarc.ietf.org</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_-4665118171389748141WordSection1">
<p class=3D"MsoNormal">Yeah this doesn=E2=80=99t have to be unilateral and =
is a negotiation. Either side is free to terminate the handshake and fall b=
ack to TCP if it doesn=E2=80=99t want to support the transforms being offer=
ed in the negotiation. This works perfectly fine for
 the intra-DC use cases.</p></div></div></blockquote><div><br></div><div>So=
, please help me understand whether I&#39;m tracking this.</div><div><br></=
div><div>Most of the time, QUIC connections are expected to traverse someth=
ing like the public Internet, so a bunch of participants want PNE as an ant=
i-ossification thing in this case.=C2=A0</div><div><br></div><div>Sometimes=
, QUIC connections would traverse only a controlled network path (which I T=
HINK is the point of the conversation about datacenters), for server-to-ser=
ver connections. Some participants would like to avoid any overhead they ca=
n avoid in those situations, and don&#39;t see any need for PNE, only addit=
ional (single-digit percentage) costs, and would like to negotiate not usin=
g PNE for those connections.</div><div><br></div><div>Is that about right, =
so far? Assuming so ...</div><div><br></div><div>Is it correct that those c=
onnections are using TCP today, and are seeing sufficiently good performanc=
e with TCP to make additional overhead look problematic?</div><div><br></di=
v><div>Is it correct that if an implementation doesn&#39;t want to use QUIC=
 with PNE overhead, Plan A would be to refuse the QUIC connection and fall =
back to TCP?</div><div><br></div><div>Thanks in advance for clues ...</div>=
<div><br></div><div>Spencer</div></div></div></div>

--00000000000033bc18056b30f6b0--


From nobody Tue May  1 23:18:40 2018
Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0FB6C12D86C for <quic@ietfa.amsl.com>; Tue,  1 May 2018 23:18:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 T6uoJGb6UIuK for <quic@ietfa.amsl.com>; Tue,  1 May 2018 23:18:38 -0700 (PDT)
Received: from mail-pf0-x230.google.com (mail-pf0-x230.google.com [IPv6:2607:f8b0:400e:c00::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E98DC127698 for <quic@ietf.org>; Tue,  1 May 2018 23:18:37 -0700 (PDT)
Received: by mail-pf0-x230.google.com with SMTP id w129so5461514pfd.3 for <quic@ietf.org>; Tue, 01 May 2018 23:18:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :mime-version; bh=2OvPa4wVZmxoCfgzGIPP7pl1UAwsRGgI7eMTwcRDKlQ=; b=qsaOzSHOTbIaJMCPTDkA5ahAXQskfqF6CT9xBdeqZJM6Y0l5APXtxt1JReix5ppN5k zr3ZXW5qGKZS57OXmKJ4XSqHz96mbxZtdReZI/Ruk52/4bFLcMukXbNHLEcRyfJHb2DM GtKH+uwLhCMYiPY9c/GdJ93beUzTbneGeZv71mNxqnz3j1CuqaNcNuy2TLDdfosf33zT yWNf+NY7eKDo9II3P6Br/i42dy5/VpwBtEGUZVJ9yDpkFKRaIl1tcXPV3ii5gcezNq1A 3Diia7vj77ZCsh2nXvLdlX/e+BF/w3Vuww4NCB9mrGi9oAgt+eo8TaGC8Zi2nIrnwZx4 nZ8A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:mime-version; bh=2OvPa4wVZmxoCfgzGIPP7pl1UAwsRGgI7eMTwcRDKlQ=; b=Jy20bldnBrzH8FgwK/rCoxvW5X1uN8VDqX5zBDRF+zC1JpdngSmoLjEQzWeksDhzU4 A0106rbPeeo/AIu7mI2E9rMX/zG+1zXeAlXA0oPd07n3J6Yd5YXZGczwLWLtjouaRf8Z fNrDP6prIwLqj29N109moWlRLKG1VAc9HyFY7MBkJZkNZtfhRMS17ZJoWxccAV6ViSjG 92o6vdKBl24SuMqXHA3pYF3QAukO8yAqXjkEPNQUYVExVLqit2CRsThUWouClYIl4ujJ zs0OFf/VEHHNd13dhM+LLUquqwLYKPeeWCW6q6yz66GolpPxhnxKeS9SOcggEU9gsMzq 4e6Q==
X-Gm-Message-State: ALQs6tDlQBkQicSUrNHX30cOhlvOkWGzHScjaXSfMzouGDzOt66d2zjd 9CcYj3TkEQtLGqaLCRIySZM=
X-Google-Smtp-Source: AB8JxZrokNEbIc6dLMZmMG/FGRg0AH17wXz+eO0gcGAk+fCRMLS+vdDk23wX5/Ab9Pbl60YCJoaYLg==
X-Received: by 2002:a63:a06a:: with SMTP id u42-v6mr14572816pgn.389.1525241917316;  Tue, 01 May 2018 23:18:37 -0700 (PDT)
Received: from DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM ([40.101.73.69]) by smtp.gmail.com with ESMTPSA id j9sm18509705pff.46.2018.05.01.23.18.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 01 May 2018 23:18:36 -0700 (PDT)
From: =?Windows-1252?Q?Mikkel_Fahn=F8e_J=F8rgensen?= <mikkelfj@gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>
CC: Ted Hardie <ted.ietf@gmail.com>, "Salz, Rich" <rsalz@akamai.com>, "Lubashev, Igor" <ilubashe@akamai.com>, Roberto Peon <fenix@fb.com>, "Brian Trammell (IETF)" <ietf@trammell.ch>, Benjamin Kaduk <bkaduk@akamai.com>, IETF QUIC WG <quic@ietf.org>
Subject: Re: Getting to consensus on packet number encryption
Thread-Topic: Getting to consensus on packet number encryption
Thread-Index: AQHTy9Gavrm3K/jvTEOucWh2l1TdAaPwZ0sAgAC4ugCAAARcAIAAG5CAgAAFCACAAACJgIAAEVkAgACR+YCAB09lAIAFXyIAgAVK+oCAAJlSAIABxdSAgACOHICAB/EyAIACo7YAgACiMICAAADPgIAAIs8AgAAm/YCAABExgIAABpIAgAAK6ACAAPIgAIAA5wcAgACzcYCAAHHMgIAEe1cAgAABEACAABWHgIAA8UgAgAABeQCAAC8kAIAAC7UAgAARLwCAAA0zAIAAD7YAgAAFcACAAJPZAIAAKeKS
X-MS-Exchange-MessageSentRepresentingType: 2
Date: Wed, 2 May 2018 06:18:30 +0000
Message-ID: <DB6PR10MB17667578B2E994EE1B771E45AC800@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM>
References: <CANatvzwCYrOZULG3iVmDFp97nr=M5=Gufo8TZjOGQVFUpsn0bQ@mail.gmail.com> <CAAedzxqDcPXJUE83KVnDiU23PvqDcTCrc6rRMw09FexjJA-Y6Q@mail.gmail.com> <CANatvzwjYE6EdvFtOXJMVQnutbVQ4YY+=XsQFzKwHzqWzZ4U+w@mail.gmail.com> <d32ade7b56bf4651952659307c08893b@usma1ex-dag1mb5.msg.corp.akamai.com> <CANatvzwHtCn8rLB8npf3i7PGyYZhVDRd2uojh5hv3uxtFPEsSA@mail.gmail.com> <58447D8E-782C-431C-8FC3-71124B10A047@trammell.ch> <CACpbDcdfF9w3qqrH1eB0sGU_4vheD9aMP5EXnp1o3Y19N19NUg@mail.gmail.com> <e8b4931a-3931-5b8d-8dad-3ca1939d5542@huitema.net> <CAKcm_gPaj3o-VTdA_0+Kk+nTcVJrYcs_BMyOiDGXKub3gB=GLg@mail.gmail.com> <MWHPR21MB063869878060E850137210FEB6820@MWHPR21MB0638.namprd21.prod.outlook.com> <20180501121906.GA5742@akamai.com> <F63059EA-BA14-4886-A4FB-AA5F04AC164B@akamai.com> <BY2PR15MB07757EAB6A818F1D8D8CCED9CD810@BY2PR15MB0775.namprd15.prod.outlook.com> <CA+9kkMCpxve3CKhQk45YKbvyOyQ6kvzyhpJhrTq1UM-QM+ms2Q@mail.gmail.com> <89893592-7135-4C24-BE1E-4B0FFD1A2E97@trammell.ch> <CA+9kkMCUTRrM9SPEz=Q5GDgU7whryZ1cRdj-O3=GP=-vOr-X+A@mail.gmail.com> <ba56bca23f5747e5abdfec137de37481@usma1ex-dag1mb5.msg.corp.akamai.com> <MWHPR21MB0638014E783CE63F5D30DE38B6810@MWHPR21MB0638.namprd21.prod.outlook.com>, <CAKKJt-e6WsXpvTRELUSCMRQJBgAsRFHPh9SHO6sH_LHEYY1VmQ@mail.gmail.com>
In-Reply-To: <CAKKJt-e6WsXpvTRELUSCMRQJBgAsRFHPh9SHO6sH_LHEYY1VmQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator: 
X-MS-Exchange-Organization-RecordReviewCfmType: 0
Content-Type: multipart/alternative; boundary="_000_DB6PR10MB17667578B2E994EE1B771E45AC800DB6PR10MB1766EURP_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/YO-Vgs1RLdUOxUr2W4U4PFEF4Po>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 06:18:40 -0000

--_000_DB6PR10MB17667578B2E994EE1B771E45AC800DB6PR10MB1766EURP_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

I think there are cases where the PNE overhead is more than single digit pc=
t:

Small packets with, say, latest stockquote would have PNE double the packet=
 protection overhead - and there isn=92t much other overhead. This adds lat=
ency.

Another example is sending a transaction ID serially through 3 out of 5 mas=
ters to reach consensus. PNE could dominate the achievable transaction rate=
 assuming very fast networks.

________________________________
From: QUIC <quic-bounces@ietf.org> on behalf of Spencer Dawkins at IETF <sp=
encerdawkins.ietf@gmail.com>
Sent: Wednesday, May 2, 2018 5:48:36 AM
To: Praveen Balasubramanian
Cc: Ted Hardie; Salz, Rich; Lubashev, Igor; Roberto Peon; Brian Trammell (I=
ETF); Benjamin Kaduk; IETF QUIC WG
Subject: Re: Getting to consensus on packet number encryption

Speaking as a curious observer with no hat on ...

On Tue, May 1, 2018 at 1:59 PM, Praveen Balasubramanian <pravb=3D40microsof=
t.com@dmarc.ietf.org<mailto:pravb=3D40microsoft.com@dmarc.ietf.org>> wrote:
Yeah this doesn=92t have to be unilateral and is a negotiation. Either side=
 is free to terminate the handshake and fall back to TCP if it doesn=92t wa=
nt to support the transforms being offered in the negotiation. This works p=
erfectly fine for the intra-DC use cases.

So, please help me understand whether I'm tracking this.

Most of the time, QUIC connections are expected to traverse something like =
the public Internet, so a bunch of participants want PNE as an anti-ossific=
ation thing in this case.

Sometimes, QUIC connections would traverse only a controlled network path (=
which I THINK is the point of the conversation about datacenters), for serv=
er-to-server connections. Some participants would like to avoid any overhea=
d they can avoid in those situations, and don't see any need for PNE, only =
additional (single-digit percentage) costs, and would like to negotiate not=
 using PNE for those connections.

Is that about right, so far? Assuming so ...

Is it correct that those connections are using TCP today, and are seeing su=
fficiently good performance with TCP to make additional overhead look probl=
ematic?

Is it correct that if an implementation doesn't want to use QUIC with PNE o=
verhead, Plan A would be to refuse the QUIC connection and fall back to TCP=
?

Thanks in advance for clues ...

Spencer

--_000_DB6PR10MB17667578B2E994EE1B771E45AC800DB6PR10MB1766EURP_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<meta content=3D"text/html; charset=3Dutf-8">
</head>
<body>
<div id=3D"compose-container" itemscope=3D"" itemtype=3D"https://schema.org=
/EmailMessage" style=3D"direction:ltr">
<span itemprop=3D"creator" itemscope=3D"" itemtype=3D"https://schema.org/Or=
ganization"><span itemprop=3D"name"></span></span>
<div>
<div style=3D"direction:ltr">I think there are cases where the PNE overhead=
 is more than single digit pct:</div>
<div><br>
</div>
<div style=3D"direction:ltr">Small packets with, say, latest stockquote wou=
ld have PNE double the packet protection overhead - and there isn=92t much =
other overhead. This adds latency.</div>
<div><br>
</div>
<div style=3D"direction:ltr">Another example is sending a transaction ID se=
rially through 3 out of 5 masters to reach consensus. PNE could dominate th=
e achievable transaction rate assuming very fast networks.</div>
<div><br>
</div>
<div class=3D"acompli_signature"></div>
</div>
</div>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" co=
lor=3D"#000000" style=3D"font-size:11pt"><b>From:</b> QUIC &lt;quic-bounces=
@ietf.org&gt; on behalf of Spencer Dawkins at IETF &lt;spencerdawkins.ietf@=
gmail.com&gt;<br>
<b>Sent:</b> Wednesday, May 2, 2018 5:48:36 AM<br>
<b>To:</b> Praveen Balasubramanian<br>
<b>Cc:</b> Ted Hardie; Salz, Rich; Lubashev, Igor; Roberto Peon; Brian Tram=
mell (IETF); Benjamin Kaduk; IETF QUIC WG<br>
<b>Subject:</b> Re: Getting to consensus on packet number encryption</font>
<div>&nbsp;</div>
</div>
<div>
<div dir=3D"ltr">Speaking as a curious observer with no hat on ...
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Tue, May 1, 2018 at 1:59 PM, Praveen Balasubr=
amanian <span dir=3D"ltr">
&lt;<a href=3D"mailto:pravb=3D40microsoft.com@dmarc.ietf.org" target=3D"_bl=
ank">pravb=3D40microsoft.com@dmarc.ietf.org</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex; border-left:1=
px #ccc solid; padding-left:1ex">
<div lang=3D"EN-US">
<div class=3D"m_-4665118171389748141WordSection1">
<p class=3D"MsoNormal">Yeah this doesn=92t have to be unilateral and is a n=
egotiation. Either side is free to terminate the handshake and fall back to=
 TCP if it doesn=92t want to support the transforms being offered in the ne=
gotiation. This works perfectly fine for
 the intra-DC use cases.</p>
</div>
</div>
</blockquote>
<div><br>
</div>
<div>So, please help me understand whether I'm tracking this.</div>
<div><br>
</div>
<div>Most of the time, QUIC connections are expected to traverse something =
like the public Internet, so a bunch of participants want PNE as an anti-os=
sification thing in this case.&nbsp;</div>
<div><br>
</div>
<div>Sometimes, QUIC connections would traverse only a controlled network p=
ath (which I THINK is the point of the conversation about datacenters), for=
 server-to-server connections. Some participants would like to avoid any ov=
erhead they can avoid in those situations,
 and don't see any need for PNE, only additional (single-digit percentage) =
costs, and would like to negotiate not using PNE for those connections.</di=
v>
<div><br>
</div>
<div>Is that about right, so far? Assuming so ...</div>
<div><br>
</div>
<div>Is it correct that those connections are using TCP today, and are seei=
ng sufficiently good performance with TCP to make additional overhead look =
problematic?</div>
<div><br>
</div>
<div>Is it correct that if an implementation doesn't want to use QUIC with =
PNE overhead, Plan A would be to refuse the QUIC connection and fall back t=
o TCP?</div>
<div><br>
</div>
<div>Thanks in advance for clues ...</div>
<div><br>
</div>
<div>Spencer</div>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_DB6PR10MB17667578B2E994EE1B771E45AC800DB6PR10MB1766EURP_--


From nobody Tue May  1 23:25:11 2018
Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D1A412D86F for <quic@ietfa.amsl.com>; Tue,  1 May 2018 23:25:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.02
X-Spam-Level: 
X-Spam-Status: No, score=-1.02 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FROM_EXCESS_BASE64=0.979, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 vY2VCB1PIuB3 for <quic@ietfa.amsl.com>; Tue,  1 May 2018 23:25:06 -0700 (PDT)
Received: from mail-pf0-x22a.google.com (mail-pf0-x22a.google.com [IPv6:2607:f8b0:400e:c00::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4521712D86C for <quic@ietf.org>; Tue,  1 May 2018 23:25:06 -0700 (PDT)
Received: by mail-pf0-x22a.google.com with SMTP id f189so10898103pfa.7 for <quic@ietf.org>; Tue, 01 May 2018 23:25:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :mime-version; bh=GEh6cGnM+bk53RVGWznDHsr5YjRXnr1u6rSZ/dePfIY=; b=KBoo+kk7p29+r8WixtOjamqorsaOSRwyNJQJYScfA8v6Q53Gs56Rg+Pdur5Fj4ClhQ /7jluCv17qfDDsGnAe9328B5myWWNoedw9EdR5pApLy39LC0ATuZMQD0DIH9MqiH0LbG AK6ZQkOfN/uU/s3gJb/dJ2mAONm295illT7/JQh6AoVTaw/xAE/H0KswZX7iCOVvFEZ8 ZQ1Fv2mK7OjR5bQxBq6h9fxXCKubWKrqqmc4/ciRVdfcwaPEsz/dIGmlxMoi0FTsAbQ1 p1wwoyFyEAhwgr0BHpuwWulFGVcLC18b3uCpr16nUsqc3DA7knbKJJnbCTMWGJrj5JNY MDKw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:mime-version; bh=GEh6cGnM+bk53RVGWznDHsr5YjRXnr1u6rSZ/dePfIY=; b=Z0k4fxB1diHh2/21YSH7j2oMoWS8AGtkr9LmIJYdUf3MIg9uoSVT3NWs7A5Unb6yOd vfqdATk2jS7MiOZceadpBXM5eRBqjygyvFP5IVQWtUCLQEVvVTVS8Ss1vSp1EFCG06aM bb/aTp/6h5tJgP3lRVYYWZBMOeTwnzrTHZDn9InU9iXlS8F/OaW2bT4LfZNFgEOZARsI TTNif1dcEmXUuhPz0fEBuoJSD9zCSdv6jUM6rG4U/aCgG58T3VsaSE2fvf497Uy/IjoC wyaE/W69jPUposWPRX9OJhiPXaSoskbrR0cQBdqvJ12BRN6ghzbQdLu2Xwk0xLVQ3Kao qWtA==
X-Gm-Message-State: ALQs6tD3P4GN+UCY92SDfW1VGpchL9csf8UiDHIy7xF4XjzDCZvdd6Gl MI8LAQG3AiF7jEUc61pKQLBRX39uhXw=
X-Google-Smtp-Source: AB8JxZoku5teAU7HFaidy4Rq0VODRLaTf7NW2bpTXpRa7wyuH5gKhDgo+JLwBkNKIsRdtFB1MRbfbg==
X-Received: by 2002:a63:7207:: with SMTP id n7-v6mr12700018pgc.195.1525242304044;  Tue, 01 May 2018 23:25:04 -0700 (PDT)
Received: from DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM ([40.101.73.69]) by smtp.gmail.com with ESMTPSA id q75sm22459819pfj.94.2018.05.01.23.25.01 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Tue, 01 May 2018 23:25:03 -0700 (PDT)
From: =?utf-8?B?TWlra2VsIEZhaG7DuGUgSsO4cmdlbnNlbg==?= <mikkelfj@gmail.com>
To: Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>, Jana Iyengar <jri.ietf@gmail.com>, Roberto Peon <fenix@fb.com>
CC: "Salz, Rich" <rsalz@akamai.com>, Ted Hardie <ted.ietf@gmail.com>, IETF QUIC WG <quic@ietf.org>, Benjamin Kaduk <bkaduk@akamai.com>
Subject: Re: [Potential Spoof] Re: Getting to consensus on packet number encryption
Thread-Topic: [Potential Spoof] Re: Getting to consensus on packet number encryption
Thread-Index: ATlBQzQ2YYsevZZUfFBI+4kQmRWChHd0T3BIMDBBMDCwBBGovA==
X-MS-Exchange-MessageSentRepresentingType: 2
Date: Wed, 2 May 2018 06:24:58 +0000
Message-ID: <DB6PR10MB17660511ED052322C7BD4F17AC800@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM>
References: <01AE46C6-682C-4A21-84CD-1D8DAD6F49D9@fb.com> <CACpbDcdnmHrWMCShYd1pEDBervRKfO1pMUM8hb4tkK9nqH1Mdw@mail.gmail.com>, <MWHPR21MB06386100B48E17A059B5A04EB6800@MWHPR21MB0638.namprd21.prod.outlook.com>
In-Reply-To: <MWHPR21MB06386100B48E17A059B5A04EB6800@MWHPR21MB0638.namprd21.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator: 
X-MS-Exchange-Organization-RecordReviewCfmType: 0
Content-Type: multipart/alternative; boundary="_000_DB6PR10MB17660511ED052322C7BD4F17AC800DB6PR10MB1766EURP_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/bqXQfhHP8A4JzPFLXTd1N5iyUvY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 06:25:10 -0000

--_000_DB6PR10MB17660511ED052322C7BD4F17AC800DB6PR10MB1766EURP_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

QSBkYXRhIGNlbnRlciBtaWdodCB1c2UgYW4gb3ZlcmxheSBuZXR3b3JrIHdpdGggS3ViZXJuZXRl
cyBvciBTd2FybSAtIHdoaWNoIG1pZ2h0IGxlYWQgdG8gb3NzaWZpY2F0aW9uLg0KDQpBbiB1bmVu
Y3J5cHRlZCBwZXIgQ0lEIFBOIHdpdGggY2hlYXAgbXVsdGlwbGljYXRpb24gcGVybXV0YXRpb24g
aXMgYW5vdGhlciBvcHRpb24gY29tcGFyZWQgdG8gMTA3OS4NCg0KX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX18NCkZyb206IFFVSUMgPHF1aWMtYm91bmNlc0BpZXRmLm9yZz4gb24gYmVo
YWxmIG9mIFByYXZlZW4gQmFsYXN1YnJhbWFuaWFuIDxwcmF2Yj00MG1pY3Jvc29mdC5jb21AZG1h
cmMuaWV0Zi5vcmc+DQpTZW50OiBXZWRuZXNkYXksIE1heSAyLCAyMDE4IDQ6MDI6MzcgQU0NClRv
OiBKYW5hIEl5ZW5nYXI7IFJvYmVydG8gUGVvbg0KQ2M6IFNhbHosIFJpY2g7IFRlZCBIYXJkaWU7
IElFVEYgUVVJQyBXRzsgQmVuamFtaW4gS2FkdWsNClN1YmplY3Q6IFJFOiBbUG90ZW50aWFsIFNw
b29mXSBSZTogR2V0dGluZyB0byBjb25zZW5zdXMgb24gcGFja2V0IG51bWJlciBlbmNyeXB0aW9u
DQoNCldlIGNhbiBnZXQgKDEpIGRvbmUgYnV0IEkgZGlzYWdyZWUgdGhhdCB3ZSBjYW4gZGVjb3Vw
bGUgKDIpLiBJdCBkb2VzbuKAmXQgbWFrZSBzZW5zZSB0byByZXF1aXJlIHBlcmZvcm1hbmNlIG92
ZXJoZWFkIGFsbCB0aGUgdGltZSB3aXRoIG5vIGJlbmVmaXQuIEZvciB0aGUgSW50ZXJuZXQsIFBO
RSBjYW4gcHJldmVudCBvc3NpZmljYXRpb24gc28gaXQgaXMgc2VlbiBhcyBhIHJlYXNvbmFibGUg
dHJhZGUtb2ZmLiBGb3IgdGhlIGRhdGFjZW50ZXIsIHRoZXJlIGlzIG5vIGtub3duIGJlbmVmaXQs
IG9ubHkgY29zdC4NCg0KV2Uga25vdyB0aGF0IHRoZXJlIGlzIGEgQ1BVIGNvc3QsIHRoaXMgaXMg
bm90IHNwZWN1bGF0aW9uLiBEb2VzbuKAmXQgbWF0dGVyIGlmIHRoZSBjb3N0IGlzIDElIG9yIDEw
JS4gSGFyZHdhcmUgaW1wbGVtZW50ZXJzIGhhdmUgYWxzbyByYWlzZWQgY29uY2VybnMuIEV2ZXJ5
IENQVSBjeWNsZSB3ZSBzcGVuZCBvbiB0aGluZ3MgdGhhdCBhZGQgbm8gdmFsdWUgdG8gdGhlIHVz
ZXIgc2hvdWxkIGJlIHF1ZXN0aW9uZWQuIEV2ZXJ5IGV4dHJhIGluc3RydWN0aW9uIHdlIGV4ZWN1
dGUgaW4gdGhlIGhvdCBkYXRhIHBhdGggbGVhdmVzIGxlc3MgQ1BVIGZvciB3b3JrbG9hZHMsIGJ1
cm5zIG1vcmUgcG93ZXIgYW5kIG1ha2VzIGZvciBhIHdvcnNlIGNvbXBhcmlzb24gd2l0aCBIVFRQ
UyBvdmVyIFRDUC4gVGhlIHNhbWUgYXJndW1lbnQgYXMgcHJpdmFjeSBob2xlcyBob2xkcyBoZXJl
IOKAkyBqdXN0IGJlY2F1c2UgdGhlcmUgYXJlIHNvbWUgZXhpc3RpbmcgcGVyZiBib3R0bGVuZWNr
cyBkb2VzbuKAmXQgbWVhbiB3ZSBhZGQgbW9yZSwgcGFydGljdWxhcmx5IG9uZXMgd2UgY2Fubm90
IG1pdGlnYXRlLiBJIHNhaWQgaXQgYmVmb3JlIHRoYXQgdGhlcmUgYXJlIGxvdHMgb2Ygd2F5cyB3
ZSBjYW4gaW1wcm92ZSBVRFAgcGVyZiBidXQgSSBkb27igJl0IGtub3cgb2YgYW55IHRlY2huaXF1
ZSBmb3IgcmVkdWNpbmcgY3J5cHRvIENQVSBjb3N0IG90aGVyIHRoYW4gaGFyZHdhcmUgb2ZmbG9h
ZC4NCg0KVGhlIGNvc3QgaXMgY2VydGFpbmx5IHdvcnRoIHNhdmluZyB3aXRoIHNvbWV0aGluZyBh
cyBzaW1wbGUgYXMgYSBuZWdvdGlhdGlvbiBtZWNoYW5pc20uIEFtIEkgbWlzc2luZyBzb21ldGhp
bmcgYWJvdXQgYSB0cmFuc3BvcnQgcGFyYW1ldGVyIGJlaW5nIGNvbXBsaWNhdGVkIHRvIGltcGxl
bWVudD8gSW1wbGVtZW50YXRpb25zIGFyZSBmcmVlIHRvIHN1cHBvcnQgb25seSBQTkUgYW5kIG5v
dCBuZWdvdGlhdGUgYW55dGhpbmcgZWxzZS4gVGhlcmUgaXMgYWN0dWFsbHkgYW4gZXZlbiBzaW1w
bGVyIG1lY2hhbmlzbSBpZiBhIHRyYW5zcG9ydCBwYXJhbWV0ZXIgaXMgZGVlbWVkIGFzIGNvc3Rs
eTogaWYgdGhlIHBlZXIgc2VuZHMgUE4gPSAwIGluIHRoZSBDSSwgdGhlbiBpdHMgcmVxdWVzdGlu
ZyBubyBQTkUgYW5kIHRoZSByZWNlaXZlciBjYW4gY2hvb3NlIHRvIHByb2NlZWQgb3IgZHJvcCBh
bmQgZm9yY2UgVENQIGZhbGwgYmFjay4gVGhpcyBzaG91bGQgdGFrZSBvbmx5IGFuIGV4dHJhIGlm
IGNoZWNrIG9uIHRoZSByZWNlaXZlciBDSSBwcm9jZXNzaW5nIGxvZ2ljIHRvIGltcGxlbWVudC4g
SSBhbSBhc3N1bWluZyBoZXJlIHRoYXQgUE5FIG9uIGlucHV0IG9mIDAgd2lsbCBub3QgcHJvZHVj
ZSAwIHNvIGl04oCZcyBhIHNhZmUgc2VudGluZWwgdmFsdWUuDQoNCkZyb206IEphbmEgSXllbmdh
ciBbbWFpbHRvOmpyaS5pZXRmQGdtYWlsLmNvbV0NClNlbnQ6IFR1ZXNkYXksIE1heSAxLCAyMDE4
IDU6MzcgUE0NClRvOiBSb2JlcnRvIFBlb24gPGZlbml4QGZiLmNvbT4NCkNjOiBQcmF2ZWVuIEJh
bGFzdWJyYW1hbmlhbiA8cHJhdmJAbWljcm9zb2Z0LmNvbT47IFRlZCBIYXJkaWUgPHRlZC5pZXRm
QGdtYWlsLmNvbT47IFNhbHosIFJpY2ggPHJzYWx6QGFrYW1haS5jb20+OyBCZW5qYW1pbiBLYWR1
ayA8YmthZHVrQGFrYW1haS5jb20+OyBJRVRGIFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc+DQpTdWJq
ZWN0OiBSZTogW1BvdGVudGlhbCBTcG9vZl0gUmU6IEdldHRpbmcgdG8gY29uc2Vuc3VzIG9uIHBh
Y2tldCBudW1iZXIgZW5jcnlwdGlvbg0KDQpJJ2xsIHRyeSB0byBzdW1tYXJpemUgbXkgcG9zaXRp
b24gb24gIzEwNzkuIEkgc2VlIHR3byBwb2ludHM6DQoxLiBQTkUgd2lsbCBoZWxwIGFnYWluc3Qg
b3NzaWZpY2F0aW9uIGFuZCBhbHNvLCBhbGJlaXQgdG8gYSBsaW1pdGVkIGV4dGVudCwgbGlua2Fi
aWxpdHkuDQoyLiBQTkUgaGFzIGEgQ1BVIGNvc3QuIFdoaWxlIHdlIGNhbiBzcGVjdWxhdGUsIHdl
IHN0aWxsIGRvbid0ICprbm93KiB3aGF0IHRoaXMgY29zdCB3aWxsIGJlIGluIHRoZSBjb250ZXh0
IG9mIGRlcGxveW1lbnQsIGFuZCB3aGV0aGVyIHRoaXMgY29zdCB3aWxsIGJlIHRoZSBzaG93LXN0
b3BwZXIuIFBORSdzIENQVSBjb3N0IG1heSBvciBtYXkgbm90IGJlIGFtZWxpb3JhdGVkIGJ5IE5J
QyBpbXBsZW1lbnRhdGlvbi4gV2Ugc2hvdWxkIGFsbG93IFBORSBuZWdvdGlhYmlsaXR5IHdoZW4g
d2UgaGF2ZSBlc3RhYmxpc2hlZCB0aGF0IHRoaXMgY29zdCBpcyB3b3J0aCBzYXZpbmcuDQoNCk15
IHNlbnNlIGlzIHRoYXQgd2UgYWdyZWUgb24gKDEpLiBUaGlzIGlzIHdoYXQgIzEwNzkgaXMgZG9p
bmcsIHNvIHdlIHNob3VsZCBzZXBhcmF0ZSB0aGUgdHdvIHF1ZXN0aW9ucyBhbmQgZ2V0ICgxKSBk
b25lLiBXaGV0aGVyIHdlIGRvICgyKSBvciBub3QgaXMgYmVpbmcgZGlzY3Vzc2VkIG9uIHRoaXMg
dGhyZWFkLCBhbmQgSSB0aGluayB3ZSBjYW4gY29udGludWUsIGJ1dCAjMTA3OSBzaG91bGQgYmUg
aW5kZXBlbmRlbnRseSBzdWJtaXR0ZWQuDQoNCkZXSVcsIEkgYmVsaWV2ZSB0aGF0IHdlIHdhbnQg
dG8gaXRlcmF0ZSBvbiB2ZXJzaW9ucywgYW5kIHRoYXQgd2Ugd2lsbCB3YW50IHRvIGdldCBhIHYy
IG91dCBhcyBzb29uIGFzIHdlIGhhdmUgdGhpbmdzIHRvIGdldCBkZXBsb3llZCB0aGF0IGxlZnQg
cGVuZGluZyBpbiB2MS4NCg0KDQpUaG91Z2h0cyBvbiBpbnRyYS1EQyBRVUlDLCByZWxhdGVkIHRv
IHBvaW50ICgyKSBmb2xsb3c6DQoNCkkgZG9uJ3QgdGhpbmsgd2UnbGwgcmVhY2ggYSBtZWFuaW5n
ZnVsIGVuZCB0byB0aGlzIGRpc2N1c3Npb24gYnkgZ2V0dGluZyBpbnRvIHNlY3VyaXR5IGZvciBp
bnRyYS1EQyBwcm90b2NvbHMuIEkgdW5kZXJzdGFuZCB0aGF0IHRoZXJlIG1heSBiZSBzaXR1YXRp
b25zIHdoZXJlIG9uZSBtYXkgaGF2ZSBmYWlyIGNlcnRhaW50eSBhYm91dCB0aGUgZGVwbG95bWVu
dCBjb250ZXh0IGFuZCBnaXZlbiB0aGF0IHRoZSBzZWN1cml0eSB0cmFkZW9mZiBpc24ndCB0aGUg
c2FtZSBhcyBkaXNhYmxpbmcgVExTLCB0aGUgYmFyIHdpbGwgYmUgc3Vic3RhbnRpYWxseSBsb3dl
ciBmb3IgZGlzYWJsaW5nIFBORS4NCg0KT24gUVVJQyBpbiBpbnRyYS1EQyBlbnZpcm9ubWVudHM6
DQoxLiBBcyBJZ29yIG5vdGVkLCB0aGUgdmFsdWUgb2YgUVVJQyBpbiB0aGUgaW50cmEtREMgZW52
aXJvbm1lbnRzIGlzIHVuY2VydGFpbiwgYW5kIEknbSBub3QgeWV0IHN1cmUgdGhhdCBjb21wcm9t
aXNpbmcgb24gUE5FIGZvciBhbiB1bmtub3duIGNvc3QgaW4gYW4gdW5jZXJ0YWluIGRlcGxveW1l
bnQgY29udGV4dCBpcyBuZWNlc3NhcmlseSB1c2VmdWwuDQoyLiBTZXBhcmF0ZWx5LCBJIHJlbWFp
biB1bmNvbnZpbmNlZCwgYmFzZWQgb24gbXkgZXhwZXJpZW5jZSB3aXRoIHRyeWluZyB0byBnZXQg
UVVJQyB1c2VkIGZvciBEQyB0cmFuc3BvcnQsIHRoYXQgdGhpcyBjb3N0IGlzIGdvaW5nIHRvIGJl
IGFuIGltcG9ydGFudCBmYWN0b3IgaW4gUVVJQyBhZG9wdGlvbiB3aXRoaW4gRENzLiBJIGFncmVl
IHRoYXQgQ1BVIGNvc3QgaXMgYSBmYWN0b3IsIGJ1dCB0aGVyZSBhcmUgbXVjaCBiaWdnZXIgdGhp
bmdzIGhlcmUgdGhhdCB3aWxsIG5lZWQgYXR0ZW50aW9uIChzZWdtZW50YXRpb24gb2ZmbG9hZCwg
c21hbGxlciByZWNvcmQgc2l6ZXMsIHVzZXJzcGFjZSBjb3N0cykgdGhhdCB3aWxsIGRvbWluYXRl
IHdlbGwgYmVmb3JlIHRoaXMgQUVTIG9wZXJhdGlvbiBiZWNvbWVzIGEgZmFjdG9yLiBUaGlzIGFs
bCByZW1haW5zIHNwZWN1bGF0aW9uIHRob3VnaC4NCg0KUHJhdmVlbjogTm90IG1ha2luZyBQTkUg
b3B0aW9uYWwgcmlnaHQgbm93IGRvZXMgbm90IG1lYW4gd2Ugd29uJ3QgZG8gaXQuIEl0IGp1c3Qg
bWVhbnMgdGhhdCBpdCdzIGFuIG9wZW4gcXVlc3Rpb24uIEknbSBub3QgeWV0IGNvbnZpbmNlZCB0
aGF0IGl0J3MgYSBkZWJpbGl0YXRpbmcgY29zdCBvciBvbmUgb2YgdGhlIHByb3ZlcmJpYWwgIm1p
bGxpb24gY3V0cyIgdGhhdCB3aWxsIGtlZXAgaXQgZnJvbSBnZXR0aW5nIGRlcGxveWVkIGludHJh
LURDLiBZb3UgYXJlIHJpZ2h0IHRoYXQgeW91J2xsIHdhbnQgdG8gc3RhbmRhcmRpemUgUE5FIG5l
Z290aWF0aW9uIGlmIHlvdSB1c2UgbXVsdGlwbGUgcGxhdGZvcm1zLCBidXQgc3VyZWx5IHlvdSB3
aWxsIGJlIGp1c3QgZG9pbmcgdGhpcyBiZXR3ZWVuIFdpbmRvd3Mgc3lzdGVtcyBmb3IgYSB3aGls
ZSBpZiB5b3Ugc3RhcnQgdXNpbmcgUVVJQyBpbnNpZGUgdGhlIERDLiBUaGF0IHdvdWxkIGJlIGEg
Z3JlYXQgdGltZSB0byB1c2UgdmVyc2lvbmluZyB0byBydW4geW91ciBvd24gdmVyc2lvbiB3aXRo
aW4gdGhlIERDLCBhbmQgY29tcGFyZSB0aGUgY29zdCB0byBJRVRGIHYxLCBhbmQgc2VlIGlmIGl0
IGlzIHdvcnRoIHJlbW92aW5nIFBORS4gSSBob3BlIHlvdSBmaW5kIG90aGVyIGNvc3RzIHRoYXQg
YXJlIHdvcnRoIGVsaW1pbmF0aW5nIG9yIGNoYW5nZXMgdGhhdCBhcmUgd29ydGggbWFraW5nIHRv
IHRoZSBwcm90b2NvbCB0b28sIGFuZCB0aGF0IHRoZXkgYWxsIGJlY29tZSBwYXJ0IG9mIHN0YW5k
YXJkIFFVSUMgYXMgYSBjb25zZXF1ZW5jZS4gQnV0IGluIHRoZSBtZWFud2hpbGUsIEkgZG9uJ3Qg
c2VlIHdoeSBtYWtpbmcgaXQgb3B0aW9uYWwgaXMgbmVjZXNzYXJ5IHJpZ2h0IG5vdyB0byBhZGQg
UE5FIGF0IGFsbC4NCg0KT24gVHVlLCBNYXkgMSwgMjAxOCBhdCA0OjIyIFBNLCBSb2JlcnRvIFBl
b24gPGZlbml4QGZiLmNvbTxtYWlsdG86ZmVuaXhAZmIuY29tPj4gd3JvdGU6DQpJ4oCZZCBzdWdn
ZXN0IHdlIHN0YXJ0IHdvcmtpbmcgb24gaXQgbm93Lg0KVGhpcyBpcyBvbmx5IHBhcnRseSBhIGpv
a2Ug4pi6DQotPVINCg0KRnJvbTogUVVJQyA8cXVpYy1ib3VuY2VzQGlldGYub3JnPG1haWx0bzpx
dWljLWJvdW5jZXNAaWV0Zi5vcmc+PiBvbiBiZWhhbGYgb2YgUm9iZXJ0byBQZW9uIDxmZW5peEBm
Yi5jb208bWFpbHRvOmZlbml4QGZiLmNvbT4+DQpEYXRlOiBUdWVzZGF5LCBNYXkgMSwgMjAxOCBh
dCA0OjIxIFBNDQpUbzogUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gPHByYXZiPTQwbWljcm9zb2Z0
LmNvbUBkbWFyYy5pZXRmLm9yZzxtYWlsdG86NDBtaWNyb3NvZnQuY29tQGRtYXJjLmlldGYub3Jn
Pj4sIFRlZCBIYXJkaWUgPHRlZC5pZXRmQGdtYWlsLmNvbTxtYWlsdG86dGVkLmlldGZAZ21haWwu
Y29tPj4NCkNjOiAiU2FseiwgUmljaCIgPHJzYWx6QGFrYW1haS5jb208bWFpbHRvOnJzYWx6QGFr
YW1haS5jb20+PiwgQmVuamFtaW4gS2FkdWsgPGJrYWR1a0Bha2FtYWkuY29tPG1haWx0bzpia2Fk
dWtAYWthbWFpLmNvbT4+LCBJRVRGIFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc8bWFpbHRvOnF1aWNA
aWV0Zi5vcmc+Pg0KU3ViamVjdDogW1BvdGVudGlhbCBTcG9vZl0gUmU6IEdldHRpbmcgdG8gY29u
c2Vuc3VzIG9uIHBhY2tldCBudW1iZXIgZW5jcnlwdGlvbg0KDQpZdXAuIEkga25vdy4NClByaXNt
IHdhcyBleWUtb3BlbmluZyBwYXJ0aWFsbHkgYmVjYXVzZSBvZiB0aGUgZmFjdCB0aGF0IHRoZSBw
YWNrZXRzIHdlcmUgbm90IGdvaW5nIGFjcm9zcyB0aGUgaW50ZXJuZXQsIGJ1dCByYXRoZXIgd2l0
aGluIGEgc2VjdXJlIG5ldHdvcmsuDQoNCkkgYmVsaWV2ZSB0aGF0IG9zc2lmaWNhdGlvbiBhbG9u
ZSBpcyBhIGdvb2QgZW5vdWdoIHJlYXNvbiB0byBkbyBQTkUuDQpUaGUgY2hlcnJ5IGZvciBtZSBp
cyB0aGF0IGl0LCBhbG9uZyB3aXRoIG90aGVyIGFjdGlvbnMvbWl0aWdhdGlvbnMsIG1ha2VzIGxp
bmthYmlsaXR5IG1vcmUgZGlmZmljdWx0IGZvciBtYWxpY2lvdXMgYWN0b3JzLg0KQ1JJTUUgYW5k
IHJlbGF0ZWQgd2FzIGV5ZS1vcGVuaW5nIGJlY2F1c2UgaXQgZXhwb3NlZCB0aGUgcG93ZXIgb2Yg
dGhlIG9ic2VydmFibGUgc2lkZS1jaGFubmVsLg0KDQotPVINCg0KRnJvbTogUVVJQyA8cXVpYy1i
b3VuY2VzQGlldGYub3JnPG1haWx0bzpxdWljLWJvdW5jZXNAaWV0Zi5vcmc+PiBvbiBiZWhhbGYg
b2YgUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gPHByYXZiPTQwbWljcm9zb2Z0LmNvbUBkbWFyYy5p
ZXRmLm9yZzxtYWlsdG86NDBtaWNyb3NvZnQuY29tQGRtYXJjLmlldGYub3JnPj4NCkRhdGU6IFR1
ZXNkYXksIE1heSAxLCAyMDE4IGF0IDk6MzUgQU0NClRvOiBUZWQgSGFyZGllIDx0ZWQuaWV0ZkBn
bWFpbC5jb208bWFpbHRvOnRlZC5pZXRmQGdtYWlsLmNvbT4+LCBSb2JlcnRvIFBlb24gPGZlbml4
QGZiLmNvbTxtYWlsdG86ZmVuaXhAZmIuY29tPj4NCkNjOiAiU2FseiwgUmljaCIgPHJzYWx6QGFr
YW1haS5jb208bWFpbHRvOnJzYWx6QGFrYW1haS5jb20+PiwgQmVuamFtaW4gS2FkdWsgPGJrYWR1
a0Bha2FtYWkuY29tPG1haWx0bzpia2FkdWtAYWthbWFpLmNvbT4+LCBJRVRGIFFVSUMgV0cgPHF1
aWNAaWV0Zi5vcmc8bWFpbHRvOnF1aWNAaWV0Zi5vcmc+Pg0KU3ViamVjdDogUkU6IEdldHRpbmcg
dG8gY29uc2Vuc3VzIG9uIHBhY2tldCBudW1iZXIgZW5jcnlwdGlvbg0KDQpUaGlzIGlzIG5vdCBh
Ym91dCBwdXR0aW5nIHBsYWludGV4dCBkYXRhIG9uIHRoZSBuZXR3b3JrLCB0aGlzIGlzIGFib3V0
IG5vdCBhZGRpbmcgUE5FIHdoaWNoIGlzIGludGVuZGVkIGZvciBwcmV2ZW50aW5nIG9zc2lmaWNh
dGlvbi4gU28gSSBkb27igJl0IHVuZGVyc3RhbmQgd2hhdCB0aGUgdHJ1c3QgaXNzdWUgYmVpbmcg
cmVmZXJyZWQgdG8gaXMgaW4gY2FzZSBvZiB0aGUgcmFyZSBtaXNjb25maWcuDQoNCldpdGhpbiBh
IERDIHNldmVyYWwgdGhpbmdzIGFyZSBkaWZmZXJlbnQg4oCTIHRoZSBkZXBsb3ltZW50IG1heSBu
ZWVkIGRpZmZlcmVudCBjb25nZXN0aW9uIGNvbnRyb2wgbGlrZSBEQ1RDUCwgZGlmZmVyZW50IHNl
dHRpbmdzIGZvciB2YXJpb3VzIHRyYW5zcG9ydCBwYXJhbWV0ZXJzIChsaWtlIG1pbnJ0byBhbmQg
bWF4IEFDSyBkZWxheSksIGxhcmdlciBmbG93IGNvbnRyb2wgd2luZG93IGV0Yy4gVGhpcyBpcyB0
cnVlIGZvciBUQ1AgdG9kYXkuIFRoZSBvdXQgb2YgYm94IGRlZmF1bHQgdXNlcyB0aGUgaGFuZHNo
YWtlIFJUVCB0byBtYWtlIGEgZGV0ZXJtaW5hdGlvbiBvZiB3aGF04oCZcyBpbnRyYS1EQyBidXQg
dGhlcmUgaXMgcmljaCBjb25maWd1cmF0aW9uIHRvIG92ZXJyaWRlIHRoZSBkZWZhdWx0IGFuZCBz
ZXQgaXQgYmFzZWQgb24gNC10dXBsZSBmaWx0ZXJzLg0KDQpBbmQgdGhlcmUgd29ya2xvYWRzIGxp
a2UgY2xvdWQgc3RvcmFnZSBhbmQgbGl2ZSBtaWdyYXRpb24gdGhhdCBhcmUgYnkgdmlydHVlIG9m
IGRlcGxveW1lbnQgaW50cmEtREMuIFRoZXNlIGNhbm5vdCBiZSBsb2FkIHNoaWZ0ZWQgYXMgdGhl
eSB1c2UgcHJpdmF0ZSBJUCBhZGRyZXNzIHNwYWNlLg0KDQpGcm9tOiBUZWQgSGFyZGllIFttYWls
dG86dGVkLmlldGZAZ21haWwuY29tPG1haWx0bzp0ZWQuaWV0ZkBnbWFpbC5jb20+XQ0KU2VudDog
VHVlc2RheSwgTWF5IDEsIDIwMTggODo1NSBBTQ0KVG86IFJvYmVydG8gUGVvbiA8ZmVuaXhAZmIu
Y29tPG1haWx0bzpmZW5peEBmYi5jb20+Pg0KQ2M6IFNhbHosIFJpY2ggPHJzYWx6QGFrYW1haS5j
b208bWFpbHRvOnJzYWx6QGFrYW1haS5jb20+PjsgQmVuamFtaW4gS2FkdWsgPGJrYWR1a0Bha2Ft
YWkuY29tPG1haWx0bzpia2FkdWtAYWthbWFpLmNvbT4+OyBQcmF2ZWVuIEJhbGFzdWJyYW1hbmlh
biA8cHJhdmJAbWljcm9zb2Z0LmNvbTxtYWlsdG86cHJhdmJAbWljcm9zb2Z0LmNvbT4+OyBJRVRG
IFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc8bWFpbHRvOnF1aWNAaWV0Zi5vcmc+Pg0KU3ViamVjdDog
UmU6IEdldHRpbmcgdG8gY29uc2Vuc3VzIG9uIHBhY2tldCBudW1iZXIgZW5jcnlwdGlvbg0KDQpP
biBUdWUsIE1heSAxLCAyMDE4IGF0IDg6MTMgQU0sIFJvYmVydG8gUGVvbiA8ZmVuaXhAZmIuY29t
PG1haWx0bzpmZW5peEBmYi5jb20+PiB3cm90ZToNCkFsc28sIFByaXNtLg0KDQotPVINCg0KDQoN
ClRoYXQncyBhIGxpdHRsZSBtb3JlIHN1Y2NpbmN0IHRoYW4gSSB3b3VsZCBiZSwgYnV0IHllcy4g
IEhvdyBkb2VzIGFuIGFwcGxpY2F0aW9uIGtub3cgdGhhdCB0aGUgZmxvdyBpdCBpcyBpbml0aWF0
aW5nIHdpbGwgdHJhdmVyc2UgYSB0b3BvbG9neSB0aGF0IGlzIGRlZW1lZCB0byBiZSB3aXRoaW4g
YSBjb250cm9sbGVkIGVudmlyb25tZW50PyAgWW91IGNhbiBzYXkgImNvbmZpZ3VyYXRpb24iIGJ1
dCBJIGZlYXIgaXQgd2lsbCB0dXJuIHVwIG9uIGEgcG9zdC1pdCAgPGh0dHBzOi8vbmEwMS5zYWZl
bGlua3MucHJvdGVjdGlvbi5vdXRsb29rLmNvbS8/dXJsPWh0dHBzJTNBJTJGJTJGdXJsZGVmZW5z
ZS5wcm9vZnBvaW50LmNvbSUyRnYyJTJGdXJsJTNGdSUzRGh0dHBzLTNBX19uYTAxLnNhZmVsaW5r
cy5wcm90ZWN0aW9uLm91dGxvb2suY29tXy0zRnVybC0zRGh0dHBzLTI1M0EtMjUyRi0yNTJGaS5r
aW5qYS0yRGltZy5jb20tMjUyRmdhd2tlci0yRG1lZGlhLTI1MkZpbWFnZS0yNTJGdXBsb2FkLTI1
MkZzLTJELTJERWR1NkxQdTktMkQtMkQtMjUyRmMtNUZzY2FsZS0yNTJDZi01RmF1dG8tMjUyQ2Zs
LTVGcHJvZ3Jlc3NpdmUtMjUyQ3EtNUY4MC0yNTJDdy01RjgwMC0yNTJGMTk0dGhidHllbmNzMGpw
Zy5qcGctMjZkYXRhLTNEMDItMjU3QzAxLTI1N0NwcmF2Yi0yNTQwbWljcm9zb2Z0LmNvbS0yNTdD
NGRhNDRlOGFjMWRmNDcwOGFkODgwOGQ1YWY3YmZjYTgtMjU3QzcyZjk4OGJmODZmMTQxYWY5MWFi
MmQ3Y2QwMTFkYjQ3LTI1N0MxLTI1N0MxLTI1N0M2MzY2MDc4Njk0MTEyNTg5NzYtMjZzZGF0YS0z
RFByb2xTSGtiRjJTZ01IM3FkUU4tMjUyQlpGb2tYdnNFQmYtMjUyRjNvOU1hVW5pbDBnOC0yNTNE
LTI2cmVzZXJ2ZWQtM0QwJTI2ZCUzRER3TUdhUSUyNmMlM0Q1VkQwUlR0TmxUaDN5Y2Q0MWIzTVV3
JTI2ciUzREMwc1VvLUxGTkJhWWZ5b2FDc2Y2VEElMjZtJTNEVHVWZnp5cG8tQ1pMbzUyMmxnTVJy
THBLeGNGYUh2VzlrZE5TSTU3bFhUMCUyNnMlM0RCeTJkX3RvN1h6TEVnQUwzT3I5Y1pjMkF5a3ll
LVBaRWVuRlFEdmlBVWx3JTI2ZSUzRCZkYXRhPTAyJTdDMDElN0NwcmF2YiU0MG1pY3Jvc29mdC5j
b20lN0NjNTBmOTFiYzNlYzc0NDU0NDFkZTA4ZDVhZmM0ZDc5ZSU3QzcyZjk4OGJmODZmMTQxYWY5
MWFiMmQ3Y2QwMTFkYjQ3JTdDMSU3QzAlN0M2MzY2MDgxODIzMzU2MzMyODImc2RhdGE9JTJGNkpF
YnVDbmxXYmlVWTh1YUVzT0dkR05XUHNiMktWT2lWS0gwVWdkVThVJTNEJnJlc2VydmVkPTA+IGlm
IHlvdSBkby4gIExvYWRzIHNoaWZ0LCByZXNvdXJjZXMgbW92ZSwgYW5kIHN1ZGRlbmx5IHlvdSBm
aW5kIHRoYXQgaG9zdCB3aGljaCB1c2VkIHRvIGJlIGluIHRoZSBzYW1lIHJhY2ssIGJlaW5nIGRv
d24sIGhhcyBsb2FkLXNoaWZ0ZWQgdG8gdGhlIG5leHQgaW5zdGFuY2UsICBpbiBhIGRhdGFjZW50
ZXIgNTAwIG1pbGVzIGF3YXkgYWNyb3NzIGEgdmVyeSBkaWZmZXJlbnQgbmV0d29yay4NCg0KTWFu
eSBtb2Rlcm4gZGVwbG95bWVudHMgYXJlIGFsc28gaW4gc29tZW9uZSBlbHNlJ3MgZGF0YSBjZW50
ZXIsIHNvIHNheWluZyAiRGF0YSBjZW50ZXIgbmV0d29ya3MiIGRvZXNuJ3Qgc2F5IG11Y2ggYWJv
dXQgd2h5IHlvdSdyZSB0cnVzdGluZyB0aGUgbmV0d29yayBpbnNpZGUuDQpUZWQNCg0KU2VudCB2
aWEgdGhlIFNhbXN1bmcgR2FsYXh5IFM3LCBhbiBBVCZUIDRHIExURSBzbWFydHBob25lDQoNCg0K
LS0tLS0tLS0gT3JpZ2luYWwgbWVzc2FnZSAtLS0tLS0tLQ0KRnJvbTogIlNhbHosIFJpY2giIDxy
c2Fsej00MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmc8bWFpbHRvOjQwYWthbWFpLmNvbUBkbWFy
Yy5pZXRmLm9yZz4+DQpEYXRlOiA1LzEvMTggNToyNSBBTSAoR01ULTA4OjAwKQ0KVG86IEJlbmph
bWluIEthZHVrIDxia2FkdWs9NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnPG1haWx0bzo0MGFr
YW1haS5jb21AZG1hcmMuaWV0Zi5vcmc+PiwgUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gPHByYXZi
PTQwbWljcm9zb2Z0LmNvbUBkbWFyYy5pZXRmLm9yZzxtYWlsdG86NDBtaWNyb3NvZnQuY29tQGRt
YXJjLmlldGYub3JnPj4NCkNjOiBJRVRGIFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc8bWFpbHRvOnF1
aWNAaWV0Zi5vcmc+Pg0KU3ViamVjdDogUmU6IEdldHRpbmcgdG8gY29uc2Vuc3VzIG9uIHBhY2tl
dCBudW1iZXIgZW5jcnlwdGlvbg0KDQogICAgPiBJIGRpc2FncmVlIHRoYXQgd2UgbmVlZCBhbnkg
bW9yZSBkYXRhIGZvciBub3QgZG9pbmcgUE5FIGluIHRoZSBkYXRhY2VudGVyLiBXaHkgd291bGQg
d2UgYWRkIGFuIGV4dHJhIGVuY3J5cHQtZGVjcnlwdCBzdGVwIGZvciBubyBvYnZpb3VzIGJlbmVm
aXQ/DQoNCkkgYW0gY29uY2VybmVkIHRoYXQgcGVvcGxlIHdpbGwgbWlzLWludGVycHJldCB0aGUg
bWVhbmluZyBvZiBhIGRhdGFjZW50ZXIsIGFuZCB0aGluayB0aGF0IGEgYnVuY2ggb2Ygc2VydmVy
cywgb3IgZXZlbiBhIHJhY2ssIGluIGFuIG9wZW4gY29sbyBzcGFjZSBpcyBhICJkYXRhY2VudGVy
LiIgIENvbXB1dGVycyBrZWVwIGdldHRpbmcgZmFzdGVyLg0KDQoNCg==

--_000_DB6PR10MB17660511ED052322C7BD4F17AC800DB6PR10MB1766EURP_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIGNvbnRlbnQ9InRleHQvaHRtbDsgY2hh
cnNldD11dGYtOCI+DQo8bWV0YSBuYW1lPSJHZW5lcmF0b3IiIGNvbnRlbnQ9Ik1pY3Jvc29mdCBX
b3JkIDE1IChmaWx0ZXJlZCBtZWRpdW0pIj4NCjxzdHlsZT4NCjwhLS0NCkBmb250LWZhY2UNCgl7
Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCJ9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNh
bGlicml9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJTZWdvZSBVSSBFbW9qaSJ9DQpwLk1z
b05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowaW47DQoJbWFy
Z2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNh
bGlicmkiLHNhbnMtc2VyaWZ9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe2NvbG9yOmJs
dWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZX0NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBl
cmxpbmtGb2xsb3dlZA0KCXtjb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGlu
ZX0NCnAubXNvbm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1hbDANCgl7bWFyZ2lu
LXJpZ2h0OjBpbjsNCgltYXJnaW4tbGVmdDowaW47DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250
LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZn0NCnNwYW4uRW1haWxTdHlsZTE4DQoJe2ZvbnQt
ZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHR9DQpzcGFuLkVt
YWlsU3R5bGUxOQ0KCXtmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3
aW5kb3d0ZXh0fQ0KLk1zb0NocERlZmF1bHQNCgl7Zm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMt
c2VyaWZ9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7bWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEu
MGlufQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXt9DQotLT4NCjwvc3R5bGU+DQo8L2hlYWQ+DQo8Ym9k
eSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGlkPSJjb21w
b3NlLWNvbnRhaW5lciIgaXRlbXNjb3BlPSIiIGl0ZW10eXBlPSJodHRwczovL3NjaGVtYS5vcmcv
RW1haWxNZXNzYWdlIiBzdHlsZT0iZGlyZWN0aW9uOmx0ciI+DQo8c3BhbiBpdGVtcHJvcD0iY3Jl
YXRvciIgaXRlbXNjb3BlPSIiIGl0ZW10eXBlPSJodHRwczovL3NjaGVtYS5vcmcvT3JnYW5pemF0
aW9uIj48c3BhbiBpdGVtcHJvcD0ibmFtZSI+PC9zcGFuPjwvc3Bhbj4NCjxkaXY+DQo8ZGl2Pg0K
PGRpdiBzdHlsZT0iZGlyZWN0aW9uOmx0ciI+QSBkYXRhIGNlbnRlciBtaWdodCB1c2UgYW4gb3Zl
cmxheSBuZXR3b3JrIHdpdGggS3ViZXJuZXRlcyBvciBTd2FybSAtIHdoaWNoIG1pZ2h0IGxlYWQg
dG8gb3NzaWZpY2F0aW9uLjwvZGl2Pg0KPGRpdj48YnI+DQo8L2Rpdj4NCjxkaXYgc3R5bGU9ImRp
cmVjdGlvbjpsdHIiPkFuIHVuZW5jcnlwdGVkIHBlciBDSUQgUE4gd2l0aCBjaGVhcCBtdWx0aXBs
aWNhdGlvbiBwZXJtdXRhdGlvbiBpcyBhbm90aGVyIG9wdGlvbiBjb21wYXJlZCB0byAxMDc5Ljwv
ZGl2Pg0KPC9kaXY+DQo8ZGl2Pjxicj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iYWNvbXBsaV9zaWdu
YXR1cmUiPjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxociB0YWJpbmRleD0iLTEiIHN0eWxlPSJk
aXNwbGF5OmlubGluZS1ibG9jazsgd2lkdGg6OTglIj4NCjxkaXYgaWQ9ImRpdlJwbHlGd2RNc2ci
IGRpcj0ibHRyIj48Zm9udCBmYWNlPSJDYWxpYnJpLCBzYW5zLXNlcmlmIiBjb2xvcj0iIzAwMDAw
MCIgc3R5bGU9ImZvbnQtc2l6ZToxMXB0Ij48Yj5Gcm9tOjwvYj4gUVVJQyAmbHQ7cXVpYy1ib3Vu
Y2VzQGlldGYub3JnJmd0OyBvbiBiZWhhbGYgb2YgUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gJmx0
O3ByYXZiPTQwbWljcm9zb2Z0LmNvbUBkbWFyYy5pZXRmLm9yZyZndDs8YnI+DQo8Yj5TZW50Ojwv
Yj4gV2VkbmVzZGF5LCBNYXkgMiwgMjAxOCA0OjAyOjM3IEFNPGJyPg0KPGI+VG86PC9iPiBKYW5h
IEl5ZW5nYXI7IFJvYmVydG8gUGVvbjxicj4NCjxiPkNjOjwvYj4gU2FseiwgUmljaDsgVGVkIEhh
cmRpZTsgSUVURiBRVUlDIFdHOyBCZW5qYW1pbiBLYWR1azxicj4NCjxiPlN1YmplY3Q6PC9iPiBS
RTogW1BvdGVudGlhbCBTcG9vZl0gUmU6IEdldHRpbmcgdG8gY29uc2Vuc3VzIG9uIHBhY2tldCBu
dW1iZXIgZW5jcnlwdGlvbjwvZm9udD4NCjxkaXY+Jm5ic3A7PC9kaXY+DQo8L2Rpdj4NCjxkaXY+
DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+V2UgY2Fu
IGdldCAoMSkgZG9uZSBidXQgSSBkaXNhZ3JlZSB0aGF0IHdlIGNhbiBkZWNvdXBsZSAoMikuIEl0
IGRvZXNu4oCZdCBtYWtlIHNlbnNlIHRvIHJlcXVpcmUgcGVyZm9ybWFuY2Ugb3ZlcmhlYWQgYWxs
IHRoZSB0aW1lIHdpdGggbm8gYmVuZWZpdC4gRm9yIHRoZSBJbnRlcm5ldCwgUE5FIGNhbiBwcmV2
ZW50IG9zc2lmaWNhdGlvbiBzbyBpdCBpcyBzZWVuIGFzIGEgcmVhc29uYWJsZSB0cmFkZS1vZmYu
IEZvcg0KIHRoZSBkYXRhY2VudGVyLCB0aGVyZSBpcyBubyBrbm93biBiZW5lZml0LCBvbmx5IGNv
c3QuIDwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPldlIGtub3cgdGhhdCB0aGVyZSBpcyBhIENQVSBjb3N0LCB0aGlzIGlzIG5vdCBzcGVj
dWxhdGlvbi4gRG9lc27igJl0IG1hdHRlciBpZiB0aGUgY29zdCBpcyAxJSBvciAxMCUuIEhhcmR3
YXJlIGltcGxlbWVudGVycyBoYXZlIGFsc28gcmFpc2VkIGNvbmNlcm5zLiBFdmVyeSBDUFUgY3lj
bGUgd2Ugc3BlbmQgb24gdGhpbmdzIHRoYXQgYWRkIG5vIHZhbHVlIHRvIHRoZSB1c2VyIHNob3Vs
ZCBiZSBxdWVzdGlvbmVkLg0KIEV2ZXJ5IGV4dHJhIGluc3RydWN0aW9uIHdlIGV4ZWN1dGUgaW4g
dGhlIGhvdCBkYXRhIHBhdGggbGVhdmVzIGxlc3MgQ1BVIGZvciB3b3JrbG9hZHMsIGJ1cm5zIG1v
cmUgcG93ZXIgYW5kIG1ha2VzIGZvciBhIHdvcnNlIGNvbXBhcmlzb24gd2l0aCBIVFRQUyBvdmVy
IFRDUC4gVGhlIHNhbWUgYXJndW1lbnQgYXMgcHJpdmFjeSBob2xlcyBob2xkcyBoZXJlIOKAkyBq
dXN0IGJlY2F1c2UgdGhlcmUgYXJlIHNvbWUgZXhpc3RpbmcgcGVyZiBib3R0bGVuZWNrcw0KIGRv
ZXNu4oCZdCBtZWFuIHdlIGFkZCBtb3JlLCBwYXJ0aWN1bGFybHkgb25lcyB3ZSBjYW5ub3QgbWl0
aWdhdGUuIEkgc2FpZCBpdCBiZWZvcmUgdGhhdCB0aGVyZSBhcmUgbG90cyBvZiB3YXlzIHdlIGNh
biBpbXByb3ZlIFVEUCBwZXJmIGJ1dCBJIGRvbuKAmXQga25vdyBvZiBhbnkgdGVjaG5pcXVlIGZv
ciByZWR1Y2luZyBjcnlwdG8gQ1BVIGNvc3Qgb3RoZXIgdGhhbiBoYXJkd2FyZSBvZmZsb2FkLjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PlRoZSBjb3N0IGlzIGNlcnRhaW5seSB3b3J0aCBzYXZpbmcgd2l0aCBzb21ldGhpbmcgYXMgc2lt
cGxlIGFzIGEgbmVnb3RpYXRpb24gbWVjaGFuaXNtLiBBbSBJIG1pc3Npbmcgc29tZXRoaW5nIGFi
b3V0IGEgdHJhbnNwb3J0IHBhcmFtZXRlciBiZWluZyBjb21wbGljYXRlZCB0byBpbXBsZW1lbnQ/
IEltcGxlbWVudGF0aW9ucyBhcmUgZnJlZSB0byBzdXBwb3J0IG9ubHkgUE5FIGFuZCBub3QgbmVn
b3RpYXRlIGFueXRoaW5nDQogZWxzZS4gVGhlcmUgaXMgYWN0dWFsbHkgYW4gZXZlbiBzaW1wbGVy
IG1lY2hhbmlzbSBpZiBhIHRyYW5zcG9ydCBwYXJhbWV0ZXIgaXMgZGVlbWVkIGFzIGNvc3RseTog
aWYgdGhlIHBlZXIgc2VuZHMgUE4gPSAwIGluIHRoZSBDSSwgdGhlbiBpdHMgcmVxdWVzdGluZyBu
byBQTkUgYW5kIHRoZSByZWNlaXZlciBjYW4gY2hvb3NlIHRvIHByb2NlZWQgb3IgZHJvcCBhbmQg
Zm9yY2UgVENQIGZhbGwgYmFjay4gVGhpcyBzaG91bGQgdGFrZSBvbmx5IGFuDQogZXh0cmEgaWYg
Y2hlY2sgb24gdGhlIHJlY2VpdmVyIENJIHByb2Nlc3NpbmcgbG9naWMgdG8gaW1wbGVtZW50LiBJ
IGFtIGFzc3VtaW5nIGhlcmUgdGhhdCBQTkUgb24gaW5wdXQgb2YgMCB3aWxsIG5vdCBwcm9kdWNl
IDAgc28gaXTigJlzIGEgc2FmZSBzZW50aW5lbCB2YWx1ZS4NCjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPiZuYnNwOzwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPkZyb206PC9iPiBKYW5h
IEl5ZW5nYXIgW21haWx0bzpqcmkuaWV0ZkBnbWFpbC5jb21dIDxicj4NCjxiPlNlbnQ6PC9iPiBU
dWVzZGF5LCBNYXkgMSwgMjAxOCA1OjM3IFBNPGJyPg0KPGI+VG86PC9iPiBSb2JlcnRvIFBlb24g
Jmx0O2Zlbml4QGZiLmNvbSZndDs8YnI+DQo8Yj5DYzo8L2I+IFByYXZlZW4gQmFsYXN1YnJhbWFu
aWFuICZsdDtwcmF2YkBtaWNyb3NvZnQuY29tJmd0OzsgVGVkIEhhcmRpZSAmbHQ7dGVkLmlldGZA
Z21haWwuY29tJmd0OzsgU2FseiwgUmljaCAmbHQ7cnNhbHpAYWthbWFpLmNvbSZndDs7IEJlbmph
bWluIEthZHVrICZsdDtia2FkdWtAYWthbWFpLmNvbSZndDs7IElFVEYgUVVJQyBXRyAmbHQ7cXVp
Y0BpZXRmLm9yZyZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFtQb3RlbnRpYWwgU3Bvb2Zd
IFJlOiBHZXR0aW5nIHRvIGNvbnNlbnN1cyBvbiBwYWNrZXQgbnVtYmVyIGVuY3J5cHRpb248L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+SSdsbCB0cnkgdG8gc3VtbWFyaXplIG15IHBvc2l0aW9uIG9uICMxMDc5LiBJIHNlZSB0
d28gcG9pbnRzOjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4xLiBQTkUgd2lsbCBo
ZWxwIGFnYWluc3Qgb3NzaWZpY2F0aW9uIGFuZCBhbHNvLCBhbGJlaXQgdG8gYSBsaW1pdGVkIGV4
dGVudCwgbGlua2FiaWxpdHkuPC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+Mi4gUE5FIGhhcyBhIENQVSBjb3N0LiBXaGlsZSB3ZSBjYW4gc3BlY3VsYXRlLCB3ZSBzdGls
bCBkb24ndCAqa25vdyogd2hhdCB0aGlzIGNvc3Qgd2lsbCBiZSBpbiB0aGUgY29udGV4dCBvZiBk
ZXBsb3ltZW50LCBhbmQgd2hldGhlciB0aGlzIGNvc3Qgd2lsbCBiZSB0aGUgc2hvdy1zdG9wcGVy
Lg0KPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7IGZvbnQtZmFtaWx5OiZxdW90O0FyaWFs
JnF1b3Q7LHNhbnMtc2VyaWY7IGNvbG9yOiMyMjIyMjI7IGJhY2tncm91bmQ6d2hpdGUiPg0KUE5F
J3MgQ1BVIGNvc3QgbWF5IG9yIG1heSBub3QgYmUgYW1lbGlvcmF0ZWQgYnkgTklDIGltcGxlbWVu
dGF0aW9uLiBXZSBzaG91bGQgYWxsb3cgUE5FIG5lZ290aWFiaWxpdHkgd2hlbiB3ZSBoYXZlIGVz
dGFibGlzaGVkIHRoYXQgdGhpcyBjb3N0IGlzIHdvcnRoIHNhdmluZy4mbmJzcDs8L3NwYW4+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+TXkgc2Vuc2UgaXMgdGhhdCB3ZSBhZ3JlZSBv
biAoMSkuIFRoaXMgaXMgd2hhdCAjMTA3OSBpcyBkb2luZywgc28gd2Ugc2hvdWxkIHNlcGFyYXRl
IHRoZSB0d28gcXVlc3Rpb25zIGFuZCBnZXQgKDEpIGRvbmUuIFdoZXRoZXIgd2UgZG8gKDIpIG9y
IG5vdCBpcyBiZWluZyBkaXNjdXNzZWQgb24gdGhpcyB0aHJlYWQsIGFuZCBJIHRoaW5rIHdlIGNh
biBjb250aW51ZSwgYnV0ICMxMDc5IHNob3VsZCBiZSBpbmRlcGVuZGVudGx5DQogc3VibWl0dGVk
LjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkZXSVcsJm5ic3A7PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMi4wcHQ7IGZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2Vy
aWY7IGNvbG9yOiMyMjIyMjI7IGJhY2tncm91bmQ6d2hpdGUiPkkgYmVsaWV2ZSB0aGF0IHdlIHdh
bnQgdG8gaXRlcmF0ZSBvbiB2ZXJzaW9ucywgYW5kIHRoYXQgd2Ugd2lsbCB3YW50IHRvIGdldCBh
IHYyIG91dCBhcyBzb29uIGFzIHdlIGhhdmUgdGhpbmdzIHRvIGdldCBkZXBsb3llZCB0aGF0IGxl
ZnQNCiBwZW5kaW5nIGluIHYxLjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj4mbmJzcDs8L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij4mbmJzcDs8L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaG91Z2h0
cyBvbiBpbnRyYS1EQyBRVUlDLCByZWxhdGVkIHRvIHBvaW50ICgyKSBmb2xsb3c6PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7IGZv
bnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7IGNvbG9yOiMyMjIyMjI7IGJh
Y2tncm91bmQ6d2hpdGUiPkkgZG9uJ3QgdGhpbmsgd2UnbGwgcmVhY2ggYSBtZWFuaW5nZnVsIGVu
ZCB0byB0aGlzIGRpc2N1c3Npb24gYnkgZ2V0dGluZyBpbnRvIHNlY3VyaXR5IGZvciBpbnRyYS1E
QyBwcm90b2NvbHMuJm5ic3A7PC9zcGFuPkkgdW5kZXJzdGFuZCB0aGF0IHRoZXJlDQogbWF5IGJl
IHNpdHVhdGlvbnMgd2hlcmUgb25lIG1heSBoYXZlIGZhaXIgY2VydGFpbnR5IGFib3V0IHRoZSBk
ZXBsb3ltZW50IGNvbnRleHQgYW5kIGdpdmVuIHRoYXQgdGhlIHNlY3VyaXR5IHRyYWRlb2ZmIGlz
bid0IHRoZSBzYW1lIGFzIGRpc2FibGluZyBUTFMsIHRoZSBiYXIgd2lsbCBiZSBzdWJzdGFudGlh
bGx5IGxvd2VyIGZvciBkaXNhYmxpbmcgUE5FLiZuYnNwOzwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDsgZm9udC1mYW1p
bHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjsgY29sb3I6IzIyMjIyMiI+T24gUVVJQyBp
biBpbnRyYS1EQyBlbnZpcm9ubWVudHM6Jm5ic3A7PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0OyBmb250
LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmOyBjb2xvcjojMjIyMjIyIj4xLiBB
cyBJZ29yIG5vdGVkLCB0aGUgdmFsdWUgb2YgUVVJQyBpbiB0aGUgaW50cmEtREMgZW52aXJvbm1l
bnRzIGlzIHVuY2VydGFpbiwgYW5kIEknbSBub3QgeWV0IHN1cmUgdGhhdCBjb21wcm9taXNpbmcg
b24gUE5FIGZvciBhbiB1bmtub3duIGNvc3QgaW4gYW4gdW5jZXJ0YWluDQogZGVwbG95bWVudCBj
b250ZXh0IGlzIG5lY2Vzc2FyaWx5IHVzZWZ1bC4mbmJzcDs8L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7
IGZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7IGNvbG9yOiMyMjIyMjIi
PjIuIFNlcGFyYXRlbHksIEkgcmVtYWluIHVuY29udmluY2VkLCBiYXNlZCBvbiBteSBleHBlcmll
bmNlIHdpdGggdHJ5aW5nIHRvIGdldCBRVUlDIHVzZWQgZm9yIERDIHRyYW5zcG9ydCwgdGhhdCB0
aGlzIGNvc3QgaXMgZ29pbmcgdG8gYmUgYW4gaW1wb3J0YW50IGZhY3RvciBpbg0KIFFVSUMgYWRv
cHRpb24gd2l0aGluIERDcy4gSSBhZ3JlZSB0aGF0IENQVSBjb3N0IGlzIGEgZmFjdG9yLCBidXQg
dGhlcmUgYXJlIG11Y2ggYmlnZ2VyIHRoaW5ncyBoZXJlIHRoYXQgd2lsbCBuZWVkIGF0dGVudGlv
biAoc2VnbWVudGF0aW9uIG9mZmxvYWQsIHNtYWxsZXIgcmVjb3JkIHNpemVzLCB1c2Vyc3BhY2Ug
Y29zdHMpIHRoYXQgd2lsbCBkb21pbmF0ZSB3ZWxsIGJlZm9yZSB0aGlzIEFFUyBvcGVyYXRpb24g
YmVjb21lcyBhIGZhY3Rvci4gVGhpcw0KIGFsbCByZW1haW5zIHNwZWN1bGF0aW9uIHRob3VnaC48
L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4m
bmJzcDs8L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5QcmF2ZWVuOiBO
b3QgbWFraW5nIFBORSBvcHRpb25hbCByaWdodCBub3cgZG9lcyBub3QgbWVhbiB3ZSB3b24ndCBk
byBpdC4gSXQganVzdCBtZWFucyB0aGF0IGl0J3MgYW4gb3BlbiBxdWVzdGlvbi4gSSdtIG5vdCB5
ZXQgY29udmluY2VkIHRoYXQgaXQncyBhIGRlYmlsaXRhdGluZyBjb3N0IG9yIG9uZSBvZiB0aGUg
cHJvdmVyYmlhbCAmcXVvdDttaWxsaW9uIGN1dHMmcXVvdDsgdGhhdCB3aWxsIGtlZXAgaXQgZnJv
bSBnZXR0aW5nDQogZGVwbG95ZWQgaW50cmEtREMuIFlvdSBhcmUgcmlnaHQgdGhhdCB5b3UnbGwg
d2FudCB0byBzdGFuZGFyZGl6ZSBQTkUgbmVnb3RpYXRpb24gaWYgeW91IHVzZSBtdWx0aXBsZSBw
bGF0Zm9ybXMsIGJ1dCBzdXJlbHkgeW91IHdpbGwgYmUganVzdCBkb2luZyB0aGlzIGJldHdlZW4g
V2luZG93cyBzeXN0ZW1zIGZvciBhIHdoaWxlIGlmIHlvdSBzdGFydCB1c2luZyBRVUlDIGluc2lk
ZSB0aGUgREMuIFRoYXQgd291bGQgYmUgYSBncmVhdCB0aW1lIHRvDQogdXNlIHZlcnNpb25pbmcg
dG8gcnVuIHlvdXIgb3duIHZlcnNpb24gd2l0aGluIHRoZSBEQywgYW5kIGNvbXBhcmUgdGhlIGNv
c3QgdG8gSUVURiB2MSwgYW5kIHNlZSBpZiBpdCBpcyB3b3J0aCByZW1vdmluZyBQTkUuIEkgaG9w
ZSB5b3UgZmluZCBvdGhlciBjb3N0cyB0aGF0IGFyZSB3b3J0aCBlbGltaW5hdGluZyBvciBjaGFu
Z2VzIHRoYXQgYXJlIHdvcnRoIG1ha2luZyB0byB0aGUgcHJvdG9jb2wgdG9vLCBhbmQgdGhhdCB0
aGV5IGFsbCBiZWNvbWUNCiBwYXJ0IG9mIHN0YW5kYXJkIFFVSUMgYXMgYSBjb25zZXF1ZW5jZS4g
QnV0IGluIHRoZSBtZWFud2hpbGUsIEkgZG9uJ3Qgc2VlIHdoeSBtYWtpbmcgaXQgb3B0aW9uYWwg
aXMgbmVjZXNzYXJ5IHJpZ2h0IG5vdyB0byBhZGQgUE5FIGF0IGFsbC48L3A+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzwvcD4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5PbiBUdWUsIE1heSAxLCAyMDE4IGF0IDQ6MjIgUE0sIFJvYmVydG8g
UGVvbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmZlbml4QGZiLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmZl
bml4QGZiLmNvbTwvYT4mZ3Q7IHdyb3RlOjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6
bm9uZTsgYm9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDsgcGFkZGluZzowaW4gMGluIDBp
biA2LjBwdDsgbWFyZ2luLWxlZnQ6NC44cHQ7IG1hcmdpbi1yaWdodDowaW4iPg0KPGRpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iIj5J4oCZZCBzdWdnZXN0IHdlIHN0YXJ0
IHdvcmtpbmcgb24gaXQgbm93LjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSIiPlRo
aXMgaXMgb25seSBwYXJ0bHkgYSBqb2tlIDxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtT
ZWdvZSBVSSBFbW9qaSZxdW90OyxzYW5zLXNlcmlmIj4NCuKYujwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0iIj4tPVI8L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0iIj4mbmJzcDs8L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTsgYm9yZGVyLXRvcDpzb2xp
ZCAjQjVDNERGIDEuMHB0OyBwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSIiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0OyBjb2xv
cjpibGFjayI+RnJvbToNCjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7
IGNvbG9yOmJsYWNrIj5RVUlDICZsdDs8YSBocmVmPSJtYWlsdG86cXVpYy1ib3VuY2VzQGlldGYu
b3JnIiB0YXJnZXQ9Il9ibGFuayI+cXVpYy1ib3VuY2VzQGlldGYub3JnPC9hPiZndDsgb24gYmVo
YWxmIG9mIFJvYmVydG8gUGVvbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmZlbml4QGZiLmNvbSIgdGFy
Z2V0PSJfYmxhbmsiPmZlbml4QGZiLmNvbTwvYT4mZ3Q7PGJyPg0KPGI+RGF0ZTogPC9iPlR1ZXNk
YXksIE1heSAxLCAyMDE4IGF0IDQ6MjEgUE08YnI+DQo8Yj5UbzogPC9iPlByYXZlZW4gQmFsYXN1
YnJhbWFuaWFuICZsdDtwcmF2Yj08YSBocmVmPSJtYWlsdG86NDBtaWNyb3NvZnQuY29tQGRtYXJj
LmlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+NDBtaWNyb3NvZnQuY29tQGRtYXJjLmlldGYub3Jn
PC9hPiZndDssIFRlZCBIYXJkaWUgJmx0OzxhIGhyZWY9Im1haWx0bzp0ZWQuaWV0ZkBnbWFpbC5j
b20iIHRhcmdldD0iX2JsYW5rIj50ZWQuaWV0ZkBnbWFpbC5jb208L2E+Jmd0Ozxicj4NCjxiPkNj
OiA8L2I+JnF1b3Q7U2FseiwgUmljaCZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnJzYWx6QGFr
YW1haS5jb20iIHRhcmdldD0iX2JsYW5rIj5yc2FsekBha2FtYWkuY29tPC9hPiZndDssIEJlbmph
bWluIEthZHVrICZsdDs8YSBocmVmPSJtYWlsdG86YmthZHVrQGFrYW1haS5jb20iIHRhcmdldD0i
X2JsYW5rIj5ia2FkdWtAYWthbWFpLmNvbTwvYT4mZ3Q7LCBJRVRGIFFVSUMgV0cgJmx0OzxhIGhy
ZWY9Im1haWx0bzpxdWljQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+cXVpY0BpZXRmLm9yZzwv
YT4mZ3Q7PGJyPg0KPGI+U3ViamVjdDogPC9iPltQb3RlbnRpYWwgU3Bvb2ZdIFJlOiBHZXR0aW5n
IHRvIGNvbnNlbnN1cyBvbiBwYWNrZXQgbnVtYmVyIGVuY3J5cHRpb248L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9IiI+Jm5ic3A7PC9wPg0KPC9k
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iIj5ZdXAuIEkga25vdy48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iIj5QcmlzbSB3YXMgZXllLW9wZW5pbmcgcGFydGlhbGx5
IGJlY2F1c2Ugb2YgdGhlIGZhY3QgdGhhdCB0aGUgcGFja2V0cyB3ZXJlIG5vdCBnb2luZyBhY3Jv
c3MgdGhlIGludGVybmV0LCBidXQgcmF0aGVyIHdpdGhpbiBhIHNlY3VyZSBuZXR3b3JrLjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSIiPiZuYnNwOzwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSIiPkkgYmVsaWV2ZSB0aGF0IG9zc2lmaWNhdGlvbiBhbG9uZSBpcyBhIGdv
b2QgZW5vdWdoIHJlYXNvbiB0byBkbyBQTkUuPC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9IiI+VGhlIGNoZXJyeSBmb3IgbWUgaXMgdGhhdCBpdCwgYWxvbmcgd2l0aCBvdGhlciBhY3Rp
b25zL21pdGlnYXRpb25zLCBtYWtlcyBsaW5rYWJpbGl0eSBtb3JlIGRpZmZpY3VsdCBmb3IgbWFs
aWNpb3VzIGFjdG9ycy48YnI+DQpDUklNRSBhbmQgcmVsYXRlZCB3YXMgZXllLW9wZW5pbmcgYmVj
YXVzZSBpdCBleHBvc2VkIHRoZSBwb3dlciBvZiB0aGUgb2JzZXJ2YWJsZSBzaWRlLWNoYW5uZWwu
DQo8L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iIj48YnI+DQotPVI8L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iIj4mbmJzcDs8L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6
bm9uZTsgYm9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0OyBwYWRkaW5nOjMuMHB0IDBpbiAw
aW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSIiPjxiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTIuMHB0OyBjb2xvcjpibGFjayI+RnJvbToNCjwvc3Bhbj48L2I+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMi4wcHQ7IGNvbG9yOmJsYWNrIj5RVUlDICZsdDs8YSBocmVmPSJtYWls
dG86cXVpYy1ib3VuY2VzQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+cXVpYy1ib3VuY2VzQGll
dGYub3JnPC9hPiZndDsgb24gYmVoYWxmIG9mIFByYXZlZW4gQmFsYXN1YnJhbWFuaWFuICZsdDtw
cmF2Yj08YSBocmVmPSJtYWlsdG86NDBtaWNyb3NvZnQuY29tQGRtYXJjLmlldGYub3JnIiB0YXJn
ZXQ9Il9ibGFuayI+NDBtaWNyb3NvZnQuY29tQGRtYXJjLmlldGYub3JnPC9hPiZndDs8YnI+DQo8
Yj5EYXRlOiA8L2I+VHVlc2RheSwgTWF5IDEsIDIwMTggYXQgOTozNSBBTTxicj4NCjxiPlRvOiA8
L2I+VGVkIEhhcmRpZSAmbHQ7PGEgaHJlZj0ibWFpbHRvOnRlZC5pZXRmQGdtYWlsLmNvbSIgdGFy
Z2V0PSJfYmxhbmsiPnRlZC5pZXRmQGdtYWlsLmNvbTwvYT4mZ3Q7LCBSb2JlcnRvIFBlb24gJmx0
OzxhIGhyZWY9Im1haWx0bzpmZW5peEBmYi5jb20iIHRhcmdldD0iX2JsYW5rIj5mZW5peEBmYi5j
b208L2E+Jmd0Ozxicj4NCjxiPkNjOiA8L2I+JnF1b3Q7U2FseiwgUmljaCZxdW90OyAmbHQ7PGEg
aHJlZj0ibWFpbHRvOnJzYWx6QGFrYW1haS5jb20iIHRhcmdldD0iX2JsYW5rIj5yc2FsekBha2Ft
YWkuY29tPC9hPiZndDssIEJlbmphbWluIEthZHVrICZsdDs8YSBocmVmPSJtYWlsdG86YmthZHVr
QGFrYW1haS5jb20iIHRhcmdldD0iX2JsYW5rIj5ia2FkdWtAYWthbWFpLmNvbTwvYT4mZ3Q7LCBJ
RVRGIFFVSUMgV0cgJmx0OzxhIGhyZWY9Im1haWx0bzpxdWljQGlldGYub3JnIiB0YXJnZXQ9Il9i
bGFuayI+cXVpY0BpZXRmLm9yZzwvYT4mZ3Q7PGJyPg0KPGI+U3ViamVjdDogPC9iPlJFOiBHZXR0
aW5nIHRvIGNvbnNlbnN1cyBvbiBwYWNrZXQgbnVtYmVyIGVuY3J5cHRpb248L3NwYW4+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9IiI+Jm5ic3A7PC9wPg0K
PC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iIj48YSBuYW1lPSJtXy0xODM0MjAz
NjYyMDkyMjk2MTg1X19NYWlsT3JpZ2luYWxCb2R5Ij5UaGlzIGlzIG5vdCBhYm91dCBwdXR0aW5n
IHBsYWludGV4dCBkYXRhIG9uIHRoZSBuZXR3b3JrLCB0aGlzIGlzIGFib3V0IG5vdCBhZGRpbmcg
UE5FIHdoaWNoIGlzIGludGVuZGVkIGZvciBwcmV2ZW50aW5nIG9zc2lmaWNhdGlvbi4gU28gSSBk
b27igJl0IHVuZGVyc3RhbmQgd2hhdCB0aGUgdHJ1c3QgaXNzdWUNCiBiZWluZyByZWZlcnJlZCB0
byBpcyBpbiBjYXNlIG9mIHRoZSByYXJlIG1pc2NvbmZpZy4gPC9hPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSIiPiZuYnNwOzwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSIiPldpdGhpbiBhIERDIHNldmVyYWwgdGhpbmdzIGFyZSBkaWZmZXJlbnQg4oCTIHRoZSBkZXBs
b3ltZW50IG1heSBuZWVkIGRpZmZlcmVudCBjb25nZXN0aW9uIGNvbnRyb2wgbGlrZSBEQ1RDUCwg
ZGlmZmVyZW50IHNldHRpbmdzIGZvciB2YXJpb3VzIHRyYW5zcG9ydCBwYXJhbWV0ZXJzIChsaWtl
IG1pbnJ0byBhbmQgbWF4IEFDSyBkZWxheSksIGxhcmdlciBmbG93IGNvbnRyb2wgd2luZG93IGV0
Yy4gVGhpcw0KIGlzIHRydWUgZm9yIFRDUCB0b2RheS4gVGhlIG91dCBvZiBib3ggZGVmYXVsdCB1
c2VzIHRoZSBoYW5kc2hha2UgUlRUIHRvIG1ha2UgYSBkZXRlcm1pbmF0aW9uIG9mIHdoYXTigJlz
IGludHJhLURDIGJ1dCB0aGVyZSBpcyByaWNoIGNvbmZpZ3VyYXRpb24gdG8gb3ZlcnJpZGUgdGhl
IGRlZmF1bHQgYW5kIHNldCBpdCBiYXNlZCBvbiA0LXR1cGxlIGZpbHRlcnMuDQo8L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iIj4mbmJzcDs8L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0iIj5BbmQgdGhlcmUgd29ya2xvYWRzIGxpa2UgY2xvdWQgc3RvcmFnZSBhbmQgbGl2
ZSBtaWdyYXRpb24gdGhhdCBhcmUgYnkgdmlydHVlIG9mIGRlcGxveW1lbnQgaW50cmEtREMuIFRo
ZXNlIGNhbm5vdCBiZSBsb2FkIHNoaWZ0ZWQgYXMgdGhleSB1c2UgcHJpdmF0ZSBJUCBhZGRyZXNz
IHNwYWNlLjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSIiPiZuYnNwOzwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSIiPjxiPkZyb206PC9iPiBUZWQgSGFyZGllIFttYWls
dG86PGEgaHJlZj0ibWFpbHRvOnRlZC5pZXRmQGdtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPnRl
ZC5pZXRmQGdtYWlsLmNvbTwvYT5dDQo8YnI+DQo8Yj5TZW50OjwvYj4gVHVlc2RheSwgTWF5IDEs
IDIwMTggODo1NSBBTTxicj4NCjxiPlRvOjwvYj4gUm9iZXJ0byBQZW9uICZsdDs8YSBocmVmPSJt
YWlsdG86ZmVuaXhAZmIuY29tIiB0YXJnZXQ9Il9ibGFuayI+ZmVuaXhAZmIuY29tPC9hPiZndDs8
YnI+DQo8Yj5DYzo8L2I+IFNhbHosIFJpY2ggJmx0OzxhIGhyZWY9Im1haWx0bzpyc2FsekBha2Ft
YWkuY29tIiB0YXJnZXQ9Il9ibGFuayI+cnNhbHpAYWthbWFpLmNvbTwvYT4mZ3Q7OyBCZW5qYW1p
biBLYWR1ayAmbHQ7PGEgaHJlZj0ibWFpbHRvOmJrYWR1a0Bha2FtYWkuY29tIiB0YXJnZXQ9Il9i
bGFuayI+YmthZHVrQGFrYW1haS5jb208L2E+Jmd0OzsgUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4g
Jmx0OzxhIGhyZWY9Im1haWx0bzpwcmF2YkBtaWNyb3NvZnQuY29tIiB0YXJnZXQ9Il9ibGFuayI+
cHJhdmJAbWljcm9zb2Z0LmNvbTwvYT4mZ3Q7Ow0KIElFVEYgUVVJQyBXRyAmbHQ7PGEgaHJlZj0i
bWFpbHRvOnF1aWNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5xdWljQGlldGYub3JnPC9hPiZn
dDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IEdldHRpbmcgdG8gY29uc2Vuc3VzIG9uIHBhY2tl
dCBudW1iZXIgZW5jcnlwdGlvbjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSIiPiZu
YnNwOzwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iIj5PbiBUdWUsIE1h
eSAxLCAyMDE4IGF0IDg6MTMgQU0sIFJvYmVydG8gUGVvbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmZl
bml4QGZiLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmZlbml4QGZiLmNvbTwvYT4mZ3Q7IHdyb3RlOjwv
cD4NCjxkaXY+DQo8ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lOyBib3JkZXIt
bGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0OyBwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0OyBtYXJn
aW4tbGVmdDo0LjhwdDsgbWFyZ2luLXRvcDo1LjBwdDsgbWFyZ2luLXJpZ2h0OjBpbjsgbWFyZ2lu
LWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0iIj5BbHNvLCBQcmlzbS4mbmJzcDs8L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0iIj4mbmJzcDs8L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0iIj4tPVImbmJzcDs8L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iIj4mbmJzcDs8L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iIj4mbmJzcDs8L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9IiI+
Jm5ic3A7PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1h
cmdpbi1ib3R0b206MTIuMHB0Ij5UaGF0J3MgYSBsaXR0bGUgbW9yZSBzdWNjaW5jdCB0aGFuIEkg
d291bGQgYmUsIGJ1dCB5ZXMuJm5ic3A7IEhvdyBkb2VzIGFuIGFwcGxpY2F0aW9uIGtub3cgdGhh
dCB0aGUgZmxvdyBpdCBpcyBpbml0aWF0aW5nIHdpbGwgdHJhdmVyc2UgYSB0b3BvbG9neSB0aGF0
IGlzIGRlZW1lZCB0byBiZSB3aXRoaW4gYSBjb250cm9sbGVkIGVudmlyb25tZW50PyZuYnNwOyBZ
b3UgY2FuIHNheQ0KICZxdW90O2NvbmZpZ3VyYXRpb24mcXVvdDsgYnV0IEkgZmVhciBpdCB3aWxs
IHR1cm4gPGEgaHJlZj0iaHR0cHM6Ly9uYTAxLnNhZmVsaW5rcy5wcm90ZWN0aW9uLm91dGxvb2su
Y29tLz91cmw9aHR0cHMlM0ElMkYlMkZ1cmxkZWZlbnNlLnByb29mcG9pbnQuY29tJTJGdjIlMkZ1
cmwlM0Z1JTNEaHR0cHMtM0FfX25hMDEuc2FmZWxpbmtzLnByb3RlY3Rpb24ub3V0bG9vay5jb21f
LTNGdXJsLTNEaHR0cHMtMjUzQS0yNTJGLTI1MkZpLmtpbmphLTJEaW1nLmNvbS0yNTJGZ2F3a2Vy
LTJEbWVkaWEtMjUyRmltYWdlLTI1MkZ1cGxvYWQtMjUyRnMtMkQtMkRFZHU2TFB1OS0yRC0yRC0y
NTJGYy01RnNjYWxlLTI1MkNmLTVGYXV0by0yNTJDZmwtNUZwcm9ncmVzc2l2ZS0yNTJDcS01Rjgw
LTI1MkN3LTVGODAwLTI1MkYxOTR0aGJ0eWVuY3MwanBnLmpwZy0yNmRhdGEtM0QwMi0yNTdDMDEt
MjU3Q3ByYXZiLTI1NDBtaWNyb3NvZnQuY29tLTI1N0M0ZGE0NGU4YWMxZGY0NzA4YWQ4ODA4ZDVh
ZjdiZmNhOC0yNTdDNzJmOTg4YmY4NmYxNDFhZjkxYWIyZDdjZDAxMWRiNDctMjU3QzEtMjU3QzEt
MjU3QzYzNjYwNzg2OTQxMTI1ODk3Ni0yNnNkYXRhLTNEUHJvbFNIa2JGMlNnTUgzcWRRTi0yNTJC
WkZva1h2c0VCZi0yNTJGM285TWFVbmlsMGc4LTI1M0QtMjZyZXNlcnZlZC0zRDAlMjZkJTNERHdN
R2FRJTI2YyUzRDVWRDBSVHRObFRoM3ljZDQxYjNNVXclMjZyJTNEQzBzVW8tTEZOQmFZZnlvYUNz
ZjZUQSUyNm0lM0RUdVZmenlwby1DWkxvNTIybGdNUnJMcEt4Y0ZhSHZXOWtkTlNJNTdsWFQwJTI2
cyUzREJ5MmRfdG83WHpMRWdBTDNPcjljWmMyQXlreWUtUFpFZW5GUUR2aUFVbHclMjZlJTNEJmFt
cDtkYXRhPTAyJTdDMDElN0NwcmF2YiU0MG1pY3Jvc29mdC5jb20lN0NjNTBmOTFiYzNlYzc0NDU0
NDFkZTA4ZDVhZmM0ZDc5ZSU3QzcyZjk4OGJmODZmMTQxYWY5MWFiMmQ3Y2QwMTFkYjQ3JTdDMSU3
QzAlN0M2MzY2MDgxODIzMzU2MzMyODImYW1wO3NkYXRhPSUyRjZKRWJ1Q25sV2JpVVk4dWFFc09H
ZEdOV1BzYjJLVk9pVktIMFVnZFU4VSUzRCZhbXA7cmVzZXJ2ZWQ9MCIgdGFyZ2V0PSJfYmxhbmsi
Pg0KdXAgb24gYSBwb3N0LWl0Jm5ic3A7IDwvYT5pZiB5b3UgZG8uJm5ic3A7IExvYWRzIHNoaWZ0
LCByZXNvdXJjZXMgbW92ZSwgYW5kIHN1ZGRlbmx5IHlvdSBmaW5kIHRoYXQgaG9zdCB3aGljaCB1
c2VkIHRvIGJlIGluIHRoZSBzYW1lIHJhY2ssIGJlaW5nIGRvd24sIGhhcyBsb2FkLXNoaWZ0ZWQg
dG8gdGhlIG5leHQgaW5zdGFuY2UsJm5ic3A7IGluIGEgZGF0YWNlbnRlciA1MDAgbWlsZXMgYXdh
eSBhY3Jvc3MgYSB2ZXJ5IGRpZmZlcmVudCBuZXR3b3JrLiZuYnNwOw0KPGJyPg0KPGJyPg0KTWFu
eSBtb2Rlcm4gZGVwbG95bWVudHMgYXJlIGFsc28gaW4gc29tZW9uZSBlbHNlJ3MgZGF0YSBjZW50
ZXIsIHNvIHNheWluZyAmcXVvdDtEYXRhIGNlbnRlciBuZXR3b3JrcyZxdW90OyBkb2Vzbid0IHNh
eSBtdWNoIGFib3V0IHdoeSB5b3UncmUgdHJ1c3RpbmcgdGhlIG5ldHdvcmsgaW5zaWRlLjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSIiPlRlZDwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSIiPiZuYnNwOzwvcD4NCjwv
ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lOyBib3JkZXItbGVmdDpzb2xpZCAj
Q0NDQ0NDIDEuMHB0OyBwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0OyBtYXJnaW4tbGVmdDo0Ljhw
dDsgbWFyZ2luLXRvcDo1LjBwdDsgbWFyZ2luLXJpZ2h0OjBpbjsgbWFyZ2luLWJvdHRvbTo1LjBw
dCI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXYgaWQ9Im1fLTE4MzQyMDM2NjIwOTIyOTYxODVtXy0zNzc1
NTUyMDk3NTgyNjY0NTYyeF9jb21wb3Nlcl9zaWduYXR1cmUiPg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSIiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6OS41cHQ7IGNvbG9yOiM1
NzU3NTciPlNlbnQgdmlhIHRoZSBTYW1zdW5nIEdhbGF4eSBTNywgYW4gQVQmYW1wO1QgNEcgTFRF
IHNtYXJ0cGhvbmU8L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0iIj4mbmJzcDs8L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0iIj4mbmJzcDs8L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0iIj4tLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tPC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9IiI+RnJvbTogJnF1
b3Q7U2FseiwgUmljaCZxdW90OyAmbHQ7cnNhbHo9PGEgaHJlZj0ibWFpbHRvOjQwYWthbWFpLmNv
bUBkbWFyYy5pZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPjQwYWthbWFpLmNvbUBkbWFyYy5pZXRm
Lm9yZzwvYT4mZ3Q7DQo8L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0iIj5EYXRlOiA1LzEvMTggNToyNSBBTSAoR01ULTA4OjAwKSA8L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iIj5UbzogQmVuamFtaW4gS2FkdWsgJmx0
O2JrYWR1az08YSBocmVmPSJtYWlsdG86NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnIiB0YXJn
ZXQ9Il9ibGFuayI+NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnPC9hPiZndDssIFByYXZlZW4g
QmFsYXN1YnJhbWFuaWFuICZsdDtwcmF2Yj08YSBocmVmPSJtYWlsdG86NDBtaWNyb3NvZnQuY29t
QGRtYXJjLmlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+NDBtaWNyb3NvZnQuY29tQGRtYXJjLmll
dGYub3JnPC9hPiZndDsNCjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSIiPkNjOiBJRVRGIFFVSUMgV0cgJmx0OzxhIGhyZWY9Im1haWx0bzpxdWljQGlldGYu
b3JnIiB0YXJnZXQ9Il9ibGFuayI+cXVpY0BpZXRmLm9yZzwvYT4mZ3Q7DQo8L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iIj5TdWJqZWN0OiBSZTogR2V0dGlu
ZyB0byBjb25zZW5zdXMgb24gcGFja2V0IG51bWJlciBlbmNyeXB0aW9uDQo8L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0iIj4mbmJzcDs8L3A+DQo8L2Rpdj4N
CjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1hcmdpbi1ib3R0b206MTIuMHB0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyBJIGRpc2FncmVl
IHRoYXQgd2UgbmVlZCBhbnkgbW9yZSBkYXRhIGZvciBub3QgZG9pbmcgUE5FIGluIHRoZSBkYXRh
Y2VudGVyLiBXaHkgd291bGQgd2UgYWRkIGFuIGV4dHJhIGVuY3J5cHQtZGVjcnlwdCBzdGVwIGZv
ciBubyBvYnZpb3VzIGJlbmVmaXQ/PGJyPg0KPGJyPg0KSSBhbSBjb25jZXJuZWQgdGhhdCBwZW9w
bGUgd2lsbCBtaXMtaW50ZXJwcmV0IHRoZSBtZWFuaW5nIG9mIGEgZGF0YWNlbnRlciwgYW5kIHRo
aW5rIHRoYXQgYSBidW5jaCBvZiBzZXJ2ZXJzLCBvciBldmVuIGEgcmFjaywgaW4gYW4gb3BlbiBj
b2xvIHNwYWNlIGlzIGEgJnF1b3Q7ZGF0YWNlbnRlci4mcXVvdDsmbmJzcDsgQ29tcHV0ZXJzIGtl
ZXAgZ2V0dGluZyBmYXN0ZXIuDQo8L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4N
CjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9IiI+Jm5i
c3A7PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8
L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_DB6PR10MB17660511ED052322C7BD4F17AC800DB6PR10MB1766EURP_--


From nobody Wed May  2 01:37:38 2018
Return-Path: <lars@netapp.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 84A1C124319 for <quic@ietfa.amsl.com>; Wed,  2 May 2018 01:37:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.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 V0Osh2UHrWkK for <quic@ietfa.amsl.com>; Wed,  2 May 2018 01:37:35 -0700 (PDT)
Received: from mx141.netapp.com (mx141.netapp.com [IPv6:2620:10a:4005:8000:2306::a]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B9D3126CD8 for <quic@ietf.org>; Wed,  2 May 2018 01:37:34 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.49,354,1520924400";  d="asc'?scan'208";a="270872034"
Received: from vmwexchts04-prd.hq.netapp.com ([10.122.105.32]) by mx141-out.netapp.com with ESMTP; 02 May 2018 01:37:34 -0700
Received: from HIOEXCMBX08-PRD.hq.netapp.com (10.122.105.41) by VMWEXCHTS04-PRD.hq.netapp.com (10.122.105.32) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 2 May 2018 01:37:34 -0700
Received: from VMWEXCCAS02-PRD.hq.netapp.com (10.122.105.18) by hioexcmbx08-prd.hq.netapp.com (10.122.105.41) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Wed, 2 May 2018 01:37:34 -0700
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS02-PRD.hq.netapp.com (10.122.105.18) with Microsoft SMTP Server (TLS) id 15.0.1320.4 via Frontend Transport; Wed, 2 May 2018 01:37:34 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ozM75Rjbj4q7cL7Km0J4xE6R8DzS/QZQkbhhvFYFueQ=; b=Qfxr+xZivVfYs3vRsQAjmlswHgE2IqCjQkBvQhfrrDyVwQindI5bjmn1l29yo1phciZB8LCspS7COr1akNQMvPHlbwz9WlNurrZLU14SFLPdKX8sbPOQ4DCltFhLgzFaZXNjHkvpAfk+rxOOkLVvVT9ky+l8A+7YoHIiKACyZbQ=
Received: from BLUPR06MB1764.namprd06.prod.outlook.com (10.162.224.150) by BLUPR06MB884.namprd06.prod.outlook.com (10.141.207.155) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.715.20; Wed, 2 May 2018 08:37:32 +0000
Received: from BLUPR06MB1764.namprd06.prod.outlook.com ([fe80::5520:2312:30a8:6bd2]) by BLUPR06MB1764.namprd06.prod.outlook.com ([fe80::5520:2312:30a8:6bd2%7]) with mapi id 15.20.0715.024; Wed, 2 May 2018 08:37:32 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: QUIC WG <quic@ietf.org>
Subject: Decision on PNE
Thread-Topic: Decision on PNE
Thread-Index: AQHT4fDPmB4Fk4HtJ0qSYuiuzy7oxA==
Date: Wed, 2 May 2018 08:37:32 +0000
Message-ID: <FC2560DD-2F6E-4624-B2CF-96B6D28871F5@netapp.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3445.6.18)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lars@netapp.com; 
x-originating-ip: [2001:a61:2ba2:f400:a00d:19d:6df8:4a2d]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BLUPR06MB884; 7:dCbWZbPKu7Gl/lyncR+T6w0GE+3oIQboNryVEms1FJCBDgpeC3ZsHg9hNyYGAWr3oH2RNT00bQFoPEuOoYkYkVO4zTsKj9WeBGq2UX0PRwVRcisLWW0q9ou/w7p37VWhwi/84+TxtdJDj6rpz+g72cDsylsCloTRTK536DdFvuSfrcF6yNbp4oB2wpIS6ZU6uMxyNilf6hTsX060Vv4HMKbLNsMhIJHuuIILrJ7sguGnJx9n6JT7Mi0zzREFNqNc
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(49563074)(7193020); SRVR:BLUPR06MB884; 
x-ms-traffictypediagnostic: BLUPR06MB884:
x-microsoft-antispam-prvs: <BLUPR06MB884144A66DDB9F29E52C4A3A7800@BLUPR06MB884.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(100405760836317);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(102415395)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(3231254)(944501410)(52105095)(10201501046)(3002001)(6055026)(6041310)(20161123564045)(20161123558120)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:BLUPR06MB884; BCL:0; PCL:0; RULEID:; SRVR:BLUPR06MB884; 
x-forefront-prvs: 06607E485E
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(39380400002)(396003)(346002)(376002)(366004)(39860400002)(199004)(189003)(2906002)(478600001)(5660300001)(99286004)(99936001)(6116002)(83716003)(86362001)(33656002)(105586002)(305945005)(106356001)(68736007)(82746002)(5250100002)(14454004)(7116003)(6436002)(3660700001)(25786009)(3280700002)(57306001)(316002)(8936002)(2900100001)(3480700004)(81166006)(46003)(102836004)(6486002)(476003)(486006)(8676002)(59450400001)(6916009)(7736002)(97736004)(53936002)(6512007)(6506007)(81156014)(50226002)(2616005)(36756003)(186003); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR06MB884; H:BLUPR06MB1764.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: netapp.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: lu8Uhd8/uL2j89oFCv7mXP+hT76QLmUEKcPQn8Gk/GRxR+03VAV9+KZrlEEnEwfNlHkezKlmyWsRZ6QGsXj0RE4wkwi+SG17ZqvnLCpZNqcqGVq/KPEAqSI3IM2DldYzlucGWdhBIoaPznEGfqcE7qq+72RvuK9klcSALWzfk/V5Awx9xSIzepgol3bhwms8
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_668E01D1-F91E-4010-855F-F93A90CCA398"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: f8ebf3b6-a1bc-4fae-cbd1-08d5b007f272
X-MS-Exchange-CrossTenant-Network-Message-Id: f8ebf3b6-a1bc-4fae-cbd1-08d5b007f272
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 May 2018 08:37:32.0331 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR06MB884
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/iXnguiKGc0xw9VJRKafWJaE_x1I>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 08:37:36 -0000

--Apple-Mail=_668E01D1-F91E-4010-855F-F93A90CCA398
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

Mark and me have reviewed the WG discussion on packet number encryption, =
and are in agreement that the WG seems to have reached rough consensus =
to land PR 1079 in its current form for QUICv1. So we're asking the =
editors to please make that change to the documents.

As always, this issue can be reopened if better ideas and/or new data =
emerges. But since PNE is blocking the conclusion of several other =
things, we feel that it is important to make a decision now, so that the =
WG can move on to other unresolved issues.

Thanks,
Lars

--Apple-Mail=_668E01D1-F91E-4010-855F-F93A90CCA398
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAlrpeMsACgkQVLXDCb9w
wVegCQ/8CgUY/lkpwCCIdyQXShKAWKvO+WJRDhB5hqXyhSdLl/h/7TdKOw3WKwpL
mdyqJbLqXGkf1K/UGnXmQrNrpQqvoytKLVnTeR+BIs5wd5yXcYXXNGhp+2A7DIZS
gzp/KU5dF6b7vz/II8vj6adi9c21XjcjP/izDrmmYdmJuQLhWGuJk89QQ7zBn1X5
/KxbFDvt7awKHwwcXW/zxkvTzTxCaiPejOITpQHRSjPj0wOY31rhApSlUFQG0ar8
UshSjIZZ6kKy6XMLY4x8ZbMiBNo/1x9GsCkAqCr9xkoWw9FWH8ToVIAXYGlcq6Om
jEiTLc5dxKQo4dchZ9N5ABF0EPJBdswDRPOgAE6ofOaYeIWtxks36MNnxUkmqDXd
AvNAf1KW0wFW1ceH93krzi671Eh//i2dVTfQoOX0N7TqymLrT8hqz3VIEtojcyon
zJHH5CmyUv/gVXe/IluNBfTukT9qmUcdMbC1ybiHIJFl8HQii+Qe31HaqSHLsz5Z
3vptQl4L+gGSDkupKrbnSu4O9U03E8325AqngP2ScAB66X2VlsphNqu2bEmbVM7x
8xbJorK8mDQ8u7wU4Elxr1tXH3BelSSVFkSaA8++nFlg5ez72snMqLGpmexz5/QK
96b6Te+Isoa/p1JQErmBST7zkX7UDeYk7KfuCW0IiBD+HS7V+Z0=
=1oKL
-----END PGP SIGNATURE-----

--Apple-Mail=_668E01D1-F91E-4010-855F-F93A90CCA398--


From nobody Wed May  2 05:10:27 2018
Return-Path: <bkaduk@akamai.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 35A4B126FB3 for <quic@ietfa.amsl.com>; Wed,  2 May 2018 05:10:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Level: 
X-Spam-Status: No, score=-2.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 NSTSB1zixWdr for <quic@ietfa.amsl.com>; Wed,  2 May 2018 05:10:23 -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 6782C126D45 for <quic@ietf.org>; Wed,  2 May 2018 05:10:23 -0700 (PDT)
Received: from pps.filterd (m0122333.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w42C4Qp8008160; Wed, 2 May 2018 13:10:23 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=date : from : to : cc : subject : message-id : references : mime-version : content-type : content-transfer-encoding : in-reply-to; s=jan2016.eng; bh=NqdvoISDvRY1AkM6yi8+WvFwSiYZrrLhiLR3imSShd8=; b=VeS7T+wWAA0ZSw1R7MbpdgHSFwFfsWjrJkccyBi8orXZoBCoCVvJMKzCSv42Qh9otJ6B FnlPwkZnkw3xPK8bGV7489DR7E/WdcZchJ5l5JbBMTjBRNTxCCbnoJo5Gi0RGId1wduO 09/tXXOIa8qmwx4w07KaDDM9Bql3Z1gn8ES1uHzOnbzd+Us0+uGHTzoGJX3Ko4hccWPH wlGEZi6Zc6C/EYEfOtOqbYmUt4rnacrCQMdJmxhqJ3ghDNZ1cOgU8hdmOZmSI5NI0tMO NCdQKlyP43Q2zs+VZafOa0J9bBZtVErzVG+bq/II/7VbbEm1WmptsBYm0RSOo1L5ab4m tA== 
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19]) by mx0a-00190b01.pphosted.com with ESMTP id 2hmpsprvdu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 02 May 2018 13:10:22 +0100
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w42C1QKU032400; Wed, 2 May 2018 08:10:21 -0400
Received: from prod-mail-relay10.akamai.com ([172.27.118.251]) by prod-mail-ppoint2.akamai.com with ESMTP id 2hmm9v17hp-1; Wed, 02 May 2018 08:10:20 -0400
Received: from bos-lpczi.kendall.corp.akamai.com (bos-lpczi.kendall.corp.akamai.com [172.19.17.86]) by prod-mail-relay10.akamai.com (Postfix) with ESMTP id 166831FCD8; Wed,  2 May 2018 12:10:19 +0000 (GMT)
Received: from bkaduk by bos-lpczi.kendall.corp.akamai.com with local (Exim 4.86_2) (envelope-from <bkaduk@akamai.com>) id 1fDqaQ-0000uj-GO; Wed, 02 May 2018 07:10:18 -0500
Date: Wed, 2 May 2018 07:10:18 -0500
From: Benjamin Kaduk <bkaduk@akamai.com>
To: Praveen Balasubramanian <pravb@microsoft.com>
Cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Getting to consensus on packet number encryption
Message-ID: <20180502121018.GF5742@akamai.com>
References: <01AE46C6-682C-4A21-84CD-1D8DAD6F49D9@fb.com> <CACpbDcdnmHrWMCShYd1pEDBervRKfO1pMUM8hb4tkK9nqH1Mdw@mail.gmail.com> <MWHPR21MB06386100B48E17A059B5A04EB6800@MWHPR21MB0638.namprd21.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <MWHPR21MB06386100B48E17A059B5A04EB6800@MWHPR21MB0638.namprd21.prod.outlook.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-02_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=899 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805020099
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-02_04:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=874 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805020099
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/9Oj921-SUN7ceUMwfECtjOVTRc0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 12:10:25 -0000

Hi Praveen,

On Wed, May 02, 2018 at 02:02:37AM +0000, Praveen Balasubramanian wrote:
> We can get (1) done but I disagree that we can decouple (2). It doesn’t make sense to require performance overhead all the time with no benefit. For the Internet, PNE can prevent ossification so it is seen as a reasonable trade-off. For the datacenter, there is no known benefit, only cost.

Most of why I am pushing back so hard on this point is that I am having a
*really* hard time getting the statement of "no benefit" (i.e., exactly zero)
to mesh with my understanding of the situation.  I don't know the best
way past this impasse -- it doesn't really seem right for me to make a
list of potential benefits and have you shoot them down, for example.  I
think maybe you are trying to make a slightly different point involving
something like ongoing operational benefits (as opposed to cost of
implementation/risk of bugs/ecosystem benefits), but I'm not entirely
sure.

> We know that there is a CPU cost, this is not speculation. Doesn’t matter if
> the cost is 1% or 10%. Hardware implementers have also raised concerns. Every

Well, I think it rather does matter for 1% vs. 10%.  If it was 0.1%
(unlikely, I suppose), then that might be "in the noise" and not worth
doing anything about, ever.  For a 1% cost, that's significant enough to
make me want to address it in my long-term plans, but it is not
necessarily a big enough impact to require immediate attention.  10%, on
the other hand, probably would require immediate attention and be a
show-stopper.

> CPU cycle we spend on things that add no value to the user should be
> questioned. Every extra instruction we execute in the hot data path leaves
> less CPU for workloads, burns more power and makes for a worse comparison
> with HTTPS over TCP. The same argument as privacy holes holds here – just

The "burns more power" argument can be applied to every single CPU
instruction; relative measures (i.e., percentage of total CPU) from
actual deployment are what I find to be most compelling.

> because there are some existing perf bottlenecks doesn’t mean we add more,
> particularly ones we cannot mitigate. I said it before that there are lots of
> ways we can improve UDP perf but I don’t know of any technique for reducing
> crypto CPU cost other than hardware offload.

And I ask again, who is "we"?  (At this point I am mostly assuming "all
QUIC implementors", but it would be nice to be sure.)

> The cost is certainly worth saving with something as simple as a negotiation
> mechanism. Am I missing something about a transport parameter being

>From the rest of the discussion, I don't think you've really sold people
on "certainly", yet.

> complicated to implement? Implementations are free to support only PNE and
> not negotiate anything else. There is actually an even simpler mechanism if a
> transport parameter is deemed as costly: if the peer sends PN = 0 in the CI,
> then its requesting no PNE and the receiver can choose to proceed or drop and
> force TCP fall back. This should take only an extra if check on the receiver
> CI processing logic to implement. I am assuming here that PNE on input of 0
> will not produce 0 so it’s a safe sentinel value.

I think some people are worried not just about the complexity/simplicity
of the mechanism implemented, but broader-scope ecosystem and
architecture issues, whether that's a general complexity reduction
initiative or more subtle issues involving middleboxes attempting to
coerce certain sorts of behavior.

-Ben


From nobody Wed May  2 05:28:28 2018
Return-Path: <ianswett@google.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A22E8126D3F for <quic@ietfa.amsl.com>; Wed,  2 May 2018 05:28:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 wVP4lgMJrkfH for <quic@ietfa.amsl.com>; Wed,  2 May 2018 05:28:24 -0700 (PDT)
Received: from mail-yb0-x22a.google.com (mail-yb0-x22a.google.com [IPv6:2607:f8b0:4002:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1049E120454 for <quic@ietf.org>; Wed,  2 May 2018 05:28:24 -0700 (PDT)
Received: by mail-yb0-x22a.google.com with SMTP id o80-v6so3850134ybc.7 for <quic@ietf.org>; Wed, 02 May 2018 05:28:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=wjI/1z43BuLdhXGxoQUd7mn7pj3x0TNHW8voV2Fs2ug=; b=WzMbdhG0kLeKCsD2dzLI4tFbDhfuWVcx44Gmz9cdyPcWxIp/1L75XEeofC7bBWgqrf CmO4NZw7oJcb4bbbrYjdRsPSiVh00AhMgF9fXCPHb3ggpCh7f5J8ej/2gNBO2iaPhHrF sekJ7Gr8oTzTgchN8cryAdBpKefGG3y6fCjpVKPdX1c//9k+zgt8YLk/X3ANJ/7WqG3c 3C/FX2Ukgl8/o5oYR/iYM0eQNmMpgDtQNETDjH2CDuomwuyFRV/47iPGDuEzh2UoYxaY SELhDpbr+CugW84xpBHIWwd0YSB6rx2YshE9zg8JrcvzZFWhHZgxwneLDwxC2cqPpVc7 mNmQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=wjI/1z43BuLdhXGxoQUd7mn7pj3x0TNHW8voV2Fs2ug=; b=kLHReHIzMN8gXJAWgEhJDey0VGQXwcRa9qoU1SvKe2uwjzcnmZTQSbeot5ASCdxPdp HGFLa69pmis/lXfqpNHGY9newIe4C6WL9HrrXWvhLPvfVieAlocnraiEWim/KwKxQnF1 LWkoFsRf+81OxSRG5TjzYn2t0iQQiHxh4BTtcgQ11Bog0dOpIB9zB0Uspl/H6Em9wvGg fh9Xd32EGHogcqIcIk9yAU2epvFwPJyubnuCZhWmxpqR+lEODp5H6ftDAsfEX8NpRNos 2+IkYbLsdmG8FwZuyUtal/CIZQkNiR0pGd6Wzwvlc4qdMDMUM62t+veNtuzbRyPmHW0C ABxA==
X-Gm-Message-State: ALQs6tC93+HzuzrcwUV0KsOSMVnWkgO0mnQ7ZjWVjNqXpZ7khtxEG8he u1vm01d3Mldkz8qqtkwZreFjdcSW07kHd92dUpqHVa4Z
X-Google-Smtp-Source: AB8JxZoAwTUUYNqh5bEXFTg5+jQSA4ke9qNBZ004TC+DxTJOPaHtK1p7OkDzvfpIu20+7XeEVS14nhsuFbq+EVgDoKs=
X-Received: by 2002:a5b:c0e:: with SMTP id f14-v6mr12047191ybq.107.1525264102972;  Wed, 02 May 2018 05:28:22 -0700 (PDT)
MIME-Version: 1.0
References: <01AE46C6-682C-4A21-84CD-1D8DAD6F49D9@fb.com> <CACpbDcdnmHrWMCShYd1pEDBervRKfO1pMUM8hb4tkK9nqH1Mdw@mail.gmail.com> <MWHPR21MB06386100B48E17A059B5A04EB6800@MWHPR21MB0638.namprd21.prod.outlook.com> <20180502121018.GF5742@akamai.com>
In-Reply-To: <20180502121018.GF5742@akamai.com>
From: Ian Swett <ianswett@google.com>
Date: Wed, 02 May 2018 12:28:10 +0000
Message-ID: <CAKcm_gPt7gJNvykq9422Rr4AGxYg+vGjK-aEDfbT+4ryzK1veg@mail.gmail.com>
Subject: Re: Getting to consensus on packet number encryption
To: bkaduk=40akamai.com@dmarc.ietf.org
Cc: Praveen Balasubramanian <pravb@microsoft.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000ca211056b38392f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/F8ysyAue0qaWHr3Aqa2uLdRctrk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 12:28:27 -0000

--0000000000000ca211056b38392f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Praveen, I thought the suggested plan by Martin was to default enable PNE
and then we can separately discuss a mechanism(ie: Transport params) where
if both sides agreed, PNE would be disabled for short header packets?  That
seems fine for your use cases, correct?  Or is the concern that the WG will
reject any sort of mechanism that allows PNE to be disabled?

And as Ben said, if this adds 10% CPU, then we need to rethink this
completely, but I don't believe it will.  Hopefully I'll have some numbers
before the next interim

AND FWIW, I'd like to see a QUIC v2 within a year or two of QUIC v1.

On Wed, May 2, 2018 at 8:10 AM Benjamin Kaduk <bkaduk=3D
40akamai.com@dmarc.ietf.org> wrote:

> Hi Praveen,
>
> On Wed, May 02, 2018 at 02:02:37AM +0000, Praveen Balasubramanian wrote:
> > We can get (1) done but I disagree that we can decouple (2). It doesn=
=E2=80=99t
> make sense to require performance overhead all the time with no benefit.
> For the Internet, PNE can prevent ossification so it is seen as a
> reasonable trade-off. For the datacenter, there is no known benefit, only
> cost.
>
> Most of why I am pushing back so hard on this point is that I am having a
> *really* hard time getting the statement of "no benefit" (i.e., exactly
> zero)
> to mesh with my understanding of the situation.  I don't know the best
> way past this impasse -- it doesn't really seem right for me to make a
> list of potential benefits and have you shoot them down, for example.  I
> think maybe you are trying to make a slightly different point involving
> something like ongoing operational benefits (as opposed to cost of
> implementation/risk of bugs/ecosystem benefits), but I'm not entirely
> sure.
>
> > We know that there is a CPU cost, this is not speculation. Doesn=E2=80=
=99t
> matter if
> > the cost is 1% or 10%. Hardware implementers have also raised concerns.
> Every
>
> Well, I think it rather does matter for 1% vs. 10%.  If it was 0.1%
> (unlikely, I suppose), then that might be "in the noise" and not worth
> doing anything about, ever.  For a 1% cost, that's significant enough to
> make me want to address it in my long-term plans, but it is not
> necessarily a big enough impact to require immediate attention.  10%, on
> the other hand, probably would require immediate attention and be a
> show-stopper.
>
> > CPU cycle we spend on things that add no value to the user should be
> > questioned. Every extra instruction we execute in the hot data path
> leaves
> > less CPU for workloads, burns more power and makes for a worse comparis=
on
> > with HTTPS over TCP. The same argument as privacy holes holds here =E2=
=80=93 just
>
> The "burns more power" argument can be applied to every single CPU
> instruction; relative measures (i.e., percentage of total CPU) from
> actual deployment are what I find to be most compelling.
>
> > because there are some existing perf bottlenecks doesn=E2=80=99t mean w=
e add
> more,
> > particularly ones we cannot mitigate. I said it before that there are
> lots of
> > ways we can improve UDP perf but I don=E2=80=99t know of any technique =
for
> reducing
> > crypto CPU cost other than hardware offload.
>
> And I ask again, who is "we"?  (At this point I am mostly assuming "all
> QUIC implementors", but it would be nice to be sure.)
>
> > The cost is certainly worth saving with something as simple as a
> negotiation
> > mechanism. Am I missing something about a transport parameter being
>
> >From the rest of the discussion, I don't think you've really sold people
> on "certainly", yet.
>
> > complicated to implement? Implementations are free to support only PNE
> and
> > not negotiate anything else. There is actually an even simpler mechanis=
m
> if a
> > transport parameter is deemed as costly: if the peer sends PN =3D 0 in =
the
> CI,
> > then its requesting no PNE and the receiver can choose to proceed or
> drop and
> > force TCP fall back. This should take only an extra if check on the
> receiver
> > CI processing logic to implement. I am assuming here that PNE on input
> of 0
> > will not produce 0 so it=E2=80=99s a safe sentinel value.
>
> I think some people are worried not just about the complexity/simplicity
> of the mechanism implemented, but broader-scope ecosystem and
> architecture issues, whether that's a general complexity reduction
> initiative or more subtle issues involving middleboxes attempting to
> coerce certain sorts of behavior.
>
> -Ben
>
>

--0000000000000ca211056b38392f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Praveen, I thought the suggested plan by Martin was to def=
ault enable PNE and then we can separately discuss a mechanism(ie: Transpor=
t params) where if both sides agreed, PNE would be disabled for short heade=
r packets?=C2=A0 That seems fine for your use cases, correct?=C2=A0 Or is t=
he concern that the WG will reject any sort of mechanism that allows PNE to=
 be disabled?<div><br></div><div>And as Ben said, if this adds 10% CPU, the=
n we need to rethink this completely, but I don&#39;t believe it will.=C2=
=A0 Hopefully I&#39;ll have some numbers before the next interim<br></div><=
div><br></div><div>AND FWIW, I&#39;d like to see a QUIC v2 within a year or=
 two of QUIC v1.</div><div></div><div></div><div></div><div></div></div><br=
><div class=3D"gmail_quote"><div dir=3D"ltr">On Wed, May 2, 2018 at 8:10 AM=
 Benjamin Kaduk &lt;bkaduk=3D<a href=3D"mailto:40akamai.com@dmarc.ietf.org"=
>40akamai.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"g=
mail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-l=
eft:1ex">Hi Praveen,<br>
<br>
On Wed, May 02, 2018 at 02:02:37AM +0000, Praveen Balasubramanian wrote:<br=
>
&gt; We can get (1) done but I disagree that we can decouple (2). It doesn=
=E2=80=99t make sense to require performance overhead all the time with no =
benefit. For the Internet, PNE can prevent ossification so it is seen as a =
reasonable trade-off. For the datacenter, there is no known benefit, only c=
ost.<br>
<br>
Most of why I am pushing back so hard on this point is that I am having a<b=
r>
*really* hard time getting the statement of &quot;no benefit&quot; (i.e., e=
xactly zero)<br>
to mesh with my understanding of the situation.=C2=A0 I don&#39;t know the =
best<br>
way past this impasse -- it doesn&#39;t really seem right for me to make a<=
br>
list of potential benefits and have you shoot them down, for example.=C2=A0=
 I<br>
think maybe you are trying to make a slightly different point involving<br>
something like ongoing operational benefits (as opposed to cost of<br>
implementation/risk of bugs/ecosystem benefits), but I&#39;m not entirely<b=
r>
sure.<br>
<br>
&gt; We know that there is a CPU cost, this is not speculation. Doesn=E2=80=
=99t matter if<br>
&gt; the cost is 1% or 10%. Hardware implementers have also raised concerns=
. Every<br>
<br>
Well, I think it rather does matter for 1% vs. 10%.=C2=A0 If it was 0.1%<br=
>
(unlikely, I suppose), then that might be &quot;in the noise&quot; and not =
worth<br>
doing anything about, ever.=C2=A0 For a 1% cost, that&#39;s significant eno=
ugh to<br>
make me want to address it in my long-term plans, but it is not<br>
necessarily a big enough impact to require immediate attention.=C2=A0 10%, =
on<br>
the other hand, probably would require immediate attention and be a<br>
show-stopper.<br>
<br>
&gt; CPU cycle we spend on things that add no value to the user should be<b=
r>
&gt; questioned. Every extra instruction we execute in the hot data path le=
aves<br>
&gt; less CPU for workloads, burns more power and makes for a worse compari=
son<br>
&gt; with HTTPS over TCP. The same argument as privacy holes holds here =E2=
=80=93 just<br>
<br>
The &quot;burns more power&quot; argument can be applied to every single CP=
U<br>
instruction; relative measures (i.e., percentage of total CPU) from<br>
actual deployment are what I find to be most compelling.<br>
<br>
&gt; because there are some existing perf bottlenecks doesn=E2=80=99t mean =
we add more,<br>
&gt; particularly ones we cannot mitigate. I said it before that there are =
lots of<br>
&gt; ways we can improve UDP perf but I don=E2=80=99t know of any technique=
 for reducing<br>
&gt; crypto CPU cost other than hardware offload.<br>
<br>
And I ask again, who is &quot;we&quot;?=C2=A0 (At this point I am mostly as=
suming &quot;all<br>
QUIC implementors&quot;, but it would be nice to be sure.)<br>
<br>
&gt; The cost is certainly worth saving with something as simple as a negot=
iation<br>
&gt; mechanism. Am I missing something about a transport parameter being<br=
>
<br>
&gt;From the rest of the discussion, I don&#39;t think you&#39;ve really so=
ld people<br>
on &quot;certainly&quot;, yet.<br>
<br>
&gt; complicated to implement? Implementations are free to support only PNE=
 and<br>
&gt; not negotiate anything else. There is actually an even simpler mechani=
sm if a<br>
&gt; transport parameter is deemed as costly: if the peer sends PN =3D 0 in=
 the CI,<br>
&gt; then its requesting no PNE and the receiver can choose to proceed or d=
rop and<br>
&gt; force TCP fall back. This should take only an extra if check on the re=
ceiver<br>
&gt; CI processing logic to implement. I am assuming here that PNE on input=
 of 0<br>
&gt; will not produce 0 so it=E2=80=99s a safe sentinel value.<br>
<br>
I think some people are worried not just about the complexity/simplicity<br=
>
of the mechanism implemented, but broader-scope ecosystem and<br>
architecture issues, whether that&#39;s a general complexity reduction<br>
initiative or more subtle issues involving middleboxes attempting to<br>
coerce certain sorts of behavior.<br>
<br>
-Ben<br>
<br>
</blockquote></div>

--0000000000000ca211056b38392f--


From nobody Wed May  2 05:47:09 2018
Return-Path: <mirja.kuehlewind@tik.ee.ethz.ch>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7FADA120725 for <quic@ietfa.amsl.com>; Wed,  2 May 2018 05:47:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=ham autolearn_force=no
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 VlErAWF9h7kQ for <quic@ietfa.amsl.com>; Wed,  2 May 2018 05:47:05 -0700 (PDT)
Received: from virgo01.ee.ethz.ch (virgo01.ee.ethz.ch [129.132.2.226]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D49861243FE for <quic@ietf.org>; Wed,  2 May 2018 05:46:55 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by virgo01.ee.ethz.ch (Postfix) with ESMTP id 40bdML0JxDzMlLG; Wed,  2 May 2018 14:46:54 +0200 (CEST)
X-Virus-Scanned: Debian amavisd-new at virgo01.ee.ethz.ch
Received: from virgo01.ee.ethz.ch ([127.0.0.1]) by localhost (virgo01.ee.ethz.ch [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C6ebgpxlcPmb; Wed,  2 May 2018 14:46:53 +0200 (CEST)
X-MtScore: NO score=0
Received: from [192.168.178.24] (i577BCED7.versanet.de [87.123.206.215]) by virgo01.ee.ethz.ch (Postfix) with ESMTPSA; Wed,  2 May 2018 14:46:52 +0200 (CEST)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Subject: Re: Getting to consensus on packet number encryption
From: =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
In-Reply-To: <20180502121018.GF5742@akamai.com>
Date: Wed, 2 May 2018 14:46:51 +0200
Cc: Praveen Balasubramanian <pravb@microsoft.com>, IETF QUIC WG <quic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <4C049C27-FAB7-4CF4-8ABE-DABDE8CD0F8B@tik.ee.ethz.ch>
References: <01AE46C6-682C-4A21-84CD-1D8DAD6F49D9@fb.com> <CACpbDcdnmHrWMCShYd1pEDBervRKfO1pMUM8hb4tkK9nqH1Mdw@mail.gmail.com> <MWHPR21MB06386100B48E17A059B5A04EB6800@MWHPR21MB0638.namprd21.prod.outlook.com> <20180502121018.GF5742@akamai.com>
To: Benjamin Kaduk <bkaduk=40akamai.com@dmarc.ietf.org>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Ttnfdk5uEO-ZSXhRvacdvoynJkA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 12:47:07 -0000

Hi Ben, hi all,

at this point, I'm fine with moving on with a decision and I didn=E2=80=99=
t speak up recently because I did feel that just repeating my point of =
view over and over again (like other do) would bring the discussion =
forward but I have to say that I=E2=80=99m still skeptical about the =
benefits of PNE.=20

I don=E2=80=99t think that it will help linkability as mitigation can be =
easy detected with simple traffic analysis (if you see both flows; if =
you don=E2=80=99t see both flows you can=E2=80=99t detect it no matter =
what) and I rate the risk of ossification on the packet number rather =
low (both in terms of the risk that it will happen and if even if it =
happens that it will hinder protocol evolution strongly) such that I =
simply don=E2=80=99t think that it is justified to spend ANY additional =
complexity on PNE.=20

I might be wrong and I understand the fear of people about what can =
happen in a worst case scenario, however, I also learned during my time =
in the IEFT that complexity itself can be a barrier for deployment that =
should not be underestimated. If people don=E2=80=99t understand the =
specs we write, they will not be able to implement (and maintain) our =
protocols, or at least not be able to implement it correctly which might =
be even worse for deployment and security (than not using them at all).=20=


Independent of the decision on PNE, I would like people to please keep =
in mind that while increased security is preferable, it does not mean =
that this is a free ticket to add encryption wherever we can, even if =
there are no or maybe yet unknown benefits as it always comes with a =
cost.

Mirja



> Am 02.05.2018 um 14:10 schrieb Benjamin Kaduk =
<bkaduk=3D40akamai.com@dmarc.ietf.org>:
>=20
> Hi Praveen,
>=20
> On Wed, May 02, 2018 at 02:02:37AM +0000, Praveen Balasubramanian =
wrote:
>> We can get (1) done but I disagree that we can decouple (2). It =
doesn=E2=80=99t make sense to require performance overhead all the time =
with no benefit. For the Internet, PNE can prevent ossification so it is =
seen as a reasonable trade-off. For the datacenter, there is no known =
benefit, only cost.
>=20
> Most of why I am pushing back so hard on this point is that I am =
having a
> *really* hard time getting the statement of "no benefit" (i.e., =
exactly zero)
> to mesh with my understanding of the situation.  I don't know the best
> way past this impasse -- it doesn't really seem right for me to make a
> list of potential benefits and have you shoot them down, for example.  =
I
> think maybe you are trying to make a slightly different point =
involving
> something like ongoing operational benefits (as opposed to cost of
> implementation/risk of bugs/ecosystem benefits), but I'm not entirely
> sure.
>=20
>> We know that there is a CPU cost, this is not speculation. Doesn=E2=80=99=
t matter if
>> the cost is 1% or 10%. Hardware implementers have also raised =
concerns. Every
>=20
> Well, I think it rather does matter for 1% vs. 10%.  If it was 0.1%
> (unlikely, I suppose), then that might be "in the noise" and not worth
> doing anything about, ever.  For a 1% cost, that's significant enough =
to
> make me want to address it in my long-term plans, but it is not
> necessarily a big enough impact to require immediate attention.  10%, =
on
> the other hand, probably would require immediate attention and be a
> show-stopper.
>=20
>> CPU cycle we spend on things that add no value to the user should be
>> questioned. Every extra instruction we execute in the hot data path =
leaves
>> less CPU for workloads, burns more power and makes for a worse =
comparison
>> with HTTPS over TCP. The same argument as privacy holes holds here =
=E2=80=93 just
>=20
> The "burns more power" argument can be applied to every single CPU
> instruction; relative measures (i.e., percentage of total CPU) from
> actual deployment are what I find to be most compelling.
>=20
>> because there are some existing perf bottlenecks doesn=E2=80=99t mean =
we add more,
>> particularly ones we cannot mitigate. I said it before that there are =
lots of
>> ways we can improve UDP perf but I don=E2=80=99t know of any =
technique for reducing
>> crypto CPU cost other than hardware offload.
>=20
> And I ask again, who is "we"?  (At this point I am mostly assuming =
"all
> QUIC implementors", but it would be nice to be sure.)
>=20
>> The cost is certainly worth saving with something as simple as a =
negotiation
>> mechanism. Am I missing something about a transport parameter being
>=20
>> =46rom the rest of the discussion, I don't think you've really sold =
people
> on "certainly", yet.
>=20
>> complicated to implement? Implementations are free to support only =
PNE and
>> not negotiate anything else. There is actually an even simpler =
mechanism if a
>> transport parameter is deemed as costly: if the peer sends PN =3D 0 =
in the CI,
>> then its requesting no PNE and the receiver can choose to proceed or =
drop and
>> force TCP fall back. This should take only an extra if check on the =
receiver
>> CI processing logic to implement. I am assuming here that PNE on =
input of 0
>> will not produce 0 so it=E2=80=99s a safe sentinel value.
>=20
> I think some people are worried not just about the =
complexity/simplicity
> of the mechanism implemented, but broader-scope ecosystem and
> architecture issues, whether that's a general complexity reduction
> initiative or more subtle issues involving middleboxes attempting to
> coerce certain sorts of behavior.
>=20
> -Ben
>=20


From nobody Wed May  2 06:05:01 2018
Return-Path: <roni.even@huawei.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C7E2D126DCA for <quic@ietfa.amsl.com>; Wed,  2 May 2018 06:04:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 vBBdmrqim4O6 for <quic@ietfa.amsl.com>; Wed,  2 May 2018 06:04:57 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 6B6C4126D05 for <quic@ietf.org>; Wed,  2 May 2018 06:04:57 -0700 (PDT)
Received: from lhreml708-cah.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 44403AA34247D for <quic@ietf.org>; Wed,  2 May 2018 14:04:53 +0100 (IST)
Received: from DGGEMM404-HUB.china.huawei.com (10.3.20.212) by lhreml708-cah.china.huawei.com (10.201.108.49) with Microsoft SMTP Server (TLS) id 14.3.382.0; Wed, 2 May 2018 14:04:54 +0100
Received: from DGGEMM506-MBS.china.huawei.com ([169.254.4.14]) by DGGEMM404-HUB.china.huawei.com ([10.3.20.212]) with mapi id 14.03.0361.001; Wed, 2 May 2018 21:04:49 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: =?utf-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>, Benjamin Kaduk <bkaduk=40akamai.com@dmarc.ietf.org>
CC: Praveen Balasubramanian <pravb@microsoft.com>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Getting to consensus on packet number encryption
Thread-Topic: Getting to consensus on packet number encryption
Thread-Index: AQHT4hO80n5bAGn7ak+xDRyXTDK38qQcY9ag
Date: Wed, 2 May 2018 13:04:49 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD87F34A@DGGEMM506-MBS.china.huawei.com>
References: <01AE46C6-682C-4A21-84CD-1D8DAD6F49D9@fb.com> <CACpbDcdnmHrWMCShYd1pEDBervRKfO1pMUM8hb4tkK9nqH1Mdw@mail.gmail.com> <MWHPR21MB06386100B48E17A059B5A04EB6800@MWHPR21MB0638.namprd21.prod.outlook.com> <20180502121018.GF5742@akamai.com> <4C049C27-FAB7-4CF4-8ABE-DABDE8CD0F8B@tik.ee.ethz.ch>
In-Reply-To: <4C049C27-FAB7-4CF4-8ABE-DABDE8CD0F8B@tik.ee.ethz.ch>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.202.72]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/fvifUPML95wejPJfpyGMgyqLRFE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 13:05:00 -0000

SGksDQpJIHN0cm9uZ2x5IHN1cHBvcnQgTWlyamEncyB2aWV3LiAgQXQgbGVhc3Qgd2UgY2FuIG1v
dmUgZm9yd2FyZC4NCg0KSSBkaWQgbm90IGZlZWwgZnJvbSB0aGUgZGlzY3Vzc2lvbiB0aGF0IHRo
ZSBiZW5lZml0cyBmcm9tIFBORSB2cyB0aGUgUE4gd2VyZSBtZWFuaW5nZnVsIGVub3VnaCB0byBt
YWtlIG1lIHN1cHBvcnQgYW55IGRpcmVjdGlvbiB0b28gbWFueSB2YXJpYWJsZXMgKE9zc2lmaWNh
dGlvbiwgbGlua2FiaWxpdHksIGNvbXBsZXhpdHkgYW5kIHByb2Nlc3NpbmcgcmVxdWlyZW1lbnRz
LCBQTkUgbm90IG5lZWRlZCBmb3IgYWxsIGNhc2VzIHNvIG5lZ290aWF0ZSwuLi4pIHdpdGggbm8g
d2F5IGZvciBldmFsdWF0aW9uLiAgSWYgdGhlcmUgd2FzIGEgaHVtIEkgd291bGQgcHJvYmFibHkg
aHVtIGZvciAibm90IGVub3VnaCBpbmZvcm1hdGlvbiIgb3IgIm5vIG9waW5pb24iIGJ1dCBzdGls
bCBob3BlIHRoYXQgc29tZSBkZWNpc2lvbiB3aWxsIGJlIG1hZGUuDQoNCg0KUm9uaSBFdmVuDQoN
Cg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IFFVSUMgW21haWx0bzpxdWljLWJv
dW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBNaXJqYSBLw7xobGV3aW5kDQpTZW50OiBXZWRu
ZXNkYXksIE1heSAwMiwgMjAxOCAzOjQ3IFBNDQpUbzogQmVuamFtaW4gS2FkdWsNCkNjOiBQcmF2
ZWVuIEJhbGFzdWJyYW1hbmlhbjsgSUVURiBRVUlDIFdHDQpTdWJqZWN0OiBSZTogR2V0dGluZyB0
byBjb25zZW5zdXMgb24gcGFja2V0IG51bWJlciBlbmNyeXB0aW9uDQoNCkhpIEJlbiwgaGkgYWxs
LA0KDQphdCB0aGlzIHBvaW50LCBJJ20gZmluZSB3aXRoIG1vdmluZyBvbiB3aXRoIGEgZGVjaXNp
b24gYW5kIEkgZGlkbuKAmXQgc3BlYWsgdXAgcmVjZW50bHkgYmVjYXVzZSBJIGRpZCBmZWVsIHRo
YXQganVzdCByZXBlYXRpbmcgbXkgcG9pbnQgb2YgdmlldyBvdmVyIGFuZCBvdmVyIGFnYWluIChs
aWtlIG90aGVyIGRvKSB3b3VsZCBicmluZyB0aGUgZGlzY3Vzc2lvbiBmb3J3YXJkIGJ1dCBJIGhh
dmUgdG8gc2F5IHRoYXQgSeKAmW0gc3RpbGwgc2tlcHRpY2FsIGFib3V0IHRoZSBiZW5lZml0cyBv
ZiBQTkUuIA0KDQpJIGRvbuKAmXQgdGhpbmsgdGhhdCBpdCB3aWxsIGhlbHAgbGlua2FiaWxpdHkg
YXMgbWl0aWdhdGlvbiBjYW4gYmUgZWFzeSBkZXRlY3RlZCB3aXRoIHNpbXBsZSB0cmFmZmljIGFu
YWx5c2lzIChpZiB5b3Ugc2VlIGJvdGggZmxvd3M7IGlmIHlvdSBkb27igJl0IHNlZSBib3RoIGZs
b3dzIHlvdSBjYW7igJl0IGRldGVjdCBpdCBubyBtYXR0ZXIgd2hhdCkgYW5kIEkgcmF0ZSB0aGUg
cmlzayBvZiBvc3NpZmljYXRpb24gb24gdGhlIHBhY2tldCBudW1iZXIgcmF0aGVyIGxvdyAoYm90
aCBpbiB0ZXJtcyBvZiB0aGUgcmlzayB0aGF0IGl0IHdpbGwgaGFwcGVuIGFuZCBpZiBldmVuIGlm
IGl0IGhhcHBlbnMgdGhhdCBpdCB3aWxsIGhpbmRlciBwcm90b2NvbCBldm9sdXRpb24gc3Ryb25n
bHkpIHN1Y2ggdGhhdCBJIHNpbXBseSBkb27igJl0IHRoaW5rIHRoYXQgaXQgaXMganVzdGlmaWVk
IHRvIHNwZW5kIEFOWSBhZGRpdGlvbmFsIGNvbXBsZXhpdHkgb24gUE5FLiANCg0KSSBtaWdodCBi
ZSB3cm9uZyBhbmQgSSB1bmRlcnN0YW5kIHRoZSBmZWFyIG9mIHBlb3BsZSBhYm91dCB3aGF0IGNh
biBoYXBwZW4gaW4gYSB3b3JzdCBjYXNlIHNjZW5hcmlvLCBob3dldmVyLCBJIGFsc28gbGVhcm5l
ZCBkdXJpbmcgbXkgdGltZSBpbiB0aGUgSUVGVCB0aGF0IGNvbXBsZXhpdHkgaXRzZWxmIGNhbiBi
ZSBhIGJhcnJpZXIgZm9yIGRlcGxveW1lbnQgdGhhdCBzaG91bGQgbm90IGJlIHVuZGVyZXN0aW1h
dGVkLiBJZiBwZW9wbGUgZG9u4oCZdCB1bmRlcnN0YW5kIHRoZSBzcGVjcyB3ZSB3cml0ZSwgdGhl
eSB3aWxsIG5vdCBiZSBhYmxlIHRvIGltcGxlbWVudCAoYW5kIG1haW50YWluKSBvdXIgcHJvdG9j
b2xzLCBvciBhdCBsZWFzdCBub3QgYmUgYWJsZSB0byBpbXBsZW1lbnQgaXQgY29ycmVjdGx5IHdo
aWNoIG1pZ2h0IGJlIGV2ZW4gd29yc2UgZm9yIGRlcGxveW1lbnQgYW5kIHNlY3VyaXR5ICh0aGFu
IG5vdCB1c2luZyB0aGVtIGF0IGFsbCkuIA0KDQpJbmRlcGVuZGVudCBvZiB0aGUgZGVjaXNpb24g
b24gUE5FLCBJIHdvdWxkIGxpa2UgcGVvcGxlIHRvIHBsZWFzZSBrZWVwIGluIG1pbmQgdGhhdCB3
aGlsZSBpbmNyZWFzZWQgc2VjdXJpdHkgaXMgcHJlZmVyYWJsZSwgaXQgZG9lcyBub3QgbWVhbiB0
aGF0IHRoaXMgaXMgYSBmcmVlIHRpY2tldCB0byBhZGQgZW5jcnlwdGlvbiB3aGVyZXZlciB3ZSBj
YW4sIGV2ZW4gaWYgdGhlcmUgYXJlIG5vIG9yIG1heWJlIHlldCB1bmtub3duIGJlbmVmaXRzIGFz
IGl0IGFsd2F5cyBjb21lcyB3aXRoIGEgY29zdC4NCg0KTWlyamENCg0KDQoNCj4gQW0gMDIuMDUu
MjAxOCB1bSAxNDoxMCBzY2hyaWViIEJlbmphbWluIEthZHVrIDxia2FkdWs9NDBha2FtYWkuY29t
QGRtYXJjLmlldGYub3JnPjoNCj4gDQo+IEhpIFByYXZlZW4sDQo+IA0KPiBPbiBXZWQsIE1heSAw
MiwgMjAxOCBhdCAwMjowMjozN0FNICswMDAwLCBQcmF2ZWVuIEJhbGFzdWJyYW1hbmlhbiB3cm90
ZToNCj4+IFdlIGNhbiBnZXQgKDEpIGRvbmUgYnV0IEkgZGlzYWdyZWUgdGhhdCB3ZSBjYW4gZGVj
b3VwbGUgKDIpLiBJdCBkb2VzbuKAmXQgbWFrZSBzZW5zZSB0byByZXF1aXJlIHBlcmZvcm1hbmNl
IG92ZXJoZWFkIGFsbCB0aGUgdGltZSB3aXRoIG5vIGJlbmVmaXQuIEZvciB0aGUgSW50ZXJuZXQs
IFBORSBjYW4gcHJldmVudCBvc3NpZmljYXRpb24gc28gaXQgaXMgc2VlbiBhcyBhIHJlYXNvbmFi
bGUgdHJhZGUtb2ZmLiBGb3IgdGhlIGRhdGFjZW50ZXIsIHRoZXJlIGlzIG5vIGtub3duIGJlbmVm
aXQsIG9ubHkgY29zdC4NCj4gDQo+IE1vc3Qgb2Ygd2h5IEkgYW0gcHVzaGluZyBiYWNrIHNvIGhh
cmQgb24gdGhpcyBwb2ludCBpcyB0aGF0IEkgYW0gDQo+IGhhdmluZyBhDQo+ICpyZWFsbHkqIGhh
cmQgdGltZSBnZXR0aW5nIHRoZSBzdGF0ZW1lbnQgb2YgIm5vIGJlbmVmaXQiIChpLmUuLCANCj4g
ZXhhY3RseSB6ZXJvKSB0byBtZXNoIHdpdGggbXkgdW5kZXJzdGFuZGluZyBvZiB0aGUgc2l0dWF0
aW9uLiAgSSBkb24ndCANCj4ga25vdyB0aGUgYmVzdCB3YXkgcGFzdCB0aGlzIGltcGFzc2UgLS0g
aXQgZG9lc24ndCByZWFsbHkgc2VlbSByaWdodCANCj4gZm9yIG1lIHRvIG1ha2UgYSBsaXN0IG9m
IHBvdGVudGlhbCBiZW5lZml0cyBhbmQgaGF2ZSB5b3Ugc2hvb3QgdGhlbSANCj4gZG93biwgZm9y
IGV4YW1wbGUuICBJIHRoaW5rIG1heWJlIHlvdSBhcmUgdHJ5aW5nIHRvIG1ha2UgYSBzbGlnaHRs
eSANCj4gZGlmZmVyZW50IHBvaW50IGludm9sdmluZyBzb21ldGhpbmcgbGlrZSBvbmdvaW5nIG9w
ZXJhdGlvbmFsIGJlbmVmaXRzIA0KPiAoYXMgb3Bwb3NlZCB0byBjb3N0IG9mIGltcGxlbWVudGF0
aW9uL3Jpc2sgb2YgYnVncy9lY29zeXN0ZW0gDQo+IGJlbmVmaXRzKSwgYnV0IEknbSBub3QgZW50
aXJlbHkgc3VyZS4NCj4gDQo+PiBXZSBrbm93IHRoYXQgdGhlcmUgaXMgYSBDUFUgY29zdCwgdGhp
cyBpcyBub3Qgc3BlY3VsYXRpb24uIERvZXNu4oCZdCANCj4+IG1hdHRlciBpZiB0aGUgY29zdCBp
cyAxJSBvciAxMCUuIEhhcmR3YXJlIGltcGxlbWVudGVycyBoYXZlIGFsc28gDQo+PiByYWlzZWQg
Y29uY2VybnMuIEV2ZXJ5DQo+IA0KPiBXZWxsLCBJIHRoaW5rIGl0IHJhdGhlciBkb2VzIG1hdHRl
ciBmb3IgMSUgdnMuIDEwJS4gIElmIGl0IHdhcyAwLjElIA0KPiAodW5saWtlbHksIEkgc3VwcG9z
ZSksIHRoZW4gdGhhdCBtaWdodCBiZSAiaW4gdGhlIG5vaXNlIiBhbmQgbm90IHdvcnRoIA0KPiBk
b2luZyBhbnl0aGluZyBhYm91dCwgZXZlci4gIEZvciBhIDElIGNvc3QsIHRoYXQncyBzaWduaWZp
Y2FudCBlbm91Z2ggDQo+IHRvIG1ha2UgbWUgd2FudCB0byBhZGRyZXNzIGl0IGluIG15IGxvbmct
dGVybSBwbGFucywgYnV0IGl0IGlzIG5vdCANCj4gbmVjZXNzYXJpbHkgYSBiaWcgZW5vdWdoIGlt
cGFjdCB0byByZXF1aXJlIGltbWVkaWF0ZSBhdHRlbnRpb24uICAxMCUsIA0KPiBvbiB0aGUgb3Ro
ZXIgaGFuZCwgcHJvYmFibHkgd291bGQgcmVxdWlyZSBpbW1lZGlhdGUgYXR0ZW50aW9uIGFuZCBi
ZSBhIA0KPiBzaG93LXN0b3BwZXIuDQo+IA0KPj4gQ1BVIGN5Y2xlIHdlIHNwZW5kIG9uIHRoaW5n
cyB0aGF0IGFkZCBubyB2YWx1ZSB0byB0aGUgdXNlciBzaG91bGQgYmUgDQo+PiBxdWVzdGlvbmVk
LiBFdmVyeSBleHRyYSBpbnN0cnVjdGlvbiB3ZSBleGVjdXRlIGluIHRoZSBob3QgZGF0YSBwYXRo
IA0KPj4gbGVhdmVzIGxlc3MgQ1BVIGZvciB3b3JrbG9hZHMsIGJ1cm5zIG1vcmUgcG93ZXIgYW5k
IG1ha2VzIGZvciBhIHdvcnNlIA0KPj4gY29tcGFyaXNvbiB3aXRoIEhUVFBTIG92ZXIgVENQLiBU
aGUgc2FtZSBhcmd1bWVudCBhcyBwcml2YWN5IGhvbGVzIA0KPj4gaG9sZHMgaGVyZSDigJMganVz
dA0KPiANCj4gVGhlICJidXJucyBtb3JlIHBvd2VyIiBhcmd1bWVudCBjYW4gYmUgYXBwbGllZCB0
byBldmVyeSBzaW5nbGUgQ1BVIA0KPiBpbnN0cnVjdGlvbjsgcmVsYXRpdmUgbWVhc3VyZXMgKGku
ZS4sIHBlcmNlbnRhZ2Ugb2YgdG90YWwgQ1BVKSBmcm9tIA0KPiBhY3R1YWwgZGVwbG95bWVudCBh
cmUgd2hhdCBJIGZpbmQgdG8gYmUgbW9zdCBjb21wZWxsaW5nLg0KPiANCj4+IGJlY2F1c2UgdGhl
cmUgYXJlIHNvbWUgZXhpc3RpbmcgcGVyZiBib3R0bGVuZWNrcyBkb2VzbuKAmXQgbWVhbiB3ZSBh
ZGQgDQo+PiBtb3JlLCBwYXJ0aWN1bGFybHkgb25lcyB3ZSBjYW5ub3QgbWl0aWdhdGUuIEkgc2Fp
ZCBpdCBiZWZvcmUgdGhhdCANCj4+IHRoZXJlIGFyZSBsb3RzIG9mIHdheXMgd2UgY2FuIGltcHJv
dmUgVURQIHBlcmYgYnV0IEkgZG9u4oCZdCBrbm93IG9mIA0KPj4gYW55IHRlY2huaXF1ZSBmb3Ig
cmVkdWNpbmcgY3J5cHRvIENQVSBjb3N0IG90aGVyIHRoYW4gaGFyZHdhcmUgb2ZmbG9hZC4NCj4g
DQo+IEFuZCBJIGFzayBhZ2Fpbiwgd2hvIGlzICJ3ZSI/ICAoQXQgdGhpcyBwb2ludCBJIGFtIG1v
c3RseSBhc3N1bWluZyANCj4gImFsbCBRVUlDIGltcGxlbWVudG9ycyIsIGJ1dCBpdCB3b3VsZCBi
ZSBuaWNlIHRvIGJlIHN1cmUuKQ0KPiANCj4+IFRoZSBjb3N0IGlzIGNlcnRhaW5seSB3b3J0aCBz
YXZpbmcgd2l0aCBzb21ldGhpbmcgYXMgc2ltcGxlIGFzIGEgDQo+PiBuZWdvdGlhdGlvbiBtZWNo
YW5pc20uIEFtIEkgbWlzc2luZyBzb21ldGhpbmcgYWJvdXQgYSB0cmFuc3BvcnQgDQo+PiBwYXJh
bWV0ZXIgYmVpbmcNCj4gDQo+PiBGcm9tIHRoZSByZXN0IG9mIHRoZSBkaXNjdXNzaW9uLCBJIGRv
bid0IHRoaW5rIHlvdSd2ZSByZWFsbHkgc29sZCANCj4+IHBlb3BsZQ0KPiBvbiAiY2VydGFpbmx5
IiwgeWV0Lg0KPiANCj4+IGNvbXBsaWNhdGVkIHRvIGltcGxlbWVudD8gSW1wbGVtZW50YXRpb25z
IGFyZSBmcmVlIHRvIHN1cHBvcnQgb25seSANCj4+IFBORSBhbmQgbm90IG5lZ290aWF0ZSBhbnl0
aGluZyBlbHNlLiBUaGVyZSBpcyBhY3R1YWxseSBhbiBldmVuIA0KPj4gc2ltcGxlciBtZWNoYW5p
c20gaWYgYSB0cmFuc3BvcnQgcGFyYW1ldGVyIGlzIGRlZW1lZCBhcyBjb3N0bHk6IGlmIA0KPj4g
dGhlIHBlZXIgc2VuZHMgUE4gPSAwIGluIHRoZSBDSSwgdGhlbiBpdHMgcmVxdWVzdGluZyBubyBQ
TkUgYW5kIHRoZSANCj4+IHJlY2VpdmVyIGNhbiBjaG9vc2UgdG8gcHJvY2VlZCBvciBkcm9wIGFu
ZCBmb3JjZSBUQ1AgZmFsbCBiYWNrLiBUaGlzIA0KPj4gc2hvdWxkIHRha2Ugb25seSBhbiBleHRy
YSBpZiBjaGVjayBvbiB0aGUgcmVjZWl2ZXIgQ0kgcHJvY2Vzc2luZyANCj4+IGxvZ2ljIHRvIGlt
cGxlbWVudC4gSSBhbSBhc3N1bWluZyBoZXJlIHRoYXQgUE5FIG9uIGlucHV0IG9mIDAgd2lsbCBu
b3QgcHJvZHVjZSAwIHNvIGl04oCZcyBhIHNhZmUgc2VudGluZWwgdmFsdWUuDQo+IA0KPiBJIHRo
aW5rIHNvbWUgcGVvcGxlIGFyZSB3b3JyaWVkIG5vdCBqdXN0IGFib3V0IHRoZSANCj4gY29tcGxl
eGl0eS9zaW1wbGljaXR5IG9mIHRoZSBtZWNoYW5pc20gaW1wbGVtZW50ZWQsIGJ1dCBicm9hZGVy
LXNjb3BlIA0KPiBlY29zeXN0ZW0gYW5kIGFyY2hpdGVjdHVyZSBpc3N1ZXMsIHdoZXRoZXIgdGhh
dCdzIGEgZ2VuZXJhbCBjb21wbGV4aXR5IA0KPiByZWR1Y3Rpb24gaW5pdGlhdGl2ZSBvciBtb3Jl
IHN1YnRsZSBpc3N1ZXMgaW52b2x2aW5nIG1pZGRsZWJveGVzIA0KPiBhdHRlbXB0aW5nIHRvIGNv
ZXJjZSBjZXJ0YWluIHNvcnRzIG9mIGJlaGF2aW9yLg0KPiANCj4gLUJlbg0KPiANCg0K


From nobody Wed May  2 06:11:55 2018
Return-Path: <dtikhonov@litespeedtech.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1F77F12D879 for <quic@ietfa.amsl.com>; Wed,  2 May 2018 06:11:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level: 
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 AcadfdJfcgo3 for <quic@ietfa.amsl.com>; Wed,  2 May 2018 06:11:52 -0700 (PDT)
Received: from mail-qk0-x232.google.com (mail-qk0-x232.google.com [IPv6:2607:f8b0:400d:c09::232]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AA66612E866 for <quic@ietf.org>; Wed,  2 May 2018 06:11:50 -0700 (PDT)
Received: by mail-qk0-x232.google.com with SMTP id s70so11121141qks.13 for <quic@ietf.org>; Wed, 02 May 2018 06:11:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=nsIeLMQTDSSCjHNPSNrdRiGtBLfmw2KscW5760RN9jU=; b=OrMoYNA5jF8MYKc87XcWbpLzznoKEHr4lX0eBzOKUB8+VeF4i1W8ydjadE13fmkeD4 HLNl6jT/RW9zpX0B1OdlhhXAJ7B9edkes2ZJj/3M5ZkJKXpWxx0MjufpaHOPWQsMMk89 wrooU7CmZvZzmLBYBG2sCZ9ZdImMZM8WGbaWDV6XFPz9mWQyq9oNp1uVQV2lx4O5j89F PkOqZDOxOVagxuJzsXKv4fRuen2j1H/b1ZZ51b6NONzCTdMGYvfktT+fKc8vkUA2PDTr ZmiNTer3lkCNc1wGhoUa6rIHoOHDt4lJxgrNNQ8/+jelb/8XM27zeKSQPS+94/Gz46Oj MIQw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=nsIeLMQTDSSCjHNPSNrdRiGtBLfmw2KscW5760RN9jU=; b=CpRw/Md2aH4x4qLShfqsV2h1uBVJbEK8XRyC176DZCUzQeTukNziKCVPoqigfHENrF jIYX5wnSTQG/xSYYcgD9Kt6Fvuv42ZsAmVAmLDmBZ3+I35a9JDgqgU64ZeVuonSGiEN8 uAoQU+wuF+k5s4V2vgnJhIFZJ1o8IBREaLv+NDWiZ0LDU4kCTepOAiomFqvxkCmRwfQ4 cVDIRQOzCC+I0EXrUYFmH4jRWsB9SeoEEUB4W6Y2+4ZyRgcSrfUDeFnGqmchdt91sGzu D6mKvgL/nS6I8MNnw+Rfj1RZGwLtvOSP2oazkWmu2YybhBiYMEcdWHcV2eytdFifC6A5 l6HQ==
X-Gm-Message-State: ALQs6tBZVwz17HHrc1X3iXUZA1683KHeOPiAimHtuKDNE+Xg6KBtfzR+ fNDQk1VmBskmPDraY9T1K1L2HA==
X-Google-Smtp-Source: AB8JxZp23SrKJ1qB1qAXCd/RKix9uw7YaQ0CAC4QlZvlHWSSukyHpcmKxNZcvNwyzx7HPFSm/wVz2A==
X-Received: by 10.55.41.20 with SMTP id p20mr16024480qkh.410.1525266709740; Wed, 02 May 2018 06:11:49 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id i63-v6sm8935142qtb.52.2018.05.02.06.11.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 02 May 2018 06:11:49 -0700 (PDT)
Date: Wed, 2 May 2018 09:11:39 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Mirja =?iso-8859-1?Q?K=FChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>
Cc: Benjamin Kaduk <bkaduk=40akamai.com@dmarc.ietf.org>, Praveen Balasubramanian <pravb@microsoft.com>, IETF QUIC WG <quic@ietf.org>
Subject: Re: Getting to consensus on packet number encryption
Message-ID: <20180502131138.GA29220@ubuntu-dmitri>
Mail-Followup-To: Mirja =?iso-8859-1?Q?K=FChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>,  Benjamin Kaduk <bkaduk=40akamai.com@dmarc.ietf.org>, Praveen Balasubramanian <pravb@microsoft.com>, IETF QUIC WG <quic@ietf.org>
References: <01AE46C6-682C-4A21-84CD-1D8DAD6F49D9@fb.com> <CACpbDcdnmHrWMCShYd1pEDBervRKfO1pMUM8hb4tkK9nqH1Mdw@mail.gmail.com> <MWHPR21MB06386100B48E17A059B5A04EB6800@MWHPR21MB0638.namprd21.prod.outlook.com> <20180502121018.GF5742@akamai.com> <4C049C27-FAB7-4CF4-8ABE-DABDE8CD0F8B@tik.ee.ethz.ch>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <4C049C27-FAB7-4CF4-8ABE-DABDE8CD0F8B@tik.ee.ethz.ch>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/QE_8bv4vdo1Fg_-Yl_6gOFi4akc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 13:11:54 -0000

On Wed, May 02, 2018 at 02:46:51PM +0200, Mirja Kühlewind wrote:
> [...] I also learned during my time in the IEFT that complexity itself
> can be a barrier for deployment that should not be underestimated. If
> people don’t understand the specs we write, they will not be able
> to implement (and maintain) our protocols, or at least not be able to
> implement it correctly which might be even worse for deployment and
> security (than not using them at all).

Agreed.

  - Dmitri.


From nobody Wed May  2 06:46:53 2018
Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DE075127076 for <quic@ietfa.amsl.com>; Wed,  2 May 2018 06:46:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3] autolearn=unavailable autolearn_force=no
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 qG4LB_23LdWT for <quic@ietfa.amsl.com>; Wed,  2 May 2018 06:46:48 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [139.133.204.173]) by ietfa.amsl.com (Postfix) with ESMTP id C560F126FB3 for <quic@ietf.org>; Wed,  2 May 2018 06:46:47 -0700 (PDT)
Received: from Gs-MacBook-Pro.local (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPA id F3A971B0021C; Wed,  2 May 2018 14:46:10 +0100 (BST)
Message-ID: <5AE9C122.7060408@erg.abdn.ac.uk>
Date: Wed, 02 May 2018 14:46:10 +0100
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Reply-To: gorry@erg.abdn.ac.uk
Organization: University of Aberdeen
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "Roni Even (A)" <roni.even@huawei.com>
CC: =?UTF-8?B?TWlyamEgS8O8aGxld2luZA==?= <mirja.kuehlewind@tik.ee.ethz.ch>,  Benjamin Kaduk <bkaduk=40akamai.com@dmarc.ietf.org>, Praveen Balasubramanian <pravb@microsoft.com>,  IETF QUIC WG <quic@ietf.org>
Subject: Re: Getting to consensus on packet number encryption
References: <01AE46C6-682C-4A21-84CD-1D8DAD6F49D9@fb.com> <CACpbDcdnmHrWMCShYd1pEDBervRKfO1pMUM8hb4tkK9nqH1Mdw@mail.gmail.com> <MWHPR21MB06386100B48E17A059B5A04EB6800@MWHPR21MB0638.namprd21.prod.outlook.com> <20180502121018.GF5742@akamai.com> <4C049C27-FAB7-4CF4-8ABE-DABDE8CD0F8B@tik.ee.ethz.ch> <6E58094ECC8D8344914996DAD28F1CCD87F34A@DGGEMM506-MBS.china.huawei.com>
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD87F34A@DGGEMM506-MBS.china.huawei.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/fppmc_fFPgWAVDYAv16o5xbLsCs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 13:46:52 -0000

As I see it, adding PNE adds complexity, and presents risks for the 
protocol.

I accept there could also be a future be risk of ossification around any 
packet header - although as said also, the incentives for a middlebox 
doing odd things with a PN in QUIC would seem to me to be quite 
different from the incentives to mangle TCP (where you can easily 
influence the receiver state machine). As Mirja stated, this also leaves 
me skeptical about the benefits of PNE in avoiding ossification, nor the 
downsides of this. The direct linakbility appears from a decision to 
continue the PN sequence in the clear part of the header across a 
migration, not because a PN was visible.

While we are summarising: the majority of IETF transports have to date 
included some form of sequence number in all transport segements. This 
has often been usefully harnessed by tools such as wireshark or similar 
for measurement, debugging, and as a basis for more in depth analysis 
and operational tools. We have decades of experience with this way of 
working - although it seems to me that this list has not proven a useful 
place to discuss that.

I didn't see strong consensus on the value of PNE, so I understand that 
this is just something that has to be decided to move on. And I do wish 
to move on.

Gorry

On 02/05/2018, 14:04, Roni Even (A) wrote:
> Hi,
> I strongly support Mirja's view.  At least we can move forward.
>
> I did not feel from the discussion that the benefits from PNE vs the PN were meaningful enough to make me support any direction too many variables (Ossification, linkability, complexity and processing requirements, PNE not needed for all cases so negotiate,...) with no way for evaluation.  If there was a hum I would probably hum for "not enough information" or "no opinion" but still hope that some decision will be made.
>
>
> Roni Even
>
>
> -----Original Message-----
> From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of Mirja Kühlewind
> Sent: Wednesday, May 02, 2018 3:47 PM
> To: Benjamin Kaduk
> Cc: Praveen Balasubramanian; IETF QUIC WG
> Subject: Re: Getting to consensus on packet number encryption
>
> Hi Ben, hi all,
>
> at this point, I'm fine with moving on with a decision and I didn’t speak up recently because I did feel that just repeating my point of view over and over again (like other do) would bring the discussion forward but I have to say that I’m still skeptical about the benefits of PNE.
>
> I don’t think that it will help linkability as mitigation can be easy detected with simple traffic analysis (if you see both flows; if you don’t see both flows you can’t detect it no matter what) and I rate the risk of ossification on the packet number rather low (both in terms of the risk that it will happen and if even if it happens that it will hinder protocol evolution strongly) such that I simply don’t think that it is justified to spend ANY additional complexity on PNE.
>
> I might be wrong and I understand the fear of people about what can happen in a worst case scenario, however, I also learned during my time in the IEFT that complexity itself can be a barrier for deployment that should not be underestimated. If people don’t understand the specs we write, they will not be able to implement (and maintain) our protocols, or at least not be able to implement it correctly which might be even worse for deployment and security (than not using them at all).
>
> Independent of the decision on PNE, I would like people to please keep in mind that while increased security is preferable, it does not mean that this is a free ticket to add encryption wherever we can, even if there are no or maybe yet unknown benefits as it always comes with a cost.
>
> Mirja
>
>
>
>> Am 02.05.2018 um 14:10 schrieb Benjamin Kaduk<bkaduk=40akamai.com@dmarc.ietf.org>:
>>
>> Hi Praveen,
>>
>> On Wed, May 02, 2018 at 02:02:37AM +0000, Praveen Balasubramanian wrote:
>>> We can get (1) done but I disagree that we can decouple (2). It doesn’t make sense to require performance overhead all the time with no benefit. For the Internet, PNE can prevent ossification so it is seen as a reasonable trade-off. For the datacenter, there is no known benefit, only cost.
>> Most of why I am pushing back so hard on this point is that I am
>> having a
>> *really* hard time getting the statement of "no benefit" (i.e.,
>> exactly zero) to mesh with my understanding of the situation.  I don't
>> know the best way past this impasse -- it doesn't really seem right
>> for me to make a list of potential benefits and have you shoot them
>> down, for example.  I think maybe you are trying to make a slightly
>> different point involving something like ongoing operational benefits
>> (as opposed to cost of implementation/risk of bugs/ecosystem
>> benefits), but I'm not entirely sure.
>>
>>> We know that there is a CPU cost, this is not speculation. Doesn’t
>>> matter if the cost is 1% or 10%. Hardware implementers have also
>>> raised concerns. Every
>> Well, I think it rather does matter for 1% vs. 10%.  If it was 0.1%
>> (unlikely, I suppose), then that might be "in the noise" and not worth
>> doing anything about, ever.  For a 1% cost, that's significant enough
>> to make me want to address it in my long-term plans, but it is not
>> necessarily a big enough impact to require immediate attention.  10%,
>> on the other hand, probably would require immediate attention and be a
>> show-stopper.
>>
>>> CPU cycle we spend on things that add no value to the user should be
>>> questioned. Every extra instruction we execute in the hot data path
>>> leaves less CPU for workloads, burns more power and makes for a worse
>>> comparison with HTTPS over TCP. The same argument as privacy holes
>>> holds here – just
>> The "burns more power" argument can be applied to every single CPU
>> instruction; relative measures (i.e., percentage of total CPU) from
>> actual deployment are what I find to be most compelling.
>>
>>> because there are some existing perf bottlenecks doesn’t mean we add
>>> more, particularly ones we cannot mitigate. I said it before that
>>> there are lots of ways we can improve UDP perf but I don’t know of
>>> any technique for reducing crypto CPU cost other than hardware offload.
>> And I ask again, who is "we"?  (At this point I am mostly assuming
>> "all QUIC implementors", but it would be nice to be sure.)
>>
>>> The cost is certainly worth saving with something as simple as a
>>> negotiation mechanism. Am I missing something about a transport
>>> parameter being
>>>  From the rest of the discussion, I don't think you've really sold
>>> people
>> on "certainly", yet.
>>
>>> complicated to implement? Implementations are free to support only
>>> PNE and not negotiate anything else. There is actually an even
>>> simpler mechanism if a transport parameter is deemed as costly: if
>>> the peer sends PN = 0 in the CI, then its requesting no PNE and the
>>> receiver can choose to proceed or drop and force TCP fall back. This
>>> should take only an extra if check on the receiver CI processing
>>> logic to implement. I am assuming here that PNE on input of 0 will not produce 0 so it’s a safe sentinel value.
>> I think some people are worried not just about the
>> complexity/simplicity of the mechanism implemented, but broader-scope
>> ecosystem and architecture issues, whether that's a general complexity
>> reduction initiative or more subtle issues involving middleboxes
>> attempting to coerce certain sorts of behavior.
>>
>> -Ben
>>


From nobody Wed May  2 09:08:15 2018
Return-Path: <pravb@microsoft.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE0491289B0 for <quic@ietfa.amsl.com>; Wed,  2 May 2018 09:08:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 r4xMb6PKhXlp for <quic@ietfa.amsl.com>; Wed,  2 May 2018 09:08:10 -0700 (PDT)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0110.outbound.protection.outlook.com [104.47.40.110]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 05A511200F1 for <quic@ietf.org>; Wed,  2 May 2018 09:08:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Wqy+nPVcTsTRkmjveJkxTj9fsbkLEbNvOae5mDdfYOQ=; b=H0YJ3AoQe4Z2WodV1J7hQcpKsLmOysPVnzqeTg7PNh5KV3bBY3JbO/IgCPIBEK+TQfrEVCGiFoh3CQlRx2gTBuJollsLW2coqqU0oAFDx5uPOQ29fE/q9wQz6SC6OUhyMiZI8gxgdHyeZaVoWc2bzld3rwe4twszB79/V9UDQuk=
Received: from MWHPR21MB0638.namprd21.prod.outlook.com (10.175.141.139) by MWHPR21MB0829.namprd21.prod.outlook.com (10.173.51.7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.735.4; Wed, 2 May 2018 16:08:08 +0000
Received: from MWHPR21MB0638.namprd21.prod.outlook.com ([fe80::6d48:f7af:d267:2021]) by MWHPR21MB0638.namprd21.prod.outlook.com ([fe80::6d48:f7af:d267:2021%7]) with mapi id 15.20.0735.006; Wed, 2 May 2018 16:08:08 +0000
From: Praveen Balasubramanian <pravb@microsoft.com>
To: Ian Swett <ianswett@google.com>, "bkaduk=40akamai.com@dmarc.ietf.org" <bkaduk=40akamai.com@dmarc.ietf.org>
CC: IETF QUIC WG <quic@ietf.org>
Subject: RE: Getting to consensus on packet number encryption
Thread-Topic: Getting to consensus on packet number encryption
Thread-Index: AQHT4g6OhRYaO/dGwkGGvgfVyogzO6QcXfIAgAA2SbA=
Date: Wed, 2 May 2018 16:08:08 +0000
Message-ID: <MWHPR21MB06380ECA5B8F534088870992B6800@MWHPR21MB0638.namprd21.prod.outlook.com>
References: <01AE46C6-682C-4A21-84CD-1D8DAD6F49D9@fb.com> <CACpbDcdnmHrWMCShYd1pEDBervRKfO1pMUM8hb4tkK9nqH1Mdw@mail.gmail.com> <MWHPR21MB06386100B48E17A059B5A04EB6800@MWHPR21MB0638.namprd21.prod.outlook.com> <20180502121018.GF5742@akamai.com> <CAKcm_gPt7gJNvykq9422Rr4AGxYg+vGjK-aEDfbT+4ryzK1veg@mail.gmail.com>
In-Reply-To: <CAKcm_gPt7gJNvykq9422Rr4AGxYg+vGjK-aEDfbT+4ryzK1veg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e8:9::5ef]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MWHPR21MB0829; 7:OD2m1wFBg1xvY0tc9xCyssOiEkdNIGCDLSwBjMWJHbzM6b05WZv0uvLIlQV8voH5NT1t2mITIwVHQxI6lVtyQA0XJ0Vnss5I/x1YmhPwmGqFgeeJfdzUr+aVpUrjorC6f6FZaEZfZDVoKzV9YYKjefNF0UwrWCQC31LS+00lqsbJvqFxRqRbUh6ZGbsFbI+ALREZI0zLzGvrX2lg9R+vcMPMqbolBwLMGiUC9MkF6fNzrlRA40YP0oQIz7dGmxMx; 20:EvcsanFDvZYt6mSv/QwzgOOdmyX03OXabWJwP4hRstzR8wVTnUVfgf93BmLnElxNh57mngIxBB/giz7pZfxTybUdwD5NY895cZ2WMrnZDsYkqjgM4ylVic06Xibhpf1OG/b7aLQ2DNPYb7xWz48XL+pT8vZUvi2e8xhh6yerN7Q=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(48565401081)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(2017052603328)(7193020); SRVR:MWHPR21MB0829; 
x-ms-traffictypediagnostic: MWHPR21MB0829:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=pravb@microsoft.com; 
x-microsoft-antispam-prvs: <MWHPR21MB08293954B20942B9F125C2ADB6800@MWHPR21MB0829.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(89211679590171)(189930954265078)(211936372134217)(100405760836317)(219752817060721)(21748063052155);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(10201501046)(3231254)(2018427008)(944501410)(52105095)(6055026)(6041310)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123558120)(20161123564045)(6072148)(201708071742011); SRVR:MWHPR21MB0829; BCL:0; PCL:0; RULEID:; SRVR:MWHPR21MB0829; 
x-forefront-prvs: 06607E485E
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(39380400002)(366004)(396003)(376002)(39860400002)(199004)(189003)(476003)(33656002)(3280700002)(8936002)(105586002)(14454004)(478600001)(106356001)(86612001)(68736007)(25786009)(10290500003)(229853002)(6116002)(110136005)(5250100002)(5660300001)(8676002)(97736004)(790700001)(76176011)(55016002)(6506007)(3660700001)(236005)(54896002)(6306002)(46003)(486006)(606006)(9686003)(186003)(6246003)(53936002)(59450400001)(102836004)(2900100001)(53546011)(74316002)(86362001)(93886005)(19609705001)(7696005)(446003)(99286004)(11346002)(7736002)(22452003)(6436002)(316002)(10090500001)(81166006)(4326008)(81156014)(8990500004)(2906002); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR21MB0829; H:MWHPR21MB0638.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: boPG/T1/LqEq8jub1Z+OChjQIzYMuyKFl592U1dtsTZbeOWMFC1YWF3d+BeHBr6/am8Efg/lqiagWmeUmTC9oq08f7IgJMitYxmL4Jwy69W9pZF/H5toEd14CGe/WdJN1+4PQ/szJHYlksXfMJ4H95gvUBtCR672kMBKrN6NfjHGYSpxUVF87VIajjcLLHTI
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_MWHPR21MB06380ECA5B8F534088870992B6800MWHPR21MB0638namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: d5f93cb9-fbe1-49e6-071b-08d5b046e53e
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d5f93cb9-fbe1-49e6-071b-08d5b046e53e
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 May 2018 16:08:08.0367 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR21MB0829
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/A2J7YUJkqrWG1ZItUTUFuqMYe9Q>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 16:08:14 -0000

--_000_MWHPR21MB06380ECA5B8F534088870992B6800MWHPR21MB0638namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

WWVzIHRoYXQgbWVjaGFuaXNtIGlzIHBlcmZlY3RseSBmaW5lIGFuZCBpcyB3aGF0IEkgaGF2ZSBi
ZWVuIGFyZ3VpbmcgZm9yLiBJdCBzaG91bGQgYmUgZmFpcmx5IHN0cmFpZ2h0Zm9yd2FyZCB0byBh
ZGQuIEkgYWxzbyB0aGluayBpdCBpcyBiZXR0ZXIgaW1wbGVtZW50ZWQgdG9nZXRoZXIgd2l0aCBQ
TkUgYnV0IGJhc2VkIG9uIHRoZSBkZWNpc2lvbiBvbiBQTkUsIHdlIGhhdmUgZGVjb3VwbGVkIGl0
LiBJIG11c3QgaGF2ZSBtaXNzZWQgTWFydGlu4oCZcyBzdWdnZXN0ZWQgcGxhbiBhYm91dCB0aGUg
bmVnb3RpYXRpb24sIGlmIHRoYXQgaXMgYmVpbmcgY29uc2lkZXJlZCB0aGVuIEkgaGF2ZSBubyBj
b25jZXJuLiBJc3N1ZSAjMTI5NjxodHRwczovL25hMDEuc2FmZWxpbmtzLnByb3RlY3Rpb24ub3V0
bG9vay5jb20vP3VybD1odHRwcyUzQSUyRiUyRmdpdGh1Yi5jb20lMkZxdWljd2clMkZiYXNlLWRy
YWZ0cyUyRmlzc3VlcyUyRjEyOTYmZGF0YT0wMiU3QzAxJTdDcHJhdmIlNDBtaWNyb3NvZnQuY29t
JTdDYzQ2OTVjNDA1MDlhNGYzNzc3NDIwOGQ1YTQ5NmNkOGMlN0M3MmY5ODhiZjg2ZjE0MWFmOTFh
YjJkN2NkMDExZGI0NyU3QzElN0MwJTdDNjM2NTk1ODg5OTcxNDQ4NjkxJnNkYXRhPUFmZmo1bDUl
MkJuTENUd3ZMTGdTOSUyQjNnemUlMkY5YzlScmhGWklId0glMkZrMUxqdyUzRCZyZXNlcnZlZD0w
PiBpcyBvcGVuIGFuZCB0aGUgbmV4dCBzdGVwIHdvdWxkIGJlIGEgUFIgZm9yIHRoZSBuZWdvdGlh
dGlvbi4NCg0KR2V0dGluZyBiZWZvcmUgYW5kIGFmdGVyIG51bWJlcnMgd2lsbCBiZSBncmVhdC4g
TGFzdCB0aW1lIHdlIGltcGxlbWVudGVkIGFuZCBtZWFzdXJlZCBQTkUsIGl0IHdhcyBzaG93aW5n
IHRvIGJlIDElKyBidXQgd2UgZGlkIG5vdCBkbyBtb3JlIGRldGFpbGVkIHRlc3RzIGxpa2Ugd2hh
dCBoYXBwZW5zIGZvciBzbWFsbGVyIHBhY2tldHMgYW5kIEFDS3MuDQoNCkZyb206IElhbiBTd2V0
dCBbbWFpbHRvOmlhbnN3ZXR0QGdvb2dsZS5jb21dDQpTZW50OiBXZWRuZXNkYXksIE1heSAyLCAy
MDE4IDU6MjggQU0NClRvOiBia2FkdWs9NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnDQpDYzog
UHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gPHByYXZiQG1pY3Jvc29mdC5jb20+OyBJRVRGIFFVSUMg
V0cgPHF1aWNAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogR2V0dGluZyB0byBjb25zZW5zdXMgb24g
cGFja2V0IG51bWJlciBlbmNyeXB0aW9uDQoNClByYXZlZW4sIEkgdGhvdWdodCB0aGUgc3VnZ2Vz
dGVkIHBsYW4gYnkgTWFydGluIHdhcyB0byBkZWZhdWx0IGVuYWJsZSBQTkUgYW5kIHRoZW4gd2Ug
Y2FuIHNlcGFyYXRlbHkgZGlzY3VzcyBhIG1lY2hhbmlzbShpZTogVHJhbnNwb3J0IHBhcmFtcykg
d2hlcmUgaWYgYm90aCBzaWRlcyBhZ3JlZWQsIFBORSB3b3VsZCBiZSBkaXNhYmxlZCBmb3Igc2hv
cnQgaGVhZGVyIHBhY2tldHM/ICBUaGF0IHNlZW1zIGZpbmUgZm9yIHlvdXIgdXNlIGNhc2VzLCBj
b3JyZWN0PyAgT3IgaXMgdGhlIGNvbmNlcm4gdGhhdCB0aGUgV0cgd2lsbCByZWplY3QgYW55IHNv
cnQgb2YgbWVjaGFuaXNtIHRoYXQgYWxsb3dzIFBORSB0byBiZSBkaXNhYmxlZD8NCg0KQW5kIGFz
IEJlbiBzYWlkLCBpZiB0aGlzIGFkZHMgMTAlIENQVSwgdGhlbiB3ZSBuZWVkIHRvIHJldGhpbmsg
dGhpcyBjb21wbGV0ZWx5LCBidXQgSSBkb24ndCBiZWxpZXZlIGl0IHdpbGwuICBIb3BlZnVsbHkg
SSdsbCBoYXZlIHNvbWUgbnVtYmVycyBiZWZvcmUgdGhlIG5leHQgaW50ZXJpbQ0KDQpBTkQgRldJ
VywgSSdkIGxpa2UgdG8gc2VlIGEgUVVJQyB2MiB3aXRoaW4gYSB5ZWFyIG9yIHR3byBvZiBRVUlD
IHYxLg0KDQpPbiBXZWQsIE1heSAyLCAyMDE4IGF0IDg6MTAgQU0gQmVuamFtaW4gS2FkdWsgPGJr
YWR1az00MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmc8bWFpbHRvOjQwYWthbWFpLmNvbUBkbWFy
Yy5pZXRmLm9yZz4+IHdyb3RlOg0KSGkgUHJhdmVlbiwNCg0KT24gV2VkLCBNYXkgMDIsIDIwMTgg
YXQgMDI6MDI6MzdBTSArMDAwMCwgUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gd3JvdGU6DQo+IFdl
IGNhbiBnZXQgKDEpIGRvbmUgYnV0IEkgZGlzYWdyZWUgdGhhdCB3ZSBjYW4gZGVjb3VwbGUgKDIp
LiBJdCBkb2VzbuKAmXQgbWFrZSBzZW5zZSB0byByZXF1aXJlIHBlcmZvcm1hbmNlIG92ZXJoZWFk
IGFsbCB0aGUgdGltZSB3aXRoIG5vIGJlbmVmaXQuIEZvciB0aGUgSW50ZXJuZXQsIFBORSBjYW4g
cHJldmVudCBvc3NpZmljYXRpb24gc28gaXQgaXMgc2VlbiBhcyBhIHJlYXNvbmFibGUgdHJhZGUt
b2ZmLiBGb3IgdGhlIGRhdGFjZW50ZXIsIHRoZXJlIGlzIG5vIGtub3duIGJlbmVmaXQsIG9ubHkg
Y29zdC4NCg0KTW9zdCBvZiB3aHkgSSBhbSBwdXNoaW5nIGJhY2sgc28gaGFyZCBvbiB0aGlzIHBv
aW50IGlzIHRoYXQgSSBhbSBoYXZpbmcgYQ0KKnJlYWxseSogaGFyZCB0aW1lIGdldHRpbmcgdGhl
IHN0YXRlbWVudCBvZiAibm8gYmVuZWZpdCIgKGkuZS4sIGV4YWN0bHkgemVybykNCnRvIG1lc2gg
d2l0aCBteSB1bmRlcnN0YW5kaW5nIG9mIHRoZSBzaXR1YXRpb24uICBJIGRvbid0IGtub3cgdGhl
IGJlc3QNCndheSBwYXN0IHRoaXMgaW1wYXNzZSAtLSBpdCBkb2Vzbid0IHJlYWxseSBzZWVtIHJp
Z2h0IGZvciBtZSB0byBtYWtlIGENCmxpc3Qgb2YgcG90ZW50aWFsIGJlbmVmaXRzIGFuZCBoYXZl
IHlvdSBzaG9vdCB0aGVtIGRvd24sIGZvciBleGFtcGxlLiAgSQ0KdGhpbmsgbWF5YmUgeW91IGFy
ZSB0cnlpbmcgdG8gbWFrZSBhIHNsaWdodGx5IGRpZmZlcmVudCBwb2ludCBpbnZvbHZpbmcNCnNv
bWV0aGluZyBsaWtlIG9uZ29pbmcgb3BlcmF0aW9uYWwgYmVuZWZpdHMgKGFzIG9wcG9zZWQgdG8g
Y29zdCBvZg0KaW1wbGVtZW50YXRpb24vcmlzayBvZiBidWdzL2Vjb3N5c3RlbSBiZW5lZml0cyks
IGJ1dCBJJ20gbm90IGVudGlyZWx5DQpzdXJlLg0KDQo+IFdlIGtub3cgdGhhdCB0aGVyZSBpcyBh
IENQVSBjb3N0LCB0aGlzIGlzIG5vdCBzcGVjdWxhdGlvbi4gRG9lc27igJl0IG1hdHRlciBpZg0K
PiB0aGUgY29zdCBpcyAxJSBvciAxMCUuIEhhcmR3YXJlIGltcGxlbWVudGVycyBoYXZlIGFsc28g
cmFpc2VkIGNvbmNlcm5zLiBFdmVyeQ0KDQpXZWxsLCBJIHRoaW5rIGl0IHJhdGhlciBkb2VzIG1h
dHRlciBmb3IgMSUgdnMuIDEwJS4gIElmIGl0IHdhcyAwLjElDQoodW5saWtlbHksIEkgc3VwcG9z
ZSksIHRoZW4gdGhhdCBtaWdodCBiZSAiaW4gdGhlIG5vaXNlIiBhbmQgbm90IHdvcnRoDQpkb2lu
ZyBhbnl0aGluZyBhYm91dCwgZXZlci4gIEZvciBhIDElIGNvc3QsIHRoYXQncyBzaWduaWZpY2Fu
dCBlbm91Z2ggdG8NCm1ha2UgbWUgd2FudCB0byBhZGRyZXNzIGl0IGluIG15IGxvbmctdGVybSBw
bGFucywgYnV0IGl0IGlzIG5vdA0KbmVjZXNzYXJpbHkgYSBiaWcgZW5vdWdoIGltcGFjdCB0byBy
ZXF1aXJlIGltbWVkaWF0ZSBhdHRlbnRpb24uICAxMCUsIG9uDQp0aGUgb3RoZXIgaGFuZCwgcHJv
YmFibHkgd291bGQgcmVxdWlyZSBpbW1lZGlhdGUgYXR0ZW50aW9uIGFuZCBiZSBhDQpzaG93LXN0
b3BwZXIuDQoNCj4gQ1BVIGN5Y2xlIHdlIHNwZW5kIG9uIHRoaW5ncyB0aGF0IGFkZCBubyB2YWx1
ZSB0byB0aGUgdXNlciBzaG91bGQgYmUNCj4gcXVlc3Rpb25lZC4gRXZlcnkgZXh0cmEgaW5zdHJ1
Y3Rpb24gd2UgZXhlY3V0ZSBpbiB0aGUgaG90IGRhdGEgcGF0aCBsZWF2ZXMNCj4gbGVzcyBDUFUg
Zm9yIHdvcmtsb2FkcywgYnVybnMgbW9yZSBwb3dlciBhbmQgbWFrZXMgZm9yIGEgd29yc2UgY29t
cGFyaXNvbg0KPiB3aXRoIEhUVFBTIG92ZXIgVENQLiBUaGUgc2FtZSBhcmd1bWVudCBhcyBwcml2
YWN5IGhvbGVzIGhvbGRzIGhlcmUg4oCTIGp1c3QNCg0KVGhlICJidXJucyBtb3JlIHBvd2VyIiBh
cmd1bWVudCBjYW4gYmUgYXBwbGllZCB0byBldmVyeSBzaW5nbGUgQ1BVDQppbnN0cnVjdGlvbjsg
cmVsYXRpdmUgbWVhc3VyZXMgKGkuZS4sIHBlcmNlbnRhZ2Ugb2YgdG90YWwgQ1BVKSBmcm9tDQph
Y3R1YWwgZGVwbG95bWVudCBhcmUgd2hhdCBJIGZpbmQgdG8gYmUgbW9zdCBjb21wZWxsaW5nLg0K
DQo+IGJlY2F1c2UgdGhlcmUgYXJlIHNvbWUgZXhpc3RpbmcgcGVyZiBib3R0bGVuZWNrcyBkb2Vz
buKAmXQgbWVhbiB3ZSBhZGQgbW9yZSwNCj4gcGFydGljdWxhcmx5IG9uZXMgd2UgY2Fubm90IG1p
dGlnYXRlLiBJIHNhaWQgaXQgYmVmb3JlIHRoYXQgdGhlcmUgYXJlIGxvdHMgb2YNCj4gd2F5cyB3
ZSBjYW4gaW1wcm92ZSBVRFAgcGVyZiBidXQgSSBkb27igJl0IGtub3cgb2YgYW55IHRlY2huaXF1
ZSBmb3IgcmVkdWNpbmcNCj4gY3J5cHRvIENQVSBjb3N0IG90aGVyIHRoYW4gaGFyZHdhcmUgb2Zm
bG9hZC4NCg0KQW5kIEkgYXNrIGFnYWluLCB3aG8gaXMgIndlIj8gIChBdCB0aGlzIHBvaW50IEkg
YW0gbW9zdGx5IGFzc3VtaW5nICJhbGwNClFVSUMgaW1wbGVtZW50b3JzIiwgYnV0IGl0IHdvdWxk
IGJlIG5pY2UgdG8gYmUgc3VyZS4pDQoNCj4gVGhlIGNvc3QgaXMgY2VydGFpbmx5IHdvcnRoIHNh
dmluZyB3aXRoIHNvbWV0aGluZyBhcyBzaW1wbGUgYXMgYSBuZWdvdGlhdGlvbg0KPiBtZWNoYW5p
c20uIEFtIEkgbWlzc2luZyBzb21ldGhpbmcgYWJvdXQgYSB0cmFuc3BvcnQgcGFyYW1ldGVyIGJl
aW5nDQoNCj5Gcm9tIHRoZSByZXN0IG9mIHRoZSBkaXNjdXNzaW9uLCBJIGRvbid0IHRoaW5rIHlv
dSd2ZSByZWFsbHkgc29sZCBwZW9wbGUNCm9uICJjZXJ0YWlubHkiLCB5ZXQuDQoNCj4gY29tcGxp
Y2F0ZWQgdG8gaW1wbGVtZW50PyBJbXBsZW1lbnRhdGlvbnMgYXJlIGZyZWUgdG8gc3VwcG9ydCBv
bmx5IFBORSBhbmQNCj4gbm90IG5lZ290aWF0ZSBhbnl0aGluZyBlbHNlLiBUaGVyZSBpcyBhY3R1
YWxseSBhbiBldmVuIHNpbXBsZXIgbWVjaGFuaXNtIGlmIGENCj4gdHJhbnNwb3J0IHBhcmFtZXRl
ciBpcyBkZWVtZWQgYXMgY29zdGx5OiBpZiB0aGUgcGVlciBzZW5kcyBQTiA9IDAgaW4gdGhlIENJ
LA0KPiB0aGVuIGl0cyByZXF1ZXN0aW5nIG5vIFBORSBhbmQgdGhlIHJlY2VpdmVyIGNhbiBjaG9v
c2UgdG8gcHJvY2VlZCBvciBkcm9wIGFuZA0KPiBmb3JjZSBUQ1AgZmFsbCBiYWNrLiBUaGlzIHNo
b3VsZCB0YWtlIG9ubHkgYW4gZXh0cmEgaWYgY2hlY2sgb24gdGhlIHJlY2VpdmVyDQo+IENJIHBy
b2Nlc3NpbmcgbG9naWMgdG8gaW1wbGVtZW50LiBJIGFtIGFzc3VtaW5nIGhlcmUgdGhhdCBQTkUg
b24gaW5wdXQgb2YgMA0KPiB3aWxsIG5vdCBwcm9kdWNlIDAgc28gaXTigJlzIGEgc2FmZSBzZW50
aW5lbCB2YWx1ZS4NCg0KSSB0aGluayBzb21lIHBlb3BsZSBhcmUgd29ycmllZCBub3QganVzdCBh
Ym91dCB0aGUgY29tcGxleGl0eS9zaW1wbGljaXR5DQpvZiB0aGUgbWVjaGFuaXNtIGltcGxlbWVu
dGVkLCBidXQgYnJvYWRlci1zY29wZSBlY29zeXN0ZW0gYW5kDQphcmNoaXRlY3R1cmUgaXNzdWVz
LCB3aGV0aGVyIHRoYXQncyBhIGdlbmVyYWwgY29tcGxleGl0eSByZWR1Y3Rpb24NCmluaXRpYXRp
dmUgb3IgbW9yZSBzdWJ0bGUgaXNzdWVzIGludm9sdmluZyBtaWRkbGVib3hlcyBhdHRlbXB0aW5n
IHRvDQpjb2VyY2UgY2VydGFpbiBzb3J0cyBvZiBiZWhhdmlvci4NCg0KLUJlbg0K

--_000_MWHPR21MB06380ECA5B8F534088870992B6800MWHPR21MB0638namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQph
OmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xv
cjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1z
b0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJw
bGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLm1zb25vcm1hbDAsIGxpLm1zb25v
cm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCgltc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21z
by1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlm
Ow0KCWNvbG9yOndpbmRvd3RleHQ7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5
cGU6cGVyc29uYWwtY29tcG9zZTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsN
Cgljb2xvcjp3aW5kb3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4
cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNh
bnMtc2VyaWY7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1h
cmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6
V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpz
aGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5k
aWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRp
dCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48
L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVl
IiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5ZZXMgdGhhdCBtZWNoYW5pc20gaXMgcGVyZmVjdGx5IGZpbmUgYW5kIGlzIHdo
YXQgSSBoYXZlIGJlZW4gYXJndWluZyBmb3IuIEl0IHNob3VsZCBiZSBmYWlybHkgc3RyYWlnaHRm
b3J3YXJkIHRvIGFkZC4gSSBhbHNvIHRoaW5rIGl0IGlzIGJldHRlciBpbXBsZW1lbnRlZCB0b2dl
dGhlciB3aXRoIFBORSBidXQgYmFzZWQgb24gdGhlIGRlY2lzaW9uIG9uIFBORSwgd2UgaGF2ZSBk
ZWNvdXBsZWQgaXQuIEkgbXVzdA0KIGhhdmUgbWlzc2VkIE1hcnRpbuKAmXMgc3VnZ2VzdGVkIHBs
YW4gYWJvdXQgdGhlIG5lZ290aWF0aW9uLCBpZiB0aGF0IGlzIGJlaW5nIGNvbnNpZGVyZWQgdGhl
biBJIGhhdmUgbm8gY29uY2Vybi4gSXNzdWUNCjxhIGhyZWY9Imh0dHBzOi8vbmEwMS5zYWZlbGlu
a3MucHJvdGVjdGlvbi5vdXRsb29rLmNvbS8/dXJsPWh0dHBzJTNBJTJGJTJGZ2l0aHViLmNvbSUy
RnF1aWN3ZyUyRmJhc2UtZHJhZnRzJTJGaXNzdWVzJTJGMTI5NiZhbXA7ZGF0YT0wMiU3QzAxJTdD
cHJhdmIlNDBtaWNyb3NvZnQuY29tJTdDYzQ2OTVjNDA1MDlhNGYzNzc3NDIwOGQ1YTQ5NmNkOGMl
N0M3MmY5ODhiZjg2ZjE0MWFmOTFhYjJkN2NkMDExZGI0NyU3QzElN0MwJTdDNjM2NTk1ODg5OTcx
NDQ4NjkxJmFtcDtzZGF0YT1BZmZqNWw1JTJCbkxDVHd2TExnUzklMkIzZ3plJTJGOWM5UnJoRlpJ
SHdIJTJGazFManclM0QmYW1wO3Jlc2VydmVkPTAiPg0KIzEyOTY8L2E+IGlzIG9wZW4gYW5kIHRo
ZSBuZXh0IHN0ZXAgd291bGQgYmUgYSBQUiBmb3IgdGhlIG5lZ290aWF0aW9uLiA8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+R2V0dGluZyBiZWZvcmUgYW5kIGFmdGVyIG51bWJlcnMgd2lsbCBiZSBn
cmVhdC4gTGFzdCB0aW1lIHdlIGltcGxlbWVudGVkIGFuZCBtZWFzdXJlZCBQTkUsIGl0IHdhcyBz
aG93aW5nIHRvIGJlIDElJiM0MzsgYnV0IHdlIGRpZCBub3QgZG8gbW9yZSBkZXRhaWxlZCB0ZXN0
cyBsaWtlIHdoYXQgaGFwcGVucyBmb3Igc21hbGxlciBwYWNrZXRzIGFuZCBBQ0tzLg0KPG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxiPkZyb206PC9iPiBJYW4gU3dldHQgW21haWx0bzppYW5zd2V0
dEBnb29nbGUuY29tXSA8YnI+DQo8Yj5TZW50OjwvYj4gV2VkbmVzZGF5LCBNYXkgMiwgMjAxOCA1
OjI4IEFNPGJyPg0KPGI+VG86PC9iPiBia2FkdWs9NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3Jn
PGJyPg0KPGI+Q2M6PC9iPiBQcmF2ZWVuIEJhbGFzdWJyYW1hbmlhbiAmbHQ7cHJhdmJAbWljcm9z
b2Z0LmNvbSZndDs7IElFVEYgUVVJQyBXRyAmbHQ7cXVpY0BpZXRmLm9yZyZndDs8YnI+DQo8Yj5T
dWJqZWN0OjwvYj4gUmU6IEdldHRpbmcgdG8gY29uc2Vuc3VzIG9uIHBhY2tldCBudW1iZXIgZW5j
cnlwdGlvbjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+UHJhdmVlbiwgSSB0aG91Z2h0
IHRoZSBzdWdnZXN0ZWQgcGxhbiBieSBNYXJ0aW4gd2FzIHRvIGRlZmF1bHQgZW5hYmxlIFBORSBh
bmQgdGhlbiB3ZSBjYW4gc2VwYXJhdGVseSBkaXNjdXNzIGEgbWVjaGFuaXNtKGllOiBUcmFuc3Bv
cnQgcGFyYW1zKSB3aGVyZSBpZiBib3RoIHNpZGVzIGFncmVlZCwgUE5FIHdvdWxkIGJlIGRpc2Fi
bGVkIGZvciBzaG9ydCBoZWFkZXIgcGFja2V0cz8mbmJzcDsgVGhhdCBzZWVtcyBmaW5lDQogZm9y
IHlvdXIgdXNlIGNhc2VzLCBjb3JyZWN0PyZuYnNwOyBPciBpcyB0aGUgY29uY2VybiB0aGF0IHRo
ZSBXRyB3aWxsIHJlamVjdCBhbnkgc29ydCBvZiBtZWNoYW5pc20gdGhhdCBhbGxvd3MgUE5FIHRv
IGJlIGRpc2FibGVkPzxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+QW5kIGFzIEJlbiBzYWlkLCBpZiB0aGlzIGFkZHMgMTAlIENQVSwgdGhlbiB3ZSBuZWVkIHRv
IHJldGhpbmsgdGhpcyBjb21wbGV0ZWx5LCBidXQgSSBkb24ndCBiZWxpZXZlIGl0IHdpbGwuJm5i
c3A7IEhvcGVmdWxseSBJJ2xsIGhhdmUgc29tZSBudW1iZXJzIGJlZm9yZSB0aGUgbmV4dCBpbnRl
cmltPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PkFORCBGV0lXLCBJJ2QgbGlrZSB0byBzZWUgYSBRVUlDIHYyIHdpdGhpbiBhIHllYXIgb3IgdHdv
IG9mIFFVSUMgdjEuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPk9uIFdlZCwgTWF5IDIsIDIwMTggYXQgODoxMCBBTSBCZW5qYW1pbiBLYWR1ayAm
bHQ7YmthZHVrPTxhIGhyZWY9Im1haWx0bzo0MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmciPjQw
YWthbWFpLmNvbUBkbWFyYy5pZXRmLm9yZzwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQg
I0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0
O21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0OjBpbjttYXJnaW4tYm90dG9tOjUuMHB0Ij4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+SGkgUHJh
dmVlbiw8YnI+DQo8YnI+DQpPbiBXZWQsIE1heSAwMiwgMjAxOCBhdCAwMjowMjozN0FNICYjNDM7
MDAwMCwgUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gd3JvdGU6PGJyPg0KJmd0OyBXZSBjYW4gZ2V0
ICgxKSBkb25lIGJ1dCBJIGRpc2FncmVlIHRoYXQgd2UgY2FuIGRlY291cGxlICgyKS4gSXQgZG9l
c27igJl0IG1ha2Ugc2Vuc2UgdG8gcmVxdWlyZSBwZXJmb3JtYW5jZSBvdmVyaGVhZCBhbGwgdGhl
IHRpbWUgd2l0aCBubyBiZW5lZml0LiBGb3IgdGhlIEludGVybmV0LCBQTkUgY2FuIHByZXZlbnQg
b3NzaWZpY2F0aW9uIHNvIGl0IGlzIHNlZW4gYXMgYSByZWFzb25hYmxlIHRyYWRlLW9mZi4gRm9y
IHRoZSBkYXRhY2VudGVyLCB0aGVyZQ0KIGlzIG5vIGtub3duIGJlbmVmaXQsIG9ubHkgY29zdC48
YnI+DQo8YnI+DQpNb3N0IG9mIHdoeSBJIGFtIHB1c2hpbmcgYmFjayBzbyBoYXJkIG9uIHRoaXMg
cG9pbnQgaXMgdGhhdCBJIGFtIGhhdmluZyBhPGJyPg0KKnJlYWxseSogaGFyZCB0aW1lIGdldHRp
bmcgdGhlIHN0YXRlbWVudCBvZiAmcXVvdDtubyBiZW5lZml0JnF1b3Q7IChpLmUuLCBleGFjdGx5
IHplcm8pPGJyPg0KdG8gbWVzaCB3aXRoIG15IHVuZGVyc3RhbmRpbmcgb2YgdGhlIHNpdHVhdGlv
bi4mbmJzcDsgSSBkb24ndCBrbm93IHRoZSBiZXN0PGJyPg0Kd2F5IHBhc3QgdGhpcyBpbXBhc3Nl
IC0tIGl0IGRvZXNuJ3QgcmVhbGx5IHNlZW0gcmlnaHQgZm9yIG1lIHRvIG1ha2UgYTxicj4NCmxp
c3Qgb2YgcG90ZW50aWFsIGJlbmVmaXRzIGFuZCBoYXZlIHlvdSBzaG9vdCB0aGVtIGRvd24sIGZv
ciBleGFtcGxlLiZuYnNwOyBJPGJyPg0KdGhpbmsgbWF5YmUgeW91IGFyZSB0cnlpbmcgdG8gbWFr
ZSBhIHNsaWdodGx5IGRpZmZlcmVudCBwb2ludCBpbnZvbHZpbmc8YnI+DQpzb21ldGhpbmcgbGlr
ZSBvbmdvaW5nIG9wZXJhdGlvbmFsIGJlbmVmaXRzIChhcyBvcHBvc2VkIHRvIGNvc3Qgb2Y8YnI+
DQppbXBsZW1lbnRhdGlvbi9yaXNrIG9mIGJ1Z3MvZWNvc3lzdGVtIGJlbmVmaXRzKSwgYnV0IEkn
bSBub3QgZW50aXJlbHk8YnI+DQpzdXJlLjxicj4NCjxicj4NCiZndDsgV2Uga25vdyB0aGF0IHRo
ZXJlIGlzIGEgQ1BVIGNvc3QsIHRoaXMgaXMgbm90IHNwZWN1bGF0aW9uLiBEb2VzbuKAmXQgbWF0
dGVyIGlmPGJyPg0KJmd0OyB0aGUgY29zdCBpcyAxJSBvciAxMCUuIEhhcmR3YXJlIGltcGxlbWVu
dGVycyBoYXZlIGFsc28gcmFpc2VkIGNvbmNlcm5zLiBFdmVyeTxicj4NCjxicj4NCldlbGwsIEkg
dGhpbmsgaXQgcmF0aGVyIGRvZXMgbWF0dGVyIGZvciAxJSB2cy4gMTAlLiZuYnNwOyBJZiBpdCB3
YXMgMC4xJTxicj4NCih1bmxpa2VseSwgSSBzdXBwb3NlKSwgdGhlbiB0aGF0IG1pZ2h0IGJlICZx
dW90O2luIHRoZSBub2lzZSZxdW90OyBhbmQgbm90IHdvcnRoPGJyPg0KZG9pbmcgYW55dGhpbmcg
YWJvdXQsIGV2ZXIuJm5ic3A7IEZvciBhIDElIGNvc3QsIHRoYXQncyBzaWduaWZpY2FudCBlbm91
Z2ggdG88YnI+DQptYWtlIG1lIHdhbnQgdG8gYWRkcmVzcyBpdCBpbiBteSBsb25nLXRlcm0gcGxh
bnMsIGJ1dCBpdCBpcyBub3Q8YnI+DQpuZWNlc3NhcmlseSBhIGJpZyBlbm91Z2ggaW1wYWN0IHRv
IHJlcXVpcmUgaW1tZWRpYXRlIGF0dGVudGlvbi4mbmJzcDsgMTAlLCBvbjxicj4NCnRoZSBvdGhl
ciBoYW5kLCBwcm9iYWJseSB3b3VsZCByZXF1aXJlIGltbWVkaWF0ZSBhdHRlbnRpb24gYW5kIGJl
IGE8YnI+DQpzaG93LXN0b3BwZXIuPGJyPg0KPGJyPg0KJmd0OyBDUFUgY3ljbGUgd2Ugc3BlbmQg
b24gdGhpbmdzIHRoYXQgYWRkIG5vIHZhbHVlIHRvIHRoZSB1c2VyIHNob3VsZCBiZTxicj4NCiZn
dDsgcXVlc3Rpb25lZC4gRXZlcnkgZXh0cmEgaW5zdHJ1Y3Rpb24gd2UgZXhlY3V0ZSBpbiB0aGUg
aG90IGRhdGEgcGF0aCBsZWF2ZXM8YnI+DQomZ3Q7IGxlc3MgQ1BVIGZvciB3b3JrbG9hZHMsIGJ1
cm5zIG1vcmUgcG93ZXIgYW5kIG1ha2VzIGZvciBhIHdvcnNlIGNvbXBhcmlzb248YnI+DQomZ3Q7
IHdpdGggSFRUUFMgb3ZlciBUQ1AuIFRoZSBzYW1lIGFyZ3VtZW50IGFzIHByaXZhY3kgaG9sZXMg
aG9sZHMgaGVyZSDigJMganVzdDxicj4NCjxicj4NClRoZSAmcXVvdDtidXJucyBtb3JlIHBvd2Vy
JnF1b3Q7IGFyZ3VtZW50IGNhbiBiZSBhcHBsaWVkIHRvIGV2ZXJ5IHNpbmdsZSBDUFU8YnI+DQpp
bnN0cnVjdGlvbjsgcmVsYXRpdmUgbWVhc3VyZXMgKGkuZS4sIHBlcmNlbnRhZ2Ugb2YgdG90YWwg
Q1BVKSBmcm9tPGJyPg0KYWN0dWFsIGRlcGxveW1lbnQgYXJlIHdoYXQgSSBmaW5kIHRvIGJlIG1v
c3QgY29tcGVsbGluZy48YnI+DQo8YnI+DQomZ3Q7IGJlY2F1c2UgdGhlcmUgYXJlIHNvbWUgZXhp
c3RpbmcgcGVyZiBib3R0bGVuZWNrcyBkb2VzbuKAmXQgbWVhbiB3ZSBhZGQgbW9yZSw8YnI+DQom
Z3Q7IHBhcnRpY3VsYXJseSBvbmVzIHdlIGNhbm5vdCBtaXRpZ2F0ZS4gSSBzYWlkIGl0IGJlZm9y
ZSB0aGF0IHRoZXJlIGFyZSBsb3RzIG9mPGJyPg0KJmd0OyB3YXlzIHdlIGNhbiBpbXByb3ZlIFVE
UCBwZXJmIGJ1dCBJIGRvbuKAmXQga25vdyBvZiBhbnkgdGVjaG5pcXVlIGZvciByZWR1Y2luZzxi
cj4NCiZndDsgY3J5cHRvIENQVSBjb3N0IG90aGVyIHRoYW4gaGFyZHdhcmUgb2ZmbG9hZC48YnI+
DQo8YnI+DQpBbmQgSSBhc2sgYWdhaW4sIHdobyBpcyAmcXVvdDt3ZSZxdW90Oz8mbmJzcDsgKEF0
IHRoaXMgcG9pbnQgSSBhbSBtb3N0bHkgYXNzdW1pbmcgJnF1b3Q7YWxsPGJyPg0KUVVJQyBpbXBs
ZW1lbnRvcnMmcXVvdDssIGJ1dCBpdCB3b3VsZCBiZSBuaWNlIHRvIGJlIHN1cmUuKTxicj4NCjxi
cj4NCiZndDsgVGhlIGNvc3QgaXMgY2VydGFpbmx5IHdvcnRoIHNhdmluZyB3aXRoIHNvbWV0aGlu
ZyBhcyBzaW1wbGUgYXMgYSBuZWdvdGlhdGlvbjxicj4NCiZndDsgbWVjaGFuaXNtLiBBbSBJIG1p
c3Npbmcgc29tZXRoaW5nIGFib3V0IGEgdHJhbnNwb3J0IHBhcmFtZXRlciBiZWluZzxicj4NCjxi
cj4NCiZndDtGcm9tIHRoZSByZXN0IG9mIHRoZSBkaXNjdXNzaW9uLCBJIGRvbid0IHRoaW5rIHlv
dSd2ZSByZWFsbHkgc29sZCBwZW9wbGU8YnI+DQpvbiAmcXVvdDtjZXJ0YWlubHkmcXVvdDssIHll
dC48YnI+DQo8YnI+DQomZ3Q7IGNvbXBsaWNhdGVkIHRvIGltcGxlbWVudD8gSW1wbGVtZW50YXRp
b25zIGFyZSBmcmVlIHRvIHN1cHBvcnQgb25seSBQTkUgYW5kPGJyPg0KJmd0OyBub3QgbmVnb3Rp
YXRlIGFueXRoaW5nIGVsc2UuIFRoZXJlIGlzIGFjdHVhbGx5IGFuIGV2ZW4gc2ltcGxlciBtZWNo
YW5pc20gaWYgYTxicj4NCiZndDsgdHJhbnNwb3J0IHBhcmFtZXRlciBpcyBkZWVtZWQgYXMgY29z
dGx5OiBpZiB0aGUgcGVlciBzZW5kcyBQTiA9IDAgaW4gdGhlIENJLDxicj4NCiZndDsgdGhlbiBp
dHMgcmVxdWVzdGluZyBubyBQTkUgYW5kIHRoZSByZWNlaXZlciBjYW4gY2hvb3NlIHRvIHByb2Nl
ZWQgb3IgZHJvcCBhbmQ8YnI+DQomZ3Q7IGZvcmNlIFRDUCBmYWxsIGJhY2suIFRoaXMgc2hvdWxk
IHRha2Ugb25seSBhbiBleHRyYSBpZiBjaGVjayBvbiB0aGUgcmVjZWl2ZXI8YnI+DQomZ3Q7IENJ
IHByb2Nlc3NpbmcgbG9naWMgdG8gaW1wbGVtZW50LiBJIGFtIGFzc3VtaW5nIGhlcmUgdGhhdCBQ
TkUgb24gaW5wdXQgb2YgMDxicj4NCiZndDsgd2lsbCBub3QgcHJvZHVjZSAwIHNvIGl04oCZcyBh
IHNhZmUgc2VudGluZWwgdmFsdWUuPGJyPg0KPGJyPg0KSSB0aGluayBzb21lIHBlb3BsZSBhcmUg
d29ycmllZCBub3QganVzdCBhYm91dCB0aGUgY29tcGxleGl0eS9zaW1wbGljaXR5PGJyPg0Kb2Yg
dGhlIG1lY2hhbmlzbSBpbXBsZW1lbnRlZCwgYnV0IGJyb2FkZXItc2NvcGUgZWNvc3lzdGVtIGFu
ZDxicj4NCmFyY2hpdGVjdHVyZSBpc3N1ZXMsIHdoZXRoZXIgdGhhdCdzIGEgZ2VuZXJhbCBjb21w
bGV4aXR5IHJlZHVjdGlvbjxicj4NCmluaXRpYXRpdmUgb3IgbW9yZSBzdWJ0bGUgaXNzdWVzIGlu
dm9sdmluZyBtaWRkbGVib3hlcyBhdHRlbXB0aW5nIHRvPGJyPg0KY29lcmNlIGNlcnRhaW4gc29y
dHMgb2YgYmVoYXZpb3IuPGJyPg0KPGJyPg0KLUJlbjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1
b3RlPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_MWHPR21MB06380ECA5B8F534088870992B6800MWHPR21MB0638namp_--


From nobody Wed May  2 10:39:16 2018
Return-Path: <huitema@huitema.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B2AF012D7ED for <quic@ietfa.amsl.com>; Wed,  2 May 2018 10:39:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 MP0w7O8Lnj98 for <quic@ietfa.amsl.com>; Wed,  2 May 2018 10:39:12 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 3E6CD1270A3 for <quic@ietf.org>; Wed,  2 May 2018 10:39:12 -0700 (PDT)
Received: from xsmtp01.mail2web.com ([168.144.250.230]) by mx64.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1fDvid-000Ce1-QS for quic@ietf.org; Wed, 02 May 2018 19:39:08 +0200
Received: from [10.5.2.35] (helo=xmail10.myhosting.com) by xsmtp01.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1fDviX-0003jQ-AC for quic@ietf.org; Wed, 02 May 2018 13:39:01 -0400
Received: (qmail 17587 invoked from network); 2 May 2018 17:38:49 -0000
Received: from unknown (HELO [192.168.1.14]) (Authenticated-user:_huitema@huitema.net@[90.105.145.87]) (envelope-sender <huitema@huitema.net>) by xmail10.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 2 May 2018 17:38:49 -0000
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (1.0)
From: Christian Huitema <huitema@huitema.net>
X-Mailer: iPhone Mail (15E216)
In-Reply-To: <5AE9C122.7060408@erg.abdn.ac.uk>
Date: Wed, 2 May 2018 19:38:43 +0200
Cc: "Roni Even (A)" <roni.even@huawei.com>, Praveen Balasubramanian <pravb@microsoft.com>, IETF QUIC WG <quic@ietf.org>, =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>, Benjamin Kaduk <bkaduk=40akamai.com@dmarc.ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <94292722-D812-4196-BC41-C3B2B7D277A1@huitema.net>
References: <01AE46C6-682C-4A21-84CD-1D8DAD6F49D9@fb.com> <CACpbDcdnmHrWMCShYd1pEDBervRKfO1pMUM8hb4tkK9nqH1Mdw@mail.gmail.com> <MWHPR21MB06386100B48E17A059B5A04EB6800@MWHPR21MB0638.namprd21.prod.outlook.com> <20180502121018.GF5742@akamai.com> <4C049C27-FAB7-4CF4-8ABE-DABDE8CD0F8B@tik.ee.ethz.ch> <6E58094ECC8D8344914996DAD28F1CCD87F34A@DGGEMM506-MBS.china.huawei.com> <5AE9C122.7060408@erg.abdn.ac.uk>
To: gorry@erg.abdn.ac.uk
Subject: Re: Getting to consensus on packet number encryption
X-Originating-IP: 168.144.250.230
X-AntiSpamCloud-Domain: xsmtpout.mail2web.com
X-AntiSpamCloud-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-AntiSpamCloud-Outgoing-Class: ham
X-AntiSpamCloud-Outgoing-Evidence: Combined (0.02)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5oNisjT0MgLlHlYwGdMv3zR602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO37pNwwF1lRXh5rzvPzo9Jts1ujulqUFmMITHM77eiViZR5x92UIX8Dz48sAy6kZhM7i TvJ2/ZGzVWB9scFAaCdIFaUvXN+CI+RGy3Me16pBmePYa3CQqb9L6x2mHOMrWx/TBCf6oYXAWGet lavcAjAiREicRPMV5adYQyNOvKmgizQS7ZJXB6rwDFOa1j0OJR6ijzwzq5HGxV3pRhOdYuobeA2G NaAif0QyGEAJd8kel+zffa+S3paXsykGResyE7dAzbZabvf4+eAvvSn0D5YzxzA4C4+ILjmdkQoL 6F7cCSavQBrPoagEXfZ210Cx8bwqyT5p50x81ZKcmzCu2U1l0pLLr6Q2GfeLeJGF+80D4WY7xWSn pVjQVprFFOt2hDWKtLT9WR57oxUvRixjadcobnduoQv5Sp6y3SmK1n5SMPepZn00xVXQbuUt1pns FwEiRQv+PVjjwa+Z5RFCOMRB5wS+iRG/ctaYj82jDD3qGaYW0HWeDLV4Niuc/GonMPI9UybIUHdE /L+yu1NsrS1giNplmw3yp4FFFCuS+k6jh5d4Swn5E67RV+LaU4GmVjH8gYlRWMzXMtJksqe+xLeX oHkzkRzbKyRDRP8j7fY6rka7glK07Vs7rsUOKUDQF2h+wlfAS2SbL4bvnSO/22UmcHZwcoiAtd0I g50mD8t8bnC1YHvZzd5/K0YJcya/dpRins15oKFWvUk5C9olBXDhjX6bHzu+acs8UcTQf4enw6nI oDr0sXUZ7YZoZ/GZ+jr47k1ZYM+XPLUTB3aEhddz5NQBt6vrTjaii/MA7FoCAhy1/eljfSN5aXns qLZLef9qwM7RXpJS8RjTdyh2j5AWyDZ7BRCxIW6XiPgk5wgNeRXbC69qDBnTAPdQSCnD1TRj9D8H LKHAKpPGP8EPnuDHTXhIrVzYteKGVryF5qVZ
X-Report-Abuse-To: spam@quarantine6.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/icwScHilA4vwD065U2l5HinRAnU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 17:39:15 -0000

=20
> On May 2, 2018, at 3:46 PM, Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:
>=20
> As I see it, adding PNE adds complexity, and presents risks for the protoc=
ol.

Personally I feel that PNE removes complexity. You don't need the synchroniz=
ed offset on migration required in the current spec. You can support multipa=
th without the added complexity of per path sequence numbers and per path ac=
ks. You could potentially do away with the numbering of connection ID. All t=
hat is significant.

-- Christian Huitema=


From nobody Wed May  2 10:56:12 2018
Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D1CA512D962 for <quic@ietfa.amsl.com>; Wed,  2 May 2018 10:56:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Jdy5Su7bm1g0 for <quic@ietfa.amsl.com>; Wed,  2 May 2018 10:56:09 -0700 (PDT)
Received: from mail-it0-x242.google.com (mail-it0-x242.google.com [IPv6:2607:f8b0:4001:c0b::242]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DFAE712D960 for <quic@ietf.org>; Wed,  2 May 2018 10:56:08 -0700 (PDT)
Received: by mail-it0-x242.google.com with SMTP id i136-v6so9634187ita.2 for <quic@ietf.org>; Wed, 02 May 2018 10:56:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=KnLNFq14SbbvxP0EjVOhkw1I3eqkyUHVltc0uDo5WZw=; b=ELIK5PACQ34W5c1lVHa8DS890HwgxI1Cmy4w5XOmJwehH022rifbxUZwZg0hbK9c0n /hVNPgqYLP6vYGhbOq9yyy8BaxZufaik4ZYRzyhawFiTP3/0kNt0nudrjt2+UIyI7pf7 R4DppN19Bxx/8xAtTfmwkyAm3KXL66uFw5UHTO8jA+tJDzPxFAca9Xajnn9x6fjWo15W MbCF6D+T/5OG4H/BPJnNe0/WUvmXyl5gCKS1p65mP81h8jM4zU2B44bozTx/CzVUp47n B3pIt+nCK92D6Ybim1EUCE+gqLVI0Dg2zCfAbuQ4zSXtOtW/ySIbCzD6ZyEjhgpebywR vNmw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=KnLNFq14SbbvxP0EjVOhkw1I3eqkyUHVltc0uDo5WZw=; b=JTvk+qBEznMExOFeRoPfEcpKWacRX0OwYOLawlIQPYtVzk+cPsbBTJihzW1bKRJd7n nnzCBNhKJqTiD+W3Vk6HSgtNkz9w6XY9oqbbTEdw4SPa1g2KIlaTKlKrXYima/sRbK7I kk5QEE7gq6M/gT0YZ17ofB4ffdlNvLcKT+onMfF4gdaAzyOcBCefwK199Cp2AbKoDAPM 5colHbXnsH9jjUwvYowYHt/oOJolJMMr7s9uVB4XVnghDO1+bGqXkBGdKmMfpTWVe+qZ TsdXGxEMGuNq+HWPw8tfkMNvJBORAhQa0AA0t4Sjv1fQL7LuV+bRwRLo3VAn7Q801wQX 5xsg==
X-Gm-Message-State: ALQs6tCO44RriHKY3e1BoS8cY4APkcFvxR29rMDgnICVuoB/Db8uDGpJ XkBgOXV2nbzk6ZfKr03QsIbsMcQTGdXJv8WbRDo=
X-Google-Smtp-Source: AB8JxZq0NYTv1clVoOrbVpWWu1093q+A9zVton+6CN2sZS24JyGzyJ5C078fgmWXh8R6Icudx+WiBEo5dp7/HZ+j87g=
X-Received: by 2002:a24:72c5:: with SMTP id x188-v6mr22352614itc.118.1525283767898;  Wed, 02 May 2018 10:56:07 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 2 May 2018 13:56:07 -0400
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <94292722-D812-4196-BC41-C3B2B7D277A1@huitema.net>
References: <01AE46C6-682C-4A21-84CD-1D8DAD6F49D9@fb.com> <CACpbDcdnmHrWMCShYd1pEDBervRKfO1pMUM8hb4tkK9nqH1Mdw@mail.gmail.com> <MWHPR21MB06386100B48E17A059B5A04EB6800@MWHPR21MB0638.namprd21.prod.outlook.com> <20180502121018.GF5742@akamai.com> <4C049C27-FAB7-4CF4-8ABE-DABDE8CD0F8B@tik.ee.ethz.ch> <6E58094ECC8D8344914996DAD28F1CCD87F34A@DGGEMM506-MBS.china.huawei.com> <5AE9C122.7060408@erg.abdn.ac.uk> <94292722-D812-4196-BC41-C3B2B7D277A1@huitema.net>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Wed, 2 May 2018 13:56:06 -0400
Message-ID: <CAN1APdf4QaX1rt--w5pcgmjquWvWgdqpNcmYg+9Y1RE0penQbQ@mail.gmail.com>
Subject: Re: Getting to consensus on packet number encryption
To: gorry@erg.abdn.ac.uk, Christian Huitema <huitema@huitema.net>
Cc: "Roni Even (A)" <roni.even@huawei.com>, Praveen Balasubramanian <pravb@microsoft.com>,  IETF QUIC WG <quic@ietf.org>, =?UTF-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>,  Benjamin Kaduk <bkaduk=40akamai.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002ad5d6056b3ccd59"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/lQ8UlM4d_DRXrlkoGMEo0MY9yXI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 17:56:11 -0000

--0000000000002ad5d6056b3ccd59
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On 2 May 2018 at 19.39.23, Christian Huitema (huitema@huitema.net) wrote:

 You can support multipath without the added complexity of per path
sequence numbers and per path acks.

How would you do proper congestion control over multiple paths without
dedicating PN=E2=80=99s to a specific path?

--0000000000002ad5d6056b3ccd59
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">On 2 May 2018 at 19.=
39.23, Christian Huitema (<a href=3D"mailto:huitema@huitema.net">huitema@hu=
itema.net</a>) wrote:</div> <div><blockquote type=3D"cite" class=3D"clean_b=
q" style=3D"font-family:Helvetica,Arial;font-size:13px;font-style:normal;fo=
nt-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:=
start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0=
px;text-decoration:none"><span><div><span style=3D"color:rgb(0,0,0);font-fa=
mily:&quot;helvetica Neue&quot;,helvetica;font-size:14px;font-style:normal;=
font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-alig=
n:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing=
:0px;background-color:rgb(255,255,255);text-decoration:none;float:none;disp=
lay:inline!important"><span class=3D"Apple-converted-space">=C2=A0</span>Yo=
u can support multipath without the added complexity of per path sequence n=
umbers and per path acks.<span class=3D"Apple-converted-space">=C2=A0</span=
></span></div></span></blockquote></div><p>How would you do proper congesti=
on control over multiple paths without dedicating PN=E2=80=99s to a specifi=
c path?</p><p><br></p><div></div></body></html>

--0000000000002ad5d6056b3ccd59--


From nobody Wed May  2 12:15:57 2018
Return-Path: <huitema@huitema.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05EFB12DA11 for <quic@ietfa.amsl.com>; Wed,  2 May 2018 12:15:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
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 FtXdO5kf4V-L for <quic@ietfa.amsl.com>; Wed,  2 May 2018 12:15:54 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 59575124D68 for <quic@ietf.org>; Wed,  2 May 2018 12:15:54 -0700 (PDT)
Received: from xsmtp02.mail2web.com ([168.144.250.215]) by mx35.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1fDxEC-0003Pr-TQ for quic@ietf.org; Wed, 02 May 2018 21:15:49 +0200
Received: from [10.5.2.16] (helo=xmail06.myhosting.com) by xsmtp02.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1fDxBY-0003DI-2X for quic@ietf.org; Wed, 02 May 2018 15:13:36 -0400
Received: (qmail 1555 invoked from network); 2 May 2018 19:12:42 -0000
Received: from unknown (HELO [192.168.1.14]) (Authenticated-user:_huitema@huitema.net@[90.105.145.87]) (envelope-sender <huitema@huitema.net>) by xmail06.myhosting.com (qmail-ldap-1.03) with ESMTPA for <pravb@microsoft.com>; 2 May 2018 19:12:42 -0000
Content-Type: multipart/alternative; boundary=Apple-Mail-3D52F39A-7688-435A-A6F7-650FA2B3F71E
Mime-Version: 1.0 (1.0)
From: Christian Huitema <huitema@huitema.net>
X-Mailer: iPhone Mail (15E216)
In-Reply-To: <CAN1APdf4QaX1rt--w5pcgmjquWvWgdqpNcmYg+9Y1RE0penQbQ@mail.gmail.com>
Date: Wed, 2 May 2018 21:12:41 +0200
Cc: gorry@erg.abdn.ac.uk, "Roni Even (A)" <roni.even@huawei.com>, Praveen Balasubramanian <pravb@microsoft.com>, IETF QUIC WG <quic@ietf.org>, =?utf-8?Q?Mirja_K=C3=BChlewind?= <mirja.kuehlewind@tik.ee.ethz.ch>, Benjamin Kaduk <bkaduk=40akamai.com@dmarc.ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <B628D63F-87D4-47D6-9AB4-4DD2E3A655DC@huitema.net>
References: <01AE46C6-682C-4A21-84CD-1D8DAD6F49D9@fb.com> <CACpbDcdnmHrWMCShYd1pEDBervRKfO1pMUM8hb4tkK9nqH1Mdw@mail.gmail.com> <MWHPR21MB06386100B48E17A059B5A04EB6800@MWHPR21MB0638.namprd21.prod.outlook.com> <20180502121018.GF5742@akamai.com> <4C049C27-FAB7-4CF4-8ABE-DABDE8CD0F8B@tik.ee.ethz.ch> <6E58094ECC8D8344914996DAD28F1CCD87F34A@DGGEMM506-MBS.china.huawei.com> <5AE9C122.7060408@erg.abdn.ac.uk> <94292722-D812-4196-BC41-C3B2B7D277A1@huitema.net> <CAN1APdf4QaX1rt--w5pcgmjquWvWgdqpNcmYg+9Y1RE0penQbQ@mail.gmail.com>
To: =?utf-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
Subject: Re: Getting to consensus on packet number encryption
X-Originating-IP: 168.144.250.215
X-AntiSpamCloud-Domain: xsmtpout.mail2web.com
X-AntiSpamCloud-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-AntiSpamCloud-Outgoing-Class: ham
X-AntiSpamCloud-Outgoing-Evidence: Combined (0.04)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5pul4apcklhoKfREeza3G+N602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO37pNwwF1lRXh5rzvPzo9Jts1ujulqUFmMITHM77eiVilPPX3065+Hfl1xnY2jydXM7i TvJ2/ZGzVWB9scFAaCdIFaUvXN+CI+RGy3Me16pB6nkU4uouGtaIPSwAALHVjh/TBCf6oYXAWGet lavcAjAiREicRPMV5adYQyNOvKmgizQS7ZJXB6rwDFOa1j0OJR6ijzwzq5HGxV3pRhOdYuobeA2G NaAif0QyGEAJd8kel+zffa+S3paXsykGResyE7dAzbZabvf4+eAvvSn0D5YzxzA4C4+ILjmdkQoL 6F7cCSavQBrPoagEXfZ210Cx8bwqyT5p50x81ZKcmzCu2U1l0pLLr6Q2GfeLeJGF+80D4WY7xWSn pVjQVprFFOt2hDWKtLT9WR57oxUvRixjadcobnduoQv5Sp6y3SmK1n5SMPepZn00xVXQbuUt1pns FwEiRQv+PVjjwa+Z5RFCOMSVX0hY9vhgpjWAGHpOTk2gddP2MpKItZvZ+C7587l4X9hV01g/Lh1a bsOJn7yAj8RgiNplmw3yp4FFFCuS+k6jh5d4Swn5E67RV+LaU4GmVjH8gYlRWMzXMtJksqe+xLeX oHkzkRzbKyRDRP8j7fY6qf56vTMbt2qnAITT5tZcB2h+wlfAS2SbL4bvnSO/22U+luhwxr3rIDor bGUBzA1tfXjZjIcL0ghb0hwwkn+c25Rins15oKFWvUk5C9olBXDaeMvijik4Wj80Y0qVd4i4w6nI oDr0sXUZ7YZoZ/GZ+hM5SBB0A3IybZLQFGPC5D1z5NQBt6vrTjaii/MA7FoCAhy1/eljfSN5aXns qLZLef9qwM7RXpJS8RjTdyh2j5AWyDZ7BRCxIW6XiPgk5wgNeRXbC69qDBnTAPdQSCnD1TRj9D8H LKHAKpPGP8EPnuDHTXhIrVzYteKGVryF5qVZ
X-Report-Abuse-To: spam@quarantine6.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/CtufHc1TKHGuMRhLyxktSgmCgEs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 02 May 2018 19:15:56 -0000

--Apple-Mail-3D52F39A-7688-435A-A6F7-650FA2B3F71E
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

=20

> On May 2, 2018, at 7:56 PM, Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@gm=
ail.com> wrote:
>=20
>> On 2 May 2018 at 19.39.23, Christian Huitema (huitema@huitema.net) wrote:=

>>  You can support multipath without the added complexity of per path seque=
nce numbers and per path acks.=20
>=20
> How would you do proper congestion control over multiple paths without ded=
icating PN=E2=80=99s to a specific path?
>=20
Very simple. You know on which path a packet was sent. You can thus give con=
gestion credits on that path when the packet is acknowledged, or congestion s=
ignals if the packet is lost.=20

-- Christian Huitema=20=

--Apple-Mail-3D52F39A-7688-435A-A6F7-650FA2B3F71E
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto">&nbsp;<br><div><br>On May 2, 2018, at 7:56 P=
M, Mikkel Fahn=C3=B8e J=C3=B8rgensen &lt;<a href=3D"mailto:mikkelfj@gmail.co=
m">mikkelfj@gmail.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cite">=
<div><style>body{font-family:Helvetica,Arial;font-size:13px}</style><div id=3D=
"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;color=
:rgba(0,0,0,1.0);margin:0px;line-height:auto">On 2 May 2018 at 19.39.23, Chr=
istian Huitema (<a href=3D"mailto:huitema@huitema.net">huitema@huitema.net</=
a>) wrote:</div> <div><blockquote type=3D"cite" class=3D"clean_bq" style=3D"=
font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-ca=
ps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-ind=
ent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decorat=
ion:none"><span><div><span style=3D"color:rgb(0,0,0);font-family:&quot;helve=
tica Neue&quot;,helvetica;font-size:14px;font-style:normal;font-variant-caps=
:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-inden=
t:0px;text-transform:none;white-space:normal;word-spacing:0px;background-col=
or:rgb(255,255,255);text-decoration:none;float:none;display:inline!important=
"><span class=3D"Apple-converted-space">&nbsp;</span>You can support multipa=
th without the added complexity of per path sequence numbers and per path ac=
ks.<span class=3D"Apple-converted-space">&nbsp;</span></span></div></span></=
blockquote></div><p>How would you do proper congestion control over multiple=
 paths without dedicating PN=E2=80=99s to a specific path?</p><div></div>
</div></blockquote>Very simple. You know on which path a packet was sent. Yo=
u can thus give congestion credits on that path when the packet is acknowled=
ged, or congestion signals if the packet is lost.&nbsp;<div><br></div><div>-=
- Christian Huitema&nbsp;</div></body></html>=

--Apple-Mail-3D52F39A-7688-435A-A6F7-650FA2B3F71E--


From nobody Thu May  3 22:27:10 2018
Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1541D1273E2 for <quic@ietfa.amsl.com>; Thu,  3 May 2018 22:27:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Dcov7wfqsmUg for <quic@ietfa.amsl.com>; Thu,  3 May 2018 22:27:06 -0700 (PDT)
Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 37910127342 for <quic@ietf.org>; Thu,  3 May 2018 22:27:06 -0700 (PDT)
Received: by mail-io0-x22e.google.com with SMTP id e78-v6so24355195iod.0 for <quic@ietf.org>; Thu, 03 May 2018 22:27:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:mime-version:date:message-id:subject:to; bh=E5/9W3brD74JSFGXe0VOm1Vb3TrigvYn5jhEzlk43x4=; b=S9aHL9gVkijVlWbEr6DBbaFipJjElAl4FZnv1QVMWo8Bk1EF8jyWD9de4J8yki+ZYX tL4Dlkj4tb5QYXZ07FwNzSJ8kqwwJgA5pr9Knc1MxtRoJFeav6fGfnkfwoNyLczUS6H5 EQ4qVypSsMgEmD7iA+ScwuOcxkUwiwIlfCbqsrOE56bpHGrW/e1lOh+0Quy/uCy2CTj6 PMDcujC71UT5FUfTTareu9ywztoNKPg2QvmaUdi+gDWo9L9Pby1Vsk8cWXiYExtC30AU KALtYA6bZIj+PrVPD7ETd/Ukw/TxYtmyYZG6+e6pdkoMcHSTvGyM/r9hJKQmSuL7Fs6p R6VQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:date:message-id:subject:to; bh=E5/9W3brD74JSFGXe0VOm1Vb3TrigvYn5jhEzlk43x4=; b=Rz0T3aoOa/l4Sm66j94TIWtBoEHt8WaEc3ZVSch037rAIGD8lU8NC6x9rXbU4fZhTP ZfdoqDrNigOQzz0T6v2pTqZIzkdfmE6RrypuFwTQEVq/sCXULp1jgP2gvYpJWMHVqAlA BYRhqERWXT3vLaudyDyCNf2JzajB5VcKEdVok2YLrA85suhMZtvRQ2EmZrroaYM0zPtq mOScrErBRqLW0l0acmo6V8mvkrtR0seURCoHvnlr3/iGfwiDZYZtcwOGOPX31pPC0Pop E8fKqlZX6KXzcynkU8nYV1+U8dHMJ4CJp4FDZceGXPgzpOvtBt4u+DEzV/3lXCgJOa/L vhUg==
X-Gm-Message-State: ALQs6tCVsEBfYC+CdgSVMpF3GZxOfYUxrpShru+BnMy+oktZyHB6xVCc anQ62qD8WwjqCl4lD0kSD3b00MZwu8KRyTRJUGlGfQ==
X-Google-Smtp-Source: AB8JxZrQJOXImvK/yCII0LWJuJgCamce0NFfiSnaM9KDUaLIi+3ICfGJT+HdFqVfTSl03vj19Pb72JAKhvPQR9IdU1U=
X-Received: by 2002:a6b:b60a:: with SMTP id g10-v6mr27130479iof.209.1525411625277;  Thu, 03 May 2018 22:27:05 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Fri, 4 May 2018 01:27:04 -0400
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Fri, 4 May 2018 01:27:04 -0400
Message-ID: <CAN1APdfbFrHvc2Q8qGDbZBR44ouL0v+Loadtnay-jjqVvSmoZg@mail.gmail.com>
Subject: unique tuples
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000f9de2056b5a92c6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/mjKGfF6DnluAKqeyhBBpH9MgHBU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 May 2018 05:27:08 -0000

--0000000000000f9de2056b5a92c6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

There has been a lot of back and forth on unique tuples in QUIC, and I am
not quite sure where it all landed.

It is my understanding that at some meeting it was decided to require
unique tuples in V1, if only in certain contexts like handshake for the
sake of simplicity. At the same time, having introduced dual CID=E2=80=99s =
the need
for unique tuples is greatly reduced along with random initial CID=E2=80=99=
s that
are reflected in version negotiation and stateless retry.

Reading through the spec, I can=E2=80=99t find any obvious places where uni=
que
tuples are still required unless a peer volunteer to have a 0-length CID.

This does matter a lot, because there is a world of difference between
managing a single socket and many concurrent sockets in how you talk to the
OS. QUIC makes it possible to move all the 10K multiplexing problem into
QUIC and out of the OS interface, except for this one detail. Even if it is
only for, say, handshake, it still places a constraint that must be handled=
.

It of course also matters wrt. ephemeral port exhaustion although the
argument here is that if you limit it to the duration of handshakes you
should be good. But especially in server p2p with many concurrent
connections between same hosts, this adds complexity.

So bottom line, do we still have constraints in this area, and are they
really worth keeping? And if so, could this be made more obvious in the
spec? And if not, could it be made explicit that unique tuples are only
required if the CID is 0 - it already almost says so for connection
identification, but this does not exclude certain packet types from having
such a constraint.


Kind Regards,
Mikkel Fahn=C3=B8e J=C3=B8rgensen

--0000000000000f9de2056b5a92c6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">There has been a lot=
 of back and forth on unique tuples in QUIC, and I am not quite sure where =
it all landed.</div><div id=3D"bloop_customfont" style=3D"font-family:Helve=
tica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto=
"><br></div><div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Ari=
al;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">It is =
my understanding that at some meeting it was decided to require unique tupl=
es in V1, if only in certain contexts like handshake for the sake of simpli=
city. At the same time, having introduced dual CID=E2=80=99s the need for u=
nique tuples is greatly reduced along with random initial CID=E2=80=99s tha=
t are reflected in version negotiation and stateless retry.</div><div id=3D=
"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;colo=
r:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div id=3D"bloop_c=
ustomfont" style=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0=
,0,0,1.0);margin:0px;line-height:auto">Reading through the spec, I can=E2=
=80=99t find any obvious places where unique tuples are still required unle=
ss a peer volunteer to have a 0-length CID.</div><div id=3D"bloop_customfon=
t" style=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0=
);margin:0px;line-height:auto"><br></div><div id=3D"bloop_customfont" style=
=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin=
:0px;line-height:auto">This does matter a lot, because there is a world of =
difference between managing a single socket and many concurrent sockets in =
how you talk to the OS. QUIC makes it possible to move all the 10K multiple=
xing problem into QUIC and out of the OS interface, except for this one det=
ail. Even if it is only for, say, handshake, it still places a constraint t=
hat must be handled.</div><div id=3D"bloop_customfont" style=3D"font-family=
:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-heigh=
t:auto"><br></div><div id=3D"bloop_customfont" style=3D"font-family:Helveti=
ca,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">=
It of course also matters wrt. ephemeral port exhaustion although the argum=
ent here is that if you limit it to the duration of handshakes you should b=
e good. But especially in server p2p with many concurrent connections betwe=
en same hosts, this adds complexity.</div><div id=3D"bloop_customfont" styl=
e=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margi=
n:0px;line-height:auto"><br></div><div id=3D"bloop_customfont" style=3D"fon=
t-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;li=
ne-height:auto">So bottom line, do we still have constraints in this area, =
and are they really worth keeping? And if so, could this be made more obvio=
us in the spec? And if not, could it be made explicit that unique tuples ar=
e only required if the CID is 0 - it already almost says so for connection =
identification, but this does not exclude certain packet types from having =
such a constraint.</div><div id=3D"bloop_customfont" style=3D"font-family:H=
elvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:=
auto"><br></div><br><div id=3D"bloop_sign_1525410743219941120" class=3D"blo=
op_sign"><div style=3D"font-family:helvetica,arial;font-size:13px">Kind Reg=
ards,</div><div style=3D"font-family:helvetica,arial;font-size:13px">Mikkel=
 Fahn=C3=B8e J=C3=B8rgensen<br><br></div></div></body></html>

--0000000000000f9de2056b5a92c6--


From nobody Fri May  4 00:01:16 2018
Return-Path: <martin.thomson@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0AFA0126E01 for <quic@ietfa.amsl.com>; Fri,  4 May 2018 00:01:15 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 HgNvdK34f5qF for <quic@ietfa.amsl.com>; Fri,  4 May 2018 00:01:13 -0700 (PDT)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7C469124205 for <quic@ietf.org>; Fri,  4 May 2018 00:01:13 -0700 (PDT)
Received: by mail-oi0-x233.google.com with SMTP id k5-v6so11481681oiw.0 for <quic@ietf.org>; Fri, 04 May 2018 00:01:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=bzCgrTaXj3GuQdNkLz6lHHxF/R3Mgz/7U44dlREQCQM=; b=EdrQ8YJ8PBbDhIa4jNcT/BgWwMcUPh6mlF34K7bgjlEGQCLBzHAyiWAtIe04nh3tAl LILw5d6/xa3m5s30e9qVDjRG7SbWkJmBpsKz0REyoBrKqIRhRDj0OFr0ngxkYF3FA0w0 x8RojDwQdZ9TgtmzS0FppgzxD54n24RW+NibtleQDob22i3IX4Fd/L8+dFTdeUzC8Rbk 3+me7vMQlJ2zqJ2riKuVWZ+d/0X+ToJ3SGpgfmCPFFIkspPYGTS12lFloP2TsRJAd29i VsASOZA2zTIZlSDFJAzO5fItI6W0YzFjXg9BJS0cTptYYs6or3/dW6mnhnwv9IWziybf YYIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=bzCgrTaXj3GuQdNkLz6lHHxF/R3Mgz/7U44dlREQCQM=; b=dRN0ctHRBaX+n+n8Ymhmb3jSZJ6rzbnN1ppXfv74JKI3wbnKm0wyGqW0XRbxtLNNc0 VhtA5CSIWXxc5RiuMLappdRopSTyVpZPi2LO+OJSIcLPA6OcxktI+X7/dkXk64QZOqa1 g8duElI2OpSnkj1IMw/gO1ON2j3IPiz1JmMoqUMf8D43tb2mw71qVQNv4lMtWIiPZjpE M7ed+BoE1712ylBlmFWh4uJRHcFtxVU92gaU/HgjepHryQXv10K33ni50/zt6jxlwOZG JdNMZcHRKK+rrWBJRAuu+2fL3ynUN+VAsCpwCqsxv5nUENVmcRFiZlITtprcAZtIoRt2 UBNQ==
X-Gm-Message-State: ALQs6tAivBKTQprupiECUNFZEJD7cFvU3O/N5CDHUQlR3WENEuJiCNmY M3PPp3MVqKmBTS1Mt/kpP+K/CJ/bP1ZlKKPFfeY=
X-Google-Smtp-Source: AB8JxZo90YDWrMXUi3fSP8Y1d9wXAelmHwsGYKFFhAha55YGhrVxAu3o5wMOuGau0cV3hCGz+z9dOEZkIM3NLIZA/wU=
X-Received: by 2002:aca:ebd4:: with SMTP id j203-v6mr17618401oih.110.1525417272706;  Fri, 04 May 2018 00:01:12 -0700 (PDT)
MIME-Version: 1.0
References: <CAN1APdfbFrHvc2Q8qGDbZBR44ouL0v+Loadtnay-jjqVvSmoZg@mail.gmail.com>
In-Reply-To: <CAN1APdfbFrHvc2Q8qGDbZBR44ouL0v+Loadtnay-jjqVvSmoZg@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 04 May 2018 07:01:01 +0000
Message-ID: <CABkgnnWG_qSOLak23_zyxff6QSV2rGWSLTf+Bw94JVF0v-L1zg@mail.gmail.com>
Subject: Re: unique tuples
To: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
Cc: QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/uWLhihk5WVtTl5cSQlGibLFLkuU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 May 2018 07:01:15 -0000

Yes, with the change to connection IDs, it should be possible to have
multiple connections running concurrently on the same address tuple.  This
is true at any stage of the connection, including the handshake.

Of course, you have to use a connection ID if this is what you want to do.
On Fri, May 4, 2018 at 3:27 PM Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@=
gmail.com>
wrote:

> There has been a lot of back and forth on unique tuples in QUIC, and I am
not quite sure where it all landed.

> It is my understanding that at some meeting it was decided to require
unique tuples in V1, if only in certain contexts like handshake for the
sake of simplicity. At the same time, having introduced dual CID=E2=80=99s =
the need
for unique tuples is greatly reduced along with random initial CID=E2=80=99=
s that
are reflected in version negotiation and stateless retry.

> Reading through the spec, I can=E2=80=99t find any obvious places where u=
nique
tuples are still required unless a peer volunteer to have a 0-length CID.

> This does matter a lot, because there is a world of difference between
managing a single socket and many concurrent sockets in how you talk to the
OS. QUIC makes it possible to move all the 10K multiplexing problem into
QUIC and out of the OS interface, except for this one detail. Even if it is
only for, say, handshake, it still places a constraint that must be handled=
.

> It of course also matters wrt. ephemeral port exhaustion although the
argument here is that if you limit it to the duration of handshakes you
should be good. But especially in server p2p with many concurrent
connections between same hosts, this adds complexity.

> So bottom line, do we still have constraints in this area, and are they
really worth keeping? And if so, could this be made more obvious in the
spec? And if not, could it be made explicit that unique tuples are only
required if the CID is 0 - it already almost says so for connection
identification, but this does not exclude certain packet types from having
such a constraint.


> Kind Regards,
> Mikkel Fahn=C3=B8e J=C3=B8rgensen


From nobody Fri May  4 03:26:17 2018
Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B1651241F8 for <quic@ietfa.amsl.com>; Fri,  4 May 2018 03:26:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.698
X-Spam-Level: 
X-Spam-Status: No, score=-1.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 eM0-HY2m0S2K for <quic@ietfa.amsl.com>; Fri,  4 May 2018 03:26:14 -0700 (PDT)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2EB5E120726 for <quic@ietf.org>; Fri,  4 May 2018 03:26:14 -0700 (PDT)
Received: by mail-io0-x233.google.com with SMTP id r9-v6so25054898iod.6 for <quic@ietf.org>; Fri, 04 May 2018 03:26:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=wiX3+34ecZScuEPzaYersV3qp/nEx/kc6dQ4jpnCnBY=; b=b8XbYg0nSo1tD1VWcxNpYufh7eTci/4UqRIIzbRC3/Le+Km57rf7PobTsK4R2z1YH9 jS8mFkGCG2k9xHG7ugTJKz5xPbLs0VHODIXx7837U7hPqqPzjDef1ZdiVNftx2OPqvBe gBnHd5EDfkGjDyPanLMu0bFTmmh8+brwN3NMo88IRp7djcqrKh6902ELZr26RqBke1f2 7P+UsKRtDfu4p6Ie5PmUez5thxpclyy5bDosF6fz5Y7J3eZquOWoGMcXFq+Ut5UqKiZ8 ZU7b21Z+Kb0Adck+RrUundKaSty/KfhtIsWn4pNbhsNkgTiBsKFpesanV7wHYl+G664c zeQg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=wiX3+34ecZScuEPzaYersV3qp/nEx/kc6dQ4jpnCnBY=; b=Ii0OHjVUYL4pMo3dRjqsRueRY1qkvR6GhqeVEIodcZ1ei5xM8vVvABt6KxTxVOxhSy YnkFFPslSRMr0xuHb2qPe6SPrazpNis9EXieJg+rBKJzE354znMgr6OyrJlTMizCOEB+ cwMIjVMBEL+coJ1v7cKcsEnvBl279/Nmf0CbVMnIWBo3sXmW3VME2aL94mZ3SuFa4C0T c//0L5wcm8UzS8qm/mU63vbAScPDXnoAFeZ7UvOogsJ5eM7HdUpU2w3/tOKkTIcfdmME IwpQZV+ncqwOZMsyE7G56PjqKvxzvz4FfG7lakepCNYNhn/GyF/QaJpQVf/xtckagkFp nw8Q==
X-Gm-Message-State: ALQs6tCh5CuGJybomvOMuGrB9oiVpMmTdXKGdHM5YaR5NU3hLk4umAsR EYA+29WArOvOksRcjFNp/wb7rIeUQs4FpA88ESE=
X-Google-Smtp-Source: AB8JxZr9HqLEVXD0PwAC5fd4SVXFCUmCAebOYMbRHlH54xkocdsBNkvTAZK+E/GVtzNstQb0NtZSGumsmoBen/otpyI=
X-Received: by 2002:a6b:5010:: with SMTP id e16-v6mr28132625iob.274.1525429573568;  Fri, 04 May 2018 03:26:13 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Fri, 4 May 2018 03:26:12 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <CABkgnnWG_qSOLak23_zyxff6QSV2rGWSLTf+Bw94JVF0v-L1zg@mail.gmail.com>
References: <CAN1APdfbFrHvc2Q8qGDbZBR44ouL0v+Loadtnay-jjqVvSmoZg@mail.gmail.com> <CABkgnnWG_qSOLak23_zyxff6QSV2rGWSLTf+Bw94JVF0v-L1zg@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Fri, 4 May 2018 03:26:12 -0700
Message-ID: <CAN1APddL7UNWqF8JrEz+HeFMqJOU2xQ2zO7_GJE1V9i=j_XyHQ@mail.gmail.com>
Subject: Re: unique tuples
To: Martin Thomson <martin.thomson@gmail.com>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000dcd030056b5ebfd6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/RRRgHVV_lWohH9xyKWJexjCPNaQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 May 2018 10:26:16 -0000

--000000000000dcd030056b5ebfd6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks, this is helpful.


On 4 May 2018 at 09.01.13, Martin Thomson (martin.thomson@gmail.com) wrote:

Yes, with the change to connection IDs, it should be possible to have
multiple connections running concurrently on the same address tuple. This
is true at any stage of the connection, including the handshake.

Of course, you have to use a connection ID if this is what you want to do.
On Fri, May 4, 2018 at 3:27 PM Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@=
gmail.com>
wrote:

> There has been a lot of back and forth on unique tuples in QUIC, and I am
not quite sure where it all landed.

> It is my understanding that at some meeting it was decided to require
unique tuples in V1, if only in certain contexts like handshake for the
sake of simplicity. At the same time, having introduced dual CID=E2=80=99s =
the need
for unique tuples is greatly reduced along with random initial CID=E2=80=99=
s that
are reflected in version negotiation and stateless retry.

> Reading through the spec, I can=E2=80=99t find any obvious places where u=
nique
tuples are still required unless a peer volunteer to have a 0-length CID.

> This does matter a lot, because there is a world of difference between
managing a single socket and many concurrent sockets in how you talk to the
OS. QUIC makes it possible to move all the 10K multiplexing problem into
QUIC and out of the OS interface, except for this one detail. Even if it is
only for, say, handshake, it still places a constraint that must be
handled.

> It of course also matters wrt. ephemeral port exhaustion although the
argument here is that if you limit it to the duration of handshakes you
should be good. But especially in server p2p with many concurrent
connections between same hosts, this adds complexity.

> So bottom line, do we still have constraints in this area, and are they
really worth keeping? And if so, could this be made more obvious in the
spec? And if not, could it be made explicit that unique tuples are only
required if the CID is 0 - it already almost says so for connection
identification, but this does not exclude certain packet types from having
such a constraint.


> Kind Regards,
> Mikkel Fahn=C3=B8e J=C3=B8rgensen

--000000000000dcd030056b5ebfd6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Thanks, this is help=
ful.</div> <div id=3D"bloop_sign_1525429541122295808" class=3D"bloop_sign">=
<div style=3D"font-family:helvetica,arial;font-size:13px"><br></div></div> =
<br><p class=3D"airmail_on">On 4 May 2018 at 09.01.13, Martin Thomson (<a h=
ref=3D"mailto:martin.thomson@gmail.com">martin.thomson@gmail.com</a>) wrote=
:</p> <blockquote type=3D"cite" class=3D"clean_bq"><span><div><div></div><d=
iv>Yes, with the change to connection IDs, it should be possible to have
<br>multiple connections running concurrently on the same address tuple.  T=
his
<br>is true at any stage of the connection, including the handshake.
<br>
<br>Of course, you have to use a connection ID if this is what you want to =
do.
<br>On Fri, May 4, 2018 at 3:27 PM Mikkel Fahn=C3=B8e J=C3=B8rgensen &lt;<a=
 href=3D"mailto:mikkelfj@gmail.com">mikkelfj@gmail.com</a>&gt;
<br>wrote:
<br>
<br>&gt; There has been a lot of back and forth on unique tuples in QUIC, a=
nd I am
<br>not quite sure where it all landed.
<br>
<br>&gt; It is my understanding that at some meeting it was decided to requ=
ire
<br>unique tuples in V1, if only in certain contexts like handshake for the
<br>sake of simplicity. At the same time, having introduced dual CID=E2=80=
=99s the need
<br>for unique tuples is greatly reduced along with random initial CID=E2=
=80=99s that
<br>are reflected in version negotiation and stateless retry.
<br>
<br>&gt; Reading through the spec, I can=E2=80=99t find any obvious places =
where unique
<br>tuples are still required unless a peer volunteer to have a 0-length CI=
D.
<br>
<br>&gt; This does matter a lot, because there is a world of difference bet=
ween
<br>managing a single socket and many concurrent sockets in how you talk to=
 the
<br>OS. QUIC makes it possible to move all the 10K multiplexing problem int=
o
<br>QUIC and out of the OS interface, except for this one detail. Even if i=
t is
<br>only for, say, handshake, it still places a constraint that must be han=
dled.
<br>
<br>&gt; It of course also matters wrt. ephemeral port exhaustion although =
the
<br>argument here is that if you limit it to the duration of handshakes you
<br>should be good. But especially in server p2p with many concurrent
<br>connections between same hosts, this adds complexity.
<br>
<br>&gt; So bottom line, do we still have constraints in this area, and are=
 they
<br>really worth keeping? And if so, could this be made more obvious in the
<br>spec? And if not, could it be made explicit that unique tuples are only
<br>required if the CID is 0 - it already almost says so for connection
<br>identification, but this does not exclude certain packet types from hav=
ing
<br>such a constraint.
<br>
<br>
<br>&gt; Kind Regards,
<br>&gt; Mikkel Fahn=C3=B8e J=C3=B8rgensen
<br></div></div></span></blockquote></body></html>

--000000000000dcd030056b5ebfd6--


From nobody Fri May  4 06:30:12 2018
Return-Path: <quentin.deconinck@uclouvain.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7EE4D12706D for <quic@ietfa.amsl.com>; Fri,  4 May 2018 06:30:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.3
X-Spam-Level: 
X-Spam-Status: No, score=-4.3 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=uclouvain.be
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 U4sH8BTAlw2e for <quic@ietfa.amsl.com>; Fri,  4 May 2018 06:30:06 -0700 (PDT)
Received: from smtp2.sgsi.ucl.ac.be (smtp.sgsi.ucl.ac.be [130.104.5.67]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CD3A126FB3 for <quic@ietf.org>; Fri,  4 May 2018 06:30:06 -0700 (PDT)
Received: from [130.104.228.12] (1o0-328.dhcp.info.ucl.ac.be [130.104.228.12]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: qdeconinck@smtp2.sgsi.ucl.ac.be) by smtp2.sgsi.ucl.ac.be (Postfix) with ESMTPSA id 236A567F204; Fri,  4 May 2018 15:29:55 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=uclouvain.be; s=selucl; t=1525440595; bh=TMJJgo1cxJG9cD8Jhy8SsSX3CsCjQSKLg/CQt2QRhpM=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=wtmzMFSf/opyHh+86rjQcnGEf32vOtcepTyjMdzVge/Z4ll2iCR6pznm3JpWE1ZQE FVzwZj3ijVV5F1UemKoOKwIdANzkkF3rUZv6XPTnEdD2+KlVYLtD5OfzeZVkWn+7D0 sweBqhezcGkgg4aMjE93QewoZUcIn93ExVv72YBU=
X-Virus-Status: Clean
X-Virus-Scanned: clamav-milter 0.99.3-beta2 at smtp-2.sipr-dc.ucl.ac.be
Subject: Re: Collecting measurements with Multipath QUIC
To: Ian Swett <ianswett@google.com>, Olivier Bonaventure <olivier.bonaventure@uclouvain.be>
Cc: IETF QUIC WG <quic@ietf.org>
References: <5c08873a-6ea3-474c-bc9c-6623b67349dc@uclouvain.be> <CAKcm_gOoYxjFdyK6adEarnzrnSaR78FirT1ECDcG-6-vo05k9Q@mail.gmail.com>
From: Quentin De Coninck <quentin.deconinck@uclouvain.be>
Message-ID: <29d255d4-0b48-c303-b72a-78748be66631@uclouvain.be>
Date: Fri, 4 May 2018 15:29:55 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <CAKcm_gOoYxjFdyK6adEarnzrnSaR78FirT1ECDcG-6-vo05k9Q@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------F23F307E436A4DD2CE313E1C"
Content-Language: en-US
X-Sgsi-Spamcheck: SASL authenticated, 
X-SGSI-Information: 
X-SGSI-MailScanner-ID: 236A567F204.A0011
X-SGSI-MailScanner: Found to be clean
X-SGSI-From: quentin.deconinck@uclouvain.be
X-SGSI-Spam-Status: No
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/AlOaH7n8JsSt2FjxPM7oXFrGbY4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 04 May 2018 13:30:10 -0000

This is a multi-part message in MIME format.
--------------F23F307E436A4DD2CE313E1C
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit

Hello Ian,

Thanks for your comments, my thoughts inline.


Le 29/04/18 à 21:25, Ian Swett a écrit :
> Thanks for the updated doc.  I think it embodies the goals of the QUIC 
> WG much better than the past version.
>
> Some comments below:
>
> In 3.3 "The negotiated value will determine how many bytes will be 
> used to encode the Path ID in frames."
> I think it's easier, and more in keeping with the overall QUIC design 
> to use a varint for Path ID?
Sounds good to me
>
> In 3.5, there is discussion of NEW_CONNECTION_ID in a way that makes 
> me think this document needs an update now that QUIC has adopted 
> asymmetric connection IDs?
I think that it's still desirable to keep a symmetric Path ID between 
hosts (for instance, performance metrics with RTT,...). Now that 
NEW_CONNECTION_ID frames can be sent by each host and that Connection 
IDs are asymmetric, two NEW_CONNECTION_ID should be exchanged before 
starting to use a new path ID. When an host agrees to let the peer use a 
given path ID, it communicates the corresponding NEW_CONNECTION_ID 
frame. A path ID can be used by an host once it is aware of both 
corresponding "source" and "destination" Connection IDs. Like this, both 
hosts can still control the number of paths the connection can use.
>
> In 3.6 "The presence of the Path ID in the public header ensures that 
> the packets sent over a given path will contain monotonically 
> increasing packet numbers."
>
> There is no explicit Path ID in this draft, so I suspect this should 
> be reworded to talk about the implicit path ID associated with the 
> connection ID?
Good catch, probably some old text from the previous draft version :-)
>
> In 3.7, I feel like it's cleaner to supply alternate addresses once in 
> transport params, which Mike Bishop's PR#1251 
> <https://github.com/quicwg/base-drafts/pull/1251> does, though with a 
> slightly different use case in mind.  As a corollary, I'm not 
> convinced the REMOVE_ADDRESS frame is really necessary.  If it is, I 
> think I'd rather combine Mike's PR with an UPDATE_TRANPORT_PARAMS 
> frame, which I have a few other use cases for already.
I'm not against using transport parameters (and a corresponding update 
frame) to communicate addresses between peers, but I think it is 
valuable to keep the ability to communicate several addresses. With a 
dual-stacked server, it might be useful for the client to know about 
both addresses, especially is the client has two networks 
connectivities, one IPv4 only and another IPv6 only. The dynamic address 
changes can be needed if we consider the peer-to-peer case with QUIC.
>
> In 3.10, I'd prefer to say each path needs to have it's own congestion 
> controller, rather than just specifying it's own congestion window, 
> since there are other aspects of congestion control besides a CWND.  
> And I'm confused why they MUST be coupled together?  Given the flow 
> control is not path specific, I'm unclear on the benefits of coupling 
> the congestion controllers?  Possibly you can send me some background 
> reading to clarify that?  I read some indication this was for fairness 
> in the RFC, but that seems questionable, given it's possible no 
> portion of the path is shared until you get to the host, in which case 
> it's the host's responsibility to ensure a peer isn't given an unfair 
> share of bandwidth.
Keeping uncoupled congestion controls on paths is fine as long as those 
paths does not share any bottleneck. However, this is not always the 
case, and sometimes hosts are unable to figure it easily. An example a 
client connected to both a WiFi and a cellular network, where the WiFi 
Internet access is actually provided by the (same) cellular network. In 
such case, if the CCs on paths are uncoupled and the cellular base 
station is overloaded (i.e., it is the bottleneck), multipath 
connections will be unfair towards singlepath ones, as they will get 
twice the bandwidth of the bottleneck compared to singlepath. Also, at 
some points, hosts might face network migrations, such that two paths 
initially disjoint can share a common bottleneck. See for instance 
Wischik, Damon, et al. "Design, Implementation and Evaluation of 
Congestion Control for Multipath TCP." (NSDI) or Khalili, Ramin, et al. 
"MPTCP is not pareto-optimal: performance issues and a possible 
solution." (CoNEXT).

For the flow control, it looks like the receive window in TCP, i.e., to 
avoid flooding the peer (while the CWIN is IMHO to avoid flooding the 
network).
>
> 5.2  As I mentioned in reference to 3.3, I'd just use a QUIC varint, 
> which simplifies this quite a bit, and makes the typical cases of a 
> small number of paths very efficient.
Will change this in the next version
>
> 6.1 Given the NEW_CONNECTION_ID frame already has a sequence, it seems 
> simpler to use that than add another PATH ID.
The Path ID was added to the sequence number in order to allow 
Connection ID changes for a given Path ID, but it might be overkill to 
do this. If no one has use cases for this, the sequence number could be 
renamed as the Path ID.
>
> 7.1 MAX_PATHS could also be replaced by an UPDATE_TRANPORT_PARAMS frame.
Agreed
>
> 7.5 It's clear the PATHS frame could be useful to close a path, but 
> I'm not sure what other uses it has?  If it has no other uses, I'd 
> prefer a PATH_CLOSE frame.  If it has other uses, can you clarify it's 
> purpose?
The PATHS frame was initially though as a way to share path information 
between peers, but I'm not sure we need a standard way to do this, and 
the PATHS frame could be skipped. To close paths, we still have the 
PATH_UPDATE, that can both close a path and optionally propose to 
migrate the path over another one.
>
>
>
>
>
>
>
> On Thu, Mar 22, 2018 at 8:05 AM Quentin De Coninck 
> <quentin.deconinck@uclouvain.be 
> <mailto:quentin.deconinck@uclouvain.be>> wrote:
>
>     Hello,
>
>     During today's discussions, we heard several times questions on
>     Multipath QUIC and even more mentions on the benefits of having
>     measurement data before taking decisions. Multipath QUIC will be
>     discussed later this year within the IETF, but in the mean time we
>     have
>     already proposed a first design (recently updated, see
>     https://datatracker.ietf.org/doc/draft-deconinck-quic-multipath/) and
>     even more written an implementation of Multipath QUIC which allows to
>     collect data in a variety of networks. Experience with Multipath TCP
>     shows that the performance of a multipath transport depends on a
>     variety
>     of algorithms such as path management and packet scheduling that
>     interact together.
>
>     During the MPTCP working group this afternoon, I will briefly
>     present an
>     iOS application that includes our Multipath QUIC implementation. It
>     allows collecting different types of measurements. As it runs on
>     iOS, we
>     can also compare Multipath QUIC and Multipath TCP together. If you
>     have
>     an iPhone, I encourage you to install the MultipathTester application
>     below and run it in different networks and notably outside the
>     ietf WiFi.
>
>     https://itunes.apple.com/us/app/multipathtester/id1351286809
>
>     We have already confirmed experimentally the importance of validating
>     addresses in QUIC through a firewall that blocks UDP port 443 in one
>     direction (see
>     https://multipath-quic.org/2018/03/15/firewall-address-validation.html).
>
>     We'll probably find other strange results thanks to your
>     measurements,
>     we will update our findings on https://www.multipath-quic.org
>
>     Best regards,
>
>     Quentin De Coninck
>

-- 

Quentin De Coninck
FNRS Research Fellow - PhD Student
ICTEAM / INGI
Ecole Polytechnique de Louvain
Bâtiment Réaumur (bureau A.010)
Place Sainte Barbe 2, bte L5.02.01
B – 1348 LOUVAIN-LA-NEUVE (Belgium)


--------------F23F307E436A4DD2CE313E1C
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>Hello Ian,</p>
    <p>Thanks for your comments, my thoughts inline. <br>
    </p>
    <br>
    <div class="moz-cite-prefix">Le 29/04/18 à 21:25, Ian Swett a
      écrit :<br>
    </div>
    <blockquote type="cite"
cite="mid:CAKcm_gOoYxjFdyK6adEarnzrnSaR78FirT1ECDcG-6-vo05k9Q@mail.gmail.com">
      <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
      <div dir="ltr">Thanks for the updated doc.  I think it embodies
        the goals of the QUIC WG much better than the past version.<br>
        <div><br>
        </div>
        <div>Some comments below:</div>
        <div><br>
        </div>
        <div>
          <div
style="color:rgb(34,34,34);font-family:sans-serif;font-size:13px;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial">In
            3.3 "<span style="color:rgb(0,0,0);font-size:13.3333px">The
              negotiated value will determine how many bytes </span><span
              style="color:rgb(0,0,0);font-size:13.3333px">will be used
              to encode the Path ID in frames."</span><br>
          </div>
          <pre class="m_3553980802748058612gmail-m_1258175430991841818gmail-newpage" style="font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;word-spacing:0px;text-decoration-style:initial;text-decoration-color:initial;font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color:rgb(0,0,0)">
</pre>
          I think it's easier, and more in keeping with the overall QUIC
          design to use a varint for Path ID?<br>
        </div>
      </div>
    </blockquote>
    Sounds good to me<br>
    <blockquote type="cite"
cite="mid:CAKcm_gOoYxjFdyK6adEarnzrnSaR78FirT1ECDcG-6-vo05k9Q@mail.gmail.com">
      <div dir="ltr">
        <div><br>
        </div>
        <div>In 3.5, there is discussion of NEW_CONNECTION_ID in a way
          that makes me think this document needs an update now that
          QUIC has adopted asymmetric connection IDs?</div>
      </div>
    </blockquote>
    I think that it's still desirable to keep a symmetric Path ID
    between hosts (for instance, performance metrics with RTT,...). Now
    that NEW_CONNECTION_ID frames can be sent by each host and that
    Connection IDs are asymmetric, two NEW_CONNECTION_ID should be
    exchanged before starting to use a new path ID. When an host agrees
    to let the peer use a given path ID, it communicates the
    corresponding NEW_CONNECTION_ID frame. A path ID can be used by an
    host once it is aware of both corresponding "source" and
    "destination" Connection IDs. Like this, both hosts can still
    control the number of paths the connection can use.<br>
    <blockquote type="cite"
cite="mid:CAKcm_gOoYxjFdyK6adEarnzrnSaR78FirT1ECDcG-6-vo05k9Q@mail.gmail.com">
      <div dir="ltr">
        <div><br>
        </div>
        <div>In 3.6 "The presence of the Path ID in the public header
          ensures that the packets sent over a given path will contain
          monotonically increasing packet numbers."</div>
        <div><br>
        </div>
        <div>There is no explicit Path ID in this draft, so I suspect
          this should be reworded to talk about the implicit path ID
          associated with the connection ID?</div>
      </div>
    </blockquote>
    Good catch, probably some old text from the previous draft version
    :-)<br>
    <blockquote type="cite"
cite="mid:CAKcm_gOoYxjFdyK6adEarnzrnSaR78FirT1ECDcG-6-vo05k9Q@mail.gmail.com">
      <div dir="ltr">
        <div><br>
        </div>
        <div>In 3.7, I feel like it's cleaner to supply alternate
          addresses once in transport params, which Mike Bishop's <a
            href="https://github.com/quicwg/base-drafts/pull/1251"
            moz-do-not-send="true">PR#1251</a> does, though with a
          slightly different use case in mind.  As a corollary, I'm not
          convinced the REMOVE_ADDRESS frame is really necessary.  If it
          is, I think I'd rather combine Mike's PR with an
          UPDATE_TRANPORT_PARAMS frame, which I have a few other use
          cases for already.</div>
      </div>
    </blockquote>
    I'm not against using transport parameters (and a corresponding
    update frame) to communicate addresses between peers, but I think it
    is valuable to keep the ability to communicate several addresses.
    With a dual-stacked server, it might be useful for the client to
    know about both addresses, especially is the client has two networks
    connectivities, one IPv4 only and another IPv6 only. The dynamic
    address changes can be needed if we consider the peer-to-peer case
    with QUIC.<br>
    <blockquote type="cite"
cite="mid:CAKcm_gOoYxjFdyK6adEarnzrnSaR78FirT1ECDcG-6-vo05k9Q@mail.gmail.com">
      <div dir="ltr">
        <div><br>
        </div>
        <div>In 3.10, I'd prefer to say each path needs to have it's own
          congestion controller, rather than just specifying it's own
          congestion window, since there are other aspects of congestion
          control besides a CWND.  And I'm confused why they MUST be
          coupled together?  Given the flow control is not path
          specific, I'm unclear on the benefits of coupling the
          congestion controllers?  Possibly you can send me some
          background reading to clarify that?  I read some indication
          this was for fairness in the RFC, but that seems questionable,
          given it's possible no portion of the path is shared until you
          get to the host, in which case it's the host's responsibility
          to ensure a peer isn't given an unfair share of bandwidth.</div>
      </div>
    </blockquote>
    Keeping uncoupled congestion controls on paths is fine as long as
    those paths does not share any bottleneck. However, this is not
    always the case, and sometimes hosts are unable to figure it easily.
    An example a client connected to both a WiFi and a cellular network,
    where the WiFi Internet access is actually provided by the (same)
    cellular network. In such case, if the CCs on paths are uncoupled
    and the cellular base station is overloaded (i.e., it is the
    bottleneck), multipath connections will be unfair towards singlepath
    ones, as they will get twice the bandwidth of the bottleneck
    compared to singlepath. Also, at some points, hosts might face
    network migrations, such that two paths initially disjoint can share
    a common bottleneck. See for instance Wischik, Damon, et al.
    "Design, Implementation and Evaluation of Congestion Control for
    Multipath TCP." (NSDI) or Khalili, Ramin, et al. "MPTCP is not
    pareto-optimal: performance issues and a possible solution."
    (CoNEXT).<br>
    <br>
    For the flow control, it looks like the receive window in TCP, i.e.,
    to avoid flooding the peer (while the CWIN is IMHO to avoid flooding
    the network).<br>
    <blockquote type="cite"
cite="mid:CAKcm_gOoYxjFdyK6adEarnzrnSaR78FirT1ECDcG-6-vo05k9Q@mail.gmail.com">
      <div dir="ltr">
        <div><br>
        </div>
        <div>5.2  As I mentioned in reference to 3.3, I'd just use a
          QUIC varint, which simplifies this quite a bit, and makes the
          typical cases of a small number of paths very efficient.</div>
      </div>
    </blockquote>
    Will change this in the next version<br>
    <blockquote type="cite"
cite="mid:CAKcm_gOoYxjFdyK6adEarnzrnSaR78FirT1ECDcG-6-vo05k9Q@mail.gmail.com">
      <div dir="ltr">
        <div><br>
        </div>
        <div>6.1 Given the NEW_CONNECTION_ID frame already has a
          sequence, it seems simpler to use that than add another PATH
          ID.</div>
      </div>
    </blockquote>
    The Path ID was added to the sequence number in order to allow
    Connection ID changes for a given Path ID, but it might be overkill
    to do this. If no one has use cases for this, the sequence number
    could be renamed as the Path ID.<br>
    <blockquote type="cite"
cite="mid:CAKcm_gOoYxjFdyK6adEarnzrnSaR78FirT1ECDcG-6-vo05k9Q@mail.gmail.com">
      <div dir="ltr">
        <div><br>
        </div>
        <div>7.1 MAX_PATHS could also be replaced by an
          UPDATE_TRANPORT_PARAMS frame.</div>
      </div>
    </blockquote>
    Agreed<br>
    <blockquote type="cite"
cite="mid:CAKcm_gOoYxjFdyK6adEarnzrnSaR78FirT1ECDcG-6-vo05k9Q@mail.gmail.com">
      <div dir="ltr">
        <div><br>
        </div>
        <div>7.5 It's clear the PATHS frame could be useful to close a
          path, but I'm not sure what other uses it has?  If it has no
          other uses, I'd prefer a PATH_CLOSE frame.  If it has other
          uses, can you clarify it's purpose?</div>
      </div>
    </blockquote>
    The PATHS frame was initially though as a way to share path
    information between peers, but I'm not sure we need a standard way
    to do this, and the PATHS frame could be skipped. To close paths, we
    still have the PATH_UPDATE, that can both close a path and
    optionally propose to migrate the path over another one.<br>
    <blockquote type="cite"
cite="mid:CAKcm_gOoYxjFdyK6adEarnzrnSaR78FirT1ECDcG-6-vo05k9Q@mail.gmail.com">
      <div dir="ltr">
        <div><br>
        </div>
        <div><br>
        </div>
        <div><br>
        </div>
        <div><br>
        </div>
        <div><br>
        </div>
        <div><br>
        </div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr">On Thu, Mar 22, 2018 at 8:05 AM Quentin De
          Coninck &lt;<a href="mailto:quentin.deconinck@uclouvain.be"
            target="_blank" moz-do-not-send="true">quentin.deconinck@uclouvain.be</a>&gt;
          wrote:<br>
        </div>
        <blockquote class="gmail_quote" style="margin:0 0 0
          .8ex;border-left:1px #ccc solid;padding-left:1ex">Hello,<br>
          <br>
          During today's discussions, we heard several times questions
          on <br>
          Multipath QUIC and even more mentions on the benefits of
          having <br>
          measurement data before taking decisions. Multipath QUIC will
          be <br>
          discussed later this year within the IETF, but in the mean
          time we have <br>
          already proposed a first design (recently updated, see <br>
          <a
            href="https://datatracker.ietf.org/doc/draft-deconinck-quic-multipath/"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://datatracker.ietf.org/doc/draft-deconinck-quic-multipath/</a>)
          and <br>
          even more written an implementation of Multipath QUIC which
          allows to <br>
          collect data in a variety of networks. Experience with
          Multipath TCP <br>
          shows that the performance of a multipath transport depends on
          a variety <br>
          of algorithms such as path management and packet scheduling
          that <br>
          interact together.<br>
          <br>
          During the MPTCP working group this afternoon, I will briefly
          present an <br>
          iOS application that includes our Multipath QUIC
          implementation. It <br>
          allows collecting different types of measurements. As it runs
          on iOS, we <br>
          can also compare Multipath QUIC and Multipath TCP together. If
          you have <br>
          an iPhone, I encourage you to install the MultipathTester
          application <br>
          below and run it in different networks and notably outside the
          ietf WiFi.<br>
          <br>
          <a
            href="https://itunes.apple.com/us/app/multipathtester/id1351286809"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://itunes.apple.com/us/app/multipathtester/id1351286809</a><br>
          <br>
          We have already confirmed experimentally the importance of
          validating <br>
          addresses in QUIC through a firewall that blocks UDP port 443
          in one <br>
          direction (see <br>
          <a
href="https://multipath-quic.org/2018/03/15/firewall-address-validation.html"
            rel="noreferrer" target="_blank" moz-do-not-send="true">https://multipath-quic.org/2018/03/15/firewall-address-validation.html</a>).
          <br>
          We'll probably find other strange results thanks to your
          measurements, <br>
          we will update our findings on <a
            href="https://www.multipath-quic.org" rel="noreferrer"
            target="_blank" moz-do-not-send="true">https://www.multipath-quic.org</a><br>
          <br>
          Best regards,<br>
          <br>
          Quentin De Coninck<br>
          <br>
        </blockquote>
      </div>
    </blockquote>
    <br>
    <pre class="moz-signature" cols="72">-- 

Quentin De Coninck
FNRS Research Fellow - PhD Student
ICTEAM / INGI
Ecole Polytechnique de Louvain
Bâtiment Réaumur (bureau A.010)
Place Sainte Barbe 2, bte L5.02.01
B – 1348 LOUVAIN-LA-NEUVE (Belgium)</pre>
  </body>
</html>

--------------F23F307E436A4DD2CE313E1C--


From nobody Sun May  6 18:45:28 2018
Return-Path: <mnot@mnot.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 210FA12D886 for <quic@ietfa.amsl.com>; Sun,  6 May 2018 18:45:27 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=IcEZka+r; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=gojPxZ5h
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 G-1GYnX_IC_x for <quic@ietfa.amsl.com>; Sun,  6 May 2018 18:45:24 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8B9BF12D885 for <quic@ietf.org>; Sun,  6 May 2018 18:45:24 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id DB74D2127F; Sun,  6 May 2018 21:45:23 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Sun, 06 May 2018 21:45:23 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=17kLkZ0y85hVGvtuLy4sXxvliUbn8 wTgOsaPOR+rnhA=; b=IcEZka+rrRbSVuREYWkFVawaBXs2eYMnYJmEYk27fHvqy +wAIvodEwXfTuVmgpXPvo68CIgvfjtZYdjnfpQoyHyKp7/R+dYzRdKLvQ7yXCKmT eEyHSoo4BMSGW6QBUsWUUlWLu2XXfkgSzK6wn6diBmxdCdiBnDL7NlGYQ6s0Yzcs eWv1Nw9QkLesQlrTtl6gPae1/tp8G2fOm8azbNUqCPIto1NovnejGcj0HooHdEYf Rv9NsYOiDzseSFhgf/seIlSejgl7ANhhiclHXnExDy+cO52qmRjTb+2ah2nJhmPB L4fB0lGIVSKD0DEPhtZA9mjyoWgzZvzRGX2NZGVtQ==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=17kLkZ 0y85hVGvtuLy4sXxvliUbn8wTgOsaPOR+rnhA=; b=gojPxZ5hrfsrGYuYhpBywr 1cO2gcrzbzVeUCea8gvWtcoNoUItRB5owI0q9Jj+hltpKCGVRPj8UBfGX35ncFrz WgRnyNpDbOYELb/gA7EjsSOI7GXQP7sXAp8fCvTyKAW7VjG6puePLWiqgcqbLjbe guStjChe0q7ooQI22L9iAsUJi6sNUFM6vn+DKaze80bCnHY0rkULoLX7jVFltEOu sCfV6T4elpoDO9QqXB2nxiH3QHzipBDxGRfSJKpYy8iASbfPPHZ8N1zgpFdUKo1W mkoV6Gtm9+RRxZxATJ0mLSH1m0mtH++205cmuNGqWwClMiu8ehiGCX+X34oZSFqw ==
X-ME-Sender: <xms:s6_vWmxktxUWm1xydM-blsyABgBRZMTVG7GJZQaoTSLl5PCFaXvGoA>
Received: from [192.168.1.25] (unknown [144.136.175.28]) by mail.messagingengine.com (Postfix) with ESMTPA id 804AEE4408; Sun,  6 May 2018 21:45:22 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Subject: Re: Working Group Last Call: QUIC Invariants
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <ADF53A3A-447C-40D3-97F4-9943058CBB36@mnot.net>
Date: Mon, 7 May 2018 11:45:19 +1000
Cc: Lars Eggert <lars@eggert.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <45C7358E-99A9-4D12-BBF9-B543696E175C@mnot.net>
References: <ADF53A3A-447C-40D3-97F4-9943058CBB36@mnot.net>
To: IETF QUIC WG <quic@ietf.org>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7THHfB4TQVzJtWgCQwLTYeyH2R8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2018 01:45:27 -0000

This WGLC ended a while back. As discussed, this document will be parked =
with consensus to publish until the other documents catch up.

Regards,


> On 22 Mar 2018, at 12:41 am, Mark Nottingham <mnot@mnot.net> wrote:
>=20
> In London, we continued discussion of the Invariants document, and =
confirmed the plan to issue a WGLC on it now, with the understanding =
that after WGLC closes we will "park" the document until the rest of the =
document set is ready for publication.
>=20
> The purpose of doing so is to give a high level of confidence that the =
invariants will not change, while leaving the possibility of changes =
open if we find *strong* reasons to do so -- i.e., the bar for =
introducing changes to the Invariants will be much higher after WGLC.
>=20
> Please have a look at the document and raise any issues on the issues =
list or on this e-mail list:
>  https://tools.ietf.org/html/draft-ietf-quic-invariants-01
>=20
> WGLC will end on 11 April 2018.
>=20
> Regards,
>=20
> Mark and Lars, WG Chairs
>=20

--
Mark Nottingham   https://www.mnot.net/


From nobody Mon May  7 14:35:11 2018
Return-Path: <briansw@microsoft.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4D1B412D7E8 for <quic@ietfa.amsl.com>; Mon,  7 May 2018 14:35:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 GsI7YTin3Wr1 for <quic@ietfa.amsl.com>; Mon,  7 May 2018 14:35:06 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0719.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe45::719]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C7A57124234 for <quic@ietf.org>; Mon,  7 May 2018 14:35:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=sBJjhDUbnp3rkRKkrdYnlpLo5izY+IHiSvd26nd8pAI=; b=netE7Ou/Eb75xraM/xFKk7Kk3OiQjvGFQU/R2uG/DkK8c0FQALS4Ow9E1RZ/56V9kMBbGaNQ4u2aXJCkwHoYZahXSZOkyfk7Wuisaf6Hf5iEwMETVmzVRDUwzItLTnPpCgnDP6FEyxee+csQ5VQKVLWbh1zNVZJ5f4bnMu67Xu4=
Received: from DM5PR21MB0857.namprd21.prod.outlook.com (10.173.172.143) by DM5PR21MB0474.namprd21.prod.outlook.com (10.172.92.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.776.3; Mon, 7 May 2018 21:35:05 +0000
Received: from DM5PR21MB0857.namprd21.prod.outlook.com ([fe80::e926:e65e:c9a6:365d]) by DM5PR21MB0857.namprd21.prod.outlook.com ([fe80::e926:e65e:c9a6:365d%9]) with mapi id 15.20.0776.004; Mon, 7 May 2018 21:35:05 +0000
From: Brian Swander <briansw@microsoft.com>
To: "quic@ietf.org" <quic@ietf.org>
Subject: QPACK - proposal to optimize compression
Thread-Topic: QPACK - proposal to optimize compression
Thread-Index: AdPmSVy6766G9sm1TzOdAr1rcH/nrA==
Date: Mon, 7 May 2018 21:35:05 +0000
Message-ID: <DM5PR21MB0857F41DCB080F130E1436ADB39B0@DM5PR21MB0857.namprd21.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Owner=briansw@microsoft.com; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2018-05-07T21:35:04.6051258Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic; Sensitivity=General
x-originating-ip: [2001:4898:80e8:a::7cc]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR21MB0474; 7:CobFbAlPqGk/NiGlR4h0Y3V5sqVXCHu6IFQBAKDabmwDni87vOh+JBKPC1jCNR/pQzUm+VBB83Ndb9gJR+ksL+jW7swZbqgQMWK/7SKmjS2uNo1odQvnZCzVfjkwmRftwnfL7nhYfikVa6kJBI4g6ET93ku5gRWCJTyExTxHLHcl/EU7PQEFceZIhNIRM0v8YlBcjgAcUY78pm8gjcwsgxrLjMT166Y30NpPlvsBrPwUWT9sH2o3DVFTR7BgrfxF; 20:IWIk5GmKxk8TaxwPrhWZsctFMFwlJmq5ZUSkMjh1fwoSBtWLSHsMnk19Jb1nkf7Kh0myoBbox11dB9e1nAETZBmPKnW4SF8izvSa8gzmGgs10W8tIAgX7j3HUD3M2xvu4DTEz16MSRLE0saN0qKi6LtA1jXBgtlhVlcjUkwyw/4=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(48565401081)(2017052603328)(7193020); SRVR:DM5PR21MB0474; 
x-ms-traffictypediagnostic: DM5PR21MB0474:
x-microsoft-antispam-prvs: <DM5PR21MB04746553AA35BF0E10FE7D34B39B0@DM5PR21MB0474.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3002001)(3231254)(2018427008)(944501410)(52105095)(10201501046)(93006095)(93001095)(6055026)(149027)(150027)(6041310)(20161123558120)(20161123562045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(6072148)(201708071742011); SRVR:DM5PR21MB0474; BCL:0; PCL:0; RULEID:; SRVR:DM5PR21MB0474; 
x-forefront-prvs: 066517B35B
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(346002)(39860400002)(39380400002)(396003)(366004)(189003)(199004)(7736002)(86362001)(5660300001)(86612001)(55016002)(105586002)(10290500003)(6506007)(6346003)(316002)(102836004)(68736007)(486006)(97736004)(478600001)(9686003)(22452003)(476003)(25786009)(5640700003)(33656002)(6916009)(6306002)(186003)(6436002)(54896002)(74316002)(46003)(8990500004)(5630700001)(8936002)(6116002)(81156014)(2906002)(5250100002)(1730700003)(81166006)(8676002)(2501003)(10090500001)(2900100001)(99286004)(53936002)(2351001)(790700001)(106356001)(3280700002)(3660700001)(14454004)(7696005); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR21MB0474; H:DM5PR21MB0857.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=briansw@microsoft.com; 
x-microsoft-antispam-message-info: bSBlVzmYe/HW0iGQ5grPN0KJHUPAfTCALpievZrQlcKLCJJMwRJpfRoLivzI088ItXlw1M8RiR190oo5bSIzyxAzLNzyzZwJbU5LCQlbquDyXlUqlYhGjKQSvMu9E5tAV5dYNzwoLbr206J0GXj8kKdUOp/1yHZh/5B6yGnmL9VyGFTjDPIxo4PSLqZQaUpG
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM5PR21MB0857F41DCB080F130E1436ADB39B0DM5PR21MB0857namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 533bf5ab-7ac2-413d-9522-08d5b462661e
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 533bf5ab-7ac2-413d-9522-08d5b462661e
X-MS-Exchange-CrossTenant-originalarrivaltime: 07 May 2018 21:35:05.4930 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR21MB0474
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Aahe7gc8L0ECQIkOXQ2JrCZOVco>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 07 May 2018 21:35:09 -0000

--_000_DM5PR21MB0857F41DCB080F130E1436ADB39B0DM5PR21MB0857namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Please correct me if I'm wrong here.

It looks like the latest QPACK draft has been optimized to allow encode of =
both control and data streams in a single pass.
Because of this, we now must support that post-base encoding, and the multi=
ple encoding formats that use Post-Base.
I.e. Literal Header Field with Name Reference and Literal Header Filter Wit=
h Post-Base Name Reference, and similarly for Indexed Header Field.

To me, it seems like the simpler, more efficient option of removing post-ba=
se entirely could be better.   At the cost of requiring 2-pass encode, we c=
an save a few bits for most headers since we would never need the post base=
 header prefix.

So it's a question of looping thru the headers twice, vs. being less effici=
ent on the wire.

I haven't profiled it, but I'd guess that double pass thru the headers isn'=
t going to be that much slower than single pass.   Many of the headers are =
going to be encoded in both streams.   So the more efficient wire format ma=
y be more optimal.

bs

--_000_DM5PR21MB0857F41DCB080F130E1436ADB39B0DM5PR21MB0857namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;
	font-weight:normal;
	font-style:normal;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Please correct me i=
f I&#8217;m wrong here.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">It looks like the l=
atest QPACK draft has been optimized to allow encode of both control and da=
ta streams in a single pass.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">Because of this, we=
 now must support that post-base encoding, and the multiple encoding format=
s that use Post-Base.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">I.e. Literal Header=
 Field with Name Reference and Literal Header Filter With Post-Base Name Re=
ference, and similarly for Indexed Header Field.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">To me, it seems lik=
e the simpler, more efficient option of removing post-base entirely could b=
e better.&nbsp;&nbsp; At the cost of requiring 2-pass encode, we can save a=
 few bits for most headers since we would never
 need the post base header prefix.&nbsp;&nbsp; <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">So it&#8217;s a que=
stion of looping thru the headers twice, vs. being less efficient on the wi=
re.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">I haven&#8217;t pro=
filed it, but I&#8217;d guess that double pass thru the headers isn&#8217;t=
 going to be that much slower than single pass. &nbsp;&nbsp;Many of the hea=
ders are going to be encoded in both streams.&nbsp;&nbsp; So the more effic=
ient
 wire format may be more optimal.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></=
span></p>
<p class=3D"MsoNormal"><span style=3D"font-size:12.0pt">bs<o:p></o:p></span=
></p>
</div>
</body>
</html>

--_000_DM5PR21MB0857F41DCB080F130E1436ADB39B0DM5PR21MB0857namp_--


From nobody Tue May  8 13:39:43 2018
Return-Path: <prvs=8666beae1a=afrind@fb.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22C1C12EAC0 for <quic@ietfa.amsl.com>; Tue,  8 May 2018 13:39:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=fpteT1pl; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=dX5IO6J6
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 XBU3zdtcIGNo for <quic@ietfa.amsl.com>; Tue,  8 May 2018 13:39:38 -0700 (PDT)
Received: from mx0a-00082601.pphosted.com (mx0a-00082601.pphosted.com [67.231.145.42]) (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 8083612EAC6 for <quic@ietf.org>; Tue,  8 May 2018 13:39:38 -0700 (PDT)
Received: from pps.filterd (m0044010.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w48KCCdu022013; Tue, 8 May 2018 13:13:23 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=facebook; bh=IijVSuV1fDxYFZ4vViicUfbFZsoxEwAlWnLEr21aSWw=; b=fpteT1plvuDBYEmzgZcwsHXTf/IVYmeBBCx4OrF1ID6b+5dfq7Un1K00zbR9TVj3nHFL iJI74u18wG1jXsPV18Ay6+PZ9uhYBEx7mPMQretWc5inPrGXGjt7aVa/xspHevREjJJL aLVInqD1MTCQmu4BZAROEwQOrXHwaJfE2dE= 
Received: from mail.thefacebook.com ([199.201.64.23]) by mx0a-00082601.pphosted.com with ESMTP id 2huhqa06f0-2 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 08 May 2018 13:13:22 -0700
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (192.168.54.28) by o365-in.thefacebook.com (192.168.16.17) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 8 May 2018 13:12:59 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version;  bh=IijVSuV1fDxYFZ4vViicUfbFZsoxEwAlWnLEr21aSWw=; b=dX5IO6J689imrOoovinrhyUA8BjIUjBm95GOnUagjf7upEPOaDIdJv9nT1hn0rT27G6ku+ByDKjrdAgdXGlyjEjCwD9/wbpH+ZgI5wRMPmOpmLZD9wJ64FzjVO0PfBkroUe7ufZH9E0tKcSqMpd73eAUCbzjH8GtoduqLrnA+90=
Received: from MWHPR15MB1181.namprd15.prod.outlook.com (10.175.2.135) by MWHPR15MB1743.namprd15.prod.outlook.com (10.174.255.8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.735.17; Tue, 8 May 2018 20:12:53 +0000
Received: from MWHPR15MB1181.namprd15.prod.outlook.com ([fe80::555:6a20:1573:7b7a]) by MWHPR15MB1181.namprd15.prod.outlook.com ([fe80::555:6a20:1573:7b7a%18]) with mapi id 15.20.0735.019; Tue, 8 May 2018 20:12:53 +0000
From: Alan Frindell <afrind@fb.com>
To: Brian Swander <briansw=40microsoft.com@dmarc.ietf.org>, "quic@ietf.org" <quic@ietf.org>
Subject: Re: QPACK - proposal to optimize compression
Thread-Topic: QPACK - proposal to optimize compression
Thread-Index: AdPmSVy6766G9sm1TzOdAr1rcH/nrAAhOhQA
Date: Tue, 8 May 2018 20:12:53 +0000
Message-ID: <BCF18407-B5DD-4608-ACFE-C229E17A2C1B@fb.com>
References: <DM5PR21MB0857F41DCB080F130E1436ADB39B0@DM5PR21MB0857.namprd21.prod.outlook.com>
In-Reply-To: <DM5PR21MB0857F41DCB080F130E1436ADB39B0@DM5PR21MB0857.namprd21.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.c.0.180410
x-originating-ip: [2620:10d:c090:200::5:d48]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MWHPR15MB1743; 7:i56o/CSggBlEgqrBeUFWZMaqyNdz+2tGtbCCJdxBzboMd9evGk6F5bynZiabnrV9te1Z8WJRnol+dnw5xIB/iLyPspnb3+62an1smFefgCMI/8uW/mAk9PhaVLweMljFHL1pVgNOGgHYeioghVgfgTTjqPpU9RXJJIQOwn2RT/KvQm3c14YRTlTJ149N8ZkGDT9fuK9W97VJQPECoMRFMgbKdjBEBM7ZqCManFWKcJDWTm+LaNE6A+LcufRNoDIJ; 20:JmBcGaDm3ltIyRnicGBCY5fKMkpeQLAl6yAMkkK9FpVJQSCW/G3paBziUCZQH3o+5jQm1yEbuuLicpzAxcnwvLsVdK+iLT4LDswD6fNtajcU3CydXSglbrcb4jqP9/sqcsGfZOaUcfWZJYv441BPzLwLou+SDWZ6q6lhrMY+kn0=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:MWHPR15MB1743; 
x-ms-traffictypediagnostic: MWHPR15MB1743:
x-microsoft-antispam-prvs: <MWHPR15MB1743A46E7EDA6D716DF7904AA79A0@MWHPR15MB1743.namprd15.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(100405760836317)(21748063052155); 
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3002001)(10201501046)(3231254)(11241501184)(944501410)(52105095)(93006095)(93001095)(149027)(150027)(6041310)(20161123558120)(20161123564045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(6072148)(201708071742011); SRVR:MWHPR15MB1743; BCL:0; PCL:0; RULEID:; SRVR:MWHPR15MB1743; 
x-forefront-prvs: 0666E15D35
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(396003)(346002)(376002)(39860400002)(39380400002)(199004)(189003)(561944003)(8936002)(316002)(14454004)(81156014)(46003)(53546011)(59450400001)(6506007)(68736007)(6436002)(446003)(58126008)(7736002)(8676002)(110136005)(6486002)(2616005)(11346002)(33656002)(6116002)(102836004)(3660700001)(5660300001)(25786009)(3280700002)(2906002)(478600001)(36756003)(105586002)(106356001)(76176011)(81166006)(82746002)(86362001)(99286004)(486006)(6306002)(6512007)(54896002)(2501003)(5250100002)(83716003)(186003)(476003)(6246003)(2900100001)(53936002)(97736004)(229853002); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR15MB1743; H:MWHPR15MB1181.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: fb.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 7yZnKMnTrcOdgWZ5SQRjkEg6gHDDPp1QbZ7UD9RUBsyTLxT/6K7pAWSOJMyzDNSBjdZEGFtnAB3AtnPavbUyQ2FU2OPR6gpsWmqv6ZWwIlX+um0hANYrmYWKgTzObsUeZE673FPsWnRJW4UijVCk9L57P61A8CjrjDaPNTRNlSjHj3lW+rzJw4akZiw9ubL/
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BCF18407B5DD4608ACFEC229E17A2C1Bfbcom_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: eb90aa1d-8471-4162-e578-08d5b520149b
X-MS-Exchange-CrossTenant-Network-Message-Id: eb90aa1d-8471-4162-e578-08d5b520149b
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 May 2018 20:12:53.0885 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR15MB1743
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-08_07:, , signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/iGqBU3u95V7-6cIcX2QSJrkyWeA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2018 20:39:41 -0000

--_000_BCF18407B5DD4608ACFEC229E17A2C1Bfbcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

U2luZ2xlIHBhc3MgZW5jb2RpbmcgaXMgbm90IHJlcXVpcmVkLCBhbiBlbmNvZGVyIGhhcyB0aGUg
b3B0aW9uIHRvIGVuY29kZSB1c2luZyBvbmUgb3IgdHdvIHBhc3Nlcy4gIFRoZSBvbmx5IHdpcmUg
cGVuYWx0eSBmb3IgYSB0d28tcGFzcyBlbmNvZGVyIGlzIG9uZSBleHRyYSBieXRlIHBlciBoZWFk
ZXIgYmxvY2sgaW4gdGhlIHByZWZpeCwgYXMgbGFyZ2VzdCByZWZlcmVuY2UgYW5kIGJhc2UgaW5k
ZXggY2FuIGJlIHRoZSBzYW1lIGluIHR3by1wYXNzIGVuY29kaW5nLiAgVGhlIG9yaWdpbmFsIHNw
ZWNpZmljYXRpb24gKHdoaWNoIHVzZWQgRGVwZW5kcykgaGFkIGEgb25lIGJpdCBmbGFnIGluIHRo
ZSBIVFRQIGZyYW1lIHRoYXQgYWxsb3dlZCB0aGUgZW5jb2RlciBzYXZlIHRoaXMgYnl0ZSBhcyB3
ZWxsLCBidXQgdGhlIGNvbnNlbnN1cyBzZWVtZWQgdG8gYmUgaXQgd2FzIGJldHRlciB0byBoYXZl
IGEgZml4ZWQgZm9ybWF0IHRvIHRoZSBwcmVmaXguICBXaXRob3V0IHBvc3QtYmFzZSwgdGhlcmUg
Y291bGQgYWxzbyBiZSBvbmUgbW9yZSBiaXQgYXZhaWxhYmxlIGZvciB0aGUgbGVuZ3RoIG9mIGEg
bGl0ZXJhbCBoZWFkZXIgbmFtZSB3aXRob3V0IGFkZGluZyBhbiBleHRyYSBieXRlIChoZWFkZXIg
bmFtZXMgd2l0aCA3IDw9IGxlbmd0aCA8IDE1KS4gIFdlIGNhbiBvZiBjb3Vyc2Ugc2ltdWxhdGUg
aXQsIGJ1dCBJIGV4cGVjdCB0aGUgZGlmZmVyZW5jZSB0byBiZSBpbiB0aGUgbm9pc2UuDQoNCkRl
Y29kZXJzIGRvIG5lZWQgdG8gc3VwcG9ydCBib3RoIGtpbmRzIG9mIGluc3RydWN0aW9ucywgYnV0
IEkgZG9u4oCZdCBmaW5kIGl0IHRvIGJlIHRlcnJpYmx5IGNvbXBsZXguICBUaGUgcHJveHlnZW4g
aW1wbGVtZW50YXRpb24gb2YgdGhlIGxhdGVzdCBkcmFmdCBpbmNsdWRpbmcgb25lLXBhc3MgZW5j
b2RpbmcvZGVjb2Rpbmcgc2hvdWxkIGJlIHN5bmNlZCB0byBnaXRodWIgdGhpcyB3ZWVrLg0KDQpJ
4oCZbSBub3Qgc3VyZSB3aGF0IHlvdSBtZWFuIHdoZW4geW91IHNheSDigJxNYW55IG9mIHRoZSBo
ZWFkZXJzIGFyZSBnb2luZyB0byBiZSBlbmNvZGVkIGluIGJvdGggc3RyZWFtcy7igJ0gIElmIHlv
dSBtZWFuIGl0IHdpbGwgZW5jb2RlIGFuIGluc2VydCBvbiB0aGUgY29udHJvbCBzdHJlYW0gYW5k
IGFuIGluZGV4IHJlZmVyZW5jZSBvbiB0aGUgcmVxdWVzdCBzdHJlYW0sIHRoYXQgaXMgdHJ1ZSwg
YW5kIHRoZSBwb3N0LWJhc2UgZW5jb2Rpbmcgb2YgdGhlIHJlZmVyZW5jZXMgb2NjdXBpZXMgb25s
eSBvbmUgYnl0ZSBmb3IgdGhlIGZpcnN0IDE1IHN1Y2ggaGVhZGVycyBwZXIgYmxvY2suDQoNCi1B
bGFuDQoNCg0KRnJvbTogUVVJQyA8cXVpYy1ib3VuY2VzQGlldGYub3JnPiBvbiBiZWhhbGYgb2Yg
QnJpYW4gU3dhbmRlciA8YnJpYW5zdz00MG1pY3Jvc29mdC5jb21AZG1hcmMuaWV0Zi5vcmc+DQpE
YXRlOiBNb25kYXksIE1heSA3LCAyMDE4IGF0IDI6MzUgUE0NClRvOiAicXVpY0BpZXRmLm9yZyIg
PHF1aWNAaWV0Zi5vcmc+DQpTdWJqZWN0OiBRUEFDSyAtIHByb3Bvc2FsIHRvIG9wdGltaXplIGNv
bXByZXNzaW9uDQoNClBsZWFzZSBjb3JyZWN0IG1lIGlmIEnigJltIHdyb25nIGhlcmUuDQoNCkl0
IGxvb2tzIGxpa2UgdGhlIGxhdGVzdCBRUEFDSyBkcmFmdCBoYXMgYmVlbiBvcHRpbWl6ZWQgdG8g
YWxsb3cgZW5jb2RlIG9mIGJvdGggY29udHJvbCBhbmQgZGF0YSBzdHJlYW1zIGluIGEgc2luZ2xl
IHBhc3MuDQpCZWNhdXNlIG9mIHRoaXMsIHdlIG5vdyBtdXN0IHN1cHBvcnQgdGhhdCBwb3N0LWJh
c2UgZW5jb2RpbmcsIGFuZCB0aGUgbXVsdGlwbGUgZW5jb2RpbmcgZm9ybWF0cyB0aGF0IHVzZSBQ
b3N0LUJhc2UuDQpJLmUuIExpdGVyYWwgSGVhZGVyIEZpZWxkIHdpdGggTmFtZSBSZWZlcmVuY2Ug
YW5kIExpdGVyYWwgSGVhZGVyIEZpbHRlciBXaXRoIFBvc3QtQmFzZSBOYW1lIFJlZmVyZW5jZSwg
YW5kIHNpbWlsYXJseSBmb3IgSW5kZXhlZCBIZWFkZXIgRmllbGQuDQoNClRvIG1lLCBpdCBzZWVt
cyBsaWtlIHRoZSBzaW1wbGVyLCBtb3JlIGVmZmljaWVudCBvcHRpb24gb2YgcmVtb3ZpbmcgcG9z
dC1iYXNlIGVudGlyZWx5IGNvdWxkIGJlIGJldHRlci4gICBBdCB0aGUgY29zdCBvZiByZXF1aXJp
bmcgMi1wYXNzIGVuY29kZSwgd2UgY2FuIHNhdmUgYSBmZXcgYml0cyBmb3IgbW9zdCBoZWFkZXJz
IHNpbmNlIHdlIHdvdWxkIG5ldmVyIG5lZWQgdGhlIHBvc3QgYmFzZSBoZWFkZXIgcHJlZml4Lg0K
DQpTbyBpdOKAmXMgYSBxdWVzdGlvbiBvZiBsb29waW5nIHRocnUgdGhlIGhlYWRlcnMgdHdpY2Us
IHZzLiBiZWluZyBsZXNzIGVmZmljaWVudCBvbiB0aGUgd2lyZS4NCg0KSSBoYXZlbuKAmXQgcHJv
ZmlsZWQgaXQsIGJ1dCBJ4oCZZCBndWVzcyB0aGF0IGRvdWJsZSBwYXNzIHRocnUgdGhlIGhlYWRl
cnMgaXNu4oCZdCBnb2luZyB0byBiZSB0aGF0IG11Y2ggc2xvd2VyIHRoYW4gc2luZ2xlIHBhc3Mu
ICAgTWFueSBvZiB0aGUgaGVhZGVycyBhcmUgZ29pbmcgdG8gYmUgZW5jb2RlZCBpbiBib3RoIHN0
cmVhbXMuICAgU28gdGhlIG1vcmUgZWZmaWNpZW50IHdpcmUgZm9ybWF0IG1heSBiZSBtb3JlIG9w
dGltYWwuDQoNCmJzDQo=

--_000_BCF18407B5DD4608ACFEC229E17A2C1Bfbcom_
Content-Type: text/html; charset="utf-8"
Content-ID: <FF43ADFCAF8F124095907E84FB4BDDFB@namprd15.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1i
b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
IixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9
DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpw
Lm1zb25vcm1hbDAsIGxpLm1zb25vcm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1u
YW1lOm1zb25vcm1hbDsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6
MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglm
b250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNw
YW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5
OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7DQoJZm9udC13ZWlnaHQ6
bm9ybWFsOw0KCWZvbnQtc3R5bGU6bm9ybWFsO30NCnNwYW4uRW1haWxTdHlsZTE5DQoJe21zby1z
dHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNl
cmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5
cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjEN
Cgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30N
CmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT4NCjwv
aGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSIjMDU2M0MxIiB2bGluaz0iIzk1NEY3MiI+
DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U2luZ2xl
IHBhc3MgZW5jb2RpbmcgaXMgbm90IHJlcXVpcmVkLCBhbiBlbmNvZGVyIGhhcyB0aGUgb3B0aW9u
IHRvIGVuY29kZSB1c2luZyBvbmUgb3IgdHdvIHBhc3Nlcy4mbmJzcDsgVGhlIG9ubHkgd2lyZSBw
ZW5hbHR5IGZvciBhIHR3by1wYXNzIGVuY29kZXIgaXMgb25lIGV4dHJhIGJ5dGUgcGVyIGhlYWRl
ciBibG9jayBpbiB0aGUgcHJlZml4LCBhcyBsYXJnZXN0IHJlZmVyZW5jZSBhbmQgYmFzZSBpbmRl
eCBjYW4gYmUNCiB0aGUgc2FtZSBpbiB0d28tcGFzcyBlbmNvZGluZy4mbmJzcDsgVGhlIG9yaWdp
bmFsIHNwZWNpZmljYXRpb24gKHdoaWNoIHVzZWQgRGVwZW5kcykgaGFkIGEgb25lIGJpdCBmbGFn
IGluIHRoZSBIVFRQIGZyYW1lIHRoYXQgYWxsb3dlZCB0aGUgZW5jb2RlciBzYXZlIHRoaXMgYnl0
ZSBhcyB3ZWxsLCBidXQgdGhlIGNvbnNlbnN1cyBzZWVtZWQgdG8gYmUgaXQgd2FzIGJldHRlciB0
byBoYXZlIGEgZml4ZWQgZm9ybWF0IHRvIHRoZSBwcmVmaXguJm5ic3A7IFdpdGhvdXQNCiBwb3N0
LWJhc2UsIHRoZXJlIGNvdWxkIGFsc28gYmUgb25lIG1vcmUgYml0IGF2YWlsYWJsZSBmb3IgdGhl
IGxlbmd0aCBvZiBhIGxpdGVyYWwgaGVhZGVyIG5hbWUgd2l0aG91dCBhZGRpbmcgYW4gZXh0cmEg
Ynl0ZSAoaGVhZGVyIG5hbWVzIHdpdGggNyAmbHQ7PSBsZW5ndGggJmx0OyAxNSkuJm5ic3A7IFdl
IGNhbiBvZiBjb3Vyc2Ugc2ltdWxhdGUgaXQsIGJ1dCBJIGV4cGVjdCB0aGUgZGlmZmVyZW5jZSB0
byBiZSBpbiB0aGUgbm9pc2UuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkRlY29kZXJzIGRvIG5l
ZWQgdG8gc3VwcG9ydCBib3RoIGtpbmRzIG9mIGluc3RydWN0aW9ucywgYnV0IEkgZG9u4oCZdCBm
aW5kIGl0IHRvIGJlIHRlcnJpYmx5IGNvbXBsZXguJm5ic3A7IFRoZSBwcm94eWdlbiBpbXBsZW1l
bnRhdGlvbiBvZiB0aGUgbGF0ZXN0IGRyYWZ0IGluY2x1ZGluZyBvbmUtcGFzcyBlbmNvZGluZy9k
ZWNvZGluZyBzaG91bGQgYmUgc3luY2VkIHRvIGdpdGh1YiB0aGlzIHdlZWsuPG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPknigJltIG5vdCBzdXJlIHdoYXQgeW91IG1lYW4gd2hlbiB5b3Ugc2F5IOKA
nE1hbnkgb2YgdGhlIGhlYWRlcnMgYXJlIGdvaW5nIHRvIGJlIGVuY29kZWQgaW4gYm90aCBzdHJl
YW1zLuKAnSZuYnNwOyBJZiB5b3UgbWVhbiBpdCB3aWxsIGVuY29kZSBhbiBpbnNlcnQgb24gdGhl
IGNvbnRyb2wgc3RyZWFtIGFuZCBhbiBpbmRleCByZWZlcmVuY2Ugb24gdGhlIHJlcXVlc3Qgc3Ry
ZWFtLCB0aGF0IGlzIHRydWUsIGFuZCB0aGUgcG9zdC1iYXNlDQogZW5jb2Rpbmcgb2YgdGhlIHJl
ZmVyZW5jZXMgb2NjdXBpZXMgb25seSBvbmUgYnl0ZSBmb3IgdGhlIGZpcnN0IDE1IHN1Y2ggaGVh
ZGVycyBwZXIgYmxvY2suPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi1BbGFuPG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAw
aW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4w
cHQ7Y29sb3I6YmxhY2siPkZyb206IDwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
Mi4wcHQ7Y29sb3I6YmxhY2siPlFVSUMgJmx0O3F1aWMtYm91bmNlc0BpZXRmLm9yZyZndDsgb24g
YmVoYWxmIG9mIEJyaWFuIFN3YW5kZXIgJmx0O2JyaWFuc3c9NDBtaWNyb3NvZnQuY29tQGRtYXJj
LmlldGYub3JnJmd0Ozxicj4NCjxiPkRhdGU6IDwvYj5Nb25kYXksIE1heSA3LCAyMDE4IGF0IDI6
MzUgUE08YnI+DQo8Yj5UbzogPC9iPiZxdW90O3F1aWNAaWV0Zi5vcmcmcXVvdDsgJmx0O3F1aWNA
aWV0Zi5vcmcmZ3Q7PGJyPg0KPGI+U3ViamVjdDogPC9iPlFQQUNLIC0gcHJvcG9zYWwgdG8gb3B0
aW1pemUgY29tcHJlc3Npb248bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PGEgbmFtZT0iX01haWxPcmlnaW5hbEJvZHkiPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTIuMHB0Ij5QbGVhc2UgY29ycmVjdCBtZSBpZiBJ4oCZbSB3cm9uZyBoZXJlLjwv
c3Bhbj48bzpwPjwvbzpwPjwvYT48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEyLjBwdCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0Ij5JdCBsb29rcyBsaWtlIHRoZSBsYXRlc3QgUVBB
Q0sgZHJhZnQgaGFzIGJlZW4gb3B0aW1pemVkIHRvIGFsbG93IGVuY29kZSBvZiBib3RoIGNvbnRy
b2wgYW5kIGRhdGEgc3RyZWFtcyBpbiBhIHNpbmdsZSBwYXNzLjwvc3Bhbj48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJr
Ol9NYWlsT3JpZ2luYWxCb2R5Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdCI+QmVjYXVz
ZSBvZiB0aGlzLCB3ZSBub3cgbXVzdCBzdXBwb3J0IHRoYXQgcG9zdC1iYXNlIGVuY29kaW5nLCBh
bmQgdGhlIG11bHRpcGxlIGVuY29kaW5nIGZvcm1hdHMgdGhhdCB1c2UgUG9zdC1CYXNlLjwvc3Bh
bj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEyLjBwdCI+SS5lLiBMaXRlcmFsIEhlYWRlciBGaWVsZCB3aXRoIE5hbWUgUmVmZXJlbmNlIGFu
ZCBMaXRlcmFsIEhlYWRlciBGaWx0ZXIgV2l0aCBQb3N0LUJhc2UgTmFtZSBSZWZlcmVuY2UsIGFu
ZCBzaW1pbGFybHkgZm9yIEluZGV4ZWQgSGVhZGVyIEZpZWxkLjwvc3Bhbj48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJr
Ol9NYWlsT3JpZ2luYWxCb2R5Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdCI+Jm5ic3A7
PC9zcGFuPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPjxzcGFuIHN0eWxlPSJmb250
LXNpemU6MTIuMHB0Ij5UbyBtZSwgaXQgc2VlbXMgbGlrZSB0aGUgc2ltcGxlciwgbW9yZSBlZmZp
Y2llbnQgb3B0aW9uIG9mIHJlbW92aW5nIHBvc3QtYmFzZSBlbnRpcmVseSBjb3VsZCBiZSBiZXR0
ZXIuJm5ic3A7Jm5ic3A7IEF0IHRoZSBjb3N0IG9mIHJlcXVpcmluZyAyLXBhc3MgZW5jb2RlLCB3
ZSBjYW4gc2F2ZSBhDQogZmV3IGJpdHMgZm9yIG1vc3QgaGVhZGVycyBzaW5jZSB3ZSB3b3VsZCBu
ZXZlciBuZWVkIHRoZSBwb3N0IGJhc2UgaGVhZGVyIHByZWZpeC4mbmJzcDsmbmJzcDsNCjwvc3Bh
bj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij48c3BhbiBzdHlsZT0iZm9udC1zaXpl
OjEyLjBwdCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0Ij5TbyBpdOKAmXMgYSBxdWVzdGlvbiBvZiBsb29w
aW5nIHRocnUgdGhlIGhlYWRlcnMgdHdpY2UsIHZzLiBiZWluZyBsZXNzIGVmZmljaWVudCBvbiB0
aGUgd2lyZS48L3NwYW4+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMi4wcHQiPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3Jp
Z2luYWxCb2R5Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdCI+SSBoYXZlbuKAmXQgcHJv
ZmlsZWQgaXQsIGJ1dCBJ4oCZZCBndWVzcyB0aGF0IGRvdWJsZSBwYXNzIHRocnUgdGhlIGhlYWRl
cnMgaXNu4oCZdCBnb2luZyB0byBiZSB0aGF0IG11Y2ggc2xvd2VyIHRoYW4gc2luZ2xlIHBhc3Mu
ICZuYnNwOyZuYnNwO01hbnkgb2YgdGhlIGhlYWRlcnMgYXJlIGdvaW5nIHRvIGJlDQogZW5jb2Rl
ZCBpbiBib3RoIHN0cmVhbXMuJm5ic3A7Jm5ic3A7IFNvIHRoZSBtb3JlIGVmZmljaWVudCB3aXJl
IGZvcm1hdCBtYXkgYmUgbW9yZSBvcHRpbWFsLjwvc3Bhbj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3Jp
Z2luYWxCb2R5Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdCI+Jm5ic3A7PC9zcGFuPjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJt
c28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIu
MHB0Ij5iczwvc3Bhbj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvYm9keT4NCjwv
aHRtbD4NCg==

--_000_BCF18407B5DD4608ACFEC229E17A2C1Bfbcom_--


From nobody Tue May  8 13:50:24 2018
Return-Path: <briansw@microsoft.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4497912EACA for <quic@ietfa.amsl.com>; Tue,  8 May 2018 13:50:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level: 
X-Spam-Status: No, score=-2.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 YzIn8zKsMFGd for <quic@ietfa.amsl.com>; Tue,  8 May 2018 13:50:19 -0700 (PDT)
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0101.outbound.protection.outlook.com [104.47.34.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B50412EABF for <quic@ietf.org>; Tue,  8 May 2018 13:50:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=gnDTzzWI8P5FiFAOxWvcAU4SkIRFzgp82vhyWK0SWug=; b=lfzUSkPp1jzvye9b7YxwwHp/vfZhK9nixwaHTLRPFvCbfOQe8T9u53f1n4g5mHQ6hpHGnlQ8gD0K+S6IMtBgg2R9xaIBVJQRXrupoPHZZfIQomqWKDZ65L4ng2MDGflnv+GLoqC27tbb0EV6xxE32BtQjZbKHJvPqgNv//nvK50=
Received: from DM5PR21MB0857.namprd21.prod.outlook.com (10.173.172.143) by DM5PR21MB0825.namprd21.prod.outlook.com (10.173.172.7) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.776.3; Tue, 8 May 2018 20:50:17 +0000
Received: from DM5PR21MB0857.namprd21.prod.outlook.com ([fe80::e926:e65e:c9a6:365d]) by DM5PR21MB0857.namprd21.prod.outlook.com ([fe80::e926:e65e:c9a6:365d%9]) with mapi id 15.20.0776.004; Tue, 8 May 2018 20:50:17 +0000
From: Brian Swander <briansw@microsoft.com>
To: Alan Frindell <afrind@fb.com>, "quic@ietf.org" <quic@ietf.org>
Subject: RE: QPACK - proposal to optimize compression
Thread-Topic: QPACK - proposal to optimize compression
Thread-Index: AdPmSVy6766G9sm1TzOdAr1rcH/nrAAhOhQAAA++e/A=
Date: Tue, 8 May 2018 20:50:17 +0000
Message-ID: <DM5PR21MB08572BEFDA60C6EE920D0357B39A0@DM5PR21MB0857.namprd21.prod.outlook.com>
References: <DM5PR21MB0857F41DCB080F130E1436ADB39B0@DM5PR21MB0857.namprd21.prod.outlook.com> <BCF18407-B5DD-4608-ACFE-C229E17A2C1B@fb.com>
In-Reply-To: <BCF18407-B5DD-4608-ACFE-C229E17A2C1B@fb.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Owner=briansw@microsoft.com; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2018-05-08T20:50:16.6195148Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic; Sensitivity=General
x-originating-ip: [2001:4898:80e8:a::7cc]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR21MB0825; 7:0z4Uw3iHBfxyvxsguWOTBcN71GrOaQpk7MwaAP+RxjBkDnpGr5n5vwWqVOtx9HPiwt1nGG51vp5wuI2Alek2uNnYkJ3Ohs8RF6qUrErS9BpfYLuwEKqbWJSNnrP/iOF6JmCt7bx39mcKkehK2Wxn0P4PCPXFoGndmSFrZlcF3TwWVPktsB0T1HSjGP0q6bSF8tLWCMEo3jOYp6avD2T4gpyQRPkJ97AaAV717kOB6NA3CXlIgP0W10P2BvFl/f0F; 20:P9dmkaZSeaYW7Ihcyu3hqLG8tAmQJ8G61nIcaEw1Jg/RTLqn5oinTLZUAXpILknlePUCKvVCehu0naP+uhhDH2RIPFIAMC6jZyCa3vrRY16zzGaACAn/w9jRvSp0dMuR29K+rHZ8jwsa0KbE6CakZTnwhnmOrhKzlvfEF0mXRoM=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(48565401081)(2017052603328)(7193020); SRVR:DM5PR21MB0825; 
x-ms-traffictypediagnostic: DM5PR21MB0825:
x-microsoft-antispam-prvs: <DM5PR21MB0825D2B8A415BA9081CAF9E9B39A0@DM5PR21MB0825.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(89211679590171)(67672495146484)(100405760836317)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93001095)(3002001)(3231254)(2018427008)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123558120)(20161123562045)(20161123560045)(6072148)(201708071742011); SRVR:DM5PR21MB0825; BCL:0; PCL:0; RULEID:; SRVR:DM5PR21MB0825; 
x-forefront-prvs: 0666E15D35
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(376002)(346002)(39380400002)(39860400002)(366004)(189003)(199004)(81156014)(6506007)(81166006)(86612001)(53546011)(3660700001)(486006)(446003)(53936002)(476003)(8990500004)(11346002)(186003)(10090500001)(2906002)(74316002)(46003)(316002)(561944003)(6246003)(8936002)(33656002)(3280700002)(22452003)(102836004)(6436002)(5660300001)(6346003)(8676002)(97736004)(59450400001)(25786009)(110136005)(106356001)(790700001)(105586002)(478600001)(229853002)(6116002)(14454004)(7696005)(54896002)(7736002)(55016002)(99286004)(6306002)(2501003)(236005)(10290500003)(76176011)(2900100001)(5250100002)(86362001)(68736007)(9686003); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR21MB0825; H:DM5PR21MB0857.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=briansw@microsoft.com; 
x-microsoft-antispam-message-info: Om3mJStN4Wwpy1Pshr7nZPECVUjm/VnDpAbdFxGRLsnOsHXO/QE/HSBRFkzHoyCyeBRQBbVuj2BXv9cM12RP85nvt9dq/X+zKSGxBd/PgZXsCHbmyPzEEaw4eZKIQvDinI8FmlVgSHn1yzjoMJjmaRC1oEjaj9ZXKccSaxz8rqTLjZ5uls7EWEJEHjaab6WN
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM5PR21MB08572BEFDA60C6EE920D0357B39A0DM5PR21MB0857namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: cec91eca-21c1-471b-35df-08d5b5254e7f
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: cec91eca-21c1-471b-35df-08d5b5254e7f
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 May 2018 20:50:17.6764 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR21MB0825
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/GkV8iLFvc28_1NvOkuA4hrKPFko>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2018 20:50:22 -0000

--_000_DM5PR21MB08572BEFDA60C6EE920D0357B39A0DM5PR21MB0857namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

T2YgY291cnNlIHNpbmdsZSBwYXNzIGlzbuKAmXQgcmVxdWlyZWQuICBCdXQgdGhlIFBvc3RCYXNl
IGlzIHRoZXJlIG9ubHkgdG8gc3VwcG9ydCBzaW5nbGUgcGFzcy4gIFNvIHRoZXJlIGFyZSBkZWZp
bml0ZWx5IChwcm9iYWJseSBmcmluZ2UpIGNhc2VzIHdoZXJlIHRoZSBlbmNvZGVkIHNpemUgd2ls
bCBiZSBsYXJnZXIgYmVjYXVzZSBvZiBQb3N0QmFzZS4NCg0KU28gSU1PLCBpdCBjb21lcyBkb3du
IHRvIHRoZSB0cmFkZW9mZiBvZiB0aGUgcG9zc2libGUgc3BlZWQgaW1wcm92ZW1lbnQgb2Ygc2lu
Z2xlIHBhc3MgdnMuIGNvbXByZXNzaW9uIHNpemUuICAgQW5kIEkganVzdCBkb27igJl0IHNlZSB0
aGUgc3BlZWQgb2YgdGhlIHNpbmdsZSBwYXNzIGJlaW5nIHZlcnkgY29tcGVsbGluZyBlaXRoZXIu
ICBGb3IgaW5zdGFuY2UsIHlvdSBjYW4gY2FjaGUgdGhlIGluZGljZXMsIGV0YyBmcm9tIHBhc3Mg
MSwgYW5kIGp1c3QgcXVpY2tseSBidXJuIHRocnUgdGhlIGFycmF5IGFnYWluIGVuY29kaW5nIHRo
ZSBpbmRpY2VzIGRldGVybWluZWQgZnJvbSBwYXNzIDEuDQoNClBlcnNvbmFsbHksIGdpdmVuIHRo
YXQgdGhlIHNwZWVkIGltcHJvdmVtZW50IG9mIHNpbmdsZSBwYXNzIGlzIHByb2JhYmx5IG1hcmdp
bmFsIGF0IGJlc3QsIEnigJlkIGVyciBvbiB0aGUgc2lkZSBvZiBsZXNzIGNvbXBsZXhpdHkg4oCT
IGFuZCBzbGlnaHRseSBiZXR0ZXIgY29tcHJlc3Npb24uDQoNCkJ1dCBJ4oCZbSBub3QgcGFzc2lv
bmF0ZSBhYm91dCB0aGlzIGlzc3VlLiAgIFNvIEnigJltIGZpbmUgd2l0aCB0aGUgY3VycmVudCBk
cmFmdCwgaWYgZXZlcnlvbmUgZWxzZSBsaWtlcyBpdC4gICBJIGp1c3QgcHJlZmVyIHNpbXBsaWNp
dHkgd2hlbiBpdCBzZWVtcyBsaWtlIGNvbXBsZXhpdHkgaXNu4oCZdCBidXlpbmcgdXMgbXVjaC4g
IEFuZCBpbiB0aGlzIGNhc2UsIHNpbXBsaWNpdHkgYWxzbyBnaXZlcyBzbGlnaHRseSBiZXR0ZXIg
Y29tcHJlc3Npb24uDQoNCmJzDQoNCkZyb206IEFsYW4gRnJpbmRlbGwgPGFmcmluZEBmYi5jb20+
DQpTZW50OiBUdWVzZGF5LCBNYXkgOCwgMjAxOCAxOjEzIFBNDQpUbzogQnJpYW4gU3dhbmRlciA8
YnJpYW5zd0BtaWNyb3NvZnQuY29tPjsgcXVpY0BpZXRmLm9yZw0KU3ViamVjdDogUmU6IFFQQUNL
IC0gcHJvcG9zYWwgdG8gb3B0aW1pemUgY29tcHJlc3Npb24NCg0KU2luZ2xlIHBhc3MgZW5jb2Rp
bmcgaXMgbm90IHJlcXVpcmVkLCBhbiBlbmNvZGVyIGhhcyB0aGUgb3B0aW9uIHRvIGVuY29kZSB1
c2luZyBvbmUgb3IgdHdvIHBhc3Nlcy4gIFRoZSBvbmx5IHdpcmUgcGVuYWx0eSBmb3IgYSB0d28t
cGFzcyBlbmNvZGVyIGlzIG9uZSBleHRyYSBieXRlIHBlciBoZWFkZXIgYmxvY2sgaW4gdGhlIHBy
ZWZpeCwgYXMgbGFyZ2VzdCByZWZlcmVuY2UgYW5kIGJhc2UgaW5kZXggY2FuIGJlIHRoZSBzYW1l
IGluIHR3by1wYXNzIGVuY29kaW5nLiAgVGhlIG9yaWdpbmFsIHNwZWNpZmljYXRpb24gKHdoaWNo
IHVzZWQgRGVwZW5kcykgaGFkIGEgb25lIGJpdCBmbGFnIGluIHRoZSBIVFRQIGZyYW1lIHRoYXQg
YWxsb3dlZCB0aGUgZW5jb2RlciBzYXZlIHRoaXMgYnl0ZSBhcyB3ZWxsLCBidXQgdGhlIGNvbnNl
bnN1cyBzZWVtZWQgdG8gYmUgaXQgd2FzIGJldHRlciB0byBoYXZlIGEgZml4ZWQgZm9ybWF0IHRv
IHRoZSBwcmVmaXguICBXaXRob3V0IHBvc3QtYmFzZSwgdGhlcmUgY291bGQgYWxzbyBiZSBvbmUg
bW9yZSBiaXQgYXZhaWxhYmxlIGZvciB0aGUgbGVuZ3RoIG9mIGEgbGl0ZXJhbCBoZWFkZXIgbmFt
ZSB3aXRob3V0IGFkZGluZyBhbiBleHRyYSBieXRlIChoZWFkZXIgbmFtZXMgd2l0aCA3IDw9IGxl
bmd0aCA8IDE1KS4gIFdlIGNhbiBvZiBjb3Vyc2Ugc2ltdWxhdGUgaXQsIGJ1dCBJIGV4cGVjdCB0
aGUgZGlmZmVyZW5jZSB0byBiZSBpbiB0aGUgbm9pc2UuDQoNCkRlY29kZXJzIGRvIG5lZWQgdG8g
c3VwcG9ydCBib3RoIGtpbmRzIG9mIGluc3RydWN0aW9ucywgYnV0IEkgZG9u4oCZdCBmaW5kIGl0
IHRvIGJlIHRlcnJpYmx5IGNvbXBsZXguICBUaGUgcHJveHlnZW4gaW1wbGVtZW50YXRpb24gb2Yg
dGhlIGxhdGVzdCBkcmFmdCBpbmNsdWRpbmcgb25lLXBhc3MgZW5jb2RpbmcvZGVjb2Rpbmcgc2hv
dWxkIGJlIHN5bmNlZCB0byBnaXRodWIgdGhpcyB3ZWVrLg0KDQpJ4oCZbSBub3Qgc3VyZSB3aGF0
IHlvdSBtZWFuIHdoZW4geW91IHNheSDigJxNYW55IG9mIHRoZSBoZWFkZXJzIGFyZSBnb2luZyB0
byBiZSBlbmNvZGVkIGluIGJvdGggc3RyZWFtcy7igJ0gIElmIHlvdSBtZWFuIGl0IHdpbGwgZW5j
b2RlIGFuIGluc2VydCBvbiB0aGUgY29udHJvbCBzdHJlYW0gYW5kIGFuIGluZGV4IHJlZmVyZW5j
ZSBvbiB0aGUgcmVxdWVzdCBzdHJlYW0sIHRoYXQgaXMgdHJ1ZSwgYW5kIHRoZSBwb3N0LWJhc2Ug
ZW5jb2Rpbmcgb2YgdGhlIHJlZmVyZW5jZXMgb2NjdXBpZXMgb25seSBvbmUgYnl0ZSBmb3IgdGhl
IGZpcnN0IDE1IHN1Y2ggaGVhZGVycyBwZXIgYmxvY2suDQoNCi1BbGFuDQoNCg0KRnJvbTogUVVJ
QyA8cXVpYy1ib3VuY2VzQGlldGYub3JnPG1haWx0bzpxdWljLWJvdW5jZXNAaWV0Zi5vcmc+PiBv
biBiZWhhbGYgb2YgQnJpYW4gU3dhbmRlciA8YnJpYW5zdz00MG1pY3Jvc29mdC5jb21AZG1hcmMu
aWV0Zi5vcmc8bWFpbHRvOmJyaWFuc3c9NDBtaWNyb3NvZnQuY29tQGRtYXJjLmlldGYub3JnPj4N
CkRhdGU6IE1vbmRheSwgTWF5IDcsIDIwMTggYXQgMjozNSBQTQ0KVG86ICJxdWljQGlldGYub3Jn
PG1haWx0bzpxdWljQGlldGYub3JnPiIgPHF1aWNAaWV0Zi5vcmc8bWFpbHRvOnF1aWNAaWV0Zi5v
cmc+Pg0KU3ViamVjdDogUVBBQ0sgLSBwcm9wb3NhbCB0byBvcHRpbWl6ZSBjb21wcmVzc2lvbg0K
DQpQbGVhc2UgY29ycmVjdCBtZSBpZiBJ4oCZbSB3cm9uZyBoZXJlLg0KDQpJdCBsb29rcyBsaWtl
IHRoZSBsYXRlc3QgUVBBQ0sgZHJhZnQgaGFzIGJlZW4gb3B0aW1pemVkIHRvIGFsbG93IGVuY29k
ZSBvZiBib3RoIGNvbnRyb2wgYW5kIGRhdGEgc3RyZWFtcyBpbiBhIHNpbmdsZSBwYXNzLg0KQmVj
YXVzZSBvZiB0aGlzLCB3ZSBub3cgbXVzdCBzdXBwb3J0IHRoYXQgcG9zdC1iYXNlIGVuY29kaW5n
LCBhbmQgdGhlIG11bHRpcGxlIGVuY29kaW5nIGZvcm1hdHMgdGhhdCB1c2UgUG9zdC1CYXNlLg0K
SS5lLiBMaXRlcmFsIEhlYWRlciBGaWVsZCB3aXRoIE5hbWUgUmVmZXJlbmNlIGFuZCBMaXRlcmFs
IEhlYWRlciBGaWx0ZXIgV2l0aCBQb3N0LUJhc2UgTmFtZSBSZWZlcmVuY2UsIGFuZCBzaW1pbGFy
bHkgZm9yIEluZGV4ZWQgSGVhZGVyIEZpZWxkLg0KDQpUbyBtZSwgaXQgc2VlbXMgbGlrZSB0aGUg
c2ltcGxlciwgbW9yZSBlZmZpY2llbnQgb3B0aW9uIG9mIHJlbW92aW5nIHBvc3QtYmFzZSBlbnRp
cmVseSBjb3VsZCBiZSBiZXR0ZXIuICAgQXQgdGhlIGNvc3Qgb2YgcmVxdWlyaW5nIDItcGFzcyBl
bmNvZGUsIHdlIGNhbiBzYXZlIGEgZmV3IGJpdHMgZm9yIG1vc3QgaGVhZGVycyBzaW5jZSB3ZSB3
b3VsZCBuZXZlciBuZWVkIHRoZSBwb3N0IGJhc2UgaGVhZGVyIHByZWZpeC4NCg0KU28gaXTigJlz
IGEgcXVlc3Rpb24gb2YgbG9vcGluZyB0aHJ1IHRoZSBoZWFkZXJzIHR3aWNlLCB2cy4gYmVpbmcg
bGVzcyBlZmZpY2llbnQgb24gdGhlIHdpcmUuDQoNCkkgaGF2ZW7igJl0IHByb2ZpbGVkIGl0LCBi
dXQgSeKAmWQgZ3Vlc3MgdGhhdCBkb3VibGUgcGFzcyB0aHJ1IHRoZSBoZWFkZXJzIGlzbuKAmXQg
Z29pbmcgdG8gYmUgdGhhdCBtdWNoIHNsb3dlciB0aGFuIHNpbmdsZSBwYXNzLiAgIE1hbnkgb2Yg
dGhlIGhlYWRlcnMgYXJlIGdvaW5nIHRvIGJlIGVuY29kZWQgaW4gYm90aCBzdHJlYW1zLiAgIFNv
IHRoZSBtb3JlIGVmZmljaWVudCB3aXJlIGZvcm1hdCBtYXkgYmUgbW9yZSBvcHRpbWFsLg0KDQpi
cw0K

--_000_DM5PR21MB08572BEFDA60C6EE920D0357B39A0DM5PR21MB0857namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQph
OmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xv
cjojMDU2M0MxOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFu
Lk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjoj
OTU0RjcyOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5tc29ub3JtYWwwLCBsaS5t
c29ub3JtYWwwLCBkaXYubXNvbm9ybWFsMA0KCXttc28tc3R5bGUtbmFtZTptc29ub3JtYWw7DQoJ
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBpbjsNCgltc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowaW47DQoJZm9udC1zaXplOjExLjBwdDsN
Cglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpzcGFuLkVtYWlsU3R5bGUxOA0K
CXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1z
ZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0Ow0KCWZvbnQtd2VpZ2h0Om5vcm1hbDsNCglmb250LXN0
eWxlOm5vcm1hbDt9DQpzcGFuLkVtYWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25h
bDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0
O30NCnNwYW4uRW1haWxTdHlsZTIxDQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0K
CWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0K
Lk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXpl
OjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFy
Z2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpX
b3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNo
YXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRp
Zl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0
Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0Pjwv
eG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9IiMwNTYz
QzEiIHZsaW5rPSIjOTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5PZiBjb3Vyc2Ugc2luZ2xlIHBhc3MgaXNu4oCZdCByZXF1aXJlZC4mbmJz
cDsgQnV0IHRoZSBQb3N0QmFzZSBpcyB0aGVyZSBvbmx5IHRvIHN1cHBvcnQgc2luZ2xlIHBhc3Mu
Jm5ic3A7IFNvIHRoZXJlIGFyZSBkZWZpbml0ZWx5IChwcm9iYWJseSBmcmluZ2UpIGNhc2VzIHdo
ZXJlIHRoZSBlbmNvZGVkIHNpemUgd2lsbCBiZSBsYXJnZXIgYmVjYXVzZSBvZiBQb3N0QmFzZS48
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U28gSU1PLCBpdCBjb21lcyBkb3duIHRvIHRoZSB0cmFk
ZW9mZiBvZiB0aGUgcG9zc2libGUgc3BlZWQgaW1wcm92ZW1lbnQgb2Ygc2luZ2xlIHBhc3MgdnMu
IGNvbXByZXNzaW9uIHNpemUuJm5ic3A7Jm5ic3A7IEFuZCBJIGp1c3QgZG9u4oCZdCBzZWUgdGhl
IHNwZWVkIG9mIHRoZSBzaW5nbGUgcGFzcyBiZWluZyB2ZXJ5IGNvbXBlbGxpbmcgZWl0aGVyLiZu
YnNwOyBGb3IgaW5zdGFuY2UsIHlvdSBjYW4gY2FjaGUgdGhlIGluZGljZXMsIGV0Yw0KIGZyb20g
cGFzcyAxLCBhbmQganVzdCBxdWlja2x5IGJ1cm4gdGhydSB0aGUgYXJyYXkgYWdhaW4gZW5jb2Rp
bmcgdGhlIGluZGljZXMgZGV0ZXJtaW5lZCBmcm9tIHBhc3MgMS48bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+UGVyc29uYWxseSwgZ2l2ZW4gdGhhdCB0aGUgc3BlZWQgaW1wcm92ZW1lbnQgb2Ygc2lu
Z2xlIHBhc3MgaXMgcHJvYmFibHkgbWFyZ2luYWwgYXQgYmVzdCwgSeKAmWQgZXJyIG9uIHRoZSBz
aWRlIG9mIGxlc3MgY29tcGxleGl0eSDigJMgYW5kIHNsaWdodGx5IGJldHRlciBjb21wcmVzc2lv
bi48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QnV0IEnigJltIG5vdCBwYXNzaW9uYXRlIGFib3V0
IHRoaXMgaXNzdWUuJm5ic3A7ICZuYnNwO1NvIEnigJltIGZpbmUgd2l0aCB0aGUgY3VycmVudCBk
cmFmdCwgaWYgZXZlcnlvbmUgZWxzZSBsaWtlcyBpdC4mbmJzcDsgJm5ic3A7SSBqdXN0IHByZWZl
ciBzaW1wbGljaXR5IHdoZW4gaXQgc2VlbXMgbGlrZSBjb21wbGV4aXR5IGlzbuKAmXQgYnV5aW5n
IHVzIG11Y2guJm5ic3A7IEFuZCBpbiB0aGlzIGNhc2UsIHNpbXBsaWNpdHkgYWxzbyBnaXZlcyBz
bGlnaHRseSBiZXR0ZXINCiBjb21wcmVzc2lvbi48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+YnM8
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFF
MSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxiPkZyb206PC9iPiBBbGFuIEZyaW5kZWxsICZsdDthZnJpbmRAZmIuY29tJmd0OyA8YnI+DQo8
Yj5TZW50OjwvYj4gVHVlc2RheSwgTWF5IDgsIDIwMTggMToxMyBQTTxicj4NCjxiPlRvOjwvYj4g
QnJpYW4gU3dhbmRlciAmbHQ7YnJpYW5zd0BtaWNyb3NvZnQuY29tJmd0OzsgcXVpY0BpZXRmLm9y
Zzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogUVBBQ0sgLSBwcm9wb3NhbCB0byBvcHRpbWl6ZSBj
b21wcmVzc2lvbjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U2luZ2xl
IHBhc3MgZW5jb2RpbmcgaXMgbm90IHJlcXVpcmVkLCBhbiBlbmNvZGVyIGhhcyB0aGUgb3B0aW9u
IHRvIGVuY29kZSB1c2luZyBvbmUgb3IgdHdvIHBhc3Nlcy4mbmJzcDsgVGhlIG9ubHkgd2lyZSBw
ZW5hbHR5IGZvciBhIHR3by1wYXNzIGVuY29kZXIgaXMgb25lIGV4dHJhIGJ5dGUgcGVyIGhlYWRl
ciBibG9jayBpbiB0aGUgcHJlZml4LCBhcyBsYXJnZXN0IHJlZmVyZW5jZSBhbmQgYmFzZSBpbmRl
eCBjYW4gYmUNCiB0aGUgc2FtZSBpbiB0d28tcGFzcyBlbmNvZGluZy4mbmJzcDsgVGhlIG9yaWdp
bmFsIHNwZWNpZmljYXRpb24gKHdoaWNoIHVzZWQgRGVwZW5kcykgaGFkIGEgb25lIGJpdCBmbGFn
IGluIHRoZSBIVFRQIGZyYW1lIHRoYXQgYWxsb3dlZCB0aGUgZW5jb2RlciBzYXZlIHRoaXMgYnl0
ZSBhcyB3ZWxsLCBidXQgdGhlIGNvbnNlbnN1cyBzZWVtZWQgdG8gYmUgaXQgd2FzIGJldHRlciB0
byBoYXZlIGEgZml4ZWQgZm9ybWF0IHRvIHRoZSBwcmVmaXguJm5ic3A7IFdpdGhvdXQNCiBwb3N0
LWJhc2UsIHRoZXJlIGNvdWxkIGFsc28gYmUgb25lIG1vcmUgYml0IGF2YWlsYWJsZSBmb3IgdGhl
IGxlbmd0aCBvZiBhIGxpdGVyYWwgaGVhZGVyIG5hbWUgd2l0aG91dCBhZGRpbmcgYW4gZXh0cmEg
Ynl0ZSAoaGVhZGVyIG5hbWVzIHdpdGggNyAmbHQ7PSBsZW5ndGggJmx0OyAxNSkuJm5ic3A7IFdl
IGNhbiBvZiBjb3Vyc2Ugc2ltdWxhdGUgaXQsIGJ1dCBJIGV4cGVjdCB0aGUgZGlmZmVyZW5jZSB0
byBiZSBpbiB0aGUgbm9pc2UuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkRlY29kZXJzIGRvIG5l
ZWQgdG8gc3VwcG9ydCBib3RoIGtpbmRzIG9mIGluc3RydWN0aW9ucywgYnV0IEkgZG9u4oCZdCBm
aW5kIGl0IHRvIGJlIHRlcnJpYmx5IGNvbXBsZXguJm5ic3A7IFRoZSBwcm94eWdlbiBpbXBsZW1l
bnRhdGlvbiBvZiB0aGUgbGF0ZXN0IGRyYWZ0IGluY2x1ZGluZyBvbmUtcGFzcyBlbmNvZGluZy9k
ZWNvZGluZyBzaG91bGQgYmUgc3luY2VkIHRvIGdpdGh1YiB0aGlzIHdlZWsuPG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPknigJltIG5vdCBzdXJlIHdoYXQgeW91IG1lYW4gd2hlbiB5b3Ugc2F5IOKA
nE1hbnkgb2YgdGhlIGhlYWRlcnMgYXJlIGdvaW5nIHRvIGJlIGVuY29kZWQgaW4gYm90aCBzdHJl
YW1zLuKAnSZuYnNwOyBJZiB5b3UgbWVhbiBpdCB3aWxsIGVuY29kZSBhbiBpbnNlcnQgb24gdGhl
IGNvbnRyb2wgc3RyZWFtIGFuZCBhbiBpbmRleCByZWZlcmVuY2Ugb24gdGhlIHJlcXVlc3Qgc3Ry
ZWFtLCB0aGF0IGlzIHRydWUsIGFuZCB0aGUgcG9zdC1iYXNlDQogZW5jb2Rpbmcgb2YgdGhlIHJl
ZmVyZW5jZXMgb2NjdXBpZXMgb25seSBvbmUgYnl0ZSBmb3IgdGhlIGZpcnN0IDE1IHN1Y2ggaGVh
ZGVycyBwZXIgYmxvY2suPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi1BbGFuPG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5v
bmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAw
aW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4w
cHQ7Y29sb3I6YmxhY2siPkZyb206IDwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
Mi4wcHQ7Y29sb3I6YmxhY2siPlFVSUMgJmx0OzxhIGhyZWY9Im1haWx0bzpxdWljLWJvdW5jZXNA
aWV0Zi5vcmciPnF1aWMtYm91bmNlc0BpZXRmLm9yZzwvYT4mZ3Q7IG9uIGJlaGFsZiBvZiBCcmlh
biBTd2FuZGVyICZsdDs8YSBocmVmPSJtYWlsdG86YnJpYW5zdz00MG1pY3Jvc29mdC5jb21AZG1h
cmMuaWV0Zi5vcmciPmJyaWFuc3c9NDBtaWNyb3NvZnQuY29tQGRtYXJjLmlldGYub3JnPC9hPiZn
dDs8YnI+DQo8Yj5EYXRlOiA8L2I+TW9uZGF5LCBNYXkgNywgMjAxOCBhdCAyOjM1IFBNPGJyPg0K
PGI+VG86IDwvYj4mcXVvdDs8YSBocmVmPSJtYWlsdG86cXVpY0BpZXRmLm9yZyI+cXVpY0BpZXRm
Lm9yZzwvYT4mcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpxdWljQGlldGYub3JnIj5xdWljQGll
dGYub3JnPC9hPiZndDs8YnI+DQo8Yj5TdWJqZWN0OiA8L2I+UVBBQ0sgLSBwcm9wb3NhbCB0byBv
cHRpbWl6ZSBjb21wcmVzc2lvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48YSBuYW1lPSJfTWFpbE9yaWdpbmFsQm9keSI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMi4wcHQiPlBsZWFzZSBjb3JyZWN0IG1lIGlmIEnigJltIHdyb25nIGhlcmUu
PC9zcGFuPjxvOnA+PC9vOnA+PC9hPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTIuMHB0Ij4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQiPkl0IGxvb2tzIGxpa2UgdGhlIGxhdGVzdCBR
UEFDSyBkcmFmdCBoYXMgYmVlbiBvcHRpbWl6ZWQgdG8gYWxsb3cgZW5jb2RlIG9mIGJvdGggY29u
dHJvbCBhbmQgZGF0YSBzdHJlYW1zIGluIGEgc2luZ2xlIHBhc3MuPC9zcGFuPjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21h
cms6X01haWxPcmlnaW5hbEJvZHkiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0Ij5CZWNh
dXNlIG9mIHRoaXMsIHdlIG5vdyBtdXN0IHN1cHBvcnQgdGhhdCBwb3N0LWJhc2UgZW5jb2Rpbmcs
IGFuZCB0aGUgbXVsdGlwbGUgZW5jb2RpbmcgZm9ybWF0cyB0aGF0IHVzZSBQb3N0LUJhc2UuPC9z
cGFuPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTIuMHB0Ij5JLmUuIExpdGVyYWwgSGVhZGVyIEZpZWxkIHdpdGggTmFtZSBSZWZlcmVuY2Ug
YW5kIExpdGVyYWwgSGVhZGVyIEZpbHRlciBXaXRoIFBvc3QtQmFzZSBOYW1lIFJlZmVyZW5jZSwg
YW5kIHNpbWlsYXJseSBmb3IgSW5kZXhlZCBIZWFkZXIgRmllbGQuPC9zcGFuPjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21h
cms6X01haWxPcmlnaW5hbEJvZHkiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0Ij4mbmJz
cDs8L3NwYW4+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+PHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZToxMi4wcHQiPlRvIG1lLCBpdCBzZWVtcyBsaWtlIHRoZSBzaW1wbGVyLCBtb3JlIGVm
ZmljaWVudCBvcHRpb24gb2YgcmVtb3ZpbmcgcG9zdC1iYXNlIGVudGlyZWx5IGNvdWxkIGJlIGJl
dHRlci4mbmJzcDsmbmJzcDsgQXQgdGhlIGNvc3Qgb2YgcmVxdWlyaW5nIDItcGFzcyBlbmNvZGUs
IHdlIGNhbiBzYXZlIGENCiBmZXcgYml0cyBmb3IgbW9zdCBoZWFkZXJzIHNpbmNlIHdlIHdvdWxk
IG5ldmVyIG5lZWQgdGhlIHBvc3QgYmFzZSBoZWFkZXIgcHJlZml4LiZuYnNwOyZuYnNwOw0KPC9z
cGFuPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6MTIuMHB0Ij4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQiPlNvIGl04oCZcyBhIHF1ZXN0aW9uIG9mIGxv
b3BpbmcgdGhydSB0aGUgaGVhZGVycyB0d2ljZSwgdnMuIGJlaW5nIGxlc3MgZWZmaWNpZW50IG9u
IHRoZSB3aXJlLjwvc3Bhbj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjEyLjBwdCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxP
cmlnaW5hbEJvZHkiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0Ij5JIGhhdmVu4oCZdCBw
cm9maWxlZCBpdCwgYnV0IEnigJlkIGd1ZXNzIHRoYXQgZG91YmxlIHBhc3MgdGhydSB0aGUgaGVh
ZGVycyBpc27igJl0IGdvaW5nIHRvIGJlIHRoYXQgbXVjaCBzbG93ZXIgdGhhbiBzaW5nbGUgcGFz
cy4gJm5ic3A7Jm5ic3A7TWFueSBvZiB0aGUgaGVhZGVycyBhcmUgZ29pbmcgdG8gYmUNCiBlbmNv
ZGVkIGluIGJvdGggc3RyZWFtcy4mbmJzcDsmbmJzcDsgU28gdGhlIG1vcmUgZWZmaWNpZW50IHdp
cmUgZm9ybWF0IG1heSBiZSBtb3JlIG9wdGltYWwuPC9zcGFuPjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxP
cmlnaW5hbEJvZHkiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0Ij4mbmJzcDs8L3NwYW4+
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
Mi4wcHQiPmJzPC9zcGFuPjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9ib2R5Pg0K
PC9odG1sPg0K

--_000_DM5PR21MB08572BEFDA60C6EE920D0357B39A0DM5PR21MB0857namp_--


From nobody Tue May  8 14:58:00 2018
Return-Path: <mbishop@evequefou.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B10EB12D7E6 for <quic@ietfa.amsl.com>; Tue,  8 May 2018 14:57:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 TCQoJVTtF5fJ for <quic@ietfa.amsl.com>; Tue,  8 May 2018 14:57:56 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0097.outbound.protection.outlook.com [104.47.38.97]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 57F9B12EAE9 for <quic@ietf.org>; Tue,  8 May 2018 14:57:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=6Kb7IlfSURHmkn5xWMS6jX41cgnTxuJ9ZVnZWJrAXDI=; b=It9A6dRYljM/3baiOYlgFDhYmrK5xP5XZfS6P4BOqgfma35JLToumTB9Vw2aornkVa399xNssrbinVmCw6VmyS084sxAlL9DTPlGsv5g1bn/3uUXEbmqFJFA6j0++dRjtlnoH/kQVkXlr6Lnk3DfV9Y5GzM+Tad8UmuM5fwQieg=
Received: from SN1PR08MB1854.namprd08.prod.outlook.com (10.169.39.8) by SN1PR08MB1758.namprd08.prod.outlook.com (10.162.134.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.735.16; Tue, 8 May 2018 21:57:52 +0000
Received: from SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d]) by SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d%13]) with mapi id 15.20.0735.018; Tue, 8 May 2018 21:57:52 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Brian Swander <briansw=40microsoft.com@dmarc.ietf.org>, Alan Frindell <afrind@fb.com>, "quic@ietf.org" <quic@ietf.org>
Subject: RE: QPACK - proposal to optimize compression
Thread-Topic: QPACK - proposal to optimize compression
Thread-Index: AdPmSVy6766G9sm1TzOdAr1rcH/nrAAhOhQAAA++e/AAAjyFUA==
Date: Tue, 8 May 2018 21:57:52 +0000
Message-ID: <SN1PR08MB18544B4959E9E21B5F1CF578DA9A0@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <DM5PR21MB0857F41DCB080F130E1436ADB39B0@DM5PR21MB0857.namprd21.prod.outlook.com> <BCF18407-B5DD-4608-ACFE-C229E17A2C1B@fb.com> <DM5PR21MB08572BEFDA60C6EE920D0357B39A0@DM5PR21MB0857.namprd21.prod.outlook.com>
In-Reply-To: <DM5PR21MB08572BEFDA60C6EE920D0357B39A0@DM5PR21MB0857.namprd21.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2601:600:8080:5a28:5004:e201:a5af:9d41]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN1PR08MB1758; 7:XTe5OWE8Ddcxyau5azstifeclOKykgxp5zbeq5Fq2zhwzpgcJXG0r5hpLZcGKYACiGdr0WNMEGYmz/olag4kRn/k1uFTFRKbRUgQmXR0mwLxEyOo/SMJgvd1cWjaocEZcTbkEiRh7YjGkZYpeGQL8bVltyuaz1geYqeQnv2Oexr0YIyk58oy1AWonv2Z58mt314LQVIKzrG7fk6TOCLGuYtMuILuzBoGatC+8KGaTf6hIGIUQVwjedRZvK/vJAM9
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(5600026)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(2017052603328)(7153060)(7193020); SRVR:SN1PR08MB1758; 
x-ms-traffictypediagnostic: SN1PR08MB1758:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-microsoft-antispam-prvs: <SN1PR08MB1758145FC2E8FED2AFC32F3EDA9A0@SN1PR08MB1758.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(89211679590171)(67672495146484)(100405760836317)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(3231254)(944501410)(52105095)(93006095)(93001095)(3002001)(10201501046)(149027)(150027)(6041310)(20161123564045)(20161123560045)(2016111802025)(20161123558120)(20161123562045)(6043046)(6072148)(201708071742011); SRVR:SN1PR08MB1758; BCL:0; PCL:0; RULEID:; SRVR:SN1PR08MB1758; 
x-forefront-prvs: 0666E15D35
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(39380400002)(366004)(39830400003)(396003)(376002)(199004)(189003)(790700001)(97736004)(74316002)(3660700001)(6116002)(81156014)(99286004)(229853002)(45080400002)(86362001)(8936002)(3280700002)(25786009)(5250100002)(8676002)(76176011)(74482002)(2906002)(6436002)(7736002)(5660300001)(7696005)(2900100001)(81166006)(6506007)(6246003)(2501003)(53546011)(476003)(478600001)(14454004)(561944003)(102836004)(106356001)(11346002)(186003)(110136005)(105586002)(9686003)(236005)(446003)(53936002)(59450400001)(55016002)(68736007)(486006)(46003)(33656002)(316002)(6306002)(54896002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR08MB1758; H:SN1PR08MB1854.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: jCWngTiBB/jetftHRaLtXgoxZ+jjoM3Vc3gERTeJSC0Wq16dXmACwQuF3iG7AAy+cUlg3jH9yriWvWBS023mxQ0BfBFMtofh6iwHcVcqbzSk1VA5YNdt6We8D/Qk+vBryEazLx1bDwwH16uKfT/zyfYGu4fKygQcufLJjdpR8uvyFS0uLeedqbIOzi0TFnZE
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_SN1PR08MB18544B4959E9E21B5F1CF578DA9A0SN1PR08MB1854namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 74ede924-8cec-45f5-9424-08d5b52ebf8a
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 74ede924-8cec-45f5-9424-08d5b52ebf8a
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 May 2018 21:57:52.8508 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR08MB1758
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/SRmsYgcKA3sutuVkuTuwbc_5eGY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 08 May 2018 21:58:00 -0000

--_000_SN1PR08MB18544B4959E9E21B5F1CF578DA9A0SN1PR08MB1854namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

VGhpcyBpcyBwYXJ0IG9mIHdoeSBJIGRpZG7igJl0IGF0dGVtcHQgdG8gbWVyZ2UgQWxhbuKAmXMg
cG9zdC1iYXNlIGRlc2lnbiBpbnRvICMxMTQxLCBidXQgbGVmdCBpdCBhcyBhIHNlcGFyYXRlIFBS
LiAgVGhhdCBoZWxwcyB0byBpZGVudGlmeSBleGFjdGx5IHdoaWNoIGluc3RydWN0aW9ucyBoYXZl
IGJlZW4gZGVncmFkZWQgYnkgYWRkaW5nIHRoZXNlIHR3byBhZGRpdGlvbmFsIGluc3RydWN0aW9u
cy4gIFRoZSBpbXBhY3QgdHVybmVkIG91dCB0byBiZToNCg0KICAqICAg4oCcRGVwZW5kc+KAnSB3
YXMgcmVzdXJyZWN0ZWQgZnJvbSB0aGUgZGVhZCwgb25lIGJ5dGUgcGVyIGhlYWRlciBibG9jaw0K
ICAqICAgTGl0ZXJhbCBoZWFkZXJzIHdpdGhvdXQgbmFtZSByZWZlcmVuY2VzIG5vdyByZXF1aXJl
IG9uZSBtb3JlIGJ5dGUgZm9yIG5hbWVzIHdoaWNoIGFyZSA3LTE1IG9jdGV0cyBsb25nDQoNCldo
aWxlIHRoZSBpbXBhY3QgaXMgY2VydGFpbmx5IG5vdCBub24temVybywgdGhpcyBzZWVtcyBmYWly
bHkgY29udGFpbmVkLiAgSSBkb27igJl0IGhhdmUgYSBwcm9ibGVtIHdpdGggdHdvLXBhc3MgZW5j
b2Rpbmcg4oCTIHRoYXQgd2FzIGFjdHVhbGx5IG15IG9yaWdpbmFsIGRlc2lnbiwgYW5kIEkgc3Rp
bGwgdGhpbmsgaXQgbWFrZXMgYSBsb3Qgb2Ygc2Vuc2UuICBCdXQgcGFydCBvZiB0aGUgY29uc2Vu
c3VzIGF0IHRoZSBTZWF0dGxlIGludGVyaW0gd2FzIHRoYXQgd2Ugd2FudCB0byBhbGxvdyB0aGUg
aW50ZWxsaWdlbmNlIGFuZCBjaG9pY2VzIHRvIGxpdmUgaW4gdGhlIGVuY29kZXIsIGFuZCBJIHNl
ZSBwZXJtaXR0aW5nIHRoZSBlbmNvZGVyIHRvIGNob29zZSBzaW5nbGUtcGFzcyB2ZXJzdXMgZG91
YmxlLXBhc3MgYXMgYW4gZXhhbXBsZSBvZiB0aGF0Lg0KDQpBbHNvLCBkb3VibGUtcGFzcyBoYXMg
aXRzIG93biBwb3RlbnRpYWwgcGl0ZmFsbHMg4oCTIG5vdGluZyB0aGF0IHlvdeKAmWxsIHJlZmVy
IHRvIGFuIGVudHJ5IHdoaWNoIGlzIGluIHRoZSBkeW5hbWljIHRhYmxlIGR1cmluZyB5b3VyIGZp
cnN0IHBhc3MsIGJ1dCB0aGVuIGRpc2NvdmVyaW5nIHRoYXQgZW50cnkgaGFzIGJlZW4gcHVzaGVk
IG91dCBkdWUgdG8gaW5zZXJ0aW9ucyB3aGVuIHlvdSB0cnkgdG8gYWN0dWFsbHkgcmVmZXJlbmNl
IGl0IG9uIHRoZSBzZWNvbmQgcGFzcywgZm9yIGV4YW1wbGUuICBUaGVyZSBhcmUgbWl0aWdhdGlv
bnMgZm9yIHRoZXNlLCBvZiBjb3Vyc2UsIGJ1dCBJIGRvbuKAmXQgc2VlIGVpdGhlciBhcyBkcmFt
YXRpY2FsbHkgc2ltcGxlciB0aGFuIHRoZSBvdGhlci4NCg0KRnJvbTogUVVJQyA8cXVpYy1ib3Vu
Y2VzQGlldGYub3JnPiBPbiBCZWhhbGYgT2YgQnJpYW4gU3dhbmRlcg0KU2VudDogVHVlc2RheSwg
TWF5IDgsIDIwMTggMTo1MCBQTQ0KVG86IEFsYW4gRnJpbmRlbGwgPGFmcmluZEBmYi5jb20+OyBx
dWljQGlldGYub3JnDQpTdWJqZWN0OiBSRTogUVBBQ0sgLSBwcm9wb3NhbCB0byBvcHRpbWl6ZSBj
b21wcmVzc2lvbg0KDQpPZiBjb3Vyc2Ugc2luZ2xlIHBhc3MgaXNu4oCZdCByZXF1aXJlZC4gIEJ1
dCB0aGUgUG9zdEJhc2UgaXMgdGhlcmUgb25seSB0byBzdXBwb3J0IHNpbmdsZSBwYXNzLiAgU28g
dGhlcmUgYXJlIGRlZmluaXRlbHkgKHByb2JhYmx5IGZyaW5nZSkgY2FzZXMgd2hlcmUgdGhlIGVu
Y29kZWQgc2l6ZSB3aWxsIGJlIGxhcmdlciBiZWNhdXNlIG9mIFBvc3RCYXNlLg0KDQpTbyBJTU8s
IGl0IGNvbWVzIGRvd24gdG8gdGhlIHRyYWRlb2ZmIG9mIHRoZSBwb3NzaWJsZSBzcGVlZCBpbXBy
b3ZlbWVudCBvZiBzaW5nbGUgcGFzcyB2cy4gY29tcHJlc3Npb24gc2l6ZS4gICBBbmQgSSBqdXN0
IGRvbuKAmXQgc2VlIHRoZSBzcGVlZCBvZiB0aGUgc2luZ2xlIHBhc3MgYmVpbmcgdmVyeSBjb21w
ZWxsaW5nIGVpdGhlci4gIEZvciBpbnN0YW5jZSwgeW91IGNhbiBjYWNoZSB0aGUgaW5kaWNlcywg
ZXRjIGZyb20gcGFzcyAxLCBhbmQganVzdCBxdWlja2x5IGJ1cm4gdGhydSB0aGUgYXJyYXkgYWdh
aW4gZW5jb2RpbmcgdGhlIGluZGljZXMgZGV0ZXJtaW5lZCBmcm9tIHBhc3MgMS4NCg0KUGVyc29u
YWxseSwgZ2l2ZW4gdGhhdCB0aGUgc3BlZWQgaW1wcm92ZW1lbnQgb2Ygc2luZ2xlIHBhc3MgaXMg
cHJvYmFibHkgbWFyZ2luYWwgYXQgYmVzdCwgSeKAmWQgZXJyIG9uIHRoZSBzaWRlIG9mIGxlc3Mg
Y29tcGxleGl0eSDigJMgYW5kIHNsaWdodGx5IGJldHRlciBjb21wcmVzc2lvbi4NCg0KQnV0IEni
gJltIG5vdCBwYXNzaW9uYXRlIGFib3V0IHRoaXMgaXNzdWUuICAgU28gSeKAmW0gZmluZSB3aXRo
IHRoZSBjdXJyZW50IGRyYWZ0LCBpZiBldmVyeW9uZSBlbHNlIGxpa2VzIGl0LiAgIEkganVzdCBw
cmVmZXIgc2ltcGxpY2l0eSB3aGVuIGl0IHNlZW1zIGxpa2UgY29tcGxleGl0eSBpc27igJl0IGJ1
eWluZyB1cyBtdWNoLiAgQW5kIGluIHRoaXMgY2FzZSwgc2ltcGxpY2l0eSBhbHNvIGdpdmVzIHNs
aWdodGx5IGJldHRlciBjb21wcmVzc2lvbi4NCg0KYnMNCg0KRnJvbTogQWxhbiBGcmluZGVsbCA8
YWZyaW5kQGZiLmNvbTxtYWlsdG86YWZyaW5kQGZiLmNvbT4+DQpTZW50OiBUdWVzZGF5LCBNYXkg
OCwgMjAxOCAxOjEzIFBNDQpUbzogQnJpYW4gU3dhbmRlciA8YnJpYW5zd0BtaWNyb3NvZnQuY29t
PG1haWx0bzpicmlhbnN3QG1pY3Jvc29mdC5jb20+PjsgcXVpY0BpZXRmLm9yZzxtYWlsdG86cXVp
Y0BpZXRmLm9yZz4NClN1YmplY3Q6IFJlOiBRUEFDSyAtIHByb3Bvc2FsIHRvIG9wdGltaXplIGNv
bXByZXNzaW9uDQoNClNpbmdsZSBwYXNzIGVuY29kaW5nIGlzIG5vdCByZXF1aXJlZCwgYW4gZW5j
b2RlciBoYXMgdGhlIG9wdGlvbiB0byBlbmNvZGUgdXNpbmcgb25lIG9yIHR3byBwYXNzZXMuICBU
aGUgb25seSB3aXJlIHBlbmFsdHkgZm9yIGEgdHdvLXBhc3MgZW5jb2RlciBpcyBvbmUgZXh0cmEg
Ynl0ZSBwZXIgaGVhZGVyIGJsb2NrIGluIHRoZSBwcmVmaXgsIGFzIGxhcmdlc3QgcmVmZXJlbmNl
IGFuZCBiYXNlIGluZGV4IGNhbiBiZSB0aGUgc2FtZSBpbiB0d28tcGFzcyBlbmNvZGluZy4gIFRo
ZSBvcmlnaW5hbCBzcGVjaWZpY2F0aW9uICh3aGljaCB1c2VkIERlcGVuZHMpIGhhZCBhIG9uZSBi
aXQgZmxhZyBpbiB0aGUgSFRUUCBmcmFtZSB0aGF0IGFsbG93ZWQgdGhlIGVuY29kZXIgc2F2ZSB0
aGlzIGJ5dGUgYXMgd2VsbCwgYnV0IHRoZSBjb25zZW5zdXMgc2VlbWVkIHRvIGJlIGl0IHdhcyBi
ZXR0ZXIgdG8gaGF2ZSBhIGZpeGVkIGZvcm1hdCB0byB0aGUgcHJlZml4LiAgV2l0aG91dCBwb3N0
LWJhc2UsIHRoZXJlIGNvdWxkIGFsc28gYmUgb25lIG1vcmUgYml0IGF2YWlsYWJsZSBmb3IgdGhl
IGxlbmd0aCBvZiBhIGxpdGVyYWwgaGVhZGVyIG5hbWUgd2l0aG91dCBhZGRpbmcgYW4gZXh0cmEg
Ynl0ZSAoaGVhZGVyIG5hbWVzIHdpdGggNyA8PSBsZW5ndGggPCAxNSkuICBXZSBjYW4gb2YgY291
cnNlIHNpbXVsYXRlIGl0LCBidXQgSSBleHBlY3QgdGhlIGRpZmZlcmVuY2UgdG8gYmUgaW4gdGhl
IG5vaXNlLg0KDQpEZWNvZGVycyBkbyBuZWVkIHRvIHN1cHBvcnQgYm90aCBraW5kcyBvZiBpbnN0
cnVjdGlvbnMsIGJ1dCBJIGRvbuKAmXQgZmluZCBpdCB0byBiZSB0ZXJyaWJseSBjb21wbGV4LiAg
VGhlIHByb3h5Z2VuIGltcGxlbWVudGF0aW9uIG9mIHRoZSBsYXRlc3QgZHJhZnQgaW5jbHVkaW5n
IG9uZS1wYXNzIGVuY29kaW5nL2RlY29kaW5nIHNob3VsZCBiZSBzeW5jZWQgdG8gZ2l0aHViIHRo
aXMgd2Vlay4NCg0KSeKAmW0gbm90IHN1cmUgd2hhdCB5b3UgbWVhbiB3aGVuIHlvdSBzYXkg4oCc
TWFueSBvZiB0aGUgaGVhZGVycyBhcmUgZ29pbmcgdG8gYmUgZW5jb2RlZCBpbiBib3RoIHN0cmVh
bXMu4oCdICBJZiB5b3UgbWVhbiBpdCB3aWxsIGVuY29kZSBhbiBpbnNlcnQgb24gdGhlIGNvbnRy
b2wgc3RyZWFtIGFuZCBhbiBpbmRleCByZWZlcmVuY2Ugb24gdGhlIHJlcXVlc3Qgc3RyZWFtLCB0
aGF0IGlzIHRydWUsIGFuZCB0aGUgcG9zdC1iYXNlIGVuY29kaW5nIG9mIHRoZSByZWZlcmVuY2Vz
IG9jY3VwaWVzIG9ubHkgb25lIGJ5dGUgZm9yIHRoZSBmaXJzdCAxNSBzdWNoIGhlYWRlcnMgcGVy
IGJsb2NrLg0KDQotQWxhbg0KDQoNCkZyb206IFFVSUMgPHF1aWMtYm91bmNlc0BpZXRmLm9yZzxt
YWlsdG86cXVpYy1ib3VuY2VzQGlldGYub3JnPj4gb24gYmVoYWxmIG9mIEJyaWFuIFN3YW5kZXIg
PGJyaWFuc3c9NDBtaWNyb3NvZnQuY29tQGRtYXJjLmlldGYub3JnPG1haWx0bzpicmlhbnN3PTQw
bWljcm9zb2Z0LmNvbUBkbWFyYy5pZXRmLm9yZz4+DQpEYXRlOiBNb25kYXksIE1heSA3LCAyMDE4
IGF0IDI6MzUgUE0NClRvOiAicXVpY0BpZXRmLm9yZzxtYWlsdG86cXVpY0BpZXRmLm9yZz4iIDxx
dWljQGlldGYub3JnPG1haWx0bzpxdWljQGlldGYub3JnPj4NClN1YmplY3Q6IFFQQUNLIC0gcHJv
cG9zYWwgdG8gb3B0aW1pemUgY29tcHJlc3Npb24NCg0KUGxlYXNlIGNvcnJlY3QgbWUgaWYgSeKA
mW0gd3JvbmcgaGVyZS4NCg0KSXQgbG9va3MgbGlrZSB0aGUgbGF0ZXN0IFFQQUNLIGRyYWZ0IGhh
cyBiZWVuIG9wdGltaXplZCB0byBhbGxvdyBlbmNvZGUgb2YgYm90aCBjb250cm9sIGFuZCBkYXRh
IHN0cmVhbXMgaW4gYSBzaW5nbGUgcGFzcy4NCkJlY2F1c2Ugb2YgdGhpcywgd2Ugbm93IG11c3Qg
c3VwcG9ydCB0aGF0IHBvc3QtYmFzZSBlbmNvZGluZywgYW5kIHRoZSBtdWx0aXBsZSBlbmNvZGlu
ZyBmb3JtYXRzIHRoYXQgdXNlIFBvc3QtQmFzZS4NCkkuZS4gTGl0ZXJhbCBIZWFkZXIgRmllbGQg
d2l0aCBOYW1lIFJlZmVyZW5jZSBhbmQgTGl0ZXJhbCBIZWFkZXIgRmlsdGVyIFdpdGggUG9zdC1C
YXNlIE5hbWUgUmVmZXJlbmNlLCBhbmQgc2ltaWxhcmx5IGZvciBJbmRleGVkIEhlYWRlciBGaWVs
ZC4NCg0KVG8gbWUsIGl0IHNlZW1zIGxpa2UgdGhlIHNpbXBsZXIsIG1vcmUgZWZmaWNpZW50IG9w
dGlvbiBvZiByZW1vdmluZyBwb3N0LWJhc2UgZW50aXJlbHkgY291bGQgYmUgYmV0dGVyLiAgIEF0
IHRoZSBjb3N0IG9mIHJlcXVpcmluZyAyLXBhc3MgZW5jb2RlLCB3ZSBjYW4gc2F2ZSBhIGZldyBi
aXRzIGZvciBtb3N0IGhlYWRlcnMgc2luY2Ugd2Ugd291bGQgbmV2ZXIgbmVlZCB0aGUgcG9zdCBi
YXNlIGhlYWRlciBwcmVmaXguDQoNClNvIGl04oCZcyBhIHF1ZXN0aW9uIG9mIGxvb3BpbmcgdGhy
dSB0aGUgaGVhZGVycyB0d2ljZSwgdnMuIGJlaW5nIGxlc3MgZWZmaWNpZW50IG9uIHRoZSB3aXJl
Lg0KDQpJIGhhdmVu4oCZdCBwcm9maWxlZCBpdCwgYnV0IEnigJlkIGd1ZXNzIHRoYXQgZG91Ymxl
IHBhc3MgdGhydSB0aGUgaGVhZGVycyBpc27igJl0IGdvaW5nIHRvIGJlIHRoYXQgbXVjaCBzbG93
ZXIgdGhhbiBzaW5nbGUgcGFzcy4gICBNYW55IG9mIHRoZSBoZWFkZXJzIGFyZSBnb2luZyB0byBi
ZSBlbmNvZGVkIGluIGJvdGggc3RyZWFtcy4gICBTbyB0aGUgbW9yZSBlZmZpY2llbnQgd2lyZSBm
b3JtYXQgbWF5IGJlIG1vcmUgb3B0aW1hbC4NCg0KYnMNCg==

--_000_SN1PR08MB18544B4959E9E21B5F1CF578DA9A0SN1PR08MB1854namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMg
MiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1
IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLk1z
b0xpc3RQYXJhZ3JhcGgsIGxpLk1zb0xpc3RQYXJhZ3JhcGgsIGRpdi5Nc29MaXN0UGFyYWdyYXBo
DQoJe21zby1zdHlsZS1wcmlvcml0eTozNDsNCgltYXJnaW4tdG9wOjBpbjsNCgltYXJnaW4tcmln
aHQ6MGluOw0KCW1hcmdpbi1ib3R0b206MGluOw0KCW1hcmdpbi1sZWZ0Oi41aW47DQoJbWFyZ2lu
LWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGli
cmkiLHNhbnMtc2VyaWY7fQ0KcC5tc29ub3JtYWwwLCBsaS5tc29ub3JtYWwwLCBkaXYubXNvbm9y
bWFsMA0KCXttc28tc3R5bGUtbmFtZTptc29ub3JtYWw7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87DQoJbWFyZ2luLXJpZ2h0OjBpbjsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCglt
YXJnaW4tbGVmdDowaW47DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJy
aSIsc2Fucy1zZXJpZjt9DQpzcGFuLkVtYWlsU3R5bGUxOA0KCXttc28tc3R5bGUtdHlwZTpwZXJz
b25hbDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0
ZXh0Ow0KCWZvbnQtd2VpZ2h0Om5vcm1hbDsNCglmb250LXN0eWxlOm5vcm1hbDt9DQpzcGFuLkVt
YWlsU3R5bGUxOQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2Fs
aWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCnNwYW4uRW1haWxTdHlsZTIw
DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5z
LXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjINCgl7bXNvLXN0
eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2Vy
aWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlw
ZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0K
CXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0K
ZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQovKiBMaXN0IERlZmluaXRp
b25zICovDQpAbGlzdCBsMA0KCXttc28tbGlzdC1pZDoxNjU0ODczMjI2Ow0KCW1zby1saXN0LXR5
cGU6aHlicmlkOw0KCW1zby1saXN0LXRlbXBsYXRlLWlkczotMTUzNDAyNzE5MCA2NzY5ODY4OSA2
NzY5ODY5MSA2NzY5ODY5MyA2NzY5ODY4OSA2NzY5ODY5MSA2NzY5ODY5MyA2NzY5ODY4OSA2NzY5
ODY5MSA2NzY5ODY5Mzt9DQpAbGlzdCBsMDpsZXZlbDENCgl7bXNvLWxldmVsLW51bWJlci1mb3Jt
YXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9u
ZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWlu
Ow0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDINCgl7bXNvLWxldmVsLW51
bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1z
dG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50
Oi0uMjVpbjsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCkBsaXN0IGwwOmxldmVsMw0K
CXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0K
CW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVm
dDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0
IGwwOmxldmVsNA0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVs
LXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXIt
cG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6U3ltYm9s
O30NCkBsaXN0IGwwOmxldmVsNQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJ
bXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwt
bnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5
OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6bGV2ZWw2DQoJe21zby1sZXZlbC1udW1iZXItZm9y
bWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5v
bmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVp
bjsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw3DQoJe21zby1sZXZl
bC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVs
LXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQt
aW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWw4DQoJ
e21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1z
by1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsN
Cgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlz
dCBsMDpsZXZlbDkNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZl
bC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVy
LXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5Oldpbmdk
aW5nczt9DQpvbA0KCXttYXJnaW4tYm90dG9tOjBpbjt9DQp1bA0KCXttYXJnaW4tYm90dG9tOjBp
bjt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0
cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1b
aWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRt
YXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5k
aWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iIzA1NjNDMSIgdmxpbms9
IiM5NTRGNzIiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPlRoaXMgaXMgcGFydCBvZiB3aHkgSSBkaWRu4oCZdCBhdHRlbXB0IHRvIG1lcmdlIEFsYW7i
gJlzIHBvc3QtYmFzZSBkZXNpZ24gaW50byAjMTE0MSwgYnV0IGxlZnQgaXQgYXMgYSBzZXBhcmF0
ZSBQUi4mbmJzcDsgVGhhdCBoZWxwcyB0byBpZGVudGlmeSBleGFjdGx5IHdoaWNoIGluc3RydWN0
aW9ucyBoYXZlIGJlZW4gZGVncmFkZWQgYnkgYWRkaW5nIHRoZXNlIHR3byBhZGRpdGlvbmFsIGlu
c3RydWN0aW9ucy4mbmJzcDsgVGhlIGltcGFjdA0KIHR1cm5lZCBvdXQgdG8gYmU6PG86cD48L286
cD48L3A+DQo8dWwgc3R5bGU9Im1hcmdpbi10b3A6MGluIiB0eXBlPSJkaXNjIj4NCjxsaSBjbGFz
cz0iTXNvTGlzdFBhcmFncmFwaCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjBpbjttc28tbGlzdDpsMCBs
ZXZlbDEgbGZvMSI+4oCcRGVwZW5kc+KAnSB3YXMgcmVzdXJyZWN0ZWQgZnJvbSB0aGUgZGVhZCwg
b25lIGJ5dGUgcGVyIGhlYWRlciBibG9jazxvOnA+PC9vOnA+PC9saT48bGkgY2xhc3M9Ik1zb0xp
c3RQYXJhZ3JhcGgiIHN0eWxlPSJtYXJnaW4tbGVmdDowaW47bXNvLWxpc3Q6bDAgbGV2ZWwxIGxm
bzEiPkxpdGVyYWwgaGVhZGVycyB3aXRob3V0IG5hbWUgcmVmZXJlbmNlcyBub3cgcmVxdWlyZSBv
bmUgbW9yZSBieXRlIGZvciBuYW1lcyB3aGljaCBhcmUgNy0xNSBvY3RldHMgbG9uZzxvOnA+PC9v
OnA+PC9saT48L3VsPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5XaGlsZSB0aGUgaW1wYWN0IGlzIGNlcnRhaW5seSBub3Qg
bm9uLXplcm8sIHRoaXMgc2VlbXMgZmFpcmx5IGNvbnRhaW5lZC4mbmJzcDsgSSBkb27igJl0IGhh
dmUgYSBwcm9ibGVtIHdpdGggdHdvLXBhc3MgZW5jb2Rpbmcg4oCTIHRoYXQgd2FzIGFjdHVhbGx5
IG15IG9yaWdpbmFsIGRlc2lnbiwgYW5kIEkgc3RpbGwgdGhpbmsgaXQgbWFrZXMgYSBsb3Qgb2Yg
c2Vuc2UuJm5ic3A7IEJ1dCBwYXJ0IG9mIHRoZSBjb25zZW5zdXMgYXQgdGhlDQogU2VhdHRsZSBp
bnRlcmltIHdhcyB0aGF0IHdlIHdhbnQgdG8gYWxsb3cgdGhlIGludGVsbGlnZW5jZSBhbmQgY2hv
aWNlcyB0byBsaXZlIGluIHRoZSBlbmNvZGVyLCBhbmQgSSBzZWUgcGVybWl0dGluZyB0aGUgZW5j
b2RlciB0byBjaG9vc2Ugc2luZ2xlLXBhc3MgdmVyc3VzIGRvdWJsZS1wYXNzIGFzIGFuIGV4YW1w
bGUgb2YgdGhhdC48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QWxzbywgZG91YmxlLXBhc3MgaGFz
IGl0cyBvd24gcG90ZW50aWFsIHBpdGZhbGxzIOKAkyBub3RpbmcgdGhhdCB5b3XigJlsbCByZWZl
ciB0byBhbiBlbnRyeSB3aGljaCBpcyBpbiB0aGUgZHluYW1pYyB0YWJsZSBkdXJpbmcgeW91ciBm
aXJzdCBwYXNzLCBidXQgdGhlbiBkaXNjb3ZlcmluZyB0aGF0IGVudHJ5IGhhcyBiZWVuIHB1c2hl
ZCBvdXQgZHVlIHRvIGluc2VydGlvbnMgd2hlbiB5b3UgdHJ5IHRvIGFjdHVhbGx5DQogcmVmZXJl
bmNlIGl0IG9uIHRoZSBzZWNvbmQgcGFzcywgZm9yIGV4YW1wbGUuJm5ic3A7IFRoZXJlIGFyZSBt
aXRpZ2F0aW9ucyBmb3IgdGhlc2UsIG9mIGNvdXJzZSwgYnV0IEkgZG9u4oCZdCBzZWUgZWl0aGVy
IGFzIGRyYW1hdGljYWxseSBzaW1wbGVyIHRoYW4gdGhlIG90aGVyLjxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdiBz
dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6
My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+RnJvbTo8L2I+IFFV
SUMgJmx0O3F1aWMtYm91bmNlc0BpZXRmLm9yZyZndDsgPGI+T24gQmVoYWxmIE9mIDwvYj4NCkJy
aWFuIFN3YW5kZXI8YnI+DQo8Yj5TZW50OjwvYj4gVHVlc2RheSwgTWF5IDgsIDIwMTggMTo1MCBQ
TTxicj4NCjxiPlRvOjwvYj4gQWxhbiBGcmluZGVsbCAmbHQ7YWZyaW5kQGZiLmNvbSZndDs7IHF1
aWNAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUkU6IFFQQUNLIC0gcHJvcG9zYWwgdG8g
b3B0aW1pemUgY29tcHJlc3Npb248bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPk9mIGNvdXJzZSBzaW5nbGUgcGFzcyBpc27igJl0IHJlcXVpcmVkLiZuYnNwOyBCdXQgdGhl
IFBvc3RCYXNlIGlzIHRoZXJlIG9ubHkgdG8gc3VwcG9ydCBzaW5nbGUgcGFzcy4mbmJzcDsgU28g
dGhlcmUgYXJlIGRlZmluaXRlbHkgKHByb2JhYmx5IGZyaW5nZSkgY2FzZXMgd2hlcmUgdGhlIGVu
Y29kZWQgc2l6ZSB3aWxsIGJlIGxhcmdlciBiZWNhdXNlIG9mIFBvc3RCYXNlLjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5TbyBJTU8sIGl0IGNvbWVzIGRvd24gdG8gdGhlIHRyYWRlb2ZmIG9mIHRo
ZSBwb3NzaWJsZSBzcGVlZCBpbXByb3ZlbWVudCBvZiBzaW5nbGUgcGFzcyB2cy4gY29tcHJlc3Np
b24gc2l6ZS4mbmJzcDsmbmJzcDsgQW5kIEkganVzdCBkb27igJl0IHNlZSB0aGUgc3BlZWQgb2Yg
dGhlIHNpbmdsZSBwYXNzIGJlaW5nIHZlcnkgY29tcGVsbGluZyBlaXRoZXIuJm5ic3A7IEZvciBp
bnN0YW5jZSwgeW91IGNhbiBjYWNoZSB0aGUgaW5kaWNlcywgZXRjDQogZnJvbSBwYXNzIDEsIGFu
ZCBqdXN0IHF1aWNrbHkgYnVybiB0aHJ1IHRoZSBhcnJheSBhZ2FpbiBlbmNvZGluZyB0aGUgaW5k
aWNlcyBkZXRlcm1pbmVkIGZyb20gcGFzcyAxLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5QZXJz
b25hbGx5LCBnaXZlbiB0aGF0IHRoZSBzcGVlZCBpbXByb3ZlbWVudCBvZiBzaW5nbGUgcGFzcyBp
cyBwcm9iYWJseSBtYXJnaW5hbCBhdCBiZXN0LCBJ4oCZZCBlcnIgb24gdGhlIHNpZGUgb2YgbGVz
cyBjb21wbGV4aXR5IOKAkyBhbmQgc2xpZ2h0bHkgYmV0dGVyIGNvbXByZXNzaW9uLjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5CdXQgSeKAmW0gbm90IHBhc3Npb25hdGUgYWJvdXQgdGhpcyBpc3N1
ZS4mbmJzcDsgJm5ic3A7U28gSeKAmW0gZmluZSB3aXRoIHRoZSBjdXJyZW50IGRyYWZ0LCBpZiBl
dmVyeW9uZSBlbHNlIGxpa2VzIGl0LiZuYnNwOyAmbmJzcDtJIGp1c3QgcHJlZmVyIHNpbXBsaWNp
dHkgd2hlbiBpdCBzZWVtcyBsaWtlIGNvbXBsZXhpdHkgaXNu4oCZdCBidXlpbmcgdXMgbXVjaC4m
bmJzcDsgQW5kIGluIHRoaXMgY2FzZSwgc2ltcGxpY2l0eSBhbHNvIGdpdmVzIHNsaWdodGx5IGJl
dHRlcg0KIGNvbXByZXNzaW9uLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5iczxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0K
PGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3Bh
ZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+RnJvbTo8
L2I+IEFsYW4gRnJpbmRlbGwgJmx0OzxhIGhyZWY9Im1haWx0bzphZnJpbmRAZmIuY29tIj5hZnJp
bmRAZmIuY29tPC9hPiZndDsNCjxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCBNYXkgOCwgMjAx
OCAxOjEzIFBNPGJyPg0KPGI+VG86PC9iPiBCcmlhbiBTd2FuZGVyICZsdDs8YSBocmVmPSJtYWls
dG86YnJpYW5zd0BtaWNyb3NvZnQuY29tIj5icmlhbnN3QG1pY3Jvc29mdC5jb208L2E+Jmd0OzsN
CjxhIGhyZWY9Im1haWx0bzpxdWljQGlldGYub3JnIj5xdWljQGlldGYub3JnPC9hPjxicj4NCjxi
PlN1YmplY3Q6PC9iPiBSZTogUVBBQ0sgLSBwcm9wb3NhbCB0byBvcHRpbWl6ZSBjb21wcmVzc2lv
bjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+U2luZ2xlIHBhc3MgZW5j
b2RpbmcgaXMgbm90IHJlcXVpcmVkLCBhbiBlbmNvZGVyIGhhcyB0aGUgb3B0aW9uIHRvIGVuY29k
ZSB1c2luZyBvbmUgb3IgdHdvIHBhc3Nlcy4mbmJzcDsgVGhlIG9ubHkgd2lyZSBwZW5hbHR5IGZv
ciBhIHR3by1wYXNzIGVuY29kZXIgaXMgb25lIGV4dHJhIGJ5dGUgcGVyIGhlYWRlciBibG9jayBp
biB0aGUgcHJlZml4LCBhcyBsYXJnZXN0IHJlZmVyZW5jZSBhbmQgYmFzZSBpbmRleCBjYW4gYmUN
CiB0aGUgc2FtZSBpbiB0d28tcGFzcyBlbmNvZGluZy4mbmJzcDsgVGhlIG9yaWdpbmFsIHNwZWNp
ZmljYXRpb24gKHdoaWNoIHVzZWQgRGVwZW5kcykgaGFkIGEgb25lIGJpdCBmbGFnIGluIHRoZSBI
VFRQIGZyYW1lIHRoYXQgYWxsb3dlZCB0aGUgZW5jb2RlciBzYXZlIHRoaXMgYnl0ZSBhcyB3ZWxs
LCBidXQgdGhlIGNvbnNlbnN1cyBzZWVtZWQgdG8gYmUgaXQgd2FzIGJldHRlciB0byBoYXZlIGEg
Zml4ZWQgZm9ybWF0IHRvIHRoZSBwcmVmaXguJm5ic3A7IFdpdGhvdXQNCiBwb3N0LWJhc2UsIHRo
ZXJlIGNvdWxkIGFsc28gYmUgb25lIG1vcmUgYml0IGF2YWlsYWJsZSBmb3IgdGhlIGxlbmd0aCBv
ZiBhIGxpdGVyYWwgaGVhZGVyIG5hbWUgd2l0aG91dCBhZGRpbmcgYW4gZXh0cmEgYnl0ZSAoaGVh
ZGVyIG5hbWVzIHdpdGggNyAmbHQ7PSBsZW5ndGggJmx0OyAxNSkuJm5ic3A7IFdlIGNhbiBvZiBj
b3Vyc2Ugc2ltdWxhdGUgaXQsIGJ1dCBJIGV4cGVjdCB0aGUgZGlmZmVyZW5jZSB0byBiZSBpbiB0
aGUgbm9pc2UuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkRlY29kZXJzIGRvIG5lZWQgdG8gc3Vw
cG9ydCBib3RoIGtpbmRzIG9mIGluc3RydWN0aW9ucywgYnV0IEkgZG9u4oCZdCBmaW5kIGl0IHRv
IGJlIHRlcnJpYmx5IGNvbXBsZXguJm5ic3A7IFRoZSBwcm94eWdlbiBpbXBsZW1lbnRhdGlvbiBv
ZiB0aGUgbGF0ZXN0IGRyYWZ0IGluY2x1ZGluZyBvbmUtcGFzcyBlbmNvZGluZy9kZWNvZGluZyBz
aG91bGQgYmUgc3luY2VkIHRvIGdpdGh1YiB0aGlzIHdlZWsuPG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPknigJltIG5vdCBzdXJlIHdoYXQgeW91IG1lYW4gd2hlbiB5b3Ugc2F5IOKAnE1hbnkgb2Yg
dGhlIGhlYWRlcnMgYXJlIGdvaW5nIHRvIGJlIGVuY29kZWQgaW4gYm90aCBzdHJlYW1zLuKAnSZu
YnNwOyBJZiB5b3UgbWVhbiBpdCB3aWxsIGVuY29kZSBhbiBpbnNlcnQgb24gdGhlIGNvbnRyb2wg
c3RyZWFtIGFuZCBhbiBpbmRleCByZWZlcmVuY2Ugb24gdGhlIHJlcXVlc3Qgc3RyZWFtLCB0aGF0
IGlzIHRydWUsIGFuZCB0aGUgcG9zdC1iYXNlDQogZW5jb2Rpbmcgb2YgdGhlIHJlZmVyZW5jZXMg
b2NjdXBpZXMgb25seSBvbmUgYnl0ZSBmb3IgdGhlIGZpcnN0IDE1IHN1Y2ggaGVhZGVycyBwZXIg
YmxvY2suPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi1BbGFuPG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Y29sb3I6
YmxhY2siPkZyb206IDwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Y29s
b3I6YmxhY2siPlFVSUMgJmx0OzxhIGhyZWY9Im1haWx0bzpxdWljLWJvdW5jZXNAaWV0Zi5vcmci
PnF1aWMtYm91bmNlc0BpZXRmLm9yZzwvYT4mZ3Q7IG9uIGJlaGFsZiBvZiBCcmlhbiBTd2FuZGVy
ICZsdDs8YSBocmVmPSJtYWlsdG86YnJpYW5zdz00MG1pY3Jvc29mdC5jb21AZG1hcmMuaWV0Zi5v
cmciPmJyaWFuc3c9NDBtaWNyb3NvZnQuY29tQGRtYXJjLmlldGYub3JnPC9hPiZndDs8YnI+DQo8
Yj5EYXRlOiA8L2I+TW9uZGF5LCBNYXkgNywgMjAxOCBhdCAyOjM1IFBNPGJyPg0KPGI+VG86IDwv
Yj4mcXVvdDs8YSBocmVmPSJtYWlsdG86cXVpY0BpZXRmLm9yZyI+cXVpY0BpZXRmLm9yZzwvYT4m
cXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzpxdWljQGlldGYub3JnIj5xdWljQGlldGYub3JnPC9h
PiZndDs8YnI+DQo8Yj5TdWJqZWN0OiA8L2I+UVBBQ0sgLSBwcm9wb3NhbCB0byBvcHRpbWl6ZSBj
b21wcmVzc2lvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48YSBuYW1lPSJfTWFpbE9yaWdpbmFsQm9keSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMi4wcHQiPlBsZWFzZSBjb3JyZWN0IG1lIGlmIEnigJltIHdyb25nIGhlcmUuPC9zcGFuPjxv
OnA+PC9vOnA+PC9hPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28t
Ym9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0
Ij4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMi4wcHQiPkl0IGxvb2tzIGxpa2UgdGhlIGxhdGVzdCBRUEFDSyBkcmFm
dCBoYXMgYmVlbiBvcHRpbWl6ZWQgdG8gYWxsb3cgZW5jb2RlIG9mIGJvdGggY29udHJvbCBhbmQg
ZGF0YSBzdHJlYW1zIGluIGEgc2luZ2xlIHBhc3MuPC9zcGFuPjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxP
cmlnaW5hbEJvZHkiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0Ij5CZWNhdXNlIG9mIHRo
aXMsIHdlIG5vdyBtdXN0IHN1cHBvcnQgdGhhdCBwb3N0LWJhc2UgZW5jb2RpbmcsIGFuZCB0aGUg
bXVsdGlwbGUgZW5jb2RpbmcgZm9ybWF0cyB0aGF0IHVzZSBQb3N0LUJhc2UuPC9zcGFuPjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28t
Ym9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0
Ij5JLmUuIExpdGVyYWwgSGVhZGVyIEZpZWxkIHdpdGggTmFtZSBSZWZlcmVuY2UgYW5kIExpdGVy
YWwgSGVhZGVyIEZpbHRlciBXaXRoIFBvc3QtQmFzZSBOYW1lIFJlZmVyZW5jZSwgYW5kIHNpbWls
YXJseSBmb3IgSW5kZXhlZCBIZWFkZXIgRmllbGQuPC9zcGFuPjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxP
cmlnaW5hbEJvZHkiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0Ij4mbmJzcDs8L3NwYW4+
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
Mi4wcHQiPlRvIG1lLCBpdCBzZWVtcyBsaWtlIHRoZSBzaW1wbGVyLCBtb3JlIGVmZmljaWVudCBv
cHRpb24gb2YgcmVtb3ZpbmcgcG9zdC1iYXNlIGVudGlyZWx5IGNvdWxkIGJlIGJldHRlci4mbmJz
cDsmbmJzcDsgQXQgdGhlIGNvc3Qgb2YgcmVxdWlyaW5nIDItcGFzcyBlbmNvZGUsIHdlIGNhbiBz
YXZlIGENCiBmZXcgYml0cyBmb3IgbW9zdCBoZWFkZXJzIHNpbmNlIHdlIHdvdWxkIG5ldmVyIG5l
ZWQgdGhlIHBvc3QgYmFzZSBoZWFkZXIgcHJlZml4LiZuYnNwOyZuYnNwOw0KPC9zcGFuPjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28t
Ym9va21hcms6X01haWxPcmlnaW5hbEJvZHkiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0
Ij4mbmJzcDs8L3NwYW4+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9Im1zby1ib29rbWFyazpfTWFpbE9yaWdpbmFsQm9keSI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMi4wcHQiPlNvIGl04oCZcyBhIHF1ZXN0aW9uIG9mIGxvb3BpbmcgdGhy
dSB0aGUgaGVhZGVycyB0d2ljZSwgdnMuIGJlaW5nIGxlc3MgZWZmaWNpZW50IG9uIHRoZSB3aXJl
Ljwvc3Bhbj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0ibXNvLWJvb2ttYXJrOl9NYWlsT3JpZ2luYWxCb2R5Ij48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEyLjBwdCI+Jm5ic3A7PC9zcGFuPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJv
ZHkiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0Ij5JIGhhdmVu4oCZdCBwcm9maWxlZCBp
dCwgYnV0IEnigJlkIGd1ZXNzIHRoYXQgZG91YmxlIHBhc3MgdGhydSB0aGUgaGVhZGVycyBpc27i
gJl0IGdvaW5nIHRvIGJlIHRoYXQgbXVjaCBzbG93ZXIgdGhhbiBzaW5nbGUgcGFzcy4gJm5ic3A7
Jm5ic3A7TWFueSBvZiB0aGUgaGVhZGVycyBhcmUgZ29pbmcgdG8gYmUNCiBlbmNvZGVkIGluIGJv
dGggc3RyZWFtcy4mbmJzcDsmbmJzcDsgU28gdGhlIG1vcmUgZWZmaWNpZW50IHdpcmUgZm9ybWF0
IG1heSBiZSBtb3JlIG9wdGltYWwuPC9zcGFuPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tYm9va21hcms6X01haWxPcmlnaW5hbEJv
ZHkiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0Ij4mbmJzcDs8L3NwYW4+PG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1ib29r
bWFyazpfTWFpbE9yaWdpbmFsQm9keSI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQiPmJz
PC9zcGFuPjwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_SN1PR08MB18544B4959E9E21B5F1CF578DA9A0SN1PR08MB1854namp_--


From nobody Wed May  9 09:05:20 2018
Return-Path: <samuelh@rd.bbc.co.uk>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C057E12DA51 for <quic@ietfa.amsl.com>; Wed,  9 May 2018 09:05:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.301
X-Spam-Level: 
X-Spam-Status: No, score=-2.301 tagged_above=-999 required=5 tests=[RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 hYWuIMcY79Gy for <quic@ietfa.amsl.com>; Wed,  9 May 2018 09:05:04 -0700 (PDT)
Received: from gateh.kw.bbc.co.uk (gateh.kw.bbc.co.uk [132.185.132.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70D3512E85E for <quic@ietf.org>; Wed,  9 May 2018 09:05:03 -0700 (PDT)
Received: from mailhub0.rd.bbc.co.uk ([172.29.120.128]) by gateh.kw.bbc.co.uk (8.14.5+Sun/8.13.6) with ESMTP id w49G51vU013545 for <quic@ietf.org>; Wed, 9 May 2018 17:05:01 +0100 (BST)
Received: from rd015072.rd.bbc.co.uk ([172.29.91.136]:46326) by mailhub0.rd.bbc.co.uk with esmtp (Exim 4.84_2) (envelope-from <samuelh@rd.bbc.co.uk>) id 1fGRaP-0001FQ-BB for quic@ietf.org; Wed, 09 May 2018 17:05:01 +0100
From: Samuel Hurst <samuelh@rd.bbc.co.uk>
Subject: Clarification of transport and HTTP version compatibility
To: IETF QUIC WG <quic@ietf.org>
Message-ID: <906fdff3-8009-238b-998b-4ea515a2684d@rd.bbc.co.uk>
Date: Wed, 9 May 2018 17:04:56 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="oYGoytREnNRT3p4KejHLe5e48cklVEiRB"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/nQGhH1Kajwk7wIdfaloNPDGB36g>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2018 16:05:15 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--oYGoytREnNRT3p4KejHLe5e48cklVEiRB
Content-Type: multipart/mixed; boundary="1lRzTC6FJe2nGVQYCfnvRFpxfZmfM0K4J";
 protected-headers="v1"
From: Samuel Hurst <samuelh@rd.bbc.co.uk>
To: IETF QUIC WG <quic@ietf.org>
Message-ID: <906fdff3-8009-238b-998b-4ea515a2684d@rd.bbc.co.uk>
Subject: Clarification of transport and HTTP version compatibility

--1lRzTC6FJe2nGVQYCfnvRFpxfZmfM0K4J
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: quoted-printable

Hi all,

Does the quic-transport version and the HTTP mapping version have to
match? For example, could you negotiate QUIC draft-11, but the HTTP side
is still using an older version (such as draft-09 to avoid the
requirement of QPACK)?

As far as I understand it, the QUIC transport version is negotiated as
part of the TransportParams in the appropriate TLS extension, and the
HTTP mapping version is negotiated by ALPN. So in the example above,
would it be acceptable to negotiate 0xff00000a as the transport protocol
version, and then have an ALPN string of "hq-09"?

I'm then assuming that a valid Alt-Svc header for my example could be as
follows:

Alt-Svc: hq-09=3D":4443";quic=3D"ff00000a"

The quic-tls draft mentions in Section 9.1 "The application-layer
protocol MAY restrict the QUIC version that it can operate over", but
none of the quic-http drafts that I've read list any such restriction.
Therefore, I'm then further assuming that it's safe to run whatever
version of the HTTP mapping I like, unless there's a compatibility
matrix between the various specs that I'm missing?

Best Regards,
Sam


--1lRzTC6FJe2nGVQYCfnvRFpxfZmfM0K4J--

--oYGoytREnNRT3p4KejHLe5e48cklVEiRB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2

iQIcBAEBCAAGBQJa8xwoAAoJEJGbiYWuJo/5+h0P/33k7jjJYoS6Jnzh1KrORtbN
zojF2/U0G7NWwJK5didlvgFuYEwXUXhkVmkC7D8ARHdQF3Wsu43M6pP737GbUY8F
x++cXaq+WzNwHdDSNPPIT3l4eY4alr8q0gGhIhTkCi+9UN1mR3xkpFCcjF6vJWb5
EGtpc6hcTTNNmVKKyXU10Y5S9JZuG1omi28WeSxYTBDBwwoSTDmwXAGr60FqImuO
lec3owWSKWa6QiBHedgrhchJ+fP4kMIcv/om5LhU871wb3ZzhIwLt1gGPKA4Xlz0
9Ct85jZaASoitgpWbnlMSOO5oIe5qAtOfAzJtMSE1WoQWpmczbUIe4P5eyWJQJs2
UxGvHxvgvKYrRwRNFFJEEbiVqK29pk2V3E9w6ZcoDWQyYyTfr4BrUgmyv4NHatT1
6BFOIiCPzEKG3Jcz268FQyYgdSu0J13xvR1uuq48Zi515Y5++nODK6L/lEvY8PPd
h0krxbXYuTUKAGNCIYT2Ox2Yjgi/DJheRba+GtRKdKNWCRACIQ5uuHt/vdE23n4p
b6G8Nr9QrhTxciTV+47oyVwKvoxAs20p+tzL33IrMWb5etGxPcpqLLLQ60LbKC/n
+vcFtddd5Z4nqbDzpgRONxyVlRNpU5gB8Jy2/61bTNptO6az1qsn19og1v3BZuiQ
gWT0qOZTTQJo5/DZVydF
=fQwE
-----END PGP SIGNATURE-----

--oYGoytREnNRT3p4KejHLe5e48cklVEiRB--


From nobody Wed May  9 10:18:17 2018
Return-Path: <mbishop@evequefou.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C875712D955 for <quic@ietfa.amsl.com>; Wed,  9 May 2018 10:18:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.011
X-Spam-Level: 
X-Spam-Status: No, score=-0.011 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 Qr80jmeJ0F3a for <quic@ietfa.amsl.com>; Wed,  9 May 2018 10:18:13 -0700 (PDT)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0111.outbound.protection.outlook.com [104.47.40.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D86F912D950 for <quic@ietf.org>; Wed,  9 May 2018 10:18:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=ECeXl1ihEfwtf7v5XwBoJtEIhAuXOpNhAhPqnefyGTg=; b=mHGpVost28TFaIIB3zlR3qVjFC4FEVHJEiKU6LMGIYU1+LbazY7jVndEM/5jxc+CuEjvuWrIzvYrKTH8UvEj9a+ZrjbQJJFs6ArNKFo7E+2BWEUJ5Yr1JmSX+CvogVnzkXP9TLsSK67558WNQtO4cUeiv81LEfq/N4yEs0NZVsQ=
Received: from SN1PR08MB1854.namprd08.prod.outlook.com (10.169.39.8) by SN1PR08MB1709.namprd08.prod.outlook.com (10.162.133.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.755.16; Wed, 9 May 2018 17:18:10 +0000
Received: from SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d]) by SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d%13]) with mapi id 15.20.0735.018; Wed, 9 May 2018 17:18:10 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Samuel Hurst <samuelh@rd.bbc.co.uk>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Clarification of transport and HTTP version compatibility
Thread-Topic: Clarification of transport and HTTP version compatibility
Thread-Index: AQHT56+xI3vQwOQ++kOo1AZLBRUIXaQno4FA
Date: Wed, 9 May 2018 17:18:10 +0000
Message-ID: <SN1PR08MB1854826DACF0454471CB162DDA990@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <906fdff3-8009-238b-998b-4ea515a2684d@rd.bbc.co.uk>
In-Reply-To: <906fdff3-8009-238b-998b-4ea515a2684d@rd.bbc.co.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [2603:3023:123:2900:2da8:81e8:86dc:e86e]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN1PR08MB1709; 7:wVkmYAnrqYHkIqmfrxOITdqAsFb3F8JMTv3REDyxj4wdXmsE+1qos952ZlCj1ZkouT6fBphr04ndhtpqPJwJwLMaqUu7D9uVZMYJDJz1e3Jf3ll64mGOsQw0R7YIE5pTpfx1nJWbgmBrMdpIpwgE1jKYZGB/OrTjp89CkPop4UtwbPwUuHLUpsVsqQ/CZrFwUh6GS2mZhj32xQ3zV97YjFzSJGDRHxjY2sbEYLSJdx8Dh4AnQeDILpKP4NNtVYIa
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(5600026)(2017052603328)(7153060)(7193020); SRVR:SN1PR08MB1709; 
x-ms-traffictypediagnostic: SN1PR08MB1709:
x-microsoft-antispam-prvs: <SN1PR08MB1709D5BB5C43B3EAE5A60889DA990@SN1PR08MB1709.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3231254)(944501410)(52105095)(3002001)(93006095)(93001095)(10201501046)(149027)(150027)(6041310)(2016111802025)(20161123562045)(20161123558120)(20161123564045)(20161123560045)(6043046)(6072148)(201708071742011); SRVR:SN1PR08MB1709; BCL:0; PCL:0; RULEID:; SRVR:SN1PR08MB1709; 
x-forefront-prvs: 0667289FF8
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(39380400002)(346002)(366004)(396003)(39830400003)(189003)(199004)(13464003)(53754006)(6116002)(486006)(46003)(2906002)(97736004)(478600001)(2900100001)(446003)(81156014)(81166006)(8676002)(3280700002)(74316002)(3660700001)(86362001)(5660300001)(55016002)(53936002)(476003)(11346002)(7736002)(229853002)(305945005)(9686003)(6246003)(74482002)(106356001)(6436002)(33656002)(102836004)(99286004)(6506007)(53546011)(5250100002)(105586002)(110136005)(186003)(8936002)(25786009)(14454004)(76176011)(7696005)(316002)(68736007); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR08MB1709; H:SN1PR08MB1854.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: D3DWFXJ+q8XS8R4T68v8QU9rF5VoxGqZ6md4fvQo4IgXbqxQCbKCDAOrynIXeWIgLyRbR/LbAO+Wb6Iaee9xmiN8fKkL1fGsUDnmaUfkf0hjImicdSKAIWQ4DTkCRL6yI643buC5kZbdxmZrMB2JpbL2DsSyHDdpvYqz91m6kx9w1AkkZh6N/bsgcU3C2Ge9
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 6ae4c620-5c1b-470e-e66b-08d5b5d0d6a6
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 6ae4c620-5c1b-470e-e66b-08d5b5d0d6a6
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 May 2018 17:18:10.0786 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR08MB1709
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/k0kjoM9G2DfBEfcmEfE-zWpTK6k>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2018 17:18:16 -0000

VGhlcmUncyBubyBmaXJtIHJlc3RyaWN0aW9uLCBuby4gIFdoaWxlIEkgZmluZCBpdCBsaWtlbHkg
dGhhdCBkcmFmdCBkZXBsb3ltZW50cyB3aWxsIGNob29zZSB0byBrZWVwIG1hdGNoaW5nIHZlcnNp
b25zLCB0aGUgb25seSByZXN0cmljdGlvbiB0aGF0IHRoZSBIVFRQIGRyYWZ0IGN1cnJlbnRseSBp
bXBvc2VzIGlzIHRoYXQgaXQgYmUgYSB2ZXJzaW9uIG9mIFFVSUMgd2hpY2ggdXNlcyBUTFMgYXMg
dGhlIGhhbmRzaGFrZSBwcm90b2NvbC4NCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZy
b206IFFVSUMgPHF1aWMtYm91bmNlc0BpZXRmLm9yZz4gT24gQmVoYWxmIE9mIFNhbXVlbCBIdXJz
dA0KU2VudDogV2VkbmVzZGF5LCBNYXkgOSwgMjAxOCA5OjA1IEFNDQpUbzogSUVURiBRVUlDIFdH
IDxxdWljQGlldGYub3JnPg0KU3ViamVjdDogQ2xhcmlmaWNhdGlvbiBvZiB0cmFuc3BvcnQgYW5k
IEhUVFAgdmVyc2lvbiBjb21wYXRpYmlsaXR5DQoNCkhpIGFsbCwNCg0KRG9lcyB0aGUgcXVpYy10
cmFuc3BvcnQgdmVyc2lvbiBhbmQgdGhlIEhUVFAgbWFwcGluZyB2ZXJzaW9uIGhhdmUgdG8gbWF0
Y2g/IEZvciBleGFtcGxlLCBjb3VsZCB5b3UgbmVnb3RpYXRlIFFVSUMgZHJhZnQtMTEsIGJ1dCB0
aGUgSFRUUCBzaWRlIGlzIHN0aWxsIHVzaW5nIGFuIG9sZGVyIHZlcnNpb24gKHN1Y2ggYXMgZHJh
ZnQtMDkgdG8gYXZvaWQgdGhlIHJlcXVpcmVtZW50IG9mIFFQQUNLKT8NCg0KQXMgZmFyIGFzIEkg
dW5kZXJzdGFuZCBpdCwgdGhlIFFVSUMgdHJhbnNwb3J0IHZlcnNpb24gaXMgbmVnb3RpYXRlZCBh
cyBwYXJ0IG9mIHRoZSBUcmFuc3BvcnRQYXJhbXMgaW4gdGhlIGFwcHJvcHJpYXRlIFRMUyBleHRl
bnNpb24sIGFuZCB0aGUgSFRUUCBtYXBwaW5nIHZlcnNpb24gaXMgbmVnb3RpYXRlZCBieSBBTFBO
LiBTbyBpbiB0aGUgZXhhbXBsZSBhYm92ZSwgd291bGQgaXQgYmUgYWNjZXB0YWJsZSB0byBuZWdv
dGlhdGUgMHhmZjAwMDAwYSBhcyB0aGUgdHJhbnNwb3J0IHByb3RvY29sIHZlcnNpb24sIGFuZCB0
aGVuIGhhdmUgYW4gQUxQTiBzdHJpbmcgb2YgImhxLTA5Ij8NCg0KSSdtIHRoZW4gYXNzdW1pbmcg
dGhhdCBhIHZhbGlkIEFsdC1TdmMgaGVhZGVyIGZvciBteSBleGFtcGxlIGNvdWxkIGJlIGFzDQpm
b2xsb3dzOg0KDQpBbHQtU3ZjOiBocS0wOT0iOjQ0NDMiO3F1aWM9ImZmMDAwMDBhIg0KDQpUaGUg
cXVpYy10bHMgZHJhZnQgbWVudGlvbnMgaW4gU2VjdGlvbiA5LjEgIlRoZSBhcHBsaWNhdGlvbi1s
YXllciBwcm90b2NvbCBNQVkgcmVzdHJpY3QgdGhlIFFVSUMgdmVyc2lvbiB0aGF0IGl0IGNhbiBv
cGVyYXRlIG92ZXIiLCBidXQgbm9uZSBvZiB0aGUgcXVpYy1odHRwIGRyYWZ0cyB0aGF0IEkndmUg
cmVhZCBsaXN0IGFueSBzdWNoIHJlc3RyaWN0aW9uLg0KVGhlcmVmb3JlLCBJJ20gdGhlbiBmdXJ0
aGVyIGFzc3VtaW5nIHRoYXQgaXQncyBzYWZlIHRvIHJ1biB3aGF0ZXZlciB2ZXJzaW9uIG9mIHRo
ZSBIVFRQIG1hcHBpbmcgSSBsaWtlLCB1bmxlc3MgdGhlcmUncyBhIGNvbXBhdGliaWxpdHkgbWF0
cml4IGJldHdlZW4gdGhlIHZhcmlvdXMgc3BlY3MgdGhhdCBJJ20gbWlzc2luZz8NCg0KQmVzdCBS
ZWdhcmRzLA0KU2FtDQoNCg==


From nobody Wed May  9 11:04:07 2018
Return-Path: <Lucas.Pardue@bbc.co.uk>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ED9BA126E64 for <quic@ietfa.amsl.com>; Wed,  9 May 2018 11:04:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 hq_RQJSEAQ_w for <quic@ietfa.amsl.com>; Wed,  9 May 2018 11:04:03 -0700 (PDT)
Received: from mailout0.telhc.bbc.co.uk (mailout0.telhc.bbc.co.uk [132.185.161.179]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7DAE1127077 for <quic@ietf.org>; Wed,  9 May 2018 11:04:02 -0700 (PDT)
Received: from BGB01XI1012.national.core.bbc.co.uk (bgb01xi1012.national.core.bbc.co.uk [10.161.14.16]) by mailout0.telhc.bbc.co.uk (8.15.2/8.15.2) with ESMTP id w49I3vFn006520; Wed, 9 May 2018 19:03:57 +0100 (BST)
Received: from BGB01XUD1012.national.core.bbc.co.uk ([10.161.14.10]) by BGB01XI1012.national.core.bbc.co.uk ([10.161.14.16]) with mapi id 14.03.0361.001; Wed, 9 May 2018 19:03:57 +0100
From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
To: Mike Bishop <mbishop@evequefou.be>, Sam Hurst-RD <samuelh@rd.bbc.co.uk>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Clarification of transport and HTTP version compatibility
Thread-Topic: Clarification of transport and HTTP version compatibility
Thread-Index: AQHT56+xKCNEYXqr2EueYoxG7/YhOKQnk0UAgAAbrQ8=
Date: Wed, 9 May 2018 18:03:56 +0000
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A3BB2B67C@bgb01xud1012>
References: <906fdff3-8009-238b-998b-4ea515a2684d@rd.bbc.co.uk>, <SN1PR08MB1854826DACF0454471CB162DDA990@SN1PR08MB1854.namprd08.prod.outlook.com>
In-Reply-To: <SN1PR08MB1854826DACF0454471CB162DDA990@SN1PR08MB1854.namprd08.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.19.161.213]
x-exclaimer-md-config: c91d45b2-6e10-4209-9543-d9970fac71b7
x-tm-as-product-ver: SMEX-11.0.0.4255-8.200.1013-23834.001
x-tm-as-result: No--1.129300-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/q4Uoo2M_MCWOjm7MPxP5PdiLOt4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2018 18:04:05 -0000

I think this all works fine in the current stage of specification.=20

Longer term, what is the failure case for interoperability where different =
implementations have  different rules for how to combine QUIC version and H=
TTP/QUIC version. Protocol error due to reception of unanticipated packets =
and or HTTP/QUIC frames?

Lucas
________________________________________
From: QUIC [quic-bounces@ietf.org] on behalf of Mike Bishop [mbishop@eveque=
fou.be]
Sent: 09 May 2018 18:18
To: Sam Hurst-RD; IETF QUIC WG
Subject: RE: Clarification of transport and HTTP version compatibility

There's no firm restriction, no.  While I find it likely that draft deploym=
ents will choose to keep matching versions, the only restriction that the H=
TTP draft currently imposes is that it be a version of QUIC which uses TLS =
as the handshake protocol.

-----Original Message-----
From: QUIC <quic-bounces@ietf.org> On Behalf Of Samuel Hurst
Sent: Wednesday, May 9, 2018 9:05 AM
To: IETF QUIC WG <quic@ietf.org>
Subject: Clarification of transport and HTTP version compatibility

Hi all,

Does the quic-transport version and the HTTP mapping version have to match?=
 For example, could you negotiate QUIC draft-11, but the HTTP side is still=
 using an older version (such as draft-09 to avoid the requirement of QPACK=
)?

As far as I understand it, the QUIC transport version is negotiated as part=
 of the TransportParams in the appropriate TLS extension, and the HTTP mapp=
ing version is negotiated by ALPN. So in the example above, would it be acc=
eptable to negotiate 0xff00000a as the transport protocol version, and then=
 have an ALPN string of "hq-09"?

I'm then assuming that a valid Alt-Svc header for my example could be as
follows:

Alt-Svc: hq-09=3D":4443";quic=3D"ff00000a"

The quic-tls draft mentions in Section 9.1 "The application-layer protocol =
MAY restrict the QUIC version that it can operate over", but none of the qu=
ic-http drafts that I've read list any such restriction.
Therefore, I'm then further assuming that it's safe to run whatever version=
 of the HTTP mapping I like, unless there's a compatibility matrix between =
the various specs that I'm missing?

Best Regards,
Sam


From nobody Wed May  9 14:02:05 2018
Return-Path: <mbishop@evequefou.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6068712DB6B for <quic@ietfa.amsl.com>; Wed,  9 May 2018 14:02:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 NmqOzkhS-yuy for <quic@ietfa.amsl.com>; Wed,  9 May 2018 14:02:02 -0700 (PDT)
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0091.outbound.protection.outlook.com [104.47.36.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0D9A612DA72 for <quic@ietf.org>; Wed,  9 May 2018 14:02:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=z9CQYWu2jP5Ni+evNPu4HxJLBmGhUJbxx1EJ7svjLmM=; b=g4w5jCwaP4CsxqpyXhUW+zuvdoPcLwgdPm6fK2GX5OrthI7/geoY9zBQKv2X6Z0BrNZQ4tVHKcp2jPhxqK9C65mAcOKtM5a+nHe6q8J8ou8xkW4VD2TfkiRE2QIfiXsMKGun4bGpA+Oz+bds6YRD+Dj+Er8E7rYlVfjR9DctpGM=
Received: from SN1PR08MB1854.namprd08.prod.outlook.com (10.169.39.8) by SN1PR08MB1423.namprd08.prod.outlook.com (10.162.1.20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.755.16; Wed, 9 May 2018 21:01:59 +0000
Received: from SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d]) by SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d%13]) with mapi id 15.20.0735.018; Wed, 9 May 2018 21:01:59 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Lucas Pardue <Lucas.Pardue@bbc.co.uk>, Sam Hurst-RD <samuelh@rd.bbc.co.uk>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Clarification of transport and HTTP version compatibility
Thread-Topic: Clarification of transport and HTTP version compatibility
Thread-Index: AQHT56+xI3vQwOQ++kOo1AZLBRUIXaQno4FAgAANUQCAADE84A==
Date: Wed, 9 May 2018 21:01:58 +0000
Message-ID: <SN1PR08MB1854FC73444239C609552459DA990@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <906fdff3-8009-238b-998b-4ea515a2684d@rd.bbc.co.uk>, <SN1PR08MB1854826DACF0454471CB162DDA990@SN1PR08MB1854.namprd08.prod.outlook.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB2B67C@bgb01xud1012>
In-Reply-To: <7CF7F94CB496BF4FAB1676F375F9666A3BB2B67C@bgb01xud1012>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [38.134.241.6]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN1PR08MB1423; 7:lTgw/PORZ28wyTwrR85eQcw0WyO1iMigQPK66lZ/ELXADqzXPgaxoA+p3GsHPkNKCqTHYL6LqH64l3jNErFEx3TBPF1UwOUNbCd3I5oN3QeGJUiF0nvkarMbo9wIXgSIvzAR/KGZXW8w3B1RR6aBbSmh3mACMQqtpZYce1N5nPocV9feVhNbG293AGSjgXPLCFYJVWaZuvhi98X5WoOMGXbt/7ZBjOjUHu2IchqXUHxYJL0ZQwwxxOICX5cYJ0El
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(5600026)(2017052603328)(7153060)(7193020); SRVR:SN1PR08MB1423; 
x-ms-traffictypediagnostic: SN1PR08MB1423:
x-microsoft-antispam-prvs: <SN1PR08MB142302C72160D9FBA0D0DEEFDA990@SN1PR08MB1423.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(127952516941037);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(3002001)(93006095)(93001095)(3231254)(944501410)(52105095)(10201501046)(149027)(150027)(6041310)(2016111802025)(20161123558120)(20161123564045)(20161123560045)(20161123562045)(6072148)(6043046)(201708071742011); SRVR:SN1PR08MB1423; BCL:0; PCL:0; RULEID:; SRVR:SN1PR08MB1423; 
x-forefront-prvs: 0667289FF8
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39380400002)(366004)(396003)(39830400003)(376002)(346002)(53754006)(199004)(189003)(13464003)(3660700001)(66066001)(53546011)(14454004)(110136005)(7736002)(105586002)(305945005)(33656002)(26005)(229853002)(7696005)(8936002)(6506007)(6436002)(316002)(5660300001)(2906002)(6116002)(3846002)(8676002)(59450400001)(81156014)(81166006)(68736007)(3280700002)(6246003)(186003)(5250100002)(478600001)(55016002)(486006)(11346002)(446003)(9686003)(99286004)(476003)(74482002)(102836004)(97736004)(86362001)(53936002)(106356001)(2900100001)(25786009)(76176011)(74316002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR08MB1423; H:SN1PR08MB1854.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: OooSWlx4t9wT4tGxonKkP5+Lmu0qILAHX9qvfQxP789oQoA2AXXJ8KqNH1fBljX8tQMALhfEKKQJs76nnoBb80G0TftpGYWNMp1gFJg3pjyUdbF8nKOT+lCKV9FvM8qMs54c6nepXwUSgp+rRWNFW01HZ0NXiX05/gKYzu5cTC0i1kFWpOAu6ve5xvZb73AN
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 0f8651fd-51df-49f2-756c-08d5b5f01aeb
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 0f8651fd-51df-49f2-756c-08d5b5f01aeb
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 May 2018 21:01:58.9960 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR08MB1423
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Ke3AAb1bYjaXCuFplO1z9GI1Hms>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2018 21:02:04 -0000

They *shouldn't* be unanticipated protocol errors, because both are negotia=
ted.  I would expect (or at least hope) that these will manifest as negotia=
tion failures at worst.

-----Original Message-----
From: Lucas Pardue [mailto:Lucas.Pardue@bbc.co.uk]=20
Sent: Wednesday, May 9, 2018 11:04 AM
To: Mike Bishop <mbishop@evequefou.be>; Sam Hurst-RD <samuelh@rd.bbc.co.uk>=
; IETF QUIC WG <quic@ietf.org>
Subject: RE: Clarification of transport and HTTP version compatibility

I think this all works fine in the current stage of specification.=20

Longer term, what is the failure case for interoperability where different =
implementations have  different rules for how to combine QUIC version and H=
TTP/QUIC version. Protocol error due to reception of unanticipated packets =
and or HTTP/QUIC frames?

Lucas
________________________________________
From: QUIC [quic-bounces@ietf.org] on behalf of Mike Bishop [mbishop@eveque=
fou.be]
Sent: 09 May 2018 18:18
To: Sam Hurst-RD; IETF QUIC WG
Subject: RE: Clarification of transport and HTTP version compatibility

There's no firm restriction, no.  While I find it likely that draft deploym=
ents will choose to keep matching versions, the only restriction that the H=
TTP draft currently imposes is that it be a version of QUIC which uses TLS =
as the handshake protocol.

-----Original Message-----
From: QUIC <quic-bounces@ietf.org> On Behalf Of Samuel Hurst
Sent: Wednesday, May 9, 2018 9:05 AM
To: IETF QUIC WG <quic@ietf.org>
Subject: Clarification of transport and HTTP version compatibility

Hi all,

Does the quic-transport version and the HTTP mapping version have to match?=
 For example, could you negotiate QUIC draft-11, but the HTTP side is still=
 using an older version (such as draft-09 to avoid the requirement of QPACK=
)?

As far as I understand it, the QUIC transport version is negotiated as part=
 of the TransportParams in the appropriate TLS extension, and the HTTP mapp=
ing version is negotiated by ALPN. So in the example above, would it be acc=
eptable to negotiate 0xff00000a as the transport protocol version, and then=
 have an ALPN string of "hq-09"?

I'm then assuming that a valid Alt-Svc header for my example could be as
follows:

Alt-Svc: hq-09=3D":4443";quic=3D"ff00000a"

The quic-tls draft mentions in Section 9.1 "The application-layer protocol =
MAY restrict the QUIC version that it can operate over", but none of the qu=
ic-http drafts that I've read list any such restriction.
Therefore, I'm then further assuming that it's safe to run whatever version=
 of the HTTP mapping I like, unless there's a compatibility matrix between =
the various specs that I'm missing?

Best Regards,
Sam


From nobody Wed May  9 14:43:05 2018
Return-Path: <Lucas.Pardue@bbc.co.uk>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63DD712DB6E for <quic@ietfa.amsl.com>; Wed,  9 May 2018 14:43:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 s9tWpGp-L81b for <quic@ietfa.amsl.com>; Wed,  9 May 2018 14:43:02 -0700 (PDT)
Received: from mailout0.cwwtf.bbc.co.uk (mailout0.cwwtf.bbc.co.uk [132.185.160.179]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2458A12DB6F for <quic@ietf.org>; Wed,  9 May 2018 14:42:58 -0700 (PDT)
Received: from BGB01XI1006.national.core.bbc.co.uk ([10.184.50.56]) by mailout0.cwwtf.bbc.co.uk (8.15.2/8.15.2) with ESMTP id w49Lgr1d025525; Wed, 9 May 2018 22:42:53 +0100 (BST)
Received: from BGB01XUD1012.national.core.bbc.co.uk ([10.161.14.10]) by BGB01XI1006.national.core.bbc.co.uk ([10.184.50.56]) with mapi id 14.03.0361.001; Wed, 9 May 2018 22:42:53 +0100
From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
To: Mike Bishop <mbishop@evequefou.be>, Sam Hurst-RD <samuelh@rd.bbc.co.uk>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Clarification of transport and HTTP version compatibility
Thread-Topic: Clarification of transport and HTTP version compatibility
Thread-Index: AQHT56+xKCNEYXqr2EueYoxG7/YhOKQnk0UAgAAbrQ+AACLaAIAAFAPX
Date: Wed, 9 May 2018 21:42:52 +0000
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A3BB2B6A9@bgb01xud1012>
References: <906fdff3-8009-238b-998b-4ea515a2684d@rd.bbc.co.uk>, <SN1PR08MB1854826DACF0454471CB162DDA990@SN1PR08MB1854.namprd08.prod.outlook.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB2B67C@bgb01xud1012>, <SN1PR08MB1854FC73444239C609552459DA990@SN1PR08MB1854.namprd08.prod.outlook.com>
In-Reply-To: <SN1PR08MB1854FC73444239C609552459DA990@SN1PR08MB1854.namprd08.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.19.161.213]
x-exclaimer-md-config: 1cd3ac1c-62e5-43f2-8404-6b688271c769
x-tm-as-product-ver: SMEX-11.0.0.4255-8.200.1013-23834.002
x-tm-as-result: No--15.322400-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/vOxm48oGNr6N1GZL-V7Uq8uWXn8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2018 21:43:04 -0000

I've not terribly familiar with the transport negotiation aspects, so I'm p=
robably missing something sorry.

I guess what is not clear to me is the question, who is responsible for ens=
uring a sane answer is negotiated? (I suspect no one). It gets more annoyin=
g if the client is acting on information provided to it via Alt-Svc, which =
is quite liberal to from the sender perspective (there are some rules for t=
he client defined in HTTP/QUIC 2.1.1.).

How I read things in the simple case was:

1) Transport version negotiation takes place and client chooses a version. =
Cryptographic handshake is next.
2) Client intitiates TLS 1.3 handshake with version info for revalidation, =
plus ALPN list of what it believes are application protocols that are compa=
tible with the chosen version of QUIC.
   a) POSSIBILITY 1 in a pathological case it always sends the same list re=
gardless of version.
3) Server selects an application protocol it believes is compatible with th=
e chosen version of QUIC.
  b) POSSIBILITY 2 naive implementations just assume "hq" works for everyth=
ing.
4) Client sends something the server is unhappy with and the connection bom=
bs with a protocol error.

Cheers
Lucas
________________________________________
From: Mike Bishop [mbishop@evequefou.be]
Sent: 09 May 2018 22:01
To: Lucas Pardue; Sam Hurst-RD; IETF QUIC WG
Subject: RE: Clarification of transport and HTTP version compatibility

They *shouldn't* be unanticipated protocol errors, because both are negotia=
ted.  I would expect (or at least hope) that these will manifest as negotia=
tion failures at worst.

-----Original Message-----
From: Lucas Pardue [mailto:Lucas.Pardue@bbc.co.uk]
Sent: Wednesday, May 9, 2018 11:04 AM
To: Mike Bishop <mbishop@evequefou.be>; Sam Hurst-RD <samuelh@rd.bbc.co.uk>=
; IETF QUIC WG <quic@ietf.org>
Subject: RE: Clarification of transport and HTTP version compatibility

I think this all works fine in the current stage of specification.

Longer term, what is the failure case for interoperability where different =
implementations have  different rules for how to combine QUIC version and H=
TTP/QUIC version. Protocol error due to reception of unanticipated packets =
and or HTTP/QUIC frames?

Lucas
________________________________________
From: QUIC [quic-bounces@ietf.org] on behalf of Mike Bishop [mbishop@eveque=
fou.be]
Sent: 09 May 2018 18:18
To: Sam Hurst-RD; IETF QUIC WG
Subject: RE: Clarification of transport and HTTP version compatibility

There's no firm restriction, no.  While I find it likely that draft deploym=
ents will choose to keep matching versions, the only restriction that the H=
TTP draft currently imposes is that it be a version of QUIC which uses TLS =
as the handshake protocol.

-----Original Message-----
From: QUIC <quic-bounces@ietf.org> On Behalf Of Samuel Hurst
Sent: Wednesday, May 9, 2018 9:05 AM
To: IETF QUIC WG <quic@ietf.org>
Subject: Clarification of transport and HTTP version compatibility

Hi all,

Does the quic-transport version and the HTTP mapping version have to match?=
 For example, could you negotiate QUIC draft-11, but the HTTP side is still=
 using an older version (such as draft-09 to avoid the requirement of QPACK=
)?

As far as I understand it, the QUIC transport version is negotiated as part=
 of the TransportParams in the appropriate TLS extension, and the HTTP mapp=
ing version is negotiated by ALPN. So in the example above, would it be acc=
eptable to negotiate 0xff00000a as the transport protocol version, and then=
 have an ALPN string of "hq-09"?

I'm then assuming that a valid Alt-Svc header for my example could be as
follows:

Alt-Svc: hq-09=3D":4443";quic=3D"ff00000a"

The quic-tls draft mentions in Section 9.1 "The application-layer protocol =
MAY restrict the QUIC version that it can operate over", but none of the qu=
ic-http drafts that I've read list any such restriction.
Therefore, I'm then further assuming that it's safe to run whatever version=
 of the HTTP mapping I like, unless there's a compatibility matrix between =
the various specs that I'm missing?

Best Regards,
Sam



-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specif=
ically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
immediately.
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
this.
-----------------------------


From nobody Wed May  9 15:44:24 2018
Return-Path: <mbishop@evequefou.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 90F0D12D7E2 for <quic@ietfa.amsl.com>; Wed,  9 May 2018 15:44:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 MHQOvm9DXGwb for <quic@ietfa.amsl.com>; Wed,  9 May 2018 15:44:07 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0133.outbound.protection.outlook.com [104.47.38.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C6DF612E055 for <quic@ietf.org>; Wed,  9 May 2018 15:43:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=MPFLkonBr96bHne3/QHCVr/BZIaZRcwI9P5QZiInP+E=; b=VJHmEZ+ybJ9vc4aAlcoXu6EcxIvJxjT+GPXKVUAAlQpTgJn1T5KhHz2lLPj1kyg4ieUL4B7//mQ+kSBvFTkOGmWvHqb9xa8vcG1UzL6AuQLzsQAYXuK5HNtoiaskep0est060MX71OcgAc/SnQCh+tLL0WsuMbQXurs19YRezhQ=
Received: from SN1PR08MB1854.namprd08.prod.outlook.com (10.169.39.8) by SN1PR08MB1342.namprd08.prod.outlook.com (10.162.1.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.755.16; Wed, 9 May 2018 22:43:53 +0000
Received: from SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d]) by SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d%13]) with mapi id 15.20.0735.018; Wed, 9 May 2018 22:43:53 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Lucas Pardue <Lucas.Pardue@bbc.co.uk>, Sam Hurst-RD <samuelh@rd.bbc.co.uk>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Clarification of transport and HTTP version compatibility
Thread-Topic: Clarification of transport and HTTP version compatibility
Thread-Index: AQHT56+xI3vQwOQ++kOo1AZLBRUIXaQno4FAgAANUQCAADE84IAAC+8AgAALO3A=
Date: Wed, 9 May 2018 22:43:52 +0000
Message-ID: <SN1PR08MB1854232CFA318E21E062BBE3DA990@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <906fdff3-8009-238b-998b-4ea515a2684d@rd.bbc.co.uk>, <SN1PR08MB1854826DACF0454471CB162DDA990@SN1PR08MB1854.namprd08.prod.outlook.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB2B67C@bgb01xud1012>, <SN1PR08MB1854FC73444239C609552459DA990@SN1PR08MB1854.namprd08.prod.outlook.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB2B6A9@bgb01xud1012>
In-Reply-To: <7CF7F94CB496BF4FAB1676F375F9666A3BB2B6A9@bgb01xud1012>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [38.134.241.6]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN1PR08MB1342; 7:h+WdsylwMuQ/jhbmy5zmeXZVBIx5bA8GMlMGEMIYlCh9jhiZLaNhAf2eh0J5c/DDSo1ZyDHYjAiO1bgxcPDZsLqlJIVFwD0Akyk5NGPbRXYOfa8GcA9VW/SLfO99dyHebpidDaPDNpT5NLAMdaC0/umwwH7BXMT02faFQ7KAEcvONXWeketnLxxm90UTdpHZOmOckFVK5pD58KZvK53i6PrbsNzmdWFPcuAu/tTeIRQ9H3V8mKz2RoO03nDuK8Lh
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(5600026)(2017052603328)(7153060)(7193020); SRVR:SN1PR08MB1342; 
x-ms-traffictypediagnostic: SN1PR08MB1342:
x-microsoft-antispam-prvs: <SN1PR08MB13424E6F0A9A15D86B84436DDA990@SN1PR08MB1342.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(204407124797145)(35073007944872)(127952516941037); 
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3231254)(944501410)(52105095)(93006095)(93001095)(10201501046)(3002001)(149027)(150027)(6041310)(20161123562045)(20161123558120)(2016111802025)(20161123564045)(20161123560045)(6043046)(6072148)(201708071742011); SRVR:SN1PR08MB1342; BCL:0; PCL:0; RULEID:; SRVR:SN1PR08MB1342; 
x-forefront-prvs: 0667289FF8
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(346002)(39380400002)(39830400003)(396003)(366004)(199004)(189003)(53754006)(13464003)(7736002)(486006)(55016002)(11346002)(2900100001)(476003)(6246003)(53386004)(74316002)(6116002)(8676002)(8936002)(9686003)(6306002)(33656002)(53936002)(81156014)(74482002)(5660300001)(2906002)(25786009)(14454004)(305945005)(81166006)(3846002)(478600001)(446003)(6436002)(3660700001)(3280700002)(102836004)(105586002)(106356001)(66066001)(966005)(53546011)(6506007)(59450400001)(316002)(186003)(86362001)(76176011)(110136005)(229853002)(93886005)(7696005)(5250100002)(99286004)(97736004)(68736007)(26005)(5890100001); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR08MB1342; H:SN1PR08MB1854.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: iCUpVcQEZLY37s0bYGxrSlRervnT1hmfA+nWCQEvaARLkIwnKbhReG+FyK23ThThr4oRQRWtcLu9v9ZAaqfi6WWCM6g6AxcBhQHbDgU/CRGe8ddzIL32ZAlasFWRwKQEAIYVtQGeB8O1APlVIWiLGThHkQ6IWbT2GHig7HKyiDax4tbfyxahR9QCITLaXVdf
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: b8ebe604-0620-41b0-cd59-08d5b5fe571e
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: b8ebe604-0620-41b0-cd59-08d5b5fe571e
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 May 2018 22:43:52.4656 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR08MB1342
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/4OG52SSp3ItD52hZAEP4co_Vq6g>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2018 22:44:11 -0000

I think your description of the process is correct.  But for something to f=
ail post-handshake, both possibilities have to occur, not just one.  If a c=
lient naively offers an application protocol that doesn't work over the sel=
ected version, the server ought to ignore it (and abort the connection if i=
t was the only one offered).  If a client correctly filters its list, the s=
erver can't accept what isn't offered even if it's buggy.  So if only one s=
ide is broken, what happens should be that the TLS handshake will fail to s=
elect an application-level protocol and the connection fails before any req=
uests are sent.

What the TLS draft says about ALPN and versions is:
> If the server cannot select a compatible combination of application proto=
col and QUIC version, it MUST abort the connection.=20
> A client MUST abort a connection if the server picks an incompatible comb=
ination of QUIC version and ALPN identifier.

It should be implied, but might be worth explicitly stating, that failure t=
o agree on an ALPN is incompatible with all QUIC versions, always fatal.

>From the Alt-Svc perspective, the ALPN is proscriptive (7838 says fail if t=
hat particular ALPN isn't accepted) and the QUIC version is only advisory. =
 If the advertised version of HTTP/QUIC is no longer supported, they'll fai=
l back to HTTPS, get a new Alt-Svc entry, and try again later.  If the adve=
rtised version of HTTP/QUIC *is* supported but a new transport version has =
become available, the client might try that if it believes the new transpor=
t version to be compatible with its existing HQ version.  If that works, it=
 might get an updated Alt-Svc entry telling it that a new HQ version is ava=
ilable as well.

Now, if both sides have mutually agreed to speak an incompatible pair of ap=
plication protocol and transport versions, then you're in uncharted territo=
ry.  If they both expect the same things about how those interact, it'll wo=
rk; if not, it won't.  That's basically the same as anyone who mutually neg=
otiates an option but disagrees about what the option means, and that's har=
d to guard against.

-----Original Message-----
From: Lucas Pardue [mailto:Lucas.Pardue@bbc.co.uk]=20
Sent: Wednesday, May 9, 2018 2:43 PM
To: Mike Bishop <mbishop@evequefou.be>; Sam Hurst-RD <samuelh@rd.bbc.co.uk>=
; IETF QUIC WG <quic@ietf.org>
Subject: RE: Clarification of transport and HTTP version compatibility

I've not terribly familiar with the transport negotiation aspects, so I'm p=
robably missing something sorry.

I guess what is not clear to me is the question, who is responsible for ens=
uring a sane answer is negotiated? (I suspect no one). It gets more annoyin=
g if the client is acting on information provided to it via Alt-Svc, which =
is quite liberal to from the sender perspective (there are some rules for t=
he client defined in HTTP/QUIC 2.1.1.).

How I read things in the simple case was:

1) Transport version negotiation takes place and client chooses a version. =
Cryptographic handshake is next.
2) Client intitiates TLS 1.3 handshake with version info for revalidation, =
plus ALPN list of what it believes are application protocols that are compa=
tible with the chosen version of QUIC.
   a) POSSIBILITY 1 in a pathological case it always sends the same list re=
gardless of version.
3) Server selects an application protocol it believes is compatible with th=
e chosen version of QUIC.
  b) POSSIBILITY 2 naive implementations just assume "hq" works for everyth=
ing.
4) Client sends something the server is unhappy with and the connection bom=
bs with a protocol error.

Cheers
Lucas
________________________________________
From: Mike Bishop [mbishop@evequefou.be]
Sent: 09 May 2018 22:01
To: Lucas Pardue; Sam Hurst-RD; IETF QUIC WG
Subject: RE: Clarification of transport and HTTP version compatibility

They *shouldn't* be unanticipated protocol errors, because both are negotia=
ted.  I would expect (or at least hope) that these will manifest as negotia=
tion failures at worst.

-----Original Message-----
From: Lucas Pardue [mailto:Lucas.Pardue@bbc.co.uk]
Sent: Wednesday, May 9, 2018 11:04 AM
To: Mike Bishop <mbishop@evequefou.be>; Sam Hurst-RD <samuelh@rd.bbc.co.uk>=
; IETF QUIC WG <quic@ietf.org>
Subject: RE: Clarification of transport and HTTP version compatibility

I think this all works fine in the current stage of specification.

Longer term, what is the failure case for interoperability where different =
implementations have  different rules for how to combine QUIC version and H=
TTP/QUIC version. Protocol error due to reception of unanticipated packets =
and or HTTP/QUIC frames?

Lucas
________________________________________
From: QUIC [quic-bounces@ietf.org] on behalf of Mike Bishop [mbishop@eveque=
fou.be]
Sent: 09 May 2018 18:18
To: Sam Hurst-RD; IETF QUIC WG
Subject: RE: Clarification of transport and HTTP version compatibility

There's no firm restriction, no.  While I find it likely that draft deploym=
ents will choose to keep matching versions, the only restriction that the H=
TTP draft currently imposes is that it be a version of QUIC which uses TLS =
as the handshake protocol.

-----Original Message-----
From: QUIC <quic-bounces@ietf.org> On Behalf Of Samuel Hurst
Sent: Wednesday, May 9, 2018 9:05 AM
To: IETF QUIC WG <quic@ietf.org>
Subject: Clarification of transport and HTTP version compatibility

Hi all,

Does the quic-transport version and the HTTP mapping version have to match?=
 For example, could you negotiate QUIC draft-11, but the HTTP side is still=
 using an older version (such as draft-09 to avoid the requirement of QPACK=
)?

As far as I understand it, the QUIC transport version is negotiated as part=
 of the TransportParams in the appropriate TLS extension, and the HTTP mapp=
ing version is negotiated by ALPN. So in the example above, would it be acc=
eptable to negotiate 0xff00000a as the transport protocol version, and then=
 have an ALPN string of "hq-09"?

I'm then assuming that a valid Alt-Svc header for my example could be as
follows:

Alt-Svc: hq-09=3D":4443";quic=3D"ff00000a"

The quic-tls draft mentions in Section 9.1 "The application-layer protocol =
MAY restrict the QUIC version that it can operate over", but none of the qu=
ic-http drafts that I've read list any such restriction.
Therefore, I'm then further assuming that it's safe to run whatever version=
 of the HTTP mapping I like, unless there's a compatibility matrix between =
the various specs that I'm missing?

Best Regards,
Sam



-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the BBC unless specifically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender imme=
diately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
-----------------------------


From nobody Wed May  9 16:24:37 2018
Return-Path: <Lucas.Pardue@bbc.co.uk>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F63012DA1D for <quic@ietfa.amsl.com>; Wed,  9 May 2018 16:24:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 TNv689fHCMp0 for <quic@ietfa.amsl.com>; Wed,  9 May 2018 16:24:34 -0700 (PDT)
Received: from mailout0.cwwtf.bbc.co.uk (mailout0.cwwtf.bbc.co.uk [132.185.160.179]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C2E7E126CF9 for <quic@ietf.org>; Wed,  9 May 2018 16:24:33 -0700 (PDT)
Received: from BGB01XI1010.national.core.bbc.co.uk (bgb01xi1010.national.core.bbc.co.uk [10.161.14.14]) by mailout0.cwwtf.bbc.co.uk (8.15.2/8.15.2) with ESMTP id w49NOS7T004196; Thu, 10 May 2018 00:24:28 +0100 (BST)
Received: from BGB01XUD1012.national.core.bbc.co.uk ([10.161.14.10]) by BGB01XI1010.national.core.bbc.co.uk ([10.161.14.14]) with mapi id 14.03.0361.001; Thu, 10 May 2018 00:24:27 +0100
From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
To: Mike Bishop <mbishop@evequefou.be>, Sam Hurst-RD <samuelh@rd.bbc.co.uk>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Clarification of transport and HTTP version compatibility
Thread-Topic: Clarification of transport and HTTP version compatibility
Thread-Index: AQHT56+xKCNEYXqr2EueYoxG7/YhOKQnk0UAgAAbrQ+AACLaAIAAFAPXgAAIdgCAABryEA==
Date: Wed, 9 May 2018 23:24:26 +0000
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A3BB2B6BE@bgb01xud1012>
References: <906fdff3-8009-238b-998b-4ea515a2684d@rd.bbc.co.uk>, <SN1PR08MB1854826DACF0454471CB162DDA990@SN1PR08MB1854.namprd08.prod.outlook.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB2B67C@bgb01xud1012>, <SN1PR08MB1854FC73444239C609552459DA990@SN1PR08MB1854.namprd08.prod.outlook.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB2B6A9@bgb01xud1012>, <SN1PR08MB1854232CFA318E21E062BBE3DA990@SN1PR08MB1854.namprd08.prod.outlook.com>
In-Reply-To: <SN1PR08MB1854232CFA318E21E062BBE3DA990@SN1PR08MB1854.namprd08.prod.outlook.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.19.161.213]
x-exclaimer-md-config: c91d45b2-6e10-4209-9543-d9970fac71b7
x-tm-as-product-ver: SMEX-11.0.0.4255-8.200.1013-23834.003
x-tm-as-result: No--21.481000-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/4KwzNw44DJ3pWkA39TYhTMFzix4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 09 May 2018 23:24:36 -0000

Thanks for that explanation Mike, it makes more sense now. =0A=
=0A=
> It should be implied, but might be worth explicitly stating, that failure=
 to agree on an ALPN is incompatible with all QUIC versions, always fatal.=
=0A=
=0A=
I don't know if it needs explicit statement. RFC 7301 section 3.2 states th=
at "In the event that the server supports no=0A=
 protocols that the client advertises, then the server SHALL respond with a=
 fatal "no_application_protocol" alert."=0A=
=0A=
Cheers=0A=
Lucas=0A=
=0A=
-----Original Message-----=0A=
From: Lucas Pardue [mailto:Lucas.Pardue@bbc.co.uk]=0A=
Sent: Wednesday, May 9, 2018 2:43 PM=0A=
To: Mike Bishop <mbishop@evequefou.be>; Sam Hurst-RD <samuelh@rd.bbc.co.uk>=
; IETF QUIC WG <quic@ietf.org>=0A=
Subject: RE: Clarification of transport and HTTP version compatibility=0A=
=0A=
I've not terribly familiar with the transport negotiation aspects, so I'm p=
robably missing something sorry.=0A=
=0A=
I guess what is not clear to me is the question, who is responsible for ens=
uring a sane answer is negotiated? (I suspect no one). It gets more annoyin=
g if the client is acting on information provided to it via Alt-Svc, which =
is quite liberal to from the sender perspective (there are some rules for t=
he client defined in HTTP/QUIC 2.1.1.).=0A=
=0A=
How I read things in the simple case was:=0A=
=0A=
1) Transport version negotiation takes place and client chooses a version. =
Cryptographic handshake is next.=0A=
2) Client intitiates TLS 1.3 handshake with version info for revalidation, =
plus ALPN list of what it believes are application protocols that are compa=
tible with the chosen version of QUIC.=0A=
   a) POSSIBILITY 1 in a pathological case it always sends the same list re=
gardless of version.=0A=
3) Server selects an application protocol it believes is compatible with th=
e chosen version of QUIC.=0A=
  b) POSSIBILITY 2 naive implementations just assume "hq" works for everyth=
ing.=0A=
4) Client sends something the server is unhappy with and the connection bom=
bs with a protocol error.=0A=
=0A=
Cheers=0A=
Lucas=0A=
________________________________________=0A=
From: Mike Bishop [mbishop@evequefou.be]=0A=
Sent: 09 May 2018 22:01=0A=
To: Lucas Pardue; Sam Hurst-RD; IETF QUIC WG=0A=
Subject: RE: Clarification of transport and HTTP version compatibility=0A=
=0A=
They *shouldn't* be unanticipated protocol errors, because both are negotia=
ted.  I would expect (or at least hope) that these will manifest as negotia=
tion failures at worst.=0A=
=0A=
-----Original Message-----=0A=
From: Lucas Pardue [mailto:Lucas.Pardue@bbc.co.uk]=0A=
Sent: Wednesday, May 9, 2018 11:04 AM=0A=
To: Mike Bishop <mbishop@evequefou.be>; Sam Hurst-RD <samuelh@rd.bbc.co.uk>=
; IETF QUIC WG <quic@ietf.org>=0A=
Subject: RE: Clarification of transport and HTTP version compatibility=0A=
=0A=
I think this all works fine in the current stage of specification.=0A=
=0A=
Longer term, what is the failure case for interoperability where different =
implementations have  different rules for how to combine QUIC version and H=
TTP/QUIC version. Protocol error due to reception of unanticipated packets =
and or HTTP/QUIC frames?=0A=
=0A=
Lucas=0A=
________________________________________=0A=
From: QUIC [quic-bounces@ietf.org] on behalf of Mike Bishop [mbishop@eveque=
fou.be]=0A=
Sent: 09 May 2018 18:18=0A=
To: Sam Hurst-RD; IETF QUIC WG=0A=
Subject: RE: Clarification of transport and HTTP version compatibility=0A=
=0A=
There's no firm restriction, no.  While I find it likely that draft deploym=
ents will choose to keep matching versions, the only restriction that the H=
TTP draft currently imposes is that it be a version of QUIC which uses TLS =
as the handshake protocol.=0A=
=0A=
-----Original Message-----=0A=
From: QUIC <quic-bounces@ietf.org> On Behalf Of Samuel Hurst=0A=
Sent: Wednesday, May 9, 2018 9:05 AM=0A=
To: IETF QUIC WG <quic@ietf.org>=0A=
Subject: Clarification of transport and HTTP version compatibility=0A=
=0A=
Hi all,=0A=
=0A=
Does the quic-transport version and the HTTP mapping version have to match?=
 For example, could you negotiate QUIC draft-11, but the HTTP side is still=
 using an older version (such as draft-09 to avoid the requirement of QPACK=
)?=0A=
=0A=
As far as I understand it, the QUIC transport version is negotiated as part=
 of the TransportParams in the appropriate TLS extension, and the HTTP mapp=
ing version is negotiated by ALPN. So in the example above, would it be acc=
eptable to negotiate 0xff00000a as the transport protocol version, and then=
 have an ALPN string of "hq-09"?=0A=
=0A=
I'm then assuming that a valid Alt-Svc header for my example could be as=0A=
follows:=0A=
=0A=
Alt-Svc: hq-09=3D":4443";quic=3D"ff00000a"=0A=
=0A=
The quic-tls draft mentions in Section 9.1 "The application-layer protocol =
MAY restrict the QUIC version that it can operate over", but none of the qu=
ic-http drafts that I've read list any such restriction.=0A=
Therefore, I'm then further assuming that it's safe to run whatever version=
 of the HTTP mapping I like, unless there's a compatibility matrix between =
the various specs that I'm missing?=0A=
=0A=
Best Regards,=0A=
Sam=0A=
=0A=
=0A=
=0A=
-----------------------------=0A=
http://www.bbc.co.uk=0A=
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the BBC unless specifically stated.=0A=
If you have received it in=0A=
error, please delete it from your system.=0A=
Do not use, copy or disclose the=0A=
information in any way nor act in reliance on it and notify the sender imme=
diately.=0A=
Please note that the BBC monitors e-mails sent or received.=0A=
Further communication will signify your consent to this.=0A=
-----------------------------=0A=


From nobody Thu May 10 05:50:20 2018
Return-Path: <c@gryning.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A1E4A12D883 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 05:50:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level: 
X-Spam-Status: No, score=-2.609 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gryning-com.20150623.gappssmtp.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 cXAK9dusNDL9 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 05:50:14 -0700 (PDT)
Received: from mail-lf0-x235.google.com (mail-lf0-x235.google.com [IPv6:2a00:1450:4010:c07::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3A78E1275AB for <quic@ietf.org>; Thu, 10 May 2018 05:50:14 -0700 (PDT)
Received: by mail-lf0-x235.google.com with SMTP id t129-v6so2807959lff.3 for <quic@ietf.org>; Thu, 10 May 2018 05:50:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gryning-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0s/vCrkmQGVG9bnxM6blDr3P4Q97LYzmEdCDZgFtXYs=; b=Kcaj/YfwC0jMMQGqo1PxX9tp5wUnY2I2e6OhhIgEOgceClQN46pgm9xS76pxK3asDi lW0uncXLcl0FLbrrq07xiMY8Mhx8KvkMmt/+JcgQQFe6IndxcfzJ2AU2k9+VhOhu6tcd nHenNVoCsjyLXvB7ESGJ+aSOSEPddhyHWjwqFyjitV690l0P4OILBZQBHcHS+bLEts2D jCaSdJxfWp8cOS1pYooufzE0XIueaCX5U/6jTdaYpsoaZ0I/CCwhAhpOMl5W7XshnYxV i+jlz0G2qnYwf2wF8N0Ra+k9eGK+hHL5PGQCtNvlC6w8wEdRV+5/Rql2CA+VJHbXrfmB BiqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0s/vCrkmQGVG9bnxM6blDr3P4Q97LYzmEdCDZgFtXYs=; b=gNGQkhhGoekssM248/p56AkpiaXxOiBpaToPnEDaySpGleG4l+nykd4poqtw/pky0M EtX0M8m+J7CDle2xaQQmvp1XbppSfnNqGSmeKlyvnKOCUjm5sFgKBLb5yQ2h/zhWF/6F nTY0iWQTF+dCj5+W1jMt+sWD69Ab7ShHuR0lKAqEsPOSV0jQvd6mrzA6O26xwHciLv04 UWI88jEsl4UahaR3w2K9+QiLCwQ8nZ89Xr5skAR+bKRtza4S+hWi7xKZPpMd5rtS56TO xCW7Uvo+QWfFfla92WI2srqx8mA2Rpk+bsUEc+NJ+nOTPpn8jTa6l0MrRvPdCj7UkkfB SRnw==
X-Gm-Message-State: ALKqPwct5xbZACRJiCIhApBpT/fBqzBx5QsOZFtlbOBnB7TD6tlrGERl zIp40e19yfgac1Tq9IAxQdYsAtcNTWhCs9RLSIcOnw==
X-Google-Smtp-Source: AB8JxZptleoyHeF2lusWWbh9NQBpvs4c8NVt674zZkgBpOIo6qFKSjXit653VmqOp/Ek4SG5g7Q3OVHzq7aC9ROEbbg=
X-Received: by 2002:a19:d853:: with SMTP id p80-v6mr1019026lfg.36.1525956612330;  Thu, 10 May 2018 05:50:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a19:d012:0:0:0:0:0 with HTTP; Thu, 10 May 2018 05:50:11 -0700 (PDT)
X-Originating-IP: [2001:41c1:4:8000:186e:9af4:4c85:721a]
In-Reply-To: <A6F55755-D7E1-40E4-8EC3-D5FE77A2EDBE@fb.com>
References: <CY4PR21MB0630CE4DE6BA4EDF54A1FEB1B6A40@CY4PR21MB0630.namprd21.prod.outlook.com> <CAN1APde93+S8CP-KcZmqPKCCvsGRiq6ECPUoh_Qk0j9hqs8h0Q@mail.gmail.com> <SN1PR08MB1854E64D7C370BF0A7456977DABB0@SN1PR08MB1854.namprd08.prod.outlook.com> <CAKcm_gNhsHxXM77FjRj-Wh4JxA21NAWKXX3KBT=eZJsCdacM7Q@mail.gmail.com> <DB6PR10MB1766789B25E31EBE70564BD3ACBA0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <SN1PR08MB18548155722C665FFD45CC4DDABA0@SN1PR08MB1854.namprd08.prod.outlook.com> <CAKcm_gMYf6AbHgvg+WKv-woQCtzz9WztiEDf-iRUjKw63Qx=9Q@mail.gmail.com> <1F436ED13A22A246A59CA374CBC543998B60C7AD@ORSMSX111.amr.corp.intel.com> <CAN1APdc3y0EwFqeYVvZs7MtBHhS_9CzwGmcwRqi_6GHWzF3_2Q@mail.gmail.com> <1F436ED13A22A246A59CA374CBC543998B60C851@ORSMSX111.amr.corp.intel.com> <CAN1APdcPkO-HfXqqvjeee6K8U8KSZQdtx=6fW1vZo+H6pKfzzQ@mail.gmail.com> <CAKcm_gP8TRPT7yi1y=mU5Fvq7xB5-1ieyKFLQMPomfabYbkcxA@mail.gmail.com> <bf540ec1f6f045aca1cf2379380630b5@usma1ex-dag1mb5.msg.corp.akamai.com> <SN1PR08MB185446750FCDA2B58C9833C8DA890@SN1PR08MB1854.namprd08.prod.outlook.com> <CACsn0cmJcAxORo4Cd-qyGJL3ZOT5Yz0WgdMqv_AGi4DjedyzFA@mail.gmail.com> <A6F55755-D7E1-40E4-8EC3-D5FE77A2EDBE@fb.com>
From: craigt <c@gryning.com>
Date: Thu, 10 May 2018 13:50:11 +0100
Message-ID: <CAK-1kemWAW+2Sk5aKJ+RXKUAyjFii4MRH=xK7SE0mr=tbCiRfw@mail.gmail.com>
Subject: Re: Impact of hardware offloads on network stack performance
To: Roberto Peon <fenix@fb.com>
Cc: Watson Ladd <watsonbladd@gmail.com>, Mike Bishop <mbishop@evequefou.be>,  Praveen Balasubramanian <pravb@microsoft.com>, "Lubashev, Igor" <ilubashe@akamai.com>,  Ian Swett <ianswett=40google.com@dmarc.ietf.org>,  =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>,  IETF QUIC WG <quic@ietf.org>, "Deval, Manasi" <manasi.deval@intel.com>
Content-Type: multipart/alternative; boundary="000000000000d22b22056bd97523"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/JXWQV1yEQiSJzSrP4zbKQr3Mj6M>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 12:50:19 -0000

--000000000000d22b22056bd97523
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Has anyone experimented with the zerocopy socket interfaces for exactly
this use case?
  https://netdevconf.org/2.1/papers/netdev.pdf

It would seem that is a more natural fit to the assertions made by several
of the authors surrounding packetisation.
I'm unaware if Windows/BSD have similar interfaces/implementations.

c


On 30 April 2018 at 21:37, Roberto Peon <fenix@fb.com> wrote:

> QUIC (mostly) doesn=E2=80=99t do that (rexmit a packet verbatim)=E2=80=94=
you=E2=80=99d need a new
> packet# for the rexmitted packet.
>
> -=3DR
>
>
>
> *From: *QUIC <quic-bounces@ietf.org> on behalf of Watson Ladd <
> watsonbladd@gmail.com>
> *Date: *Monday, April 23, 2018 at 1:56 PM
> *To: *Mike Bishop <mbishop@evequefou.be>
> *Cc: *Praveen Balasubramanian <pravb@microsoft.com>, "Lubashev, Igor" <
> ilubashe@akamai.com>, Ian Swett <ianswett=3D40google.com@dmarc.ietf.org>,
> Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@gmail.com>, IETF QUIC WG <qui=
c@ietf.org>,
> "Deval, Manasi" <manasi.deval@intel.com>
> *Subject: *Re: Impact of hardware offloads on network stack performance
>
>
>
>
>
>
>
> On Mon, Apr 23, 2018 at 1:06 PM, Mike Bishop <mbishop@evequefou.be> wrote=
:
>
> I agree =E2=80=93 the point of offloading the crypto is not only to spare=
 that
> cost on the CPU, though that can be useful, it=E2=80=99s to enable furthe=
r offloads
> that can=E2=80=99t be done on the encrypted packet.
>
>
>
> LRO that could simply group packets by CID and deliver a single batch of
> packets from a single CID in a single invocation seems like a great first
> step, and doesn=E2=80=99t even require crypto offload.  Once you have cry=
pto
> offload, of course those packets per CID could be delivered already
> decrypted.  I=E2=80=99d want to see data on whether there=E2=80=99s value=
 in making the
> received data look like one huge packet when there=E2=80=99s not a single
> bytestream, but that=E2=80=99s not something we need to specify here.
>
>
>
> LSO is more interesting, and the challenge there is that the transport
> stack still needs to know what data was in which packet so that it can do
> loss recovery properly.  QUIC explicitly disallows fragmentation of the U=
DP
> datagram, for the =E2=80=9Cpainful and potentially non-deterministic=E2=
=80=9D reasons you
> referenced.
>
>
>
> Forgive my complete ignorance, but doesn't it just need to know what
> packet it sent?
>
> More explicitly the sender would maintain a queue of sendable packets, an=
d
> mark which have been sent. Acknowledged packets are removed from the queu=
e.
> In event of loss, they simply retransmit the same packet. It's up to high=
er
> layers to pick the right size of packet and take data from the individual
> QUIC streams. If you wanted to expose the stream structure, that sounds a
> lot more complicated.
>
>
> Sincerely,
>
> Watson
>
>
>
>
>

--000000000000d22b22056bd97523
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Has anyone experimented with the zerocopy socket interface=
s for exactly this use case?<div>=C2=A0 <a href=3D"https://netdevconf.org/2=
.1/papers/netdev.pdf">https://netdevconf.org/2.1/papers/netdev.pdf</a><br><=
/div><div><br></div><div>It would seem that is a more natural fit to the as=
sertions made by several of the authors surrounding packetisation.</div><di=
v>I&#39;m unaware if Windows/BSD have similar interfaces/implementations.</=
div><div><br></div><div>c</div><div><br></div></div><div class=3D"gmail_ext=
ra"><br><div class=3D"gmail_quote">On 30 April 2018 at 21:37, Roberto Peon =
<span dir=3D"ltr">&lt;<a href=3D"mailto:fenix@fb.com" target=3D"_blank">fen=
ix@fb.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=
=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_5002203081352271915WordSection1">
<p class=3D"MsoNormal">QUIC (mostly) doesn=E2=80=99t do that (rexmit a pack=
et verbatim)=E2=80=94you=E2=80=99d need a new packet# for the rexmitted pac=
ket.<u></u><u></u></p>
<p class=3D"MsoNormal">-=3DR<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:12.0pt;color:black">From=
: </span></b><span style=3D"font-size:12.0pt;color:black">QUIC &lt;<a href=
=3D"mailto:quic-bounces@ietf.org" target=3D"_blank">quic-bounces@ietf.org</=
a>&gt; on behalf of Watson Ladd &lt;<a href=3D"mailto:watsonbladd@gmail.com=
" target=3D"_blank">watsonbladd@gmail.com</a>&gt;<br>
<b>Date: </b>Monday, April 23, 2018 at 1:56 PM<br>
<b>To: </b>Mike Bishop &lt;<a href=3D"mailto:mbishop@evequefou.be" target=
=3D"_blank">mbishop@evequefou.be</a>&gt;<br>
<b>Cc: </b>Praveen Balasubramanian &lt;<a href=3D"mailto:pravb@microsoft.co=
m" target=3D"_blank">pravb@microsoft.com</a>&gt;, &quot;Lubashev, Igor&quot=
; &lt;<a href=3D"mailto:ilubashe@akamai.com" target=3D"_blank">ilubashe@aka=
mai.com</a>&gt;, Ian Swett &lt;ianswett=3D<a href=3D"mailto:40google.com@dm=
arc.ietf.org" target=3D"_blank">40google.com@dmarc.<wbr>ietf.org</a>&gt;, M=
ikkel Fahn=C3=B8e J=C3=B8rgensen &lt;<a href=3D"mailto:mikkelfj@gmail.com" =
target=3D"_blank">mikkelfj@gmail.com</a>&gt;, IETF QUIC WG &lt;<a href=3D"m=
ailto:quic@ietf.org" target=3D"_blank">quic@ietf.org</a>&gt;, &quot;Deval, =
Manasi&quot; &lt;<a href=3D"mailto:manasi.deval@intel.com" target=3D"_blank=
">manasi.deval@intel.com</a>&gt;<span class=3D""><br>
<b>Subject: </b>Re: Impact of hardware offloads on network stack performanc=
e<u></u><u></u></span></span></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><a name=3D"m_5002203081352271915__MailOriginalBody">=
<u></u>=C2=A0<u></u></a></p>
<div>
<p class=3D"MsoNormal"><span><u></u>=C2=A0<u></u></span></p>
<div>
<p class=3D"MsoNormal"><span>On Mon, Apr 23, 2018 at 1:06 PM, Mike Bishop &=
lt;</span><a href=3D"mailto:mbishop@evequefou.be" target=3D"_blank"><span>m=
bishop@evequefou.be</span><span></span></a><span>&gt;
 wrote:<u></u><u></u></span></p><div><div class=3D"h5">
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal"><span>I agree =E2=80=93 the point of offloading the =
crypto is not only to spare that cost on the CPU, though that can be useful=
, it=E2=80=99s to enable further
 offloads that can=E2=80=99t be done on the encrypted packet.<u></u><u></u>=
</span></p>
<p class=3D"MsoNormal"><span>=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span>LRO that could simply group packets by CID and=
 deliver a single batch of packets from a single CID in a single invocation=
 seems like
 a great first step, and doesn=E2=80=99t even require crypto offload.=C2=A0=
 Once you have crypto offload, of course those packets per CID could be del=
ivered already decrypted.=C2=A0 I=E2=80=99d want to see data on whether the=
re=E2=80=99s value in making the received data look like one huge
 packet when there=E2=80=99s not a single bytestream, but that=E2=80=99s no=
t something we need to specify here.<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span>=C2=A0<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span>LSO is more interesting, and the challenge the=
re is that the transport stack still needs to know what data was in which p=
acket so that
 it can do loss recovery properly.=C2=A0 QUIC explicitly disallows fragment=
ation of the UDP datagram, for the =E2=80=9C<span style=3D"color:#1f497d">p=
ainful and potentially non-deterministic</span>=E2=80=9D reasons you refere=
nced.<u></u><u></u></span></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>Forgive my complete ignorance, but doesn&#39;t=
 it just need to know what packet it sent?<br>
<br>
More explicitly the sender would maintain a queue of sendable packets, and =
mark which have been sent. Acknowledged packets are removed from the queue.=
 In event of loss, they simply retransmit the same packet. It&#39;s up to h=
igher layers to pick the right size
 of packet and take data from the individual QUIC streams. If you wanted to=
 expose the stream structure, that sounds a lot more complicated.<u></u><u>=
</u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span><br>
Sincerely,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>Watson<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span><u></u>=C2=A0<u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span><u></u>=C2=A0<u></u></span></p>
</div>
</div></div></div>
</div>
</div>
</div>
</div>

</blockquote></div><br></div>

--000000000000d22b22056bd97523--


From nobody Thu May 10 06:31:04 2018
Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 25F3312D969 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 06:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.697
X-Spam-Level: 
X-Spam-Status: No, score=-2.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 UdhhDC432Yhp for <quic@ietfa.amsl.com>; Thu, 10 May 2018 06:30:59 -0700 (PDT)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E34F812DA19 for <quic@ietf.org>; Thu, 10 May 2018 06:30:57 -0700 (PDT)
Received: by mail-io0-x233.google.com with SMTP id t23-v6so2980085ioc.10 for <quic@ietf.org>; Thu, 10 May 2018 06:30:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=kJU9Iej97Itqjb3+nUwU/OCR0ZTdISGuNND0WVECUHo=; b=pao5+ZYsHG7BaXf2LLtrJ7YatClL1zwNTe4QR2KlbDPK95VbWTwkej74xKiJXBH+7I yfH2/xuQVj6mxxFz5caWjnw+SbC5Vf3DPRWkIMzyVV9DgLksIJ9AnK8nutj70jOqDPFE bVhbLTeRJicUX6ka3w7DX5gadsOdxu/tcjuVqX5wy4aT05YPMvpyxhdo+eVl2hWze+uv FCjIqlAyj+xooDhfK6KLOIuzodbsMW7df2aIYHLuLvj+bx92tLFPgOV77u/Q8VYMTWkt GNZ2nlO1L6FOPRGm3h/ohd72HP6Td8qacumgZ67nQk5K2o/ZI0cC2W4PGgjeuiwFUZm8 yYXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=kJU9Iej97Itqjb3+nUwU/OCR0ZTdISGuNND0WVECUHo=; b=Xt4gVI9bS/nSiuJIjToOjhw1XzCF4AGjAmEaOg9SekXRPB1FtegF7kpJ2RC+WuIRrY rgwVKhavLcD8Zj/Sv7YBoYJFdlxpJRyTc5l1lDYYKcK/mib2yCHST1JqbH7gNw+/SQsa Zpb8SFHZNccfyNNHY7E3CKGlErcGBrCaj6Ypz72hGY6ZSQQNps1gIzpxu4QA3ddqdOh3 Jcew+3tzqYerkUO0ddmCvsP/wGU3g1B/NvPilE5sEqHKQ0JTvPh6w19JAgsLd+YuO2GA cbm32/jMMJ9KXEDt2Op6ES8NLU5WHc2XEW6p52p6gMRCG62RbFAWU0s0wnLVhIwn1BHR +70Q==
X-Gm-Message-State: ALKqPwc5+OyJnZXdZxmlFeLYjrk9KUbmy7uv7KWbb0+nO8ZBLq0UGGuu G+S+634nxky/BWSYVkPovmi11sl9NgMzXN+mJMg=
X-Google-Smtp-Source: AB8JxZo9k3V5JZIbnEpen5rR8ohU0jfNPz66Dp8AhRp7KBUbj3INzOwZvMUIYfS4o7sc/bVsAowEE1TryNsStSZcP5o=
X-Received: by 2002:a6b:39d4:: with SMTP id g203-v6mr1548325ioa.165.1525959057186;  Thu, 10 May 2018 06:30:57 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 10 May 2018 06:30:56 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <CAK-1kemWAW+2Sk5aKJ+RXKUAyjFii4MRH=xK7SE0mr=tbCiRfw@mail.gmail.com>
References: <CY4PR21MB0630CE4DE6BA4EDF54A1FEB1B6A40@CY4PR21MB0630.namprd21.prod.outlook.com> <CAN1APde93+S8CP-KcZmqPKCCvsGRiq6ECPUoh_Qk0j9hqs8h0Q@mail.gmail.com> <SN1PR08MB1854E64D7C370BF0A7456977DABB0@SN1PR08MB1854.namprd08.prod.outlook.com> <CAKcm_gNhsHxXM77FjRj-Wh4JxA21NAWKXX3KBT=eZJsCdacM7Q@mail.gmail.com> <DB6PR10MB1766789B25E31EBE70564BD3ACBA0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <SN1PR08MB18548155722C665FFD45CC4DDABA0@SN1PR08MB1854.namprd08.prod.outlook.com> <CAKcm_gMYf6AbHgvg+WKv-woQCtzz9WztiEDf-iRUjKw63Qx=9Q@mail.gmail.com> <1F436ED13A22A246A59CA374CBC543998B60C7AD@ORSMSX111.amr.corp.intel.com> <CAN1APdc3y0EwFqeYVvZs7MtBHhS_9CzwGmcwRqi_6GHWzF3_2Q@mail.gmail.com> <1F436ED13A22A246A59CA374CBC543998B60C851@ORSMSX111.amr.corp.intel.com> <CAN1APdcPkO-HfXqqvjeee6K8U8KSZQdtx=6fW1vZo+H6pKfzzQ@mail.gmail.com> <CAKcm_gP8TRPT7yi1y=mU5Fvq7xB5-1ieyKFLQMPomfabYbkcxA@mail.gmail.com> <bf540ec1f6f045aca1cf2379380630b5@usma1ex-dag1mb5.msg.corp.akamai.com> <SN1PR08MB185446750FCDA2B58C9833C8DA890@SN1PR08MB1854.namprd08.prod.outlook.com> <CACsn0cmJcAxORo4Cd-qyGJL3ZOT5Yz0WgdMqv_AGi4DjedyzFA@mail.gmail.com> <A6F55755-D7E1-40E4-8EC3-D5FE77A2EDBE@fb.com> <CAK-1kemWAW+2Sk5aKJ+RXKUAyjFii4MRH=xK7SE0mr=tbCiRfw@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Thu, 10 May 2018 06:30:56 -0700
Message-ID: <CAN1APddgX6=CxKdUA718=95EeCUPS60vVxbGFDHa7-eRjw7BxA@mail.gmail.com>
Subject: Re: Impact of hardware offloads on network stack performance
To: craigt <c@gryning.com>, Roberto Peon <fenix@fb.com>
Cc: IETF QUIC WG <quic@ietf.org>, Mike Bishop <mbishop@evequefou.be>,  Ian Swett <ianswett=40google.com@dmarc.ietf.org>,  "Deval, Manasi" <manasi.deval@intel.com>, Watson Ladd <watsonbladd@gmail.com>,  "Lubashev, Igor" <ilubashe@akamai.com>, Praveen Balasubramanian <pravb@microsoft.com>
Content-Type: multipart/alternative; boundary="0000000000008ba6e8056bda07e1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/sKVpvo3WFdGB9hYKqVxrm-Anppg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 13:31:02 -0000

--0000000000008ba6e8056bda07e1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Thanks for the pointer.

I doubt you will see similar gains (92%) in UDP because there is going to
be a lot of kernel context switches, one for each packet vis sendmsg.
Copying is probably not the dominating factor here.

I do wish there was an easier way to use the netmap interface without
kernel patches and without taking over the entire network card, e.g. by
binding netmap to a single UDP port.

https://www.unix.com/man-page/freebsd/4/netmap/

Mikkel

On 10 May 2018 at 14.50.13, craigt (c@gryning.com) wrote:

Has anyone experimented with the zerocopy socket interfaces for exactly
this use case?
  https://netdevconf.org/2.1/papers/netdev.pdf

It would seem that is a more natural fit to the assertions made by several
of the authors surrounding packetisation.
I'm unaware if Windows/BSD have similar interfaces/implementations.

c


On 30 April 2018 at 21:37, Roberto Peon <fenix@fb.com> wrote:

> QUIC (mostly) doesn=E2=80=99t do that (rexmit a packet verbatim)=E2=80=94=
you=E2=80=99d need a new
> packet# for the rexmitted packet.
>
> -=3DR
>
>
>
> *From:* QUIC <quic-bounces@ietf.org> on behalf of Watson Ladd <
> watsonbladd@gmail.com>
> *Date:* Monday, April 23, 2018 at 1:56 PM
> *To:* Mike Bishop <mbishop@evequefou.be>
> *Cc:* Praveen Balasubramanian <pravb@microsoft.com>, "Lubashev, Igor" <
> ilubashe@akamai.com>, Ian Swett <ianswett=3D40google.com@dmarc.ietf.org>,
> Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@gmail.com>, IETF QUIC WG <qui=
c@ietf.org>,
> "Deval, Manasi" <manasi.deval@intel.com>
> *Subject:* Re: Impact of hardware offloads on network stack performance
>
>
>
>
>
>
>
> On Mon, Apr 23, 2018 at 1:06 PM, Mike Bishop <mbishop@evequefou.be> wrote=
:
>
> I agree =E2=80=93 the point of offloading the crypto is not only to spare=
 that
> cost on the CPU, though that can be useful, it=E2=80=99s to enable furthe=
r offloads
> that can=E2=80=99t be done on the encrypted packet.
>
>
>
> LRO that could simply group packets by CID and deliver a single batch of
> packets from a single CID in a single invocation seems like a great first
> step, and doesn=E2=80=99t even require crypto offload.  Once you have cry=
pto
> offload, of course those packets per CID could be delivered already
> decrypted.  I=E2=80=99d want to see data on whether there=E2=80=99s value=
 in making the
> received data look like one huge packet when there=E2=80=99s not a single
> bytestream, but that=E2=80=99s not something we need to specify here.
>
>
>
> LSO is more interesting, and the challenge there is that the transport
> stack still needs to know what data was in which packet so that it can do
> loss recovery properly.  QUIC explicitly disallows fragmentation of the U=
DP
> datagram, for the =E2=80=9Cpainful and potentially non-deterministic=E2=
=80=9D reasons you
> referenced.
>
>
>
> Forgive my complete ignorance, but doesn't it just need to know what
> packet it sent?
>
> More explicitly the sender would maintain a queue of sendable packets, an=
d
> mark which have been sent. Acknowledged packets are removed from the queu=
e.
> In event of loss, they simply retransmit the same packet. It's up to high=
er
> layers to pick the right size of packet and take data from the individual
> QUIC streams. If you wanted to expose the stream structure, that sounds a
> lot more complicated.
>
>
> Sincerely,
>
> Watson
>
>
>
>
>

--0000000000008ba6e8056bda07e1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Thanks for the point=
er.</div><div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;=
font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div=
><div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-siz=
e:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">I doubt you will =
see similar gains (92%) in UDP because there is going to be a lot of kernel=
 context switches, one for each packet vis sendmsg. Copying is probably not=
 the dominating factor here.</div><div id=3D"bloop_customfont" style=3D"fon=
t-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;li=
ne-height:auto"><br></div><div id=3D"bloop_customfont" style=3D"font-family=
:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-heigh=
t:auto">I do wish there was an easier way to use the netmap interface witho=
ut kernel patches and without taking over the entire network card, e.g. by =
binding netmap to a single UDP port.</div><div id=3D"bloop_customfont" styl=
e=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margi=
n:0px;line-height:auto"><br></div><div id=3D"bloop_customfont" style=3D"fon=
t-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;li=
ne-height:auto"><a href=3D"https://www.unix.com/man-page/freebsd/4/netmap/"=
>https://www.unix.com/man-page/freebsd/4/netmap/</a></div><div id=3D"bloop_=
customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(=
0,0,0,1.0);margin:0px;line-height:auto"><br></div><div id=3D"bloop_customfo=
nt" style=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.=
0);margin:0px;line-height:auto">Mikkel</div> <br><p class=3D"airmail_on">On=
 10 May 2018 at 14.50.13, craigt (<a href=3D"mailto:c@gryning.com">c@grynin=
g.com</a>) wrote:</p> <blockquote type=3D"cite" class=3D"clean_bq"><span><d=
iv><div></div><div>


<title></title>


<div dir=3D"ltr">Has anyone experimented with the zerocopy socket
interfaces for exactly this use case?
<div>=C2=A0 <a href=3D"https://netdevconf.org/2.1/papers/netdev.pdf">https:=
//netdevconf.org/2.1/papers/netdev.pdf</a><br>
</div>
<div><br></div>
<div>It would seem that is a more natural fit to the assertions
made by several of the authors surrounding packetisation.</div>
<div>I&#39;m unaware if Windows/BSD have similar
interfaces/implementations.</div>
<div><br></div>
<div>c</div>
<div><br></div>
</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On 30 April 2018 at 21:37, Roberto Peon
<span dir=3D"ltr">&lt;<a href=3D"mailto:fenix@fb.com" target=3D"_blank">fen=
ix@fb.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1p=
x #ccc solid;padding-left:1ex">
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_5002203081352271915WordSection1">
<p class=3D"MsoNormal">QUIC (mostly) doesn=E2=80=99t do that (rexmit a pack=
et
verbatim)=E2=80=94you=E2=80=99d need a new packet# for the rexmitted packet=
.</p>
<p class=3D"MsoNormal">-=3DR</p>
<p class=3D"MsoNormal">=C2=A0</p>
<div style=3D"border:none;border-top:solid #b5c4df 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"font-size:12.0pt;color:black">From=
:</span></b> <span style=3D"font-size:12.0pt;color:black">QUIC &lt;<a href=
=3D"mailto:quic-bounces@ietf.org" target=3D"_blank">quic-bounces@ietf.org</=
a>&gt; on behalf of Watson Ladd
&lt;<a href=3D"mailto:watsonbladd@gmail.com" target=3D"_blank">watsonbladd@=
gmail.com</a>&gt;<br>
<b>Date:</b> Monday, April 23, 2018 at 1:56 PM<br>
<b>To:</b> Mike Bishop &lt;<a href=3D"mailto:mbishop@evequefou.be" target=
=3D"_blank">mbishop@evequefou.be</a>&gt;<br>
<b>Cc:</b> Praveen Balasubramanian &lt;<a href=3D"mailto:pravb@microsoft.co=
m" target=3D"_blank">pravb@microsoft.com</a>&gt;, &quot;Lubashev, Igor&quot=
; &lt;<a href=3D"mailto:ilubashe@akamai.com" target=3D"_blank">ilubashe@aka=
mai.com</a>&gt;, Ian Swett
&lt;ianswett=3D<a href=3D"mailto:40google.com@dmarc.ietf.org" target=3D"_bl=
ank">40google.com@dmarc.<wbr>ietf.org</a>&gt;, Mikkel Fahn=C3=B8e
J=C3=B8rgensen &lt;<a href=3D"mailto:mikkelfj@gmail.com" target=3D"_blank">=
mikkelfj@gmail.com</a>&gt;, IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.or=
g" target=3D"_blank">quic@ietf.org</a>&gt;,
&quot;Deval, Manasi&quot; &lt;<a href=3D"mailto:manasi.deval@intel.com" tar=
get=3D"_blank">manasi.deval@intel.com</a>&gt;<span class=3D""><br>
<b>Subject:</b> Re: Impact of hardware offloads on network stack
performance</span></span></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0</p>
</div>
<div>
<p class=3D"MsoNormal"><a name=3D"m_5002203081352271915__MailOriginalBody" =
id=3D"m_5002203081352271915__MailOriginalBody">=C2=A0</a></p>
<div>
<p class=3D"MsoNormal"><span>=C2=A0</span></p>
<div>
<p class=3D"MsoNormal"><span>On Mon, Apr 23, 2018 at 1:06 PM, Mike
Bishop &lt;</span><a href=3D"mailto:mbishop@evequefou.be" target=3D"_blank"=
><span>mbishop@evequefou.be</span></a><span>&gt;
wrote:</span></p>
<div>
<div class=3D"h5">
<blockquote style=3D"border:none;border-left:solid #cccccc 1.0pt;padding:0i=
n 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal"><span>I agree =E2=80=93 the point of offloading the
crypto is not only to spare that cost on the CPU, though that can
be useful, it=E2=80=99s to enable further offloads that can=E2=80=99t be do=
ne on
the encrypted packet.</span></p>
<p class=3D"MsoNormal"><span>=C2=A0</span></p>
<p class=3D"MsoNormal"><span>LRO that could simply group packets by
CID and deliver a single batch of packets from a single CID in a
single invocation seems like a great first step, and doesn=E2=80=99t even
require crypto offload.=C2=A0 Once you have crypto offload, of
course those packets per CID could be delivered already
decrypted.=C2=A0 I=E2=80=99d want to see data on whether there=E2=80=99s va=
lue in
making the received data look like one huge packet when there=E2=80=99s not
a single bytestream, but that=E2=80=99s not something we need to specify
here.</span></p>
<p class=3D"MsoNormal"><span>=C2=A0</span></p>
<p class=3D"MsoNormal"><span>LSO is more interesting, and the
challenge there is that the transport stack still needs to know
what data was in which packet so that it can do loss recovery
properly.=C2=A0 QUIC explicitly disallows fragmentation of the UDP
datagram, for the =E2=80=9C<span style=3D"color:#1f497d">painful and
potentially non-deterministic</span>=E2=80=9D reasons you
referenced.</span></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><span>=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>Forgive my complete ignorance, but
doesn&#39;t it just need to know what packet it sent?<br>
<br>
More explicitly the sender would maintain a queue of sendable
packets, and mark which have been sent. Acknowledged packets are
removed from the queue. In event of loss, they simply retransmit
the same packet. It&#39;s up to higher layers to pick the right size of
packet and take data from the individual QUIC streams. If you
wanted to expose the stream structure, that sounds a lot more
complicated.</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span><br>
Sincerely,</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>Watson</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span>=C2=A0</span></p>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</div>
</blockquote>
</div>
<br></div>


</div></div></span></blockquote></body></html>

--0000000000008ba6e8056bda07e1--


From nobody Thu May 10 06:34:01 2018
Return-Path: <lars@netapp.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3636712D88B for <quic@ietfa.amsl.com>; Thu, 10 May 2018 06:34:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.211
X-Spam-Level: 
X-Spam-Status: No, score=-4.211 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.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 emAVwyzJWDlE for <quic@ietfa.amsl.com>; Thu, 10 May 2018 06:33:59 -0700 (PDT)
Received: from mx143.netapp.com (mx143.netapp.com [IPv6:2620:10a:4005:8000:2306::c]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C147E12EACD for <quic@ietf.org>; Thu, 10 May 2018 06:33:58 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.49,385,1520924400";  d="asc'?scan'208";a="258082880"
Received: from vmwexchts01-prd.hq.netapp.com ([10.122.105.12]) by mx143-out.netapp.com with ESMTP; 10 May 2018 06:33:33 -0700
Received: from HIOEXCMBX07-PRD.hq.netapp.com (10.122.105.40) by VMWEXCHTS01-PRD.hq.netapp.com (10.122.105.12) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 10 May 2018 06:33:33 -0700
Received: from VMWEXCCAS05-PRD.hq.netapp.com (10.122.105.21) by hioexcmbx07-prd.hq.netapp.com (10.122.105.40) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 10 May 2018 06:33:32 -0700
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS05-PRD.hq.netapp.com (10.122.105.21) with Microsoft SMTP Server (TLS) id 15.0.1320.4 via Frontend Transport; Thu, 10 May 2018 06:33:33 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=2HBKKn+AUUBguku08ycpEaicK9/8H04G+SoyWi7Haog=; b=JcYXZaaACwRtdzPwA54RMxtcy84yYk+iTUDQ9JjB5dR5wptkKtMc319eLoXJHs/WuFQjklGmQNeu7nYbkTgvUi3bwhkNkrBJUMIRapXsQZq5/CrDS3sa9ZorahGwgOPTXLHSSdaG0PdqZEEd1xgQYDHc+taJTSTef37eeaAQz4c=
Received: from BY2PR06MB1765.namprd06.prod.outlook.com (10.163.33.19) by BY2PR06MB2182.namprd06.prod.outlook.com (10.166.113.144) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.735.18; Thu, 10 May 2018 13:33:32 +0000
Received: from BY2PR06MB1765.namprd06.prod.outlook.com ([fe80::7d12:230a:1ce3:5f60]) by BY2PR06MB1765.namprd06.prod.outlook.com ([fe80::7d12:230a:1ce3:5f60%13]) with mapi id 15.20.0735.019; Thu, 10 May 2018 13:33:31 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: =?utf-8?B?TWlra2VsIEZhaG7DuGUgSsO4cmdlbnNlbg==?= <mikkelfj@gmail.com>
CC: craigt <c@gryning.com>, Roberto Peon <fenix@fb.com>, Watson Ladd <watsonbladd@gmail.com>, "Lubashev, Igor" <ilubashe@akamai.com>, Mike Bishop <mbishop@evequefou.be>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Praveen Balasubramanian <pravb@microsoft.com>, IETF QUIC WG <quic@ietf.org>, "Deval, Manasi" <manasi.deval@intel.com>
Subject: Re: Impact of hardware offloads on network stack performance
Thread-Topic: Impact of hardware offloads on network stack performance
Thread-Index: AdPMUbL7T8nZAW2ySiO289IPTC0ttgAApm4AADSbFZAACUWYgAAFkLQAACA3b/AAAajkgANRfL2AAAA3SQAAAHMwgAAAR/kAAAEuygAAAJMTgAAAxh6AAAICTwABULcLAAH1RkWAAAFsVQAAABcZgA==
Date: Thu, 10 May 2018 13:33:31 +0000
Message-ID: <98A67023-AE1D-48EE-BD75-7D03E05E980D@netapp.com>
References: <CY4PR21MB0630CE4DE6BA4EDF54A1FEB1B6A40@CY4PR21MB0630.namprd21.prod.outlook.com> <CAN1APde93+S8CP-KcZmqPKCCvsGRiq6ECPUoh_Qk0j9hqs8h0Q@mail.gmail.com> <SN1PR08MB1854E64D7C370BF0A7456977DABB0@SN1PR08MB1854.namprd08.prod.outlook.com> <CAKcm_gNhsHxXM77FjRj-Wh4JxA21NAWKXX3KBT=eZJsCdacM7Q@mail.gmail.com> <DB6PR10MB1766789B25E31EBE70564BD3ACBA0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <SN1PR08MB18548155722C665FFD45CC4DDABA0@SN1PR08MB1854.namprd08.prod.outlook.com> <CAKcm_gMYf6AbHgvg+WKv-woQCtzz9WztiEDf-iRUjKw63Qx=9Q@mail.gmail.com> <1F436ED13A22A246A59CA374CBC543998B60C7AD@ORSMSX111.amr.corp.intel.com> <CAN1APdc3y0EwFqeYVvZs7MtBHhS_9CzwGmcwRqi_6GHWzF3_2Q@mail.gmail.com> <1F436ED13A22A246A59CA374CBC543998B60C851@ORSMSX111.amr.corp.intel.com> <CAN1APdcPkO-HfXqqvjeee6K8U8KSZQdtx=6fW1vZo+H6pKfzzQ@mail.gmail.com> <CAKcm_gP8TRPT7yi1y=mU5Fvq7xB5-1ieyKFLQMPomfabYbkcxA@mail.gmail.com> <bf540ec1f6f045aca1cf2379380630b5@usma1ex-dag1mb5.msg.corp.akamai.com> <SN1PR08MB185446750FCDA2B58C9833C8DA890@SN1PR08MB1854.namprd08.prod.outlook.com> <CACsn0cmJcAxORo4Cd-qyGJL3ZOT5Yz0WgdMqv_AGi4DjedyzFA@mail.gmail.com> <A6F55755-D7E1-40E4-8EC3-D5FE77A2EDBE@fb.com> <CAK-1kemWAW+2Sk5aKJ+RXKUAyjFii4MRH=xK7SE0mr=tbCiRfw@mail.gmail.com> <CAN1APddgX6=CxKdUA718=95EeCUPS60vVxbGFDHa7-eRjw7BxA@mail.gmail.com>
In-Reply-To: <CAN1APddgX6=CxKdUA718=95EeCUPS60vVxbGFDHa7-eRjw7BxA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3445.6.18)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lars@netapp.com; 
x-originating-ip: [62.189.0.100]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BY2PR06MB2182; 7:k0pFuuwN0vLOSuHTplSO3kMuMea+2NRwR4GcciLm2vfSKqv6FQz9QLbBDsdaCThtSklL8KMVLeredkn9H8FJthCiP6yT/AEQSBv9JeLNU5VG68WXjT3PLbsNezweoKViZ+Fp47VG0uDaahfJX8o97bvJenx33vw3QpHUIKTgtbdRrXJLBXFAq8ChvUoFy1GrnunXOpdbntKTfYUNAjGi+B0Qo0ZZQ4kkGZy5VzvaqE/nTWRnVW5kaOuBC77ot1M3
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(2017052603328)(49563074)(7193020); SRVR:BY2PR06MB2182; 
x-ms-traffictypediagnostic: BY2PR06MB2182:
x-microsoft-antispam-prvs: <BY2PR06MB2182A194E28FDFF879427548A7980@BY2PR06MB2182.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(85827821059158);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(102415395)(6040522)(2401047)(8121501046)(5005006)(3231254)(944501410)(52105095)(3002001)(93006095)(93001095)(10201501046)(6055026)(149027)(150027)(6041310)(20161123562045)(20161123558120)(20161123564045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:BY2PR06MB2182; BCL:0; PCL:0; RULEID:; SRVR:BY2PR06MB2182; 
x-forefront-prvs: 066898046A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(979002)(39380400002)(396003)(39860400002)(346002)(376002)(366004)(377424004)(199004)(189003)(8666007)(81166006)(99936001)(6512007)(5250100002)(25786009)(305945005)(7736002)(3846002)(105586002)(4326008)(53936002)(186003)(39060400002)(106356001)(5660300001)(8676002)(68736007)(50226002)(86362001)(8936002)(97736004)(229853002)(4001150100001)(7416002)(6116002)(6486002)(6246003)(54906003)(82746002)(36756003)(6506007)(446003)(14454004)(11346002)(102836004)(57306001)(76176011)(26005)(6916009)(486006)(476003)(3660700001)(6436002)(2616005)(66066001)(53546011)(3280700002)(81156014)(2900100001)(2906002)(83716003)(33656002)(558084003)(1411001)(93886005)(316002)(99286004)(478600001)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR06MB2182; H:BY2PR06MB1765.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: netapp.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: sUYBjOLVaNLmn3paA2VMAO0HnZuQNMtr8tuURQo6sgqmU2NT3ooKW+fqRq1vtnwyCvu1pAKIwseZPW80kt6HFDpD+Ywd4DoMeBlPWCWwFlHYfhDAu13vJJ28z7UFTRfOu65m+KhDnlRo0NIjF6GWroALptoU9ZBvVDpY8U+6yEnz2jmmB2driIMtNAYVtwwa
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_C2668C65-DEF1-48E2-9DD4-3BF4C7B665B1"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: ec673d9d-88a0-437e-02c7-08d5b67a9f4c
X-MS-Exchange-CrossTenant-Network-Message-Id: ec673d9d-88a0-437e-02c7-08d5b67a9f4c
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 May 2018 13:33:31.5586 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR06MB2182
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/AatVUfAlAf1NvU7dsC8sYT952NQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 13:34:00 -0000

--Apple-Mail=_C2668C65-DEF1-48E2-9DD4-3BF4C7B665B1
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

On 2018-5-10, at 14:30, Mikkel Fahn=C3=B8e J=C3=B8rgensen =
<mikkelfj@gmail.com> wrote:
> I do wish there was an easier way to use the netmap interface without =
kernel patches and without taking over the entire network card, e.g. by =
binding netmap to a single UDP port.

You can bind netmap to individual NIC rings.

Lars

--Apple-Mail=_C2668C65-DEF1-48E2-9DD4-3BF4C7B665B1
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAlr0SisACgkQVLXDCb9w
wVcc+A/6AnP1DgcOHm3fbVxJiGpKYoRLD5x1ecnvKJmRZTfHYS5CQ9D5ei1+h9QZ
jFlaQnakWxVxsXUjk9D2zxU/xbfL1OIxaBWqfRyQyCy5SR0AwCDFLzKAyyzwVDCi
VJpLT8hvBmnOD8Yc5ELhmzdRZTgBcZwGAxkJ6GRK3niokl70LQTjtuuyzQCKGimf
wpTekBOrXYr9mXutrG4oPLwXnESSKHnfb6jBBHuqDm2nsWQ1rFjeBhViURAVWomN
Q1ezmRkMiUDd07w/DP2/UTau4PPxmCWsX7IPn1E12wfuH+7mbCJC8EBG4cObPC73
N1CnQZkOUZw/GAr6cw4HE0OIx+ANZSDDEVXDct18U9EtQfDWcFrNq2991y9E8/54
8x/ZmCFyeA2VQFaTNJ3+lR7rlH3WWpniaq1tziRsJcgKQX9pgDm+IJXig9WaLX5g
duolJ7WOGztp+8naKB7T+4yyJMPDsz211StFFcETKT/LGMceru8KaXUTShsMHFHB
fg/JNSzk2UZ81JEzVdV8xuGIXsandcNXzAnU4poQHdn+d82k9yM9WxM2StrjJlXX
JrjmWXyJ6LT4+aP8FuX1+916GOITNu3G/2bEg2bXlzgt67hgHJ76s6OAm8wTzUhX
U4mT0mRaWKSBKfrL/Ps3Z3JywuZvd8BCIsogjXyIy57cBgqNtTw=
=RRpO
-----END PGP SIGNATURE-----

--Apple-Mail=_C2668C65-DEF1-48E2-9DD4-3BF4C7B665B1--


From nobody Thu May 10 06:38:31 2018
Return-Path: <manasi.deval@intel.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C5324124217 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 06:38:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level: 
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
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 xOdXzeq1-7kb for <quic@ietfa.amsl.com>; Thu, 10 May 2018 06:38:26 -0700 (PDT)
Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) (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 7ABEC12DA14 for <quic@ietf.org>; Thu, 10 May 2018 06:38:26 -0700 (PDT)
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from orsmga008.jf.intel.com ([10.7.209.65]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 May 2018 06:38:25 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos; i="5.49,385,1520924400"; d="scan'208,217"; a="40178803"
Received: from orsmsx107.amr.corp.intel.com ([10.22.240.5]) by orsmga008.jf.intel.com with ESMTP; 10 May 2018 06:38:25 -0700
Received: from orsmsx114.amr.corp.intel.com (10.22.240.10) by ORSMSX107.amr.corp.intel.com (10.22.240.5) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 10 May 2018 06:38:25 -0700
Received: from orsmsx111.amr.corp.intel.com ([169.254.12.62]) by ORSMSX114.amr.corp.intel.com ([169.254.8.88]) with mapi id 14.03.0319.002; Thu, 10 May 2018 06:38:24 -0700
From: "Deval, Manasi" <manasi.deval@intel.com>
To: craigt <c@gryning.com>, Roberto Peon <fenix@fb.com>
CC: Watson Ladd <watsonbladd@gmail.com>, Mike Bishop <mbishop@evequefou.be>, Praveen Balasubramanian <pravb@microsoft.com>, "Lubashev, Igor" <ilubashe@akamai.com>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>, =?utf-8?B?TWlra2VsIEZhaG7DuGUgSsO4cmdlbnNlbg==?= <mikkelfj@gmail.com>, "IETF QUIC WG" <quic@ietf.org>
Subject: RE: Impact of hardware offloads on network stack performance
Thread-Topic: Impact of hardware offloads on network stack performance
Thread-Index: AdPMUbL7T8nZAW2ySiO289IPTC0ttgAPUYUAADUrUQAACLVdgAAFkLMAACFByIAAAJ6MgANCFysgAA+c2wAADpmtUP//kQsAgAAJdwCAAASYgIAACHiAgAANzACACvsUgIAPNNaAgABrlFA=
Date: Thu, 10 May 2018 13:38:24 +0000
Message-ID: <1F436ED13A22A246A59CA374CBC543998B64E589@ORSMSX111.amr.corp.intel.com>
References: <CY4PR21MB0630CE4DE6BA4EDF54A1FEB1B6A40@CY4PR21MB0630.namprd21.prod.outlook.com> <CAN1APde93+S8CP-KcZmqPKCCvsGRiq6ECPUoh_Qk0j9hqs8h0Q@mail.gmail.com> <SN1PR08MB1854E64D7C370BF0A7456977DABB0@SN1PR08MB1854.namprd08.prod.outlook.com> <CAKcm_gNhsHxXM77FjRj-Wh4JxA21NAWKXX3KBT=eZJsCdacM7Q@mail.gmail.com> <DB6PR10MB1766789B25E31EBE70564BD3ACBA0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <SN1PR08MB18548155722C665FFD45CC4DDABA0@SN1PR08MB1854.namprd08.prod.outlook.com> <CAKcm_gMYf6AbHgvg+WKv-woQCtzz9WztiEDf-iRUjKw63Qx=9Q@mail.gmail.com> <1F436ED13A22A246A59CA374CBC543998B60C7AD@ORSMSX111.amr.corp.intel.com> <CAN1APdc3y0EwFqeYVvZs7MtBHhS_9CzwGmcwRqi_6GHWzF3_2Q@mail.gmail.com> <1F436ED13A22A246A59CA374CBC543998B60C851@ORSMSX111.amr.corp.intel.com> <CAN1APdcPkO-HfXqqvjeee6K8U8KSZQdtx=6fW1vZo+H6pKfzzQ@mail.gmail.com> <CAKcm_gP8TRPT7yi1y=mU5Fvq7xB5-1ieyKFLQMPomfabYbkcxA@mail.gmail.com> <bf540ec1f6f045aca1cf2379380630b5@usma1ex-dag1mb5.msg.corp.akamai.com> <SN1PR08MB185446750FCDA2B58C9833C8DA890@SN1PR08MB1854.namprd08.prod.outlook.com> <CACsn0cmJcAxORo4Cd-qyGJL3ZOT5Yz0WgdMqv_AGi4DjedyzFA@mail.gmail.com> <A6F55755-D7E1-40E4-8EC3-D5FE77A2EDBE@fb.com> <CAK-1kemWAW+2Sk5aKJ+RXKUAyjFii4MRH=xK7SE0mr=tbCiRfw@mail.gmail.com>
In-Reply-To: <CAK-1kemWAW+2Sk5aKJ+RXKUAyjFii4MRH=xK7SE0mr=tbCiRfw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.0.200.100
dlp-reaction: no-action
x-originating-ip: [10.22.254.138]
Content-Type: multipart/alternative; boundary="_000_1F436ED13A22A246A59CA374CBC543998B64E589ORSMSX111amrcor_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/LK8z32Qni0wJcVBxgO7GAfkh8Xw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 13:38:30 -0000

--_000_1F436ED13A22A246A59CA374CBC543998B64E589ORSMSX111amrcor_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

VGhlIGN1cnJlbnQgc29ja2V0IHNjaGVtZSB1c2VzIHRoZSBrZXJuZWwgc3RhY2sgdG8gaW1wbGVt
ZW50IHRoZSBFdGhlcm5ldCDigJMgSVAg4oCTIFVEUCBzdGFjayBwcm9jZXNzaW5nIGZvciBRVUlD
IHBhY2tldHMuIFRoZSBBRl9YRFAgcHJvdmlkZXMgYSByYXcgZnJhbWUgc28gb25lIHdvdWxkIG5l
ZWQgYSBwb2xpY3kgb24gd2hlcmUgdG8gcnVuIHRoZSBwcm90b2NvbCBzdGFjayBwcm9jZXNzaW5n
Lg0KDQpBbm90aGVyIGNvbW1lbnQgb24gb2ZmbG9hZHMgLQ0KVGhhbmtzIGZvciB0aGUgaW5zaWdo
dGZ1bCBwb2ludCBvZiBob3cgY3J5cHRvIG9mZmxvYWQgZW5hYmxlcyBvdGhlciBvZmZsb2FkcyBs
aWtlIHNlZ21lbnRhdGlvbi4gQSBzZWdtZW50YXRpb24gb2ZmbG9hZCBmb3IgUVVJQyB3b3VsZCBu
ZWVkIHRvIGluY3JlbWVudCBwYWNrZXQgbnVtYmVycyBmb3IgZWFjaCBvZiB0aGUgaW5kaXZpZHVh
bCBwYWNrZXRzIHB1dCBvbiB0aGUgd2lyZS4gVGhlIHRyYW5zbWl0dGVkIHBhY2tldCBudW1iZXJz
IGZvciBhIHRyYW5zbWl0IHNjYXR0ZXIgZ2F0aGVyIGxpc3Qgd291bGQgYmUgZGV0ZXJtaW5pc3Rp
Yy4gVGhlcmVmb3JlLCB0aGlzIHNob3VsZCBub3QgYWR2ZXJzZWx5IGltcGFjdCBhbnkgcmV0cmFu
c21pdHMuDQoNClRoYW5rcywNCk1hbmFzaQ0KDQoNCkZyb206IGNyYWlndCBbbWFpbHRvOmNAZ3J5
bmluZy5jb21dDQpTZW50OiBUaHVyc2RheSwgTWF5IDEwLCAyMDE4IDU6NTAgQU0NClRvOiBSb2Jl
cnRvIFBlb24gPGZlbml4QGZiLmNvbT4NCkNjOiBXYXRzb24gTGFkZCA8d2F0c29uYmxhZGRAZ21h
aWwuY29tPjsgTWlrZSBCaXNob3AgPG1iaXNob3BAZXZlcXVlZm91LmJlPjsgUHJhdmVlbiBCYWxh
c3VicmFtYW5pYW4gPHByYXZiQG1pY3Jvc29mdC5jb20+OyBMdWJhc2hldiwgSWdvciA8aWx1YmFz
aGVAYWthbWFpLmNvbT47IElhbiBTd2V0dCA8aWFuc3dldHQ9NDBnb29nbGUuY29tQGRtYXJjLmll
dGYub3JnPjsgTWlra2VsIEZhaG7DuGUgSsO4cmdlbnNlbiA8bWlra2VsZmpAZ21haWwuY29tPjsg
SUVURiBRVUlDIFdHIDxxdWljQGlldGYub3JnPjsgRGV2YWwsIE1hbmFzaSA8bWFuYXNpLmRldmFs
QGludGVsLmNvbT4NClN1YmplY3Q6IFJlOiBJbXBhY3Qgb2YgaGFyZHdhcmUgb2ZmbG9hZHMgb24g
bmV0d29yayBzdGFjayBwZXJmb3JtYW5jZQ0KDQpIYXMgYW55b25lIGV4cGVyaW1lbnRlZCB3aXRo
IHRoZSB6ZXJvY29weSBzb2NrZXQgaW50ZXJmYWNlcyBmb3IgZXhhY3RseSB0aGlzIHVzZSBjYXNl
Pw0KICBodHRwczovL25ldGRldmNvbmYub3JnLzIuMS9wYXBlcnMvbmV0ZGV2LnBkZg0KDQpJdCB3
b3VsZCBzZWVtIHRoYXQgaXMgYSBtb3JlIG5hdHVyYWwgZml0IHRvIHRoZSBhc3NlcnRpb25zIG1h
ZGUgYnkgc2V2ZXJhbCBvZiB0aGUgYXV0aG9ycyBzdXJyb3VuZGluZyBwYWNrZXRpc2F0aW9uLg0K
SSdtIHVuYXdhcmUgaWYgV2luZG93cy9CU0QgaGF2ZSBzaW1pbGFyIGludGVyZmFjZXMvaW1wbGVt
ZW50YXRpb25zLg0KDQpjDQoNCg0KT24gMzAgQXByaWwgMjAxOCBhdCAyMTozNywgUm9iZXJ0byBQ
ZW9uIDxmZW5peEBmYi5jb208bWFpbHRvOmZlbml4QGZiLmNvbT4+IHdyb3RlOg0KUVVJQyAobW9z
dGx5KSBkb2VzbuKAmXQgZG8gdGhhdCAocmV4bWl0IGEgcGFja2V0IHZlcmJhdGltKeKAlHlvdeKA
mWQgbmVlZCBhIG5ldyBwYWNrZXQjIGZvciB0aGUgcmV4bWl0dGVkIHBhY2tldC4NCi09Ug0KDQpG
cm9tOiBRVUlDIDxxdWljLWJvdW5jZXNAaWV0Zi5vcmc8bWFpbHRvOnF1aWMtYm91bmNlc0BpZXRm
Lm9yZz4+IG9uIGJlaGFsZiBvZiBXYXRzb24gTGFkZCA8d2F0c29uYmxhZGRAZ21haWwuY29tPG1h
aWx0bzp3YXRzb25ibGFkZEBnbWFpbC5jb20+Pg0KRGF0ZTogTW9uZGF5LCBBcHJpbCAyMywgMjAx
OCBhdCAxOjU2IFBNDQpUbzogTWlrZSBCaXNob3AgPG1iaXNob3BAZXZlcXVlZm91LmJlPG1haWx0
bzptYmlzaG9wQGV2ZXF1ZWZvdS5iZT4+DQpDYzogUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gPHBy
YXZiQG1pY3Jvc29mdC5jb208bWFpbHRvOnByYXZiQG1pY3Jvc29mdC5jb20+PiwgIkx1YmFzaGV2
LCBJZ29yIiA8aWx1YmFzaGVAYWthbWFpLmNvbTxtYWlsdG86aWx1YmFzaGVAYWthbWFpLmNvbT4+
LCBJYW4gU3dldHQgPGlhbnN3ZXR0PTQwZ29vZ2xlLmNvbUBkbWFyYy5pZXRmLm9yZzxtYWlsdG86
NDBnb29nbGUuY29tQGRtYXJjLmlldGYub3JnPj4sIE1pa2tlbCBGYWhuw7hlIErDuHJnZW5zZW4g
PG1pa2tlbGZqQGdtYWlsLmNvbTxtYWlsdG86bWlra2VsZmpAZ21haWwuY29tPj4sIElFVEYgUVVJ
QyBXRyA8cXVpY0BpZXRmLm9yZzxtYWlsdG86cXVpY0BpZXRmLm9yZz4+LCAiRGV2YWwsIE1hbmFz
aSIgPG1hbmFzaS5kZXZhbEBpbnRlbC5jb208bWFpbHRvOm1hbmFzaS5kZXZhbEBpbnRlbC5jb20+
Pg0KU3ViamVjdDogUmU6IEltcGFjdCBvZiBoYXJkd2FyZSBvZmZsb2FkcyBvbiBuZXR3b3JrIHN0
YWNrIHBlcmZvcm1hbmNlDQoNCg0KDQpPbiBNb24sIEFwciAyMywgMjAxOCBhdCAxOjA2IFBNLCBN
aWtlIEJpc2hvcCA8bWJpc2hvcEBldmVxdWVmb3UuYmU8bWFpbHRvOm1iaXNob3BAZXZlcXVlZm91
LmJlPj4gd3JvdGU6DQpJIGFncmVlIOKAkyB0aGUgcG9pbnQgb2Ygb2ZmbG9hZGluZyB0aGUgY3J5
cHRvIGlzIG5vdCBvbmx5IHRvIHNwYXJlIHRoYXQgY29zdCBvbiB0aGUgQ1BVLCB0aG91Z2ggdGhh
dCBjYW4gYmUgdXNlZnVsLCBpdOKAmXMgdG8gZW5hYmxlIGZ1cnRoZXIgb2ZmbG9hZHMgdGhhdCBj
YW7igJl0IGJlIGRvbmUgb24gdGhlIGVuY3J5cHRlZCBwYWNrZXQuDQoNCkxSTyB0aGF0IGNvdWxk
IHNpbXBseSBncm91cCBwYWNrZXRzIGJ5IENJRCBhbmQgZGVsaXZlciBhIHNpbmdsZSBiYXRjaCBv
ZiBwYWNrZXRzIGZyb20gYSBzaW5nbGUgQ0lEIGluIGEgc2luZ2xlIGludm9jYXRpb24gc2VlbXMg
bGlrZSBhIGdyZWF0IGZpcnN0IHN0ZXAsIGFuZCBkb2VzbuKAmXQgZXZlbiByZXF1aXJlIGNyeXB0
byBvZmZsb2FkLiAgT25jZSB5b3UgaGF2ZSBjcnlwdG8gb2ZmbG9hZCwgb2YgY291cnNlIHRob3Nl
IHBhY2tldHMgcGVyIENJRCBjb3VsZCBiZSBkZWxpdmVyZWQgYWxyZWFkeSBkZWNyeXB0ZWQuICBJ
4oCZZCB3YW50IHRvIHNlZSBkYXRhIG9uIHdoZXRoZXIgdGhlcmXigJlzIHZhbHVlIGluIG1ha2lu
ZyB0aGUgcmVjZWl2ZWQgZGF0YSBsb29rIGxpa2Ugb25lIGh1Z2UgcGFja2V0IHdoZW4gdGhlcmXi
gJlzIG5vdCBhIHNpbmdsZSBieXRlc3RyZWFtLCBidXQgdGhhdOKAmXMgbm90IHNvbWV0aGluZyB3
ZSBuZWVkIHRvIHNwZWNpZnkgaGVyZS4NCg0KTFNPIGlzIG1vcmUgaW50ZXJlc3RpbmcsIGFuZCB0
aGUgY2hhbGxlbmdlIHRoZXJlIGlzIHRoYXQgdGhlIHRyYW5zcG9ydCBzdGFjayBzdGlsbCBuZWVk
cyB0byBrbm93IHdoYXQgZGF0YSB3YXMgaW4gd2hpY2ggcGFja2V0IHNvIHRoYXQgaXQgY2FuIGRv
IGxvc3MgcmVjb3ZlcnkgcHJvcGVybHkuICBRVUlDIGV4cGxpY2l0bHkgZGlzYWxsb3dzIGZyYWdt
ZW50YXRpb24gb2YgdGhlIFVEUCBkYXRhZ3JhbSwgZm9yIHRoZSDigJxwYWluZnVsIGFuZCBwb3Rl
bnRpYWxseSBub24tZGV0ZXJtaW5pc3RpY+KAnSByZWFzb25zIHlvdSByZWZlcmVuY2VkLg0KDQpG
b3JnaXZlIG15IGNvbXBsZXRlIGlnbm9yYW5jZSwgYnV0IGRvZXNuJ3QgaXQganVzdCBuZWVkIHRv
IGtub3cgd2hhdCBwYWNrZXQgaXQgc2VudD8NCg0KTW9yZSBleHBsaWNpdGx5IHRoZSBzZW5kZXIg
d291bGQgbWFpbnRhaW4gYSBxdWV1ZSBvZiBzZW5kYWJsZSBwYWNrZXRzLCBhbmQgbWFyayB3aGlj
aCBoYXZlIGJlZW4gc2VudC4gQWNrbm93bGVkZ2VkIHBhY2tldHMgYXJlIHJlbW92ZWQgZnJvbSB0
aGUgcXVldWUuIEluIGV2ZW50IG9mIGxvc3MsIHRoZXkgc2ltcGx5IHJldHJhbnNtaXQgdGhlIHNh
bWUgcGFja2V0LiBJdCdzIHVwIHRvIGhpZ2hlciBsYXllcnMgdG8gcGljayB0aGUgcmlnaHQgc2l6
ZSBvZiBwYWNrZXQgYW5kIHRha2UgZGF0YSBmcm9tIHRoZSBpbmRpdmlkdWFsIFFVSUMgc3RyZWFt
cy4gSWYgeW91IHdhbnRlZCB0byBleHBvc2UgdGhlIHN0cmVhbSBzdHJ1Y3R1cmUsIHRoYXQgc291
bmRzIGEgbG90IG1vcmUgY29tcGxpY2F0ZWQuDQoNClNpbmNlcmVseSwNCldhdHNvbg0KDQoNCg0K

--_000_1F436ED13A22A246A59CA374CBC543998B64E589ORSMSX111amrcor_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6ZHQ9InV1aWQ6QzJGNDEwMTAtNjVC
My0xMWQxLUEyOUYtMDBBQTAwQzE0ODgyIiB4bWxuczptPSJodHRwOi8vc2NoZW1hcy5taWNyb3Nv
ZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJodHRwOi8vd3d3LnczLm9yZy9UUi9S
RUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVpdj0iQ29udGVudC1UeXBlIiBjb250
ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1ldGEgbmFtZT0iR2VuZXJhdG9yIiBj
b250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQgbWVkaXVtKSI+DQo8c3R5bGU+PCEt
LQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiQ2Ft
YnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9
DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2
Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250
LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNlcmlmO30NCmE6
bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9y
OmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNv
SHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBs
ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnNwYW4uRW1haWxTdHlsZTE3DQoJe21z
by1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5z
LXNlcmlmOw0KCWNvbG9yOiMxRjQ5N0Q7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5
cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KQHBh
Z2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBp
biAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30N
Ci0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6
ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBn
dGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2
OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0t
LT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxl
Ij4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+VGhlIGN1cnJlbnQgc29ja2V0IHNjaGVtZSB1c2Vz
IHRoZSBrZXJuZWwgc3RhY2sgdG8gaW1wbGVtZW50IHRoZSBFdGhlcm5ldCDigJMgSVAg4oCTIFVE
UCBzdGFjayBwcm9jZXNzaW5nIGZvciBRVUlDIHBhY2tldHMuIFRoZSBBRl9YRFAgcHJvdmlkZXMg
YSByYXcgZnJhbWUgc28gb25lDQogd291bGQgbmVlZCBhIHBvbGljeSBvbiB3aGVyZSB0byBydW4g
dGhlIHByb3RvY29sIHN0YWNrIHByb2Nlc3NpbmcuIDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2Vy
aWY7Y29sb3I6IzFGNDk3RCI+QW5vdGhlciBjb21tZW50IG9uIG9mZmxvYWRzIC0gJm5ic3A7PG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGEgbmFtZT0iX01haWxF
bmRDb21wb3NlIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVv
dDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+VGhhbmtzIGZvciB0aGUg
aW5zaWdodGZ1bCBwb2ludCBvZiBob3cgY3J5cHRvIG9mZmxvYWQgZW5hYmxlcyBvdGhlciBvZmZs
b2FkcyBsaWtlIHNlZ21lbnRhdGlvbi4gQSBzZWdtZW50YXRpb24gb2ZmbG9hZCBmb3IgUVVJQyB3
b3VsZA0KIG5lZWQgdG8gaW5jcmVtZW50IHBhY2tldCBudW1iZXJzIGZvciBlYWNoIG9mIHRoZSBp
bmRpdmlkdWFsIHBhY2tldHMgcHV0IG9uIHRoZSB3aXJlLiBUaGUgdHJhbnNtaXR0ZWQgcGFja2V0
IG51bWJlcnMgZm9yIGEgdHJhbnNtaXQgc2NhdHRlciBnYXRoZXIgbGlzdCB3b3VsZCBiZSBkZXRl
cm1pbmlzdGljLiBUaGVyZWZvcmUsIHRoaXMgc2hvdWxkIG5vdCBhZHZlcnNlbHkgaW1wYWN0IGFu
eSByZXRyYW5zbWl0cy4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvYT48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
YWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+PG86cD4mbmJzcDs8L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTox
MS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMx
RjQ5N0QiPlRoYW5rcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJp
JnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6IzFGNDk3RCI+TWFuYXNpPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOiMxRjQ5N0Qi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVvdDss
c2Fucy1zZXJpZjtjb2xvcjojMUY0OTdEIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPkZyb206PC9zcGFuPjwvYj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1
b3Q7LHNhbnMtc2VyaWYiPiBjcmFpZ3QgW21haWx0bzpjQGdyeW5pbmcuY29tXQ0KPGJyPg0KPGI+
U2VudDo8L2I+IFRodXJzZGF5LCBNYXkgMTAsIDIwMTggNTo1MCBBTTxicj4NCjxiPlRvOjwvYj4g
Um9iZXJ0byBQZW9uICZsdDtmZW5peEBmYi5jb20mZ3Q7PGJyPg0KPGI+Q2M6PC9iPiBXYXRzb24g
TGFkZCAmbHQ7d2F0c29uYmxhZGRAZ21haWwuY29tJmd0OzsgTWlrZSBCaXNob3AgJmx0O21iaXNo
b3BAZXZlcXVlZm91LmJlJmd0OzsgUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gJmx0O3ByYXZiQG1p
Y3Jvc29mdC5jb20mZ3Q7OyBMdWJhc2hldiwgSWdvciAmbHQ7aWx1YmFzaGVAYWthbWFpLmNvbSZn
dDs7IElhbiBTd2V0dCAmbHQ7aWFuc3dldHQ9NDBnb29nbGUuY29tQGRtYXJjLmlldGYub3JnJmd0
OzsgTWlra2VsIEZhaG7DuGUgSsO4cmdlbnNlbiAmbHQ7bWlra2VsZmpAZ21haWwuY29tJmd0OzsN
CiBJRVRGIFFVSUMgV0cgJmx0O3F1aWNAaWV0Zi5vcmcmZ3Q7OyBEZXZhbCwgTWFuYXNpICZsdDtt
YW5hc2kuZGV2YWxAaW50ZWwuY29tJmd0Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogSW1wYWN0
IG9mIGhhcmR3YXJlIG9mZmxvYWRzIG9uIG5ldHdvcmsgc3RhY2sgcGVyZm9ybWFuY2U8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5IYXMgYW55b25lIGV4cGVyaW1lbnRlZCB3
aXRoIHRoZSB6ZXJvY29weSBzb2NrZXQgaW50ZXJmYWNlcyBmb3IgZXhhY3RseSB0aGlzIHVzZSBj
YXNlPzxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOyA8
YSBocmVmPSJodHRwczovL25ldGRldmNvbmYub3JnLzIuMS9wYXBlcnMvbmV0ZGV2LnBkZiI+aHR0
cHM6Ly9uZXRkZXZjb25mLm9yZy8yLjEvcGFwZXJzL25ldGRldi5wZGY8L2E+PG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkl0IHdvdWxkIHNlZW0g
dGhhdCBpcyBhIG1vcmUgbmF0dXJhbCBmaXQgdG8gdGhlIGFzc2VydGlvbnMgbWFkZSBieSBzZXZl
cmFsIG9mIHRoZSBhdXRob3JzIHN1cnJvdW5kaW5nIHBhY2tldGlzYXRpb24uPG86cD48L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JJ20gdW5hd2FyZSBpZiBX
aW5kb3dzL0JTRCBoYXZlIHNpbWlsYXIgaW50ZXJmYWNlcy9pbXBsZW1lbnRhdGlvbnMuPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPmM8bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiAzMCBB
cHJpbCAyMDE4IGF0IDIxOjM3LCBSb2JlcnRvIFBlb24gJmx0OzxhIGhyZWY9Im1haWx0bzpmZW5p
eEBmYi5jb20iIHRhcmdldD0iX2JsYW5rIj5mZW5peEBmYi5jb208L2E+Jmd0OyB3cm90ZTo8bzpw
PjwvbzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpz
b2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6
NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+UVVJQyAobW9zdGx5KSBkb2VzbuKAmXQgZG8gdGhhdCAocmV4bWl0IGEgcGFja2V0IHZl
cmJhdGltKeKAlHlvdeKAmWQgbmVlZCBhIG5ldyBwYWNrZXQjIGZvciB0aGUgcmV4bWl0dGVkIHBh
Y2tldC48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+LT1SPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPGRp
diBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERGIDEuMHB0O3BhZGRp
bmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48Yj48c3BhbiBz
dHlsZT0iY29sb3I6YmxhY2siPkZyb206DQo8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJjb2xvcjpi
bGFjayI+UVVJQyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnF1aWMtYm91bmNlc0BpZXRmLm9yZyIgdGFy
Z2V0PSJfYmxhbmsiPnF1aWMtYm91bmNlc0BpZXRmLm9yZzwvYT4mZ3Q7IG9uIGJlaGFsZiBvZiBX
YXRzb24gTGFkZCAmbHQ7PGEgaHJlZj0ibWFpbHRvOndhdHNvbmJsYWRkQGdtYWlsLmNvbSIgdGFy
Z2V0PSJfYmxhbmsiPndhdHNvbmJsYWRkQGdtYWlsLmNvbTwvYT4mZ3Q7PGJyPg0KPGI+RGF0ZTog
PC9iPk1vbmRheSwgQXByaWwgMjMsIDIwMTggYXQgMTo1NiBQTTxicj4NCjxiPlRvOiA8L2I+TWlr
ZSBCaXNob3AgJmx0OzxhIGhyZWY9Im1haWx0bzptYmlzaG9wQGV2ZXF1ZWZvdS5iZSIgdGFyZ2V0
PSJfYmxhbmsiPm1iaXNob3BAZXZlcXVlZm91LmJlPC9hPiZndDs8YnI+DQo8Yj5DYzogPC9iPlBy
YXZlZW4gQmFsYXN1YnJhbWFuaWFuICZsdDs8YSBocmVmPSJtYWlsdG86cHJhdmJAbWljcm9zb2Z0
LmNvbSIgdGFyZ2V0PSJfYmxhbmsiPnByYXZiQG1pY3Jvc29mdC5jb208L2E+Jmd0OywgJnF1b3Q7
THViYXNoZXYsIElnb3ImcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzppbHViYXNoZUBha2FtYWku
Y29tIiB0YXJnZXQ9Il9ibGFuayI+aWx1YmFzaGVAYWthbWFpLmNvbTwvYT4mZ3Q7LCBJYW4gU3dl
dHQgJmx0O2lhbnN3ZXR0PTxhIGhyZWY9Im1haWx0bzo0MGdvb2dsZS5jb21AZG1hcmMuaWV0Zi5v
cmciIHRhcmdldD0iX2JsYW5rIj40MGdvb2dsZS5jb21AZG1hcmMuaWV0Zi5vcmc8L2E+Jmd0OywN
CiBNaWtrZWwgRmFobsO4ZSBKw7hyZ2Vuc2VuICZsdDs8YSBocmVmPSJtYWlsdG86bWlra2VsZmpA
Z21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+bWlra2VsZmpAZ21haWwuY29tPC9hPiZndDssIElF
VEYgUVVJQyBXRyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnF1aWNAaWV0Zi5vcmciIHRhcmdldD0iX2Js
YW5rIj5xdWljQGlldGYub3JnPC9hPiZndDssICZxdW90O0RldmFsLCBNYW5hc2kmcXVvdDsgJmx0
OzxhIGhyZWY9Im1haWx0bzptYW5hc2kuZGV2YWxAaW50ZWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+
bWFuYXNpLmRldmFsQGludGVsLmNvbTwvYT4mZ3Q7PGJyPg0KPGI+U3ViamVjdDogPC9iPlJlOiBJ
bXBhY3Qgb2YgaGFyZHdhcmUgb2ZmbG9hZHMgb24gbmV0d29yayBzdGFjayBwZXJmb3JtYW5jZTwv
c3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG8iPjxhIG5hbWU9Im1fNTAwMjIwMzA4MTM1MjI3MTkxNV9fTWFpbE9yaWdpbmFsQm9keSI+
Jm5ic3A7PC9hPjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
Jm5ic3A7PG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5PbiBN
b24sIEFwciAyMywgMjAxOCBhdCAxOjA2IFBNLCBNaWtlIEJpc2hvcCAmbHQ7PGEgaHJlZj0ibWFp
bHRvOm1iaXNob3BAZXZlcXVlZm91LmJlIiB0YXJnZXQ9Il9ibGFuayI+bWJpc2hvcEBldmVxdWVm
b3UuYmU8L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPGJsb2Nr
cXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7
cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tdG9wOjUu
MHB0O21hcmdpbi1yaWdodDowaW47bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28t
bWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+SSBhZ3JlZSDigJMgdGhlIHBvaW50IG9mIG9mZmxvYWRp
bmcgdGhlIGNyeXB0byBpcyBub3Qgb25seSB0byBzcGFyZSB0aGF0IGNvc3Qgb24gdGhlIENQVSwg
dGhvdWdoIHRoYXQgY2FuIGJlIHVzZWZ1bCwgaXTigJlzIHRvIGVuYWJsZSBmdXJ0aGVyIG9mZmxv
YWRzIHRoYXQgY2Fu4oCZdCBiZSBkb25lIG9uIHRoZSBlbmNyeXB0ZWQNCiBwYWNrZXQuPG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvIj5MUk8gdGhhdCBjb3VsZCBzaW1wbHkgZ3JvdXAgcGFja2V0
cyBieSBDSUQgYW5kIGRlbGl2ZXIgYSBzaW5nbGUgYmF0Y2ggb2YgcGFja2V0cyBmcm9tIGEgc2lu
Z2xlIENJRCBpbiBhIHNpbmdsZSBpbnZvY2F0aW9uIHNlZW1zIGxpa2UgYSBncmVhdCBmaXJzdCBz
dGVwLCBhbmQgZG9lc27igJl0IGV2ZW4gcmVxdWlyZQ0KIGNyeXB0byBvZmZsb2FkLiZuYnNwOyBP
bmNlIHlvdSBoYXZlIGNyeXB0byBvZmZsb2FkLCBvZiBjb3Vyc2UgdGhvc2UgcGFja2V0cyBwZXIg
Q0lEIGNvdWxkIGJlIGRlbGl2ZXJlZCBhbHJlYWR5IGRlY3J5cHRlZC4mbmJzcDsgSeKAmWQgd2Fu
dCB0byBzZWUgZGF0YSBvbiB3aGV0aGVyIHRoZXJl4oCZcyB2YWx1ZSBpbiBtYWtpbmcgdGhlIHJl
Y2VpdmVkIGRhdGEgbG9vayBsaWtlIG9uZSBodWdlIHBhY2tldCB3aGVuIHRoZXJl4oCZcyBub3Qg
YSBzaW5nbGUgYnl0ZXN0cmVhbSwNCiBidXQgdGhhdOKAmXMgbm90IHNvbWV0aGluZyB3ZSBuZWVk
IHRvIHNwZWNpZnkgaGVyZS48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPkxTTyBpcyBtb3Jl
IGludGVyZXN0aW5nLCBhbmQgdGhlIGNoYWxsZW5nZSB0aGVyZSBpcyB0aGF0IHRoZSB0cmFuc3Bv
cnQgc3RhY2sgc3RpbGwgbmVlZHMgdG8ga25vdyB3aGF0IGRhdGEgd2FzIGluIHdoaWNoIHBhY2tl
dCBzbyB0aGF0IGl0IGNhbiBkbyBsb3NzIHJlY292ZXJ5IHByb3Blcmx5LiZuYnNwOyBRVUlDIGV4
cGxpY2l0bHkNCiBkaXNhbGxvd3MgZnJhZ21lbnRhdGlvbiBvZiB0aGUgVURQIGRhdGFncmFtLCBm
b3IgdGhlIOKAnDxzcGFuIHN0eWxlPSJjb2xvcjojMUY0OTdEIj5wYWluZnVsIGFuZCBwb3RlbnRp
YWxseSBub24tZGV0ZXJtaW5pc3RpYzwvc3Bhbj7igJ0gcmVhc29ucyB5b3UgcmVmZXJlbmNlZC48
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28t
bWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Rm9yZ2l2ZSBteSBjb21wbGV0ZSBpZ25vcmFuY2UsIGJ1
dCBkb2Vzbid0IGl0IGp1c3QgbmVlZCB0byBrbm93IHdoYXQgcGFja2V0IGl0IHNlbnQ/PGJyPg0K
PGJyPg0KTW9yZSBleHBsaWNpdGx5IHRoZSBzZW5kZXIgd291bGQgbWFpbnRhaW4gYSBxdWV1ZSBv
ZiBzZW5kYWJsZSBwYWNrZXRzLCBhbmQgbWFyayB3aGljaCBoYXZlIGJlZW4gc2VudC4gQWNrbm93
bGVkZ2VkIHBhY2tldHMgYXJlIHJlbW92ZWQgZnJvbSB0aGUgcXVldWUuIEluIGV2ZW50IG9mIGxv
c3MsIHRoZXkgc2ltcGx5IHJldHJhbnNtaXQgdGhlIHNhbWUgcGFja2V0LiBJdCdzIHVwIHRvIGhp
Z2hlciBsYXllcnMgdG8gcGljayB0aGUgcmlnaHQgc2l6ZQ0KIG9mIHBhY2tldCBhbmQgdGFrZSBk
YXRhIGZyb20gdGhlIGluZGl2aWR1YWwgUVVJQyBzdHJlYW1zLiBJZiB5b3Ugd2FudGVkIHRvIGV4
cG9zZSB0aGUgc3RyZWFtIHN0cnVjdHVyZSwgdGhhdCBzb3VuZHMgYSBsb3QgbW9yZSBjb21wbGlj
YXRlZC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+PGJyPg0KU2luY2VyZWx5LDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj5XYXRzb248bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFy
Z2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwv
YmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_1F436ED13A22A246A59CA374CBC543998B64E589ORSMSX111amrcor_--


From nobody Thu May 10 06:46:09 2018
Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CE38712EAD4 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 06:46:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.697
X-Spam-Level: 
X-Spam-Status: No, score=-2.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 w_G2SGrFHnpq for <quic@ietfa.amsl.com>; Thu, 10 May 2018 06:46:03 -0700 (PDT)
Received: from mail-io0-x22e.google.com (mail-io0-x22e.google.com [IPv6:2607:f8b0:4001:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 658E112EAD7 for <quic@ietf.org>; Thu, 10 May 2018 06:46:02 -0700 (PDT)
Received: by mail-io0-x22e.google.com with SMTP id g1-v6so3071969iob.2 for <quic@ietf.org>; Thu, 10 May 2018 06:46:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=8miJN8ZoGlKgd87XnVP6o1DFVEFm166Bu+4FJIrDzJs=; b=PqLWHHUdQdWuHRJgBRMZZcJh7rzRA4+YnbP9Owck5kGZsVpwaPhjgEQCO+VuVHo2s9 0PUHf2kp/ZWbnOo1Sofh8TFmKPi/34piViH4s3DsT+f6zciV0J8ibUvNwc+X8kMkS7mq shg+4p701vtloHfO6vnuTmq27Jq/ZFRaqNHEZaDom5Wnvhd8OHZ7XA0nn3PEgjQuq6qm 6q8bdDPvnX4pKg07P3qe9JsD27C5yDClan3EIcLQPj3T6Z44RxILarO6mblTyio9hYCu utd59xGdPz3xsiYNt09FiFLsmvsedveLWC4UkR0fyFmAEqLe9Sln/hFnoNMyyBFLJuOR vhKA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=8miJN8ZoGlKgd87XnVP6o1DFVEFm166Bu+4FJIrDzJs=; b=MqjoNPsdCyz4f5DOqYfJ26VgfdIilaev6w4Nv5IDYVRcAAjLeQ51vxFtfTDpPbte34 oCoM7AJpA7HanOqQJ4R4PQCYzYOGTbW/rf/sOY9d1Dr7qy47mwO4j+lDcpsSYDDAwHri ymT5XCeYDw1205nZJhfIXwM3Zz3C8JxFnwI+yzsDq3+QGu5YWX9rwA1L26dwLgqF3ylU PdUe7kESGvZdyxbonEVAvZouXdLLoM/Om78l65v9Hzm/R4pgINesTaKWUHp+39bWPgBN IEKMaCajYoO9HNn48c7fGN0r9VWR+c/LpNq634IKY4ZPE5q3aY9ohehIHzFouC7pOCqb PM/w==
X-Gm-Message-State: ALKqPwfELnYawIQ2Uamvb+haW2a2CV4Ew16YI4K0ZRcRoS8N+gBw8wSa mdMHkf+JIMQa4bswPrXP3WKb4KLXUajOwbYP9Lg=
X-Google-Smtp-Source: AB8JxZp7jMMTwzxxlZ2jkgjuhnxVWUBnPe4IE5hRfU4XCcbZePsWPSHxzm7aLvWPyvGcfLBEyZIvMbcn5xgau3g1wz4=
X-Received: by 2002:a6b:8dc3:: with SMTP id p186-v6mr1506317iod.70.1525959961813;  Thu, 10 May 2018 06:46:01 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 10 May 2018 06:46:01 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <98A67023-AE1D-48EE-BD75-7D03E05E980D@netapp.com>
References: <CY4PR21MB0630CE4DE6BA4EDF54A1FEB1B6A40@CY4PR21MB0630.namprd21.prod.outlook.com> <CAN1APde93+S8CP-KcZmqPKCCvsGRiq6ECPUoh_Qk0j9hqs8h0Q@mail.gmail.com> <SN1PR08MB1854E64D7C370BF0A7456977DABB0@SN1PR08MB1854.namprd08.prod.outlook.com> <CAKcm_gNhsHxXM77FjRj-Wh4JxA21NAWKXX3KBT=eZJsCdacM7Q@mail.gmail.com> <DB6PR10MB1766789B25E31EBE70564BD3ACBA0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM> <SN1PR08MB18548155722C665FFD45CC4DDABA0@SN1PR08MB1854.namprd08.prod.outlook.com> <CAKcm_gMYf6AbHgvg+WKv-woQCtzz9WztiEDf-iRUjKw63Qx=9Q@mail.gmail.com> <1F436ED13A22A246A59CA374CBC543998B60C7AD@ORSMSX111.amr.corp.intel.com> <CAN1APdc3y0EwFqeYVvZs7MtBHhS_9CzwGmcwRqi_6GHWzF3_2Q@mail.gmail.com> <1F436ED13A22A246A59CA374CBC543998B60C851@ORSMSX111.amr.corp.intel.com> <CAN1APdcPkO-HfXqqvjeee6K8U8KSZQdtx=6fW1vZo+H6pKfzzQ@mail.gmail.com> <CAKcm_gP8TRPT7yi1y=mU5Fvq7xB5-1ieyKFLQMPomfabYbkcxA@mail.gmail.com> <bf540ec1f6f045aca1cf2379380630b5@usma1ex-dag1mb5.msg.corp.akamai.com> <SN1PR08MB185446750FCDA2B58C9833C8DA890@SN1PR08MB1854.namprd08.prod.outlook.com> <CACsn0cmJcAxORo4Cd-qyGJL3ZOT5Yz0WgdMqv_AGi4DjedyzFA@mail.gmail.com> <A6F55755-D7E1-40E4-8EC3-D5FE77A2EDBE@fb.com> <CAK-1kemWAW+2Sk5aKJ+RXKUAyjFii4MRH=xK7SE0mr=tbCiRfw@mail.gmail.com> <CAN1APddgX6=CxKdUA718=95EeCUPS60vVxbGFDHa7-eRjw7BxA@mail.gmail.com> <98A67023-AE1D-48EE-BD75-7D03E05E980D@netapp.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Thu, 10 May 2018 06:46:01 -0700
Message-ID: <CAN1APdf2VKXB-sO97S=n5rCC4t6YZL22T=xdxPba9SgRAPKwLA@mail.gmail.com>
Subject: Re: Impact of hardware offloads on network stack performance
To: "Eggert, Lars" <lars@netapp.com>
Cc: Roberto Peon <fenix@fb.com>, Mike Bishop <mbishop@evequefou.be>,  Ian Swett <ianswett=40google.com@dmarc.ietf.org>, IETF QUIC WG <quic@ietf.org>, craigt <c@gryning.com>, "Deval, Manasi" <manasi.deval@intel.com>,  Watson Ladd <watsonbladd@gmail.com>, "Lubashev, Igor" <ilubashe@akamai.com>,  Praveen Balasubramanian <pravb@microsoft.com>
Content-Type: multipart/alternative; boundary="0000000000007726f3056bda3d9c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/govcAIh770k3H95f6JiuvWj-54k>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 13:46:08 -0000

--0000000000007726f3056bda3d9c
Content-Type: text/plain; charset="UTF-8"

On 10 May 2018 at 15.33.58, Eggert, Lars (lars@netapp.com) wrote:

You can bind netmap to individual NIC rings.


Yes, but is is not exactly simple since deployment gets rather elaborate.

--0000000000007726f3056bda3d9c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">On 10 May 2018 at 15=
.33.58, Eggert, Lars (<a href=3D"mailto:lars@netapp.com">lars@netapp.com</a=
>) wrote:</div> <div><blockquote type=3D"cite" class=3D"clean_bq" style=3D"=
font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-c=
aps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-i=
ndent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-deco=
ration:none"><span><div><span style=3D"color:rgb(0,0,0);font-family:&quot;h=
elvetica Neue&quot;,helvetica;font-size:14px;font-style:normal;font-variant=
-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;text=
-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;backgro=
und-color:rgb(255,255,255);text-decoration:none;float:none;display:inline!i=
mportant">You can bind netmap to individual NIC rings.<span class=3D"Apple-=
converted-space">=C2=A0</span></span></div></span></blockquote></div><p><br=
></p><p>Yes, but is is not exactly simple since deployment gets rather elab=
orate.</p><div></div></body></html>

--0000000000007726f3056bda3d9c--


From nobody Thu May 10 06:57:45 2018
Return-Path: <borisp@mellanox.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D9D5C12EAD8 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 06:57:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=mellanox.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 yUsRf1q2EmgW for <quic@ietfa.amsl.com>; Thu, 10 May 2018 06:57:41 -0700 (PDT)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20068.outbound.protection.outlook.com [40.107.2.68]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1FBCC12EACF for <quic@ietf.org>; Thu, 10 May 2018 06:57:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=Mellanox.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=JYdlsWfUrq5B2VHc3+Qf5HCJoKliIXh8G+XnteDITc4=; b=NIizpDt74vZway4U3VyMqMCZxgwFLs9vvTVcu8JVLRBFrelokuxs/WCV4g1lCeSOmOnLQp4sEAohQTkC3KtFimmhzTbId6zE24DSVGL4d8m3ysiT3gQb2qUiHZVpzBGggJVhJcASxil3uhnBbTO/bg4mSdmzDcwK6B4+LqscWhI=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=borisp@mellanox.com; 
Received: from [10.8.2.53] (193.47.165.251) by DB7PR05MB4348.eurprd05.prod.outlook.com (2603:10a6:5:1a::21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.735.17; Thu, 10 May 2018 13:57:35 +0000
Subject: Re: Impact of hardware offloads on network stack performance
To: =?UTF-8?Q?Mikkel_Fahn=c3=b8e_J=c3=b8rgensen?= <mikkelfj@gmail.com>, "Eggert, Lars" <lars@netapp.com>
Cc: Watson Ladd <watsonbladd@gmail.com>, craigt <c@gryning.com>, "Lubashev, Igor" <ilubashe@akamai.com>, Roberto Peon <fenix@fb.com>, Mike Bishop <mbishop@evequefou.be>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Praveen Balasubramanian <pravb@microsoft.com>, IETF QUIC WG <quic@ietf.org>, "Deval, Manasi" <manasi.deval@intel.com>
References: <CY4PR21MB0630CE4DE6BA4EDF54A1FEB1B6A40@CY4PR21MB0630.namprd21.prod.outlook.com> <1F436ED13A22A246A59CA374CBC543998B60C7AD@ORSMSX111.amr.corp.intel.com> <CAN1APdc3y0EwFqeYVvZs7MtBHhS_9CzwGmcwRqi_6GHWzF3_2Q@mail.gmail.com> <1F436ED13A22A246A59CA374CBC543998B60C851@ORSMSX111.amr.corp.intel.com> <CAN1APdcPkO-HfXqqvjeee6K8U8KSZQdtx=6fW1vZo+H6pKfzzQ@mail.gmail.com> <CAKcm_gP8TRPT7yi1y=mU5Fvq7xB5-1ieyKFLQMPomfabYbkcxA@mail.gmail.com> <bf540ec1f6f045aca1cf2379380630b5@usma1ex-dag1mb5.msg.corp.akamai.com> <SN1PR08MB185446750FCDA2B58C9833C8DA890@SN1PR08MB1854.namprd08.prod.outlook.com> <CACsn0cmJcAxORo4Cd-qyGJL3ZOT5Yz0WgdMqv_AGi4DjedyzFA@mail.gmail.com> <A6F55755-D7E1-40E4-8EC3-D5FE77A2EDBE@fb.com> <CAK-1kemWAW+2Sk5aKJ+RXKUAyjFii4MRH=xK7SE0mr=tbCiRfw@mail.gmail.com> <CAN1APddgX6=CxKdUA718=95EeCUPS60vVxbGFDHa7-eRjw7BxA@mail.gmail.com> <98A67023-AE1D-48EE-BD75-7D03E05E980D@netapp.com> <CAN1APdf2VKXB-sO97S=n5rCC4t6YZL22T=xdxPba9SgRAPKwLA@mail.gmail.com>
From: Boris Pismenny <borisp@mellanox.com>
Message-ID: <5213b2f5-c795-9d54-72b8-01a4a6db03ee@mellanox.com>
Date: Thu, 10 May 2018 16:57:29 +0300
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <CAN1APdf2VKXB-sO97S=n5rCC4t6YZL22T=xdxPba9SgRAPKwLA@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Originating-IP: [193.47.165.251]
X-ClientProxiedBy: CWLP265CA0121.GBRP265.PROD.OUTLOOK.COM (2603:10a6:401:53::13) To DB7PR05MB4348.eurprd05.prod.outlook.com (2603:10a6:5:1a::21)
X-MS-PublicTrafficType: Email
X-MS-Office365-Filtering-HT: Tenant
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(48565401081)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:DB7PR05MB4348; 
X-Microsoft-Exchange-Diagnostics: 1; DB7PR05MB4348; 3:dkpbSMb+195o1nRG9DSP+kNAmERf5AYaMFeddXLAOoiAKQa3kalpiH26oFLRGywGKEpVSo9hZC+410U9lwfXLYqaahPAxd7BK4z0E5RVr7gRdrB8fIfy8nfoOWHgZy/9Wmjrg5otudcClYk3ytIyc45RhoMA6i372LZyBH7TxQIQXuln0BXbhoBjEfFhQEeD65EKOqOk2JTd7gVfk5g9VrykObZ4iMeq1leyzced8HdvK2VFdyi3ME/fjAvpBUXm; 25:5CvpGH2iL6lhXa0nLVgz3vyZ85httk32FfuVfDRLPJZUjggYRFlPzdKmE26r8hO21ow1bDSPwNNPrvjeLVRlFWs1UgKrUWcaJM5o1YPZ6epMlqJ2jbxIj0D5bhufFJkv1V4kqDnq5lRZ5M9BSmbb4kzicWsX/S9mVwiQAsKpBX71ZrljVanVZeG1RRN/yziqpHHe1+GdC0Z3f1OnseSq2r0UtSa61lM+kgYXjW4RAwaKkXio/b/n1fWJnZhpOZZO96YZ1uQ9fnVW+b7SfvFp5mbe6LF3pVW5uvWX9WxAPTn34x/TwA+r9qWUz7hWvLhgao6oGPe4aQ66qZpL+MvQZw==; 31:1gsIsLg1VooaNJvcmwNZfB33ojmz26dZGnwuaOqQRoy20PA6hluBlJQoKWrZs2BmQhkepRDaJvdrnJ4DiK8N/ZO2x0lT17+EgEIs8RQSvMmImNO7V+6nrn5heCiQSgFanVPakrho6BjtcaWR33dDMuT0b9fsOJsCYSQmQniJnf2TD947KkfbR6JcqtgHBczPqpyNQACpITbKddcvE/4tv2m1j0p+O8LIcutvxfo1Nio=
X-MS-TrafficTypeDiagnostic: DB7PR05MB4348:
X-Microsoft-Exchange-Diagnostics: 1; DB7PR05MB4348; 20:6rpH671RoCvJ7rXxvvHenRCllHOkw+bcYpgfjcIX1kpDHX3tvw3LIuyscB47Yn7AGRBKdWRLH5N8Ov3rFB1C9VeEuPcw7LUj9/Bf+RuJuP5pdG4t0YGQLBS69yALMDay5bq8AfFb27DqwRFyCcLK3DjaLRcUo4RUrXWb1LPlG56ikuKBGqwS5fznfSQ/KQgWp1wRG9t8A1dYjkY7t44DxiYZwGBAnoL9WffkHUmx3p68mNWACuudF2HvUVCcnIc+7agqTgIp08MoKMkhF2pkZwVULCex8lgKLHdbfmeQzBn0J7c6dkPeGQ0oqrBxP7CNjliEbM7fuMO4uh6Z/gW0RxUw0zfT0njlARbw5aw+fbAyZSFLEIPlrGb+8VDvudqIX/gZKx/NcV8byPR15bDgcZX8jdJMj+MmLhQErjJbYor23oum+jt2Dx7HuHMTcwB3OoF4z6Sz1faVvC8mwuG+5V1BQ/K19e//P9iZM/1kwNWTtPKe+PZdwp5YVsw2Yrq+; 4:cW3CCS8xdS8aMYA/SPz7VHmrsekmgzj6hsbc2Ut0mX/vKAze0l6YGr/U7gLD/zcKv5fJOzCEYerNxV42+slXRhjnyZ0gmUER6rDmd0/aFlrRoxT3/+EReZYiFQ64fE565qEeJ9pXmnSUI5r7G/rl067Z/edk8CezG/UHZQ1iL+ldgoSOZAIZNNK2GYkbn3LugoBPJYWL54OiIqiKrxjMrrfxhM1xfTVnLGkghS7OW0WI7szOEDTfUiTX+X5yorSOpPS85IIzu139MHYnV7NLMyT5/1zxPRTnW50WPDF+jqEnNZ4M3bdkuXx46rLWG940tXgr+1hs8OoOKOM9HlfXk9L+qBjJT3AX/BuJdK6oq3c=
X-Microsoft-Antispam-PRVS: <DB7PR05MB4348B04C764A50DD12D30AB3B0980@DB7PR05MB4348.eurprd05.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:(178636050973902)(132712982866762);
X-MS-Exchange-SenderADCheck: 1
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3231254)(944501410)(52105095)(93006095)(93001095)(10201501046)(3002001)(6055026)(149027)(150027)(6041310)(20161123562045)(20161123558120)(20161123564045)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:DB7PR05MB4348; BCL:0; PCL:0; RULEID:; SRVR:DB7PR05MB4348; 
X-Forefront-PRVS: 066898046A
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10009020)(6049001)(39380400002)(346002)(396003)(376002)(39860400002)(366004)(189003)(199004)(4326008)(3846002)(110136005)(97736004)(5660300001)(39060400002)(81156014)(81166006)(8666007)(54906003)(486006)(53936002)(316002)(186003)(7416002)(8936002)(16576012)(31686004)(8676002)(58126008)(305945005)(2906002)(2870700001)(16526019)(65826007)(6246003)(77096007)(26005)(93886005)(6116002)(52116002)(66066001)(65956001)(966005)(386003)(53546011)(105586002)(956004)(25786009)(47776003)(36756003)(86362001)(229853002)(106356001)(6486002)(2486003)(476003)(3260700006)(76176011)(50466002)(65806001)(52146003)(478600001)(446003)(68736007)(64126003)(2616005)(7736002)(67846002)(11346002)(23676004)(31696002)(6666003)(6306002); DIR:OUT; SFP:1101; SCL:1; SRVR:DB7PR05MB4348; H:[10.8.2.53]; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
Received-SPF: None (protection.outlook.com: mellanox.com does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtEQjdQUjA1TUI0MzQ4OzIzOmRjYlN5RnhNVFdTb1Y1czg5WlVadFozeEVJ?= =?utf-8?B?Vzg3WllvR1cvaDlscFJubEQyUmtQZGUzcXE1ZHRvU0tLRCsxOWVCbEdWbGIr?= =?utf-8?B?cTJwdU1mQVJYZWZtdlFwV01HSEhKNnl4TXBpNUJuUko5VHhId0tXem1JM0lU?= =?utf-8?B?RUtiVTV0SWgwM3Z1TmlWK0UrdzRuLzk2WTk2QWlNQnpQVUZJYUxzOW1maSs5?= =?utf-8?B?ZHhUSWQrREhGYXgvbHZXODZUQ1RrTHp5OHdDYzlQUFdwbVZzWjNqTXhIb1gr?= =?utf-8?B?Q1FvMlVzclZnZ0thcGMzM0N1TGlhN1NLajFDVUxLSWRVNEdYR2VyRExia1dl?= =?utf-8?B?L0xoSWVIU3o0WjE2c24zVjFMVWlZZHFlQzRXTW9DV0dPVmREd1FRNEZxOXZQ?= =?utf-8?B?cWtaQml6K2toMXhJL1c4TVFMbnZUVFE1aWhTSkZERFdpVkE0RmVZWWFHSHQ0?= =?utf-8?B?SGlYbmhKZHltdHRpdjFpRXAxQVZ3OHhHOHN0N3o5RGdmZW5hTnN5Y3U3em8r?= =?utf-8?B?R1N3b0k3Y1d4MGpVS1A4TkhPVGhuZ3BwTkFodmJEbXNWQklkZXRYNzZEYjRB?= =?utf-8?B?RWlUVm9mZU9xUG9sQ1BhQWNuL1NiZlljL2h6NVBXWEtqR3prNUQxVWNyWGFn?= =?utf-8?B?aDUyc0Y5ek1NOUl6RjRYOGxaSXlFOWVzNmk2cGJwZ2xkbHFaa3pqTHNnMzNE?= =?utf-8?B?cWdQbzNpaW1UazI5cFhRTnB2Mml6OFBSK25tSmdkM2oxeVRoWFJWejRYei9n?= =?utf-8?B?R2p5N1lwd2I2UVNQZk0vRHVHMENkMm5lS1lReU5iM1M3d1hQZEthK2pPTFpu?= =?utf-8?B?MC9leHM4VFg5RXBjZ1lNZU9DREM0RUkzRlhZM25ST2F4RytxQ1pDbitqbUlN?= =?utf-8?B?M0QzZnF0YVdPRnBLVzgxYXRJeTZaTTNQU2YzRXZCaHd2YXc3SndKSEQ0MGxR?= =?utf-8?B?RFdYZzd1ZFR0cVkwYTFxSk9JT0dKZUxjTkNuV2wxTUZEbzFBelFwYXF2RVc1?= =?utf-8?B?djNSb2NqdUk3NU1jcVhwQ0g3VWhHQnVYUjExM28rK3hSZENDSnFSbU1LTnFj?= =?utf-8?B?R2NTL05MbTQ2NkNpMFpoZ3ZTdFRKSWtXZnpJcE5QdDNiYmdONXFNMHdUUExz?= =?utf-8?B?QlcrRkwyNStyQ2RRTDFsajRPWkJqRWx0bkpCZFhHVjdlekRrdEcxZjNDVGRz?= =?utf-8?B?VTM5bWdVdmZaUUV3cTgzNzJIZGRHYU5GTFdLb1FjMGdFWEhlMFVVa0ZmZFRL?= =?utf-8?B?V05PYyt5YWRCNUo2OXJhdWZlSXcvOUNKdU9vZi9jcmhtQTdZM093TGZHeDVL?= =?utf-8?B?WlZUQUdJcHpYaXVHSDhaT3BMRE95czdESlAwTFpUN3d6bmM4RWxsa202YmNv?= =?utf-8?B?b0JoM0s3eVNyOUs3L2hUdVlPUUVBbHBDM3JiM1pTVS9xU1dwRFZkVjlESUM5?= =?utf-8?B?bEZMTjA4MDNxb2Mvb0FYdFg2b0tPdmJoMG9CcXNUNjN5VjFtTUx3REpWOVJU?= =?utf-8?B?dlcxQ3hkWDFUN0UrajBKblM5cWlXck9NSHVLcWMwVmRhMzBMbFArYVoxU3Jy?= =?utf-8?B?bVhtZzdWQkVVbHh0aHA0cWY0NkZpOUFWcWE3ZUc4NHpZNWhMdG41dGw0MEdv?= =?utf-8?B?RTZvMjh4WUVXTzgrZFIwSDBvbVExelpKY0NXQ0YvVEhMcmx3TUtEWlNjemFo?= =?utf-8?B?NjhqVFY3cnV0eUQyejkreXBLWUNaT0pJL0Vkb1BzWFhDbEVLWVM0OEpVM1pO?= =?utf-8?B?VDJlNDc2WVFSTklJTkV5dHVZQ3Fmb01xU2MwTnd4bEw2QWpiUUVCWkIraFp1?= =?utf-8?B?Zi9mUEZESlVaODhFRzRoc1Jub2JnWDFvWmI4NlFGSnUrdklpOTJjUC9xM0h4?= =?utf-8?B?MzA0cFUyeGtsU0pWU2owaFpqUVVyc0FFMVBqZlVZRjFRVE5uSXgwdGRmc3Ev?= =?utf-8?B?eitSeW9vRENsbng3ZW5qVStKempna0ZiNSthUnYwZHptTTB0U2lMNUVNZnZP?= =?utf-8?B?SzhtcDJDbGQ5MTlHK1RISUZUUkpHWXIzaHR3QUs4L1RaOGNtLzlyeHYrUGRm?= =?utf-8?B?dE9nclJ6aStZRHZUL2h0UzI5VFZqVnFuUFdEMGJoUUhwakVNQmE2KzFDd1Ex?= =?utf-8?B?WFlGd0hxcHo0a1hxNXQ5SXVqWlY0d3p6Z0ZFOUc1ZE5zV1JuZHIxSlZpYzY2?= =?utf-8?B?UTBoUkVzb0tZN0s3anpaOXp2MDlBPT0=?=
X-Microsoft-Antispam-Message-Info: rLuzP7+BpAefwTyXCMa9gEPh7/QCDMIuYBHZYvggmS7dDJCVIGPRUAP5yENNAUyb1d1xBjUZYR4ma0NIOFbRUttqriPqRipHiKP+/s3Q2zG2M3gdSk18CuBuCN9qf0DkqGP0jEWyFQn5+vo6+qzcY8nLU01XfQ2Natur4RSGYh/FOSPE70AJVDmKZF8DgkVW
X-Microsoft-Exchange-Diagnostics: 1; DB7PR05MB4348; 6:4S7RedddlxFhutRWP08YX4l/bMgc9lmZDJ/OsiimIDvEtA9+EQcO84/lgX0MAgfsuJl2zCcA7axOWEAwfsnShVrcc3MACmrkDyA6RPZjZZy5NYQ5KrWEqtjeZdAQ/aXJctskusHXgh41oQOwi8VE9R+o7y+o3jkiQ0LJBPNtEeLVra8tFV8yE2nF+SO4eWmu2qT0ZsWdh6dS4EQPTnMLJR2q1lI1LRJj/qlBisvEwUW4jR7Zxe299po5LE/4zCCwBjI8Ve4nGqUUyZMKtsX01uZoqHWyktGWjf/HKygOXzEk7dYsYmKgTAuEpTFThjzK3sISw3Vq9c58wf1G4+cdN1gE/+nW+LBGrBdmWwDPd5xMyQ54E5gTdcTK3f1CWOIwbGaQvsUQZfQ5fddKpMu2MtLa9rjVNZJNddn19DNo6yDsaHVohHJLHL1gZxkuP3EszB3Jyj8uhN0nxgiprSjw+Q==; 5:j5vxmgmmo7I3aFudSSSiIMpLjfTrxafLOBBx9yNptHYuRJi33+jPWzexHY3OnZAySbYj8dUQSXQSlnznUvFEDQCbz8CvEVcjW8XaeMZWhykINm4/LeSGYQ9R0hESrowmyQhq3xztNW10b7eDlPXD0DXDzNAXktLmQOP7VqyfXTU=; 24:OceW/NuTcCikkUFnmhahmrmuTcwlGA94ls99F9Kfh+uBZXlIF7B8WQjpGf6amFqdQgvTJiJxivcSlYNPRtbyRAnQE1X3N2wGVdRz+rXaJM0=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; DB7PR05MB4348; 7:Vea80yecQ6tmgKZkKBQUrhyM+FNJAL7VfWKpV6yhyC31yvdu4YMnXBcLc42M4M5DWuMX1hkOljn08SP5S3TH8Ajb6Q15FsvlQkIanO/D7KObIK5TV1Sesl6q4EfcxOC1DjbDOTd+b6NWxOXPdCVjphrGbETvdsIyVjNLQd3UhgNNPE7du+G6XHVcwyGb1LRkAApzfvu1yZVYqD/gDzPBCbW5UAm4vhVo7MwWMlKt1KPQ23iQj5kFa3+wqKyo7uNT
X-MS-Office365-Filtering-Correlation-Id: 79c306c8-7eda-4c6a-d412-08d5b67dfc38
X-OriginatorOrg: Mellanox.com
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 10 May 2018 13:57:35.1074 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 79c306c8-7eda-4c6a-d412-08d5b67dfc38
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: a652971c-7d2e-4d9b-a6a4-d149256f461b
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DB7PR05MB4348
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/6RGieKIWDReYnKQcJie_B4eTpsg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 13:57:44 -0000

On 5/10/2018 4:46 PM, Mikkel Fahnøe Jørgensen wrote:
> On 10 May 2018 at 15..33.58, Eggert, Lars (lars@netapp.com 
> <mailto:lars@netapp.com>) wrote:
>> You can bind netmap to individual NIC rings.
> 
> 
> Yes, but is is not exactly simple since deployment gets rather elaborate.
> 

It is possible to use DPDK without taking over the entire network card:
https://www.slideshare.net/LF_DPDK/lfdpdkmellanox-bifurcated-driver-model

Also, is there a reason to prefer netmap over other userspace network 
stacks like DPDK/VPP/etc?


From nobody Thu May 10 07:03:30 2018
Return-Path: <lars@netapp.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 166DE12E049 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 07:03:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.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 bNvlxFkoRN34 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 07:03:27 -0700 (PDT)
Received: from mx143.netapp.com (mx143.netapp.com [IPv6:2620:10a:4005:8000:2306::c]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE3DD124235 for <quic@ietf.org>; Thu, 10 May 2018 07:03:27 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.49,385,1520924400";  d="asc'?scan'208";a="258088661"
Received: from vmwexchts04-prd.hq.netapp.com ([10.122.105.32]) by mx143-out.netapp.com with ESMTP; 10 May 2018 07:03:27 -0700
Received: from VMWEXCCAS06-PRD.hq.netapp.com (10.122.105.22) by VMWEXCHTS04-PRD.hq.netapp.com (10.122.105.32) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Thu, 10 May 2018 07:03:26 -0700
Received: from NAM03-BY2-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS06-PRD.hq.netapp.com (10.122.105.22) with Microsoft SMTP Server (TLS) id 15.0.1320.4 via Frontend Transport; Thu, 10 May 2018 07:03:27 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=tCv2LjVqQEhhTuxbLwCld/nzXMf1pwVD8FcA1QW5z1w=; b=qzkx/D8Hk3vxWCBivIsjuHsDg4f4bZqAhkLh0ZCEB4+oj/w/XeTQA3b21lLIxs4+5pxM96ftZDqQCXQjyzUc7TrHSr1bZGPpD1BeyEu0hr6Wk59K4dpY1BeTzzANP1c7N2PkVlmsXicwHTebMXvKqUIEebQr+tS4U32v4+xeP70=
Received: from BY2PR06MB1765.namprd06.prod.outlook.com (10.163.33.19) by BY2PR06MB089.namprd06.prod.outlook.com (10.242.43.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.755.16; Thu, 10 May 2018 14:03:25 +0000
Received: from BY2PR06MB1765.namprd06.prod.outlook.com ([fe80::7d12:230a:1ce3:5f60]) by BY2PR06MB1765.namprd06.prod.outlook.com ([fe80::7d12:230a:1ce3:5f60%13]) with mapi id 15.20.0735.019; Thu, 10 May 2018 14:03:25 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: Boris Pismenny <borisp@mellanox.com>
CC: =?iso-8859-1?Q?Mikkel_Fahn=F8e_J=F8rgensen?= <mikkelfj@gmail.com>, "Watson Ladd" <watsonbladd@gmail.com>, craigt <c@gryning.com>, "Lubashev, Igor" <ilubashe@akamai.com>, Roberto Peon <fenix@fb.com>, Mike Bishop <mbishop@evequefou.be>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Praveen Balasubramanian <pravb@microsoft.com>, IETF QUIC WG <quic@ietf.org>, "Deval, Manasi" <manasi.deval@intel.com>
Subject: Re: Impact of hardware offloads on network stack performance
Thread-Topic: Impact of hardware offloads on network stack performance
Thread-Index: AdPMUbL7T8nZAW2ySiO289IPTC0ttgAApm4AADSbFZAACUWYgAAFkLQAACA3b/AAAajkgANRfL2AAAA3SQAAAHMwgAAAR/kAAAEuygAAAJMTgAAAxh6AAAICTwABULcLAAH1RkWAAAFsVQAAABcZgAAAb8KAAABmhYAAADTmAA==
Date: Thu, 10 May 2018 14:03:24 +0000
Message-ID: <9E549481-9B80-4DED-AC37-DC0C91AEBCDE@netapp.com>
References: <CY4PR21MB0630CE4DE6BA4EDF54A1FEB1B6A40@CY4PR21MB0630.namprd21.prod.outlook.com> <1F436ED13A22A246A59CA374CBC543998B60C7AD@ORSMSX111.amr.corp.intel.com> <CAN1APdc3y0EwFqeYVvZs7MtBHhS_9CzwGmcwRqi_6GHWzF3_2Q@mail.gmail.com> <1F436ED13A22A246A59CA374CBC543998B60C851@ORSMSX111.amr.corp.intel.com> <CAN1APdcPkO-HfXqqvjeee6K8U8KSZQdtx=6fW1vZo+H6pKfzzQ@mail.gmail.com> <CAKcm_gP8TRPT7yi1y=mU5Fvq7xB5-1ieyKFLQMPomfabYbkcxA@mail.gmail.com> <bf540ec1f6f045aca1cf2379380630b5@usma1ex-dag1mb5.msg.corp.akamai.com> <SN1PR08MB185446750FCDA2B58C9833C8DA890@SN1PR08MB1854.namprd08.prod.outlook.com> <CACsn0cmJcAxORo4Cd-qyGJL3ZOT5Yz0WgdMqv_AGi4DjedyzFA@mail.gmail.com> <A6F55755-D7E1-40E4-8EC3-D5FE77A2EDBE@fb.com> <CAK-1kemWAW+2Sk5aKJ+RXKUAyjFii4MRH=xK7SE0mr=tbCiRfw@mail.gmail.com> <CAN1APddgX6=CxKdUA718=95EeCUPS60vVxbGFDHa7-eRjw7BxA@mail.gmail.com> <98A67023-AE1D-48EE-BD75-7D03E05E980D@netapp.com> <CAN1APdf2VKXB-sO97S=n5rCC4t6YZL22T=xdxPba9SgRAPKwLA@mail.gmail.com> <5213b2f5-c795-9d54-72b8-01a4a6db03ee@mellanox.com>
In-Reply-To: <5213b2f5-c795-9d54-72b8-01a4a6db03ee@mellanox.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3445.6.18)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lars@netapp.com; 
x-originating-ip: [62.189.0.100]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BY2PR06MB089; 7:raw2njuB2OxqzooIi901mK1kc5+iT8FDRyTTFik9QgyxAPdWyDhigWa9hSC9KyzSD+Gxg702BX5CG5JrZEWtvFDmxaxlL9mztNRUace+0/+HrGaWWa23qWV1SPQdqu/fMPwFcNCY61P1EF1xh5kJgcOx3BcSfex4VzN6x3CSNxTbxNX5fDq58yMBcuL0W3V8WdbFkoEIuyHifwi1pziond25Auq7L+nlNWtoKtNw4EYbntAIUlbzCHacA5dG2e97
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(2017052603328)(49563074)(7193020); SRVR:BY2PR06MB089; 
x-ms-traffictypediagnostic: BY2PR06MB089:
x-microsoft-antispam-prvs: <BY2PR06MB089BB0B5C3B1DFAD0EE92BAA7980@BY2PR06MB089.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(102415395)(6040522)(2401047)(5005006)(8121501046)(10201501046)(93006095)(93001095)(3002001)(3231254)(944501410)(52105095)(6055026)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123558120)(20161123562045)(6072148)(201708071742011); SRVR:BY2PR06MB089; BCL:0; PCL:0; RULEID:; SRVR:BY2PR06MB089; 
x-forefront-prvs: 066898046A
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(39380400002)(39860400002)(346002)(366004)(376002)(377424004)(189003)(199004)(82746002)(93886005)(36756003)(6506007)(39060400002)(486006)(6512007)(4326008)(99936001)(2616005)(476003)(8936002)(11346002)(446003)(8666007)(66066001)(6486002)(81156014)(6436002)(81166006)(26005)(5660300001)(186003)(3660700001)(57306001)(50226002)(25786009)(102836004)(5250100002)(6916009)(54906003)(6246003)(33656002)(76176011)(53546011)(83716003)(86362001)(53936002)(478600001)(316002)(14454004)(99286004)(106356001)(68736007)(97736004)(105586002)(3280700002)(2900100001)(7416002)(7736002)(229853002)(305945005)(8676002)(3846002)(6116002)(2906002)(4001150100001); DIR:OUT; SFP:1101; SCL:1; SRVR:BY2PR06MB089; H:BY2PR06MB1765.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: netapp.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: lXsOoWzTk4pi/4B2i4PSLz2ubuR90TpTCDdrswaS2l5uq0D7Fe6+zYgPUBCzzqlo/GdvXwxXjmCS4IqOiUiCFoJOcbP9C4E226RUEZR3sZRfNefnxByrYNm3jqLKFrB3NEjag+411trQaJocqXXnvFwd2MBBnOSQm5S69S3MumlfbTGjxyPhJ/g9b/frDts6
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_C3996F64-80FA-4249-8776-79ED6290501B"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: b74f2c59-53ec-49b5-4cc7-08d5b67ecc43
X-MS-Exchange-CrossTenant-Network-Message-Id: b74f2c59-53ec-49b5-4cc7-08d5b67ecc43
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 May 2018 14:03:24.9546 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR06MB089
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Po9hfm9DsneyuCEzozUCtU146M0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 14:03:29 -0000

--Apple-Mail=_C3996F64-80FA-4249-8776-79ED6290501B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 2018-5-10, at 14:57, Boris Pismenny <borisp@mellanox.com> wrote:
> Also, is there a reason to prefer netmap over other userspace network =
stacks like DPDK/VPP/etc?

For me personally, the netmap API is a lot more minimal and therefore =
easier to integrate. DPDK really wants to take over scheduling, memory =
management and all kinds of other stuff besides packet I/O. YMMV.

Lars

--Apple-Mail=_C3996F64-80FA-4249-8776-79ED6290501B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAlr0USwACgkQVLXDCb9w
wVdFGw//fbWW7K5j5G/FfnH17yq8chXOqocwk4CPSJ3JoFX45HNtBNUbIXkR8pI8
p4cZbVB5JB8/noZJxcSjlOYbYeRUGSDsDPcNh5VZEcwFGG9BWVIdPyYpdnu7vlLd
kX8k2o/uknjrtawUS9znKZ/+XNuM+ykMU9vSwqmYPn0/rJ8tbthm5eZNsdqXD1k9
i3DF7V6iQF9S5NYc1GZ0p1m3QVZrNtqzD8ojmqNM/fopeS9+tCbI3DuAB0nWQUdm
BtntvCv67zKNr3BFGRipxI3nCet01yUViR31Ss6uO7Hi4uINreOeL0S/fzbjhha7
yQ9atnFz9e07vzgRTsP1T6gHd9vy37RGecHg5aChOAS6b9PVkOL392FuZE12UBOs
AB86eA55h860XMPBvGwa3MY/nGQrqZ4ganniV01RIz3IP5PSwxIHltktq5x6ve1D
/NcrA9DppD2+tp62C3IJ+HHA9H+Qwkw9Y1M/lCygM3QoYEpcnAy6k47GsDSYDD4k
jD/YlaVdpThthVBCO9kLukb9ROq38NHHS4iZpSTp1zWxWeVeMvGCfBYJgrJrV3C7
0Or/A53KGZRRUwQ2m3mILw0DAIwx632j458quCE1sVA2RlhkUu4TuQ6yLok5BpPq
UKGiMtkePbjsgGQ1pA+P9e8uCZDExEs3H2Zm0vMerS5IyD/+gAQ=
=o8Ro
-----END PGP SIGNATURE-----

--Apple-Mail=_C3996F64-80FA-4249-8776-79ED6290501B--


From nobody Thu May 10 07:25:43 2018
Return-Path: <manasi.deval@intel.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDF7F12EADE for <quic@ietfa.amsl.com>; Thu, 10 May 2018 07:25:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.9
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 8yaSwRPlJ3hS for <quic@ietfa.amsl.com>; Thu, 10 May 2018 07:25:40 -0700 (PDT)
Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) (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 3C22512EAD0 for <quic@ietf.org>; Thu, 10 May 2018 07:25:40 -0700 (PDT)
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 10 May 2018 07:25:39 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos; i="5.49,385,1520924400"; d="scan'208,217"; a="39913301"
Received: from orsmsx109.amr.corp.intel.com ([10.22.240.7]) by orsmga007.jf.intel.com with ESMTP; 10 May 2018 07:25:39 -0700
Received: from orsmsx155.amr.corp.intel.com (10.22.240.21) by ORSMSX109.amr.corp.intel.com (10.22.240.7) with Microsoft SMTP Server (TLS) id 14.3.319.2; Thu, 10 May 2018 07:25:39 -0700
Received: from orsmsx111.amr.corp.intel.com ([169.254.12.62]) by ORSMSX155.amr.corp.intel.com ([169.254.7.38]) with mapi id 14.03.0319.002; Thu, 10 May 2018 07:25:39 -0700
From: "Deval, Manasi" <manasi.deval@intel.com>
To: IETF QUIC WG <quic@ietf.org>
Subject: Cost of parsing ACK frames in QUIC
Thread-Topic: Cost of parsing ACK frames in QUIC
Thread-Index: AdPoaJzXsjis3gTFQX6IIe0OpT4RMg==
Date: Thu, 10 May 2018 14:25:38 +0000
Message-ID: <1F436ED13A22A246A59CA374CBC543998B64E65D@ORSMSX111.amr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.0.200.100
dlp-reaction: no-action
x-originating-ip: [10.22.254.138]
Content-Type: multipart/alternative; boundary="_000_1F436ED13A22A246A59CA374CBC543998B64E65DORSMSX111amrcor_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/pGD2nWPCN0c3lgGbwZA5SVygBxA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 14:25:42 -0000

--_000_1F436ED13A22A246A59CA374CBC543998B64E65DORSMSX111amrcor_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Hi All,

The QUIC header definitions tend to use as few bits as possible by implemen=
ting the policy to use variable size fields. The result of this policy woul=
d be that each receiver needs to do a two part lookup to identify the field=
 and this needs to be implemented serially in order to parse the whole fram=
e time.

For example, in a case where no packets were dropped, a sender may receive =
an ACK for a single block. If a code path were trying to determine the size=
 of an ACK, they would have to read 8 fields to determine the size of ACK.

A client only sees a few ACKs. Majority of the ACKs are seen on the server =
side. It would be good to simplify this scheme so ACK processing can be acc=
elerated with SIMD instructions would be good.

Thanks,
Manasi

--_000_1F436ED13A22A246A59CA374CBC543998B64E65DORSMSX111amrcor_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi All,<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The QUIC header definitions tend to use as few bits =
as possible by implementing the policy to use variable size fields. The res=
ult of this policy would be that each receiver needs to do a two part looku=
p to identify the field and this needs
 to be implemented serially in order to parse the whole frame time. <o:p></=
o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">For example, in a case where no packets were dropped=
, a sender may receive an ACK for a single block. If a code path were tryin=
g to determine the size of an ACK, they would have to read 8 fields to dete=
rmine the size of ACK.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">A client only sees a few ACKs. Majority of the ACKs =
are seen on the server side. It would be good to simplify this scheme so AC=
K processing can be accelerated with SIMD instructions would be good.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks,<o:p></o:p></p>
<p class=3D"MsoNormal">Manasi<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p></o:p></p>
</div>
</body>
</html>

--_000_1F436ED13A22A246A59CA374CBC543998B64E65DORSMSX111amrcor_--


From nobody Thu May 10 07:44:25 2018
Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7F8D812EB05 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 07:44:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.697
X-Spam-Level: 
X-Spam-Status: No, score=-2.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 YMVSodUHR0qd for <quic@ietfa.amsl.com>; Thu, 10 May 2018 07:44:23 -0700 (PDT)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1012C12EAF9 for <quic@ietf.org>; Thu, 10 May 2018 07:44:23 -0700 (PDT)
Received: by mail-io0-x233.google.com with SMTP id e12-v6so3275986iob.8 for <quic@ietf.org>; Thu, 10 May 2018 07:44:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to;  bh=MPq7VywDNj/NEEYZeQEIanAipmyEOYNyqZiejzrMImY=; b=U/zG6FoQOMKM98jZ6lSok5vjK6inPlOLyI1gqTX+AWImiHPefH2e4fFlS8nPjcJJ2O +OcYnHnUfJ10sCgpalxQEmQVbEzMGJtJ+LH9P8YZz5RzO1wRzErXQ0aP3mo9NouFb7+Q sdLanog28FJywdjjy7GTvEm1k14bpOjfgDvbfzzRFVi5BMoMyppEXe/Dx5Sg/wFNrIUQ 2x3KkXIpElIifSkyGAYJjH+tWIYt6h69wQdrAC3KMg3hicnB/QrVs43JVXrGUQ7IhnDX 5s5HtFt8tO5+vE/pNUEOjSL+wbmRzQHW8USq7SjZAMp5ZFcACgrp32Do7c7dJ48P1DOm XLpA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to; bh=MPq7VywDNj/NEEYZeQEIanAipmyEOYNyqZiejzrMImY=; b=L12ldad+Hw3qAzwM+9QJ9HRbt2QIQ4mEhjEN1GEGEQTqWJywSnX4jEUJ58KYn/5LXK TTs5/jgKD1g0dE5SrfWviORYQflih6Kb4KYOut/Fe1d+XieyfA7jMQEJ+Nu8+gTRbsDu z3Vcz6lfUPnYLfZHrMmkOZU9bWbZJeP5l2PXjKsFOcMBZirzlR+FyhsiG1HSVBKXHic9 7E+jUHw4t1ZmQmyAvhVMrlZvfdJWQFcHGVpQmb2PW3sLEn4haDS9nUPPQtIZnP6mMnt+ tX/AeRHW9EsUrtP45BQ95mSmmcrxlOEW1smdIWQM9vVb34elhZh4/77juB3p9jVraz2H 2aJg==
X-Gm-Message-State: ALKqPwdBl0TN/MWqCDvqhiNkZF2updh828jsfxpPYGeMWTeOluqTYgt9 78JkjG7OD+gJpsN8rzJWbjzxcow/isDnQv0wb4yVuZWb
X-Google-Smtp-Source: AB8JxZprn4pvZ8TwTpBYrWMNmHJxvlxfnrVHoUNXg3pDxHf7JOY33HjUAqSetkh1UHjGzgd2mTUcINPLhdXT0M2alDI=
X-Received: by 2002:a6b:1e4d:: with SMTP id e74-v6mr1858675ioe.36.1525963462451;  Thu, 10 May 2018 07:44:22 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 10 May 2018 07:44:21 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <1F436ED13A22A246A59CA374CBC543998B64E65D@ORSMSX111.amr.corp.intel.com>
References: <1F436ED13A22A246A59CA374CBC543998B64E65D@ORSMSX111.amr.corp.intel.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Thu, 10 May 2018 07:44:21 -0700
Message-ID: <CAN1APdcfmAsM-CBGzFEicBWf6Ck2uRhOmoiooo7d3EPDTjwt7g@mail.gmail.com>
Subject: Re: Cost of parsing ACK frames in QUIC
To: "Deval, Manasi" <manasi.deval@intel.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001ea71c056bdb0e8f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Ufnuw7Oc5nH_vv2vj4wulgMh7pk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 14:44:24 -0000

--0000000000001ea71c056bdb0e8f
Content-Type: text/plain; charset="UTF-8"

While this may be true, please note that QUIC also requires that the entire
packet is valid before it does anything that modifies the state of the
receiver.

This means that you generally have to do two passes of the packet to ensure
that the packet is valid. In the first pass you can then store data for the
optimistic case of a single ACK frame.

That said, arguments about fast(er) processing still apply, but it is no
longer limited to only ACK frames.


On 10 May 2018 at 16.25.50, Deval, Manasi (manasi.deval@intel.com) wrote:

Hi All,



The QUIC header definitions tend to use as few bits as possible by
implementing the policy to use variable size fields. The result of this
policy would be that each receiver needs to do a two part lookup to
identify the field and this needs to be implemented serially in order to
parse the whole frame time.



For example, in a case where no packets were dropped, a sender may receive
an ACK for a single block. If a code path were trying to determine the size
of an ACK, they would have to read 8 fields to determine the size of ACK.



A client only sees a few ACKs. Majority of the ACKs are seen on the server
side. It would be good to simplify this scheme so ACK processing can be
accelerated with SIMD instructions would be good.



Thanks,

Manasi

--0000000000001ea71c056bdb0e8f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">While this may be tr=
ue, please note that QUIC also requires that the entire packet is valid bef=
ore it does anything that modifies the state of the receiver.</div><div id=
=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;c=
olor:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><div id=3D"bloo=
p_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;color:rgb=
a(0,0,0,1.0);margin:0px;line-height:auto">This means that you generally hav=
e to do two passes of the packet to ensure that the packet is valid. In the=
 first pass you can then store data for the optimistic case of a single ACK=
 frame.</div><div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Ar=
ial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br><=
/div><div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font=
-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">That said, ar=
guments about fast(er) processing still apply, but it is no longer limited =
to only ACK frames.</div><div id=3D"bloop_customfont" style=3D"font-family:=
Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height=
:auto"><br></div> <br><p class=3D"airmail_on">On 10 May 2018 at 16.25.50, D=
eval, Manasi (<a href=3D"mailto:manasi.deval@intel.com">manasi.deval@intel.=
com</a>) wrote:</p> <blockquote type=3D"cite" class=3D"clean_bq"><span><div=
 lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72"><div></div><div>






<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi All,</p>
<p class=3D"MsoNormal">=C2=A0</p>
<p class=3D"MsoNormal">The QUIC header definitions tend to use as few bits =
as possible by implementing the policy to use variable size fields. The res=
ult of this policy would be that each receiver needs to do a two part looku=
p to identify the field and this needs
 to be implemented serially in order to parse the whole frame time. </p>
<p class=3D"MsoNormal">=C2=A0</p>
<p class=3D"MsoNormal">For example, in a case where no packets were dropped=
, a sender may receive an ACK for a single block. If a code path were tryin=
g to determine the size of an ACK, they would have to read 8 fields to dete=
rmine the size of ACK.
</p>
<p class=3D"MsoNormal">=C2=A0</p>
<p class=3D"MsoNormal">A client only sees a few ACKs. Majority of the ACKs =
are seen on the server side. It would be good to simplify this scheme so AC=
K processing can be accelerated with SIMD instructions would be good.
</p>
<p class=3D"MsoNormal">=C2=A0</p>
<p class=3D"MsoNormal">Thanks,</p>
<p class=3D"MsoNormal">Manasi</p>
<p class=3D"MsoNormal"></p>
</div>


</div></div></span></blockquote></body></html>

--0000000000001ea71c056bdb0e8f--


From nobody Thu May 10 07:48:33 2018
Return-Path: <ilubashe@akamai.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDF4812EAF7 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 07:48:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.709
X-Spam-Level: 
X-Spam-Status: No, score=-2.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 hG6zQJdy8MfZ for <quic@ietfa.amsl.com>; Thu, 10 May 2018 07:48:30 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::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 ADB1B1241FC for <quic@ietf.org>; Thu, 10 May 2018 07:48:30 -0700 (PDT)
Received: from pps.filterd (m0122331.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w4AEl2R1004580; Thu, 10 May 2018 15:48:27 +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 : mime-version; s=jan2016.eng; bh=sLqYqbj6F/Txsu/tCQq+IkxxdURm1tGWAzUlcKpR6Dg=; b=f6moue2MR1gJhovcSE+LLTiAxaSPgwleACEvAGNmc1696uxpzq7ge0bGFP6aNiSw4vnu 4md/NmlwOrQXQnPbKPFO4ODysBOJkhYaLHCsHpz9arSfIAunb0DDM8RB3LB7JQAL6a6B HxCVS7sOQmLGR8SiP4UjZP0x27+1kUQNWoRQHGGGzOYd+kK0X+DpB8VDINL8bf2u3XNy nRsRzyRRbViAtWihGjhE92gK8cG9YCVQLW0UYXnD//uu9q35rtctZ76eZsR0Vzc+buz7 Sw7/9WQj/C7//FERWc3IV03eBhxVFiaTNgXyvMwGkc7sTBs3XLKHsnFiSN9nPEic+YsS 0Q== 
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19]) by mx0b-00190b01.pphosted.com with ESMTP id 2hue76nmqn-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 10 May 2018 15:48:27 +0100
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w4AEkuo7012858; Thu, 10 May 2018 10:48:26 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.34]) by prod-mail-ppoint2.akamai.com with ESMTP id 2hs7xvmw6m-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 10 May 2018 10:48:25 -0400
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com (172.27.123.105) by usma1ex-dag3mb4.msg.corp.akamai.com (172.27.123.56) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Thu, 10 May 2018 07:48:25 -0700
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com (172.27.123.105) by usma1ex-dag1mb5.msg.corp.akamai.com (172.27.123.105) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Thu, 10 May 2018 10:48:25 -0400
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com ([172.27.123.105]) by usma1ex-dag1mb5.msg.corp.akamai.com ([172.27.123.105]) with mapi id 15.00.1365.000; Thu, 10 May 2018 10:48:25 -0400
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: =?utf-8?B?TWlra2VsIEZhaG7DuGUgSsO4cmdlbnNlbg==?= <mikkelfj@gmail.com>, "Deval, Manasi" <manasi.deval@intel.com>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Cost of parsing ACK frames in QUIC
Thread-Topic: Cost of parsing ACK frames in QUIC
Thread-Index: AdPoaJzXsjis3gTFQX6IIe0OpT4RMgAJkvOAAAhXJ8A=
Date: Thu, 10 May 2018 14:48:24 +0000
Message-ID: <514f80e45dbe4c588fc1f6be7884a0dd@usma1ex-dag1mb5.msg.corp.akamai.com>
References: <1F436ED13A22A246A59CA374CBC543998B64E65D@ORSMSX111.amr.corp.intel.com> <CAN1APdcfmAsM-CBGzFEicBWf6Ck2uRhOmoiooo7d3EPDTjwt7g@mail.gmail.com>
In-Reply-To: <CAN1APdcfmAsM-CBGzFEicBWf6Ck2uRhOmoiooo7d3EPDTjwt7g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.34.240]
Content-Type: multipart/alternative; boundary="_000_514f80e45dbe4c588fc1f6be7884a0ddusma1exdag1mb5msgcorpak_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-10_06:, , 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=531 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805100141
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-10_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=471 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805100140
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/45aUS1GXFaos-dxQJW6epsywDkI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 14:48:33 -0000

--_000_514f80e45dbe4c588fc1f6be7884a0ddusma1exdag1mb5msgcorpak_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

TXkgdW5kZXJzdGFuZGluZyBpcyB0aGF0IFFVSUMgcmVxdWlyZXMgdGhhdCB0aGUgcGFja2V0IGRl
Y3J5cHRzIHN1Y2Nlc3NmdWxseSBiZWZvcmUgaXQgY2FuIG1vZGlmeSB0aGUgc3RhdGUgb2YgdGhl
IHJlY2VpdmVyLiAgSG93ZXZlciwgb25jZSBpdCBkZWNyeXB0cyAoaG9wZWZ1bGx5IGluIEgvVyks
IHlvdSBkbyBub3QgbmVlZCB0d28gcGFzc2VzLiAgWW91IGNhbiBtb2RpZnkgdGhlIHN0YXRlIGFz
IHlvdSBwYXJzZSB0aGUgcGFja2V0LiAgSWYgdGhlcmUgaXMgYW55dGhpbmcgc3ludGFjdGljYWxs
eSBvciBzZW1hbnRpY2FsbHkgd3Jvbmcgd2l0aCB0aGUgcGFja2V0LCB0aGF04oCZcyBhIGNhdXNl
IGZvciBhbiBpbW1lZGlhdGUgY29ubmVjdGlvbiBhYm9ydCwgc28geW91ciBlbnRpcmUgc3RhdGUg
aXMgb3V0IG9mIHRoZSB3aW5kb3cgYXQgdGhhdCBwb2ludCBhbnl3YXkuDQoNCg0KICAqICAgSWdv
cg0KDQpGcm9tOiBNaWtrZWwgRmFobsO4ZSBKw7hyZ2Vuc2VuIFttYWlsdG86bWlra2VsZmpAZ21h
aWwuY29tXQ0KU2VudDogVGh1cnNkYXksIE1heSAxMCwgMjAxOCAxMDo0NCBBTQ0KVG86IERldmFs
LCBNYW5hc2kgPG1hbmFzaS5kZXZhbEBpbnRlbC5jb20+OyBJRVRGIFFVSUMgV0cgPHF1aWNAaWV0
Zi5vcmc+DQpTdWJqZWN0OiBSZTogQ29zdCBvZiBwYXJzaW5nIEFDSyBmcmFtZXMgaW4gUVVJQw0K
DQpXaGlsZSB0aGlzIG1heSBiZSB0cnVlLCBwbGVhc2Ugbm90ZSB0aGF0IFFVSUMgYWxzbyByZXF1
aXJlcyB0aGF0IHRoZSBlbnRpcmUgcGFja2V0IGlzIHZhbGlkIGJlZm9yZSBpdCBkb2VzIGFueXRo
aW5nIHRoYXQgbW9kaWZpZXMgdGhlIHN0YXRlIG9mIHRoZSByZWNlaXZlci4NCg0KVGhpcyBtZWFu
cyB0aGF0IHlvdSBnZW5lcmFsbHkgaGF2ZSB0byBkbyB0d28gcGFzc2VzIG9mIHRoZSBwYWNrZXQg
dG8gZW5zdXJlIHRoYXQgdGhlIHBhY2tldCBpcyB2YWxpZC4gSW4gdGhlIGZpcnN0IHBhc3MgeW91
IGNhbiB0aGVuIHN0b3JlIGRhdGEgZm9yIHRoZSBvcHRpbWlzdGljIGNhc2Ugb2YgYSBzaW5nbGUg
QUNLIGZyYW1lLg0KDQpUaGF0IHNhaWQsIGFyZ3VtZW50cyBhYm91dCBmYXN0KGVyKSBwcm9jZXNz
aW5nIHN0aWxsIGFwcGx5LCBidXQgaXQgaXMgbm8gbG9uZ2VyIGxpbWl0ZWQgdG8gb25seSBBQ0sg
ZnJhbWVzLg0KDQoNCg0KT24gMTAgTWF5IDIwMTggYXQgMTYuMjUuNTAsIERldmFsLCBNYW5hc2kg
KG1hbmFzaS5kZXZhbEBpbnRlbC5jb208bWFpbHRvOm1hbmFzaS5kZXZhbEBpbnRlbC5jb20+KSB3
cm90ZToNCkhpIEFsbCwNCg0KVGhlIFFVSUMgaGVhZGVyIGRlZmluaXRpb25zIHRlbmQgdG8gdXNl
IGFzIGZldyBiaXRzIGFzIHBvc3NpYmxlIGJ5IGltcGxlbWVudGluZyB0aGUgcG9saWN5IHRvIHVz
ZSB2YXJpYWJsZSBzaXplIGZpZWxkcy4gVGhlIHJlc3VsdCBvZiB0aGlzIHBvbGljeSB3b3VsZCBi
ZSB0aGF0IGVhY2ggcmVjZWl2ZXIgbmVlZHMgdG8gZG8gYSB0d28gcGFydCBsb29rdXAgdG8gaWRl
bnRpZnkgdGhlIGZpZWxkIGFuZCB0aGlzIG5lZWRzIHRvIGJlIGltcGxlbWVudGVkIHNlcmlhbGx5
IGluIG9yZGVyIHRvIHBhcnNlIHRoZSB3aG9sZSBmcmFtZSB0aW1lLg0KDQpGb3IgZXhhbXBsZSwg
aW4gYSBjYXNlIHdoZXJlIG5vIHBhY2tldHMgd2VyZSBkcm9wcGVkLCBhIHNlbmRlciBtYXkgcmVj
ZWl2ZSBhbiBBQ0sgZm9yIGEgc2luZ2xlIGJsb2NrLiBJZiBhIGNvZGUgcGF0aCB3ZXJlIHRyeWlu
ZyB0byBkZXRlcm1pbmUgdGhlIHNpemUgb2YgYW4gQUNLLCB0aGV5IHdvdWxkIGhhdmUgdG8gcmVh
ZCA4IGZpZWxkcyB0byBkZXRlcm1pbmUgdGhlIHNpemUgb2YgQUNLLg0KDQpBIGNsaWVudCBvbmx5
IHNlZXMgYSBmZXcgQUNLcy4gTWFqb3JpdHkgb2YgdGhlIEFDS3MgYXJlIHNlZW4gb24gdGhlIHNl
cnZlciBzaWRlLiBJdCB3b3VsZCBiZSBnb29kIHRvIHNpbXBsaWZ5IHRoaXMgc2NoZW1lIHNvIEFD
SyBwcm9jZXNzaW5nIGNhbiBiZSBhY2NlbGVyYXRlZCB3aXRoIFNJTUQgaW5zdHJ1Y3Rpb25zIHdv
dWxkIGJlIGdvb2QuDQoNClRoYW5rcywNCk1hbmFzaQ0K

--_000_514f80e45dbe4c588fc1f6be7884a0ddusma1exdag1mb5msgcorpak_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7
fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToy
IDQgNSAzIDUgNCA2IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsN
CglwYW5vc2UtMToyIDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAq
Lw0KcC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGlu
Ow0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFt
aWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7
bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVu
ZGVybGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0
eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJs
aW5lO30NCnAuTXNvTGlzdFBhcmFncmFwaCwgbGkuTXNvTGlzdFBhcmFncmFwaCwgZGl2Lk1zb0xp
c3RQYXJhZ3JhcGgNCgl7bXNvLXN0eWxlLXByaW9yaXR5OjM0Ow0KCW1hcmdpbi10b3A6MGluOw0K
CW1hcmdpbi1yaWdodDowaW47DQoJbWFyZ2luLWJvdHRvbTowaW47DQoJbWFyZ2luLWxlZnQ6LjVp
bjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZh
bWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpwLm1zb25vcm1hbDAsIGxpLm1zb25vcm1hbDAs
IGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCgltc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFt
aWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnAuYWlybWFpbG9uLCBsaS5haXJtYWlsb24sIGRp
di5haXJtYWlsb24NCgl7bXNvLXN0eWxlLW5hbWU6YWlybWFpbF9vbjsNCgltc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDph
dXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5
OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE5DQoJe21zby1zdHlsZS10
eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0K
CWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhw
b3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6
ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5X
b3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLyogTGlzdCBEZWZpbml0aW9ucyAq
Lw0KQGxpc3QgbDANCgl7bXNvLWxpc3QtaWQ6Mjg4ODI0NTc2Ow0KCW1zby1saXN0LXR5cGU6aHli
cmlkOw0KCW1zby1saXN0LXRlbXBsYXRlLWlkczotMjU1OTY0MTI2IDE5OTI4MzcwNjIgNjc2OTg2
OTEgNjc2OTg2OTMgNjc2OTg2ODkgNjc2OTg2OTEgNjc2OTg2OTMgNjc2OTg2ODkgNjc2OTg2OTEg
Njc2OTg2OTM7fQ0KQGxpc3QgbDA6bGV2ZWwxDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1
bGxldDsNCgltc28tbGV2ZWwtdGV4dDotOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1z
by1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9u
dC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJbXNvLWZhcmVhc3QtZm9udC1mYW1pbHk6
Q2FsaWJyaTsNCgltc28tYmlkaS1mb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIjt9DQpAbGlz
dCBsMDpsZXZlbDINCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZl
bC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1w
b3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseToiQ291cmll
ciBOZXciO30NCkBsaXN0IGwwOmxldmVsMw0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxs
ZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1z
by1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9u
dC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwwOmxldmVsNA0KCXttc28tbGV2ZWwtbnVtYmVy
LWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3Rv
cDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDot
LjI1aW47DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwwOmxldmVsNQ0KCXttc28tbGV2
ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwt
dGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1p
bmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6bGV2
ZWw2DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrv
gqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlv
bjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0K
QGxpc3QgbDA6bGV2ZWw3DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28t
bGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51
bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpT
eW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWw4DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxl
dDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1s
ZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1m
YW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMDpsZXZlbDkNCgl7bXNvLWxldmVsLW51bWJl
ci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0
b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6
LS4yNWluOw0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpvbA0KCXttYXJnaW4tYm90dG9tOjBp
bjt9DQp1bA0KCXttYXJnaW4tYm90dG9tOjBpbjt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1z
byA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIg
Lz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVs
YXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8
L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJF
Ti1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlv
bjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+TXkgdW5kZXJzdGFuZGluZyBpcyB0aGF0IFFVSUMg
cmVxdWlyZXMgdGhhdCB0aGUgcGFja2V0IGRlY3J5cHRzIHN1Y2Nlc3NmdWxseSBiZWZvcmUgaXQg
Y2FuIG1vZGlmeSB0aGUgc3RhdGUgb2YgdGhlIHJlY2VpdmVyLiZuYnNwOyBIb3dldmVyLCBvbmNl
IGl0IGRlY3J5cHRzIChob3BlZnVsbHkgaW4gSC9XKSwgeW91IGRvIG5vdCBuZWVkIHR3byBwYXNz
ZXMuJm5ic3A7IFlvdSBjYW4gbW9kaWZ5IHRoZSBzdGF0ZSBhcyB5b3UgcGFyc2UNCiB0aGUgcGFj
a2V0LiZuYnNwOyBJZiB0aGVyZSBpcyBhbnl0aGluZyBzeW50YWN0aWNhbGx5IG9yIHNlbWFudGlj
YWxseSB3cm9uZyB3aXRoIHRoZSBwYWNrZXQsIHRoYXTigJlzIGEgY2F1c2UgZm9yIGFuIGltbWVk
aWF0ZSBjb25uZWN0aW9uIGFib3J0LCBzbyB5b3VyIGVudGlyZSBzdGF0ZSBpcyBvdXQgb2YgdGhl
IHdpbmRvdyBhdCB0aGF0IHBvaW50IGFueXdheS48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHVsIHN0eWxlPSJtYXJnaW4tdG9wOjBp
biIgdHlwZT0iZGlzYyI+DQo8bGkgY2xhc3M9Ik1zb0xpc3RQYXJhZ3JhcGgiIHN0eWxlPSJtYXJn
aW4tbGVmdDowaW47bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzEiPklnb3I8bzpwPjwvbzpwPjwvbGk+
PC91bD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4N
CjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBwdDtw
YWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPkZyb206
PC9iPiBNaWtrZWwgRmFobsO4ZSBKw7hyZ2Vuc2VuIFttYWlsdG86bWlra2VsZmpAZ21haWwuY29t
XQ0KPGJyPg0KPGI+U2VudDo8L2I+IFRodXJzZGF5LCBNYXkgMTAsIDIwMTggMTA6NDQgQU08YnI+
DQo8Yj5Ubzo8L2I+IERldmFsLCBNYW5hc2kgJmx0O21hbmFzaS5kZXZhbEBpbnRlbC5jb20mZ3Q7
OyBJRVRGIFFVSUMgV0cgJmx0O3F1aWNAaWV0Zi5vcmcmZ3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+
IFJlOiBDb3N0IG9mIHBhcnNpbmcgQUNLIGZyYW1lcyBpbiBRVUlDPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8ZGl2IGlkPSJibG9vcF9jdXN0b21mb250Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90
OyxzYW5zLXNlcmlmIj5XaGlsZSB0aGlzIG1heSBiZSB0cnVlLCBwbGVhc2Ugbm90ZSB0aGF0IFFV
SUMgYWxzbyByZXF1aXJlcyB0aGF0IHRoZSBlbnRpcmUgcGFja2V0IGlzIHZhbGlkIGJlZm9yZSBp
dCBkb2VzIGFueXRoaW5nIHRoYXQgbW9kaWZpZXMgdGhlIHN0YXRlIG9mIHRoZSByZWNlaXZlci48
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXYgaWQ9ImJsb29wX2N1c3RvbWZvbnQi
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdiBpZD0iYmxvb3BfY3VzdG9tZm9udCI+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+VGhpcyBtZWFucyB0aGF0IHlvdSBn
ZW5lcmFsbHkgaGF2ZSB0byBkbyB0d28gcGFzc2VzIG9mIHRoZSBwYWNrZXQgdG8gZW5zdXJlIHRo
YXQgdGhlIHBhY2tldCBpcyB2YWxpZC4gSW4gdGhlIGZpcnN0IHBhc3MgeW91IGNhbiB0aGVuIHN0
b3JlIGRhdGEgZm9yIHRoZSBvcHRpbWlzdGljIGNhc2Ugb2YNCiBhIHNpbmdsZSBBQ0sgZnJhbWUu
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2IGlkPSJibG9vcF9jdXN0b21mb250
Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXYgaWQ9ImJsb29wX2N1c3RvbWZvbnQiPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYiPlRoYXQgc2FpZCwgYXJndW1lbnRz
IGFib3V0IGZhc3QoZXIpIHByb2Nlc3Npbmcgc3RpbGwgYXBwbHksIGJ1dCBpdCBpcyBubyBsb25n
ZXIgbGltaXRlZCB0byBvbmx5IEFDSyBmcmFtZXMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9k
aXY+DQo8ZGl2IGlkPSJibG9vcF9jdXN0b21mb250Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZx
dW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iYWlybWFpbG9uIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+T24gMTAg
TWF5IDIwMTggYXQgMTYuMjUuNTAsIERldmFsLCBNYW5hc2kgKDxhIGhyZWY9Im1haWx0bzptYW5h
c2kuZGV2YWxAaW50ZWwuY29tIj5tYW5hc2kuZGV2YWxAaW50ZWwuY29tPC9hPikgd3JvdGU6PG86
cD48L286cD48L3NwYW4+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7
bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmIj5IaSBBbGwsPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtm
b250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+Jm5ic3A7PG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9u
dC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJp
ZiI+VGhlIFFVSUMgaGVhZGVyIGRlZmluaXRpb25zIHRlbmQgdG8gdXNlIGFzIGZldyBiaXRzIGFz
IHBvc3NpYmxlIGJ5IGltcGxlbWVudGluZyB0aGUgcG9saWN5IHRvIHVzZSB2YXJpYWJsZSBzaXpl
DQogZmllbGRzLiBUaGUgcmVzdWx0IG9mIHRoaXMgcG9saWN5IHdvdWxkIGJlIHRoYXQgZWFjaCBy
ZWNlaXZlciBuZWVkcyB0byBkbyBhIHR3byBwYXJ0IGxvb2t1cCB0byBpZGVudGlmeSB0aGUgZmll
bGQgYW5kIHRoaXMgbmVlZHMgdG8gYmUgaW1wbGVtZW50ZWQgc2VyaWFsbHkgaW4gb3JkZXIgdG8g
cGFyc2UgdGhlIHdob2xlIGZyYW1lIHRpbWUuDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdp
bi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmIj4mbmJzcDs8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmIj5Gb3Ig
ZXhhbXBsZSwgaW4gYSBjYXNlIHdoZXJlIG5vIHBhY2tldHMgd2VyZSBkcm9wcGVkLCBhIHNlbmRl
ciBtYXkgcmVjZWl2ZSBhbiBBQ0sgZm9yIGEgc2luZ2xlIGJsb2NrLiBJZiBhIGNvZGUNCiBwYXRo
IHdlcmUgdHJ5aW5nIHRvIGRldGVybWluZSB0aGUgc2l6ZSBvZiBhbiBBQ0ssIHRoZXkgd291bGQg
aGF2ZSB0byByZWFkIDggZmllbGRzIHRvIGRldGVybWluZSB0aGUgc2l6ZSBvZiBBQ0suDQo8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJm
b250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNl
cmlmIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8i
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGlj
YSZxdW90OyxzYW5zLXNlcmlmIj5BIGNsaWVudCBvbmx5IHNlZXMgYSBmZXcgQUNLcy4gTWFqb3Jp
dHkgb2YgdGhlIEFDS3MgYXJlIHNlZW4gb24gdGhlIHNlcnZlciBzaWRlLiBJdCB3b3VsZCBiZSBn
b29kIHRvIHNpbXBsaWZ5IHRoaXMNCiBzY2hlbWUgc28gQUNLIHByb2Nlc3NpbmcgY2FuIGJlIGFj
Y2VsZXJhdGVkIHdpdGggU0lNRCBpbnN0cnVjdGlvbnMgd291bGQgYmUgZ29vZC4NCjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQt
c2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYi
PiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1
b3Q7LHNhbnMtc2VyaWYiPlRoYW5rcyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0
b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZx
dW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmIj5NYW5hc2k8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvYm9k
eT4NCjwvaHRtbD4NCg==

--_000_514f80e45dbe4c588fc1f6be7884a0ddusma1exdag1mb5msgcorpak_--


From nobody Thu May 10 07:50:20 2018
Return-Path: <nibanks@microsoft.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1EC0A1241FC for <quic@ietfa.amsl.com>; Thu, 10 May 2018 07:50:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.009
X-Spam-Level: 
X-Spam-Status: No, score=-2.009 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 bj7L68r4_8yV for <quic@ietfa.amsl.com>; Thu, 10 May 2018 07:50:00 -0700 (PDT)
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0093.outbound.protection.outlook.com [104.47.34.93]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id C09BA12EB0A for <quic@ietf.org>; Thu, 10 May 2018 07:49:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=QxXVLQGqriFqcNREJMwzwtWIEUSzoj3YeuvwgknNndU=; b=H8EN/zSDK2uPbiK+jS0oxzA3Y3Bhs0thmJIbUzWkW2jD/F5HuUI8fED1BravZNjnhMibhGwcDlqdtbYoGQECxyiCNBnDCrB2omuu0yyF2gZHKxa86SdJ+9rm6wUB1ew2AsT2R9mYLwaLv4q0xTdRxr9btgELZdHAlUmGBbtS5AI=
Received: from DM5PR2101MB0901.namprd21.prod.outlook.com (52.132.132.158) by DM5PR2101MB1047.namprd21.prod.outlook.com (52.132.128.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.776.3; Thu, 10 May 2018 14:49:58 +0000
Received: from DM5PR2101MB0901.namprd21.prod.outlook.com ([fe80::ac02:3f79:af:e239]) by DM5PR2101MB0901.namprd21.prod.outlook.com ([fe80::ac02:3f79:af:e239%2]) with mapi id 15.20.0776.004; Thu, 10 May 2018 14:49:58 +0000
From: Nick Banks <nibanks@microsoft.com>
To: =?utf-8?B?TWlra2VsIEZhaG7DuGUgSsO4cmdlbnNlbg==?= <mikkelfj@gmail.com>, "Deval, Manasi" <manasi.deval@intel.com>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Cost of parsing ACK frames in QUIC
Thread-Topic: Cost of parsing ACK frames in QUIC
Thread-Index: AdPoaJzXsjis3gTFQX6IIe0OpT4RMgABMS+AAAANEdA=
Date: Thu, 10 May 2018 14:49:58 +0000
Message-ID: <DM5PR2101MB0901149C9E14440DF9CEE269B3980@DM5PR2101MB0901.namprd21.prod.outlook.com>
References: <1F436ED13A22A246A59CA374CBC543998B64E65D@ORSMSX111.amr.corp.intel.com> <CAN1APdcfmAsM-CBGzFEicBWf6Ck2uRhOmoiooo7d3EPDTjwt7g@mail.gmail.com>
In-Reply-To: <CAN1APdcfmAsM-CBGzFEicBWf6Ck2uRhOmoiooo7d3EPDTjwt7g@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Owner=nibanks@microsoft.com; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2018-05-10T14:49:56.8437086Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic; Sensitivity=General
x-originating-ip: [2001:4898:80e8::256]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR2101MB1047; 7:2D/rA+ASZdQlBLK0B7qfrpTwoWrj/acJFncli5LpXX3HYHwak++m5x3/nVSwWMPnnXaFpKtGelEpQP2GV38yquttRE2UGHAzqBSq7p+poKdylDwTZZHHyxrGKRRXYEnM7+KaIW2c3HBi1691KnVaF4mZg/np57TuTEDYC+D3/J+nqbAMvAI3VUhAK6WcLkd2kjiTrS/6dlJPWlKppYEpLd2ZzK8wlYiXQz0mFTxDbwbzdA0lheSRKs4uMuwt9Qn+; 20:+DefrBcXThYTDBmaKekPsjH/l/u5a/pMBe84hILp2OsjtEqTW/2MTTAIC++VcyyLVHGzfZp6C3KcZMabPL8DHQ8KHZxJqHMT2lwPMegYc9cIHnVmFpReVmOnxg07zKPXOX8aapW1elOj2vjDH0EYgHrnc1qorucU4dSnPW91B40=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(4534165)(4627221)(201703031133081)(201702281549075)(5600026)(48565401081)(2017052603328)(7193020); SRVR:DM5PR2101MB1047; 
x-ms-traffictypediagnostic: DM5PR2101MB1047:
x-microsoft-antispam-prvs: <DM5PR2101MB1047C6BD9F8FC6D47097A99FB3980@DM5PR2101MB1047.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(158342451672863)(21748063052155)(228905959029699); 
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(3231254)(2018427008)(944501410)(52105095)(10201501046)(6055026)(149027)(150027)(6041310)(20161123558120)(20161123562045)(20161123560045)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:DM5PR2101MB1047; BCL:0; PCL:0; RULEID:; SRVR:DM5PR2101MB1047; 
x-forefront-prvs: 066898046A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(376002)(346002)(366004)(39380400002)(39860400002)(189003)(199004)(53754006)(86362001)(74316002)(106356001)(55016002)(54896002)(5250100002)(6306002)(5660300001)(59450400001)(19609705001)(10090500001)(2900100001)(22452003)(14454004)(7696005)(97736004)(99286004)(110136005)(236005)(9686003)(53936002)(105586002)(10290500003)(3660700001)(81156014)(790700001)(476003)(7736002)(2906002)(6116002)(316002)(486006)(8676002)(6246003)(39060400002)(33656002)(446003)(86612001)(6436002)(8936002)(478600001)(3280700002)(6346003)(186003)(8990500004)(102836004)(6506007)(11346002)(76176011)(229853002)(68736007)(53546011)(81166006)(25786009)(46003); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR2101MB1047; H:DM5PR2101MB0901.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=nibanks@microsoft.com; 
x-microsoft-antispam-message-info: pD5LZV6sNr/DvTCWxeM/fqjciPorNakGMpa+kCEbB/K+pdKpSIkXb0qjLkqh5GhVuY0gMMebnlT+Ac/bLv/gULUQXQfgv3m5WAxFX19FNUAm/HWrh3EO0Gh6KjWwYlqpV0hdSFQsqMgx6sirCELXtPtYsKBDfroWR0ez78oHmKH64jC1tU7EXXdjPuHlAPZM
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_DM5PR2101MB0901149C9E14440DF9CEE269B3980DM5PR2101MB0901_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 1c556ccb-1b52-48c0-f0b2-08d5b6854d14
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 1c556ccb-1b52-48c0-f0b2-08d5b6854d14
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 May 2018 14:49:58.2006 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR2101MB1047
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Mcbc_l1oGY0ncovy_19sheh-Vb4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 14:50:03 -0000

--_000_DM5PR2101MB0901149C9E14440DF9CEE269B3980DM5PR2101MB0901_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SeKAmW0gZG9u4oCZdCBhZ3JlZSB0aGF0IHlvdSBuZWVkIHRvIG1ha2UgdHdvIHBhc3NlcyBvbiBh
IHBhY2tldCB3aGVuIHByb2Nlc3NpbmcgQUNLIGZyYW1lcy4gSWYgeW91IGhhdmUgc3VjY2Vzc2Z1
bGx5IGRlY3J5cHRlZCB0aGUgcGFja2V0IGFuZCB5b3UgZ290IHRvIHRoZSBwb2ludCBvZiBwcm9j
ZXNzaW5nIEFDSyBmcmFtZXMsIHRoZW4gYW55IG90aGVyIGVycm9yIHRoYXQgd291bGQgbGF0ZXIg
ZW5jb3VudGVyIHdoaWxlIHByb2Nlc3NpbmcgdGhlIHBhY2tldCB3b3VsZCBsaWtlbHkgYmUgY29u
c2lkZXJlZCBhIHByb3RvY29sIHZpb2xhdGlvbiwgd291bGQgaXQgbm90PyBJZiBzbywgdGhlbiB5
b3Ugd291bGQgdGVybWluYXRlIHRoZSBlbnRpcmUgY29ubmVjdGlvbi4NCg0KVGhhdCBiZWluZyBz
YWlkLCBvbiB0aGUgdG9waWMgb2YgYmVpbmcgYSBiaXQgbW9yZSBleHBlbnNpdmUgdG8gcHJvY2Vz
cyBBQ0sgZnJhbWVzIGluIGdlbmVyYWwsIFFVSUMgaGFzIG1hZGUgYSBkZWNpc2lvbiB0byBnZW5l
cmFsbHkgcHJlZmVyIHNtYWxsZXIgd2lyZSBlbmNvZGluZyBvdmVyIENQVSBjb3N0cywgd2hlcmUg
YXBwcm9wcmlhdGUuIElmIHlvdSBoYXZlIGEgc3VnZ2VzdGlvbiB0byBjaGFuZ2UgdGhlIGVuY29k
aW5nIHRoYXQgZG9lc27igJl0IGluY3JlYXNlIHRoZSB3aXJlIGZvcm1hdCBjb3N0LCB3ZSBjb3Vs
ZCB0YWtlIGEgbG9vayBhdCBpdC4NCg0KLSBOaWNrDQoNCkZyb206IFFVSUMgPHF1aWMtYm91bmNl
c0BpZXRmLm9yZz4gT24gQmVoYWxmIE9mIE1pa2tlbCBGYWhuw7hlIErDuHJnZW5zZW4NClNlbnQ6
IFRodXJzZGF5LCBNYXkgMTAsIDIwMTggNzo0NCBBTQ0KVG86IERldmFsLCBNYW5hc2kgPG1hbmFz
aS5kZXZhbEBpbnRlbC5jb20+OyBJRVRGIFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc+DQpTdWJqZWN0
OiBSZTogQ29zdCBvZiBwYXJzaW5nIEFDSyBmcmFtZXMgaW4gUVVJQw0KDQpXaGlsZSB0aGlzIG1h
eSBiZSB0cnVlLCBwbGVhc2Ugbm90ZSB0aGF0IFFVSUMgYWxzbyByZXF1aXJlcyB0aGF0IHRoZSBl
bnRpcmUgcGFja2V0IGlzIHZhbGlkIGJlZm9yZSBpdCBkb2VzIGFueXRoaW5nIHRoYXQgbW9kaWZp
ZXMgdGhlIHN0YXRlIG9mIHRoZSByZWNlaXZlci4NCg0KVGhpcyBtZWFucyB0aGF0IHlvdSBnZW5l
cmFsbHkgaGF2ZSB0byBkbyB0d28gcGFzc2VzIG9mIHRoZSBwYWNrZXQgdG8gZW5zdXJlIHRoYXQg
dGhlIHBhY2tldCBpcyB2YWxpZC4gSW4gdGhlIGZpcnN0IHBhc3MgeW91IGNhbiB0aGVuIHN0b3Jl
IGRhdGEgZm9yIHRoZSBvcHRpbWlzdGljIGNhc2Ugb2YgYSBzaW5nbGUgQUNLIGZyYW1lLg0KDQpU
aGF0IHNhaWQsIGFyZ3VtZW50cyBhYm91dCBmYXN0KGVyKSBwcm9jZXNzaW5nIHN0aWxsIGFwcGx5
LCBidXQgaXQgaXMgbm8gbG9uZ2VyIGxpbWl0ZWQgdG8gb25seSBBQ0sgZnJhbWVzLg0KDQoNCg0K
T24gMTAgTWF5IDIwMTggYXQgMTYuMjUuNTAsIERldmFsLCBNYW5hc2kgKG1hbmFzaS5kZXZhbEBp
bnRlbC5jb208bWFpbHRvOm1hbmFzaS5kZXZhbEBpbnRlbC5jb20+KSB3cm90ZToNCkhpIEFsbCwN
Cg0KVGhlIFFVSUMgaGVhZGVyIGRlZmluaXRpb25zIHRlbmQgdG8gdXNlIGFzIGZldyBiaXRzIGFz
IHBvc3NpYmxlIGJ5IGltcGxlbWVudGluZyB0aGUgcG9saWN5IHRvIHVzZSB2YXJpYWJsZSBzaXpl
IGZpZWxkcy4gVGhlIHJlc3VsdCBvZiB0aGlzIHBvbGljeSB3b3VsZCBiZSB0aGF0IGVhY2ggcmVj
ZWl2ZXIgbmVlZHMgdG8gZG8gYSB0d28gcGFydCBsb29rdXAgdG8gaWRlbnRpZnkgdGhlIGZpZWxk
IGFuZCB0aGlzIG5lZWRzIHRvIGJlIGltcGxlbWVudGVkIHNlcmlhbGx5IGluIG9yZGVyIHRvIHBh
cnNlIHRoZSB3aG9sZSBmcmFtZSB0aW1lLg0KDQpGb3IgZXhhbXBsZSwgaW4gYSBjYXNlIHdoZXJl
IG5vIHBhY2tldHMgd2VyZSBkcm9wcGVkLCBhIHNlbmRlciBtYXkgcmVjZWl2ZSBhbiBBQ0sgZm9y
IGEgc2luZ2xlIGJsb2NrLiBJZiBhIGNvZGUgcGF0aCB3ZXJlIHRyeWluZyB0byBkZXRlcm1pbmUg
dGhlIHNpemUgb2YgYW4gQUNLLCB0aGV5IHdvdWxkIGhhdmUgdG8gcmVhZCA4IGZpZWxkcyB0byBk
ZXRlcm1pbmUgdGhlIHNpemUgb2YgQUNLLg0KDQpBIGNsaWVudCBvbmx5IHNlZXMgYSBmZXcgQUNL
cy4gTWFqb3JpdHkgb2YgdGhlIEFDS3MgYXJlIHNlZW4gb24gdGhlIHNlcnZlciBzaWRlLiBJdCB3
b3VsZCBiZSBnb29kIHRvIHNpbXBsaWZ5IHRoaXMgc2NoZW1lIHNvIEFDSyBwcm9jZXNzaW5nIGNh
biBiZSBhY2NlbGVyYXRlZCB3aXRoIFNJTUQgaW5zdHJ1Y3Rpb25zIHdvdWxkIGJlIGdvb2QuDQoN
ClRoYW5rcywNCk1hbmFzaQ0K

--_000_DM5PR2101MB0901149C9E14440DF9CEE269B3980DM5PR2101MB0901_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
SGVsdmV0aWNhOw0KCXBhbm9zZS0xOjIgMTEgNiA0IDIgMiAyIDIgMiA0O30NCkBmb250LWZhY2UN
Cgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAz
IDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAx
NSA1IDIgMiAyIDQgMyAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFs
LCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90
dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIs
c2Fucy1zZXJpZjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlv
cml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2
aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5
OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLm1zb25v
cm1hbDAsIGxpLm1zb25vcm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1uYW1lOm1z
b25vcm1hbDsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0K
CW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNp
emU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnAuYWlybWFp
bG9uLCBsaS5haXJtYWlsb24sIGRpdi5haXJtYWlsb24NCgl7bXNvLXN0eWxlLW5hbWU6YWlybWFp
bF9vbjsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGluOw0KCW1z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglmb250LXNpemU6
MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNwYW4uRW1haWxT
dHlsZTE5DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJD
YWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQN
Cgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDt9DQpAcGFn
ZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGlu
IDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0K
LS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpl
eHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0
ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6
ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0t
Pg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUi
Pg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPknigJlt
IGRvbuKAmXQgYWdyZWUgdGhhdCB5b3UgbmVlZCB0byBtYWtlIHR3byBwYXNzZXMgb24gYSBwYWNr
ZXQgd2hlbiBwcm9jZXNzaW5nIEFDSyBmcmFtZXMuIElmIHlvdSBoYXZlIHN1Y2Nlc3NmdWxseSBk
ZWNyeXB0ZWQgdGhlIHBhY2tldCBhbmQgeW91IGdvdCB0byB0aGUgcG9pbnQgb2YgcHJvY2Vzc2lu
ZyBBQ0sgZnJhbWVzLCB0aGVuIGFueSBvdGhlciBlcnJvciB0aGF0IHdvdWxkIGxhdGVyIGVuY291
bnRlciB3aGlsZQ0KIHByb2Nlc3NpbmcgdGhlIHBhY2tldCB3b3VsZCBsaWtlbHkgYmUgY29uc2lk
ZXJlZCBhIHByb3RvY29sIHZpb2xhdGlvbiwgd291bGQgaXQgbm90PyBJZiBzbywgdGhlbiB5b3Ug
d291bGQgdGVybWluYXRlIHRoZSBlbnRpcmUgY29ubmVjdGlvbi48bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+VGhhdCBiZWluZyBzYWlkLCBvbiB0aGUgdG9waWMgb2YgYmVpbmcgYSBiaXQgbW9yZSBl
eHBlbnNpdmUgdG8gcHJvY2VzcyBBQ0sgZnJhbWVzIGluIGdlbmVyYWwsIFFVSUMgaGFzIG1hZGUg
YSBkZWNpc2lvbiB0byBnZW5lcmFsbHkgcHJlZmVyIHNtYWxsZXIgd2lyZSBlbmNvZGluZyBvdmVy
IENQVSBjb3N0cywgd2hlcmUgYXBwcm9wcmlhdGUuIElmIHlvdSBoYXZlIGEgc3VnZ2VzdGlvbiB0
byBjaGFuZ2UgdGhlIGVuY29kaW5nDQogdGhhdCBkb2VzbuKAmXQgaW5jcmVhc2UgdGhlIHdpcmUg
Zm9ybWF0IGNvc3QsIHdlIGNvdWxkIHRha2UgYSBsb29rIGF0IGl0LjxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj4tIE5pY2s8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10
b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxiPkZyb206PC9iPiBRVUlDICZsdDtxdWljLWJvdW5jZXNAaWV0Zi5v
cmcmZ3Q7IDxiPk9uIEJlaGFsZiBPZiA8L2I+DQpNaWtrZWwgRmFobsO4ZSBKw7hyZ2Vuc2VuPGJy
Pg0KPGI+U2VudDo8L2I+IFRodXJzZGF5LCBNYXkgMTAsIDIwMTggNzo0NCBBTTxicj4NCjxiPlRv
OjwvYj4gRGV2YWwsIE1hbmFzaSAmbHQ7bWFuYXNpLmRldmFsQGludGVsLmNvbSZndDs7IElFVEYg
UVVJQyBXRyAmbHQ7cXVpY0BpZXRmLm9yZyZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IENv
c3Qgb2YgcGFyc2luZyBBQ0sgZnJhbWVzIGluIFFVSUM8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXYg
aWQ9ImJsb29wX2N1c3RvbWZvbnQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMt
c2VyaWYiPldoaWxlIHRoaXMgbWF5IGJlIHRydWUsIHBsZWFzZSBub3RlIHRoYXQgUVVJQyBhbHNv
IHJlcXVpcmVzIHRoYXQgdGhlIGVudGlyZSBwYWNrZXQgaXMgdmFsaWQgYmVmb3JlIGl0IGRvZXMg
YW55dGhpbmcgdGhhdCBtb2RpZmllcyB0aGUgc3RhdGUgb2YgdGhlIHJlY2VpdmVyLjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdiBpZD0iYmxvb3BfY3VzdG9tZm9udCI+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWls
eTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPC9kaXY+DQo8ZGl2IGlkPSJibG9vcF9jdXN0b21mb250Ij4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90
O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmIj5UaGlzIG1lYW5zIHRoYXQgeW91IGdlbmVyYWxs
eSBoYXZlIHRvIGRvIHR3byBwYXNzZXMgb2YgdGhlIHBhY2tldCB0byBlbnN1cmUgdGhhdCB0aGUg
cGFja2V0IGlzIHZhbGlkLiBJbiB0aGUgZmlyc3QgcGFzcyB5b3UgY2FuIHRoZW4gc3RvcmUgZGF0
YSBmb3IgdGhlIG9wdGltaXN0aWMgY2FzZSBvZg0KIGEgc2luZ2xlIEFDSyBmcmFtZS48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXYgaWQ9ImJsb29wX2N1c3RvbWZvbnQiPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdiBpZD0iYmxvb3BfY3VzdG9tZm9udCI+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVv
dDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+VGhhdCBzYWlkLCBhcmd1bWVudHMgYWJvdXQg
ZmFzdChlcikgcHJvY2Vzc2luZyBzdGlsbCBhcHBseSwgYnV0IGl0IGlzIG5vIGxvbmdlciBsaW1p
dGVkIHRvIG9ubHkgQUNLIGZyYW1lcy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxk
aXYgaWQ9ImJsb29wX2N1c3RvbWZvbnQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNh
bnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJhaXJtYWlsb24iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2Zv
bnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmIj5PbiAxMCBNYXkgMjAx
OCBhdCAxNi4yNS41MCwgRGV2YWwsIE1hbmFzaSAoPGEgaHJlZj0ibWFpbHRvOm1hbmFzaS5kZXZh
bEBpbnRlbC5jb20iPm1hbmFzaS5kZXZhbEBpbnRlbC5jb208L2E+KSB3cm90ZTo8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4t
Ym90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0
aWNhJnF1b3Q7LHNhbnMtc2VyaWYiPkhpIEFsbCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdp
bi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmIj4mbmJzcDs8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmIj5UaGUg
UVVJQyBoZWFkZXIgZGVmaW5pdGlvbnMgdGVuZCB0byB1c2UgYXMgZmV3IGJpdHMgYXMgcG9zc2li
bGUgYnkgaW1wbGVtZW50aW5nIHRoZSBwb2xpY3kgdG8gdXNlIHZhcmlhYmxlIHNpemUNCiBmaWVs
ZHMuIFRoZSByZXN1bHQgb2YgdGhpcyBwb2xpY3kgd291bGQgYmUgdGhhdCBlYWNoIHJlY2VpdmVy
IG5lZWRzIHRvIGRvIGEgdHdvIHBhcnQgbG9va3VwIHRvIGlkZW50aWZ5IHRoZSBmaWVsZCBhbmQg
dGhpcyBuZWVkcyB0byBiZSBpbXBsZW1lbnRlZCBzZXJpYWxseSBpbiBvcmRlciB0byBwYXJzZSB0
aGUgd2hvbGUgZnJhbWUgdGltZS4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1
b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYiPkZvciBleGFtcGxl
LCBpbiBhIGNhc2Ugd2hlcmUgbm8gcGFja2V0cyB3ZXJlIGRyb3BwZWQsIGEgc2VuZGVyIG1heSBy
ZWNlaXZlIGFuIEFDSyBmb3IgYSBzaW5nbGUgYmxvY2suIElmIGEgY29kZQ0KIHBhdGggd2VyZSB0
cnlpbmcgdG8gZGV0ZXJtaW5lIHRoZSBzaXplIG9mIGFuIEFDSywgdGhleSB3b3VsZCBoYXZlIHRv
IHJlYWQgOCBmaWVsZHMgdG8gZGV0ZXJtaW5lIHRoZSBzaXplIG9mIEFDSy4NCjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYiPiZu
YnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7
LHNhbnMtc2VyaWYiPkEgY2xpZW50IG9ubHkgc2VlcyBhIGZldyBBQ0tzLiBNYWpvcml0eSBvZiB0
aGUgQUNLcyBhcmUgc2VlbiBvbiB0aGUgc2VydmVyIHNpZGUuIEl0IHdvdWxkIGJlIGdvb2QgdG8g
c2ltcGxpZnkgdGhpcw0KIHNjaGVtZSBzbyBBQ0sgcHJvY2Vzc2luZyBjYW4gYmUgYWNjZWxlcmF0
ZWQgd2l0aCBTSU1EIGluc3RydWN0aW9ucyB3b3VsZCBiZSBnb29kLg0KPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDph
dXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEw
LjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+Jm5ic3A7
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fu
cy1zZXJpZiI+VGhhbmtzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVs
dmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYiPk1hbmFzaTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9o
dG1sPg0K

--_000_DM5PR2101MB0901149C9E14440DF9CEE269B3980DM5PR2101MB0901_--


From nobody Thu May 10 07:52:15 2018
Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9B72112EB00 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 07:52:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 dsvqZAsjBxQM for <quic@ietfa.amsl.com>; Thu, 10 May 2018 07:52:11 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B62F11241FC for <quic@ietf.org>; Thu, 10 May 2018 07:52:11 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id a10-v6so3312620ioc.9 for <quic@ietf.org>; Thu, 10 May 2018 07:52:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to;  bh=H2KnolZP2sKh9BLhEDc96pIpQQDzBTO0QQ1I9ssTL1M=; b=JRxXccWjlYJfCC0XDV0L/dTTeWDG3v8UY4PwgNzAupVNeHSisbbSUSB/SaG5O+eDPY r926E6hFn50TkocVcGnhUoODPWFKUfdPJ5cifbb5r55S8zvwgZ/uX7IGKr2bu7Xt7ofa +lz9ITsiOE3XGplUAOmC9GdkIH89PyVRrvGD7Nct/e7CmDv9GEF3xhhYhXbnmsMrPUMx XbNcjmGzyM5SbUQvQ8s/q2m9x+L+Pkcvm7zKbchRf7wpo57RC/pGdR5OgPtlQrOrRGdb A8LnTZfQd2cp5XBcz7iFGTxaGubNbUDr8IhzfM2bEBL4CBlzxZLGFq/TnR7sBd+4OXYu nLPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to; bh=H2KnolZP2sKh9BLhEDc96pIpQQDzBTO0QQ1I9ssTL1M=; b=sEWxwHaaGAn79xDPozdL4lGbFNPoWV4nxhsCMd8oTecQqeduYxubHhMgMD9Fwzikbw D/LRpGUoFdVQ7tQFRagrM8MV0zNiRp9dQvRlW7UqXqTRrVNm1gyQb9Hd9mUKKCfyuAny yAuyd2Eu16NhcF6+abPyl6gxvOxzxviocv3AC+q1YYZaawmCrTTkRgAHHuHoFHAZ/cVQ dpVELI6x8reEqXWV/eMjbOtqBd+d5HrEJF5i4JbMzK5KycrF+ZHB/W31BE8itMj9J4m/ I6Tl5Xgv1B+EuC6H3yeasQ5Eiw6h85S/vfKisx7rP/u/WvOpilKveBNQU7GKyobghori XY5g==
X-Gm-Message-State: ALKqPwfvnUvGRhuWgDh3KJ5pmYUwwFjUs4UCBilQShULxahiNtlwrP0R PP8X3i9FI1Pz54tb0VmZmWisdHbob/wBtqr1BpE=
X-Google-Smtp-Source: AB8JxZrAvjXZFz8gW2FPcxzyF4FAhWi4i3tXTM1uAQejoutB/VL7Zsl+cEQzZa24rJmmyaA8JNavdmn9jgQmWxPvDyY=
X-Received: by 2002:a6b:b60a:: with SMTP id g10-v6mr1745539iof.209.1525963931069;  Thu, 10 May 2018 07:52:11 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 10 May 2018 07:52:10 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <DM5PR2101MB0901149C9E14440DF9CEE269B3980@DM5PR2101MB0901.namprd21.prod.outlook.com>
References: <1F436ED13A22A246A59CA374CBC543998B64E65D@ORSMSX111.amr.corp.intel.com> <CAN1APdcfmAsM-CBGzFEicBWf6Ck2uRhOmoiooo7d3EPDTjwt7g@mail.gmail.com> <DM5PR2101MB0901149C9E14440DF9CEE269B3980@DM5PR2101MB0901.namprd21.prod.outlook.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Thu, 10 May 2018 07:52:10 -0700
Message-ID: <CAN1APdfFBRzrf5d2L2i5gtT3_aGUcu0Oi3NVX_UdempAzyq9Tw@mail.gmail.com>
Subject: RE: Cost of parsing ACK frames in QUIC
To: Nick Banks <nibanks@microsoft.com>, "Deval, Manasi" <manasi.deval@intel.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000d33fc056bdb2a10"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/sOf1uLNnPA1ss_yXMCkT9kzm4L0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 14:52:14 -0000

--0000000000000d33fc056bdb2a10
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Yes, that would often be the case.


On 10 May 2018 at 16.49.59, Nick Banks (nibanks@microsoft.com) wrote:

I=E2=80=99m don=E2=80=99t agree that you need to make two passes on a packe=
t when
processing ACK frames. If you have successfully decrypted the packet and
you got to the point of processing ACK frames, then any other error that
would later encounter while processing the packet would likely be
considered a protocol violation, would it not? If so, then you would
terminate the entire connection.



That being said, on the topic of being a bit more expensive to process ACK
frames in general, QUIC has made a decision to generally prefer smaller
wire encoding over CPU costs, where appropriate. If you have a suggestion
to change the encoding that doesn=E2=80=99t increase the wire format cost, =
we could
take a look at it.



- Nick



*From:* QUIC <quic-bounces@ietf.org> *On Behalf Of * Mikkel Fahn=C3=B8e J=
=C3=B8rgensen
*Sent:* Thursday, May 10, 2018 7:44 AM
*To:* Deval, Manasi <manasi.deval@intel.com>; IETF QUIC WG <quic@ietf.org>
*Subject:* Re: Cost of parsing ACK frames in QUIC



While this may be true, please note that QUIC also requires that the entire
packet is valid before it does anything that modifies the state of the
receiver.



This means that you generally have to do two passes of the packet to ensure
that the packet is valid. In the first pass you can then store data for the
optimistic case of a single ACK frame.



That said, arguments about fast(er) processing still apply, but it is no
longer limited to only ACK frames.





On 10 May 2018 at 16.25.50, Deval, Manasi (manasi.deval@intel.com) wrote:

Hi All,



The QUIC header definitions tend to use as few bits as possible by
implementing the policy to use variable size fields. The result of this
policy would be that each receiver needs to do a two part lookup to
identify the field and this needs to be implemented serially in order to
parse the whole frame time.



For example, in a case where no packets were dropped, a sender may receive
an ACK for a single block. If a code path were trying to determine the size
of an ACK, they would have to read 8 fields to determine the size of ACK.



A client only sees a few ACKs. Majority of the ACKs are seen on the server
side. It would be good to simplify this scheme so ACK processing can be
accelerated with SIMD instructions would be good.



Thanks,

Manasi

--0000000000000d33fc056bdb2a10
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Yes, that would ofte=
n be the case.</div> <div id=3D"bloop_sign_1525963882581045248" class=3D"bl=
oop_sign"><div style=3D"font-family:helvetica,arial;font-size:13px"><br></d=
iv></div> <br><p class=3D"airmail_on">On 10 May 2018 at 16.49.59, Nick Bank=
s (<a href=3D"mailto:nibanks@microsoft.com">nibanks@microsoft.com</a>) wrot=
e:</p> <blockquote type=3D"cite" class=3D"clean_bq"><span><div lang=3D"EN-U=
S" link=3D"blue" vlink=3D"purple"><div></div><div>






<div class=3D"WordSection1">
<p class=3D"MsoNormal">I=E2=80=99m don=E2=80=99t agree that you need to mak=
e two passes on a packet when processing ACK frames. If you have successful=
ly decrypted the packet and you got to the point of processing ACK frames, =
then any other error that would later encounter while
 processing the packet would likely be considered a protocol violation, wou=
ld it not? If so, then you would terminate the entire connection.</p>
<p class=3D"MsoNormal">=C2=A0</p>
<p class=3D"MsoNormal">That being said, on the topic of being a bit more ex=
pensive to process ACK frames in general, QUIC has made a decision to gener=
ally prefer smaller wire encoding over CPU costs, where appropriate. If you=
 have a suggestion to change the encoding
 that doesn=E2=80=99t increase the wire format cost, we could take a look a=
t it.</p>
<p class=3D"MsoNormal">=C2=A0</p>
<p class=3D"MsoNormal">- Nick</p>
<p class=3D"MsoNormal">=C2=A0</p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> QUIC &lt;<a href=3D"mailto:quic-bounces=
@ietf.org">quic-bounces@ietf.org</a>&gt; <b>On Behalf Of </b>
Mikkel Fahn=C3=B8e J=C3=B8rgensen<br>
<b>Sent:</b> Thursday, May 10, 2018 7:44 AM<br>
<b>To:</b> Deval, Manasi &lt;<a href=3D"mailto:manasi.deval@intel.com">mana=
si.deval@intel.com</a>&gt;; IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.or=
g">quic@ietf.org</a>&gt;<br>
<b>Subject:</b> Re: Cost of parsing ACK frames in QUIC</p>
</div>
</div>
<p class=3D"MsoNormal">=C2=A0</p>
<div id=3D"bloop_customfont">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;He=
lvetica&quot;,sans-serif">While this may be true, please note that QUIC als=
o requires that the entire packet is valid before it does anything that mod=
ifies the state of the receiver.</span></p>
</div>
<div id=3D"bloop_customfont">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;He=
lvetica&quot;,sans-serif">=C2=A0</span></p>
</div>
<div id=3D"bloop_customfont">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;He=
lvetica&quot;,sans-serif">This means that you generally have to do two pass=
es of the packet to ensure that the packet is valid. In the first pass you =
can then store data for the optimistic case of
 a single ACK frame.</span></p>
</div>
<div id=3D"bloop_customfont">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;He=
lvetica&quot;,sans-serif">=C2=A0</span></p>
</div>
<div id=3D"bloop_customfont">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;He=
lvetica&quot;,sans-serif">That said, arguments about fast(er) processing st=
ill apply, but it is no longer limited to only ACK frames.</span></p>
</div>
<div id=3D"bloop_customfont">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;He=
lvetica&quot;,sans-serif">=C2=A0</span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;He=
lvetica&quot;,sans-serif">=C2=A0</span></p>
<p class=3D"airmailon"><span style=3D"font-size:10.0pt;font-family:&quot;He=
lvetica&quot;,sans-serif">On 10 May 2018 at 16.25.50, Deval, Manasi (<a hre=
f=3D"mailto:manasi.deval@intel.com">manasi.deval@intel.com</a>) wrote:</spa=
n></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">Hi All,</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">=C2=A0</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">The QUIC header definitions tend to use as few bits as possible=
 by implementing the policy to use variable size
 fields. The result of this policy would be that each receiver needs to do =
a two part lookup to identify the field and this needs to be implemented se=
rially in order to parse the whole frame time.
</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">=C2=A0</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">For example, in a case where no packets were dropped, a sender =
may receive an ACK for a single block. If a code
 path were trying to determine the size of an ACK, they would have to read =
8 fields to determine the size of ACK.
</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">=C2=A0</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">A client only sees a few ACKs. Majority of the ACKs are seen on=
 the server side. It would be good to simplify this
 scheme so ACK processing can be accelerated with SIMD instructions would b=
e good.
</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">=C2=A0</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">Thanks,</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">Manasi</span></p>
</div>
</div>
</div>
</blockquote>
</div>


</div></div></span></blockquote></body></html>

--0000000000000d33fc056bdb2a10--


From nobody Thu May 10 07:57:48 2018
Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 43E071242EA for <quic@ietfa.amsl.com>; Thu, 10 May 2018 07:57:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.697
X-Spam-Level: 
X-Spam-Status: No, score=-2.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 FyRXkSNHwdc4 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 07:57:36 -0700 (PDT)
Received: from mail-io0-x235.google.com (mail-io0-x235.google.com [IPv6:2607:f8b0:4001:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8EBF0124205 for <quic@ietf.org>; Thu, 10 May 2018 07:57:36 -0700 (PDT)
Received: by mail-io0-x235.google.com with SMTP id p124-v6so3358462iod.1 for <quic@ietf.org>; Thu, 10 May 2018 07:57:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=vjxJvLD5pzK9fH/nL5TjmW0aPUIpSJiA5bOiuEXWNGA=; b=p+AjfFwrn58gruRzyUtdUQPGr3syK4jNfcNHF7OjflKG0uPhELkI2ypQHbmQUpeZKQ QPqVfs/nksthug2V2DGkTAiMkz2enANSMIQHsysLXZHbzY+j4G/iFIUnXN087aS6XizJ EYTWajB38wDQi2ySLIv5TuPjpOE/c6/fE5DtcScmliFwTHdHiDtBazEHcRDODGThHhqr om/KIvWhhFo2D+nUIlD5l+q+Cnp4yaw9RxHVH58m/ozHreoZnNNWicivbggHvsT+XvrZ WaoPRHU80eaBDhOznIFzHpr2Vdq7LuLen45fRlCwkZeC0iiTxKVnZCa8CiSW5rqZaJXw eTQw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=vjxJvLD5pzK9fH/nL5TjmW0aPUIpSJiA5bOiuEXWNGA=; b=LiOH15nhIfYxlyCkIYSOyZ2XIg4IxnMnE3mXqn8Oh3Cy+wklmsnWRXsLXX3jD/aCgt alzF1/aZNApNa4swr5NAvp1MUv4C9rcQihTbgTRYIylLiAKSodocj6UVqtYqjpQQSBXS ELznYLg8P/DtTQybiIHcc9HdW6Z/eEk3nsmcOFMB08/x9AB4C1mMtiS86EbJVS92krAX o6noem/8gtKOpho8g8TY6+kc1HkFhGWE+40PQLFiaEIDYCeiHHNDIeBNnGej/jKVapA6 shDdFLK5xkJqy3+5tSmDb/+bammgaCMKC/wEfxvrcZzcb09jnlz0/TKXbpe2l8Oaj034 qApA==
X-Gm-Message-State: ALKqPwfvwswcXQG31Ytjg+kEOlEFV+Lq+7tRN67sMMtiFLjhHd3HiACn p7zSb/WJoBB2I37E+Aia7E+xxnbml+INPI2+Oqc=
X-Google-Smtp-Source: AB8JxZqHdyBef3FR8/YgR3/5wHnrjfbI3dLFWaCgIwbUiuSWcisWj1LoML0gxlooXqzxWT4M/fI/2Vg1rnGQlQFhib0=
X-Received: by 2002:a6b:b60a:: with SMTP id g10-v6mr1765560iof.209.1525964256041;  Thu, 10 May 2018 07:57:36 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 10 May 2018 07:57:35 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <9E549481-9B80-4DED-AC37-DC0C91AEBCDE@netapp.com>
References: <CY4PR21MB0630CE4DE6BA4EDF54A1FEB1B6A40@CY4PR21MB0630.namprd21.prod.outlook.com> <1F436ED13A22A246A59CA374CBC543998B60C7AD@ORSMSX111.amr.corp.intel.com> <CAN1APdc3y0EwFqeYVvZs7MtBHhS_9CzwGmcwRqi_6GHWzF3_2Q@mail.gmail.com> <1F436ED13A22A246A59CA374CBC543998B60C851@ORSMSX111.amr.corp.intel.com> <CAN1APdcPkO-HfXqqvjeee6K8U8KSZQdtx=6fW1vZo+H6pKfzzQ@mail.gmail.com> <CAKcm_gP8TRPT7yi1y=mU5Fvq7xB5-1ieyKFLQMPomfabYbkcxA@mail.gmail.com> <bf540ec1f6f045aca1cf2379380630b5@usma1ex-dag1mb5.msg.corp.akamai.com> <SN1PR08MB185446750FCDA2B58C9833C8DA890@SN1PR08MB1854.namprd08.prod.outlook.com> <CACsn0cmJcAxORo4Cd-qyGJL3ZOT5Yz0WgdMqv_AGi4DjedyzFA@mail.gmail.com> <A6F55755-D7E1-40E4-8EC3-D5FE77A2EDBE@fb.com> <CAK-1kemWAW+2Sk5aKJ+RXKUAyjFii4MRH=xK7SE0mr=tbCiRfw@mail.gmail.com> <CAN1APddgX6=CxKdUA718=95EeCUPS60vVxbGFDHa7-eRjw7BxA@mail.gmail.com> <98A67023-AE1D-48EE-BD75-7D03E05E980D@netapp.com> <CAN1APdf2VKXB-sO97S=n5rCC4t6YZL22T=xdxPba9SgRAPKwLA@mail.gmail.com> <5213b2f5-c795-9d54-72b8-01a4a6db03ee@mellanox.com> <9E549481-9B80-4DED-AC37-DC0C91AEBCDE@netapp.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Thu, 10 May 2018 07:57:35 -0700
Message-ID: <CAN1APdcZfs5UwNsyeqb=C3oodC6GzcoPM2EOY8nK1ofV+yqevA@mail.gmail.com>
Subject: Re: Impact of hardware offloads on network stack performance
To: Boris Pismenny <borisp@mellanox.com>, "Eggert, Lars" <lars@netapp.com>
Cc: Roberto Peon <fenix@fb.com>, Mike Bishop <mbishop@evequefou.be>,  Ian Swett <ianswett=40google.com@dmarc.ietf.org>, IETF QUIC WG <quic@ietf.org>, craigt <c@gryning.com>, "Deval, Manasi" <manasi.deval@intel.com>,  Watson Ladd <watsonbladd@gmail.com>, "Lubashev, Igor" <ilubashe@akamai.com>,  Praveen Balasubramanian <pravb@microsoft.com>
Content-Type: multipart/alternative; boundary="0000000000006bde41056bdb3d9f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/HeEOqM6jTRtJ_43oq5qpR_zKJ2g>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 14:57:46 -0000

--0000000000006bde41056bdb3d9f
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Netmap is has a fairly low line count and complexity for what it achieves,
it is not tied to any vendor specific hardware, it patches do seem to
arrive for various cards.

I recently did a user space emulation of netmap where separate user threads
drains and fills the tx and rx rings respectively. I=E2=80=99m not sure thi=
s is
worth it in terms of performance since it adds more synchronization (netmap
makes certain assumptions because some updates are in the kernel). However,
it does provide a uniform buffering layer and it makes it easier to plug in
proper netmap when available. It does move some per message latency out of
the way.


On 10 May 2018 at 16.03.28, Eggert, Lars (lars@netapp.com) wrote:

On 2018-5-10, at 14:57, Boris Pismenny <borisp@mellanox.com> wrote:
> Also, is there a reason to prefer netmap over other userspace network
stacks like DPDK/VPP/etc?

For me personally, the netmap API is a lot more minimal and therefore
easier to integrate. DPDK really wants to take over scheduling, memory
management and all kinds of other stuff besides packet I/O. YMMV.

Lars

--0000000000006bde41056bdb3d9f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Netmap is has a fair=
ly low line count and complexity for what it achieves, it is not tied to an=
y vendor specific hardware, it patches do seem to arrive for various cards.=
</div><div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;fon=
t-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">I recently did a use=
r space emulation of netmap where separate user threads drains and fills th=
e tx and rx rings respectively. I=E2=80=99m not sure this is worth it in te=
rms of performance since it adds more synchronization (netmap makes certain=
 assumptions because some updates are in the kernel). However, it does prov=
ide a uniform buffering layer and it makes it easier to plug in proper netm=
ap when available. It does move some per message latency out of the way.</d=
iv><div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-s=
ize:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div> <br>=
<p class=3D"airmail_on">On 10 May 2018 at 16.03.28, Eggert, Lars (<a href=
=3D"mailto:lars@netapp.com">lars@netapp.com</a>) wrote:</p> <blockquote typ=
e=3D"cite" class=3D"clean_bq"><span><div><div></div><div>On 2018-5-10, at 1=
4:57, Boris Pismenny &lt;<a href=3D"mailto:borisp@mellanox.com">borisp@mell=
anox.com</a>&gt; wrote:
<br>&gt; Also, is there a reason to prefer netmap over other userspace netw=
ork stacks like DPDK/VPP/etc?
<br>
<br>For me personally, the netmap API is a lot more minimal and therefore e=
asier to integrate. DPDK really wants to take over scheduling, memory manag=
ement and all kinds of other stuff besides packet I/O. YMMV.
<br>
<br>Lars
<br></div></div></span></blockquote></body></html>

--0000000000006bde41056bdb3d9f--


From nobody Thu May 10 08:02:25 2018
Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0D087124B18 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 08:02:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.697
X-Spam-Level: 
X-Spam-Status: No, score=-2.697 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 6YjgoTFt63Vo for <quic@ietfa.amsl.com>; Thu, 10 May 2018 08:02:22 -0700 (PDT)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6364A1243FE for <quic@ietf.org>; Thu, 10 May 2018 08:02:21 -0700 (PDT)
Received: by mail-io0-x22b.google.com with SMTP id e78-v6so3381733iod.0 for <quic@ietf.org>; Thu, 10 May 2018 08:02:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=PNiGaSL/aUhqMPzM3/HPm4hba1UOnYFk1Tc5dVAszec=; b=mGpcq41ouAshDl/oaFkhqSPar6yTvK8V6hTDl1HuqobQ6FagCGZfE4tXEDftPnqw7x Z9J03PGDstL2CdpJMqiBTRE9PbOLWwQzUcJ1neQPCuBpR4AVNv7eRX5Ah30wl9xSzRxw /OkGXxsBgaPgnP/+l4CUVGVaFY1bCLcUShs4v7RYSClXBSY7Ya/HA80KOBiD4aQ8tpMB faXVDcCghJetUwEWG6zy0FoQhVvzLon90/epesCYLSPhH4xxBYa51MytoiKfIn320XtY rjkpLrQMCz3f8z3nATPezj68mdGjZp7PcaTvLIzoKTsPtASRJ0GaILomkhH81o6qqK4T RYHw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=PNiGaSL/aUhqMPzM3/HPm4hba1UOnYFk1Tc5dVAszec=; b=s82dY8sZmH0LejfD+Td/kxN8ZFMKf8so3nPymEEeUHQg5+F9Llz5aFpN86Fuaq2L0K nf4uwQOoTGYxCmWItKKZjBEP9hUPPBBtO6EZl1MuwdfSidU58q8V8KvhNngiWE353JHn 92mnc/u0MdRv6eVud4HaHuM1mpMnxppTfClwoDYfiGNMqiEhRWKxeQw7sQwRPSQKnR2K nbQS96wnTf3v+tIxR/XDuwhVV+69d3gqrp0LIKmYKQrbBpnp6G+0iXDOrD5YDYpHdEll k12vAamsyibZnSIQ6T+IX0fEokSzwye24HIFff1pyPcyMlAc1w+5wSm7SEH3HAMTWado HFsw==
X-Gm-Message-State: ALKqPwfr9rHf//FsDcUY+198gjW/NRsEklEW3zsuvM8w9xiz07S+THSG 1Xypv7f70d0XcY7YPMNAeVaGA0dpJHnIePhO/jw=
X-Google-Smtp-Source: AB8JxZrFNCMeIgTCQbWwRAgVu5ABxkXxvuGt1yDYmqUNpZwpm6Vmse0Ux73/18E/I4HUXnGAd3CbInGIOdEmtKDfrUo=
X-Received: by 2002:a6b:5010:: with SMTP id e16-v6mr1819977iob.274.1525964540858;  Thu, 10 May 2018 08:02:20 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 10 May 2018 08:02:20 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <CAN1APdcZfs5UwNsyeqb=C3oodC6GzcoPM2EOY8nK1ofV+yqevA@mail.gmail.com>
References: <CY4PR21MB0630CE4DE6BA4EDF54A1FEB1B6A40@CY4PR21MB0630.namprd21.prod.outlook.com> <1F436ED13A22A246A59CA374CBC543998B60C7AD@ORSMSX111.amr.corp.intel.com> <CAN1APdc3y0EwFqeYVvZs7MtBHhS_9CzwGmcwRqi_6GHWzF3_2Q@mail.gmail.com> <1F436ED13A22A246A59CA374CBC543998B60C851@ORSMSX111.amr.corp.intel.com> <CAN1APdcPkO-HfXqqvjeee6K8U8KSZQdtx=6fW1vZo+H6pKfzzQ@mail.gmail.com> <CAKcm_gP8TRPT7yi1y=mU5Fvq7xB5-1ieyKFLQMPomfabYbkcxA@mail.gmail.com> <bf540ec1f6f045aca1cf2379380630b5@usma1ex-dag1mb5.msg.corp.akamai.com> <SN1PR08MB185446750FCDA2B58C9833C8DA890@SN1PR08MB1854.namprd08.prod.outlook.com> <CACsn0cmJcAxORo4Cd-qyGJL3ZOT5Yz0WgdMqv_AGi4DjedyzFA@mail.gmail.com> <A6F55755-D7E1-40E4-8EC3-D5FE77A2EDBE@fb.com> <CAK-1kemWAW+2Sk5aKJ+RXKUAyjFii4MRH=xK7SE0mr=tbCiRfw@mail.gmail.com> <CAN1APddgX6=CxKdUA718=95EeCUPS60vVxbGFDHa7-eRjw7BxA@mail.gmail.com> <98A67023-AE1D-48EE-BD75-7D03E05E980D@netapp.com> <CAN1APdf2VKXB-sO97S=n5rCC4t6YZL22T=xdxPba9SgRAPKwLA@mail.gmail.com> <5213b2f5-c795-9d54-72b8-01a4a6db03ee@mellanox.com> <9E549481-9B80-4DED-AC37-DC0C91AEBCDE@netapp.com> <CAN1APdcZfs5UwNsyeqb=C3oodC6GzcoPM2EOY8nK1ofV+yqevA@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Thu, 10 May 2018 08:02:20 -0700
Message-ID: <CAN1APdejvqPWi-E14PiO6Pts7BpBv9BODMBjRoSDzwRD_hiruw@mail.gmail.com>
Subject: Re: Impact of hardware offloads on network stack performance
To: Boris Pismenny <borisp@mellanox.com>, "Eggert, Lars" <lars@netapp.com>
Cc: Roberto Peon <fenix@fb.com>, Mike Bishop <mbishop@evequefou.be>, IETF QUIC WG <quic@ietf.org>,  "Lubashev, Igor" <ilubashe@akamai.com>, craigt <c@gryning.com>,  Praveen Balasubramanian <pravb@microsoft.com>, Watson Ladd <watsonbladd@gmail.com>,  Ian Swett <ianswett=40google.com@dmarc.ietf.org>,  "Deval, Manasi" <manasi.deval@intel.com>
Content-Type: multipart/alternative; boundary="00000000000065d4ef056bdb4eff"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/-5-Df5NSNbmFA8Njk-Qptsr39nU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 15:02:24 -0000

--00000000000065d4ef056bdb4eff
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Some of you probably have inside knowledge of this:

https://www.bbc.co.uk/rd/blog/2018-04-high-speed-networking-open-source-ker=
nel-bypass


On 10 May 2018 at 16.57.35, Mikkel Fahn=C3=B8e J=C3=B8rgensen (mikkelfj@gma=
il.com)
wrote:

Netmap is has a fairly low line count and complexity for what it achieves,
it is not tied to any vendor specific hardware, it patches do seem to
arrive for various cards.

I recently did a user space emulation of netmap where separate user threads
drains and fills the tx and rx rings respectively. I=E2=80=99m not sure thi=
s is
worth it in terms of performance since it adds more synchronization (netmap
makes certain assumptions because some updates are in the kernel). However,
it does provide a uniform buffering layer and it makes it easier to plug in
proper netmap when available. It does move some per message latency out of
the way.


On 10 May 2018 at 16.03.28, Eggert, Lars (lars@netapp.com) wrote:

On 2018-5-10, at 14:57, Boris Pismenny <borisp@mellanox.com> wrote:
> Also, is there a reason to prefer netmap over other userspace network
stacks like DPDK/VPP/etc?

For me personally, the netmap API is a lot more minimal and therefore
easier to integrate. DPDK really wants to take over scheduling, memory
management and all kinds of other stuff besides packet I/O. YMMV.

Lars

--00000000000065d4ef056bdb4eff
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Some of you probably=
 have inside knowledge of this:</div><div id=3D"bloop_customfont" style=3D"=
font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px=
;line-height:auto"><br></div><div id=3D"bloop_customfont" style=3D"font-fam=
ily:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-he=
ight:auto"><a href=3D"https://www.bbc.co.uk/rd/blog/2018-04-high-speed-netw=
orking-open-source-kernel-bypass">https://www.bbc.co.uk/rd/blog/2018-04-hig=
h-speed-networking-open-source-kernel-bypass</a></div><div id=3D"bloop_cust=
omfont" style=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,=
0,1.0);margin:0px;line-height:auto"><br></div> <br><p class=3D"airmail_on">=
On 10 May 2018 at 16.57.35, Mikkel Fahn=C3=B8e J=C3=B8rgensen (<a href=3D"m=
ailto:mikkelfj@gmail.com">mikkelfj@gmail.com</a>) wrote:</p> <blockquote ty=
pe=3D"cite" class=3D"clean_bq"><span><div style=3D"word-wrap:break-word;lin=
e-break:after-white-space"><div></div><div>




<title></title>



<div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size=
:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">
Netmap is has a fairly low line count and complexity for what it
achieves, it is not tied to any vendor specific hardware, it
patches do seem to arrive for various cards.</div>
<div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size=
:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">
<br></div>
<div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size=
:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">
I recently did a user space emulation of netmap where separate user
threads drains and fills the tx and rx rings respectively. I=E2=80=99m not
sure this is worth it in terms of performance since it adds more
synchronization (netmap makes certain assumptions because some
updates are in the kernel). However, it does provide a uniform
buffering layer and it makes it easier to plug in proper netmap
when available. It does move some per message latency out of the
way.</div>
<div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size=
:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">
<br></div>
<br>
<p class=3D"airmail_on">On 10 May 2018 at 16.03.28, Eggert, Lars
(<a href=3D"mailto:lars@netapp.com">lars@netapp.com</a>) wrote:</p>
<blockquote type=3D"cite" class=3D"clean_bq">
<div>
<div><span>On 2018-5-10, at 14:57, Boris Pismenny
&lt;<a href=3D"mailto:borisp@mellanox.com">borisp@mellanox.com</a>&gt; wrot=
e:<br>
&gt; Also, is there a reason to prefer netmap over other userspace
network stacks like DPDK/VPP/etc?<br>
<br>
For me personally, the netmap API is a lot more minimal and
therefore easier to integrate. DPDK really wants to take over
scheduling, memory management and all kinds of other stuff besides
packet I/O. YMMV.<br>
<br>
Lars<br></span></div>
</div>
</blockquote>


</div></div></span></blockquote></body></html>

--00000000000065d4ef056bdb4eff--


From nobody Thu May 10 08:12:35 2018
Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A873612741D for <quic@ietfa.amsl.com>; Thu, 10 May 2018 08:12:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 k_6EKa0gNQAT for <quic@ietfa.amsl.com>; Thu, 10 May 2018 08:12:32 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 027F8126CB6 for <quic@ietf.org>; Thu, 10 May 2018 08:12:32 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id e12-v6so3388989iob.8 for <quic@ietf.org>; Thu, 10 May 2018 08:12:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to;  bh=Rj1k5fMdWuO4a8WPikkcfrX3ZsFXWZBTney5VyFuR8s=; b=Hb9ylRp/TVrPxgS6xiCT7GszbCW2nhV0H70d7CQN2gtSnZsCGCX2M4Y7eM7hEsuHdg I7+iXNEphGJTve98X1OT3HBw83HvZgdiPoQiGvAoz4X0OaETRm2P/jf5xU9mUQGC4rMH eFFK/pHmj1JmqHbRqDs7CnLcTI+9R9O4XbcTMg4tczvq2b8kOGi6i9VSmPjpZ6EbnHjC DppBWKzwbzI+jxtlMb19qxjJFMY6SwY/p8WPfDgJYCphM5r6oyKJOwcf5RRSKQo4Jn64 9hqgFEjdbaZyFi/OTx851SOXlqVC1qAu94XGcb51xuWbdfkBFEkXyq0qTZ9OSOW6oqXv U8Jg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to; bh=Rj1k5fMdWuO4a8WPikkcfrX3ZsFXWZBTney5VyFuR8s=; b=crhFuuf9QIoxPVcWl6dirEsvDnSaq2d+Ji5tfnCHg6z3GW3DxL2I+qQ08b1o5VAWki hvzpJ2XvShZeJlCh8NAqyn4UWahSDW3JUWmG7XM98HpvEL7EDWENoecQyjhCknQFsPo1 rtxuVWtM8h8wTC3e9P7ETIWmwcs8ibXY9vPLv/LYlx3UJ0q9NiT5ffMZWomh51pPsDZZ wkt+JQLCUnyBEPDTMM3H12zV9IoJDDTcNbPz/aPcKmvxz5hiaQgdDWGVy6fJy3RDn1DF KjJvjnL89k0qhwrhrdFq6IMqZJjAxpdmQ1OX3kb5an2eHumKwYfppQiRQ/cK3e4PuZz6 6fxg==
X-Gm-Message-State: ALKqPwfUxY5uc4F0yX0n7HRfUUTAlNv0j5ktvlTT8c2V8iPZsX9N76SZ CjGDM/c+AY/XObF6jw2f4pn0quKhBbWEYBl63aM=
X-Google-Smtp-Source: AB8JxZoFHM9+iOERf/c4MHgTS9MLqGShbPkXWBIbaXZv4Iu+IQcVe+SRGz9dDO2ypGTF+d6vtr+u4yEaZV9OQ1gIOTE=
X-Received: by 2002:a6b:b60a:: with SMTP id g10-v6mr1835270iof.209.1525965151447;  Thu, 10 May 2018 08:12:31 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 10 May 2018 08:12:30 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <CAN1APdfFBRzrf5d2L2i5gtT3_aGUcu0Oi3NVX_UdempAzyq9Tw@mail.gmail.com>
References: <1F436ED13A22A246A59CA374CBC543998B64E65D@ORSMSX111.amr.corp.intel.com> <CAN1APdcfmAsM-CBGzFEicBWf6Ck2uRhOmoiooo7d3EPDTjwt7g@mail.gmail.com> <DM5PR2101MB0901149C9E14440DF9CEE269B3980@DM5PR2101MB0901.namprd21.prod.outlook.com> <CAN1APdfFBRzrf5d2L2i5gtT3_aGUcu0Oi3NVX_UdempAzyq9Tw@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Thu, 10 May 2018 08:12:30 -0700
Message-ID: <CAN1APddSV6R2L2Fp-d4V1T0jZ1JqDfmHcTpgsYtUm3hyjEU44Q@mail.gmail.com>
Subject: RE: Cost of parsing ACK frames in QUIC
To: Nick Banks <nibanks@microsoft.com>, "Deval, Manasi" <manasi.deval@intel.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cab119056bdb72c1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/5G70IKexv6byiMNtQT-MpYuQy2o>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 15:12:33 -0000

--000000000000cab119056bdb72c1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

At least for ACK outside handshake,
but you cannot feed unreliable data into your application, so generally you
need a full packet validation.


On 10 May 2018 at 16.52.10, Mikkel Fahn=C3=B8e J=C3=B8rgensen (mikkelfj@gma=
il.com)
wrote:

Yes, that would often be the case.


On 10 May 2018 at 16.49.59, Nick Banks (nibanks@microsoft.com) wrote:

I=E2=80=99m don=E2=80=99t agree that you need to make two passes on a packe=
t when
processing ACK frames. If you have successfully decrypted the packet and
you got to the point of processing ACK frames, then any other error that
would later encounter while processing the packet would likely be
considered a protocol violation, would it not? If so, then you would
terminate the entire connection.



That being said, on the topic of being a bit more expensive to process ACK
frames in general, QUIC has made a decision to generally prefer smaller
wire encoding over CPU costs, where appropriate. If you have a suggestion
to change the encoding that doesn=E2=80=99t increase the wire format cost, =
we could
take a look at it.



- Nick



*From:* QUIC <quic-bounces@ietf.org> *On Behalf Of * Mikkel Fahn=C3=B8e J=
=C3=B8rgensen
*Sent:* Thursday, May 10, 2018 7:44 AM
*To:* Deval, Manasi <manasi.deval@intel.com>; IETF QUIC WG <quic@ietf.org>
*Subject:* Re: Cost of parsing ACK frames in QUIC



While this may be true, please note that QUIC also requires that the entire
packet is valid before it does anything that modifies the state of the
receiver.



This means that you generally have to do two passes of the packet to ensure
that the packet is valid. In the first pass you can then store data for the
optimistic case of a single ACK frame.



That said, arguments about fast(er) processing still apply, but it is no
longer limited to only ACK frames.





On 10 May 2018 at 16.25.50, Deval, Manasi (manasi.deval@intel.com) wrote:

Hi All,



The QUIC header definitions tend to use as few bits as possible by
implementing the policy to use variable size fields. The result of this
policy would be that each receiver needs to do a two part lookup to
identify the field and this needs to be implemented serially in order to
parse the whole frame time.



For example, in a case where no packets were dropped, a sender may receive
an ACK for a single block. If a code path were trying to determine the size
of an ACK, they would have to read 8 fields to determine the size of ACK.



A client only sees a few ACKs. Majority of the ACKs are seen on the server
side. It would be good to simplify this scheme so ACK processing can be
accelerated with SIMD instructions would be good.



Thanks,

Manasi

--000000000000cab119056bdb72c1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">At least for ACK out=
side handshake,</div><div id=3D"bloop_customfont" style=3D"font-family:Helv=
etica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:aut=
o">but you cannot feed unreliable data into your application, so generally =
you need a full packet validation.</div> <div id=3D"bloop_sign_152596507789=
2535040" class=3D"bloop_sign"><div style=3D"font-family:helvetica,arial;fon=
t-size:13px"><br></div></div> <br><p class=3D"airmail_on">On 10 May 2018 at=
 16.52.10, Mikkel Fahn=C3=B8e J=C3=B8rgensen (<a href=3D"mailto:mikkelfj@gm=
ail.com">mikkelfj@gmail.com</a>) wrote:</p> <blockquote type=3D"cite" class=
=3D"clean_bq"><span><div style=3D"word-wrap:break-word;line-break:after-whi=
te-space"><div></div><div><div id=3D"bloop_customfont" style=3D"font-family=
:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-heigh=
t:auto">Yes, that would often be the case.</div> <div id=3D"bloop_sign_1525=
963882581045248" class=3D"bloop_sign"><div style=3D"font-family:helvetica,a=
rial;font-size:13px"><br></div></div> <br><p class=3D"airmail_on">On 10 May=
 2018 at 16.49.59, Nick Banks (<a href=3D"mailto:nibanks@microsoft.com">nib=
anks@microsoft.com</a>) wrote:</p> <blockquote type=3D"cite" class=3D"clean=
_bq"><span><div lang=3D"EN-US" link=3D"blue" vlink=3D"purple"><div></div><d=
iv>






<div class=3D"WordSection1">
<p class=3D"MsoNormal">I=E2=80=99m don=E2=80=99t agree that you need to mak=
e two passes on a packet when processing ACK frames. If you have successful=
ly decrypted the packet and you got to the point of processing ACK frames, =
then any other error that would later encounter while
 processing the packet would likely be considered a protocol violation, wou=
ld it not? If so, then you would terminate the entire connection.</p>
<p class=3D"MsoNormal">=C2=A0</p>
<p class=3D"MsoNormal">That being said, on the topic of being a bit more ex=
pensive to process ACK frames in general, QUIC has made a decision to gener=
ally prefer smaller wire encoding over CPU costs, where appropriate. If you=
 have a suggestion to change the encoding
 that doesn=E2=80=99t increase the wire format cost, we could take a look a=
t it.</p>
<p class=3D"MsoNormal">=C2=A0</p>
<p class=3D"MsoNormal">- Nick</p>
<p class=3D"MsoNormal">=C2=A0</p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> QUIC &lt;<a href=3D"mailto:quic-bounces=
@ietf.org">quic-bounces@ietf.org</a>&gt; <b>On Behalf Of </b>
Mikkel Fahn=C3=B8e J=C3=B8rgensen<br>
<b>Sent:</b> Thursday, May 10, 2018 7:44 AM<br>
<b>To:</b> Deval, Manasi &lt;<a href=3D"mailto:manasi.deval@intel.com">mana=
si.deval@intel.com</a>&gt;; IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.or=
g">quic@ietf.org</a>&gt;<br>
<b>Subject:</b> Re: Cost of parsing ACK frames in QUIC</p>
</div>
</div>
<p class=3D"MsoNormal">=C2=A0</p>
<div id=3D"bloop_customfont">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;He=
lvetica&quot;,sans-serif">While this may be true, please note that QUIC als=
o requires that the entire packet is valid before it does anything that mod=
ifies the state of the receiver.</span></p>
</div>
<div id=3D"bloop_customfont">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;He=
lvetica&quot;,sans-serif">=C2=A0</span></p>
</div>
<div id=3D"bloop_customfont">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;He=
lvetica&quot;,sans-serif">This means that you generally have to do two pass=
es of the packet to ensure that the packet is valid. In the first pass you =
can then store data for the optimistic case of
 a single ACK frame.</span></p>
</div>
<div id=3D"bloop_customfont">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;He=
lvetica&quot;,sans-serif">=C2=A0</span></p>
</div>
<div id=3D"bloop_customfont">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;He=
lvetica&quot;,sans-serif">That said, arguments about fast(er) processing st=
ill apply, but it is no longer limited to only ACK frames.</span></p>
</div>
<div id=3D"bloop_customfont">
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;He=
lvetica&quot;,sans-serif">=C2=A0</span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-size:10.0pt;font-family:&quot;He=
lvetica&quot;,sans-serif">=C2=A0</span></p>
<p class=3D"airmailon"><span style=3D"font-size:10.0pt;font-family:&quot;He=
lvetica&quot;,sans-serif">On 10 May 2018 at 16.25.50, Deval, Manasi (<a hre=
f=3D"mailto:manasi.deval@intel.com">manasi.deval@intel.com</a>) wrote:</spa=
n></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">Hi All,</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">=C2=A0</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">The QUIC header definitions tend to use as few bits as possible=
 by implementing the policy to use variable size
 fields. The result of this policy would be that each receiver needs to do =
a two part lookup to identify the field and this needs to be implemented se=
rially in order to parse the whole frame time.
</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">=C2=A0</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">For example, in a case where no packets were dropped, a sender =
may receive an ACK for a single block. If a code
 path were trying to determine the size of an ACK, they would have to read =
8 fields to determine the size of ACK.
</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">=C2=A0</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">A client only sees a few ACKs. Majority of the ACKs are seen on=
 the server side. It would be good to simplify this
 scheme so ACK processing can be accelerated with SIMD instructions would b=
e good.
</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">=C2=A0</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">Thanks,</span></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto"><span style=3D"font-size:10.0pt;font-family:&quot;Helvetica&quot;,=
sans-serif">Manasi</span></p>
</div>
</div>
</div>
</blockquote>
</div>


</div></div></span></blockquote></div></div></span></blockquote></body></ht=
ml>

--000000000000cab119056bdb72c1--


From nobody Thu May 10 08:39:43 2018
Return-Path: <c@gryning.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B8E9D12EB21 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 08:39:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.609
X-Spam-Level: 
X-Spam-Status: No, score=-2.609 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gryning-com.20150623.gappssmtp.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 gcrpjfJNvtzT for <quic@ietfa.amsl.com>; Thu, 10 May 2018 08:39:39 -0700 (PDT)
Received: from mail-lf0-x22e.google.com (mail-lf0-x22e.google.com [IPv6:2a00:1450:4010:c07::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2753412762F for <quic@ietf.org>; Thu, 10 May 2018 08:39:39 -0700 (PDT)
Received: by mail-lf0-x22e.google.com with SMTP id r2-v6so3617746lff.4 for <quic@ietf.org>; Thu, 10 May 2018 08:39:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gryning-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=CQQhPpg+I4Ab2OCkvCarRUrxK62N8dsZRy432STQPcY=; b=TQlvOcJ+vB6Pk/jt95e66a+uOhqstFyWXueYC4DXFqCfpm7gjACg4GlLZSYOPH+ZY0 bqPOo4OVomgLXlBQSjDN6R/V5t/4/yFxYFnxCpwH1UCYmw6+7bmPBPex6expqbQfC4wz qaMZeuxJ0F6Svb5ouYfGtOeKvxD+SO3sSr/+Xav3BFjai30eStz7xxJ6BDUcUwo4pXT+ noEF6tmirzPl4CTh63uMJxbgqm8CsN0Pm3hESi94DfcMs96KnLKPZ/9VaRFtsVUzQmSK TFQFmrc14m7fXsIzNeI3AWNDcS/1RLovgkAkmYSahXwLbsV9xBXOsStyebayIoVhWiqQ Y69w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=CQQhPpg+I4Ab2OCkvCarRUrxK62N8dsZRy432STQPcY=; b=Q6sJI+gWW98LwPOGTo4BGkFGWNp7jeAwxQ/4zq/xoGxinL2GkT/VJSYa7E5liKFU6I EwqlM8aQy6vcoj/IMUVrhYweiaBPUsTeOz+/i03I9+pLizsMQywM35WVutED0Kfju+dG 1SH62y7+85iyOB2m5hiX/svDk8tEh0VicVTaberOyltsbSoG4L/6VGdZIlD7RUf79NZ5 ieE4yk9sqsp79bCuiUEp0GJzmPZR2eN5uPkiVNcYthSEtN1mQJZmdCsQ/GEYIYqp90Tg KtMVQUbIolKqazFPoKWzuDA9vnIVgjqVLfE/PyvmeCqmJZmxUUhHFQx0eceBuWs2Qfa2 8Ztw==
X-Gm-Message-State: ALKqPwcNTPPL3UKmkO+n/gU6WDF/IecVhtzzfnrJr7j34lNwx94Jd94Y vujG89UJ/ZJ1z463XhaJ1Z/+Lk5LNrM14yemK75fFg==
X-Google-Smtp-Source: AB8JxZro5GiboK1A9xIp77kQSllNzuoYfzri6Ti05v2LqVK7agXswInCPJfuARlFADR4ZOtGH9Xg5Oul3tGPjx0JHRs=
X-Received: by 2002:a2e:89d7:: with SMTP id c23-v6mr1536985ljk.22.1525966777321;  Thu, 10 May 2018 08:39:37 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a19:d012:0:0:0:0:0 with HTTP; Thu, 10 May 2018 08:39:36 -0700 (PDT)
X-Originating-IP: [2001:41c1:4:8000:e554:161e:d4c5:8156]
In-Reply-To: <CAN1APdejvqPWi-E14PiO6Pts7BpBv9BODMBjRoSDzwRD_hiruw@mail.gmail.com>
References: <CY4PR21MB0630CE4DE6BA4EDF54A1FEB1B6A40@CY4PR21MB0630.namprd21.prod.outlook.com> <1F436ED13A22A246A59CA374CBC543998B60C7AD@ORSMSX111.amr.corp.intel.com> <CAN1APdc3y0EwFqeYVvZs7MtBHhS_9CzwGmcwRqi_6GHWzF3_2Q@mail.gmail.com> <1F436ED13A22A246A59CA374CBC543998B60C851@ORSMSX111.amr.corp.intel.com> <CAN1APdcPkO-HfXqqvjeee6K8U8KSZQdtx=6fW1vZo+H6pKfzzQ@mail.gmail.com> <CAKcm_gP8TRPT7yi1y=mU5Fvq7xB5-1ieyKFLQMPomfabYbkcxA@mail.gmail.com> <bf540ec1f6f045aca1cf2379380630b5@usma1ex-dag1mb5.msg.corp.akamai.com> <SN1PR08MB185446750FCDA2B58C9833C8DA890@SN1PR08MB1854.namprd08.prod.outlook.com> <CACsn0cmJcAxORo4Cd-qyGJL3ZOT5Yz0WgdMqv_AGi4DjedyzFA@mail.gmail.com> <A6F55755-D7E1-40E4-8EC3-D5FE77A2EDBE@fb.com> <CAK-1kemWAW+2Sk5aKJ+RXKUAyjFii4MRH=xK7SE0mr=tbCiRfw@mail.gmail.com> <CAN1APddgX6=CxKdUA718=95EeCUPS60vVxbGFDHa7-eRjw7BxA@mail.gmail.com> <98A67023-AE1D-48EE-BD75-7D03E05E980D@netapp.com> <CAN1APdf2VKXB-sO97S=n5rCC4t6YZL22T=xdxPba9SgRAPKwLA@mail.gmail.com> <5213b2f5-c795-9d54-72b8-01a4a6db03ee@mellanox.com> <9E549481-9B80-4DED-AC37-DC0C91AEBCDE@netapp.com> <CAN1APdcZfs5UwNsyeqb=C3oodC6GzcoPM2EOY8nK1ofV+yqevA@mail.gmail.com> <CAN1APdejvqPWi-E14PiO6Pts7BpBv9BODMBjRoSDzwRD_hiruw@mail.gmail.com>
From: craigt <c@gryning.com>
Date: Thu, 10 May 2018 16:39:36 +0100
Message-ID: <CAK-1kemP1GTVaa-n03OS+BiCDqMEqMYctyPQ+F+Y2S7q1k8Ovg@mail.gmail.com>
Subject: Re: Impact of hardware offloads on network stack performance
To: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
Cc: Boris Pismenny <borisp@mellanox.com>, "Eggert, Lars" <lars@netapp.com>, Roberto Peon <fenix@fb.com>,  Mike Bishop <mbishop@evequefou.be>, IETF QUIC WG <quic@ietf.org>,  "Lubashev, Igor" <ilubashe@akamai.com>, Praveen Balasubramanian <pravb@microsoft.com>,  Watson Ladd <watsonbladd@gmail.com>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>,  "Deval, Manasi" <manasi.deval@intel.com>
Content-Type: multipart/alternative; boundary="000000000000b3a07b056bdbd378"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/0VY0Qj0HwGz8Ygq_mZlpaEdPuUs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 15:39:42 -0000

--000000000000b3a07b056bdbd378
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

The BBC folk involved in that work aren't on this list. If there are
questions about the implementation you would like answered, get in touch
with me and I'll try to get some time.

c

On 10 May 2018 at 16:02, Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@gmail.=
com> wrote:

> Some of you probably have inside knowledge of this:
>
> https://www.bbc.co.uk/rd/blog/2018-04-high-speed-networking-
> open-source-kernel-bypass
>
>
> On 10 May 2018 at 16.57.35, Mikkel Fahn=C3=B8e J=C3=B8rgensen (mikkelfj@g=
mail.com)
> wrote:
>
> Netmap is has a fairly low line count and complexity for what it achieves=
,
> it is not tied to any vendor specific hardware, it patches do seem to
> arrive for various cards.
>
> I recently did a user space emulation of netmap where separate user
> threads drains and fills the tx and rx rings respectively. I=E2=80=99m no=
t sure
> this is worth it in terms of performance since it adds more synchronizati=
on
> (netmap makes certain assumptions because some updates are in the kernel)=
.
> However, it does provide a uniform buffering layer and it makes it easier
> to plug in proper netmap when available. It does move some per message
> latency out of the way.
>
>
> On 10 May 2018 at 16.03.28, Eggert, Lars (lars@netapp.com) wrote:
>
> On 2018-5-10, at 14:57, Boris Pismenny <borisp@mellanox.com> wrote:
> > Also, is there a reason to prefer netmap over other userspace network
> stacks like DPDK/VPP/etc?
>
> For me personally, the netmap API is a lot more minimal and therefore
> easier to integrate. DPDK really wants to take over scheduling, memory
> management and all kinds of other stuff besides packet I/O. YMMV.
>
> Lars
>
>

--000000000000b3a07b056bdbd378
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">The BBC folk involved in that work aren&#39;t on this list=
. If there are questions about the implementation you would like answered, =
get in touch with me and I&#39;ll try to get some time.<div><br></div><div>=
c</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On 1=
0 May 2018 at 16:02, Mikkel Fahn=C3=B8e J=C3=B8rgensen <span dir=3D"ltr">&l=
t;<a href=3D"mailto:mikkelfj@gmail.com" target=3D"_blank">mikkelfj@gmail.co=
m</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style=3D"wor=
d-wrap:break-word;line-break:after-white-space"><div id=3D"m_11334396015086=
79751bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;=
color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Some of you probably hav=
e inside knowledge of this:</div><div id=3D"m_1133439601508679751bloop_cust=
omfont" style=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,=
0,1.0);margin:0px;line-height:auto"><br></div><div id=3D"m_1133439601508679=
751bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;co=
lor:rgba(0,0,0,1.0);margin:0px;line-height:auto"><a href=3D"https://www.bbc=
.co.uk/rd/blog/2018-04-high-speed-networking-open-source-kernel-bypass" tar=
get=3D"_blank">https://www.bbc.co.uk/rd/blog/<wbr>2018-04-high-speed-networ=
king-<wbr>open-source-kernel-bypass</a></div><div><div class=3D"h5"><div id=
=3D"m_1133439601508679751bloop_customfont" style=3D"font-family:Helvetica,A=
rial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br>=
</div> <br><p class=3D"m_1133439601508679751airmail_on">On 10 May 2018 at 1=
6.57.35, Mikkel Fahn=C3=B8e J=C3=B8rgensen (<a href=3D"mailto:mikkelfj@gmai=
l.com" target=3D"_blank">mikkelfj@gmail.com</a>) wrote:</p> <blockquote typ=
e=3D"cite" class=3D"m_1133439601508679751clean_bq"><span><div style=3D"word=
-wrap:break-word;line-break:after-white-space"><div></div><div>








<div id=3D"m_1133439601508679751bloop_customfont" style=3D"font-family:Helv=
etica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:aut=
o">
Netmap is has a fairly low line count and complexity for what it
achieves, it is not tied to any vendor specific hardware, it
patches do seem to arrive for various cards.</div>
<div id=3D"m_1133439601508679751bloop_customfont" style=3D"font-family:Helv=
etica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:aut=
o">
<br></div>
<div id=3D"m_1133439601508679751bloop_customfont" style=3D"font-family:Helv=
etica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:aut=
o">
I recently did a user space emulation of netmap where separate user
threads drains and fills the tx and rx rings respectively. I=E2=80=99m not
sure this is worth it in terms of performance since it adds more
synchronization (netmap makes certain assumptions because some
updates are in the kernel). However, it does provide a uniform
buffering layer and it makes it easier to plug in proper netmap
when available. It does move some per message latency out of the
way.</div>
<div id=3D"m_1133439601508679751bloop_customfont" style=3D"font-family:Helv=
etica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:aut=
o">
<br></div>
<br>
<p class=3D"m_1133439601508679751airmail_on">On 10 May 2018 at 16.03.28, Eg=
gert, Lars
(<a href=3D"mailto:lars@netapp.com" target=3D"_blank">lars@netapp.com</a>) =
wrote:</p>
<blockquote type=3D"cite" class=3D"m_1133439601508679751clean_bq">
<div>
<div><span>On 2018-5-10, at 14:57, Boris Pismenny
&lt;<a href=3D"mailto:borisp@mellanox.com" target=3D"_blank">borisp@mellano=
x.com</a>&gt; wrote:<br>
&gt; Also, is there a reason to prefer netmap over other userspace
network stacks like DPDK/VPP/etc?<br>
<br>
For me personally, the netmap API is a lot more minimal and
therefore easier to integrate. DPDK really wants to take over
scheduling, memory management and all kinds of other stuff besides
packet I/O. YMMV.<br>
<br>
Lars<br></span></div>
</div>
</blockquote>


</div></div></span></blockquote></div></div></div>
</blockquote></div><br></div>

--000000000000b3a07b056bdbd378--


From nobody Thu May 10 11:05:44 2018
Return-Path: <dtikhonov@litespeedtech.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5ED1412EB63 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 11:05:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 UkhgTtTOKmNf for <quic@ietfa.amsl.com>; Thu, 10 May 2018 11:05:37 -0700 (PDT)
Received: from mail-qt0-x22b.google.com (mail-qt0-x22b.google.com [IPv6:2607:f8b0:400d:c0d::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8097012EC1A for <quic@ietf.org>; Thu, 10 May 2018 11:05:31 -0700 (PDT)
Received: by mail-qt0-x22b.google.com with SMTP id e8-v6so3742193qth.0 for <quic@ietf.org>; Thu, 10 May 2018 11:05:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mail-followup-to:mime-version :content-disposition:user-agent; bh=3Qb0Nq09tfvmiFNAAeOoFvc/6JGboNyfERIf028Z4Nc=; b=1qoEXycneQMdCHwXSNnlPNE/awhQNTjon6PvWEViQz8Lj4K343e9aWYpYIwztAYiCn XgQMWHHxaLiqQNvnbOs3p9xd7eebYfO3gE2+j/tHlkNSU9hxzZ29So9Xy9LLw75DhQeu qhhn4Mfs9Ub6mvb5VVUot0kw44s+pQmdkG62hfnBpY8LsXCQnYbKpbkPf/Ug7BvoxLVN XF1075gJakQjPUASKgxwtUdpYHh9G1v92avt5MIdrOec6yzwzGHn5QdCbQZaot/8ezrd /bnUSZlZO5dYuiwHkz+gWjTgnFuf+wOINuFkw01N0DkZzBC0ok9yrZZuIifwr52eq8SU ea8w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :mime-version:content-disposition:user-agent; bh=3Qb0Nq09tfvmiFNAAeOoFvc/6JGboNyfERIf028Z4Nc=; b=GdO4kRSm4hGiqW694sJZyUkK7syWjNA4F3+rmOXwfUhpKChRO3PmMwWxSYmVI2VquW 3DbYmktSH3yTqMlzRrh2jdKLxoFiu4742flf8oVkjaSTJbETRwvKXOgY31O9Y3HLqKRG +q4pJREDvOAKRMih2uUw7udBvubiS5gpGWsWJwkBoymJIG9bNY3m8GTDq+Z/EiuRS0hV Hs52spwFwSE3RrjCZ/WXNQ/Mclg1M3/uihEf3N5EbEpC18g3Hsj6NvHKjXyIPVgqnbHl POSRlSCC8/0PkXoH4cosSyd27HFbEZ3C8CXlByE7UhohTNg9c7hfaRpgAz8d3ip6ymNs EJQw==
X-Gm-Message-State: ALKqPwdDpy49wIwV1qTwTHrZWJhWfTVvSyN3mxuGev83/KLB/KXIO1K7 RZK8J3OArYiTx19KtLPO/9g32HsN
X-Google-Smtp-Source: AB8JxZqAXuwYKC0ydB6sFy9wGEl0TMYFqYutCeoMGFNG99S6DYjsxZvlt/1oz3Yn8DEJJGEy9rSBSA==
X-Received: by 2002:ac8:235c:: with SMTP id b28-v6mr2365585qtb.212.1525975530499;  Thu, 10 May 2018 11:05:30 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id k10-v6sm1050442qkh.95.2018.05.10.11.05.29 for <quic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 May 2018 11:05:29 -0700 (PDT)
Date: Thu, 10 May 2018 14:05:25 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: IETF QUIC WG <quic@ietf.org>
Subject: Why allow empty STREAM frames when offset is zero?
Message-ID: <20180510180509.GA2505@ubuntu-dmitri>
Mail-Followup-To: IETF QUIC WG <quic@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/z55Nf2K9EXtTrrj-8ayf9-Yq9xI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 18:05:41 -0000

[draft-ietf-quic-transport-11] says the following:

   A stream frame's Stream Data MUST NOT be empty, unless the offset is
   0 or the FIN bit is set.

Why allow empty STREAM frames when the offset is zero?  What is the
purpose?

  - Dmitri.


From nobody Thu May 10 11:26:03 2018
Return-Path: <mbishop@evequefou.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C4D6E12D94B for <quic@ietfa.amsl.com>; Thu, 10 May 2018 11:26:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 iM3Apw11rrwi for <quic@ietfa.amsl.com>; Thu, 10 May 2018 11:26:00 -0700 (PDT)
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (mail-sn1nam01on0125.outbound.protection.outlook.com [104.47.32.125]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 08A4012D88D for <quic@ietf.org>; Thu, 10 May 2018 11:25:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=eZ/bmSTiEQ0v3CUagFZ2vQ2XWtHBwiNTQXiN9WXYdUo=; b=VnQKVVBJbzwTgZpbm+FT8zwBLPNbxFc5p8JLYkGfrYzoQYdJj1c33ttOKkEevZTEMucosShAX0TseqBEH8aXUhSKiQfC3st/qSbwES+teUD/uyWiOx7PVInxvC31soZsSRfBXQsG+DKL+1ASOhQP7Dku+xUaeo9fCDSRggHgYFA=
Received: from SN1PR08MB1854.namprd08.prod.outlook.com (10.169.39.8) by SN1PR08MB1712.namprd08.prod.outlook.com (10.162.133.150) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.755.16; Thu, 10 May 2018 18:25:56 +0000
Received: from SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d]) by SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d%13]) with mapi id 15.20.0735.021; Thu, 10 May 2018 18:25:56 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Dmitri Tikhonov <dtikhonov@litespeedtech.com>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Why allow empty STREAM frames when offset is zero?
Thread-Topic: Why allow empty STREAM frames when offset is zero?
Thread-Index: AQHT6ImL5mFkHkbJHUyy0/Pe1hIypaQpR13A
Date: Thu, 10 May 2018 18:25:55 +0000
Message-ID: <SN1PR08MB18543D4C234CC672616E37BFDA980@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <20180510180509.GA2505@ubuntu-dmitri>
In-Reply-To: <20180510180509.GA2505@ubuntu-dmitri>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [2001:4878:8103:102:100::308]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN1PR08MB1712; 7:WY2kU+wgbrCMGY7auhN2yXOwmJb1y+5HiWpeqZtSQGNvg9abrmGvXoRE7GF9LuBJfEs25IJz54f3j3VFYg3Tmk5gGyVr1kM5IjSf10Or6nrnh3TEfxcNfyEOACfVRT9D+CKiJ1yzFBCsBldMwxYhKNigHyfX2oRUAu0Z4mJ6V16271UF55/FYgrqdfaf8Z4VqJV6uVQewr2aswUR/Sv3DgU86xw0qFHRvQoEvU+0KMtDi7YVr6MukL+lZpcdoOJS
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(5600026)(2017052603328)(7153060)(7193020); SRVR:SN1PR08MB1712; 
x-ms-traffictypediagnostic: SN1PR08MB1712:
x-microsoft-antispam-prvs: <SN1PR08MB171295FC949CEBFE02B0FB86DA980@SN1PR08MB1712.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3231254)(944501410)(52105095)(93006095)(93001095)(10201501046)(3002001)(149027)(150027)(6041310)(2016111802025)(20161123562045)(20161123558120)(20161123564045)(20161123560045)(6043046)(6072148)(201708071742011); SRVR:SN1PR08MB1712; BCL:0; PCL:0; RULEID:; SRVR:SN1PR08MB1712; 
x-forefront-prvs: 066898046A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(366004)(39830400003)(396003)(346002)(39380400002)(199004)(189003)(13464003)(74482002)(7696005)(97736004)(86362001)(14454004)(6116002)(6436002)(5250100002)(7736002)(106356001)(3660700001)(105586002)(76176011)(478600001)(2906002)(3280700002)(229853002)(110136005)(305945005)(6246003)(33656002)(5660300001)(316002)(99286004)(25786009)(8676002)(81156014)(81166006)(186003)(446003)(102836004)(9686003)(476003)(2900100001)(8936002)(46003)(74316002)(55016002)(68736007)(53546011)(486006)(53936002)(6506007)(11346002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR08MB1712; H:SN1PR08MB1854.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: i3r7X37VKNX+MouAz3PK3jbvR453Y6mbwRn5/fZA9Gq0sU+oYeSUPlSbkeyeOM6NhlZMFz26kqDazjqZGxQCZQ6sAyXiN6cTiK6r7qfkgfP+7zWgMW6MW6ZaSw6Rd86Nt/lMDlIzCfNyGmJds2ES6oH8vPJ3yiOAHuceFSHHkY2BCJ5KZX0bd6zlsVm4VZJ9
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 7f504ffb-dff4-4696-c67e-08d5b6a378b6
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 7f504ffb-dff4-4696-c67e-08d5b6a378b6
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 May 2018 18:25:55.2086 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR08MB1712
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/KUY3Yt_S1xymtQzu6NQpBbc9C04>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 18:26:02 -0000

If you want to open a stream (e.g. permit data to be sent in the opposite d=
irection of a bidirectional stream), but don't actually have data ready to =
send yet.

-----Original Message-----
From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of Dmitri Tikhonov
Sent: Thursday, May 10, 2018 11:05 AM
To: IETF QUIC WG <quic@ietf.org>
Subject: Why allow empty STREAM frames when offset is zero?

[draft-ietf-quic-transport-11] says the following:

   A stream frame's Stream Data MUST NOT be empty, unless the offset is
   0 or the FIN bit is set.

Why allow empty STREAM frames when the offset is zero?  What is the purpose=
?

  - Dmitri.


From nobody Thu May 10 11:28:23 2018
Return-Path: <mbishop@evequefou.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0F11312D963 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 11:28:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 obnAs800V0qL for <quic@ietfa.amsl.com>; Thu, 10 May 2018 11:28:19 -0700 (PDT)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on0721.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe49::721]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 32D9212D88D for <quic@ietf.org>; Thu, 10 May 2018 11:28:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=Y7eMJ8bgQEjB5OGj4NRsx2Qz5juCjRYjLKYqcgEpJDI=; b=C7dhq9BslNvVgd3aIg/oMeUFuY4rSv4u9fbrDSRsT/YAEugpKLmi6R2z4zYAYUT8WnVQaFDtfoi96RSryYtRK9TDIu9iRzJW/AK9yNhbDFyn8DXc3rzsVfgviYX57Yg/uDfHkficA6KfQU7oTZGFg1hxf1hPkcFGbaWZ++h4fu4=
Received: from SN1PR08MB1854.namprd08.prod.outlook.com (10.169.39.8) by SN1PR08MB1983.namprd08.prod.outlook.com (10.169.39.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.735.17; Thu, 10 May 2018 18:28:15 +0000
Received: from SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d]) by SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d%13]) with mapi id 15.20.0735.021; Thu, 10 May 2018 18:28:15 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Lucas Pardue <Lucas.Pardue@bbc.co.uk>, Sam Hurst-RD <samuelh@rd.bbc.co.uk>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Clarification of transport and HTTP version compatibility
Thread-Topic: Clarification of transport and HTTP version compatibility
Thread-Index: AQHT56+xI3vQwOQ++kOo1AZLBRUIXaQno4FAgAANUQCAADE84IAAC+8AgAALO3CAABEmAIABPx9A
Date: Thu, 10 May 2018 18:28:15 +0000
Message-ID: <SN1PR08MB18540A5DF3C55D60BB357F46DA980@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <906fdff3-8009-238b-998b-4ea515a2684d@rd.bbc.co.uk>, <SN1PR08MB1854826DACF0454471CB162DDA990@SN1PR08MB1854.namprd08.prod.outlook.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB2B67C@bgb01xud1012>, <SN1PR08MB1854FC73444239C609552459DA990@SN1PR08MB1854.namprd08.prod.outlook.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB2B6A9@bgb01xud1012>, <SN1PR08MB1854232CFA318E21E062BBE3DA990@SN1PR08MB1854.namprd08.prod.outlook.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB2B6BE@bgb01xud1012>
In-Reply-To: <7CF7F94CB496BF4FAB1676F375F9666A3BB2B6BE@bgb01xud1012>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [2001:4878:8103:102:100::308]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN1PR08MB1983; 7:s0OkbVJvUt8k8g5PTIPf5WAskiGdwy8vUk13sdVTTXCKozoZeypAU8VA8qmFH8gy3Dr4Up/7Jf/8rqDWPVuuuRXvGPL1VCqJ6AuOnDQmOCfVCjV/PZa6JCCEIzkMPwmtfM2A88YUTMKu9nom1LJQFTk8PBeXqrKOR8gogRx4mjw5qkSvvjSPuXHHPiYgGXRIQWr+PwDy1ByGjDoRWgs8O1DF4aZ0eVJ6DqEN96Iq7Bu4E1/bag+KWFNzu0DNk2Kp
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(5600026)(2017052603328)(7153060)(7193020); SRVR:SN1PR08MB1983; 
x-ms-traffictypediagnostic: SN1PR08MB1983:
x-microsoft-antispam-prvs: <SN1PR08MB1983A5615B52CC1C5C640E7EDA980@SN1PR08MB1983.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(204407124797145)(127952516941037); 
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3002001)(10201501046)(93006095)(93001095)(3231254)(944501410)(52105095)(149027)(150027)(6041310)(2016111802025)(20161123558120)(20161123564045)(20161123562045)(20161123560045)(6072148)(6043046)(201708071742011); SRVR:SN1PR08MB1983; BCL:0; PCL:0; RULEID:; SRVR:SN1PR08MB1983; 
x-forefront-prvs: 066898046A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(39830400003)(366004)(39380400002)(346002)(376002)(53754006)(13464003)(189003)(199004)(25786009)(305945005)(3280700002)(55016002)(186003)(33656002)(8676002)(2906002)(9686003)(6306002)(11346002)(97736004)(5250100002)(93886005)(53936002)(53386004)(476003)(316002)(99286004)(2900100001)(486006)(86362001)(7736002)(5890100001)(6116002)(3660700001)(110136005)(8936002)(6246003)(478600001)(53546011)(446003)(106356001)(59450400001)(105586002)(6506007)(6436002)(81166006)(14454004)(81156014)(102836004)(76176011)(74316002)(68736007)(7696005)(5660300001)(229853002)(46003)(74482002)(966005); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR08MB1983; H:SN1PR08MB1854.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: jhyVG4iNAYbnGPfRHSJbc5Kkvl8wuN+f3eqAtgsylNTSAKrfSusZcZJJkNLt70zJTziGlZ0BzmThZVNAnOGt/CXh/4y5XnSBeYhQ9yRZZQz3HHzT8oY9MrEhshkl/aztYtd1WFjUMMjSlRUecm6yNuBHpOnlr2A005WJFC+I3oEQinnKNcVDIwB13gVGcikH
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 603f58f9-c183-4958-648c-08d5b6a3cbca
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 603f58f9-c183-4958-648c-08d5b6a3cbca
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 May 2018 18:28:15.4006 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR08MB1983
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/txx0rbBrxjoJh3dN6HUj9ZEDr1g>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 18:28:22 -0000

Interesting.  I don't believe I've ever seen an implementation actually do =
that.  If none of the client's proffered protocols are supported, they pret=
end not to support ALPN and don't include the extension in the ServerHello.=
  (Though obviously I haven't attempted to test this much.)

-----Original Message-----
From: Lucas Pardue [mailto:Lucas.Pardue@bbc.co.uk]=20
Sent: Wednesday, May 9, 2018 4:24 PM
To: Mike Bishop <mbishop@evequefou.be>; Sam Hurst-RD <samuelh@rd.bbc.co.uk>=
; IETF QUIC WG <quic@ietf.org>
Subject: RE: Clarification of transport and HTTP version compatibility

Thanks for that explanation Mike, it makes more sense now.=20

> It should be implied, but might be worth explicitly stating, that failure=
 to agree on an ALPN is incompatible with all QUIC versions, always fatal.

I don't know if it needs explicit statement. RFC 7301 section 3.2 states th=
at "In the event that the server supports no  protocols that the client adv=
ertises, then the server SHALL respond with a fatal "no_application_protoco=
l" alert."

Cheers
Lucas

-----Original Message-----
From: Lucas Pardue [mailto:Lucas.Pardue@bbc.co.uk]
Sent: Wednesday, May 9, 2018 2:43 PM
To: Mike Bishop <mbishop@evequefou.be>; Sam Hurst-RD <samuelh@rd.bbc.co.uk>=
; IETF QUIC WG <quic@ietf.org>
Subject: RE: Clarification of transport and HTTP version compatibility

I've not terribly familiar with the transport negotiation aspects, so I'm p=
robably missing something sorry.

I guess what is not clear to me is the question, who is responsible for ens=
uring a sane answer is negotiated? (I suspect no one). It gets more annoyin=
g if the client is acting on information provided to it via Alt-Svc, which =
is quite liberal to from the sender perspective (there are some rules for t=
he client defined in HTTP/QUIC 2.1.1.).

How I read things in the simple case was:

1) Transport version negotiation takes place and client chooses a version. =
Cryptographic handshake is next.
2) Client intitiates TLS 1.3 handshake with version info for revalidation, =
plus ALPN list of what it believes are application protocols that are compa=
tible with the chosen version of QUIC.
   a) POSSIBILITY 1 in a pathological case it always sends the same list re=
gardless of version.
3) Server selects an application protocol it believes is compatible with th=
e chosen version of QUIC.
  b) POSSIBILITY 2 naive implementations just assume "hq" works for everyth=
ing.
4) Client sends something the server is unhappy with and the connection bom=
bs with a protocol error.

Cheers
Lucas
________________________________________
From: Mike Bishop [mbishop@evequefou.be]
Sent: 09 May 2018 22:01
To: Lucas Pardue; Sam Hurst-RD; IETF QUIC WG
Subject: RE: Clarification of transport and HTTP version compatibility

They *shouldn't* be unanticipated protocol errors, because both are negotia=
ted.  I would expect (or at least hope) that these will manifest as negotia=
tion failures at worst.

-----Original Message-----
From: Lucas Pardue [mailto:Lucas.Pardue@bbc.co.uk]
Sent: Wednesday, May 9, 2018 11:04 AM
To: Mike Bishop <mbishop@evequefou.be>; Sam Hurst-RD <samuelh@rd.bbc.co.uk>=
; IETF QUIC WG <quic@ietf.org>
Subject: RE: Clarification of transport and HTTP version compatibility

I think this all works fine in the current stage of specification.

Longer term, what is the failure case for interoperability where different =
implementations have  different rules for how to combine QUIC version and H=
TTP/QUIC version. Protocol error due to reception of unanticipated packets =
and or HTTP/QUIC frames?

Lucas
________________________________________
From: QUIC [quic-bounces@ietf.org] on behalf of Mike Bishop [mbishop@eveque=
fou.be]
Sent: 09 May 2018 18:18
To: Sam Hurst-RD; IETF QUIC WG
Subject: RE: Clarification of transport and HTTP version compatibility

There's no firm restriction, no.  While I find it likely that draft deploym=
ents will choose to keep matching versions, the only restriction that the H=
TTP draft currently imposes is that it be a version of QUIC which uses TLS =
as the handshake protocol.

-----Original Message-----
From: QUIC <quic-bounces@ietf.org> On Behalf Of Samuel Hurst
Sent: Wednesday, May 9, 2018 9:05 AM
To: IETF QUIC WG <quic@ietf.org>
Subject: Clarification of transport and HTTP version compatibility

Hi all,

Does the quic-transport version and the HTTP mapping version have to match?=
 For example, could you negotiate QUIC draft-11, but the HTTP side is still=
 using an older version (such as draft-09 to avoid the requirement of QPACK=
)?

As far as I understand it, the QUIC transport version is negotiated as part=
 of the TransportParams in the appropriate TLS extension, and the HTTP mapp=
ing version is negotiated by ALPN. So in the example above, would it be acc=
eptable to negotiate 0xff00000a as the transport protocol version, and then=
 have an ALPN string of "hq-09"?

I'm then assuming that a valid Alt-Svc header for my example could be as
follows:

Alt-Svc: hq-09=3D":4443";quic=3D"ff00000a"

The quic-tls draft mentions in Section 9.1 "The application-layer protocol =
MAY restrict the QUIC version that it can operate over", but none of the qu=
ic-http drafts that I've read list any such restriction.
Therefore, I'm then further assuming that it's safe to run whatever version=
 of the HTTP mapping I like, unless there's a compatibility matrix between =
the various specs that I'm missing?

Best Regards,
Sam



-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and may contain personal =
views which are not the views of the BBC unless specifically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender imme=
diately.
Please note that the BBC monitors e-mails sent or received.
Further communication will signify your consent to this.
-----------------------------


From nobody Thu May 10 11:41:20 2018
Return-Path: <Andrei.Popov@microsoft.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 693AE12EB68 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 11:41:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 q2G9Bps0dCAR for <quic@ietfa.amsl.com>; Thu, 10 May 2018 11:41:15 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0129.outbound.protection.outlook.com [104.47.33.129]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 753EB12D94B for <quic@ietf.org>; Thu, 10 May 2018 11:41:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=1tJntnNXfbtbMpnfxDqCoXOffIRb3vCzNz1PiEzM+iA=; b=abal/NSh4e5HkApFZJfL4eBYirjw+yZbZRu6dKAPFstv3IL49VKkqwE4t68iwnX0Ozf1S2bOVq0MFDs++uUjQlZtgtK8K70IKkJB5lzVoPxns2gJIXtrUSqpjUX0LlT9Ogj4cNciKwwJwCaWf80O6MdXG458PtHwRQ1KJ1ZrH4M=
Received: from DM5PR21MB0507.namprd21.prod.outlook.com (10.172.91.141) by DM5PR21MB0124.namprd21.prod.outlook.com (10.173.173.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.776.3; Thu, 10 May 2018 18:41:13 +0000
Received: from DM5PR21MB0507.namprd21.prod.outlook.com ([fe80::49e8:420f:baa2:a62f]) by DM5PR21MB0507.namprd21.prod.outlook.com ([fe80::49e8:420f:baa2:a62f%6]) with mapi id 15.20.0776.004; Thu, 10 May 2018 18:41:13 +0000
From: Andrei Popov <Andrei.Popov@microsoft.com>
To: Mike Bishop <mbishop@evequefou.be>, Lucas Pardue <Lucas.Pardue@bbc.co.uk>,  Sam Hurst-RD <samuelh@rd.bbc.co.uk>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Clarification of transport and HTTP version compatibility
Thread-Topic: Clarification of transport and HTTP version compatibility
Thread-Index: AQHT56+vffKCQ/PRkUih8Oq141QUU6QnpAgAgAAMygCAADG+AIAAC20AgAARCwCAAAtWAIABP5SAgAABP0A=
Date: Thu, 10 May 2018 18:41:13 +0000
Message-ID: <DM5PR21MB05078DE242AB207AFA7BBEC98C980@DM5PR21MB0507.namprd21.prod.outlook.com>
References: <906fdff3-8009-238b-998b-4ea515a2684d@rd.bbc.co.uk>, <SN1PR08MB1854826DACF0454471CB162DDA990@SN1PR08MB1854.namprd08.prod.outlook.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB2B67C@bgb01xud1012>, <SN1PR08MB1854FC73444239C609552459DA990@SN1PR08MB1854.namprd08.prod.outlook.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB2B6A9@bgb01xud1012>, <SN1PR08MB1854232CFA318E21E062BBE3DA990@SN1PR08MB1854.namprd08.prod.outlook.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB2B6BE@bgb01xud1012> <SN1PR08MB18540A5DF3C55D60BB357F46DA980@SN1PR08MB1854.namprd08.prod.outlook.com>
In-Reply-To: <SN1PR08MB18540A5DF3C55D60BB357F46DA980@SN1PR08MB1854.namprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2001:4898:80e8:c::4ca]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR21MB0124; 7:vx1YLW7lb1nRsq1NcDVSURj82haSAyqKoX1Gs6zgWgBFNKBwOLHx59mjB/X47LWetXdnEkNhBZbLH/6TKREOKCuhhmI1/ac7i5s1YL3wJ/iKVhuwSDQbOAdM6r4eRFiTaevzarzAfVRD/CmUVevSQtT5oM6NLXFVLeTLcKD0TIlc4GKSqSE8VeyTrPzXon2KVvnywiK/vKY97j/gAHlvkmC0QPtnCyV+PpS21OESSKcuO0fGMjfEtJXasWrhlso/; 20:sAjGDHqqYEO1ApzlAHzOnMdGJ65OFRCn1I2QZUiqBghmpBXtWUeX5uovtKR5u8qBKjDcUMRFgLutUZ0DkszPTkTxGIptXhvupnw6PLPBmyrJS+ZLs61gYnTsB1qUzgw9AN+kZFN4yTa42yr+bmj8EYAmcJoXcwM6ppk4AzQumiA=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(48565401081)(2017052603328)(7193020); SRVR:DM5PR21MB0124; 
x-ms-traffictypediagnostic: DM5PR21MB0124:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=Andrei.Popov@microsoft.com; 
x-microsoft-antispam-prvs: <DM5PR21MB01248482623E275346277D288C980@DM5PR21MB0124.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(189930954265078)(219752817060721)(127952516941037); 
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3231254)(2018427008)(944501410)(52105095)(3002001)(93006095)(93001095)(10201501046)(6055026)(149027)(150027)(6041310)(20161123564045)(20161123562045)(20161123558120)(20161123560045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011); SRVR:DM5PR21MB0124; BCL:0; PCL:0; RULEID:; SRVR:DM5PR21MB0124; 
x-forefront-prvs: 066898046A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(346002)(39380400002)(39860400002)(396003)(366004)(53754006)(199004)(189003)(13464003)(14454004)(7736002)(2900100001)(5890100001)(46003)(3660700001)(6436002)(8990500004)(966005)(3280700002)(10090500001)(25786009)(10290500003)(2906002)(11346002)(486006)(9686003)(446003)(6306002)(72206003)(478600001)(5250100002)(229853002)(6116002)(102836004)(8936002)(316002)(97736004)(86362001)(74316002)(6506007)(110136005)(59450400001)(22452003)(93886005)(68736007)(575784001)(6246003)(53936002)(305945005)(5660300001)(186003)(55016002)(106356001)(81156014)(8676002)(476003)(53546011)(76176011)(81166006)(7696005)(33656002)(99286004)(86612001)(105586002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR21MB0124; H:DM5PR21MB0507.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: jAIiKX61pLa3a+2357E8WDEQulVRWpiQ/uc/j8OERRRlQ91fo+Eqhbvxc5zoFopMcqbp/8USo+qZs6NHBx8vAFdX2DRaIhtCaTOuWRY5Oqxl/+r9rnuDtNaWnLca0w5N8b4RG41KkX2FHC9qAUG+OOqqU55K4HYvUwpnbszlII+jD6H4p4V1FNhketMg4CBb
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: c55271f8-3dd9-483b-50cf-08d5b6a59b31
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c55271f8-3dd9-483b-50cf-08d5b6a59b31
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 May 2018 18:41:13.0721 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR21MB0124
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/85ndrooKHaUvTGeBSBFfajTTjkM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 18:41:18 -0000

TWlrZSwgeW91IGhhdmUgbm90IG9ubHkgc2VlbiwgYnV0IHNoaXBwZWQgc3VjaCBhbiBpbXBsZW1l
bnRhdGlvbiBpbiBzZXZlcmFsIFdpbmRvd3MgcmVsZWFzZXMuDQrwn5iKDQoNClRoZSBsb2dpYyBi
ZWhpbmQgdGhlIFJGQyBpcyB0aGF0IHRoZXJlIGlzIG5vIG5lZWQgdG8gd2FzdGUgY3ljbGVzIGFu
ZCBjb21wbGV0ZSB0aGUgaGFuZHNoYWtlIGlmIHRoZSBjbGllbnQgYW5kIHNlcnZlciBkaXNhZ3Jl
ZSBvbiB0aGUgYXBwbGljYXRpb24gcHJvdG9jb2wuDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0t
LS0tDQpGcm9tOiBRVUlDIDxxdWljLWJvdW5jZXNAaWV0Zi5vcmc+IE9uIEJlaGFsZiBPZiBNaWtl
IEJpc2hvcA0KU2VudDogVGh1cnNkYXksIE1heSAxMCwgMjAxOCAxMToyOCBBTQ0KVG86IEx1Y2Fz
IFBhcmR1ZSA8THVjYXMuUGFyZHVlQGJiYy5jby51az47IFNhbSBIdXJzdC1SRCA8c2FtdWVsaEBy
ZC5iYmMuY28udWs+OyBJRVRGIFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSRTog
Q2xhcmlmaWNhdGlvbiBvZiB0cmFuc3BvcnQgYW5kIEhUVFAgdmVyc2lvbiBjb21wYXRpYmlsaXR5
DQoNCkludGVyZXN0aW5nLiAgSSBkb24ndCBiZWxpZXZlIEkndmUgZXZlciBzZWVuIGFuIGltcGxl
bWVudGF0aW9uIGFjdHVhbGx5IGRvIHRoYXQuICBJZiBub25lIG9mIHRoZSBjbGllbnQncyBwcm9m
ZmVyZWQgcHJvdG9jb2xzIGFyZSBzdXBwb3J0ZWQsIHRoZXkgcHJldGVuZCBub3QgdG8gc3VwcG9y
dCBBTFBOIGFuZCBkb24ndCBpbmNsdWRlIHRoZSBleHRlbnNpb24gaW4gdGhlIFNlcnZlckhlbGxv
LiAgKFRob3VnaCBvYnZpb3VzbHkgSSBoYXZlbid0IGF0dGVtcHRlZCB0byB0ZXN0IHRoaXMgbXVj
aC4pDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBMdWNhcyBQYXJkdWUgW21h
aWx0bzpMdWNhcy5QYXJkdWVAYmJjLmNvLnVrXSANClNlbnQ6IFdlZG5lc2RheSwgTWF5IDksIDIw
MTggNDoyNCBQTQ0KVG86IE1pa2UgQmlzaG9wIDxtYmlzaG9wQGV2ZXF1ZWZvdS5iZT47IFNhbSBI
dXJzdC1SRCA8c2FtdWVsaEByZC5iYmMuY28udWs+OyBJRVRGIFFVSUMgV0cgPHF1aWNAaWV0Zi5v
cmc+DQpTdWJqZWN0OiBSRTogQ2xhcmlmaWNhdGlvbiBvZiB0cmFuc3BvcnQgYW5kIEhUVFAgdmVy
c2lvbiBjb21wYXRpYmlsaXR5DQoNClRoYW5rcyBmb3IgdGhhdCBleHBsYW5hdGlvbiBNaWtlLCBp
dCBtYWtlcyBtb3JlIHNlbnNlIG5vdy4gDQoNCj4gSXQgc2hvdWxkIGJlIGltcGxpZWQsIGJ1dCBt
aWdodCBiZSB3b3J0aCBleHBsaWNpdGx5IHN0YXRpbmcsIHRoYXQgZmFpbHVyZSB0byBhZ3JlZSBv
biBhbiBBTFBOIGlzIGluY29tcGF0aWJsZSB3aXRoIGFsbCBRVUlDIHZlcnNpb25zLCBhbHdheXMg
ZmF0YWwuDQoNCkkgZG9uJ3Qga25vdyBpZiBpdCBuZWVkcyBleHBsaWNpdCBzdGF0ZW1lbnQuIFJG
QyA3MzAxIHNlY3Rpb24gMy4yIHN0YXRlcyB0aGF0ICJJbiB0aGUgZXZlbnQgdGhhdCB0aGUgc2Vy
dmVyIHN1cHBvcnRzIG5vICBwcm90b2NvbHMgdGhhdCB0aGUgY2xpZW50IGFkdmVydGlzZXMsIHRo
ZW4gdGhlIHNlcnZlciBTSEFMTCByZXNwb25kIHdpdGggYSBmYXRhbCAibm9fYXBwbGljYXRpb25f
cHJvdG9jb2wiIGFsZXJ0LiINCg0KQ2hlZXJzDQpMdWNhcw0KDQotLS0tLU9yaWdpbmFsIE1lc3Nh
Z2UtLS0tLQ0KRnJvbTogTHVjYXMgUGFyZHVlIFttYWlsdG86THVjYXMuUGFyZHVlQGJiYy5jby51
a10NClNlbnQ6IFdlZG5lc2RheSwgTWF5IDksIDIwMTggMjo0MyBQTQ0KVG86IE1pa2UgQmlzaG9w
IDxtYmlzaG9wQGV2ZXF1ZWZvdS5iZT47IFNhbSBIdXJzdC1SRCA8c2FtdWVsaEByZC5iYmMuY28u
dWs+OyBJRVRGIFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSRTogQ2xhcmlmaWNh
dGlvbiBvZiB0cmFuc3BvcnQgYW5kIEhUVFAgdmVyc2lvbiBjb21wYXRpYmlsaXR5DQoNCkkndmUg
bm90IHRlcnJpYmx5IGZhbWlsaWFyIHdpdGggdGhlIHRyYW5zcG9ydCBuZWdvdGlhdGlvbiBhc3Bl
Y3RzLCBzbyBJJ20gcHJvYmFibHkgbWlzc2luZyBzb21ldGhpbmcgc29ycnkuDQoNCkkgZ3Vlc3Mg
d2hhdCBpcyBub3QgY2xlYXIgdG8gbWUgaXMgdGhlIHF1ZXN0aW9uLCB3aG8gaXMgcmVzcG9uc2li
bGUgZm9yIGVuc3VyaW5nIGEgc2FuZSBhbnN3ZXIgaXMgbmVnb3RpYXRlZD8gKEkgc3VzcGVjdCBu
byBvbmUpLiBJdCBnZXRzIG1vcmUgYW5ub3lpbmcgaWYgdGhlIGNsaWVudCBpcyBhY3Rpbmcgb24g
aW5mb3JtYXRpb24gcHJvdmlkZWQgdG8gaXQgdmlhIEFsdC1TdmMsIHdoaWNoIGlzIHF1aXRlIGxp
YmVyYWwgdG8gZnJvbSB0aGUgc2VuZGVyIHBlcnNwZWN0aXZlICh0aGVyZSBhcmUgc29tZSBydWxl
cyBmb3IgdGhlIGNsaWVudCBkZWZpbmVkIGluIEhUVFAvUVVJQyAyLjEuMS4pLg0KDQpIb3cgSSBy
ZWFkIHRoaW5ncyBpbiB0aGUgc2ltcGxlIGNhc2Ugd2FzOg0KDQoxKSBUcmFuc3BvcnQgdmVyc2lv
biBuZWdvdGlhdGlvbiB0YWtlcyBwbGFjZSBhbmQgY2xpZW50IGNob29zZXMgYSB2ZXJzaW9uLiBD
cnlwdG9ncmFwaGljIGhhbmRzaGFrZSBpcyBuZXh0Lg0KMikgQ2xpZW50IGludGl0aWF0ZXMgVExT
IDEuMyBoYW5kc2hha2Ugd2l0aCB2ZXJzaW9uIGluZm8gZm9yIHJldmFsaWRhdGlvbiwgcGx1cyBB
TFBOIGxpc3Qgb2Ygd2hhdCBpdCBiZWxpZXZlcyBhcmUgYXBwbGljYXRpb24gcHJvdG9jb2xzIHRo
YXQgYXJlIGNvbXBhdGlibGUgd2l0aCB0aGUgY2hvc2VuIHZlcnNpb24gb2YgUVVJQy4NCiAgIGEp
IFBPU1NJQklMSVRZIDEgaW4gYSBwYXRob2xvZ2ljYWwgY2FzZSBpdCBhbHdheXMgc2VuZHMgdGhl
IHNhbWUgbGlzdCByZWdhcmRsZXNzIG9mIHZlcnNpb24uDQozKSBTZXJ2ZXIgc2VsZWN0cyBhbiBh
cHBsaWNhdGlvbiBwcm90b2NvbCBpdCBiZWxpZXZlcyBpcyBjb21wYXRpYmxlIHdpdGggdGhlIGNo
b3NlbiB2ZXJzaW9uIG9mIFFVSUMuDQogIGIpIFBPU1NJQklMSVRZIDIgbmFpdmUgaW1wbGVtZW50
YXRpb25zIGp1c3QgYXNzdW1lICJocSIgd29ya3MgZm9yIGV2ZXJ5dGhpbmcuDQo0KSBDbGllbnQg
c2VuZHMgc29tZXRoaW5nIHRoZSBzZXJ2ZXIgaXMgdW5oYXBweSB3aXRoIGFuZCB0aGUgY29ubmVj
dGlvbiBib21icyB3aXRoIGEgcHJvdG9jb2wgZXJyb3IuDQoNCkNoZWVycw0KTHVjYXMNCl9fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkZyb206IE1pa2UgQmlzaG9wIFtt
YmlzaG9wQGV2ZXF1ZWZvdS5iZV0NClNlbnQ6IDA5IE1heSAyMDE4IDIyOjAxDQpUbzogTHVjYXMg
UGFyZHVlOyBTYW0gSHVyc3QtUkQ7IElFVEYgUVVJQyBXRw0KU3ViamVjdDogUkU6IENsYXJpZmlj
YXRpb24gb2YgdHJhbnNwb3J0IGFuZCBIVFRQIHZlcnNpb24gY29tcGF0aWJpbGl0eQ0KDQpUaGV5
ICpzaG91bGRuJ3QqIGJlIHVuYW50aWNpcGF0ZWQgcHJvdG9jb2wgZXJyb3JzLCBiZWNhdXNlIGJv
dGggYXJlIG5lZ290aWF0ZWQuICBJIHdvdWxkIGV4cGVjdCAob3IgYXQgbGVhc3QgaG9wZSkgdGhh
dCB0aGVzZSB3aWxsIG1hbmlmZXN0IGFzIG5lZ290aWF0aW9uIGZhaWx1cmVzIGF0IHdvcnN0Lg0K
DQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogTHVjYXMgUGFyZHVlIFttYWlsdG86
THVjYXMuUGFyZHVlQGJiYy5jby51a10NClNlbnQ6IFdlZG5lc2RheSwgTWF5IDksIDIwMTggMTE6
MDQgQU0NClRvOiBNaWtlIEJpc2hvcCA8bWJpc2hvcEBldmVxdWVmb3UuYmU+OyBTYW0gSHVyc3Qt
UkQgPHNhbXVlbGhAcmQuYmJjLmNvLnVrPjsgSUVURiBRVUlDIFdHIDxxdWljQGlldGYub3JnPg0K
U3ViamVjdDogUkU6IENsYXJpZmljYXRpb24gb2YgdHJhbnNwb3J0IGFuZCBIVFRQIHZlcnNpb24g
Y29tcGF0aWJpbGl0eQ0KDQpJIHRoaW5rIHRoaXMgYWxsIHdvcmtzIGZpbmUgaW4gdGhlIGN1cnJl
bnQgc3RhZ2Ugb2Ygc3BlY2lmaWNhdGlvbi4NCg0KTG9uZ2VyIHRlcm0sIHdoYXQgaXMgdGhlIGZh
aWx1cmUgY2FzZSBmb3IgaW50ZXJvcGVyYWJpbGl0eSB3aGVyZSBkaWZmZXJlbnQgaW1wbGVtZW50
YXRpb25zIGhhdmUgIGRpZmZlcmVudCBydWxlcyBmb3IgaG93IHRvIGNvbWJpbmUgUVVJQyB2ZXJz
aW9uIGFuZCBIVFRQL1FVSUMgdmVyc2lvbi4gUHJvdG9jb2wgZXJyb3IgZHVlIHRvIHJlY2VwdGlv
biBvZiB1bmFudGljaXBhdGVkIHBhY2tldHMgYW5kIG9yIEhUVFAvUVVJQyBmcmFtZXM/DQoNCkx1
Y2FzDQpfX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fDQpGcm9tOiBRVUlD
IFtxdWljLWJvdW5jZXNAaWV0Zi5vcmddIG9uIGJlaGFsZiBvZiBNaWtlIEJpc2hvcCBbbWJpc2hv
cEBldmVxdWVmb3UuYmVdDQpTZW50OiAwOSBNYXkgMjAxOCAxODoxOA0KVG86IFNhbSBIdXJzdC1S
RDsgSUVURiBRVUlDIFdHDQpTdWJqZWN0OiBSRTogQ2xhcmlmaWNhdGlvbiBvZiB0cmFuc3BvcnQg
YW5kIEhUVFAgdmVyc2lvbiBjb21wYXRpYmlsaXR5DQoNClRoZXJlJ3Mgbm8gZmlybSByZXN0cmlj
dGlvbiwgbm8uICBXaGlsZSBJIGZpbmQgaXQgbGlrZWx5IHRoYXQgZHJhZnQgZGVwbG95bWVudHMg
d2lsbCBjaG9vc2UgdG8ga2VlcCBtYXRjaGluZyB2ZXJzaW9ucywgdGhlIG9ubHkgcmVzdHJpY3Rp
b24gdGhhdCB0aGUgSFRUUCBkcmFmdCBjdXJyZW50bHkgaW1wb3NlcyBpcyB0aGF0IGl0IGJlIGEg
dmVyc2lvbiBvZiBRVUlDIHdoaWNoIHVzZXMgVExTIGFzIHRoZSBoYW5kc2hha2UgcHJvdG9jb2wu
DQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBRVUlDIDxxdWljLWJvdW5jZXNA
aWV0Zi5vcmc+IE9uIEJlaGFsZiBPZiBTYW11ZWwgSHVyc3QNClNlbnQ6IFdlZG5lc2RheSwgTWF5
IDksIDIwMTggOTowNSBBTQ0KVG86IElFVEYgUVVJQyBXRyA8cXVpY0BpZXRmLm9yZz4NClN1Ympl
Y3Q6IENsYXJpZmljYXRpb24gb2YgdHJhbnNwb3J0IGFuZCBIVFRQIHZlcnNpb24gY29tcGF0aWJp
bGl0eQ0KDQpIaSBhbGwsDQoNCkRvZXMgdGhlIHF1aWMtdHJhbnNwb3J0IHZlcnNpb24gYW5kIHRo
ZSBIVFRQIG1hcHBpbmcgdmVyc2lvbiBoYXZlIHRvIG1hdGNoPyBGb3IgZXhhbXBsZSwgY291bGQg
eW91IG5lZ290aWF0ZSBRVUlDIGRyYWZ0LTExLCBidXQgdGhlIEhUVFAgc2lkZSBpcyBzdGlsbCB1
c2luZyBhbiBvbGRlciB2ZXJzaW9uIChzdWNoIGFzIGRyYWZ0LTA5IHRvIGF2b2lkIHRoZSByZXF1
aXJlbWVudCBvZiBRUEFDSyk/DQoNCkFzIGZhciBhcyBJIHVuZGVyc3RhbmQgaXQsIHRoZSBRVUlD
IHRyYW5zcG9ydCB2ZXJzaW9uIGlzIG5lZ290aWF0ZWQgYXMgcGFydCBvZiB0aGUgVHJhbnNwb3J0
UGFyYW1zIGluIHRoZSBhcHByb3ByaWF0ZSBUTFMgZXh0ZW5zaW9uLCBhbmQgdGhlIEhUVFAgbWFw
cGluZyB2ZXJzaW9uIGlzIG5lZ290aWF0ZWQgYnkgQUxQTi4gU28gaW4gdGhlIGV4YW1wbGUgYWJv
dmUsIHdvdWxkIGl0IGJlIGFjY2VwdGFibGUgdG8gbmVnb3RpYXRlIDB4ZmYwMDAwMGEgYXMgdGhl
IHRyYW5zcG9ydCBwcm90b2NvbCB2ZXJzaW9uLCBhbmQgdGhlbiBoYXZlIGFuIEFMUE4gc3RyaW5n
IG9mICJocS0wOSI/DQoNCkknbSB0aGVuIGFzc3VtaW5nIHRoYXQgYSB2YWxpZCBBbHQtU3ZjIGhl
YWRlciBmb3IgbXkgZXhhbXBsZSBjb3VsZCBiZSBhcw0KZm9sbG93czoNCg0KQWx0LVN2YzogaHEt
MDk9Ijo0NDQzIjtxdWljPSJmZjAwMDAwYSINCg0KVGhlIHF1aWMtdGxzIGRyYWZ0IG1lbnRpb25z
IGluIFNlY3Rpb24gOS4xICJUaGUgYXBwbGljYXRpb24tbGF5ZXIgcHJvdG9jb2wgTUFZIHJlc3Ry
aWN0IHRoZSBRVUlDIHZlcnNpb24gdGhhdCBpdCBjYW4gb3BlcmF0ZSBvdmVyIiwgYnV0IG5vbmUg
b2YgdGhlIHF1aWMtaHR0cCBkcmFmdHMgdGhhdCBJJ3ZlIHJlYWQgbGlzdCBhbnkgc3VjaCByZXN0
cmljdGlvbi4NClRoZXJlZm9yZSwgSSdtIHRoZW4gZnVydGhlciBhc3N1bWluZyB0aGF0IGl0J3Mg
c2FmZSB0byBydW4gd2hhdGV2ZXIgdmVyc2lvbiBvZiB0aGUgSFRUUCBtYXBwaW5nIEkgbGlrZSwg
dW5sZXNzIHRoZXJlJ3MgYSBjb21wYXRpYmlsaXR5IG1hdHJpeCBiZXR3ZWVuIHRoZSB2YXJpb3Vz
IHNwZWNzIHRoYXQgSSdtIG1pc3Npbmc/DQoNCkJlc3QgUmVnYXJkcywNClNhbQ0KDQoNCg0KLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCmh0dHBzOi8vbmEwMS5zYWZlbGlua3MucHJvdGVj
dGlvbi5vdXRsb29rLmNvbS8/dXJsPWh0dHAlM0ElMkYlMkZ3d3cuYmJjLmNvLnVrJmRhdGE9MDIl
N0MwMSU3Q0FuZHJlaS5Qb3BvdiU0MG1pY3Jvc29mdC5jb20lN0M0YWU5NzM2ZTM5NjE0NjAxNjYw
MzA4ZDViNmEzZDRlNyU3QzcyZjk4OGJmODZmMTQxYWY5MWFiMmQ3Y2QwMTFkYjQ3JTdDMSU3QzAl
N0M2MzY2MTU3MzcxMzU0MTUyODcmc2RhdGE9JTJGY3J0NVltWERONGJ2Vjl5ZkdranZuV3ZZcjBM
YnR0c0ZQM05taEZNdHVJJTNEJnJlc2VydmVkPTANClRoaXMgZS1tYWlsIChhbmQgYW55IGF0dGFj
aG1lbnRzKSBpcyBjb25maWRlbnRpYWwgYW5kIG1heSBjb250YWluIHBlcnNvbmFsIHZpZXdzIHdo
aWNoIGFyZSBub3QgdGhlIHZpZXdzIG9mIHRoZSBCQkMgdW5sZXNzIHNwZWNpZmljYWxseSBzdGF0
ZWQuDQpJZiB5b3UgaGF2ZSByZWNlaXZlZCBpdCBpbg0KZXJyb3IsIHBsZWFzZSBkZWxldGUgaXQg
ZnJvbSB5b3VyIHN5c3RlbS4NCkRvIG5vdCB1c2UsIGNvcHkgb3IgZGlzY2xvc2UgdGhlDQppbmZv
cm1hdGlvbiBpbiBhbnkgd2F5IG5vciBhY3QgaW4gcmVsaWFuY2Ugb24gaXQgYW5kIG5vdGlmeSB0
aGUgc2VuZGVyIGltbWVkaWF0ZWx5Lg0KUGxlYXNlIG5vdGUgdGhhdCB0aGUgQkJDIG1vbml0b3Jz
IGUtbWFpbHMgc2VudCBvciByZWNlaXZlZC4NCkZ1cnRoZXIgY29tbXVuaWNhdGlvbiB3aWxsIHNp
Z25pZnkgeW91ciBjb25zZW50IHRvIHRoaXMuDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LQ0KDQo=


From nobody Thu May 10 11:45:15 2018
Return-Path: <dtikhonov@litespeedtech.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C334112EB7B for <quic@ietfa.amsl.com>; Thu, 10 May 2018 11:45:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 jTSBfqP0JYsA for <quic@ietfa.amsl.com>; Thu, 10 May 2018 11:45:12 -0700 (PDT)
Received: from mail-qk0-x22b.google.com (mail-qk0-x22b.google.com [IPv6:2607:f8b0:400d:c09::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 34271127077 for <quic@ietf.org>; Thu, 10 May 2018 11:45:12 -0700 (PDT)
Received: by mail-qk0-x22b.google.com with SMTP id c137-v6so2386246qkg.2 for <quic@ietf.org>; Thu, 10 May 2018 11:45:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=AT7GKMoISm3dTS6n7SeCrOWSYEsIwEkYpL0Wnm/Wg9s=; b=z/zFSN5V+rkgqkX9tIioJibGTJOw515+qyVGEdF4Xjk1+oxhV9lvD3MGwqlvNQnhKQ RWVWGqNHShhzvxX97INuCHtDn14fKhbkdLaxSzvOv6j5DpbD0NHwm09dKMAhJjNcDHxp pMIItufjgpoJyWGO0zTqcwpK/ZINUOkYX956QAe7cHVn+5zZWyCRk1+K7+UpH0uCcW4q 8KW1m0CMQVjQGbtGnrN/vXiibvS7WxUyB+IdW8vpgDNAYkrdfaWTBCDHjNz7hI2u9tGj FF/MzHNoEi8esKNy8OXe+cINVOrcS+PhVXl+rEZbN3U6Eo5jaLXNG2uoG/+PI/0/3+za Wl+A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=AT7GKMoISm3dTS6n7SeCrOWSYEsIwEkYpL0Wnm/Wg9s=; b=nq9I7tULl6YOACCetMfkwwFoH81flF9tKMiGnvF+2RWD/2h6ReQ6aEQPa3HjiBP7Vn 9pLuVIZ7TyqVbE0W4Qj+MjgXiPJXYJjWs+5FZvlk7BEf/lmYyJwHuHZYvaXMTEL9G6EB pR7bCU2RhKlbDM2t6aOii3EjVVeXyQMuc8Ad8JmVeijrwPCu7bbtVU3Eh9SgYsE/iLzr gZ8IZMBRNGNOz7B2G7Atcsb2lRB9nZTPLMuqgxk+e6HQSHkmIrz5fAo7hiVK0y/cQ2qe 8fx0w0Mlk/GYWc12yte8airCYRRNq/5/QlNLmsCZ2HGf8KjwwiOHeIA5FZ19bzC9Y/bc +/3A==
X-Gm-Message-State: ALKqPwdyUY0MBeDC/0yIbVVc57UiSqKmRCqZIhhC1W6+XjGZFMsdyNCT cBiIcaCscApFlP2VBBi4JJ3CZpZt
X-Google-Smtp-Source: AB8JxZoXUUbqV9V4XYgWH7KNpVmCG/GPL6YGE+dgOnMtHqimPl9lI1j89RdmS4HPu4qWLXl2GSuD4g==
X-Received: by 2002:a37:c89b:: with SMTP id t27-v6mr2349315qkl.214.1525977911238;  Thu, 10 May 2018 11:45:11 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id b12-v6sm1158040qtb.57.2018.05.10.11.45.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 May 2018 11:45:11 -0700 (PDT)
Date: Thu, 10 May 2018 14:45:05 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Mike Bishop <mbishop@evequefou.be>
Cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Why allow empty STREAM frames when offset is zero?
Message-ID: <20180510184505.GA23837@ubuntu-dmitri>
Mail-Followup-To: Mike Bishop <mbishop@evequefou.be>, IETF QUIC WG <quic@ietf.org>
References: <20180510180509.GA2505@ubuntu-dmitri> <SN1PR08MB18543D4C234CC672616E37BFDA980@SN1PR08MB1854.namprd08.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <SN1PR08MB18543D4C234CC672616E37BFDA980@SN1PR08MB1854.namprd08.prod.outlook.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/xNdsjkWisthh7aFabT6jF3MsYcs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 18:45:14 -0000

Is there a real-life use case that is implied here?  I can't see why it
would be useful.

On the other hand, it creates an odd situation for an implementation:
a frame has arrived, yet the higher layer cannot read from it yet, so
an incoming stream is unreadable.

On Thu, May 10, 2018 at 06:25:55PM +0000, Mike Bishop wrote:
> If you want to open a stream (e.g. permit data to be sent in the opposite direction of a bidirectional stream), but don't actually have data ready to send yet.
> 
> -----Original Message-----
> From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of Dmitri Tikhonov
> Sent: Thursday, May 10, 2018 11:05 AM
> To: IETF QUIC WG <quic@ietf.org>
> Subject: Why allow empty STREAM frames when offset is zero?
> 
> [draft-ietf-quic-transport-11] says the following:
> 
>    A stream frame's Stream Data MUST NOT be empty, unless the offset is
>    0 or the FIN bit is set.
> 
> Why allow empty STREAM frames when the offset is zero?  What is the purpose?
> 
>   - Dmitri.
> 


From nobody Thu May 10 11:55:57 2018
Return-Path: <mbishop@evequefou.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5C03C12EB87 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 11:55:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 Dxt4NCjGopWY for <quic@ietfa.amsl.com>; Thu, 10 May 2018 11:55:52 -0700 (PDT)
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (mail-by2nam01on0091.outbound.protection.outlook.com [104.47.34.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89BB112EB82 for <quic@ietf.org>; Thu, 10 May 2018 11:55:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=olK2HdVAfOlrxtkhypwezJUhnQBP4WixAo4e/2JkWAc=; b=YoQ2pKLFVQJVL/GoJ4jSHrxolrNtpbcQi6896TsNZ9fWagvA1jK84ENhm2PCM99HcW6tB7IFB1MMWw0qwRaboKBkzwdqBM3eXRvalH8tgYYRxSQjMw34M4DwuVjx+eGbze31Eyc8Z1rtzGpYhhoeMKBQCXTOz0ajRwjCKXpU7us=
Received: from SN1PR08MB1854.namprd08.prod.outlook.com (10.169.39.8) by SN1PR08MB1791.namprd08.prod.outlook.com (10.162.134.21) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.755.16; Thu, 10 May 2018 18:55:49 +0000
Received: from SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d]) by SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d%13]) with mapi id 15.20.0735.021; Thu, 10 May 2018 18:55:49 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Andrei Popov <Andrei.Popov@microsoft.com>, Lucas Pardue <Lucas.Pardue@bbc.co.uk>, Sam Hurst-RD <samuelh@rd.bbc.co.uk>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Clarification of transport and HTTP version compatibility
Thread-Topic: Clarification of transport and HTTP version compatibility
Thread-Index: AQHT56+xI3vQwOQ++kOo1AZLBRUIXaQno4FAgAANUQCAADE84IAAC+8AgAALO3CAABEmAIABPx9AgAAEFICAAAOa4A==
Date: Thu, 10 May 2018 18:55:48 +0000
Message-ID: <SN1PR08MB1854CBF3794EA23E4B42398FDA980@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <906fdff3-8009-238b-998b-4ea515a2684d@rd.bbc.co.uk>, <SN1PR08MB1854826DACF0454471CB162DDA990@SN1PR08MB1854.namprd08.prod.outlook.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB2B67C@bgb01xud1012>, <SN1PR08MB1854FC73444239C609552459DA990@SN1PR08MB1854.namprd08.prod.outlook.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB2B6A9@bgb01xud1012>, <SN1PR08MB1854232CFA318E21E062BBE3DA990@SN1PR08MB1854.namprd08.prod.outlook.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB2B6BE@bgb01xud1012> <SN1PR08MB18540A5DF3C55D60BB357F46DA980@SN1PR08MB1854.namprd08.prod.outlook.com> <DM5PR21MB05078DE242AB207AFA7BBEC98C980@DM5PR21MB0507.namprd21.prod.outlook.com>
In-Reply-To: <DM5PR21MB05078DE242AB207AFA7BBEC98C980@DM5PR21MB0507.namprd21.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [2001:4878:8103:102:100::308]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN1PR08MB1791; 7:yZDXXHZWF7YHmxKLiM1z5tnnLTMTqPN2SzmkbusU7Y5KfgKIDxWLG0vwHJUq8fPYFD3dElqPgOozXHHL9ys39XQSICm0CQUDr0xOPWJyEHs3OcQZXkcP1GQcuerMyfHNCvaPH/4qs3CNtd/hV0A0Rqqw0QpFLzIfk3higRr9pHcnrGl1yeenEayjEV68Vsokc0FLZ2sU2EKvHrkJrUT0GSLfpXWfCXrpux9uf+63sjIrmV7Hp1Q7/p6oysDwZuKL
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(5600026)(2017052603328)(7153060)(7193020); SRVR:SN1PR08MB1791; 
x-ms-traffictypediagnostic: SN1PR08MB1791:
x-microsoft-antispam-prvs: <SN1PR08MB179192049D4067AC0D34228CDA980@SN1PR08MB1791.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(158342451672863)(189930954265078)(219752817060721)(127952516941037);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3002001)(10201501046)(3231254)(944501410)(52105095)(93006095)(93001095)(149027)(150027)(6041310)(20161123558120)(2016111802025)(20161123564045)(20161123562045)(20161123560045)(6072148)(6043046)(201708071742011); SRVR:SN1PR08MB1791; BCL:0; PCL:0; RULEID:; SRVR:SN1PR08MB1791; 
x-forefront-prvs: 066898046A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(366004)(39830400003)(346002)(376002)(39380400002)(13464003)(53754006)(199004)(189003)(316002)(9686003)(46003)(8936002)(6116002)(6306002)(53546011)(59450400001)(53936002)(55016002)(74316002)(305945005)(6246003)(1511001)(68736007)(93886005)(575784001)(81166006)(6506007)(76176011)(486006)(86362001)(102836004)(446003)(7696005)(476003)(5890100001)(11346002)(99286004)(2900100001)(74482002)(5250100002)(186003)(14454004)(45080400002)(33656002)(478600001)(5660300001)(966005)(25786009)(97736004)(229853002)(3660700001)(3280700002)(7736002)(6436002)(8666007)(106356001)(2906002)(110136005)(81156014)(105586002)(8676002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR08MB1791; H:SN1PR08MB1854.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: /9JZV9MVGUwR2gh6bPFxECnsU9oDge7gQSQruSUf7zMGiCr9kGBFF3P1uycDXzutXOlmF4wdswRSla6l/VY0qwLsnifU3JRJ7spwfKUyqrvpP/Fj+lcMuayfq5DbVFbMlUDJyIPoc7QK63C7qS6UaGqWZxZimrPudqN53RM/182TBebNDXld/oispiDEWTNe
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: adb47e8b-66f6-4be5-8896-08d5b6a7a531
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: adb47e8b-66f6-4be5-8896-08d5b6a7a531
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 May 2018 18:55:48.7729 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR08MB1791
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/LwWCtZ7fcO07aEWM2r2sPkNF5HA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 18:55:55 -0000

QWgsIEkgc2VlIFNFQ19FX0FQUExJQ0FUSU9OX1BST1RPQ09MX01JU01BVENIIGZvciB0aGF0LiAg
R29vZCB0byBrbm93Lg0KDQpJbiB0aGF0IGNhc2UsIHdlIHNob3VsZCBiZSBhYmxlIHRvIGFzc3Vt
ZSB0aGF0IHRoZSByZXF1aXJlbWVudCB0byB1c2UgQUxQTiBpcyBzdWZmaWNpZW50OyBpZiBubyBB
TFBOIHRva2VuIGNhbiBiZSBhZ3JlZWQgb24sIHRoZSBUTFMgaGFuZHNoYWtlIHdpbGwgZmFpbCBh
bmQgdGhlIGNvbm5lY3Rpb24gd2lsbCBjbG9zZS4NCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0t
LS0NCkZyb206IEFuZHJlaSBQb3BvdiBbbWFpbHRvOkFuZHJlaS5Qb3BvdkBtaWNyb3NvZnQuY29t
XSANClNlbnQ6IFRodXJzZGF5LCBNYXkgMTAsIDIwMTggMTE6NDEgQU0NClRvOiBNaWtlIEJpc2hv
cCA8bWJpc2hvcEBldmVxdWVmb3UuYmU+OyBMdWNhcyBQYXJkdWUgPEx1Y2FzLlBhcmR1ZUBiYmMu
Y28udWs+OyBTYW0gSHVyc3QtUkQgPHNhbXVlbGhAcmQuYmJjLmNvLnVrPjsgSUVURiBRVUlDIFdH
IDxxdWljQGlldGYub3JnPg0KU3ViamVjdDogUkU6IENsYXJpZmljYXRpb24gb2YgdHJhbnNwb3J0
IGFuZCBIVFRQIHZlcnNpb24gY29tcGF0aWJpbGl0eQ0KDQpNaWtlLCB5b3UgaGF2ZSBub3Qgb25s
eSBzZWVuLCBidXQgc2hpcHBlZCBzdWNoIGFuIGltcGxlbWVudGF0aW9uIGluIHNldmVyYWwgV2lu
ZG93cyByZWxlYXNlcy4NCvCfmIoNCg0KVGhlIGxvZ2ljIGJlaGluZCB0aGUgUkZDIGlzIHRoYXQg
dGhlcmUgaXMgbm8gbmVlZCB0byB3YXN0ZSBjeWNsZXMgYW5kIGNvbXBsZXRlIHRoZSBoYW5kc2hh
a2UgaWYgdGhlIGNsaWVudCBhbmQgc2VydmVyIGRpc2FncmVlIG9uIHRoZSBhcHBsaWNhdGlvbiBw
cm90b2NvbC4NCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IFFVSUMgPHF1aWMt
Ym91bmNlc0BpZXRmLm9yZz4gT24gQmVoYWxmIE9mIE1pa2UgQmlzaG9wDQpTZW50OiBUaHVyc2Rh
eSwgTWF5IDEwLCAyMDE4IDExOjI4IEFNDQpUbzogTHVjYXMgUGFyZHVlIDxMdWNhcy5QYXJkdWVA
YmJjLmNvLnVrPjsgU2FtIEh1cnN0LVJEIDxzYW11ZWxoQHJkLmJiYy5jby51az47IElFVEYgUVVJ
QyBXRyA8cXVpY0BpZXRmLm9yZz4NClN1YmplY3Q6IFJFOiBDbGFyaWZpY2F0aW9uIG9mIHRyYW5z
cG9ydCBhbmQgSFRUUCB2ZXJzaW9uIGNvbXBhdGliaWxpdHkNCg0KSW50ZXJlc3RpbmcuICBJIGRv
bid0IGJlbGlldmUgSSd2ZSBldmVyIHNlZW4gYW4gaW1wbGVtZW50YXRpb24gYWN0dWFsbHkgZG8g
dGhhdC4gIElmIG5vbmUgb2YgdGhlIGNsaWVudCdzIHByb2ZmZXJlZCBwcm90b2NvbHMgYXJlIHN1
cHBvcnRlZCwgdGhleSBwcmV0ZW5kIG5vdCB0byBzdXBwb3J0IEFMUE4gYW5kIGRvbid0IGluY2x1
ZGUgdGhlIGV4dGVuc2lvbiBpbiB0aGUgU2VydmVySGVsbG8uICAoVGhvdWdoIG9idmlvdXNseSBJ
IGhhdmVuJ3QgYXR0ZW1wdGVkIHRvIHRlc3QgdGhpcyBtdWNoLikNCg0KLS0tLS1PcmlnaW5hbCBN
ZXNzYWdlLS0tLS0NCkZyb206IEx1Y2FzIFBhcmR1ZSBbbWFpbHRvOkx1Y2FzLlBhcmR1ZUBiYmMu
Y28udWtdIA0KU2VudDogV2VkbmVzZGF5LCBNYXkgOSwgMjAxOCA0OjI0IFBNDQpUbzogTWlrZSBC
aXNob3AgPG1iaXNob3BAZXZlcXVlZm91LmJlPjsgU2FtIEh1cnN0LVJEIDxzYW11ZWxoQHJkLmJi
Yy5jby51az47IElFVEYgUVVJQyBXRyA8cXVpY0BpZXRmLm9yZz4NClN1YmplY3Q6IFJFOiBDbGFy
aWZpY2F0aW9uIG9mIHRyYW5zcG9ydCBhbmQgSFRUUCB2ZXJzaW9uIGNvbXBhdGliaWxpdHkNCg0K
VGhhbmtzIGZvciB0aGF0IGV4cGxhbmF0aW9uIE1pa2UsIGl0IG1ha2VzIG1vcmUgc2Vuc2Ugbm93
LiANCg0KPiBJdCBzaG91bGQgYmUgaW1wbGllZCwgYnV0IG1pZ2h0IGJlIHdvcnRoIGV4cGxpY2l0
bHkgc3RhdGluZywgdGhhdCBmYWlsdXJlIHRvIGFncmVlIG9uIGFuIEFMUE4gaXMgaW5jb21wYXRp
YmxlIHdpdGggYWxsIFFVSUMgdmVyc2lvbnMsIGFsd2F5cyBmYXRhbC4NCg0KSSBkb24ndCBrbm93
IGlmIGl0IG5lZWRzIGV4cGxpY2l0IHN0YXRlbWVudC4gUkZDIDczMDEgc2VjdGlvbiAzLjIgc3Rh
dGVzIHRoYXQgIkluIHRoZSBldmVudCB0aGF0IHRoZSBzZXJ2ZXIgc3VwcG9ydHMgbm8gIHByb3Rv
Y29scyB0aGF0IHRoZSBjbGllbnQgYWR2ZXJ0aXNlcywgdGhlbiB0aGUgc2VydmVyIFNIQUxMIHJl
c3BvbmQgd2l0aCBhIGZhdGFsICJub19hcHBsaWNhdGlvbl9wcm90b2NvbCIgYWxlcnQuIg0KDQpD
aGVlcnMNCkx1Y2FzDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBMdWNhcyBQ
YXJkdWUgW21haWx0bzpMdWNhcy5QYXJkdWVAYmJjLmNvLnVrXQ0KU2VudDogV2VkbmVzZGF5LCBN
YXkgOSwgMjAxOCAyOjQzIFBNDQpUbzogTWlrZSBCaXNob3AgPG1iaXNob3BAZXZlcXVlZm91LmJl
PjsgU2FtIEh1cnN0LVJEIDxzYW11ZWxoQHJkLmJiYy5jby51az47IElFVEYgUVVJQyBXRyA8cXVp
Y0BpZXRmLm9yZz4NClN1YmplY3Q6IFJFOiBDbGFyaWZpY2F0aW9uIG9mIHRyYW5zcG9ydCBhbmQg
SFRUUCB2ZXJzaW9uIGNvbXBhdGliaWxpdHkNCg0KSSd2ZSBub3QgdGVycmlibHkgZmFtaWxpYXIg
d2l0aCB0aGUgdHJhbnNwb3J0IG5lZ290aWF0aW9uIGFzcGVjdHMsIHNvIEknbSBwcm9iYWJseSBt
aXNzaW5nIHNvbWV0aGluZyBzb3JyeS4NCg0KSSBndWVzcyB3aGF0IGlzIG5vdCBjbGVhciB0byBt
ZSBpcyB0aGUgcXVlc3Rpb24sIHdobyBpcyByZXNwb25zaWJsZSBmb3IgZW5zdXJpbmcgYSBzYW5l
IGFuc3dlciBpcyBuZWdvdGlhdGVkPyAoSSBzdXNwZWN0IG5vIG9uZSkuIEl0IGdldHMgbW9yZSBh
bm5veWluZyBpZiB0aGUgY2xpZW50IGlzIGFjdGluZyBvbiBpbmZvcm1hdGlvbiBwcm92aWRlZCB0
byBpdCB2aWEgQWx0LVN2Yywgd2hpY2ggaXMgcXVpdGUgbGliZXJhbCB0byBmcm9tIHRoZSBzZW5k
ZXIgcGVyc3BlY3RpdmUgKHRoZXJlIGFyZSBzb21lIHJ1bGVzIGZvciB0aGUgY2xpZW50IGRlZmlu
ZWQgaW4gSFRUUC9RVUlDIDIuMS4xLikuDQoNCkhvdyBJIHJlYWQgdGhpbmdzIGluIHRoZSBzaW1w
bGUgY2FzZSB3YXM6DQoNCjEpIFRyYW5zcG9ydCB2ZXJzaW9uIG5lZ290aWF0aW9uIHRha2VzIHBs
YWNlIGFuZCBjbGllbnQgY2hvb3NlcyBhIHZlcnNpb24uIENyeXB0b2dyYXBoaWMgaGFuZHNoYWtl
IGlzIG5leHQuDQoyKSBDbGllbnQgaW50aXRpYXRlcyBUTFMgMS4zIGhhbmRzaGFrZSB3aXRoIHZl
cnNpb24gaW5mbyBmb3IgcmV2YWxpZGF0aW9uLCBwbHVzIEFMUE4gbGlzdCBvZiB3aGF0IGl0IGJl
bGlldmVzIGFyZSBhcHBsaWNhdGlvbiBwcm90b2NvbHMgdGhhdCBhcmUgY29tcGF0aWJsZSB3aXRo
IHRoZSBjaG9zZW4gdmVyc2lvbiBvZiBRVUlDLg0KICAgYSkgUE9TU0lCSUxJVFkgMSBpbiBhIHBh
dGhvbG9naWNhbCBjYXNlIGl0IGFsd2F5cyBzZW5kcyB0aGUgc2FtZSBsaXN0IHJlZ2FyZGxlc3Mg
b2YgdmVyc2lvbi4NCjMpIFNlcnZlciBzZWxlY3RzIGFuIGFwcGxpY2F0aW9uIHByb3RvY29sIGl0
IGJlbGlldmVzIGlzIGNvbXBhdGlibGUgd2l0aCB0aGUgY2hvc2VuIHZlcnNpb24gb2YgUVVJQy4N
CiAgYikgUE9TU0lCSUxJVFkgMiBuYWl2ZSBpbXBsZW1lbnRhdGlvbnMganVzdCBhc3N1bWUgImhx
IiB3b3JrcyBmb3IgZXZlcnl0aGluZy4NCjQpIENsaWVudCBzZW5kcyBzb21ldGhpbmcgdGhlIHNl
cnZlciBpcyB1bmhhcHB5IHdpdGggYW5kIHRoZSBjb25uZWN0aW9uIGJvbWJzIHdpdGggYSBwcm90
b2NvbCBlcnJvci4NCg0KQ2hlZXJzDQpMdWNhcw0KX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fXw0KRnJvbTogTWlrZSBCaXNob3AgW21iaXNob3BAZXZlcXVlZm91LmJlXQ0K
U2VudDogMDkgTWF5IDIwMTggMjI6MDENClRvOiBMdWNhcyBQYXJkdWU7IFNhbSBIdXJzdC1SRDsg
SUVURiBRVUlDIFdHDQpTdWJqZWN0OiBSRTogQ2xhcmlmaWNhdGlvbiBvZiB0cmFuc3BvcnQgYW5k
IEhUVFAgdmVyc2lvbiBjb21wYXRpYmlsaXR5DQoNClRoZXkgKnNob3VsZG4ndCogYmUgdW5hbnRp
Y2lwYXRlZCBwcm90b2NvbCBlcnJvcnMsIGJlY2F1c2UgYm90aCBhcmUgbmVnb3RpYXRlZC4gIEkg
d291bGQgZXhwZWN0IChvciBhdCBsZWFzdCBob3BlKSB0aGF0IHRoZXNlIHdpbGwgbWFuaWZlc3Qg
YXMgbmVnb3RpYXRpb24gZmFpbHVyZXMgYXQgd29yc3QuDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2Fn
ZS0tLS0tDQpGcm9tOiBMdWNhcyBQYXJkdWUgW21haWx0bzpMdWNhcy5QYXJkdWVAYmJjLmNvLnVr
XQ0KU2VudDogV2VkbmVzZGF5LCBNYXkgOSwgMjAxOCAxMTowNCBBTQ0KVG86IE1pa2UgQmlzaG9w
IDxtYmlzaG9wQGV2ZXF1ZWZvdS5iZT47IFNhbSBIdXJzdC1SRCA8c2FtdWVsaEByZC5iYmMuY28u
dWs+OyBJRVRGIFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSRTogQ2xhcmlmaWNh
dGlvbiBvZiB0cmFuc3BvcnQgYW5kIEhUVFAgdmVyc2lvbiBjb21wYXRpYmlsaXR5DQoNCkkgdGhp
bmsgdGhpcyBhbGwgd29ya3MgZmluZSBpbiB0aGUgY3VycmVudCBzdGFnZSBvZiBzcGVjaWZpY2F0
aW9uLg0KDQpMb25nZXIgdGVybSwgd2hhdCBpcyB0aGUgZmFpbHVyZSBjYXNlIGZvciBpbnRlcm9w
ZXJhYmlsaXR5IHdoZXJlIGRpZmZlcmVudCBpbXBsZW1lbnRhdGlvbnMgaGF2ZSAgZGlmZmVyZW50
IHJ1bGVzIGZvciBob3cgdG8gY29tYmluZSBRVUlDIHZlcnNpb24gYW5kIEhUVFAvUVVJQyB2ZXJz
aW9uLiBQcm90b2NvbCBlcnJvciBkdWUgdG8gcmVjZXB0aW9uIG9mIHVuYW50aWNpcGF0ZWQgcGFj
a2V0cyBhbmQgb3IgSFRUUC9RVUlDIGZyYW1lcz8NCg0KTHVjYXMNCl9fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX19fX19fX18NCkZyb206IFFVSUMgW3F1aWMtYm91bmNlc0BpZXRmLm9y
Z10gb24gYmVoYWxmIG9mIE1pa2UgQmlzaG9wIFttYmlzaG9wQGV2ZXF1ZWZvdS5iZV0NClNlbnQ6
IDA5IE1heSAyMDE4IDE4OjE4DQpUbzogU2FtIEh1cnN0LVJEOyBJRVRGIFFVSUMgV0cNClN1Ympl
Y3Q6IFJFOiBDbGFyaWZpY2F0aW9uIG9mIHRyYW5zcG9ydCBhbmQgSFRUUCB2ZXJzaW9uIGNvbXBh
dGliaWxpdHkNCg0KVGhlcmUncyBubyBmaXJtIHJlc3RyaWN0aW9uLCBuby4gIFdoaWxlIEkgZmlu
ZCBpdCBsaWtlbHkgdGhhdCBkcmFmdCBkZXBsb3ltZW50cyB3aWxsIGNob29zZSB0byBrZWVwIG1h
dGNoaW5nIHZlcnNpb25zLCB0aGUgb25seSByZXN0cmljdGlvbiB0aGF0IHRoZSBIVFRQIGRyYWZ0
IGN1cnJlbnRseSBpbXBvc2VzIGlzIHRoYXQgaXQgYmUgYSB2ZXJzaW9uIG9mIFFVSUMgd2hpY2gg
dXNlcyBUTFMgYXMgdGhlIGhhbmRzaGFrZSBwcm90b2NvbC4NCg0KLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCkZyb206IFFVSUMgPHF1aWMtYm91bmNlc0BpZXRmLm9yZz4gT24gQmVoYWxmIE9m
IFNhbXVlbCBIdXJzdA0KU2VudDogV2VkbmVzZGF5LCBNYXkgOSwgMjAxOCA5OjA1IEFNDQpUbzog
SUVURiBRVUlDIFdHIDxxdWljQGlldGYub3JnPg0KU3ViamVjdDogQ2xhcmlmaWNhdGlvbiBvZiB0
cmFuc3BvcnQgYW5kIEhUVFAgdmVyc2lvbiBjb21wYXRpYmlsaXR5DQoNCkhpIGFsbCwNCg0KRG9l
cyB0aGUgcXVpYy10cmFuc3BvcnQgdmVyc2lvbiBhbmQgdGhlIEhUVFAgbWFwcGluZyB2ZXJzaW9u
IGhhdmUgdG8gbWF0Y2g/IEZvciBleGFtcGxlLCBjb3VsZCB5b3UgbmVnb3RpYXRlIFFVSUMgZHJh
ZnQtMTEsIGJ1dCB0aGUgSFRUUCBzaWRlIGlzIHN0aWxsIHVzaW5nIGFuIG9sZGVyIHZlcnNpb24g
KHN1Y2ggYXMgZHJhZnQtMDkgdG8gYXZvaWQgdGhlIHJlcXVpcmVtZW50IG9mIFFQQUNLKT8NCg0K
QXMgZmFyIGFzIEkgdW5kZXJzdGFuZCBpdCwgdGhlIFFVSUMgdHJhbnNwb3J0IHZlcnNpb24gaXMg
bmVnb3RpYXRlZCBhcyBwYXJ0IG9mIHRoZSBUcmFuc3BvcnRQYXJhbXMgaW4gdGhlIGFwcHJvcHJp
YXRlIFRMUyBleHRlbnNpb24sIGFuZCB0aGUgSFRUUCBtYXBwaW5nIHZlcnNpb24gaXMgbmVnb3Rp
YXRlZCBieSBBTFBOLiBTbyBpbiB0aGUgZXhhbXBsZSBhYm92ZSwgd291bGQgaXQgYmUgYWNjZXB0
YWJsZSB0byBuZWdvdGlhdGUgMHhmZjAwMDAwYSBhcyB0aGUgdHJhbnNwb3J0IHByb3RvY29sIHZl
cnNpb24sIGFuZCB0aGVuIGhhdmUgYW4gQUxQTiBzdHJpbmcgb2YgImhxLTA5Ij8NCg0KSSdtIHRo
ZW4gYXNzdW1pbmcgdGhhdCBhIHZhbGlkIEFsdC1TdmMgaGVhZGVyIGZvciBteSBleGFtcGxlIGNv
dWxkIGJlIGFzDQpmb2xsb3dzOg0KDQpBbHQtU3ZjOiBocS0wOT0iOjQ0NDMiO3F1aWM9ImZmMDAw
MDBhIg0KDQpUaGUgcXVpYy10bHMgZHJhZnQgbWVudGlvbnMgaW4gU2VjdGlvbiA5LjEgIlRoZSBh
cHBsaWNhdGlvbi1sYXllciBwcm90b2NvbCBNQVkgcmVzdHJpY3QgdGhlIFFVSUMgdmVyc2lvbiB0
aGF0IGl0IGNhbiBvcGVyYXRlIG92ZXIiLCBidXQgbm9uZSBvZiB0aGUgcXVpYy1odHRwIGRyYWZ0
cyB0aGF0IEkndmUgcmVhZCBsaXN0IGFueSBzdWNoIHJlc3RyaWN0aW9uLg0KVGhlcmVmb3JlLCBJ
J20gdGhlbiBmdXJ0aGVyIGFzc3VtaW5nIHRoYXQgaXQncyBzYWZlIHRvIHJ1biB3aGF0ZXZlciB2
ZXJzaW9uIG9mIHRoZSBIVFRQIG1hcHBpbmcgSSBsaWtlLCB1bmxlc3MgdGhlcmUncyBhIGNvbXBh
dGliaWxpdHkgbWF0cml4IGJldHdlZW4gdGhlIHZhcmlvdXMgc3BlY3MgdGhhdCBJJ20gbWlzc2lu
Zz8NCg0KQmVzdCBSZWdhcmRzLA0KU2FtDQoNCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLQ0KaHR0cHM6Ly9uYTAxLnNhZmVsaW5rcy5wcm90ZWN0aW9uLm91dGxvb2suY29tLz91cmw9
aHR0cCUzQSUyRiUyRnd3dy5iYmMuY28udWsmZGF0YT0wMiU3QzAxJTdDQW5kcmVpLlBvcG92JTQw
bWljcm9zb2Z0LmNvbSU3QzRhZTk3MzZlMzk2MTQ2MDE2NjAzMDhkNWI2YTNkNGU3JTdDNzJmOTg4
YmY4NmYxNDFhZjkxYWIyZDdjZDAxMWRiNDclN0MxJTdDMCU3QzYzNjYxNTczNzEzNTQxNTI4NyZz
ZGF0YT0lMkZjcnQ1WW1YRE40YnZWOXlmR2tqdm5XdllyMExidHRzRlAzTm1oRk10dUklM0QmcmVz
ZXJ2ZWQ9MA0KVGhpcyBlLW1haWwgKGFuZCBhbnkgYXR0YWNobWVudHMpIGlzIGNvbmZpZGVudGlh
bCBhbmQgbWF5IGNvbnRhaW4gcGVyc29uYWwgdmlld3Mgd2hpY2ggYXJlIG5vdCB0aGUgdmlld3Mg
b2YgdGhlIEJCQyB1bmxlc3Mgc3BlY2lmaWNhbGx5IHN0YXRlZC4NCklmIHlvdSBoYXZlIHJlY2Vp
dmVkIGl0IGluDQplcnJvciwgcGxlYXNlIGRlbGV0ZSBpdCBmcm9tIHlvdXIgc3lzdGVtLg0KRG8g
bm90IHVzZSwgY29weSBvciBkaXNjbG9zZSB0aGUNCmluZm9ybWF0aW9uIGluIGFueSB3YXkgbm9y
IGFjdCBpbiByZWxpYW5jZSBvbiBpdCBhbmQgbm90aWZ5IHRoZSBzZW5kZXIgaW1tZWRpYXRlbHku
DQpQbGVhc2Ugbm90ZSB0aGF0IHRoZSBCQkMgbW9uaXRvcnMgZS1tYWlscyBzZW50IG9yIHJlY2Vp
dmVkLg0KRnVydGhlciBjb21tdW5pY2F0aW9uIHdpbGwgc2lnbmlmeSB5b3VyIGNvbnNlbnQgdG8g
dGhpcy4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQoNCg==


From nobody Thu May 10 12:02:01 2018
Return-Path: <pmcmanus@mozilla.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CFDD12EB7E for <quic@ietfa.amsl.com>; Thu, 10 May 2018 12:02:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.233
X-Spam-Level: 
X-Spam-Status: No, score=-1.233 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 up8KWkGWSDwy for <quic@ietfa.amsl.com>; Thu, 10 May 2018 12:01:58 -0700 (PDT)
Received: from linode64.ducksong.com (www.ducksong.com [192.155.95.102]) by ietfa.amsl.com (Postfix) with ESMTP id D4B1512EB8D for <quic@ietf.org>; Thu, 10 May 2018 12:01:28 -0700 (PDT)
Received: from mail-oi0-f53.google.com (mail-oi0-f53.google.com [209.85.218.53]) by linode64.ducksong.com (Postfix) with ESMTPSA id 7AC583A055 for <quic@ietf.org>; Thu, 10 May 2018 15:01:26 -0400 (EDT)
Received: by mail-oi0-f53.google.com with SMTP id v2-v6so2700480oif.3 for <quic@ietf.org>; Thu, 10 May 2018 12:01:26 -0700 (PDT)
X-Gm-Message-State: ALKqPwc5afo+dGBzegrjvLYXylc0d8m6E9S80PEHhaB8qvqfXh9psfTB YcStyEHT0r55+nqurl+Z11j2Ol8QK+gqs7f6cuw=
X-Google-Smtp-Source: AB8JxZrklaXduhscSHUrI7kuOtEu9d1oZDvTqiOVcRx7NrCjusdICjZLJVpUOADCNy6Rqs8CX85wQvKQLHuWjUADJ6c=
X-Received: by 2002:aca:ccd4:: with SMTP id c203-v6mr1596267oig.38.1525978886206;  Thu, 10 May 2018 12:01:26 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.74.138.36 with HTTP; Thu, 10 May 2018 12:01:25 -0700 (PDT)
In-Reply-To: <20180510184505.GA23837@ubuntu-dmitri>
References: <20180510180509.GA2505@ubuntu-dmitri> <SN1PR08MB18543D4C234CC672616E37BFDA980@SN1PR08MB1854.namprd08.prod.outlook.com> <20180510184505.GA23837@ubuntu-dmitri>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Thu, 10 May 2018 21:01:25 +0200
X-Gmail-Original-Message-ID: <CAOdDvNpM0hSH9Qzm2qbXcfyYdUGAT5Sg373NPcV2B4WC2ebzmg@mail.gmail.com>
Message-ID: <CAOdDvNpM0hSH9Qzm2qbXcfyYdUGAT5Sg373NPcV2B4WC2ebzmg@mail.gmail.com>
Subject: Re: Why allow empty STREAM frames when offset is zero?
To: Mike Bishop <mbishop@evequefou.be>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000727c35056bdea592"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/L63VqAjP6DD-CUnV7rzPWtJe9Aw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 19:02:00 -0000

--000000000000727c35056bdea592
Content-Type: text/plain; charset="UTF-8"

maybe its the only way to get more stream id flow control credits :)

On Thu, May 10, 2018 at 8:45 PM, Dmitri Tikhonov <
dtikhonov@litespeedtech.com> wrote:

> Is there a real-life use case that is implied here?  I can't see why it
> would be useful.
>
> On the other hand, it creates an odd situation for an implementation:
> a frame has arrived, yet the higher layer cannot read from it yet, so
> an incoming stream is unreadable.
>
> On Thu, May 10, 2018 at 06:25:55PM +0000, Mike Bishop wrote:
> > If you want to open a stream (e.g. permit data to be sent in the
> opposite direction of a bidirectional stream), but don't actually have data
> ready to send yet.
> >
> > -----Original Message-----
> > From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of Dmitri Tikhonov
> > Sent: Thursday, May 10, 2018 11:05 AM
> > To: IETF QUIC WG <quic@ietf.org>
> > Subject: Why allow empty STREAM frames when offset is zero?
> >
> > [draft-ietf-quic-transport-11] says the following:
> >
> >    A stream frame's Stream Data MUST NOT be empty, unless the offset is
> >    0 or the FIN bit is set.
> >
> > Why allow empty STREAM frames when the offset is zero?  What is the
> purpose?
> >
> >   - Dmitri.
> >
>
>

--000000000000727c35056bdea592
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">maybe its the only way to get more stream id flow control =
credits :)<br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quot=
e">On Thu, May 10, 2018 at 8:45 PM, Dmitri Tikhonov <span dir=3D"ltr">&lt;<=
a href=3D"mailto:dtikhonov@litespeedtech.com" target=3D"_blank">dtikhonov@l=
itespeedtech.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote"=
 style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Is=
 there a real-life use case that is implied here?=C2=A0 I can&#39;t see why=
 it<br>
would be useful.<br>
<br>
On the other hand, it creates an odd situation for an implementation:<br>
a frame has arrived, yet the higher layer cannot read from it yet, so<br>
an incoming stream is unreadable.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On Thu, May 10, 2018 at 06:25:55PM +0000, Mike Bishop wrote:<br>
&gt; If you want to open a stream (e.g. permit data to be sent in the oppos=
ite direction of a bidirectional stream), but don&#39;t actually have data =
ready to send yet.<br>
&gt; <br>
&gt; -----Original Message-----<br>
&gt; From: QUIC [mailto:<a href=3D"mailto:quic-bounces@ietf.org">quic-bounc=
es@ietf.org</a>] On Behalf Of Dmitri Tikhonov<br>
&gt; Sent: Thursday, May 10, 2018 11:05 AM<br>
&gt; To: IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org">quic@ietf.org</a=
>&gt;<br>
&gt; Subject: Why allow empty STREAM frames when offset is zero?<br>
&gt; <br>
&gt; [draft-ietf-quic-transport-11] says the following:<br>
&gt; <br>
&gt;=C2=A0 =C2=A0 A stream frame&#39;s Stream Data MUST NOT be empty, unles=
s the offset is<br>
&gt;=C2=A0 =C2=A0 0 or the FIN bit is set.<br>
&gt; <br>
&gt; Why allow empty STREAM frames when the offset is zero?=C2=A0 What is t=
he purpose?<br>
&gt; <br>
&gt;=C2=A0 =C2=A0- Dmitri.<br>
&gt; <br>
<br>
</div></div></blockquote></div><br></div>

--000000000000727c35056bdea592--


From nobody Thu May 10 12:02:20 2018
Return-Path: <nibanks@microsoft.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D14E212EB8D for <quic@ietfa.amsl.com>; Thu, 10 May 2018 12:02:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.01
X-Spam-Level: 
X-Spam-Status: No, score=-2.01 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=microsoft.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 odO_f5XOW1a0 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 12:02:17 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0090.outbound.protection.outlook.com [104.47.37.90]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B97DB12EBB3 for <quic@ietf.org>; Thu, 10 May 2018 12:02:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=MflOFR89+TFQm5JGmTjZ0CSdt0dKp7e+ZEmO5Y/M5yw=; b=HIPv6M1ZX94yjUo25CNqoI9UO14V8nyAKOFKldhHBFWHjN4L6R5n98evbmOkDqVlhxsOCWGSoSHeM2SBDgXJkUiqSlfqdvKpGiwvX6cMqRZJY63RApo28d1dAjynHsGv4py3KriaLc5POnwDQF0LGc64FTheLDeqO1KyY7Nu34I=
Received: from DM5PR2101MB0901.namprd21.prod.outlook.com (52.132.132.158) by DM5PR2101MB1077.namprd21.prod.outlook.com (52.132.130.11) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.776.3; Thu, 10 May 2018 19:02:06 +0000
Received: from DM5PR2101MB0901.namprd21.prod.outlook.com ([fe80::ac02:3f79:af:e239]) by DM5PR2101MB0901.namprd21.prod.outlook.com ([fe80::ac02:3f79:af:e239%2]) with mapi id 15.20.0776.004; Thu, 10 May 2018 19:02:06 +0000
From: Nick Banks <nibanks@microsoft.com>
To: Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Mike Bishop <mbishop@evequefou.be>
CC: IETF QUIC WG <quic@ietf.org>
Subject: RE: Why allow empty STREAM frames when offset is zero?
Thread-Topic: Why allow empty STREAM frames when offset is zero?
Thread-Index: AQHT6ImMM/Ln2zdjxECadMVu77QIk6QpR5eAgAAFW4CAAAQyAA==
Date: Thu, 10 May 2018 19:02:06 +0000
Message-ID: <DM5PR2101MB090184FC657942BD294E555DB3980@DM5PR2101MB0901.namprd21.prod.outlook.com>
References: <20180510180509.GA2505@ubuntu-dmitri> <SN1PR08MB18543D4C234CC672616E37BFDA980@SN1PR08MB1854.namprd08.prod.outlook.com> <20180510184505.GA23837@ubuntu-dmitri>
In-Reply-To: <20180510184505.GA23837@ubuntu-dmitri>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=True; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Owner=nibanks@microsoft.com; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2018-05-10T19:02:04.8333603Z; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=General; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Application=Microsoft Azure Information Protection; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Extended_MSFT_Method=Automatic; Sensitivity=General
x-originating-ip: [2001:4898:80e8::256]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; DM5PR2101MB1077; 7:QmBmO81q/5vG/R+iguDObwj7SLLFKqrTdlEhZnQjb109o7jzJo7e/tT2BqaWJWzZkZ1J0QKY6efac3yw8eEPjQQLgiedMaTnkoYhZXvFqFJCA9jzwrXDZRiYCcdKyG3w7Kyt9McHPxM1frVy4ED5Dx+qicEkweYNkpoWUgUhdMWk8sP8xb+miGn2bvj6RvYkZ0+9SnClhfNFHfWcseEFQv+8S21zKEpbKh1mmGObeBWtuakBUQ3xiidp8r3IQYjo; 20:WVAoPW7NIVDi98kkxk6C5KrjbZyXQ8lLTH5zwJppOU4ExcLbSilR19eVDnSnzEpXMomDWLWILuB6puwk57CPi2H4R0KbVN/PrwI5ucXpGSh7qp4cYB0UZ2gq8I7Iu6MSOq3GvRZGenDhfoUeCuENJkX56XMnt2r7Q9qgFvD+WZo=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-ms-office365-filtering-ht: Tenant
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(48565401081)(2017052603328)(7193020); SRVR:DM5PR2101MB1077; 
x-ms-traffictypediagnostic: DM5PR2101MB1077:
x-microsoft-antispam-prvs: <DM5PR2101MB10772D5A1858863C7E74D5D2B3980@DM5PR2101MB1077.namprd21.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(21532816269658);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3231254)(2018427008)(944501410)(52105095)(93006095)(93001095)(10201501046)(3002001)(6055026)(149027)(150027)(6041310)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123562045)(20161123558120)(6072148)(201708071742011); SRVR:DM5PR2101MB1077; BCL:0; PCL:0; RULEID:; SRVR:DM5PR2101MB1077; 
x-forefront-prvs: 066898046A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(376002)(346002)(39380400002)(366004)(39860400002)(199004)(189003)(13464003)(4326008)(106356001)(97736004)(33656002)(7736002)(68736007)(46003)(55016002)(9686003)(105586002)(8676002)(486006)(6246003)(305945005)(8936002)(110136005)(11346002)(53936002)(8990500004)(81156014)(81166006)(446003)(316002)(6116002)(476003)(5660300001)(14454004)(10290500003)(5250100002)(86612001)(74316002)(186003)(10090500001)(2906002)(3280700002)(25786009)(86362001)(76176011)(6346003)(3660700001)(102836004)(53546011)(7696005)(2900100001)(6506007)(229853002)(478600001)(99286004)(6436002)(22452003); DIR:OUT; SFP:1102; SCL:1; SRVR:DM5PR2101MB1077; H:DM5PR2101MB0901.namprd21.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: microsoft.com does not designate permitted sender hosts)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=nibanks@microsoft.com; 
x-microsoft-antispam-message-info: EfsOa+ZnxVw4beFoEJcxjJsWj6T7cJwS6U+gpS3qr+sJHMwVyrfgyVEPNSAVFGxvZPJsi8AtJm9/0Tqy/crlgiz2Y1Wclv8vs7g4FlieAjSsyqX2a6rRJ39Eo2oWCAeYVQacqjIAaBLWvv/22bmJcb0FmGgvr5kILBWM8x3Gmq+UqCOHHXvIxYj1aZmWVY4i
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 07185a89-5184-4d13-8501-08d5b6a88619
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 07185a89-5184-4d13-8501-08d5b6a88619
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 May 2018 19:02:06.3133 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM5PR2101MB1077
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/gd6zsVdCrSGzyTZnWMe80ZGUnO8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 19:02:19 -0000

In WinQuic, the resulting frame just results in the NEW_STREAM event to the=
 application layer. They can start reading from it, but we just won't have =
anything to read yet. That NEW_STREAM event can be used for a number of thi=
ngs. If you are moving from multiple TCP connections to a single QUIC conne=
ction, it could be seen as the equivalent of a single TCP connect event.

- Nick

-----Original Message-----
From: QUIC <quic-bounces@ietf.org> On Behalf Of Dmitri Tikhonov
Sent: Thursday, May 10, 2018 11:45 AM
To: Mike Bishop <mbishop@evequefou.be>
Cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Why allow empty STREAM frames when offset is zero?

Is there a real-life use case that is implied here?  I can't see why it wou=
ld be useful.

On the other hand, it creates an odd situation for an implementation:
a frame has arrived, yet the higher layer cannot read from it yet, so an in=
coming stream is unreadable.

On Thu, May 10, 2018 at 06:25:55PM +0000, Mike Bishop wrote:
> If you want to open a stream (e.g. permit data to be sent in the opposite=
 direction of a bidirectional stream), but don't actually have data ready t=
o send yet.
>=20
> -----Original Message-----
> From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of Dmitri Tikhonov
> Sent: Thursday, May 10, 2018 11:05 AM
> To: IETF QUIC WG <quic@ietf.org>
> Subject: Why allow empty STREAM frames when offset is zero?
>=20
> [draft-ietf-quic-transport-11] says the following:
>=20
>    A stream frame's Stream Data MUST NOT be empty, unless the offset is
>    0 or the FIN bit is set.
>=20
> Why allow empty STREAM frames when the offset is zero?  What is the purpo=
se?
>=20
>   - Dmitri.
>=20


From nobody Thu May 10 12:10:55 2018
Return-Path: <dtikhonov@litespeedtech.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2D4FD1270AB for <quic@ietfa.amsl.com>; Thu, 10 May 2018 12:10:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 xU6nPGZ8b6BN for <quic@ietfa.amsl.com>; Thu, 10 May 2018 12:10:50 -0700 (PDT)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 517E6126FB3 for <quic@ietf.org>; Thu, 10 May 2018 12:10:50 -0700 (PDT)
Received: by mail-qt0-x236.google.com with SMTP id c2-v6so3997697qtn.9 for <quic@ietf.org>; Thu, 10 May 2018 12:10:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=H9+vuyfENML4FxZi+b9Evi/oj2W9VyTjKPMxq2DLbXE=; b=CJs5drhTGwjIMBCT2APTLmHSM6bYtXp4voLTyTmrZpvfI8EgMuuLu2F3ohRKVePSF8 0ZLZfEp2f3vfqOahXCAr8VqbnueXWibXXYJ/kLqaS/WsxwE3uTxEU7oTBEFH7hvmUxf7 Bo0vs6NZiQ1xfNFyAqXf+mZtcdyD4ZMIndZ3wBfZqwhjvlphBzOw/4maKMM9jk3m4H0h hVbMbwpqHWzn9NYyNmUTFDgzWNCYxCx6iVU73tYMOkb6wSydigYppCnXqy/HN0uVDVL0 efUEYvEwmngcV1s9gkTDkYfBug4ObMmUMvGM5WZlEwX5CqmpoEzpKCefuiPDUaRWYt/l ccAg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=H9+vuyfENML4FxZi+b9Evi/oj2W9VyTjKPMxq2DLbXE=; b=mflTwjP7oLUA7ISZ/vuMYXERx4g4xJMSWs+xshCR5L6EMVDbmGxvXGz6VyzPT2ZJVb uIS4XDt97D9awjryG+tDsQl+5Gz6+EN9UVaqp42xLXq8IuyaSigOR+D8ernUs9i9J4LT sSFniSVd0mnEPzWn9jlxmLYNT+3HmJzdxpao3pz7CTdNw6uBkXSWQ3SM1HIi9jY1QVjo Rbz+U8d+eZ/yDS1hv58Cf/AAkUixIPnHhcoXfolNFvX8pkpEAh5tnYWzgJwL72FqbpZy DtqCy8D4oo3zDHQdJg2mObOjjbTUNZiB5tcb8d5L6P36srojpWA43DRGJLyY57tdrXVh +4CQ==
X-Gm-Message-State: ALKqPwfKnokWRTsW3G5kDhVhtDi9MYmhV8AjbDhGkxkPe5IRCpvVPP7L WbkBgfyOtubW+b0POVrK0tG54g==
X-Google-Smtp-Source: AB8JxZqbCmanH8l1BlWoHk0/DF7ogi5+3JJAVtO0PuJs0WYKiZKJpsLbkvAciuhCBVB0GFHjD3UGCA==
X-Received: by 2002:aed:23f5:: with SMTP id k50-v6mr2654053qtc.367.1525979449363;  Thu, 10 May 2018 12:10:49 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id p63-v6sm997455qkd.92.2018.05.10.12.10.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 10 May 2018 12:10:48 -0700 (PDT)
Date: Thu, 10 May 2018 15:10:46 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Nick Banks <nibanks@microsoft.com>
Cc: Mike Bishop <mbishop@evequefou.be>, IETF QUIC WG <quic@ietf.org>
Subject: Re: Why allow empty STREAM frames when offset is zero?
Message-ID: <20180510191045.GB23837@ubuntu-dmitri>
Mail-Followup-To: Nick Banks <nibanks@microsoft.com>, Mike Bishop <mbishop@evequefou.be>, IETF QUIC WG <quic@ietf.org>
References: <20180510180509.GA2505@ubuntu-dmitri> <SN1PR08MB18543D4C234CC672616E37BFDA980@SN1PR08MB1854.namprd08.prod.outlook.com> <20180510184505.GA23837@ubuntu-dmitri> <DM5PR2101MB090184FC657942BD294E555DB3980@DM5PR2101MB0901.namprd21.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <DM5PR2101MB090184FC657942BD294E555DB3980@DM5PR2101MB0901.namprd21.prod.outlook.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/RlpetHXpu-dT35G_KWcy3AyKqjo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 19:10:53 -0000

On Thu, May 10, 2018 at 07:02:06PM +0000, Nick Banks wrote:
> If you are moving from multiple TCP connections to a single QUIC
> connection, it could be seen as the equivalent of a single TCP
> connect event.

Hmm!  This is an interesting way to look at it.

  - Dmitri.


From nobody Thu May 10 12:12:10 2018
Return-Path: <prvs=866817be88=fenix@fb.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DC06E12DA05 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 12:12:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=ngFiwkB/; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=Ac5DbrST
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 XD0hlEKS5f2a for <quic@ietfa.amsl.com>; Thu, 10 May 2018 12:12:07 -0700 (PDT)
Received: from mx0a-00082601.pphosted.com (mx0b-00082601.pphosted.com [67.231.153.30]) (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 6EB9C1270AB for <quic@ietf.org>; Thu, 10 May 2018 12:12:07 -0700 (PDT)
Received: from pps.filterd (m0089730.ppops.net [127.0.0.1]) by m0089730.ppops.net (8.16.0.22/8.16.0.22) with SMTP id w4AJBnuh014064; Thu, 10 May 2018 12:12:00 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=facebook; bh=yV9EQ0NeAvKu4iGJyJVGzmiYUXyATC4XSYmP0+wogDU=; b=ngFiwkB/60/9kRIMziMJzeqtjwt0mZ9iD8Mv1jR6oC6bVBkiUfzefEAcew9s3SVJ1mn2 pU46H7DCZWu/l/y7Ft2Ptw8EVFIEtYesfBQ6jcAZEdsUDrTg+5qC3jTBNAtwy26rTFNP sr2O1zawO1mGBwqKctkQuRWKReT/QVBYFMo= 
Received: from mail.thefacebook.com ([199.201.64.23]) by m0089730.ppops.net with ESMTP id 2hvtju0cxn-2 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 10 May 2018 12:12:00 -0700
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (192.168.54.28) by o365-in.thefacebook.com (192.168.16.18) with Microsoft SMTP Server (TLS) id 14.3.361.1; Thu, 10 May 2018 12:11:59 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version;  bh=yV9EQ0NeAvKu4iGJyJVGzmiYUXyATC4XSYmP0+wogDU=; b=Ac5DbrSTF7eunpcS6e8jTQ5NuhRgd3xRytKjwn6WFBUJoJzaASKq+IENYvfBejVkSpZGf6HfYLwfMljBzBLq2iEYbhK+HP+eNXnQi0BTlq5ZHG/jm2TcaV0ot+Et7teP7L8W7OXbYeJuKkVbbgu84MsJ4GVkYMwB+hbXG3ff79c=
Received: from BY2PR15MB0775.namprd15.prod.outlook.com (10.164.171.11) by BY2PR15MB0807.namprd15.prod.outlook.com (10.164.171.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.755.16; Thu, 10 May 2018 19:11:42 +0000
Received: from BY2PR15MB0775.namprd15.prod.outlook.com ([fe80::49b2:cd82:55e8:9da8]) by BY2PR15MB0775.namprd15.prod.outlook.com ([fe80::49b2:cd82:55e8:9da8%14]) with mapi id 15.20.0755.012; Thu, 10 May 2018 19:11:43 +0000
From: Roberto Peon <fenix@fb.com>
To: Nick Banks <nibanks=40microsoft.com@dmarc.ietf.org>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Mike Bishop <mbishop@evequefou.be>
CC: IETF QUIC WG <quic@ietf.org>
Subject: Re: Why allow empty STREAM frames when offset is zero?
Thread-Topic: Why allow empty STREAM frames when offset is zero?
Thread-Index: AQHT6ImcXNfNXuzUWkeHTiDTNe07k6QpR5eAgAAFW4CAAATBAIAAArAy
Date: Thu, 10 May 2018 19:11:42 +0000
Message-ID: <BY2PR15MB0775E5FA5E6869C85AB98933CD980@BY2PR15MB0775.namprd15.prod.outlook.com>
References: <20180510180509.GA2505@ubuntu-dmitri> <SN1PR08MB18543D4C234CC672616E37BFDA980@SN1PR08MB1854.namprd08.prod.outlook.com> <20180510184505.GA23837@ubuntu-dmitri>, <DM5PR2101MB090184FC657942BD294E555DB3980@DM5PR2101MB0901.namprd21.prod.outlook.com>
In-Reply-To: <DM5PR2101MB090184FC657942BD294E555DB3980@DM5PR2101MB0901.namprd21.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2600:387:6:80d::85]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BY2PR15MB0807; 7:6Vsj9kdJNYm5oqK3q+4xxUBcNwwex2ugcH1MGVrNsFsml3kZhmdkdv+rZ9f+LsOxmVmXZCjZVzbEJKeOyleawlUhaLtT6IF8S41D7eHwN1lBdUBjk5ZQe76JXKahVrMmwnaBLqpxauNTpbVF8I4Jx70Vh38G2XuYV9920EgQzOvGnFCqmS8+EnWctqsRcTNcQn7eou4bP5dIrlWeD9mToQEQzvyeUYAjt21xcO7l82p3En6c0HYg6yGTJqYBbqLe; 20:cwwJn6TPkUfihgCv0FtoFo5hSU71UtCGfMJyj1oCLPpwjY6BeLXbNZpxgkE8skGraOfg/TcTNjWc6c/nPwRrESM41Xsn1U2Ok/C5k32YGTfFoQQeLd2m7jjOzDA6r/gfwWxstWXowrDhpWGStoKX8np9+Ah2LBJD0NtlqtTgxcs=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BY2PR15MB0807; 
x-ms-traffictypediagnostic: BY2PR15MB0807:
x-microsoft-antispam-prvs: <BY2PR15MB0807996A554179890CDA1C29CD980@BY2PR15MB0807.namprd15.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(21532816269658);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(10201501046)(93006095)(93001095)(3002001)(3231254)(11241501184)(944501410)(52105095)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123558120)(20161123562045)(6072148)(201708071742011); SRVR:BY2PR15MB0807; BCL:0; PCL:0; RULEID:; SRVR:BY2PR15MB0807; 
x-forefront-prvs: 066898046A
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(346002)(376002)(39860400002)(39380400002)(366004)(189003)(199004)(13464003)(106356001)(186003)(53546011)(5660300001)(446003)(11346002)(2906002)(236005)(53936002)(74316002)(110136005)(102836004)(81166006)(105586002)(93886005)(55016002)(476003)(46003)(316002)(3280700002)(97736004)(54896002)(33656002)(8936002)(9686003)(486006)(7696005)(3660700001)(14454004)(8676002)(478600001)(6246003)(5250100002)(6506007)(6436002)(25786009)(229853002)(7736002)(68736007)(99286004)(86362001)(76176011)(6116002)(81156014)(2900100001)(4326008)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BY2PR15MB0807; H:BY2PR15MB0775.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: fb.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: iIQPOpe/Z1zHuEOZK9pFmSnuL+ftdY+gHywe7dbfCtfCB+2JzbGml8sqpsROsIQWadK7Fro6HYEral8HBRnc3DG72Sq1EjzG4/FHzEu9JtLhnp10jI1IBi4+ngxUaIN4PSeKe055KDEDOXXc8AfhISuBN6UOgBZ6YmNChiyQe8DLNxuCsLgAvauvUvaZskHO
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BY2PR15MB0775E5FA5E6869C85AB98933CD980BY2PR15MB0775namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: bd9c4dad-0786-4515-0f88-08d5b6a9ddda
X-MS-Exchange-CrossTenant-Network-Message-Id: bd9c4dad-0786-4515-0f88-08d5b6a9ddda
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 May 2018 19:11:42.9014 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BY2PR15MB0807
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-10_06:, , signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/O2LHBo_iQ3vl0d_pGBVS_6CGpwY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 19:12:09 -0000

--_000_BY2PR15MB0775E5FA5E6869C85AB98933CD980BY2PR15MB0775namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

It can be used to establish the mapping of the stream (src-conn-id:streamid=
 <-> dst-conn-id:streamid) through the stack of proxies, etc, especially fo=
r usecases where there is an early response.

-=3DR



Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone


-------- Original message --------
From: Nick Banks <nibanks=3D40microsoft.com@dmarc.ietf.org>
Date: 5/10/18 12:02 PM (GMT-08:00)
To: Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Mike Bishop <mbishop@eve=
quefou.be>
Cc: IETF QUIC WG <quic@ietf.org>
Subject: RE: Why allow empty STREAM frames when offset is zero?

In WinQuic, the resulting frame just results in the NEW_STREAM event to the=
 application layer. They can start reading from it, but we just won't have =
anything to read yet. That NEW_STREAM event can be used for a number of thi=
ngs. If you are moving from multiple TCP connections to a single QUIC conne=
ction, it could be seen as the equivalent of a single TCP connect event.

- Nick

-----Original Message-----
From: QUIC <quic-bounces@ietf.org> On Behalf Of Dmitri Tikhonov
Sent: Thursday, May 10, 2018 11:45 AM
To: Mike Bishop <mbishop@evequefou.be>
Cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Why allow empty STREAM frames when offset is zero?

Is there a real-life use case that is implied here?  I can't see why it wou=
ld be useful.

On the other hand, it creates an odd situation for an implementation:
a frame has arrived, yet the higher layer cannot read from it yet, so an in=
coming stream is unreadable.

On Thu, May 10, 2018 at 06:25:55PM +0000, Mike Bishop wrote:
> If you want to open a stream (e.g. permit data to be sent in the opposite=
 direction of a bidirectional stream), but don't actually have data ready t=
o send yet.
>
> -----Original Message-----
> From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of Dmitri Tikhonov
> Sent: Thursday, May 10, 2018 11:05 AM
> To: IETF QUIC WG <quic@ietf.org>
> Subject: Why allow empty STREAM frames when offset is zero?
>
> [draft-ietf-quic-transport-11] says the following:
>
>    A stream frame's Stream Data MUST NOT be empty, unless the offset is
>    0 or the FIN bit is set.
>
> Why allow empty STREAM frames when the offset is zero?  What is the purpo=
se?
>
>   - Dmitri.
>


--_000_BY2PR15MB0775E5FA5E6869C85AB98933CD980BY2PR15MB0775namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div>It can be used to establish the mapping of the stream (src-conn-id:str=
eamid &lt;-&gt; dst-conn-id:streamid) through the stack of proxies, etc, es=
pecially for usecases where there is an early response.&nbsp;</div>
<div><br>
</div>
<div>-=3DR</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div id=3D"x_composer_signature">
<div dir=3D"auto" style=3D"font-size:85%; color:#575757">Sent via the Samsu=
ng Galaxy S7, an AT&amp;T 4G LTE smartphone</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div>-------- Original message --------</div>
<div>From: Nick Banks &lt;nibanks=3D40microsoft.com@dmarc.ietf.org&gt; </di=
v>
<div>Date: 5/10/18 12:02 PM (GMT-08:00) </div>
<div>To: Dmitri Tikhonov &lt;dtikhonov@litespeedtech.com&gt;, Mike Bishop &=
lt;mbishop@evequefou.be&gt;
</div>
<div>Cc: IETF QUIC WG &lt;quic@ietf.org&gt; </div>
<div>Subject: RE: Why allow empty STREAM frames when offset is zero? </div>
<div><br>
</div>
</div>
<font size=3D"2"><span style=3D"font-size:11pt;">
<div class=3D"PlainText">In WinQuic, the resulting frame just results in th=
e NEW_STREAM event to the application layer. They can start reading from it=
, but we just won't have anything to read yet. That NEW_STREAM event can be=
 used for a number of things. If you
 are moving from multiple TCP connections to a single QUIC connection, it c=
ould be seen as the equivalent of a single TCP connect event.<br>
<br>
- Nick<br>
<br>
-----Original Message-----<br>
From: QUIC &lt;quic-bounces@ietf.org&gt; On Behalf Of Dmitri Tikhonov<br>
Sent: Thursday, May 10, 2018 11:45 AM<br>
To: Mike Bishop &lt;mbishop@evequefou.be&gt;<br>
Cc: IETF QUIC WG &lt;quic@ietf.org&gt;<br>
Subject: Re: Why allow empty STREAM frames when offset is zero?<br>
<br>
Is there a real-life use case that is implied here?&nbsp; I can't see why i=
t would be useful.<br>
<br>
On the other hand, it creates an odd situation for an implementation:<br>
a frame has arrived, yet the higher layer cannot read from it yet, so an in=
coming stream is unreadable.<br>
<br>
On Thu, May 10, 2018 at 06:25:55PM &#43;0000, Mike Bishop wrote:<br>
&gt; If you want to open a stream (e.g. permit data to be sent in the oppos=
ite direction of a bidirectional stream), but don't actually have data read=
y to send yet.<br>
&gt; <br>
&gt; -----Original Message-----<br>
&gt; From: QUIC [<a href=3D"mailto:quic-bounces@ietf.org">mailto:quic-bounc=
es@ietf.org</a>] On Behalf Of Dmitri Tikhonov<br>
&gt; Sent: Thursday, May 10, 2018 11:05 AM<br>
&gt; To: IETF QUIC WG &lt;quic@ietf.org&gt;<br>
&gt; Subject: Why allow empty STREAM frames when offset is zero?<br>
&gt; <br>
&gt; [draft-ietf-quic-transport-11] says the following:<br>
&gt; <br>
&gt;&nbsp;&nbsp;&nbsp; A stream frame's Stream Data MUST NOT be empty, unle=
ss the offset is<br>
&gt;&nbsp;&nbsp;&nbsp; 0 or the FIN bit is set.<br>
&gt; <br>
&gt; Why allow empty STREAM frames when the offset is zero?&nbsp; What is t=
he purpose?<br>
&gt; <br>
&gt;&nbsp;&nbsp; - Dmitri.<br>
&gt; <br>
<br>
</div>
</span></font>
</body>
</html>

--_000_BY2PR15MB0775E5FA5E6869C85AB98933CD980BY2PR15MB0775namp_--


From nobody Thu May 10 14:58:37 2018
Return-Path: <ilubashe@akamai.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A8E52129C51 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 14:58:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.709
X-Spam-Level: 
X-Spam-Status: No, score=-2.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 SoqXXARajhDV for <quic@ietfa.amsl.com>; Thu, 10 May 2018 14:58:28 -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 6CE9612DB70 for <quic@ietf.org>; Thu, 10 May 2018 14:58:28 -0700 (PDT)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.0.22/8.16.0.22) with SMTP id w4ALq46E021179; Thu, 10 May 2018 22:58:24 +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=N04NML7lxi7vo/+Cbs4mCSA5ZDXBnXre2tNjyGyQZ0o=; b=iMys2SNAkLaCZHEv3H+MyTHEi3WCK8Dp1tSQYuTFMBkgFQADCopdHfyax5sl4MD6iC+J jNcIblmXVkK/EOMhe6Cmphr1fXWaqP7iD7+rlgEmlBomOOYy2DpQpxiue98S2G1X3Fg+ YlmC6M7iM7NnipfwBBv2T4zyxpAPqJN0KFqH8nu/LRaTu8lfAiT8UynmiSWlwRfZTG2f 36DZitilG47bcxiE3rn97mM+8eo2kyr8Vdmq2wyem9+qVBaOcamf3zx+QP5waXsECf+I HsXqMOkyBHpUvBSX7tz6RuEappcXM6O13pCbA3AmVFT5/5v5W94XC3EZfdhguTOfaS0K mA== 
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19]) by m0050095.ppops.net-00190b01. with ESMTP id 2huyqtce3g-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 10 May 2018 22:58:24 +0100
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w4ALtxOQ022660; Thu, 10 May 2018 17:58:23 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.34]) by prod-mail-ppoint2.akamai.com with ESMTP id 2hs7xvpck7-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 10 May 2018 17:58:22 -0400
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com (172.27.123.105) by usma1ex-dag1mb3.msg.corp.akamai.com (172.27.123.103) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Thu, 10 May 2018 17:58:22 -0400
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com ([172.27.123.105]) by usma1ex-dag1mb5.msg.corp.akamai.com ([172.27.123.105]) with mapi id 15.00.1365.000; Thu, 10 May 2018 17:58:22 -0400
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: Roberto Peon <fenix@fb.com>, Nick Banks <nibanks=40microsoft.com@dmarc.ietf.org>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Mike Bishop <mbishop@evequefou.be>
CC: IETF QUIC WG <quic@ietf.org>
Subject: RE: Why allow empty STREAM frames when offset is zero?
Thread-Topic: Why allow empty STREAM frames when offset is zero?
Thread-Index: AQHT6ImJSKTfLtwgAkSWTEz8kX9aw6QpiqWAgAAFW4CAAATBAIAAAq8A///p/YA=
Date: Thu, 10 May 2018 21:58:22 +0000
Message-ID: <c0b4cd48aa5f491f91828d529a7d2c68@usma1ex-dag1mb5.msg.corp.akamai.com>
References: <20180510180509.GA2505@ubuntu-dmitri> <SN1PR08MB18543D4C234CC672616E37BFDA980@SN1PR08MB1854.namprd08.prod.outlook.com> <20180510184505.GA23837@ubuntu-dmitri>, <DM5PR2101MB090184FC657942BD294E555DB3980@DM5PR2101MB0901.namprd21.prod.outlook.com> <BY2PR15MB0775E5FA5E6869C85AB98933CD980@BY2PR15MB0775.namprd15.prod.outlook.com>
In-Reply-To: <BY2PR15MB0775E5FA5E6869C85AB98933CD980@BY2PR15MB0775.namprd15.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.34.240]
Content-Type: multipart/alternative; boundary="_000_c0b4cd48aa5f491f91828d529a7d2c68usma1exdag1mb5msgcorpak_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-10_06:, , 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=635 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805100201
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-10_06:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=574 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805100201
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/XmLmnIvhJVp9rdsovbn1zCZ58v0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 10 May 2018 21:58:35 -0000

--_000_c0b4cd48aa5f491f91828d529a7d2c68usma1exdag1mb5msgcorpak_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Actually, I'll take an issue with:

[draft-ietf-quic-transport-11] says the following:
    A stream frame's Stream Data MUST NOT be empty, unless the offset is
    0 or the FIN bit is set.

Why disallow this?  This may be a signal to the receiver about where in the=
 stream the sender is, even if the sender does not have any new data to sen=
d.  This signal may be useful in cases of packet loss, when the sender is n=
ot ready to declare a packet with stream data lost and retransmit lots of s=
tream data (has not been long enough), but it is very important for the app=
lication to know where the sender is in the stream.  Of course, there are w=
orkarounds - you can send a STREAM frame, retransmitting a single byte.  Bu=
t it still seems like an unnecessary restriction.


  *   Igor


From: Roberto Peon [mailto:fenix@fb.com]
Sent: Thursday, May 10, 2018 3:12 PM
To: Nick Banks <nibanks=3D40microsoft.com@dmarc.ietf.org>; Dmitri Tikhonov =
<dtikhonov@litespeedtech.com>; Mike Bishop <mbishop@evequefou.be>
Cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Why allow empty STREAM frames when offset is zero?

It can be used to establish the mapping of the stream (src-conn-id:streamid=
 <-> dst-conn-id:streamid) through the stack of proxies, etc, especially fo=
r usecases where there is an early response.

-=3DR



Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone


-------- Original message --------
From: Nick Banks <nibanks=3D40microsoft.com@dmarc.ietf.org<mailto:nibanks=
=3D40microsoft.com@dmarc.ietf.org>>
Date: 5/10/18 12:02 PM (GMT-08:00)
To: Dmitri Tikhonov <dtikhonov@litespeedtech.com<mailto:dtikhonov@litespeed=
tech.com>>, Mike Bishop <mbishop@evequefou.be<mailto:mbishop@evequefou.be>>
Cc: IETF QUIC WG <quic@ietf.org<mailto:quic@ietf.org>>
Subject: RE: Why allow empty STREAM frames when offset is zero?

In WinQuic, the resulting frame just results in the NEW_STREAM event to the=
 application layer. They can start reading from it, but we just won't have =
anything to read yet. That NEW_STREAM event can be used for a number of thi=
ngs. If you are moving from multiple TCP connections to a single QUIC conne=
ction, it could be seen as the equivalent of a single TCP connect event.

- Nick

-----Original Message-----
From: QUIC <quic-bounces@ietf.org<mailto:quic-bounces@ietf.org>> On Behalf =
Of Dmitri Tikhonov
Sent: Thursday, May 10, 2018 11:45 AM
To: Mike Bishop <mbishop@evequefou.be<mailto:mbishop@evequefou.be>>
Cc: IETF QUIC WG <quic@ietf.org<mailto:quic@ietf.org>>
Subject: Re: Why allow empty STREAM frames when offset is zero?

Is there a real-life use case that is implied here?  I can't see why it wou=
ld be useful.

On the other hand, it creates an odd situation for an implementation:
a frame has arrived, yet the higher layer cannot read from it yet, so an in=
coming stream is unreadable.

On Thu, May 10, 2018 at 06:25:55PM +0000, Mike Bishop wrote:
> If you want to open a stream (e.g. permit data to be sent in the opposite=
 direction of a bidirectional stream), but don't actually have data ready t=
o send yet.
>
> -----Original Message-----
> From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of Dmitri Tikhonov
> Sent: Thursday, May 10, 2018 11:05 AM
> To: IETF QUIC WG <quic@ietf.org<mailto:quic@ietf.org>>
> Subject: Why allow empty STREAM frames when offset is zero?
>
> [draft-ietf-quic-transport-11] says the following:
>
>    A stream frame's Stream Data MUST NOT be empty, unless the offset is
>    0 or the FIN bit is set.
>
> Why allow empty STREAM frames when the offset is zero?  What is the purpo=
se?
>
>   - Dmitri.
>

--_000_c0b4cd48aa5f491f91828d529a7d2c68usma1exdag1mb5msgcorpak_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
p.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	border:none;
	padding:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:104621069;
	mso-list-type:hybrid;
	mso-list-template-ids:457466904 -963485458 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Actually, I&#8217;ll take an issue with:<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">[draft-ietf-quic-transport-11] says the following:<b=
r>
&nbsp;&nbsp;&nbsp; A stream frame's Stream Data MUST NOT be empty, unless t=
he offset is<br>
&nbsp;&nbsp;&nbsp; 0 or the FIN bit is set.<br>
<br>
<o:p></o:p></p>
<p class=3D"MsoNormal">Why disallow this?&nbsp; This may be a signal to the=
 receiver about where in the stream the sender is, even if the sender does =
not have any new data to send.&nbsp; This signal may be useful in cases of =
packet loss, when the sender is not ready to
 declare a packet with stream data lost and retransmit lots of stream data =
(has not been long enough), but it is very important for the application to=
 know where the sender is in the stream.&nbsp; Of course, there are workaro=
unds &#8211; you can send a STREAM frame, retransmitting
 a single byte.&nbsp; But it still seems like an unnecessary restriction.<o=
:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l0 level1 =
lfo1">Igor<o:p></o:p></li></ul>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Roberto Peon [mailto:fenix@fb.com] <br>
<b>Sent:</b> Thursday, May 10, 2018 3:12 PM<br>
<b>To:</b> Nick Banks &lt;nibanks=3D40microsoft.com@dmarc.ietf.org&gt;; Dmi=
tri Tikhonov &lt;dtikhonov@litespeedtech.com&gt;; Mike Bishop &lt;mbishop@e=
vequefou.be&gt;<br>
<b>Cc:</b> IETF QUIC WG &lt;quic@ietf.org&gt;<br>
<b>Subject:</b> Re: Why allow empty STREAM frames when offset is zero?<o:p>=
</o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal">It can be used to establish the mapping of the strea=
m (src-conn-id:streamid &lt;-&gt; dst-conn-id:streamid) through the stack o=
f proxies, etc, especially for usecases where there is an early response.&n=
bsp;<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">-=3DR<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div id=3D"x_composer_signature">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.5pt;color:#575757">Sent v=
ia the Samsung Galaxy S7, an AT&amp;T 4G LTE smartphone<o:p></o:p></span></=
p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">-------- Original message --------<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">From: Nick Banks &lt;<a href=3D"mailto:nibanks=3D40m=
icrosoft.com@dmarc.ietf.org">nibanks=3D40microsoft.com@dmarc.ietf.org</a>&g=
t;
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Date: 5/10/18 12:02 PM (GMT-08:00) <o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">To: Dmitri Tikhonov &lt;<a href=3D"mailto:dtikhonov@=
litespeedtech.com">dtikhonov@litespeedtech.com</a>&gt;, Mike Bishop &lt;<a =
href=3D"mailto:mbishop@evequefou.be">mbishop@evequefou.be</a>&gt;
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Cc: IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org=
">quic@ietf.org</a>&gt;
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Subject: RE: Why allow empty STREAM frames when offs=
et is zero?
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">In WinQuic, the resul=
ting frame just results in the NEW_STREAM event to the application layer. T=
hey can start reading from it, but we just won't have anything to read yet.=
 That NEW_STREAM event can be used for
 a number of things. If you are moving from multiple TCP connections to a s=
ingle QUIC connection, it could be seen as the equivalent of a single TCP c=
onnect event.<br>
<br>
- Nick<br>
<br>
-----Original Message-----<br>
From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org">quic-bounces@ietf.o=
rg</a>&gt; On Behalf Of Dmitri Tikhonov<br>
Sent: Thursday, May 10, 2018 11:45 AM<br>
To: Mike Bishop &lt;<a href=3D"mailto:mbishop@evequefou.be">mbishop@evequef=
ou.be</a>&gt;<br>
Cc: IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org">quic@ietf.org</a>&gt;=
<br>
Subject: Re: Why allow empty STREAM frames when offset is zero?<br>
<br>
Is there a real-life use case that is implied here?&nbsp; I can't see why i=
t would be useful.<br>
<br>
On the other hand, it creates an odd situation for an implementation:<br>
a frame has arrived, yet the higher layer cannot read from it yet, so an in=
coming stream is unreadable.<br>
<br>
On Thu, May 10, 2018 at 06:25:55PM &#43;0000, Mike Bishop wrote:<br>
&gt; If you want to open a stream (e.g. permit data to be sent in the oppos=
ite direction of a bidirectional stream), but don't actually have data read=
y to send yet.<br>
&gt; <br>
&gt; -----Original Message-----<br>
&gt; From: QUIC [<a href=3D"mailto:quic-bounces@ietf.org">mailto:quic-bounc=
es@ietf.org</a>] On Behalf Of Dmitri Tikhonov<br>
&gt; Sent: Thursday, May 10, 2018 11:05 AM<br>
&gt; To: IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org">quic@ietf.org</a=
>&gt;<br>
&gt; Subject: Why allow empty STREAM frames when offset is zero?<br>
&gt; <br>
&gt; [draft-ietf-quic-transport-11] says the following:<br>
&gt; <br>
&gt;&nbsp;&nbsp;&nbsp; A stream frame's Stream Data MUST NOT be empty, unle=
ss the offset is<br>
&gt;&nbsp;&nbsp;&nbsp; 0 or the FIN bit is set.<br>
&gt; <br>
&gt; Why allow empty STREAM frames when the offset is zero?&nbsp; What is t=
he purpose?<br>
&gt; <br>
&gt;&nbsp;&nbsp; - Dmitri.<br>
&gt; <o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_c0b4cd48aa5f491f91828d529a7d2c68usma1exdag1mb5msgcorpak_--


From nobody Thu May 10 17:11:19 2018
Return-Path: <ianswett@google.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9E8FE12DA1A for <quic@ietfa.amsl.com>; Thu, 10 May 2018 17:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.509
X-Spam-Level: 
X-Spam-Status: No, score=-17.509 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 yTNdCjEpSIbc for <quic@ietfa.amsl.com>; Thu, 10 May 2018 17:11:16 -0700 (PDT)
Received: from mail-yb0-x233.google.com (mail-yb0-x233.google.com [IPv6:2607:f8b0:4002:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E66612D7E6 for <quic@ietf.org>; Thu, 10 May 2018 17:11:16 -0700 (PDT)
Received: by mail-yb0-x233.google.com with SMTP id j143-v6so1270171ybg.2 for <quic@ietf.org>; Thu, 10 May 2018 17:11:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lYs1jsG5BewT9d5EqDaLkHZrfc/+w2ruQJ+cmVIodpE=; b=BlbWeYgk4kYSvv1VoCCirpSc4nOBh0aslXZZGq/9jQXj3cB05OUnzV5VFgN65z5su1 lOHjc3zCAJOtatBP6tbN80WGnDx9kpUjpBMCuncPpa3l8r9xVWXvYNGThYSultNkXf60 3U4C3OLfXOmuav0Ymo6gcPaRO2jE91B5AYpo5Kngb5dei4Q/PSQ78Rq9VtPreudr00Sw i36Pny49OPoL0PuUWJVz44j6rpDfQTjW72HeTRlJDWFb+5+FMZETHZYLtDlOV1gTFoDf RXIYHLTYRYKr3mvg3kD+vKMoELm6cRJDqbXTNZYHvmI2y1JPnazXupNuutqenYMS3csw fz7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lYs1jsG5BewT9d5EqDaLkHZrfc/+w2ruQJ+cmVIodpE=; b=rcq5yNaKqbEvdyiyrcTUg8OV0gzW8sslXqBguMBkjTzeG1CgpYaWyi5hOQZkq4YkSk AP/CM7gVouAO0WDR2I1q95Ox86YxoagpNreUak5VxNF/nIQVkffh4avHxviyj4ylZ/g3 OTW7VSVjmJVziTbMPvRKroYhjGBQc0uiB7u8jmhRSC6jYStBVod+jyn69P6kR6RkRXp7 z3KUQNigRNHEenQHvmftj4fTDaKTt31GEGzhK6I0aW4ILvrDf5882F1EWdXuz5WsWUwH uJwBuY+RR4B1hrqMzOSplLRJoYao4fJuUYpn0aFVJHarqGofU0xsmbMYjBlDBH3NHak1 30EQ==
X-Gm-Message-State: ALKqPwcOBqO3ZD1jakEwYxrbSEZUlXtG+JkMTR1Z2By4YBGe7VYpzj43 jJ3f1eZxCIelMTTKXJqKlw6MiIfpGmOyIA6GdJg6eA==
X-Google-Smtp-Source: AB8JxZoxTljnsgkSpyE9ggLVZTE4dIi1sxV8Dwg5aQ4LPmZ276cIwFTzSrLPGEZaKwcf3PeRbHpq2sjiDsQkTwe6qOA=
X-Received: by 2002:a25:386:: with SMTP id 128-v6mr50019ybd.241.1525997475328;  Thu, 10 May 2018 17:11:15 -0700 (PDT)
MIME-Version: 1.0
References: <20180510180509.GA2505@ubuntu-dmitri> <SN1PR08MB18543D4C234CC672616E37BFDA980@SN1PR08MB1854.namprd08.prod.outlook.com> <20180510184505.GA23837@ubuntu-dmitri> <DM5PR2101MB090184FC657942BD294E555DB3980@DM5PR2101MB0901.namprd21.prod.outlook.com> <BY2PR15MB0775E5FA5E6869C85AB98933CD980@BY2PR15MB0775.namprd15.prod.outlook.com> <c0b4cd48aa5f491f91828d529a7d2c68@usma1ex-dag1mb5.msg.corp.akamai.com>
In-Reply-To: <c0b4cd48aa5f491f91828d529a7d2c68@usma1ex-dag1mb5.msg.corp.akamai.com>
From: Ian Swett <ianswett@google.com>
Date: Fri, 11 May 2018 00:11:03 +0000
Message-ID: <CAKcm_gNgYUhvu6g_TVqP-gVwA0e__hqK7bGbNs_JnumvyaQeqQ@mail.gmail.com>
Subject: Re: Why allow empty STREAM frames when offset is zero?
To: ilubashe=40akamai.com@dmarc.ietf.org
Cc: Roberto Peon <fenix@fb.com>, nibanks=40microsoft.com@dmarc.ietf.org,  Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Mike Bishop <mbishop@evequefou.be>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007284f5056be2f9ff"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/RTAmL0tglAU0Ogs5rn7QeojZN5k>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 May 2018 00:11:18 -0000

--0000000000007284f5056be2f9ff
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I would agree that the restriction here seem unnecessary and I tend to
think we'd be better off removing it.

On Thu, May 10, 2018 at 5:58 PM Lubashev, Igor <ilubashe=3D
40akamai.com@dmarc.ietf.org> wrote:

> Actually, I=E2=80=99ll take an issue with:
>
>
>
> [draft-ietf-quic-transport-11] says the following:
>     A stream frame's Stream Data MUST NOT be empty, unless the offset is
>     0 or the FIN bit is set.
>
> Why disallow this?  This may be a signal to the receiver about where in
> the stream the sender is, even if the sender does not have any new data t=
o
> send.  This signal may be useful in cases of packet loss, when the sender
> is not ready to declare a packet with stream data lost and retransmit lot=
s
> of stream data (has not been long enough), but it is very important for t=
he
> application to know where the sender is in the stream.  Of course, there
> are workarounds =E2=80=93 you can send a STREAM frame, retransmitting a s=
ingle
> byte.  But it still seems like an unnecessary restriction.
>
>
>
>    - Igor
>
>
>
>
>
> *From:* Roberto Peon [mailto:fenix@fb.com]
> *Sent:* Thursday, May 10, 2018 3:12 PM
> *To:* Nick Banks <nibanks=3D40microsoft.com@dmarc.ietf.org>; Dmitri
> Tikhonov <dtikhonov@litespeedtech.com>; Mike Bishop <mbishop@evequefou.be=
>
> *Cc:* IETF QUIC WG <quic@ietf.org>
> *Subject:* Re: Why allow empty STREAM frames when offset is zero?
>
>
>
> It can be used to establish the mapping of the stream
> (src-conn-id:streamid <-> dst-conn-id:streamid) through the stack of
> proxies, etc, especially for usecases where there is an early response.
>
>
>
> -=3DR
>
>
>
>
>
>
>
> Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
>
>
>
>
>
> -------- Original message --------
>
> From: Nick Banks <nibanks=3D40microsoft.com@dmarc.ietf.org>
>
> Date: 5/10/18 12:02 PM (GMT-08:00)
>
> To: Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Mike Bishop <
> mbishop@evequefou.be>
>
> Cc: IETF QUIC WG <quic@ietf.org>
>
> Subject: RE: Why allow empty STREAM frames when offset is zero?
>
>
>
> In WinQuic, the resulting frame just results in the NEW_STREAM event to
> the application layer. They can start reading from it, but we just won't
> have anything to read yet. That NEW_STREAM event can be used for a number
> of things. If you are moving from multiple TCP connections to a single QU=
IC
> connection, it could be seen as the equivalent of a single TCP connect
> event.
>
> - Nick
>
> -----Original Message-----
> From: QUIC <quic-bounces@ietf.org> On Behalf Of Dmitri Tikhonov
> Sent: Thursday, May 10, 2018 11:45 AM
> To: Mike Bishop <mbishop@evequefou.be>
> Cc: IETF QUIC WG <quic@ietf.org>
> Subject: Re: Why allow empty STREAM frames when offset is zero?
>
> Is there a real-life use case that is implied here?  I can't see why it
> would be useful.
>
> On the other hand, it creates an odd situation for an implementation:
> a frame has arrived, yet the higher layer cannot read from it yet, so an
> incoming stream is unreadable.
>
> On Thu, May 10, 2018 at 06:25:55PM +0000, Mike Bishop wrote:
> > If you want to open a stream (e.g. permit data to be sent in the
> opposite direction of a bidirectional stream), but don't actually have da=
ta
> ready to send yet.
> >
> > -----Original Message-----
> > From: QUIC [mailto:quic-bounces@ietf.org <quic-bounces@ietf.org>] On
> Behalf Of Dmitri Tikhonov
> > Sent: Thursday, May 10, 2018 11:05 AM
> > To: IETF QUIC WG <quic@ietf.org>
> > Subject: Why allow empty STREAM frames when offset is zero?
> >
> > [draft-ietf-quic-transport-11] says the following:
> >
> >    A stream frame's Stream Data MUST NOT be empty, unless the offset is
> >    0 or the FIN bit is set.
> >
> > Why allow empty STREAM frames when the offset is zero?  What is the
> purpose?
> >
> >   - Dmitri.
> >
>

--0000000000007284f5056be2f9ff
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I would agree that the restriction here seem unnecessary a=
nd I tend to think we&#39;d be better off removing it.</div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr">On Thu, May 10, 2018 at 5:58 PM Lubashev,=
 Igor &lt;ilubashe=3D<a href=3D"mailto:40akamai.com@dmarc.ietf.org">40akama=
i.com@dmarc.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"=
>





<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"m_-6264302616729601548WordSection1">
<p class=3D"MsoNormal">Actually, I=E2=80=99ll take an issue with:<u></u><u>=
</u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">[draft-ietf-quic-transport-11] says the following:<b=
r>
=C2=A0=C2=A0=C2=A0 A stream frame&#39;s Stream Data MUST NOT be empty, unle=
ss the offset is<br>
=C2=A0=C2=A0=C2=A0 0 or the FIN bit is set.<br>
<br>
<u></u><u></u></p>
<p class=3D"MsoNormal">Why disallow this?=C2=A0 This may be a signal to the=
 receiver about where in the stream the sender is, even if the sender does =
not have any new data to send.=C2=A0 This signal may be useful in cases of =
packet loss, when the sender is not ready to
 declare a packet with stream data lost and retransmit lots of stream data =
(has not been long enough), but it is very important for the application to=
 know where the sender is in the stream.=C2=A0 Of course, there are workaro=
unds =E2=80=93 you can send a STREAM frame, retransmitting
 a single byte.=C2=A0 But it still seems like an unnecessary restriction.<u=
></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"m_-6264302616729601548MsoListParagraph" style=3D"margin-left:0=
in">Igor<u></u><u></u></li></ul>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Roberto Peon [mailto:<a href=3D"mailto:=
fenix@fb.com" target=3D"_blank">fenix@fb.com</a>] <br>
<b>Sent:</b> Thursday, May 10, 2018 3:12 PM<br>
<b>To:</b> Nick Banks &lt;nibanks=3D<a href=3D"mailto:40microsoft.com@dmarc=
.ietf.org" target=3D"_blank">40microsoft.com@dmarc.ietf.org</a>&gt;; Dmitri=
 Tikhonov &lt;<a href=3D"mailto:dtikhonov@litespeedtech.com" target=3D"_bla=
nk">dtikhonov@litespeedtech.com</a>&gt;; Mike Bishop &lt;<a href=3D"mailto:=
mbishop@evequefou.be" target=3D"_blank">mbishop@evequefou.be</a>&gt;<br>
<b>Cc:</b> IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_bla=
nk">quic@ietf.org</a>&gt;<br>
<b>Subject:</b> Re: Why allow empty STREAM frames when offset is zero?<u></=
u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">It can be used to establish the mapping of the strea=
m (src-conn-id:streamid &lt;-&gt; dst-conn-id:streamid) through the stack o=
f proxies, etc, especially for usecases where there is an early response.=
=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-=3DR<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div id=3D"m_-6264302616729601548x_composer_signature">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.5pt;color:#575757">Sent v=
ia the Samsung Galaxy S7, an AT&amp;T 4G LTE smartphone<u></u><u></u></span=
></p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">-------- Original message --------<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">From: Nick Banks &lt;<a href=3D"mailto:nibanks=3D40m=
icrosoft.com@dmarc.ietf.org" target=3D"_blank">nibanks=3D40microsoft.com@dm=
arc.ietf.org</a>&gt;
<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Date: 5/10/18 12:02 PM (GMT-08:00) <u></u><u></u></p=
>
</div>
<div>
<p class=3D"MsoNormal">To: Dmitri Tikhonov &lt;<a href=3D"mailto:dtikhonov@=
litespeedtech.com" target=3D"_blank">dtikhonov@litespeedtech.com</a>&gt;, M=
ike Bishop &lt;<a href=3D"mailto:mbishop@evequefou.be" target=3D"_blank">mb=
ishop@evequefou.be</a>&gt;
<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Cc: IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org=
" target=3D"_blank">quic@ietf.org</a>&gt;
<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Subject: RE: Why allow empty STREAM frames when offs=
et is zero?
<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">In WinQuic, the resul=
ting frame just results in the NEW_STREAM event to the application layer. T=
hey can start reading from it, but we just won&#39;t have anything to read =
yet. That NEW_STREAM event can be used for
 a number of things. If you are moving from multiple TCP connections to a s=
ingle QUIC connection, it could be seen as the equivalent of a single TCP c=
onnect event.<br>
<br>
- Nick<br>
<br>
-----Original Message-----<br>
From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_blank">q=
uic-bounces@ietf.org</a>&gt; On Behalf Of Dmitri Tikhonov<br>
Sent: Thursday, May 10, 2018 11:45 AM<br>
To: Mike Bishop &lt;<a href=3D"mailto:mbishop@evequefou.be" target=3D"_blan=
k">mbishop@evequefou.be</a>&gt;<br>
Cc: IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">qui=
c@ietf.org</a>&gt;<br>
Subject: Re: Why allow empty STREAM frames when offset is zero?<br>
<br>
Is there a real-life use case that is implied here?=C2=A0 I can&#39;t see w=
hy it would be useful.<br>
<br>
On the other hand, it creates an odd situation for an implementation:<br>
a frame has arrived, yet the higher layer cannot read from it yet, so an in=
coming stream is unreadable.<br>
<br>
On Thu, May 10, 2018 at 06:25:55PM +0000, Mike Bishop wrote:<br>
&gt; If you want to open a stream (e.g. permit data to be sent in the oppos=
ite direction of a bidirectional stream), but don&#39;t actually have data =
ready to send yet.<br>
&gt; <br>
&gt; -----Original Message-----<br>
&gt; From: QUIC [<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_blank"=
>mailto:quic-bounces@ietf.org</a>] On Behalf Of Dmitri Tikhonov<br>
&gt; Sent: Thursday, May 10, 2018 11:05 AM<br>
&gt; To: IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank=
">quic@ietf.org</a>&gt;<br>
&gt; Subject: Why allow empty STREAM frames when offset is zero?<br>
&gt; <br>
&gt; [draft-ietf-quic-transport-11] says the following:<br>
&gt; <br>
&gt;=C2=A0=C2=A0=C2=A0 A stream frame&#39;s Stream Data MUST NOT be empty, =
unless the offset is<br>
&gt;=C2=A0=C2=A0=C2=A0 0 or the FIN bit is set.<br>
&gt; <br>
&gt; Why allow empty STREAM frames when the offset is zero?=C2=A0 What is t=
he purpose?<br>
&gt; <br>
&gt;=C2=A0=C2=A0 - Dmitri.<br>
&gt; <u></u><u></u></p>
</div>
</div>
</div>

</blockquote></div>

--0000000000007284f5056be2f9ff--


From nobody Thu May 10 17:37:34 2018
Return-Path: <martin.thomson@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C456912EBC2 for <quic@ietfa.amsl.com>; Thu, 10 May 2018 17:37:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 3co7MHfUsjOW for <quic@ietfa.amsl.com>; Thu, 10 May 2018 17:37:30 -0700 (PDT)
Received: from mail-oi0-x233.google.com (mail-oi0-x233.google.com [IPv6:2607:f8b0:4003:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AE8B612EBB9 for <quic@ietf.org>; Thu, 10 May 2018 17:37:30 -0700 (PDT)
Received: by mail-oi0-x233.google.com with SMTP id n65-v6so3367206oig.6 for <quic@ietf.org>; Thu, 10 May 2018 17:37:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=xaaRbHgAbZBpseQyvV6AT07Io4q412CCNJM53NZibZk=; b=iyCKF7B/ImcwBePN6LWKTfm9OszHypXDmdk88Fq623bfhoylwf5+gQ53cXQ5qO1Ory IjYfiQNy6n03rquHwZnDxDhJ7+CJB4xB3B+OgVRqb20+hH6Z412yY/EsmUJEzUFld+rN a2zEk0quSq4Ft93pWeTIfjJP27B389u4BPmnOZMsdCAXrgBy7mZvCT2JLiov0EnVzjWP zjXz2FaTsIvqoexuEQPLOOXtcZ1cLqMnNwEVQfRF3gcLnHQereAVaJkN/ofKPHnlBLCb h7GRhz1ew0PrVDEFB6nKVJsNXlycZFlSLrnu2YfmIIeluIeWe6WEB0qHmaRfEfucJZ2a bzRg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=xaaRbHgAbZBpseQyvV6AT07Io4q412CCNJM53NZibZk=; b=TezesuM1/Csixf60a/B7G4vQEvGK+cTD7veEL90ys/NsYcTavA94pXUV49WrmFom8V +CPachGDnY8NdEMtKsgTVJCe5Gexhu68pinDU5NHjI6TGqV74xP3SunQSZofYd4PkhQ1 wScBqChlEfD/k0pNzX0jc3femsNl27pEQmOSk7Dd4BPpG+nJR6GIufyM74K4bfvodp/X aL7pDq/XIWQdluYkVyVNqRvNczoUdmjozwZssObgrr4wt4B1614mGMeBZrKgTcJYjXCq TUp/5OYkW6wwj6hpmJtTOsfIHQPJscMrWC3ee0nnUI0NJDvUcdPyEMjhPCeAuDMdrY+N ZTiQ==
X-Gm-Message-State: ALKqPwcAX7/9E8nxzz+kiKoMno7Um7MFy5wbXNCw1q6wj3wI9W3l3K69 9wTLToLLrtw3QmuXouir61bwKTjYudKMlJa4KVGsSw==
X-Google-Smtp-Source: AB8JxZr8E1PC6ZpZreYIkRIUd4hOeVWHxBSmsPerZeh6eExeUuFjMlI4NtgKFT+EqfzPRe94EFsbJ0jTtMvg0MKbK8k=
X-Received: by 2002:aca:1218:: with SMTP id 24-v6mr1992521ois.144.1525999049929;  Thu, 10 May 2018 17:37:29 -0700 (PDT)
MIME-Version: 1.0
References: <20180510180509.GA2505@ubuntu-dmitri> <SN1PR08MB18543D4C234CC672616E37BFDA980@SN1PR08MB1854.namprd08.prod.outlook.com> <20180510184505.GA23837@ubuntu-dmitri> <DM5PR2101MB090184FC657942BD294E555DB3980@DM5PR2101MB0901.namprd21.prod.outlook.com> <BY2PR15MB0775E5FA5E6869C85AB98933CD980@BY2PR15MB0775.namprd15.prod.outlook.com> <c0b4cd48aa5f491f91828d529a7d2c68@usma1ex-dag1mb5.msg.corp.akamai.com> <CAKcm_gNgYUhvu6g_TVqP-gVwA0e__hqK7bGbNs_JnumvyaQeqQ@mail.gmail.com>
In-Reply-To: <CAKcm_gNgYUhvu6g_TVqP-gVwA0e__hqK7bGbNs_JnumvyaQeqQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 11 May 2018 10:37:23 +1000
Message-ID: <CABkgnnWZHcVaRzEmG5QwZCFUOXE8khyHbf8Hav=RZQHiDdsOfQ@mail.gmail.com>
Subject: Re: Why allow empty STREAM frames when offset is zero?
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Cc: "Lubashev, Igor" <ilubashe=40akamai.com@dmarc.ietf.org>,  Nick Banks <nibanks=40microsoft.com@dmarc.ietf.org>, Mike Bishop <mbishop@evequefou.be>,  Roberto Peon <fenix@fb.com>, QUIC WG <quic@ietf.org>,  Dmitri Tikhonov <dtikhonov@litespeedtech.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/VJ-WC-xP6YsTKlp1o4h36Rl94qU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 May 2018 00:37:33 -0000

That's possible, if someone wants to open a PR.

To be clear, I don't think that there is a valid use case for an empty
STREAM frame (other than at the start or end) that isn't satisfied better
by other frames.  But we're not necessarily in the business of policing
these things and allowing empty STREAM frames is actually easier than
creating the exclusions.

Here's a use case: steganography.  A covert channel to the peer that won't
manifest as observable activity outside of the QUIC stack.  An empty STREAM
frame can carry a surprising amount of entropy if you are clever.

We would then put empty STREAM frames in the same bucket as other frames
that could be pointless and wasteful when used excessively.  There's
already a bunch of those.
On Fri, May 11, 2018 at 10:11 AM Ian Swett <ianswett=3D
40google.com@dmarc.ietf.org> wrote:

> I would agree that the restriction here seem unnecessary and I tend to
think we'd be better off removing it.

> On Thu, May 10, 2018 at 5:58 PM Lubashev, Igor <ilubashe=3D
40akamai.com@dmarc.ietf.org> wrote:

>> Actually, I=E2=80=99ll take an issue with:



>> [draft-ietf-quic-transport-11] says the following:
>>      A stream frame's Stream Data MUST NOT be empty, unless the offset i=
s
>>      0 or the FIN bit is set.

>> Why disallow this?  This may be a signal to the receiver about where in
the stream the sender is, even if the sender does not have any new data to
send.  This signal may be useful in cases of packet loss, when the sender
is not ready to declare a packet with stream data lost and retransmit lots
of stream data (has not been long enough), but it is very important for the
application to know where the sender is in the stream.  Of course, there
are workarounds =E2=80=93 you can send a STREAM frame, retransmitting a sin=
gle
byte.  But it still seems like an unnecessary restriction.



>> Igor





>> From: Roberto Peon [mailto:fenix@fb.com]
>> Sent: Thursday, May 10, 2018 3:12 PM
>> To: Nick Banks <nibanks=3D40microsoft.com@dmarc.ietf.org>; Dmitri Tikhon=
ov
<dtikhonov@litespeedtech.com>; Mike Bishop <mbishop@evequefou.be>
>> Cc: IETF QUIC WG <quic@ietf.org>
>> Subject: Re: Why allow empty STREAM frames when offset is zero?



>> It can be used to establish the mapping of the stream
(src-conn-id:streamid <-> dst-conn-id:streamid) through the stack of
proxies, etc, especially for usecases where there is an early response.



>> -=3DR







>> Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone





>> -------- Original message --------

>> From: Nick Banks <nibanks=3D40microsoft.com@dmarc.ietf.org>

>> Date: 5/10/18 12:02 PM (GMT-08:00)

>> To: Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Mike Bishop <
mbishop@evequefou.be>

>> Cc: IETF QUIC WG <quic@ietf.org>

>> Subject: RE: Why allow empty STREAM frames when offset is zero?



>> In WinQuic, the resulting frame just results in the NEW_STREAM event to
the application layer. They can start reading from it, but we just won't
have anything to read yet. That NEW_STREAM event can be used for a number
of things. If you are moving from multiple TCP connections to a single QUIC
connection, it could be seen as the equivalent of a single TCP connect
event.

>> - Nick

>> -----Original Message-----
>> From: QUIC <quic-bounces@ietf.org> On Behalf Of Dmitri Tikhonov
>> Sent: Thursday, May 10, 2018 11:45 AM
>> To: Mike Bishop <mbishop@evequefou.be>
>> Cc: IETF QUIC WG <quic@ietf.org>
>> Subject: Re: Why allow empty STREAM frames when offset is zero?

>> Is there a real-life use case that is implied here?  I can't see why it
would be useful.

>> On the other hand, it creates an odd situation for an implementation:
>> a frame has arrived, yet the higher layer cannot read from it yet, so an
incoming stream is unreadable.

>> On Thu, May 10, 2018 at 06:25:55PM +0000, Mike Bishop wrote:
>> > If you want to open a stream (e.g. permit data to be sent in the
opposite direction of a bidirectional stream), but don't actually have data
ready to send yet.
>> >
>> > -----Original Message-----
>> > From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of Dmitri Tikhonov
>> > Sent: Thursday, May 10, 2018 11:05 AM
>> > To: IETF QUIC WG <quic@ietf.org>
>> > Subject: Why allow empty STREAM frames when offset is zero?
>> >
>> > [draft-ietf-quic-transport-11] says the following:
>> >
>> >    A stream frame's Stream Data MUST NOT be empty, unless the offset i=
s
>> >    0 or the FIN bit is set.
>> >
>> > Why allow empty STREAM frames when the offset is zero?  What is the
purpose?
>> >
>> >   - Dmitri.
>> >


From nobody Thu May 10 18:28:07 2018
Return-Path: <ilubashe@akamai.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4724612E85B for <quic@ietfa.amsl.com>; Thu, 10 May 2018 18:28:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.711
X-Spam-Level: 
X-Spam-Status: No, score=-2.711 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 YcFHH3KtAmkg for <quic@ietfa.amsl.com>; Thu, 10 May 2018 18:28:03 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::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 31CAF12426E for <quic@ietf.org>; Thu, 10 May 2018 18:28:03 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.22/8.16.0.22) with SMTP id w4B1ReSF012147; Fri, 11 May 2018 02:27:55 +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 : content-transfer-encoding : mime-version; s=jan2016.eng; bh=c8hZUYIP9kDX+bJPBhYaeDQ9yWTrE1K/+ff09ymD+0A=; b=S3xg1ZiTvZR1F1jaYIbxjGBeDKlNCfDtDkq3sxpXEb+X2ilwJr0ubo54x6LYTPEtLkCZ 0KdO1//QFwf42aMzHm5IhekUDRGCLUt6uKrNyOfk4KivpCPU38JlwYPST+aqLQUzN+kH b1SQSOw0hJUY6ikm2ws93Tqmq2jCkPhuO3GELuL4hnci+5mXOz5TZ1AmrUVRPe92IONr pMRVqNHDkm1dEecza+vfl3W9J/cXzb/oJwAsFyMHylVggJK610j2WJBHkvwpWPov4WMg TbuekEBH9lSUiSl8axKJfo2kp/G/3a+vIxX8JmF22fwcDccOZlpKJk5o/rrp+6th61yC RQ== 
Received: from prod-mail-ppoint4 ([96.6.114.87]) by m0050102.ppops.net-00190b01. with ESMTP id 2hvwmk0h65-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 11 May 2018 02:27:55 +0100
Received: from pps.filterd (prod-mail-ppoint4.akamai.com [127.0.0.1]) by prod-mail-ppoint4.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w4B1R7M9002028; Thu, 10 May 2018 21:27:54 -0400
Received: from email.msg.corp.akamai.com ([172.27.123.53]) by prod-mail-ppoint4.akamai.com with ESMTP id 2hs7xwnnku-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 10 May 2018 21:27:53 -0400
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com (172.27.123.105) by usma1ex-dag1mb2.msg.corp.akamai.com (172.27.123.102) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Thu, 10 May 2018 21:27:48 -0400
Received: from USMA1EX-DAG1MB5.msg.corp.akamai.com ([172.27.123.105]) by usma1ex-dag1mb5.msg.corp.akamai.com ([172.27.123.105]) with mapi id 15.00.1365.000; Thu, 10 May 2018 21:27:48 -0400
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: Martin Thomson <martin.thomson@gmail.com>, Ian Swett <ianswett@google.com>
CC: Nick Banks <nibanks@microsoft.com>, Mike Bishop <mbishop@evequefou.be>, Roberto Peon <fenix@fb.com>, QUIC WG <quic@ietf.org>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>
Subject: RE: Why allow empty STREAM frames when offset is zero?
Thread-Topic: Why allow empty STREAM frames when offset is zero?
Thread-Index: AQHT6ImJSKTfLtwgAkSWTEz8kX9aw6QpiqWAgAAFW4CAAATBAIAAAq8A///p/YCAAGmmgIAAB1yA///KuaA=
Date: Fri, 11 May 2018 01:27:48 +0000
Message-ID: <1c9ddb102f854ed890c0e4d9f2a0724e@usma1ex-dag1mb5.msg.corp.akamai.com>
References: <20180510180509.GA2505@ubuntu-dmitri> <SN1PR08MB18543D4C234CC672616E37BFDA980@SN1PR08MB1854.namprd08.prod.outlook.com> <20180510184505.GA23837@ubuntu-dmitri> <DM5PR2101MB090184FC657942BD294E555DB3980@DM5PR2101MB0901.namprd21.prod.outlook.com> <BY2PR15MB0775E5FA5E6869C85AB98933CD980@BY2PR15MB0775.namprd15.prod.outlook.com> <c0b4cd48aa5f491f91828d529a7d2c68@usma1ex-dag1mb5.msg.corp.akamai.com> <CAKcm_gNgYUhvu6g_TVqP-gVwA0e__hqK7bGbNs_JnumvyaQeqQ@mail.gmail.com> <CABkgnnWZHcVaRzEmG5QwZCFUOXE8khyHbf8Hav=RZQHiDdsOfQ@mail.gmail.com>
In-Reply-To: <CABkgnnWZHcVaRzEmG5QwZCFUOXE8khyHbf8Hav=RZQHiDdsOfQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.34.240]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-11_01:, , 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-1711220000 definitions=main-1805110007
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-11_01:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805110007
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ZzMQmUHEdsd730Uf4zEJ3fvj1Rg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 11 May 2018 01:28:05 -0000

RG9uZS4gIGh0dHBzOi8vZ2l0aHViLmNvbS9xdWljd2cvYmFzZS1kcmFmdHMvcHVsbC8xMzUwDQoN
Ci0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBNYXJ0aW4gVGhvbXNvbiBbbWFpbHRv
Om1hcnRpbi50aG9tc29uQGdtYWlsLmNvbV0gDQpTZW50OiBUaHVyc2RheSwgTWF5IDEwLCAyMDE4
IDg6MzcgUE0NClRvOiBJYW4gU3dldHQgPGlhbnN3ZXR0QGdvb2dsZS5jb20+DQpDYzogTHViYXNo
ZXYsIElnb3IgPGlsdWJhc2hlQGFrYW1haS5jb20+OyBOaWNrIEJhbmtzIDxuaWJhbmtzQG1pY3Jv
c29mdC5jb20+OyBNaWtlIEJpc2hvcCA8bWJpc2hvcEBldmVxdWVmb3UuYmU+OyBSb2JlcnRvIFBl
b24gPGZlbml4QGZiLmNvbT47IFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc+OyBEbWl0cmkgVGlraG9u
b3YgPGR0aWtob25vdkBsaXRlc3BlZWR0ZWNoLmNvbT4NClN1YmplY3Q6IFJlOiBXaHkgYWxsb3cg
ZW1wdHkgU1RSRUFNIGZyYW1lcyB3aGVuIG9mZnNldCBpcyB6ZXJvPw0KDQpUaGF0J3MgcG9zc2li
bGUsIGlmIHNvbWVvbmUgd2FudHMgdG8gb3BlbiBhIFBSLg0KDQpUbyBiZSBjbGVhciwgSSBkb24n
dCB0aGluayB0aGF0IHRoZXJlIGlzIGEgdmFsaWQgdXNlIGNhc2UgZm9yIGFuIGVtcHR5IFNUUkVB
TSBmcmFtZSAob3RoZXIgdGhhbiBhdCB0aGUgc3RhcnQgb3IgZW5kKSB0aGF0IGlzbid0IHNhdGlz
ZmllZCBiZXR0ZXIgYnkgb3RoZXIgZnJhbWVzLiAgQnV0IHdlJ3JlIG5vdCBuZWNlc3NhcmlseSBp
biB0aGUgYnVzaW5lc3Mgb2YgcG9saWNpbmcgdGhlc2UgdGhpbmdzIGFuZCBhbGxvd2luZyBlbXB0
eSBTVFJFQU0gZnJhbWVzIGlzIGFjdHVhbGx5IGVhc2llciB0aGFuIGNyZWF0aW5nIHRoZSBleGNs
dXNpb25zLg0KDQpIZXJlJ3MgYSB1c2UgY2FzZTogc3RlZ2Fub2dyYXBoeS4gIEEgY292ZXJ0IGNo
YW5uZWwgdG8gdGhlIHBlZXIgdGhhdCB3b24ndCBtYW5pZmVzdCBhcyBvYnNlcnZhYmxlIGFjdGl2
aXR5IG91dHNpZGUgb2YgdGhlIFFVSUMgc3RhY2suICBBbiBlbXB0eSBTVFJFQU0gZnJhbWUgY2Fu
IGNhcnJ5IGEgc3VycHJpc2luZyBhbW91bnQgb2YgZW50cm9weSBpZiB5b3UgYXJlIGNsZXZlci4N
Cg0KV2Ugd291bGQgdGhlbiBwdXQgZW1wdHkgU1RSRUFNIGZyYW1lcyBpbiB0aGUgc2FtZSBidWNr
ZXQgYXMgb3RoZXIgZnJhbWVzIHRoYXQgY291bGQgYmUgcG9pbnRsZXNzIGFuZCB3YXN0ZWZ1bCB3
aGVuIHVzZWQgZXhjZXNzaXZlbHkuICBUaGVyZSdzIGFscmVhZHkgYSBidW5jaCBvZiB0aG9zZS4N
Ck9uIEZyaSwgTWF5IDExLCAyMDE4IGF0IDEwOjExIEFNIElhbiBTd2V0dCA8aWFuc3dldHQ9IDQw
Z29vZ2xlLmNvbUBkbWFyYy5pZXRmLm9yZz4gd3JvdGU6DQoNCj4gSSB3b3VsZCBhZ3JlZSB0aGF0
IHRoZSByZXN0cmljdGlvbiBoZXJlIHNlZW0gdW5uZWNlc3NhcnkgYW5kIEkgdGVuZCB0bw0KdGhp
bmsgd2UnZCBiZSBiZXR0ZXIgb2ZmIHJlbW92aW5nIGl0Lg0KDQo+IE9uIFRodSwgTWF5IDEwLCAy
MDE4IGF0IDU6NTggUE0gTHViYXNoZXYsIElnb3IgPGlsdWJhc2hlPSA0MGFrYW1haS5jb21AZG1h
cmMuaWV0Zi5vcmc+IHdyb3RlOg0KDQo+PiBBY3R1YWxseSwgSeKAmWxsIHRha2UgYW4gaXNzdWUg
d2l0aDoNCj4+DQo+PiBbZHJhZnQtaWV0Zi1xdWljLXRyYW5zcG9ydC0xMV0gc2F5cyB0aGUgZm9s
bG93aW5nOg0KPj4gICAgICBBIHN0cmVhbSBmcmFtZSdzIFN0cmVhbSBEYXRhIE1VU1QgTk9UIGJl
IGVtcHR5LCB1bmxlc3MgdGhlIG9mZnNldCBpcw0KPj4gICAgICAwIG9yIHRoZSBGSU4gYml0IGlz
IHNldC4NCj4+DQo+PiBXaHkgZGlzYWxsb3cgdGhpcz8gIFRoaXMgbWF5IGJlIGEgc2lnbmFsIHRv
IHRoZSByZWNlaXZlciBhYm91dCB3aGVyZSANCj4+IGluIHRoZSBzdHJlYW0gdGhlIHNlbmRlciBp
cywgZXZlbiBpZiB0aGUgc2VuZGVyIGRvZXMgbm90IGhhdmUgYW55IG5ldyBkYXRhIHRvIHNlbmQu
ICBUaGlzIHNpZ25hbCBtYXkgYmUgdXNlZnVsIGluIGNhc2VzIG9mIHBhY2tldCBsb3NzLCB3aGVu
IHRoZSBzZW5kZXIgaXMgbm90IHJlYWR5IHRvIGRlY2xhcmUgYSBwYWNrZXQgd2l0aCBzdHJlYW0g
ZGF0YSBsb3N0IGFuZCByZXRyYW5zbWl0IGxvdHMgb2Ygc3RyZWFtIGRhdGEgKGhhcyBub3QgYmVl
biBsb25nIGVub3VnaCksIGJ1dCBpdCBpcyB2ZXJ5IGltcG9ydGFudCBmb3IgdGhlIGFwcGxpY2F0
aW9uIHRvIGtub3cgd2hlcmUgdGhlIHNlbmRlciBpcyBpbiB0aGUgc3RyZWFtLiAgT2YgY291cnNl
LCB0aGVyZSBhcmUgd29ya2Fyb3VuZHMg4oCTIHlvdSBjYW4gc2VuZCBhIFNUUkVBTSBmcmFtZSwg
cmV0cmFuc21pdHRpbmcgYSBzaW5nbGUgYnl0ZS4gIEJ1dCBpdCBzdGlsbCBzZWVtcyBsaWtlIGFu
IHVubmVjZXNzYXJ5IHJlc3RyaWN0aW9uLg0K


From nobody Mon May 14 10:15:56 2018
Return-Path: <samuelh@rd.bbc.co.uk>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3F9351242EA for <quic@ietfa.amsl.com>; Mon, 14 May 2018 10:15:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 XxlAgpxJAztm for <quic@ietfa.amsl.com>; Mon, 14 May 2018 10:15:53 -0700 (PDT)
Received: from gateh.kw.bbc.co.uk (gateh.kw.bbc.co.uk [132.185.132.17]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 356A4124217 for <quic@ietf.org>; Mon, 14 May 2018 10:15:53 -0700 (PDT)
Received: from mailhub0.rd.bbc.co.uk ([172.29.120.128]) by gateh.kw.bbc.co.uk (8.14.5+Sun/8.13.6) with ESMTP id w4EHFpgY026277 for <quic@ietf.org>; Mon, 14 May 2018 18:15:51 +0100 (BST)
Received: from rd015072.rd.bbc.co.uk ([172.29.91.136]:46218) by mailhub0.rd.bbc.co.uk with esmtp (Exim 4.84_2) (envelope-from <samuelh@rd.bbc.co.uk>) id 1fIH4g-0007fi-Ti for quic@ietf.org; Mon, 14 May 2018 18:15:50 +0100
From: Samuel Hurst <samuelh@rd.bbc.co.uk>
Subject: nghq - A HTTP/QUIC Implementation
To: IETF QUIC WG <quic@ietf.org>
Message-ID: <8c3712fd-cc1f-ccc7-05c2-b29ccd85f308@rd.bbc.co.uk>
Date: Mon, 14 May 2018 18:15:50 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Zh_pVDyaTJ7C4YE8YHU07AZDi6k>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 14 May 2018 17:15:55 -0000

BBC R&D is pleased to announce the immediate availability of "nghq", an 
open source HTTP/QUIC library hosted on GitHub under an MIT licence. We 
welcome contributions to the code via pull requests on GitHub at 
https://github.com/bbc/nghq.

nghq implements the HTTP/QUIC mapping on top of ngtcp2. Its API is 
modelled on nghttp2, meaning that the library does not own the socket 
and does no encryption or decryption. Instead, it relies on the 
application to feed in data, and act on callbacks from the library. For 
more information, please read the README on the project.

nghq currently has partial support for HTTP/QUIC draft-09. This version 
was chosen because it uses HPACK. nghq's header compression 
implementation is provided by nghttp2. We are not aware of any publicly 
available QPACK implementation, but have designed things so that one can 
easily be swapped in at a later date.

The library currently integrates against a version of ngtcp2 supporting 
draft-09 of the QUIC transport. We intend to keep tracking ongoing 
ngtcp2 development and integrate them in due course.

ngtcp2 can already create and parse the following HTTP/QUIC frame types: 
DATA, HEADERS, PUSH_PROMISE, CANCEL_PUSH, MAX_PUSH_ID and GOAWAY. In 
addition, there are untested parsers for SETTINGS and PRIORITY frames, 
but the library cannot create or do anything with them yet.

Since we have been primarily targeting our multicast use-case 
(draft-pardue-quic-http-mcast-02), there has not been any work done on 
the unicast handshake. However, all of the heavy lifting is done by 
ngtcp2, so it shouldn't be too difficult to add.

Our multicast sender example does not presently perform AEAD on the QUIC 
packet payload.

We invite contributions in the above areas. We're also happy to receive 
feedback and can answer questions on the mailing list or QUIC developer 
slack.


Best Regards,
Sam


From nobody Wed May 16 00:29:26 2018
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F534129C59 for <quic@ietfa.amsl.com>; Wed, 16 May 2018 00:29:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.411
X-Spam-Level: 
X-Spam-Status: No, score=-2.411 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 TuAozXnL3d4C for <quic@ietfa.amsl.com>; Wed, 16 May 2018 00:29:25 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (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 D5972129C51 for <quic@ietf.org>; Wed, 16 May 2018 00:29:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1526455763; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=mNJrts2YnNn7bwzdYZDf/dkceeDvi9/0QA7F2fyguWY=; b=ahYb8e4J8jVmJr/WqKTskg7oDpDj1rjOeZvSeCL6iWZYk0onh+ULQ+oFia6Y0YGN 5sqAZwwHfKmb45x+ga4VwEw17AP4WdgYTUGX2umGWGxga676zbg0b59mP4rurj2T /Kvgu6z0HxRN8UbmkAA6oPhM8VYpSSiM9ToafgQg+X8=;
X-AuditID: c1b4fb30-e77ff7000000169b-76-5afbddd23ed1
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.183.24]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 54.D9.05787.2DDDBFA5; Wed, 16 May 2018 09:29:23 +0200 (CEST)
Received: from [147.214.161.108] (153.88.183.153) by smtps.internal.ericsson.com (153.88.183.24) with Microsoft SMTP Server (TLS) id 14.3.382.0; Wed, 16 May 2018 09:29:22 +0200
To: IETF QUIC WG <quic@ietf.org>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: QUIC Interim in Stockholm - On site participants with food restrictions
Message-ID: <eee5904c-b7a8-b949-4c77-c8fdbe8b5d45@ericsson.com>
Date: Wed, 16 May 2018 09:29:22 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
X-Originating-IP: [153.88.183.153]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrKLMWRmVeSWpSXmKPExsUyM2K7hO7lu7+jDDblWfQs4HZg9Fiy5CdT AGMUl01Kak5mWWqRvl0CV8bbZfIFJ9gqHjx8z9TAuJa1i5GTQ0LARGLpu2tANheHkMARRol5 DXPZIZwtjBJzZ95l62Lk4BARUJBY08AJ0sAmYCFx80cjG4gtLBAk8ffQV2YQm1fAXuLSxhks IDaLgKrE0+ZeRhBbVCBG4sfRLhaIGkGJkzOfsICMZAaqf7C1DCTMLCAvsf3tHGYIW1yi6ctK sNuEBLQlGpo6oO5Ukrg+7zrLBEb+WUgmzUKYNAvJpFlIJi1gZFnFKFqcWpyUm25kpJdalJlc XJyfp5eXWrKJERh4B7f8NtjB+PK54yFGAQ5GJR7eq0d+RwmxJpYVV+YeYpTgYFYS4c3kBQrx piRWVqUW5ccXleakFh9ilOZgURLntfDbHCUkkJ5YkpqdmlqQWgSTZeLglGpgnPpDSuvJ3nTx /fea2LXdeO3vJjLvbJzEut7q3Qfjzxks2c1ThGaZcB7WNjFsXbaY9ZR1+zGRX95t6UEf1HQ1 X1++t/vbdaYNT8WqeV1KHp1O93a/kN39XuqO2rN77OUbTiZeSBAQ9hRdcyjmygn2fV7JkZKZ azmKylvXnWItu995jTfsYLGyEktxRqKhFnNRcSIA+4ixNjgCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/-vhteoyMV-JbYwqvYlaM9SfcUlk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2018 07:29:26 -0000

QUIC WG Participants

To those who will be on site for the June Interim meeting and interop. 
If you have any food restrictions please send them to me no later than 
Monday the 21st of May. Ericsson intended to provide sandwiches or 
coffee bread in the coffee breaks.

Lunch will be at your own expense at any of the available restaurants in 
Kista.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Network Architecture & Protocols, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Wed May 16 03:01:12 2018
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 12AB212D967 for <quic@ietfa.amsl.com>; Wed, 16 May 2018 03:01:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.411
X-Spam-Level: 
X-Spam-Status: No, score=-2.411 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 hCQ-5lBxqycA for <quic@ietfa.amsl.com>; Wed, 16 May 2018 03:01:03 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 8B2A112D7F2 for <quic@ietf.org>; Wed, 16 May 2018 03:01:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1526464861; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=ToH37s//m7b0YCk58JSkfRUSmr+CMQ8uvXeE497ufRY=; b=We8OSZPDoG0qXNLz9XlG5PsLo+XzpAD5E11FlBn4s7RzgoL+ogb5MI7w5Lv+RgbZ 12RkANlBHeegEnS+D9Iu85iOjOaI2grJSOTqyNVhOk1pnfaKmfLaAzvmrdzEValr 6cXcMwHAH6CyWsuTkvWOh4FcXk5Z+sfxJGd1IiHXzvg=;
X-AuditID: c1b4fb3a-5a4b59c000006a47-d8-5afc015df559
Received: from ESESSHC018.ericsson.se (Unknown_Domain [153.88.183.72]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id B7.33.27207.D510CFA5; Wed, 16 May 2018 12:01:01 +0200 (CEST)
Received: from [147.214.161.108] (153.88.183.153) by smtps.internal.ericsson.com (153.88.183.72) with Microsoft SMTP Server (TLS) id 14.3.382.0; Wed, 16 May 2018 12:00:59 +0200
To: IETF QUIC WG <quic@ietf.org>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Path verification contradictions in Connection migration
Message-ID: <6842c0d0-f186-7043-31d5-c05a0fa4dba9@ericsson.com>
Date: Wed, 16 May 2018 12:00:59 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
X-Originating-IP: [153.88.183.153]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrKLMWRmVeSWpSXmKPExsUyM2K7h24s458ogxNnzC16FnA7MHosWfKT KYAxissmJTUnsyy1SN8ugSvjzfKrTAXPBSuWvj3B2sC4ka+LkZNDQsBE4sT7PewgtpDAEUaJ b590IewtjBIn1gR2MXJwiAgoSKxp4AQJswlYSNz80cgGYgsLOEo0tv9mArF5BewlGj++YgGx WQRUJfbueAg2UlQgRuLH0S4WiBpBiZMzn7CAjGQGqn+wtQwkzCwgL9G8dTYzhC0u0fRlJSvE BdoSDU0drBBXKklcn3edZQIj/ywkk2YhTJqFZNIsJJMWMLKsYhQtTi0uzk03MtJLLcpMLi7O z9PLSy3ZxAgMvINbflvtYDz43PEQowAHoxIPb8Pf31FCrIllxZW5hxglOJiVRHgzeYFCvCmJ lVWpRfnxRaU5qcWHGKU5WJTEeZ3SLKKEBNITS1KzU1MLUotgskwcnFINjCz8cvvYb/TccU0q ORTif0TJ4EnUhhKOO28b+f72LC7/8J61bvnJL4bH2Djk900N4PueFpDglnro5uqergkKVecn nnp16cJFztPFXxfNvMnH1Ja7br4+T2vih+Lv4ceXJb475vQn8ED5q+TUX4v4qzYxtrPn/3T0 bHOoXOpuOT33EKvWG5tfe5RYijMSDbWYi4oTAa4tQ784AgAA
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/JugnT_PHOE1rbTQKGXDlildGnTk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 16 May 2018 10:01:10 -0000

Hi,

I was looking at the connection migration text in transport-11:

Section 6.8.2 says:

    Each endpoint validates its peer's address during connection
    establishment.  Therefore, a migrating endpoint can send to its peer
    knowing that the peer is willing to receive at the peer's current
    address.  Thus an endpoint can migrate to a new local address without
    first validating the peer's address.

    Receiving acknowledgments for data sent on the new path serves as
    proof of the peer's reachability from the new address.  Note that
    since acknowledgments may be received on any path, return
    reachability on the new path is not established.  To establish return
    reachability on the new path, an endpoint MAY concurrently initiate
    path validation Section 6.7 on the new path.

Then Section 6.8.3 says:

    Receiving a packet from a new peer address containing a non-probing
    frame indicates that the peer has migrated to that address.

    In response to such a packet, an endpoint MUST start sending
    subsequent packets to the new peer address and MUST initiate path
    validation (Section 6.7) to verify the peer's ownership of the
    unvalidated address.

It is especially the Note in 6.8.2 second of above paragraphs that I 
find contradicting.

When the server receives the clients non-probing frames from the 
client's new address, then the server MUST send the ACK for that packet 
towards the client's new address. That is at least how I interpret the 
second in Section 6.8.3 paragraph. Yes, from the server's perspective 
the serve->client path is unverified. However, I don't understand how 
the first part of the Note would be possible: "Note that since 
acknowledgments may be received on any path"?


Cheers

Magnus Westerlund

----------------------------------------------------------------------
Network Architecture & Protocols, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Thu May 17 22:08:18 2018
Return-Path: <martenseemann@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF19312706D for <quic@ietfa.amsl.com>; Thu, 17 May 2018 22:08:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Ics616LWeSwd for <quic@ietfa.amsl.com>; Thu, 17 May 2018 22:08:13 -0700 (PDT)
Received: from mail-io0-x236.google.com (mail-io0-x236.google.com [IPv6:2607:f8b0:4001:c06::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6965B127023 for <quic@ietf.org>; Thu, 17 May 2018 22:08:12 -0700 (PDT)
Received: by mail-io0-x236.google.com with SMTP id d73-v6so4749522iog.3 for <quic@ietf.org>; Thu, 17 May 2018 22:08:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=zViNx863Qe+fElB0vkXursxUI2Lh0+T/dgjTJeYa144=; b=rHOTJEw8kR1yOxDRyDko65KeoyZ+bq/J5yeyD2mPdxozbZymjO3+d2FZOwruxAWGRP SiyR1nox3oz87jfRG3Tb5CcKgQTZPa3iKKHAUaTHIe6P3jlU46Y5ZI2LeC0zjz6pVEDA z/vZTy75mIRiFWbyxkDh3O8XxU/PXYHN5a2yySFagdbw9D67BucYGwAOFjQKy17YWHHW Ed1vErscYzx3OY14DNVuqmUPi+UnsRE1cXJhGCb7AObp2SiR+0o7m+7UWszLQYyfJz1S I0u0CfrwakW5K2zO5I34A0TW6exF0tpRzczbc7oPKQrFyNjdSDY7Mno23jPcxl0VAg0+ Zp5Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=zViNx863Qe+fElB0vkXursxUI2Lh0+T/dgjTJeYa144=; b=qAmMu1jzIP5ygqSCvi/YyDttXEYn6zsPXGxmVyBtiGJFebbm3xoaMvFHe67nqf04iu nKW1k7pXSH3CRbGOKnCwduS8NunBzU1s96VaZQWWL4PlocEheuSmoodp6FrPS/tnZUu8 impiCC7juLWJS8AJLwmG69OD4Q5rr6j1Lgy82AGtiBPLeaLNYJ8u+CFoSQkzUmT/Beqw jncjsL2i70UYuWMxn3aYDw9HGCWyOTe+1kqNyN8MVZd87b8uW505qQvdA3sjbdlmnbDu mBhn3w0MQh10J5zn3wnJGIOxWJaUGXVchCLG7Qvhdzm5uDifBVEVzjrW5XfJPddA8n/d KNSw==
X-Gm-Message-State: ALKqPwddel6cX8MmARzsEuo2sZk5cNr97Uj6aBNPYJhnoFIA2pOFVmxf wlT1YyV1CtQ7A2HnFW9JYIKSmE599Z3yqpIR65uCtg==
X-Google-Smtp-Source: AB8JxZqKeFLeOlEXTw+zGQKcWKWFzVCmLiuy9IE+nYyBV+NQsnJeuUVQv2/1eOoh+1aaNINXIdz62oQWmM3jJAtcG0o=
X-Received: by 2002:a6b:1c06:: with SMTP id c6-v6mr9297349ioc.247.1526620091962;  Thu, 17 May 2018 22:08:11 -0700 (PDT)
MIME-Version: 1.0
From: Marten Seemann <martenseemann@gmail.com>
Date: Fri, 18 May 2018 14:08:00 +0900
Message-ID: <CAOYVs2q63DpkPZTbw9T24ZcFOxbvrWAGvOtUaHvCuSg_13pSkQ@mail.gmail.com>
Subject: Payload length 0
To: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000049dbe0056c73f0cf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/5Wv6o9enwQUBrQ3VODiFvQhV3Gk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 May 2018 05:08:16 -0000

--00000000000049dbe0056c73f0cf
Content-Type: text/plain; charset="UTF-8"

Jana asked me to raise this issue on the list, after we already had a bit
of discussion in https://github.com/quicwg/base-drafts/pull/1301.

The proposal is to make a payload length of 0 a special value, indicating
that the packet is not a coalesced packet, i.e. that the whole payload of
the UDP packet is the QUIC packet. This would eliminate an invalid value of
the payload length (there are no empty packets), save one byte for packet
lengths where varint encoding would result in a two byte number, and
apparently also simplify (some) implementations.

Kazuho argued creating two versions of each Long Header type (one with and
one without a payload length) is the better solution, since all values
below the AEAD tag length + 1 are invalid values anyway, and it would save
one more byte.

We should make a decision if and what we want to do about this.

--00000000000049dbe0056c73f0cf
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Jana asked me to raise this issue on the list, after we al=
ready had a bit of discussion in=C2=A0<a href=3D"https://github.com/quicwg/=
base-drafts/pull/1301">https://github.com/quicwg/base-drafts/pull/1301</a>.=
<div><br></div><div>The proposal is to make a payload length of 0 a special=
 value, indicating that the packet is not a coalesced packet, i.e. that the=
 whole payload of the UDP packet is the QUIC packet. This would eliminate a=
n invalid value of the payload length (there are no empty packets), save on=
e byte for packet lengths where varint encoding would result in a two byte =
number, and apparently also simplify (some) implementations.</div><div><br>=
</div><div>Kazuho argued creating two versions of each Long Header type (on=
e with and one without a payload length) is the better solution, since all =
values below the AEAD tag length=C2=A0+ 1 are invalid values anyway, and it=
 would save one more byte.</div><div><br></div><div>We should make a decisi=
on if and what we want to do about this.</div></div>

--00000000000049dbe0056c73f0cf--


From nobody Thu May 17 22:34:29 2018
Return-Path: <martin.thomson@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 307BC1270AB for <quic@ietfa.amsl.com>; Thu, 17 May 2018 22:34:27 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 6U7_u20RWcUF for <quic@ietfa.amsl.com>; Thu, 17 May 2018 22:34:24 -0700 (PDT)
Received: from mail-ot0-x236.google.com (mail-ot0-x236.google.com [IPv6:2607:f8b0:4003:c0f::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 629F31270A3 for <quic@ietf.org>; Thu, 17 May 2018 22:34:24 -0700 (PDT)
Received: by mail-ot0-x236.google.com with SMTP id m11-v6so7766410otf.3 for <quic@ietf.org>; Thu, 17 May 2018 22:34:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=4CpTIGAMEHdFs97YNZkUybkYF/PmnZvrQ2/0u9U2Bug=; b=hdPRLE1cahP5fQRgI7Of08XrlBpaDqeAJ5ztg76jXUXlXmTmOW5a5zBVAvcTIYYORD TS0v4iLK72lnTfpTta3puDdU9DYptMXgn1SPixxv8AVLd/VBUkfIwLFdTM+qLaiAH2Fe 4jyU8g7wRVrj/mC/z4m/384XybW3Ggl9nA2Qu+T8Znl6qOV5W4Vo7zAkkRiYQvh32S8O nwFHi3KiDWGVFKePMmIpzT6z7J0a0S1L6eXzyKPr6G9excRtYdsLk8cD1XMblHPZJbWC CClx6XvaaBk5UsqHn4k6D+sRsgRKZtTKMfCS2jo0jzHj+she5xER6I2yF0eJLUzuwgO4 t+Bw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=4CpTIGAMEHdFs97YNZkUybkYF/PmnZvrQ2/0u9U2Bug=; b=eF1WUOKmJU0lmEKsZNQehyr0+A/S4PwWSAVnVWloigr9ShHDDgLrfr6v3grsglSUa+ NzQUMBwT5Qj6yMgnH0LDsBbAnXfUlFhs+Cumdh8NBa2LLyioLiEl6C8+NQtwkdgr9luV Lkp0SnurpuyuDDEP2O0/9uGMByULyfUCqONtgWIsuBSLXNMVpXW5xTWSzgvgk64iTU7F wDv4D/jeCTboJYS0jlIuAt8X+3TkAPXtKOSK0gVTLWJBTz7Kh3qtnObcejBsBqmmEsny pEo2wBrd6m5bL0Lm/XG0g7zWdVB3M3tpRkup0q2YczSab6y7uDFEe3zCcnW80tkca4Wu UTaw==
X-Gm-Message-State: ALKqPwd0z2TLPBnXIyk628U+Igz6fEsMQOqaerKoztnJRvEcmP0oLWHu 7Qo1Re1Ky6I2F6ccdCSmnMx7bh1cv//z0GjOFCU=
X-Google-Smtp-Source: AB8JxZqu0LdtZRzTy3yyZdDmW2ZsxN7d6NjLtqZldoMT9uy9zJE+dl2ft3KTkIK3gZjx0//CJYGExficb/CHb7f/us0=
X-Received: by 2002:a9d:354a:: with SMTP id l10-v6mr5815352ote.15.1526621663609;  Thu, 17 May 2018 22:34:23 -0700 (PDT)
MIME-Version: 1.0
References: <CAOYVs2q63DpkPZTbw9T24ZcFOxbvrWAGvOtUaHvCuSg_13pSkQ@mail.gmail.com>
In-Reply-To: <CAOYVs2q63DpkPZTbw9T24ZcFOxbvrWAGvOtUaHvCuSg_13pSkQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 18 May 2018 15:34:12 +1000
Message-ID: <CABkgnnWpgyN_OPac-uSKALEaVc8mO_LpT9gAOs-n1eKqso5QAQ@mail.gmail.com>
Subject: Re: Payload length 0
To: Marten Seemann <martenseemann@gmail.com>
Cc: QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/tRBd-rGchKWzQOfb7GubepqrXVo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 May 2018 05:34:27 -0000

Having just implemented this (and gotten it wrong once), I don't want more
special cases.  Both of these options need extra code.  As Kazuho points
out, filling in a two octet length is trivial.

It's true that a length of 0 is invalid, but so is 1 through 16.

Yes, this saves an octet, on about 4 packets per connection in the common
case, more like 2 if you actually take advantage of compound packets.
On Fri, May 18, 2018 at 3:08 PM Marten Seemann <martenseemann@gmail.com>
wrote:

> Jana asked me to raise this issue on the list, after we already had a bit
of discussion in https://github.com/quicwg/base-drafts/pull/1301.

> The proposal is to make a payload length of 0 a special value, indicating
that the packet is not a coalesced packet, i.e. that the whole payload of
the UDP packet is the QUIC packet. This would eliminate an invalid value of
the payload length (there are no empty packets), save one byte for packet
lengths where varint encoding would result in a two byte number, and
apparently also simplify (some) implementations.

> Kazuho argued creating two versions of each Long Header type (one with
and one without a payload length) is the better solution, since all values
below the AEAD tag length + 1 are invalid values anyway, and it would save
one more byte.

> We should make a decision if and what we want to do about this.


From nobody Fri May 18 05:07:02 2018
Return-Path: <ianswett@google.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6366212D7F8 for <quic@ietfa.amsl.com>; Fri, 18 May 2018 05:07:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -18.21
X-Spam-Level: 
X-Spam-Status: No, score=-18.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 2vdBGwX-Nlov for <quic@ietfa.amsl.com>; Fri, 18 May 2018 05:06:59 -0700 (PDT)
Received: from mail-yw0-x233.google.com (mail-yw0-x233.google.com [IPv6:2607:f8b0:4002:c05::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 270AE12D7F4 for <quic@ietf.org>; Fri, 18 May 2018 05:06:59 -0700 (PDT)
Received: by mail-yw0-x233.google.com with SMTP id g16-v6so2326829ywk.0 for <quic@ietf.org>; Fri, 18 May 2018 05:06:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=GlkyZ2ag0fZu5HykXFqcO86SQ8+v5iwLnNusREqa76c=; b=SZOxIsIQb8UZq+9/hF1JVWN6KxrOVnv0tIKh/cv8Hdzu1rTGnQajyVlbUVtcSY+DmN Gxga93oQb9BPcFQm0KX3a6+S/UKtHwOj1QleO7JDKNSNaXLwTNCBHQFGXOOMQrQi4j8M 6w2QZmghYXKPzhDdYUxr8wyz1LhkzsZbSVDBrHi6jbqGvMNe9umjzjGM2yURLrir6okT C2CvjQf721A9ogNcdL9zoTVFQMkFYFWhoehow8IWoVvnffiTPf51QXyURpSCJkuzIMAF 7RaBxxjIkJQSIkwgTzn2YAtq9HvluGNLbPJtsRs5gfmsyMBh6XKUKuztWCWaykF9quWP nLGA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=GlkyZ2ag0fZu5HykXFqcO86SQ8+v5iwLnNusREqa76c=; b=TyegD56AuxLWgrgYjN/9xfX3t7EFJDP9/HMESRvEh9E5v8nugLtNLXIqLFU6pqmqnT EAwZQ4oO7WZl7I/6k4esoWnH34r/ENRm6TVW+m/CH+GcwxEem1E9RH7FWCbCytkZ8ase ZLCH9wt8AqG1BgTT+BkZDpF60Sf7eoNLlIHrajmSr7JWuaNbJSl6mHb1/YoBL87Miq9G F9wTvMPetf7WbeMjnK4yQhPyigBdjr7SopKfHxrL7ZechYoootZ+XFX2Sgyrap8kfTQu UJsgIKB6l8ZCrQIuQA2YTuWE2HEHObSw1SZhu+dZm4hQYvcbgqqcaK67vbbEp4cpKP7A ae7w==
X-Gm-Message-State: ALKqPwcybh6AqGnYM6lNPnmT8KK5h8ThFwVtY96ndbMqPXiyPy9Pu6ss Mvq6wuaGXwtXKgvso2yzsFjy864u+lNqiiFx2KRIKw==
X-Google-Smtp-Source: AB8JxZqsTzGVSZtWKVzE/PUKc/LsfiRhBuoc2yyiN/5Kil3BcmR/V4RX4k6NTrOhuBxp06Y2iviEJGVVxZo/J/8dzWs=
X-Received: by 2002:a81:b344:: with SMTP id r65-v6mr4399568ywh.283.1526645218109;  Fri, 18 May 2018 05:06:58 -0700 (PDT)
MIME-Version: 1.0
References: <CAOYVs2q63DpkPZTbw9T24ZcFOxbvrWAGvOtUaHvCuSg_13pSkQ@mail.gmail.com> <CABkgnnWpgyN_OPac-uSKALEaVc8mO_LpT9gAOs-n1eKqso5QAQ@mail.gmail.com>
In-Reply-To: <CABkgnnWpgyN_OPac-uSKALEaVc8mO_LpT9gAOs-n1eKqso5QAQ@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Fri, 18 May 2018 08:06:01 -0400
Message-ID: <CAKcm_gMFumNgPq4FxwcgzgDUCvn_jUxb0qk7tAgYZ=LvKfxjfg@mail.gmail.com>
Subject: Re: Payload length 0
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Marten Seemann <martenseemann@gmail.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ed0966056c79c9e0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/CO8rEXqgtV67yUdS4YwthCF-o4k>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 May 2018 12:07:02 -0000

--000000000000ed0966056c79c9e0
Content-Type: text/plain; charset="UTF-8"

I would also prefer to not do either of these, because I think it adds
complexity and the byte savings are tiny.

On Fri, May 18, 2018 at 1:34 AM Martin Thomson <martin.thomson@gmail.com>
wrote:

> Having just implemented this (and gotten it wrong once), I don't want more
> special cases.  Both of these options need extra code.  As Kazuho points
> out, filling in a two octet length is trivial.
>
> It's true that a length of 0 is invalid, but so is 1 through 16.
>
> Yes, this saves an octet, on about 4 packets per connection in the common
> case, more like 2 if you actually take advantage of compound packets.
> On Fri, May 18, 2018 at 3:08 PM Marten Seemann <martenseemann@gmail.com>
> wrote:
>
> > Jana asked me to raise this issue on the list, after we already had a bit
> of discussion in https://github.com/quicwg/base-drafts/pull/1301.
>
> > The proposal is to make a payload length of 0 a special value, indicating
> that the packet is not a coalesced packet, i.e. that the whole payload of
> the UDP packet is the QUIC packet. This would eliminate an invalid value of
> the payload length (there are no empty packets), save one byte for packet
> lengths where varint encoding would result in a two byte number, and
> apparently also simplify (some) implementations.
>
> > Kazuho argued creating two versions of each Long Header type (one with
> and one without a payload length) is the better solution, since all values
> below the AEAD tag length + 1 are invalid values anyway, and it would save
> one more byte.
>
> > We should make a decision if and what we want to do about this.
>
>

--000000000000ed0966056c79c9e0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I would also prefer to not do either of these, because I t=
hink it adds complexity and the byte savings are tiny.<br></div><br><div cl=
ass=3D"gmail_quote"><div dir=3D"ltr">On Fri, May 18, 2018 at 1:34 AM Martin=
 Thomson &lt;<a href=3D"mailto:martin.thomson@gmail.com">martin.thomson@gma=
il.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Having just i=
mplemented this (and gotten it wrong once), I don&#39;t want more<br>
special cases.=C2=A0 Both of these options need extra code.=C2=A0 As Kazuho=
 points<br>
out, filling in a two octet length is trivial.<br>
<br>
It&#39;s true that a length of 0 is invalid, but so is 1 through 16.<br>
<br>
Yes, this saves an octet, on about 4 packets per connection in the common<b=
r>
case, more like 2 if you actually take advantage of compound packets.<br>
On Fri, May 18, 2018 at 3:08 PM Marten Seemann &lt;<a href=3D"mailto:marten=
seemann@gmail.com" target=3D"_blank">martenseemann@gmail.com</a>&gt;<br>
wrote:<br>
<br>
&gt; Jana asked me to raise this issue on the list, after we already had a =
bit<br>
of discussion in <a href=3D"https://github.com/quicwg/base-drafts/pull/1301=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/1301</a>.<br>
<br>
&gt; The proposal is to make a payload length of 0 a special value, indicat=
ing<br>
that the packet is not a coalesced packet, i.e. that the whole payload of<b=
r>
the UDP packet is the QUIC packet. This would eliminate an invalid value of=
<br>
the payload length (there are no empty packets), save one byte for packet<b=
r>
lengths where varint encoding would result in a two byte number, and<br>
apparently also simplify (some) implementations.<br>
<br>
&gt; Kazuho argued creating two versions of each Long Header type (one with=
<br>
and one without a payload length) is the better solution, since all values<=
br>
below the AEAD tag length + 1 are invalid values anyway, and it would save<=
br>
one more byte.<br>
<br>
&gt; We should make a decision if and what we want to do about this.<br>
<br>
</blockquote></div>

--000000000000ed0966056c79c9e0--


From nobody Fri May 18 06:44:11 2018
Return-Path: <dtikhonov@litespeedtech.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7224312D95F for <quic@ietfa.amsl.com>; Fri, 18 May 2018 06:44:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 jb4YbaJJqbwy for <quic@ietfa.amsl.com>; Fri, 18 May 2018 06:44:07 -0700 (PDT)
Received: from mail-qt0-x22f.google.com (mail-qt0-x22f.google.com [IPv6:2607:f8b0:400d:c0d::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8AEC112D95E for <quic@ietf.org>; Fri, 18 May 2018 06:44:07 -0700 (PDT)
Received: by mail-qt0-x22f.google.com with SMTP id h2-v6so10283348qtp.7 for <quic@ietf.org>; Fri, 18 May 2018 06:44:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=qd13B0wvou3IoyNsYGcpCYLSITYag5nrhi9pGGxxaMc=; b=nXrb9aPLod4Kv+NF+vpu+d7Cl5hCPy6CrILHM7+tE9pwiu3A3wcOTwN5rSmdvFDMN7 xf5WJY06K0k9Q+ph35+jjwE6bGVTBu52EGlovintn1OK61M2tcMARZ0yvb6gDRekGh2I GWrMLhmlLZX72MXV/z06L/g1hpBPg5EsUYehU2PNq55Rn5rgMfUlnxwQzeLTpAfWAWEk PwOfw4c3l/FPvAAmw0HbwzJHHn2jpuqTMPxfte63xIXAsTbAhUfmE/yd+TFfbtTwHo3b 9K1n0+0qTCYZd27e8GDBKJIy8S/tvx1f1zepPTkc1qx22O16MNqjpKodapT952N+jiTs Ey8A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=qd13B0wvou3IoyNsYGcpCYLSITYag5nrhi9pGGxxaMc=; b=EE228qAReENcacOZY4v3Acgf8tAU//04+eWKmoGuSo0x8biGICQ6Lu9O1lEVXnEVVi ktWatvNkh9p1jcL8ZSfof6YhTEksmhApNvOlP0P2QECU0Fh2MhP39fmaisFt6WL1Pn8h 7YrVwWpYTbPwH/6oVXyBCU+TZ25uIvGy+p/0rWpBlNoygV0j44NYnl5bH6tXm/iLf13K tYA/ow/AV4zCgO5XhCQ15AxJZ7GKdVEgYAWSJCcp5Z3RBh6qTb5JX8hGZ5GNcttcmn79 WeKz1F6ilSj1RoIx22wJr1ZZ7FewGwksj4YhF3uzFgj2ZYyUj6O5H+n+mwWMmGJ5bHjQ iKeA==
X-Gm-Message-State: ALKqPwethHzCjkFrkLBZSESOOTT9gRamEOQ1rSkL4MBz3/hvY3vM7Ke/ GZynw4MAvdYbCU7Oy9js5MWXbQ==
X-Google-Smtp-Source: AB8JxZoLaMwfgyA0YGBkZ8XBQhsJw7M6SeIgjxzTr2vPKS6+7Fp3W3yYOQdRvEPA3LdHKZ+8SXFZvw==
X-Received: by 2002:ac8:41e:: with SMTP id v30-v6mr9687950qtg.270.1526651046570;  Fri, 18 May 2018 06:44:06 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id f82-v6sm5771815qkh.73.2018.05.18.06.44.05 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 18 May 2018 06:44:06 -0700 (PDT)
Date: Fri, 18 May 2018 09:44:01 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Ian Swett <ianswett@google.com>
Cc: Martin Thomson <martin.thomson@gmail.com>, Marten Seemann <martenseemann@gmail.com>, IETF QUIC WG <quic@ietf.org>
Subject: Re: Payload length 0
Message-ID: <20180518134400.GA12617@ubuntu-dmitri>
Mail-Followup-To: Ian Swett <ianswett@google.com>, Martin Thomson <martin.thomson@gmail.com>, Marten Seemann <martenseemann@gmail.com>, IETF QUIC WG <quic@ietf.org>
References: <CAOYVs2q63DpkPZTbw9T24ZcFOxbvrWAGvOtUaHvCuSg_13pSkQ@mail.gmail.com> <CABkgnnWpgyN_OPac-uSKALEaVc8mO_LpT9gAOs-n1eKqso5QAQ@mail.gmail.com> <CAKcm_gMFumNgPq4FxwcgzgDUCvn_jUxb0qk7tAgYZ=LvKfxjfg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAKcm_gMFumNgPq4FxwcgzgDUCvn_jUxb0qk7tAgYZ=LvKfxjfg@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/nEGyOZRXFooglOOOBRY9D1H8ppU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 May 2018 13:44:10 -0000

I agree with Martin and Ian.  We should keep the payload length field
and its value should be the actual length of the payload.

In addition to being simple, this allows some flexibility when packet
generattion is far away (in time or code) from actually sending a
packet.  That is to say, it is easier not to have to make the decision
which version of the payload length value to use when the packet is
created.

  - Dmitri.

On Fri, May 18, 2018 at 08:06:01AM -0400, Ian Swett wrote:
> I would also prefer to not do either of these, because I think it adds
> complexity and the byte savings are tiny.
> 
> On Fri, May 18, 2018 at 1:34 AM Martin Thomson <martin.thomson@gmail.com>
> wrote:
> 
> > Having just implemented this (and gotten it wrong once), I don't want more
> > special cases.  Both of these options need extra code.  As Kazuho points
> > out, filling in a two octet length is trivial.
> >
> > It's true that a length of 0 is invalid, but so is 1 through 16.
> >
> > Yes, this saves an octet, on about 4 packets per connection in the common
> > case, more like 2 if you actually take advantage of compound packets.
> > On Fri, May 18, 2018 at 3:08 PM Marten Seemann <martenseemann@gmail.com>
> > wrote:
> >
> > > Jana asked me to raise this issue on the list, after we already had a bit
> > of discussion in https://github.com/quicwg/base-drafts/pull/1301.
> >
> > > The proposal is to make a payload length of 0 a special value, indicating
> > that the packet is not a coalesced packet, i.e. that the whole payload of
> > the UDP packet is the QUIC packet. This would eliminate an invalid value of
> > the payload length (there are no empty packets), save one byte for packet
> > lengths where varint encoding would result in a two byte number, and
> > apparently also simplify (some) implementations.
> >
> > > Kazuho argued creating two versions of each Long Header type (one with
> > and one without a payload length) is the better solution, since all values
> > below the AEAD tag length + 1 are invalid values anyway, and it would save
> > one more byte.
> >
> > > We should make a decision if and what we want to do about this.
> >
> >


From nobody Fri May 18 07:05:54 2018
Return-Path: <manasi.deval@intel.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 610F312D96B for <quic@ietfa.amsl.com>; Fri, 18 May 2018 07:05:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level: 
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 ERPfr_icsvYf for <quic@ietfa.amsl.com>; Fri, 18 May 2018 07:05:50 -0700 (PDT)
Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) (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 735D812D947 for <quic@ietf.org>; Fri, 18 May 2018 07:05:50 -0700 (PDT)
X-Amp-Result: SKIPPED(no attachment in message)
X-Amp-File-Uploaded: False
Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 18 May 2018 07:05:50 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.49,415,1520924400"; d="scan'208";a="51963770"
Received: from orsmsx101.amr.corp.intel.com ([10.22.225.128]) by orsmga003.jf.intel.com with ESMTP; 18 May 2018 07:05:49 -0700
Received: from orsmsx161.amr.corp.intel.com (10.22.240.84) by ORSMSX101.amr.corp.intel.com (10.22.225.128) with Microsoft SMTP Server (TLS) id 14.3.319.2; Fri, 18 May 2018 07:05:49 -0700
Received: from orsmsx111.amr.corp.intel.com ([169.254.12.62]) by ORSMSX161.amr.corp.intel.com ([169.254.4.211]) with mapi id 14.03.0319.002; Fri, 18 May 2018 07:05:49 -0700
From: "Deval, Manasi" <manasi.deval@intel.com>
To: Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Ian Swett <ianswett@google.com>
CC: Marten Seemann <martenseemann@gmail.com>, IETF QUIC WG <quic@ietf.org>, Martin Thomson <martin.thomson@gmail.com>
Subject: RE: Payload length 0
Thread-Topic: Payload length 0
Thread-Index: AQHT7mZJNe1DSmftdUmmN/yzX8LXe6Q1bEAAgABteYCAABthgP//kH4A
Date: Fri, 18 May 2018 14:05:49 +0000
Message-ID: <1F436ED13A22A246A59CA374CBC543998B7C712F@ORSMSX111.amr.corp.intel.com>
References: <CAOYVs2q63DpkPZTbw9T24ZcFOxbvrWAGvOtUaHvCuSg_13pSkQ@mail.gmail.com> <CABkgnnWpgyN_OPac-uSKALEaVc8mO_LpT9gAOs-n1eKqso5QAQ@mail.gmail.com> <CAKcm_gMFumNgPq4FxwcgzgDUCvn_jUxb0qk7tAgYZ=LvKfxjfg@mail.gmail.com> <20180518134400.GA12617@ubuntu-dmitri>
In-Reply-To: <20180518134400.GA12617@ubuntu-dmitri>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
dlp-product: dlpe-windows
dlp-version: 11.0.200.100
dlp-reaction: no-action
x-originating-ip: [10.22.254.140]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ZGCwb2QQEiZVM-l7f0dItIuNgIU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 18 May 2018 14:05:53 -0000

Agree with keeping payload length in the header.


-----Original Message-----
From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of Dmitri Tikhonov
Sent: Friday, May 18, 2018 6:44 AM
To: Ian Swett <ianswett@google.com>
Cc: Marten Seemann <martenseemann@gmail.com>; IETF QUIC WG <quic@ietf.org>;=
 Martin Thomson <martin.thomson@gmail.com>
Subject: Re: Payload length 0

I agree with Martin and Ian.  We should keep the payload length field and i=
ts value should be the actual length of the payload.

In addition to being simple, this allows some flexibility when packet gener=
attion is far away (in time or code) from actually sending a packet.  That =
is to say, it is easier not to have to make the decision which version of t=
he payload length value to use when the packet is created.

  - Dmitri.

On Fri, May 18, 2018 at 08:06:01AM -0400, Ian Swett wrote:
> I would also prefer to not do either of these, because I think it adds=20
> complexity and the byte savings are tiny.
>=20
> On Fri, May 18, 2018 at 1:34 AM Martin Thomson=20
> <martin.thomson@gmail.com>
> wrote:
>=20
> > Having just implemented this (and gotten it wrong once), I don't=20
> > want more special cases.  Both of these options need extra code.  As=20
> > Kazuho points out, filling in a two octet length is trivial.
> >
> > It's true that a length of 0 is invalid, but so is 1 through 16.
> >
> > Yes, this saves an octet, on about 4 packets per connection in the=20
> > common case, more like 2 if you actually take advantage of compound pac=
kets.
> > On Fri, May 18, 2018 at 3:08 PM Marten Seemann=20
> > <martenseemann@gmail.com>
> > wrote:
> >
> > > Jana asked me to raise this issue on the list, after we already=20
> > > had a bit
> > of discussion in https://github.com/quicwg/base-drafts/pull/1301.
> >
> > > The proposal is to make a payload length of 0 a special value,=20
> > > indicating
> > that the packet is not a coalesced packet, i.e. that the whole=20
> > payload of the UDP packet is the QUIC packet. This would eliminate=20
> > an invalid value of the payload length (there are no empty packets),=20
> > save one byte for packet lengths where varint encoding would result=20
> > in a two byte number, and apparently also simplify (some) implementatio=
ns.
> >
> > > Kazuho argued creating two versions of each Long Header type (one=20
> > > with
> > and one without a payload length) is the better solution, since all=20
> > values below the AEAD tag length + 1 are invalid values anyway, and=20
> > it would save one more byte.
> >
> > > We should make a decision if and what we want to do about this.
> >
> >


From nobody Sat May 19 17:50:22 2018
Return-Path: <jri.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5B90C12E890 for <quic@ietfa.amsl.com>; Sat, 19 May 2018 17:50:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 3GmcoZ60omsl for <quic@ietfa.amsl.com>; Sat, 19 May 2018 17:50:17 -0700 (PDT)
Received: from mail-io0-x22c.google.com (mail-io0-x22c.google.com [IPv6:2607:f8b0:4001:c06::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7582F12D96C for <quic@ietf.org>; Sat, 19 May 2018 17:50:17 -0700 (PDT)
Received: by mail-io0-x22c.google.com with SMTP id e78-v6so10488068iod.0 for <quic@ietf.org>; Sat, 19 May 2018 17:50:17 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+L6kTWU5nQqspdyEWMjbuFSJIfQKfa9kEux5b9tOPHw=; b=p2dgn39CDm/K9SFN5+k4IX3M3N2eLfVNhaNXaiFmXHwznu+rPiuImTYQaj8KevqRDw LEmt3hsavZsfMe2oYEQ75w1ZhLUaXsT3BOL8Gs+mz9Wsfa2HA9EIgty16gHvvn/98CNS fKX9b7oEEW8+zFNpw7IUJf5Ez0A+DE/0CYqYPqHHkPup4dTsWTvoz1HX23EEFca2O1Iv rSRbjtdTZ0f1AXER4WVmLnoPGMtiOMf0DRzIkTSx1JJIk9+kAP2Reu0DJvUA7KPP5Vcj PA0xhVnzRR7F4UvcHZ6e65LZahbNwn1RQOcJsevub0CNu/DzOsiYsTpp5aNzUHxAB9O/ 48Fg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+L6kTWU5nQqspdyEWMjbuFSJIfQKfa9kEux5b9tOPHw=; b=ZsWrP37DdsSgm51xcTzZ8X1ArfZ/44ahaM99lyJSCNITVABHjI8PvRA9uQ3wEyr0E2 B9ynB5lVfpFUjL9SWDyxPAl4z6Jg8QtynOhwRK5LWgFwkSnA9PhOveNGONTPmylsBYY6 Xp6T2h9Us1KmsN531ek4azqOsx1gYeu3PFPkGVhNhZXD7HLw6Jts3NmvT39LrZWdbNt8 FCdjLSrzLsC4kgs0e1ZnuNy+RBN4yHMrdXXunD77TxyK6IddpyQbCxfLZ9d8y+/CCdJc bqK1ndc8bsSNMG8zdKELzxn5Z5n/TCKQ6EcqGTvbMRaW7QBWVhjuKDKQe9RrJn8xiH+b Dfhg==
X-Gm-Message-State: ALKqPwcbFvWkFDS3HqbXefIVl+A34FTXOe9tDBwo9SZJpNsq9TmPsNkv O/TkndD6OHN6aX2KwcvgEg3ip4F6l01lNztBMGE=
X-Google-Smtp-Source: AB8JxZq0HJUh3Nu2bj1LVQjlHJ7ehrQ6oLd5GqbKF7U1g+a1OnB9AXzjbWV1hWJVa6kdGffF6kzYtHGfU9jLRbZLEBQ=
X-Received: by 2002:a6b:4119:: with SMTP id n25-v6mr3041281ioa.59.1526777416759;  Sat, 19 May 2018 17:50:16 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:27d4:0:0:0:0:0 with HTTP; Sat, 19 May 2018 17:50:16 -0700 (PDT)
In-Reply-To: <1F436ED13A22A246A59CA374CBC543998B7C712F@ORSMSX111.amr.corp.intel.com>
References: <CAOYVs2q63DpkPZTbw9T24ZcFOxbvrWAGvOtUaHvCuSg_13pSkQ@mail.gmail.com> <CABkgnnWpgyN_OPac-uSKALEaVc8mO_LpT9gAOs-n1eKqso5QAQ@mail.gmail.com> <CAKcm_gMFumNgPq4FxwcgzgDUCvn_jUxb0qk7tAgYZ=LvKfxjfg@mail.gmail.com> <20180518134400.GA12617@ubuntu-dmitri> <1F436ED13A22A246A59CA374CBC543998B7C712F@ORSMSX111.amr.corp.intel.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Sat, 19 May 2018 17:50:16 -0700
Message-ID: <CACpbDcdb6JK_-fmUcKMgbdm0iD2qFvQSVbM74uzo28aShb7H2w@mail.gmail.com>
Subject: Re: Payload length 0
To: "Deval, Manasi" <manasi.deval@intel.com>
Cc: Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Ian Swett <ianswett@google.com>,  Marten Seemann <martenseemann@gmail.com>, IETF QUIC WG <quic@ietf.org>,  Martin Thomson <martin.thomson@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000093bd69056c9891e6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/aXIluFBUjKNnFh0RQz6qR2SaAe4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 May 2018 00:50:21 -0000

--00000000000093bd69056c9891e6
Content-Type: text/plain; charset="UTF-8"

I don't have a strong preference, but a weak one: It seems silly to have a
length field in non-coalesced packets, and non-coalesced packets will be
the common case.

There may be a slightly more compelling reason though. I've been thinking
about optimizing loss recovery for coalesced packets, and I keep running up
against the possibility that a future middlebox might split coalesced QUIC
packets, if it is allowed. I have been thinking about future-proofing
coalesced packets from getting split by such middleboxes (as they do for
TCP), and it occurs to me that a special value of 0 could be used as this
signal. If length is 0, then the packet is coalesced, and otherwise not.
This forces a middlebox to forward coalesced or non-coalesced packets as
they are, without any re-packetization shenanigans.

If folks agree that there's value in this signal, length of 0 may be a neat
way to get it.

On Fri, May 18, 2018 at 7:05 AM, Deval, Manasi <manasi.deval@intel.com>
wrote:

> Agree with keeping payload length in the header.
>
>
> -----Original Message-----
> From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of Dmitri Tikhonov
> Sent: Friday, May 18, 2018 6:44 AM
> To: Ian Swett <ianswett@google.com>
> Cc: Marten Seemann <martenseemann@gmail.com>; IETF QUIC WG <quic@ietf.org>;
> Martin Thomson <martin.thomson@gmail.com>
> Subject: Re: Payload length 0
>
> I agree with Martin and Ian.  We should keep the payload length field and
> its value should be the actual length of the payload.
>
> In addition to being simple, this allows some flexibility when packet
> generattion is far away (in time or code) from actually sending a packet.
> That is to say, it is easier not to have to make the decision which version
> of the payload length value to use when the packet is created.
>
>   - Dmitri.
>
> On Fri, May 18, 2018 at 08:06:01AM -0400, Ian Swett wrote:
> > I would also prefer to not do either of these, because I think it adds
> > complexity and the byte savings are tiny.
> >
> > On Fri, May 18, 2018 at 1:34 AM Martin Thomson
> > <martin.thomson@gmail.com>
> > wrote:
> >
> > > Having just implemented this (and gotten it wrong once), I don't
> > > want more special cases.  Both of these options need extra code.  As
> > > Kazuho points out, filling in a two octet length is trivial.
> > >
> > > It's true that a length of 0 is invalid, but so is 1 through 16.
> > >
> > > Yes, this saves an octet, on about 4 packets per connection in the
> > > common case, more like 2 if you actually take advantage of compound
> packets.
> > > On Fri, May 18, 2018 at 3:08 PM Marten Seemann
> > > <martenseemann@gmail.com>
> > > wrote:
> > >
> > > > Jana asked me to raise this issue on the list, after we already
> > > > had a bit
> > > of discussion in https://github.com/quicwg/base-drafts/pull/1301.
> > >
> > > > The proposal is to make a payload length of 0 a special value,
> > > > indicating
> > > that the packet is not a coalesced packet, i.e. that the whole
> > > payload of the UDP packet is the QUIC packet. This would eliminate
> > > an invalid value of the payload length (there are no empty packets),
> > > save one byte for packet lengths where varint encoding would result
> > > in a two byte number, and apparently also simplify (some)
> implementations.
> > >
> > > > Kazuho argued creating two versions of each Long Header type (one
> > > > with
> > > and one without a payload length) is the better solution, since all
> > > values below the AEAD tag length + 1 are invalid values anyway, and
> > > it would save one more byte.
> > >
> > > > We should make a decision if and what we want to do about this.
> > >
> > >
>
>

--00000000000093bd69056c9891e6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I don&#39;t have a strong preference, but a weak one: It s=
eems silly to have a length field in non-coalesced packets, and non-coalesc=
ed packets will be the common case.<div><br></div><div>There may be a sligh=
tly more compelling reason though. I&#39;ve been thinking about optimizing =
loss recovery for coalesced packets, and I keep running up against the poss=
ibility that a future middlebox might split coalesced QUIC packets, if it i=
s allowed. I have been thinking about future-proofing coalesced packets fro=
m getting split by such middleboxes (as they do for TCP), and it occurs to =
me that a special value of 0 could be used as this signal. If length is 0, =
then the packet is coalesced, and otherwise not. This forces a middlebox to=
 forward coalesced or non-coalesced packets as they are, without any re-pac=
ketization shenanigans.</div><div><br></div><div>If folks agree that there&=
#39;s value in this signal, length of 0 may be a neat way to get it.</div><=
/div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Fri, May =
18, 2018 at 7:05 AM, Deval, Manasi <span dir=3D"ltr">&lt;<a href=3D"mailto:=
manasi.deval@intel.com" target=3D"_blank">manasi.deval@intel.com</a>&gt;</s=
pan> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex=
;border-left:1px #ccc solid;padding-left:1ex">Agree with keeping payload le=
ngth in the header.<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
-----Original Message-----<br>
From: QUIC [mailto:<a href=3D"mailto:quic-bounces@ietf.org">quic-bounces@ie=
tf.org</a>] On Behalf Of Dmitri Tikhonov<br>
Sent: Friday, May 18, 2018 6:44 AM<br>
To: Ian Swett &lt;<a href=3D"mailto:ianswett@google.com">ianswett@google.co=
m</a>&gt;<br>
Cc: Marten Seemann &lt;<a href=3D"mailto:martenseemann@gmail.com">martensee=
mann@gmail.com</a>&gt;; IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org">q=
uic@ietf.org</a>&gt;; Martin Thomson &lt;<a href=3D"mailto:martin.thomson@g=
mail.com">martin.thomson@gmail.com</a>&gt;<br>
Subject: Re: Payload length 0<br>
<br>
I agree with Martin and Ian.=C2=A0 We should keep the payload length field =
and its value should be the actual length of the payload.<br>
<br>
In addition to being simple, this allows some flexibility when packet gener=
attion is far away (in time or code) from actually sending a packet.=C2=A0 =
That is to say, it is easier not to have to make the decision which version=
 of the payload length value to use when the packet is created.<br>
<br>
=C2=A0 - Dmitri.<br>
<br>
On Fri, May 18, 2018 at 08:06:01AM -0400, Ian Swett wrote:<br>
&gt; I would also prefer to not do either of these, because I think it adds=
 <br>
&gt; complexity and the byte savings are tiny.<br>
&gt; <br>
&gt; On Fri, May 18, 2018 at 1:34 AM Martin Thomson <br>
&gt; &lt;<a href=3D"mailto:martin.thomson@gmail.com">martin.thomson@gmail.c=
om</a>&gt;<br>
&gt; wrote:<br>
&gt; <br>
&gt; &gt; Having just implemented this (and gotten it wrong once), I don&#3=
9;t <br>
&gt; &gt; want more special cases.=C2=A0 Both of these options need extra c=
ode.=C2=A0 As <br>
&gt; &gt; Kazuho points out, filling in a two octet length is trivial.<br>
&gt; &gt;<br>
&gt; &gt; It&#39;s true that a length of 0 is invalid, but so is 1 through =
16.<br>
&gt; &gt;<br>
&gt; &gt; Yes, this saves an octet, on about 4 packets per connection in th=
e <br>
&gt; &gt; common case, more like 2 if you actually take advantage of compou=
nd packets.<br>
&gt; &gt; On Fri, May 18, 2018 at 3:08 PM Marten Seemann <br>
&gt; &gt; &lt;<a href=3D"mailto:martenseemann@gmail.com">martenseemann@gmai=
l.com</a>&gt;<br>
&gt; &gt; wrote:<br>
&gt; &gt;<br>
&gt; &gt; &gt; Jana asked me to raise this issue on the list, after we alre=
ady <br>
&gt; &gt; &gt; had a bit<br>
&gt; &gt; of discussion in <a href=3D"https://github.com/quicwg/base-drafts=
/pull/1301" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/=
<wbr>base-drafts/pull/1301</a>.<br>
&gt; &gt;<br>
&gt; &gt; &gt; The proposal is to make a payload length of 0 a special valu=
e, <br>
&gt; &gt; &gt; indicating<br>
&gt; &gt; that the packet is not a coalesced packet, i.e. that the whole <b=
r>
&gt; &gt; payload of the UDP packet is the QUIC packet. This would eliminat=
e <br>
&gt; &gt; an invalid value of the payload length (there are no empty packet=
s), <br>
&gt; &gt; save one byte for packet lengths where varint encoding would resu=
lt <br>
&gt; &gt; in a two byte number, and apparently also simplify (some) impleme=
ntations.<br>
&gt; &gt;<br>
&gt; &gt; &gt; Kazuho argued creating two versions of each Long Header type=
 (one <br>
&gt; &gt; &gt; with<br>
&gt; &gt; and one without a payload length) is the better solution, since a=
ll <br>
&gt; &gt; values below the AEAD tag length + 1 are invalid values anyway, a=
nd <br>
&gt; &gt; it would save one more byte.<br>
&gt; &gt;<br>
&gt; &gt; &gt; We should make a decision if and what we want to do about th=
is.<br>
&gt; &gt;<br>
&gt; &gt;<br>
<br>
</div></div></blockquote></div><br></div>

--00000000000093bd69056c9891e6--


From nobody Sat May 19 18:06:57 2018
Return-Path: <huitema@huitema.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AAB7C120227 for <quic@ietfa.amsl.com>; Sat, 19 May 2018 18:06:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 kJfJW2eaDEIP for <quic@ietfa.amsl.com>; Sat, 19 May 2018 18:06:52 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 8BE411200A0 for <quic@ietf.org>; Sat, 19 May 2018 18:06:52 -0700 (PDT)
Received: from xsmtp12.mail2web.com ([168.144.250.177]) by mx35.antispamcloud.com with esmtps (TLSv1.2:AES128-SHA:128) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1fKCoD-0000Rz-Pj for quic@ietf.org; Sun, 20 May 2018 03:06:50 +0200
Received: from [10.5.2.49] (helo=xmail11.myhosting.com) by xsmtp12.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from <huitema@huitema.net>) id 1fKCoB-0002NP-Nl for quic@ietf.org; Sat, 19 May 2018 21:06:48 -0400
Received: (qmail 2831 invoked from network); 20 May 2018 01:06:43 -0000
Received: from unknown (HELO [192.168.1.106]) (Authenticated-user:_huitema@huitema.net@[172.56.42.66]) (envelope-sender <huitema@huitema.net>) by xmail11.myhosting.com (qmail-ldap-1.03) with ESMTPA for <dtikhonov@litespeedtech.com>; 20 May 2018 01:06:43 -0000
To: Jana Iyengar <jri.ietf@gmail.com>, "Deval, Manasi" <manasi.deval@intel.com>
Cc: Marten Seemann <martenseemann@gmail.com>, Ian Swett <ianswett@google.com>, IETF QUIC WG <quic@ietf.org>, Martin Thomson <martin.thomson@gmail.com>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>
References: <CAOYVs2q63DpkPZTbw9T24ZcFOxbvrWAGvOtUaHvCuSg_13pSkQ@mail.gmail.com> <CABkgnnWpgyN_OPac-uSKALEaVc8mO_LpT9gAOs-n1eKqso5QAQ@mail.gmail.com> <CAKcm_gMFumNgPq4FxwcgzgDUCvn_jUxb0qk7tAgYZ=LvKfxjfg@mail.gmail.com> <20180518134400.GA12617@ubuntu-dmitri> <1F436ED13A22A246A59CA374CBC543998B7C712F@ORSMSX111.amr.corp.intel.com> <CACpbDcdb6JK_-fmUcKMgbdm0iD2qFvQSVbM74uzo28aShb7H2w@mail.gmail.com>
From: Christian Huitema <huitema@huitema.net>
Openpgp: preference=signencrypt
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= xsBNBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAHNJ0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PsLAeQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1bOwE0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAcLBfgQYAQIACQUCUhFfyAIb LgEpCRCTQwmyVcgNcsBdIAQZAQIABgUCUhFfyAAKCRC22tOSFDh1UOlBB/94RsCJepNvmi/c YiNmMnm0mKb6vjv43OsHkqrrCqJSfo95KHyl5Up4JEp8tiJMyYT2mp4IsirZHxz/5lqkw9Az tcGAF3GlFsj++xTyD07DXlNeddwTKlqPRi/b8sppjtWur6Pm+wnAHp0mQ7GidhxHccFCl65w uT7S/ocb1MjrTgnAMiz+x87d48n1UJ7yIdI41Wpg2XFZiA9xPBiDuuoPwFj14/nK0elV5Dvq 4/HVgfurb4+fd74PV/CC/dmd7hg0ZRlgnB5rFUcFO7ywb7/TvICIIaLWcI42OJDSZjZ/MAzz BeXm263lHh+kFxkh2LxEHnQGHCHGpTYyi4Z3dv03HtkH/1SI8joQMQq00Bv+RdEbJXfEExrT u4gtdZAihwvy97OPA2nCdTAHm/phkzryMeOaOztI4PS8u2Ce5lUB6P/HcGtK/038KdX5MYST Fn8KUDt4o29bkv0CUXwDzS3oTzPNtGdryBkRMc9b+yn9+AdwFEH4auhiTQXPMnl0+G3nhKr7 jvzVFJCRif3OAhEm4vmBNDE3uuaXFQnbK56GJrnqVN+KX5Z3M7X3fA8UcVCGOEHXRP/aubiw Ngawj0V9x+43kUapFp+nF69R53UI65YtJ95ec4PTO/Edvap8h1UbdEOc4+TiYwY1TBuIKltY 1cnrjgAWUh/Ucvr++/KbD9tD6C8=
Message-ID: <6c99fb18-f511-7246-e248-466400675e62@huitema.net>
Date: Sat, 19 May 2018 18:06:40 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <CACpbDcdb6JK_-fmUcKMgbdm0iD2qFvQSVbM74uzo28aShb7H2w@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Subject: Re: Payload length 0
X-Originating-IP: 168.144.250.177
X-AntiSpamCloud-Domain: xsmtpout.mail2web.com
X-AntiSpamCloud-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-AntiSpamCloud-Outgoing-Class: unsure
X-AntiSpamCloud-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5hpiqpqsZh6ze181mRiYrx1602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO37pNwwF1lRXh5rzvPzo9Jts1ujulqUFmMITHM77eiVi9yycgTaoevOymOS184Cx587i TvJ2/ZGzVWB9scFAaCdIFaUvXN+CI+RGy3Me16pB6nkU4uouGtaIPSwAALHVjh/TBCf6oYXAWGet lavcAjD9ytQxIHf9lN5jjLJaPK8lRJSPf/SXbEnDSsal/zZzc4n9VZdr7RAFD5mRwooUYhwMPaBP aKeQW+/QlaOdv8isl/qMm08Zpim2AHUKEWvQ6G/bWfgucjnNmABpGhD9TTttrFCuZ0NkwnSz2Luu o1u9uevuNfM1HjkNEFwape+IgNezYqxGMqsKjARq8PBC4qjpVMhqNcdjhoIlgrKzBvjTmdySlZou 9qHIGOZDEEo7Oyc1nq0gsY582CWqKjiRB3ukywmZtiDkyd4mEBjJGGEJgawbllbHk+xyUKopM6rc KCaQX/lIXcRWtobViGg9fpWMTYkVuh1T3D5J+USJRhROnnXm95a0vRtjH3/UwFOlrQUaXQYB2DYu idWXJF5bnGm3B+q+bUHXAsYFgsNREGhlzTFYPIyr5voE3ggyv83xvYRfyCMB4QZToA5YKb0SaS5E llm5CBzrwBATJ22MAarY7TrOwPFJd4XqI4y6kTdZJ07k+vjbEFIODONvVl7uk80S9mtyiCYdmZGV R9AmPbPyYRu94EmF8owAU/QVsB9LQtfH1yALUGC6BHMPRvkcc+0wo4oa20NpWO+vM+mpnwDI9R/2 gMGq0KWAzmMf+ibVDq6QUJiwen3oy/CTqKqDmsuqWKEc9MBxZCWS72/wjopIVAY+3RHRetx4B6Z4 Ei5woFss+n2ffnQxt6aJ7klZab+5U3mWTJPTqb+xVIKqgeO7n3iwosDmKSszPVW9RecIRsxn9uie 2n4+ooHGqAOWILQxL7hrJSk60SF3F6RYOYr2
X-Report-Abuse-To: spam@quarantine6.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/gpaVmTjlQlRq2fLZVbNBEvD9FvQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 May 2018 01:06:55 -0000

On 5/19/2018 5:50 PM, Jana Iyengar wrote:

> There may be a slightly more compelling reason though. I've been
> thinking about optimizing loss recovery for coalesced packets, and I
> keep running up against the possibility that a future middlebox might
> split coalesced QUIC packets, if it is allowed. I have been thinking
> about future-proofing coalesced packets from getting split by such
> middleboxes (as they do for TCP), and it occurs to me that a special
> value of 0 could be used as this signal. If length is 0, then the
> packet is coalesced, and otherwise not. This forces a middlebox to
> forward coalesced or non-coalesced packets as they are, without any
> re-packetization shenanigans.

The only way to prevent middlebox from hacking some part of the protocol
is to use encryption. Any clear text hack will only be a slight road
bump for the middle-box hackers.

For example, if we coalesce a CI and a 0-RTT packet, we could have the
zero RTT encryption depend on the presence of the previous packet.

-- Christian Huitema






From nobody Sat May 19 18:16:11 2018
Return-Path: <jri.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD42E1205F0 for <quic@ietfa.amsl.com>; Sat, 19 May 2018 18:16:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 QN5NzH-db_YG for <quic@ietfa.amsl.com>; Sat, 19 May 2018 18:16:08 -0700 (PDT)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D937E12025C for <quic@ietf.org>; Sat, 19 May 2018 18:16:07 -0700 (PDT)
Received: by mail-io0-x22b.google.com with SMTP id c9-v6so10518180iob.12 for <quic@ietf.org>; Sat, 19 May 2018 18:16:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=tTaDCoWfFNeayNDr6mUfqDk/zbu+dEnZmR9pSTky8Nw=; b=J79NuvM9FiTMqgGoAgw1WxPUIhkunvleUoefinPQgpPPARO3/nFVvltVQI5dsRFiJo O0V/mEJlpvO++7Qvu1tBJ44TUc7szJwXoG1+dfC0ikSMYPQyt6hXjKluAFKYGqJe1we/ HHAGHXRCNTmG8uHy2g1uNhZnl9AtFx2ikusalI9MribnSBuvjKZIgdisbfIrfzBpaIJr QBbdc5sZSJyZUQQow65TXizlKwJYFg+0bdhY71oysLw2uK4pXVJYaP8JBjoy1wUmR7qg p68tY42jNdIWuG9khaOwdP+Fz0/xp52zcybQE0cO+g53vkU+lJj704V1uhEtSKBxyBrO N1dA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=tTaDCoWfFNeayNDr6mUfqDk/zbu+dEnZmR9pSTky8Nw=; b=PDYdhq22fqRN8EA4vQ/eUC2+tzk5ZRrXVyrk7tLBC5toyscI+ZDpwLx61UVknAttyp TC4W6LXk1Sx6jBPQJD5er2tvAOatDrLqPRxKu8StBxFAE9paOUIidEIM4XiuSeEB9e8a 3ez9MWINixnL++49IFcP4rzXrCQQ8JwBhswYq/eJNFcMgSMwUzZqe8902yeeK0YW1NPO Vokj/17VyhXypvNhJh8Yfj/PjwzS/fl86mDXQbep9AGIHd2YPy2sd9M9p8Gl1PbTy7ga usgDgOOoWQUjZvqfIAMnC+CKZMlwlV2RGFOiJVvcQ/7mRmOKkwlnpUS7jX0r9fDPVyKu DEQw==
X-Gm-Message-State: ALKqPwehhkMHyPmXQZZKbeXBFAnE2ralFQFtbb7YG2vPFSeVPdmGz77V b311/Nnv/5/m1fI75l4fMf223KMG2xrmnOEp4b8=
X-Google-Smtp-Source: AB8JxZpZZwOIBvqJsCm4tcdx1e35IHnXtUy9Yg/sd0vXuhDeTc0c6sEtrMrUhjsLlVFD/SztsPqekgSdOrgHewEEjD4=
X-Received: by 2002:a6b:dc12:: with SMTP id s18-v6mr17313297ioc.203.1526778967200;  Sat, 19 May 2018 18:16:07 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:27d4:0:0:0:0:0 with HTTP; Sat, 19 May 2018 18:16:06 -0700 (PDT)
In-Reply-To: <6c99fb18-f511-7246-e248-466400675e62@huitema.net>
References: <CAOYVs2q63DpkPZTbw9T24ZcFOxbvrWAGvOtUaHvCuSg_13pSkQ@mail.gmail.com> <CABkgnnWpgyN_OPac-uSKALEaVc8mO_LpT9gAOs-n1eKqso5QAQ@mail.gmail.com> <CAKcm_gMFumNgPq4FxwcgzgDUCvn_jUxb0qk7tAgYZ=LvKfxjfg@mail.gmail.com> <20180518134400.GA12617@ubuntu-dmitri> <1F436ED13A22A246A59CA374CBC543998B7C712F@ORSMSX111.amr.corp.intel.com> <CACpbDcdb6JK_-fmUcKMgbdm0iD2qFvQSVbM74uzo28aShb7H2w@mail.gmail.com> <6c99fb18-f511-7246-e248-466400675e62@huitema.net>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Sat, 19 May 2018 18:16:06 -0700
Message-ID: <CACpbDcfjDfQP69ZvUNjcUnQBGYKJAEJuh2BMK5dQZ8eRwfzOGQ@mail.gmail.com>
Subject: Re: Payload length 0
To: Christian Huitema <huitema@huitema.net>
Cc: "Deval, Manasi" <manasi.deval@intel.com>, Marten Seemann <martenseemann@gmail.com>,  Ian Swett <ianswett@google.com>, IETF QUIC WG <quic@ietf.org>,  Martin Thomson <martin.thomson@gmail.com>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>
Content-Type: multipart/alternative; boundary="000000000000fd9877056c98ed40"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/GciU20oMxaqyQm-MhjYLWnCskmM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 May 2018 01:16:10 -0000

--000000000000fd9877056c98ed40
Content-Type: text/plain; charset="UTF-8"

>
> The only way to prevent middlebox from hacking some part of the protocol
> is to use encryption. Any clear text hack will only be a slight road
> bump for the middle-box hackers.
>

Agreed, though I'll note that authenticating may be enough in some cases,
encrypting may not be necessary.

For example, if we coalesce a CI and a 0-RTT packet, we could have the
> zero RTT encryption depend on the presence of the previous packet.
>

What I'm suggesting is that the length field, which is part of the
authenticated header, include this signal as zero, or non-zero. I think
this may be one interpretation of what you're saying: the header field,
which is part of the AEAD hash, encodes the presence of another packet.

--000000000000fd9877056c98ed40
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">The only way to prevent middlebox from hacking s=
ome part of the protocol<br>
is to use encryption. Any clear text hack will only be a slight road<br>
bump for the middle-box hackers.<br></blockquote><div><br></div><div>Agreed=
, though I&#39;ll note that authenticating may be enough in some cases, enc=
rypting may not be necessary.</div><div><br></div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left=
:1ex">
For example, if we coalesce a CI and a 0-RTT packet, we could have the<br>
zero RTT encryption depend on the presence of the previous packet.<br></blo=
ckquote><div><br></div><div>What I&#39;m suggesting is that the length fiel=
d, which is part of the authenticated header, include this signal as zero, =
or non-zero. I think this may be one interpretation of what you&#39;re sayi=
ng: the header field, which is part of the AEAD hash, encodes the presence =
of another packet.=C2=A0</div></div></div></div>

--000000000000fd9877056c98ed40--


From nobody Sat May 19 18:37:58 2018
Return-Path: <huitema@huitema.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A07312025C for <quic@ietfa.amsl.com>; Sat, 19 May 2018 18:37:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 EWlPUypV1E6P for <quic@ietfa.amsl.com>; Sat, 19 May 2018 18:37:56 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 58D781200C5 for <quic@ietf.org>; Sat, 19 May 2018 18:37:56 -0700 (PDT)
Received: from xsmtp06.mail2web.com ([168.144.250.232]) by mx44.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1fKDIH-0002Bn-NV for quic@ietf.org; Sun, 20 May 2018 03:37:54 +0200
Received: from [10.5.2.35] (helo=xmail10.myhosting.com) by xsmtp06.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1fKDIF-0003yQ-TL for quic@ietf.org; Sat, 19 May 2018 21:37:52 -0400
Received: (qmail 29267 invoked from network); 20 May 2018 01:37:49 -0000
Received: from unknown (HELO [192.168.1.106]) (Authenticated-user:_huitema@huitema.net@[172.56.42.66]) (envelope-sender <huitema@huitema.net>) by xmail10.myhosting.com (qmail-ldap-1.03) with ESMTPA for <dtikhonov@litespeedtech.com>; 20 May 2018 01:37:49 -0000
To: Jana Iyengar <jri.ietf@gmail.com>
Cc: "Deval, Manasi" <manasi.deval@intel.com>, Marten Seemann <martenseemann@gmail.com>, Ian Swett <ianswett@google.com>, IETF QUIC WG <quic@ietf.org>, Martin Thomson <martin.thomson@gmail.com>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>
References: <CAOYVs2q63DpkPZTbw9T24ZcFOxbvrWAGvOtUaHvCuSg_13pSkQ@mail.gmail.com> <CABkgnnWpgyN_OPac-uSKALEaVc8mO_LpT9gAOs-n1eKqso5QAQ@mail.gmail.com> <CAKcm_gMFumNgPq4FxwcgzgDUCvn_jUxb0qk7tAgYZ=LvKfxjfg@mail.gmail.com> <20180518134400.GA12617@ubuntu-dmitri> <1F436ED13A22A246A59CA374CBC543998B7C712F@ORSMSX111.amr.corp.intel.com> <CACpbDcdb6JK_-fmUcKMgbdm0iD2qFvQSVbM74uzo28aShb7H2w@mail.gmail.com> <6c99fb18-f511-7246-e248-466400675e62@huitema.net> <CACpbDcfjDfQP69ZvUNjcUnQBGYKJAEJuh2BMK5dQZ8eRwfzOGQ@mail.gmail.com>
From: Christian Huitema <huitema@huitema.net>
Openpgp: preference=signencrypt
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= xsBNBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAHNJ0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PsLAeQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1bOwE0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAcLBfgQYAQIACQUCUhFfyAIb LgEpCRCTQwmyVcgNcsBdIAQZAQIABgUCUhFfyAAKCRC22tOSFDh1UOlBB/94RsCJepNvmi/c YiNmMnm0mKb6vjv43OsHkqrrCqJSfo95KHyl5Up4JEp8tiJMyYT2mp4IsirZHxz/5lqkw9Az tcGAF3GlFsj++xTyD07DXlNeddwTKlqPRi/b8sppjtWur6Pm+wnAHp0mQ7GidhxHccFCl65w uT7S/ocb1MjrTgnAMiz+x87d48n1UJ7yIdI41Wpg2XFZiA9xPBiDuuoPwFj14/nK0elV5Dvq 4/HVgfurb4+fd74PV/CC/dmd7hg0ZRlgnB5rFUcFO7ywb7/TvICIIaLWcI42OJDSZjZ/MAzz BeXm263lHh+kFxkh2LxEHnQGHCHGpTYyi4Z3dv03HtkH/1SI8joQMQq00Bv+RdEbJXfEExrT u4gtdZAihwvy97OPA2nCdTAHm/phkzryMeOaOztI4PS8u2Ce5lUB6P/HcGtK/038KdX5MYST Fn8KUDt4o29bkv0CUXwDzS3oTzPNtGdryBkRMc9b+yn9+AdwFEH4auhiTQXPMnl0+G3nhKr7 jvzVFJCRif3OAhEm4vmBNDE3uuaXFQnbK56GJrnqVN+KX5Z3M7X3fA8UcVCGOEHXRP/aubiw Ngawj0V9x+43kUapFp+nF69R53UI65YtJ95ec4PTO/Edvap8h1UbdEOc4+TiYwY1TBuIKltY 1cnrjgAWUh/Ucvr++/KbD9tD6C8=
Message-ID: <90c7800b-2c91-762d-e822-883b45e2f814@huitema.net>
Date: Sat, 19 May 2018 18:37:49 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <CACpbDcfjDfQP69ZvUNjcUnQBGYKJAEJuh2BMK5dQZ8eRwfzOGQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------A62C4BA4F240CF141137E276"
Content-Language: en-US
Subject: Re: Payload length 0
X-Originating-IP: 168.144.250.232
X-AntiSpamCloud-Domain: xsmtpout.mail2web.com
X-AntiSpamCloud-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-AntiSpamCloud-Outgoing-Class: unsure
X-AntiSpamCloud-Outgoing-Evidence: Combined (0.14)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5t1Up7XRR54cx+GdT8NO6Ll602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO37pNwwF1lRXh5rzvPzo9Jts1ujulqUFmMITHM77eiViFrsPPfxhjSZ8nqA7iiQseM7i TvJ2/ZGzVWB9scFAaCdIFaUvXN+CI+RGy3Me16pB+FWCyy3VMwU/Tu6lpkyLYh/TBCf6oYXAWGet lavcAjD9ytQxIHf9lN5jjLJaPK8lRJSPf/SXbEnDSsal/zZzc4n9VZdr7RAFD5mRwooUYhwMPaBP aKeQW+/QlaOdv8isl/qMm08Zpim2AHUKEWvQ6G/bWfgucjnNmABpGhD9TTttrFCuZ0NkwnSz2Luu o1u9uevuNfM1HjkNEFwape+IgNezYqxGMqsKjARq8PBC4qjpVMhqNcdjhoIlgrKzBvjTmdySlZou 9qHIGOZDEEo7Oyc1nq0gsY582CWqKjiRB3ukywmZtiDkyd4mEBjJGGEJgawbllbHk+xyUKopM6rc KCaQX/lIXcRWtobViGg9fpXDzxM5P50wvQiu34cU//edF8FcHzzV3acxBudgYcInbz1OxCAQOm0C UgVSDqPRHtqZ4+t4LK79cWIqQA4tGr3po0jfgLl+Ahd0TIbt0Zij6hgeJ07QR0GiieIKGR3KfdmQ xACKGgjW6av7lJfpYBfZuVGBtJ1DsK23UcLYdhI56FwBl1z1+w2zS/h3e6UiVRfKopHI0+1EANu7 qZk5QEllrHwiKb/DQe75Ta07EfI3+GeqA47D/juB1cx4exzYk7zESTfxsnn+QWY3vu7vIpAn647l NwN4qOsSZg+fYhVZG7jR1X6ZfhgbqJ49KX9lIV7VwaDsyRiTeu4Ip+KAECko9HdE0Smt1e6HZuGs N7RwePAFMvX7q8M4x6bP/gjzw0OFbIWNJOiaifOc2xlkb46Pa4K5MPGI7fF8+j7E9IwdcQR2aish SbQcCCOvcJLn8v/2OKHH5lr9xXvSM4nM3avg
X-Report-Abuse-To: spam@quarantine6.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7kC6hTWLO6_CcFLiZmjOtbqubbs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 May 2018 01:37:58 -0000

This is a multi-part message in MIME format.
--------------A62C4BA4F240CF141137E276
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

On 5/19/2018 6:16 PM, Jana Iyengar wrote:

>     The only way to prevent middlebox from hacking some part of the
>     protocol
>     is to use encryption. Any clear text hack will only be a slight road
>     bump for the middle-box hackers.
>
>
> Agreed, though I'll note that authenticating may be enough in some
> cases, encrypting may not be necessary.
>
>     For example, if we coalesce a CI and a 0-RTT packet, we could have the
>     zero RTT encryption depend on the presence of the previous packet.
>
>
> What I'm suggesting is that the length field, which is part of the
> authenticated header, include this signal as zero, or non-zero. I
> think this may be one interpretation of what you're saying: the header
> field, which is part of the AEAD hash, encodes the presence of another
> packet.

Yes, something like that would work. Maybe a flag in the first octet,
"is coalesced".

Note that, in the plausible CI + 0RTT coalescing, splitting the CI won't
work. It will be too short, and thus rejected by the server.

-- Christian Huitema


--------------A62C4BA4F240CF141137E276
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>On 5/19/2018 6:16 PM, Jana Iyengar wrote:<br>
    </p>
    <blockquote type="cite"
cite="mid:CACpbDcfjDfQP69ZvUNjcUnQBGYKJAEJuh2BMK5dQZ8eRwfzOGQ@mail.gmail.com">
      <div class="moz-text-html" lang="x-unicode">
        <div dir="ltr">
          <div class="gmail_extra">
            <div class="gmail_quote">
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">The
                only way to prevent middlebox from hacking some part of
                the protocol<br>
                is to use encryption. Any clear text hack will only be a
                slight road<br>
                bump for the middle-box hackers.<br>
              </blockquote>
              <div><br>
              </div>
              <div>Agreed, though I'll note that authenticating may be
                enough in some cases, encrypting may not be necessary.</div>
              <div><br>
              </div>
              <blockquote class="gmail_quote" style="margin:0 0 0
                .8ex;border-left:1px #ccc solid;padding-left:1ex">
                For example, if we coalesce a CI and a 0-RTT packet, we
                could have the<br>
                zero RTT encryption depend on the presence of the
                previous packet.<br>
              </blockquote>
              <div><br>
              </div>
              <div>What I'm suggesting is that the length field, which
                is part of the authenticated header, include this signal
                as zero, or non-zero. I think this may be one
                interpretation of what you're saying: the header field,
                which is part of the AEAD hash, encodes the presence of
                another packet. <br>
              </div>
            </div>
          </div>
        </div>
      </div>
    </blockquote>
    <br>
    Yes, something like that would work. Maybe a flag in the first
    octet, "is coalesced". <br>
    <br>
    Note that, in the plausible CI + 0RTT coalescing, splitting the CI
    won't work. It will be too short, and thus rejected by the server.<br>
    <br>
    -- Christian Huitema<br>
    <br>
  </body>
</html>

--------------A62C4BA4F240CF141137E276--


From nobody Sun May 20 00:15:15 2018
Return-Path: <martin.thomson@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 211BA126C2F for <quic@ietfa.amsl.com>; Sun, 20 May 2018 00:15:14 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 9hWXvGiJJZeB for <quic@ietfa.amsl.com>; Sun, 20 May 2018 00:15:12 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89DA0126B72 for <quic@ietf.org>; Sun, 20 May 2018 00:15:12 -0700 (PDT)
Received: by mail-oi0-x229.google.com with SMTP id w123-v6so10526019oia.4 for <quic@ietf.org>; Sun, 20 May 2018 00:15:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=IP/YVUFFJlahkBMZ3CdbDYO91jlQ3/Vug/rYnBzmiEQ=; b=ENtvSZGhVjUWwb9XRFmGfguSfgHvcziroJtoYsCJS4PE0G0EsdLn2x7zkTewsDC3dC IejJgmeN9/yc8VPwwSq92CjxccQoPEgnaag9DD7IwGUWMuKEzgIXb591p3XNDAv+D1Tg Qzc8TeyOddk66X6ph/uBCWMaTyG+38haoq3xrlu6OkSJpGym4yyjR61anrjB4ZPcYNza MYpxAh/lYyDnhWNr/6ZL8/so4FeDgCQ3BnBtqQclgoHQesqwOk5GxZ+QLI/FBbwduemJ 79v9qodRa/qW3Q7ul9XXcMjLQsA1R4tsgZMbRIZ3fhId+kRalPKaRVqrpR1KvMSziGQA Oqjw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=IP/YVUFFJlahkBMZ3CdbDYO91jlQ3/Vug/rYnBzmiEQ=; b=VZm0GPtfHy8SPyGWAcWizKI4g2Jh8HBil8189mtQxoplYSfl3w0NQ7X27TpAWwEnul EQ/tYr/2rntLMJCoErSNcxabSEiArasABgTM7AiKJjqR/aCFHnK1ixYxeYFskPpt7eFY hFmrHkfB7XhkxD+uil7i+I+RERFMCckCih+qnMj6WcYz0ZCkwEHMfPkjEiTcboZYVKW8 8BtU4W+n/3tw3NkmZRm55Ir+LXo4ZnDKM6/CDDCURGTLYNIAxvdTzvMqbkU+KS4E9y1P XfQ4vIrlbzJubRvthTcVmqW4GPA/aij7vStWyjRJXVMxaf9MzrGx6Tm4yBUAEm7qcHJU o8Hg==
X-Gm-Message-State: ALKqPweZd9VpS5cxYwgPC4zfdKqigbl7Qt6ozsOF4xCWC/xydb2i/vIk lJu/WHwEy9L/ZEuLAzc4K7uBOOl2rfiaBchfXwQ=
X-Google-Smtp-Source: AB8JxZpZdCMfqWkuo8dOTHr5Ph20SAKHPMaqVY49oLS4q2qLZSm7i4Asg3IXPd3ZwbDccGpi/9YbmZeCcpMX/JWdrJ4=
X-Received: by 2002:aca:1218:: with SMTP id 24-v6mr6493298ois.144.1526800511735;  Sun, 20 May 2018 00:15:11 -0700 (PDT)
MIME-Version: 1.0
References: <CAOYVs2q63DpkPZTbw9T24ZcFOxbvrWAGvOtUaHvCuSg_13pSkQ@mail.gmail.com> <CABkgnnWpgyN_OPac-uSKALEaVc8mO_LpT9gAOs-n1eKqso5QAQ@mail.gmail.com> <CAKcm_gMFumNgPq4FxwcgzgDUCvn_jUxb0qk7tAgYZ=LvKfxjfg@mail.gmail.com> <20180518134400.GA12617@ubuntu-dmitri> <1F436ED13A22A246A59CA374CBC543998B7C712F@ORSMSX111.amr.corp.intel.com> <CACpbDcdb6JK_-fmUcKMgbdm0iD2qFvQSVbM74uzo28aShb7H2w@mail.gmail.com> <6c99fb18-f511-7246-e248-466400675e62@huitema.net> <CACpbDcfjDfQP69ZvUNjcUnQBGYKJAEJuh2BMK5dQZ8eRwfzOGQ@mail.gmail.com> <90c7800b-2c91-762d-e822-883b45e2f814@huitema.net>
In-Reply-To: <90c7800b-2c91-762d-e822-883b45e2f814@huitema.net>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Sun, 20 May 2018 17:14:59 +1000
Message-ID: <CABkgnnXETJUkghZu=xxLNU7pBiEWmZ5O32bxDR7f_5Fo9SoK1Q@mail.gmail.com>
Subject: Re: Payload length 0
To: Christian Huitema <huitema@huitema.net>
Cc: Jana Iyengar <jri.ietf@gmail.com>, "Deval, Manasi" <manasi.deval@intel.com>, Marten Seemann <martenseemann@gmail.com>, Ian Swett <ianswett@google.com>, QUIC WG <quic@ietf.org>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/KRSyGnCx-4Ssy2_bLW1B0JuNM8g>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 May 2018 07:15:14 -0000

It only works to ensure that the last packet remains the last packet.  That
doesn't seem like an actual defense against splitting.
On Sun, May 20, 2018 at 11:37 AM Christian Huitema <huitema@huitema.net>
wrote:

> On 5/19/2018 6:16 PM, Jana Iyengar wrote:

>> The only way to prevent middlebox from hacking some part of the protocol
>> is to use encryption. Any clear text hack will only be a slight road
>> bump for the middle-box hackers.


> Agreed, though I'll note that authenticating may be enough in some cases,
encrypting may not be necessary.

>> For example, if we coalesce a CI and a 0-RTT packet, we could have the
>> zero RTT encryption depend on the presence of the previous packet.


> What I'm suggesting is that the length field, which is part of the
authenticated header, include this signal as zero, or non-zero. I think
this may be one interpretation of what you're saying: the header field,
which is part of the AEAD hash, encodes the presence of another packet.


> Yes, something like that would work. Maybe a flag in the first octet, "is
coalesced".

> Note that, in the plausible CI + 0RTT coalescing, splitting the CI won't
work. It will be too short, and thus rejected by the server.

> -- Christian Huitema


From nobody Sun May 20 10:44:38 2018
Return-Path: <jri.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D32F212D7F4 for <quic@ietfa.amsl.com>; Sun, 20 May 2018 10:44:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 DeewlCFJyzDw for <quic@ietfa.amsl.com>; Sun, 20 May 2018 10:44:34 -0700 (PDT)
Received: from mail-it0-x236.google.com (mail-it0-x236.google.com [IPv6:2607:f8b0:4001:c0b::236]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AEE0512D7F2 for <quic@ietf.org>; Sun, 20 May 2018 10:44:34 -0700 (PDT)
Received: by mail-it0-x236.google.com with SMTP id e20-v6so18702598itc.1 for <quic@ietf.org>; Sun, 20 May 2018 10:44:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=JGtU4J4+mADyNO3zYsUlDLH656WQw04hRbNLS0bAO5o=; b=RDsdraDX7vHtFsFhCxsqaq9QSfUc2N1sax7AadVPXth1If/l9E1vEWNv04tQTysAFm /74q1OBznYHY5EZ2Bvs5WdmbWdP/WIdCY1AK1mIHD+x60MtILyX3SrWh1zrZJIwRMrAu T4O9xQJ7ahPBhm0uvkQpAhNYO5OOn8c0Ru+2zdmzRGrVNu1cw4iNLmdPVv1znVLbeufV sw2d/f0DK7FF7x6NjE+dGdYB2jQfwM2Qd3UMoux15HBcpfR01iigcTrkeSP9d80e7WKy EKCylTdp+o8RC/DDR0x/hrccN4tqEmyEu0a23InnCiIijV9629Gm9tijF2wr45QLAJd8 zZPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=JGtU4J4+mADyNO3zYsUlDLH656WQw04hRbNLS0bAO5o=; b=akPQyMm+xYwXlwzFChND6wsf/4NpKPH6r0Zlmv5Hw3pwcSPglln8nst/CT05UOtUeU cF4PSnfMoKDVMW0cm4QodNC41j4EMrfquDc+rKlCNv0TVW70f/s7pEefzwijWNjJ4n5q 2lxUlO3RucltAUr/9KtTiVul+GutZ01L8EpfYPuRmepzkk5NSHN067EMVtoZa5WM3x5M 4dJy9DJ31Jllwz9fJt7o2XGKnmz7HrLsEDBnxOhcGAHnsHN4UkeOk5fCHzIQVHUuA/x0 qVpNnK09F39FDINL4kHdVOBRf5bZI7MBElPMXITTgaXNK3TxtstYxvMVLBbQGmkk0liX pXow==
X-Gm-Message-State: ALKqPwdF/u3UDD9KfYKNxZ7YuTrJaX52Lzfmf3BlBxYbinjz9E/kE455 zrmUnqdqnkYkCEvS+sQZmGqUEFjN8lwmv5/oZP0=
X-Google-Smtp-Source: AB8JxZpzYeGjMhufySb7owTXxPzvHnSvKYQQCYSysind+GdMI6GLCOnFMsKWpyGmBlvE1iAmD/9JX2MLWTjkBOOPnTA=
X-Received: by 2002:a24:36ca:: with SMTP id l193-v6mr14691689itl.103.1526838273974;  Sun, 20 May 2018 10:44:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:27d4:0:0:0:0:0 with HTTP; Sun, 20 May 2018 10:44:33 -0700 (PDT)
In-Reply-To: <CABkgnnXETJUkghZu=xxLNU7pBiEWmZ5O32bxDR7f_5Fo9SoK1Q@mail.gmail.com>
References: <CAOYVs2q63DpkPZTbw9T24ZcFOxbvrWAGvOtUaHvCuSg_13pSkQ@mail.gmail.com> <CABkgnnWpgyN_OPac-uSKALEaVc8mO_LpT9gAOs-n1eKqso5QAQ@mail.gmail.com> <CAKcm_gMFumNgPq4FxwcgzgDUCvn_jUxb0qk7tAgYZ=LvKfxjfg@mail.gmail.com> <20180518134400.GA12617@ubuntu-dmitri> <1F436ED13A22A246A59CA374CBC543998B7C712F@ORSMSX111.amr.corp.intel.com> <CACpbDcdb6JK_-fmUcKMgbdm0iD2qFvQSVbM74uzo28aShb7H2w@mail.gmail.com> <6c99fb18-f511-7246-e248-466400675e62@huitema.net> <CACpbDcfjDfQP69ZvUNjcUnQBGYKJAEJuh2BMK5dQZ8eRwfzOGQ@mail.gmail.com> <90c7800b-2c91-762d-e822-883b45e2f814@huitema.net> <CABkgnnXETJUkghZu=xxLNU7pBiEWmZ5O32bxDR7f_5Fo9SoK1Q@mail.gmail.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Sun, 20 May 2018 10:44:33 -0700
Message-ID: <CACpbDccLRXZZc4G=Z2dk62fK5heu_MhSUX4pqtQefSQgmDPSKw@mail.gmail.com>
Subject: Re: Payload length 0
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Christian Huitema <huitema@huitema.net>, "Deval, Manasi" <manasi.deval@intel.com>,  Marten Seemann <martenseemann@gmail.com>, Ian Swett <ianswett@google.com>, QUIC WG <quic@ietf.org>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>
Content-Type: multipart/alternative; boundary="000000000000f325ec056ca6bc26"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/OAJz_OTABKlYupkMTYPv6OiS4yM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 May 2018 17:44:37 -0000

--000000000000f325ec056ca6bc26
Content-Type: text/plain; charset="UTF-8"

Just to be clear about what I'm suggesting:

Packets that are coalesced in a UDP datagram have their length fields set
to the packet length. Packets that are not coalesced set the packet length
to zero.
A receiver that sees a non-zero packet length field in a long header checks
if this packet is coalesced. Similarly, a packet that is received with a
zero in the packet length field must be not coalesced.

I believe this protects from splitting.

CFIN+1RTT packets can also be coalesced in addition to CI+0RTT.

On Sun, May 20, 2018 at 12:14 AM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> It only works to ensure that the last packet remains the last packet.  That
> doesn't seem like an actual defense against splitting.
> On Sun, May 20, 2018 at 11:37 AM Christian Huitema <huitema@huitema.net>
> wrote:
>
> > On 5/19/2018 6:16 PM, Jana Iyengar wrote:
>
> >> The only way to prevent middlebox from hacking some part of the protocol
> >> is to use encryption. Any clear text hack will only be a slight road
> >> bump for the middle-box hackers.
>
>
> > Agreed, though I'll note that authenticating may be enough in some cases,
> encrypting may not be necessary.
>
> >> For example, if we coalesce a CI and a 0-RTT packet, we could have the
> >> zero RTT encryption depend on the presence of the previous packet.
>
>
> > What I'm suggesting is that the length field, which is part of the
> authenticated header, include this signal as zero, or non-zero. I think
> this may be one interpretation of what you're saying: the header field,
> which is part of the AEAD hash, encodes the presence of another packet.
>
>
> > Yes, something like that would work. Maybe a flag in the first octet, "is
> coalesced".
>
> > Note that, in the plausible CI + 0RTT coalescing, splitting the CI won't
> work. It will be too short, and thus rejected by the server.
>
> > -- Christian Huitema
>

--000000000000f325ec056ca6bc26
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Just to be clear about what I&#39;m suggesting:<div><br></=
div><div>Packets that are coalesced in a UDP datagram have their length fie=
lds set to the packet length. Packets that are not coalesced set the packet=
 length to zero.</div><div>A receiver that sees a non-zero packet length fi=
eld in a long header checks if this packet is coalesced. Similarly, a packe=
t that is received with a zero in the packet length field must be not coale=
sced.<br></div><div><br></div><div>I believe this protects from splitting.<=
/div><div><br></div><div>CFIN+1RTT packets can also be coalesced in additio=
n to CI+0RTT.</div></div><div class=3D"gmail_extra"><br><div class=3D"gmail=
_quote">On Sun, May 20, 2018 at 12:14 AM, Martin Thomson <span dir=3D"ltr">=
&lt;<a href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.th=
omson@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" =
style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It =
only works to ensure that the last packet remains the last packet.=C2=A0 Th=
at<br>
doesn&#39;t seem like an actual defense against splitting.<br>
On Sun, May 20, 2018 at 11:37 AM Christian Huitema &lt;<a href=3D"mailto:hu=
itema@huitema.net">huitema@huitema.net</a>&gt;<br>
wrote:<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
&gt; On 5/19/2018 6:16 PM, Jana Iyengar wrote:<br>
<br>
&gt;&gt; The only way to prevent middlebox from hacking some part of the pr=
otocol<br>
&gt;&gt; is to use encryption. Any clear text hack will only be a slight ro=
ad<br>
&gt;&gt; bump for the middle-box hackers.<br>
<br>
<br>
&gt; Agreed, though I&#39;ll note that authenticating may be enough in some=
 cases,<br>
encrypting may not be necessary.<br>
<br>
&gt;&gt; For example, if we coalesce a CI and a 0-RTT packet, we could have=
 the<br>
&gt;&gt; zero RTT encryption depend on the presence of the previous packet.=
<br>
<br>
<br>
&gt; What I&#39;m suggesting is that the length field, which is part of the=
<br>
authenticated header, include this signal as zero, or non-zero. I think<br>
this may be one interpretation of what you&#39;re saying: the header field,=
<br>
which is part of the AEAD hash, encodes the presence of another packet.<br>
<br>
<br>
&gt; Yes, something like that would work. Maybe a flag in the first octet, =
&quot;is<br>
coalesced&quot;.<br>
<br>
&gt; Note that, in the plausible CI + 0RTT coalescing, splitting the CI won=
&#39;t<br>
work. It will be too short, and thus rejected by the server.<br>
<br>
&gt; -- Christian Huitema<br>
</div></div></blockquote></div><br></div>

--000000000000f325ec056ca6bc26--


From nobody Sun May 20 11:00:26 2018
Return-Path: <huitema@huitema.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ADEBE12D80E for <quic@ietfa.amsl.com>; Sun, 20 May 2018 11:00:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 R3jop4j83wTv for <quic@ietfa.amsl.com>; Sun, 20 May 2018 11:00:22 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 B3B5B12D7FC for <quic@ietf.org>; Sun, 20 May 2018 11:00:22 -0700 (PDT)
Received: from xsmtp06.mail2web.com ([168.144.250.232]) by mx63.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1fKSd2-000BvK-C1 for quic@ietf.org; Sun, 20 May 2018 20:00:21 +0200
Received: from [10.5.2.18] (helo=xmail08.myhosting.com) by xsmtp06.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1fKScz-00055r-6P for quic@ietf.org; Sun, 20 May 2018 14:00:17 -0400
Received: (qmail 25644 invoked from network); 20 May 2018 18:00:14 -0000
Received: from unknown (HELO [192.168.1.106]) (Authenticated-user:_huitema@huitema.net@[172.56.42.66]) (envelope-sender <huitema@huitema.net>) by xmail08.myhosting.com (qmail-ldap-1.03) with ESMTPA for <manasi.deval@intel.com>; 20 May 2018 18:00:14 -0000
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Jana Iyengar <jri.ietf@gmail.com>, Ian Swett <ianswett@google.com>, Marten Seemann <martenseemann@gmail.com>, QUIC WG <quic@ietf.org>, "Deval, Manasi" <manasi.deval@intel.com>
References: <CAOYVs2q63DpkPZTbw9T24ZcFOxbvrWAGvOtUaHvCuSg_13pSkQ@mail.gmail.com> <CABkgnnWpgyN_OPac-uSKALEaVc8mO_LpT9gAOs-n1eKqso5QAQ@mail.gmail.com> <CAKcm_gMFumNgPq4FxwcgzgDUCvn_jUxb0qk7tAgYZ=LvKfxjfg@mail.gmail.com> <20180518134400.GA12617@ubuntu-dmitri> <1F436ED13A22A246A59CA374CBC543998B7C712F@ORSMSX111.amr.corp.intel.com> <CACpbDcdb6JK_-fmUcKMgbdm0iD2qFvQSVbM74uzo28aShb7H2w@mail.gmail.com> <6c99fb18-f511-7246-e248-466400675e62@huitema.net> <CACpbDcfjDfQP69ZvUNjcUnQBGYKJAEJuh2BMK5dQZ8eRwfzOGQ@mail.gmail.com> <90c7800b-2c91-762d-e822-883b45e2f814@huitema.net> <CABkgnnXETJUkghZu=xxLNU7pBiEWmZ5O32bxDR7f_5Fo9SoK1Q@mail.gmail.com>
From: Christian Huitema <huitema@huitema.net>
Openpgp: preference=signencrypt
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= xsBNBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAHNJ0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PsLAeQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1bOwE0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAcLBfgQYAQIACQUCUhFfyAIb LgEpCRCTQwmyVcgNcsBdIAQZAQIABgUCUhFfyAAKCRC22tOSFDh1UOlBB/94RsCJepNvmi/c YiNmMnm0mKb6vjv43OsHkqrrCqJSfo95KHyl5Up4JEp8tiJMyYT2mp4IsirZHxz/5lqkw9Az tcGAF3GlFsj++xTyD07DXlNeddwTKlqPRi/b8sppjtWur6Pm+wnAHp0mQ7GidhxHccFCl65w uT7S/ocb1MjrTgnAMiz+x87d48n1UJ7yIdI41Wpg2XFZiA9xPBiDuuoPwFj14/nK0elV5Dvq 4/HVgfurb4+fd74PV/CC/dmd7hg0ZRlgnB5rFUcFO7ywb7/TvICIIaLWcI42OJDSZjZ/MAzz BeXm263lHh+kFxkh2LxEHnQGHCHGpTYyi4Z3dv03HtkH/1SI8joQMQq00Bv+RdEbJXfEExrT u4gtdZAihwvy97OPA2nCdTAHm/phkzryMeOaOztI4PS8u2Ce5lUB6P/HcGtK/038KdX5MYST Fn8KUDt4o29bkv0CUXwDzS3oTzPNtGdryBkRMc9b+yn9+AdwFEH4auhiTQXPMnl0+G3nhKr7 jvzVFJCRif3OAhEm4vmBNDE3uuaXFQnbK56GJrnqVN+KX5Z3M7X3fA8UcVCGOEHXRP/aubiw Ngawj0V9x+43kUapFp+nF69R53UI65YtJ95ec4PTO/Edvap8h1UbdEOc4+TiYwY1TBuIKltY 1cnrjgAWUh/Ucvr++/KbD9tD6C8=
Message-ID: <b7cff98c-1e8b-6be5-3a93-804f6da28cc7@huitema.net>
Date: Sun, 20 May 2018 11:00:11 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <CABkgnnXETJUkghZu=xxLNU7pBiEWmZ5O32bxDR7f_5Fo9SoK1Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Subject: Re: Payload length 0
X-Originating-IP: 168.144.250.232
X-AntiSpamCloud-Domain: xsmtpout.mail2web.com
X-AntiSpamCloud-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-AntiSpamCloud-Outgoing-Class: unsure
X-AntiSpamCloud-Outgoing-Evidence: Combined (0.16)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5kcOQvVtAxNT1uHFUilEr6l602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO37pNwwF1lRXh5rzvPzo9Jts1ujulqUFmMITHM77eiVidSLt+zomffPyByYhEwPioc7i TvJ2/ZGzVWB9scFAaCdIFaUvXN+CI+RGy3Me16pB4lampmfDNuiABFovtjnMdR/TBCf6oYXAWGet lavcAjD9ytQxIHf9lN5jjLJaPK8lRJSPf/SXbEnDSsal/zZzc4n9VZdr7RAFD5mRwooUYhwMPaBP aKeQW+/QlaOdv8isl/qMm08Zpim2AHUKEWvQ6G/bWfgucjnNmABpGhD9TTttrFCuZ0NkwnSz2Luu o1u9uevuNfM1HjkNEFwape+IgNezYqxGMqsKjARq8PBC4qjpVMhqNcdjhoIlgrKzBvjTmdySlZou 9qHIGOZDEEo7Oyc1nq0gsY582CWqKjiRB3ukywmZtiDkyd4mEBjJGGEJgawbllbHk+xyUKopM6rc KCaQX/lIXcRWtobViGg9fpX6N+2DyDXes8vYD17nJ00F1plJbJWyV2fhV11O+/8dD1nu99v86e+x KzdeJi5RoGhz1HQkoj+jjvmw3UQ3Zextr+7/jg66NXUoieIpLIJirIV7hPvBDpgDmC+XXO9ws5qS dbWrmlMqpoC2dVXCySAVi5bZXEudL3ieMOBM2bJNcVYE7tCqypI5WX0qWh4YQLAxL4Rl2gqNEBWr ilTpbNR2br8Ks0SqCpRWIiXMtOo8/pI8jnU4taLGlA8rnD8bXLXYENHEHdfH4WKtOnkQjvURQKHY 6H+wSCoVvwvquzDDiAFgqbLsMBS3CSu0TYW/KPOYdub/YU/cH64QiTAnRDmAKMFEHS3+vt/Njsed NDmPw/Ld14/y82ebPziYNS9mrGcHWFhVQvKDd9aHm1tzPaYBnxycJOQKmrvtOUL1jquCMfd5HnMi k4ibTRVHi8subW0=
X-Report-Abuse-To: spam@quarantine6.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/vzeFFz8z1jHCb7DCaIdlp-9_gaQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 20 May 2018 18:00:25 -0000

On 5/20/2018 12:14 AM, Martin Thomson wrote:

> It only works to ensure that the last packet remains the last packet.  =
That
> doesn't seem like an actual defense against splitting.

I have been thinking of the middle-box hacks that could interfere with
packet coalescing, trying to build a threat model. I am not sure I can't
come with convincing attacks, or rather with convincing attacks that we
can defend against. For me the main coalescing scenarios are:

1) Client Initial (Client Hello) + 0Rtt.

2) Server Handshake (first flight) + 1Rtt.

3) Client Handshake (second flight) + 1Rtt

What would be the motivation for splitting? In the CI+0-RTT case, the
middlebox designer might have heard that 0Rtt is insecure, and might
sell blocking 0RTT as a feature. It might want to pass the CI and block
the 0Rtt. This can be done in many ways. Flipping a couple bits in the
0Rtt payload would achieve that -- decryption would fail, and the 0Rtt
will be ignored. Or, unwrap the coalesced packet, decrypt the CI using
the well known key, add padding to reach the min size, and reencrypt
using the well known key. Tweaking the long header is not going to fix
either of these hacks.

In the Server Handshake + 1Rtt case, the motivation might be similar:
prevent 0.5Rtt transmission because it is arguably insecure. Again, this
can be achieved by flipping bits in the 1Rtt payload to cause a
decryption error, or unwrapping and reformatting the handshake packet.
Since the handshake is only "protected" by a well known key, this is
still possible, even if we added some kind of coalescing indication in
the short header of the 1Rtt data.

In the Client Handshake + 1Rtt case, I fail to find a motivation. But
evil middlebox designers could invent something. Again, if the goal is
to remove the 1Rtt packet, tweaking the headers of that packet won't help=
=2E

If we did want to remove the attack, we would have to protect the
coalescing indication with a key that is unknown to the middlebox. That
probably requires an encrypted extension to the client hello, server
hello or finished messages. we could do that, but I wonder whether
that's worth the effort.

-- Christian Huitema


From nobody Tue May 22 02:31:18 2018
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6159812E876 for <quic@ietfa.amsl.com>; Tue, 22 May 2018 02:31:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 FYbWzi39X6pW for <quic@ietfa.amsl.com>; Tue, 22 May 2018 02:31:09 -0700 (PDT)
Received: from sesbmg22.ericsson.net (sesbmg22.ericsson.net [193.180.251.48]) (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 505E812E866 for <quic@ietf.org>; Tue, 22 May 2018 02:31:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1526981467; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=VG6xpXG8vQLyWwMu8teQT960+ijcO6mkTirjR+dy05k=; b=C4reZn44Pt4RtWoNblEevS4eocQeCTi/7dw4ON8OT69rIrmG/RPQbLtC0l1Qbi86 hpGzHwNPEVAP/ke5rPz0Ro64lCme/wKrjs822L4O5+BHmxk0/YJhE5dF8Fc4nufW 9ND0kQbItaxPSuvszqG70bb/Kmc4E7SDSXWHuoGDLOE=;
X-AuditID: c1b4fb30-263479c00000169b-b2-5b03e35bd5f6
Received: from ESESSHC005.ericsson.se (Unknown_Domain [153.88.183.33]) by sesbmg22.ericsson.net (Symantec Mail Security) with SMTP id 45.EF.05787.B53E30B5; Tue, 22 May 2018 11:31:07 +0200 (CEST)
Received: from [147.214.160.12] (153.88.183.153) by smtps.internal.ericsson.com (153.88.183.33) with Microsoft SMTP Server (TLS) id 14.3.382.0; Tue, 22 May 2018 11:30:57 +0200
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Questions regarding the handshake sequence
To: IETF QUIC WG <quic@ietf.org>
Message-ID: <4582ce45-d016-1eda-46f9-57cf868c5f3d@ericsson.com>
Date: Tue, 22 May 2018 11:30:56 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
X-Originating-IP: [153.88.183.153]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrGLMWRmVeSWpSXmKPExsUyM2K7om70Y+Zog/sb5Cx6FnA7MHosWfKT KYAxissmJTUnsyy1SN8ugSvj/OerbAWXuCsmPfzI3sC4lrOLkZNDQsBEYvbDCUxdjFwcQgJH GCVePrgE5WxmlJh2/zcLSBWbgIXEzR+NbCC2sICxRM/zVYxdjBwcIgIKEmsawAbxCthL/Lh+ ggUkzCKgKvHggi9IWFQgRuLH0S4WiBJBiZMzn4CVMAOVP9haBhJmFpCX2P52DjOELS7R9GUl K4gtJKAt0dDUwQpxppLE9XnXWSYw8s9CMmkWwqRZSCbNQjJpASPLKkbR4tTipNx0IyO91KLM 5OLi/Dy9vNSSTYzA0Du45bfBDsaXzx0PMQpwMCrx8AoeY44WYk0sK67MPcQowcGsJML76RJT tBBvSmJlVWpRfnxRaU5q8SFGaQ4WJXFeC7/NUUIC6YklqdmpqQWpRTBZJg5OqQZGRp0tJ9Lf xqsdqtjHIf4mcX5/4JKSCCPTTNmXn3htPrBc7dlTcWjbbx69Y89/H3HrXjjrQtae876uWX0M Z9+bCOtIfxAJ6XYoPsNlt8SA7W96fv+N/0cYbE6k/Hy5rP9fT/2OdRsbQm+c4RBLN/tmJJPG LvDj3ELe5dyGc3gUr5n56m/7O3u7EktxRqKhFnNRcSIAMAAkVTkCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/9omTDHzDgxRe97Zs8h7ZwcvN_WM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2018 09:31:17 -0000

Hi,

Reviewing the transport draft -11 I get a bit confused about what 
possible combination of packets type that can occur during the 
handshaking. Thus, I would appreciate some clarifications.

First a sequence with a HelloRetryRequest

C -> S: Initial PN=0, ClientHello

S-> C: Retry Packet PN=0, HelloRetryRequest, ACK (0)

C -> s: Initial PN=1, ClientHello

S -> C: Handshake Packet PN=0, ServerHello, ACK (0,1)

C -> S: ? PN=2, Client Finished, Data Frame, ACK (0)

So in this sequence, in what type of packet is the client sending its 
Client Finished message?

Secondly, In the Handshake packet, is the server using PN=0 again. Spec 
text appear to indicate that, but I get uncertain.

And I understand correctly this is also a valid sequence:

C -> S: Initial PN=0, ClientHello

S -> C: Handshake Packet PN=0, ServerHello, ACK (0)

C-> S: ? PN=1, Client Finished, Data frame, ACK(0)

Also here, it is unclear which packet type the client uses in its second 
message.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Network Architecture & Protocols, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Tue May 22 03:27:09 2018
Return-Path: <martin.thomson@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0236612EADE for <quic@ietfa.amsl.com>; Tue, 22 May 2018 03:27:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 fpwWgz1uzZa7 for <quic@ietfa.amsl.com>; Tue, 22 May 2018 03:27:06 -0700 (PDT)
Received: from mail-oi0-x235.google.com (mail-oi0-x235.google.com [IPv6:2607:f8b0:4003:c06::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EBFA512EAD4 for <quic@ietf.org>; Tue, 22 May 2018 03:27:05 -0700 (PDT)
Received: by mail-oi0-x235.google.com with SMTP id w123-v6so15701004oia.4 for <quic@ietf.org>; Tue, 22 May 2018 03:27:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=0GIUYXUDt+WlL3HG08NnQSceO3Lp6CPgzpE2nU/u9ZU=; b=p6ju9C+6aIgDGV/4a8diR7cuKtF2lkEI5tIyF4PZEeEDdmK+J5srDXQbDDHilOua/Y Lm2hj5qvNOAwzfJyWWFLznD5+SeI1MSdPxBn8nIG6iMeqUorUR8bC2BLgfh/fTJ2F/PS Eg+aUw5b1rNU/cwLYDftKq+Ijixr+7tgCHvt5Zut4MZuuqUveMlXd2d9SjH6owDgAsr9 c1P/b2kBUDjzruB2lnzP+nGsAAV/aNCXrTzoRVlu31z8S9Xez9QIycmxMuG/Yt5KxNdb xxJkD3FTm3IaqcRqPj7lN17mmzQ3aky11JMWN/EI4c89N2ksF215F1pmPQNIqeOW3cZG jWmA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=0GIUYXUDt+WlL3HG08NnQSceO3Lp6CPgzpE2nU/u9ZU=; b=cj+9jEq9C8jz5I4bpg2vo6HRlSd1XE8OexA0mm01fCYfcdcDD3da1fIwTjPU1PTE4T pHH6vpMFXOPWSf/HUIsl6iyGKUjsBB7hySqMD898thomGSbWKJ61rSHPUAYcM4n4fseG wt7xZLDE139IepZx+jz9i6/UF2RpLEKZeHtt55frLrkqacN+U1+s2CD0CL0DF6rrY5DU H6NDBWTAGOFwozt5ygWVDVIf/gzQ/PSFhZ9Pf1GWYL0OwM9cadRCKttxZ9LkLMTLf2G1 pAGCsZPpryoNM+mUuOtOzxLiVk0cZi6Pff9scxMaUtJvyKy0q+BqfvAS7ZAYdmeXPuCP +4TQ==
X-Gm-Message-State: ALKqPwf0Zak6VcXgaUUwcrtd+XCyNzJdGYPEaMYeYggWwH4PZXEueskZ /xrqAin4JiZVXyJoVrBRLMCKwk+x4wUUSslhZPR2peRJ
X-Google-Smtp-Source: AB8JxZrr80I7dWBftEcu3He5n5YPcKfJylTq39NyLWvBpIRu/3P2MEcBrp3ruLKH4L7lrLPUgi+kOfXBg3/U+290e5Y=
X-Received: by 2002:aca:ebd4:: with SMTP id j203-v6mr14580281oih.110.1526984825099;  Tue, 22 May 2018 03:27:05 -0700 (PDT)
MIME-Version: 1.0
References: <4582ce45-d016-1eda-46f9-57cf868c5f3d@ericsson.com>
In-Reply-To: <4582ce45-d016-1eda-46f9-57cf868c5f3d@ericsson.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Tue, 22 May 2018 20:26:53 +1000
Message-ID: <CABkgnnVRM5Rd+6j3YghGbvcZaJo82rTnhr1Z6vDJkt8Hh0tDtQ@mail.gmail.com>
Subject: Re: Questions regarding the handshake sequence
To: Magnus Westerlund <magnus.westerlund@ericsson.com>
Cc: QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/8ukzEYwzDAa5ZhAK5YIb4KfTeAM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2018 10:27:08 -0000

Hmm, yes, that could be clearer.  Does this help?

https://github.com/quicwg/base-drafts/pull/1368
On Tue, May 22, 2018 at 7:31 PM Magnus Westerlund <
magnus.westerlund@ericsson.com> wrote:

> Hi,

> Reviewing the transport draft -11 I get a bit confused about what
> possible combination of packets type that can occur during the
> handshaking. Thus, I would appreciate some clarifications.

> First a sequence with a HelloRetryRequest

> C -> S: Initial PN=0, ClientHello

> S-> C: Retry Packet PN=0, HelloRetryRequest, ACK (0)

> C -> s: Initial PN=1, ClientHello

> S -> C: Handshake Packet PN=0, ServerHello, ACK (0,1)

> C -> S: ? PN=2, Client Finished, Data Frame, ACK (0)

> So in this sequence, in what type of packet is the client sending its
> Client Finished message?

> Secondly, In the Handshake packet, is the server using PN=0 again. Spec
> text appear to indicate that, but I get uncertain.

> And I understand correctly this is also a valid sequence:

> C -> S: Initial PN=0, ClientHello

> S -> C: Handshake Packet PN=0, ServerHello, ACK (0)

> C-> S: ? PN=1, Client Finished, Data frame, ACK(0)

> Also here, it is unclear which packet type the client uses in its second
> message.

> Cheers

> Magnus Westerlund

> ----------------------------------------------------------------------
> Network Architecture & Protocols, Ericsson Research
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> Torshamnsgatan 23           | Mobile +46 73 0949079
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------


From nobody Tue May 22 04:39:35 2018
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 55C6812EB18 for <quic@ietfa.amsl.com>; Tue, 22 May 2018 04:39:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.31
X-Spam-Level: 
X-Spam-Status: No, score=-4.31 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 0Ix0wCvNYUd2 for <quic@ietfa.amsl.com>; Tue, 22 May 2018 04:39:31 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 CC8DF12EB15 for <quic@ietf.org>; Tue, 22 May 2018 04:39:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1526989169; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:CC:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=Ygaon08HilF1IgocTVPTWrI8p9ch2FbpjFFGAFlbjO0=; b=WXxO2UPxolRUGF5RP8AQtmZuWYKhrHWgOuNQkJH75SSFqLMwKvTOwR2xOBcRWYcO xK1exzZ33VbZm6LudtrVQxPiY3ZpySg58ljCzb7wD2XXoWi0A9Y3teINwk1o2p88 +eFy0mQmGe8USpIx2Gngflf18YpE0JSB3+KbKchukGM=;
X-AuditID: c1b4fb3a-01cc39c00000033e-6c-5b040170d04e
Received: from ESESSHC002.ericsson.se (Unknown_Domain [153.88.183.24]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id 22.19.00830.071040B5; Tue, 22 May 2018 13:39:29 +0200 (CEST)
Received: from [147.214.160.12] (153.88.183.153) by smtps.internal.ericsson.com (153.88.183.24) with Microsoft SMTP Server (TLS) id 14.3.382.0; Tue, 22 May 2018 13:39:27 +0200
Subject: Re: Questions regarding the handshake sequence
To: Martin Thomson <martin.thomson@gmail.com>
CC: QUIC WG <quic@ietf.org>
References: <4582ce45-d016-1eda-46f9-57cf868c5f3d@ericsson.com> <CABkgnnVRM5Rd+6j3YghGbvcZaJo82rTnhr1Z6vDJkt8Hh0tDtQ@mail.gmail.com>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Message-ID: <cdc630ce-83fc-1e07-2061-aabd676a8b33@ericsson.com>
Date: Tue, 22 May 2018 13:39:27 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.7.0
MIME-Version: 1.0
In-Reply-To: <CABkgnnVRM5Rd+6j3YghGbvcZaJo82rTnhr1Z6vDJkt8Hh0tDtQ@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
X-Originating-IP: [153.88.183.153]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrBLMWRmVeSWpSXmKPExsUyM2K7hG4hI0u0we19LBbXzvxjtOhZwO3A 5LFz1l12jyVLfjIFMEVx2aSk5mSWpRbp2yVwZTy68Yyp4KFkxeJG9gbGvyJdjJwcEgImEt// /2DtYuTiEBI4wigx99FpKGczo8TS13PZQKqEBcwlvk3ZygJiiwjoSiw6+4AdxGYWkJZo6r/D BtHQxigx/+s+VpAEm4CFxM0fjWDNvAL2Eq231oE1sAioSnQcPMMIYosKxEj8ONrFAlEjKHFy 5hMwm1MgUGLRhSlsEAssJGbOP88IYctLNG+dzQxhi0s0fVkJtktIQFuioamDFeIdJYnr866z TGAUmoVk7Cwko2YhGTULyagFjCyrGEWLU4uLc9ONjPRSizKTi4vz8/TyUks2MQLD++CW31Y7 GA8+dzzEKMDBqMTDK/CfOVqINbGsuDL3EKMEB7OSCO+nS0zRQrwpiZVVqUX58UWlOanFhxil OViUxHmd0iyihATSE0tSs1NTC1KLYLJMHJxSDYxuHeULT7Avbyhe8iTan3Fp3D45xlni2Ud3 9F9p+czVUeR2d5dfroirUNn9nQlVUk+ydj+584ple1lLxNbSgtMRWh4TnW6bXGnjW/GtRVDE TK6jRul6TYzOpf3z5n6u+bhHQ8jk15zkubddnvqlZkw6tkPa6UrDn4vpXA72Xy+HuX16yTF3 X40SS3FGoqEWc1FxIgA5A9x8awIAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/QOG_FWWjOpXuHSRYO8pZ0s8uLSk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2018 11:39:34 -0000

Thanks,

Yes, that is clearer for that aspect.

Which I think leads to the next unclarity. Non-handshake packets are 
protected packets. And to my understanding there exists two types of 
these. Short packets and 0-RTT packets.  However, the initial paragraph 
in Section 4.5 is a bit confusing here:

    All QUIC packets are protected.  Packets that are protected with the
    static handshake keys or the 0-RTT keys are sent with long headers;
    all packets protected with 1-RTT keys are sent with short headers.
    The different packet types explicitly indicate the encryption level
    and therefore the keys that are used to remove packet protection.

This fails to make the distinction between the concept of the protected 
packet, i.e. a non handshake packet and the fact that yes all packets 
have some type of protection. And I do wonder if that first sentence is 
in fact wrong as Init packets don't really are protected in the same way 
as Protected Packets.

Cheers

Magnus

Den 2018-05-22 kl. 12:26, skrev Martin Thomson:
> Hmm, yes, that could be clearer.  Does this help?
>
> https://github.com/quicwg/base-drafts/pull/1368
> On Tue, May 22, 2018 at 7:31 PM Magnus Westerlund <
> magnus.westerlund@ericsson.com> wrote:
>
>> Hi,
>> Reviewing the transport draft -11 I get a bit confused about what
>> possible combination of packets type that can occur during the
>> handshaking. Thus, I would appreciate some clarifications.
>> First a sequence with a HelloRetryRequest
>> C -> S: Initial PN=0, ClientHello
>> S-> C: Retry Packet PN=0, HelloRetryRequest, ACK (0)
>> C -> s: Initial PN=1, ClientHello
>> S -> C: Handshake Packet PN=0, ServerHello, ACK (0,1)
>> C -> S: ? PN=2, Client Finished, Data Frame, ACK (0)
>> So in this sequence, in what type of packet is the client sending its
>> Client Finished message?
>> Secondly, In the Handshake packet, is the server using PN=0 again. Spec
>> text appear to indicate that, but I get uncertain.
>> And I understand correctly this is also a valid sequence:
>> C -> S: Initial PN=0, ClientHello
>> S -> C: Handshake Packet PN=0, ServerHello, ACK (0)
>> C-> S: ? PN=1, Client Finished, Data frame, ACK(0)
>> Also here, it is unclear which packet type the client uses in its second
>> message.
>> Cheers
>> Magnus Westerlund
>> ----------------------------------------------------------------------
>> Network Architecture & Protocols, Ericsson Research
>> ----------------------------------------------------------------------
>> Ericsson AB                 | Phone  +46 10 7148287
>> Torshamnsgatan 23           | Mobile +46 73 0949079
>> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
>> ----------------------------------------------------------------------

-- 

Magnus Westerlund

----------------------------------------------------------------------
Network Architecture & Protocols, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Tue May 22 15:43:22 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 74CC7127077; Tue, 22 May 2018 15:43:20 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-transport-12.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.80.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152702900042.27129.8429011093238069313@ietfa.amsl.com>
Date: Tue, 22 May 2018 15:43:20 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/EryY1fd3gzhW6-XTQRktM5QfLSo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2018 22:43:21 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the QUIC WG of the IETF.

        Title           : QUIC: A UDP-Based Multiplexed and Secure Transport
        Authors         : Jana Iyengar
                          Martin Thomson
	Filename        : draft-ietf-quic-transport-12.txt
	Pages           : 107
	Date            : 2018-05-22

Abstract:
   This document defines the core of the QUIC transport protocol.  This
   document describes connection establishment, packet format,
   multiplexing and reliability.  Accompanying documents describe the
   cryptographic handshake and loss detection.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-transport/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-transport-12
https://datatracker.ietf.org/doc/html/draft-ietf-quic-transport-12

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-transport-12


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue May 22 15:43:51 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C7B7E12E9DC; Tue, 22 May 2018 15:43:34 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-http-12.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.80.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152702901476.26817.6859856275602594600@ietfa.amsl.com>
Date: Tue, 22 May 2018 15:43:34 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/yG4e9Lw53HHvss6GCdC8gU9L0IE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2018 22:43:45 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the QUIC WG of the IETF.

        Title           : Hypertext Transfer Protocol (HTTP) over QUIC
        Author          : Mike Bishop
	Filename        : draft-ietf-quic-http-12.txt
	Pages           : 38
	Date            : 2018-05-22

Abstract:
   The QUIC transport protocol has several features that are desirable
   in a transport for HTTP, such as stream multiplexing, per-stream flow
   control, and low-latency connection establishment.  This document
   describes a mapping of HTTP semantics over QUIC.  This document also
   identifies HTTP/2 features that are subsumed by QUIC, and describes
   how HTTP/2 extensions can be ported to QUIC.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-http/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-http-12
https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-12

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-http-12


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue May 22 15:48:06 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 4E7A6127077; Tue, 22 May 2018 15:47:57 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-recovery-12.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.80.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152702927727.26946.8384916470472332985@ietfa.amsl.com>
Date: Tue, 22 May 2018 15:47:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/gBMXL38TQ0RAX8T817HR0SRu_SI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2018 22:47:58 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the QUIC WG of the IETF.

        Title           : QUIC Loss Detection and Congestion Control
        Authors         : Jana Iyengar
                          Ian Swett
	Filename        : draft-ietf-quic-recovery-12.txt
	Pages           : 30
	Date            : 2018-05-22

Abstract:
   This document describes loss detection and congestion control
   mechanisms for QUIC.

Note to Readers

   Discussion of this draft takes place on the QUIC working group
   mailing list (quic@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/search/?email_list=quic [1].

   Working Group information can be found at https://github.com/quicwg
   [2]; source code and issues list for this draft can be found at
   https://github.com/quicwg/base-drafts/labels/-recovery [3].


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-recovery/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-recovery-12
https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-12

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-recovery-12


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue May 22 15:50:18 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id C133A127077; Tue, 22 May 2018 15:50:15 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-tls-12.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.80.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152702941572.26880.2414546241621168164@ietfa.amsl.com>
Date: Tue, 22 May 2018 15:50:15 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/9ng9Nv96W4Lhj4eHQaAhcAitS4k>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2018 22:50:16 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the QUIC WG of the IETF.

        Title           : Using Transport Layer Security (TLS) to Secure QUIC
        Authors         : Martin Thomson
                          Sean Turner
	Filename        : draft-ietf-quic-tls-12.txt
	Pages           : 42
	Date            : 2018-05-22

Abstract:
   This document describes how Transport Layer Security (TLS) is used to
   secure QUIC.

Note to Readers

   Discussion of this draft takes place on the QUIC working group
   mailing list (quic@ietf.org), which is archived at
   https://mailarchive.ietf.org/arch/search/?email_list=quic [1].

   Working Group information can be found at https://github.com/quicwg
   [2]; source code and issues list for this draft can be found at
   https://github.com/quicwg/base-drafts/labels/-tls [3].


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-tls/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-tls-12
https://datatracker.ietf.org/doc/html/draft-ietf-quic-tls-12

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-tls-12


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue May 22 16:44:02 2018
Return-Path: <martin.thomson@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5250E12751F for <quic@ietfa.amsl.com>; Tue, 22 May 2018 16:44:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 r_fWUWXfTWsA for <quic@ietfa.amsl.com>; Tue, 22 May 2018 16:43:59 -0700 (PDT)
Received: from mail-ot0-x22b.google.com (mail-ot0-x22b.google.com [IPv6:2607:f8b0:4003:c0f::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B5706127201 for <quic@ietf.org>; Tue, 22 May 2018 16:43:59 -0700 (PDT)
Received: by mail-ot0-x22b.google.com with SMTP id t1-v6so23038906ott.13 for <quic@ietf.org>; Tue, 22 May 2018 16:43:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=zj16L41tgfIRM67eSrm1k7YPicZhs144XUVmzyBuluU=; b=NXwsUpMZBaPC4f9YE6QeDSuYxFAT2/25Yej1+ZtoFTLyUc7I5FrU/38bU3HAKgo9wu CSgz5xU0JnfJFQ8MHPRuC2jb9EyUUxg9d1NfEuTScVF2oDn6wnbiqMGn9lyTMc8fXcHx Od+c/Z6+HsxvC4zsFohrfi1BzfbOpyTy4PtfxI6dXmyGwGB/n4r9u541jTJB3QV8+1aV 8YDT7QT8tjYnK+Sa1rKL83eGiQRLqa62QGNGmcIw86QgFbUNOmpNB65mw656CnXBi+2P e6hnHplebP0w6QgpAo9Dbmldo2/dW6OHLEtW3GmYPgdCW5+ReFl+23ERantzM5RTbyrz aGyQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=zj16L41tgfIRM67eSrm1k7YPicZhs144XUVmzyBuluU=; b=NKCBkZCEIpAvfupXX3Lur1YBonsf5QJqUVG3ofx4NFiQgacPeJZB8Di7boRgsOtBxK MRzp1Vb8rDVvvnBDN8vImHFUXbyCUf8sdo5std38wn4+tcADcTvCMdPZJzjN92zyTbu+ 61BdEUtd++ISM2O8gBdCM//E8hB//RCJn6FNOTg0jvh4ouGubBGjYaatbkayVFUPUJX9 Ald+5P87WWsFHSFzOfYtnKiotO+1vfm7Ltcrg8Dj1nk9x9eipSBBn3Pk9e9+E+ruAdBe 6xZhbF7ySsPHC7SrB2pFM5TwCsH6WhtxJuUVv0F3cnksSbP1737/eGSdM2i95omeGkkL 6LbQ==
X-Gm-Message-State: ALKqPweAQcJ1zXv/5ZcHZU1oOvzEJbBuAscis39uMx/83MZywzY/9xmE 80AjiHy4U0S0e13l2BGcLcJHdcL+Y8kbuuRKIDgVbg==
X-Google-Smtp-Source: AB8JxZrUL3wFWPJ+kv5KSxXbQO0c0O4zMJtHKobRADNz8lGI7+MxsvhCp5iCAKJoKVI13BY7Z3OXqUmNzIbF45NMoiU=
X-Received: by 2002:a9d:3a65:: with SMTP id j92-v6mr377181otc.352.1527032638841;  Tue, 22 May 2018 16:43:58 -0700 (PDT)
MIME-Version: 1.0
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 23 May 2018 09:43:49 +1000
Message-ID: <CABkgnnWt-OgU4_X0Kx5SwzAwe4VmM5Md6cMqgdWmUqLNx4wDYQ@mail.gmail.com>
Subject: -12 drafts out
To: QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/72fw8CgDc-lwXuzCguONpvO_uC4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 22 May 2018 23:44:01 -0000

As you can see, the -12 drafts are out.  The qpack-00 draft should appear
too once chairs approve.

There are tons of changes in qpack, but very few in the others.  The main
change that implementations considering an update have to manage is packet
number encryption.  The editors thought that it might be good to establish
a baseline for the interim.  Thus, it will be assumed that people have at
least a passing familiarity with these drafts.

For those looking to interop, there is a poll on the quicdev slack that
asks if the target should move to -12.  Thus far, it seems like we'll be
sticking with -11.


From nobody Tue May 22 18:31:04 2018
Return-Path: <ianswett@google.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 32E89129C6D for <quic@ietfa.amsl.com>; Tue, 22 May 2018 18:31:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.5
X-Spam-Level: 
X-Spam-Status: No, score=-17.5 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, T_KAM_HTML_FONT_INVALID=0.01, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 gGWZ1EYtQJkw for <quic@ietfa.amsl.com>; Tue, 22 May 2018 18:31:00 -0700 (PDT)
Received: from mail-yb0-x22a.google.com (mail-yb0-x22a.google.com [IPv6:2607:f8b0:4002:c09::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DDE6A12778E for <quic@ietf.org>; Tue, 22 May 2018 18:30:59 -0700 (PDT)
Received: by mail-yb0-x22a.google.com with SMTP id g140-v6so7050445ybf.6 for <quic@ietf.org>; Tue, 22 May 2018 18:30:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to:cc; bh=YerQzNrgGwI+UlX0qMD7bZvu5lwemILvmfVW5AsZTGI=; b=M9YeC6r1NtIOC2ibJyNG97cV1vvBCD25v1bSMb4azYw0JWzj9u+AMUnsNK0rz6tz+t 0YduMAYnY/UUS+7H4tM0oyUbbpJiV94gq/cEpoc0W+YAH9NJj6pA1KZcXy6RwXMvItPc QXDjXnvcMQwdYdqB2Vu0QTX6lIni3o6CbmkNJ41z2wts8qnFbfCA8r+3qxQ+CNGabRqV M5Xrjxcfgx2eMQEjkcyfghWKzeFRpxctysGHVhvLZO3UDO0gp3eWlAKqWc6uFi+uyXHR RqIRNce9rocYtj9vXHMapRhHMZYxyWTbRv916jKgPaOEt96glhsNgf7ygtO+6ZZDFftI yzOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=YerQzNrgGwI+UlX0qMD7bZvu5lwemILvmfVW5AsZTGI=; b=tzjhB8eyUNXaMQTGe3diRieWNrHmCUXuJrXD1lHat9LXYnN2fIOPLrvP/yQphmULvl 3jPzQY4DZrGkhX6loyGiW0C6IbOZHEer9tlNDxh2XLuwlVsAz4/PQV+n208UMi3/sgkO lvKVNrghbEo6NQehR7DXoUND76ysHqNzyYgRAYME8V+mFIK7wUAiwS3UJ/cp9RSsThrW +Y29bsBu8NN7lPf4V0Bxs8BMNAAyRgNwvU1jD4KDwZBqekTm2h9NNCvf9QcPVfUrh/nT d2n0lKsPPq/IbXcV91874G0cT0UR7F4oXgZiSzRDyHxouLj4s7ZqmVucg9uUL4j4aj+T bm5Q==
X-Gm-Message-State: ALKqPwfAADklvlF3bBVd3MZfcwo37AkQRDWR3Ohp+0fjmh7NDJbW9QUk 4DDq1hxiWmBgV18uIuIS/qVxorknsIV791GDP9Gb2CAnGsc=
X-Google-Smtp-Source: AB8JxZpd8y+hgZmAca5AUTX2JYQCZSwUFB4E606+s2MNn+abANev6sBeV/2PvSPgGMJe9FPZ5uBzk4Dz9yvf+tgJ2mY=
X-Received: by 2002:a5b:b01:: with SMTP id z1-v6mr444563ybp.241.1527039057190;  Tue, 22 May 2018 18:30:57 -0700 (PDT)
MIME-Version: 1.0
From: Ian Swett <ianswett@google.com>
Date: Tue, 22 May 2018 21:30:45 -0400
Message-ID: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com>
Subject: Stream0 Design Team Proposal
To: IETF QUIC WG <quic@ietf.org>
Cc: Eric Rescorla <ekr@mozilla.com>
Content-Type: multipart/alternative; boundary="00000000000090d3fc056cd57cd4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/x6aEQN4snTkyx7CP0I-j3_EWYlM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 01:31:02 -0000

--00000000000090d3fc056cd57cd4
Content-Type: text/plain; charset="UTF-8"

*Dear QUIC WG,On behalf of the Stream 0 Design Team, I am pleased to report
that we have consensus on a proposed approach to share with the WG. The
DT's proposal will make QUIC and TLS work closer together and incorporates
ideas from DTLS, but it does not use the DTLS protocol itself. The DT
believes this solves the important open Stream 0 issues. The proposal will
be a bit more invasive in TLS, but we believe it is the right long-term
direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and Mint) are
willing and able to do the work necessary. A number of stacks are currently
working on implementations of this new approach, which we hope to have in
time for the Interim meeting.A design document describing the overall
approach can be found
at:https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit
<https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit>A
PR making the changes to the QUIC documents can be found
at:https://github.com/quicwg/base-drafts/pull/1377
<https://github.com/ekr/base-drafts/pull/29>A few design details did not
have clear consensus, but it was felt it would be better to discuss those
in the wider WG than delay the design team.  A consistent choice was made
in the PR and these issues are mentioned in Appendix B of the design doc.As
always, comments and questions welcome. That said, this is a big PR and we
recognize that some editorial work is going to be needed before merging. In
the interest of letting people follow along, and to keep github from
falling over, we ask people to keep discussion on the mailing list and
refrain from making PR comments.See you in Kista!*
Ian and Eric

--00000000000090d3fc056cd57cd4
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><b style=3D"font-weight:normal" id=3D"gmail-docs-internal-=
guid-2a62f340-8a8f-9073-5cad-25b8001e52b3"><p dir=3D"ltr" style=3D"line-hei=
ght:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;fo=
nt-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:4=
00;font-style:normal;font-variant:normal;text-decoration:none;vertical-alig=
n:baseline;white-space:pre-wrap">Dear QUIC WG,</span></p><br><p dir=3D"ltr"=
 style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D=
"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transpa=
rent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:=
none;vertical-align:baseline;white-space:pre-wrap">On behalf of the Stream =
0 Design Team, I am pleased to report that we have consensus on a proposed =
approach to share with the WG. The DT&#39;s proposal will make QUIC and TLS=
 work closer together and incorporates ideas from DTLS, but it does not use=
 the DTLS protocol itself. </span></p><br><p dir=3D"ltr" style=3D"line-heig=
ht:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;fon=
t-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:40=
0;font-style:normal;font-variant:normal;text-decoration:none;vertical-align=
:baseline;white-space:pre-wrap">The DT believes this solves the important o=
pen Stream 0 issues. The proposal will be a bit more invasive in TLS, but w=
e believe it is the right long-term direction and several TLS stacks (Borin=
gSSL, PicoTLS, NSS, and Mint) are willing and able to do the work necessary=
. A number of stacks are currently working on implementations of this new a=
pproach, which we hope to have in time for the Interim meeting.</span></p><=
br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0p=
t"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);backgro=
und-color:transparent;font-weight:400;font-style:normal;font-variant:normal=
;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">A desig=
n document describing the overall approach can be found at:</span></p><p di=
r=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span=
 style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-colo=
r:transparent;font-weight:400;font-style:normal;font-variant:normal;text-de=
coration:none;vertical-align:baseline;white-space:pre-wrap"><a href=3D"http=
s://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8=
/edit">https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxd=
dT93j6SwHY8/edit</a></span></p><br><p dir=3D"ltr" style=3D"line-height:1.38=
;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-famil=
y:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-=
style:normal;font-variant:normal;text-decoration:none;vertical-align:baseli=
ne;white-space:pre-wrap">A PR making the changes to the QUIC documents can =
be found at:</span></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:=
0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal=
;font-variant:normal;text-decoration:none;vertical-align:baseline;white-spa=
ce:pre-wrap"><a href=3D"https://github.com/ekr/base-drafts/pull/29">https:/=
/github.com/quicwg/base-drafts/pull/1377</a></span></p><br><p dir=3D"ltr" s=
tyle=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"f=
ont-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transpare=
nt;font-weight:400;font-style:normal;font-variant:normal;text-decoration:no=
ne;vertical-align:baseline;white-space:pre-wrap">A few design details did n=
ot have clear consensus, but it was felt it would be better to discuss thos=
e in the wider WG than delay the design team.=C2=A0 A consistent choice was=
 made in the PR and these issues are mentioned in Appendix B of the design =
doc.</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;=
margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rg=
b(0,0,0);background-color:transparent;font-weight:400;font-style:normal;fon=
t-variant:normal;text-decoration:none;vertical-align:baseline;white-space:p=
re-wrap">As always, comments and questions welcome. That said, this is a bi=
g PR and we recognize that some editorial work is going to be needed before=
 merging. In the interest of letting people follow along, and to keep githu=
b from falling over, we ask people to keep discussion on the mailing list a=
nd refrain from making PR comments.</span></p><br><p dir=3D"ltr" style=3D"l=
ine-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:=
11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-w=
eight:400;font-style:normal;font-variant:normal;text-decoration:none;vertic=
al-align:baseline;white-space:pre-wrap">See you in Kista!</span></p></b><br=
 class=3D"gmail-Apple-interchange-newline">Ian and Eric</div>

--00000000000090d3fc056cd57cd4--


From nobody Tue May 22 20:00:55 2018
Return-Path: <martin.thomson@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D040512895E for <quic@ietfa.amsl.com>; Tue, 22 May 2018 20:00:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 lItVSoH8P_4D for <quic@ietfa.amsl.com>; Tue, 22 May 2018 20:00:51 -0700 (PDT)
Received: from mail-ot0-x22f.google.com (mail-ot0-x22f.google.com [IPv6:2607:f8b0:4003:c0f::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 792591200C1 for <quic@ietf.org>; Tue, 22 May 2018 20:00:51 -0700 (PDT)
Received: by mail-ot0-x22f.google.com with SMTP id m11-v6so23489432otf.3 for <quic@ietf.org>; Tue, 22 May 2018 20:00:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=lmsrWj28kzYvWDcTxlu1R5aUUqf/CVX6nbMtaI3V/I4=; b=IEJRgv88I9I9FXU4tiLaDC76hSZBvwIIeysnyxwYhBMLjR1n0uRbPmF7eTnPimb7zd DOLMSep+GexBKFlRg8pD3lapEDKFxd5jTH79/cM+uQQXMH0MH76pknCSoWTrHVDXSlWx SV8j69+Ggkl0pvKmKHC63WxSAaFK++fH907jmyE69b3HoT/t1qvr6j4N45Wzrc+9s4Q3 1PHFySOKtypv+hLeGTg5hr+B/ImJMFbgU0Sc4sEvhC8JSm8hvLcTmrKvsCtkORfIj4d/ 73XQRzC+JgWlYwZIZvnuMkd6wfl/dYBA2AXMkbffS0TKsLBJ9jl4H4fKeiWk3te8e5ml Kv/w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=lmsrWj28kzYvWDcTxlu1R5aUUqf/CVX6nbMtaI3V/I4=; b=Holnco0ZOg5XFHdVAneBcdhUez88oO+bce8TNBt+GoAK9BZS3QtndxEfMdSyKavxWv zxqt7c2v56HEcDQo9Iwb5OYnaFoIPMgWyXGbi0ks9aXlTus1DXrAP/NAXcxWPL7DXIs7 Vntq0/9cSWl8feuA0uDKseZ+8ubMs91LUjWylBU44zBc3J88swtX9baT3FVf31KOHgGq uF6sK/PT/6cxymNg1otgJIimi5NZyraRdeN18F4ahcXCvR5ZTj09eHGZgmnPnmtwydJt glcM9wGjRWeMa8uachpux7/BqEIIa9LtQgo5oNOjoz64XVlb6VeEns/tBoDn4ofqC4vg 3EqQ==
X-Gm-Message-State: ALKqPwegvsNjOXRLlNethJ/sOY3eVkaYWmcSwY7zhO1Jv1czCmdog2az 7kG+pvuQwaLolIpAIn7BUl0NWZBdBJCzyTYbfV3n2UwW
X-Google-Smtp-Source: AB8JxZozKF6Ecq/cSuTyt24DeXJgIWz6RRIXeLjpTkCdSjkj8qMiMISd5sRKBK1gAl8jMmLDkR68MUIX8NJHtgiRGU0=
X-Received: by 2002:a9d:3a65:: with SMTP id j92-v6mr705026otc.352.1527044450663;  Tue, 22 May 2018 20:00:50 -0700 (PDT)
MIME-Version: 1.0
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com>
In-Reply-To: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 23 May 2018 13:00:40 +1000
Message-ID: <CABkgnnUB=jqwFzb2rjBHUFzOgu0hX0YUgaf5kW5ENNGKP+mGiA@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Cc: QUIC WG <quic@ietf.org>, ekr@mozilla.com
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/nFKFDp_ksux2Ocji28vFh33e3Pw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 03:00:54 -0000

First of all, thanks to the design team for the work they have done.  I
haven't digested everything yet, but I think that I have a good sense of
the shape of the proposal.

Overall, this looks like a workable design.  It's a lot more invasive of
the cryptographic handshake implementation than I had thought people were
willing to stomach originally.  But it's clear that we've run into problems
with the current, more abstract API and this is a fairly natural way to
split TLS.  I've spent a little time thinking about how this might be
implemented and I think that it's not going to be *too* painful.  The proof
will be in the pudding there though.

In looking at the PR, I really appreciate seeing all the changes together.
BTW, the link above points to the wrong PR, so be careful (it appears to
have the same content, but that's not guaranteed).  The actual PR is here:
https://github.com/quicwg/base-drafts/pull/1377

I've pushed a branch to the main repo so that you can preview the entire
document set: https://quicwg.github.io/base-drafts/stream0/

It seems like there are some core changes here and a bunch of separable or
at least secondary changes.  I'm sure that each one has its own
justification, but that isn't always clear. The following changes seem like
they are separable:

* The use of separate packet number spaces
* The Retry packet changes (and NEW_TOKEN)
* EMPTY_ACK
* The TLS extension for flow control

Right now, some of these appear to be entirely gratuitous.  I'd like to get
to the bottom of each before we continue.

At a minimum, the PR we land first should include just the core changes.
As you say, reviewing a monster PR like this will only make GitHub weep
unicorns, but we might be able to cut this into smaller pieces.

On Wed, May 23, 2018 at 11:31 AM Ian Swett <ianswett=
40google.com@dmarc.ietf.org> wrote:

> Dear QUIC WG,


> On behalf of the Stream 0 Design Team, I am pleased to report that we
have consensus on a proposed approach to share with the WG. The DT's
proposal will make QUIC and TLS work closer together and incorporates ideas
from DTLS, but it does not use the DTLS protocol itself.


> The DT believes this solves the important open Stream 0 issues. The
proposal will be a bit more invasive in TLS, but we believe it is the right
long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and
Mint) are willing and able to do the work necessary.. A number of stacks
are currently working on implementations of this new approach, which we
hope to have in time for the Interim meeting.


> A design document describing the overall approach can be found at:


https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit


> A PR making the changes to the QUIC documents can be found at:

> https://github.com/quicwg/base-drafts/pull/1377


> A few design details did not have clear consensus, but it was felt it
would be better to discuss those in the wider WG than delay the design
team.  A consistent choice was made in the PR and these issues are
mentioned in Appendix B of the design doc.


> As always, comments and questions welcome. That said, this is a big PR
and we recognize that some editorial work is going to be needed before
merging. In the interest of letting people follow along, and to keep github
from falling over, we ask people to keep discussion on the mailing list and
refrain from making PR comments.


> See you in Kista!


> Ian and Eric


From nobody Tue May 22 20:26:13 2018
Return-Path: <prvs=86810e156b=subodh@fb.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5DF6712895E for <quic@ietfa.amsl.com>; Tue, 22 May 2018 20:26:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, T_DKIMWL_WL_MED=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=NSnSFJ98; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=Ekk4MkdS
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 VRQHxQFZE2d7 for <quic@ietfa.amsl.com>; Tue, 22 May 2018 20:26:10 -0700 (PDT)
Received: from mx0b-00082601.pphosted.com (mx0b-00082601.pphosted.com [67.231.153.30]) (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 BAFA612DA02 for <quic@ietf.org>; Tue, 22 May 2018 20:26:09 -0700 (PDT)
Received: from pps.filterd (m0109331.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w4N3NPbm023637; Tue, 22 May 2018 20:26:05 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=facebook; bh=0q5LYYOLfthgLsFV7hJ4rKDnJr8lV+zro2b00S1R8+s=; b=NSnSFJ980jKYHoVybsCrDkttxp/eVy5XwO426UdIHYM7iy38OJZDOw7ib1zB3kJ60aU4 t0kKm8fh87dlWkdIXs6K+T5Ppq1sjShGbDi3QDOOCBtl8u7AVO00Bddt8Whow5y2dTnq WUVQQgYXuam90ZzTmHjyETZPM1rXQQnjnlI= 
Received: from mail.thefacebook.com ([199.201.64.23]) by mx0a-00082601.pphosted.com with ESMTP id 2j4wnp099k-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Tue, 22 May 2018 20:26:05 -0700
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (192.168.54.28) by o365-in.thefacebook.com (192.168.16.19) with Microsoft SMTP Server (TLS) id 14.3.361.1; Tue, 22 May 2018 20:26:02 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=0q5LYYOLfthgLsFV7hJ4rKDnJr8lV+zro2b00S1R8+s=; b=Ekk4MkdSIABPsZJpovcp1MdkDKDx3Sn8H6O3WSuqpng8hYgyzYEhc5AiMcxBlGbI89KZlFfrwABZxfJXSLs9E/hgGfajC7lJjZ6+E1NCLCeA3TIfUwRBXtf7DImwDO4uOggM+YFRb/n9acMV9l+3Jw9CVpVtW63GXGQ32L8oGUI=
Received: from MWHPR15MB1821.namprd15.prod.outlook.com (10.174.255.137) by MWHPR15MB1150.namprd15.prod.outlook.com (10.175.2.16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.776.11; Wed, 23 May 2018 03:26:02 +0000
Received: from MWHPR15MB1821.namprd15.prod.outlook.com ([fe80::808f:5749:11db:a6a4]) by MWHPR15MB1821.namprd15.prod.outlook.com ([fe80::808f:5749:11db:a6a4%18]) with mapi id 15.20.0776.019; Wed, 23 May 2018 03:26:01 +0000
From: Subodh Iyengar <subodh@fb.com>
To: Martin Thomson <martin.thomson@gmail.com>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
CC: "ekr@mozilla.com" <ekr@mozilla.com>, QUIC WG <quic@ietf.org>
Subject: Re: Stream0 Design Team Proposal
Thread-Topic: Stream0 Design Team Proposal
Thread-Index: AQHT8jXGhBLiPTEoUE2u+pT4iGJsEaQ8oAoAgAAGHGg=
Date: Wed, 23 May 2018 03:26:01 +0000
Message-ID: <MWHPR15MB1821F33BAB20815A38EB34A2B66B0@MWHPR15MB1821.namprd15.prod.outlook.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com>,  <CABkgnnUB=jqwFzb2rjBHUFzOgu0hX0YUgaf5kW5ENNGKP+mGiA@mail.gmail.com>
In-Reply-To: <CABkgnnUB=jqwFzb2rjBHUFzOgu0hX0YUgaf5kW5ENNGKP+mGiA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2620:10d:c090:180::1:55f1]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MWHPR15MB1150; 7:igmfl40zA50gpJrcPMMREAQPCH8vPTv7ZgG/p7FeeOBfIMUHhc8z+Iu+mSYvLUBPyzwwtRO1esia87bHEcznMTfwrY2Pdk7K7hujGDEi8taJwJeQ98BWdF396YTmon3s2HlhTccgrScRHErtoW2961/bHhMCyEbwLkALcxez7YVX1RzIbAf04hthITnyZwcrcqSvKbXxuM9jMu4jHtZ7mDQa5Db07Qp9NJKnCCQi6OcI1r9vEU9TJoiOWaQHw38/; 20:wiL+P0gZYVOqoSg0Lqs/WhT5CeAlSMcgJ0ZjIVfbHs8nl/AUoTPswyZbESrLoe9dTKuJ24+rCa3oK45uI4SjJ6yKvy1hUcIkm+lmXNKSJBT+0StIpPCXgW49eG27/QMa/5Hodl1xzO8qnwgozx7yNImqfyyhBDbGEbOiJxI+OEc=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:MWHPR15MB1150; 
x-ms-traffictypediagnostic: MWHPR15MB1150:
x-microsoft-antispam-prvs: <MWHPR15MB11508B4CE6E22C320F258515B66B0@MWHPR15MB1150.namprd15.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(10436049006162)(166708455590820)(85827821059158)(211936372134217)(100405760836317);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3231254)(11241501184)(944501410)(52105095)(93006095)(93001095)(3002001)(10201501046)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123558120)(20161123562045)(20161123560045)(6072148)(201708071742011)(7699016); SRVR:MWHPR15MB1150; BCL:0; PCL:0; RULEID:; SRVR:MWHPR15MB1150; 
x-forefront-prvs: 06818431B9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(979002)(346002)(376002)(39380400002)(39860400002)(396003)(366004)(199004)(189003)(51444003)(316002)(186003)(86362001)(6116002)(102836004)(53546011)(8676002)(19627405001)(14454004)(5250100002)(81156014)(110136005)(11346002)(54906003)(46003)(476003)(6506007)(486006)(33656002)(99286004)(8936002)(446003)(81166006)(575784001)(74316002)(6606003)(59450400001)(106356001)(54896002)(9686003)(68736007)(606006)(6306002)(4326008)(55016002)(105586002)(3280700002)(53936002)(39060400002)(7736002)(2906002)(236005)(6436002)(561944003)(97736004)(3660700001)(7696005)(2900100001)(6246003)(25786009)(76176011)(966005)(5660300001)(478600001)(229853002)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR15MB1150; H:MWHPR15MB1821.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: fb.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: jB5Yz7RY59U42n53i/6qALcqgdJcO/Oub3GJnza7VU04XMOncEjwYnYINCZyvNWsQFY+y0httExsohkUrybFZ4qaDqRmw4n25AGH6J6yOxx5Td0phKo/EAWERX4oMlsVNxuIx39sR7WPzCc2M1uAmyLu1A5uxc8AmBr1PVK53b/sTcDQZew3/Odt8ZOpigV9
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_MWHPR15MB1821F33BAB20815A38EB34A2B66B0MWHPR15MB1821namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 6ec43089-353c-4f35-f744-08d5c05ce8dd
X-MS-Exchange-CrossTenant-Network-Message-Id: 6ec43089-353c-4f35-f744-08d5c05ce8dd
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 May 2018 03:26:01.7436 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR15MB1150
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-23_02:, , signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/MZ7fgCpRnPUG0XIqdswv4DtkfJY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 03:26:12 -0000

--_000_MWHPR15MB1821F33BAB20815A38EB34A2B66B0MWHPR15MB1821namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

As an implementor of fizz, I support this design and am willing to implemen=
t this as well.


While this is a change in the API that TLS classically exposes, I think thi=
s is the right tradeoff because it helps make things way more explicit whic=
h will prevent several other bugs from happening in the future.


Subodh

________________________________
From: QUIC <quic-bounces@ietf.org> on behalf of Martin Thomson <martin.thom=
son@gmail.com>
Sent: Tuesday, May 22, 2018 8:00:40 PM
To: Ian Swett
Cc: ekr@mozilla.com; QUIC WG
Subject: Re: Stream0 Design Team Proposal

First of all, thanks to the design team for the work they have done.  I
haven't digested everything yet, but I think that I have a good sense of
the shape of the proposal.

Overall, this looks like a workable design.  It's a lot more invasive of
the cryptographic handshake implementation than I had thought people were
willing to stomach originally.  But it's clear that we've run into problems
with the current, more abstract API and this is a fairly natural way to
split TLS.  I've spent a little time thinking about how this might be
implemented and I think that it's not going to be *too* painful.  The proof
will be in the pudding there though.

In looking at the PR, I really appreciate seeing all the changes together.
BTW, the link above points to the wrong PR, so be careful (it appears to
have the same content, but that's not guaranteed).  The actual PR is here:
https://github.com/quicwg/base-drafts/pull/1377

I've pushed a branch to the main repo so that you can preview the entire
document set: https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__quicwg=
.github.io_base-2Ddrafts_stream0_&d=3DDwIBaQ&c=3D5VD0RTtNlTh3ycd41b3MUw&r=
=3Dh3Ju9EBS7mHtwg-wAyN7fQ&m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&s=
=3DususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&e=3D

It seems like there are some core changes here and a bunch of separable or
at least secondary changes.  I'm sure that each one has its own
justification, but that isn't always clear. The following changes seem like
they are separable:

* The use of separate packet number spaces
* The Retry packet changes (and NEW_TOKEN)
* EMPTY_ACK
* The TLS extension for flow control

Right now, some of these appear to be entirely gratuitous.  I'd like to get
to the bottom of each before we continue.

At a minimum, the PR we land first should include just the core changes.
As you say, reviewing a monster PR like this will only make GitHub weep
unicorns, but we might be able to cut this into smaller pieces.

On Wed, May 23, 2018 at 11:31 AM Ian Swett <ianswett=3D
40google.com@dmarc.ietf.org> wrote:

> Dear QUIC WG,


> On behalf of the Stream 0 Design Team, I am pleased to report that we
have consensus on a proposed approach to share with the WG. The DT's
proposal will make QUIC and TLS work closer together and incorporates ideas
from DTLS, but it does not use the DTLS protocol itself.


> The DT believes this solves the important open Stream 0 issues. The
proposal will be a bit more invasive in TLS, but we believe it is the right
long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and
Mint) are willing and able to do the work necessary.. A number of stacks
are currently working on implementations of this new approach, which we
hope to have in time for the Interim meeting.


> A design document describing the overall approach can be found at:


https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__docs.google.com_docu=
ment_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8_edit&d=3DDwIBaQ&c=3D5=
VD0RTtNlTh3ycd41b3MUw&r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&m=3D_vGK3zTKFrMOkFihJnPntL=
Yw1T0_NEMiHYSM0Q_u1JA&s=3DjDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg&e=3D


> A PR making the changes to the QUIC documents can be found at:

> https://github.com/quicwg/base-drafts/pull/1377


> A few design details did not have clear consensus, but it was felt it
would be better to discuss those in the wider WG than delay the design
team.  A consistent choice was made in the PR and these issues are
mentioned in Appendix B of the design doc.


> As always, comments and questions welcome. That said, this is a big PR
and we recognize that some editorial work is going to be needed before
merging. In the interest of letting people follow along, and to keep github
from falling over, we ask people to keep discussion on the mailing list and
refrain from making PR comments.


> See you in Kista!


> Ian and Eric


--_000_MWHPR15MB1821F33BAB20815A38EB34A2B66B0MWHPR15MB1821namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Helvetica,sans-serif;" dir=3D"ltr">
<p style=3D"margin-top:0;margin-bottom:0">As an implementor of fizz, I supp=
ort this design and am willing to implement this as well.
<br>
</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<p style=3D"margin-top:0;margin-bottom:0">While this is a change in the API=
 that TLS classically exposes, I think this is the right tradeoff because i=
t helps make things way more explicit which will prevent several other bugs=
 from happening in the future.</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<p style=3D"margin-top:0;margin-bottom:0">Subodh<br>
</p>
</div>
<hr style=3D"display:inline-block;width:98%" tabindex=3D"-1">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st=
yle=3D"font-size:11pt" color=3D"#000000"><b>From:</b> QUIC &lt;quic-bounces=
@ietf.org&gt; on behalf of Martin Thomson &lt;martin.thomson@gmail.com&gt;<=
br>
<b>Sent:</b> Tuesday, May 22, 2018 8:00:40 PM<br>
<b>To:</b> Ian Swett<br>
<b>Cc:</b> ekr@mozilla.com; QUIC WG<br>
<b>Subject:</b> Re: Stream0 Design Team Proposal</font>
<div>&nbsp;</div>
</div>
<div class=3D"BodyFragment"><font size=3D"2"><span style=3D"font-size:11pt;=
">
<div class=3D"PlainText">First of all, thanks to the design team for the wo=
rk they have done.&nbsp; I<br>
haven't digested everything yet, but I think that I have a good sense of<br=
>
the shape of the proposal.<br>
<br>
Overall, this looks like a workable design.&nbsp; It's a lot more invasive =
of<br>
the cryptographic handshake implementation than I had thought people were<b=
r>
willing to stomach originally.&nbsp; But it's clear that we've run into pro=
blems<br>
with the current, more abstract API and this is a fairly natural way to<br>
split TLS.&nbsp; I've spent a little time thinking about how this might be<=
br>
implemented and I think that it's not going to be *too* painful.&nbsp; The =
proof<br>
will be in the pudding there though.<br>
<br>
In looking at the PR, I really appreciate seeing all the changes together.<=
br>
BTW, the link above points to the wrong PR, so be careful (it appears to<br=
>
have the same content, but that's not guaranteed).&nbsp; The actual PR is h=
ere:<br>
<a href=3D"https://github.com/quicwg/base-drafts/pull/1377">https://github.=
com/quicwg/base-drafts/pull/1377</a><br>
<br>
I've pushed a branch to the main repo so that you can preview the entire<br=
>
document set: <a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps=
-3A__quicwg.github.io_base-2Ddrafts_stream0_&amp;d=3DDwIBaQ&amp;c=3D5VD0RTt=
NlTh3ycd41b3MUw&amp;r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&amp;m=3D_vGK3zTKFrMOkFihJnPn=
tLYw1T0_NEMiHYSM0Q_u1JA&amp;s=3DususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak=
&amp;e=3D">
https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__quicwg.github.io_bas=
e-2Ddrafts_stream0_&amp;d=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3Dh=
3Ju9EBS7mHtwg-wAyN7fQ&amp;m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&a=
mp;s=3DususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&amp;e=3D</a><br>
<br>
It seems like there are some core changes here and a bunch of separable or<=
br>
at least secondary changes.&nbsp; I'm sure that each one has its own<br>
justification, but that isn't always clear. The following changes seem like=
<br>
they are separable:<br>
<br>
* The use of separate packet number spaces<br>
* The Retry packet changes (and NEW_TOKEN)<br>
* EMPTY_ACK<br>
* The TLS extension for flow control<br>
<br>
Right now, some of these appear to be entirely gratuitous.&nbsp; I'd like t=
o get<br>
to the bottom of each before we continue.<br>
<br>
At a minimum, the PR we land first should include just the core changes.<br=
>
As you say, reviewing a monster PR like this will only make GitHub weep<br>
unicorns, but we might be able to cut this into smaller pieces.<br>
<br>
On Wed, May 23, 2018 at 11:31 AM Ian Swett &lt;ianswett=3D<br>
40google.com@dmarc.ietf.org&gt; wrote:<br>
<br>
&gt; Dear QUIC WG,<br>
<br>
<br>
&gt; On behalf of the Stream 0 Design Team, I am pleased to report that we<=
br>
have consensus on a proposed approach to share with the WG. The DT's<br>
proposal will make QUIC and TLS work closer together and incorporates ideas=
<br>
from DTLS, but it does not use the DTLS protocol itself.<br>
<br>
<br>
&gt; The DT believes this solves the important open Stream 0 issues. The<br=
>
proposal will be a bit more invasive in TLS, but we believe it is the right=
<br>
long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and<br=
>
Mint) are willing and able to do the work necessary.. A number of stacks<br=
>
are currently working on implementations of this new approach, which we<br>
hope to have in time for the Interim meeting.<br>
<br>
<br>
&gt; A design document describing the overall approach can be found at:<br>
<br>
<br>
<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__docs.goog=
le.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8_edit&amp;d=
=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&amp=
;m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&amp;s=3DjDNnz34hmWvLSQnHkS=
nYdihW-jG-0xZ-YYqKq30wVGg&amp;e=3D">https://urldefense.proofpoint.com/v2/ur=
l?u=3Dhttps-3A__docs.google.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJL=
kxddT93j6SwHY8_edit&amp;d=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3Dh=
3Ju9EBS7mHtwg-wAyN7fQ&amp;m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&a=
mp;s=3DjDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg&amp;e=3D</a><br>
<br>
<br>
&gt; A PR making the changes to the QUIC documents can be found at:<br>
<br>
&gt; <a href=3D"https://github.com/quicwg/base-drafts/pull/1377">https://gi=
thub.com/quicwg/base-drafts/pull/1377</a><br>
<br>
<br>
&gt; A few design details did not have clear consensus, but it was felt it<=
br>
would be better to discuss those in the wider WG than delay the design<br>
team.&nbsp; A consistent choice was made in the PR and these issues are<br>
mentioned in Appendix B of the design doc.<br>
<br>
<br>
&gt; As always, comments and questions welcome. That said, this is a big PR=
<br>
and we recognize that some editorial work is going to be needed before<br>
merging. In the interest of letting people follow along, and to keep github=
<br>
from falling over, we ask people to keep discussion on the mailing list and=
<br>
refrain from making PR comments.<br>
<br>
<br>
&gt; See you in Kista!<br>
<br>
<br>
&gt; Ian and Eric<br>
<br>
</div>
</span></font></div>
</body>
</html>

--_000_MWHPR15MB1821F33BAB20815A38EB34A2B66B0MWHPR15MB1821namp_--


From nobody Tue May 22 21:25:34 2018
Return-Path: <internet-drafts@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 40AB412D893; Tue, 22 May 2018 21:25:32 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-qpack-00.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.80.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152704953222.27129.17217282994017208552@ietfa.amsl.com>
Date: Tue, 22 May 2018 21:25:32 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/pIw8wOd4n1HvgBFqeDpl-ZIwtDU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 04:25:32 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the QUIC WG of the IETF.

        Title           : QPACK: Header Compression for HTTP over QUIC
        Authors         : Charles 'Buck' Krasic
                          Mike Bishop
                          Alan Frindell
	Filename        : draft-ietf-quic-qpack-00.txt
	Pages           : 20
	Date            : 2018-05-22

Abstract:
   This specification defines QPACK, a compression format for
   efficiently representing HTTP header fields, to be used in HTTP over
   QUIC.  This is a variation of HPACK header compression that seeks to
   reduce head-of-line blocking.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-ietf-quic-qpack/

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-qpack-00
https://datatracker.ietf.org/doc/html/draft-ietf-quic-qpack-00


Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

Internet-Drafts are also available by anonymous FTP at:
ftp://ftp.ietf.org/internet-drafts/


From nobody Tue May 22 21:58:04 2018
Return-Path: <kazuhooku@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E83CC12DA03 for <quic@ietfa.amsl.com>; Tue, 22 May 2018 21:58:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Wjq7rRTbF_RX for <quic@ietfa.amsl.com>; Tue, 22 May 2018 21:57:59 -0700 (PDT)
Received: from mail-pl0-x231.google.com (mail-pl0-x231.google.com [IPv6:2607:f8b0:400e:c01::231]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 70F4F12025C for <quic@ietf.org>; Tue, 22 May 2018 21:57:59 -0700 (PDT)
Received: by mail-pl0-x231.google.com with SMTP id c11-v6so12251657plr.5 for <quic@ietf.org>; Tue, 22 May 2018 21:57:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Co8FIQ+3ytPQcslH0OZQYSOCXGLwmRBrOBpuxhTlTlk=; b=XvuadnlAc1PrbwoMiGsLqLlN/bso1KOsmnr1KqX0KVwy8y5nBoqysnGcEJy0HLxyBE Pd9iUE/TH+pxaIV7gRmld0E0XPls8cx1iauKzq0FeyaK7MXFbDzcA/0/zfz1JZ5n2THE nqdaUv7GqO3ujyvsBqDQw1DsqNhT8aEN/Q4w1nftxI78s3j/tpqIRSG4ro1eyggwmcP2 bEU3CsG81irPfOP4fyKI4r7sZNHsjDFKN3+bd//Pb++G2iUGDHKtLzFhGlh/hEETqB89 fhEBCLWgXG/2XaAJqK+xvsdRtDNCMVDC64Ihp/O6ywmQwuk1rm9Bz84ji4chWjeM1ubV jYQQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Co8FIQ+3ytPQcslH0OZQYSOCXGLwmRBrOBpuxhTlTlk=; b=elOsskxai/TSgdxTazs3/t+Uoh/cRS0b/jpUIwGcZi/uB6ZhBwnxbI7J7qNP8QrA9P ivxCxzX47Z70zK0Qjzgm8Ct+rbeZEFNl5FdRyu8hfC9IsivhA4oRLG2a/o7MH0jZddui 0pG3SV3i71t8MfQnIRzaEzHOIpY/ZnMzcBFsbhV0t8OoTDsZb2x5yImLj23t6a58a23n 83nmvt8jyLP2epVdtxxU6TcsPBat1eg5swtyp9wH+bf6axm+JTZt5zvJlfqIbnnA7Voi igFxGJSlreQ9wDEWTWCtZFEWXwS5GdMTLfaYe1FOrCLDIB8pN/JVOics3Mur+GXOZlkU YavA==
X-Gm-Message-State: ALKqPwdaMyjz3DDYExOnU4uibngADVXY/4h8JC41wAt3BJRJldppEir9 G0yO31lHxmyzxEwP6xI7ukBsaO9GHHIgLynERZU=
X-Google-Smtp-Source: AB8JxZrofFmA/+wIrSol3G1WgjStICojVnagL+wgs1fA1gLrQQuHCPoWrdDOcjW3/S1CIGnaa+1ZOZyuYSsYLjz/Jek=
X-Received: by 2002:a17:902:b7c4:: with SMTP id v4-v6mr711048plz.224.1527051478871;  Tue, 22 May 2018 21:57:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:1189:0:0:0:0 with HTTP; Tue, 22 May 2018 21:57:58 -0700 (PDT)
In-Reply-To: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Wed, 23 May 2018 13:57:58 +0900
Message-ID: <CANatvzzS+T4HcddCemKF7bb1BmACFp=R4n+YMWkq7tnZaUXw4w@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Cc: IETF QUIC WG <quic@ietf.org>, Eric Rescorla <ekr@mozilla.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/WoLdex42eY-3O7TuJzjwBWJWI5Q>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 04:58:02 -0000

FWIW, I am happy to tell you that I have a working PoC code for the
proposed approach.

On the QUIC side, I saw 2% (124 lines) increase in code size (more on
that below). On the TLS side, I also saw 2% (175 lines) increase.
However please look at the code size change especially on the QUIC
side with grain of salt, as it is just a PoC.

As expected, the key and encryption-level management on the QUIC side
became very clean. Following are some of the design decisions I made
as well as the outcomes:

* All the interaction between picotls and quicly are accompanied by
"epoch". Handshake messages are attributed with their epochs so that
they do not get protected by the wrong key, or so that octets received
under an incorrect encryption context cannot be misused.

* All the traffic keys are governed by quicly (managing some traffic
keys in TLS while managing PNE key in QUIC seems messy).

* The Initial key is setup by quicly, wheeras other traffic keys are
installed by picotls by calling a callback named
update_traffic_key_cb. The callback accepts and installs 6 keys in
total: for three levels (i.e. 0-RTT, handshake, 1-RTT) in two
directions (send-side and receive-side).

* Three PN spaces have their own AEAD encryption key. Initial PN and
Handshake PN spaces have one aead decryption key each. Application PN
space has up to two decryption keys: either for 0-RTT and 1-RTT or for
two 1-RTT keys during key update.

It was a pain to have a dedicated frame encoding for CRYPTO_HS, even
though we can reuse (and I reused) the retransmission and reassembly
logic of QUIC streams for the handshake flows. About a half of the
code size increase comes from that (the other half comes from the
added abstraction for having two contexts for the handshake). I would
prefer reusing the STREAM frame encoding for the handshake data. We
could possibly use a different base offset (i.e. for CRYPTO_HS frames
we could use 0b00011XXX, whereas the STREAM frames use 0b00010XXX), as
well as omitting the Stream ID field.

Overall, now that I have a PoC, I am more confident that the proposed
approach is the correct path forward. It *simplifies* the QUIC stack
at the same time giving us better security properties as well as
fixing various issues in the current design (as discussed in the
design doc).


2018-05-23 10:30 GMT+09:00 Ian Swett <ianswett=40google.com@dmarc.ietf.org>:
> Dear QUIC WG,
>
>
> On behalf of the Stream 0 Design Team, I am pleased to report that we have
> consensus on a proposed approach to share with the WG. The DT's proposal
> will make QUIC and TLS work closer together and incorporates ideas from
> DTLS, but it does not use the DTLS protocol itself.
>
>
> The DT believes this solves the important open Stream 0 issues. The proposal
> will be a bit more invasive in TLS, but we believe it is the right long-term
> direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and Mint) are
> willing and able to do the work necessary.. A number of stacks are currently
> working on implementations of this new approach, which we hope to have in
> time for the Interim meeting.
>
>
> A design document describing the overall approach can be found at:
>
> https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit
>
>
> A PR making the changes to the QUIC documents can be found at:
>
> https://github.com/quicwg/base-drafts/pull/1377
>
>
> A few design details did not have clear consensus, but it was felt it would
> be better to discuss those in the wider WG than delay the design team.  A
> consistent choice was made in the PR and these issues are mentioned in
> Appendix B of the design doc.
>
>
> As always, comments and questions welcome. That said, this is a big PR and
> we recognize that some editorial work is going to be needed before merging.
> In the interest of letting people follow along, and to keep github from
> falling over, we ask people to keep discussion on the mailing list and
> refrain from making PR comments.
>
>
> See you in Kista!
>
>
> Ian and Eric



-- 
Kazuho Oku


From nobody Tue May 22 21:58:43 2018
Return-Path: <kazuhooku@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 192E112DA0C for <quic@ietfa.amsl.com>; Tue, 22 May 2018 21:58:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 s7ZsAMYquEvT for <quic@ietfa.amsl.com>; Tue, 22 May 2018 21:58:38 -0700 (PDT)
Received: from mail-pl0-x233.google.com (mail-pl0-x233.google.com [IPv6:2607:f8b0:400e:c01::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DC33F12025C for <quic@ietf.org>; Tue, 22 May 2018 21:58:38 -0700 (PDT)
Received: by mail-pl0-x233.google.com with SMTP id n10-v6so12254327plp.0 for <quic@ietf.org>; Tue, 22 May 2018 21:58:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TRYdwwvtagfugiXekzlTpYO+QSpHKqVVqHWyS/V8z1I=; b=AaJngRypGPIKAw12jdETwRzNUXeSa3zxy/q3BhlkGKFBkLerp3vdnUQ8q/Yl/feD3F GW2BZoc9iuiBqAEXjWeO05eNq9ynlhekVIK5FB9XvFYv5YFFIsAx1lSlWCcyLWRVnCOP XlPJQ5mprT/w9tQP2sOw0I77IbP1FpN1jkjNh3asBd7oUxYzlZLjQbPZSzLI6hEeZR4z qL0kX3gzwbZd8PkEkyrrrk1AB2ruez3rPewSEZ6JB9yXrnzjHfArsZJRo/soAuJe7LVe LiL7Qq+XKkcwEvpm3FQ8u36eHqilsEqcSm4rRK0WNxdyNC1+e6wRDvruyQpeKRMmuLJq ROtQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TRYdwwvtagfugiXekzlTpYO+QSpHKqVVqHWyS/V8z1I=; b=ZEmnJjFNtAfy0ZG6hkpZTxVIAhun5CAI7+3gcJVOJ1KzbtSYgcmUafllS9lw7WbPIW NZPlApbUqi/HdQdt9gflyGq8ppEvz0Hoy1G5piV9E4SdLiU7PBklNRt4E/hRxpjSuHfL 2DLGcgq1afkvBvDX3lNg23w0n7GyUa556o2XrVJupFw0v9MdtFBNkHPi5crw4WYSUmUP IFD8qCIpeLdW4q6Kbun8Y90jdGblHEsc00BMmjyKCieJsmFOjHotv8YRsrBw/6gjS8JT 03MHItrNhRqmHADdycD8+5wjbqImKOHbR/byjC51eYHeCIGdihaOwTKM+9065rhBIgsE DU4Q==
X-Gm-Message-State: ALKqPwdN7lj+mGIlbw3Wl4sRRN3XK6qP/fjhr7r6/ZKZMmU8uN4t2FMl LmgOkEym+DEf6gZbFwiSc8aXgHX2LmC60sQpHwY=
X-Google-Smtp-Source: AB8JxZrYxtg/TjzFbDu4BFujblMttQoDPlO1VaKx1yxU77i0xq0jClwMNYdyiPYiZlZjII9kzNUI92PJOEa+R2I0ZPI=
X-Received: by 2002:a17:902:8486:: with SMTP id c6-v6mr1392027plo.23.1527051518323;  Tue, 22 May 2018 21:58:38 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:1189:0:0:0:0 with HTTP; Tue, 22 May 2018 21:58:37 -0700 (PDT)
In-Reply-To: <CANatvzzS+T4HcddCemKF7bb1BmACFp=R4n+YMWkq7tnZaUXw4w@mail.gmail.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CANatvzzS+T4HcddCemKF7bb1BmACFp=R4n+YMWkq7tnZaUXw4w@mail.gmail.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Wed, 23 May 2018 13:58:37 +0900
Message-ID: <CANatvzzmLveA2N8qZ-Fa47G8Mzdv=k3+AdSeqvXCNm_0VNr1iA@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Cc: IETF QUIC WG <quic@ietf.org>, Eric Rescorla <ekr@mozilla.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/OPh4-xxw3wtoZ_fPeBWqkctQeA0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 04:58:41 -0000

PS. I forgot the link. The PoC is available at
https://github.com/h2o/quicly/pull/8.

2018-05-23 13:57 GMT+09:00 Kazuho Oku <kazuhooku@gmail.com>:
> FWIW, I am happy to tell you that I have a working PoC code for the
> proposed approach.
>
> On the QUIC side, I saw 2% (124 lines) increase in code size (more on
> that below). On the TLS side, I also saw 2% (175 lines) increase.
> However please look at the code size change especially on the QUIC
> side with grain of salt, as it is just a PoC.
>
> As expected, the key and encryption-level management on the QUIC side
> became very clean. Following are some of the design decisions I made
> as well as the outcomes:
>
> * All the interaction between picotls and quicly are accompanied by
> "epoch". Handshake messages are attributed with their epochs so that
> they do not get protected by the wrong key, or so that octets received
> under an incorrect encryption context cannot be misused.
>
> * All the traffic keys are governed by quicly (managing some traffic
> keys in TLS while managing PNE key in QUIC seems messy).
>
> * The Initial key is setup by quicly, wheeras other traffic keys are
> installed by picotls by calling a callback named
> update_traffic_key_cb. The callback accepts and installs 6 keys in
> total: for three levels (i.e. 0-RTT, handshake, 1-RTT) in two
> directions (send-side and receive-side).
>
> * Three PN spaces have their own AEAD encryption key. Initial PN and
> Handshake PN spaces have one aead decryption key each. Application PN
> space has up to two decryption keys: either for 0-RTT and 1-RTT or for
> two 1-RTT keys during key update.
>
> It was a pain to have a dedicated frame encoding for CRYPTO_HS, even
> though we can reuse (and I reused) the retransmission and reassembly
> logic of QUIC streams for the handshake flows. About a half of the
> code size increase comes from that (the other half comes from the
> added abstraction for having two contexts for the handshake). I would
> prefer reusing the STREAM frame encoding for the handshake data. We
> could possibly use a different base offset (i.e. for CRYPTO_HS frames
> we could use 0b00011XXX, whereas the STREAM frames use 0b00010XXX), as
> well as omitting the Stream ID field.
>
> Overall, now that I have a PoC, I am more confident that the proposed
> approach is the correct path forward. It *simplifies* the QUIC stack
> at the same time giving us better security properties as well as
> fixing various issues in the current design (as discussed in the
> design doc).
>
>
> 2018-05-23 10:30 GMT+09:00 Ian Swett <ianswett=40google.com@dmarc.ietf.org>:
>> Dear QUIC WG,
>>
>>
>> On behalf of the Stream 0 Design Team, I am pleased to report that we have
>> consensus on a proposed approach to share with the WG. The DT's proposal
>> will make QUIC and TLS work closer together and incorporates ideas from
>> DTLS, but it does not use the DTLS protocol itself.
>>
>>
>> The DT believes this solves the important open Stream 0 issues. The proposal
>> will be a bit more invasive in TLS, but we believe it is the right long-term
>> direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and Mint) are
>> willing and able to do the work necessary.. A number of stacks are currently
>> working on implementations of this new approach, which we hope to have in
>> time for the Interim meeting.
>>
>>
>> A design document describing the overall approach can be found at:
>>
>> https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit
>>
>>
>> A PR making the changes to the QUIC documents can be found at:
>>
>> https://github.com/quicwg/base-drafts/pull/1377
>>
>>
>> A few design details did not have clear consensus, but it was felt it would
>> be better to discuss those in the wider WG than delay the design team.  A
>> consistent choice was made in the PR and these issues are mentioned in
>> Appendix B of the design doc.
>>
>>
>> As always, comments and questions welcome. That said, this is a big PR and
>> we recognize that some editorial work is going to be needed before merging.
>> In the interest of letting people follow along, and to keep github from
>> falling over, we ask people to keep discussion on the mailing list and
>> refrain from making PR comments.
>>
>>
>> See you in Kista!
>>
>>
>> Ian and Eric
>
>
>
> --
> Kazuho Oku



-- 
Kazuho Oku


From nobody Tue May 22 22:29:39 2018
Return-Path: <huitema@huitema.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D89681241F5 for <quic@ietfa.amsl.com>; Tue, 22 May 2018 22:29:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.6
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 s5Smw4RCsKgc for <quic@ietfa.amsl.com>; Tue, 22 May 2018 22:29:35 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 A5BF512025C for <quic@ietf.org>; Tue, 22 May 2018 22:29:34 -0700 (PDT)
Received: from xsmtp02.mail2web.com ([168.144.250.215]) by mx26.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1fLML4-0003tA-Qb for quic@ietf.org; Wed, 23 May 2018 07:29:32 +0200
Received: from [10.5.2.35] (helo=xmail10.myhosting.com) by xsmtp02.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1fLMKx-0004rR-R6 for quic@ietf.org; Wed, 23 May 2018 01:29:27 -0400
Received: (qmail 23171 invoked from network); 23 May 2018 05:29:22 -0000
Received: from unknown (HELO [192.168.1.106]) (Authenticated-user:_huitema@huitema.net@[172.56.42.66]) (envelope-sender <huitema@huitema.net>) by xmail10.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 23 May 2018 05:29:22 -0000
To: quic@ietf.org
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CABkgnnUB=jqwFzb2rjBHUFzOgu0hX0YUgaf5kW5ENNGKP+mGiA@mail.gmail.com> <MWHPR15MB1821F33BAB20815A38EB34A2B66B0@MWHPR15MB1821.namprd15.prod.outlook.com>
From: Christian Huitema <huitema@huitema.net>
Openpgp: preference=signencrypt
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= xsBNBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAHNJ0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PsLAeQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1bOwE0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAcLBfgQYAQIACQUCUhFfyAIb LgEpCRCTQwmyVcgNcsBdIAQZAQIABgUCUhFfyAAKCRC22tOSFDh1UOlBB/94RsCJepNvmi/c YiNmMnm0mKb6vjv43OsHkqrrCqJSfo95KHyl5Up4JEp8tiJMyYT2mp4IsirZHxz/5lqkw9Az tcGAF3GlFsj++xTyD07DXlNeddwTKlqPRi/b8sppjtWur6Pm+wnAHp0mQ7GidhxHccFCl65w uT7S/ocb1MjrTgnAMiz+x87d48n1UJ7yIdI41Wpg2XFZiA9xPBiDuuoPwFj14/nK0elV5Dvq 4/HVgfurb4+fd74PV/CC/dmd7hg0ZRlgnB5rFUcFO7ywb7/TvICIIaLWcI42OJDSZjZ/MAzz BeXm263lHh+kFxkh2LxEHnQGHCHGpTYyi4Z3dv03HtkH/1SI8joQMQq00Bv+RdEbJXfEExrT u4gtdZAihwvy97OPA2nCdTAHm/phkzryMeOaOztI4PS8u2Ce5lUB6P/HcGtK/038KdX5MYST Fn8KUDt4o29bkv0CUXwDzS3oTzPNtGdryBkRMc9b+yn9+AdwFEH4auhiTQXPMnl0+G3nhKr7 jvzVFJCRif3OAhEm4vmBNDE3uuaXFQnbK56GJrnqVN+KX5Z3M7X3fA8UcVCGOEHXRP/aubiw Ngawj0V9x+43kUapFp+nF69R53UI65YtJ95ec4PTO/Edvap8h1UbdEOc4+TiYwY1TBuIKltY 1cnrjgAWUh/Ucvr++/KbD9tD6C8=
Message-ID: <046ee03d-a675-86b6-ed3b-4fa69288c42d@huitema.net>
Date: Tue, 22 May 2018 22:29:12 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <MWHPR15MB1821F33BAB20815A38EB34A2B66B0@MWHPR15MB1821.namprd15.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------16AE8EB6EBC4B8EB86EA1E0C"
Content-Language: en-US
Subject: Re: Stream0 Design Team Proposal
X-Originating-IP: 168.144.250.215
X-AntiSpamCloud-Domain: xsmtpout.mail2web.com
X-AntiSpamCloud-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-AntiSpamCloud-Outgoing-Class: unsure
X-AntiSpamCloud-Outgoing-Evidence: Combined (0.34)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5iIhwcd0PmOQbQoa1/fCxbx602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO37pNwwF1lRXh5rzvPzo9Jts1ujulqUFmMITHM77eiVipHPYbz5lftSIizApgCPMbs7i TvJ2/ZGzVWB9scFAaCdIFaUvXN+CI+RGy3Me16pBy0LkIcQZ+RRGzUcmNZyDXh/TBCf6oYXAWGet lavcAjD9ytQxIHf9lN5jjLJaPK8lRJSPf/SXbEnDSsal/zZzc4n9VZdr7RAFD5mRwooUYhwMPaBP aKeQW+/QlaOdv8isl/qMm08Zpim2AHUKEWvQ6G/bWfgucjnNmABpGhD9TTttrFCuZ0NkwnSz2Luu o1u9uevuNfM1HjkNEFwape+IgNezYqxGMqsKjARq8PBC4qjpVMhqNcdjhoIlgrKzBvjTmdySlZou 9qHIGOZDEEo7Oyc1nq0gsY582CWqKjiRB3ukywmZtiDkyd4mEBjJGGEJgawbllbHk+xyUKopM6rc KCaQX/lIXcRWtobViGg9fpXXTg8/eGzRNUUVgcQ9smKzWE4kNwHFJ1FRpFF1qVhW+97PWzLGmQvK RC7xldu8DpWU2yw6z85L3UyCdO+oQ3S7VPd90DA1c/ZLOZZo7XGPVfWv8HL1YL3Zn8TE/e4IMjT6 4dZYZAAUgQSn0n4YsmwRRGxQZAxG+4f1XAVNzQl2yuggKW28pboyZCmKkHUYXaluOeVTar9zozYB t9COYTwdEvjlXiWkXE5dwL2v3l4fZntB4/4Pbrz2QtFuyl+Sh6dFwOZmPeQdOCsWer2luIDmfqb5 R4VemuUI6bcEARsm0H3NNoW1ZvdERgvndX6lJvSNZy58uobCIkCdwVDO83SGTnM2K/9iKCD9v589 nVS3hWSdEOMftBjsWb6BDQzjSsHUIomTnJwT4ky6b7E7Hukt2Ge4B8NG0VKlrY+34Zmj+F/tjlrZ UvGhhjiSam0tWhQxL7hrJSk60SF3F6RYOYr2
X-Report-Abuse-To: spam@quarantine6.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/sQ5Vi1fKMVPoirulOQ2fmLzIKF8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 05:29:38 -0000

This is a multi-part message in MIME format.
--------------16AE8EB6EBC4B8EB86EA1E0C
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

I like the proposal. In particular, I really like the encryption of
handshake packets with the handshake key, as it does close a number of
avenues for attacks. And I like that it solves the "ack promotion" issue
that I was complaining against for some time. Turns out that in the
current draft, it is very hard to contain that problem if you enable
client auth.


On the other hand, I agree with Martin that a lot of the additions to
transmission recovery should be moved to separate PRs. I am not
enthusiastic with the EMPTY ACK mechanism, or with the proposed
"implicit acknowledgement" of a lower crypto stream by a higher level
ack. In any case, starting as simple as possible would help having the
first implementations and tests.


On 5/22/2018 8:26 PM, Subodh Iyengar wrote:
>
> As an implementor of fizz, I support this design and am willing to
> implement this as well.
>
>
> While this is a change in the API that TLS classically exposes, I
> think this is the right tradeoff because it helps make things way more
> explicit which will prevent several other bugs from happening in the
> future.
>
>
> Subodh
>
> -----------------------------------------------------------------------=
-
> *From:* QUIC <quic-bounces@ietf.org> on behalf of Martin Thomson
> <martin.thomson@gmail.com>
> *Sent:* Tuesday, May 22, 2018 8:00:40 PM
> *To:* Ian Swett
> *Cc:* ekr@mozilla.com; QUIC WG
> *Subject:* Re: Stream0 Design Team Proposal
> =A0
> First of all, thanks to the design team for the work they have done.=A0=
 I
> haven't digested everything yet, but I think that I have a good sense o=
f
> the shape of the proposal.
>
> Overall, this looks like a workable design.=A0 It's a lot more invasive=
 of
> the cryptographic handshake implementation than I had thought people we=
re
> willing to stomach originally.=A0 But it's clear that we've run into
> problems
> with the current, more abstract API and this is a fairly natural way to=

> split TLS.=A0 I've spent a little time thinking about how this might be=

> implemented and I think that it's not going to be *too* painful.=A0 The=

> proof
> will be in the pudding there though.
>
> In looking at the PR, I really appreciate seeing all the changes togeth=
er.
> BTW, the link above points to the wrong PR, so be careful (it appears t=
o
> have the same content, but that's not guaranteed).=A0 The actual PR is =
here:
> https://github.com/quicwg/base-drafts/pull/1377
>
> I've pushed a branch to the main repo so that you can preview the entir=
e
> document set:
> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__quicwg.github.io=
_base-2Ddrafts_stream0_&d=3DDwIBaQ&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3Dh3Ju9EB=
S7mHtwg-wAyN7fQ&m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&s=3Dususm=
txI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&e=3D
>
> It seems like there are some core changes here and a bunch of separable=
 or
> at least secondary changes.=A0 I'm sure that each one has its own
> justification, but that isn't always clear. The following changes seem
> like
> they are separable:
>
> * The use of separate packet number spaces
> * The Retry packet changes (and NEW_TOKEN)
> * EMPTY_ACK
> * The TLS extension for flow control
>
> Right now, some of these appear to be entirely gratuitous.=A0 I'd like
> to get
> to the bottom of each before we continue.
>
> At a minimum, the PR we land first should include just the core changes=
=2E
> As you say, reviewing a monster PR like this will only make GitHub weep=

> unicorns, but we might be able to cut this into smaller pieces.
>
> On Wed, May 23, 2018 at 11:31 AM Ian Swett <ianswett=3D
> 40google.com@dmarc.ietf.org> wrote:
>
> > Dear QUIC WG,
>
>
> > On behalf of the Stream 0 Design Team, I am pleased to report that we=

> have consensus on a proposed approach to share with the WG. The DT's
> proposal will make QUIC and TLS work closer together and incorporates
> ideas
> from DTLS, but it does not use the DTLS protocol itself.
>
>
> > The DT believes this solves the important open Stream 0 issues. The
> proposal will be a bit more invasive in TLS, but we believe it is the
> right
> long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS, an=
d
> Mint) are willing and able to do the work necessary.. A number of stack=
s
> are currently working on implementations of this new approach, which we=

> hope to have in time for the Interim meeting.
>
>
> > A design document describing the overall approach can be found at:
>
>
> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__docs.google.com_=
document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8_edit&d=3DDwIBaQ=
&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&m=3D_vGK3zTKFrMOkF=
ihJnPntLYw1T0_NEMiHYSM0Q_u1JA&s=3DjDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30=
wVGg&e=3D
>
>
> > A PR making the changes to the QUIC documents can be found at:
>
> > https://github.com/quicwg/base-drafts/pull/1377
>
>
> > A few design details did not have clear consensus, but it was felt it=

> would be better to discuss those in the wider WG than delay the design
> team.=A0 A consistent choice was made in the PR and these issues are
> mentioned in Appendix B of the design doc.
>
>
> > As always, comments and questions welcome. That said, this is a big P=
R
> and we recognize that some editorial work is going to be needed before
> merging. In the interest of letting people follow along, and to keep
> github
> from falling over, we ask people to keep discussion on the mailing
> list and
> refrain from making PR comments.
>
>
> > See you in Kista!
>
>
> > Ian and Eric
>


--------------16AE8EB6EBC4B8EB86EA1E0C
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>I like the proposal. In particular, I really like the encryption
      of handshake packets with the handshake key, as it does close a
      number of avenues for attacks. And I like that it solves the "ack
      promotion" issue that I was complaining against for some time.
      Turns out that in the current draft, it is very hard to contain
      that problem if you enable client auth.</p>
    <p><br>
    </p>
    <p>On the other hand, I agree with Martin that a lot of the
      additions to transmission recovery should be moved to separate
      PRs. I am not enthusiastic with the EMPTY ACK mechanism, or with
      the proposed "implicit acknowledgement" of a lower crypto stream
      by a higher level ack. In any case, starting as simple as possible
      would help having the first implementations and tests.<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 5/22/2018 8:26 PM, Subodh Iyengar
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:MWHPR15MB1821F33BAB20815A38EB34A2B66B0@MWHPR15MB1821.namprd15.prod.outlook.com">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <style type="text/css" style="display:none;"><!-- P {margin-top:0;margin-bottom:0;} --></style>
      <div id="divtagdefaultwrapper"
style="font-size:12pt;color:#000000;font-family:Calibri,Helvetica,sans-serif;"
        dir="ltr">
        <p style="margin-top:0;margin-bottom:0">As an implementor of
          fizz, I support this design and am willing to implement this
          as well.
          <br>
        </p>
        <p style="margin-top:0;margin-bottom:0"><br>
        </p>
        <p style="margin-top:0;margin-bottom:0">While this is a change
          in the API that TLS classically exposes, I think this is the
          right tradeoff because it helps make things way more explicit
          which will prevent several other bugs from happening in the
          future.</p>
        <p style="margin-top:0;margin-bottom:0"><br>
        </p>
        <p style="margin-top:0;margin-bottom:0">Subodh<br>
        </p>
      </div>
      <hr style="display:inline-block;width:98%" tabindex="-1">
      <div id="divRplyFwdMsg" dir="ltr"><font style="font-size:11pt"
          face="Calibri, sans-serif" color="#000000"><b>From:</b> QUIC
          <a class="moz-txt-link-rfc2396E" href="mailto:quic-bounces@ietf.org">&lt;quic-bounces@ietf.org&gt;</a> on behalf of Martin Thomson
          <a class="moz-txt-link-rfc2396E" href="mailto:martin.thomson@gmail.com">&lt;martin.thomson@gmail.com&gt;</a><br>
          <b>Sent:</b> Tuesday, May 22, 2018 8:00:40 PM<br>
          <b>To:</b> Ian Swett<br>
          <b>Cc:</b> <a class="moz-txt-link-abbreviated" href="mailto:ekr@mozilla.com">ekr@mozilla.com</a>; QUIC WG<br>
          <b>Subject:</b> Re: Stream0 Design Team Proposal</font>
        <div> </div>
      </div>
      <div class="BodyFragment"><font size="2"><span
            style="font-size:11pt;">
            <div class="PlainText">First of all, thanks to the design
              team for the work they have done.  I<br>
              haven't digested everything yet, but I think that I have a
              good sense of<br>
              the shape of the proposal.<br>
              <br>
              Overall, this looks like a workable design.  It's a lot
              more invasive of<br>
              the cryptographic handshake implementation than I had
              thought people were<br>
              willing to stomach originally.  But it's clear that we've
              run into problems<br>
              with the current, more abstract API and this is a fairly
              natural way to<br>
              split TLS.  I've spent a little time thinking about how
              this might be<br>
              implemented and I think that it's not going to be *too*
              painful.  The proof<br>
              will be in the pudding there though.<br>
              <br>
              In looking at the PR, I really appreciate seeing all the
              changes together.<br>
              BTW, the link above points to the wrong PR, so be careful
              (it appears to<br>
              have the same content, but that's not guaranteed).  The
              actual PR is here:<br>
              <a href="https://github.com/quicwg/base-drafts/pull/1377"
                moz-do-not-send="true">https://github.com/quicwg/base-drafts/pull/1377</a><br>
              <br>
              I've pushed a branch to the main repo so that you can
              preview the entire<br>
              document set: <a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__quicwg.github.io_base-2Ddrafts_stream0_&amp;d=DwIBaQ&amp;c=5VD0RTtNlTh3ycd41b3MUw&amp;r=h3Ju9EBS7mHtwg-wAyN7fQ&amp;m=_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&amp;s=ususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&amp;e="
                moz-do-not-send="true">
https://urldefense.proofpoint.com/v2/url?u=https-3A__quicwg.github.io_base-2Ddrafts_stream0_&amp;d=DwIBaQ&amp;c=5VD0RTtNlTh3ycd41b3MUw&amp;r=h3Ju9EBS7mHtwg-wAyN7fQ&amp;m=_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&amp;s=ususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&amp;e=</a><br>
              <br>
              It seems like there are some core changes here and a bunch
              of separable or<br>
              at least secondary changes.  I'm sure that each one has
              its own<br>
              justification, but that isn't always clear. The following
              changes seem like<br>
              they are separable:<br>
              <br>
              * The use of separate packet number spaces<br>
              * The Retry packet changes (and NEW_TOKEN)<br>
              * EMPTY_ACK<br>
              * The TLS extension for flow control<br>
              <br>
              Right now, some of these appear to be entirely
              gratuitous.  I'd like to get<br>
              to the bottom of each before we continue.<br>
              <br>
              At a minimum, the PR we land first should include just the
              core changes.<br>
              As you say, reviewing a monster PR like this will only
              make GitHub weep<br>
              unicorns, but we might be able to cut this into smaller
              pieces.<br>
              <br>
              On Wed, May 23, 2018 at 11:31 AM Ian Swett &lt;ianswett=<br>
              <a class="moz-txt-link-abbreviated" href="mailto:40google.com@dmarc.ietf.org">40google.com@dmarc.ietf.org</a>&gt; wrote:<br>
              <br>
              &gt; Dear QUIC WG,<br>
              <br>
              <br>
              &gt; On behalf of the Stream 0 Design Team, I am pleased
              to report that we<br>
              have consensus on a proposed approach to share with the
              WG. The DT's<br>
              proposal will make QUIC and TLS work closer together and
              incorporates ideas<br>
              from DTLS, but it does not use the DTLS protocol itself.<br>
              <br>
              <br>
              &gt; The DT believes this solves the important open Stream
              0 issues. The<br>
              proposal will be a bit more invasive in TLS, but we
              believe it is the right<br>
              long-term direction and several TLS stacks (BoringSSL,
              PicoTLS, NSS, and<br>
              Mint) are willing and able to do the work necessary.. A
              number of stacks<br>
              are currently working on implementations of this new
              approach, which we<br>
              hope to have in time for the Interim meeting.<br>
              <br>
              <br>
              &gt; A design document describing the overall approach can
              be found at:<br>
              <br>
              <br>
              <a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8_edit&amp;d=DwIBaQ&amp;c=5VD0RTtNlTh3ycd41b3MUw&amp;r=h3Ju9EBS7mHtwg-wAyN7fQ&amp;m=_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&amp;s=jDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg&amp;e="
                moz-do-not-send="true">https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8_edit&amp;d=DwIBaQ&amp;c=5VD0RTtNlTh3ycd41b3MUw&amp;r=h3Ju9EBS7mHtwg-wAyN7fQ&amp;m=_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&amp;s=jDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg&amp;e=</a><br>
              <br>
              <br>
              &gt; A PR making the changes to the QUIC documents can be
              found at:<br>
              <br>
              &gt; <a
                href="https://github.com/quicwg/base-drafts/pull/1377"
                moz-do-not-send="true">https://github.com/quicwg/base-drafts/pull/1377</a><br>
              <br>
              <br>
              &gt; A few design details did not have clear consensus,
              but it was felt it<br>
              would be better to discuss those in the wider WG than
              delay the design<br>
              team.  A consistent choice was made in the PR and these
              issues are<br>
              mentioned in Appendix B of the design doc.<br>
              <br>
              <br>
              &gt; As always, comments and questions welcome. That said,
              this is a big PR<br>
              and we recognize that some editorial work is going to be
              needed before<br>
              merging. In the interest of letting people follow along,
              and to keep github<br>
              from falling over, we ask people to keep discussion on the
              mailing list and<br>
              refrain from making PR comments.<br>
              <br>
              <br>
              &gt; See you in Kista!<br>
              <br>
              <br>
              &gt; Ian and Eric<br>
              <br>
            </div>
          </span></font></div>
    </blockquote>
    <br>
  </body>
</html>

--------------16AE8EB6EBC4B8EB86EA1E0C--


From nobody Tue May 22 23:40:00 2018
Return-Path: <jri.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E264124B0A for <quic@ietfa.amsl.com>; Tue, 22 May 2018 23:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 to4lbWCM6isg for <quic@ietfa.amsl.com>; Tue, 22 May 2018 23:39:55 -0700 (PDT)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BDE2C124BFA for <quic@ietf.org>; Tue, 22 May 2018 23:39:54 -0700 (PDT)
Received: by mail-io0-x22d.google.com with SMTP id p124-v6so21486401iod.1 for <quic@ietf.org>; Tue, 22 May 2018 23:39:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=AZtCJM1Z+BKUOVA+t4ilfqriEfCZJh/r4PBubjQLrrU=; b=h5AhR5JqA6Kf+CWdudWUbn42jcoUVkRuvKa+ZFPHy+M8YwwhxpaUdi2sYxwVuqYJsQ 5GhcAOuO+0xTLlg5XYYiYQ9Vlh4v3BVZtXZkxnfEYqRzwjCymISlFrGBS21AgQu58vhY x0X6GSVDTa3X2h+BqyUwpSIYhVURnxAKsxJBtQ8rGkQ2i8cm8E5jEjekD0eErHFmviyZ fbQlCAPngId+EKJ1kiD+WUQoLDvOCQOTiwwgLSHtbp8WQC1SwYwwkb0ywWt+pZzbrHkM c7cFtIEEvTCLK88JDpwrV5UVpU9ER5yn8GdE2cM02KoqBi06krjx+8W4y7SrAC1VQcw0 Wh3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=AZtCJM1Z+BKUOVA+t4ilfqriEfCZJh/r4PBubjQLrrU=; b=DYMgxvWMBCEhqrEzqxRJ1tp8cL3iXHeshCiFfR7Q3ViCqWRbFGemsDeM1onvim9X7h IdZAY20YvPy+b/LuAXDVRYI1wmLTXss3j5M3RZPkEOQoN8Ba+owf0KOxlulihO7EK+9n CC4LGNEcSKaJdooESz9BltF5bzYlWSMziCNi9pTUXjX26NzwIdTR2qEC+oN0t0P8+q2e j1LL6EGL4mSSTO5vMyQgAr3+5jlZdrc07GwXhztNhAqvUP8j+t+VjdYtPKJcnHiHRtVQ Gx7P3lRoporVvbsLX0ij920e2nWiloXAOn2B3bMg0QwtOBDZ+gua9CyVMxpYN80qa6hF Omeg==
X-Gm-Message-State: ALKqPweUA8FqxrZsHxYK4BMMJe1FmWDX8xB7w++8cirSDtCYqAYa5Tr6 mATAkjAfPPAmGkCoEwHBFYilwZjCJGdD4r6eW2vggQ==
X-Google-Smtp-Source: ADUXVKJczOpdj7Ygu8qN/2UV6We0bpBheX39E/Go1m161wwOcH6Uw1IRWLZH/mqbmhcf29aauHf/s2mbSumzr/tyv+s=
X-Received: by 2002:a6b:88e3:: with SMTP id s96-v6mr1338921ioi.45.1527057593947;  Tue, 22 May 2018 23:39:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:27d4:0:0:0:0:0 with HTTP; Tue, 22 May 2018 23:39:53 -0700 (PDT)
In-Reply-To: <CANatvzzS+T4HcddCemKF7bb1BmACFp=R4n+YMWkq7tnZaUXw4w@mail.gmail.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CANatvzzS+T4HcddCemKF7bb1BmACFp=R4n+YMWkq7tnZaUXw4w@mail.gmail.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Tue, 22 May 2018 23:39:53 -0700
Message-ID: <CACpbDcddWz_i5GoNWYfDAdWKcX0_gOMiKk=ORVABGPE8+7c8Vw@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: Kazuho Oku <kazuhooku@gmail.com>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Eric Rescorla <ekr@mozilla.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000705907056cd9cd89"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/g_em-EST1jWfEhm0XnZuqJ6AqAA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 06:39:58 -0000

--000000000000705907056cd9cd89
Content-Type: text/plain; charset="UTF-8"

Thank you for your implementation and your report -- this is terrific and
helpful!

On your note about CRYPTO_HS frames, I think your idea is clever. Just to
ensure that I am understanding it correctly, I believe you're proposing
defining:
0x10 - 0x17: STREAM frame
0x18 - 0x1F: CRYPTO_HS frame

We can the same frame format for CRYPTO_HS as STREAM except that CRYPTO_HS
will not have the stream ID field. This means an implementation handling
these frames can reuse the stream machinery with a small change to parse
the header bits as follows:

if (type & 0x10)  {  // STREAM or CRYPTO_HS frame
    if (type & 0x08) streamID = varint_consume(frame);
    if (type & 0x04) offset = varint_consume(frame);
    if (type & 0x02) length = varint_consume(frame);
    if (type & 0x01) fin = 1;
    read body if present
}

On Tue, May 22, 2018 at 9:57 PM, Kazuho Oku <kazuhooku@gmail.com> wrote:

> FWIW, I am happy to tell you that I have a working PoC code for the
> proposed approach.
>
> On the QUIC side, I saw 2% (124 lines) increase in code size (more on
> that below). On the TLS side, I also saw 2% (175 lines) increase.
> However please look at the code size change especially on the QUIC
> side with grain of salt, as it is just a PoC.
>
> As expected, the key and encryption-level management on the QUIC side
> became very clean. Following are some of the design decisions I made
> as well as the outcomes:
>
> * All the interaction between picotls and quicly are accompanied by
> "epoch". Handshake messages are attributed with their epochs so that
> they do not get protected by the wrong key, or so that octets received
> under an incorrect encryption context cannot be misused.
>
> * All the traffic keys are governed by quicly (managing some traffic
> keys in TLS while managing PNE key in QUIC seems messy).
>
> * The Initial key is setup by quicly, wheeras other traffic keys are
> installed by picotls by calling a callback named
> update_traffic_key_cb. The callback accepts and installs 6 keys in
> total: for three levels (i.e. 0-RTT, handshake, 1-RTT) in two
> directions (send-side and receive-side).
>
> * Three PN spaces have their own AEAD encryption key. Initial PN and
> Handshake PN spaces have one aead decryption key each. Application PN
> space has up to two decryption keys: either for 0-RTT and 1-RTT or for
> two 1-RTT keys during key update.
>
> It was a pain to have a dedicated frame encoding for CRYPTO_HS, even
> though we can reuse (and I reused) the retransmission and reassembly
> logic of QUIC streams for the handshake flows. About a half of the
> code size increase comes from that (the other half comes from the
> added abstraction for having two contexts for the handshake). I would
> prefer reusing the STREAM frame encoding for the handshake data. We
> could possibly use a different base offset (i.e. for CRYPTO_HS frames
> we could use 0b00011XXX, whereas the STREAM frames use 0b00010XXX), as
> well as omitting the Stream ID field.
>
> Overall, now that I have a PoC, I am more confident that the proposed
> approach is the correct path forward. It *simplifies* the QUIC stack
> at the same time giving us better security properties as well as
> fixing various issues in the current design (as discussed in the
> design doc).
>
>
> 2018-05-23 10:30 GMT+09:00 Ian Swett <ianswett=40google.com@dmarc.ietf.org
> >:
> > Dear QUIC WG,
> >
> >
> > On behalf of the Stream 0 Design Team, I am pleased to report that we
> have
> > consensus on a proposed approach to share with the WG. The DT's proposal
> > will make QUIC and TLS work closer together and incorporates ideas from
> > DTLS, but it does not use the DTLS protocol itself.
> >
> >
> > The DT believes this solves the important open Stream 0 issues. The
> proposal
> > will be a bit more invasive in TLS, but we believe it is the right
> long-term
> > direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and Mint) are
> > willing and able to do the work necessary.. A number of stacks are
> currently
> > working on implementations of this new approach, which we hope to have in
> > time for the Interim meeting.
> >
> >
> > A design document describing the overall approach can be found at:
> >
> > https://docs.google.com/document/d/1fRsJqPinJl8N3b-
> bflDRV6auojfJLkxddT93j6SwHY8/edit
> >
> >
> > A PR making the changes to the QUIC documents can be found at:
> >
> > https://github.com/quicwg/base-drafts/pull/1377
> >
> >
> > A few design details did not have clear consensus, but it was felt it
> would
> > be better to discuss those in the wider WG than delay the design team.  A
> > consistent choice was made in the PR and these issues are mentioned in
> > Appendix B of the design doc.
> >
> >
> > As always, comments and questions welcome. That said, this is a big PR
> and
> > we recognize that some editorial work is going to be needed before
> merging.
> > In the interest of letting people follow along, and to keep github from
> > falling over, we ask people to keep discussion on the mailing list and
> > refrain from making PR comments.
> >
> >
> > See you in Kista!
> >
> >
> > Ian and Eric
>
>
>
> --
> Kazuho Oku
>
>

--000000000000705907056cd9cd89
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Thank you for your implementation and your report -- this =
is terrific and helpful!<div><br></div><div>On your note about CRYPTO_HS fr=
ames, I think your idea is clever. Just to ensure that I am understanding i=
t correctly, I believe you&#39;re proposing defining:<br>0x10 - 0x17: STREA=
M frame</div><div>0x18 - 0x1F: CRYPTO_HS frame<br><br></div><div>We can the=
 same frame format for CRYPTO_HS as STREAM except that CRYPTO_HS will not h=
ave the stream ID field. This means an implementation handling these frames=
 can reuse the stream machinery with a small change to parse the header bit=
s as follows:</div><div><br></div><div>if (type &amp; 0x10)=C2=A0 {<span st=
yle=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;fon=
t-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-=
weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-tran=
sform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255=
,255);text-decoration-style:initial;text-decoration-color:initial;float:non=
e;display:inline">=C2=A0 // STREAM or CRYPTO_HS frame</span></div><div>=C2=
=A0 =C2=A0 if (type &amp; 0x08) streamID =3D varint_consume(frame);<br>=C2=
=A0 =C2=A0 if (type &amp; 0x04) offset =3D varint_consume(frame);<br><span =
style=3D"color:rgb(34,34,34);font-family:arial,sans-serif;font-size:small;f=
ont-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;fon=
t-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-tr=
ansform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,2=
55,255);text-decoration-style:initial;text-decoration-color:initial;float:n=
one;display:inline">=C2=A0 =C2=A0 if (type &amp; 0x02) length =3D varint_co=
nsume(frame);</span><br style=3D"color:rgb(34,34,34);font-family:arial,sans=
-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font=
-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start=
;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;ba=
ckground-color:rgb(255,255,255);text-decoration-style:initial;text-decorati=
on-color:initial"><span style=3D"color:rgb(34,34,34);font-family:arial,sans=
-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font=
-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start=
;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;ba=
ckground-color:rgb(255,255,255);text-decoration-style:initial;text-decorati=
on-color:initial;float:none;display:inline">=C2=A0 =C2=A0 if (type &amp; 0x=
01) fin =3D 1;</span></div><div><span style=3D"color:rgb(34,34,34);font-fam=
ily:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatur=
es:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;te=
xt-align:start;text-indent:0px;text-transform:none;white-space:normal;word-=
spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial=
;text-decoration-color:initial;float:none;display:inline">=C2=A0 =C2=A0 rea=
d body if present</span></div><div><span style=3D"color:rgb(34,34,34);font-=
family:arial,sans-serif;font-size:small;font-style:normal;font-variant-liga=
tures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal=
;text-align:start;text-indent:0px;text-transform:none;white-space:normal;wo=
rd-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:init=
ial;text-decoration-color:initial;float:none;display:inline">}</span></div>=
</div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Tue, May=
 22, 2018 at 9:57 PM, Kazuho Oku <span dir=3D"ltr">&lt;<a href=3D"mailto:ka=
zuhooku@gmail.com" target=3D"_blank">kazuhooku@gmail.com</a>&gt;</span> wro=
te:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex">FWIW, I am happy to tell you that I h=
ave a working PoC code for the<br>
proposed approach.<br>
<br>
On the QUIC side, I saw 2% (124 lines) increase in code size (more on<br>
that below). On the TLS side, I also saw 2% (175 lines) increase.<br>
However please look at the code size change especially on the QUIC<br>
side with grain of salt, as it is just a PoC.<br>
<br>
As expected, the key and encryption-level management on the QUIC side<br>
became very clean. Following are some of the design decisions I made<br>
as well as the outcomes:<br>
<br>
* All the interaction between picotls and quicly are accompanied by<br>
&quot;epoch&quot;. Handshake messages are attributed with their epochs so t=
hat<br>
they do not get protected by the wrong key, or so that octets received<br>
under an incorrect encryption context cannot be misused.<br>
<br>
* All the traffic keys are governed by quicly (managing some traffic<br>
keys in TLS while managing PNE key in QUIC seems messy).<br>
<br>
* The Initial key is setup by quicly, wheeras other traffic keys are<br>
installed by picotls by calling a callback named<br>
update_traffic_key_cb. The callback accepts and installs 6 keys in<br>
total: for three levels (i.e. 0-RTT, handshake, 1-RTT) in two<br>
directions (send-side and receive-side).<br>
<br>
* Three PN spaces have their own AEAD encryption key. Initial PN and<br>
Handshake PN spaces have one aead decryption key each. Application PN<br>
space has up to two decryption keys: either for 0-RTT and 1-RTT or for<br>
two 1-RTT keys during key update.<br>
<br>
It was a pain to have a dedicated frame encoding for CRYPTO_HS, even<br>
though we can reuse (and I reused) the retransmission and reassembly<br>
logic of QUIC streams for the handshake flows. About a half of the<br>
code size increase comes from that (the other half comes from the<br>
added abstraction for having two contexts for the handshake). I would<br>
prefer reusing the STREAM frame encoding for the handshake data. We<br>
could possibly use a different base offset (i.e. for CRYPTO_HS frames<br>
we could use 0b00011XXX, whereas the STREAM frames use 0b00010XXX), as<br>
well as omitting the Stream ID field.<br>
<br>
Overall, now that I have a PoC, I am more confident that the proposed<br>
approach is the correct path forward. It *simplifies* the QUIC stack<br>
at the same time giving us better security properties as well as<br>
fixing various issues in the current design (as discussed in the<br>
design doc).<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
2018-05-23 10:30 GMT+09:00 Ian Swett &lt;ianswett=3D<a href=3D"mailto:40goo=
gle.com@dmarc.ietf.org">40google.com@dmarc.<wbr>ietf.org</a>&gt;:<br>
&gt; Dear QUIC WG,<br>
&gt;<br>
&gt;<br>
&gt; On behalf of the Stream 0 Design Team, I am pleased to report that we =
have<br>
&gt; consensus on a proposed approach to share with the WG. The DT&#39;s pr=
oposal<br>
&gt; will make QUIC and TLS work closer together and incorporates ideas fro=
m<br>
&gt; DTLS, but it does not use the DTLS protocol itself.<br>
&gt;<br>
&gt;<br>
&gt; The DT believes this solves the important open Stream 0 issues. The pr=
oposal<br>
&gt; will be a bit more invasive in TLS, but we believe it is the right lon=
g-term<br>
&gt; direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and Mint) a=
re<br>
&gt; willing and able to do the work necessary.. A number of stacks are cur=
rently<br>
&gt; working on implementations of this new approach, which we hope to have=
 in<br>
&gt; time for the Interim meeting.<br>
&gt;<br>
&gt;<br>
&gt; A design document describing the overall approach can be found at:<br>
&gt;<br>
&gt; <a href=3D"https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6a=
uojfJLkxddT93j6SwHY8/edit" rel=3D"noreferrer" target=3D"_blank">https://doc=
s.google.com/<wbr>document/d/1fRsJqPinJl8N3b-<wbr>bflDRV6auojfJLkxddT93j6Sw=
HY8/<wbr>edit</a><br>
&gt;<br>
&gt;<br>
&gt; A PR making the changes to the QUIC documents can be found at:<br>
&gt;<br>
&gt; <a href=3D"https://github.com/quicwg/base-drafts/pull/1377" rel=3D"nor=
eferrer" target=3D"_blank">https://github.com/quicwg/<wbr>base-drafts/pull/=
1377</a><br>
&gt;<br>
&gt;<br>
&gt; A few design details did not have clear consensus, but it was felt it =
would<br>
&gt; be better to discuss those in the wider WG than delay the design team.=
=C2=A0 A<br>
&gt; consistent choice was made in the PR and these issues are mentioned in=
<br>
&gt; Appendix B of the design doc.<br>
&gt;<br>
&gt;<br>
&gt; As always, comments and questions welcome. That said, this is a big PR=
 and<br>
&gt; we recognize that some editorial work is going to be needed before mer=
ging.<br>
&gt; In the interest of letting people follow along, and to keep github fro=
m<br>
&gt; falling over, we ask people to keep discussion on the mailing list and=
<br>
&gt; refrain from making PR comments.<br>
&gt;<br>
&gt;<br>
&gt; See you in Kista!<br>
&gt;<br>
&gt;<br>
&gt; Ian and Eric<br>
<br>
<br>
<br>
</div></div><span class=3D"HOEnZb"><font color=3D"#888888">-- <br>
Kazuho Oku<br>
<br>
</font></span></blockquote></div><br></div>

--000000000000705907056cd9cd89--


From nobody Tue May 22 23:57:11 2018
Return-Path: <kazuhooku@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 667A1124B0A for <quic@ietfa.amsl.com>; Tue, 22 May 2018 23:57:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 icoSMS6qr5VB for <quic@ietfa.amsl.com>; Tue, 22 May 2018 23:57:06 -0700 (PDT)
Received: from mail-pl0-x22d.google.com (mail-pl0-x22d.google.com [IPv6:2607:f8b0:400e:c01::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 665D91243FE for <quic@ietf.org>; Tue, 22 May 2018 23:57:06 -0700 (PDT)
Received: by mail-pl0-x22d.google.com with SMTP id w19-v6so12425769plq.4 for <quic@ietf.org>; Tue, 22 May 2018 23:57:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=XRKPDyQIjJ65EV1Th+vhE7TArrbq2Q0U3haGMt8giC4=; b=jYhy2NMv757odftA8IOegGAXZzJ8DJMhUaE5dLQGFXmBnbnLxTe94fqMO60J3EH/BE KsnYh6bUcUrGigjwgBCX2OA/gzJSFeTNuP+KgMFX+o0IG/FrATrRdsQGfzuOJTuuRwl7 Y8Mh+HMy1DjV53GY8jGiVoxT+WYTyxeouUAELxRFKPllyBvkElMT0ui1FGtf9wWQGU0f hoN+2GeAlMZqiYR0mkvqmbgoQ2pkXYFCgBIge+9kkiD+JkF0Xj5LG0E1UR1j+hWgMCCq xHiakjbGa9+fEY198dffaqGS3OYUGngd4kO/BzHQXg+D0kuCNOazrfFS76AIo9gFUhFL Q/HA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=XRKPDyQIjJ65EV1Th+vhE7TArrbq2Q0U3haGMt8giC4=; b=eecmm0PkS4W3lZ3t3FBIGEKfIYTaB/r18h/Ts+LyytFwe+Iwquln8zAXVj2a32Eqz7 DlTX4dO6Qwo3HASnB1Klap27LBy1O7jlqebOB04h90JNiDYlTiDIWkSVwYGCUDFrBxwr x33EMbul3DGDFYBhQaku72U5LfjY4FQdP5YDq9JSbFwBHcjzFrOf5QKSZdsojArnzkGc dBfLeNzCL2x4gOwoqT7wwJ8PdRMtKl5eaRq0DnUxB7rcqEKpRzcIXrRqxbmIch26tRGc xWbxL059IZWRV9SYFnZN9yha7pPUsH0yim2CG7j9Z8mMz2VJ3JmIKdAn1zf2xZxOqyZw FjTA==
X-Gm-Message-State: ALKqPwd2O8ZbHZt+H2YlWIhuKZUMWgJFecauGPZ1UXfO0ozK67YDp0yL 6waBjsfLpaClxUPssw9PSYU4auSPODpCwCGXpmE=
X-Google-Smtp-Source: AB8JxZoGcxPiLd8p47fL72dDofIZeQdyv2C1uKvUug5J4a31/LSEbSI+Ts8Bqf4A6h9qLjjz4zVbw4ISVwIcbTaXBIQ=
X-Received: by 2002:a17:902:b409:: with SMTP id x9-v6mr1754561plr.180.1527058625581;  Tue, 22 May 2018 23:57:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:1189:0:0:0:0 with HTTP; Tue, 22 May 2018 23:57:04 -0700 (PDT)
In-Reply-To: <CACpbDcddWz_i5GoNWYfDAdWKcX0_gOMiKk=ORVABGPE8+7c8Vw@mail.gmail.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CANatvzzS+T4HcddCemKF7bb1BmACFp=R4n+YMWkq7tnZaUXw4w@mail.gmail.com> <CACpbDcddWz_i5GoNWYfDAdWKcX0_gOMiKk=ORVABGPE8+7c8Vw@mail.gmail.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Wed, 23 May 2018 15:57:04 +0900
Message-ID: <CANatvzwC9ueFVjgg_hPsNkz1Wu4qYjKiWhzyj+UVnSby177Ehg@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: Jana Iyengar <jri.ietf@gmail.com>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Eric Rescorla <ekr@mozilla.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/01R_ejlEhbYCOZqxTZ_kEdzyeVk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 06:57:09 -0000

2018-05-23 15:39 GMT+09:00 Jana Iyengar <jri.ietf@gmail.com>:
> Thank you for your implementation and your report -- this is terrific and
> helpful!
>
> On your note about CRYPTO_HS frames, I think your idea is clever. Just to
> ensure that I am understanding it correctly, I believe you're proposing
> defining:
> 0x10 - 0x17: STREAM frame
> 0x18 - 0x1F: CRYPTO_HS frame
>
> We can the same frame format for CRYPTO_HS as STREAM except that CRYPTO_HS
> will not have the stream ID field. This means an implementation handling
> these frames can reuse the stream machinery with a small change to parse the
> header bits as follows:
>
> if (type & 0x10)  {  // STREAM or CRYPTO_HS frame
>     if (type & 0x08) streamID = varint_consume(frame);
>     if (type & 0x04) offset = varint_consume(frame);
>     if (type & 0x02) length = varint_consume(frame);
>     if (type & 0x01) fin = 1;
>     read body if present
> }

That's correct. Considering the fact that the handshake flows are
never closed, we could do something like below to preserve some more,
by swapping the bits used for offset and fin.

0x10-0x17: STREAM frame
0x18-0x1B: CRYPTO_HS frame

if (0x10 <= type && type <= 0x1c) {
    if (type <= 0x18) {
        streamID = varint_consume(frame);
        if (type & 0x04)
            fin = 1;
    }
    if (type & 0x02)
        length = varint_consume(frame);
    if (type & 0x01)
        offset = varint_consume(frame);
}

>
> On Tue, May 22, 2018 at 9:57 PM, Kazuho Oku <kazuhooku@gmail.com> wrote:
>>
>> FWIW, I am happy to tell you that I have a working PoC code for the
>> proposed approach.
>>
>> On the QUIC side, I saw 2% (124 lines) increase in code size (more on
>> that below). On the TLS side, I also saw 2% (175 lines) increase.
>> However please look at the code size change especially on the QUIC
>> side with grain of salt, as it is just a PoC.
>>
>> As expected, the key and encryption-level management on the QUIC side
>> became very clean. Following are some of the design decisions I made
>> as well as the outcomes:
>>
>> * All the interaction between picotls and quicly are accompanied by
>> "epoch". Handshake messages are attributed with their epochs so that
>> they do not get protected by the wrong key, or so that octets received
>> under an incorrect encryption context cannot be misused.
>>
>> * All the traffic keys are governed by quicly (managing some traffic
>> keys in TLS while managing PNE key in QUIC seems messy).
>>
>> * The Initial key is setup by quicly, wheeras other traffic keys are
>> installed by picotls by calling a callback named
>> update_traffic_key_cb. The callback accepts and installs 6 keys in
>> total: for three levels (i.e. 0-RTT, handshake, 1-RTT) in two
>> directions (send-side and receive-side).
>>
>> * Three PN spaces have their own AEAD encryption key. Initial PN and
>> Handshake PN spaces have one aead decryption key each. Application PN
>> space has up to two decryption keys: either for 0-RTT and 1-RTT or for
>> two 1-RTT keys during key update.
>>
>> It was a pain to have a dedicated frame encoding for CRYPTO_HS, even
>> though we can reuse (and I reused) the retransmission and reassembly
>> logic of QUIC streams for the handshake flows. About a half of the
>> code size increase comes from that (the other half comes from the
>> added abstraction for having two contexts for the handshake). I would
>> prefer reusing the STREAM frame encoding for the handshake data. We
>> could possibly use a different base offset (i.e. for CRYPTO_HS frames
>> we could use 0b00011XXX, whereas the STREAM frames use 0b00010XXX), as
>> well as omitting the Stream ID field.
>>
>> Overall, now that I have a PoC, I am more confident that the proposed
>> approach is the correct path forward. It *simplifies* the QUIC stack
>> at the same time giving us better security properties as well as
>> fixing various issues in the current design (as discussed in the
>> design doc).
>>
>>
>> 2018-05-23 10:30 GMT+09:00 Ian Swett
>> <ianswett=40google.com@dmarc.ietf.org>:
>> > Dear QUIC WG,
>> >
>> >
>> > On behalf of the Stream 0 Design Team, I am pleased to report that we
>> > have
>> > consensus on a proposed approach to share with the WG. The DT's proposal
>> > will make QUIC and TLS work closer together and incorporates ideas from
>> > DTLS, but it does not use the DTLS protocol itself.
>> >
>> >
>> > The DT believes this solves the important open Stream 0 issues. The
>> > proposal
>> > will be a bit more invasive in TLS, but we believe it is the right
>> > long-term
>> > direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and Mint) are
>> > willing and able to do the work necessary.. A number of stacks are
>> > currently
>> > working on implementations of this new approach, which we hope to have
>> > in
>> > time for the Interim meeting.
>> >
>> >
>> > A design document describing the overall approach can be found at:
>> >
>> >
>> > https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit
>> >
>> >
>> > A PR making the changes to the QUIC documents can be found at:
>> >
>> > https://github.com/quicwg/base-drafts/pull/1377
>> >
>> >
>> > A few design details did not have clear consensus, but it was felt it
>> > would
>> > be better to discuss those in the wider WG than delay the design team.
>> > A
>> > consistent choice was made in the PR and these issues are mentioned in
>> > Appendix B of the design doc.
>> >
>> >
>> > As always, comments and questions welcome. That said, this is a big PR
>> > and
>> > we recognize that some editorial work is going to be needed before
>> > merging.
>> > In the interest of letting people follow along, and to keep github from
>> > falling over, we ask people to keep discussion on the mailing list and
>> > refrain from making PR comments.
>> >
>> >
>> > See you in Kista!
>> >
>> >
>> > Ian and Eric
>>
>>
>>
>> --
>> Kazuho Oku
>>
>



-- 
Kazuho Oku


From nobody Wed May 23 00:05:17 2018
Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BF3312DA07 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 00:05:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Nol0N7_MPW25 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 00:05:13 -0700 (PDT)
Received: from mail-pg0-x230.google.com (mail-pg0-x230.google.com [IPv6:2607:f8b0:400e:c05::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E4E91124C27 for <quic@ietf.org>; Wed, 23 May 2018 00:05:12 -0700 (PDT)
Received: by mail-pg0-x230.google.com with SMTP id e21-v6so4085882pgv.0 for <quic@ietf.org>; Wed, 23 May 2018 00:05:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :mime-version; bh=bmonkrGfmbB9M7himuKA0YiL8Sq4w+VtoWmn2TUWYrU=; b=YHuc3LHOi/fH60xuNdJok8vwFxSxaSZHbnerDVKfkX7/I1lOnytXZSMoUxizZT+rX0 dtzL5fClfxiorzz9cNaT6hif40rTRiAPR0oBS+QjDMLeKKXMsVfVWa6yZhIQjL/qoo7N pJyOgjGVoDHYkaevNS5bTjKXwjkGr2z/YcbhFcsnB/CSW3hCq9RxZzzeeJ1VT+NL9NY7 kMmaQsPgbTEq0VhnUI+rdONJ49Gn0yocMvhGjsHy0/2vDJHcoKRQrxnw90NcNMMPRVEE VmawiljlnUXRocffLr0N2kJTWpctLZLIWavQbjmnkuBMpBBOqTI3zPZ6AlkWeGiv6G9g U+Pg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:mime-version; bh=bmonkrGfmbB9M7himuKA0YiL8Sq4w+VtoWmn2TUWYrU=; b=ib6Y0SRto/WR66nV6jQMqHWTioTtSU3eK7j3x2m3z9M9tdNxOa7DurAZdrooQiA3bJ bTzcm7oY/V7l03/oaNUUloGmEKqXCDfmxf920sRHnu8kGM1a04E/Rtme2pU10gEggpgh 1tFt2x6g+SCAq0qWuGGm0Ed1Bu/vSYrt8cHXAXJuY2xZCpq2zkIg240kH0I/EDjmeYtL hBDjeMqHhrlZuhMMmJX/Nxr/gD7/8JtphBaO3czq5AT2S9lP6wBChUb6nFzVVQvmx5p8 QuB8sw0GAp4RGQ1mxiR/SBbqEfqdtPAj/wmvZCLnfZaL60clxBs6IZrSc88ZXKj041dp TWMA==
X-Gm-Message-State: ALKqPwfZBY7uu4C8PJjjrL2V4LyISj7cCBsw+7FKtPyGKBFp6LqWFJyy 9M4JMZqJm6PKyB7fJMo1AwWL/nJ+
X-Google-Smtp-Source: AB8JxZr+SUmD/EYtnUJmtdOpX8k0Ur0Y7Xem1ujUnb27IM1eSYbj9FV178o5up9MrT+jL4XYQGZQwA==
X-Received: by 2002:a62:1306:: with SMTP id b6-v6mr1682972pfj.58.1527059112338;  Wed, 23 May 2018 00:05:12 -0700 (PDT)
Received: from DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM ([40.101.73.69]) by smtp.gmail.com with ESMTPSA id h75-v6sm35936281pfh.148.2018.05.23.00.05.10 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 23 May 2018 00:05:11 -0700 (PDT)
From: =?iso-8859-1?Q?Mikkel_Fahn=F8e_J=F8rgensen?= <mikkelfj@gmail.com>
To: Jana Iyengar <jri.ietf@gmail.com>, Kazuho Oku <kazuhooku@gmail.com>
CC: Eric Rescorla <ekr@mozilla.com>, IETF QUIC WG <quic@ietf.org>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Subject: Re: Stream0 Design Team Proposal
Thread-Topic: Stream0 Design Team Proposal
Thread-Index: AXdfQTVfdsMHO8uMeTvioDg7HZXh4ndxcEZUd0JPRHqxsKhcvw==
X-MS-Exchange-MessageSentRepresentingType: 2
Date: Wed, 23 May 2018 07:05:07 +0000
Message-ID: <DB6PR10MB17663BEF867A18F421B796B2AC6B0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CANatvzzS+T4HcddCemKF7bb1BmACFp=R4n+YMWkq7tnZaUXw4w@mail.gmail.com>, <CACpbDcddWz_i5GoNWYfDAdWKcX0_gOMiKk=ORVABGPE8+7c8Vw@mail.gmail.com>
In-Reply-To: <CACpbDcddWz_i5GoNWYfDAdWKcX0_gOMiKk=ORVABGPE8+7c8Vw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator: 
X-MS-Exchange-Organization-RecordReviewCfmType: 0
Content-Type: multipart/alternative; boundary="_000_DB6PR10MB17663BEF867A18F421B796B2AC6B0DB6PR10MB1766EURP_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Uu-STnv1b7u-7DH7qZKnGdFJE6k>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 07:05:16 -0000

--_000_DB6PR10MB17663BEF867A18F421B796B2AC6B0DB6PR10MB1766EURP_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I only had a quick pass over text but I like the concept and appreciate the=
 rationales given.

In particular it seems to decouple QUIC from TLS and it may be worth keepin=
g as a design guideline. Consider a separate theoretical simplified handsha=
ke for embedded devices that always negotiate via ed/x25519 - would that fi=
t cleanly in framing structure and handshake messaging?

On the open issue of confirming client finished - I lean towards an explici=
t signal unless that leads to eternal ping pong. It takes out the guesswork=
 and seen from a generic handshake perspective it may be more actionable wi=
thout detailing why a key epoch was locked in.

Mikkel

________________________________
From: QUIC <quic-bounces@ietf.org> on behalf of Jana Iyengar <jri.ietf@gmai=
l.com>
Sent: Wednesday, May 23, 2018 8:39:53 AM
To: Kazuho Oku
Cc: Eric Rescorla; IETF QUIC WG; Ian Swett
Subject: Re: Stream0 Design Team Proposal

Thank you for your implementation and your report -- this is terrific and h=
elpful!

On your note about CRYPTO_HS frames, I think your idea is clever. Just to e=
nsure that I am understanding it correctly, I believe you're proposing defi=
ning:
0x10 - 0x17: STREAM frame
0x18 - 0x1F: CRYPTO_HS frame

We can the same frame format for CRYPTO_HS as STREAM except that CRYPTO_HS =
will not have the stream ID field. This means an implementation handling th=
ese frames can reuse the stream machinery with a small change to parse the =
header bits as follows:

if (type & 0x10)  {  // STREAM or CRYPTO_HS frame
    if (type & 0x08) streamID =3D varint_consume(frame);
    if (type & 0x04) offset =3D varint_consume(frame);
    if (type & 0x02) length =3D varint_consume(frame);
    if (type & 0x01) fin =3D 1;
    read body if present
}

On Tue, May 22, 2018 at 9:57 PM, Kazuho Oku <kazuhooku@gmail.com<mailto:kaz=
uhooku@gmail.com>> wrote:
FWIW, I am happy to tell you that I have a working PoC code for the
proposed approach.

On the QUIC side, I saw 2% (124 lines) increase in code size (more on
that below). On the TLS side, I also saw 2% (175 lines) increase.
However please look at the code size change especially on the QUIC
side with grain of salt, as it is just a PoC.

As expected, the key and encryption-level management on the QUIC side
became very clean. Following are some of the design decisions I made
as well as the outcomes:

* All the interaction between picotls and quicly are accompanied by
"epoch". Handshake messages are attributed with their epochs so that
they do not get protected by the wrong key, or so that octets received
under an incorrect encryption context cannot be misused.

* All the traffic keys are governed by quicly (managing some traffic
keys in TLS while managing PNE key in QUIC seems messy).

* The Initial key is setup by quicly, wheeras other traffic keys are
installed by picotls by calling a callback named
update_traffic_key_cb. The callback accepts and installs 6 keys in
total: for three levels (i.e. 0-RTT, handshake, 1-RTT) in two
directions (send-side and receive-side).

* Three PN spaces have their own AEAD encryption key. Initial PN and
Handshake PN spaces have one aead decryption key each. Application PN
space has up to two decryption keys: either for 0-RTT and 1-RTT or for
two 1-RTT keys during key update.

It was a pain to have a dedicated frame encoding for CRYPTO_HS, even
though we can reuse (and I reused) the retransmission and reassembly
logic of QUIC streams for the handshake flows. About a half of the
code size increase comes from that (the other half comes from the
added abstraction for having two contexts for the handshake). I would
prefer reusing the STREAM frame encoding for the handshake data. We
could possibly use a different base offset (i.e. for CRYPTO_HS frames
we could use 0b00011XXX, whereas the STREAM frames use 0b00010XXX), as
well as omitting the Stream ID field.

Overall, now that I have a PoC, I am more confident that the proposed
approach is the correct path forward. It *simplifies* the QUIC stack
at the same time giving us better security properties as well as
fixing various issues in the current design (as discussed in the
design doc).


2018-05-23 10:30 GMT+09:00 Ian Swett <ianswett=3D40google.com@dmarc.ietf.or=
g<mailto:40google.com@dmarc.ietf.org>>:
> Dear QUIC WG,
>
>
> On behalf of the Stream 0 Design Team, I am pleased to report that we hav=
e
> consensus on a proposed approach to share with the WG. The DT's proposal
> will make QUIC and TLS work closer together and incorporates ideas from
> DTLS, but it does not use the DTLS protocol itself.
>
>
> The DT believes this solves the important open Stream 0 issues. The propo=
sal
> will be a bit more invasive in TLS, but we believe it is the right long-t=
erm
> direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and Mint) are
> willing and able to do the work necessary.. A number of stacks are curren=
tly
> working on implementations of this new approach, which we hope to have in
> time for the Interim meeting.
>
>
> A design document describing the overall approach can be found at:
>
> https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j=
6SwHY8/edit
>
>
> A PR making the changes to the QUIC documents can be found at:
>
> https://github.com/quicwg/base-drafts/pull/1377
>
>
> A few design details did not have clear consensus, but it was felt it wou=
ld
> be better to discuss those in the wider WG than delay the design team.  A
> consistent choice was made in the PR and these issues are mentioned in
> Appendix B of the design doc.
>
>
> As always, comments and questions welcome. That said, this is a big PR an=
d
> we recognize that some editorial work is going to be needed before mergin=
g.
> In the interest of letting people follow along, and to keep github from
> falling over, we ask people to keep discussion on the mailing list and
> refrain from making PR comments.
>
>
> See you in Kista!
>
>
> Ian and Eric



--
Kazuho Oku



--_000_DB6PR10MB17663BEF867A18F421B796B2AC6B0DB6PR10MB1766EURP_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta content=3D"text/html; charset=3Dutf-8">
</head>
<body>
<div id=3D"compose-container" itemscope=3D"" itemtype=3D"https://schema.org=
/EmailMessage" style=3D"direction:ltr">
<span itemprop=3D"creator" itemscope=3D"" itemtype=3D"https://schema.org/Or=
ganization"><span itemprop=3D"name"></span></span>
<div>
<div>
<div style=3D"direction:ltr">I only had a quick pass over text but I like t=
he concept and appreciate the rationales given.</div>
<div><br>
</div>
<div style=3D"direction:ltr">In particular it seems to decouple QUIC from T=
LS and it may be worth keeping as a design guideline. Consider a separate t=
heoretical simplified handshake for embedded devices that always negotiate =
via ed/x25519 - would that fit cleanly
 in framing structure and handshake messaging?</div>
<div><br>
</div>
<div style=3D"direction:ltr">On the open issue of confirming client finishe=
d - I lean towards an explicit signal unless that leads to eternal ping pon=
g. It takes out the guesswork and seen from a generic handshake perspective=
 it may be more actionable without
 detailing why a key epoch was locked in.</div>
<div><br>
</div>
<div style=3D"direction:ltr">Mikkel</div>
</div>
<div><br>
</div>
<div class=3D"acompli_signature"></div>
</div>
</div>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" co=
lor=3D"#000000" style=3D"font-size:11pt"><b>From:</b> QUIC &lt;quic-bounces=
@ietf.org&gt; on behalf of Jana Iyengar &lt;jri.ietf@gmail.com&gt;<br>
<b>Sent:</b> Wednesday, May 23, 2018 8:39:53 AM<br>
<b>To:</b> Kazuho Oku<br>
<b>Cc:</b> Eric Rescorla; IETF QUIC WG; Ian Swett<br>
<b>Subject:</b> Re: Stream0 Design Team Proposal</font>
<div>&nbsp;</div>
</div>
<div>
<div dir=3D"ltr">Thank you for your implementation and your report -- this =
is terrific and helpful!
<div><br>
</div>
<div>On your note about CRYPTO_HS frames, I think your idea is clever. Just=
 to ensure that I am understanding it correctly, I believe you're proposing=
 defining:<br>
0x10 - 0x17: STREAM frame</div>
<div>0x18 - 0x1F: CRYPTO_HS frame<br>
<br>
</div>
<div>We can the same frame format for CRYPTO_HS as STREAM except that CRYPT=
O_HS will not have the stream ID field. This means an implementation handli=
ng these frames can reuse the stream machinery with a small change to parse=
 the header bits as follows:</div>
<div><br>
</div>
<div>if (type &amp; 0x10)&nbsp; {<span style=3D"color:rgb(34,34,34); font-f=
amily:arial,sans-serif; font-size:small; font-style:normal; font-weight:400=
; letter-spacing:normal; text-align:start; text-indent:0px; text-transform:=
none; white-space:normal; word-spacing:0px; background-color:rgb(255,255,25=
5); float:none; display:inline">&nbsp;
 // STREAM or CRYPTO_HS frame</span></div>
<div>&nbsp; &nbsp; if (type &amp; 0x08) streamID =3D varint_consume(frame);=
<br>
&nbsp; &nbsp; if (type &amp; 0x04) offset =3D varint_consume(frame);<br>
<span style=3D"color:rgb(34,34,34); font-family:arial,sans-serif; font-size=
:small; font-style:normal; font-weight:400; letter-spacing:normal; text-ali=
gn:start; text-indent:0px; text-transform:none; white-space:normal; word-sp=
acing:0px; background-color:rgb(255,255,255); float:none; display:inline">&=
nbsp;
 &nbsp; if (type &amp; 0x02) length =3D varint_consume(frame);</span><br st=
yle=3D"color:rgb(34,34,34); font-family:arial,sans-serif; font-size:small; =
font-style:normal; font-weight:400; letter-spacing:normal; text-align:start=
; text-indent:0px; text-transform:none; white-space:normal; word-spacing:0p=
x; background-color:rgb(255,255,255)">
<span style=3D"color:rgb(34,34,34); font-family:arial,sans-serif; font-size=
:small; font-style:normal; font-weight:400; letter-spacing:normal; text-ali=
gn:start; text-indent:0px; text-transform:none; white-space:normal; word-sp=
acing:0px; background-color:rgb(255,255,255); float:none; display:inline">&=
nbsp;
 &nbsp; if (type &amp; 0x01) fin =3D 1;</span></div>
<div><span style=3D"color:rgb(34,34,34); font-family:arial,sans-serif; font=
-size:small; font-style:normal; font-weight:400; letter-spacing:normal; tex=
t-align:start; text-indent:0px; text-transform:none; white-space:normal; wo=
rd-spacing:0px; background-color:rgb(255,255,255); float:none; display:inli=
ne">&nbsp;
 &nbsp; read body if present</span></div>
<div><span style=3D"color:rgb(34,34,34); font-family:arial,sans-serif; font=
-size:small; font-style:normal; font-weight:400; letter-spacing:normal; tex=
t-align:start; text-indent:0px; text-transform:none; white-space:normal; wo=
rd-spacing:0px; background-color:rgb(255,255,255); float:none; display:inli=
ne">}</span></div>
</div>
<div class=3D"gmail_extra"><br>
<div class=3D"gmail_quote">On Tue, May 22, 2018 at 9:57 PM, Kazuho Oku <spa=
n dir=3D"ltr">
&lt;<a href=3D"mailto:kazuhooku@gmail.com" target=3D"_blank">kazuhooku@gmai=
l.com</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex; border-left:1=
px #ccc solid; padding-left:1ex">
FWIW, I am happy to tell you that I have a working PoC code for the<br>
proposed approach.<br>
<br>
On the QUIC side, I saw 2% (124 lines) increase in code size (more on<br>
that below). On the TLS side, I also saw 2% (175 lines) increase.<br>
However please look at the code size change especially on the QUIC<br>
side with grain of salt, as it is just a PoC.<br>
<br>
As expected, the key and encryption-level management on the QUIC side<br>
became very clean. Following are some of the design decisions I made<br>
as well as the outcomes:<br>
<br>
* All the interaction between picotls and quicly are accompanied by<br>
&quot;epoch&quot;. Handshake messages are attributed with their epochs so t=
hat<br>
they do not get protected by the wrong key, or so that octets received<br>
under an incorrect encryption context cannot be misused.<br>
<br>
* All the traffic keys are governed by quicly (managing some traffic<br>
keys in TLS while managing PNE key in QUIC seems messy).<br>
<br>
* The Initial key is setup by quicly, wheeras other traffic keys are<br>
installed by picotls by calling a callback named<br>
update_traffic_key_cb. The callback accepts and installs 6 keys in<br>
total: for three levels (i.e. 0-RTT, handshake, 1-RTT) in two<br>
directions (send-side and receive-side).<br>
<br>
* Three PN spaces have their own AEAD encryption key. Initial PN and<br>
Handshake PN spaces have one aead decryption key each. Application PN<br>
space has up to two decryption keys: either for 0-RTT and 1-RTT or for<br>
two 1-RTT keys during key update.<br>
<br>
It was a pain to have a dedicated frame encoding for CRYPTO_HS, even<br>
though we can reuse (and I reused) the retransmission and reassembly<br>
logic of QUIC streams for the handshake flows. About a half of the<br>
code size increase comes from that (the other half comes from the<br>
added abstraction for having two contexts for the handshake). I would<br>
prefer reusing the STREAM frame encoding for the handshake data. We<br>
could possibly use a different base offset (i.e. for CRYPTO_HS frames<br>
we could use 0b00011XXX, whereas the STREAM frames use 0b00010XXX), as<br>
well as omitting the Stream ID field.<br>
<br>
Overall, now that I have a PoC, I am more confident that the proposed<br>
approach is the correct path forward. It *simplifies* the QUIC stack<br>
at the same time giving us better security properties as well as<br>
fixing various issues in the current design (as discussed in the<br>
design doc).<br>
<div class=3D"HOEnZb">
<div class=3D"h5"><br>
<br>
2018-05-23 10:30 GMT&#43;09:00 Ian Swett &lt;ianswett=3D<a href=3D"mailto:4=
0google.com@dmarc.ietf.org">40google.com@dmarc.<wbr>ietf.org</a>&gt;:<br>
&gt; Dear QUIC WG,<br>
&gt;<br>
&gt;<br>
&gt; On behalf of the Stream 0 Design Team, I am pleased to report that we =
have<br>
&gt; consensus on a proposed approach to share with the WG. The DT's propos=
al<br>
&gt; will make QUIC and TLS work closer together and incorporates ideas fro=
m<br>
&gt; DTLS, but it does not use the DTLS protocol itself.<br>
&gt;<br>
&gt;<br>
&gt; The DT believes this solves the important open Stream 0 issues. The pr=
oposal<br>
&gt; will be a bit more invasive in TLS, but we believe it is the right lon=
g-term<br>
&gt; direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and Mint) a=
re<br>
&gt; willing and able to do the work necessary.. A number of stacks are cur=
rently<br>
&gt; working on implementations of this new approach, which we hope to have=
 in<br>
&gt; time for the Interim meeting.<br>
&gt;<br>
&gt;<br>
&gt; A design document describing the overall approach can be found at:<br>
&gt;<br>
&gt; <a href=3D"https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6a=
uojfJLkxddT93j6SwHY8/edit" rel=3D"noreferrer" target=3D"_blank">
https://docs.google.com/<wbr>document/d/1fRsJqPinJl8N3b-<wbr>bflDRV6auojfJL=
kxddT93j6SwHY8/<wbr>edit</a><br>
&gt;<br>
&gt;<br>
&gt; A PR making the changes to the QUIC documents can be found at:<br>
&gt;<br>
&gt; <a href=3D"https://github.com/quicwg/base-drafts/pull/1377" rel=3D"nor=
eferrer" target=3D"_blank">
https://github.com/quicwg/<wbr>base-drafts/pull/1377</a><br>
&gt;<br>
&gt;<br>
&gt; A few design details did not have clear consensus, but it was felt it =
would<br>
&gt; be better to discuss those in the wider WG than delay the design team.=
&nbsp; A<br>
&gt; consistent choice was made in the PR and these issues are mentioned in=
<br>
&gt; Appendix B of the design doc.<br>
&gt;<br>
&gt;<br>
&gt; As always, comments and questions welcome. That said, this is a big PR=
 and<br>
&gt; we recognize that some editorial work is going to be needed before mer=
ging.<br>
&gt; In the interest of letting people follow along, and to keep github fro=
m<br>
&gt; falling over, we ask people to keep discussion on the mailing list and=
<br>
&gt; refrain from making PR comments.<br>
&gt;<br>
&gt;<br>
&gt; See you in Kista!<br>
&gt;<br>
&gt;<br>
&gt; Ian and Eric<br>
<br>
<br>
<br>
</div>
</div>
<span class=3D"HOEnZb"><font color=3D"#888888">-- <br>
Kazuho Oku<br>
<br>
</font></span></blockquote>
</div>
<br>
</div>
</div>
</body>
</html>

--_000_DB6PR10MB17663BEF867A18F421B796B2AC6B0DB6PR10MB1766EURP_--


From nobody Wed May 23 00:21:28 2018
Return-Path: <kazuhooku@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 22DCB1252BA for <quic@ietfa.amsl.com>; Wed, 23 May 2018 00:21:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 RU4R5pQ7_KcP for <quic@ietfa.amsl.com>; Wed, 23 May 2018 00:21:23 -0700 (PDT)
Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0A03B120047 for <quic@ietf.org>; Wed, 23 May 2018 00:21:23 -0700 (PDT)
Received: by mail-pg0-x229.google.com with SMTP id e21-v6so4105299pgv.0 for <quic@ietf.org>; Wed, 23 May 2018 00:21:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=pPb3j0gwCH7ra+ontKqiX0+36FMauRHToc3vq9Nyz9g=; b=D/bcDzWyUW38ulBwvLoweKEFQWOyUWisk5aswKi1M5kF5ZTt8Fd5Sh2KvkiVyQ21zS sc6h1KIOiJu4z/TxgMfXf8p2eFxRwS0ut20Qs/E0pFcthLzHuLkm9vg2lYq/OmV/cUsI tJ1pA2aAlBz8K9s7dAK5hY1s6jyBl39lR7qQauWm6YH9hxRMEjJaIqqujbvNYS+5MU1K WbfWuzqGlLK596B9oy53YklMrA9XHMvQjabWKUftBAnOGP2W4F5Z8MKN88pZIyJ6rQYp jnfxn960Ag/+onWigLZWGyz4hd4ivi3kgamCAC1ZBVAOKfaHXVaRx7SZgPbQPeOXee8V cnhw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=pPb3j0gwCH7ra+ontKqiX0+36FMauRHToc3vq9Nyz9g=; b=nMPwtvmYdAuef8NeEIfFTIj77yRTkMwixB7v9hjqTSxLwgKEUKhsco3QM3qZ9moHjL SufdTB2kbcxYP773j2MKEhtKC4mXmhG1hoageyf/fB2x3DXkOiP1KxqqOwhBI69HPdjb aMeiy24DWOcZTaStipCf3LQMNz1xBhVHtGeL5b7BYTrLIa5KMXSef9iBIckZFL33JrIE 8nFqfQo2k+0+rS1s0TF7FH/BsTjr18QcOOH+YDnrYbVA2HFHo5f/WqoIX2/gnCa6A0ea v20M91TLClyJM+O9AgHzFYteUw+PiolagZlFOg8BUvVZ2mh0uXI6y6O4nFZG/OJxeUDa 39Qg==
X-Gm-Message-State: ALKqPweFf8Qcvd2F2wqQ1q7urs/eYG9aa1tMOMvnWLdMxI6nyYE1KDDG y7SrFEYNKceY8bLuvTicsnGOOH6CKVCg9rhZ5ck=
X-Google-Smtp-Source: AB8JxZrKm/PQHSOUoy4xwmSJLexWppqoiVR+Ji04CvR69CgMV+2no4zjkFTlriUNFHlj5iqmz6Y1WtBUzAZ0nXESSJk=
X-Received: by 2002:a62:e710:: with SMTP id s16-v6mr1711709pfh.227.1527060082362;  Wed, 23 May 2018 00:21:22 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:1189:0:0:0:0 with HTTP; Wed, 23 May 2018 00:21:21 -0700 (PDT)
In-Reply-To: <DB6PR10MB17663BEF867A18F421B796B2AC6B0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CANatvzzS+T4HcddCemKF7bb1BmACFp=R4n+YMWkq7tnZaUXw4w@mail.gmail.com> <CACpbDcddWz_i5GoNWYfDAdWKcX0_gOMiKk=ORVABGPE8+7c8Vw@mail.gmail.com> <DB6PR10MB17663BEF867A18F421B796B2AC6B0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Wed, 23 May 2018 16:21:21 +0900
Message-ID: <CANatvzwiXc+JLHfNFkkpuU_ahL6FJyjZbtJF7FFpYiPbyv3-8Q@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
Cc: Jana Iyengar <jri.ietf@gmail.com>, Eric Rescorla <ekr@mozilla.com>, IETF QUIC WG <quic@ietf.org>,  Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/yYzI0HVT8SHPaYYiMysJV_LS9yc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 07:21:27 -0000

2018-05-23 16:05 GMT+09:00 Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@gmai=
l.com>:
> I only had a quick pass over text but I like the concept and appreciate t=
he
> rationales given.
>
> In particular it seems to decouple QUIC from TLS and it may be worth keep=
ing
> as a design guideline. Consider a separate theoretical simplified handsha=
ke
> for embedded devices that always negotiate via ed/x25519 - would that fit
> cleanly in framing structure and handshake messaging?

I think that is a very good question, and I believe that the answer is yes.

IIUC, the goal of any handshake protocol is to switch to a encrypted
bidirectional channel. The difference between the protocols is how
many intermediate encryption levels they will have (In TLS 1.3, we
have one intermediate level. There were no intermediate levels in the
prior versions of TLS).

If we are to adopt a handshake protocol that does not have any
intermediate encryption level, we can support it simply by ditching
the Handshake level.

If we are to adopt a handshake protocol that has multiple intermediate
levels, we can support that by splitting Handshake level into multiple
levels.

> On the open issue of confirming client finished - I lean towards an expli=
cit
> signal unless that leads to eternal ping pong. It takes out the guesswork
> and seen from a generic handshake perspective it may be more actionable
> without detailing why a key epoch was locked in.
>
> Mikkel
>
> ________________________________
> From: QUIC <quic-bounces@ietf.org> on behalf of Jana Iyengar
> <jri.ietf@gmail.com>
> Sent: Wednesday, May 23, 2018 8:39:53 AM
> To: Kazuho Oku
> Cc: Eric Rescorla; IETF QUIC WG; Ian Swett
> Subject: Re: Stream0 Design Team Proposal
>
> Thank you for your implementation and your report -- this is terrific and
> helpful!
>
> On your note about CRYPTO_HS frames, I think your idea is clever. Just to
> ensure that I am understanding it correctly, I believe you're proposing
> defining:
> 0x10 - 0x17: STREAM frame
> 0x18 - 0x1F: CRYPTO_HS frame
>
> We can the same frame format for CRYPTO_HS as STREAM except that CRYPTO_H=
S
> will not have the stream ID field. This means an implementation handling
> these frames can reuse the stream machinery with a small change to parse =
the
> header bits as follows:
>
> if (type & 0x10)  {  // STREAM or CRYPTO_HS frame
>     if (type & 0x08) streamID =3D varint_consume(frame);
>     if (type & 0x04) offset =3D varint_consume(frame);
>     if (type & 0x02) length =3D varint_consume(frame);
>     if (type & 0x01) fin =3D 1;
>     read body if present
> }
>
> On Tue, May 22, 2018 at 9:57 PM, Kazuho Oku <kazuhooku@gmail.com> wrote:
>>
>> FWIW, I am happy to tell you that I have a working PoC code for the
>> proposed approach.
>>
>> On the QUIC side, I saw 2% (124 lines) increase in code size (more on
>> that below). On the TLS side, I also saw 2% (175 lines) increase.
>> However please look at the code size change especially on the QUIC
>> side with grain of salt, as it is just a PoC.
>>
>> As expected, the key and encryption-level management on the QUIC side
>> became very clean. Following are some of the design decisions I made
>> as well as the outcomes:
>>
>> * All the interaction between picotls and quicly are accompanied by
>> "epoch". Handshake messages are attributed with their epochs so that
>> they do not get protected by the wrong key, or so that octets received
>> under an incorrect encryption context cannot be misused.
>>
>> * All the traffic keys are governed by quicly (managing some traffic
>> keys in TLS while managing PNE key in QUIC seems messy).
>>
>> * The Initial key is setup by quicly, wheeras other traffic keys are
>> installed by picotls by calling a callback named
>> update_traffic_key_cb. The callback accepts and installs 6 keys in
>> total: for three levels (i.e. 0-RTT, handshake, 1-RTT) in two
>> directions (send-side and receive-side).
>>
>> * Three PN spaces have their own AEAD encryption key. Initial PN and
>> Handshake PN spaces have one aead decryption key each. Application PN
>> space has up to two decryption keys: either for 0-RTT and 1-RTT or for
>> two 1-RTT keys during key update.
>>
>> It was a pain to have a dedicated frame encoding for CRYPTO_HS, even
>> though we can reuse (and I reused) the retransmission and reassembly
>> logic of QUIC streams for the handshake flows. About a half of the
>> code size increase comes from that (the other half comes from the
>> added abstraction for having two contexts for the handshake). I would
>> prefer reusing the STREAM frame encoding for the handshake data. We
>> could possibly use a different base offset (i.e. for CRYPTO_HS frames
>> we could use 0b00011XXX, whereas the STREAM frames use 0b00010XXX), as
>> well as omitting the Stream ID field.
>>
>> Overall, now that I have a PoC, I am more confident that the proposed
>> approach is the correct path forward. It *simplifies* the QUIC stack
>> at the same time giving us better security properties as well as
>> fixing various issues in the current design (as discussed in the
>> design doc).
>>
>>
>> 2018-05-23 10:30 GMT+09:00 Ian Swett
>> <ianswett=3D40google.com@dmarc.ietf.org>:
>> > Dear QUIC WG,
>> >
>> >
>> > On behalf of the Stream 0 Design Team, I am pleased to report that we
>> > have
>> > consensus on a proposed approach to share with the WG. The DT's propos=
al
>> > will make QUIC and TLS work closer together and incorporates ideas fro=
m
>> > DTLS, but it does not use the DTLS protocol itself.
>> >
>> >
>> > The DT believes this solves the important open Stream 0 issues. The
>> > proposal
>> > will be a bit more invasive in TLS, but we believe it is the right
>> > long-term
>> > direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and Mint) a=
re
>> > willing and able to do the work necessary.. A number of stacks are
>> > currently
>> > working on implementations of this new approach, which we hope to have
>> > in
>> > time for the Interim meeting.
>> >
>> >
>> > A design document describing the overall approach can be found at:
>> >
>> >
>> > https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT=
93j6SwHY8/edit
>> >
>> >
>> > A PR making the changes to the QUIC documents can be found at:
>> >
>> > https://github.com/quicwg/base-drafts/pull/1377
>> >
>> >
>> > A few design details did not have clear consensus, but it was felt it
>> > would
>> > be better to discuss those in the wider WG than delay the design team.
>> > A
>> > consistent choice was made in the PR and these issues are mentioned in
>> > Appendix B of the design doc.
>> >
>> >
>> > As always, comments and questions welcome. That said, this is a big PR
>> > and
>> > we recognize that some editorial work is going to be needed before
>> > merging.
>> > In the interest of letting people follow along, and to keep github fro=
m
>> > falling over, we ask people to keep discussion on the mailing list and
>> > refrain from making PR comments.
>> >
>> >
>> > See you in Kista!
>> >
>> >
>> > Ian and Eric
>>
>>
>>
>> --
>> Kazuho Oku
>>
>



--=20
Kazuho Oku


From nobody Wed May 23 02:14:09 2018
Return-Path: <kazuhooku@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C714126B6E for <quic@ietfa.amsl.com>; Wed, 23 May 2018 02:14:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 awZ9PPY8SupJ for <quic@ietfa.amsl.com>; Wed, 23 May 2018 02:13:54 -0700 (PDT)
Received: from mail-pl0-x229.google.com (mail-pl0-x229.google.com [IPv6:2607:f8b0:400e:c01::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0FE21124BAC for <quic@ietf.org>; Wed, 23 May 2018 02:13:54 -0700 (PDT)
Received: by mail-pl0-x229.google.com with SMTP id c41-v6so12638000plj.10 for <quic@ietf.org>; Wed, 23 May 2018 02:13:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=IZznODxbyoNMufn2ydRfjLwI/1YqcIPLHvRS0ghCxYY=; b=DBRHvno0GFswoC2qgGDvExPNqMuj7eIhl2E5NEBDZK9kIkh/5IrV2D5V0mxdqgxnJ0 sEEK9GW9qg+KFIReCyyporB+r/vc+/OO1SiNnh2SjTlDK5pY8+5NE2p9VCb0y55Te0lL d4DBVZiZGmK5s93mCSlQhJkLp+R2uCHJPuzEhFAQjv3M75WsODGYJyKrjUlCg72d51ki dvCvnOTMaP7ZRrYnQYjlwBIYULNyWjnzQMh3vBGYo2VEHqOGqtU888V03iItjG47H/ao ZyuiuSso9YZmXN0cx58QpLB4aA58Ule2H5biX9thz45YGVCPc9Lbk7JZ6mGbLMu5r8Mf b1WA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=IZznODxbyoNMufn2ydRfjLwI/1YqcIPLHvRS0ghCxYY=; b=VLLgaHh0atLqgKm6xIQGfUfqv86JEoibY5CblrXLKj4xM9ZDuDWuel8RATZggSyuib 57/Panp69WUTk9dL0RH+FpO6hgznUQBZdHIH4OHekvVEabAe4yjp5oD6DgrxyPxgJQd7 /Nn12amtxw6iu9ZEOgrzi91iNqxo0QQ/m0HhN4bZCru6d80t/fFv+5ZzMQd/eVb1hLOa LxTUnNrYsOfP/DkjN9C4HFJYXfZGPAesfNdC47reHcAhvVQyOX+Gmj3u5Kv7Nj0s8iMi tlWwKbhtj7Mz0RqJnAXRKmKEXnLYEpyA/NCVAIdzFxGt9zijPAViLQaQ8wPOLn/JYf1I XfOA==
X-Gm-Message-State: ALKqPwfwXizNlVx2xfYGLYza7FfoX++Cx6ug1DAgovRC0SxNp94DTIWi ByOkiTCi0PM3UzU/a6CYxj/7/PKP9zCA3b9Yg3PRBQ==
X-Google-Smtp-Source: AB8JxZoWaFrpq447NDgRAb5fcPAUQU6EUrAxKQ+wJSKbRdZNNaCQOV3s8eRegn71+i4bAHxzP8B8YFG0DDPTrbhmwYw=
X-Received: by 2002:a17:902:343:: with SMTP id 61-v6mr2179560pld.39.1527066833403;  Wed, 23 May 2018 02:13:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:1189:0:0:0:0 with HTTP; Wed, 23 May 2018 02:13:52 -0700 (PDT)
In-Reply-To: <046ee03d-a675-86b6-ed3b-4fa69288c42d@huitema.net>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CABkgnnUB=jqwFzb2rjBHUFzOgu0hX0YUgaf5kW5ENNGKP+mGiA@mail.gmail.com> <MWHPR15MB1821F33BAB20815A38EB34A2B66B0@MWHPR15MB1821.namprd15.prod.outlook.com> <046ee03d-a675-86b6-ed3b-4fa69288c42d@huitema.net>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Wed, 23 May 2018 18:13:52 +0900
Message-ID: <CANatvzzn1VuAY2+cc8vpo75N3T=VH7YkSTjRC6uB4HATAFfW4Q@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: Christian Huitema <huitema@huitema.net>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/67yjfn17CrDJAv2EAZSLlAyQy8M>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 09:14:08 -0000

2018-05-23 14:29 GMT+09:00 Christian Huitema <huitema@huitema.net>:
> I like the proposal. In particular, I really like the encryption of
> handshake packets with the handshake key, as it does close a number of
> avenues for attacks. And I like that it solves the "ack promotion" issue
> that I was complaining against for some time. Turns out that in the curre=
nt
> draft, it is very hard to contain that problem if you enable client auth.
>
>
> On the other hand, I agree with Martin that a lot of the additions to
> transmission recovery should be moved to separate PRs. I am not enthusias=
tic
> with the EMPTY ACK mechanism, or with the proposed "implicit
> acknowledgement" of a lower crypto stream by a higher level ack.

At the moment I do not have a strong opinion on the Empty ACK mechanism.

However, regarding how we close the Initial and Handshake contexts, my
preference goes to using implicit ACKs (i.e. use the successful
receipt of a packet that is protected under a higher level of
encryption key as the signal) rather than explicitly ACKing the last
flight of data.

As I see, there are two downsides in the Explicit ACKing approach.

* Explicit ACKing requires sending two additional packets during the
handshake, which means that we would have more AES operations plus
somewhere around 60 bytes of overhead on the wire.
* Explicit ACKing requires more signaling from the TLS stack. In case
of implicit ACKing, the TLS stack need to only provide the AEAD
contexts and the messages, whereas in case of explicit ACKing, the TLS
stack also needs to provide a signal indicating the end of the
transmission at each encryption level.

The downside of the implicit ACKing approach is that the server needs
to signal the termination of the Handshake context using a special
frame sent using a 1-RTT packet.

But even taking that into consideration, I think that implicit ACKing
is still easier to implement, considering the need for the additional
signal in the explicit ACK case that have been described above.


> In any
> case, starting as simple as possible would help having the first
> implementations and tests.
>
>
> On 5/22/2018 8:26 PM, Subodh Iyengar wrote:
>
> As an implementor of fizz, I support this design and am willing to implem=
ent
> this as well.
>
>
> While this is a change in the API that TLS classically exposes, I think t=
his
> is the right tradeoff because it helps make things way more explicit whic=
h
> will prevent several other bugs from happening in the future.
>
>
> Subodh
>
> ________________________________
> From: QUIC <quic-bounces@ietf.org> on behalf of Martin Thomson
> <martin.thomson@gmail.com>
> Sent: Tuesday, May 22, 2018 8:00:40 PM
> To: Ian Swett
> Cc: ekr@mozilla.com; QUIC WG
> Subject: Re: Stream0 Design Team Proposal
>
> First of all, thanks to the design team for the work they have done.  I
> haven't digested everything yet, but I think that I have a good sense of
> the shape of the proposal.
>
> Overall, this looks like a workable design.  It's a lot more invasive of
> the cryptographic handshake implementation than I had thought people were
> willing to stomach originally.  But it's clear that we've run into proble=
ms
> with the current, more abstract API and this is a fairly natural way to
> split TLS.  I've spent a little time thinking about how this might be
> implemented and I think that it's not going to be *too* painful.  The pro=
of
> will be in the pudding there though.
>
> In looking at the PR, I really appreciate seeing all the changes together=
.
> BTW, the link above points to the wrong PR, so be careful (it appears to
> have the same content, but that's not guaranteed).  The actual PR is here=
:
> https://github.com/quicwg/base-drafts/pull/1377
>
> I've pushed a branch to the main repo so that you can preview the entire
> document set:
> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__quicwg.github.io_b=
ase-2Ddrafts_stream0_&d=3DDwIBaQ&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3Dh3Ju9EBS7mH=
twg-wAyN7fQ&m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&s=3DususmtxI3BT=
aLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&e=3D
>
> It seems like there are some core changes here and a bunch of separable o=
r
> at least secondary changes.  I'm sure that each one has its own
> justification, but that isn't always clear. The following changes seem li=
ke
> they are separable:
>
> * The use of separate packet number spaces
> * The Retry packet changes (and NEW_TOKEN)
> * EMPTY_ACK
> * The TLS extension for flow control
>
> Right now, some of these appear to be entirely gratuitous.  I'd like to g=
et
> to the bottom of each before we continue.
>
> At a minimum, the PR we land first should include just the core changes.
> As you say, reviewing a monster PR like this will only make GitHub weep
> unicorns, but we might be able to cut this into smaller pieces.
>
> On Wed, May 23, 2018 at 11:31 AM Ian Swett <ianswett=3D
> 40google.com@dmarc.ietf.org> wrote:
>
>> Dear QUIC WG,
>
>
>> On behalf of the Stream 0 Design Team, I am pleased to report that we
> have consensus on a proposed approach to share with the WG. The DT's
> proposal will make QUIC and TLS work closer together and incorporates ide=
as
> from DTLS, but it does not use the DTLS protocol itself.
>
>
>> The DT believes this solves the important open Stream 0 issues. The
> proposal will be a bit more invasive in TLS, but we believe it is the rig=
ht
> long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and
> Mint) are willing and able to do the work necessary.. A number of stacks
> are currently working on implementations of this new approach, which we
> hope to have in time for the Interim meeting.
>
>
>> A design document describing the overall approach can be found at:
>
>
> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__docs.google.com_do=
cument_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8_edit&d=3DDwIBaQ&c=
=3D5VD0RTtNlTh3ycd41b3MUw&r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&m=3D_vGK3zTKFrMOkFihJn=
PntLYw1T0_NEMiHYSM0Q_u1JA&s=3DjDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg&e=
=3D
>
>
>> A PR making the changes to the QUIC documents can be found at:
>
>> https://github.com/quicwg/base-drafts/pull/1377
>
>
>> A few design details did not have clear consensus, but it was felt it
> would be better to discuss those in the wider WG than delay the design
> team.  A consistent choice was made in the PR and these issues are
> mentioned in Appendix B of the design doc.
>
>
>> As always, comments and questions welcome. That said, this is a big PR
> and we recognize that some editorial work is going to be needed before
> merging. In the interest of letting people follow along, and to keep gith=
ub
> from falling over, we ask people to keep discussion on the mailing list a=
nd
> refrain from making PR comments.
>
>
>> See you in Kista!
>
>
>> Ian and Eric
>
>



--=20
Kazuho Oku


From nobody Wed May 23 02:40:31 2018
Return-Path: <Lucas.Pardue@bbc.co.uk>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8BBBE12DA1A for <quic@ietfa.amsl.com>; Wed, 23 May 2018 02:40:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
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 dZgJoywfqYOr for <quic@ietfa.amsl.com>; Wed, 23 May 2018 02:40:29 -0700 (PDT)
Received: from mailout1.cwwtf.bbc.co.uk (mailout1.cwwtf.bbc.co.uk [132.185.160.180]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E069A126C83 for <quic@ietf.org>; Wed, 23 May 2018 02:40:28 -0700 (PDT)
Received: from BGB01XI1003.national.core.bbc.co.uk ([10.184.50.53]) by mailout1.cwwtf.bbc.co.uk (8.15.2/8.15.2) with ESMTP id w4N9eO7I022277; Wed, 23 May 2018 10:40:24 +0100 (BST)
Received: from BGB01XUD1012.national.core.bbc.co.uk ([10.161.14.10]) by BGB01XI1003.national.core.bbc.co.uk ([10.184.50.53]) with mapi id 14.03.0361.001; Wed, 23 May 2018 10:40:21 +0100
From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
To: Martin Thomson <martin.thomson@gmail.com>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
CC: "ekr@mozilla.com" <ekr@mozilla.com>, QUIC WG <quic@ietf.org>
Subject: RE: Stream0 Design Team Proposal
Thread-Topic: Stream0 Design Team Proposal
Thread-Index: AQHT8jXDF7auV92dOkK/EvW9Iv1WNaQ8j0cAgAB8lrA=
Date: Wed, 23 May 2018 09:40:20 +0000
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A3BB3F4D7@bgb01xud1012>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CABkgnnUB=jqwFzb2rjBHUFzOgu0hX0YUgaf5kW5ENNGKP+mGiA@mail.gmail.com>
In-Reply-To: <CABkgnnUB=jqwFzb2rjBHUFzOgu0hX0YUgaf5kW5ENNGKP+mGiA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.19.161.213]
x-exclaimer-md-config: 1cd3ac1c-62e5-43f2-8404-6b688271c769
x-tm-as-product-ver: SMEX-11.0.0.4255-8.200.1013-23860.006
x-tm-as-result: No--8.692800-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Snu6FNl-T3I2ziK8jFtXaKOI9g0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 09:40:30 -0000

SGkgTWFydGluLA0KDQo+SSd2ZSBwdXNoZWQgYSBicmFuY2ggdG8gdGhlIG1haW4gcmVwbyBzbyB0
aGF0IHlvdSBjYW4gcHJldmlldyB0aGUgZW50aXJlDQo+ZG9jdW1lbnQgc2V0OiBodHRwczovL3F1
aWN3Zy5naXRodWIuaW8vYmFzZS1kcmFmdHMvc3RyZWFtMC8NCg0KDQpUaGFua3MgYnV0IHBsZWFz
ZSBub3RlIHRoYXQgdGhlIGRpZmYgVVJMUyBvbiB0aGF0IHBhZ2UgYXJlIGJyb2tlbiwgdGhleSBk
b24ndCBwcm92aWRlIHRoZSBJRVRGIHRvb2xzIHdpdGggdGhlIGNvcnJlY3QgdmVyc2lvbiB0byBk
aWZmLCB3aGljaCBtYWtlcyBpdCBsb29rIGxpa2UgdGhlIHN0cmVhbSAwIGNoYW5nZXMgYXJlIG1p
bmltYWwuDQoNCkluIHRoZSBtZWFudGltZSwgaGVyZSBhcmUgY29ycmVjdCBVUkxzIHRoYXQgcGVv
cGxlIGNhbiB1c2UgdG8gdmlldyB0aGUgZGlmZnM6DQoNClRyYW5zcG9ydDogaHR0cHM6Ly90b29s
cy5pZXRmLm9yZy9yZmNkaWZmP3VybDE9aHR0cHM6Ly90b29scy5pZXRmLm9yZy9pZC9kcmFmdC1p
ZXRmLXF1aWMtdHJhbnNwb3J0LnR4dCZ1cmwyPWh0dHBzOi8vcXVpY3dnLmdpdGh1Yi5pby9iYXNl
LWRyYWZ0cy9zdHJlYW0wL2RyYWZ0LWlldGYtcXVpYy10cmFuc3BvcnQudHh0DQpUTFM6IGh0dHBz
Oi8vdG9vbHMuaWV0Zi5vcmcvcmZjZGlmZj91cmwxPWh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaWQv
ZHJhZnQtaWV0Zi1xdWljLXRscy50eHQmdXJsMj1odHRwczovL3F1aWN3Zy5naXRodWIuaW8vYmFz
ZS1kcmFmdHMvc3RyZWFtMC9kcmFmdC1pZXRmLXF1aWMtdGxzLnR4dA0KUmVjb3Zlcnk6IGh0dHBz
Oi8vdG9vbHMuaWV0Zi5vcmcvcmZjZGlmZj91cmwxPWh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaWQv
ZHJhZnQtaWV0Zi1xdWljLXJlY292ZXJ5LnR4dCZ1cmwyPWh0dHBzOi8vcXVpY3dnLmdpdGh1Yi5p
by9iYXNlLWRyYWZ0cy9zdHJlYW0wL2RyYWZ0LWlldGYtcXVpYy1yZWNvdmVyeS50eHQNCkhUVFA6
IGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvcmZjZGlmZj91cmwxPWh0dHBzOi8vdG9vbHMuaWV0Zi5v
cmcvaWQvZHJhZnQtaWV0Zi1xdWljLWh0dHAudHh0JnVybDI9aHR0cHM6Ly9xdWljd2cuZ2l0aHVi
LmlvL2Jhc2UtZHJhZnRzL3N0cmVhbTAvZHJhZnQtaWV0Zi1xdWljLWh0dHAudHh0DQoNClJlZ2Fy
ZHMNCkx1Y2FzDQoNCg0KLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCmh0dHA6Ly93d3cu
YmJjLmNvLnVrDQpUaGlzIGUtbWFpbCAoYW5kIGFueSBhdHRhY2htZW50cykgaXMgY29uZmlkZW50
aWFsIGFuZA0KbWF5IGNvbnRhaW4gcGVyc29uYWwgdmlld3Mgd2hpY2ggYXJlIG5vdCB0aGUgdmll
d3Mgb2YgdGhlIEJCQyB1bmxlc3Mgc3BlY2lmaWNhbGx5IHN0YXRlZC4NCklmIHlvdSBoYXZlIHJl
Y2VpdmVkIGl0IGluDQplcnJvciwgcGxlYXNlIGRlbGV0ZSBpdCBmcm9tIHlvdXIgc3lzdGVtLg0K
RG8gbm90IHVzZSwgY29weSBvciBkaXNjbG9zZSB0aGUNCmluZm9ybWF0aW9uIGluIGFueSB3YXkg
bm9yIGFjdCBpbiByZWxpYW5jZSBvbiBpdCBhbmQgbm90aWZ5IHRoZSBzZW5kZXINCmltbWVkaWF0
ZWx5Lg0KUGxlYXNlIG5vdGUgdGhhdCB0aGUgQkJDIG1vbml0b3JzIGUtbWFpbHMNCnNlbnQgb3Ig
cmVjZWl2ZWQuDQpGdXJ0aGVyIGNvbW11bmljYXRpb24gd2lsbCBzaWduaWZ5IHlvdXIgY29uc2Vu
dCB0bw0KdGhpcy4NCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQo=


From nobody Wed May 23 11:46:17 2018
Return-Path: <jri.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1DD48129C56 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 11:46:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 NHoQyJ3O0FtH for <quic@ietfa.amsl.com>; Wed, 23 May 2018 11:46:12 -0700 (PDT)
Received: from mail-io0-x234.google.com (mail-io0-x234.google.com [IPv6:2607:f8b0:4001:c06::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 91508128959 for <quic@ietf.org>; Wed, 23 May 2018 11:46:12 -0700 (PDT)
Received: by mail-io0-x234.google.com with SMTP id z4-v6so24010870iof.5 for <quic@ietf.org>; Wed, 23 May 2018 11:46:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=GoyCUCNSFQx6Z/KuX8TFaJwCAqil/oW6zoLTvtTVhhM=; b=Cn4FqbMRyFqRCuRBKcCGH3oy5vEdd2YIG7UgfwdMjcN/egx7Q6Ove+c1wiNvotc6hd ZOaqFNLKSmH68iZn8FKMP41TNZnRF11zJkEJj0V0oHlfAyx1H0joYLV1lcfMVLbn0q6W 9vgtresVajU3uFeSQ745Y88o8zwrixU/R6w0jKtQAc6VsZKZv8v5HRRfER/c88xdw5oL YRAFM2PxnoCmHatlJ6mxkbPwAptCG18z+6aq3SKL5CIHipUfGkWfG9nJ75dEQrL9wZKt iT1Azfk8RLs3+UfF5xv2yGX9kSfLHOnKURDXdKZYSLp3gMiAq9QK2RG9p2YApybXhmyb +b+g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=GoyCUCNSFQx6Z/KuX8TFaJwCAqil/oW6zoLTvtTVhhM=; b=Ua8sj79kI+h82DWo6Hp7nkrWcJGCG7QBgtAHG4kXYSF8mQY9pz3Plshu+5dru/HzjT IcDBF7yC1oZHL3l6TnHyB+Pwh7Gh49BUE2G0fgrUp3U6Nz1iBXs75FBRx2MVYL0eljAX TymCPOBmNQ+S2/EGqH2juT07fsVK+eV5CC2sCrOVtjuH73mVvUfbhaLYT6LucGFxLafN 8XbKbhx9g3CND0NFJNXFQaN18kXPymvCLDKqj3tDiNgcCcc4tJ7WbT2Ouwi4Ju5N2Ubt DEPnwY7r1B2kxlUvygdVUxtBdkVwkbDLuwJd9BPySud4Epk7bxv3C+hUJ3RPgcxIoKvb vICg==
X-Gm-Message-State: ALKqPwdF1YnR+WW4ze5oh/+IbOJAsHiLb9vk5jzsI+99sw9LwL4VxJ6c 3vuaRevEstAWwteuih+WDuEmB1NsPYVLCsOkpOk=
X-Google-Smtp-Source: AB8JxZoK5nlvSOYZoHOwKI+COA0uarAFYq4/lKOXp7q7Un99iUaW373bdkc0u0CbniSIUe67xda/mws6UtOXgaVOwII=
X-Received: by 2002:a6b:c083:: with SMTP id q125-v6mr3619249iof.42.1527101171654;  Wed, 23 May 2018 11:46:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:27d4:0:0:0:0:0 with HTTP; Wed, 23 May 2018 11:46:11 -0700 (PDT)
In-Reply-To: <CANatvzwC9ueFVjgg_hPsNkz1Wu4qYjKiWhzyj+UVnSby177Ehg@mail.gmail.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CANatvzzS+T4HcddCemKF7bb1BmACFp=R4n+YMWkq7tnZaUXw4w@mail.gmail.com> <CACpbDcddWz_i5GoNWYfDAdWKcX0_gOMiKk=ORVABGPE8+7c8Vw@mail.gmail.com> <CANatvzwC9ueFVjgg_hPsNkz1Wu4qYjKiWhzyj+UVnSby177Ehg@mail.gmail.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Wed, 23 May 2018 11:46:11 -0700
Message-ID: <CACpbDcfPBot2k+JyU2x+vKG-9NizOGTHQHbTzLT6f76uAa2r8A@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: Kazuho Oku <kazuhooku@gmail.com>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Eric Rescorla <ekr@mozilla.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000df63d6056ce3f22c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/YVZeVAZMXgWFjF8zh1xTPCXJOc8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 18:46:16 -0000

--000000000000df63d6056ce3f22c
Content-Type: text/plain; charset="UTF-8"

>
> That's correct. Considering the fact that the handshake flows are
> never closed, we could do something like below to preserve some more,
> by swapping the bits used for offset and fin.
>
> 0x10-0x17: STREAM frame
> 0x18-0x1B: CRYPTO_HS frame
>
> if (0x10 <= type && type <= 0x1c) {
>     if (type <= 0x18) {
>         streamID = varint_consume(frame);
>         if (type & 0x04)
>             fin = 1;
>     }
>     if (type & 0x02)
>         length = varint_consume(frame);
>     if (type & 0x01)
>         offset = varint_consume(frame);
> }
>

That works as well. Though we'd have exhausted 1/8ths of the frame type
space, so I don't care much about saving bits here.

A thought occurs to me: a CRYPTO_HS frame with the fin bit set can be used
to indicate that the handshake is done.This could be used as a signal (aka
HANDSHAKE_DONE) to solve Marten's problem of a client rtxing a CFIN. Of
course, this would mean that this particular CRYPTO_HS frame would be
encrypted with a 1-RTT key... which *I think* is fine. What do you think?


> >
> > On Tue, May 22, 2018 at 9:57 PM, Kazuho Oku <kazuhooku@gmail.com> wrote:
> >>
> >> FWIW, I am happy to tell you that I have a working PoC code for the
> >> proposed approach.
> >>
> >> On the QUIC side, I saw 2% (124 lines) increase in code size (more on
> >> that below). On the TLS side, I also saw 2% (175 lines) increase.
> >> However please look at the code size change especially on the QUIC
> >> side with grain of salt, as it is just a PoC.
> >>
> >> As expected, the key and encryption-level management on the QUIC side
> >> became very clean. Following are some of the design decisions I made
> >> as well as the outcomes:
> >>
> >> * All the interaction between picotls and quicly are accompanied by
> >> "epoch". Handshake messages are attributed with their epochs so that
> >> they do not get protected by the wrong key, or so that octets received
> >> under an incorrect encryption context cannot be misused.
> >>
> >> * All the traffic keys are governed by quicly (managing some traffic
> >> keys in TLS while managing PNE key in QUIC seems messy).
> >>
> >> * The Initial key is setup by quicly, wheeras other traffic keys are
> >> installed by picotls by calling a callback named
> >> update_traffic_key_cb. The callback accepts and installs 6 keys in
> >> total: for three levels (i.e. 0-RTT, handshake, 1-RTT) in two
> >> directions (send-side and receive-side).
> >>
> >> * Three PN spaces have their own AEAD encryption key. Initial PN and
> >> Handshake PN spaces have one aead decryption key each. Application PN
> >> space has up to two decryption keys: either for 0-RTT and 1-RTT or for
> >> two 1-RTT keys during key update.
> >>
> >> It was a pain to have a dedicated frame encoding for CRYPTO_HS, even
> >> though we can reuse (and I reused) the retransmission and reassembly
> >> logic of QUIC streams for the handshake flows. About a half of the
> >> code size increase comes from that (the other half comes from the
> >> added abstraction for having two contexts for the handshake). I would
> >> prefer reusing the STREAM frame encoding for the handshake data. We
> >> could possibly use a different base offset (i.e. for CRYPTO_HS frames
> >> we could use 0b00011XXX, whereas the STREAM frames use 0b00010XXX), as
> >> well as omitting the Stream ID field.
> >>
> >> Overall, now that I have a PoC, I am more confident that the proposed
> >> approach is the correct path forward. It *simplifies* the QUIC stack
> >> at the same time giving us better security properties as well as
> >> fixing various issues in the current design (as discussed in the
> >> design doc).
> >>
> >>
> >> 2018-05-23 10:30 GMT+09:00 Ian Swett
> >> <ianswett=40google.com@dmarc.ietf.org>:
> >> > Dear QUIC WG,
> >> >
> >> >
> >> > On behalf of the Stream 0 Design Team, I am pleased to report that we
> >> > have
> >> > consensus on a proposed approach to share with the WG. The DT's
> proposal
> >> > will make QUIC and TLS work closer together and incorporates ideas
> from
> >> > DTLS, but it does not use the DTLS protocol itself.
> >> >
> >> >
> >> > The DT believes this solves the important open Stream 0 issues. The
> >> > proposal
> >> > will be a bit more invasive in TLS, but we believe it is the right
> >> > long-term
> >> > direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and Mint)
> are
> >> > willing and able to do the work necessary.. A number of stacks are
> >> > currently
> >> > working on implementations of this new approach, which we hope to have
> >> > in
> >> > time for the Interim meeting.
> >> >
> >> >
> >> > A design document describing the overall approach can be found at:
> >> >
> >> >
> >> > https://docs.google.com/document/d/1fRsJqPinJl8N3b-
> bflDRV6auojfJLkxddT93j6SwHY8/edit
> >> >
> >> >
> >> > A PR making the changes to the QUIC documents can be found at:
> >> >
> >> > https://github.com/quicwg/base-drafts/pull/1377
> >> >
> >> >
> >> > A few design details did not have clear consensus, but it was felt it
> >> > would
> >> > be better to discuss those in the wider WG than delay the design team.
> >> > A
> >> > consistent choice was made in the PR and these issues are mentioned in
> >> > Appendix B of the design doc.
> >> >
> >> >
> >> > As always, comments and questions welcome. That said, this is a big PR
> >> > and
> >> > we recognize that some editorial work is going to be needed before
> >> > merging.
> >> > In the interest of letting people follow along, and to keep github
> from
> >> > falling over, we ask people to keep discussion on the mailing list and
> >> > refrain from making PR comments.
> >> >
> >> >
> >> > See you in Kista!
> >> >
> >> >
> >> > Ian and Eric
> >>
> >>
> >>
> >> --
> >> Kazuho Oku
> >>
> >
>
>
>
> --
> Kazuho Oku
>

--000000000000df63d6056ce3f22c
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">That&#39;s correct. Considering the fact that th=
e handshake flows are<br>
never closed, we could do something like below to preserve some more,<br>
by swapping the bits used for offset and fin.<br>
<br>
0x10-0x17: STREAM frame<br>
0x18-0x1B: CRYPTO_HS frame<br>
<br>
if (0x10 &lt;=3D type &amp;&amp; type &lt;=3D 0x1c) {<br>
=C2=A0 =C2=A0 if (type &lt;=3D 0x18) {<br>
<span class=3D"">=C2=A0 =C2=A0 =C2=A0 =C2=A0 streamID =3D varint_consume(fr=
ame);<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 if (type &amp; 0x04)<br>
</span>=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 fin =3D 1;<br>
<span class=3D"">=C2=A0 =C2=A0 }<br>
=C2=A0 =C2=A0 if (type &amp; 0x02)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 length =3D varint_consume(frame);<br>
=C2=A0 =C2=A0 if (type &amp; 0x01)<br>
</span>=C2=A0 =C2=A0 =C2=A0 =C2=A0 offset =3D varint_consume(frame);<br>
<div class=3D"HOEnZb"><div class=3D"h5">}<br></div></div></blockquote><div>=
<br></div><div>That works as well. Though we&#39;d have exhausted 1/8ths of=
 the frame type space, so I don&#39;t care much about saving bits here.</di=
v><div><br></div><div>A thought occurs to me: a CRYPTO_HS frame with the fi=
n bit set can be used to indicate that the handshake is done.This could be =
used as a signal (aka HANDSHAKE_DONE) to solve Marten&#39;s problem of a cl=
ient rtxing a CFIN. Of course, this would mean that this particular CRYPTO_=
HS frame would be encrypted with a 1-RTT key... which *I think* is fine. Wh=
at do you think?</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div =
class=3D"HOEnZb"><div class=3D"h5">
&gt;<br>
&gt; On Tue, May 22, 2018 at 9:57 PM, Kazuho Oku &lt;<a href=3D"mailto:kazu=
hooku@gmail.com">kazuhooku@gmail.com</a>&gt; wrote:<br>
&gt;&gt;<br>
&gt;&gt; FWIW, I am happy to tell you that I have a working PoC code for th=
e<br>
&gt;&gt; proposed approach.<br>
&gt;&gt;<br>
&gt;&gt; On the QUIC side, I saw 2% (124 lines) increase in code size (more=
 on<br>
&gt;&gt; that below). On the TLS side, I also saw 2% (175 lines) increase.<=
br>
&gt;&gt; However please look at the code size change especially on the QUIC=
<br>
&gt;&gt; side with grain of salt, as it is just a PoC.<br>
&gt;&gt;<br>
&gt;&gt; As expected, the key and encryption-level management on the QUIC s=
ide<br>
&gt;&gt; became very clean. Following are some of the design decisions I ma=
de<br>
&gt;&gt; as well as the outcomes:<br>
&gt;&gt;<br>
&gt;&gt; * All the interaction between picotls and quicly are accompanied b=
y<br>
&gt;&gt; &quot;epoch&quot;. Handshake messages are attributed with their ep=
ochs so that<br>
&gt;&gt; they do not get protected by the wrong key, or so that octets rece=
ived<br>
&gt;&gt; under an incorrect encryption context cannot be misused.<br>
&gt;&gt;<br>
&gt;&gt; * All the traffic keys are governed by quicly (managing some traff=
ic<br>
&gt;&gt; keys in TLS while managing PNE key in QUIC seems messy).<br>
&gt;&gt;<br>
&gt;&gt; * The Initial key is setup by quicly, wheeras other traffic keys a=
re<br>
&gt;&gt; installed by picotls by calling a callback named<br>
&gt;&gt; update_traffic_key_cb. The callback accepts and installs 6 keys in=
<br>
&gt;&gt; total: for three levels (i.e. 0-RTT, handshake, 1-RTT) in two<br>
&gt;&gt; directions (send-side and receive-side).<br>
&gt;&gt;<br>
&gt;&gt; * Three PN spaces have their own AEAD encryption key. Initial PN a=
nd<br>
&gt;&gt; Handshake PN spaces have one aead decryption key each. Application=
 PN<br>
&gt;&gt; space has up to two decryption keys: either for 0-RTT and 1-RTT or=
 for<br>
&gt;&gt; two 1-RTT keys during key update.<br>
&gt;&gt;<br>
&gt;&gt; It was a pain to have a dedicated frame encoding for CRYPTO_HS, ev=
en<br>
&gt;&gt; though we can reuse (and I reused) the retransmission and reassemb=
ly<br>
&gt;&gt; logic of QUIC streams for the handshake flows. About a half of the=
<br>
&gt;&gt; code size increase comes from that (the other half comes from the<=
br>
&gt;&gt; added abstraction for having two contexts for the handshake). I wo=
uld<br>
&gt;&gt; prefer reusing the STREAM frame encoding for the handshake data. W=
e<br>
&gt;&gt; could possibly use a different base offset (i.e. for CRYPTO_HS fra=
mes<br>
&gt;&gt; we could use 0b00011XXX, whereas the STREAM frames use 0b00010XXX)=
, as<br>
&gt;&gt; well as omitting the Stream ID field.<br>
&gt;&gt;<br>
&gt;&gt; Overall, now that I have a PoC, I am more confident that the propo=
sed<br>
&gt;&gt; approach is the correct path forward. It *simplifies* the QUIC sta=
ck<br>
&gt;&gt; at the same time giving us better security properties as well as<b=
r>
&gt;&gt; fixing various issues in the current design (as discussed in the<b=
r>
&gt;&gt; design doc).<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; 2018-05-23 10:30 GMT+09:00 Ian Swett<br>
&gt;&gt; &lt;ianswett=3D<a href=3D"mailto:40google.com@dmarc.ietf.org">40go=
ogle.com@dmarc.<wbr>ietf.org</a>&gt;:<br>
&gt;&gt; &gt; Dear QUIC WG,<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; On behalf of the Stream 0 Design Team, I am pleased to report=
 that we<br>
&gt;&gt; &gt; have<br>
&gt;&gt; &gt; consensus on a proposed approach to share with the WG. The DT=
&#39;s proposal<br>
&gt;&gt; &gt; will make QUIC and TLS work closer together and incorporates =
ideas from<br>
&gt;&gt; &gt; DTLS, but it does not use the DTLS protocol itself.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; The DT believes this solves the important open Stream 0 issue=
s. The<br>
&gt;&gt; &gt; proposal<br>
&gt;&gt; &gt; will be a bit more invasive in TLS, but we believe it is the =
right<br>
&gt;&gt; &gt; long-term<br>
&gt;&gt; &gt; direction and several TLS stacks (BoringSSL, PicoTLS, NSS, an=
d Mint) are<br>
&gt;&gt; &gt; willing and able to do the work necessary.. A number of stack=
s are<br>
&gt;&gt; &gt; currently<br>
&gt;&gt; &gt; working on implementations of this new approach, which we hop=
e to have<br>
&gt;&gt; &gt; in<br>
&gt;&gt; &gt; time for the Interim meeting.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; A design document describing the overall approach can be foun=
d at:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; <a href=3D"https://docs.google.com/document/d/1fRsJqPinJl8N3b=
-bflDRV6auojfJLkxddT93j6SwHY8/edit" rel=3D"noreferrer" target=3D"_blank">ht=
tps://docs.google.com/<wbr>document/d/1fRsJqPinJl8N3b-<wbr>bflDRV6auojfJLkx=
ddT93j6SwHY8/<wbr>edit</a><br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; A PR making the changes to the QUIC documents can be found at=
:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; <a href=3D"https://github.com/quicwg/base-drafts/pull/1377" r=
el=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/<wbr>base-dra=
fts/pull/1377</a><br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; A few design details did not have clear consensus, but it was=
 felt it<br>
&gt;&gt; &gt; would<br>
&gt;&gt; &gt; be better to discuss those in the wider WG than delay the des=
ign team.<br>
&gt;&gt; &gt; A<br>
&gt;&gt; &gt; consistent choice was made in the PR and these issues are men=
tioned in<br>
&gt;&gt; &gt; Appendix B of the design doc.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; As always, comments and questions welcome. That said, this is=
 a big PR<br>
&gt;&gt; &gt; and<br>
&gt;&gt; &gt; we recognize that some editorial work is going to be needed b=
efore<br>
&gt;&gt; &gt; merging.<br>
&gt;&gt; &gt; In the interest of letting people follow along, and to keep g=
ithub from<br>
&gt;&gt; &gt; falling over, we ask people to keep discussion on the mailing=
 list and<br>
&gt;&gt; &gt; refrain from making PR comments.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; See you in Kista!<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Ian and Eric<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; --<br>
&gt;&gt; Kazuho Oku<br>
&gt;&gt;<br>
&gt;<br>
<br>
<br>
<br>
</div></div><span class=3D"HOEnZb"><font color=3D"#888888">-- <br>
Kazuho Oku<br>
</font></span></blockquote></div><br></div></div>

--000000000000df63d6056ce3f22c--


From nobody Wed May 23 12:43:35 2018
Return-Path: <ted.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E32D012AAB6 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 12:43:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.689
X-Spam-Level: 
X-Spam-Status: No, score=-2.689 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 IUK7JvBQVCLc for <quic@ietfa.amsl.com>; Wed, 23 May 2018 12:43:31 -0700 (PDT)
Received: from mail-oi0-x229.google.com (mail-oi0-x229.google.com [IPv6:2607:f8b0:4003:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0B3FD1277BB for <quic@ietf.org>; Wed, 23 May 2018 12:43:31 -0700 (PDT)
Received: by mail-oi0-x229.google.com with SMTP id b130-v6so20598150oif.12 for <quic@ietf.org>; Wed, 23 May 2018 12:43:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=RoKCJIWofmS7iqi5nr/nBhNlBRh+CuI7L+K37O9JjHU=; b=tILdCxeQgoXHZ9FHii/mSppU8828ACj6T6SYCWVGGAG9E0OCW/AQuVD+gjGqXOjZ8x 8JERoZCEYeGJ0BWNPCwhVau7qEQevx5O0KgIc0TeIv1ohelnw3hm6wC4Zvxa/5rggMKy HYdQx71QMDlzWhS/7yvNfjJKXDSXa2q0cknRlyY1g/o01/oEnLx0pAM3M2MkjlK/ObAg MDiDSsAMLlEI9HZAWvSPL9HP4R8dMcVR/VI/FGPd/3wozFMzd43jGpSai7/1E9ys6HKy yVgpqEFdotxXE4TQvlr741H9mci8U/wLcDXxGHrrD622cRL2PMYdKvUmotyw7oXmHjkb MjkA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=RoKCJIWofmS7iqi5nr/nBhNlBRh+CuI7L+K37O9JjHU=; b=hm277kFFLTPFK+6LZsGlyxnJ/0WhucmsZbepSngG+YnzDI5/ph2rWcj2cI89HFY+I/ /+x6TecepLi8qabyFqgIP0jhvVvfejyfpVaKvk8fq2fot+21sIFpH0aUSpArrLzwwSBw Z0+YuU/MIjHoJNae7M3hqz8JeCsZNhOwex0hir5jpGlppMEr/nIBmDKnC64p381a3YDZ Mm8CcAW/3OMs3QDQ6veY9MfoG7rx7PwEYj0dSVTpZe6h7Eh5SmIDc1gVEz6iN5KKICZN IX8cowzW795appQqPOs7ObN3VBPR+yK7j8hvmmHUAb8PEPhAV3tHCc0K0cWipQjHJtDE JaHQ==
X-Gm-Message-State: ALKqPwcWtGnnOl0J0yRZQOh3py8Ogh9YZcpeAf3zqCGxsTeI5ufN0+uo tdZ5wodX0jkqfxSBg5KyNnDgKNb93FHUMLcITko=
X-Google-Smtp-Source: AB8JxZpBT+0c+L3eI4aBcxYasvoqZ6JfzshYlxJvgKnEDcUXTO+D1HkE7P25RT5S5sSCINqRF9NEQTzA7c7p2AE/KS8=
X-Received: by 2002:aca:488d:: with SMTP id v135-v6mr846882oia.142.1527104610081;  Wed, 23 May 2018 12:43:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:4399:0:0:0:0:0 with HTTP; Wed, 23 May 2018 12:42:59 -0700 (PDT)
In-Reply-To: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 23 May 2018 12:42:59 -0700
Message-ID: <CA+9kkMC0a+HELyVvh+DtvkiorWmKkUQ346zt49Xfyd1zzZ780Q@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Cc: IETF QUIC WG <quic@ietf.org>, Eric Rescorla <ekr@mozilla.com>
Content-Type: multipart/alternative; boundary="000000000000d1a2b1056ce4bfb5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/xhIM81NIaRqME--g5R5SR2HHAx0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 19:43:34 -0000

--000000000000d1a2b1056ce4bfb5
Content-Type: text/plain; charset="UTF-8"

Howdy,

Thanks for sharing the document.  I have a couple of detailed comments, and
then some high level comments which I will put into a separate email.

First, the document says this:

Though proper analysis is needed, it is not likely that the removal of the
TLS record layer will cause a security concern, because the security
properties provided by QUIC packets are identical to what have been
provided by TLS records.


I'm not sure that this is actually the statement we need to analyze,
though. We need to be sure that the security properties of TLS records used
in TCP packets are available in QUIC streams in QUIC packets using UDP as a
multiplexing layer. There appear to be some difference in where the
facilities the overall system provides that may require more description.
As an example, I think the way padding works in this proposal needs more
description. If I understand correctly, each TLS record is encrypted
separately and the presence or absence of padding is indicated by a
padding_length byte present in each record. That means the padding is
related to the record, not the packet; by removing the record layer and
using QUIC frames, though, we seem to have a different padding structure.
QUIC uses padding frames, not padding within other frame types which is
both conceptually and practically different. Similarly, I'd be interested
in more text on the interaction with precedence, since the loss of the
record layer means that the former guarantee that the record layer makes
records available in the order in which they were protected now seems to be
unavailable.


Secondly, I think the advantages of the different number spaces would be
present in many different designs, and I would a prefer that a proposal for
that be decoupled from the other pieces of this. At least to my
understanding, the attacks it mitigates are unrelated to the other stream 0
issues that this addresses.


regards,


Ted





On Tue, May 22, 2018 at 6:30 PM, Ian Swett <
ianswett=40google.com@dmarc.ietf.org> wrote:

>
>
>
>
>
>
>
> *Dear QUIC WG,On behalf of the Stream 0 Design Team, I am pleased to
> report that we have consensus on a proposed approach to share with the WG.
> The DT's proposal will make QUIC and TLS work closer together and
> incorporates ideas from DTLS, but it does not use the DTLS protocol itself.
> The DT believes this solves the important open Stream 0 issues. The
> proposal will be a bit more invasive in TLS, but we believe it is the right
> long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and
> Mint) are willing and able to do the work necessary.. A number of stacks
> are currently working on implementations of this new approach, which we
> hope to have in time for the Interim meeting.A design document describing
> the overall approach can be found
> at:https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit
> <https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit>A
> PR making the changes to the QUIC documents can be found
> at:https://github.com/quicwg/base-drafts/pull/1377
> <https://github.com/ekr/base-drafts/pull/29>A few design details did not
> have clear consensus, but it was felt it would be better to discuss those
> in the wider WG than delay the design team.  A consistent choice was made
> in the PR and these issues are mentioned in Appendix B of the design doc.As
> always, comments and questions welcome. That said, this is a big PR and we
> recognize that some editorial work is going to be needed before merging. In
> the interest of letting people follow along, and to keep github from
> falling over, we ask people to keep discussion on the mailing list and
> refrain from making PR comments.See you in Kista!*
> Ian and Eric
>

--000000000000d1a2b1056ce4bfb5
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>Howdy,</div><div><br></div><div>Thanks for sharing th=
e document.=C2=A0 I have a couple of detailed comments, and then some high =
level comments which I will put into a separate email.</div><div><br></div>=
<div>First, the document says this:</div><div><br></div><div><p style=3D"li=
ne-height:1.38;margin-top:0pt;margin-bottom:0pt;text-align:justify;margin-l=
eft:40px" id=3D"gmail-docs-internal-guid-ae9978f1-8e74-9194-2b6b-f4000bc3b5=
41"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);backgr=
ound-color:transparent;font-weight:400;font-style:normal;font-variant:norma=
l;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Though=
 proper analysis is needed, it is not likely that the removal of the TLS re=
cord layer will cause a security concern, because the security properties p=
rovided by QUIC packets are identical to what have been provided by TLS rec=
ords.</span></p><p style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0=
pt;text-align:justify"><span style=3D"font-size:11pt;font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal=
;font-variant:normal;text-decoration:none;vertical-align:baseline;white-spa=
ce:pre-wrap"><br></span></p><p style=3D"line-height:1.38;margin-top:0pt;mar=
gin-bottom:0pt;text-align:justify"><span style=3D"font-size:11pt;font-famil=
y:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-=
style:normal;font-variant:normal;text-decoration:none;vertical-align:baseli=
ne;white-space:pre-wrap">I&#39;m not sure that this is actually the stateme=
nt we need to analyze, though.  We need to be sure that the security proper=
ties of TLS records used in TCP packets are available in QUIC streams in QU=
IC packets using UDP as a multiplexing layer.  There appear to be some diff=
erence in where the facilities the overall system provides that may require=
 more description.  As an example, I think the way padding works in this pr=
oposal needs more description.  If I understand correctly, each TLS record =
is encrypted separately and the presence or absence of padding is indicated=
 by a padding_length byte present in each record.  That means the padding i=
s related to the record, not the packet; by removing the record layer and u=
sing QUIC frames, though, we seem to have a different padding structure.  Q=
UIC uses padding frames, not padding within other frame types which is both=
 conceptually and practically different.  Similarly, I&#39;d be interested =
in more text on the interaction with precedence, since the loss of the reco=
rd layer means that the former guarantee that the record layer makes record=
s available in the order in which they were protected now seems to be unava=
ilable.<br></span></p><p style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt;text-align:justify"><span style=3D"font-size:11pt;font-family:Aria=
l;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:=
normal;font-variant:normal;text-decoration:none;vertical-align:baseline;whi=
te-space:pre-wrap"><br></span></p><p style=3D"line-height:1.38;margin-top:0=
pt;margin-bottom:0pt;text-align:justify"><span style=3D"font-size:11pt;font=
-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400=
;font-style:normal;font-variant:normal;text-decoration:none;vertical-align:=
baseline;white-space:pre-wrap">Secondly, I think the advantages of the diff=
erent number spaces would be present in many different designs, and I would=
 a prefer that a proposal for that be decoupled from the other pieces of th=
is.  At least to my understanding, the attacks it mitigates are unrelated t=
o the other stream 0 issues that this addresses.</span></p><p style=3D"line=
-height:1.38;margin-top:0pt;margin-bottom:0pt;text-align:justify"><span sty=
le=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:tr=
ansparent;font-weight:400;font-style:normal;font-variant:normal;text-decora=
tion:none;vertical-align:baseline;white-space:pre-wrap"><br></span></p><p s=
tyle=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;text-align:justif=
y"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);backgro=
und-color:transparent;font-weight:400;font-style:normal;font-variant:normal=
;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">regards=
,</span></p><p style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;t=
ext-align:justify"><span style=3D"font-size:11pt;font-family:Arial;color:rg=
b(0,0,0);background-color:transparent;font-weight:400;font-style:normal;fon=
t-variant:normal;text-decoration:none;vertical-align:baseline;white-space:p=
re-wrap"><br></span></p><p style=3D"line-height:1.38;margin-top:0pt;margin-=
bottom:0pt;text-align:justify"><span style=3D"font-size:11pt;font-family:Ar=
ial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-styl=
e:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;w=
hite-space:pre-wrap">Ted<br></span></p><p style=3D"line-height:1.38;margin-=
top:0pt;margin-bottom:0pt;text-align:justify"><span style=3D"font-size:11pt=
;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weigh=
t:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-a=
lign:baseline;white-space:pre-wrap"></span></p><pre><br></pre><br><p></p><b=
r></div></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On =
Tue, May 22, 2018 at 6:30 PM, Ian Swett <span dir=3D"ltr">&lt;<a href=3D"ma=
ilto:ianswett=3D40google.com@dmarc.ietf.org" target=3D"_blank">ianswett=3D4=
0google.com@dmarc.ietf.org</a>&gt;</span> wrote:<br><blockquote class=3D"gm=
ail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-le=
ft:1ex"><div dir=3D"ltr"><b style=3D"font-weight:normal" id=3D"m_-185109161=
0820382769gmail-docs-internal-guid-2a62f340-8a8f-9073-5cad-25b8001e52b3"><p=
 dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><s=
pan style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-c=
olor:transparent;font-weight:400;font-style:normal;font-variant:normal;text=
-decoration:none;vertical-align:baseline;white-space:pre-wrap">Dear QUIC WG=
,</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;mar=
gin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0=
,0,0);background-color:transparent;font-weight:400;font-style:normal;font-v=
ariant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-=
wrap">On behalf of the Stream 0 Design Team, I am pleased to report that we=
 have consensus on a proposed approach to share with the WG. The DT&#39;s p=
roposal will make QUIC and TLS work closer together and incorporates ideas =
from DTLS, but it does not use the DTLS protocol itself. </span></p><br><p =
dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><sp=
an style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-co=
lor:transparent;font-weight:400;font-style:normal;font-variant:normal;text-=
decoration:none;vertical-align:baseline;white-space:pre-wrap">The DT believ=
es this solves the important open Stream 0 issues. The proposal will be a b=
it more invasive in TLS, but we believe it is the right long-term direction=
 and several TLS stacks (BoringSSL, PicoTLS, NSS, and Mint) are willing and=
 able to do the work necessary.. A number of stacks are currently working o=
n implementations of this new approach, which we hope to have in time for t=
he Interim meeting.</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;=
margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family=
:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-s=
tyle:normal;font-variant:normal;text-decoration:none;vertical-align:baselin=
e;white-space:pre-wrap">A design document describing the overall approach c=
an be found at:</span></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-t=
op:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;c=
olor:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:nor=
mal;font-variant:normal;text-decoration:none;vertical-align:baseline;white-=
space:pre-wrap"><a href=3D"https://docs.google.com/document/d/1fRsJqPinJl8N=
3b-bflDRV6auojfJLkxddT93j6SwHY8/edit" target=3D"_blank">https://docs.google=
.com/<wbr>document/d/1fRsJqPinJl8N3b-<wbr>bflDRV6auojfJLkxddT93j6SwHY8/<wbr=
>edit</a></span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top=
:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;col=
or:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:norma=
l;font-variant:normal;text-decoration:none;vertical-align:baseline;white-sp=
ace:pre-wrap">A PR making the changes to the QUIC documents can be found at=
:</span></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-=
bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0=
);background-color:transparent;font-weight:400;font-style:normal;font-varia=
nt:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap=
"><a href=3D"https://github.com/ekr/base-drafts/pull/29" target=3D"_blank">=
https://github.com/quicwg/<wbr>base-drafts/pull/1377</a></span></p><br><p d=
ir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><spa=
n style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-col=
or:transparent;font-weight:400;font-style:normal;font-variant:normal;text-d=
ecoration:none;vertical-align:baseline;white-space:pre-wrap">A few design d=
etails did not have clear consensus, but it was felt it would be better to =
discuss those in the wider WG than delay the design team.=C2=A0 A consisten=
t choice was made in the PR and these issues are mentioned in Appendix B of=
 the design doc.</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;mar=
gin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Ar=
ial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-styl=
e:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;w=
hite-space:pre-wrap">As always, comments and questions welcome. That said, =
this is a big PR and we recognize that some editorial work is going to be n=
eeded before merging. In the interest of letting people follow along, and t=
o keep github from falling over, we ask people to keep discussion on the ma=
iling list and refrain from making PR comments.</span></p><br><p dir=3D"ltr=
" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=
=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:tran=
sparent;font-weight:400;font-style:normal;font-variant:normal;text-decorati=
on:none;vertical-align:baseline;white-space:pre-wrap">See you in Kista!</sp=
an></p></b><br class=3D"m_-1851091610820382769gmail-Apple-interchange-newli=
ne">Ian and Eric</div>
</blockquote></div><br></div>

--000000000000d1a2b1056ce4bfb5--


From nobody Wed May 23 13:17:10 2018
Return-Path: <ted.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 381CD12D7E4 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 13:17:09 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 ucEd3JYBGR0e for <quic@ietfa.amsl.com>; Wed, 23 May 2018 13:16:59 -0700 (PDT)
Received: from mail-ot0-x235.google.com (mail-ot0-x235.google.com [IPv6:2607:f8b0:4003:c0f::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A19F712D7E2 for <quic@ietf.org>; Wed, 23 May 2018 13:16:54 -0700 (PDT)
Received: by mail-ot0-x235.google.com with SMTP id l22-v6so26752435otj.0 for <quic@ietf.org>; Wed, 23 May 2018 13:16:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=jm7ba8CcwSm1dv6wkVQBvMCNdqvXeN8UL12mhpAHvPk=; b=af1HkacNndKmXXzthiGjIVgkYWBMspSZPXO+lYM7iS9qy7UDdp2V2T8gWOXU2XvmKm A68au9ANfM73GSQ88q32YcV0qDrBQa1AKW0pbEpLp1eDsS7fnyC0xxNh4yoEQcukJya6 lMFPCxaVpE6BVA8u9k2LYjF7vJdxNCeo+MtpnwM0PrDxdLxFdW9PXiapxmf/VSYvcKMT UWOj3EvGhltr2qD4eCTltYA336m7xupWLOSd5Uc5wWP4BUQWCkrY/Ec8HZIBMKV4xmBT BOjH0eNaXspNuitRtD173SYYlnvrsTFQvsCgtEKYoASMRUkHx7b2tRr28YchDc3RtmHu sarw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=jm7ba8CcwSm1dv6wkVQBvMCNdqvXeN8UL12mhpAHvPk=; b=oTc/Jp/hFt1qqtyVpbNlmGGBhQzTABoaiOgEhwZYnKbUGFVbBN9nh8XyQTmcNLpB2W Msd3ILgtF3vqlSZYSYOs2G2ffBnUJh0LoFGPsAjOhUb4NlCqDp91KYE9v6yjSUpcS2ch siQ2ev4TSdVV4gxESGcJVvej7EIWVFf9mKOHITaoSRRaQE21OAvhaxKVVFmYNXd4oIYj w8gSu6e2bUIqfoOaaXnuhQEtPMzrMXTZZyhYoUHDpEytwL5+5zZ+cPiSmFoh4pJALNp5 AbKj+JDNH+/hf71B8yxsaob0dCEa1FhV8I91/MFYbs8LxBvmn4Tw2lmbjjQkpi7MlEtr v9mA==
X-Gm-Message-State: ALKqPwe0RAUFspGgOioKe9TZ2NjywEkbQrUpkYcdoancXXeCQ+6XdARe WltcaHdWwAsPsDoqLIirqnhPRcOG2zOVD81o8qJxlA==
X-Google-Smtp-Source: AB8JxZq6PTxEY+yVcFqQ6r6l4XVf9bVpjaaDTXchmv/pfiTSmUszoHE5/PpdwfKQv8nXhaA5uaoGRnckJWDxHdaC8yg=
X-Received: by 2002:a9d:3fda:: with SMTP id i26-v6mr2542375ote.18.1527106613665;  Wed, 23 May 2018 13:16:53 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:4399:0:0:0:0:0 with HTTP; Wed, 23 May 2018 13:16:23 -0700 (PDT)
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 23 May 2018 13:16:23 -0700
Message-ID: <CA+9kkMA0QnSmvbGOktngU+B-eC7CJFXLicEZfxQga6m6Z+gJLQ@mail.gmail.com>
Subject: Higher layer comments on stream 0 proposal, WG schedule, and gQUIC
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003de303056ce5373a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/9iBS2-qtizta2G6DFE5wC43_ZMA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 20:17:09 -0000

--0000000000003de303056ce5373a
Content-Type: text/plain; charset="UTF-8"

The charter for the working group currently says:

This work will describe how the protocol uses TLS 1.3 for key negotiation
and will also describe how those keys are used to provide confidentiality
and integrity protection of both application data and QUIC headers.

It's easy to read that as saying the work should be constrained to use TLS
1.3 as provided.  If we read it that way, the design team proposal is
strictly speaking out of charter, because it requires the creation of not
just new APIs for TLS 1.3 but essentially a new formal analysis that the
security guarantees work when there is no record layer and where the
replacement has somewhat different facilities.

But the charter also says

Note that consensus is required both for changes to the current
protocol mechanisms and retention of current mechanisms. In particular,
because something is in the initial document set does not imply that
there is consensus around the feature or around how it is specified.

That argues that the community was willing to see serious change in
adopting this work and that this work falls within the kind of change that
was contemplated, even if happens to be across working groups.  Personally,
I think that means the design should be considered.

But I have grave concerns about the implications.  My back of the envelope
calculation is that this means at least one more cycle of specification and
interop will be required before we get back to where we are with draft -11,
and that estimate is because I'm in a hopeful mood that Sean and Eric can
move the required work in TLS along.  A more practical Ted would see this
as adding at minimum 6 months to the schedule.  The changes in TLS are also
large enough that I expect that the deployment time to see significant
penetration of the new libraries to be longer than it would be for the
previous design.   Call it 9 months, with 3 months of error bar.

During that time, the penetration of gQUIC outside Google does not seem
likely to slow.  If you want what QUIC has to offer now, you will take the
already available code and go.  For Web usages, there are some down sides
to that, and it may slow the eventual deployment of IETF QUIC.

But there are also down sides to all of the other protocols that would like
to use QUIC but have been told to wait for the completion of this effort.
We're likely to see DNS over HTTPS over QUIC instead of DNS over QUIC,
simply because the DOH transport docs will be done.  There are some
advantages there, but also disadvantages in enmeshing the HTTP and DNS
caching semantics.    There are also a number of groups who want to use
QUIC as a replacement for the WebRTC data channel (and some as the
substrate for media).  This additional delay will certainly cause some code
to be written that will either need extensive change or will bit rot (or
fork).  None of that is without costs, especially opportunity costs.

If the working group does decide to adopt this design, I believe part of
the milestone adjustment must be a serious consideration of delaying the
qpack and HTTP-specific work while the core transport is finished.  The
good news, I think this design could end up making the document separation
that requires much cleaner, as well as making how to use QUIC with other
application protocols much more obvious.

My thanks again for doing the work of bringing the design forward,

Ted

--0000000000003de303056ce5373a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>The charter for the working group currently says:</di=
v><div><br></div><div style=3D"margin-left:40px">This work will describe ho=
w the protocol uses TLS 1.3 for key negotiation and will also describe how =
those keys are used to provide confidentiality and integrity protection of =
both application data and QUIC headers. <br></div><div><br></div><div>It&#3=
9;s easy to read that as saying the work should be constrained to use TLS 1=
.3 as provided.=C2=A0 If we read it that way, the design team proposal is s=
trictly speaking out of charter, because it requires the creation of not ju=
st new APIs for TLS 1.3 but essentially a new formal analysis that the secu=
rity guarantees work when there is no record layer and where the replacemen=
t has somewhat different facilities.=C2=A0 <br></div><div><br></div><div>Bu=
t the charter also says<br></div><div><br></div><div style=3D"margin-left:4=
0px">Note that consensus is required both for changes to the current <br>pr=
otocol mechanisms and retention of current mechanisms. In particular, <br>b=
ecause something is in the initial document set does not imply that <br>the=
re is consensus around the feature or around how it is specified.</div><div=
 style=3D"margin-left:40px"><br></div><div>That argues that the community w=
as willing to see serious change in adopting this work and that this work f=
alls within the kind of change that was contemplated, even if happens to be=
 across working groups.=C2=A0 Personally, I think that means the design sho=
uld be considered.</div><div><br></div><div>But I have grave concerns about=
 the implications.=C2=A0 My back of the envelope calculation is that this m=
eans at least one more cycle of specification and interop will be required =
before we get back to where we are with draft -11, and that estimate is bec=
ause I&#39;m in a hopeful mood that Sean and Eric can move the required wor=
k in TLS along.=C2=A0 A more practical Ted would see this as adding at mini=
mum 6 months to the schedule.=C2=A0 The changes in TLS are also large enoug=
h that I expect that the deployment time to see significant penetration of =
the new libraries to be longer than it would be for the previous design.=C2=
=A0=C2=A0 Call it 9 months, with 3 months of error bar.</div><div><br></div=
><div>During that time, the penetration of gQUIC outside Google does not se=
em likely to slow.=C2=A0 If you want what QUIC has to offer now, you will t=
ake the already available code and go.=C2=A0 For Web usages, there are some=
 down sides to that, and it may slow the eventual deployment of IETF QUIC.<=
br></div><div><br></div><div>But there are also down sides to all of the ot=
her protocols that would like to use QUIC but have been told to wait for th=
e completion of this effort.=C2=A0 We&#39;re likely to see DNS over HTTPS o=
ver QUIC instead of DNS over QUIC, simply because the DOH transport docs wi=
ll be done.=C2=A0 There are some advantages there, but also disadvantages i=
n enmeshing the HTTP and DNS caching semantics.=C2=A0=C2=A0=C2=A0 There are=
 also a number of groups who want to use QUIC as a replacement for the WebR=
TC data channel (and some as the substrate for media).=C2=A0 This additiona=
l delay will certainly cause some code to be written that will either need =
extensive change or will bit rot (or fork).=C2=A0 None of that is without c=
osts, especially opportunity costs.</div><div><br></div><div>If the working=
 group does decide to adopt this design, I believe part of the milestone ad=
justment must be a serious consideration of delaying the qpack and HTTP-spe=
cific work while the core transport is finished.=C2=A0 The good news, I thi=
nk this design could end up making the document separation that requires mu=
ch cleaner, as well as making how to use QUIC with other application protoc=
ols much more obvious.</div><div><br></div><div>My thanks again for doing t=
he work of bringing the design forward,</div><div><br></div><div>Ted<br></d=
iv><div><br></div><div><br></div></div>

--0000000000003de303056ce5373a--


From nobody Wed May 23 13:23:36 2018
Return-Path: <rsalz@akamai.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E63A112E8EE for <quic@ietfa.amsl.com>; Wed, 23 May 2018 13:23:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level: 
X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 QXSD_GNbEUHZ for <quic@ietfa.amsl.com>; Wed, 23 May 2018 13:23:21 -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 AB68912D7F5 for <quic@ietf.org>; Wed, 23 May 2018 13:23:21 -0700 (PDT)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.0.22/8.16.0.22) with SMTP id w4NKGeII001845; Wed, 23 May 2018 21:23:19 +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 : mime-version; s=jan2016.eng; bh=aopgM+ZgDdJiorM/l3AxCelP4UMqKMKnrUscayt1vZY=; b=Sh+Wh2VYQ/pkvH0mz2McUlTrpzTGZCKQHN6hg6wcrThJF73SPQOoy9wnCAw9ST6ABhZw c2Nxv1xkHJIoS8HE/Cs0uPXajqfW72fFEVEnrTLIVRayKTZs4wij8BcyUBDXl0IA/zXg OMU/0KLf+H3ZoMc1BsBzfHeq/VGFHFPNURzqjowv0qsghhcptJtYPogk8S1xyBkiUZhw HUi8WxGzz1j9ea/QIRUTVAKkBujFEgFsCAKvxmJj9MZTpPU9VJjSb+JFdquLzZjF398V eI6S/9JEgxdopfc6WurI3FOFfZWDDMSpEgcd7amRFCC0WDQLPDcf5RzgbMkEyFMTLOd1 CA== 
Received: from prod-mail-ppoint2 (prod-mail-ppoint2.akamai.com [184.51.33.19]) by m0050095.ppops.net-00190b01. with ESMTP id 2j5e90r6ca-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 23 May 2018 21:23:19 +0100
Received: from pps.filterd (prod-mail-ppoint2.akamai.com [127.0.0.1]) by prod-mail-ppoint2.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w4NKGIIq028042; Wed, 23 May 2018 16:23:17 -0400
Received: from email.msg.corp.akamai.com ([172.27.25.34]) by prod-mail-ppoint2.akamai.com with ESMTP id 2j2f8um84f-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 23 May 2018 16:23:17 -0400
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com (172.27.27.101) by ustx2ex-dag1mb3.msg.corp.akamai.com (172.27.27.103) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 23 May 2018 15:23:16 -0500
Received: from USTX2EX-DAG1MB1.msg.corp.akamai.com ([172.27.6.131]) by ustx2ex-dag1mb1.msg.corp.akamai.com ([172.27.6.131]) with mapi id 15.00.1365.000; Wed, 23 May 2018 15:23:16 -0500
From: "Salz, Rich" <rsalz@akamai.com>
To: Ted Hardie <ted.ietf@gmail.com>, IETF QUIC WG <quic@ietf.org>
Subject: Re: Higher layer comments on stream 0 proposal, WG schedule, and gQUIC
Thread-Topic: Higher layer comments on stream 0 proposal, WG schedule, and gQUIC
Thread-Index: AQHT8tMOC2K7YAwKpUaetsFygE0BU6Q90uAA
Date: Wed, 23 May 2018 20:23:16 +0000
Message-ID: <82DC1097-F6AB-426C-90B1-010C65A0F4BE@akamai.com>
References: <CA+9kkMA0QnSmvbGOktngU+B-eC7CJFXLicEZfxQga6m6Z+gJLQ@mail.gmail.com>
In-Reply-To: <CA+9kkMA0QnSmvbGOktngU+B-eC7CJFXLicEZfxQga6m6Z+gJLQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.d.0.180513
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.41.7]
Content-Type: multipart/alternative; boundary="_000_82DC1097F6AB426C90B1010C65A0F4BEakamaicom_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-23_07:, , 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=869 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805230199
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-23_07:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=800 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1711220000 definitions=main-1805230199
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/W_A1kXHPWJQrGhOZjefk9YppNrg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 20:23:34 -0000

--_000_82DC1097F6AB426C90B1010C65A0F4BEakamaicom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

PiBUaGUgY2hhbmdlcyBpbiBUTFMgYXJlIGFsc28gbGFyZ2UgZW5vdWdoIHRoYXQgSSBleHBlY3Qg
dGhhdCB0aGUgZGVwbG95bWVudCB0aW1lIHRvIHNlZSBzaWduaWZpY2FudCBwZW5ldHJhdGlvbiBv
ZiB0aGUgbmV3IGxpYnJhcmllcyB0byBiZSBsb25nZXIgdGhhbiBpdCB3b3VsZCBiZSBmb3IgdGhl
IHByZXZpb3VzIGRlc2lnbi4gICBDYWxsIGl0IDkgbW9udGhzLCB3aXRoIDMgbW9udGhzIG9mIGVy
cm9yIGJhci4NCg0KRm9yIHdoYXQgaXTigJlzIHdvcnRoLCB0aGUgbmV4dCByZWxlYXNlIG9mIE9w
ZW5TU0wgd291bGQgaGF2ZSBzdXBwb3J0ZWQgZXZlcnl0aGluZyB0aGF04oCZcyBuZWVkZWQgZm9y
IHRoZSBwcmlvciBRVUlDIGNyeXB0by4gV2UgaGFkIHNvbWUgZW1haWwgY2hhdHMgd2l0aCBDaHJp
cywgYW5kIGluIG15IHZpZXcsIHRoaXMgaXMgbm8gbG9uZ2VyIHBvc3NpYmxlLCB3aGljaCBtZWFu
cyBpdCB3aWxsIGZhbGwgdG8gdGhlIG5leHQgcmVsZWFzZSwgd2hpY2ggd2lsbCBiZSBnYXRlZCBi
eSBGSVBTIHZhbGlkYXRpb24gd29yayBhbmQgaXMgcHJvYmFibHkgc2ltaWxhciB0aW1ldGFibGUg
dG8geW91cnMsIGFib3ZlLiAgT3IgZm9sa3Mgd2lsbCBoYXZlIHRvIHJ1biBvZmYgbWFzdGVyLCB3
aGljaCBtYW55IGFyZSByZWx1Y3RhbnQgdG8gZG8uDQoNCg0KDQo=

--_000_82DC1097F6AB426C90B1010C65A0F4BEakamaicom_
Content-Type: text/html; charset="utf-8"
Content-ID: <00F53E909943D64E945E962B2228AA32@akamai.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1i
b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
IixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9
DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpw
Lm1zb25vcm1hbDAsIGxpLm1zb25vcm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1u
YW1lOm1zb25vcm1hbDsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6
MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglm
b250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNw
YW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0No
cERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBw
dDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEu
MGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2Vj
dGlvbjE7fQ0KLS0+PC9zdHlsZT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSIj
MDU2M0MxIiB2bGluaz0iIzk1NEY3MiI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+Jmd0OyBUaGUgY2hhbmdlcyBpbiBUTFMgYXJlIGFsc28gbGFyZ2Ug
ZW5vdWdoIHRoYXQgSSBleHBlY3QgdGhhdCB0aGUgZGVwbG95bWVudCB0aW1lIHRvIHNlZSBzaWdu
aWZpY2FudCBwZW5ldHJhdGlvbiBvZiB0aGUgbmV3IGxpYnJhcmllcyB0byBiZSBsb25nZXIgdGhh
biBpdCB3b3VsZCBiZSBmb3IgdGhlIHByZXZpb3VzIGRlc2lnbi4mbmJzcDsmbmJzcDsgQ2FsbCBp
dCA5IG1vbnRocywgd2l0aCAzIG1vbnRocyBvZiBlcnJvciBiYXIuPG86cD48L286cD48L3A+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5Gb3Igd2hhdCBpdOKAmXMgd29ydGgsIHRoZSBuZXh0IHJlbGVhc2Ugb2Yg
T3BlblNTTCB3b3VsZCBoYXZlIHN1cHBvcnRlZCBldmVyeXRoaW5nIHRoYXTigJlzIG5lZWRlZCBm
b3IgdGhlIHByaW9yIFFVSUMgY3J5cHRvLiBXZSBoYWQgc29tZSBlbWFpbCBjaGF0cyB3aXRoIENo
cmlzLCBhbmQgaW4gbXkgdmlldywgdGhpcyBpcyBubyBsb25nZXIgcG9zc2libGUsIHdoaWNoIG1l
YW5zIGl0IHdpbGwgZmFsbCB0byB0aGUgbmV4dA0KIHJlbGVhc2UsIHdoaWNoIHdpbGwgYmUgZ2F0
ZWQgYnkgRklQUyB2YWxpZGF0aW9uIHdvcmsgYW5kIGlzIHByb2JhYmx5IHNpbWlsYXIgdGltZXRh
YmxlIHRvIHlvdXJzLCBhYm92ZS4mbmJzcDsgT3IgZm9sa3Mgd2lsbCBoYXZlIHRvIHJ1biBvZmYg
bWFzdGVyLCB3aGljaCBtYW55IGFyZSByZWx1Y3RhbnQgdG8gZG8uPG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_82DC1097F6AB426C90B1010C65A0F4BEakamaicom_--


From nobody Wed May 23 13:24:36 2018
Return-Path: <ekr@rtfm.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B6C412D7E2 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 13:24:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 xwHJGJcfTg24 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 13:24:32 -0700 (PDT)
Received: from mail-ot0-x22b.google.com (mail-ot0-x22b.google.com [IPv6:2607:f8b0:4003:c0f::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 019F1127978 for <quic@ietf.org>; Wed, 23 May 2018 13:24:32 -0700 (PDT)
Received: by mail-ot0-x22b.google.com with SMTP id l12-v6so26759319oth.6 for <quic@ietf.org>; Wed, 23 May 2018 13:24:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=dvTTb3t4jd39G5NrgbgszDn8dXHAranPpchjQ83+Hrg=; b=wn1rTn3rsDt3dZhfFrWM2Dx7RJvlii/priLyBsFppgZpbcr0ty9g9o1R9iAnIJpJcM XNZDNnuUdy/0iSpCTMLm6rnZrIotWjQEZn96Jv/O9u+ubWjc7JcsLT+XexdFhwQgzi9C l2y7XWe0IeLAqjC0Th8ongou7kaEri/0kRKW9wuiJEymXPB9/bfuKJT9GFm2LAqU0s0e EJgqDPdl4ZxqLL/3ftaStDNxXykaBTQbK8ERWml9x/tZGUo3w6X+f+4VSw5qCDcU9FLP juGuluYInxZSipeDb6oBniZpfpl7/7fom+olP//ma/iyqP4z+q4Kj1uRjUFb8Ba/+pWu zKGQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=dvTTb3t4jd39G5NrgbgszDn8dXHAranPpchjQ83+Hrg=; b=QENFK8sNXWIhuELFZ84/KahEoL19L5TbiB7m1CdPCNQMtFKnKJBS7/KuY9xBUrCUGl uqnVIxybJlgZlu6MLcJwsV1zZZTwhCC5NCO9DDL781S3KPDkk5mgtkidu+r7FJQDez+P iridT5jIAT8qVnaMX2Z81OE6Z/fhCS5c7fxDooWL9XXuiqZyvhTXUHhyAiWwnh++U507 /vO8m6WmKZ77OeL7v7uxrdSVSFpfzJVNPD0my80YjJyILY1hdgbYj4J90CHzGFm1ktmZ dyLs4w/WRo46akS3eDxug8qs6hkTAfMrRx2W/reQTKgEDdupKL8dvsKriWWsEaFifjbc JrXw==
X-Gm-Message-State: ALKqPwfDTR7z2x6sNCKaFs+qaeg1mw+y6LwqEh+3/0Bis9CBBXdjUE0/ 5qeo3gCxkm6B8BYMp/bsspsOHVZUDKX7EplvVEtBBg==
X-Google-Smtp-Source: AB8JxZp05qMJO9dcR68YBRnecDL5PhKw8IQYeks+dqP8edV0TtzaCGlEn23AeRXZ4SSU6z4OCGWne5x0szhN1p109rQ=
X-Received: by 2002:a9d:5917:: with SMTP id t23-v6mr2875332oth.217.1527107071201;  Wed, 23 May 2018 13:24:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:ac9:66:0:0:0:0:0 with HTTP; Wed, 23 May 2018 13:23:50 -0700 (PDT)
In-Reply-To: <CA+9kkMC0a+HELyVvh+DtvkiorWmKkUQ346zt49Xfyd1zzZ780Q@mail.gmail.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CA+9kkMC0a+HELyVvh+DtvkiorWmKkUQ346zt49Xfyd1zzZ780Q@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 23 May 2018 13:23:50 -0700
Message-ID: <CABcZeBP-BWwVAbPuT8rT12pMoNpWhD0qdOLB=-Lj=qrRrwq3ag@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: Ted Hardie <ted.ietf@gmail.com>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Eric Rescorla <ekr@mozilla.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000836754056ce5523f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/o2Ykdfi17w_tNZb9huFmw-VG0pY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 20:24:36 -0000

--000000000000836754056ce5523f
Content-Type: text/plain; charset="UTF-8"

On Wed, May 23, 2018 at 12:42 PM, Ted Hardie <ted.ietf@gmail.com> wrote:

> Howdy,
>
> Thanks for sharing the document.  I have a couple of detailed comments,
> and then some high level comments which I will put into a separate email.
>
> First, the document says this:
>
> Though proper analysis is needed, it is not likely that the removal of the
> TLS record layer will cause a security concern, because the security
> properties provided by QUIC packets are identical to what have been
> provided by TLS records.
>
>
> I'm not sure that this is actually the statement we need to analyze,
> though. We need to be sure that the security properties of TLS records used
> in TCP packets are available in QUIC streams in QUIC packets using UDP as a
> multiplexing layer. There appear to be some difference in where the
> facilities the overall system provides that may require more description.
> As an example, I think the way padding works in this proposal needs more
> description. If I understand correctly, each TLS record is encrypted
> separately and the presence or absence of padding is indicated by a
> padding_length byte present in each record. That means the padding is
> related to the record, not the packet; by removing the record layer and
> using QUIC frames, though, we seem to have a different padding structure.
> QUIC uses padding frames, not padding within other frame types which is
> both conceptually and practically different.
>

I believe you have misunderstood. In this document, there are no TLS
records and TLS handshake messages are carried in CRYPTO_HS frames.
Accordingly, padding is provided in the same fashion as QUIC ordinarily
does, i.e., using PADDING frames.


Similarly, I'd be interested in more text on the interaction with
> precedence, since the loss of the record layer means that the former
> guarantee that the record layer makes records available in the order in
> which they were protected now seems to be unavailable.
>

I'm not quite sure I follow what you are asking about here. In both cases,
TLS sits on top of QUIC's reliable in-order deliver guarantees. Is the
point you are making that formerly, if QUIC violated these guarantees, that
would result in TLS handshake failure, whereas now it does not?

-Ekr



> regards,
>
>
> Ted
>
>
>
>
>
> On Tue, May 22, 2018 at 6:30 PM, Ian Swett <ianswett=40google.com@dmarc.
> ietf.org> wrote:
>
>>
>>
>>
>>
>>
>>
>>
>> *Dear QUIC WG,On behalf of the Stream 0 Design Team, I am pleased to
>> report that we have consensus on a proposed approach to share with the WG.
>> The DT's proposal will make QUIC and TLS work closer together and
>> incorporates ideas from DTLS, but it does not use the DTLS protocol itself.
>> The DT believes this solves the important open Stream 0 issues. The
>> proposal will be a bit more invasive in TLS, but we believe it is the right
>> long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and
>> Mint) are willing and able to do the work necessary.. A number of stacks
>> are currently working on implementations of this new approach, which we
>> hope to have in time for the Interim meeting.A design document describing
>> the overall approach can be found
>> at:https://docs.google..com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit
>> <https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit>A
>> PR making the changes to the QUIC documents can be found
>> at:https://github.com/quicwg/base-drafts/pull/1377
>> <https://github.com/ekr/base-drafts/pull/29>A few design details did not
>> have clear consensus, but it was felt it would be better to discuss those
>> in the wider WG than delay the design team.  A consistent choice was made
>> in the PR and these issues are mentioned in Appendix B of the design doc.As
>> always, comments and questions welcome. That said, this is a big PR and we
>> recognize that some editorial work is going to be needed before merging. In
>> the interest of letting people follow along, and to keep github from
>> falling over, we ask people to keep discussion on the mailing list and
>> refrain from making PR comments.See you in Kista!*
>> Ian and Eric
>>
>
>

--000000000000836754056ce5523f
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, May 23, 2018 at 12:42 PM, Ted Hardie <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:ted.ietf@gmail.com" target=3D"_blank">ted.ietf@gmail.com</a>&=
gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>H=
owdy,</div><div><br></div><div>Thanks for sharing the document.=C2=A0 I hav=
e a couple of detailed comments, and then some high level comments which I =
will put into a separate email.</div><div><br></div><div>First, the documen=
t says this:</div><div><br></div><div><p style=3D"line-height:1.38;margin-t=
op:0pt;margin-bottom:0pt;text-align:justify;margin-left:40px" id=3D"m_-7919=
340867003085784gmail-docs-internal-guid-ae9978f1-8e74-9194-2b6b-f4000bc3b54=
1"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);backgro=
und-color:transparent;font-weight:400;font-style:normal;font-variant:normal=
;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Though =
proper analysis is needed, it is not likely that the removal of the TLS rec=
ord layer will cause a security concern, because the security properties pr=
ovided by QUIC packets are identical to what have been provided by TLS reco=
rds.</span></p><p style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0p=
t;text-align:justify"><span style=3D"font-size:11pt;font-family:Arial;color=
:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;=
font-variant:normal;text-decoration:none;vertical-align:baseline;white-spac=
e:pre-wrap"><br></span></p><p style=3D"line-height:1.38;margin-top:0pt;marg=
in-bottom:0pt;text-align:justify"><span style=3D"font-size:11pt;font-family=
:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-s=
tyle:normal;font-variant:normal;text-decoration:none;vertical-align:baselin=
e;white-space:pre-wrap">I&#39;m not sure that this is actually the statemen=
t we need to analyze, though.  We need to be sure that the security propert=
ies of TLS records used in TCP packets are available in QUIC streams in QUI=
C packets using UDP as a multiplexing layer.  There appear to be some diffe=
rence in where the facilities the overall system provides that may require =
more description.  As an example, I think the way padding works in this pro=
posal needs more description.  If I understand correctly, each TLS record i=
s encrypted separately and the presence or absence of padding is indicated =
by a padding_length byte present in each record.  That means the padding is=
 related to the record, not the packet; by removing the record layer and us=
ing QUIC frames, though, we seem to have a different padding structure.  QU=
IC uses padding frames, not padding within other frame types which is both =
conceptually and practically different.  </span></p></div></div></blockquot=
e><div><br></div><div>I believe you have misunderstood. In this document, t=
here are no TLS records and TLS handshake messages are carried in CRYPTO_HS=
 frames. Accordingly, padding is provided in the same fashion as QUIC ordin=
arily does, i.e., using PADDING frames.<br></div><div><br></div><div><br></=
div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-lef=
t:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><p style=3D"line-h=
eight:1.38;margin-top:0pt;margin-bottom:0pt;text-align:justify"><span style=
=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:tran=
sparent;font-weight:400;font-style:normal;font-variant:normal;text-decorati=
on:none;vertical-align:baseline;white-space:pre-wrap">Similarly, I&#39;d be=
 interested in more text on the interaction with precedence, since the loss=
 of the record layer means that the former guarantee that the record layer =
makes records available in the order in which they were protected now seems=
 to be unavailable.<br></span></p></div></div></blockquote><div><br></div><=
div>I&#39;m not quite sure I follow what you are asking about here. In both=
 cases, TLS sits on top of QUIC&#39;s reliable in-order deliver guarantees.=
 Is the point you are making that formerly, if QUIC violated these guarante=
es, that would result in TLS handshake failure, whereas now it does not?<br=
></div><br></div><div class=3D"gmail_quote">-Ekr</div><div class=3D"gmail_q=
uote"><br></div><div class=3D"gmail_quote"><div><br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div dir=3D"ltr"><div><p style=3D"line-height:1.38;margin-top=
:0pt;margin-bottom:0pt;text-align:justify"><span style=3D"font-size:11pt;fo=
nt-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:4=
00;font-style:normal;font-variant:normal;text-decoration:none;vertical-alig=
n:baseline;white-space:pre-wrap"><br></span></p><p style=3D"line-height:1.3=
8;margin-top:0pt;margin-bottom:0pt;text-align:justify"><span style=3D"font-=
size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;f=
ont-weight:400;font-style:normal;font-variant:normal;text-decoration:none;v=
ertical-align:baseline;white-space:pre-wrap">regards,</span></p><p style=3D=
"line-height:1.38;margin-top:0pt;margin-bottom:0pt;text-align:justify"><spa=
n style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-col=
or:transparent;font-weight:400;font-style:normal;font-variant:normal;text-d=
ecoration:none;vertical-align:baseline;white-space:pre-wrap"><br></span></p=
><p style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;text-align:j=
ustify"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);ba=
ckground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Te=
d<br></span></p><p style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0=
pt;text-align:justify"><span style=3D"font-size:11pt;font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal=
;font-variant:normal;text-decoration:none;vertical-align:baseline;white-spa=
ce:pre-wrap"></span></p><pre><br></pre><br><p></p><br></div></div><div clas=
s=3D"gmail_extra"><br><div class=3D"gmail_quote"><span class=3D"">On Tue, M=
ay 22, 2018 at 6:30 PM, Ian Swett <span dir=3D"ltr">&lt;<a href=3D"mailto:i=
answett=3D40google.com@dmarc.ietf.org" target=3D"_blank">ianswett=3D40googl=
e.com@dmarc.<wbr>ietf.org</a>&gt;</span> wrote:<br></span><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div dir=3D"ltr"><b style=3D"font-weight:normal" id=3D"m_-791=
9340867003085784m_-1851091610820382769gmail-docs-internal-guid-2a62f340-8a8=
f-9073-5cad-25b8001e52b3"><span class=3D""><p dir=3D"ltr" style=3D"line-hei=
ght:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;fo=
nt-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:4=
00;font-style:normal;font-variant:normal;text-decoration:none;vertical-alig=
n:baseline;white-space:pre-wrap">Dear QUIC WG,</span></p><br><p dir=3D"ltr"=
 style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D=
"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transpa=
rent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:=
none;vertical-align:baseline;white-space:pre-wrap">On behalf of the Stream =
0 Design Team, I am pleased to report that we have consensus on a proposed =
approach to share with the WG. The DT&#39;s proposal will make QUIC and TLS=
 work closer together and incorporates ideas from DTLS, but it does not use=
 the DTLS protocol itself. </span></p><br><p dir=3D"ltr" style=3D"line-heig=
ht:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;fon=
t-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:40=
0;font-style:normal;font-variant:normal;text-decoration:none;vertical-align=
:baseline;white-space:pre-wrap">The DT believes this solves the important o=
pen Stream 0 issues. The proposal will be a bit more invasive in TLS, but w=
e believe it is the right long-term direction and several TLS stacks (Borin=
gSSL, PicoTLS, NSS, and Mint) are willing and able to do the work necessary=
.. A number of stacks are currently working on implementations of this new =
approach, which we hope to have in time for the Interim meeting.</span></p>=
<br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0=
pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);backgr=
ound-color:transparent;font-weight:400;font-style:normal;font-variant:norma=
l;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">A desi=
gn document describing the overall approach can be found at:</span></p></sp=
an><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0p=
t"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);backgro=
und-color:transparent;font-weight:400;font-style:normal;font-variant:normal=
;text-decoration:none;vertical-align:baseline;white-space:pre-wrap"><a href=
=3D"https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT9=
3j6SwHY8/edit" target=3D"_blank">https://docs.google..com/docum<wbr>ent/d/1=
fRsJqPinJl8N3b-bflDRV6a<wbr>uojfJLkxddT93j6SwHY8/edit</a></span></p><span c=
lass=3D""><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margi=
n-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0=
,0);background-color:transparent;font-weight:400;font-style:normal;font-var=
iant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wr=
ap">A PR making the changes to the QUIC documents can be found at:</span></=
p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt=
"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);backgrou=
nd-color:transparent;font-weight:400;font-style:normal;font-variant:normal;=
text-decoration:none;vertical-align:baseline;white-space:pre-wrap"><a href=
=3D"https://github.com/ekr/base-drafts/pull/29" target=3D"_blank">https://g=
ithub.com/quicwg/base<wbr>-drafts/pull/1377</a></span></p><br><p dir=3D"ltr=
" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=
=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:tran=
sparent;font-weight:400;font-style:normal;font-variant:normal;text-decorati=
on:none;vertical-align:baseline;white-space:pre-wrap">A few design details =
did not have clear consensus, but it was felt it would be better to discuss=
 those in the wider WG than delay the design team.=C2=A0 A consistent choic=
e was made in the PR and these issues are mentioned in Appendix B of the de=
sign doc.</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top=
:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;col=
or:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:norma=
l;font-variant:normal;text-decoration:none;vertical-align:baseline;white-sp=
ace:pre-wrap">As always, comments and questions welcome. That said, this is=
 a big PR and we recognize that some editorial work is going to be needed b=
efore merging. In the interest of letting people follow along, and to keep =
github from falling over, we ask people to keep discussion on the mailing l=
ist and refrain from making PR comments.</span></p><br><p dir=3D"ltr" style=
=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-=
size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;f=
ont-weight:400;font-style:normal;font-variant:normal;text-decoration:none;v=
ertical-align:baseline;white-space:pre-wrap">See you in Kista!</span></p></=
span></b><br class=3D"m_-7919340867003085784m_-1851091610820382769gmail-App=
le-interchange-newline">Ian and Eric</div>
</blockquote></div><br></div>
</blockquote></div><br></div></div>

--000000000000836754056ce5523f--


From nobody Wed May 23 13:25:53 2018
Return-Path: <prvs=8681a6c8ca=fenix@fb.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9536512D7E6 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 13:25:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=BcyE9W5P; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=HPHpf3UG
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 1xawbMCqBdyt for <quic@ietfa.amsl.com>; Wed, 23 May 2018 13:25:49 -0700 (PDT)
Received: from mx0a-00082601.pphosted.com (mx0b-00082601.pphosted.com [67.231.153.30]) (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 4D8CD12D77B for <quic@ietf.org>; Wed, 23 May 2018 13:25:49 -0700 (PDT)
Received: from pps.filterd (m0089730.ppops.net [127.0.0.1]) by m0089730.ppops.net (8.16.0.22/8.16.0.22) with SMTP id w4NKJJQ5029030; Wed, 23 May 2018 13:25:47 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=facebook; bh=9L6JCcCwww7jnxyTrLia2vc1m0plkTHGYrTrZbNvDyY=; b=BcyE9W5PUfBd70UsyHq58//8V3KVAOyVrs5qi6S9+5vZZIkarYi0MFtxAG4/TdGOGDAw 6bVJEZ+s//gXrrChLL2GN9DoDljnWa1DoUGz05RNH0pI1bXX/jWNz6HlRpWR9MNyorSw AypRzeEkiLJ5ZWSur/JfjO2VO6GWvg5gQ1Y= 
Received: from maileast.thefacebook.com ([199.201.65.23]) by m0089730.ppops.net with ESMTP id 2j5e11885s-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 23 May 2018 13:25:47 -0700
Received: from NAM01-BY2-obe.outbound.protection.outlook.com (192.168.183.28) by o365-in.thefacebook.com (192.168.177.21) with Microsoft SMTP Server (TLS) id 14.3.361.1; Wed, 23 May 2018 16:25:46 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=9L6JCcCwww7jnxyTrLia2vc1m0plkTHGYrTrZbNvDyY=; b=HPHpf3UGu7d1Xlgd+zAhGmHzQNf5/RZ758kAo9zVye0g7hZI9lOVM+gGDkrn8SvGZ7J+fbAeB+TiaZXMSs3VEqWitgz05DCtnAE8eXZE19tZD4h4A6wkoRTS0vCuguX95+DTuSm9lmDOLREp5agjHHFVUUK1D07YDGRajjKoPrA=
Received: from BYAPR15MB2312.namprd15.prod.outlook.com (52.135.197.146) by BYAPR15MB2296.namprd15.prod.outlook.com (52.135.197.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.776.11; Wed, 23 May 2018 20:25:44 +0000
Received: from BYAPR15MB2312.namprd15.prod.outlook.com ([fe80::b434:da9b:6102:49eb]) by BYAPR15MB2312.namprd15.prod.outlook.com ([fe80::b434:da9b:6102:49eb%13]) with mapi id 15.20.0776.015; Wed, 23 May 2018 20:25:44 +0000
From: Roberto Peon <fenix@fb.com>
To: Ted Hardie <ted.ietf@gmail.com>, IETF QUIC WG <quic@ietf.org>
Subject: Re: Higher layer comments on stream 0 proposal, WG schedule, and gQUIC
Thread-Topic: Higher layer comments on stream 0 proposal, WG schedule, and gQUIC
Thread-Index: AQHT8tMjhc9MF6V1v0+36QOR0rfQvqQ9TXOA
Date: Wed, 23 May 2018 20:25:44 +0000
Message-ID: <319424C3-524D-4F0B-853A-F824DC3D9F9D@fb.com>
References: <CA+9kkMA0QnSmvbGOktngU+B-eC7CJFXLicEZfxQga6m6Z+gJLQ@mail.gmail.com>
In-Reply-To: <CA+9kkMA0QnSmvbGOktngU+B-eC7CJFXLicEZfxQga6m6Z+gJLQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.d.0.180513
x-originating-ip: [2620:10d:c090:200::5:de4e]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR15MB2296; 7:LXlPrwtt4fuRmJ7BgF8r/ddadaqr8SwKsoBhSpLl2W6QUZVCyJ6EcJS8QYyOcvpt3AypST2Q4eiED/V9Knu4ENHNeCX9Gl/j4h/SuYxc1KApgD3tKr2dRtgYpptXWlEmcajoUxJ8z9zMaQxvdxHgIq3KdiolDptgCUQdmiRsbkZhpxM7+/qFeQD2OOsnnwI+JY1VHUFUFCpuTZFkuzcwaTKjtWLI3qqlRxH93925KgBeMMQspGhGgQJPgo3WADTa; 20:K1+1/K7ZWBWvIthPJLFUXeqZ9+mTK5H7ZHO1rtWWoxvJ+OndvQaC6AxWMfAj5iuw8wZlw3/ZUiDOZgSKBJJsedT+C2He74rtwYD/c1l0r61u8gIdXxU6i8ypuuojTScQb3yHftuCC8MJGVtGsw1dB/b2GprPvl/hMXjUMMM6EQI=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BYAPR15MB2296; 
x-ms-traffictypediagnostic: BYAPR15MB2296:
x-microsoft-antispam-prvs: <BYAPR15MB22963A003139F3F06108B590CD6B0@BYAPR15MB2296.namprd15.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(192374486261705)(85827821059158)(100405760836317)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(3002001)(10201501046)(3231254)(11241501184)(944501410)(52105095)(93006095)(93001095)(149027)(150027)(6041310)(20161123558120)(20161123560045)(20161123562045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(6072148)(201708071742011)(7699016); SRVR:BYAPR15MB2296; BCL:0; PCL:0; RULEID:; SRVR:BYAPR15MB2296; 
x-forefront-prvs: 06818431B9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(39860400002)(366004)(39380400002)(396003)(346002)(51444003)(199004)(189003)(81166006)(97736004)(76176011)(3280700002)(99286004)(5250100002)(6512007)(6306002)(54896002)(53936002)(229853002)(2906002)(68736007)(6436002)(3660700001)(8676002)(81156014)(83716003)(2616005)(8936002)(6116002)(476003)(46003)(11346002)(446003)(59450400001)(6486002)(5660300001)(6506007)(36756003)(53546011)(186003)(102836004)(106356001)(7736002)(58126008)(316002)(486006)(14454004)(33656002)(82746002)(6246003)(39060400002)(110136005)(25786009)(86362001)(478600001)(2900100001)(105586002)(561944003)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR15MB2296; H:BYAPR15MB2312.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: fb.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: pvLJCU0qsiiHisNBuXRUuZWjocumLomiUoQssNcWwk4JmNN2rSc3IYAwD4ge/AKFB1VO2LOIamqwaa1WsTzCf3F79k+ni8m3m0m1sdxLNtgMJgue3/VegTfI1XQPuFGtLlRQUFe6FWX8KhYNla0qPRskCQQ/yks4OFGkmM4oyxxxb2SJYZ6sDKX/Pa+LYq4N
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_319424C3524D4F0B853AF824DC3D9F9Dfbcom_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 4205c48c-216d-41ea-be46-08d5c0eb5c4e
X-MS-Exchange-CrossTenant-Network-Message-Id: 4205c48c-216d-41ea-be46-08d5c0eb5c4e
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 May 2018 20:25:44.0211 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR15MB2296
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-23_07:, , signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/GGFmeSSETwo5zDKXuc8pD5wgs-k>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 20:25:52 -0000

--_000_319424C3524D4F0B853AF824DC3D9F9Dfbcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SeKAmWxsIHNheSBhZ2FpbiB0aGF0IHdlIHNob3VsZCBzdGFydCB3b3JrIG9uIElFVEYgUVVJQ3Yy
IG5vdy4NCkhvdy93aGVuIGRvIHdlIGNoYXJ0ZXIgdGhhdCB3b3JrPyBOb3Qgb25seSBkbyBJIHRo
aW5rIHRoaXMgaXMgdGhlIHJpZ2h0IHRoaW5nLCBJIHN1c3BlY3QgaXQgd2lsbCBzcGVlZCB1cCB0
aGUgd29yayBvbiBJRVRGIFFVSUN2MQ0KDQotPVINCg0KRnJvbTogUVVJQyA8cXVpYy1ib3VuY2Vz
QGlldGYub3JnPiBvbiBiZWhhbGYgb2YgVGVkIEhhcmRpZSA8dGVkLmlldGZAZ21haWwuY29tPg0K
RGF0ZTogV2VkbmVzZGF5LCBNYXkgMjMsIDIwMTggYXQgMToxNyBQTQ0KVG86IElFVEYgUVVJQyBX
RyA8cXVpY0BpZXRmLm9yZz4NClN1YmplY3Q6IEhpZ2hlciBsYXllciBjb21tZW50cyBvbiBzdHJl
YW0gMCBwcm9wb3NhbCwgV0cgc2NoZWR1bGUsIGFuZCBnUVVJQw0KDQpUaGUgY2hhcnRlciBmb3Ig
dGhlIHdvcmtpbmcgZ3JvdXAgY3VycmVudGx5IHNheXM6DQoNClRoaXMgd29yayB3aWxsIGRlc2Ny
aWJlIGhvdyB0aGUgcHJvdG9jb2wgdXNlcyBUTFMgMS4zIGZvciBrZXkgbmVnb3RpYXRpb24gYW5k
IHdpbGwgYWxzbyBkZXNjcmliZSBob3cgdGhvc2Uga2V5cyBhcmUgdXNlZCB0byBwcm92aWRlIGNv
bmZpZGVudGlhbGl0eSBhbmQgaW50ZWdyaXR5IHByb3RlY3Rpb24gb2YgYm90aCBhcHBsaWNhdGlv
biBkYXRhIGFuZCBRVUlDIGhlYWRlcnMuDQoNCkl0J3MgZWFzeSB0byByZWFkIHRoYXQgYXMgc2F5
aW5nIHRoZSB3b3JrIHNob3VsZCBiZSBjb25zdHJhaW5lZCB0byB1c2UgVExTIDEuLjMgYXMgcHJv
dmlkZWQuICBJZiB3ZSByZWFkIGl0IHRoYXQgd2F5LCB0aGUgZGVzaWduIHRlYW0gcHJvcG9zYWwg
aXMgc3RyaWN0bHkgc3BlYWtpbmcgb3V0IG9mIGNoYXJ0ZXIsIGJlY2F1c2UgaXQgcmVxdWlyZXMg
dGhlIGNyZWF0aW9uIG9mIG5vdCBqdXN0IG5ldyBBUElzIGZvciBUTFMgMS4zIGJ1dCBlc3NlbnRp
YWxseSBhIG5ldyBmb3JtYWwgYW5hbHlzaXMgdGhhdCB0aGUgc2VjdXJpdHkgZ3VhcmFudGVlcyB3
b3JrIHdoZW4gdGhlcmUgaXMgbm8gcmVjb3JkIGxheWVyIGFuZCB3aGVyZSB0aGUgcmVwbGFjZW1l
bnQgaGFzIHNvbWV3aGF0IGRpZmZlcmVudCBmYWNpbGl0aWVzLg0KDQpCdXQgdGhlIGNoYXJ0ZXIg
YWxzbyBzYXlzDQoNCk5vdGUgdGhhdCBjb25zZW5zdXMgaXMgcmVxdWlyZWQgYm90aCBmb3IgY2hh
bmdlcyB0byB0aGUgY3VycmVudA0KcHJvdG9jb2wgbWVjaGFuaXNtcyBhbmQgcmV0ZW50aW9uIG9m
IGN1cnJlbnQgbWVjaGFuaXNtcy4gSW4gcGFydGljdWxhciwNCmJlY2F1c2Ugc29tZXRoaW5nIGlz
IGluIHRoZSBpbml0aWFsIGRvY3VtZW50IHNldCBkb2VzIG5vdCBpbXBseSB0aGF0DQp0aGVyZSBp
cyBjb25zZW5zdXMgYXJvdW5kIHRoZSBmZWF0dXJlIG9yIGFyb3VuZCBob3cgaXQgaXMgc3BlY2lm
aWVkLg0KDQpUaGF0IGFyZ3VlcyB0aGF0IHRoZSBjb21tdW5pdHkgd2FzIHdpbGxpbmcgdG8gc2Vl
IHNlcmlvdXMgY2hhbmdlIGluIGFkb3B0aW5nIHRoaXMgd29yayBhbmQgdGhhdCB0aGlzIHdvcmsg
ZmFsbHMgd2l0aGluIHRoZSBraW5kIG9mIGNoYW5nZSB0aGF0IHdhcyBjb250ZW1wbGF0ZWQsIGV2
ZW4gaWYgaGFwcGVucyB0byBiZSBhY3Jvc3Mgd29ya2luZyBncm91cHMuICBQZXJzb25hbGx5LCBJ
IHRoaW5rIHRoYXQgbWVhbnMgdGhlIGRlc2lnbiBzaG91bGQgYmUgY29uc2lkZXJlZC4NCg0KQnV0
IEkgaGF2ZSBncmF2ZSBjb25jZXJucyBhYm91dCB0aGUgaW1wbGljYXRpb25zLiAgTXkgYmFjayBv
ZiB0aGUgZW52ZWxvcGUgY2FsY3VsYXRpb24gaXMgdGhhdCB0aGlzIG1lYW5zIGF0IGxlYXN0IG9u
ZSBtb3JlIGN5Y2xlIG9mIHNwZWNpZmljYXRpb24gYW5kIGludGVyb3Agd2lsbCBiZSByZXF1aXJl
ZCBiZWZvcmUgd2UgZ2V0IGJhY2sgdG8gd2hlcmUgd2UgYXJlIHdpdGggZHJhZnQgLTExLCBhbmQg
dGhhdCBlc3RpbWF0ZSBpcyBiZWNhdXNlIEknbSBpbiBhIGhvcGVmdWwgbW9vZCB0aGF0IFNlYW4g
YW5kIEVyaWMgY2FuIG1vdmUgdGhlIHJlcXVpcmVkIHdvcmsgaW4gVExTIGFsb25nLiAgQSBtb3Jl
IHByYWN0aWNhbCBUZWQgd291bGQgc2VlIHRoaXMgYXMgYWRkaW5nIGF0IG1pbmltdW0gNiBtb250
aHMgdG8gdGhlIHNjaGVkdWxlLiAgVGhlIGNoYW5nZXMgaW4gVExTIGFyZSBhbHNvIGxhcmdlIGVu
b3VnaCB0aGF0IEkgZXhwZWN0IHRoYXQgdGhlIGRlcGxveW1lbnQgdGltZSB0byBzZWUgc2lnbmlm
aWNhbnQgcGVuZXRyYXRpb24gb2YgdGhlIG5ldyBsaWJyYXJpZXMgdG8gYmUgbG9uZ2VyIHRoYW4g
aXQgd291bGQgYmUgZm9yIHRoZSBwcmV2aW91cyBkZXNpZ24uICAgQ2FsbCBpdCA5IG1vbnRocywg
d2l0aCAzIG1vbnRocyBvZiBlcnJvciBiYXIuDQoNCkR1cmluZyB0aGF0IHRpbWUsIHRoZSBwZW5l
dHJhdGlvbiBvZiBnUVVJQyBvdXRzaWRlIEdvb2dsZSBkb2VzIG5vdCBzZWVtIGxpa2VseSB0byBz
bG93LiAgSWYgeW91IHdhbnQgd2hhdCBRVUlDIGhhcyB0byBvZmZlciBub3csIHlvdSB3aWxsIHRh
a2UgdGhlIGFscmVhZHkgYXZhaWxhYmxlIGNvZGUgYW5kIGdvLiAgRm9yIFdlYiB1c2FnZXMsIHRo
ZXJlIGFyZSBzb21lIGRvd24gc2lkZXMgdG8gdGhhdCwgYW5kIGl0IG1heSBzbG93IHRoZSBldmVu
dHVhbCBkZXBsb3ltZW50IG9mIElFVEYgUVVJQy4NCg0KQnV0IHRoZXJlIGFyZSBhbHNvIGRvd24g
c2lkZXMgdG8gYWxsIG9mIHRoZSBvdGhlciBwcm90b2NvbHMgdGhhdCB3b3VsZCBsaWtlIHRvIHVz
ZSBRVUlDIGJ1dCBoYXZlIGJlZW4gdG9sZCB0byB3YWl0IGZvciB0aGUgY29tcGxldGlvbiBvZiB0
aGlzIGVmZm9ydC4gIFdlJ3JlIGxpa2VseSB0byBzZWUgRE5TIG92ZXIgSFRUUFMgb3ZlciBRVUlD
IGluc3RlYWQgb2YgRE5TIG92ZXIgUVVJQywgc2ltcGx5IGJlY2F1c2UgdGhlIERPSCB0cmFuc3Bv
cnQgZG9jcyB3aWxsIGJlIGRvbmUuICBUaGVyZSBhcmUgc29tZSBhZHZhbnRhZ2VzIHRoZXJlLCBi
dXQgYWxzbyBkaXNhZHZhbnRhZ2VzIGluIGVubWVzaGluZyB0aGUgSFRUUCBhbmQgRE5TIGNhY2hp
bmcgc2VtYW50aWNzLiAgICBUaGVyZSBhcmUgYWxzbyBhIG51bWJlciBvZiBncm91cHMgd2hvIHdh
bnQgdG8gdXNlIFFVSUMgYXMgYSByZXBsYWNlbWVudCBmb3IgdGhlIFdlYlJUQyBkYXRhIGNoYW5u
ZWwgKGFuZCBzb21lIGFzIHRoZSBzdWJzdHJhdGUgZm9yIG1lZGlhKS4gIFRoaXMgYWRkaXRpb25h
bCBkZWxheSB3aWxsIGNlcnRhaW5seSBjYXVzZSBzb21lIGNvZGUgdG8gYmUgd3JpdHRlbiB0aGF0
IHdpbGwgZWl0aGVyIG5lZWQgZXh0ZW5zaXZlIGNoYW5nZSBvciB3aWxsIGJpdCByb3QgKG9yIGZv
cmspLiAgTm9uZSBvZiB0aGF0IGlzIHdpdGhvdXQgY29zdHMsIGVzcGVjaWFsbHkgb3Bwb3J0dW5p
dHkgY29zdHMuDQoNCklmIHRoZSB3b3JraW5nIGdyb3VwIGRvZXMgZGVjaWRlIHRvIGFkb3B0IHRo
aXMgZGVzaWduLCBJIGJlbGlldmUgcGFydCBvZiB0aGUgbWlsZXN0b25lIGFkanVzdG1lbnQgbXVz
dCBiZSBhIHNlcmlvdXMgY29uc2lkZXJhdGlvbiBvZiBkZWxheWluZyB0aGUgcXBhY2sgYW5kIEhU
VFAtc3BlY2lmaWMgd29yayB3aGlsZSB0aGUgY29yZSB0cmFuc3BvcnQgaXMgZmluaXNoZWQuICBU
aGUgZ29vZCBuZXdzLCBJIHRoaW5rIHRoaXMgZGVzaWduIGNvdWxkIGVuZCB1cCBtYWtpbmcgdGhl
IGRvY3VtZW50IHNlcGFyYXRpb24gdGhhdCByZXF1aXJlcyBtdWNoIGNsZWFuZXIsIGFzIHdlbGwg
YXMgbWFraW5nIGhvdyB0byB1c2UgUVVJQyB3aXRoIG90aGVyIGFwcGxpY2F0aW9uIHByb3RvY29s
cyBtdWNoIG1vcmUgb2J2aW91cy4NCg0KTXkgdGhhbmtzIGFnYWluIGZvciBkb2luZyB0aGUgd29y
ayBvZiBicmluZ2luZyB0aGUgZGVzaWduIGZvcndhcmQsDQoNClRlZA0KDQoNCg==

--_000_319424C3524D4F0B853AF824DC3D9F9Dfbcom_
Content-Type: text/html; charset="utf-8"
Content-ID: <72E22379852B1C48961A27AC8417D7EC@namprd15.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1i
b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
IixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9
DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpw
Lm1zb25vcm1hbDAsIGxpLm1zb25vcm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1u
YW1lOm1zb25vcm1hbDsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6
MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBpbjsNCglm
b250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNw
YW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0No
cERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBw
dDt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEu
MGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2Vj
dGlvbjE7fQ0KLS0+PC9zdHlsZT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSIj
MDU2M0MxIiB2bGluaz0iIzk1NEY3MiI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+SeKAmWxsIHNheSBhZ2FpbiB0aGF0IHdlIHNob3VsZCBzdGFydCB3
b3JrIG9uIElFVEYgUVVJQ3YyIG5vdy48YnI+DQpIb3cvd2hlbiBkbyB3ZSBjaGFydGVyIHRoYXQg
d29yaz8gTm90IG9ubHkgZG8gSSB0aGluayB0aGlzIGlzIHRoZSByaWdodCB0aGluZywgSSBzdXNw
ZWN0IGl0IHdpbGwgc3BlZWQgdXAgdGhlIHdvcmsgb24gSUVURiBRVUlDdjE8bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+LT1SPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29s
aWQgI0I1QzRERiAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2NvbG9yOmJsYWNrIj5G
cm9tOiA8L3NwYW4+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2NvbG9yOmJsYWNr
Ij5RVUlDICZsdDtxdWljLWJvdW5jZXNAaWV0Zi5vcmcmZ3Q7IG9uIGJlaGFsZiBvZiBUZWQgSGFy
ZGllICZsdDt0ZWQuaWV0ZkBnbWFpbC5jb20mZ3Q7PGJyPg0KPGI+RGF0ZTogPC9iPldlZG5lc2Rh
eSwgTWF5IDIzLCAyMDE4IGF0IDE6MTcgUE08YnI+DQo8Yj5UbzogPC9iPklFVEYgUVVJQyBXRyAm
bHQ7cXVpY0BpZXRmLm9yZyZndDs8YnI+DQo8Yj5TdWJqZWN0OiA8L2I+SGlnaGVyIGxheWVyIGNv
bW1lbnRzIG9uIHN0cmVhbSAwIHByb3Bvc2FsLCBXRyBzY2hlZHVsZSwgYW5kIGdRVUlDPG86cD48
L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+VGhlIGNoYXJ0ZXIgZm9yIHRoZSB3b3JraW5nIGdyb3VwIGN1cnJlbnRseSBzYXlzOjxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXYgc3R5bGU9Im1hcmdpbi1sZWZ0OjMwLjBwdCI+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGlzIHdvcmsgd2lsbCBkZXNjcmliZSBob3cgdGhlIHBy
b3RvY29sIHVzZXMgVExTIDEuMyBmb3Iga2V5IG5lZ290aWF0aW9uIGFuZCB3aWxsIGFsc28gZGVz
Y3JpYmUgaG93IHRob3NlIGtleXMgYXJlIHVzZWQgdG8gcHJvdmlkZSBjb25maWRlbnRpYWxpdHkg
YW5kIGludGVncml0eSBwcm90ZWN0aW9uIG9mIGJvdGggYXBwbGljYXRpb24gZGF0YSBhbmQgUVVJ
QyBoZWFkZXJzLg0KPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPkl0J3MgZWFzeSB0byByZWFkIHRoYXQgYXMgc2F5aW5nIHRoZSB3b3JrIHNob3Vs
ZCBiZSBjb25zdHJhaW5lZCB0byB1c2UgVExTIDEuLjMgYXMgcHJvdmlkZWQuJm5ic3A7IElmIHdl
IHJlYWQgaXQgdGhhdCB3YXksIHRoZSBkZXNpZ24gdGVhbSBwcm9wb3NhbCBpcyBzdHJpY3RseSBz
cGVha2luZyBvdXQgb2YgY2hhcnRlciwgYmVjYXVzZSBpdCByZXF1aXJlcyB0aGUgY3JlYXRpb24g
b2Ygbm90IGp1c3QgbmV3IEFQSXMgZm9yDQogVExTIDEuMyBidXQgZXNzZW50aWFsbHkgYSBuZXcg
Zm9ybWFsIGFuYWx5c2lzIHRoYXQgdGhlIHNlY3VyaXR5IGd1YXJhbnRlZXMgd29yayB3aGVuIHRo
ZXJlIGlzIG5vIHJlY29yZCBsYXllciBhbmQgd2hlcmUgdGhlIHJlcGxhY2VtZW50IGhhcyBzb21l
d2hhdCBkaWZmZXJlbnQgZmFjaWxpdGllcy4mbmJzcDsNCjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5CdXQgdGhlIGNoYXJ0ZXIgYWxzbyBzYXlz
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzAuMHB0
Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk5vdGUgdGhhdCBjb25zZW5zdXMgaXMgcmVxdWlyZWQg
Ym90aCBmb3IgY2hhbmdlcyB0byB0aGUgY3VycmVudA0KPGJyPg0KcHJvdG9jb2wgbWVjaGFuaXNt
cyBhbmQgcmV0ZW50aW9uIG9mIGN1cnJlbnQgbWVjaGFuaXNtcy4gSW4gcGFydGljdWxhciwgPGJy
Pg0KYmVjYXVzZSBzb21ldGhpbmcgaXMgaW4gdGhlIGluaXRpYWwgZG9jdW1lbnQgc2V0IGRvZXMg
bm90IGltcGx5IHRoYXQgPGJyPg0KdGhlcmUgaXMgY29uc2Vuc3VzIGFyb3VuZCB0aGUgZmVhdHVy
ZSBvciBhcm91bmQgaG93IGl0IGlzIHNwZWNpZmllZC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzAuMHB0Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
VGhhdCBhcmd1ZXMgdGhhdCB0aGUgY29tbXVuaXR5IHdhcyB3aWxsaW5nIHRvIHNlZSBzZXJpb3Vz
IGNoYW5nZSBpbiBhZG9wdGluZyB0aGlzIHdvcmsgYW5kIHRoYXQgdGhpcyB3b3JrIGZhbGxzIHdp
dGhpbiB0aGUga2luZCBvZiBjaGFuZ2UgdGhhdCB3YXMgY29udGVtcGxhdGVkLCBldmVuIGlmIGhh
cHBlbnMgdG8gYmUgYWNyb3NzIHdvcmtpbmcgZ3JvdXBzLiZuYnNwOyBQZXJzb25hbGx5LCBJIHRo
aW5rIHRoYXQgbWVhbnMNCiB0aGUgZGVzaWduIHNob3VsZCBiZSBjb25zaWRlcmVkLjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5CdXQgSSBoYXZl
IGdyYXZlIGNvbmNlcm5zIGFib3V0IHRoZSBpbXBsaWNhdGlvbnMuJm5ic3A7IE15IGJhY2sgb2Yg
dGhlIGVudmVsb3BlIGNhbGN1bGF0aW9uIGlzIHRoYXQgdGhpcyBtZWFucyBhdCBsZWFzdCBvbmUg
bW9yZSBjeWNsZSBvZiBzcGVjaWZpY2F0aW9uIGFuZCBpbnRlcm9wIHdpbGwgYmUgcmVxdWlyZWQg
YmVmb3JlIHdlIGdldCBiYWNrIHRvIHdoZXJlIHdlIGFyZSB3aXRoIGRyYWZ0IC0xMSwgYW5kIHRo
YXQNCiBlc3RpbWF0ZSBpcyBiZWNhdXNlIEknbSBpbiBhIGhvcGVmdWwgbW9vZCB0aGF0IFNlYW4g
YW5kIEVyaWMgY2FuIG1vdmUgdGhlIHJlcXVpcmVkIHdvcmsgaW4gVExTIGFsb25nLiZuYnNwOyBB
IG1vcmUgcHJhY3RpY2FsIFRlZCB3b3VsZCBzZWUgdGhpcyBhcyBhZGRpbmcgYXQgbWluaW11bSA2
IG1vbnRocyB0byB0aGUgc2NoZWR1bGUuJm5ic3A7IFRoZSBjaGFuZ2VzIGluIFRMUyBhcmUgYWxz
byBsYXJnZSBlbm91Z2ggdGhhdCBJIGV4cGVjdCB0aGF0IHRoZSBkZXBsb3ltZW50DQogdGltZSB0
byBzZWUgc2lnbmlmaWNhbnQgcGVuZXRyYXRpb24gb2YgdGhlIG5ldyBsaWJyYXJpZXMgdG8gYmUg
bG9uZ2VyIHRoYW4gaXQgd291bGQgYmUgZm9yIHRoZSBwcmV2aW91cyBkZXNpZ24uJm5ic3A7Jm5i
c3A7IENhbGwgaXQgOSBtb250aHMsIHdpdGggMyBtb250aHMgb2YgZXJyb3IgYmFyLjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5EdXJpbmcgdGhh
dCB0aW1lLCB0aGUgcGVuZXRyYXRpb24gb2YgZ1FVSUMgb3V0c2lkZSBHb29nbGUgZG9lcyBub3Qg
c2VlbSBsaWtlbHkgdG8gc2xvdy4mbmJzcDsgSWYgeW91IHdhbnQgd2hhdCBRVUlDIGhhcyB0byBv
ZmZlciBub3csIHlvdSB3aWxsIHRha2UgdGhlIGFscmVhZHkgYXZhaWxhYmxlIGNvZGUgYW5kIGdv
LiZuYnNwOyBGb3IgV2ViIHVzYWdlcywgdGhlcmUgYXJlIHNvbWUgZG93biBzaWRlcyB0byB0aGF0
LCBhbmQgaXQNCiBtYXkgc2xvdyB0aGUgZXZlbnR1YWwgZGVwbG95bWVudCBvZiBJRVRGIFFVSUMu
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkJ1
dCB0aGVyZSBhcmUgYWxzbyBkb3duIHNpZGVzIHRvIGFsbCBvZiB0aGUgb3RoZXIgcHJvdG9jb2xz
IHRoYXQgd291bGQgbGlrZSB0byB1c2UgUVVJQyBidXQgaGF2ZSBiZWVuIHRvbGQgdG8gd2FpdCBm
b3IgdGhlIGNvbXBsZXRpb24gb2YgdGhpcyBlZmZvcnQuJm5ic3A7IFdlJ3JlIGxpa2VseSB0byBz
ZWUgRE5TIG92ZXIgSFRUUFMgb3ZlciBRVUlDIGluc3RlYWQgb2YgRE5TIG92ZXIgUVVJQywgc2lt
cGx5IGJlY2F1c2UNCiB0aGUgRE9IIHRyYW5zcG9ydCBkb2NzIHdpbGwgYmUgZG9uZS4mbmJzcDsg
VGhlcmUgYXJlIHNvbWUgYWR2YW50YWdlcyB0aGVyZSwgYnV0IGFsc28gZGlzYWR2YW50YWdlcyBp
biBlbm1lc2hpbmcgdGhlIEhUVFAgYW5kIEROUyBjYWNoaW5nIHNlbWFudGljcy4mbmJzcDsmbmJz
cDsmbmJzcDsgVGhlcmUgYXJlIGFsc28gYSBudW1iZXIgb2YgZ3JvdXBzIHdobyB3YW50IHRvIHVz
ZSBRVUlDIGFzIGEgcmVwbGFjZW1lbnQgZm9yIHRoZSBXZWJSVEMgZGF0YSBjaGFubmVsIChhbmQg
c29tZQ0KIGFzIHRoZSBzdWJzdHJhdGUgZm9yIG1lZGlhKS4mbmJzcDsgVGhpcyBhZGRpdGlvbmFs
IGRlbGF5IHdpbGwgY2VydGFpbmx5IGNhdXNlIHNvbWUgY29kZSB0byBiZSB3cml0dGVuIHRoYXQg
d2lsbCBlaXRoZXIgbmVlZCBleHRlbnNpdmUgY2hhbmdlIG9yIHdpbGwgYml0IHJvdCAob3IgZm9y
aykuJm5ic3A7IE5vbmUgb2YgdGhhdCBpcyB3aXRob3V0IGNvc3RzLCBlc3BlY2lhbGx5IG9wcG9y
dHVuaXR5IGNvc3RzLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5JZiB0aGUgd29ya2luZyBncm91cCBkb2VzIGRlY2lkZSB0byBhZG9wdCB0aGlz
IGRlc2lnbiwgSSBiZWxpZXZlIHBhcnQgb2YgdGhlIG1pbGVzdG9uZSBhZGp1c3RtZW50IG11c3Qg
YmUgYSBzZXJpb3VzIGNvbnNpZGVyYXRpb24gb2YgZGVsYXlpbmcgdGhlIHFwYWNrIGFuZCBIVFRQ
LXNwZWNpZmljIHdvcmsgd2hpbGUgdGhlIGNvcmUgdHJhbnNwb3J0IGlzIGZpbmlzaGVkLiZuYnNw
OyBUaGUgZ29vZCBuZXdzLCBJIHRoaW5rDQogdGhpcyBkZXNpZ24gY291bGQgZW5kIHVwIG1ha2lu
ZyB0aGUgZG9jdW1lbnQgc2VwYXJhdGlvbiB0aGF0IHJlcXVpcmVzIG11Y2ggY2xlYW5lciwgYXMg
d2VsbCBhcyBtYWtpbmcgaG93IHRvIHVzZSBRVUlDIHdpdGggb3RoZXIgYXBwbGljYXRpb24gcHJv
dG9jb2xzIG11Y2ggbW9yZSBvYnZpb3VzLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5NeSB0aGFua3MgYWdhaW4gZm9yIGRvaW5nIHRoZSB3b3Jr
IG9mIGJyaW5naW5nIHRoZSBkZXNpZ24gZm9yd2FyZCw8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGVkPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_319424C3524D4F0B853AF824DC3D9F9Dfbcom_--


From nobody Wed May 23 13:51:08 2018
Return-Path: <pmcmanus@mozilla.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C6E7412D7F0 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 13:51:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level: 
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 rrIr-L4I62Fr for <quic@ietfa.amsl.com>; Wed, 23 May 2018 13:51:00 -0700 (PDT)
Received: from linode64.ducksong.com (linode6only.ducksong.com [IPv6:2600:3c02::f03c:91ff:fe6e:e8da]) by ietfa.amsl.com (Postfix) with ESMTP id EBCD7127010 for <quic@ietf.org>; Wed, 23 May 2018 13:50:59 -0700 (PDT)
Received: from mail-ot0-f171.google.com (mail-ot0-f171.google.com [74.125.82.171]) by linode64.ducksong.com (Postfix) with ESMTPSA id BDFC63A043 for <quic@ietf.org>; Wed, 23 May 2018 16:50:58 -0400 (EDT)
Received: by mail-ot0-f171.google.com with SMTP id 77-v6so26854531otd.4 for <quic@ietf.org>; Wed, 23 May 2018 13:50:58 -0700 (PDT)
X-Gm-Message-State: ALKqPwcWqRdUjC9wZ+5H4KGjNJnwByNSU/5b4BWksgq59ayDKpcAAEw5 oal1rvCqAU5aIwCvrMEvETWCP4+bXdACihHKVBk=
X-Google-Smtp-Source: AB8JxZoVZ9bsiIr1SWtmOfOnHoD+tu+2peG/XIJIgUxHHIoaGqdm/PNADBRYAW7nIp5AIfJsj0M2SegXVtOYPUCum8o=
X-Received: by 2002:a9d:1ba8:: with SMTP id z37-v6mr2984885otd.85.1527108658429;  Wed, 23 May 2018 13:50:58 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:8a24:0:0:0:0:0 with HTTP; Wed, 23 May 2018 13:50:57 -0700 (PDT)
In-Reply-To: <CA+9kkMA0QnSmvbGOktngU+B-eC7CJFXLicEZfxQga6m6Z+gJLQ@mail.gmail.com>
References: <CA+9kkMA0QnSmvbGOktngU+B-eC7CJFXLicEZfxQga6m6Z+gJLQ@mail.gmail.com>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Wed, 23 May 2018 16:50:57 -0400
X-Gmail-Original-Message-ID: <CAOdDvNrx4vUBvZe6QpO9cYyAjVYCo95EC6dWmp-+tU8BCbbZ7A@mail.gmail.com>
Message-ID: <CAOdDvNrx4vUBvZe6QpO9cYyAjVYCo95EC6dWmp-+tU8BCbbZ7A@mail.gmail.com>
Subject: Re: Higher layer comments on stream 0 proposal, WG schedule, and gQUIC
To: Ted Hardie <ted.ietf@gmail.com>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001e889b056ce5b167"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2NdS6NjN2qwFqcLwXoqJAk72jo4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 20:51:04 -0000

--0000000000001e889b056ce5b167
Content-Type: text/plain; charset="UTF-8"

Schedule needs to be part of this conversation - it certainly was within
the design team. But its not the initial (or solely determinative)
question, in my mind.

At the end of the DT process the group had consensus that it was more
important to get it right with reasonable cost instead of constraining
ourselves to near zero cost. The output reflects that.

In particular the proposal does a nice job of sorting out the issues of
encryption level (which is a terrible problem with stream 0 and the
associated acks) while still maintaining a unified reliability layer.
That's a pretty neat trick and a tough circle to square.

There was a bit of a personal journey on this as well for me (it may have
helped to have internalized an entire potential shift to DTLS first before
settling on this much more modest approach). I would encourage you to get
comfortable with the details, and lets all have a discussion of the merits
instead of jumping ahead to the cost benefit discussion (I'm not suggesting
eliding that discussion entirely - shipping is a feature, and we should
balance all the features as we've done in the past.). As the details start
to come together it actually feels less ambitious - just a reasonable
ordering of things really that solves a number of very practical issues
we've shown during our running code exercises. It just looks at the
boundaries between security/application/transport in a novel way.. which is
just a synonym for the QUIC WG :)

That's my experience anyhow.

Personally, I've been reassured that the owners of a number of TLS stacks
embraced this approach so eagerly, as a significant amount of the burden
falls on them. There will, as always, be laggards and trailblazers on that
front.. as long as there are existence proofs that it can be done
reasonably I wouldn't let the competitive details of which libraries are at
what stage tell us too much about what is right for the protocol we're
building.

-P



On Wed, May 23, 2018 at 4:16 PM, Ted Hardie <ted.ietf@gmail.com> wrote:

> The charter for the working group currently says:
>
> This work will describe how the protocol uses TLS 1.3 for key negotiation
> and will also describe how those keys are used to provide confidentiality
> and integrity protection of both application data and QUIC headers.
>
> It's easy to read that as saying the work should be constrained to use TLS
> 1..3 as provided.  If we read it that way, the design team proposal is
> strictly speaking out of charter, because it requires the creation of not
> just new APIs for TLS 1.3 but essentially a new formal analysis that the
> security guarantees work when there is no record layer and where the
> replacement has somewhat different facilities.
>
> But the charter also says
>
> Note that consensus is required both for changes to the current
> protocol mechanisms and retention of current mechanisms. In particular,
> because something is in the initial document set does not imply that
> there is consensus around the feature or around how it is specified.
>
> That argues that the community was willing to see serious change in
> adopting this work and that this work falls within the kind of change that
> was contemplated, even if happens to be across working groups.  Personally,
> I think that means the design should be considered.
>
> But I have grave concerns about the implications.  My back of the envelope
> calculation is that this means at least one more cycle of specification and
> interop will be required before we get back to where we are with draft -11,
> and that estimate is because I'm in a hopeful mood that Sean and Eric can
> move the required work in TLS along.  A more practical Ted would see this
> as adding at minimum 6 months to the schedule.  The changes in TLS are also
> large enough that I expect that the deployment time to see significant
> penetration of the new libraries to be longer than it would be for the
> previous design.   Call it 9 months, with 3 months of error bar.
>
> During that time, the penetration of gQUIC outside Google does not seem
> likely to slow.  If you want what QUIC has to offer now, you will take the
> already available code and go.  For Web usages, there are some down sides
> to that, and it may slow the eventual deployment of IETF QUIC.
>
> But there are also down sides to all of the other protocols that would
> like to use QUIC but have been told to wait for the completion of this
> effort.  We're likely to see DNS over HTTPS over QUIC instead of DNS over
> QUIC, simply because the DOH transport docs will be done.  There are some
> advantages there, but also disadvantages in enmeshing the HTTP and DNS
> caching semantics.    There are also a number of groups who want to use
> QUIC as a replacement for the WebRTC data channel (and some as the
> substrate for media).  This additional delay will certainly cause some code
> to be written that will either need extensive change or will bit rot (or
> fork).  None of that is without costs, especially opportunity costs.
>
> If the working group does decide to adopt this design, I believe part of
> the milestone adjustment must be a serious consideration of delaying the
> qpack and HTTP-specific work while the core transport is finished.  The
> good news, I think this design could end up making the document separation
> that requires much cleaner, as well as making how to use QUIC with other
> application protocols much more obvious.
>
> My thanks again for doing the work of bringing the design forward,
>
> Ted
>
>
>

--0000000000001e889b056ce5b167
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div></div><div>Schedule needs to be part of this conversa=
tion - it certainly was within the design team. But its not the initial (or=
 solely determinative) question, in my mind.<br></div><div><br></div><div>A=
t the end of the DT process the group had consensus that it was more import=
ant to get it right with reasonable cost instead of constraining ourselves =
to near zero cost. The output reflects that.<br></div><div><br></div><div>I=
n particular the proposal does a nice job of sorting out the issues of encr=
yption
 level (which is a terrible problem with stream 0 and the associated=20
acks) while still maintaining a unified reliability layer. That&#39;s a=20
pretty neat trick and a tough circle to square.<br></div><div><br></div><di=
v>There was a bit of a personal journey on this as well for me (it may have=
 helped to have internalized an entire potential shift to DTLS first before=
 settling on this much more modest approach). I would encourage you to get =
comfortable with the details, and lets all have a discussion of the merits =
instead of jumping ahead to the cost benefit discussion (I&#39;m not sugges=
ting eliding that discussion entirely - shipping is a feature, and we shoul=
d balance all the features as we&#39;ve done in the past.). As the details =
start to come together it actually feels less ambitious - just a reasonable=
 ordering of things really that solves a number of very practical issues we=
&#39;ve shown during our running code exercises. It just looks at the bound=
aries between security/application/transport in a novel way.. which is just=
 a synonym for the QUIC WG :)<br></div><div><br></div><div>That&#39;s my ex=
perience anyhow.<br></div><div></div><div><br></div><div>Personally, I&#39;=
ve been reassured that the owners of a number of TLS stacks embraced this a=
pproach so eagerly, as a significant amount of the burden falls on them. Th=
ere will, as always, be laggards and trailblazers on that front.. as long a=
s there are existence proofs that it can be done reasonably I wouldn&#39;t =
let the competitive details of which libraries are at what stage tell us to=
o much about what is right for the protocol we&#39;re building.</div><div><=
br></div><div>-P</div><div><br></div><div><br></div></div><div class=3D"gma=
il_extra"><br><div class=3D"gmail_quote">On Wed, May 23, 2018 at 4:16 PM, T=
ed Hardie <span dir=3D"ltr">&lt;<a href=3D"mailto:ted.ietf@gmail.com" targe=
t=3D"_blank">ted.ietf@gmail.com</a>&gt;</span> wrote:<br><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div dir=3D"ltr"><div>The charter for the working group curre=
ntly says:</div><div><br></div><div style=3D"margin-left:40px">This work wi=
ll describe how the protocol uses TLS 1.3 for key negotiation and will also=
 describe how those keys are used to provide confidentiality and integrity =
protection of both application data and QUIC headers. <br></div><div><br></=
div><div>It&#39;s easy to read that as saying the work should be constraine=
d to use TLS 1..3 as provided.=C2=A0 If we read it that way, the design tea=
m proposal is strictly speaking out of charter, because it requires the cre=
ation of not just new APIs for TLS 1.3 but essentially a new formal analysi=
s that the security guarantees work when there is no record layer and where=
 the replacement has somewhat different facilities.=C2=A0 <br></div><div><b=
r></div><div>But the charter also says<br></div><div><br></div><div style=
=3D"margin-left:40px">Note that consensus is required both for changes to t=
he current <br>protocol mechanisms and retention of current mechanisms. In =
particular, <br>because something is in the initial document set does not i=
mply that <br>there is consensus around the feature or around how it is spe=
cified.</div><div style=3D"margin-left:40px"><br></div><div>That argues tha=
t the community was willing to see serious change in adopting this work and=
 that this work falls within the kind of change that was contemplated, even=
 if happens to be across working groups.=C2=A0 Personally, I think that mea=
ns the design should be considered.</div><div><br></div><div>But I have gra=
ve concerns about the implications.=C2=A0 My back of the envelope calculati=
on is that this means at least one more cycle of specification and interop =
will be required before we get back to where we are with draft -11, and tha=
t estimate is because I&#39;m in a hopeful mood that Sean and Eric can move=
 the required work in TLS along.=C2=A0 A more practical Ted would see this =
as adding at minimum 6 months to the schedule.=C2=A0 The changes in TLS are=
 also large enough that I expect that the deployment time to see significan=
t penetration of the new libraries to be longer than it would be for the pr=
evious design.=C2=A0=C2=A0 Call it 9 months, with 3 months of error bar.</d=
iv><div><br></div><div>During that time, the penetration of gQUIC outside G=
oogle does not seem likely to slow.=C2=A0 If you want what QUIC has to offe=
r now, you will take the already available code and go.=C2=A0 For Web usage=
s, there are some down sides to that, and it may slow the eventual deployme=
nt of IETF QUIC.<br></div><div><br></div><div>But there are also down sides=
 to all of the other protocols that would like to use QUIC but have been to=
ld to wait for the completion of this effort.=C2=A0 We&#39;re likely to see=
 DNS over HTTPS over QUIC instead of DNS over QUIC, simply because the DOH =
transport docs will be done.=C2=A0 There are some advantages there, but als=
o disadvantages in enmeshing the HTTP and DNS caching semantics.=C2=A0=C2=
=A0=C2=A0 There are also a number of groups who want to use QUIC as a repla=
cement for the WebRTC data channel (and some as the substrate for media).=
=C2=A0 This additional delay will certainly cause some code to be written t=
hat will either need extensive change or will bit rot (or fork).=C2=A0 None=
 of that is without costs, especially opportunity costs.</div><div><br></di=
v><div>If the working group does decide to adopt this design, I believe par=
t of the milestone adjustment must be a serious consideration of delaying t=
he qpack and HTTP-specific work while the core transport is finished.=C2=A0=
 The good news, I think this design could end up making the document separa=
tion that requires much cleaner, as well as making how to use QUIC with oth=
er application protocols much more obvious.</div><div><br></div><div>My tha=
nks again for doing the work of bringing the design forward,</div><div><br>=
</div><div>Ted<br></div><div><br></div><div><br></div></div>
</blockquote></div><br></div>

--0000000000001e889b056ce5b167--


From nobody Wed May 23 14:00:53 2018
Return-Path: <ted.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 18874129C51 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 14:00:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level: 
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 vmrMuHlszxjM for <quic@ietfa.amsl.com>; Wed, 23 May 2018 14:00:48 -0700 (PDT)
Received: from mail-ot0-x22b.google.com (mail-ot0-x22b.google.com [IPv6:2607:f8b0:4003:c0f::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2CD70127010 for <quic@ietf.org>; Wed, 23 May 2018 14:00:48 -0700 (PDT)
Received: by mail-ot0-x22b.google.com with SMTP id 77-v6so26885197otd.4 for <quic@ietf.org>; Wed, 23 May 2018 14:00:48 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=5gf4Sj9VzpQDVG7KVhv4a/QZZUZRnrUEbChqwQrbBk0=; b=RfvJbWNsfRdHWYVbGbzDxYnaZaIlHdpExa5sVNioXmzo1/ykx2ANJBgLDU1H7NMaRX Nrn/uUj8/tiJHAO0llBcxAg5fKm4kLiWG+W3xzXYxkTOpesrJUZ0Q2gWjaJB4lzkCMFR 3fSIKGgaL50vQezOfwRySaBvlbihPsQnKIlXQFccnjME3gYvVRWWQtp4IeWasJKdTPPF lRqTamxAb4hFALj/iJh/hFVijDZylD3pMDWyt240DFR27TSztu+rzem9ODiIZ+ONq9Kn nJcItSJVwvM73rWn4O1vfgzYoVRpws2ONNnc+hSlmCBG/v+iVh+Yb8wkucX8/AM571r0 ZRMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=5gf4Sj9VzpQDVG7KVhv4a/QZZUZRnrUEbChqwQrbBk0=; b=rca9LV7HY1+cbpfu4G7BQWVgskrK4CwV6JTSCSCpT39iPYt1tVZUO4QScOrnO7bwdT CRJgQ+hCfePEB3kuQOAwq66G7qMTbAladI3h2M/9Bg6gLdlUJaZYV5+djpaTECDIKjDW YtUd89vbJuUtL9TtEvq8TVI1vKhKEnbf8A8GZ7TtHSVcIisV+fNnamA460Lwdy9G4enc mAntHwx4T0jMBmMHRVyjCLk7LB0PMUqXDZQoJXCSicPaq3QLNwB1240r8JuVa8ApiznX 3o/blAKlBEK5AUruH9okNMcusLAG5EAPiL6+uJRIr0b+ARSwwJbfuF4V/zd3CsJIR+bO LFzw==
X-Gm-Message-State: ALKqPwfY13SuUBzWWmicYweWNjO4hpqJ9UBZvrj2aWhqquxggMtoNXJ+ P1t8DTxW9/woTBmohvve6FhH4fiexHE9CPcVt9I=
X-Google-Smtp-Source: AB8JxZrx/En9qizNq2XxFTYeOZddbIpreyUWghLWzRRPu+5qvT9ms6l2JfFSq7usGwrXIxbY+bzuTDHPkyBcG0YmhLo=
X-Received: by 2002:a9d:25c6:: with SMTP id q64-v6mr3010252ota.193.1527109245456;  Wed, 23 May 2018 14:00:45 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:4399:0:0:0:0:0 with HTTP; Wed, 23 May 2018 14:00:14 -0700 (PDT)
In-Reply-To: <CABcZeBP-BWwVAbPuT8rT12pMoNpWhD0qdOLB=-Lj=qrRrwq3ag@mail.gmail.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CA+9kkMC0a+HELyVvh+DtvkiorWmKkUQ346zt49Xfyd1zzZ780Q@mail.gmail.com> <CABcZeBP-BWwVAbPuT8rT12pMoNpWhD0qdOLB=-Lj=qrRrwq3ag@mail.gmail.com>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 23 May 2018 14:00:14 -0700
Message-ID: <CA+9kkMDiV8MHGSF1Uz0+mA5n12+tb-vcJzPSX1J8gPb-mmNXCw@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: Eric Rescorla <ekr@rtfm.com>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Eric Rescorla <ekr@mozilla.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001bd744056ce5d4b6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ef6Yz2LG31E_AwRaUXZFYoJ7AlY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 21:00:51 -0000

--0000000000001bd744056ce5d4b6
Content-Type: text/plain; charset="UTF-8"

On Wed, May 23, 2018 at 1:23 PM, Eric Rescorla <ekr@rtfm.com> wrote:

>
>
> On Wed, May 23, 2018 at 12:42 PM, Ted Hardie <ted.ietf@gmail.com> wrote:
>
>> Howdy,
>>
>> Thanks for sharing the document.  I have a couple of detailed comments,
>> and then some high level comments which I will put into a separate email.
>>
>> First, the document says this:
>>
>> Though proper analysis is needed, it is not likely that the removal of
>> the TLS record layer will cause a security concern, because the security
>> properties provided by QUIC packets are identical to what have been
>> provided by TLS records.
>>
>>
>> I'm not sure that this is actually the statement we need to analyze,
>> though. We need to be sure that the security properties of TLS records used
>> in TCP packets are available in QUIC streams in QUIC packets using UDP as a
>> multiplexing layer. There appear to be some difference in where the
>> facilities the overall system provides that may require more description.
>> As an example, I think the way padding works in this proposal needs more
>> description. If I understand correctly, each TLS record is encrypted
>> separately and the presence or absence of padding is indicated by a
>> padding_length byte present in each record. That means the padding is
>> related to the record, not the packet; by removing the record layer and
>> using QUIC frames, though, we seem to have a different padding structure.
>> QUIC uses padding frames, not padding within other frame types which is
>> both conceptually and practically different.
>>
>
> I believe you have misunderstood. In this document, there are no TLS
> records and TLS handshake messages are carried in CRYPTO_HS frames.
> Accordingly, padding is provided in the same fashion as QUIC ordinarily
> does, i.e., using PADDING frames.
>
> That's what I understood from the design document.  The point I'm making
is that this actually a substantive change to the padding structure that
was previously present (in TLS records), and the security analysis has to
take that into account, so it (and similar things) should be described.

Similarly, I'd be interested in more text on the interaction with
> precedence, since the loss of the record layer means that the former
> guarantee that the record layer makes records available in the order in
> which they were protected now seems to be unavailable.
>

I'm not quite sure I follow what you are asking about here. In both cases,
TLS sits on top of QUIC's reliable in-order deliver guarantees. Is the
point you are making that formerly, if QUIC violated these guarantees, that
would result in TLS handshake failure, whereas now it does not?

This just related to the general point I was making above.  When the design
shifts where it was getting a function, it would be helpful if it called it
out more directly, to facilitate the analysis.

regards,

Ted

-Ekr
>
>
>
>> regards,
>>
>>
>> Ted
>>
>>
>>
>>
>>
>> On Tue, May 22, 2018 at 6:30 PM, Ian Swett <ianswett=40google.com@dmarc.i
>> etf.org> wrote:
>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> *Dear QUIC WG,On behalf of the Stream 0 Design Team, I am pleased to
>>> report that we have consensus on a proposed approach to share with the WG.
>>> The DT's proposal will make QUIC and TLS work closer together and
>>> incorporates ideas from DTLS, but it does not use the DTLS protocol itself.
>>> The DT believes this solves the important open Stream 0 issues. The
>>> proposal will be a bit more invasive in TLS, but we believe it is the right
>>> long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and
>>> Mint) are willing and able to do the work necessary.. A number of stacks
>>> are currently working on implementations of this new approach, which we
>>> hope to have in time for the Interim meeting.A design document describing
>>> the overall approach can be found
>>> at:https://docs.google..com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit
>>> <https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit>A
>>> PR making the changes to the QUIC documents can be found
>>> at:https://github.com/quicwg/base-drafts/pull/1377
>>> <https://github.com/ekr/base-drafts/pull/29>A few design details did not
>>> have clear consensus, but it was felt it would be better to discuss those
>>> in the wider WG than delay the design team.  A consistent choice was made
>>> in the PR and these issues are mentioned in Appendix B of the design doc.As
>>> always, comments and questions welcome. That said, this is a big PR and we
>>> recognize that some editorial work is going to be needed before merging. In
>>> the interest of letting people follow along, and to keep github from
>>> falling over, we ask people to keep discussion on the mailing list and
>>> refrain from making PR comments.See you in Kista!*
>>> Ian and Eric
>>>
>>
>>
>

--0000000000001bd744056ce5d4b6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra">On Wed, May 23, 2018 at 1:2=
3 PM, Eric Rescorla <span dir=3D"ltr">&lt;<a href=3D"mailto:ekr@rtfm.com" t=
arget=3D"_blank">ekr@rtfm.com</a>&gt;</span> wrote:<br><div class=3D"gmail_=
quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><br><div class=3D"gm=
ail_extra"><br><div class=3D"gmail_quote"><span class=3D"">On Wed, May 23, =
2018 at 12:42 PM, Ted Hardie <span dir=3D"ltr">&lt;<a href=3D"mailto:ted.ie=
tf@gmail.com" target=3D"_blank">ted.ietf@gmail.com</a>&gt;</span> wrote:<br=
><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1=
px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>Howdy,</div><div><br>=
</div><div>Thanks for sharing the document.=C2=A0 I have a couple of detail=
ed comments, and then some high level comments which I will put into a sepa=
rate email.</div><div><br></div><div>First, the document says this:</div><d=
iv><br></div><div><p style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt;text-align:justify;margin-left:40px" id=3D"m_7659979686296042694m_-791=
9340867003085784gmail-docs-internal-guid-ae9978f1-8e74-9194-2b6b-f4000bc3b5=
41"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);backgr=
ound-color:transparent;font-weight:400;font-style:normal;font-variant:norma=
l;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Though=
 proper analysis is needed, it is not likely that the removal of the TLS re=
cord layer will cause a security concern, because the security properties p=
rovided by QUIC packets are identical to what have been provided by TLS rec=
ords.</span></p><p style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0=
pt;text-align:justify"><span style=3D"font-size:11pt;font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal=
;font-variant:normal;text-decoration:none;vertical-align:baseline;white-spa=
ce:pre-wrap"><br></span></p><p style=3D"line-height:1.38;margin-top:0pt;mar=
gin-bottom:0pt;text-align:justify"><span style=3D"font-size:11pt;font-famil=
y:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-=
style:normal;font-variant:normal;text-decoration:none;vertical-align:baseli=
ne;white-space:pre-wrap">I&#39;m not sure that this is actually the stateme=
nt we need to analyze, though.  We need to be sure that the security proper=
ties of TLS records used in TCP packets are available in QUIC streams in QU=
IC packets using UDP as a multiplexing layer.  There appear to be some diff=
erence in where the facilities the overall system provides that may require=
 more description.  As an example, I think the way padding works in this pr=
oposal needs more description.  If I understand correctly, each TLS record =
is encrypted separately and the presence or absence of padding is indicated=
 by a padding_length byte present in each record.  That means the padding i=
s related to the record, not the packet; by removing the record layer and u=
sing QUIC frames, though, we seem to have a different padding structure.  Q=
UIC uses padding frames, not padding within other frame types which is both=
 conceptually and practically different.  </span></p></div></div></blockquo=
te><div><br></div></span><div>I believe you have misunderstood. In this doc=
ument, there are no TLS records and TLS handshake messages are carried in C=
RYPTO_HS frames. Accordingly, padding is provided in the same fashion as QU=
IC ordinarily does, i.e., using PADDING frames.<br></div><span class=3D""><=
div><br></div></span></div></div></div></blockquote><div class=3D"gmail_quo=
te">That&#39;s what I understood from the design document.=C2=A0 The point =
I&#39;m making is that this actually a substantive change to the padding st=
ructure that was previously present (in TLS records), and the security anal=
ysis has to take that into account, so it (and similar things) should be de=
scribed.</div><div class=3D"gmail_quote"><br><span class=3D""><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;=
padding-left:1ex"><div dir=3D"ltr"><div><p style=3D"line-height:1.38;margin=
-top:0pt;margin-bottom:0pt;text-align:justify"><span style=3D"font-size:11p=
t;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weig=
ht:400;font-style:normal;font-variant:normal;text-decoration:none;vertical-=
align:baseline;white-space:pre-wrap">Similarly, I&#39;d be interested in mo=
re text on the interaction with precedence, since the loss of the record la=
yer means that the former guarantee that the record layer makes records ava=
ilable in the order in which they were protected now seems to be unavailabl=
e.<br></span></p></div></div></blockquote><div><br></div></span><div>I&#39;=
m not quite sure I follow what you are asking about here. In both cases, TL=
S sits on top of QUIC&#39;s reliable in-order deliver guarantees. Is the po=
int you are making that formerly, if QUIC violated these guarantees, that w=
ould result in TLS handshake failure, whereas now it does not?<br></div></d=
iv><div class=3D"gmail_quote"><br></div><div class=3D"gmail_quote">This jus=
t related to the general point I was making above.=C2=A0 When the design sh=
ifts where it was getting a function, it would be helpful if it called it o=
ut more directly, to facilitate the analysis. <br></div><div class=3D"gmail=
_quote"><br></div><div class=3D"gmail_quote">regards,</div><div class=3D"gm=
ail_quote"><br></div><div class=3D"gmail_quote">Ted<br></div><div class=3D"=
gmail_quote"><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 =
0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div=
 class=3D"gmail_extra"><div class=3D"gmail_quote">-Ekr</div><div class=3D"g=
mail_quote"><br></div><div class=3D"gmail_quote"><div><br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc soli=
d;padding-left:1ex"><div dir=3D"ltr"><div><p style=3D"line-height:1.38;marg=
in-top:0pt;margin-bottom:0pt;text-align:justify"><span style=3D"font-size:1=
1pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-we=
ight:400;font-style:normal;font-variant:normal;text-decoration:none;vertica=
l-align:baseline;white-space:pre-wrap"><br></span></p><p style=3D"line-heig=
ht:1.38;margin-top:0pt;margin-bottom:0pt;text-align:justify"><span style=3D=
"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transpa=
rent;font-weight:400;font-style:normal;font-variant:normal;text-decoration:=
none;vertical-align:baseline;white-space:pre-wrap">regards,</span></p><p st=
yle=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;text-align:justify=
"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);backgrou=
nd-color:transparent;font-weight:400;font-style:normal;font-variant:normal;=
text-decoration:none;vertical-align:baseline;white-space:pre-wrap"><br></sp=
an></p><p style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;text-a=
lign:justify"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0=
,0);background-color:transparent;font-weight:400;font-style:normal;font-var=
iant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wr=
ap">Ted<br></span></p><p style=3D"line-height:1.38;margin-top:0pt;margin-bo=
ttom:0pt;text-align:justify"><span style=3D"font-size:11pt;font-family:Aria=
l;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:=
normal;font-variant:normal;text-decoration:none;vertical-align:baseline;whi=
te-space:pre-wrap"></span></p><pre><br></pre><br><p></p><br></div></div><di=
v class=3D"gmail_extra"><br><div class=3D"gmail_quote"><span class=3D""><sp=
an>On Tue, May 22, 2018 at 6:30 PM, Ian Swett <span dir=3D"ltr">&lt;<a href=
=3D"mailto:ianswett=3D40google.com@dmarc.ietf.org" target=3D"_blank">ianswe=
tt=3D40google.com@dmarc.i<wbr>etf.org</a>&gt;</span> wrote:<br></span></spa=
n><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><b style=3D"font-weight:n=
ormal" id=3D"m_7659979686296042694m_-7919340867003085784m_-1851091610820382=
769gmail-docs-internal-guid-2a62f340-8a8f-9073-5cad-25b8001e52b3"><span cla=
ss=3D""><span><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margi=
n-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0=
,0);background-color:transparent;font-weight:400;font-style:normal;font-var=
iant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wr=
ap">Dear QUIC WG,</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;ma=
rgin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:A=
rial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-sty=
le:normal;font-variant:normal;text-decoration:none;vertical-align:baseline;=
white-space:pre-wrap">On behalf of the Stream 0 Design Team, I am pleased t=
o report that we have consensus on a proposed approach to share with the WG=
. The DT&#39;s proposal will make QUIC and TLS work closer together and inc=
orporates ideas from DTLS, but it does not use the DTLS protocol itself. </=
span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin=
-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,=
0);background-color:transparent;font-weight:400;font-style:normal;font-vari=
ant:normal;text-decoration:none;vertical-align:baseline;white-space:pre-wra=
p">The DT believes this solves the important open Stream 0 issues. The prop=
osal will be a bit more invasive in TLS, but we believe it is the right lon=
g-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and Mint)=
 are willing and able to do the work necessary.. A number of stacks are cur=
rently working on implementations of this new approach, which we hope to ha=
ve in time for the Interim meeting.</span></p><br><p dir=3D"ltr" style=3D"l=
ine-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:=
11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-w=
eight:400;font-style:normal;font-variant:normal;text-decoration:none;vertic=
al-align:baseline;white-space:pre-wrap">A design document describing the ov=
erall approach can be found at:</span></p></span></span><p dir=3D"ltr" styl=
e=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font=
-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;=
font-weight:400;font-style:normal;font-variant:normal;text-decoration:none;=
vertical-align:baseline;white-space:pre-wrap"><a href=3D"https://docs.googl=
e.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit" target=
=3D"_blank">https://docs.google..com/docum<wbr>ent/d/1fRsJqPinJl8N3b-bflDRV=
6a<wbr>uojfJLkxddT93j6SwHY8/edit</a></span></p><span class=3D""><span><br><=
p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><=
span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-=
color:transparent;font-weight:400;font-style:normal;font-variant:normal;tex=
t-decoration:none;vertical-align:baseline;white-space:pre-wrap">A PR making=
 the changes to the QUIC documents can be found at:</span></p><p dir=3D"ltr=
" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=
=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:tran=
sparent;font-weight:400;font-style:normal;font-variant:normal;text-decorati=
on:none;vertical-align:baseline;white-space:pre-wrap"><a href=3D"https://gi=
thub.com/ekr/base-drafts/pull/29" target=3D"_blank">https://github.com/quic=
wg/base<wbr>-drafts/pull/1377</a></span></p><br><p dir=3D"ltr" style=3D"lin=
e-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11=
pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-wei=
ght:400;font-style:normal;font-variant:normal;text-decoration:none;vertical=
-align:baseline;white-space:pre-wrap">A few design details did not have cle=
ar consensus, but it was felt it would be better to discuss those in the wi=
der WG than delay the design team.=C2=A0 A consistent choice was made in th=
e PR and these issues are mentioned in Appendix B of the design doc.</span>=
</p><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bott=
om:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);ba=
ckground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">As=
 always, comments and questions welcome. That said, this is a big PR and we=
 recognize that some editorial work is going to be needed before merging. I=
n the interest of letting people follow along, and to keep github from fall=
ing over, we ask people to keep discussion on the mailing list and refrain =
from making PR comments.</span></p><br><p dir=3D"ltr" style=3D"line-height:=
1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-f=
amily:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;f=
ont-style:normal;font-variant:normal;text-decoration:none;vertical-align:ba=
seline;white-space:pre-wrap">See you in Kista!</span></p></span></span></b>=
<br class=3D"m_7659979686296042694m_-7919340867003085784m_-1851091610820382=
769gmail-Apple-interchange-newline">Ian and Eric</div>
</blockquote></div><br></div>
</blockquote></div><br></div></div>
</blockquote></div><br></div></div>

--0000000000001bd744056ce5d4b6--


From nobody Wed May 23 14:20:30 2018
Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8C49612D7F6 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 14:20:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 wl_vnLU3fWIH for <quic@ietfa.amsl.com>; Wed, 23 May 2018 14:20:09 -0700 (PDT)
Received: from mail-it0-x234.google.com (mail-it0-x234.google.com [IPv6:2607:f8b0:4001:c0b::234]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A10EE1201F8 for <quic@ietf.org>; Wed, 23 May 2018 14:20:09 -0700 (PDT)
Received: by mail-it0-x234.google.com with SMTP id p3-v6so6324484itc.0 for <quic@ietf.org>; Wed, 23 May 2018 14:20:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=UY7othutBv8VHD2q99Fl/HKzhiO/e7EKIEa/B5R9YVg=; b=A0x/RrgI47lwcJ6XMvDRUjX8s2KQhYD3qFce7tAxqf3mbzrGTxzoQxjvzEeicvJp2A 4UMMfFGC2QAztc2Yr0AeLC8dl26hqH81RpiXZ8AbOh4nSST1xvQCHQ8ngJyDSJES4F9U OICZz9/0dkzlcZeNsNb3E5QteiHhrKRW1+9OcWeCNqpDpjoYkDK2cMgmYGMUzJzBc4Oh UPFhaZulYl35VvMeQGLWhdWpZ1RTfKHqQJl6iPtfoIgJWo0dHWlNaspbrhy2UbqaTSC3 3Oh3a3oBNjknF57KHNqzc51I6cNLt7ZixZs1xI540pQcQPuOF3cUvPBzs4iH9L+qMfrB i8zQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=UY7othutBv8VHD2q99Fl/HKzhiO/e7EKIEa/B5R9YVg=; b=IUW/rOdAsPrwDHVOWyy8kdFsHsnbVEbZyIezOcq+9Fn7iYggwEEm8HB7Y7/IuzDnWY 2rwihLMtVtiqOSWJ33ml3+Iu5TqHYNLNWPlZJy+598YVzNXODXQITsmOic4yf6f7f9Qq FjNw8gpKIboSdizToT6AH/gXlkTuzmjG0pgvE1up1VKYJvWkwDpcAlmKYEsqb1q85BvM IrsRTRHm/xhDk8E73tJ7RuZVLt3eavW1ubAQo+m10f2O9q6wmzhi0qjX7PQ2q5HsMXC3 aa6hF9FjlnabvZktVcXZwD/6aTivT8BPRd5/f3bzBKs9cA2XSZLk2sSxsjfo1rYfnpA/ yacQ==
X-Gm-Message-State: ALKqPwdnZdIq8VuZOYIkl26ELUekSIMyP761V4oA3HqgCtJTzjKe0sil Qko0/AR449dXUWIc3I43oWbyU0wE8ugeOzl8/tU=
X-Google-Smtp-Source: AB8JxZrwydR7ixMSf+mBo/FPY2NMF7wV771qi+dlHzFjuVEZZGqzidk2ylDNImacFVYQKtzETUJn9gVCFLKq/dfocPw=
X-Received: by 2002:a24:186:: with SMTP id 128-v6mr6942630itk.25.1527110409057;  Wed, 23 May 2018 14:20:09 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 23 May 2018 17:20:08 -0400
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <CA+9kkMDiV8MHGSF1Uz0+mA5n12+tb-vcJzPSX1J8gPb-mmNXCw@mail.gmail.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CA+9kkMC0a+HELyVvh+DtvkiorWmKkUQ346zt49Xfyd1zzZ780Q@mail.gmail.com> <CABcZeBP-BWwVAbPuT8rT12pMoNpWhD0qdOLB=-Lj=qrRrwq3ag@mail.gmail.com> <CA+9kkMDiV8MHGSF1Uz0+mA5n12+tb-vcJzPSX1J8gPb-mmNXCw@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Wed, 23 May 2018 17:20:08 -0400
Message-ID: <CAN1APdcq2zgsk-Y-w0YX8VnRq7S=6LvzrfX9HY0wbFYR+ojg-w@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: Ted Hardie <ted.ietf@gmail.com>, Eric Rescorla <ekr@rtfm.com>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Eric Rescorla <ekr@mozilla.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000076faee056ce619b7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/cl5MMpLf0SRfMPNAeXtVf4mxxk8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 21:20:12 -0000

--00000000000076faee056ce619b7
Content-Type: text/plain; charset="UTF-8"

I believe you have misunderstood. In this document, there are no TLS
> records and TLS handshake messages are carried in CRYPTO_HS frames.
> Accordingly, padding is provided in the same fashion as QUIC ordinarily
> does, i.e., using PADDING frames.
>
> That's what I understood from the design document.  The point I'm making
is that this actually a substantive change to the padding structure that
was previously present (in TLS records), and the security analysis has to
take that into account, so it (and similar things) should be described.

As an example of things to consider, padding is probably a fair point. From
a practical perspective, padding could be seen as a pain from older crypto
formats that needs to be dealt with in TLS while the crypto primitives of
QUIC already has an answer to this problem.

But if TLS messages contain encryption primitives beyond what QUIC provides
in early handshake that assumption breaks down while the QUIC crypto is
still weak. For example concerning the encoding of key exchange parameters.
So at the very least it must be stated that this is not an issue and why it
is not issue.

--00000000000076faee056ce619b7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv><blockquote type=3D"cite" class=3D"clean_bq" style=3D"font-family:Helvet=
ica,Arial;font-size:13px;font-style:normal;font-variant-caps:normal;font-we=
ight:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-tra=
nsform:none;white-space:normal;word-spacing:0px;text-decoration:none"><span=
><div><div><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_=
quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204=
,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div cl=
ass=3D"gmail_quote"><div>I believe you have misunderstood. In this document=
, there are no TLS records and TLS handshake messages are carried in CRYPTO=
_HS frames. Accordingly, padding is provided in the same fashion as QUIC or=
dinarily does, i.e., using PADDING frames.<br></div><div><span class=3D""><=
br></span></div></div></div></div></blockquote><div class=3D"gmail_quote">T=
hat&#39;s what I understood from the design document.=C2=A0 The point I&#39=
;m making is that this actually a substantive change to the padding structu=
re that was previously present (in TLS records), and the security analysis =
has to take that into account, so it (and similar things) should be describ=
ed.</div></div></div></div></div></div></span></blockquote></div><p>As an e=
xample of things to consider, padding is probably a fair point. From a prac=
tical perspective, padding could be seen as a pain from older crypto format=
s that needs to be dealt with in TLS while the crypto primitives of QUIC al=
ready has an answer to this problem.</p><p>But if TLS messages contain encr=
yption primitives beyond what QUIC provides in early handshake that assumpt=
ion breaks down while the QUIC crypto is still weak. For example concerning=
 the encoding of key exchange parameters. So at the very least it must be s=
tated that this is not an issue and why it is not issue.</p></body></html>

--00000000000076faee056ce619b7--


From nobody Wed May 23 14:34:27 2018
Return-Path: <ekr@rtfm.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D719012E8C1 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 14:34:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, T_DKIMWL_WL_MED=-0.01, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 wNpaldr6NjI0 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 14:34:13 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1DAF212E865 for <quic@ietf.org>; Wed, 23 May 2018 14:34:13 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id a6-v6so20868072oia.2 for <quic@ietf.org>; Wed, 23 May 2018 14:34:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=nOdVUHzf8gWnZFslUTll7Yjza+EmuNGCWqgfa2kEjaI=; b=nVBvezl7RsGqR1iaLh1zBTEZ5rRRlKAcjn6ww8OVT3iGJ1wEOdpURv7MUzxujVulaX 5o9CaJiJoRIyWQqWSm4+m6Kqm/9y059Tjf8F3rM98JrknBR7drTOmzAgkynEIZ3+a0Bd 06q07MQIJqB5jRUY/OdoJMG9CwhVUgLwZr9KLYaerI41e9/IhFmXmHwu4UKZqn0gKiAF h0SITKYHkrS55RHpd27N3MffDjAp0/uMZCrjdB1HhqbJI9eKMJvXqVhYg5QiyQGM096d cn/ayHdHc4hZaAouYHHHm9hpzqRDx20wUD62WLgDDw4Cxa0+GDQG5SM/bELb5yyrnyLP /7pg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=nOdVUHzf8gWnZFslUTll7Yjza+EmuNGCWqgfa2kEjaI=; b=aBE3jfm9HiRBebzKZdxqDbmyrdgOraZF3tfIn3lA8+jV4oJLRdxPq7dBgioU3B/RkI GP7VmzkKxvxtfGtdZezfWjCuYAljYhY0fUOmrDTLyL+JRczCNSnMDR0JYovqR/MBAm+w A3RdzIKPFwrBAagaBtPvugYMdY05F0K2RjD+nXxICBcK9dsMyUybkN+SSBGNBbQZob7p Bo02TYZbJn3ZH7E0DdhTUo+BnlUBFQyomV//XjRBjXkCHTSEzP8O+rscK9FMtkhKmoe0 i4k7baEvFfNcxSJlT+PrFSuIz1UVcM4g/ALVl9O5WYyMzUxV4zoM84MRFKjvyf4VAo3N ykRg==
X-Gm-Message-State: ALKqPwcrb5rZT/glkd/vuD8ruC/trDYdcrNKBsQdlxzPaDECFKtO0K1Q 4BjMDAT84oFwDerLz5iW1dl6NNdxwplo1WoePOAVdg==
X-Google-Smtp-Source: AB8JxZqkC2R3L2AcBst5wlWg1xIBy9ouid45OASqN2yc8l5krnkh7aWn63SLzAL8MRRPHhQxj3t7HHgtfMgxSZDy0O4=
X-Received: by 2002:aca:c589:: with SMTP id v131-v6mr2669013oif.92.1527111252192;  Wed, 23 May 2018 14:34:12 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:ac9:66:0:0:0:0:0 with HTTP; Wed, 23 May 2018 14:33:31 -0700 (PDT)
In-Reply-To: <CA+9kkMDiV8MHGSF1Uz0+mA5n12+tb-vcJzPSX1J8gPb-mmNXCw@mail.gmail.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CA+9kkMC0a+HELyVvh+DtvkiorWmKkUQ346zt49Xfyd1zzZ780Q@mail.gmail.com> <CABcZeBP-BWwVAbPuT8rT12pMoNpWhD0qdOLB=-Lj=qrRrwq3ag@mail.gmail.com> <CA+9kkMDiV8MHGSF1Uz0+mA5n12+tb-vcJzPSX1J8gPb-mmNXCw@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 23 May 2018 14:33:31 -0700
Message-ID: <CABcZeBNNYNhKEBiB3_cVGRMO7_cV_c8vzjuHgUpp59ziTJWeHg@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: Ted Hardie <ted.ietf@gmail.com>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Eric Rescorla <ekr@mozilla.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b8415d056ce64bf1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/1-DwurU3ECEAouutFE9457sdbZ4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 21:34:26 -0000

--000000000000b8415d056ce64bf1
Content-Type: text/plain; charset="UTF-8"

On Wed, May 23, 2018 at 2:00 PM, Ted Hardie <ted.ietf@gmail.com> wrote:

>
> On Wed, May 23, 2018 at 1:23 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>
>>
>>
>> On Wed, May 23, 2018 at 12:42 PM, Ted Hardie <ted.ietf@gmail.com> wrote:
>>
>>> Howdy,
>>>
>>> Thanks for sharing the document.  I have a couple of detailed comments,
>>> and then some high level comments which I will put into a separate email.
>>>
>>> First, the document says this:
>>>
>>> Though proper analysis is needed, it is not likely that the removal of
>>> the TLS record layer will cause a security concern, because the security
>>> properties provided by QUIC packets are identical to what have been
>>> provided by TLS records.
>>>
>>>
>>> I'm not sure that this is actually the statement we need to analyze,
>>> though. We need to be sure that the security properties of TLS records used
>>> in TCP packets are available in QUIC streams in QUIC packets using UDP as a
>>> multiplexing layer. There appear to be some difference in where the
>>> facilities the overall system provides that may require more description.
>>> As an example, I think the way padding works in this proposal needs more
>>> description. If I understand correctly, each TLS record is encrypted
>>> separately and the presence or absence of padding is indicated by a
>>> padding_length byte present in each record. That means the padding is
>>> related to the record, not the packet; by removing the record layer and
>>> using QUIC frames, though, we seem to have a different padding structure.
>>> QUIC uses padding frames, not padding within other frame types which is
>>> both conceptually and practically different.
>>>
>>
>> I believe you have misunderstood. In this document, there are no TLS
>> records and TLS handshake messages are carried in CRYPTO_HS frames.
>> Accordingly, padding is provided in the same fashion as QUIC ordinarily
>> does, i.e., using PADDING frames.
>>
>> That's what I understood from the design document.  The point I'm making
> is that this actually a substantive change to the padding structure that
> was previously present (in TLS records), and the security analysis has to
> take that into account, so it (and similar things) should be described.
>

I don't think most of the analyses take padding into account, partly
because basically nobody pads, so nobody was assuming that padding came
from TLS.

-Ekr



Similarly, I'd be interested in more text on the interaction with
>> precedence, since the loss of the record layer means that the former
>> guarantee that the record layer makes records available in the order in
>> which they were protected now seems to be unavailable.
>>
>
> I'm not quite sure I follow what you are asking about here. In both cases,
> TLS sits on top of QUIC's reliable in-order deliver guarantees. Is the
> point you are making that formerly, if QUIC violated these guarantees, that
> would result in TLS handshake failure, whereas now it does not?
>
> This just related to the general point I was making above.  When the
> design shifts where it was getting a function, it would be helpful if it
> called it out more directly, to facilitate the analysis.
>
> regards,
>
> Ted
>
> -Ekr
>>
>>
>>
>>> regards,
>>>
>>>
>>> Ted
>>>
>>>
>>>
>>>
>>>
>>> On Tue, May 22, 2018 at 6:30 PM, Ian Swett <
>>> ianswett=40google.com@dmarc.ietf.org> wrote:
>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> *Dear QUIC WG,On behalf of the Stream 0 Design Team, I am pleased to
>>>> report that we have consensus on a proposed approach to share with the WG.
>>>> The DT's proposal will make QUIC and TLS work closer together and
>>>> incorporates ideas from DTLS, but it does not use the DTLS protocol itself.
>>>> The DT believes this solves the important open Stream 0 issues. The
>>>> proposal will be a bit more invasive in TLS, but we believe it is the right
>>>> long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and
>>>> Mint) are willing and able to do the work necessary.. A number of stacks
>>>> are currently working on implementations of this new approach, which we
>>>> hope to have in time for the Interim meeting.A design document describing
>>>> the overall approach can be found
>>>> at:https://docs.google..com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit
>>>> <https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit>A
>>>> PR making the changes to the QUIC documents can be found
>>>> at:https://github.com/quicwg/base-drafts/pull/1377
>>>> <https://github.com/ekr/base-drafts/pull/29>A few design details did not
>>>> have clear consensus, but it was felt it would be better to discuss those
>>>> in the wider WG than delay the design team.  A consistent choice was made
>>>> in the PR and these issues are mentioned in Appendix B of the design doc.As
>>>> always, comments and questions welcome. That said, this is a big PR and we
>>>> recognize that some editorial work is going to be needed before merging. In
>>>> the interest of letting people follow along, and to keep github from
>>>> falling over, we ask people to keep discussion on the mailing list and
>>>> refrain from making PR comments.See you in Kista!*
>>>> Ian and Eric
>>>>
>>>
>>>
>>
>

--000000000000b8415d056ce64bf1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, May 23, 2018 at 2:00 PM, Ted Hardie <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:ted.ietf@gmail.com" target=3D"_blank">ted.ietf@gmail.com</a>&g=
t;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><br><di=
v class=3D"gmail_extra"><span class=3D"">On Wed, May 23, 2018 at 1:23 PM, E=
ric Rescorla <span dir=3D"ltr">&lt;<a href=3D"mailto:ekr@rtfm.com" target=
=3D"_blank">ekr@rtfm.com</a>&gt;</span> wrote:<br></span><div class=3D"gmai=
l_quote"><span class=3D""><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><=
br><div class=3D"gmail_extra"><br><div class=3D"gmail_quote"><span>On Wed, =
May 23, 2018 at 12:42 PM, Ted Hardie <span dir=3D"ltr">&lt;<a href=3D"mailt=
o:ted.ietf@gmail.com" target=3D"_blank">ted.ietf@gmail.com</a>&gt;</span> w=
rote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;borde=
r-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div>Howdy,</div><=
div><br></div><div>Thanks for sharing the document.=C2=A0 I have a couple o=
f detailed comments, and then some high level comments which I will put int=
o a separate email.</div><div><br></div><div>First, the document says this:=
</div><div><br></div><div><p style=3D"line-height:1.38;margin-top:0pt;margi=
n-bottom:0pt;text-align:justify;margin-left:40px" id=3D"m_59269954856168750=
03m_7659979686296042694m_-7919340867003085784gmail-docs-internal-guid-ae997=
8f1-8e74-9194-2b6b-f4000bc3b541"><span style=3D"font-size:11pt;font-family:=
Arial;color:rgb(0,0,0);background-color:transparent;font-weight:400;font-st=
yle:normal;font-variant:normal;text-decoration:none;vertical-align:baseline=
;white-space:pre-wrap">Though proper analysis is needed, it is not likely t=
hat the removal of the TLS record layer will cause a security concern, beca=
use the security properties provided by QUIC packets are identical to what =
have been provided by TLS records.</span></p><p style=3D"line-height:1.38;m=
argin-top:0pt;margin-bottom:0pt;text-align:justify"><span style=3D"font-siz=
e:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font=
-weight:400;font-style:normal;font-variant:normal;text-decoration:none;vert=
ical-align:baseline;white-space:pre-wrap"><br></span></p><p style=3D"line-h=
eight:1.38;margin-top:0pt;margin-bottom:0pt;text-align:justify"><span style=
=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:tran=
sparent;font-weight:400;font-style:normal;font-variant:normal;text-decorati=
on:none;vertical-align:baseline;white-space:pre-wrap">I&#39;m not sure that=
 this is actually the statement we need to analyze, though.  We need to be =
sure that the security properties of TLS records used in TCP packets are av=
ailable in QUIC streams in QUIC packets using UDP as a multiplexing layer. =
 There appear to be some difference in where the facilities the overall sys=
tem provides that may require more description.  As an example, I think the=
 way padding works in this proposal needs more description.  If I understan=
d correctly, each TLS record is encrypted separately and the presence or ab=
sence of padding is indicated by a padding_length byte present in each reco=
rd.  That means the padding is related to the record, not the packet; by re=
moving the record layer and using QUIC frames, though, we seem to have a di=
fferent padding structure.  QUIC uses padding frames, not padding within ot=
her frame types which is both conceptually and practically different.  </sp=
an></p></div></div></blockquote><div><br></div></span><div>I believe you ha=
ve misunderstood. In this document, there are no TLS records and TLS handsh=
ake messages are carried in CRYPTO_HS frames. Accordingly, padding is provi=
ded in the same fashion as QUIC ordinarily does, i.e., using PADDING frames=
.<br></div><span><div><br></div></span></div></div></div></blockquote></spa=
n><div class=3D"gmail_quote">That&#39;s what I understood from the design d=
ocument.=C2=A0 The point I&#39;m making is that this actually a substantive=
 change to the padding structure that was previously present (in TLS record=
s), and the security analysis has to take that into account, so it (and sim=
ilar things) should be described.<br></div></div></div></div></blockquote><=
div><br></div><div>I don&#39;t think most of the analyses take padding into=
 account, partly because basically nobody pads, so nobody was assuming that=
 padding came from TLS.</div><div><br></div><div>-Ekr</div><div><br></div><=
div><br></div><div><br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr=
"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div class=3D"gmail=
_quote"><span><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;=
border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div><p style=
=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;text-align:justify"><=
span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-=
color:transparent;font-weight:400;font-style:normal;font-variant:normal;tex=
t-decoration:none;vertical-align:baseline;white-space:pre-wrap">Similarly, =
I&#39;d be interested in more text on the interaction with precedence, sinc=
e the loss of the record layer means that the former guarantee that the rec=
ord layer makes records available in the order in which they were protected=
 now seems to be unavailable.<br></span></p></div></div></blockquote><div><=
br></div></span><div>I&#39;m not quite sure I follow what you are asking ab=
out here. In both cases, TLS sits on top of QUIC&#39;s reliable in-order de=
liver guarantees. Is the point you are making that formerly, if QUIC violat=
ed these guarantees, that would result in TLS handshake failure, whereas no=
w it does not?<br></div></div><span class=3D""><div class=3D"gmail_quote"><=
br></div></span><div class=3D"gmail_quote">This just related to the general=
 point I was making above.=C2=A0 When the design shifts where it was gettin=
g a function, it would be helpful if it called it out more directly, to fac=
ilitate the analysis. <br></div><div class=3D"gmail_quote"><br></div><div c=
lass=3D"gmail_quote">regards,</div><div class=3D"gmail_quote"><br></div><di=
v class=3D"gmail_quote">Ted<br></div><span class=3D""><div class=3D"gmail_q=
uote"><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8e=
x;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr"><div class=
=3D"gmail_extra"><div class=3D"gmail_quote">-Ekr</div><div class=3D"gmail_q=
uote"><br></div><div class=3D"gmail_quote"><div><br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div dir=3D"ltr"><div><p style=3D"line-height:1.38;margin-top=
:0pt;margin-bottom:0pt;text-align:justify"><span style=3D"font-size:11pt;fo=
nt-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:4=
00;font-style:normal;font-variant:normal;text-decoration:none;vertical-alig=
n:baseline;white-space:pre-wrap"><br></span></p><p style=3D"line-height:1.3=
8;margin-top:0pt;margin-bottom:0pt;text-align:justify"><span style=3D"font-=
size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;f=
ont-weight:400;font-style:normal;font-variant:normal;text-decoration:none;v=
ertical-align:baseline;white-space:pre-wrap">regards,</span></p><p style=3D=
"line-height:1.38;margin-top:0pt;margin-bottom:0pt;text-align:justify"><spa=
n style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-col=
or:transparent;font-weight:400;font-style:normal;font-variant:normal;text-d=
ecoration:none;vertical-align:baseline;white-space:pre-wrap"><br></span></p=
><p style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt;text-align:j=
ustify"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);ba=
ckground-color:transparent;font-weight:400;font-style:normal;font-variant:n=
ormal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Te=
d<br></span></p><p style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0=
pt;text-align:justify"><span style=3D"font-size:11pt;font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:normal=
;font-variant:normal;text-decoration:none;vertical-align:baseline;white-spa=
ce:pre-wrap"></span></p><pre><br></pre><br><p></p><br></div></div><div clas=
s=3D"gmail_extra"><br><div class=3D"gmail_quote"><span><span>On Tue, May 22=
, 2018 at 6:30 PM, Ian Swett <span dir=3D"ltr">&lt;<a href=3D"mailto:ianswe=
tt=3D40google.com@dmarc.ietf.org" target=3D"_blank">ianswett=3D40google.com=
@dmarc.i<wbr>etf.org</a>&gt;</span> wrote:<br></span></span><blockquote cla=
ss=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pa=
dding-left:1ex"><div dir=3D"ltr"><b style=3D"font-weight:normal" id=3D"m_59=
26995485616875003m_7659979686296042694m_-7919340867003085784m_-185109161082=
0382769gmail-docs-internal-guid-2a62f340-8a8f-9073-5cad-25b8001e52b3"><span=
><span><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-botto=
m:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);bac=
kground-color:transparent;font-weight:400;font-style:normal;font-variant:no=
rmal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">Dea=
r QUIC WG,</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-to=
p:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;co=
lor:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:norm=
al;font-variant:normal;text-decoration:none;vertical-align:baseline;white-s=
pace:pre-wrap">On behalf of the Stream 0 Design Team, I am pleased to repor=
t that we have consensus on a proposed approach to share with the WG. The D=
T&#39;s proposal will make QUIC and TLS work closer together and incorporat=
es ideas from DTLS, but it does not use the DTLS protocol itself. </span></=
p><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom=
:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);back=
ground-color:transparent;font-weight:400;font-style:normal;font-variant:nor=
mal;text-decoration:none;vertical-align:baseline;white-space:pre-wrap">The =
DT believes this solves the important open Stream 0 issues. The proposal wi=
ll be a bit more invasive in TLS, but we believe it is the right long-term =
direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and Mint) are wi=
lling and able to do the work necessary.. A number of stacks are currently =
working on implementations of this new approach, which we hope to have in t=
ime for the Interim meeting.</span></p><br><p dir=3D"ltr" style=3D"line-hei=
ght:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;fo=
nt-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:4=
00;font-style:normal;font-variant:normal;text-decoration:none;vertical-alig=
n:baseline;white-space:pre-wrap">A design document describing the overall a=
pproach can be found at:</span></p></span></span><p dir=3D"ltr" style=3D"li=
ne-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:1=
1pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-we=
ight:400;font-style:normal;font-variant:normal;text-decoration:none;vertica=
l-align:baseline;white-space:pre-wrap"><a href=3D"https://docs.google.com/d=
ocument/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit" target=3D"_bla=
nk">https://docs.google..com/docum<wbr>ent/d/1fRsJqPinJl8N3b-bflDRV6a<wbr>u=
ojfJLkxddT93j6SwHY8/edit</a></span></p><span><span><br><p dir=3D"ltr" style=
=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-=
size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;f=
ont-weight:400;font-style:normal;font-variant:normal;text-decoration:none;v=
ertical-align:baseline;white-space:pre-wrap">A PR making the changes to the=
 QUIC documents can be found at:</span></p><p dir=3D"ltr" style=3D"line-hei=
ght:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;fo=
nt-family:Arial;color:rgb(0,0,0);background-color:transparent;font-weight:4=
00;font-style:normal;font-variant:normal;text-decoration:none;vertical-alig=
n:baseline;white-space:pre-wrap"><a href=3D"https://github.com/ekr/base-dra=
fts/pull/29" target=3D"_blank">https://github.com/quicwg/base<wbr>-drafts/p=
ull/1377</a></span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-=
top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;=
color:rgb(0,0,0);background-color:transparent;font-weight:400;font-style:no=
rmal;font-variant:normal;text-decoration:none;vertical-align:baseline;white=
-space:pre-wrap">A few design details did not have clear consensus, but it =
was felt it would be better to discuss those in the wider WG than delay the=
 design team.=C2=A0 A consistent choice was made in the PR and these issues=
 are mentioned in Appendix B of the design doc.</span></p><br><p dir=3D"ltr=
" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=
=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:tran=
sparent;font-weight:400;font-style:normal;font-variant:normal;text-decorati=
on:none;vertical-align:baseline;white-space:pre-wrap">As always, comments a=
nd questions welcome. That said, this is a big PR and we recognize that som=
e editorial work is going to be needed before merging. In the interest of l=
etting people follow along, and to keep github from falling over, we ask pe=
ople to keep discussion on the mailing list and refrain from making PR comm=
ents.</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:r=
gb(0,0,0);background-color:transparent;font-weight:400;font-style:normal;fo=
nt-variant:normal;text-decoration:none;vertical-align:baseline;white-space:=
pre-wrap">See you in Kista!</span></p></span></span></b><br class=3D"m_5926=
995485616875003m_7659979686296042694m_-7919340867003085784m_-18510916108203=
82769gmail-Apple-interchange-newline">Ian and Eric</div>
</blockquote></div><br></div>
</blockquote></div><br></div></div>
</blockquote></span></div><br></div></div>
</blockquote></div><br></div></div>

--000000000000b8415d056ce64bf1--


From nobody Wed May 23 14:47:12 2018
Return-Path: <Lucas.Pardue@bbc.co.uk>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3FA45127010 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 14:47:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 mjt1RPSSbITt for <quic@ietfa.amsl.com>; Wed, 23 May 2018 14:47:09 -0700 (PDT)
Received: from mailout1.telhc.bbc.co.uk (mailout1.telhc.bbc.co.uk [132.185.161.180]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8E84E1201F8 for <quic@ietf.org>; Wed, 23 May 2018 14:47:09 -0700 (PDT)
Received: from BGB01XI1010.national.core.bbc.co.uk (bgb01xi1010.national.core.bbc.co.uk [10.161.14.14]) by mailout1.telhc.bbc.co.uk (8.15.2/8.15.2) with ESMTP id w4NLl72R011569; Wed, 23 May 2018 22:47:07 +0100 (BST)
Received: from BGB01XUD1012.national.core.bbc.co.uk ([10.161.14.10]) by BGB01XI1010.national.core.bbc.co.uk ([10.161.14.14]) with mapi id 14.03.0361.001; Wed, 23 May 2018 22:47:07 +0100
From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
To: Ted Hardie <ted.ietf@gmail.com>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Higher layer comments on stream 0 proposal, WG schedule, and gQUIC
Thread-Topic: Higher layer comments on stream 0 proposal, WG schedule, and gQUIC
Thread-Index: AQHT8tMTqawdr9+Tv0OIrhKYX9dM0KQ92Rhq
Date: Wed, 23 May 2018 21:47:05 +0000
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A3BB3F654@bgb01xud1012>
References: <CA+9kkMA0QnSmvbGOktngU+B-eC7CJFXLicEZfxQga6m6Z+gJLQ@mail.gmail.com>
In-Reply-To: <CA+9kkMA0QnSmvbGOktngU+B-eC7CJFXLicEZfxQga6m6Z+gJLQ@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.19.161.212]
x-exclaimer-md-config: c91d45b2-6e10-4209-9543-d9970fac71b7
x-tm-as-product-ver: SMEX-11.0.0.4255-8.200.1013-23862.002
x-tm-as-result: No--1.103400-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/DOPsD9u7R1N0eXU9h7bWFi2MLFo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 21:47:11 -0000

Hi Ted,

Thanks for your thoughts.

> My back of the envelope calculation is that this means at least one more =
cycle of specification and interop will be required before we get back to w=
here we are with draft -11, and that estimate is because I'm in a hopeful m=
ood that Sean and Eric can move the required work in TLS along.  A more pra=
ctical Ted would see this as adding at minimum 6 months to the schedule.  T=
he changes in TLS are also large enough that I expect that the deployment t=
ime to see significant penetration of the new libraries to be longer than i=
t would be for the previous design.   Call it 9 months, with 3 months of er=
ror bar.

I can't talk to the merit of this proposal in relation to QUIC transport. A=
s somebody greatly interested in application mapping (with a WIP HTTP/QUIC =
implementation) I have concerns that progress in this area keeps being push=
ed back. We have little interop experience in this area to feed back to tra=
nsport.=20

A particular sore point is that the handshake-oriented changes have weak re=
lation to QUIC "steady state', upon which application mappings depend. E.g.=
 Draft 09 and 12 differ little in handling of STREAM frames.=20

Regards
Lucas=


From nobody Wed May 23 14:50:09 2018
Return-Path: <jri.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36CEF12D7E6 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 14:50:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.999
X-Spam-Level: 
X-Spam-Status: No, score=-0.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 0L0Jcl66fBNC for <quic@ietfa.amsl.com>; Wed, 23 May 2018 14:50:06 -0700 (PDT)
Received: from mail-io0-x22f.google.com (mail-io0-x22f.google.com [IPv6:2607:f8b0:4001:c06::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7107E1201F8 for <quic@ietf.org>; Wed, 23 May 2018 14:50:06 -0700 (PDT)
Received: by mail-io0-x22f.google.com with SMTP id c9-v6so24608255iob.12 for <quic@ietf.org>; Wed, 23 May 2018 14:50:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=i6K8NIw5y3opTcywTEFxNFscL804qmaMW6ocUt+nlxg=; b=QmFCdR/nFAKhNvWOrjAMV/TnAVUOtybuM0qz2xeILQAfPlORkcjj4KnHisGSAeRV9o TbEQ5PCJtfyoX+LhVDWFtWcSpeVe3J3ydMV5vWAMzZBEQ0MrBDGjBevS3EehtmPxtXe1 6pfFjWCPyGY7zRoYqWiwHG5QzhF0tDsgUQX6YvV8xWWuTSbgOIVzkUf6hxPgxC8LaMz/ /JIVcDDgG6VDx+UJEYLbpbwC34Xs43TviuXMeC3AueaACjOK2q5R2JNp1f0DtjI+mpUP DgZAA4loEIuDwQVszLA3k5i6wAMFHYvZ+pcbem8L859gwnwXKpMg5j2DQ0tW6dSWm+Fg lF0g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=i6K8NIw5y3opTcywTEFxNFscL804qmaMW6ocUt+nlxg=; b=bpWphLgGdd7qq+CMPDfT5nx92Hizt/TSo1TeC0lZsXTVJElexmHwfROD/sXhJ0nE1C QtbVT1egay5llZ2MQPTJYsoZAJ2uk58Ft9Ewct+VOYubCfNqQ7ErtYynf8wvdyuQ/Zre Tgw+/nw/oJvyHP5XvRQlrmooT2dmSnqNP9KTJE7ZsqWla5asBh44ESAMHEu1xXJbBjwX LiL1WIQ1q8Fm34KbS+3c0VGFTjx87mA9Z8vzcpvn1re2ShZs8JQObs7BP2aih+MF6FSY iVdqjbFrTl1WcGjUTksGmJ3xe5Ec1LYpqDvL54UwalMRJiczd1lzLj2ClvVBUzxHP3gJ vWDw==
X-Gm-Message-State: ALKqPwfYdzpKv21bepXwvj3+1Gg17P49//rTNtF8ts2XEBZeq9kVu8rA 4IS4zhTieIBauKtvMS7Njy5olLf2P12EC6alBLI=
X-Google-Smtp-Source: ADUXVKKCYT9qytigJ4jlfyRj+IuI9LJxmElAbl2ayBMezS4hSiUiDtJMFKzgitrmPnJlyXechr0odLKIPP64+3g0Dxo=
X-Received: by 2002:a6b:d617:: with SMTP id w23-v6mr4076563ioa.8.1527112205680;  Wed, 23 May 2018 14:50:05 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:27d4:0:0:0:0:0 with HTTP; Wed, 23 May 2018 14:50:05 -0700 (PDT)
In-Reply-To: <CAN1APdcq2zgsk-Y-w0YX8VnRq7S=6LvzrfX9HY0wbFYR+ojg-w@mail.gmail.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CA+9kkMC0a+HELyVvh+DtvkiorWmKkUQ346zt49Xfyd1zzZ780Q@mail.gmail.com> <CABcZeBP-BWwVAbPuT8rT12pMoNpWhD0qdOLB=-Lj=qrRrwq3ag@mail.gmail.com> <CA+9kkMDiV8MHGSF1Uz0+mA5n12+tb-vcJzPSX1J8gPb-mmNXCw@mail.gmail.com> <CAN1APdcq2zgsk-Y-w0YX8VnRq7S=6LvzrfX9HY0wbFYR+ojg-w@mail.gmail.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Wed, 23 May 2018 14:50:05 -0700
Message-ID: <CACpbDccHf_FY8AbA_vohsf=30vuq7CveZSfNL-gx66rv90euAw@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
Cc: Ted Hardie <ted.ietf@gmail.com>, Eric Rescorla <ekr@rtfm.com>, Eric Rescorla <ekr@mozilla.com>,  IETF QUIC WG <quic@ietf.org>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008d47b6056ce68454"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/tM90xrL-QRfnzWgzYdKjeXpUHNE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 21:50:08 -0000

--0000000000008d47b6056ce68454
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Ted,

I agree that we should be careful and describe differences in detail where
they exist before making any conclusions about a security analysis. Perhaps
we ought to bring this in front of the tlswg and make sure that folks there
get a chance to poke holes in this proposal.

That said, I don't believe your mapping from records to frames is right. As
I see it, the equivalent of a TLS record in this proposal is a QUIC packet.
Both are encrypted similarly, and both contain pieces of or one or multiple
messages. Padding in TLS is present within the records but outside
messages. Equivalently, padding in this proposal is present within packets
but outside frames carrying TLS messages.

- jana

On Wed, May 23, 2018 at 2:20 PM, Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelf=
j@gmail.com
> wrote:

> I believe you have misunderstood. In this document, there are no TLS
>> records and TLS handshake messages are carried in CRYPTO_HS frames.
>> Accordingly, padding is provided in the same fashion as QUIC ordinarily
>> does, i.e., using PADDING frames.
>>
>> That's what I understood from the design document.  The point I'm making
> is that this actually a substantive change to the padding structure that
> was previously present (in TLS records), and the security analysis has to
> take that into account, so it (and similar things) should be described.
>
> As an example of things to consider, padding is probably a fair point.
> From a practical perspective, padding could be seen as a pain from older
> crypto formats that needs to be dealt with in TLS while the crypto
> primitives of QUIC already has an answer to this problem.
>
> But if TLS messages contain encryption primitives beyond what QUIC
> provides in early handshake that assumption breaks down while the QUIC
> crypto is still weak. For example concerning the encoding of key exchange
> parameters. So at the very least it must be stated that this is not an
> issue and why it is not issue.
>

--0000000000008d47b6056ce68454
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Ted,<div><br></div><div>I agree that we should be careful =
and describe differences in detail where they exist before making any concl=
usions about a security analysis. Perhaps we ought to bring this in front o=
f the tlswg and make sure that folks there get a chance to poke holes in th=
is proposal.<br><br>That said, I don&#39;t believe your mapping from record=
s to frames is right. As I see it, the equivalent of a TLS record in this p=
roposal is a QUIC packet. Both are encrypted similarly, and both contain pi=
eces of or one or multiple messages. Padding in TLS is present within the r=
ecords but outside messages. Equivalently, padding in this proposal is pres=
ent within packets but outside frames carrying TLS messages.</div><div><br>=
</div><div>- jana</div></div><div class=3D"gmail_extra"><br><div class=3D"g=
mail_quote">On Wed, May 23, 2018 at 2:20 PM, Mikkel Fahn=C3=B8e J=C3=B8rgen=
sen <span dir=3D"ltr">&lt;<a href=3D"mailto:mikkelfj@gmail.com" target=3D"_=
blank">mikkelfj@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gma=
il_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-lef=
t:1ex"><div style=3D"word-wrap:break-word;line-break:after-white-space"><sp=
an class=3D""><div><blockquote type=3D"cite" class=3D"m_-502733975983532183=
6clean_bq" style=3D"font-family:Helvetica,Arial;font-size:13px;font-style:n=
ormal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;tex=
t-align:start;text-indent:0px;text-transform:none;white-space:normal;word-s=
pacing:0px;text-decoration:none"><span><div><div><div dir=3D"ltr"><div clas=
s=3D"gmail_extra"><div class=3D"gmail_quote"><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-sty=
le:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><div dir=3D"l=
tr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div>I believe yo=
u have misunderstood. In this document, there are no TLS records and TLS ha=
ndshake messages are carried in CRYPTO_HS frames. Accordingly, padding is p=
rovided in the same fashion as QUIC ordinarily does, i.e., using PADDING fr=
ames.<br></div><div><span><br></span></div></div></div></div></blockquote><=
div class=3D"gmail_quote">That&#39;s what I understood from the design docu=
ment.=C2=A0 The point I&#39;m making is that this actually a substantive ch=
ange to the padding structure that was previously present (in TLS records),=
 and the security analysis has to take that into account, so it (and simila=
r things) should be described.</div></div></div></div></div></div></span></=
blockquote></div></span><p>As an example of things to consider, padding is =
probably a fair point. From a practical perspective, padding could be seen =
as a pain from older crypto formats that needs to be dealt with in TLS whil=
e the crypto primitives of QUIC already has an answer to this problem.</p><=
p>But if TLS messages contain encryption primitives beyond what QUIC provid=
es in early handshake that assumption breaks down while the QUIC crypto is =
still weak. For example concerning the encoding of key exchange parameters.=
 So at the very least it must be stated that this is not an issue and why i=
t is not issue.</p></div>
</blockquote></div><br></div>

--0000000000008d47b6056ce68454--


From nobody Wed May 23 15:14:39 2018
Return-Path: <mbishop@evequefou.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6E907127010 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 15:14:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 rZcnUp_37fmN for <quic@ietfa.amsl.com>; Wed, 23 May 2018 15:14:33 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0139.outbound.protection.outlook.com [104.47.38.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8195F124D37 for <quic@ietf.org>; Wed, 23 May 2018 15:14:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=skteaPTbzNLJ2Fwr/TuORuYYU5kbRgz3NJ0106RpVvI=; b=qMB4ZJC8OykW34xXoKlLEBQukS9aVzaC5udB5Qsxjn77La9tKOd7s1z6ktRpeR0ImUzhe79zPGNXCKrICYMPK1HBukTUJMFm2+zK8DpZ/gEV6vp1fPXbGbqILXDu69SnucFuOXfarjxCAQ6WtlsallxwLn4MHtJR7KMXF4Q4icc=
Received: from SN1PR08MB1854.namprd08.prod.outlook.com (10.169.39.8) by SN1PR08MB1725.namprd08.prod.outlook.com (10.162.133.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.776.11; Wed, 23 May 2018 22:14:30 +0000
Received: from SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d]) by SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d%13]) with mapi id 15.20.0776.015; Wed, 23 May 2018 22:14:29 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Kazuho Oku <kazuhooku@gmail.com>, Christian Huitema <huitema@huitema.net>
CC: IETF QUIC WG <quic@ietf.org>
Subject: RE: Stream0 Design Team Proposal
Thread-Topic: Stream0 Design Team Proposal
Thread-Index: AQHT8jXB/BpXll/I90GhSvtB/+hM26Q8oAsAgAAHFYCAACJqAIAAPsYAgADY9jA=
Date: Wed, 23 May 2018 22:14:29 +0000
Message-ID: <SN1PR08MB1854074075313C93BC71A6F1DA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CABkgnnUB=jqwFzb2rjBHUFzOgu0hX0YUgaf5kW5ENNGKP+mGiA@mail.gmail.com> <MWHPR15MB1821F33BAB20815A38EB34A2B66B0@MWHPR15MB1821.namprd15.prod.outlook.com> <046ee03d-a675-86b6-ed3b-4fa69288c42d@huitema.net> <CANatvzzn1VuAY2+cc8vpo75N3T=VH7YkSTjRC6uB4HATAFfW4Q@mail.gmail.com>
In-Reply-To: <CANatvzzn1VuAY2+cc8vpo75N3T=VH7YkSTjRC6uB4HATAFfW4Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [2601:600:8080:5a28:4940:a32d:2658:89dc]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN1PR08MB1725; 7:M0M5MxrFvBvOfxTwnCxgN7c2A3ZQkDV80igv9dMhUIOwrWVvbezxFQdamvzI8tev+IId/e+DPn8w7+znNVv2QMdz8m+YN2r+XEGmeaIAPIjghN/EZelYSmDAFBowt46QTUipemtMP/xRTk9ir/nUJSVoS1m+nKtc7U5WsEY+0SIuJdNCRxIqHNL88dJSe8mseXMs0qI8QWcBblSIrR2tS48YJNwmxRzvFR05X8R9kLNpvsar6ZTQMK/1v9YphGKy
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(5600026)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(2017052603328)(7153060)(7193020); SRVR:SN1PR08MB1725; 
x-ms-traffictypediagnostic: SN1PR08MB1725:
x-microsoft-antispam-prvs: <SN1PR08MB1725328FB682B3C9FEDB055BDA6B0@SN1PR08MB1725.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(10436049006162)(166708455590820)(85827821059158)(211936372134217)(100405760836317);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(3231254)(944501410)(52105095)(149027)(150027)(6041310)(20161123564045)(20161123560045)(20161123558120)(20161123562045)(2016111802025)(6043046)(6072148)(201708071742011)(7699016); SRVR:SN1PR08MB1725; BCL:0; PCL:0; RULEID:; SRVR:SN1PR08MB1725; 
x-forefront-prvs: 06818431B9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39380400002)(346002)(39830400003)(366004)(376002)(396003)(377424004)(189003)(51444003)(13464003)(199004)(39060400002)(6306002)(102836004)(53936002)(81166006)(6116002)(9686003)(8676002)(55016002)(81156014)(486006)(6436002)(229853002)(110136005)(74316002)(6246003)(59450400001)(99286004)(76176011)(4326008)(8936002)(68736007)(14454004)(3280700002)(3660700001)(2906002)(25786009)(106356001)(11346002)(575784001)(86362001)(7696005)(5660300001)(561944003)(74482002)(5250100002)(7736002)(53546011)(6506007)(446003)(46003)(105586002)(33656002)(478600001)(93886005)(305945005)(97736004)(2900100001)(316002)(186003)(966005)(476003)(19627235001); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR08MB1725; H:SN1PR08MB1854.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: QKGCATzCEGODpQ85B4HeUTX+uFopvStNhXTFMZEG/CEMnDnj38nPmYRS5hvwjAVxULnO3EeO8vf5ZOaoXHy96L12BTEcdjqCP0cLrXueIsseoFeBb9oVs9Osk/mh8cuygH4qYIwAb4gY25EDHiiyg6z6FIlnAYNIBlQvgh3pQ25cdkJGhKou1znlccz20foT
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 77408048-f248-471b-5f4b-08d5c0fa8dfa
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 77408048-f248-471b-5f4b-08d5c0fa8dfa
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 May 2018 22:14:29.7896 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR08MB1725
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Ng2S0KTNp6BpY9NYtKVjRRS6fIg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 22:14:38 -0000

V2hpbGUgYSBIU19ET05FIGZyYW1lIHNlbnQgdW5kZXIgMS1SVFQgd291bGQgc2ltcGxpZnkgc29t
ZSB0aGluZ3MsIEknbSBub3Qgc3VyZSB0aGF0IGl0J3MgcmVxdWlyZWQuICBUaGVyZSdzIGEgdmVy
eSBjbGVhciBzeW5jaHJvbml6YXRpb24gcG9pbnQgd2hpY2ggYWxyZWFkeSBleGlzdHMuDQoNClRo
ZSBjbGllbnQgY2FuJ3Qgc2VuZCAxLVJUVCBtZXNzYWdlcyB1bnRpbCBpdCBoYXMgc2VudCBDbGll
bnQgRmluaXNoZWQuICBUaGUgc2VydmVyIGNhbiBzZW5kLCBidXQgbm90IHByb2Nlc3MsIDEtUlRU
IG1lc3NhZ2VzIHByaW9yIHRvIHJlY2VpdmluZyBDbGllbnQgRmluaXNoZWQuICAoVGhpcyBpcyBh
IHNwZWMgcmVxdWlyZW1lbnQgcmF0aGVyIHRoYW4gYSBjcnlwdG8gbGltaXRhdGlvbiwgaG93ZXZl
ciwgc28gYSBidWdneSBzZXJ2ZXIgbWlnaHQgdmlvbGF0ZSBpdC4pICBUaHVzLCBhbiBBQ0sgZm9y
IGFueSAxLVJUVCBwYWNrZXQgZnJvbSB0aGUgY2xpZW50IGltcGxpY2l0bHkgYWNrbm93bGVkZ2Vz
IHRoZSBjbGllbnQncyBlbnRpcmUgaGFuZHNoYWtlLiAgUmVjZWlwdCBvZiBhbnkgMS1SVFQgcGFj
a2V0IGZyb20gdGhlIGNsaWVudCBpbXBsaWNpdGx5IGFja25vd2xlZGdlcyB0aGUgc2VydmVyJ3Mg
ZW50aXJlIGhhbmRzaGFrZS4NCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IFFV
SUMgPHF1aWMtYm91bmNlc0BpZXRmLm9yZz4gT24gQmVoYWxmIE9mIEthenVobyBPa3UNClNlbnQ6
IFdlZG5lc2RheSwgTWF5IDIzLCAyMDE4IDI6MTQgQU0NClRvOiBDaHJpc3RpYW4gSHVpdGVtYSA8
aHVpdGVtYUBodWl0ZW1hLm5ldD4NCkNjOiBJRVRGIFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc+DQpT
dWJqZWN0OiBSZTogU3RyZWFtMCBEZXNpZ24gVGVhbSBQcm9wb3NhbA0KDQoyMDE4LTA1LTIzIDE0
OjI5IEdNVCswOTowMCBDaHJpc3RpYW4gSHVpdGVtYSA8aHVpdGVtYUBodWl0ZW1hLm5ldD46DQo+
IEkgbGlrZSB0aGUgcHJvcG9zYWwuIEluIHBhcnRpY3VsYXIsIEkgcmVhbGx5IGxpa2UgdGhlIGVu
Y3J5cHRpb24gb2YgDQo+IGhhbmRzaGFrZSBwYWNrZXRzIHdpdGggdGhlIGhhbmRzaGFrZSBrZXks
IGFzIGl0IGRvZXMgY2xvc2UgYSBudW1iZXIgb2YgDQo+IGF2ZW51ZXMgZm9yIGF0dGFja3MuIEFu
ZCBJIGxpa2UgdGhhdCBpdCBzb2x2ZXMgdGhlICJhY2sgcHJvbW90aW9uIiANCj4gaXNzdWUgdGhh
dCBJIHdhcyBjb21wbGFpbmluZyBhZ2FpbnN0IGZvciBzb21lIHRpbWUuIFR1cm5zIG91dCB0aGF0
IGluIA0KPiB0aGUgY3VycmVudCBkcmFmdCwgaXQgaXMgdmVyeSBoYXJkIHRvIGNvbnRhaW4gdGhh
dCBwcm9ibGVtIGlmIHlvdSBlbmFibGUgY2xpZW50IGF1dGguDQo+DQo+DQo+IE9uIHRoZSBvdGhl
ciBoYW5kLCBJIGFncmVlIHdpdGggTWFydGluIHRoYXQgYSBsb3Qgb2YgdGhlIGFkZGl0aW9ucyB0
byANCj4gdHJhbnNtaXNzaW9uIHJlY292ZXJ5IHNob3VsZCBiZSBtb3ZlZCB0byBzZXBhcmF0ZSBQ
UnMuIEkgYW0gbm90IA0KPiBlbnRodXNpYXN0aWMgd2l0aCB0aGUgRU1QVFkgQUNLIG1lY2hhbmlz
bSwgb3Igd2l0aCB0aGUgcHJvcG9zZWQgDQo+ICJpbXBsaWNpdCBhY2tub3dsZWRnZW1lbnQiIG9m
IGEgbG93ZXIgY3J5cHRvIHN0cmVhbSBieSBhIGhpZ2hlciBsZXZlbCBhY2suDQoNCkF0IHRoZSBt
b21lbnQgSSBkbyBub3QgaGF2ZSBhIHN0cm9uZyBvcGluaW9uIG9uIHRoZSBFbXB0eSBBQ0sgbWVj
aGFuaXNtLg0KDQpIb3dldmVyLCByZWdhcmRpbmcgaG93IHdlIGNsb3NlIHRoZSBJbml0aWFsIGFu
ZCBIYW5kc2hha2UgY29udGV4dHMsIG15IHByZWZlcmVuY2UgZ29lcyB0byB1c2luZyBpbXBsaWNp
dCBBQ0tzIChpLmUuIHVzZSB0aGUgc3VjY2Vzc2Z1bCByZWNlaXB0IG9mIGEgcGFja2V0IHRoYXQg
aXMgcHJvdGVjdGVkIHVuZGVyIGEgaGlnaGVyIGxldmVsIG9mIGVuY3J5cHRpb24ga2V5IGFzIHRo
ZSBzaWduYWwpIHJhdGhlciB0aGFuIGV4cGxpY2l0bHkgQUNLaW5nIHRoZSBsYXN0IGZsaWdodCBv
ZiBkYXRhLg0KDQpBcyBJIHNlZSwgdGhlcmUgYXJlIHR3byBkb3duc2lkZXMgaW4gdGhlIEV4cGxp
Y2l0IEFDS2luZyBhcHByb2FjaC4NCg0KKiBFeHBsaWNpdCBBQ0tpbmcgcmVxdWlyZXMgc2VuZGlu
ZyB0d28gYWRkaXRpb25hbCBwYWNrZXRzIGR1cmluZyB0aGUgaGFuZHNoYWtlLCB3aGljaCBtZWFu
cyB0aGF0IHdlIHdvdWxkIGhhdmUgbW9yZSBBRVMgb3BlcmF0aW9ucyBwbHVzIHNvbWV3aGVyZSBh
cm91bmQgNjAgYnl0ZXMgb2Ygb3ZlcmhlYWQgb24gdGhlIHdpcmUuDQoqIEV4cGxpY2l0IEFDS2lu
ZyByZXF1aXJlcyBtb3JlIHNpZ25hbGluZyBmcm9tIHRoZSBUTFMgc3RhY2suIEluIGNhc2Ugb2Yg
aW1wbGljaXQgQUNLaW5nLCB0aGUgVExTIHN0YWNrIG5lZWQgdG8gb25seSBwcm92aWRlIHRoZSBB
RUFEIGNvbnRleHRzIGFuZCB0aGUgbWVzc2FnZXMsIHdoZXJlYXMgaW4gY2FzZSBvZiBleHBsaWNp
dCBBQ0tpbmcsIHRoZSBUTFMgc3RhY2sgYWxzbyBuZWVkcyB0byBwcm92aWRlIGEgc2lnbmFsIGlu
ZGljYXRpbmcgdGhlIGVuZCBvZiB0aGUgdHJhbnNtaXNzaW9uIGF0IGVhY2ggZW5jcnlwdGlvbiBs
ZXZlbC4NCg0KVGhlIGRvd25zaWRlIG9mIHRoZSBpbXBsaWNpdCBBQ0tpbmcgYXBwcm9hY2ggaXMg
dGhhdCB0aGUgc2VydmVyIG5lZWRzIHRvIHNpZ25hbCB0aGUgdGVybWluYXRpb24gb2YgdGhlIEhh
bmRzaGFrZSBjb250ZXh0IHVzaW5nIGEgc3BlY2lhbCBmcmFtZSBzZW50IHVzaW5nIGEgMS1SVFQg
cGFja2V0Lg0KDQpCdXQgZXZlbiB0YWtpbmcgdGhhdCBpbnRvIGNvbnNpZGVyYXRpb24sIEkgdGhp
bmsgdGhhdCBpbXBsaWNpdCBBQ0tpbmcgaXMgc3RpbGwgZWFzaWVyIHRvIGltcGxlbWVudCwgY29u
c2lkZXJpbmcgdGhlIG5lZWQgZm9yIHRoZSBhZGRpdGlvbmFsIHNpZ25hbCBpbiB0aGUgZXhwbGlj
aXQgQUNLIGNhc2UgdGhhdCBoYXZlIGJlZW4gZGVzY3JpYmVkIGFib3ZlLg0KDQoNCj4gSW4gYW55
DQo+IGNhc2UsIHN0YXJ0aW5nIGFzIHNpbXBsZSBhcyBwb3NzaWJsZSB3b3VsZCBoZWxwIGhhdmlu
ZyB0aGUgZmlyc3QgDQo+IGltcGxlbWVudGF0aW9ucyBhbmQgdGVzdHMuDQo+DQo+DQo+IE9uIDUv
MjIvMjAxOCA4OjI2IFBNLCBTdWJvZGggSXllbmdhciB3cm90ZToNCj4NCj4gQXMgYW4gaW1wbGVt
ZW50b3Igb2YgZml6eiwgSSBzdXBwb3J0IHRoaXMgZGVzaWduIGFuZCBhbSB3aWxsaW5nIHRvIA0K
PiBpbXBsZW1lbnQgdGhpcyBhcyB3ZWxsLg0KPg0KPg0KPiBXaGlsZSB0aGlzIGlzIGEgY2hhbmdl
IGluIHRoZSBBUEkgdGhhdCBUTFMgY2xhc3NpY2FsbHkgZXhwb3NlcywgSSANCj4gdGhpbmsgdGhp
cyBpcyB0aGUgcmlnaHQgdHJhZGVvZmYgYmVjYXVzZSBpdCBoZWxwcyBtYWtlIHRoaW5ncyB3YXkg
bW9yZSANCj4gZXhwbGljaXQgd2hpY2ggd2lsbCBwcmV2ZW50IHNldmVyYWwgb3RoZXIgYnVncyBm
cm9tIGhhcHBlbmluZyBpbiB0aGUgZnV0dXJlLg0KPg0KPg0KPiBTdWJvZGgNCj4NCj4gX19fX19f
X19fX19fX19fX19fX19fX19fX19fX19fX18NCj4gRnJvbTogUVVJQyA8cXVpYy1ib3VuY2VzQGll
dGYub3JnPiBvbiBiZWhhbGYgb2YgTWFydGluIFRob21zb24gDQo+IDxtYXJ0aW4udGhvbXNvbkBn
bWFpbC5jb20+DQo+IFNlbnQ6IFR1ZXNkYXksIE1heSAyMiwgMjAxOCA4OjAwOjQwIFBNDQo+IFRv
OiBJYW4gU3dldHQNCj4gQ2M6IGVrckBtb3ppbGxhLmNvbTsgUVVJQyBXRw0KPiBTdWJqZWN0OiBS
ZTogU3RyZWFtMCBEZXNpZ24gVGVhbSBQcm9wb3NhbA0KPg0KPiBGaXJzdCBvZiBhbGwsIHRoYW5r
cyB0byB0aGUgZGVzaWduIHRlYW0gZm9yIHRoZSB3b3JrIHRoZXkgaGF2ZSBkb25lLiAgDQo+IEkg
aGF2ZW4ndCBkaWdlc3RlZCBldmVyeXRoaW5nIHlldCwgYnV0IEkgdGhpbmsgdGhhdCBJIGhhdmUg
YSBnb29kIA0KPiBzZW5zZSBvZiB0aGUgc2hhcGUgb2YgdGhlIHByb3Bvc2FsLg0KPg0KPiBPdmVy
YWxsLCB0aGlzIGxvb2tzIGxpa2UgYSB3b3JrYWJsZSBkZXNpZ24uICBJdCdzIGEgbG90IG1vcmUg
aW52YXNpdmUgDQo+IG9mIHRoZSBjcnlwdG9ncmFwaGljIGhhbmRzaGFrZSBpbXBsZW1lbnRhdGlv
biB0aGFuIEkgaGFkIHRob3VnaHQgDQo+IHBlb3BsZSB3ZXJlIHdpbGxpbmcgdG8gc3RvbWFjaCBv
cmlnaW5hbGx5LiAgQnV0IGl0J3MgY2xlYXIgdGhhdCB3ZSd2ZSANCj4gcnVuIGludG8gcHJvYmxl
bXMgd2l0aCB0aGUgY3VycmVudCwgbW9yZSBhYnN0cmFjdCBBUEkgYW5kIHRoaXMgaXMgYSANCj4g
ZmFpcmx5IG5hdHVyYWwgd2F5IHRvIHNwbGl0IFRMUy4gIEkndmUgc3BlbnQgYSBsaXR0bGUgdGlt
ZSB0aGlua2luZyANCj4gYWJvdXQgaG93IHRoaXMgbWlnaHQgYmUgaW1wbGVtZW50ZWQgYW5kIEkg
dGhpbmsgdGhhdCBpdCdzIG5vdCBnb2luZyB0byANCj4gYmUgKnRvbyogcGFpbmZ1bC4gIFRoZSBw
cm9vZiB3aWxsIGJlIGluIHRoZSBwdWRkaW5nIHRoZXJlIHRob3VnaC4NCj4NCj4gSW4gbG9va2lu
ZyBhdCB0aGUgUFIsIEkgcmVhbGx5IGFwcHJlY2lhdGUgc2VlaW5nIGFsbCB0aGUgY2hhbmdlcyB0
b2dldGhlci4uDQo+IEJUVywgdGhlIGxpbmsgYWJvdmUgcG9pbnRzIHRvIHRoZSB3cm9uZyBQUiwg
c28gYmUgY2FyZWZ1bCAoaXQgYXBwZWFycyANCj4gdG8gaGF2ZSB0aGUgc2FtZSBjb250ZW50LCBi
dXQgdGhhdCdzIG5vdCBndWFyYW50ZWVkKS4gIFRoZSBhY3R1YWwgUFIgaXMgaGVyZToNCj4gaHR0
cHM6Ly9naXRodWIuY29tL3F1aWN3Zy9iYXNlLWRyYWZ0cy9wdWxsLzEzNzcNCj4NCj4gSSd2ZSBw
dXNoZWQgYSBicmFuY2ggdG8gdGhlIG1haW4gcmVwbyBzbyB0aGF0IHlvdSBjYW4gcHJldmlldyB0
aGUgDQo+IGVudGlyZSBkb2N1bWVudCBzZXQ6DQo+IGh0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBv
aW50LmNvbS92Mi91cmw/dT1odHRwcy0zQV9fcXVpY3dnLmdpdGh1Yi5pb18NCj4gYmFzZS0yRGRy
YWZ0c19zdHJlYW0wXyZkPUR3SUJhUSZjPTVWRDBSVHRObFRoM3ljZDQxYjNNVXcmcj1oM0p1OUVC
UzdtSA0KPiB0d2ctd0F5TjdmUSZtPV92R0szelRLRnJNT2tGaWhKblBudExZdzFUMF9ORU1pSFlT
TTBRX3UxSkEmcz11c3VzbXR4STNCDQo+IFRhTGxCV2VfSGtRVVdSSDRzQkkwQ2dnajFvV1pNQkhh
ayZlPQ0KPg0KPiBJdCBzZWVtcyBsaWtlIHRoZXJlIGFyZSBzb21lIGNvcmUgY2hhbmdlcyBoZXJl
IGFuZCBhIGJ1bmNoIG9mIA0KPiBzZXBhcmFibGUgb3IgYXQgbGVhc3Qgc2Vjb25kYXJ5IGNoYW5n
ZXMuICBJJ20gc3VyZSB0aGF0IGVhY2ggb25lIGhhcyANCj4gaXRzIG93biBqdXN0aWZpY2F0aW9u
LCBidXQgdGhhdCBpc24ndCBhbHdheXMgY2xlYXIuIFRoZSBmb2xsb3dpbmcgDQo+IGNoYW5nZXMg
c2VlbSBsaWtlIHRoZXkgYXJlIHNlcGFyYWJsZToNCj4NCj4gKiBUaGUgdXNlIG9mIHNlcGFyYXRl
IHBhY2tldCBudW1iZXIgc3BhY2VzDQo+ICogVGhlIFJldHJ5IHBhY2tldCBjaGFuZ2VzIChhbmQg
TkVXX1RPS0VOKQ0KPiAqIEVNUFRZX0FDSw0KPiAqIFRoZSBUTFMgZXh0ZW5zaW9uIGZvciBmbG93
IGNvbnRyb2wNCj4NCj4gUmlnaHQgbm93LCBzb21lIG9mIHRoZXNlIGFwcGVhciB0byBiZSBlbnRp
cmVseSBncmF0dWl0b3VzLiAgSSdkIGxpa2UgDQo+IHRvIGdldCB0byB0aGUgYm90dG9tIG9mIGVh
Y2ggYmVmb3JlIHdlIGNvbnRpbnVlLg0KPg0KPiBBdCBhIG1pbmltdW0sIHRoZSBQUiB3ZSBsYW5k
IGZpcnN0IHNob3VsZCBpbmNsdWRlIGp1c3QgdGhlIGNvcmUgY2hhbmdlcy4NCj4gQXMgeW91IHNh
eSwgcmV2aWV3aW5nIGEgbW9uc3RlciBQUiBsaWtlIHRoaXMgd2lsbCBvbmx5IG1ha2UgR2l0SHVi
IA0KPiB3ZWVwIHVuaWNvcm5zLCBidXQgd2UgbWlnaHQgYmUgYWJsZSB0byBjdXQgdGhpcyBpbnRv
IHNtYWxsZXIgcGllY2VzLg0KPg0KPiBPbiBXZWQsIE1heSAyMywgMjAxOCBhdCAxMTozMSBBTSBJ
YW4gU3dldHQgPGlhbnN3ZXR0PSANCj4gNDBnb29nbGUuY29tQGRtYXJjLmlldGYub3JnPiB3cm90
ZToNCj4NCj4+IERlYXIgUVVJQyBXRywNCj4NCj4NCj4+IE9uIGJlaGFsZiBvZiB0aGUgU3RyZWFt
IDAgRGVzaWduIFRlYW0sIEkgYW0gcGxlYXNlZCB0byByZXBvcnQgdGhhdCB3ZQ0KPiBoYXZlIGNv
bnNlbnN1cyBvbiBhIHByb3Bvc2VkIGFwcHJvYWNoIHRvIHNoYXJlIHdpdGggdGhlIFdHLiBUaGUg
RFQncyANCj4gcHJvcG9zYWwgd2lsbCBtYWtlIFFVSUMgYW5kIFRMUyB3b3JrIGNsb3NlciB0b2dl
dGhlciBhbmQgaW5jb3Jwb3JhdGVzIA0KPiBpZGVhcyBmcm9tIERUTFMsIGJ1dCBpdCBkb2VzIG5v
dCB1c2UgdGhlIERUTFMgcHJvdG9jb2wgaXRzZWxmLg0KPg0KPg0KPj4gVGhlIERUIGJlbGlldmVz
IHRoaXMgc29sdmVzIHRoZSBpbXBvcnRhbnQgb3BlbiBTdHJlYW0gMCBpc3N1ZXMuIFRoZQ0KPiBw
cm9wb3NhbCB3aWxsIGJlIGEgYml0IG1vcmUgaW52YXNpdmUgaW4gVExTLCBidXQgd2UgYmVsaWV2
ZSBpdCBpcyB0aGUgDQo+IHJpZ2h0IGxvbmctdGVybSBkaXJlY3Rpb24gYW5kIHNldmVyYWwgVExT
IHN0YWNrcyAoQm9yaW5nU1NMLCBQaWNvVExTLCANCj4gTlNTLCBhbmQNCj4gTWludCkgYXJlIHdp
bGxpbmcgYW5kIGFibGUgdG8gZG8gdGhlIHdvcmsgbmVjZXNzYXJ5Li4gQSBudW1iZXIgb2YgDQo+
IHN0YWNrcyBhcmUgY3VycmVudGx5IHdvcmtpbmcgb24gaW1wbGVtZW50YXRpb25zIG9mIHRoaXMg
bmV3IGFwcHJvYWNoLCANCj4gd2hpY2ggd2UgaG9wZSB0byBoYXZlIGluIHRpbWUgZm9yIHRoZSBJ
bnRlcmltIG1lZXRpbmcuDQo+DQo+DQo+PiBBIGRlc2lnbiBkb2N1bWVudCBkZXNjcmliaW5nIHRo
ZSBvdmVyYWxsIGFwcHJvYWNoIGNhbiBiZSBmb3VuZCBhdDoNCj4NCj4NCj4gaHR0cHM6Ly91cmxk
ZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3VybD91PWh0dHBzLTNBX19kb2NzLmdvb2dsZS5jb21f
ZA0KPiBvY3VtZW50X2RfMWZSc0pxUGluSmw4TjNiLTJEYmZsRFJWNmF1b2pmSkxreGRkVDkzajZT
d0hZOF9lZGl0JmQ9RHdJQmFRDQo+ICZjPTVWRDBSVHRObFRoM3ljZDQxYjNNVXcmcj1oM0p1OUVC
UzdtSHR3Zy13QXlON2ZRJm09X3ZHSzN6VEtGck1Pa0ZpaEoNCj4gblBudExZdzFUMF9ORU1pSFlT
TTBRX3UxSkEmcz1qRE5uejM0aG1XdkxTUW5Ia1NuWWRpaFctakctMHhaLVlZcUtxMzB3Vg0KPiBH
ZyZlPQ0KPg0KPg0KPj4gQSBQUiBtYWtpbmcgdGhlIGNoYW5nZXMgdG8gdGhlIFFVSUMgZG9jdW1l
bnRzIGNhbiBiZSBmb3VuZCBhdDoNCj4NCj4+IGh0dHBzOi8vZ2l0aHViLmNvbS9xdWljd2cvYmFz
ZS1kcmFmdHMvcHVsbC8xMzc3DQo+DQo+DQo+PiBBIGZldyBkZXNpZ24gZGV0YWlscyBkaWQgbm90
IGhhdmUgY2xlYXIgY29uc2Vuc3VzLCBidXQgaXQgd2FzIGZlbHQgaXQNCj4gd291bGQgYmUgYmV0
dGVyIHRvIGRpc2N1c3MgdGhvc2UgaW4gdGhlIHdpZGVyIFdHIHRoYW4gZGVsYXkgdGhlIGRlc2ln
biANCj4gdGVhbS4gIEEgY29uc2lzdGVudCBjaG9pY2Ugd2FzIG1hZGUgaW4gdGhlIFBSIGFuZCB0
aGVzZSBpc3N1ZXMgYXJlIA0KPiBtZW50aW9uZWQgaW4gQXBwZW5kaXggQiBvZiB0aGUgZGVzaWdu
IGRvYy4NCj4NCj4NCj4+IEFzIGFsd2F5cywgY29tbWVudHMgYW5kIHF1ZXN0aW9ucyB3ZWxjb21l
LiBUaGF0IHNhaWQsIHRoaXMgaXMgYSBiaWcgDQo+PiBQUg0KPiBhbmQgd2UgcmVjb2duaXplIHRo
YXQgc29tZSBlZGl0b3JpYWwgd29yayBpcyBnb2luZyB0byBiZSBuZWVkZWQgYmVmb3JlIA0KPiBt
ZXJnaW5nLiBJbiB0aGUgaW50ZXJlc3Qgb2YgbGV0dGluZyBwZW9wbGUgZm9sbG93IGFsb25nLCBh
bmQgdG8ga2VlcCANCj4gZ2l0aHViIGZyb20gZmFsbGluZyBvdmVyLCB3ZSBhc2sgcGVvcGxlIHRv
IGtlZXAgZGlzY3Vzc2lvbiBvbiB0aGUgDQo+IG1haWxpbmcgbGlzdCBhbmQgcmVmcmFpbiBmcm9t
IG1ha2luZyBQUiBjb21tZW50cy4NCj4NCj4NCj4+IFNlZSB5b3UgaW4gS2lzdGEhDQo+DQo+DQo+
PiBJYW4gYW5kIEVyaWMNCj4NCj4NCg0KDQoNCi0tDQpLYXp1aG8gT2t1DQoNCg==


From nobody Wed May 23 15:23:28 2018
Return-Path: <mbishop@evequefou.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ABBB7126BF3 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 15:23:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, T_KAM_HTML_FONT_INVALID=0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 IPvPSvsj4MUN for <quic@ietfa.amsl.com>; Wed, 23 May 2018 15:23:23 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0139.outbound.protection.outlook.com [104.47.33.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1C7F5124D37 for <quic@ietf.org>; Wed, 23 May 2018 15:23:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=AYQM/K8MtuKsD88vDNLlOrY454mGPoovY80g6pC5UUI=; b=Ek5xM7IzcZFICSgCbfh26mMUSCZDA4eHh++jDh3k08C1EhVVs21DrEOaJDSEe6fgyjAipcdqkbQRZWoI4S+9l800y9EL5jffHWIBKbvgKp5NYEzqG3Iul2bCE8eFgUqF7wZllWwoGG8yMm2EnXQSsSPXo1S2K04nV+xKk2WcTco=
Received: from SN1PR08MB1854.namprd08.prod.outlook.com (10.169.39.8) by SN1PR08MB1725.namprd08.prod.outlook.com (10.162.133.151) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.776.11; Wed, 23 May 2018 22:23:20 +0000
Received: from SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d]) by SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d%13]) with mapi id 15.20.0776.015; Wed, 23 May 2018 22:23:20 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Martin Thomson <martin.thomson@gmail.com>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
CC: "ekr@mozilla.com" <ekr@mozilla.com>, QUIC WG <quic@ietf.org>
Subject: RE: Stream0 Design Team Proposal
Thread-Topic: Stream0 Design Team Proposal
Thread-Index: AQHT8jXB/BpXll/I90GhSvtB/+hM26Q8oAsAgAFDfJA=
Date: Wed, 23 May 2018 22:23:20 +0000
Message-ID: <SN1PR08MB1854BF85FCCA0F21CE0DA1A4DA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CABkgnnUB=jqwFzb2rjBHUFzOgu0hX0YUgaf5kW5ENNGKP+mGiA@mail.gmail.com>
In-Reply-To: <CABkgnnUB=jqwFzb2rjBHUFzOgu0hX0YUgaf5kW5ENNGKP+mGiA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [2601:600:8080:5a28:4940:a32d:2658:89dc]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN1PR08MB1725; 7:weLcB/4ecmpcKkO8T1Wl3hRDDIGJu7CSimlwP7u54/IRsJDRIWuWsLe9Q8HyNuJsR4O/cByNSt8PcL2ye/9z1JPNGiSCpM48PRE4x9ItayvpFvnMGQLLEQqNYzgqVgFNjGnGMPN843EV4twho8Quk1sBc2wdDi5BRRwOPKxvDklp1NqsKLrTcemHJw8FXbzj3afC9oV8ytzhtZYn5RhBE0Di6QgmeQgCtD4E3PQi5cZbM+rRobyANaw4QgCqqsz2
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(5600026)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(2017052603328)(7153060)(7193020); SRVR:SN1PR08MB1725; 
x-ms-traffictypediagnostic: SN1PR08MB1725:
x-microsoft-antispam-prvs: <SN1PR08MB1725926660F3D871214E9935DA6B0@SN1PR08MB1725.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(166708455590820)(35073007944872)(211936372134217)(100405760836317)(21748063052155)(119230021023882);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(3231254)(944501410)(52105095)(149027)(150027)(6041310)(20161123564045)(20161123560045)(20161123558120)(20161123562045)(2016111802025)(6043046)(6072148)(201708071742011)(7699016); SRVR:SN1PR08MB1725; BCL:0; PCL:0; RULEID:; SRVR:SN1PR08MB1725; 
x-forefront-prvs: 06818431B9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(376002)(366004)(39830400003)(39380400002)(346002)(13464003)(199004)(51444003)(189003)(53546011)(6506007)(7736002)(46003)(105586002)(446003)(11346002)(86362001)(7696005)(106356001)(5250100002)(561944003)(5660300001)(74482002)(97736004)(2900100001)(606006)(478600001)(476003)(966005)(316002)(186003)(33656002)(410100003)(229853002)(790700001)(110136005)(486006)(6436002)(54906003)(6246003)(74316002)(39060400002)(6306002)(8676002)(55016002)(81156014)(236005)(53936002)(81166006)(102836004)(9686003)(54896002)(6116002)(3660700001)(14454004)(3280700002)(25786009)(2906002)(4326008)(76176011)(59450400001)(99286004)(8936002)(68736007)(15940465004); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR08MB1725; H:SN1PR08MB1854.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: YkLipmTWl/wXlBdx2e32d+Pr8rUsRJPShNmMbPgnQMtgB3HeVdkvDfcCfbHIggnyXQvAomD+XzgpoH2rmuYGkW+nXT6wZMhxdQDhpemf0rGLZ7su8VWkHYSm7bzwjUBOb892u7uGqu8ctYJFxYBh8Oj5MjOPFqXXUMQyky+9Md5fYY8yuSeufsDd/v4RNjmm
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_SN1PR08MB1854BF85FCCA0F21CE0DA1A4DA6B0SN1PR08MB1854namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 426cf3c6-21c3-4459-0f57-08d5c0fbca2f
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 426cf3c6-21c3-4459-0f57-08d5c0fbca2f
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 May 2018 22:23:20.3261 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR08MB1725
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2t3Y2RCAAQgSIW_pj3N29ery8vg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 22:23:27 -0000

--_000_SN1PR08MB1854BF85FCCA0F21CE0DA1A4DA6B0SN1PR08MB1854namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

SSBhbHNvIHRoaW5rIHRoZXNlIHR3byBwaWVjZXMgYXJlIG5vdCBpbmV4dHJpY2FibHkgYm91bmQg
dG9nZXRoZXI6DQoNCiAgKiAgIE1vdmluZyBmcm9tIFN0cmVhbSAwIHRvIENSWVBUTyBmcmFtZXMN
CiAgKiAgIFJlbW92aW5nIHRoZSBUTFMgcmVjb3JkIGxheWVyIGFuZCB1c2luZyB0aGUgVExTIGtl
eXMgZGlyZWN0bHkgaW4gUVVJQyBwYWNrZXQgcHJvdGVjdGlvbg0KDQrigKZ0aG91Z2ggYm90aCBv
ZiB0aGVzZSBpbnRlcmFjdCBwcmV0dHkgY2xvc2VseSB3aXRoIHRoZSBzZXBhcmF0ZSBwYWNrZXQg
bnVtYmVyIHNwYWNlcy4NCg0KDQoNClNvIEkgdGhpbmsgdGhhdOKAmXMgcm91Z2hseSBzaXggUFJz
IHdlIHNob3VsZCBleHBlY3QgdG8gc2VlIG91dCBvZiB0aGUgZGVzaWduIHRlYW3igJlzIHByb3Bv
c2FsLiAgQSBmZXcgb2YgdGhlbSBoYXZlIGRlcGVuZGVuY2llcyBvbiBlYWNoIG90aGVyLCBidXQg
dGhleSBzZWVtIG1vc3RseSBzZXBhcmFibGUuICBJdCBzb3VuZHMgbGlrZSBzZXZlcmFsIG9mIHRo
ZW0gaGF2ZSBjb25zZW5zdXMgaW4gdGhlIGRlc2lnbiB0ZWFtLCBidXQgbm90IGFsbCBvZiB0aGVt
LCBhbmQgaXQgd291bGQgYmUgZ29vZCB0byBiZSBhYmxlIHRvIGRpc2N1c3MgdGhlbSBzZXBhcmF0
ZWx5Lg0KDQoNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IFFVSUMgPHF1aWMt
Ym91bmNlc0BpZXRmLm9yZz4gT24gQmVoYWxmIE9mIE1hcnRpbiBUaG9tc29uDQpTZW50OiBUdWVz
ZGF5LCBNYXkgMjIsIDIwMTggODowMSBQTQ0KVG86IElhbiBTd2V0dCA8aWFuc3dldHQ9NDBnb29n
bGUuY29tQGRtYXJjLmlldGYub3JnPg0KQ2M6IGVrckBtb3ppbGxhLmNvbTsgUVVJQyBXRyA8cXVp
Y0BpZXRmLm9yZz4NClN1YmplY3Q6IFJlOiBTdHJlYW0wIERlc2lnbiBUZWFtIFByb3Bvc2FsDQoN
Cg0KDQpGaXJzdCBvZiBhbGwsIHRoYW5rcyB0byB0aGUgZGVzaWduIHRlYW0gZm9yIHRoZSB3b3Jr
IHRoZXkgaGF2ZSBkb25lLiAgSSBoYXZlbid0IGRpZ2VzdGVkIGV2ZXJ5dGhpbmcgeWV0LCBidXQg
SSB0aGluayB0aGF0IEkgaGF2ZSBhIGdvb2Qgc2Vuc2Ugb2YgdGhlIHNoYXBlIG9mIHRoZSBwcm9w
b3NhbC4NCg0KDQoNCk92ZXJhbGwsIHRoaXMgbG9va3MgbGlrZSBhIHdvcmthYmxlIGRlc2lnbi4g
IEl0J3MgYSBsb3QgbW9yZSBpbnZhc2l2ZSBvZiB0aGUgY3J5cHRvZ3JhcGhpYyBoYW5kc2hha2Ug
aW1wbGVtZW50YXRpb24gdGhhbiBJIGhhZCB0aG91Z2h0IHBlb3BsZSB3ZXJlIHdpbGxpbmcgdG8g
c3RvbWFjaCBvcmlnaW5hbGx5LiAgQnV0IGl0J3MgY2xlYXIgdGhhdCB3ZSd2ZSBydW4gaW50byBw
cm9ibGVtcyB3aXRoIHRoZSBjdXJyZW50LCBtb3JlIGFic3RyYWN0IEFQSSBhbmQgdGhpcyBpcyBh
IGZhaXJseSBuYXR1cmFsIHdheSB0byBzcGxpdCBUTFMuICBJJ3ZlIHNwZW50IGEgbGl0dGxlIHRp
bWUgdGhpbmtpbmcgYWJvdXQgaG93IHRoaXMgbWlnaHQgYmUgaW1wbGVtZW50ZWQgYW5kIEkgdGhp
bmsgdGhhdCBpdCdzIG5vdCBnb2luZyB0byBiZSAqdG9vKiBwYWluZnVsLiAgVGhlIHByb29mIHdp
bGwgYmUgaW4gdGhlIHB1ZGRpbmcgdGhlcmUgdGhvdWdoLg0KDQoNCg0KSW4gbG9va2luZyBhdCB0
aGUgUFIsIEkgcmVhbGx5IGFwcHJlY2lhdGUgc2VlaW5nIGFsbCB0aGUgY2hhbmdlcyB0b2dldGhl
ci4NCg0KQlRXLCB0aGUgbGluayBhYm92ZSBwb2ludHMgdG8gdGhlIHdyb25nIFBSLCBzbyBiZSBj
YXJlZnVsIChpdCBhcHBlYXJzIHRvIGhhdmUgdGhlIHNhbWUgY29udGVudCwgYnV0IHRoYXQncyBu
b3QgZ3VhcmFudGVlZCkuICBUaGUgYWN0dWFsIFBSIGlzIGhlcmU6DQoNCmh0dHBzOi8vZ2l0aHVi
LmNvbS9xdWljd2cvYmFzZS1kcmFmdHMvcHVsbC8xMzc3DQoNCg0KDQpJJ3ZlIHB1c2hlZCBhIGJy
YW5jaCB0byB0aGUgbWFpbiByZXBvIHNvIHRoYXQgeW91IGNhbiBwcmV2aWV3IHRoZSBlbnRpcmUg
ZG9jdW1lbnQgc2V0OiBodHRwczovL3F1aWN3Zy5naXRodWIuaW8vYmFzZS1kcmFmdHMvc3RyZWFt
MC8NCg0KDQoNCkl0IHNlZW1zIGxpa2UgdGhlcmUgYXJlIHNvbWUgY29yZSBjaGFuZ2VzIGhlcmUg
YW5kIGEgYnVuY2ggb2Ygc2VwYXJhYmxlIG9yIGF0IGxlYXN0IHNlY29uZGFyeSBjaGFuZ2VzLiAg
SSdtIHN1cmUgdGhhdCBlYWNoIG9uZSBoYXMgaXRzIG93biBqdXN0aWZpY2F0aW9uLCBidXQgdGhh
dCBpc24ndCBhbHdheXMgY2xlYXIuIFRoZSBmb2xsb3dpbmcgY2hhbmdlcyBzZWVtIGxpa2UgdGhl
eSBhcmUgc2VwYXJhYmxlOg0KDQoNCg0KKiBUaGUgdXNlIG9mIHNlcGFyYXRlIHBhY2tldCBudW1i
ZXIgc3BhY2VzDQoNCiogVGhlIFJldHJ5IHBhY2tldCBjaGFuZ2VzIChhbmQgTkVXX1RPS0VOKQ0K
DQoqIEVNUFRZX0FDSw0KDQoqIFRoZSBUTFMgZXh0ZW5zaW9uIGZvciBmbG93IGNvbnRyb2wNCg0K
DQoNClJpZ2h0IG5vdywgc29tZSBvZiB0aGVzZSBhcHBlYXIgdG8gYmUgZW50aXJlbHkgZ3JhdHVp
dG91cy4gIEknZCBsaWtlIHRvIGdldCB0byB0aGUgYm90dG9tIG9mIGVhY2ggYmVmb3JlIHdlIGNv
bnRpbnVlLg0KDQoNCg0KQXQgYSBtaW5pbXVtLCB0aGUgUFIgd2UgbGFuZCBmaXJzdCBzaG91bGQg
aW5jbHVkZSBqdXN0IHRoZSBjb3JlIGNoYW5nZXMuDQoNCkFzIHlvdSBzYXksIHJldmlld2luZyBh
IG1vbnN0ZXIgUFIgbGlrZSB0aGlzIHdpbGwgb25seSBtYWtlIEdpdEh1YiB3ZWVwIHVuaWNvcm5z
LCBidXQgd2UgbWlnaHQgYmUgYWJsZSB0byBjdXQgdGhpcyBpbnRvIHNtYWxsZXIgcGllY2VzLg0K
DQoNCg0KT24gV2VkLCBNYXkgMjMsIDIwMTggYXQgMTE6MzEgQU0gSWFuIFN3ZXR0IDxpYW5zd2V0
dD0gNDBnb29nbGUuY29tQGRtYXJjLmlldGYub3JnPG1haWx0bzo0MGdvb2dsZS5jb21AZG1hcmMu
aWV0Zi5vcmc+PiB3cm90ZToNCg0KDQoNCj4gRGVhciBRVUlDIFdHLA0KDQoNCg0KDQoNCj4gT24g
YmVoYWxmIG9mIHRoZSBTdHJlYW0gMCBEZXNpZ24gVGVhbSwgSSBhbSBwbGVhc2VkIHRvIHJlcG9y
dCB0aGF0IHdlDQoNCmhhdmUgY29uc2Vuc3VzIG9uIGEgcHJvcG9zZWQgYXBwcm9hY2ggdG8gc2hh
cmUgd2l0aCB0aGUgV0cuIFRoZSBEVCdzIHByb3Bvc2FsIHdpbGwgbWFrZSBRVUlDIGFuZCBUTFMg
d29yayBjbG9zZXIgdG9nZXRoZXIgYW5kIGluY29ycG9yYXRlcyBpZGVhcyBmcm9tIERUTFMsIGJ1
dCBpdCBkb2VzIG5vdCB1c2UgdGhlIERUTFMgcHJvdG9jb2wgaXRzZWxmLg0KDQoNCg0KDQoNCj4g
VGhlIERUIGJlbGlldmVzIHRoaXMgc29sdmVzIHRoZSBpbXBvcnRhbnQgb3BlbiBTdHJlYW0gMCBp
c3N1ZXMuIFRoZQ0KDQpwcm9wb3NhbCB3aWxsIGJlIGEgYml0IG1vcmUgaW52YXNpdmUgaW4gVExT
LCBidXQgd2UgYmVsaWV2ZSBpdCBpcyB0aGUgcmlnaHQgbG9uZy10ZXJtIGRpcmVjdGlvbiBhbmQg
c2V2ZXJhbCBUTFMgc3RhY2tzIChCb3JpbmdTU0wsIFBpY29UTFMsIE5TUywgYW5kDQoNCk1pbnQp
IGFyZSB3aWxsaW5nIGFuZCBhYmxlIHRvIGRvIHRoZSB3b3JrIG5lY2Vzc2FyeS4uIEEgbnVtYmVy
IG9mIHN0YWNrcyBhcmUgY3VycmVudGx5IHdvcmtpbmcgb24gaW1wbGVtZW50YXRpb25zIG9mIHRo
aXMgbmV3IGFwcHJvYWNoLCB3aGljaCB3ZSBob3BlIHRvIGhhdmUgaW4gdGltZSBmb3IgdGhlIElu
dGVyaW0gbWVldGluZy4NCg0KDQoNCg0KDQo+IEEgZGVzaWduIGRvY3VtZW50IGRlc2NyaWJpbmcg
dGhlIG92ZXJhbGwgYXBwcm9hY2ggY2FuIGJlIGZvdW5kIGF0Og0KDQoNCg0KDQoNCmh0dHBzOi8v
ZG9jcy5nb29nbGUuY29tL2RvY3VtZW50L2QvMWZSc0pxUGluSmw4TjNiLWJmbERSVjZhdW9qZkpM
a3hkZFQ5M2o2U3dIWTgvZWRpdA0KDQoNCg0KDQoNCj4gQSBQUiBtYWtpbmcgdGhlIGNoYW5nZXMg
dG8gdGhlIFFVSUMgZG9jdW1lbnRzIGNhbiBiZSBmb3VuZCBhdDoNCg0KDQoNCj4gaHR0cHM6Ly9n
aXRodWIuY29tL3F1aWN3Zy9iYXNlLWRyYWZ0cy9wdWxsLzEzNzcNCg0KDQoNCg0KDQo+IEEgZmV3
IGRlc2lnbiBkZXRhaWxzIGRpZCBub3QgaGF2ZSBjbGVhciBjb25zZW5zdXMsIGJ1dCBpdCB3YXMg
ZmVsdCBpdA0KDQp3b3VsZCBiZSBiZXR0ZXIgdG8gZGlzY3VzcyB0aG9zZSBpbiB0aGUgd2lkZXIg
V0cgdGhhbiBkZWxheSB0aGUgZGVzaWduIHRlYW0uICBBIGNvbnNpc3RlbnQgY2hvaWNlIHdhcyBt
YWRlIGluIHRoZSBQUiBhbmQgdGhlc2UgaXNzdWVzIGFyZSBtZW50aW9uZWQgaW4gQXBwZW5kaXgg
QiBvZiB0aGUgZGVzaWduIGRvYy4NCg0KDQoNCg0KDQo+IEFzIGFsd2F5cywgY29tbWVudHMgYW5k
IHF1ZXN0aW9ucyB3ZWxjb21lLiBUaGF0IHNhaWQsIHRoaXMgaXMgYSBiaWcgUFINCg0KYW5kIHdl
IHJlY29nbml6ZSB0aGF0IHNvbWUgZWRpdG9yaWFsIHdvcmsgaXMgZ29pbmcgdG8gYmUgbmVlZGVk
IGJlZm9yZSBtZXJnaW5nLiBJbiB0aGUgaW50ZXJlc3Qgb2YgbGV0dGluZyBwZW9wbGUgZm9sbG93
IGFsb25nLCBhbmQgdG8ga2VlcCBnaXRodWIgZnJvbSBmYWxsaW5nIG92ZXIsIHdlIGFzayBwZW9w
bGUgdG8ga2VlcCBkaXNjdXNzaW9uIG9uIHRoZSBtYWlsaW5nIGxpc3QgYW5kIHJlZnJhaW4gZnJv
bSBtYWtpbmcgUFIgY29tbWVudHMuDQoNCg0KDQoNCg0KPiBTZWUgeW91IGluIEtpc3RhIQ0KDQoN
Cg0KDQoNCj4gSWFuIGFuZCBFcmljDQoNCg0K

--_000_SN1PR08MB1854BF85FCCA0F21CE0DA1A4DA6B0SN1PR08MB1854namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMg
MiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1
IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLk1z
b1BsYWluVGV4dCwgbGkuTXNvUGxhaW5UZXh0LCBkaXYuTXNvUGxhaW5UZXh0DQoJe21zby1zdHls
ZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiUGxhaW4gVGV4dCBDaGFyIjsNCgltYXJn
aW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNwYW4uUGxhaW5UZXh0Q2hhcg0KCXtt
c28tc3R5bGUtbmFtZToiUGxhaW4gVGV4dCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7
DQoJbXNvLXN0eWxlLWxpbms6IlBsYWluIFRleHQiOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCkBwYWdlIFdvcmRTZWN0aW9u
MQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47
fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQovKiBMaXN0IERlZmlu
aXRpb25zICovDQpAbGlzdCBsMA0KCXttc28tbGlzdC1pZDoyODEzNTA0Njc7DQoJbXNvLWxpc3Qt
dHlwZTpoeWJyaWQ7DQoJbXNvLWxpc3QtdGVtcGxhdGUtaWRzOi0xMzAzOTAzMzAyIDY3Njk4Njg5
IDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3
Njk4NjkxIDY3Njk4NjkzO30NCkBsaXN0IGwwOmxldmVsMQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZv
cm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDpu
b25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1
aW47DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwwOmxldmVsMg0KCXttc28tbGV2ZWwt
bnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwtdGFi
LXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRl
bnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6bGV2ZWwz
DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7
DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjps
ZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxp
c3QgbDA6bGV2ZWw0DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2
ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJl
ci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpTeW1i
b2w7fQ0KQGxpc3QgbDA6bGV2ZWw1DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsN
Cgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZl
bC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1p
bHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMDpsZXZlbDYNCgl7bXNvLWxldmVsLW51bWJlci1m
b3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6
bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4y
NWluOw0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMDpsZXZlbDcNCgl7bXNvLWxl
dmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2
ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4
dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDgN
Cgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJ
bXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0
Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCkBs
aXN0IGwwOmxldmVsOQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxl
dmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1i
ZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6V2lu
Z2RpbmdzO30NCm9sDQoJe21hcmdpbi1ib3R0b206MGluO30NCnVsDQoJe21hcmdpbi1ib3R0b206
MGluO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1
bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEt
LVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzpp
ZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtl
bmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSIjMDU2M0MxIiB2bGlu
az0iIzk1NEY3MiI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+SSBhbHNvIHRoaW5rIHRoZXNlIHR3byBwaWVjZXMgYXJlIG5vdCBpbmV4dHJpY2Fi
bHkgYm91bmQgdG9nZXRoZXI6PG86cD48L286cD48L3A+DQo8dWwgc3R5bGU9Im1hcmdpbi10b3A6
MGluIiB0eXBlPSJkaXNjIj4NCjxsaSBjbGFzcz0iTXNvUGxhaW5UZXh0IiBzdHlsZT0ibXNvLWxp
c3Q6bDAgbGV2ZWwxIGxmbzEiPk1vdmluZyBmcm9tIFN0cmVhbSAwIHRvIENSWVBUTyBmcmFtZXM8
bzpwPjwvbzpwPjwvbGk+PGxpIGNsYXNzPSJNc29QbGFpblRleHQiIHN0eWxlPSJtc28tbGlzdDps
MCBsZXZlbDEgbGZvMSI+UmVtb3ZpbmcgdGhlIFRMUyByZWNvcmQgbGF5ZXIgYW5kIHVzaW5nIHRo
ZSBUTFMga2V5cyBkaXJlY3RseSBpbiBRVUlDIHBhY2tldCBwcm90ZWN0aW9uPG86cD48L286cD48
L2xpPjwvdWw+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij7igKZ0aG91Z2ggYm90aCBvZiB0aGVz
ZSBpbnRlcmFjdCBwcmV0dHkgY2xvc2VseSB3aXRoIHRoZSBzZXBhcmF0ZSBwYWNrZXQgbnVtYmVy
IHNwYWNlcy48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+U28gSSB0aGluayB0aGF04oCZ
cyByb3VnaGx5IHNpeCBQUnMgd2Ugc2hvdWxkIGV4cGVjdCB0byBzZWUgb3V0IG9mIHRoZSBkZXNp
Z24gdGVhbeKAmXMgcHJvcG9zYWwuJm5ic3A7IEEgZmV3IG9mIHRoZW0gaGF2ZSBkZXBlbmRlbmNp
ZXMgb24gZWFjaCBvdGhlciwgYnV0IHRoZXkgc2VlbSBtb3N0bHkgc2VwYXJhYmxlLiZuYnNwOyBJ
dCBzb3VuZHMgbGlrZSBzZXZlcmFsIG9mIHRoZW0gaGF2ZSBjb25zZW5zdXMgaW4gdGhlIGRlc2ln
bg0KIHRlYW0sIGJ1dCBub3QgYWxsIG9mIHRoZW0sIGFuZCBpdCB3b3VsZCBiZSBnb29kIHRvIGJl
IGFibGUgdG8gZGlzY3VzcyB0aGVtIHNlcGFyYXRlbHkuPG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPGJyPg0KRnJvbTogUVVJQyAmbHQ7cXVp
Yy1ib3VuY2VzQGlldGYub3JnJmd0OyBPbiBCZWhhbGYgT2YgTWFydGluIFRob21zb248YnI+DQpT
ZW50OiBUdWVzZGF5LCBNYXkgMjIsIDIwMTggODowMSBQTTxicj4NClRvOiBJYW4gU3dldHQgJmx0
O2lhbnN3ZXR0PTQwZ29vZ2xlLmNvbUBkbWFyYy5pZXRmLm9yZyZndDs8YnI+DQpDYzogZWtyQG1v
emlsbGEuY29tOyBRVUlDIFdHICZsdDtxdWljQGlldGYub3JnJmd0Ozxicj4NClN1YmplY3Q6IFJl
OiBTdHJlYW0wIERlc2lnbiBUZWFtIFByb3Bvc2FsPC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5GaXJzdCBv
ZiBhbGwsIHRoYW5rcyB0byB0aGUgZGVzaWduIHRlYW0gZm9yIHRoZSB3b3JrIHRoZXkgaGF2ZSBk
b25lLiZuYnNwOyBJIGhhdmVuJ3QgZGlnZXN0ZWQgZXZlcnl0aGluZyB5ZXQsIGJ1dCBJIHRoaW5r
IHRoYXQgSSBoYXZlIGEgZ29vZCBzZW5zZSBvZiB0aGUgc2hhcGUgb2YgdGhlIHByb3Bvc2FsLjxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5PdmVyYWxsLCB0aGlzIGxvb2tzIGxpa2UgYSB3
b3JrYWJsZSBkZXNpZ24uJm5ic3A7IEl0J3MgYSBsb3QgbW9yZSBpbnZhc2l2ZSBvZiB0aGUgY3J5
cHRvZ3JhcGhpYyBoYW5kc2hha2UgaW1wbGVtZW50YXRpb24gdGhhbiBJIGhhZCB0aG91Z2h0IHBl
b3BsZSB3ZXJlIHdpbGxpbmcgdG8gc3RvbWFjaCBvcmlnaW5hbGx5LiZuYnNwOyBCdXQgaXQncyBj
bGVhciB0aGF0IHdlJ3ZlIHJ1biBpbnRvIHByb2JsZW1zIHdpdGggdGhlIGN1cnJlbnQsDQogbW9y
ZSBhYnN0cmFjdCBBUEkgYW5kIHRoaXMgaXMgYSBmYWlybHkgbmF0dXJhbCB3YXkgdG8gc3BsaXQg
VExTLiZuYnNwOyBJJ3ZlIHNwZW50IGEgbGl0dGxlIHRpbWUgdGhpbmtpbmcgYWJvdXQgaG93IHRo
aXMgbWlnaHQgYmUgaW1wbGVtZW50ZWQgYW5kIEkgdGhpbmsgdGhhdCBpdCdzIG5vdCBnb2luZyB0
byBiZSAqdG9vKiBwYWluZnVsLiZuYnNwOyBUaGUgcHJvb2Ygd2lsbCBiZSBpbiB0aGUgcHVkZGlu
ZyB0aGVyZSB0aG91Z2guPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPkluIGxvb2tpbmcg
YXQgdGhlIFBSLCBJIHJlYWxseSBhcHByZWNpYXRlIHNlZWluZyBhbGwgdGhlIGNoYW5nZXMgdG9n
ZXRoZXIuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5CVFcsIHRoZSBs
aW5rIGFib3ZlIHBvaW50cyB0byB0aGUgd3JvbmcgUFIsIHNvIGJlIGNhcmVmdWwgKGl0IGFwcGVh
cnMgdG8gaGF2ZSB0aGUgc2FtZSBjb250ZW50LCBidXQgdGhhdCdzIG5vdCBndWFyYW50ZWVkKS4m
bmJzcDsgVGhlIGFjdHVhbCBQUiBpcyBoZXJlOjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+PGEgaHJlZj0iaHR0cHM6Ly9naXRodWIuY29tL3F1aWN3Zy9iYXNlLWRyYWZ0
cy9wdWxsLzEzNzciPjxzcGFuIHN0eWxlPSJjb2xvcjp3aW5kb3d0ZXh0O3RleHQtZGVjb3JhdGlv
bjpub25lIj5odHRwczovL2dpdGh1Yi5jb20vcXVpY3dnL2Jhc2UtZHJhZnRzL3B1bGwvMTM3Nzwv
c3Bhbj48L2E+PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPkkndmUgcHVzaGVkIGEgYnJh
bmNoIHRvIHRoZSBtYWluIHJlcG8gc28gdGhhdCB5b3UgY2FuIHByZXZpZXcgdGhlIGVudGlyZSBk
b2N1bWVudCBzZXQ6DQo8YSBocmVmPSJodHRwczovL3F1aWN3Zy5naXRodWIuaW8vYmFzZS1kcmFm
dHMvc3RyZWFtMC8iPjxzcGFuIHN0eWxlPSJjb2xvcjp3aW5kb3d0ZXh0O3RleHQtZGVjb3JhdGlv
bjpub25lIj5odHRwczovL3F1aWN3Zy5naXRodWIuaW8vYmFzZS1kcmFmdHMvc3RyZWFtMC88L3Nw
YW4+PC9hPjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5JdCBzZWVtcyBsaWtlIHRoZXJl
IGFyZSBzb21lIGNvcmUgY2hhbmdlcyBoZXJlIGFuZCBhIGJ1bmNoIG9mIHNlcGFyYWJsZSBvciBh
dCBsZWFzdCBzZWNvbmRhcnkgY2hhbmdlcy4mbmJzcDsgSSdtIHN1cmUgdGhhdCBlYWNoIG9uZSBo
YXMgaXRzIG93biBqdXN0aWZpY2F0aW9uLCBidXQgdGhhdCBpc24ndCBhbHdheXMgY2xlYXIuIFRo
ZSBmb2xsb3dpbmcgY2hhbmdlcyBzZWVtIGxpa2UgdGhleSBhcmUgc2VwYXJhYmxlOjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4qIFRoZSB1c2Ugb2Ygc2VwYXJhdGUgcGFja2V0IG51bWJl
ciBzcGFjZXM8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiogVGhlIFJl
dHJ5IHBhY2tldCBjaGFuZ2VzIChhbmQgTkVXX1RPS0VOKTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+KiBFTVBUWV9BQ0s8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPiogVGhlIFRMUyBleHRlbnNpb24gZm9yIGZsb3cgY29udHJvbDxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5SaWdodCBub3csIHNvbWUgb2YgdGhlc2UgYXBwZWFyIHRv
IGJlIGVudGlyZWx5IGdyYXR1aXRvdXMuJm5ic3A7IEknZCBsaWtlIHRvIGdldCB0byB0aGUgYm90
dG9tIG9mIGVhY2ggYmVmb3JlIHdlIGNvbnRpbnVlLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij5BdCBhIG1pbmltdW0sIHRoZSBQUiB3ZSBsYW5kIGZpcnN0IHNob3VsZCBpbmNsdWRlIGp1
c3QgdGhlIGNvcmUgY2hhbmdlcy48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRl
eHQiPkFzIHlvdSBzYXksIHJldmlld2luZyBhIG1vbnN0ZXIgUFIgbGlrZSB0aGlzIHdpbGwgb25s
eSBtYWtlIEdpdEh1YiB3ZWVwIHVuaWNvcm5zLCBidXQgd2UgbWlnaHQgYmUgYWJsZSB0byBjdXQg
dGhpcyBpbnRvIHNtYWxsZXIgcGllY2VzLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5P
biBXZWQsIE1heSAyMywgMjAxOCBhdCAxMTozMSBBTSBJYW4gU3dldHQgJmx0O2lhbnN3ZXR0PSA8
YSBocmVmPSJtYWlsdG86NDBnb29nbGUuY29tQGRtYXJjLmlldGYub3JnIj4NCjxzcGFuIHN0eWxl
PSJjb2xvcjp3aW5kb3d0ZXh0O3RleHQtZGVjb3JhdGlvbjpub25lIj40MGdvb2dsZS5jb21AZG1h
cmMuaWV0Zi5vcmc8L3NwYW4+PC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPiZndDsgRGVhciBRVUlDIFdHLDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsgT24gYmVo
YWxmIG9mIHRoZSBTdHJlYW0gMCBEZXNpZ24gVGVhbSwgSSBhbSBwbGVhc2VkIHRvIHJlcG9ydCB0
aGF0IHdlPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5oYXZlIGNvbnNl
bnN1cyBvbiBhIHByb3Bvc2VkIGFwcHJvYWNoIHRvIHNoYXJlIHdpdGggdGhlIFdHLiBUaGUgRFQn
cyBwcm9wb3NhbCB3aWxsIG1ha2UgUVVJQyBhbmQgVExTIHdvcmsgY2xvc2VyIHRvZ2V0aGVyIGFu
ZCBpbmNvcnBvcmF0ZXMgaWRlYXMgZnJvbSBEVExTLCBidXQgaXQgZG9lcyBub3QgdXNlIHRoZSBE
VExTIHByb3RvY29sIGl0c2VsZi48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRl
eHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IFRoZSBEVCBiZWxp
ZXZlcyB0aGlzIHNvbHZlcyB0aGUgaW1wb3J0YW50IG9wZW4gU3RyZWFtIDAgaXNzdWVzLiBUaGU8
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPnByb3Bvc2FsIHdpbGwgYmUg
YSBiaXQgbW9yZSBpbnZhc2l2ZSBpbiBUTFMsIGJ1dCB3ZSBiZWxpZXZlIGl0IGlzIHRoZSByaWdo
dCBsb25nLXRlcm0gZGlyZWN0aW9uIGFuZCBzZXZlcmFsIFRMUyBzdGFja3MgKEJvcmluZ1NTTCwg
UGljb1RMUywgTlNTLCBhbmQ8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQi
Pk1pbnQpIGFyZSB3aWxsaW5nIGFuZCBhYmxlIHRvIGRvIHRoZSB3b3JrIG5lY2Vzc2FyeS4uIEEg
bnVtYmVyIG9mIHN0YWNrcyBhcmUgY3VycmVudGx5IHdvcmtpbmcgb24gaW1wbGVtZW50YXRpb25z
IG9mIHRoaXMgbmV3IGFwcHJvYWNoLCB3aGljaCB3ZSBob3BlIHRvIGhhdmUgaW4gdGltZSBmb3Ig
dGhlIEludGVyaW0gbWVldGluZy48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRl
eHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IEEgZGVzaWduIGRv
Y3VtZW50IGRlc2NyaWJpbmcgdGhlIG92ZXJhbGwgYXBwcm9hY2ggY2FuIGJlIGZvdW5kIGF0Ojxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPjxhIGhyZWY9Imh0dHBzOi8vZG9jcy5nb29nbGUuY29tL2RvY3Vt
ZW50L2QvMWZSc0pxUGluSmw4TjNiLWJmbERSVjZhdW9qZkpMa3hkZFQ5M2o2U3dIWTgvZWRpdCI+
PHNwYW4gc3R5bGU9ImNvbG9yOndpbmRvd3RleHQ7dGV4dC1kZWNvcmF0aW9uOm5vbmUiPmh0dHBz
Oi8vZG9jcy5nb29nbGUuY29tL2RvY3VtZW50L2QvMWZSc0pxUGluSmw4TjNiLWJmbERSVjZhdW9q
ZkpMa3hkZFQ5M2o2U3dIWTgvZWRpdDwvc3Bhbj48L2E+PG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jmd0
OyBBIFBSIG1ha2luZyB0aGUgY2hhbmdlcyB0byB0aGUgUVVJQyBkb2N1bWVudHMgY2FuIGJlIGZv
dW5kIGF0OjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IDxhIGhyZWY9Imh0dHBz
Oi8vZ2l0aHViLmNvbS9xdWljd2cvYmFzZS1kcmFmdHMvcHVsbC8xMzc3Ij4NCjxzcGFuIHN0eWxl
PSJjb2xvcjp3aW5kb3d0ZXh0O3RleHQtZGVjb3JhdGlvbjpub25lIj5odHRwczovL2dpdGh1Yi5j
b20vcXVpY3dnL2Jhc2UtZHJhZnRzL3B1bGwvMTM3Nzwvc3Bhbj48L2E+PG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+Jmd0OyBBIGZldyBkZXNpZ24gZGV0YWlscyBkaWQgbm90IGhhdmUgY2xlYXIgY29uc2Vu
c3VzLCBidXQgaXQgd2FzIGZlbHQgaXQ8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPndvdWxkIGJlIGJldHRlciB0byBkaXNjdXNzIHRob3NlIGluIHRoZSB3aWRlciBXRyB0
aGFuIGRlbGF5IHRoZSBkZXNpZ24gdGVhbS4mbmJzcDsgQSBjb25zaXN0ZW50IGNob2ljZSB3YXMg
bWFkZSBpbiB0aGUgUFIgYW5kIHRoZXNlIGlzc3VlcyBhcmUgbWVudGlvbmVkIGluIEFwcGVuZGl4
IEIgb2YgdGhlIGRlc2lnbiBkb2MuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jmd0OyBBcyBhbHdheXMs
IGNvbW1lbnRzIGFuZCBxdWVzdGlvbnMgd2VsY29tZS4gVGhhdCBzYWlkLCB0aGlzIGlzIGEgYmln
IFBSPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5hbmQgd2UgcmVjb2du
aXplIHRoYXQgc29tZSBlZGl0b3JpYWwgd29yayBpcyBnb2luZyB0byBiZSBuZWVkZWQgYmVmb3Jl
IG1lcmdpbmcuIEluIHRoZSBpbnRlcmVzdCBvZiBsZXR0aW5nIHBlb3BsZSBmb2xsb3cgYWxvbmcs
IGFuZCB0byBrZWVwIGdpdGh1YiBmcm9tIGZhbGxpbmcgb3Zlciwgd2UgYXNrIHBlb3BsZSB0byBr
ZWVwIGRpc2N1c3Npb24gb24gdGhlIG1haWxpbmcgbGlzdCBhbmQgcmVmcmFpbiBmcm9tDQogbWFr
aW5nIFBSIGNvbW1lbnRzLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZndDsgU2VlIHlvdSBpbiBLaXN0
YSE8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mZ3Q7IElhbiBhbmQgRXJpYzxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjwv
Ym9keT4NCjwvaHRtbD4NCg==

--_000_SN1PR08MB1854BF85FCCA0F21CE0DA1A4DA6B0SN1PR08MB1854namp_--


From nobody Wed May 23 15:26:45 2018
Return-Path: <mbishop@evequefou.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EE439127010 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 15:26:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 aopSDXbjuS1p for <quic@ietfa.amsl.com>; Wed, 23 May 2018 15:26:40 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0715.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe45::715]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0E714124D37 for <quic@ietf.org>; Wed, 23 May 2018 15:26:39 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=hJQ6FwrRSOMgiTViX/vj/KvtH+noD4oDlEkNvgaOHf8=; b=WPjUDrEz8GLc9rgRHMllQSTdk/GeVfAOkEhd8S6TBYL1Z3v5l2SCoVIcBwviLYJRnO+zvHR7c0ec0dJVlJz7gkICyp02+giuvxVi5z/G/gT7kQ1EkXwt5kGmt1hr1q/U7p5+MoCfXDRroIUMQbGsWdZLb5VpcGr4xiJvbWhyN+w=
Received: from SN1PR08MB1854.namprd08.prod.outlook.com (10.169.39.8) by SN1PR08MB1807.namprd08.prod.outlook.com (10.162.134.25) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.776.16; Wed, 23 May 2018 22:26:35 +0000
Received: from SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d]) by SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d%13]) with mapi id 15.20.0776.015; Wed, 23 May 2018 22:26:35 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Christian Huitema <huitema@huitema.net>, "quic@ietf.org" <quic@ietf.org>
Subject: RE: Stream0 Design Team Proposal
Thread-Topic: Stream0 Design Team Proposal
Thread-Index: AQHT8jXB/BpXll/I90GhSvtB/+hM26Q8oAsAgAAHFYCAACJqAIABG3Iw
Date: Wed, 23 May 2018 22:26:35 +0000
Message-ID: <SN1PR08MB1854C15D0B7806D0CCD30E70DA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CABkgnnUB=jqwFzb2rjBHUFzOgu0hX0YUgaf5kW5ENNGKP+mGiA@mail.gmail.com> <MWHPR15MB1821F33BAB20815A38EB34A2B66B0@MWHPR15MB1821.namprd15.prod.outlook.com> <046ee03d-a675-86b6-ed3b-4fa69288c42d@huitema.net>
In-Reply-To: <046ee03d-a675-86b6-ed3b-4fa69288c42d@huitema.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [2601:600:8080:5a28:4940:a32d:2658:89dc]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN1PR08MB1807; 7:E/xlQJf+1ih7CkkXz3CW1k/D9Ud3GBFtIDMQlWvEBVlbCiIAivgQLk1TdbBspP8CuDXy/4e8F+ozBMQ3MkaSnBg7lWIit8StKpt3guDmyrCdlqrzlT8un31aMu334Fu2Y2gMdK4URbEWHDIJAZXPQLLjU0WtRBTISTaWQHqWwRJ8ti/CEtqybS04kG72JI3y9AFeToI3R0l0HuE+A/cfHYqs9p4alKonR94Nzr9V1HXohoOgmE/W5hfHWCsN4Dvr
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(5600026)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(2017052603328)(7153060)(7193020); SRVR:SN1PR08MB1807; 
x-ms-traffictypediagnostic: SN1PR08MB1807:
x-microsoft-antispam-prvs: <SN1PR08MB1807D72C0A40E10CA593763ADA6B0@SN1PR08MB1807.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(158342451672863)(10436049006162)(166708455590820)(85827821059158)(211936372134217)(100405760836317)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93001095)(3002001)(3231254)(944501410)(52105095)(149027)(150027)(6041310)(20161123558120)(20161123564045)(20161123562045)(20161123560045)(2016111802025)(6072148)(6043046)(201708071742011)(7699016); SRVR:SN1PR08MB1807; BCL:0; PCL:0; RULEID:; SRVR:SN1PR08MB1807; 
x-forefront-prvs: 06818431B9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(396003)(39830400003)(366004)(376002)(39380400002)(51444003)(199004)(189003)(229853002)(6116002)(8676002)(790700001)(55016002)(76176011)(7696005)(99286004)(5660300001)(74482002)(74316002)(561944003)(33656002)(6506007)(68736007)(14454004)(316002)(7736002)(8936002)(53546011)(110136005)(59450400001)(6436002)(6306002)(9686003)(54896002)(93886005)(236005)(446003)(6246003)(46003)(105586002)(575784001)(86362001)(2900100001)(81156014)(966005)(25786009)(3280700002)(606006)(81166006)(5250100002)(97736004)(106356001)(53936002)(476003)(478600001)(102836004)(186003)(486006)(11346002)(2501003)(2906002)(3660700001); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR08MB1807; H:SN1PR08MB1854.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: VcM7dMwUdr/A3YLCAoF4htXNSrY7s+aE+RsZids8ht6ZV0Lu/Tk91RIUcOL2b+Z5S601n+PdnM4i6gOdaVMl469w+UeLgBWFgoosb2Z3F36MP1JeajhCx+fbYJu2oAoHS0R+RzOxuIuZ9KNe4lY4pubLfqVwr7kqoNR0V7RyNWfQxmp4gHfgoujCJ0vrEL/G
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_SN1PR08MB1854C15D0B7806D0CCD30E70DA6B0SN1PR08MB1854namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 07ef7f3a-76e3-4d25-2eea-08d5c0fc3e5a
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 07ef7f3a-76e3-4d25-2eea-08d5c0fc3e5a
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 May 2018 22:26:35.2088 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR08MB1807
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/lleOxiROQyAK0Di5NmjJwqPfFO0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 22:26:44 -0000

--_000_SN1PR08MB1854C15D0B7806D0CCD30E70DA6B0SN1PR08MB1854namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Christian, can you expand on why you dislike the EMPTY_ACK?  Being able to =
say "I've received some packets from you, but am unable to process any of t=
hem because I'm missing some handshake data" seems like a useful way to sho=
rt-circuit timeouts on clients.  It also doesn't commit the server to holdi=
ng any state - IIUC, a server could form a packet containing an EMPTY_ACK a=
nd then discard its internal state until it gets the retransmitted (or dela=
yed) Initial packet.

From: QUIC <quic-bounces@ietf.org> On Behalf Of Christian Huitema
Sent: Tuesday, May 22, 2018 10:29 PM
To: quic@ietf.org
Subject: Re: Stream0 Design Team Proposal


I like the proposal. In particular, I really like the encryption of handsha=
ke packets with the handshake key, as it does close a number of avenues for=
 attacks. And I like that it solves the "ack promotion" issue that I was co=
mplaining against for some time. Turns out that in the current draft, it is=
 very hard to contain that problem if you enable client auth.



On the other hand, I agree with Martin that a lot of the additions to trans=
mission recovery should be moved to separate PRs. I am not enthusiastic wit=
h the EMPTY ACK mechanism, or with the proposed "implicit acknowledgement" =
of a lower crypto stream by a higher level ack. In any case, starting as si=
mple as possible would help having the first implementations and tests.

On 5/22/2018 8:26 PM, Subodh Iyengar wrote:

As an implementor of fizz, I support this design and am willing to implemen=
t this as well.



While this is a change in the API that TLS classically exposes, I think thi=
s is the right tradeoff because it helps make things way more explicit whic=
h will prevent several other bugs from happening in the future.



Subodh

________________________________
From: QUIC <quic-bounces@ietf.org><mailto:quic-bounces@ietf.org> on behalf =
of Martin Thomson <martin.thomson@gmail.com><mailto:martin.thomson@gmail.co=
m>
Sent: Tuesday, May 22, 2018 8:00:40 PM
To: Ian Swett
Cc: ekr@mozilla.com<mailto:ekr@mozilla.com>; QUIC WG
Subject: Re: Stream0 Design Team Proposal

First of all, thanks to the design team for the work they have done.  I
haven't digested everything yet, but I think that I have a good sense of
the shape of the proposal.

Overall, this looks like a workable design.  It's a lot more invasive of
the cryptographic handshake implementation than I had thought people were
willing to stomach originally.  But it's clear that we've run into problems
with the current, more abstract API and this is a fairly natural way to
split TLS.  I've spent a little time thinking about how this might be
implemented and I think that it's not going to be *too* painful.  The proof
will be in the pudding there though.

In looking at the PR, I really appreciate seeing all the changes together.
BTW, the link above points to the wrong PR, so be careful (it appears to
have the same content, but that's not guaranteed).  The actual PR is here:
https://github.com/quicwg/base-drafts/pull/1377

I've pushed a branch to the main repo so that you can preview the entire
document set: https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__quicwg=
.github.io_base-2Ddrafts_stream0_&d=3DDwIBaQ&c=3D5VD0RTtNlTh3ycd41b3MUw&r=
=3Dh3Ju9EBS7mHtwg-wAyN7fQ&m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&s=
=3DususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&e=3D

It seems like there are some core changes here and a bunch of separable or
at least secondary changes.  I'm sure that each one has its own
justification, but that isn't always clear. The following changes seem like
they are separable:

* The use of separate packet number spaces
* The Retry packet changes (and NEW_TOKEN)
* EMPTY_ACK
* The TLS extension for flow control

Right now, some of these appear to be entirely gratuitous.  I'd like to get
to the bottom of each before we continue.

At a minimum, the PR we land first should include just the core changes.
As you say, reviewing a monster PR like this will only make GitHub weep
unicorns, but we might be able to cut this into smaller pieces.

On Wed, May 23, 2018 at 11:31 AM Ian Swett <ianswett=3D
40google.com@dmarc.ietf.org<mailto:40google.com@dmarc.ietf.org>> wrote:

> Dear QUIC WG,


> On behalf of the Stream 0 Design Team, I am pleased to report that we
have consensus on a proposed approach to share with the WG. The DT's
proposal will make QUIC and TLS work closer together and incorporates ideas
from DTLS, but it does not use the DTLS protocol itself.


> The DT believes this solves the important open Stream 0 issues. The
proposal will be a bit more invasive in TLS, but we believe it is the right
long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and
Mint) are willing and able to do the work necessary.. A number of stacks
are currently working on implementations of this new approach, which we
hope to have in time for the Interim meeting.


> A design document describing the overall approach can be found at:


https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__docs.google.com_docu=
ment_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8_edit&d=3DDwIBaQ&c=3D5=
VD0RTtNlTh3ycd41b3MUw&r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&m=3D_vGK3zTKFrMOkFihJnPntL=
Yw1T0_NEMiHYSM0Q_u1JA&s=3DjDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg&e=3D


> A PR making the changes to the QUIC documents can be found at:

> https://github.com/quicwg/base-drafts/pull/1377


> A few design details did not have clear consensus, but it was felt it
would be better to discuss those in the wider WG than delay the design
team.  A consistent choice was made in the PR and these issues are
mentioned in Appendix B of the design doc.


> As always, comments and questions welcome. That said, this is a big PR
and we recognize that some editorial work is going to be needed before
merging. In the interest of letting people follow along, and to keep github
from falling over, we ask people to keep discussion on the mailing list and
refrain from making PR comments.


> See you in Kista!


> Ian and Eric


--_000_SN1PR08MB1854C15D0B7806D0CCD30E70DA6B0SN1PR08MB1854namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	color:black;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	color:black;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body bgcolor=3D"white" lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:windowtext">Christian, can you =
expand on why you dislike the EMPTY_ACK?&nbsp; Being able to say &#8220;I&#=
8217;ve received some packets from you, but am unable to process any of the=
m because I&#8217;m missing some handshake data&#8221; seems like
 a useful way to short-circuit timeouts on clients.&nbsp; It also doesn&#82=
17;t commit the server to holding any state &#8211; IIUC, a server could fo=
rm a packet containing an EMPTY_ACK and then discard its internal state unt=
il it gets the retransmitted (or delayed) Initial
 packet.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span style=3D"color:windowtext"><o:p>&nbsp;</o:p></=
span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b><span style=3D"color:windowtext">From:</span></b>=
<span style=3D"color:windowtext"> QUIC &lt;quic-bounces@ietf.org&gt;
<b>On Behalf Of </b>Christian Huitema<br>
<b>Sent:</b> Tuesday, May 22, 2018 10:29 PM<br>
<b>To:</b> quic@ietf.org<br>
<b>Subject:</b> Re: Stream0 Design Team Proposal<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p>I like the proposal. In particular, I really like the encryption of hand=
shake packets with the handshake key, as it does close a number of avenues =
for attacks. And I like that it solves the &quot;ack promotion&quot; issue =
that I was complaining against for some time.
 Turns out that in the current draft, it is very hard to contain that probl=
em if you enable client auth.<o:p></o:p></p>
<p><o:p>&nbsp;</o:p></p>
<p>On the other hand, I agree with Martin that a lot of the additions to tr=
ansmission recovery should be moved to separate PRs. I am not enthusiastic =
with the EMPTY ACK mechanism, or with the proposed &quot;implicit acknowled=
gement&quot; of a lower crypto stream by a
 higher level ack. In any case, starting as simple as possible would help h=
aving the first implementations and tests.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">On 5/22/2018 8:26 PM, Subodh Iyengar wrote:<o:p></o:=
p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<div id=3D"divtagdefaultwrapper">
<p><span style=3D"font-size:12.0pt">As an implementor of fizz, I support th=
is design and am willing to implement this as well.
<o:p></o:p></span></p>
<p><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></span></p>
<p><span style=3D"font-size:12.0pt">While this is a change in the API that =
TLS classically exposes, I think this is the right tradeoff because it help=
s make things way more explicit which will prevent several other bugs from =
happening in the future.<o:p></o:p></span></p>
<p><span style=3D"font-size:12.0pt"><o:p>&nbsp;</o:p></span></p>
<p><span style=3D"font-size:12.0pt">Subodh<o:p></o:p></span></p>
</div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"98%" align=3D"center">
</div>
<div id=3D"divRplyFwdMsg">
<p class=3D"MsoNormal"><b>From:</b> QUIC <a href=3D"mailto:quic-bounces@iet=
f.org">&lt;quic-bounces@ietf.org&gt;</a> on behalf of Martin Thomson
<a href=3D"mailto:martin.thomson@gmail.com">&lt;martin.thomson@gmail.com&gt=
;</a><br>
<b>Sent:</b> Tuesday, May 22, 2018 8:00:40 PM<br>
<b>To:</b> Ian Swett<br>
<b>Cc:</b> <a href=3D"mailto:ekr@mozilla.com">ekr@mozilla.com</a>; QUIC WG<=
br>
<b>Subject:</b> Re: Stream0 Design Team Proposal <o:p></o:p></p>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">First of all, thanks =
to the design team for the work they have done.&nbsp; I<br>
haven't digested everything yet, but I think that I have a good sense of<br=
>
the shape of the proposal.<br>
<br>
Overall, this looks like a workable design.&nbsp; It's a lot more invasive =
of<br>
the cryptographic handshake implementation than I had thought people were<b=
r>
willing to stomach originally.&nbsp; But it's clear that we've run into pro=
blems<br>
with the current, more abstract API and this is a fairly natural way to<br>
split TLS.&nbsp; I've spent a little time thinking about how this might be<=
br>
implemented and I think that it's not going to be *too* painful.&nbsp; The =
proof<br>
will be in the pudding there though.<br>
<br>
In looking at the PR, I really appreciate seeing all the changes together.<=
br>
BTW, the link above points to the wrong PR, so be careful (it appears to<br=
>
have the same content, but that's not guaranteed).&nbsp; The actual PR is h=
ere:<br>
<a href=3D"https://github.com/quicwg/base-drafts/pull/1377">https://github.=
com/quicwg/base-drafts/pull/1377</a><br>
<br>
I've pushed a branch to the main repo so that you can preview the entire<br=
>
document set: <a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps=
-3A__quicwg.github.io_base-2Ddrafts_stream0_&amp;d=3DDwIBaQ&amp;c=3D5VD0RTt=
NlTh3ycd41b3MUw&amp;r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&amp;m=3D_vGK3zTKFrMOkFihJnPn=
tLYw1T0_NEMiHYSM0Q_u1JA&amp;s=3DususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak=
&amp;e=3D">
https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__quicwg.github.io_bas=
e-2Ddrafts_stream0_&amp;d=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3Dh=
3Ju9EBS7mHtwg-wAyN7fQ&amp;m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&a=
mp;s=3DususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&amp;e=3D</a><br>
<br>
It seems like there are some core changes here and a bunch of separable or<=
br>
at least secondary changes.&nbsp; I'm sure that each one has its own<br>
justification, but that isn't always clear. The following changes seem like=
<br>
they are separable:<br>
<br>
* The use of separate packet number spaces<br>
* The Retry packet changes (and NEW_TOKEN)<br>
* EMPTY_ACK<br>
* The TLS extension for flow control<br>
<br>
Right now, some of these appear to be entirely gratuitous.&nbsp; I'd like t=
o get<br>
to the bottom of each before we continue.<br>
<br>
At a minimum, the PR we land first should include just the core changes.<br=
>
As you say, reviewing a monster PR like this will only make GitHub weep<br>
unicorns, but we might be able to cut this into smaller pieces.<br>
<br>
On Wed, May 23, 2018 at 11:31 AM Ian Swett &lt;ianswett=3D<br>
<a href=3D"mailto:40google.com@dmarc.ietf.org">40google.com@dmarc.ietf.org<=
/a>&gt; wrote:<br>
<br>
&gt; Dear QUIC WG,<br>
<br>
<br>
&gt; On behalf of the Stream 0 Design Team, I am pleased to report that we<=
br>
have consensus on a proposed approach to share with the WG. The DT's<br>
proposal will make QUIC and TLS work closer together and incorporates ideas=
<br>
from DTLS, but it does not use the DTLS protocol itself.<br>
<br>
<br>
&gt; The DT believes this solves the important open Stream 0 issues. The<br=
>
proposal will be a bit more invasive in TLS, but we believe it is the right=
<br>
long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and<br=
>
Mint) are willing and able to do the work necessary.. A number of stacks<br=
>
are currently working on implementations of this new approach, which we<br>
hope to have in time for the Interim meeting.<br>
<br>
<br>
&gt; A design document describing the overall approach can be found at:<br>
<br>
<br>
<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__docs.goog=
le.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8_edit&amp;d=
=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&amp=
;m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&amp;s=3DjDNnz34hmWvLSQnHkS=
nYdihW-jG-0xZ-YYqKq30wVGg&amp;e=3D">https://urldefense.proofpoint.com/v2/ur=
l?u=3Dhttps-3A__docs.google.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJL=
kxddT93j6SwHY8_edit&amp;d=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3Dh=
3Ju9EBS7mHtwg-wAyN7fQ&amp;m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&a=
mp;s=3DjDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg&amp;e=3D</a><br>
<br>
<br>
&gt; A PR making the changes to the QUIC documents can be found at:<br>
<br>
&gt; <a href=3D"https://github.com/quicwg/base-drafts/pull/1377">https://gi=
thub.com/quicwg/base-drafts/pull/1377</a><br>
<br>
<br>
&gt; A few design details did not have clear consensus, but it was felt it<=
br>
would be better to discuss those in the wider WG than delay the design<br>
team.&nbsp; A consistent choice was made in the PR and these issues are<br>
mentioned in Appendix B of the design doc.<br>
<br>
<br>
&gt; As always, comments and questions welcome. That said, this is a big PR=
<br>
and we recognize that some editorial work is going to be needed before<br>
merging. In the interest of letting people follow along, and to keep github=
<br>
from falling over, we ask people to keep discussion on the mailing list and=
<br>
refrain from making PR comments.<br>
<br>
<br>
&gt; See you in Kista!<br>
<br>
<br>
&gt; Ian and Eric<o:p></o:p></p>
</div>
</div>
</blockquote>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_SN1PR08MB1854C15D0B7806D0CCD30E70DA6B0SN1PR08MB1854namp_--


From nobody Wed May 23 15:37:30 2018
Return-Path: <prvs=86810e156b=subodh@fb.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 508FA127369 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 15:37:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level: 
X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, T_DKIMWL_WL_MED=-0.01, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=BUix24dG; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=M7Ihl6mD
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 umj8LeLZmyP4 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 15:37:26 -0700 (PDT)
Received: from mx0b-00082601.pphosted.com (mx0b-00082601.pphosted.com [67.231.153.30]) (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 4610E124D37 for <quic@ietf.org>; Wed, 23 May 2018 15:37:26 -0700 (PDT)
Received: from pps.filterd (m0148460.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w4NMYebL006241; Wed, 23 May 2018 15:37:15 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=facebook; bh=BvIRwh+BbQ/ZVxrsDSQAbM6AM0IS4SETv1tlDZuwHB8=; b=BUix24dGgpNfSKNghBp+lLAXJ4yfzQaadobH4vEPxhkTNe1T7RXxwr1eduPRcRnub1BH 1A4ESBt1tUmPbnHjJ3C2u+UV9c2TDDNpyjnfI+SOQ623P92AO9V8UFUhoIa2pjofI+hK qjTvPR7N55h2++wUXZpFa3XPClHzP2xWD3Y= 
Received: from mail.thefacebook.com ([199.201.64.23]) by mx0a-00082601.pphosted.com with ESMTP id 2j5fc0gapd-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 23 May 2018 15:37:14 -0700
Received: from NAM01-SN1-obe.outbound.protection.outlook.com (192.168.54.28) by o365-in.thefacebook.com (192.168.16.20) with Microsoft SMTP Server (TLS) id 14.3.361.1; Wed, 23 May 2018 15:37:11 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=BvIRwh+BbQ/ZVxrsDSQAbM6AM0IS4SETv1tlDZuwHB8=; b=M7Ihl6mD5vvK6zHy48E1M7pdPp2/ogIw/IlOKHvEhyApmkMAaiXstx+ZSLkAUZuQhEvJaFQjSL5y3+Vzu5Yvf2gFcwoYjPTKHHUV5o8B6EkkMDqnUzxg7ZC0P+xkZSShhMmhv7sm6QUDUAdKzFjjMbKhkuHpgd3XZPFrqkKun2M=
Received: from MWHPR15MB1821.namprd15.prod.outlook.com (10.174.255.137) by MWHPR15MB1933.namprd15.prod.outlook.com (10.174.100.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.797.11; Wed, 23 May 2018 22:37:09 +0000
Received: from MWHPR15MB1821.namprd15.prod.outlook.com ([fe80::808f:5749:11db:a6a4]) by MWHPR15MB1821.namprd15.prod.outlook.com ([fe80::808f:5749:11db:a6a4%18]) with mapi id 15.20.0776.019; Wed, 23 May 2018 22:37:09 +0000
From: Subodh Iyengar <subodh@fb.com>
To: Mike Bishop <mbishop@evequefou.be>, Christian Huitema <huitema@huitema.net>, "quic@ietf.org" <quic@ietf.org>
Subject: Re: Stream0 Design Team Proposal
Thread-Topic: Stream0 Design Team Proposal
Thread-Index: AQHT8jXGhBLiPTEoUE2u+pT4iGJsEaQ8oAoAgAAGHGiAACNkAIABHEGAgAACW9E=
Date: Wed, 23 May 2018 22:37:09 +0000
Message-ID: <MWHPR15MB18217FABBB1021C1D8C59952B66B0@MWHPR15MB1821.namprd15.prod.outlook.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CABkgnnUB=jqwFzb2rjBHUFzOgu0hX0YUgaf5kW5ENNGKP+mGiA@mail.gmail.com> <MWHPR15MB1821F33BAB20815A38EB34A2B66B0@MWHPR15MB1821.namprd15.prod.outlook.com> <046ee03d-a675-86b6-ed3b-4fa69288c42d@huitema.net>, <SN1PR08MB1854C15D0B7806D0CCD30E70DA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
In-Reply-To: <SN1PR08MB1854C15D0B7806D0CCD30E70DA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2620:10d:c090:180::1:29f2]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; MWHPR15MB1933; 7:O6QK+NtEo+Ci0HLS6mJ7nmJmE9mESHjxZH/RDmraMStNSzZtzt2EcpDvYyzMnl3rR1tX8QmZXNi/gJ5MZW2mgbmes9iknjjFZEFVvkyTrweSMdyF9KaYW60ORnjiut9Qp9b93oprS7+axC3Zxe3KFTuuhaPPI2qCOc6kRVUbZI48Q1s12WxdrJ++GoAZz0F4tcT1aJw/RP4MGBi0o+naHSrnm3+Cq0IpbZQ4lDiH3QBsWm3gsn9+zvMQQQFZZUyD; 20:H/hqclRygitQDXAT1ZjVk051WCjxiYB10dZf29iXkIzIu4DfhanorotE96aUlT40pXKtVRONyPC8kpbs2NRyfOhlePvUurETFrXo77cU3uWaTNPL5pJ4+V/JuTFKa3dOr06hT6DL7QezPuXk3U1AxbwWIQL2wcqtKNF1zKmon2k=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:MWHPR15MB1933; 
x-ms-traffictypediagnostic: MWHPR15MB1933:
x-microsoft-antispam-prvs: <MWHPR15MB1933D34F6AE69DE1D8AEE6DDB66B0@MWHPR15MB1933.namprd15.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(10436049006162)(166708455590820)(85827821059158)(211936372134217)(100405760836317);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(3231254)(11241501184)(944501410)(52105095)(93006095)(93001095)(10201501046)(3002001)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123558120)(20161123562045)(20161123560045)(6072148)(201708071742011)(7699016); SRVR:MWHPR15MB1933; BCL:0; PCL:0; RULEID:; SRVR:MWHPR15MB1933; 
x-forefront-prvs: 06818431B9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(366004)(346002)(376002)(396003)(39380400002)(189003)(199004)(51444003)(7736002)(97736004)(606006)(46003)(6116002)(14454004)(81166006)(55016002)(476003)(5660300001)(486006)(2900100001)(11346002)(446003)(54896002)(6306002)(236005)(6506007)(102836004)(9686003)(53936002)(6246003)(59450400001)(25786009)(5250100002)(2501003)(186003)(53546011)(86362001)(575784001)(105586002)(561944003)(106356001)(76176011)(93886005)(229853002)(33656002)(110136005)(6436002)(99286004)(2906002)(7696005)(3660700001)(3280700002)(68736007)(19627405001)(966005)(478600001)(8676002)(74316002)(6606003)(8936002)(316002)(81156014)(19627235001); DIR:OUT; SFP:1102; SCL:1; SRVR:MWHPR15MB1933; H:MWHPR15MB1821.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: fb.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 8bFkx+CuQD87+WXZNBtkhCHRRpNiL5DVl7cjTgb8ZCHiCdtZVpHeUs70aqI0ghP8en63fwCsCU1g+cQUp3vNN62OWYDSFbjA39xrz7Ldj5NtTjj19eUSwEujoWDZziTKVX1dgxn2/hfNnhiBd+/t2liwS1LBI2Hf1vc5Xt0GIWtbphX3I9n+TGzK6r9SN6pS
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_MWHPR15MB18217FABBB1021C1D8C59952B66B0MWHPR15MB1821namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 4d2c7cbd-1851-45dd-9739-08d5c0fdb853
X-MS-Exchange-CrossTenant-Network-Message-Id: 4d2c7cbd-1851-45dd-9739-08d5c0fdb853
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 May 2018 22:37:09.2819 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: MWHPR15MB1933
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-23_08:, , signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/R3q3zn64eFAUahPIlT2j10k2Fug>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 22:37:30 -0000

--_000_MWHPR15MB18217FABBB1021C1D8C59952B66B0MWHPR15MB1821namp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

FWIW I see EMPTY_ACKs as being very similar to a Duplicate ack. We thought =
about using Duplicate acks as well but we thought that EMPTY_ACks would be =
simpler to implement and be able to convey similar information.


Subodh

________________________________
From: QUIC <quic-bounces@ietf.org> on behalf of Mike Bishop <mbishop@eveque=
fou.be>
Sent: Wednesday, May 23, 2018 3:26:35 PM
To: Christian Huitema; quic@ietf.org
Subject: RE: Stream0 Design Team Proposal


Christian, can you expand on why you dislike the EMPTY_ACK?  Being able to =
say =93I=92ve received some packets from you, but am unable to process any =
of them because I=92m missing some handshake data=94 seems like a useful wa=
y to short-circuit timeouts on clients.  It also doesn=92t commit the serve=
r to holding any state =96 IIUC, a server could form a packet containing an=
 EMPTY_ACK and then discard its internal state until it gets the retransmit=
ted (or delayed) Initial packet.



From: QUIC <quic-bounces@ietf.org> On Behalf Of Christian Huitema
Sent: Tuesday, May 22, 2018 10:29 PM
To: quic@ietf.org
Subject: Re: Stream0 Design Team Proposal



I like the proposal. In particular, I really like the encryption of handsha=
ke packets with the handshake key, as it does close a number of avenues for=
 attacks. And I like that it solves the "ack promotion" issue that I was co=
mplaining against for some time. Turns out that in the current draft, it is=
 very hard to contain that problem if you enable client auth.



On the other hand, I agree with Martin that a lot of the additions to trans=
mission recovery should be moved to separate PRs. I am not enthusiastic wit=
h the EMPTY ACK mechanism, or with the proposed "implicit acknowledgement" =
of a lower crypto stream by a higher level ack. In any case, starting as si=
mple as possible would help having the first implementations and tests.



On 5/22/2018 8:26 PM, Subodh Iyengar wrote:

As an implementor of fizz, I support this design and am willing to implemen=
t this as well.



While this is a change in the API that TLS classically exposes, I think thi=
s is the right tradeoff because it helps make things way more explicit whic=
h will prevent several other bugs from happening in the future.



Subodh

________________________________

From: QUIC <quic-bounces@ietf.org><mailto:quic-bounces@ietf.org> on behalf =
of Martin Thomson <martin.thomson@gmail.com><mailto:martin.thomson@gmail.co=
m>
Sent: Tuesday, May 22, 2018 8:00:40 PM
To: Ian Swett
Cc: ekr@mozilla.com<mailto:ekr@mozilla.com>; QUIC WG
Subject: Re: Stream0 Design Team Proposal



First of all, thanks to the design team for the work they have done.  I
haven't digested everything yet, but I think that I have a good sense of
the shape of the proposal.

Overall, this looks like a workable design.  It's a lot more invasive of
the cryptographic handshake implementation than I had thought people were
willing to stomach originally.  But it's clear that we've run into problems
with the current, more abstract API and this is a fairly natural way to
split TLS.  I've spent a little time thinking about how this might be
implemented and I think that it's not going to be *too* painful.  The proof
will be in the pudding there though.

In looking at the PR, I really appreciate seeing all the changes together.
BTW, the link above points to the wrong PR, so be careful (it appears to
have the same content, but that's not guaranteed).  The actual PR is here:
https://github.com/quicwg/base-drafts/pull/1377

I've pushed a branch to the main repo so that you can preview the entire
document set: https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__quicwg=
.github.io_base-2Ddrafts_stream0_&d=3DDwIBaQ&c=3D5VD0RTtNlTh3ycd41b3MUw&r=
=3Dh3Ju9EBS7mHtwg-wAyN7fQ&m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&s=
=3DususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&e=3D

It seems like there are some core changes here and a bunch of separable or
at least secondary changes.  I'm sure that each one has its own
justification, but that isn't always clear. The following changes seem like
they are separable:

* The use of separate packet number spaces
* The Retry packet changes (and NEW_TOKEN)
* EMPTY_ACK
* The TLS extension for flow control

Right now, some of these appear to be entirely gratuitous.  I'd like to get
to the bottom of each before we continue.

At a minimum, the PR we land first should include just the core changes.
As you say, reviewing a monster PR like this will only make GitHub weep
unicorns, but we might be able to cut this into smaller pieces.

On Wed, May 23, 2018 at 11:31 AM Ian Swett <ianswett=3D
40google.com@dmarc.ietf.org<mailto:40google.com@dmarc.ietf.org>> wrote:

> Dear QUIC WG,


> On behalf of the Stream 0 Design Team, I am pleased to report that we
have consensus on a proposed approach to share with the WG. The DT's
proposal will make QUIC and TLS work closer together and incorporates ideas
from DTLS, but it does not use the DTLS protocol itself.


> The DT believes this solves the important open Stream 0 issues. The
proposal will be a bit more invasive in TLS, but we believe it is the right
long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and
Mint) are willing and able to do the work necessary.. A number of stacks
are currently working on implementations of this new approach, which we
hope to have in time for the Interim meeting.


> A design document describing the overall approach can be found at:


https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__docs.google.com_docu=
ment_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8_edit&d=3DDwIBaQ&c=3D5=
VD0RTtNlTh3ycd41b3MUw&r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&m=3D_vGK3zTKFrMOkFihJnPntL=
Yw1T0_NEMiHYSM0Q_u1JA&s=3DjDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg&e=3D


> A PR making the changes to the QUIC documents can be found at:

> https://github.com/quicwg/base-drafts/pull/1377


> A few design details did not have clear consensus, but it was felt it
would be better to discuss those in the wider WG than delay the design
team.  A consistent choice was made in the PR and these issues are
mentioned in Appendix B of the design doc.


> As always, comments and questions welcome. That said, this is a big PR
and we recognize that some editorial work is going to be needed before
merging. In the interest of letting people follow along, and to keep github
from falling over, we ask people to keep discussion on the mailing list and
refrain from making PR comments.


> See you in Kista!


> Ian and Eric



--_000_MWHPR15MB18217FABBB1021C1D8C59952B66B0MWHPR15MB1821namp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<style type=3D"text/css" style=3D"display:none;"><!-- P {margin-top:0;margi=
n-bottom:0;} --></style>
</head>
<body dir=3D"ltr">
<div id=3D"divtagdefaultwrapper" style=3D"font-size:12pt;color:#000000;font=
-family:Calibri,Helvetica,sans-serif;" dir=3D"ltr">
<p style=3D"margin-top:0;margin-bottom:0">FWIW I see EMPTY_ACKs as being ve=
ry similar to a Duplicate ack. We thought about using Duplicate acks as wel=
l but we thought that EMPTY_ACks would be simpler to implement and be able =
to convey similar&nbsp;information.<br>
</p>
<p style=3D"margin-top:0;margin-bottom:0"><br>
</p>
<p style=3D"margin-top:0;margin-bottom:0">Subodh<br>
</p>
</div>
<hr style=3D"display:inline-block;width:98%" tabindex=3D"-1">
<div id=3D"divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" st=
yle=3D"font-size:11pt" color=3D"#000000"><b>From:</b> QUIC &lt;quic-bounces=
@ietf.org&gt; on behalf of Mike Bishop &lt;mbishop@evequefou.be&gt;<br>
<b>Sent:</b> Wednesday, May 23, 2018 3:26:35 PM<br>
<b>To:</b> Christian Huitema; quic@ietf.org<br>
<b>Subject:</b> RE: Stream0 Design Team Proposal</font>
<div>&nbsp;</div>
</div>
<meta content=3D"text/html; charset=3DWindows-1252">
<meta name=3D"x_Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style>
<!--
@font-face
	{font-family:"Cambria Math"}
@font-face
	{font-family:Calibri}
p.x_MsoNormal, li.x_MsoNormal, div.x_MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	color:black}
a:x_link, span.x_MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:x_visited, span.x_MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
p.x_msonormal0, li.x_msonormal0, div.x_msonormal0
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	color:black}
span.x_EmailStyle19
	{font-family:"Calibri",sans-serif;
	color:windowtext}
span.x_EmailStyle20
	{font-family:"Calibri",sans-serif;
	color:windowtext}
@page WordSection1
	{margin:1.0in 1.0in 1.0in 1.0in}
div.x_WordSection1
	{}
-->
</style>
<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple" style=3D"background-colo=
r:white">
<div class=3D"x_WordSection1">
<p class=3D"x_MsoNormal"><span style=3D"color:windowtext">Christian, can yo=
u expand on why you dislike the EMPTY_ACK?&nbsp; Being able to say =93I=92v=
e received some packets from you, but am unable to process any of them beca=
use I=92m missing some handshake data=94 seems like
 a useful way to short-circuit timeouts on clients.&nbsp; It also doesn=92t=
 commit the server to holding any state =96 IIUC, a server could form a pac=
ket containing an EMPTY_ACK and then discard its internal state until it ge=
ts the retransmitted (or delayed) Initial
 packet.</span></p>
<p class=3D"x_MsoNormal"><span style=3D"color:windowtext">&nbsp;</span></p>
<div>
<div style=3D"border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0i=
n 0in 0in">
<p class=3D"x_MsoNormal"><b><span style=3D"color:windowtext">From:</span></=
b><span style=3D"color:windowtext"> QUIC &lt;quic-bounces@ietf.org&gt;
<b>On Behalf Of </b>Christian Huitema<br>
<b>Sent:</b> Tuesday, May 22, 2018 10:29 PM<br>
<b>To:</b> quic@ietf.org<br>
<b>Subject:</b> Re: Stream0 Design Team Proposal</span></p>
</div>
</div>
<p class=3D"x_MsoNormal">&nbsp;</p>
<p>I like the proposal. In particular, I really like the encryption of hand=
shake packets with the handshake key, as it does close a number of avenues =
for attacks. And I like that it solves the &quot;ack promotion&quot; issue =
that I was complaining against for some time.
 Turns out that in the current draft, it is very hard to contain that probl=
em if you enable client auth.</p>
<p>&nbsp;</p>
<p>On the other hand, I agree with Martin that a lot of the additions to tr=
ansmission recovery should be moved to separate PRs. I am not enthusiastic =
with the EMPTY ACK mechanism, or with the proposed &quot;implicit acknowled=
gement&quot; of a lower crypto stream by a
 higher level ack. In any case, starting as simple as possible would help h=
aving the first implementations and tests.</p>
<p class=3D"x_MsoNormal">&nbsp;</p>
<div>
<p class=3D"x_MsoNormal">On 5/22/2018 8:26 PM, Subodh Iyengar wrote:</p>
</div>
<blockquote style=3D"margin-top:5.0pt; margin-bottom:5.0pt">
<div id=3D"x_divtagdefaultwrapper">
<p><span style=3D"font-size:12.0pt">As an implementor of fizz, I support th=
is design and am willing to implement this as well.
</span></p>
<p><span style=3D"font-size:12.0pt">&nbsp;</span></p>
<p><span style=3D"font-size:12.0pt">While this is a change in the API that =
TLS classically exposes, I think this is the right tradeoff because it help=
s make things way more explicit which will prevent several other bugs from =
happening in the future.</span></p>
<p><span style=3D"font-size:12.0pt">&nbsp;</span></p>
<p><span style=3D"font-size:12.0pt">Subodh</span></p>
</div>
<div class=3D"x_MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"98%" align=3D"center">
</div>
<div id=3D"x_divRplyFwdMsg">
<p class=3D"x_MsoNormal"><b>From:</b> QUIC <a href=3D"mailto:quic-bounces@i=
etf.org">&lt;quic-bounces@ietf.org&gt;</a> on behalf of Martin Thomson
<a href=3D"mailto:martin.thomson@gmail.com">&lt;martin.thomson@gmail.com&gt=
;</a><br>
<b>Sent:</b> Tuesday, May 22, 2018 8:00:40 PM<br>
<b>To:</b> Ian Swett<br>
<b>Cc:</b> <a href=3D"mailto:ekr@mozilla.com">ekr@mozilla.com</a>; QUIC WG<=
br>
<b>Subject:</b> Re: Stream0 Design Team Proposal </p>
<div>
<p class=3D"x_MsoNormal">&nbsp;</p>
</div>
</div>
<div>
<div>
<p class=3D"x_MsoNormal" style=3D"margin-bottom:12.0pt">First of all, thank=
s to the design team for the work they have done.&nbsp; I<br>
haven't digested everything yet, but I think that I have a good sense of<br=
>
the shape of the proposal.<br>
<br>
Overall, this looks like a workable design.&nbsp; It's a lot more invasive =
of<br>
the cryptographic handshake implementation than I had thought people were<b=
r>
willing to stomach originally.&nbsp; But it's clear that we've run into pro=
blems<br>
with the current, more abstract API and this is a fairly natural way to<br>
split TLS.&nbsp; I've spent a little time thinking about how this might be<=
br>
implemented and I think that it's not going to be *too* painful.&nbsp; The =
proof<br>
will be in the pudding there though.<br>
<br>
In looking at the PR, I really appreciate seeing all the changes together.<=
br>
BTW, the link above points to the wrong PR, so be careful (it appears to<br=
>
have the same content, but that's not guaranteed).&nbsp; The actual PR is h=
ere:<br>
<a href=3D"https://github.com/quicwg/base-drafts/pull/1377">https://github.=
com/quicwg/base-drafts/pull/1377</a><br>
<br>
I've pushed a branch to the main repo so that you can preview the entire<br=
>
document set: <a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps=
-3A__quicwg.github.io_base-2Ddrafts_stream0_&amp;d=3DDwIBaQ&amp;c=3D5VD0RTt=
NlTh3ycd41b3MUw&amp;r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&amp;m=3D_vGK3zTKFrMOkFihJnPn=
tLYw1T0_NEMiHYSM0Q_u1JA&amp;s=3DususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak=
&amp;e=3D">
https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__quicwg.github.io_bas=
e-2Ddrafts_stream0_&amp;d=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3Dh=
3Ju9EBS7mHtwg-wAyN7fQ&amp;m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&a=
mp;s=3DususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&amp;e=3D</a><br>
<br>
It seems like there are some core changes here and a bunch of separable or<=
br>
at least secondary changes.&nbsp; I'm sure that each one has its own<br>
justification, but that isn't always clear. The following changes seem like=
<br>
they are separable:<br>
<br>
* The use of separate packet number spaces<br>
* The Retry packet changes (and NEW_TOKEN)<br>
* EMPTY_ACK<br>
* The TLS extension for flow control<br>
<br>
Right now, some of these appear to be entirely gratuitous.&nbsp; I'd like t=
o get<br>
to the bottom of each before we continue.<br>
<br>
At a minimum, the PR we land first should include just the core changes.<br=
>
As you say, reviewing a monster PR like this will only make GitHub weep<br>
unicorns, but we might be able to cut this into smaller pieces.<br>
<br>
On Wed, May 23, 2018 at 11:31 AM Ian Swett &lt;ianswett=3D<br>
<a href=3D"mailto:40google.com@dmarc.ietf.org">40google.com@dmarc.ietf.org<=
/a>&gt; wrote:<br>
<br>
&gt; Dear QUIC WG,<br>
<br>
<br>
&gt; On behalf of the Stream 0 Design Team, I am pleased to report that we<=
br>
have consensus on a proposed approach to share with the WG. The DT's<br>
proposal will make QUIC and TLS work closer together and incorporates ideas=
<br>
from DTLS, but it does not use the DTLS protocol itself.<br>
<br>
<br>
&gt; The DT believes this solves the important open Stream 0 issues. The<br=
>
proposal will be a bit more invasive in TLS, but we believe it is the right=
<br>
long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and<br=
>
Mint) are willing and able to do the work necessary.. A number of stacks<br=
>
are currently working on implementations of this new approach, which we<br>
hope to have in time for the Interim meeting.<br>
<br>
<br>
&gt; A design document describing the overall approach can be found at:<br>
<br>
<br>
<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__docs.goog=
le.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8_edit&amp;d=
=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&amp=
;m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&amp;s=3DjDNnz34hmWvLSQnHkS=
nYdihW-jG-0xZ-YYqKq30wVGg&amp;e=3D">https://urldefense.proofpoint.com/v2/ur=
l?u=3Dhttps-3A__docs.google.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJL=
kxddT93j6SwHY8_edit&amp;d=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3Dh=
3Ju9EBS7mHtwg-wAyN7fQ&amp;m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&a=
mp;s=3DjDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg&amp;e=3D</a><br>
<br>
<br>
&gt; A PR making the changes to the QUIC documents can be found at:<br>
<br>
&gt; <a href=3D"https://github.com/quicwg/base-drafts/pull/1377">https://gi=
thub.com/quicwg/base-drafts/pull/1377</a><br>
<br>
<br>
&gt; A few design details did not have clear consensus, but it was felt it<=
br>
would be better to discuss those in the wider WG than delay the design<br>
team.&nbsp; A consistent choice was made in the PR and these issues are<br>
mentioned in Appendix B of the design doc.<br>
<br>
<br>
&gt; As always, comments and questions welcome. That said, this is a big PR=
<br>
and we recognize that some editorial work is going to be needed before<br>
merging. In the interest of letting people follow along, and to keep github=
<br>
from falling over, we ask people to keep discussion on the mailing list and=
<br>
refrain from making PR comments.<br>
<br>
<br>
&gt; See you in Kista!<br>
<br>
<br>
&gt; Ian and Eric</p>
</div>
</div>
</blockquote>
<p class=3D"x_MsoNormal">&nbsp;</p>
</div>
</div>
</body>
</html>

--_000_MWHPR15MB18217FABBB1021C1D8C59952B66B0MWHPR15MB1821namp_--


From nobody Wed May 23 16:00:47 2018
Return-Path: <kazuhooku@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1A80612D7F9 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:00:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 OTGjiy2sWfUL for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:00:43 -0700 (PDT)
Received: from mail-pg0-x22c.google.com (mail-pg0-x22c.google.com [IPv6:2607:f8b0:400e:c05::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 469FE12D7F0 for <quic@ietf.org>; Wed, 23 May 2018 16:00:43 -0700 (PDT)
Received: by mail-pg0-x22c.google.com with SMTP id p8-v6so10048830pgq.10 for <quic@ietf.org>; Wed, 23 May 2018 16:00:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=VmBkXE4d/j7DvhXlucg0Z+Ji2OkKKPKXGSSbsWd63HE=; b=gtNZwiilBp5VuEOCEN9VdC3Das8BZOMuGRTIffjOycd6sz5IbqugHpb27RmBK/miGH 3NXZAJeES8kTOWIpp1icUiWPiDq7TU7wlg4063lGDfKGAiB5pSAcUwmY9tZTwmnwzyBB go5KKu40s1vLHVdEVCMVv272ev9FKIZ4IGxqX2l9Q3MlIIziYGCyC4Pv3nJtvgJ1O39t 3g2EDrcDbw+RZ10Tuym8RClujSsYHWN/AjEk6BMfETGgYMpwi1y/ItEZfn4WDwhtZWoH sTO63HMsappQhFYmge9TgCLg0wj6+AKPAoK89zPRfZsJvk+KJQ+iuDzi4mCTSXRPTBff Jslg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=VmBkXE4d/j7DvhXlucg0Z+Ji2OkKKPKXGSSbsWd63HE=; b=MR55WH/172DgIabKAPsWDKW/jko24o1RSdxWbPHQ0BWWoGVvEpU4jEXi4VvN1rLVHu rMWSw+S1y1rAIvPj4vIcWlceAukZ52Gl0c5yFg/u+On8v71yaEAinTvI8zqf57JBL/vr 2ACDOeaE3tRounL0w0P5E0MxG1rD9sFbr+vpgBC7iixoQH+I5j4CRNX8rJ5J8mzVraFi bv7GVKrfGeUHpYQie1mc8jq2bZ+DNMjnFFQnpeDV9XuMYpvP9t4wlCwaPWs3j+UjmYw0 sBQv7oBBzRddZ7tijAjxzmtv97AFoHreJfH5hQ7269LYuxVTHmlYLv2KIocg3GimCdVV W5yQ==
X-Gm-Message-State: ALKqPwfr18yF1g0p0A94QyxwX2o+zXCeUxT5zCXcIe6dYD1lOnOnFDD8 Z3ia495MMREuJ8DPAxO3QkzqUFHH5hSiXHEHcxE=
X-Google-Smtp-Source: AB8JxZru9TLr9tjlyGqJGsuuoNQava8/hesxL6zz3/31ahxTpg33Bi897oErPRtkMQqc/RnjYhHiHHy44PQy8nIJdcc=
X-Received: by 2002:a65:44c3:: with SMTP id g3-v6mr3760290pgs.428.1527116441528;  Wed, 23 May 2018 16:00:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:1189:0:0:0:0 with HTTP; Wed, 23 May 2018 16:00:40 -0700 (PDT)
In-Reply-To: <SN1PR08MB1854074075313C93BC71A6F1DA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CABkgnnUB=jqwFzb2rjBHUFzOgu0hX0YUgaf5kW5ENNGKP+mGiA@mail.gmail.com> <MWHPR15MB1821F33BAB20815A38EB34A2B66B0@MWHPR15MB1821.namprd15.prod.outlook.com> <046ee03d-a675-86b6-ed3b-4fa69288c42d@huitema.net> <CANatvzzn1VuAY2+cc8vpo75N3T=VH7YkSTjRC6uB4HATAFfW4Q@mail.gmail.com> <SN1PR08MB1854074075313C93BC71A6F1DA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Thu, 24 May 2018 08:00:40 +0900
Message-ID: <CANatvzxRhuDf0-nV88unj6x7DZQfcM_o3DjELw9-xbEqZcAmdw@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: Mike Bishop <mbishop@evequefou.be>
Cc: Christian Huitema <huitema@huitema.net>, IETF QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/1Q7K8SaQnhBlyYl5apdKdVLcFrU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 23:00:46 -0000

2018-05-24 7:14 GMT+09:00 Mike Bishop <mbishop@evequefou.be>:
> While a HS_DONE frame sent under 1-RTT would simplify some things, I'm no=
t sure that it's required.  There's a very clear synchronization point whic=
h already exists.
>
> The client can't send 1-RTT messages until it has sent Client Finished.  =
The server can send, but not process, 1-RTT messages prior to receiving Cli=
ent Finished.  (This is a spec requirement rather than a crypto limitation,=
 however, so a buggy server might violate it.)  Thus, an ACK for any 1-RTT =
packet from the client implicitly acknowledges the client's entire handshak=
e.  Receipt of any 1-RTT packet from the client implicitly acknowledges the=
 server's entire handshake.

That is true.

However, I think that the issue remains in case where 0-RTT is
involved. If the client sends it's request using a 0-RTT packet and
the server ACKs and sends a response in 0.5-RTT, there will be no
1-RTT packets from server after ClientFinished is delivered to the
server.

> -----Original Message-----
> From: QUIC <quic-bounces@ietf.org> On Behalf Of Kazuho Oku
> Sent: Wednesday, May 23, 2018 2:14 AM
> To: Christian Huitema <huitema@huitema.net>
> Cc: IETF QUIC WG <quic@ietf.org>
> Subject: Re: Stream0 Design Team Proposal
>
> 2018-05-23 14:29 GMT+09:00 Christian Huitema <huitema@huitema.net>:
>> I like the proposal. In particular, I really like the encryption of
>> handshake packets with the handshake key, as it does close a number of
>> avenues for attacks. And I like that it solves the "ack promotion"
>> issue that I was complaining against for some time. Turns out that in
>> the current draft, it is very hard to contain that problem if you enable=
 client auth.
>>
>>
>> On the other hand, I agree with Martin that a lot of the additions to
>> transmission recovery should be moved to separate PRs. I am not
>> enthusiastic with the EMPTY ACK mechanism, or with the proposed
>> "implicit acknowledgement" of a lower crypto stream by a higher level ac=
k.
>
> At the moment I do not have a strong opinion on the Empty ACK mechanism.
>
> However, regarding how we close the Initial and Handshake contexts, my pr=
eference goes to using implicit ACKs (i.e. use the successful receipt of a =
packet that is protected under a higher level of encryption key as the sign=
al) rather than explicitly ACKing the last flight of data.
>
> As I see, there are two downsides in the Explicit ACKing approach.
>
> * Explicit ACKing requires sending two additional packets during the hand=
shake, which means that we would have more AES operations plus somewhere ar=
ound 60 bytes of overhead on the wire.
> * Explicit ACKing requires more signaling from the TLS stack. In case of =
implicit ACKing, the TLS stack need to only provide the AEAD contexts and t=
he messages, whereas in case of explicit ACKing, the TLS stack also needs t=
o provide a signal indicating the end of the transmission at each encryptio=
n level.
>
> The downside of the implicit ACKing approach is that the server needs to =
signal the termination of the Handshake context using a special frame sent =
using a 1-RTT packet.
>
> But even taking that into consideration, I think that implicit ACKing is =
still easier to implement, considering the need for the additional signal i=
n the explicit ACK case that have been described above.
>
>
>> In any
>> case, starting as simple as possible would help having the first
>> implementations and tests.
>>
>>
>> On 5/22/2018 8:26 PM, Subodh Iyengar wrote:
>>
>> As an implementor of fizz, I support this design and am willing to
>> implement this as well.
>>
>>
>> While this is a change in the API that TLS classically exposes, I
>> think this is the right tradeoff because it helps make things way more
>> explicit which will prevent several other bugs from happening in the fut=
ure.
>>
>>
>> Subodh
>>
>> ________________________________
>> From: QUIC <quic-bounces@ietf.org> on behalf of Martin Thomson
>> <martin.thomson@gmail.com>
>> Sent: Tuesday, May 22, 2018 8:00:40 PM
>> To: Ian Swett
>> Cc: ekr@mozilla.com; QUIC WG
>> Subject: Re: Stream0 Design Team Proposal
>>
>> First of all, thanks to the design team for the work they have done.
>> I haven't digested everything yet, but I think that I have a good
>> sense of the shape of the proposal.
>>
>> Overall, this looks like a workable design.  It's a lot more invasive
>> of the cryptographic handshake implementation than I had thought
>> people were willing to stomach originally.  But it's clear that we've
>> run into problems with the current, more abstract API and this is a
>> fairly natural way to split TLS.  I've spent a little time thinking
>> about how this might be implemented and I think that it's not going to
>> be *too* painful.  The proof will be in the pudding there though.
>>
>> In looking at the PR, I really appreciate seeing all the changes togethe=
r..
>> BTW, the link above points to the wrong PR, so be careful (it appears
>> to have the same content, but that's not guaranteed).  The actual PR is =
here:
>> https://github.com/quicwg/base-drafts/pull/1377
>>
>> I've pushed a branch to the main repo so that you can preview the
>> entire document set:
>> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__quicwg.github.io_
>> base-2Ddrafts_stream0_&d=3DDwIBaQ&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3Dh3Ju9EB=
S7mH
>> twg-wAyN7fQ&m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&s=3DususmtxI=
3B
>> TaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&e=3D
>>
>> It seems like there are some core changes here and a bunch of
>> separable or at least secondary changes.  I'm sure that each one has
>> its own justification, but that isn't always clear. The following
>> changes seem like they are separable:
>>
>> * The use of separate packet number spaces
>> * The Retry packet changes (and NEW_TOKEN)
>> * EMPTY_ACK
>> * The TLS extension for flow control
>>
>> Right now, some of these appear to be entirely gratuitous.  I'd like
>> to get to the bottom of each before we continue.
>>
>> At a minimum, the PR we land first should include just the core changes.
>> As you say, reviewing a monster PR like this will only make GitHub
>> weep unicorns, but we might be able to cut this into smaller pieces.
>>
>> On Wed, May 23, 2018 at 11:31 AM Ian Swett <ianswett=3D
>> 40google.com@dmarc.ietf.org> wrote:
>>
>>> Dear QUIC WG,
>>
>>
>>> On behalf of the Stream 0 Design Team, I am pleased to report that we
>> have consensus on a proposed approach to share with the WG. The DT's
>> proposal will make QUIC and TLS work closer together and incorporates
>> ideas from DTLS, but it does not use the DTLS protocol itself.
>>
>>
>>> The DT believes this solves the important open Stream 0 issues. The
>> proposal will be a bit more invasive in TLS, but we believe it is the
>> right long-term direction and several TLS stacks (BoringSSL, PicoTLS,
>> NSS, and
>> Mint) are willing and able to do the work necessary.. A number of
>> stacks are currently working on implementations of this new approach,
>> which we hope to have in time for the Interim meeting.
>>
>>
>>> A design document describing the overall approach can be found at:
>>
>>
>> https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__docs.google.com_d
>> ocument_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8_edit&d=3DDwIBaQ
>> &c=3D5VD0RTtNlTh3ycd41b3MUw&r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&m=3D_vGK3zTKFrMOk=
FihJ
>> nPntLYw1T0_NEMiHYSM0Q_u1JA&s=3DjDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wV
>> Gg&e=3D
>>
>>
>>> A PR making the changes to the QUIC documents can be found at:
>>
>>> https://github.com/quicwg/base-drafts/pull/1377
>>
>>
>>> A few design details did not have clear consensus, but it was felt it
>> would be better to discuss those in the wider WG than delay the design
>> team.  A consistent choice was made in the PR and these issues are
>> mentioned in Appendix B of the design doc.
>>
>>
>>> As always, comments and questions welcome. That said, this is a big
>>> PR
>> and we recognize that some editorial work is going to be needed before
>> merging. In the interest of letting people follow along, and to keep
>> github from falling over, we ask people to keep discussion on the
>> mailing list and refrain from making PR comments.
>>
>>
>>> See you in Kista!
>>
>>
>>> Ian and Eric
>>
>>
>
>
>
> --
> Kazuho Oku
>



--=20
Kazuho Oku


From nobody Wed May 23 16:16:26 2018
Return-Path: <mbishop@evequefou.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3BBF012D871 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:16:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 RBlUvyTJPbtL for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:16:21 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-cys01nam02on0107.outbound.protection.outlook.com [104.47.37.107]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B7D6C12D86D for <quic@ietf.org>; Wed, 23 May 2018 16:16:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=I2ZgeKKzYSaAoR+Lu5twlousLUaM5tyb4qTcEwU549Q=; b=MXFHh/J8KBrp5SnThjp2n2mUScuF1G/LHeQ2rBsc6zSn1g5d2nQZ8qQycl+E7qiNLJ1fh84DCpRB+L6BxQ6iUtWbqk4ebemFqsjoPpuhSiqdaKVY87E61AXIe8kyKX6xqtvplWA61ultPL1FQs9eURXuZ3U4LB11e+66DeFpImI=
Received: from SN1PR08MB1854.namprd08.prod.outlook.com (10.169.39.8) by SN1PR08MB1439.namprd08.prod.outlook.com (10.162.1.24) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.797.11; Wed, 23 May 2018 23:16:19 +0000
Received: from SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d]) by SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d%13]) with mapi id 15.20.0776.015; Wed, 23 May 2018 23:16:18 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: HTTP Working Group <ietf-http-wg@w3.org>, "quic@ietf.org" <quic@ietf.org>
Subject: QPACK and the Static Table
Thread-Topic: QPACK and the Static Table
Thread-Index: AdPy6/ObcVQE/1QBQB2X+UF0YtinwQ==
Date: Wed, 23 May 2018 23:16:18 +0000
Message-ID: <SN1PR08MB1854395A2875541C4DC0673DDA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [2601:600:8080:5a28:4940:a32d:2658:89dc]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN1PR08MB1439; 7:HDmlhFtjwA2bji60/CbpvJ655Yuto4FcTD63UzQv1bGQWrl5cyadNblDVWA0uN2RMHsMp1LmtGZQ0yMDxn2HA6oVuddMhoCCqRG0mbuz/09Qy6Zn+PpmdBVB8AX03Rko14tG0hqb8zyoCfUcYAFh5dxuC6TZK/GMc4YD2XFrBOFYeOBi8Ng76iuBfcuRX8GD5/1NEFXKMgCHB+7BWd0U4NH5DCUAH9SuAN4fyGgUgpWRA2ahYUXtcRPxiZbsCcjF
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(5600026)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(2017052603328)(7153060)(7193020); SRVR:SN1PR08MB1439; 
x-ms-traffictypediagnostic: SN1PR08MB1439:
x-microsoft-antispam-prvs: <SN1PR08MB1439A8B8325E593AD2459BCEDA6B0@SN1PR08MB1439.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(158342451672863)(166708455590820)(86561027422486)(21748063052155)(64217206974132);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(10201501046)(3002001)(3231254)(944501410)(52105095)(149027)(150027)(6041310)(2016111802025)(20161123562045)(20161123558120)(20161123560045)(20161123564045)(6072148)(6043046)(201708071742011)(7699016); SRVR:SN1PR08MB1439; BCL:0; PCL:0; RULEID:; SRVR:SN1PR08MB1439; 
x-forefront-prvs: 06818431B9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(39830400003)(346002)(376002)(39380400002)(366004)(199004)(189003)(7736002)(2900100001)(5250100002)(86362001)(790700001)(97736004)(74316002)(6116002)(2501003)(486006)(478600001)(68736007)(46003)(966005)(81156014)(81166006)(8676002)(6436002)(8936002)(14454004)(106356001)(105586002)(476003)(316002)(6506007)(3280700002)(74482002)(5660300001)(99286004)(606006)(55016002)(110136005)(9686003)(6306002)(54896002)(53936002)(236005)(7696005)(25786009)(59450400001)(2906002)(102836004)(33656002)(3660700001)(186003); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR08MB1439; H:SN1PR08MB1854.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 4vobyqk0bc0uxMd1vrjIlHIrPYaxx6sVO/m/2lSrVWoa/WW/KKh8GEIjdkBdeNinvH4vFvzC/jxrYBTSwZ4FLahuKIuawOyEhtTWoxq1WxkEr0GNlJYl9sEmGrSDuG1F34hmqJNX4PhIRMpPIUwP98QLyb63l6UHnD1vlQ+X2AqXDk42/s2GPPHiMEATz0e0
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_SN1PR08MB1854395A2875541C4DC0673DDA6B0SN1PR08MB1854namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 52322018-a1b3-4f20-5a0f-08d5c10330c1
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 52322018-a1b3-4f20-5a0f-08d5c10330c1
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 May 2018 23:16:18.8427 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR08MB1439
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/SiDTgKSv2Nv5bgtlCaGlNs5czZ4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 23:16:25 -0000

--_000_SN1PR08MB1854395A2875541C4DC0673DDA6B0SN1PR08MB1854namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Wanted to get a sense of the affected working groups on two issues in QPACK=
 (header compression for HTTP/QUIC).

Rather than indexing the tables together and having the static table at 1-6=
1, QPACK uses a bit to indicate static vs. dynamic.  Since the field is sev=
en bits long, the performance is comparable for the dynamic table (you can =
access 63 entries in one byte, 190 in two), but you can increase the size o=
f the static table without hurting the dynamic table.  As a result, we're b=
uilding a fresh static table<https://github.com/quicwg/base-drafts/pull/135=
5> based on queries against HTTPArchive data.

The key question that has come up in a couple venues:  What real-world head=
ers do we want to artificially remove from what the data shows, and what he=
aders not seen by HTTP Archive do we want to force in anyway?

So far, we've:

  *   forced in pseudo-headers because the Archive doesn't capture them and=
 they would otherwise be absent
     *   :path, :authority, :method
  *   deleted values presumed biased by the test configuration:
     *   Server: (various vendors)
     *   User-Agent
     *   Accept-Language: en-us, en;q=3D0.9
     *   Content-Length: 531
        *   I still wonder exactly why that's so common....
     *   P3p: policyref=3D"https://www.googleadservices.com/..."....
     *   Origin: https://www.facebook.com
     *   Alt-Svc for various versions of gQUIC
     *   ...the list goes on
  *   deleted headers prohibited by HTTP/QUIC and HTTP/2
     *   Transfer-Encoding: chunked
  *   Reordered to put headers you're likely to name-reference at the front=
, especially if you're unlikely to add them to the dynamic table

The question is whether we should also backfill headers which HTTP Archive =
wouldn't see, delete headers we wish people wouldn't use, and/or insert the=
 ones we hope they eventually will.  Some candidates:

  *   Add Alt-Svc entry for HTTP/QUIC with QUIC v1
  *   Add X-Forwarded-For
  *   Don't add X-Forwarded-For, but do add Forwarded
  *   Remove Expires to incent the use of Cache-Control
  *   Collapse the "Content-Type: <thingey>" and "Content-Type: <thingey>; =
charset=3Dutf-8" entries together
     *   ...but which one to keep?
  *   Add Content-Encoding and/or Accept-Encoding entries for zstd

There's an endless parade of bikesheds here.  As Martin has pointed out, th=
is will never be perfect, so the goal is "good enough and keep going."  Any=
 strong feelings about any of these before we merge it?

Also, there's been some discussion of a mechanism for selecting one of seve=
ral static tables at the start of a connection.  In that case, the spec wou=
ld probably define three tables (client headers, server headers [for server=
s that don't push], combined [for servers that push]) and enable future RFC=
s to define others for targeted scenarios (proxies, video playback, IoT, et=
c.).  How much does that interest folks?

--_000_SN1PR08MB1854395A2875541C4DC0673DDA6B0SN1PR08MB1854namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:216626318;
	mso-list-type:hybrid;
	mso-list-template-ids:-2046362272 67698689 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1
	{mso-list-id:382562332;
	mso-list-type:hybrid;
	mso-list-template-ids:1843668932 67698689 67698691 67698693 67698689 67698=
691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Wanted to get a sense of the affected working groups=
 on two issues in QPACK (header compression for HTTP/QUIC).<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Rather than indexing the tables together and having =
the static table at 1-61, QPACK uses a bit to indicate static vs. dynamic.&=
nbsp; Since the field is seven bits long, the performance is comparable for=
 the dynamic table (you can access 63 entries
 in one byte, 190 in two), but you can increase the size of the static tabl=
e without hurting the dynamic table.&nbsp; As a result, we&#8217;re buildin=
g a
<a href=3D"https://github.com/quicwg/base-drafts/pull/1355">fresh static ta=
ble</a> based on queries against HTTPArchive data.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The key question that has come up in a couple venues=
:&nbsp; What real-world headers do we want to artificially remove from what=
 the data shows, and what headers not seen by HTTP Archive do we want to fo=
rce in anyway?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">So far, we&#8217;ve:<o:p></o:p></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l1 level1 =
lfo1">forced in pseudo-headers because the Archive doesn&#8217;t capture th=
em and they would otherwise be absent<o:p></o:p>
<ul style=3D"margin-top:0in" type=3D"circle">
<li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l1 level2 =
lfo1">:path, :authority, :method<o:p></o:p></li></ul>
</li><li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l1 le=
vel1 lfo1">deleted values presumed biased by the test configuration:<o:p></=
o:p>
<ul style=3D"margin-top:0in" type=3D"circle">
<li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l1 level2 =
lfo1">Server: (various vendors)<o:p></o:p></li><li class=3D"MsoListParagrap=
h" style=3D"margin-left:0in;mso-list:l1 level2 lfo1">User-Agent<o:p></o:p><=
/li><li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l1 lev=
el2 lfo1">Accept-Language: en-us, en;q=3D0.9<o:p></o:p></li><li class=3D"Ms=
oListParagraph" style=3D"margin-left:0in;mso-list:l1 level2 lfo1">Content-L=
ength: 531<o:p></o:p>
<ul style=3D"margin-top:0in" type=3D"square">
<li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l1 level3 =
lfo1">I still wonder exactly why that&#8217;s so common&#8230;.<o:p></o:p><=
/li></ul>
</li><li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l1 le=
vel2 lfo1">P3p: policyref=3D&#8221;https://www.googleadservices.com/...&#82=
21;&#8230;.<o:p></o:p></li><li class=3D"MsoListParagraph" style=3D"margin-l=
eft:0in;mso-list:l1 level2 lfo1">Origin: https://www.facebook.com<o:p></o:p=
></li><li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l1 l=
evel2 lfo1">Alt-Svc for various versions of gQUIC<o:p></o:p></li><li class=
=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l1 level2 lfo1">&#8=
230;the list goes on<o:p></o:p></li></ul>
</li><li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l1 le=
vel1 lfo1">deleted headers prohibited by HTTP/QUIC and HTTP/2<o:p></o:p>
<ul style=3D"margin-top:0in" type=3D"circle">
<li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l1 level2 =
lfo1">Transfer-Encoding: chunked<o:p></o:p></li></ul>
</li><li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l1 le=
vel1 lfo1">Reordered to put headers you&#8217;re likely to name-reference a=
t the front, especially if you&#8217;re unlikely to add them to the dynamic=
 table<o:p></o:p></li></ul>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The question is whether we should also backfill head=
ers which HTTP Archive wouldn&#8217;t see, delete headers we wish people wo=
uldn&#8217;t use, and/or insert the ones we hope they eventually will.&nbsp=
; Some candidates:<o:p></o:p></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l0 level1 =
lfo2">Add Alt-Svc entry for HTTP/QUIC with QUIC v1<o:p></o:p></li><li class=
=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l0 level1 lfo2">Add=
 X-Forwarded-For<o:p></o:p></li><li class=3D"MsoListParagraph" style=3D"mar=
gin-left:0in;mso-list:l0 level1 lfo2">Don&#8217;t add X-Forwarded-For, but =
do add Forwarded<o:p></o:p></li><li class=3D"MsoListParagraph" style=3D"mar=
gin-left:0in;mso-list:l0 level1 lfo2">Remove Expires to incent the use of C=
ache-Control<o:p></o:p></li><li class=3D"MsoListParagraph" style=3D"margin-=
left:0in;mso-list:l0 level1 lfo2">Collapse the &#8220;Content-Type: &lt;thi=
ngey&gt;&#8221; and &#8220;Content-Type: &lt;thingey&gt;; charset=3Dutf-8&#=
8221; entries together<o:p></o:p>
<ul style=3D"margin-top:0in" type=3D"circle">
<li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l0 level2 =
lfo2">&#8230;but which one to keep?<o:p></o:p></li></ul>
</li><li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l0 le=
vel1 lfo2">Add Content-Encoding and/or Accept-Encoding entries for zstd<o:p=
></o:p></li></ul>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">There&#8217;s an endless parade of bikesheds here. &=
nbsp;As Martin has pointed out, this will never be perfect, so the goal is =
&#8220;good enough and keep going.&#8221;&nbsp; Any strong feelings about a=
ny of these before we merge it?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Also, there&#8217;s been some discussion of a mechan=
ism for selecting one of several static tables at the start of a connection=
.&nbsp; In that case, the spec would probably define three tables (client h=
eaders, server headers [for servers that don&#8217;t
 push], combined [for servers that push]) and enable future RFCs to define =
others for targeted scenarios (proxies, video playback, IoT, etc.).&nbsp; H=
ow much does that interest folks?<o:p></o:p></p>
</div>
</body>
</html>

--_000_SN1PR08MB1854395A2875541C4DC0673DDA6B0SN1PR08MB1854namp_--


From nobody Wed May 23 16:23:35 2018
Return-Path: <jri.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5FD7A12D7F1 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:23:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.989
X-Spam-Level: 
X-Spam-Status: No, score=-1.989 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 y9mInm4lGXeL for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:23:31 -0700 (PDT)
Received: from mail-io0-x230.google.com (mail-io0-x230.google.com [IPv6:2607:f8b0:4001:c06::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B988812783A for <quic@ietf.org>; Wed, 23 May 2018 16:23:31 -0700 (PDT)
Received: by mail-io0-x230.google.com with SMTP id e20-v6so81475iof.4 for <quic@ietf.org>; Wed, 23 May 2018 16:23:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=SvNvxv6npXicFuGoylezoxiXP3kzs8nlKsoMG+YVTik=; b=jaD80i6T5ck0FiyeWYkSzXcQLP06SswisuLNJbc+hzuv7FhvZrnd5OLa3Aj0smbulB paojRJBaH8gV1OwEtgF0Wu+UKnBMGhvBHgden1BUqvMMi01ljNgSpXOlHcPohCkg7l81 924jOdTnJVvfe+Ui/zWuOFDeMrInb6u3jcOm3CrIIYpxxY5zTaVHhY4iYb7mCTkjuF6z P7BSRYl440hUl2TYF+zaeFl2Hu+FsoOA6F+6eGs4B3cmXgNSLC3ASWy9CRu1WsdVPfDt UmjoZAVf3n1CiPQP89mw215HCKWQoqT0LgGrE0BB3fQiqsXJwsjfdORqpIYygx7ref+/ ZF/A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=SvNvxv6npXicFuGoylezoxiXP3kzs8nlKsoMG+YVTik=; b=Z7CKapZzgrpxzn2GdJLKbCJirZ+wS76aintOoLMfG/A5VxpKTNd+XCvMltu6qpxVKZ POJqqO49mgLvgUItMh37jEFlJ8aHZt5aQq49D60b+TOnP71j118WS/vxJHemeabGL4zF bdMHS3LEpCQHwHu2ax9PSTAm9J5mjGB5fpoZX2GRNqRr1PEKr7X6w+FssoZ/EmMgoZfc GHiVuKB7WoVCqxrdTG31fDS/Yz/y5CC+guwEUL0kbgVxybfhojGyPIi7FvPDRiLE05+8 5N6AxEvoFBrFu5D0GR/CLhh+qR9jHFjo/OIbG7RQDyY+OEqexkA0ekWlGuXL0eh4B+Qc Gl5g==
X-Gm-Message-State: ALKqPwe9M9vb5pV2qSm7av4plJfMMi88vALneEXTKBYLTTnM1HI2nZ/M IGCxeiNl9Mf+jLuB60BX/gWd8tRtRUEBMBX0DHE=
X-Google-Smtp-Source: AB8JxZpc9iRynl/BSxUm3Dm5FokIngUTxl1x23cZAtvVSvzs2JJSyNBRB+06D0stgum1m/HcIIckarY/IemNJOW93m0=
X-Received: by 2002:a6b:dc12:: with SMTP id s18-v6mr4818381ioc.203.1527117810719;  Wed, 23 May 2018 16:23:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:27d4:0:0:0:0:0 with HTTP; Wed, 23 May 2018 16:23:30 -0700 (PDT)
In-Reply-To: <SN1PR08MB1854BF85FCCA0F21CE0DA1A4DA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CABkgnnUB=jqwFzb2rjBHUFzOgu0hX0YUgaf5kW5ENNGKP+mGiA@mail.gmail.com> <SN1PR08MB1854BF85FCCA0F21CE0DA1A4DA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Wed, 23 May 2018 16:23:30 -0700
Message-ID: <CACpbDce-vsqvutYCDjWJmEW_K=HX=F2y6bk7c34dxky22-mzwg@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: Mike Bishop <mbishop@evequefou.be>
Cc: Martin Thomson <martin.thomson@gmail.com>,  Ian Swett <ianswett=40google.com@dmarc.ietf.org>, "ekr@mozilla.com" <ekr@mozilla.com>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a3621f056ce7d27a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ygzqBowTfW_OGUHFFHhETpFYqoY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 23:23:35 -0000

--000000000000a3621f056ce7d27a
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Just a point of order, because this thread can easily become a
thousand-tentacled monster.

There are many parts to the proposal. There was general agreement in the DT
that it's valuable to see all parts of what were discussed, even if some
parts stretched the original mandate, and even if some parts end up being
discarded. That is entirely the wg's prerogative. We should discuss
individual disagreements or points of concern, and I strongly recommend
forking off new threads for each of these points.


On Wed, May 23, 2018 at 3:23 PM, Mike Bishop <mbishop@evequefou.be> wrote:

> I also think these two pieces are not inextricably bound together:
>
>    - Moving from Stream 0 to CRYPTO frames
>    - Removing the TLS record layer and using the TLS keys directly in
>    QUIC packet protection
>
> =E2=80=A6though both of these interact pretty closely with the separate p=
acket
> number spaces.
>
>
>
> So I think that=E2=80=99s roughly six PRs we should expect to see out of =
the
> design team=E2=80=99s proposal.  A few of them have dependencies on each =
other, but
> they seem mostly separable.  It sounds like several of them have consensu=
s
> in the design team, but not all of them, and it would be good to be able =
to
> discuss them separately.
>
>
>
> -----Original Message-----
> From: QUIC <quic-bounces@ietf.org> On Behalf Of Martin Thomson
> Sent: Tuesday, May 22, 2018 8:01 PM
> To: Ian Swett <ianswett=3D40google.com@dmarc.ietf.org>
> Cc: ekr@mozilla.com; QUIC WG <quic@ietf.org>
> Subject: Re: Stream0 Design Team Proposal
>
>
>
> First of all, thanks to the design team for the work they have done.  I
> haven't digested everything yet, but I think that I have a good sense of
> the shape of the proposal.
>
>
>
> Overall, this looks like a workable design.  It's a lot more invasive of
> the cryptographic handshake implementation than I had thought people were
> willing to stomach originally.  But it's clear that we've run into proble=
ms
> with the current, more abstract API and this is a fairly natural way to
> split TLS.  I've spent a little time thinking about how this might be
> implemented and I think that it's not going to be *too* painful.  The pro=
of
> will be in the pudding there though.
>
>
>
> In looking at the PR, I really appreciate seeing all the changes together=
.
>
> BTW, the link above points to the wrong PR, so be careful (it appears to
> have the same content, but that's not guaranteed).  The actual PR is here=
:
>
> https://github.com/quicwg/base-drafts/pull/1377
>
>
>
> I've pushed a branch to the main repo so that you can preview the entire
> document set: https://quicwg.github.io/base-drafts/stream0/
>
>
>
> It seems like there are some core changes here and a bunch of separable o=
r
> at least secondary changes.  I'm sure that each one has its own
> justification, but that isn't always clear. The following changes seem li=
ke
> they are separable:
>
>
>
> * The use of separate packet number spaces
>
> * The Retry packet changes (and NEW_TOKEN)
>
> * EMPTY_ACK
>
> * The TLS extension for flow control
>
>
>
> Right now, some of these appear to be entirely gratuitous.  I'd like to
> get to the bottom of each before we continue.
>
>
>
> At a minimum, the PR we land first should include just the core changes.
>
> As you say, reviewing a monster PR like this will only make GitHub weep
> unicorns, but we might be able to cut this into smaller pieces.
>
>
>
> On Wed, May 23, 2018 at 11:31 AM Ian Swett <ianswett=3D
> 40google.com@dmarc.ietf.org> wrote:
>
>
>
> > Dear QUIC WG,
>
>
>
>
>
> > On behalf of the Stream 0 Design Team, I am pleased to report that we
>
> have consensus on a proposed approach to share with the WG. The DT's
> proposal will make QUIC and TLS work closer together and incorporates ide=
as
> from DTLS, but it does not use the DTLS protocol itself.
>
>
>
>
>
> > The DT believes this solves the important open Stream 0 issues. The
>
> proposal will be a bit more invasive in TLS, but we believe it is the
> right long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS=
,
> and
>
> Mint) are willing and able to do the work necessary.. A number of stacks
> are currently working on implementations of this new approach, which we
> hope to have in time for the Interim meeting.
>
>
>
>
>
> > A design document describing the overall approach can be found at:
>
>
>
>
>
> https://docs.google.com/document/d/1fRsJqPinJl8N3b-
> bflDRV6auojfJLkxddT93j6SwHY8/edit
>
>
>
>
>
> > A PR making the changes to the QUIC documents can be found at:
>
>
>
> > https://github.com/quicwg/base-drafts/pull/1377
>
>
>
>
>
> > A few design details did not have clear consensus, but it was felt it
>
> would be better to discuss those in the wider WG than delay the design
> team.  A consistent choice was made in the PR and these issues are
> mentioned in Appendix B of the design doc.
>
>
>
>
>
> > As always, comments and questions welcome. That said, this is a big PR
>
> and we recognize that some editorial work is going to be needed before
> merging. In the interest of letting people follow along, and to keep gith=
ub
> from falling over, we ask people to keep discussion on the mailing list a=
nd
> refrain from making PR comments.
>
>
>
>
>
> > See you in Kista!
>
>
>
>
>
> > Ian and Eric
>
>
>

--000000000000a3621f056ce7d27a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Just a point of order, because this thread can easily beco=
me a thousand-tentacled monster.<div><br></div><div>There are many parts to=
 the proposal. There was general agreement in the DT that it&#39;s valuable=
 to see all parts of what were discussed, even if some parts stretched the =
original mandate, and even if some parts end up being discarded. That is en=
tirely the wg&#39;s prerogative. We should discuss individual disagreements=
 or points of concern, and I strongly recommend forking off new threads for=
 each of these points.<br><br></div></div><div class=3D"gmail_extra"><br><d=
iv class=3D"gmail_quote">On Wed, May 23, 2018 at 3:23 PM, Mike Bishop <span=
 dir=3D"ltr">&lt;<a href=3D"mailto:mbishop@evequefou.be" target=3D"_blank">=
mbishop@evequefou.be</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
">





<div lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"m_2680712970263117419WordSection1">
<p class=3D"m_2680712970263117419MsoPlainText">I also think these two piece=
s are not inextricably bound together:<u></u><u></u></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"m_2680712970263117419MsoPlainText">Moving from Stream 0 to CRY=
PTO frames<u></u><u></u></li><li class=3D"m_2680712970263117419MsoPlainText=
">Removing the TLS record layer and using the TLS keys directly in QUIC pac=
ket protection<u></u><u></u></li></ul>
<p class=3D"m_2680712970263117419MsoPlainText">=E2=80=A6though both of thes=
e interact pretty closely with the separate packet number spaces.<u></u><u>=
</u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">So I think that=E2=80=99s ro=
ughly six PRs we should expect to see out of the design team=E2=80=99s prop=
osal.=C2=A0 A few of them have dependencies on each other, but they seem mo=
stly separable.=C2=A0 It sounds like several of them have consensus in the =
design
 team, but not all of them, and it would be good to be able to discuss them=
 separately.<u></u><u></u></p><span class=3D"">
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">-----Original Message-----<b=
r>
From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_blank">q=
uic-bounces@ietf.org</a>&gt; On Behalf Of Martin Thomson<br>
Sent: Tuesday, May 22, 2018 8:01 PM<br>
To: Ian Swett &lt;ianswett=3D<a href=3D"mailto:40google.com@dmarc.ietf.org"=
 target=3D"_blank">40google.com@dmarc.<wbr>ietf.org</a>&gt;<br>
Cc: <a href=3D"mailto:ekr@mozilla.com" target=3D"_blank">ekr@mozilla.com</a=
>; QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic@ietf=
.org</a>&gt;<br>
Subject: Re: Stream0 Design Team Proposal</p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
</span><p class=3D"m_2680712970263117419MsoPlainText">First of all, thanks =
to the design team for the work they have done.=C2=A0 I haven&#39;t digeste=
d everything yet, but I think that I have a good sense of the shape of the =
proposal.<u></u><u></u></p><div><div class=3D"h5">
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">Overall, this looks like a w=
orkable design.=C2=A0 It&#39;s a lot more invasive of the cryptographic han=
dshake implementation than I had thought people were willing to stomach ori=
ginally.=C2=A0 But it&#39;s clear that we&#39;ve run into problems with the=
 current,
 more abstract API and this is a fairly natural way to split TLS.=C2=A0 I&#=
39;ve spent a little time thinking about how this might be implemented and =
I think that it&#39;s not going to be *too* painful.=C2=A0 The proof will b=
e in the pudding there though.<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">In looking at the PR, I real=
ly appreciate seeing all the changes together.<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">BTW, the link above points t=
o the wrong PR, so be careful (it appears to have the same content, but tha=
t&#39;s not guaranteed).=C2=A0 The actual PR is here:<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><a href=3D"https://github.co=
m/quicwg/base-drafts/pull/1377" target=3D"_blank"><span style=3D"color:wind=
owtext;text-decoration:none">https://github.com/quicwg/<wbr>base-drafts/pul=
l/1377</span></a><u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">I&#39;ve pushed a branch to =
the main repo so that you can preview the entire document set:
<a href=3D"https://quicwg.github.io/base-drafts/stream0/" target=3D"_blank"=
><span style=3D"color:windowtext;text-decoration:none">https://quicwg.githu=
b.io/base-<wbr>drafts/stream0/</span></a><u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">It seems like there are some=
 core changes here and a bunch of separable or at least secondary changes.=
=C2=A0 I&#39;m sure that each one has its own justification, but that isn&#=
39;t always clear. The following changes seem like they are separable:<u></=
u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">* The use of separate packet=
 number spaces<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">* The Retry packet changes (=
and NEW_TOKEN)<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">* EMPTY_ACK<u></u><u></u></p=
>
<p class=3D"m_2680712970263117419MsoPlainText">* The TLS extension for flow=
 control<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">Right now, some of these app=
ear to be entirely gratuitous.=C2=A0 I&#39;d like to get to the bottom of e=
ach before we continue.<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">At a minimum, the PR we land=
 first should include just the core changes.<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">As you say, reviewing a mons=
ter PR like this will only make GitHub weep unicorns, but we might be able =
to cut this into smaller pieces.<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">On Wed, May 23, 2018 at 11:3=
1 AM Ian Swett &lt;ianswett=3D <a href=3D"mailto:40google.com@dmarc.ietf.or=
g" target=3D"_blank">
<span style=3D"color:windowtext;text-decoration:none">40google.com@dmarc.ie=
tf.org</span></a>&gt; wrote:<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">&gt; Dear QUIC WG,<u></u><u>=
</u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">&gt; On behalf of the Stream=
 0 Design Team, I am pleased to report that we<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">have consensus on a proposed=
 approach to share with the WG. The DT&#39;s proposal will make QUIC and TL=
S work closer together and incorporates ideas from DTLS, but it does not us=
e the DTLS protocol itself.<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">&gt; The DT believes this so=
lves the important open Stream 0 issues. The<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">proposal will be a bit more =
invasive in TLS, but we believe it is the right long-term direction and sev=
eral TLS stacks (BoringSSL, PicoTLS, NSS, and<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">Mint) are willing and able t=
o do the work necessary.. A number of stacks are currently working on imple=
mentations of this new approach, which we hope to have in time for the Inte=
rim meeting.<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">&gt; A design document descr=
ibing the overall approach can be found at:<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><a href=3D"https://docs.goog=
le.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit" target=
=3D"_blank"><span style=3D"color:windowtext;text-decoration:none">https://d=
ocs.google.com/<wbr>document/d/1fRsJqPinJl8N3b-<wbr>bflDRV6auojfJLkxddT93j6=
SwHY8/<wbr>edit</span></a><u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">&gt; A PR making the changes=
 to the QUIC documents can be found at:<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">&gt; <a href=3D"https://gith=
ub.com/quicwg/base-drafts/pull/1377" target=3D"_blank">
<span style=3D"color:windowtext;text-decoration:none">https://github.com/qu=
icwg/<wbr>base-drafts/pull/1377</span></a><u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">&gt; A few design details di=
d not have clear consensus, but it was felt it<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">would be better to discuss t=
hose in the wider WG than delay the design team.=C2=A0 A consistent choice =
was made in the PR and these issues are mentioned in Appendix B of the desi=
gn doc.<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">&gt; As always, comments and=
 questions welcome. That said, this is a big PR<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">and we recognize that some e=
ditorial work is going to be needed before merging. In the interest of lett=
ing people follow along, and to keep github from falling over, we ask peopl=
e to keep discussion on the mailing list and refrain from
 making PR comments.<u></u><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">&gt; See you in Kista!<u></u=
><u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
<p class=3D"m_2680712970263117419MsoPlainText">&gt; Ian and Eric<u></u><u><=
/u></p>
<p class=3D"m_2680712970263117419MsoPlainText"><u></u>=C2=A0<u></u></p>
</div></div></div>
</div>

</blockquote></div><br></div>

--000000000000a3621f056ce7d27a--


From nobody Wed May 23 16:25:36 2018
Return-Path: <jri.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7BBA212D7F1 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:25:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 rP33hifcnA8S for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:25:31 -0700 (PDT)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3EAD61273B1 for <quic@ietf.org>; Wed, 23 May 2018 16:25:31 -0700 (PDT)
Received: by mail-io0-x233.google.com with SMTP id e12-v6so76030iob.8 for <quic@ietf.org>; Wed, 23 May 2018 16:25:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=NyybhNzaTdrtVS4hg5OdPZrZfXeSd9Oq8fTnXwtD+28=; b=JNe2K+cYBd9Qi3vmiqA37St870C9XZSXwOMW50xL91HxPs/nbGnw5UJ3jrhFQDhS59 aeQ1tibhSus0MjRNDtavBbOqzAIYekWLZlyyGMy7FoUQ8HDqjFAI8V8pBpEfn8k5RZ3R 8YKPJ7zyV/Ik1cp28X7PR+jenkXrDH4im9UrA15r4ngwwRQJoJoWX+5aJKW2IFdqu4Uf CmErmKjkb+nQdih+vQmzTkq98NGYurd+MVE7FaqPTPSEiYTlQ3gu4vyt8c5kYQS/lCqO 2jBN+vOnAfgCn2zkeRAWgpmUb1czyilWkdB1pBu+oOFcZXbbKytxuBdTUoV9sC7GSqNC sryw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=NyybhNzaTdrtVS4hg5OdPZrZfXeSd9Oq8fTnXwtD+28=; b=RMnpb+bSAButHON3qRORgQAqLOD+D7Em4PTBoeSFc/oKdDdlKLwCCphIQGlvNEwx/L IR4Wc1pliN+MpQdYXDkuk7FGt3bmiIQFOBdUeYBfnw4NKubQoqSC86RH9JeqMe1CgjiX CCPuXEK/BPqiDcEfc6HijgsXMFZ3Gmc/sihrKnqk1MYZib9f+ZMbZ4w95stpTHsqWQE1 NU8HFr6ktAe8gtavbg2H3OrE9NeooT8O+lgm+DfvGjuabRyqWEjpprDBNM200KQjbUvj 68fdhh+5q/80exb+/DYgHBpDLq5elK/Wm24CWBUem4e09EQC1K4r2F35vTJb6Xtunjud KKyw==
X-Gm-Message-State: ALKqPwcWhm7si6JxQNYEDQWj7tTEKZ/VvGgfdYhTB1HKy/tZ41G1vjx+ kf/SlVMkNwqAMIdREgrk31oj+AQ+qVbFD4xkmS0=
X-Google-Smtp-Source: ADUXVKKLMbaBUibxDFyaS5QW+BLJzu4eq2Y+id6GnDdn7WBSzkCs0jTByI0P+lZx52UtirOJJxF611cofXOmz88MI/4=
X-Received: by 2002:a6b:88e3:: with SMTP id s96-v6mr4605916ioi.45.1527117930206;  Wed, 23 May 2018 16:25:30 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:27d4:0:0:0:0:0 with HTTP; Wed, 23 May 2018 16:25:29 -0700 (PDT)
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Wed, 23 May 2018 16:25:29 -0700
Message-ID: <CACpbDcd+Ho15unyb_r-sVE39jWO+z5sszsX5QqUvn+2oBqq+1w@mail.gmail.com>
Subject: Stream0 Proposal: EMPTY_ACK
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c29d25056ce7d917"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/VNm9eZWKnjB4SP11F-fNKZaI4fM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 23:25:34 -0000

--000000000000c29d25056ce7d917
Content-Type: text/plain; charset="UTF-8"

(Forking this discussion off from the main thread.)

On Wed, May 23, 2018 at 2:13 AM, Kazuho Oku <kazuhooku@gmail.com> wrote:

> 2018-05-23 14:29 GMT+09:00 Christian Huitema <huitema@huitema.net>:
> > I like the proposal. In particular, I really like the encryption of
> > handshake packets with the handshake key, as it does close a number of
> > avenues for attacks. And I like that it solves the "ack promotion" issue
> > that I was complaining against for some time. Turns out that in the
> current
> > draft, it is very hard to contain that problem if you enable client auth.
> >
> >
> > On the other hand, I agree with Martin that a lot of the additions to
> > transmission recovery should be moved to separate PRs. I am not
> enthusiastic
> > with the EMPTY ACK mechanism, or with the proposed "implicit
> > acknowledgement" of a lower crypto stream by a higher level ack.
>
> At the moment I do not have a strong opinion on the Empty ACK mechanism.
>
> However, regarding how we close the Initial and Handshake contexts, my
> preference goes to using implicit ACKs (i.e. use the successful
> receipt of a packet that is protected under a higher level of
> encryption key as the signal) rather than explicitly ACKing the last
> flight of data.
>
> As I see, there are two downsides in the Explicit ACKing approach.
>
> * Explicit ACKing requires sending two additional packets during the
> handshake, which means that we would have more AES operations plus
> somewhere around 60 bytes of overhead on the wire.
> * Explicit ACKing requires more signaling from the TLS stack. In case
> of implicit ACKing, the TLS stack need to only provide the AEAD
> contexts and the messages, whereas in case of explicit ACKing, the TLS
> stack also needs to provide a signal indicating the end of the
> transmission at each encryption level.
>
> The downside of the implicit ACKing approach is that the server needs
> to signal the termination of the Handshake context using a special
> frame sent using a 1-RTT packet.
>
> But even taking that into consideration, I think that implicit ACKing
> is still easier to implement, considering the need for the additional
> signal in the explicit ACK case that have been described above.
>
>
> > In any
> > case, starting as simple as possible would help having the first
> > implementations and tests.
> >
> >
> > On 5/22/2018 8:26 PM, Subodh Iyengar wrote:
> >
> > As an implementor of fizz, I support this design and am willing to
> implement
> > this as well.
> >
> >
> > While this is a change in the API that TLS classically exposes, I think
> this
> > is the right tradeoff because it helps make things way more explicit
> which
> > will prevent several other bugs from happening in the future.
> >
> >
> > Subodh
> >
> > ________________________________
> > From: QUIC <quic-bounces@ietf.org> on behalf of Martin Thomson
> > <martin.thomson@gmail.com>
> > Sent: Tuesday, May 22, 2018 8:00:40 PM
> > To: Ian Swett
> > Cc: ekr@mozilla.com; QUIC WG
> > Subject: Re: Stream0 Design Team Proposal
> >
> > First of all, thanks to the design team for the work they have done.  I
> > haven't digested everything yet, but I think that I have a good sense of
> > the shape of the proposal.
> >
> > Overall, this looks like a workable design.  It's a lot more invasive of
> > the cryptographic handshake implementation than I had thought people were
> > willing to stomach originally.  But it's clear that we've run into
> problems
> > with the current, more abstract API and this is a fairly natural way to
> > split TLS.  I've spent a little time thinking about how this might be
> > implemented and I think that it's not going to be *too* painful.  The
> proof
> > will be in the pudding there though.
> >
> > In looking at the PR, I really appreciate seeing all the changes
> together..
> > BTW, the link above points to the wrong PR, so be careful (it appears to
> > have the same content, but that's not guaranteed).  The actual PR is
> here:
> > https://github.com/quicwg/base-drafts/pull/1377
> >
> > I've pushed a branch to the main repo so that you can preview the entire
> > document set:
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__quicwg.
> github.io_base-2Ddrafts_stream0_&d=DwIBaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=
> h3Ju9EBS7mHtwg-wAyN7fQ&m=_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&s=
> ususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&e=
> >
> > It seems like there are some core changes here and a bunch of separable
> or
> > at least secondary changes.  I'm sure that each one has its own
> > justification, but that isn't always clear. The following changes seem
> like
> > they are separable:
> >
> > * The use of separate packet number spaces
> > * The Retry packet changes (and NEW_TOKEN)
> > * EMPTY_ACK
> > * The TLS extension for flow control
> >
> > Right now, some of these appear to be entirely gratuitous.  I'd like to
> get
> > to the bottom of each before we continue.
> >
> > At a minimum, the PR we land first should include just the core changes.
> > As you say, reviewing a monster PR like this will only make GitHub weep
> > unicorns, but we might be able to cut this into smaller pieces.
> >
> > On Wed, May 23, 2018 at 11:31 AM Ian Swett <ianswett=
> > 40google.com@dmarc.ietf.org> wrote:
> >
> >> Dear QUIC WG,
> >
> >
> >> On behalf of the Stream 0 Design Team, I am pleased to report that we
> > have consensus on a proposed approach to share with the WG. The DT's
> > proposal will make QUIC and TLS work closer together and incorporates
> ideas
> > from DTLS, but it does not use the DTLS protocol itself.
> >
> >
> >> The DT believes this solves the important open Stream 0 issues. The
> > proposal will be a bit more invasive in TLS, but we believe it is the
> right
> > long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and
> > Mint) are willing and able to do the work necessary.. A number of stacks
> > are currently working on implementations of this new approach, which we
> > hope to have in time for the Interim meeting.
> >
> >
> >> A design document describing the overall approach can be found at:
> >
> >
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.
> google.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8
> _edit&d=DwIBaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=h3Ju9EBS7mHtwg-wAyN7fQ&m=_
> vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&s=jDNnz34hmWvLSQnHkSnYdihW-jG-
> 0xZ-YYqKq30wVGg&e=
> >
> >
> >> A PR making the changes to the QUIC documents can be found at:
> >
> >> https://github.com/quicwg/base-drafts/pull/1377
> >
> >
> >> A few design details did not have clear consensus, but it was felt it
> > would be better to discuss those in the wider WG than delay the design
> > team.  A consistent choice was made in the PR and these issues are
> > mentioned in Appendix B of the design doc.
> >
> >
> >> As always, comments and questions welcome. That said, this is a big PR
> > and we recognize that some editorial work is going to be needed before
> > merging. In the interest of letting people follow along, and to keep
> github
> > from falling over, we ask people to keep discussion on the mailing list
> and
> > refrain from making PR comments.
> >
> >
> >> See you in Kista!
> >
> >
> >> Ian and Eric
> >
> >
>
>
>
> --
> Kazuho Oku
>
>

--000000000000c29d25056ce7d917
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">(Forking this discussion off from the main thread.)<br><di=
v class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, May 23, 2018=
 at 2:13 AM, Kazuho Oku <span dir=3D"ltr">&lt;<a href=3D"mailto:kazuhooku@g=
mail.com" target=3D"_blank">kazuhooku@gmail.com</a>&gt;</span> wrote:<br><b=
lockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px =
#ccc solid;padding-left:1ex"><span class=3D"">2018-05-23 14:29 GMT+09:00 Ch=
ristian Huitema &lt;<a href=3D"mailto:huitema@huitema.net">huitema@huitema.=
net</a>&gt;:<br>
&gt; I like the proposal. In particular, I really like the encryption of<br=
>
&gt; handshake packets with the handshake key, as it does close a number of=
<br>
&gt; avenues for attacks. And I like that it solves the &quot;ack promotion=
&quot; issue<br>
&gt; that I was complaining against for some time. Turns out that in the cu=
rrent<br>
&gt; draft, it is very hard to contain that problem if you enable client au=
th.<br>
&gt;<br>
&gt;<br>
&gt; On the other hand, I agree with Martin that a lot of the additions to<=
br>
&gt; transmission recovery should be moved to separate PRs. I am not enthus=
iastic<br>
&gt; with the EMPTY ACK mechanism, or with the proposed &quot;implicit<br>
&gt; acknowledgement&quot; of a lower crypto stream by a higher level ack.<=
br>
<br>
</span>At the moment I do not have a strong opinion on the Empty ACK mechan=
ism.<br>
<br>
However, regarding how we close the Initial and Handshake contexts, my<br>
preference goes to using implicit ACKs (i.e. use the successful<br>
receipt of a packet that is protected under a higher level of<br>
encryption key as the signal) rather than explicitly ACKing the last<br>
flight of data.<br>
<br>
As I see, there are two downsides in the Explicit ACKing approach.<br>
<br>
* Explicit ACKing requires sending two additional packets during the<br>
handshake, which means that we would have more AES operations plus<br>
somewhere around 60 bytes of overhead on the wire.<br>
* Explicit ACKing requires more signaling from the TLS stack. In case<br>
of implicit ACKing, the TLS stack need to only provide the AEAD<br>
contexts and the messages, whereas in case of explicit ACKing, the TLS<br>
stack also needs to provide a signal indicating the end of the<br>
transmission at each encryption level.<br>
<br>
The downside of the implicit ACKing approach is that the server needs<br>
to signal the termination of the Handshake context using a special<br>
frame sent using a 1-RTT packet.<br>
<br>
But even taking that into consideration, I think that implicit ACKing<br>
is still easier to implement, considering the need for the additional<br>
signal in the explicit ACK case that have been described above.<br>
<div><div class=3D"h5"><br>
<br>
&gt; In any<br>
&gt; case, starting as simple as possible would help having the first<br>
&gt; implementations and tests.<br>
&gt;<br>
&gt;<br>
&gt; On 5/22/2018 8:26 PM, Subodh Iyengar wrote:<br>
&gt;<br>
&gt; As an implementor of fizz, I support this design and am willing to imp=
lement<br>
&gt; this as well.<br>
&gt;<br>
&gt;<br>
&gt; While this is a change in the API that TLS classically exposes, I thin=
k this<br>
&gt; is the right tradeoff because it helps make things way more explicit w=
hich<br>
&gt; will prevent several other bugs from happening in the future.<br>
&gt;<br>
&gt;<br>
&gt; Subodh<br>
&gt;<br>
&gt; ______________________________<wbr>__<br>
&gt; From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org">quic-bounces@i=
etf.org</a>&gt; on behalf of Martin Thomson<br>
&gt; &lt;<a href=3D"mailto:martin.thomson@gmail.com">martin.thomson@gmail.c=
om</a>&gt;<br>
&gt; Sent: Tuesday, May 22, 2018 8:00:40 PM<br>
&gt; To: Ian Swett<br>
&gt; Cc: <a href=3D"mailto:ekr@mozilla.com">ekr@mozilla.com</a>; QUIC WG<br=
>
&gt; Subject: Re: Stream0 Design Team Proposal<br>
&gt;<br>
&gt; First of all, thanks to the design team for the work they have done.=
=C2=A0 I<br>
&gt; haven&#39;t digested everything yet, but I think that I have a good se=
nse of<br>
&gt; the shape of the proposal.<br>
&gt;<br>
&gt; Overall, this looks like a workable design.=C2=A0 It&#39;s a lot more =
invasive of<br>
&gt; the cryptographic handshake implementation than I had thought people w=
ere<br>
&gt; willing to stomach originally.=C2=A0 But it&#39;s clear that we&#39;ve=
 run into problems<br>
&gt; with the current, more abstract API and this is a fairly natural way t=
o<br>
&gt; split TLS.=C2=A0 I&#39;ve spent a little time thinking about how this =
might be<br>
&gt; implemented and I think that it&#39;s not going to be *too* painful.=
=C2=A0 The proof<br>
&gt; will be in the pudding there though.<br>
&gt;<br>
</div></div>&gt; In looking at the PR, I really appreciate seeing all the c=
hanges together..<br>
<div class=3D"HOEnZb"><div class=3D"h5">&gt; BTW, the link above points to =
the wrong PR, so be careful (it appears to<br>
&gt; have the same content, but that&#39;s not guaranteed).=C2=A0 The actua=
l PR is here:<br>
&gt; <a href=3D"https://github.com/quicwg/base-drafts/pull/1377" rel=3D"nor=
eferrer" target=3D"_blank">https://github.com/quicwg/<wbr>base-drafts/pull/=
1377</a><br>
&gt;<br>
&gt; I&#39;ve pushed a branch to the main repo so that you can preview the =
entire<br>
&gt; document set:<br>
&gt; <a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__quic=
wg.github.io_base-2Ddrafts_stream0_&amp;d=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd4=
1b3MUw&amp;r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&amp;m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_N=
EMiHYSM0Q_u1JA&amp;s=3DususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&amp;e=3D=
" rel=3D"noreferrer" target=3D"_blank">https://urldefense.proofpoint.<wbr>c=
om/v2/url?u=3Dhttps-3A__quicwg.<wbr>github.io_base-2Ddrafts_<wbr>stream0_&a=
mp;d=3DDwIBaQ&amp;c=3D<wbr>5VD0RTtNlTh3ycd41b3MUw&amp;r=3D<wbr>h3Ju9EBS7mHt=
wg-wAyN7fQ&amp;m=3D_<wbr>vGK3zTKFrMOkFihJnPntLYw1T0_<wbr>NEMiHYSM0Q_u1JA&am=
p;s=3D<wbr>ususmtxI3BTaLlBWe_<wbr>HkQUWRH4sBI0Cggj1oWZMBHak&amp;e=3D</a><br=
>
&gt;<br>
&gt; It seems like there are some core changes here and a bunch of separabl=
e or<br>
&gt; at least secondary changes.=C2=A0 I&#39;m sure that each one has its o=
wn<br>
&gt; justification, but that isn&#39;t always clear. The following changes =
seem like<br>
&gt; they are separable:<br>
&gt;<br>
&gt; * The use of separate packet number spaces<br>
&gt; * The Retry packet changes (and NEW_TOKEN)<br>
&gt; * EMPTY_ACK<br>
&gt; * The TLS extension for flow control<br>
&gt;<br>
&gt; Right now, some of these appear to be entirely gratuitous.=C2=A0 I&#39=
;d like to get<br>
&gt; to the bottom of each before we continue.<br>
&gt;<br>
&gt; At a minimum, the PR we land first should include just the core change=
s.<br>
&gt; As you say, reviewing a monster PR like this will only make GitHub wee=
p<br>
&gt; unicorns, but we might be able to cut this into smaller pieces.<br>
&gt;<br>
&gt; On Wed, May 23, 2018 at 11:31 AM Ian Swett &lt;ianswett=3D<br>
&gt; <a href=3D"mailto:40google.com@dmarc.ietf.org">40google.com@dmarc.ietf=
.org</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; Dear QUIC WG,<br>
&gt;<br>
&gt;<br>
&gt;&gt; On behalf of the Stream 0 Design Team, I am pleased to report that=
 we<br>
&gt; have consensus on a proposed approach to share with the WG. The DT&#39=
;s<br>
&gt; proposal will make QUIC and TLS work closer together and incorporates =
ideas<br>
&gt; from DTLS, but it does not use the DTLS protocol itself.<br>
&gt;<br>
&gt;<br>
&gt;&gt; The DT believes this solves the important open Stream 0 issues. Th=
e<br>
&gt; proposal will be a bit more invasive in TLS, but we believe it is the =
right<br>
&gt; long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS, a=
nd<br>
&gt; Mint) are willing and able to do the work necessary.. A number of stac=
ks<br>
&gt; are currently working on implementations of this new approach, which w=
e<br>
&gt; hope to have in time for the Interim meeting.<br>
&gt;<br>
&gt;<br>
&gt;&gt; A design document describing the overall approach can be found at:=
<br>
&gt;<br>
&gt;<br>
&gt; <a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__docs=
.google.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8_edit&=
amp;d=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3Dh3Ju9EBS7mHtwg-wAyN7f=
Q&amp;m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&amp;s=3DjDNnz34hmWvLS=
QnHkSnYdihW-jG-0xZ-YYqKq30wVGg&amp;e=3D" rel=3D"noreferrer" target=3D"_blan=
k">https://urldefense.proofpoint.<wbr>com/v2/url?u=3Dhttps-3A__docs.<wbr>go=
ogle.com_document_d_<wbr>1fRsJqPinJl8N3b-<wbr>2DbflDRV6auojfJLkxddT93j6SwHY=
8<wbr>_edit&amp;d=3DDwIBaQ&amp;c=3D<wbr>5VD0RTtNlTh3ycd41b3MUw&amp;r=3D<wbr=
>h3Ju9EBS7mHtwg-wAyN7fQ&amp;m=3D_<wbr>vGK3zTKFrMOkFihJnPntLYw1T0_<wbr>NEMiH=
YSM0Q_u1JA&amp;s=3D<wbr>jDNnz34hmWvLSQnHkSnYdihW-jG-<wbr>0xZ-YYqKq30wVGg&am=
p;e=3D</a><br>
&gt;<br>
&gt;<br>
&gt;&gt; A PR making the changes to the QUIC documents can be found at:<br>
&gt;<br>
&gt;&gt; <a href=3D"https://github.com/quicwg/base-drafts/pull/1377" rel=3D=
"noreferrer" target=3D"_blank">https://github.com/quicwg/<wbr>base-drafts/p=
ull/1377</a><br>
&gt;<br>
&gt;<br>
&gt;&gt; A few design details did not have clear consensus, but it was felt=
 it<br>
&gt; would be better to discuss those in the wider WG than delay the design=
<br>
&gt; team.=C2=A0 A consistent choice was made in the PR and these issues ar=
e<br>
&gt; mentioned in Appendix B of the design doc.<br>
&gt;<br>
&gt;<br>
&gt;&gt; As always, comments and questions welcome. That said, this is a bi=
g PR<br>
&gt; and we recognize that some editorial work is going to be needed before=
<br>
&gt; merging. In the interest of letting people follow along, and to keep g=
ithub<br>
&gt; from falling over, we ask people to keep discussion on the mailing lis=
t and<br>
&gt; refrain from making PR comments.<br>
&gt;<br>
&gt;<br>
&gt;&gt; See you in Kista!<br>
&gt;<br>
&gt;<br>
&gt;&gt; Ian and Eric<br>
&gt;<br>
&gt;<br>
<br>
<br>
<br>
</div></div><span class=3D"HOEnZb"><font color=3D"#888888">-- <br>
Kazuho Oku<br>
<br>
</font></span></blockquote></div><br></div></div>

--000000000000c29d25056ce7d917--


From nobody Wed May 23 16:27:20 2018
Return-Path: <jri.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA163129C6C for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:27:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.689
X-Spam-Level: 
X-Spam-Status: No, score=-2.689 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 YuxTHNywp3_M for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:27:15 -0700 (PDT)
Received: from mail-io0-x22d.google.com (mail-io0-x22d.google.com [IPv6:2607:f8b0:4001:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BB2DE1273B1 for <quic@ietf.org>; Wed, 23 May 2018 16:27:14 -0700 (PDT)
Received: by mail-io0-x22d.google.com with SMTP id d73-v6so93520iog.3 for <quic@ietf.org>; Wed, 23 May 2018 16:27:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=z1xzU1lE5M7B4q8royO+EZRokKVW/97l8AclQRZlbF0=; b=QwNuxvvhXRfHgioGk+iKGIGbG01gDi8Wm9k+LdBOjJNlWWGeA4R65FoAd/gGSTxTme 5s6FOhXiwr5ucCxBAAnY5P/nt/n34v36zAq5jyG/8S3f0krGFOzF7LUM6ZX+ikc+M3Iv K1HlqsavBiI7jlSnv3sszurkgx3PEoa559m5eA0CmLxNSHC4+fzoofw1SYi69YDMLeMH l8PQOCYAH7TX+OsJVIHgswO/KUX6SxWMI+v/kGjsVK+bky4Rj5yc7CtMAMwTL4DbuEVI emF9SEXmRXMh3QDbSkt8yO7STICzEzK1dEn7OVCCvSDX88eqeSnWrvmVusR3PpJ1GMoX /BVg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=z1xzU1lE5M7B4q8royO+EZRokKVW/97l8AclQRZlbF0=; b=PyDwoZd2q6QvCA/sXmgztuRsj2FZhkj5QOndwH8hSDkotgEv5ZcA8fwxKmA+r1sOtY /y7mBc6eXqrNhCdRf3JWixN11oIfxVOlXi5+W/a8C4AfUjf2siz8drweGOL3AuqyxYft HhesjpB/x1zSTe4IOvsZM62hWX/s7Zgoi2aZbXHycI1H15MD1gqJtV6vwLwTdzdQ3fbR 2F945JKa92K8xkfBIXMWbTwIIadY4nzG7Ext47hQ4/9drZywNYXU1JFxXL7/rX2HJDIS PvmQ6RmkMNiiROvNUCesKY2M1DqE+K07ZXWon9GxzqSLuKpoz/dPv0Rr/ZTamzNi+bA0 ZFfg==
X-Gm-Message-State: ALKqPwcT64Y18qKbJwbpYdGWjhS2fyqKfTwJheIJNWMdlw0klkR9YjDq 6fkHBACtrPYoXL8QPnWJTEcNv+0jQUHLUYwhCY9xlg==
X-Google-Smtp-Source: ADUXVKJZ1G7lvM3xa8ZJaa5sviF91sgCoJ88PBphhi4/D990y7AcPE1qlc9hG+IdB9OptQBTFOGCLXWkYV+kvJEd05Q=
X-Received: by 2002:a6b:4119:: with SMTP id n25-v6mr4723806ioa.59.1527118033869;  Wed, 23 May 2018 16:27:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:27d4:0:0:0:0:0 with HTTP; Wed, 23 May 2018 16:27:13 -0700 (PDT)
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Wed, 23 May 2018 16:27:13 -0700
Message-ID: <CACpbDcckRvyn18qowWbLRT+sX2EGj3_yPtoS2d-h6ypg4dFrVQ@mail.gmail.com>
Subject: Re: Stream0 Proposal: EMPTY_ACK
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f066d9056ce7df35"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/PqRNB0HJuZZ0_n3FuewuIm1DY3w>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 23:27:19 -0000

--000000000000f066d9056ce7df35
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

(Moving more discussions from main thread)

---------- Forwarded message ----------
From: Subodh Iyengar <subodh@fb.com>
Date: Wed, May 23, 2018 at 3:37 PM
Subject: Re: Stream0 Design Team Proposal
To: Mike Bishop <mbishop@evequefou.be>, Christian Huitema <
huitema@huitema.net>, "quic@ietf.org" <quic@ietf.org>


FWIW I see EMPTY_ACKs as being very similar to a Duplicate ack. We thought
about using Duplicate acks as well but we thought that EMPTY_ACks would be
simpler to implement and be able to convey similar information.


Subodh
------------------------------
*From:* QUIC <quic-bounces@ietf.org> on behalf of Mike Bishop <
mbishop@evequefou.be>
*Sent:* Wednesday, May 23, 2018 3:26:35 PM
*To:* Christian Huitema; quic@ietf.org
*Subject:* RE: Stream0 Design Team Proposal


Christian, can you expand on why you dislike the EMPTY_ACK?  Being able to
say =E2=80=9CI=E2=80=99ve received some packets from you, but am unable to =
process any of
them because I=E2=80=99m missing some handshake data=E2=80=9D seems like a =
useful way to
short-circuit timeouts on clients.  It also doesn=E2=80=99t commit the serv=
er to
holding any state =E2=80=93 IIUC, a server could form a packet containing a=
n
EMPTY_ACK and then discard its internal state until it gets the
retransmitted (or delayed) Initial packet.





On Wed, May 23, 2018 at 4:25 PM, Jana Iyengar <jri.ietf@gmail.com> wrote:

> (Forking this discussion off from the main thread.)
>
> On Wed, May 23, 2018 at 2:13 AM, Kazuho Oku <kazuhooku@gmail.com> wrote:
>
>> 2018-05-23 14:29 GMT+09:00 Christian Huitema <huitema@huitema.net>:
>> > I like the proposal. In particular, I really like the encryption of
>> > handshake packets with the handshake key, as it does close a number of
>> > avenues for attacks. And I like that it solves the "ack promotion" iss=
ue
>> > that I was complaining against for some time. Turns out that in the
>> current
>> > draft, it is very hard to contain that problem if you enable client
>> auth.
>> >
>> >
>> > On the other hand, I agree with Martin that a lot of the additions to
>> > transmission recovery should be moved to separate PRs. I am not
>> enthusiastic
>> > with the EMPTY ACK mechanism, or with the proposed "implicit
>> > acknowledgement" of a lower crypto stream by a higher level ack.
>>
>> At the moment I do not have a strong opinion on the Empty ACK mechanism.
>>
>> However, regarding how we close the Initial and Handshake contexts, my
>> preference goes to using implicit ACKs (i.e. use the successful
>> receipt of a packet that is protected under a higher level of
>> encryption key as the signal) rather than explicitly ACKing the last
>> flight of data.
>>
>> As I see, there are two downsides in the Explicit ACKing approach.
>>
>> * Explicit ACKing requires sending two additional packets during the
>> handshake, which means that we would have more AES operations plus
>> somewhere around 60 bytes of overhead on the wire.
>> * Explicit ACKing requires more signaling from the TLS stack. In case
>> of implicit ACKing, the TLS stack need to only provide the AEAD
>> contexts and the messages, whereas in case of explicit ACKing, the TLS
>> stack also needs to provide a signal indicating the end of the
>> transmission at each encryption level.
>>
>> The downside of the implicit ACKing approach is that the server needs
>> to signal the termination of the Handshake context using a special
>> frame sent using a 1-RTT packet.
>>
>> But even taking that into consideration, I think that implicit ACKing
>> is still easier to implement, considering the need for the additional
>> signal in the explicit ACK case that have been described above.
>>
>>
>> > In any
>> > case, starting as simple as possible would help having the first
>> > implementations and tests.
>> >
>> >
>> > On 5/22/2018 8:26 PM, Subodh Iyengar wrote:
>> >
>> > As an implementor of fizz, I support this design and am willing to
>> implement
>> > this as well.
>> >
>> >
>> > While this is a change in the API that TLS classically exposes, I thin=
k
>> this
>> > is the right tradeoff because it helps make things way more explicit
>> which
>> > will prevent several other bugs from happening in the future.
>> >
>> >
>> > Subodh
>> >
>> > ________________________________
>> > From: QUIC <quic-bounces@ietf.org> on behalf of Martin Thomson
>> > <martin.thomson@gmail.com>
>> > Sent: Tuesday, May 22, 2018 8:00:40 PM
>> > To: Ian Swett
>> > Cc: ekr@mozilla.com; QUIC WG
>> > Subject: Re: Stream0 Design Team Proposal
>> >
>> > First of all, thanks to the design team for the work they have done.  =
I
>> > haven't digested everything yet, but I think that I have a good sense =
of
>> > the shape of the proposal.
>> >
>> > Overall, this looks like a workable design.  It's a lot more invasive =
of
>> > the cryptographic handshake implementation than I had thought people
>> were
>> > willing to stomach originally.  But it's clear that we've run into
>> problems
>> > with the current, more abstract API and this is a fairly natural way t=
o
>> > split TLS.  I've spent a little time thinking about how this might be
>> > implemented and I think that it's not going to be *too* painful.  The
>> proof
>> > will be in the pudding there though.
>> >
>> > In looking at the PR, I really appreciate seeing all the changes
>> together..
>> > BTW, the link above points to the wrong PR, so be careful (it appears =
to
>> > have the same content, but that's not guaranteed).  The actual PR is
>> here:
>> > https://github.com/quicwg/base-drafts/pull/1377
>> >
>> > I've pushed a branch to the main repo so that you can preview the enti=
re
>> > document set:
>> > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__quicwg.
>> github.io_base-2Ddrafts_stream0_&d=3DDwIBaQ&c=3D5VD0RTtNlTh3ycd4
>> 1b3MUw&r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&m=3D_vGK3zTKFrMOkFihJnPn
>> tLYw1T0_NEMiHYSM0Q_u1JA&s=3DususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&=
e=3D
>> >
>> > It seems like there are some core changes here and a bunch of separabl=
e
>> or
>> > at least secondary changes.  I'm sure that each one has its own
>> > justification, but that isn't always clear. The following changes seem
>> like
>> > they are separable:
>> >
>> > * The use of separate packet number spaces
>> > * The Retry packet changes (and NEW_TOKEN)
>> > * EMPTY_ACK
>> > * The TLS extension for flow control
>> >
>> > Right now, some of these appear to be entirely gratuitous.  I'd like t=
o
>> get
>> > to the bottom of each before we continue.
>> >
>> > At a minimum, the PR we land first should include just the core change=
s.
>> > As you say, reviewing a monster PR like this will only make GitHub wee=
p
>> > unicorns, but we might be able to cut this into smaller pieces.
>> >
>> > On Wed, May 23, 2018 at 11:31 AM Ian Swett <ianswett=3D
>> > 40google.com@dmarc.ietf.org> wrote:
>> >
>> >> Dear QUIC WG,
>> >
>> >
>> >> On behalf of the Stream 0 Design Team, I am pleased to report that we
>> > have consensus on a proposed approach to share with the WG. The DT's
>> > proposal will make QUIC and TLS work closer together and incorporates
>> ideas
>> > from DTLS, but it does not use the DTLS protocol itself.
>> >
>> >
>> >> The DT believes this solves the important open Stream 0 issues. The
>> > proposal will be a bit more invasive in TLS, but we believe it is the
>> right
>> > long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS, a=
nd
>> > Mint) are willing and able to do the work necessary.. A number of stac=
ks
>> > are currently working on implementations of this new approach, which w=
e
>> > hope to have in time for the Interim meeting.
>> >
>> >
>> >> A design document describing the overall approach can be found at:
>> >
>> >
>> > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__docs.go
>> ogle.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j
>> 6SwHY8_edit&d=3DDwIBaQ&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3Dh3Ju9EBS7mHt
>> wg-wAyN7fQ&m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&s=3Dj
>> DNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg&e=3D
>> >
>> >
>> >> A PR making the changes to the QUIC documents can be found at:
>> >
>> >> https://github.com/quicwg/base-drafts/pull/1377
>> >
>> >
>> >> A few design details did not have clear consensus, but it was felt it
>> > would be better to discuss those in the wider WG than delay the design
>> > team.  A consistent choice was made in the PR and these issues are
>> > mentioned in Appendix B of the design doc.
>> >
>> >
>> >> As always, comments and questions welcome. That said, this is a big P=
R
>> > and we recognize that some editorial work is going to be needed before
>> > merging. In the interest of letting people follow along, and to keep
>> github
>> > from falling over, we ask people to keep discussion on the mailing lis=
t
>> and
>> > refrain from making PR comments.
>> >
>> >
>> >> See you in Kista!
>> >
>> >
>> >> Ian and Eric
>> >
>> >
>>
>>
>>
>> --
>> Kazuho Oku
>>
>>
>

--000000000000f066d9056ce7df35
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>(Moving more discussions from main thread)</div><div>=
<br></div>---------- Forwarded message ----------<br>From:<span>=C2=A0</spa=
n><b class=3D"gmail_sendername">Subodh Iyengar</b><span>=C2=A0</span><span =
dir=3D"ltr">&lt;<a href=3D"mailto:subodh@fb.com">subodh@fb.com</a>&gt;</spa=
n><br>Date: Wed, May 23, 2018 at 3:37 PM<br>Subject: Re: Stream0 Design Tea=
m Proposal<br>To: Mike Bishop &lt;<a href=3D"mailto:mbishop@evequefou.be">m=
bishop@evequefou.be</a>&gt;, Christian Huitema &lt;<a href=3D"mailto:huitem=
a@huitema.net">huitema@huitema.net</a>&gt;, &quot;<a href=3D"mailto:quic@ie=
tf.org">quic@ietf.org</a>&quot; &lt;<a href=3D"mailto:quic@ietf.org">quic@i=
etf.org</a>&gt;<br><br><br><div dir=3D"ltr"><div id=3D"gmail-m_-63734183374=
59262039divtagdefaultwrapper" dir=3D"ltr" style=3D"font-size:12pt;color:rgb=
(0,0,0);font-family:Calibri,Helvetica,sans-serif"><p style=3D"margin-top:0p=
x;margin-bottom:0px">FWIW I see EMPTY_ACKs as being very similar to a Dupli=
cate ack. We thought about using Duplicate acks as well but we thought that=
 EMPTY_ACks would be simpler to implement and be able to convey similar=C2=
=A0information.<br></p><p style=3D"margin-top:0px;margin-bottom:0px"><br></=
p><p style=3D"margin-top:0px;margin-bottom:0px">Subodh<br></p></div><hr sty=
le=3D"display:inline-block;width:1427.78px"><div id=3D"gmail-m_-63734183374=
59262039divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" color=
=3D"#000000" style=3D"font-size:11pt"><b>From:</b><span>=C2=A0</span>QUIC &=
lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_blank" style=3D"colo=
r:rgb(17,85,204)">quic-bounces@ietf.org</a>&gt; on behalf of Mike Bishop &l=
t;<a href=3D"mailto:mbishop@evequefou.be" target=3D"_blank" style=3D"color:=
rgb(17,85,204)">mbishop@evequefou.be</a>&gt;<br><b>Sent:</b><span>=C2=A0</s=
pan>Wednesday, May 23, 2018 3:26:35 PM<br><b>To:</b><span>=C2=A0</span>Chri=
stian Huitema;<span>=C2=A0</span><a href=3D"mailto:quic@ietf.org" target=3D=
"_blank" style=3D"color:rgb(17,85,204)">quic@ietf.org</a><br><b>Subject:</b=
><span>=C2=A0</span>RE: Stream0 Design Team Proposal</font><div>=C2=A0</div=
></div><div><div class=3D"gmail-h5" style=3D"display:block;color:rgb(80,0,8=
0)"><div lang=3D"EN-US" style=3D"background-color:white"><div class=3D"gmai=
l-m_-6373418337459262039x_WordSection1"><p class=3D"gmail-m_-63734183374592=
62039x_MsoNormal" style=3D"color:rgb(80,0,80);font-family:arial,sans-serif;=
font-size:small;font-style:normal;font-variant-ligatures:normal;font-varian=
t-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-i=
ndent:0px;text-transform:none;white-space:normal;word-spacing:0px;backgroun=
d-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-colo=
r:initial"><span style=3D"color:windowtext">Christian, can you expand on wh=
y you dislike the EMPTY_ACK?=C2=A0 Being able to say =E2=80=9CI=E2=80=99ve =
received some packets from you, but am unable to process any of them becaus=
e I=E2=80=99m missing some handshake data=E2=80=9D seems like a useful way =
to short-circuit timeouts on clients.=C2=A0 It also doesn=E2=80=99t commit =
the server to holding any state =E2=80=93 IIUC, a server could form a packe=
t containing an EMPTY_ACK and then discard its internal state until it gets=
 the retransmitted (or delayed) Initial packet.</span></p><p class=3D"gmail=
-m_-6373418337459262039x_MsoNormal" style=3D"color:rgb(80,0,80);font-family=
:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:=
normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-=
align:start;text-indent:0px;text-transform:none;white-space:normal;word-spa=
cing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;te=
xt-decoration-color:initial"><span style=3D"color:windowtext">=C2=A0</span>=
</p><div style=3D"color:rgb(80,0,80);font-family:arial,sans-serif;font-size=
:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:no=
rmal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px=
;text-transform:none;white-space:normal;word-spacing:0px;background-color:r=
gb(255,255,255);text-decoration-style:initial;text-decoration-color:initial=
"><div style=3D"border-right:none;border-bottom:none;border-left:none;borde=
r-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in"><br class=3D"gmail-Ap=
ple-interchange-newline"></div></div></div></div></div></div></div><br><div=
 class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, May 23, 2018 =
at 4:25 PM, Jana Iyengar <span dir=3D"ltr">&lt;<a href=3D"mailto:jri.ietf@g=
mail.com" target=3D"_blank">jri.ietf@gmail.com</a>&gt;</span> wrote:<br><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #=
ccc solid;padding-left:1ex"><div dir=3D"ltr">(Forking this discussion off f=
rom the main thread.)<br><div class=3D"gmail_extra"><br><div class=3D"gmail=
_quote">On Wed, May 23, 2018 at 2:13 AM, Kazuho Oku <span dir=3D"ltr">&lt;<=
a href=3D"mailto:kazuhooku@gmail.com" target=3D"_blank">kazuhooku@gmail.com=
</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin=
:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>2018-05-23 1=
4:29 GMT+09:00 Christian Huitema &lt;<a href=3D"mailto:huitema@huitema.net"=
 target=3D"_blank">huitema@huitema.net</a>&gt;:<br>
&gt; I like the proposal. In particular, I really like the encryption of<br=
>
&gt; handshake packets with the handshake key, as it does close a number of=
<br>
&gt; avenues for attacks. And I like that it solves the &quot;ack promotion=
&quot; issue<br>
&gt; that I was complaining against for some time. Turns out that in the cu=
rrent<br>
&gt; draft, it is very hard to contain that problem if you enable client au=
th.<br>
&gt;<br>
&gt;<br>
&gt; On the other hand, I agree with Martin that a lot of the additions to<=
br>
&gt; transmission recovery should be moved to separate PRs. I am not enthus=
iastic<br>
&gt; with the EMPTY ACK mechanism, or with the proposed &quot;implicit<br>
&gt; acknowledgement&quot; of a lower crypto stream by a higher level ack.<=
br>
<br>
</span>At the moment I do not have a strong opinion on the Empty ACK mechan=
ism.<br>
<br>
However, regarding how we close the Initial and Handshake contexts, my<br>
preference goes to using implicit ACKs (i.e. use the successful<br>
receipt of a packet that is protected under a higher level of<br>
encryption key as the signal) rather than explicitly ACKing the last<br>
flight of data.<br>
<br>
As I see, there are two downsides in the Explicit ACKing approach.<br>
<br>
* Explicit ACKing requires sending two additional packets during the<br>
handshake, which means that we would have more AES operations plus<br>
somewhere around 60 bytes of overhead on the wire.<br>
* Explicit ACKing requires more signaling from the TLS stack. In case<br>
of implicit ACKing, the TLS stack need to only provide the AEAD<br>
contexts and the messages, whereas in case of explicit ACKing, the TLS<br>
stack also needs to provide a signal indicating the end of the<br>
transmission at each encryption level.<br>
<br>
The downside of the implicit ACKing approach is that the server needs<br>
to signal the termination of the Handshake context using a special<br>
frame sent using a 1-RTT packet.<br>
<br>
But even taking that into consideration, I think that implicit ACKing<br>
is still easier to implement, considering the need for the additional<br>
signal in the explicit ACK case that have been described above.<br>
<div><div class=3D"m_-1934665759982005286h5"><br>
<br>
&gt; In any<br>
&gt; case, starting as simple as possible would help having the first<br>
&gt; implementations and tests.<br>
&gt;<br>
&gt;<br>
&gt; On 5/22/2018 8:26 PM, Subodh Iyengar wrote:<br>
&gt;<br>
&gt; As an implementor of fizz, I support this design and am willing to imp=
lement<br>
&gt; this as well.<br>
&gt;<br>
&gt;<br>
&gt; While this is a change in the API that TLS classically exposes, I thin=
k this<br>
&gt; is the right tradeoff because it helps make things way more explicit w=
hich<br>
&gt; will prevent several other bugs from happening in the future.<br>
&gt;<br>
&gt;<br>
&gt; Subodh<br>
&gt;<br>
&gt; ______________________________<wbr>__<br>
&gt; From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_bla=
nk">quic-bounces@ietf.org</a>&gt; on behalf of Martin Thomson<br>
&gt; &lt;<a href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">mart=
in.thomson@gmail.com</a>&gt;<br>
&gt; Sent: Tuesday, May 22, 2018 8:00:40 PM<br>
&gt; To: Ian Swett<br>
&gt; Cc: <a href=3D"mailto:ekr@mozilla.com" target=3D"_blank">ekr@mozilla.c=
om</a>; QUIC WG<br>
&gt; Subject: Re: Stream0 Design Team Proposal<br>
&gt;<br>
&gt; First of all, thanks to the design team for the work they have done.=
=C2=A0 I<br>
&gt; haven&#39;t digested everything yet, but I think that I have a good se=
nse of<br>
&gt; the shape of the proposal.<br>
&gt;<br>
&gt; Overall, this looks like a workable design.=C2=A0 It&#39;s a lot more =
invasive of<br>
&gt; the cryptographic handshake implementation than I had thought people w=
ere<br>
&gt; willing to stomach originally.=C2=A0 But it&#39;s clear that we&#39;ve=
 run into problems<br>
&gt; with the current, more abstract API and this is a fairly natural way t=
o<br>
&gt; split TLS.=C2=A0 I&#39;ve spent a little time thinking about how this =
might be<br>
&gt; implemented and I think that it&#39;s not going to be *too* painful.=
=C2=A0 The proof<br>
&gt; will be in the pudding there though.<br>
&gt;<br>
</div></div>&gt; In looking at the PR, I really appreciate seeing all the c=
hanges together..<br>
<div class=3D"m_-1934665759982005286HOEnZb"><div class=3D"m_-19346657599820=
05286h5">&gt; BTW, the link above points to the wrong PR, so be careful (it=
 appears to<br>
&gt; have the same content, but that&#39;s not guaranteed).=C2=A0 The actua=
l PR is here:<br>
&gt; <a href=3D"https://github.com/quicwg/base-drafts/pull/1377" rel=3D"nor=
eferrer" target=3D"_blank">https://github.com/quicwg/base<wbr>-drafts/pull/=
1377</a><br>
&gt;<br>
&gt; I&#39;ve pushed a branch to the main repo so that you can preview the =
entire<br>
&gt; document set:<br>
&gt; <a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__quic=
wg.github.io_base-2Ddrafts_stream0_&amp;d=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd4=
1b3MUw&amp;r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&amp;m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_N=
EMiHYSM0Q_u1JA&amp;s=3DususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&amp;e=3D=
" rel=3D"noreferrer" target=3D"_blank">https://urldefense.proofpoint.<wbr>c=
om/v2/url?u=3Dhttps-3A__quicwg.<wbr>github.io_base-2Ddrafts_stream<wbr>0_&a=
mp;d=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd4<wbr>1b3MUw&amp;r=3Dh3Ju9EBS7mHtwg-<w=
br>wAyN7fQ&amp;m=3D_vGK3zTKFrMOkFihJnPn<wbr>tLYw1T0_NEMiHYSM0Q_u1JA&amp;s=
=3Dusus<wbr>mtxI3BTaLlBWe_HkQUWRH4sBI0Cggj<wbr>1oWZMBHak&amp;e=3D</a><br>
&gt;<br>
&gt; It seems like there are some core changes here and a bunch of separabl=
e or<br>
&gt; at least secondary changes.=C2=A0 I&#39;m sure that each one has its o=
wn<br>
&gt; justification, but that isn&#39;t always clear. The following changes =
seem like<br>
&gt; they are separable:<br>
&gt;<br>
&gt; * The use of separate packet number spaces<br>
&gt; * The Retry packet changes (and NEW_TOKEN)<br>
&gt; * EMPTY_ACK<br>
&gt; * The TLS extension for flow control<br>
&gt;<br>
&gt; Right now, some of these appear to be entirely gratuitous.=C2=A0 I&#39=
;d like to get<br>
&gt; to the bottom of each before we continue.<br>
&gt;<br>
&gt; At a minimum, the PR we land first should include just the core change=
s.<br>
&gt; As you say, reviewing a monster PR like this will only make GitHub wee=
p<br>
&gt; unicorns, but we might be able to cut this into smaller pieces.<br>
&gt;<br>
&gt; On Wed, May 23, 2018 at 11:31 AM Ian Swett &lt;ianswett=3D<br>
&gt; <a href=3D"mailto:40google.com@dmarc.ietf.org" target=3D"_blank">40goo=
gle.com@dmarc.ietf.org</a>&gt; wrote:<br>
&gt;<br>
&gt;&gt; Dear QUIC WG,<br>
&gt;<br>
&gt;<br>
&gt;&gt; On behalf of the Stream 0 Design Team, I am pleased to report that=
 we<br>
&gt; have consensus on a proposed approach to share with the WG. The DT&#39=
;s<br>
&gt; proposal will make QUIC and TLS work closer together and incorporates =
ideas<br>
&gt; from DTLS, but it does not use the DTLS protocol itself.<br>
&gt;<br>
&gt;<br>
&gt;&gt; The DT believes this solves the important open Stream 0 issues. Th=
e<br>
&gt; proposal will be a bit more invasive in TLS, but we believe it is the =
right<br>
&gt; long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS, a=
nd<br>
&gt; Mint) are willing and able to do the work necessary.. A number of stac=
ks<br>
&gt; are currently working on implementations of this new approach, which w=
e<br>
&gt; hope to have in time for the Interim meeting.<br>
&gt;<br>
&gt;<br>
&gt;&gt; A design document describing the overall approach can be found at:=
<br>
&gt;<br>
&gt;<br>
&gt; <a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__docs=
.google.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8_edit&=
amp;d=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3Dh3Ju9EBS7mHtwg-wAyN7f=
Q&amp;m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&amp;s=3DjDNnz34hmWvLS=
QnHkSnYdihW-jG-0xZ-YYqKq30wVGg&amp;e=3D" rel=3D"noreferrer" target=3D"_blan=
k">https://urldefense.proofpoint.<wbr>com/v2/url?u=3Dhttps-3A__docs.go<wbr>=
ogle.com_document_d_1fRsJqPinJ<wbr>l8N3b-2DbflDRV6auojfJLkxddT93j<wbr>6SwHY=
8_edit&amp;d=3DDwIBaQ&amp;c=3D5VD0RTt<wbr>NlTh3ycd41b3MUw&amp;r=3Dh3Ju9EBS7=
mHt<wbr>wg-wAyN7fQ&amp;m=3D_vGK3zTKFrMOkFihJ<wbr>nPntLYw1T0_NEMiHYSM0Q_u1JA=
&amp;s=3Dj<wbr>DNnz34hmWvLSQnHkSnYdihW-jG-0xZ<wbr>-YYqKq30wVGg&amp;e=3D</a>=
<br>
&gt;<br>
&gt;<br>
&gt;&gt; A PR making the changes to the QUIC documents can be found at:<br>
&gt;<br>
&gt;&gt; <a href=3D"https://github.com/quicwg/base-drafts/pull/1377" rel=3D=
"noreferrer" target=3D"_blank">https://github.com/quicwg/base<wbr>-drafts/p=
ull/1377</a><br>
&gt;<br>
&gt;<br>
&gt;&gt; A few design details did not have clear consensus, but it was felt=
 it<br>
&gt; would be better to discuss those in the wider WG than delay the design=
<br>
&gt; team.=C2=A0 A consistent choice was made in the PR and these issues ar=
e<br>
&gt; mentioned in Appendix B of the design doc.<br>
&gt;<br>
&gt;<br>
&gt;&gt; As always, comments and questions welcome. That said, this is a bi=
g PR<br>
&gt; and we recognize that some editorial work is going to be needed before=
<br>
&gt; merging. In the interest of letting people follow along, and to keep g=
ithub<br>
&gt; from falling over, we ask people to keep discussion on the mailing lis=
t and<br>
&gt; refrain from making PR comments.<br>
&gt;<br>
&gt;<br>
&gt;&gt; See you in Kista!<br>
&gt;<br>
&gt;<br>
&gt;&gt; Ian and Eric<br>
&gt;<br>
&gt;<br>
<br>
<br><span class=3D"HOEnZb"><font color=3D"#888888">
<br>
</font></span></div></div><span class=3D"HOEnZb"><font color=3D"#888888"><s=
pan class=3D"m_-1934665759982005286HOEnZb"><font color=3D"#888888">-- <br>
Kazuho Oku<br>
<br>
</font></span></font></span></blockquote></div><br></div></div>
</blockquote></div><br></div></div>

--000000000000f066d9056ce7df35--


From nobody Wed May 23 16:41:33 2018
Return-Path: <ekr@rtfm.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5383612E88A for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:41:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level: 
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, T_DKIMWL_WL_MED=-0.01, T_KAM_HTML_FONT_INVALID=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 py9Yw-Pbfh0C for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:41:13 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6C55A12D941 for <quic@ietf.org>; Wed, 23 May 2018 16:41:13 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id a6-v6so21106877oia.2 for <quic@ietf.org>; Wed, 23 May 2018 16:41:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=E0C2ztHaNFtqNNG5wG1SNdl018NoxiHvx6bbqGW8PBI=; b=cSIR3mG3FBGRDCmwmZb5V0avTxSwIHh9chzxYc0UsmAGRBuqKqUCn1Kj6j3rk3xqZO gwbTEzoBlRR8x8O/I+Jz1qUz9RR49u6p5Nw3z8fIGDtCb1tgFBx6Mqvmdg4vIZdmsf2w 3PTDLrj4JzRP9wSou+XNDzh283ClCDirHPgL7pXakIxy7Pp40b1SzqsPp3LSrOWTS/Tk b30/c4yWd+VFl0+OhlMTMxs0sBQGOXjIW/3jeH+FJuqY1JhVYUEC3TWnY2xJgCtdkMoP SE+8BNFgER4hc8FXdh/TRKLC9yIfVzkbNrneub1yioxPf4A2VsdizW49bfVq/aVFMYIs P4Hw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=E0C2ztHaNFtqNNG5wG1SNdl018NoxiHvx6bbqGW8PBI=; b=BF0GdnsKxtqDbtbRqKElf8QkT0x7su7W3YY17YPD+lDNL5Yu8jd3na6hm3KnkhHeFn 1fMv4SR8xffOhgOenkvnU60+nF77W02wSZmfA+hzQjJyDRZCf/LEJybFjl5zWeCE9kg8 OoT6B4Rp3sxQT8VqwT6OV36GdiA9jGCm10kR1TgLW1rF8O7zPNfZBGPGVnrOBi4K6wsi 7iR4/gNlomBVUpfHcG4couiCV2KdScw649q7PwO6JWNvYh6ckGc9mBrUG6iSEEzIAJMU NBvW/A5lClHQ9gpvfw5Dsn6PaxbQ6G31BnWDfgE3EXDdpjZCFUrivlwed3sE28kNNVI0 kBzg==
X-Gm-Message-State: ALKqPwfHY4M3XLRq+31XE8RaDW+vPd6KHu95U3an9U5e7vaYONTXo+7Z yBhUrrOCsxNvitZh/t4oxpjcEn+E9vHhtN12LY36uA==
X-Google-Smtp-Source: AB8JxZofLVEfQ6GGHERKHF0g+OmatljnYDDbH+C3gCqZnsnEih9ueWeXpVeTT/crafMmIAT0Y4zfL2LMwJu+g73EbTI=
X-Received: by 2002:aca:3cc1:: with SMTP id j184-v6mr2794275oia.91.1527118871984;  Wed, 23 May 2018 16:41:11 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:ac9:66:0:0:0:0:0 with HTTP; Wed, 23 May 2018 16:40:31 -0700 (PDT)
In-Reply-To: <SN1PR08MB1854BF85FCCA0F21CE0DA1A4DA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CABkgnnUB=jqwFzb2rjBHUFzOgu0hX0YUgaf5kW5ENNGKP+mGiA@mail.gmail.com> <SN1PR08MB1854BF85FCCA0F21CE0DA1A4DA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 23 May 2018 16:40:31 -0700
Message-ID: <CABcZeBMK5mpM26vWs5+gAAnmzkNtytHGSJ8dUjRM4ihf21yZHw@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: Mike Bishop <mbishop@evequefou.be>
Cc: Martin Thomson <martin.thomson@gmail.com>,  Ian Swett <ianswett=40google.com@dmarc.ietf.org>, "ekr@mozilla.com" <ekr@mozilla.com>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e50fa2056ce81188"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/109rn0qqZ-Su_cDbL6f4yOLVt9I>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 23:41:31 -0000

--000000000000e50fa2056ce81188
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, May 23, 2018 at 3:23 PM, Mike Bishop <mbishop@evequefou.be> wrote:

> So I think that=E2=80=99s roughly six PRs we should expect to see out of =
the
> design team=E2=80=99s proposal.  A few of them have dependencies on each =
other, but
> they seem mostly separable.  It sounds like several of them have consensu=
s
> in the design team, but not all of them, and it would be good to be able =
to
> discuss them separately
>

Hi Mike,

The vast majority of the proposal had consensus in the design team. It's
true that there are a few pieces that had somewhat less support and we just
made a decision in the interest of having a coherent proposal. These points
are called out explicitly in the Overview document.

With that said, I think it would be better to resist the urge to try to
decompose the proposal into its minimal constituent pieces. In many cases,
even when a piece is in theory independent from other pieces, there are
interactions and so we made a conscious decision to present it as a whole
proposal. Obviously, if there are explicit things that people object to,
they should raise them, but I think trying to break the proposal up into
pieces and consider them individually -- while intellectually interesting
--  isn't going to be that productive.

-Ekr



>
> -----Original Message-----
> From: QUIC <quic-bounces@ietf.org> On Behalf Of Martin Thomson
> Sent: Tuesday, May 22, 2018 8:01 PM
> To: Ian Swett <ianswett=3D40google.com@dmarc.ietf.org>
> Cc: ekr@mozilla.com; QUIC WG <quic@ietf.org>
> Subject: Re: Stream0 Design Team Proposal
>
>
>
> First of all, thanks to the design team for the work they have done.  I
> haven't digested everything yet, but I think that I have a good sense of
> the shape of the proposal.
>
>
>
> Overall, this looks like a workable design.  It's a lot more invasive of
> the cryptographic handshake implementation than I had thought people were
> willing to stomach originally.  But it's clear that we've run into proble=
ms
> with the current, more abstract API and this is a fairly natural way to
> split TLS.  I've spent a little time thinking about how this might be
> implemented and I think that it's not going to be *too* painful.  The pro=
of
> will be in the pudding there though.
>
>
>
> In looking at the PR, I really appreciate seeing all the changes together=
.
>
> BTW, the link above points to the wrong PR, so be careful (it appears to
> have the same content, but that's not guaranteed).  The actual PR is here=
:
>
> https://github.com/quicwg/base-drafts/pull/1377
>
>
>
> I've pushed a branch to the main repo so that you can preview the entire
> document set: https://quicwg.github.io/base-drafts/stream0/
>
>
>
> It seems like there are some core changes here and a bunch of separable o=
r
> at least secondary changes.  I'm sure that each one has its own
> justification, but that isn't always clear. The following changes seem li=
ke
> they are separable:
>
>
>
> * The use of separate packet number spaces
>
> * The Retry packet changes (and NEW_TOKEN)
>
> * EMPTY_ACK
>
> * The TLS extension for flow control
>
>
>
> Right now, some of these appear to be entirely gratuitous.  I'd like to
> get to the bottom of each before we continue.
>
>
>
> At a minimum, the PR we land first should include just the core changes.
>
> As you say, reviewing a monster PR like this will only make GitHub weep
> unicorns, but we might be able to cut this into smaller pieces.
>
>
>
> On Wed, May 23, 2018 at 11:31 AM Ian Swett <ianswett=3D
> 40google.com@dmarc.ietf.org> wrote:
>
>
>
> > Dear QUIC WG,
>
>
>
>
>
> > On behalf of the Stream 0 Design Team, I am pleased to report that we
>
> have consensus on a proposed approach to share with the WG. The DT's
> proposal will make QUIC and TLS work closer together and incorporates ide=
as
> from DTLS, but it does not use the DTLS protocol itself.
>
>
>
>
>
> > The DT believes this solves the important open Stream 0 issues. The
>
> proposal will be a bit more invasive in TLS, but we believe it is the
> right long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS=
,
> and
>
> Mint) are willing and able to do the work necessary.. A number of stacks
> are currently working on implementations of this new approach, which we
> hope to have in time for the Interim meeting.
>
>
>
>
>
> > A design document describing the overall approach can be found at:
>
>
>
>
>
> https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6au
> ojfJLkxddT93j6SwHY8/edit
>
>
>
>
>
> > A PR making the changes to the QUIC documents can be found at:
>
>
>
> > https://github.com/quicwg/base-drafts/pull/1377
>
>
>
>
>
> > A few design details did not have clear consensus, but it was felt it
>
> would be better to discuss those in the wider WG than delay the design
> team.  A consistent choice was made in the PR and these issues are
> mentioned in Appendix B of the design doc.
>
>
>
>
>
> > As always, comments and questions welcome. That said, this is a big PR
>
> and we recognize that some editorial work is going to be needed before
> merging. In the interest of letting people follow along, and to keep gith=
ub
> from falling over, we ask people to keep discussion on the mailing list a=
nd
> refrain from making PR comments.
>
>
>
>
>
> > See you in Kista!
>
>
>
>
>
> > Ian and Eric
>
>
>

--000000000000e50fa2056ce81188
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, May 23, 2018 at 3:23 PM, Mike Bishop <span dir=3D"ltr">&lt;<a h=
ref=3D"mailto:mbishop@evequefou.be" target=3D"_blank">mbishop@evequefou.be<=
/a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:=
0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div link=3D"#0563C=
1" vlink=3D"#954F72" lang=3D"EN-US"><div class=3D"m_-7725196871598781590m_-=
1728187892838803882WordSection1"><p class=3D"m_-7725196871598781590m_-17281=
87892838803882MsoPlainText">So I think that=E2=80=99s roughly six PRs we sh=
ould expect to see out of the design team=E2=80=99s proposal.=C2=A0 A few o=
f them have dependencies on each other, but they seem mostly separable.=C2=
=A0 It sounds like several of them have consensus in the design
 team, but not all of them, and it would be good to be able to discuss them=
 separately</p></div></div></blockquote><div><br></div><div>Hi Mike,</div><=
div><br></div><div>The vast majority of the proposal had consensus in the d=
esign team. It&#39;s true that there are a few pieces that had somewhat les=
s support and we just made a decision in the interest of having a coherent =
proposal. These points are called out explicitly in the Overview document.<=
/div><div><br></div><div>With that said, I think it would be better to resi=
st the urge to try to decompose the proposal into its minimal constituent p=
ieces. In many cases, even when a piece is in theory independent from other=
 pieces, there are interactions and so we made a conscious decision to pres=
ent it as a whole proposal. Obviously, if there are explicit things that pe=
ople object to, they should raise them, but I think trying to break the pro=
posal up into pieces and consider them individually -- while intellectually=
 interesting --=C2=A0 isn&#39;t going to be that productive.<br></div><div>=
<br></div><div>-Ekr</div><div><br></div><div> <br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rg=
b(204,204,204);padding-left:1ex"><div link=3D"#0563C1" vlink=3D"#954F72" la=
ng=3D"EN-US"><div class=3D"m_-7725196871598781590m_-1728187892838803882Word=
Section1"><p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainT=
ext"><u></u></p><p class=3D"m_-7725196871598781590m_-1728187892838803882Mso=
PlainText"><u></u></p><span>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">-----=
Original Message-----<br>
From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_blank">q=
uic-bounces@ietf.org</a>&gt; On Behalf Of Martin Thomson<br>
Sent: Tuesday, May 22, 2018 8:01 PM<br>
To: Ian Swett &lt;ianswett=3D<a href=3D"mailto:40google.com@dmarc.ietf.org"=
 target=3D"_blank">40google.com@dmarc.i<wbr>etf.org</a>&gt;<br>
Cc: <a href=3D"mailto:ekr@mozilla.com" target=3D"_blank">ekr@mozilla.com</a=
>; QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic@ietf=
.org</a>&gt;<br>
Subject: Re: Stream0 Design Team Proposal</p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
</span><p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText=
">First of all, thanks to the design team for the work they have done.=C2=
=A0 I haven&#39;t digested everything yet, but I think that I have a good s=
ense of the shape of the proposal.<u></u><u></u></p><div><div class=3D"m_-7=
725196871598781590h5">
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">Overa=
ll, this looks like a workable design.=C2=A0 It&#39;s a lot more invasive o=
f the cryptographic handshake implementation than I had thought people were=
 willing to stomach originally.=C2=A0 But it&#39;s clear that we&#39;ve run=
 into problems with the current,
 more abstract API and this is a fairly natural way to split TLS.=C2=A0 I&#=
39;ve spent a little time thinking about how this might be implemented and =
I think that it&#39;s not going to be *too* painful.=C2=A0 The proof will b=
e in the pudding there though.<u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">In lo=
oking at the PR, I really appreciate seeing all the changes together.<u></u=
><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">BTW, =
the link above points to the wrong PR, so be careful (it appears to have th=
e same content, but that&#39;s not guaranteed).=C2=A0 The actual PR is here=
:<u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><a hr=
ef=3D"https://github.com/quicwg/base-drafts/pull/1377" target=3D"_blank"><s=
pan style=3D"color:windowtext;text-decoration:none">https://github.com/quic=
wg/base<wbr>-drafts/pull/1377</span></a><u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">I&#39=
;ve pushed a branch to the main repo so that you can preview the entire doc=
ument set:
<a href=3D"https://quicwg.github.io/base-drafts/stream0/" target=3D"_blank"=
><span style=3D"color:windowtext;text-decoration:none">https://quicwg.githu=
b.io/base-<wbr>drafts/stream0/</span></a><u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">It se=
ems like there are some core changes here and a bunch of separable or at le=
ast secondary changes.=C2=A0 I&#39;m sure that each one has its own justifi=
cation, but that isn&#39;t always clear. The following changes seem like th=
ey are separable:<u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">* The=
 use of separate packet number spaces<u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">* The=
 Retry packet changes (and NEW_TOKEN)<u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">* EMP=
TY_ACK<u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">* The=
 TLS extension for flow control<u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">Right=
 now, some of these appear to be entirely gratuitous.=C2=A0 I&#39;d like to=
 get to the bottom of each before we continue.<u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">At a =
minimum, the PR we land first should include just the core changes.<u></u><=
u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">As yo=
u say, reviewing a monster PR like this will only make GitHub weep unicorns=
, but we might be able to cut this into smaller pieces.<u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">On We=
d, May 23, 2018 at 11:31 AM Ian Swett &lt;ianswett=3D <a href=3D"mailto:40g=
oogle.com@dmarc.ietf.org" target=3D"_blank">
<span style=3D"color:windowtext;text-decoration:none">40google.com@dmarc.ie=
tf.org</span></a>&gt; wrote:<u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">&gt; =
Dear QUIC WG,<u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">&gt; =
On behalf of the Stream 0 Design Team, I am pleased to report that we<u></u=
><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">have =
consensus on a proposed approach to share with the WG. The DT&#39;s proposa=
l will make QUIC and TLS work closer together and incorporates ideas from D=
TLS, but it does not use the DTLS protocol itself.<u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">&gt; =
The DT believes this solves the important open Stream 0 issues. The<u></u><=
u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">propo=
sal will be a bit more invasive in TLS, but we believe it is the right long=
-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and<u></u>=
<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">Mint)=
 are willing and able to do the work necessary.. A number of stacks are cur=
rently working on implementations of this new approach, which we hope to ha=
ve in time for the Interim meeting.<u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">&gt; =
A design document describing the overall approach can be found at:<u></u><u=
></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><a hr=
ef=3D"https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxdd=
T93j6SwHY8/edit" target=3D"_blank"><span style=3D"color:windowtext;text-dec=
oration:none">https://docs.google.com/docume<wbr>nt/d/1fRsJqPinJl8N3b-bflDR=
V6au<wbr>ojfJLkxddT93j6SwHY8/edit</span></a><u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">&gt; =
A PR making the changes to the QUIC documents can be found at:<u></u><u></u=
></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">&gt; =
<a href=3D"https://github.com/quicwg/base-drafts/pull/1377" target=3D"_blan=
k">
<span style=3D"color:windowtext;text-decoration:none">https://github.com/qu=
icwg/base<wbr>-drafts/pull/1377</span></a><u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">&gt; =
A few design details did not have clear consensus, but it was felt it<u></u=
><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">would=
 be better to discuss those in the wider WG than delay the design team.=C2=
=A0 A consistent choice was made in the PR and these issues are mentioned i=
n Appendix B of the design doc.<u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">&gt; =
As always, comments and questions welcome. That said, this is a big PR<u></=
u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">and w=
e recognize that some editorial work is going to be needed before merging. =
In the interest of letting people follow along, and to keep github from fal=
ling over, we ask people to keep discussion on the mailing list and refrain=
 from
 making PR comments.<u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">&gt; =
See you in Kista!<u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText">&gt; =
Ian and Eric<u></u><u></u></p>
<p class=3D"m_-7725196871598781590m_-1728187892838803882MsoPlainText"><u></=
u>=C2=A0<u></u></p>
</div></div></div>
</div>

</blockquote></div><br></div></div>

--000000000000e50fa2056ce81188--


From nobody Wed May 23 16:47:56 2018
Return-Path: <mnot@mnot.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21306127077 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:47:55 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=I0FqwY4y; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=D26Ev6cF
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 fUYLN7M3_zZe for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:47:50 -0700 (PDT)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ACF4D1273B1 for <quic@ietf.org>; Wed, 23 May 2018 16:47:50 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 2850221F1A; Wed, 23 May 2018 19:47:50 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Wed, 23 May 2018 19:47:50 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=4VTKw4WLQ6Pw3fI2MeqgvwNaNRq54 uGw/evx9JBnREg=; b=I0FqwY4ywyHO/Yitq5iAz0RxMb80qSeyBhy32NLSa2DWF RwnQ3yMsWX1bYC2plJp4lkCj4DZwXPnV0d/9zOQWfsdwnNpRLwPnV1kqAFcXu3pO ree30X2nnqugtZFgG5JjoCXvw80RB2KrEXWroaqiUVLcFCPAn75iua0B9qwwEqvq AymaSG0h52v8wseKqNdCJuxHUrANeochpR/hraWuzsahHTLP9msfDFgBbzNddf26 McPuv8Hdz+XpsmBscAfPXjP/rwNX2eYuMS/LuA0Et5x+NgzaxVryDwJKQQ5U5i54 UlyzrS2khEqoDoH99MKVXatVhgiEmpo2BXtv59F3w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=4VTKw4 WLQ6Pw3fI2MeqgvwNaNRq54uGw/evx9JBnREg=; b=D26Ev6cFMgn0N1NnIkalwv FHAl5uxL6J6KPV/qDnHKldXD12pkC4cNnvbdjSIzx9J84U67fGrEi+ahT1qeOtFZ CQ71cvu2cgDXVoknqa63zEF8yCkccNzRr5Q/Rf6dvPAE4SfZrMpbIsMmAUMdGC9H uQZHcJi9yMqo0Pvz3haoUqMtteH34tK5JJR9rSuMTyOeWGGtpEOnA7QfnCjbwc4n MgvMcK2ZL+aDUFW2O16Z9gWUl+viMFJUG5nAfk21mBmyqxMqq4EaR0tqtqQI6BvE smGhyrrX4qZYpVHYlHqKFz5PQh8UgdVfqCfljO7ztytxKnP6XXylVrZPmEY5Mzvg ==
X-ME-Proxy: <xmx:pf0FW9FvFzjO4aSKqaKl1d--WMLahQ3U36nQM_VsyhKOJ2P9Ju0pMQ>
X-ME-Proxy: <xmx:pf0FWySjfUL6GNKtamF9FZ7UD60j4FOM8FyaLgfkTlsWMMcGHd4IIQ>
X-ME-Proxy: <xmx:pf0FW6vsQd1C8rZBSS9BOU-ObWFqH7k8KH5oeYE31fe-Zl38X1HPeQ>
X-ME-Proxy: <xmx:pf0FW4C7H0Tle97HPZ8Dn4HsOgPrCrRu1nPhItot_IohMx5oDFF_2Q>
X-ME-Proxy: <xmx:pf0FW8158fp_iQkvilUxpsZGGfwOIpWF_NgIVz9L9M88z31eE58bBw>
X-ME-Proxy: <xmx:pv0FW0b2gNZWCoP4SrE4NW8BL2UFpw4a8OpY4rQcO_-L0AOaz2Jn8g>
X-ME-Sender: <xms:pf0FW0kDP2U4TKcyviNw_mhJ-4QBlKgNpakpjt7GZn2jOSqgyZ6dDA>
Received: from [192.168.1.25] (unknown [144.136.175.28]) by mail.messagingengine.com (Postfix) with ESMTPA id 6616CE4437; Wed, 23 May 2018 19:47:48 -0400 (EDT)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Subject: Re: QPACK and the Static Table
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <SN1PR08MB1854395A2875541C4DC0673DDA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
Date: Thu, 24 May 2018 09:47:45 +1000
Cc: HTTP Working Group <ietf-http-wg@w3.org>, "quic@ietf.org" <quic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DE78AF39-9DAE-498E-9800-660DA55CD378@mnot.net>
References: <SN1PR08MB1854395A2875541C4DC0673DDA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
To: Mike Bishop <mbishop@evequefou.be>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Cgi_uWaAIVM9t2SZ2Jk68f37Qi4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 23:47:55 -0000

Hey Mike,

My .02 (I also left some notes in the PR) -

The static table is most useful on request headers, so that's what we =
should be focusing on. If it were me, I'd drop all of the response =
header fields except the most common ones (say 10 or so), and focus on =
request headers.

In fact, I'd look at paring down the number of entries in total for =
*just* the initial requests on a connection -- putting too many things =
in the static table might influence how implementations emit other =
headers, and that's not the intent here.

The HTTP Archive is a bit problematic; not only is it focused on "big" =
sites (albeit a lot of them), but it's also AIUI pretty homogenous on =
the client side, so it's not going to be very representative for request =
headers.

I think it would be better to get a sample of request headers seen by a =
couple of sites, a CDN or two, and at least one "HTTP API" type =
deployment, and see where that leads -- if we can find someone willing =
to do the work.

Cheers,


> On 24 May 2018, at 9:16 am, Mike Bishop <mbishop@evequefou.be> wrote:
>=20
> Wanted to get a sense of the affected working groups on two issues in =
QPACK (header compression for HTTP/QUIC).
> =20
> Rather than indexing the tables together and having the static table =
at 1-61, QPACK uses a bit to indicate static vs. dynamic.  Since the =
field is seven bits long, the performance is comparable for the dynamic =
table (you can access 63 entries in one byte, 190 in two), but you can =
increase the size of the static table without hurting the dynamic table. =
 As a result, we=E2=80=99re building a fresh static tablebased on =
queries against HTTPArchive data.
> =20
> The key question that has come up in a couple venues:  What real-world =
headers do we want to artificially remove from what the data shows, and =
what headers not seen by HTTP Archive do we want to force in anyway?
> =20
> So far, we=E2=80=99ve:
> 	=E2=80=A2 forced in pseudo-headers because the Archive doesn=E2=80=
=99t capture them and they would otherwise be absent
> 		=E2=80=A2 :path, :authority, :method
> 	=E2=80=A2 deleted values presumed biased by the test =
configuration:
> 		=E2=80=A2 Server: (various vendors)
> 		=E2=80=A2 User-Agent
> 		=E2=80=A2 Accept-Language: en-us, en;q=3D0.9
> 		=E2=80=A2 Content-Length: 531
> 			=E2=80=A2 I still wonder exactly why that=E2=80=99=
s so common=E2=80=A6.
> 		=E2=80=A2 P3p: =
policyref=3D=E2=80=9Dhttps://www.googleadservices.com/...=E2=80=9D=E2=80=A6=
.
> 		=E2=80=A2 Origin: https://www.facebook.com
> 		=E2=80=A2 Alt-Svc for various versions of gQUIC
> 		=E2=80=A2 =E2=80=A6the list goes on
> 	=E2=80=A2 deleted headers prohibited by HTTP/QUIC and HTTP/2
> 		=E2=80=A2 Transfer-Encoding: chunked
> 	=E2=80=A2 Reordered to put headers you=E2=80=99re likely to =
name-reference at the front, especially if you=E2=80=99re unlikely to =
add them to the dynamic table
> =20
> The question is whether we should also backfill headers which HTTP =
Archive wouldn=E2=80=99t see, delete headers we wish people wouldn=E2=80=99=
t use, and/or insert the ones we hope they eventually will.  Some =
candidates:
> 	=E2=80=A2 Add Alt-Svc entry for HTTP/QUIC with QUIC v1
> 	=E2=80=A2 Add X-Forwarded-For
> 	=E2=80=A2 Don=E2=80=99t add X-Forwarded-For, but do add =
Forwarded
> 	=E2=80=A2 Remove Expires to incent the use of Cache-Control
> 	=E2=80=A2 Collapse the =E2=80=9CContent-Type: <thingey>=E2=80=9D =
and =E2=80=9CContent-Type: <thingey>; charset=3Dutf-8=E2=80=9D entries =
together
> 		=E2=80=A2 =E2=80=A6but which one to keep?
> 	=E2=80=A2 Add Content-Encoding and/or Accept-Encoding entries =
for zstd
> =20
> There=E2=80=99s an endless parade of bikesheds here.  As Martin has =
pointed out, this will never be perfect, so the goal is =E2=80=9Cgood =
enough and keep going.=E2=80=9D  Any strong feelings about any of these =
before we merge it?
> =20
> Also, there=E2=80=99s been some discussion of a mechanism for =
selecting one of several static tables at the start of a connection.  In =
that case, the spec would probably define three tables (client headers, =
server headers [for servers that don=E2=80=99t push], combined [for =
servers that push]) and enable future RFCs to define others for targeted =
scenarios (proxies, video playback, IoT, etc.).  How much does that =
interest folks?

--
Mark Nottingham   https://www.mnot.net/


From nobody Wed May 23 16:50:59 2018
Return-Path: <mbishop@evequefou.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1FB2F1273B1 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:50:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 uM29kv2Si19g for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:50:55 -0700 (PDT)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-co1nam03on0091.outbound.protection.outlook.com [104.47.40.91]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A8974127077 for <quic@ietf.org>; Wed, 23 May 2018 16:50:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=RdXpICy2+TvIOHj0Q4QoPXeD1Aa2cEzlhGatkNqFEcA=; b=hwqheSuCDGM8fgrhtfBrk+KNnu7HraoJJpT6Yfdgk6Z59mq8tkh4qJ+U+HwoNZXxFovXO4lrUsBO1TBAj9RPYF27EEw+VjO4YDCj/1DyMBFlw9s63ic9pxf95amM7HVoinuH9nkE8Ue7CcOkVhUPwER3vrCFYhnftoRwKFhE+ZE=
Received: from SN1PR08MB1854.namprd08.prod.outlook.com (10.169.39.8) by SN1PR08MB1901.namprd08.prod.outlook.com (10.169.39.19) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.776.11; Wed, 23 May 2018 23:50:52 +0000
Received: from SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d]) by SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d%13]) with mapi id 15.20.0776.015; Wed, 23 May 2018 23:50:52 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Mark Nottingham <mnot@mnot.net>
CC: HTTP Working Group <ietf-http-wg@w3.org>, "quic@ietf.org" <quic@ietf.org>
Subject: RE: QPACK and the Static Table
Thread-Topic: QPACK and the Static Table
Thread-Index: AdPy6/ObcVQE/1QBQB2X+UF0YtinwQABH7WAAAAGeIA=
Date: Wed, 23 May 2018 23:50:51 +0000
Message-ID: <SN1PR08MB185461200872CE4122BC4F20DA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <SN1PR08MB1854395A2875541C4DC0673DDA6B0@SN1PR08MB1854.namprd08.prod.outlook.com> <DE78AF39-9DAE-498E-9800-660DA55CD378@mnot.net>
In-Reply-To: <DE78AF39-9DAE-498E-9800-660DA55CD378@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [2601:600:8080:5a28:4940:a32d:2658:89dc]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN1PR08MB1901; 7:EuqdaOtHu831YPcrOHP9GoXNFE5nDtOCK2F5/OsUxnjFLGa56UQGSxjMwUfvz5cyrRCgRO81YXTiLbscjflUKE4hQlh90TZop8NexUTVSE2UzDePot+c6nvxboVtM9f9PKtaCzwAdk10YX4ZYPElI/Z0jmIyl4DGM4zMxQZLgkR5E/mFhw028+/nx1zla2FAn1ef85p8bzmUHxT8PVrWvpdHMpH02tbhR6qemoO4srQ+zWeW82zcahumns/CmmxJ
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(5600026)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(2017052603328)(7153060)(7193020); SRVR:SN1PR08MB1901; 
x-ms-traffictypediagnostic: SN1PR08MB1901:
x-microsoft-antispam-prvs: <SN1PR08MB19015633EAEECE25563245FADA6B0@SN1PR08MB1901.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(86561027422486)(64217206974132); 
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(10201501046)(3002001)(93006095)(93001095)(3231254)(944501410)(52105095)(149027)(150027)(6041310)(20161123558120)(20161123562045)(20161123564045)(20161123560045)(2016111802025)(6072148)(6043046)(201708071742011)(7699016); SRVR:SN1PR08MB1901; BCL:0; PCL:0; RULEID:; SRVR:SN1PR08MB1901; 
x-forefront-prvs: 06818431B9
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39830400003)(366004)(396003)(39380400002)(346002)(376002)(13464003)(199004)(189003)(305945005)(97736004)(4326008)(5250100002)(102836004)(8936002)(86362001)(74316002)(105586002)(476003)(6916009)(8676002)(2906002)(486006)(81166006)(11346002)(6506007)(186003)(81156014)(55016002)(59450400001)(68736007)(53546011)(446003)(14454004)(106356001)(5660300001)(6246003)(3660700001)(99286004)(6116002)(966005)(54906003)(229853002)(25786009)(46003)(74482002)(7736002)(9686003)(478600001)(53936002)(6306002)(3280700002)(7696005)(2900100001)(6436002)(316002)(76176011)(33656002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR08MB1901; H:SN1PR08MB1854.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: ug3EU3MufERfG8Smg62wvopUmAFdtdU/s3Xk0762lupxRTRuXkDDiOYPOdbjk9G3KTZEPS4BDI2uEKilwTnYRM2VXhNrOdCBlMdww5KC8zzgyTk1S+te7zSerG7I1o1fotz7AM7aOHJwk1R5wQvcHoQg6+kefC9vi3B82G1SQcs2adgh/XKYPICUrBVOfsBK
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 29656c8f-79eb-4dfe-c3ac-08d5c1080482
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 29656c8f-79eb-4dfe-c3ac-08d5c1080482
X-MS-Exchange-CrossTenant-originalarrivaltime: 23 May 2018 23:50:52.0495 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR08MB1901
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/9BndRobITOUi_TUOCxXFnA8xo_Q>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 23:50:58 -0000

V2hpbGUgSSd2ZSB0cmllZCB0byBsaW1pdCB0aGUgYmlhcyBpbnRyb2R1Y2VkIGJ5IHRoZWlyIHNp
bmdsZSBicm93c2VyIGFuZCBzZWxlY3Rpb24gb2Ygc2l0ZXMsIEkgc2hhcmUgdGhvc2UgY29uY2Vy
bnMgYWJvdXQgdXNpbmcgdGhlIEhUVFAgQXJjaGl2ZSBhcyBhIHNpbmdsZSBzb3VyY2Ugb2YgZGF0
YS4gIEhvd2V2ZXIsIHdoYXQgSSd2ZSBoZWFyZCBmcm9tIG9uZSBIVFRQIEFQSSBkZXBsb3ltZW50
IGFuZCBzdXNwZWN0IGlzIHRydWUgYWNyb3NzIENETnMgaXMgdGhhdCBzaGFyaW5nIHJlcXVlc3Qg
aGVhZGVyIHZhbHVlcyBpcyBwcm9ibGVtYXRpYy4NCg0KTWF5YmUgaWYgd2UgbG9jYWxseSBhcHBs
aWVkIHRoZSBmaWx0ZXJpbmcgb2Ygbm90IHNoYXJpbmcgdmFsdWVzIHVubGVzcyBhIHNpbmdsZSB2
YWx1ZSByZXByZXNlbnRzIG1vcmUgdGhhbiA1JSBvZiBoZWFkZXIgb2NjdXJyZW5jZXMsIHRoYXQg
d291bGQgYmUgc3VmZmljaWVudGx5IGFub255bWl6ZWQgZm9yIGZvbGtzIHRvIGJlIHdpbGxpbmcg
dG8gc2hhcmUuDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBNYXJrIE5vdHRp
bmdoYW0gPG1ub3RAbW5vdC5uZXQ+IA0KU2VudDogV2VkbmVzZGF5LCBNYXkgMjMsIDIwMTggNDo0
OCBQTQ0KVG86IE1pa2UgQmlzaG9wIDxtYmlzaG9wQGV2ZXF1ZWZvdS5iZT4NCkNjOiBIVFRQIFdv
cmtpbmcgR3JvdXAgPGlldGYtaHR0cC13Z0B3My5vcmc+OyBxdWljQGlldGYub3JnDQpTdWJqZWN0
OiBSZTogUVBBQ0sgYW5kIHRoZSBTdGF0aWMgVGFibGUNCg0KSGV5IE1pa2UsDQoNCk15IC4wMiAo
SSBhbHNvIGxlZnQgc29tZSBub3RlcyBpbiB0aGUgUFIpIC0NCg0KVGhlIHN0YXRpYyB0YWJsZSBp
cyBtb3N0IHVzZWZ1bCBvbiByZXF1ZXN0IGhlYWRlcnMsIHNvIHRoYXQncyB3aGF0IHdlIHNob3Vs
ZCBiZSBmb2N1c2luZyBvbi4gSWYgaXQgd2VyZSBtZSwgSSdkIGRyb3AgYWxsIG9mIHRoZSByZXNw
b25zZSBoZWFkZXIgZmllbGRzIGV4Y2VwdCB0aGUgbW9zdCBjb21tb24gb25lcyAoc2F5IDEwIG9y
IHNvKSwgYW5kIGZvY3VzIG9uIHJlcXVlc3QgaGVhZGVycy4NCg0KSW4gZmFjdCwgSSdkIGxvb2sg
YXQgcGFyaW5nIGRvd24gdGhlIG51bWJlciBvZiBlbnRyaWVzIGluIHRvdGFsIGZvciAqanVzdCog
dGhlIGluaXRpYWwgcmVxdWVzdHMgb24gYSBjb25uZWN0aW9uIC0tIHB1dHRpbmcgdG9vIG1hbnkg
dGhpbmdzIGluIHRoZSBzdGF0aWMgdGFibGUgbWlnaHQgaW5mbHVlbmNlIGhvdyBpbXBsZW1lbnRh
dGlvbnMgZW1pdCBvdGhlciBoZWFkZXJzLCBhbmQgdGhhdCdzIG5vdCB0aGUgaW50ZW50IGhlcmUu
DQoNClRoZSBIVFRQIEFyY2hpdmUgaXMgYSBiaXQgcHJvYmxlbWF0aWM7IG5vdCBvbmx5IGlzIGl0
IGZvY3VzZWQgb24gImJpZyIgc2l0ZXMgKGFsYmVpdCBhIGxvdCBvZiB0aGVtKSwgYnV0IGl0J3Mg
YWxzbyBBSVVJIHByZXR0eSBob21vZ2Vub3VzIG9uIHRoZSBjbGllbnQgc2lkZSwgc28gaXQncyBu
b3QgZ29pbmcgdG8gYmUgdmVyeSByZXByZXNlbnRhdGl2ZSBmb3IgcmVxdWVzdCBoZWFkZXJzLg0K
DQpJIHRoaW5rIGl0IHdvdWxkIGJlIGJldHRlciB0byBnZXQgYSBzYW1wbGUgb2YgcmVxdWVzdCBo
ZWFkZXJzIHNlZW4gYnkgYSBjb3VwbGUgb2Ygc2l0ZXMsIGEgQ0ROIG9yIHR3bywgYW5kIGF0IGxl
YXN0IG9uZSAiSFRUUCBBUEkiIHR5cGUgZGVwbG95bWVudCwgYW5kIHNlZSB3aGVyZSB0aGF0IGxl
YWRzIC0tIGlmIHdlIGNhbiBmaW5kIHNvbWVvbmUgd2lsbGluZyB0byBkbyB0aGUgd29yay4NCg0K
Q2hlZXJzLA0KDQoNCj4gT24gMjQgTWF5IDIwMTgsIGF0IDk6MTYgYW0sIE1pa2UgQmlzaG9wIDxt
YmlzaG9wQGV2ZXF1ZWZvdS5iZT4gd3JvdGU6DQo+IA0KPiBXYW50ZWQgdG8gZ2V0IGEgc2Vuc2Ug
b2YgdGhlIGFmZmVjdGVkIHdvcmtpbmcgZ3JvdXBzIG9uIHR3byBpc3N1ZXMgaW4gUVBBQ0sgKGhl
YWRlciBjb21wcmVzc2lvbiBmb3IgSFRUUC9RVUlDKS4NCj4gIA0KPiBSYXRoZXIgdGhhbiBpbmRl
eGluZyB0aGUgdGFibGVzIHRvZ2V0aGVyIGFuZCBoYXZpbmcgdGhlIHN0YXRpYyB0YWJsZSBhdCAx
LTYxLCBRUEFDSyB1c2VzIGEgYml0IHRvIGluZGljYXRlIHN0YXRpYyB2cy4gZHluYW1pYy4gIFNp
bmNlIHRoZSBmaWVsZCBpcyBzZXZlbiBiaXRzIGxvbmcsIHRoZSBwZXJmb3JtYW5jZSBpcyBjb21w
YXJhYmxlIGZvciB0aGUgZHluYW1pYyB0YWJsZSAoeW91IGNhbiBhY2Nlc3MgNjMgZW50cmllcyBp
biBvbmUgYnl0ZSwgMTkwIGluIHR3byksIGJ1dCB5b3UgY2FuIGluY3JlYXNlIHRoZSBzaXplIG9m
IHRoZSBzdGF0aWMgdGFibGUgd2l0aG91dCBodXJ0aW5nIHRoZSBkeW5hbWljIHRhYmxlLiAgQXMg
YSByZXN1bHQsIHdl4oCZcmUgYnVpbGRpbmcgYSBmcmVzaCBzdGF0aWMgdGFibGViYXNlZCBvbiBx
dWVyaWVzIGFnYWluc3QgSFRUUEFyY2hpdmUgZGF0YS4NCj4gIA0KPiBUaGUga2V5IHF1ZXN0aW9u
IHRoYXQgaGFzIGNvbWUgdXAgaW4gYSBjb3VwbGUgdmVudWVzOiAgV2hhdCByZWFsLXdvcmxkIGhl
YWRlcnMgZG8gd2Ugd2FudCB0byBhcnRpZmljaWFsbHkgcmVtb3ZlIGZyb20gd2hhdCB0aGUgZGF0
YSBzaG93cywgYW5kIHdoYXQgaGVhZGVycyBub3Qgc2VlbiBieSBIVFRQIEFyY2hpdmUgZG8gd2Ug
d2FudCB0byBmb3JjZSBpbiBhbnl3YXk/DQo+ICANCj4gU28gZmFyLCB3ZeKAmXZlOg0KPiAJ4oCi
IGZvcmNlZCBpbiBwc2V1ZG8taGVhZGVycyBiZWNhdXNlIHRoZSBBcmNoaXZlIGRvZXNu4oCZdCBj
YXB0dXJlIHRoZW0gYW5kIHRoZXkgd291bGQgb3RoZXJ3aXNlIGJlIGFic2VudA0KPiAJCeKAoiA6
cGF0aCwgOmF1dGhvcml0eSwgOm1ldGhvZA0KPiAJ4oCiIGRlbGV0ZWQgdmFsdWVzIHByZXN1bWVk
IGJpYXNlZCBieSB0aGUgdGVzdCBjb25maWd1cmF0aW9uOg0KPiAJCeKAoiBTZXJ2ZXI6ICh2YXJp
b3VzIHZlbmRvcnMpDQo+IAkJ4oCiIFVzZXItQWdlbnQNCj4gCQnigKIgQWNjZXB0LUxhbmd1YWdl
OiBlbi11cywgZW47cT0wLjkNCj4gCQnigKIgQ29udGVudC1MZW5ndGg6IDUzMQ0KPiAJCQnigKIg
SSBzdGlsbCB3b25kZXIgZXhhY3RseSB3aHkgdGhhdOKAmXMgc28gY29tbW9u4oCmLg0KPiAJCeKA
oiBQM3A6IHBvbGljeXJlZj3igJ1odHRwczovL3d3dy5nb29nbGVhZHNlcnZpY2VzLmNvbS8uLi7i
gJ3igKYuDQo+IAkJ4oCiIE9yaWdpbjogaHR0cHM6Ly93d3cuZmFjZWJvb2suY29tDQo+IAkJ4oCi
IEFsdC1TdmMgZm9yIHZhcmlvdXMgdmVyc2lvbnMgb2YgZ1FVSUMNCj4gCQnigKIg4oCmdGhlIGxp
c3QgZ29lcyBvbg0KPiAJ4oCiIGRlbGV0ZWQgaGVhZGVycyBwcm9oaWJpdGVkIGJ5IEhUVFAvUVVJ
QyBhbmQgSFRUUC8yDQo+IAkJ4oCiIFRyYW5zZmVyLUVuY29kaW5nOiBjaHVua2VkDQo+IAnigKIg
UmVvcmRlcmVkIHRvIHB1dCBoZWFkZXJzIHlvdeKAmXJlIGxpa2VseSB0byBuYW1lLXJlZmVyZW5j
ZSBhdCB0aGUgZnJvbnQsIGVzcGVjaWFsbHkgaWYgeW914oCZcmUgdW5saWtlbHkgdG8gYWRkIHRo
ZW0gdG8gdGhlIGR5bmFtaWMgdGFibGUNCj4gIA0KPiBUaGUgcXVlc3Rpb24gaXMgd2hldGhlciB3
ZSBzaG91bGQgYWxzbyBiYWNrZmlsbCBoZWFkZXJzIHdoaWNoIEhUVFAgQXJjaGl2ZSB3b3VsZG7i
gJl0IHNlZSwgZGVsZXRlIGhlYWRlcnMgd2Ugd2lzaCBwZW9wbGUgd291bGRu4oCZdCB1c2UsIGFu
ZC9vciBpbnNlcnQgdGhlIG9uZXMgd2UgaG9wZSB0aGV5IGV2ZW50dWFsbHkgd2lsbC4gIFNvbWUg
Y2FuZGlkYXRlczoNCj4gCeKAoiBBZGQgQWx0LVN2YyBlbnRyeSBmb3IgSFRUUC9RVUlDIHdpdGgg
UVVJQyB2MQ0KPiAJ4oCiIEFkZCBYLUZvcndhcmRlZC1Gb3INCj4gCeKAoiBEb27igJl0IGFkZCBY
LUZvcndhcmRlZC1Gb3IsIGJ1dCBkbyBhZGQgRm9yd2FyZGVkDQo+IAnigKIgUmVtb3ZlIEV4cGly
ZXMgdG8gaW5jZW50IHRoZSB1c2Ugb2YgQ2FjaGUtQ29udHJvbA0KPiAJ4oCiIENvbGxhcHNlIHRo
ZSDigJxDb250ZW50LVR5cGU6IDx0aGluZ2V5PuKAnSBhbmQg4oCcQ29udGVudC1UeXBlOiA8dGhp
bmdleT47IGNoYXJzZXQ9dXRmLTjigJ0gZW50cmllcyB0b2dldGhlcg0KPiAJCeKAoiDigKZidXQg
d2hpY2ggb25lIHRvIGtlZXA/DQo+IAnigKIgQWRkIENvbnRlbnQtRW5jb2RpbmcgYW5kL29yIEFj
Y2VwdC1FbmNvZGluZyBlbnRyaWVzIGZvciB6c3RkDQo+ICANCj4gVGhlcmXigJlzIGFuIGVuZGxl
c3MgcGFyYWRlIG9mIGJpa2VzaGVkcyBoZXJlLiAgQXMgTWFydGluIGhhcyBwb2ludGVkIG91dCwg
dGhpcyB3aWxsIG5ldmVyIGJlIHBlcmZlY3QsIHNvIHRoZSBnb2FsIGlzIOKAnGdvb2QgZW5vdWdo
IGFuZCBrZWVwIGdvaW5nLuKAnSAgQW55IHN0cm9uZyBmZWVsaW5ncyBhYm91dCBhbnkgb2YgdGhl
c2UgYmVmb3JlIHdlIG1lcmdlIGl0Pw0KPiAgDQo+IEFsc28sIHRoZXJl4oCZcyBiZWVuIHNvbWUg
ZGlzY3Vzc2lvbiBvZiBhIG1lY2hhbmlzbSBmb3Igc2VsZWN0aW5nIG9uZSBvZiBzZXZlcmFsIHN0
YXRpYyB0YWJsZXMgYXQgdGhlIHN0YXJ0IG9mIGEgY29ubmVjdGlvbi4gIEluIHRoYXQgY2FzZSwg
dGhlIHNwZWMgd291bGQgcHJvYmFibHkgZGVmaW5lIHRocmVlIHRhYmxlcyAoY2xpZW50IGhlYWRl
cnMsIHNlcnZlciBoZWFkZXJzIFtmb3Igc2VydmVycyB0aGF0IGRvbuKAmXQgcHVzaF0sIGNvbWJp
bmVkIFtmb3Igc2VydmVycyB0aGF0IHB1c2hdKSBhbmQgZW5hYmxlIGZ1dHVyZSBSRkNzIHRvIGRl
ZmluZSBvdGhlcnMgZm9yIHRhcmdldGVkIHNjZW5hcmlvcyAocHJveGllcywgdmlkZW8gcGxheWJh
Y2ssIElvVCwgZXRjLikuICBIb3cgbXVjaCBkb2VzIHRoYXQgaW50ZXJlc3QgZm9sa3M/DQoNCi0t
DQpNYXJrIE5vdHRpbmdoYW0gICBodHRwczovL3d3dy5tbm90Lm5ldC8NCg0K


From nobody Wed May 23 16:51:33 2018
Return-Path: <martin.thomson@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E9F5912D7F1 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:51:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 uVxZeHxDvSOG for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:51:29 -0700 (PDT)
Received: from mail-ot0-x22c.google.com (mail-ot0-x22c.google.com [IPv6:2607:f8b0:4003:c0f::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4D7D7127077 for <quic@ietf.org>; Wed, 23 May 2018 16:51:29 -0700 (PDT)
Received: by mail-ot0-x22c.google.com with SMTP id l13-v6so27294492otk.9 for <quic@ietf.org>; Wed, 23 May 2018 16:51:29 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=b3rG876BoZ3/h62mIR98Brr1zwR/yxNdd46I5Gu0d10=; b=ilVMZYgz4zmThhAsaSaepDGuElm2N+gF+evaFzDFTmfRRiH/WS6CwOoRT5NeJq0AHP Qp/e8bx41ZInoT3oF+PPmaPhOEa0ekZJPeFiTFlmDf2JiyCEdQBsInPpQAl1h+9Lz39N rwjUDtRJECKDZGMNYD6yEQjS6ZZLbOqMTxkIVQ692X1qoYqvo/XVRgvE3/+ZDxfGxgc+ MoBBWWcs4V4WUOlz1oUpWmSWccOHt2PbEFT2cgVtc98VIsdSwDNNTyepHt+YBAqofGnd 6w/42Hk+Vut83Uwn8zJ5QTIzD+i2Heyo+cQt5Kz0V8z6ej/W+/HrGOoEzHMK79cLc8QS kUAQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=b3rG876BoZ3/h62mIR98Brr1zwR/yxNdd46I5Gu0d10=; b=aVAZ73WAu/JgveVRwa04xKw8w89KVSJsAYVYIN/Ilf1MQfJG7fvZqz7J3EUybsDMYH Ap0qco6faxbNMRKGS3Y0HumY7eX5rfOmio6Lu2Wt0VJtBQEMbVNkOg6YkesFmPCZ4HN/ oJCJEqq6HgKnSrkp8rgnZdPs3EV3hO5/sBw6BnkBOUFPSYnysQSoJB+kGEAMPPT3/faI qjXxz/jxNV8eH75IO+QOhS9UdIcqtbr8boVm7SyFkkd09WCygHyeQnx8aFGiryOj4qYS +T9ni3lyGQFQKKyJmu0ee9QSL+exb/+d7nbZkq4Acjknv59U7lf2if3MnTWLe5bylYja bEIw==
X-Gm-Message-State: ALKqPweurHnPwSd8HCpFe8tJvRtBWY0J+dJIJrcul8vM8Mlnczrv/Xgz F0hcoQJCzVn9rn7hxMm87+SRj9U2i6JT8PGe4TU=
X-Google-Smtp-Source: AB8JxZr3zNg3buAx1QEIaTOv4afOdek4YXTB1DZqQJjOXgTgr0MaNyovFzpp5P+DFW9P0BxyMyxayo+9FqyxhM0wARI=
X-Received: by 2002:a9d:524d:: with SMTP id q13-v6mr3313848otg.241.1527119488429;  Wed, 23 May 2018 16:51:28 -0700 (PDT)
MIME-Version: 1.0
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CANatvzzS+T4HcddCemKF7bb1BmACFp=R4n+YMWkq7tnZaUXw4w@mail.gmail.com> <CACpbDcddWz_i5GoNWYfDAdWKcX0_gOMiKk=ORVABGPE8+7c8Vw@mail.gmail.com>
In-Reply-To: <CACpbDcddWz_i5GoNWYfDAdWKcX0_gOMiKk=ORVABGPE8+7c8Vw@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 24 May 2018 09:51:16 +1000
Message-ID: <CABkgnnUfEtkXBYrzZFm9mJ5o_nG_vLVgbgxDG5TxUhLYoe55Xg@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: Jana Iyengar <jri.ietf@gmail.com>
Cc: Kazuho Oku <kazuhooku@gmail.com>, ekr@mozilla.com, QUIC WG <quic@ietf.org>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/414bfpkYD0skCKo5_93vEdh2LLg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 23:51:32 -0000

I'm not a fan of micro-optimizations like this, especially when it means
taking space we don't need.

We don't need ANY of the bits on the CRYPTO stream.  The savings for an
absent length and offset are marginal and not worth burning 8 frame types
on, and the stream never really ends.  So if we made it have a type of
0x18, then you would run it through the same code and get the same result.

On Wed, May 23, 2018 at 4:40 PM Jana Iyengar <jri.ietf@gmail.com> wrote:

> Thank you for your implementation and your report -- this is terrific and
helpful!

> On your note about CRYPTO_HS frames, I think your idea is clever. Just to
ensure that I am understanding it correctly, I believe you're proposing
defining:
> 0x10 - 0x17: STREAM frame
> 0x18 - 0x1F: CRYPTO_HS frame

> We can the same frame format for CRYPTO_HS as STREAM except that
CRYPTO_HS will not have the stream ID field. This means an implementation
handling these frames can reuse the stream machinery with a small change to
parse the header bits as follows:

> if (type & 0x10)  {  // STREAM or CRYPTO_HS frame
>      if (type & 0x08) streamID = varint_consume(frame);
>      if (type & 0x04) offset = varint_consume(frame);
>      if (type & 0x02) length = varint_consume(frame);
>      if (type & 0x01) fin = 1;
>      read body if present
> }

> On Tue, May 22, 2018 at 9:57 PM, Kazuho Oku <kazuhooku@gmail.com> wrote:

>> FWIW, I am happy to tell you that I have a working PoC code for the
>> proposed approach.

>> On the QUIC side, I saw 2% (124 lines) increase in code size (more on
>> that below). On the TLS side, I also saw 2% (175 lines) increase.
>> However please look at the code size change especially on the QUIC
>> side with grain of salt, as it is just a PoC.

>> As expected, the key and encryption-level management on the QUIC side
>> became very clean. Following are some of the design decisions I made
>> as well as the outcomes:

>> * All the interaction between picotls and quicly are accompanied by
>> "epoch". Handshake messages are attributed with their epochs so that
>> they do not get protected by the wrong key, or so that octets received
>> under an incorrect encryption context cannot be misused.

>> * All the traffic keys are governed by quicly (managing some traffic
>> keys in TLS while managing PNE key in QUIC seems messy).

>> * The Initial key is setup by quicly, wheeras other traffic keys are
>> installed by picotls by calling a callback named
>> update_traffic_key_cb. The callback accepts and installs 6 keys in
>> total: for three levels (i.e. 0-RTT, handshake, 1-RTT) in two
>> directions (send-side and receive-side).

>> * Three PN spaces have their own AEAD encryption key. Initial PN and
>> Handshake PN spaces have one aead decryption key each. Application PN
>> space has up to two decryption keys: either for 0-RTT and 1-RTT or for
>> two 1-RTT keys during key update.

>> It was a pain to have a dedicated frame encoding for CRYPTO_HS, even
>> though we can reuse (and I reused) the retransmission and reassembly
>> logic of QUIC streams for the handshake flows. About a half of the
>> code size increase comes from that (the other half comes from the
>> added abstraction for having two contexts for the handshake). I would
>> prefer reusing the STREAM frame encoding for the handshake data. We
>> could possibly use a different base offset (i.e. for CRYPTO_HS frames
>> we could use 0b00011XXX, whereas the STREAM frames use 0b00010XXX), as
>> well as omitting the Stream ID field.

>> Overall, now that I have a PoC, I am more confident that the proposed
>> approach is the correct path forward. It *simplifies* the QUIC stack
>> at the same time giving us better security properties as well as
>> fixing various issues in the current design (as discussed in the
>> design doc).


>> 2018-05-23 10:30 GMT+09:00 Ian Swett <ianswett=
40google.com@dmarc.ietf.org>:
>> > Dear QUIC WG,
>> >
>> >
>> > On behalf of the Stream 0 Design Team, I am pleased to report that we
have
>> > consensus on a proposed approach to share with the WG. The DT's
proposal
>> > will make QUIC and TLS work closer together and incorporates ideas from
>> > DTLS, but it does not use the DTLS protocol itself.
>> >
>> >
>> > The DT believes this solves the important open Stream 0 issues. The
proposal
>> > will be a bit more invasive in TLS, but we believe it is the right
long-term
>> > direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and Mint)
are
>> > willing and able to do the work necessary.. A number of stacks are
currently
>> > working on implementations of this new approach, which we hope to have
in
>> > time for the Interim meeting.
>> >
>> >
>> > A design document describing the overall approach can be found at:
>> >
>> >
https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit
>> >
>> >
>> > A PR making the changes to the QUIC documents can be found at:
>> >
>> > https://github.com/quicwg/base-drafts/pull/1377
>> >
>> >
>> > A few design details did not have clear consensus, but it was felt it
would
>> > be better to discuss those in the wider WG than delay the design team.
  A
>> > consistent choice was made in the PR and these issues are mentioned in
>> > Appendix B of the design doc.
>> >
>> >
>> > As always, comments and questions welcome. That said, this is a big PR
and
>> > we recognize that some editorial work is going to be needed before
merging.
>> > In the interest of letting people follow along, and to keep github from
>> > falling over, we ask people to keep discussion on the mailing list and
>> > refrain from making PR comments.
>> >
>> >
>> > See you in Kista!
>> >
>> >
>> > Ian and Eric



>> --
>> Kazuho Oku


From nobody Wed May 23 16:52:50 2018
Return-Path: <pmcmanus@mozilla.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C546E127077 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:52:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.234
X-Spam-Level: 
X-Spam-Status: No, score=-1.234 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_SOFTFAIL=0.665] autolearn=no autolearn_force=no
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 qHXSYozhkgCJ for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:52:46 -0700 (PDT)
Received: from linode64.ducksong.com (www.ducksong.com [192.155.95.102]) by ietfa.amsl.com (Postfix) with ESMTP id DFB61124217 for <quic@ietf.org>; Wed, 23 May 2018 16:52:45 -0700 (PDT)
Received: from mail-oi0-f49.google.com (mail-oi0-f49.google.com [209.85.218.49]) by linode64.ducksong.com (Postfix) with ESMTPSA id 771EB3A068 for <quic@ietf.org>; Wed, 23 May 2018 19:52:44 -0400 (EDT)
Received: by mail-oi0-f49.google.com with SMTP id e80-v6so21118750oig.11 for <quic@ietf.org>; Wed, 23 May 2018 16:52:44 -0700 (PDT)
X-Gm-Message-State: ALKqPwf8LR9kYH20lHnYUE6yEwNfpitr9hSngFGvS958nu47f464DWmM cvBKDp4gSgN5gcQ5b0yLXvEy8YDu8RFibje8LKg=
X-Google-Smtp-Source: AB8JxZqBpUZDNo9kyApYS00crUKIkAi+7I2hsB7GPPrGgFnb3/blQkiJxIVIoaQb8CECbg4tESwZB2EdBnwEmF0NdGU=
X-Received: by 2002:aca:eb0b:: with SMTP id j11-v6mr2569439oih.347.1527119564194;  Wed, 23 May 2018 16:52:44 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:8a24:0:0:0:0:0 with HTTP; Wed, 23 May 2018 16:52:43 -0700 (PDT)
In-Reply-To: <SN1PR08MB1854395A2875541C4DC0673DDA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <SN1PR08MB1854395A2875541C4DC0673DDA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Wed, 23 May 2018 19:52:43 -0400
X-Gmail-Original-Message-ID: <CAOdDvNqsNmU5qahRk_p34gxvEFsZJS0f=xiLixGLSLuZM7pBwQ@mail.gmail.com>
Message-ID: <CAOdDvNqsNmU5qahRk_p34gxvEFsZJS0f=xiLixGLSLuZM7pBwQ@mail.gmail.com>
Subject: Re: QPACK and the Static Table
To: Mike Bishop <mbishop@evequefou.be>
Cc: HTTP Working Group <ietf-http-wg@w3.org>, "quic@ietf.org" <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000274be4056ce83b32"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/nP3xtjHv6hhOxM8WqO66WoUnndg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 23:52:48 -0000

--000000000000274be4056ce83b32
Content-Type: text/plain; charset="UTF-8"

limiting feedback to just strong opinions on your suggestions:

On Wed, May 23, 2018 at 7:16 PM, Mike Bishop <mbishop@evequefou.be> wrote:

>
>    - Add Alt-Svc entry for HTTP/QUIC with QUIC v1
>
> this is clever and a good idea.


>
>    - Remove Expires to incent the use of Cache-Control
>
> tempting, but I think you're better off reflecting reality here.

>
>
>    - Add Content-Encoding and/or Accept-Encoding entries for zstd
>
> seems premature. When it was presented at ietf 100 Murray was clear this
was a 'targetted use case' and wasn't seeking browser adoption.. there are
certainly non-browser use cases to consider, but giving dictionary space to
it seems.. well, premature.

--000000000000274be4056ce83b32
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">limiting feedback to just strong opinions on your suggesti=
ons:<br><div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On W=
ed, May 23, 2018 at 7:16 PM, Mike Bishop <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:mbishop@evequefou.be" target=3D"_blank">mbishop@evequefou.be</a>&gt;<=
/span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8=
ex;border-left:1px #ccc solid;padding-left:1ex">





<div link=3D"#0563C1" vlink=3D"#954F72" lang=3D"EN-US">
<div class=3D"m_1452110050838579947WordSection1">
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"m_1452110050838579947MsoListParagraph" style=3D"margin-left:0i=
n">Add Alt-Svc entry for HTTP/QUIC with QUIC v1<u></u><u></u></li></ul></di=
v></div></blockquote><div>this is clever and a good idea.<br></div><div></d=
iv><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div link=3D"#0563C1" vl=
ink=3D"#954F72" lang=3D"EN-US"><div class=3D"m_1452110050838579947WordSecti=
on1"><ul style=3D"margin-top:0in" type=3D"disc"><li class=3D"m_145211005083=
8579947MsoListParagraph" style=3D"margin-left:0in">Remove Expires to incent=
 the use of Cache-Control<u></u><u></u></li></ul></div></div></blockquote><=
div>tempting, but I think you&#39;re better off reflecting reality here.<br=
></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-=
left:1px #ccc solid;padding-left:1ex"><div link=3D"#0563C1" vlink=3D"#954F7=
2" lang=3D"EN-US"><div class=3D"m_1452110050838579947WordSection1"><br><ul =
style=3D"margin-top:0in" type=3D"disc"><li class=3D"m_1452110050838579947Ms=
oListParagraph" style=3D"margin-left:0in">Add Content-Encoding and/or Accep=
t-Encoding entries for zstd<u></u><u></u></li></ul>
<p class=3D"MsoNormal"><u></u></p></div></div></blockquote><div>seems prema=
ture. When it was presented at ietf 100 Murray was clear this was a &#39;ta=
rgetted use case&#39; and wasn&#39;t seeking browser adoption.. there are c=
ertainly non-browser use cases to consider, but giving dictionary space to =
it seems.. well, premature.<br></div><br></div></div></div></div>

--000000000000274be4056ce83b32--


From nobody Wed May 23 16:56:37 2018
Return-Path: <ekr@rtfm.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 21529128D2E for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:56:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 FiVEdDyIDt-J for <quic@ietfa.amsl.com>; Wed, 23 May 2018 16:56:32 -0700 (PDT)
Received: from mail-ot0-x230.google.com (mail-ot0-x230.google.com [IPv6:2607:f8b0:4003:c0f::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5E62B124217 for <quic@ietf.org>; Wed, 23 May 2018 16:56:32 -0700 (PDT)
Received: by mail-ot0-x230.google.com with SMTP id h8-v6so27335117otb.2 for <quic@ietf.org>; Wed, 23 May 2018 16:56:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=/CW7UjMtqiKBHudYlHq+vy/X5jagEA9Oey4gqFkw11w=; b=a8e9l0ldhXfyUgbz2FlbH1i1T4U1Se83ArtkRvCaIJQC0jbouZGYf3ASUCcydeNV8j ywRkwZ82EdKTU0tThzeLHMzrleeFNbN9wb4PrTAA4bb5LdCvrKcUPlik8wONji7NR9qV /YjYbvT0+x5uG8aJiYg34WwnpcdNejuoC9XrNblOtIJ/TQjGZJJ51D+3xhfFkxjaaLGD LxvbPmqGly1+g/LUP2cym0M2IBqa4o+vaaAeXcDEJQHrwMSrDNLsUVQlmBYlDS2gR1eq FDTtDQfTHf84E1yZ8+LoZHsgurJ2pvV15bNqQ013F/4UsrWTGPRbtHewUA8BfEUzAp4J 3aUw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=/CW7UjMtqiKBHudYlHq+vy/X5jagEA9Oey4gqFkw11w=; b=MS/4hLG2V1CT8m1uin1/A4xTGgePzsTrzvUzV/jpONUT46Xhh3A3v+17ZG6JXeFrcH lI0dsxUXKIQLvoXiQUNqfMLQzCEMusH7GFCOt5uUyLAEVG9BqmyxNUedEL6swwjoYo9q Qq+1lVdFCmkjDrkH74mASfS10k1rHEnL0+vSEHVjPq5KllCpmJ+p/7nM55zZqJkGvGpn DgpKLP24hpIM3Xr44wCFmexuedj1EZZnMKn5DEdocHvc/fEhU/Y0efnsFdkZuLFPuJcP 5x/83xeWEudT5SMRjPMYSiHGr85BrPyYweTrqqrsBn2BLXlEnPrJFVo9x7XL5jyFtT+C gIRA==
X-Gm-Message-State: ALKqPwfSWhNg37SZ+MQXPXKpeJHiswEjSi0Sf7IDv1KAV6/9UGKg6yCv PQfXAazispOL22eXWx3V8ttweIa3Bbxv+JfqdsutuA==
X-Google-Smtp-Source: AB8JxZokn2OxtVrFpVMYxewKwijeZheI77XEw2Haiwaxlf1lwns+xky/NU5L8htiatIQMB8rBB+y1+PAXDywyK1CX7E=
X-Received: by 2002:a9d:719a:: with SMTP id o26-v6mr3458844otj.44.1527119791664;  Wed, 23 May 2018 16:56:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:ac9:66:0:0:0:0:0 with HTTP; Wed, 23 May 2018 16:55:51 -0700 (PDT)
In-Reply-To: <CABkgnnUfEtkXBYrzZFm9mJ5o_nG_vLVgbgxDG5TxUhLYoe55Xg@mail.gmail.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CANatvzzS+T4HcddCemKF7bb1BmACFp=R4n+YMWkq7tnZaUXw4w@mail.gmail.com> <CACpbDcddWz_i5GoNWYfDAdWKcX0_gOMiKk=ORVABGPE8+7c8Vw@mail.gmail.com> <CABkgnnUfEtkXBYrzZFm9mJ5o_nG_vLVgbgxDG5TxUhLYoe55Xg@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 23 May 2018 16:55:51 -0700
Message-ID: <CABcZeBNYVmqnv_42mX=cQsdas-ZS8DS1v0dcLjdnBB0iZkoKfQ@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Jana Iyengar <jri.ietf@gmail.com>, Eric Rescorla <ekr@mozilla.com>, QUIC WG <quic@ietf.org>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Kazuho Oku <kazuhooku@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000b63f6f056ce848c3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/rqRj8Q324NuuRHSLXl5o0WjsOjg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 23 May 2018 23:56:36 -0000

--000000000000b63f6f056ce848c3
Content-Type: text/plain; charset="UTF-8"

I'm with MT on this one. Bits in the handshake are comparatively cheap. I
do think it's of *some* benefit to be able to use the STREAM frame parser,
but that 0x18 hack seems to get us that.

-Ekr


On Wed, May 23, 2018 at 4:51 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> I'm not a fan of micro-optimizations like this, especially when it means
> taking space we don't need.
>
> We don't need ANY of the bits on the CRYPTO stream.  The savings for an
> absent length and offset are marginal and not worth burning 8 frame types
> on, and the stream never really ends.  So if we made it have a type of
> 0x18, then you would run it through the same code and get the same result.
>
> On Wed, May 23, 2018 at 4:40 PM Jana Iyengar <jri.ietf@gmail.com> wrote:
>
> > Thank you for your implementation and your report -- this is terrific and
> helpful!
>
> > On your note about CRYPTO_HS frames, I think your idea is clever. Just to
> ensure that I am understanding it correctly, I believe you're proposing
> defining:
> > 0x10 - 0x17: STREAM frame
> > 0x18 - 0x1F: CRYPTO_HS frame
>
> > We can the same frame format for CRYPTO_HS as STREAM except that
> CRYPTO_HS will not have the stream ID field. This means an implementation
> handling these frames can reuse the stream machinery with a small change to
> parse the header bits as follows:
>
> > if (type & 0x10)  {  // STREAM or CRYPTO_HS frame
> >      if (type & 0x08) streamID = varint_consume(frame);
> >      if (type & 0x04) offset = varint_consume(frame);
> >      if (type & 0x02) length = varint_consume(frame);
> >      if (type & 0x01) fin = 1;
> >      read body if present
> > }
>
> > On Tue, May 22, 2018 at 9:57 PM, Kazuho Oku <kazuhooku@gmail.com> wrote:
>
> >> FWIW, I am happy to tell you that I have a working PoC code for the
> >> proposed approach.
>
> >> On the QUIC side, I saw 2% (124 lines) increase in code size (more on
> >> that below). On the TLS side, I also saw 2% (175 lines) increase.
> >> However please look at the code size change especially on the QUIC
> >> side with grain of salt, as it is just a PoC.
>
> >> As expected, the key and encryption-level management on the QUIC side
> >> became very clean. Following are some of the design decisions I made
> >> as well as the outcomes:
>
> >> * All the interaction between picotls and quicly are accompanied by
> >> "epoch". Handshake messages are attributed with their epochs so that
> >> they do not get protected by the wrong key, or so that octets received
> >> under an incorrect encryption context cannot be misused.
>
> >> * All the traffic keys are governed by quicly (managing some traffic
> >> keys in TLS while managing PNE key in QUIC seems messy).
>
> >> * The Initial key is setup by quicly, wheeras other traffic keys are
> >> installed by picotls by calling a callback named
> >> update_traffic_key_cb. The callback accepts and installs 6 keys in
> >> total: for three levels (i.e. 0-RTT, handshake, 1-RTT) in two
> >> directions (send-side and receive-side).
>
> >> * Three PN spaces have their own AEAD encryption key. Initial PN and
> >> Handshake PN spaces have one aead decryption key each. Application PN
> >> space has up to two decryption keys: either for 0-RTT and 1-RTT or for
> >> two 1-RTT keys during key update.
>
> >> It was a pain to have a dedicated frame encoding for CRYPTO_HS, even
> >> though we can reuse (and I reused) the retransmission and reassembly
> >> logic of QUIC streams for the handshake flows. About a half of the
> >> code size increase comes from that (the other half comes from the
> >> added abstraction for having two contexts for the handshake). I would
> >> prefer reusing the STREAM frame encoding for the handshake data. We
> >> could possibly use a different base offset (i.e. for CRYPTO_HS frames
> >> we could use 0b00011XXX, whereas the STREAM frames use 0b00010XXX), as
> >> well as omitting the Stream ID field.
>
> >> Overall, now that I have a PoC, I am more confident that the proposed
> >> approach is the correct path forward. It *simplifies* the QUIC stack
> >> at the same time giving us better security properties as well as
> >> fixing various issues in the current design (as discussed in the
> >> design doc).
>
>
> >> 2018-05-23 10:30 GMT+09:00 Ian Swett <ianswett=
> 40google.com@dmarc.ietf.org>:
> >> > Dear QUIC WG,
> >> >
> >> >
> >> > On behalf of the Stream 0 Design Team, I am pleased to report that we
> have
> >> > consensus on a proposed approach to share with the WG. The DT's
> proposal
> >> > will make QUIC and TLS work closer together and incorporates ideas
> from
> >> > DTLS, but it does not use the DTLS protocol itself.
> >> >
> >> >
> >> > The DT believes this solves the important open Stream 0 issues. The
> proposal
> >> > will be a bit more invasive in TLS, but we believe it is the right
> long-term
> >> > direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and Mint)
> are
> >> > willing and able to do the work necessary.. A number of stacks are
> currently
> >> > working on implementations of this new approach, which we hope to have
> in
> >> > time for the Interim meeting.
> >> >
> >> >
> >> > A design document describing the overall approach can be found at:
> >> >
> >> >
> https://docs.google.com/document/d/1fRsJqPinJl8N3b-
> bflDRV6auojfJLkxddT93j6SwHY8/edit
> >> >
> >> >
> >> > A PR making the changes to the QUIC documents can be found at:
> >> >
> >> > https://github.com/quicwg/base-drafts/pull/1377
> >> >
> >> >
> >> > A few design details did not have clear consensus, but it was felt it
> would
> >> > be better to discuss those in the wider WG than delay the design team.
>   A
> >> > consistent choice was made in the PR and these issues are mentioned in
> >> > Appendix B of the design doc.
> >> >
> >> >
> >> > As always, comments and questions welcome. That said, this is a big PR
> and
> >> > we recognize that some editorial work is going to be needed before
> merging.
> >> > In the interest of letting people follow along, and to keep github
> from
> >> > falling over, we ask people to keep discussion on the mailing list and
> >> > refrain from making PR comments.
> >> >
> >> >
> >> > See you in Kista!
> >> >
> >> >
> >> > Ian and Eric
>
>
>
> >> --
> >> Kazuho Oku
>
>

--000000000000b63f6f056ce848c3
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div>I&#39;m with MT on this one. Bits in the handshake ar=
e comparatively cheap. I do think it&#39;s of *some* benefit to be able to =
use the STREAM frame parser, but that 0x18 hack seems to get us that. <br><=
/div><div><br></div><div>-Ekr</div><div><br></div></div><div class=3D"gmail=
_extra"><br><div class=3D"gmail_quote">On Wed, May 23, 2018 at 4:51 PM, Mar=
tin Thomson <span dir=3D"ltr">&lt;<a href=3D"mailto:martin.thomson@gmail.co=
m" target=3D"_blank">martin.thomson@gmail.com</a>&gt;</span> wrote:<br><blo=
ckquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #c=
cc solid;padding-left:1ex">I&#39;m not a fan of micro-optimizations like th=
is, especially when it means<br>
taking space we don&#39;t need.<br>
<br>
We don&#39;t need ANY of the bits on the CRYPTO stream.=C2=A0 The savings f=
or an<br>
absent length and offset are marginal and not worth burning 8 frame types<b=
r>
on, and the stream never really ends.=C2=A0 So if we made it have a type of=
<br>
0x18, then you would run it through the same code and get the same result.<=
br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
On Wed, May 23, 2018 at 4:40 PM Jana Iyengar &lt;<a href=3D"mailto:jri.ietf=
@gmail.com">jri.ietf@gmail.com</a>&gt; wrote:<br>
<br>
&gt; Thank you for your implementation and your report -- this is terrific =
and<br>
helpful!<br>
<br>
&gt; On your note about CRYPTO_HS frames, I think your idea is clever. Just=
 to<br>
ensure that I am understanding it correctly, I believe you&#39;re proposing=
<br>
defining:<br>
&gt; 0x10 - 0x17: STREAM frame<br>
&gt; 0x18 - 0x1F: CRYPTO_HS frame<br>
<br>
&gt; We can the same frame format for CRYPTO_HS as STREAM except that<br>
CRYPTO_HS will not have the stream ID field. This means an implementation<b=
r>
handling these frames can reuse the stream machinery with a small change to=
<br>
parse the header bits as follows:<br>
<br>
&gt; if (type &amp; 0x10)=C2=A0 {=C2=A0 // STREAM or CRYPTO_HS frame<br>
&gt;=C2=A0 =C2=A0 =C2=A0 if (type &amp; 0x08) streamID =3D varint_consume(f=
rame);<br>
&gt;=C2=A0 =C2=A0 =C2=A0 if (type &amp; 0x04) offset =3D varint_consume(fra=
me);<br>
&gt;=C2=A0 =C2=A0 =C2=A0 if (type &amp; 0x02) length =3D varint_consume(fra=
me);<br>
&gt;=C2=A0 =C2=A0 =C2=A0 if (type &amp; 0x01) fin =3D 1;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 read body if present<br>
&gt; }<br>
<br>
&gt; On Tue, May 22, 2018 at 9:57 PM, Kazuho Oku &lt;<a href=3D"mailto:kazu=
hooku@gmail.com">kazuhooku@gmail.com</a>&gt; wrote:<br>
<br>
&gt;&gt; FWIW, I am happy to tell you that I have a working PoC code for th=
e<br>
&gt;&gt; proposed approach.<br>
<br>
&gt;&gt; On the QUIC side, I saw 2% (124 lines) increase in code size (more=
 on<br>
&gt;&gt; that below). On the TLS side, I also saw 2% (175 lines) increase.<=
br>
&gt;&gt; However please look at the code size change especially on the QUIC=
<br>
&gt;&gt; side with grain of salt, as it is just a PoC.<br>
<br>
&gt;&gt; As expected, the key and encryption-level management on the QUIC s=
ide<br>
&gt;&gt; became very clean. Following are some of the design decisions I ma=
de<br>
&gt;&gt; as well as the outcomes:<br>
<br>
&gt;&gt; * All the interaction between picotls and quicly are accompanied b=
y<br>
&gt;&gt; &quot;epoch&quot;. Handshake messages are attributed with their ep=
ochs so that<br>
&gt;&gt; they do not get protected by the wrong key, or so that octets rece=
ived<br>
&gt;&gt; under an incorrect encryption context cannot be misused.<br>
<br>
&gt;&gt; * All the traffic keys are governed by quicly (managing some traff=
ic<br>
&gt;&gt; keys in TLS while managing PNE key in QUIC seems messy).<br>
<br>
&gt;&gt; * The Initial key is setup by quicly, wheeras other traffic keys a=
re<br>
&gt;&gt; installed by picotls by calling a callback named<br>
&gt;&gt; update_traffic_key_cb. The callback accepts and installs 6 keys in=
<br>
&gt;&gt; total: for three levels (i.e. 0-RTT, handshake, 1-RTT) in two<br>
&gt;&gt; directions (send-side and receive-side).<br>
<br>
&gt;&gt; * Three PN spaces have their own AEAD encryption key. Initial PN a=
nd<br>
&gt;&gt; Handshake PN spaces have one aead decryption key each. Application=
 PN<br>
&gt;&gt; space has up to two decryption keys: either for 0-RTT and 1-RTT or=
 for<br>
&gt;&gt; two 1-RTT keys during key update.<br>
<br>
&gt;&gt; It was a pain to have a dedicated frame encoding for CRYPTO_HS, ev=
en<br>
&gt;&gt; though we can reuse (and I reused) the retransmission and reassemb=
ly<br>
&gt;&gt; logic of QUIC streams for the handshake flows. About a half of the=
<br>
&gt;&gt; code size increase comes from that (the other half comes from the<=
br>
&gt;&gt; added abstraction for having two contexts for the handshake). I wo=
uld<br>
&gt;&gt; prefer reusing the STREAM frame encoding for the handshake data. W=
e<br>
&gt;&gt; could possibly use a different base offset (i.e. for CRYPTO_HS fra=
mes<br>
&gt;&gt; we could use 0b00011XXX, whereas the STREAM frames use 0b00010XXX)=
, as<br>
&gt;&gt; well as omitting the Stream ID field.<br>
<br>
&gt;&gt; Overall, now that I have a PoC, I am more confident that the propo=
sed<br>
&gt;&gt; approach is the correct path forward. It *simplifies* the QUIC sta=
ck<br>
&gt;&gt; at the same time giving us better security properties as well as<b=
r>
&gt;&gt; fixing various issues in the current design (as discussed in the<b=
r>
&gt;&gt; design doc).<br>
<br>
<br>
&gt;&gt; 2018-05-23 10:30 GMT+09:00 Ian Swett &lt;ianswett=3D<br>
<a href=3D"mailto:40google.com@dmarc.ietf.org">40google.com@dmarc.ietf.org<=
/a>&gt;:<br>
&gt;&gt; &gt; Dear QUIC WG,<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; On behalf of the Stream 0 Design Team, I am pleased to report=
 that we<br>
have<br>
&gt;&gt; &gt; consensus on a proposed approach to share with the WG. The DT=
&#39;s<br>
proposal<br>
&gt;&gt; &gt; will make QUIC and TLS work closer together and incorporates =
ideas from<br>
&gt;&gt; &gt; DTLS, but it does not use the DTLS protocol itself.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; The DT believes this solves the important open Stream 0 issue=
s. The<br>
proposal<br>
&gt;&gt; &gt; will be a bit more invasive in TLS, but we believe it is the =
right<br>
long-term<br>
&gt;&gt; &gt; direction and several TLS stacks (BoringSSL, PicoTLS, NSS, an=
d Mint)<br>
are<br>
&gt;&gt; &gt; willing and able to do the work necessary.. A number of stack=
s are<br>
currently<br>
&gt;&gt; &gt; working on implementations of this new approach, which we hop=
e to have<br>
in<br>
&gt;&gt; &gt; time for the Interim meeting.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; A design document describing the overall approach can be foun=
d at:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
<a href=3D"https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJ=
LkxddT93j6SwHY8/edit" rel=3D"noreferrer" target=3D"_blank">https://docs.goo=
gle.com/<wbr>document/d/1fRsJqPinJl8N3b-<wbr>bflDRV6auojfJLkxddT93j6SwHY8/<=
wbr>edit</a><br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; A PR making the changes to the QUIC documents can be found at=
:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; <a href=3D"https://github.com/quicwg/base-drafts/pull/1377" r=
el=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/<wbr>base-dra=
fts/pull/1377</a><br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; A few design details did not have clear consensus, but it was=
 felt it<br>
would<br>
&gt;&gt; &gt; be better to discuss those in the wider WG than delay the des=
ign team.<br>
=C2=A0 A<br>
&gt;&gt; &gt; consistent choice was made in the PR and these issues are men=
tioned in<br>
&gt;&gt; &gt; Appendix B of the design doc.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; As always, comments and questions welcome. That said, this is=
 a big PR<br>
and<br>
&gt;&gt; &gt; we recognize that some editorial work is going to be needed b=
efore<br>
merging.<br>
&gt;&gt; &gt; In the interest of letting people follow along, and to keep g=
ithub from<br>
&gt;&gt; &gt; falling over, we ask people to keep discussion on the mailing=
 list and<br>
&gt;&gt; &gt; refrain from making PR comments.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; See you in Kista!<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Ian and Eric<br>
<br>
<br>
<br>
&gt;&gt; --<br>
&gt;&gt; Kazuho Oku<br>
<br>
</div></div></blockquote></div><br></div>

--000000000000b63f6f056ce848c3--


From nobody Wed May 23 17:06:01 2018
Return-Path: <jri.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3DE561273B1 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 17:06:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 XQJjmCtGt--I for <quic@ietfa.amsl.com>; Wed, 23 May 2018 17:05:58 -0700 (PDT)
Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4956F124217 for <quic@ietf.org>; Wed, 23 May 2018 17:05:58 -0700 (PDT)
Received: by mail-it0-x22f.google.com with SMTP id c3-v6so176317itj.4 for <quic@ietf.org>; Wed, 23 May 2018 17:05:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=BefT/fXTLn/aXNL1+Dk2tXVOlmRGV0NkCsVc58MgnI0=; b=iHlB8jKAo9MQPlYlw+JPgnbUEO/xgwYHe0Y/pqkqfcUYq5DB8CqvmavbOPFgI0Vlr9 5lytcTL3t7bd268dYK84Jaso1u9Qv3L+5VFTEVDqFHc+ZWw7nlJZ8DWbnBxA4Q3VtDU3 yz2g26LALrwu9XQtBlBNqtrv8mnNoGeGz4+yowh5+NN5Jn8w8kDiW9S76VRzatzSZL6x unKh0AP6SVH2/4QrcA0hdV+72JFeWa6qdNQxsuOh2hHakWggRgj6NvCj6nFh+II1UtsS JWytB2e+jk++q5wzLd+pR+ii2K+v6MdbSw2TytKkITzTZctN1Z/7TQw7pz5CE2vhg/Tk 0W7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=BefT/fXTLn/aXNL1+Dk2tXVOlmRGV0NkCsVc58MgnI0=; b=aO2giQ0Jgk8/NLgZ73JKudZkqphelVHnlr0Fu82E4AwDpmcX2WN0EQKVSLfwsUTcRV o9OUnzFJxSw3EMXsM2Xq0g5pEpoiMmFhsfmx+PfCw3lO3YDGt7QkNVWn5S/jH+8OEXtr h2W+W4DXZp10Yau4O4sonUJSZ23hQgiqSQTGP34iT1xDj+wxrxB7rTEYGxDTkOT7SbWS 7zYuljev+bOqoEkRjXwPPBB6q4p3/6RTJqSeHh44x6Keyd8rtsHs4mda/avH2gi0HOJB q1lAybSvahDPxc6VBuDQaUvPwL+IwuujxmvhY+rFF3/kUcazLs61qCKUDGxuzvCRvlYG 2nlg==
X-Gm-Message-State: ALKqPwdJV8xM6HMnDZKeqhDsa7yWRZpLaY61Tu86atb3uWkrZtprGivM Aab/kCAkjon/Q6ncV6g0c8ZBZtAke22R2kM8faA=
X-Google-Smtp-Source: AB8JxZoPqFGYQV9/+wL5n0Ge9S9si194pLLRpYp8MiL422Ak4q5Q55akwq7qVq+YdVATNtdJxQnzHUmub+S4KbG31fQ=
X-Received: by 2002:a24:36ca:: with SMTP id l193-v6mr7106835itl.103.1527120357489;  Wed, 23 May 2018 17:05:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:27d4:0:0:0:0:0 with HTTP; Wed, 23 May 2018 17:05:56 -0700 (PDT)
In-Reply-To: <7CF7F94CB496BF4FAB1676F375F9666A3BB3F654@bgb01xud1012>
References: <CA+9kkMA0QnSmvbGOktngU+B-eC7CJFXLicEZfxQga6m6Z+gJLQ@mail.gmail.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB3F654@bgb01xud1012>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Wed, 23 May 2018 17:05:56 -0700
Message-ID: <CACpbDce+rCjtqc50uRT8vn2ORLPpBeMiOeGcARUn30TdXRbUZw@mail.gmail.com>
Subject: Re: Higher layer comments on stream 0 proposal, WG schedule, and gQUIC
To: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
Cc: Ted Hardie <ted.ietf@gmail.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007003e5056ce86aef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Gh9TJhskCrNVc6qWiuzSONpTKbc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 00:06:00 -0000

--0000000000007003e5056ce86aef
Content-Type: text/plain; charset="UTF-8"

I agree that we must grapple with the question of what this proposal does
to the timeline and that schedule needs to be a part of the discussion.

That said, I think this needs to be done in context. Going into London, the
editors spent three days whittling down and addressing open issues as best
we could. This was presented during the wg meeting. Importantly, the list
of issues that we had no clear ideas or direction on how to fix were all
around the handshake (see slide 9 in this deck
<https://github.com/quicwg/wg-materials/blob/master/ietf101/editors-update.pdf>
.)

The set of handshake issues is probably the most difficult and glaring one
at this point in the list of pending QUICv1 issues.

Solving them with the DT's proposal moves us closer to our goals. Yes, it
will take time, but how much time any other solution(s) take? We have only
one other real proposal that fully solves all those issues: some form of
the QUIC/DTLS proposal. The DT spent time with further generations of
integrating QUIC and DTLS, but among others, there are concerns of
available implementations and implementation maturity there. Additionally,
that proposal ends up tying up QUIC and DTLS standardization processes in
ways that may cause even more delay and limit future evolution. It may be
worth documenting the alternative DTLS proposal and why the DT chose the
proposal it did, for posterity.

I agree that we should have a discussion on what this proposal does to our
timeline. But I'll note that this is finally a timeline that would include
real solutions to important open issues that need solving for QUICv1 to
finish.


On Wed, May 23, 2018 at 2:47 PM, Lucas Pardue <Lucas.Pardue@bbc.co.uk>
wrote:

> Hi Ted,
>
> Thanks for your thoughts.
>
> > My back of the envelope calculation is that this means at least one more
> cycle of specification and interop will be required before we get back to
> where we are with draft -11, and that estimate is because I'm in a hopeful
> mood that Sean and Eric can move the required work in TLS along.  A more
> practical Ted would see this as adding at minimum 6 months to the
> schedule.  The changes in TLS are also large enough that I expect that the
> deployment time to see significant penetration of the new libraries to be
> longer than it would be for the previous design.   Call it 9 months, with 3
> months of error bar.
>
> I can't talk to the merit of this proposal in relation to QUIC transport.
> As somebody greatly interested in application mapping (with a WIP HTTP/QUIC
> implementation) I have concerns that progress in this area keeps being
> pushed back. We have little interop experience in this area to feed back to
> transport.
>
> A particular sore point is that the handshake-oriented changes have weak
> relation to QUIC "steady state', upon which application mappings depend.
> E.g. Draft 09 and 12 differ little in handling of STREAM frames.
>
> Regards
> Lucas
>

--0000000000007003e5056ce86aef
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I agree that we must grapple with the question of what thi=
s proposal does to the timeline and that schedule needs to be a part of the=
 discussion.<div><br></div><div>That said, I think this needs to be done in=
 context. Going into London, the editors spent three days whittling down an=
d addressing open issues as best we could. This was presented during the wg=
 meeting. Importantly, the list of issues that we had no clear ideas or dir=
ection on how to fix were all around the handshake (see slide 9 in <a href=
=3D"https://github.com/quicwg/wg-materials/blob/master/ietf101/editors-upda=
te.pdf">this deck</a>.)</div><div><br></div><div>The set of handshake issue=
s is probably the most difficult and glaring one at this point in the list =
of pending QUICv1 issues.</div><div><br></div><div>Solving them with the DT=
&#39;s proposal moves us closer to our goals. Yes, it will take time, but h=
ow much time any other solution(s) take? We have only one other real propos=
al that fully solves all those issues: some form of the QUIC/DTLS proposal.=
 The DT spent time with further generations of integrating QUIC and DTLS, b=
ut among others, there are concerns of available implementations and implem=
entation maturity there. Additionally, that proposal ends up tying up QUIC =
and DTLS standardization processes in ways that may cause even more delay a=
nd limit future evolution. It may be worth documenting the alternative DTLS=
 proposal and why the DT chose the proposal it did, for posterity.</div><di=
v><br></div><div>I agree that we should have a discussion on what this prop=
osal does to our timeline. But I&#39;ll note that this is finally a timelin=
e that would include real solutions to important open issues that need solv=
ing for QUICv1 to finish.</div><div><br></div></div><div class=3D"gmail_ext=
ra"><br><div class=3D"gmail_quote">On Wed, May 23, 2018 at 2:47 PM, Lucas P=
ardue <span dir=3D"ltr">&lt;<a href=3D"mailto:Lucas.Pardue@bbc.co.uk" targe=
t=3D"_blank">Lucas.Pardue@bbc.co.uk</a>&gt;</span> wrote:<br><blockquote cl=
ass=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;p=
adding-left:1ex">Hi Ted,<br>
<br>
Thanks for your thoughts.<br>
<span class=3D""><br>
&gt; My back of the envelope calculation is that this means at least one mo=
re cycle of specification and interop will be required before we get back t=
o where we are with draft -11, and that estimate is because I&#39;m in a ho=
peful mood that Sean and Eric can move the required work in TLS along.=C2=
=A0 A more practical Ted would see this as adding at minimum 6 months to th=
e schedule.=C2=A0 The changes in TLS are also large enough that I expect th=
at the deployment time to see significant penetration of the new libraries =
to be longer than it would be for the previous design.=C2=A0 =C2=A0Call it =
9 months, with 3 months of error bar.<br>
<br>
</span>I can&#39;t talk to the merit of this proposal in relation to QUIC t=
ransport. As somebody greatly interested in application mapping (with a WIP=
 HTTP/QUIC implementation) I have concerns that progress in this area keeps=
 being pushed back. We have little interop experience in this area to feed =
back to transport. <br>
<br>
A particular sore point is that the handshake-oriented changes have weak re=
lation to QUIC &quot;steady state&#39;, upon which application mappings dep=
end. E.g. Draft 09 and 12 differ little in handling of STREAM frames. <br>
<br>
Regards<br>
<span class=3D"HOEnZb"><font color=3D"#888888">Lucas<br>
</font></span></blockquote></div><br></div>

--0000000000007003e5056ce86aef--


From nobody Wed May 23 17:06:08 2018
Return-Path: <kazuhooku@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31197124217 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 17:06:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 MkvpdeMNyENL for <quic@ietfa.amsl.com>; Wed, 23 May 2018 17:06:00 -0700 (PDT)
Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e:c05::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4EBAD12D7F7 for <quic@ietf.org>; Wed, 23 May 2018 17:06:00 -0700 (PDT)
Received: by mail-pg0-x229.google.com with SMTP id n9-v6so10117071pgq.5 for <quic@ietf.org>; Wed, 23 May 2018 17:06:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to:cc; bh=rOlOMHNI7HB8/LQtP9iI34EJLLR5B4b7B7qTVEQ+s/M=; b=X+qD8olflNv8mxnY3HSsAMI9bXm0o63QNFddFoxNtHBhvIVfImaFQCK8rW/MeOTHda J7CgdC2EVqB0yBcFzVK+cVo/msalwKZ8DFN/41P5dAD38rmfNyBaUT2knO60qyrJHjlT 24rs24sujYKBM0KO+B4g8I/3/w0AScsxCIB8efKbg5eGZGxFQljT53SLw2GdFpHBcoR+ BYeBs4b9TZ7EeZb4AUHnGAtFIuj6rb2uVKTa/P+8VGpEypkQLFlYxSG/AdU6fAr7PnTy rIGg1luIPk+MEhtv94AwgQ0U5Oi+zgrZTZazt6aAJ0UGPBn+wyfbHu8R2ItOp1M6kA8v I/Lg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=rOlOMHNI7HB8/LQtP9iI34EJLLR5B4b7B7qTVEQ+s/M=; b=nm3ZJmtSXHou6ekGKP66WQwNFgX2Z3n+aWOViAZWvL7oeH6T5NUVHiRS78L1JsfBnu SeoRNBinSfWOz6b1Rl5ZWyzKQFqZWjxVvQrcFtqHbYemjN7EnI/uzLRekr60mqg59QRl 66cU2FpOPmBt1Fr3dE6yAR23Gvi/F5+iJt/j2u64Ot7dBo/wBOB7IGRCWDepkxnDvYdX BRl9pZWCYdSr3WFzIq5LL1GukP5iJQ7Txm5TziDdQ0YlwPqSPAY9nnq0DwHIidNbvzBD s8yFJDTZQQNkl8GR7Z+TzEF+bNHFZH7+rdTwaEg6NRpvHg+jEc9pg2RL/tL+aD9MXHDf jOrw==
X-Gm-Message-State: ALKqPwczR++gxgUcw1eDC3mRVEyCfzGcGtKzvXlE4FmeqeeYl+lBn1cS +jh0KKCBukcuRsC5DnuyhfXVEctAla6o+2PrhCQ=
X-Google-Smtp-Source: AB8JxZqUvLPe5VHrPmkJNxGom3Cw7sOICZa4selQocJgUWrcFDl5/mI/V0lw548G/ye8y/ilNgekmRKfdyeZ2xQwZJo=
X-Received: by 2002:a63:ba1c:: with SMTP id k28-v6mr2137449pgf.179.1527120359531;  Wed, 23 May 2018 17:05:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:1189:0:0:0:0 with HTTP; Wed, 23 May 2018 17:05:58 -0700 (PDT)
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Thu, 24 May 2018 09:05:58 +0900
Message-ID: <CANatvzyWK3OxTYx6EFRQG_tJ0tYmyvAd9-2HH2=cDVRhuUd2bQ@mail.gmail.com>
Subject: Stream0 Proposal: CRYPTO_HS frame encoding (Re: Stream0 Design Team Proposal)
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Jana Iyengar <jri.ietf@gmail.com>, Eric Rescorla <ekr@mozilla.com>, QUIC WG <quic@ietf.org>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/X1u1oEdGiVIZt6Py3-7IeRpf5Ic>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 00:06:07 -0000

2018-05-24 8:51 GMT+09:00 Martin Thomson <martin.thomson@gmail.com>:
> I'm not a fan of micro-optimizations like this, especially when it means
> taking space we don't need.
>
> We don't need ANY of the bits on the CRYPTO stream.  The savings for an
> absent length and offset are marginal and not worth burning 8 frame types
> on, and the stream never really ends.  So if we made it have a type of
> 0x18, then you would run it through the same code and get the same result.

Clarification question: are you and EKR suggesting something like below?

0x10 - 0x17: STREAM frame
0x18: CRYPTO_HS frame

if (0x10 <= type && type <= 0x18)  {  // STREAM or CRYPTO_HS frame
     if (type != 0x18) streamID = varint_consume(frame);
     if ((type & 0x04) || type == 0x18) offset = varint_consume(frame);
     if ((type & 0x02) || type == 0x18) length = varint_consume(frame);
     if (type & 0x01) fin = 1;
     read body if present
}

I think that is workable, although it makes me sad because we will
have more conditional branches.

> On Wed, May 23, 2018 at 4:40 PM Jana Iyengar <jri.ietf@gmail.com> wrote:
>
>> Thank you for your implementation and your report -- this is terrific and
> helpful!
>
>> On your note about CRYPTO_HS frames, I think your idea is clever. Just to
> ensure that I am understanding it correctly, I believe you're proposing
> defining:
>> 0x10 - 0x17: STREAM frame
>> 0x18 - 0x1F: CRYPTO_HS frame
>
>> We can the same frame format for CRYPTO_HS as STREAM except that
> CRYPTO_HS will not have the stream ID field. This means an implementation
> handling these frames can reuse the stream machinery with a small change to
> parse the header bits as follows:
>
>> if (type & 0x10)  {  // STREAM or CRYPTO_HS frame
>>      if (type & 0x08) streamID = varint_consume(frame);
>>      if (type & 0x04) offset = varint_consume(frame);
>>      if (type & 0x02) length = varint_consume(frame);
>>      if (type & 0x01) fin = 1;
>>      read body if present
>> }
>
>> On Tue, May 22, 2018 at 9:57 PM, Kazuho Oku <kazuhooku@gmail.com> wrote:
>
>>> FWIW, I am happy to tell you that I have a working PoC code for the
>>> proposed approach.
>
>>> On the QUIC side, I saw 2% (124 lines) increase in code size (more on
>>> that below). On the TLS side, I also saw 2% (175 lines) increase.
>>> However please look at the code size change especially on the QUIC
>>> side with grain of salt, as it is just a PoC.
>
>>> As expected, the key and encryption-level management on the QUIC side
>>> became very clean. Following are some of the design decisions I made
>>> as well as the outcomes:
>
>>> * All the interaction between picotls and quicly are accompanied by
>>> "epoch". Handshake messages are attributed with their epochs so that
>>> they do not get protected by the wrong key, or so that octets received
>>> under an incorrect encryption context cannot be misused.
>
>>> * All the traffic keys are governed by quicly (managing some traffic
>>> keys in TLS while managing PNE key in QUIC seems messy).
>
>>> * The Initial key is setup by quicly, wheeras other traffic keys are
>>> installed by picotls by calling a callback named
>>> update_traffic_key_cb. The callback accepts and installs 6 keys in
>>> total: for three levels (i.e. 0-RTT, handshake, 1-RTT) in two
>>> directions (send-side and receive-side).
>
>>> * Three PN spaces have their own AEAD encryption key. Initial PN and
>>> Handshake PN spaces have one aead decryption key each. Application PN
>>> space has up to two decryption keys: either for 0-RTT and 1-RTT or for
>>> two 1-RTT keys during key update.
>
>>> It was a pain to have a dedicated frame encoding for CRYPTO_HS, even
>>> though we can reuse (and I reused) the retransmission and reassembly
>>> logic of QUIC streams for the handshake flows. About a half of the
>>> code size increase comes from that (the other half comes from the
>>> added abstraction for having two contexts for the handshake). I would
>>> prefer reusing the STREAM frame encoding for the handshake data. We
>>> could possibly use a different base offset (i.e. for CRYPTO_HS frames
>>> we could use 0b00011XXX, whereas the STREAM frames use 0b00010XXX), as
>>> well as omitting the Stream ID field.
>
>>> Overall, now that I have a PoC, I am more confident that the proposed
>>> approach is the correct path forward. It *simplifies* the QUIC stack
>>> at the same time giving us better security properties as well as
>>> fixing various issues in the current design (as discussed in the
>>> design doc).
>
>
>>> 2018-05-23 10:30 GMT+09:00 Ian Swett <ianswett=
> 40google.com@dmarc.ietf.org>:
>>> > Dear QUIC WG,
>>> >
>>> >
>>> > On behalf of the Stream 0 Design Team, I am pleased to report that we
> have
>>> > consensus on a proposed approach to share with the WG. The DT's
> proposal
>>> > will make QUIC and TLS work closer together and incorporates ideas from
>>> > DTLS, but it does not use the DTLS protocol itself.
>>> >
>>> >
>>> > The DT believes this solves the important open Stream 0 issues. The
> proposal
>>> > will be a bit more invasive in TLS, but we believe it is the right
> long-term
>>> > direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and Mint)
> are
>>> > willing and able to do the work necessary.. A number of stacks are
> currently
>>> > working on implementations of this new approach, which we hope to have
> in
>>> > time for the Interim meeting.
>>> >
>>> >
>>> > A design document describing the overall approach can be found at:
>>> >
>>> >
> https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/edit
>>> >
>>> >
>>> > A PR making the changes to the QUIC documents can be found at:
>>> >
>>> > https://github.com/quicwg/base-drafts/pull/1377
>>> >
>>> >
>>> > A few design details did not have clear consensus, but it was felt it
> would
>>> > be better to discuss those in the wider WG than delay the design team.
>   A
>>> > consistent choice was made in the PR and these issues are mentioned in
>>> > Appendix B of the design doc.
>>> >
>>> >
>>> > As always, comments and questions welcome. That said, this is a big PR
> and
>>> > we recognize that some editorial work is going to be needed before
> merging.
>>> > In the interest of letting people follow along, and to keep github from
>>> > falling over, we ask people to keep discussion on the mailing list and
>>> > refrain from making PR comments.
>>> >
>>> >
>>> > See you in Kista!
>>> >
>>> >
>>> > Ian and Eric
>
>
>
>>> --
>>> Kazuho Oku



-- 
Kazuho Oku


From nobody Wed May 23 17:07:40 2018
Return-Path: <jri.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 36720127077 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 17:07:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 XMeJ7IHbW5XM for <quic@ietfa.amsl.com>; Wed, 23 May 2018 17:07:36 -0700 (PDT)
Received: from mail-it0-x22b.google.com (mail-it0-x22b.google.com [IPv6:2607:f8b0:4001:c0b::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 25F47124217 for <quic@ietf.org>; Wed, 23 May 2018 17:07:36 -0700 (PDT)
Received: by mail-it0-x22b.google.com with SMTP id d10-v6so186131itj.1 for <quic@ietf.org>; Wed, 23 May 2018 17:07:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=uuZsKdMZGL37wohzWFEKHhTDUnaivh+p6DXqfDXeGR4=; b=DV5yQOBpOcZebDOl3d/WEaaMex4L9d/afcqAOEttzH04UZdFGgNd2tGeJKUQdKMsxf eFy2lO51GjvApCbm9AswIsT/cqzCkPMA/K0UlZjyINF9rXLDkRytszSCVO4HUNdePaBQ LiNi0iUyj3u05GWdgKbnH3nKEgQQ9uc59FPnRDygv8Ri8yrPfwmj7DezVYbvBq01fiUL kpWqaKD2GaVaGSYKZ59KIP5YBHwOBeOIkIBU7ap0LVExiL9vUK7kWzcr4MkdLy0ksLg8 wZPWHwspbHUvEtw0bJO2l9ljXFGd8PHfuu3XQ2tw0VXrSbt5HD3r9TQKpEZY5AcmnBRQ bshQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=uuZsKdMZGL37wohzWFEKHhTDUnaivh+p6DXqfDXeGR4=; b=ZXqTXdeC1WTpmFcA/FmwWr7C9z0ZKhWOzvZjrKIjqXEjpP+dNvmXNJDjcVL083Akiz 8CE4CuDa4bsz3Fi6vT/4YjwzcfDZ8r1uxoLVUQT5ogs8VOwkHVssDkODW2Ib8yetI8Z+ 3JGneMhSqVYxubhfRWBm/fHXL8OIrrd8jg0rYQdp7cdlGtiK3f/ax3x/f9qgBbWWZJVL h06u2AQTm3dNdCQJCMmC5mLpUqY1YNzulzR7imgJm0EXCQQ6IFhxiJsq9JxHK9mLX5zP tD96FEc8i0pmf0MpyoZ6/mDDNzoyV8Eg1Dvn7kJ7R9pWfiyusrJlNj0XjXPpaPsXmBxf V6Dg==
X-Gm-Message-State: ALKqPwfa++J6TGjpW31fZVKjUsTg5c+6v9hc+9FmA6KRWIaaewr+6xUg +WsKj0ejxg6EYbjkL5mLASmf9Hj4jq23ysyAgyk=
X-Google-Smtp-Source: AB8JxZr7HABtRpcflg4rstc/umvWAWnYjYnes3xkYy8DhwWRoZaA3KrLxR3YQdRZaqRYUJM9NvaqhKjPWWzsuJad0Gc=
X-Received: by 2002:a24:9c1:: with SMTP id 184-v6mr7813106itm.9.1527120455249;  Wed, 23 May 2018 17:07:35 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:27d4:0:0:0:0:0 with HTTP; Wed, 23 May 2018 17:07:34 -0700 (PDT)
In-Reply-To: <CABcZeBNYVmqnv_42mX=cQsdas-ZS8DS1v0dcLjdnBB0iZkoKfQ@mail.gmail.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CANatvzzS+T4HcddCemKF7bb1BmACFp=R4n+YMWkq7tnZaUXw4w@mail.gmail.com> <CACpbDcddWz_i5GoNWYfDAdWKcX0_gOMiKk=ORVABGPE8+7c8Vw@mail.gmail.com> <CABkgnnUfEtkXBYrzZFm9mJ5o_nG_vLVgbgxDG5TxUhLYoe55Xg@mail.gmail.com> <CABcZeBNYVmqnv_42mX=cQsdas-ZS8DS1v0dcLjdnBB0iZkoKfQ@mail.gmail.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Wed, 23 May 2018 17:07:34 -0700
Message-ID: <CACpbDce9nib7hOqBAS3ksoEcZ1d7c3yOFGcL1n+9HNreHRZ-iw@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: Eric Rescorla <ekr@rtfm.com>
Cc: Martin Thomson <martin.thomson@gmail.com>, Eric Rescorla <ekr@mozilla.com>, QUIC WG <quic@ietf.org>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Kazuho Oku <kazuhooku@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000043b50b056ce8704d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/GVCOLHo3vo6-_GBUyAb-4QUz2II>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 00:07:39 -0000

--00000000000043b50b056ce8704d
Content-Type: text/plain; charset="UTF-8"

Fair enough. I think 0x18 is fine.

On Wed, May 23, 2018 at 4:55 PM, Eric Rescorla <ekr@rtfm.com> wrote:

> I'm with MT on this one. Bits in the handshake are comparatively cheap. I
> do think it's of *some* benefit to be able to use the STREAM frame parser,
> but that 0x18 hack seems to get us that.
>
> -Ekr
>
>
> On Wed, May 23, 2018 at 4:51 PM, Martin Thomson <martin.thomson@gmail.com>
> wrote:
>
>> I'm not a fan of micro-optimizations like this, especially when it means
>> taking space we don't need.
>>
>> We don't need ANY of the bits on the CRYPTO stream.  The savings for an
>> absent length and offset are marginal and not worth burning 8 frame types
>> on, and the stream never really ends.  So if we made it have a type of
>> 0x18, then you would run it through the same code and get the same result.
>>
>> On Wed, May 23, 2018 at 4:40 PM Jana Iyengar <jri.ietf@gmail.com> wrote:
>>
>> > Thank you for your implementation and your report -- this is terrific
>> and
>> helpful!
>>
>> > On your note about CRYPTO_HS frames, I think your idea is clever. Just
>> to
>> ensure that I am understanding it correctly, I believe you're proposing
>> defining:
>> > 0x10 - 0x17: STREAM frame
>> > 0x18 - 0x1F: CRYPTO_HS frame
>>
>> > We can the same frame format for CRYPTO_HS as STREAM except that
>> CRYPTO_HS will not have the stream ID field. This means an implementation
>> handling these frames can reuse the stream machinery with a small change
>> to
>> parse the header bits as follows:
>>
>> > if (type & 0x10)  {  // STREAM or CRYPTO_HS frame
>> >      if (type & 0x08) streamID = varint_consume(frame);
>> >      if (type & 0x04) offset = varint_consume(frame);
>> >      if (type & 0x02) length = varint_consume(frame);
>> >      if (type & 0x01) fin = 1;
>> >      read body if present
>> > }
>>
>> > On Tue, May 22, 2018 at 9:57 PM, Kazuho Oku <kazuhooku@gmail.com>
>> wrote:
>>
>> >> FWIW, I am happy to tell you that I have a working PoC code for the
>> >> proposed approach.
>>
>> >> On the QUIC side, I saw 2% (124 lines) increase in code size (more on
>> >> that below). On the TLS side, I also saw 2% (175 lines) increase.
>> >> However please look at the code size change especially on the QUIC
>> >> side with grain of salt, as it is just a PoC.
>>
>> >> As expected, the key and encryption-level management on the QUIC side
>> >> became very clean. Following are some of the design decisions I made
>> >> as well as the outcomes:
>>
>> >> * All the interaction between picotls and quicly are accompanied by
>> >> "epoch". Handshake messages are attributed with their epochs so that
>> >> they do not get protected by the wrong key, or so that octets received
>> >> under an incorrect encryption context cannot be misused.
>>
>> >> * All the traffic keys are governed by quicly (managing some traffic
>> >> keys in TLS while managing PNE key in QUIC seems messy).
>>
>> >> * The Initial key is setup by quicly, wheeras other traffic keys are
>> >> installed by picotls by calling a callback named
>> >> update_traffic_key_cb. The callback accepts and installs 6 keys in
>> >> total: for three levels (i.e. 0-RTT, handshake, 1-RTT) in two
>> >> directions (send-side and receive-side).
>>
>> >> * Three PN spaces have their own AEAD encryption key. Initial PN and
>> >> Handshake PN spaces have one aead decryption key each. Application PN
>> >> space has up to two decryption keys: either for 0-RTT and 1-RTT or for
>> >> two 1-RTT keys during key update.
>>
>> >> It was a pain to have a dedicated frame encoding for CRYPTO_HS, even
>> >> though we can reuse (and I reused) the retransmission and reassembly
>> >> logic of QUIC streams for the handshake flows. About a half of the
>> >> code size increase comes from that (the other half comes from the
>> >> added abstraction for having two contexts for the handshake). I would
>> >> prefer reusing the STREAM frame encoding for the handshake data. We
>> >> could possibly use a different base offset (i.e. for CRYPTO_HS frames
>> >> we could use 0b00011XXX, whereas the STREAM frames use 0b00010XXX), as
>> >> well as omitting the Stream ID field.
>>
>> >> Overall, now that I have a PoC, I am more confident that the proposed
>> >> approach is the correct path forward. It *simplifies* the QUIC stack
>> >> at the same time giving us better security properties as well as
>> >> fixing various issues in the current design (as discussed in the
>> >> design doc).
>>
>>
>> >> 2018-05-23 10:30 GMT+09:00 Ian Swett <ianswett=
>> 40google.com@dmarc.ietf.org>:
>> >> > Dear QUIC WG,
>> >> >
>> >> >
>> >> > On behalf of the Stream 0 Design Team, I am pleased to report that we
>> have
>> >> > consensus on a proposed approach to share with the WG. The DT's
>> proposal
>> >> > will make QUIC and TLS work closer together and incorporates ideas
>> from
>> >> > DTLS, but it does not use the DTLS protocol itself.
>> >> >
>> >> >
>> >> > The DT believes this solves the important open Stream 0 issues. The
>> proposal
>> >> > will be a bit more invasive in TLS, but we believe it is the right
>> long-term
>> >> > direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and Mint)
>> are
>> >> > willing and able to do the work necessary.. A number of stacks are
>> currently
>> >> > working on implementations of this new approach, which we hope to
>> have
>> in
>> >> > time for the Interim meeting.
>> >> >
>> >> >
>> >> > A design document describing the overall approach can be found at:
>> >> >
>> >> >
>> https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6au
>> ojfJLkxddT93j6SwHY8/edit
>> >> >
>> >> >
>> >> > A PR making the changes to the QUIC documents can be found at:
>> >> >
>> >> > https://github.com/quicwg/base-drafts/pull/1377
>> >> >
>> >> >
>> >> > A few design details did not have clear consensus, but it was felt it
>> would
>> >> > be better to discuss those in the wider WG than delay the design
>> team.
>>   A
>> >> > consistent choice was made in the PR and these issues are mentioned
>> in
>> >> > Appendix B of the design doc.
>> >> >
>> >> >
>> >> > As always, comments and questions welcome. That said, this is a big
>> PR
>> and
>> >> > we recognize that some editorial work is going to be needed before
>> merging.
>> >> > In the interest of letting people follow along, and to keep github
>> from
>> >> > falling over, we ask people to keep discussion on the mailing list
>> and
>> >> > refrain from making PR comments.
>> >> >
>> >> >
>> >> > See you in Kista!
>> >> >
>> >> >
>> >> > Ian and Eric
>>
>>
>>
>> >> --
>> >> Kazuho Oku
>>
>>
>

--00000000000043b50b056ce8704d
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Fair enough. I think 0x18 is fine.</div><div class=3D"gmai=
l_extra"><br><div class=3D"gmail_quote">On Wed, May 23, 2018 at 4:55 PM, Er=
ic Rescorla <span dir=3D"ltr">&lt;<a href=3D"mailto:ekr@rtfm.com" target=3D=
"_blank">ekr@rtfm.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><div dir=3D"ltr"><div>I&#39;m with MT on this one. Bits in the handshake=
 are comparatively cheap. I do think it&#39;s of *some* benefit to be able =
to use the STREAM frame parser, but that 0x18 hack seems to get us that. <b=
r></div><div><br></div><div>-Ekr</div><div><br></div></div><div class=3D"HO=
EnZb"><div class=3D"h5"><div class=3D"gmail_extra"><br><div class=3D"gmail_=
quote">On Wed, May 23, 2018 at 4:51 PM, Martin Thomson <span dir=3D"ltr">&l=
t;<a href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.thom=
son@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">I&#39=
;m not a fan of micro-optimizations like this, especially when it means<br>
taking space we don&#39;t need.<br>
<br>
We don&#39;t need ANY of the bits on the CRYPTO stream.=C2=A0 The savings f=
or an<br>
absent length and offset are marginal and not worth burning 8 frame types<b=
r>
on, and the stream never really ends.=C2=A0 So if we made it have a type of=
<br>
0x18, then you would run it through the same code and get the same result.<=
br>
<div class=3D"m_1023881310675815114HOEnZb"><div class=3D"m_1023881310675815=
114h5"><br>
On Wed, May 23, 2018 at 4:40 PM Jana Iyengar &lt;<a href=3D"mailto:jri.ietf=
@gmail.com" target=3D"_blank">jri.ietf@gmail.com</a>&gt; wrote:<br>
<br>
&gt; Thank you for your implementation and your report -- this is terrific =
and<br>
helpful!<br>
<br>
&gt; On your note about CRYPTO_HS frames, I think your idea is clever. Just=
 to<br>
ensure that I am understanding it correctly, I believe you&#39;re proposing=
<br>
defining:<br>
&gt; 0x10 - 0x17: STREAM frame<br>
&gt; 0x18 - 0x1F: CRYPTO_HS frame<br>
<br>
&gt; We can the same frame format for CRYPTO_HS as STREAM except that<br>
CRYPTO_HS will not have the stream ID field. This means an implementation<b=
r>
handling these frames can reuse the stream machinery with a small change to=
<br>
parse the header bits as follows:<br>
<br>
&gt; if (type &amp; 0x10)=C2=A0 {=C2=A0 // STREAM or CRYPTO_HS frame<br>
&gt;=C2=A0 =C2=A0 =C2=A0 if (type &amp; 0x08) streamID =3D varint_consume(f=
rame);<br>
&gt;=C2=A0 =C2=A0 =C2=A0 if (type &amp; 0x04) offset =3D varint_consume(fra=
me);<br>
&gt;=C2=A0 =C2=A0 =C2=A0 if (type &amp; 0x02) length =3D varint_consume(fra=
me);<br>
&gt;=C2=A0 =C2=A0 =C2=A0 if (type &amp; 0x01) fin =3D 1;<br>
&gt;=C2=A0 =C2=A0 =C2=A0 read body if present<br>
&gt; }<br>
<br>
&gt; On Tue, May 22, 2018 at 9:57 PM, Kazuho Oku &lt;<a href=3D"mailto:kazu=
hooku@gmail.com" target=3D"_blank">kazuhooku@gmail.com</a>&gt; wrote:<br>
<br>
&gt;&gt; FWIW, I am happy to tell you that I have a working PoC code for th=
e<br>
&gt;&gt; proposed approach.<br>
<br>
&gt;&gt; On the QUIC side, I saw 2% (124 lines) increase in code size (more=
 on<br>
&gt;&gt; that below). On the TLS side, I also saw 2% (175 lines) increase.<=
br>
&gt;&gt; However please look at the code size change especially on the QUIC=
<br>
&gt;&gt; side with grain of salt, as it is just a PoC.<br>
<br>
&gt;&gt; As expected, the key and encryption-level management on the QUIC s=
ide<br>
&gt;&gt; became very clean. Following are some of the design decisions I ma=
de<br>
&gt;&gt; as well as the outcomes:<br>
<br>
&gt;&gt; * All the interaction between picotls and quicly are accompanied b=
y<br>
&gt;&gt; &quot;epoch&quot;. Handshake messages are attributed with their ep=
ochs so that<br>
&gt;&gt; they do not get protected by the wrong key, or so that octets rece=
ived<br>
&gt;&gt; under an incorrect encryption context cannot be misused.<br>
<br>
&gt;&gt; * All the traffic keys are governed by quicly (managing some traff=
ic<br>
&gt;&gt; keys in TLS while managing PNE key in QUIC seems messy).<br>
<br>
&gt;&gt; * The Initial key is setup by quicly, wheeras other traffic keys a=
re<br>
&gt;&gt; installed by picotls by calling a callback named<br>
&gt;&gt; update_traffic_key_cb. The callback accepts and installs 6 keys in=
<br>
&gt;&gt; total: for three levels (i.e. 0-RTT, handshake, 1-RTT) in two<br>
&gt;&gt; directions (send-side and receive-side).<br>
<br>
&gt;&gt; * Three PN spaces have their own AEAD encryption key. Initial PN a=
nd<br>
&gt;&gt; Handshake PN spaces have one aead decryption key each. Application=
 PN<br>
&gt;&gt; space has up to two decryption keys: either for 0-RTT and 1-RTT or=
 for<br>
&gt;&gt; two 1-RTT keys during key update.<br>
<br>
&gt;&gt; It was a pain to have a dedicated frame encoding for CRYPTO_HS, ev=
en<br>
&gt;&gt; though we can reuse (and I reused) the retransmission and reassemb=
ly<br>
&gt;&gt; logic of QUIC streams for the handshake flows. About a half of the=
<br>
&gt;&gt; code size increase comes from that (the other half comes from the<=
br>
&gt;&gt; added abstraction for having two contexts for the handshake). I wo=
uld<br>
&gt;&gt; prefer reusing the STREAM frame encoding for the handshake data. W=
e<br>
&gt;&gt; could possibly use a different base offset (i.e. for CRYPTO_HS fra=
mes<br>
&gt;&gt; we could use 0b00011XXX, whereas the STREAM frames use 0b00010XXX)=
, as<br>
&gt;&gt; well as omitting the Stream ID field.<br>
<br>
&gt;&gt; Overall, now that I have a PoC, I am more confident that the propo=
sed<br>
&gt;&gt; approach is the correct path forward. It *simplifies* the QUIC sta=
ck<br>
&gt;&gt; at the same time giving us better security properties as well as<b=
r>
&gt;&gt; fixing various issues in the current design (as discussed in the<b=
r>
&gt;&gt; design doc).<br>
<br>
<br>
&gt;&gt; 2018-05-23 10:30 GMT+09:00 Ian Swett &lt;ianswett=3D<br>
<a href=3D"mailto:40google.com@dmarc.ietf.org" target=3D"_blank">40google.c=
om@dmarc.ietf.org</a>&gt;:<br>
&gt;&gt; &gt; Dear QUIC WG,<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; On behalf of the Stream 0 Design Team, I am pleased to report=
 that we<br>
have<br>
&gt;&gt; &gt; consensus on a proposed approach to share with the WG. The DT=
&#39;s<br>
proposal<br>
&gt;&gt; &gt; will make QUIC and TLS work closer together and incorporates =
ideas from<br>
&gt;&gt; &gt; DTLS, but it does not use the DTLS protocol itself.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; The DT believes this solves the important open Stream 0 issue=
s. The<br>
proposal<br>
&gt;&gt; &gt; will be a bit more invasive in TLS, but we believe it is the =
right<br>
long-term<br>
&gt;&gt; &gt; direction and several TLS stacks (BoringSSL, PicoTLS, NSS, an=
d Mint)<br>
are<br>
&gt;&gt; &gt; willing and able to do the work necessary.. A number of stack=
s are<br>
currently<br>
&gt;&gt; &gt; working on implementations of this new approach, which we hop=
e to have<br>
in<br>
&gt;&gt; &gt; time for the Interim meeting.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; A design document describing the overall approach can be foun=
d at:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
<a href=3D"https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJ=
LkxddT93j6SwHY8/edit" rel=3D"noreferrer" target=3D"_blank">https://docs.goo=
gle.com/docume<wbr>nt/d/1fRsJqPinJl8N3b-bflDRV6au<wbr>ojfJLkxddT93j6SwHY8/e=
dit</a><br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; A PR making the changes to the QUIC documents can be found at=
:<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; <a href=3D"https://github.com/quicwg/base-drafts/pull/1377" r=
el=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base<wbr>-dra=
fts/pull/1377</a><br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; A few design details did not have clear consensus, but it was=
 felt it<br>
would<br>
&gt;&gt; &gt; be better to discuss those in the wider WG than delay the des=
ign team.<br>
=C2=A0 A<br>
&gt;&gt; &gt; consistent choice was made in the PR and these issues are men=
tioned in<br>
&gt;&gt; &gt; Appendix B of the design doc.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; As always, comments and questions welcome. That said, this is=
 a big PR<br>
and<br>
&gt;&gt; &gt; we recognize that some editorial work is going to be needed b=
efore<br>
merging.<br>
&gt;&gt; &gt; In the interest of letting people follow along, and to keep g=
ithub from<br>
&gt;&gt; &gt; falling over, we ask people to keep discussion on the mailing=
 list and<br>
&gt;&gt; &gt; refrain from making PR comments.<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; See you in Kista!<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt;<br>
&gt;&gt; &gt; Ian and Eric<br>
<br>
<br>
<br>
&gt;&gt; --<br>
&gt;&gt; Kazuho Oku<br>
<br>
</div></div></blockquote></div><br></div>
</div></div></blockquote></div><br></div>

--00000000000043b50b056ce8704d--


From nobody Wed May 23 17:37:48 2018
Return-Path: <martin.thomson@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F98612D876 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 17:37:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 XskrQSVUQFWA for <quic@ietfa.amsl.com>; Wed, 23 May 2018 17:37:44 -0700 (PDT)
Received: from mail-ot0-x230.google.com (mail-ot0-x230.google.com [IPv6:2607:f8b0:4003:c0f::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B369D12751F for <quic@ietf.org>; Wed, 23 May 2018 17:37:44 -0700 (PDT)
Received: by mail-ot0-x230.google.com with SMTP id 15-v6so27394011otn.12 for <quic@ietf.org>; Wed, 23 May 2018 17:37:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=y7uu26AkISUsuTz2SoXThmA6m2qlAHTeyzLjd8rW8VI=; b=fKWSqoH6JjjWpsesrgcBf2o9/GwWxC4GUmOfF+oY8uHTzSdV0+bvqMB0fb3BFUraU1 Pj4fYHqFp2Xj8juXQGrEem2WE3Zfb9Ueo6oc61FwZbY/iV9bLQdEIkthKiK56VUEXOAW w9e0iAyUvudYgIDY2R/zUf0U1shLUqVklrlTwAb2qDyT69hO1GLqk+EpHtw7JLD9zOM+ GxVb8z9amqz/9vWcqfqLd+pUr8QladVcSYLBRmdWmT5VanSbBHmJwGlVt5gdE6gQE0QR E9ddaHPAQmnX3pmynLfJsXiqTODREMfd6nGf7JnabbE2B59Zk9LgKzN5bl55ABpjHQvx kBMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=y7uu26AkISUsuTz2SoXThmA6m2qlAHTeyzLjd8rW8VI=; b=MLoTpU7yUrbyRzieo3pdO07X2qsLyyReHeCjtpgZXxiMTYh7tOdHcbqWwnfxzkgAyv cK3wY7d+jSDkniqWbp8UI399uUkqC4angZ5dqQcv8sZS8UWLG6P7cQUi/x9w0fMReUH3 QmVgXSVpLNJxSkXPBASfRUtZp5Gb2h7kbOo6xXq7XvfZQk1ewPbGSh1tRCbG+Nz06xlU 0rBpmLgraAbFznoqpCzJhtZjdsz9RwG/WywXYCAmCMFNbv9yC+eI3ldSo8cjTMyiRE6J E4aP3nLFYbf7KZ0JwkAlhoatdNFVFF8ndS3DAGSk5sS1iVD7Mf4YPxpt3Xw7YdQCV3MS h+1Q==
X-Gm-Message-State: ALKqPwdRstfdDU8gBLwVU8361y/LZyHgIJsmBUKtR4SA76L2wEymMOAI UijON8Bs7O7Dmy+9tEpX7mKs176e7WhvrxPjEK0=
X-Google-Smtp-Source: AB8JxZqiv2wy0CJ/AN29gevjKe2VFykHV4LeIDcRL4/Zr3gCw+uviCzjbl461x0IynegunhikNkIs46Kub4t/M/Orzw=
X-Received: by 2002:a9d:354a:: with SMTP id l10-v6mr3423572ote.15.1527122264027;  Wed, 23 May 2018 17:37:44 -0700 (PDT)
MIME-Version: 1.0
References: <SN1PR08MB1854395A2875541C4DC0673DDA6B0@SN1PR08MB1854.namprd08.prod.outlook.com> <CAOdDvNqsNmU5qahRk_p34gxvEFsZJS0f=xiLixGLSLuZM7pBwQ@mail.gmail.com>
In-Reply-To: <CAOdDvNqsNmU5qahRk_p34gxvEFsZJS0f=xiLixGLSLuZM7pBwQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 24 May 2018 10:37:33 +1000
Message-ID: <CABkgnnVN1KO7XabhdiCY8-zfKU54_i22jhKDxyJyqo3Kt=c4KQ@mail.gmail.com>
Subject: Re: QPACK and the Static Table
To: patrick mcmanus <pmcmanus@mozilla.com>
Cc: Mike Bishop <mbishop@evequefou.be>, QUIC WG <quic@ietf.org>,  HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Og0Ba8TQ0iZDXTCPoI8E92OPbXU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 00:37:46 -0000

On Thu, May 24, 2018 at 9:53 AM Patrick McManus <pmcmanus@mozilla.com>
wrote:
> On Wed, May 23, 2018 at 7:16 PM, Mike Bishop <mbishop@evequefou.be> wrote:

>> Add Alt-Svc entry for HTTP/QUIC with QUIC v1

> this is clever and a good idea.

Alt-Svc includes a hostname, so the value won't help.  The name is all we
can realistically use.


From nobody Wed May 23 17:38:38 2018
Return-Path: <martin.thomson@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDAF812D87D for <quic@ietfa.amsl.com>; Wed, 23 May 2018 17:38:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 bEq-FBu2O3hZ for <quic@ietfa.amsl.com>; Wed, 23 May 2018 17:38:34 -0700 (PDT)
Received: from mail-ot0-x22c.google.com (mail-ot0-x22c.google.com [IPv6:2607:f8b0:4003:c0f::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ADF9412D87A for <quic@ietf.org>; Wed, 23 May 2018 17:38:34 -0700 (PDT)
Received: by mail-ot0-x22c.google.com with SMTP id l13-v6so27394766otk.9 for <quic@ietf.org>; Wed, 23 May 2018 17:38:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=f8L69NNbipk5awztxQV9rZ7rTPhukIAlg+GJq/LUu4k=; b=I6b/nS2kweYaS3aPL9fgEKK21ccNAYGOsG0e5eQBqi7koVIwyy0Ef6HL3huv+H44PC ylnaqzoO5FbdqCyMKpus7/OXdNrlH1dzH682A970lcW7+mn3tZFEINV68Ao8BG9p7256 TVOBITd3Y5SVKf9jOjtoiTpDI0k3WUZ4f2OIOFVFZTU0wjsWshUugaS11y7+gvx9X9Sf hvFb+Yc1yGWyncaLp11X/VcBkPbQEjfPXZm+kRMgqSbGIqtcwYgi55krvOd1bjZxF4UR i8FNIHaBXiRD9UMDx5xnwM/9OEVszFXYGY4xmtaHIcEbzOJzvaupbiNcv9uzmMkN1vZv 6DVw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=f8L69NNbipk5awztxQV9rZ7rTPhukIAlg+GJq/LUu4k=; b=hJnnBlq3bgGSxg6IOLDb4W+sIo0w9gOV6+zzCvy9hzFAKKdyPd97lzodkI7FrGzoxB +LnFU4ZL7n2FZ4PQbFcI3bhkyRwh4GBm/oa0BdgA9Zv192WGF90glRQbrOlfIXcoCddD 8zsNDPbPF8ISCjEqRZrLD7KqPDsFxqBqZ6TGr69LTIbecGPLKw1MYlh85Yw+xCfEMluK 1PvZNAh77na0ke6EyeKznyR+kL5498g3BgiAspjqteSWvhKWL0JA/Xnb15h0rZVD2lyX 0bfSn6zC0pfhvGd+B0o6uXPZO6EUpyZ+XmZCZNJ7sPKQ6euSqy72L1bXrahhinXADnd1 FdOg==
X-Gm-Message-State: ALKqPwf3L203L8xj6kDKnlyogxZLB31qW3FxfsO/7+RPHNWT/+5pTUc8 bZO8/gx0NJj6ZgG4Xfqe2+R5mZE6yuVHiPdT0sE=
X-Google-Smtp-Source: AB8JxZrPJItBFVNNplwhbdXGHvU4oZNSHqGGVP853R4c2vbMY4WLfde+W47VGiFnun3JXynF2U/U8FPGTg8NzFwGWnc=
X-Received: by 2002:a9d:3a65:: with SMTP id j92-v6mr3491399otc.352.1527122314033;  Wed, 23 May 2018 17:38:34 -0700 (PDT)
MIME-Version: 1.0
References: <SN1PR08MB1854395A2875541C4DC0673DDA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
In-Reply-To: <SN1PR08MB1854395A2875541C4DC0673DDA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 24 May 2018 10:38:24 +1000
Message-ID: <CABkgnnUmAGb29zhthW9PH1HVpp3J7ypFxweGOMWcQ8+yjPv7Mg@mail.gmail.com>
Subject: Re: QPACK and the Static Table
To: Mike Bishop <mbishop@evequefou.be>
Cc: HTTP Working Group <ietf-http-wg@w3.org>, QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/mBGzRE9GXNcyZ9LO2PyxrL9Nw_U>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 00:38:37 -0000

It might be worth skimming our current drafts and recent RFCs for header
fields that might be useful.  Early-Data seems like a real option, value
and all.
On Thu, May 24, 2018 at 9:16 AM Mike Bishop <mbishop@evequefou.be> wrote:

> Wanted to get a sense of the affected working groups on two issues in
QPACK (header compression for HTTP/QUIC).



> Rather than indexing the tables together and having the static table at
1-61, QPACK uses a bit to indicate static vs. dynamic.  Since the field is
seven bits long, the performance is comparable for the dynamic table (you
can access 63 entries in one byte, 190 in two), but you can increase the
size of the static table without hurting the dynamic table.  As a result,
we=E2=80=99re building a fresh static table based on queries against HTTPAr=
chive
data.



> The key question that has come up in a couple venues:  What real-world
headers do we want to artificially remove from what the data shows, and
what headers not seen by HTTP Archive do we want to force in anyway?



> So far, we=E2=80=99ve:

> forced in pseudo-headers because the Archive doesn=E2=80=99t capture them=
 and
they would otherwise be absent

> :path, :authority, :method

> deleted values presumed biased by the test configuration:

> Server: (various vendors)
> User-Agent
> Accept-Language: en-us, en;q=3D0.9
> Content-Length: 531

> I still wonder exactly why that=E2=80=99s so common=E2=80=A6.

> P3p: policyref=3D=E2=80=9Dhttps://www.googleadservices.com/...=E2=80=9D=
=E2=80=A6.
> Origin: https://www.facebook.com
> Alt-Svc for various versions of gQUIC
> =E2=80=A6the list goes on

> deleted headers prohibited by HTTP/QUIC and HTTP/2

> Transfer-Encoding: chunked

> Reordered to put headers you=E2=80=99re likely to name-reference at the f=
ront,
especially if you=E2=80=99re unlikely to add them to the dynamic table



> The question is whether we should also backfill headers which HTTP
Archive wouldn=E2=80=99t see, delete headers we wish people wouldn=E2=80=99=
t use, and/or
insert the ones we hope they eventually will.  Some candidates:

> Add Alt-Svc entry for HTTP/QUIC with QUIC v1
> Add X-Forwarded-For
> Don=E2=80=99t add X-Forwarded-For, but do add Forwarded
> Remove Expires to incent the use of Cache-Control
> Collapse the =E2=80=9CContent-Type: <thingey>=E2=80=9D and =E2=80=9CConte=
nt-Type: <thingey>;
charset=3Dutf-8=E2=80=9D entries together

> =E2=80=A6but which one to keep?

> Add Content-Encoding and/or Accept-Encoding entries for zstd



> There=E2=80=99s an endless parade of bikesheds here.  As Martin has point=
ed out,
this will never be perfect, so the goal is =E2=80=9Cgood enough and keep go=
ing.=E2=80=9D
  Any strong feelings about any of these before we merge it?



> Also, there=E2=80=99s been some discussion of a mechanism for selecting o=
ne of
several static tables at the start of a connection..  In that case, the
spec would probably define three tables (client headers, server headers
[for servers that don=E2=80=99t push], combined [for servers that push]) an=
d enable
future RFCs to define others for targeted scenarios (proxies, video
playback, IoT, etc.).  How much does that interest folks?


From nobody Wed May 23 17:41:45 2018
Return-Path: <martin.thomson@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 52E7312D87A for <quic@ietfa.amsl.com>; Wed, 23 May 2018 17:41:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 aBqcUrAtpkC7 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 17:41:41 -0700 (PDT)
Received: from mail-ot0-x22c.google.com (mail-ot0-x22c.google.com [IPv6:2607:f8b0:4003:c0f::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2253212751F for <quic@ietf.org>; Wed, 23 May 2018 17:41:41 -0700 (PDT)
Received: by mail-ot0-x22c.google.com with SMTP id 77-v6so27430880otd.4 for <quic@ietf.org>; Wed, 23 May 2018 17:41:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=ajt71+OAhZ8Wf0hq+AM9VPVKkdk9QoG/pvPT1A9Xqto=; b=oi51fMWwS6c3jMB58VW/aArcyeYK8OPJH3EMagN/oWNy85AgHDQwEep9iEpHjqJ8qH 5MhbPj48xiNJoRRdjASuMuyV6Bhs2MKGjG8OaClaOTasbZtTagpZOh2sGQh7KyiB7tBd IdaFSIYb2WT6WIxlZNv3tHNSN2GvPvp0k3Mg99AI40EBqAQwB+EB+WKz1gtljYElDsTe T7s3srh1WVULa1fjq/fMG+fZPTtBMuT9Ld75dg+9Z17XeqnAzjPtFO6F2ajm4xdnXU+V F7f20DdT8A7EzIJOIMnpxnOEawKqYmu+/2sAwy/mYVQUwzHIFd0GaFvi8amYM4RAmfw4 H21g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=ajt71+OAhZ8Wf0hq+AM9VPVKkdk9QoG/pvPT1A9Xqto=; b=XwITRPPfUNmq16PxW0wesfhfqdKgrD2yuP5zUifk8v323jJ49gGnZ0Rwks+MvOF/rB TsvD3C0JhGSN8RMxPiuogDLGEhVK092SKxPJHscO8U6dAVRI2D3zNh/6ioIxaddAIThy xvfIxUlmv+ObPXSv5eY3Ay+UwKx1BrH6fu5PYyn9l0oQFbeHBCb4JXEJTeI7U2LF6MQl +wk1n3ZxEkItYNO54Tb44uKNiOUrzWTW7AOZVcYnQtwlbF+znK0xOP5YLkzjFr0V3ra3 v0DtpBmWJEIih31vuegyL36lZMLbLRNWFfCRZ6XBXFIeGBUEyoow2+8VSs6uQqI9tjGz 6/jw==
X-Gm-Message-State: ALKqPwfOJNDvg+CCR1E2gx7+rxBGLzeBlQmbJLnxjb493XMgPrSoiolw H6kLqPx0rM8zKdGoLeFtss4frj2+fyU1EkSbANclHA==
X-Google-Smtp-Source: AB8JxZqruk+P3CdsnecDwgWAV8UaZhgfLJmq9EgkltT81rtgxBltRjeJCMei2VtAWvhs2UKatC6V7j/plgKzJajtZbk=
X-Received: by 2002:a9d:3ea5:: with SMTP id b34-v6mr3030705otc.283.1527122500486;  Wed, 23 May 2018 17:41:40 -0700 (PDT)
MIME-Version: 1.0
References: <CANatvzyWK3OxTYx6EFRQG_tJ0tYmyvAd9-2HH2=cDVRhuUd2bQ@mail.gmail.com>
In-Reply-To: <CANatvzyWK3OxTYx6EFRQG_tJ0tYmyvAd9-2HH2=cDVRhuUd2bQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 24 May 2018 10:41:30 +1000
Message-ID: <CABkgnnUe8yd5s+kyPvwXQ6RoSdFXbaL2P4j0_fkL_reVe7s+_Q@mail.gmail.com>
Subject: Re: Stream0 Proposal: CRYPTO_HS frame encoding (Re: Stream0 Design Team Proposal)
To: Kazuho Oku <kazuhooku@gmail.com>
Cc: Jana Iyengar <jri.ietf@gmail.com>, ekr@mozilla.com, QUIC WG <quic@ietf.org>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Bb7ortyocRPUb-ojgn1k2F8GqTg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 00:41:43 -0000

On Thu, May 24, 2018 at 10:06 AM Kazuho Oku <kazuhooku@gmail.com> wrote:
> 0x10 - 0x17: STREAM frame
> 0x18: CRYPTO_HS frame
...
> I think that is workable, although it makes me sad because we will
> have more conditional branches.

Yeah.  We have an extremely limited space here.  And while Jana is right
that we haven't used much yet, we're only just starting.  As for
conditionals.  Maybe.  One way to implement this is a switch statement, and
those might not suffer as badly when you consider that you also have to
dispatch to other frame handlers in the same piece of code.


From nobody Wed May 23 17:42:45 2018
Return-Path: <kazuhooku@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C723712751F for <quic@ietfa.amsl.com>; Wed, 23 May 2018 17:42:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 MmaTwZhzmerq for <quic@ietfa.amsl.com>; Wed, 23 May 2018 17:42:42 -0700 (PDT)
Received: from mail-pf0-x235.google.com (mail-pf0-x235.google.com [IPv6:2607:f8b0:400e:c00::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 22D2F127201 for <quic@ietf.org>; Wed, 23 May 2018 17:42:42 -0700 (PDT)
Received: by mail-pf0-x235.google.com with SMTP id q22-v6so11312982pff.11 for <quic@ietf.org>; Wed, 23 May 2018 17:42:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=n9sagG6fKSJP+8k9ZEHBc/76V67/ipUKO8JyIxtxYRE=; b=XjhfSVUN6Xb2/WwGud/RYrLSWvReHoMtcUCz0vlWCdI+ta5vVsQtvQC9c2dh2DbvEt UuOI9Ad4VZ1tgRJp1DEYoxAGmSyYFY5WuvEVBO4JTCoJDmdmDXqjZ4vDjM13vRnsCotk 2Jc7BWQMDoQWQsUX0EABH5jonCIgO3gQz/p8NcpooGZfG6bQbAeMqGjD6uGfseR3mtag ET/6eyfwGfJt6UjS1ecvZoRO3luErZ9/ALQNaGQGuaXDfqANK/HhovqA4Lxfyhy84lU+ 7vM98YdeBIsgP8BruC8w+aN4E4/zDTx377UsGEco9D4pZ+KOM6VV92ALyWLjRIDP6ILT x36A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=n9sagG6fKSJP+8k9ZEHBc/76V67/ipUKO8JyIxtxYRE=; b=AJcB3Tqs3j0zUVKU26bSddS0ymiU8yj0zzgI1qsdfVV7Ovi+abKHm+xoOE1en3y6zk B8fd4gX16epPPUpWC8TbflRahCYUljzrsAGF3SxNRBwK+aSOwicI/WkZpqhfh0guento MEzx5SqPSA33bsUrTUtyOrGBo/HMKrKEdZMu9oge5mOB0H+Dg+G/5pBYoQXXlhn+IFcs XMdGAxzb4ON4B4SLRUbmBwCwg1VqB/Xs9B5SOiy/VdWjKkXg1Q5JvAUUF7ngvC5l/1RB SZrGPz5HYUgavN1nxl768Lua8Mzzj6sRPSyLbZxTpgxiww//UnyU1pLzG422tgib+bTH JpuA==
X-Gm-Message-State: ALKqPwcy6Nkrt27Oqh3Iq6VrCVBTJ7vtTCvznp7908hLkU2kyS4LvjFu aNJnAsWTXQwRt/X1EmfmNCoqyGcIuMbPuUZK+tA=
X-Google-Smtp-Source: AB8JxZpTyE+JG1VtsaEAgpfrSG5URvsRJGj49ECLNiHmY3UdFOMX/+ZkGd5Mhr/Z4ymCfe8ZUaU4owZLoTS9ME1sq7s=
X-Received: by 2002:a63:7c04:: with SMTP id x4-v6mr3939420pgc.67.1527122561547;  Wed, 23 May 2018 17:42:41 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:1189:0:0:0:0 with HTTP; Wed, 23 May 2018 17:42:40 -0700 (PDT)
In-Reply-To: <CACpbDce+rCjtqc50uRT8vn2ORLPpBeMiOeGcARUn30TdXRbUZw@mail.gmail.com>
References: <CA+9kkMA0QnSmvbGOktngU+B-eC7CJFXLicEZfxQga6m6Z+gJLQ@mail.gmail.com> <7CF7F94CB496BF4FAB1676F375F9666A3BB3F654@bgb01xud1012> <CACpbDce+rCjtqc50uRT8vn2ORLPpBeMiOeGcARUn30TdXRbUZw@mail.gmail.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Thu, 24 May 2018 09:42:40 +0900
Message-ID: <CANatvzyy4TBpRvOHUD3m0ph=jO_GwYH_v3n_WHX7vrF_OtL7Yg@mail.gmail.com>
Subject: Re: Higher layer comments on stream 0 proposal, WG schedule, and gQUIC
To: Jana Iyengar <jri.ietf@gmail.com>
Cc: Lucas Pardue <Lucas.Pardue@bbc.co.uk>, Ted Hardie <ted.ietf@gmail.com>,  IETF QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/t2FA3wyf6USe4rJujX8tCoFqU1M>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 00:42:44 -0000

2018-05-24 9:05 GMT+09:00 Jana Iyengar <jri.ietf@gmail.com>:
> I agree that we must grapple with the question of what this proposal does to
> the timeline and that schedule needs to be a part of the discussion.
>
> That said, I think this needs to be done in context. Going into London, the
> editors spent three days whittling down and addressing open issues as best
> we could. This was presented during the wg meeting. Importantly, the list of
> issues that we had no clear ideas or direction on how to fix were all around
> the handshake (see slide 9 in this deck.)
>
> The set of handshake issues is probably the most difficult and glaring one
> at this point in the list of pending QUICv1 issues.
>
> Solving them with the DT's proposal moves us closer to our goals. Yes, it
> will take time, but how much time any other solution(s) take? We have only
> one other real proposal that fully solves all those issues: some form of the
> QUIC/DTLS proposal. The DT spent time with further generations of
> integrating QUIC and DTLS, but among others, there are concerns of available
> implementations and implementation maturity there. Additionally, that
> proposal ends up tying up QUIC and DTLS standardization processes in ways
> that may cause even more delay and limit future evolution. It may be worth
> documenting the alternative DTLS proposal and why the DT chose the proposal
> it did, for posterity.

FWIW, I have added Appendix C to the design doc that briefly explains
the DTLS-based approach as well as the reasons why we abandoned it.

The text is rough and is likely to have some aspects missing, I would
appreciate it if anybody in the Design Team could improve it.

Lastly, the comparison of the wire formats between the DTLS-based
approach and the proposed approach might give us a clue on what the
difference of security aspects are between DTLS and the proposed
approach. I think that it is more natural to compare the proposed
approach to DTLS than to TLS when discussing about security aspects.

>
> I agree that we should have a discussion on what this proposal does to our
> timeline. But I'll note that this is finally a timeline that would include
> real solutions to important open issues that need solving for QUICv1 to
> finish.
>
>
> On Wed, May 23, 2018 at 2:47 PM, Lucas Pardue <Lucas.Pardue@bbc.co.uk>
> wrote:
>>
>> Hi Ted,
>>
>> Thanks for your thoughts.
>>
>> > My back of the envelope calculation is that this means at least one more
>> > cycle of specification and interop will be required before we get back to
>> > where we are with draft -11, and that estimate is because I'm in a hopeful
>> > mood that Sean and Eric can move the required work in TLS along.  A more
>> > practical Ted would see this as adding at minimum 6 months to the schedule.
>> > The changes in TLS are also large enough that I expect that the deployment
>> > time to see significant penetration of the new libraries to be longer than
>> > it would be for the previous design.   Call it 9 months, with 3 months of
>> > error bar.
>>
>> I can't talk to the merit of this proposal in relation to QUIC transport.
>> As somebody greatly interested in application mapping (with a WIP HTTP/QUIC
>> implementation) I have concerns that progress in this area keeps being
>> pushed back. We have little interop experience in this area to feed back to
>> transport.
>>
>> A particular sore point is that the handshake-oriented changes have weak
>> relation to QUIC "steady state', upon which application mappings depend.
>> E.g. Draft 09 and 12 differ little in handling of STREAM frames.
>>
>> Regards
>> Lucas
>
>



-- 
Kazuho Oku


From nobody Wed May 23 17:47:00 2018
Return-Path: <pmcmanus@mozilla.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F3CF112D875 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 17:46:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.233
X-Spam-Level: 
X-Spam-Status: No, score=-1.233 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
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 BHqJE9vkO5bh for <quic@ietfa.amsl.com>; Wed, 23 May 2018 17:46:57 -0700 (PDT)
Received: from linode64.ducksong.com (linode6only.ducksong.com [IPv6:2600:3c02::f03c:91ff:fe6e:e8da]) by ietfa.amsl.com (Postfix) with ESMTP id 42ECA12D87A for <quic@ietf.org>; Wed, 23 May 2018 17:46:57 -0700 (PDT)
Received: from mail-ot0-f174.google.com (mail-ot0-f174.google.com [74.125.82.174]) by linode64.ducksong.com (Postfix) with ESMTPSA id BEBF13A06A for <quic@ietf.org>; Wed, 23 May 2018 20:46:56 -0400 (EDT)
Received: by mail-ot0-f174.google.com with SMTP id g7-v6so27419394otj.11 for <quic@ietf.org>; Wed, 23 May 2018 17:46:56 -0700 (PDT)
X-Gm-Message-State: ALKqPwe+PKoZJHSph24Nl7N8rscSFtQWkMUztDIOn1vMnkYd7AT+FQNA 4HCihjRRoqkT/CVFPTBzAv4hwnsBlQj36ZVnC5k=
X-Google-Smtp-Source: AB8JxZozvfEk48w84HuvJTDoyv3ClBxvlkHSBNrGqR9MUdkyvWeJ40ThwA+uLH0LUyBxDaWuxFZnP24xYdP1QthfRQA=
X-Received: by 2002:a9d:4181:: with SMTP id p1-v6mr3475131ote.2.1527122816465;  Wed, 23 May 2018 17:46:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4a:8a24:0:0:0:0:0 with HTTP; Wed, 23 May 2018 17:46:55 -0700 (PDT)
In-Reply-To: <CABkgnnVN1KO7XabhdiCY8-zfKU54_i22jhKDxyJyqo3Kt=c4KQ@mail.gmail.com>
References: <SN1PR08MB1854395A2875541C4DC0673DDA6B0@SN1PR08MB1854.namprd08.prod.outlook.com> <CAOdDvNqsNmU5qahRk_p34gxvEFsZJS0f=xiLixGLSLuZM7pBwQ@mail.gmail.com> <CABkgnnVN1KO7XabhdiCY8-zfKU54_i22jhKDxyJyqo3Kt=c4KQ@mail.gmail.com>
From: Patrick McManus <pmcmanus@mozilla.com>
Date: Wed, 23 May 2018 20:46:55 -0400
X-Gmail-Original-Message-ID: <CAOdDvNquN4M5HiWeS0wnLmpUEh=cQFsxjFcFWjxjTc5KGJfM7A@mail.gmail.com>
Message-ID: <CAOdDvNquN4M5HiWeS0wnLmpUEh=cQFsxjFcFWjxjTc5KGJfM7A@mail.gmail.com>
Subject: Re: QPACK and the Static Table
To: Martin Thomson <martin.thomson@gmail.com>
Cc: patrick mcmanus <pmcmanus@mozilla.com>, Mike Bishop <mbishop@evequefou.be>, QUIC WG <quic@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="000000000000010991056ce8fde0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/UYA8c-82n_NqGo5K7SvEnYIsLbw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 00:46:59 -0000

--000000000000010991056ce8fde0
Content-Type: text/plain; charset="UTF-8"

iirc alt-svc requires a colon and a port (and an alpn) but not a hostname.
so quic=":443" would make sense.

On Wed, May 23, 2018 at 8:37 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> On Thu, May 24, 2018 at 9:53 AM Patrick McManus <pmcmanus@mozilla.com>
> wrote:
> > On Wed, May 23, 2018 at 7:16 PM, Mike Bishop <mbishop@evequefou.be>
> wrote:
>
> >> Add Alt-Svc entry for HTTP/QUIC with QUIC v1
>
> > this is clever and a good idea.
>
> Alt-Svc includes a hostname, so the value won't help.  The name is all we
> can realistically use.
>

--000000000000010991056ce8fde0
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">iirc alt-svc requires a colon and a port (and an alpn) but=
 not a hostname. so quic=3D&quot;:443&quot; would make sense.<br></div><div=
 class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, May 23, 2018 =
at 8:37 PM, Martin Thomson <span dir=3D"ltr">&lt;<a href=3D"mailto:martin.t=
homson@gmail.com" target=3D"_blank">martin.thomson@gmail.com</a>&gt;</span>=
 wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">On Thu, May 24, 2018 at 9:53 AM P=
atrick McManus &lt;<a href=3D"mailto:pmcmanus@mozilla.com">pmcmanus@mozilla=
.com</a>&gt;<br>
wrote:<br>
<span class=3D"">&gt; On Wed, May 23, 2018 at 7:16 PM, Mike Bishop &lt;<a h=
ref=3D"mailto:mbishop@evequefou.be">mbishop@evequefou.be</a>&gt; wrote:<br>
<br>
&gt;&gt; Add Alt-Svc entry for HTTP/QUIC with QUIC v1<br>
<br>
&gt; this is clever and a good idea.<br>
<br>
</span>Alt-Svc includes a hostname, so the value won&#39;t help.=C2=A0 The =
name is all we<br>
can realistically use.<br>
</blockquote></div><br></div>

--000000000000010991056ce8fde0--


From nobody Wed May 23 17:50:28 2018
Return-Path: <martin.thomson@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F2B2512D87A for <quic@ietfa.amsl.com>; Wed, 23 May 2018 17:50:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 QjOqB2NPYJDJ for <quic@ietfa.amsl.com>; Wed, 23 May 2018 17:50:25 -0700 (PDT)
Received: from mail-ot0-x235.google.com (mail-ot0-x235.google.com [IPv6:2607:f8b0:4003:c0f::235]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0ABBB124217 for <quic@ietf.org>; Wed, 23 May 2018 17:50:25 -0700 (PDT)
Received: by mail-ot0-x235.google.com with SMTP id l22-v6so27458629otj.0 for <quic@ietf.org>; Wed, 23 May 2018 17:50:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=30oFtekTPX6bXMnWbXoJREOLvjG8X0W3E488ijO+6vA=; b=sRztkMs7T0z9C3VlKTLZa8oHcCOhY7IupsbmNLPwGUUC79Rsl+Gp0XvMHjVJrtKClk uvkgzZl/2VTGhEYeR4DnTbHEMMpuuM2dRWshVoY5VCApso5HMdhjGT7H7pzyj8Ol/ZAO rO1mDr7BT5RAYlaRqXSrEWVFCCfv0qtsm907YTIIKHycpvHuU3EoubPB+eOYnBgVV937 qBXgknFQED7TigJ99uqOqlCbf8JFa9zs0kI0iI7Vy8JqHeClkgNCHr2H5swyjNBLgN0R Pb1QHwdEbRTVDvffs4zJM3bSzgWqko8TFaGNUGcipqtUsQZ5HHFimfBxV5nylyuBx+1h pTow==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=30oFtekTPX6bXMnWbXoJREOLvjG8X0W3E488ijO+6vA=; b=EZtOYVHeFRev/6XxDKEl8n5md+Py7L7q45z/XnsRuDyeCXWyVMJ67Ey4jGzn5XAar9 MA5b5xA1sIZlnD4On07pAm0TNyCyoGYbQ0zJeQybuG5kpgRhQoAocPclL0AsFlFchpvP u3k8zczRC1+c/F2Qvj14cmJgwiN2iOtMpFDEL5b2HgjG7dmqJFi85DDyfOCViguprw5U MXXWOpkLI4Da0DkC5FpTEebbj/hhLre8IFFMBWV4HLQ0yotaf4i2XYkPrHG+nFVGAM+X Em+Ecawfm/aIibTCVyyMSfnDchW8WeSx4AT8vyQ+4+Efe985hPctTj9l532tsfFii+ek N2yg==
X-Gm-Message-State: ALKqPweXLduIZknU7dn14YyPVR9diP2DDy1fWmB0YJcAZ8i9o6gqMZ2e 9RFYLPvoe40qjzgfBm32L+qetkAS+M7yEA91OOTCKupj
X-Google-Smtp-Source: AB8JxZr7YUc15H8VDykEP/JLnLq4JHMnVsGWDAFKnjrgCWebi1mQBKJ3iMPwcz5SaalCllWEUwmv1tv5XLu4Bfzq7QA=
X-Received: by 2002:a9d:34f1:: with SMTP id t46-v6mr3097250otd.396.1527123024416;  Wed, 23 May 2018 17:50:24 -0700 (PDT)
MIME-Version: 1.0
References: <SN1PR08MB1854395A2875541C4DC0673DDA6B0@SN1PR08MB1854.namprd08.prod.outlook.com> <CAOdDvNqsNmU5qahRk_p34gxvEFsZJS0f=xiLixGLSLuZM7pBwQ@mail.gmail.com> <CABkgnnVN1KO7XabhdiCY8-zfKU54_i22jhKDxyJyqo3Kt=c4KQ@mail.gmail.com> <CAOdDvNquN4M5HiWeS0wnLmpUEh=cQFsxjFcFWjxjTc5KGJfM7A@mail.gmail.com>
In-Reply-To: <CAOdDvNquN4M5HiWeS0wnLmpUEh=cQFsxjFcFWjxjTc5KGJfM7A@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 24 May 2018 10:50:14 +1000
Message-ID: <CABkgnnVTsbRnp18Ub1p2PahX_b1Mh4jD+znZG3HODfebPPAvqw@mail.gmail.com>
Subject: Re: QPACK and the Static Table
To: patrick mcmanus <pmcmanus@mozilla.com>
Cc: Mike Bishop <mbishop@evequefou.be>, QUIC WG <quic@ietf.org>,  HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/nRNrW4wcIkcmNtWvyxS4GX0uGq8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 00:50:27 -0000

On Thu, May 24, 2018 at 10:46 AM Patrick McManus <pmcmanus@mozilla.com>
wrote:> iirc alt-svc requires a colon and a port (and an alpn) but not a
hostname. so quic=":443" would make sense.

Ahh, right, then carry on.  That's not the interesting case, but it is
certainly a good default.  I think that it's hq=":443";quic=1 or something
like that though.


From nobody Wed May 23 18:07:38 2018
Return-Path: <kazuhooku@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5F652127077 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 18:07:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 9oZsc-HhAUdG for <quic@ietfa.amsl.com>; Wed, 23 May 2018 18:07:34 -0700 (PDT)
Received: from mail-pg0-x22d.google.com (mail-pg0-x22d.google.com [IPv6:2607:f8b0:400e:c05::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87855124217 for <quic@ietf.org>; Wed, 23 May 2018 18:07:34 -0700 (PDT)
Received: by mail-pg0-x22d.google.com with SMTP id w3-v6so10161644pgv.12 for <quic@ietf.org>; Wed, 23 May 2018 18:07:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to:cc; bh=gXO1t5yUchixC9j7AfiC8oViCJdc7MG2auqsQfEw0/8=; b=l7aRKkEaLPyWqTYKPGnc8ihQg7Hrehc3x+wClybb6Op8kHPF37rwOHfGIVHinzlJwt 3a+AZtpcVo51MHqZfY1TR/Iz9QXkIvJM43TXcDVY7XpTz5pI7Pj/2Fb2y+K59X8k5TNy LHN6iUH1gFWFfUVBDNBRbzSB2SVVp/T/Sj/SGOlOJ3uh4ZTQY+WJU7iILKm++Fye2a8J 29hg7I+AIcghwQAnLmArgV4upe/2XA/E9EltDmlMgCifrTDeUyxYqqm92lsGVdU6195V k8jBz/LIttpfv/cnn3VQlG3Wb7bXxptwKvDGG6n5bxBVdh6f1trJMxOy/tPbFqbYAlKo hhvg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to:cc; bh=gXO1t5yUchixC9j7AfiC8oViCJdc7MG2auqsQfEw0/8=; b=Be7uJz/D6/RHKX4mDAUSRCgfr2m5KHts/4XVK9vUDBmA+/HJUvCu+wZd+gKZ9Q7cUW 8P+H/7MTqRQnSPpLSry8bx3VMYi8nSulWyjR5nD3R4QarZaHqVOshPElEkcTaFx/gMUi Y2V6rZIu7EHCfe/pmIP/HGMacP6tgNK0SiS+tz/w+o6BhmGHikOwoZz9AgeZGF2TZEQG +PKExDbmXuQ2qHyLDpO8KiEMPzry/UNxns+5/tKdZyjlORmXlUfKmstAh0jufr8O2p5M Li1C49n6LwsYj8subJUnTmsJmzpKRv/rXFCVLnrXZbf4d1vdHtKxBN/l0S93GAAzjj5T BHrQ==
X-Gm-Message-State: ALKqPwcvPw5nH91GEd5EuqOATx9GNGHBk6kmPQFJN1MLja+iCcU1m9O2 B1UzRSpEcVC8vabaVoQzImFf/X46sSFI1g8CBmA=
X-Google-Smtp-Source: AB8JxZoojEuik0L2olqbAveGV5wFEBY13zJYTDGGKQl3yOSxPElWAFN5IS+E+7jQVkTcQCw/l54uPmh6M1dT4W2sLeA=
X-Received: by 2002:a65:61c8:: with SMTP id j8-v6mr4029748pgv.370.1527124053990;  Wed, 23 May 2018 18:07:33 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:1189:0:0:0:0 with HTTP; Wed, 23 May 2018 18:07:33 -0700 (PDT)
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Thu, 24 May 2018 10:07:33 +0900
Message-ID: <CANatvzwN1kVO3ofvyYX9cg=cKcg4FdqUT3VB6hneEDa5UjT_0w@mail.gmail.com>
Subject: Stream0 Proposal: Explicit vs. Implicit ACK (Re: Stream0 Design Team Proposal)
To: Jana Iyengar <jri.ietf@gmail.com>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Eric Rescorla <ekr@mozilla.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/aRJLvMh9nBTty_GWKlw2apATzr8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 01:07:37 -0000

2018-05-24 3:46 GMT+09:00 Jana Iyengar <jri.ietf@gmail.com>:

> A thought occurs to me: a CRYPTO_HS frame with the fin bit set can be used
> to indicate that the handshake is done.This could be used as a signal (aka
> HANDSHAKE_DONE) to solve Marten's problem of a client rtxing a CFIN. Of
> course, this would mean that this particular CRYPTO_HS frame would be
> encrypted with a 1-RTT key... which *I think* is fine. What do you think?

I am not sure if that is a good approach.

I would assume that we would like to keep the handshake flow on the
1-RTT key open for the lifetime of the QUIC connection, so that we
could send things related to the TLS (e.g. session tickets). Sending
FIN from the server right after receiving ClientFinished makes that
impossible.

Having said that, I do agree that the need for a dedicated frame is a
pain. It is a pain because we need to have a retransmission logic for
the frame.

I think that you are making a good point in suggesting to consider
reusing the retransmission logic that already exists for bidirectional
flows. But as said, FIN bit does not seem like an answer in this case.

IMO, ideally we should define a new TLS post-handshake message (that
does not convey any data), and send that from the server in response
to ClientFinished using 1-RTT packet. The message will act as a signal
that the server has received ClientFinished.

The benefit of this approach is that we can reuse the retransmission
logic that will exist for handshake flows. The downside is that TLS
stacks need to be aware of the new handshake message.

Considering the fact that the Design Team is already suggesting a
substantial change to the TLS stack, we might have chance in asking
for the addition of a new handshake message. But I am not sure.

-- 
Kazuho Oku


From nobody Wed May 23 19:07:59 2018
Return-Path: <huitema@huitema.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A514712D883 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 19:07:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.601
X-Spam-Level: 
X-Spam-Status: No, score=-2.601 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
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 Hl4k1jHdcatG for <quic@ietfa.amsl.com>; Wed, 23 May 2018 19:07:56 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 B423B12D870 for <quic@ietf.org>; Wed, 23 May 2018 19:07:56 -0700 (PDT)
Received: from xsmtp04.mail2web.com ([168.144.250.231]) by mx62.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1fLffW-0000IU-EJ for quic@ietf.org; Thu, 24 May 2018 04:07:55 +0200
Received: from [10.5.2.15] (helo=xmail05.myhosting.com) by xsmtp04.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1fLfez-0005vi-PF for quic@ietf.org; Wed, 23 May 2018 22:07:52 -0400
Received: (qmail 9405 invoked from network); 24 May 2018 02:07:18 -0000
Received: from unknown (HELO [192.168.1.106]) (Authenticated-user:_huitema@huitema.net@[172.56.42.66]) (envelope-sender <huitema@huitema.net>) by xmail05.myhosting.com (qmail-ldap-1.03) with ESMTPA for <ianswett=40google.com@dmarc.ietf.org>; 24 May 2018 02:07:18 -0000
To: Martin Thomson <martin.thomson@gmail.com>, Kazuho Oku <kazuhooku@gmail.com>
Cc: Jana Iyengar <jri.ietf@gmail.com>, ekr@mozilla.com, QUIC WG <quic@ietf.org>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
References: <CANatvzyWK3OxTYx6EFRQG_tJ0tYmyvAd9-2HH2=cDVRhuUd2bQ@mail.gmail.com> <CABkgnnUe8yd5s+kyPvwXQ6RoSdFXbaL2P4j0_fkL_reVe7s+_Q@mail.gmail.com>
From: Christian Huitema <huitema@huitema.net>
Openpgp: preference=signencrypt
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= xsBNBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAHNJ0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PsLAeQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1bOwE0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAcLBfgQYAQIACQUCUhFfyAIb LgEpCRCTQwmyVcgNcsBdIAQZAQIABgUCUhFfyAAKCRC22tOSFDh1UOlBB/94RsCJepNvmi/c YiNmMnm0mKb6vjv43OsHkqrrCqJSfo95KHyl5Up4JEp8tiJMyYT2mp4IsirZHxz/5lqkw9Az tcGAF3GlFsj++xTyD07DXlNeddwTKlqPRi/b8sppjtWur6Pm+wnAHp0mQ7GidhxHccFCl65w uT7S/ocb1MjrTgnAMiz+x87d48n1UJ7yIdI41Wpg2XFZiA9xPBiDuuoPwFj14/nK0elV5Dvq 4/HVgfurb4+fd74PV/CC/dmd7hg0ZRlgnB5rFUcFO7ywb7/TvICIIaLWcI42OJDSZjZ/MAzz BeXm263lHh+kFxkh2LxEHnQGHCHGpTYyi4Z3dv03HtkH/1SI8joQMQq00Bv+RdEbJXfEExrT u4gtdZAihwvy97OPA2nCdTAHm/phkzryMeOaOztI4PS8u2Ce5lUB6P/HcGtK/038KdX5MYST Fn8KUDt4o29bkv0CUXwDzS3oTzPNtGdryBkRMc9b+yn9+AdwFEH4auhiTQXPMnl0+G3nhKr7 jvzVFJCRif3OAhEm4vmBNDE3uuaXFQnbK56GJrnqVN+KX5Z3M7X3fA8UcVCGOEHXRP/aubiw Ngawj0V9x+43kUapFp+nF69R53UI65YtJ95ec4PTO/Edvap8h1UbdEOc4+TiYwY1TBuIKltY 1cnrjgAWUh/Ucvr++/KbD9tD6C8=
Message-ID: <fa325bc3-5bec-a120-05f2-76d41e0ec605@huitema.net>
Date: Wed, 23 May 2018 19:07:15 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <CABkgnnUe8yd5s+kyPvwXQ6RoSdFXbaL2P4j0_fkL_reVe7s+_Q@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
Subject: Re: Stream0 Proposal: CRYPTO_HS frame encoding (Re: Stream0 Design Team Proposal)
X-Originating-IP: 168.144.250.231
X-AntiSpamCloud-Domain: xsmtpout.mail2web.com
X-AntiSpamCloud-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-AntiSpamCloud-Outgoing-Class: unsure
X-AntiSpamCloud-Outgoing-Evidence: Combined (0.32)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5gbTtVc4RFRxihkczgkqaLp602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO37pNwwF1lRXh5rzvPzo9Jts1ujulqUFmMITHM77eiVisRHd72j1WGykT+2yqiy3xc7i TvJ2/ZGzVWB9scFAaCdIFaUvXN+CI+RGy3Me16pBCnY1T4UEFfy74vbELeG6IB/TBCf6oYXAWGet lavcAjD9ytQxIHf9lN5jjLJaPK8lRJSPf/SXbEnDSsal/zZzc4n9VZdr7RAFD5mRwooUYhwMPaBP aKeQW+/QlaOdv8isl/qMm08Zpim2AHUKEWvQ6G/bWfgucjnNmABpGhD9TTttrFCuZ0NkwnSz2Luu o1u9uevuNfM1HjkNEFwape+IgNezYqxGMqsKjARq8PBC4qjpVMhqNcdjhoIlgrKzBvjTmdySlZou 9qHIGOZDEEo7Oyc1nq0gsY582CWqKjiRB3ukywmZtiDkyd4mEBjJGGEJgawbllbHk+xyUKopM6rc KCaQX/lIXcRWtobViGg9fpW4c1OgHtPoe1bkMdZgVo8qBCB9vp/Ak5XnOfANqRg04KdGK65MmF3z 2sWesOmXQtlz1HQkoj+jjvmw3UQ3Zextr+7/jg66NXUoieIpLIJirIV7hPvBDpgDmC+XXO9ws5qS dbWrmlMqpoC2dVXCySAVqz6Jnv65JqzoprPQQCAlAFYE7tCqypI5WX0qWh4YQLAggJD4IUu+M3kp suZHf2dpbr8Ks0SqCpRWIiXMtOo8/pI8jnU4taLGlA8rnD8bXLUKQCrMv/Srp/VLqDjjh0L1QKHY 6H+wSCoVvwvquzDDiPkKIKnisj+1ZHYjRAh7nr2Ydub/YU/cH64QiTAnRDmAKMFEHS3+vt/Njsed NDmPw/Ld14/y82ebPziYNS9mrGcHWFhVQvKDd9aHm1tzPaYBnxycJOQKmrvtOUL1jquCMfd5HnMi k4ibTRVHi8subW0=
X-Report-Abuse-To: spam@quarantine6.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Wj9-u6oFWWHPkVlxHqT29t4INJQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 02:07:58 -0000

On 5/23/2018 5:41 PM, Martin Thomson wrote:

> On Thu, May 24, 2018 at 10:06 AM Kazuho Oku <kazuhooku@gmail.com> wrote=
:
>> 0x10 - 0x17: STREAM frame
>> 0x18: CRYPTO_HS frame
> ....
>> I think that is workable, although it makes me sad because we will
>> have more conditional branches.
> Yeah.  We have an extremely limited space here.  And while Jana is righ=
t
> that we haven't used much yet, we're only just starting.  As for
> conditionals.  Maybe.  One way to implement this is a switch statement,=
 and
> those might not suffer as badly when you consider that you also have to=

> dispatch to other frame handlers in the same piece of code.
>

I am with Martin on this one. Just one code point for crypto frames,
please. At best the optimization saves 2 bytes in the entire duration of
the connection -- one byte for the CH, one byte for the first frame of
the SH. And for the CH, you don't care because you are going to pas to
min length anyhow.

You can still do common code with the "stream" data even without that,
you just need two small branches of code to parse the stream id, stream
offset, and stream fin. Just default to "stream=3DCrypto, stream offset=3D=

always present, stream fin=3D false" in the crypto branch.

-- Christian Huitema


From nobody Wed May 23 19:10:31 2018
Return-Path: <huitema@huitema.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 83C4412D870 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 19:10:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.589
X-Spam-Level: 
X-Spam-Status: No, score=-2.589 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 lNX_X_BOnIEq for <quic@ietfa.amsl.com>; Wed, 23 May 2018 19:10:26 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 DD6C1129C53 for <quic@ietf.org>; Wed, 23 May 2018 19:10:25 -0700 (PDT)
Received: from xsmtp03.mail2web.com ([168.144.250.223]) by mx66.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1fLfhu-000A0T-EV for quic@ietf.org; Thu, 24 May 2018 04:10:24 +0200
Received: from [10.5.2.12] (helo=xmail02.myhosting.com) by xsmtp03.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1fLfho-0007EB-9Y for quic@ietf.org; Wed, 23 May 2018 22:10:20 -0400
Received: (qmail 11504 invoked from network); 24 May 2018 02:10:14 -0000
Received: from unknown (HELO [192.168.1.106]) (Authenticated-user:_huitema@huitema.net@[172.56.42.66]) (envelope-sender <huitema@huitema.net>) by xmail02.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 24 May 2018 02:10:13 -0000
To: Jana Iyengar <jri.ietf@gmail.com>, IETF QUIC WG <quic@ietf.org>
References: <CACpbDcckRvyn18qowWbLRT+sX2EGj3_yPtoS2d-h6ypg4dFrVQ@mail.gmail.com>
From: Christian Huitema <huitema@huitema.net>
Openpgp: preference=signencrypt
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= xsBNBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAHNJ0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PsLAeQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1bOwE0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAcLBfgQYAQIACQUCUhFfyAIb LgEpCRCTQwmyVcgNcsBdIAQZAQIABgUCUhFfyAAKCRC22tOSFDh1UOlBB/94RsCJepNvmi/c YiNmMnm0mKb6vjv43OsHkqrrCqJSfo95KHyl5Up4JEp8tiJMyYT2mp4IsirZHxz/5lqkw9Az tcGAF3GlFsj++xTyD07DXlNeddwTKlqPRi/b8sppjtWur6Pm+wnAHp0mQ7GidhxHccFCl65w uT7S/ocb1MjrTgnAMiz+x87d48n1UJ7yIdI41Wpg2XFZiA9xPBiDuuoPwFj14/nK0elV5Dvq 4/HVgfurb4+fd74PV/CC/dmd7hg0ZRlgnB5rFUcFO7ywb7/TvICIIaLWcI42OJDSZjZ/MAzz BeXm263lHh+kFxkh2LxEHnQGHCHGpTYyi4Z3dv03HtkH/1SI8joQMQq00Bv+RdEbJXfEExrT u4gtdZAihwvy97OPA2nCdTAHm/phkzryMeOaOztI4PS8u2Ce5lUB6P/HcGtK/038KdX5MYST Fn8KUDt4o29bkv0CUXwDzS3oTzPNtGdryBkRMc9b+yn9+AdwFEH4auhiTQXPMnl0+G3nhKr7 jvzVFJCRif3OAhEm4vmBNDE3uuaXFQnbK56GJrnqVN+KX5Z3M7X3fA8UcVCGOEHXRP/aubiw Ngawj0V9x+43kUapFp+nF69R53UI65YtJ95ec4PTO/Edvap8h1UbdEOc4+TiYwY1TBuIKltY 1cnrjgAWUh/Ucvr++/KbD9tD6C8=
Message-ID: <6d80b771-ba07-cab7-fa86-d4e31d56b919@huitema.net>
Date: Wed, 23 May 2018 19:10:12 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <CACpbDcckRvyn18qowWbLRT+sX2EGj3_yPtoS2d-h6ypg4dFrVQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------34E66CDE848BDCF5F8673E88"
Content-Language: en-US
Subject: Re: Stream0 Proposal: EMPTY_ACK
X-Originating-IP: 168.144.250.223
X-AntiSpamCloud-Domain: xsmtpout.mail2web.com
X-AntiSpamCloud-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-AntiSpamCloud-Outgoing-Class: unsure
X-AntiSpamCloud-Outgoing-Evidence: Combined (0.22)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5tuhAUsZ8s2HCjp/MTl+ysZ602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO37pNwwF1lRXh5rzvPzo9Jts1ujulqUFmMITHM77eiViC28GycJs9THfCUt45GkKlc7i TvJ2/ZGzVWB9scFAaCdIFaUvXN+CI+RGy3Me16pB1XpqFDyTB1Bz0n/bLAAUYB/TBCf6oYXAWGet lavcAjD9ytQxIHf9lN5jjLJaPK8lRJSPf/SXbEnDSsal/zZzc4n9VZdr7RAFD5mRwooUYhwMPaBP aKeQW+/QlaOdv8isl/qMm08Zpim2AHUKEWvQ6G/bWfgucjnNmABpGhD9TTttrFCuZ0NkwnSz2Luu o1u9uevuNfM1HjkNEFwape+IgNezYqxGMqsKjARq8PBC4qjpVMhqNcdjhoIlgrKzBvjTmdySlZou 9qHIGOZDEEo7Oyc1nq0gsY582CWqKjiRB3ukywmZtiDkyd4mEBjJGGEJgawbllbHk+xyUKopM6rc KCaQX/lIXcRWtobViGg9fpWbjljpzcldG5bc9h0NLkX5F8FcHzzV3acxBudgYcInb1adrcf9GnHP f8EL7qeLD8SZ4+t4LK79cWIqQA4tGr3po0jfgLl+Ahd0TIbt0Zij6hgeJ07QR0GiieIKGR3KfdmQ xACKGgjW6av7lJfpYBfZhfURd0e4QPXFipyALWtbLFwBl1z1+w2zS/h3e6UiVRfFVU4swprO0xwu UA+K6SDWpncAZC7h8t4QEhNqmVub9meqA47D/juB1cx4exzYk7zGRNvb2Jhdd2bCgCq95vNY647l NwN4qOsSZg+fYhVZGwX3xdN+1KruynacUoWIYszVwaDsyRiTeu4Ip+KAECko9HdE0Smt1e6HZuGs N7RwePAFMvX7q8M4x6bP/gjzw0OFbIWNJOiaifOc2xlkb46Pa4K5MPGI7fF8+j7E9IwdcQR2aish SbQcCCOvcJLn8v/2OKHH5lr9xXvSM4nM3avg
X-Report-Abuse-To: spam@quarantine6.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2XuvcXVyQP4TPy1supBtemopyEI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 02:10:30 -0000

This is a multi-part message in MIME format.
--------------34E66CDE848BDCF5F8673E88
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit

I dislike the EMPTY_ACK because they are "responses to something that
could not be decrypted". You don't know where the packet came from, it
could be spoofed. So you have on one hand a possible optimization, on
the other hand a possible vulnerability, and in all cases additional
complexity.


On 5/23/2018 4:27 PM, Jana Iyengar wrote:
> (Moving more discussions from main thread)
>
> ---------- Forwarded message ----------
> From: *Subodh Iyengar* <subodh@fb.com <mailto:subodh@fb.com>>
> Date: Wed, May 23, 2018 at 3:37 PM
> Subject: Re: Stream0 Design Team Proposal
> To: Mike Bishop <mbishop@evequefou.be <mailto:mbishop@evequefou.be>>,
> Christian Huitema <huitema@huitema.net <mailto:huitema@huitema.net>>,
> "quic@ietf.org <mailto:quic@ietf.org>" <quic@ietf.org
> <mailto:quic@ietf.org>>
>
>
> FWIW I see EMPTY_ACKs as being very similar to a Duplicate ack. We
> thought about using Duplicate acks as well but we thought that
> EMPTY_ACks would be simpler to implement and be able to convey
> similar information.
>
>
> Subodh
>
> ------------------------------------------------------------------------
> *From:* QUIC <quic-bounces@ietf.org <mailto:quic-bounces@ietf.org>> on
> behalf of Mike Bishop <mbishop@evequefou.be <mailto:mbishop@evequefou.be>>
> *Sent:* Wednesday, May 23, 2018 3:26:35 PM
> *To:* Christian Huitema; quic@ietf.org <mailto:quic@ietf.org>
> *Subject:* RE: Stream0 Design Team Proposal
>  
>
> Christian, can you expand on why you dislike the EMPTY_ACK?  Being
> able to say “I’ve received some packets from you, but am unable to
> process any of them because I’m missing some handshake data” seems
> like a useful way to short-circuit timeouts on clients.  It also
> doesn’t commit the server to holding any state – IIUC, a server could
> form a packet containing an EMPTY_ACK and then discard its internal
> state until it gets the retransmitted (or delayed) Initial packet.
>
>  
>
>
>
>
> On Wed, May 23, 2018 at 4:25 PM, Jana Iyengar <jri.ietf@gmail.com
> <mailto:jri.ietf@gmail.com>> wrote:
>
>     (Forking this discussion off from the main thread.)
>
>     On Wed, May 23, 2018 at 2:13 AM, Kazuho Oku <kazuhooku@gmail.com
>     <mailto:kazuhooku@gmail.com>> wrote:
>
>         2018-05-23 14:29 GMT+09:00 Christian Huitema
>         <huitema@huitema.net <mailto:huitema@huitema.net>>:
>         > I like the proposal. In particular, I really like the
>         encryption of
>         > handshake packets with the handshake key, as it does close a
>         number of
>         > avenues for attacks. And I like that it solves the "ack
>         promotion" issue
>         > that I was complaining against for some time. Turns out that
>         in the current
>         > draft, it is very hard to contain that problem if you enable
>         client auth.
>         >
>         >
>         > On the other hand, I agree with Martin that a lot of the
>         additions to
>         > transmission recovery should be moved to separate PRs. I am
>         not enthusiastic
>         > with the EMPTY ACK mechanism, or with the proposed "implicit
>         > acknowledgement" of a lower crypto stream by a higher level ack.
>
>         At the moment I do not have a strong opinion on the Empty ACK
>         mechanism.
>
>         However, regarding how we close the Initial and Handshake
>         contexts, my
>         preference goes to using implicit ACKs (i.e. use the successful
>         receipt of a packet that is protected under a higher level of
>         encryption key as the signal) rather than explicitly ACKing
>         the last
>         flight of data.
>
>         As I see, there are two downsides in the Explicit ACKing approach.
>
>         * Explicit ACKing requires sending two additional packets
>         during the
>         handshake, which means that we would have more AES operations plus
>         somewhere around 60 bytes of overhead on the wire.
>         * Explicit ACKing requires more signaling from the TLS stack.
>         In case
>         of implicit ACKing, the TLS stack need to only provide the AEAD
>         contexts and the messages, whereas in case of explicit ACKing,
>         the TLS
>         stack also needs to provide a signal indicating the end of the
>         transmission at each encryption level.
>
>         The downside of the implicit ACKing approach is that the
>         server needs
>         to signal the termination of the Handshake context using a special
>         frame sent using a 1-RTT packet.
>
>         But even taking that into consideration, I think that implicit
>         ACKing
>         is still easier to implement, considering the need for the
>         additional
>         signal in the explicit ACK case that have been described above.
>
>
>         > In any
>         > case, starting as simple as possible would help having the first
>         > implementations and tests.
>         >
>         >
>         > On 5/22/2018 8:26 PM, Subodh Iyengar wrote:
>         >
>         > As an implementor of fizz, I support this design and am
>         willing to implement
>         > this as well.
>         >
>         >
>         > While this is a change in the API that TLS classically
>         exposes, I think this
>         > is the right tradeoff because it helps make things way more
>         explicit which
>         > will prevent several other bugs from happening in the future.
>         >
>         >
>         > Subodh
>         >
>         > ________________________________
>         > From: QUIC <quic-bounces@ietf.org
>         <mailto:quic-bounces@ietf.org>> on behalf of Martin Thomson
>         > <martin.thomson@gmail.com <mailto:martin.thomson@gmail.com>>
>         > Sent: Tuesday, May 22, 2018 8:00:40 PM
>         > To: Ian Swett
>         > Cc: ekr@mozilla.com <mailto:ekr@mozilla.com>; QUIC WG
>         > Subject: Re: Stream0 Design Team Proposal
>         >
>         > First of all, thanks to the design team for the work they
>         have done.  I
>         > haven't digested everything yet, but I think that I have a
>         good sense of
>         > the shape of the proposal.
>         >
>         > Overall, this looks like a workable design.  It's a lot more
>         invasive of
>         > the cryptographic handshake implementation than I had
>         thought people were
>         > willing to stomach originally.  But it's clear that we've
>         run into problems
>         > with the current, more abstract API and this is a fairly
>         natural way to
>         > split TLS.  I've spent a little time thinking about how this
>         might be
>         > implemented and I think that it's not going to be *too*
>         painful.  The proof
>         > will be in the pudding there though.
>         >
>         > In looking at the PR, I really appreciate seeing all the
>         changes together..
>         > BTW, the link above points to the wrong PR, so be careful
>         (it appears to
>         > have the same content, but that's not guaranteed).  The
>         actual PR is here:
>         > https://github.com/quicwg/base-drafts/pull/1377
>         <https://github.com/quicwg/base-drafts/pull/1377>
>         >
>         > I've pushed a branch to the main repo so that you can
>         preview the entire
>         > document set:
>         >
>         https://urldefense.proofpoint.com/v2/url?u=https-3A__quicwg.github.io_base-2Ddrafts_stream0_&d=DwIBaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=h3Ju9EBS7mHtwg-wAyN7fQ&m=_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&s=ususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&e=
>         <https://urldefense.proofpoint.com/v2/url?u=https-3A__quicwg.github.io_base-2Ddrafts_stream0_&d=DwIBaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=h3Ju9EBS7mHtwg-wAyN7fQ&m=_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&s=ususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&e=>
>         >
>         > It seems like there are some core changes here and a bunch
>         of separable or
>         > at least secondary changes.  I'm sure that each one has its own
>         > justification, but that isn't always clear. The following
>         changes seem like
>         > they are separable:
>         >
>         > * The use of separate packet number spaces
>         > * The Retry packet changes (and NEW_TOKEN)
>         > * EMPTY_ACK
>         > * The TLS extension for flow control
>         >
>         > Right now, some of these appear to be entirely gratuitous. 
>         I'd like to get
>         > to the bottom of each before we continue.
>         >
>         > At a minimum, the PR we land first should include just the
>         core changes.
>         > As you say, reviewing a monster PR like this will only make
>         GitHub weep
>         > unicorns, but we might be able to cut this into smaller pieces.
>         >
>         > On Wed, May 23, 2018 at 11:31 AM Ian Swett <ianswett=
>         > 40google.com@dmarc.ietf.org
>         <mailto:40google.com@dmarc.ietf.org>> wrote:
>         >
>         >> Dear QUIC WG,
>         >
>         >
>         >> On behalf of the Stream 0 Design Team, I am pleased to
>         report that we
>         > have consensus on a proposed approach to share with the WG.
>         The DT's
>         > proposal will make QUIC and TLS work closer together and
>         incorporates ideas
>         > from DTLS, but it does not use the DTLS protocol itself.
>         >
>         >
>         >> The DT believes this solves the important open Stream 0
>         issues. The
>         > proposal will be a bit more invasive in TLS, but we believe
>         it is the right
>         > long-term direction and several TLS stacks (BoringSSL,
>         PicoTLS, NSS, and
>         > Mint) are willing and able to do the work necessary.. A
>         number of stacks
>         > are currently working on implementations of this new
>         approach, which we
>         > hope to have in time for the Interim meeting.
>         >
>         >
>         >> A design document describing the overall approach can be
>         found at:
>         >
>         >
>         >
>         https://urldefense.proofpoint.com/v2/url?u=https-3A__docs.google.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8_edit&d=DwIBaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=h3Ju9EBS7mHtwg-wAyN7fQ&m=_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&s=jDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg&e=
>         <https://urldefense.proofpoint.com/v2/url?u=https-3A__docs..google.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8_edit&d=DwIBaQ&c=5VD0RTtNlTh3ycd41b3MUw&r=h3Ju9EBS7mHtwg-wAyN7fQ&m=_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&s=jDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg&e=>
>         >
>         >
>         >> A PR making the changes to the QUIC documents can be found at:
>         >
>         >> https://github.com/quicwg/base-drafts/pull/1377
>         <https://github.com/quicwg/base-drafts/pull/1377>
>         >
>         >
>         >> A few design details did not have clear consensus, but it
>         was felt it
>         > would be better to discuss those in the wider WG than delay
>         the design
>         > team.  A consistent choice was made in the PR and these
>         issues are
>         > mentioned in Appendix B of the design doc.
>         >
>         >
>         >> As always, comments and questions welcome. That said, this
>         is a big PR
>         > and we recognize that some editorial work is going to be
>         needed before
>         > merging. In the interest of letting people follow along, and
>         to keep github
>         > from falling over, we ask people to keep discussion on the
>         mailing list and
>         > refrain from making PR comments.
>         >
>         >
>         >> See you in Kista!
>         >
>         >
>         >> Ian and Eric
>         >
>         >
>
>
>
>         -- 
>         Kazuho Oku
>
>
>


--------------34E66CDE848BDCF5F8673E88
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html; charset=utf-8">
  </head>
  <body text="#000000" bgcolor="#FFFFFF">
    <p>I dislike the EMPTY_ACK because they are "responses to something
      that could not be decrypted". You don't know where the packet came
      from, it could be spoofed. So you have on one hand a possible
      optimization, on the other hand a possible vulnerability, and in
      all cases additional complexity.<br>
    </p>
    <br>
    <div class="moz-cite-prefix">On 5/23/2018 4:27 PM, Jana Iyengar
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CACpbDcckRvyn18qowWbLRT+sX2EGj3_yPtoS2d-h6ypg4dFrVQ@mail.gmail.com">
      <div dir="ltr">
        <div>(Moving more discussions from main thread)</div>
        <div><br>
        </div>
        ---------- Forwarded message ----------<br>
        From:<span> </span><b class="gmail_sendername">Subodh Iyengar</b><span> </span><span
          dir="ltr">&lt;<a href="mailto:subodh@fb.com"
            moz-do-not-send="true">subodh@fb.com</a>&gt;</span><br>
        Date: Wed, May 23, 2018 at 3:37 PM<br>
        Subject: Re: Stream0 Design Team Proposal<br>
        To: Mike Bishop &lt;<a href="mailto:mbishop@evequefou.be"
          moz-do-not-send="true">mbishop@evequefou.be</a>&gt;, Christian
        Huitema &lt;<a href="mailto:huitema@huitema.net"
          moz-do-not-send="true">huitema@huitema.net</a>&gt;, "<a
          href="mailto:quic@ietf.org" moz-do-not-send="true">quic@ietf.org</a>"
        &lt;<a href="mailto:quic@ietf.org" moz-do-not-send="true">quic@ietf.org</a>&gt;<br>
        <br>
        <br>
        <div dir="ltr">
          <div id="gmail-m_-6373418337459262039divtagdefaultwrapper"
            dir="ltr"
style="font-size:12pt;color:rgb(0,0,0);font-family:Calibri,Helvetica,sans-serif">
            <p style="margin-top:0px;margin-bottom:0px">FWIW I see
              EMPTY_ACKs as being very similar to a Duplicate ack. We
              thought about using Duplicate acks as well but we thought
              that EMPTY_ACks would be simpler to implement and be able
              to convey similar information.<br>
            </p>
            <p style="margin-top:0px;margin-bottom:0px"><br>
            </p>
            <p style="margin-top:0px;margin-bottom:0px">Subodh<br>
            </p>
          </div>
          <hr style="display:inline-block;width:1427.78px">
          <div id="gmail-m_-6373418337459262039divRplyFwdMsg" dir="ltr"><font
              style="font-size:11pt" face="Calibri, sans-serif"
              color="#000000"><b>From:</b><span> </span>QUIC &lt;<a
                href="mailto:quic-bounces@ietf.org" target="_blank"
                style="color:rgb(17,85,204)" moz-do-not-send="true">quic-bounces@ietf.org</a>&gt;
              on behalf of Mike Bishop &lt;<a
                href="mailto:mbishop@evequefou.be" target="_blank"
                style="color:rgb(17,85,204)" moz-do-not-send="true">mbishop@evequefou.be</a>&gt;<br>
              <b>Sent:</b><span> </span>Wednesday, May 23, 2018 3:26:35
              PM<br>
              <b>To:</b><span> </span>Christian Huitema;<span> </span><a
                href="mailto:quic@ietf.org" target="_blank"
                style="color:rgb(17,85,204)" moz-do-not-send="true">quic@ietf.org</a><br>
              <b>Subject:</b><span> </span>RE: Stream0 Design Team
              Proposal</font>
            <div> </div>
          </div>
          <div>
            <div class="gmail-h5"
              style="display:block;color:rgb(80,0,80)">
              <div style="background-color:white" lang="EN-US">
                <div class="gmail-m_-6373418337459262039x_WordSection1">
                  <p class="gmail-m_-6373418337459262039x_MsoNormal"
style="color:rgb(80,0,80);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><span
                      style="color:windowtext">Christian, can you expand
                      on why you dislike the EMPTY_ACK?  Being able to
                      say “I’ve received some packets from you, but am
                      unable to process any of them because I’m missing
                      some handshake data” seems like a useful way to
                      short-circuit timeouts on clients.  It also
                      doesn’t commit the server to holding any state –
                      IIUC, a server could form a packet containing an
                      EMPTY_ACK and then discard its internal state
                      until it gets the retransmitted (or delayed)
                      Initial packet.</span></p>
                  <p class="gmail-m_-6373418337459262039x_MsoNormal"
style="color:rgb(80,0,80);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial"><span
                      style="color:windowtext"> </span></p>
                  <div
style="color:rgb(80,0,80);font-family:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initial">
                    <div
style="border-right:none;border-bottom:none;border-left:none;border-top:1pt
                      solid rgb(225,225,225);padding:3pt 0in 0in"><br
                        class="gmail-Apple-interchange-newline">
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
        <br>
        <div class="gmail_extra"><br>
          <div class="gmail_quote">On Wed, May 23, 2018 at 4:25 PM, Jana
            Iyengar <span dir="ltr">&lt;<a
                href="mailto:jri.ietf@gmail.com" target="_blank"
                moz-do-not-send="true">jri.ietf@gmail.com</a>&gt;</span>
            wrote:<br>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div dir="ltr">(Forking this discussion off from the main
                thread.)<br>
                <div class="gmail_extra"><br>
                  <div class="gmail_quote">On Wed, May 23, 2018 at 2:13
                    AM, Kazuho Oku <span dir="ltr">&lt;<a
                        href="mailto:kazuhooku@gmail.com"
                        target="_blank" moz-do-not-send="true">kazuhooku@gmail.com</a>&gt;</span>
                    wrote:<br>
                    <blockquote class="gmail_quote" style="margin:0 0 0
                      .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>2018-05-23
                        14:29 GMT+09:00 Christian Huitema &lt;<a
                          href="mailto:huitema@huitema.net"
                          target="_blank" moz-do-not-send="true">huitema@huitema.net</a>&gt;:<br>
                        &gt; I like the proposal. In particular, I
                        really like the encryption of<br>
                        &gt; handshake packets with the handshake key,
                        as it does close a number of<br>
                        &gt; avenues for attacks. And I like that it
                        solves the "ack promotion" issue<br>
                        &gt; that I was complaining against for some
                        time. Turns out that in the current<br>
                        &gt; draft, it is very hard to contain that
                        problem if you enable client auth.<br>
                        &gt;<br>
                        &gt;<br>
                        &gt; On the other hand, I agree with Martin that
                        a lot of the additions to<br>
                        &gt; transmission recovery should be moved to
                        separate PRs. I am not enthusiastic<br>
                        &gt; with the EMPTY ACK mechanism, or with the
                        proposed "implicit<br>
                        &gt; acknowledgement" of a lower crypto stream
                        by a higher level ack.<br>
                        <br>
                      </span>At the moment I do not have a strong
                      opinion on the Empty ACK mechanism.<br>
                      <br>
                      However, regarding how we close the Initial and
                      Handshake contexts, my<br>
                      preference goes to using implicit ACKs (i.e. use
                      the successful<br>
                      receipt of a packet that is protected under a
                      higher level of<br>
                      encryption key as the signal) rather than
                      explicitly ACKing the last<br>
                      flight of data.<br>
                      <br>
                      As I see, there are two downsides in the Explicit
                      ACKing approach.<br>
                      <br>
                      * Explicit ACKing requires sending two additional
                      packets during the<br>
                      handshake, which means that we would have more AES
                      operations plus<br>
                      somewhere around 60 bytes of overhead on the wire.<br>
                      * Explicit ACKing requires more signaling from the
                      TLS stack. In case<br>
                      of implicit ACKing, the TLS stack need to only
                      provide the AEAD<br>
                      contexts and the messages, whereas in case of
                      explicit ACKing, the TLS<br>
                      stack also needs to provide a signal indicating
                      the end of the<br>
                      transmission at each encryption level.<br>
                      <br>
                      The downside of the implicit ACKing approach is
                      that the server needs<br>
                      to signal the termination of the Handshake context
                      using a special<br>
                      frame sent using a 1-RTT packet.<br>
                      <br>
                      But even taking that into consideration, I think
                      that implicit ACKing<br>
                      is still easier to implement, considering the need
                      for the additional<br>
                      signal in the explicit ACK case that have been
                      described above.<br>
                      <div>
                        <div class="m_-1934665759982005286h5"><br>
                          <br>
                          &gt; In any<br>
                          &gt; case, starting as simple as possible
                          would help having the first<br>
                          &gt; implementations and tests.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt; On 5/22/2018 8:26 PM, Subodh Iyengar
                          wrote:<br>
                          &gt;<br>
                          &gt; As an implementor of fizz, I support this
                          design and am willing to implement<br>
                          &gt; this as well.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt; While this is a change in the API that
                          TLS classically exposes, I think this<br>
                          &gt; is the right tradeoff because it helps
                          make things way more explicit which<br>
                          &gt; will prevent several other bugs from
                          happening in the future.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt; Subodh<br>
                          &gt;<br>
                          &gt; ______________________________<wbr>__<br>
                          &gt; From: QUIC &lt;<a
                            href="mailto:quic-bounces@ietf.org"
                            target="_blank" moz-do-not-send="true">quic-bounces@ietf.org</a>&gt;
                          on behalf of Martin Thomson<br>
                          &gt; &lt;<a
                            href="mailto:martin.thomson@gmail.com"
                            target="_blank" moz-do-not-send="true">martin.thomson@gmail.com</a>&gt;<br>
                          &gt; Sent: Tuesday, May 22, 2018 8:00:40 PM<br>
                          &gt; To: Ian Swett<br>
                          &gt; Cc: <a href="mailto:ekr@mozilla.com"
                            target="_blank" moz-do-not-send="true">ekr@mozilla.com</a>;
                          QUIC WG<br>
                          &gt; Subject: Re: Stream0 Design Team Proposal<br>
                          &gt;<br>
                          &gt; First of all, thanks to the design team
                          for the work they have done.  I<br>
                          &gt; haven't digested everything yet, but I
                          think that I have a good sense of<br>
                          &gt; the shape of the proposal.<br>
                          &gt;<br>
                          &gt; Overall, this looks like a workable
                          design.  It's a lot more invasive of<br>
                          &gt; the cryptographic handshake
                          implementation than I had thought people were<br>
                          &gt; willing to stomach originally.  But it's
                          clear that we've run into problems<br>
                          &gt; with the current, more abstract API and
                          this is a fairly natural way to<br>
                          &gt; split TLS.  I've spent a little time
                          thinking about how this might be<br>
                          &gt; implemented and I think that it's not
                          going to be *too* painful.  The proof<br>
                          &gt; will be in the pudding there though.<br>
                          &gt;<br>
                        </div>
                      </div>
                      &gt; In looking at the PR, I really appreciate
                      seeing all the changes together..<br>
                      <div class="m_-1934665759982005286HOEnZb">
                        <div class="m_-1934665759982005286h5">&gt; BTW,
                          the link above points to the wrong PR, so be
                          careful (it appears to<br>
                          &gt; have the same content, but that's not
                          guaranteed).  The actual PR is here:<br>
                          &gt; <a
                            href="https://github.com/quicwg/base-drafts/pull/1377"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://github.com/quicwg/base<wbr>-drafts/pull/1377</a><br>
                          &gt;<br>
                          &gt; I've pushed a branch to the main repo so
                          that you can preview the entire<br>
                          &gt; document set:<br>
                          &gt; <a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__quicwg.github.io_base-2Ddrafts_stream0_&amp;d=DwIBaQ&amp;c=5VD0RTtNlTh3ycd41b3MUw&amp;r=h3Ju9EBS7mHtwg-wAyN7fQ&amp;m=_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&amp;s=ususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&amp;e="
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://urldefense.proofpoint.<wbr>com/v2/url?u=https-3A__quicwg.<wbr>github.io_base-2Ddrafts_stream<wbr>0_&amp;d=DwIBaQ&amp;c=5VD0RTtNlTh3ycd4<wbr>1b3MUw&amp;r=h3Ju9EBS7mHtwg-<wbr>wAyN7fQ&amp;m=_vGK3zTKFrMOkFihJnPn<wbr>tLYw1T0_NEMiHYSM0Q_u1JA&amp;s=usus<wbr>mtxI3BTaLlBWe_HkQUWRH4sBI0Cggj<wbr>1oWZMBHak&amp;e=</a><br>
                          &gt;<br>
                          &gt; It seems like there are some core changes
                          here and a bunch of separable or<br>
                          &gt; at least secondary changes.  I'm sure
                          that each one has its own<br>
                          &gt; justification, but that isn't always
                          clear. The following changes seem like<br>
                          &gt; they are separable:<br>
                          &gt;<br>
                          &gt; * The use of separate packet number
                          spaces<br>
                          &gt; * The Retry packet changes (and
                          NEW_TOKEN)<br>
                          &gt; * EMPTY_ACK<br>
                          &gt; * The TLS extension for flow control<br>
                          &gt;<br>
                          &gt; Right now, some of these appear to be
                          entirely gratuitous.  I'd like to get<br>
                          &gt; to the bottom of each before we continue.<br>
                          &gt;<br>
                          &gt; At a minimum, the PR we land first should
                          include just the core changes.<br>
                          &gt; As you say, reviewing a monster PR like
                          this will only make GitHub weep<br>
                          &gt; unicorns, but we might be able to cut
                          this into smaller pieces.<br>
                          &gt;<br>
                          &gt; On Wed, May 23, 2018 at 11:31 AM Ian
                          Swett &lt;ianswett=<br>
                          &gt; <a
                            href="mailto:40google.com@dmarc.ietf.org"
                            target="_blank" moz-do-not-send="true">40google.com@dmarc.ietf.org</a>&gt;
                          wrote:<br>
                          &gt;<br>
                          &gt;&gt; Dear QUIC WG,<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; On behalf of the Stream 0 Design
                          Team, I am pleased to report that we<br>
                          &gt; have consensus on a proposed approach to
                          share with the WG. The DT's<br>
                          &gt; proposal will make QUIC and TLS work
                          closer together and incorporates ideas<br>
                          &gt; from DTLS, but it does not use the DTLS
                          protocol itself.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; The DT believes this solves the
                          important open Stream 0 issues. The<br>
                          &gt; proposal will be a bit more invasive in
                          TLS, but we believe it is the right<br>
                          &gt; long-term direction and several TLS
                          stacks (BoringSSL, PicoTLS, NSS, and<br>
                          &gt; Mint) are willing and able to do the work
                          necessary.. A number of stacks<br>
                          &gt; are currently working on implementations
                          of this new approach, which we<br>
                          &gt; hope to have in time for the Interim
                          meeting.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; A design document describing the
                          overall approach can be found at:<br>
                          &gt;<br>
                          &gt;<br>
                          &gt; <a
href="https://urldefense.proofpoint.com/v2/url?u=https-3A__docs..google.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8_edit&amp;d=DwIBaQ&amp;c=5VD0RTtNlTh3ycd41b3MUw&amp;r=h3Ju9EBS7mHtwg-wAyN7fQ&amp;m=_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&amp;s=jDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg&amp;e="
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://urldefense.proofpoint.<wbr>com/v2/url?u=https-3A__docs.go<wbr>ogle.com_document_d_1fRsJqPinJ<wbr>l8N3b-2DbflDRV6auojfJLkxddT93j<wbr>6SwHY8_edit&amp;d=DwIBaQ&amp;c=5VD0RTt<wbr>NlTh3ycd41b3MUw&amp;r=h3Ju9EBS7mHt<wbr>wg-wAyN7fQ&amp;m=_vGK3zTKFrMOkFihJ<wbr>nPntLYw1T0_NEMiHYSM0Q_u1JA&amp;s=j<wbr>DNnz34hmWvLSQnHkSnYdihW-jG-0xZ<wbr>-YYqKq30wVGg&amp;e=</a><br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; A PR making the changes to the QUIC
                          documents can be found at:<br>
                          &gt;<br>
                          &gt;&gt; <a
                            href="https://github.com/quicwg/base-drafts/pull/1377"
                            rel="noreferrer" target="_blank"
                            moz-do-not-send="true">https://github.com/quicwg/base<wbr>-drafts/pull/1377</a><br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; A few design details did not have
                          clear consensus, but it was felt it<br>
                          &gt; would be better to discuss those in the
                          wider WG than delay the design<br>
                          &gt; team.  A consistent choice was made in
                          the PR and these issues are<br>
                          &gt; mentioned in Appendix B of the design
                          doc.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; As always, comments and questions
                          welcome. That said, this is a big PR<br>
                          &gt; and we recognize that some editorial work
                          is going to be needed before<br>
                          &gt; merging. In the interest of letting
                          people follow along, and to keep github<br>
                          &gt; from falling over, we ask people to keep
                          discussion on the mailing list and<br>
                          &gt; refrain from making PR comments.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; See you in Kista!<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; Ian and Eric<br>
                          &gt;<br>
                          &gt;<br>
                          <br>
                          <br>
                          <span class="HOEnZb"><font color="#888888">
                              <br>
                            </font></span></div>
                      </div>
                      <span class="HOEnZb"><font color="#888888"><span
                            class="m_-1934665759982005286HOEnZb"><font
                              color="#888888">-- <br>
                              Kazuho Oku<br>
                              <br>
                            </font></span></font></span></blockquote>
                  </div>
                  <br>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
  </body>
</html>

--------------34E66CDE848BDCF5F8673E88--


From nobody Wed May 23 19:46:24 2018
Return-Path: <ekr@rtfm.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 753A312D88D for <quic@ietfa.amsl.com>; Wed, 23 May 2018 19:46:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 DiB1_83ZIC7b for <quic@ietfa.amsl.com>; Wed, 23 May 2018 19:46:18 -0700 (PDT)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8344F126CC7 for <quic@ietf.org>; Wed, 23 May 2018 19:46:18 -0700 (PDT)
Received: by mail-oi0-x22e.google.com with SMTP id t27-v6so111419oij.9 for <quic@ietf.org>; Wed, 23 May 2018 19:46:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=5KYaJo/MZLMvagDqpNP6lfXSlobZDso8XHhiOatxmmU=; b=P/QyOthpfb11MK4G5r3oMOQKZYhdoO1Qv58DtoMdgv2Oqp7OntGbCSbCWFvvENqDqC yPIfm9pV8yseNQkG+CRDWfIxrsj3DW+uLAg3oqlfbzHwiFtwUDAiIlYKsXqAsJgOzKYv czLjfSyhZdLyzH3QWwkW7gRTyuwkJvLx2RHb9BmY71JwH+xmVYEsMxtC4YJ1ReVW3a5t 2aHE3xOiGayKq9uvwrg/J1/xWfvkyfvJtSzGqRswCy1ZvqekzVRZfkEhyjX2J15JZFDF yPy2VHVCvqf7UGnLYfHzz93hX200BKQBH7/mWqLNOdQf+ZaoIdK1ddgxtHMBvStGb/RS eRjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=5KYaJo/MZLMvagDqpNP6lfXSlobZDso8XHhiOatxmmU=; b=KwGB5ozlSEpZ+Ej1u2DzRrxwgfLnTBdLnKHmxu62jIGOjxqUUNykVtMB22khdLaT+z kxWicgqw/+oa2EsY57y7I+TAUDcadAE1RXUDW/7/x3qd10p1lCGZBNR1mFG+pZGBiV6J sgT0lgNLP8McNVgSkSZDF2QaP1cznj3rOQ+9cZ0fAbyW4DfRxyz1E8m9Ga4aLIfgSjKE 7uTTtfdABWl6jGscoRLTmjWvTpnATR7bm4mSyu1mN5z8D6hFIWSOxEag4xk11T2gju6a 6htQ3I2T8iz/OAcubgkYIu2k5/HBX32Zq2CtWdS6yKue6qO/Cr7UsVpRaWEoAurgc42t WjYw==
X-Gm-Message-State: ALKqPwcyB5B2frKYVHj04BYxSDUZHtJpaY5ptyMIKCcVm1m1vV3d+Knf uTfju0cTG2cmgCHtQVtE7BVTwjrEEj5q0Nyv5fIhLQ==
X-Google-Smtp-Source: AB8JxZoI4C1kTtDib/Ih4MBXfYgBLoCe+3F0dPzPCa0wDUgmpyKPHFYlSvkIKj7dFgFN0jOYcCLS7B3VSXCEjFT5mdU=
X-Received: by 2002:aca:4c11:: with SMTP id z17-v6mr3084133oia.174.1527129977780;  Wed, 23 May 2018 19:46:17 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:ac9:66:0:0:0:0:0 with HTTP; Wed, 23 May 2018 19:45:37 -0700 (PDT)
In-Reply-To: <6d80b771-ba07-cab7-fa86-d4e31d56b919@huitema.net>
References: <CACpbDcckRvyn18qowWbLRT+sX2EGj3_yPtoS2d-h6ypg4dFrVQ@mail.gmail.com> <6d80b771-ba07-cab7-fa86-d4e31d56b919@huitema.net>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 23 May 2018 19:45:37 -0700
Message-ID: <CABcZeBPtjbMVL2RQMyLZJg_QyHcgA5E_g8SAgoHUqjpLrJRA4g@mail.gmail.com>
Subject: Re: Stream0 Proposal: EMPTY_ACK
To: Christian Huitema <huitema@huitema.net>
Cc: Jana Iyengar <jri.ietf@gmail.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000da1481056ceaa7eb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/J-Fwp3jEHnHSAECUNGYtbIrunZs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 02:46:23 -0000

--000000000000da1481056ceaa7eb
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, May 23, 2018 at 7:10 PM, Christian Huitema <huitema@huitema.net>
wrote:

> I dislike the EMPTY_ACK because they are "responses to something that
> could not be decrypted". You don't know where the packet came from, it
> could be spoofed. So you have on one hand a possible optimization, on the
> other hand a possible vulnerability, and in all cases additional complexi=
ty.
>
What's the vulnerability? Anything more than a spurious retransmit?

-Ekr


> On 5/23/2018 4:27 PM, Jana Iyengar wrote:
>
> (Moving more discussions from main thread)
>
> ---------- Forwarded message ----------
> From: Subodh Iyengar <subodh@fb.com>
> Date: Wed, May 23, 2018 at 3:37 PM
> Subject: Re: Stream0 Design Team Proposal
> To: Mike Bishop <mbishop@evequefou.be>, Christian Huitema <
> huitema@huitema.net>, "quic@ietf.org" <quic@ietf.org>
>
>
> FWIW I see EMPTY_ACKs as being very similar to a Duplicate ack. We though=
t
> about using Duplicate acks as well but we thought that EMPTY_ACks would b=
e
> simpler to implement and be able to convey similar information.
>
>
> Subodh
> ------------------------------
> *From:* QUIC <quic-bounces@ietf.org> on behalf of Mike Bishop <
> mbishop@evequefou.be>
> *Sent:* Wednesday, May 23, 2018 3:26:35 PM
> *To:* Christian Huitema; quic@ietf.org
> *Subject:* RE: Stream0 Design Team Proposal
>
>
> Christian, can you expand on why you dislike the EMPTY_ACK?  Being able t=
o
> say =E2=80=9CI=E2=80=99ve received some packets from you, but am unable t=
o process any of
> them because I=E2=80=99m missing some handshake data=E2=80=9D seems like =
a useful way to
> short-circuit timeouts on clients.  It also doesn=E2=80=99t commit the se=
rver to
> holding any state =E2=80=93 IIUC, a server could form a packet containing=
 an
> EMPTY_ACK and then discard its internal state until it gets the
> retransmitted (or delayed) Initial packet.
>
>
>
>
>
> On Wed, May 23, 2018 at 4:25 PM, Jana Iyengar <jri.ietf@gmail.com> wrote:
>
>> (Forking this discussion off from the main thread.)
>>
>> On Wed, May 23, 2018 at 2:13 AM, Kazuho Oku <kazuhooku@gmail.com> wrote:
>>
>>> 2018-05-23 14:29 GMT+09:00 Christian Huitema <huitema@huitema.net>:
>>> > I like the proposal. In particular, I really like the encryption of
>>> > handshake packets with the handshake key, as it does close a number o=
f
>>> > avenues for attacks. And I like that it solves the "ack promotion"
>>> issue
>>> > that I was complaining against for some time. Turns out that in the
>>> current
>>> > draft, it is very hard to contain that problem if you enable client
>>> auth.
>>> >
>>> >
>>> > On the other hand, I agree with Martin that a lot of the additions to
>>> > transmission recovery should be moved to separate PRs. I am not
>>> enthusiastic
>>> > with the EMPTY ACK mechanism, or with the proposed "implicit
>>> > acknowledgement" of a lower crypto stream by a higher level ack.
>>>
>>> At the moment I do not have a strong opinion on the Empty ACK mechanism=
.
>>>
>>> However, regarding how we close the Initial and Handshake contexts, my
>>> preference goes to using implicit ACKs (i.e. use the successful
>>> receipt of a packet that is protected under a higher level of
>>> encryption key as the signal) rather than explicitly ACKing the last
>>> flight of data.
>>>
>>> As I see, there are two downsides in the Explicit ACKing approach.
>>>
>>> * Explicit ACKing requires sending two additional packets during the
>>> handshake, which means that we would have more AES operations plus
>>> somewhere around 60 bytes of overhead on the wire.
>>> * Explicit ACKing requires more signaling from the TLS stack. In case
>>> of implicit ACKing, the TLS stack need to only provide the AEAD
>>> contexts and the messages, whereas in case of explicit ACKing, the TLS
>>> stack also needs to provide a signal indicating the end of the
>>> transmission at each encryption level.
>>>
>>> The downside of the implicit ACKing approach is that the server needs
>>> to signal the termination of the Handshake context using a special
>>> frame sent using a 1-RTT packet.
>>>
>>> But even taking that into consideration, I think that implicit ACKing
>>> is still easier to implement, considering the need for the additional
>>> signal in the explicit ACK case that have been described above.
>>>
>>>
>>> > In any
>>> > case, starting as simple as possible would help having the first
>>> > implementations and tests.
>>> >
>>> >
>>> > On 5/22/2018 8:26 PM, Subodh Iyengar wrote:
>>> >
>>> > As an implementor of fizz, I support this design and am willing to
>>> implement
>>> > this as well.
>>> >
>>> >
>>> > While this is a change in the API that TLS classically exposes, I
>>> think this
>>> > is the right tradeoff because it helps make things way more explicit
>>> which
>>> > will prevent several other bugs from happening in the future.
>>> >
>>> >
>>> > Subodh
>>> >
>>> > ________________________________
>>> > From: QUIC <quic-bounces@ietf.org> on behalf of Martin Thomson
>>> > <martin.thomson@gmail.com>
>>> > Sent: Tuesday, May 22, 2018 8:00:40 PM
>>> > To: Ian Swett
>>> > Cc: ekr@mozilla.com; QUIC WG
>>> > Subject: Re: Stream0 Design Team Proposal
>>> >
>>> > First of all, thanks to the design team for the work they have done. =
 I
>>> > haven't digested everything yet, but I think that I have a good sense
>>> of
>>> > the shape of the proposal.
>>> >
>>> > Overall, this looks like a workable design.  It's a lot more invasive
>>> of
>>> > the cryptographic handshake implementation than I had thought people
>>> were
>>> > willing to stomach originally.  But it's clear that we've run into
>>> problems
>>> > with the current, more abstract API and this is a fairly natural way =
to
>>> > split TLS.  I've spent a little time thinking about how this might be
>>> > implemented and I think that it's not going to be *too* painful.  The
>>> proof
>>> > will be in the pudding there though.
>>> >
>>> > In looking at the PR, I really appreciate seeing all the changes
>>> together..
>>> > BTW, the link above points to the wrong PR, so be careful (it appears
>>> to
>>> > have the same content, but that's not guaranteed).  The actual PR is
>>> here:
>>> > https://github.com/quicwg/base-drafts/pull/1377
>>> >
>>> > I've pushed a branch to the main repo so that you can preview the
>>> entire
>>> > document set:
>>> > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__quicwg.
>>> github.io_base-2Ddrafts_stream0_&d=3DDwIBaQ&c=3D5VD0RTtNlTh3ycd4
>>> 1b3MUw&r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&m=3D_vGK3zTKFrMOkFihJnPntLYw1T
>>> 0_NEMiHYSM0Q_u1JA&s=3DususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&e=3D
>>> >
>>> > It seems like there are some core changes here and a bunch of
>>> separable or
>>> > at least secondary changes.  I'm sure that each one has its own
>>> > justification, but that isn't always clear. The following changes see=
m
>>> like
>>> > they are separable:
>>> >
>>> > * The use of separate packet number spaces
>>> > * The Retry packet changes (and NEW_TOKEN)
>>> > * EMPTY_ACK
>>> > * The TLS extension for flow control
>>> >
>>> > Right now, some of these appear to be entirely gratuitous.  I'd like
>>> to get
>>> > to the bottom of each before we continue.
>>> >
>>> > At a minimum, the PR we land first should include just the core
>>> changes.
>>> > As you say, reviewing a monster PR like this will only make GitHub we=
ep
>>> > unicorns, but we might be able to cut this into smaller pieces.
>>> >
>>> > On Wed, May 23, 2018 at 11:31 AM Ian Swett <ianswett=3D
>>> > 40google.com@dmarc.ietf.org> wrote:
>>> >
>>> >> Dear QUIC WG,
>>> >
>>> >
>>> >> On behalf of the Stream 0 Design Team, I am pleased to report that w=
e
>>> > have consensus on a proposed approach to share with the WG. The DT's
>>> > proposal will make QUIC and TLS work closer together and incorporates
>>> ideas
>>> > from DTLS, but it does not use the DTLS protocol itself.
>>> >
>>> >
>>> >> The DT believes this solves the important open Stream 0 issues. The
>>> > proposal will be a bit more invasive in TLS, but we believe it is the
>>> right
>>> > long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS,
>>> and
>>> > Mint) are willing and able to do the work necessary.. A number of
>>> stacks
>>> > are currently working on implementations of this new approach, which =
we
>>> > hope to have in time for the Interim meeting.
>>> >
>>> >
>>> >> A design document describing the overall approach can be found at:
>>> >
>>> >
>>> > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__docs.go
>>> ogle.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j
>>> 6SwHY8_edit&d=3DDwIBaQ&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3Dh3Ju9EBS7mHt
>>> wg-wAyN7fQ&m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&s=3Dj
>>> DNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg&e=3D
>>> <https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__docs..google.co=
m_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8_edit&d=3DDwIBaQ=
&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&m=3D_vGK3zTKFrMOkFih=
JnPntLYw1T0_NEMiHYSM0Q_u1JA&s=3DjDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg=
&e=3D>
>>> >
>>> >
>>> >> A PR making the changes to the QUIC documents can be found at:
>>> >
>>> >> https://github.com/quicwg/base-drafts/pull/1377
>>> >
>>> >
>>> >> A few design details did not have clear consensus, but it was felt i=
t
>>> > would be better to discuss those in the wider WG than delay the desig=
n
>>> > team.  A consistent choice was made in the PR and these issues are
>>> > mentioned in Appendix B of the design doc.
>>> >
>>> >
>>> >> As always, comments and questions welcome. That said, this is a big =
PR
>>> > and we recognize that some editorial work is going to be needed befor=
e
>>> > merging. In the interest of letting people follow along, and to keep
>>> github
>>> > from falling over, we ask people to keep discussion on the mailing
>>> list and
>>> > refrain from making PR comments.
>>> >
>>> >
>>> >> See you in Kista!
>>> >
>>> >
>>> >> Ian and Eric
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> Kazuho Oku
>>>
>>>
>>
>
>

--000000000000da1481056ceaa7eb
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Wed, May 23, 2018 at 7:10 PM, Christian Huitema <span dir=3D"ltr">&l=
t;<a href=3D"mailto:huitema@huitema.net" target=3D"_blank">huitema@huitema.=
net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <p>I dislike the EMPTY_ACK because they are &quot;responses to somethin=
g
      that could not be decrypted&quot;. You don&#39;t know where the packe=
t came
      from, it could be spoofed. So you have on one hand a possible
      optimization, on the other hand a possible vulnerability, and in
      all cases additional complexity.<br></p></div></blockquote><div>What&=
#39;s the vulnerability? Anything more than a spurious retransmit?<br></div=
><div><br></div><div>-Ekr</div><div><br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
"><div text=3D"#000000" bgcolor=3D"#FFFFFF"><p>
    </p><div><div class=3D"h5">
    <br>
    <div class=3D"m_2322101816431292516moz-cite-prefix">On 5/23/2018 4:27 P=
M, Jana Iyengar
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div>(Moving more discussions from main thread)</div>
        <div><br>
        </div>
        ---------- Forwarded message ----------<br>
        From:<span>=C2=A0</span><b class=3D"gmail_sendername">Subodh Iyenga=
r</b><span>=C2=A0</span><span dir=3D"ltr">&lt;<a href=3D"mailto:subodh@fb.c=
om" target=3D"_blank">subodh@fb.com</a>&gt;</span><br>
        Date: Wed, May 23, 2018 at 3:37 PM<br>
        Subject: Re: Stream0 Design Team Proposal<br>
        To: Mike Bishop &lt;<a href=3D"mailto:mbishop@evequefou.be" target=
=3D"_blank">mbishop@evequefou.be</a>&gt;, Christian
        Huitema &lt;<a href=3D"mailto:huitema@huitema.net" target=3D"_blank=
">huitema@huitema.net</a>&gt;, &quot;<a href=3D"mailto:quic@ietf.org" targe=
t=3D"_blank">quic@ietf.org</a>&quot;
        &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic@ietf.or=
g</a>&gt;<br>
        <br>
        <br>
        <div dir=3D"ltr">
          <div id=3D"m_2322101816431292516gmail-m_-6373418337459262039divta=
gdefaultwrapper" dir=3D"ltr" style=3D"font-size:12pt;color:rgb(0,0,0);font-=
family:Calibri,Helvetica,sans-serif">
            <p style=3D"margin-top:0px;margin-bottom:0px">FWIW I see
              EMPTY_ACKs as being very similar to a Duplicate ack. We
              thought about using Duplicate acks as well but we thought
              that EMPTY_ACks would be simpler to implement and be able
              to convey similar=C2=A0information.<br>
            </p>
            <p style=3D"margin-top:0px;margin-bottom:0px"><br>
            </p>
            <p style=3D"margin-top:0px;margin-bottom:0px">Subodh<br>
            </p>
          </div>
          <hr style=3D"display:inline-block;width:1427.78px">
          <div id=3D"m_2322101816431292516gmail-m_-6373418337459262039divRp=
lyFwdMsg" dir=3D"ltr"><font style=3D"font-size:11pt" face=3D"Calibri, sans-=
serif" color=3D"#000000"><b>From:</b><span>=C2=A0</span>QUIC &lt;<a href=3D=
"mailto:quic-bounces@ietf.org" style=3D"color:rgb(17,85,204)" target=3D"_bl=
ank">quic-bounces@ietf.org</a>&gt;
              on behalf of Mike Bishop &lt;<a href=3D"mailto:mbishop@eveque=
fou.be" style=3D"color:rgb(17,85,204)" target=3D"_blank">mbishop@evequefou.=
be</a>&gt;<br>
              <b>Sent:</b><span>=C2=A0</span>Wednesday, May 23, 2018 3:26:3=
5
              PM<br>
              <b>To:</b><span>=C2=A0</span>Christian Huitema;<span>=C2=A0</=
span><a href=3D"mailto:quic@ietf.org" style=3D"color:rgb(17,85,204)" target=
=3D"_blank">quic@ietf.org</a><br>
              <b>Subject:</b><span>=C2=A0</span>RE: Stream0 Design Team
              Proposal</font>
            <div>=C2=A0</div>
          </div>
          <div>
            <div class=3D"m_2322101816431292516gmail-h5" style=3D"display:b=
lock;color:rgb(80,0,80)">
              <div style=3D"background-color:white" lang=3D"EN-US">
                <div class=3D"m_2322101816431292516gmail-m_-637341833745926=
2039x_WordSection1">
                  <p class=3D"m_2322101816431292516gmail-m_-637341833745926=
2039x_MsoNormal" style=3D"color:rgb(80,0,80);font-family:arial,sans-serif;f=
ont-size:small;font-style:normal;font-variant-ligatures:normal;font-variant=
-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-in=
dent:0px;text-transform:none;white-space:normal;word-spacing:0px;background=
-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color=
:initial"><span style=3D"color:windowtext">Christian, can you expand
                      on why you dislike the EMPTY_ACK?=C2=A0 Being able to
                      say =E2=80=9CI=E2=80=99ve received some packets from =
you, but am
                      unable to process any of them because I=E2=80=99m mis=
sing
                      some handshake data=E2=80=9D seems like a useful way =
to
                      short-circuit timeouts on clients.=C2=A0 It also
                      doesn=E2=80=99t commit the server to holding any stat=
e =E2=80=93
                      IIUC, a server could form a packet containing an
                      EMPTY_ACK and then discard its internal state
                      until it gets the retransmitted (or delayed)
                      Initial packet.</span></p>
                  <p class=3D"m_2322101816431292516gmail-m_-637341833745926=
2039x_MsoNormal" style=3D"color:rgb(80,0,80);font-family:arial,sans-serif;f=
ont-size:small;font-style:normal;font-variant-ligatures:normal;font-variant=
-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-in=
dent:0px;text-transform:none;white-space:normal;word-spacing:0px;background=
-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-color=
:initial"><span style=3D"color:windowtext">=C2=A0</span></p>
                  <div style=3D"color:rgb(80,0,80);font-family:arial,sans-s=
erif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-v=
ariant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;t=
ext-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;back=
ground-color:rgb(255,255,255);text-decoration-style:initial;text-decoration=
-color:initial">
                    <div style=3D"border-right:none;border-bottom:none;bord=
er-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in"><br=
 class=3D"m_2322101816431292516gmail-Apple-interchange-newline">
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
        <br>
        <div class=3D"gmail_extra"><br>
          <div class=3D"gmail_quote">On Wed, May 23, 2018 at 4:25 PM, Jana
            Iyengar <span dir=3D"ltr">&lt;<a href=3D"mailto:jri.ietf@gmail.=
com" target=3D"_blank">jri.ietf@gmail.com</a>&gt;</span>
            wrote:<br>
            <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">
              <div dir=3D"ltr">(Forking this discussion off from the main
                thread.)<br>
                <div class=3D"gmail_extra"><br>
                  <div class=3D"gmail_quote">On Wed, May 23, 2018 at 2:13
                    AM, Kazuho Oku <span dir=3D"ltr">&lt;<a href=3D"mailto:=
kazuhooku@gmail.com" target=3D"_blank">kazuhooku@gmail.com</a>&gt;</span>
                    wrote:<br>
                    <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>2018-05-23
                        14:29 GMT+09:00 Christian Huitema &lt;<a href=3D"ma=
ilto:huitema@huitema.net" target=3D"_blank">huitema@huitema.net</a>&gt;:<br=
>
                        &gt; I like the proposal. In particular, I
                        really like the encryption of<br>
                        &gt; handshake packets with the handshake key,
                        as it does close a number of<br>
                        &gt; avenues for attacks. And I like that it
                        solves the &quot;ack promotion&quot; issue<br>
                        &gt; that I was complaining against for some
                        time. Turns out that in the current<br>
                        &gt; draft, it is very hard to contain that
                        problem if you enable client auth.<br>
                        &gt;<br>
                        &gt;<br>
                        &gt; On the other hand, I agree with Martin that
                        a lot of the additions to<br>
                        &gt; transmission recovery should be moved to
                        separate PRs. I am not enthusiastic<br>
                        &gt; with the EMPTY ACK mechanism, or with the
                        proposed &quot;implicit<br>
                        &gt; acknowledgement&quot; of a lower crypto stream
                        by a higher level ack.<br>
                        <br>
                      </span>At the moment I do not have a strong
                      opinion on the Empty ACK mechanism.<br>
                      <br>
                      However, regarding how we close the Initial and
                      Handshake contexts, my<br>
                      preference goes to using implicit ACKs (i.e. use
                      the successful<br>
                      receipt of a packet that is protected under a
                      higher level of<br>
                      encryption key as the signal) rather than
                      explicitly ACKing the last<br>
                      flight of data.<br>
                      <br>
                      As I see, there are two downsides in the Explicit
                      ACKing approach.<br>
                      <br>
                      * Explicit ACKing requires sending two additional
                      packets during the<br>
                      handshake, which means that we would have more AES
                      operations plus<br>
                      somewhere around 60 bytes of overhead on the wire.<br=
>
                      * Explicit ACKing requires more signaling from the
                      TLS stack. In case<br>
                      of implicit ACKing, the TLS stack need to only
                      provide the AEAD<br>
                      contexts and the messages, whereas in case of
                      explicit ACKing, the TLS<br>
                      stack also needs to provide a signal indicating
                      the end of the<br>
                      transmission at each encryption level.<br>
                      <br>
                      The downside of the implicit ACKing approach is
                      that the server needs<br>
                      to signal the termination of the Handshake context
                      using a special<br>
                      frame sent using a 1-RTT packet.<br>
                      <br>
                      But even taking that into consideration, I think
                      that implicit ACKing<br>
                      is still easier to implement, considering the need
                      for the additional<br>
                      signal in the explicit ACK case that have been
                      described above.<br>
                      <div>
                        <div class=3D"m_2322101816431292516m_-1934665759982=
005286h5"><br>
                          <br>
                          &gt; In any<br>
                          &gt; case, starting as simple as possible
                          would help having the first<br>
                          &gt; implementations and tests.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt; On 5/22/2018 8:26 PM, Subodh Iyengar
                          wrote:<br>
                          &gt;<br>
                          &gt; As an implementor of fizz, I support this
                          design and am willing to implement<br>
                          &gt; this as well.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt; While this is a change in the API that
                          TLS classically exposes, I think this<br>
                          &gt; is the right tradeoff because it helps
                          make things way more explicit which<br>
                          &gt; will prevent several other bugs from
                          happening in the future.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt; Subodh<br>
                          &gt;<br>
                          &gt; ______________________________<wbr>__<br>
                          &gt; From: QUIC &lt;<a href=3D"mailto:quic-bounce=
s@ietf.org" target=3D"_blank">quic-bounces@ietf.org</a>&gt;
                          on behalf of Martin Thomson<br>
                          &gt; &lt;<a href=3D"mailto:martin.thomson@gmail.c=
om" target=3D"_blank">martin.thomson@gmail.com</a>&gt;<br>
                          &gt; Sent: Tuesday, May 22, 2018 8:00:40 PM<br>
                          &gt; To: Ian Swett<br>
                          &gt; Cc: <a href=3D"mailto:ekr@mozilla.com" targe=
t=3D"_blank">ekr@mozilla.com</a>;
                          QUIC WG<br>
                          &gt; Subject: Re: Stream0 Design Team Proposal<br=
>
                          &gt;<br>
                          &gt; First of all, thanks to the design team
                          for the work they have done.=C2=A0 I<br>
                          &gt; haven&#39;t digested everything yet, but I
                          think that I have a good sense of<br>
                          &gt; the shape of the proposal.<br>
                          &gt;<br>
                          &gt; Overall, this looks like a workable
                          design.=C2=A0 It&#39;s a lot more invasive of<br>
                          &gt; the cryptographic handshake
                          implementation than I had thought people were<br>
                          &gt; willing to stomach originally.=C2=A0 But it&=
#39;s
                          clear that we&#39;ve run into problems<br>
                          &gt; with the current, more abstract API and
                          this is a fairly natural way to<br>
                          &gt; split TLS.=C2=A0 I&#39;ve spent a little tim=
e
                          thinking about how this might be<br>
                          &gt; implemented and I think that it&#39;s not
                          going to be *too* painful.=C2=A0 The proof<br>
                          &gt; will be in the pudding there though.<br>
                          &gt;<br>
                        </div>
                      </div>
                      &gt; In looking at the PR, I really appreciate
                      seeing all the changes together..<br>
                      <div class=3D"m_2322101816431292516m_-193466575998200=
5286HOEnZb">
                        <div class=3D"m_2322101816431292516m_-1934665759982=
005286h5">&gt; BTW,
                          the link above points to the wrong PR, so be
                          careful (it appears to<br>
                          &gt; have the same content, but that&#39;s not
                          guaranteed).=C2=A0 The actual PR is here:<br>
                          &gt; <a href=3D"https://github.com/quicwg/base-dr=
afts/pull/1377" rel=3D"noreferrer" target=3D"_blank">https://github.com/qui=
cwg/base<wbr>-drafts/pull/1377</a><br>
                          &gt;<br>
                          &gt; I&#39;ve pushed a branch to the main repo so
                          that you can preview the entire<br>
                          &gt; document set:<br>
                          &gt; <a href=3D"https://urldefense.proofpoint.com=
/v2/url?u=3Dhttps-3A__quicwg.github.io_base-2Ddrafts_stream0_&amp;d=3DDwIBa=
Q&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&amp;m=3D_vG=
K3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&amp;s=3DususmtxI3BTaLlBWe_HkQUWRH4=
sBI0Cggj1oWZMBHak&amp;e=3D" rel=3D"noreferrer" target=3D"_blank">https://ur=
ldefense.proofpoint.<wbr>com/v2/url?u=3Dhttps-3A__quicwg.<wbr>github.io_bas=
e-2Ddrafts_stream<wbr>0_&amp;d=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd4<wbr>1b3MUw=
&amp;r=3Dh3Ju9EBS7mHtwg-wAyN7f<wbr>Q&amp;m=3D_vGK3zTKFrMOkFihJnPntLYw1T<wbr=
>0_NEMiHYSM0Q_u1JA&amp;s=3DususmtxI3B<wbr>TaLlBWe_HkQUWRH4sBI0Cggj1oWZMB<wb=
r>Hak&amp;e=3D</a><br>
                          &gt;<br>
                          &gt; It seems like there are some core changes
                          here and a bunch of separable or<br>
                          &gt; at least secondary changes.=C2=A0 I&#39;m su=
re
                          that each one has its own<br>
                          &gt; justification, but that isn&#39;t always
                          clear. The following changes seem like<br>
                          &gt; they are separable:<br>
                          &gt;<br>
                          &gt; * The use of separate packet number
                          spaces<br>
                          &gt; * The Retry packet changes (and
                          NEW_TOKEN)<br>
                          &gt; * EMPTY_ACK<br>
                          &gt; * The TLS extension for flow control<br>
                          &gt;<br>
                          &gt; Right now, some of these appear to be
                          entirely gratuitous.=C2=A0 I&#39;d like to get<br=
>
                          &gt; to the bottom of each before we continue.<br=
>
                          &gt;<br>
                          &gt; At a minimum, the PR we land first should
                          include just the core changes.<br>
                          &gt; As you say, reviewing a monster PR like
                          this will only make GitHub weep<br>
                          &gt; unicorns, but we might be able to cut
                          this into smaller pieces.<br>
                          &gt;<br>
                          &gt; On Wed, May 23, 2018 at 11:31 AM Ian
                          Swett &lt;ianswett=3D<br>
                          &gt; <a href=3D"mailto:40google.com@dmarc.ietf.or=
g" target=3D"_blank">40google.com@dmarc.ietf.org</a>&gt;
                          wrote:<br>
                          &gt;<br>
                          &gt;&gt; Dear QUIC WG,<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; On behalf of the Stream 0 Design
                          Team, I am pleased to report that we<br>
                          &gt; have consensus on a proposed approach to
                          share with the WG. The DT&#39;s<br>
                          &gt; proposal will make QUIC and TLS work
                          closer together and incorporates ideas<br>
                          &gt; from DTLS, but it does not use the DTLS
                          protocol itself.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; The DT believes this solves the
                          important open Stream 0 issues. The<br>
                          &gt; proposal will be a bit more invasive in
                          TLS, but we believe it is the right<br>
                          &gt; long-term direction and several TLS
                          stacks (BoringSSL, PicoTLS, NSS, and<br>
                          &gt; Mint) are willing and able to do the work
                          necessary.. A number of stacks<br>
                          &gt; are currently working on implementations
                          of this new approach, which we<br>
                          &gt; hope to have in time for the Interim
                          meeting.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; A design document describing the
                          overall approach can be found at:<br>
                          &gt;<br>
                          &gt;<br>
                          &gt; <a href=3D"https://urldefense.proofpoint.com=
/v2/url?u=3Dhttps-3A__docs..google.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6=
auojfJLkxddT93j6SwHY8_edit&amp;d=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&am=
p;r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&amp;m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q=
_u1JA&amp;s=3DjDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg&amp;e=3D" rel=3D"=
noreferrer" target=3D"_blank">https://urldefense.proofpoint.<wbr>com/v2/url=
?u=3Dhttps-3A__docs.go<wbr>ogle.com_document_d_1fRsJqPinJ<wbr>l8N3b-2DbflDR=
V6auojfJLkxddT93j<wbr>6SwHY8_edit&amp;d=3DDwIBaQ&amp;c=3D5VD0RTt<wbr>NlTh3y=
cd41b3MUw&amp;r=3Dh3Ju9EBS7mHt<wbr>wg-wAyN7fQ&amp;m=3D_vGK3zTKFrMOkFihJ<wbr=
>nPntLYw1T0_NEMiHYSM0Q_u1JA&amp;s=3Dj<wbr>DNnz34hmWvLSQnHkSnYdihW-jG-0xZ<wb=
r>-YYqKq30wVGg&amp;e=3D</a><br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; A PR making the changes to the QUIC
                          documents can be found at:<br>
                          &gt;<br>
                          &gt;&gt; <a href=3D"https://github.com/quicwg/bas=
e-drafts/pull/1377" rel=3D"noreferrer" target=3D"_blank">https://github.com=
/quicwg/base<wbr>-drafts/pull/1377</a><br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; A few design details did not have
                          clear consensus, but it was felt it<br>
                          &gt; would be better to discuss those in the
                          wider WG than delay the design<br>
                          &gt; team.=C2=A0 A consistent choice was made in
                          the PR and these issues are<br>
                          &gt; mentioned in Appendix B of the design
                          doc.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; As always, comments and questions
                          welcome. That said, this is a big PR<br>
                          &gt; and we recognize that some editorial work
                          is going to be needed before<br>
                          &gt; merging. In the interest of letting
                          people follow along, and to keep github<br>
                          &gt; from falling over, we ask people to keep
                          discussion on the mailing list and<br>
                          &gt; refrain from making PR comments.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; See you in Kista!<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; Ian and Eric<br>
                          &gt;<br>
                          &gt;<br>
                          <br>
                          <br>
                          <span class=3D"m_2322101816431292516HOEnZb"><font=
 color=3D"#888888">
                              <br>
                            </font></span></div>
                      </div>
                      <span class=3D"m_2322101816431292516HOEnZb"><font col=
or=3D"#888888"><span class=3D"m_2322101816431292516m_-1934665759982005286HO=
EnZb"><font color=3D"#888888">-- <br>
                              Kazuho Oku<br>
                              <br>
                            </font></span></font></span></blockquote>
                  </div>
                  <br>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
  </div></div></div>

</blockquote></div><br></div></div>

--000000000000da1481056ceaa7eb--


From nobody Wed May 23 20:55:06 2018
Return-Path: <huitema@huitema.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5AA89120721 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 20:55:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.588
X-Spam-Level: 
X-Spam-Status: No, score=-2.588 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 AnB9ZFN31-QU for <quic@ietfa.amsl.com>; Wed, 23 May 2018 20:55:02 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (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 9D7F11200C1 for <quic@ietf.org>; Wed, 23 May 2018 20:55:01 -0700 (PDT)
Received: from xsmtp04.mail2web.com ([168.144.250.231]) by mx66.antispamcloud.com with esmtps (TLSv1:AES256-SHA:256) (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1fLhL8-0003I4-4C for quic@ietf.org; Thu, 24 May 2018 05:55:00 +0200
Received: from [10.5.2.14] (helo=xmail04.myhosting.com) by xsmtp04.mail2web.com with esmtps (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.63) (envelope-from <huitema@huitema.net>) id 1fLhKy-0000UL-T6 for quic@ietf.org; Wed, 23 May 2018 23:54:55 -0400
Received: (qmail 8906 invoked from network); 24 May 2018 03:54:47 -0000
Received: from unknown (HELO [IPv6:2607:fb90:b283:e8b0:fcd4:75c0:abeb:ab5b]) (Authenticated-user:_huitema@huitema.net@[172.58.45.19]) (envelope-sender <huitema@huitema.net>) by xmail04.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 24 May 2018 03:54:47 -0000
Content-Type: multipart/alternative; boundary=Apple-Mail-2FAE5C97-5E51-4915-ACEA-732E3CDD4E6C
Mime-Version: 1.0 (1.0)
From: Christian Huitema <huitema@huitema.net>
X-Mailer: iPhone Mail (15E302)
In-Reply-To: <CABcZeBPtjbMVL2RQMyLZJg_QyHcgA5E_g8SAgoHUqjpLrJRA4g@mail.gmail.com>
Date: Wed, 23 May 2018 20:54:45 -0700
Cc: Jana Iyengar <jri.ietf@gmail.com>, IETF QUIC WG <quic@ietf.org>
Content-Transfer-Encoding: 7bit
Message-Id: <C48DFD01-BB1F-418D-A2A6-E2BD80407465@huitema.net>
References: <CACpbDcckRvyn18qowWbLRT+sX2EGj3_yPtoS2d-h6ypg4dFrVQ@mail.gmail.com> <6d80b771-ba07-cab7-fa86-d4e31d56b919@huitema.net> <CABcZeBPtjbMVL2RQMyLZJg_QyHcgA5E_g8SAgoHUqjpLrJRA4g@mail.gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
Subject: Re: Stream0 Proposal: EMPTY_ACK
X-Originating-IP: 168.144.250.231
X-AntiSpamCloud-Domain: xsmtpout.mail2web.com
X-AntiSpamCloud-Username: 168.144.250.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=168.144.250.0/24@xsmtpout.mail2web.com
X-AntiSpamCloud-Outgoing-Class: unsure
X-AntiSpamCloud-Outgoing-Evidence: Combined (0.24)
X-Recommended-Action: accept
X-Filter-ID: EX5BVjFpneJeBchSMxfU5k06TzfMM85Y7mlql7PakSN602E9L7XzfQH6nu9C/Fh9KJzpNe6xgvOx q3u0UDjvO37pNwwF1lRXh5rzvPzo9Jts1ujulqUFmMITHM77eiViH/FbFIcIrL/KevcFV68rXs7i TvJ2/ZGzVWB9scFAaCdIFaUvXN+CI+RGy3Me16pB1XpqFDyTB1Bz0n/bLAAUYB/TBCf6oYXAWGet lavcAjD9ytQxIHf9lN5jjLJaPK8lRJSPf/SXbEnDSsal/zZzc4n9VZdr7RAFD5mRwooUYhwMPaBP aKeQW+/QlaOdv8isl/qMm08Zpim2AHUKEWvQ6G/bWfgucjnNmABpGhD9TTttrFCuZ0NkwnSz2Luu o1u9uevuNfM1HjkNEFwape+IgNezYqxGMqsKjARq8PBC4qjpVMhqNcdjhoIlgrKzBvjTmdySlZou 9qHIGOZDEEo7Oyc1nq0gsY582CWqKjiRB3ukywmZtiDkyd4mEBjJGGEJgawbllbHk+xyUKopM6rc KCaQX/lIXcRWtobViGg9fpWbjljpzcldG5bc9h0NLkX5F8FcHzzV3acxBudgYcInb4dOoCMnLjP/ 8RAg0e+WyFCZ4+t4LK79cWIqQA4tGr3po0jfgLl+Ahd0TIbt0Zij6hgeJ07QR0GiieIKGR3KfdmQ xACKGgjW6av7lJfpYBfZN1zg8T9ahw4hquQDupK1jlwBl1z1+w2zS/h3e6UiVRdDYX3tuq4/d4fO KwjajcIDGlUh000z6J0XX7zaLZaVX2eqA47D/juB1cx4exzYk7wfjirBnMSvLt+oZCsKZvqt647l NwN4qOsSZg+fYhVZG9EQ9b9YI+9ZsqMLtlmzzH7VwaDsyRiTeu4Ip+KAECko9HdE0Smt1e6HZuGs N7RwePAFMvX7q8M4x6bP/gjzw0OFbIWNJOiaifOc2xlkb46Pa4K5MPGI7fF8+j7E9IwdcQR2aish SbQcCCOvcJLn8v/2OKHH5lr9xXvSM4nM3avg
X-Report-Abuse-To: spam@quarantine6.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Vr-dCiNA7LM5hbTbaZuXsyccOzs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 03:55:06 -0000

--Apple-Mail-2FAE5C97-5E51-4915-ACEA-732E3CDD4E6C
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

What vulnerability? At a minimum, reflection Dos.
Send UDP packet with "0rtt" content. Trigger emty-ack.

-- Christian Huitema=20

> On May 23, 2018, at 7:45 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>=20
>=20
>=20
>> On Wed, May 23, 2018 at 7:10 PM, Christian Huitema <huitema@huitema.net> w=
rote:
>> I dislike the EMPTY_ACK because they are "responses to something that cou=
ld not be decrypted". You don't know where the packet came from, it could be=
 spoofed. So you have on one hand a possible optimization, on the other hand=
 a possible vulnerability, and in all cases additional complexity.
>>=20
> What's the vulnerability? Anything more than a spurious retransmit?
>=20
> -Ekr
>=20
>>=20
>>> On 5/23/2018 4:27 PM, Jana Iyengar wrote:
>>> (Moving more discussions from main thread)
>>>=20
>>> ---------- Forwarded message ----------
>>> From: Subodh Iyengar <subodh@fb.com>
>>> Date: Wed, May 23, 2018 at 3:37 PM
>>> Subject: Re: Stream0 Design Team Proposal
>>> To: Mike Bishop <mbishop@evequefou.be>, Christian Huitema <huitema@huite=
ma.net>, "quic@ietf.org" <quic@ietf.org>
>>>=20
>>>=20
>>> FWIW I see EMPTY_ACKs as being very similar to a Duplicate ack. We thoug=
ht about using Duplicate acks as well but we thought that EMPTY_ACks would b=
e simpler to implement and be able to convey similar information.
>>>=20
>>> Subodh
>>>           =20
>>> From: QUIC <quic-bounces@ietf.org> on behalf of Mike Bishop <mbishop@eve=
quefou.be>
>>> Sent: Wednesday, May 23, 2018 3:26:35 PM
>>> To: Christian Huitema; quic@ietf.org
>>> Subject: RE: Stream0 Design Team Proposal
>>> =20
>>> Christian, can you expand on why you dislike the EMPTY_ACK?  Being able t=
o say =E2=80=9CI=E2=80=99ve received some packets from you, but am unable to=
 process any of them because I=E2=80=99m missing some handshake data=E2=80=9D=
 seems like a useful way to short-circuit timeouts on clients.  It also does=
n=E2=80=99t commit the server to holding any state =E2=80=93 IIUC, a server c=
ould form a packet containing an EMPTY_ACK and then discard its internal sta=
te until it gets the retransmitted (or delayed) Initial packet.
>>>=20
>>> =20
>>>=20
>>>=20
>>>=20
>>>=20
>>>> On Wed, May 23, 2018 at 4:25 PM, Jana Iyengar <jri.ietf@gmail.com> wrot=
e:
>>>> (Forking this discussion off from the main thread.)
>>>>=20
>>>>> On Wed, May 23, 2018 at 2:13 AM, Kazuho Oku <kazuhooku@gmail.com> wrot=
e:
>>>>> 2018-05-23 14:29 GMT+09:00 Christian Huitema <huitema@huitema.net>:
>>>>> > I like the proposal. In particular, I really like the encryption of
>>>>> > handshake packets with the handshake key, as it does close a number o=
f
>>>>> > avenues for attacks. And I like that it solves the "ack promotion" i=
ssue
>>>>> > that I was complaining against for some time. Turns out that in the c=
urrent
>>>>> > draft, it is very hard to contain that problem if you enable client a=
uth.
>>>>> >
>>>>> >
>>>>> > On the other hand, I agree with Martin that a lot of the additions t=
o
>>>>> > transmission recovery should be moved to separate PRs. I am not enth=
usiastic
>>>>> > with the EMPTY ACK mechanism, or with the proposed "implicit
>>>>> > acknowledgement" of a lower crypto stream by a higher level ack.
>>>>>=20
>>>>> At the moment I do not have a strong opinion on the Empty ACK mechanis=
m.
>>>>>=20
>>>>> However, regarding how we close the Initial and Handshake contexts, my=

>>>>> preference goes to using implicit ACKs (i.e. use the successful
>>>>> receipt of a packet that is protected under a higher level of
>>>>> encryption key as the signal) rather than explicitly ACKing the last
>>>>> flight of data.
>>>>>=20
>>>>> As I see, there are two downsides in the Explicit ACKing approach.
>>>>>=20
>>>>> * Explicit ACKing requires sending two additional packets during the
>>>>> handshake, which means that we would have more AES operations plus
>>>>> somewhere around 60 bytes of overhead on the wire.
>>>>> * Explicit ACKing requires more signaling from the TLS stack. In case
>>>>> of implicit ACKing, the TLS stack need to only provide the AEAD
>>>>> contexts and the messages, whereas in case of explicit ACKing, the TLS=

>>>>> stack also needs to provide a signal indicating the end of the
>>>>> transmission at each encryption level.
>>>>>=20
>>>>> The downside of the implicit ACKing approach is that the server needs
>>>>> to signal the termination of the Handshake context using a special
>>>>> frame sent using a 1-RTT packet.
>>>>>=20
>>>>> But even taking that into consideration, I think that implicit ACKing
>>>>> is still easier to implement, considering the need for the additional
>>>>> signal in the explicit ACK case that have been described above.
>>>>>=20
>>>>>=20
>>>>> > In any
>>>>> > case, starting as simple as possible would help having the first
>>>>> > implementations and tests.
>>>>> >
>>>>> >
>>>>> > On 5/22/2018 8:26 PM, Subodh Iyengar wrote:
>>>>> >
>>>>> > As an implementor of fizz, I support this design and am willing to i=
mplement
>>>>> > this as well.
>>>>> >
>>>>> >
>>>>> > While this is a change in the API that TLS classically exposes, I th=
ink this
>>>>> > is the right tradeoff because it helps make things way more explicit=
 which
>>>>> > will prevent several other bugs from happening in the future.
>>>>> >
>>>>> >
>>>>> > Subodh
>>>>> >
>>>>> > ________________________________
>>>>> > From: QUIC <quic-bounces@ietf.org> on behalf of Martin Thomson
>>>>> > <martin.thomson@gmail.com>
>>>>> > Sent: Tuesday, May 22, 2018 8:00:40 PM
>>>>> > To: Ian Swett
>>>>> > Cc: ekr@mozilla.com; QUIC WG
>>>>> > Subject: Re: Stream0 Design Team Proposal
>>>>> >
>>>>> > First of all, thanks to the design team for the work they have done.=
  I
>>>>> > haven't digested everything yet, but I think that I have a good sens=
e of
>>>>> > the shape of the proposal.
>>>>> >
>>>>> > Overall, this looks like a workable design.  It's a lot more invasiv=
e of
>>>>> > the cryptographic handshake implementation than I had thought people=
 were
>>>>> > willing to stomach originally.  But it's clear that we've run into p=
roblems
>>>>> > with the current, more abstract API and this is a fairly natural way=
 to
>>>>> > split TLS.  I've spent a little time thinking about how this might b=
e
>>>>> > implemented and I think that it's not going to be *too* painful.  Th=
e proof
>>>>> > will be in the pudding there though.
>>>>> >
>>>>> > In looking at the PR, I really appreciate seeing all the changes tog=
ether..
>>>>> > BTW, the link above points to the wrong PR, so be careful (it appear=
s to
>>>>> > have the same content, but that's not guaranteed).  The actual PR is=
 here:
>>>>> > https://github.com/quicwg/base-drafts/pull/1377
>>>>> >
>>>>> > I've pushed a branch to the main repo so that you can preview the en=
tire
>>>>> > document set:
>>>>> > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__quicwg.github=
.io_base-2Ddrafts_stream0_&d=3DDwIBaQ&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3Dh3Ju9EB=
S7mHtwg-wAyN7fQ&m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&s=3DususmtxI=
3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&e=3D
>>>>> >
>>>>> > It seems like there are some core changes here and a bunch of separa=
ble or
>>>>> > at least secondary changes.  I'm sure that each one has its own
>>>>> > justification, but that isn't always clear. The following changes se=
em like
>>>>> > they are separable:
>>>>> >
>>>>> > * The use of separate packet number spaces
>>>>> > * The Retry packet changes (and NEW_TOKEN)
>>>>> > * EMPTY_ACK
>>>>> > * The TLS extension for flow control
>>>>> >
>>>>> > Right now, some of these appear to be entirely gratuitous.  I'd like=
 to get
>>>>> > to the bottom of each before we continue.
>>>>> >
>>>>> > At a minimum, the PR we land first should include just the core chan=
ges.
>>>>> > As you say, reviewing a monster PR like this will only make GitHub w=
eep
>>>>> > unicorns, but we might be able to cut this into smaller pieces.
>>>>> >
>>>>> > On Wed, May 23, 2018 at 11:31 AM Ian Swett <ianswett=3D
>>>>> > 40google.com@dmarc.ietf.org> wrote:
>>>>> >
>>>>> >> Dear QUIC WG,
>>>>> >
>>>>> >
>>>>> >> On behalf of the Stream 0 Design Team, I am pleased to report that w=
e
>>>>> > have consensus on a proposed approach to share with the WG. The DT's=

>>>>> > proposal will make QUIC and TLS work closer together and incorporate=
s ideas
>>>>> > from DTLS, but it does not use the DTLS protocol itself.
>>>>> >
>>>>> >
>>>>> >> The DT believes this solves the important open Stream 0 issues. The=

>>>>> > proposal will be a bit more invasive in TLS, but we believe it is th=
e right
>>>>> > long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS,=
 and
>>>>> > Mint) are willing and able to do the work necessary.. A number of st=
acks
>>>>> > are currently working on implementations of this new approach, which=
 we
>>>>> > hope to have in time for the Interim meeting.
>>>>> >
>>>>> >
>>>>> >> A design document describing the overall approach can be found at:
>>>>> >
>>>>> >
>>>>> > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__docs.google.c=
om_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8_edit&d=3DDwIBaQ=
&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&m=3D_vGK3zTKFrMOkFihJ=
nPntLYw1T0_NEMiHYSM0Q_u1JA&s=3DjDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg&e=
=3D
>>>>> >
>>>>> >
>>>>> >> A PR making the changes to the QUIC documents can be found at:
>>>>> >
>>>>> >> https://github.com/quicwg/base-drafts/pull/1377
>>>>> >
>>>>> >
>>>>> >> A few design details did not have clear consensus, but it was felt i=
t
>>>>> > would be better to discuss those in the wider WG than delay the desi=
gn
>>>>> > team.  A consistent choice was made in the PR and these issues are
>>>>> > mentioned in Appendix B of the design doc.
>>>>> >
>>>>> >
>>>>> >> As always, comments and questions welcome. That said, this is a big=
 PR
>>>>> > and we recognize that some editorial work is going to be needed befo=
re
>>>>> > merging. In the interest of letting people follow along, and to keep=
 github
>>>>> > from falling over, we ask people to keep discussion on the mailing l=
ist and
>>>>> > refrain from making PR comments.
>>>>> >
>>>>> >
>>>>> >> See you in Kista!
>>>>> >
>>>>> >
>>>>> >> Ian and Eric
>>>>> >
>>>>> >
>>>>>=20
>>>>>=20
>>>>>=20
>>>>> --=20
>>>>> Kazuho Oku
>>>>>=20
>>>>=20
>>>=20
>>=20
>=20

--Apple-Mail-2FAE5C97-5E51-4915-ACEA-732E3CDD4E6C
Content-Type: text/html;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto">What vulnerability? At a minimum, reflectio=
n Dos.<div>Send UDP packet with "0rtt" content. Trigger emty-ack.<br><br><di=
v id=3D"AppleMailSignature">-- Christian Huitema&nbsp;</div><div><br>On May 2=
3, 2018, at 7:45 PM, Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com">ekr@r=
tfm.com</a>&gt; wrote:<br><br></div><blockquote type=3D"cite"><div><div dir=3D=
"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, M=
ay 23, 2018 at 7:10 PM, Christian Huitema <span dir=3D"ltr">&lt;<a href=3D"m=
ailto:huitema@huitema.net" target=3D"_blank">huitema@huitema.net</a>&gt;</sp=
an> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;b=
order-left:1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <p>I dislike the EMPTY_ACK because they are "responses to something
      that could not be decrypted". You don't know where the packet came
      from, it could be spoofed. So you have on one hand a possible
      optimization, on the other hand a possible vulnerability, and in
      all cases additional complexity.<br></p></div></blockquote><div>What's=
 the vulnerability? Anything more than a spurious retransmit?<br></div><div>=
<br></div><div>-Ekr</div><div><br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div t=
ext=3D"#000000" bgcolor=3D"#FFFFFF"><p>
    </p><div><div class=3D"h5">
    <br>
    <div class=3D"m_2322101816431292516moz-cite-prefix">On 5/23/2018 4:27 PM=
, Jana Iyengar
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div>(Moving more discussions from main thread)</div>
        <div><br>
        </div>
        ---------- Forwarded message ----------<br>
        From:<span>&nbsp;</span><b class=3D"gmail_sendername">Subodh Iyengar=
</b><span>&nbsp;</span><span dir=3D"ltr">&lt;<a href=3D"mailto:subodh@fb.com=
" target=3D"_blank">subodh@fb.com</a>&gt;</span><br>
        Date: Wed, May 23, 2018 at 3:37 PM<br>
        Subject: Re: Stream0 Design Team Proposal<br>
        To: Mike Bishop &lt;<a href=3D"mailto:mbishop@evequefou.be" target=3D=
"_blank">mbishop@evequefou.be</a>&gt;, Christian
        Huitema &lt;<a href=3D"mailto:huitema@huitema.net" target=3D"_blank"=
>huitema@huitema.net</a>&gt;, "<a href=3D"mailto:quic@ietf.org" target=3D"_b=
lank">quic@ietf.org</a>"
        &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic@ietf.org=
</a>&gt;<br>
        <br>
        <br>
        <div dir=3D"ltr">
          <div id=3D"m_2322101816431292516gmail-m_-6373418337459262039divtag=
defaultwrapper" dir=3D"ltr" style=3D"font-size:12pt;color:rgb(0,0,0);font-fa=
mily:Calibri,Helvetica,sans-serif">
            <p style=3D"margin-top:0px;margin-bottom:0px">FWIW I see
              EMPTY_ACKs as being very similar to a Duplicate ack. We
              thought about using Duplicate acks as well but we thought
              that EMPTY_ACks would be simpler to implement and be able
              to convey similar&nbsp;information.<br>
            </p>
            <p style=3D"margin-top:0px;margin-bottom:0px"><br>
            </p>
            <p style=3D"margin-top:0px;margin-bottom:0px">Subodh<br>
            </p>
          </div>
          <hr style=3D"display:inline-block;width:1427.78px">
          <div id=3D"m_2322101816431292516gmail-m_-6373418337459262039divRpl=
yFwdMsg" dir=3D"ltr"><font style=3D"font-size:11pt" face=3D"Calibri, sans-se=
rif" color=3D"#000000"><b>From:</b><span>&nbsp;</span>QUIC &lt;<a href=3D"ma=
ilto:quic-bounces@ietf.org" style=3D"color:rgb(17,85,204)" target=3D"_blank"=
>quic-bounces@ietf.org</a>&gt;
              on behalf of Mike Bishop &lt;<a href=3D"mailto:mbishop@evequef=
ou.be" style=3D"color:rgb(17,85,204)" target=3D"_blank">mbishop@evequefou.be=
</a>&gt;<br>
              <b>Sent:</b><span>&nbsp;</span>Wednesday, May 23, 2018 3:26:35=

              PM<br>
              <b>To:</b><span>&nbsp;</span>Christian Huitema;<span>&nbsp;</s=
pan><a href=3D"mailto:quic@ietf.org" style=3D"color:rgb(17,85,204)" target=3D=
"_blank">quic@ietf.org</a><br>
              <b>Subject:</b><span>&nbsp;</span>RE: Stream0 Design Team
              Proposal</font>
            <div>&nbsp;</div>
          </div>
          <div>
            <div class=3D"m_2322101816431292516gmail-h5" style=3D"display:bl=
ock;color:rgb(80,0,80)">
              <div style=3D"background-color:white" lang=3D"EN-US">
                <div class=3D"m_2322101816431292516gmail-m_-6373418337459262=
039x_WordSection1">
                  <p class=3D"m_2322101816431292516gmail-m_-6373418337459262=
039x_MsoNormal" style=3D"color:rgb(80,0,80);font-family:arial,sans-serif;fon=
t-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-ca=
ps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent=
:0px;text-transform:none;white-space:normal;word-spacing:0px;background-colo=
r:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initi=
al"><span style=3D"color:windowtext">Christian, can you expand
                      on why you dislike the EMPTY_ACK?&nbsp; Being able to
                      say =E2=80=9CI=E2=80=99ve received some packets from y=
ou, but am
                      unable to process any of them because I=E2=80=99m miss=
ing
                      some handshake data=E2=80=9D seems like a useful way t=
o
                      short-circuit timeouts on clients.&nbsp; It also
                      doesn=E2=80=99t commit the server to holding any state=
 =E2=80=93
                      IIUC, a server could form a packet containing an
                      EMPTY_ACK and then discard its internal state
                      until it gets the retransmitted (or delayed)
                      Initial packet.</span></p>
                  <p class=3D"m_2322101816431292516gmail-m_-6373418337459262=
039x_MsoNormal" style=3D"color:rgb(80,0,80);font-family:arial,sans-serif;fon=
t-size:small;font-style:normal;font-variant-ligatures:normal;font-variant-ca=
ps:normal;font-weight:400;letter-spacing:normal;text-align:start;text-indent=
:0px;text-transform:none;white-space:normal;word-spacing:0px;background-colo=
r:rgb(255,255,255);text-decoration-style:initial;text-decoration-color:initi=
al"><span style=3D"color:windowtext">&nbsp;</span></p>
                  <div style=3D"color:rgb(80,0,80);font-family:arial,sans-se=
rif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-var=
iant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;text=
-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;backgrou=
nd-color:rgb(255,255,255);text-decoration-style:initial;text-decoration-colo=
r:initial">
                    <div style=3D"border-right:none;border-bottom:none;borde=
r-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in"><br c=
lass=3D"m_2322101816431292516gmail-Apple-interchange-newline">
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
        <br>
        <div class=3D"gmail_extra"><br>
          <div class=3D"gmail_quote">On Wed, May 23, 2018 at 4:25 PM, Jana
            Iyengar <span dir=3D"ltr">&lt;<a href=3D"mailto:jri.ietf@gmail.c=
om" target=3D"_blank">jri.ietf@gmail.com</a>&gt;</span>
            wrote:<br>
            <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bor=
der-left:1px #ccc solid;padding-left:1ex">
              <div dir=3D"ltr">(Forking this discussion off from the main
                thread.)<br>
                <div class=3D"gmail_extra"><br>
                  <div class=3D"gmail_quote">On Wed, May 23, 2018 at 2:13
                    AM, Kazuho Oku <span dir=3D"ltr">&lt;<a href=3D"mailto:k=
azuhooku@gmail.com" target=3D"_blank">kazuhooku@gmail.com</a>&gt;</span>
                    wrote:<br>
                    <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><span>2018-05-23
                        14:29 GMT+09:00 Christian Huitema &lt;<a href=3D"mai=
lto:huitema@huitema.net" target=3D"_blank">huitema@huitema.net</a>&gt;:<br>
                        &gt; I like the proposal. In particular, I
                        really like the encryption of<br>
                        &gt; handshake packets with the handshake key,
                        as it does close a number of<br>
                        &gt; avenues for attacks. And I like that it
                        solves the "ack promotion" issue<br>
                        &gt; that I was complaining against for some
                        time. Turns out that in the current<br>
                        &gt; draft, it is very hard to contain that
                        problem if you enable client auth.<br>
                        &gt;<br>
                        &gt;<br>
                        &gt; On the other hand, I agree with Martin that
                        a lot of the additions to<br>
                        &gt; transmission recovery should be moved to
                        separate PRs. I am not enthusiastic<br>
                        &gt; with the EMPTY ACK mechanism, or with the
                        proposed "implicit<br>
                        &gt; acknowledgement" of a lower crypto stream
                        by a higher level ack.<br>
                        <br>
                      </span>At the moment I do not have a strong
                      opinion on the Empty ACK mechanism.<br>
                      <br>
                      However, regarding how we close the Initial and
                      Handshake contexts, my<br>
                      preference goes to using implicit ACKs (i.e. use
                      the successful<br>
                      receipt of a packet that is protected under a
                      higher level of<br>
                      encryption key as the signal) rather than
                      explicitly ACKing the last<br>
                      flight of data.<br>
                      <br>
                      As I see, there are two downsides in the Explicit
                      ACKing approach.<br>
                      <br>
                      * Explicit ACKing requires sending two additional
                      packets during the<br>
                      handshake, which means that we would have more AES
                      operations plus<br>
                      somewhere around 60 bytes of overhead on the wire.<br>=

                      * Explicit ACKing requires more signaling from the
                      TLS stack. In case<br>
                      of implicit ACKing, the TLS stack need to only
                      provide the AEAD<br>
                      contexts and the messages, whereas in case of
                      explicit ACKing, the TLS<br>
                      stack also needs to provide a signal indicating
                      the end of the<br>
                      transmission at each encryption level.<br>
                      <br>
                      The downside of the implicit ACKing approach is
                      that the server needs<br>
                      to signal the termination of the Handshake context
                      using a special<br>
                      frame sent using a 1-RTT packet.<br>
                      <br>
                      But even taking that into consideration, I think
                      that implicit ACKing<br>
                      is still easier to implement, considering the need
                      for the additional<br>
                      signal in the explicit ACK case that have been
                      described above.<br>
                      <div>
                        <div class=3D"m_2322101816431292516m_-19346657599820=
05286h5"><br>
                          <br>
                          &gt; In any<br>
                          &gt; case, starting as simple as possible
                          would help having the first<br>
                          &gt; implementations and tests.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt; On 5/22/2018 8:26 PM, Subodh Iyengar
                          wrote:<br>
                          &gt;<br>
                          &gt; As an implementor of fizz, I support this
                          design and am willing to implement<br>
                          &gt; this as well.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt; While this is a change in the API that
                          TLS classically exposes, I think this<br>
                          &gt; is the right tradeoff because it helps
                          make things way more explicit which<br>
                          &gt; will prevent several other bugs from
                          happening in the future.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt; Subodh<br>
                          &gt;<br>
                          &gt; ______________________________<wbr>__<br>
                          &gt; From: QUIC &lt;<a href=3D"mailto:quic-bounces=
@ietf.org" target=3D"_blank">quic-bounces@ietf.org</a>&gt;
                          on behalf of Martin Thomson<br>
                          &gt; &lt;<a href=3D"mailto:martin.thomson@gmail.co=
m" target=3D"_blank">martin.thomson@gmail.com</a>&gt;<br>
                          &gt; Sent: Tuesday, May 22, 2018 8:00:40 PM<br>
                          &gt; To: Ian Swett<br>
                          &gt; Cc: <a href=3D"mailto:ekr@mozilla.com" target=
=3D"_blank">ekr@mozilla.com</a>;
                          QUIC WG<br>
                          &gt; Subject: Re: Stream0 Design Team Proposal<br>=

                          &gt;<br>
                          &gt; First of all, thanks to the design team
                          for the work they have done.&nbsp; I<br>
                          &gt; haven't digested everything yet, but I
                          think that I have a good sense of<br>
                          &gt; the shape of the proposal.<br>
                          &gt;<br>
                          &gt; Overall, this looks like a workable
                          design.&nbsp; It's a lot more invasive of<br>
                          &gt; the cryptographic handshake
                          implementation than I had thought people were<br>
                          &gt; willing to stomach originally.&nbsp; But it's=

                          clear that we've run into problems<br>
                          &gt; with the current, more abstract API and
                          this is a fairly natural way to<br>
                          &gt; split TLS.&nbsp; I've spent a little time
                          thinking about how this might be<br>
                          &gt; implemented and I think that it's not
                          going to be *too* painful.&nbsp; The proof<br>
                          &gt; will be in the pudding there though.<br>
                          &gt;<br>
                        </div>
                      </div>
                      &gt; In looking at the PR, I really appreciate
                      seeing all the changes together..<br>
                      <div class=3D"m_2322101816431292516m_-1934665759982005=
286HOEnZb">
                        <div class=3D"m_2322101816431292516m_-19346657599820=
05286h5">&gt; BTW,
                          the link above points to the wrong PR, so be
                          careful (it appears to<br>
                          &gt; have the same content, but that's not
                          guaranteed).&nbsp; The actual PR is here:<br>
                          &gt; <a href=3D"https://github.com/quicwg/base-dra=
fts/pull/1377" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicw=
g/base<wbr>-drafts/pull/1377</a><br>
                          &gt;<br>
                          &gt; I've pushed a branch to the main repo so
                          that you can preview the entire<br>
                          &gt; document set:<br>
                          &gt; <a href=3D"https://urldefense.proofpoint.com/=
v2/url?u=3Dhttps-3A__quicwg.github.io_base-2Ddrafts_stream0_&amp;d=3DDwIBaQ&=
amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&amp;m=3D_vGK3z=
TKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&amp;s=3DususmtxI3BTaLlBWe_HkQUWRH4sBI0=
Cggj1oWZMBHak&amp;e=3D" rel=3D"noreferrer" target=3D"_blank">https://urldefe=
nse.proofpoint.<wbr>com/v2/url?u=3Dhttps-3A__quicwg.<wbr>github.io_base-2Ddr=
afts_stream<wbr>0_&amp;d=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd4<wbr>1b3MUw&amp;r=3D=
h3Ju9EBS7mHtwg-wAyN7f<wbr>Q&amp;m=3D_vGK3zTKFrMOkFihJnPntLYw1T<wbr>0_NEMiHYS=
M0Q_u1JA&amp;s=3DususmtxI3B<wbr>TaLlBWe_HkQUWRH4sBI0Cggj1oWZMB<wbr>Hak&amp;e=
=3D</a><br>
                          &gt;<br>
                          &gt; It seems like there are some core changes
                          here and a bunch of separable or<br>
                          &gt; at least secondary changes.&nbsp; I'm sure
                          that each one has its own<br>
                          &gt; justification, but that isn't always
                          clear. The following changes seem like<br>
                          &gt; they are separable:<br>
                          &gt;<br>
                          &gt; * The use of separate packet number
                          spaces<br>
                          &gt; * The Retry packet changes (and
                          NEW_TOKEN)<br>
                          &gt; * EMPTY_ACK<br>
                          &gt; * The TLS extension for flow control<br>
                          &gt;<br>
                          &gt; Right now, some of these appear to be
                          entirely gratuitous.&nbsp; I'd like to get<br>
                          &gt; to the bottom of each before we continue.<br>=

                          &gt;<br>
                          &gt; At a minimum, the PR we land first should
                          include just the core changes.<br>
                          &gt; As you say, reviewing a monster PR like
                          this will only make GitHub weep<br>
                          &gt; unicorns, but we might be able to cut
                          this into smaller pieces.<br>
                          &gt;<br>
                          &gt; On Wed, May 23, 2018 at 11:31 AM Ian
                          Swett &lt;ianswett=3D<br>
                          &gt; <a href=3D"mailto:40google.com@dmarc.ietf.org=
" target=3D"_blank">40google.com@dmarc.ietf.org</a>&gt;
                          wrote:<br>
                          &gt;<br>
                          &gt;&gt; Dear QUIC WG,<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; On behalf of the Stream 0 Design
                          Team, I am pleased to report that we<br>
                          &gt; have consensus on a proposed approach to
                          share with the WG. The DT's<br>
                          &gt; proposal will make QUIC and TLS work
                          closer together and incorporates ideas<br>
                          &gt; from DTLS, but it does not use the DTLS
                          protocol itself.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; The DT believes this solves the
                          important open Stream 0 issues. The<br>
                          &gt; proposal will be a bit more invasive in
                          TLS, but we believe it is the right<br>
                          &gt; long-term direction and several TLS
                          stacks (BoringSSL, PicoTLS, NSS, and<br>
                          &gt; Mint) are willing and able to do the work
                          necessary.. A number of stacks<br>
                          &gt; are currently working on implementations
                          of this new approach, which we<br>
                          &gt; hope to have in time for the Interim
                          meeting.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; A design document describing the
                          overall approach can be found at:<br>
                          &gt;<br>
                          &gt;<br>
                          &gt; <a href=3D"https://urldefense.proofpoint.com/=
v2/url?u=3Dhttps-3A__docs..google.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6au=
ojfJLkxddT93j6SwHY8_edit&amp;d=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=
=3Dh3Ju9EBS7mHtwg-wAyN7fQ&amp;m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1J=
A&amp;s=3DjDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg&amp;e=3D" rel=3D"noref=
errer" target=3D"_blank">https://urldefense.proofpoint.<wbr>com/v2/url?u=3Dh=
ttps-3A__docs.go<wbr>ogle.com_document_d_1fRsJqPinJ<wbr>l8N3b-2DbflDRV6auojf=
JLkxddT93j<wbr>6SwHY8_edit&amp;d=3DDwIBaQ&amp;c=3D5VD0RTt<wbr>NlTh3ycd41b3MU=
w&amp;r=3Dh3Ju9EBS7mHt<wbr>wg-wAyN7fQ&amp;m=3D_vGK3zTKFrMOkFihJ<wbr>nPntLYw1=
T0_NEMiHYSM0Q_u1JA&amp;s=3Dj<wbr>DNnz34hmWvLSQnHkSnYdihW-jG-0xZ<wbr>-YYqKq30=
wVGg&amp;e=3D</a><br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; A PR making the changes to the QUIC
                          documents can be found at:<br>
                          &gt;<br>
                          &gt;&gt; <a href=3D"https://github.com/quicwg/base=
-drafts/pull/1377" rel=3D"noreferrer" target=3D"_blank">https://github.com/q=
uicwg/base<wbr>-drafts/pull/1377</a><br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; A few design details did not have
                          clear consensus, but it was felt it<br>
                          &gt; would be better to discuss those in the
                          wider WG than delay the design<br>
                          &gt; team.&nbsp; A consistent choice was made in
                          the PR and these issues are<br>
                          &gt; mentioned in Appendix B of the design
                          doc.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; As always, comments and questions
                          welcome. That said, this is a big PR<br>
                          &gt; and we recognize that some editorial work
                          is going to be needed before<br>
                          &gt; merging. In the interest of letting
                          people follow along, and to keep github<br>
                          &gt; from falling over, we ask people to keep
                          discussion on the mailing list and<br>
                          &gt; refrain from making PR comments.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; See you in Kista!<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; Ian and Eric<br>
                          &gt;<br>
                          &gt;<br>
                          <br>
                          <br>
                          <span class=3D"m_2322101816431292516HOEnZb"><font c=
olor=3D"#888888">
                              <br>
                            </font></span></div>
                      </div>
                      <span class=3D"m_2322101816431292516HOEnZb"><font colo=
r=3D"#888888"><span class=3D"m_2322101816431292516m_-1934665759982005286HOEn=
Zb"><font color=3D"#888888">-- <br>
                              Kazuho Oku<br>
                              <br>
                            </font></span></font></span></blockquote>
                  </div>
                  <br>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
  </div></div></div>

</blockquote></div><br></div></div>
</div></blockquote></div></body></html>=

--Apple-Mail-2FAE5C97-5E51-4915-ACEA-732E3CDD4E6C--


From nobody Wed May 23 21:00:20 2018
Return-Path: <ekr@rtfm.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 642DE1243F3 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 21:00:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level: 
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, T_DKIMWL_WL_MED=-0.01, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 5IjaDEllfpEy for <quic@ietfa.amsl.com>; Wed, 23 May 2018 21:00:16 -0700 (PDT)
Received: from mail-oi0-x22d.google.com (mail-oi0-x22d.google.com [IPv6:2607:f8b0:4003:c06::22d]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D9B14120227 for <quic@ietf.org>; Wed, 23 May 2018 21:00:15 -0700 (PDT)
Received: by mail-oi0-x22d.google.com with SMTP id a6-v6so229377oia.2 for <quic@ietf.org>; Wed, 23 May 2018 21:00:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=1nNS8CeQEY9E096FdR4lyTKjDFihQY6aYaVy5aR5d3U=; b=L0uIxXo0e7IIrPfFYLSSnVUzeBrLSzVBpVJfGtY55IT+uvQel3UDFVdnBcnbptTofR Jq8TyaNGZo0wCt/QovBG+VsbCLfIA756BvMF7hwhJxC6zYwQVKAGPxCUqmxoIOO2xbFZ iU4VSZGnTRCU/tdrQ7WNarCUhWwZKV1z0BcGrHA0R8zmtFRYpS0fWlKXfjfJg6yPx5Fn 39bDRrwV8EKW8t/vtFuZUtlCyC8DjJ00SIj5MzJ76xGG9iFvka/Z4GfqqBFbB3EKYolw 2Da0jDB4y3t7ZWTaM0fX7jaatB+RxL8M5PfmJNjptv4evb7QNrBm/kgpGDblwwubBMd6 1z8w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=1nNS8CeQEY9E096FdR4lyTKjDFihQY6aYaVy5aR5d3U=; b=GiulZjDHm3Wjky+tiDSAvoNYI4ZQkZLXps5eb9L2thSWWBOp0GfRgqMHQakgnjfjur JOnO9i0V0tl7CIuAlmDBHSs9IJ/pCP2qDmJuB6lauRfEbEiaqnOF0s5K1pcBr7cobLed rYK6yJBIsusjNr8GYPaqP1QeeNN2eSyInfcm8yRfc6djf0qxYGy7YlqtETp1qyJO18Cg 6EZ6kjaADxU6i3ZR2kP/9BnCFlWR/gnuY8sY9F50eWOt/k3ndDC9eClWiTcHPEplYNJL vU/TDyvYZ7pVqe0em3MqeYdXGH68VHKDA2/BQxTNez7HtCMSOyGYdkpz5aA+/D+ulLvS /O2A==
X-Gm-Message-State: ALKqPwehIIL4rQHpszrG7UvMfWe1hJjgC4o+JGoVJ9DxSzBhOeYey0qO BrkH8i7bJccy8Fbi84LI9L0jJmaZjoqfVrftr8h/yQ==
X-Google-Smtp-Source: AB8JxZrpN4zdU2pZjN/A5qZ2OyRuNwl9y2lcYwYfcWE5DWDspqepG/eCaysKpG7O/PNMeCAx2dy1nIUqgacSzju9TmI=
X-Received: by 2002:aca:4c11:: with SMTP id z17-v6mr3173641oia.174.1527134415160;  Wed, 23 May 2018 21:00:15 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:ac9:66:0:0:0:0:0 with HTTP; Wed, 23 May 2018 20:59:34 -0700 (PDT)
In-Reply-To: <C48DFD01-BB1F-418D-A2A6-E2BD80407465@huitema.net>
References: <CACpbDcckRvyn18qowWbLRT+sX2EGj3_yPtoS2d-h6ypg4dFrVQ@mail.gmail.com> <6d80b771-ba07-cab7-fa86-d4e31d56b919@huitema.net> <CABcZeBPtjbMVL2RQMyLZJg_QyHcgA5E_g8SAgoHUqjpLrJRA4g@mail.gmail.com> <C48DFD01-BB1F-418D-A2A6-E2BD80407465@huitema.net>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 23 May 2018 20:59:34 -0700
Message-ID: <CABcZeBM1hKYxVe2aFgfQe3zAwhpgQEi03jRuzJShXt8Q1=7dKg@mail.gmail.com>
Subject: Re: Stream0 Proposal: EMPTY_ACK
To: Christian Huitema <huitema@huitema.net>
Cc: Jana Iyengar <jri.ietf@gmail.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000571f24056cebb070"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/s-XdAiCCX9oUYM3d1jdAGnJnuNU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 04:00:19 -0000

--000000000000571f24056cebb070
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Wed, May 23, 2018 at 8:54 PM, Christian Huitema <huitema@huitema.net>
wrote:

> What vulnerability? At a minimum, reflection Dos.
> Send UDP packet with "0rtt" content. Trigger emty-ack.
>

Given that you can already trigger transmission of the full cert chain with
CH, this doesn't seem very interesting.

-Ekr


> -- Christian Huitema
>
> On May 23, 2018, at 7:45 PM, Eric Rescorla <ekr@rtfm.com> wrote:
>
>
>
> On Wed, May 23, 2018 at 7:10 PM, Christian Huitema <huitema@huitema.net>
> wrote:
>
>> I dislike the EMPTY_ACK because they are "responses to something that
>> could not be decrypted". You don't know where the packet came from, it
>> could be spoofed. So you have on one hand a possible optimization, on th=
e
>> other hand a possible vulnerability, and in all cases additional complex=
ity.
>>
> What's the vulnerability? Anything more than a spurious retransmit?
>
> -Ekr
>
>
>> On 5/23/2018 4:27 PM, Jana Iyengar wrote:
>>
>> (Moving more discussions from main thread)
>>
>> ---------- Forwarded message ----------
>> From: Subodh Iyengar <subodh@fb.com>
>> Date: Wed, May 23, 2018 at 3:37 PM
>> Subject: Re: Stream0 Design Team Proposal
>> To: Mike Bishop <mbishop@evequefou.be>, Christian Huitema <
>> huitema@huitema.net>, "quic@ietf.org" <quic@ietf.org>
>>
>>
>> FWIW I see EMPTY_ACKs as being very similar to a Duplicate ack. We
>> thought about using Duplicate acks as well but we thought that EMPTY_ACk=
s
>> would be simpler to implement and be able to convey similar information.
>>
>>
>> Subodh
>> ------------------------------
>> *From:* QUIC <quic-bounces@ietf.org> on behalf of Mike Bishop <
>> mbishop@evequefou.be>
>> *Sent:* Wednesday, May 23, 2018 3:26:35 PM
>> *To:* Christian Huitema; quic@ietf.org
>> *Subject:* RE: Stream0 Design Team Proposal
>>
>>
>> Christian, can you expand on why you dislike the EMPTY_ACK?  Being able
>> to say =E2=80=9CI=E2=80=99ve received some packets from you, but am unab=
le to process any
>> of them because I=E2=80=99m missing some handshake data=E2=80=9D seems l=
ike a useful way to
>> short-circuit timeouts on clients.  It also doesn=E2=80=99t commit the s=
erver to
>> holding any state =E2=80=93 IIUC, a server could form a packet containin=
g an
>> EMPTY_ACK and then discard its internal state until it gets the
>> retransmitted (or delayed) Initial packet.
>>
>>
>>
>>
>>
>> On Wed, May 23, 2018 at 4:25 PM, Jana Iyengar <jri.ietf@gmail.com> wrote=
:
>>
>>> (Forking this discussion off from the main thread.)
>>>
>>> On Wed, May 23, 2018 at 2:13 AM, Kazuho Oku <kazuhooku@gmail.com> wrote=
:
>>>
>>>> 2018-05-23 14:29 GMT+09:00 Christian Huitema <huitema@huitema.net>:
>>>> > I like the proposal. In particular, I really like the encryption of
>>>> > handshake packets with the handshake key, as it does close a number =
of
>>>> > avenues for attacks. And I like that it solves the "ack promotion"
>>>> issue
>>>> > that I was complaining against for some time. Turns out that in the
>>>> current
>>>> > draft, it is very hard to contain that problem if you enable client
>>>> auth.
>>>> >
>>>> >
>>>> > On the other hand, I agree with Martin that a lot of the additions t=
o
>>>> > transmission recovery should be moved to separate PRs. I am not
>>>> enthusiastic
>>>> > with the EMPTY ACK mechanism, or with the proposed "implicit
>>>> > acknowledgement" of a lower crypto stream by a higher level ack.
>>>>
>>>> At the moment I do not have a strong opinion on the Empty ACK mechanis=
m.
>>>>
>>>> However, regarding how we close the Initial and Handshake contexts, my
>>>> preference goes to using implicit ACKs (i.e. use the successful
>>>> receipt of a packet that is protected under a higher level of
>>>> encryption key as the signal) rather than explicitly ACKing the last
>>>> flight of data.
>>>>
>>>> As I see, there are two downsides in the Explicit ACKing approach.
>>>>
>>>> * Explicit ACKing requires sending two additional packets during the
>>>> handshake, which means that we would have more AES operations plus
>>>> somewhere around 60 bytes of overhead on the wire.
>>>> * Explicit ACKing requires more signaling from the TLS stack. In case
>>>> of implicit ACKing, the TLS stack need to only provide the AEAD
>>>> contexts and the messages, whereas in case of explicit ACKing, the TLS
>>>> stack also needs to provide a signal indicating the end of the
>>>> transmission at each encryption level.
>>>>
>>>> The downside of the implicit ACKing approach is that the server needs
>>>> to signal the termination of the Handshake context using a special
>>>> frame sent using a 1-RTT packet.
>>>>
>>>> But even taking that into consideration, I think that implicit ACKing
>>>> is still easier to implement, considering the need for the additional
>>>> signal in the explicit ACK case that have been described above.
>>>>
>>>>
>>>> > In any
>>>> > case, starting as simple as possible would help having the first
>>>> > implementations and tests.
>>>> >
>>>> >
>>>> > On 5/22/2018 8:26 PM, Subodh Iyengar wrote:
>>>> >
>>>> > As an implementor of fizz, I support this design and am willing to
>>>> implement
>>>> > this as well.
>>>> >
>>>> >
>>>> > While this is a change in the API that TLS classically exposes, I
>>>> think this
>>>> > is the right tradeoff because it helps make things way more explicit
>>>> which
>>>> > will prevent several other bugs from happening in the future.
>>>> >
>>>> >
>>>> > Subodh
>>>> >
>>>> > ________________________________
>>>> > From: QUIC <quic-bounces@ietf.org> on behalf of Martin Thomson
>>>> > <martin.thomson@gmail.com>
>>>> > Sent: Tuesday, May 22, 2018 8:00:40 PM
>>>> > To: Ian Swett
>>>> > Cc: ekr@mozilla.com; QUIC WG
>>>> > Subject: Re: Stream0 Design Team Proposal
>>>> >
>>>> > First of all, thanks to the design team for the work they have done.
>>>> I
>>>> > haven't digested everything yet, but I think that I have a good sens=
e
>>>> of
>>>> > the shape of the proposal.
>>>> >
>>>> > Overall, this looks like a workable design.  It's a lot more invasiv=
e
>>>> of
>>>> > the cryptographic handshake implementation than I had thought people
>>>> were
>>>> > willing to stomach originally.  But it's clear that we've run into
>>>> problems
>>>> > with the current, more abstract API and this is a fairly natural way
>>>> to
>>>> > split TLS.  I've spent a little time thinking about how this might b=
e
>>>> > implemented and I think that it's not going to be *too* painful.  Th=
e
>>>> proof
>>>> > will be in the pudding there though.
>>>> >
>>>> > In looking at the PR, I really appreciate seeing all the changes
>>>> together..
>>>> > BTW, the link above points to the wrong PR, so be careful (it appear=
s
>>>> to
>>>> > have the same content, but that's not guaranteed).  The actual PR is
>>>> here:
>>>> > https://github.com/quicwg/base-drafts/pull/1377
>>>> >
>>>> > I've pushed a branch to the main repo so that you can preview the
>>>> entire
>>>> > document set:
>>>> > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__quicwg.
>>>> github.io_base-2Ddrafts_stream0_&d=3DDwIBaQ&c=3D5VD0RTtNlTh3ycd4
>>>> 1b3MUw&r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&m=3D_vGK3zTKFrMOkFihJnPntLYw1T
>>>> 0_NEMiHYSM0Q_u1JA&s=3DususmtxI3BTaLlBWe_HkQUWRH4sBI0Cggj1oWZMBHak&e=3D
>>>> >
>>>> > It seems like there are some core changes here and a bunch of
>>>> separable or
>>>> > at least secondary changes.  I'm sure that each one has its own
>>>> > justification, but that isn't always clear. The following changes
>>>> seem like
>>>> > they are separable:
>>>> >
>>>> > * The use of separate packet number spaces
>>>> > * The Retry packet changes (and NEW_TOKEN)
>>>> > * EMPTY_ACK
>>>> > * The TLS extension for flow control
>>>> >
>>>> > Right now, some of these appear to be entirely gratuitous.  I'd like
>>>> to get
>>>> > to the bottom of each before we continue.
>>>> >
>>>> > At a minimum, the PR we land first should include just the core
>>>> changes.
>>>> > As you say, reviewing a monster PR like this will only make GitHub
>>>> weep
>>>> > unicorns, but we might be able to cut this into smaller pieces.
>>>> >
>>>> > On Wed, May 23, 2018 at 11:31 AM Ian Swett <ianswett=3D
>>>> > 40google.com@dmarc.ietf.org> wrote:
>>>> >
>>>> >> Dear QUIC WG,
>>>> >
>>>> >
>>>> >> On behalf of the Stream 0 Design Team, I am pleased to report that =
we
>>>> > have consensus on a proposed approach to share with the WG. The DT's
>>>> > proposal will make QUIC and TLS work closer together and incorporate=
s
>>>> ideas
>>>> > from DTLS, but it does not use the DTLS protocol itself.
>>>> >
>>>> >
>>>> >> The DT believes this solves the important open Stream 0 issues. The
>>>> > proposal will be a bit more invasive in TLS, but we believe it is th=
e
>>>> right
>>>> > long-term direction and several TLS stacks (BoringSSL, PicoTLS, NSS,
>>>> and
>>>> > Mint) are willing and able to do the work necessary.. A number of
>>>> stacks
>>>> > are currently working on implementations of this new approach, which
>>>> we
>>>> > hope to have in time for the Interim meeting.
>>>> >
>>>> >
>>>> >> A design document describing the overall approach can be found at:
>>>> >
>>>> >
>>>> > https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__docs.go
>>>> ogle.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j
>>>> 6SwHY8_edit&d=3DDwIBaQ&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3Dh3Ju9EBS7mHt
>>>> wg-wAyN7fQ&m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&s=3Dj
>>>> DNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg&e=3D
>>>> <https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__docs..google.c=
om_document_d_1fRsJqPinJl8N3b-2DbflDRV6auojfJLkxddT93j6SwHY8_edit&d=3DDwIBa=
Q&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&m=3D_vGK3zTKFrMOkFi=
hJnPntLYw1T0_NEMiHYSM0Q_u1JA&s=3DjDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVG=
g&e=3D>
>>>> >
>>>> >
>>>> >> A PR making the changes to the QUIC documents can be found at:
>>>> >
>>>> >> https://github.com/quicwg/base-drafts/pull/1377
>>>> >
>>>> >
>>>> >> A few design details did not have clear consensus, but it was felt =
it
>>>> > would be better to discuss those in the wider WG than delay the desi=
gn
>>>> > team.  A consistent choice was made in the PR and these issues are
>>>> > mentioned in Appendix B of the design doc.
>>>> >
>>>> >
>>>> >> As always, comments and questions welcome. That said, this is a big
>>>> PR
>>>> > and we recognize that some editorial work is going to be needed befo=
re
>>>> > merging. In the interest of letting people follow along, and to keep
>>>> github
>>>> > from falling over, we ask people to keep discussion on the mailing
>>>> list and
>>>> > refrain from making PR comments.
>>>> >
>>>> >
>>>> >> See you in Kista!
>>>> >
>>>> >
>>>> >> Ian and Eric
>>>> >
>>>> >
>>>>
>>>>
>>>>
>>>> --
>>>> Kazuho Oku
>>>>
>>>>
>>>
>>
>>
>

--000000000000571f24056cebb070
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">On Wed, May 23, 2018 at 8:54 PM, Christian Huitema <span d=
ir=3D"ltr">&lt;<a href=3D"mailto:huitema@huitema.net" target=3D"_blank">hui=
tema@huitema.net</a>&gt;</span> wrote:<br><div class=3D"gmail_extra"><div c=
lass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0 0 =
0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto">What =
vulnerability? At a minimum, reflection Dos.<div>Send UDP packet with &quot=
;0rtt&quot; content. Trigger emty-ack.<span class=3D"HOEnZb"><font color=3D=
"#888888"><br></font></span></div></div></blockquote><div><br></div><div>Gi=
ven that you can already trigger transmission of the full cert chain with C=
H, this doesn&#39;t seem very interesting.</div><div><br></div><div>-Ekr</d=
iv><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .=
8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir=3D"auto"><div><sp=
an class=3D"HOEnZb"><font color=3D"#888888"><br><div id=3D"m_-5404312927767=
375629AppleMailSignature">-- Christian Huitema=C2=A0</div></font></span><di=
v><div class=3D"h5"><div><br>On May 23, 2018, at 7:45 PM, Eric Rescorla &lt=
;<a href=3D"mailto:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt; wro=
te:<br><br></div><blockquote type=3D"cite"><div><div dir=3D"ltr"><br><div c=
lass=3D"gmail_extra"><br><div class=3D"gmail_quote">On Wed, May 23, 2018 at=
 7:10 PM, Christian Huitema <span dir=3D"ltr">&lt;<a href=3D"mailto:huitema=
@huitema.net" target=3D"_blank">huitema@huitema.net</a>&gt;</span> wrote:<b=
r><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:=
1px #ccc solid;padding-left:1ex">
 =20
   =20
 =20
  <div text=3D"#000000" bgcolor=3D"#FFFFFF">
    <p>I dislike the EMPTY_ACK because they are &quot;responses to somethin=
g
      that could not be decrypted&quot;. You don&#39;t know where the packe=
t came
      from, it could be spoofed. So you have on one hand a possible
      optimization, on the other hand a possible vulnerability, and in
      all cases additional complexity.<br></p></div></blockquote><div>What&=
#39;s the vulnerability? Anything more than a spurious retransmit?<br></div=
><div><br></div><div>-Ekr</div><div><br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex=
"><div text=3D"#000000" bgcolor=3D"#FFFFFF"><p>
    </p><div><div class=3D"m_-5404312927767375629h5">
    <br>
    <div class=3D"m_-5404312927767375629m_2322101816431292516moz-cite-prefi=
x">On 5/23/2018 4:27 PM, Jana Iyengar
      wrote:<br>
    </div>
    <blockquote type=3D"cite">
      <div dir=3D"ltr">
        <div>(Moving more discussions from main thread)</div>
        <div><br>
        </div>
        ---------- Forwarded message ----------<br>
        From:<span>=C2=A0</span><b class=3D"gmail_sendername">Subodh Iyenga=
r</b><span>=C2=A0</span><span dir=3D"ltr">&lt;<a href=3D"mailto:subodh@fb.c=
om" target=3D"_blank">subodh@fb.com</a>&gt;</span><br>
        Date: Wed, May 23, 2018 at 3:37 PM<br>
        Subject: Re: Stream0 Design Team Proposal<br>
        To: Mike Bishop &lt;<a href=3D"mailto:mbishop@evequefou.be" target=
=3D"_blank">mbishop@evequefou.be</a>&gt;, Christian
        Huitema &lt;<a href=3D"mailto:huitema@huitema.net" target=3D"_blank=
">huitema@huitema.net</a>&gt;, &quot;<a href=3D"mailto:quic@ietf.org" targe=
t=3D"_blank">quic@ietf.org</a>&quot;
        &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic@ietf.or=
g</a>&gt;<br>
        <br>
        <br>
        <div dir=3D"ltr">
          <div id=3D"m_-5404312927767375629m_2322101816431292516gmail-m_-63=
73418337459262039divtagdefaultwrapper" dir=3D"ltr" style=3D"font-size:12pt;=
color:rgb(0,0,0);font-family:Calibri,Helvetica,sans-serif">
            <p style=3D"margin-top:0px;margin-bottom:0px">FWIW I see
              EMPTY_ACKs as being very similar to a Duplicate ack. We
              thought about using Duplicate acks as well but we thought
              that EMPTY_ACks would be simpler to implement and be able
              to convey similar=C2=A0information.<br>
            </p>
            <p style=3D"margin-top:0px;margin-bottom:0px"><br>
            </p>
            <p style=3D"margin-top:0px;margin-bottom:0px">Subodh<br>
            </p>
          </div>
          <hr style=3D"display:inline-block;width:1427.78px">
          <div id=3D"m_-5404312927767375629m_2322101816431292516gmail-m_-63=
73418337459262039divRplyFwdMsg" dir=3D"ltr"><font style=3D"font-size:11pt" =
face=3D"Calibri, sans-serif" color=3D"#000000"><b>From:</b><span>=C2=A0</sp=
an>QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" style=3D"color:rgb(17,=
85,204)" target=3D"_blank">quic-bounces@ietf.org</a>&gt;
              on behalf of Mike Bishop &lt;<a href=3D"mailto:mbishop@eveque=
fou.be" style=3D"color:rgb(17,85,204)" target=3D"_blank">mbishop@evequefou.=
be</a>&gt;<br>
              <b>Sent:</b><span>=C2=A0</span>Wednesday, May 23, 2018 3:26:3=
5
              PM<br>
              <b>To:</b><span>=C2=A0</span>Christian Huitema;<span>=C2=A0</=
span><a href=3D"mailto:quic@ietf.org" style=3D"color:rgb(17,85,204)" target=
=3D"_blank">quic@ietf.org</a><br>
              <b>Subject:</b><span>=C2=A0</span>RE: Stream0 Design Team
              Proposal</font>
            <div>=C2=A0</div>
          </div>
          <div>
            <div class=3D"m_-5404312927767375629m_2322101816431292516gmail-=
h5" style=3D"display:block;color:rgb(80,0,80)">
              <div style=3D"background-color:white" lang=3D"EN-US">
                <div class=3D"m_-5404312927767375629m_2322101816431292516gm=
ail-m_-6373418337459262039x_WordSection1">
                  <p class=3D"m_-5404312927767375629m_2322101816431292516gm=
ail-m_-6373418337459262039x_MsoNormal" style=3D"color:rgb(80,0,80);font-fam=
ily:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatur=
es:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;te=
xt-align:start;text-indent:0px;text-transform:none;white-space:normal;word-=
spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial=
;text-decoration-color:initial"><span style=3D"color:windowtext">Christian,=
 can you expand
                      on why you dislike the EMPTY_ACK?=C2=A0 Being able to
                      say =E2=80=9CI=E2=80=99ve received some packets from =
you, but am
                      unable to process any of them because I=E2=80=99m mis=
sing
                      some handshake data=E2=80=9D seems like a useful way =
to
                      short-circuit timeouts on clients.=C2=A0 It also
                      doesn=E2=80=99t commit the server to holding any stat=
e =E2=80=93
                      IIUC, a server could form a packet containing an
                      EMPTY_ACK and then discard its internal state
                      until it gets the retransmitted (or delayed)
                      Initial packet.</span></p>
                  <p class=3D"m_-5404312927767375629m_2322101816431292516gm=
ail-m_-6373418337459262039x_MsoNormal" style=3D"color:rgb(80,0,80);font-fam=
ily:arial,sans-serif;font-size:small;font-style:normal;font-variant-ligatur=
es:normal;font-variant-caps:normal;font-weight:400;letter-spacing:normal;te=
xt-align:start;text-indent:0px;text-transform:none;white-space:normal;word-=
spacing:0px;background-color:rgb(255,255,255);text-decoration-style:initial=
;text-decoration-color:initial"><span style=3D"color:windowtext">=C2=A0</sp=
an></p>
                  <div style=3D"color:rgb(80,0,80);font-family:arial,sans-s=
erif;font-size:small;font-style:normal;font-variant-ligatures:normal;font-v=
ariant-caps:normal;font-weight:400;letter-spacing:normal;text-align:start;t=
ext-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;back=
ground-color:rgb(255,255,255);text-decoration-style:initial;text-decoration=
-color:initial">
                    <div style=3D"border-right:none;border-bottom:none;bord=
er-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt 0in 0in"><br=
 class=3D"m_-5404312927767375629m_2322101816431292516gmail-Apple-interchang=
e-newline">
                    </div>
                  </div>
                </div>
              </div>
            </div>
          </div>
        </div>
        <br>
        <div class=3D"gmail_extra"><br>
          <div class=3D"gmail_quote">On Wed, May 23, 2018 at 4:25 PM, Jana
            Iyengar <span dir=3D"ltr">&lt;<a href=3D"mailto:jri.ietf@gmail.=
com" target=3D"_blank">jri.ietf@gmail.com</a>&gt;</span>
            wrote:<br>
            <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;bo=
rder-left:1px #ccc solid;padding-left:1ex">
              <div dir=3D"ltr">(Forking this discussion off from the main
                thread.)<br>
                <div class=3D"gmail_extra"><br>
                  <div class=3D"gmail_quote">On Wed, May 23, 2018 at 2:13
                    AM, Kazuho Oku <span dir=3D"ltr">&lt;<a href=3D"mailto:=
kazuhooku@gmail.com" target=3D"_blank">kazuhooku@gmail.com</a>&gt;</span>
                    wrote:<br>
                    <blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>2018-05-23
                        14:29 GMT+09:00 Christian Huitema &lt;<a href=3D"ma=
ilto:huitema@huitema.net" target=3D"_blank">huitema@huitema.net</a>&gt;:<br=
>
                        &gt; I like the proposal. In particular, I
                        really like the encryption of<br>
                        &gt; handshake packets with the handshake key,
                        as it does close a number of<br>
                        &gt; avenues for attacks. And I like that it
                        solves the &quot;ack promotion&quot; issue<br>
                        &gt; that I was complaining against for some
                        time. Turns out that in the current<br>
                        &gt; draft, it is very hard to contain that
                        problem if you enable client auth.<br>
                        &gt;<br>
                        &gt;<br>
                        &gt; On the other hand, I agree with Martin that
                        a lot of the additions to<br>
                        &gt; transmission recovery should be moved to
                        separate PRs. I am not enthusiastic<br>
                        &gt; with the EMPTY ACK mechanism, or with the
                        proposed &quot;implicit<br>
                        &gt; acknowledgement&quot; of a lower crypto stream
                        by a higher level ack.<br>
                        <br>
                      </span>At the moment I do not have a strong
                      opinion on the Empty ACK mechanism.<br>
                      <br>
                      However, regarding how we close the Initial and
                      Handshake contexts, my<br>
                      preference goes to using implicit ACKs (i.e. use
                      the successful<br>
                      receipt of a packet that is protected under a
                      higher level of<br>
                      encryption key as the signal) rather than
                      explicitly ACKing the last<br>
                      flight of data.<br>
                      <br>
                      As I see, there are two downsides in the Explicit
                      ACKing approach.<br>
                      <br>
                      * Explicit ACKing requires sending two additional
                      packets during the<br>
                      handshake, which means that we would have more AES
                      operations plus<br>
                      somewhere around 60 bytes of overhead on the wire.<br=
>
                      * Explicit ACKing requires more signaling from the
                      TLS stack. In case<br>
                      of implicit ACKing, the TLS stack need to only
                      provide the AEAD<br>
                      contexts and the messages, whereas in case of
                      explicit ACKing, the TLS<br>
                      stack also needs to provide a signal indicating
                      the end of the<br>
                      transmission at each encryption level.<br>
                      <br>
                      The downside of the implicit ACKing approach is
                      that the server needs<br>
                      to signal the termination of the Handshake context
                      using a special<br>
                      frame sent using a 1-RTT packet.<br>
                      <br>
                      But even taking that into consideration, I think
                      that implicit ACKing<br>
                      is still easier to implement, considering the need
                      for the additional<br>
                      signal in the explicit ACK case that have been
                      described above.<br>
                      <div>
                        <div class=3D"m_-5404312927767375629m_2322101816431=
292516m_-1934665759982005286h5"><br>
                          <br>
                          &gt; In any<br>
                          &gt; case, starting as simple as possible
                          would help having the first<br>
                          &gt; implementations and tests.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt; On 5/22/2018 8:26 PM, Subodh Iyengar
                          wrote:<br>
                          &gt;<br>
                          &gt; As an implementor of fizz, I support this
                          design and am willing to implement<br>
                          &gt; this as well.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt; While this is a change in the API that
                          TLS classically exposes, I think this<br>
                          &gt; is the right tradeoff because it helps
                          make things way more explicit which<br>
                          &gt; will prevent several other bugs from
                          happening in the future.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt; Subodh<br>
                          &gt;<br>
                          &gt; ______________________________<wbr>__<br>
                          &gt; From: QUIC &lt;<a href=3D"mailto:quic-bounce=
s@ietf.org" target=3D"_blank">quic-bounces@ietf.org</a>&gt;
                          on behalf of Martin Thomson<br>
                          &gt; &lt;<a href=3D"mailto:martin.thomson@gmail.c=
om" target=3D"_blank">martin.thomson@gmail.com</a>&gt;<br>
                          &gt; Sent: Tuesday, May 22, 2018 8:00:40 PM<br>
                          &gt; To: Ian Swett<br>
                          &gt; Cc: <a href=3D"mailto:ekr@mozilla.com" targe=
t=3D"_blank">ekr@mozilla.com</a>;
                          QUIC WG<br>
                          &gt; Subject: Re: Stream0 Design Team Proposal<br=
>
                          &gt;<br>
                          &gt; First of all, thanks to the design team
                          for the work they have done.=C2=A0 I<br>
                          &gt; haven&#39;t digested everything yet, but I
                          think that I have a good sense of<br>
                          &gt; the shape of the proposal.<br>
                          &gt;<br>
                          &gt; Overall, this looks like a workable
                          design.=C2=A0 It&#39;s a lot more invasive of<br>
                          &gt; the cryptographic handshake
                          implementation than I had thought people were<br>
                          &gt; willing to stomach originally.=C2=A0 But it&=
#39;s
                          clear that we&#39;ve run into problems<br>
                          &gt; with the current, more abstract API and
                          this is a fairly natural way to<br>
                          &gt; split TLS.=C2=A0 I&#39;ve spent a little tim=
e
                          thinking about how this might be<br>
                          &gt; implemented and I think that it&#39;s not
                          going to be *too* painful.=C2=A0 The proof<br>
                          &gt; will be in the pudding there though.<br>
                          &gt;<br>
                        </div>
                      </div>
                      &gt; In looking at the PR, I really appreciate
                      seeing all the changes together..<br>
                      <div class=3D"m_-5404312927767375629m_232210181643129=
2516m_-1934665759982005286HOEnZb">
                        <div class=3D"m_-5404312927767375629m_2322101816431=
292516m_-1934665759982005286h5">&gt; BTW,
                          the link above points to the wrong PR, so be
                          careful (it appears to<br>
                          &gt; have the same content, but that&#39;s not
                          guaranteed).=C2=A0 The actual PR is here:<br>
                          &gt; <a href=3D"https://github.com/quicwg/base-dr=
afts/pull/1377" rel=3D"noreferrer" target=3D"_blank">https://github.com/qui=
cwg/base<wbr>-drafts/pull/1377</a><br>
                          &gt;<br>
                          &gt; I&#39;ve pushed a branch to the main repo so
                          that you can preview the entire<br>
                          &gt; document set:<br>
                          &gt; <a href=3D"https://urldefense.proofpoint.com=
/v2/url?u=3Dhttps-3A__quicwg.github.io_base-2Ddrafts_stream0_&amp;d=3DDwIBa=
Q&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&amp;m=3D_vG=
K3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q_u1JA&amp;s=3DususmtxI3BTaLlBWe_HkQUWRH4=
sBI0Cggj1oWZMBHak&amp;e=3D" rel=3D"noreferrer" target=3D"_blank">https://ur=
ldefense.proofpoint.<wbr>com/v2/url?u=3Dhttps-3A__quicwg.<wbr>github.io_bas=
e-2Ddrafts_stream<wbr>0_&amp;d=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd4<wbr>1b3MUw=
&amp;r=3Dh3Ju9EBS7mHtwg-wAyN7f<wbr>Q&amp;m=3D_vGK3zTKFrMOkFihJnPntLYw1T<wbr=
>0_NEMiHYSM0Q_u1JA&amp;s=3DususmtxI3B<wbr>TaLlBWe_HkQUWRH4sBI0Cggj1oWZMB<wb=
r>Hak&amp;e=3D</a><br>
                          &gt;<br>
                          &gt; It seems like there are some core changes
                          here and a bunch of separable or<br>
                          &gt; at least secondary changes.=C2=A0 I&#39;m su=
re
                          that each one has its own<br>
                          &gt; justification, but that isn&#39;t always
                          clear. The following changes seem like<br>
                          &gt; they are separable:<br>
                          &gt;<br>
                          &gt; * The use of separate packet number
                          spaces<br>
                          &gt; * The Retry packet changes (and
                          NEW_TOKEN)<br>
                          &gt; * EMPTY_ACK<br>
                          &gt; * The TLS extension for flow control<br>
                          &gt;<br>
                          &gt; Right now, some of these appear to be
                          entirely gratuitous.=C2=A0 I&#39;d like to get<br=
>
                          &gt; to the bottom of each before we continue.<br=
>
                          &gt;<br>
                          &gt; At a minimum, the PR we land first should
                          include just the core changes.<br>
                          &gt; As you say, reviewing a monster PR like
                          this will only make GitHub weep<br>
                          &gt; unicorns, but we might be able to cut
                          this into smaller pieces.<br>
                          &gt;<br>
                          &gt; On Wed, May 23, 2018 at 11:31 AM Ian
                          Swett &lt;ianswett=3D<br>
                          &gt; <a href=3D"mailto:40google.com@dmarc.ietf.or=
g" target=3D"_blank">40google.com@dmarc.ietf.org</a>&gt;
                          wrote:<br>
                          &gt;<br>
                          &gt;&gt; Dear QUIC WG,<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; On behalf of the Stream 0 Design
                          Team, I am pleased to report that we<br>
                          &gt; have consensus on a proposed approach to
                          share with the WG. The DT&#39;s<br>
                          &gt; proposal will make QUIC and TLS work
                          closer together and incorporates ideas<br>
                          &gt; from DTLS, but it does not use the DTLS
                          protocol itself.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; The DT believes this solves the
                          important open Stream 0 issues. The<br>
                          &gt; proposal will be a bit more invasive in
                          TLS, but we believe it is the right<br>
                          &gt; long-term direction and several TLS
                          stacks (BoringSSL, PicoTLS, NSS, and<br>
                          &gt; Mint) are willing and able to do the work
                          necessary.. A number of stacks<br>
                          &gt; are currently working on implementations
                          of this new approach, which we<br>
                          &gt; hope to have in time for the Interim
                          meeting.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; A design document describing the
                          overall approach can be found at:<br>
                          &gt;<br>
                          &gt;<br>
                          &gt; <a href=3D"https://urldefense.proofpoint.com=
/v2/url?u=3Dhttps-3A__docs..google.com_document_d_1fRsJqPinJl8N3b-2DbflDRV6=
auojfJLkxddT93j6SwHY8_edit&amp;d=3DDwIBaQ&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&am=
p;r=3Dh3Ju9EBS7mHtwg-wAyN7fQ&amp;m=3D_vGK3zTKFrMOkFihJnPntLYw1T0_NEMiHYSM0Q=
_u1JA&amp;s=3DjDNnz34hmWvLSQnHkSnYdihW-jG-0xZ-YYqKq30wVGg&amp;e=3D" rel=3D"=
noreferrer" target=3D"_blank">https://urldefense.proofpoint.<wbr>com/v2/url=
?u=3Dhttps-3A__docs.go<wbr>ogle.com_document_d_1fRsJqPinJ<wbr>l8N3b-2DbflDR=
V6auojfJLkxddT93j<wbr>6SwHY8_edit&amp;d=3DDwIBaQ&amp;c=3D5VD0RTt<wbr>NlTh3y=
cd41b3MUw&amp;r=3Dh3Ju9EBS7mHt<wbr>wg-wAyN7fQ&amp;m=3D_vGK3zTKFrMOkFihJ<wbr=
>nPntLYw1T0_NEMiHYSM0Q_u1JA&amp;s=3Dj<wbr>DNnz34hmWvLSQnHkSnYdihW-jG-0xZ<wb=
r>-YYqKq30wVGg&amp;e=3D</a><br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; A PR making the changes to the QUIC
                          documents can be found at:<br>
                          &gt;<br>
                          &gt;&gt; <a href=3D"https://github.com/quicwg/bas=
e-drafts/pull/1377" rel=3D"noreferrer" target=3D"_blank">https://github.com=
/quicwg/base<wbr>-drafts/pull/1377</a><br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; A few design details did not have
                          clear consensus, but it was felt it<br>
                          &gt; would be better to discuss those in the
                          wider WG than delay the design<br>
                          &gt; team.=C2=A0 A consistent choice was made in
                          the PR and these issues are<br>
                          &gt; mentioned in Appendix B of the design
                          doc.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; As always, comments and questions
                          welcome. That said, this is a big PR<br>
                          &gt; and we recognize that some editorial work
                          is going to be needed before<br>
                          &gt; merging. In the interest of letting
                          people follow along, and to keep github<br>
                          &gt; from falling over, we ask people to keep
                          discussion on the mailing list and<br>
                          &gt; refrain from making PR comments.<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; See you in Kista!<br>
                          &gt;<br>
                          &gt;<br>
                          &gt;&gt; Ian and Eric<br>
                          &gt;<br>
                          &gt;<br>
                          <br>
                          <br>
                          <span class=3D"m_-5404312927767375629m_2322101816=
431292516HOEnZb"><font color=3D"#888888">
                              <br>
                            </font></span></div>
                      </div>
                      <span class=3D"m_-5404312927767375629m_23221018164312=
92516HOEnZb"><font color=3D"#888888"><span class=3D"m_-5404312927767375629m=
_2322101816431292516m_-1934665759982005286HOEnZb"><font color=3D"#888888">-=
- <br>
                              Kazuho Oku<br>
                              <br>
                            </font></span></font></span></blockquote>
                  </div>
                  <br>
                </div>
              </div>
            </blockquote>
          </div>
          <br>
        </div>
      </div>
    </blockquote>
    <br>
  </div></div></div>

</blockquote></div><br></div></div>
</div></blockquote></div></div></div></div></blockquote></div><br></div></d=
iv>

--000000000000571f24056cebb070--


From nobody Wed May 23 21:41:56 2018
Return-Path: <w@1wt.eu>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AA3561204DA for <quic@ietfa.amsl.com>; Wed, 23 May 2018 21:41:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 EfkYX1NlhDRw for <quic@ietfa.amsl.com>; Wed, 23 May 2018 21:41:52 -0700 (PDT)
Received: from 1wt.eu (wtarreau.pck.nerim.net [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id E6F3A1200A0 for <quic@ietf.org>; Wed, 23 May 2018 21:41:51 -0700 (PDT)
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id w4O4fk1d005233; Thu, 24 May 2018 06:41:46 +0200
Date: Thu, 24 May 2018 06:41:46 +0200
From: Willy Tarreau <w@1wt.eu>
To: Mike Bishop <mbishop@evequefou.be>
Cc: HTTP Working Group <ietf-http-wg@w3.org>, "quic@ietf.org" <quic@ietf.org>
Subject: Re: QPACK and the Static Table
Message-ID: <20180524044146.GA5215@1wt.eu>
References: <SN1PR08MB1854395A2875541C4DC0673DDA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <SN1PR08MB1854395A2875541C4DC0673DDA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/SchKU2lPOkQ5G_IEaE7VEPzzc2w>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 04:41:55 -0000

Hi Mike,

On Wed, May 23, 2018 at 11:16:18PM +0000, Mike Bishop wrote:
> Rather than indexing the tables together and having the static table at 1-61,
> QPACK uses a bit to indicate static vs. dynamic.  Since the field is seven
> bits long, the performance is comparable for the dynamic table (you can
> access 63 entries in one byte, 190 in two), but you can increase the size of
> the static table without hurting the dynamic table.

It will make the code look less "magic"!

> As a result, we're
> building a fresh static
> table<https://github.com/quicwg/base-drafts/pull/1355> based on queries
> against HTTPArchive data.
> 
> The key question that has come up in a couple venues:  What real-world
> headers do we want to artificially remove from what the data shows, and what
> headers not seen by HTTP Archive do we want to force in anyway?

I agree with Mark that request really is what matters the most.

>   *   Reordered to put headers you're likely to name-reference at the front,
>   especially if you're unlikely to add them to the dynamic table

Well, some of us have been really bothered by the lack of ordering
in the HPACK headers table, making it painful to perform efficient
lookups. I'd suggest that they are sorted by (name,value) to make
it possible to perform efficient dichotomic lookups.

> The question is whether we should also backfill headers which HTTP Archive
> wouldn't see, delete headers we wish people wouldn't use, and/or insert the
> ones we hope they eventually will.  Some candidates:

That's indeed a good point.

>   *   Add Alt-Svc entry for HTTP/QUIC with QUIC v1
>   *   Add X-Forwarded-For
>   *   Don't add X-Forwarded-For, but do add Forwarded

In practice, we can take both or none. After all, most QUIC requests going
through proxies will be encrypted already thus the proxy will not be able
to add these fields. For clear-text requests, the header field name is
roughly as long as the value, so there's not *that* much to save by encoding
them. And it will not change in most consecutive requests, so the dynamic
compression will be more efficient than the static one. Thus I suggest that
we only add them *if* we have enough unused slots at the end that we care
to cover a very broad set.

>   *   Remove Expires to incent the use of Cache-Control

Expires is for responses only anyway, thus it matters much less. Cache-control
can be used in both directions. I think that the technical focus on request
may make Expires disappear from the table ;-)

>   *   Collapse the "Content-Type: <thingey>" and "Content-Type: <thingey>; charset=utf-8" entries together
>      *   ...but which one to keep?

Probably just focus on the most reported ones and not try to collapse. I
suspect that we see a lot of en-us alone, and utf-8 added to some other
languages, but I could be wrong.

>   *   Add Content-Encoding and/or Accept-Encoding entries for zstd

Probably too early yet, and will not make a big difference overall (almost
only response, 4 characters value).

> There's an endless parade of bikesheds here.  As Martin has pointed out, this
> will never be perfect, so the goal is "good enough and keep going."  Any
> strong feelings about any of these before we merge it?

No real strong feeling here except about the ability to perform fast lookups.

> Also, there's been some discussion of a mechanism for selecting one of
> several static tables at the start of a connection.  In that case, the spec
> would probably define three tables (client headers, server headers [for
> servers that don't push], combined [for servers that push]) and enable future
> RFCs to define others for targeted scenarios (proxies, video playback, IoT,
> etc.).  How much does that interest folks?

I think it could be a good solution. We could also think about APIs and
various datacenter-oriented use cases (eg: webservice etc) where very fast
response and network efficiency matters. It could be a way to encourage
QUIC adoption inside the DC. The risk however is that tables defined too
late are never deployed due to interoperability concerns (unless there's
a way to know that it will be supported before encoding). Thus if some
participants are interested in optimizing for certain use cases, they should
probably provide their own tables to be merged into the standard from day 1.

Cheers,
Willy


From nobody Wed May 23 21:44:04 2018
Return-Path: <martin.thomson@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC5911204DA for <quic@ietfa.amsl.com>; Wed, 23 May 2018 21:44:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 00Ydr-EAW7M6 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 21:44:00 -0700 (PDT)
Received: from mail-ot0-x22f.google.com (mail-ot0-x22f.google.com [IPv6:2607:f8b0:4003:c0f::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 745211200A0 for <quic@ietf.org>; Wed, 23 May 2018 21:44:00 -0700 (PDT)
Received: by mail-ot0-x22f.google.com with SMTP id t1-v6so372973oth.8 for <quic@ietf.org>; Wed, 23 May 2018 21:44:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Re32adJoIhdI6DVhDYzV/VlGJgPRHOBLsMZKRW1PK1M=; b=sSmHC3W1gqUBMjKglSyKIAQrSTE26OLLnNm3+9i2gjdIe8jLD4DsUCPaAjTCX7uw1b BXxc1pV6ABgVUeokfsIo60z3yzAwN9GOUSldmXtmPo79b/UJ/zc9xO2gPrQsNYF/Y3cG i3JwIxcJuTsEJCHlik06+p/NNoKw00WT/Rnw5oQJg+oweHqFDBvsP3jjHikPAZ9+Z9vV mkCszNtLAhhbIFnQY/Ay2FsA7dDuTt7hj6Cnifi9bJegmo+SE/IiiXOotMWHkJ93zZ7n Xs/J77fpMdTPuPDmAMX1TcAjtGHzrStNbPkDG0FTGBbpQN6IQd2Z2LbdatNfbuV9EiKI kq7w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Re32adJoIhdI6DVhDYzV/VlGJgPRHOBLsMZKRW1PK1M=; b=qNi7Zf0KHg5DbhMDbwWbGO8nW6I664nb++rkc/1OM/MisynKimms9MhaTZ4d5etMgk hVY2UqQPvDf23DJjR4OHrmi1cZF4ljy6+TnVyxIMWU+UicYROktdMZJbXku924mnZGb7 e9wLvj7m8DQIxZec6bEQcmi4eoI9DjiC9XreHzG4yjTLS2LipEOaTdC4HM9Ye5Lgir3y oNzWoTp1EKXYOAgGeJNzqIU2fl6s2vZUT9IMIkiAivkKYV4SrEk9GF2nGrIyJiNf89Cy jfXR4FuyjP6H5gKH2S/tTXV3QO6yKJ/g2WHlyO4J3YPuJAoxO5RG6c47bv49vlO0LHuF x38Q==
X-Gm-Message-State: ALKqPwfypCC0NTBselAKC2e73lmmbmo1TJA0r+pnz12o58sTaJWzmqrK hx2hF8zr8KEArMPBLUcC+n0QlWV+mrQSF0HPXNg=
X-Google-Smtp-Source: AB8JxZpmG4OuErp2S37rN3jY/9b7SZlj0grskowXwKbsOqRWeoikWEnDgDK+A9HJkT0UqvPBfWQqr4klCHJlPxAVx+Q=
X-Received: by 2002:a9d:3ea5:: with SMTP id b34-v6mr3371574otc.283.1527137039627;  Wed, 23 May 2018 21:43:59 -0700 (PDT)
MIME-Version: 1.0
References: <CANatvzwN1kVO3ofvyYX9cg=cKcg4FdqUT3VB6hneEDa5UjT_0w@mail.gmail.com>
In-Reply-To: <CANatvzwN1kVO3ofvyYX9cg=cKcg4FdqUT3VB6hneEDa5UjT_0w@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 24 May 2018 14:43:49 +1000
Message-ID: <CABkgnnUjw4WYDv5mmsFp2nDq4LtdJBzsgdFkxFzEdHrA37tejw@mail.gmail.com>
Subject: Re: Stream0 Proposal: Explicit vs. Implicit ACK (Re: Stream0 Design Team Proposal)
To: Kazuho Oku <kazuhooku@gmail.com>
Cc: Jana Iyengar <jri.ietf@gmail.com>, ekr@mozilla.com, QUIC WG <quic@ietf.org>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/kdyE2nGc4EpYXNw3CZUulNvhlfg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 04:44:03 -0000

The obvious solution for the problem of not retransmitting the client
Finished is to retransmit it until it is acknowledged.  With the proposed
design, that means that the server sends a Handshake message after the
handshake is done, which I think is fine.  If the client sends Finished
until it is acknowledged, then I think we're good.

I can see the appeal in saying that if you receive an ACK for 1-RTT data
then your Handshake packets must have been received.  I can see that
working even, but you have to be careful.  It's just a signal that you can
stop sending CRYPTO frames, not that you are done with the keys.  You might
need to send ACK again and you might still receive packets at that level.
You could drop read keys and ACK only the old packets that you did decrypt,
but I suspect that it's better to authenticate any packet and ACK
faithfully, which would be better for your peer's congestion state.

That also means that you probably need to have timers for cleaning up, to
avoid the pathological case where acknowledgments are sent indefinitely.

I think that the FIN bit idea might work to close out the use of the
"stream" for each set of keys. That is, as opposed to the crypto stream as
a whole.  But it's duplicative: the crypto handshake needs to know when it
moves from one set of keys to the next and replicating that signaling at
the QUIC layer only really adds things to check for consistency.
On Thu, May 24, 2018 at 11:07 AM Kazuho Oku <kazuhooku@gmail.com> wrote:

> 2018-05-24 3:46 GMT+09:00 Jana Iyengar <jri.ietf@gmail.com>:

> > A thought occurs to me: a CRYPTO_HS frame with the fin bit set can be
used
> > to indicate that the handshake is done.This could be used as a signal
(aka
> > HANDSHAKE_DONE) to solve Marten's problem of a client rtxing a CFIN. Of
> > course, this would mean that this particular CRYPTO_HS frame would be
> > encrypted with a 1-RTT key... which *I think* is fine. What do you
think?

> I am not sure if that is a good approach.

> I would assume that we would like to keep the handshake flow on the
> 1-RTT key open for the lifetime of the QUIC connection, so that we
> could send things related to the TLS (e.g. session tickets). Sending
> FIN from the server right after receiving ClientFinished makes that
> impossible.

> Having said that, I do agree that the need for a dedicated frame is a
> pain. It is a pain because we need to have a retransmission logic for
> the frame.

> I think that you are making a good point in suggesting to consider
> reusing the retransmission logic that already exists for bidirectional
> flows. But as said, FIN bit does not seem like an answer in this case.

> IMO, ideally we should define a new TLS post-handshake message (that
> does not convey any data), and send that from the server in response
> to ClientFinished using 1-RTT packet. The message will act as a signal
> that the server has received ClientFinished.

> The benefit of this approach is that we can reuse the retransmission
> logic that will exist for handshake flows. The downside is that TLS
> stacks need to be aware of the new handshake message.

> Considering the fact that the Design Team is already suggesting a
> substantial change to the TLS stack, we might have chance in asking
> for the addition of a new handshake message. But I am not sure.

> --
> Kazuho Oku


From nobody Wed May 23 22:49:19 2018
Return-Path: <kazuhooku@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C705712D945 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 22:49:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 YaC7ItQVo36L for <quic@ietfa.amsl.com>; Wed, 23 May 2018 22:49:15 -0700 (PDT)
Received: from mail-pf0-x241.google.com (mail-pf0-x241.google.com [IPv6:2607:f8b0:400e:c00::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4E44112D944 for <quic@ietf.org>; Wed, 23 May 2018 22:49:14 -0700 (PDT)
Received: by mail-pf0-x241.google.com with SMTP id o76-v6so284382pfi.5 for <quic@ietf.org>; Wed, 23 May 2018 22:49:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=cVHhOGXo/EpzX4pagav4x0LxdVkoSkiQE2ltykr8PzY=; b=gE2cxTM9gxQWoAohdxhBvsbEvEW2rmDKsLz42RLv+peJq8J/avBpg6hgohWpu24Rvh WZjxwazx7NwoavOUoKByBLN8og4TztfXI2BPUVdcJGK2ZSb4uwt3JSbsdEy1sOcMNZ82 t694dkK8jl7Shh0C3/fpJxiH76DU/ORTtJNLtmbDGQxg4JnMZdzcJGk4VyApEwDc+l// 3wyzScOG6jyAZvMYJnYKv5O5BlWMqExiLHZB+7OdOKCBZk2Rj5mqMWSnMGVQ6KetsgU5 2+UrN+kkPa8pFhb/eP5ImPNlRprWFUN/SH1Hk9HNBjpiWhHZv1b47a/6PCUZQ267ykDt emMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=cVHhOGXo/EpzX4pagav4x0LxdVkoSkiQE2ltykr8PzY=; b=osmbKuA9+7tyuP/L3wGZlw9FP+y42EdqDgeXWGssaodKAHkw4emnuf6mTtbDw6dS/m ASiyv6NUUnfGshMJItCliQbCcjPrRmZblvnS21el6sg4KXYsBTWXiggs0WRAxT8w+Lat U9/7njt3UHtloyvnIUWNgqFP9/0Ake7T/VKLz9T0czKFtsmHzPwMoOIHOQ3Kv3e4v/YI 4BRBrn7YH2rnpDwCQa5M/V0/LTWaJkZLJzsf5pW8lSe1iMyBcIpPjV1QDPEonasjbxSk gi/esRxdNb6ZpZh9BxUvqWfKpS0r9Nnlrrp0iu6VG+gAffaaid+Iu/oCzxSSjjS50hv8 7cAQ==
X-Gm-Message-State: ALKqPwehUggFrAxeMKkP/xh4GdI3Sdx3/Ge8XTkLzOuNPF57M8hHG8eX MBqwLAlir4bHrpiOCNI+BETVTEvJRTAbTvdW8do=
X-Google-Smtp-Source: AB8JxZp7XGIpZzJJgacQA9gtV7635Mpf+VEjM4UU/V3gLPZRdQVw0viCWa1LFMIH69cJxWLorKW6abFckKuAJG/Fabk=
X-Received: by 2002:a62:ccdc:: with SMTP id j89-v6mr5887580pfk.182.1527140953515;  Wed, 23 May 2018 22:49:13 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:1189:0:0:0:0 with HTTP; Wed, 23 May 2018 22:49:12 -0700 (PDT)
In-Reply-To: <CABkgnnUjw4WYDv5mmsFp2nDq4LtdJBzsgdFkxFzEdHrA37tejw@mail.gmail.com>
References: <CANatvzwN1kVO3ofvyYX9cg=cKcg4FdqUT3VB6hneEDa5UjT_0w@mail.gmail.com> <CABkgnnUjw4WYDv5mmsFp2nDq4LtdJBzsgdFkxFzEdHrA37tejw@mail.gmail.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Thu, 24 May 2018 14:49:12 +0900
Message-ID: <CANatvzyNHpTFpdS6_A-gijn2+dOiU=zxyiRJsQuSZVy+EyZ1gQ@mail.gmail.com>
Subject: Re: Stream0 Proposal: Explicit vs. Implicit ACK (Re: Stream0 Design Team Proposal)
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Jana Iyengar <jri.ietf@gmail.com>, Eric Rescorla <ekr@mozilla.com>, QUIC WG <quic@ietf.org>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/JQAvSqYzNgsixCzpSJMTyeVRifs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 05:49:17 -0000

2018-05-24 13:43 GMT+09:00 Martin Thomson <martin.thomson@gmail.com>:
> The obvious solution for the problem of not retransmitting the client
> Finished is to retransmit it until it is acknowledged.  With the proposed
> design, that means that the server sends a Handshake message after the
> handshake is done, which I think is fine.  If the client sends Finished
> until it is acknowledged, then I think we're good.

I agree that that would work.

IIUC downsides compared to the implicit ACK approach are that the
server needs to keep the old keys for certain amount of time (e.g., 2
MSL) and that the additional Handshake packet will consume about 30
octets of the 3 packet window that we have for the server's first
flights.

> I can see the appeal in saying that if you receive an ACK for 1-RTT data
> then your Handshake packets must have been received.  I can see that
> working even, but you have to be careful.  It's just a signal that you can
> stop sending CRYPTO frames, not that you are done with the keys.  You might
> need to send ACK again and you might still receive packets at that level.
> You could drop read keys and ACK only the old packets that you did decrypt,
> but I suspect that it's better to authenticate any packet and ACK
> faithfully, which would be better for your peer's congestion state.
>
> That also means that you probably need to have timers for cleaning up, to
> avoid the pathological case where acknowledgments are sent indefinitely.

I agree with your argument about congestion control.

One way of acquiring correct congestion control information in the
implicit ACK approach will be to send coalesced packets that combines
a Handshake packet with a packet protected by a higher encryption key.
That will guarantee that you would receive an ACK for the delivery of
the datagrams, and you can feed the information to the congestion
controller.

FWIW, I have implemented implicit ACK in quicly, and it only required
about 40 additional lines of code, including the retransmission logic
for Handshake_Done. The code can be found at
https://github.com/h2o/quicly/pull/8/commits/eee6eb5fc7c0359edfeb0b8f89ae9ac191ef0758.
Coalesced packets is not implemented.

>
> I think that the FIN bit idea might work to close out the use of the
> "stream" for each set of keys. That is, as opposed to the crypto stream as
> a whole.  But it's duplicative: the crypto handshake needs to know when it
> moves from one set of keys to the next and replicating that signaling at
> the QUIC layer only really adds things to check for consistency.
> On Thu, May 24, 2018 at 11:07 AM Kazuho Oku <kazuhooku@gmail.com> wrote:
>
>> 2018-05-24 3:46 GMT+09:00 Jana Iyengar <jri.ietf@gmail.com>:
>
>> > A thought occurs to me: a CRYPTO_HS frame with the fin bit set can be
> used
>> > to indicate that the handshake is done.This could be used as a signal
> (aka
>> > HANDSHAKE_DONE) to solve Marten's problem of a client rtxing a CFIN. Of
>> > course, this would mean that this particular CRYPTO_HS frame would be
>> > encrypted with a 1-RTT key... which *I think* is fine. What do you
> think?
>
>> I am not sure if that is a good approach.
>
>> I would assume that we would like to keep the handshake flow on the
>> 1-RTT key open for the lifetime of the QUIC connection, so that we
>> could send things related to the TLS (e.g. session tickets). Sending
>> FIN from the server right after receiving ClientFinished makes that
>> impossible.
>
>> Having said that, I do agree that the need for a dedicated frame is a
>> pain. It is a pain because we need to have a retransmission logic for
>> the frame.
>
>> I think that you are making a good point in suggesting to consider
>> reusing the retransmission logic that already exists for bidirectional
>> flows. But as said, FIN bit does not seem like an answer in this case.
>
>> IMO, ideally we should define a new TLS post-handshake message (that
>> does not convey any data), and send that from the server in response
>> to ClientFinished using 1-RTT packet. The message will act as a signal
>> that the server has received ClientFinished.
>
>> The benefit of this approach is that we can reuse the retransmission
>> logic that will exist for handshake flows. The downside is that TLS
>> stacks need to be aware of the new handshake message.
>
>> Considering the fact that the Design Team is already suggesting a
>> substantial change to the TLS stack, we might have chance in asking
>> for the addition of a new handshake message. But I am not sure.
>
>> --
>> Kazuho Oku



-- 
Kazuho Oku


From nobody Wed May 23 22:54:13 2018
Return-Path: <kazuhooku@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EB51B1205F0 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 22:54:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 nO4FYxdCjl7m for <quic@ietfa.amsl.com>; Wed, 23 May 2018 22:54:09 -0700 (PDT)
Received: from mail-pl0-x230.google.com (mail-pl0-x230.google.com [IPv6:2607:f8b0:400e:c01::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3821012D948 for <quic@ietf.org>; Wed, 23 May 2018 22:54:09 -0700 (PDT)
Received: by mail-pl0-x230.google.com with SMTP id v24-v6so364489plo.3 for <quic@ietf.org>; Wed, 23 May 2018 22:54:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=+iD7jYdef3Q4MSgXQ6lokgU+cbR3Etfzwlxcpe4j4r0=; b=lRC4S+77C4NiY+n+iCUzEBoDnudVCwJpxAoQ41xb7jd9GcJY5ukdfkhzOcVAqAdrn+ nrbKqFXfCDhzwyr/o/yFBpGag06NULDKE8PGez8i+bA9UJwPs31NWi7bA2UXKj9Gp3aH rCwFeT/syMH9i8SNLRkdtXX83GDLfgtpUjd0CA57DMUQxzxgQJEHF7DkMAGfrU7JmY1o WRF7un4qlY7lTsE7v2XEuTjj6VBmX4/cFcMhIxdyVglX5KLJT4EXqY8nqMwlx3vz7agt SP+bZjf3qmrbV7dKMZ9bPIXnKXEBmm7gRR4NQF8F2Wm/pdc+V9UNdXN0Elq8uqxv7qIS 0N8w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=+iD7jYdef3Q4MSgXQ6lokgU+cbR3Etfzwlxcpe4j4r0=; b=X727aEOhkCU+cM7GqMvQC01iN2GOpZqUkSgzi/C3cwNM9uz6AgaeiRZHXRzzVYws9D Pbr6uR+bh0b1yPKXYQ468OukJzZ1oyX0F+HNxTkZA9BfEYt6Sf9px3REhlXm5MwU0ox4 Ix7SsD3Ui5Ud8zh0sQthhTR0z4RTlxeDR/EUqG99dSSfX1HEjGjDe8WPjdmHEQwomkw7 6exi+3At+nFxofcZzhRJkqVx3EkdR0IPR5ZxI3iJP+QnG4qEsYyRzJckSKvglggV7jqW 5j0a+VvDi8j98dS8+ZL+vVDQTJGZF3fQ95hmFeB2vYCKCgAZJvemF6wPT16DFC/inxuC 8yCA==
X-Gm-Message-State: ALKqPwfJi+nU2yhxiRgbpQRAciLosyG5XHu+NF0TJZDOfRll+0M9WK02 M0n8Y8CmpyAyDfJjiP0IV1iEBYGz7qX++fOw5eAkYw==
X-Google-Smtp-Source: AB8JxZpWE5t0I9s4jHUPVnhLC0MVK1i0dVN/LyYd/JJgJgnlx1oQCwKlL9qjRcH+FXj02zb2EEOA3E3CMl9SBRqkDw0=
X-Received: by 2002:a17:902:ba87:: with SMTP id k7-v6mr5914006pls.193.1527141248800;  Wed, 23 May 2018 22:54:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:1189:0:0:0:0 with HTTP; Wed, 23 May 2018 22:54:08 -0700 (PDT)
In-Reply-To: <fa325bc3-5bec-a120-05f2-76d41e0ec605@huitema.net>
References: <CANatvzyWK3OxTYx6EFRQG_tJ0tYmyvAd9-2HH2=cDVRhuUd2bQ@mail.gmail.com> <CABkgnnUe8yd5s+kyPvwXQ6RoSdFXbaL2P4j0_fkL_reVe7s+_Q@mail.gmail.com> <fa325bc3-5bec-a120-05f2-76d41e0ec605@huitema.net>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Thu, 24 May 2018 14:54:08 +0900
Message-ID: <CANatvzxEJnn6OCRBtqWoJkg0xn7LFo_x-U1t=pGoAObV4JEWNQ@mail.gmail.com>
Subject: Re: Stream0 Proposal: CRYPTO_HS frame encoding (Re: Stream0 Design Team Proposal)
To: Christian Huitema <huitema@huitema.net>
Cc: Martin Thomson <martin.thomson@gmail.com>, Jana Iyengar <jri.ietf@gmail.com>,  Eric Rescorla <ekr@mozilla.com>, QUIC WG <quic@ietf.org>,  Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/NvGLEC9XRD2N4ga_eUeACeDvHPE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 05:54:12 -0000

2018-05-24 11:07 GMT+09:00 Christian Huitema <huitema@huitema.net>:
> On 5/23/2018 5:41 PM, Martin Thomson wrote:
>
>> On Thu, May 24, 2018 at 10:06 AM Kazuho Oku <kazuhooku@gmail.com> wrote:
>>> 0x10 - 0x17: STREAM frame
>>> 0x18: CRYPTO_HS frame
>> ....
>>> I think that is workable, although it makes me sad because we will
>>> have more conditional branches.
>> Yeah.  We have an extremely limited space here.  And while Jana is right
>> that we haven't used much yet, we're only just starting.  As for
>> conditionals.  Maybe.  One way to implement this is a switch statement, and
>> those might not suffer as badly when you consider that you also have to
>> dispatch to other frame handlers in the same piece of code.
>>
>
> I am with Martin on this one. Just one code point for crypto frames,
> please. At best the optimization saves 2 bytes in the entire duration of
> the connection -- one byte for the CH, one byte for the first frame of
> the SH. And for the CH, you don't care because you are going to pas to
> min length anyhow.

FWIW, I disagree with the calculation.

My understanding is that having the OFF bit saves us 3 octets on the
server's flights and 2 to 3 octets on the client's flights per each
connection, because there will be 3 to 4 encryption levels and because
CRYPTO_HS will appear in all encryption levels except the client's
1-RTT flights.

The LEN bit has a bigger impact. It saves 4+2N octets where N is the
total number of Initial and Handshake packets sent by the server,
assuming that SH and NST will be larger than 63 octets.

So we will be using additional 13 octets in the first 3 packets that
the server sends.

OTOH, I do agree that additional 13 octets is big enough to justify
consuming more code points by itself. It's somewhere around 0.3% of
the amount of data you can send in 3 packets.

> You can still do common code with the "stream" data even without that,
> you just need two small branches of code to parse the stream id, stream
> offset, and stream fin. Just default to "stream=Crypto, stream offset=
> always present, stream fin= false" in the crypto branch.

The thing that makes me sad is the omission the FIN bit making the
encoding side complex.

With the FIN bit, we have the guarantee that a payload of any size can
be sent without additional overhead. That simplifies the encoder
logic. What you do is:

if (payload_len <= window - 2) {
    set_len_bit()
    varint_encode(len)
    emit_payload()
} else if (payload_len <= window) {
    if (payload_len != window)
        prepend_padding_before_the_frame()
    clear_len_bit()
    emit_payload()
} else {
    partial_write...
}

Without the FIN bit, the framing code becomes completely different
because we will always have the overhead of the length field, and the
length of the length field depends on the amount of payload or the
space we have.

>
> -- Christian Huitema
>



-- 
Kazuho Oku


From nobody Wed May 23 23:18:20 2018
Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 124F912D950 for <quic@ietfa.amsl.com>; Wed, 23 May 2018 23:18:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.998
X-Spam-Level: 
X-Spam-Status: No, score=-1.998 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 GAVUrkdMceaY for <quic@ietfa.amsl.com>; Wed, 23 May 2018 23:18:15 -0700 (PDT)
Received: from mail-pl0-x241.google.com (mail-pl0-x241.google.com [IPv6:2607:f8b0:400e:c01::241]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F6861200E5 for <quic@ietf.org>; Wed, 23 May 2018 23:18:15 -0700 (PDT)
Received: by mail-pl0-x241.google.com with SMTP id m24-v6so390885pls.11 for <quic@ietf.org>; Wed, 23 May 2018 23:18:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:cc:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :mime-version; bh=GCbhHGAy+J+muwjSBaWurkVNjUee1oGTZue8JVvGgmI=; b=LwBFbla7VXo3s5ey25dr/g18tGqpH7u8n8DK7f4NDDYXnd3taMwElqXIZgtyQZm3Uo bdAQ8EgZqE9jIVKOJXUC/IKO7tmbecuppbS9xTxRCc2+0xo3DFKt0SjcWVaiBuIscSMP d4kwgidFRYNmoKFSNSGHdtx0wdSKbGFZYaudRLPWmveYQVn5gAH6qpwk2HjIbAy9yv0N QrJOBcLMb7LpUU04oc68XRzMtMqNxzY78f2CfoOrRF0CADAbTQ7UQwf1M0VBvsmMEnmC DZQwp0S7u3+RJuXavhhwZzICyvV+7YP1Cx5Q2yXJaOHJaYU1OZhCN078mawzNK45/Pr2 +0JA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:thread-topic:thread-index :date:message-id:references:in-reply-to:accept-language :content-language:mime-version; bh=GCbhHGAy+J+muwjSBaWurkVNjUee1oGTZue8JVvGgmI=; b=OiogNz0m+U8hoXJdXFcK5ZLMoZdg6LfO7s/t5KARWkK3PnxA2EPyHWpSy5/xggCNI7 8YibxYwkOVmWyF33PSkm/BB1oo1x2LWvR/sEUL5ZCmrvUV3dVEeaKeZ1BEtNgM7SlCs0 i7BjZ+Uq6vkhaKC7VCPPIrVu3VzZDmrLC0vk/Mz3GNiGv2xTM/AHL67StkUbGekkF7wZ UMROqzEkFUiI3J1Sn44yBp7SxNFCtIUYuonKrFYVNGdh5wCH/6fT8LX0ht1PAJPgJppr QMHPSNNm47RwIVM6xYxAFTooqmHPp+bkDf5kZE0OOHNwamzT90lToIRsplt9f/bnBDTI a06w==
X-Gm-Message-State: ALKqPwfLo05n5n0Nm4lYb8VTrVWnIymygBFN7EH4204VkfMBh+5xKMfP SXLMMquyIF1ZHko25lQU7ns511GEKus=
X-Google-Smtp-Source: AB8JxZpvisFZjz9zoaHx7TwPrJTWl/GT8EBZEA8msYiCPY4luPQ3MJO8iAAOxOTZrhQ2S7RQsHRaiw==
X-Received: by 2002:a17:902:5a03:: with SMTP id q3-v6mr5015242pli.300.1527142694397;  Wed, 23 May 2018 23:18:14 -0700 (PDT)
Received: from DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM ([40.101.73.69]) by smtp.gmail.com with ESMTPSA id k2-v6sm40038424pfg.82.2018.05.23.23.18.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Wed, 23 May 2018 23:18:13 -0700 (PDT)
From: =?iso-8859-1?Q?Mikkel_Fahn=F8e_J=F8rgensen?= <mikkelfj@gmail.com>
To: Willy Tarreau <w@1wt.eu>, Mike Bishop <mbishop@evequefou.be>
CC: "quic@ietf.org" <quic@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Subject: Re: QPACK and the Static Table
Thread-Topic: QPACK and the Static Table
Thread-Index: ATA3MUExtIGgs/i5yafQYsNfY1TP4jVBNDAwxc3h1f4=
X-MS-Exchange-MessageSentRepresentingType: 2
Date: Thu, 24 May 2018 06:18:10 +0000
Message-ID: <DB6PR10MB1766FB99352EA99B31384A1CAC6A0@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM>
References: <SN1PR08MB1854395A2875541C4DC0673DDA6B0@SN1PR08MB1854.namprd08.prod.outlook.com>, <20180524044146.GA5215@1wt.eu>
In-Reply-To: <20180524044146.GA5215@1wt.eu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-Exchange-Organization-SCL: -1
X-MS-TNEF-Correlator: 
X-MS-Exchange-Organization-RecordReviewCfmType: 0
Content-Type: multipart/alternative; boundary="_000_DB6PR10MB1766FB99352EA99B31384A1CAC6A0DB6PR10MB1766EURP_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/tGNQPuMOX1Xfmpv8zA2S3TUBVUo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 06:18:18 -0000

--_000_DB6PR10MB1766FB99352EA99B31384A1CAC6A0DB6PR10MB1766EURP_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Mentioning CDN there are also the cross origin headers. Also needed for 1 p=
age apps secondary api calls. (No one seems to understand them but they are=
 there).

charset utf-8 is probably a very good idea to support.

________________________________
From: QUIC <quic-bounces@ietf.org> on behalf of Willy Tarreau <w@1wt.eu>
Sent: Thursday, May 24, 2018 6:41:46 AM
To: Mike Bishop
Cc: quic@ietf.org; HTTP Working Group
Subject: Re: QPACK and the Static Table

Hi Mike,

On Wed, May 23, 2018 at 11:16:18PM +0000, Mike Bishop wrote:
> Rather than indexing the tables together and having the static table at 1=
-61,
> QPACK uses a bit to indicate static vs. dynamic.  Since the field is seve=
n
> bits long, the performance is comparable for the dynamic table (you can
> access 63 entries in one byte, 190 in two), but you can increase the size=
 of
> the static table without hurting the dynamic table.

It will make the code look less "magic"!

> As a result, we're
> building a fresh static
> table<https://github.com/quicwg/base-drafts/pull/1355> based on queries
> against HTTPArchive data.
>
> The key question that has come up in a couple venues:  What real-world
> headers do we want to artificially remove from what the data shows, and w=
hat
> headers not seen by HTTP Archive do we want to force in anyway?

I agree with Mark that request really is what matters the most.

>   *   Reordered to put headers you're likely to name-reference at the fro=
nt,
>   especially if you're unlikely to add them to the dynamic table

Well, some of us have been really bothered by the lack of ordering
in the HPACK headers table, making it painful to perform efficient
lookups. I'd suggest that they are sorted by (name,value) to make
it possible to perform efficient dichotomic lookups.

> The question is whether we should also backfill headers which HTTP Archiv=
e
> wouldn't see, delete headers we wish people wouldn't use, and/or insert t=
he
> ones we hope they eventually will.  Some candidates:

That's indeed a good point.

>   *   Add Alt-Svc entry for HTTP/QUIC with QUIC v1
>   *   Add X-Forwarded-For
>   *   Don't add X-Forwarded-For, but do add Forwarded

In practice, we can take both or none. After all, most QUIC requests going
through proxies will be encrypted already thus the proxy will not be able
to add these fields. For clear-text requests, the header field name is
roughly as long as the value, so there's not *that* much to save by encodin=
g
them. And it will not change in most consecutive requests, so the dynamic
compression will be more efficient than the static one. Thus I suggest that
we only add them *if* we have enough unused slots at the end that we care
to cover a very broad set.

>   *   Remove Expires to incent the use of Cache-Control

Expires is for responses only anyway, thus it matters much less. Cache-cont=
rol
can be used in both directions. I think that the technical focus on request
may make Expires disappear from the table ;-)

>   *   Collapse the "Content-Type: <thingey>" and "Content-Type: <thingey>=
; charset=3Dutf-8" entries together
>      *   ...but which one to keep?

Probably just focus on the most reported ones and not try to collapse. I
suspect that we see a lot of en-us alone, and utf-8 added to some other
languages, but I could be wrong.

>   *   Add Content-Encoding and/or Accept-Encoding entries for zstd

Probably too early yet, and will not make a big difference overall (almost
only response, 4 characters value).

> There's an endless parade of bikesheds here.  As Martin has pointed out, =
this
> will never be perfect, so the goal is "good enough and keep going."  Any
> strong feelings about any of these before we merge it?

No real strong feeling here except about the ability to perform fast lookup=
s.

> Also, there's been some discussion of a mechanism for selecting one of
> several static tables at the start of a connection.  In that case, the sp=
ec
> would probably define three tables (client headers, server headers [for
> servers that don't push], combined [for servers that push]) and enable fu=
ture
> RFCs to define others for targeted scenarios (proxies, video playback, Io=
T,
> etc.).  How much does that interest folks?

I think it could be a good solution. We could also think about APIs and
various datacenter-oriented use cases (eg: webservice etc) where very fast
response and network efficiency matters. It could be a way to encourage
QUIC adoption inside the DC. The risk however is that tables defined too
late are never deployed due to interoperability concerns (unless there's
a way to know that it will be supported before encoding). Thus if some
participants are interested in optimizing for certain use cases, they shoul=
d
probably provide their own tables to be merged into the standard from day 1=
.

Cheers,
Willy


--_000_DB6PR10MB1766FB99352EA99B31384A1CAC6A0DB6PR10MB1766EURP_
Content-Type: text/html; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Diso-8859-=
1">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div id=3D"x_compose-container" itemscope=3D"" itemtype=3D"https://schema.o=
rg/EmailMessage" style=3D"direction:ltr">
<span itemprop=3D"creator" itemscope=3D"" itemtype=3D"https://schema.org/Or=
ganization"><span itemprop=3D"name"></span></span>
<div>
<div>
<div style=3D"direction:ltr">Mentioning CDN there are also the cross origin=
 headers. Also needed for 1 page apps secondary api calls. (No one seems to=
 understand them but they are there).</div>
<div><br>
</div>
<div style=3D"direction:ltr">charset utf-8 is probably a very good idea to =
support.</div>
</div>
<div><br>
</div>
<div class=3D"x_acompli_signature"></div>
</div>
</div>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"x_divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" =
color=3D"#000000" style=3D"font-size:11pt"><b>From:</b> QUIC &lt;quic-bounc=
es@ietf.org&gt; on behalf of Willy Tarreau &lt;w@1wt.eu&gt;<br>
<b>Sent:</b> Thursday, May 24, 2018 6:41:46 AM<br>
<b>To:</b> Mike Bishop<br>
<b>Cc:</b> quic@ietf.org; HTTP Working Group<br>
<b>Subject:</b> Re: QPACK and the Static Table</font>
<div>&nbsp;</div>
</div>
</div>
<font size=3D"2"><span style=3D"font-size:11pt;">
<div class=3D"PlainText">Hi Mike,<br>
<br>
On Wed, May 23, 2018 at 11:16:18PM &#43;0000, Mike Bishop wrote:<br>
&gt; Rather than indexing the tables together and having the static table a=
t 1-61,<br>
&gt; QPACK uses a bit to indicate static vs. dynamic.&nbsp; Since the field=
 is seven<br>
&gt; bits long, the performance is comparable for the dynamic table (you ca=
n<br>
&gt; access 63 entries in one byte, 190 in two), but you can increase the s=
ize of<br>
&gt; the static table without hurting the dynamic table.<br>
<br>
It will make the code look less &quot;magic&quot;!<br>
<br>
&gt; As a result, we're<br>
&gt; building a fresh static<br>
&gt; table&lt;<a href=3D"https://github.com/quicwg/base-drafts/pull/1355">h=
ttps://github.com/quicwg/base-drafts/pull/1355</a>&gt; based on queries<br>
&gt; against HTTPArchive data.<br>
&gt; <br>
&gt; The key question that has come up in a couple venues:&nbsp; What real-=
world<br>
&gt; headers do we want to artificially remove from what the data shows, an=
d what<br>
&gt; headers not seen by HTTP Archive do we want to force in anyway?<br>
<br>
I agree with Mark that request really is what matters the most.<br>
<br>
&gt;&nbsp;&nbsp; *&nbsp;&nbsp; Reordered to put headers you're likely to na=
me-reference at the front,<br>
&gt;&nbsp;&nbsp; especially if you're unlikely to add them to the dynamic t=
able<br>
<br>
Well, some of us have been really bothered by the lack of ordering<br>
in the HPACK headers table, making it painful to perform efficient<br>
lookups. I'd suggest that they are sorted by (name,value) to make<br>
it possible to perform efficient dichotomic lookups.<br>
<br>
&gt; The question is whether we should also backfill headers which HTTP Arc=
hive<br>
&gt; wouldn't see, delete headers we wish people wouldn't use, and/or inser=
t the<br>
&gt; ones we hope they eventually will.&nbsp; Some candidates:<br>
<br>
That's indeed a good point.<br>
<br>
&gt;&nbsp;&nbsp; *&nbsp;&nbsp; Add Alt-Svc entry for HTTP/QUIC with QUIC v1=
<br>
&gt;&nbsp;&nbsp; *&nbsp;&nbsp; Add X-Forwarded-For<br>
&gt;&nbsp;&nbsp; *&nbsp;&nbsp; Don't add X-Forwarded-For, but do add Forwar=
ded<br>
<br>
In practice, we can take both or none. After all, most QUIC requests going<=
br>
through proxies will be encrypted already thus the proxy will not be able<b=
r>
to add these fields. For clear-text requests, the header field name is<br>
roughly as long as the value, so there's not *that* much to save by encodin=
g<br>
them. And it will not change in most consecutive requests, so the dynamic<b=
r>
compression will be more efficient than the static one. Thus I suggest that=
<br>
we only add them *if* we have enough unused slots at the end that we care<b=
r>
to cover a very broad set.<br>
<br>
&gt;&nbsp;&nbsp; *&nbsp;&nbsp; Remove Expires to incent the use of Cache-Co=
ntrol<br>
<br>
Expires is for responses only anyway, thus it matters much less. Cache-cont=
rol<br>
can be used in both directions. I think that the technical focus on request=
<br>
may make Expires disappear from the table ;-)<br>
<br>
&gt;&nbsp;&nbsp; *&nbsp;&nbsp; Collapse the &quot;Content-Type: &lt;thingey=
&gt;&quot; and &quot;Content-Type: &lt;thingey&gt;; charset=3Dutf-8&quot; e=
ntries together<br>
&gt;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; *&nbsp;&nbsp; ...but which one to keep?<=
br>
<br>
Probably just focus on the most reported ones and not try to collapse. I<br=
>
suspect that we see a lot of en-us alone, and utf-8 added to some other<br>
languages, but I could be wrong.<br>
<br>
&gt;&nbsp;&nbsp; *&nbsp;&nbsp; Add Content-Encoding and/or Accept-Encoding =
entries for zstd<br>
<br>
Probably too early yet, and will not make a big difference overall (almost<=
br>
only response, 4 characters value).<br>
<br>
&gt; There's an endless parade of bikesheds here.&nbsp; As Martin has point=
ed out, this<br>
&gt; will never be perfect, so the goal is &quot;good enough and keep going=
.&quot;&nbsp; Any<br>
&gt; strong feelings about any of these before we merge it?<br>
<br>
No real strong feeling here except about the ability to perform fast lookup=
s.<br>
<br>
&gt; Also, there's been some discussion of a mechanism for selecting one of=
<br>
&gt; several static tables at the start of a connection.&nbsp; In that case=
, the spec<br>
&gt; would probably define three tables (client headers, server headers [fo=
r<br>
&gt; servers that don't push], combined [for servers that push]) and enable=
 future<br>
&gt; RFCs to define others for targeted scenarios (proxies, video playback,=
 IoT,<br>
&gt; etc.).&nbsp; How much does that interest folks?<br>
<br>
I think it could be a good solution. We could also think about APIs and<br>
various datacenter-oriented use cases (eg: webservice etc) where very fast<=
br>
response and network efficiency matters. It could be a way to encourage<br>
QUIC adoption inside the DC. The risk however is that tables defined too<br=
>
late are never deployed due to interoperability concerns (unless there's<br=
>
a way to know that it will be supported before encoding). Thus if some<br>
participants are interested in optimizing for certain use cases, they shoul=
d<br>
probably provide their own tables to be merged into the standard from day 1=
.<br>
<br>
Cheers,<br>
Willy<br>
<br>
</div>
</span></font>
</body>
</html>

--_000_DB6PR10MB1766FB99352EA99B31384A1CAC6A0DB6PR10MB1766EURP_--


From nobody Thu May 24 06:34:20 2018
Return-Path: <ietf-secretariat-reply@ietf.org>
X-Original-To: quic@ietf.org
Delivered-To: quic@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 0119212E8D0 for <quic@ietf.org>; Thu, 24 May 2018 06:34:19 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
To: <quic@ietf.org>
Subject: Milestones changed for quic WG
X-Test-IDTracker: no
X-IETF-IDTracker: 6.80.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <152716885899.29859.17833962780265294843.idtracker@ietfa.amsl.com>
Date: Thu, 24 May 2018 06:34:18 -0700
From: IETF Secretariat <ietf-secretariat-reply@ietf.org>
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/6W_AvFY_zqa5v7-siXMof3d30o8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 13:34:19 -0000

Changed milestone "QPACK: Header Compression for HTTP over QUIC to IESG", set
state to active from review, accepting new milestone.

URL: https://datatracker.ietf.org/wg/quic/about/


From nobody Thu May 24 10:53:48 2018
Return-Path: <prvs=868201a72d=fenix@fb.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 81C8B12EAD0 for <quic@ietfa.amsl.com>; Thu, 24 May 2018 10:53:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.72
X-Spam-Level: 
X-Spam-Status: No, score=-2.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=aYyyk9vc; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=dH0mNDal
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 LQPGy6E3LiLx for <quic@ietfa.amsl.com>; Thu, 24 May 2018 10:53:44 -0700 (PDT)
Received: from mx0a-00082601.pphosted.com (mx0b-00082601.pphosted.com [67.231.153.30]) (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 142CA1274D2 for <quic@ietf.org>; Thu, 24 May 2018 10:53:44 -0700 (PDT)
Received: from pps.filterd (m0089730.ppops.net [127.0.0.1]) by m0089730.ppops.net (8.16.0.22/8.16.0.22) with SMTP id w4OHmiTH022697; Thu, 24 May 2018 10:53:18 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : content-id : content-transfer-encoding : mime-version; s=facebook; bh=bs5o6Veyvt5TVf0JkiLjr4foezg8WLywJfSW0vQsmCI=; b=aYyyk9vcf/nnjRuW/0JbJZunwsExiE/kSHEucVGpgiLcx8rzzaPWlGOzYmqlrTxMMuAw 9pn3GeRA9f8tXpReLndLl7a+eSxC4pqTqAVBjIEQfbi9i4qjBtSKEoDfJpN4QaPVsHL7 qVIjbfRGla/YWCPnQbV7Ch+k4DxG1QhyKug= 
Received: from maileast.thefacebook.com ([199.201.65.23]) by m0089730.ppops.net with ESMTP id 2j61tcr2n3-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 24 May 2018 10:53:17 -0700
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (192.168.183.28) by o365-in.thefacebook.com (192.168.177.26) with Microsoft SMTP Server (TLS) id 14.3.361.1; Thu, 24 May 2018 13:53:16 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bs5o6Veyvt5TVf0JkiLjr4foezg8WLywJfSW0vQsmCI=; b=dH0mNDal2RZ3U+uP7Lu+qp+Cxzs2Q32mR2AZ9BSfzmmxAb7SEVh9DWMYvGEOHeJ8X0nK8E+JDufwaxlwtmI5JkyAfEkQfcRUZZAj/2jL6oRyqLw9OLyEST5kpnuk5Lf9TpXZ3J+/zMd0Ghk4nEVX7B3BgqPDt8Q7qDvRqahxs6E=
Received: from BYAPR15MB2312.namprd15.prod.outlook.com (52.135.197.146) by BYAPR15MB2486.namprd15.prod.outlook.com (52.135.198.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.797.11; Thu, 24 May 2018 17:53:14 +0000
Received: from BYAPR15MB2312.namprd15.prod.outlook.com ([fe80::b434:da9b:6102:49eb]) by BYAPR15MB2312.namprd15.prod.outlook.com ([fe80::b434:da9b:6102:49eb%13]) with mapi id 15.20.0776.019; Thu, 24 May 2018 17:53:14 +0000
From: Roberto Peon <fenix@fb.com>
To: Willy Tarreau <w@1wt.eu>, Mike Bishop <mbishop@evequefou.be>
CC: "quic@ietf.org" <quic@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Subject: Re: QPACK and the Static Table
Thread-Topic: QPACK and the Static Table
Thread-Index: AdPy6/ObcVQE/1QBQB2X+UF0YtinwQALZGwAAAz5BYA=
Date: Thu, 24 May 2018 17:53:14 +0000
Message-ID: <993659D9-8A3B-4375-AEC6-0B7706F96B42@fb.com>
References: <SN1PR08MB1854395A2875541C4DC0673DDA6B0@SN1PR08MB1854.namprd08.prod.outlook.com> <20180524044146.GA5215@1wt.eu>
In-Reply-To: <20180524044146.GA5215@1wt.eu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.d.0.180513
x-originating-ip: [2620:10d:c090:200::7:88c]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR15MB2486; 7:artymMB+4cNpX0hKOaCAE0C2rPQfojUp2E3q9NklG73q31UJ7CrJRh+IM+5EF/sgxi5md+QPU0klvqXEo3nP2LSLm15tAnjzqZbEd9ACu/No1DHgpgEVKRQ3aROUOfp0/f8D+alx78PKlkQuC1x9TDjn2eIEiWraqutN/GZryrvYQ0gmYimK+ywcihZwrZK1jmXb4/UXF6qHtpovIiGDJOK/I31Q0pLYKewT6im/TNAMrGdME4/hBSszOGBN7jH/; 20:oqzDwEh3h79HPziOPMwAQ9ias3n6CWQmgufaw5dK1nfRKQIl43EBNsyWZqh6ZNLDz128gdj/XEIcgugEOL6g7Kzwxw7jSdaEoymggCJB7XdBPytHS5ZNSxQtLzNGvnZ3w96a12R64HGsxS0lHKgan22zxN4L0biKul79JIRBicw=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BYAPR15MB2486; 
x-ms-traffictypediagnostic: BYAPR15MB2486:
x-microsoft-antispam-prvs: <BYAPR15MB2486A5BEA843386F9FE7ACFDCD6A0@BYAPR15MB2486.namprd15.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(166708455590820)(17755550239193); 
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(3231254)(11241501184)(944501410)(52105095)(10201501046)(3002001)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123558120)(20161123562045)(20161123560045)(6072148)(201708071742011)(7699016); SRVR:BYAPR15MB2486; BCL:0; PCL:0; RULEID:; SRVR:BYAPR15MB2486; 
x-forefront-prvs: 0682FC00E8
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(366004)(346002)(39380400002)(376002)(396003)(52314003)(189003)(199004)(51444003)(6436002)(2906002)(97736004)(106356001)(4326008)(486006)(99286004)(68736007)(305945005)(14454004)(186003)(86362001)(6116002)(229853002)(76176011)(2900100001)(102836004)(82746002)(3280700002)(25786009)(81156014)(8936002)(53936002)(8676002)(36756003)(105586002)(46003)(83716003)(59450400001)(5250100002)(81166006)(6506007)(6512007)(3660700001)(5660300001)(446003)(6306002)(2616005)(58126008)(476003)(6486002)(33656002)(6246003)(316002)(110136005)(54906003)(7736002)(478600001)(11346002)(781001)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR15MB2486; H:BYAPR15MB2312.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: fb.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: V6Ib91KhQWTlX72QtRJm1fEyA2NpbtRzw72lZTZEMs3lDQK7g5BOksjcQ/BhQhIjfK3gpKiQBw6vdurXq9KEF9RFK3pfVr6fBNYCQqTf/HnFDtLMzLWK6V1jIv7xCUBukBVGTW6PD7Coqc66NchNgQm6F6d/ojjik+42uZ8iKEN/7/fezADABm9jkQZD6jpS
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <EED2E1014C84204A93FD79D9B29A1E4F@namprd15.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 27900cdf-653d-4a29-9a3e-08d5c19f3946
X-MS-Exchange-CrossTenant-Network-Message-Id: 27900cdf-653d-4a29-9a3e-08d5c19f3946
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 May 2018 17:53:14.5807 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR15MB2486
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-24_06:, , signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/gje6Gm5wW4uxesuIoT0Uo30Rzrc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 17:53:47 -0000

T25lIGNvdWxkIG1ha2UgdGhlIGxvb2t1cCAobW9yZSkgZWZmaWNpZW50IGJ5IHN0b3JpbmcgdGhl
IGluZGV4IChhIGJ5dGUgYXQgbW9zdCkgd2l0aCB0aGUga2V5LXZhbHVlIHBhaXIsIHdoZXJlIHRo
ZSBrZXktdmFsdWUgcGFpciB3ZXJlIHNvcnRlZCB2aWEgd2hhdGV2ZXIgc29ydGluZyB5b3UnZCBm
aW5kIG1vc3QgZWZmaWNpZW50Lg0KSWYgcmVvcmRlcmluZyBhbGxvd3MgZm9yIHNvbWUgaW5jcmVh
c2VkIGVmZmljaWVuY3kgd2l0aG91dCBpbmNyZWFzaW5nIGJpdHMtb24td2lyZSwgSSdkIHRoaW5r
IGl0IHNlZW1zIHJlYXNvbmFibGUgdG8gY2hhbmdlLg0KDQpJIHdvdWxkIG5vdCB0cnVzdCB0aGUg
SFRUUCBBcmNoaXZlIHRvIGdpdmUgYSBmcmVxdWVuY3kgYW5hbHlzaXMgZm9yIHJlYWwtd29ybGQg
dXNlLiBSZW1lbWJlciB0aGF0IHdlIGdhdGhlcmVkIHRoZSBmcmVxIGRhdGEgZm9yIEhQQUNLIGZy
b20gcmVhbC13b3JsZCB1c2UgYWNyb3NzIGEgaG9wZWZ1bGx5IG5vdC1zby1iaWFzZWQgc2FtcGxl
IHZpYSBicm93c2VycyBkaXJlY3RseS4gSWYgdGhlIHdvcmxkIGhhcyBjaGFuZ2VkIHNpbmNlIEhQ
QUNLIGNhbWUgb3V0IGluIHRlcm1zIG9mIGhlYWRlciBmcmVxIChzZWVtcyBwb3NzaWJsZSBpZiBu
b3QgcHJvYmFibGUpLCB0aGVuIHBlcmhhcHMgd2Ugc2hvdWxkIGNvbnNpZGVyIGFuIHVwZGF0ZSB0
byBIVFRQMi9IUEFDSyBhcyB3ZWxsPw0KDQpJIGFncmVlIHRoYXQgcGVyZmVjdGlvbiBoZXJlIGlz
bid0IHJlYWxseSBuZWVkZWQsIGJ1dCBJJ20gbm90IHN1cmUgYWRkaW5nIGl0ZW1zIHRvIHRoZSB0
YWJsZSBhcmJpdHJhcmlseSBtYWtlcyBzZW5zZSBlaXRoZXIuDQoNCi09Ug0KDQrvu79PbiA1LzIz
LzE4LCA5OjQyIFBNLCAiUVVJQyBvbiBiZWhhbGYgb2YgV2lsbHkgVGFycmVhdSIgPHF1aWMtYm91
bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2Ygd0Axd3QuZXU+IHdyb3RlOg0KDQogICAgSGkgTWlr
ZSwNCiAgICANCiAgICBPbiBXZWQsIE1heSAyMywgMjAxOCBhdCAxMToxNjoxOFBNICswMDAwLCBN
aWtlIEJpc2hvcCB3cm90ZToNCiAgICA+IFJhdGhlciB0aGFuIGluZGV4aW5nIHRoZSB0YWJsZXMg
dG9nZXRoZXIgYW5kIGhhdmluZyB0aGUgc3RhdGljIHRhYmxlIGF0IDEtNjEsDQogICAgPiBRUEFD
SyB1c2VzIGEgYml0IHRvIGluZGljYXRlIHN0YXRpYyB2cy4gZHluYW1pYy4gIFNpbmNlIHRoZSBm
aWVsZCBpcyBzZXZlbg0KICAgID4gYml0cyBsb25nLCB0aGUgcGVyZm9ybWFuY2UgaXMgY29tcGFy
YWJsZSBmb3IgdGhlIGR5bmFtaWMgdGFibGUgKHlvdSBjYW4NCiAgICA+IGFjY2VzcyA2MyBlbnRy
aWVzIGluIG9uZSBieXRlLCAxOTAgaW4gdHdvKSwgYnV0IHlvdSBjYW4gaW5jcmVhc2UgdGhlIHNp
emUgb2YNCiAgICA+IHRoZSBzdGF0aWMgdGFibGUgd2l0aG91dCBodXJ0aW5nIHRoZSBkeW5hbWlj
IHRhYmxlLg0KICAgIA0KICAgIEl0IHdpbGwgbWFrZSB0aGUgY29kZSBsb29rIGxlc3MgIm1hZ2lj
IiENCiAgICANCiAgICA+IEFzIGEgcmVzdWx0LCB3ZSdyZQ0KICAgID4gYnVpbGRpbmcgYSBmcmVz
aCBzdGF0aWMNCiAgICA+IHRhYmxlPGh0dHBzOi8vZ2l0aHViLmNvbS9xdWljd2cvYmFzZS1kcmFm
dHMvcHVsbC8xMzU1PiBiYXNlZCBvbiBxdWVyaWVzDQogICAgPiBhZ2FpbnN0IEhUVFBBcmNoaXZl
IGRhdGEuDQogICAgPiANCiAgICA+IFRoZSBrZXkgcXVlc3Rpb24gdGhhdCBoYXMgY29tZSB1cCBp
biBhIGNvdXBsZSB2ZW51ZXM6ICBXaGF0IHJlYWwtd29ybGQNCiAgICA+IGhlYWRlcnMgZG8gd2Ug
d2FudCB0byBhcnRpZmljaWFsbHkgcmVtb3ZlIGZyb20gd2hhdCB0aGUgZGF0YSBzaG93cywgYW5k
IHdoYXQNCiAgICA+IGhlYWRlcnMgbm90IHNlZW4gYnkgSFRUUCBBcmNoaXZlIGRvIHdlIHdhbnQg
dG8gZm9yY2UgaW4gYW55d2F5Pw0KICAgIA0KICAgIEkgYWdyZWUgd2l0aCBNYXJrIHRoYXQgcmVx
dWVzdCByZWFsbHkgaXMgd2hhdCBtYXR0ZXJzIHRoZSBtb3N0Lg0KICAgIA0KICAgID4gICAqICAg
UmVvcmRlcmVkIHRvIHB1dCBoZWFkZXJzIHlvdSdyZSBsaWtlbHkgdG8gbmFtZS1yZWZlcmVuY2Ug
YXQgdGhlIGZyb250LA0KICAgID4gICBlc3BlY2lhbGx5IGlmIHlvdSdyZSB1bmxpa2VseSB0byBh
ZGQgdGhlbSB0byB0aGUgZHluYW1pYyB0YWJsZQ0KICAgIA0KICAgIFdlbGwsIHNvbWUgb2YgdXMg
aGF2ZSBiZWVuIHJlYWxseSBib3RoZXJlZCBieSB0aGUgbGFjayBvZiBvcmRlcmluZw0KICAgIGlu
IHRoZSBIUEFDSyBoZWFkZXJzIHRhYmxlLCBtYWtpbmcgaXQgcGFpbmZ1bCB0byBwZXJmb3JtIGVm
ZmljaWVudA0KICAgIGxvb2t1cHMuIEknZCBzdWdnZXN0IHRoYXQgdGhleSBhcmUgc29ydGVkIGJ5
IChuYW1lLHZhbHVlKSB0byBtYWtlDQogICAgaXQgcG9zc2libGUgdG8gcGVyZm9ybSBlZmZpY2ll
bnQgZGljaG90b21pYyBsb29rdXBzLg0KICAgIA0KICAgID4gVGhlIHF1ZXN0aW9uIGlzIHdoZXRo
ZXIgd2Ugc2hvdWxkIGFsc28gYmFja2ZpbGwgaGVhZGVycyB3aGljaCBIVFRQIEFyY2hpdmUNCiAg
ICA+IHdvdWxkbid0IHNlZSwgZGVsZXRlIGhlYWRlcnMgd2Ugd2lzaCBwZW9wbGUgd291bGRuJ3Qg
dXNlLCBhbmQvb3IgaW5zZXJ0IHRoZQ0KICAgID4gb25lcyB3ZSBob3BlIHRoZXkgZXZlbnR1YWxs
eSB3aWxsLiAgU29tZSBjYW5kaWRhdGVzOg0KICAgIA0KICAgIFRoYXQncyBpbmRlZWQgYSBnb29k
IHBvaW50Lg0KICAgIA0KICAgID4gICAqICAgQWRkIEFsdC1TdmMgZW50cnkgZm9yIEhUVFAvUVVJ
QyB3aXRoIFFVSUMgdjENCiAgICA+ICAgKiAgIEFkZCBYLUZvcndhcmRlZC1Gb3INCiAgICA+ICAg
KiAgIERvbid0IGFkZCBYLUZvcndhcmRlZC1Gb3IsIGJ1dCBkbyBhZGQgRm9yd2FyZGVkDQogICAg
DQogICAgSW4gcHJhY3RpY2UsIHdlIGNhbiB0YWtlIGJvdGggb3Igbm9uZS4gQWZ0ZXIgYWxsLCBt
b3N0IFFVSUMgcmVxdWVzdHMgZ29pbmcNCiAgICB0aHJvdWdoIHByb3hpZXMgd2lsbCBiZSBlbmNy
eXB0ZWQgYWxyZWFkeSB0aHVzIHRoZSBwcm94eSB3aWxsIG5vdCBiZSBhYmxlDQogICAgdG8gYWRk
IHRoZXNlIGZpZWxkcy4gRm9yIGNsZWFyLXRleHQgcmVxdWVzdHMsIHRoZSBoZWFkZXIgZmllbGQg
bmFtZSBpcw0KICAgIHJvdWdobHkgYXMgbG9uZyBhcyB0aGUgdmFsdWUsIHNvIHRoZXJlJ3Mgbm90
ICp0aGF0KiBtdWNoIHRvIHNhdmUgYnkgZW5jb2RpbmcNCiAgICB0aGVtLiBBbmQgaXQgd2lsbCBu
b3QgY2hhbmdlIGluIG1vc3QgY29uc2VjdXRpdmUgcmVxdWVzdHMsIHNvIHRoZSBkeW5hbWljDQog
ICAgY29tcHJlc3Npb24gd2lsbCBiZSBtb3JlIGVmZmljaWVudCB0aGFuIHRoZSBzdGF0aWMgb25l
LiBUaHVzIEkgc3VnZ2VzdCB0aGF0DQogICAgd2Ugb25seSBhZGQgdGhlbSAqaWYqIHdlIGhhdmUg
ZW5vdWdoIHVudXNlZCBzbG90cyBhdCB0aGUgZW5kIHRoYXQgd2UgY2FyZQ0KICAgIHRvIGNvdmVy
IGEgdmVyeSBicm9hZCBzZXQuDQogICAgDQogICAgPiAgICogICBSZW1vdmUgRXhwaXJlcyB0byBp
bmNlbnQgdGhlIHVzZSBvZiBDYWNoZS1Db250cm9sDQogICAgDQogICAgRXhwaXJlcyBpcyBmb3Ig
cmVzcG9uc2VzIG9ubHkgYW55d2F5LCB0aHVzIGl0IG1hdHRlcnMgbXVjaCBsZXNzLiBDYWNoZS1j
b250cm9sDQogICAgY2FuIGJlIHVzZWQgaW4gYm90aCBkaXJlY3Rpb25zLiBJIHRoaW5rIHRoYXQg
dGhlIHRlY2huaWNhbCBmb2N1cyBvbiByZXF1ZXN0DQogICAgbWF5IG1ha2UgRXhwaXJlcyBkaXNh
cHBlYXIgZnJvbSB0aGUgdGFibGUgOy0pDQogICAgDQogICAgPiAgICogICBDb2xsYXBzZSB0aGUg
IkNvbnRlbnQtVHlwZTogPHRoaW5nZXk+IiBhbmQgIkNvbnRlbnQtVHlwZTogPHRoaW5nZXk+OyBj
aGFyc2V0PXV0Zi04IiBlbnRyaWVzIHRvZ2V0aGVyDQogICAgPiAgICAgICogICAuLi5idXQgd2hp
Y2ggb25lIHRvIGtlZXA/DQogICAgDQogICAgUHJvYmFibHkganVzdCBmb2N1cyBvbiB0aGUgbW9z
dCByZXBvcnRlZCBvbmVzIGFuZCBub3QgdHJ5IHRvIGNvbGxhcHNlLiBJDQogICAgc3VzcGVjdCB0
aGF0IHdlIHNlZSBhIGxvdCBvZiBlbi11cyBhbG9uZSwgYW5kIHV0Zi04IGFkZGVkIHRvIHNvbWUg
b3RoZXINCiAgICBsYW5ndWFnZXMsIGJ1dCBJIGNvdWxkIGJlIHdyb25nLg0KICAgIA0KICAgID4g
ICAqICAgQWRkIENvbnRlbnQtRW5jb2RpbmcgYW5kL29yIEFjY2VwdC1FbmNvZGluZyBlbnRyaWVz
IGZvciB6c3RkDQogICAgDQogICAgUHJvYmFibHkgdG9vIGVhcmx5IHlldCwgYW5kIHdpbGwgbm90
IG1ha2UgYSBiaWcgZGlmZmVyZW5jZSBvdmVyYWxsIChhbG1vc3QNCiAgICBvbmx5IHJlc3BvbnNl
LCA0IGNoYXJhY3RlcnMgdmFsdWUpLg0KICAgIA0KICAgID4gVGhlcmUncyBhbiBlbmRsZXNzIHBh
cmFkZSBvZiBiaWtlc2hlZHMgaGVyZS4gIEFzIE1hcnRpbiBoYXMgcG9pbnRlZCBvdXQsIHRoaXMN
CiAgICA+IHdpbGwgbmV2ZXIgYmUgcGVyZmVjdCwgc28gdGhlIGdvYWwgaXMgImdvb2QgZW5vdWdo
IGFuZCBrZWVwIGdvaW5nLiIgIEFueQ0KICAgID4gc3Ryb25nIGZlZWxpbmdzIGFib3V0IGFueSBv
ZiB0aGVzZSBiZWZvcmUgd2UgbWVyZ2UgaXQ/DQogICAgDQogICAgTm8gcmVhbCBzdHJvbmcgZmVl
bGluZyBoZXJlIGV4Y2VwdCBhYm91dCB0aGUgYWJpbGl0eSB0byBwZXJmb3JtIGZhc3QgbG9va3Vw
cy4NCiAgICANCiAgICA+IEFsc28sIHRoZXJlJ3MgYmVlbiBzb21lIGRpc2N1c3Npb24gb2YgYSBt
ZWNoYW5pc20gZm9yIHNlbGVjdGluZyBvbmUgb2YNCiAgICA+IHNldmVyYWwgc3RhdGljIHRhYmxl
cyBhdCB0aGUgc3RhcnQgb2YgYSBjb25uZWN0aW9uLiAgSW4gdGhhdCBjYXNlLCB0aGUgc3BlYw0K
ICAgID4gd291bGQgcHJvYmFibHkgZGVmaW5lIHRocmVlIHRhYmxlcyAoY2xpZW50IGhlYWRlcnMs
IHNlcnZlciBoZWFkZXJzIFtmb3INCiAgICA+IHNlcnZlcnMgdGhhdCBkb24ndCBwdXNoXSwgY29t
YmluZWQgW2ZvciBzZXJ2ZXJzIHRoYXQgcHVzaF0pIGFuZCBlbmFibGUgZnV0dXJlDQogICAgPiBS
RkNzIHRvIGRlZmluZSBvdGhlcnMgZm9yIHRhcmdldGVkIHNjZW5hcmlvcyAocHJveGllcywgdmlk
ZW8gcGxheWJhY2ssIElvVCwNCiAgICA+IGV0Yy4pLiAgSG93IG11Y2ggZG9lcyB0aGF0IGludGVy
ZXN0IGZvbGtzPw0KICAgIA0KICAgIEkgdGhpbmsgaXQgY291bGQgYmUgYSBnb29kIHNvbHV0aW9u
LiBXZSBjb3VsZCBhbHNvIHRoaW5rIGFib3V0IEFQSXMgYW5kDQogICAgdmFyaW91cyBkYXRhY2Vu
dGVyLW9yaWVudGVkIHVzZSBjYXNlcyAoZWc6IHdlYnNlcnZpY2UgZXRjKSB3aGVyZSB2ZXJ5IGZh
c3QNCiAgICByZXNwb25zZSBhbmQgbmV0d29yayBlZmZpY2llbmN5IG1hdHRlcnMuIEl0IGNvdWxk
IGJlIGEgd2F5IHRvIGVuY291cmFnZQ0KICAgIFFVSUMgYWRvcHRpb24gaW5zaWRlIHRoZSBEQy4g
VGhlIHJpc2sgaG93ZXZlciBpcyB0aGF0IHRhYmxlcyBkZWZpbmVkIHRvbw0KICAgIGxhdGUgYXJl
IG5ldmVyIGRlcGxveWVkIGR1ZSB0byBpbnRlcm9wZXJhYmlsaXR5IGNvbmNlcm5zICh1bmxlc3Mg
dGhlcmUncw0KICAgIGEgd2F5IHRvIGtub3cgdGhhdCBpdCB3aWxsIGJlIHN1cHBvcnRlZCBiZWZv
cmUgZW5jb2RpbmcpLiBUaHVzIGlmIHNvbWUNCiAgICBwYXJ0aWNpcGFudHMgYXJlIGludGVyZXN0
ZWQgaW4gb3B0aW1pemluZyBmb3IgY2VydGFpbiB1c2UgY2FzZXMsIHRoZXkgc2hvdWxkDQogICAg
cHJvYmFibHkgcHJvdmlkZSB0aGVpciBvd24gdGFibGVzIHRvIGJlIG1lcmdlZCBpbnRvIHRoZSBz
dGFuZGFyZCBmcm9tIGRheSAxLg0KICAgIA0KICAgIENoZWVycywNCiAgICBXaWxseQ0KICAgIA0K
ICAgIA0KDQo=


From nobody Thu May 24 11:21:08 2018
Return-Path: <dtikhonov@litespeedtech.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4775212E872 for <quic@ietfa.amsl.com>; Thu, 24 May 2018 11:21:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.611
X-Spam-Level: 
X-Spam-Status: No, score=-2.611 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 0qlEaUuE1xDS for <quic@ietfa.amsl.com>; Thu, 24 May 2018 11:21:05 -0700 (PDT)
Received: from mail-qk0-x22e.google.com (mail-qk0-x22e.google.com [IPv6:2607:f8b0:400d:c09::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 2834312E057 for <quic@ietf.org>; Thu, 24 May 2018 11:21:05 -0700 (PDT)
Received: by mail-qk0-x22e.google.com with SMTP id k86-v6so2047223qkh.13 for <quic@ietf.org>; Thu, 24 May 2018 11:21:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=+dEbjzytb1Xr0C/ON7gFYVyXFi9eIooVOENf7UHPrRI=; b=EnXG+x6BD7S03qr53RZmyPFWY2ElSVdUzsVr71FlAJbyJ9vVE4z/tpRJKaJVOcFi48 YLxFS2Gaf2PKoWivgXSpHK8sfCa9EJnN4wbfYiBAzac5pQ2EMd16x/qI7PHzKnz5vD2F oxQVifektdmPJ2+017nVjBXnYKzN4EB0gcq5opT58DyJwxHNfha1m9Br5RJSMRCpFLuo HB1l+gdwxZcG2FxJvBp8t1jcCRrVu0p/wQwttLyiYnla2014X9uS6RIFm0JnrjvhPm8q JKnau/RZ+G2ianntF2bMa1ngps3sDhxwFde7NfAgzSoQ+ySZv7fBozw6F1CKPb0AgNJM ORIA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :in-reply-to:user-agent; bh=+dEbjzytb1Xr0C/ON7gFYVyXFi9eIooVOENf7UHPrRI=; b=ZkG0hucdpeCF47pCnv1t/pvuZgJh99GR/CZDamU4FHfW0KXzVOIsi52Uy9l4YMOj45 Kh5xNcmdszACjX6UCaGdgUenKZTHFLN961pmBrs0kUbGMY6iZ59KmvLi5IJzMPTR1vyT zEy2DRQsSnrJ3gOEhwcJVrvm7yc5ml4hWiJt/62ftS4sIcEHw/V5K++hcjL90kRM4s/Z ZRLoK7jDlgVdYuZu1+5JKK/muVNAwoSm1ljKjvfqBsLhf3u2VxwpOdtVlsCzgYZEUpRT XcGM9p8qwqQ52NVfnyEsSOScnHGA54EvEjAbPy1AGirmUBRpsrrIgjV3bL3rChRuJ5Ou XIng==
X-Gm-Message-State: ALKqPwft4TYrK4hjDK8fPxwED+91302AIPxQLu8ARYQY7uFjyIHBFCYu ImYTnEOD0b8qD8MlOA/JouThmg==
X-Google-Smtp-Source: ADUXVKK4CO4Aa/jr/NIw0HdLpje1RYm0dadp8Nrch6jVn1XlBw7FGhfJx3UlgYZn1jkEF7/InOIF+w==
X-Received: by 2002:a37:c5cb:: with SMTP id k72-v6mr7562451qkl.316.1527186064296;  Thu, 24 May 2018 11:21:04 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id y41-v6sm17961763qty.84.2018.05.24.11.21.03 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 24 May 2018 11:21:03 -0700 (PDT)
Date: Thu, 24 May 2018 14:20:56 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Roberto Peon <fenix@fb.com>
Cc: Willy Tarreau <w@1wt.eu>, Mike Bishop <mbishop@evequefou.be>, "quic@ietf.org" <quic@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Subject: Re: QPACK and the Static Table
Message-ID: <20180524182055.GA16465@ubuntu-dmitri>
Mail-Followup-To: Roberto Peon <fenix@fb.com>, Willy Tarreau <w@1wt.eu>, Mike Bishop <mbishop@evequefou.be>, "quic@ietf.org" <quic@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
References: <SN1PR08MB1854395A2875541C4DC0673DDA6B0@SN1PR08MB1854.namprd08.prod.outlook.com> <20180524044146.GA5215@1wt.eu> <993659D9-8A3B-4375-AEC6-0B7706F96B42@fb.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <993659D9-8A3B-4375-AEC6-0B7706F96B42@fb.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/RiYKGMIW0mW4fhu-n21qHpoMw_Q>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 18:21:07 -0000

On Thu, May 24, 2018 at 05:53:14PM +0000, Roberto Peon wrote:
> One could make the lookup (more) efficient by storing the index (a
> byte at most) with the key-value pair, where the key-value pair were
> sorted via whatever sorting you'd find most efficient.  If reordering
> allows for some increased efficiency without increasing bits-on-wire,
> I'd think it seems reasonable to change.

Lookup efficiency should be a marginal consideration.  The table has
only a few dozen entries.  There are ways to compile the static table
to make lookups faster (for example, by using a perfect hash) if one
is bothered by doing a simple scan.

  - Dmitri.


From nobody Thu May 24 11:21:31 2018
Return-Path: <mbishop@evequefou.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1C15D12EB14 for <quic@ietfa.amsl.com>; Thu, 24 May 2018 11:21:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level: 
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 0bEWGclj8S8O for <quic@ietfa.amsl.com>; Thu, 24 May 2018 11:21:20 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0128.outbound.protection.outlook.com [104.47.38.128]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AAE0E12EAFE for <quic@ietf.org>; Thu, 24 May 2018 11:21:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=bcUDnE+BxHTuCdzOWqW2LGuh3rOF/YtDmpRwvgX+wMw=; b=eADzI8NW/UCIDzXKOTL9gBD8LTdNA5/10BKON9IO9SZQ7yWxtWD4PrRrSASS0/YUzosezCbPRR14n3H1K3rBalIfWX9nHI71aaExvbL6t5/iT9svL7UBETD+lRafC3Kp/E0lf1lf7izjuAfnzlrszBMFiREs/Y3G2Qp6e+1FrJI=
Received: from SN1PR08MB1854.namprd08.prod.outlook.com (10.169.39.8) by SN1PR08MB1680.namprd08.prod.outlook.com (10.162.133.142) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.776.11; Thu, 24 May 2018 18:21:16 +0000
Received: from SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d]) by SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::3c18:f60d:11c1:143d%13]) with mapi id 15.20.0776.015; Thu, 24 May 2018 18:21:16 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Roberto Peon <fenix@fb.com>, Willy Tarreau <w@1wt.eu>
CC: "quic@ietf.org" <quic@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Subject: RE: QPACK and the Static Table
Thread-Topic: QPACK and the Static Table
Thread-Index: AdPy6/ObcVQE/1QBQB2X+UF0YtinwQALZGwAAAz5BYAAD2QCcA==
Date: Thu, 24 May 2018 18:21:15 +0000
Message-ID: <SN1PR08MB185459B20E930B87BAE380EFDA6A0@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <SN1PR08MB1854395A2875541C4DC0673DDA6B0@SN1PR08MB1854.namprd08.prod.outlook.com> <20180524044146.GA5215@1wt.eu> <993659D9-8A3B-4375-AEC6-0B7706F96B42@fb.com>
In-Reply-To: <993659D9-8A3B-4375-AEC6-0B7706F96B42@fb.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [2601:600:8080:5a28:3dff:1440:9743:1059]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN1PR08MB1680; 7:a/K1TkvNfEUhU8og5+dTD9DD+GZqwDbmaVnsq2kGdb4z/BrlxrlTiBbthoPVxW1Nvz6xVojMRM3yppMEgx5yC2Sh381MrXEVPJeKZYf+qvf/yZRtzeEhMpVL9SzvdGc9IdwEzbWuXK96pC6fFOpeu13vx54awgZgV/luFQdMBCOSi9k1Qzp5qJuZfcJha1zhv2hW6jT0vdBFwvE8ppDd3YQpLur+08q/c1nNXrKYUHtXGCHe16Naf2zDNdDZ4oda
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(5600026)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(2017052603328)(7153060)(7193020); SRVR:SN1PR08MB1680; 
x-ms-traffictypediagnostic: SN1PR08MB1680:
x-microsoft-antispam-prvs: <SN1PR08MB1680008E946B4C429905F583DA6A0@SN1PR08MB1680.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(158342451672863)(166708455590820)(67672495146484)(21748063052155)(17755550239193);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(10201501046)(3231254)(944501410)(52105095)(149027)(150027)(6041310)(20161123564045)(20161123562045)(20161123560045)(20161123558120)(2016111802025)(6043046)(6072148)(201708071742011)(7699016); SRVR:SN1PR08MB1680; BCL:0; PCL:0; RULEID:; SRVR:SN1PR08MB1680; 
x-forefront-prvs: 0682FC00E8
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(39380400002)(376002)(39830400003)(346002)(366004)(51444003)(13464003)(189003)(199004)(52314003)(25786009)(486006)(54906003)(99286004)(3660700001)(316002)(2906002)(74482002)(97736004)(110136005)(3280700002)(14454004)(7696005)(68736007)(478600001)(5660300001)(86362001)(5250100002)(74316002)(8676002)(6436002)(81156014)(81166006)(46003)(6116002)(2900100001)(606006)(236005)(186003)(790700001)(446003)(6246003)(11346002)(105586002)(33656002)(102836004)(76176011)(53936002)(6506007)(8936002)(9686003)(6306002)(55016002)(53546011)(229853002)(106356001)(59450400001)(7736002)(54896002)(4326008)(476003)(781001); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR08MB1680; H:SN1PR08MB1854.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: Q0Y5NxUiS222NOQXCgQvqPSPugU0xJvscEvrT1P1eKb1FRz3sHC6z6vyeXOjJ2Ai6oyAiNA74pPE/Kdu9RIzXzAc/2FPsvknWpX2YL+gY5fxrfwA47xeWAyBrX8PBRRiQ3jWNkiij/4QF7IQq0JzPJzFNNPAxCpetSo0PyIFIQL0aRqksav3HHcurxaNFQ5+
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_SN1PR08MB185459B20E930B87BAE380EFDA6A0SN1PR08MB1854namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: a2216954-ffd5-424d-b46e-08d5c1a32385
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: a2216954-ffd5-424d-b46e-08d5c1a32385
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 May 2018 18:21:16.0176 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR08MB1680
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/amvZkRU-ivHGwRb9tmrfU_QPPzA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 18:21:29 -0000

--_000_SN1PR08MB185459B20E930B87BAE380EFDA6A0SN1PR08MB1854namp_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

WWVzLCBJIHRoaW5rIHlvdSBuZWVkIHRoZSBsb29rdXAgdGFibGUgZm9yIGluZGljZXMuICBBbHBo
YWJldGljYWwgZG9lc24ndCB3b3JrIGFzIHdlbGwsIGJlY2F1c2UgdGhlcmUgYXJlIHR3byBrZXkg
YmFycmllcnMgdG8gZGVhbCB3aXRoOg0KDQogICogICBPbmx5IHRoZSBmaXJzdCBzaXh0ZWVuIGVu
dHJpZXMgY2FuIGJlIG5hbWUtcmVmZXJlbmNlZCBpbiBhIHNpbmdsZSBieXRlLiAgV2UgZGVncmFk
ZWQgcGVyZm9ybWFuY2UgaW4gYSBwcmV2aW91cyBkcmFmdCBvZiB0aGlzIHRhYmxlIGJlY2F1c2Ug
OnBhdGggd2FzbuKAmXQgaW4gdGhlIGZpcnN0IHNpeHRlZW4gZW50cmllcywgYW5kIHRoZSBlbmNv
ZGVyIHRoYXQgdHJpZWQgdGhlIHVwZGF0ZWQgdGFibGUgdXNlZCB0d28tYnl0ZSBuYW1lIHJlZmVy
ZW5jZXMgZm9yIGV2ZXJ5IHJlcXVlc3QuDQogICogICBPbmx5IHRoZSBmaXJzdCBzaXh0eS1mb3Vy
IGVudHJpZXMgY2FuIGJlIGluZGV4LXJlZmVyZW5jZWQgaW4gYSBzaW5nbGUgYnl0ZS4NCg0KDQoN
ClRoaXMgaW1wbGllcyB0aGF0IHlvdSB3YW50IGFuIG9yZGVyaW5nIGJ5IGxpa2VsaWhvb2Qgb2Yg
dXNpbmcgdGhlIG5hbWUgYXQgYWxsLCBieSBsaWtlbGlob29kIG9mIG5vdCBpbmRleGluZyB0aGUg
dmFsdWUgZm9yIHJlcGVhdCB1c2UsIGFuZCBieSBsaWtlbGlob29kIG9mIHVzaW5nIHRoZSBuYW1l
K3ZhbHVlIHBhaXIgZGlyZWN0bHkuDQoNCg0KDQpXaGlsZSBhbiBhbHBoYWJldGljYWxseS1zb3J0
ZWQgbGlzdCBpc27igJl0IGltcG9zc2libGUgd2l0aGluIGVhY2ggdGllciwgaXQgc2VlbXMgZWFz
aWVyIHRvIG1haW50YWluIGEgc3RhdGljIG1hcCBvZiB0aGUgaW5kaWNlcyB0aGFuIHRvIGFscGhh
YmV0aWNhbGx5IGluZGV4IGludG8gZWFjaCB0aWVyIHRvIHNlZSBpZiB0aGUgaGVhZGVyIHlvdSB3
YW50IGlzIHByZXNlbnQuDQoNCg0KDQpJ4oCZZCBiZSBvcGVuIHRvIGFkZGl0aW9uYWwgc291cmNl
cyBvZiBkYXRhIHRvIHJ1biB0aGUgc2FtZSBxdWVyeSBhZ2FpbnN0LiAgQW55IGJyb3dzZXJzIHVw
IHRvIHJ1bm5pbmcgYW4gZXhwZXJpbWVudCBhbmQgc2hhcmluZyB0aGUgdGVsZW1ldHJ5Pw0KDQoN
Cg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IFJvYmVydG8gUGVvbiA8ZmVuaXhA
ZmIuY29tPg0KU2VudDogVGh1cnNkYXksIE1heSAyNCwgMjAxOCAxMDo1MyBBTQ0KVG86IFdpbGx5
IFRhcnJlYXUgPHdAMXd0LmV1PjsgTWlrZSBCaXNob3AgPG1iaXNob3BAZXZlcXVlZm91LmJlPg0K
Q2M6IHF1aWNAaWV0Zi5vcmc7IEhUVFAgV29ya2luZyBHcm91cCA8aWV0Zi1odHRwLXdnQHczLm9y
Zz4NClN1YmplY3Q6IFJlOiBRUEFDSyBhbmQgdGhlIFN0YXRpYyBUYWJsZQ0KDQoNCg0KT25lIGNv
dWxkIG1ha2UgdGhlIGxvb2t1cCAobW9yZSkgZWZmaWNpZW50IGJ5IHN0b3JpbmcgdGhlIGluZGV4
IChhIGJ5dGUgYXQgbW9zdCkgd2l0aCB0aGUga2V5LXZhbHVlIHBhaXIsIHdoZXJlIHRoZSBrZXkt
dmFsdWUgcGFpciB3ZXJlIHNvcnRlZCB2aWEgd2hhdGV2ZXIgc29ydGluZyB5b3UnZCBmaW5kIG1v
c3QgZWZmaWNpZW50Lg0KDQpJZiByZW9yZGVyaW5nIGFsbG93cyBmb3Igc29tZSBpbmNyZWFzZWQg
ZWZmaWNpZW5jeSB3aXRob3V0IGluY3JlYXNpbmcgYml0cy1vbi13aXJlLCBJJ2QgdGhpbmsgaXQg
c2VlbXMgcmVhc29uYWJsZSB0byBjaGFuZ2UuDQoNCg0KDQpJIHdvdWxkIG5vdCB0cnVzdCB0aGUg
SFRUUCBBcmNoaXZlIHRvIGdpdmUgYSBmcmVxdWVuY3kgYW5hbHlzaXMgZm9yIHJlYWwtd29ybGQg
dXNlLiBSZW1lbWJlciB0aGF0IHdlIGdhdGhlcmVkIHRoZSBmcmVxIGRhdGEgZm9yIEhQQUNLIGZy
b20gcmVhbC13b3JsZCB1c2UgYWNyb3NzIGEgaG9wZWZ1bGx5IG5vdC1zby1iaWFzZWQgc2FtcGxl
IHZpYSBicm93c2VycyBkaXJlY3RseS4gSWYgdGhlIHdvcmxkIGhhcyBjaGFuZ2VkIHNpbmNlIEhQ
QUNLIGNhbWUgb3V0IGluIHRlcm1zIG9mIGhlYWRlciBmcmVxIChzZWVtcyBwb3NzaWJsZSBpZiBu
b3QgcHJvYmFibGUpLCB0aGVuIHBlcmhhcHMgd2Ugc2hvdWxkIGNvbnNpZGVyIGFuIHVwZGF0ZSB0
byBIVFRQMi9IUEFDSyBhcyB3ZWxsPw0KDQoNCg0KSSBhZ3JlZSB0aGF0IHBlcmZlY3Rpb24gaGVy
ZSBpc24ndCByZWFsbHkgbmVlZGVkLCBidXQgSSdtIG5vdCBzdXJlIGFkZGluZyBpdGVtcyB0byB0
aGUgdGFibGUgYXJiaXRyYXJpbHkgbWFrZXMgc2Vuc2UgZWl0aGVyLg0KDQoNCg0KLT1SDQoNCg0K
DQrvu79PbiA1LzIzLzE4LCA5OjQyIFBNLCAiUVVJQyBvbiBiZWhhbGYgb2YgV2lsbHkgVGFycmVh
dSIgPHF1aWMtYm91bmNlc0BpZXRmLm9yZyBvbiBiZWhhbGYgb2Ygd0Axd3QuZXU8bWFpbHRvOnF1
aWMtYm91bmNlc0BpZXRmLm9yZyUyMG9uJTIwYmVoYWxmJTIwb2YlMjB3QDF3dC5ldT4+IHdyb3Rl
Og0KDQoNCg0KICAgIEhpIE1pa2UsDQoNCg0KDQogICAgT24gV2VkLCBNYXkgMjMsIDIwMTggYXQg
MTE6MTY6MThQTSArMDAwMCwgTWlrZSBCaXNob3Agd3JvdGU6DQoNCiAgICA+IFJhdGhlciB0aGFu
IGluZGV4aW5nIHRoZSB0YWJsZXMgdG9nZXRoZXIgYW5kIGhhdmluZyB0aGUgc3RhdGljIHRhYmxl
IGF0IDEtNjEsDQoNCiAgICA+IFFQQUNLIHVzZXMgYSBiaXQgdG8gaW5kaWNhdGUgc3RhdGljIHZz
LiBkeW5hbWljLiAgU2luY2UgdGhlIGZpZWxkIGlzIHNldmVuDQoNCiAgICA+IGJpdHMgbG9uZywg
dGhlIHBlcmZvcm1hbmNlIGlzIGNvbXBhcmFibGUgZm9yIHRoZSBkeW5hbWljIHRhYmxlICh5b3Ug
Y2FuDQoNCiAgICA+IGFjY2VzcyA2MyBlbnRyaWVzIGluIG9uZSBieXRlLCAxOTAgaW4gdHdvKSwg
YnV0IHlvdSBjYW4gaW5jcmVhc2UgdGhlIHNpemUgb2YNCg0KICAgID4gdGhlIHN0YXRpYyB0YWJs
ZSB3aXRob3V0IGh1cnRpbmcgdGhlIGR5bmFtaWMgdGFibGUuDQoNCg0KDQogICAgSXQgd2lsbCBt
YWtlIHRoZSBjb2RlIGxvb2sgbGVzcyAibWFnaWMiIQ0KDQoNCg0KICAgID4gQXMgYSByZXN1bHQs
IHdlJ3JlDQoNCiAgICA+IGJ1aWxkaW5nIGEgZnJlc2ggc3RhdGljDQoNCiAgICA+IHRhYmxlPGh0
dHBzOi8vZ2l0aHViLmNvbS9xdWljd2cvYmFzZS1kcmFmdHMvcHVsbC8xMzU1PiBiYXNlZCBvbiBx
dWVyaWVzDQoNCiAgICA+IGFnYWluc3QgSFRUUEFyY2hpdmUgZGF0YS4NCg0KICAgID4NCg0KICAg
ID4gVGhlIGtleSBxdWVzdGlvbiB0aGF0IGhhcyBjb21lIHVwIGluIGEgY291cGxlIHZlbnVlczog
IFdoYXQgcmVhbC13b3JsZA0KDQogICAgPiBoZWFkZXJzIGRvIHdlIHdhbnQgdG8gYXJ0aWZpY2lh
bGx5IHJlbW92ZSBmcm9tIHdoYXQgdGhlIGRhdGEgc2hvd3MsIGFuZCB3aGF0DQoNCiAgICA+IGhl
YWRlcnMgbm90IHNlZW4gYnkgSFRUUCBBcmNoaXZlIGRvIHdlIHdhbnQgdG8gZm9yY2UgaW4gYW55
d2F5Pw0KDQoNCg0KICAgIEkgYWdyZWUgd2l0aCBNYXJrIHRoYXQgcmVxdWVzdCByZWFsbHkgaXMg
d2hhdCBtYXR0ZXJzIHRoZSBtb3N0Lg0KDQoNCg0KICAgID4gICAqICAgUmVvcmRlcmVkIHRvIHB1
dCBoZWFkZXJzIHlvdSdyZSBsaWtlbHkgdG8gbmFtZS1yZWZlcmVuY2UgYXQgdGhlIGZyb250LA0K
DQogICAgPiAgIGVzcGVjaWFsbHkgaWYgeW91J3JlIHVubGlrZWx5IHRvIGFkZCB0aGVtIHRvIHRo
ZSBkeW5hbWljIHRhYmxlDQoNCg0KDQogICAgV2VsbCwgc29tZSBvZiB1cyBoYXZlIGJlZW4gcmVh
bGx5IGJvdGhlcmVkIGJ5IHRoZSBsYWNrIG9mIG9yZGVyaW5nDQoNCiAgICBpbiB0aGUgSFBBQ0sg
aGVhZGVycyB0YWJsZSwgbWFraW5nIGl0IHBhaW5mdWwgdG8gcGVyZm9ybSBlZmZpY2llbnQNCg0K
ICAgIGxvb2t1cHMuIEknZCBzdWdnZXN0IHRoYXQgdGhleSBhcmUgc29ydGVkIGJ5IChuYW1lLHZh
bHVlKSB0byBtYWtlDQoNCiAgICBpdCBwb3NzaWJsZSB0byBwZXJmb3JtIGVmZmljaWVudCBkaWNo
b3RvbWljIGxvb2t1cHMuDQoNCg0KDQogICAgPiBUaGUgcXVlc3Rpb24gaXMgd2hldGhlciB3ZSBz
aG91bGQgYWxzbyBiYWNrZmlsbCBoZWFkZXJzIHdoaWNoIEhUVFAgQXJjaGl2ZQ0KDQogICAgPiB3
b3VsZG4ndCBzZWUsIGRlbGV0ZSBoZWFkZXJzIHdlIHdpc2ggcGVvcGxlIHdvdWxkbid0IHVzZSwg
YW5kL29yIGluc2VydCB0aGUNCg0KICAgID4gb25lcyB3ZSBob3BlIHRoZXkgZXZlbnR1YWxseSB3
aWxsLiAgU29tZSBjYW5kaWRhdGVzOg0KDQoNCg0KICAgIFRoYXQncyBpbmRlZWQgYSBnb29kIHBv
aW50Lg0KDQoNCg0KICAgID4gICAqICAgQWRkIEFsdC1TdmMgZW50cnkgZm9yIEhUVFAvUVVJQyB3
aXRoIFFVSUMgdjENCg0KICAgID4gICAqICAgQWRkIFgtRm9yd2FyZGVkLUZvcg0KDQogICAgPiAg
ICogICBEb24ndCBhZGQgWC1Gb3J3YXJkZWQtRm9yLCBidXQgZG8gYWRkIEZvcndhcmRlZA0KDQoN
Cg0KICAgIEluIHByYWN0aWNlLCB3ZSBjYW4gdGFrZSBib3RoIG9yIG5vbmUuIEFmdGVyIGFsbCwg
bW9zdCBRVUlDIHJlcXVlc3RzIGdvaW5nDQoNCiAgICB0aHJvdWdoIHByb3hpZXMgd2lsbCBiZSBl
bmNyeXB0ZWQgYWxyZWFkeSB0aHVzIHRoZSBwcm94eSB3aWxsIG5vdCBiZSBhYmxlDQoNCiAgICB0
byBhZGQgdGhlc2UgZmllbGRzLiBGb3IgY2xlYXItdGV4dCByZXF1ZXN0cywgdGhlIGhlYWRlciBm
aWVsZCBuYW1lIGlzDQoNCiAgICByb3VnaGx5IGFzIGxvbmcgYXMgdGhlIHZhbHVlLCBzbyB0aGVy
ZSdzIG5vdCAqdGhhdCogbXVjaCB0byBzYXZlIGJ5IGVuY29kaW5nDQoNCiAgICB0aGVtLiBBbmQg
aXQgd2lsbCBub3QgY2hhbmdlIGluIG1vc3QgY29uc2VjdXRpdmUgcmVxdWVzdHMsIHNvIHRoZSBk
eW5hbWljDQoNCiAgICBjb21wcmVzc2lvbiB3aWxsIGJlIG1vcmUgZWZmaWNpZW50IHRoYW4gdGhl
IHN0YXRpYyBvbmUuIFRodXMgSSBzdWdnZXN0IHRoYXQNCg0KICAgIHdlIG9ubHkgYWRkIHRoZW0g
KmlmKiB3ZSBoYXZlIGVub3VnaCB1bnVzZWQgc2xvdHMgYXQgdGhlIGVuZCB0aGF0IHdlIGNhcmUN
Cg0KICAgIHRvIGNvdmVyIGEgdmVyeSBicm9hZCBzZXQuDQoNCg0KDQogICAgPiAgICogICBSZW1v
dmUgRXhwaXJlcyB0byBpbmNlbnQgdGhlIHVzZSBvZiBDYWNoZS1Db250cm9sDQoNCg0KDQogICAg
RXhwaXJlcyBpcyBmb3IgcmVzcG9uc2VzIG9ubHkgYW55d2F5LCB0aHVzIGl0IG1hdHRlcnMgbXVj
aCBsZXNzLiBDYWNoZS1jb250cm9sDQoNCiAgICBjYW4gYmUgdXNlZCBpbiBib3RoIGRpcmVjdGlv
bnMuIEkgdGhpbmsgdGhhdCB0aGUgdGVjaG5pY2FsIGZvY3VzIG9uIHJlcXVlc3QNCg0KICAgIG1h
eSBtYWtlIEV4cGlyZXMgZGlzYXBwZWFyIGZyb20gdGhlIHRhYmxlIDstKQ0KDQoNCg0KICAgID4g
ICAqICAgQ29sbGFwc2UgdGhlICJDb250ZW50LVR5cGU6IDx0aGluZ2V5PiIgYW5kICJDb250ZW50
LVR5cGU6IDx0aGluZ2V5PjsgY2hhcnNldD11dGYtOCIgZW50cmllcyB0b2dldGhlcg0KDQogICAg
PiAgICAgICogICAuLi5idXQgd2hpY2ggb25lIHRvIGtlZXA/DQoNCg0KDQogICAgUHJvYmFibHkg
anVzdCBmb2N1cyBvbiB0aGUgbW9zdCByZXBvcnRlZCBvbmVzIGFuZCBub3QgdHJ5IHRvIGNvbGxh
cHNlLiBJDQoNCiAgICBzdXNwZWN0IHRoYXQgd2Ugc2VlIGEgbG90IG9mIGVuLXVzIGFsb25lLCBh
bmQgdXRmLTggYWRkZWQgdG8gc29tZSBvdGhlcg0KDQogICAgbGFuZ3VhZ2VzLCBidXQgSSBjb3Vs
ZCBiZSB3cm9uZy4NCg0KDQoNCiAgICA+ICAgKiAgIEFkZCBDb250ZW50LUVuY29kaW5nIGFuZC9v
ciBBY2NlcHQtRW5jb2RpbmcgZW50cmllcyBmb3IgenN0ZA0KDQoNCg0KICAgIFByb2JhYmx5IHRv
byBlYXJseSB5ZXQsIGFuZCB3aWxsIG5vdCBtYWtlIGEgYmlnIGRpZmZlcmVuY2Ugb3ZlcmFsbCAo
YWxtb3N0DQoNCiAgICBvbmx5IHJlc3BvbnNlLCA0IGNoYXJhY3RlcnMgdmFsdWUpLg0KDQoNCg0K
ICAgID4gVGhlcmUncyBhbiBlbmRsZXNzIHBhcmFkZSBvZiBiaWtlc2hlZHMgaGVyZS4gIEFzIE1h
cnRpbiBoYXMgcG9pbnRlZCBvdXQsIHRoaXMNCg0KICAgID4gd2lsbCBuZXZlciBiZSBwZXJmZWN0
LCBzbyB0aGUgZ29hbCBpcyAiZ29vZCBlbm91Z2ggYW5kIGtlZXAgZ29pbmcuIiAgQW55DQoNCiAg
ICA+IHN0cm9uZyBmZWVsaW5ncyBhYm91dCBhbnkgb2YgdGhlc2UgYmVmb3JlIHdlIG1lcmdlIGl0
Pw0KDQoNCg0KICAgIE5vIHJlYWwgc3Ryb25nIGZlZWxpbmcgaGVyZSBleGNlcHQgYWJvdXQgdGhl
IGFiaWxpdHkgdG8gcGVyZm9ybSBmYXN0IGxvb2t1cHMuDQoNCg0KDQogICAgPiBBbHNvLCB0aGVy
ZSdzIGJlZW4gc29tZSBkaXNjdXNzaW9uIG9mIGEgbWVjaGFuaXNtIGZvciBzZWxlY3Rpbmcgb25l
IG9mDQoNCiAgICA+IHNldmVyYWwgc3RhdGljIHRhYmxlcyBhdCB0aGUgc3RhcnQgb2YgYSBjb25u
ZWN0aW9uLiAgSW4gdGhhdCBjYXNlLCB0aGUgc3BlYw0KDQogICAgPiB3b3VsZCBwcm9iYWJseSBk
ZWZpbmUgdGhyZWUgdGFibGVzIChjbGllbnQgaGVhZGVycywgc2VydmVyIGhlYWRlcnMgW2Zvcg0K
DQogICAgPiBzZXJ2ZXJzIHRoYXQgZG9uJ3QgcHVzaF0sIGNvbWJpbmVkIFtmb3Igc2VydmVycyB0
aGF0IHB1c2hdKSBhbmQgZW5hYmxlIGZ1dHVyZQ0KDQogICAgPiBSRkNzIHRvIGRlZmluZSBvdGhl
cnMgZm9yIHRhcmdldGVkIHNjZW5hcmlvcyAocHJveGllcywgdmlkZW8gcGxheWJhY2ssIElvVCwN
Cg0KICAgID4gZXRjLikuICBIb3cgbXVjaCBkb2VzIHRoYXQgaW50ZXJlc3QgZm9sa3M/DQoNCg0K
DQogICAgSSB0aGluayBpdCBjb3VsZCBiZSBhIGdvb2Qgc29sdXRpb24uIFdlIGNvdWxkIGFsc28g
dGhpbmsgYWJvdXQgQVBJcyBhbmQNCg0KICAgIHZhcmlvdXMgZGF0YWNlbnRlci1vcmllbnRlZCB1
c2UgY2FzZXMgKGVnOiB3ZWJzZXJ2aWNlIGV0Yykgd2hlcmUgdmVyeSBmYXN0DQoNCiAgICByZXNw
b25zZSBhbmQgbmV0d29yayBlZmZpY2llbmN5IG1hdHRlcnMuIEl0IGNvdWxkIGJlIGEgd2F5IHRv
IGVuY291cmFnZQ0KDQogICAgUVVJQyBhZG9wdGlvbiBpbnNpZGUgdGhlIERDLiBUaGUgcmlzayBo
b3dldmVyIGlzIHRoYXQgdGFibGVzIGRlZmluZWQgdG9vDQoNCiAgICBsYXRlIGFyZSBuZXZlciBk
ZXBsb3llZCBkdWUgdG8gaW50ZXJvcGVyYWJpbGl0eSBjb25jZXJucyAodW5sZXNzIHRoZXJlJ3MN
Cg0KICAgIGEgd2F5IHRvIGtub3cgdGhhdCBpdCB3aWxsIGJlIHN1cHBvcnRlZCBiZWZvcmUgZW5j
b2RpbmcpLiBUaHVzIGlmIHNvbWUNCg0KICAgIHBhcnRpY2lwYW50cyBhcmUgaW50ZXJlc3RlZCBp
biBvcHRpbWl6aW5nIGZvciBjZXJ0YWluIHVzZSBjYXNlcywgdGhleSBzaG91bGQNCg0KICAgIHBy
b2JhYmx5IHByb3ZpZGUgdGhlaXIgb3duIHRhYmxlcyB0byBiZSBtZXJnZWQgaW50byB0aGUgc3Rh
bmRhcmQgZnJvbSBkYXkgMS4NCg0KDQoNCiAgICBDaGVlcnMsDQoNCiAgICBXaWxseQ0KDQoNCg0K
DQoNCg0K

--_000_SN1PR08MB185459B20E930B87BAE380EFDA6A0SN1PR08MB1854namp_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
V2luZ2RpbmdzOw0KCXBhbm9zZS0xOjUgMCAwIDAgMCAwIDAgMCAwIDA7fQ0KQGZvbnQtZmFjZQ0K
CXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMg
MiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1
IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXByaW9y
aXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLk1z
b1BsYWluVGV4dCwgbGkuTXNvUGxhaW5UZXh0LCBkaXYuTXNvUGxhaW5UZXh0DQoJe21zby1zdHls
ZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiUGxhaW4gVGV4dCBDaGFyIjsNCgltYXJn
aW46MGluOw0KCW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNwYW4uUGxhaW5UZXh0Q2hhcg0KCXtt
c28tc3R5bGUtbmFtZToiUGxhaW4gVGV4dCBDaGFyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7
DQoJbXNvLXN0eWxlLWxpbms6IlBsYWluIFRleHQiOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCkBwYWdlIFdvcmRTZWN0aW9u
MQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47
fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQovKiBMaXN0IERlZmlu
aXRpb25zICovDQpAbGlzdCBsMA0KCXttc28tbGlzdC1pZDoxNDA0NDUxMTE2Ow0KCW1zby1saXN0
LXR5cGU6aHlicmlkOw0KCW1zby1saXN0LXRlbXBsYXRlLWlkczo5NTg4NDQzNzIgNjc2OTg2ODkg
Njc2OTg2OTEgNjc2OTg2OTMgNjc2OTg2ODkgNjc2OTg2OTEgNjc2OTg2OTMgNjc2OTg2ODkgNjc2
OTg2OTEgNjc2OTg2OTM7fQ0KQGxpc3QgbDA6bGV2ZWwxDQoJe21zby1sZXZlbC1udW1iZXItZm9y
bWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5v
bmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVp
bjsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWwyDQoJe21zby1sZXZlbC1u
dW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWIt
c3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVu
dDotLjI1aW47DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMDpsZXZlbDMN
Cgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsN
Cgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxl
ZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlz
dCBsMDpsZXZlbDQNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZl
bC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVy
LXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OlN5bWJv
bDt9DQpAbGlzdCBsMDpsZXZlbDUNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0K
CW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVs
LW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWls
eToiQ291cmllciBOZXciO30NCkBsaXN0IGwwOmxldmVsNg0KCXttc28tbGV2ZWwtbnVtYmVyLWZv
cm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDpu
b25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1
aW47DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwwOmxldmVsNw0KCXttc28tbGV2
ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZl
bC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0
LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwwOmxldmVsOA0K
CXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCglt
c28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7
DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxp
c3QgbDA6bGV2ZWw5DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2
ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJl
ci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpXaW5n
ZGluZ3M7fQ0Kb2wNCgl7bWFyZ2luLWJvdHRvbTowaW47fQ0KdWwNCgl7bWFyZ2luLWJvdHRvbTow
aW47fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVs
dHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0t
W2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlk
bWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2Vu
ZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9IiMwNTYzQzEiIHZsaW5r
PSIjOTU0RjcyIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij5ZZXMsIEkgdGhpbmsgeW91IG5lZWQgdGhlIGxvb2t1cCB0YWJsZSBmb3IgaW5kaWNl
cy4mbmJzcDsgQWxwaGFiZXRpY2FsIGRvZXNuJ3Qgd29yayBhcyB3ZWxsLCBiZWNhdXNlIHRoZXJl
IGFyZSB0d28ga2V5IGJhcnJpZXJzIHRvIGRlYWwgd2l0aDo8bzpwPjwvbzpwPjwvcD4NCjx1bCBz
dHlsZT0ibWFyZ2luLXRvcDowaW4iIHR5cGU9ImRpc2MiPg0KPGxpIGNsYXNzPSJNc29QbGFpblRl
eHQiIHN0eWxlPSJtc28tbGlzdDpsMCBsZXZlbDEgbGZvMSI+T25seSB0aGUgZmlyc3Qgc2l4dGVl
biBlbnRyaWVzIGNhbiBiZSBuYW1lLXJlZmVyZW5jZWQgaW4gYSBzaW5nbGUgYnl0ZS4mbmJzcDsg
V2UgZGVncmFkZWQgcGVyZm9ybWFuY2UgaW4gYSBwcmV2aW91cyBkcmFmdCBvZiB0aGlzIHRhYmxl
IGJlY2F1c2UgOnBhdGggd2FzbuKAmXQgaW4gdGhlIGZpcnN0IHNpeHRlZW4gZW50cmllcywgYW5k
IHRoZSBlbmNvZGVyIHRoYXQNCiB0cmllZCB0aGUgdXBkYXRlZCB0YWJsZSB1c2VkIHR3by1ieXRl
IG5hbWUgcmVmZXJlbmNlcyBmb3IgZXZlcnkgcmVxdWVzdC48bzpwPjwvbzpwPjwvbGk+PGxpIGNs
YXNzPSJNc29QbGFpblRleHQiIHN0eWxlPSJtc28tbGlzdDpsMCBsZXZlbDEgbGZvMSI+T25seSB0
aGUgZmlyc3Qgc2l4dHktZm91ciBlbnRyaWVzIGNhbiBiZSBpbmRleC1yZWZlcmVuY2VkIGluIGEg
c2luZ2xlIGJ5dGUuPG86cD48L286cD48L2xpPjwvdWw+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPlRoaXMgaW1w
bGllcyB0aGF0IHlvdSB3YW50IGFuIG9yZGVyaW5nIGJ5IGxpa2VsaWhvb2Qgb2YgdXNpbmcgdGhl
IG5hbWUgYXQgYWxsLCBieSBsaWtlbGlob29kIG9mIG5vdCBpbmRleGluZyB0aGUgdmFsdWUgZm9y
IHJlcGVhdCB1c2UsIGFuZCBieSBsaWtlbGlob29kIG9mIHVzaW5nIHRoZSBuYW1lJiM0Mzt2YWx1
ZSBwYWlyIGRpcmVjdGx5LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5XaGlsZSBhbiBh
bHBoYWJldGljYWxseS1zb3J0ZWQgbGlzdCBpc27igJl0IGltcG9zc2libGUgd2l0aGluIGVhY2gg
dGllciwgaXQgc2VlbXMgZWFzaWVyIHRvIG1haW50YWluIGEgc3RhdGljIG1hcCBvZiB0aGUgaW5k
aWNlcyB0aGFuIHRvIGFscGhhYmV0aWNhbGx5IGluZGV4IGludG8gZWFjaCB0aWVyIHRvIHNlZSBp
ZiB0aGUgaGVhZGVyIHlvdSB3YW50IGlzIHByZXNlbnQuPG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPknigJlkIGJlIG9wZW4gdG8gYWRkaXRpb25hbCBzb3VyY2VzIG9mIGRhdGEgdG8gcnVu
IHRoZSBzYW1lIHF1ZXJ5IGFnYWluc3QuJm5ic3A7IEFueSBicm93c2VycyB1cCB0byBydW5uaW5n
IGFuIGV4cGVyaW1lbnQgYW5kIHNoYXJpbmcgdGhlIHRlbGVtZXRyeT88bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS08YnI+DQpGcm9tOiBSb2Jl
cnRvIFBlb24gJmx0O2Zlbml4QGZiLmNvbSZndDsgPGJyPg0KU2VudDogVGh1cnNkYXksIE1heSAy
NCwgMjAxOCAxMDo1MyBBTTxicj4NClRvOiBXaWxseSBUYXJyZWF1ICZsdDt3QDF3dC5ldSZndDs7
IE1pa2UgQmlzaG9wICZsdDttYmlzaG9wQGV2ZXF1ZWZvdS5iZSZndDs8YnI+DQpDYzogcXVpY0Bp
ZXRmLm9yZzsgSFRUUCBXb3JraW5nIEdyb3VwICZsdDtpZXRmLWh0dHAtd2dAdzMub3JnJmd0Ozxi
cj4NClN1YmplY3Q6IFJlOiBRUEFDSyBhbmQgdGhlIFN0YXRpYyBUYWJsZTwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+T25lIGNvdWxkIG1ha2UgdGhlIGxvb2t1cCAobW9yZSkgZWZmaWNpZW50IGJ5IHN0b3Jp
bmcgdGhlIGluZGV4IChhIGJ5dGUgYXQgbW9zdCkgd2l0aCB0aGUga2V5LXZhbHVlIHBhaXIsIHdo
ZXJlIHRoZSBrZXktdmFsdWUgcGFpciB3ZXJlIHNvcnRlZCB2aWEgd2hhdGV2ZXIgc29ydGluZyB5
b3UnZCBmaW5kIG1vc3QgZWZmaWNpZW50LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+SWYgcmVvcmRlcmluZyBhbGxvd3MgZm9yIHNvbWUgaW5jcmVhc2VkIGVmZmljaWVu
Y3kgd2l0aG91dCBpbmNyZWFzaW5nIGJpdHMtb24td2lyZSwgSSdkIHRoaW5rIGl0IHNlZW1zIHJl
YXNvbmFibGUgdG8gY2hhbmdlLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5JIHdvdWxk
IG5vdCB0cnVzdCB0aGUgSFRUUCBBcmNoaXZlIHRvIGdpdmUgYSBmcmVxdWVuY3kgYW5hbHlzaXMg
Zm9yIHJlYWwtd29ybGQgdXNlLiBSZW1lbWJlciB0aGF0IHdlIGdhdGhlcmVkIHRoZSBmcmVxIGRh
dGEgZm9yIEhQQUNLIGZyb20gcmVhbC13b3JsZCB1c2UgYWNyb3NzIGEgaG9wZWZ1bGx5IG5vdC1z
by1iaWFzZWQgc2FtcGxlIHZpYSBicm93c2VycyBkaXJlY3RseS4gSWYgdGhlIHdvcmxkIGhhcw0K
IGNoYW5nZWQgc2luY2UgSFBBQ0sgY2FtZSBvdXQgaW4gdGVybXMgb2YgaGVhZGVyIGZyZXEgKHNl
ZW1zIHBvc3NpYmxlIGlmIG5vdCBwcm9iYWJsZSksIHRoZW4gcGVyaGFwcyB3ZSBzaG91bGQgY29u
c2lkZXIgYW4gdXBkYXRlIHRvIEhUVFAyL0hQQUNLIGFzIHdlbGw/PG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPkkgYWdyZWUgdGhhdCBwZXJmZWN0aW9uIGhlcmUgaXNuJ3QgcmVhbGx5IG5l
ZWRlZCwgYnV0IEknbSBub3Qgc3VyZSBhZGRpbmcgaXRlbXMgdG8gdGhlIHRhYmxlIGFyYml0cmFy
aWx5IG1ha2VzIHNlbnNlIGVpdGhlci48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+LT1S
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPu+7v09uIDUvMjMvMTgsIDk6NDIgUE0sICZx
dW90O1FVSUMgb24gYmVoYWxmIG9mIFdpbGx5IFRhcnJlYXUmcXVvdDsgJmx0OzxhIGhyZWY9Im1h
aWx0bzpxdWljLWJvdW5jZXNAaWV0Zi5vcmclMjBvbiUyMGJlaGFsZiUyMG9mJTIwd0Axd3QuZXUi
PjxzcGFuIHN0eWxlPSJjb2xvcjp3aW5kb3d0ZXh0O3RleHQtZGVjb3JhdGlvbjpub25lIj5xdWlj
LWJvdW5jZXNAaWV0Zi5vcmcgb24gYmVoYWxmIG9mIHdAMXd0LmV1PC9zcGFuPjwvYT4mZ3Q7DQog
d3JvdGU6PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48bzpwPiZuYnNw
OzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyBI
aSBNaWtlLDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5i
c3A7Jm5ic3A7IDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7T24gV2VkLCBNYXkgMjMsIDIwMTggYXQgMTE6MTY6MThQTSAmIzQz
OzAwMDAsIE1pa2UgQmlzaG9wIHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDsgUmF0aGVyIHRoYW4gaW5kZXhpbmcgdGhl
IHRhYmxlcyB0b2dldGhlciBhbmQgaGF2aW5nIHRoZSBzdGF0aWMgdGFibGUgYXQgMS02MSw8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyAm
Z3Q7IFFQQUNLIHVzZXMgYSBiaXQgdG8gaW5kaWNhdGUgc3RhdGljIHZzLiBkeW5hbWljLiZuYnNw
OyBTaW5jZSB0aGUgZmllbGQgaXMgc2V2ZW48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IGJpdHMgbG9uZywgdGhlIHBlcmZvcm1h
bmNlIGlzIGNvbXBhcmFibGUgZm9yIHRoZSBkeW5hbWljIHRhYmxlICh5b3UgY2FuPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyBh
Y2Nlc3MgNjMgZW50cmllcyBpbiBvbmUgYnl0ZSwgMTkwIGluIHR3byksIGJ1dCB5b3UgY2FuIGlu
Y3JlYXNlIHRoZSBzaXplIG9mPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij4mbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyB0aGUgc3RhdGljIHRhYmxlIHdpdGhvdXQgaHVydGlu
ZyB0aGUgZHluYW1pYyB0YWJsZS48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRl
eHQiPiZuYnNwOyZuYnNwOyZuYnNwOyA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO0l0IHdpbGwgbWFrZSB0aGUgY29kZSBsb29r
IGxlc3MgJnF1b3Q7bWFnaWMmcXVvdDshPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmZ3Q7IEFzIGEgcmVzdWx0LCB3ZSdy
ZTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5i
c3A7ICZndDsgYnVpbGRpbmcgYSBmcmVzaCBzdGF0aWM8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IHRhYmxlJmx0OzxhIGhyZWY9
Imh0dHBzOi8vZ2l0aHViLmNvbS9xdWljd2cvYmFzZS1kcmFmdHMvcHVsbC8xMzU1Ij48c3BhbiBz
dHlsZT0iY29sb3I6d2luZG93dGV4dDt0ZXh0LWRlY29yYXRpb246bm9uZSI+aHR0cHM6Ly9naXRo
dWIuY29tL3F1aWN3Zy9iYXNlLWRyYWZ0cy9wdWxsLzEzNTU8L3NwYW4+PC9hPiZndDsgYmFzZWQg
b24gcXVlcmllczxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7
Jm5ic3A7ICZuYnNwOyZndDsgYWdhaW5zdCBIVFRQQXJjaGl2ZSBkYXRhLjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDsgPG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmZ3Q7IFRoZSBrZXkgcXVlc3Rpb24gdGhhdCBoYXMgY29tZSB1cCBpbiBhIGNvdXBsZSB2ZW51
ZXM6Jm5ic3A7IFdoYXQgcmVhbC13b3JsZDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDsgaGVhZGVycyBkbyB3ZSB3YW50IHRvIGFy
dGlmaWNpYWxseSByZW1vdmUgZnJvbSB3aGF0IHRoZSBkYXRhIHNob3dzLCBhbmQgd2hhdDxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZn
dDsgaGVhZGVycyBub3Qgc2VlbiBieSBIVFRQIEFyY2hpdmUgZG8gd2Ugd2FudCB0byBmb3JjZSBp
biBhbnl3YXk/PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsm
bmJzcDsmbmJzcDsgPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDtJIGFncmVlIHdpdGggTWFyayB0aGF0IHJlcXVlc3QgcmVhbGx5
IGlzIHdoYXQgbWF0dGVycyB0aGUgbW9zdC48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZndDsmbmJzcDsmbmJzcDsgKiZu
YnNwOyZuYnNwOyBSZW9yZGVyZWQgdG8gcHV0IGhlYWRlcnMgeW91J3JlIGxpa2VseSB0byBuYW1l
LXJlZmVyZW5jZSBhdCB0aGUgZnJvbnQsPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyZuYnNwOyZuYnNwOyBlc3BlY2lhbGx5IGlm
IHlvdSdyZSB1bmxpa2VseSB0byBhZGQgdGhlbSB0byB0aGUgZHluYW1pYyB0YWJsZTxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7V2VsbCwgc29tZSBvZiB1cyBoYXZlIGJlZW4gcmVhbGx5IGJvdGhlcmVkIGJ5IHRoZSBsYWNr
IG9mIG9yZGVyaW5nPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJz
cDsmbmJzcDsmbmJzcDsgaW4gdGhlIEhQQUNLIGhlYWRlcnMgdGFibGUsIG1ha2luZyBpdCBwYWlu
ZnVsIHRvIHBlcmZvcm0gZWZmaWNpZW50PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgbG9va3Vwcy4gSSdkIHN1Z2dlc3QgdGhhdCB0aGV5
IGFyZSBzb3J0ZWQgYnkgKG5hbWUsdmFsdWUpIHRvIG1ha2U8bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyBpdCBwb3NzaWJsZSB0byBwZXJm
b3JtIGVmZmljaWVudCBkaWNob3RvbWljIGxvb2t1cHMuPG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgPG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmZ3Q7IFRoZSBxdWVz
dGlvbiBpcyB3aGV0aGVyIHdlIHNob3VsZCBhbHNvIGJhY2tmaWxsIGhlYWRlcnMgd2hpY2ggSFRU
UCBBcmNoaXZlPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsm
bmJzcDsmbmJzcDsgJmd0OyB3b3VsZG4ndCBzZWUsIGRlbGV0ZSBoZWFkZXJzIHdlIHdpc2ggcGVv
cGxlIHdvdWxkbid0IHVzZSwgYW5kL29yIGluc2VydCB0aGU8bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IG9uZXMgd2UgaG9wZSB0
aGV5IGV2ZW50dWFsbHkgd2lsbC4mbmJzcDsgU29tZSBjYW5kaWRhdGVzOjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7VGhh
dCdzIGluZGVlZCBhIGdvb2QgcG9pbnQuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmZ3Q7Jm5ic3A7Jm5ic3A7ICombmJz
cDsmbmJzcDsgQWRkIEFsdC1TdmMgZW50cnkgZm9yIEhUVFAvUVVJQyB3aXRoIFFVSUMgdjE8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyAm
Z3Q7Jm5ic3A7Jm5ic3A7ICombmJzcDsmbmJzcDsgQWRkIFgtRm9yd2FyZGVkLUZvcjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDsm
bmJzcDsmbmJzcDsgKiZuYnNwOyZuYnNwOyBEb24ndCBhZGQgWC1Gb3J3YXJkZWQtRm9yLCBidXQg
ZG8gYWRkIEZvcndhcmRlZDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7SW4gcHJhY3RpY2UsIHdlIGNhbiB0YWtlIGJvdGgg
b3Igbm9uZS4gQWZ0ZXIgYWxsLCBtb3N0IFFVSUMgcmVxdWVzdHMgZ29pbmc8bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyB0aHJvdWdoIHBy
b3hpZXMgd2lsbCBiZSBlbmNyeXB0ZWQgYWxyZWFkeSB0aHVzIHRoZSBwcm94eSB3aWxsIG5vdCBi
ZSBhYmxlPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJz
cDsmbmJzcDsgdG8gYWRkIHRoZXNlIGZpZWxkcy4gRm9yIGNsZWFyLXRleHQgcmVxdWVzdHMsIHRo
ZSBoZWFkZXIgZmllbGQgbmFtZSBpczxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IHJvdWdobHkgYXMgbG9uZyBhcyB0aGUgdmFsdWUsIHNv
IHRoZXJlJ3Mgbm90ICp0aGF0KiBtdWNoIHRvIHNhdmUgYnkgZW5jb2Rpbmc8bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyB0aGVtLiBBbmQg
aXQgd2lsbCBub3QgY2hhbmdlIGluIG1vc3QgY29uc2VjdXRpdmUgcmVxdWVzdHMsIHNvIHRoZSBk
eW5hbWljPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJz
cDsmbmJzcDsgY29tcHJlc3Npb24gd2lsbCBiZSBtb3JlIGVmZmljaWVudCB0aGFuIHRoZSBzdGF0
aWMgb25lLiBUaHVzIEkgc3VnZ2VzdCB0aGF0PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgd2Ugb25seSBhZGQgdGhlbSAqaWYqIHdlIGhh
dmUgZW5vdWdoIHVudXNlZCBzbG90cyBhdCB0aGUgZW5kIHRoYXQgd2UgY2FyZTxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IHRvIGNvdmVy
IGEgdmVyeSBicm9hZCBzZXQuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij4mbmJzcDsmbmJzcDsmbmJzcDsgPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmZ3Q7Jm5ic3A7Jm5ic3A7ICombmJzcDsmbmJz
cDsgUmVtb3ZlIEV4cGlyZXMgdG8gaW5jZW50IHRoZSB1c2Ugb2YgQ2FjaGUtQ29udHJvbDxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7RXhwaXJlcyBpcyBmb3IgcmVzcG9uc2VzIG9ubHkgYW55d2F5LCB0aHVzIGl0IG1hdHRl
cnMgbXVjaCBsZXNzLiBDYWNoZS1jb250cm9sPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgY2FuIGJlIHVzZWQgaW4gYm90aCBkaXJlY3Rp
b25zLiBJIHRoaW5rIHRoYXQgdGhlIHRlY2huaWNhbCBmb2N1cyBvbiByZXF1ZXN0PG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgbWF5IG1h
a2UgRXhwaXJlcyBkaXNhcHBlYXIgZnJvbSB0aGUgdGFibGUgOy0pPG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgPG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmZ3Q7Jm5i
c3A7Jm5ic3A7ICombmJzcDsmbmJzcDsgQ29sbGFwc2UgdGhlICZxdW90O0NvbnRlbnQtVHlwZTog
Jmx0O3RoaW5nZXkmZ3Q7JnF1b3Q7IGFuZCAmcXVvdDtDb250ZW50LVR5cGU6ICZsdDt0aGluZ2V5
Jmd0OzsgY2hhcnNldD11dGYtOCZxdW90OyBlbnRyaWVzIHRvZ2V0aGVyPG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyAqJm5ic3A7Jm5ic3A7IC4uLmJ1dCB3aGljaCBvbmUgdG8g
a2VlcD88bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNw
OyZuYnNwOyA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwO1Byb2JhYmx5IGp1c3QgZm9jdXMgb24gdGhlIG1vc3QgcmVwb3J0ZWQg
b25lcyBhbmQgbm90IHRyeSB0byBjb2xsYXBzZS4gSTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IHN1c3BlY3QgdGhhdCB3ZSBzZWUgYSBs
b3Qgb2YgZW4tdXMgYWxvbmUsIGFuZCB1dGYtOCBhZGRlZCB0byBzb21lIG90aGVyPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgbGFuZ3Vh
Z2VzLCBidXQgSSBjb3VsZCBiZSB3cm9uZy48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZndDsmbmJzcDsmbmJzcDsgKiZu
YnNwOyZuYnNwOyBBZGQgQ29udGVudC1FbmNvZGluZyBhbmQvb3IgQWNjZXB0LUVuY29kaW5nIGVu
dHJpZXMgZm9yIHpzdGQ8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZu
YnNwOyZuYnNwOyZuYnNwOyA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQi
PiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO1Byb2JhYmx5IHRvbyBlYXJseSB5ZXQsIGFuZCB3aWxs
IG5vdCBtYWtlIGEgYmlnIGRpZmZlcmVuY2Ugb3ZlcmFsbCAoYWxtb3N0PG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgb25seSByZXNwb25z
ZSwgNCBjaGFyYWN0ZXJzIHZhbHVlKS48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZndDsgVGhlcmUncyBhbiBlbmRsZXNz
IHBhcmFkZSBvZiBiaWtlc2hlZHMgaGVyZS4mbmJzcDsgQXMgTWFydGluIGhhcyBwb2ludGVkIG91
dCwgdGhpczxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5i
c3A7Jm5ic3A7ICZndDsgd2lsbCBuZXZlciBiZSBwZXJmZWN0LCBzbyB0aGUgZ29hbCBpcyAmcXVv
dDtnb29kIGVub3VnaCBhbmQga2VlcCBnb2luZy4mcXVvdDsmbmJzcDsgQW55PG86cD48L286cD48
L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyBzdHJv
bmcgZmVlbGluZ3MgYWJvdXQgYW55IG9mIHRoZXNlIGJlZm9yZSB3ZSBtZXJnZSBpdD88bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyA8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwO05vIHJlYWwgc3Ryb25nIGZlZWxpbmcgaGVyZSBleGNlcHQgYWJvdXQgdGhlIGFiaWxpdHkg
dG8gcGVyZm9ybSBmYXN0IGxvb2t1cHMuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmZ3Q7IEFsc28sIHRoZXJlJ3MgYmVl
biBzb21lIGRpc2N1c3Npb24gb2YgYSBtZWNoYW5pc20gZm9yIHNlbGVjdGluZyBvbmUgb2Y8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyAm
Z3Q7IHNldmVyYWwgc3RhdGljIHRhYmxlcyBhdCB0aGUgc3RhcnQgb2YgYSBjb25uZWN0aW9uLiZu
YnNwOyBJbiB0aGF0IGNhc2UsIHRoZSBzcGVjPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyB3b3VsZCBwcm9iYWJseSBkZWZpbmUg
dGhyZWUgdGFibGVzIChjbGllbnQgaGVhZGVycywgc2VydmVyIGhlYWRlcnMgW2ZvcjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDsg
c2VydmVycyB0aGF0IGRvbid0IHB1c2hdLCBjb21iaW5lZCBbZm9yIHNlcnZlcnMgdGhhdCBwdXNo
XSkgYW5kIGVuYWJsZSBmdXR1cmU8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRl
eHQiPiZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IFJGQ3MgdG8gZGVmaW5lIG90aGVycyBmb3IgdGFy
Z2V0ZWQgc2NlbmFyaW9zIChwcm94aWVzLCB2aWRlbyBwbGF5YmFjaywgSW9ULDxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDsgZXRj
LikuJm5ic3A7IEhvdyBtdWNoIGRvZXMgdGhhdCBpbnRlcmVzdCBmb2xrcz88bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyA8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO0kg
dGhpbmsgaXQgY291bGQgYmUgYSBnb29kIHNvbHV0aW9uLiBXZSBjb3VsZCBhbHNvIHRoaW5rIGFi
b3V0IEFQSXMgYW5kPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJz
cDsmbmJzcDsmbmJzcDsgdmFyaW91cyBkYXRhY2VudGVyLW9yaWVudGVkIHVzZSBjYXNlcyAoZWc6
IHdlYnNlcnZpY2UgZXRjKSB3aGVyZSB2ZXJ5IGZhc3Q8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyByZXNwb25zZSBhbmQgbmV0d29yayBl
ZmZpY2llbmN5IG1hdHRlcnMuIEl0IGNvdWxkIGJlIGEgd2F5IHRvIGVuY291cmFnZTxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IFFVSUMg
YWRvcHRpb24gaW5zaWRlIHRoZSBEQy4gVGhlIHJpc2sgaG93ZXZlciBpcyB0aGF0IHRhYmxlcyBk
ZWZpbmVkIHRvbzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7
Jm5ic3A7Jm5ic3A7IGxhdGUgYXJlIG5ldmVyIGRlcGxveWVkIGR1ZSB0byBpbnRlcm9wZXJhYmls
aXR5IGNvbmNlcm5zICh1bmxlc3MgdGhlcmUnczxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IGEgd2F5IHRvIGtub3cgdGhhdCBpdCB3aWxs
IGJlIHN1cHBvcnRlZCBiZWZvcmUgZW5jb2RpbmcpLiBUaHVzIGlmIHNvbWU8bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyBwYXJ0aWNpcGFu
dHMgYXJlIGludGVyZXN0ZWQgaW4gb3B0aW1pemluZyBmb3IgY2VydGFpbiB1c2UgY2FzZXMsIHRo
ZXkgc2hvdWxkPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsm
bmJzcDsmbmJzcDsgcHJvYmFibHkgcHJvdmlkZSB0aGVpciBvd24gdGFibGVzIHRvIGJlIG1lcmdl
ZCBpbnRvIHRoZSBzdGFuZGFyZCBmcm9tIGRheSAxLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Q2hlZXJzLDxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IFdpbGx5
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJz
cDsgPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_SN1PR08MB185459B20E930B87BAE380EFDA6A0SN1PR08MB1854namp_--


From nobody Thu May 24 11:40:20 2018
Return-Path: <prvs=868201a72d=fenix@fb.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 947ED12E898 for <quic@ietfa.amsl.com>; Thu, 24 May 2018 11:40:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.709
X-Spam-Level: 
X-Spam-Status: No, score=-2.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, T_DKIMWL_WL_MED=-0.01, T_KAM_HTML_FONT_INVALID=0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=PTgh3dOd; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=Z45efed2
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 IFgDdEZf73S9 for <quic@ietfa.amsl.com>; Thu, 24 May 2018 11:40:14 -0700 (PDT)
Received: from mx0b-00082601.pphosted.com (mx0b-00082601.pphosted.com [67.231.153.30]) (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 0AB1A12EB00 for <quic@ietf.org>; Thu, 24 May 2018 11:40:13 -0700 (PDT)
Received: from pps.filterd (m0148460.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w4OIck1Q031746; Thu, 24 May 2018 11:39:47 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=facebook; bh=sItpZMGMPz212YUgJF7gc9rfUNo+SWqXomxYfreEq2M=; b=PTgh3dOdYL/oMtf0PSJFJjpI6ad9T60XVguh+XA+juNkCnWNGxwcoz0MvY/evly85zrQ bKkMqELgkdNAyIy8t3nWEUsX4EXvHcQE8+NWQndxmRgHl9hV2HE14SzAE3EGNghCrAhz 580JPimVwxcuP5UdfFmyrZuhJU1cBZUe6vg= 
Received: from mail.thefacebook.com ([199.201.64.23]) by mx0a-00082601.pphosted.com with ESMTP id 2j61qpr81p-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 24 May 2018 11:39:46 -0700
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (192.168.54.28) by o365-in.thefacebook.com (192.168.16.17) with Microsoft SMTP Server (TLS) id 14.3.361.1; Thu, 24 May 2018 11:39:43 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=sItpZMGMPz212YUgJF7gc9rfUNo+SWqXomxYfreEq2M=; b=Z45efed2nyuzKqrizqv/l5kRSsQMsUfSt2RMgD3b+Ov0uTHiFORsS3HhTV/Fh8MRSNDGj/3A0UQgYZrdTMRM96EL1dBFv2t6qrNV2WSalVC4ec7AA5CyJH8YhMKjSb8TGcLPMp4UhPubN56p4UPkyFk7BSQwMQYU9cTBOm3Z6BA=
Received: from BYAPR15MB2312.namprd15.prod.outlook.com (52.135.197.146) by BYAPR15MB2406.namprd15.prod.outlook.com (52.135.198.143) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.776.11; Thu, 24 May 2018 18:39:41 +0000
Received: from BYAPR15MB2312.namprd15.prod.outlook.com ([fe80::b434:da9b:6102:49eb]) by BYAPR15MB2312.namprd15.prod.outlook.com ([fe80::b434:da9b:6102:49eb%13]) with mapi id 15.20.0776.019; Thu, 24 May 2018 18:39:41 +0000
From: Roberto Peon <fenix@fb.com>
To: Mike Bishop <mbishop@evequefou.be>, Willy Tarreau <w@1wt.eu>
CC: "quic@ietf.org" <quic@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Subject: Re: QPACK and the Static Table
Thread-Topic: QPACK and the Static Table
Thread-Index: AdPy6/ObcVQE/1QBQB2X+UF0YtinwQALZGwAAAz5BYAAD2QCcP//kdoA
Date: Thu, 24 May 2018 18:39:41 +0000
Message-ID: <B0995EA8-A329-49F3-8B47-0F6042D38DFC@fb.com>
References: <SN1PR08MB1854395A2875541C4DC0673DDA6B0@SN1PR08MB1854.namprd08.prod.outlook.com> <20180524044146.GA5215@1wt.eu> <993659D9-8A3B-4375-AEC6-0B7706F96B42@fb.com> <SN1PR08MB185459B20E930B87BAE380EFDA6A0@SN1PR08MB1854.namprd08.prod.outlook.com>
In-Reply-To: <SN1PR08MB185459B20E930B87BAE380EFDA6A0@SN1PR08MB1854.namprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.d.0.180513
x-originating-ip: [2620:10d:c090:200::7:88c]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR15MB2406; 7:jerfUeHZLTOQ858ASLPJ3iEE7UpUBWPoGiXCe8atfteh4ccv/IcQbSKWyjdl5i3OtygtGyY+VC6Ajxkjb2nK7EiYfhhqM+YnMiShc8l6YiVFhG+6r74VDTDJvVeRl/BUyq4z422kW9b/XQGOdXxaJgJtBt6Ekurcc9le4vfBf+LSzBA+03yVxUjTRWKRFZ/gQ7Ka+kphLasb7oi8om8G1l1f20RyIYVMlN/oroBIZTFzT68I3eJO9VmpuMJFloA8; 20:k4vroE5Rwl90+rV4gXWiHXqP2fXYcoY5+fhJ5N1sW+yN26JEQOW3tFbPMnBb0GlEzf3nKCVgWp26pALkj1siTNcsxqND0bs8g6db8kaE+Z7+TkfTDMvJpy5ANpaZGbbjfItc8hg7HWb0Dkxr88LuYj/gRn7H2rqMevVIxUEjIrk=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BYAPR15MB2406; 
x-ms-traffictypediagnostic: BYAPR15MB2406:
x-microsoft-antispam-prvs: <BYAPR15MB24063F33D8411F876D31CEE2CD6A0@BYAPR15MB2406.namprd15.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(158342451672863)(166708455590820)(67672495146484)(21748063052155)(17755550239193);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(3231254)(11241501184)(944501410)(52105095)(10201501046)(3002001)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123564045)(20161123562045)(20161123560045)(20161123558120)(6072148)(201708071742011)(7699016); SRVR:BYAPR15MB2406; BCL:0; PCL:0; RULEID:; SRVR:BYAPR15MB2406; 
x-forefront-prvs: 0682FC00E8
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(346002)(396003)(39380400002)(366004)(39860400002)(52314003)(51444003)(189003)(199004)(13464003)(68736007)(59450400001)(5250100002)(6246003)(76176011)(7736002)(53546011)(6506007)(6436002)(14454004)(102836004)(93886005)(316002)(81156014)(5660300001)(3660700001)(99286004)(3280700002)(2906002)(81166006)(8936002)(446003)(11346002)(606006)(46003)(4326008)(476003)(2616005)(53936002)(486006)(36756003)(6116002)(82746002)(54896002)(33656002)(83716003)(86362001)(6512007)(6306002)(236005)(54906003)(2900100001)(229853002)(6486002)(186003)(110136005)(58126008)(478600001)(25786009)(106356001)(97736004)(105586002)(8676002)(781001)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR15MB2406; H:BYAPR15MB2312.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: fb.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: Ka2u2HjA5Guui74Qw9bG7zXndVDafAk3EoKc8zWaB0YKgezQxUjbQDhZcyqhKn+BQLtR5kTxnA/4/HPJDjvreAo5CFRE0urKDtZr3ofvDUyn4dUWIo45niO2zoKQrhe0474P73DgVQg2sX25hUu/rH4gCMRBAyu4Q3ZCOfHhSbJDS5JhbktdD+v0J+udWLQ9
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_B0995EA8A32949F38B470F6042D38DFCfbcom_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: a98934ce-5320-48af-9fc5-08d5c1a5b671
X-MS-Exchange-CrossTenant-Network-Message-Id: a98934ce-5320-48af-9fc5-08d5c1a5b671
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 May 2018 18:39:41.6207 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR15MB2406
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-24_06:, , signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Vq5_rd_eeSuCRT0PxNGLrIPDIO0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 May 2018 18:40:19 -0000

--_000_B0995EA8A32949F38B470F6042D38DFCfbcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

VG8gYmUgY2xlYXIsIEkgZG9u4oCZdCBiZWxpZXZlIHRoYXQgc29ydGluZyB0aGUgdGFibGUgaW4g
UVBBQ0sgaXMgbmVjZXNzYXJ5IGZvciBDUFXigJRJIGFncmVlIGl0IHNob3VsZCBiZSBzb3J0ZWQg
YnkgdGhpbmdzIHdoaWNoIGltcHJvdmUgKG9yIGFyZSBuZXV0cmFsIHRvKSBvbi10aGUtd2lyZSBl
ZmZpY2llbmN5Lg0KQ1BVLXJlbGF0ZWQgY29zdHMgZm9yIGxvb2t1cHMgY2FuIGJlIGltcHJvdmVk
IChhcyBEbWl0cmkgbm90ZXMpIGJ5IHN0cnVjdHVyaW5nIHRoZSBsb29rdXBzIGRpZmZlcmVudGx5
IGluIHRoZSBpbXBsZW1lbnRhdGlvbi4NCkZvciBpbnN0YW5jZSwgdGhlcmUgYXJlIGZ1biB3YXlz
IG9uZSBjYW4gdXNlIFNTRSAoYW5kIHN1Y2Nlc3NvcnMpIHRvIHNlbGVjdCBhbW9uZ3N0IHRoZSBo
ZWFkZXJzIGluIHRoZSBzdGF0aWMgdGFibGUgbW9yZSBxdWlja2x5IHRoYW4gb25lIG1pZ2h0IGFj
aGlldmUgd2l0aCBhIGhhc2gtbWFwLg0KLT1SDQoNCkZyb206IE1pa2UgQmlzaG9wIDxtYmlzaG9w
QGV2ZXF1ZWZvdS5iZT4NCkRhdGU6IFRodXJzZGF5LCBNYXkgMjQsIDIwMTggYXQgMTE6MjEgQU0N
ClRvOiBSb2JlcnRvIFBlb24gPGZlbml4QGZiLmNvbT4sIFdpbGx5IFRhcnJlYXUgPHdAMXd0LmV1
Pg0KQ2M6ICJxdWljQGlldGYub3JnIiA8cXVpY0BpZXRmLm9yZz4sIEhUVFAgV29ya2luZyBHcm91
cCA8aWV0Zi1odHRwLXdnQHczLm9yZz4NClN1YmplY3Q6IFJFOiBRUEFDSyBhbmQgdGhlIFN0YXRp
YyBUYWJsZQ0KDQoNClllcywgSSB0aGluayB5b3UgbmVlZCB0aGUgbG9va3VwIHRhYmxlIGZvciBp
bmRpY2VzLiAgQWxwaGFiZXRpY2FsIGRvZXNuJ3Qgd29yayBhcyB3ZWxsLCBiZWNhdXNlIHRoZXJl
IGFyZSB0d28ga2V5IGJhcnJpZXJzIHRvIGRlYWwgd2l0aDoNCg0KICAqICAgT25seSB0aGUgZmly
c3Qgc2l4dGVlbiBlbnRyaWVzIGNhbiBiZSBuYW1lLXJlZmVyZW5jZWQgaW4gYSBzaW5nbGUgYnl0
ZS4gIFdlIGRlZ3JhZGVkIHBlcmZvcm1hbmNlIGluIGEgcHJldmlvdXMgZHJhZnQgb2YgdGhpcyB0
YWJsZSBiZWNhdXNlIDpwYXRoIHdhc27igJl0IGluIHRoZSBmaXJzdCBzaXh0ZWVuIGVudHJpZXMs
IGFuZCB0aGUgZW5jb2RlciB0aGF0IHRyaWVkIHRoZSB1cGRhdGVkIHRhYmxlIHVzZWQgdHdvLWJ5
dGUgbmFtZSByZWZlcmVuY2VzIGZvciBldmVyeSByZXF1ZXN0Lg0KICAqICAgT25seSB0aGUgZmly
c3Qgc2l4dHktZm91ciBlbnRyaWVzIGNhbiBiZSBpbmRleC1yZWZlcmVuY2VkIGluIGEgc2luZ2xl
IGJ5dGUuDQoNCg0KDQpUaGlzIGltcGxpZXMgdGhhdCB5b3Ugd2FudCBhbiBvcmRlcmluZyBieSBs
aWtlbGlob29kIG9mIHVzaW5nIHRoZSBuYW1lIGF0IGFsbCwgYnkgbGlrZWxpaG9vZCBvZiBub3Qg
aW5kZXhpbmcgdGhlIHZhbHVlIGZvciByZXBlYXQgdXNlLCBhbmQgYnkgbGlrZWxpaG9vZCBvZiB1
c2luZyB0aGUgbmFtZSt2YWx1ZSBwYWlyIGRpcmVjdGx5Lg0KDQoNCg0KV2hpbGUgYW4gYWxwaGFi
ZXRpY2FsbHktc29ydGVkIGxpc3QgaXNu4oCZdCBpbXBvc3NpYmxlIHdpdGhpbiBlYWNoIHRpZXIs
IGl0IHNlZW1zIGVhc2llciB0byBtYWludGFpbiBhIHN0YXRpYyBtYXAgb2YgdGhlIGluZGljZXMg
dGhhbiB0byBhbHBoYWJldGljYWxseSBpbmRleCBpbnRvIGVhY2ggdGllciB0byBzZWUgaWYgdGhl
IGhlYWRlciB5b3Ugd2FudCBpcyBwcmVzZW50Lg0KDQoNCg0KSeKAmWQgYmUgb3BlbiB0byBhZGRp
dGlvbmFsIHNvdXJjZXMgb2YgZGF0YSB0byBydW4gdGhlIHNhbWUgcXVlcnkgYWdhaW5zdC4gIEFu
eSBicm93c2VycyB1cCB0byBydW5uaW5nIGFuIGV4cGVyaW1lbnQgYW5kIHNoYXJpbmcgdGhlIHRl
bGVtZXRyeT8NCg0KDQoNCi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tDQpGcm9tOiBSb2JlcnRv
IFBlb24gPGZlbml4QGZiLmNvbT4NClNlbnQ6IFRodXJzZGF5LCBNYXkgMjQsIDIwMTggMTA6NTMg
QU0NClRvOiBXaWxseSBUYXJyZWF1IDx3QDF3dC5ldT47IE1pa2UgQmlzaG9wIDxtYmlzaG9wQGV2
ZXF1ZWZvdS5iZT4NCkNjOiBxdWljQGlldGYub3JnOyBIVFRQIFdvcmtpbmcgR3JvdXAgPGlldGYt
aHR0cC13Z0B3My5vcmc+DQpTdWJqZWN0OiBSZTogUVBBQ0sgYW5kIHRoZSBTdGF0aWMgVGFibGUN
Cg0KDQoNCk9uZSBjb3VsZCBtYWtlIHRoZSBsb29rdXAgKG1vcmUpIGVmZmljaWVudCBieSBzdG9y
aW5nIHRoZSBpbmRleCAoYSBieXRlIGF0IG1vc3QpIHdpdGggdGhlIGtleS12YWx1ZSBwYWlyLCB3
aGVyZSB0aGUga2V5LXZhbHVlIHBhaXIgd2VyZSBzb3J0ZWQgdmlhIHdoYXRldmVyIHNvcnRpbmcg
eW91J2QgZmluZCBtb3N0IGVmZmljaWVudC4NCg0KSWYgcmVvcmRlcmluZyBhbGxvd3MgZm9yIHNv
bWUgaW5jcmVhc2VkIGVmZmljaWVuY3kgd2l0aG91dCBpbmNyZWFzaW5nIGJpdHMtb24td2lyZSwg
SSdkIHRoaW5rIGl0IHNlZW1zIHJlYXNvbmFibGUgdG8gY2hhbmdlLg0KDQoNCg0KSSB3b3VsZCBu
b3QgdHJ1c3QgdGhlIEhUVFAgQXJjaGl2ZSB0byBnaXZlIGEgZnJlcXVlbmN5IGFuYWx5c2lzIGZv
ciByZWFsLXdvcmxkIHVzZS4gUmVtZW1iZXIgdGhhdCB3ZSBnYXRoZXJlZCB0aGUgZnJlcSBkYXRh
IGZvciBIUEFDSyBmcm9tIHJlYWwtd29ybGQgdXNlIGFjcm9zcyBhIGhvcGVmdWxseSBub3Qtc28t
Ymlhc2VkIHNhbXBsZSB2aWEgYnJvd3NlcnMgZGlyZWN0bHkuIElmIHRoZSB3b3JsZCBoYXMgY2hh
bmdlZCBzaW5jZSBIUEFDSyBjYW1lIG91dCBpbiB0ZXJtcyBvZiBoZWFkZXIgZnJlcSAoc2VlbXMg
cG9zc2libGUgaWYgbm90IHByb2JhYmxlKSwgdGhlbiBwZXJoYXBzIHdlIHNob3VsZCBjb25zaWRl
ciBhbiB1cGRhdGUgdG8gSFRUUDIvSFBBQ0sgYXMgd2VsbD8NCg0KDQoNCkkgYWdyZWUgdGhhdCBw
ZXJmZWN0aW9uIGhlcmUgaXNuJ3QgcmVhbGx5IG5lZWRlZCwgYnV0IEknbSBub3Qgc3VyZSBhZGRp
bmcgaXRlbXMgdG8gdGhlIHRhYmxlIGFyYml0cmFyaWx5IG1ha2VzIHNlbnNlIGVpdGhlci4NCg0K
DQoNCi09Ug0KDQoNCg0KT24gNS8yMy8xOCwgOTo0MiBQTSwgIlFVSUMgb24gYmVoYWxmIG9mIFdp
bGx5IFRhcnJlYXUiIDxxdWljLWJvdW5jZXNAaWV0Zi5vcmcgb24gYmVoYWxmIG9mIHdAMXd0LmV1
PG1haWx0bzpxdWljLWJvdW5jZXNAaWV0Zi5vcmclMjBvbiUyMGJlaGFsZiUyMG9mJTIwd0Axd3Qu
ZXU+PiB3cm90ZToNCg0KDQoNCiAgICBIaSBNaWtlLA0KDQoNCg0KICAgIE9uIFdlZCwgTWF5IDIz
LCAyMDE4IGF0IDExOjE2OjE4UE0gKzAwMDAsIE1pa2UgQmlzaG9wIHdyb3RlOg0KDQogICAgPiBS
YXRoZXIgdGhhbiBpbmRleGluZyB0aGUgdGFibGVzIHRvZ2V0aGVyIGFuZCBoYXZpbmcgdGhlIHN0
YXRpYyB0YWJsZSBhdCAxLTYxLA0KDQogICAgPiBRUEFDSyB1c2VzIGEgYml0IHRvIGluZGljYXRl
IHN0YXRpYyB2cy4gZHluYW1pYy4gIFNpbmNlIHRoZSBmaWVsZCBpcyBzZXZlbg0KDQogICAgPiBi
aXRzIGxvbmcsIHRoZSBwZXJmb3JtYW5jZSBpcyBjb21wYXJhYmxlIGZvciB0aGUgZHluYW1pYyB0
YWJsZSAoeW91IGNhbg0KDQogICAgPiBhY2Nlc3MgNjMgZW50cmllcyBpbiBvbmUgYnl0ZSwgMTkw
IGluIHR3byksIGJ1dCB5b3UgY2FuIGluY3JlYXNlIHRoZSBzaXplIG9mDQoNCiAgICA+IHRoZSBz
dGF0aWMgdGFibGUgd2l0aG91dCBodXJ0aW5nIHRoZSBkeW5hbWljIHRhYmxlLg0KDQoNCg0KICAg
IEl0IHdpbGwgbWFrZSB0aGUgY29kZSBsb29rIGxlc3MgIm1hZ2ljIiENCg0KDQoNCiAgICA+IEFz
IGEgcmVzdWx0LCB3ZSdyZQ0KDQogICAgPiBidWlsZGluZyBhIGZyZXNoIHN0YXRpYw0KDQogICAg
PiB0YWJsZTxodHRwczovL2dpdGh1Yi5jb20vcXVpY3dnL2Jhc2UtZHJhZnRzL3B1bGwvMTM1NT4g
YmFzZWQgb24gcXVlcmllcw0KDQogICAgPiBhZ2FpbnN0IEhUVFBBcmNoaXZlIGRhdGEuDQoNCiAg
ICA+DQoNCiAgICA+IFRoZSBrZXkgcXVlc3Rpb24gdGhhdCBoYXMgY29tZSB1cCBpbiBhIGNvdXBs
ZSB2ZW51ZXM6ICBXaGF0IHJlYWwtd29ybGQNCg0KICAgID4gaGVhZGVycyBkbyB3ZSB3YW50IHRv
IGFydGlmaWNpYWxseSByZW1vdmUgZnJvbSB3aGF0IHRoZSBkYXRhIHNob3dzLCBhbmQgd2hhdA0K
DQogICAgPiBoZWFkZXJzIG5vdCBzZWVuIGJ5IEhUVFAgQXJjaGl2ZSBkbyB3ZSB3YW50IHRvIGZv
cmNlIGluIGFueXdheT8NCg0KDQoNCiAgICBJIGFncmVlIHdpdGggTWFyayB0aGF0IHJlcXVlc3Qg
cmVhbGx5IGlzIHdoYXQgbWF0dGVycyB0aGUgbW9zdC4NCg0KDQoNCiAgICA+ICAgKiAgIFJlb3Jk
ZXJlZCB0byBwdXQgaGVhZGVycyB5b3UncmUgbGlrZWx5IHRvIG5hbWUtcmVmZXJlbmNlIGF0IHRo
ZSBmcm9udCwNCg0KICAgID4gICBlc3BlY2lhbGx5IGlmIHlvdSdyZSB1bmxpa2VseSB0byBhZGQg
dGhlbSB0byB0aGUgZHluYW1pYyB0YWJsZQ0KDQoNCg0KICAgIFdlbGwsIHNvbWUgb2YgdXMgaGF2
ZSBiZWVuIHJlYWxseSBib3RoZXJlZCBieSB0aGUgbGFjayBvZiBvcmRlcmluZw0KDQogICAgaW4g
dGhlIEhQQUNLIGhlYWRlcnMgdGFibGUsIG1ha2luZyBpdCBwYWluZnVsIHRvIHBlcmZvcm0gZWZm
aWNpZW50DQoNCiAgICBsb29rdXBzLiBJJ2Qgc3VnZ2VzdCB0aGF0IHRoZXkgYXJlIHNvcnRlZCBi
eSAobmFtZSx2YWx1ZSkgdG8gbWFrZQ0KDQogICAgaXQgcG9zc2libGUgdG8gcGVyZm9ybSBlZmZp
Y2llbnQgZGljaG90b21pYyBsb29rdXBzLg0KDQoNCg0KICAgID4gVGhlIHF1ZXN0aW9uIGlzIHdo
ZXRoZXIgd2Ugc2hvdWxkIGFsc28gYmFja2ZpbGwgaGVhZGVycyB3aGljaCBIVFRQIEFyY2hpdmUN
Cg0KICAgID4gd291bGRuJ3Qgc2VlLCBkZWxldGUgaGVhZGVycyB3ZSB3aXNoIHBlb3BsZSB3b3Vs
ZG4ndCB1c2UsIGFuZC9vciBpbnNlcnQgdGhlDQoNCiAgICA+IG9uZXMgd2UgaG9wZSB0aGV5IGV2
ZW50dWFsbHkgd2lsbC4gIFNvbWUgY2FuZGlkYXRlczoNCg0KDQoNCiAgICBUaGF0J3MgaW5kZWVk
IGEgZ29vZCBwb2ludC4NCg0KDQoNCiAgICA+ICAgKiAgIEFkZCBBbHQtU3ZjIGVudHJ5IGZvciBI
VFRQL1FVSUMgd2l0aCBRVUlDIHYxDQoNCiAgICA+ICAgKiAgIEFkZCBYLUZvcndhcmRlZC1Gb3IN
Cg0KICAgID4gICAqICAgRG9uJ3QgYWRkIFgtRm9yd2FyZGVkLUZvciwgYnV0IGRvIGFkZCBGb3J3
YXJkZWQNCg0KDQoNCiAgICBJbiBwcmFjdGljZSwgd2UgY2FuIHRha2UgYm90aCBvciBub25lLiBB
ZnRlciBhbGwsIG1vc3QgUVVJQyByZXF1ZXN0cyBnb2luZw0KDQogICAgdGhyb3VnaCBwcm94aWVz
IHdpbGwgYmUgZW5jcnlwdGVkIGFscmVhZHkgdGh1cyB0aGUgcHJveHkgd2lsbCBub3QgYmUgYWJs
ZQ0KDQogICAgdG8gYWRkIHRoZXNlIGZpZWxkcy4gRm9yIGNsZWFyLXRleHQgcmVxdWVzdHMsIHRo
ZSBoZWFkZXIgZmllbGQgbmFtZSBpcw0KDQogICAgcm91Z2hseSBhcyBsb25nIGFzIHRoZSB2YWx1
ZSwgc28gdGhlcmUncyBub3QgKnRoYXQqIG11Y2ggdG8gc2F2ZSBieSBlbmNvZGluZw0KDQogICAg
dGhlbS4gQW5kIGl0IHdpbGwgbm90IGNoYW5nZSBpbiBtb3N0IGNvbnNlY3V0aXZlIHJlcXVlc3Rz
LCBzbyB0aGUgZHluYW1pYw0KDQogICAgY29tcHJlc3Npb24gd2lsbCBiZSBtb3JlIGVmZmljaWVu
dCB0aGFuIHRoZSBzdGF0aWMgb25lLiBUaHVzIEkgc3VnZ2VzdCB0aGF0DQoNCiAgICB3ZSBvbmx5
IGFkZCB0aGVtICppZiogd2UgaGF2ZSBlbm91Z2ggdW51c2VkIHNsb3RzIGF0IHRoZSBlbmQgdGhh
dCB3ZSBjYXJlDQoNCiAgICB0byBjb3ZlciBhIHZlcnkgYnJvYWQgc2V0Lg0KDQoNCg0KICAgID4g
ICAqICAgUmVtb3ZlIEV4cGlyZXMgdG8gaW5jZW50IHRoZSB1c2Ugb2YgQ2FjaGUtQ29udHJvbA0K
DQoNCg0KICAgIEV4cGlyZXMgaXMgZm9yIHJlc3BvbnNlcyBvbmx5IGFueXdheSwgdGh1cyBpdCBt
YXR0ZXJzIG11Y2ggbGVzcy4gQ2FjaGUtY29udHJvbA0KDQogICAgY2FuIGJlIHVzZWQgaW4gYm90
aCBkaXJlY3Rpb25zLiBJIHRoaW5rIHRoYXQgdGhlIHRlY2huaWNhbCBmb2N1cyBvbiByZXF1ZXN0
DQoNCiAgICBtYXkgbWFrZSBFeHBpcmVzIGRpc2FwcGVhciBmcm9tIHRoZSB0YWJsZSA7LSkNCg0K
DQoNCiAgICA+ICAgKiAgIENvbGxhcHNlIHRoZSAiQ29udGVudC1UeXBlOiA8dGhpbmdleT4iIGFu
ZCAiQ29udGVudC1UeXBlOiA8dGhpbmdleT47IGNoYXJzZXQ9dXRmLTgiIGVudHJpZXMgdG9nZXRo
ZXINCg0KICAgID4gICAgICAqICAgLi4uYnV0IHdoaWNoIG9uZSB0byBrZWVwPw0KDQoNCg0KICAg
IFByb2JhYmx5IGp1c3QgZm9jdXMgb24gdGhlIG1vc3QgcmVwb3J0ZWQgb25lcyBhbmQgbm90IHRy
eSB0byBjb2xsYXBzZS4gSQ0KDQogICAgc3VzcGVjdCB0aGF0IHdlIHNlZSBhIGxvdCBvZiBlbi11
cyBhbG9uZSwgYW5kIHV0Zi04IGFkZGVkIHRvIHNvbWUgb3RoZXINCg0KICAgIGxhbmd1YWdlcywg
YnV0IEkgY291bGQgYmUgd3JvbmcuDQoNCg0KDQogICAgPiAgICogICBBZGQgQ29udGVudC1FbmNv
ZGluZyBhbmQvb3IgQWNjZXB0LUVuY29kaW5nIGVudHJpZXMgZm9yIHpzdGQNCg0KDQoNCiAgICBQ
cm9iYWJseSB0b28gZWFybHkgeWV0LCBhbmQgd2lsbCBub3QgbWFrZSBhIGJpZyBkaWZmZXJlbmNl
IG92ZXJhbGwgKGFsbW9zdA0KDQogICAgb25seSByZXNwb25zZSwgNCBjaGFyYWN0ZXJzIHZhbHVl
KS4NCg0KDQoNCiAgICA+IFRoZXJlJ3MgYW4gZW5kbGVzcyBwYXJhZGUgb2YgYmlrZXNoZWRzIGhl
cmUuICBBcyBNYXJ0aW4gaGFzIHBvaW50ZWQgb3V0LCB0aGlzDQoNCiAgICA+IHdpbGwgbmV2ZXIg
YmUgcGVyZmVjdCwgc28gdGhlIGdvYWwgaXMgImdvb2QgZW5vdWdoIGFuZCBrZWVwIGdvaW5nLiIg
IEFueQ0KDQogICAgPiBzdHJvbmcgZmVlbGluZ3MgYWJvdXQgYW55IG9mIHRoZXNlIGJlZm9yZSB3
ZSBtZXJnZSBpdD8NCg0KDQoNCiAgICBObyByZWFsIHN0cm9uZyBmZWVsaW5nIGhlcmUgZXhjZXB0
IGFib3V0IHRoZSBhYmlsaXR5IHRvIHBlcmZvcm0gZmFzdCBsb29rdXBzLg0KDQoNCg0KICAgID4g
QWxzbywgdGhlcmUncyBiZWVuIHNvbWUgZGlzY3Vzc2lvbiBvZiBhIG1lY2hhbmlzbSBmb3Igc2Vs
ZWN0aW5nIG9uZSBvZg0KDQogICAgPiBzZXZlcmFsIHN0YXRpYyB0YWJsZXMgYXQgdGhlIHN0YXJ0
IG9mIGEgY29ubmVjdGlvbi4gIEluIHRoYXQgY2FzZSwgdGhlIHNwZWMNCg0KICAgID4gd291bGQg
cHJvYmFibHkgZGVmaW5lIHRocmVlIHRhYmxlcyAoY2xpZW50IGhlYWRlcnMsIHNlcnZlciBoZWFk
ZXJzIFtmb3INCg0KICAgID4gc2VydmVycyB0aGF0IGRvbid0IHB1c2hdLCBjb21iaW5lZCBbZm9y
IHNlcnZlcnMgdGhhdCBwdXNoXSkgYW5kIGVuYWJsZSBmdXR1cmUNCg0KICAgID4gUkZDcyB0byBk
ZWZpbmUgb3RoZXJzIGZvciB0YXJnZXRlZCBzY2VuYXJpb3MgKHByb3hpZXMsIHZpZGVvIHBsYXli
YWNrLCBJb1QsDQoNCiAgICA+IGV0Yy4pLiAgSG93IG11Y2ggZG9lcyB0aGF0IGludGVyZXN0IGZv
bGtzPw0KDQoNCg0KICAgIEkgdGhpbmsgaXQgY291bGQgYmUgYSBnb29kIHNvbHV0aW9uLiBXZSBj
b3VsZCBhbHNvIHRoaW5rIGFib3V0IEFQSXMgYW5kDQoNCiAgICB2YXJpb3VzIGRhdGFjZW50ZXIt
b3JpZW50ZWQgdXNlIGNhc2VzIChlZzogd2Vic2VydmljZSBldGMpIHdoZXJlIHZlcnkgZmFzdA0K
DQogICAgcmVzcG9uc2UgYW5kIG5ldHdvcmsgZWZmaWNpZW5jeSBtYXR0ZXJzLiBJdCBjb3VsZCBi
ZSBhIHdheSB0byBlbmNvdXJhZ2UNCg0KICAgIFFVSUMgYWRvcHRpb24gaW5zaWRlIHRoZSBEQy4g
VGhlIHJpc2sgaG93ZXZlciBpcyB0aGF0IHRhYmxlcyBkZWZpbmVkIHRvbw0KDQogICAgbGF0ZSBh
cmUgbmV2ZXIgZGVwbG95ZWQgZHVlIHRvIGludGVyb3BlcmFiaWxpdHkgY29uY2VybnMgKHVubGVz
cyB0aGVyZSdzDQoNCiAgICBhIHdheSB0byBrbm93IHRoYXQgaXQgd2lsbCBiZSBzdXBwb3J0ZWQg
YmVmb3JlIGVuY29kaW5nKS4gVGh1cyBpZiBzb21lDQoNCiAgICBwYXJ0aWNpcGFudHMgYXJlIGlu
dGVyZXN0ZWQgaW4gb3B0aW1pemluZyBmb3IgY2VydGFpbiB1c2UgY2FzZXMsIHRoZXkgc2hvdWxk
DQoNCiAgICBwcm9iYWJseSBwcm92aWRlIHRoZWlyIG93biB0YWJsZXMgdG8gYmUgbWVyZ2VkIGlu
dG8gdGhlIHN0YW5kYXJkIGZyb20gZGF5IDEuDQoNCg0KDQogICAgQ2hlZXJzLA0KDQogICAgV2ls
bHkNCg0KDQoNCg0KDQoNCg==

--_000_B0995EA8A32949F38B470F6042D38DFCfbcom_
Content-Type: text/html; charset="utf-8"
Content-ID: <7CFCF6DAD50A9F46821B0A066591C923@namprd15.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseTpXaW5nZGluZ3M7DQoJcGFub3NlLTE6NSAwIDAgMCAwIDAgMCAwIDAg
MDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0x
OjIgNCA1IDMgNSA0IDYgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJp
Ow0KCXBhbm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25z
ICovDQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjow
aW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1m
YW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0K
CXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6IzA1NjNDMTsNCgl0ZXh0LWRlY29yYXRp
b246dW5kZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXtt
c28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Izk1NEY3MjsNCgl0ZXh0LWRlY29yYXRpb246
dW5kZXJsaW5lO30NCnAuTXNvUGxhaW5UZXh0LCBsaS5Nc29QbGFpblRleHQsIGRpdi5Nc29QbGFp
blRleHQNCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJQbGFpbiBU
ZXh0IENoYXIiOw0KCW1hcmdpbjowaW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQt
c2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KcC5tc29u
b3JtYWwwLCBsaS5tc29ub3JtYWwwLCBkaXYubXNvbm9ybWFsMA0KCXttc28tc3R5bGUtbmFtZTpt
c29ub3JtYWw7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBpbjsN
Cgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowaW47DQoJZm9udC1z
aXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpzcGFuLlBs
YWluVGV4dENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IlBsYWluIFRleHQgQ2hhciI7DQoJbXNvLXN0
eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOiJQbGFpbiBUZXh0IjsNCglmb250LWZh
bWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpzcGFuLkVtYWlsU3R5bGUyMA0KCXttc28tc3R5
bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJp
ZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBl
OmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJ
e3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpk
aXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi8qIExpc3QgRGVmaW5pdGlv
bnMgKi8NCkBsaXN0IGwwDQoJe21zby1saXN0LWlkOjE0MDQ0NTExMTY7DQoJbXNvLWxpc3QtdHlw
ZTpoeWJyaWQ7DQoJbXNvLWxpc3QtdGVtcGxhdGUtaWRzOjk1ODg0NDM3MiA2NzY5ODY4OSA2NzY5
ODY5MSA2NzY5ODY5MyA2NzY5ODY4OSA2NzY5ODY5MSA2NzY5ODY5MyA2NzY5ODY4OSA2NzY5ODY5
MSA2NzY5ODY5Mzt9DQpAbGlzdCBsMDpsZXZlbDENCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6
YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsN
Cgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0K
CWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDINCgl7bXNvLWxldmVsLW51bWJl
ci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9w
Om5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0u
MjVpbjsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCkBsaXN0IGwwOmxldmVsMw0KCXtt
c28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1z
by1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsN
Cgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGww
OmxldmVsNA0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRl
eHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9z
aXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6U3ltYm9sO30N
CkBsaXN0IGwwOmxldmVsNQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNv
LWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVt
YmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OiJD
b3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6bGV2ZWw2DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0
OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7
DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsN
Cglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw3DQoJe21zby1sZXZlbC1u
dW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRh
Yi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5k
ZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWw4DQoJe21z
by1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1s
ZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0
ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBs
MDpsZXZlbDkNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10
ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBv
c2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OldpbmdkaW5n
czt9DQpAbGlzdCBsMQ0KCXttc28tbGlzdC1pZDoxNjY1MzU1MDg2Ow0KCW1zby1saXN0LXRlbXBs
YXRlLWlkczotMjI2MjEwNDY0O30NCkBsaXN0IGwxOmxldmVsMQ0KCXttc28tbGV2ZWwtbnVtYmVy
LWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3Rv
cDouNWluOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDot
LjI1aW47DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpTeW1ib2w7
fQ0KQGxpc3QgbDE6bGV2ZWwyDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCglt
c28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjEuMGluOw0KCW1zby1sZXZl
bC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJbXNvLWFuc2kt
Zm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDE6bGV2ZWwz
DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7
DQoJbXNvLWxldmVsLXRhYi1zdG9wOjEuNWluOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246
bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsN
Cglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDE6bGV2ZWw0DQoJe21zby1sZXZlbC1udW1i
ZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1z
dG9wOjIuMGluOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVu
dDotLjI1aW47DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpTeW1i
b2w7fQ0KQGxpc3QgbDE6bGV2ZWw1DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsN
Cgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjIuNWluOw0KCW1zby1s
ZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJbXNvLWFu
c2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDE6bGV2
ZWw2DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrv
grc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjMuMGluOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRp
b246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBw
dDsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDE6bGV2ZWw3DQoJe21zby1sZXZlbC1u
dW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRh
Yi1zdG9wOjMuNWluOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWlu
ZGVudDotLjI1aW47DQoJbXNvLWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpT
eW1ib2w7fQ0KQGxpc3QgbDE6bGV2ZWw4DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxl
dDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjQuMGluOw0KCW1z
by1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJbXNv
LWFuc2ktZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDE6
bGV2ZWw5DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4
dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOjQuNWluOw0KCW1zby1sZXZlbC1udW1iZXItcG9z
aXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJbXNvLWFuc2ktZm9udC1zaXplOjEw
LjBwdDsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0Kb2wNCgl7bWFyZ2luLWJvdHRvbTowaW47fQ0K
dWwNCgl7bWFyZ2luLWJvdHRvbTowaW47fQ0KLS0+PC9zdHlsZT4NCjwvaGVhZD4NCjxib2R5IGxh
bmc9IkVOLVVTIiBsaW5rPSIjMDU2M0MxIiB2bGluaz0iIzk1NEY3MiI+DQo8ZGl2IGNsYXNzPSJX
b3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VG8gYmUgY2xlYXIsIEkgZG9u4oCZ
dCBiZWxpZXZlIHRoYXQgc29ydGluZyB0aGUgdGFibGUgaW4gUVBBQ0sgaXMgbmVjZXNzYXJ5IGZv
ciBDUFXigJRJIGFncmVlIGl0IHNob3VsZCBiZSBzb3J0ZWQgYnkgdGhpbmdzIHdoaWNoIGltcHJv
dmUgKG9yIGFyZSBuZXV0cmFsIHRvKSBvbi10aGUtd2lyZSBlZmZpY2llbmN5LjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Q1BVLXJlbGF0ZWQgY29zdHMgZm9yIGxvb2t1cHMg
Y2FuIGJlIGltcHJvdmVkIChhcyBEbWl0cmkgbm90ZXMpIGJ5IHN0cnVjdHVyaW5nIHRoZSBsb29r
dXBzIGRpZmZlcmVudGx5IGluIHRoZSBpbXBsZW1lbnRhdGlvbi48bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPkZvciBpbnN0YW5jZSwgdGhlcmUgYXJlIGZ1biB3YXlzIG9uZSBj
YW4gdXNlIFNTRSAoYW5kIHN1Y2Nlc3NvcnMpIHRvIHNlbGVjdCBhbW9uZ3N0IHRoZSBoZWFkZXJz
IGluIHRoZSBzdGF0aWMgdGFibGUgbW9yZSBxdWlja2x5IHRoYW4gb25lIG1pZ2h0IGFjaGlldmUg
d2l0aCBhIGhhc2gtbWFwLjxicj4NCi09UjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItdG9wOnNvbGlkICNCNUM0REYgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtjb2xv
cjpibGFjayI+RnJvbTogPC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtj
b2xvcjpibGFjayI+TWlrZSBCaXNob3AgJmx0O21iaXNob3BAZXZlcXVlZm91LmJlJmd0Ozxicj4N
CjxiPkRhdGU6IDwvYj5UaHVyc2RheSwgTWF5IDI0LCAyMDE4IGF0IDExOjIxIEFNPGJyPg0KPGI+
VG86IDwvYj5Sb2JlcnRvIFBlb24gJmx0O2Zlbml4QGZiLmNvbSZndDssIFdpbGx5IFRhcnJlYXUg
Jmx0O3dAMXd0LmV1Jmd0Ozxicj4NCjxiPkNjOiA8L2I+JnF1b3Q7cXVpY0BpZXRmLm9yZyZxdW90
OyAmbHQ7cXVpY0BpZXRmLm9yZyZndDssIEhUVFAgV29ya2luZyBHcm91cCAmbHQ7aWV0Zi1odHRw
LXdnQHczLm9yZyZndDs8YnI+DQo8Yj5TdWJqZWN0OiA8L2I+UkU6IFFQQUNLIGFuZCB0aGUgU3Rh
dGljIFRhYmxlPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPlllcywgSSB0aGluayB5b3UgbmVlZCB0aGUgbG9va3VwIHRhYmxlIGZvciBpbmRp
Y2VzLiZuYnNwOyBBbHBoYWJldGljYWwgZG9lc24ndCB3b3JrIGFzIHdlbGwsIGJlY2F1c2UgdGhl
cmUgYXJlIHR3byBrZXkgYmFycmllcnMgdG8gZGVhbCB3aXRoOjxvOnA+PC9vOnA+PC9wPg0KPHVs
IHN0eWxlPSJtYXJnaW4tdG9wOjBpbiIgdHlwZT0iZGlzYyI+DQo8bGkgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1zby1saXN0OmwwIGxldmVsMSBsZm8zIj5Pbmx5IHRoZSBmaXJzdCBzaXh0ZWVu
IGVudHJpZXMgY2FuIGJlIG5hbWUtcmVmZXJlbmNlZCBpbiBhIHNpbmdsZSBieXRlLiZuYnNwOyBX
ZSBkZWdyYWRlZCBwZXJmb3JtYW5jZSBpbiBhIHByZXZpb3VzIGRyYWZ0IG9mIHRoaXMgdGFibGUg
YmVjYXVzZSA6cGF0aCB3YXNu4oCZdCBpbiB0aGUgZmlyc3Qgc2l4dGVlbiBlbnRyaWVzLCBhbmQg
dGhlIGVuY29kZXIgdGhhdA0KIHRyaWVkIHRoZSB1cGRhdGVkIHRhYmxlIHVzZWQgdHdvLWJ5dGUg
bmFtZSByZWZlcmVuY2VzIGZvciBldmVyeSByZXF1ZXN0LjxvOnA+PC9vOnA+PC9saT48bGkgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1saXN0OmwwIGxldmVsMSBsZm8zIj5Pbmx5IHRoZSBm
aXJzdCBzaXh0eS1mb3VyIGVudHJpZXMgY2FuIGJlIGluZGV4LXJlZmVyZW5jZWQgaW4gYSBzaW5n
bGUgYnl0ZS48bzpwPjwvbzpwPjwvbGk+PC91bD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZu
YnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+VGhpcyBpbXBsaWVz
IHRoYXQgeW91IHdhbnQgYW4gb3JkZXJpbmcgYnkgbGlrZWxpaG9vZCBvZiB1c2luZyB0aGUgbmFt
ZSBhdCBhbGwsIGJ5IGxpa2VsaWhvb2Qgb2Ygbm90IGluZGV4aW5nIHRoZSB2YWx1ZSBmb3IgcmVw
ZWF0IHVzZSwgYW5kIGJ5IGxpa2VsaWhvb2Qgb2YgdXNpbmcgdGhlIG5hbWUmIzQzO3ZhbHVlIHBh
aXIgZGlyZWN0bHkuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJz
cDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPldoaWxlIGFuIGFscGhh
YmV0aWNhbGx5LXNvcnRlZCBsaXN0IGlzbuKAmXQgaW1wb3NzaWJsZSB3aXRoaW4gZWFjaCB0aWVy
LCBpdCBzZWVtcyBlYXNpZXIgdG8gbWFpbnRhaW4gYSBzdGF0aWMgbWFwIG9mIHRoZSBpbmRpY2Vz
IHRoYW4gdG8gYWxwaGFiZXRpY2FsbHkgaW5kZXggaW50byBlYWNoIHRpZXIgdG8gc2VlIGlmIHRo
ZSBoZWFkZXIgeW91IHdhbnQgaXMgcHJlc2VudC48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+SeKAmWQgYmUgb3BlbiB0byBhZGRpdGlvbmFsIHNvdXJjZXMgb2YgZGF0YSB0byBydW4gdGhl
IHNhbWUgcXVlcnkgYWdhaW5zdC4mbmJzcDsgQW55IGJyb3dzZXJzIHVwIHRvIHJ1bm5pbmcgYW4g
ZXhwZXJpbWVudCBhbmQgc2hhcmluZyB0aGUgdGVsZW1ldHJ5PzxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4NCkZyb206IFJvYmVydG8g
UGVvbiAmbHQ7ZmVuaXhAZmIuY29tJmd0OyA8YnI+DQpTZW50OiBUaHVyc2RheSwgTWF5IDI0LCAy
MDE4IDEwOjUzIEFNPGJyPg0KVG86IFdpbGx5IFRhcnJlYXUgJmx0O3dAMXd0LmV1Jmd0OzsgTWlr
ZSBCaXNob3AgJmx0O21iaXNob3BAZXZlcXVlZm91LmJlJmd0Ozxicj4NCkNjOiBxdWljQGlldGYu
b3JnOyBIVFRQIFdvcmtpbmcgR3JvdXAgJmx0O2lldGYtaHR0cC13Z0B3My5vcmcmZ3Q7PGJyPg0K
U3ViamVjdDogUmU6IFFQQUNLIGFuZCB0aGUgU3RhdGljIFRhYmxlPG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPk9uZSBjb3VsZCBtYWtlIHRoZSBsb29rdXAgKG1vcmUpIGVmZmljaWVudCBi
eSBzdG9yaW5nIHRoZSBpbmRleCAoYSBieXRlIGF0IG1vc3QpIHdpdGggdGhlIGtleS12YWx1ZSBw
YWlyLCB3aGVyZSB0aGUga2V5LXZhbHVlIHBhaXIgd2VyZSBzb3J0ZWQgdmlhIHdoYXRldmVyIHNv
cnRpbmcgeW91J2QgZmluZCBtb3N0IGVmZmljaWVudC48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPklmIHJlb3JkZXJpbmcgYWxsb3dzIGZvciBzb21lIGluY3JlYXNlZCBl
ZmZpY2llbmN5IHdpdGhvdXQgaW5jcmVhc2luZyBiaXRzLW9uLXdpcmUsIEknZCB0aGluayBpdCBz
ZWVtcyByZWFzb25hYmxlIHRvIGNoYW5nZS48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
SSB3b3VsZCBub3QgdHJ1c3QgdGhlIEhUVFAgQXJjaGl2ZSB0byBnaXZlIGEgZnJlcXVlbmN5IGFu
YWx5c2lzIGZvciByZWFsLXdvcmxkIHVzZS4gUmVtZW1iZXIgdGhhdCB3ZSBnYXRoZXJlZCB0aGUg
ZnJlcSBkYXRhIGZvciBIUEFDSyBmcm9tIHJlYWwtd29ybGQgdXNlIGFjcm9zcyBhIGhvcGVmdWxs
eSBub3Qtc28tYmlhc2VkIHNhbXBsZSB2aWEgYnJvd3NlcnMgZGlyZWN0bHkuIElmIHRoZSB3b3Js
ZCBoYXMNCiBjaGFuZ2VkIHNpbmNlIEhQQUNLIGNhbWUgb3V0IGluIHRlcm1zIG9mIGhlYWRlciBm
cmVxIChzZWVtcyBwb3NzaWJsZSBpZiBub3QgcHJvYmFibGUpLCB0aGVuIHBlcmhhcHMgd2Ugc2hv
dWxkIGNvbnNpZGVyIGFuIHVwZGF0ZSB0byBIVFRQMi9IUEFDSyBhcyB3ZWxsPzxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij5JIGFncmVlIHRoYXQgcGVyZmVjdGlvbiBoZXJlIGlzbid0IHJl
YWxseSBuZWVkZWQsIGJ1dCBJJ20gbm90IHN1cmUgYWRkaW5nIGl0ZW1zIHRvIHRoZSB0YWJsZSBh
cmJpdHJhcmlseSBtYWtlcyBzZW5zZSBlaXRoZXIuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRl
eHQiPi09UjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7PG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij5PbiA1LzIzLzE4LCA5OjQyIFBN
LCAmcXVvdDtRVUlDIG9uIGJlaGFsZiBvZiBXaWxseSBUYXJyZWF1JnF1b3Q7ICZsdDs8YSBocmVm
PSJtYWlsdG86cXVpYy1ib3VuY2VzQGlldGYub3JnJTIwb24lMjBiZWhhbGYlMjBvZiUyMHdAMXd0
LmV1Ij48c3BhbiBzdHlsZT0iY29sb3I6d2luZG93dGV4dDt0ZXh0LWRlY29yYXRpb246bm9uZSI+
cXVpYy1ib3VuY2VzQGlldGYub3JnIG9uIGJlaGFsZiBvZiB3QDF3dC5ldTwvc3Bhbj48L2E+Jmd0
Ow0KIHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJz
cDsgSGkgTWlrZSw8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNw
OyZuYnNwOyZuYnNwOyA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwO09uIFdlZCwgTWF5IDIzLCAyMDE4IGF0IDExOjE2OjE4UE0g
JiM0MzswMDAwLCBNaWtlIEJpc2hvcCB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IFJhdGhlciB0aGFuIGluZGV4aW5n
IHRoZSB0YWJsZXMgdG9nZXRoZXIgYW5kIGhhdmluZyB0aGUgc3RhdGljIHRhYmxlIGF0IDEtNjEs
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJz
cDsgJmd0OyBRUEFDSyB1c2VzIGEgYml0IHRvIGluZGljYXRlIHN0YXRpYyB2cy4gZHluYW1pYy4m
bmJzcDsgU2luY2UgdGhlIGZpZWxkIGlzIHNldmVuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyBiaXRzIGxvbmcsIHRoZSBwZXJm
b3JtYW5jZSBpcyBjb21wYXJhYmxlIGZvciB0aGUgZHluYW1pYyB0YWJsZSAoeW91IGNhbjxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZn
dDsgYWNjZXNzIDYzIGVudHJpZXMgaW4gb25lIGJ5dGUsIDE5MCBpbiB0d28pLCBidXQgeW91IGNh
biBpbmNyZWFzZSB0aGUgc2l6ZSBvZjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDsgdGhlIHN0YXRpYyB0YWJsZSB3aXRob3V0IGh1
cnRpbmcgdGhlIGR5bmFtaWMgdGFibGUuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtJdCB3aWxsIG1ha2UgdGhlIGNvZGUg
bG9vayBsZXNzICZxdW90O21hZ2ljJnF1b3Q7ITxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jmd0OyBBcyBhIHJlc3VsdCwg
d2UncmU8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNw
OyZuYnNwOyAmZ3Q7IGJ1aWxkaW5nIGEgZnJlc2ggc3RhdGljPG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyB0YWJsZSZsdDs8YSBo
cmVmPSJodHRwczovL2dpdGh1Yi5jb20vcXVpY3dnL2Jhc2UtZHJhZnRzL3B1bGwvMTM1NSI+PHNw
YW4gc3R5bGU9ImNvbG9yOndpbmRvd3RleHQ7dGV4dC1kZWNvcmF0aW9uOm5vbmUiPmh0dHBzOi8v
Z2l0aHViLmNvbS9xdWljd2cvYmFzZS1kcmFmdHMvcHVsbC8xMzU1PC9zcGFuPjwvYT4mZ3Q7IGJh
c2VkIG9uIHF1ZXJpZXM8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZu
YnNwOyZuYnNwOyAmbmJzcDsmZ3Q7IGFnYWluc3QgSFRUUEFyY2hpdmUgZGF0YS48bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IDxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jmd0OyBUaGUga2V5IHF1ZXN0aW9uIHRoYXQgaGFzIGNvbWUgdXAgaW4gYSBjb3VwbGUg
dmVudWVzOiZuYnNwOyBXaGF0IHJlYWwtd29ybGQ8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7IGhlYWRlcnMgZG8gd2Ugd2FudCB0
byBhcnRpZmljaWFsbHkgcmVtb3ZlIGZyb20gd2hhdCB0aGUgZGF0YSBzaG93cywgYW5kIHdoYXQ8
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNw
OyAmZ3Q7IGhlYWRlcnMgbm90IHNlZW4gYnkgSFRUUCBBcmNoaXZlIGRvIHdlIHdhbnQgdG8gZm9y
Y2UgaW4gYW55d2F5PzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5i
c3A7Jm5ic3A7Jm5ic3A7IDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7SSBhZ3JlZSB3aXRoIE1hcmsgdGhhdCByZXF1ZXN0IHJl
YWxseSBpcyB3aGF0IG1hdHRlcnMgdGhlIG1vc3QuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgPG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmZ3Q7Jm5ic3A7Jm5ic3A7
ICombmJzcDsmbmJzcDsgUmVvcmRlcmVkIHRvIHB1dCBoZWFkZXJzIHlvdSdyZSBsaWtlbHkgdG8g
bmFtZS1yZWZlcmVuY2UgYXQgdGhlIGZyb250LDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDsmbmJzcDsmbmJzcDsgZXNwZWNpYWxs
eSBpZiB5b3UncmUgdW5saWtlbHkgdG8gYWRkIHRoZW0gdG8gdGhlIGR5bmFtaWMgdGFibGU8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyA8
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwO1dlbGwsIHNvbWUgb2YgdXMgaGF2ZSBiZWVuIHJlYWxseSBib3RoZXJlZCBieSB0aGUg
bGFjayBvZiBvcmRlcmluZzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
Jm5ic3A7Jm5ic3A7Jm5ic3A7IGluIHRoZSBIUEFDSyBoZWFkZXJzIHRhYmxlLCBtYWtpbmcgaXQg
cGFpbmZ1bCB0byBwZXJmb3JtIGVmZmljaWVudDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IGxvb2t1cHMuIEknZCBzdWdnZXN0IHRoYXQg
dGhleSBhcmUgc29ydGVkIGJ5IChuYW1lLHZhbHVlKSB0byBtYWtlPG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgaXQgcG9zc2libGUgdG8g
cGVyZm9ybSBlZmZpY2llbnQgZGljaG90b21pYyBsb29rdXBzLjxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jmd0OyBUaGUg
cXVlc3Rpb24gaXMgd2hldGhlciB3ZSBzaG91bGQgYWxzbyBiYWNrZmlsbCBoZWFkZXJzIHdoaWNo
IEhUVFAgQXJjaGl2ZTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5i
c3A7Jm5ic3A7Jm5ic3A7ICZndDsgd291bGRuJ3Qgc2VlLCBkZWxldGUgaGVhZGVycyB3ZSB3aXNo
IHBlb3BsZSB3b3VsZG4ndCB1c2UsIGFuZC9vciBpbnNlcnQgdGhlPG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyBvbmVzIHdlIGhv
cGUgdGhleSBldmVudHVhbGx5IHdpbGwuJm5ic3A7IFNvbWUgY2FuZGlkYXRlczo8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyA8bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
O1RoYXQncyBpbmRlZWQgYSBnb29kIHBvaW50LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jmd0OyZuYnNwOyZuYnNwOyAq
Jm5ic3A7Jm5ic3A7IEFkZCBBbHQtU3ZjIGVudHJ5IGZvciBIVFRQL1FVSUMgd2l0aCBRVUlDIHYx
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJz
cDsgJmd0OyZuYnNwOyZuYnNwOyAqJm5ic3A7Jm5ic3A7IEFkZCBYLUZvcndhcmRlZC1Gb3I8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyAm
Z3Q7Jm5ic3A7Jm5ic3A7ICombmJzcDsmbmJzcDsgRG9uJ3QgYWRkIFgtRm9yd2FyZGVkLUZvciwg
YnV0IGRvIGFkZCBGb3J3YXJkZWQ8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRl
eHQiPiZuYnNwOyZuYnNwOyZuYnNwOyA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO0luIHByYWN0aWNlLCB3ZSBjYW4gdGFrZSBi
b3RoIG9yIG5vbmUuIEFmdGVyIGFsbCwgbW9zdCBRVUlDIHJlcXVlc3RzIGdvaW5nPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgdGhyb3Vn
aCBwcm94aWVzIHdpbGwgYmUgZW5jcnlwdGVkIGFscmVhZHkgdGh1cyB0aGUgcHJveHkgd2lsbCBu
b3QgYmUgYWJsZTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7
Jm5ic3A7Jm5ic3A7IHRvIGFkZCB0aGVzZSBmaWVsZHMuIEZvciBjbGVhci10ZXh0IHJlcXVlc3Rz
LCB0aGUgaGVhZGVyIGZpZWxkIG5hbWUgaXM8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyByb3VnaGx5IGFzIGxvbmcgYXMgdGhlIHZhbHVl
LCBzbyB0aGVyZSdzIG5vdCAqdGhhdCogbXVjaCB0byBzYXZlIGJ5IGVuY29kaW5nPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgdGhlbS4g
QW5kIGl0IHdpbGwgbm90IGNoYW5nZSBpbiBtb3N0IGNvbnNlY3V0aXZlIHJlcXVlc3RzLCBzbyB0
aGUgZHluYW1pYzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7
Jm5ic3A7Jm5ic3A7IGNvbXByZXNzaW9uIHdpbGwgYmUgbW9yZSBlZmZpY2llbnQgdGhhbiB0aGUg
c3RhdGljIG9uZS4gVGh1cyBJIHN1Z2dlc3QgdGhhdDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IHdlIG9ubHkgYWRkIHRoZW0gKmlmKiB3
ZSBoYXZlIGVub3VnaCB1bnVzZWQgc2xvdHMgYXQgdGhlIGVuZCB0aGF0IHdlIGNhcmU8bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyB0byBj
b3ZlciBhIHZlcnkgYnJvYWQgc2V0LjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jmd0OyZuYnNwOyZuYnNwOyAqJm5ic3A7
Jm5ic3A7IFJlbW92ZSBFeHBpcmVzIHRvIGluY2VudCB0aGUgdXNlIG9mIENhY2hlLUNvbnRyb2w8
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNw
OyA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwO0V4cGlyZXMgaXMgZm9yIHJlc3BvbnNlcyBvbmx5IGFueXdheSwgdGh1cyBpdCBt
YXR0ZXJzIG11Y2ggbGVzcy4gQ2FjaGUtY29udHJvbDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IGNhbiBiZSB1c2VkIGluIGJvdGggZGly
ZWN0aW9ucy4gSSB0aGluayB0aGF0IHRoZSB0ZWNobmljYWwgZm9jdXMgb24gcmVxdWVzdDxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IG1h
eSBtYWtlIEV4cGlyZXMgZGlzYXBwZWFyIGZyb20gdGhlIHRhYmxlIDstKTxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jmd0
OyZuYnNwOyZuYnNwOyAqJm5ic3A7Jm5ic3A7IENvbGxhcHNlIHRoZSAmcXVvdDtDb250ZW50LVR5
cGU6ICZsdDt0aGluZ2V5Jmd0OyZxdW90OyBhbmQgJnF1b3Q7Q29udGVudC1UeXBlOiAmbHQ7dGhp
bmdleSZndDs7IGNoYXJzZXQ9dXRmLTgmcXVvdDsgZW50cmllcyB0b2dldGhlcjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgKiZuYnNwOyZuYnNwOyAuLi5idXQgd2hpY2ggb25l
IHRvIGtlZXA/PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsm
bmJzcDsmbmJzcDsgPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDtQcm9iYWJseSBqdXN0IGZvY3VzIG9uIHRoZSBtb3N0IHJlcG9y
dGVkIG9uZXMgYW5kIG5vdCB0cnkgdG8gY29sbGFwc2UuIEk8bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyBzdXNwZWN0IHRoYXQgd2Ugc2Vl
IGEgbG90IG9mIGVuLXVzIGFsb25lLCBhbmQgdXRmLTggYWRkZWQgdG8gc29tZSBvdGhlcjxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IGxh
bmd1YWdlcywgYnV0IEkgY291bGQgYmUgd3JvbmcuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgPG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmZ3Q7Jm5ic3A7Jm5ic3A7
ICombmJzcDsmbmJzcDsgQWRkIENvbnRlbnQtRW5jb2RpbmcgYW5kL29yIEFjY2VwdC1FbmNvZGlu
ZyBlbnRyaWVzIGZvciB6c3RkPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij4mbmJzcDsmbmJzcDsmbmJzcDsgPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDtQcm9iYWJseSB0b28gZWFybHkgeWV0LCBhbmQg
d2lsbCBub3QgbWFrZSBhIGJpZyBkaWZmZXJlbmNlIG92ZXJhbGwgKGFsbW9zdDxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IG9ubHkgcmVz
cG9uc2UsIDQgY2hhcmFjdGVycyB2YWx1ZSkuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmZ3Q7IFRoZXJlJ3MgYW4gZW5k
bGVzcyBwYXJhZGUgb2YgYmlrZXNoZWRzIGhlcmUuJm5ic3A7IEFzIE1hcnRpbiBoYXMgcG9pbnRl
ZCBvdXQsIHRoaXM8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNw
OyZuYnNwOyZuYnNwOyAmZ3Q7IHdpbGwgbmV2ZXIgYmUgcGVyZmVjdCwgc28gdGhlIGdvYWwgaXMg
JnF1b3Q7Z29vZCBlbm91Z2ggYW5kIGtlZXAgZ29pbmcuJnF1b3Q7Jm5ic3A7IEFueTxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDsg
c3Ryb25nIGZlZWxpbmdzIGFib3V0IGFueSBvZiB0aGVzZSBiZWZvcmUgd2UgbWVyZ2UgaXQ/PG86
cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsg
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDtObyByZWFsIHN0cm9uZyBmZWVsaW5nIGhlcmUgZXhjZXB0IGFib3V0IHRoZSBhYmls
aXR5IHRvIHBlcmZvcm0gZmFzdCBsb29rdXBzLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7IDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jmd0OyBBbHNvLCB0aGVyZSdz
IGJlZW4gc29tZSBkaXNjdXNzaW9uIG9mIGEgbWVjaGFuaXNtIGZvciBzZWxlY3Rpbmcgb25lIG9m
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJz
cDsgJmd0OyBzZXZlcmFsIHN0YXRpYyB0YWJsZXMgYXQgdGhlIHN0YXJ0IG9mIGEgY29ubmVjdGlv
bi4mbmJzcDsgSW4gdGhhdCBjYXNlLCB0aGUgc3BlYzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7Jm5ic3A7ICZndDsgd291bGQgcHJvYmFibHkgZGVm
aW5lIHRocmVlIHRhYmxlcyAoY2xpZW50IGhlYWRlcnMsIHNlcnZlciBoZWFkZXJzIFtmb3I8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyAm
Z3Q7IHNlcnZlcnMgdGhhdCBkb24ndCBwdXNoXSwgY29tYmluZWQgW2ZvciBzZXJ2ZXJzIHRoYXQg
cHVzaF0pIGFuZCBlbmFibGUgZnV0dXJlPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxh
aW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgJmd0OyBSRkNzIHRvIGRlZmluZSBvdGhlcnMgZm9y
IHRhcmdldGVkIHNjZW5hcmlvcyAocHJveGllcywgdmlkZW8gcGxheWJhY2ssIElvVCw8bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyAmZ3Q7
IGV0Yy4pLiZuYnNwOyBIb3cgbXVjaCBkb2VzIHRoYXQgaW50ZXJlc3QgZm9sa3M/PG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgPG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDtJIHRoaW5rIGl0IGNvdWxkIGJlIGEgZ29vZCBzb2x1dGlvbi4gV2UgY291bGQgYWxzbyB0aGlu
ayBhYm91dCBBUElzIGFuZDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
Jm5ic3A7Jm5ic3A7Jm5ic3A7IHZhcmlvdXMgZGF0YWNlbnRlci1vcmllbnRlZCB1c2UgY2FzZXMg
KGVnOiB3ZWJzZXJ2aWNlIGV0Yykgd2hlcmUgdmVyeSBmYXN0PG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgcmVzcG9uc2UgYW5kIG5ldHdv
cmsgZWZmaWNpZW5jeSBtYXR0ZXJzLiBJdCBjb3VsZCBiZSBhIHdheSB0byBlbmNvdXJhZ2U8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyBR
VUlDIGFkb3B0aW9uIGluc2lkZSB0aGUgREMuIFRoZSByaXNrIGhvd2V2ZXIgaXMgdGhhdCB0YWJs
ZXMgZGVmaW5lZCB0b288bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZu
YnNwOyZuYnNwOyZuYnNwOyBsYXRlIGFyZSBuZXZlciBkZXBsb3llZCBkdWUgdG8gaW50ZXJvcGVy
YWJpbGl0eSBjb25jZXJucyAodW5sZXNzIHRoZXJlJ3M8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyBhIHdheSB0byBrbm93IHRoYXQgaXQg
d2lsbCBiZSBzdXBwb3J0ZWQgYmVmb3JlIGVuY29kaW5nKS4gVGh1cyBpZiBzb21lPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4mbmJzcDsmbmJzcDsmbmJzcDsgcGFydGlj
aXBhbnRzIGFyZSBpbnRlcmVzdGVkIGluIG9wdGltaXppbmcgZm9yIGNlcnRhaW4gdXNlIGNhc2Vz
LCB0aGV5IHNob3VsZDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5i
c3A7Jm5ic3A7Jm5ic3A7IHByb2JhYmx5IHByb3ZpZGUgdGhlaXIgb3duIHRhYmxlcyB0byBiZSBt
ZXJnZWQgaW50byB0aGUgc3RhbmRhcmQgZnJvbSBkYXkgMS48bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyA8bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwO0NoZWVycyw8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPiZuYnNwOyZuYnNwOyZuYnNwOyBX
aWxseTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5ic3A7
Jm5ic3A7IDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+Jm5ic3A7Jm5i
c3A7Jm5ic3A7Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij4m
bmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_B0995EA8A32949F38B470F6042D38DFCfbcom_--


From nobody Thu May 24 21:06:28 2018
Return-Path: <martin.thomson@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id F230312D885 for <quic@ietfa.amsl.com>; Thu, 24 May 2018 21:06:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 q-oxRbFE2Sm1 for <quic@ietfa.amsl.com>; Thu, 24 May 2018 21:06:24 -0700 (PDT)
Received: from mail-ot0-x233.google.com (mail-ot0-x233.google.com [IPv6:2607:f8b0:4003:c0f::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F0A4F1273E2 for <quic@ietf.org>; Thu, 24 May 2018 21:06:23 -0700 (PDT)
Received: by mail-ot0-x233.google.com with SMTP id g7-v6so4564291otj.11 for <quic@ietf.org>; Thu, 24 May 2018 21:06:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=Df1l/pzwfmcWftzsCtNVlBIOJ//oNqK52k7UxLrLhyw=; b=mKFs3QAhqpLYaBXPuOJdIcWKo44ct70dZRLE6n2Sx4guGOjuM4y/6/XwLN2bBDCRAc Nr0DckmZf/qK2e317DasAHNnc/8RjhbDDM4dhqdLXwIshDZ6A9HfP+U8GBvcR1z47pRZ TXg2c8mbZmF1Ka1ZOJz3j0cF7sk2EIN37eLYyxMarvnG2FZCcjnaSkMeMHQvM4fJAKhK /w5Ra/GbtKRWpo+QlXOTS32VKNItYi32JOvSk17EZnCwpTH+MsfbHLXEXA22Jbj5x7/I mYf8qOSAr+eHZjGyU+fEhwWW/DPpHUGi6UOEuLuYs5Y2mgIhzBwyH1gx2OEhS/G3cc1B TP5g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=Df1l/pzwfmcWftzsCtNVlBIOJ//oNqK52k7UxLrLhyw=; b=DIv7neFBThpf7eNpid3BUyKORfMOaYxelNZYRq6m3Gxl6pzKJeKsc9eMpVW7Q7sJ5z k8P8Lp+VXVrgjKzzOiFCmIngHa4ipF6BB4OoJ7um/X0qLsJwszUpsxahtGIxW6uyljPR PdaZxkTuDA6bLjR3nB2+vIuuQZUiASBgtn6hHuDTlo45dUBNQs8mNVJ6B2T12BTT/iA4 X0Lnj2EIKtbxTmJJ7VBoCOzVNVU7TDql5+Gv5oX9Bz3kGaup+iaPPsMs9O7VI8SotVZ+ smB48GY348cDl2inlupZuozbhVStcbMBMnU5rXflFnNE7en8XPD5qM2Qphtmz78l8NTd RyoA==
X-Gm-Message-State: ALKqPwfxBChUF8fAVD9KhnNiaAfBiDevXGDNnahYyKzDxOjA3qJE/aIi FbQuUaPCSlt5MsyPYlMtTG343dSfp8gZy50GsfQ=
X-Google-Smtp-Source: AB8JxZoPqp+aMjzfQbtrbwTRoEH5UmsHuQtAZ6zv1PsbjkRdpSXx+T3fhOdz4wpE2WgWopcb79C66bSqV0zbHXV0PHI=
X-Received: by 2002:a9d:524d:: with SMTP id q13-v6mr533086otg.241.1527221183287;  Thu, 24 May 2018 21:06:23 -0700 (PDT)
MIME-Version: 1.0
References: <CAOYVs2q63DpkPZTbw9T24ZcFOxbvrWAGvOtUaHvCuSg_13pSkQ@mail.gmail.com>
In-Reply-To: <CAOYVs2q63DpkPZTbw9T24ZcFOxbvrWAGvOtUaHvCuSg_13pSkQ@mail.gmail.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Fri, 25 May 2018 14:06:10 +1000
Message-ID: <CABkgnnUAiztUw-kEr97bCX499eQL8wno11rRJQJD+49eBn6LXA@mail.gmail.com>
Subject: Re: Payload length 0
To: Marten Seemann <martenseemann@gmail.com>
Cc: QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/X_ab8VHhgkAxDPWyNhSWRaJmxEs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 May 2018 04:06:26 -0000

It seems like the discussion has settled down.

For those advocating for 0 being special, are you happy to keep things as
they are?
On Fri, May 18, 2018 at 3:08 PM Marten Seemann <martenseemann@gmail.com>
wrote:

> Jana asked me to raise this issue on the list, after we already had a bit
of discussion in https://github.com/quicwg/base-drafts/pull/1301.

> The proposal is to make a payload length of 0 a special value, indicating
that the packet is not a coalesced packet, i.e. that the whole payload of
the UDP packet is the QUIC packet. This would eliminate an invalid value of
the payload length (there are no empty packets), save one byte for packet
lengths where varint encoding would result in a two byte number, and
apparently also simplify (some) implementations.

> Kazuho argued creating two versions of each Long Header type (one with
and one without a payload length) is the better solution, since all values
below the AEAD tag length + 1 are invalid values anyway, and it would save
one more byte.

> We should make a decision if and what we want to do about this.


From nobody Fri May 25 01:06:29 2018
Return-Path: <kazuhooku@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D34EE1243FE for <quic@ietfa.amsl.com>; Fri, 25 May 2018 01:06:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 1v_kmufKYtoV for <quic@ietfa.amsl.com>; Fri, 25 May 2018 01:06:24 -0700 (PDT)
Received: from mail-pl0-x22b.google.com (mail-pl0-x22b.google.com [IPv6:2607:f8b0:400e:c01::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD4BB1201FA for <quic@ietf.org>; Fri, 25 May 2018 01:06:24 -0700 (PDT)
Received: by mail-pl0-x22b.google.com with SMTP id f1-v6so2247165plt.6 for <quic@ietf.org>; Fri, 25 May 2018 01:06:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=959mrzNQKutR5mTu8Cg9qPeBMNREemoDauXuaoxApl0=; b=CtXDUN5apxwLMBfpmjepHXC9dw57AssEe6D36GO7EOWhKK41q21VJf6j6B8vjRHTWA u89UPIOJsHvnDEXU2Xqz80XiGUkiMP2MZ0Q1vV5fZeIx84cihw96Fi5tTy+v8G+eVp8h B9TngoGhxwb4ew6WiVgDPa7FvzVHTyBZZjDIoD5dBezk74huM6mUcVVonci49brga7WB RrB53rLKK9qsk19gol7cFOD6g4IqnrylHfd/3CiHajN99kFRQ8P2CQWQfPwkJmepbje2 OEjZiipRYg0Y8a6CGQYEeGJvuOCfcAm9B0kCpXljfwZk9KoHXxhxICyNaSyWTF136VWx KOMw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=959mrzNQKutR5mTu8Cg9qPeBMNREemoDauXuaoxApl0=; b=X48DU+JoRdwdrXChg4WK3VZ2PBUv2QalxhJCDrlEI2SiYuiKVdofHpFRFjg4A0Q8Ah beYWz1oOW4NgeETETUxhsWX5ZqfLX1NlPqv55s7nTuHG5MkuRBtYOBQqUQqm/7gqc6Ge VeOo+ZG9wLU2Fam4RUAwLoKT9KMGdHcadtXryHbw9w4NLk2uLeu1SroD4m+q17tTNnQj lBYHiuxIYEe/aSIP14yVmcqaDoGW34EyKPeuOEbQuzDpvMtoJksHgvcIYO+Jb7PL9C6Q yUTXNR2GX79Tpkqp6CN8wRTshL0wZ0aluwCpLfqWyRDMjb6weBe15m6S4p48UU282rgW wQPg==
X-Gm-Message-State: ALKqPwdBgMcNcZHLpM31IjElQRg3bysrhugCSgid9LZoUzsAG0GN/5uQ VcNWBkldvPZlnHkUxaSfFPhD1QeG8CayZ+OkA0A=
X-Google-Smtp-Source: AB8JxZonnfjt2nS0NosbicC08MAiGZ169fM0pHHTvepSenQ5V2N6TJXShS8WWnnHJjeQdV11hrsS76B5ECUDGVCGBIM=
X-Received: by 2002:a17:902:b7ca:: with SMTP id v10-v6mr1519677plz.224.1527235584119;  Fri, 25 May 2018 01:06:24 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:1189:0:0:0:0 with HTTP; Fri, 25 May 2018 01:06:23 -0700 (PDT)
In-Reply-To: <CANatvzyNHpTFpdS6_A-gijn2+dOiU=zxyiRJsQuSZVy+EyZ1gQ@mail.gmail.com>
References: <CANatvzwN1kVO3ofvyYX9cg=cKcg4FdqUT3VB6hneEDa5UjT_0w@mail.gmail.com> <CABkgnnUjw4WYDv5mmsFp2nDq4LtdJBzsgdFkxFzEdHrA37tejw@mail.gmail.com> <CANatvzyNHpTFpdS6_A-gijn2+dOiU=zxyiRJsQuSZVy+EyZ1gQ@mail.gmail.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Fri, 25 May 2018 17:06:23 +0900
Message-ID: <CANatvzwXhqZBDt59HJCThbdhomGbac=Na0vcofZhPbEYRniV-g@mail.gmail.com>
Subject: Re: Stream0 Proposal: Explicit vs. Implicit ACK (Re: Stream0 Design Team Proposal)
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Jana Iyengar <jri.ietf@gmail.com>, Eric Rescorla <ekr@mozilla.com>, QUIC WG <quic@ietf.org>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/I_xH457cYGkGWq6MnYnsl1ZBfng>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 May 2018 08:06:27 -0000

I think I might have found an issue in the explicit ACK approach that
we use in the PR.

That is that EOED cannot be ACKed.

Assuming that EOED is sent using 0-RTT keys, it needs to be acked by
the server using the same key, because the transmission of EOED needs
to be guaranteed for the TLS handshake to complete.

However, there is no 0-RTT send key on the server-side.

Do we have any rule for dealing with this? I searched though the text
of the PR but could not find an answer.


2018-05-24 14:49 GMT+09:00 Kazuho Oku <kazuhooku@gmail.com>:
> 2018-05-24 13:43 GMT+09:00 Martin Thomson <martin.thomson@gmail.com>:
>> The obvious solution for the problem of not retransmitting the client
>> Finished is to retransmit it until it is acknowledged.  With the proposed
>> design, that means that the server sends a Handshake message after the
>> handshake is done, which I think is fine.  If the client sends Finished
>> until it is acknowledged, then I think we're good.
>
> I agree that that would work.
>
> IIUC downsides compared to the implicit ACK approach are that the
> server needs to keep the old keys for certain amount of time (e.g., 2
> MSL) and that the additional Handshake packet will consume about 30
> octets of the 3 packet window that we have for the server's first
> flights.
>
>> I can see the appeal in saying that if you receive an ACK for 1-RTT data
>> then your Handshake packets must have been received.  I can see that
>> working even, but you have to be careful.  It's just a signal that you can
>> stop sending CRYPTO frames, not that you are done with the keys.  You might
>> need to send ACK again and you might still receive packets at that level.
>> You could drop read keys and ACK only the old packets that you did decrypt,
>> but I suspect that it's better to authenticate any packet and ACK
>> faithfully, which would be better for your peer's congestion state.
>>
>> That also means that you probably need to have timers for cleaning up, to
>> avoid the pathological case where acknowledgments are sent indefinitely.
>
> I agree with your argument about congestion control.
>
> One way of acquiring correct congestion control information in the
> implicit ACK approach will be to send coalesced packets that combines
> a Handshake packet with a packet protected by a higher encryption key.
> That will guarantee that you would receive an ACK for the delivery of
> the datagrams, and you can feed the information to the congestion
> controller.
>
> FWIW, I have implemented implicit ACK in quicly, and it only required
> about 40 additional lines of code, including the retransmission logic
> for Handshake_Done. The code can be found at
> https://github.com/h2o/quicly/pull/8/commits/eee6eb5fc7c0359edfeb0b8f89ae9ac191ef0758.
> Coalesced packets is not implemented.
>
>>
>> I think that the FIN bit idea might work to close out the use of the
>> "stream" for each set of keys. That is, as opposed to the crypto stream as
>> a whole.  But it's duplicative: the crypto handshake needs to know when it
>> moves from one set of keys to the next and replicating that signaling at
>> the QUIC layer only really adds things to check for consistency.
>> On Thu, May 24, 2018 at 11:07 AM Kazuho Oku <kazuhooku@gmail.com> wrote:
>>
>>> 2018-05-24 3:46 GMT+09:00 Jana Iyengar <jri.ietf@gmail.com>:
>>
>>> > A thought occurs to me: a CRYPTO_HS frame with the fin bit set can be
>> used
>>> > to indicate that the handshake is done.This could be used as a signal
>> (aka
>>> > HANDSHAKE_DONE) to solve Marten's problem of a client rtxing a CFIN. Of
>>> > course, this would mean that this particular CRYPTO_HS frame would be
>>> > encrypted with a 1-RTT key... which *I think* is fine. What do you
>> think?
>>
>>> I am not sure if that is a good approach.
>>
>>> I would assume that we would like to keep the handshake flow on the
>>> 1-RTT key open for the lifetime of the QUIC connection, so that we
>>> could send things related to the TLS (e.g. session tickets). Sending
>>> FIN from the server right after receiving ClientFinished makes that
>>> impossible.
>>
>>> Having said that, I do agree that the need for a dedicated frame is a
>>> pain. It is a pain because we need to have a retransmission logic for
>>> the frame.
>>
>>> I think that you are making a good point in suggesting to consider
>>> reusing the retransmission logic that already exists for bidirectional
>>> flows. But as said, FIN bit does not seem like an answer in this case.
>>
>>> IMO, ideally we should define a new TLS post-handshake message (that
>>> does not convey any data), and send that from the server in response
>>> to ClientFinished using 1-RTT packet. The message will act as a signal
>>> that the server has received ClientFinished.
>>
>>> The benefit of this approach is that we can reuse the retransmission
>>> logic that will exist for handshake flows. The downside is that TLS
>>> stacks need to be aware of the new handshake message.
>>
>>> Considering the fact that the Design Team is already suggesting a
>>> substantial change to the TLS stack, we might have chance in asking
>>> for the addition of a new handshake message. But I am not sure.
>>
>>> --
>>> Kazuho Oku
>
>
>
> --
> Kazuho Oku



-- 
Kazuho Oku


From nobody Fri May 25 01:33:50 2018
Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DFB251243F6 for <quic@ietfa.amsl.com>; Fri, 25 May 2018 01:33:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.688
X-Spam-Level: 
X-Spam-Status: No, score=-1.688 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, UNPARSEABLE_RELAY=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 2E-6mwEz8vwe for <quic@ietfa.amsl.com>; Fri, 25 May 2018 01:33:45 -0700 (PDT)
Received: from mail-io0-x233.google.com (mail-io0-x233.google.com [IPv6:2607:f8b0:4001:c06::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DAA51201FA for <quic@ietf.org>; Fri, 25 May 2018 01:33:45 -0700 (PDT)
Received: by mail-io0-x233.google.com with SMTP id g14-v6so5516335ioc.7 for <quic@ietf.org>; Fri, 25 May 2018 01:33:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to :cc; bh=MVe37+whc+WlRxd7PydWpbOuHs1MxHv9t0lEMi+RSzQ=; b=ASIOzExAX5kTp00cHwl8Dkycv/ZUOVFXBMK4z7KJs7rKTrAJf3TipSLEzNRbJUqD8a 5fI5QTruO0ibbtz2gTnjhLcTdPTa7y5aw9ghgM0g9tA6fjamTHmCD1pXtKBeYqnDOypT h5CgDgjzYVkqw0mDe5XQg0/bmv4XFtuEmtnl8u1ROSBOryijeCZ6jfwda0UVpnHAvmiQ 1R6vSV8oEoYsgm3SYzlW/KoE75MyC8//SlnrUdXk1RLfh5LF8IGwWBClnsm6EAsz6aIj EbW0Zs5LxtcMrd66nTxr7oFU9D/g1yrXeVQtHHWQvM5BM5UrO9U2dgP0a1BM4IGk8Qql ELhg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to:cc; bh=MVe37+whc+WlRxd7PydWpbOuHs1MxHv9t0lEMi+RSzQ=; b=GIUijcyVpxOoBSOoR3XV6+sERlj8IqB297JlHXDsUrIxHBPLGXuEoKTMGcTDpBQEHD 7d2OsSPxfkxf6V+LlgWUcGZR/8ZzcVUzvdA2GABaAJCk3T2FKDnH47e6Yf5wmhK+nFsn 1d8GXpSe1gek8kT2sEp2lo2pNfVOKVzNr21eO6VOzEwzf6OKSkgGbSdIGNfFs0aLZqzE ES1jnOIhy13w5baYEeHN19o67+tuatKdZwngCjU45zCiu3byLNGp6DTp8SvBB8+Pn7Ul e8g8wm6/YYCzXbEdzE3T/A0DwiVE8CpuwYK1Mba8pQaC9zFcD6BaP36owHog1AUmuadm fg5Q==
X-Gm-Message-State: ALKqPwdpEo7RSUN4CehkXGhjf+GgsEvStwuJZ+fUUxEpgkzeN1w4Puoi KPbpICWbDgbo6x+RQT6QLeb/kPgliqBsxXDAIzU=
X-Google-Smtp-Source: ADUXVKKObv1J2ZoCo2naeIUmRPtDww5cp3UECqi0cJAokx/rqrhm2guI2Lgm9laoazywQBUzXsJTPeevnR2ffg82yHg=
X-Received: by 2002:a6b:8dc3:: with SMTP id p186-v6mr1128372iod.70.1527237224675;  Fri, 25 May 2018 01:33:44 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Fri, 25 May 2018 04:33:43 -0400
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <CANatvzwXhqZBDt59HJCThbdhomGbac=Na0vcofZhPbEYRniV-g@mail.gmail.com>
References: <CANatvzwN1kVO3ofvyYX9cg=cKcg4FdqUT3VB6hneEDa5UjT_0w@mail.gmail.com> <CABkgnnUjw4WYDv5mmsFp2nDq4LtdJBzsgdFkxFzEdHrA37tejw@mail.gmail.com> <CANatvzyNHpTFpdS6_A-gijn2+dOiU=zxyiRJsQuSZVy+EyZ1gQ@mail.gmail.com> <CANatvzwXhqZBDt59HJCThbdhomGbac=Na0vcofZhPbEYRniV-g@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Fri, 25 May 2018 04:33:43 -0400
Message-ID: <CAN1APddOMnmf_dAEpVZEjuL2xx5GYK08MHrHBO_OY9JUh+jtjQ@mail.gmail.com>
Subject: Re: Stream0 Proposal: Explicit vs. Implicit ACK (Re: Stream0 Design Team Proposal)
To: Martin Thomson <martin.thomson@gmail.com>, Kazuho Oku <kazuhooku@gmail.com>
Cc: Eric Rescorla <ekr@mozilla.com>, Jana Iyengar <jri.ietf@gmail.com>, QUIC WG <quic@ietf.org>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="00000000000043bf65056d03a0af"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/JUrvtRF6P-4NGKlGHC4h0KEFRz8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 May 2018 08:33:48 -0000

--00000000000043bf65056d03a0af
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

The overview doc seems to be clear on ACK=E2=80=99s in general, not sure ab=
out EOED
specficially.

https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6S=
wHY8/edit

section 2.2

ACKs in 1-RTT packets will acknowledge the receipt of 0-RTT or 1-RTT
packets.  ACKs cannot be sent in 0-RTT packets.



Kind Regards,
Mikkel Fahn=C3=B8e J=C3=B8rgensen


On 25 May 2018 at 10.06.49, Kazuho Oku (kazuhooku@gmail.com) wrote:

I think I might have found an issue in the explicit ACK approach that
we use in the PR.

That is that EOED cannot be ACKed.

Assuming that EOED is sent using 0-RTT keys, it needs to be acked by
the server using the same key, because the transmission of EOED needs
to be guaranteed for the TLS handshake to complete.

However, there is no 0-RTT send key on the server-side.

Do we have any rule for dealing with this? I searched though the text
of the PR but could not find an answer.


2018-05-24 14:49 GMT+09:00 Kazuho Oku <kazuhooku@gmail.com>:
> 2018-05-24 13:43 GMT+09:00 Martin Thomson <martin.thomson@gmail.com>:
>> The obvious solution for the problem of not retransmitting the client
>> Finished is to retransmit it until it is acknowledged. With the proposed
>> design, that means that the server sends a Handshake message after the
>> handshake is done, which I think is fine. If the client sends Finished
>> until it is acknowledged, then I think we're good.
>
> I agree that that would work.
>
> IIUC downsides compared to the implicit ACK approach are that the
> server needs to keep the old keys for certain amount of time (e.g., 2
> MSL) and that the additional Handshake packet will consume about 30
> octets of the 3 packet window that we have for the server's first
> flights.
>
>> I can see the appeal in saying that if you receive an ACK for 1-RTT data
>> then your Handshake packets must have been received. I can see that
>> working even, but you have to be careful. It's just a signal that you
can
>> stop sending CRYPTO frames, not that you are done with the keys. You
might
>> need to send ACK again and you might still receive packets at that
level.
>> You could drop read keys and ACK only the old packets that you did
decrypt,
>> but I suspect that it's better to authenticate any packet and ACK
>> faithfully, which would be better for your peer's congestion state.
>>
>> That also means that you probably need to have timers for cleaning up,
to
>> avoid the pathological case where acknowledgments are sent indefinitely.
>
> I agree with your argument about congestion control.
>
> One way of acquiring correct congestion control information in the
> implicit ACK approach will be to send coalesced packets that combines
> a Handshake packet with a packet protected by a higher encryption key.
> That will guarantee that you would receive an ACK for the delivery of
> the datagrams, and you can feed the information to the congestion
> controller.
>
> FWIW, I have implemented implicit ACK in quicly, and it only required
> about 40 additional lines of code, including the retransmission logic
> for Handshake_Done. The code can be found at
>
https://github.com/h2o/quicly/pull/8/commits/eee6eb5fc7c0359edfeb0b8f89ae9a=
c191ef0758.

> Coalesced packets is not implemented.
>
>>
>> I think that the FIN bit idea might work to close out the use of the
>> "stream" for each set of keys. That is, as opposed to the crypto stream
as
>> a whole. But it's duplicative: the crypto handshake needs to know when
it
>> moves from one set of keys to the next and replicating that signaling at
>> the QUIC layer only really adds things to check for consistency.
>> On Thu, May 24, 2018 at 11:07 AM Kazuho Oku <kazuhooku@gmail.com> wrote:
>>
>>> 2018-05-24 3:46 GMT+09:00 Jana Iyengar <jri.ietf@gmail.com>:
>>
>>> > A thought occurs to me: a CRYPTO_HS frame with the fin bit set can be
>> used
>>> > to indicate that the handshake is done.This could be used as a signal
>> (aka
>>> > HANDSHAKE_DONE) to solve Marten's problem of a client rtxing a CFIN.
Of
>>> > course, this would mean that this particular CRYPTO_HS frame would be
>>> > encrypted with a 1-RTT key... which *I think* is fine. What do you
>> think?
>>
>>> I am not sure if that is a good approach.
>>
>>> I would assume that we would like to keep the handshake flow on the
>>> 1-RTT key open for the lifetime of the QUIC connection, so that we
>>> could send things related to the TLS (e.g. session tickets). Sending
>>> FIN from the server right after receiving ClientFinished makes that
>>> impossible.
>>
>>> Having said that, I do agree that the need for a dedicated frame is a
>>> pain. It is a pain because we need to have a retransmission logic for
>>> the frame.
>>
>>> I think that you are making a good point in suggesting to consider
>>> reusing the retransmission logic that already exists for bidirectional
>>> flows. But as said, FIN bit does not seem like an answer in this case.
>>
>>> IMO, ideally we should define a new TLS post-handshake message (that
>>> does not convey any data), and send that from the server in response
>>> to ClientFinished using 1-RTT packet. The message will act as a signal
>>> that the server has received ClientFinished.
>>
>>> The benefit of this approach is that we can reuse the retransmission
>>> logic that will exist for handshake flows. The downside is that TLS
>>> stacks need to be aware of the new handshake message.
>>
>>> Considering the fact that the Design Team is already suggesting a
>>> substantial change to the TLS stack, we might have chance in asking
>>> for the addition of a new handshake message. But I am not sure.
>>
>>> --
>>> Kazuho Oku
>
>
>
> --
> Kazuho Oku



--=20
Kazuho Oku

--00000000000043bf65056d03a0af
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">The overview doc see=
ms to be clear on ACK=E2=80=99s in general, not sure about EOED specficiall=
y.</div><div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;f=
ont-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div>=
<div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size=
:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><a href=3D"https:/=
/docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j6SwHY8/ed=
it">https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT9=
3j6SwHY8/edit</a></div><div id=3D"bloop_customfont" style=3D"font-family:He=
lvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:a=
uto"><br></div><div id=3D"bloop_customfont" style=3D"font-family:Helvetica,=
Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">sec=
tion 2.2</div><div id=3D"bloop_customfont" style=3D"font-family:Helvetica,A=
rial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br>=
</div><div id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;fon=
t-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><span id=3D"=
docs-internal-guid-1bb287d2-966d-5d1c-75cf-80f8291baf82" style=3D"font-fami=
ly:-webkit-standard"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0p=
t;margin-bottom:0pt;text-align:justify"><span style=3D"font-size:11pt;font-=
family:Arial;background-color:transparent;font-variant-ligatures:normal;fon=
t-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">A=
CKs in 1-RTT packets will acknowledge the receipt of 0-RTT or 1-RTT packets=
.=C2=A0 ACKs cannot be sent in 0-RTT packets.</span></p></span><br class=3D=
"Apple-interchange-newline" style=3D"font-family:-webkit-standard"></div><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"><br></div> <br> <div=
 id=3D"bloop_sign_1527237147591558912" class=3D"bloop_sign"><div style=3D"f=
ont-family:helvetica,arial;font-size:13px">Kind Regards,</div><div style=3D=
"font-family:helvetica,arial;font-size:13px">Mikkel Fahn=C3=B8e J=C3=B8rgen=
sen<br><br></div></div> <br><p class=3D"airmail_on">On 25 May 2018 at 10.06=
.49, Kazuho Oku (<a href=3D"mailto:kazuhooku@gmail.com">kazuhooku@gmail.com=
</a>) wrote:</p> <blockquote type=3D"cite" class=3D"clean_bq"><span><div><d=
iv></div><div>I think I might have found an issue in the explicit ACK appro=
ach that
<br>we use in the PR.
<br>
<br>That is that EOED cannot be ACKed.
<br>
<br>Assuming that EOED is sent using 0-RTT keys, it needs to be acked by
<br>the server using the same key, because the transmission of EOED needs
<br>to be guaranteed for the TLS handshake to complete.
<br>
<br>However, there is no 0-RTT send key on the server-side.
<br>
<br>Do we have any rule for dealing with this? I searched though the text
<br>of the PR but could not find an answer.
<br>
<br>
<br>2018-05-24 14:49 GMT+09:00 Kazuho Oku &lt;<a href=3D"mailto:kazuhooku@g=
mail.com">kazuhooku@gmail.com</a>&gt;:
<br>&gt; 2018-05-24 13:43 GMT+09:00 Martin Thomson &lt;<a href=3D"mailto:ma=
rtin.thomson@gmail.com">martin.thomson@gmail.com</a>&gt;:
<br>&gt;&gt; The obvious solution for the problem of not retransmitting the=
 client
<br>&gt;&gt; Finished is to retransmit it until it is acknowledged.  With t=
he proposed
<br>&gt;&gt; design, that means that the server sends a Handshake message a=
fter the
<br>&gt;&gt; handshake is done, which I think is fine.  If the client sends=
 Finished
<br>&gt;&gt; until it is acknowledged, then I think we&#39;re good.
<br>&gt;
<br>&gt; I agree that that would work.
<br>&gt;
<br>&gt; IIUC downsides compared to the implicit ACK approach are that the
<br>&gt; server needs to keep the old keys for certain amount of time (e.g.=
, 2
<br>&gt; MSL) and that the additional Handshake packet will consume about 3=
0
<br>&gt; octets of the 3 packet window that we have for the server&#39;s fi=
rst
<br>&gt; flights.
<br>&gt;
<br>&gt;&gt; I can see the appeal in saying that if you receive an ACK for =
1-RTT data
<br>&gt;&gt; then your Handshake packets must have been received.  I can se=
e that
<br>&gt;&gt; working even, but you have to be careful.  It&#39;s just a sig=
nal that you can
<br>&gt;&gt; stop sending CRYPTO frames, not that you are done with the key=
s.  You might
<br>&gt;&gt; need to send ACK again and you might still receive packets at =
that level.
<br>&gt;&gt; You could drop read keys and ACK only the old packets that you=
 did decrypt,
<br>&gt;&gt; but I suspect that it&#39;s better to authenticate any packet =
and ACK
<br>&gt;&gt; faithfully, which would be better for your peer&#39;s congesti=
on state.
<br>&gt;&gt;
<br>&gt;&gt; That also means that you probably need to have timers for clea=
ning up, to
<br>&gt;&gt; avoid the pathological case where acknowledgments are sent ind=
efinitely.
<br>&gt;
<br>&gt; I agree with your argument about congestion control.
<br>&gt;
<br>&gt; One way of acquiring correct congestion control information in the
<br>&gt; implicit ACK approach will be to send coalesced packets that combi=
nes
<br>&gt; a Handshake packet with a packet protected by a higher encryption =
key.
<br>&gt; That will guarantee that you would receive an ACK for the delivery=
 of
<br>&gt; the datagrams, and you can feed the information to the congestion
<br>&gt; controller.
<br>&gt;
<br>&gt; FWIW, I have implemented implicit ACK in quicly, and it only requi=
red
<br>&gt; about 40 additional lines of code, including the retransmission lo=
gic
<br>&gt; for Handshake_Done. The code can be found at
<br>&gt; <a href=3D"https://github.com/h2o/quicly/pull/8/commits/eee6eb5fc7=
c0359edfeb0b8f89ae9ac191ef0758">https://github.com/h2o/quicly/pull/8/commit=
s/eee6eb5fc7c0359edfeb0b8f89ae9ac191ef0758</a>.
<br>&gt; Coalesced packets is not implemented.
<br>&gt;
<br>&gt;&gt;
<br>&gt;&gt; I think that the FIN bit idea might work to close out the use =
of the
<br>&gt;&gt; &quot;stream&quot; for each set of keys. That is, as opposed t=
o the crypto stream as
<br>&gt;&gt; a whole.  But it&#39;s duplicative: the crypto handshake needs=
 to know when it
<br>&gt;&gt; moves from one set of keys to the next and replicating that si=
gnaling at
<br>&gt;&gt; the QUIC layer only really adds things to check for consistenc=
y.
<br>&gt;&gt; On Thu, May 24, 2018 at 11:07 AM Kazuho Oku &lt;<a href=3D"mai=
lto:kazuhooku@gmail.com">kazuhooku@gmail.com</a>&gt; wrote:
<br>&gt;&gt;
<br>&gt;&gt;&gt; 2018-05-24 3:46 GMT+09:00 Jana Iyengar &lt;<a href=3D"mail=
to:jri.ietf@gmail.com">jri.ietf@gmail.com</a>&gt;:
<br>&gt;&gt;
<br>&gt;&gt;&gt; &gt; A thought occurs to me: a CRYPTO_HS frame with the fi=
n bit set can be
<br>&gt;&gt; used
<br>&gt;&gt;&gt; &gt; to indicate that the handshake is done.This could be =
used as a signal
<br>&gt;&gt; (aka
<br>&gt;&gt;&gt; &gt; HANDSHAKE_DONE) to solve Marten&#39;s problem of a cl=
ient rtxing a CFIN. Of
<br>&gt;&gt;&gt; &gt; course, this would mean that this particular CRYPTO_H=
S frame would be
<br>&gt;&gt;&gt; &gt; encrypted with a 1-RTT key... which *I think* is fine=
. What do you
<br>&gt;&gt; think?
<br>&gt;&gt;
<br>&gt;&gt;&gt; I am not sure if that is a good approach.
<br>&gt;&gt;
<br>&gt;&gt;&gt; I would assume that we would like to keep the handshake fl=
ow on the
<br>&gt;&gt;&gt; 1-RTT key open for the lifetime of the QUIC connection, so=
 that we
<br>&gt;&gt;&gt; could send things related to the TLS (e.g. session tickets=
). Sending
<br>&gt;&gt;&gt; FIN from the server right after receiving ClientFinished m=
akes that
<br>&gt;&gt;&gt; impossible.
<br>&gt;&gt;
<br>&gt;&gt;&gt; Having said that, I do agree that the need for a dedicated=
 frame is a
<br>&gt;&gt;&gt; pain. It is a pain because we need to have a retransmissio=
n logic for
<br>&gt;&gt;&gt; the frame.
<br>&gt;&gt;
<br>&gt;&gt;&gt; I think that you are making a good point in suggesting to =
consider
<br>&gt;&gt;&gt; reusing the retransmission logic that already exists for b=
idirectional
<br>&gt;&gt;&gt; flows. But as said, FIN bit does not seem like an answer i=
n this case.
<br>&gt;&gt;
<br>&gt;&gt;&gt; IMO, ideally we should define a new TLS post-handshake mes=
sage (that
<br>&gt;&gt;&gt; does not convey any data), and send that from the server i=
n response
<br>&gt;&gt;&gt; to ClientFinished using 1-RTT packet. The message will act=
 as a signal
<br>&gt;&gt;&gt; that the server has received ClientFinished.
<br>&gt;&gt;
<br>&gt;&gt;&gt; The benefit of this approach is that we can reuse the retr=
ansmission
<br>&gt;&gt;&gt; logic that will exist for handshake flows. The downside is=
 that TLS
<br>&gt;&gt;&gt; stacks need to be aware of the new handshake message.
<br>&gt;&gt;
<br>&gt;&gt;&gt; Considering the fact that the Design Team is already sugge=
sting a
<br>&gt;&gt;&gt; substantial change to the TLS stack, we might have chance =
in asking
<br>&gt;&gt;&gt; for the addition of a new handshake message. But I am not =
sure.
<br>&gt;&gt;
<br>&gt;&gt;&gt; --
<br>&gt;&gt;&gt; Kazuho Oku
<br>&gt;
<br>&gt;
<br>&gt;
<br>&gt; --
<br>&gt; Kazuho Oku
<br>
<br>
<br>
<br>-- =20
<br>Kazuho Oku
<br>
<br></div></div></span></blockquote></body></html>

--00000000000043bf65056d03a0af--


From nobody Fri May 25 01:57:36 2018
Return-Path: <kazuhooku@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 63942124BE8 for <quic@ietfa.amsl.com>; Fri, 25 May 2018 01:57:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Yqb67i5kBai0 for <quic@ietfa.amsl.com>; Fri, 25 May 2018 01:57:32 -0700 (PDT)
Received: from mail-pf0-x22c.google.com (mail-pf0-x22c.google.com [IPv6:2607:f8b0:400e:c00::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 049741201FA for <quic@ietf.org>; Fri, 25 May 2018 01:57:32 -0700 (PDT)
Received: by mail-pf0-x22c.google.com with SMTP id a22-v6so2271819pfn.6 for <quic@ietf.org>; Fri, 25 May 2018 01:57:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=pzzhsJk0NQ3l8LuAvpNoQMLDlDdDvoccRKAnBBStRow=; b=PFwH88xM7ANR76bezhOEhrJgRrA3k+caS7oTx8R7ryfCKrtS9WB9n6gTUVgP+MvILv 5agF5g4o4E1iRk1RrHTruXUxFgTGg5s/sHoSPL3SB1OA5H1gO0tQfNBDUHZXyU0OYmK1 RLuzWk3Fit3Rnn0du13PygOiFvTzlEQPqvS9w8jPC9fma3gktQdqLGRNWgH19qZeMYok msf8dPge9RSiJ7Tx6PQZ8EIBViB3NfwsoH4JIr5yPRwJCPyA3Jhe3dikE7tY5EN0lAPP bHPEQf7WV9IQse0Zpj32DPSeXlp4Pe3SWW16AEaGpAPVhmVafNpLa1YFzFniVAie0Z9s 6hEQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=pzzhsJk0NQ3l8LuAvpNoQMLDlDdDvoccRKAnBBStRow=; b=aOpr1mLm+oiQRgPQqKPYosn9Sa2tvXWAAGvuFCLhMcun372Bicj/WVpIIW0LSpeq1c +eO/t9p42BWaoxKnxmdmNun26727cKqMgAZ2+vuRaxDvzcVs8r4DrZeSZIAuc7OtNhNx J+b4P3O3yKKOp8LjXirQVWmTGtEsVmXweWrfzlOoCzH65V4MU8ZW1vg2eCB+FWHR3yfa 2TwxMQVxwnj7WSan2lfLnrX7Oo95jEKzJtnZZvMw9mxmdIPGTSBHHTiy5l8HZUFgbwG4 Vsdn6jGZ7DS9o5xow+TodTL703E/rgFSr7Bi/7oChImx/TNNwd70S7AhFlNtjT2JNPqk WOkg==
X-Gm-Message-State: ALKqPwfYg+xb0paj/sjicfVGdjTQ4FDZX7+ZVIHwYk5c7AqwN3/y3cht 8ls5w4Hr9jSTV334IdQbOVDOIvpbzEXHTO4T9fw=
X-Google-Smtp-Source: AB8JxZq8rsLpn8Wl2Wu8RxeSACzZTumJNcwpjKu6YNE+A4VV5zW0SAPDmqAz4rWKzkwSyVMsgkoBQhLHcqUKQaZNL30=
X-Received: by 2002:a65:61c8:: with SMTP id j8-v6mr1291412pgv.370.1527238651246;  Fri, 25 May 2018 01:57:31 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a17:90a:1189:0:0:0:0 with HTTP; Fri, 25 May 2018 01:57:30 -0700 (PDT)
In-Reply-To: <CAN1APddOMnmf_dAEpVZEjuL2xx5GYK08MHrHBO_OY9JUh+jtjQ@mail.gmail.com>
References: <CANatvzwN1kVO3ofvyYX9cg=cKcg4FdqUT3VB6hneEDa5UjT_0w@mail.gmail.com> <CABkgnnUjw4WYDv5mmsFp2nDq4LtdJBzsgdFkxFzEdHrA37tejw@mail.gmail.com> <CANatvzyNHpTFpdS6_A-gijn2+dOiU=zxyiRJsQuSZVy+EyZ1gQ@mail.gmail.com> <CANatvzwXhqZBDt59HJCThbdhomGbac=Na0vcofZhPbEYRniV-g@mail.gmail.com> <CAN1APddOMnmf_dAEpVZEjuL2xx5GYK08MHrHBO_OY9JUh+jtjQ@mail.gmail.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Fri, 25 May 2018 17:57:30 +0900
Message-ID: <CANatvzw7tR8wZud_bFmxc2HPPXAMBLUx=SC7MoD87JQcvQfbZQ@mail.gmail.com>
Subject: Re: Stream0 Proposal: Explicit vs. Implicit ACK (Re: Stream0 Design Team Proposal)
To: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
Cc: Martin Thomson <martin.thomson@gmail.com>, Eric Rescorla <ekr@mozilla.com>, Jana Iyengar <jri.ietf@gmail.com>, QUIC WG <quic@ietf.org>,  Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/vii4kueVoKUIEvbo6AehOKua5fA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 May 2018 08:57:35 -0000

2018-05-25 17:33 GMT+09:00 Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@gmai=
l.com>:
> The overview doc seems to be clear on ACK=E2=80=99s in general, not sure =
about EOED
> specficially.
>
> https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6auojfJLkxddT93j=
6SwHY8/edit
>
> section 2.2
>
> ACKs in 1-RTT packets will acknowledge the receipt of 0-RTT or 1-RTT
> packets.  ACKs cannot be sent in 0-RTT packets.

Thank you for pointing that out.

That statement in the doc seem to contradict with the following
statement in the PR.

  - ACK frames MAY appear in packets of any encryption level, but
    MUST only acknowledge packets which appeared in that encryption
    level.

Maybe the reference to "encryption level" should be corrected to
"packet number space."

>
>
>
>
> Kind Regards,
> Mikkel Fahn=C3=B8e J=C3=B8rgensen
>
>
> On 25 May 2018 at 10.06.49, Kazuho Oku (kazuhooku@gmail.com) wrote:
>
> I think I might have found an issue in the explicit ACK approach that
> we use in the PR.
>
> That is that EOED cannot be ACKed.
>
> Assuming that EOED is sent using 0-RTT keys, it needs to be acked by
> the server using the same key, because the transmission of EOED needs
> to be guaranteed for the TLS handshake to complete.
>
> However, there is no 0-RTT send key on the server-side.
>
> Do we have any rule for dealing with this? I searched though the text
> of the PR but could not find an answer.
>
>
> 2018-05-24 14:49 GMT+09:00 Kazuho Oku <kazuhooku@gmail.com>:
>> 2018-05-24 13:43 GMT+09:00 Martin Thomson <martin.thomson@gmail.com>:
>>> The obvious solution for the problem of not retransmitting the client
>>> Finished is to retransmit it until it is acknowledged. With the propose=
d
>>> design, that means that the server sends a Handshake message after the
>>> handshake is done, which I think is fine. If the client sends Finished
>>> until it is acknowledged, then I think we're good.
>>
>> I agree that that would work.
>>
>> IIUC downsides compared to the implicit ACK approach are that the
>> server needs to keep the old keys for certain amount of time (e.g., 2
>> MSL) and that the additional Handshake packet will consume about 30
>> octets of the 3 packet window that we have for the server's first
>> flights.
>>
>>> I can see the appeal in saying that if you receive an ACK for 1-RTT dat=
a
>>> then your Handshake packets must have been received. I can see that
>>> working even, but you have to be careful. It's just a signal that you c=
an
>>> stop sending CRYPTO frames, not that you are done with the keys. You
>>> might
>>> need to send ACK again and you might still receive packets at that leve=
l.
>>> You could drop read keys and ACK only the old packets that you did
>>> decrypt,
>>> but I suspect that it's better to authenticate any packet and ACK
>>> faithfully, which would be better for your peer's congestion state.
>>>
>>> That also means that you probably need to have timers for cleaning up, =
to
>>> avoid the pathological case where acknowledgments are sent indefinitely=
.
>>
>> I agree with your argument about congestion control.
>>
>> One way of acquiring correct congestion control information in the
>> implicit ACK approach will be to send coalesced packets that combines
>> a Handshake packet with a packet protected by a higher encryption key.
>> That will guarantee that you would receive an ACK for the delivery of
>> the datagrams, and you can feed the information to the congestion
>> controller.
>>
>> FWIW, I have implemented implicit ACK in quicly, and it only required
>> about 40 additional lines of code, including the retransmission logic
>> for Handshake_Done. The code can be found at
>>
>> https://github.com/h2o/quicly/pull/8/commits/eee6eb5fc7c0359edfeb0b8f89a=
e9ac191ef0758.
>> Coalesced packets is not implemented.
>>
>>>
>>> I think that the FIN bit idea might work to close out the use of the
>>> "stream" for each set of keys. That is, as opposed to the crypto stream
>>> as
>>> a whole. But it's duplicative: the crypto handshake needs to know when =
it
>>> moves from one set of keys to the next and replicating that signaling a=
t
>>> the QUIC layer only really adds things to check for consistency.
>>> On Thu, May 24, 2018 at 11:07 AM Kazuho Oku <kazuhooku@gmail.com> wrote=
:
>>>
>>>> 2018-05-24 3:46 GMT+09:00 Jana Iyengar <jri.ietf@gmail.com>:
>>>
>>>> > A thought occurs to me: a CRYPTO_HS frame with the fin bit set can b=
e
>>> used
>>>> > to indicate that the handshake is done.This could be used as a signa=
l
>>> (aka
>>>> > HANDSHAKE_DONE) to solve Marten's problem of a client rtxing a CFIN.
>>>> > Of
>>>> > course, this would mean that this particular CRYPTO_HS frame would b=
e
>>>> > encrypted with a 1-RTT key... which *I think* is fine. What do you
>>> think?
>>>
>>>> I am not sure if that is a good approach.
>>>
>>>> I would assume that we would like to keep the handshake flow on the
>>>> 1-RTT key open for the lifetime of the QUIC connection, so that we
>>>> could send things related to the TLS (e.g. session tickets). Sending
>>>> FIN from the server right after receiving ClientFinished makes that
>>>> impossible.
>>>
>>>> Having said that, I do agree that the need for a dedicated frame is a
>>>> pain. It is a pain because we need to have a retransmission logic for
>>>> the frame.
>>>
>>>> I think that you are making a good point in suggesting to consider
>>>> reusing the retransmission logic that already exists for bidirectional
>>>> flows. But as said, FIN bit does not seem like an answer in this case.
>>>
>>>> IMO, ideally we should define a new TLS post-handshake message (that
>>>> does not convey any data), and send that from the server in response
>>>> to ClientFinished using 1-RTT packet. The message will act as a signal
>>>> that the server has received ClientFinished.
>>>
>>>> The benefit of this approach is that we can reuse the retransmission
>>>> logic that will exist for handshake flows. The downside is that TLS
>>>> stacks need to be aware of the new handshake message.
>>>
>>>> Considering the fact that the Design Team is already suggesting a
>>>> substantial change to the TLS stack, we might have chance in asking
>>>> for the addition of a new handshake message. But I am not sure.
>>>
>>>> --
>>>> Kazuho Oku
>>
>>
>>
>> --
>> Kazuho Oku
>
>
>
> --
> Kazuho Oku
>



--=20
Kazuho Oku


From nobody Fri May 25 06:52:01 2018
Return-Path: <ekr@rtfm.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7D75C12DA0D for <quic@ietfa.amsl.com>; Fri, 25 May 2018 06:51:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 hULgQ98-3iUE for <quic@ietfa.amsl.com>; Fri, 25 May 2018 06:51:56 -0700 (PDT)
Received: from mail-ot0-x229.google.com (mail-ot0-x229.google.com [IPv6:2607:f8b0:4003:c0f::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E06AA126D45 for <quic@ietf.org>; Fri, 25 May 2018 06:51:55 -0700 (PDT)
Received: by mail-ot0-x229.google.com with SMTP id l12-v6so6131920oth.6 for <quic@ietf.org>; Fri, 25 May 2018 06:51:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=SVNt1FRIYqArtDHD9gUyl24KZFix9r1IKDikBrqLays=; b=Xoh+7uiz40nHorTg/Iu4PgZzI8/2LXLfjdAsKg45IHY8JX4lnwDZovwNu058JTr+vG 3wsDQhtuX+F+ktooSTwsDTMXvbrv3ml8MLnmOMlutVCSZZv49tF27nSNvs87mVkwcRmm 4djqgavHV9UuUkqAoygAoVqIrHmUqIVoNZgMOS1SprVvgwtUOFJasGdrhk26MhrZ68Zz sAMMX/a+a4GlPzN7q+MclOEeNnpISxE7tYZVXF4RW9zJptUyl6XxiT2TPKqQcLRoe+Xe AY8AeJfv5MXbSqXCYESo35T82ti+wYCE46HkOkDniU0CwvMeQzOabnkdM8fDnpUd64/6 Fxew==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=SVNt1FRIYqArtDHD9gUyl24KZFix9r1IKDikBrqLays=; b=Svj64yt9/0+X2OoDS1TT67+rALTgU+pf81+EjbESzITA5h1//cWjrPY3aYBcQdQXhS W7iGe1U2GANl0FO/X14DrCObqSY1nRs6YLkcESbmpUMfVclrKd634ESvQUgS/oBWH7Xz /RBx2YKv1U0vy/O9KNZUxn2IJ5vuvnkTa0ZF/vh1DMiPDzpt6vEz0UWXbHmnOe1u2fWO 0Gvrbty/WOKp/OdiMIp7REytoPv0QeXqE45BAzKZPh5juWm0R32JHJMI7hFMwxIqtMTq 1XJDx+hO/rpahscULBmW4fkEo4mu6eKwr/APkIwtGi9DBbLqCYcBOyIilofXFg8ngvPP ZFXg==
X-Gm-Message-State: ALKqPwesP2o4SXSQk/zSYQwYjFgftesCvVOvaZNjqKhpcdBRxhIYwV6C IjJoKB4t38nFrVCKJSxAJIN5icHb7MSlX6WYszO/HA==
X-Google-Smtp-Source: ADUXVKJabysCCvu2R0KR4jJN4HM/F+kDAuL0hS2F6tORfJ2JhnGD5IhZhy1/sEoC/UWNZLqGX+VQooeMfaZ3JwqwRUw=
X-Received: by 2002:a9d:224d:: with SMTP id o71-v6mr1720032ota.101.1527256315049;  Fri, 25 May 2018 06:51:55 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:ac9:66:0:0:0:0:0 with HTTP; Fri, 25 May 2018 06:51:14 -0700 (PDT)
In-Reply-To: <CANatvzw7tR8wZud_bFmxc2HPPXAMBLUx=SC7MoD87JQcvQfbZQ@mail.gmail.com>
References: <CANatvzwN1kVO3ofvyYX9cg=cKcg4FdqUT3VB6hneEDa5UjT_0w@mail.gmail.com> <CABkgnnUjw4WYDv5mmsFp2nDq4LtdJBzsgdFkxFzEdHrA37tejw@mail.gmail.com> <CANatvzyNHpTFpdS6_A-gijn2+dOiU=zxyiRJsQuSZVy+EyZ1gQ@mail.gmail.com> <CANatvzwXhqZBDt59HJCThbdhomGbac=Na0vcofZhPbEYRniV-g@mail.gmail.com> <CAN1APddOMnmf_dAEpVZEjuL2xx5GYK08MHrHBO_OY9JUh+jtjQ@mail.gmail.com> <CANatvzw7tR8wZud_bFmxc2HPPXAMBLUx=SC7MoD87JQcvQfbZQ@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 25 May 2018 06:51:14 -0700
Message-ID: <CABcZeBP16jmef9voFBisnqQAAbN8TgwSBC9nXEQ3dN3ST9gVLQ@mail.gmail.com>
Subject: Re: Stream0 Proposal: Explicit vs. Implicit ACK (Re: Stream0 Design Team Proposal)
To: Kazuho Oku <kazuhooku@gmail.com>
Cc: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>,  Eric Rescorla <ekr@mozilla.com>, Jana Iyengar <jri.ietf@gmail.com>, QUIC WG <quic@ietf.org>, Martin Thomson <martin.thomson@gmail.com>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="00000000000023ce01056d0812b7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/NzriqmMiMvbOoE4pvVwE3JSCYrU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 May 2018 13:52:00 -0000

--00000000000023ce01056d0812b7
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

On Fri, May 25, 2018 at 1:57 AM, Kazuho Oku <kazuhooku@gmail.com> wrote:

> 2018-05-25 17:33 GMT+09:00 Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@gm=
ail.com>:
> > The overview doc seems to be clear on ACK=E2=80=99s in general, not sur=
e about
> EOED
> > specficially.
> >
> > https://docs.google.com/document/d/1fRsJqPinJl8N3b-
> bflDRV6auojfJLkxddT93j6SwHY8/edit
> >
> > section 2.2
> >
> > ACKs in 1-RTT packets will acknowledge the receipt of 0-RTT or 1-RTT
> > packets.  ACKs cannot be sent in 0-RTT packets.
>
> Thank you for pointing that out.
>
> That statement in the doc seem to contradict with the following
> statement in the PR.
>
>   - ACK frames MAY appear in packets of any encryption level, but
>     MUST only acknowledge packets which appeared in that encryption
>     level.
>

> Maybe the reference to "encryption level" should be corrected to
> "packet number space."
>

I agree. this is a defect.

-Ekr

>
> >
> >
> >
> > Kind Regards,
> > Mikkel Fahn=C3=B8e J=C3=B8rgensen
> >
> >
> > On 25 May 2018 at 10.06.49, Kazuho Oku (kazuhooku@gmail.com) wrote:
> >
> > I think I might have found an issue in the explicit ACK approach that
> > we use in the PR.
> >
> > That is that EOED cannot be ACKed.
> >
> > Assuming that EOED is sent using 0-RTT keys, it needs to be acked by
> > the server using the same key, because the transmission of EOED needs
> > to be guaranteed for the TLS handshake to complete.
> >
> > However, there is no 0-RTT send key on the server-side.
> >
> > Do we have any rule for dealing with this? I searched though the text
> > of the PR but could not find an answer.
> >
> >
> > 2018-05-24 14:49 GMT+09:00 Kazuho Oku <kazuhooku@gmail.com>:
> >> 2018-05-24 13:43 GMT+09:00 Martin Thomson <martin.thomson@gmail.com>:
> >>> The obvious solution for the problem of not retransmitting the client
> >>> Finished is to retransmit it until it is acknowledged. With the
> proposed
> >>> design, that means that the server sends a Handshake message after th=
e
> >>> handshake is done, which I think is fine. If the client sends Finishe=
d
> >>> until it is acknowledged, then I think we're good.
> >>
> >> I agree that that would work.
> >>
> >> IIUC downsides compared to the implicit ACK approach are that the
> >> server needs to keep the old keys for certain amount of time (e.g., 2
> >> MSL) and that the additional Handshake packet will consume about 30
> >> octets of the 3 packet window that we have for the server's first
> >> flights.
> >>
> >>> I can see the appeal in saying that if you receive an ACK for 1-RTT
> data
> >>> then your Handshake packets must have been received. I can see that
> >>> working even, but you have to be careful. It's just a signal that you
> can
> >>> stop sending CRYPTO frames, not that you are done with the keys. You
> >>> might
> >>> need to send ACK again and you might still receive packets at that
> level.
> >>> You could drop read keys and ACK only the old packets that you did
> >>> decrypt,
> >>> but I suspect that it's better to authenticate any packet and ACK
> >>> faithfully, which would be better for your peer's congestion state.
> >>>
> >>> That also means that you probably need to have timers for cleaning up=
,
> to
> >>> avoid the pathological case where acknowledgments are sent
> indefinitely..
> >>
> >> I agree with your argument about congestion control.
> >>
> >> One way of acquiring correct congestion control information in the
> >> implicit ACK approach will be to send coalesced packets that combines
> >> a Handshake packet with a packet protected by a higher encryption key.
> >> That will guarantee that you would receive an ACK for the delivery of
> >> the datagrams, and you can feed the information to the congestion
> >> controller.
> >>
> >> FWIW, I have implemented implicit ACK in quicly, and it only required
> >> about 40 additional lines of code, including the retransmission logic
> >> for Handshake_Done. The code can be found at
> >>
> >> https://github.com/h2o/quicly/pull/8/commits/
> eee6eb5fc7c0359edfeb0b8f89ae9ac191ef0758.
> >> Coalesced packets is not implemented.
> >>
> >>>
> >>> I think that the FIN bit idea might work to close out the use of the
> >>> "stream" for each set of keys. That is, as opposed to the crypto stre=
am
> >>> as
> >>> a whole. But it's duplicative: the crypto handshake needs to know whe=
n
> it
> >>> moves from one set of keys to the next and replicating that signaling
> at
> >>> the QUIC layer only really adds things to check for consistency.
> >>> On Thu, May 24, 2018 at 11:07 AM Kazuho Oku <kazuhooku@gmail.com>
> wrote:
> >>>
> >>>> 2018-05-24 3:46 GMT+09:00 Jana Iyengar <jri.ietf@gmail.com>:
> >>>
> >>>> > A thought occurs to me: a CRYPTO_HS frame with the fin bit set can
> be
> >>> used
> >>>> > to indicate that the handshake is done.This could be used as a
> signal
> >>> (aka
> >>>> > HANDSHAKE_DONE) to solve Marten's problem of a client rtxing a CFI=
N.
> >>>> > Of
> >>>> > course, this would mean that this particular CRYPTO_HS frame would
> be
> >>>> > encrypted with a 1-RTT key... which *I think* is fine. What do you
> >>> think?
> >>>
> >>>> I am not sure if that is a good approach.
> >>>
> >>>> I would assume that we would like to keep the handshake flow on the
> >>>> 1-RTT key open for the lifetime of the QUIC connection, so that we
> >>>> could send things related to the TLS (e.g. session tickets). Sending
> >>>> FIN from the server right after receiving ClientFinished makes that
> >>>> impossible.
> >>>
> >>>> Having said that, I do agree that the need for a dedicated frame is =
a
> >>>> pain. It is a pain because we need to have a retransmission logic fo=
r
> >>>> the frame.
> >>>
> >>>> I think that you are making a good point in suggesting to consider
> >>>> reusing the retransmission logic that already exists for bidirection=
al
> >>>> flows. But as said, FIN bit does not seem like an answer in this cas=
e.
> >>>
> >>>> IMO, ideally we should define a new TLS post-handshake message (that
> >>>> does not convey any data), and send that from the server in response
> >>>> to ClientFinished using 1-RTT packet. The message will act as a sign=
al
> >>>> that the server has received ClientFinished.
> >>>
> >>>> The benefit of this approach is that we can reuse the retransmission
> >>>> logic that will exist for handshake flows. The downside is that TLS
> >>>> stacks need to be aware of the new handshake message.
> >>>
> >>>> Considering the fact that the Design Team is already suggesting a
> >>>> substantial change to the TLS stack, we might have chance in asking
> >>>> for the addition of a new handshake message. But I am not sure.
> >>>
> >>>> --
> >>>> Kazuho Oku
> >>
> >>
> >>
> >> --
> >> Kazuho Oku
> >
> >
> >
> > --
> > Kazuho Oku
> >
>
>
>
> --
> Kazuho Oku
>
>

--00000000000023ce01056d0812b7
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><br><div class=3D"gmail_extra"><br><div class=3D"gmail_quo=
te">On Fri, May 25, 2018 at 1:57 AM, Kazuho Oku <span dir=3D"ltr">&lt;<a hr=
ef=3D"mailto:kazuhooku@gmail.com" target=3D"_blank">kazuhooku@gmail.com</a>=
&gt;</span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">2018-=
05-25 17:33 GMT+09:00 Mikkel Fahn=C3=B8e J=C3=B8rgensen &lt;<a href=3D"mail=
to:mikkelfj@gmail.com">mikkelfj@gmail.com</a>&gt;:<br>
&gt; The overview doc seems to be clear on ACK=E2=80=99s in general, not su=
re about EOED<br>
&gt; specficially.<br>
&gt;<br>
&gt; <a href=3D"https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6a=
uojfJLkxddT93j6SwHY8/edit" rel=3D"noreferrer" target=3D"_blank">https://doc=
s.google.com/<wbr>document/d/1fRsJqPinJl8N3b-<wbr>bflDRV6auojfJLkxddT93j6Sw=
HY8/<wbr>edit</a><br>
&gt;<br>
&gt; section 2.2<br>
&gt;<br>
&gt; ACKs in 1-RTT packets will acknowledge the receipt of 0-RTT or 1-RTT<b=
r>
</span>&gt; packets.=C2=A0 ACKs cannot be sent in 0-RTT packets.<br>
<br>
Thank you for pointing that out.<br>
<br>
That statement in the doc seem to contradict with the following<br>
statement in the PR.<br>
<br>
=C2=A0 - ACK frames MAY appear in packets of any encryption level, but<br>
=C2=A0 =C2=A0 MUST only acknowledge packets which appeared in that encrypti=
on<br>
=C2=A0 =C2=A0 level.<br></blockquote><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Maybe the reference to &quot;encryption level&quot; should be corrected to<=
br>
&quot;packet number space.&quot;<span class=3D""><br></span></blockquote><d=
iv><br></div><div>I agree. this is a defect.</div><div><br></div><div>-Ekr<=
/div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0=
 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class=3D"">
&gt;<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Kind Regards,<br>
&gt; Mikkel Fahn=C3=B8e J=C3=B8rgensen<br>
&gt;<br>
&gt;<br>
</span><div><div class=3D"h5">&gt; On 25 May 2018 at 10.06.49, Kazuho Oku (=
<a href=3D"mailto:kazuhooku@gmail.com">kazuhooku@gmail.com</a>) wrote:<br>
&gt;<br>
&gt; I think I might have found an issue in the explicit ACK approach that<=
br>
&gt; we use in the PR.<br>
&gt;<br>
&gt; That is that EOED cannot be ACKed.<br>
&gt;<br>
&gt; Assuming that EOED is sent using 0-RTT keys, it needs to be acked by<b=
r>
&gt; the server using the same key, because the transmission of EOED needs<=
br>
&gt; to be guaranteed for the TLS handshake to complete.<br>
&gt;<br>
&gt; However, there is no 0-RTT send key on the server-side.<br>
&gt;<br>
&gt; Do we have any rule for dealing with this? I searched though the text<=
br>
&gt; of the PR but could not find an answer.<br>
&gt;<br>
&gt;<br>
&gt; 2018-05-24 14:49 GMT+09:00 Kazuho Oku &lt;<a href=3D"mailto:kazuhooku@=
gmail.com">kazuhooku@gmail.com</a>&gt;:<br>
&gt;&gt; 2018-05-24 13:43 GMT+09:00 Martin Thomson &lt;<a href=3D"mailto:ma=
rtin.thomson@gmail.com">martin.thomson@gmail.com</a>&gt;:<br>
&gt;&gt;&gt; The obvious solution for the problem of not retransmitting the=
 client<br>
&gt;&gt;&gt; Finished is to retransmit it until it is acknowledged. With th=
e proposed<br>
&gt;&gt;&gt; design, that means that the server sends a Handshake message a=
fter the<br>
&gt;&gt;&gt; handshake is done, which I think is fine. If the client sends =
Finished<br>
&gt;&gt;&gt; until it is acknowledged, then I think we&#39;re good.<br>
&gt;&gt;<br>
&gt;&gt; I agree that that would work.<br>
&gt;&gt;<br>
&gt;&gt; IIUC downsides compared to the implicit ACK approach are that the<=
br>
&gt;&gt; server needs to keep the old keys for certain amount of time (e.g.=
, 2<br>
&gt;&gt; MSL) and that the additional Handshake packet will consume about 3=
0<br>
&gt;&gt; octets of the 3 packet window that we have for the server&#39;s fi=
rst<br>
&gt;&gt; flights.<br>
&gt;&gt;<br>
&gt;&gt;&gt; I can see the appeal in saying that if you receive an ACK for =
1-RTT data<br>
&gt;&gt;&gt; then your Handshake packets must have been received. I can see=
 that<br>
&gt;&gt;&gt; working even, but you have to be careful. It&#39;s just a sign=
al that you can<br>
&gt;&gt;&gt; stop sending CRYPTO frames, not that you are done with the key=
s. You<br>
&gt;&gt;&gt; might<br>
&gt;&gt;&gt; need to send ACK again and you might still receive packets at =
that level.<br>
&gt;&gt;&gt; You could drop read keys and ACK only the old packets that you=
 did<br>
&gt;&gt;&gt; decrypt,<br>
&gt;&gt;&gt; but I suspect that it&#39;s better to authenticate any packet =
and ACK<br>
&gt;&gt;&gt; faithfully, which would be better for your peer&#39;s congesti=
on state.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; That also means that you probably need to have timers for clea=
ning up, to<br>
</div></div>&gt;&gt;&gt; avoid the pathological case where acknowledgments =
are sent indefinitely..<br>
<div><div class=3D"h5">&gt;&gt;<br>
&gt;&gt; I agree with your argument about congestion control.<br>
&gt;&gt;<br>
&gt;&gt; One way of acquiring correct congestion control information in the=
<br>
&gt;&gt; implicit ACK approach will be to send coalesced packets that combi=
nes<br>
&gt;&gt; a Handshake packet with a packet protected by a higher encryption =
key.<br>
&gt;&gt; That will guarantee that you would receive an ACK for the delivery=
 of<br>
&gt;&gt; the datagrams, and you can feed the information to the congestion<=
br>
&gt;&gt; controller.<br>
&gt;&gt;<br>
&gt;&gt; FWIW, I have implemented implicit ACK in quicly, and it only requi=
red<br>
&gt;&gt; about 40 additional lines of code, including the retransmission lo=
gic<br>
&gt;&gt; for Handshake_Done. The code can be found at<br>
&gt;&gt;<br>
&gt;&gt; <a href=3D"https://github.com/h2o/quicly/pull/8/commits/eee6eb5fc7=
c0359edfeb0b8f89ae9ac191ef0758" rel=3D"noreferrer" target=3D"_blank">https:=
//github.com/h2o/quicly/<wbr>pull/8/commits/<wbr>eee6eb5fc7c0359edfeb0b8f89=
ae9a<wbr>c191ef0758</a>.<br>
&gt;&gt; Coalesced packets is not implemented.<br>
&gt;&gt;<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt; I think that the FIN bit idea might work to close out the use =
of the<br>
&gt;&gt;&gt; &quot;stream&quot; for each set of keys. That is, as opposed t=
o the crypto stream<br>
&gt;&gt;&gt; as<br>
&gt;&gt;&gt; a whole. But it&#39;s duplicative: the crypto handshake needs =
to know when it<br>
&gt;&gt;&gt; moves from one set of keys to the next and replicating that si=
gnaling at<br>
&gt;&gt;&gt; the QUIC layer only really adds things to check for consistenc=
y.<br>
&gt;&gt;&gt; On Thu, May 24, 2018 at 11:07 AM Kazuho Oku &lt;<a href=3D"mai=
lto:kazuhooku@gmail.com">kazuhooku@gmail.com</a>&gt; wrote:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; 2018-05-24 3:46 GMT+09:00 Jana Iyengar &lt;<a href=3D"mail=
to:jri.ietf@gmail.com">jri.ietf@gmail.com</a>&gt;:<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; &gt; A thought occurs to me: a CRYPTO_HS frame with the fi=
n bit set can be<br>
&gt;&gt;&gt; used<br>
&gt;&gt;&gt;&gt; &gt; to indicate that the handshake is done.This could be =
used as a signal<br>
&gt;&gt;&gt; (aka<br>
&gt;&gt;&gt;&gt; &gt; HANDSHAKE_DONE) to solve Marten&#39;s problem of a cl=
ient rtxing a CFIN.<br>
&gt;&gt;&gt;&gt; &gt; Of<br>
&gt;&gt;&gt;&gt; &gt; course, this would mean that this particular CRYPTO_H=
S frame would be<br>
</div></div>&gt;&gt;&gt;&gt; &gt; encrypted with a 1-RTT key... which *I th=
ink* is fine. What do you<br>
<div class=3D"HOEnZb"><div class=3D"h5">&gt;&gt;&gt; think?<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; I am not sure if that is a good approach.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; I would assume that we would like to keep the handshake fl=
ow on the<br>
&gt;&gt;&gt;&gt; 1-RTT key open for the lifetime of the QUIC connection, so=
 that we<br>
&gt;&gt;&gt;&gt; could send things related to the TLS (e.g. session tickets=
). Sending<br>
&gt;&gt;&gt;&gt; FIN from the server right after receiving ClientFinished m=
akes that<br>
&gt;&gt;&gt;&gt; impossible.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Having said that, I do agree that the need for a dedicated=
 frame is a<br>
&gt;&gt;&gt;&gt; pain. It is a pain because we need to have a retransmissio=
n logic for<br>
&gt;&gt;&gt;&gt; the frame.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; I think that you are making a good point in suggesting to =
consider<br>
&gt;&gt;&gt;&gt; reusing the retransmission logic that already exists for b=
idirectional<br>
&gt;&gt;&gt;&gt; flows. But as said, FIN bit does not seem like an answer i=
n this case.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; IMO, ideally we should define a new TLS post-handshake mes=
sage (that<br>
&gt;&gt;&gt;&gt; does not convey any data), and send that from the server i=
n response<br>
&gt;&gt;&gt;&gt; to ClientFinished using 1-RTT packet. The message will act=
 as a signal<br>
&gt;&gt;&gt;&gt; that the server has received ClientFinished.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; The benefit of this approach is that we can reuse the retr=
ansmission<br>
&gt;&gt;&gt;&gt; logic that will exist for handshake flows. The downside is=
 that TLS<br>
&gt;&gt;&gt;&gt; stacks need to be aware of the new handshake message.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; Considering the fact that the Design Team is already sugge=
sting a<br>
&gt;&gt;&gt;&gt; substantial change to the TLS stack, we might have chance =
in asking<br>
&gt;&gt;&gt;&gt; for the addition of a new handshake message. But I am not =
sure.<br>
&gt;&gt;&gt;<br>
&gt;&gt;&gt;&gt; --<br>
&gt;&gt;&gt;&gt; Kazuho Oku<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; --<br>
&gt;&gt; Kazuho Oku<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; --<br>
&gt; Kazuho Oku<br>
&gt;<br>
<br>
<br>
<br>
</div></div><span class=3D"HOEnZb"><font color=3D"#888888">-- <br>
Kazuho Oku<br>
<br>
</font></span></blockquote></div><br></div></div>

--00000000000023ce01056d0812b7--


From nobody Fri May 25 10:46:15 2018
Return-Path: <Lucas.Pardue@bbc.co.uk>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D2BD412E3AE for <quic@ietfa.amsl.com>; Fri, 25 May 2018 10:46:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 6F7xM3jrWjb2 for <quic@ietfa.amsl.com>; Fri, 25 May 2018 10:46:11 -0700 (PDT)
Received: from mailout1.cwwtf.bbc.co.uk (mailout1.cwwtf.bbc.co.uk [132.185.160.180]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 64A77127241 for <quic@ietf.org>; Fri, 25 May 2018 10:46:11 -0700 (PDT)
Received: from BGB01XI1001.national.core.bbc.co.uk ([10.184.50.51]) by mailout1.cwwtf.bbc.co.uk (8.15.2/8.15.2) with ESMTP id w4PHk6Ub013719; Fri, 25 May 2018 18:46:06 +0100 (BST)
Received: from BGB01XUD1012.national.core.bbc.co.uk ([10.161.14.10]) by BGB01XI1001.national.core.bbc.co.uk ([10.184.50.51]) with mapi id 14.03.0361.001; Fri, 25 May 2018 18:46:05 +0100
From: Lucas Pardue <Lucas.Pardue@bbc.co.uk>
To: Martin Thomson <martin.thomson@gmail.com>, patrick mcmanus <pmcmanus@mozilla.com>
CC: QUIC WG <quic@ietf.org>, Mike Bishop <mbishop@evequefou.be>, "HTTP Working Group" <ietf-http-wg@w3.org>
Subject: RE: QPACK and the Static Table
Thread-Topic: QPACK and the Static Table
Thread-Index: AdPy6/ObcVQE/1QBQB2X+UF0Ytinwf//+Z2AgAAMh4CAAAKegIAAAO0AgAK4B0U=
Date: Fri, 25 May 2018 17:46:05 +0000
Message-ID: <7CF7F94CB496BF4FAB1676F375F9666A3BB3F89B@bgb01xud1012>
References: <SN1PR08MB1854395A2875541C4DC0673DDA6B0@SN1PR08MB1854.namprd08.prod.outlook.com> <CAOdDvNqsNmU5qahRk_p34gxvEFsZJS0f=xiLixGLSLuZM7pBwQ@mail.gmail.com> <CABkgnnVN1KO7XabhdiCY8-zfKU54_i22jhKDxyJyqo3Kt=c4KQ@mail.gmail.com> <CAOdDvNquN4M5HiWeS0wnLmpUEh=cQFsxjFcFWjxjTc5KGJfM7A@mail.gmail.com>, <CABkgnnVTsbRnp18Ub1p2PahX_b1Mh4jD+znZG3HODfebPPAvqw@mail.gmail.com>
In-Reply-To: <CABkgnnVTsbRnp18Ub1p2PahX_b1Mh4jD+znZG3HODfebPPAvqw@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [172.19.161.211]
x-exclaimer-md-config: 1cd3ac1c-62e5-43f2-8404-6b688271c769
x-tm-as-product-ver: SMEX-11.0.0.4255-8.200.1013-23868.000
x-tm-as-result: No--16.765600-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/FbFx9Z2SgsDREyKpjWYkXKxcUuo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 May 2018 17:46:14 -0000

If we assume that HTTP/QUIC will be bootstrapped by Alt-Svc on TCP, then a =
QPACK Alt-Svc entry is mainly about refreshing liveliness. So ":port" appea=
rs as a reasonable option to refresh to self, plus omission of the "ma" par=
ameter implies a freshness of 24 hours (RFC 7838). Anecdotally, I would exp=
ect the same Alt-Svc to be sent on every response.

However, I don't think that there is any Alt-Svc reasonable general value t=
hat can be picked. We've previously discussed the use of UDP port 443. Some=
 of that was punted to the applicability document (https://github.com/quicw=
g/ops-drafts/issues/26). The HTTP doc kind of skirts this by saying that an=
y port can be used.

Is there any danger in optimising for v1 when it is anticipated that QUIC w=
ill rev quickly?

To summarise, I think a simple Alt-Svc default could cause more harm than g=
ood.

Lucas
________________________________________
From: QUIC [quic-bounces@ietf.org] on behalf of Martin Thomson [martin.thom=
son@gmail.com]
Sent: 24 May 2018 01:50
To: patrick mcmanus
Cc: QUIC WG; Mike Bishop; HTTP Working Group
Subject: Re: QPACK and the Static Table

On Thu, May 24, 2018 at 10:46 AM Patrick McManus <pmcmanus@mozilla.com>
wrote:> iirc alt-svc requires a colon and a port (and an alpn) but not a
hostname. so quic=3D":443" would make sense.

Ahh, right, then carry on.  That's not the interesting case, but it is
certainly a good default.  I think that it's hq=3D":443";quic=3D1 or someth=
ing
like that though.



-----------------------------
http://www.bbc.co.uk
This e-mail (and any attachments) is confidential and
may contain personal views which are not the views of the BBC unless specif=
ically stated.
If you have received it in
error, please delete it from your system.
Do not use, copy or disclose the
information in any way nor act in reliance on it and notify the sender
immediately.
Please note that the BBC monitors e-mails
sent or received.
Further communication will signify your consent to
this.
-----------------------------


From nobody Fri May 25 15:51:02 2018
Return-Path: <jri.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 59C3212D7F4 for <quic@ietfa.amsl.com>; Fri, 25 May 2018 15:51:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.699
X-Spam-Level: 
X-Spam-Status: No, score=-2.699 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 7PtXt74frFj8 for <quic@ietfa.amsl.com>; Fri, 25 May 2018 15:50:58 -0700 (PDT)
Received: from mail-it0-x22f.google.com (mail-it0-x22f.google.com [IPv6:2607:f8b0:4001:c0b::22f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1646F127286 for <quic@ietf.org>; Fri, 25 May 2018 15:50:58 -0700 (PDT)
Received: by mail-it0-x22f.google.com with SMTP id c3-v6so8686645itj.4 for <quic@ietf.org>; Fri, 25 May 2018 15:50:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gFEUPdl3aTh61XNkzcedbBx2wd+io9Idt4d1CHN8LK4=; b=DOZ5NbuDFVLjIt7xhy9hyOqzc07X0TYuF9Bx7G10TJxuJpS+ucg76z1JrXePzdz3r1 Q0LJKtCbUnNSVSk26S9+n+fVyWqbq11Sd4piGvHmSZtcQmdEFBSqytkv1GF2KY+2cofb 2iTrNlKEATcbY/XcFLCJRE9FAtT68Hig1sV/IIyYLZ8lcTUx6IKPnuo8yYKw8/cI7DnD WxwJIR9EvuYy6cEwi9yDn6juyfTXX8KFRJVrsgVrxhegWmJe1xiiHVKNMzE62tSI/SVj U1lXKAC1ldKBr/rRYYzfenLTum0V5Tg12I9uo98QEM6HzvMXrDteZU6B9V8tDjp4W4yE lJjQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=gFEUPdl3aTh61XNkzcedbBx2wd+io9Idt4d1CHN8LK4=; b=FYZ9kotsnP5uDVbW1ymx9Wrf050jetODRsDgbfLFvzK5vNPqJjNKVOWkDuUYr0vvqs 1vqHXjiZtN2zQ6Eb6y+SFzBTM+1upkdjob95mH82T9hqsd8V+M28ViquAvk0gev0uEtx om6RuO0blZCy47f3UhM0DSlhfKSPJOTUsCxV7q3Tenb9fVdKX5aTAB8Ti6JKZG0A19D1 0Rna7bSuYKxRR4pWMrvr3mBY7/wB7y9KWe36dGG6fYUu2MDbD4titvEbmIGyrBeVlb5W d5iQ1opn5hw4PGzPBvx3+DtVh0XIiL3/87rkXVceblulPHm5GepUcxqjuPTVKonhFvCT jn2w==
X-Gm-Message-State: ALKqPwdVex9gY9uf9FqcalFsMvOxn8weAg/3d9XJCHzBOcAW6gVg1K/a avy4zM4BbooV7WhUAp9mw958WM17BCYwbN2LNSU=
X-Google-Smtp-Source: ADUXVKJSnFU14pVBf7061NW9JP2/QgqWylT5q4YV86vtRoANBQis/SztyONRxNMIZIQ1KMpFGYef1L64aD+jdsG5jM0=
X-Received: by 2002:a24:9c1:: with SMTP id 184-v6mr4143717itm.9.1527288657451;  Fri, 25 May 2018 15:50:57 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:2a46:0:0:0:0:0 with HTTP; Fri, 25 May 2018 15:50:56 -0700 (PDT)
In-Reply-To: <CABkgnnUAiztUw-kEr97bCX499eQL8wno11rRJQJD+49eBn6LXA@mail.gmail.com>
References: <CAOYVs2q63DpkPZTbw9T24ZcFOxbvrWAGvOtUaHvCuSg_13pSkQ@mail.gmail.com> <CABkgnnUAiztUw-kEr97bCX499eQL8wno11rRJQJD+49eBn6LXA@mail.gmail.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Fri, 25 May 2018 15:50:56 -0700
Message-ID: <CACpbDcezAWLC+4W8CezXnjyivWGV6ktR_XoCDnBT24MUKCg-PA@mail.gmail.com>
Subject: Re: Payload length 0
To: Martin Thomson <martin.thomson@gmail.com>
Cc: Marten Seemann <martenseemann@gmail.com>, QUIC WG <quic@ietf.org>,  "Eggert, Lars" <lars@netapp.com>
Content-Type: multipart/alternative; boundary="000000000000e59e68056d0f99c1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/-9xUdh_77VSqcQaeAKK6a_AVYf8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 25 May 2018 22:51:01 -0000

--000000000000e59e68056d0f99c1
Content-Type: text/plain; charset="UTF-8"

I'm fine with having 0 not be special. Marten and Lars had stronger
opinions, so they should speak up.

On Thu, May 24, 2018 at 9:06 PM, Martin Thomson <martin.thomson@gmail.com>
wrote:

> It seems like the discussion has settled down.
>
> For those advocating for 0 being special, are you happy to keep things as
> they are?
> On Fri, May 18, 2018 at 3:08 PM Marten Seemann <martenseemann@gmail.com>
> wrote:
>
> > Jana asked me to raise this issue on the list, after we already had a bit
> of discussion in https://github.com/quicwg/base-drafts/pull/1301.
>
> > The proposal is to make a payload length of 0 a special value, indicating
> that the packet is not a coalesced packet, i.e. that the whole payload of
> the UDP packet is the QUIC packet. This would eliminate an invalid value of
> the payload length (there are no empty packets), save one byte for packet
> lengths where varint encoding would result in a two byte number, and
> apparently also simplify (some) implementations.
>
> > Kazuho argued creating two versions of each Long Header type (one with
> and one without a payload length) is the better solution, since all values
> below the AEAD tag length + 1 are invalid values anyway, and it would save
> one more byte.
>
> > We should make a decision if and what we want to do about this.
>
>

--000000000000e59e68056d0f99c1
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;m fine with having 0 not be special. Marten and Lars=
 had stronger opinions, so they should speak up.</div><div class=3D"gmail_e=
xtra"><br><div class=3D"gmail_quote">On Thu, May 24, 2018 at 9:06 PM, Marti=
n Thomson <span dir=3D"ltr">&lt;<a href=3D"mailto:martin.thomson@gmail.com"=
 target=3D"_blank">martin.thomson@gmail.com</a>&gt;</span> wrote:<br><block=
quote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc=
 solid;padding-left:1ex">It seems like the discussion has settled down.<br>
<br>
For those advocating for 0 being special, are you happy to keep things as<b=
r>
they are?<br>
<span class=3D"im HOEnZb">On Fri, May 18, 2018 at 3:08 PM Marten Seemann &l=
t;<a href=3D"mailto:martenseemann@gmail.com">martenseemann@gmail.com</a>&gt=
;<br>
wrote:<br>
<br>
</span><div class=3D"HOEnZb"><div class=3D"h5">&gt; Jana asked me to raise =
this issue on the list, after we already had a bit<br>
of discussion in <a href=3D"https://github.com/quicwg/base-drafts/pull/1301=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/<wbr>base-=
drafts/pull/1301</a>.<br>
<br>
&gt; The proposal is to make a payload length of 0 a special value, indicat=
ing<br>
that the packet is not a coalesced packet, i.e. that the whole payload of<b=
r>
the UDP packet is the QUIC packet. This would eliminate an invalid value of=
<br>
the payload length (there are no empty packets), save one byte for packet<b=
r>
lengths where varint encoding would result in a two byte number, and<br>
apparently also simplify (some) implementations.<br>
<br>
&gt; Kazuho argued creating two versions of each Long Header type (one with=
<br>
and one without a payload length) is the better solution, since all values<=
br>
below the AEAD tag length + 1 are invalid values anyway, and it would save<=
br>
one more byte.<br>
<br>
&gt; We should make a decision if and what we want to do about this.<br>
<br>
</div></div></blockquote></div><br></div>

--000000000000e59e68056d0f99c1--


From nobody Fri May 25 17:20:37 2018
Return-Path: <martenseemann@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B6370127058 for <quic@ietfa.amsl.com>; Fri, 25 May 2018 17:20:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 y9Pde8qoedha for <quic@ietfa.amsl.com>; Fri, 25 May 2018 17:20:33 -0700 (PDT)
Received: from mail-io0-x22b.google.com (mail-io0-x22b.google.com [IPv6:2607:f8b0:4001:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 80A1D1267BB for <quic@ietf.org>; Fri, 25 May 2018 17:20:33 -0700 (PDT)
Received: by mail-io0-x22b.google.com with SMTP id y2-v6so2927350iob.11 for <quic@ietf.org>; Fri, 25 May 2018 17:20:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=cV3ran88uC9DMoP+Xhffy97WlPaMqXM+8gwYPAzAlzs=; b=IyE4y6XUwi1uVSvKj6eStsoQ87jcpTtFfAg8vUH7zqC4fPQ/722xd5BrDUjctNUfRz +if7i/WO0Y2+2XiCanfcy+wHrQDI3H0qGYlwlgx+lssFdohGJ0ky8pcRlDABg+gAvhh8 UOqd9s6DYkLUnWIcGFW/Uu5e8LHPdzqZlbyF2+B/hpNP1CsY681OViA2ovZhNAqptluM pGtu1C9YLaNdMoJY5z37vFCxWz2+/WUO156XYgTmiBHuPBdvW3Gtrb/j8iQSugJ8uvXb uZfUulhbXcvtqpf0FN70pjT9lBMh1ySZUKFZoiWpy0nTtR5ca6+9nT/rsIGQc9wjmC2A zagQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=cV3ran88uC9DMoP+Xhffy97WlPaMqXM+8gwYPAzAlzs=; b=Da63V37w8QhXQs2anO7QBkMkWwhw80SVnI2IHDwvciN8vcXe57j5iMkIT5MpnlRY81 QzE8+3IZ0I7DRvH2qf1NLf/GfylbuW2IgLeykBUaX/hKbF9EF4u3OlyoWY7DFqEX8pa7 XgjL0wMORZvOEPgSqLrL2wGwA2cGj75Lb5I8D+CPchrha3Ok4FDTXwutmNzlUFmqCde/ gkONUpfouqnCRBdWPaLujZ8JAiRvVSN/0s3KJ2NqI2QM/gQED2sNniml5ekGnJl92DOV s0n1zZVgjtoMJkyPTXCa1g97DUqupDgRteACmHL5uBz4HYNNPcVaaPnL1W3hI8B9QgZ2 Z7dw==
X-Gm-Message-State: ALKqPweqmKnAxrOvq3SS0peyNqXSZroHuiZHmd/pxzo74tNNqDYj88wb VfWLZN+t5qVS962Ubuc0JdO4ckqeL7aQMf59MEw=
X-Google-Smtp-Source: ADUXVKJHFXGBCGFFYH0g0GUuihVIWudtJX0bCrxWUzlTg5w0X32PL6/WBUvkbru7PtYWU5UwqTGaNSa8r8aV1ACY+FA=
X-Received: by 2002:a6b:b5c6:: with SMTP id e189-v6mr3880070iof.29.1527294032686;  Fri, 25 May 2018 17:20:32 -0700 (PDT)
MIME-Version: 1.0
References: <CAOYVs2q63DpkPZTbw9T24ZcFOxbvrWAGvOtUaHvCuSg_13pSkQ@mail.gmail.com> <CABkgnnUAiztUw-kEr97bCX499eQL8wno11rRJQJD+49eBn6LXA@mail.gmail.com> <CACpbDcezAWLC+4W8CezXnjyivWGV6ktR_XoCDnBT24MUKCg-PA@mail.gmail.com>
In-Reply-To: <CACpbDcezAWLC+4W8CezXnjyivWGV6ktR_XoCDnBT24MUKCg-PA@mail.gmail.com>
From: Marten Seemann <martenseemann@gmail.com>
Date: Sat, 26 May 2018 08:20:21 +0800
Message-ID: <CAOYVs2pcSC__ERAWzd8dwJ_4HXL_je1heftyQz6YCCSM6gQ_yQ@mail.gmail.com>
Subject: Re: Payload length 0
To: Jana Iyengar <jri.ietf@gmail.com>
Cc: "Eggert, Lars" <lars@netapp.com>, Martin Thomson <martin.thomson@gmail.com>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004939f6056d10dad6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/a862BgQWNfvH09Qoka0hGvbrczo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 May 2018 00:20:36 -0000

--0000000000004939f6056d10dad6
Content-Type: text/plain; charset="UTF-8"

Works for me.

On Sat 26. May 2018 at 06:50, Jana Iyengar <jri.ietf@gmail.com> wrote:

> I'm fine with having 0 not be special. Marten and Lars had stronger
> opinions, so they should speak up.
>
> On Thu, May 24, 2018 at 9:06 PM, Martin Thomson <martin.thomson@gmail.com>
> wrote:
>
>> It seems like the discussion has settled down.
>>
>> For those advocating for 0 being special, are you happy to keep things as
>> they are?
>> On Fri, May 18, 2018 at 3:08 PM Marten Seemann <martenseemann@gmail.com>
>> wrote:
>>
>> > Jana asked me to raise this issue on the list, after we already had a
>> bit
>> of discussion in https://github.com/quicwg/base-drafts/pull/1301.
>>
>> > The proposal is to make a payload length of 0 a special value,
>> indicating
>> that the packet is not a coalesced packet, i.e. that the whole payload of
>> the UDP packet is the QUIC packet. This would eliminate an invalid value
>> of
>> the payload length (there are no empty packets), save one byte for packet
>> lengths where varint encoding would result in a two byte number, and
>> apparently also simplify (some) implementations.
>>
>> > Kazuho argued creating two versions of each Long Header type (one with
>> and one without a payload length) is the better solution, since all values
>> below the AEAD tag length + 1 are invalid values anyway, and it would save
>> one more byte.
>>
>> > We should make a decision if and what we want to do about this.
>>
>>
>

--0000000000004939f6056d10dad6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div><div dir=3D"auto">Works for me.</div><br><div class=3D"gmail_quote"><d=
iv>On Sat 26. May 2018 at 06:50, Jana Iyengar &lt;<a href=3D"mailto:jri.iet=
f@gmail.com">jri.ietf@gmail.com</a>&gt; wrote:<br></div><blockquote class=
=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd=
ing-left:1ex"><div>I&#39;m fine with having 0 not be special. Marten and La=
rs had stronger opinions, so they should speak up.</div><div class=3D"gmail=
_extra"><br><div class=3D"gmail_quote">On Thu, May 24, 2018 at 9:06 PM, Mar=
tin Thomson <span>&lt;<a href=3D"mailto:martin.thomson@gmail.com" target=3D=
"_blank">martin.thomson@gmail.com</a>&gt;</span> wrote:<br><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex">It seems like the discussion has settled down.<br>
<br>
For those advocating for 0 being special, are you happy to keep things as<b=
r>
they are?<br>
<span class=3D"m_-5126186033742849739im m_-5126186033742849739HOEnZb">On Fr=
i, May 18, 2018 at 3:08 PM Marten Seemann &lt;<a href=3D"mailto:martenseema=
nn@gmail.com" target=3D"_blank">martenseemann@gmail.com</a>&gt;<br>
wrote:<br>
<br>
</span><div class=3D"m_-5126186033742849739HOEnZb"><div class=3D"m_-5126186=
033742849739h5">&gt; Jana asked me to raise this issue on the list, after w=
e already had a bit<br>
of discussion in <a href=3D"https://github.com/quicwg/base-drafts/pull/1301=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/1301</a>.<br>
<br>
&gt; The proposal is to make a payload length of 0 a special value, indicat=
ing<br>
that the packet is not a coalesced packet, i.e. that the whole payload of<b=
r>
the UDP packet is the QUIC packet. This would eliminate an invalid value of=
<br>
the payload length (there are no empty packets), save one byte for packet<b=
r>
lengths where varint encoding would result in a two byte number, and<br>
apparently also simplify (some) implementations.<br>
<br>
&gt; Kazuho argued creating two versions of each Long Header type (one with=
<br>
and one without a payload length) is the better solution, since all values<=
br>
below the AEAD tag length + 1 are invalid values anyway, and it would save<=
br>
one more byte.<br>
<br>
&gt; We should make a decision if and what we want to do about this.<br>
<br>
</div></div></blockquote></div><br></div>
</blockquote></div></div>

--0000000000004939f6056d10dad6--


From nobody Sat May 26 00:38:27 2018
Return-Path: <lars@netapp.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 64B89120724 for <quic@ietfa.amsl.com>; Sat, 26 May 2018 00:38:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.21
X-Spam-Level: 
X-Spam-Status: No, score=-4.21 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=netapp.onmicrosoft.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 FWNzpaui5CHd for <quic@ietfa.amsl.com>; Sat, 26 May 2018 00:38:23 -0700 (PDT)
Received: from mx144.netapp.com (mx144.netapp.com [IPv6:2620:10a:4005:8000:2306::d]) (using TLSv1.2 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A5C9212025C for <quic@ietf.org>; Sat, 26 May 2018 00:38:23 -0700 (PDT)
X-IronPort-AV: E=Sophos;i="5.49,443,1520924400";  d="asc'?scan'208";a="259681941"
Received: from vmwexchts04-prd.hq.netapp.com ([10.122.105.32]) by mx144-out.netapp.com with ESMTP; 26 May 2018 00:38:22 -0700
Received: from VMWEXCCAS06-PRD.hq.netapp.com (10.122.105.22) by VMWEXCHTS04-PRD.hq.netapp.com (10.122.105.32) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Sat, 26 May 2018 00:38:22 -0700
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (10.120.60.153) by VMWEXCCAS06-PRD.hq.netapp.com (10.122.105.22) with Microsoft SMTP Server (TLS) id 15.0.1320.4 via Frontend Transport; Sat, 26 May 2018 00:38:22 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=netapp.onmicrosoft.com; s=selector1-netapp-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=F3sfCZGChVcXdZtxMgc+aMXNsIYI4usXLc3RWwtkaL4=; b=e09w9K0HhT5Bwr0OzjDeU5Y4AEtT9GCsiQEwdxwX/WfBpnqiFdaoPVNaG4y69yHmXy/ss5GGUHCjdhGmTkwxSu4DYZgbvJZnLCNkcsaaFj6jrCkRPe7coft+c6EKIY2gtFT9syWKdUN4sEte0xLH46xKtfDXNSS7LkDZBF72Jtw=
Received: from BLUPR06MB1764.namprd06.prod.outlook.com (10.162.224.150) by BLUPR06MB1874.namprd06.prod.outlook.com (10.162.225.28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.797.11; Sat, 26 May 2018 07:38:19 +0000
Received: from BLUPR06MB1764.namprd06.prod.outlook.com ([fe80::fdfb:ef8b:4fae:590c]) by BLUPR06MB1764.namprd06.prod.outlook.com ([fe80::fdfb:ef8b:4fae:590c%4]) with mapi id 15.20.0797.015; Sat, 26 May 2018 07:38:19 +0000
From: "Eggert, Lars" <lars@netapp.com>
To: Marten Seemann <martenseemann@gmail.com>
CC: Janardhan Iyengar <jri.ietf@gmail.com>, Martin Thomson <martin.thomson@gmail.com>, QUIC WG <quic@ietf.org>
Subject: Re: Payload length 0
Thread-Topic: Payload length 0
Thread-Index: AQHT7mZLfA1S8PwR1UqMWwbQnUpKsKQ/3qAAgAE6QgCAABj7gIAAel0A
Date: Sat, 26 May 2018 07:38:19 +0000
Message-ID: <85B11F91-D4F1-4487-B2ED-6EA6DEF3297E@netapp.com>
References: <CAOYVs2q63DpkPZTbw9T24ZcFOxbvrWAGvOtUaHvCuSg_13pSkQ@mail.gmail.com> <CABkgnnUAiztUw-kEr97bCX499eQL8wno11rRJQJD+49eBn6LXA@mail.gmail.com> <CACpbDcezAWLC+4W8CezXnjyivWGV6ktR_XoCDnBT24MUKCg-PA@mail.gmail.com> <CAOYVs2pcSC__ERAWzd8dwJ_4HXL_je1heftyQz6YCCSM6gQ_yQ@mail.gmail.com>
In-Reply-To: <CAOYVs2pcSC__ERAWzd8dwJ_4HXL_je1heftyQz6YCCSM6gQ_yQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3445.6.18)
authentication-results: spf=none (sender IP is ) smtp.mailfrom=lars@netapp.com; 
x-originating-ip: [2001:a61:702:2a01:c873:92b3:67dd:8fee]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BLUPR06MB1874; 7:HNnreKiXnvBN5P7Bjj2E2DP6IaeaMd6L1zjFowP4uuMOaCSN7/bMkdnlW04hRYKDx69C7Il0niY9fB42MUEP/1hB36gSR0oEZ6AD82CCP6uUvt+0k7T98yv54/JQuFT1rZjhoIfvpkTeXBTPVrRL8zXhQRHmYg+/mjF86H7im2yz5xJra0m40iFFLGBfH2tWAFThomfzPpjDS4CknQSnJvkvkV7SPGr7cP1GnucXO8z7JJLnOC+rQ35nqRRLIq/8
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(49563074)(7193020); SRVR:BLUPR06MB1874; 
x-ms-traffictypediagnostic: BLUPR06MB1874:
x-microsoft-antispam-prvs: <BLUPR06MB18743E1DE97946A90E933C58A7680@BLUPR06MB1874.namprd06.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(166708455590820)(85827821059158);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(102415395)(6040522)(2401047)(8121501046)(5005006)(3231254)(944501410)(52105095)(93006095)(93001095)(3002001)(10201501046)(6055026)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123558120)(20161123562045)(20161123564045)(6072148)(201708071742011)(7699016); SRVR:BLUPR06MB1874; BCL:0; PCL:0; RULEID:; SRVR:BLUPR06MB1874; 
x-forefront-prvs: 0684F80A5C
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(396003)(39860400002)(376002)(346002)(366004)(39380400002)(52314003)(377424004)(199004)(189003)(83716003)(966005)(57306001)(46003)(6116002)(99286004)(53546011)(11346002)(8936002)(6506007)(105586002)(2900100001)(50226002)(5250100002)(2616005)(76176011)(486006)(476003)(54906003)(478600001)(82746002)(86362001)(316002)(25786009)(36756003)(4001150100001)(14454004)(229853002)(33656002)(39060400002)(561944003)(2906002)(106356001)(3660700001)(3280700002)(99936001)(7736002)(4326008)(6246003)(305945005)(97736004)(81156014)(81166006)(93886005)(8676002)(446003)(6512007)(6306002)(53936002)(186003)(5660300001)(7116003)(6916009)(1411001)(102836004)(6436002)(68736007)(6486002); DIR:OUT; SFP:1101; SCL:1; SRVR:BLUPR06MB1874; H:BLUPR06MB1764.namprd06.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: netapp.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: X2YlCLV0xdgB5cA7f0F9ulN6IY9ql9mROts0ddzpe6exTGNGQXLBsLhtTxDm5r9M7wq/zup8750mRFyOq+hnjqZh5QqF2S081Deh/pVitqXEB2yZJFlnr+mCtPjATIMqJyghXayJNu/32XwRwpl8q1j6+iWANkh5ozoWjoVY3C1HOzfmnX9IkSCiiIlmkQTj
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/signed; boundary="Apple-Mail=_C7E374BC-FF40-416A-AE50-499D45F20FC0"; protocol="application/pgp-signature"; micalg=pgp-sha512
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: e7478f7b-fe73-411f-c9a7-08d5c2dba709
X-MS-Exchange-CrossTenant-Network-Message-Id: e7478f7b-fe73-411f-c9a7-08d5c2dba709
X-MS-Exchange-CrossTenant-originalarrivaltime: 26 May 2018 07:38:19.7725 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 4b0911a0-929b-4715-944b-c03745165b3a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BLUPR06MB1874
X-OriginatorOrg: netapp.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/cyVgcNjKygVeN47BWL7LWcVTQTo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 26 May 2018 07:38:26 -0000

--Apple-Mail=_C7E374BC-FF40-416A-AE50-499D45F20FC0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

If we make the plen field fixed (which I think we just did to fix the =
issue with coalesced packets) I'm fine.

Lars

> On 2018-5-26, at 2:20, Marten Seemann <martenseemann@gmail.com> wrote:
>=20
> Works for me.
>=20
> On Sat 26. May 2018 at 06:50, Jana Iyengar <jri.ietf@gmail.com> wrote:
> I'm fine with having 0 not be special. Marten and Lars had stronger =
opinions, so they should speak up.
>=20
> On Thu, May 24, 2018 at 9:06 PM, Martin Thomson =
<martin.thomson@gmail.com> wrote:
> It seems like the discussion has settled down.
>=20
> For those advocating for 0 being special, are you happy to keep things =
as
> they are?
> On Fri, May 18, 2018 at 3:08 PM Marten Seemann =
<martenseemann@gmail.com>
> wrote:
>=20
> > Jana asked me to raise this issue on the list, after we already had =
a bit
> of discussion in https://github.com/quicwg/base-drafts/pull/1301.
>=20
> > The proposal is to make a payload length of 0 a special value, =
indicating
> that the packet is not a coalesced packet, i.e. that the whole payload =
of
> the UDP packet is the QUIC packet. This would eliminate an invalid =
value of
> the payload length (there are no empty packets), save one byte for =
packet
> lengths where varint encoding would result in a two byte number, and
> apparently also simplify (some) implementations.
>=20
> > Kazuho argued creating two versions of each Long Header type (one =
with
> and one without a payload length) is the better solution, since all =
values
> below the AEAD tag length + 1 are invalid values anyway, and it would =
save
> one more byte.
>=20
> > We should make a decision if and what we want to do about this.
>=20
>=20


--Apple-Mail=_C7E374BC-FF40-416A-AE50-499D45F20FC0
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment; filename="signature.asc"
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Message signed with OpenPGP

-----BEGIN PGP SIGNATURE-----

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAlsJDuoACgkQVLXDCb9w
wVdfPg/+IAnh8xVcYangT78sDiKG9sX1rvJh1MiPPBYWm1k8h58KgIfuSXyNNm0I
fs31a5AG4rXV91nwrS3TD9rv8yXiQxdyqYJ4ohYsuj2DXYSXz0CQE6jz2B5KizKY
34Zz+AqzH+bNjThTek01thtLfSz8Ur6ywGGW3LkskckTcvpUzXkF1wBw9paKcfqH
msRon/SrM160FSVvz5XWwiahh8bAAHEEBvLxo0pqkmRlqBNQ8mBU9/shg7eW5nN3
LqhJzsibnBPEg4+XdYy+XEkzoXE0qCKD3yx26YYmDCw9DKpUyqF0ExVJcSjxU+qn
1h7PlJgcSAgY5UjJY8GC+9VBapXtJJEp+4tgV4I6+v6q2PJzOK/ORCFmzg+0ina4
RGgZF3/mNtQGXxS+7JXki3WBwzvE3Y6933hzYN5hLbZld/+EsBphZ3P1wm1RavBa
zRMOXIg8XCETC/uoLqpDQrM3duo8ZMUXc+t1yDwP/4H8LmzFpwF3cWr4X3LARyH0
1DEVj0MWON1eAPEcyQVZyy8tlaWnUbGDnKstpCjcQ0/hzKjki3FWRUl/6xsEe0TZ
O0ftCQWw1QBzLMb8O1KAZFWAz7f8wuaBcpqwV9TNtSnfiXQadSIkh32V8w4LQHz1
FcH/MhJs62s6PMTSs8PpKxHiLMbbUECofnYOWvRMIDydaLHN5Mc=
=7Voq
-----END PGP SIGNATURE-----

--Apple-Mail=_C7E374BC-FF40-416A-AE50-499D45F20FC0--


From nobody Sat May 26 17:45:28 2018
Return-Path: <do_not_reply@mnot.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1AE1612EA8E for <quic@ietfa.amsl.com>; Sat, 26 May 2018 17:45:27 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=x5bzgHMU; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=BQUga9w6
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 pySXFn7aNHEs for <quic@ietfa.amsl.com>; Sat, 26 May 2018 17:45:23 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 76A59128959 for <quic@ietf.org>; Sat, 26 May 2018 17:45:23 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id DD3E920FD4 for <quic@ietf.org>; Sat, 26 May 2018 20:45:22 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sat, 26 May 2018 20:45:22 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:date:from:message-id:mime-version:subject:to :x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=TscWAPy7cCWAk/ruD AT5K9hxtqGoVCdj0Dbf7quLYko=; b=x5bzgHMUzBeEdOeVJGYdyZqWOqaisH7eS 6IFdpsHsISzAhDPOrGywJyKz812Tr4sNAyrHvv+rTFwgbhA1vCGc3ualke4qoOzr T6+b4MVW7hrsAj+m+zy+WiQLRV9GSSJ+SzuBIICt7ZzKZ7XZXg+DS1dlF+tlhZwj ySYLS7sO/6NT46r5+rJwksFUk5JOOcMJjF7gmHLV+u73D7nI11CCdftatoRNYUgV g7XZpNUwMjge579qSqe2/YbdxmNQlkOSmcvGKaMmBQZPysEOjy8yc4SloFbG0dWE gNaq6wSK3LzHww34YQXkwZM4vRk38Z5b4in0eSrlSVROXL+aedByw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=TscWAPy7cCWAk/ruDAT5K9hxtqGoVCdj0Dbf7quLYko=; b=BQUga9w6 yYwLp8QFW7nurlTFjTbtNufkmOsml2ZcXUTrWIbtmNXHtLLLQ24j0x9wd//Q0gk/ I4lnLFUQreViNW0aBgmmQfEjZl3oQQAvA4d0sD3wd3bxpsOhlGXPVMP+gOYuVPqU V9b0pFHJl/TCioMMOwnMFTytmuOyl7cSK+Jl107ny/Ru7lS7dWFscC3oUufwvhDG ttFYCN9KroNCJTVqSgAF3yihrTGW9KZ2t1zTM7Cigc9/tj4cVXK6eRAP0de5OrE1 n86U6l6DNNopMZTn6hP899W/3dlR/LXAOw8/Nps+oxiIc57vneZc2zkHSWUAifxi NsF3OC2XG3gIxA==
X-ME-Proxy: <xmx:ov8JW2eiBc7ia4iIbjfRdU_9aUHgx4jip7J1S-vMvQAfdfdI-8n-nQ>
X-ME-Proxy: <xmx:ov8JW1umoXncaLeXxxs5jJujbH46n4JlHHTX3QF3ntjGQFMpEL2xDg>
X-ME-Proxy: <xmx:ov8JW6MAsGUuKZMti6ZSx0bz2ld1p2Di_tTzMa_iWVmLLqvus9nM3g>
X-ME-Proxy: <xmx:ov8JWxU39Vzpu4YVZ4g6Pxg_xRACHmB0KU1vVJjRf0f_iRI8um6oFA>
X-ME-Proxy: <xmx:ov8JW9WHz93sFFbT257DgfU88lwpVU4NHycztO1Ke9GsVlLx57bG1w>
X-ME-Proxy: <xmx:ov8JW87qClPpEpaj_SnjXfcCqvuzcKO-_O6Oa6KzBkmRApvqCwNmfQ>
X-ME-Sender: <xms:ov8JW0euBhcjZPUlMPauDszNz3eGxzFjW5SHa78Ti6g7hQO4CjuPYA>
Received: from cloud.mnot.net (cloud.mnot.net [119.9.43.241]) by mail.messagingengine.com (Postfix) with ESMTPA id D36BBE4412 for <quic@ietf.org>; Sat, 26 May 2018 20:45:21 -0400 (EDT)
Received: from cloud.mnot.net (localhost [127.0.0.1]) by cloud.mnot.net (Postfix) with ESMTP id 3C28DC03AE for <quic@ietf.org>; Sun, 27 May 2018 00:45:19 +0000 (UTC)
Content-Type: multipart/alternative; boundary="===============4962897920316989364=="
MIME-Version: 1.0
From: =?utf-8?q?Github_Notifications?= <do_not_reply@mnot.net>
To: quic@ietf.org
Subject: Weekly github digest (QUIC Working Group Specifications)
Message-Id: <20180527004519.3C28DC03AE@cloud.mnot.net>
Date: Sun, 27 May 2018 00:45:19 +0000 (UTC)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/bfwcxRGDeKx40aDqF-O3Si_iAl4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sun, 27 May 2018 00:45:27 -0000

--===============4962897920316989364==
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="utf-8"; format="flowed"




Events without label "editorial"

Issues
------
* quicwg/base-drafts (+10/-2/=F0=9F=92=AC20)
  10 issues created:
  - No generic error codes (by martinthomson)
    https://github.com/quicwg/base-drafts/issues/1391 [-http] [design] =

  - Sec 4.2 refers to "Short Packet Type" field (by lumisota)
    https://github.com/quicwg/base-drafts/issues/1390 =

  - Flags in HTTP/QUIC frames are wasted space (by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1388 [-http] [design] =

  - 5.6 Packet Number Protection is hard to follow (by tatsuhiro-t)
    https://github.com/quicwg/base-drafts/issues/1387 =

  - Stateless reset oracle defense (by martinthomson)
    https://github.com/quicwg/base-drafts/issues/1386 [-transport] [design] =

  - Alarm vs. timeout (by rpaulo)
    https://github.com/quicwg/base-drafts/issues/1383 =

  - placement of change log and acknowledgements (by reschke)
    https://github.com/quicwg/base-drafts/issues/1381 =

  - Editorial comments (by janaiyengar)
    https://github.com/quicwg/base-drafts/issues/1376 [-transport] =

  - Tracking of header blocks for reset streams (by martinthomson)
    https://github.com/quicwg/base-drafts/issues/1371 [-qpack] [design] =

  - Implicitly acknowledging table updates by acknowleding header blocks (b=
y martinthomson)
    https://github.com/quicwg/base-drafts/issues/1370 [-qpack] [design] =


  8 issues received 20 new comments:
  - #1362 Swap largest reference and base indices (5 by afrind, MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1362 [-qpack] [design] =

  - #1370 Implicitly acknowledging table updates by acknowleding header blo=
cks (4 by martinthomson, afrind, MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1370 [-qpack] [design] =

  - #1365 Table resize can't be acknowledged (3 by afrind, MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1365 [-qpack] [design] =

  - #1371 Tracking of header blocks for reset streams (3 by martinthomson, =
afrind, MikeBishop)
    https://github.com/quicwg/base-drafts/issues/1371 [-qpack] [design] =

  - #1386 Stateless reset oracle defense (2 by martinthomson, mikkelfj)
    https://github.com/quicwg/base-drafts/issues/1386 [-transport] [design] =

  - #1383 Alarm vs. timeout (1 by janaiyengar)
    https://github.com/quicwg/base-drafts/issues/1383 =

  - #1387 5.6 Packet Number Protection is hard to follow (1 by tatsuhiro-t)
    https://github.com/quicwg/base-drafts/issues/1387 =

  - #1388 Flags in HTTP/QUIC frames are wasted space (1 by martinthomson)
    https://github.com/quicwg/base-drafts/issues/1388 [-http] [design] =


  2 issues closed:
  - Stateless Reset from clients https://github.com/quicwg/base-drafts/issu=
es/466 [-transport] [design] =

  - Handshake guarantees/compromises https://github.com/quicwg/base-drafts/=
issues/645 [-transport] [arch] [design] [editor-ready] =




Pull requests
-------------
* quicwg/base-drafts (+9/-7/=F0=9F=92=AC6)
  9 pull requests submitted:
  - Reorder appendices (by MikeBishop)
    https://github.com/quicwg/base-drafts/pull/1385 =

  - This is what you get from reading Python docs (by martinthomson)
    https://github.com/quicwg/base-drafts/pull/1380 =

  - Use tilde instead of backticks, again (by martinthomson)
    https://github.com/quicwg/base-drafts/pull/1379 =

  - Explain what packet protection means (by martinthomson)
    https://github.com/quicwg/base-drafts/pull/1378 =

  - Stream0 dt output ready (by ekr)
    https://github.com/quicwg/base-drafts/pull/1377 =

  - Disable gh-pages build when building tags (by martinthomson)
    https://github.com/quicwg/base-drafts/pull/1374 =

  - transport: add preferred_address to IANA registry (by alagoutte)
    https://github.com/quicwg/base-drafts/pull/1373 =

  - Proposal for adding ECN support to QUIC. (by gloinul)
    https://github.com/quicwg/base-drafts/pull/1372 =

  - Update draft-ietf-quic-transport.md (by gloinul)
    https://github.com/quicwg/base-drafts/pull/1367 =


  4 pull requests received 6 new comments:
  - #1303 Remove term "application-owned streams" (3 by martinthomson, LPar=
due, MikeBishop)
    https://github.com/quicwg/base-drafts/pull/1303 =

  - #1346 Stateless reset fixes (1 by martinthomson)
    https://github.com/quicwg/base-drafts/pull/1346 [-transport] =

  - #1379 Use tilde instead of backticks, again (1 by MikeBishop)
    https://github.com/quicwg/base-drafts/pull/1379 =

  - #1372 Proposal for adding ECN support to QUIC. (1 by IngJohEricsson)
    https://github.com/quicwg/base-drafts/pull/1372 =


  7 pull requests merged:
  - Stateless reset fixes
    https://github.com/quicwg/base-drafts/pull/1346 [-transport] =

  - Reorder appendices
    https://github.com/quicwg/base-drafts/pull/1385 =

  - Write down spoofed packet guarantees
    https://github.com/quicwg/base-drafts/pull/1347 =

  - This is what you get from reading Python docs
    https://github.com/quicwg/base-drafts/pull/1380 =

  - Disable gh-pages build when building tags
    https://github.com/quicwg/base-drafts/pull/1374 =

  - transport: add preferred_address to IANA registry
    https://github.com/quicwg/base-drafts/pull/1373 =

  - Update draft-ietf-quic-transport.md
    https://github.com/quicwg/base-drafts/pull/1367 =



Repositories tracked by this digest:
-----------------------------------
* https://github.com/quicwg/base-drafts

--===============4962897920316989364==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (QUIC Working Group Specifications)</title>
<style>
body { font-family: Gotham, "Helvetica Neue", Helvetica, Arial, sans-serif;=
 font-size: 14px; }
h2 { margin-top: 3em; color: #A52A2A; font-style: italic; font-weight: norm=
al; }
h3 { margin-bottom:0; margin-top: 2em; font-size: 1.2em; }
h1+h2 { margin-top: 1em; }
a { color: #bb6219; text-decoration: none; }
li { margin-bottom: .35em; }
.repos { margin-bottom: 0; margin-top:0; line-height: 1.2; }
.new { color: red; }
.label { display: inline;
	padding: .2em .6em .3em;
	font-size: 75%;
	font-weight: 700;
	line-height: 1;
	color: #fff;
	text-align: center;
	white-space: nowrap;
	vertical-align: baseline;
	border-radius: .25em;
}
</style>
</head>

<body>
<h1>Sunday May 27, 2018</h1>

<p>Events without label "editorial"</p>

<h2>Issues</h2>

<h3>quicwg/base-drafts (+10/-2/=F0=9F=92=AC20)</h3>
  <p class=3D"new">10 issues created:</p>
  <ul>
  <li>#1391 <a href=3D"https://github.com/quicwg/base-drafts/issues/1391">N=
o generic error codes</a> (by martinthomson) <span class=3D"label" style=3D=
"background-color: #fbca04; color: #000000">-http</span> <span class=3D"lab=
el" style=3D"background-color: #1d76db; color: #ffffff">design</span> </li>
  =

  <li>#1390 <a href=3D"https://github.com/quicwg/base-drafts/issues/1390">S=
ec 4.2 refers to &quot;Short Packet Type&quot; field</a> (by lumisota) </li>
  =

  <li>#1388 <a href=3D"https://github.com/quicwg/base-drafts/issues/1388">F=
lags in HTTP/QUIC frames are wasted space</a> (by MikeBishop) <span class=
=3D"label" style=3D"background-color: #fbca04; color: #000000">-http</span>=
 <span class=3D"label" style=3D"background-color: #1d76db; color: #ffffff">=
design</span> </li>
  =

  <li>#1387 <a href=3D"https://github.com/quicwg/base-drafts/issues/1387">5=
.6 Packet Number Protection is hard to follow</a> (by tatsuhiro-t) </li>
  =

  <li>#1386 <a href=3D"https://github.com/quicwg/base-drafts/issues/1386">S=
tateless reset oracle defense</a> (by martinthomson) <span class=3D"label" =
style=3D"background-color: #fbca04; color: #000000">-transport</span> <span=
 class=3D"label" style=3D"background-color: #1d76db; color: #ffffff">design=
</span> </li>
  =

  <li>#1383 <a href=3D"https://github.com/quicwg/base-drafts/issues/1383">A=
larm vs. timeout</a> (by rpaulo) </li>
  =

  <li>#1381 <a href=3D"https://github.com/quicwg/base-drafts/issues/1381">p=
lacement of change log and acknowledgements</a> (by reschke) </li>
  =

  <li>#1376 <a href=3D"https://github.com/quicwg/base-drafts/issues/1376">E=
ditorial comments</a> (by janaiyengar) <span class=3D"label" style=3D"backg=
round-color: #fbca04; color: #000000">-transport</span> </li>
  =

  <li>#1371 <a href=3D"https://github.com/quicwg/base-drafts/issues/1371">T=
racking of header blocks for reset streams</a> (by martinthomson) <span cla=
ss=3D"label" style=3D"background-color: #fbca04; color: #000000">-qpack</sp=
an> <span class=3D"label" style=3D"background-color: #1d76db; color: #fffff=
f">design</span> </li>
  =

  <li>#1370 <a href=3D"https://github.com/quicwg/base-drafts/issues/1370">I=
mplicitly acknowledging table updates by acknowleding header blocks</a> (by=
 martinthomson) <span class=3D"label" style=3D"background-color: #fbca04; c=
olor: #000000">-qpack</span> <span class=3D"label" style=3D"background-colo=
r: #1d76db; color: #ffffff">design</span> </li>
  </ul>

  <p>8 issues received 20 new comments:</p>
  <ul>
  <li>#1362 <a href=3D"https://github.com/quicwg/base-drafts/issues/1362">S=
wap largest reference and base indices</a> (5 by afrind, MikeBishop) <span =
class=3D"label" style=3D"background-color: #fbca04; color: #000000">-qpack<=
/span> <span class=3D"label" style=3D"background-color: #1d76db; color: #ff=
ffff">design</span> </li>
  =

  <li>#1370 <a href=3D"https://github.com/quicwg/base-drafts/issues/1370">I=
mplicitly acknowledging table updates by acknowleding header blocks</a> (4 =
by martinthomson, afrind, MikeBishop) <span class=3D"label" style=3D"backgr=
ound-color: #fbca04; color: #000000">-qpack</span> <span class=3D"label" st=
yle=3D"background-color: #1d76db; color: #ffffff">design</span> </li>
  =

  <li>#1365 <a href=3D"https://github.com/quicwg/base-drafts/issues/1365">T=
able resize can&#x27;t be acknowledged</a> (3 by afrind, MikeBishop) <span =
class=3D"label" style=3D"background-color: #fbca04; color: #000000">-qpack<=
/span> <span class=3D"label" style=3D"background-color: #1d76db; color: #ff=
ffff">design</span> </li>
  =

  <li>#1371 <a href=3D"https://github.com/quicwg/base-drafts/issues/1371">T=
racking of header blocks for reset streams</a> (3 by martinthomson, afrind,=
 MikeBishop) <span class=3D"label" style=3D"background-color: #fbca04; colo=
r: #000000">-qpack</span> <span class=3D"label" style=3D"background-color: =
#1d76db; color: #ffffff">design</span> </li>
  =

  <li>#1386 <a href=3D"https://github.com/quicwg/base-drafts/issues/1386">S=
tateless reset oracle defense</a> (2 by martinthomson, mikkelfj) <span clas=
s=3D"label" style=3D"background-color: #fbca04; color: #000000">-transport<=
/span> <span class=3D"label" style=3D"background-color: #1d76db; color: #ff=
ffff">design</span> </li>
  =

  <li>#1383 <a href=3D"https://github.com/quicwg/base-drafts/issues/1383">A=
larm vs. timeout</a> (1 by janaiyengar) </li>
  =

  <li>#1387 <a href=3D"https://github.com/quicwg/base-drafts/issues/1387">5=
.6 Packet Number Protection is hard to follow</a> (1 by tatsuhiro-t) </li>
  =

  <li>#1388 <a href=3D"https://github.com/quicwg/base-drafts/issues/1388">F=
lags in HTTP/QUIC frames are wasted space</a> (1 by martinthomson) <span cl=
ass=3D"label" style=3D"background-color: #fbca04; color: #000000">-http</sp=
an> <span class=3D"label" style=3D"background-color: #1d76db; color: #fffff=
f">design</span> </li>
  </ul>

  <p>2 issues closed:</p>
  <ul>
  <li>#466 <a href=3D"https://github.com/quicwg/base-drafts/issues/466">Sta=
teless Reset from clients</a> <span class=3D"label" style=3D"background-col=
or: #fbca04; color: #000000">-transport</span> <span class=3D"label" style=
=3D"background-color: #1d76db; color: #ffffff">design</span> </li>
  =

  <li>#645 <a href=3D"https://github.com/quicwg/base-drafts/issues/645">Han=
dshake guarantees/compromises</a> <span class=3D"label" style=3D"background=
-color: #fbca04; color: #000000">-transport</span> <span class=3D"label" st=
yle=3D"background-color: #b60205; color: #ffffff">arch</span> <span class=
=3D"label" style=3D"background-color: #1d76db; color: #ffffff">design</span=
> <span class=3D"label" style=3D"background-color: #0e8a16; color: #ffffff"=
>editor-ready</span> </li>
  </ul>



<h2>Pull requests</h2>
<h3>quicwg/base-drafts (+9/-7/=F0=9F=92=AC6)</h3>
  <p class=3D"new">9 pull requests submitted:</p>
  <ul>
  <li>#1385 <a href=3D"https://github.com/quicwg/base-drafts/pull/1385">Reo=
rder appendices</a> (by MikeBishop) </li>
  =

  <li>#1380 <a href=3D"https://github.com/quicwg/base-drafts/pull/1380">Thi=
s is what you get from reading Python docs</a> (by martinthomson) </li>
  =

  <li>#1379 <a href=3D"https://github.com/quicwg/base-drafts/pull/1379">Use=
 tilde instead of backticks, again</a> (by martinthomson) </li>
  =

  <li>#1378 <a href=3D"https://github.com/quicwg/base-drafts/pull/1378">Exp=
lain what packet protection means</a> (by martinthomson) </li>
  =

  <li>#1377 <a href=3D"https://github.com/quicwg/base-drafts/pull/1377">Str=
eam0 dt output ready</a> (by ekr) </li>
  =

  <li>#1374 <a href=3D"https://github.com/quicwg/base-drafts/pull/1374">Dis=
able gh-pages build when building tags</a> (by martinthomson) </li>
  =

  <li>#1373 <a href=3D"https://github.com/quicwg/base-drafts/pull/1373">tra=
nsport: add preferred_address to IANA registry</a> (by alagoutte) </li>
  =

  <li>#1372 <a href=3D"https://github.com/quicwg/base-drafts/pull/1372">Pro=
posal for adding ECN support to QUIC.</a> (by gloinul) </li>
  =

  <li>#1367 <a href=3D"https://github.com/quicwg/base-drafts/pull/1367">Upd=
ate draft-ietf-quic-transport.md</a> (by gloinul) </li>
  </ul>

  <p>4 pull requests received 6 new comments:</p>
  <ul>
  <li>#1303 <a href=3D"https://github.com/quicwg/base-drafts/pull/1303">Rem=
ove term &quot;application-owned streams&quot;</a> (3 by martinthomson, LPa=
rdue, MikeBishop) </li>
  =

  <li>#1346 <a href=3D"https://github.com/quicwg/base-drafts/pull/1346">Sta=
teless reset fixes</a> (1 by martinthomson) <span class=3D"label" style=3D"=
background-color: #fbca04; color: #000000">-transport</span> </li>
  =

  <li>#1379 <a href=3D"https://github.com/quicwg/base-drafts/pull/1379">Use=
 tilde instead of backticks, again</a> (1 by MikeBishop) </li>
  =

  <li>#1372 <a href=3D"https://github.com/quicwg/base-drafts/pull/1372">Pro=
posal for adding ECN support to QUIC.</a> (1 by IngJohEricsson) </li>
  </ul>

  <p>7 pull requests merged:</p>
  <ul>
  <li>#1346 <a href=3D"https://github.com/quicwg/base-drafts/pull/1346">Sta=
teless reset fixes</a> <span class=3D"label" style=3D"background-color: #fb=
ca04; color: #">-transport</span> </li>
  =

  <li>#1385 <a href=3D"https://github.com/quicwg/base-drafts/pull/1385">Reo=
rder appendices</a> </li>
  =

  <li>#1347 <a href=3D"https://github.com/quicwg/base-drafts/pull/1347">Wri=
te down spoofed packet guarantees</a> </li>
  =

  <li>#1380 <a href=3D"https://github.com/quicwg/base-drafts/pull/1380">Thi=
s is what you get from reading Python docs</a> </li>
  =

  <li>#1374 <a href=3D"https://github.com/quicwg/base-drafts/pull/1374">Dis=
able gh-pages build when building tags</a> </li>
  =

  <li>#1373 <a href=3D"https://github.com/quicwg/base-drafts/pull/1373">tra=
nsport: add preferred_address to IANA registry</a> </li>
  =

  <li>#1367 <a href=3D"https://github.com/quicwg/base-drafts/pull/1367">Upd=
ate draft-ietf-quic-transport.md</a> </li>
  </ul>


<h2>Repositories tracked by this digest:</h2>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/quicwg/base-drafts">https://github.com/=
quicwg/base-drafts</a></li>
  </ul>
</body>
</html>

--===============4962897920316989364==--


From nobody Mon May 28 13:30:14 2018
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7C18912E8DE for <quic@ietfa.amsl.com>; Mon, 28 May 2018 13:30:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.311
X-Spam-Level: 
X-Spam-Status: No, score=-4.311 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ericsson.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 6uLSdpgJB4Yf for <quic@ietfa.amsl.com>; Mon, 28 May 2018 13:30:00 -0700 (PDT)
Received: from sessmg22.ericsson.net (sessmg22.ericsson.net [193.180.251.58]) (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 99B5412E8A6 for <quic@ietf.org>; Mon, 28 May 2018 13:29:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=ericsson.com; s=mailgw201801; c=relaxed/simple; q=dns/txt; i=@ericsson.com; t=1527539395; h=From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date:Resent-From: Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To:References:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=kGwNYul40TwUuSWav/wsLIr+5b6/MdywMrWDSSOPaXE=; b=J4vurdUPYc80g9s5JNyx+gAcDab2fTIm/EZQvjpB9+JQuvjQNBr8h1nG/rvzK0Mw fxBi9q17kAsXJd03AD8UVgsbkj+pxy3qhGFvsPlHAQFNMvd++pRBGJDvK4PL6+TR Z34TmooM2yF0CSlMAL+8k4unHHJm0py32WTVMagJ1QE=;
X-AuditID: c1b4fb3a-b3bff700000034a5-f0-5b0c66c39ae5
Received: from ESESSHC019.ericsson.se (Unknown_Domain [153.88.183.75]) by sessmg22.ericsson.net (Symantec Mail Security) with SMTP id FF.51.13477.3C66C0B5; Mon, 28 May 2018 22:29:55 +0200 (CEST)
Received: from [100.94.46.175] (153.88.183.153) by smtps.internal.ericsson.com (153.88.183.75) with Microsoft SMTP Server (TLS) id 14.3.382.0; Mon, 28 May 2018 22:29:55 +0200
To: IETF QUIC WG <quic@ietf.org>
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
Subject: Adding ECN to Transport and Recovery
Message-ID: <26584f2a-230b-c55e-db16-d32225c8ee4d@ericsson.com>
Date: Mon, 28 May 2018 22:29:54 +0200
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
Content-Type: text/plain; charset="windows-1252"; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
X-Originating-IP: [153.88.183.153]
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFlrGLMWRmVeSWpSXmKPExsUyM2K7t+7hNJ5og6sTrC16FnA7MHosWfKT KYAxissmJTUnsyy1SN8ugSvjw6MPbAUzOSo2fTrL2sD4jK2LkZNDQsBEYm3LZtYuRi4OIYEj jBIPjxxjgnA2MUrsvn4VqIqDQ0RAQWJNAydIA5uAhcTNH41gzcICuhJ/emYwgpTwCthLvD7v AxJmEVCVeNe8nB3EFhWIkVi98TKYzSsgKHFy5hMWkHJmoPIHW8tAwswC8hLb385hhrDFJZq+ rGQFsYUEtCUamjpYIc5Ukrg+7zrLBEb+WUgmzUKYNAvJpFlIJi1gZFnFKFqcWlycm25kpJda lJlcXJyfp5eXWrKJERh6B7f8ttrBePC54yFGAQ5GJR7eT/480UKsiWXFlbmHGCU4mJVEeLl0 uaKFeFMSK6tSi/Lji0pzUosPMUpzsCiJ8zqlWUQJCaQnlqRmp6YWpBbBZJk4OKUaGBnvBZ54 7RnJ4pHR9PDTWjHlBNV/UYlWHDP1Dp7LKBA/8rGn5+ETSZEnS86W5YZsnMX22qqhSa2izMj4 b/6+tWWLXWYwSn3sfLPFed3VoP+lbdLnGnmrXRyu/3vc4j/xc35AxO7HncXS9f8rMx09GpQL 7gXrOJg4fS2y9XaV2bMy6Fu/V/ACJZbijERDLeai4kQAJYQ+JTkCAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/u1i9fYiflThEsGJbVYhyQ6da7aA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 May 2018 20:30:13 -0000

WG,

I have been working on a Pull Request 
(https://github.com/quicwg/base-drafts/pull/1372) that implements the 
ECN proposal from the design team 
(https://github.com/quicwg/base-drafts/wiki/ECN-in-QUIC) into something 
reasonably well integrated into the current drafts. Thus, I think it is 
time that people review and consider this proposal so that any issues 
can be addressed.

I would very much like to present at the interim this proposal, some of 
the choices made, and determine if there are additional changes to be 
made before merging this.

Cheers

Magnus Westerlund

----------------------------------------------------------------------
Network Architecture & Protocols, Ericsson Research
----------------------------------------------------------------------
Ericsson AB                 | Phone  +46 10 7148287
Torshamnsgatan 23           | Mobile +46 73 0949079
SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
----------------------------------------------------------------------


From nobody Tue May 29 07:40:07 2018
Return-Path: <ekr@rtfm.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C87A712E957 for <quic@ietfa.amsl.com>; Tue, 29 May 2018 07:40:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.608
X-Spam-Level: 
X-Spam-Status: No, score=-2.608 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=rtfm-com.20150623.gappssmtp.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 J8WGiCcLxNkl for <quic@ietfa.amsl.com>; Tue, 29 May 2018 07:40:02 -0700 (PDT)
Received: from mail-oi0-x22a.google.com (mail-oi0-x22a.google.com [IPv6:2607:f8b0:4003:c06::22a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8810F12E899 for <quic@ietf.org>; Tue, 29 May 2018 07:40:02 -0700 (PDT)
Received: by mail-oi0-x22a.google.com with SMTP id 14-v6so5234852oie.3 for <quic@ietf.org>; Tue, 29 May 2018 07:40:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=qgXCrrfgyjX1bH7A4ba9Sn/6QJCN7we54xLKFE/rYro=; b=tba7yFO9r8EeyG3DkjGtJWKyZTEDCmw/9qy2HEIqIxeb79JYcEKXlxX14WHifxondQ 9z4LS80w8efisqus+PYeDavO1JunaxnWGm4u41H3ZkvwA5rpODx2jmEXFobQLvoshpZv 5t6B814obgqMKS2Ltt7i1aP0AGRYw+AX0KuIRA+p8ew8lilU3qY7ifTDN1/HpDPU2YNI wgZht4zHxkk7RSvOA0py8pquyUHSnmIZ/a1TiObLTAq3Ap+58CQtO5y1OMKjnf9AaZ1s QGef97hAfdD+vvqAYXjpPkf6S3PzX/M+rWcWiEv6RVmhFbsdSzo840hAZXffYJYYdeyF zGeg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=qgXCrrfgyjX1bH7A4ba9Sn/6QJCN7we54xLKFE/rYro=; b=EKVV1hqy0YFqAFZCOYXnoXNYgWjoStVnTusWaJDVtAr2YZ4eX4IqlAmXW6iCfWon36 ni99JsYrl/RhdW0rGPlh9FCHAd9vH+P500I6RtRI7EpAjmaLCR/UxDMRVcIMzJRa1pSt DoaqMZwuuEhAY2tJtplz1ICrBRSMDuE1RFJ9PwhVFlO7ezVtQ4ti5Pcg98mBFGp5YLR2 fa6wCMS3Vv2hoHbcsRLACycHXxUB0mFd8SJncAe6K/rdIY3Jj3oQ7dnN2xBm+LWPUkap jbXNclrRTPw949OQ2+lJ82ATBrbC0nVDoSCd/7tpV9Gfnjo7/klWJ82ibeUPxBnA9iTG d01Q==
X-Gm-Message-State: ALKqPwfjG0Y5ybiq5gojljKCTaIFZ/hzmWVQipjsX+Iuj1JbpBVGzETl uLzX5v/wgbhakaQXpoX1BuYlCVQnBMjvPSc1AvUFOA==
X-Google-Smtp-Source: ADUXVKJG1T1Pwk4nPDsd8Jnn2rE8LDWHQVhYlldk4xhb6isc9YhW5VXQDu/ndFF/p4SAP7lDX06h9SvzgME4VSfa/1k=
X-Received: by 2002:aca:1c3:: with SMTP id 186-v6mr5318193oib.174.1527604800694;  Tue, 29 May 2018 07:40:00 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:ac9:66:0:0:0:0:0 with HTTP; Tue, 29 May 2018 07:39:20 -0700 (PDT)
In-Reply-To: <CANatvzzS+T4HcddCemKF7bb1BmACFp=R4n+YMWkq7tnZaUXw4w@mail.gmail.com>
References: <CAKcm_gM39_x+==WwYfb5qeiqB_qxdAt0ow69V+s_Jny3Ek_hDw@mail.gmail.com> <CANatvzzS+T4HcddCemKF7bb1BmACFp=R4n+YMWkq7tnZaUXw4w@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 29 May 2018 07:39:20 -0700
Message-ID: <CABcZeBMrbS9v11Ooz+6F3xVyp28UeNV+_2ntj2o_At7kfDvELw@mail.gmail.com>
Subject: Re: Stream0 Design Team Proposal
To: Kazuho Oku <kazuhooku@gmail.com>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Eric Rescorla <ekr@mozilla.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000080c126056d59351a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/QHeaVkw28h8lF7xpptIJacWmZVo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 May 2018 14:40:05 -0000

--00000000000080c126056d59351a
Content-Type: text/plain; charset="UTF-8"

Hi folks,

I have implemented the proposal from the Stream 0 DT in Minq, and have
interop with Quicly in the 1-RTT mode. This went in quite cleanly at
the cost of probably a day of programming. The code size is about
the same (slight reduction but that's before I cleand up old code
and added some things I know I need).


Mint already had a separated record layer, so on the Mint side, this
was mostly a matter of making that API public, i.e.,

- Making it a Golang interface so I could have multiple
  implementations
- Cleaning up the interface a bit (mostly removing APIs that only DTLS
  uses).
- Adding a way for Minq to add its own record layer implementation
- Adding an API to override the TLS HKDF label prefix

Here's the definition of RecordLayer, with some unnecessary APIs that
I haven't cleaned up yet removed.

  type RecordLayer interface {
        // Install a new TLS key at the record layer
      Rekey(epoch Epoch, factory AeadFactory, key []byte, iv []byte) error

        // Reset back to the "cleartext" record layer
      ResetClear(seq uint64)

        // I'm never going to want to read at this level again
      DiscardReadKey(epoch Epoch)

        // Read a record
      ReadRecord() (*TLSPlaintext, error)

        // Write a record
      WriteRecord(pt *TLSPlaintext) error

        // What is the current Epoch (saves bookkeeping in Mint)
      Epoch() Epoch
  }

The way this works is that Minq installs two RecordLayer objects, one
in each direction [0]. Each one has one active epoch that it expects
to read or write from, and the epoch has an associated queue.

So, for instance, on the server side when Minq receives an Initial
packet, it decrypts it and then stuffs the CRYPTO_HS frames into the
queue associated with epoch 0. It then calls Mint.handshake() which
does:

  Rx: ReadRecord() -> ClientHello
  Tx: WriteRecord(ServerHello)
  Tx: Rekey(epoch = 2 [Handshake)
  Tx: WriteRecord(EncryptedExtensions)
  Tx: WriteRecord(Certificate)
  Tx: WriteRecord(CertificateVerify)
  Tx: WriteRecord(Finished)
  Tx: Rekey(epoch = 3 [Application Data])
  Rx: Rekey(epoch = 2 [Handshake)

This queues up two "flows" of data, corresponding to the Initial and
Handshake encryption levels. Minq is then responsible for sending
these flows in their own packet types with the appropriate keys. When
Mint calls ReadRecord() again, it's reading out of the Handshake input
queue (due to the Rekey that's the last operation).

This is still a bit too messy to put up on Github, but I should have
something up in time for Kista.

-Ekr

[0] One might want to have ReadRecordLayer and WriteRecordLayer, but I
was lazy.


On Tue, May 22, 2018 at 9:57 PM, Kazuho Oku <kazuhooku@gmail.com> wrote:

> FWIW, I am happy to tell you that I have a working PoC code for the
> proposed approach.
>
> On the QUIC side, I saw 2% (124 lines) increase in code size (more on
> that below). On the TLS side, I also saw 2% (175 lines) increase.
> However please look at the code size change especially on the QUIC
> side with grain of salt, as it is just a PoC.
>
> As expected, the key and encryption-level management on the QUIC side
> became very clean. Following are some of the design decisions I made
> as well as the outcomes:
>
> * All the interaction between picotls and quicly are accompanied by
> "epoch". Handshake messages are attributed with their epochs so that
> they do not get protected by the wrong key, or so that octets received
> under an incorrect encryption context cannot be misused.
>
> * All the traffic keys are governed by quicly (managing some traffic
> keys in TLS while managing PNE key in QUIC seems messy).
>
> * The Initial key is setup by quicly, wheeras other traffic keys are
> installed by picotls by calling a callback named
> update_traffic_key_cb. The callback accepts and installs 6 keys in
> total: for three levels (i.e. 0-RTT, handshake, 1-RTT) in two
> directions (send-side and receive-side).
>
> * Three PN spaces have their own AEAD encryption key. Initial PN and
> Handshake PN spaces have one aead decryption key each. Application PN
> space has up to two decryption keys: either for 0-RTT and 1-RTT or for
> two 1-RTT keys during key update.
>
> It was a pain to have a dedicated frame encoding for CRYPTO_HS, even
> though we can reuse (and I reused) the retransmission and reassembly
> logic of QUIC streams for the handshake flows. About a half of the
> code size increase comes from that (the other half comes from the
> added abstraction for having two contexts for the handshake). I would
> prefer reusing the STREAM frame encoding for the handshake data. We
> could possibly use a different base offset (i.e. for CRYPTO_HS frames
> we could use 0b00011XXX, whereas the STREAM frames use 0b00010XXX), as
> well as omitting the Stream ID field.
>
> Overall, now that I have a PoC, I am more confident that the proposed
> approach is the correct path forward. It *simplifies* the QUIC stack
> at the same time giving us better security properties as well as
> fixing various issues in the current design (as discussed in the
> design doc).
>
>
> 2018-05-23 10:30 GMT+09:00 Ian Swett <ianswett=40google.com@dmarc.ietf.org
> >:
> > Dear QUIC WG,
> >
> >
> > On behalf of the Stream 0 Design Team, I am pleased to report that we
> have
> > consensus on a proposed approach to share with the WG. The DT's proposal
> > will make QUIC and TLS work closer together and incorporates ideas from
> > DTLS, but it does not use the DTLS protocol itself.
> >
> >
> > The DT believes this solves the important open Stream 0 issues. The
> proposal
> > will be a bit more invasive in TLS, but we believe it is the right
> long-term
> > direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and Mint) are
> > willing and able to do the work necessary.. A number of stacks are
> currently
> > working on implementations of this new approach, which we hope to have in
> > time for the Interim meeting.
> >
> >
> > A design document describing the overall approach can be found at:
> >
> > https://docs.google.com/document/d/1fRsJqPinJl8N3b-
> bflDRV6auojfJLkxddT93j6SwHY8/edit
> >
> >
> > A PR making the changes to the QUIC documents can be found at:
> >
> > https://github.com/quicwg/base-drafts/pull/1377
> >
> >
> > A few design details did not have clear consensus, but it was felt it
> would
> > be better to discuss those in the wider WG than delay the design team.  A
> > consistent choice was made in the PR and these issues are mentioned in
> > Appendix B of the design doc.
> >
> >
> > As always, comments and questions welcome. That said, this is a big PR
> and
> > we recognize that some editorial work is going to be needed before
> merging.
> > In the interest of letting people follow along, and to keep github from
> > falling over, we ask people to keep discussion on the mailing list and
> > refrain from making PR comments.
> >
> >
> > See you in Kista!
> >
> >
> > Ian and Eric
>
>
>
> --
> Kazuho Oku
>
>

--00000000000080c126056d59351a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">Hi folks,<br><br>I have implemented the proposal from the =
Stream 0 DT in Minq, and have<br>interop with Quicly in the 1-RTT mode. Thi=
s went in quite cleanly at<br>the cost of probably a day of programming. Th=
e code size is about<br>the same (slight reduction but that&#39;s before I =
cleand up old code<br>and added some things I know I need).<br><br><br>Mint=
 already had a separated record layer, so on the Mint side, this<br>was mos=
tly a matter of making that API public, i.e.,<br><br>- Making it a Golang i=
nterface so I could have multiple<br>=C2=A0 implementations<br>- Cleaning u=
p the interface a bit (mostly removing APIs that only DTLS<br>=C2=A0 uses).=
<br>- Adding a way for Minq to add its own record layer implementation<br>-=
 Adding an API to override the TLS HKDF label prefix<br><br>Here&#39;s the =
definition of RecordLayer, with some unnecessary APIs that<br>I haven&#39;t=
 cleaned up yet removed.<br><br>=C2=A0 type RecordLayer interface {<br>=C2=
=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 // Install a new TLS key at the rec=
ord layer<br>=C2=A0 =C2=A0=C2=A0=C2=A0 Rekey(epoch Epoch, factory AeadFacto=
ry, key []byte, iv []byte) error<br><br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0 // Reset back to the &quot;cleartext&quot; record layer<br>=C2=A0=
 =C2=A0=C2=A0=C2=A0 ResetClear(seq uint64)<br><br>=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0 // I&#39;m never going to want to read at this level aga=
in<br>=C2=A0 =C2=A0=C2=A0=C2=A0 DiscardReadKey(epoch Epoch)<br><br>=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 // Read a record<br>=C2=A0 =C2=A0=C2=
=A0=C2=A0 ReadRecord() (*TLSPlaintext, error)<br><br>=C2=A0=C2=A0=C2=A0=C2=
=A0=C2=A0=C2=A0=C2=A0 // Write a record<br>=C2=A0 =C2=A0=C2=A0=C2=A0 WriteR=
ecord(pt *TLSPlaintext) error<br><br>=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 // What is the current Epoch (saves bookkeeping in Mint)<br>=C2=A0 =
=C2=A0=C2=A0=C2=A0 Epoch() Epoch<br>=C2=A0 }<br><br>The way this works is t=
hat Minq installs two RecordLayer objects, one<br>in each direction [0]. Ea=
ch one has one active epoch that it expects<br>to read or write from, and t=
he epoch has an associated queue.<br><br>So, for instance, on the server si=
de when Minq receives an Initial<br>packet, it decrypts it and then stuffs =
the CRYPTO_HS frames into the<br>queue associated with epoch 0. It then cal=
ls Mint.handshake() which<br>does:<br><br>=C2=A0 Rx: ReadRecord() -&gt; Cli=
entHello<br>=C2=A0 Tx: WriteRecord(ServerHello)<br>=C2=A0 Tx: Rekey(epoch =
=3D 2 [Handshake)<br>=C2=A0 Tx: WriteRecord(EncryptedExtensions)<br>=C2=A0 =
Tx: WriteRecord(Certificate)<br>=C2=A0 Tx: WriteRecord(CertificateVerify)<b=
r>=C2=A0 Tx: WriteRecord(Finished)<br>=C2=A0 Tx: Rekey(epoch =3D 3 [Applica=
tion Data])<br>=C2=A0 Rx: Rekey(epoch =3D 2 [Handshake)<br><br>This queues =
up two &quot;flows&quot; of data, corresponding to the Initial and<br>Hands=
hake encryption levels. Minq is then responsible for sending<br>these flows=
 in their own packet types with the appropriate keys. When<br>Mint calls Re=
adRecord() again, it&#39;s reading out of the Handshake input<br>queue (due=
 to the Rekey that&#39;s the last operation).<br><br>This is still a bit to=
o messy to put up on Github, but I should have<br>something up in time for =
Kista.<br><br>-Ekr<br><br>[0] One might want to have ReadRecordLayer and Wr=
iteRecordLayer, but I<br>was lazy.<br><br></div><div class=3D"gmail_extra">=
<br><div class=3D"gmail_quote">On Tue, May 22, 2018 at 9:57 PM, Kazuho Oku =
<span dir=3D"ltr">&lt;<a href=3D"mailto:kazuhooku@gmail.com" target=3D"_bla=
nk">kazuhooku@gmail.com</a>&gt;</span> wrote:<br><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:=
1ex">FWIW, I am happy to tell you that I have a working PoC code for the<br=
>
proposed approach.<br>
<br>
On the QUIC side, I saw 2% (124 lines) increase in code size (more on<br>
that below). On the TLS side, I also saw 2% (175 lines) increase.<br>
However please look at the code size change especially on the QUIC<br>
side with grain of salt, as it is just a PoC.<br>
<br>
As expected, the key and encryption-level management on the QUIC side<br>
became very clean. Following are some of the design decisions I made<br>
as well as the outcomes:<br>
<br>
* All the interaction between picotls and quicly are accompanied by<br>
&quot;epoch&quot;. Handshake messages are attributed with their epochs so t=
hat<br>
they do not get protected by the wrong key, or so that octets received<br>
under an incorrect encryption context cannot be misused.<br>
<br>
* All the traffic keys are governed by quicly (managing some traffic<br>
keys in TLS while managing PNE key in QUIC seems messy).<br>
<br>
* The Initial key is setup by quicly, wheeras other traffic keys are<br>
installed by picotls by calling a callback named<br>
update_traffic_key_cb. The callback accepts and installs 6 keys in<br>
total: for three levels (i.e. 0-RTT, handshake, 1-RTT) in two<br>
directions (send-side and receive-side).<br>
<br>
* Three PN spaces have their own AEAD encryption key. Initial PN and<br>
Handshake PN spaces have one aead decryption key each. Application PN<br>
space has up to two decryption keys: either for 0-RTT and 1-RTT or for<br>
two 1-RTT keys during key update.<br>
<br>
It was a pain to have a dedicated frame encoding for CRYPTO_HS, even<br>
though we can reuse (and I reused) the retransmission and reassembly<br>
logic of QUIC streams for the handshake flows. About a half of the<br>
code size increase comes from that (the other half comes from the<br>
added abstraction for having two contexts for the handshake). I would<br>
prefer reusing the STREAM frame encoding for the handshake data. We<br>
could possibly use a different base offset (i.e. for CRYPTO_HS frames<br>
we could use 0b00011XXX, whereas the STREAM frames use 0b00010XXX), as<br>
well as omitting the Stream ID field.<br>
<br>
Overall, now that I have a PoC, I am more confident that the proposed<br>
approach is the correct path forward. It *simplifies* the QUIC stack<br>
at the same time giving us better security properties as well as<br>
fixing various issues in the current design (as discussed in the<br>
design doc).<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
<br>
2018-05-23 10:30 GMT+09:00 Ian Swett &lt;ianswett=3D<a href=3D"mailto:40goo=
gle.com@dmarc.ietf.org">40google.com@dmarc.<wbr>ietf.org</a>&gt;:<br>
&gt; Dear QUIC WG,<br>
&gt;<br>
&gt;<br>
&gt; On behalf of the Stream 0 Design Team, I am pleased to report that we =
have<br>
&gt; consensus on a proposed approach to share with the WG. The DT&#39;s pr=
oposal<br>
&gt; will make QUIC and TLS work closer together and incorporates ideas fro=
m<br>
&gt; DTLS, but it does not use the DTLS protocol itself.<br>
&gt;<br>
&gt;<br>
&gt; The DT believes this solves the important open Stream 0 issues. The pr=
oposal<br>
&gt; will be a bit more invasive in TLS, but we believe it is the right lon=
g-term<br>
&gt; direction and several TLS stacks (BoringSSL, PicoTLS, NSS, and Mint) a=
re<br>
&gt; willing and able to do the work necessary.. A number of stacks are cur=
rently<br>
&gt; working on implementations of this new approach, which we hope to have=
 in<br>
&gt; time for the Interim meeting.<br>
&gt;<br>
&gt;<br>
&gt; A design document describing the overall approach can be found at:<br>
&gt;<br>
&gt; <a href=3D"https://docs.google.com/document/d/1fRsJqPinJl8N3b-bflDRV6a=
uojfJLkxddT93j6SwHY8/edit" rel=3D"noreferrer" target=3D"_blank">https://doc=
s.google.com/<wbr>document/d/1fRsJqPinJl8N3b-<wbr>bflDRV6auojfJLkxddT93j6Sw=
HY8/<wbr>edit</a><br>
&gt;<br>
&gt;<br>
&gt; A PR making the changes to the QUIC documents can be found at:<br>
&gt;<br>
&gt; <a href=3D"https://github.com/quicwg/base-drafts/pull/1377" rel=3D"nor=
eferrer" target=3D"_blank">https://github.com/quicwg/<wbr>base-drafts/pull/=
1377</a><br>
&gt;<br>
&gt;<br>
&gt; A few design details did not have clear consensus, but it was felt it =
would<br>
&gt; be better to discuss those in the wider WG than delay the design team.=
=C2=A0 A<br>
&gt; consistent choice was made in the PR and these issues are mentioned in=
<br>
&gt; Appendix B of the design doc.<br>
&gt;<br>
&gt;<br>
&gt; As always, comments and questions welcome. That said, this is a big PR=
 and<br>
&gt; we recognize that some editorial work is going to be needed before mer=
ging.<br>
&gt; In the interest of letting people follow along, and to keep github fro=
m<br>
&gt; falling over, we ask people to keep discussion on the mailing list and=
<br>
&gt; refrain from making PR comments.<br>
&gt;<br>
&gt;<br>
&gt; See you in Kista!<br>
&gt;<br>
&gt;<br>
&gt; Ian and Eric<br>
<br>
<br>
<br>
</div></div><span class=3D"HOEnZb"><font color=3D"#888888">-- <br>
Kazuho Oku<br>
<br>
</font></span></blockquote></div><br></div>

--00000000000080c126056d59351a--


From nobody Tue May 29 12:34:40 2018
Return-Path: <dtikhonov@litespeedtech.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5D16112EBD7 for <quic@ietfa.amsl.com>; Tue, 29 May 2018 12:34:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 K8kDuzFi5Pzf for <quic@ietfa.amsl.com>; Tue, 29 May 2018 12:34:36 -0700 (PDT)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABF8812EBB5 for <quic@ietf.org>; Tue, 29 May 2018 12:34:36 -0700 (PDT)
Received: by mail-qt0-x22c.google.com with SMTP id c2-v6so20191049qtn.9 for <quic@ietf.org>; Tue, 29 May 2018 12:34:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mail-followup-to:mime-version :content-disposition:user-agent; bh=QJMEGAbNY7XifyPtLLHf/afVGbX/C2oZyLzMKkaBhDA=; b=QD4bv5FdYyYiyaZ/cFWhLzZUHt3NqHRvuePRKMPCSHb/rgrAkG+3pu6Bzdn2yyaM3W sQaamv1u4Nq1+bBX2MyhZ5Kx0+8F9RMRVlXsGO0i2/RtTQJk/iETwOOahoN56sLNNoI5 PeoxYVsTvCIAmbkqj7XAvcD0jrJdmHtFBTtOPleyxJF4B54xpwykYbFfHVvZMX6RVsT+ xFtG6N+6bXkW4cYjsBFXrWIKBboXaBrURvcngV8KFwmbgv0pQr3iLS4xX5QWYCeB0TUe qcWZ0zQJE3+JaflpPx4u0midfUSqoX4ggsUL7Swalw5ivhNSV1jNIuW56nnQL8U4wrrT id+w==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:subject:message-id:mail-followup-to :mime-version:content-disposition:user-agent; bh=QJMEGAbNY7XifyPtLLHf/afVGbX/C2oZyLzMKkaBhDA=; b=kFiB5c/OcsaSYiAPGvhaoBDxTWD5V45KrMbvv8fr0XX+rH1g3SUmc5Ic4nqnM6xssb q6d+t1bD2zxCDPdtxumulbuN1pyH+6DIUpJDhEBI6zTGAGJy9eTMvAScltqmi9KmR9wi 7/y4634mr4lENhqPh40ZYh4XSndlaDp8dzI/SlxMnWfGzQ8szgHnhf0bU0wrLQkP6nuZ Q7NnlP7j4SE/PDbc6aM/M5sbjcUKb7PlkeEfjwyFYgu0Ox2JGZC/9E0Pq2XN8NkYS2Bq rZm2e/gZJ82f0m48EUvUzMP9WgMazBrMhSigsinpenE7tmjfuEtvSE1pnXiHnyJYLseT 0GwA==
X-Gm-Message-State: ALKqPwdfZSOkcvveqYkHVEhMW+6NyGK9Pzs5XbFVLC8atLR5MlQ/LYDd s5/EknIgkMmABu40eT+9ullAeFqd
X-Google-Smtp-Source: ADUXVKIfqII3WWvv0IkxWjUXFBDYoSC/DNeQWFSmv0wI/4UOpVkORj2i8wKNGDmhVj4Cqt9N5aobyA==
X-Received: by 2002:a0c:9126:: with SMTP id q35-v6mr16968023qvq.230.1527622475556;  Tue, 29 May 2018 12:34:35 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id v123-v6sm6506055qka.79.2018.05.29.12.34.34 for <quic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 May 2018 12:34:35 -0700 (PDT)
Date: Tue, 29 May 2018 15:34:28 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: IETF QUIC WG <quic@ietf.org>
Subject: Wrong level protection ACKs: why not an error
Message-ID: <20180529193427.GA2500@ubuntu-dmitri>
Mail-Followup-To: IETF QUIC WG <quic@ietf.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/l1mpECMlxR3hmBmR-ihfp5kRJW4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 May 2018 19:34:38 -0000

The Draft states:

   A packet that is not protected and claims to acknowledge a packet
   number that was sent with packet protection is not valid.  An
   unprotected packet that carries acknowledgments for protected packets
   MUST be discarded in its entirety.

This seems odd.  Why is this not a connection error?  Do we expect
the peer not to be able to construct a valid ACK?

  - Dmitri.


From nobody Tue May 29 12:38:51 2018
Return-Path: <mikkelfj@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id EC5A312EBD7 for <quic@ietfa.amsl.com>; Tue, 29 May 2018 12:38:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.997
X-Spam-Level: 
X-Spam-Status: No, score=-1.997 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 Tz9OvMlg0nDh for <quic@ietfa.amsl.com>; Tue, 29 May 2018 12:38:42 -0700 (PDT)
Received: from mail-io0-x229.google.com (mail-io0-x229.google.com [IPv6:2607:f8b0:4001:c06::229]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0EA9412EB4F for <quic@ietf.org>; Tue, 29 May 2018 12:38:42 -0700 (PDT)
Received: by mail-io0-x229.google.com with SMTP id e15-v6so10628670iog.1 for <quic@ietf.org>; Tue, 29 May 2018 12:38:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:in-reply-to:references:mime-version:date:message-id:subject:to;  bh=CkCeiC+Jo0ec3q40nsb4J0cOBXrPZ02IJmmVsh72uqs=; b=GUB9TdW80hx8xjZsZI8w2iheGWAQNlde62KRWk82uTMCQ7GLr6lDeeBJNOAjaeCN34 SshXVddIBG8l98RqPW+ENr+Mn0lmxPg4R2Ms/iPO8bG87YMadkYV90cp0/UFff1atsB1 PAgYA/41rEKBkdWSqECvRU39ouidO6vidNNwAVGK8h6BbQJhjFjtl6c/1nIXvImsDsgf k9+Ff3IxOQS7+VnCV/WQj6isH5Ow3okWfZtH1PA3fYyis/UdYLZc3TwjPtjmTJSVKGSt 1L6ZZD/p+pfb+EUTeFwi28JppHVsIAUP9llNl8RJvR1dCo9XAMGw8GL+7VDSI1vZKkXf e80A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:in-reply-to:references:mime-version:date :message-id:subject:to; bh=CkCeiC+Jo0ec3q40nsb4J0cOBXrPZ02IJmmVsh72uqs=; b=Fwo126j3HwnIVKOv63uvXkG7DEb48/AQFNJV6vGlUcH5uacwsxdEYhMcjK5E9qFqU9 aswZeDjRUNu34ylSt75d4Vp9ZFa5mL2gbhrza62uYvvMY5zegFLQmVdCcfY8HYwCNcER v0iv4phBud7X2hjyd5JlcHbJOcAa9bwmwDkkqdL0JeeJ7qXpv09JZQeCsPNlAYilmp4+ Lcg9czxTNPJYZYu+VOeXjFzNDRkUo4GF3MgLDL9YZn/GFLcyTJjiqPJpk4rsJfwpC8Sm YR9lVEiIljNP1D5VgJNCXDiaqQEQxInQp8kgMrmb1eCqH/T+ha9Pw0wfcpiTUqMgVELs 5doA==
X-Gm-Message-State: ALKqPwft6Lv6BXsIh9zag+tigsLmTPLLFYbD/ghCPzgsr8c+8P6z0Q7U S3JgD2KZ7V5P16G0VW6yceAstdHwk4BIhrgZ1B4=
X-Google-Smtp-Source: ADUXVKLdZ8l02Y2JOdRd/ksK7IpkJUws4MeyCHQdo3nTqsLsSCBf0PizpW9lN2USMPKCMJxTPNzKMISZ0CFHkCKkZmE=
X-Received: by 2002:a6b:39d4:: with SMTP id g203-v6mr16944191ioa.165.1527622721384;  Tue, 29 May 2018 12:38:41 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 29 May 2018 12:38:40 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <20180529193427.GA2500@ubuntu-dmitri>
References: <20180529193427.GA2500@ubuntu-dmitri>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Tue, 29 May 2018 12:38:40 -0700
Message-ID: <CAN1APdcpMmVVDydLNErfJKfa6_fH8LPWfNzaupi_Kxx+qA-Jxw@mail.gmail.com>
Subject: Re: Wrong level protection ACKs: why not an error
To: Dmitri Tikhonov <dtikhonov@litespeedtech.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a8bd26056d5d61d6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/lRp23T3RpWtjekKWmGvmGpbcT0w>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 May 2018 19:38:50 -0000

--000000000000a8bd26056d5d61d6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Anything in early handshake it is vulnerable to attacks.
It is better to drop ill-formed packets than allowing them to interrupt the
handshake since you can=E2=80=99t be sure who the sender is.


On 29 May 2018 at 21.35.01, Dmitri Tikhonov (dtikhonov@litespeedtech.com)
wrote:

The Draft states:

A packet that is not protected and claims to acknowledge a packet
number that was sent with packet protection is not valid. An
unprotected packet that carries acknowledgments for protected packets
MUST be discarded in its entirety.

This seems odd. Why is this not a connection error? Do we expect
the peer not to be able to construct a valid ACK?

- Dmitri.

--000000000000a8bd26056d5d61d6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style>=
</head><body style=3D"word-wrap:break-word;line-break:after-white-space"><d=
iv id=3D"bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">Anything in early ha=
ndshake it is vulnerable to attacks.</div><div id=3D"bloop_customfont" styl=
e=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margi=
n:0px;line-height:auto">It is better to drop ill-formed packets than allowi=
ng them to interrupt the handshake since you can=E2=80=99t be sure who the =
sender is.</div><div id=3D"bloop_sign_1527622652822163968" class=3D"bloop_s=
ign"><div style=3D"font-family:helvetica,arial;font-size:13px"><br></div></=
div> <br><p class=3D"airmail_on">On 29 May 2018 at 21.35.01, Dmitri Tikhono=
v (<a href=3D"mailto:dtikhonov@litespeedtech.com">dtikhonov@litespeedtech.c=
om</a>) wrote:</p> <blockquote type=3D"cite" class=3D"clean_bq"><span><div>=
<div></div><div>The Draft states:
<br>
<br>   A packet that is not protected and claims to acknowledge a packet
<br>   number that was sent with packet protection is not valid.  An
<br>   unprotected packet that carries acknowledgments for protected packet=
s
<br>   MUST be discarded in its entirety.
<br>
<br>This seems odd.  Why is this not a connection error?  Do we expect
<br>the peer not to be able to construct a valid ACK?
<br>
<br>  - Dmitri.
<br>
<br></div></div></span></blockquote></body></html>

--000000000000a8bd26056d5d61d6--


From nobody Tue May 29 12:41:34 2018
Return-Path: <dtikhonov@litespeedtech.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9D92912FA8B for <quic@ietfa.amsl.com>; Tue, 29 May 2018 12:41:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.61
X-Spam-Level: 
X-Spam-Status: No, score=-2.61 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=litespeedtech-com.20150623.gappssmtp.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 GTxuSIahBOGb for <quic@ietfa.amsl.com>; Tue, 29 May 2018 12:41:31 -0700 (PDT)
Received: from mail-qk0-x233.google.com (mail-qk0-x233.google.com [IPv6:2607:f8b0:400d:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D3EC512FA85 for <quic@ietf.org>; Tue, 29 May 2018 12:41:30 -0700 (PDT)
Received: by mail-qk0-x233.google.com with SMTP id h7-v6so5333662qkm.0 for <quic@ietf.org>; Tue, 29 May 2018 12:41:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:content-transfer-encoding :in-reply-to:user-agent; bh=DCxi0Nv5xdf0phY3+irhW0eP6WK9BVpCvtSjrIBeHBU=; b=dr+Hc8Pggujltq24jaFSrj+7DrvNHg2pyBY5jERHz8W8cviZTx7helkDnBWyvlLMKO mmds7tHydYAcFsl+X0lAhBZsgjsgKLixR/lzkAO3wJ3VVVBYCJNJmIjfhGJfh/GISTXk cfnljz/4qwkvFyjBhJmfUiG8YMs+Dh2vUxXLFkURH+ZZ9qWPXXMYo2Vvx2Rtz01oTSp/ ejWTdY7srSLdxly+wy1oTJxOnuGu3Nug/eNUkJ2ZTmLbYDEp14KkhGW+jD0z2QCtdYX9 lBDmSd14CzSkI8CNkGIVL2WDLG8mH541hc5Zr216TkuXhYt0DszNkMi80LrUk1M9gRjN urCA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id :mail-followup-to:references:mime-version:content-disposition :content-transfer-encoding:in-reply-to:user-agent; bh=DCxi0Nv5xdf0phY3+irhW0eP6WK9BVpCvtSjrIBeHBU=; b=C//MpGhoFfvkNDVYbowJ16Vm6/JLI7i56csIU0ThXJcCAI1CQlWWHG7WDe2LBnczGn Ayshf/QWjPP9jKbY34blhmOlh038efwqp6z3IGfvw+cxjeRQjk4NE+j3z5gZo1hWmR0A Gpu3LT2cdAOb987VG8TipdZRGHUL4WfyrGFDgWqYfLPVa+N2JoBY1Qx4B1/NwHGwDeBC KCyvHY0yoQ4CEOrF04g1QfaI7CdiN3EU0bV8cGAsJ81Fk2uIeLWaM1EjaPG28q8aV3g3 Sl/Pmh6/Fn0ejNFrNMhwU39K/Bs8mtxe8uId0GEXEn0Z7bmQo8srE9iAr30T5OnD0GBu Wf4w==
X-Gm-Message-State: ALKqPwduasK8TFv7MTCz6Fjodu5clG4UIbE730NyuGrN+0a0jeCtS2w2 CIrDdbxAF7tXOJdCLrmidDh+dpPO
X-Google-Smtp-Source: ADUXVKKg/3XlUsZOIXI3xtLEhygNfxdoHeq9mPsV+Po8unSyTrzuWmAI1H6hl0zHUigeT7WD+ZWrQQ==
X-Received: by 2002:a37:6d07:: with SMTP id i7-v6mr17010462qkc.208.1527622890000;  Tue, 29 May 2018 12:41:30 -0700 (PDT)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id v22-v6sm5121950qtg.46.2018.05.29.12.41.28 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 29 May 2018 12:41:29 -0700 (PDT)
Date: Tue, 29 May 2018 15:41:25 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Mikkel =?iso-8859-1?Q?Fahn=F8e_J=F8rgensen?= <mikkelfj@gmail.com>
Cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Wrong level protection ACKs: why not an error
Message-ID: <20180529194124.GB2500@ubuntu-dmitri>
Mail-Followup-To: Mikkel =?iso-8859-1?Q?Fahn=F8e_J=F8rgensen?= <mikkelfj@gmail.com>, IETF QUIC WG <quic@ietf.org>
References: <20180529193427.GA2500@ubuntu-dmitri> <CAN1APdcpMmVVDydLNErfJKfa6_fH8LPWfNzaupi_Kxx+qA-Jxw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CAN1APdcpMmVVDydLNErfJKfa6_fH8LPWfNzaupi_Kxx+qA-Jxw@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/y-1TCzv8ipNCNlwle_ZxIhrhI_0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 May 2018 19:41:33 -0000

I see.  Thank you!

  - Dmitri.

On Tue, May 29, 2018 at 12:38:40PM -0700, Mikkel Fahnøe Jørgensen wrote:
> Anything in early handshake it is vulnerable to attacks.
> It is better to drop ill-formed packets than allowing them to interrupt the
> handshake since you can’t be sure who the sender is.
> 
> 
> On 29 May 2018 at 21.35.01, Dmitri Tikhonov (dtikhonov@litespeedtech.com)
> wrote:
> 
> The Draft states:
> 
> A packet that is not protected and claims to acknowledge a packet
> number that was sent with packet protection is not valid. An
> unprotected packet that carries acknowledgments for protected packets
> MUST be discarded in its entirety.
> 
> This seems odd. Why is this not a connection error? Do we expect
> the peer not to be able to construct a valid ACK?
> 
> - Dmitri.


From nobody Wed May 30 09:45:02 2018
Return-Path: <ilubashe@akamai.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D699812D963 for <quic@ietfa.amsl.com>; Wed, 30 May 2018 09:44:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level: 
X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01] 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 mDtl0rDmn2j0 for <quic@ietfa.amsl.com>; Wed, 30 May 2018 09:44:55 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::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 723D112D779 for <quic@ietf.org>; Wed, 30 May 2018 09:44:55 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.22/8.16.0.22) with SMTP id w4UGgnRo019774 for <quic@ietf.org>; Wed, 30 May 2018 17:44:54 +0100
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : content-type : mime-version; s=jan2016.eng; bh=wgwAi6SUgo8VPx8ipm6/f5om7+3g2UnkK/fMpOOj0v0=; b=mZO8a+hTJzlB4BrMRzNk7Tu5eUDRTh1/iy6Fv4KYBOQHuRpPLpjeLNvVgAzDYu9/kx+1 QCacQSNB2Pd9ikyT4Ba+jYxW77ferA/2+nx4PiuJ4ZLKNnRMBJImVjoDyxGxb71t81t+ Xsfe/IpqJGwGNWCedrkTojRbyYnBLoH+prUOYaKXNjFSTQVNvDScSa07SbAPd16UeUFy b8cpe8zLPbOXYKWX6iMf1VD2F3eGa5mAUA/7E5oqREwsRKhYh3V/9fBYAdF7iwjad4QL aw9PyzE4Cv1UFbLRIpbCAT2/OoZmMPDDc+TphoqkcaNvfARJF64rlI4HIebPb7uGKvIm SA== 
Received: from prod-mail-ppoint4 (a96-6-114-87.deploy.static.akamaitechnologies.com [96.6.114.87] (may be forged)) by m0050102.ppops.net-00190b01. with ESMTP id 2j9cw73pbp-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <quic@ietf.org>; Wed, 30 May 2018 17:44:54 +0100
Received: from pps.filterd (prod-mail-ppoint4.akamai.com [127.0.0.1]) by prod-mail-ppoint4.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w4UGfWOi028916 for <quic@ietf.org>; Wed, 30 May 2018 12:44:53 -0400
Received: from email.msg.corp.akamai.com ([172.27.25.33]) by prod-mail-ppoint4.akamai.com with ESMTP id 2j9cvv4err-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT) for <quic@ietf.org>; Wed, 30 May 2018 12:44:50 -0400
Received: from ustx2ex-dag1mb6.msg.corp.akamai.com (172.27.27.107) by ustx2ex-dag1mb3.msg.corp.akamai.com (172.27.27.103) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 30 May 2018 11:44:36 -0500
Received: from ustx2ex-dag1mb6.msg.corp.akamai.com ([172.27.27.107]) by ustx2ex-dag1mb6.msg.corp.akamai.com ([172.27.27.107]) with mapi id 15.00.1365.000; Wed, 30 May 2018 09:44:36 -0700
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: QUIC WG <quic@ietf.org>
Subject: Partially Reliable Message Stream
Thread-Topic: Partially Reliable Message Stream
Thread-Index: AdP4Mo3KTicRHsMuS7e4Jrowbk1vdQ==
Date: Wed, 30 May 2018 16:44:36 +0000
Message-ID: <d263c36bc5264842a65f04fc3b017538@ustx2ex-dag1mb6.msg.corp.akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.35.106]
Content-Type: multipart/alternative; boundary="_000_d263c36bc5264842a65f04fc3b017538ustx2exdag1mb6msgcorpak_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-30_08:, , 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=904 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1805220000 definitions=main-1805300179
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-30_08:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=830 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1805220000 definitions=main-1805300179
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/zKPRYDn1_FN08BuDwWo44ENWGeY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 May 2018 16:45:00 -0000

--_000_d263c36bc5264842a65f04fc3b017538ustx2exdag1mb6msgcorpak_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I've just uploaded a new draft for partially reliable QUIC streams.  Note: =
this feature is likely not in scope for V1, but it can be an extension for =
V1 and/or a part of V2.

The new version 03 (https://tools.ietf.org/html/draft-lubashev-quic-partial=
-reliability-03) no longer needs complex flow control changes and removes t=
he need to transmit multiple frames in the same packet.


  *   Igor

P.S.
  There is also a new version 02, which includes a more complex algorithm w=
ith more features and different trade-offs.  But I think version 03 is a be=
tter match for the needs so far.

--_000_d263c36bc5264842a65f04fc3b017538ustx2exdag1mb6msgcorpak_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:70856379;
	mso-list-type:hybrid;
	mso-list-template-ids:-489010456 1033792020 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:16;
	mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1
	{mso-list-id:862086199;
	mso-list-type:hybrid;
	mso-list-template-ids:-1251558108 -2135622018 67698691 67698693 67698689 6=
7698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:16;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I&#8217;ve just uploaded a new draft for partially r=
eliable QUIC streams.&nbsp; Note: this feature is likely not in scope for V=
1, but it can be an extension for V1 and/or a part of V2.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The new version 03 (<a href=3D"https://tools.ietf.or=
g/html/draft-lubashev-quic-partial-reliability-03">https://tools.ietf.org/h=
tml/draft-lubashev-quic-partial-reliability-03</a>) no longer needs complex=
 flow control changes and removes the
 need to transmit multiple frames in the same packet.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l1 level1 =
lfo2">Igor<o:p></o:p></li></ul>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">P.S.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp; There is also a new version 02, which include=
s a more complex algorithm with more features and different trade-offs.&nbs=
p; But I think version 03 is a better match for the needs so far.<o:p></o:p=
></p>
</div>
</body>
</html>

--_000_d263c36bc5264842a65f04fc3b017538ustx2exdag1mb6msgcorpak_--


From nobody Wed May 30 15:47:00 2018
Return-Path: <mbishop@evequefou.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 71F4D12EAAF for <quic@ietfa.amsl.com>; Wed, 30 May 2018 15:46:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.91
X-Spam-Level: 
X-Spam-Status: No, score=-1.91 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 Upl_jyQG5kqD for <quic@ietfa.amsl.com>; Wed, 30 May 2018 15:46:55 -0700 (PDT)
Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0134.outbound.protection.outlook.com [104.47.38.134]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F25EE12E054 for <quic@ietf.org>; Wed, 30 May 2018 15:46:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=PLzqCjCbyuc4ZNTf7YwRD/EhRiGe08bwDH1dC/m55mE=; b=H5jAwqIUsF5cUr4pWWvlZMI5URsao3/N0S1Iusf1OQnsIt2j9QyQqlyS/1D8/A9P0bx5sbPauHNUTd1Oorjtk0RC98Vcn6ELX+VPRYidVnIMqGKXlvgC61jTkbYUHWUUEEmdxuhWLkDTyrE/Z0LZOyR1LDhq2i3q4cFtvABrYBE=
Received: from SN1PR08MB1854.namprd08.prod.outlook.com (10.169.39.8) by SN1PR08MB1758.namprd08.prod.outlook.com (10.162.134.12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.797.11; Wed, 30 May 2018 22:46:52 +0000
Received: from SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::c1ff:4f0e:a59b:b9a9]) by SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::c1ff:4f0e:a59b:b9a9%13]) with mapi id 15.20.0797.018; Wed, 30 May 2018 22:46:51 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: "Lubashev, Igor" <ilubashe=40akamai.com@dmarc.ietf.org>, QUIC WG <quic@ietf.org>
Subject: RE: Partially Reliable Message Stream
Thread-Topic: Partially Reliable Message Stream
Thread-Index: AdP4Mo3KTicRHsMuS7e4Jrowbk1vdQAMuR2g
Date: Wed, 30 May 2018 22:46:51 +0000
Message-ID: <SN1PR08MB18541BF8B27EA5484FA6A437DA6C0@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <d263c36bc5264842a65f04fc3b017538@ustx2ex-dag1mb6.msg.corp.akamai.com>
In-Reply-To: <d263c36bc5264842a65f04fc3b017538@ustx2ex-dag1mb6.msg.corp.akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [2601:600:8080:5a28:c0d8:4f09:d150:c307]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN1PR08MB1758; 7:f33J6i2wpH5o8IKB1Kd5ltX4L4xFU9zqI3YoXxOGWA1DDn3M9c6kF4I5VlD4/jJLp3lQy0WNqp3/yBiwbiuImQLjbIt2cssTXiUWfBHO4nW6XpxoURx9Zt8kG9ocytfccQSFfNRWXXaENHZOA5Yel4nTb74wEML8PMlFGZfO3jpPcoL1Ubu/ytpte1s85paYq9n1PvdsuBEHAfSiF6Lp30N8JNf/IG9mJOdsTo8A6AMLjq6VAZe1NcPPAuEI8ciV
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(5600026)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(2017052603328)(7153060)(7193020); SRVR:SN1PR08MB1758; 
x-ms-traffictypediagnostic: SN1PR08MB1758:
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-microsoft-antispam-prvs: <SN1PR08MB1758B600AFE9B138182A9F73DA6C0@SN1PR08MB1758.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(10201501046)(3002001)(3231254)(944501410)(52105095)(93006095)(93001095)(149027)(150027)(6041310)(20161123558120)(2016111802025)(20161123564045)(20161123560045)(20161123562045)(6072148)(6043046)(201708071742011)(7699016); SRVR:SN1PR08MB1758; BCL:0; PCL:0; RULEID:; SRVR:SN1PR08MB1758; 
x-forefront-prvs: 0688BF9B46
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(376002)(39830400003)(39380400002)(346002)(396003)(189003)(199004)(446003)(11346002)(2420400007)(106356001)(74316002)(8676002)(476003)(2900100001)(33656002)(105586002)(5250100002)(486006)(606006)(99286004)(186003)(7736002)(14454004)(5660300001)(110136005)(68736007)(15650500001)(97736004)(86362001)(316002)(478600001)(54896002)(74482002)(6306002)(7696005)(76176011)(53936002)(6116002)(25786009)(55016002)(790700001)(9686003)(229853002)(236005)(102836004)(6506007)(6246003)(59450400001)(53546011)(6436002)(7110500001)(2906002)(3280700002)(81166006)(81156014)(3660700001)(46003)(10710500007)(8936002)(3480700004); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR08MB1758; H:SN1PR08MB1854.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: izLXm+NsZZ5iY0VGZxHnsq/Q+RPQpUhlx/RzTYYUo4988RBqwDVu0szMZgx46p3UFGRuwFfkGglSNIXwtEnly8NLi13JT8bAHn0/GgP4PG7SbOld06hNoopB0iDDsDreOnoCsWRBMM1KDahSX6z6Ju+Gq+SqNr2rpxoZXcxGjXvecLi9Qvbh7mSRCBs3mzl7
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_SN1PR08MB18541BF8B27EA5484FA6A437DA6C0SN1PR08MB1854namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 6472fedf-db17-4cce-8b80-08d5c67f3c6e
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 6472fedf-db17-4cce-8b80-08d5c67f3c6e
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 May 2018 22:46:51.8254 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR08MB1758
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/B4JXdSB9mKsRxujYVn3nY1GsdJA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 May 2018 22:46:59 -0000

--_000_SN1PR08MB18541BF8B27EA5484FA6A437DA6C0SN1PR08MB1854namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I find the one octet gap a bit confusing, but as I think about it, I see wh=
y you need it.  If all the stream data arrived successfully (but hadn't bee=
n acknowledged yet due to loss of the ACK, delay, etc.) and the EXPIRED_STR=
EAM_DATA gets lost, the receiver can only retroactively realize there was a=
 jump.  Having an octet that is never transmitted ensures the receiver actu=
ally sees a gap, which means that an in-order API will not proceed until it=
 has received either the missing octet or an EXPIRED_STREAM_DATA informing =
it the octet will never arrive.

This simplification (versus -02) comes at a price:  If an API were exposing=
 stream data out-of-order, then in your example, the receiver knows that a =
message always begins on a ten-byte boundary.  A receiver can no longer fin=
d ten-byte boundaries, because the offset on the read side doesn't match th=
e offset on the send side.  I agree with you that this seems like a reasona=
ble trade-off for the simpler flow control.

One conflict I see in the doc:

*         Section 3 says:  Receipt of an EXPIRED_STREAM_DATA does not advan=
ce the largest received offset for the stream.

  *   Section 5 says:  A receiver SHOULD discard any stream data received f=
or an offset smaller than the new smallest receive offset, possibly advanci=
ng the largest received offset for the stream.

Other minor nits are better done via PR.
From: QUIC <quic-bounces@ietf.org> On Behalf Of Lubashev, Igor
Sent: Wednesday, May 30, 2018 9:45 AM
To: QUIC WG <quic@ietf.org>
Subject: Partially Reliable Message Stream

I've just uploaded a new draft for partially reliable QUIC streams.  Note: =
this feature is likely not in scope for V1, but it can be an extension for =
V1 and/or a part of V2.

The new version 03 (https://tools.ietf.org/html/draft-lubashev-quic-partial=
-reliability-03) no longer needs complex flow control changes and removes t=
he need to transmit multiple frames in the same packet.


  *   Igor

P.S.
  There is also a new version 02, which includes a more complex algorithm w=
ith more features and different trade-offs.  But I think version 03 is a be=
tter match for the needs so far.

--_000_SN1PR08MB18541BF8B27EA5484FA6A437DA6C0SN1PR08MB1854namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle20
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle21
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:15236067;
	mso-list-template-ids:175170554;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1
	{mso-list-id:862086199;
	mso-list-type:hybrid;
	mso-list-template-ids:-1251558108 -2135622018 67698691 67698693 67698689 6=
7698691 67698693 67698689 67698691 67698693;}
@list l1:level1
	{mso-level-start-at:16;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2
	{mso-list-id:1865288174;
	mso-list-type:hybrid;
	mso-list-template-ids:-1448442924 67698689 67698691 67698693 67698689 6769=
8691 67698693 67698689 67698691 67698693;}
@list l2:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l2:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l2:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l2:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l2:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l2:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I find the one octet gap a bit confusing, but as I t=
hink about it, I see why you need it.&nbsp; If all the stream data arrived =
successfully (but hadn&#8217;t been acknowledged yet due to loss of the ACK=
, delay, etc.)
<i>and</i> the EXPIRED_STREAM_DATA gets lost, the receiver can only retroac=
tively realize there was a jump.&nbsp; Having an octet that is never transm=
itted ensures the receiver actually
<i>sees</i> a gap, which means that an in-order API will not proceed until =
it has received either the missing octet or an EXPIRED_STREAM_DATA informin=
g it the octet will never arrive.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">This simplification (versus -02) comes at a price:&n=
bsp; If an API were exposing stream data out-of-order, then in your example=
, the receiver knows that a message always begins on a ten-byte boundary.&n=
bsp; A receiver can no longer find ten-byte
 boundaries, because the offset on the read side doesn&#8217;t match the of=
fset on the send side.&nbsp; I agree with you that this seems like a reason=
able trade-off for the simpler flow control.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">One conflict I see in the doc:<o:p></o:p></p>
<pre style=3D"margin-left:.5in;text-indent:-.25in;mso-list:l2 level1 lfo4">=
<![if !supportLists]><span style=3D"font-family:Symbol"><span style=3D"mso-=
list:Ignore">&middot;<span style=3D"font:7.0pt &quot;Times New Roman&quot;"=
>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></span></span><![e=
ndif]><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,sans-=
serif">Section 3 says:</span><span style=3D"font-family:&quot;Calibri&quot;=
,sans-serif">&nbsp; </span>Receipt of an EXPIRED_STREAM_DATA <b>does not ad=
vance the largest received offset for the stream</b>.<o:p></o:p></pre>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l2 level1 =
lfo4">Section 5 says:&nbsp;
<span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">A rece=
iver SHOULD discard any stream data received for an offset smaller than the=
 new smallest receive offset,
<b>possibly advancing the largest received offset for the stream</b>.<o:p><=
/o:p></span></li></ul>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Other minor nits are better done via PR.<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p></o:p></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> QUIC &lt;quic-bounces@ietf.org&gt; <b>O=
n Behalf Of </b>
Lubashev, Igor<br>
<b>Sent:</b> Wednesday, May 30, 2018 9:45 AM<br>
<b>To:</b> QUIC WG &lt;quic@ietf.org&gt;<br>
<b>Subject:</b> Partially Reliable Message Stream<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I&#8217;ve just uploaded a new draft for partially r=
eliable QUIC streams.&nbsp; Note: this feature is likely not in scope for V=
1, but it can be an extension for V1 and/or a part of V2.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The new version 03 (<a href=3D"https://tools.ietf.or=
g/html/draft-lubashev-quic-partial-reliability-03">https://tools.ietf.org/h=
tml/draft-lubashev-quic-partial-reliability-03</a>) no longer needs complex=
 flow control changes and removes the
 need to transmit multiple frames in the same packet.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-list:l1 level1 lfo3">Igor<o:p></o:p></=
li></ul>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">P.S.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp; There is also a new version 02, which include=
s a more complex algorithm with more features and different trade-offs.&nbs=
p; But I think version 03 is a better match for the needs so far.<o:p></o:p=
></p>
</div>
</body>
</html>

--_000_SN1PR08MB18541BF8B27EA5484FA6A437DA6C0SN1PR08MB1854namp_--


From nobody Wed May 30 17:51:17 2018
Return-Path: <martin.thomson@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2CE6C12EBAF for <quic@ietfa.amsl.com>; Wed, 30 May 2018 17:51:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level: 
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 qflx96OUxqDq for <quic@ietfa.amsl.com>; Wed, 30 May 2018 17:51:12 -0700 (PDT)
Received: from mail-oi0-x22e.google.com (mail-oi0-x22e.google.com [IPv6:2607:f8b0:4003:c06::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F70F12EB7F for <quic@ietf.org>; Wed, 30 May 2018 17:51:12 -0700 (PDT)
Received: by mail-oi0-x22e.google.com with SMTP id f79-v6so4097532oib.7 for <quic@ietf.org>; Wed, 30 May 2018 17:51:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc:content-transfer-encoding; bh=MTMfaXPR9jOKB2IJBO93n6KrEi0fIoHIDlKbPWBjiZ8=; b=scpY9ybjrST7muJuTRx8/9a7bFgKm6SDpsuyNAYAwtZN1D8jXlbmCrnuyB1eWg5lVN 3pTJLVe3U36sL/mN1wEfKXULohZTQY6ohNF1n1WYuxzE2jUzA33gwf22JJHQWq+vQ2t6 tV8Gacyz6p2axLybXPBtJqP6HSjtcoP8eIIBWNiYLnWIbpeb7zCUp5LfG28bRgpCGuG7 00OJRKZq5BkpCDJQer+IgPdWS9071kb7Psp3hekjukKs4zSGDFT2Yvc3o8yjiIwS3Z53 cYpljkFfQ9ZeJzsNkyzYO1quKKkGabUVDBMpaSeyrwodbv883my/FtAlBCh/kNNQDOJF MzPw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc:content-transfer-encoding; bh=MTMfaXPR9jOKB2IJBO93n6KrEi0fIoHIDlKbPWBjiZ8=; b=Ek5Lv6x8C4JZ44u2wqFNG6Hf/eOX03nMQSz7HF1iSfolLBQAupqy/Pr0xwnHUUA92M L4Q78qLTXE6PCqBvgmop0YCW/OqoXCxVpX9STFZHFaIsEOQA+llbpzw0qzBU/4swvf/F eF+IXThEgSxFwrwlgNFxSXofBY+N6y3SYFfwGzWDzvXjghzgQ8OUQfxgU17tzU8CV+RO OxKRfIFcyx6yfHObDBW+kGqkdfXDLPgw6AMy2DfNNa6DaVyIL4Ti9hXzQ4XEpH/8dEVT 8PtTIoJZHiRXd8VL3+vuDl/kOzAFmgudX1MKyFqITZmUv3ArBO89no9qndgpG51gjyI1 kpgA==
X-Gm-Message-State: APt69E3lnFmmLXPDMZh3AKBzbCOWTryaOT+MVuaWTRMcmqWmIBQKQM7o zuw6IJ2vcoQ/brqlcK844uttOqmHz+x5f2pkawozrQ==
X-Google-Smtp-Source: ADUXVKKt6wW95d7eyx3tBr0g5shMLRu/+nzMVgyvre8MQ1djjmzhah8IMYQFBM5KfMCl2uGEGpnzllgH0karhltVDis=
X-Received: by 2002:aca:1218:: with SMTP id 24-v6mr2723236ois.144.1527727871607;  Wed, 30 May 2018 17:51:11 -0700 (PDT)
MIME-Version: 1.0
References: <d263c36bc5264842a65f04fc3b017538@ustx2ex-dag1mb6.msg.corp.akamai.com> <SN1PR08MB18541BF8B27EA5484FA6A437DA6C0@SN1PR08MB1854.namprd08.prod.outlook.com>
In-Reply-To: <SN1PR08MB18541BF8B27EA5484FA6A437DA6C0@SN1PR08MB1854.namprd08.prod.outlook.com>
From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 31 May 2018 10:50:59 +1000
Message-ID: <CABkgnnWUpaFvz3d0SJJ99JkhdQfwdaxYosKwj3dK9BVZUtZ_yw@mail.gmail.com>
Subject: Re: Partially Reliable Message Stream
To: Mike Bishop <mbishop@evequefou.be>
Cc: "Lubashev, Igor" <ilubashe=40akamai.com@dmarc.ietf.org>, QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/U7sZS3Y8WZsmamuzUeumteX1Wdk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2018 00:51:15 -0000

Like Mike, I find this gap thing confusing.  And Mike's message
helped, but not a lot.

It took a while to realize that forcing a gap creates a new starting
point for the next message that forces the recipient to recognize and
deal with.  However, the logic for identifying that is just hard and
it's an unnecessary imposition in my view.

Say I send a message with a length of 10 and only two octets make it
onto the wire (as with your example), then it is immediately
abandoned.  Your solution would have the EXPIRED_STREAM_DATA force a
gap after the second octet, so that the next message could start at
offset 3 rather than offset 10.  That saves the remaining 7 octets of
flow control credit.  (Use bigger numbers and perhaps it seems more
motivating).

If the octets that cover the gap were sent, then you have a problem
because now you have sent two versions of the same octets, so you can
only do this if the octets were never sent.  It starts to get closer
and closer to the point where a new stream is just easier.

Worst, I think is that the receiver has to have complicated logic for
identifying that a gap exists and dealing with it.  It has to read up
to what it has, observe that the data has expired, then learn where
the gap ends, then resynchronize based on 1+gap_end for the next
message.

Better to eat the flow control cost in my view.  Or send RST_STREAM
and make another stream.
On Thu, May 31, 2018 at 8:48 AM Mike Bishop <mbishop@evequefou.be> wrote:
>
> I find the one octet gap a bit confusing, but as I think about it, I see =
why you need it.  If all the stream data arrived successfully (but hadn=E2=
=80=99t been acknowledged yet due to loss of the ACK, delay, etc.) and the =
EXPIRED_STREAM_DATA gets lost, the receiver can only retroactively realize =
there was a jump.  Having an octet that is never transmitted ensures the re=
ceiver actually sees a gap, which means that an in-order API will not proce=
ed until it has received either the missing octet or an EXPIRED_STREAM_DATA=
 informing it the octet will never arrive.
>
>
>
> This simplification (versus -02) comes at a price:  If an API were exposi=
ng stream data out-of-order, then in your example, the receiver knows that =
a message always begins on a ten-byte boundary.  A receiver can no longer f=
ind ten-byte boundaries, because the offset on the read side doesn=E2=80=99=
t match the offset on the send side.  I agree with you that this seems like=
 a reasonable trade-off for the simpler flow control.
>
>
>
> One conflict I see in the doc:
>
> =C2=B7         Section 3 says:  Receipt of an EXPIRED_STREAM_DATA does no=
t advance the largest received offset for the stream.
>
> Section 5 says:  A receiver SHOULD discard any stream data received for a=
n offset smaller than the new smallest receive offset, possibly advancing t=
he largest received offset for the stream.
>
>
>
> Other minor nits are better done via PR.
>
> From: QUIC <quic-bounces@ietf.org> On Behalf Of Lubashev, Igor
> Sent: Wednesday, May 30, 2018 9:45 AM
> To: QUIC WG <quic@ietf.org>
> Subject: Partially Reliable Message Stream
>
>
>
> I=E2=80=99ve just uploaded a new draft for partially reliable QUIC stream=
s.  Note: this feature is likely not in scope for V1, but it can be an exte=
nsion for V1 and/or a part of V2.
>
>
>
> The new version 03 (https://tools.ietf.org/html/draft-lubashev-quic-parti=
al-reliability-03) no longer needs complex flow control changes and removes=
 the need to transmit multiple frames in the same packet.
>
>
>
> Igor
>
>
>
> P.S.
>
>   There is also a new version 02, which includes a more complex algorithm=
 with more features and different trade-offs.  But I think version 03 is a =
better match for the needs so far.


From nobody Wed May 30 18:03:27 2018
Return-Path: <prvs=968909f698=fenix@fb.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B48A12D870 for <quic@ietfa.amsl.com>; Wed, 30 May 2018 18:03:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=Z6gGa+dN; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=BEXsAlRt
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 bv8N3Jv43ojZ for <quic@ietfa.amsl.com>; Wed, 30 May 2018 18:03:23 -0700 (PDT)
Received: from mx0a-00082601.pphosted.com (mx0b-00082601.pphosted.com [67.231.153.30]) (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 81B5912DA15 for <quic@ietf.org>; Wed, 30 May 2018 18:03:23 -0700 (PDT)
Received: from pps.filterd (m0001255.ppops.net [127.0.0.1]) by mx0b-00082601.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w4V0v392017377; Wed, 30 May 2018 18:03:18 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=facebook; bh=amDVm5B/8H94R/Ir+COvnrRlerLOrP0SUyovYyvn3pk=; b=Z6gGa+dNT75ypHxjp6H+smDTeE/cEUCp84xTDXTDU5aYL5wS2cSP0OnUjUHzH7I/tUQs LkR5Ntr7W5FTZdVaA7wlNoTyNSiWQK9PMdjqnbHmlli4815y39zszxgo87lYrRgwGA16 PMeU3JajwSv19Q84ok2lqrqmSUWXclnmnk0= 
Received: from maileast.thefacebook.com ([199.201.65.23]) by mx0b-00082601.pphosted.com with ESMTP id 2ja2msgp8w-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Wed, 30 May 2018 18:03:18 -0700
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (192.168.183.28) by o365-in.thefacebook.com (192.168.177.29) with Microsoft SMTP Server (TLS) id 14.3.361.1; Wed, 30 May 2018 21:03:16 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=amDVm5B/8H94R/Ir+COvnrRlerLOrP0SUyovYyvn3pk=; b=BEXsAlRtONw0fCvOjOTiYpfhrM3cn/CpHfEj1FZ/+sa6gH9B18NYt2NYCtBmhNj3qnywa98c9XkWxjwCwBALqHq/LNktgLoRX1jqTTDDxYnD9pZ4cQRt7FTI7g9oc1sapDw0pPu/WaXX7CJNl68wCXqxqFudAVWv98fG0jJE9jE=
Received: from BYAPR15MB2312.namprd15.prod.outlook.com (52.135.197.146) by BYAPR15MB2408.namprd15.prod.outlook.com (52.135.198.148) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.797.11; Thu, 31 May 2018 01:03:15 +0000
Received: from BYAPR15MB2312.namprd15.prod.outlook.com ([fe80::949a:9cbd:277c:96e0]) by BYAPR15MB2312.namprd15.prod.outlook.com ([fe80::949a:9cbd:277c:96e0%4]) with mapi id 15.20.0797.020; Thu, 31 May 2018 01:03:15 +0000
From: Roberto Peon <fenix@fb.com>
To: Mike Bishop <mbishop@evequefou.be>, Martin Thomson <martin.thomson@gmail.com>
CC: QUIC WG <quic@ietf.org>, "Lubashev, Igor" <ilubashe=40akamai.com@dmarc.ietf.org>
Subject: Re: Partially Reliable Message Stream
Thread-Topic: Partially Reliable Message Stream
Thread-Index: AdP4Mo3KTicRHsMuS7e4Jrowbk1vdQAMuR2gAAT/n4AAAG2XyQ==
Date: Thu, 31 May 2018 01:03:14 +0000
Message-ID: <BYAPR15MB2312A20C0FFF67119059D2B3CD630@BYAPR15MB2312.namprd15.prod.outlook.com>
References: <d263c36bc5264842a65f04fc3b017538@ustx2ex-dag1mb6.msg.corp.akamai.com> <SN1PR08MB18541BF8B27EA5484FA6A437DA6C0@SN1PR08MB1854.namprd08.prod.outlook.com>, <CABkgnnWUpaFvz3d0SJJ99JkhdQfwdaxYosKwj3dK9BVZUtZ_yw@mail.gmail.com>
In-Reply-To: <CABkgnnWUpaFvz3d0SJJ99JkhdQfwdaxYosKwj3dK9BVZUtZ_yw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [40.67.186.83]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR15MB2408; 7:7oqAVlH2zcNYYF+VF382ZjGiiUkHj9EgAdG9LbddZRlNye0ZZk7puBTQGjBdwR14CsrXcT3axf1wKzbrec5ZoAr43LoVBKDzvLYAx5mZJouizDpoi70q7sS3aS8EwDOLBCC2X/2LUFPQKxVPfK6PS0OUopVtY9kN6SSXe5I9skTvxoKH8dbDLIvNEXPYFw02OimyMyr/JBydicFUR2bPVDLug5kpHG1LXQs4uDa3kMHYAPl8Ye694yXMYjN7TyZm; 20:rp6nmXDNxpYBfw0sPJxIMSvLBMVhbbIAe2gBuubI1B+1yO9uUTYae9Bz/NzzDZ8Nvimf4PDgZO/oofZ+aDR/qibXbmdVf3W4Ba71x/PKvGbtNQdm76KkTmG4CnKQSFz9O9qqY7i+CYWRSKZRRW6bVMRaMhzvLQuAOmyvOCJbBNY=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BYAPR15MB2408; 
x-ms-traffictypediagnostic: BYAPR15MB2408:
x-microsoft-antispam-prvs: <BYAPR15MB2408E379D30B34D2F9F029D1CD630@BYAPR15MB2408.namprd15.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(190756311086443)(158342451672863)(10436049006162)(85827821059158)(265313219721884);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(93006095)(93001095)(10201501046)(3231254)(11241501184)(944501410)(52105095)(3002001)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123558120)(20161123562045)(6072148)(201708071742011)(7699016); SRVR:BYAPR15MB2408; BCL:0; PCL:0; RULEID:; SRVR:BYAPR15MB2408; 
x-forefront-prvs: 06891E23FB
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(346002)(376002)(366004)(39860400002)(39380400002)(189003)(199004)(110136005)(99286004)(54906003)(478600001)(6246003)(3480700004)(105586002)(229853002)(2906002)(45080400002)(106356001)(102836004)(53936002)(66066001)(59450400001)(2900100001)(316002)(81156014)(8676002)(26005)(55016002)(15650500001)(81166006)(186003)(6436002)(86362001)(575784001)(68736007)(486006)(3660700001)(97736004)(5660300001)(3280700002)(476003)(5250100002)(74316002)(6116002)(3846002)(6306002)(9686003)(54896002)(236005)(53546011)(76176011)(8936002)(14454004)(6506007)(25786009)(7696005)(446003)(39060400002)(11346002)(4326008)(606006)(33656002)(7736002)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR15MB2408; H:BYAPR15MB2312.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: fb.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: +GzY6irqwJLvz0U9j9trvvDH/T9mzVU7EBxUpKTSbFXa0qkh545woM9ZhaSQdpLyeaJBRWM5S1Q3MG+kKovBb+KAq1tTbAaqgh0zA7e4Tel8OYo1uQV3xvYSli/aMquTN3kK82WgOuGLUDxid5081Qd1RiYhcpurTFJIFmiC3EcutzwJWa3NQv51Zd1CSeLZ
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BYAPR15MB2312A20C0FFF67119059D2B3CD630BYAPR15MB2312namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 9ddb7c32-163e-40ea-2b10-08d5c69249f2
X-MS-Exchange-CrossTenant-Network-Message-Id: 9ddb7c32-163e-40ea-2b10-08d5c69249f2
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 May 2018 01:03:14.9519 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR15MB2408
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-30_10:, , signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ryyoVvOj4MaAenT7-DaLXatOHtM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2018 01:03:26 -0000

--_000_BYAPR15MB2312A20C0FFF67119059D2B3CD630BYAPR15MB2312namp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

I find it confusing as well.  I far prefer keeping the offsets monotonicall=
y increasing as it allows for real-world use of a partially reliable stream=
 (where you may not recieve that data but you can at least figure out what =
you did get and interpret it).

I dont know how one wohud resolve the race even within the sending applicat=
ion -- one thread sends, another thread sends while the first says to forge=
t about stuff. I dont know what offset stuff ends up at in such cases, and =
so I cannot frame data in a way that is non-synchronous. That defeats some =
of the main reasons to do partial reliability (i.e. to reduce jitter).

Draft 02 seemed to be going in a better direction w.r.t the usecases i can =
conceive of. I think rewinding to that and then potentially figuring out ho=
w to simplify it would be fun!

I'm excited to have this being discussed, since there is pent up demand to =
use it already.
-=3DR

Get Outlook for Android<https://aka.ms/ghei36>

________________________________
From: QUIC <quic-bounces@ietf.org> on behalf of Martin Thomson <martin.thom=
son@gmail.com>
Sent: Wednesday, May 30, 2018 5:50:59 PM
To: Mike Bishop
Cc: QUIC WG; Lubashev, Igor
Subject: Re: Partially Reliable Message Stream

Like Mike, I find this gap thing confusing.  And Mike's message
helped, but not a lot.

It took a while to realize that forcing a gap creates a new starting
point for the next message that forces the recipient to recognize and
deal with.  However, the logic for identifying that is just hard and
it's an unnecessary imposition in my view.

Say I send a message with a length of 10 and only two octets make it
onto the wire (as with your example), then it is immediately
abandoned.  Your solution would have the EXPIRED_STREAM_DATA force a
gap after the second octet, so that the next message could start at
offset 3 rather than offset 10.  That saves the remaining 7 octets of
flow control credit.  (Use bigger numbers and perhaps it seems more
motivating).

If the octets that cover the gap were sent, then you have a problem
because now you have sent two versions of the same octets, so you can
only do this if the octets were never sent.  It starts to get closer
and closer to the point where a new stream is just easier.

Worst, I think is that the receiver has to have complicated logic for
identifying that a gap exists and dealing with it.  It has to read up
to what it has, observe that the data has expired, then learn where
the gap ends, then resynchronize based on 1+gap_end for the next
message.

Better to eat the flow control cost in my view.  Or send RST_STREAM
and make another stream.
On Thu, May 31, 2018 at 8:48 AM Mike Bishop <mbishop@evequefou.be> wrote:
>
> I find the one octet gap a bit confusing, but as I think about it, I see =
why you need it.  If all the stream data arrived successfully (but hadn=92t=
 been acknowledged yet due to loss of the ACK, delay, etc.) and the EXPIRED=
_STREAM_DATA gets lost, the receiver can only retroactively realize there w=
as a jump.  Having an octet that is never transmitted ensures the receiver =
actually sees a gap, which means that an in-order API will not proceed unti=
l it has received either the missing octet or an EXPIRED_STREAM_DATA inform=
ing it the octet will never arrive.
>
>
>
> This simplification (versus -02) comes at a price:  If an API were exposi=
ng stream data out-of-order, then in your example, the receiver knows that =
a message always begins on a ten-byte boundary.  A receiver can no longer f=
ind ten-byte boundaries, because the offset on the read side doesn=92t matc=
h the offset on the send side.  I agree with you that this seems like a rea=
sonable trade-off for the simpler flow control.
>
>
>
> One conflict I see in the doc:
>
> =B7         Section 3 says:  Receipt of an EXPIRED_STREAM_DATA does not a=
dvance the largest received offset for the stream.
>
> Section 5 says:  A receiver SHOULD discard any stream data received for a=
n offset smaller than the new smallest receive offset, possibly advancing t=
he largest received offset for the stream.
>
>
>
> Other minor nits are better done via PR.
>
> From: QUIC <quic-bounces@ietf.org> On Behalf Of Lubashev, Igor
> Sent: Wednesday, May 30, 2018 9:45 AM
> To: QUIC WG <quic@ietf.org>
> Subject: Partially Reliable Message Stream
>
>
>
> I=92ve just uploaded a new draft for partially reliable QUIC streams.  No=
te: this feature is likely not in scope for V1, but it can be an extension =
for V1 and/or a part of V2.
>
>
>
> The new version 03 (https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A=
__tools.ietf.org_html_draft-2Dlubashev-2Dquic-2Dpartial-2Dreliability-2D03&=
d=3DDwIFaQ&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3DC0sUo-LFNBaYfyoaCsf6TA&m=3DyyRpbe=
14kTYgY413gjVkOalWE_UC3xYerKpJqS8HiQo&s=3DXZ295xiZsN11yP8GLcdMs1jf7z0b2_Whi=
IxMLLorZXo&e=3D) no longer needs complex flow control changes and removes t=
he need to transmit multiple frames in the same packet.
>
>
>
> Igor
>
>
>
> P.S.
>
>   There is also a new version 02, which includes a more complex algorithm=
 with more features and different trade-offs.  But I think version 03 is a =
better match for the needs so far.


--_000_BYAPR15MB2312A20C0FFF67119059D2B3CD630BYAPR15MB2312namp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<meta name=3D"Generator" content=3D"Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; pad=
ding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
I find it confusing as well.&nbsp; I far prefer keeping the offsets monoton=
ically increasing as it allows for real-world use of a partially reliable s=
tream (where you may not recieve that data but you can at least figure out =
what you did get and interpret it).<br>
<br>
</div>
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
I dont know how one wohud resolve the race even within the sending applicat=
ion -- one thread sends, another thread sends while the first says to forge=
t about stuff. I dont know what offset stuff ends up at in such cases, and =
so I cannot frame data in a way
 that is non-synchronous. That defeats some of the main reasons to do parti=
al reliability (i.e. to reduce jitter).<br>
<br>
</div>
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
Draft 02 seemed to be going in a better direction w.r.t the usecases i can =
conceive of. I think rewinding to that and then potentially figuring out ho=
w to simplify it would be fun!<br>
<br>
</div>
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
I'm excited to have this being discussed, since there is pent up demand to =
use it already.<br>
</div>
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
-=3DR<br>
<br>
</div>
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
<div dir=3D"auto" style=3D"direction:ltr; margin:0; padding:0; font-family:=
sans-serif; font-size:11pt; color:black">
Get <a href=3D"https://aka.ms/ghei36">Outlook for Android</a></div>
<br>
</div>
<hr tabindex=3D"-1" style=3D"display:inline-block; width:98%">
<div id=3D"x_divRplyFwdMsg" dir=3D"ltr"><font face=3D"Calibri, sans-serif" =
color=3D"#000000" style=3D"font-size:11pt"><b>From:</b> QUIC &lt;quic-bounc=
es@ietf.org&gt; on behalf of Martin Thomson &lt;martin.thomson@gmail.com&gt=
;<br>
<b>Sent:</b> Wednesday, May 30, 2018 5:50:59 PM<br>
<b>To:</b> Mike Bishop<br>
<b>Cc:</b> QUIC WG; Lubashev, Igor<br>
<b>Subject:</b> Re: Partially Reliable Message Stream</font>
<div>&nbsp;</div>
</div>
</div>
<font size=3D"2"><span style=3D"font-size:11pt;">
<div class=3D"PlainText">Like Mike, I find this gap thing confusing.&nbsp; =
And Mike's message<br>
helped, but not a lot.<br>
<br>
It took a while to realize that forcing a gap creates a new starting<br>
point for the next message that forces the recipient to recognize and<br>
deal with.&nbsp; However, the logic for identifying that is just hard and<b=
r>
it's an unnecessary imposition in my view.<br>
<br>
Say I send a message with a length of 10 and only two octets make it<br>
onto the wire (as with your example), then it is immediately<br>
abandoned.&nbsp; Your solution would have the EXPIRED_STREAM_DATA force a<b=
r>
gap after the second octet, so that the next message could start at<br>
offset 3 rather than offset 10.&nbsp; That saves the remaining 7 octets of<=
br>
flow control credit.&nbsp; (Use bigger numbers and perhaps it seems more<br=
>
motivating).<br>
<br>
If the octets that cover the gap were sent, then you have a problem<br>
because now you have sent two versions of the same octets, so you can<br>
only do this if the octets were never sent.&nbsp; It starts to get closer<b=
r>
and closer to the point where a new stream is just easier.<br>
<br>
Worst, I think is that the receiver has to have complicated logic for<br>
identifying that a gap exists and dealing with it.&nbsp; It has to read up<=
br>
to what it has, observe that the data has expired, then learn where<br>
the gap ends, then resynchronize based on 1&#43;gap_end for the next<br>
message.<br>
<br>
Better to eat the flow control cost in my view.&nbsp; Or send RST_STREAM<br=
>
and make another stream.<br>
On Thu, May 31, 2018 at 8:48 AM Mike Bishop &lt;mbishop@evequefou.be&gt; wr=
ote:<br>
&gt;<br>
&gt; I find the one octet gap a bit confusing, but as I think about it, I s=
ee why you need it.&nbsp; If all the stream data arrived successfully (but =
hadn=92t been acknowledged yet due to loss of the ACK, delay, etc.) and the=
 EXPIRED_STREAM_DATA gets lost, the receiver
 can only retroactively realize there was a jump.&nbsp; Having an octet tha=
t is never transmitted ensures the receiver actually sees a gap, which mean=
s that an in-order API will not proceed until it has received either the mi=
ssing octet or an EXPIRED_STREAM_DATA
 informing it the octet will never arrive.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; This simplification (versus -02) comes at a price:&nbsp; If an API wer=
e exposing stream data out-of-order, then in your example, the receiver kno=
ws that a message always begins on a ten-byte boundary.&nbsp; A receiver ca=
n no longer find ten-byte boundaries, because
 the offset on the read side doesn=92t match the offset on the send side.&n=
bsp; I agree with you that this seems like a reasonable trade-off for the s=
impler flow control.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; One conflict I see in the doc:<br>
&gt;<br>
&gt; =B7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Section 3 says:&nb=
sp; Receipt of an EXPIRED_STREAM_DATA does not advance the largest received=
 offset for the stream.<br>
&gt;<br>
&gt; Section 5 says:&nbsp; A receiver SHOULD discard any stream data receiv=
ed for an offset smaller than the new smallest receive offset, possibly adv=
ancing the largest received offset for the stream.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Other minor nits are better done via PR.<br>
&gt;<br>
&gt; From: QUIC &lt;quic-bounces@ietf.org&gt; On Behalf Of Lubashev, Igor<b=
r>
&gt; Sent: Wednesday, May 30, 2018 9:45 AM<br>
&gt; To: QUIC WG &lt;quic@ietf.org&gt;<br>
&gt; Subject: Partially Reliable Message Stream<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; I=92ve just uploaded a new draft for partially reliable QUIC streams.&=
nbsp; Note: this feature is likely not in scope for V1, but it can be an ex=
tension for V1 and/or a part of V2.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The new version 03 (<a href=3D"https://urldefense.proofpoint.com/v2/ur=
l?u=3Dhttps-3A__tools.ietf.org_html_draft-2Dlubashev-2Dquic-2Dpartial-2Drel=
iability-2D03&amp;d=3DDwIFaQ&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3DC0sUo-L=
FNBaYfyoaCsf6TA&amp;m=3DyyRpbe14kTYgY413gjVkOalWE_UC3xYerKpJqS8HiQo&amp;s=
=3DXZ295xiZsN11yP8GLcdMs1jf7z0b2_WhiIxMLLorZXo&amp;e=3D">https://urldefense=
.proofpoint.com/v2/url?u=3Dhttps-3A__tools.ietf.org_html_draft-2Dlubashev-2=
Dquic-2Dpartial-2Dreliability-2D03&amp;d=3DDwIFaQ&amp;c=3D5VD0RTtNlTh3ycd41=
b3MUw&amp;r=3DC0sUo-LFNBaYfyoaCsf6TA&amp;m=3DyyRpbe14kTYgY413gjVkOalWE_UC3x=
YerKpJqS8HiQo&amp;s=3DXZ295xiZsN11yP8GLcdMs1jf7z0b2_WhiIxMLLorZXo&amp;e=3D<=
/a>)
 no longer needs complex flow control changes and removes the need to trans=
mit multiple frames in the same packet.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Igor<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; P.S.<br>
&gt;<br>
&gt;&nbsp;&nbsp; There is also a new version 02, which includes a more comp=
lex algorithm with more features and different trade-offs.&nbsp; But I thin=
k version 03 is a better match for the needs so far.<br>
<br>
</div>
</span></font>
</body>
</html>

--_000_BYAPR15MB2312A20C0FFF67119059D2B3CD630BYAPR15MB2312namp_--


From nobody Wed May 30 18:20:48 2018
Return-Path: <ilubashe@akamai.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6FC8C12EAF2 for <quic@ietfa.amsl.com>; Wed, 30 May 2018 18:20:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.72
X-Spam-Level: 
X-Spam-Status: No, score=-0.72 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 kpVHPOxGm8Tb for <quic@ietfa.amsl.com>; Wed, 30 May 2018 18:20:43 -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 A875412EAF7 for <quic@ietf.org>; Wed, 30 May 2018 18:20:43 -0700 (PDT)
Received: from pps.filterd (m0122333.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w4V1HE5T005040; Thu, 31 May 2018 02:20:40 +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 : mime-version; s=jan2016.eng; bh=eri4NMko+aMsTyuPfvuYfA8pPiU7dntTDmx9SY0n8d0=; b=jNEwLUJwy/8+UEzINXfAsx7UcQRhbGlstdN4m4vcjqAN3wLJiU7cQk5+uAs+S3qVpb9K eq2SkP+PhKvWjd+9bXyTZYvbkEZRQzsmtpf5LMMIVY5oMdykkGtqlkKt6WbLkKwmCjia K3xOANFs9g7DZUZQgsZD2ZPbbS0lekqy/im0c1SUQCDFzWC1orRkY3ejlbzxCFalmcoy g5fZKpmMkqlC2gWz9DfeQUJTSRoW30fBbOvQly9XFfAXoOx1051thR5+UPBkzFOGoJBP Q4O///rXTYBzp+H2uU+Ug+mQu8womFeZe/CqSy/hjdcNydW04WKfaTuyQ7It1NESF0KB Ug== 
Received: from prod-mail-ppoint3 (a96-6-114-86.deploy.static.akamaitechnologies.com [96.6.114.86] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 2j9cw5mxwr-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 31 May 2018 02:20:40 +0100
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w4V1GM5Y024828; Wed, 30 May 2018 21:20:39 -0400
Received: from email.msg.corp.akamai.com ([172.27.25.34]) by prod-mail-ppoint3.akamai.com with ESMTP id 2j9cvv6c1c-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Wed, 30 May 2018 21:20:39 -0400
Received: from ustx2ex-dag1mb6.msg.corp.akamai.com (172.27.27.107) by ustx2ex-dag1mb1.msg.corp.akamai.com (172.27.27.101) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Wed, 30 May 2018 20:20:28 -0500
Received: from ustx2ex-dag1mb6.msg.corp.akamai.com ([172.27.27.107]) by ustx2ex-dag1mb6.msg.corp.akamai.com ([172.27.27.107]) with mapi id 15.00.1365.000; Wed, 30 May 2018 18:20:28 -0700
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: "quic@ietf.org" <quic@ietf.org>, "mbishop@evequefou.be" <mbishop@evequefou.be>
Subject: RE: Partially Reliable Message Stream
Thread-Topic: Partially Reliable Message Stream
Thread-Index: AdP4Mo3KTicRHsMuS7e4Jrowbk1vdQAMuR2gAAYHOXA=
Date: Thu, 31 May 2018 01:20:28 +0000
Message-ID: <56752d2e4628483caf2456ba31257844@ustx2ex-dag1mb6.msg.corp.akamai.com>
References: <d263c36bc5264842a65f04fc3b017538@ustx2ex-dag1mb6.msg.corp.akamai.com>,  <SN1PR08MB18541BF8B27EA5484FA6A437DA6C0@SN1PR08MB1854.namprd08.prod.outlook.com>
In-Reply-To: <SN1PR08MB18541BF8B27EA5484FA6A437DA6C0@SN1PR08MB1854.namprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
Content-Type: multipart/alternative; boundary="_000_56752d2e4628483caf2456ba31257844ustx2exdag1mb6msgcorpak_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-30_10:, , 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-1805220000 definitions=main-1805310012
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-30_10:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1805220000 definitions=main-1805310012
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/XsZOA1qArkZMH7p316eGBvp0FK4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2018 01:20:47 -0000

--_000_56752d2e4628483caf2456ba31257844ustx2exdag1mb6msgcorpak_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Thanks for the review, Mike!

Yes, you got the purpose of the gap exactly right.

> Conflict in the doc.

Actually, I do not see a conflict, but it is true that the accounting is tr=
icky, and the wording could be a bit better. The receiver maintains two dis=
tinct variables:
* smallest receive offset -- the smallest offset it is waiting for
* largest received offset -- just what it says, probably used for nothing e=
lse by the receiver but verifying compliance with flow control (important, =
since "largest received offset" - "smallest receive offset" =3D "size of in=
-use receive buffer" for the stream).

The quotation from section 5 says that when a new STREAM frame is received,=
 data at offsets smaller than "smallest receive offset" should be discarded=
 (since the receiver should not care for it anymore -- it is expired), but =
"largest received offset" should still advance if needed (since data has be=
en received -- compliance with flow control is still required for STREAM fr=
ames).

-----Original Message-----
From: Mike Bishop [mbishop@evequefou.be]
Received: Wednesday, 30 May 2018, 6:47PM
To: Lubashev, Igor [ilubashe@akamai.com]; QUIC WG [quic@ietf.org]
Subject: RE: Partially Reliable Message Stream

I find the one octet gap a bit confusing, but as I think about it, I see wh=
y you need it.  If all the stream data arrived successfully (but hadn't bee=
n acknowledged yet due to loss of the ACK, delay, etc.) and the EXPIRED_STR=
EAM_DATA gets lost, the receiver can only retroactively realize there was a=
 jump.  Having an octet that is never transmitted ensures the receiver actu=
ally sees a gap, which means that an in-order API will not proceed until it=
 has received either the missing octet or an EXPIRED_STREAM_DATA informing =
it the octet will never arrive.

This simplification (versus -02) comes at a price:  If an API were exposing=
 stream data out-of-order, then in your example, the receiver knows that a =
message always begins on a ten-byte boundary.  A receiver can no longer fin=
d ten-byte boundaries, because the offset on the read side doesn't match th=
e offset on the send side.  I agree with you that this seems like a reasona=
ble trade-off for the simpler flow control.

One conflict I see in the doc:

*         Section 3 says:  Receipt of an EXPIRED_STREAM_DATA does not advan=
ce the largest received offset for the stream.

  *   Section 5 says:  A receiver SHOULD discard any stream data received f=
or an offset smaller than the new smallest receive offset, possibly advanci=
ng the largest received offset for the stream.

Other minor nits are better done via PR.
From: QUIC <quic-bounces@ietf.org> On Behalf Of Lubashev, Igor
Sent: Wednesday, May 30, 2018 9:45 AM
To: QUIC WG <quic@ietf.org>
Subject: Partially Reliable Message Stream

I've just uploaded a new draft for partially reliable QUIC streams.  Note: =
this feature is likely not in scope for V1, but it can be an extension for =
V1 and/or a part of V2.

The new version 03 (https://tools.ietf.org/html/draft-lubashev-quic-partial=
-reliability-03<https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__tool=
s.ietf.org_html_draft-2Dlubashev-2Dquic-2Dpartial-2Dreliability-2D03&d=3DDw=
MFAg&c=3D96ZbZZcaMF4w0F4jpN6LZg&r=3DDjn3bQ5uNJDPM_2skfL3rW1tzcIxyjUZdn_m55K=
Pmlo&m=3D_kwXz2JdtqD8uvvd8h8cZ-GQ3_FgDf7dRoorJ-DYVhg&s=3Dt0au9Hcc2L02NXlpLb=
99Y4e-72lBv2kC2hHZuGifUWg&e=3D>) no longer needs complex flow control chang=
es and removes the need to transmit multiple frames in the same packet.


  *   Igor

P.S.
  There is also a new version 02, which includes a more complex algorithm w=
ith more features and different trade-offs.  But I think version 03 is a be=
tter match for the needs so far.

--_000_56752d2e4628483caf2456ba31257844ustx2exdag1mb6msgcorpak_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta content=3D"text/html; charset=3Dus-ascii">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style>
<!--
@font-face
	{font-family:Wingdings}
@font-face
	{font-family:"Cambria Math"}
@font-face
	{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif}
a:link, span.MsoHyperlink
	{color:#0563C1;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:#954F72;
	text-decoration:underline}
pre
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New"}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif}
p.msonormal0, li.msonormal0, div.msonormal0
	{margin-right:0in;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif}
span.EmailStyle19
	{font-family:"Calibri",sans-serif;
	color:windowtext}
span.EmailStyle20
	{font-family:"Calibri",sans-serif;
	color:windowtext}
span.EmailStyle21
	{font-family:"Calibri",sans-serif;
	color:windowtext}
span.HTMLPreformattedChar
	{font-family:"Courier New"}
@page WordSection1
	{margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
	{}
ol
	{margin-bottom:0in}
ul
	{margin-bottom:0in}
-->
</style>
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<span style=3D"font-family:Calibri,Arial,Helvetica,sans-serif; font-size:11=
pt; color:black">Thanks for the review, Mike!<br>
<br>
Yes, you got the purpose of the gap exactly right.<br>
<br>
&gt; Conflict in the doc.<br>
<br>
Actually, I do not see a conflict, but it is true that the accounting is tr=
icky, and the wording could be a bit better. The receiver maintains two dis=
tinct variables:<br>
* smallest receive offset -- the smallest offset it is waiting for<br>
* largest received offset -- just what it says, probably used for nothing e=
lse by the receiver but verifying compliance with flow control (important, =
since &quot;largest received offset&quot; - &quot;smallest receive offset&q=
uot; =3D &quot;size of in-use receive buffer&quot; for the stream).<br>
<br>
The quotation from section 5 says that when a new STREAM frame is received,=
 data at offsets smaller than &quot;smallest receive offset&quot; should be=
 discarded (since the receiver should not care for it anymore -- it is expi=
red), but &quot;largest received offset&quot; should
 still advance if needed (since data has been received -- compliance with f=
low control is still required for STREAM frames).<br>
<br>
<span style=3D"color:black">-----Original Message----- <br>
<b>From:</b> Mike Bishop [mbishop@evequefou.be]<br>
<b>Received:</b> Wednesday, 30 May 2018, 6:47PM<br>
<b>To:</b> Lubashev, Igor [ilubashe@akamai.com]; QUIC WG [quic@ietf.org]<br=
>
<b>Subject:</b> RE: Partially Reliable Message Stream<br>
<br>
</span></span>
<div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal">I find the one octet gap a bit confusing, but as I t=
hink about it, I see why you need it.&nbsp; If all the stream data arrived =
successfully (but hadn&#8217;t been acknowledged yet due to loss of the ACK=
, delay, etc.)
<i>and</i> the EXPIRED_STREAM_DATA gets lost, the receiver can only retroac=
tively realize there was a jump.&nbsp; Having an octet that is never transm=
itted ensures the receiver actually
<i>sees</i> a gap, which means that an in-order API will not proceed until =
it has received either the missing octet or an EXPIRED_STREAM_DATA informin=
g it the octet will never arrive.</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">This simplification (versus -02) comes at a price:&n=
bsp; If an API were exposing stream data out-of-order, then in your example=
, the receiver knows that a message always begins on a ten-byte boundary.&n=
bsp; A receiver can no longer find ten-byte
 boundaries, because the offset on the read side doesn&#8217;t match the of=
fset on the send side.&nbsp; I agree with you that this seems like a reason=
able trade-off for the simpler flow control.</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">One conflict I see in the doc:</p>
<pre style=3D"margin-left:.5in; text-indent:-.25in"><span style=3D"font-fam=
ily:Symbol"><span style=3D"">&middot;<span style=3D"font:7.0pt &quot;Times =
New Roman&quot;">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; </span></=
span></span><span style=3D"font-size:11.0pt; font-family:&quot;Calibri&quot=
;,sans-serif">Section 3 says:</span><span style=3D"font-family:&quot;Calibr=
i&quot;,sans-serif">&nbsp; </span>Receipt of an EXPIRED_STREAM_DATA <b>does=
 not advance the largest received offset for the stream</b>.</pre>
<ul type=3D"disc" style=3D"margin-top:0in">
<li class=3D"MsoListParagraph" style=3D"margin-left:0in">Section 5 says:&nb=
sp; <span style=3D"font-size:10.0pt; font-family:&quot;Courier New&quot;">
A receiver SHOULD discard any stream data received for an offset smaller th=
an the new smallest receive offset,
<b>possibly advancing the largest received offset for the stream</b>.</span=
></li></ul>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">Other minor nits are better done via PR.</p>
<p class=3D"MsoNormal"></p>
<div>
<div style=3D"border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0i=
n 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> QUIC &lt;quic-bounces@ietf.org&gt; <b>O=
n Behalf Of </b>
Lubashev, Igor<br>
<b>Sent:</b> Wednesday, May 30, 2018 9:45 AM<br>
<b>To:</b> QUIC WG &lt;quic@ietf.org&gt;<br>
<b>Subject:</b> Partially Reliable Message Stream</p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">I&#8217;ve just uploaded a new draft for partially r=
eliable QUIC streams.&nbsp; Note: this feature is likely not in scope for V=
1, but it can be an extension for V1 and/or a part of V2.</p>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">The new version 03 (<a href=3D"https://urldefense.pr=
oofpoint.com/v2/url?u=3Dhttps-3A__tools.ietf.org_html_draft-2Dlubashev-2Dqu=
ic-2Dpartial-2Dreliability-2D03&amp;d=3DDwMFAg&amp;c=3D96ZbZZcaMF4w0F4jpN6L=
Zg&amp;r=3DDjn3bQ5uNJDPM_2skfL3rW1tzcIxyjUZdn_m55KPmlo&amp;m=3D_kwXz2JdtqD8=
uvvd8h8cZ-GQ3_FgDf7dRoorJ-DYVhg&amp;s=3Dt0au9Hcc2L02NXlpLb99Y4e-72lBv2kC2hH=
ZuGifUWg&amp;e=3D">https://tools.ietf.org/html/draft-lubashev-quic-partial-=
reliability-03</a>)
 no longer needs complex flow control changes and removes the need to trans=
mit multiple frames in the same packet.</p>
<p class=3D"MsoNormal">&nbsp;</p>
<ul type=3D"disc" style=3D"margin-top:0in">
<li class=3D"MsoNormal" style=3D"">Igor</li></ul>
<p class=3D"MsoNormal">&nbsp;</p>
<p class=3D"MsoNormal">P.S.</p>
<p class=3D"MsoNormal">&nbsp; There is also a new version 02, which include=
s a more complex algorithm with more features and different trade-offs.&nbs=
p; But I think version 03 is a better match for the needs so far.</p>
</div>
</div>
</body>
</html>

--_000_56752d2e4628483caf2456ba31257844ustx2exdag1mb6msgcorpak_--


From nobody Wed May 30 20:21:21 2018
Return-Path: <mnot@mnot.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EFD812EC77 for <quic@ietfa.amsl.com>; Wed, 30 May 2018 20:21:20 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=SzShoFkB; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=KTGiWfTT
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 BUeJmxDmaGzq for <quic@ietfa.amsl.com>; Wed, 30 May 2018 20:21:17 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id BD3BF12DDD2 for <quic@ietf.org>; Wed, 30 May 2018 20:21:14 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id CCC0C217A8; Wed, 30 May 2018 23:21:13 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Wed, 30 May 2018 23:21:13 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-transfer-encoding:content-type:date:from:message-id :mime-version:subject:to:x-me-sender:x-me-sender:x-sasl-enc; s= fm2; bh=Zgtu9sDmK9guPdvJJF4Kw6m7RzY7jFr6CMSg8j02gfo=; b=SzShoFkB VOZZ1v++Bt0X6T9snQDiNmfyXqbFCo6PVBqKGrKxqXtzEckYygcCvv065Fv7Ob8/ sKAdvM/DdfNAXwaDCyqoAB7wPWQAyjwu3XsnihlATz7yOpyo/50LOdJtGFGNQVim a2vgHU2QsBMWTq9xKISGiyQ4qJ64c/xm49FYhE38k4Vtl8n+SjkNef9i6XwJ2Sb/ xWmv8ESAQrtHGDsWS52baqpNuhVPlC0bKKgO1W1s6wxKAtyfhfin7Rnn/Q00kJ05 Ef7boZ7haEMKinGEErdGt+FzOP4JrSuSLqBb65UefHDYo2tjN8HTHUb45OC1qO9i DLE6mZz9Ou/M3g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:message-id:mime-version:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=Zgtu9sDmK9guPdvJJF4Kw6m7RzY7j Fr6CMSg8j02gfo=; b=KTGiWfTTALnVATs2u3RNGO109llsljx/2B+eceGCvGR7Q wTTA/6k2/5OBMpNLS+D/r5WN2PQhJ7f6KFaJvMHBetjkW6R7BHvnNMyp/M5GwI2p a9ChdIlawyb3kLjlKglrIoI00rjvnwp6UuqcMVS/8k/VQ1UwpSyZbPB9Ll2VL8h6 aUI8I3YoAlFG3ZDAp454+Ua3soW6jHSFdXUpHZclS7ilSj7KkB5wMNzi7MpNnolR 2aAjDJ2eXw83PERl9y3sqVZhElCiKUuvWCJB/raVviyV7UcQKXz+ekoPP6+9dsZx to8fzJ9lfpwlBn27kCGBe+xGwDs8oB7xGlwX6PIxA==
X-ME-Proxy: <xmx:KWoPW4R0et1fOg61sAl_NgXtLpA-eWLhppjP-lUoZ8S3gMZKVrvPPA>
X-ME-Proxy: <xmx:KWoPWxXeuUEsNcXQFlw7lrmyVnS8kVbUGxNmw7OhUWXF79OSMjYcpw>
X-ME-Proxy: <xmx:KWoPW9G21R8mKFx6v_vcvE1Zz86xykw7aGBrk9WpdLF5n0Y_Hz_utg>
X-ME-Proxy: <xmx:KWoPW0bgvqb-_2hhBkhJekkk0Gxxg24P_dNVk543ZZjWOftnyeKDCg>
X-ME-Proxy: <xmx:KWoPW9RnIWoMWMpxqE0dsVGsNYJqgYKjaAA75VkniI-E7UEMerB5zA>
X-ME-Proxy: <xmx:KWoPWxyrg1fN8XcFynfRmv4oznht9Z8_qO4Ip5LVlBdINhTFpDH3Qg>
X-ME-Sender: <xms:KWoPWwh5NrnKaZTGZknUUpFPQuhgmOX7na8ALPAEs1xbQ947ffCWBw>
Received: from attitudadjuster.localdomain (unknown [144.136.175.28]) by mail.messagingengine.com (Postfix) with ESMTPA id 9B6B410255; Wed, 30 May 2018 23:21:12 -0400 (EDT)
From: Mark Nottingham <mnot@mnot.net>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Subject: Q3 2018 interim planning
Message-Id: <F26E202D-78CA-4E24-9A6B-4D14ED951FB7@mnot.net>
Date: Thu, 31 May 2018 13:21:09 +1000
Cc: Lars Eggert <lars@eggert.org>
To: IETF QUIC WG <quic@ietf.org>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/1vlbqie2rgRdXdxTk8tzFhfsJfo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2018 03:21:21 -0000

QUIC folks,

We're in the final stages of planning our next interim meeting (between =
the Montreal and Bangkok IETF meetings).

Previously, we'd said that we'd avoid holding meetings in the US, due to =
some uncertainty about the application of entry requirements.

It appears that that concern is no longer so great, and as far as we can =
tell entry to the US should not pose a significant issue for our usual =
participants. At the same time, we do know of at least one case where a =
person would like to attend our meetings, but cannot due to visa issues =
getting *out* of the US.

As a result, we're planning on holding our Q3 meeting this year in the =
US. If you believe this means you would not be able to attend when you =
otherwise would, please contact Lars and I as soon as possible.

Regards,

--
Mark Nottingham   https://www.mnot.net/


From nobody Wed May 30 20:31:48 2018
Return-Path: <mbishop@evequefou.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 61FD1131641 for <quic@ietfa.amsl.com>; Wed, 30 May 2018 20:31:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.08
X-Spam-Level: 
X-Spam-Status: No, score=0.08 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=1.989, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 6SeRyFJQJsLb for <quic@ietfa.amsl.com>; Wed, 30 May 2018 20:31:43 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0095.outbound.protection.outlook.com [104.47.33.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5BB26131637 for <quic@ietf.org>; Wed, 30 May 2018 20:31:43 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=d0IvRq10baq9exOBuDmUuSytUGWNVpBhFcFUh64n4OY=; b=WWD6txjsDvNmjpK7dY8XYu6PlSnkdN3YvgJovoEYaNXVt3Ob3YiG1b2bH6RK1P+9mLqCvc3tjLTorTYUMW3xRGUzk8+PY7lVu49REyRSBycgTQxpawWhh9ujs72Biqed5s7CmICoY45WlYvHljgPckEuYDgyTrmDxMsAQFSft+8=
Received: from SN1PR08MB1854.namprd08.prod.outlook.com (10.169.39.8) by SN1PR08MB1678.namprd08.prod.outlook.com (10.162.133.140) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.20.797.11; Thu, 31 May 2018 03:31:40 +0000
Received: from SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::c1ff:4f0e:a59b:b9a9]) by SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::c1ff:4f0e:a59b:b9a9%13]) with mapi id 15.20.0797.020; Thu, 31 May 2018 03:31:40 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: "Lubashev, Igor" <ilubashe@akamai.com>, "quic@ietf.org" <quic@ietf.org>
Subject: RE: Partially Reliable Message Stream
Thread-Topic: Partially Reliable Message Stream
Thread-Index: AdP4Mo3KTicRHsMuS7e4Jrowbk1vdQAMuR2gAAYHOXAABI83QA==
Date: Thu, 31 May 2018 03:31:40 +0000
Message-ID: <SN1PR08MB18543DDEB2765F23109E5949DA630@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <d263c36bc5264842a65f04fc3b017538@ustx2ex-dag1mb6.msg.corp.akamai.com>,  <SN1PR08MB18541BF8B27EA5484FA6A437DA6C0@SN1PR08MB1854.namprd08.prod.outlook.com> <56752d2e4628483caf2456ba31257844@ustx2ex-dag1mb6.msg.corp.akamai.com>
In-Reply-To: <56752d2e4628483caf2456ba31257844@ustx2ex-dag1mb6.msg.corp.akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [2601:600:8080:5a28:5405:472:6b:afc4]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN1PR08MB1678; 7:Xn+LOwPqpCcJVKzrfxf+X+AKFpNviv+e8v97kpwAXVmH5J7jy0FItVyqd9PglzoBo1oZmcHlZPR8x2829Yx1GjEUABqq1MaDnMQkGFMW2z41bVa+lWj5lRKXjgsLIMFehcDs8N7TXkIHmDWFWd36l40SbssbgqrH88UsKf8szCFeL/aX3O0kY20xlkz/XGy/B+XV0xKiYIVwc0IZmUPa+OqeoWUK68/Raa7iRr2TKjDCKuB/M+7u+M7JJVl4S0yX
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(5600026)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(2017052603328)(7153060)(7193020); SRVR:SN1PR08MB1678; 
x-ms-traffictypediagnostic: SN1PR08MB1678:
x-microsoft-antispam-prvs: <SN1PR08MB1678EFB2D613B548CC9C23D4DA630@SN1PR08MB1678.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(10436049006162)(21748063052155); 
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(10201501046)(3002001)(93006095)(93001095)(3231254)(944501410)(52105095)(149027)(150027)(6041310)(20161123560045)(20161123562045)(2016111802025)(20161123564045)(20161123558120)(6072148)(6043046)(201708071742011)(7699016); SRVR:SN1PR08MB1678; BCL:0; PCL:0; RULEID:; SRVR:SN1PR08MB1678; 
x-forefront-prvs: 06891E23FB
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(376002)(39380400002)(39830400003)(396003)(366004)(189003)(199004)(51914003)(13464003)(316002)(68736007)(2906002)(59450400001)(5660300001)(5250100002)(15650500001)(606006)(2420400007)(3660700001)(3280700002)(33656002)(3480700004)(106356001)(476003)(8936002)(8676002)(76176011)(229853002)(7736002)(486006)(7696005)(6116002)(790700001)(81166006)(86362001)(46003)(110136005)(14454004)(55016002)(74482002)(11346002)(81156014)(186003)(446003)(99286004)(105586002)(102836004)(7110500001)(74316002)(478600001)(2501003)(25786009)(97736004)(236005)(6306002)(2900100001)(53546011)(53936002)(54896002)(9686003)(6436002)(6506007)(6246003); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR08MB1678; H:SN1PR08MB1854.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: hFPQZmBmE+ZunAEU1RbcHPkzx3WmlLqAjn4G4OMmpOB+rM9MoAM1P2MmTDEuSn9T1eGrxXobAql/G/RC4mc192IFEYY9jZWZbrF+zHUo/LKJ8q6Kv1lK4VuTizI90ur+rK7I9SSDxArXAmb26CtC+1C2nbbIRJ3cR+PjFsxnkvmdl9m3OwYdre+6mSIBfB5R
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_SN1PR08MB18543DDEB2765F23109E5949DA630SN1PR08MB1854namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: e066508f-d3ed-43a3-b545-08d5c6a705ea
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: e066508f-d3ed-43a3-b545-08d5c6a705ea
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 May 2018 03:31:40.2180 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR08MB1678
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/YHXaGgchQA6GK_uwDUA94LTn3a0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2018 03:31:47 -0000

--_000_SN1PR08MB18543DDEB2765F23109E5949DA630SN1PR08MB1854namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Ah, I see - the second is talking about actions taken on receipt of a STREA=
M frame, not an ESD frame; I missed that.

From: Lubashev, Igor <ilubashe@akamai.com>
Sent: Wednesday, May 30, 2018 6:20 PM
To: quic@ietf.org; Mike Bishop <mbishop@evequefou.be>
Subject: RE: Partially Reliable Message Stream

Thanks for the review, Mike!

Yes, you got the purpose of the gap exactly right.

> Conflict in the doc.

Actually, I do not see a conflict, but it is true that the accounting is tr=
icky, and the wording could be a bit better. The receiver maintains two dis=
tinct variables:
* smallest receive offset -- the smallest offset it is waiting for
* largest received offset -- just what it says, probably used for nothing e=
lse by the receiver but verifying compliance with flow control (important, =
since "largest received offset" - "smallest receive offset" =3D "size of in=
-use receive buffer" for the stream).

The quotation from section 5 says that when a new STREAM frame is received,=
 data at offsets smaller than "smallest receive offset" should be discarded=
 (since the receiver should not care for it anymore -- it is expired), but =
"largest received offset" should still advance if needed (since data has be=
en received -- compliance with flow control is still required for STREAM fr=
ames).

-----Original Message-----
From: Mike Bishop [mbishop@evequefou.be]
Received: Wednesday, 30 May 2018, 6:47PM
To: Lubashev, Igor [ilubashe@akamai.com]; QUIC WG [quic@ietf.org]
Subject: RE: Partially Reliable Message Stream
I find the one octet gap a bit confusing, but as I think about it, I see wh=
y you need it.  If all the stream data arrived successfully (but hadn't bee=
n acknowledged yet due to loss of the ACK, delay, etc.) and the EXPIRED_STR=
EAM_DATA gets lost, the receiver can only retroactively realize there was a=
 jump.  Having an octet that is never transmitted ensures the receiver actu=
ally sees a gap, which means that an in-order API will not proceed until it=
 has received either the missing octet or an EXPIRED_STREAM_DATA informing =
it the octet will never arrive.

This simplification (versus -02) comes at a price:  If an API were exposing=
 stream data out-of-order, then in your example, the receiver knows that a =
message always begins on a ten-byte boundary.  A receiver can no longer fin=
d ten-byte boundaries, because the offset on the read side doesn't match th=
e offset on the send side.  I agree with you that this seems like a reasona=
ble trade-off for the simpler flow control.

One conflict I see in the doc:

*         Section 3 says:  Receipt of an EXPIRED_STREAM_DATA does not advan=
ce the largest received offset for the stream.

  *   Section 5 says:  A receiver SHOULD discard any stream data received f=
or an offset smaller than the new smallest receive offset, possibly advanci=
ng the largest received offset for the stream.

Other minor nits are better done via PR.
From: QUIC <quic-bounces@ietf.org<mailto:quic-bounces@ietf.org>> On Behalf =
Of Lubashev, Igor
Sent: Wednesday, May 30, 2018 9:45 AM
To: QUIC WG <quic@ietf.org<mailto:quic@ietf.org>>
Subject: Partially Reliable Message Stream

I've just uploaded a new draft for partially reliable QUIC streams.  Note: =
this feature is likely not in scope for V1, but it can be an extension for =
V1 and/or a part of V2.

The new version 03 (https://tools.ietf.org/html/draft-lubashev-quic-partial=
-reliability-03<https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__tool=
s.ietf.org_html_draft-2Dlubashev-2Dquic-2Dpartial-2Dreliability-2D03&d=3DDw=
MFAg&c=3D96ZbZZcaMF4w0F4jpN6LZg&r=3DDjn3bQ5uNJDPM_2skfL3rW1tzcIxyjUZdn_m55K=
Pmlo&m=3D_kwXz2JdtqD8uvvd8h8cZ-GQ3_FgDf7dRoorJ-DYVhg&s=3Dt0au9Hcc2L02NXlpLb=
99Y4e-72lBv2kC2hHZuGifUWg&e=3D>) no longer needs complex flow control chang=
es and removes the need to transmit multiple frames in the same packet.


  *   Igor

P.S.
  There is also a new version 02, which includes a more complex algorithm w=
ith more features and different trade-offs.  But I think version 03 is a be=
tter match for the needs so far.

--_000_SN1PR08MB18543DDEB2765F23109E5949DA630SN1PR08MB1854namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Consolas;
	panose-1:2 11 6 9 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0in;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:Consolas;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
p.msonormal00, li.msonormal00, div.msonormal00
	{mso-style-name:msonormal0;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.emailstyle19
	{mso-style-name:emailstyle19;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.emailstyle20
	{mso-style-name:emailstyle20;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.emailstyle21
	{mso-style-name:emailstyle21;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.htmlpreformattedchar0
	{mso-style-name:htmlpreformattedchar;
	font-family:"Courier New";}
span.EmailStyle27
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:192770497;
	mso-list-template-ids:2054436720;}
@list l0:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1
	{mso-list-id:675152681;
	mso-list-template-ids:-771454774;}
@list l1:level1
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level2
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:1.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level5
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:2.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:3.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level8
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.0in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
@list l1:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:4.5in;
	mso-level-number-position:left;
	text-indent:-.25in;
	mso-ansi-font-size:10.0pt;
	font-family:Symbol;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Ah, I see &#8211; the second is talking about action=
s taken on receipt of a STREAM frame, not an ESD frame; I missed that.<o:p>=
</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Lubashev, Igor &lt;ilubashe@akamai.com&=
gt; <br>
<b>Sent:</b> Wednesday, May 30, 2018 6:20 PM<br>
<b>To:</b> quic@ietf.org; Mike Bishop &lt;mbishop@evequefou.be&gt;<br>
<b>Subject:</b> RE: Partially Reliable Message Stream<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"color:=
black">Thanks for the review, Mike!<br>
<br>
Yes, you got the purpose of the gap exactly right.<br>
<br>
&gt; Conflict in the doc.<br>
<br>
Actually, I do not see a conflict, but it is true that the accounting is tr=
icky, and the wording could be a bit better. The receiver maintains two dis=
tinct variables:<br>
* smallest receive offset -- the smallest offset it is waiting for<br>
* largest received offset -- just what it says, probably used for nothing e=
lse by the receiver but verifying compliance with flow control (important, =
since &quot;largest received offset&quot; - &quot;smallest receive offset&q=
uot; =3D &quot;size of in-use receive buffer&quot; for the stream).<br>
<br>
The quotation from section 5 says that when a new STREAM frame is received,=
 data at offsets smaller than &quot;smallest receive offset&quot; should be=
 discarded (since the receiver should not care for it anymore -- it is expi=
red), but &quot;largest received offset&quot; should
 still advance if needed (since data has been received -- compliance with f=
low control is still required for STREAM frames).<br>
<br>
-----Original Message----- <br>
<b>From:</b> Mike Bishop [mbishop@evequefou.be]<br>
<b>Received:</b> Wednesday, 30 May 2018, 6:47PM<br>
<b>To:</b> Lubashev, Igor [ilubashe@akamai.com]; QUIC WG [quic@ietf.org]<br=
>
<b>Subject:</b> RE: Partially Reliable Message Stream</span><o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal">I find the one octet gap a bit confusing, but as I t=
hink about it, I see why you need it.&nbsp; If all the stream data arrived =
successfully (but hadn&#8217;t been acknowledged yet due to loss of the ACK=
, delay, etc.)
<i>and</i> the EXPIRED_STREAM_DATA gets lost, the receiver can only retroac=
tively realize there was a jump.&nbsp; Having an octet that is never transm=
itted ensures the receiver actually
<i>sees</i> a gap, which means that an in-order API will not proceed until =
it has received either the missing octet or an EXPIRED_STREAM_DATA informin=
g it the octet will never arrive.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">This simplification (versus -02) comes at a price:&n=
bsp; If an API were exposing stream data out-of-order, then in your example=
, the receiver knows that a message always begins on a ten-byte boundary.&n=
bsp; A receiver can no longer find ten-byte
 boundaries, because the offset on the read side doesn&#8217;t match the of=
fset on the send side.&nbsp; I agree with you that this seems like a reason=
able trade-off for the simpler flow control.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">One conflict I see in the doc:<o:p></o:p></p>
<pre style=3D"margin-left:.5in;text-indent:-.25in"><span style=3D"font-fami=
ly:Symbol">&middot;</span><span style=3D"font-size:7.0pt;font-family:&quot;=
Times New Roman&quot;,serif">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p; </span><span style=3D"font-size:11.0pt;font-family:&quot;Calibri&quot;,s=
ans-serif">Section 3 says:</span><span style=3D"font-family:&quot;Calibri&q=
uot;,sans-serif">&nbsp; </span>Receipt of an EXPIRED_STREAM_DATA <b>does no=
t advance the largest received offset for the stream</b>.<o:p></o:p></pre>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-list:l0 level1 lfo1">Section 5 says:&n=
bsp; <span style=3D"font-size:10.0pt;font-family:&quot;Courier New&quot;">
A receiver SHOULD discard any stream data received for an offset smaller th=
an the new smallest receive offset,
<b>possibly advancing the largest received offset for the stream</b>.</span=
><o:p></o:p></li></ul>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">Other minor nits are better done via PR.<o:p></o:p><=
/p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> QUIC &lt;<a href=3D"mailto:quic-bounces=
@ietf.org">quic-bounces@ietf.org</a>&gt;
<b>On Behalf Of </b>Lubashev, Igor<br>
<b>Sent:</b> Wednesday, May 30, 2018 9:45 AM<br>
<b>To:</b> QUIC WG &lt;<a href=3D"mailto:quic@ietf.org">quic@ietf.org</a>&g=
t;<br>
<b>Subject:</b> Partially Reliable Message Stream<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">I&#8217;ve just uploaded a new draft for partially r=
eliable QUIC streams.&nbsp; Note: this feature is likely not in scope for V=
1, but it can be an extension for V1 and/or a part of V2.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">The new version 03 (<a href=3D"https://urldefense.pr=
oofpoint.com/v2/url?u=3Dhttps-3A__tools.ietf.org_html_draft-2Dlubashev-2Dqu=
ic-2Dpartial-2Dreliability-2D03&amp;d=3DDwMFAg&amp;c=3D96ZbZZcaMF4w0F4jpN6L=
Zg&amp;r=3DDjn3bQ5uNJDPM_2skfL3rW1tzcIxyjUZdn_m55KPmlo&amp;m=3D_kwXz2JdtqD8=
uvvd8h8cZ-GQ3_FgDf7dRoorJ-DYVhg&amp;s=3Dt0au9Hcc2L02NXlpLb99Y4e-72lBv2kC2hH=
ZuGifUWg&amp;e=3D">https://tools.ietf.org/html/draft-lubashev-quic-partial-=
reliability-03</a>)
 no longer needs complex flow control changes and removes the need to trans=
mit multiple frames in the same packet.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"MsoNormal" style=3D"mso-list:l1 level1 lfo2">Igor<o:p></o:p></=
li></ul>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal">P.S.<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp; There is also a new version 02, which include=
s a more complex algorithm with more features and different trade-offs.&nbs=
p; But I think version 03 is a better match for the needs so far.<o:p></o:p=
></p>
</div>
</div>
</div>
</body>
</html>

--_000_SN1PR08MB18543DDEB2765F23109E5949DA630SN1PR08MB1854namp_--


From nobody Wed May 30 20:33:07 2018
Return-Path: <mbishop@evequefou.be>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6BC2A1316C8 for <quic@ietfa.amsl.com>; Wed, 30 May 2018 20:33:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.909
X-Spam-Level: 
X-Spam-Status: No, score=-1.909 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=evequefou.onmicrosoft.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 p25IZjFP4dkT for <quic@ietfa.amsl.com>; Wed, 30 May 2018 20:33:01 -0700 (PDT)
Received: from NAM01-BN3-obe.outbound.protection.outlook.com (mail-bn3nam01on0103.outbound.protection.outlook.com [104.47.33.103]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 238E51316C3 for <quic@ietf.org>; Wed, 30 May 2018 20:33:01 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector1-evequefou-be; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VV8UMlVgN7Z7SekTpNGCH2TVaB+DbNxghnXidsqIhJs=; b=RIDFVz7DhEvhmH88PyVpINiok34UaXUeY0MPlMmBJVheRMX/RqMmaOvfMC52n4GwSbkt5dsTIa1Vv6G14dUSHBKv99dKLgQk6U/SIt521n+k5FHS94BWFiEv5vCrnCl2ESBX2Ntv7HzD+ROX7TaGaA/ctYkQWFLp92rnCvKmqHA=
Received: from SN1PR08MB1854.namprd08.prod.outlook.com (10.169.39.8) by SN1PR08MB1471.namprd08.prod.outlook.com (10.162.2.139) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.20.820.11; Thu, 31 May 2018 03:32:54 +0000
Received: from SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::c1ff:4f0e:a59b:b9a9]) by SN1PR08MB1854.namprd08.prod.outlook.com ([fe80::c1ff:4f0e:a59b:b9a9%13]) with mapi id 15.20.0797.020; Thu, 31 May 2018 03:32:54 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Roberto Peon <fenix@fb.com>, Martin Thomson <martin.thomson@gmail.com>
CC: QUIC WG <quic@ietf.org>, "Lubashev, Igor" <ilubashe=40akamai.com@dmarc.ietf.org>
Subject: RE: Partially Reliable Message Stream
Thread-Topic: Partially Reliable Message Stream
Thread-Index: AdP4Mo3KTicRHsMuS7e4Jrowbk1vdQAMuR2gAAT/n4AAAG2XyQAFL0wg
Date: Thu, 31 May 2018 03:32:53 +0000
Message-ID: <SN1PR08MB1854EB788295504BEE169A25DA630@SN1PR08MB1854.namprd08.prod.outlook.com>
References: <d263c36bc5264842a65f04fc3b017538@ustx2ex-dag1mb6.msg.corp.akamai.com> <SN1PR08MB18541BF8B27EA5484FA6A437DA6C0@SN1PR08MB1854.namprd08.prod.outlook.com>, <CABkgnnWUpaFvz3d0SJJ99JkhdQfwdaxYosKwj3dK9BVZUtZ_yw@mail.gmail.com> <BYAPR15MB2312A20C0FFF67119059D2B3CD630@BYAPR15MB2312.namprd15.prod.outlook.com>
In-Reply-To: <BYAPR15MB2312A20C0FFF67119059D2B3CD630@BYAPR15MB2312.namprd15.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mbishop@evequefou.be; 
x-originating-ip: [2601:600:8080:5a28:5405:472:6b:afc4]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; SN1PR08MB1471; 7:kyXTbJ6xEpypSQA4j0VnsQ/WL/TlFxnPb3FJgSDjdh1075D4VPVxxBhq0kHjirWBNINF+Cbv+JSLdtMRPqgsAOTEEEwW7DcaE3VmiaOvVO8znzq6tQdInLM5lfZfbAgg3HKEfDmHawpgq9v34zrEbN1pAvKr9W5Jtsd0TTTCU4VVji5ZmI74dpcQEPNxs7+PpvQzG8Z4WzihPRDs8743HzXiNEn+Ou8PEKTGG11h/lwTdy2T239Q/iAXXU3K1qu/
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(7021125)(5600026)(4534165)(7022125)(4603075)(4627221)(201702281549075)(7048125)(7024125)(7027125)(7028125)(7023125)(2017052603328)(7153060)(7193020); SRVR:SN1PR08MB1471; 
x-ms-traffictypediagnostic: SN1PR08MB1471:
x-microsoft-antispam-prvs: <SN1PR08MB1471C86E6A4B839ED24A4799DA630@SN1PR08MB1471.namprd08.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(190756311086443)(10436049006162)(85827821059158)(67672495146484)(21748063052155)(265313219721884);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(8121501046)(5005006)(3231254)(944501410)(52105095)(10201501046)(93006095)(93001095)(3002001)(149027)(150027)(6041310)(20161123562045)(2016111802025)(20161123560045)(20161123558120)(20161123564045)(6072148)(6043046)(201708071742011)(7699016); SRVR:SN1PR08MB1471; BCL:0; PCL:0; RULEID:; SRVR:SN1PR08MB1471; 
x-forefront-prvs: 06891E23FB
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39830400003)(39380400002)(346002)(376002)(366004)(396003)(189003)(199004)(6246003)(93886005)(86362001)(7736002)(575784001)(6436002)(97736004)(105586002)(106356001)(186003)(68736007)(2900100001)(110136005)(54906003)(316002)(606006)(229853002)(74316002)(46003)(19609705001)(25786009)(7110500001)(486006)(5660300001)(5250100002)(8676002)(478600001)(7696005)(39060400002)(8936002)(81156014)(81166006)(76176011)(54896002)(14454004)(3660700001)(9686003)(3280700002)(6306002)(3480700004)(99286004)(2420400007)(74482002)(236005)(2906002)(15650500001)(102836004)(4326008)(6116002)(790700001)(446003)(59450400001)(45080400002)(476003)(11346002)(53936002)(55016002)(6506007)(53546011)(33656002); DIR:OUT; SFP:1102; SCL:1; SRVR:SN1PR08MB1471; H:SN1PR08MB1854.namprd08.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-microsoft-antispam-message-info: ZLjOOvaGc9QbXzBdVzS9k5Q3mAVa75iCP/C3Tvwos9rBBzpMCaCPLk38kRyg/L6fV7BO6+KBGU8i0uBf1rHXDmw9pcuZyIjU+8Ds/jaqSzVOhs+RdxBKgLEsDady+h80KhEFwHKl+xL49o8jL68tTxy5JXQKIF2KvjekdNXQJ4z346hX9g421Cg8cxY9pVOE
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_SN1PR08MB1854EB788295504BEE169A25DA630SN1PR08MB1854namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 3c738ec8-49ea-4886-165d-08d5c6a731cf
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 3c738ec8-49ea-4886-165d-08d5c6a731cf
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 May 2018 03:32:53.8724 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN1PR08MB1471
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/TsJ_vc4owoWWADWlq3FIgmNupwQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2018 03:33:06 -0000

--_000_SN1PR08MB1854EB788295504BEE169A25DA630SN1PR08MB1854namp_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Just to be clear....  You're suggesting multiple threads that would be writ=
ing to a single stream in parallel, rather than a single thread "owning" th=
e stream?

From: Roberto Peon <fenix@fb.com>
Sent: Wednesday, May 30, 2018 6:03 PM
To: Mike Bishop <mbishop@evequefou.be>; Martin Thomson <martin.thomson@gmai=
l.com>
Cc: QUIC WG <quic@ietf.org>; Lubashev, Igor <ilubashe=3D40akamai.com@dmarc.=
ietf.org>
Subject: Re: Partially Reliable Message Stream

I find it confusing as well.  I far prefer keeping the offsets monotonicall=
y increasing as it allows for real-world use of a partially reliable stream=
 (where you may not recieve that data but you can at least figure out what =
you did get and interpret it).
I dont know how one wohud resolve the race even within the sending applicat=
ion -- one thread sends, another thread sends while the first says to forge=
t about stuff. I dont know what offset stuff ends up at in such cases, and =
so I cannot frame data in a way that is non-synchronous. That defeats some =
of the main reasons to do partial reliability (i.e. to reduce jitter).
Draft 02 seemed to be going in a better direction w.r.t the usecases i can =
conceive of. I think rewinding to that and then potentially figuring out ho=
w to simplify it would be fun!
I'm excited to have this being discussed, since there is pent up demand to =
use it already.
-=3DR
Get Outlook for Android<https://aka.ms/ghei36>

________________________________
From: QUIC <quic-bounces@ietf.org<mailto:quic-bounces@ietf.org>> on behalf =
of Martin Thomson <martin.thomson@gmail.com<mailto:martin.thomson@gmail.com=
>>
Sent: Wednesday, May 30, 2018 5:50:59 PM
To: Mike Bishop
Cc: QUIC WG; Lubashev, Igor
Subject: Re: Partially Reliable Message Stream

Like Mike, I find this gap thing confusing.  And Mike's message
helped, but not a lot.

It took a while to realize that forcing a gap creates a new starting
point for the next message that forces the recipient to recognize and
deal with.  However, the logic for identifying that is just hard and
it's an unnecessary imposition in my view.

Say I send a message with a length of 10 and only two octets make it
onto the wire (as with your example), then it is immediately
abandoned.  Your solution would have the EXPIRED_STREAM_DATA force a
gap after the second octet, so that the next message could start at
offset 3 rather than offset 10.  That saves the remaining 7 octets of
flow control credit.  (Use bigger numbers and perhaps it seems more
motivating).

If the octets that cover the gap were sent, then you have a problem
because now you have sent two versions of the same octets, so you can
only do this if the octets were never sent.  It starts to get closer
and closer to the point where a new stream is just easier.

Worst, I think is that the receiver has to have complicated logic for
identifying that a gap exists and dealing with it.  It has to read up
to what it has, observe that the data has expired, then learn where
the gap ends, then resynchronize based on 1+gap_end for the next
message.

Better to eat the flow control cost in my view.  Or send RST_STREAM
and make another stream.
On Thu, May 31, 2018 at 8:48 AM Mike Bishop <mbishop@evequefou.be<mailto:mb=
ishop@evequefou.be>> wrote:
>
> I find the one octet gap a bit confusing, but as I think about it, I see =
why you need it.  If all the stream data arrived successfully (but hadn't b=
een acknowledged yet due to loss of the ACK, delay, etc.) and the EXPIRED_S=
TREAM_DATA gets lost, the receiver can only retroactively realize there was=
 a jump.  Having an octet that is never transmitted ensures the receiver ac=
tually sees a gap, which means that an in-order API will not proceed until =
it has received either the missing octet or an EXPIRED_STREAM_DATA informin=
g it the octet will never arrive.
>
>
>
> This simplification (versus -02) comes at a price:  If an API were exposi=
ng stream data out-of-order, then in your example, the receiver knows that =
a message always begins on a ten-byte boundary.  A receiver can no longer f=
ind ten-byte boundaries, because the offset on the read side doesn't match =
the offset on the send side.  I agree with you that this seems like a reaso=
nable trade-off for the simpler flow control.
>
>
>
> One conflict I see in the doc:
>
> *         Section 3 says:  Receipt of an EXPIRED_STREAM_DATA does not adv=
ance the largest received offset for the stream.
>
> Section 5 says:  A receiver SHOULD discard any stream data received for a=
n offset smaller than the new smallest receive offset, possibly advancing t=
he largest received offset for the stream.
>
>
>
> Other minor nits are better done via PR.
>
> From: QUIC <quic-bounces@ietf.org<mailto:quic-bounces@ietf.org>> On Behal=
f Of Lubashev, Igor
> Sent: Wednesday, May 30, 2018 9:45 AM
> To: QUIC WG <quic@ietf.org<mailto:quic@ietf.org>>
> Subject: Partially Reliable Message Stream
>
>
>
> I've just uploaded a new draft for partially reliable QUIC streams.  Note=
: this feature is likely not in scope for V1, but it can be an extension fo=
r V1 and/or a part of V2.
>
>
>
> The new version 03 (https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A=
__tools.ietf.org_html_draft-2Dlubashev-2Dquic-2Dpartial-2Dreliability-2D03&=
d=3DDwIFaQ&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3DC0sUo-LFNBaYfyoaCsf6TA&m=3DyyRpbe=
14kTYgY413gjVkOalWE_UC3xYerKpJqS8HiQo&s=3DXZ295xiZsN11yP8GLcdMs1jf7z0b2_Whi=
IxMLLorZXo&e=3D) no longer needs complex flow control changes and removes t=
he need to transmit multiple frames in the same packet.
>
>
>
> Igor
>
>
>
> P.S.
>
>   There is also a new version 02, which includes a more complex algorithm=
 with more features and different trade-offs.  But I think version 03 is a =
better match for the needs so far.

--_000_SN1PR08MB1854EB788295504BEE169A25DA630SN1PR08MB1854namp_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
p.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	border:none;
	padding:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Just to be clear&#8230;.&nbsp; You&#8217;re suggesti=
ng multiple threads that would be writing to a single stream in parallel, r=
ather than a single thread &#8220;owning&#8221; the stream?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Roberto Peon &lt;fenix@fb.com&gt; <br>
<b>Sent:</b> Wednesday, May 30, 2018 6:03 PM<br>
<b>To:</b> Mike Bishop &lt;mbishop@evequefou.be&gt;; Martin Thomson &lt;mar=
tin.thomson@gmail.com&gt;<br>
<b>Cc:</b> QUIC WG &lt;quic@ietf.org&gt;; Lubashev, Igor &lt;ilubashe=3D40a=
kamai.com@dmarc.ietf.org&gt;<br>
<b>Subject:</b> Re: Partially Reliable Message Stream<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Arial&quot;,sans-serif;color:black">I find it confusing as well=
.&nbsp; I far prefer keeping the offsets monotonically increasing as it all=
ows for real-world use of a partially reliable stream
 (where you may not recieve that data but you can at least figure out what =
you did get and interpret it).<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Arial&quot;,sans-serif;color:black">I dont know how one wohud r=
esolve the race even within the sending application -- one thread sends, an=
other thread sends while the first says to forget
 about stuff. I dont know what offset stuff ends up at in such cases, and s=
o I cannot frame data in a way that is non-synchronous. That defeats some o=
f the main reasons to do partial reliability (i.e. to reduce jitter).<o:p><=
/o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Arial&quot;,sans-serif;color:black">Draft 02 seemed to be going=
 in a better direction w.r.t the usecases i can conceive of. I think rewind=
ing to that and then potentially figuring out how
 to simplify it would be fun!<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:black">I'm excited to have this being discussed, since there is p=
ent up demand to use it already.<o:p></o:p></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Arial&quot;,sans-serif;color:black">-=3DR<o:p></o:p></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:black">Get
<a href=3D"https://aka.ms/ghei36">Outlook for Android</a><o:p></o:p></span>=
</p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:black"><o:p>&nbsp;</o:p></span></p>
</div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"98%" align=3D"center">
</div>
<div id=3D"x_divRplyFwdMsg">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From:</span></b><span=
 style=3D"color:black"> QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org">q=
uic-bounces@ietf.org</a>&gt; on behalf of Martin Thomson &lt;<a href=3D"mai=
lto:martin.thomson@gmail.com">martin.thomson@gmail.com</a>&gt;<br>
<b>Sent:</b> Wednesday, May 30, 2018 5:50:59 PM<br>
<b>To:</b> Mike Bishop<br>
<b>Cc:</b> QUIC WG; Lubashev, Igor<br>
<b>Subject:</b> Re: Partially Reliable Message Stream</span> <o:p></o:p></p=
>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Like Mike, I find thi=
s gap thing confusing.&nbsp; And Mike's message<br>
helped, but not a lot.<br>
<br>
It took a while to realize that forcing a gap creates a new starting<br>
point for the next message that forces the recipient to recognize and<br>
deal with.&nbsp; However, the logic for identifying that is just hard and<b=
r>
it's an unnecessary imposition in my view.<br>
<br>
Say I send a message with a length of 10 and only two octets make it<br>
onto the wire (as with your example), then it is immediately<br>
abandoned.&nbsp; Your solution would have the EXPIRED_STREAM_DATA force a<b=
r>
gap after the second octet, so that the next message could start at<br>
offset 3 rather than offset 10.&nbsp; That saves the remaining 7 octets of<=
br>
flow control credit.&nbsp; (Use bigger numbers and perhaps it seems more<br=
>
motivating).<br>
<br>
If the octets that cover the gap were sent, then you have a problem<br>
because now you have sent two versions of the same octets, so you can<br>
only do this if the octets were never sent.&nbsp; It starts to get closer<b=
r>
and closer to the point where a new stream is just easier.<br>
<br>
Worst, I think is that the receiver has to have complicated logic for<br>
identifying that a gap exists and dealing with it.&nbsp; It has to read up<=
br>
to what it has, observe that the data has expired, then learn where<br>
the gap ends, then resynchronize based on 1&#43;gap_end for the next<br>
message.<br>
<br>
Better to eat the flow control cost in my view.&nbsp; Or send RST_STREAM<br=
>
and make another stream.<br>
On Thu, May 31, 2018 at 8:48 AM Mike Bishop &lt;<a href=3D"mailto:mbishop@e=
vequefou.be">mbishop@evequefou.be</a>&gt; wrote:<br>
&gt;<br>
&gt; I find the one octet gap a bit confusing, but as I think about it, I s=
ee why you need it.&nbsp; If all the stream data arrived successfully (but =
hadn&#8217;t been acknowledged yet due to loss of the ACK, delay, etc.) and=
 the EXPIRED_STREAM_DATA gets lost, the receiver
 can only retroactively realize there was a jump.&nbsp; Having an octet tha=
t is never transmitted ensures the receiver actually sees a gap, which mean=
s that an in-order API will not proceed until it has received either the mi=
ssing octet or an EXPIRED_STREAM_DATA
 informing it the octet will never arrive.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; This simplification (versus -02) comes at a price:&nbsp; If an API wer=
e exposing stream data out-of-order, then in your example, the receiver kno=
ws that a message always begins on a ten-byte boundary.&nbsp; A receiver ca=
n no longer find ten-byte boundaries, because
 the offset on the read side doesn&#8217;t match the offset on the send sid=
e.&nbsp; I agree with you that this seems like a reasonable trade-off for t=
he simpler flow control.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; One conflict I see in the doc:<br>
&gt;<br>
&gt; &middot;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Section 3 say=
s:&nbsp; Receipt of an EXPIRED_STREAM_DATA does not advance the largest rec=
eived offset for the stream.<br>
&gt;<br>
&gt; Section 5 says:&nbsp; A receiver SHOULD discard any stream data receiv=
ed for an offset smaller than the new smallest receive offset, possibly adv=
ancing the largest received offset for the stream.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Other minor nits are better done via PR.<br>
&gt;<br>
&gt; From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org">quic-bounces@i=
etf.org</a>&gt; On Behalf Of Lubashev, Igor<br>
&gt; Sent: Wednesday, May 30, 2018 9:45 AM<br>
&gt; To: QUIC WG &lt;<a href=3D"mailto:quic@ietf.org">quic@ietf.org</a>&gt;=
<br>
&gt; Subject: Partially Reliable Message Stream<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; I&#8217;ve just uploaded a new draft for partially reliable QUIC strea=
ms.&nbsp; Note: this feature is likely not in scope for V1, but it can be a=
n extension for V1 and/or a part of V2.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The new version 03 (<a href=3D"https://urldefense.proofpoint.com/v2/ur=
l?u=3Dhttps-3A__tools.ietf.org_html_draft-2Dlubashev-2Dquic-2Dpartial-2Drel=
iability-2D03&amp;d=3DDwIFaQ&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3DC0sUo-L=
FNBaYfyoaCsf6TA&amp;m=3DyyRpbe14kTYgY413gjVkOalWE_UC3xYerKpJqS8HiQo&amp;s=
=3DXZ295xiZsN11yP8GLcdMs1jf7z0b2_WhiIxMLLorZXo&amp;e=3D">https://urldefense=
.proofpoint.com/v2/url?u=3Dhttps-3A__tools.ietf.org_html_draft-2Dlubashev-2=
Dquic-2Dpartial-2Dreliability-2D03&amp;d=3DDwIFaQ&amp;c=3D5VD0RTtNlTh3ycd41=
b3MUw&amp;r=3DC0sUo-LFNBaYfyoaCsf6TA&amp;m=3DyyRpbe14kTYgY413gjVkOalWE_UC3x=
YerKpJqS8HiQo&amp;s=3DXZ295xiZsN11yP8GLcdMs1jf7z0b2_WhiIxMLLorZXo&amp;e=3D<=
/a>)
 no longer needs complex flow control changes and removes the need to trans=
mit multiple frames in the same packet.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Igor<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; P.S.<br>
&gt;<br>
&gt;&nbsp;&nbsp; There is also a new version 02, which includes a more comp=
lex algorithm with more features and different trade-offs.&nbsp; But I thin=
k version 03 is a better match for the needs so far.<o:p></o:p></p>
</div>
</div>
</body>
</html>

--_000_SN1PR08MB1854EB788295504BEE169A25DA630SN1PR08MB1854namp_--


From nobody Wed May 30 22:36:51 2018
Return-Path: <roni.even@huawei.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id DDCFD12EC85 for <quic@ietfa.amsl.com>; Wed, 30 May 2018 22:36:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level: 
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 8ZAuJOWqo8xt for <quic@ietfa.amsl.com>; Wed, 30 May 2018 22:36:48 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 3E8B612EC28 for <quic@ietf.org>; Wed, 30 May 2018 22:36:48 -0700 (PDT)
Received: from lhreml701-cah.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 4E6882FB0DCAF for <quic@ietf.org>; Thu, 31 May 2018 06:36:41 +0100 (IST)
Received: from DGGEMM401-HUB.china.huawei.com (10.3.20.209) by lhreml701-cah.china.huawei.com (10.201.108.42) with Microsoft SMTP Server (TLS) id 14.3.382.0; Thu, 31 May 2018 06:36:42 +0100
Received: from DGGEMM506-MBS.china.huawei.com ([169.254.4.90]) by DGGEMM401-HUB.china.huawei.com ([10.3.20.209]) with mapi id 14.03.0382.000; Thu, 31 May 2018 13:36:39 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: Mark Nottingham <mnot@mnot.net>, IETF QUIC WG <quic@ietf.org>
CC: Lars Eggert <lars@eggert.org>
Subject: RE: Q3 2018 interim planning
Thread-Topic: Q3 2018 interim planning
Thread-Index: AQHT+I6BB6f69JIiQkKY2HkegPmFYaRJSVAw
Date: Thu, 31 May 2018 05:36:39 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD891A8D@DGGEMM506-MBS.china.huawei.com>
References: <F26E202D-78CA-4E24-9A6B-4D14ED951FB7@mnot.net>
In-Reply-To: <F26E202D-78CA-4E24-9A6B-4D14ED951FB7@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.203.100]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/v0Ai0yKY_1IdnDCQskFLZ5JWCQw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2018 05:36:50 -0000

Hi,
I have no major problem with having a meeting in US just some small issues:

1. The Jewish holidays are in September so I hope that the meeting will tak=
e place after September 20th
2. I may have problem if the meeting will be in a city where hotel prices a=
re expensive (e.g. New York) so expect that the city selection will also co=
nsider hotel prices.
3. I do not understand what it means "cannot get out of the US due to visa =
problem"  ; if someone does not have a legal status in the US I do not thin=
k that this should affect the meeting location.

Regards
Roni Even

-----Original Message-----
From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of Mark Nottingham
Sent: Thursday, May 31, 2018 6:21 AM
To: IETF QUIC WG
Cc: Lars Eggert
Subject: Q3 2018 interim planning

QUIC folks,

We're in the final stages of planning our next interim meeting (between the=
 Montreal and Bangkok IETF meetings).

Previously, we'd said that we'd avoid holding meetings in the US, due to so=
me uncertainty about the application of entry requirements.

It appears that that concern is no longer so great, and as far as we can te=
ll entry to the US should not pose a significant issue for our usual partic=
ipants. At the same time, we do know of at least one case where a person wo=
uld like to attend our meetings, but cannot due to visa issues getting *out=
* of the US.

As a result, we're planning on holding our Q3 meeting this year in the US. =
If you believe this means you would not be able to attend when you otherwis=
e would, please contact Lars and I as soon as possible.

Regards,

--
Mark Nottingham   https://www.mnot.net/


From nobody Wed May 30 22:55:44 2018
Return-Path: <mnot@mnot.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C12E712EAFA for <quic@ietfa.amsl.com>; Wed, 30 May 2018 22:55:43 -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, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=nblagPS9; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=dTkiBysH
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 GqCx_JDnIm0p for <quic@ietfa.amsl.com>; Wed, 30 May 2018 22:55:41 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7889612EAED for <quic@ietf.org>; Wed, 30 May 2018 22:55:41 -0700 (PDT)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id A88EB21E62; Thu, 31 May 2018 01:55:40 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 31 May 2018 01:55:40 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=cc :content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=fm2; bh=iEwrBiE44AS4Tasj6Oo2Jgj/P3TWO RMtA0CadMdrNbo=; b=nblagPS9iHa3EwUbe7FnyyiNiu51MNYJCQvNt9dUjqLJk gZUZdesTm37sxTBfklWXVuBHrNrEDpeik7v5lvo5gCOpYB0ce05KUgT9YWBysSVI K7I6BSfRerhvJPAW5xgLJbEiLOBBKtZdnoVnK+/7SGpJV81zq6h3d9MmL/YSVyY1 ZxZD1fF9xfuVcGvTSTIfZ5GLPBefWL6iQ97lxAZwZlqNdcpRtOsrFBa8l1BiTjc5 ypo8QnnEHzwye8O41cGgyAawvv8JRZf97oyvL6tcb+UkMKshvL2FI2GrBMej9XBe e0tYGtJI46E0lvaygl33wPB30S4Xjuql9uw6j3dVw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm2; bh=iEwrBi E44AS4Tasj6Oo2Jgj/P3TWORMtA0CadMdrNbo=; b=dTkiBysHxde9FApF54fQaB QaU2ZVgfzkxNUUKL6gewnkQkPwOojakJK5lEE/T/Cd6AHacs4z2fGUqBNyOJgg/U oqkGJ1U6an6GAwkP1o1OcesdpSKWX2w4tCz8l0udMAK8cJS6fcf4vYngd7TNKO1X hCwq/5bQjvXgwAaDYO4W3XCz/4meirLn895+7Co8YJ17pu+xodgFXv3Cgp57nC0a Y2FutwKH0CUereRvyMYFkDwlNZUxhminLEjmGkZFOGSIQzbhZg5XqpEsKRuhmBJK p+4yIDxMJOlLJ167LAVlwaw2e2MoMcx8zqgNMWpZa8t3qy9ti4hM4kOj8xn+yrjg ==
X-ME-Proxy: <xmx:XI4PW-9jDmD6jrC0upQzds8st2311woEIHwFMxgU2hVPQGd_hgJ-Ig>
X-ME-Proxy: <xmx:XI4PW_RsLoZT8TQlv8b44BG8gIcT95krheD19VMe957NGBrnh4EiiA>
X-ME-Proxy: <xmx:XI4PW87KOTkhyWn97Fv-cl2C5_l_DhJTdcKGYjS39x0U60WsX_0cxQ>
X-ME-Proxy: <xmx:XI4PWwq6AgwhZxbfvMyKEGuIQhT8w6R5peHJ4WHT9qQcaDM4DG9C6w>
X-ME-Proxy: <xmx:XI4PW4XN4lBi-Cui0o2BAphwtDFD9iVi0Ar2YX5vBF0j_RE1c5fLEQ>
X-ME-Proxy: <xmx:XI4PW-OocJittoHhq2-T-fOiZC7qiJZwK2dX3f_WMMOKIAz0EDRYiQ>
X-ME-Sender: <xms:XI4PW1vUf9rjRjLD23OCDEkCEr5AixpdryFjebljNzyODDBIQUog5A>
Received: from attitudadjuster.localdomain (unknown [144.136.175.28]) by mail.messagingengine.com (Postfix) with ESMTPA id 243D410255; Thu, 31 May 2018 01:55:38 -0400 (EDT)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 11.3 \(3445.6.18\))
Subject: Re: Q3 2018 interim planning
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD891A8D@DGGEMM506-MBS.china.huawei.com>
Date: Thu, 31 May 2018 15:55:36 +1000
Cc: IETF QUIC WG <quic@ietf.org>, Lars Eggert <lars@eggert.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A386C335-716D-4057-904F-889314FC2E80@mnot.net>
References: <F26E202D-78CA-4E24-9A6B-4D14ED951FB7@mnot.net> <6E58094ECC8D8344914996DAD28F1CCD891A8D@DGGEMM506-MBS.china.huawei.com>
To: "Roni Even (A)" <roni.even@huawei.com>
X-Mailer: Apple Mail (2.3445.6.18)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/R-s2bS9yg_7NdV5c8-lcMSAqbWs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2018 05:55:44 -0000

Hi Roni,

> On 31 May 2018, at 3:36 pm, Roni Even (A) <roni.even@huawei.com> =
wrote:
>=20
> Hi,
> I have no major problem with having a meeting in US just some small =
issues:
>=20
> 1. The Jewish holidays are in September so I hope that the meeting =
will take place after September 20th
> 2. I may have problem if the meeting will be in a city where hotel =
prices are expensive (e.g. New York) so expect that the city selection =
will also consider hotel prices.

We're aware of many potential conflicts and cost sensitivities, and are =
doing our best to balance them. Please note that this is NOT a request =
for people to talk about availability / preferred locations.

> 3. I do not understand what it means "cannot get out of the US due to =
visa problem"  ; if someone does not have a legal status in the US I do =
not think that this should affect the meeting location.

We can't go into details without violating people's privacy, but I =
assure you it is possible.

Thanks,


>=20
> Regards
> Roni Even
>=20
> -----Original Message-----
> From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of Mark Nottingham
> Sent: Thursday, May 31, 2018 6:21 AM
> To: IETF QUIC WG
> Cc: Lars Eggert
> Subject: Q3 2018 interim planning
>=20
> QUIC folks,
>=20
> We're in the final stages of planning our next interim meeting =
(between the Montreal and Bangkok IETF meetings).
>=20
> Previously, we'd said that we'd avoid holding meetings in the US, due =
to some uncertainty about the application of entry requirements.
>=20
> It appears that that concern is no longer so great, and as far as we =
can tell entry to the US should not pose a significant issue for our =
usual participants. At the same time, we do know of at least one case =
where a person would like to attend our meetings, but cannot due to visa =
issues getting *out* of the US.
>=20
> As a result, we're planning on holding our Q3 meeting this year in the =
US. If you believe this means you would not be able to attend when you =
otherwise would, please contact Lars and I as soon as possible.
>=20
> Regards,
>=20
> --
> Mark Nottingham   https://www.mnot.net/
>=20

--
Mark Nottingham   https://www.mnot.net/


From nobody Wed May 30 23:05:40 2018
Return-Path: <roni.even@huawei.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1500412EC54 for <quic@ietfa.amsl.com>; Wed, 30 May 2018 23:05:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.201
X-Spam-Level: 
X-Spam-Status: No, score=-4.201 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 r69JTz3vInPN for <quic@ietfa.amsl.com>; Wed, 30 May 2018 23:05:36 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [194.213.3.17]) (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 0FF7D12EBEE for <quic@ietf.org>; Wed, 30 May 2018 23:05:36 -0700 (PDT)
Received: from LHREML711-CAH.china.huawei.com (unknown [172.18.7.107]) by Forcepoint Email with ESMTP id 9A68CE51D32A9 for <quic@ietf.org>; Thu, 31 May 2018 07:05:32 +0100 (IST)
Received: from DGGEMM424-HUB.china.huawei.com (10.1.198.41) by LHREML711-CAH.china.huawei.com (10.201.108.34) with Microsoft SMTP Server (TLS) id 14.3.382.0; Thu, 31 May 2018 07:05:34 +0100
Received: from DGGEMM506-MBS.china.huawei.com ([169.254.4.90]) by dggemm424-hub.china.huawei.com ([10.1.198.41]) with mapi id 14.03.0382.000; Thu, 31 May 2018 14:05:31 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: Mark Nottingham <mnot@mnot.net>
CC: IETF QUIC WG <quic@ietf.org>, Lars Eggert <lars@eggert.org>
Subject: RE: Q3 2018 interim planning
Thread-Topic: Q3 2018 interim planning
Thread-Index: AQHT+I6BB6f69JIiQkKY2HkegPmFYaRJSVAw//+HdACAAIgjQA==
Date: Thu, 31 May 2018 06:05:31 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD891AAE@DGGEMM506-MBS.china.huawei.com>
References: <F26E202D-78CA-4E24-9A6B-4D14ED951FB7@mnot.net> <6E58094ECC8D8344914996DAD28F1CCD891A8D@DGGEMM506-MBS.china.huawei.com> <A386C335-716D-4057-904F-889314FC2E80@mnot.net>
In-Reply-To: <A386C335-716D-4057-904F-889314FC2E80@mnot.net>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.200.203.100]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/T_WH23q5kNN15tI5dBMnifRTLpg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2018 06:05:38 -0000

Hi Mark,

>=20
> 1. The Jewish holidays are in September so I hope that the meeting=20
> will take place after September 20th 2. I may have problem if the meeting=
 will be in a city where hotel prices are expensive (e.g. New York) so expe=
ct that the city selection will also consider hotel prices.

We're aware of many potential conflicts and cost sensitivities, and are doi=
ng our best to balance them. Please note that this is NOT a request for peo=
ple to talk about availability / preferred locations.

RE - if you are mentioning someone problem with travel out of the US as a r=
eason for meeting in the US,  you are talking about availability/preferred =
locations=20

> 3. I do not understand what it means "cannot get out of the US due to vis=
a problem"  ; if someone does not have a legal status in the US I do not th=
ink that this should affect the meeting location.

We can't go into details without violating people's privacy, but I assure y=
ou it is possible.

Thanks,


>=20
> Regards
> Roni Even
>=20


From nobody Thu May 31 00:38:05 2018
Return-Path: <duerst@it.aoyama.ac.jp>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8779A12DA06 for <quic@ietfa.amsl.com>; Thu, 31 May 2018 00:38:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.911
X-Spam-Level: 
X-Spam-Status: No, score=-1.911 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001, T_DKIMWL_WL_MED=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=itaoyama.onmicrosoft.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 S807S0cj0lbd for <quic@ietfa.amsl.com>; Thu, 31 May 2018 00:38:00 -0700 (PDT)
Received: from JPN01-TY1-obe.outbound.protection.outlook.com (mail-ty1jpn01on0139.outbound.protection.outlook.com [104.47.93.139]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 71D1E12D961 for <quic@ietf.org>; Thu, 31 May 2018 00:38:00 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=itaoyama.onmicrosoft.com; s=selector1-it-aoyama-ac-jp; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=UpybvWhfKSEzjUcycnzXHIlloY32dLHezbXNJvUn/jA=; b=uiMvOMsWQjrbf+vtxryXNRKYv+ggmGFiWxiA7TlpqZPEXc5BAPwnXxVEmNV15/8ZXH8LGEQ4ndonbSpWOvyIn/vMC7R94oiMjOy5DIQAyRxtARPi8aR/fxDKP4M2yTTBy9IzSUe+j+PmviuBgLLzTVnSR7sZCBWF/NYhgUdvwFg=
Authentication-Results: spf=none (sender IP is ) smtp.mailfrom=duerst@it.aoyama.ac.jp; 
Received: from [100.70.12.254] (133.2.59.31) by OSBPR01MB1541.jpnprd01.prod.outlook.com (2603:1096:603:3::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.797.11; Thu, 31 May 2018 07:37:57 +0000
Subject: Re: Q3 2018 interim planning
To: Mark Nottingham <mnot@mnot.net>, "Roni Even (A)" <roni.even@huawei.com>
Cc: Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
References: <F26E202D-78CA-4E24-9A6B-4D14ED951FB7@mnot.net> <6E58094ECC8D8344914996DAD28F1CCD891A8D@DGGEMM506-MBS.china.huawei.com> <A386C335-716D-4057-904F-889314FC2E80@mnot.net>
From: =?UTF-8?Q?Martin_J._D=c3=bcrst?= <duerst@it.aoyama.ac.jp>
Organization: Aoyama Gakuin University
Message-ID: <0c2e501e-1379-2b4f-a337-ee084c0bff22@it.aoyama.ac.jp>
Date: Thu, 31 May 2018 16:37:55 +0900
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.8.0
MIME-Version: 1.0
In-Reply-To: <A386C335-716D-4057-904F-889314FC2E80@mnot.net>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-Originating-IP: [133.2.59.31]
X-ClientProxiedBy: TY1PR01CA0205.jpnprd01.prod.outlook.com (2603:1096:403::35) To OSBPR01MB1541.jpnprd01.prod.outlook.com (2603:1096:603:3::16)
X-MS-PublicTrafficType: Email
X-Microsoft-Antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:OSBPR01MB1541; 
X-Microsoft-Exchange-Diagnostics: 1; OSBPR01MB1541; 3:lA2v/Ed3jk5CTSMU1lQsAUR+fbT/LenFyL7lFU0q3joDemG/4K/8D9d+mwqE88zikiPOkS4wMj4il0ekTs37N0N7G4FaTUJsQR2CFJK7ofyck+FW5tyOPYxJHTkRkA1gE++77d0E0CUqF2jN4h3htqV5FGxWcgmBl89nvKi0okXVxhkMrdi7XQT7dmbpO0SbblPFK3RDpz+AIESCHOZvXmI4NW0Nd+ruy+gCJg49em3JgcsHfEeo2unnWd8b8TSr; 25:smfvBwBuTeZDEZG5L6d7eqNSkSeyTW3dEN/H+dH/2ggANZyPti43kqzO07mIMhJiY/7HeGq4C2O8LqEY+PYQAev/D2Mq2xEdHa07yDqqi6HhloI1tY4iMYgCOBWy6/Sx2+XvP12vUUuBzVleKixPVJbBTadFRix1EfEys1+X00zyfEk9DH0zbqB0jhXVwuoZLK4qBAoVgmLe/liDqg8g1ckrkKXLU3JoxmU0p0ZSfzMB6b5om9kEFrGtgdnMwR3Oecgp/XuDx2gOkkitE+ymwXVEZgBw2PmB9UimhuP9F9c0Oig607WM/+twF9ZbKP7qC/rXmW88trlPfptp+KmTow==; 31:ZeexfWB9m3FLSilaSYpThORU/s77JdBWODNk0+gaz7dzIVDon0OkhHx5Lu5nPdI5Hy5Rtrp1O7hrSoy7BGkA1AhV1InQatWpCDEvZ8W/VKKKLJ7A6YCy4DdmxmGCqU60/b1QPJhRBF6JAJjMEF3DjfFaZl1qSHYKPMrTfdEAgSIzfo/9zRVYMyK1t70+YAV1vRvNwls9hK7bRZq3Vu1TFAVXt76xp+/+G1fhsJGUwEc=
X-MS-TrafficTypeDiagnostic: OSBPR01MB1541:
X-Microsoft-Antispam-PRVS: <OSBPR01MB1541AD56FF2BD24BAA2374B4CA630@OSBPR01MB1541.jpnprd01.prod.outlook.com>
X-Exchange-Antispam-Report-Test: UriScan:;
X-MS-Exchange-SenderADCheck: 1
X-Exchange-Antispam-Report-CFA-Test: BCL:0; PCL:0; RULEID:(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(3002001)(3231254)(944501410)(52105095)(10201501046)(149027)(150027)(6041310)(201703131423095)(201702281529075)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123560045)(20161123564045)(20161123562045)(20161123558120)(6072148)(201708071742011)(7699016); SRVR:OSBPR01MB1541; BCL:0; PCL:0; RULEID:; SRVR:OSBPR01MB1541; 
X-Microsoft-Exchange-Diagnostics: 1; OSBPR01MB1541; 4:Lk26z//uh4SjOa7bFG3FbEQFxvwN83ajnfzzuGUP0bXvwKgNM8K1KGLJPQ8eJWjUoNYuCurxOeWyyM2yeMhq4CwPZLaYYkMwrxycZgXAkyNjoIql3F3a69CisH9ab4ckZO+Ri26pAtR7VwukF8SOSysGSxyS+Ox09J+Qa5Y+lPp58ZHdL/VR4EraTcH0Kb3Msm6XbvjNY/ybJEFADM0eGyIpCjJe586jokcRg5Mr1z+IGI9ZBzORzkqxho1NNJnIfBupZMy0B/6rfOTyX3Lpbg==
X-Forefront-PRVS: 06891E23FB
X-Forefront-Antispam-Report: SFV:NSPM; SFS:(10019020)(6049001)(376002)(366004)(39380400002)(39840400004)(396003)(346002)(199004)(189003)(36916002)(6116002)(67846002)(16526019)(186003)(7736002)(65956001)(4326008)(305945005)(68736007)(49976009)(478600001)(59450400001)(26005)(956004)(53546011)(2616005)(386003)(3846002)(66066001)(16576012)(476003)(786003)(25786009)(106356001)(11346002)(105586002)(229853002)(65806001)(316002)(446003)(52146003)(23676004)(31686004)(47776003)(53936002)(5660300001)(86362001)(7116003)(8936002)(97736004)(110136005)(64126003)(31696002)(54906003)(58126008)(50466002)(81156014)(81166006)(8676002)(230700001)(486006)(6246003)(6486002)(76176011)(74482002)(2906002)(52116002)(2486003)(65826007)(78286006); DIR:OUT; SFP:1102; SCL:1; SRVR:OSBPR01MB1541; H:[100.70.12.254]; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:0; MX:1; 
Received-SPF: None (protection.outlook.com: it.aoyama.ac.jp does not designate permitted sender hosts)
X-Microsoft-Exchange-Diagnostics: =?utf-8?B?MTtPU0JQUjAxTUIxNTQxOzIzOjg1Uzh1VkZuemRlcm53Z2hBZU9xRXNGVGsx?= =?utf-8?B?OVRDN2RKOE5kcnVyL0luSmE4Tjc5Y1N1M3M3dGJNSnNJMVFQZTgwSmVTZUVT?= =?utf-8?B?WGNLS1g2SElUSHZ0WnJ4OEFaTlF3YkdicUVSMmE0UGdtK01qTmtFYnhDcU5M?= =?utf-8?B?QkN4eWlIUkxGMmhaeE9ZakMzbVRsaHN0MHNpUmF3YjRYekduMkNockFxeHlU?= =?utf-8?B?QklkbFRrTGF6eG1SSFBuR0pLMnZGWnd4bVZoSEtuVUgwVkMrUStRZUI1cnJI?= =?utf-8?B?QVcvb3RHYllEQU90TmU2S0RjVFpUejBvbmpFdnJkR1I5ZGY3MGF6OTNld3JZ?= =?utf-8?B?RUNvckF1bDNYUENSTEd1ZU5qU3FHaXpiUjdUbEFoTnM1ZlJFaGVQVC9ETTZV?= =?utf-8?B?amhsU1dhei9ndEJycStmTmQxRUQ1TTN0eldyeHpxdFd2bnF1NXA1L2VtNWl6?= =?utf-8?B?Ung5dWoyYzlFczgzNmVBTmR3enRNSGFwT0pqSm43aEN0ZVFWdFhTK3dqUzB6?= =?utf-8?B?Z0JjWTNrb1hVK0VyMEVQVTNYVi9vb1FYUHZGS0dqSTdROXRodzVUY0RMcTZ6?= =?utf-8?B?MmNlMUlJVXIzYnBuekVTNjdvZk5yOXhDZG5CM1pSZEVReHJBRnZ1SXZRWTRC?= =?utf-8?B?b29uMUp2OXBvMVAwUXNaQ051VWVRZjVHRm9oU3RrSWF5Uy93cnJWVFpTWWpm?= =?utf-8?B?MGJuS1FLL1RtVGdXNWtTZTlwN2VGdFJ5Yy9nRjlSUWVUME1FZW04WFppN2dI?= =?utf-8?B?YnBnZ2ZaWmYzY091NFBWTGNQYUp0eUh4bk5QTlBVenlmVW56RDlHcmZoNXU5?= =?utf-8?B?YUlBa1FnYXR3WUZIa2owOFMxdjg5Q0NvZlg3Y1RmTVNFL2cwYWpmK3hlREoy?= =?utf-8?B?WHNMWU1EM0ZSOGs3OHFRNzAwOTY0RjY2enJVWUJPU1htVzRKZlZJenI5Q1R1?= =?utf-8?B?Rkd3YkhnU2tFNXpVVGlLdmFKa3IxYVpGczlVWjZ0OEFxWVZkMmNyeVBjWVR2?= =?utf-8?B?RzIzT1YxVGlUSGpJUFRmZGluWFQ3SDRiaFlWbzYzQjNEemJsbnE0Rkt4RUR0?= =?utf-8?B?VnVta3lnTWVKMTJuTTFTSjJ1cy9zalQ3S0tiN0hkTWRrQ3N2bjFKZjduYzkr?= =?utf-8?B?RFdOYXdwUG5MbmJ5MzJGZWlHZjdFaEFQaDdkdUQyTXkzTDhZR1ZqTVVldGZV?= =?utf-8?B?bGxjVlpaUWJZTG1FLzhoNlEwTy9LN091UkdNNnVLc1ZpQWZhRzE2WlpUVE50?= =?utf-8?B?SlRtRXozaUVuQVZpcFJ4d2JNVGFkR1V6U3Q3ZG9oNjhJRFU4TzJQWmI1VWhm?= =?utf-8?B?NEY5V2VYTnNkdHg3ZTNrRjVnUlRxTTZjVEZ2anJwYWxOZDN5MWRFNWNDU3JH?= =?utf-8?B?YlpnWklFM2JaaGZ6bER6SnFlbWs3eGNib1pTNFBFWjAwMFlvTnNSV0JJMitS?= =?utf-8?B?Rjk2QWxVOFNmWHZSeFIyS0lvR0ttYTA2ZDhsSG9yb3hJZXU1SG8zSFFWZHdS?= =?utf-8?B?MjFKRmN1SWk4R1pVTUdnSkViTmMyeENSOU9wUmtyT2tHRW9lWEtQR2NhQjFU?= =?utf-8?B?WXhDMlMwckJXZ2dlZW5TbjVkaEVYYkxuVmx6UEtBYnpJWTlCckV4VHFROGcz?= =?utf-8?B?VW9CSEVVblZDNHVRZWxZN2lwc1dXTnVNMnNlVTU4dUN3aHlBcG9UTlNDNm52?= =?utf-8?B?aFd1TGs5ZkMvajJXRXg0aGtkQ3JKVlZkb29GNytjaVZQMVNkdGFjL0lGWXZm?= =?utf-8?B?WmtIS0t2UnRiNlE0NDJ2bzIyUDhoalZ3WUMvYzJQZ092Q2RWYTB1YTZsdmg1?= =?utf-8?B?TVZBbXBMV0VNdWZWMUY2Y28wVlRxdHRQS0d3Yi9sY01QclRQZUpZbTNscGZw?= =?utf-8?B?RnFuNlQ3NnRMcDU1T1MvTGZRLzBqRkxrUFRDN0JlZHhtSzlUSS9ic3VVVTdH?= =?utf-8?B?ay8wTmJmMGVraWV3UUFhaHEwallYTStiTEx5QVNMeS9lUTB2LzcvZXZZem5N?= =?utf-8?B?TVduMzZ0bnZKZ002SVlQUnE0ZTV4M2ZiMGZYR3dWQTFtYzMxTUZUa2owbHNJ?= =?utf-8?B?Z2VwcExkYTBaRVp4VUxjZC8xeFk4VkdPSDlLTUYxWml5MjdCTm1DY3Q2NHNt?= =?utf-8?B?TUE9PQ==?=
X-Microsoft-Antispam-Message-Info: fpiq0nw8amp7ODelB1twGCsrcPwvpaAW1WGKkFhQJodYaOeR5eWkvxW4dPXJLmPlAsE5N6oCr1K3wn3UMV7WUZnfWgLH8naSus16io9/XCjHyDhaJS97XY8bffZ6/s1OqTjAkoJ1QkBgBl624PETCzOVIX+T34Gc5o+FRTSkK1iqSKD13w8wdL14vqGstu8C
X-Microsoft-Exchange-Diagnostics: 1; OSBPR01MB1541; 6:qAC/gPZ8zMgWqbCgIeuOoDk1qoYhNHKW72PS9zsngqCe/l4I201tGOIZLOxOW9nAiGXdy++rUvangXcdsQvg+sjVbYfaO2LldnpOBirDaXdH3xEf5O9muizhZxC7twA9FprGf8eDLvMVgput+l37ViVLZEgwdnOITB1To3kAaN4FascQeqH/DqL6/+s03FSYLj8ecsWxXihtdSPfbwTvojQPjl5MOdODotDDAQLcPJPZTjNRWg0CuH7FxA5Dkzs12/6BaUM49BroIf79BLd7IFhBQ0m6X2P1+Vf0j1ExIuYFbKGAror+hWCK/5AocuBCYJXvHMldQ9foDlfLi5KMSeh990mH5342u7hMgYCWjjlPZMXtqyKY3Wvu4/t+8Gj+q9nT2OVGC4WlnmjvCf7TjMtOf+aV5dEVAvON1qeRisFmOE/dJ5BvKu+VDaWCMdHCixD1AQJ4e154lm/JnpAYxw==; 5:XXeondIgKxyvvG0AM1SvjTWe/K8zFeeH1z02EC9poFKJLs6t3T411Wx9KDggMZTxcvigDZiHMzHcuju51T916Whau8FViuvajaQy2VLeBnztJk+k5gw9+2qmWbpjTAEd3LadhjEUaDVbcekU1x639BjiKgYUMlUaHM5bM9O6aWQ=; 24:M+StwiS+5o6jW/CjKgXKGJxHMuQeZjHNB5H4q354XowOPdVSfPxyw6OC02HrlhzrT2IkI3LoZewPxALuNkMlzNxEsKMfxJSOiyJtb33RfBM=
SpamDiagnosticOutput: 1:99
SpamDiagnosticMetadata: NSPM
X-Microsoft-Exchange-Diagnostics: 1; OSBPR01MB1541; 7:7O0ITzZiivnb/7frwdeWS8xHiJBtTn3Ag96jx6gUY7W37UpLkn+LIOG3NGfT8skGEv1ZrqpcpHUjnYE4NIuMlJ9OjUcRYVCPj8Fp0SK6rIzyJE2SFyvW28WRzGdA3P0XRZCKlbPCABgPCsHJKXwyiQldV0rDaCfy1kfI/pulYPbLVjoBmuFtNr3i7N3ryDLEfSEfSHlwny2O19PoQgEboRx4OozJaqpoIMF2CjkhdPUuNwNP2a9/Tx63NXvlYBso
X-MS-Office365-Filtering-Correlation-Id: 85da0672-4ff4-468f-d4dc-08d5c6c96e4f
X-OriginatorOrg: it.aoyama.ac.jp
X-MS-Exchange-CrossTenant-OriginalArrivalTime: 31 May 2018 07:37:57.8776 (UTC)
X-MS-Exchange-CrossTenant-Network-Message-Id: 85da0672-4ff4-468f-d4dc-08d5c6c96e4f
X-MS-Exchange-CrossTenant-FromEntityHeader: Hosted
X-MS-Exchange-CrossTenant-Id: e02030e7-4d45-463e-a968-0290e738c18e
X-MS-Exchange-Transport-CrossTenantHeadersStamped: OSBPR01MB1541
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/qrrZaZwB8qCuDJNg3NYl5u_GBt8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2018 07:38:04 -0000

On 2018/05/31 14:55, Mark Nottingham wrote:

>> 3. I do not understand what it means "cannot get out of the US due to visa problem"  ; if someone does not have a legal status in the US I do not think that this should affect the meeting location.
> 
> We can't go into details without violating people's privacy, but I assure you it is possible.

Because I don't know the details, I can talk about some general cases of 
how that can happen, based on my own experience and what I have heard 
from (unrelated) others.

There are at least two cases:

1) (personal experience) I entered the US with a 1-year visa. When the 
year came to an end, I was able to extend my permit to stay for another 
year. This allowed me to stay in the US for that other year. But to 
enter the US again after leaving for a meeting abroad, I had to get a 
new visa stamp, which involved a meeting at an US embassy abroad, with 
about three weeks lead time to get an appointment, which was only 
possible using an automatic phone system that was restricted to calls 
from within the country of the embassy.

2) (third-party story) When applying for a change of status (e.g. from a 
temporary to a permanent ("green card") permit, people are not allowed 
to leave the country.

There may be other cases, or something I got wrong, or things may have 
changed, but I hope the above helps to get an idea of how it can happen.

Regards,   Martin.


From nobody Thu May 31 08:21:29 2018
Return-Path: <prvs=968909f698=fenix@fb.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9A29612ECC2 for <quic@ietfa.amsl.com>; Thu, 31 May 2018 08:21:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=igYW8FCu; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=RdqYTzIo
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 hvgUpWopWUmX for <quic@ietfa.amsl.com>; Thu, 31 May 2018 08:21:17 -0700 (PDT)
Received: from mx0b-00082601.pphosted.com (mx0b-00082601.pphosted.com [67.231.153.30]) (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 82A2312F28A for <quic@ietf.org>; Thu, 31 May 2018 08:21:16 -0700 (PDT)
Received: from pps.filterd (m0148460.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w4VFIt9P028540; Thu, 31 May 2018 08:21:10 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=facebook; bh=mFY0raw9vlbNdTdkfVTtPNeEUg5Wg3cKLSTIQEeIaNw=; b=igYW8FCuBk7d/GWZOXtcZ2ZFayucI3bIhlSnEsCMJedIgDuFmVkny1WcvBXizCB4TYeb CwFbkSw0/aZoxrg6Xy2BY3jD3VqYpYWGYEqrGyBEPYAioje/tlDhBR4EPtp0lPIWIcK+ dos3T7hkYuzJQXg57/1Fln2edretuAm14OY= 
Received: from mail.thefacebook.com ([199.201.64.23]) by mx0a-00082601.pphosted.com with ESMTP id 2jag3rgmcb-3 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 31 May 2018 08:21:10 -0700
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (192.168.54.28) by o365-in.thefacebook.com (192.168.16.23) with Microsoft SMTP Server (TLS) id 14.3.361.1; Thu, 31 May 2018 08:21:06 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=mFY0raw9vlbNdTdkfVTtPNeEUg5Wg3cKLSTIQEeIaNw=; b=RdqYTzIoDXlCh7OVgkr4AJ5N70M65adM1tuYDIlway9qp7ZY9FnIWLRBoUnGvNwD0ypudxp6DIIqoUcJh1uhXTfPky3evROqkXfhr1rhv4zJ12rbdkrqpv1j96syqHFqdyQ36enrxaWo89/bLlXFxMcEFM5mcH1UytsrO8kqoQ4=
Received: from BYAPR15MB2312.namprd15.prod.outlook.com (52.135.197.146) by BYAPR15MB2325.namprd15.prod.outlook.com (52.135.197.149) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.820.11; Thu, 31 May 2018 15:21:04 +0000
Received: from BYAPR15MB2312.namprd15.prod.outlook.com ([fe80::949a:9cbd:277c:96e0]) by BYAPR15MB2312.namprd15.prod.outlook.com ([fe80::949a:9cbd:277c:96e0%4]) with mapi id 15.20.0797.020; Thu, 31 May 2018 15:21:04 +0000
From: Roberto Peon <fenix@fb.com>
To: Mike Bishop <mbishop@evequefou.be>, Martin Thomson <martin.thomson@gmail.com>
CC: QUIC WG <quic@ietf.org>, "Lubashev, Igor" <ilubashe=40akamai.com@dmarc.ietf.org>
Subject: Re: Partially Reliable Message Stream
Thread-Topic: Partially Reliable Message Stream
Thread-Index: AdP4Mo3KTicRHsMuS7e4Jrowbk1vdQAMuR2gAAT/n4AAAG2XyQAFL0wgABjGQgc=
Date: Thu, 31 May 2018 15:21:04 +0000
Message-ID: <BYAPR15MB2312B11929B6DEC29AC67CA3CD630@BYAPR15MB2312.namprd15.prod.outlook.com>
References: <d263c36bc5264842a65f04fc3b017538@ustx2ex-dag1mb6.msg.corp.akamai.com> <SN1PR08MB18541BF8B27EA5484FA6A437DA6C0@SN1PR08MB1854.namprd08.prod.outlook.com>, <CABkgnnWUpaFvz3d0SJJ99JkhdQfwdaxYosKwj3dK9BVZUtZ_yw@mail.gmail.com> <BYAPR15MB2312A20C0FFF67119059D2B3CD630@BYAPR15MB2312.namprd15.prod.outlook.com>, <SN1PR08MB1854EB788295504BEE169A25DA630@SN1PR08MB1854.namprd08.prod.outlook.com>
In-Reply-To: <SN1PR08MB1854EB788295504BEE169A25DA630@SN1PR08MB1854.namprd08.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [98.234.190.115]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR15MB2325; 7:a/z6FCqNdSK2QesznYF5Z422UJ9bH7Kb6DDjAE5cCC2YbUMbtq6f68gqyB8gwtUMUEyr3/tRGz+Qj7XPsmBZkIVOuqINBVAKsUjxXMSMlJrTzWbj8CuRXwS7C/H/NnpCO+uUkWUypPA8aBr3KI5J5cjLZCrPohY12rnxLpnzSpEaDz8JBQQLwQuex+WzeqA7eFoWFlXcaLfUBFLRNPTZEuoEYNdrmnxJpxMMGy9GxTIffToCVdnSYlyrxhWadT59; 20:WCK8fojcYa8pFI67SA/cGl7UaU0OBrHJhpcC/E5EvNuvrLEMpruU/sgMHK1SNnm0HkF+636EQ4/Qwg+c2U8TcLBeskNr48mEldCyPLnsY26Ca0vcXyxcai6ogh8k6fd3ATeVgNtLnhNfmPbHTJPOAL0FiCPLXW36m9Oz8QPcyKA=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BYAPR15MB2325; 
x-ms-traffictypediagnostic: BYAPR15MB2325:
x-microsoft-antispam-prvs: <BYAPR15MB2325B528C2418C52088BDF16CD630@BYAPR15MB2325.namprd15.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(190756311086443)(10436049006162)(85827821059158)(67672495146484); 
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(5005006)(8121501046)(93006095)(93001095)(3231254)(11241501184)(944501410)(52105095)(10201501046)(3002001)(149027)(150027)(6041310)(20161123558120)(20161123560045)(20161123562045)(20161123564045)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(6072148)(201708071742011)(7699016); SRVR:BYAPR15MB2325; BCL:0; PCL:0; RULEID:; SRVR:BYAPR15MB2325; 
x-forefront-prvs: 06891E23FB
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(39860400002)(366004)(39380400002)(346002)(376002)(396003)(199004)(189003)(606006)(446003)(14454004)(6246003)(236005)(54896002)(6306002)(478600001)(53936002)(9686003)(97736004)(11346002)(476003)(93886005)(59450400001)(6506007)(110136005)(3280700002)(15650500001)(7696005)(26005)(33656002)(186003)(3660700001)(76176011)(53546011)(316002)(68736007)(86362001)(102836004)(5250100002)(575784001)(66066001)(486006)(99286004)(54906003)(8936002)(3846002)(5660300001)(81156014)(81166006)(55016002)(2906002)(7736002)(3480700004)(8676002)(106356001)(45080400002)(105586002)(4326008)(39060400002)(25786009)(2900100001)(229853002)(6116002)(74316002)(6436002)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR15MB2325; H:BYAPR15MB2312.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: fb.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: 4Aw0WQ/mJxt2FZLJ1zi27/LDXbs0WfR345GMr5yEyzWlW9JdzN454QIT7U7bwQO45qZdy04sfJ2hJz0TNJsp9a6YKy8138EotoYlpslLxNHLuIASWxnMlVWoqj2dMnPtNZE62GJPJJBgovMTIGk3XnWKoRfBPTOwLozj8zBb57MO/1jYLhz0paA0yMKPKV8C
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_BYAPR15MB2312B11929B6DEC29AC67CA3CD630BYAPR15MB2312namp_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: a51c6f1f-558b-4a33-afd2-08d5c70a200d
X-MS-Exchange-CrossTenant-Network-Message-Id: a51c6f1f-558b-4a33-afd2-08d5c70a200d
X-MS-Exchange-CrossTenant-originalarrivaltime: 31 May 2018 15:21:04.2130 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR15MB2325
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-31_08:, , signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/6OwxYV5Al_d2-wK-O4arasqnkuw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2018 15:21:27 -0000

--_000_BYAPR15MB2312B11929B6DEC29AC67CA3CD630BYAPR15MB2312namp_
Content-Type: text/plain; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

Yes. You may want a single resource for an output which you may be generati=
ng in parallel. Even if a single thread 'owns' the stream, you've lost the =
ability to coordinate the data it recieves by monotonically increasing offs=
et.

Renumbering the offsets breaks the file-like abstraction we've effectively =
used for http.


-=3DR



Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone


-------- Original message --------
From: Mike Bishop <mbishop@evequefou.be>
Date: 5/30/18 8:33 PM (GMT-08:00)
To: Roberto Peon <fenix@fb.com>, Martin Thomson <martin.thomson@gmail.com>
Cc: QUIC WG <quic@ietf.org>, "Lubashev, Igor" <ilubashe=3D40akamai.com@dmar=
c.ietf.org>
Subject: RE: Partially Reliable Message Stream

Just to be clear=85.  You=92re suggesting multiple threads that would be wr=
iting to a single stream in parallel, rather than a single thread =93owning=
=94 the stream?

From: Roberto Peon <fenix@fb.com>
Sent: Wednesday, May 30, 2018 6:03 PM
To: Mike Bishop <mbishop@evequefou.be>; Martin Thomson <martin.thomson@gmai=
l.com>
Cc: QUIC WG <quic@ietf.org>; Lubashev, Igor <ilubashe=3D40akamai.com@dmarc.=
ietf.org>
Subject: Re: Partially Reliable Message Stream

I find it confusing as well.  I far prefer keeping the offsets monotonicall=
y increasing as it allows for real-world use of a partially reliable stream=
 (where you may not recieve that data but you can at least figure out what =
you did get and interpret it).
I dont know how one wohud resolve the race even within the sending applicat=
ion -- one thread sends, another thread sends while the first says to forge=
t about stuff. I dont know what offset stuff ends up at in such cases, and =
so I cannot frame data in a way that is non-synchronous. That defeats some =
of the main reasons to do partial reliability (i.e. to reduce jitter).
Draft 02 seemed to be going in a better direction w.r.t the usecases i can =
conceive of. I think rewinding to that and then potentially figuring out ho=
w to simplify it would be fun!
I'm excited to have this being discussed, since there is pent up demand to =
use it already.
-=3DR
Get Outlook for Android<https://urldefense.proofpoint.com/v2/url?u=3Dhttps-=
3A__aka.ms_ghei36&d=3DDwMFAg&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3DC0sUo-LFNBaYfyo=
aCsf6TA&m=3DVOUj_MnwWf_PgdHvcGV1Se1o3k5jC8m8noKDixq8HqA&s=3D-xJb_JWOdL_DpDM=
43E06S54LPE-xkpYkSen4El-wkS4&e=3D>

________________________________
From: QUIC <quic-bounces@ietf.org<mailto:quic-bounces@ietf.org>> on behalf =
of Martin Thomson <martin.thomson@gmail.com<mailto:martin.thomson@gmail.com=
>>
Sent: Wednesday, May 30, 2018 5:50:59 PM
To: Mike Bishop
Cc: QUIC WG; Lubashev, Igor
Subject: Re: Partially Reliable Message Stream

Like Mike, I find this gap thing confusing.  And Mike's message
helped, but not a lot.

It took a while to realize that forcing a gap creates a new starting
point for the next message that forces the recipient to recognize and
deal with.  However, the logic for identifying that is just hard and
it's an unnecessary imposition in my view.

Say I send a message with a length of 10 and only two octets make it
onto the wire (as with your example), then it is immediately
abandoned.  Your solution would have the EXPIRED_STREAM_DATA force a
gap after the second octet, so that the next message could start at
offset 3 rather than offset 10.  That saves the remaining 7 octets of
flow control credit.  (Use bigger numbers and perhaps it seems more
motivating).

If the octets that cover the gap were sent, then you have a problem
because now you have sent two versions of the same octets, so you can
only do this if the octets were never sent.  It starts to get closer
and closer to the point where a new stream is just easier.

Worst, I think is that the receiver has to have complicated logic for
identifying that a gap exists and dealing with it.  It has to read up
to what it has, observe that the data has expired, then learn where
the gap ends, then resynchronize based on 1+gap_end for the next
message.

Better to eat the flow control cost in my view.  Or send RST_STREAM
and make another stream.
On Thu, May 31, 2018 at 8:48 AM Mike Bishop <mbishop@evequefou.be<mailto:mb=
ishop@evequefou.be>> wrote:
>
> I find the one octet gap a bit confusing, but as I think about it, I see =
why you need it.  If all the stream data arrived successfully (but hadn=92t=
 been acknowledged yet due to loss of the ACK, delay, etc.) and the EXPIRED=
_STREAM_DATA gets lost, the receiver can only retroactively realize there w=
as a jump.  Having an octet that is never transmitted ensures the receiver =
actually sees a gap, which means that an in-order API will not proceed unti=
l it has received either the missing octet or an EXPIRED_STREAM_DATA inform=
ing it the octet will never arrive.
>
>
>
> This simplification (versus -02) comes at a price:  If an API were exposi=
ng stream data out-of-order, then in your example, the receiver knows that =
a message always begins on a ten-byte boundary.  A receiver can no longer f=
ind ten-byte boundaries, because the offset on the read side doesn=92t matc=
h the offset on the send side.  I agree with you that this seems like a rea=
sonable trade-off for the simpler flow control.
>
>
>
> One conflict I see in the doc:
>
> =B7         Section 3 says:  Receipt of an EXPIRED_STREAM_DATA does not a=
dvance the largest received offset for the stream.
>
> Section 5 says:  A receiver SHOULD discard any stream data received for a=
n offset smaller than the new smallest receive offset, possibly advancing t=
he largest received offset for the stream.
>
>
>
> Other minor nits are better done via PR.
>
> From: QUIC <quic-bounces@ietf.org<mailto:quic-bounces@ietf.org>> On Behal=
f Of Lubashev, Igor
> Sent: Wednesday, May 30, 2018 9:45 AM
> To: QUIC WG <quic@ietf.org<mailto:quic@ietf.org>>
> Subject: Partially Reliable Message Stream
>
>
>
> I=92ve just uploaded a new draft for partially reliable QUIC streams.  No=
te: this feature is likely not in scope for V1, but it can be an extension =
for V1 and/or a part of V2.
>
>
>
> The new version 03 (https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A=
__tools.ietf.org_html_draft-2Dlubashev-2Dquic-2Dpartial-2Dreliability-2D03&=
d=3DDwIFaQ&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3DC0sUo-LFNBaYfyoaCsf6TA&m=3DyyRpbe=
14kTYgY413gjVkOalWE_UC3xYerKpJqS8HiQo&s=3DXZ295xiZsN11yP8GLcdMs1jf7z0b2_Whi=
IxMLLorZXo&e=3D) no longer needs complex flow control changes and removes t=
he need to transmit multiple frames in the same packet.
>
>
>
> Igor
>
>
>
> P.S.
>
>   There is also a new version 02, which includes a more complex algorithm=
 with more features and different trade-offs.  But I think version 03 is a =
better match for the needs so far.

--_000_BYAPR15MB2312B11929B6DEC29AC67CA3CD630BYAPR15MB2312namp_
Content-Type: text/html; charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable

<html>
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3DWindows-1=
252">
<meta content=3D"text/html; charset=3DWindows-1252">
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style>
<!--
@font-face
	{font-family:"Cambria Math"}
@font-face
	{font-family:Calibri}
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif}
a:link, span.MsoHyperlink
	{color:blue;
	text-decoration:underline}
a:visited, span.MsoHyperlinkFollowed
	{color:purple;
	text-decoration:underline}
p.msonormal0, li.msonormal0, div.msonormal0
	{margin-right:0in;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif}
p.emailquote, li.emailquote, div.emailquote
	{margin-right:0in;
	margin-left:1.0pt;
	border:none;
	padding:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif}
span.EmailStyle20
	{font-family:"Calibri",sans-serif;
	color:windowtext}
.MsoChpDefault
	{font-size:10.0pt}
@page WordSection1
	{margin:1.0in 1.0in 1.0in 1.0in}
div.WordSection1
	{}
-->
</style>
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>Yes. You may want a single resource for an output which you may be gen=
erating in parallel. Even if a single thread 'owns' the stream, you've lost=
 the ability to coordinate the data it recieves by monotonically increasing=
 offset.</div>
<div><br>
</div>
<div>Renumbering the offsets breaks the file-like abstraction we've effecti=
vely used for http.</div>
<div><br>
</div>
<div><br>
</div>
<div>-=3DR</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div id=3D"composer_signature">
<div dir=3D"auto" style=3D"font-size:85%; color:#575757">Sent via the Samsu=
ng Galaxy S7, an AT&amp;T 4G LTE smartphone</div>
</div>
<div><br>
</div>
<div><br>
</div>
<div>-------- Original message --------</div>
<div>From: Mike Bishop &lt;mbishop@evequefou.be&gt; </div>
<div>Date: 5/30/18 8:33 PM (GMT-08:00) </div>
<div>To: Roberto Peon &lt;fenix@fb.com&gt;, Martin Thomson &lt;martin.thoms=
on@gmail.com&gt; </div>
<div>Cc: QUIC WG &lt;quic@ietf.org&gt;, &quot;Lubashev, Igor&quot; &lt;ilub=
ashe=3D40akamai.com@dmarc.ietf.org&gt;
</div>
<div>Subject: RE: Partially Reliable Message Stream </div>
<div><br>
</div>
<div>
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Just to be clear=85.&nbsp; You=92re suggesting multi=
ple threads that would be writing to a single stream in parallel, rather th=
an a single thread =93owning=94 the stream?</p>
<p class=3D"MsoNormal">&nbsp;</p>
<div>
<div style=3D"border:none; border-top:solid #E1E1E1 1.0pt; padding:3.0pt 0i=
n 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Roberto Peon &lt;fenix@fb.com&gt; <br>
<b>Sent:</b> Wednesday, May 30, 2018 6:03 PM<br>
<b>To:</b> Mike Bishop &lt;mbishop@evequefou.be&gt;; Martin Thomson &lt;mar=
tin.thomson@gmail.com&gt;<br>
<b>Cc:</b> QUIC WG &lt;quic@ietf.org&gt;; Lubashev, Igor &lt;ilubashe=3D40a=
kamai.com@dmarc.ietf.org&gt;<br>
<b>Subject:</b> Re: Partially Reliable Message Stream</p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;</p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Arial&quot;,sans-serif; color:black">I find it confusing as wel=
l.&nbsp; I far prefer keeping the offsets monotonically increasing as it al=
lows for real-world use of a partially reliable stream
 (where you may not recieve that data but you can at least figure out what =
you did get and interpret it).</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Arial&quot;,sans-serif; color:black">I dont know how one wohud =
resolve the race even within the sending application -- one thread sends, a=
nother thread sends while the first says to forget
 about stuff. I dont know what offset stuff ends up at in such cases, and s=
o I cannot frame data in a way that is non-synchronous. That defeats some o=
f the main reasons to do partial reliability (i.e. to reduce jitter).</span=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Arial&quot;,sans-serif; color:black">Draft 02 seemed to be goin=
g in a better direction w.r.t the usecases i can conceive of. I think rewin=
ding to that and then potentially figuring out how
 to simplify it would be fun!</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif; color:black">I'm excited to have this being discussed, since there is =
pent up demand to use it already.</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Arial&quot;,sans-serif; color:black">-=3DR</span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif; color:black">Get
<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__aka.ms_gh=
ei36&amp;d=3DDwMFAg&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3DC0sUo-LFNBaYfyoa=
Csf6TA&amp;m=3DVOUj_MnwWf_PgdHvcGV1Se1o3k5jC8m8noKDixq8HqA&amp;s=3D-xJb_JWO=
dL_DpDM43E06S54LPE-xkpYkSen4El-wkS4&amp;e=3D">
Outlook for Android</a></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif; color:black">&nbsp;</span></p>
</div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"98%" align=3D"center">
</div>
<div id=3D"x_divRplyFwdMsg">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From:</span></b><span=
 style=3D"color:black"> QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org">q=
uic-bounces@ietf.org</a>&gt; on behalf of Martin Thomson &lt;<a href=3D"mai=
lto:martin.thomson@gmail.com">martin.thomson@gmail.com</a>&gt;<br>
<b>Sent:</b> Wednesday, May 30, 2018 5:50:59 PM<br>
<b>To:</b> Mike Bishop<br>
<b>Cc:</b> QUIC WG; Lubashev, Igor<br>
<b>Subject:</b> Re: Partially Reliable Message Stream</span> </p>
<div>
<p class=3D"MsoNormal">&nbsp;</p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Like Mike, I find thi=
s gap thing confusing.&nbsp; And Mike's message<br>
helped, but not a lot.<br>
<br>
It took a while to realize that forcing a gap creates a new starting<br>
point for the next message that forces the recipient to recognize and<br>
deal with.&nbsp; However, the logic for identifying that is just hard and<b=
r>
it's an unnecessary imposition in my view.<br>
<br>
Say I send a message with a length of 10 and only two octets make it<br>
onto the wire (as with your example), then it is immediately<br>
abandoned.&nbsp; Your solution would have the EXPIRED_STREAM_DATA force a<b=
r>
gap after the second octet, so that the next message could start at<br>
offset 3 rather than offset 10.&nbsp; That saves the remaining 7 octets of<=
br>
flow control credit.&nbsp; (Use bigger numbers and perhaps it seems more<br=
>
motivating).<br>
<br>
If the octets that cover the gap were sent, then you have a problem<br>
because now you have sent two versions of the same octets, so you can<br>
only do this if the octets were never sent.&nbsp; It starts to get closer<b=
r>
and closer to the point where a new stream is just easier.<br>
<br>
Worst, I think is that the receiver has to have complicated logic for<br>
identifying that a gap exists and dealing with it.&nbsp; It has to read up<=
br>
to what it has, observe that the data has expired, then learn where<br>
the gap ends, then resynchronize based on 1&#43;gap_end for the next<br>
message.<br>
<br>
Better to eat the flow control cost in my view.&nbsp; Or send RST_STREAM<br=
>
and make another stream.<br>
On Thu, May 31, 2018 at 8:48 AM Mike Bishop &lt;<a href=3D"mailto:mbishop@e=
vequefou.be">mbishop@evequefou.be</a>&gt; wrote:<br>
&gt;<br>
&gt; I find the one octet gap a bit confusing, but as I think about it, I s=
ee why you need it.&nbsp; If all the stream data arrived successfully (but =
hadn=92t been acknowledged yet due to loss of the ACK, delay, etc.) and the=
 EXPIRED_STREAM_DATA gets lost, the receiver
 can only retroactively realize there was a jump.&nbsp; Having an octet tha=
t is never transmitted ensures the receiver actually sees a gap, which mean=
s that an in-order API will not proceed until it has received either the mi=
ssing octet or an EXPIRED_STREAM_DATA
 informing it the octet will never arrive.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; This simplification (versus -02) comes at a price:&nbsp; If an API wer=
e exposing stream data out-of-order, then in your example, the receiver kno=
ws that a message always begins on a ten-byte boundary.&nbsp; A receiver ca=
n no longer find ten-byte boundaries, because
 the offset on the read side doesn=92t match the offset on the send side.&n=
bsp; I agree with you that this seems like a reasonable trade-off for the s=
impler flow control.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; One conflict I see in the doc:<br>
&gt;<br>
&gt; =B7&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Section 3 says:&nb=
sp; Receipt of an EXPIRED_STREAM_DATA does not advance the largest received=
 offset for the stream.<br>
&gt;<br>
&gt; Section 5 says:&nbsp; A receiver SHOULD discard any stream data receiv=
ed for an offset smaller than the new smallest receive offset, possibly adv=
ancing the largest received offset for the stream.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Other minor nits are better done via PR.<br>
&gt;<br>
&gt; From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org">quic-bounces@i=
etf.org</a>&gt; On Behalf Of Lubashev, Igor<br>
&gt; Sent: Wednesday, May 30, 2018 9:45 AM<br>
&gt; To: QUIC WG &lt;<a href=3D"mailto:quic@ietf.org">quic@ietf.org</a>&gt;=
<br>
&gt; Subject: Partially Reliable Message Stream<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; I=92ve just uploaded a new draft for partially reliable QUIC streams.&=
nbsp; Note: this feature is likely not in scope for V1, but it can be an ex=
tension for V1 and/or a part of V2.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The new version 03 (<a href=3D"https://urldefense.proofpoint.com/v2/ur=
l?u=3Dhttps-3A__tools.ietf.org_html_draft-2Dlubashev-2Dquic-2Dpartial-2Drel=
iability-2D03&amp;d=3DDwIFaQ&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3DC0sUo-L=
FNBaYfyoaCsf6TA&amp;m=3DyyRpbe14kTYgY413gjVkOalWE_UC3xYerKpJqS8HiQo&amp;s=
=3DXZ295xiZsN11yP8GLcdMs1jf7z0b2_WhiIxMLLorZXo&amp;e=3D">https://urldefense=
.proofpoint.com/v2/url?u=3Dhttps-3A__tools.ietf.org_html_draft-2Dlubashev-2=
Dquic-2Dpartial-2Dreliability-2D03&amp;d=3DDwIFaQ&amp;c=3D5VD0RTtNlTh3ycd41=
b3MUw&amp;r=3DC0sUo-LFNBaYfyoaCsf6TA&amp;m=3DyyRpbe14kTYgY413gjVkOalWE_UC3x=
YerKpJqS8HiQo&amp;s=3DXZ295xiZsN11yP8GLcdMs1jf7z0b2_WhiIxMLLorZXo&amp;e=3D<=
/a>)
 no longer needs complex flow control changes and removes the need to trans=
mit multiple frames in the same packet.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Igor<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; P.S.<br>
&gt;<br>
&gt;&nbsp;&nbsp; There is also a new version 02, which includes a more comp=
lex algorithm with more features and different trade-offs.&nbsp; But I thin=
k version 03 is a better match for the needs so far.</p>
</div>
</div>
</div>
</body>
</html>

--_000_BYAPR15MB2312B11929B6DEC29AC67CA3CD630BYAPR15MB2312namp_--


From nobody Thu May 31 13:37:39 2018
Return-Path: <jri.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8CEEF131795 for <quic@ietfa.amsl.com>; Thu, 31 May 2018 13:37:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.698
X-Spam-Level: 
X-Spam-Status: No, score=-2.698 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 vHYzrW_aRrU9 for <quic@ietfa.amsl.com>; Thu, 31 May 2018 13:37:28 -0700 (PDT)
Received: from mail-it0-x230.google.com (mail-it0-x230.google.com [IPv6:2607:f8b0:4001:c0b::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 1F7C91320DD for <quic@ietf.org>; Thu, 31 May 2018 13:37:28 -0700 (PDT)
Received: by mail-it0-x230.google.com with SMTP id c3-v6so29701371itj.4 for <quic@ietf.org>; Thu, 31 May 2018 13:37:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=TtrcnQ6clRfd6Ws7fFc55SUWNKwc0obTiiEHnjxNf5U=; b=DG25G9Xj1Ck8P45jsoZHjzy0cdAsu5AEQ48w0l5HDIgk60JPQrywURRjgbXFQXy+LS p5ddgVRr4J8aJGiXugtX5aSqXegcXjKYO90yXEahFnz5qaNyCPQWjCeVBqbS65vtfdXP Eobr6j0eXpZLj44GN+AqN/I1lyfzqRuVn+6ob2avccKB1vhKa/OGbl+UsAiFSiLW1v0T IvDdIHT7j26YVqeHi+txe/zyIhiP633pd+/vm2MargaPTq/UT83dwoDeLLtq8zpqJtUe eV+2sCecInEV+XF38ER81gFBDXuVzeumAod6nc3Chtz1atHgSoB3IZmtbSN3jWn8LtTg DvFA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=TtrcnQ6clRfd6Ws7fFc55SUWNKwc0obTiiEHnjxNf5U=; b=N1ELxqZeHHQ737jALMChSQMM7OS/9HRQr3pVgNj700oU6emU47vCh1+JqNZaXwLGgU EQ3lFUV6McBNIrVafftkHuo9CLiBtpW4FB+xKtKKUIkR5dcvUwR/3VL0xPNVt8BlT1r0 4sLFnsIP04Xk/O3K6ty3ZYB0jh6l/3Nion2lU46SKM3XZoxhznEoJsCt7VZr5Kd4r935 bgfBaLSydfJngp2OVL4/MoEz6du3EcXhB7v5odA5hBZTKLj6+bFoJjB8/ETR1OblXkUA W+lHauO1ihtsDUdoD4+hPYkMdBTUMB0bq32eam2nMFCbvbTJHObJ0RR2EtiAcIb6d6TB Tbfg==
X-Gm-Message-State: ALKqPwezgndlQYQHpEKAJo7DU0I7XxHBkdsaUD1wb4plXhF3D0dvLxy5 UaDhVERG745QoGSAqN9pVn7CXeR9ZdgIFI2PkBA=
X-Google-Smtp-Source: ADUXVKJuaB5qCHLPilzoffaBl0wAibkD7QCwySZ5ujTy+uJ79b4Gy4GiGF4k+uRTMmU6zfloHYK4QMCVJpPhB7HHdDc=
X-Received: by 2002:a24:e306:: with SMTP id d6-v6mr1498985ith.103.1527799047142;  Thu, 31 May 2018 13:37:27 -0700 (PDT)
MIME-Version: 1.0
Received: by 2002:a4f:2a46:0:0:0:0:0 with HTTP; Thu, 31 May 2018 13:37:26 -0700 (PDT)
In-Reply-To: <BYAPR15MB2312B11929B6DEC29AC67CA3CD630@BYAPR15MB2312.namprd15.prod.outlook.com>
References: <d263c36bc5264842a65f04fc3b017538@ustx2ex-dag1mb6.msg.corp.akamai.com> <SN1PR08MB18541BF8B27EA5484FA6A437DA6C0@SN1PR08MB1854.namprd08.prod.outlook.com> <CABkgnnWUpaFvz3d0SJJ99JkhdQfwdaxYosKwj3dK9BVZUtZ_yw@mail.gmail.com> <BYAPR15MB2312A20C0FFF67119059D2B3CD630@BYAPR15MB2312.namprd15.prod.outlook.com> <SN1PR08MB1854EB788295504BEE169A25DA630@SN1PR08MB1854.namprd08.prod.outlook.com> <BYAPR15MB2312B11929B6DEC29AC67CA3CD630@BYAPR15MB2312.namprd15.prod.outlook.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Thu, 31 May 2018 13:37:26 -0700
Message-ID: <CACpbDcdoc9T-4hSEEko+j5ihRaMQW8VR+pgdof7k-5E7stSk8Q@mail.gmail.com>
Subject: Re: Partially Reliable Message Stream
To: Roberto Peon <fenix@fb.com>
Cc: Mike Bishop <mbishop@evequefou.be>, Martin Thomson <martin.thomson@gmail.com>,  QUIC WG <quic@ietf.org>, "Lubashev, Igor" <ilubashe=40akamai.com@dmarc.ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007e41a7056d866f2b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/y72pYiMy3ssikJ2EztgVfkJ9zpA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2018 20:37:32 -0000

--0000000000007e41a7056d866f2b
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

I'm not keen to get into the weeds of this discussion at this time (as you
say, it's for v2), but I understand the overall design. A few higher-order
points with this design direction:

1. There's clear demarcation of app messages, but they aren't really made
first class citizens. If you did that, I imagine that you might have a
simpler design. For instance, define a MSG_STREAM frame, which supports
message streams (instead of the current byte streams), and then you can
cancel messages easily without having to do stream offset shenanigans.

2. Your design has exactly one ordering capability, which is limiting.
Generally, apps that can drop messages and read subsequent ones are also
capable of handling messages out of sequence. You'll want to support
partial ordering as well and not constrain messages to be only delivered in
strictly linear order.

3. I'm keen to see what we can do with using streams as messages. We don't
need to punt everything to the app (as your text suggests), but we can
start with a grouping of streams (or messages) and building flow control
mechanisms for these groups. I suspect this might be cleaner, and it gives
you flexibility to consider various orderings of messages. When we're
closer to v2, I'm happy to spin up a draft exploring this direction.

On Thu, May 31, 2018 at 8:21 AM, Roberto Peon <fenix@fb.com> wrote:

> Yes. You may want a single resource for an output which you may be
> generating in parallel. Even if a single thread 'owns' the stream, you've
> lost the ability to coordinate the data it recieves by monotonically
> increasing offset.
>
> Renumbering the offsets breaks the file-like abstraction we've effectivel=
y
> used for http.
>
>
> -=3DR
>
>
>
> Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone
>
>
> -------- Original message --------
> From: Mike Bishop <mbishop@evequefou.be>
> Date: 5/30/18 8:33 PM (GMT-08:00)
> To: Roberto Peon <fenix@fb.com>, Martin Thomson <martin.thomson@gmail.com=
>
>
> Cc: QUIC WG <quic@ietf.org>, "Lubashev, Igor" <ilubashe=3D
> 40akamai.com@dmarc.ietf.org>
> Subject: RE: Partially Reliable Message Stream
>
> Just to be clear=E2=80=A6.  You=E2=80=99re suggesting multiple threads th=
at would be
> writing to a single stream in parallel, rather than a single thread
> =E2=80=9Cowning=E2=80=9D the stream?
>
>
>
> *From:* Roberto Peon <fenix@fb.com>
> *Sent:* Wednesday, May 30, 2018 6:03 PM
> *To:* Mike Bishop <mbishop@evequefou.be>; Martin Thomson <
> martin.thomson@gmail.com>
> *Cc:* QUIC WG <quic@ietf.org>; Lubashev, Igor <ilubashe=3D
> 40akamai.com@dmarc.ietf.org>
> *Subject:* Re: Partially Reliable Message Stream
>
>
>
> I find it confusing as well.  I far prefer keeping the offsets
> monotonically increasing as it allows for real-world use of a partially
> reliable stream (where you may not recieve that data but you can at least
> figure out what you did get and interpret it).
>
> I dont know how one wohud resolve the race even within the sending
> application -- one thread sends, another thread sends while the first say=
s
> to forget about stuff. I dont know what offset stuff ends up at in such
> cases, and so I cannot frame data in a way that is non-synchronous. That
> defeats some of the main reasons to do partial reliability (i.e. to reduc=
e
> jitter).
>
> Draft 02 seemed to be going in a better direction w.r.t the usecases i ca=
n
> conceive of. I think rewinding to that and then potentially figuring out
> how to simplify it would be fun!
>
> I'm excited to have this being discussed, since there is pent up demand t=
o
> use it already.
>
> -=3DR
>
> Get Outlook for Android
> <https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__aka.ms_ghei36&d=
=3DDwMFAg&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3DC0sUo-LFNBaYfyoaCsf6TA&m=3DVOUj_Mn=
wWf_PgdHvcGV1Se1o3k5jC8m8noKDixq8HqA&s=3D-xJb_JWOdL_DpDM43E06S54LPE-xkpYkSe=
n4El-wkS4&e=3D>
>
>
> ------------------------------
>
> *From:* QUIC <quic-bounces@ietf.org> on behalf of Martin Thomson <
> martin.thomson@gmail.com>
> *Sent:* Wednesday, May 30, 2018 5:50:59 PM
> *To:* Mike Bishop
> *Cc:* QUIC WG; Lubashev, Igor
> *Subject:* Re: Partially Reliable Message Stream
>
>
>
> Like Mike, I find this gap thing confusing.  And Mike's message
> helped, but not a lot.
>
> It took a while to realize that forcing a gap creates a new starting
> point for the next message that forces the recipient to recognize and
> deal with.  However, the logic for identifying that is just hard and
> it's an unnecessary imposition in my view.
>
> Say I send a message with a length of 10 and only two octets make it
> onto the wire (as with your example), then it is immediately
> abandoned.  Your solution would have the EXPIRED_STREAM_DATA force a
> gap after the second octet, so that the next message could start at
> offset 3 rather than offset 10.  That saves the remaining 7 octets of
> flow control credit.  (Use bigger numbers and perhaps it seems more
> motivating).
>
> If the octets that cover the gap were sent, then you have a problem
> because now you have sent two versions of the same octets, so you can
> only do this if the octets were never sent.  It starts to get closer
> and closer to the point where a new stream is just easier.
>
> Worst, I think is that the receiver has to have complicated logic for
> identifying that a gap exists and dealing with it.  It has to read up
> to what it has, observe that the data has expired, then learn where
> the gap ends, then resynchronize based on 1+gap_end for the next
> message.
>
> Better to eat the flow control cost in my view.  Or send RST_STREAM
> and make another stream.
> On Thu, May 31, 2018 at 8:48 AM Mike Bishop <mbishop@evequefou.be> wrote:
> >
> > I find the one octet gap a bit confusing, but as I think about it, I se=
e
> why you need it.  If all the stream data arrived successfully (but hadn=
=E2=80=99t
> been acknowledged yet due to loss of the ACK, delay, etc.) and the
> EXPIRED_STREAM_DATA gets lost, the receiver can only retroactively realiz=
e
> there was a jump.  Having an octet that is never transmitted ensures the
> receiver actually sees a gap, which means that an in-order API will not
> proceed until it has received either the missing octet or an
> EXPIRED_STREAM_DATA informing it the octet will never arrive.
> >
> >
> >
> > This simplification (versus -02) comes at a price:  If an API were
> exposing stream data out-of-order, then in your example, the receiver kno=
ws
> that a message always begins on a ten-byte boundary.  A receiver can no
> longer find ten-byte boundaries, because the offset on the read side
> doesn=E2=80=99t match the offset on the send side.  I agree with you that=
 this
> seems like a reasonable trade-off for the simpler flow control.
> >
> >
> >
> > One conflict I see in the doc:
> >
> > =C2=B7         Section 3 says:  Receipt of an EXPIRED_STREAM_DATA does =
not
> advance the largest received offset for the stream.
> >
> > Section 5 says:  A receiver SHOULD discard any stream data received for
> an offset smaller than the new smallest receive offset, possibly advancin=
g
> the largest received offset for the stream.
> >
> >
> >
> > Other minor nits are better done via PR.
> >
> > From: QUIC <quic-bounces@ietf.org> On Behalf Of Lubashev, Igor
> > Sent: Wednesday, May 30, 2018 9:45 AM
> > To: QUIC WG <quic@ietf.org>
> > Subject: Partially Reliable Message Stream
> >
> >
> >
> > I=E2=80=99ve just uploaded a new draft for partially reliable QUIC stre=
ams.
> Note: this feature is likely not in scope for V1, but it can be an
> extension for V1 and/or a part of V2.
> >
> >
> >
> > The new version 03 (https://urldefense..proofpoint.com/v2/url?u=3Dhttps=
-
> 3A__tools.ietf.org_html_draft-2Dlubashev-2Dquic-2Dpartial-
> 2Dreliability-2D03&d=3DDwIFaQ&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3D
> C0sUo-LFNBaYfyoaCsf6TA&m=3DyyRpbe14kTYgY413gjVkOalWE_UC3xYerKpJqS8HiQo&s=
=3D
> XZ295xiZsN11yP8GLcdMs1jf7z0b2_WhiIxMLLorZXo&e=3D
> <https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__tools.ietf.org_ht=
ml_draft-2Dlubashev-2Dquic-2Dpartial-2Dreliability-2D03&d=3DDwIFaQ&c=3D5VD0=
RTtNlTh3ycd41b3MUw&r=3DC0sUo-LFNBaYfyoaCsf6TA&m=3DyyRpbe14kTYgY413gjVkOalWE=
_UC3xYerKpJqS8HiQo&s=3DXZ295xiZsN11yP8GLcdMs1jf7z0b2_WhiIxMLLorZXo&e=3D>)
> no longer needs complex flow control changes and removes the need to
> transmit multiple frames in the same packet.
> >
> >
> >
> > Igor
> >
> >
> >
> > P.S.
> >
> >   There is also a new version 02, which includes a more complex
> algorithm with more features and different trade-offs.  But I think versi=
on
> 03 is a better match for the needs so far.
>

--0000000000007e41a7056d866f2b
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr">I&#39;m not keen to get into the weeds of this discussion =
at this time (as you say, it&#39;s for v2), but I understand the overall de=
sign. A few higher-order points with this design direction:<div><br></div><=
div>1. There&#39;s clear demarcation of app messages, but they aren&#39;t r=
eally made first class citizens. If you did that, I imagine that you might =
have a simpler design. For instance, define a MSG_STREAM frame, which suppo=
rts message streams (instead of the current byte streams), and then you can=
 cancel messages easily without having to do stream offset shenanigans.</di=
v><div><br></div><div>2. Your design has exactly one ordering capability, w=
hich is limiting. Generally, apps that can drop messages and read subsequen=
t ones are also capable of handling messages out of sequence. You&#39;ll wa=
nt to support partial ordering as well and not constrain messages to be onl=
y delivered in strictly linear order.=C2=A0</div><div><br></div><div>3. I&#=
39;m keen to see what we can do with using streams as messages. We don&#39;=
t need to punt everything to the app (as your text suggests), but we can st=
art with a grouping of streams (or messages) and building flow control mech=
anisms for these groups. I suspect this might be cleaner, and it gives you =
flexibility to consider various orderings of messages. When we&#39;re close=
r to v2, I&#39;m happy to spin up a draft exploring this direction.</div></=
div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On Thu, May 3=
1, 2018 at 8:21 AM, Roberto Peon <span dir=3D"ltr">&lt;<a href=3D"mailto:fe=
nix@fb.com" target=3D"_blank">fenix@fb.com</a>&gt;</span> wrote:<br><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">






<div lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div>Yes. You may want a single resource for an output which you may be gen=
erating in parallel. Even if a single thread &#39;owns&#39; the stream, you=
&#39;ve lost the ability to coordinate the data it recieves by monotonicall=
y increasing offset.</div>
<div><br>
</div>
<div>Renumbering the offsets breaks the file-like abstraction we&#39;ve eff=
ectively used for http.</div>
<div><br>
</div>
<div><br>
</div>
<div>-=3DR</div>
<div><br>
</div>
<div><br>
</div>
<div><br>
</div>
<div id=3D"m_-68153589551068015composer_signature">
<div dir=3D"auto" style=3D"font-size:85%;color:#575757">Sent via the Samsun=
g Galaxy S7, an AT&amp;T 4G LTE smartphone</div>
</div><span class=3D"">
<div><br>
</div>
<div><br>
</div>
<div>-------- Original message --------</div>
<div>From: Mike Bishop &lt;<a href=3D"mailto:mbishop@evequefou.be" target=
=3D"_blank">mbishop@evequefou.be</a>&gt; </div>
<div>Date: 5/30/18 8:33 PM (GMT-08:00) </div>
<div>To: Roberto Peon &lt;<a href=3D"mailto:fenix@fb.com" target=3D"_blank"=
>fenix@fb.com</a>&gt;, Martin Thomson &lt;<a href=3D"mailto:martin.thomson@=
gmail.com" target=3D"_blank">martin.thomson@gmail.com</a>&gt; </div>
<div>Cc: QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">qui=
c@ietf.org</a>&gt;, &quot;Lubashev, Igor&quot; &lt;ilubashe=3D<a href=3D"ma=
ilto:40akamai.com@dmarc.ietf.org" target=3D"_blank">40akamai.com@dmarc.<wbr=
>ietf.org</a>&gt;
</div>
<div>Subject: RE: Partially Reliable Message Stream </div>
<div><br>
</div>
</span><div>
<div class=3D"m_-68153589551068015WordSection1"><span class=3D"">
<p class=3D"MsoNormal">Just to be clear=E2=80=A6.=C2=A0 You=E2=80=99re sugg=
esting multiple threads that would be writing to a single stream in paralle=
l, rather than a single thread =E2=80=9Cowning=E2=80=9D the stream?</p>
<p class=3D"MsoNormal">=C2=A0</p>
<div>
<div style=3D"border:none;border-top:solid #e1e1e1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Roberto Peon &lt;<a href=3D"mailto:feni=
x@fb.com" target=3D"_blank">fenix@fb.com</a>&gt; <br>
<b>Sent:</b> Wednesday, May 30, 2018 6:03 PM<br>
<b>To:</b> Mike Bishop &lt;<a href=3D"mailto:mbishop@evequefou.be" target=
=3D"_blank">mbishop@evequefou.be</a>&gt;; Martin Thomson &lt;<a href=3D"mai=
lto:martin.thomson@gmail.com" target=3D"_blank">martin.thomson@gmail.com</a=
>&gt;<br>
<b>Cc:</b> QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">q=
uic@ietf.org</a>&gt;; Lubashev, Igor &lt;ilubashe=3D<a href=3D"mailto:40aka=
mai.com@dmarc.ietf.org" target=3D"_blank">40akamai.com@dmarc.<wbr>ietf.org<=
/a>&gt;<br>
<b>Subject:</b> Re: Partially Reliable Message Stream</p>
</div>
</div>
<p class=3D"MsoNormal">=C2=A0</p>
</span><div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Arial&quot;,sans-serif;color:black">I find it confusing as well=
.=C2=A0 I far prefer keeping the offsets monotonically increasing as it all=
ows for real-world use of a partially reliable stream
 (where you may not recieve that data but you can at least figure out what =
you did get and interpret it).</span></p>
</div><div><div class=3D"h5">
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Arial&quot;,sans-serif;color:black">I dont know how one wohud r=
esolve the race even within the sending application -- one thread sends, an=
other thread sends while the first says to forget
 about stuff. I dont know what offset stuff ends up at in such cases, and s=
o I cannot frame data in a way that is non-synchronous. That defeats some o=
f the main reasons to do partial reliability (i.e. to reduce jitter).</span=
></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Arial&quot;,sans-serif;color:black">Draft 02 seemed to be going=
 in a better direction w.r.t the usecases i can conceive of. I think rewind=
ing to that and then potentially figuring out how
 to simplify it would be fun!</span></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:black">I&#39;m excited to have this being discussed, since there =
is pent up demand to use it already.</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Arial&quot;,sans-serif;color:black">-=3DR</span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:black">Get
<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__aka.ms_gh=
ei36&amp;d=3DDwMFAg&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3DC0sUo-LFNBaYfyoa=
Csf6TA&amp;m=3DVOUj_MnwWf_PgdHvcGV1Se1o3k5jC8m8noKDixq8HqA&amp;s=3D-xJb_JWO=
dL_DpDM43E06S54LPE-xkpYkSen4El-wkS4&amp;e=3D" target=3D"_blank">
Outlook for Android</a></span></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:black">=C2=A0</span></p>
</div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"98%" align=3D"center">
</div>
<div id=3D"m_-68153589551068015x_divRplyFwdMsg">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From:</span></b><span=
 style=3D"color:black"> QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" t=
arget=3D"_blank">quic-bounces@ietf.org</a>&gt; on behalf of Martin Thomson =
&lt;<a href=3D"mailto:martin.thomson@gmail.com" target=3D"_blank">martin.th=
omson@gmail.com</a>&gt;<br>
<b>Sent:</b> Wednesday, May 30, 2018 5:50:59 PM<br>
<b>To:</b> Mike Bishop<br>
<b>Cc:</b> QUIC WG; Lubashev, Igor<br>
<b>Subject:</b> Re: Partially Reliable Message Stream</span> </p>
<div>
<p class=3D"MsoNormal">=C2=A0</p>
</div>
</div>
</div></div></div><div><div class=3D"h5">
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Like Mike, I find thi=
s gap thing confusing.=C2=A0 And Mike&#39;s message<br>
helped, but not a lot.<br>
<br>
It took a while to realize that forcing a gap creates a new starting<br>
point for the next message that forces the recipient to recognize and<br>
deal with.=C2=A0 However, the logic for identifying that is just hard and<b=
r>
it&#39;s an unnecessary imposition in my view.<br>
<br>
Say I send a message with a length of 10 and only two octets make it<br>
onto the wire (as with your example), then it is immediately<br>
abandoned.=C2=A0 Your solution would have the EXPIRED_STREAM_DATA force a<b=
r>
gap after the second octet, so that the next message could start at<br>
offset 3 rather than offset 10.=C2=A0 That saves the remaining 7 octets of<=
br>
flow control credit.=C2=A0 (Use bigger numbers and perhaps it seems more<br=
>
motivating).<br>
<br>
If the octets that cover the gap were sent, then you have a problem<br>
because now you have sent two versions of the same octets, so you can<br>
only do this if the octets were never sent.=C2=A0 It starts to get closer<b=
r>
and closer to the point where a new stream is just easier.<br>
<br>
Worst, I think is that the receiver has to have complicated logic for<br>
identifying that a gap exists and dealing with it.=C2=A0 It has to read up<=
br>
to what it has, observe that the data has expired, then learn where<br>
the gap ends, then resynchronize based on 1+gap_end for the next<br>
message.<br>
<br>
Better to eat the flow control cost in my view.=C2=A0 Or send RST_STREAM<br=
>
and make another stream.<br>
On Thu, May 31, 2018 at 8:48 AM Mike Bishop &lt;<a href=3D"mailto:mbishop@e=
vequefou.be" target=3D"_blank">mbishop@evequefou.be</a>&gt; wrote:<br>
&gt;<br>
&gt; I find the one octet gap a bit confusing, but as I think about it, I s=
ee why you need it.=C2=A0 If all the stream data arrived successfully (but =
hadn=E2=80=99t been acknowledged yet due to loss of the ACK, delay, etc.) a=
nd the EXPIRED_STREAM_DATA gets lost, the receiver
 can only retroactively realize there was a jump.=C2=A0 Having an octet tha=
t is never transmitted ensures the receiver actually sees a gap, which mean=
s that an in-order API will not proceed until it has received either the mi=
ssing octet or an EXPIRED_STREAM_DATA
 informing it the octet will never arrive.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; This simplification (versus -02) comes at a price:=C2=A0 If an API wer=
e exposing stream data out-of-order, then in your example, the receiver kno=
ws that a message always begins on a ten-byte boundary.=C2=A0 A receiver ca=
n no longer find ten-byte boundaries, because
 the offset on the read side doesn=E2=80=99t match the offset on the send s=
ide.=C2=A0 I agree with you that this seems like a reasonable trade-off for=
 the simpler flow control.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; One conflict I see in the doc:<br>
&gt;<br>
&gt; =C2=B7=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Section 3 says:=
=C2=A0 Receipt of an EXPIRED_STREAM_DATA does not advance the largest recei=
ved offset for the stream.<br>
&gt;<br>
&gt; Section 5 says:=C2=A0 A receiver SHOULD discard any stream data receiv=
ed for an offset smaller than the new smallest receive offset, possibly adv=
ancing the largest received offset for the stream.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Other minor nits are better done via PR.<br>
&gt;<br>
&gt; From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_bla=
nk">quic-bounces@ietf.org</a>&gt; On Behalf Of Lubashev, Igor<br>
&gt; Sent: Wednesday, May 30, 2018 9:45 AM<br>
&gt; To: QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">qui=
c@ietf.org</a>&gt;<br>
&gt; Subject: Partially Reliable Message Stream<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; I=E2=80=99ve just uploaded a new draft for partially reliable QUIC str=
eams.=C2=A0 Note: this feature is likely not in scope for V1, but it can be=
 an extension for V1 and/or a part of V2.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The new version 03 (<a href=3D"https://urldefense.proofpoint.com/v2/ur=
l?u=3Dhttps-3A__tools.ietf.org_html_draft-2Dlubashev-2Dquic-2Dpartial-2Drel=
iability-2D03&amp;d=3DDwIFaQ&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3DC0sUo-L=
FNBaYfyoaCsf6TA&amp;m=3DyyRpbe14kTYgY413gjVkOalWE_UC3xYerKpJqS8HiQo&amp;s=
=3DXZ295xiZsN11yP8GLcdMs1jf7z0b2_WhiIxMLLorZXo&amp;e=3D" target=3D"_blank">=
https://urldefense..<wbr>proofpoint.com/v2/url?u=3Dhttps-<wbr>3A__tools.iet=
f.org_html_draft-<wbr>2Dlubashev-2Dquic-2Dpartial-<wbr>2Dreliability-2D03&a=
mp;d=3DDwIFaQ&amp;c=3D<wbr>5VD0RTtNlTh3ycd41b3MUw&amp;r=3D<wbr>C0sUo-LFNBaY=
fyoaCsf6TA&amp;m=3D<wbr>yyRpbe14kTYgY413gjVkOalWE_<wbr>UC3xYerKpJqS8HiQo&am=
p;s=3D<wbr>XZ295xiZsN11yP8GLcdMs1jf7z0b2_<wbr>WhiIxMLLorZXo&amp;e=3D</a>)
 no longer needs complex flow control changes and removes the need to trans=
mit multiple frames in the same packet.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Igor<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; P.S.<br>
&gt;<br>
&gt;=C2=A0=C2=A0 There is also a new version 02, which includes a more comp=
lex algorithm with more features and different trade-offs.=C2=A0 But I thin=
k version 03 is a better match for the needs so far.</p>
</div>
</div></div></div>
</div>
</div>

</blockquote></div><br></div>

--0000000000007e41a7056d866f2b--


From nobody Thu May 31 16:26:24 2018
Return-Path: <ilubashe@akamai.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 3516A126BF3 for <quic@ietfa.amsl.com>; Thu, 31 May 2018 16:26:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.71
X-Spam-Level: 
X-Spam-Status: No, score=-2.71 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 kcYhKuOBO-4E for <quic@ietfa.amsl.com>; Thu, 31 May 2018 16:26:21 -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 392F2124D37 for <quic@ietf.org>; Thu, 31 May 2018 16:26:21 -0700 (PDT)
Received: from pps.filterd (m0122332.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w4VNMDfa021872; Fri, 1 Jun 2018 00:26:16 +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 : content-transfer-encoding : mime-version; s=jan2016.eng; bh=IZLv24rb4bOWuG93n2pMq0KcdKT84CbzOwYoxqvsp4U=; b=LyC0ZX6Nv7Iec9cNZSu8kNndeLpVxzGH8H9MgEsnmruOfwfoqxKVkLmWuX2UD8zsF6bh J1K6tyP9fIP7bXxqDp4jsPvuU3KZTH6Y/20TK1TY5DiCye5cHdafJqBlPqtYqvboARBh 2iaT7JYOzLgDSztYtypqA376SPVl0R5dV2DTX+GYSHR8hb3pSiTF6EtFRKLJXctT9FAG Pq6lUaGIpaQm63XVG1CoirteK4d12LFHuMtQJU8+8ViTWZ0qp4JiK+nUXcMSqR4MkymN kjp5/SbTRR+EN4624YPvv6cgtO7WlezCCX/spAMfqQ3NUH04fWczdfEF7lc2zGldYDCC hg== 
Received: from prod-mail-ppoint4 (a96-6-114-87.deploy.static.akamaitechnologies.com [96.6.114.87] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 2ja5h1vnee-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 01 Jun 2018 00:26:16 +0100
Received: from pps.filterd (prod-mail-ppoint4.akamai.com [127.0.0.1]) by prod-mail-ppoint4.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w4VNQ7RL001861; Thu, 31 May 2018 19:26:15 -0400
Received: from email.msg.corp.akamai.com ([172.27.27.21]) by prod-mail-ppoint4.akamai.com with ESMTP id 2j9cvvc3a1-9 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 31 May 2018 19:26:15 -0400
Received: from ustx2ex-dag1mb6.msg.corp.akamai.com (172.27.27.107) by ustx2ex-dag1mb3.msg.corp.akamai.com (172.27.27.103) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Thu, 31 May 2018 18:22:33 -0500
Received: from ustx2ex-dag1mb6.msg.corp.akamai.com ([172.27.27.107]) by ustx2ex-dag1mb6.msg.corp.akamai.com ([172.27.27.107]) with mapi id 15.00.1365.000; Thu, 31 May 2018 16:22:33 -0700
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: Martin Thomson <martin.thomson@gmail.com>, Mike Bishop <mbishop@evequefou.be>
CC: QUIC WG <quic@ietf.org>
Subject: RE: Partially Reliable Message Stream
Thread-Topic: Partially Reliable Message Stream
Thread-Index: AdP4Mo3KTicRHsMuS7e4Jrowbk1vdQAMuR2gABOqt4AAIBzWMA==
Date: Thu, 31 May 2018 23:22:32 +0000
Message-ID: <0c68d4cc013743d789b4fff092a7b68a@ustx2ex-dag1mb6.msg.corp.akamai.com>
References: <d263c36bc5264842a65f04fc3b017538@ustx2ex-dag1mb6.msg.corp.akamai.com> <SN1PR08MB18541BF8B27EA5484FA6A437DA6C0@SN1PR08MB1854.namprd08.prod.outlook.com> <CABkgnnWUpaFvz3d0SJJ99JkhdQfwdaxYosKwj3dK9BVZUtZ_yw@mail.gmail.com>
In-Reply-To: <CABkgnnWUpaFvz3d0SJJ99JkhdQfwdaxYosKwj3dK9BVZUtZ_yw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.32.104]
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-31_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=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1805220000 definitions=main-1805310259
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-31_13:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1805220000 definitions=main-1805310258
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/o0DmPiWH8VWKSxe43cT4byAaT5Q>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2018 23:26:23 -0000

VGhhbmtzIGZvciB0aGUgcmV2aWV3LCBNYXJ0aW4hDQoNClllcywgYWxsIHRoZSBzaGVuYW5pZ2Fu
cyBhcmUgdG8gbGltaXQgdGhlIF9jb25uZWN0aW9uXyBmbG93IGNvbnRyb2wgd2FzdGFnZSB0byBh
IHNpbmdsZSBvY3RldCBwZXIgc3RyZWFtIFsqXS4gIElmIHlvdSBhbGxvdyBmb3IgdW5ib3VuZGVk
IHdhc3RhZ2UsIHlvdSBoYXZlIHRvIGFjdGl2ZWx5IGRlYWwgd2l0aCB0aGlzICh0aGF0J3Mgd2hh
dCB2ZXJzaW9uIDAyIG9mIHRoZSBkcmFmdCBkb2VzLCBidXQgaXQgaXMgbmVjZXNzYXJpbHkgbW9y
ZSBjb21wbGV4IGZvciBpdCkuDQoNCj4gSWYgdGhlIG9jdGV0cyB0aGF0IGNvdmVyIHRoZSBnYXAg
d2VyZSBzZW50LCB0aGVuIHlvdSBoYXZlIGEgcHJvYmxlbSBiZWNhdXNlIG5vdyB5b3UgaGF2ZSBz
ZW50IHR3byB2ZXJzaW9ucyBvZiB0aGUgc2FtZSBvY3RldHMNCg0KWW91IHdvdWxkIG5vdCBjcmVh
dGUgYSBnYXAsIGlmIG9jdGV0cyByaWdodCBiZWZvcmUgdGhlICJleHBpcmF0aW9uIHBvaW50IiB3
ZXJlIHNlbnQuICBCZWNhdXNlIHRoZSBhcHBsaWNhdGlvbiBvbmx5IGV4cGlyZXMgb24gbWVzc2Fn
ZSBib3VuZGFyaWVzLCB0aGVyZSBpcyBubyBwcm9ibGVtIGlmIGFsbCBvY3RldHMgYmVmb3JlIHRo
ZSAiZXhwaXJhdGlvbiBwb2ludCIgKGFrYS4gInN0YXJ0IG9mIGEgbmV3IG1lc3NhZ2UiKSBhcmUg
YWN0dWFsbHkgcmVjZWl2ZWQuICBJdCB3b3VsZCBqdXN0IG1lYW4gdGhhdCB0aGUgcmVjZWl2ZXIg
YXBwbGljYXRpb24gZ290IHRoZSBleHBpcmVkIG1lc3NhZ2U7IGl0IHdvdWxkIG5vdCBnZXQgY29u
ZnVzZWQgYWJvdXQgd2hlcmUgYSBuZXcgbWVzc2FnZSBzdGFydHMuDQoNCj4gWy4uLl0gaWRlbnRp
ZnlpbmcgYSBnYXAgWy4uLl0NCg0KRm9yIHRoZSByZWNlaXZlciwgaWRlbnRpZnlpbmcgYSBnYXAg
KHRvIG5vdGlmeSB0aGUgYXBwbGljYXRpb24gb2YgdGhlIGdhcCkgaXMgYWN0dWFsbHkgZWFzeS4g
IEdvdCBFWFBJUkVEX1NUUkVBTV9EQVRBIHRoYXQgY292ZXJzIHNvbWUgb2Zmc2V0cyB5b3UgbmV2
ZXIgcmVjZWl2ZWQ/ICBZb3UndmUgZ290IGEgZ2FwIHRvIG5vdGlmeSB0aGUgYXBwbGljYXRpb24g
YWJvdXQhDQoNCg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLQ0KRnJvbTogTWFydGluIFRo
b21zb24gW21haWx0bzptYXJ0aW4udGhvbXNvbkBnbWFpbC5jb21dIA0KU2VudDogV2VkbmVzZGF5
LCBNYXkgMzAsIDIwMTggODo1MSBQTQ0KVG86IE1pa2UgQmlzaG9wIDxtYmlzaG9wQGV2ZXF1ZWZv
dS5iZT4NCkNjOiBMdWJhc2hldiwgSWdvciA8aWx1YmFzaGVAYWthbWFpLmNvbT47IFFVSUMgV0cg
PHF1aWNAaWV0Zi5vcmc+DQpTdWJqZWN0OiBSZTogUGFydGlhbGx5IFJlbGlhYmxlIE1lc3NhZ2Ug
U3RyZWFtDQoNCkxpa2UgTWlrZSwgSSBmaW5kIHRoaXMgZ2FwIHRoaW5nIGNvbmZ1c2luZy4gIEFu
ZCBNaWtlJ3MgbWVzc2FnZSBoZWxwZWQsIGJ1dCBub3QgYSBsb3QuDQoNCkl0IHRvb2sgYSB3aGls
ZSB0byByZWFsaXplIHRoYXQgZm9yY2luZyBhIGdhcCBjcmVhdGVzIGEgbmV3IHN0YXJ0aW5nIHBv
aW50IGZvciB0aGUgbmV4dCBtZXNzYWdlIHRoYXQgZm9yY2VzIHRoZSByZWNpcGllbnQgdG8gcmVj
b2duaXplIGFuZCBkZWFsIHdpdGguICBIb3dldmVyLCB0aGUgbG9naWMgZm9yIGlkZW50aWZ5aW5n
IHRoYXQgaXMganVzdCBoYXJkIGFuZCBpdCdzIGFuIHVubmVjZXNzYXJ5IGltcG9zaXRpb24gaW4g
bXkgdmlldy4NCg0KU2F5IEkgc2VuZCBhIG1lc3NhZ2Ugd2l0aCBhIGxlbmd0aCBvZiAxMCBhbmQg
b25seSB0d28gb2N0ZXRzIG1ha2UgaXQgb250byB0aGUgd2lyZSAoYXMgd2l0aCB5b3VyIGV4YW1w
bGUpLCB0aGVuIGl0IGlzIGltbWVkaWF0ZWx5IGFiYW5kb25lZC4gIFlvdXIgc29sdXRpb24gd291
bGQgaGF2ZSB0aGUgRVhQSVJFRF9TVFJFQU1fREFUQSBmb3JjZSBhIGdhcCBhZnRlciB0aGUgc2Vj
b25kIG9jdGV0LCBzbyB0aGF0IHRoZSBuZXh0IG1lc3NhZ2UgY291bGQgc3RhcnQgYXQgb2Zmc2V0
IDMgcmF0aGVyIHRoYW4gb2Zmc2V0IDEwLiAgVGhhdCBzYXZlcyB0aGUgcmVtYWluaW5nIDcgb2N0
ZXRzIG9mIGZsb3cgY29udHJvbCBjcmVkaXQuICAoVXNlIGJpZ2dlciBudW1iZXJzIGFuZCBwZXJo
YXBzIGl0IHNlZW1zIG1vcmUgbW90aXZhdGluZykuDQoNCklmIHRoZSBvY3RldHMgdGhhdCBjb3Zl
ciB0aGUgZ2FwIHdlcmUgc2VudCwgdGhlbiB5b3UgaGF2ZSBhIHByb2JsZW0gYmVjYXVzZSBub3cg
eW91IGhhdmUgc2VudCB0d28gdmVyc2lvbnMgb2YgdGhlIHNhbWUgb2N0ZXRzLCBzbyB5b3UgY2Fu
IG9ubHkgZG8gdGhpcyBpZiB0aGUgb2N0ZXRzIHdlcmUgbmV2ZXIgc2VudC4gIEl0IHN0YXJ0cyB0
byBnZXQgY2xvc2VyIGFuZCBjbG9zZXIgdG8gdGhlIHBvaW50IHdoZXJlIGEgbmV3IHN0cmVhbSBp
cyBqdXN0IGVhc2llci4NCg0KV29yc3QsIEkgdGhpbmsgaXMgdGhhdCB0aGUgcmVjZWl2ZXIgaGFz
IHRvIGhhdmUgY29tcGxpY2F0ZWQgbG9naWMgZm9yIGlkZW50aWZ5aW5nIHRoYXQgYSBnYXAgZXhp
c3RzIGFuZCBkZWFsaW5nIHdpdGggaXQuICBJdCBoYXMgdG8gcmVhZCB1cCB0byB3aGF0IGl0IGhh
cywgb2JzZXJ2ZSB0aGF0IHRoZSBkYXRhIGhhcyBleHBpcmVkLCB0aGVuIGxlYXJuIHdoZXJlIHRo
ZSBnYXAgZW5kcywgdGhlbiByZXN5bmNocm9uaXplIGJhc2VkIG9uIDErZ2FwX2VuZCBmb3IgdGhl
IG5leHQgbWVzc2FnZS4NCg0KQmV0dGVyIHRvIGVhdCB0aGUgZmxvdyBjb250cm9sIGNvc3QgaW4g
bXkgdmlldy4gIE9yIHNlbmQgUlNUX1NUUkVBTSBhbmQgbWFrZSBhbm90aGVyIHN0cmVhbS4NCk9u
IFRodSwgTWF5IDMxLCAyMDE4IGF0IDg6NDggQU0gTWlrZSBCaXNob3AgPG1iaXNob3BAZXZlcXVl
Zm91LmJlPiB3cm90ZToNCj4NCj4gSSBmaW5kIHRoZSBvbmUgb2N0ZXQgZ2FwIGEgYml0IGNvbmZ1
c2luZywgYnV0IGFzIEkgdGhpbmsgYWJvdXQgaXQsIEkgc2VlIHdoeSB5b3UgbmVlZCBpdC4gIElm
IGFsbCB0aGUgc3RyZWFtIGRhdGEgYXJyaXZlZCBzdWNjZXNzZnVsbHkgKGJ1dCBoYWRu4oCZdCBi
ZWVuIGFja25vd2xlZGdlZCB5ZXQgZHVlIHRvIGxvc3Mgb2YgdGhlIEFDSywgZGVsYXksIGV0Yy4p
IGFuZCB0aGUgRVhQSVJFRF9TVFJFQU1fREFUQSBnZXRzIGxvc3QsIHRoZSByZWNlaXZlciBjYW4g
b25seSByZXRyb2FjdGl2ZWx5IHJlYWxpemUgdGhlcmUgd2FzIGEganVtcC4gIEhhdmluZyBhbiBv
Y3RldCB0aGF0IGlzIG5ldmVyIHRyYW5zbWl0dGVkIGVuc3VyZXMgdGhlIHJlY2VpdmVyIGFjdHVh
bGx5IHNlZXMgYSBnYXAsIHdoaWNoIG1lYW5zIHRoYXQgYW4gaW4tb3JkZXIgQVBJIHdpbGwgbm90
IHByb2NlZWQgdW50aWwgaXQgaGFzIHJlY2VpdmVkIGVpdGhlciB0aGUgbWlzc2luZyBvY3RldCBv
ciBhbiBFWFBJUkVEX1NUUkVBTV9EQVRBIGluZm9ybWluZyBpdCB0aGUgb2N0ZXQgd2lsbCBuZXZl
ciBhcnJpdmUuDQo+DQo+DQo+DQo+IFRoaXMgc2ltcGxpZmljYXRpb24gKHZlcnN1cyAtMDIpIGNv
bWVzIGF0IGEgcHJpY2U6ICBJZiBhbiBBUEkgd2VyZSBleHBvc2luZyBzdHJlYW0gZGF0YSBvdXQt
b2Ytb3JkZXIsIHRoZW4gaW4geW91ciBleGFtcGxlLCB0aGUgcmVjZWl2ZXIga25vd3MgdGhhdCBh
IG1lc3NhZ2UgYWx3YXlzIGJlZ2lucyBvbiBhIHRlbi1ieXRlIGJvdW5kYXJ5LiAgQSByZWNlaXZl
ciBjYW4gbm8gbG9uZ2VyIGZpbmQgdGVuLWJ5dGUgYm91bmRhcmllcywgYmVjYXVzZSB0aGUgb2Zm
c2V0IG9uIHRoZSByZWFkIHNpZGUgZG9lc27igJl0IG1hdGNoIHRoZSBvZmZzZXQgb24gdGhlIHNl
bmQgc2lkZS4gIEkgYWdyZWUgd2l0aCB5b3UgdGhhdCB0aGlzIHNlZW1zIGxpa2UgYSByZWFzb25h
YmxlIHRyYWRlLW9mZiBmb3IgdGhlIHNpbXBsZXIgZmxvdyBjb250cm9sLg0KPg0KPg0KPg0KPiBP
bmUgY29uZmxpY3QgSSBzZWUgaW4gdGhlIGRvYzoNCj4NCj4gwrcgICAgICAgICBTZWN0aW9uIDMg
c2F5czogIFJlY2VpcHQgb2YgYW4gRVhQSVJFRF9TVFJFQU1fREFUQSBkb2VzIG5vdCBhZHZhbmNl
IHRoZSBsYXJnZXN0IHJlY2VpdmVkIG9mZnNldCBmb3IgdGhlIHN0cmVhbS4NCj4NCj4gU2VjdGlv
biA1IHNheXM6ICBBIHJlY2VpdmVyIFNIT1VMRCBkaXNjYXJkIGFueSBzdHJlYW0gZGF0YSByZWNl
aXZlZCBmb3IgYW4gb2Zmc2V0IHNtYWxsZXIgdGhhbiB0aGUgbmV3IHNtYWxsZXN0IHJlY2VpdmUg
b2Zmc2V0LCBwb3NzaWJseSBhZHZhbmNpbmcgdGhlIGxhcmdlc3QgcmVjZWl2ZWQgb2Zmc2V0IGZv
ciB0aGUgc3RyZWFtLg0KPg0KPg0KPg0KPiBPdGhlciBtaW5vciBuaXRzIGFyZSBiZXR0ZXIgZG9u
ZSB2aWEgUFIuDQo+DQo+IEZyb206IFFVSUMgPHF1aWMtYm91bmNlc0BpZXRmLm9yZz4gT24gQmVo
YWxmIE9mIEx1YmFzaGV2LCBJZ29yDQo+IFNlbnQ6IFdlZG5lc2RheSwgTWF5IDMwLCAyMDE4IDk6
NDUgQU0NCj4gVG86IFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc+DQo+IFN1YmplY3Q6IFBhcnRpYWxs
eSBSZWxpYWJsZSBNZXNzYWdlIFN0cmVhbQ0KPg0KPg0KPg0KPiBJ4oCZdmUganVzdCB1cGxvYWRl
ZCBhIG5ldyBkcmFmdCBmb3IgcGFydGlhbGx5IHJlbGlhYmxlIFFVSUMgc3RyZWFtcy4gIE5vdGU6
IHRoaXMgZmVhdHVyZSBpcyBsaWtlbHkgbm90IGluIHNjb3BlIGZvciBWMSwgYnV0IGl0IGNhbiBi
ZSBhbiBleHRlbnNpb24gZm9yIFYxIGFuZC9vciBhIHBhcnQgb2YgVjIuDQo+DQo+DQo+DQo+IFRo
ZSBuZXcgdmVyc2lvbiAwMyAoaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWx1YmFz
aGV2LXF1aWMtcGFydGlhbC1yZWxpYWJpbGl0eS0wMykgbm8gbG9uZ2VyIG5lZWRzIGNvbXBsZXgg
ZmxvdyBjb250cm9sIGNoYW5nZXMgYW5kIHJlbW92ZXMgdGhlIG5lZWQgdG8gdHJhbnNtaXQgbXVs
dGlwbGUgZnJhbWVzIGluIHRoZSBzYW1lIHBhY2tldC4NCj4NCj4NCj4NCj4gSWdvcg0KPg0KPg0K
Pg0KPiBQLlMuDQo+DQo+ICAgVGhlcmUgaXMgYWxzbyBhIG5ldyB2ZXJzaW9uIDAyLCB3aGljaCBp
bmNsdWRlcyBhIG1vcmUgY29tcGxleCBhbGdvcml0aG0gd2l0aCBtb3JlIGZlYXR1cmVzIGFuZCBk
aWZmZXJlbnQgdHJhZGUtb2Zmcy4gIEJ1dCBJIHRoaW5rIHZlcnNpb24gMDMgaXMgYSBiZXR0ZXIg
bWF0Y2ggZm9yIHRoZSBuZWVkcyBzbyBmYXIuDQo=


From nobody Thu May 31 16:37:27 2018
Return-Path: <ilubashe@akamai.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5362B12D957 for <quic@ietfa.amsl.com>; Thu, 31 May 2018 16:37:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.709
X-Spam-Level: 
X-Spam-Status: No, score=-2.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 ipSf6GE3ktJT for <quic@ietfa.amsl.com>; Thu, 31 May 2018 16:37:21 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::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 0DC1E12EAE2 for <quic@ietf.org>; Thu, 31 May 2018 16:37:20 -0700 (PDT)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.22/8.16.0.22) with SMTP id w4VNb5ad031665; Fri, 1 Jun 2018 00:37:15 +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=c+7/EcgCylfvYNkQmav8iXWcp4CvhROR9YmK8F1etd8=; b=Vu9jakkaVmvaZzYFsMb8HcEIkdOt/9FSjsQlv+jWdVONF3dc2rB2TXgDbwX18C/w/eMh SwmMI65/TmPlIQMfuprVfNHw1d70G2qogYr+oCYUP8qKoMwxJpFSUnGB2E+IKOwaODNJ tzT5UP40rPut79rvv+W6sxe8cPuctixrvc2x/eczUuYyGw2oLMlijXnUnhpNs5PO2TCl L2WfcI8ZOL2EKdia1bLH1ZhtYF6qnO1OEDl8fxzCRLYH8f0/+bK3zGVMLneWk5Jmuump PkJuWtnA/n0cFZJBniBe2n8tHILtlo74vexRso7RURxRivfc+QKmRZ59LA/3+WQpxA0o VQ== 
Received: from prod-mail-ppoint3 (a96-6-114-86.deploy.static.akamaitechnologies.com [96.6.114.86] (may be forged)) by m0050102.ppops.net-00190b01. with ESMTP id 2ja5hg4yfu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 01 Jun 2018 00:37:14 +0100
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w4VNZX74010125; Thu, 31 May 2018 19:37:13 -0400
Received: from email.msg.corp.akamai.com ([172.27.25.33]) by prod-mail-ppoint3.akamai.com with ESMTP id 2j9cvvc38y-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 31 May 2018 19:37:12 -0400
Received: from ustx2ex-dag1mb6.msg.corp.akamai.com (172.27.27.107) by ustx2ex-dag1mb2.msg.corp.akamai.com (172.27.27.102) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Thu, 31 May 2018 18:37:11 -0500
Received: from ustx2ex-dag1mb6.msg.corp.akamai.com ([172.27.27.107]) by ustx2ex-dag1mb6.msg.corp.akamai.com ([172.27.27.107]) with mapi id 15.00.1365.000; Thu, 31 May 2018 16:37:11 -0700
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: Roberto Peon <fenix@fb.com>, Mike Bishop <mbishop@evequefou.be>, "Martin Thomson" <martin.thomson@gmail.com>
CC: QUIC WG <quic@ietf.org>
Subject: RE: Partially Reliable Message Stream
Thread-Topic: Partially Reliable Message Stream
Thread-Index: AdP4Mo3KTicRHsMuS7e4Jrowbk1vdQAMuR2gABOqt4AAAG2GAAAFOfmAABi7qAAAAkJSoA==
Date: Thu, 31 May 2018 23:37:11 +0000
Message-ID: <4a858eb49e774c34be2b0bab965bad9c@ustx2ex-dag1mb6.msg.corp.akamai.com>
References: <d263c36bc5264842a65f04fc3b017538@ustx2ex-dag1mb6.msg.corp.akamai.com> <SN1PR08MB18541BF8B27EA5484FA6A437DA6C0@SN1PR08MB1854.namprd08.prod.outlook.com>, <CABkgnnWUpaFvz3d0SJJ99JkhdQfwdaxYosKwj3dK9BVZUtZ_yw@mail.gmail.com> <BYAPR15MB2312A20C0FFF67119059D2B3CD630@BYAPR15MB2312.namprd15.prod.outlook.com>, <SN1PR08MB1854EB788295504BEE169A25DA630@SN1PR08MB1854.namprd08.prod.outlook.com> <BYAPR15MB2312B11929B6DEC29AC67CA3CD630@BYAPR15MB2312.namprd15.prod.outlook.com>
In-Reply-To: <BYAPR15MB2312B11929B6DEC29AC67CA3CD630@BYAPR15MB2312.namprd15.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.32.104]
Content-Type: multipart/alternative; boundary="_000_4a858eb49e774c34be2b0bab965bad9custx2exdag1mb6msgcorpak_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-31_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=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1805220000 definitions=main-1805310261
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-31_13:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1015 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1805220000 definitions=main-1805310261
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/T1A22JcAomGKJeB0emNLLnc0l2M>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 31 May 2018 23:37:26 -0000

--_000_4a858eb49e774c34be2b0bab965bad9custx2exdag1mb6msgcorpak_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Version 02 is certainly a more complete solution, but it is more complex.  =
I am very interested in hearing different people views on this trade-off.

I am curious of the specifics of an application you have in mind for this. =
 I.e. how keeping offsets the same on the sender and receiver helps with a =
message stream.  Are offsets themselves contained in the messages?  Does th=
e application communicate offsets outside of the message stream (on a diffe=
rent stream, for example)?

(It will probably work better to explore this next week in person.)


  *   Igor

From: Roberto Peon [mailto:fenix@fb.com]
Sent: Thursday, May 31, 2018 11:21 AM
To: Mike Bishop <mbishop@evequefou.be>; Martin Thomson <martin.thomson@gmai=
l.com>
Cc: QUIC WG <quic@ietf.org>; Lubashev, Igor <ilubashe@akamai.com>
Subject: Re: Partially Reliable Message Stream

Yes. You may want a single resource for an output which you may be generati=
ng in parallel. Even if a single thread 'owns' the stream, you've lost the =
ability to coordinate the data it recieves by monotonically increasing offs=
et.

Renumbering the offsets breaks the file-like abstraction we've effectively =
used for http.


-=3DR



Sent via the Samsung Galaxy S7, an AT&T 4G LTE smartphone


-------- Original message --------
From: Mike Bishop <mbishop@evequefou.be<mailto:mbishop@evequefou.be>>
Date: 5/30/18 8:33 PM (GMT-08:00)
To: Roberto Peon <fenix@fb.com<mailto:fenix@fb.com>>, Martin Thomson <marti=
n.thomson@gmail.com<mailto:martin.thomson@gmail.com>>
Cc: QUIC WG <quic@ietf.org<mailto:quic@ietf.org>>, "Lubashev, Igor" <ilubas=
he=3D40akamai.com@dmarc.ietf.org<mailto:ilubashe=3D40akamai.com@dmarc.ietf.=
org>>
Subject: RE: Partially Reliable Message Stream

Just to be clear....  You're suggesting multiple threads that would be writ=
ing to a single stream in parallel, rather than a single thread "owning" th=
e stream?

From: Roberto Peon <fenix@fb.com<mailto:fenix@fb.com>>
Sent: Wednesday, May 30, 2018 6:03 PM
To: Mike Bishop <mbishop@evequefou.be<mailto:mbishop@evequefou.be>>; Martin=
 Thomson <martin.thomson@gmail.com<mailto:martin.thomson@gmail.com>>
Cc: QUIC WG <quic@ietf.org<mailto:quic@ietf.org>>; Lubashev, Igor <ilubashe=
=3D40akamai.com@dmarc.ietf.org<mailto:ilubashe=3D40akamai.com@dmarc.ietf.or=
g>>
Subject: Re: Partially Reliable Message Stream

I find it confusing as well.  I far prefer keeping the offsets monotonicall=
y increasing as it allows for real-world use of a partially reliable stream=
 (where you may not recieve that data but you can at least figure out what =
you did get and interpret it).
I dont know how one wohud resolve the race even within the sending applicat=
ion -- one thread sends, another thread sends while the first says to forge=
t about stuff. I dont know what offset stuff ends up at in such cases, and =
so I cannot frame data in a way that is non-synchronous. That defeats some =
of the main reasons to do partial reliability (i.e. to reduce jitter).
Draft 02 seemed to be going in a better direction w.r.t the usecases i can =
conceive of. I think rewinding to that and then potentially figuring out ho=
w to simplify it would be fun!
I'm excited to have this being discussed, since there is pent up demand to =
use it already.
-=3DR
Get Outlook for Android<https://urldefense.proofpoint.com/v2/url?u=3Dhttps-=
3A__aka.ms_ghei36&d=3DDwMFAg&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3DC0sUo-LFNBaYfyo=
aCsf6TA&m=3DVOUj_MnwWf_PgdHvcGV1Se1o3k5jC8m8noKDixq8HqA&s=3D-xJb_JWOdL_DpDM=
43E06S54LPE-xkpYkSen4El-wkS4&e=3D>

________________________________
From: QUIC <quic-bounces@ietf.org<mailto:quic-bounces@ietf.org>> on behalf =
of Martin Thomson <martin.thomson@gmail.com<mailto:martin.thomson@gmail.com=
>>
Sent: Wednesday, May 30, 2018 5:50:59 PM
To: Mike Bishop
Cc: QUIC WG; Lubashev, Igor
Subject: Re: Partially Reliable Message Stream

Like Mike, I find this gap thing confusing.  And Mike's message
helped, but not a lot.

It took a while to realize that forcing a gap creates a new starting
point for the next message that forces the recipient to recognize and
deal with.  However, the logic for identifying that is just hard and
it's an unnecessary imposition in my view.

Say I send a message with a length of 10 and only two octets make it
onto the wire (as with your example), then it is immediately
abandoned.  Your solution would have the EXPIRED_STREAM_DATA force a
gap after the second octet, so that the next message could start at
offset 3 rather than offset 10.  That saves the remaining 7 octets of
flow control credit.  (Use bigger numbers and perhaps it seems more
motivating).

If the octets that cover the gap were sent, then you have a problem
because now you have sent two versions of the same octets, so you can
only do this if the octets were never sent.  It starts to get closer
and closer to the point where a new stream is just easier.

Worst, I think is that the receiver has to have complicated logic for
identifying that a gap exists and dealing with it.  It has to read up
to what it has, observe that the data has expired, then learn where
the gap ends, then resynchronize based on 1+gap_end for the next
message.

Better to eat the flow control cost in my view.  Or send RST_STREAM
and make another stream.
On Thu, May 31, 2018 at 8:48 AM Mike Bishop <mbishop@evequefou.be<mailto:mb=
ishop@evequefou.be>> wrote:
>
> I find the one octet gap a bit confusing, but as I think about it, I see =
why you need it.  If all the stream data arrived successfully (but hadn't b=
een acknowledged yet due to loss of the ACK, delay, etc.) and the EXPIRED_S=
TREAM_DATA gets lost, the receiver can only retroactively realize there was=
 a jump.  Having an octet that is never transmitted ensures the receiver ac=
tually sees a gap, which means that an in-order API will not proceed until =
it has received either the missing octet or an EXPIRED_STREAM_DATA informin=
g it the octet will never arrive.
>
>
>
> This simplification (versus -02) comes at a price:  If an API were exposi=
ng stream data out-of-order, then in your example, the receiver knows that =
a message always begins on a ten-byte boundary.  A receiver can no longer f=
ind ten-byte boundaries, because the offset on the read side doesn't match =
the offset on the send side.  I agree with you that this seems like a reaso=
nable trade-off for the simpler flow control.
>
>
>
> One conflict I see in the doc:
>
> *         Section 3 says:  Receipt of an EXPIRED_STREAM_DATA does not adv=
ance the largest received offset for the stream.
>
> Section 5 says:  A receiver SHOULD discard any stream data received for a=
n offset smaller than the new smallest receive offset, possibly advancing t=
he largest received offset for the stream.
>
>
>
> Other minor nits are better done via PR.
>
> From: QUIC <quic-bounces@ietf.org<mailto:quic-bounces@ietf.org>> On Behal=
f Of Lubashev, Igor
> Sent: Wednesday, May 30, 2018 9:45 AM
> To: QUIC WG <quic@ietf.org<mailto:quic@ietf.org>>
> Subject: Partially Reliable Message Stream
>
>
>
> I've just uploaded a new draft for partially reliable QUIC streams.  Note=
: this feature is likely not in scope for V1, but it can be an extension fo=
r V1 and/or a part of V2.
>
>
>
> The new version 03 (https://urldefense..proofpoint.com/v2/url?u=3Dhttps-3=
A__tools.ietf.org_html_draft-2Dlubashev-2Dquic-2Dpartial-2Dreliability-2D03=
&d=3DDwIFaQ&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3DC0sUo-LFNBaYfyoaCsf6TA&m=3DyyRpb=
e14kTYgY413gjVkOalWE_UC3xYerKpJqS8HiQo&s=3DXZ295xiZsN11yP8GLcdMs1jf7z0b2_Wh=
iIxMLLorZXo&e=3D<https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__too=
ls.ietf.org_html_draft-2Dlubashev-2Dquic-2Dpartial-2Dreliability-2D03&d=3DD=
wIFaQ&c=3D5VD0RTtNlTh3ycd41b3MUw&r=3DC0sUo-LFNBaYfyoaCsf6TA&m=3DyyRpbe14kTY=
gY413gjVkOalWE_UC3xYerKpJqS8HiQo&s=3DXZ295xiZsN11yP8GLcdMs1jf7z0b2_WhiIxMLL=
orZXo&e=3D>) no longer needs complex flow control changes and removes the n=
eed to transmit multiple frames in the same packet.
>
>
>
> Igor
>
>
>
> P.S.
>
>   There is also a new version 02, which includes a more complex algorithm=
 with more features and different trade-offs.  But I think version 03 is a =
better match for the needs so far.

--_000_4a858eb49e774c34be2b0bab965bad9custx2exdag1mb6msgcorpak_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<!--[if !mso]><style>v\:* {behavior:url(#default#VML);}
o\:* {behavior:url(#default#VML);}
w\:* {behavior:url(#default#VML);}
.shape {behavior:url(#default#VML);}
</style><![endif]--><style><!--
/* Font Definitions */
@font-face
	{font-family:Wingdings;
	panose-1:5 0 0 0 0 0 0 0 0 0;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0in;
	margin-right:0in;
	margin-bottom:0in;
	margin-left:.5in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
p.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
p.msonormal00, li.msonormal00, div.msonormal00
	{mso-style-name:msonormal0;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
p.emailquote, li.emailquote, div.emailquote
	{mso-style-name:emailquote;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:1.0pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.emailstyle20
	{mso-style-name:emailstyle20;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle22
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle23
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:361783004;
	mso-list-type:hybrid;
	mso-list-template-ids:-779863290 1751306384 67698691 67698693 67698689 676=
98691 67698693 67698689 67698691 67698693;}
@list l0:level1
	{mso-level-start-at:0;
	mso-level-number-format:bullet;
	mso-level-text:-;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Calibri",sans-serif;
	mso-fareast-font-family:Calibri;
	mso-bidi-font-family:"Times New Roman";}
@list l0:level2
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level3
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level4
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level5
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level6
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
@list l0:level7
	{mso-level-number-format:bullet;
	mso-level-text:\F0B7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Symbol;}
@list l0:level8
	{mso-level-number-format:bullet;
	mso-level-text:o;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:"Courier New";}
@list l0:level9
	{mso-level-number-format:bullet;
	mso-level-text:\F0A7;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-.25in;
	font-family:Wingdings;}
ol
	{margin-bottom:0in;}
ul
	{margin-bottom:0in;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Version 02 is certainly a more complete solution, bu=
t it is more complex.&nbsp; I am very interested in hearing different peopl=
e views on this trade-off.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I am curious of the specifics of an application you =
have in mind for this.&nbsp; I.e. how keeping offsets the same on the sende=
r and receiver helps with a message stream.&nbsp; Are offsets themselves co=
ntained in the messages?&nbsp; Does the application
 communicate offsets outside of the message stream (on a different stream, =
for example)?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">(It will probably work better to explore this next w=
eek in person.)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"MsoListParagraph" style=3D"margin-left:0in;mso-list:l0 level1 =
lfo1">Igor<o:p></o:p></li></ul>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Roberto Peon [mailto:fenix@fb.com] <br>
<b>Sent:</b> Thursday, May 31, 2018 11:21 AM<br>
<b>To:</b> Mike Bishop &lt;mbishop@evequefou.be&gt;; Martin Thomson &lt;mar=
tin.thomson@gmail.com&gt;<br>
<b>Cc:</b> QUIC WG &lt;quic@ietf.org&gt;; Lubashev, Igor &lt;ilubashe@akama=
i.com&gt;<br>
<b>Subject:</b> Re: Partially Reliable Message Stream<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<p class=3D"MsoNormal">Yes. You may want a single resource for an output wh=
ich you may be generating in parallel. Even if a single thread 'owns' the s=
tream, you've lost the ability to coordinate the data it recieves by monoto=
nically increasing offset.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Renumbering the offsets breaks the file-like abstrac=
tion we've effectively used for http.<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">-=3DR<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div id=3D"composer_signature">
<div>
<p class=3D"MsoNormal"><span style=3D"font-size:9.5pt;color:#575757">Sent v=
ia the Samsung Galaxy S7, an AT&amp;T 4G LTE smartphone<o:p></o:p></span></=
p>
</div>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<p class=3D"MsoNormal">-------- Original message --------<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">From: Mike Bishop &lt;<a href=3D"mailto:mbishop@eveq=
uefou.be">mbishop@evequefou.be</a>&gt;
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Date: 5/30/18 8:33 PM (GMT-08:00) <o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">To: Roberto Peon &lt;<a href=3D"mailto:fenix@fb.com"=
>fenix@fb.com</a>&gt;, Martin Thomson &lt;<a href=3D"mailto:martin.thomson@=
gmail.com">martin.thomson@gmail.com</a>&gt;
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Cc: QUIC WG &lt;<a href=3D"mailto:quic@ietf.org">qui=
c@ietf.org</a>&gt;, &quot;Lubashev, Igor&quot; &lt;<a href=3D"mailto:ilubas=
he=3D40akamai.com@dmarc.ietf.org">ilubashe=3D40akamai.com@dmarc.ietf.org</a=
>&gt;
<o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal">Subject: RE: Partially Reliable Message Stream <o:p>=
</o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal">Just to be clear&#8230;.&nbsp; You&#8217;re suggesti=
ng multiple threads that would be writing to a single stream in parallel, r=
ather than a single thread &#8220;owning&#8221; the stream?<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Roberto Peon &lt;<a href=3D"mailto:feni=
x@fb.com">fenix@fb.com</a>&gt;
<br>
<b>Sent:</b> Wednesday, May 30, 2018 6:03 PM<br>
<b>To:</b> Mike Bishop &lt;<a href=3D"mailto:mbishop@evequefou.be">mbishop@=
evequefou.be</a>&gt;; Martin Thomson &lt;<a href=3D"mailto:martin.thomson@g=
mail.com">martin.thomson@gmail.com</a>&gt;<br>
<b>Cc:</b> QUIC WG &lt;<a href=3D"mailto:quic@ietf.org">quic@ietf.org</a>&g=
t;; Lubashev, Igor &lt;<a href=3D"mailto:ilubashe=3D40akamai.com@dmarc.ietf=
.org">ilubashe=3D40akamai.com@dmarc.ietf.org</a>&gt;<br>
<b>Subject:</b> Re: Partially Reliable Message Stream<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Arial&quot;,sans-serif;color:black">I find it confusing as well=
.&nbsp; I far prefer keeping the offsets monotonically increasing as it all=
ows for real-world use of a partially reliable stream
 (where you may not recieve that data but you can at least figure out what =
you did get and interpret it).</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Arial&quot;,sans-serif;color:black">I dont know how one wohud r=
esolve the race even within the sending application -- one thread sends, an=
other thread sends while the first says to forget
 about stuff. I dont know what offset stuff ends up at in such cases, and s=
o I cannot frame data in a way that is non-synchronous. That defeats some o=
f the main reasons to do partial reliability (i.e. to reduce jitter).</span=
><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Arial&quot;,sans-serif;color:black">Draft 02 seemed to be going=
 in a better direction w.r.t the usecases i can conceive of. I think rewind=
ing to that and then potentially figuring out how
 to simplify it would be fun!</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:black">I'm excited to have this being discussed, since there is p=
ent up demand to use it already.</span><o:p></o:p></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt"><span style=3D"font-f=
amily:&quot;Arial&quot;,sans-serif;color:black">-=3DR</span><o:p></o:p></p>
</div>
<div>
<div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:black">Get
<a href=3D"https://urldefense.proofpoint.com/v2/url?u=3Dhttps-3A__aka.ms_gh=
ei36&amp;d=3DDwMFAg&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3DC0sUo-LFNBaYfyoa=
Csf6TA&amp;m=3DVOUj_MnwWf_PgdHvcGV1Se1o3k5jC8m8noKDixq8HqA&amp;s=3D-xJb_JWO=
dL_DpDM43E06S54LPE-xkpYkSen4El-wkS4&amp;e=3D">
Outlook for Android</a></span><o:p></o:p></p>
</div>
<p class=3D"MsoNormal"><span style=3D"font-family:&quot;Arial&quot;,sans-se=
rif;color:black">&nbsp;</span><o:p></o:p></p>
</div>
<div class=3D"MsoNormal" align=3D"center" style=3D"text-align:center">
<hr size=3D"2" width=3D"98%" align=3D"center">
</div>
<div id=3D"x_divRplyFwdMsg">
<p class=3D"MsoNormal"><b><span style=3D"color:black">From:</span></b><span=
 style=3D"color:black"> QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org">q=
uic-bounces@ietf.org</a>&gt; on behalf of Martin Thomson &lt;<a href=3D"mai=
lto:martin.thomson@gmail.com">martin.thomson@gmail.com</a>&gt;<br>
<b>Sent:</b> Wednesday, May 30, 2018 5:50:59 PM<br>
<b>To:</b> Mike Bishop<br>
<b>Cc:</b> QUIC WG; Lubashev, Igor<br>
<b>Subject:</b> Re: Partially Reliable Message Stream</span> <o:p></o:p></p=
>
<div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</div>
</div>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-bottom:12.0pt">Like Mike, I find thi=
s gap thing confusing.&nbsp; And Mike's message<br>
helped, but not a lot.<br>
<br>
It took a while to realize that forcing a gap creates a new starting<br>
point for the next message that forces the recipient to recognize and<br>
deal with.&nbsp; However, the logic for identifying that is just hard and<b=
r>
it's an unnecessary imposition in my view.<br>
<br>
Say I send a message with a length of 10 and only two octets make it<br>
onto the wire (as with your example), then it is immediately<br>
abandoned.&nbsp; Your solution would have the EXPIRED_STREAM_DATA force a<b=
r>
gap after the second octet, so that the next message could start at<br>
offset 3 rather than offset 10.&nbsp; That saves the remaining 7 octets of<=
br>
flow control credit.&nbsp; (Use bigger numbers and perhaps it seems more<br=
>
motivating).<br>
<br>
If the octets that cover the gap were sent, then you have a problem<br>
because now you have sent two versions of the same octets, so you can<br>
only do this if the octets were never sent.&nbsp; It starts to get closer<b=
r>
and closer to the point where a new stream is just easier.<br>
<br>
Worst, I think is that the receiver has to have complicated logic for<br>
identifying that a gap exists and dealing with it.&nbsp; It has to read up<=
br>
to what it has, observe that the data has expired, then learn where<br>
the gap ends, then resynchronize based on 1&#43;gap_end for the next<br>
message.<br>
<br>
Better to eat the flow control cost in my view.&nbsp; Or send RST_STREAM<br=
>
and make another stream.<br>
On Thu, May 31, 2018 at 8:48 AM Mike Bishop &lt;<a href=3D"mailto:mbishop@e=
vequefou.be">mbishop@evequefou.be</a>&gt; wrote:<br>
&gt;<br>
&gt; I find the one octet gap a bit confusing, but as I think about it, I s=
ee why you need it.&nbsp; If all the stream data arrived successfully (but =
hadn&#8217;t been acknowledged yet due to loss of the ACK, delay, etc.) and=
 the EXPIRED_STREAM_DATA gets lost, the receiver
 can only retroactively realize there was a jump.&nbsp; Having an octet tha=
t is never transmitted ensures the receiver actually sees a gap, which mean=
s that an in-order API will not proceed until it has received either the mi=
ssing octet or an EXPIRED_STREAM_DATA
 informing it the octet will never arrive.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; This simplification (versus -02) comes at a price:&nbsp; If an API wer=
e exposing stream data out-of-order, then in your example, the receiver kno=
ws that a message always begins on a ten-byte boundary.&nbsp; A receiver ca=
n no longer find ten-byte boundaries, because
 the offset on the read side doesn&#8217;t match the offset on the send sid=
e.&nbsp; I agree with you that this seems like a reasonable trade-off for t=
he simpler flow control.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; One conflict I see in the doc:<br>
&gt;<br>
&gt; &middot;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Section 3 say=
s:&nbsp; Receipt of an EXPIRED_STREAM_DATA does not advance the largest rec=
eived offset for the stream.<br>
&gt;<br>
&gt; Section 5 says:&nbsp; A receiver SHOULD discard any stream data receiv=
ed for an offset smaller than the new smallest receive offset, possibly adv=
ancing the largest received offset for the stream.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Other minor nits are better done via PR.<br>
&gt;<br>
&gt; From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org">quic-bounces@i=
etf.org</a>&gt; On Behalf Of Lubashev, Igor<br>
&gt; Sent: Wednesday, May 30, 2018 9:45 AM<br>
&gt; To: QUIC WG &lt;<a href=3D"mailto:quic@ietf.org">quic@ietf.org</a>&gt;=
<br>
&gt; Subject: Partially Reliable Message Stream<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; I&#8217;ve just uploaded a new draft for partially reliable QUIC strea=
ms.&nbsp; Note: this feature is likely not in scope for V1, but it can be a=
n extension for V1 and/or a part of V2.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; The new version 03 (<a href=3D"https://urldefense.proofpoint.com/v2/ur=
l?u=3Dhttps-3A__tools.ietf.org_html_draft-2Dlubashev-2Dquic-2Dpartial-2Drel=
iability-2D03&amp;d=3DDwIFaQ&amp;c=3D5VD0RTtNlTh3ycd41b3MUw&amp;r=3DC0sUo-L=
FNBaYfyoaCsf6TA&amp;m=3DyyRpbe14kTYgY413gjVkOalWE_UC3xYerKpJqS8HiQo&amp;s=
=3DXZ295xiZsN11yP8GLcdMs1jf7z0b2_WhiIxMLLorZXo&amp;e=3D">https://urldefense=
..proofpoint.com/v2/url?u=3Dhttps-3A__tools.ietf.org_html_draft-2Dlubashev-=
2Dquic-2Dpartial-2Dreliability-2D03&amp;d=3DDwIFaQ&amp;c=3D5VD0RTtNlTh3ycd4=
1b3MUw&amp;r=3DC0sUo-LFNBaYfyoaCsf6TA&amp;m=3DyyRpbe14kTYgY413gjVkOalWE_UC3=
xYerKpJqS8HiQo&amp;s=3DXZ295xiZsN11yP8GLcdMs1jf7z0b2_WhiIxMLLorZXo&amp;e=3D=
</a>)
 no longer needs complex flow control changes and removes the need to trans=
mit multiple frames in the same packet.<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; Igor<br>
&gt;<br>
&gt;<br>
&gt;<br>
&gt; P.S.<br>
&gt;<br>
&gt;&nbsp;&nbsp; There is also a new version 02, which includes a more comp=
lex algorithm with more features and different trade-offs.&nbsp; But I thin=
k version 03 is a better match for the needs so far.<o:p></o:p></p>
</div>
</div>
</div>
</div>
</body>
</html>

--_000_4a858eb49e774c34be2b0bab965bad9custx2exdag1mb6msgcorpak_--


From nobody Thu May 31 17:18:34 2018
Return-Path: <ilubashe@akamai.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A86FD12025C for <quic@ietfa.amsl.com>; Thu, 31 May 2018 17:18:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.709
X-Spam-Level: 
X-Spam-Status: No, score=-2.709 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, URIBL_BLOCKED=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 9IAcwdWlbtQh for <quic@ietfa.amsl.com>; Thu, 31 May 2018 17:18:28 -0700 (PDT)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [IPv6:2620:100:9005:57f::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 DF20C120227 for <quic@ietf.org>; Thu, 31 May 2018 17:18:27 -0700 (PDT)
Received: from pps.filterd (m0122331.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w510HEHd008770; Fri, 1 Jun 2018 01:18:19 +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=NWKIcSdSwL18taE04yFFRZnr/YOUin0eJ8HiokrIqXY=; b=Sfqx76PIwvBdpIuyWLfnULU/bAZfP7Q6P0uLllymUmMmt5DjS65F24zWFbrMdgNRZlTQ deoa5xzrLHC/hB/1lgOS93nrrBNFL+G+H6gy2cWm4spuun42IpY0qVyWQ0O8uAbY8opd XdEYthUVFBX8FH/acU43auOw5MQBEDSuVuzJvTeMuFoXugKtccgIxEeHd+F5qOWTWkOt noZWmCwlCGaCLeTMCxrXmm/Rz7HoYLs81ZsxTl38SvephHZD0E/K/HMJ7wVlU8QaYRhv H+z8kVi7w+M0y1N/oS3SGmdCZzBBU5qf99qTTJEiO2qC5+YEEXkfZ1h9OahuqYgGpM/+ oA== 
Received: from prod-mail-ppoint3 (a96-6-114-86.deploy.static.akamaitechnologies.com [96.6.114.86] (may be forged)) by mx0b-00190b01.pphosted.com with ESMTP id 2jahhkam3w-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 01 Jun 2018 01:18:18 +0100
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.21/8.16.0.21) with SMTP id w510BAQx012096; Thu, 31 May 2018 20:18:18 -0400
Received: from email.msg.corp.akamai.com ([172.27.25.33]) by prod-mail-ppoint3.akamai.com with ESMTP id 2j9cvvc8rn-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 31 May 2018 20:18:17 -0400
Received: from ustx2ex-dag1mb6.msg.corp.akamai.com (172.27.27.107) by ustx2ex-dag1mb5.msg.corp.akamai.com (172.27.27.105) with Microsoft SMTP Server (TLS) id 15.0.1365.1; Thu, 31 May 2018 19:18:15 -0500
Received: from ustx2ex-dag1mb6.msg.corp.akamai.com ([172.27.27.107]) by ustx2ex-dag1mb6.msg.corp.akamai.com ([172.27.27.107]) with mapi id 15.00.1365.000; Thu, 31 May 2018 17:18:15 -0700
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: Jana Iyengar <jri.ietf@gmail.com>, Roberto Peon <fenix@fb.com>
CC: Mike Bishop <mbishop@evequefou.be>, Martin Thomson <martin.thomson@gmail.com>, QUIC WG <quic@ietf.org>
Subject: RE: Partially Reliable Message Stream
Thread-Topic: Partially Reliable Message Stream
Thread-Index: AdP4Mo3KTicRHsMuS7e4Jrowbk1vdQAMuR2gABOqt4AAAG2GAAAFOfmAABi7qAAACwyJAAAIJ2uA
Date: Fri, 1 Jun 2018 00:18:15 +0000
Message-ID: <373707b557534c0e8a5fffcabf3cb2cf@ustx2ex-dag1mb6.msg.corp.akamai.com>
References: <d263c36bc5264842a65f04fc3b017538@ustx2ex-dag1mb6.msg.corp.akamai.com> <SN1PR08MB18541BF8B27EA5484FA6A437DA6C0@SN1PR08MB1854.namprd08.prod.outlook.com> <CABkgnnWUpaFvz3d0SJJ99JkhdQfwdaxYosKwj3dK9BVZUtZ_yw@mail.gmail.com> <BYAPR15MB2312A20C0FFF67119059D2B3CD630@BYAPR15MB2312.namprd15.prod.outlook.com> <SN1PR08MB1854EB788295504BEE169A25DA630@SN1PR08MB1854.namprd08.prod.outlook.com> <BYAPR15MB2312B11929B6DEC29AC67CA3CD630@BYAPR15MB2312.namprd15.prod.outlook.com> <CACpbDcdoc9T-4hSEEko+j5ihRaMQW8VR+pgdof7k-5E7stSk8Q@mail.gmail.com>
In-Reply-To: <CACpbDcdoc9T-4hSEEko+j5ihRaMQW8VR+pgdof7k-5E7stSk8Q@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [172.19.32.104]
Content-Type: multipart/alternative; boundary="_000_373707b557534c0e8a5fffcabf3cb2cfustx2exdag1mb6msgcorpak_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-31_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=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1805220000 definitions=main-1806010001
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-31_13:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 suspectscore=0 phishscore=0 bulkscore=0 spamscore=0 clxscore=1011 lowpriorityscore=0 mlxscore=0 impostorscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1805220000 definitions=main-1806010002
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/id7laWrYPDVBhnyVDENz9xOwRGg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2018 00:18:33 -0000

--_000_373707b557534c0e8a5fffcabf3cb2cfustx2exdag1mb6msgcorpak_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

VGhhbmtzLCBKYW5hLg0KDQpTdHJlYW0gR3JvdXBzIGlzIGFuIGludGVyZXN0aW5nIGlkZWEgdGhh
dCB3b3VsZCBuZWVkIHRvIGJlIGZsdXNoZWQgb3V0IGZ1cnRoZXIgdG8gc2VlIHdoZXJlIGl0IGxl
YWRzIHVzLiAgSSB3YXMgdHJ5aW5nIHRvIG1pbmltaXplIHRoZSBjaGFuZ2VzIHRvIFFVSUMgYW5k
IGxpbWl0aW5nIHRoZSBkZXNpZ24gdG8gYXBwbGljYXRpb25zIHRoYXQgd2FudCBpbi1vcmRlciBt
ZXNzYWdlIGRlbGl2ZXJ5IGJ1dCBwcmVmZXIgdG8gZHJvcCBvbGQgbWVzc2FnZXMgaW4gZmF2b3Ig
b2YgYSBtb3JlIHRpbWVseSByZWNlaXB0IG9mIG5ld2VyIG1lc3NhZ2VzLiAgSS5lLiB0aGluZ3Mg
bGlrZSByZWFsLXRpbWUgYXVkaW8vdmlkZW8sIHBlci1jaGFyYWN0ZXIgZ2FtZSBzdGF0ZSB1cGRh
dGVzLCB0ZWxlbWV0cnkgdXBkYXRlcy4NCg0KMXN0IENsYXNzIE1lc3NhZ2VzIGNvdWxkIGFjY29t
cGxpc2ggbW9yZSwgYnV0LCBhcyB5b3Ugc2FpZCwgeW914oCZZCBuZWVkIHRvIGRlc2lnbiBmbG93
IGNvbnRyb2wgZm9yIHRoZXNlLiAgQW5kIHRoYXQgd2FzIHRoZSBoYXJkZXN0IHBhcnQsIGFzIEkg
ZGlzY292ZXJlZCENCg0KKEluIGZhY3QsIHZlcnNpb24gMDMgZmxvdyBjb250cm9sIGFjY291bnRp
bmcgaXMgd3JvbmcsIGFzIEkgdGhpbmsgYWJvdXQgaXQuICBJbnN0ZWFkIG9mIOKAnFJlY2VpcHQg
b2YgYW4gRVhQSVJFRF9TVFJFQU1fREFUQSBkb2VzIG5vdCBhZHZhbmNlIHRoZSBsYXJnZXN0IHJl
Y2VpdmVkIG9mZnNldCBmb3IgdGhlIHN0cmVhbS7igJ0sIGl0IHNob3VsZCBzYXkg4oCcSWYgdGhl
IGxhcmdlc3QgcmVjZWl2ZWQgb2Zmc2V0IGlzIHNtYWxsZXIgdGhhbiBNaW5pbXVtIFN0cmVhbSBP
ZmZzZXQgZm9yIHRoZSBzdHJlYW0sIGl0IGlzIGFkdmFuY2VkIHRvIE1pbmltdW0gU3RyZWFtIE9m
ZnNldCBtaW51cyAxLuKAnSAgVGhpcyB3aWxsIGNhdGNoIGEgcm9ndWUgc2VuZGVyIHZpb2xhdGlu
ZyBmbG93IGNvbnRyb2wgYnkgc2VuZGluZyBhIGh1Z2UgTWluaW11bSBTdHJlYW0gT2Zmc2V0LCBp
biBhbiBhdHRlbXB0IHRvIGdldCB0aGUgcmVjZWl2ZXIgdG8gaW5jcmVhc2UgaXRzIFNUUkVBTV9N
QVhfREFUQSB0byDigJxNaW5pbXVtIFN0cmVhbSBPZmZzZXTigJ0gKyBzdHJlYW1fYnVmZmVyX3Np
emUgYW5kIHRoZW4gdG8gZWZmZWN0IGEgY29ycmVzcG9uZGluZyBodWdlIGluY3JlYXNlIGluIE1B
WF9EQVRBLiAgVGhhdCB3b3VsZCBhbGxvdyB0aGUgc2VuZGVyIHRvIHNlbmQgZGF0YSBvbiBvdGhl
ciBzdHJlYW1zIGVmZmVjdGl2ZWx5IHdpdGhvdXQgYSBjb25uZWN0aW9uIGZsb3cgY29udHJvbCBs
aW1pdC4pDQoNCg0KDQpGcm9tOiBKYW5hIEl5ZW5nYXIgW21haWx0bzpqcmkuaWV0ZkBnbWFpbC5j
b21dDQpTZW50OiBUaHVyc2RheSwgTWF5IDMxLCAyMDE4IDQ6MzcgUE0NClRvOiBSb2JlcnRvIFBl
b24gPGZlbml4QGZiLmNvbT4NCkNjOiBNaWtlIEJpc2hvcCA8bWJpc2hvcEBldmVxdWVmb3UuYmU+
OyBNYXJ0aW4gVGhvbXNvbiA8bWFydGluLnRob21zb25AZ21haWwuY29tPjsgUVVJQyBXRyA8cXVp
Y0BpZXRmLm9yZz47IEx1YmFzaGV2LCBJZ29yIDxpbHViYXNoZUBha2FtYWkuY29tPg0KU3ViamVj
dDogUmU6IFBhcnRpYWxseSBSZWxpYWJsZSBNZXNzYWdlIFN0cmVhbQ0KDQpJJ20gbm90IGtlZW4g
dG8gZ2V0IGludG8gdGhlIHdlZWRzIG9mIHRoaXMgZGlzY3Vzc2lvbiBhdCB0aGlzIHRpbWUgKGFz
IHlvdSBzYXksIGl0J3MgZm9yIHYyKSwgYnV0IEkgdW5kZXJzdGFuZCB0aGUgb3ZlcmFsbCBkZXNp
Z24uIEEgZmV3IGhpZ2hlci1vcmRlciBwb2ludHMgd2l0aCB0aGlzIGRlc2lnbiBkaXJlY3Rpb246
DQoNCjEuIFRoZXJlJ3MgY2xlYXIgZGVtYXJjYXRpb24gb2YgYXBwIG1lc3NhZ2VzLCBidXQgdGhl
eSBhcmVuJ3QgcmVhbGx5IG1hZGUgZmlyc3QgY2xhc3MgY2l0aXplbnMuIElmIHlvdSBkaWQgdGhh
dCwgSSBpbWFnaW5lIHRoYXQgeW91IG1pZ2h0IGhhdmUgYSBzaW1wbGVyIGRlc2lnbi4gRm9yIGlu
c3RhbmNlLCBkZWZpbmUgYSBNU0dfU1RSRUFNIGZyYW1lLCB3aGljaCBzdXBwb3J0cyBtZXNzYWdl
IHN0cmVhbXMgKGluc3RlYWQgb2YgdGhlIGN1cnJlbnQgYnl0ZSBzdHJlYW1zKSwgYW5kIHRoZW4g
eW91IGNhbiBjYW5jZWwgbWVzc2FnZXMgZWFzaWx5IHdpdGhvdXQgaGF2aW5nIHRvIGRvIHN0cmVh
bSBvZmZzZXQgc2hlbmFuaWdhbnMuDQoNCjIuIFlvdXIgZGVzaWduIGhhcyBleGFjdGx5IG9uZSBv
cmRlcmluZyBjYXBhYmlsaXR5LCB3aGljaCBpcyBsaW1pdGluZy4gR2VuZXJhbGx5LCBhcHBzIHRo
YXQgY2FuIGRyb3AgbWVzc2FnZXMgYW5kIHJlYWQgc3Vic2VxdWVudCBvbmVzIGFyZSBhbHNvIGNh
cGFibGUgb2YgaGFuZGxpbmcgbWVzc2FnZXMgb3V0IG9mIHNlcXVlbmNlLiBZb3UnbGwgd2FudCB0
byBzdXBwb3J0IHBhcnRpYWwgb3JkZXJpbmcgYXMgd2VsbCBhbmQgbm90IGNvbnN0cmFpbiBtZXNz
YWdlcyB0byBiZSBvbmx5IGRlbGl2ZXJlZCBpbiBzdHJpY3RseSBsaW5lYXIgb3JkZXIuDQoNCjMu
IEknbSBrZWVuIHRvIHNlZSB3aGF0IHdlIGNhbiBkbyB3aXRoIHVzaW5nIHN0cmVhbXMgYXMgbWVz
c2FnZXMuIFdlIGRvbid0IG5lZWQgdG8gcHVudCBldmVyeXRoaW5nIHRvIHRoZSBhcHAgKGFzIHlv
dXIgdGV4dCBzdWdnZXN0cyksIGJ1dCB3ZSBjYW4gc3RhcnQgd2l0aCBhIGdyb3VwaW5nIG9mIHN0
cmVhbXMgKG9yIG1lc3NhZ2VzKSBhbmQgYnVpbGRpbmcgZmxvdyBjb250cm9sIG1lY2hhbmlzbXMg
Zm9yIHRoZXNlIGdyb3Vwcy4gSSBzdXNwZWN0IHRoaXMgbWlnaHQgYmUgY2xlYW5lciwgYW5kIGl0
IGdpdmVzIHlvdSBmbGV4aWJpbGl0eSB0byBjb25zaWRlciB2YXJpb3VzIG9yZGVyaW5ncyBvZiBt
ZXNzYWdlcy4gV2hlbiB3ZSdyZSBjbG9zZXIgdG8gdjIsIEknbSBoYXBweSB0byBzcGluIHVwIGEg
ZHJhZnQgZXhwbG9yaW5nIHRoaXMgZGlyZWN0aW9uLg0KDQpPbiBUaHUsIE1heSAzMSwgMjAxOCBh
dCA4OjIxIEFNLCBSb2JlcnRvIFBlb24gPGZlbml4QGZiLmNvbTxtYWlsdG86ZmVuaXhAZmIuY29t
Pj4gd3JvdGU6DQpZZXMuIFlvdSBtYXkgd2FudCBhIHNpbmdsZSByZXNvdXJjZSBmb3IgYW4gb3V0
cHV0IHdoaWNoIHlvdSBtYXkgYmUgZ2VuZXJhdGluZyBpbiBwYXJhbGxlbC4gRXZlbiBpZiBhIHNp
bmdsZSB0aHJlYWQgJ293bnMnIHRoZSBzdHJlYW0sIHlvdSd2ZSBsb3N0IHRoZSBhYmlsaXR5IHRv
IGNvb3JkaW5hdGUgdGhlIGRhdGEgaXQgcmVjaWV2ZXMgYnkgbW9ub3RvbmljYWxseSBpbmNyZWFz
aW5nIG9mZnNldC4NCg0KUmVudW1iZXJpbmcgdGhlIG9mZnNldHMgYnJlYWtzIHRoZSBmaWxlLWxp
a2UgYWJzdHJhY3Rpb24gd2UndmUgZWZmZWN0aXZlbHkgdXNlZCBmb3IgaHR0cC4NCg0KDQotPVIN
Cg0KDQoNClNlbnQgdmlhIHRoZSBTYW1zdW5nIEdhbGF4eSBTNywgYW4gQVQmVCA0RyBMVEUgc21h
cnRwaG9uZQ0KDQoNCi0tLS0tLS0tIE9yaWdpbmFsIG1lc3NhZ2UgLS0tLS0tLS0NCkZyb206IE1p
a2UgQmlzaG9wIDxtYmlzaG9wQGV2ZXF1ZWZvdS5iZTxtYWlsdG86bWJpc2hvcEBldmVxdWVmb3Uu
YmU+Pg0KRGF0ZTogNS8zMC8xOCA4OjMzIFBNIChHTVQtMDg6MDApDQpUbzogUm9iZXJ0byBQZW9u
IDxmZW5peEBmYi5jb208bWFpbHRvOmZlbml4QGZiLmNvbT4+LCBNYXJ0aW4gVGhvbXNvbiA8bWFy
dGluLnRob21zb25AZ21haWwuY29tPG1haWx0bzptYXJ0aW4udGhvbXNvbkBnbWFpbC5jb20+Pg0K
Q2M6IFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc8bWFpbHRvOnF1aWNAaWV0Zi5vcmc+PiwgIkx1YmFz
aGV2LCBJZ29yIiA8aWx1YmFzaGU9NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnPG1haWx0bzo0
MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmc+Pg0KU3ViamVjdDogUkU6IFBhcnRpYWxseSBSZWxp
YWJsZSBNZXNzYWdlIFN0cmVhbQ0KDQpKdXN0IHRvIGJlIGNsZWFy4oCmLiAgWW914oCZcmUgc3Vn
Z2VzdGluZyBtdWx0aXBsZSB0aHJlYWRzIHRoYXQgd291bGQgYmUgd3JpdGluZyB0byBhIHNpbmds
ZSBzdHJlYW0gaW4gcGFyYWxsZWwsIHJhdGhlciB0aGFuIGEgc2luZ2xlIHRocmVhZCDigJxvd25p
bmfigJ0gdGhlIHN0cmVhbT8NCg0KRnJvbTogUm9iZXJ0byBQZW9uIDxmZW5peEBmYi5jb208bWFp
bHRvOmZlbml4QGZiLmNvbT4+DQpTZW50OiBXZWRuZXNkYXksIE1heSAzMCwgMjAxOCA2OjAzIFBN
DQpUbzogTWlrZSBCaXNob3AgPG1iaXNob3BAZXZlcXVlZm91LmJlPG1haWx0bzptYmlzaG9wQGV2
ZXF1ZWZvdS5iZT4+OyBNYXJ0aW4gVGhvbXNvbiA8bWFydGluLnRob21zb25AZ21haWwuY29tPG1h
aWx0bzptYXJ0aW4udGhvbXNvbkBnbWFpbC5jb20+Pg0KQ2M6IFFVSUMgV0cgPHF1aWNAaWV0Zi5v
cmc8bWFpbHRvOnF1aWNAaWV0Zi5vcmc+PjsgTHViYXNoZXYsIElnb3IgPGlsdWJhc2hlPTQwYWth
bWFpLmNvbUBkbWFyYy5pZXRmLm9yZzxtYWlsdG86NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3Jn
Pj4NClN1YmplY3Q6IFJlOiBQYXJ0aWFsbHkgUmVsaWFibGUgTWVzc2FnZSBTdHJlYW0NCg0KSSBm
aW5kIGl0IGNvbmZ1c2luZyBhcyB3ZWxsLi4gIEkgZmFyIHByZWZlciBrZWVwaW5nIHRoZSBvZmZz
ZXRzIG1vbm90b25pY2FsbHkgaW5jcmVhc2luZyBhcyBpdCBhbGxvd3MgZm9yIHJlYWwtd29ybGQg
dXNlIG9mIGEgcGFydGlhbGx5IHJlbGlhYmxlIHN0cmVhbSAod2hlcmUgeW91IG1heSBub3QgcmVj
aWV2ZSB0aGF0IGRhdGEgYnV0IHlvdSBjYW4gYXQgbGVhc3QgZmlndXJlIG91dCB3aGF0IHlvdSBk
aWQgZ2V0IGFuZCBpbnRlcnByZXQgaXQpLg0KSSBkb250IGtub3cgaG93IG9uZSB3b2h1ZCByZXNv
bHZlIHRoZSByYWNlIGV2ZW4gd2l0aGluIHRoZSBzZW5kaW5nIGFwcGxpY2F0aW9uIC0tIG9uZSB0
aHJlYWQgc2VuZHMsIGFub3RoZXIgdGhyZWFkIHNlbmRzIHdoaWxlIHRoZSBmaXJzdCBzYXlzIHRv
IGZvcmdldCBhYm91dCBzdHVmZi4gSSBkb250IGtub3cgd2hhdCBvZmZzZXQgc3R1ZmYgZW5kcyB1
cCBhdCBpbiBzdWNoIGNhc2VzLCBhbmQgc28gSSBjYW5ub3QgZnJhbWUgZGF0YSBpbiBhIHdheSB0
aGF0IGlzIG5vbi1zeW5jaHJvbm91cy4gVGhhdCBkZWZlYXRzIHNvbWUgb2YgdGhlIG1haW4gcmVh
c29ucyB0byBkbyBwYXJ0aWFsIHJlbGlhYmlsaXR5IChpLmUuIHRvIHJlZHVjZSBqaXR0ZXIpLg0K
RHJhZnQgMDIgc2VlbWVkIHRvIGJlIGdvaW5nIGluIGEgYmV0dGVyIGRpcmVjdGlvbiB3LnIudCB0
aGUgdXNlY2FzZXMgaSBjYW4gY29uY2VpdmUgb2YuIEkgdGhpbmsgcmV3aW5kaW5nIHRvIHRoYXQg
YW5kIHRoZW4gcG90ZW50aWFsbHkgZmlndXJpbmcgb3V0IGhvdyB0byBzaW1wbGlmeSBpdCB3b3Vs
ZCBiZSBmdW4hDQpJJ20gZXhjaXRlZCB0byBoYXZlIHRoaXMgYmVpbmcgZGlzY3Vzc2VkLCBzaW5j
ZSB0aGVyZSBpcyBwZW50IHVwIGRlbWFuZCB0byB1c2UgaXQgYWxyZWFkeS4NCi09Ug0KR2V0IE91
dGxvb2sgZm9yIEFuZHJvaWQ8aHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3Vy
bD91PWh0dHBzLTNBX19ha2EubXNfZ2hlaTM2JmQ9RHdNRkFnJmM9NVZEMFJUdE5sVGgzeWNkNDFi
M01VdyZyPUMwc1VvLUxGTkJhWWZ5b2FDc2Y2VEEmbT1WT1VqX01ud1dmX1BnZEh2Y0dWMVNlMW8z
azVqQzhtOG5vS0RpeHE4SHFBJnM9LXhKYl9KV09kTF9EcERNNDNFMDZTNTRMUEUteGtwWWtTZW40
RWwtd2tTNCZlPT4NCg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkZyb206IFFV
SUMgPHF1aWMtYm91bmNlc0BpZXRmLm9yZzxtYWlsdG86cXVpYy1ib3VuY2VzQGlldGYub3JnPj4g
b24gYmVoYWxmIG9mIE1hcnRpbiBUaG9tc29uIDxtYXJ0aW4udGhvbXNvbkBnbWFpbC5jb208bWFp
bHRvOm1hcnRpbi50aG9tc29uQGdtYWlsLmNvbT4+DQpTZW50OiBXZWRuZXNkYXksIE1heSAzMCwg
MjAxOCA1OjUwOjU5IFBNDQpUbzogTWlrZSBCaXNob3ANCkNjOiBRVUlDIFdHOyBMdWJhc2hldiwg
SWdvcg0KU3ViamVjdDogUmU6IFBhcnRpYWxseSBSZWxpYWJsZSBNZXNzYWdlIFN0cmVhbQ0KDQpM
aWtlIE1pa2UsIEkgZmluZCB0aGlzIGdhcCB0aGluZyBjb25mdXNpbmcuICBBbmQgTWlrZSdzIG1l
c3NhZ2UNCmhlbHBlZCwgYnV0IG5vdCBhIGxvdC4NCg0KSXQgdG9vayBhIHdoaWxlIHRvIHJlYWxp
emUgdGhhdCBmb3JjaW5nIGEgZ2FwIGNyZWF0ZXMgYSBuZXcgc3RhcnRpbmcNCnBvaW50IGZvciB0
aGUgbmV4dCBtZXNzYWdlIHRoYXQgZm9yY2VzIHRoZSByZWNpcGllbnQgdG8gcmVjb2duaXplIGFu
ZA0KZGVhbCB3aXRoLiAgSG93ZXZlciwgdGhlIGxvZ2ljIGZvciBpZGVudGlmeWluZyB0aGF0IGlz
IGp1c3QgaGFyZCBhbmQNCml0J3MgYW4gdW5uZWNlc3NhcnkgaW1wb3NpdGlvbiBpbiBteSB2aWV3
Lg0KDQpTYXkgSSBzZW5kIGEgbWVzc2FnZSB3aXRoIGEgbGVuZ3RoIG9mIDEwIGFuZCBvbmx5IHR3
byBvY3RldHMgbWFrZSBpdA0Kb250byB0aGUgd2lyZSAoYXMgd2l0aCB5b3VyIGV4YW1wbGUpLCB0
aGVuIGl0IGlzIGltbWVkaWF0ZWx5DQphYmFuZG9uZWQuICBZb3VyIHNvbHV0aW9uIHdvdWxkIGhh
dmUgdGhlIEVYUElSRURfU1RSRUFNX0RBVEEgZm9yY2UgYQ0KZ2FwIGFmdGVyIHRoZSBzZWNvbmQg
b2N0ZXQsIHNvIHRoYXQgdGhlIG5leHQgbWVzc2FnZSBjb3VsZCBzdGFydCBhdA0Kb2Zmc2V0IDMg
cmF0aGVyIHRoYW4gb2Zmc2V0IDEwLiAgVGhhdCBzYXZlcyB0aGUgcmVtYWluaW5nIDcgb2N0ZXRz
IG9mDQpmbG93IGNvbnRyb2wgY3JlZGl0LiAgKFVzZSBiaWdnZXIgbnVtYmVycyBhbmQgcGVyaGFw
cyBpdCBzZWVtcyBtb3JlDQptb3RpdmF0aW5nKS4NCg0KSWYgdGhlIG9jdGV0cyB0aGF0IGNvdmVy
IHRoZSBnYXAgd2VyZSBzZW50LCB0aGVuIHlvdSBoYXZlIGEgcHJvYmxlbQ0KYmVjYXVzZSBub3cg
eW91IGhhdmUgc2VudCB0d28gdmVyc2lvbnMgb2YgdGhlIHNhbWUgb2N0ZXRzLCBzbyB5b3UgY2Fu
DQpvbmx5IGRvIHRoaXMgaWYgdGhlIG9jdGV0cyB3ZXJlIG5ldmVyIHNlbnQuICBJdCBzdGFydHMg
dG8gZ2V0IGNsb3Nlcg0KYW5kIGNsb3NlciB0byB0aGUgcG9pbnQgd2hlcmUgYSBuZXcgc3RyZWFt
IGlzIGp1c3QgZWFzaWVyLg0KDQpXb3JzdCwgSSB0aGluayBpcyB0aGF0IHRoZSByZWNlaXZlciBo
YXMgdG8gaGF2ZSBjb21wbGljYXRlZCBsb2dpYyBmb3INCmlkZW50aWZ5aW5nIHRoYXQgYSBnYXAg
ZXhpc3RzIGFuZCBkZWFsaW5nIHdpdGggaXQuICBJdCBoYXMgdG8gcmVhZCB1cA0KdG8gd2hhdCBp
dCBoYXMsIG9ic2VydmUgdGhhdCB0aGUgZGF0YSBoYXMgZXhwaXJlZCwgdGhlbiBsZWFybiB3aGVy
ZQ0KdGhlIGdhcCBlbmRzLCB0aGVuIHJlc3luY2hyb25pemUgYmFzZWQgb24gMStnYXBfZW5kIGZv
ciB0aGUgbmV4dA0KbWVzc2FnZS4NCg0KQmV0dGVyIHRvIGVhdCB0aGUgZmxvdyBjb250cm9sIGNv
c3QgaW4gbXkgdmlldy4gIE9yIHNlbmQgUlNUX1NUUkVBTQ0KYW5kIG1ha2UgYW5vdGhlciBzdHJl
YW0uDQpPbiBUaHUsIE1heSAzMSwgMjAxOCBhdCA4OjQ4IEFNIE1pa2UgQmlzaG9wIDxtYmlzaG9w
QGV2ZXF1ZWZvdS5iZTxtYWlsdG86bWJpc2hvcEBldmVxdWVmb3UuYmU+PiB3cm90ZToNCj4NCj4g
SSBmaW5kIHRoZSBvbmUgb2N0ZXQgZ2FwIGEgYml0IGNvbmZ1c2luZywgYnV0IGFzIEkgdGhpbmsg
YWJvdXQgaXQsIEkgc2VlIHdoeSB5b3UgbmVlZCBpdC4gIElmIGFsbCB0aGUgc3RyZWFtIGRhdGEg
YXJyaXZlZCBzdWNjZXNzZnVsbHkgKGJ1dCBoYWRu4oCZdCBiZWVuIGFja25vd2xlZGdlZCB5ZXQg
ZHVlIHRvIGxvc3Mgb2YgdGhlIEFDSywgZGVsYXksIGV0Yy4pIGFuZCB0aGUgRVhQSVJFRF9TVFJF
QU1fREFUQSBnZXRzIGxvc3QsIHRoZSByZWNlaXZlciBjYW4gb25seSByZXRyb2FjdGl2ZWx5IHJl
YWxpemUgdGhlcmUgd2FzIGEganVtcC4gIEhhdmluZyBhbiBvY3RldCB0aGF0IGlzIG5ldmVyIHRy
YW5zbWl0dGVkIGVuc3VyZXMgdGhlIHJlY2VpdmVyIGFjdHVhbGx5IHNlZXMgYSBnYXAsIHdoaWNo
IG1lYW5zIHRoYXQgYW4gaW4tb3JkZXIgQVBJIHdpbGwgbm90IHByb2NlZWQgdW50aWwgaXQgaGFz
IHJlY2VpdmVkIGVpdGhlciB0aGUgbWlzc2luZyBvY3RldCBvciBhbiBFWFBJUkVEX1NUUkVBTV9E
QVRBIGluZm9ybWluZyBpdCB0aGUgb2N0ZXQgd2lsbCBuZXZlciBhcnJpdmUuDQo+DQo+DQo+DQo+
IFRoaXMgc2ltcGxpZmljYXRpb24gKHZlcnN1cyAtMDIpIGNvbWVzIGF0IGEgcHJpY2U6ICBJZiBh
biBBUEkgd2VyZSBleHBvc2luZyBzdHJlYW0gZGF0YSBvdXQtb2Ytb3JkZXIsIHRoZW4gaW4geW91
ciBleGFtcGxlLCB0aGUgcmVjZWl2ZXIga25vd3MgdGhhdCBhIG1lc3NhZ2UgYWx3YXlzIGJlZ2lu
cyBvbiBhIHRlbi1ieXRlIGJvdW5kYXJ5LiAgQSByZWNlaXZlciBjYW4gbm8gbG9uZ2VyIGZpbmQg
dGVuLWJ5dGUgYm91bmRhcmllcywgYmVjYXVzZSB0aGUgb2Zmc2V0IG9uIHRoZSByZWFkIHNpZGUg
ZG9lc27igJl0IG1hdGNoIHRoZSBvZmZzZXQgb24gdGhlIHNlbmQgc2lkZS4gIEkgYWdyZWUgd2l0
aCB5b3UgdGhhdCB0aGlzIHNlZW1zIGxpa2UgYSByZWFzb25hYmxlIHRyYWRlLW9mZiBmb3IgdGhl
IHNpbXBsZXIgZmxvdyBjb250cm9sLg0KPg0KPg0KPg0KPiBPbmUgY29uZmxpY3QgSSBzZWUgaW4g
dGhlIGRvYzoNCj4NCj4gwrcgICAgICAgICBTZWN0aW9uIDMgc2F5czogIFJlY2VpcHQgb2YgYW4g
RVhQSVJFRF9TVFJFQU1fREFUQSBkb2VzIG5vdCBhZHZhbmNlIHRoZSBsYXJnZXN0IHJlY2VpdmVk
IG9mZnNldCBmb3IgdGhlIHN0cmVhbS4NCj4NCj4gU2VjdGlvbiA1IHNheXM6ICBBIHJlY2VpdmVy
IFNIT1VMRCBkaXNjYXJkIGFueSBzdHJlYW0gZGF0YSByZWNlaXZlZCBmb3IgYW4gb2Zmc2V0IHNt
YWxsZXIgdGhhbiB0aGUgbmV3IHNtYWxsZXN0IHJlY2VpdmUgb2Zmc2V0LCBwb3NzaWJseSBhZHZh
bmNpbmcgdGhlIGxhcmdlc3QgcmVjZWl2ZWQgb2Zmc2V0IGZvciB0aGUgc3RyZWFtLg0KPg0KPg0K
Pg0KPiBPdGhlciBtaW5vciBuaXRzIGFyZSBiZXR0ZXIgZG9uZSB2aWEgUFIuDQo+DQo+IEZyb206
IFFVSUMgPHF1aWMtYm91bmNlc0BpZXRmLm9yZzxtYWlsdG86cXVpYy1ib3VuY2VzQGlldGYub3Jn
Pj4gT24gQmVoYWxmIE9mIEx1YmFzaGV2LCBJZ29yDQo+IFNlbnQ6IFdlZG5lc2RheSwgTWF5IDMw
LCAyMDE4IDk6NDUgQU0NCj4gVG86IFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc8bWFpbHRvOnF1aWNA
aWV0Zi5vcmc+Pg0KPiBTdWJqZWN0OiBQYXJ0aWFsbHkgUmVsaWFibGUgTWVzc2FnZSBTdHJlYW0N
Cj4NCj4NCj4NCj4gSeKAmXZlIGp1c3QgdXBsb2FkZWQgYSBuZXcgZHJhZnQgZm9yIHBhcnRpYWxs
eSByZWxpYWJsZSBRVUlDIHN0cmVhbXMuICBOb3RlOiB0aGlzIGZlYXR1cmUgaXMgbGlrZWx5IG5v
dCBpbiBzY29wZSBmb3IgVjEsIGJ1dCBpdCBjYW4gYmUgYW4gZXh0ZW5zaW9uIGZvciBWMSBhbmQv
b3IgYSBwYXJ0IG9mIFYyLg0KPg0KPg0KPg0KPiBUaGUgbmV3IHZlcnNpb24gMDMgKGh0dHBzOi8v
dXJsZGVmZW5zZS4ucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cHMtM0FfX3Rvb2xzLmlldGYu
b3JnX2h0bWxfZHJhZnQtMkRsdWJhc2hldi0yRHF1aWMtMkRwYXJ0aWFsLTJEcmVsaWFiaWxpdHkt
MkQwMyZkPUR3SUZhUSZjPTVWRDBSVHRObFRoM3ljZDQxYjNNVXcmcj1DMHNVby1MRk5CYVlmeW9h
Q3NmNlRBJm09eXlScGJlMTRrVFlnWTQxM2dqVmtPYWxXRV9VQzN4WWVyS3BKcVM4SGlRbyZzPVha
Mjk1eGlac04xMXlQOEdMY2RNczFqZjd6MGIyX1doaUl4TUxMb3JaWG8mZT08aHR0cHM6Ly91cmxk
ZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3VybD91PWh0dHBzLTNBX190b29scy5pZXRmLm9yZ19o
dG1sX2RyYWZ0LTJEbHViYXNoZXYtMkRxdWljLTJEcGFydGlhbC0yRHJlbGlhYmlsaXR5LTJEMDMm
ZD1Ed0lGYVEmYz01VkQwUlR0TmxUaDN5Y2Q0MWIzTVV3JnI9QzBzVW8tTEZOQmFZZnlvYUNzZjZU
QSZtPXl5UnBiZTE0a1RZZ1k0MTNnalZrT2FsV0VfVUMzeFllcktwSnFTOEhpUW8mcz1YWjI5NXhp
WnNOMTF5UDhHTGNkTXMxamY3ejBiMl9XaGlJeE1MTG9yWlhvJmU9Pikgbm8gbG9uZ2VyIG5lZWRz
IGNvbXBsZXggZmxvdyBjb250cm9sIGNoYW5nZXMgYW5kIHJlbW92ZXMgdGhlIG5lZWQgdG8gdHJh
bnNtaXQgbXVsdGlwbGUgZnJhbWVzIGluIHRoZSBzYW1lIHBhY2tldC4NCj4NCj4NCj4NCj4gSWdv
cg0KPg0KPg0KPg0KPiBQLlMuDQo+DQo+ICAgVGhlcmUgaXMgYWxzbyBhIG5ldyB2ZXJzaW9uIDAy
LCB3aGljaCBpbmNsdWRlcyBhIG1vcmUgY29tcGxleCBhbGdvcml0aG0gd2l0aCBtb3JlIGZlYXR1
cmVzIGFuZCBkaWZmZXJlbnQgdHJhZGUtb2Zmcy4gIEJ1dCBJIHRoaW5rIHZlcnNpb24gMDMgaXMg
YSBiZXR0ZXIgbWF0Y2ggZm9yIHRoZSBuZWVkcyBzbyBmYXIuDQoNCg==

--_000_373707b557534c0e8a5fffcabf3cb2cfustx2exdag1mb6msgcorpak_
Content-Type: text/html; charset="utf-8"
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPCEtLVtp
ZiAhbXNvXT48c3R5bGU+dlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPjwh
W2VuZGlmXS0tPjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0xOjIgNCA1IDMgNSA0IDYg
MyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0KCXBhbm9zZS0xOjIg
MTUgNSAyIDIgMiA0IDMgMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25zICovDQpwLk1zb05vcm1h
bCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowaW47DQoJbWFyZ2luLWJv
dHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmki
LHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJp
b3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCmE6
dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5bGUtcHJpb3JpdHk6
OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KcC5tc29u
b3JtYWwwLCBsaS5tc29ub3JtYWwwLCBkaXYubXNvbm9ybWFsMA0KCXttc28tc3R5bGUtbmFtZTpt
c29ub3JtYWw7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBpbjsN
Cgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowaW47DQoJZm9udC1z
aXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpzcGFuLkVt
YWlsU3R5bGUxOA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbDsNCglmb250LWZhbWlseToiQ2Fs
aWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCnNwYW4uRW1haWxTdHlsZTE5
DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLWNvbXBvc2U7DQoJZm9udC1mYW1pbHk6IkNhbGli
cmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVmYXVsdA0KCXtt
c28tc3R5bGUtdHlwZTpleHBvcnQtb25seTt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4
LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3Jk
U2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBt
c28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYi
IC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBl
bGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0K
PC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0i
RU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rp
b24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoYW5rcywgSmFuYS48bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+U3RyZWFtIEdyb3VwcyBpcyBhbiBpbnRlcmVzdGluZyBpZGVhIHRoYXQgd291bGQg
bmVlZCB0byBiZSBmbHVzaGVkIG91dCBmdXJ0aGVyIHRvIHNlZSB3aGVyZSBpdCBsZWFkcyB1cy4m
bmJzcDsgSSB3YXMgdHJ5aW5nIHRvIG1pbmltaXplIHRoZSBjaGFuZ2VzIHRvIFFVSUMgYW5kIGxp
bWl0aW5nIHRoZSBkZXNpZ24gdG8gYXBwbGljYXRpb25zIHRoYXQgd2FudCBpbi1vcmRlciBtZXNz
YWdlIGRlbGl2ZXJ5IGJ1dCBwcmVmZXINCiB0byBkcm9wIG9sZCBtZXNzYWdlcyBpbiBmYXZvciBv
ZiBhIG1vcmUgdGltZWx5IHJlY2VpcHQgb2YgbmV3ZXIgbWVzc2FnZXMuJm5ic3A7IEkuZS4gdGhp
bmdzIGxpa2UgcmVhbC10aW1lIGF1ZGlvL3ZpZGVvLCBwZXItY2hhcmFjdGVyIGdhbWUgc3RhdGUg
dXBkYXRlcywgdGVsZW1ldHJ5IHVwZGF0ZXMuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjE8c3Vw
PnN0PC9zdXA+IENsYXNzIE1lc3NhZ2VzIGNvdWxkIGFjY29tcGxpc2ggbW9yZSwgYnV0LCBhcyB5
b3Ugc2FpZCwgeW914oCZZCBuZWVkIHRvIGRlc2lnbiBmbG93IGNvbnRyb2wgZm9yIHRoZXNlLiZu
YnNwOyBBbmQgdGhhdCB3YXMgdGhlIGhhcmRlc3QgcGFydCwgYXMgSSBkaXNjb3ZlcmVkITxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj4oSW4gZmFjdCwgdmVyc2lvbiAwMyBmbG93IGNvbnRyb2wgYWNj
b3VudGluZyBpcyB3cm9uZywgYXMgSSB0aGluayBhYm91dCBpdC4mbmJzcDsgSW5zdGVhZCBvZiDi
gJxSZWNlaXB0IG9mIGFuIEVYUElSRURfU1RSRUFNX0RBVEENCjxiPmRvZXMgbm90IGFkdmFuY2Ug
dGhlIGxhcmdlc3QgcmVjZWl2ZWQgb2Zmc2V0IGZvciB0aGUgc3RyZWFtPC9iPi7igJ0sIGl0IHNo
b3VsZCBzYXkg4oCcSWYgdGhlIGxhcmdlc3QgcmVjZWl2ZWQgb2Zmc2V0IGlzIHNtYWxsZXIgdGhh
biBNaW5pbXVtIFN0cmVhbSBPZmZzZXQgZm9yIHRoZSBzdHJlYW0sDQo8Yj5pdCBpcyBhZHZhbmNl
ZCB0byBNaW5pbXVtIFN0cmVhbSBPZmZzZXQgbWludXMgMTwvYj4u4oCdJm5ic3A7IFRoaXMgd2ls
bCBjYXRjaCBhIHJvZ3VlIHNlbmRlciB2aW9sYXRpbmcgZmxvdyBjb250cm9sIGJ5IHNlbmRpbmcg
YSBodWdlIE1pbmltdW0gU3RyZWFtIE9mZnNldCwgaW4gYW4gYXR0ZW1wdCB0byBnZXQgdGhlIHJl
Y2VpdmVyIHRvIGluY3JlYXNlIGl0cyBTVFJFQU1fTUFYX0RBVEEgdG8g4oCcTWluaW11bSBTdHJl
YW0gT2Zmc2V04oCdICYjNDM7IHN0cmVhbV9idWZmZXJfc2l6ZQ0KIGFuZCB0aGVuIHRvIGVmZmVj
dCBhIGNvcnJlc3BvbmRpbmcgaHVnZSBpbmNyZWFzZSBpbiBNQVhfREFUQS4mbmJzcDsgVGhhdCB3
b3VsZCBhbGxvdyB0aGUgc2VuZGVyIHRvIHNlbmQgZGF0YSBvbiBvdGhlciBzdHJlYW1zIGVmZmVj
dGl2ZWx5IHdpdGhvdXQgYSBjb25uZWN0aW9uIGZsb3cgY29udHJvbCBsaW1pdC4pPG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj5Gcm9tOjwv
Yj4gSmFuYSBJeWVuZ2FyIFttYWlsdG86anJpLmlldGZAZ21haWwuY29tXSA8YnI+DQo8Yj5TZW50
OjwvYj4gVGh1cnNkYXksIE1heSAzMSwgMjAxOCA0OjM3IFBNPGJyPg0KPGI+VG86PC9iPiBSb2Jl
cnRvIFBlb24gJmx0O2Zlbml4QGZiLmNvbSZndDs8YnI+DQo8Yj5DYzo8L2I+IE1pa2UgQmlzaG9w
ICZsdDttYmlzaG9wQGV2ZXF1ZWZvdS5iZSZndDs7IE1hcnRpbiBUaG9tc29uICZsdDttYXJ0aW4u
dGhvbXNvbkBnbWFpbC5jb20mZ3Q7OyBRVUlDIFdHICZsdDtxdWljQGlldGYub3JnJmd0OzsgTHVi
YXNoZXYsIElnb3IgJmx0O2lsdWJhc2hlQGFrYW1haS5jb20mZ3Q7PGJyPg0KPGI+U3ViamVjdDo8
L2I+IFJlOiBQYXJ0aWFsbHkgUmVsaWFibGUgTWVzc2FnZSBTdHJlYW08bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPkknbSBub3Qga2VlbiB0byBnZXQgaW50byB0aGUgd2VlZHMgb2YgdGhp
cyBkaXNjdXNzaW9uIGF0IHRoaXMgdGltZSAoYXMgeW91IHNheSwgaXQncyBmb3IgdjIpLCBidXQg
SSB1bmRlcnN0YW5kIHRoZSBvdmVyYWxsIGRlc2lnbi4gQSBmZXcgaGlnaGVyLW9yZGVyIHBvaW50
cyB3aXRoIHRoaXMgZGVzaWduIGRpcmVjdGlvbjo8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjEuIFRoZXJlJ3MgY2xlYXIgZGVtYXJjYXRpb24gb2YgYXBwIG1l
c3NhZ2VzLCBidXQgdGhleSBhcmVuJ3QgcmVhbGx5IG1hZGUgZmlyc3QgY2xhc3MgY2l0aXplbnMu
IElmIHlvdSBkaWQgdGhhdCwgSSBpbWFnaW5lIHRoYXQgeW91IG1pZ2h0IGhhdmUgYSBzaW1wbGVy
IGRlc2lnbi4gRm9yIGluc3RhbmNlLCBkZWZpbmUgYSBNU0dfU1RSRUFNIGZyYW1lLCB3aGljaCBz
dXBwb3J0cyBtZXNzYWdlIHN0cmVhbXMgKGluc3RlYWQNCiBvZiB0aGUgY3VycmVudCBieXRlIHN0
cmVhbXMpLCBhbmQgdGhlbiB5b3UgY2FuIGNhbmNlbCBtZXNzYWdlcyBlYXNpbHkgd2l0aG91dCBo
YXZpbmcgdG8gZG8gc3RyZWFtIG9mZnNldCBzaGVuYW5pZ2Fucy48bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Mi4gWW91ciBkZXNpZ24gaGFzIGV4
YWN0bHkgb25lIG9yZGVyaW5nIGNhcGFiaWxpdHksIHdoaWNoIGlzIGxpbWl0aW5nLiBHZW5lcmFs
bHksIGFwcHMgdGhhdCBjYW4gZHJvcCBtZXNzYWdlcyBhbmQgcmVhZCBzdWJzZXF1ZW50IG9uZXMg
YXJlIGFsc28gY2FwYWJsZSBvZiBoYW5kbGluZyBtZXNzYWdlcyBvdXQgb2Ygc2VxdWVuY2UuIFlv
dSdsbCB3YW50IHRvIHN1cHBvcnQgcGFydGlhbCBvcmRlcmluZyBhcyB3ZWxsDQogYW5kIG5vdCBj
b25zdHJhaW4gbWVzc2FnZXMgdG8gYmUgb25seSBkZWxpdmVyZWQgaW4gc3RyaWN0bHkgbGluZWFy
IG9yZGVyLiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj4zLiBJJ20ga2VlbiB0byBzZWUgd2hhdCB3ZSBjYW4gZG8gd2l0aCB1c2luZyBz
dHJlYW1zIGFzIG1lc3NhZ2VzLiBXZSBkb24ndCBuZWVkIHRvIHB1bnQgZXZlcnl0aGluZyB0byB0
aGUgYXBwIChhcyB5b3VyIHRleHQgc3VnZ2VzdHMpLCBidXQgd2UgY2FuIHN0YXJ0IHdpdGggYSBn
cm91cGluZyBvZiBzdHJlYW1zIChvciBtZXNzYWdlcykgYW5kIGJ1aWxkaW5nIGZsb3cgY29udHJv
bCBtZWNoYW5pc21zIGZvciB0aGVzZQ0KIGdyb3Vwcy4gSSBzdXNwZWN0IHRoaXMgbWlnaHQgYmUg
Y2xlYW5lciwgYW5kIGl0IGdpdmVzIHlvdSBmbGV4aWJpbGl0eSB0byBjb25zaWRlciB2YXJpb3Vz
IG9yZGVyaW5ncyBvZiBtZXNzYWdlcy4gV2hlbiB3ZSdyZSBjbG9zZXIgdG8gdjIsIEknbSBoYXBw
eSB0byBzcGluIHVwIGEgZHJhZnQgZXhwbG9yaW5nIHRoaXMgZGlyZWN0aW9uLjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBUaHUsIE1heSAz
MSwgMjAxOCBhdCA4OjIxIEFNLCBSb2JlcnRvIFBlb24gJmx0OzxhIGhyZWY9Im1haWx0bzpmZW5p
eEBmYi5jb20iIHRhcmdldD0iX2JsYW5rIj5mZW5peEBmYi5jb208L2E+Jmd0OyB3cm90ZTo8bzpw
PjwvbzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpz
b2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6
NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPlllcy4gWW91IG1heSB3YW50IGEgc2luZ2xlIHJlc291cmNlIGZvciBhbiBvdXRwdXQgd2hp
Y2ggeW91IG1heSBiZSBnZW5lcmF0aW5nIGluIHBhcmFsbGVsLiBFdmVuIGlmIGEgc2luZ2xlIHRo
cmVhZCAnb3ducycgdGhlIHN0cmVhbSwgeW91J3ZlIGxvc3QgdGhlIGFiaWxpdHkgdG8gY29vcmRp
bmF0ZSB0aGUgZGF0YSBpdCByZWNpZXZlcyBieSBtb25vdG9uaWNhbGx5IGluY3JlYXNpbmcgb2Zm
c2V0LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5SZW51bWJlcmluZyB0aGUgb2Zmc2V0cyBicmVha3MgdGhlIGZpbGUtbGlrZSBhYnN0cmFjdGlv
biB3ZSd2ZSBlZmZlY3RpdmVseSB1c2VkIGZvciBodHRwLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi09UjxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2IGlkPSJtXy02ODE1MzU4OTU1MTA2ODAxNWNvbXBvc2VyX3NpZ25hdHVy
ZSI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTo5
LjVwdDtjb2xvcjojNTc1NzU3Ij5TZW50IHZpYSB0aGUgU2Ftc3VuZyBHYWxheHkgUzcsIGFuIEFU
JmFtcDtUIDRHIExURSBzbWFydHBob25lPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+LS0tLS0tLS0gT3JpZ2luYWwg
bWVzc2FnZSAtLS0tLS0tLTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+RnJvbTogTWlrZSBCaXNob3AgJmx0OzxhIGhyZWY9Im1haWx0bzptYmlzaG9w
QGV2ZXF1ZWZvdS5iZSIgdGFyZ2V0PSJfYmxhbmsiPm1iaXNob3BAZXZlcXVlZm91LmJlPC9hPiZn
dDsNCjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
RGF0ZTogNS8zMC8xOCA4OjMzIFBNIChHTVQtMDg6MDApIDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VG86IFJvYmVydG8gUGVvbiAmbHQ7PGEgaHJl
Zj0ibWFpbHRvOmZlbml4QGZiLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmZlbml4QGZiLmNvbTwvYT4m
Z3Q7LCBNYXJ0aW4gVGhvbXNvbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1hcnRpbi50aG9tc29uQGdt
YWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPm1hcnRpbi50aG9tc29uQGdtYWlsLmNvbTwvYT4mZ3Q7
DQo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkNj
OiBRVUlDIFdHICZsdDs8YSBocmVmPSJtYWlsdG86cXVpY0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxh
bmsiPnF1aWNAaWV0Zi5vcmc8L2E+Jmd0OywgJnF1b3Q7THViYXNoZXYsIElnb3ImcXVvdDsgJmx0
O2lsdWJhc2hlPTxhIGhyZWY9Im1haWx0bzo0MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmciIHRh
cmdldD0iX2JsYW5rIj40MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmc8L2E+Jmd0Ow0KPG86cD48
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5TdWJqZWN0OiBS
RTogUGFydGlhbGx5IFJlbGlhYmxlIE1lc3NhZ2UgU3RyZWFtIDxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5KdXN0IHRvIGJlIGNs
ZWFy4oCmLiZuYnNwOyBZb3XigJlyZSBzdWdnZXN0aW5nIG11bHRpcGxlIHRocmVhZHMgdGhhdCB3
b3VsZCBiZSB3cml0aW5nIHRvIGEgc2luZ2xlIHN0cmVhbSBpbiBwYXJhbGxlbCwgcmF0aGVyIHRo
YW4gYSBzaW5nbGUgdGhyZWFkIOKAnG93bmluZ+KAnSB0aGUgc3RyZWFtPzxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8
ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFk
ZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxiPkZyb206
PC9iPiBSb2JlcnRvIFBlb24gJmx0OzxhIGhyZWY9Im1haWx0bzpmZW5peEBmYi5jb20iIHRhcmdl
dD0iX2JsYW5rIj5mZW5peEBmYi5jb208L2E+Jmd0Ow0KPGJyPg0KPGI+U2VudDo8L2I+IFdlZG5l
c2RheSwgTWF5IDMwLCAyMDE4IDY6MDMgUE08YnI+DQo8Yj5Ubzo8L2I+IE1pa2UgQmlzaG9wICZs
dDs8YSBocmVmPSJtYWlsdG86bWJpc2hvcEBldmVxdWVmb3UuYmUiIHRhcmdldD0iX2JsYW5rIj5t
YmlzaG9wQGV2ZXF1ZWZvdS5iZTwvYT4mZ3Q7OyBNYXJ0aW4gVGhvbXNvbiAmbHQ7PGEgaHJlZj0i
bWFpbHRvOm1hcnRpbi50aG9tc29uQGdtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPm1hcnRpbi50
aG9tc29uQGdtYWlsLmNvbTwvYT4mZ3Q7PGJyPg0KPGI+Q2M6PC9iPiBRVUlDIFdHICZsdDs8YSBo
cmVmPSJtYWlsdG86cXVpY0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPnF1aWNAaWV0Zi5vcmc8
L2E+Jmd0OzsgTHViYXNoZXYsIElnb3IgJmx0O2lsdWJhc2hlPTxhIGhyZWY9Im1haWx0bzo0MGFr
YW1haS5jb21AZG1hcmMuaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj40MGFrYW1haS5jb21AZG1h
cmMuaWV0Zi5vcmc8L2E+Jmd0Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogUGFydGlhbGx5IFJl
bGlhYmxlIE1lc3NhZ2UgU3RyZWFtPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21hcmdp
bi1ib3R0b206MTIuMHB0Ij48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVv
dDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+SSBmaW5kIGl0IGNvbmZ1c2luZyBhcyB3ZWxsLi4m
bmJzcDsgSSBmYXIgcHJlZmVyIGtlZXBpbmcgdGhlIG9mZnNldHMgbW9ub3RvbmljYWxseSBpbmNy
ZWFzaW5nIGFzIGl0IGFsbG93cyBmb3IgcmVhbC13b3JsZCB1c2Ugb2YgYQ0KIHBhcnRpYWxseSBy
ZWxpYWJsZSBzdHJlYW0gKHdoZXJlIHlvdSBtYXkgbm90IHJlY2lldmUgdGhhdCBkYXRhIGJ1dCB5
b3UgY2FuIGF0IGxlYXN0IGZpZ3VyZSBvdXQgd2hhdCB5b3UgZGlkIGdldCBhbmQgaW50ZXJwcmV0
IGl0KS48L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttYXJn
aW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1
b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPkkgZG9udCBrbm93IGhvdyBvbmUgd29odWQgcmVz
b2x2ZSB0aGUgcmFjZSBldmVuIHdpdGhpbiB0aGUgc2VuZGluZyBhcHBsaWNhdGlvbiAtLSBvbmUg
dGhyZWFkIHNlbmRzLCBhbm90aGVyIHRocmVhZCBzZW5kcyB3aGlsZQ0KIHRoZSBmaXJzdCBzYXlz
IHRvIGZvcmdldCBhYm91dCBzdHVmZi4gSSBkb250IGtub3cgd2hhdCBvZmZzZXQgc3R1ZmYgZW5k
cyB1cCBhdCBpbiBzdWNoIGNhc2VzLCBhbmQgc28gSSBjYW5ub3QgZnJhbWUgZGF0YSBpbiBhIHdh
eSB0aGF0IGlzIG5vbi1zeW5jaHJvbm91cy4gVGhhdCBkZWZlYXRzIHNvbWUgb2YgdGhlIG1haW4g
cmVhc29ucyB0byBkbyBwYXJ0aWFsIHJlbGlhYmlsaXR5IChpLmUuIHRvIHJlZHVjZSBqaXR0ZXIp
Ljwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttYXJnaW4tYm90dG9tOjEyLjBwdCI+
PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29s
b3I6YmxhY2siPkRyYWZ0IDAyIHNlZW1lZCB0byBiZSBnb2luZyBpbiBhIGJldHRlciBkaXJlY3Rp
b24gdy5yLnQgdGhlIHVzZWNhc2VzIGkgY2FuIGNvbmNlaXZlIG9mLiBJIHRoaW5rIHJld2luZGlu
ZyB0byB0aGF0IGFuZCB0aGVuIHBvdGVudGlhbGx5DQogZmlndXJpbmcgb3V0IGhvdyB0byBzaW1w
bGlmeSBpdCB3b3VsZCBiZSBmdW4hPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7
QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpibGFjayI+SSdtIGV4Y2l0ZWQgdG8gaGF2ZSB0
aGlzIGJlaW5nIGRpc2N1c3NlZCwgc2luY2UgdGhlcmUgaXMgcGVudCB1cCBkZW1hbmQgdG8gdXNl
IGl0IGFscmVhZHkuPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21hcmdpbi1ib3R0
b206MTIuMHB0Ij48c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fu
cy1zZXJpZjtjb2xvcjpibGFjayI+LT1SPC9zcGFuPjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+PHNwYW4gc3R5bGU9ImZvbnQtZmFt
aWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPkdldA0KPGEgaHJl
Zj0iaHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3VybD91PWh0dHBzLTNBX19h
a2EubXNfZ2hlaTM2JmFtcDtkPUR3TUZBZyZhbXA7Yz01VkQwUlR0TmxUaDN5Y2Q0MWIzTVV3JmFt
cDtyPUMwc1VvLUxGTkJhWWZ5b2FDc2Y2VEEmYW1wO209Vk9Val9NbndXZl9QZ2RIdmNHVjFTZTFv
M2s1akM4bThub0tEaXhxOEhxQSZhbXA7cz0teEpiX0pXT2RMX0RwRE00M0UwNlM1NExQRS14a3BZ
a1NlbjRFbC13a1M0JmFtcDtlPSIgdGFyZ2V0PSJfYmxhbmsiPg0KT3V0bG9vayBmb3IgQW5kcm9p
ZDwvYT48L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+PHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7
Y29sb3I6YmxhY2siPiZuYnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdiBj
bGFzcz0iTXNvTm9ybWFsIiBhbGlnbj0iY2VudGVyIiBzdHlsZT0idGV4dC1hbGlnbjpjZW50ZXIi
Pg0KPGhyIHNpemU9IjIiIHdpZHRoPSI5OCUiIGFsaWduPSJjZW50ZXIiPg0KPC9kaXY+DQo8ZGl2
IGlkPSJtXy02ODE1MzU4OTU1MTA2ODAxNXhfZGl2UnBseUZ3ZE1zZyI+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPjxiPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+RnJvbTo8L3NwYW4+PC9iPjxz
cGFuIHN0eWxlPSJjb2xvcjpibGFjayI+IFFVSUMgJmx0OzxhIGhyZWY9Im1haWx0bzpxdWljLWJv
dW5jZXNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5xdWljLWJvdW5jZXNAaWV0Zi5vcmc8L2E+
Jmd0OyBvbiBiZWhhbGYgb2YgTWFydGluDQogVGhvbXNvbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1h
cnRpbi50aG9tc29uQGdtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPm1hcnRpbi50aG9tc29uQGdt
YWlsLmNvbTwvYT4mZ3Q7PGJyPg0KPGI+U2VudDo8L2I+IFdlZG5lc2RheSwgTWF5IDMwLCAyMDE4
IDU6NTA6NTkgUE08YnI+DQo8Yj5Ubzo8L2I+IE1pa2UgQmlzaG9wPGJyPg0KPGI+Q2M6PC9iPiBR
VUlDIFdHOyBMdWJhc2hldiwgSWdvcjxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogUGFydGlhbGx5
IFJlbGlhYmxlIE1lc3NhZ2UgU3RyZWFtPC9zcGFuPiA8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rp
dj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttYXJnaW4tYm90dG9t
OjEyLjBwdCI+TGlrZSBNaWtlLCBJIGZpbmQgdGhpcyBnYXAgdGhpbmcgY29uZnVzaW5nLiZuYnNw
OyBBbmQgTWlrZSdzIG1lc3NhZ2U8YnI+DQpoZWxwZWQsIGJ1dCBub3QgYSBsb3QuPGJyPg0KPGJy
Pg0KSXQgdG9vayBhIHdoaWxlIHRvIHJlYWxpemUgdGhhdCBmb3JjaW5nIGEgZ2FwIGNyZWF0ZXMg
YSBuZXcgc3RhcnRpbmc8YnI+DQpwb2ludCBmb3IgdGhlIG5leHQgbWVzc2FnZSB0aGF0IGZvcmNl
cyB0aGUgcmVjaXBpZW50IHRvIHJlY29nbml6ZSBhbmQ8YnI+DQpkZWFsIHdpdGguJm5ic3A7IEhv
d2V2ZXIsIHRoZSBsb2dpYyBmb3IgaWRlbnRpZnlpbmcgdGhhdCBpcyBqdXN0IGhhcmQgYW5kPGJy
Pg0KaXQncyBhbiB1bm5lY2Vzc2FyeSBpbXBvc2l0aW9uIGluIG15IHZpZXcuPGJyPg0KPGJyPg0K
U2F5IEkgc2VuZCBhIG1lc3NhZ2Ugd2l0aCBhIGxlbmd0aCBvZiAxMCBhbmQgb25seSB0d28gb2N0
ZXRzIG1ha2UgaXQ8YnI+DQpvbnRvIHRoZSB3aXJlIChhcyB3aXRoIHlvdXIgZXhhbXBsZSksIHRo
ZW4gaXQgaXMgaW1tZWRpYXRlbHk8YnI+DQphYmFuZG9uZWQuJm5ic3A7IFlvdXIgc29sdXRpb24g
d291bGQgaGF2ZSB0aGUgRVhQSVJFRF9TVFJFQU1fREFUQSBmb3JjZSBhPGJyPg0KZ2FwIGFmdGVy
IHRoZSBzZWNvbmQgb2N0ZXQsIHNvIHRoYXQgdGhlIG5leHQgbWVzc2FnZSBjb3VsZCBzdGFydCBh
dDxicj4NCm9mZnNldCAzIHJhdGhlciB0aGFuIG9mZnNldCAxMC4mbmJzcDsgVGhhdCBzYXZlcyB0
aGUgcmVtYWluaW5nIDcgb2N0ZXRzIG9mPGJyPg0KZmxvdyBjb250cm9sIGNyZWRpdC4mbmJzcDsg
KFVzZSBiaWdnZXIgbnVtYmVycyBhbmQgcGVyaGFwcyBpdCBzZWVtcyBtb3JlPGJyPg0KbW90aXZh
dGluZykuPGJyPg0KPGJyPg0KSWYgdGhlIG9jdGV0cyB0aGF0IGNvdmVyIHRoZSBnYXAgd2VyZSBz
ZW50LCB0aGVuIHlvdSBoYXZlIGEgcHJvYmxlbTxicj4NCmJlY2F1c2Ugbm93IHlvdSBoYXZlIHNl
bnQgdHdvIHZlcnNpb25zIG9mIHRoZSBzYW1lIG9jdGV0cywgc28geW91IGNhbjxicj4NCm9ubHkg
ZG8gdGhpcyBpZiB0aGUgb2N0ZXRzIHdlcmUgbmV2ZXIgc2VudC4mbmJzcDsgSXQgc3RhcnRzIHRv
IGdldCBjbG9zZXI8YnI+DQphbmQgY2xvc2VyIHRvIHRoZSBwb2ludCB3aGVyZSBhIG5ldyBzdHJl
YW0gaXMganVzdCBlYXNpZXIuPGJyPg0KPGJyPg0KV29yc3QsIEkgdGhpbmsgaXMgdGhhdCB0aGUg
cmVjZWl2ZXIgaGFzIHRvIGhhdmUgY29tcGxpY2F0ZWQgbG9naWMgZm9yPGJyPg0KaWRlbnRpZnlp
bmcgdGhhdCBhIGdhcCBleGlzdHMgYW5kIGRlYWxpbmcgd2l0aCBpdC4mbmJzcDsgSXQgaGFzIHRv
IHJlYWQgdXA8YnI+DQp0byB3aGF0IGl0IGhhcywgb2JzZXJ2ZSB0aGF0IHRoZSBkYXRhIGhhcyBl
eHBpcmVkLCB0aGVuIGxlYXJuIHdoZXJlPGJyPg0KdGhlIGdhcCBlbmRzLCB0aGVuIHJlc3luY2hy
b25pemUgYmFzZWQgb24gMSYjNDM7Z2FwX2VuZCBmb3IgdGhlIG5leHQ8YnI+DQptZXNzYWdlLjxi
cj4NCjxicj4NCkJldHRlciB0byBlYXQgdGhlIGZsb3cgY29udHJvbCBjb3N0IGluIG15IHZpZXcu
Jm5ic3A7IE9yIHNlbmQgUlNUX1NUUkVBTTxicj4NCmFuZCBtYWtlIGFub3RoZXIgc3RyZWFtLjxi
cj4NCk9uIFRodSwgTWF5IDMxLCAyMDE4IGF0IDg6NDggQU0gTWlrZSBCaXNob3AgJmx0OzxhIGhy
ZWY9Im1haWx0bzptYmlzaG9wQGV2ZXF1ZWZvdS5iZSIgdGFyZ2V0PSJfYmxhbmsiPm1iaXNob3BA
ZXZlcXVlZm91LmJlPC9hPiZndDsgd3JvdGU6PGJyPg0KJmd0Ozxicj4NCiZndDsgSSBmaW5kIHRo
ZSBvbmUgb2N0ZXQgZ2FwIGEgYml0IGNvbmZ1c2luZywgYnV0IGFzIEkgdGhpbmsgYWJvdXQgaXQs
IEkgc2VlIHdoeSB5b3UgbmVlZCBpdC4mbmJzcDsgSWYgYWxsIHRoZSBzdHJlYW0gZGF0YSBhcnJp
dmVkIHN1Y2Nlc3NmdWxseSAoYnV0IGhhZG7igJl0IGJlZW4gYWNrbm93bGVkZ2VkIHlldCBkdWUg
dG8gbG9zcyBvZiB0aGUgQUNLLCBkZWxheSwgZXRjLikgYW5kIHRoZSBFWFBJUkVEX1NUUkVBTV9E
QVRBIGdldHMgbG9zdCwgdGhlIHJlY2VpdmVyDQogY2FuIG9ubHkgcmV0cm9hY3RpdmVseSByZWFs
aXplIHRoZXJlIHdhcyBhIGp1bXAuJm5ic3A7IEhhdmluZyBhbiBvY3RldCB0aGF0IGlzIG5ldmVy
IHRyYW5zbWl0dGVkIGVuc3VyZXMgdGhlIHJlY2VpdmVyIGFjdHVhbGx5IHNlZXMgYSBnYXAsIHdo
aWNoIG1lYW5zIHRoYXQgYW4gaW4tb3JkZXIgQVBJIHdpbGwgbm90IHByb2NlZWQgdW50aWwgaXQg
aGFzIHJlY2VpdmVkIGVpdGhlciB0aGUgbWlzc2luZyBvY3RldCBvciBhbiBFWFBJUkVEX1NUUkVB
TV9EQVRBDQogaW5mb3JtaW5nIGl0IHRoZSBvY3RldCB3aWxsIG5ldmVyIGFycml2ZS48YnI+DQom
Z3Q7PGJyPg0KJmd0Ozxicj4NCiZndDs8YnI+DQomZ3Q7IFRoaXMgc2ltcGxpZmljYXRpb24gKHZl
cnN1cyAtMDIpIGNvbWVzIGF0IGEgcHJpY2U6Jm5ic3A7IElmIGFuIEFQSSB3ZXJlIGV4cG9zaW5n
IHN0cmVhbSBkYXRhIG91dC1vZi1vcmRlciwgdGhlbiBpbiB5b3VyIGV4YW1wbGUsIHRoZSByZWNl
aXZlciBrbm93cyB0aGF0IGEgbWVzc2FnZSBhbHdheXMgYmVnaW5zIG9uIGEgdGVuLWJ5dGUgYm91
bmRhcnkuJm5ic3A7IEEgcmVjZWl2ZXIgY2FuIG5vIGxvbmdlciBmaW5kIHRlbi1ieXRlIGJvdW5k
YXJpZXMsIGJlY2F1c2UNCiB0aGUgb2Zmc2V0IG9uIHRoZSByZWFkIHNpZGUgZG9lc27igJl0IG1h
dGNoIHRoZSBvZmZzZXQgb24gdGhlIHNlbmQgc2lkZS4mbmJzcDsgSSBhZ3JlZSB3aXRoIHlvdSB0
aGF0IHRoaXMgc2VlbXMgbGlrZSBhIHJlYXNvbmFibGUgdHJhZGUtb2ZmIGZvciB0aGUgc2ltcGxl
ciBmbG93IGNvbnRyb2wuPGJyPg0KJmd0Ozxicj4NCiZndDs8YnI+DQomZ3Q7PGJyPg0KJmd0OyBP
bmUgY29uZmxpY3QgSSBzZWUgaW4gdGhlIGRvYzo8YnI+DQomZ3Q7PGJyPg0KJmd0OyDCtyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyBTZWN0aW9uIDMgc2F5
czombmJzcDsgUmVjZWlwdCBvZiBhbiBFWFBJUkVEX1NUUkVBTV9EQVRBIGRvZXMgbm90IGFkdmFu
Y2UgdGhlIGxhcmdlc3QgcmVjZWl2ZWQgb2Zmc2V0IGZvciB0aGUgc3RyZWFtLjxicj4NCiZndDs8
YnI+DQomZ3Q7IFNlY3Rpb24gNSBzYXlzOiZuYnNwOyBBIHJlY2VpdmVyIFNIT1VMRCBkaXNjYXJk
IGFueSBzdHJlYW0gZGF0YSByZWNlaXZlZCBmb3IgYW4gb2Zmc2V0IHNtYWxsZXIgdGhhbiB0aGUg
bmV3IHNtYWxsZXN0IHJlY2VpdmUgb2Zmc2V0LCBwb3NzaWJseSBhZHZhbmNpbmcgdGhlIGxhcmdl
c3QgcmVjZWl2ZWQgb2Zmc2V0IGZvciB0aGUgc3RyZWFtLjxicj4NCiZndDs8YnI+DQomZ3Q7PGJy
Pg0KJmd0Ozxicj4NCiZndDsgT3RoZXIgbWlub3Igbml0cyBhcmUgYmV0dGVyIGRvbmUgdmlhIFBS
Ljxicj4NCiZndDs8YnI+DQomZ3Q7IEZyb206IFFVSUMgJmx0OzxhIGhyZWY9Im1haWx0bzpxdWlj
LWJvdW5jZXNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5xdWljLWJvdW5jZXNAaWV0Zi5vcmc8
L2E+Jmd0OyBPbiBCZWhhbGYgT2YgTHViYXNoZXYsIElnb3I8YnI+DQomZ3Q7IFNlbnQ6IFdlZG5l
c2RheSwgTWF5IDMwLCAyMDE4IDk6NDUgQU08YnI+DQomZ3Q7IFRvOiBRVUlDIFdHICZsdDs8YSBo
cmVmPSJtYWlsdG86cXVpY0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPnF1aWNAaWV0Zi5vcmc8
L2E+Jmd0Ozxicj4NCiZndDsgU3ViamVjdDogUGFydGlhbGx5IFJlbGlhYmxlIE1lc3NhZ2UgU3Ry
ZWFtPGJyPg0KJmd0Ozxicj4NCiZndDs8YnI+DQomZ3Q7PGJyPg0KJmd0OyBJ4oCZdmUganVzdCB1
cGxvYWRlZCBhIG5ldyBkcmFmdCBmb3IgcGFydGlhbGx5IHJlbGlhYmxlIFFVSUMgc3RyZWFtcy4m
bmJzcDsgTm90ZTogdGhpcyBmZWF0dXJlIGlzIGxpa2VseSBub3QgaW4gc2NvcGUgZm9yIFYxLCBi
dXQgaXQgY2FuIGJlIGFuIGV4dGVuc2lvbiBmb3IgVjEgYW5kL29yIGEgcGFydCBvZiBWMi48YnI+
DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCiZndDs8YnI+DQomZ3Q7IFRoZSBuZXcgdmVyc2lvbiAwMyAo
PGEgaHJlZj0iaHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3VybD91PWh0dHBz
LTNBX190b29scy5pZXRmLm9yZ19odG1sX2RyYWZ0LTJEbHViYXNoZXYtMkRxdWljLTJEcGFydGlh
bC0yRHJlbGlhYmlsaXR5LTJEMDMmYW1wO2Q9RHdJRmFRJmFtcDtjPTVWRDBSVHRObFRoM3ljZDQx
YjNNVXcmYW1wO3I9QzBzVW8tTEZOQmFZZnlvYUNzZjZUQSZhbXA7bT15eVJwYmUxNGtUWWdZNDEz
Z2pWa09hbFdFX1VDM3hZZXJLcEpxUzhIaVFvJmFtcDtzPVhaMjk1eGlac04xMXlQOEdMY2RNczFq
Zjd6MGIyX1doaUl4TUxMb3JaWG8mYW1wO2U9IiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly91cmxk
ZWZlbnNlLi5wcm9vZnBvaW50LmNvbS92Mi91cmw/dT1odHRwcy0zQV9fdG9vbHMuaWV0Zi5vcmdf
aHRtbF9kcmFmdC0yRGx1YmFzaGV2LTJEcXVpYy0yRHBhcnRpYWwtMkRyZWxpYWJpbGl0eS0yRDAz
JmFtcDtkPUR3SUZhUSZhbXA7Yz01VkQwUlR0TmxUaDN5Y2Q0MWIzTVV3JmFtcDtyPUMwc1VvLUxG
TkJhWWZ5b2FDc2Y2VEEmYW1wO209eXlScGJlMTRrVFlnWTQxM2dqVmtPYWxXRV9VQzN4WWVyS3BK
cVM4SGlRbyZhbXA7cz1YWjI5NXhpWnNOMTF5UDhHTGNkTXMxamY3ejBiMl9XaGlJeE1MTG9yWlhv
JmFtcDtlPTwvYT4pDQogbm8gbG9uZ2VyIG5lZWRzIGNvbXBsZXggZmxvdyBjb250cm9sIGNoYW5n
ZXMgYW5kIHJlbW92ZXMgdGhlIG5lZWQgdG8gdHJhbnNtaXQgbXVsdGlwbGUgZnJhbWVzIGluIHRo
ZSBzYW1lIHBhY2tldC48YnI+DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCiZndDs8YnI+DQomZ3Q7IEln
b3I8YnI+DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCiZndDs8YnI+DQomZ3Q7IFAuUy48YnI+DQomZ3Q7
PGJyPg0KJmd0OyZuYnNwOyZuYnNwOyBUaGVyZSBpcyBhbHNvIGEgbmV3IHZlcnNpb24gMDIsIHdo
aWNoIGluY2x1ZGVzIGEgbW9yZSBjb21wbGV4IGFsZ29yaXRobSB3aXRoIG1vcmUgZmVhdHVyZXMg
YW5kIGRpZmZlcmVudCB0cmFkZS1vZmZzLiZuYnNwOyBCdXQgSSB0aGluayB2ZXJzaW9uIDAzIGlz
IGEgYmV0dGVyIG1hdGNoIGZvciB0aGUgbmVlZHMgc28gZmFyLjxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3Rl
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_373707b557534c0e8a5fffcabf3cb2cfustx2exdag1mb6msgcorpak_--


From nobody Thu May 31 17:20:19 2018
Return-Path: <prvs=9690e85923=fenix@fb.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AF3971205F0 for <quic@ietfa.amsl.com>; Thu, 31 May 2018 17:20:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.719
X-Spam-Level: 
X-Spam-Status: No, score=-2.719 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, T_DKIMWL_WL_HIGH=-0.01, T_DKIMWL_WL_MED=-0.01, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=YoU4goDw; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=OZn/WhYE
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 oZ3AdRM6ilZ2 for <quic@ietfa.amsl.com>; Thu, 31 May 2018 17:20:10 -0700 (PDT)
Received: from mx0a-00082601.pphosted.com (mx0a-00082601.pphosted.com [67.231.145.42]) (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 8E9FB1205D3 for <quic@ietf.org>; Thu, 31 May 2018 17:20:10 -0700 (PDT)
Received: from pps.filterd (m0109333.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.16.0.22/8.16.0.22) with SMTP id w510JIA2016531; Thu, 31 May 2018 17:20:06 -0700
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=facebook; bh=/sX0wtvFvUdiZEL7vN2T1EwqDgM4ZhpOZ4OPOeL8SNE=; b=YoU4goDwq1jxmNMWFy5RUbpvX35l/rxXNmOn0qrdqzpVwydGBIRV/82IEEilStNIBeTj ubXUX/mLhICSszeJsfSlidetP0eAxqZmUl3mKzpfI+Ehg50r1Er7yR3VA3oB+RoKOlkr pC42Nl86ivA7IIJhLl+58aRR1xpad0WAips= 
Received: from maileast.thefacebook.com ([199.201.65.23]) by mx0a-00082601.pphosted.com with ESMTP id 2jath7r4ep-1 (version=TLSv1 cipher=ECDHE-RSA-AES256-SHA bits=256 verify=NOT); Thu, 31 May 2018 17:20:05 -0700
Received: from NAM02-SN1-obe.outbound.protection.outlook.com (192.168.183.28) by o365-in.thefacebook.com (192.168.177.23) with Microsoft SMTP Server (TLS) id 14.3.361.1; Thu, 31 May 2018 20:20:03 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector1-fb-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=/sX0wtvFvUdiZEL7vN2T1EwqDgM4ZhpOZ4OPOeL8SNE=; b=OZn/WhYEWm77ubo0oseJbtyOpHu9c/pqoin5/tnDaOR1CJNu40QZf7+qJLd8EUCcHmLbXTSFTUyPvwiT8Psx8oU3jwOR2gne67qeyI5UWDy9d1D9w8LBvgC1G6epUrY3e1FK12dV73vi8geEIWPXW5g8DU5ArrkUPRbVVk+ZEns=
Received: from BYAPR15MB2312.namprd15.prod.outlook.com (52.135.197.146) by BYAPR15MB2230.namprd15.prod.outlook.com (52.135.196.157) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.820.11; Fri, 1 Jun 2018 00:20:02 +0000
Received: from BYAPR15MB2312.namprd15.prod.outlook.com ([fe80::949a:9cbd:277c:96e0]) by BYAPR15MB2312.namprd15.prod.outlook.com ([fe80::949a:9cbd:277c:96e0%4]) with mapi id 15.20.0797.020; Fri, 1 Jun 2018 00:20:02 +0000
From: Roberto Peon <fenix@fb.com>
To: "Lubashev, Igor" <ilubashe=40akamai.com@dmarc.ietf.org>, Mike Bishop <mbishop@evequefou.be>, Martin Thomson <martin.thomson@gmail.com>
CC: QUIC WG <quic@ietf.org>
Subject: Re: Partially Reliable Message Stream
Thread-Topic: Partially Reliable Message Stream
Thread-Index: AdP4Mo3KTicRHsMuS7e4Jrowbk1vdQAMuR2gAAT/n4AAAG2XyQAFL0wgABjGQgcAEVOjgP//lp6A
Date: Fri, 1 Jun 2018 00:20:02 +0000
Message-ID: <9EFC5C84-5ABE-406A-A74C-7A9312EF56CF@fb.com>
References: <d263c36bc5264842a65f04fc3b017538@ustx2ex-dag1mb6.msg.corp.akamai.com> <SN1PR08MB18541BF8B27EA5484FA6A437DA6C0@SN1PR08MB1854.namprd08.prod.outlook.com> <CABkgnnWUpaFvz3d0SJJ99JkhdQfwdaxYosKwj3dK9BVZUtZ_yw@mail.gmail.com> <BYAPR15MB2312A20C0FFF67119059D2B3CD630@BYAPR15MB2312.namprd15.prod.outlook.com> <SN1PR08MB1854EB788295504BEE169A25DA630@SN1PR08MB1854.namprd08.prod.outlook.com> <BYAPR15MB2312B11929B6DEC29AC67CA3CD630@BYAPR15MB2312.namprd15.prod.outlook.com> <4a858eb49e774c34be2b0bab965bad9c@ustx2ex-dag1mb6.msg.corp.akamai.com>
In-Reply-To: <4a858eb49e774c34be2b0bab965bad9c@ustx2ex-dag1mb6.msg.corp.akamai.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.d.1.180523
x-originating-ip: [2620:10d:c090:200::7:88c]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; BYAPR15MB2230; 7:wrZCgeIv5I6JBxvBrvbkiLmVEPQalRGrU66+nxCAdD3qDTF+xt2o1iQnD5jwpG6eFuw1bwxV26CmWrE9XuElrWepcLNalbXbcYhmnoOABLZnE+6rk4OUHqbQJd8lSSWM2vkZbaf/2pyExONzseelFeVGjso640yqbeiM6GdOCvZFFmJA5N8lihulazuHomVixpOrA80bvQpEqobLZjdIPvtaHiJQ3vx0FgOdWgqiIWTVmspoethhvkLwdS5mkAMN; 20:SmAUI4hxOTzxk+ZYmMpqYnyNjvceiOdbvPYhN37lcgW391c66jc+KICJ95zSfR97DqkT6E2bXQBBZQIjXuJSQPeGgMFqdcZSFNoJMshJTjF7MbBUGrz+Jx26MTdbVMapQ7W9ZVtt5C1m1uG5uXtl8P9JXftQJtK1gwCPdjL+qbY=
x-ms-exchange-antispam-srfa-diagnostics: SOS;
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(7020095)(4652020)(5600026)(4534165)(4627221)(201703031133081)(201702281549075)(2017052603328)(7153060)(7193020); SRVR:BYAPR15MB2230; 
x-ms-traffictypediagnostic: BYAPR15MB2230:
x-microsoft-antispam-prvs: <BYAPR15MB2230E1BC4508C2C0237ACD05CD620@BYAPR15MB2230.namprd15.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(28532068793085)(190756311086443)(10436049006162)(85827821059158)(67672495146484)(21748063052155);
x-ms-exchange-senderadcheck: 1
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(8211001083)(6040522)(2401047)(8121501046)(5005006)(10201501046)(3231254)(11241501184)(944501410)(52105095)(3002001)(93006095)(93001095)(149027)(150027)(6041310)(201703131423095)(201702281528075)(20161123555045)(201703061421075)(201703061406153)(20161123562045)(20161123564045)(20161123560045)(20161123558120)(6072148)(201708071742011)(7699016); SRVR:BYAPR15MB2230; BCL:0; PCL:0; RULEID:; SRVR:BYAPR15MB2230; 
x-forefront-prvs: 0690E5FF22
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(346002)(376002)(39380400002)(39860400002)(366004)(396003)(199004)(189003)(97736004)(2900100001)(110136005)(11346002)(476003)(3660700001)(2616005)(58126008)(36756003)(46003)(316002)(606006)(14454004)(81166006)(81156014)(93886005)(33656002)(4326008)(3480700004)(99286004)(8676002)(446003)(105586002)(5660300001)(7110500001)(25786009)(3280700002)(486006)(106356001)(8936002)(575784001)(236005)(790700001)(6116002)(2906002)(59450400001)(7736002)(6512007)(53936002)(15650500001)(6246003)(6506007)(6306002)(54896002)(83716003)(86362001)(68736007)(229853002)(45080400002)(6436002)(478600001)(6486002)(2420400007)(39060400002)(186003)(76176011)(5250100002)(102836004)(53546011)(82746002)(42262002); DIR:OUT; SFP:1102; SCL:1; SRVR:BYAPR15MB2230; H:BYAPR15MB2312.namprd15.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: fb.com does not designate permitted sender hosts)
x-microsoft-antispam-message-info: nHmqkJT314roUp+njAdpj0uJ2wPqk2R7HH8RmCOHRaKn+kXsolxXBTHJLAiH/cBRXQvjkItphJ8iDam9vu1urpYznmp7cYw4BStNVPS7I047W4ll08MPZufgBmcfrjbQEqGX85IjBJuY8v6lwpkJvxXlfdKY6ifvdONdN1Yko3mj3u/bVsXmCqJd5qhnoBwz
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: multipart/alternative; boundary="_000_9EFC5C845ABE406AA74C7A9312EF56CFfbcom_"
MIME-Version: 1.0
X-MS-Office365-Filtering-Correlation-Id: 1a2df7f8-5ff1-4550-19ff-08d5c7556adb
X-MS-Exchange-CrossTenant-Network-Message-Id: 1a2df7f8-5ff1-4550-19ff-08d5c7556adb
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Jun 2018 00:20:02.0747 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BYAPR15MB2230
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2018-05-31_13:, , signatures=0
X-Proofpoint-Spam-Reason: safe
X-FB-Internal: Safe
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/CEPR4N2v-6Dxg3nVqZL4U7KvISI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.22
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/quic>, <mailto:quic-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Jun 2018 00:20:14 -0000

--_000_9EFC5C845ABE406AA74C7A9312EF56CFfbcom_
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64

QmFja2dyb3VuZCAoYm9yaW5nIGZvciBmb2xrcyB3aG8ga25vdyBhYm91dCBpbnRlcmFjdGl2ZSB2
aWRlbyk6DQoNCkluIGEgcmVhbC10aW1lL2xvdy1qaXR0ZXIgdXNlLWNhc2UsIHRoZSBwbGF5ZXIg
bWF5IHNraXAgb3ZlciBzb21lIChvbGRlcikgcGFydCBvZiB0aGUgYml0c3RyZWFtIGluIGZhdm9y
IG9mIGRlY29kaW5nL2ludGVycHJldGluZyBtb3JlIHJlY2VudCBkYXRhLg0KV2hlbiB0aGF0IGhh
cHBlbnMsIGl0IHdpbGwgYmUgdW5pbnRlcmVzdGVkIGluIGFueSBvbGRlciBkYXRhLg0KDQpIb3cg
ZG9lcyBpdCBmaW5kIHRoZSBtb3N0IGFwcHJvcHJpYXRlIG5leHQgZGF0YT8gSXQgdHlwaWNhbGx5
IGlzIG5vdCB0aGUgZGF0YSB0aGF0IGlzIHRoZSBtb3N0IHJlY2VudOKAlGV2ZW4gZm9yIGludGVy
YWN0aXZlIOKAmHBsYXliYWNr4oCZLCB5b3Ugd2FudCBhIH4xMDBtcy0yMDBtcyBidWZmZXIgdG8g
ZGVhbCB3aXRoIG5ldHdvcmsgaml0dGVyLg0KVG8gZGVjb2RlIHRoZSB2aWRlbyBiaXRzdHJlYW0s
IHdlIG5lZWQgdG8ga25vdyB3aGVyZSB0aGUgZnJhbWVzIGFyZSBpbiBpdC4gSXQgKHRoZSBiaXN0
cmVhbSkgZG9lc27igJl0IGFsd2F5cyBoYXZlIGZyYW1pbmcgb2YgaXRzIG93bi4NCg0KSWYgdGhl
cmUgaXMgYW4g4oCYaW5kZXjigJkgc3RyZWFtIGludG8gd2hpY2ggd2UgcHV0IHRoZSBwZXItZnJh
bWUvcGVyLXRpbWUtdW5pdCBtZXRhZGF0YSBhYm91dCB0aGUgdmlkZW8gYml0c3RyZWFtICh3aGlj
aCB3ZSBwdXQgb24gYW5vdGhlciBzdHJlYW0pLCB3ZSBjYW4gY2hlYXBseSB1bmRlcnN0YW5kIHRo
ZSBmcmFtaW5nIGZvciB0aGUgYml0c3RyZWFtLg0KVGhhdCBlbmFibGVzIHRoZSBwbGF5ZXIgdG8g
c2VlayBhaGVhZCB0byB0aGUgcGFydHMgdGhhdCBpdCBjYW4gaW50ZXJwcmV0LCBhcyB0aGUgcmVh
ZGVyIG9mIHRoZSBpbmRleCBzdHJlYW0ga25vd3MgdGhhdCBpZiBpdCBoYXMgayBieXRlcyBzdGFy
dGluZyBhdCBhIHBvc2l0aW9uIHdoZXJlIG4gJSBrID09MCwgaXQgaXMgYSB2YWxpZCByZWNvcmQu
IFlvdSBjYW7igJl0IGRvIHRoYXQgb24gdGhlIGJpdHN0cmVhbSwgYXMgaXQgaGFzIHZhcmlhYmxl
IGxlbmd0aC4gWW91IGNvdWxkIOKAmGVzY2FwZeKAmSBvbiB0aGUgYml0c3RyZWFtIHRvIGVuc3Vy
ZSBhIHVuaXF1ZSBmcmFtaW5nIHRva2VuLCBidXQgdGhhdCB3b3VsZCBleHBhbmQgdGhlIHNpemUg
b2YgdGhlIGJpdHN0cmVhbSwgYW5kIGJlIGEgcGFpbiBpbiBvdGhlcnMuDQoNCllvdSBjYW4gdGhl
biBwbGF5IGV2ZW4gbW9yZSBmdW4gZ2FtZXMsIGZvciBpbnN0YW5jZSBwdXR0aW5nIHRoZSBmcmFt
aW5nIGluIGJvdGggZml4ZWQtc2l6ZSBhbmQgbm9uLWZpeGVkIHNpemUgc3RyZWFtcy4gSW4gc3Vj
aCBhIGNhc2UgeW91IGNhbiByZWNvdmVyIGZyYW1pbmcgaWYgeW91IGhhdmUgcmVjZWl2ZWQgdGhh
dCBwYXJ0IG9mIHRoZSBpbmRleCBzdHJlYW0gdGhhdCBkZXNjcmliZXMgdGhlIGJpdHN0cmVhbSB0
aGF0IHlvdSB3aXNoIHRvIGludGVycHJldCwgb3IgaWYgdGhlIGJpdHN0cmVhbSBmcmFtaW5nIGlz
IGludGFjdCBmcm9tIGFueSBwb2ludCB3aGVyZSB5b3UgdW5kZXJzdG9vZCBpdCBpbiB0aGUgcGFz
dC4NCg0KVGhlIGxhdHRlciDigJxldmVuIG1vcmUgZnVuIGdhbWVz4oCdIGlzIGEgcmVhc29uYWJs
ZSBkZXBsb3ltZW50IHNjZW5hcmlvIGZvciB2aWRlbyBzdHVmZiwgYXMgaXQgd291bGQgYWxsb3cg
YSB1c2VyIHRvIGNvbnRpbnVlIHRvIHVzZSB0aGUgc3RhbmRhcmQgcGxheWJhY2sgcGF0aCB3aXRo
IHRoZSBzdGFuZGFyZCBjb250YWluZXJzLCBidXQgYWxzbyBhZmZlY3QgYSBtb3JlLWxpa2VseS10
by1iZS1pbnRlcnByZXRhYmxlLXdpdGgtbG93LWppdHRlciBwbGF5YmFjayB1c2luZyBwYXJ0aWFs
IHJlbGlhYmlsaXR5IGJ5IGhhdmluZyB0aGUgY29udGFpbmVyIGRhdGEgaW4gdGhlIHNlcGFyYXRl
IGZpbGUuDQoNCi09Ug0KDQoNCkZyb206IFFVSUMgPHF1aWMtYm91bmNlc0BpZXRmLm9yZz4gb24g
YmVoYWxmIG9mICJMdWJhc2hldiwgSWdvciIgPGlsdWJhc2hlPTQwYWthbWFpLmNvbUBkbWFyYy5p
ZXRmLm9yZz4NCkRhdGU6IFRodXJzZGF5LCBNYXkgMzEsIDIwMTggYXQgNDozNyBQTQ0KVG86IFJv
YmVydG8gUGVvbiA8ZmVuaXhAZmIuY29tPiwgTWlrZSBCaXNob3AgPG1iaXNob3BAZXZlcXVlZm91
LmJlPiwgTWFydGluIFRob21zb24gPG1hcnRpbi50aG9tc29uQGdtYWlsLmNvbT4NCkNjOiBRVUlD
IFdHIDxxdWljQGlldGYub3JnPg0KU3ViamVjdDogUkU6IFBhcnRpYWxseSBSZWxpYWJsZSBNZXNz
YWdlIFN0cmVhbQ0KDQpWZXJzaW9uIDAyIGlzIGNlcnRhaW5seSBhIG1vcmUgY29tcGxldGUgc29s
dXRpb24sIGJ1dCBpdCBpcyBtb3JlIGNvbXBsZXguICBJIGFtIHZlcnkgaW50ZXJlc3RlZCBpbiBo
ZWFyaW5nIGRpZmZlcmVudCBwZW9wbGUgdmlld3Mgb24gdGhpcyB0cmFkZS1vZmYuDQoNCkkgYW0g
Y3VyaW91cyBvZiB0aGUgc3BlY2lmaWNzIG9mIGFuIGFwcGxpY2F0aW9uIHlvdSBoYXZlIGluIG1p
bmQgZm9yIHRoaXMuICBJLmUuIGhvdyBrZWVwaW5nIG9mZnNldHMgdGhlIHNhbWUgb24gdGhlIHNl
bmRlciBhbmQgcmVjZWl2ZXIgaGVscHMgd2l0aCBhIG1lc3NhZ2Ugc3RyZWFtLiAgQXJlIG9mZnNl
dHMgdGhlbXNlbHZlcyBjb250YWluZWQgaW4gdGhlIG1lc3NhZ2VzPyAgRG9lcyB0aGUgYXBwbGlj
YXRpb24gY29tbXVuaWNhdGUgb2Zmc2V0cyBvdXRzaWRlIG9mIHRoZSBtZXNzYWdlIHN0cmVhbSAo
b24gYSBkaWZmZXJlbnQgc3RyZWFtLCBmb3IgZXhhbXBsZSk/DQoNCihJdCB3aWxsIHByb2JhYmx5
IHdvcmsgYmV0dGVyIHRvIGV4cGxvcmUgdGhpcyBuZXh0IHdlZWsgaW4gcGVyc29uLikNCg0KDQog
ICogICBJZ29yDQoNCkZyb206IFJvYmVydG8gUGVvbiBbbWFpbHRvOmZlbml4QGZiLmNvbV0NClNl
bnQ6IFRodXJzZGF5LCBNYXkgMzEsIDIwMTggMTE6MjEgQU0NClRvOiBNaWtlIEJpc2hvcCA8bWJp
c2hvcEBldmVxdWVmb3UuYmU+OyBNYXJ0aW4gVGhvbXNvbiA8bWFydGluLnRob21zb25AZ21haWwu
Y29tPg0KQ2M6IFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc+OyBMdWJhc2hldiwgSWdvciA8aWx1YmFz
aGVAYWthbWFpLmNvbT4NClN1YmplY3Q6IFJlOiBQYXJ0aWFsbHkgUmVsaWFibGUgTWVzc2FnZSBT
dHJlYW0NCg0KWWVzLiBZb3UgbWF5IHdhbnQgYSBzaW5nbGUgcmVzb3VyY2UgZm9yIGFuIG91dHB1
dCB3aGljaCB5b3UgbWF5IGJlIGdlbmVyYXRpbmcgaW4gcGFyYWxsZWwuIEV2ZW4gaWYgYSBzaW5n
bGUgdGhyZWFkICdvd25zJyB0aGUgc3RyZWFtLCB5b3UndmUgbG9zdCB0aGUgYWJpbGl0eSB0byBj
b29yZGluYXRlIHRoZSBkYXRhIGl0IHJlY2lldmVzIGJ5IG1vbm90b25pY2FsbHkgaW5jcmVhc2lu
ZyBvZmZzZXQuDQoNClJlbnVtYmVyaW5nIHRoZSBvZmZzZXRzIGJyZWFrcyB0aGUgZmlsZS1saWtl
IGFic3RyYWN0aW9uIHdlJ3ZlIGVmZmVjdGl2ZWx5IHVzZWQgZm9yIGh0dHAuDQoNCg0KLT1SDQoN
Cg0KDQpTZW50IHZpYSB0aGUgU2Ftc3VuZyBHYWxheHkgUzcsIGFuIEFUJlQgNEcgTFRFIHNtYXJ0
cGhvbmUNCg0KDQotLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tDQpGcm9tOiBNaWtl
IEJpc2hvcCA8bWJpc2hvcEBldmVxdWVmb3UuYmU8bWFpbHRvOm1iaXNob3BAZXZlcXVlZm91LmJl
Pj4NCkRhdGU6IDUvMzAvMTggODozMyBQTSAoR01ULTA4OjAwKQ0KVG86IFJvYmVydG8gUGVvbiA8
ZmVuaXhAZmIuY29tPG1haWx0bzpmZW5peEBmYi5jb20+PiwgTWFydGluIFRob21zb24gPG1hcnRp
bi50aG9tc29uQGdtYWlsLmNvbTxtYWlsdG86bWFydGluLnRob21zb25AZ21haWwuY29tPj4NCkNj
OiBRVUlDIFdHIDxxdWljQGlldGYub3JnPG1haWx0bzpxdWljQGlldGYub3JnPj4sICJMdWJhc2hl
diwgSWdvciIgPGlsdWJhc2hlPTQwYWthbWFpLmNvbUBkbWFyYy5pZXRmLm9yZzxtYWlsdG86aWx1
YmFzaGU9NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnPj4NClN1YmplY3Q6IFJFOiBQYXJ0aWFs
bHkgUmVsaWFibGUgTWVzc2FnZSBTdHJlYW0NCg0KSnVzdCB0byBiZSBjbGVhcuKApi4gIFlvdeKA
mXJlIHN1Z2dlc3RpbmcgbXVsdGlwbGUgdGhyZWFkcyB0aGF0IHdvdWxkIGJlIHdyaXRpbmcgdG8g
YSBzaW5nbGUgc3RyZWFtIGluIHBhcmFsbGVsLCByYXRoZXIgdGhhbiBhIHNpbmdsZSB0aHJlYWQg
4oCcb3duaW5n4oCdIHRoZSBzdHJlYW0/DQoNCkZyb206IFJvYmVydG8gUGVvbiA8ZmVuaXhAZmIu
Y29tPG1haWx0bzpmZW5peEBmYi5jb20+Pg0KU2VudDogV2VkbmVzZGF5LCBNYXkgMzAsIDIwMTgg
NjowMyBQTQ0KVG86IE1pa2UgQmlzaG9wIDxtYmlzaG9wQGV2ZXF1ZWZvdS5iZTxtYWlsdG86bWJp
c2hvcEBldmVxdWVmb3UuYmU+PjsgTWFydGluIFRob21zb24gPG1hcnRpbi50aG9tc29uQGdtYWls
LmNvbTxtYWlsdG86bWFydGluLnRob21zb25AZ21haWwuY29tPj4NCkNjOiBRVUlDIFdHIDxxdWlj
QGlldGYub3JnPG1haWx0bzpxdWljQGlldGYub3JnPj47IEx1YmFzaGV2LCBJZ29yIDxpbHViYXNo
ZT00MGFrYW1haS5jb21AZG1hcmMuaWV0Zi5vcmc8bWFpbHRvOmlsdWJhc2hlPTQwYWthbWFpLmNv
bUBkbWFyYy5pZXRmLi5vcmc+Pg0KU3ViamVjdDogUmU6IFBhcnRpYWxseSBSZWxpYWJsZSBNZXNz
YWdlIFN0cmVhbQ0KDQpJIGZpbmQgaXQgY29uZnVzaW5nIGFzIHdlbGwuLiAgSSBmYXIgcHJlZmVy
IGtlZXBpbmcgdGhlIG9mZnNldHMgbW9ub3RvbmljYWxseSBpbmNyZWFzaW5nIGFzIGl0IGFsbG93
cyBmb3IgcmVhbC13b3JsZCB1c2Ugb2YgYSBwYXJ0aWFsbHkgcmVsaWFibGUgc3RyZWFtICh3aGVy
ZSB5b3UgbWF5IG5vdCByZWNpZXZlIHRoYXQgZGF0YSBidXQgeW91IGNhbiBhdCBsZWFzdCBmaWd1
cmUgb3V0IHdoYXQgeW91IGRpZCBnZXQgYW5kIGludGVycHJldCBpdCkuDQpJIGRvbnQga25vdyBo
b3cgb25lIHdvaHVkIHJlc29sdmUgdGhlIHJhY2UgZXZlbiB3aXRoaW4gdGhlIHNlbmRpbmcgYXBw
bGljYXRpb24gLS0gb25lIHRocmVhZCBzZW5kcywgYW5vdGhlciB0aHJlYWQgc2VuZHMgd2hpbGUg
dGhlIGZpcnN0IHNheXMgdG8gZm9yZ2V0IGFib3V0IHN0dWZmLiBJIGRvbnQga25vdyB3aGF0IG9m
ZnNldCBzdHVmZiBlbmRzIHVwIGF0IGluIHN1Y2ggY2FzZXMsIGFuZCBzbyBJIGNhbm5vdCBmcmFt
ZSBkYXRhIGluIGEgd2F5IHRoYXQgaXMgbm9uLXN5bmNocm9ub3VzLiBUaGF0IGRlZmVhdHMgc29t
ZSBvZiB0aGUgbWFpbiByZWFzb25zIHRvIGRvIHBhcnRpYWwgcmVsaWFiaWxpdHkgKGkuZS4gdG8g
cmVkdWNlIGppdHRlcikuDQpEcmFmdCAwMiBzZWVtZWQgdG8gYmUgZ29pbmcgaW4gYSBiZXR0ZXIg
ZGlyZWN0aW9uIHcuci50IHRoZSB1c2VjYXNlcyBpIGNhbiBjb25jZWl2ZSBvZi4gSSB0aGluayBy
ZXdpbmRpbmcgdG8gdGhhdCBhbmQgdGhlbiBwb3RlbnRpYWxseSBmaWd1cmluZyBvdXQgaG93IHRv
IHNpbXBsaWZ5IGl0IHdvdWxkIGJlIGZ1biENCkknbSBleGNpdGVkIHRvIGhhdmUgdGhpcyBiZWlu
ZyBkaXNjdXNzZWQsIHNpbmNlIHRoZXJlIGlzIHBlbnQgdXAgZGVtYW5kIHRvIHVzZSBpdCBhbHJl
YWR5Lg0KLT1SDQpHZXQgT3V0bG9vayBmb3IgQW5kcm9pZDxodHRwczovL3VybGRlZmVuc2UucHJv
b2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cHMtM0FfX2FrYS5tc19naGVpMzYmZD1Ed01GQWcmYz01
VkQwUlR0TmxUaDN5Y2Q0MWIzTVV3JnI9QzBzVW8tTEZOQmFZZnlvYUNzZjZUQSZtPVZPVWpfTW53
V2ZfUGdkSHZjR1YxU2UxbzNrNWpDOG04bm9LRGl4cThIcUEmcz0teEpiX0pXT2RMX0RwRE00M0Uw
NlM1NExQRS14a3BZa1NlbjRFbC13a1M0JmU9Pg0KDQpfX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fXw0KRnJvbTogUVVJQyA8cXVpYy1ib3VuY2VzQGlldGYub3JnPG1haWx0bzpxdWljLWJv
dW5jZXNAaWV0Zi5vcmc+PiBvbiBiZWhhbGYgb2YgTWFydGluIFRob21zb24gPG1hcnRpbi50aG9t
c29uQGdtYWlsLmNvbTxtYWlsdG86bWFydGluLnRob21zb25AZ21haWwuY29tPj4NClNlbnQ6IFdl
ZG5lc2RheSwgTWF5IDMwLCAyMDE4IDU6NTA6NTkgUE0NClRvOiBNaWtlIEJpc2hvcA0KQ2M6IFFV
SUMgV0c7IEx1YmFzaGV2LCBJZ29yDQpTdWJqZWN0OiBSZTogUGFydGlhbGx5IFJlbGlhYmxlIE1l
c3NhZ2UgU3RyZWFtDQoNCkxpa2UgTWlrZSwgSSBmaW5kIHRoaXMgZ2FwIHRoaW5nIGNvbmZ1c2lu
Zy4gIEFuZCBNaWtlJ3MgbWVzc2FnZQ0KaGVscGVkLCBidXQgbm90IGEgbG90Lg0KDQpJdCB0b29r
IGEgd2hpbGUgdG8gcmVhbGl6ZSB0aGF0IGZvcmNpbmcgYSBnYXAgY3JlYXRlcyBhIG5ldyBzdGFy
dGluZw0KcG9pbnQgZm9yIHRoZSBuZXh0IG1lc3NhZ2UgdGhhdCBmb3JjZXMgdGhlIHJlY2lwaWVu
dCB0byByZWNvZ25pemUgYW5kDQpkZWFsIHdpdGguICBIb3dldmVyLCB0aGUgbG9naWMgZm9yIGlk
ZW50aWZ5aW5nIHRoYXQgaXMganVzdCBoYXJkIGFuZA0KaXQncyBhbiB1bm5lY2Vzc2FyeSBpbXBv
c2l0aW9uIGluIG15IHZpZXcuDQoNClNheSBJIHNlbmQgYSBtZXNzYWdlIHdpdGggYSBsZW5ndGgg
b2YgMTAgYW5kIG9ubHkgdHdvIG9jdGV0cyBtYWtlIGl0DQpvbnRvIHRoZSB3aXJlIChhcyB3aXRo
IHlvdXIgZXhhbXBsZSksIHRoZW4gaXQgaXMgaW1tZWRpYXRlbHkNCmFiYW5kb25lZC4gIFlvdXIg
c29sdXRpb24gd291bGQgaGF2ZSB0aGUgRVhQSVJFRF9TVFJFQU1fREFUQSBmb3JjZSBhDQpnYXAg
YWZ0ZXIgdGhlIHNlY29uZCBvY3RldCwgc28gdGhhdCB0aGUgbmV4dCBtZXNzYWdlIGNvdWxkIHN0
YXJ0IGF0DQpvZmZzZXQgMyByYXRoZXIgdGhhbiBvZmZzZXQgMTAuICBUaGF0IHNhdmVzIHRoZSBy
ZW1haW5pbmcgNyBvY3RldHMgb2YNCmZsb3cgY29udHJvbCBjcmVkaXQuICAoVXNlIGJpZ2dlciBu
dW1iZXJzIGFuZCBwZXJoYXBzIGl0IHNlZW1zIG1vcmUNCm1vdGl2YXRpbmcpLg0KDQpJZiB0aGUg
b2N0ZXRzIHRoYXQgY292ZXIgdGhlIGdhcCB3ZXJlIHNlbnQsIHRoZW4geW91IGhhdmUgYSBwcm9i
bGVtDQpiZWNhdXNlIG5vdyB5b3UgaGF2ZSBzZW50IHR3byB2ZXJzaW9ucyBvZiB0aGUgc2FtZSBv
Y3RldHMsIHNvIHlvdSBjYW4NCm9ubHkgZG8gdGhpcyBpZiB0aGUgb2N0ZXRzIHdlcmUgbmV2ZXIg
c2VudC4gIEl0IHN0YXJ0cyB0byBnZXQgY2xvc2VyDQphbmQgY2xvc2VyIHRvIHRoZSBwb2ludCB3
aGVyZSBhIG5ldyBzdHJlYW0gaXMganVzdCBlYXNpZXIuDQoNCldvcnN0LCBJIHRoaW5rIGlzIHRo
YXQgdGhlIHJlY2VpdmVyIGhhcyB0byBoYXZlIGNvbXBsaWNhdGVkIGxvZ2ljIGZvcg0KaWRlbnRp
ZnlpbmcgdGhhdCBhIGdhcCBleGlzdHMgYW5kIGRlYWxpbmcgd2l0aCBpdC4gIEl0IGhhcyB0byBy
ZWFkIHVwDQp0byB3aGF0IGl0IGhhcywgb2JzZXJ2ZSB0aGF0IHRoZSBkYXRhIGhhcyBleHBpcmVk
LCB0aGVuIGxlYXJuIHdoZXJlDQp0aGUgZ2FwIGVuZHMsIHRoZW4gcmVzeW5jaHJvbml6ZSBiYXNl
ZCBvbiAxK2dhcF9lbmQgZm9yIHRoZSBuZXh0DQptZXNzYWdlLg0KDQpCZXR0ZXIgdG8gZWF0IHRo
ZSBmbG93IGNvbnRyb2wgY29zdCBpbiBteSB2aWV3LiAgT3Igc2VuZCBSU1RfU1RSRUFNDQphbmQg
bWFrZSBhbm90aGVyIHN0cmVhbS4NCk9uIFRodSwgTWF5IDMxLCAyMDE4IGF0IDg6NDggQU0gTWlr
ZSBCaXNob3AgPG1iaXNob3BAZXZlcXVlZm91LmJlPG1haWx0bzptYmlzaG9wQGV2ZXF1ZWZvdS5i
ZT4+IHdyb3RlOg0KPg0KPiBJIGZpbmQgdGhlIG9uZSBvY3RldCBnYXAgYSBiaXQgY29uZnVzaW5n
LCBidXQgYXMgSSB0aGluayBhYm91dCBpdCwgSSBzZWUgd2h5IHlvdSBuZWVkIGl0LiAgSWYgYWxs
IHRoZSBzdHJlYW0gZGF0YSBhcnJpdmVkIHN1Y2Nlc3NmdWxseSAoYnV0IGhhZG7igJl0IGJlZW4g
YWNrbm93bGVkZ2VkIHlldCBkdWUgdG8gbG9zcyBvZiB0aGUgQUNLLCBkZWxheSwgZXRjLikgYW5k
IHRoZSBFWFBJUkVEX1NUUkVBTV9EQVRBIGdldHMgbG9zdCwgdGhlIHJlY2VpdmVyIGNhbiBvbmx5
IHJldHJvYWN0aXZlbHkgcmVhbGl6ZSB0aGVyZSB3YXMgYSBqdW1wLiAgSGF2aW5nIGFuIG9jdGV0
IHRoYXQgaXMgbmV2ZXIgdHJhbnNtaXR0ZWQgZW5zdXJlcyB0aGUgcmVjZWl2ZXIgYWN0dWFsbHkg
c2VlcyBhIGdhcCwgd2hpY2ggbWVhbnMgdGhhdCBhbiBpbi1vcmRlciBBUEkgd2lsbCBub3QgcHJv
Y2VlZCB1bnRpbCBpdCBoYXMgcmVjZWl2ZWQgZWl0aGVyIHRoZSBtaXNzaW5nIG9jdGV0IG9yIGFu
IEVYUElSRURfU1RSRUFNX0RBVEEgaW5mb3JtaW5nIGl0IHRoZSBvY3RldCB3aWxsIG5ldmVyIGFy
cml2ZS4NCj4NCj4NCj4NCj4gVGhpcyBzaW1wbGlmaWNhdGlvbiAodmVyc3VzIC0wMikgY29tZXMg
YXQgYSBwcmljZTogIElmIGFuIEFQSSB3ZXJlIGV4cG9zaW5nIHN0cmVhbSBkYXRhIG91dC1vZi1v
cmRlciwgdGhlbiBpbiB5b3VyIGV4YW1wbGUsIHRoZSByZWNlaXZlciBrbm93cyB0aGF0IGEgbWVz
c2FnZSBhbHdheXMgYmVnaW5zIG9uIGEgdGVuLWJ5dGUgYm91bmRhcnkuICBBIHJlY2VpdmVyIGNh
biBubyBsb25nZXIgZmluZCB0ZW4tYnl0ZSBib3VuZGFyaWVzLCBiZWNhdXNlIHRoZSBvZmZzZXQg
b24gdGhlIHJlYWQgc2lkZSBkb2VzbuKAmXQgbWF0Y2ggdGhlIG9mZnNldCBvbiB0aGUgc2VuZCBz
aWRlLiAgSSBhZ3JlZSB3aXRoIHlvdSB0aGF0IHRoaXMgc2VlbXMgbGlrZSBhIHJlYXNvbmFibGUg
dHJhZGUtb2ZmIGZvciB0aGUgc2ltcGxlciBmbG93IGNvbnRyb2wuDQo+DQo+DQo+DQo+IE9uZSBj
b25mbGljdCBJIHNlZSBpbiB0aGUgZG9jOg0KPg0KPiDCtyAgICAgICAgIFNlY3Rpb24gMyBzYXlz
OiAgUmVjZWlwdCBvZiBhbiBFWFBJUkVEX1NUUkVBTV9EQVRBIGRvZXMgbm90IGFkdmFuY2UgdGhl
IGxhcmdlc3QgcmVjZWl2ZWQgb2Zmc2V0IGZvciB0aGUgc3RyZWFtLg0KPg0KPiBTZWN0aW9uIDUg
c2F5czogIEEgcmVjZWl2ZXIgU0hPVUxEIGRpc2NhcmQgYW55IHN0cmVhbSBkYXRhIHJlY2VpdmVk
IGZvciBhbiBvZmZzZXQgc21hbGxlciB0aGFuIHRoZSBuZXcgc21hbGxlc3QgcmVjZWl2ZSBvZmZz
ZXQsIHBvc3NpYmx5IGFkdmFuY2luZyB0aGUgbGFyZ2VzdCByZWNlaXZlZCBvZmZzZXQgZm9yIHRo
ZSBzdHJlYW0uDQo+DQo+DQo+DQo+IE90aGVyIG1pbm9yIG5pdHMgYXJlIGJldHRlciBkb25lIHZp
YSBQUi4NCj4NCj4gRnJvbTogUVVJQyA8cXVpYy1ib3VuY2VzQGlldGYub3JnPG1haWx0bzpxdWlj
LWJvdW5jZXNAaWV0Zi5vcmc+PiBPbiBCZWhhbGYgT2YgTHViYXNoZXYsIElnb3INCj4gU2VudDog
V2VkbmVzZGF5LCBNYXkgMzAsIDIwMTggOTo0NSBBTQ0KPiBUbzogUVVJQyBXRyA8cXVpY0BpZXRm
Lm9yZzxtYWlsdG86cXVpY0BpZXRmLm9yZz4+DQo+IFN1YmplY3Q6IFBhcnRpYWxseSBSZWxpYWJs
ZSBNZXNzYWdlIFN0cmVhbQ0KPg0KPg0KPg0KPiBJ4oCZdmUganVzdCB1cGxvYWRlZCBhIG5ldyBk
cmFmdCBmb3IgcGFydGlhbGx5IHJlbGlhYmxlIFFVSUMgc3RyZWFtcy4gIE5vdGU6IHRoaXMgZmVh
dHVyZSBpcyBsaWtlbHkgbm90IGluIHNjb3BlIGZvciBWMSwgYnV0IGl0IGNhbiBiZSBhbiBleHRl
bnNpb24gZm9yIFYxIGFuZC9vciBhIHBhcnQgb2YgVjIuDQo+DQo+DQo+DQo+IFRoZSBuZXcgdmVy
c2lvbiAwMyAoaHR0cHM6Ly91cmxkZWZlbnNlLi4ucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0
cHMtM0FfX3Rvb2xzLmlldGYub3JnX2h0bWxfZHJhZnQtMkRsdWJhc2hldi0yRHF1aWMtMkRwYXJ0
aWFsLTJEcmVsaWFiaWxpdHktMkQwMyZkPUR3SUZhUSZjPTVWRDBSVHRObFRoM3ljZDQxYjNNVXcm
cj1DMHNVby1MRk5CYVlmeW9hQ3NmNlRBJm09eXlScGJlMTRrVFlnWTQxM2dqVmtPYWxXRV9VQzN4
WWVyS3BKcVM4SGlRbyZzPVhaMjk1eGlac04xMXlQOEdMY2RNczFqZjd6MGIyX1doaUl4TUxMb3Ja
WG8mZT08aHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3VybD91PWh0dHBzLTNB
X190b29scy5pZXRmLm9yZ19odG1sX2RyYWZ0LTJEbHViYXNoZXYtMkRxdWljLTJEcGFydGlhbC0y
RHJlbGlhYmlsaXR5LTJEMDMmZD1Ed0lGYVEmYz01VkQwUlR0TmxUaDN5Y2Q0MWIzTVV3JnI9QzBz
VW8tTEZOQmFZZnlvYUNzZjZUQSZtPXl5UnBiZTE0a1RZZ1k0MTNnalZrT2FsV0VfVUMzeFllcktw
SnFTOEhpUW8mcz1YWjI5NXhpWnNOMTF5UDhHTGNkTXMxamY3ejBiMl9XaGlJeE1MTG9yWlhvJmU9
Pikgbm8gbG9uZ2VyIG5lZWRzIGNvbXBsZXggZmxvdyBjb250cm9sIGNoYW5nZXMgYW5kIHJlbW92
ZXMgdGhlIG5lZWQgdG8gdHJhbnNtaXQgbXVsdGlwbGUgZnJhbWVzIGluIHRoZSBzYW1lIHBhY2tl
dC4NCj4NCj4NCj4NCj4gSWdvcg0KPg0KPg0KPg0KPiBQLlMuDQo+DQo+ICAgVGhlcmUgaXMgYWxz
byBhIG5ldyB2ZXJzaW9uIDAyLCB3aGljaCBpbmNsdWRlcyBhIG1vcmUgY29tcGxleCBhbGdvcml0
aG0gd2l0aCBtb3JlIGZlYXR1cmVzIGFuZCBkaWZmZXJlbnQgdHJhZGUtb2Zmcy4gIEJ1dCBJIHRo
aW5rIHZlcnNpb24gMDMgaXMgYSBiZXR0ZXIgbWF0Y2ggZm9yIHRoZSBuZWVkcyBzbyBmYXIuDQo=

--_000_9EFC5C845ABE406AA74C7A9312EF56CFfbcom_
Content-Type: text/html; charset="utf-8"
Content-ID: <FDAB9B955A22DE4AB61305120A1B1F66@namprd15.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPCEtLVtp
ZiAhbXNvXT48c3R5bGU+dlw6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kb1w6KiB7
YmVoYXZpb3I6dXJsKCNkZWZhdWx0I1ZNTCk7fQ0Kd1w6KiB7YmVoYXZpb3I6dXJsKCNkZWZhdWx0
I1ZNTCk7fQ0KLnNoYXBlIHtiZWhhdmlvcjp1cmwoI2RlZmF1bHQjVk1MKTt9DQo8L3N0eWxlPjwh
W2VuZGlmXS0tPjxzdHlsZT48IS0tDQovKiBGb250IERlZmluaXRpb25zICovDQpAZm9udC1mYWNl
DQoJe2ZvbnQtZmFtaWx5OldpbmdkaW5nczsNCglwYW5vc2UtMTo1IDAgMCAwIDAgMCAwIDAgMCAw
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6
MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7
DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMg
Ki8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBp
bjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZh
bWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJ
e21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1
bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1z
dHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVy
bGluZTt9DQpwLk1zb0xpc3RQYXJhZ3JhcGgsIGxpLk1zb0xpc3RQYXJhZ3JhcGgsIGRpdi5Nc29M
aXN0UGFyYWdyYXBoDQoJe21zby1zdHlsZS1wcmlvcml0eTozNDsNCgltYXJnaW4tdG9wOjBpbjsN
CgltYXJnaW4tcmlnaHQ6MGluOw0KCW1hcmdpbi1ib3R0b206MGluOw0KCW1hcmdpbi1sZWZ0Oi41
aW47DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1m
YW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KcC5tc29ub3JtYWwwLCBsaS5tc29ub3JtYWww
LCBkaXYubXNvbm9ybWFsMA0KCXttc28tc3R5bGUtbmFtZTptc29ub3JtYWw7DQoJbXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBpbjsNCgltc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowaW47DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZh
bWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpwLm1zb25vcm1hbDAwLCBsaS5tc29ub3JtYWww
MCwgZGl2Lm1zb25vcm1hbDAwDQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDA7DQoJbXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBpbjsNCgltc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowaW47DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250
LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpwLmVtYWlscXVvdGUsIGxpLmVtYWlscXVv
dGUsIGRpdi5lbWFpbHF1b3RlDQoJe21zby1zdHlsZS1uYW1lOmVtYWlscXVvdGU7DQoJbXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBpbjsNCgltc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDoxLjBwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNwYW4uZW1haWxzdHlsZTIwDQoJe21z
by1zdHlsZS1uYW1lOmVtYWlsc3R5bGUyMDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1z
ZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCnNwYW4uRW1haWxTdHlsZTIyDQoJe21zby1zdHls
ZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNv
bG9yOndpbmRvd3RleHQ7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjMNCgl7bXNvLXN0eWxlLXR5cGU6cGVy
c29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93
dGV4dDt9DQpzcGFuLkVtYWlsU3R5bGUyNA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBs
eTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0
O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQt
c2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0K
CW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3Bh
Z2U6V29yZFNlY3Rpb24xO30NCi8qIExpc3QgRGVmaW5pdGlvbnMgKi8NCkBsaXN0IGwwDQoJe21z
by1saXN0LWlkOjM2MTc4MzAwNDsNCgltc28tbGlzdC10eXBlOmh5YnJpZDsNCgltc28tbGlzdC10
ZW1wbGF0ZS1pZHM6LTc3OTg2MzI5MCAxNzUxMzA2Mzg0IDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4
Njg5IDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3Njk4NjkxIDY3Njk4NjkzO30NCkBsaXN0
IGwwOmxldmVsMQ0KCXttc28tbGV2ZWwtc3RhcnQtYXQ6MDsNCgltc28tbGV2ZWwtbnVtYmVyLWZv
cm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6LTsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9u
ZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWlu
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCW1zby1mYXJlYXN0LWZvbnQt
ZmFtaWx5OkNhbGlicmk7DQoJbXNvLWJpZGktZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiI7
fQ0KQGxpc3QgbDA6bGV2ZWwyDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCglt
c28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1u
dW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6
IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMDpsZXZlbDMNCgl7bXNvLWxldmVsLW51bWJlci1mb3Jt
YXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9u
ZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWlu
Ow0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMDpsZXZlbDQNCgl7bXNvLWxldmVs
LW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwt
dGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1p
bmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZlbDUNCgl7
bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNv
LWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0K
CXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCkBsaXN0
IGwwOmxldmVsNg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVs
LXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXIt
cG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6V2luZ2Rp
bmdzO30NCkBsaXN0IGwwOmxldmVsNw0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7
DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1s
ZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1m
YW1pbHk6U3ltYm9sO30NCkBsaXN0IGwwOmxldmVsOA0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1h
dDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsN
Cgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0K
CWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6bGV2ZWw5DQoJe21zby1sZXZl
bC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVs
LXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQt
aW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDENCgl7bXNv
LWxpc3QtaWQ6MTcyMjU1NDM5OTsNCgltc28tbGlzdC10ZW1wbGF0ZS1pZHM6MTI2NDUwNjQ4MDt9
DQpAbGlzdCBsMTpsZXZlbDENCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1z
by1sZXZlbC10ZXh0Ou+CtzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6LjVpbjsNCgltc28tbGV2ZWwt
bnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCW1zby1hbnNpLWZv
bnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwxOmxldmVsMg0K
CXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0K
CW1zby1sZXZlbC10YWItc3RvcDoxLjBpbjsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxl
ZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCW1zby1hbnNpLWZvbnQtc2l6ZToxMC4wcHQ7DQoJ
Zm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwxOmxldmVsMw0KCXttc28tbGV2ZWwtbnVtYmVy
LWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3Rv
cDoxLjVpbjsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6
LS4yNWluOw0KCW1zby1hbnNpLWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6U3ltYm9s
O30NCkBsaXN0IGwxOmxldmVsNA0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJ
bXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDoyLjBpbjsNCgltc28tbGV2
ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCW1zby1hbnNp
LWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwxOmxldmVs
NQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3
Ow0KCW1zby1sZXZlbC10YWItc3RvcDoyLjVpbjsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9u
OmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCW1zby1hbnNpLWZvbnQtc2l6ZToxMC4wcHQ7
DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwxOmxldmVsNg0KCXttc28tbGV2ZWwtbnVt
YmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWIt
c3RvcDozLjBpbjsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRl
bnQ6LS4yNWluOw0KCW1zby1hbnNpLWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6U3lt
Ym9sO30NCkBsaXN0IGwxOmxldmVsNw0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7
DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDozLjVpbjsNCgltc28t
bGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCW1zby1h
bnNpLWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwxOmxl
dmVsOA0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6
74K3Ow0KCW1zby1sZXZlbC10YWItc3RvcDo0LjBpbjsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0
aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCW1zby1hbnNpLWZvbnQtc2l6ZToxMC4w
cHQ7DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwxOmxldmVsOQ0KCXttc28tbGV2ZWwt
bnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10
YWItc3RvcDo0LjVpbjsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1p
bmRlbnQ6LS4yNWluOw0KCW1zby1hbnNpLWZvbnQtc2l6ZToxMC4wcHQ7DQoJZm9udC1mYW1pbHk6
U3ltYm9sO30NCm9sDQoJe21hcmdpbi1ib3R0b206MGluO30NCnVsDQoJe21hcmdpbi1ib3R0b206
MGluO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1
bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEt
LVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzpp
ZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtl
bmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0i
cHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5CYWNrZ3JvdW5kIChib3JpbmcgZm9yIGZvbGtzIHdobyBrbm93IGFib3V0IGludGVyYWN0aXZl
IHZpZGVvKTo8YnI+DQo8YnI+DQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PkluIGEgcmVhbC10aW1lL2xvdy1qaXR0ZXIgdXNlLWNhc2UsIHRoZSBwbGF5ZXIgbWF5IHNraXAg
b3ZlciBzb21lIChvbGRlcikgcGFydCBvZiB0aGUgYml0c3RyZWFtIGluIGZhdm9yIG9mIGRlY29k
aW5nL2ludGVycHJldGluZyBtb3JlIHJlY2VudCBkYXRhLjxicj4NCldoZW4gdGhhdCBoYXBwZW5z
LCBpdCB3aWxsIGJlIHVuaW50ZXJlc3RlZCBpbiBhbnkgb2xkZXIgZGF0YS48YnI+DQo8YnI+DQpI
b3cgZG9lcyBpdCBmaW5kIHRoZSBtb3N0IGFwcHJvcHJpYXRlIG5leHQgZGF0YT8gSXQgdHlwaWNh
bGx5IGlzIG5vdCB0aGUgZGF0YSB0aGF0IGlzIHRoZSBtb3N0IHJlY2VudOKAlGV2ZW4gZm9yIGlu
dGVyYWN0aXZlIOKAmHBsYXliYWNr4oCZLCB5b3Ugd2FudCBhIH4xMDBtcy0yMDBtcyBidWZmZXIg
dG8gZGVhbCB3aXRoIG5ldHdvcmsgaml0dGVyLjxicj4NClRvIGRlY29kZSB0aGUgdmlkZW8gYml0
c3RyZWFtLCB3ZSBuZWVkIHRvIGtub3cgd2hlcmUgdGhlIGZyYW1lcyBhcmUgaW4gaXQuIEl0ICh0
aGUgYmlzdHJlYW0pIGRvZXNu4oCZdCBhbHdheXMgaGF2ZSBmcmFtaW5nIG9mIGl0cyBvd24uPGJy
Pg0KPGJyPg0KSWYgdGhlcmUgaXMgYW4g4oCYaW5kZXjigJkgc3RyZWFtIGludG8gd2hpY2ggd2Ug
cHV0IHRoZSBwZXItZnJhbWUvcGVyLXRpbWUtdW5pdCBtZXRhZGF0YSBhYm91dCB0aGUgdmlkZW8g
Yml0c3RyZWFtICh3aGljaCB3ZSBwdXQgb24gYW5vdGhlciBzdHJlYW0pLCB3ZSBjYW4gY2hlYXBs
eSB1bmRlcnN0YW5kIHRoZSBmcmFtaW5nIGZvciB0aGUgYml0c3RyZWFtLjxicj4NClRoYXQgZW5h
YmxlcyB0aGUgcGxheWVyIHRvIHNlZWsgYWhlYWQgdG8gdGhlIHBhcnRzIHRoYXQgaXQgY2FuIGlu
dGVycHJldCwgYXMgdGhlIHJlYWRlciBvZiB0aGUgaW5kZXggc3RyZWFtIGtub3dzIHRoYXQgaWYg
aXQgaGFzIGsgYnl0ZXMgc3RhcnRpbmcgYXQgYSBwb3NpdGlvbiB3aGVyZSBuICUgayA9PTAsIGl0
IGlzIGEgdmFsaWQgcmVjb3JkLiBZb3UgY2Fu4oCZdCBkbyB0aGF0IG9uIHRoZSBiaXRzdHJlYW0s
IGFzIGl0IGhhcyB2YXJpYWJsZSBsZW5ndGguDQogWW91IGNvdWxkIOKAmGVzY2FwZeKAmSBvbiB0
aGUgYml0c3RyZWFtIHRvIGVuc3VyZSBhIHVuaXF1ZSBmcmFtaW5nIHRva2VuLCBidXQgdGhhdCB3
b3VsZCBleHBhbmQgdGhlIHNpemUgb2YgdGhlIGJpdHN0cmVhbSwgYW5kIGJlIGEgcGFpbiBpbiBv
dGhlcnMuPGJyPg0KPGJyPg0KWW91IGNhbiB0aGVuIHBsYXkgZXZlbiBtb3JlIGZ1biBnYW1lcywg
Zm9yIGluc3RhbmNlIHB1dHRpbmcgdGhlIGZyYW1pbmcgaW4gYm90aCBmaXhlZC1zaXplIGFuZCBu
b24tZml4ZWQgc2l6ZSBzdHJlYW1zLiBJbiBzdWNoIGEgY2FzZSB5b3UgY2FuIHJlY292ZXIgZnJh
bWluZyBpZiB5b3UgaGF2ZSByZWNlaXZlZCB0aGF0IHBhcnQgb2YgdGhlIGluZGV4IHN0cmVhbSB0
aGF0IGRlc2NyaWJlcyB0aGUgYml0c3RyZWFtIHRoYXQgeW91IHdpc2ggdG8gaW50ZXJwcmV0LA0K
IG9yIGlmIHRoZSBiaXRzdHJlYW0gZnJhbWluZyBpcyBpbnRhY3QgZnJvbSBhbnkgcG9pbnQgd2hl
cmUgeW91IHVuZGVyc3Rvb2QgaXQgaW4gdGhlIHBhc3QuPGJyPg0KPGJyPg0KVGhlIGxhdHRlciDi
gJxldmVuIG1vcmUgZnVuIGdhbWVz4oCdIGlzIGEgcmVhc29uYWJsZSBkZXBsb3ltZW50IHNjZW5h
cmlvIGZvciB2aWRlbyBzdHVmZiwgYXMgaXQgd291bGQgYWxsb3cgYSB1c2VyIHRvIGNvbnRpbnVl
IHRvIHVzZSB0aGUgc3RhbmRhcmQgcGxheWJhY2sgcGF0aCB3aXRoIHRoZSBzdGFuZGFyZCBjb250
YWluZXJzLCBidXQgYWxzbyBhZmZlY3QgYSBtb3JlLWxpa2VseS10by1iZS1pbnRlcnByZXRhYmxl
LXdpdGgtbG93LWppdHRlciBwbGF5YmFjaw0KIHVzaW5nIHBhcnRpYWwgcmVsaWFiaWxpdHkgYnkg
aGF2aW5nIHRoZSBjb250YWluZXIgZGF0YSBpbiB0aGUgc2VwYXJhdGUgZmlsZS48YnI+DQo8YnI+
DQotPVI8YnI+DQo8YnI+DQo8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpz
b2xpZCAjQjVDNERGIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Y29sb3I6YmxhY2si
PkZyb206IDwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Y29sb3I6Ymxh
Y2siPlFVSUMgJmx0O3F1aWMtYm91bmNlc0BpZXRmLm9yZyZndDsgb24gYmVoYWxmIG9mICZxdW90
O0x1YmFzaGV2LCBJZ29yJnF1b3Q7ICZsdDtpbHViYXNoZT00MGFrYW1haS5jb21AZG1hcmMuaWV0
Zi5vcmcmZ3Q7PGJyPg0KPGI+RGF0ZTogPC9iPlRodXJzZGF5LCBNYXkgMzEsIDIwMTggYXQgNDoz
NyBQTTxicj4NCjxiPlRvOiA8L2I+Um9iZXJ0byBQZW9uICZsdDtmZW5peEBmYi5jb20mZ3Q7LCBN
aWtlIEJpc2hvcCAmbHQ7bWJpc2hvcEBldmVxdWVmb3UuYmUmZ3Q7LCBNYXJ0aW4gVGhvbXNvbiAm
bHQ7bWFydGluLnRob21zb25AZ21haWwuY29tJmd0Ozxicj4NCjxiPkNjOiA8L2I+UVVJQyBXRyAm
bHQ7cXVpY0BpZXRmLm9yZyZndDs8YnI+DQo8Yj5TdWJqZWN0OiA8L2I+UkU6IFBhcnRpYWxseSBS
ZWxpYWJsZSBNZXNzYWdlIFN0cmVhbTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5WZXJzaW9uIDAyIGlzIGNlcnRhaW5seSBhIG1vcmUgY29tcGxl
dGUgc29sdXRpb24sIGJ1dCBpdCBpcyBtb3JlIGNvbXBsZXguJm5ic3A7IEkgYW0gdmVyeSBpbnRl
cmVzdGVkIGluIGhlYXJpbmcgZGlmZmVyZW50IHBlb3BsZSB2aWV3cyBvbiB0aGlzIHRyYWRlLW9m
Zi48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSBhbSBjdXJpb3VzIG9mIHRoZSBzcGVjaWZpY3Mg
b2YgYW4gYXBwbGljYXRpb24geW91IGhhdmUgaW4gbWluZCBmb3IgdGhpcy4mbmJzcDsgSS5lLiBo
b3cga2VlcGluZyBvZmZzZXRzIHRoZSBzYW1lIG9uIHRoZSBzZW5kZXIgYW5kIHJlY2VpdmVyIGhl
bHBzIHdpdGggYSBtZXNzYWdlIHN0cmVhbS4mbmJzcDsgQXJlIG9mZnNldHMgdGhlbXNlbHZlcyBj
b250YWluZWQgaW4gdGhlIG1lc3NhZ2VzPyZuYnNwOyBEb2VzIHRoZSBhcHBsaWNhdGlvbg0KIGNv
bW11bmljYXRlIG9mZnNldHMgb3V0c2lkZSBvZiB0aGUgbWVzc2FnZSBzdHJlYW0gKG9uIGEgZGlm
ZmVyZW50IHN0cmVhbSwgZm9yIGV4YW1wbGUpPzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4oSXQg
d2lsbCBwcm9iYWJseSB3b3JrIGJldHRlciB0byBleHBsb3JlIHRoaXMgbmV4dCB3ZWVrIGluIHBl
cnNvbi4pPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8bzpwPjwv
bzpwPjwvcD4NCjx1bCBzdHlsZT0ibWFyZ2luLXRvcDowaW4iIHR5cGU9ImRpc2MiPg0KPGxpIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbGlzdDpsMCBsZXZlbDEgbGZvMyI+SWdvcjxvOnA+
PC9vOnA+PC9saT48L3VsPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48
L3A+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFF
MUUxIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PGI+RnJvbTo8L2I+IFJvYmVydG8gUGVvbiBbbWFpbHRvOmZlbml4QGZiLmNvbV0gPGJyPg0K
PGI+U2VudDo8L2I+IFRodXJzZGF5LCBNYXkgMzEsIDIwMTggMTE6MjEgQU08YnI+DQo8Yj5Ubzo8
L2I+IE1pa2UgQmlzaG9wICZsdDttYmlzaG9wQGV2ZXF1ZWZvdS5iZSZndDs7IE1hcnRpbiBUaG9t
c29uICZsdDttYXJ0aW4udGhvbXNvbkBnbWFpbC5jb20mZ3Q7PGJyPg0KPGI+Q2M6PC9iPiBRVUlD
IFdHICZsdDtxdWljQGlldGYub3JnJmd0OzsgTHViYXNoZXYsIElnb3IgJmx0O2lsdWJhc2hlQGFr
YW1haS5jb20mZ3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBQYXJ0aWFsbHkgUmVsaWFibGUg
TWVzc2FnZSBTdHJlYW08bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5ZZXMuIFlvdSBtYXkgd2FudCBhIHNpbmdsZSByZXNvdXJjZSBmb3IgYW4gb3V0cHV0IHdo
aWNoIHlvdSBtYXkgYmUgZ2VuZXJhdGluZyBpbiBwYXJhbGxlbC4gRXZlbiBpZiBhIHNpbmdsZSB0
aHJlYWQgJ293bnMnIHRoZSBzdHJlYW0sIHlvdSd2ZSBsb3N0IHRoZSBhYmlsaXR5IHRvIGNvb3Jk
aW5hdGUgdGhlIGRhdGEgaXQgcmVjaWV2ZXMgYnkgbW9ub3RvbmljYWxseSBpbmNyZWFzaW5nIG9m
ZnNldC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+UmVudW1iZXJpbmcgdGhlIG9mZnNldHMgYnJlYWtzIHRoZSBmaWxlLWxpa2UgYWJzdHJhY3Rp
b24gd2UndmUgZWZmZWN0aXZlbHkgdXNlZCBmb3IgaHR0cC48bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4tPVI8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGRpdiBpZD0iY29tcG9zZXJfc2lnbmF0dXJlIj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjkuNXB0O2NvbG9yOiM1NzU3NTci
PlNlbnQgdmlhIHRoZSBTYW1zdW5nIEdhbGF4eSBTNywgYW4gQVQmYW1wO1QgNEcgTFRFIHNtYXJ0
cGhvbmU8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj4tLS0tLS0tLSBPcmlnaW5hbCBtZXNzYWdlIC0tLS0tLS0tPG86
cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Gcm9tOiBN
aWtlIEJpc2hvcCAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1iaXNob3BAZXZlcXVlZm91LmJlIj5tYmlz
aG9wQGV2ZXF1ZWZvdS5iZTwvYT4mZ3Q7DQo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPkRhdGU6IDUvMzAvMTggODozMyBQTSAoR01ULTA4OjAwKSA8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRvOiBS
b2JlcnRvIFBlb24gJmx0OzxhIGhyZWY9Im1haWx0bzpmZW5peEBmYi5jb20iPmZlbml4QGZiLmNv
bTwvYT4mZ3Q7LCBNYXJ0aW4gVGhvbXNvbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1hcnRpbi50aG9t
c29uQGdtYWlsLmNvbSI+bWFydGluLnRob21zb25AZ21haWwuY29tPC9hPiZndDsNCjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Q2M6IFFVSUMgV0cg
Jmx0OzxhIGhyZWY9Im1haWx0bzpxdWljQGlldGYub3JnIj5xdWljQGlldGYub3JnPC9hPiZndDss
ICZxdW90O0x1YmFzaGV2LCBJZ29yJnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86aWx1YmFzaGU9
NDBha2FtYWkuY29tQGRtYXJjLmlldGYub3JnIj5pbHViYXNoZT00MGFrYW1haS5jb21AZG1hcmMu
aWV0Zi5vcmc8L2E+Jmd0Ow0KPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5TdWJqZWN0OiBSRTogUGFydGlhbGx5IFJlbGlhYmxlIE1lc3NhZ2UgU3Ry
ZWFtIDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+SnVzdCB0byBiZSBjbGVhcuKApi4mbmJzcDsgWW914oCZcmUgc3VnZ2VzdGluZyBt
dWx0aXBsZSB0aHJlYWRzIHRoYXQgd291bGQgYmUgd3JpdGluZyB0byBhIHNpbmdsZSBzdHJlYW0g
aW4gcGFyYWxsZWwsIHJhdGhlciB0aGFuIGEgc2luZ2xlIHRocmVhZCDigJxvd25pbmfigJ0gdGhl
IHN0cmVhbT88bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+
PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29s
aWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxiPkZyb206PC9iPiBSb2JlcnRvIFBlb24gJmx0OzxhIGhyZWY9Im1haWx0bzpm
ZW5peEBmYi5jb20iPmZlbml4QGZiLmNvbTwvYT4mZ3Q7DQo8YnI+DQo8Yj5TZW50OjwvYj4gV2Vk
bmVzZGF5LCBNYXkgMzAsIDIwMTggNjowMyBQTTxicj4NCjxiPlRvOjwvYj4gTWlrZSBCaXNob3Ag
Jmx0OzxhIGhyZWY9Im1haWx0bzptYmlzaG9wQGV2ZXF1ZWZvdS5iZSI+bWJpc2hvcEBldmVxdWVm
b3UuYmU8L2E+Jmd0OzsgTWFydGluIFRob21zb24gJmx0OzxhIGhyZWY9Im1haWx0bzptYXJ0aW4u
dGhvbXNvbkBnbWFpbC5jb20iPm1hcnRpbi50aG9tc29uQGdtYWlsLmNvbTwvYT4mZ3Q7PGJyPg0K
PGI+Q2M6PC9iPiBRVUlDIFdHICZsdDs8YSBocmVmPSJtYWlsdG86cXVpY0BpZXRmLm9yZyI+cXVp
Y0BpZXRmLm9yZzwvYT4mZ3Q7OyBMdWJhc2hldiwgSWdvciAmbHQ7PGEgaHJlZj0ibWFpbHRvOmls
dWJhc2hlPTQwYWthbWFpLmNvbUBkbWFyYy5pZXRmLi5vcmciPmlsdWJhc2hlPTQwYWthbWFpLmNv
bUBkbWFyYy5pZXRmLm9yZzwvYT4mZ3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBQYXJ0aWFs
bHkgUmVsaWFibGUgTWVzc2FnZSBTdHJlYW08bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3Bh
biBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7QXJpYWwmcXVvdDssc2Fucy1zZXJpZjtjb2xvcjpi
bGFjayI+SSBmaW5kIGl0IGNvbmZ1c2luZyBhcyB3ZWxsLi4mbmJzcDsgSSBmYXIgcHJlZmVyIGtl
ZXBpbmcgdGhlIG9mZnNldHMgbW9ub3RvbmljYWxseSBpbmNyZWFzaW5nIGFzIGl0IGFsbG93cyBm
b3IgcmVhbC13b3JsZCB1c2Ugb2YgYSBwYXJ0aWFsbHkgcmVsaWFibGUgc3RyZWFtDQogKHdoZXJl
IHlvdSBtYXkgbm90IHJlY2lldmUgdGhhdCBkYXRhIGJ1dCB5b3UgY2FuIGF0IGxlYXN0IGZpZ3Vy
ZSBvdXQgd2hhdCB5b3UgZGlkIGdldCBhbmQgaW50ZXJwcmV0IGl0KS48L3NwYW4+PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2lu
LWJvdHRvbToxMi4wcHQiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5JIGRvbnQga25vdyBob3cgb25lIHdvaHVkIHJlc29s
dmUgdGhlIHJhY2UgZXZlbiB3aXRoaW4gdGhlIHNlbmRpbmcgYXBwbGljYXRpb24gLS0gb25lIHRo
cmVhZCBzZW5kcywgYW5vdGhlciB0aHJlYWQgc2VuZHMgd2hpbGUgdGhlIGZpcnN0IHNheXMgdG8g
Zm9yZ2V0DQogYWJvdXQgc3R1ZmYuIEkgZG9udCBrbm93IHdoYXQgb2Zmc2V0IHN0dWZmIGVuZHMg
dXAgYXQgaW4gc3VjaCBjYXNlcywgYW5kIHNvIEkgY2Fubm90IGZyYW1lIGRhdGEgaW4gYSB3YXkg
dGhhdCBpcyBub24tc3luY2hyb25vdXMuIFRoYXQgZGVmZWF0cyBzb21lIG9mIHRoZSBtYWluIHJl
YXNvbnMgdG8gZG8gcGFydGlhbCByZWxpYWJpbGl0eSAoaS5lLiB0byByZWR1Y2Ugaml0dGVyKS48
L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTom
cXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj5EcmFmdCAwMiBzZWVtZWQg
dG8gYmUgZ29pbmcgaW4gYSBiZXR0ZXIgZGlyZWN0aW9uIHcuci50IHRoZSB1c2VjYXNlcyBpIGNh
biBjb25jZWl2ZSBvZi4gSSB0aGluayByZXdpbmRpbmcgdG8gdGhhdCBhbmQgdGhlbiBwb3RlbnRp
YWxseSBmaWd1cmluZyBvdXQgaG93DQogdG8gc2ltcGxpZnkgaXQgd291bGQgYmUgZnVuITwvc3Bh
bj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90OyxzYW5zLXNlcmlmO2NvbG9y
OmJsYWNrIj5JJ20gZXhjaXRlZCB0byBoYXZlIHRoaXMgYmVpbmcgZGlzY3Vzc2VkLCBzaW5jZSB0
aGVyZSBpcyBwZW50IHVwIGRlbWFuZCB0byB1c2UgaXQgYWxyZWFkeS48L3NwYW4+PG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2lu
LWJvdHRvbToxMi4wcHQiPjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtBcmlhbCZxdW90
OyxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrIj4tPVI8L3NwYW4+PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQt
ZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPkdldA0KPGEg
aHJlZj0iaHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3VybD91PWh0dHBzLTNB
X19ha2EubXNfZ2hlaTM2JmFtcDtkPUR3TUZBZyZhbXA7Yz01VkQwUlR0TmxUaDN5Y2Q0MWIzTVV3
JmFtcDtyPUMwc1VvLUxGTkJhWWZ5b2FDc2Y2VEEmYW1wO209Vk9Val9NbndXZl9QZ2RIdmNHVjFT
ZTFvM2s1akM4bThub0tEaXhxOEhxQSZhbXA7cz0teEpiX0pXT2RMX0RwRE00M0UwNlM1NExQRS14
a3BZa1NlbjRFbC13a1M0JmFtcDtlPSI+DQpPdXRsb29rIGZvciBBbmRyb2lkPC9hPjwvc3Bhbj48
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
ImZvbnQtZmFtaWx5OiZxdW90O0FyaWFsJnF1b3Q7LHNhbnMtc2VyaWY7Y29sb3I6YmxhY2siPiZu
YnNwOzwvc3Bhbj48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iTXNvTm9ybWFs
IiBhbGlnbj0iY2VudGVyIiBzdHlsZT0idGV4dC1hbGlnbjpjZW50ZXIiPg0KPGhyIHNpemU9IjIi
IHdpZHRoPSI5OCUiIGFsaWduPSJjZW50ZXIiPg0KPC9kaXY+DQo8ZGl2IGlkPSJ4X2RpdlJwbHlG
d2RNc2ciPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNr
Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj4gUVVJQyAmbHQ7PGEg
aHJlZj0ibWFpbHRvOnF1aWMtYm91bmNlc0BpZXRmLm9yZyI+cXVpYy1ib3VuY2VzQGlldGYub3Jn
PC9hPiZndDsgb24gYmVoYWxmIG9mIE1hcnRpbiBUaG9tc29uICZsdDs8YSBocmVmPSJtYWlsdG86
bWFydGluLnRob21zb25AZ21haWwuY29tIj5tYXJ0aW4udGhvbXNvbkBnbWFpbC5jb208L2E+Jmd0
Ozxicj4NCjxiPlNlbnQ6PC9iPiBXZWRuZXNkYXksIE1heSAzMCwgMjAxOCA1OjUwOjU5IFBNPGJy
Pg0KPGI+VG86PC9iPiBNaWtlIEJpc2hvcDxicj4NCjxiPkNjOjwvYj4gUVVJQyBXRzsgTHViYXNo
ZXYsIElnb3I8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFBhcnRpYWxseSBSZWxpYWJsZSBNZXNz
YWdlIFN0cmVhbTwvc3Bhbj4gPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij5MaWtl
IE1pa2UsIEkgZmluZCB0aGlzIGdhcCB0aGluZyBjb25mdXNpbmcuJm5ic3A7IEFuZCBNaWtlJ3Mg
bWVzc2FnZTxicj4NCmhlbHBlZCwgYnV0IG5vdCBhIGxvdC48YnI+DQo8YnI+DQpJdCB0b29rIGEg
d2hpbGUgdG8gcmVhbGl6ZSB0aGF0IGZvcmNpbmcgYSBnYXAgY3JlYXRlcyBhIG5ldyBzdGFydGlu
Zzxicj4NCnBvaW50IGZvciB0aGUgbmV4dCBtZXNzYWdlIHRoYXQgZm9yY2VzIHRoZSByZWNpcGll
bnQgdG8gcmVjb2duaXplIGFuZDxicj4NCmRlYWwgd2l0aC4mbmJzcDsgSG93ZXZlciwgdGhlIGxv
Z2ljIGZvciBpZGVudGlmeWluZyB0aGF0IGlzIGp1c3QgaGFyZCBhbmQ8YnI+DQppdCdzIGFuIHVu
bmVjZXNzYXJ5IGltcG9zaXRpb24gaW4gbXkgdmlldy48YnI+DQo8YnI+DQpTYXkgSSBzZW5kIGEg
bWVzc2FnZSB3aXRoIGEgbGVuZ3RoIG9mIDEwIGFuZCBvbmx5IHR3byBvY3RldHMgbWFrZSBpdDxi
cj4NCm9udG8gdGhlIHdpcmUgKGFzIHdpdGggeW91ciBleGFtcGxlKSwgdGhlbiBpdCBpcyBpbW1l
ZGlhdGVseTxicj4NCmFiYW5kb25lZC4mbmJzcDsgWW91ciBzb2x1dGlvbiB3b3VsZCBoYXZlIHRo
ZSBFWFBJUkVEX1NUUkVBTV9EQVRBIGZvcmNlIGE8YnI+DQpnYXAgYWZ0ZXIgdGhlIHNlY29uZCBv
Y3RldCwgc28gdGhhdCB0aGUgbmV4dCBtZXNzYWdlIGNvdWxkIHN0YXJ0IGF0PGJyPg0Kb2Zmc2V0
IDMgcmF0aGVyIHRoYW4gb2Zmc2V0IDEwLiZuYnNwOyBUaGF0IHNhdmVzIHRoZSByZW1haW5pbmcg
NyBvY3RldHMgb2Y8YnI+DQpmbG93IGNvbnRyb2wgY3JlZGl0LiZuYnNwOyAoVXNlIGJpZ2dlciBu
dW1iZXJzIGFuZCBwZXJoYXBzIGl0IHNlZW1zIG1vcmU8YnI+DQptb3RpdmF0aW5nKS48YnI+DQo8
YnI+DQpJZiB0aGUgb2N0ZXRzIHRoYXQgY292ZXIgdGhlIGdhcCB3ZXJlIHNlbnQsIHRoZW4geW91
IGhhdmUgYSBwcm9ibGVtPGJyPg0KYmVjYXVzZSBub3cgeW91IGhhdmUgc2VudCB0d28gdmVyc2lv
bnMgb2YgdGhlIHNhbWUgb2N0ZXRzLCBzbyB5b3UgY2FuPGJyPg0Kb25seSBkbyB0aGlzIGlmIHRo
ZSBvY3RldHMgd2VyZSBuZXZlciBzZW50LiZuYnNwOyBJdCBzdGFydHMgdG8gZ2V0IGNsb3Nlcjxi
cj4NCmFuZCBjbG9zZXIgdG8gdGhlIHBvaW50IHdoZXJlIGEgbmV3IHN0cmVhbSBpcyBqdXN0IGVh
c2llci48YnI+DQo8YnI+DQpXb3JzdCwgSSB0aGluayBpcyB0aGF0IHRoZSByZWNlaXZlciBoYXMg
dG8gaGF2ZSBjb21wbGljYXRlZCBsb2dpYyBmb3I8YnI+DQppZGVudGlmeWluZyB0aGF0IGEgZ2Fw
IGV4aXN0cyBhbmQgZGVhbGluZyB3aXRoIGl0LiZuYnNwOyBJdCBoYXMgdG8gcmVhZCB1cDxicj4N
CnRvIHdoYXQgaXQgaGFzLCBvYnNlcnZlIHRoYXQgdGhlIGRhdGEgaGFzIGV4cGlyZWQsIHRoZW4g
bGVhcm4gd2hlcmU8YnI+DQp0aGUgZ2FwIGVuZHMsIHRoZW4gcmVzeW5jaHJvbml6ZSBiYXNlZCBv
biAxJiM0MztnYXBfZW5kIGZvciB0aGUgbmV4dDxicj4NCm1lc3NhZ2UuPGJyPg0KPGJyPg0KQmV0
dGVyIHRvIGVhdCB0aGUgZmxvdyBjb250cm9sIGNvc3QgaW4gbXkgdmlldy4mbmJzcDsgT3Igc2Vu
ZCBSU1RfU1RSRUFNPGJyPg0KYW5kIG1ha2UgYW5vdGhlciBzdHJlYW0uPGJyPg0KT24gVGh1LCBN
YXkgMzEsIDIwMTggYXQgODo0OCBBTSBNaWtlIEJpc2hvcCAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1i
aXNob3BAZXZlcXVlZm91LmJlIj5tYmlzaG9wQGV2ZXF1ZWZvdS5iZTwvYT4mZ3Q7IHdyb3RlOjxi
cj4NCiZndDs8YnI+DQomZ3Q7IEkgZmluZCB0aGUgb25lIG9jdGV0IGdhcCBhIGJpdCBjb25mdXNp
bmcsIGJ1dCBhcyBJIHRoaW5rIGFib3V0IGl0LCBJIHNlZSB3aHkgeW91IG5lZWQgaXQuJm5ic3A7
IElmIGFsbCB0aGUgc3RyZWFtIGRhdGEgYXJyaXZlZCBzdWNjZXNzZnVsbHkgKGJ1dCBoYWRu4oCZ
dCBiZWVuIGFja25vd2xlZGdlZCB5ZXQgZHVlIHRvIGxvc3Mgb2YgdGhlIEFDSywgZGVsYXksIGV0
Yy4pIGFuZCB0aGUgRVhQSVJFRF9TVFJFQU1fREFUQSBnZXRzIGxvc3QsIHRoZSByZWNlaXZlcg0K
IGNhbiBvbmx5IHJldHJvYWN0aXZlbHkgcmVhbGl6ZSB0aGVyZSB3YXMgYSBqdW1wLiZuYnNwOyBI
YXZpbmcgYW4gb2N0ZXQgdGhhdCBpcyBuZXZlciB0cmFuc21pdHRlZCBlbnN1cmVzIHRoZSByZWNl
aXZlciBhY3R1YWxseSBzZWVzIGEgZ2FwLCB3aGljaCBtZWFucyB0aGF0IGFuIGluLW9yZGVyIEFQ
SSB3aWxsIG5vdCBwcm9jZWVkIHVudGlsIGl0IGhhcyByZWNlaXZlZCBlaXRoZXIgdGhlIG1pc3Np
bmcgb2N0ZXQgb3IgYW4gRVhQSVJFRF9TVFJFQU1fREFUQQ0KIGluZm9ybWluZyBpdCB0aGUgb2N0
ZXQgd2lsbCBuZXZlciBhcnJpdmUuPGJyPg0KJmd0Ozxicj4NCiZndDs8YnI+DQomZ3Q7PGJyPg0K
Jmd0OyBUaGlzIHNpbXBsaWZpY2F0aW9uICh2ZXJzdXMgLTAyKSBjb21lcyBhdCBhIHByaWNlOiZu
YnNwOyBJZiBhbiBBUEkgd2VyZSBleHBvc2luZyBzdHJlYW0gZGF0YSBvdXQtb2Ytb3JkZXIsIHRo
ZW4gaW4geW91ciBleGFtcGxlLCB0aGUgcmVjZWl2ZXIga25vd3MgdGhhdCBhIG1lc3NhZ2UgYWx3
YXlzIGJlZ2lucyBvbiBhIHRlbi1ieXRlIGJvdW5kYXJ5LiZuYnNwOyBBIHJlY2VpdmVyIGNhbiBu
byBsb25nZXIgZmluZCB0ZW4tYnl0ZSBib3VuZGFyaWVzLCBiZWNhdXNlDQogdGhlIG9mZnNldCBv
biB0aGUgcmVhZCBzaWRlIGRvZXNu4oCZdCBtYXRjaCB0aGUgb2Zmc2V0IG9uIHRoZSBzZW5kIHNp
ZGUuJm5ic3A7IEkgYWdyZWUgd2l0aCB5b3UgdGhhdCB0aGlzIHNlZW1zIGxpa2UgYSByZWFzb25h
YmxlIHRyYWRlLW9mZiBmb3IgdGhlIHNpbXBsZXIgZmxvdyBjb250cm9sLjxicj4NCiZndDs8YnI+
DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCiZndDsgT25lIGNvbmZsaWN0IEkgc2VlIGluIHRoZSBkb2M6
PGJyPg0KJmd0Ozxicj4NCiZndDsgwrcmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsgU2VjdGlvbiAzIHNheXM6Jm5ic3A7IFJlY2VpcHQgb2YgYW4gRVhQSVJF
RF9TVFJFQU1fREFUQSBkb2VzIG5vdCBhZHZhbmNlIHRoZSBsYXJnZXN0IHJlY2VpdmVkIG9mZnNl
dCBmb3IgdGhlIHN0cmVhbS48YnI+DQomZ3Q7PGJyPg0KJmd0OyBTZWN0aW9uIDUgc2F5czombmJz
cDsgQSByZWNlaXZlciBTSE9VTEQgZGlzY2FyZCBhbnkgc3RyZWFtIGRhdGEgcmVjZWl2ZWQgZm9y
IGFuIG9mZnNldCBzbWFsbGVyIHRoYW4gdGhlIG5ldyBzbWFsbGVzdCByZWNlaXZlIG9mZnNldCwg
cG9zc2libHkgYWR2YW5jaW5nIHRoZSBsYXJnZXN0IHJlY2VpdmVkIG9mZnNldCBmb3IgdGhlIHN0
cmVhbS48YnI+DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCiZndDs8YnI+DQomZ3Q7IE90aGVyIG1pbm9y
IG5pdHMgYXJlIGJldHRlciBkb25lIHZpYSBQUi48YnI+DQomZ3Q7PGJyPg0KJmd0OyBGcm9tOiBR
VUlDICZsdDs8YSBocmVmPSJtYWlsdG86cXVpYy1ib3VuY2VzQGlldGYub3JnIj5xdWljLWJvdW5j
ZXNAaWV0Zi5vcmc8L2E+Jmd0OyBPbiBCZWhhbGYgT2YgTHViYXNoZXYsIElnb3I8YnI+DQomZ3Q7
IFNlbnQ6IFdlZG5lc2RheSwgTWF5IDMwLCAyMDE4IDk6NDUgQU08YnI+DQomZ3Q7IFRvOiBRVUlD
IFdHICZsdDs8YSBocmVmPSJtYWlsdG86cXVpY0BpZXRmLm9yZyI+cXVpY0BpZXRmLm9yZzwvYT4m
Z3Q7PGJyPg0KJmd0OyBTdWJqZWN0OiBQYXJ0aWFsbHkgUmVsaWFibGUgTWVzc2FnZSBTdHJlYW08
YnI+DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCiZndDs8YnI+DQomZ3Q7IEnigJl2ZSBqdXN0IHVwbG9h
ZGVkIGEgbmV3IGRyYWZ0IGZvciBwYXJ0aWFsbHkgcmVsaWFibGUgUVVJQyBzdHJlYW1zLiZuYnNw
OyBOb3RlOiB0aGlzIGZlYXR1cmUgaXMgbGlrZWx5IG5vdCBpbiBzY29wZSBmb3IgVjEsIGJ1dCBp
dCBjYW4gYmUgYW4gZXh0ZW5zaW9uIGZvciBWMSBhbmQvb3IgYSBwYXJ0IG9mIFYyLjxicj4NCiZn
dDs8YnI+DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCiZndDsgVGhlIG5ldyB2ZXJzaW9uIDAzICg8YSBo
cmVmPSJodHRwczovL3VybGRlZmVuc2UucHJvb2Zwb2ludC5jb20vdjIvdXJsP3U9aHR0cHMtM0Ff
X3Rvb2xzLmlldGYub3JnX2h0bWxfZHJhZnQtMkRsdWJhc2hldi0yRHF1aWMtMkRwYXJ0aWFsLTJE
cmVsaWFiaWxpdHktMkQwMyZhbXA7ZD1Ed0lGYVEmYW1wO2M9NVZEMFJUdE5sVGgzeWNkNDFiM01V
dyZhbXA7cj1DMHNVby1MRk5CYVlmeW9hQ3NmNlRBJmFtcDttPXl5UnBiZTE0a1RZZ1k0MTNnalZr
T2FsV0VfVUMzeFllcktwSnFTOEhpUW8mYW1wO3M9WFoyOTV4aVpzTjExeVA4R0xjZE1zMWpmN3ow
YjJfV2hpSXhNTExvclpYbyZhbXA7ZT0iPmh0dHBzOi8vdXJsZGVmZW5zZS4uLnByb29mcG9pbnQu
Y29tL3YyL3VybD91PWh0dHBzLTNBX190b29scy5pZXRmLm9yZ19odG1sX2RyYWZ0LTJEbHViYXNo
ZXYtMkRxdWljLTJEcGFydGlhbC0yRHJlbGlhYmlsaXR5LTJEMDMmYW1wO2Q9RHdJRmFRJmFtcDtj
PTVWRDBSVHRObFRoM3ljZDQxYjNNVXcmYW1wO3I9QzBzVW8tTEZOQmFZZnlvYUNzZjZUQSZhbXA7
bT15eVJwYmUxNGtUWWdZNDEzZ2pWa09hbFdFX1VDM3hZZXJLcEpxUzhIaVFvJmFtcDtzPVhaMjk1
eGlac04xMXlQOEdMY2RNczFqZjd6MGIyX1doaUl4TUxMb3JaWG8mYW1wO2U9PC9hPikNCiBubyBs
b25nZXIgbmVlZHMgY29tcGxleCBmbG93IGNvbnRyb2wgY2hhbmdlcyBhbmQgcmVtb3ZlcyB0aGUg
bmVlZCB0byB0cmFuc21pdCBtdWx0aXBsZSBmcmFtZXMgaW4gdGhlIHNhbWUgcGFja2V0Ljxicj4N
CiZndDs8YnI+DQomZ3Q7PGJyPg0KJmd0Ozxicj4NCiZndDsgSWdvcjxicj4NCiZndDs8YnI+DQom
Z3Q7PGJyPg0KJmd0Ozxicj4NCiZndDsgUC5TLjxicj4NCiZndDs8YnI+DQomZ3Q7Jm5ic3A7Jm5i
c3A7IFRoZXJlIGlzIGFsc28gYSBuZXcgdmVyc2lvbiAwMiwgd2hpY2ggaW5jbHVkZXMgYSBtb3Jl
IGNvbXBsZXggYWxnb3JpdGhtIHdpdGggbW9yZSBmZWF0dXJlcyBhbmQgZGlmZmVyZW50IHRyYWRl
LW9mZnMuJm5ic3A7IEJ1dCBJIHRoaW5rIHZlcnNpb24gMDMgaXMgYSBiZXR0ZXIgbWF0Y2ggZm9y
IHRoZSBuZWVkcyBzbyBmYXIuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_9EFC5C845ABE406AA74C7A9312EF56CFfbcom_--

