
From nobody Fri Nov  1 05:36:49 2019
Return-Path: <anqing.aq@alibaba-inc.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 7004E1208B1; Fri,  1 Nov 2019 05:36: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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 (1024-bit key) header.d=alibaba-inc.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 UzVMByd8c8BH; Fri,  1 Nov 2019 05:36:41 -0700 (PDT)
Received: from out0-158.mail.aliyun.com (out0-158.mail.aliyun.com [140.205.0.158]) (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 7E28812088E; Fri,  1 Nov 2019 05:36:38 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1572611791; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=5t40f410Q2sBhlyzGU3mT2k4wapi9bP4LR4774kJNxc=; b=d8AMljgDhsLHkOzYiXG9YbIGVKGtqN4KQJcC3+R17w9aFkf12HeLqvfmv/8urdDqhxzXbMz/sejBP9cohKCp3eQMiENyrzdHXFREjbm70GKRH79phOuqZgpRsme4i8lf8SGBePkcXkrh+vrAICYw1s04T8Fd5ygozI2/iSNMkbU=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R111e4; CH=green; DM=||false|; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03289; MF=anqing.aq@alibaba-inc.com; NM=1; PH=DW; RN=6; SR=0; TI=W4_5657687_v5ForWebDing_0AB10142_1572598284323_o7001c83d;
Received: from WS-web (anqing.aq@alibaba-inc.com[W4_5657687_v5ForWebDing_0AB10142_1572598284323_o7001c83d]) by e02c03275.eu6 at Fri, 01 Nov 2019 20:36:29 +0800
Date: Fri, 01 Nov 2019 20:36:29 +0800
From: "Qing An" <anqing.aq@alibaba-inc.com>
To: "QUIC" <quic-bounces@ietf.org>, "quic" <quic@ietf.org>, "jri.ietf" <jri.ietf@gmail.com>, "mt" <mt@lowentropy.net>, "mikkelfj" <mikkelfj@gmail.com>
Cc: "=?UTF-8?B?5YiY5aSn6bmPKOm5j+aIkCk=?=" <max.ldp@alibaba-inc.com>
Reply-To: "Qing An" <anqing.aq@alibaba-inc.com>
Message-ID: <69d1a917-b1f9-4142-afb0-f5c67abe7334.anqing.aq@alibaba-inc.com>
Subject: =?UTF-8?B?UmU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQ=?=
X-Mailer: [Alimail-Mailagent revision 2765257][W4_5657687][v5ForWebDing][Chrome]
MIME-Version: 1.0
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com> <BN6PR2201MB1700F72F3DC8F6C3CF79902CDA600@BN6PR2201MB1700.namprd22.prod.outlook.com>, <bd15f357-8e7a-42af-bf28-79f7177da385@www.fastmail.com> <f55efb80-1a95-4190-84e5-b81948a7f081.anqing.aq@alibaba-inc.com>, <BN6PR2201MB17005571E88F1C68769091A3DA630@BN6PR2201MB1700.namprd22.prod.outlook.com>
x-aliyun-mail-creator: W4_5657687_v5ForWebDing_NTMTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTVfMCkgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzc4LjAuMzkwNC43MCBTYWZhcmkvNTM3LjM2XQ
In-Reply-To: <BN6PR2201MB17005571E88F1C68769091A3DA630@BN6PR2201MB1700.namprd22.prod.outlook.com>
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_18201_4eb87940_5dbc26cd_352c27"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/iR7VDgk1NHOKc6bLre5yx5zgMvc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 12:36:48 -0000

------=ALIBOUNDARY_18201_4eb87940_5dbc26cd_352c27
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

CklmIHNvLCBmb3IgdGhlIGZpcnN0IGNvbm5lY3Rpb24gYmV0d2VlbiBjbGllbnQgYW5kIHNlcnZl
ciwgc2VydmVyIGNhbiBjaG9vc2UgdG8gZWxpbWluYXRlIHRoZSB1c2Ugb2YgUmV0cnkgcGFja2V0
IGZvciB0b2tlbiBkZWxpdmVyeSwgYW5kIHJlbHkgb24gaGFuZHNoYWtlIGVuY3J5cHRpb24gbGF5
ZXIgdG8gcHJvdmUgcmV0dXJuIHJvdXRhYmlsaXR5LiAgSW4gYWRkaXRpb24sIE5ld19Ub2tlbiBm
cmFtZSBpcyB1c2VkIGJ5IHNlcnZlciwgdmlhIGkuZS4gdGhlIEluaXRpYWwgcGFja2V0LCB0byBw
cm92aWRlIHRoZSBjbGllbnQgd2l0aCBhbiBhZGRyZXNzIHZhbGlkYXRpb24gdG9rZW4gdGhhdCBj
YW4gYmUgdXNlZCB0byB2YWxpZGF0ZSBmdXR1cmUgY29ubmVjdGlvbnMuCgpJdCBjYW4gZW5oYW5j
ZSB0aGUgZXhwZXJpZW5jZSBpbiBjbGllbnQgc2lkZSBmb3IgdGhlIGZpcnN0IGNvbm5lY3Rpb24g
ZXN0YWJsaXNobWVudC4KCkkgc3VibWl0dGVkIHRoZSBkcmFmdCwgaHR0cHM6Ly9kYXRhdHJhY2tl
ci5pZXRmLm9yZy9kb2MvZHJhZnQtYW4tZmFzdC1hZGRyZXNzLXZhbGlkYXRpb24vCgpRaW5nCgoK
CgotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0KRnJvbTpNaWtlIEJpc2hvcCA8bWJpc2hvcEBldmVxdWVmb3UuYmU+ClNlbmQg
VGltZToyMDE55bm0MTHmnIgx5pelKOaYn+acn+S6lCkgMDA6MDYKVG865a6J5YuNKOiOs+mAuCkg
PGFucWluZy5hcUBhbGliYWJhLWluYy5jb20+OyBxdWljIDxxdWljQGlldGYub3JnPjsganJpLmll
dGYgPGpyaS5pZXRmQGdtYWlsLmNvbT47IG10IDxtdEBsb3dlbnRyb3B5Lm5ldD47IG1pa2tlbGZq
IDxtaWtrZWxmakBnbWFpbC5jb20+ClN1YmplY3Q6UkU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9u
IC0gYWJvdXQKCkFzIE1hcnRpbiBwb2ludGVkIG91dCBpbiB0aGUgZS1tYWlsIHlvdSByZXBsaWVk
IHRvLCBpZiB0aGUgc2VydmVyIGlzIHdpbGxpbmcgdG8gbWFpbnRhaW4gc3RhdGUsIGFueSBwYWNr
ZXQgYXQgdGhlIEhhbmRzaGFrZSBlbmNyeXB0aW9uIGxheWVyIHByb3ZlcyByZXR1cm4gcm91dGFi
aWxpdHkuICBUaGVyZSBzZWVtcyB0byBiZSBubyBuZWVkIGZvciBhIHNlcGFyYXRlIGFkZHJlc3Mg
dmFsaWRhdGlvbiBtZWNoYW5pc20gaWYgdGhlIHNlcnZlciBpcyB3aWxsaW5nIHRvIHByb2NlZWQg
d2l0aCB0aGUgaGFuZHNoYWtlLgpGcm9tOiBRVUlDIDxxdWljLWJvdW5jZXNAaWV0Zi5vcmc+IE9u
IEJlaGFsZiBPZiAgUWluZyBBbgpTZW50OiBUaHVyc2RheSwgT2N0b2JlciAzMSwgMjAxOSA4OjU2
IEFNClRvOiBxdWljIDxxdWljQGlldGYub3JnPjsganJpLmlldGYgPGpyaS5pZXRmQGdtYWlsLmNv
bT47IG10IDxtdEBsb3dlbnRyb3B5Lm5ldD47IG1pa2tlbGZqIDxtaWtrZWxmakBnbWFpbC5jb20+
ClN1YmplY3Q6IFJlOiBGYXN0IEFkZHJlc3MgVmFsaWRhdGlvbiAtIGFib3V0CgoKVG8gY2xhcmlm
eSwgdGhlIHByb3Bvc2FsIGlzIG5vdCB0byByZXBsYWNlIHRoZSBleGlzdGluZyBSZXRyeS1iYXNl
ZCB2YWxpZGF0aW9uLCBidXQgdG8gcHJvdmlkZSBhbm90aGVyIG9wdGlvbiBmb3Igc2VydmVyIHRv
IGRvIHRoZSBjbGllbnQgdmFsaWRhdGlvbi4KCkkgdW5kZXJzdGFuZCB0aGF0IGluIHNlcnZlciBz
aWRlLCBleGNoYW5naW5nIHRoZSB0b2tlbiBhdCB0aGUgSGFuZHNoYWtlIGVuY3J5cHRpb24gbGV2
ZWwgd2lsbCBtYWtlIHRoZSBzZXJ2ZXIgc3RhcnQgdG8gbWFpbnRhaW4gaGFuZHNoYWtlIHN0YXRl
cy4gQnV0IGluIGNsaWVudCBzaWRlLCBpdCBjYW4gYWNjZWxlcmF0ZSB0aGUgY29ubmVjdGlvbiBl
c3RhYmxpc2htZW50IGZyb20gY2xpZW50IHRvIHNlcnZlci4KCkFuZCBpdCBpcyB0aGUgc2VydmVy
J3MgZGVjaXNpb24gd2hldGhlciB0byBleGNoYW5nZSB0b2tlbiBpbiBSZXRyeSBvciBpbiBIYW5k
c2hha2UuIElmIHNlcnZlciBjaG9vc2VzIHRvIGFjY2VwdCB0aGUgY29zdCBicm91Z2h0IGJ5IHRv
a2VuIGV4Y2hhbmdpbmcgaW4gSGFuZHNoYWtlLCBpdCB3aWxsIGJyaW5nIG1vcmUgZW5oYW5jZWQg
ZXhwZXJpZW5jZSBpbiBjbGllbnQgc2lkZS4KCgpCUiwKUWluZwoKCi0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQpGcm9tOk1h
cnRpbiBUaG9tc29uIDxtdEBsb3dlbnRyb3B5Lm5ldD4KU2VuZCBUaW1lOjIwMTnlubQxMOaciDMx
5pelKOaYn+acn+WbmykgMDY6MDcKVG86cXVpYyA8cXVpY0BpZXRmLm9yZz4KU3ViamVjdDpSZTog
RmFzdCBBZGRyZXNzIFZhbGlkYXRpb24gLSBhYm91dAoKQWxzbyBub3RlIHRoYXQgZXhjaGFuZ2Ug
b2YgSGFuZHNoYWtlIHBhY2tldHMgcHJvdmlkZXMgcHJvb2Ygb2YgcmV0dXJuIHJvdXRlYWJpbGl0
eSB2aWEgdGhlIHVzZSBvZiB0aGUgZW5jcnlwdGlvbiBrZXlzLCBzbyB0aGVyZSBpcyBubyBuZWVk
IHRvIGV4Y2hhbmdlIHRva2VucyBhdCB0aGF0IGxldmVsLgoKIE9uIFRodSwgT2N0IDMxLCAyMDE5
LCBhdCAwMzoyOSwgTWlrZSBCaXNob3Agd3JvdGU6CiA+ICAKID4gVGhlIGFkdmFudGFnZSBvZiB1
c2luZyBSZXRyeSwgaG93ZXZlciwgaXMgdGhhdCB0aGUgc2VydmVyIGlzIGFibGUgdG8gCiA+IGtl
ZXAgbWluaW1hbCAoaWYgYW55KSBzdGF0ZSBhYm91dCB0aGUgY2xpZW50LiBFeGNoYW5naW5nIHRo
ZSB0b2tlbiBhdCAKID4gdGhlIEhhbmRzaGFrZSBlbmNyeXB0aW9uIGxldmVsIG1lYW5zIHRoZSBz
ZXJ2ZXIgaXMgYWxyZWFkeSBkb2luZyB3b3JrIAogPiBhbmQgbWFpbnRhaW5pbmcgc3RhdGUgaW4g
b3JkZXIgdG8gcHJvY2VzcyB0aGUgaGFuZHNoYWtlLCB3aGljaCBpcyAKID4gZXhhY3RseSB3aGF0
IHRoZSBzZXJ2ZXIgaXMgdHJ5aW5nIHRvIGF2b2lkLgogPiAKID4gCiA+ICpGcm9tOiogUVVJQyA8
cXVpYy1ib3VuY2VzQGlldGYub3JnPiAqT24gQmVoYWxmIE9mICogUWluZyBBbgogPiAqU2VudDoq
IFdlZG5lc2RheSwgT2N0b2JlciAzMCwgMjAxOSA5OjQxIEFNCiA+ICpUbzoqIHF1aWMgPHF1aWNA
aWV0Zi5vcmc+OyBqcmkuaWV0ZiA8anJpLmlldGZAZ21haWwuY29tPjsgbXQgCiA+IDxtdEBsb3dl
bnRyb3B5Lm5ldD4KID4gKkNjOiog5YiY5aSn6bmPKOm5j+aIkCkgPG1heC5sZHBAYWxpYmFiYS1p
bmMuY29tPgogPiAqU3ViamVjdDoqIEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQKID4g
CiA+IAogPiAKID4gCiA+IEhpIE1hcnRpbiwgSmFuYSwgCiA+IAogPiBJIHJlYWQgdGhyb3VnaCBo
dHRwczovL3d3dy5pZXRmLm9yZy9pZC9kcmFmdC1pZXRmLXF1aWMtdHJhbnNwb3J0LTIzLnR4dCAK
ID4gYW5kIGhhdmUgYSBmZXcgY29tbWVudHMgYW5kIGlkZWFzIHRvIGRpc2N1c3MuCiA+IAogPiAK
ID4gW1FVSUMtVHJhbnNdIGRlZmluZXMgYSB0b2tlbiBiYXNlZCBzY2hlbWUgdG8gZmFjaWxpdGF0
ZSBhZGRyZXNzIAogPiB2YWxpZGF0aW9uIG9mIGEgY2xpZW50LiBUaGUgdG9rZW4gTVVTVCBiZSBj
b3ZlcmVkIGJ5IGludGVncml0eSAKID4gcHJvdGVjdGlvbiBhZ2FpbnN0IG1vZGlmaWNhdGlvbiBv
ciBmYWxzaWZpY2F0aW9uIGJ5IGNsaWVudHMuIFRoZSBzZXJ2ZXIgCiA+IHJlbWVtYmVycyB0aGUg
dmFsdWUgaXQgc2VuZHMgdG8gY2xpZW50cyBhbmQgdmFsaWRhdGVzIHRoZSB0b2tlbiBzZW50IAog
PiBiYWNrIGZyb20gYSBjbGllbnQuIEluIGl0cyBkZXNpZ24sIFJldHJ5IHBhY2tldCBpcyB1c2Vk
IHRvIGRlbGl2ZXIgdGhlIAogPiB0b2tlbiB0byBhIGNsaWVudCB3aGljaCBhZGRyZXNzIGhhcyBu
b3QgeWV0IGJlZW4gdmFsaWRhdGVkLiBJdCB2b2lkcyAKID4gdGhlIGZpcnN0IHRyYW5zbWlzc2lv
biBvZiB0aGUgSW5pdGlhbCBwYWNrZXQgc2VudCBieSB0aGUgY2xpZW50LCBhbmQgCiA+IHRyaWdn
ZXJzIGEgc2Vjb25kIEluaXRpYWwgcGFja2V0IHRvIGJlIHNlbnQgd2l0aCB0aGUgdG9rZW4uIFRo
ZSAKID4gZXhjaGFuZ2Ugb2YgdG9rZW4gd2lsbCBjYXVzZSBsb25nZXIgY29ubmVjdGlvbiBlc3Rh
Ymxpc2htZW50IGRlbGF5IGZvciAKID4gYSBjbGllbnQuCiA+IAogPiAKID4gVG8gaW1wcm92ZSB0
aGUgZWZmaWNpZW5jeSBvZiBhZGRyZXNzIHZhbGlkYXRpb24gZHVyaW5nIGhhbmRzaGFrZSwgb25l
IAogPiBpZGVhIGlzIHRoYXQgdGhlIHNhbWUgdG9rZW4gY2FuIGJlIGV4Y2hhbmdlZCB2aWEgYSBk
aWZmZXJlbnQgY29udGFpbmVyIAogPiBpLmUuIHRoZSBIYW5kc2hha2UgcGFja2V0LCB0aGF0IGVs
aW1pbmF0ZXMgdGhlIHVzZSBvZiBSZXRyeSBwYWNrZXQgZm9yIAogPiB0b2tlbiBkZWxpdmVyeS4g
CiA+IAogPiAKID4gSSBhbSB3b3JraW5nIG9uIHRoZSBjb21wbGV0ZSBkcmFmdCBhbmQgd2lsbCBz
dWJtaXQgaXQgYnkgRnJpZGF5LiBCZWZvcmUgCiA+IHRoYXQsIGhvcGUgdGhpcyBjYW4gYmUgZGlz
Y3Vzc2VkIGluIGVtYWlsIGZpcnN0LgogPiAKID4gCiA+IEJSLAogPiAKID4gUWluZyBBbgogPgoK
Cg==
------=ALIBOUNDARY_18201_4eb87940_5dbc26cd_352c27
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64

PGRpdiBjbGFzcz0iX19hbGl5dW5fZW1haWxfYm9keV9ibG9jayI+PGRpdiAgc3R5bGU9ImxpbmUt
aGVpZ2h0OjEuNztmb250LWZhbWlseTpUYWhvbWEsQXJpYWwsU1RIZWl0aSxTaW1TdW47Zm9udC1z
aXplOjE0LjBweDtjb2xvcjojMDAwMDAwOyI+PGRpdiAgc3R5bGU9ImNsZWFyOmJvdGg7Ij48YnIg
PjwvZGl2PjxkaXYgIHN0eWxlPSJjbGVhcjpib3RoOyI+SWYgc28sIGY8c3BhbiA+b3ImbmJzcDt0
aGUmbmJzcDtmaXJzdDwvc3Bhbj4mbmJzcDtjb25uZWN0aW9uJm5ic3A7YmV0d2VlbiZuYnNwO2Ns
aWVudCZuYnNwO2FuZCZuYnNwO3NlcnZlciwgc2VydmVyIGNhbiBjaG9vc2UgdG8gZWxpbWluYXRl
Jm5ic3A7dGhlJm5ic3A7dXNlJm5ic3A7b2YmbmJzcDtSZXRyeSBwYWNrZXQmbmJzcDtmb3ImbmJz
cDt0b2tlbiZuYnNwO2RlbGl2ZXJ5LCBhbmQgcmVseSZuYnNwO29uJm5ic3A7aGFuZHNoYWtlJm5i
c3A7ZW5jcnlwdGlvbiZuYnNwO2xheWVyJm5ic3A7dG8gcHJvdmUmbmJzcDtyZXR1cm4gcm91dGFi
aWxpdHkuJm5ic3A7IEluJm5ic3A7YWRkaXRpb24sIE5ld19Ub2tlbiBmcmFtZSBpcyZuYnNwO3Vz
ZWQmbmJzcDtieSBzZXJ2ZXIsJm5ic3A7dmlhJm5ic3A7aS5lLiZuYnNwO3RoZSZuYnNwO0luaXRp
YWwmbmJzcDtwYWNrZXQsJm5ic3A7dG8mbmJzcDtwcm92aWRlJm5ic3A7dGhlJm5ic3A7Y2xpZW50
Jm5ic3A7d2l0aCZuYnNwO2FuIGFkZHJlc3MmbmJzcDt2YWxpZGF0aW9uJm5ic3A7dG9rZW4mbmJz
cDt0aGF0Jm5ic3A7Y2FuJm5ic3A7YmUmbmJzcDt1c2VkJm5ic3A7dG8mbmJzcDt2YWxpZGF0ZSZu
YnNwO2Z1dHVyZTxzcGFuID4mbmJzcDtjb25uZWN0aW9ucy48L3NwYW4+PC9kaXY+PGRpdiAgc3R5
bGU9ImNsZWFyOmJvdGg7Ij48c3BhbiA+PGJyID48L3NwYW4+PC9kaXY+PGRpdiAgc3R5bGU9ImNs
ZWFyOmJvdGg7Ij48c3BhbiA+SXQgY2FuIGVuaGFuY2UgdGhlIGV4cGVyaWVuY2UgaW4gY2xpZW50
IHNpZGUgZm9yIHRoZSBmaXJzdCBjb25uZWN0aW9uIGVzdGFibGlzaG1lbnQuPC9zcGFuPjwvZGl2
PjxkaXYgIHN0eWxlPSJjbGVhcjpib3RoOyI+PHNwYW4gPjxiciA+PC9zcGFuPjwvZGl2PjxkaXYg
IHN0eWxlPSJjbGVhcjpib3RoOyI+PHNwYW4gPkkgc3VibWl0dGVkIHRoZSBkcmFmdCwmbmJzcDs8
YSAgaHJlZj0iaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtYW4tZmFzdC1h
ZGRyZXNzLXZhbGlkYXRpb24vIj5odHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFm
dC1hbi1mYXN0LWFkZHJlc3MtdmFsaWRhdGlvbi88L2E+PC9zcGFuPjwvZGl2PjxkaXYgIHN0eWxl
PSJjbGVhcjpib3RoOyI+PHNwYW4gPjxiciA+PC9zcGFuPjwvZGl2PjxkaXYgIHN0eWxlPSJjbGVh
cjpib3RoOyI+PHNwYW4gPlFpbmc8L3NwYW4+PC9kaXY+PGRpdiAgc3R5bGU9ImNsZWFyOmJvdGg7
Ij48L2Rpdj48ZGl2ICBzdHlsZT0iY2xlYXI6Ym90aDsiPjxiciA+PC9kaXY+PGRpdiAgc3R5bGU9
ImNsZWFyOmJvdGg7Ij48YnIgPjwvZGl2PjxkaXYgIHN0eWxlPSJjbGVhcjpib3RoOyI+PGJyID48
L2Rpdj48YmxvY2txdW90ZSAgX3F1b3RlPSIxIiBzdHlsZT0ibWFyZ2luLXJpZ2h0Oi4wcHg7bWFy
Z2luLXRvcDouMHB4O21hcmdpbi1ib3R0b206LjBweDtmb250LWZhbWlseTpUYWhvbWEsQXJpYWws
U1RIZWl0aSxTaW1TdW47Zm9udC1zaXplOjE0LjBweDtjb2xvcjojMDAwMDAwOyI+PGRpdiAgc3R5
bGU9ImNsZWFyOmJvdGg7Ij4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08L2Rpdj48ZGl2ICBzdHlsZT0iY2xlYXI6Ym90aDsi
PkZyb206TWlrZSBCaXNob3AgJmx0O21iaXNob3BAZXZlcXVlZm91LmJlJmd0OzwvZGl2PjxkaXYg
IHN0eWxlPSJjbGVhcjpib3RoOyI+U2VuZCBUaW1lOjIwMTnlubQxMeaciDHml6Uo5pif5pyf5LqU
KSAwMDowNjwvZGl2PjxkaXYgIHN0eWxlPSJjbGVhcjpib3RoOyI+VG865a6J5YuNKOiOs+mAuCkg
Jmx0O2FucWluZy5hcUBhbGliYWJhLWluYy5jb20mZ3Q7OyBxdWljICZsdDtxdWljQGlldGYub3Jn
Jmd0OzsganJpLmlldGYgJmx0O2pyaS5pZXRmQGdtYWlsLmNvbSZndDs7IG10ICZsdDttdEBsb3dl
bnRyb3B5Lm5ldCZndDs7IG1pa2tlbGZqICZsdDttaWtrZWxmakBnbWFpbC5jb20mZ3Q7PC9kaXY+
PGRpdiAgc3R5bGU9ImNsZWFyOmJvdGg7Ij5TdWJqZWN0OlJFOiBGYXN0IEFkZHJlc3MgVmFsaWRh
dGlvbiAtIGFib3V0PC9kaXY+PGRpdiAgc3R5bGU9ImNsZWFyOmJvdGg7Ij48YnIgPjwvZGl2Pjxk
aXYgIGNsYXNzPSJXb3JkU2VjdGlvbjEiPjxwICBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFy
Z2luOi4wcHg7Zm9udC1zaXplOjE0LjdweDtmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7
Ij5BcyBNYXJ0aW4gcG9pbnRlZCBvdXQgaW4gdGhlIGUtbWFpbCB5b3UgcmVwbGllZCB0bywgaWYg
dGhlIHNlcnZlciBpcyB3aWxsaW5nIHRvIG1haW50YWluIHN0YXRlLCBhbnkgcGFja2V0IGF0IHRo
ZSBIYW5kc2hha2UgZW5jcnlwdGlvbiBsYXllciBwcm92ZXMgcmV0dXJuIHJvdXRhYmlsaXR5LiZu
YnNwOyBUaGVyZSBzZWVtcyB0byBiZSBubyBuZWVkIGZvciBhIHNlcGFyYXRlIGFkZHJlc3MgdmFs
aWRhdGlvbiBtZWNoYW5pc20KIGlmIHRoZSBzZXJ2ZXIgaXMgd2lsbGluZyB0byBwcm9jZWVkIHdp
dGggdGhlIGhhbmRzaGFrZS48L3A+PHAgIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46
LjBweDtmb250LXNpemU6MTQuN3B4O2ZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjsiPiZu
YnNwOzwvcD48cCAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjouMHB4O2ZvbnQtc2l6
ZToxNC43cHg7Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyI+PGIgPkZyb206PC9iPiBR
VUlDICZsdDtxdWljLWJvdW5jZXNAaWV0Zi5vcmcmZ3Q7IDxiID5PbiBCZWhhbGYgT2YgPC9iPgpR
aW5nIEFuPGJyID48YiA+U2VudDo8L2I+IFRodXJzZGF5LCBPY3RvYmVyIDMxLCAyMDE5IDg6NTYg
QU08YnIgPjxiID5Ubzo8L2I+IHF1aWMgJmx0O3F1aWNAaWV0Zi5vcmcmZ3Q7OyBqcmkuaWV0ZiAm
bHQ7anJpLmlldGZAZ21haWwuY29tJmd0OzsgbXQgJmx0O210QGxvd2VudHJvcHkubmV0Jmd0Ozsg
bWlra2VsZmogJmx0O21pa2tlbGZqQGdtYWlsLmNvbSZndDs8YnIgPjxiID5TdWJqZWN0OjwvYj4g
UmU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQ8L3A+PHAgIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtYXJnaW46LjBweDtmb250LXNpemU6MTQuN3B4O2ZvbnQtZmFtaWx5OkNhbGli
cmksc2Fucy1zZXJpZjsiPiZuYnNwOzwvcD48ZGl2ID48ZGl2ID48cCAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1hcmdpbjouMHB4O2ZvbnQtc2l6ZToxNC43cHg7Zm9udC1mYW1pbHk6Q2FsaWJy
aSxzYW5zLXNlcmlmOyI+PHNwYW4gIHN0eWxlPSJmb250LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5
OlRhaG9tYSxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrOyI+Jm5ic3A7PC9zcGFuPjwvcD48L2Rpdj48
ZGl2ID48cCAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjouMHB4O2ZvbnQtc2l6ZTox
NC43cHg7Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyI+PHNwYW4gIHN0eWxlPSJmb250
LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5OlRhaG9tYSxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrOyI+
Jm5ic3A7PC9zcGFuPjwvcD48L2Rpdj48ZGl2ID48cCAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1hcmdpbjouMHB4O2ZvbnQtc2l6ZToxNC43cHg7Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNl
cmlmOyI+PHNwYW4gIHN0eWxlPSJmb250LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5OlRhaG9tYSxz
YW5zLXNlcmlmO2NvbG9yOmJsYWNrOyI+VG8gY2xhcmlmeSwgdGhlIHByb3Bvc2FsIGlzIG5vdCB0
byByZXBsYWNlIHRoZSBleGlzdGluZyBSZXRyeS1iYXNlZCB2YWxpZGF0aW9uLCBidXQgdG8gcHJv
dmlkZSBhbm90aGVyIG9wdGlvbiBmb3Igc2VydmVyIHRvIGRvIHRoZSBjbGllbnQgdmFsaWRhdGlv
bi48L3NwYW4+PC9wPjwvZGl2PjxkaXYgPjxwICBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFy
Z2luOi4wcHg7Zm9udC1zaXplOjE0LjdweDtmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7
Ij48c3BhbiAgc3R5bGU9ImZvbnQtc2l6ZToxNC4wcHg7Zm9udC1mYW1pbHk6VGFob21hLHNhbnMt
c2VyaWY7Y29sb3I6YmxhY2s7Ij4mbmJzcDs8L3NwYW4+PC9wPjwvZGl2PjxkaXYgPjxwICBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOi4wcHg7Zm9udC1zaXplOjE0LjdweDtmb250LWZh
bWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7Ij48c3BhbiAgc3R5bGU9ImZvbnQtc2l6ZToxNC4wcHg7
Zm9udC1mYW1pbHk6VGFob21hLHNhbnMtc2VyaWY7Y29sb3I6YmxhY2s7Ij5JIHVuZGVyc3RhbmQg
dGhhdCBpbiBzZXJ2ZXIgc2lkZSwgZTxzcGFuICBzdHlsZT0iYmFja2dyb3VuZDp3aGl0ZTsiPnhj
aGFuZ2luZyZuYnNwO3RoZSZuYnNwO3Rva2VuJm5ic3A7YXQmbmJzcDt0aGUmbmJzcDtIYW5kc2hh
a2UmbmJzcDtlbmNyeXB0aW9uJm5ic3A7bGV2ZWwgd2lsbCBtYWtlIHRoZSBzZXJ2ZXIgc3RhcnQg
dG8gbWFpbnRhaW4gaGFuZHNoYWtlCiBzdGF0ZXMuIEJ1dCBpbiBjbGllbnQgc2lkZSwgaXQgY2Fu
IGFjY2VsZXJhdGUgdGhlIGNvbm5lY3Rpb24gZXN0YWJsaXNobWVudCBmcm9tIGNsaWVudCB0byBz
ZXJ2ZXIuPC9zcGFuPjwvc3Bhbj48L3A+PC9kaXY+PGRpdiA+PHAgIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtYXJnaW46LjBweDtmb250LXNpemU6MTQuN3B4O2ZvbnQtZmFtaWx5OkNhbGlicmks
c2Fucy1zZXJpZjsiPjxzcGFuICBzdHlsZT0iZm9udC1zaXplOjE0LjBweDtmb250LWZhbWlseTpU
YWhvbWEsc2Fucy1zZXJpZjtjb2xvcjpibGFjazsiPiZuYnNwOzwvc3Bhbj48L3A+PC9kaXY+PGRp
diA+PHAgIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46LjBweDtmb250LXNpemU6MTQu
N3B4O2ZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjsiPjxzcGFuICBzdHlsZT0iZm9udC1z
aXplOjE0LjBweDtmb250LWZhbWlseTpUYWhvbWEsc2Fucy1zZXJpZjtjb2xvcjpibGFjaztiYWNr
Z3JvdW5kOndoaXRlOyI+QW5kIGl0IGlzIHRoZSBzZXJ2ZXIncyBkZWNpc2lvbiB3aGV0aGVyIHRv
IGV4Y2hhbmdlIHRva2VuIGluIFJldHJ5IG9yIGluIEhhbmRzaGFrZS4gSWYgc2VydmVyIGNob29z
ZXMgdG8gYWNjZXB0IHRoZSBjb3N0IGJyb3VnaHQgYnkgdG9rZW4gZXhjaGFuZ2luZwogaW4gSGFu
ZHNoYWtlLCBpdCB3aWxsIGJyaW5nIG1vcmUgZW5oYW5jZWQgZXhwZXJpZW5jZSBpbiBjbGllbnQg
c2lkZS48L3NwYW4+PHNwYW4gIHN0eWxlPSJmb250LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5OlRh
aG9tYSxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrOyI+PC9zcGFuPjwvcD48L2Rpdj48ZGl2ID48cCAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjouMHB4O2ZvbnQtc2l6ZToxNC43cHg7Zm9u
dC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyI+PHNwYW4gIHN0eWxlPSJmb250LXNpemU6MTQu
MHB4O2ZvbnQtZmFtaWx5OlRhaG9tYSxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrOyI+Jm5ic3A7PC9z
cGFuPjwvcD48L2Rpdj48ZGl2ID48cCAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjou
MHB4O2ZvbnQtc2l6ZToxNC43cHg7Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyI+PHNw
YW4gIHN0eWxlPSJmb250LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5OlRhaG9tYSxzYW5zLXNlcmlm
O2NvbG9yOmJsYWNrOyI+Jm5ic3A7PC9zcGFuPjwvcD48L2Rpdj48ZGl2ID48cCAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1hcmdpbjouMHB4O2ZvbnQtc2l6ZToxNC43cHg7Zm9udC1mYW1pbHk6
Q2FsaWJyaSxzYW5zLXNlcmlmOyI+PHNwYW4gIHN0eWxlPSJmb250LXNpemU6MTQuMHB4O2ZvbnQt
ZmFtaWx5OlRhaG9tYSxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrO2JhY2tncm91bmQ6d2hpdGU7Ij5C
Uiw8L3NwYW4+PHNwYW4gIHN0eWxlPSJmb250LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5OlRhaG9t
YSxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrOyI+PC9zcGFuPjwvcD48L2Rpdj48ZGl2ID48cCAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjouMHB4O2ZvbnQtc2l6ZToxNC43cHg7Zm9udC1m
YW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyI+PHNwYW4gIHN0eWxlPSJmb250LXNpemU6MTQuMHB4
O2ZvbnQtZmFtaWx5OlRhaG9tYSxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrO2JhY2tncm91bmQ6d2hp
dGU7Ij5RaW5nPC9zcGFuPjxzcGFuICBzdHlsZT0iZm9udC1zaXplOjE0LjBweDtmb250LWZhbWls
eTpUYWhvbWEsc2Fucy1zZXJpZjtjb2xvcjpibGFjazsiPjwvc3Bhbj48L3A+PC9kaXY+PGRpdiA+
PHAgIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46LjBweDtmb250LXNpemU6MTQuN3B4
O2ZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjsiPjxzcGFuICBzdHlsZT0iZm9udC1zaXpl
OjE0LjBweDtmb250LWZhbWlseTpUYWhvbWEsc2Fucy1zZXJpZjtjb2xvcjpibGFjazsiPiZuYnNw
Ozwvc3Bhbj48L3A+PC9kaXY+PGRpdiA+PHAgIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJn
aW46LjBweDtmb250LXNpemU6MTQuN3B4O2ZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjsi
PjxzcGFuICBzdHlsZT0iZm9udC1zaXplOjE0LjBweDtmb250LWZhbWlseTpUYWhvbWEsc2Fucy1z
ZXJpZjtjb2xvcjpibGFjazsiPiZuYnNwOzwvc3Bhbj48L3A+PC9kaXY+PGRpdiAgc3R5bGU9Im1h
cmdpbjoxNC4wcHggLjBweDsiPjxkaXYgPjxwICBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFy
Z2luOi4wcHg7Zm9udC1zaXplOjE0LjdweDtmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7
Ij48c3BhbiAgc3R5bGU9ImZvbnQtc2l6ZToxNC4wcHg7Zm9udC1mYW1pbHk6VGFob21hLHNhbnMt
c2VyaWY7Y29sb3I6YmxhY2s7Ij4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08L3NwYW4+PC9wPjwvZGl2PjxkaXYgPjxwICBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOi4wcHg7Zm9udC1zaXplOjE0LjdweDtmb250
LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7Ij48c3BhbiAgc3R5bGU9ImZvbnQtc2l6ZToxNC4w
cHg7Zm9udC1mYW1pbHk6VGFob21hLHNhbnMtc2VyaWY7Y29sb3I6YmxhY2s7Ij5Gcm9tOk1hcnRp
biBUaG9tc29uICZsdDs8YSAgaHJlZj0ibWFpbHRvOm10QGxvd2VudHJvcHkubmV0IiB0YXJnZXQ9
Il9ibGFuayIgc3R5bGU9ImNvbG9yOiMwMDAwZmY7dGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZSBz
b2xpZCAjMDAwMGZmOyI+bXRAbG93ZW50cm9weS5uZXQ8L2E+Jmd0Ozwvc3Bhbj48L3A+PC9kaXY+
PGRpdiA+PHAgIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46LjBweDtmb250LXNpemU6
MTQuN3B4O2ZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjsiPjxzcGFuICBzdHlsZT0iZm9u
dC1zaXplOjE0LjBweDtmb250LWZhbWlseTpUYWhvbWEsc2Fucy1zZXJpZjtjb2xvcjpibGFjazsi
PlNlbmQgVGltZToyMDE5PC9zcGFuPjxzcGFuICBzdHlsZT0iZm9udC1zaXplOjE0LjBweDtmb250
LWZhbWlseTpNUyBHb3RoaWM7Y29sb3I6YmxhY2s7Ij7lubQ8L3NwYW4+PHNwYW4gIHN0eWxlPSJm
b250LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5OlRhaG9tYSxzYW5zLXNlcmlmO2NvbG9yOmJsYWNr
OyI+MTA8L3NwYW4+PHNwYW4gIHN0eWxlPSJmb250LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5Ok1T
IEdvdGhpYztjb2xvcjpibGFjazsiPuaciDwvc3Bhbj48c3BhbiAgc3R5bGU9ImZvbnQtc2l6ZTox
NC4wcHg7Zm9udC1mYW1pbHk6VGFob21hLHNhbnMtc2VyaWY7Y29sb3I6YmxhY2s7Ij4zMTwvc3Bh
bj48c3BhbiAgc3R5bGU9ImZvbnQtc2l6ZToxNC4wcHg7Zm9udC1mYW1pbHk6TVMgR290aGljO2Nv
bG9yOmJsYWNrOyI+5pelPC9zcGFuPjxzcGFuICBzdHlsZT0iZm9udC1zaXplOjE0LjBweDtmb250
LWZhbWlseTpUYWhvbWEsc2Fucy1zZXJpZjtjb2xvcjpibGFjazsiPig8L3NwYW4+PHNwYW4gIHN0
eWxlPSJmb250LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5Ok1TIEdvdGhpYztjb2xvcjpibGFjazsi
PuaYn+acn+Wbmzwvc3Bhbj48c3BhbiAgc3R5bGU9ImZvbnQtc2l6ZToxNC4wcHg7Zm9udC1mYW1p
bHk6VGFob21hLHNhbnMtc2VyaWY7Y29sb3I6YmxhY2s7Ij4pCiAwNjowNzwvc3Bhbj48L3A+PC9k
aXY+PGRpdiA+PHAgIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46LjBweDtmb250LXNp
emU6MTQuN3B4O2ZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjsiPjxzcGFuICBzdHlsZT0i
Zm9udC1zaXplOjE0LjBweDtmb250LWZhbWlseTpUYWhvbWEsc2Fucy1zZXJpZjtjb2xvcjpibGFj
azsiPlRvOnF1aWMgJmx0OzxhICBocmVmPSJtYWlsdG86cXVpY0BpZXRmLm9yZyIgdGFyZ2V0PSJf
YmxhbmsiIHN0eWxlPSJjb2xvcjojMDAwMGZmO3RleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmUgc29s
aWQgIzAwMDBmZjsiPnF1aWNAaWV0Zi5vcmc8L2E+Jmd0Ozwvc3Bhbj48L3A+PC9kaXY+PGRpdiA+
PHAgIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46LjBweDtmb250LXNpemU6MTQuN3B4
O2ZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjsiPjxzcGFuICBzdHlsZT0iZm9udC1zaXpl
OjE0LjBweDtmb250LWZhbWlseTpUYWhvbWEsc2Fucy1zZXJpZjtjb2xvcjpibGFjazsiPlN1Ympl
Y3Q6UmU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQ8L3NwYW4+PC9wPjwvZGl2Pjxk
aXYgPjxwICBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOi4wcHg7Zm9udC1zaXplOjE0
LjdweDtmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7Ij48c3BhbiAgc3R5bGU9ImZvbnQt
c2l6ZToxNC4wcHg7Zm9udC1mYW1pbHk6VGFob21hLHNhbnMtc2VyaWY7Y29sb3I6YmxhY2s7Ij4m
bmJzcDs8L3NwYW4+PC9wPjwvZGl2PjxwICBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2lu
Oi4wcHg7Zm9udC1zaXplOjE0LjdweDtmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7Ij48
c3BhbiAgc3R5bGU9ImZvbnQtc2l6ZToxNC4wcHg7Zm9udC1mYW1pbHk6VGFob21hLHNhbnMtc2Vy
aWY7Y29sb3I6YmxhY2s7Ij5BbHNvJm5ic3A7bm90ZSZuYnNwO3RoYXQmbmJzcDtleGNoYW5nZSZu
YnNwO29mJm5ic3A7SGFuZHNoYWtlJm5ic3A7cGFja2V0cyZuYnNwO3Byb3ZpZGVzJm5ic3A7cHJv
b2YmbmJzcDtvZiZuYnNwO3JldHVybiZuYnNwO3JvdXRlYWJpbGl0eSZuYnNwO3ZpYSZuYnNwO3Ro
ZSZuYnNwO3VzZSZuYnNwO29mJm5ic3A7dGhlJm5ic3A7ZW5jcnlwdGlvbiZuYnNwO2tleXMsJm5i
c3A7c28mbmJzcDt0aGVyZSZuYnNwO2lzJm5ic3A7bm8mbmJzcDtuZWVkJm5ic3A7dG8mbmJzcDtl
eGNoYW5nZSZuYnNwO3Rva2VucyZuYnNwO2F0Jm5ic3A7dGhhdCZuYnNwO2xldmVsLjxiciA+PGJy
ID4KT24mbmJzcDtUaHUsJm5ic3A7T2N0Jm5ic3A7MzEsJm5ic3A7MjAxOSwmbmJzcDthdCZuYnNw
OzAzOjI5LCZuYnNwO01pa2UmbmJzcDtCaXNob3AmbmJzcDt3cm90ZTo8YnIgPgomZ3Q7Jm5ic3A7
Jm5ic3A7PGJyID4KJmd0OyZuYnNwO1RoZSZuYnNwO2FkdmFudGFnZSZuYnNwO29mJm5ic3A7dXNp
bmcmbmJzcDtSZXRyeSwmbmJzcDtob3dldmVyLCZuYnNwO2lzJm5ic3A7dGhhdCZuYnNwO3RoZSZu
YnNwO3NlcnZlciZuYnNwO2lzJm5ic3A7YWJsZSZuYnNwO3RvJm5ic3A7PGJyID4KJmd0OyZuYnNw
O2tlZXAmbmJzcDttaW5pbWFsJm5ic3A7KGlmJm5ic3A7YW55KSZuYnNwO3N0YXRlJm5ic3A7YWJv
dXQmbmJzcDt0aGUmbmJzcDtjbGllbnQuJm5ic3A7RXhjaGFuZ2luZyZuYnNwO3RoZSZuYnNwO3Rv
a2VuJm5ic3A7YXQmbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7dGhlJm5ic3A7SGFuZHNoYWtlJm5ic3A7
ZW5jcnlwdGlvbiZuYnNwO2xldmVsJm5ic3A7bWVhbnMmbmJzcDt0aGUmbmJzcDtzZXJ2ZXImbmJz
cDtpcyZuYnNwO2FscmVhZHkmbmJzcDtkb2luZyZuYnNwO3dvcmsmbmJzcDs8YnIgPgomZ3Q7Jm5i
c3A7YW5kJm5ic3A7bWFpbnRhaW5pbmcmbmJzcDtzdGF0ZSZuYnNwO2luJm5ic3A7b3JkZXImbmJz
cDt0byZuYnNwO3Byb2Nlc3MmbmJzcDt0aGUmbmJzcDtoYW5kc2hha2UsJm5ic3A7d2hpY2gmbmJz
cDtpcyZuYnNwOzxiciA+CiZndDsmbmJzcDtleGFjdGx5Jm5ic3A7d2hhdCZuYnNwO3RoZSZuYnNw
O3NlcnZlciZuYnNwO2lzJm5ic3A7dHJ5aW5nJm5ic3A7dG8mbmJzcDthdm9pZC48YnIgPgomZ3Q7
Jm5ic3A7PGJyID4KJmd0OyZuYnNwOzxiciA+CiZndDsmbmJzcDsqRnJvbToqJm5ic3A7UVVJQyZu
YnNwOyZsdDs8YSAgaHJlZj0ibWFpbHRvOnF1aWMtYm91bmNlc0BpZXRmLm9yZyIgdGFyZ2V0PSJf
YmxhbmsiIHN0eWxlPSJjb2xvcjojMDAwMGZmO3RleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmUgc29s
aWQgIzAwMDBmZjsiPnF1aWMtYm91bmNlc0BpZXRmLm9yZzwvYT4mZ3Q7Jm5ic3A7Kk9uJm5ic3A7
QmVoYWxmJm5ic3A7T2YmbmJzcDsqJm5ic3A7UWluZyZuYnNwO0FuPGJyID4KJmd0OyZuYnNwOypT
ZW50OiombmJzcDtXZWRuZXNkYXksJm5ic3A7T2N0b2JlciZuYnNwOzMwLCZuYnNwOzIwMTkmbmJz
cDs5OjQxJm5ic3A7QU08YnIgPgomZ3Q7Jm5ic3A7KlRvOiombmJzcDtxdWljJm5ic3A7Jmx0Ozxh
ICBocmVmPSJtYWlsdG86cXVpY0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiIHN0eWxlPSJjb2xv
cjojMDAwMGZmO3RleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmUgc29saWQgIzAwMDBmZjsiPnF1aWNA
aWV0Zi5vcmc8L2E+Jmd0OzsmbmJzcDtqcmkuaWV0ZiZuYnNwOyZsdDs8YSAgaHJlZj0ibWFpbHRv
OmpyaS5pZXRmQGdtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiIHN0eWxlPSJjb2xvcjojMDAwMGZm
O3RleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmUgc29saWQgIzAwMDBmZjsiPmpyaS5pZXRmQGdtYWls
LmNvbTwvYT4mZ3Q7OyZuYnNwO210Jm5ic3A7PGJyID4KJmd0OyZuYnNwOyZsdDs8YSAgaHJlZj0i
bWFpbHRvOm10QGxvd2VudHJvcHkubmV0IiB0YXJnZXQ9Il9ibGFuayIgc3R5bGU9ImNvbG9yOiMw
MDAwZmY7dGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZSBzb2xpZCAjMDAwMGZmOyI+bXRAbG93ZW50
cm9weS5uZXQ8L2E+Jmd0OzxiciA+CiZndDsmbmJzcDsqQ2M6KiZuYnNwOzwvc3Bhbj48c3BhbiAg
c3R5bGU9ImZvbnQtc2l6ZToxNC4wcHg7Zm9udC1mYW1pbHk6TVMgR290aGljO2NvbG9yOmJsYWNr
OyI+5YiY5aSnPC9zcGFuPjxzcGFuICBzdHlsZT0iZm9udC1zaXplOjE0LjBweDtmb250LWZhbWls
eTpNaWNyb3NvZnQgSmhlbmdIZWksc2Fucy1zZXJpZjtjb2xvcjpibGFjazsiPum5jzwvc3Bhbj48
c3BhbiAgc3R5bGU9ImZvbnQtc2l6ZToxNC4wcHg7Zm9udC1mYW1pbHk6VGFob21hLHNhbnMtc2Vy
aWY7Y29sb3I6YmxhY2s7Ij4oPC9zcGFuPjxzcGFuICBzdHlsZT0iZm9udC1zaXplOjE0LjBweDtm
b250LWZhbWlseTpNaWNyb3NvZnQgSmhlbmdIZWksc2Fucy1zZXJpZjtjb2xvcjpibGFjazsiPum5
j+aIkDwvc3Bhbj48c3BhbiAgc3R5bGU9ImZvbnQtc2l6ZToxNC4wcHg7Zm9udC1mYW1pbHk6VGFo
b21hLHNhbnMtc2VyaWY7Y29sb3I6YmxhY2s7Ij4pJm5ic3A7Jmx0OzxhICBocmVmPSJtYWlsdG86
bWF4LmxkcEBhbGliYWJhLWluYy5jb20iIHRhcmdldD0iX2JsYW5rIiBzdHlsZT0iY29sb3I6IzAw
MDBmZjt0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lIHNvbGlkICMwMDAwZmY7Ij5tYXgubGRwQGFs
aWJhYmEtaW5jLmNvbTwvYT4mZ3Q7PGJyID4KJmd0OyZuYnNwOypTdWJqZWN0OiombmJzcDtGYXN0
Jm5ic3A7QWRkcmVzcyZuYnNwO1ZhbGlkYXRpb24mbmJzcDstJm5ic3A7YWJvdXQ8YnIgPgomZ3Q7
Jm5ic3A7PGJyID4KJmd0OyZuYnNwOzxiciA+CiZndDsmbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7PGJy
ID4KJmd0OyZuYnNwO0hpJm5ic3A7TWFydGluLCZuYnNwO0phbmEsJm5ic3A7PGJyID4KJmd0OyZu
YnNwOzxiciA+CiZndDsmbmJzcDtJJm5ic3A7cmVhZCZuYnNwO3Rocm91Z2gmbmJzcDs8YSAgaHJl
Zj0iaHR0cHM6Ly93d3cuaWV0Zi5vcmcvaWQvZHJhZnQtaWV0Zi1xdWljLXRyYW5zcG9ydC0yMy50
eHQiIHRhcmdldD0iX2JsYW5rIiBzdHlsZT0iY29sb3I6IzAwMDBmZjt0ZXh0LWRlY29yYXRpb246
dW5kZXJsaW5lIHNvbGlkICMwMDAwZmY7Ij5odHRwczovL3d3dy5pZXRmLm9yZy9pZC9kcmFmdC1p
ZXRmLXF1aWMtdHJhbnNwb3J0LTIzLnR4dDwvYT4mbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7YW5kJm5i
c3A7aGF2ZSZuYnNwO2EmbmJzcDtmZXcmbmJzcDtjb21tZW50cyZuYnNwO2FuZCZuYnNwO2lkZWFz
Jm5ic3A7dG8mbmJzcDtkaXNjdXNzLjxiciA+CiZndDsmbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7PGJy
ID4KJmd0OyZuYnNwO1tRVUlDLVRyYW5zXSZuYnNwO2RlZmluZXMmbmJzcDthJm5ic3A7dG9rZW4m
bmJzcDtiYXNlZCZuYnNwO3NjaGVtZSZuYnNwO3RvJm5ic3A7ZmFjaWxpdGF0ZSZuYnNwO2FkZHJl
c3MmbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7dmFsaWRhdGlvbiZuYnNwO29mJm5ic3A7YSZuYnNwO2Ns
aWVudC4mbmJzcDtUaGUmbmJzcDt0b2tlbiZuYnNwO01VU1QmbmJzcDtiZSZuYnNwO2NvdmVyZWQm
bmJzcDtieSZuYnNwO2ludGVncml0eSZuYnNwOzxiciA+CiZndDsmbmJzcDtwcm90ZWN0aW9uJm5i
c3A7YWdhaW5zdCZuYnNwO21vZGlmaWNhdGlvbiZuYnNwO29yJm5ic3A7ZmFsc2lmaWNhdGlvbiZu
YnNwO2J5Jm5ic3A7Y2xpZW50cy4mbmJzcDtUaGUmbmJzcDtzZXJ2ZXImbmJzcDs8YnIgPgomZ3Q7
Jm5ic3A7cmVtZW1iZXJzJm5ic3A7dGhlJm5ic3A7dmFsdWUmbmJzcDtpdCZuYnNwO3NlbmRzJm5i
c3A7dG8mbmJzcDtjbGllbnRzJm5ic3A7YW5kJm5ic3A7dmFsaWRhdGVzJm5ic3A7dGhlJm5ic3A7
dG9rZW4mbmJzcDtzZW50Jm5ic3A7PGJyID4KJmd0OyZuYnNwO2JhY2smbmJzcDtmcm9tJm5ic3A7
YSZuYnNwO2NsaWVudC4mbmJzcDtJbiZuYnNwO2l0cyZuYnNwO2Rlc2lnbiwmbmJzcDtSZXRyeSZu
YnNwO3BhY2tldCZuYnNwO2lzJm5ic3A7dXNlZCZuYnNwO3RvJm5ic3A7ZGVsaXZlciZuYnNwO3Ro
ZSZuYnNwOzxiciA+CiZndDsmbmJzcDt0b2tlbiZuYnNwO3RvJm5ic3A7YSZuYnNwO2NsaWVudCZu
YnNwO3doaWNoJm5ic3A7YWRkcmVzcyZuYnNwO2hhcyZuYnNwO25vdCZuYnNwO3lldCZuYnNwO2Jl
ZW4mbmJzcDt2YWxpZGF0ZWQuJm5ic3A7SXQmbmJzcDt2b2lkcyZuYnNwOzxiciA+CiZndDsmbmJz
cDt0aGUmbmJzcDtmaXJzdCZuYnNwO3RyYW5zbWlzc2lvbiZuYnNwO29mJm5ic3A7dGhlJm5ic3A7
SW5pdGlhbCZuYnNwO3BhY2tldCZuYnNwO3NlbnQmbmJzcDtieSZuYnNwO3RoZSZuYnNwO2NsaWVu
dCwmbmJzcDthbmQmbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7dHJpZ2dlcnMmbmJzcDthJm5ic3A7c2Vj
b25kJm5ic3A7SW5pdGlhbCZuYnNwO3BhY2tldCZuYnNwO3RvJm5ic3A7YmUmbmJzcDtzZW50Jm5i
c3A7d2l0aCZuYnNwO3RoZSZuYnNwO3Rva2VuLiZuYnNwO1RoZSZuYnNwOzxiciA+CiZndDsmbmJz
cDtleGNoYW5nZSZuYnNwO29mJm5ic3A7dG9rZW4mbmJzcDt3aWxsJm5ic3A7Y2F1c2UmbmJzcDts
b25nZXImbmJzcDtjb25uZWN0aW9uJm5ic3A7ZXN0YWJsaXNobWVudCZuYnNwO2RlbGF5Jm5ic3A7
Zm9yJm5ic3A7PGJyID4KJmd0OyZuYnNwO2EmbmJzcDtjbGllbnQuPGJyID4KJmd0OyZuYnNwOzxi
ciA+CiZndDsmbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7VG8mbmJzcDtpbXByb3ZlJm5ic3A7dGhlJm5i
c3A7ZWZmaWNpZW5jeSZuYnNwO29mJm5ic3A7YWRkcmVzcyZuYnNwO3ZhbGlkYXRpb24mbmJzcDtk
dXJpbmcmbmJzcDtoYW5kc2hha2UsJm5ic3A7b25lJm5ic3A7PGJyID4KJmd0OyZuYnNwO2lkZWEm
bmJzcDtpcyZuYnNwO3RoYXQmbmJzcDt0aGUmbmJzcDtzYW1lJm5ic3A7dG9rZW4mbmJzcDtjYW4m
bmJzcDtiZSZuYnNwO2V4Y2hhbmdlZCZuYnNwO3ZpYSZuYnNwO2EmbmJzcDtkaWZmZXJlbnQmbmJz
cDtjb250YWluZXImbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7aS5lLiZuYnNwO3RoZSZuYnNwO0hhbmRz
aGFrZSZuYnNwO3BhY2tldCwmbmJzcDt0aGF0Jm5ic3A7ZWxpbWluYXRlcyZuYnNwO3RoZSZuYnNw
O3VzZSZuYnNwO29mJm5ic3A7UmV0cnkmbmJzcDtwYWNrZXQmbmJzcDtmb3ImbmJzcDs8YnIgPgom
Z3Q7Jm5ic3A7dG9rZW4mbmJzcDtkZWxpdmVyeS4mbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7PGJyID4K
Jmd0OyZuYnNwOzxiciA+CiZndDsmbmJzcDtJJm5ic3A7YW0mbmJzcDt3b3JraW5nJm5ic3A7b24m
bmJzcDt0aGUmbmJzcDtjb21wbGV0ZSZuYnNwO2RyYWZ0Jm5ic3A7YW5kJm5ic3A7d2lsbCZuYnNw
O3N1Ym1pdCZuYnNwO2l0Jm5ic3A7YnkmbmJzcDtGcmlkYXkuJm5ic3A7QmVmb3JlJm5ic3A7PGJy
ID4KJmd0OyZuYnNwO3RoYXQsJm5ic3A7aG9wZSZuYnNwO3RoaXMmbmJzcDtjYW4mbmJzcDtiZSZu
YnNwO2Rpc2N1c3NlZCZuYnNwO2luJm5ic3A7ZW1haWwmbmJzcDtmaXJzdC48YnIgPgomZ3Q7Jm5i
c3A7PGJyID4KJmd0OyZuYnNwOzxiciA+CiZndDsmbmJzcDtCUiw8YnIgPgomZ3Q7Jm5ic3A7PGJy
ID4KJmd0OyZuYnNwO1FpbmcmbmJzcDtBbjxiciA+CiZndDs8L3NwYW4+PC9wPjwvZGl2PjxkaXYg
PjxwICBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOi4wcHg7Zm9udC1zaXplOjE0Ljdw
eDtmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7bGluZS1oZWlnaHQ6MjAuMHB4OyI+PHNw
YW4gIHN0eWxlPSJmb250LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5OlRhaG9tYSxzYW5zLXNlcmlm
O2NvbG9yOmJsYWNrOyI+Jm5ic3A7PC9zcGFuPjwvcD48L2Rpdj48L2Rpdj48L2Rpdj48L2Jsb2Nr
cXVvdGU+PGRpdiAgc3R5bGU9ImxpbmUtaGVpZ2h0OjIwLjBweDtjbGVhcjpib3RoOyI+PGJyID48
L2Rpdj48L2Rpdj48L2Rpdj4=
------=ALIBOUNDARY_18201_4eb87940_5dbc26cd_352c27--


From nobody Fri Nov  1 05:54:09 2019
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 8BC2E1200FE; Fri,  1 Nov 2019 05:54:07 -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_HELO_NONE=0.001, 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 0-fTD-HutrPW; Fri,  1 Nov 2019 05:54:05 -0700 (PDT)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::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 E9E5D12002E; Fri,  1 Nov 2019 05:54:04 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id g3so4038510ljl.11; Fri, 01 Nov 2019 05:54:04 -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=ca0/vQIKP81eRii8nmzw4llzvd+nVzqZK4HcvQzG02g=; b=Zg52DamdYni29g5jVntxAaauA8T2/kBr7yv67QNYB0qe2yE1ajGSeXQiHpoE6ntNL8 feU4+KSt2oWouxcCBfruIiL3GIVPNNHldINPD468rEHqshjgQSnn7Zl0rMVoGe+M3rNd 2dI4V3iDEBeHpjO/x+n6wnmnT+HTBA3CwuY1wSucgMpShEZS9SOM71ZT+5LH4WRcvAX2 QOV0tDbzEx4K10IPX4IOCdhblwX3hTRRoQI8oU+aooTPDTaBa0FQvDZd3PFHzZg38vTC jqzVl0jX9cNDhyD9v+IESkhu3BFSBUk3b6pKWTW89fSkZAkoQakkfQC/GrisejLV5dTK mgag==
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=ca0/vQIKP81eRii8nmzw4llzvd+nVzqZK4HcvQzG02g=; b=F51HFDDR5kIs3NMdprGotDqye5HDXV4JB7XtW/1BgrE55+46ukazkqPG6ZlMdqSN/R +XAyu9HzXOu8O480+gwCn4Re7uiPo4UugPOeW4UXTv+jrK1JbSwfuTevSdnQNgfDxr5Z PATr+Lvna5DPENSSELbUKmFD0lGvM6WeX3pv8O5zDOt4ok+PkuiAtrAZnh8CzVun0kSj Oggo/Ioaw5yGdNl8FZ72aO1gIIaFVXs19jKxBrvPj0t5zEBUS8jLhAKBeH4QmdJ1uFlx Fw1Q/zjAvpqfjipHZVIW6EzfpGgi8HEpFFeBpkLWgcYQI8dZQOLiLODHNAvSuHnki1sm eNyA==
X-Gm-Message-State: APjAAAXuKw69eVxhJSurRsYfdaahkxytdWv8jtXbJaJFJU7HNX+IjV4W ROV0cKhc3H+hGnjeyWXUtUrxggPHWRVJaHl8rsc=
X-Google-Smtp-Source: APXvYqzxwGSH5zJHQlVDkuMMT8hObEdPTq4qGlwCmgKf9EzjIz0o/S5nZWwawFks0ZxcQ4gQlQAKL1KUcU5PLx9mmZU=
X-Received: by 2002:a2e:2c10:: with SMTP id s16mr8470325ljs.160.1572612842811;  Fri, 01 Nov 2019 05:54:02 -0700 (PDT)
MIME-Version: 1.0
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com> <BN6PR2201MB1700F72F3DC8F6C3CF79902CDA600@BN6PR2201MB1700.namprd22.prod.outlook.com> <bd15f357-8e7a-42af-bf28-79f7177da385@www.fastmail.com> <f55efb80-1a95-4190-84e5-b81948a7f081.anqing.aq@alibaba-inc.com> <BN6PR2201MB17005571E88F1C68769091A3DA630@BN6PR2201MB1700.namprd22.prod.outlook.com> <69d1a917-b1f9-4142-afb0-f5c67abe7334.anqing.aq@alibaba-inc.com>
In-Reply-To: <69d1a917-b1f9-4142-afb0-f5c67abe7334.anqing.aq@alibaba-inc.com>
From: Marten Seemann <martenseemann@gmail.com>
Date: Fri, 1 Nov 2019 19:53:51 +0700
Message-ID: <CAOYVs2r0zJzbfw5L2Mck8VEJhtyfQtHwF-db5VG45HDTF0WoOQ@mail.gmail.com>
Subject: Re: Fast Address Validation - about
To: Qing An <anqing.aq@alibaba-inc.com>
Cc: QUIC <quic-bounces@ietf.org>, quic <quic@ietf.org>,  "jri.ietf" <jri.ietf@gmail.com>, mt <mt@lowentropy.net>, mikkelfj <mikkelfj@gmail.com>,  =?UTF-8?B?5YiY5aSn6bmPKOm5j+aIkCk=?= <max.ldp@alibaba-inc.com>
Content-Type: multipart/alternative; boundary="000000000000dd75810596487508"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/1ozMFWeQ-o5vS1FoI4h3JbuQ7B8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 12:54:08 -0000

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

I don't see any enhanced client experience, since the handshake takes
exactly the same number of round trips with your proposal as with the
current version of the QUIC draft.
Sending NEW_TOKEN in Initial packets provides no benefit over sending it in
1-RTT packets, but comes with worse privacy properties, since Initial
packets are not encrypted and can therefore be read by on-path observers.

On Fri, Nov 1, 2019 at 7:37 PM Qing An <anqing.aq@alibaba-inc.com> wrote:

>
> If so, for the first connection between client and server, server can
> choose to eliminate the use of Retry packet for token delivery, and
> rely on handshake encryption layer to prove return routability.
> In addition, New_Token frame is used by
> server, via i.e. the Initial packet, to provide the client with an
> address validation token that can be used to validate future connections.
>
> It can enhance the experience in client side for the first connection
> establishment.
>
> I submitted the draft,
> https://datatracker.ietf.org/doc/draft-an-fast-address-validation/
>
> Qing
>
>
>
> ------------------------------------------------------------------
> From:Mike Bishop <mbishop@evequefou.be>
> Send Time:2019=E5=B9=B411=E6=9C=881=E6=97=A5(=E6=98=9F=E6=9C=9F=E4=BA=94)=
 00:06
> To:=E5=AE=89=E5=8B=8D(=E8=8E=B3=E9=80=B8) <anqing.aq@alibaba-inc.com>; qu=
ic <quic@ietf.org>; jri.ietf <
> jri.ietf@gmail.com>; mt <mt@lowentropy.net>; mikkelfj <mikkelfj@gmail.com=
>
> Subject:RE: Fast Address Validation - about
>
> As Martin pointed out in the e-mail you replied to, if the server is
> willing to maintain state, any packet at the Handshake encryption layer
> proves return routability.  There seems to be no need for a separate
> address validation mechanism if the server is willing to proceed with the
> handshake.
>
>
>
> *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of * Qing An
> *Sent:* Thursday, October 31, 2019 8:56 AM
> *To:* quic <quic@ietf.org>; jri.ietf <jri.ietf@gmail.com>; mt <
> mt@lowentropy.net>; mikkelfj <mikkelfj@gmail.com>
> *Subject:* Re: Fast Address Validation - about
>
>
>
>
>
>
>
> To clarify, the proposal is not to replace the existing Retry-based
> validation, but to provide another option for server to do the client
> validation.
>
>
>
> I understand that in server side, exchanging the token at the Handshake e=
ncryption level
> will make the server start to maintain handshake states. But in client
> side, it can accelerate the connection establishment from client to serve=
r.
>
>
>
> And it is the server's decision whether to exchange token in Retry or in
> Handshake. If server chooses to accept the cost brought by token exchangi=
ng
> in Handshake, it will bring more enhanced experience in client side.
>
>
>
>
>
> BR,
>
> Qing
>
>
>
>
>
> ------------------------------------------------------------------
>
> From:Martin Thomson <mt@lowentropy.net>
>
> Send Time:2019=E5=B9=B410=E6=9C=8831=E6=97=A5(=E6=98=9F=E6=9C=9F=E5=9B=9B=
) 06:07
>
> To:quic <quic@ietf.org>
>
> Subject:Re: Fast Address Validation - about
>
>
>
>
> Also note that exchange of Handshake packets provides proof of return rou=
teability via the use of the encryption keys, so there is no need to exchan=
ge tokens at that level.
>
> On Thu, Oct 31, 2019, at 03:29, Mike Bishop wrote:
> >
> > The advantage of using Retry, however, is that the server is able to
> > keep minimal (if any) state about the client. Exchanging the token at
> > the Handshake encryption level means the server is already doing work
> > and maintaining state in order to process the handshake, which is
> > exactly what the server is trying to avoid.
> >
> >
> > *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of * Qing An
> > *Sent:* Wednesday, October 30, 2019 9:41 AM
> > *To:* quic <quic@ietf.org>; jri.ietf <jri.ietf@gmail.com>; mt
> > <mt@lowentropy.net>
> > *Cc:* =E5=88=98=E5=A4=A7=E9=B9=8F(=E9=B9=8F=E6=88=90) <max.ldp@alibaba-=
inc.com>
> > *Subject:* Fast Address Validation - about
> >
> >
> >
> >
> > Hi Martin, Jana,
> >
> > I read through https://www.ietf.org/id/draft-ietf-quic-transport-23.txt
> > and have a few comments and ideas to discuss.
> >
> >
> > [QUIC-Trans] defines a token based scheme to facilitate address
> > validation of a client. The token MUST be covered by integrity
> > protection against modification or falsification by clients. The server
> > remembers the value it sends to clients and validates the token sent
> > back from a client. In its design, Retry packet is used to deliver the
> > token to a client which address has not yet been validated. It voids
> > the first transmission of the Initial packet sent by the client, and
> > triggers a second Initial packet to be sent with the token. The
> > exchange of token will cause longer connection establishment delay for
> > a client.
> >
> >
> > To improve the efficiency of address validation during handshake, one
> > idea is that the same token can be exchanged via a different container
> > i.e. the Handshake packet, that eliminates the use of Retry packet for
> > token delivery.
> >
> >
> > I am working on the complete draft and will submit it by Friday. Before
> > that, hope this can be discussed in email first.
> >
> >
> > BR,
> >
> > Qing An
> >
>
>
>
>
>

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

<div dir=3D"ltr"><div>I don&#39;t see any enhanced client experience, since=
 the handshake takes exactly the same number of round trips with your propo=
sal as with the current version of the QUIC draft.<br></div><div>Sending NE=
W_TOKEN in Initial packets provides no benefit over sending it in 1-RTT pac=
kets, but comes with worse privacy properties, since Initial packets are no=
t encrypted and can therefore be read by on-path observers.<br></div></div>=
<br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri=
, Nov 1, 2019 at 7:37 PM Qing An &lt;<a href=3D"mailto:anqing.aq@alibaba-in=
c.com">anqing.aq@alibaba-inc.com</a>&gt; wrote:<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><div style=3D"line-height:1.7;font-fa=
mily:Tahoma,Arial,STHeiti,SimSun;font-size:14px;color:rgb(0,0,0)"><div styl=
e=3D"clear:both"><br></div><div style=3D"clear:both">If so, f<span>or=C2=A0=
the=C2=A0first</span>=C2=A0connection=C2=A0between=C2=A0client=C2=A0and=C2=
=A0server, server can choose to eliminate=C2=A0the=C2=A0use=C2=A0of=C2=A0Re=
try packet=C2=A0for=C2=A0token=C2=A0delivery, and rely=C2=A0on=C2=A0handsha=
ke=C2=A0encryption=C2=A0layer=C2=A0to prove=C2=A0return routability.=C2=A0 =
In=C2=A0addition, New_Token frame is=C2=A0used=C2=A0by server,=C2=A0via=C2=
=A0i.e.=C2=A0the=C2=A0Initial=C2=A0packet,=C2=A0to=C2=A0provide=C2=A0the=C2=
=A0client=C2=A0with=C2=A0an address=C2=A0validation=C2=A0token=C2=A0that=C2=
=A0can=C2=A0be=C2=A0used=C2=A0to=C2=A0validate=C2=A0future<span>=C2=A0conne=
ctions.</span></div><div style=3D"clear:both"><span><br></span></div><div s=
tyle=3D"clear:both"><span>It can enhance the experience in client side for =
the first connection establishment.</span></div><div style=3D"clear:both"><=
span><br></span></div><div style=3D"clear:both"><span>I submitted the draft=
,=C2=A0<a href=3D"https://datatracker.ietf.org/doc/draft-an-fast-address-va=
lidation/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-an-fast=
-address-validation/</a></span></div><div style=3D"clear:both"><span><br></=
span></div><div style=3D"clear:both"><span>Qing</span></div><div style=3D"c=
lear:both"></div><div style=3D"clear:both"><br></div><div style=3D"clear:bo=
th"><br></div><div style=3D"clear:both"><br></div><blockquote style=3D"marg=
in-right:0px;margin-top:0px;margin-bottom:0px;font-family:Tahoma,Arial,STHe=
iti,SimSun;font-size:14px;color:rgb(0,0,0)"><div style=3D"clear:both">-----=
-------------------------------------------------------------</div><div sty=
le=3D"clear:both">From:Mike Bishop &lt;<a href=3D"mailto:mbishop@evequefou.=
be" target=3D"_blank">mbishop@evequefou.be</a>&gt;</div><div style=3D"clear=
:both">Send Time:2019=E5=B9=B411=E6=9C=881=E6=97=A5(=E6=98=9F=E6=9C=9F=E4=
=BA=94) 00:06</div><div style=3D"clear:both">To:=E5=AE=89=E5=8B=8D(=E8=8E=
=B3=E9=80=B8) &lt;<a href=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_b=
lank">anqing.aq@alibaba-inc.com</a>&gt;; quic &lt;<a href=3D"mailto:quic@ie=
tf.org" target=3D"_blank">quic@ietf.org</a>&gt;; jri.ietf &lt;<a href=3D"ma=
ilto:jri.ietf@gmail.com" target=3D"_blank">jri.ietf@gmail.com</a>&gt;; mt &=
lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"_blank">mt@lowentropy.net=
</a>&gt;; mikkelfj &lt;<a href=3D"mailto:mikkelfj@gmail.com" target=3D"_bla=
nk">mikkelfj@gmail.com</a>&gt;</div><div style=3D"clear:both">Subject:RE: F=
ast Address Validation - about</div><div style=3D"clear:both"><br></div><di=
v><p class=3D"MsoNormal" style=3D"margin:0px;font-size:14.7px;font-family:C=
alibri,sans-serif">As Martin pointed out in the e-mail you replied to, if t=
he server is willing to maintain state, any packet at the Handshake encrypt=
ion layer proves return routability.=C2=A0 There seems to be no need for a =
separate address validation mechanism
 if the server is willing to proceed with the handshake.</p><p class=3D"Mso=
Normal" style=3D"margin:0px;font-size:14.7px;font-family:Calibri,sans-serif=
">=C2=A0</p><p class=3D"MsoNormal" style=3D"margin:0px;font-size:14.7px;fon=
t-family:Calibri,sans-serif"><b>From:</b> QUIC &lt;<a href=3D"mailto:quic-b=
ounces@ietf.org" target=3D"_blank">quic-bounces@ietf.org</a>&gt; <b>On Beha=
lf Of </b>
Qing An<br><b>Sent:</b> Thursday, October 31, 2019 8:56 AM<br><b>To:</b> qu=
ic &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic@ietf.org</a>=
&gt;; jri.ietf &lt;<a href=3D"mailto:jri.ietf@gmail.com" target=3D"_blank">=
jri.ietf@gmail.com</a>&gt;; mt &lt;<a href=3D"mailto:mt@lowentropy.net" tar=
get=3D"_blank">mt@lowentropy.net</a>&gt;; mikkelfj &lt;<a href=3D"mailto:mi=
kkelfj@gmail.com" target=3D"_blank">mikkelfj@gmail.com</a>&gt;<br><b>Subjec=
t:</b> Re: Fast Address Validation - about</p><p class=3D"MsoNormal" style=
=3D"margin:0px;font-size:14.7px;font-family:Calibri,sans-serif">=C2=A0</p><=
div><div><p class=3D"MsoNormal" style=3D"margin:0px;font-size:14.7px;font-f=
amily:Calibri,sans-serif"><span style=3D"font-size:14px;font-family:Tahoma,=
sans-serif;color:black">=C2=A0</span></p></div><div><p class=3D"MsoNormal" =
style=3D"margin:0px;font-size:14.7px;font-family:Calibri,sans-serif"><span =
style=3D"font-size:14px;font-family:Tahoma,sans-serif;color:black">=C2=A0</=
span></p></div><div><p class=3D"MsoNormal" style=3D"margin:0px;font-size:14=
.7px;font-family:Calibri,sans-serif"><span style=3D"font-size:14px;font-fam=
ily:Tahoma,sans-serif;color:black">To clarify, the proposal is not to repla=
ce the existing Retry-based validation, but to provide another option for s=
erver to do the client validation.</span></p></div><div><p class=3D"MsoNorm=
al" style=3D"margin:0px;font-size:14.7px;font-family:Calibri,sans-serif"><s=
pan style=3D"font-size:14px;font-family:Tahoma,sans-serif;color:black">=C2=
=A0</span></p></div><div><p class=3D"MsoNormal" style=3D"margin:0px;font-si=
ze:14.7px;font-family:Calibri,sans-serif"><span style=3D"font-size:14px;fon=
t-family:Tahoma,sans-serif;color:black">I understand that in server side, e=
<span style=3D"background:white none repeat scroll 0% 0%">xchanging=C2=A0th=
e=C2=A0token=C2=A0at=C2=A0the=C2=A0Handshake=C2=A0encryption=C2=A0level wil=
l make the server start to maintain handshake
 states. But in client side, it can accelerate the connection establishment=
 from client to server.</span></span></p></div><div><p class=3D"MsoNormal" =
style=3D"margin:0px;font-size:14.7px;font-family:Calibri,sans-serif"><span =
style=3D"font-size:14px;font-family:Tahoma,sans-serif;color:black">=C2=A0</=
span></p></div><div><p class=3D"MsoNormal" style=3D"margin:0px;font-size:14=
.7px;font-family:Calibri,sans-serif"><span style=3D"font-size:14px;font-fam=
ily:Tahoma,sans-serif;color:black;background:white none repeat scroll 0% 0%=
">And it is the server&#39;s decision whether to exchange token in Retry or=
 in Handshake. If server chooses to accept the cost brought by token exchan=
ging
 in Handshake, it will bring more enhanced experience in client side.</span=
><span style=3D"font-size:14px;font-family:Tahoma,sans-serif;color:black"><=
/span></p></div><div><p class=3D"MsoNormal" style=3D"margin:0px;font-size:1=
4.7px;font-family:Calibri,sans-serif"><span style=3D"font-size:14px;font-fa=
mily:Tahoma,sans-serif;color:black">=C2=A0</span></p></div><div><p class=3D=
"MsoNormal" style=3D"margin:0px;font-size:14.7px;font-family:Calibri,sans-s=
erif"><span style=3D"font-size:14px;font-family:Tahoma,sans-serif;color:bla=
ck">=C2=A0</span></p></div><div><p class=3D"MsoNormal" style=3D"margin:0px;=
font-size:14.7px;font-family:Calibri,sans-serif"><span style=3D"font-size:1=
4px;font-family:Tahoma,sans-serif;color:black;background:white none repeat =
scroll 0% 0%">BR,</span><span style=3D"font-size:14px;font-family:Tahoma,sa=
ns-serif;color:black"></span></p></div><div><p class=3D"MsoNormal" style=3D=
"margin:0px;font-size:14.7px;font-family:Calibri,sans-serif"><span style=3D=
"font-size:14px;font-family:Tahoma,sans-serif;color:black;background:white =
none repeat scroll 0% 0%">Qing</span><span style=3D"font-size:14px;font-fam=
ily:Tahoma,sans-serif;color:black"></span></p></div><div><p class=3D"MsoNor=
mal" style=3D"margin:0px;font-size:14.7px;font-family:Calibri,sans-serif"><=
span style=3D"font-size:14px;font-family:Tahoma,sans-serif;color:black">=C2=
=A0</span></p></div><div><p class=3D"MsoNormal" style=3D"margin:0px;font-si=
ze:14.7px;font-family:Calibri,sans-serif"><span style=3D"font-size:14px;fon=
t-family:Tahoma,sans-serif;color:black">=C2=A0</span></p></div><div style=
=3D"margin:14px 0px"><div><p class=3D"MsoNormal" style=3D"margin:0px;font-s=
ize:14.7px;font-family:Calibri,sans-serif"><span style=3D"font-size:14px;fo=
nt-family:Tahoma,sans-serif;color:black">----------------------------------=
--------------------------------</span></p></div><div><p class=3D"MsoNormal=
" style=3D"margin:0px;font-size:14.7px;font-family:Calibri,sans-serif"><spa=
n style=3D"font-size:14px;font-family:Tahoma,sans-serif;color:black">From:M=
artin Thomson &lt;<a href=3D"mailto:mt@lowentropy.net" style=3D"color:rgb(0=
,0,255);text-decoration:underline rgb(0,0,255)" target=3D"_blank">mt@lowent=
ropy.net</a>&gt;</span></p></div><div><p class=3D"MsoNormal" style=3D"margi=
n:0px;font-size:14.7px;font-family:Calibri,sans-serif"><span style=3D"font-=
size:14px;font-family:Tahoma,sans-serif;color:black">Send Time:2019</span><=
span style=3D"font-size:14px;font-family:MS Gothic;color:black">=E5=B9=B4</=
span><span style=3D"font-size:14px;font-family:Tahoma,sans-serif;color:blac=
k">10</span><span style=3D"font-size:14px;font-family:MS Gothic;color:black=
">=E6=9C=88</span><span style=3D"font-size:14px;font-family:Tahoma,sans-ser=
if;color:black">31</span><span style=3D"font-size:14px;font-family:MS Gothi=
c;color:black">=E6=97=A5</span><span style=3D"font-size:14px;font-family:Ta=
homa,sans-serif;color:black">(</span><span style=3D"font-size:14px;font-fam=
ily:MS Gothic;color:black">=E6=98=9F=E6=9C=9F=E5=9B=9B</span><span style=3D=
"font-size:14px;font-family:Tahoma,sans-serif;color:black">)
 06:07</span></p></div><div><p class=3D"MsoNormal" style=3D"margin:0px;font=
-size:14.7px;font-family:Calibri,sans-serif"><span style=3D"font-size:14px;=
font-family:Tahoma,sans-serif;color:black">To:quic &lt;<a href=3D"mailto:qu=
ic@ietf.org" style=3D"color:rgb(0,0,255);text-decoration:underline rgb(0,0,=
255)" target=3D"_blank">quic@ietf.org</a>&gt;</span></p></div><div><p class=
=3D"MsoNormal" style=3D"margin:0px;font-size:14.7px;font-family:Calibri,san=
s-serif"><span style=3D"font-size:14px;font-family:Tahoma,sans-serif;color:=
black">Subject:Re: Fast Address Validation - about</span></p></div><div><p =
class=3D"MsoNormal" style=3D"margin:0px;font-size:14.7px;font-family:Calibr=
i,sans-serif"><span style=3D"font-size:14px;font-family:Tahoma,sans-serif;c=
olor:black">=C2=A0</span></p></div><p class=3D"MsoNormal" style=3D"margin:0=
px;font-size:14.7px;font-family:Calibri,sans-serif"><span style=3D"font-siz=
e:14px;font-family:Tahoma,sans-serif;color:black">Also=C2=A0note=C2=A0that=
=C2=A0exchange=C2=A0of=C2=A0Handshake=C2=A0packets=C2=A0provides=C2=A0proof=
=C2=A0of=C2=A0return=C2=A0routeability=C2=A0via=C2=A0the=C2=A0use=C2=A0of=
=C2=A0the=C2=A0encryption=C2=A0keys,=C2=A0so=C2=A0there=C2=A0is=C2=A0no=C2=
=A0need=C2=A0to=C2=A0exchange=C2=A0tokens=C2=A0at=C2=A0that=C2=A0level.<br>=
<br>
On=C2=A0Thu,=C2=A0Oct=C2=A031,=C2=A02019,=C2=A0at=C2=A003:29,=C2=A0Mike=C2=
=A0Bishop=C2=A0wrote:<br>
&gt;=C2=A0=C2=A0<br>
&gt;=C2=A0The=C2=A0advantage=C2=A0of=C2=A0using=C2=A0Retry,=C2=A0however,=
=C2=A0is=C2=A0that=C2=A0the=C2=A0server=C2=A0is=C2=A0able=C2=A0to=C2=A0<br>
&gt;=C2=A0keep=C2=A0minimal=C2=A0(if=C2=A0any)=C2=A0state=C2=A0about=C2=A0t=
he=C2=A0client.=C2=A0Exchanging=C2=A0the=C2=A0token=C2=A0at=C2=A0<br>
&gt;=C2=A0the=C2=A0Handshake=C2=A0encryption=C2=A0level=C2=A0means=C2=A0the=
=C2=A0server=C2=A0is=C2=A0already=C2=A0doing=C2=A0work=C2=A0<br>
&gt;=C2=A0and=C2=A0maintaining=C2=A0state=C2=A0in=C2=A0order=C2=A0to=C2=A0p=
rocess=C2=A0the=C2=A0handshake,=C2=A0which=C2=A0is=C2=A0<br>
&gt;=C2=A0exactly=C2=A0what=C2=A0the=C2=A0server=C2=A0is=C2=A0trying=C2=A0t=
o=C2=A0avoid.<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0*From:*=C2=A0QUIC=C2=A0&lt;<a href=3D"mailto:quic-bounces@ietf.or=
g" style=3D"color:rgb(0,0,255);text-decoration:underline rgb(0,0,255)" targ=
et=3D"_blank">quic-bounces@ietf.org</a>&gt;=C2=A0*On=C2=A0Behalf=C2=A0Of=C2=
=A0*=C2=A0Qing=C2=A0An<br>
&gt;=C2=A0*Sent:*=C2=A0Wednesday,=C2=A0October=C2=A030,=C2=A02019=C2=A09:41=
=C2=A0AM<br>
&gt;=C2=A0*To:*=C2=A0quic=C2=A0&lt;<a href=3D"mailto:quic@ietf.org" style=
=3D"color:rgb(0,0,255);text-decoration:underline rgb(0,0,255)" target=3D"_b=
lank">quic@ietf.org</a>&gt;;=C2=A0jri.ietf=C2=A0&lt;<a href=3D"mailto:jri.i=
etf@gmail.com" style=3D"color:rgb(0,0,255);text-decoration:underline rgb(0,=
0,255)" target=3D"_blank">jri.ietf@gmail.com</a>&gt;;=C2=A0mt=C2=A0<br>
&gt;=C2=A0&lt;<a href=3D"mailto:mt@lowentropy.net" style=3D"color:rgb(0,0,2=
55);text-decoration:underline rgb(0,0,255)" target=3D"_blank">mt@lowentropy=
.net</a>&gt;<br>
&gt;=C2=A0*Cc:*=C2=A0</span><span style=3D"font-size:14px;font-family:MS Go=
thic;color:black">=E5=88=98=E5=A4=A7</span><span style=3D"font-size:14px;fo=
nt-family:Microsoft JhengHei,sans-serif;color:black">=E9=B9=8F</span><span =
style=3D"font-size:14px;font-family:Tahoma,sans-serif;color:black">(</span>=
<span style=3D"font-size:14px;font-family:Microsoft JhengHei,sans-serif;col=
or:black">=E9=B9=8F=E6=88=90</span><span style=3D"font-size:14px;font-famil=
y:Tahoma,sans-serif;color:black">)=C2=A0&lt;<a href=3D"mailto:max.ldp@aliba=
ba-inc.com" style=3D"color:rgb(0,0,255);text-decoration:underline rgb(0,0,2=
55)" target=3D"_blank">max.ldp@alibaba-inc.com</a>&gt;<br>
&gt;=C2=A0*Subject:*=C2=A0Fast=C2=A0Address=C2=A0Validation=C2=A0-=C2=A0abo=
ut<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0Hi=C2=A0Martin,=C2=A0Jana,=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0I=C2=A0read=C2=A0through=C2=A0<a href=3D"https://www.ietf.org/id/=
draft-ietf-quic-transport-23.txt" style=3D"color:rgb(0,0,255);text-decorati=
on:underline rgb(0,0,255)" target=3D"_blank">https://www.ietf.org/id/draft-=
ietf-quic-transport-23.txt</a>=C2=A0<br>
&gt;=C2=A0and=C2=A0have=C2=A0a=C2=A0few=C2=A0comments=C2=A0and=C2=A0ideas=
=C2=A0to=C2=A0discuss.<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0[QUIC-Trans]=C2=A0defines=C2=A0a=C2=A0token=C2=A0based=C2=A0schem=
e=C2=A0to=C2=A0facilitate=C2=A0address=C2=A0<br>
&gt;=C2=A0validation=C2=A0of=C2=A0a=C2=A0client.=C2=A0The=C2=A0token=C2=A0M=
UST=C2=A0be=C2=A0covered=C2=A0by=C2=A0integrity=C2=A0<br>
&gt;=C2=A0protection=C2=A0against=C2=A0modification=C2=A0or=C2=A0falsificat=
ion=C2=A0by=C2=A0clients.=C2=A0The=C2=A0server=C2=A0<br>
&gt;=C2=A0remembers=C2=A0the=C2=A0value=C2=A0it=C2=A0sends=C2=A0to=C2=A0cli=
ents=C2=A0and=C2=A0validates=C2=A0the=C2=A0token=C2=A0sent=C2=A0<br>
&gt;=C2=A0back=C2=A0from=C2=A0a=C2=A0client.=C2=A0In=C2=A0its=C2=A0design,=
=C2=A0Retry=C2=A0packet=C2=A0is=C2=A0used=C2=A0to=C2=A0deliver=C2=A0the=C2=
=A0<br>
&gt;=C2=A0token=C2=A0to=C2=A0a=C2=A0client=C2=A0which=C2=A0address=C2=A0has=
=C2=A0not=C2=A0yet=C2=A0been=C2=A0validated.=C2=A0It=C2=A0voids=C2=A0<br>
&gt;=C2=A0the=C2=A0first=C2=A0transmission=C2=A0of=C2=A0the=C2=A0Initial=C2=
=A0packet=C2=A0sent=C2=A0by=C2=A0the=C2=A0client,=C2=A0and=C2=A0<br>
&gt;=C2=A0triggers=C2=A0a=C2=A0second=C2=A0Initial=C2=A0packet=C2=A0to=C2=
=A0be=C2=A0sent=C2=A0with=C2=A0the=C2=A0token.=C2=A0The=C2=A0<br>
&gt;=C2=A0exchange=C2=A0of=C2=A0token=C2=A0will=C2=A0cause=C2=A0longer=C2=
=A0connection=C2=A0establishment=C2=A0delay=C2=A0for=C2=A0<br>
&gt;=C2=A0a=C2=A0client.<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0To=C2=A0improve=C2=A0the=C2=A0efficiency=C2=A0of=C2=A0address=C2=
=A0validation=C2=A0during=C2=A0handshake,=C2=A0one=C2=A0<br>
&gt;=C2=A0idea=C2=A0is=C2=A0that=C2=A0the=C2=A0same=C2=A0token=C2=A0can=C2=
=A0be=C2=A0exchanged=C2=A0via=C2=A0a=C2=A0different=C2=A0container=C2=A0<br=
>
&gt;=C2=A0i.e.=C2=A0the=C2=A0Handshake=C2=A0packet,=C2=A0that=C2=A0eliminat=
es=C2=A0the=C2=A0use=C2=A0of=C2=A0Retry=C2=A0packet=C2=A0for=C2=A0<br>
&gt;=C2=A0token=C2=A0delivery.=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0I=C2=A0am=C2=A0working=C2=A0on=C2=A0the=C2=A0complete=C2=A0draft=
=C2=A0and=C2=A0will=C2=A0submit=C2=A0it=C2=A0by=C2=A0Friday.=C2=A0Before=C2=
=A0<br>
&gt;=C2=A0that,=C2=A0hope=C2=A0this=C2=A0can=C2=A0be=C2=A0discussed=C2=A0in=
=C2=A0email=C2=A0first.<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0BR,<br>
&gt;=C2=A0<br>
&gt;=C2=A0Qing=C2=A0An<br>
&gt;</span></p></div><div><p class=3D"MsoNormal" style=3D"margin:0px;font-s=
ize:14.7px;font-family:Calibri,sans-serif;line-height:20px"><span style=3D"=
font-size:14px;font-family:Tahoma,sans-serif;color:black">=C2=A0</span></p>=
</div></div></div></blockquote><div style=3D"line-height:20px;clear:both"><=
br></div></div></div></blockquote></div>

--000000000000dd75810596487508--


From nobody Fri Nov  1 06:00:57 2019
Return-Path: <ximaera@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 D2B81120125 for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 06:00:55 -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_HELO_NONE=0.001, 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 rJ9uP3mHrVhg for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 06:00:54 -0700 (PDT)
Received: from mail-yb1-xb2a.google.com (mail-yb1-xb2a.google.com [IPv6:2607:f8b0:4864:20::b2a]) (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 D8C8F12002E for <quic@ietf.org>; Fri,  1 Nov 2019 06:00:53 -0700 (PDT)
Received: by mail-yb1-xb2a.google.com with SMTP id t11so3811416ybk.10 for <quic@ietf.org>; Fri, 01 Nov 2019 06:00:53 -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=1gn2N7ydt6GtwXN500LKpSt5mYpidoqjYhSHSIPX0ts=; b=e0UzYaFnpWvGSpKkKlB/V7+j+9vRAfVyqHPzipqhup8tCggBUQgxdUvilydvH5Cn/k s4lpSnKEb80uvE4Pkf/6sckXts2WuD0iDKFxetWAt1ms/8cC1jkhJFVs1ti4C1JQmX8C UkCr/Z6IpvIBGAD3Oqa44ycZLVzDcyRnWCroYpCxZlVMH/8XhQi2qqttj6ZIHyB2yqti YUXJk9RlfM/PgQA60Uq2QvR3xfIgPl0btrR4vlyxIlFvD4dOb8GoDaALObN6isJ36zRx Hw3plY0uU84D6BB7EEV+6TTK/tYwjWRwGYY0NY81KRKQiL49rkMo2tqav+XENoPVUqZM 1hiw==
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=1gn2N7ydt6GtwXN500LKpSt5mYpidoqjYhSHSIPX0ts=; b=IVMZAfA/iQJ4CIjx/ADE0CaQSl0tB3PU6Loqc3yhxQM8I2eXdn8C3B0cpZiGKsxJAZ d5m8VcHuChx3U8e48Vne1LwpY6WaQB1TrVpIEjOq1ynxUTnmZoi/yDahdWnG7DrNZNFA 8KcwnL//Yc+LBeCDBDTkhTX/u9icDmdlnZPHO9E1IoRw8apSN3xju9/ZuK/y1mN8AAK7 z68oN58mtkMqGEHKpUeDA5TfjMXA7kcZ5DsIh+kC9pp2EMrBbPSA0INzKkLqbiVTerFw L4WFxqN2XWXBppMXk8VwYSSJ6W2qeay5+FnY3uO4aNzctkG4ELPYiDZ0j5xny9woqkDF SZcA==
X-Gm-Message-State: APjAAAVzR7ojrcGGQ9+2Zt0vQ1hHkOuj8E9QtSl3VgySxQXjsqD4Njml eUi870nBkH59jYnlr4WvbS7wn4z7uZqvyiqZUsA=
X-Google-Smtp-Source: APXvYqxxPKwdgmePPnwcTSbpNjTR9++zls++Nh3SYy/oB3SZ6R5HFbEsD8qOxUsIWwoRZRHJuP4um4Teh1DAoDfSpMo=
X-Received: by 2002:a25:db46:: with SMTP id g67mr8727708ybf.312.1572613252726;  Fri, 01 Nov 2019 06:00:52 -0700 (PDT)
MIME-Version: 1.0
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com>
In-Reply-To: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com>
From: =?UTF-8?Q?T=C3=B6ma_Gavrichenkov?= <ximaera@gmail.com>
Date: Fri, 1 Nov 2019 16:00:39 +0300
Message-ID: <CALZ3u+YyOQxA5zBxkhDj9-wObfqjxPxPyXH9PumaW79DNkKjsg@mail.gmail.com>
Subject: Re: Fast Address Validation - about
To: Qing An <anqing.aq@alibaba-inc.com>
Cc: IETF QUIC WG <quic@ietf.org>, "jri.ietf" <jri.ietf@gmail.com>, mt <mt@lowentropy.net>,  =?UTF-8?B?5YiY5aSn6bmPKOm5j+aIkCk=?= <max.ldp@alibaba-inc.com>
Content-Type: multipart/alternative; boundary="0000000000004c45ad0596488edd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Al0SEznBQQbQnmT2-EmSj6JQeWA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 13:00:56 -0000

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

Peace,

On Wed, Oct 30, 2019, 4:41 PM Qing An <anqing.aq@alibaba-inc.com> wrote:

> [QUIC-Trans] defines a token based scheme
> to facilitate address validation of a client. The token MUST be covered b=
y
> integrity protection against modification or falsification by clients. Th=
e
> server remembers the value it sends to clients and validates the token se=
nt
> back from a client.
>

About the only use case for the client address validation I can think of is
the protection against Hello packet floods exhausting the resources
(including memory) on the server.

In this case keeping any state for connections coming from potentially
spoofed addresses on the server compromises the very concept of flood
protection.  All the state must be kept in the Retry packet and promptly
signaled back by the client.

The speed-up brought in by keeping the state is probably negligible (TODO:
actual measurements) while with a today's average 300Mpps packet flood
hardly any state could be kept for any reasonable period of time.

--
T=C3=B6ma

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

<div dir=3D"auto">Peace,<br><br><div class=3D"gmail_quote" dir=3D"auto"><di=
v dir=3D"ltr" class=3D"gmail_attr">On Wed, Oct 30, 2019, 4:41 PM Qing An &l=
t;<a href=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_blank" rel=3D"nor=
eferrer">anqing.aq@alibaba-inc.com</a>&gt; wrote:<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;pad=
ding-left:1ex"><div style=3D"line-height:1.7;font-family:Tahoma,Arial,STHei=
ti,SimSun;font-size:14.0px;color:#000000" dir=3D"auto"><div style=3D"clear:=
both">[QUIC-Trans] defines=C2=A0a=C2=A0token=C2=A0based=C2=A0scheme to=C2=
=A0facilitate=C2=A0address=C2=A0validation=C2=A0of=C2=A0a=C2=A0client.=C2=
=A0The=C2=A0token=C2=A0MUST=C2=A0be=C2=A0covered=C2=A0by integrity protecti=
on=C2=A0against=C2=A0modification=C2=A0or=C2=A0falsification=C2=A0by=C2=A0c=
lients.=C2=A0The server=C2=A0remembers the=C2=A0value it sends to=C2=A0clie=
nts=C2=A0and=C2=A0validates=C2=A0the=C2=A0token=C2=A0sent back=C2=A0from=C2=
=A0a=C2=A0client.</div></div></blockquote></div><div dir=3D"auto"><br></div=
><div class=3D"gmail_quote" dir=3D"auto"></div><div dir=3D"auto"><div dir=
=3D"auto" style=3D"font-family:sans-serif">About the only use case for the =
client address validation I can think of is the protection against Hello pa=
cket floods exhausting the resources (including memory) on the server.</div=
><div dir=3D"auto" style=3D"font-family:sans-serif"><br></div><div dir=3D"a=
uto" style=3D"font-family:sans-serif">In this case keeping any state for co=
nnections coming from potentially spoofed addresses on the server compromis=
es the very concept of flood protection.=C2=A0 All the state must be kept i=
n the Retry packet and promptly signaled back by the client.</div><div dir=
=3D"auto" style=3D"font-family:sans-serif"><br></div><div dir=3D"auto" styl=
e=3D"font-family:sans-serif">The speed-up brought in by keeping the state i=
s probably negligible (TODO: actual measurements) while with a today&#39;s =
average 300Mpps packet flood hardly any state could be kept for any reasona=
ble period of time.</div><div dir=3D"auto" style=3D"font-family:sans-serif"=
><br></div><div dir=3D"auto" style=3D"font-family:sans-serif">--</div><div =
dir=3D"auto" style=3D"font-family:sans-serif">T=C3=B6ma</div></div><div cla=
ss=3D"gmail_quote" dir=3D"auto"></div></div>

--0000000000004c45ad0596488edd--


From nobody Fri Nov  1 06:26:36 2019
Return-Path: <anqing.aq@alibaba-inc.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 4C4931200CE; Fri,  1 Nov 2019 06:26:35 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 (1024-bit key) header.d=alibaba-inc.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 d0jykFusdbsP; Fri,  1 Nov 2019 06:26:32 -0700 (PDT)
Received: from out0-153.mail.aliyun.com (out0-153.mail.aliyun.com [140.205.0.153]) (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 DB35A12013A; Fri,  1 Nov 2019 06:26:27 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1572614780; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=RzvtrwboNpeY/sRL3sK1WiUYqHA8+wNXkrZpzZp2tyA=; b=m0gP/MWrGtb7O0W3OcAAtuAUMjTpU0bmlAqpRfouCywkrs/tGRoIhjpMuk83miB+LxqnpSSX7mhAlI8HQDtHeJasUm9whgllT13BQEj1Lkr37J6Z2PbOjKKgeDYy8IYok9k8b3t+r0/UpsWseEHpWEqJgZAE3f5v+Ep+tJNfWZk=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R471e4; CH=green; DM=||false|; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03310; MF=anqing.aq@alibaba-inc.com; NM=1; PH=DW; RN=7; SR=0; TI=W4_5657687_v5ForWebDing_0A930BF4_1572614724509_o7001c4482f; 
Received: from WS-web (anqing.aq@alibaba-inc.com[W4_5657687_v5ForWebDing_0A930BF4_1572614724509_o7001c4482f]) by e01l07408.eu6 at Fri, 01 Nov 2019 21:26:17 +0800
Date: Fri, 01 Nov 2019 21:26:17 +0800
From: "Qing An" <anqing.aq@alibaba-inc.com>
To: "Marten Seemann" <martenseemann@gmail.com>
Cc: "QUIC" <quic-bounces@ietf.org>, "quic" <quic@ietf.org>, "jri.ietf" <jri.ietf@gmail.com>, "mt" <mt@lowentropy.net>, "mikkelfj" <mikkelfj@gmail.com>, "=?UTF-8?B?5YiY5aSn6bmPKOm5j+aIkCk=?=" <max.ldp@alibaba-inc.com>
Reply-To: "Qing An" <anqing.aq@alibaba-inc.com>
Message-ID: <7ac8ad51-c1a2-461b-bc47-021b3875eab8.anqing.aq@alibaba-inc.com>
Subject: =?UTF-8?B?UmU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQ=?=
X-Mailer: [Alimail-Mailagent revision 2765257][W4_5657687][v5ForWebDing][Chrome]
MIME-Version: 1.0
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com> <BN6PR2201MB1700F72F3DC8F6C3CF79902CDA600@BN6PR2201MB1700.namprd22.prod.outlook.com> <bd15f357-8e7a-42af-bf28-79f7177da385@www.fastmail.com> <f55efb80-1a95-4190-84e5-b81948a7f081.anqing.aq@alibaba-inc.com> <BN6PR2201MB17005571E88F1C68769091A3DA630@BN6PR2201MB1700.namprd22.prod.outlook.com> <69d1a917-b1f9-4142-afb0-f5c67abe7334.anqing.aq@alibaba-inc.com>, <CAOYVs2r0zJzbfw5L2Mck8VEJhtyfQtHwF-db5VG45HDTF0WoOQ@mail.gmail.com>
x-aliyun-mail-creator: W4_5657687_v5ForWebDing_NTMTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTVfMCkgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzc4LjAuMzkwNC43MCBTYWZhcmkvNTM3LjM2XQ
In-Reply-To: <CAOYVs2r0zJzbfw5L2Mck8VEJhtyfQtHwF-db5VG45HDTF0WoOQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_29147_4c0c1940_5dbc3279_353e78"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/EX4ytNZ1WnTtjTYwshRyVMdJeTc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 13:26:35 -0000

------=ALIBOUNDARY_29147_4c0c1940_5dbc3279_353e78
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

CkkgYmVsaWV2ZSB0aGlzIGNhbiBzYXZlIDEtUlRULgoKQXMgZm9yIHRoZSBwcml2YWN5IHJpc2ss
IG5ld190b2tlbiBmcmFtZSBjYW4gYmUgZGVsaXZlcmVkIHZpYSBoYW5kc2hha2UKCgoKLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tCkZyb206TWFydGVuIFNlZW1hbm4gPG1hcnRlbnNlZW1hbm5AZ21haWwuY29tPgpTZW5kIFRp
bWU6MjAxOeW5tDEx5pyIMeaXpSjmmJ/mnJ/kupQpIDIwOjU0ClRvOuWuieWLjSjojrPpgLgpIDxh
bnFpbmcuYXFAYWxpYmFiYS1pbmMuY29tPgpDYzpRVUlDIDxxdWljLWJvdW5jZXNAaWV0Zi5vcmc+
OyBxdWljIDxxdWljQGlldGYub3JnPjsganJpLmlldGYgPGpyaS5pZXRmQGdtYWlsLmNvbT47IG10
IDxtdEBsb3dlbnRyb3B5Lm5ldD47IG1pa2tlbGZqIDxtaWtrZWxmakBnbWFpbC5jb20+OyDliJjl
pKfpuY8o6bmP5oiQKSA8bWF4LmxkcEBhbGliYWJhLWluYy5jb20+ClN1YmplY3Q6UmU6IEZhc3Qg
QWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQKCkkgZG9uJ3Qgc2VlIGFueSBlbmhhbmNlZCBjbGll
bnQgZXhwZXJpZW5jZSwgc2luY2UgdGhlIGhhbmRzaGFrZSB0YWtlcyBleGFjdGx5IHRoZSBzYW1l
IG51bWJlciBvZiByb3VuZCB0cmlwcyB3aXRoIHlvdXIgcHJvcG9zYWwgYXMgd2l0aCB0aGUgY3Vy
cmVudCB2ZXJzaW9uIG9mIHRoZSBRVUlDIGRyYWZ0LgpTZW5kaW5nIE5FV19UT0tFTiBpbiBJbml0
aWFsIHBhY2tldHMgcHJvdmlkZXMgbm8gYmVuZWZpdCBvdmVyIHNlbmRpbmcgaXQgaW4gMS1SVFQg
cGFja2V0cywgYnV0IGNvbWVzIHdpdGggd29yc2UgcHJpdmFjeSBwcm9wZXJ0aWVzLCBzaW5jZSBJ
bml0aWFsIHBhY2tldHMgYXJlIG5vdCBlbmNyeXB0ZWQgYW5kIGNhbiB0aGVyZWZvcmUgYmUgcmVh
ZCBieSBvbi1wYXRoIG9ic2VydmVycy4KCk9uIEZyaSwgTm92IDEsIDIwMTkgYXQgNzozNyBQTSBR
aW5nIEFuIDxhbnFpbmcuYXFAYWxpYmFiYS1pbmMuY29tPiB3cm90ZToKCklmIHNvLCBmb3IgdGhl
IGZpcnN0IGNvbm5lY3Rpb24gYmV0d2VlbiBjbGllbnQgYW5kIHNlcnZlciwgc2VydmVyIGNhbiBj
aG9vc2UgdG8gZWxpbWluYXRlIHRoZSB1c2Ugb2YgUmV0cnkgcGFja2V0IGZvciB0b2tlbiBkZWxp
dmVyeSwgYW5kIHJlbHkgb24gaGFuZHNoYWtlIGVuY3J5cHRpb24gbGF5ZXIgdG8gcHJvdmUgcmV0
dXJuIHJvdXRhYmlsaXR5LiAgSW4gYWRkaXRpb24sIE5ld19Ub2tlbiBmcmFtZSBpcyB1c2VkIGJ5
IHNlcnZlciwgdmlhIGkuZS4gdGhlIEluaXRpYWwgcGFja2V0LCB0byBwcm92aWRlIHRoZSBjbGll
bnQgd2l0aCBhbiBhZGRyZXNzIHZhbGlkYXRpb24gdG9rZW4gdGhhdCBjYW4gYmUgdXNlZCB0byB2
YWxpZGF0ZSBmdXR1cmUgY29ubmVjdGlvbnMuCgpJdCBjYW4gZW5oYW5jZSB0aGUgZXhwZXJpZW5j
ZSBpbiBjbGllbnQgc2lkZSBmb3IgdGhlIGZpcnN0IGNvbm5lY3Rpb24gZXN0YWJsaXNobWVudC4K
Ckkgc3VibWl0dGVkIHRoZSBkcmFmdCwgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2Mv
ZHJhZnQtYW4tZmFzdC1hZGRyZXNzLXZhbGlkYXRpb24vCgpRaW5nCgoKCi0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQpGcm9t
Ok1pa2UgQmlzaG9wIDxtYmlzaG9wQGV2ZXF1ZWZvdS5iZT4KU2VuZCBUaW1lOjIwMTnlubQxMeac
iDHml6Uo5pif5pyf5LqUKSAwMDowNgpUbzrlronli40o6I6z6YC4KSA8YW5xaW5nLmFxQGFsaWJh
YmEtaW5jLmNvbT47IHF1aWMgPHF1aWNAaWV0Zi5vcmc+OyBqcmkuaWV0ZiA8anJpLmlldGZAZ21h
aWwuY29tPjsgbXQgPG10QGxvd2VudHJvcHkubmV0PjsgbWlra2VsZmogPG1pa2tlbGZqQGdtYWls
LmNvbT4KU3ViamVjdDpSRTogRmFzdCBBZGRyZXNzIFZhbGlkYXRpb24gLSBhYm91dAoKQXMgTWFy
dGluIHBvaW50ZWQgb3V0IGluIHRoZSBlLW1haWwgeW91IHJlcGxpZWQgdG8sIGlmIHRoZSBzZXJ2
ZXIgaXMgd2lsbGluZyB0byBtYWludGFpbiBzdGF0ZSwgYW55IHBhY2tldCBhdCB0aGUgSGFuZHNo
YWtlIGVuY3J5cHRpb24gbGF5ZXIgcHJvdmVzIHJldHVybiByb3V0YWJpbGl0eS4gIFRoZXJlIHNl
ZW1zIHRvIGJlIG5vIG5lZWQgZm9yIGEgc2VwYXJhdGUgYWRkcmVzcyB2YWxpZGF0aW9uIG1lY2hh
bmlzbSBpZiB0aGUgc2VydmVyIGlzIHdpbGxpbmcgdG8gcHJvY2VlZCB3aXRoIHRoZSBoYW5kc2hh
a2UuCkZyb206IFFVSUMgPHF1aWMtYm91bmNlc0BpZXRmLm9yZz4gT24gQmVoYWxmIE9mICBRaW5n
IEFuClNlbnQ6IFRodXJzZGF5LCBPY3RvYmVyIDMxLCAyMDE5IDg6NTYgQU0KVG86IHF1aWMgPHF1
aWNAaWV0Zi5vcmc+OyBqcmkuaWV0ZiA8anJpLmlldGZAZ21haWwuY29tPjsgbXQgPG10QGxvd2Vu
dHJvcHkubmV0PjsgbWlra2VsZmogPG1pa2tlbGZqQGdtYWlsLmNvbT4KU3ViamVjdDogUmU6IEZh
c3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQKCgpUbyBjbGFyaWZ5LCB0aGUgcHJvcG9zYWwg
aXMgbm90IHRvIHJlcGxhY2UgdGhlIGV4aXN0aW5nIFJldHJ5LWJhc2VkIHZhbGlkYXRpb24sIGJ1
dCB0byBwcm92aWRlIGFub3RoZXIgb3B0aW9uIGZvciBzZXJ2ZXIgdG8gZG8gdGhlIGNsaWVudCB2
YWxpZGF0aW9uLgoKSSB1bmRlcnN0YW5kIHRoYXQgaW4gc2VydmVyIHNpZGUsIGV4Y2hhbmdpbmcg
dGhlIHRva2VuIGF0IHRoZSBIYW5kc2hha2UgZW5jcnlwdGlvbiBsZXZlbCB3aWxsIG1ha2UgdGhl
IHNlcnZlciBzdGFydCB0byBtYWludGFpbiBoYW5kc2hha2Ugc3RhdGVzLiBCdXQgaW4gY2xpZW50
IHNpZGUsIGl0IGNhbiBhY2NlbGVyYXRlIHRoZSBjb25uZWN0aW9uIGVzdGFibGlzaG1lbnQgZnJv
bSBjbGllbnQgdG8gc2VydmVyLgoKQW5kIGl0IGlzIHRoZSBzZXJ2ZXIncyBkZWNpc2lvbiB3aGV0
aGVyIHRvIGV4Y2hhbmdlIHRva2VuIGluIFJldHJ5IG9yIGluIEhhbmRzaGFrZS4gSWYgc2VydmVy
IGNob29zZXMgdG8gYWNjZXB0IHRoZSBjb3N0IGJyb3VnaHQgYnkgdG9rZW4gZXhjaGFuZ2luZyBp
biBIYW5kc2hha2UsIGl0IHdpbGwgYnJpbmcgbW9yZSBlbmhhbmNlZCBleHBlcmllbmNlIGluIGNs
aWVudCBzaWRlLgoKCkJSLApRaW5nCgoKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCkZyb206TWFydGluIFRob21zb24gPG10
QGxvd2VudHJvcHkubmV0PgpTZW5kIFRpbWU6MjAxOeW5tDEw5pyIMzHml6Uo5pif5pyf5ZubKSAw
NjowNwpUbzpxdWljIDxxdWljQGlldGYub3JnPgpTdWJqZWN0OlJlOiBGYXN0IEFkZHJlc3MgVmFs
aWRhdGlvbiAtIGFib3V0CgpBbHNvIG5vdGUgdGhhdCBleGNoYW5nZSBvZiBIYW5kc2hha2UgcGFj
a2V0cyBwcm92aWRlcyBwcm9vZiBvZiByZXR1cm4gcm91dGVhYmlsaXR5IHZpYSB0aGUgdXNlIG9m
IHRoZSBlbmNyeXB0aW9uIGtleXMsIHNvIHRoZXJlIGlzIG5vIG5lZWQgdG8gZXhjaGFuZ2UgdG9r
ZW5zIGF0IHRoYXQgbGV2ZWwuCgogT24gVGh1LCBPY3QgMzEsIDIwMTksIGF0IDAzOjI5LCBNaWtl
IEJpc2hvcCB3cm90ZToKID4gIAogPiBUaGUgYWR2YW50YWdlIG9mIHVzaW5nIFJldHJ5LCBob3dl
dmVyLCBpcyB0aGF0IHRoZSBzZXJ2ZXIgaXMgYWJsZSB0byAKID4ga2VlcCBtaW5pbWFsIChpZiBh
bnkpIHN0YXRlIGFib3V0IHRoZSBjbGllbnQuIEV4Y2hhbmdpbmcgdGhlIHRva2VuIGF0IAogPiB0
aGUgSGFuZHNoYWtlIGVuY3J5cHRpb24gbGV2ZWwgbWVhbnMgdGhlIHNlcnZlciBpcyBhbHJlYWR5
IGRvaW5nIHdvcmsgCiA+IGFuZCBtYWludGFpbmluZyBzdGF0ZSBpbiBvcmRlciB0byBwcm9jZXNz
IHRoZSBoYW5kc2hha2UsIHdoaWNoIGlzIAogPiBleGFjdGx5IHdoYXQgdGhlIHNlcnZlciBpcyB0
cnlpbmcgdG8gYXZvaWQuCiA+IAogPiAKID4gKkZyb206KiBRVUlDIDxxdWljLWJvdW5jZXNAaWV0
Zi5vcmc+ICpPbiBCZWhhbGYgT2YgKiBRaW5nIEFuCiA+ICpTZW50OiogV2VkbmVzZGF5LCBPY3Rv
YmVyIDMwLCAyMDE5IDk6NDEgQU0KID4gKlRvOiogcXVpYyA8cXVpY0BpZXRmLm9yZz47IGpyaS5p
ZXRmIDxqcmkuaWV0ZkBnbWFpbC5jb20+OyBtdCAKID4gPG10QGxvd2VudHJvcHkubmV0PgogPiAq
Q2M6KiDliJjlpKfpuY8o6bmP5oiQKSA8bWF4LmxkcEBhbGliYWJhLWluYy5jb20+CiA+ICpTdWJq
ZWN0OiogRmFzdCBBZGRyZXNzIFZhbGlkYXRpb24gLSBhYm91dAogPiAKID4gCiA+IAogPiAKID4g
SGkgTWFydGluLCBKYW5hLCAKID4gCiA+IEkgcmVhZCB0aHJvdWdoIGh0dHBzOi8vd3d3LmlldGYu
b3JnL2lkL2RyYWZ0LWlldGYtcXVpYy10cmFuc3BvcnQtMjMudHh0IAogPiBhbmQgaGF2ZSBhIGZl
dyBjb21tZW50cyBhbmQgaWRlYXMgdG8gZGlzY3Vzcy4KID4gCiA+IAogPiBbUVVJQy1UcmFuc10g
ZGVmaW5lcyBhIHRva2VuIGJhc2VkIHNjaGVtZSB0byBmYWNpbGl0YXRlIGFkZHJlc3MgCiA+IHZh
bGlkYXRpb24gb2YgYSBjbGllbnQuIFRoZSB0b2tlbiBNVVNUIGJlIGNvdmVyZWQgYnkgaW50ZWdy
aXR5IAogPiBwcm90ZWN0aW9uIGFnYWluc3QgbW9kaWZpY2F0aW9uIG9yIGZhbHNpZmljYXRpb24g
YnkgY2xpZW50cy4gVGhlIHNlcnZlciAKID4gcmVtZW1iZXJzIHRoZSB2YWx1ZSBpdCBzZW5kcyB0
byBjbGllbnRzIGFuZCB2YWxpZGF0ZXMgdGhlIHRva2VuIHNlbnQgCiA+IGJhY2sgZnJvbSBhIGNs
aWVudC4gSW4gaXRzIGRlc2lnbiwgUmV0cnkgcGFja2V0IGlzIHVzZWQgdG8gZGVsaXZlciB0aGUg
CiA+IHRva2VuIHRvIGEgY2xpZW50IHdoaWNoIGFkZHJlc3MgaGFzIG5vdCB5ZXQgYmVlbiB2YWxp
ZGF0ZWQuIEl0IHZvaWRzIAogPiB0aGUgZmlyc3QgdHJhbnNtaXNzaW9uIG9mIHRoZSBJbml0aWFs
IHBhY2tldCBzZW50IGJ5IHRoZSBjbGllbnQsIGFuZCAKID4gdHJpZ2dlcnMgYSBzZWNvbmQgSW5p
dGlhbCBwYWNrZXQgdG8gYmUgc2VudCB3aXRoIHRoZSB0b2tlbi4gVGhlIAogPiBleGNoYW5nZSBv
ZiB0b2tlbiB3aWxsIGNhdXNlIGxvbmdlciBjb25uZWN0aW9uIGVzdGFibGlzaG1lbnQgZGVsYXkg
Zm9yIAogPiBhIGNsaWVudC4KID4gCiA+IAogPiBUbyBpbXByb3ZlIHRoZSBlZmZpY2llbmN5IG9m
IGFkZHJlc3MgdmFsaWRhdGlvbiBkdXJpbmcgaGFuZHNoYWtlLCBvbmUgCiA+IGlkZWEgaXMgdGhh
dCB0aGUgc2FtZSB0b2tlbiBjYW4gYmUgZXhjaGFuZ2VkIHZpYSBhIGRpZmZlcmVudCBjb250YWlu
ZXIgCiA+IGkuZS4gdGhlIEhhbmRzaGFrZSBwYWNrZXQsIHRoYXQgZWxpbWluYXRlcyB0aGUgdXNl
IG9mIFJldHJ5IHBhY2tldCBmb3IgCiA+IHRva2VuIGRlbGl2ZXJ5LiAKID4gCiA+IAogPiBJIGFt
IHdvcmtpbmcgb24gdGhlIGNvbXBsZXRlIGRyYWZ0IGFuZCB3aWxsIHN1Ym1pdCBpdCBieSBGcmlk
YXkuIEJlZm9yZSAKID4gdGhhdCwgaG9wZSB0aGlzIGNhbiBiZSBkaXNjdXNzZWQgaW4gZW1haWwg
Zmlyc3QuCiA+IAogPiAKID4gQlIsCiA+IAogPiBRaW5nIEFuCiA+CgoKCg==
------=ALIBOUNDARY_29147_4c0c1940_5dbc3279_353e78
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64

PGRpdiBjbGFzcz0iX19hbGl5dW5fZW1haWxfYm9keV9ibG9jayI+PGRpdiAgc3R5bGU9ImxpbmUt
aGVpZ2h0OjEuNztmb250LWZhbWlseTpUYWhvbWEsQXJpYWwsU1RIZWl0aSxTaW1TdW47Zm9udC1z
aXplOjE0LjBweDtjb2xvcjojMDAwMDAwOyI+PGRpdiAgc3R5bGU9ImNsZWFyOmJvdGg7Ij48YnIg
PjwvZGl2PjxkaXYgIHN0eWxlPSJjbGVhcjpib3RoOyI+SSBiZWxpZXZlIHRoaXMgY2FuIHNhdmUg
MS1SVFQuPC9kaXY+PGRpdiAgc3R5bGU9ImNsZWFyOmJvdGg7Ij48YnIgPjwvZGl2PjxkaXYgIHN0
eWxlPSJjbGVhcjpib3RoOyI+QXMgZm9yIHRoZSBwcml2YWN5IHJpc2ssIG5ld190b2tlbiBmcmFt
ZSBjYW4gYmUgZGVsaXZlcmVkIHZpYSBoYW5kc2hha2U8L2Rpdj48ZGl2ICBzdHlsZT0iY2xlYXI6
Ym90aDsiPjxiciA+PC9kaXY+PGRpdiAgc3R5bGU9ImNsZWFyOmJvdGg7Ij48YnIgPjwvZGl2Pjxi
bG9ja3F1b3RlICBfcXVvdGU9IjEiIHN0eWxlPSJtYXJnaW4tcmlnaHQ6LjBweDttYXJnaW4tdG9w
Oi4wcHg7bWFyZ2luLWJvdHRvbTouMHB4O2ZvbnQtZmFtaWx5OlRhaG9tYSxBcmlhbCxTVEhlaXRp
LFNpbVN1bjtmb250LXNpemU6MTQuMHB4O2NvbG9yOiMwMDAwMDA7Ij48ZGl2ICBzdHlsZT0iY2xl
YXI6Ym90aDsiPi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLTwvZGl2PjxkaXYgIHN0eWxlPSJjbGVhcjpib3RoOyI+RnJvbTpN
YXJ0ZW4gU2VlbWFubiAmbHQ7bWFydGVuc2VlbWFubkBnbWFpbC5jb20mZ3Q7PC9kaXY+PGRpdiAg
c3R5bGU9ImNsZWFyOmJvdGg7Ij5TZW5kIFRpbWU6MjAxOeW5tDEx5pyIMeaXpSjmmJ/mnJ/kupQp
IDIwOjU0PC9kaXY+PGRpdiAgc3R5bGU9ImNsZWFyOmJvdGg7Ij5Ubzrlronli40o6I6z6YC4KSAm
bHQ7YW5xaW5nLmFxQGFsaWJhYmEtaW5jLmNvbSZndDs8L2Rpdj48ZGl2ICBzdHlsZT0iY2xlYXI6
Ym90aDsiPkNjOlFVSUMgJmx0O3F1aWMtYm91bmNlc0BpZXRmLm9yZyZndDs7IHF1aWMgJmx0O3F1
aWNAaWV0Zi5vcmcmZ3Q7OyBqcmkuaWV0ZiAmbHQ7anJpLmlldGZAZ21haWwuY29tJmd0OzsgbXQg
Jmx0O210QGxvd2VudHJvcHkubmV0Jmd0OzsgbWlra2VsZmogJmx0O21pa2tlbGZqQGdtYWlsLmNv
bSZndDs7IOWImOWkp+m5jyjpuY/miJApICZsdDttYXgubGRwQGFsaWJhYmEtaW5jLmNvbSZndDs8
L2Rpdj48ZGl2ICBzdHlsZT0iY2xlYXI6Ym90aDsiPlN1YmplY3Q6UmU6IEZhc3QgQWRkcmVzcyBW
YWxpZGF0aW9uIC0gYWJvdXQ8L2Rpdj48ZGl2ICBzdHlsZT0iY2xlYXI6Ym90aDsiPjxiciA+PC9k
aXY+PGRpdiA+PGRpdiA+SSBkb24ndCBzZWUgYW55IGVuaGFuY2VkIGNsaWVudCBleHBlcmllbmNl
LCBzaW5jZSB0aGUgaGFuZHNoYWtlIHRha2VzIGV4YWN0bHkgdGhlIHNhbWUgbnVtYmVyIG9mIHJv
dW5kIHRyaXBzIHdpdGggeW91ciBwcm9wb3NhbCBhcyB3aXRoIHRoZSBjdXJyZW50IHZlcnNpb24g
b2YgdGhlIFFVSUMgZHJhZnQuPGJyID48L2Rpdj48ZGl2ID5TZW5kaW5nIE5FV19UT0tFTiBpbiBJ
bml0aWFsIHBhY2tldHMgcHJvdmlkZXMgbm8gYmVuZWZpdCBvdmVyIHNlbmRpbmcgaXQgaW4gMS1S
VFQgcGFja2V0cywgYnV0IGNvbWVzIHdpdGggd29yc2UgcHJpdmFjeSBwcm9wZXJ0aWVzLCBzaW5j
ZSBJbml0aWFsIHBhY2tldHMgYXJlIG5vdCBlbmNyeXB0ZWQgYW5kIGNhbiB0aGVyZWZvcmUgYmUg
cmVhZCBieSBvbi1wYXRoIG9ic2VydmVycy48YnIgPjwvZGl2PjwvZGl2PjxiciA+PGRpdiAgY2xh
c3M9ImdtYWlsX3F1b3RlIj48ZGl2ICBjbGFzcz0iZ21haWxfYXR0ciI+T24gRnJpLCBOb3YgMSwg
MjAxOSBhdCA3OjM3IFBNIFFpbmcgQW4gJmx0OzxhICBocmVmPSJtYWlsdG86YW5xaW5nLmFxQGFs
aWJhYmEtaW5jLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmFucWluZy5hcUBhbGliYWJhLWluYy5jb208
L2E+Jmd0OyB3cm90ZTo8YnIgPjwvZGl2PjxkaXYgIHN0eWxlPSJtYXJnaW46MTQuMHB4IC4wcHg7
Ij48ZGl2ICBzdHlsZT0ibGluZS1oZWlnaHQ6MS43O2ZvbnQtZmFtaWx5OlRhaG9tYSxBcmlhbCxT
VEhlaXRpLFNpbVN1bjtmb250LXNpemU6MTQuMHB4O2NvbG9yOiMwMDAwMDA7Ij48ZGl2ICBzdHls
ZT0iY2xlYXI6Ym90aDsiPjxiciA+PC9kaXY+PGRpdiAgc3R5bGU9ImNsZWFyOmJvdGg7Ij5JZiBz
bywgZjxzcGFuID5vciZuYnNwO3RoZSZuYnNwO2ZpcnN0PC9zcGFuPiZuYnNwO2Nvbm5lY3Rpb24m
bmJzcDtiZXR3ZWVuJm5ic3A7Y2xpZW50Jm5ic3A7YW5kJm5ic3A7c2VydmVyLCBzZXJ2ZXIgY2Fu
IGNob29zZSB0byBlbGltaW5hdGUmbmJzcDt0aGUmbmJzcDt1c2UmbmJzcDtvZiZuYnNwO1JldHJ5
IHBhY2tldCZuYnNwO2ZvciZuYnNwO3Rva2VuJm5ic3A7ZGVsaXZlcnksIGFuZCByZWx5Jm5ic3A7
b24mbmJzcDtoYW5kc2hha2UmbmJzcDtlbmNyeXB0aW9uJm5ic3A7bGF5ZXImbmJzcDt0byBwcm92
ZSZuYnNwO3JldHVybiByb3V0YWJpbGl0eS4mbmJzcDsgSW4mbmJzcDthZGRpdGlvbiwgTmV3X1Rv
a2VuIGZyYW1lIGlzJm5ic3A7dXNlZCZuYnNwO2J5IHNlcnZlciwmbmJzcDt2aWEmbmJzcDtpLmUu
Jm5ic3A7dGhlJm5ic3A7SW5pdGlhbCZuYnNwO3BhY2tldCwmbmJzcDt0byZuYnNwO3Byb3ZpZGUm
bmJzcDt0aGUmbmJzcDtjbGllbnQmbmJzcDt3aXRoJm5ic3A7YW4gYWRkcmVzcyZuYnNwO3ZhbGlk
YXRpb24mbmJzcDt0b2tlbiZuYnNwO3RoYXQmbmJzcDtjYW4mbmJzcDtiZSZuYnNwO3VzZWQmbmJz
cDt0byZuYnNwO3ZhbGlkYXRlJm5ic3A7ZnV0dXJlPHNwYW4gPiZuYnNwO2Nvbm5lY3Rpb25zLjwv
c3Bhbj48L2Rpdj48ZGl2ICBzdHlsZT0iY2xlYXI6Ym90aDsiPjxzcGFuID48YnIgPjwvc3Bhbj48
L2Rpdj48ZGl2ICBzdHlsZT0iY2xlYXI6Ym90aDsiPjxzcGFuID5JdCBjYW4gZW5oYW5jZSB0aGUg
ZXhwZXJpZW5jZSBpbiBjbGllbnQgc2lkZSBmb3IgdGhlIGZpcnN0IGNvbm5lY3Rpb24gZXN0YWJs
aXNobWVudC48L3NwYW4+PC9kaXY+PGRpdiAgc3R5bGU9ImNsZWFyOmJvdGg7Ij48c3BhbiA+PGJy
ID48L3NwYW4+PC9kaXY+PGRpdiAgc3R5bGU9ImNsZWFyOmJvdGg7Ij48c3BhbiA+SSBzdWJtaXR0
ZWQgdGhlIGRyYWZ0LCZuYnNwOzxhICBocmVmPSJodHRwczovL2RhdGF0cmFja2VyLmlldGYub3Jn
L2RvYy9kcmFmdC1hbi1mYXN0LWFkZHJlc3MtdmFsaWRhdGlvbi8iIHRhcmdldD0iX2JsYW5rIj5o
dHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1hbi1mYXN0LWFkZHJlc3MtdmFs
aWRhdGlvbi88L2E+PC9zcGFuPjwvZGl2PjxkaXYgIHN0eWxlPSJjbGVhcjpib3RoOyI+PHNwYW4g
PjxiciA+PC9zcGFuPjwvZGl2PjxkaXYgIHN0eWxlPSJjbGVhcjpib3RoOyI+PHNwYW4gPlFpbmc8
L3NwYW4+PC9kaXY+PGRpdiAgc3R5bGU9ImNsZWFyOmJvdGg7Ij48L2Rpdj48ZGl2ICBzdHlsZT0i
Y2xlYXI6Ym90aDsiPjxiciA+PC9kaXY+PGRpdiAgc3R5bGU9ImNsZWFyOmJvdGg7Ij48YnIgPjwv
ZGl2PjxkaXYgIHN0eWxlPSJjbGVhcjpib3RoOyI+PGJyID48L2Rpdj48ZGl2ICBzdHlsZT0iY2xl
YXI6Ym90aDsiPi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLTwvZGl2PjxkaXYgIHN0eWxlPSJjbGVhcjpib3RoOyI+RnJvbTpN
aWtlIEJpc2hvcCAmbHQ7PGEgIGhyZWY9Im1haWx0bzptYmlzaG9wQGV2ZXF1ZWZvdS5iZSIgdGFy
Z2V0PSJfYmxhbmsiPm1iaXNob3BAZXZlcXVlZm91LmJlPC9hPiZndDs8L2Rpdj48ZGl2ICBzdHls
ZT0iY2xlYXI6Ym90aDsiPlNlbmQgVGltZToyMDE55bm0MTHmnIgx5pelKOaYn+acn+S6lCkgMDA6
MDY8L2Rpdj48ZGl2ICBzdHlsZT0iY2xlYXI6Ym90aDsiPlRvOuWuieWLjSjojrPpgLgpICZsdDs8
YSAgaHJlZj0ibWFpbHRvOmFucWluZy5hcUBhbGliYWJhLWluYy5jb20iIHRhcmdldD0iX2JsYW5r
Ij5hbnFpbmcuYXFAYWxpYmFiYS1pbmMuY29tPC9hPiZndDs7IHF1aWMgJmx0OzxhICBocmVmPSJt
YWlsdG86cXVpY0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPnF1aWNAaWV0Zi5vcmc8L2E+Jmd0
OzsganJpLmlldGYgJmx0OzxhICBocmVmPSJtYWlsdG86anJpLmlldGZAZ21haWwuY29tIiB0YXJn
ZXQ9Il9ibGFuayI+anJpLmlldGZAZ21haWwuY29tPC9hPiZndDs7IG10ICZsdDs8YSAgaHJlZj0i
bWFpbHRvOm10QGxvd2VudHJvcHkubmV0IiB0YXJnZXQ9Il9ibGFuayI+bXRAbG93ZW50cm9weS5u
ZXQ8L2E+Jmd0OzsgbWlra2VsZmogJmx0OzxhICBocmVmPSJtYWlsdG86bWlra2VsZmpAZ21haWwu
Y29tIiB0YXJnZXQ9Il9ibGFuayI+bWlra2VsZmpAZ21haWwuY29tPC9hPiZndDs8L2Rpdj48ZGl2
ICBzdHlsZT0iY2xlYXI6Ym90aDsiPlN1YmplY3Q6UkU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9u
IC0gYWJvdXQ8L2Rpdj48ZGl2ICBzdHlsZT0iY2xlYXI6Ym90aDsiPjxiciA+PC9kaXY+PGRpdiA+
PHAgIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46LjBweDtmb250LXNpemU6MTQuN3B4
O2ZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjsiPkFzIE1hcnRpbiBwb2ludGVkIG91dCBp
biB0aGUgZS1tYWlsIHlvdSByZXBsaWVkIHRvLCBpZiB0aGUgc2VydmVyIGlzIHdpbGxpbmcgdG8g
bWFpbnRhaW4gc3RhdGUsIGFueSBwYWNrZXQgYXQgdGhlIEhhbmRzaGFrZSBlbmNyeXB0aW9uIGxh
eWVyIHByb3ZlcyByZXR1cm4gcm91dGFiaWxpdHkuJm5ic3A7IFRoZXJlIHNlZW1zIHRvIGJlIG5v
IG5lZWQgZm9yIGEgc2VwYXJhdGUgYWRkcmVzcyB2YWxpZGF0aW9uIG1lY2hhbmlzbQogaWYgdGhl
IHNlcnZlciBpcyB3aWxsaW5nIHRvIHByb2NlZWQgd2l0aCB0aGUgaGFuZHNoYWtlLjwvcD48cCAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjouMHB4O2ZvbnQtc2l6ZToxNC43cHg7Zm9u
dC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyI+Jm5ic3A7PC9wPjxwICBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibWFyZ2luOi4wcHg7Zm9udC1zaXplOjE0LjdweDtmb250LWZhbWlseTpDYWxp
YnJpLHNhbnMtc2VyaWY7Ij48YiA+RnJvbTo8L2I+IFFVSUMgJmx0OzxhICBocmVmPSJtYWlsdG86
cXVpYy1ib3VuY2VzQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+cXVpYy1ib3VuY2VzQGlldGYu
b3JnPC9hPiZndDsgPGIgPk9uIEJlaGFsZiBPZiA8L2I+ClFpbmcgQW48YnIgPjxiID5TZW50Ojwv
Yj4gVGh1cnNkYXksIE9jdG9iZXIgMzEsIDIwMTkgODo1NiBBTTxiciA+PGIgPlRvOjwvYj4gcXVp
YyAmbHQ7PGEgIGhyZWY9Im1haWx0bzpxdWljQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+cXVp
Y0BpZXRmLm9yZzwvYT4mZ3Q7OyBqcmkuaWV0ZiAmbHQ7PGEgIGhyZWY9Im1haWx0bzpqcmkuaWV0
ZkBnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj5qcmkuaWV0ZkBnbWFpbC5jb208L2E+Jmd0Ozsg
bXQgJmx0OzxhICBocmVmPSJtYWlsdG86bXRAbG93ZW50cm9weS5uZXQiIHRhcmdldD0iX2JsYW5r
Ij5tdEBsb3dlbnRyb3B5Lm5ldDwvYT4mZ3Q7OyBtaWtrZWxmaiAmbHQ7PGEgIGhyZWY9Im1haWx0
bzptaWtrZWxmakBnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj5taWtrZWxmakBnbWFpbC5jb208
L2E+Jmd0OzxiciA+PGIgPlN1YmplY3Q6PC9iPiBSZTogRmFzdCBBZGRyZXNzIFZhbGlkYXRpb24g
LSBhYm91dDwvcD48cCAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjouMHB4O2ZvbnQt
c2l6ZToxNC43cHg7Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyI+Jm5ic3A7PC9wPjxk
aXYgPjxkaXYgPjxwICBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOi4wcHg7Zm9udC1z
aXplOjE0LjdweDtmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7Ij48c3BhbiAgc3R5bGU9
ImZvbnQtc2l6ZToxNC4wcHg7Zm9udC1mYW1pbHk6VGFob21hLHNhbnMtc2VyaWY7Y29sb3I6Ymxh
Y2s7Ij4mbmJzcDs8L3NwYW4+PC9wPjwvZGl2PjxkaXYgPjxwICBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibWFyZ2luOi4wcHg7Zm9udC1zaXplOjE0LjdweDtmb250LWZhbWlseTpDYWxpYnJpLHNh
bnMtc2VyaWY7Ij48c3BhbiAgc3R5bGU9ImZvbnQtc2l6ZToxNC4wcHg7Zm9udC1mYW1pbHk6VGFo
b21hLHNhbnMtc2VyaWY7Y29sb3I6YmxhY2s7Ij4mbmJzcDs8L3NwYW4+PC9wPjwvZGl2PjxkaXYg
PjxwICBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOi4wcHg7Zm9udC1zaXplOjE0Ljdw
eDtmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7Ij48c3BhbiAgc3R5bGU9ImZvbnQtc2l6
ZToxNC4wcHg7Zm9udC1mYW1pbHk6VGFob21hLHNhbnMtc2VyaWY7Y29sb3I6YmxhY2s7Ij5UbyBj
bGFyaWZ5LCB0aGUgcHJvcG9zYWwgaXMgbm90IHRvIHJlcGxhY2UgdGhlIGV4aXN0aW5nIFJldHJ5
LWJhc2VkIHZhbGlkYXRpb24sIGJ1dCB0byBwcm92aWRlIGFub3RoZXIgb3B0aW9uIGZvciBzZXJ2
ZXIgdG8gZG8gdGhlIGNsaWVudCB2YWxpZGF0aW9uLjwvc3Bhbj48L3A+PC9kaXY+PGRpdiA+PHAg
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46LjBweDtmb250LXNpemU6MTQuN3B4O2Zv
bnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjsiPjxzcGFuICBzdHlsZT0iZm9udC1zaXplOjE0
LjBweDtmb250LWZhbWlseTpUYWhvbWEsc2Fucy1zZXJpZjtjb2xvcjpibGFjazsiPiZuYnNwOzwv
c3Bhbj48L3A+PC9kaXY+PGRpdiA+PHAgIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46
LjBweDtmb250LXNpemU6MTQuN3B4O2ZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjsiPjxz
cGFuICBzdHlsZT0iZm9udC1zaXplOjE0LjBweDtmb250LWZhbWlseTpUYWhvbWEsc2Fucy1zZXJp
Zjtjb2xvcjpibGFjazsiPkkgdW5kZXJzdGFuZCB0aGF0IGluIHNlcnZlciBzaWRlLCBlPHNwYW4g
IHN0eWxlPSJiYWNrZ3JvdW5kOm5vbmUgLjAlIC4wJSByZXBlYXQgc2Nyb2xsIHdoaXRlOyI+eGNo
YW5naW5nJm5ic3A7dGhlJm5ic3A7dG9rZW4mbmJzcDthdCZuYnNwO3RoZSZuYnNwO0hhbmRzaGFr
ZSZuYnNwO2VuY3J5cHRpb24mbmJzcDtsZXZlbCB3aWxsIG1ha2UgdGhlIHNlcnZlciBzdGFydCB0
byBtYWludGFpbiBoYW5kc2hha2UKIHN0YXRlcy4gQnV0IGluIGNsaWVudCBzaWRlLCBpdCBjYW4g
YWNjZWxlcmF0ZSB0aGUgY29ubmVjdGlvbiBlc3RhYmxpc2htZW50IGZyb20gY2xpZW50IHRvIHNl
cnZlci48L3NwYW4+PC9zcGFuPjwvcD48L2Rpdj48ZGl2ID48cCAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1hcmdpbjouMHB4O2ZvbnQtc2l6ZToxNC43cHg7Zm9udC1mYW1pbHk6Q2FsaWJyaSxz
YW5zLXNlcmlmOyI+PHNwYW4gIHN0eWxlPSJmb250LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5OlRh
aG9tYSxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrOyI+Jm5ic3A7PC9zcGFuPjwvcD48L2Rpdj48ZGl2
ID48cCAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjouMHB4O2ZvbnQtc2l6ZToxNC43
cHg7Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyI+PHNwYW4gIHN0eWxlPSJmb250LXNp
emU6MTQuMHB4O2ZvbnQtZmFtaWx5OlRhaG9tYSxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrO2JhY2tn
cm91bmQ6bm9uZSAuMCUgLjAlIHJlcGVhdCBzY3JvbGwgd2hpdGU7Ij5BbmQgaXQgaXMgdGhlIHNl
cnZlcidzIGRlY2lzaW9uIHdoZXRoZXIgdG8gZXhjaGFuZ2UgdG9rZW4gaW4gUmV0cnkgb3IgaW4g
SGFuZHNoYWtlLiBJZiBzZXJ2ZXIgY2hvb3NlcyB0byBhY2NlcHQgdGhlIGNvc3QgYnJvdWdodCBi
eSB0b2tlbiBleGNoYW5naW5nCiBpbiBIYW5kc2hha2UsIGl0IHdpbGwgYnJpbmcgbW9yZSBlbmhh
bmNlZCBleHBlcmllbmNlIGluIGNsaWVudCBzaWRlLjwvc3Bhbj48c3BhbiAgc3R5bGU9ImZvbnQt
c2l6ZToxNC4wcHg7Zm9udC1mYW1pbHk6VGFob21hLHNhbnMtc2VyaWY7Y29sb3I6YmxhY2s7Ij48
L3NwYW4+PC9wPjwvZGl2PjxkaXYgPjxwICBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2lu
Oi4wcHg7Zm9udC1zaXplOjE0LjdweDtmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7Ij48
c3BhbiAgc3R5bGU9ImZvbnQtc2l6ZToxNC4wcHg7Zm9udC1mYW1pbHk6VGFob21hLHNhbnMtc2Vy
aWY7Y29sb3I6YmxhY2s7Ij4mbmJzcDs8L3NwYW4+PC9wPjwvZGl2PjxkaXYgPjxwICBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOi4wcHg7Zm9udC1zaXplOjE0LjdweDtmb250LWZhbWls
eTpDYWxpYnJpLHNhbnMtc2VyaWY7Ij48c3BhbiAgc3R5bGU9ImZvbnQtc2l6ZToxNC4wcHg7Zm9u
dC1mYW1pbHk6VGFob21hLHNhbnMtc2VyaWY7Y29sb3I6YmxhY2s7Ij4mbmJzcDs8L3NwYW4+PC9w
PjwvZGl2PjxkaXYgPjxwICBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOi4wcHg7Zm9u
dC1zaXplOjE0LjdweDtmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7Ij48c3BhbiAgc3R5
bGU9ImZvbnQtc2l6ZToxNC4wcHg7Zm9udC1mYW1pbHk6VGFob21hLHNhbnMtc2VyaWY7Y29sb3I6
YmxhY2s7YmFja2dyb3VuZDpub25lIC4wJSAuMCUgcmVwZWF0IHNjcm9sbCB3aGl0ZTsiPkJSLDwv
c3Bhbj48c3BhbiAgc3R5bGU9ImZvbnQtc2l6ZToxNC4wcHg7Zm9udC1mYW1pbHk6VGFob21hLHNh
bnMtc2VyaWY7Y29sb3I6YmxhY2s7Ij48L3NwYW4+PC9wPjwvZGl2PjxkaXYgPjxwICBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOi4wcHg7Zm9udC1zaXplOjE0LjdweDtmb250LWZhbWls
eTpDYWxpYnJpLHNhbnMtc2VyaWY7Ij48c3BhbiAgc3R5bGU9ImZvbnQtc2l6ZToxNC4wcHg7Zm9u
dC1mYW1pbHk6VGFob21hLHNhbnMtc2VyaWY7Y29sb3I6YmxhY2s7YmFja2dyb3VuZDpub25lIC4w
JSAuMCUgcmVwZWF0IHNjcm9sbCB3aGl0ZTsiPlFpbmc8L3NwYW4+PHNwYW4gIHN0eWxlPSJmb250
LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5OlRhaG9tYSxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrOyI+
PC9zcGFuPjwvcD48L2Rpdj48ZGl2ID48cCAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdp
bjouMHB4O2ZvbnQtc2l6ZToxNC43cHg7Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyI+
PHNwYW4gIHN0eWxlPSJmb250LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5OlRhaG9tYSxzYW5zLXNl
cmlmO2NvbG9yOmJsYWNrOyI+Jm5ic3A7PC9zcGFuPjwvcD48L2Rpdj48ZGl2ID48cCAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjouMHB4O2ZvbnQtc2l6ZToxNC43cHg7Zm9udC1mYW1p
bHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyI+PHNwYW4gIHN0eWxlPSJmb250LXNpemU6MTQuMHB4O2Zv
bnQtZmFtaWx5OlRhaG9tYSxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrOyI+Jm5ic3A7PC9zcGFuPjwv
cD48L2Rpdj48ZGl2ICBzdHlsZT0ibWFyZ2luOjE0LjBweCAuMHB4OyI+PGRpdiA+PHAgIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46LjBweDtmb250LXNpemU6MTQuN3B4O2ZvbnQtZmFt
aWx5OkNhbGlicmksc2Fucy1zZXJpZjsiPjxzcGFuICBzdHlsZT0iZm9udC1zaXplOjE0LjBweDtm
b250LWZhbWlseTpUYWhvbWEsc2Fucy1zZXJpZjtjb2xvcjpibGFjazsiPi0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTwvc3Bh
bj48L3A+PC9kaXY+PGRpdiA+PHAgIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46LjBw
eDtmb250LXNpemU6MTQuN3B4O2ZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjsiPjxzcGFu
ICBzdHlsZT0iZm9udC1zaXplOjE0LjBweDtmb250LWZhbWlseTpUYWhvbWEsc2Fucy1zZXJpZjtj
b2xvcjpibGFjazsiPkZyb206TWFydGluIFRob21zb24gJmx0OzxhICBocmVmPSJtYWlsdG86bXRA
bG93ZW50cm9weS5uZXQiIHRhcmdldD0iX2JsYW5rIiBzdHlsZT0iY29sb3I6IzAwMDBmZjt0ZXh0
LWRlY29yYXRpb246dW5kZXJsaW5lICMwMDAwZmY7Ij5tdEBsb3dlbnRyb3B5Lm5ldDwvYT4mZ3Q7
PC9zcGFuPjwvcD48L2Rpdj48ZGl2ID48cCAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdp
bjouMHB4O2ZvbnQtc2l6ZToxNC43cHg7Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyI+
PHNwYW4gIHN0eWxlPSJmb250LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5OlRhaG9tYSxzYW5zLXNl
cmlmO2NvbG9yOmJsYWNrOyI+U2VuZCBUaW1lOjIwMTk8L3NwYW4+PHNwYW4gIHN0eWxlPSJmb250
LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5Ok1TIEdvdGhpYztjb2xvcjpibGFjazsiPuW5tDwvc3Bh
bj48c3BhbiAgc3R5bGU9ImZvbnQtc2l6ZToxNC4wcHg7Zm9udC1mYW1pbHk6VGFob21hLHNhbnMt
c2VyaWY7Y29sb3I6YmxhY2s7Ij4xMDwvc3Bhbj48c3BhbiAgc3R5bGU9ImZvbnQtc2l6ZToxNC4w
cHg7Zm9udC1mYW1pbHk6TVMgR290aGljO2NvbG9yOmJsYWNrOyI+5pyIPC9zcGFuPjxzcGFuICBz
dHlsZT0iZm9udC1zaXplOjE0LjBweDtmb250LWZhbWlseTpUYWhvbWEsc2Fucy1zZXJpZjtjb2xv
cjpibGFjazsiPjMxPC9zcGFuPjxzcGFuICBzdHlsZT0iZm9udC1zaXplOjE0LjBweDtmb250LWZh
bWlseTpNUyBHb3RoaWM7Y29sb3I6YmxhY2s7Ij7ml6U8L3NwYW4+PHNwYW4gIHN0eWxlPSJmb250
LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5OlRhaG9tYSxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrOyI+
KDwvc3Bhbj48c3BhbiAgc3R5bGU9ImZvbnQtc2l6ZToxNC4wcHg7Zm9udC1mYW1pbHk6TVMgR290
aGljO2NvbG9yOmJsYWNrOyI+5pif5pyf5ZubPC9zcGFuPjxzcGFuICBzdHlsZT0iZm9udC1zaXpl
OjE0LjBweDtmb250LWZhbWlseTpUYWhvbWEsc2Fucy1zZXJpZjtjb2xvcjpibGFjazsiPikKIDA2
OjA3PC9zcGFuPjwvcD48L2Rpdj48ZGl2ID48cCAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1h
cmdpbjouMHB4O2ZvbnQtc2l6ZToxNC43cHg7Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlm
OyI+PHNwYW4gIHN0eWxlPSJmb250LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5OlRhaG9tYSxzYW5z
LXNlcmlmO2NvbG9yOmJsYWNrOyI+VG86cXVpYyAmbHQ7PGEgIGhyZWY9Im1haWx0bzpxdWljQGll
dGYub3JnIiB0YXJnZXQ9Il9ibGFuayIgc3R5bGU9ImNvbG9yOiMwMDAwZmY7dGV4dC1kZWNvcmF0
aW9uOnVuZGVybGluZSAjMDAwMGZmOyI+cXVpY0BpZXRmLm9yZzwvYT4mZ3Q7PC9zcGFuPjwvcD48
L2Rpdj48ZGl2ID48cCAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjouMHB4O2ZvbnQt
c2l6ZToxNC43cHg7Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyI+PHNwYW4gIHN0eWxl
PSJmb250LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5OlRhaG9tYSxzYW5zLXNlcmlmO2NvbG9yOmJs
YWNrOyI+U3ViamVjdDpSZTogRmFzdCBBZGRyZXNzIFZhbGlkYXRpb24gLSBhYm91dDwvc3Bhbj48
L3A+PC9kaXY+PGRpdiA+PHAgIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46LjBweDtm
b250LXNpemU6MTQuN3B4O2ZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjsiPjxzcGFuICBz
dHlsZT0iZm9udC1zaXplOjE0LjBweDtmb250LWZhbWlseTpUYWhvbWEsc2Fucy1zZXJpZjtjb2xv
cjpibGFjazsiPiZuYnNwOzwvc3Bhbj48L3A+PC9kaXY+PHAgIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtYXJnaW46LjBweDtmb250LXNpemU6MTQuN3B4O2ZvbnQtZmFtaWx5OkNhbGlicmksc2Fu
cy1zZXJpZjsiPjxzcGFuICBzdHlsZT0iZm9udC1zaXplOjE0LjBweDtmb250LWZhbWlseTpUYWhv
bWEsc2Fucy1zZXJpZjtjb2xvcjpibGFjazsiPkFsc28mbmJzcDtub3RlJm5ic3A7dGhhdCZuYnNw
O2V4Y2hhbmdlJm5ic3A7b2YmbmJzcDtIYW5kc2hha2UmbmJzcDtwYWNrZXRzJm5ic3A7cHJvdmlk
ZXMmbmJzcDtwcm9vZiZuYnNwO29mJm5ic3A7cmV0dXJuJm5ic3A7cm91dGVhYmlsaXR5Jm5ic3A7
dmlhJm5ic3A7dGhlJm5ic3A7dXNlJm5ic3A7b2YmbmJzcDt0aGUmbmJzcDtlbmNyeXB0aW9uJm5i
c3A7a2V5cywmbmJzcDtzbyZuYnNwO3RoZXJlJm5ic3A7aXMmbmJzcDtubyZuYnNwO25lZWQmbmJz
cDt0byZuYnNwO2V4Y2hhbmdlJm5ic3A7dG9rZW5zJm5ic3A7YXQmbmJzcDt0aGF0Jm5ic3A7bGV2
ZWwuPGJyID48YnIgPgpPbiZuYnNwO1RodSwmbmJzcDtPY3QmbmJzcDszMSwmbmJzcDsyMDE5LCZu
YnNwO2F0Jm5ic3A7MDM6MjksJm5ic3A7TWlrZSZuYnNwO0Jpc2hvcCZuYnNwO3dyb3RlOjxiciA+
CiZndDsmbmJzcDsmbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7VGhlJm5ic3A7YWR2YW50YWdlJm5ic3A7
b2YmbmJzcDt1c2luZyZuYnNwO1JldHJ5LCZuYnNwO2hvd2V2ZXIsJm5ic3A7aXMmbmJzcDt0aGF0
Jm5ic3A7dGhlJm5ic3A7c2VydmVyJm5ic3A7aXMmbmJzcDthYmxlJm5ic3A7dG8mbmJzcDs8YnIg
PgomZ3Q7Jm5ic3A7a2VlcCZuYnNwO21pbmltYWwmbmJzcDsoaWYmbmJzcDthbnkpJm5ic3A7c3Rh
dGUmbmJzcDthYm91dCZuYnNwO3RoZSZuYnNwO2NsaWVudC4mbmJzcDtFeGNoYW5naW5nJm5ic3A7
dGhlJm5ic3A7dG9rZW4mbmJzcDthdCZuYnNwOzxiciA+CiZndDsmbmJzcDt0aGUmbmJzcDtIYW5k
c2hha2UmbmJzcDtlbmNyeXB0aW9uJm5ic3A7bGV2ZWwmbmJzcDttZWFucyZuYnNwO3RoZSZuYnNw
O3NlcnZlciZuYnNwO2lzJm5ic3A7YWxyZWFkeSZuYnNwO2RvaW5nJm5ic3A7d29yayZuYnNwOzxi
ciA+CiZndDsmbmJzcDthbmQmbmJzcDttYWludGFpbmluZyZuYnNwO3N0YXRlJm5ic3A7aW4mbmJz
cDtvcmRlciZuYnNwO3RvJm5ic3A7cHJvY2VzcyZuYnNwO3RoZSZuYnNwO2hhbmRzaGFrZSwmbmJz
cDt3aGljaCZuYnNwO2lzJm5ic3A7PGJyID4KJmd0OyZuYnNwO2V4YWN0bHkmbmJzcDt3aGF0Jm5i
c3A7dGhlJm5ic3A7c2VydmVyJm5ic3A7aXMmbmJzcDt0cnlpbmcmbmJzcDt0byZuYnNwO2F2b2lk
LjxiciA+CiZndDsmbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7PGJyID4KJmd0OyZuYnNwOypGcm9tOiom
bmJzcDtRVUlDJm5ic3A7Jmx0OzxhICBocmVmPSJtYWlsdG86cXVpYy1ib3VuY2VzQGlldGYub3Jn
IiB0YXJnZXQ9Il9ibGFuayIgc3R5bGU9ImNvbG9yOiMwMDAwZmY7dGV4dC1kZWNvcmF0aW9uOnVu
ZGVybGluZSAjMDAwMGZmOyI+cXVpYy1ib3VuY2VzQGlldGYub3JnPC9hPiZndDsmbmJzcDsqT24m
bmJzcDtCZWhhbGYmbmJzcDtPZiZuYnNwOyombmJzcDtRaW5nJm5ic3A7QW48YnIgPgomZ3Q7Jm5i
c3A7KlNlbnQ6KiZuYnNwO1dlZG5lc2RheSwmbmJzcDtPY3RvYmVyJm5ic3A7MzAsJm5ic3A7MjAx
OSZuYnNwOzk6NDEmbmJzcDtBTTxiciA+CiZndDsmbmJzcDsqVG86KiZuYnNwO3F1aWMmbmJzcDsm
bHQ7PGEgIGhyZWY9Im1haWx0bzpxdWljQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayIgc3R5bGU9
ImNvbG9yOiMwMDAwZmY7dGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZSAjMDAwMGZmOyI+cXVpY0Bp
ZXRmLm9yZzwvYT4mZ3Q7OyZuYnNwO2pyaS5pZXRmJm5ic3A7Jmx0OzxhICBocmVmPSJtYWlsdG86
anJpLmlldGZAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayIgc3R5bGU9ImNvbG9yOiMwMDAwZmY7
dGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZSAjMDAwMGZmOyI+anJpLmlldGZAZ21haWwuY29tPC9h
PiZndDs7Jm5ic3A7bXQmbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7Jmx0OzxhICBocmVmPSJtYWlsdG86
bXRAbG93ZW50cm9weS5uZXQiIHRhcmdldD0iX2JsYW5rIiBzdHlsZT0iY29sb3I6IzAwMDBmZjt0
ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lICMwMDAwZmY7Ij5tdEBsb3dlbnRyb3B5Lm5ldDwvYT4m
Z3Q7PGJyID4KJmd0OyZuYnNwOypDYzoqJm5ic3A7PC9zcGFuPjxzcGFuICBzdHlsZT0iZm9udC1z
aXplOjE0LjBweDtmb250LWZhbWlseTpNUyBHb3RoaWM7Y29sb3I6YmxhY2s7Ij7liJjlpKc8L3Nw
YW4+PHNwYW4gIHN0eWxlPSJmb250LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5Ok1pY3Jvc29mdCBK
aGVuZ0hlaSxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrOyI+6bmPPC9zcGFuPjxzcGFuICBzdHlsZT0i
Zm9udC1zaXplOjE0LjBweDtmb250LWZhbWlseTpUYWhvbWEsc2Fucy1zZXJpZjtjb2xvcjpibGFj
azsiPig8L3NwYW4+PHNwYW4gIHN0eWxlPSJmb250LXNpemU6MTQuMHB4O2ZvbnQtZmFtaWx5Ok1p
Y3Jvc29mdCBKaGVuZ0hlaSxzYW5zLXNlcmlmO2NvbG9yOmJsYWNrOyI+6bmP5oiQPC9zcGFuPjxz
cGFuICBzdHlsZT0iZm9udC1zaXplOjE0LjBweDtmb250LWZhbWlseTpUYWhvbWEsc2Fucy1zZXJp
Zjtjb2xvcjpibGFjazsiPikmbmJzcDsmbHQ7PGEgIGhyZWY9Im1haWx0bzptYXgubGRwQGFsaWJh
YmEtaW5jLmNvbSIgdGFyZ2V0PSJfYmxhbmsiIHN0eWxlPSJjb2xvcjojMDAwMGZmO3RleHQtZGVj
b3JhdGlvbjp1bmRlcmxpbmUgIzAwMDBmZjsiPm1heC5sZHBAYWxpYmFiYS1pbmMuY29tPC9hPiZn
dDs8YnIgPgomZ3Q7Jm5ic3A7KlN1YmplY3Q6KiZuYnNwO0Zhc3QmbmJzcDtBZGRyZXNzJm5ic3A7
VmFsaWRhdGlvbiZuYnNwOy0mbmJzcDthYm91dDxiciA+CiZndDsmbmJzcDs8YnIgPgomZ3Q7Jm5i
c3A7PGJyID4KJmd0OyZuYnNwOzxiciA+CiZndDsmbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7SGkmbmJz
cDtNYXJ0aW4sJm5ic3A7SmFuYSwmbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7PGJyID4KJmd0OyZuYnNw
O0kmbmJzcDtyZWFkJm5ic3A7dGhyb3VnaCZuYnNwOzxhICBocmVmPSJodHRwczovL3d3dy5pZXRm
Lm9yZy9pZC9kcmFmdC1pZXRmLXF1aWMtdHJhbnNwb3J0LTIzLnR4dCIgdGFyZ2V0PSJfYmxhbmsi
IHN0eWxlPSJjb2xvcjojMDAwMGZmO3RleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmUgIzAwMDBmZjsi
Pmh0dHBzOi8vd3d3LmlldGYub3JnL2lkL2RyYWZ0LWlldGYtcXVpYy10cmFuc3BvcnQtMjMudHh0
PC9hPiZuYnNwOzxiciA+CiZndDsmbmJzcDthbmQmbmJzcDtoYXZlJm5ic3A7YSZuYnNwO2ZldyZu
YnNwO2NvbW1lbnRzJm5ic3A7YW5kJm5ic3A7aWRlYXMmbmJzcDt0byZuYnNwO2Rpc2N1c3MuPGJy
ID4KJmd0OyZuYnNwOzxiciA+CiZndDsmbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7W1FVSUMtVHJhbnNd
Jm5ic3A7ZGVmaW5lcyZuYnNwO2EmbmJzcDt0b2tlbiZuYnNwO2Jhc2VkJm5ic3A7c2NoZW1lJm5i
c3A7dG8mbmJzcDtmYWNpbGl0YXRlJm5ic3A7YWRkcmVzcyZuYnNwOzxiciA+CiZndDsmbmJzcDt2
YWxpZGF0aW9uJm5ic3A7b2YmbmJzcDthJm5ic3A7Y2xpZW50LiZuYnNwO1RoZSZuYnNwO3Rva2Vu
Jm5ic3A7TVVTVCZuYnNwO2JlJm5ic3A7Y292ZXJlZCZuYnNwO2J5Jm5ic3A7aW50ZWdyaXR5Jm5i
c3A7PGJyID4KJmd0OyZuYnNwO3Byb3RlY3Rpb24mbmJzcDthZ2FpbnN0Jm5ic3A7bW9kaWZpY2F0
aW9uJm5ic3A7b3ImbmJzcDtmYWxzaWZpY2F0aW9uJm5ic3A7YnkmbmJzcDtjbGllbnRzLiZuYnNw
O1RoZSZuYnNwO3NlcnZlciZuYnNwOzxiciA+CiZndDsmbmJzcDtyZW1lbWJlcnMmbmJzcDt0aGUm
bmJzcDt2YWx1ZSZuYnNwO2l0Jm5ic3A7c2VuZHMmbmJzcDt0byZuYnNwO2NsaWVudHMmbmJzcDth
bmQmbmJzcDt2YWxpZGF0ZXMmbmJzcDt0aGUmbmJzcDt0b2tlbiZuYnNwO3NlbnQmbmJzcDs8YnIg
PgomZ3Q7Jm5ic3A7YmFjayZuYnNwO2Zyb20mbmJzcDthJm5ic3A7Y2xpZW50LiZuYnNwO0luJm5i
c3A7aXRzJm5ic3A7ZGVzaWduLCZuYnNwO1JldHJ5Jm5ic3A7cGFja2V0Jm5ic3A7aXMmbmJzcDt1
c2VkJm5ic3A7dG8mbmJzcDtkZWxpdmVyJm5ic3A7dGhlJm5ic3A7PGJyID4KJmd0OyZuYnNwO3Rv
a2VuJm5ic3A7dG8mbmJzcDthJm5ic3A7Y2xpZW50Jm5ic3A7d2hpY2gmbmJzcDthZGRyZXNzJm5i
c3A7aGFzJm5ic3A7bm90Jm5ic3A7eWV0Jm5ic3A7YmVlbiZuYnNwO3ZhbGlkYXRlZC4mbmJzcDtJ
dCZuYnNwO3ZvaWRzJm5ic3A7PGJyID4KJmd0OyZuYnNwO3RoZSZuYnNwO2ZpcnN0Jm5ic3A7dHJh
bnNtaXNzaW9uJm5ic3A7b2YmbmJzcDt0aGUmbmJzcDtJbml0aWFsJm5ic3A7cGFja2V0Jm5ic3A7
c2VudCZuYnNwO2J5Jm5ic3A7dGhlJm5ic3A7Y2xpZW50LCZuYnNwO2FuZCZuYnNwOzxiciA+CiZn
dDsmbmJzcDt0cmlnZ2VycyZuYnNwO2EmbmJzcDtzZWNvbmQmbmJzcDtJbml0aWFsJm5ic3A7cGFj
a2V0Jm5ic3A7dG8mbmJzcDtiZSZuYnNwO3NlbnQmbmJzcDt3aXRoJm5ic3A7dGhlJm5ic3A7dG9r
ZW4uJm5ic3A7VGhlJm5ic3A7PGJyID4KJmd0OyZuYnNwO2V4Y2hhbmdlJm5ic3A7b2YmbmJzcDt0
b2tlbiZuYnNwO3dpbGwmbmJzcDtjYXVzZSZuYnNwO2xvbmdlciZuYnNwO2Nvbm5lY3Rpb24mbmJz
cDtlc3RhYmxpc2htZW50Jm5ic3A7ZGVsYXkmbmJzcDtmb3ImbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7
YSZuYnNwO2NsaWVudC48YnIgPgomZ3Q7Jm5ic3A7PGJyID4KJmd0OyZuYnNwOzxiciA+CiZndDsm
bmJzcDtUbyZuYnNwO2ltcHJvdmUmbmJzcDt0aGUmbmJzcDtlZmZpY2llbmN5Jm5ic3A7b2YmbmJz
cDthZGRyZXNzJm5ic3A7dmFsaWRhdGlvbiZuYnNwO2R1cmluZyZuYnNwO2hhbmRzaGFrZSwmbmJz
cDtvbmUmbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7aWRlYSZuYnNwO2lzJm5ic3A7dGhhdCZuYnNwO3Ro
ZSZuYnNwO3NhbWUmbmJzcDt0b2tlbiZuYnNwO2NhbiZuYnNwO2JlJm5ic3A7ZXhjaGFuZ2VkJm5i
c3A7dmlhJm5ic3A7YSZuYnNwO2RpZmZlcmVudCZuYnNwO2NvbnRhaW5lciZuYnNwOzxiciA+CiZn
dDsmbmJzcDtpLmUuJm5ic3A7dGhlJm5ic3A7SGFuZHNoYWtlJm5ic3A7cGFja2V0LCZuYnNwO3Ro
YXQmbmJzcDtlbGltaW5hdGVzJm5ic3A7dGhlJm5ic3A7dXNlJm5ic3A7b2YmbmJzcDtSZXRyeSZu
YnNwO3BhY2tldCZuYnNwO2ZvciZuYnNwOzxiciA+CiZndDsmbmJzcDt0b2tlbiZuYnNwO2RlbGl2
ZXJ5LiZuYnNwOzxiciA+CiZndDsmbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7PGJyID4KJmd0OyZuYnNw
O0kmbmJzcDthbSZuYnNwO3dvcmtpbmcmbmJzcDtvbiZuYnNwO3RoZSZuYnNwO2NvbXBsZXRlJm5i
c3A7ZHJhZnQmbmJzcDthbmQmbmJzcDt3aWxsJm5ic3A7c3VibWl0Jm5ic3A7aXQmbmJzcDtieSZu
YnNwO0ZyaWRheS4mbmJzcDtCZWZvcmUmbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7dGhhdCwmbmJzcDto
b3BlJm5ic3A7dGhpcyZuYnNwO2NhbiZuYnNwO2JlJm5ic3A7ZGlzY3Vzc2VkJm5ic3A7aW4mbmJz
cDtlbWFpbCZuYnNwO2ZpcnN0LjxiciA+CiZndDsmbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7PGJyID4K
Jmd0OyZuYnNwO0JSLDxiciA+CiZndDsmbmJzcDs8YnIgPgomZ3Q7Jm5ic3A7UWluZyZuYnNwO0Fu
PGJyID4KJmd0Ozwvc3Bhbj48L3A+PC9kaXY+PGRpdiA+PHAgIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtYXJnaW46LjBweDtmb250LXNpemU6MTQuN3B4O2ZvbnQtZmFtaWx5OkNhbGlicmksc2Fu
cy1zZXJpZjtsaW5lLWhlaWdodDoyMC4wcHg7Ij48c3BhbiAgc3R5bGU9ImZvbnQtc2l6ZToxNC4w
cHg7Zm9udC1mYW1pbHk6VGFob21hLHNhbnMtc2VyaWY7Y29sb3I6YmxhY2s7Ij4mbmJzcDs8L3Nw
YW4+PC9wPjwvZGl2PjwvZGl2PjwvZGl2PjxkaXYgIHN0eWxlPSJsaW5lLWhlaWdodDoyMC4wcHg7
Y2xlYXI6Ym90aDsiPjxiciA+PC9kaXY+PC9kaXY+PC9kaXY+PC9kaXY+PC9ibG9ja3F1b3RlPjxk
aXYgIHN0eWxlPSJsaW5lLWhlaWdodDoyMC4wcHg7Y2xlYXI6Ym90aDsiPjxiciA+PC9kaXY+PC9k
aXY+PC9kaXY+
------=ALIBOUNDARY_29147_4c0c1940_5dbc3279_353e78--


From nobody Fri Nov  1 06:31:57 2019
Return-Path: <anqing.aq@alibaba-inc.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 CD387120147 for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 06:31:55 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 (1024-bit key) header.d=alibaba-inc.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 93MPb2i6uAuU for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 06:31:54 -0700 (PDT)
Received: from out0-151.mail.aliyun.com (out0-151.mail.aliyun.com [140.205.0.151]) (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 A6A911200CE for <quic@ietf.org>; Fri,  1 Nov 2019 06:31:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1572615109; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=JLUcJ26an3+2l15srGbtI6dcOmV8uefbdg9fW13TICY=; b=r8YXYP0mqQ0S6+aVPYgUvhTw/qOdC4lJ2DRThN9u3mHVH2ge2Qp/fDAZKD/2aItiPgl9XYkJ1lLJO4X27QFVZ6iJOLG/72ItOkxqw1gDgtDYcygmLx+wuacJtib//dpdNIySMc6l1Y1BKmrVe9eeSQZBX78qoXwB0pWZoulR1Zc=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R181e4; CH=green; DM=||false|; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03303; MF=anqing.aq@alibaba-inc.com; NM=1; PH=DW; RN=5; SR=0; TI=W4_5657687_v5ForWebDing_0AB10114_1572614326929_o7001c328q; 
Received: from WS-web (anqing.aq@alibaba-inc.com[W4_5657687_v5ForWebDing_0AB10114_1572614326929_o7001c328q]) by e02c03267.eu6 at Fri, 01 Nov 2019 21:26:24 +0800
Date: Fri, 01 Nov 2019 21:26:24 +0800
From: "Qing An" <anqing.aq@alibaba-inc.com>
To: "=?UTF-8?B?VMO2bWEgR2F2cmljaGVua292?=" <ximaera@gmail.com>
Cc: "IETF QUIC WG" <quic@ietf.org>, "jri.ietf" <jri.ietf@gmail.com>, "mt" <mt@lowentropy.net>, "=?UTF-8?B?5YiY5aSn6bmPKOm5j+aIkCk=?=" <max.ldp@alibaba-inc.com>
Reply-To: "Qing An" <anqing.aq@alibaba-inc.com>
Message-ID: <6ab3b6d6-7638-4b96-b2a3-4212f747a7af.anqing.aq@alibaba-inc.com>
Subject: =?UTF-8?B?UmU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQ=?=
X-Mailer: [Alimail-Mailagent revision 2765257][W4_5657687][v5ForWebDing][Chrome]
MIME-Version: 1.0
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com>,  <CALZ3u+YyOQxA5zBxkhDj9-wObfqjxPxPyXH9PumaW79DNkKjsg@mail.gmail.com>
x-aliyun-mail-creator: W4_5657687_v5ForWebDing_NTMTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTVfMCkgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzc4LjAuMzkwNC43MCBTYWZhcmkvNTM3LjM2XQ
In-Reply-To: <CALZ3u+YyOQxA5zBxkhDj9-wObfqjxPxPyXH9PumaW79DNkKjsg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_80694_54efd940_5dbc3280_353e92"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/AKawDI6CbwsfnV1Lwqgz_5DtXr8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 13:31:56 -0000

------=ALIBOUNDARY_80694_54efd940_5dbc3280_353e92
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

ClJpZ2h0LCBjbGllbnQgYWRkcmVzcyB2YWxpZGF0aW9uIGNhbiBwcm92aWRlIHByb3RlY3Rpb24g
YWdhaW5zdCBmbG9vZHMsIGJ1dCB0b2RheSdzIHNlcnZlciBvZnRlbiBoYXMgb3RoZXIgYXBwcm9h
Y2hlcyB0byBoYW5kbGUgZmxvb2RzLiBJbiB0aGlzIGNhc2UsIElNSE8gaXQgaXMgcmVhc29uYWJs
ZSB0byBtYWtlIGl0IHBvc3NpYmxlIGZvciBzZXJ2ZXIgdG8gY2hvb3NlIHdoZXRoZXIgb3Igbm90
IHRvIHVzZSBSZXRyeSBmb3IgY2xpZW50IGFkZHJlc3MgdmFsaWRhdGlvbgoKCi0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQoK
ClBlYWNlLAoKT24gV2VkLCBPY3QgMzAsIDIwMTksIDQ6NDEgUE0gUWluZyBBbiA8YW5xaW5nLmFx
QGFsaWJhYmEtaW5jLmNvbT4gd3JvdGU6CltRVUlDLVRyYW5zXSBkZWZpbmVzIGEgdG9rZW4gYmFz
ZWQgc2NoZW1lIHRvIGZhY2lsaXRhdGUgYWRkcmVzcyB2YWxpZGF0aW9uIG9mIGEgY2xpZW50LiBU
aGUgdG9rZW4gTVVTVCBiZSBjb3ZlcmVkIGJ5IGludGVncml0eSBwcm90ZWN0aW9uIGFnYWluc3Qg
bW9kaWZpY2F0aW9uIG9yIGZhbHNpZmljYXRpb24gYnkgY2xpZW50cy4gVGhlIHNlcnZlciByZW1l
bWJlcnMgdGhlIHZhbHVlIGl0IHNlbmRzIHRvIGNsaWVudHMgYW5kIHZhbGlkYXRlcyB0aGUgdG9r
ZW4gc2VudCBiYWNrIGZyb20gYSBjbGllbnQuCgpBYm91dCB0aGUgb25seSB1c2UgY2FzZSBmb3Ig
dGhlIGNsaWVudCBhZGRyZXNzIHZhbGlkYXRpb24gSSBjYW4gdGhpbmsgb2YgaXMgdGhlIHByb3Rl
Y3Rpb24gYWdhaW5zdCBIZWxsbyBwYWNrZXQgZmxvb2RzIGV4aGF1c3RpbmcgdGhlIHJlc291cmNl
cyAoaW5jbHVkaW5nIG1lbW9yeSkgb24gdGhlIHNlcnZlci4KCkluIHRoaXMgY2FzZSBrZWVwaW5n
IGFueSBzdGF0ZSBmb3IgY29ubmVjdGlvbnMgY29taW5nIGZyb20gcG90ZW50aWFsbHkgc3Bvb2Zl
ZCBhZGRyZXNzZXMgb24gdGhlIHNlcnZlciBjb21wcm9taXNlcyB0aGUgdmVyeSBjb25jZXB0IG9m
IGZsb29kIHByb3RlY3Rpb24uICBBbGwgdGhlIHN0YXRlIG11c3QgYmUga2VwdCBpbiB0aGUgUmV0
cnkgcGFja2V0IGFuZCBwcm9tcHRseSBzaWduYWxlZCBiYWNrIGJ5IHRoZSBjbGllbnQuCgpUaGUg
c3BlZWQtdXAgYnJvdWdodCBpbiBieSBrZWVwaW5nIHRoZSBzdGF0ZSBpcyBwcm9iYWJseSBuZWds
aWdpYmxlIChUT0RPOiBhY3R1YWwgbWVhc3VyZW1lbnRzKSB3aGlsZSB3aXRoIGEgdG9kYXkncyBh
dmVyYWdlIDMwME1wcHMgcGFja2V0IGZsb29kIGhhcmRseSBhbnkgc3RhdGUgY291bGQgYmUga2Vw
dCBmb3IgYW55IHJlYXNvbmFibGUgcGVyaW9kIG9mIHRpbWUuCgotLQpUw7ZtYQoK
------=ALIBOUNDARY_80694_54efd940_5dbc3280_353e92
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64

PGRpdiBjbGFzcz0iX19hbGl5dW5fZW1haWxfYm9keV9ibG9jayI+PGRpdiAgc3R5bGU9ImxpbmUt
aGVpZ2h0OjEuNztmb250LWZhbWlseTpUYWhvbWEsQXJpYWwsU1RIZWl0aSxTaW1TdW47Zm9udC1z
aXplOjE0LjBweDtjb2xvcjojMDAwMDAwOyI+PGRpdiAgc3R5bGU9ImNsZWFyOmJvdGg7Ij48L2Rp
dj48ZGl2ICBzdHlsZT0iY2xlYXI6Ym90aDsiPjxiciA+PC9kaXY+PGRpdiAgc3R5bGU9ImNsZWFy
OmJvdGg7Ij5SaWdodCwgY2xpZW50IGFkZHJlc3MgdmFsaWRhdGlvbiBjYW4gcHJvdmlkZSBwcm90
ZWN0aW9uIGFnYWluc3QgZmxvb2RzLCBidXQgdG9kYXkncyBzZXJ2ZXIgb2Z0ZW4gaGFzIG90aGVy
IGFwcHJvYWNoZXMgdG8gaGFuZGxlIGZsb29kcy4gSW4gdGhpcyBjYXNlLCBJTUhPIGl0IGlzIHJl
YXNvbmFibGUgdG8gbWFrZSBpdCBwb3NzaWJsZSBmb3Igc2VydmVyIHRvIGNob29zZSB3aGV0aGVy
IG9yIG5vdCB0byB1c2UgUmV0cnkgZm9yIGNsaWVudCBhZGRyZXNzIHZhbGlkYXRpb248L2Rpdj48
ZGl2ICBzdHlsZT0iY2xlYXI6Ym90aDsiPjxiciA+PC9kaXY+PGRpdiAgc3R5bGU9ImNsZWFyOmJv
dGg7Ij48YnIgPjwvZGl2PjxkaXYgIHN0eWxlPSJtYXJnaW46LjBweCAuMHB4IC4wcHggMzAuMHB4
O2ZvbnQtZmFtaWx5OlRhaG9tYSxBcmlhbCxTVEhlaXRpLFNpbVN1bjtmb250LXNpemU6MTQuMHB4
O2NvbG9yOiMwMDAwMDA7Ij48ZGl2ICBzdHlsZT0iY2xlYXI6Ym90aDsiPi0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTwvZGl2
PjxkaXYgIHN0eWxlPSJjbGVhcjpib3RoOyI+PGJyID48L2Rpdj48ZGl2ICBzdHlsZT0iY2xlYXI6
Ym90aDsiPjxiciA+PC9kaXY+PGRpdiA+UGVhY2UsPGJyID48YnIgPjxkaXYgIGNsYXNzPSJnbWFp
bF9xdW90ZSI+PGRpdiAgY2xhc3M9ImdtYWlsX2F0dHIiPk9uIFdlZCwgT2N0IDMwLCAyMDE5LCA0
OjQxIFBNIFFpbmcgQW4gJmx0OzxhICBocmVmPSJtYWlsdG86YW5xaW5nLmFxQGFsaWJhYmEtaW5j
LmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmFucWluZy5hcUBhbGliYWJhLWluYy5jb208L2E+Jmd0OyB3
cm90ZTo8YnIgPjwvZGl2PjxkaXYgIHN0eWxlPSJtYXJnaW46MTQuMHB4IC4wcHg7Ij48ZGl2ICBz
dHlsZT0ibGluZS1oZWlnaHQ6MS43O2ZvbnQtZmFtaWx5OlRhaG9tYSxBcmlhbCxTVEhlaXRpLFNp
bVN1bjtmb250LXNpemU6MTQuMHB4O2NvbG9yOiMwMDAwMDA7Y2xlYXI6Ym90aDsiPltRVUlDLVRy
YW5zXSBkZWZpbmVzJm5ic3A7YSZuYnNwO3Rva2VuJm5ic3A7YmFzZWQmbmJzcDtzY2hlbWUgdG8m
bmJzcDtmYWNpbGl0YXRlJm5ic3A7YWRkcmVzcyZuYnNwO3ZhbGlkYXRpb24mbmJzcDtvZiZuYnNw
O2EmbmJzcDtjbGllbnQuJm5ic3A7VGhlJm5ic3A7dG9rZW4mbmJzcDtNVVNUJm5ic3A7YmUmbmJz
cDtjb3ZlcmVkJm5ic3A7YnkgaW50ZWdyaXR5IHByb3RlY3Rpb24mbmJzcDthZ2FpbnN0Jm5ic3A7
bW9kaWZpY2F0aW9uJm5ic3A7b3ImbmJzcDtmYWxzaWZpY2F0aW9uJm5ic3A7YnkmbmJzcDtjbGll
bnRzLiZuYnNwO1RoZSBzZXJ2ZXImbmJzcDtyZW1lbWJlcnMgdGhlJm5ic3A7dmFsdWUgaXQgc2Vu
ZHMgdG8mbmJzcDtjbGllbnRzJm5ic3A7YW5kJm5ic3A7dmFsaWRhdGVzJm5ic3A7dGhlJm5ic3A7
dG9rZW4mbmJzcDtzZW50IGJhY2smbmJzcDtmcm9tJm5ic3A7YSZuYnNwO2NsaWVudC48L2Rpdj48
L2Rpdj48L2Rpdj48ZGl2ID48YnIgPjwvZGl2PjxkaXYgIGNsYXNzPSJnbWFpbF9xdW90ZSI+PC9k
aXY+PGRpdiA+PGRpdiAgc3R5bGU9ImZvbnQtZmFtaWx5OnNhbnMtc2VyaWY7Ij5BYm91dCB0aGUg
b25seSB1c2UgY2FzZSBmb3IgdGhlIGNsaWVudCBhZGRyZXNzIHZhbGlkYXRpb24gSSBjYW4gdGhp
bmsgb2YgaXMgdGhlIHByb3RlY3Rpb24gYWdhaW5zdCBIZWxsbyBwYWNrZXQgZmxvb2RzIGV4aGF1
c3RpbmcgdGhlIHJlc291cmNlcyAoaW5jbHVkaW5nIG1lbW9yeSkgb24gdGhlIHNlcnZlci48L2Rp
dj48ZGl2ICBzdHlsZT0iZm9udC1mYW1pbHk6c2Fucy1zZXJpZjsiPjxiciA+PC9kaXY+PGRpdiAg
c3R5bGU9ImZvbnQtZmFtaWx5OnNhbnMtc2VyaWY7Ij5JbiB0aGlzIGNhc2Uga2VlcGluZyBhbnkg
c3RhdGUgZm9yIGNvbm5lY3Rpb25zIGNvbWluZyBmcm9tIHBvdGVudGlhbGx5IHNwb29mZWQgYWRk
cmVzc2VzIG9uIHRoZSBzZXJ2ZXIgY29tcHJvbWlzZXMgdGhlIHZlcnkgY29uY2VwdCBvZiBmbG9v
ZCBwcm90ZWN0aW9uLiZuYnNwOyBBbGwgdGhlIHN0YXRlIG11c3QgYmUga2VwdCBpbiB0aGUgUmV0
cnkgcGFja2V0IGFuZCBwcm9tcHRseSBzaWduYWxlZCBiYWNrIGJ5IHRoZSBjbGllbnQuPC9kaXY+
PGRpdiAgc3R5bGU9ImZvbnQtZmFtaWx5OnNhbnMtc2VyaWY7Ij48YnIgPjwvZGl2PjxkaXYgIHN0
eWxlPSJmb250LWZhbWlseTpzYW5zLXNlcmlmOyI+VGhlIHNwZWVkLXVwIGJyb3VnaHQgaW4gYnkg
a2VlcGluZyB0aGUgc3RhdGUgaXMgcHJvYmFibHkgbmVnbGlnaWJsZSAoVE9ETzogYWN0dWFsIG1l
YXN1cmVtZW50cykgd2hpbGUgd2l0aCBhIHRvZGF5J3MgYXZlcmFnZSAzMDBNcHBzIHBhY2tldCBm
bG9vZCBoYXJkbHkgYW55IHN0YXRlIGNvdWxkIGJlIGtlcHQgZm9yIGFueSByZWFzb25hYmxlIHBl
cmlvZCBvZiB0aW1lLjwvZGl2PjxkaXYgIHN0eWxlPSJmb250LWZhbWlseTpzYW5zLXNlcmlmOyI+
PGJyID48L2Rpdj48ZGl2ICBzdHlsZT0iZm9udC1mYW1pbHk6c2Fucy1zZXJpZjsiPi0tPC9kaXY+
PGRpdiAgc3R5bGU9ImZvbnQtZmFtaWx5OnNhbnMtc2VyaWY7Ij5Uw7ZtYTwvZGl2PjwvZGl2Pjxk
aXYgIGNsYXNzPSJnbWFpbF9xdW90ZSI+PC9kaXY+PC9kaXY+PC9kaXY+PGRpdiAgc3R5bGU9Imxp
bmUtaGVpZ2h0OjIwLjBweDtjbGVhcjpib3RoOyI+PGJyID48L2Rpdj48L2Rpdj48L2Rpdj4=
------=ALIBOUNDARY_80694_54efd940_5dbc3280_353e92--


From nobody Fri Nov  1 06:37:44 2019
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 129F31200CE; Fri,  1 Nov 2019 06:37:44 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level: 
X-Spam-Status: No, score=-1.996 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_HELO_NONE=0.001, 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 iWRDw7eqo4rY; Fri,  1 Nov 2019 06:37:41 -0700 (PDT)
Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (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 E751D12013A; Fri,  1 Nov 2019 06:37:40 -0700 (PDT)
Received: by mail-ed1-x52d.google.com with SMTP id c4so7595716edl.0; Fri, 01 Nov 2019 06:37:40 -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=4EaX3E55xRknAeOQ3rPvfS3DYTCimLwxFUiqhoKYzPc=; b=U3YMpYQKbxIPHtLUr9+x9YHdKaiJ5vLQLonUQuI8x2HKs8MDzn0yP3jL+uCj5k3Y20 kBo1GXB5tgphX6SmyGBbYR2rZJmk01TO3joTN4z2fj+unhuDfFMRBXqXfvxa0WnqY4MV 9c1sW4AsP0VfJvRxsKVYDiUtBsLvYW++t9AkKKR0MwZ+RnN804H2N23WUH6oPaHaZ+O9 3AkAf/ju1mjsmmhH6edig6bZ2eCnAWHDYyT+Y2K+YSDTq3kUAyah8/CNhf9SF8KzT9sg nRiiSUiTm9L2ExVFU6vECZfVDOOWb06ASsptoWSafrFwJAmgqJ+aP5yIwX3WQtN8cuF9 V+dQ==
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=4EaX3E55xRknAeOQ3rPvfS3DYTCimLwxFUiqhoKYzPc=; b=fg8smRYKwCZNa8lDqxhcybLoQh9OXsYyuE6oSQPij7X4bAqesHNnvqg4s4igMZJug8 +VtFVmfZpJF5HDQsap2tRmAEijnWgy7o/IrnKEYXi6aD9UbQx/nrXffp6amQGsQCVch9 4IuMfcAwVqPpnWxQpJ3EdA1JjBJ9H11jEFt26qzboZZ7ANIEw60qqeIAEmtcqHn7V9/9 BEOT3fTYLxPPyGFACaiTtJ/zMRKV2ncSTxQO3T4QVIDJHc3yfrH8HijyTuYGUy+3W8gR 7sWBIcUuMHDqRN+LHSNiKIA9dAHB1P/jKa2QLzCuqAWzl3XLlLPpWTlRSjOUYYjk8Hr9 lwHg==
X-Gm-Message-State: APjAAAVPgjbvAUl88d9cFvfi3aSl0AON7T1Iqyoaxh4SJTiD7EP6hTIp 5ve8QgrqH7lHPX/ITpI3y1G33DbdW2ot2GKBvpA=
X-Google-Smtp-Source: APXvYqyAHx56PYWK05D7+7wFmBSU/sVqVfAIRWs1bUoAG3n0ik6cKL8U1QCk5AAy3crwxQH07tb5AEgmjF9gAP7CTLk=
X-Received: by 2002:a05:6402:512:: with SMTP id m18mr10945438edv.250.1572615459476;  Fri, 01 Nov 2019 06:37:39 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Fri, 1 Nov 2019 06:37:38 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <7ac8ad51-c1a2-461b-bc47-021b3875eab8.anqing.aq@alibaba-inc.com>
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com> <BN6PR2201MB1700F72F3DC8F6C3CF79902CDA600@BN6PR2201MB1700.namprd22.prod.outlook.com> <bd15f357-8e7a-42af-bf28-79f7177da385@www.fastmail.com> <f55efb80-1a95-4190-84e5-b81948a7f081.anqing.aq@alibaba-inc.com> <BN6PR2201MB17005571E88F1C68769091A3DA630@BN6PR2201MB1700.namprd22.prod.outlook.com> <69d1a917-b1f9-4142-afb0-f5c67abe7334.anqing.aq@alibaba-inc.com> <CAOYVs2r0zJzbfw5L2Mck8VEJhtyfQtHwF-db5VG45HDTF0WoOQ@mail.gmail.com> <7ac8ad51-c1a2-461b-bc47-021b3875eab8.anqing.aq@alibaba-inc.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Fri, 1 Nov 2019 06:37:38 -0700
Message-ID: <CAN1APddvVeqXeWCZbe9WrLrOyVOWM5-1Dg8x5B4UpNwP6YOGrA@mail.gmail.com>
Subject: Re: Fast Address Validation - about
To: Qing An <anqing.aq@alibaba-inc.com>, Marten Seemann <martenseemann@gmail.com>
Cc: "jri.ietf" <jri.ietf@gmail.com>, QUIC <quic-bounces@ietf.org>, quic <quic@ietf.org>, mt <mt@lowentropy.net>, =?UTF-8?B?5YiY5aSn6bmPKOm5j+aIkCk=?= <max.ldp@alibaba-inc.com>
Content-Type: multipart/alternative; boundary="000000000000d4995a05964911d4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/DqZLmKZS_vZor54ykrzIjRFonmA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 13:37:44 -0000

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

You only save a roundtrip because you do not send a Retry.

If you choose not to send a Retry, the client eventually gets validated
anyway because otherwise the handshake could not complete. Therefore a
Retry token is not needed if you go down that path. In this case the RTT
overhead with fast address validation is the same as ordinary QUIC 1-RTT
handshake.

On the other hand, in the case where Retry is needed, the fast address
validation approach does not solve the problem which is one of 1) defer
handshake processing and server state until after the address is verified,
or 2) redirect the client to another server through a change in
ConnectionID.



On 1 November 2019 at 14.26.24, Qing An (anqing.aq@alibaba-inc.com) wrote:


I believe this can save 1-RTT.

As for the privacy risk, new_token frame can be delivered via handshake


------------------------------------------------------------------
From:Marten Seemann <martenseemann@gmail.com>
Send Time:2019=E5=B9=B411=E6=9C=881=E6=97=A5(=E6=98=9F=E6=9C=9F=E4=BA=94) 2=
0:54
To:=E5=AE=89=E5=8B=8D(=E8=8E=B3=E9=80=B8) <anqing.aq@alibaba-inc.com>
Cc:QUIC <quic-bounces@ietf.org>; quic <quic@ietf.org>; jri.ietf <
jri.ietf@gmail.com>; mt <mt@lowentropy.net>; mikkelfj <mikkelfj@gmail.com>;
=E5=88=98=E5=A4=A7=E9=B9=8F(=E9=B9=8F=E6=88=90) <max.ldp@alibaba-inc.com>
Subject:Re: Fast Address Validation - about

I don't see any enhanced client experience, since the handshake takes
exactly the same number of round trips with your proposal as with the
current version of the QUIC draft.
Sending NEW_TOKEN in Initial packets provides no benefit over sending it in
1-RTT packets, but comes with worse privacy properties, since Initial
packets are not encrypted and can therefore be read by on-path observers.

On Fri, Nov 1, 2019 at 7:37 PM Qing An <anqing.aq@alibaba-inc.com> wrote:

If so, for the first connection between client and server, server can
choose to eliminate the use of Retry packet for token delivery, and
rely on handshake encryption layer to prove return routability.
In addition, New_Token frame is used by
server, via i.e. the Initial packet, to provide the client with an
address validation token that can be used to validate future connections.

It can enhance the experience in client side for the first connection
establishment.

I submitted the draft,
https://datatracker.ietf.org/doc/draft-an-fast-address-validation/

Qing



------------------------------------------------------------------
From:Mike Bishop <mbishop@evequefou.be>
Send Time:2019=E5=B9=B411=E6=9C=881=E6=97=A5(=E6=98=9F=E6=9C=9F=E4=BA=94) 0=
0:06
To:=E5=AE=89=E5=8B=8D(=E8=8E=B3=E9=80=B8) <anqing.aq@alibaba-inc.com>; quic=
 <quic@ietf.org>; jri.ietf <
jri.ietf@gmail.com>; mt <mt@lowentropy.net>; mikkelfj <mikkelfj@gmail.com>
Subject:RE: Fast Address Validation - about

As Martin pointed out in the e-mail you replied to, if the server is
willing to maintain state, any packet at the Handshake encryption layer
proves return routability.  There seems to be no need for a separate
address validation mechanism if the server is willing to proceed with the
handshake.



*From:* QUIC <quic-bounces@ietf.org> *On Behalf Of* Qing An
*Sent:* Thursday, October 31, 2019 8:56 AM
*To:* quic <quic@ietf.org>; jri.ietf <jri.ietf@gmail.com>; mt <
mt@lowentropy.net>; mikkelfj <mikkelfj@gmail.com>
*Subject:* Re: Fast Address Validation - about







To clarify, the proposal is not to replace the existing Retry-based
validation, but to provide another option for server to do the client
validation.



I understand that in server side, exchanging the token at the
Handshake encryption level
will make the server start to maintain handshake states. But in client
side, it can accelerate the connection establishment from client to server.



And it is the server's decision whether to exchange token in Retry or in
Handshake. If server chooses to accept the cost brought by token exchanging
in Handshake, it will bring more enhanced experience in client side.





BR,

Qing





------------------------------------------------------------------

From:Martin Thomson <mt@lowentropy.net>

Send Time:2019=E5=B9=B410=E6=9C=8831=E6=97=A5(=E6=98=9F=E6=9C=9F=E5=9B=9B) =
06:07

To:quic <quic@ietf.org>

Subject:Re: Fast Address Validation - about



Also note that exchange of Handshake packets provides proof of return
routeability via the use of the encryption keys, so there is no need
to exchange tokens at that level.

On Thu, Oct 31, 2019, at 03:29, Mike Bishop wrote:
>
> The advantage of using Retry, however, is that the server is able to
> keep minimal (if any) state about the client. Exchanging the token at
> the Handshake encryption level means the server is already doing work
> and maintaining state in order to process the handshake, which is
> exactly what the server is trying to avoid.
>
>
> *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of * Qing An
> *Sent:* Wednesday, October 30, 2019 9:41 AM
> *To:* quic <quic@ietf.org>; jri.ietf <jri.ietf@gmail.com>; mt
> <mt@lowentropy.net>
> *Cc:* =E5=88=98=E5=A4=A7=E9=B9=8F(=E9=B9=8F=E6=88=90) <max.ldp@alibaba-in=
c.com>
> *Subject:* Fast Address Validation - about
>
>
>
>
> Hi Martin, Jana,
>
> I read through https://www.ietf.org/id/draft-ietf-quic-transport-23.txt
> and have a few comments and ideas to discuss.
>
>
> [QUIC-Trans] defines a token based scheme to facilitate address
> validation of a client. The token MUST be covered by integrity
> protection against modification or falsification by clients. The server
> remembers the value it sends to clients and validates the token sent
> back from a client. In its design, Retry packet is used to deliver the
> token to a client which address has not yet been validated. It voids
> the first transmission of the Initial packet sent by the client, and
> triggers a second Initial packet to be sent with the token. The
> exchange of token will cause longer connection establishment delay for
> a client.
>
>
> To improve the efficiency of address validation during handshake, one
> idea is that the same token can be exchanged via a different container
> i.e. the Handshake packet, that eliminates the use of Retry packet for
> token delivery.
>
>
> I am working on the complete draft and will submit it by Friday. Before
> that, hope this can be discussed in email first.
>
>
> BR,
>
> Qing An
>

--000000000000d4995a05964911d4
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">You only save a roun=
dtrip because you do not send a Retry.</div><div id=3D"bloop_customfont" st=
yle=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);mar=
gin:0px;line-height:auto"><br></div><div id=3D"bloop_customfont" style=3D"f=
ont-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;=
line-height:auto">If you choose not to send a Retry, the client eventually =
gets validated anyway because otherwise the handshake could not complete. T=
herefore a Retry token is not needed if you go down that path. In this case=
 the RTT overhead with fast address validation is the same as ordinary QUIC=
 1-RTT handshake.</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">On =
the other hand, in the case where Retry is needed, the fast address validat=
ion approach does not solve the problem which is one of 1) defer handshake =
processing and server state until after the address is verified, or 2) redi=
rect the client to another server through a change in ConnectionID.</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> <div id=
=3D"bloop_sign_1572615124613484032" class=3D"bloop_sign"><div style=3D"font=
-family:helvetica,arial;font-size:13px"><br></div></div> <br><p class=3D"ai=
rmail_on">On 1 November 2019 at 14.26.24, Qing An (<a href=3D"mailto:anqing=
.aq@alibaba-inc.com">anqing.aq@alibaba-inc.com</a>) wrote:</p> <blockquote =
type=3D"cite" class=3D"clean_bq"><span><div><div></div><div>


<title></title>


<div class=3D"__aliyun_email_body_block">
<div style=3D"line-height:1.7;font-family:Tahoma,Arial,STHeiti,SimSun;font-=
size:14.0px;color:#000000">
<div style=3D"clear:both"><br></div>
<div style=3D"clear:both">I believe this can save 1-RTT.</div>
<div style=3D"clear:both"><br></div>
<div style=3D"clear:both">As for the privacy risk, new_token frame
can be delivered via handshake</div>
<div style=3D"clear:both"><br></div>
<div style=3D"clear:both"><br></div>
<blockquote style=3D"margin-right:.0px;margin-top:.0px;margin-bottom:.0px;f=
ont-family:Tahoma,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000">
<div style=3D"clear:both">
------------------------------------------------------------------</div>
<div style=3D"clear:both">From:Marten Seemann
&lt;<a href=3D"mailto:martenseemann@gmail.com">martenseemann@gmail.com</a>&=
gt;</div>
<div style=3D"clear:both">Send Time:2019=E5=B9=B411=E6=9C=881=E6=97=A5(=E6=
=98=9F=E6=9C=9F=E4=BA=94) 20:54</div>
<div style=3D"clear:both">To:=E5=AE=89=E5=8B=8D(=E8=8E=B3=E9=80=B8)
&lt;<a href=3D"mailto:anqing.aq@alibaba-inc.com">anqing.aq@alibaba-inc.com<=
/a>&gt;</div>
<div style=3D"clear:both">Cc:QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.o=
rg">quic-bounces@ietf.org</a>&gt;;
quic &lt;<a href=3D"mailto:quic@ietf.org">quic@ietf.org</a>&gt;; jri.ietf &=
lt;<a href=3D"mailto:jri.ietf@gmail.com">jri.ietf@gmail.com</a>&gt;; mt
&lt;<a href=3D"mailto:mt@lowentropy.net">mt@lowentropy.net</a>&gt;; mikkelf=
j &lt;<a href=3D"mailto:mikkelfj@gmail.com">mikkelfj@gmail.com</a>&gt;;
=E5=88=98=E5=A4=A7=E9=B9=8F(=E9=B9=8F=E6=88=90) &lt;<a href=3D"mailto:max.l=
dp@alibaba-inc.com">max.ldp@alibaba-inc.com</a>&gt;</div>
<div style=3D"clear:both">Subject:Re: Fast Address Validation -
about</div>
<div style=3D"clear:both"><br></div>
<div>
<div>I don&#39;t see any enhanced client experience, since the
handshake takes exactly the same number of round trips with your
proposal as with the current version of the QUIC draft.<br></div>
<div>Sending NEW_TOKEN in Initial packets provides no benefit over
sending it in 1-RTT packets, but comes with worse privacy
properties, since Initial packets are not encrypted and can
therefore be read by on-path observers.<br></div>
</div>
<br>
<div class=3D"gmail_quote">
<div class=3D"gmail_attr">On Fri, Nov 1, 2019 at 7:37 PM Qing An
&lt;<a href=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_blank">anqing.a=
q@alibaba-inc.com</a>&gt; wrote:<br></div>
<div style=3D"margin:14.0px .0px">
<div style=3D"line-height:1.7;font-family:Tahoma,Arial,STHeiti,SimSun;font-=
size:14.0px;color:#000000">
<div style=3D"clear:both"><br></div>
<div style=3D"clear:both">If so,
f<span>or=C2=A0the=C2=A0first</span>=C2=A0connection=C2=A0between=C2=A0clie=
nt=C2=A0and=C2=A0server,
server can choose to eliminate=C2=A0the=C2=A0use=C2=A0of=C2=A0Retry
packet=C2=A0for=C2=A0token=C2=A0delivery, and
rely=C2=A0on=C2=A0handshake=C2=A0encryption=C2=A0layer=C2=A0to
prove=C2=A0return routability.=C2=A0 In=C2=A0addition, New_Token
frame is=C2=A0used=C2=A0by
server,=C2=A0via=C2=A0i.e.=C2=A0the=C2=A0Initial=C2=A0packet,=C2=A0to=C2=A0=
provide=C2=A0the=C2=A0client=C2=A0with=C2=A0an
address=C2=A0validation=C2=A0token=C2=A0that=C2=A0can=C2=A0be=C2=A0used=C2=
=A0to=C2=A0validate=C2=A0future<span>=C2=A0connections.</span></div>
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>It can enhance the experience in
client side for the first connection establishment.</span></div>
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>I submitted the draft,=C2=A0<a href=3D"http=
s://datatracker.ietf.org/doc/draft-an-fast-address-validation/" target=3D"_=
blank">https://datatracker.ietf.org/doc/draft-an-fast-address-validation/</=
a></span></div>
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>Qing</span></div>
<div style=3D"clear:both"></div>
<div style=3D"clear:both"><br></div>
<div style=3D"clear:both"><br></div>
<div style=3D"clear:both"><br></div>
<div style=3D"clear:both">
------------------------------------------------------------------</div>
<div style=3D"clear:both">From:Mike Bishop &lt;<a href=3D"mailto:mbishop@ev=
equefou.be" target=3D"_blank">mbishop@evequefou.be</a>&gt;</div>
<div style=3D"clear:both">Send Time:2019=E5=B9=B411=E6=9C=881=E6=97=A5(=E6=
=98=9F=E6=9C=9F=E4=BA=94) 00:06</div>
<div style=3D"clear:both">To:=E5=AE=89=E5=8B=8D(=E8=8E=B3=E9=80=B8) &lt;<a =
href=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_blank">anqing.aq@aliba=
ba-inc.com</a>&gt;; quic &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_bl=
ank">quic@ietf.org</a>&gt;;
jri.ietf &lt;<a href=3D"mailto:jri.ietf@gmail.com" target=3D"_blank">jri.ie=
tf@gmail.com</a>&gt;; mt &lt;<a href=3D"mailto:mt@lowentropy.net" target=3D=
"_blank">mt@lowentropy.net</a>&gt;; mikkelfj &lt;<a href=3D"mailto:mikkelfj=
@gmail.com" target=3D"_blank">mikkelfj@gmail.com</a>&gt;</div>
<div style=3D"clear:both">Subject:RE: Fast Address Validation -
about</div>
<div style=3D"clear:both"><br></div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">As
Martin pointed out in the e-mail you replied to, if the server is
willing to maintain state, any packet at the Handshake encryption
layer proves return routability.=C2=A0 There seems to be no need
for a separate address validation mechanism if the server is
willing to proceed with the handshake.</p>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
=C2=A0</p>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<b>From:</b> QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_b=
lank">quic-bounces@ietf.org</a>&gt; <b>On Behalf Of</b>
Qing An<br>
<b>Sent:</b> Thursday, October 31, 2019 8:56 AM<br>
<b>To:</b> quic &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic=
@ietf.org</a>&gt;; jri.ietf &lt;<a href=3D"mailto:jri.ietf@gmail.com" targe=
t=3D"_blank">jri.ietf@gmail.com</a>&gt;; mt &lt;<a href=3D"mailto:mt@lowent=
ropy.net" target=3D"_blank">mt@lowentropy.net</a>&gt;; mikkelfj &lt;<a href=
=3D"mailto:mikkelfj@gmail.com" target=3D"_blank">mikkelfj@gmail.com</a>&gt;=
<br>
<b>Subject:</b> Re: Fast Address Validation - about</p>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
=C2=A0</p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black">=
To
clarify, the proposal is not to replace the existing Retry-based
validation, but to provide another option for server to do the
client validation.</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black">=
I
understand that in server side, e<span style=3D"background:none .0% .0% rep=
eat scroll white">xchanging=C2=A0the=C2=A0token=C2=A0at=C2=A0the=C2=A0Hands=
hake=C2=A0encryption=C2=A0level
will make the server start to maintain handshake states. But in
client side, it can accelerate the connection establishment from
client to server.</span></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black;b=
ackground:none .0% .0% repeat scroll white">
And it is the server&#39;s decision whether to exchange token in Retry
or in Handshake. If server chooses to accept the cost brought by
token exchanging in Handshake, it will bring more enhanced
experience in client side.</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black;b=
ackground:none .0% .0% repeat scroll white">
BR,</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black;b=
ackground:none .0% .0% repeat scroll white">
Qing</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div style=3D"margin:14.0px .0px">
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black">=
------------------------------------------------------------------</span></=
p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black">=
From:Martin
Thomson &lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"_blank" style=3D=
"color:#0000ff;text-decoration:underline #0000ff">mt@lowentropy.net</a>&gt;=
</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black">=
Send
Time:2019</span><span style=3D"font-size:14.0px;font-family:MS Gothic;color=
:black">=E5=B9=B4</span><span style=3D"font-size:14.0px;font-family:Tahoma,=
sans-serif;color:black">10</span><span style=3D"font-size:14.0px;font-famil=
y:MS Gothic;color:black">=E6=9C=88</span><span style=3D"font-size:14.0px;fo=
nt-family:Tahoma,sans-serif;color:black">31</span><span style=3D"font-size:=
14.0px;font-family:MS Gothic;color:black">=E6=97=A5</span><span style=3D"fo=
nt-size:14.0px;font-family:Tahoma,sans-serif;color:black">(</span><span sty=
le=3D"font-size:14.0px;font-family:MS Gothic;color:black">=E6=98=9F=E6=9C=
=9F=E5=9B=9B</span><span style=3D"font-size:14.0px;font-family:Tahoma,sans-=
serif;color:black">)
06:07</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black">=
To:quic
&lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank" style=3D"color:#0000=
ff;text-decoration:underline #0000ff">quic@ietf.org</a>&gt;</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black">=
Subject:Re:
Fast Address Validation - about</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black">=
Also=C2=A0note=C2=A0that=C2=A0exchange=C2=A0of=C2=A0Handshake=C2=A0packets=
=C2=A0provides=C2=A0proof=C2=A0of=C2=A0return=C2=A0routeability=C2=A0via=C2=
=A0the=C2=A0use=C2=A0of=C2=A0the=C2=A0encryption=C2=A0keys,=C2=A0so=C2=A0th=
ere=C2=A0is=C2=A0no=C2=A0need=C2=A0to=C2=A0exchange=C2=A0tokens=C2=A0at=C2=
=A0that=C2=A0level.<br>

<br>
On=C2=A0Thu,=C2=A0Oct=C2=A031,=C2=A02019,=C2=A0at=C2=A003:29,=C2=A0Mike=C2=
=A0Bishop=C2=A0wrote:<br>

&gt;=C2=A0=C2=A0<br>
&gt;=C2=A0The=C2=A0advantage=C2=A0of=C2=A0using=C2=A0Retry,=C2=A0however,=
=C2=A0is=C2=A0that=C2=A0the=C2=A0server=C2=A0is=C2=A0able=C2=A0to=C2=A0<br>

&gt;=C2=A0keep=C2=A0minimal=C2=A0(if=C2=A0any)=C2=A0state=C2=A0about=C2=A0t=
he=C2=A0client.=C2=A0Exchanging=C2=A0the=C2=A0token=C2=A0at=C2=A0<br>

&gt;=C2=A0the=C2=A0Handshake=C2=A0encryption=C2=A0level=C2=A0means=C2=A0the=
=C2=A0server=C2=A0is=C2=A0already=C2=A0doing=C2=A0work=C2=A0<br>

&gt;=C2=A0and=C2=A0maintaining=C2=A0state=C2=A0in=C2=A0order=C2=A0to=C2=A0p=
rocess=C2=A0the=C2=A0handshake,=C2=A0which=C2=A0is=C2=A0<br>

&gt;=C2=A0exactly=C2=A0what=C2=A0the=C2=A0server=C2=A0is=C2=A0trying=C2=A0t=
o=C2=A0avoid.<br>

&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0*From:*=C2=A0QUIC=C2=A0&lt;<a href=3D"mailto:quic-bounces@ietf.or=
g" target=3D"_blank" style=3D"color:#0000ff;text-decoration:underline #0000=
ff">quic-bounces@ietf.org</a>&gt;=C2=A0*On=C2=A0Behalf=C2=A0Of=C2=A0*=C2=A0=
Qing=C2=A0An<br>

&gt;=C2=A0*Sent:*=C2=A0Wednesday,=C2=A0October=C2=A030,=C2=A02019=C2=A09:41=
=C2=A0AM<br>

&gt;=C2=A0*To:*=C2=A0quic=C2=A0&lt;<a href=3D"mailto:quic@ietf.org" target=
=3D"_blank" style=3D"color:#0000ff;text-decoration:underline #0000ff">quic@=
ietf.org</a>&gt;;=C2=A0jri.ietf=C2=A0&lt;<a href=3D"mailto:jri.ietf@gmail.c=
om" target=3D"_blank" style=3D"color:#0000ff;text-decoration:underline #000=
0ff">jri.ietf@gmail.com</a>&gt;;=C2=A0mt=C2=A0<br>

&gt;=C2=A0&lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"_blank" style=
=3D"color:#0000ff;text-decoration:underline #0000ff">mt@lowentropy.net</a>&=
gt;<br>

&gt;=C2=A0*Cc:*=C2=A0</span><span style=3D"font-size:14.0px;font-family:MS =
Gothic;color:black">=E5=88=98=E5=A4=A7</span><span style=3D"font-size:14.0p=
x;font-family:Microsoft JhengHei,sans-serif;color:black">=E9=B9=8F</span><s=
pan style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black">(<=
/span><span style=3D"font-size:14.0px;font-family:Microsoft JhengHei,sans-s=
erif;color:black">=E9=B9=8F=E6=88=90</span><span style=3D"font-size:14.0px;=
font-family:Tahoma,sans-serif;color:black">)=C2=A0&lt;<a href=3D"mailto:max=
.ldp@alibaba-inc.com" target=3D"_blank" style=3D"color:#0000ff;text-decorat=
ion:underline #0000ff">max.ldp@alibaba-inc.com</a>&gt;<br>

&gt;=C2=A0*Subject:*=C2=A0Fast=C2=A0Address=C2=A0Validation=C2=A0-=C2=A0abo=
ut<br>

&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0Hi=C2=A0Martin,=C2=A0Jana,=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0I=C2=A0read=C2=A0through=C2=A0<a href=3D"https://www.ietf.org/id/=
draft-ietf-quic-transport-23.txt" target=3D"_blank" style=3D"color:#0000ff;=
text-decoration:underline #0000ff">https://www.ietf.org/id/draft-ietf-quic-=
transport-23.txt</a>=C2=A0<br>

&gt;=C2=A0and=C2=A0have=C2=A0a=C2=A0few=C2=A0comments=C2=A0and=C2=A0ideas=
=C2=A0to=C2=A0discuss.<br>

&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0[QUIC-Trans]=C2=A0defines=C2=A0a=C2=A0token=C2=A0based=C2=A0schem=
e=C2=A0to=C2=A0facilitate=C2=A0address=C2=A0<br>

&gt;=C2=A0validation=C2=A0of=C2=A0a=C2=A0client.=C2=A0The=C2=A0token=C2=A0M=
UST=C2=A0be=C2=A0covered=C2=A0by=C2=A0integrity=C2=A0<br>

&gt;=C2=A0protection=C2=A0against=C2=A0modification=C2=A0or=C2=A0falsificat=
ion=C2=A0by=C2=A0clients.=C2=A0The=C2=A0server=C2=A0<br>

&gt;=C2=A0remembers=C2=A0the=C2=A0value=C2=A0it=C2=A0sends=C2=A0to=C2=A0cli=
ents=C2=A0and=C2=A0validates=C2=A0the=C2=A0token=C2=A0sent=C2=A0<br>

&gt;=C2=A0back=C2=A0from=C2=A0a=C2=A0client.=C2=A0In=C2=A0its=C2=A0design,=
=C2=A0Retry=C2=A0packet=C2=A0is=C2=A0used=C2=A0to=C2=A0deliver=C2=A0the=C2=
=A0<br>

&gt;=C2=A0token=C2=A0to=C2=A0a=C2=A0client=C2=A0which=C2=A0address=C2=A0has=
=C2=A0not=C2=A0yet=C2=A0been=C2=A0validated.=C2=A0It=C2=A0voids=C2=A0<br>

&gt;=C2=A0the=C2=A0first=C2=A0transmission=C2=A0of=C2=A0the=C2=A0Initial=C2=
=A0packet=C2=A0sent=C2=A0by=C2=A0the=C2=A0client,=C2=A0and=C2=A0<br>

&gt;=C2=A0triggers=C2=A0a=C2=A0second=C2=A0Initial=C2=A0packet=C2=A0to=C2=
=A0be=C2=A0sent=C2=A0with=C2=A0the=C2=A0token.=C2=A0The=C2=A0<br>

&gt;=C2=A0exchange=C2=A0of=C2=A0token=C2=A0will=C2=A0cause=C2=A0longer=C2=
=A0connection=C2=A0establishment=C2=A0delay=C2=A0for=C2=A0<br>

&gt;=C2=A0a=C2=A0client.<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0To=C2=A0improve=C2=A0the=C2=A0efficiency=C2=A0of=C2=A0address=C2=
=A0validation=C2=A0during=C2=A0handshake,=C2=A0one=C2=A0<br>

&gt;=C2=A0idea=C2=A0is=C2=A0that=C2=A0the=C2=A0same=C2=A0token=C2=A0can=C2=
=A0be=C2=A0exchanged=C2=A0via=C2=A0a=C2=A0different=C2=A0container=C2=A0<br=
>

&gt;=C2=A0i.e.=C2=A0the=C2=A0Handshake=C2=A0packet,=C2=A0that=C2=A0eliminat=
es=C2=A0the=C2=A0use=C2=A0of=C2=A0Retry=C2=A0packet=C2=A0for=C2=A0<br>

&gt;=C2=A0token=C2=A0delivery.=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0I=C2=A0am=C2=A0working=C2=A0on=C2=A0the=C2=A0complete=C2=A0draft=
=C2=A0and=C2=A0will=C2=A0submit=C2=A0it=C2=A0by=C2=A0Friday.=C2=A0Before=C2=
=A0<br>

&gt;=C2=A0that,=C2=A0hope=C2=A0this=C2=A0can=C2=A0be=C2=A0discussed=C2=A0in=
=C2=A0email=C2=A0first.<br>

&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0BR,<br>
&gt;=C2=A0<br>
&gt;=C2=A0Qing=C2=A0An<br>
&gt;</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:.0px;font-size:14.7px;font-family:Ca=
libri,sans-serif;line-height:20.0px">
<span style=3D"font-size:14.0px;font-family:Tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
</div>
</div>
<div style=3D"line-height:20.0px;clear:both"><br></div>
</div>
</div>
</div>
</blockquote>
<div style=3D"line-height:20.0px;clear:both"><br></div>
</div>
</div>


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

--000000000000d4995a05964911d4--


From nobody Fri Nov  1 07:01:11 2019
Return-Path: <ximaera@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 61B0112006E for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 07:01:09 -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_HELO_NONE=0.001, 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 4Wko8gt1OBnC for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 07:01:07 -0700 (PDT)
Received: from mail-yw1-xc2b.google.com (mail-yw1-xc2b.google.com [IPv6:2607:f8b0:4864:20::c2b]) (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 B6DC9120147 for <quic@ietf.org>; Fri,  1 Nov 2019 07:01:07 -0700 (PDT)
Received: by mail-yw1-xc2b.google.com with SMTP id i2so3489957ywg.13 for <quic@ietf.org>; Fri, 01 Nov 2019 07:01:07 -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=93T7Ijnd2USx0OFgEJWv/NjKQ0j+8IhAFTpRgvQzTGs=; b=sXwRmgPexnVC5T/bEIvMOmz1xrkqFLAwZjX8JUFOj7gtpJFRcktgv7Pq0qzbVP8B/e Sh+W7cKdKhQqTfa76aCT9Y7CwmGcKuiEmKNj9sz2WIXjH2ydQaieT82HHCb+D14LQTSt 3vcNRnZ+AhlmVGpPYx5M2tSK0gT727GcSNOGcrU6m8fam2UC9wFuBr7qJNOjB2kFKig2 b9J+JIjPymCzRyIQFgB3WpR73BrsN/CqWtpPp2g10pRwoMDY+MbeNqrbxYmglIFT5f/v 0KZbNKtSQ94BN1HLfBRhkXbpUw9b0C798MAMkGQufkbrDR6Mf/9zkVAOzQMGf6S/20rC 8k+Q==
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=93T7Ijnd2USx0OFgEJWv/NjKQ0j+8IhAFTpRgvQzTGs=; b=lKRIEKyjMyr4FV9OplrcOvQKjWTGqU2SaIly51xGMtU3l6Bolon/aciq13Q1X6Bp36 gTg67t+FIyx1XbqP516AfNDVyu6YiXpBnJyQHvEcAP83bNXLw7yVpfJmZH3wH6Hz/qaV riRUjThQTRFpIY7qCRVrsN+h31ItFy1NasHaXiApQB5ik8oqvRR1kE0k69Dxadrfk8hd 01KTF9J+0Ry1AznhmvrVRHlJmymjeOrUFcIUXV4TLvPGoFxjIRoj3NUIhqyHKoRgdPkQ u/cn8jZ6NIuKJHXvjSvF95FciLxl/ll3HkSr4RMmwVGDP4dRrulipupPxipHLLiCliWj cTkQ==
X-Gm-Message-State: APjAAAVaYpz2K/j2a0W8Ppfjq4eMdfAulueqxdmuzhO9vTIEZRpL+ZNs iGx7XSD6134rDZcXbJ3EyZ3tn+MFgvbRR1NwuP0=
X-Google-Smtp-Source: APXvYqzVlPu++mhUSrqiWm0VsCuS0tPtbQgkHKMEahzRwhaHBCnVAVgedjkg4AbVm3AQXBmkFGD/Da7znOIWbBAPcms=
X-Received: by 2002:a81:30cb:: with SMTP id w194mr8424298yww.489.1572616866151;  Fri, 01 Nov 2019 07:01:06 -0700 (PDT)
MIME-Version: 1.0
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com> <CALZ3u+YyOQxA5zBxkhDj9-wObfqjxPxPyXH9PumaW79DNkKjsg@mail.gmail.com> <6ab3b6d6-7638-4b96-b2a3-4212f747a7af.anqing.aq@alibaba-inc.com>
In-Reply-To: <6ab3b6d6-7638-4b96-b2a3-4212f747a7af.anqing.aq@alibaba-inc.com>
From: =?UTF-8?Q?T=C3=B6ma_Gavrichenkov?= <ximaera@gmail.com>
Date: Fri, 1 Nov 2019 17:00:54 +0300
Message-ID: <CALZ3u+ZaHzbNEzUsUa2bYXy2eB+fgkyzSDQir_mtTyLrrcAm7A@mail.gmail.com>
Subject: Re: Fast Address Validation - about
To: Qing An <anqing.aq@alibaba-inc.com>
Cc: IETF QUIC WG <quic@ietf.org>, "jri.ietf" <jri.ietf@gmail.com>, mt <mt@lowentropy.net>,  =?UTF-8?B?5YiY5aSn6bmPKOm5j+aIkCk=?= <max.ldp@alibaba-inc.com>
Content-Type: multipart/alternative; boundary="000000000000acc20d059649650c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/hm57sCYGrZpyJB2xwmFnXrvUXJ4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 14:01:10 -0000

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

On Fri, Nov 1, 2019, 4:26 PM Qing An <anqing.aq@alibaba-inc.com> wrote:

> Right, client address validation can provide protection against floods,
> but today's server often has other approaches to handle floods.
>

Speaking of Hello flood (and SYN flood), what particular approaches do you
have in mind?

--
T=C3=B6ma

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

<div dir=3D"auto"><div><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D=
"gmail_attr">On Fri, Nov 1, 2019, 4:26 PM Qing An &lt;<a href=3D"mailto:anq=
ing.aq@alibaba-inc.com">anqing.aq@alibaba-inc.com</a>&gt; wrote:</div><bloc=
kquote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #cc=
c solid;padding-left:1ex"><div><div style=3D"line-height:1.7;font-family:Ta=
homa,Arial,STHeiti,SimSun;font-size:14.0px;color:#000000"><div style=3D"cle=
ar:both">Right, client address validation can provide protection against fl=
oods, but today&#39;s server often has other approaches to handle floods.</=
div></div></div></blockquote></div></div><div dir=3D"auto"><br></div><div d=
ir=3D"auto">Speaking of Hello flood (and SYN flood), what particular approa=
ches do you have in mind?</div><div dir=3D"auto"><br></div><div dir=3D"auto=
">--</div><div dir=3D"auto">T=C3=B6ma</div><div dir=3D"auto"></div></div>

--000000000000acc20d059649650c--


From nobody Fri Nov  1 07:47:26 2019
Return-Path: <anqing.aq@alibaba-inc.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 98FAA1201A3 for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 07:47:24 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 (1024-bit key) header.d=alibaba-inc.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 IWTqlsE1ztle for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 07:47:22 -0700 (PDT)
Received: from out0-138.mail.aliyun.com (out0-138.mail.aliyun.com [140.205.0.138]) (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 0200A120044 for <quic@ietf.org>; Fri,  1 Nov 2019 07:47:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1572619635; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=X/xJDM8JxMT/qkuklk7fORPN9LakNzxKM6UAAbR88Qg=; b=WJcoyhXJoPetAKj7kGQW3iepm1UfNdU9BYwPAQD0PPKmeCgoYStlW9uvfD8oozl9fpZtdDmUdnvD2zidssFEv0dW0Ukh7WUzfD6IQF7h1oKipdtPxOLxWnOr5O4gPJPdz3deAerr49PLXY+5FyrrDuzLqXfTLM8jV52clYaoXP8=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R161e4; CH=green; DM=||false|; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03300; MF=anqing.aq@alibaba-inc.com; NM=1; PH=DW; RN=5; SR=0; TI=alimail_ios_2.COREAPIb4dc312a0dbd47fcbfcc9c12d14e889e; 
Received: from WS-web (anqing.aq@alibaba-inc.com[alimail_ios_2.COREAPIb4dc312a0dbd47fcbfcc9c12d14e889e]) by e01l07449.eu6 at Fri, 01 Nov 2019 22:47:13 +0800
Date: Fri, 01 Nov 2019 22:47:13 +0800
From: "Qing An" <anqing.aq@alibaba-inc.com>
To: "=?UTF-8?B?VMO2bWEgR2F2cmljaGVua292?=" <ximaera@gmail.com>
Cc: "IETF QUIC WG" <quic@ietf.org>, "jri.ietf" <jri.ietf@gmail.com>, "mt" <mt@lowentropy.net>, "Max" <max.ldp@alibaba-inc.com>
Message-ID: <cee17fee-fed3-497b-82fc-5deda3d0f565.anqing.aq@alibaba-inc.com>
Subject: =?UTF-8?B?UmU6UmU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQ=?=
X-Priority: 3
X-Mailer: [Alimail-Mailagent revision 2765257]
MIME-Version: 1.0
In-Reply-To: <CALZ3u+ZaHzbNEzUsUa2bYXy2eB+fgkyzSDQir_mtTyLrrcAm7A@mail.gmail.com>
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com> <CALZ3u+YyOQxA5zBxkhDj9-wObfqjxPxPyXH9PumaW79DNkKjsg@mail.gmail.com> <6ab3b6d6-7638-4b96-b2a3-4212f747a7af.anqing.aq@alibaba-inc.com>, <CALZ3u+ZaHzbNEzUsUa2bYXy2eB+fgkyzSDQir_mtTyLrrcAm7A@mail.gmail.com>
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_24763_55ce3940_5dbc4571_356399"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/jpdefLzQZsurJhIM4ztmJYUJZ6c>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 14:47:25 -0000

------=ALIBOUNDARY_24763_55ce3940_5dbc4571_356399
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

CkZvciBpbml0aWFsIGZsb29kLCB0aGVyZSBhcmUgYXBwcm9hY2hlcyBsaWtlIHNvdXJjZSBhZGRy
ZXNzIHN0YXRpc3RpY3MgYW5kIHNwZWVkIGxpbWl0YXRpb24uCgoKCiAtLS0tLS0tLS0tLS0tLS0t
LS1PcmlnaW5hbCBNYWlsIC0tLS0tLS0tLS0tLS0tLS0tLQpTZW5kZXI6VMO2bWEgR2F2cmljaGVu
a292IDx4aW1hZXJhQGdtYWlsLmNvbT4KU2VuZCBEYXRlOkZyaSBOb3YgMSAyMjowMTowOCAyMDE5
ClJlY2lwaWVudHM6UWluZyBBbiA8YW5xaW5nLmFxQGFsaWJhYmEtaW5jLmNvbT4KQ0M6SUVURiBR
VUlDIFdHIDxxdWljQGlldGYub3JnPiwganJpLmlldGYgPGpyaS5pZXRmQGdtYWlsLmNvbT4sIG10
IDxtdEBsb3dlbnRyb3B5Lm5ldD4sIOWImOWkp+m5jyjpuY/miJApIDxtYXgubGRwQGFsaWJhYmEt
aW5jLmNvbT4KU3ViamVjdDpSZTogRmFzdCBBZGRyZXNzIFZhbGlkYXRpb24gLSBhYm91dAoKT24g
RnJpLCBOb3YgMSwgMjAxOSwgNDoyNiBQTSBRaW5nIEFuIDxhbnFpbmcuYXFAYWxpYmFiYS1pbmMu
Y29tPiB3cm90ZToKUmlnaHQsIGNsaWVudCBhZGRyZXNzIHZhbGlkYXRpb24gY2FuIHByb3ZpZGUg
cHJvdGVjdGlvbiBhZ2FpbnN0IGZsb29kcywgYnV0IHRvZGF5J3Mgc2VydmVyIG9mdGVuIGhhcyBv
dGhlciBhcHByb2FjaGVzIHRvIGhhbmRsZSBmbG9vZHMuCgpTcGVha2luZyBvZiBIZWxsbyBmbG9v
ZCAoYW5kIFNZTiBmbG9vZCksIHdoYXQgcGFydGljdWxhciBhcHByb2FjaGVzIGRvIHlvdSBoYXZl
IGluIG1pbmQ/CgotLQpUw7ZtYQo=
------=ALIBOUNDARY_24763_55ce3940_5dbc4571_356399
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64

PGRpdiBpZD0ibWFpbGJveC1jb252ZXJzYXRpb24iPjxkaXY+PGJyPjwvZGl2PjxkaXY+Rm9yIGlu
aXRpYWwgZmxvb2QsIHRoZXJlIGFyZSBhcHByb2FjaGVzIGxpa2Ugc291cmNlIGFkZHJlc3Mgc3Rh
dGlzdGljcyBhbmQgc3BlZWQgbGltaXRhdGlvbi48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2Pjxi
cj48L2Rpdj48YmxvY2txdW90ZT48ZGl2PjxkaXYgc3R5bGU9ImZvbnQtc2l6ZTogNzAlIj4gLS0t
LS0tLS0tLS0tLS0tLS0tT3JpZ2luYWwgTWFpbCAtLS0tLS0tLS0tLS0tLS0tLS08L2Rpdj48ZGl2
PjxzcGFuIGNsYXNzPSJmb3J3YXJkLWhlYWRlci10aXRsZSI+U2VuZGVyOjwvc3Bhbj5Uw7ZtYSBH
YXZyaWNoZW5rb3YgJmx0O3hpbWFlcmFAZ21haWwuY29tJmd0OzwvZGl2PjxkaXY+PHNwYW4gY2xh
c3M9ImZvcndhcmQtaGVhZGVyLXRpdGxlIj5TZW5kIERhdGU6PC9zcGFuPkZyaSBOb3YgIDEgMjI6
MDE6MDggMjAxOTwvZGl2PjxkaXY+PHNwYW4gY2xhc3M9ImZvcndhcmQtaGVhZGVyLXRpdGxlIj5S
ZWNpcGllbnRzOjwvc3Bhbj5RaW5nIEFuICZsdDthbnFpbmcuYXFAYWxpYmFiYS1pbmMuY29tJmd0
OzwvZGl2PjxkaXY+PHNwYW4gY2xhc3M9ImZvcndhcmQtaGVhZGVyLXRpdGxlIj5DQzo8L3NwYW4+
SUVURiBRVUlDIFdHICZsdDtxdWljQGlldGYub3JnJmd0OywganJpLmlldGYgJmx0O2pyaS5pZXRm
QGdtYWlsLmNvbSZndDssIG10ICZsdDttdEBsb3dlbnRyb3B5Lm5ldCZndDssIOWImOWkp+m5jyjp
uY/miJApICZsdDttYXgubGRwQGFsaWJhYmEtaW5jLmNvbSZndDs8L2Rpdj48ZGl2PjxzcGFuIGNs
YXNzPSJmb3J3YXJkLWhlYWRlci10aXRsZSI+U3ViamVjdDo8L3NwYW4+UmU6IEZhc3QgQWRkcmVz
cyBWYWxpZGF0aW9uIC0gYWJvdXQ8L2Rpdj48L2Rpdj48ZGl2PjxibG9ja3F1b3RlIGNsYXNzPSJn
bWFpbF9xdW90ZSI+PGRpdj48ZGl2PjxkaXYgY2xhc3M9ImdtYWlsX3F1b3RlIj48ZGl2IGNsYXNz
PSJnbWFpbF9hdHRyIj5PbiBGcmksIE5vdiAxLCAyMDE5LCA0OjI2IFBNIFFpbmcgQW4gJmx0Ozxh
IGhyZWY9Im1haWx0bzphbnFpbmcuYXFAYWxpYmFiYS1pbmMuY29tIiB0YXJnZXQ9Il9ibGFuayI+
YW5xaW5nLmFxQGFsaWJhYmEtaW5jLmNvbTwvYT4mZ3Q7IHdyb3RlOjwvZGl2PjxibG9ja3F1b3Rl
IGNsYXNzPSJnbWFpbF9xdW90ZSIgc3R5bGU9Im1hcmdpbjogMCAwIDAgMC44ZXg7Ym9yZGVyLWxl
ZnQ6IDEuMHB4ICNjY2NjY2Mgc29saWQ7cGFkZGluZy1sZWZ0OiAxLjBleDsiPjxkaXY+PGRpdiBz
dHlsZT0ibGluZS1oZWlnaHQ6IDEuNztmb250LWZhbWlseTogdGFob21hICwgYXJpYWwgLCBzdGhl
aXRpICwgc2ltc3VuO2ZvbnQtc2l6ZTogMTQuMHB4O2NvbG9yOiAjMDAwMDAwOyI+PGRpdiBzdHls
ZT0iY2xlYXI6IGJvdGg7Ij5SaWdodCwgY2xpZW50IGFkZHJlc3MgdmFsaWRhdGlvbiBjYW4gcHJv
dmlkZSBwcm90ZWN0aW9uIGFnYWluc3QgZmxvb2RzLCBidXQgdG9kYXkncyBzZXJ2ZXIgb2Z0ZW4g
aGFzIG90aGVyIGFwcHJvYWNoZXMgdG8gaGFuZGxlIGZsb29kcy48L2Rpdj48L2Rpdj48L2Rpdj48
L2Jsb2NrcXVvdGU+PC9kaXY+PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj5TcGVha2luZyBvZiBI
ZWxsbyBmbG9vZCAoYW5kIFNZTiBmbG9vZCksIHdoYXQgcGFydGljdWxhciBhcHByb2FjaGVzIGRv
IHlvdSBoYXZlIGluIG1pbmQ/PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj4tLTwvZGl2PjxkaXY+
VMO2bWE8L2Rpdj48ZGl2PjwvZGl2PjwvZGl2Pgo8L2Jsb2NrcXVvdGU+PC9kaXY+PC9ibG9ja3F1
b3RlPjwvZGl2Pg==
------=ALIBOUNDARY_24763_55ce3940_5dbc4571_356399--


From nobody Fri Nov  1 07:55:17 2019
Return-Path: <anqing.aq@alibaba-inc.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 D877A1201E3; Fri,  1 Nov 2019 07:55:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.987
X-Spam-Level: 
X-Spam-Status: No, score=-1.987 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_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, UNPARSEABLE_RELAY=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=alibaba-inc.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 R6IVepbzYM-j; Fri,  1 Nov 2019 07:55:13 -0700 (PDT)
Received: from out0-154.mail.aliyun.com (out0-154.mail.aliyun.com [140.205.0.154]) (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 2A7031201DB; Fri,  1 Nov 2019 07:55:09 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1572620105; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=4UdcTmYQAkV9bxg8qQ4dknN0GN3QZ2r1pRMOHk9Fp30=; b=XWIeA/xAx6I376VCERKysS4mHvpyjuEOiowwAf5gS4fKyV/G54YlZaUlITdPvZ/4Se+6xnUgyTFG7gz47mcytXdvnN0Gv15R2B4NvqGq+ErvLxjNg3Xrd3G/N5yFfSC+d0SaE2OZl+eZFdYrXdt/WyEMTgMLGXD9rC5oke0d+M4=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R191e4; CH=green; DM=||false|; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e01a16384; MF=anqing.aq@alibaba-inc.com; NM=1; PH=DW; RN=7; SR=0; TI=alimail_ios_2.COREAPI1cb7bdc400e84b82b8e4087904d24f8e; 
Received: from WS-web (anqing.aq@alibaba-inc.com[alimail_ios_2.COREAPI1cb7bdc400e84b82b8e4087904d24f8e]) by e01e01546.eu6 at Fri, 01 Nov 2019 22:55:03 +0800
Date: Fri, 01 Nov 2019 22:55:03 +0800
From: "Qing An" <anqing.aq@alibaba-inc.com>
To: "=?UTF-8?B?TWlra2VsIEZhaG7DuGUgSsO4cmdlbnNlbg==?=" <mikkelfj@gmail.com>, "Marten Seemann" <martenseemann@gmail.com>
Cc: "jri.ietf" <jri.ietf@gmail.com>, "QUIC" <quic-bounces@ietf.org>, "quic" <quic@ietf.org>, "mt" <mt@lowentropy.net>, "Max" <max.ldp@alibaba-inc.com>
Message-ID: <8f87c3ce-d9c0-4017-be6d-4a411daeaa2d.anqing.aq@alibaba-inc.com>
Subject: =?UTF-8?B?UmU6UmU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQ=?=
X-Priority: 3
X-Mailer: [Alimail-Mailagent revision 2765257]
MIME-Version: 1.0
In-Reply-To: <CAN1APddvVeqXeWCZbe9WrLrOyVOWM5-1Dg8x5B4UpNwP6YOGrA@mail.gmail.com>
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com> <BN6PR2201MB1700F72F3DC8F6C3CF79902CDA600@BN6PR2201MB1700.namprd22.prod.outlook.com> <bd15f357-8e7a-42af-bf28-79f7177da385@www.fastmail.com> <f55efb80-1a95-4190-84e5-b81948a7f081.anqing.aq@alibaba-inc.com> <BN6PR2201MB17005571E88F1C68769091A3DA630@BN6PR2201MB1700.namprd22.prod.outlook.com> <69d1a917-b1f9-4142-afb0-f5c67abe7334.anqing.aq@alibaba-inc.com> <CAOYVs2r0zJzbfw5L2Mck8VEJhtyfQtHwF-db5VG45HDTF0WoOQ@mail.gmail.com> <7ac8ad51-c1a2-461b-bc47-021b3875eab8.anqing.aq@alibaba-inc.com>, <CAN1APddvVeqXeWCZbe9WrLrOyVOWM5-1Dg8x5B4UpNwP6YOGrA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_46354_4ec69940_5dbc4747_3544bd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/JV8DXvKC9i4Hk39e0hx_kyBpj_A>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 14:55:16 -0000

------=ALIBOUNDARY_46354_4ec69940_5dbc4747_3544bd
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

CkFnYWluLCB0aGUgZmFzdCBhZGRyZXNzIHZhbGlkYXRpb24gaXMgdG8gcHJvdmlkZSBhbm90aGVy
IG9wdGlvbiBmb3Igc2VydmVyLCBub3QgdG8gZHJvcCB0aGUgUmV0cnkgYXBwcm9hY2guCgpJIHRo
aW5rIGlmIGNob29zZSBub3QgdG8gc2VuZCBhIFJldHJ5LCBpdCBpcyBuZWNlc3NhcnkgdG8gZGVm
aW5lIGhvdyB0byBkZWxpdmVyIHRva2VuIGZyb20gc2VydmVyIHRvIGNsaWVudC4gSW4gdGhpcyBj
YXNlLCAgdmlhIG5ld190b2tlbiBmcmFtZSBpbiBoYW5kc2hha2UgY2FuIGJlIGFuIGFwcHJvYWNo
LgoKCgogLS0tLS0tLS0tLS0tLS0tLS0tT3JpZ2luYWwgTWFpbCAtLS0tLS0tLS0tLS0tLS0tLS0K
U2VuZGVyOk1pa2tlbCBGYWhuw7hlIErDuHJnZW5zZW4gPG1pa2tlbGZqQGdtYWlsLmNvbT4KU2Vu
ZCBEYXRlOkZyaSBOb3YgMSAyMTozNzo0MiAyMDE5ClJlY2lwaWVudHM6UWluZyBBbiA8YW5xaW5n
LmFxQGFsaWJhYmEtaW5jLmNvbT4sIE1hcnRlbiBTZWVtYW5uIDxtYXJ0ZW5zZWVtYW5uQGdtYWls
LmNvbT4KQ0M6anJpLmlldGYgPGpyaS5pZXRmQGdtYWlsLmNvbT4sIFFVSUMgPHF1aWMtYm91bmNl
c0BpZXRmLm9yZz4sIHF1aWMgPHF1aWNAaWV0Zi5vcmc+LCBtdCA8bXRAbG93ZW50cm9weS5uZXQ+
LCDliJjlpKfpuY8o6bmP5oiQKSA8bWF4LmxkcEBhbGliYWJhLWluYy5jb20+ClN1YmplY3Q6UmU6
IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQKCllvdSBvbmx5IHNhdmUgYSByb3VuZHRy
aXAgYmVjYXVzZSB5b3UgZG8gbm90IHNlbmQgYSBSZXRyeS4KCklmIHlvdSBjaG9vc2Ugbm90IHRv
IHNlbmQgYSBSZXRyeSwgdGhlIGNsaWVudCBldmVudHVhbGx5IGdldHMgdmFsaWRhdGVkIGFueXdh
eSBiZWNhdXNlIG90aGVyd2lzZSB0aGUgaGFuZHNoYWtlIGNvdWxkIG5vdCBjb21wbGV0ZS4gVGhl
cmVmb3JlIGEgUmV0cnkgdG9rZW4gaXMgbm90IG5lZWRlZCBpZiB5b3UgZ28gZG93biB0aGF0IHBh
dGguIEluIHRoaXMgY2FzZSB0aGUgUlRUIG92ZXJoZWFkIHdpdGggZmFzdCBhZGRyZXNzIHZhbGlk
YXRpb24gaXMgdGhlIHNhbWUgYXMgb3JkaW5hcnkgUVVJQyAxLVJUVCBoYW5kc2hha2UuCgpPbiB0
aGUgb3RoZXIgaGFuZCwgaW4gdGhlIGNhc2Ugd2hlcmUgUmV0cnkgaXMgbmVlZGVkLCB0aGUgZmFz
dCBhZGRyZXNzIHZhbGlkYXRpb24gYXBwcm9hY2ggZG9lcyBub3Qgc29sdmUgdGhlIHByb2JsZW0g
d2hpY2ggaXMgb25lIG9mIDEpIGRlZmVyIGhhbmRzaGFrZSBwcm9jZXNzaW5nIGFuZCBzZXJ2ZXIg
c3RhdGUgdW50aWwgYWZ0ZXIgdGhlIGFkZHJlc3MgaXMgdmVyaWZpZWQsIG9yIDIpIHJlZGlyZWN0
IHRoZSBjbGllbnQgdG8gYW5vdGhlciBzZXJ2ZXIgdGhyb3VnaCBhIGNoYW5nZSBpbiBDb25uZWN0
aW9uSUQuCgoKCk9uIDEgTm92ZW1iZXIgMjAxOSBhdCAxNC4yNi4yNCwgUWluZyBBbiAoYW5xaW5n
LmFxQGFsaWJhYmEtaW5jLmNvbSkgd3JvdGU6IAoKSSBiZWxpZXZlIHRoaXMgY2FuIHNhdmUgMS1S
VFQuCgpBcyBmb3IgdGhlIHByaXZhY3kgcmlzaywgbmV3X3Rva2VuIGZyYW1lIGNhbiBiZSBkZWxp
dmVyZWQgdmlhIGhhbmRzaGFrZQoKCgogLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tCkZyb206TWFydGVuIFNlZW1hbm4gPG1h
cnRlbnNlZW1hbm5AZ21haWwuY29tPgpTZW5kIFRpbWU6MjAxOeW5tDEx5pyIMeaXpSjmmJ/mnJ/k
upQpIDIwOjU0ClRvOuWuieWLjSjojrPpgLgpIDxhbnFpbmcuYXFAYWxpYmFiYS1pbmMuY29tPgpD
YzpRVUlDIDxxdWljLWJvdW5jZXNAaWV0Zi5vcmc+OyBxdWljIDxxdWljQGlldGYub3JnPjsganJp
LmlldGYgPGpyaS5pZXRmQGdtYWlsLmNvbT47IG10IDxtdEBsb3dlbnRyb3B5Lm5ldD47IG1pa2tl
bGZqIDxtaWtrZWxmakBnbWFpbC5jb20+OyDliJjlpKfpuY8o6bmP5oiQKSA8bWF4LmxkcEBhbGli
YWJhLWluYy5jb20+ClN1YmplY3Q6UmU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQK
CkkgZG9uJ3Qgc2VlIGFueSBlbmhhbmNlZCBjbGllbnQgZXhwZXJpZW5jZSwgc2luY2UgdGhlIGhh
bmRzaGFrZSB0YWtlcyBleGFjdGx5IHRoZSBzYW1lIG51bWJlciBvZiByb3VuZCB0cmlwcyB3aXRo
IHlvdXIgcHJvcG9zYWwgYXMgd2l0aCB0aGUgY3VycmVudCB2ZXJzaW9uIG9mIHRoZSBRVUlDIGRy
YWZ0LgpTZW5kaW5nIE5FV19UT0tFTiBpbiBJbml0aWFsIHBhY2tldHMgcHJvdmlkZXMgbm8gYmVu
ZWZpdCBvdmVyIHNlbmRpbmcgaXQgaW4gMS1SVFQgcGFja2V0cywgYnV0IGNvbWVzIHdpdGggd29y
c2UgcHJpdmFjeSBwcm9wZXJ0aWVzLCBzaW5jZSBJbml0aWFsIHBhY2tldHMgYXJlIG5vdCBlbmNy
eXB0ZWQgYW5kIGNhbiB0aGVyZWZvcmUgYmUgcmVhZCBieSBvbi1wYXRoIG9ic2VydmVycy4KCk9u
IEZyaSwgTm92IDEsIDIwMTkgYXQgNzozNyBQTSBRaW5nIEFuIDxhbnFpbmcuYXFAYWxpYmFiYS1p
bmMuY29tPiB3cm90ZToKCklmIHNvLCBmb3IgdGhlIGZpcnN0IGNvbm5lY3Rpb24gYmV0d2VlbiBj
bGllbnQgYW5kIHNlcnZlciwgc2VydmVyIGNhbiBjaG9vc2UgdG8gZWxpbWluYXRlIHRoZSB1c2Ug
b2YgUmV0cnkgcGFja2V0IGZvciB0b2tlbiBkZWxpdmVyeSwgYW5kIHJlbHkgb24gaGFuZHNoYWtl
IGVuY3J5cHRpb24gbGF5ZXIgdG8gcHJvdmUgcmV0dXJuIHJvdXRhYmlsaXR5LiAgSW4gYWRkaXRp
b24sIE5ld19Ub2tlbiBmcmFtZSBpcyB1c2VkIGJ5IHNlcnZlciwgdmlhIGkuZS4gdGhlIEluaXRp
YWwgcGFja2V0LCB0byBwcm92aWRlIHRoZSBjbGllbnQgd2l0aCBhbiBhZGRyZXNzIHZhbGlkYXRp
b24gdG9rZW4gdGhhdCBjYW4gYmUgdXNlZCB0byB2YWxpZGF0ZSBmdXR1cmUgY29ubmVjdGlvbnMu
CgpJdCBjYW4gZW5oYW5jZSB0aGUgZXhwZXJpZW5jZSBpbiBjbGllbnQgc2lkZSBmb3IgdGhlIGZp
cnN0IGNvbm5lY3Rpb24gZXN0YWJsaXNobWVudC4KCkkgc3VibWl0dGVkIHRoZSBkcmFmdCwgaHR0
cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtYW4tZmFzdC1hZGRyZXNzLXZhbGlk
YXRpb24vCgpRaW5nCgoKCiAtLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KRnJvbTpNaWtlIEJpc2hvcCA8bWJpc2hvcEBldmVx
dWVmb3UuYmU+ClNlbmQgVGltZToyMDE55bm0MTHmnIgx5pelKOaYn+acn+S6lCkgMDA6MDYKVG86
5a6J5YuNKOiOs+mAuCkgPGFucWluZy5hcUBhbGliYWJhLWluYy5jb20+OyBxdWljIDxxdWljQGll
dGYub3JnPjsganJpLmlldGYgPGpyaS5pZXRmQGdtYWlsLmNvbT47IG10IDxtdEBsb3dlbnRyb3B5
Lm5ldD47IG1pa2tlbGZqIDxtaWtrZWxmakBnbWFpbC5jb20+ClN1YmplY3Q6UkU6IEZhc3QgQWRk
cmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQKCkFzIE1hcnRpbiBwb2ludGVkIG91dCBpbiB0aGUgZS1t
YWlsIHlvdSByZXBsaWVkIHRvLCBpZiB0aGUgc2VydmVyIGlzIHdpbGxpbmcgdG8gbWFpbnRhaW4g
c3RhdGUsIGFueSBwYWNrZXQgYXQgdGhlIEhhbmRzaGFrZSBlbmNyeXB0aW9uIGxheWVyIHByb3Zl
cyByZXR1cm4gcm91dGFiaWxpdHkuICBUaGVyZSBzZWVtcyB0byBiZSBubyBuZWVkIGZvciBhIHNl
cGFyYXRlIGFkZHJlc3MgdmFsaWRhdGlvbiBtZWNoYW5pc20gaWYgdGhlIHNlcnZlciBpcyB3aWxs
aW5nIHRvIHByb2NlZWQgd2l0aCB0aGUgaGFuZHNoYWtlLgpGcm9tOiBRVUlDIDxxdWljLWJvdW5j
ZXNAaWV0Zi5vcmc+IE9uIEJlaGFsZiBPZiBRaW5nIEFuClNlbnQ6IFRodXJzZGF5LCBPY3RvYmVy
IDMxLCAyMDE5IDg6NTYgQU0KVG86IHF1aWMgPHF1aWNAaWV0Zi5vcmc+OyBqcmkuaWV0ZiA8anJp
LmlldGZAZ21haWwuY29tPjsgbXQgPG10QGxvd2VudHJvcHkubmV0PjsgbWlra2VsZmogPG1pa2tl
bGZqQGdtYWlsLmNvbT4KU3ViamVjdDogUmU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJv
dXQKICAKICAKVG8gY2xhcmlmeSwgdGhlIHByb3Bvc2FsIGlzIG5vdCB0byByZXBsYWNlIHRoZSBl
eGlzdGluZyBSZXRyeS1iYXNlZCB2YWxpZGF0aW9uLCBidXQgdG8gcHJvdmlkZSBhbm90aGVyIG9w
dGlvbiBmb3Igc2VydmVyIHRvIGRvIHRoZSBjbGllbnQgdmFsaWRhdGlvbi4gCiAgCkkgdW5kZXJz
dGFuZCB0aGF0IGluIHNlcnZlciBzaWRlLCBleGNoYW5naW5nIHRoZSB0b2tlbiBhdCB0aGUgSGFu
ZHNoYWtlIGVuY3J5cHRpb24gbGV2ZWwgd2lsbCBtYWtlIHRoZSBzZXJ2ZXIgc3RhcnQgdG8gbWFp
bnRhaW4gaGFuZHNoYWtlIHN0YXRlcy4gQnV0IGluIGNsaWVudCBzaWRlLCBpdCBjYW4gYWNjZWxl
cmF0ZSB0aGUgY29ubmVjdGlvbiBlc3RhYmxpc2htZW50IGZyb20gY2xpZW50IHRvIHNlcnZlci4g
CiAgCiBBbmQgaXQgaXMgdGhlIHNlcnZlcidzIGRlY2lzaW9uIHdoZXRoZXIgdG8gZXhjaGFuZ2Ug
dG9rZW4gaW4gUmV0cnkgb3IgaW4gSGFuZHNoYWtlLiBJZiBzZXJ2ZXIgY2hvb3NlcyB0byBhY2Nl
cHQgdGhlIGNvc3QgYnJvdWdodCBieSB0b2tlbiBleGNoYW5naW5nIGluIEhhbmRzaGFrZSwgaXQg
d2lsbCBicmluZyBtb3JlIGVuaGFuY2VkIGV4cGVyaWVuY2UgaW4gY2xpZW50IHNpZGUuIAogIAog
IAogQlIsIAogUWluZyAKICAKICAKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tIApGcm9tOk1hcnRpbiBUaG9tc29uIDxtdEBs
b3dlbnRyb3B5Lm5ldD4gClNlbmQgVGltZToyMDE55bm0MTDmnIgzMeaXpSjmmJ/mnJ/lm5spIDA2
OjA3IApUbzpxdWljIDxxdWljQGlldGYub3JnPiAKU3ViamVjdDpSZTogRmFzdCBBZGRyZXNzIFZh
bGlkYXRpb24gLSBhYm91dCAKICAKQWxzbyBub3RlIHRoYXQgZXhjaGFuZ2Ugb2YgSGFuZHNoYWtl
IHBhY2tldHMgcHJvdmlkZXMgcHJvb2Ygb2YgcmV0dXJuIHJvdXRlYWJpbGl0eSB2aWEgdGhlIHVz
ZSBvZiB0aGUgZW5jcnlwdGlvbiBrZXlzLCBzbyB0aGVyZSBpcyBubyBuZWVkIHRvIGV4Y2hhbmdl
IHRva2VucyBhdCB0aGF0IGxldmVsLgoKIE9uIFRodSwgT2N0IDMxLCAyMDE5LCBhdCAwMzoyOSwg
TWlrZSBCaXNob3Agd3JvdGU6CiA+ICAKID4gVGhlIGFkdmFudGFnZSBvZiB1c2luZyBSZXRyeSwg
aG93ZXZlciwgaXMgdGhhdCB0aGUgc2VydmVyIGlzIGFibGUgdG8gCiA+IGtlZXAgbWluaW1hbCAo
aWYgYW55KSBzdGF0ZSBhYm91dCB0aGUgY2xpZW50LiBFeGNoYW5naW5nIHRoZSB0b2tlbiBhdCAK
ID4gdGhlIEhhbmRzaGFrZSBlbmNyeXB0aW9uIGxldmVsIG1lYW5zIHRoZSBzZXJ2ZXIgaXMgYWxy
ZWFkeSBkb2luZyB3b3JrIAogPiBhbmQgbWFpbnRhaW5pbmcgc3RhdGUgaW4gb3JkZXIgdG8gcHJv
Y2VzcyB0aGUgaGFuZHNoYWtlLCB3aGljaCBpcyAKID4gZXhhY3RseSB3aGF0IHRoZSBzZXJ2ZXIg
aXMgdHJ5aW5nIHRvIGF2b2lkLgogPiAKID4gCiA+ICpGcm9tOiogUVVJQyA8cXVpYy1ib3VuY2Vz
QGlldGYub3JnPiAqT24gQmVoYWxmIE9mICogUWluZyBBbgogPiAqU2VudDoqIFdlZG5lc2RheSwg
T2N0b2JlciAzMCwgMjAxOSA5OjQxIEFNCiA+ICpUbzoqIHF1aWMgPHF1aWNAaWV0Zi5vcmc+OyBq
cmkuaWV0ZiA8anJpLmlldGZAZ21haWwuY29tPjsgbXQgCiA+IDxtdEBsb3dlbnRyb3B5Lm5ldD4K
ID4gKkNjOiog5YiY5aSn6bmPKOm5j+aIkCkgPG1heC5sZHBAYWxpYmFiYS1pbmMuY29tPgogPiAq
U3ViamVjdDoqIEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQKID4gCiA+IAogPiAKID4g
CiA+IEhpIE1hcnRpbiwgSmFuYSwgCiA+IAogPiBJIHJlYWQgdGhyb3VnaCBodHRwczovL3d3dy5p
ZXRmLm9yZy9pZC9kcmFmdC1pZXRmLXF1aWMtdHJhbnNwb3J0LTIzLnR4dCAKID4gYW5kIGhhdmUg
YSBmZXcgY29tbWVudHMgYW5kIGlkZWFzIHRvIGRpc2N1c3MuCiA+IAogPiAKID4gW1FVSUMtVHJh
bnNdIGRlZmluZXMgYSB0b2tlbiBiYXNlZCBzY2hlbWUgdG8gZmFjaWxpdGF0ZSBhZGRyZXNzIAog
PiB2YWxpZGF0aW9uIG9mIGEgY2xpZW50LiBUaGUgdG9rZW4gTVVTVCBiZSBjb3ZlcmVkIGJ5IGlu
dGVncml0eSAKID4gcHJvdGVjdGlvbiBhZ2FpbnN0IG1vZGlmaWNhdGlvbiBvciBmYWxzaWZpY2F0
aW9uIGJ5IGNsaWVudHMuIFRoZSBzZXJ2ZXIgCiA+IHJlbWVtYmVycyB0aGUgdmFsdWUgaXQgc2Vu
ZHMgdG8gY2xpZW50cyBhbmQgdmFsaWRhdGVzIHRoZSB0b2tlbiBzZW50IAogPiBiYWNrIGZyb20g
YSBjbGllbnQuIEluIGl0cyBkZXNpZ24sIFJldHJ5IHBhY2tldCBpcyB1c2VkIHRvIGRlbGl2ZXIg
dGhlIAogPiB0b2tlbiB0byBhIGNsaWVudCB3aGljaCBhZGRyZXNzIGhhcyBub3QgeWV0IGJlZW4g
dmFsaWRhdGVkLiBJdCB2b2lkcyAKID4gdGhlIGZpcnN0IHRyYW5zbWlzc2lvbiBvZiB0aGUgSW5p
dGlhbCBwYWNrZXQgc2VudCBieSB0aGUgY2xpZW50LCBhbmQgCiA+IHRyaWdnZXJzIGEgc2Vjb25k
IEluaXRpYWwgcGFja2V0IHRvIGJlIHNlbnQgd2l0aCB0aGUgdG9rZW4uIFRoZSAKID4gZXhjaGFu
Z2Ugb2YgdG9rZW4gd2lsbCBjYXVzZSBsb25nZXIgY29ubmVjdGlvbiBlc3RhYmxpc2htZW50IGRl
bGF5IGZvciAKID4gYSBjbGllbnQuCiA+IAogPiAKID4gVG8gaW1wcm92ZSB0aGUgZWZmaWNpZW5j
eSBvZiBhZGRyZXNzIHZhbGlkYXRpb24gZHVyaW5nIGhhbmRzaGFrZSwgb25lIAogPiBpZGVhIGlz
IHRoYXQgdGhlIHNhbWUgdG9rZW4gY2FuIGJlIGV4Y2hhbmdlZCB2aWEgYSBkaWZmZXJlbnQgY29u
dGFpbmVyIAogPiBpLmUuIHRoZSBIYW5kc2hha2UgcGFja2V0LCB0aGF0IGVsaW1pbmF0ZXMgdGhl
IHVzZSBvZiBSZXRyeSBwYWNrZXQgZm9yIAogPiB0b2tlbiBkZWxpdmVyeS4gCiA+IAogPiAKID4g
SSBhbSB3b3JraW5nIG9uIHRoZSBjb21wbGV0ZSBkcmFmdCBhbmQgd2lsbCBzdWJtaXQgaXQgYnkg
RnJpZGF5LiBCZWZvcmUgCiA+IHRoYXQsIGhvcGUgdGhpcyBjYW4gYmUgZGlzY3Vzc2VkIGluIGVt
YWlsIGZpcnN0LgogPiAKID4gCiA+IEJSLAogPiAKID4gUWluZyBBbgogPiAKICAgIAoKCg==
------=ALIBOUNDARY_46354_4ec69940_5dbc4747_3544bd
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64

PGRpdiBpZD0ibWFpbGJveC1jb252ZXJzYXRpb24iPjxkaXY+PGJyPjwvZGl2PjxkaXY+QWdhaW4s
IHRoZSBmYXN0IGFkZHJlc3MgdmFsaWRhdGlvbiBpcyB0byBwcm92aWRlIGFub3RoZXIgb3B0aW9u
IGZvciBzZXJ2ZXIsIG5vdCB0byBkcm9wIHRoZSBSZXRyeSBhcHByb2FjaC48L2Rpdj48ZGl2Pjxi
cj48L2Rpdj48ZGl2PkkgdGhpbmsgaWYgY2hvb3NlIG5vdCB0byBzZW5kIGEgUmV0cnksIGl0IGlz
IG5lY2Vzc2FyeSB0byBkZWZpbmUgaG93IHRvIGRlbGl2ZXIgdG9rZW4gZnJvbSBzZXJ2ZXIgdG8g
Y2xpZW50LiBJbiB0aGlzIGNhc2UsICZuYnNwO3ZpYSBuZXdfdG9rZW4gZnJhbWUgaW4gaGFuZHNo
YWtlIGNhbiBiZSBhbiBhcHByb2FjaC48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2Pjxicj48L2Rp
dj48YmxvY2txdW90ZT48ZGl2PjxkaXYgc3R5bGU9ImZvbnQtc2l6ZTogNzAlIj4gLS0tLS0tLS0t
LS0tLS0tLS0tT3JpZ2luYWwgTWFpbCAtLS0tLS0tLS0tLS0tLS0tLS08L2Rpdj48ZGl2PjxzcGFu
IGNsYXNzPSJmb3J3YXJkLWhlYWRlci10aXRsZSI+U2VuZGVyOjwvc3Bhbj5NaWtrZWwgRmFobsO4
ZSBKw7hyZ2Vuc2VuICZsdDttaWtrZWxmakBnbWFpbC5jb20mZ3Q7PC9kaXY+PGRpdj48c3BhbiBj
bGFzcz0iZm9yd2FyZC1oZWFkZXItdGl0bGUiPlNlbmQgRGF0ZTo8L3NwYW4+RnJpIE5vdiAgMSAy
MTozNzo0MiAyMDE5PC9kaXY+PGRpdj48c3BhbiBjbGFzcz0iZm9yd2FyZC1oZWFkZXItdGl0bGUi
PlJlY2lwaWVudHM6PC9zcGFuPlFpbmcgQW4gJmx0O2FucWluZy5hcUBhbGliYWJhLWluYy5jb20m
Z3Q7LCBNYXJ0ZW4gU2VlbWFubiAmbHQ7bWFydGVuc2VlbWFubkBnbWFpbC5jb20mZ3Q7PC9kaXY+
PGRpdj48c3BhbiBjbGFzcz0iZm9yd2FyZC1oZWFkZXItdGl0bGUiPkNDOjwvc3Bhbj5qcmkuaWV0
ZiAmbHQ7anJpLmlldGZAZ21haWwuY29tJmd0OywgUVVJQyAmbHQ7cXVpYy1ib3VuY2VzQGlldGYu
b3JnJmd0OywgcXVpYyAmbHQ7cXVpY0BpZXRmLm9yZyZndDssIG10ICZsdDttdEBsb3dlbnRyb3B5
Lm5ldCZndDssIOWImOWkp+m5jyjpuY/miJApICZsdDttYXgubGRwQGFsaWJhYmEtaW5jLmNvbSZn
dDs8L2Rpdj48ZGl2PjxzcGFuIGNsYXNzPSJmb3J3YXJkLWhlYWRlci10aXRsZSI+U3ViamVjdDo8
L3NwYW4+UmU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQ8L2Rpdj48L2Rpdj48ZGl2
PjxibG9ja3F1b3RlIGNsYXNzPSJnbWFpbF9xdW90ZSI+PHN0eWxlPgpib2R5IHtmb250LWZhbWls
eTogaGVsdmV0aWNhICwgYXJpYWw7Zm9udC1zaXplOiAxMy4wcHg7fQo8L3N0eWxlPjxkaXYgaWQ9
ImJsb29wX2N1c3RvbWZvbnQiIHN0eWxlPSJmb250LWZhbWlseTogaGVsdmV0aWNhICwgYXJpYWw7
Zm9udC1zaXplOiAxMy4wcHg7Y29sb3I6IDttYXJnaW46IDAuMHB4O2xpbmUtaGVpZ2h0OiBhdXRv
OyI+WW91IG9ubHkgc2F2ZSBhIHJvdW5kdHJpcCBiZWNhdXNlIHlvdSBkbyBub3Qgc2VuZCBhIFJl
dHJ5LjwvZGl2PjxkaXYgaWQ9ImJsb29wX2N1c3RvbWZvbnQiIHN0eWxlPSJmb250LWZhbWlseTog
aGVsdmV0aWNhICwgYXJpYWw7Zm9udC1zaXplOiAxMy4wcHg7Y29sb3I6IDttYXJnaW46IDAuMHB4
O2xpbmUtaGVpZ2h0OiBhdXRvOyI+PGJyPjwvZGl2PjxkaXYgaWQ9ImJsb29wX2N1c3RvbWZvbnQi
IHN0eWxlPSJmb250LWZhbWlseTogaGVsdmV0aWNhICwgYXJpYWw7Zm9udC1zaXplOiAxMy4wcHg7
Y29sb3I6IDttYXJnaW46IDAuMHB4O2xpbmUtaGVpZ2h0OiBhdXRvOyI+SWYgeW91IGNob29zZSBu
b3QgdG8gc2VuZCBhIFJldHJ5LCB0aGUgY2xpZW50IGV2ZW50dWFsbHkgZ2V0cyB2YWxpZGF0ZWQg
YW55d2F5IGJlY2F1c2Ugb3RoZXJ3aXNlIHRoZSBoYW5kc2hha2UgY291bGQgbm90IGNvbXBsZXRl
LiBUaGVyZWZvcmUgYSBSZXRyeSB0b2tlbiBpcyBub3QgbmVlZGVkIGlmIHlvdSBnbyBkb3duIHRo
YXQgcGF0aC4gSW4gdGhpcyBjYXNlIHRoZSBSVFQgb3ZlcmhlYWQgd2l0aCBmYXN0IGFkZHJlc3Mg
dmFsaWRhdGlvbiBpcyB0aGUgc2FtZSBhcyBvcmRpbmFyeSBRVUlDIDEtUlRUIGhhbmRzaGFrZS48
L2Rpdj48ZGl2IGlkPSJibG9vcF9jdXN0b21mb250IiBzdHlsZT0iZm9udC1mYW1pbHk6IGhlbHZl
dGljYSAsIGFyaWFsO2ZvbnQtc2l6ZTogMTMuMHB4O2NvbG9yOiA7bWFyZ2luOiAwLjBweDtsaW5l
LWhlaWdodDogYXV0bzsiPjxicj48L2Rpdj48ZGl2IGlkPSJibG9vcF9jdXN0b21mb250IiBzdHls
ZT0iZm9udC1mYW1pbHk6IGhlbHZldGljYSAsIGFyaWFsO2ZvbnQtc2l6ZTogMTMuMHB4O2NvbG9y
OiA7bWFyZ2luOiAwLjBweDtsaW5lLWhlaWdodDogYXV0bzsiPk9uIHRoZSBvdGhlciBoYW5kLCBp
biB0aGUgY2FzZSB3aGVyZSBSZXRyeSBpcyBuZWVkZWQsIHRoZSBmYXN0IGFkZHJlc3MgdmFsaWRh
dGlvbiBhcHByb2FjaCBkb2VzIG5vdCBzb2x2ZSB0aGUgcHJvYmxlbSB3aGljaCBpcyBvbmUgb2Yg
MSkgZGVmZXIgaGFuZHNoYWtlIHByb2Nlc3NpbmcgYW5kIHNlcnZlciBzdGF0ZSB1bnRpbCBhZnRl
ciB0aGUgYWRkcmVzcyBpcyB2ZXJpZmllZCwgb3IgMikgcmVkaXJlY3QgdGhlIGNsaWVudCB0byBh
bm90aGVyIHNlcnZlciB0aHJvdWdoIGEgY2hhbmdlIGluIENvbm5lY3Rpb25JRC48L2Rpdj48ZGl2
IGlkPSJibG9vcF9jdXN0b21mb250IiBzdHlsZT0iZm9udC1mYW1pbHk6IGhlbHZldGljYSAsIGFy
aWFsO2ZvbnQtc2l6ZTogMTMuMHB4O2NvbG9yOiA7bWFyZ2luOiAwLjBweDtsaW5lLWhlaWdodDog
YXV0bzsiPjxicj48L2Rpdj4gPGRpdiBpZD0iYmxvb3Bfc2lnbl8xNTcyNjE1MTI0NjEzNDg0MDMy
IiBjbGFzcz0iYmxvb3Bfc2lnbiI+PGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6IGhlbHZldGljYSAs
IGFyaWFsO2ZvbnQtc2l6ZTogMTMuMHB4OyI+PGJyPjwvZGl2PjwvZGl2PiA8YnI+PHAgY2xhc3M9
ImFpcm1haWxfb24iPk9uIDEgTm92ZW1iZXIgMjAxOSBhdCAxNC4yNi4yNCwgUWluZyBBbiAoPGEg
aHJlZj0ibWFpbHRvOmFucWluZy5hcUBhbGliYWJhLWluYy5jb20iIHRhcmdldD0iX2JsYW5rIj5h
bnFpbmcuYXFAYWxpYmFiYS1pbmMuY29tPC9hPikgd3JvdGU6PC9wPiA8YmxvY2txdW90ZSBjbGFz
cz0iY2xlYW5fYnEiPjxzcGFuPjxkaXY+PGRpdj48L2Rpdj48ZGl2PgoKCgoKCjxkaXYgY2xhc3M9
Il9fYWxpeXVuX2VtYWlsX2JvZHlfYmxvY2siPgo8ZGl2IHN0eWxlPSJsaW5lLWhlaWdodDogMS43
O2ZvbnQtZmFtaWx5OiB0YWhvbWEgLCBhcmlhbCAsIHN0aGVpdGkgLCBzaW1zdW47Zm9udC1zaXpl
OiAxNC4wcHg7Y29sb3I6ICMwMDAwMDA7Ij4KPGRpdiBzdHlsZT0iY2xlYXI6IGJvdGg7Ij48YnI+
PC9kaXY+CjxkaXYgc3R5bGU9ImNsZWFyOiBib3RoOyI+SSBiZWxpZXZlIHRoaXMgY2FuIHNhdmUg
MS1SVFQuPC9kaXY+CjxkaXYgc3R5bGU9ImNsZWFyOiBib3RoOyI+PGJyPjwvZGl2Pgo8ZGl2IHN0
eWxlPSJjbGVhcjogYm90aDsiPkFzIGZvciB0aGUgcHJpdmFjeSByaXNrLCBuZXdfdG9rZW4gZnJh
bWUKY2FuIGJlIGRlbGl2ZXJlZCB2aWEgaGFuZHNoYWtlPC9kaXY+CjxkaXYgc3R5bGU9ImNsZWFy
OiBib3RoOyI+PGJyPjwvZGl2Pgo8ZGl2IHN0eWxlPSJjbGVhcjogYm90aDsiPjxicj48L2Rpdj4K
PGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi1yaWdodDogMC4wcHg7bWFyZ2luLXRvcDogMC4wcHg7
bWFyZ2luLWJvdHRvbTogMC4wcHg7Zm9udC1mYW1pbHk6IHRhaG9tYSAsIGFyaWFsICwgc3RoZWl0
aSAsIHNpbXN1bjtmb250LXNpemU6IDE0LjBweDtjb2xvcjogIzAwMDAwMDsiPgo8ZGl2IHN0eWxl
PSJjbGVhcjogYm90aDsiPgotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08L2Rpdj4KPGRpdiBzdHlsZT0iY2xlYXI6IGJvdGg7
Ij5Gcm9tOk1hcnRlbiBTZWVtYW5uCiZsdDs8YSBocmVmPSJtYWlsdG86bWFydGVuc2VlbWFubkBn
bWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj5tYXJ0ZW5zZWVtYW5uQGdtYWlsLmNvbTwvYT4mZ3Q7
PC9kaXY+CjxkaXYgc3R5bGU9ImNsZWFyOiBib3RoOyI+U2VuZCBUaW1lOjIwMTnlubQxMeaciDHm
l6Uo5pif5pyf5LqUKSAyMDo1NDwvZGl2Pgo8ZGl2IHN0eWxlPSJjbGVhcjogYm90aDsiPlRvOuWu
ieWLjSjojrPpgLgpCiZsdDs8YSBocmVmPSJtYWlsdG86YW5xaW5nLmFxQGFsaWJhYmEtaW5jLmNv
bSIgdGFyZ2V0PSJfYmxhbmsiPmFucWluZy5hcUBhbGliYWJhLWluYy5jb208L2E+Jmd0OzwvZGl2
Pgo8ZGl2IHN0eWxlPSJjbGVhcjogYm90aDsiPkNjOlFVSUMgJmx0OzxhIGhyZWY9Im1haWx0bzpx
dWljLWJvdW5jZXNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5xdWljLWJvdW5jZXNAaWV0Zi5v
cmc8L2E+Jmd0OzsKcXVpYyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnF1aWNAaWV0Zi5vcmciIHRhcmdl
dD0iX2JsYW5rIj5xdWljQGlldGYub3JnPC9hPiZndDs7IGpyaS5pZXRmICZsdDs8YSBocmVmPSJt
YWlsdG86anJpLmlldGZAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+anJpLmlldGZAZ21haWwu
Y29tPC9hPiZndDs7IG10CiZsdDs8YSBocmVmPSJtYWlsdG86bXRAbG93ZW50cm9weS5uZXQiIHRh
cmdldD0iX2JsYW5rIj5tdEBsb3dlbnRyb3B5Lm5ldDwvYT4mZ3Q7OyBtaWtrZWxmaiAmbHQ7PGEg
aHJlZj0ibWFpbHRvOm1pa2tlbGZqQGdtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPm1pa2tlbGZq
QGdtYWlsLmNvbTwvYT4mZ3Q7OwrliJjlpKfpuY8o6bmP5oiQKSAmbHQ7PGEgaHJlZj0ibWFpbHRv
Om1heC5sZHBAYWxpYmFiYS1pbmMuY29tIiB0YXJnZXQ9Il9ibGFuayI+bWF4LmxkcEBhbGliYWJh
LWluYy5jb208L2E+Jmd0OzwvZGl2Pgo8ZGl2IHN0eWxlPSJjbGVhcjogYm90aDsiPlN1YmplY3Q6
UmU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0KYWJvdXQ8L2Rpdj4KPGRpdiBzdHlsZT0iY2xl
YXI6IGJvdGg7Ij48YnI+PC9kaXY+CjxkaXY+CjxkaXY+SSBkb24ndCBzZWUgYW55IGVuaGFuY2Vk
IGNsaWVudCBleHBlcmllbmNlLCBzaW5jZSB0aGUKaGFuZHNoYWtlIHRha2VzIGV4YWN0bHkgdGhl
IHNhbWUgbnVtYmVyIG9mIHJvdW5kIHRyaXBzIHdpdGggeW91cgpwcm9wb3NhbCBhcyB3aXRoIHRo
ZSBjdXJyZW50IHZlcnNpb24gb2YgdGhlIFFVSUMgZHJhZnQuPGJyPjwvZGl2Pgo8ZGl2PlNlbmRp
bmcgTkVXX1RPS0VOIGluIEluaXRpYWwgcGFja2V0cyBwcm92aWRlcyBubyBiZW5lZml0IG92ZXIK
c2VuZGluZyBpdCBpbiAxLVJUVCBwYWNrZXRzLCBidXQgY29tZXMgd2l0aCB3b3JzZSBwcml2YWN5
CnByb3BlcnRpZXMsIHNpbmNlIEluaXRpYWwgcGFja2V0cyBhcmUgbm90IGVuY3J5cHRlZCBhbmQg
Y2FuCnRoZXJlZm9yZSBiZSByZWFkIGJ5IG9uLXBhdGggb2JzZXJ2ZXJzLjxicj48L2Rpdj4KPC9k
aXY+Cjxicj4KPGRpdiBjbGFzcz0iZ21haWxfcXVvdGUiPgo8ZGl2IGNsYXNzPSJnbWFpbF9hdHRy
Ij5PbiBGcmksIE5vdiAxLCAyMDE5IGF0IDc6MzcgUE0gUWluZyBBbgombHQ7PGEgaHJlZj0ibWFp
bHRvOmFucWluZy5hcUBhbGliYWJhLWluYy5jb20iIHRhcmdldD0iX2JsYW5rIj5hbnFpbmcuYXFA
YWxpYmFiYS1pbmMuY29tPC9hPiZndDsgd3JvdGU6PGJyPjwvZGl2Pgo8ZGl2IHN0eWxlPSJtYXJn
aW46IDE0LjBweCAwLjBweDsiPgo8ZGl2IHN0eWxlPSJsaW5lLWhlaWdodDogMS43O2ZvbnQtZmFt
aWx5OiB0YWhvbWEgLCBhcmlhbCAsIHN0aGVpdGkgLCBzaW1zdW47Zm9udC1zaXplOiAxNC4wcHg7
Y29sb3I6ICMwMDAwMDA7Ij4KPGRpdiBzdHlsZT0iY2xlYXI6IGJvdGg7Ij48YnI+PC9kaXY+Cjxk
aXYgc3R5bGU9ImNsZWFyOiBib3RoOyI+SWYgc28sCmY8c3Bhbj5vciZuYnNwO3RoZSZuYnNwO2Zp
cnN0PC9zcGFuPiZuYnNwO2Nvbm5lY3Rpb24mbmJzcDtiZXR3ZWVuJm5ic3A7Y2xpZW50Jm5ic3A7
YW5kJm5ic3A7c2VydmVyLApzZXJ2ZXIgY2FuIGNob29zZSB0byBlbGltaW5hdGUmbmJzcDt0aGUm
bmJzcDt1c2UmbmJzcDtvZiZuYnNwO1JldHJ5CnBhY2tldCZuYnNwO2ZvciZuYnNwO3Rva2VuJm5i
c3A7ZGVsaXZlcnksIGFuZApyZWx5Jm5ic3A7b24mbmJzcDtoYW5kc2hha2UmbmJzcDtlbmNyeXB0
aW9uJm5ic3A7bGF5ZXImbmJzcDt0bwpwcm92ZSZuYnNwO3JldHVybiByb3V0YWJpbGl0eS4mbmJz
cDsgSW4mbmJzcDthZGRpdGlvbiwgTmV3X1Rva2VuCmZyYW1lIGlzJm5ic3A7dXNlZCZuYnNwO2J5
CnNlcnZlciwmbmJzcDt2aWEmbmJzcDtpLmUuJm5ic3A7dGhlJm5ic3A7SW5pdGlhbCZuYnNwO3Bh
Y2tldCwmbmJzcDt0byZuYnNwO3Byb3ZpZGUmbmJzcDt0aGUmbmJzcDtjbGllbnQmbmJzcDt3aXRo
Jm5ic3A7YW4KYWRkcmVzcyZuYnNwO3ZhbGlkYXRpb24mbmJzcDt0b2tlbiZuYnNwO3RoYXQmbmJz
cDtjYW4mbmJzcDtiZSZuYnNwO3VzZWQmbmJzcDt0byZuYnNwO3ZhbGlkYXRlJm5ic3A7ZnV0dXJl
PHNwYW4+Jm5ic3A7Y29ubmVjdGlvbnMuPC9zcGFuPjwvZGl2Pgo8ZGl2IHN0eWxlPSJjbGVhcjog
Ym90aDsiPjxzcGFuPjxicj48L3NwYW4+PC9kaXY+CjxkaXYgc3R5bGU9ImNsZWFyOiBib3RoOyI+
PHNwYW4+SXQgY2FuIGVuaGFuY2UgdGhlIGV4cGVyaWVuY2UgaW4KY2xpZW50IHNpZGUgZm9yIHRo
ZSBmaXJzdCBjb25uZWN0aW9uIGVzdGFibGlzaG1lbnQuPC9zcGFuPjwvZGl2Pgo8ZGl2IHN0eWxl
PSJjbGVhcjogYm90aDsiPjxzcGFuPjxicj48L3NwYW4+PC9kaXY+CjxkaXYgc3R5bGU9ImNsZWFy
OiBib3RoOyI+PHNwYW4+SSBzdWJtaXR0ZWQgdGhlIGRyYWZ0LCZuYnNwOzxhIGhyZWY9Imh0dHBz
Oi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWFuLWZhc3QtYWRkcmVzcy12YWxpZGF0
aW9uLyIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2Ry
YWZ0LWFuLWZhc3QtYWRkcmVzcy12YWxpZGF0aW9uLzwvYT48L3NwYW4+PC9kaXY+CjxkaXYgc3R5
bGU9ImNsZWFyOiBib3RoOyI+PHNwYW4+PGJyPjwvc3Bhbj48L2Rpdj4KPGRpdiBzdHlsZT0iY2xl
YXI6IGJvdGg7Ij48c3Bhbj5RaW5nPC9zcGFuPjwvZGl2Pgo8ZGl2IHN0eWxlPSJjbGVhcjogYm90
aDsiPjwvZGl2Pgo8ZGl2IHN0eWxlPSJjbGVhcjogYm90aDsiPjxicj48L2Rpdj4KPGRpdiBzdHls
ZT0iY2xlYXI6IGJvdGg7Ij48YnI+PC9kaXY+CjxkaXYgc3R5bGU9ImNsZWFyOiBib3RoOyI+PGJy
PjwvZGl2Pgo8ZGl2IHN0eWxlPSJjbGVhcjogYm90aDsiPgotLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08L2Rpdj4KPGRpdiBz
dHlsZT0iY2xlYXI6IGJvdGg7Ij5Gcm9tOk1pa2UgQmlzaG9wICZsdDs8YSBocmVmPSJtYWlsdG86
bWJpc2hvcEBldmVxdWVmb3UuYmUiIHRhcmdldD0iX2JsYW5rIj5tYmlzaG9wQGV2ZXF1ZWZvdS5i
ZTwvYT4mZ3Q7PC9kaXY+CjxkaXYgc3R5bGU9ImNsZWFyOiBib3RoOyI+U2VuZCBUaW1lOjIwMTnl
ubQxMeaciDHml6Uo5pif5pyf5LqUKSAwMDowNjwvZGl2Pgo8ZGl2IHN0eWxlPSJjbGVhcjogYm90
aDsiPlRvOuWuieWLjSjojrPpgLgpICZsdDs8YSBocmVmPSJtYWlsdG86YW5xaW5nLmFxQGFsaWJh
YmEtaW5jLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmFucWluZy5hcUBhbGliYWJhLWluYy5jb208L2E+
Jmd0OzsgcXVpYyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnF1aWNAaWV0Zi5vcmciIHRhcmdldD0iX2Js
YW5rIj5xdWljQGlldGYub3JnPC9hPiZndDs7CmpyaS5pZXRmICZsdDs8YSBocmVmPSJtYWlsdG86
anJpLmlldGZAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+anJpLmlldGZAZ21haWwuY29tPC9h
PiZndDs7IG10ICZsdDs8YSBocmVmPSJtYWlsdG86bXRAbG93ZW50cm9weS5uZXQiIHRhcmdldD0i
X2JsYW5rIj5tdEBsb3dlbnRyb3B5Lm5ldDwvYT4mZ3Q7OyBtaWtrZWxmaiAmbHQ7PGEgaHJlZj0i
bWFpbHRvOm1pa2tlbGZqQGdtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPm1pa2tlbGZqQGdtYWls
LmNvbTwvYT4mZ3Q7PC9kaXY+CjxkaXYgc3R5bGU9ImNsZWFyOiBib3RoOyI+U3ViamVjdDpSRTog
RmFzdCBBZGRyZXNzIFZhbGlkYXRpb24gLQphYm91dDwvZGl2Pgo8ZGl2IHN0eWxlPSJjbGVhcjog
Ym90aDsiPjxicj48L2Rpdj4KPGRpdj4KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdp
bjogMC4wcHg7Zm9udC1zaXplOiAxNC43cHg7Zm9udC1mYW1pbHk6IGNhbGlicmkgLCBzYW5zLXNl
cmlmOyI+QXMKTWFydGluIHBvaW50ZWQgb3V0IGluIHRoZSBlLW1haWwgeW91IHJlcGxpZWQgdG8s
IGlmIHRoZSBzZXJ2ZXIgaXMKd2lsbGluZyB0byBtYWludGFpbiBzdGF0ZSwgYW55IHBhY2tldCBh
dCB0aGUgSGFuZHNoYWtlIGVuY3J5cHRpb24KbGF5ZXIgcHJvdmVzIHJldHVybiByb3V0YWJpbGl0
eS4mbmJzcDsgVGhlcmUgc2VlbXMgdG8gYmUgbm8gbmVlZApmb3IgYSBzZXBhcmF0ZSBhZGRyZXNz
IHZhbGlkYXRpb24gbWVjaGFuaXNtIGlmIHRoZSBzZXJ2ZXIgaXMKd2lsbGluZyB0byBwcm9jZWVk
IHdpdGggdGhlIGhhbmRzaGFrZS48L3A+CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJn
aW46IDAuMHB4O2ZvbnQtc2l6ZTogMTQuN3B4O2ZvbnQtZmFtaWx5OiBjYWxpYnJpICwgc2Fucy1z
ZXJpZjsiPgombmJzcDs8L3A+CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46IDAu
MHB4O2ZvbnQtc2l6ZTogMTQuN3B4O2ZvbnQtZmFtaWx5OiBjYWxpYnJpICwgc2Fucy1zZXJpZjsi
Pgo8Yj5Gcm9tOjwvYj4gUVVJQyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnF1aWMtYm91bmNlc0BpZXRm
Lm9yZyIgdGFyZ2V0PSJfYmxhbmsiPnF1aWMtYm91bmNlc0BpZXRmLm9yZzwvYT4mZ3Q7IDxiPk9u
IEJlaGFsZiBPZjwvYj4KUWluZyBBbjxicj4KPGI+U2VudDo8L2I+IFRodXJzZGF5LCBPY3RvYmVy
IDMxLCAyMDE5IDg6NTYgQU08YnI+CjxiPlRvOjwvYj4gcXVpYyAmbHQ7PGEgaHJlZj0ibWFpbHRv
OnF1aWNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5xdWljQGlldGYub3JnPC9hPiZndDs7IGpy
aS5pZXRmICZsdDs8YSBocmVmPSJtYWlsdG86anJpLmlldGZAZ21haWwuY29tIiB0YXJnZXQ9Il9i
bGFuayI+anJpLmlldGZAZ21haWwuY29tPC9hPiZndDs7IG10ICZsdDs8YSBocmVmPSJtYWlsdG86
bXRAbG93ZW50cm9weS5uZXQiIHRhcmdldD0iX2JsYW5rIj5tdEBsb3dlbnRyb3B5Lm5ldDwvYT4m
Z3Q7OyBtaWtrZWxmaiAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1pa2tlbGZqQGdtYWlsLmNvbSIgdGFy
Z2V0PSJfYmxhbmsiPm1pa2tlbGZqQGdtYWlsLmNvbTwvYT4mZ3Q7PGJyPgo8Yj5TdWJqZWN0Ojwv
Yj4gUmU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQ8L3A+CjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtYXJnaW46IDAuMHB4O2ZvbnQtc2l6ZTogMTQuN3B4O2ZvbnQtZmFtaWx5
OiBjYWxpYnJpICwgc2Fucy1zZXJpZjsiPgombmJzcDs8L3A+CjxkaXY+CjxkaXY+CjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46IDAuMHB4O2ZvbnQtc2l6ZTogMTQuN3B4O2ZvbnQt
ZmFtaWx5OiBjYWxpYnJpICwgc2Fucy1zZXJpZjsiPgo8c3BhbiBzdHlsZT0iZm9udC1zaXplOiAx
NC4wcHg7Zm9udC1mYW1pbHk6IHRhaG9tYSAsIHNhbnMtc2VyaWY7Y29sb3I6IGJsYWNrOyI+Jm5i
c3A7PC9zcGFuPjwvcD4KPC9kaXY+CjxkaXY+CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
YXJnaW46IDAuMHB4O2ZvbnQtc2l6ZTogMTQuN3B4O2ZvbnQtZmFtaWx5OiBjYWxpYnJpICwgc2Fu
cy1zZXJpZjsiPgo8c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxNC4wcHg7Zm9udC1mYW1pbHk6IHRh
aG9tYSAsIHNhbnMtc2VyaWY7Y29sb3I6IGJsYWNrOyI+Jm5ic3A7PC9zcGFuPjwvcD4KPC9kaXY+
CjxkaXY+CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46IDAuMHB4O2ZvbnQtc2l6
ZTogMTQuN3B4O2ZvbnQtZmFtaWx5OiBjYWxpYnJpICwgc2Fucy1zZXJpZjsiPgo8c3BhbiBzdHls
ZT0iZm9udC1zaXplOiAxNC4wcHg7Zm9udC1mYW1pbHk6IHRhaG9tYSAsIHNhbnMtc2VyaWY7Y29s
b3I6IGJsYWNrOyI+VG8KY2xhcmlmeSwgdGhlIHByb3Bvc2FsIGlzIG5vdCB0byByZXBsYWNlIHRo
ZSBleGlzdGluZyBSZXRyeS1iYXNlZAp2YWxpZGF0aW9uLCBidXQgdG8gcHJvdmlkZSBhbm90aGVy
IG9wdGlvbiBmb3Igc2VydmVyIHRvIGRvIHRoZQpjbGllbnQgdmFsaWRhdGlvbi48L3NwYW4+PC9w
Pgo8L2Rpdj4KPGRpdj4KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjogMC4wcHg7
Zm9udC1zaXplOiAxNC43cHg7Zm9udC1mYW1pbHk6IGNhbGlicmkgLCBzYW5zLXNlcmlmOyI+Cjxz
cGFuIHN0eWxlPSJmb250LXNpemU6IDE0LjBweDtmb250LWZhbWlseTogdGFob21hICwgc2Fucy1z
ZXJpZjtjb2xvcjogYmxhY2s7Ij4mbmJzcDs8L3NwYW4+PC9wPgo8L2Rpdj4KPGRpdj4KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjogMC4wcHg7Zm9udC1zaXplOiAxNC43cHg7Zm9u
dC1mYW1pbHk6IGNhbGlicmkgLCBzYW5zLXNlcmlmOyI+CjxzcGFuIHN0eWxlPSJmb250LXNpemU6
IDE0LjBweDtmb250LWZhbWlseTogdGFob21hICwgc2Fucy1zZXJpZjtjb2xvcjogYmxhY2s7Ij5J
CnVuZGVyc3RhbmQgdGhhdCBpbiBzZXJ2ZXIgc2lkZSwgZTxzcGFuIHN0eWxlPSJiYWNrZ3JvdW5k
OiBub25lIDAuMCUgMC4wJSByZXBlYXQgc2Nyb2xsIHdoaXRlOyI+eGNoYW5naW5nJm5ic3A7dGhl
Jm5ic3A7dG9rZW4mbmJzcDthdCZuYnNwO3RoZSZuYnNwO0hhbmRzaGFrZSZuYnNwO2VuY3J5cHRp
b24mbmJzcDtsZXZlbAp3aWxsIG1ha2UgdGhlIHNlcnZlciBzdGFydCB0byBtYWludGFpbiBoYW5k
c2hha2Ugc3RhdGVzLiBCdXQgaW4KY2xpZW50IHNpZGUsIGl0IGNhbiBhY2NlbGVyYXRlIHRoZSBj
b25uZWN0aW9uIGVzdGFibGlzaG1lbnQgZnJvbQpjbGllbnQgdG8gc2VydmVyLjwvc3Bhbj48L3Nw
YW4+PC9wPgo8L2Rpdj4KPGRpdj4KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjog
MC4wcHg7Zm9udC1zaXplOiAxNC43cHg7Zm9udC1mYW1pbHk6IGNhbGlicmkgLCBzYW5zLXNlcmlm
OyI+CjxzcGFuIHN0eWxlPSJmb250LXNpemU6IDE0LjBweDtmb250LWZhbWlseTogdGFob21hICwg
c2Fucy1zZXJpZjtjb2xvcjogYmxhY2s7Ij4mbmJzcDs8L3NwYW4+PC9wPgo8L2Rpdj4KPGRpdj4K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjogMC4wcHg7Zm9udC1zaXplOiAxNC43
cHg7Zm9udC1mYW1pbHk6IGNhbGlicmkgLCBzYW5zLXNlcmlmOyI+CjxzcGFuIHN0eWxlPSJmb250
LXNpemU6IDE0LjBweDtmb250LWZhbWlseTogdGFob21hICwgc2Fucy1zZXJpZjtjb2xvcjogYmxh
Y2s7YmFja2dyb3VuZDogbm9uZSAwLjAlIDAuMCUgcmVwZWF0IHNjcm9sbCB3aGl0ZTsiPgpBbmQg
aXQgaXMgdGhlIHNlcnZlcidzIGRlY2lzaW9uIHdoZXRoZXIgdG8gZXhjaGFuZ2UgdG9rZW4gaW4g
UmV0cnkKb3IgaW4gSGFuZHNoYWtlLiBJZiBzZXJ2ZXIgY2hvb3NlcyB0byBhY2NlcHQgdGhlIGNv
c3QgYnJvdWdodCBieQp0b2tlbiBleGNoYW5naW5nIGluIEhhbmRzaGFrZSwgaXQgd2lsbCBicmlu
ZyBtb3JlIGVuaGFuY2VkCmV4cGVyaWVuY2UgaW4gY2xpZW50IHNpZGUuPC9zcGFuPjwvcD4KPC9k
aXY+CjxkaXY+CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46IDAuMHB4O2ZvbnQt
c2l6ZTogMTQuN3B4O2ZvbnQtZmFtaWx5OiBjYWxpYnJpICwgc2Fucy1zZXJpZjsiPgo8c3BhbiBz
dHlsZT0iZm9udC1zaXplOiAxNC4wcHg7Zm9udC1mYW1pbHk6IHRhaG9tYSAsIHNhbnMtc2VyaWY7
Y29sb3I6IGJsYWNrOyI+Jm5ic3A7PC9zcGFuPjwvcD4KPC9kaXY+CjxkaXY+CjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46IDAuMHB4O2ZvbnQtc2l6ZTogMTQuN3B4O2ZvbnQtZmFt
aWx5OiBjYWxpYnJpICwgc2Fucy1zZXJpZjsiPgo8c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxNC4w
cHg7Zm9udC1mYW1pbHk6IHRhaG9tYSAsIHNhbnMtc2VyaWY7Y29sb3I6IGJsYWNrOyI+Jm5ic3A7
PC9zcGFuPjwvcD4KPC9kaXY+CjxkaXY+CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJn
aW46IDAuMHB4O2ZvbnQtc2l6ZTogMTQuN3B4O2ZvbnQtZmFtaWx5OiBjYWxpYnJpICwgc2Fucy1z
ZXJpZjsiPgo8c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxNC4wcHg7Zm9udC1mYW1pbHk6IHRhaG9t
YSAsIHNhbnMtc2VyaWY7Y29sb3I6IGJsYWNrO2JhY2tncm91bmQ6IG5vbmUgMC4wJSAwLjAlIHJl
cGVhdCBzY3JvbGwgd2hpdGU7Ij4KQlIsPC9zcGFuPjwvcD4KPC9kaXY+CjxkaXY+CjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46IDAuMHB4O2ZvbnQtc2l6ZTogMTQuN3B4O2ZvbnQt
ZmFtaWx5OiBjYWxpYnJpICwgc2Fucy1zZXJpZjsiPgo8c3BhbiBzdHlsZT0iZm9udC1zaXplOiAx
NC4wcHg7Zm9udC1mYW1pbHk6IHRhaG9tYSAsIHNhbnMtc2VyaWY7Y29sb3I6IGJsYWNrO2JhY2tn
cm91bmQ6IG5vbmUgMC4wJSAwLjAlIHJlcGVhdCBzY3JvbGwgd2hpdGU7Ij4KUWluZzwvc3Bhbj48
L3A+CjwvZGl2Pgo8ZGl2Pgo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOiAwLjBw
eDtmb250LXNpemU6IDE0LjdweDtmb250LWZhbWlseTogY2FsaWJyaSAsIHNhbnMtc2VyaWY7Ij4K
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTQuMHB4O2ZvbnQtZmFtaWx5OiB0YWhvbWEgLCBzYW5z
LXNlcmlmO2NvbG9yOiBibGFjazsiPiZuYnNwOzwvc3Bhbj48L3A+CjwvZGl2Pgo8ZGl2Pgo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOiAwLjBweDtmb250LXNpemU6IDE0LjdweDtm
b250LWZhbWlseTogY2FsaWJyaSAsIHNhbnMtc2VyaWY7Ij4KPHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZTogMTQuMHB4O2ZvbnQtZmFtaWx5OiB0YWhvbWEgLCBzYW5zLXNlcmlmO2NvbG9yOiBibGFjazsi
PiZuYnNwOzwvc3Bhbj48L3A+CjwvZGl2Pgo8ZGl2IHN0eWxlPSJtYXJnaW46IDE0LjBweCAwLjBw
eDsiPgo8ZGl2Pgo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOiAwLjBweDtmb250
LXNpemU6IDE0LjdweDtmb250LWZhbWlseTogY2FsaWJyaSAsIHNhbnMtc2VyaWY7Ij4KPHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZTogMTQuMHB4O2ZvbnQtZmFtaWx5OiB0YWhvbWEgLCBzYW5zLXNlcmlm
O2NvbG9yOiBibGFjazsiPi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTwvc3Bhbj48L3A+CjwvZGl2Pgo8ZGl2Pgo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOiAwLjBweDtmb250LXNpemU6IDE0LjdweDtmb250
LWZhbWlseTogY2FsaWJyaSAsIHNhbnMtc2VyaWY7Ij4KPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTog
MTQuMHB4O2ZvbnQtZmFtaWx5OiB0YWhvbWEgLCBzYW5zLXNlcmlmO2NvbG9yOiBibGFjazsiPkZy
b206TWFydGluClRob21zb24gJmx0OzxhIGhyZWY9Im1haWx0bzptdEBsb3dlbnRyb3B5Lm5ldCIg
dGFyZ2V0PSJfYmxhbmsiIHN0eWxlPSJjb2xvcjogIzAwMDBmZjt0ZXh0LWRlY29yYXRpb246IHVu
ZGVybGluZSAjMDAwMGZmOyI+bXRAbG93ZW50cm9weS5uZXQ8L2E+Jmd0Ozwvc3Bhbj48L3A+Cjwv
ZGl2Pgo8ZGl2Pgo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOiAwLjBweDtmb250
LXNpemU6IDE0LjdweDtmb250LWZhbWlseTogY2FsaWJyaSAsIHNhbnMtc2VyaWY7Ij4KPHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZTogMTQuMHB4O2ZvbnQtZmFtaWx5OiB0YWhvbWEgLCBzYW5zLXNlcmlm
O2NvbG9yOiBibGFjazsiPlNlbmQKVGltZToyMDE5PC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNp
emU6IDE0LjBweDtmb250LWZhbWlseTogbXMgZ290aGljO2NvbG9yOiBibGFjazsiPuW5tDwvc3Bh
bj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxNC4wcHg7Zm9udC1mYW1pbHk6IHRhaG9tYSAsIHNh
bnMtc2VyaWY7Y29sb3I6IGJsYWNrOyI+MTA8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTog
MTQuMHB4O2ZvbnQtZmFtaWx5OiBtcyBnb3RoaWM7Y29sb3I6IGJsYWNrOyI+5pyIPC9zcGFuPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6IDE0LjBweDtmb250LWZhbWlseTogdGFob21hICwgc2Fucy1z
ZXJpZjtjb2xvcjogYmxhY2s7Ij4zMTwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxNC4w
cHg7Zm9udC1mYW1pbHk6IG1zIGdvdGhpYztjb2xvcjogYmxhY2s7Ij7ml6U8L3NwYW4+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZTogMTQuMHB4O2ZvbnQtZmFtaWx5OiB0YWhvbWEgLCBzYW5zLXNlcmlm
O2NvbG9yOiBibGFjazsiPig8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTQuMHB4O2Zv
bnQtZmFtaWx5OiBtcyBnb3RoaWM7Y29sb3I6IGJsYWNrOyI+5pif5pyf5ZubPC9zcGFuPjxzcGFu
IHN0eWxlPSJmb250LXNpemU6IDE0LjBweDtmb250LWZhbWlseTogdGFob21hICwgc2Fucy1zZXJp
Zjtjb2xvcjogYmxhY2s7Ij4pCjA2OjA3PC9zcGFuPjwvcD4KPC9kaXY+CjxkaXY+CjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46IDAuMHB4O2ZvbnQtc2l6ZTogMTQuN3B4O2ZvbnQt
ZmFtaWx5OiBjYWxpYnJpICwgc2Fucy1zZXJpZjsiPgo8c3BhbiBzdHlsZT0iZm9udC1zaXplOiAx
NC4wcHg7Zm9udC1mYW1pbHk6IHRhaG9tYSAsIHNhbnMtc2VyaWY7Y29sb3I6IGJsYWNrOyI+VG86
cXVpYwombHQ7PGEgaHJlZj0ibWFpbHRvOnF1aWNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIiBz
dHlsZT0iY29sb3I6ICMwMDAwZmY7dGV4dC1kZWNvcmF0aW9uOiB1bmRlcmxpbmUgIzAwMDBmZjsi
PnF1aWNAaWV0Zi5vcmc8L2E+Jmd0Ozwvc3Bhbj48L3A+CjwvZGl2Pgo8ZGl2Pgo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOiAwLjBweDtmb250LXNpemU6IDE0LjdweDtmb250LWZh
bWlseTogY2FsaWJyaSAsIHNhbnMtc2VyaWY7Ij4KPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTQu
MHB4O2ZvbnQtZmFtaWx5OiB0YWhvbWEgLCBzYW5zLXNlcmlmO2NvbG9yOiBibGFjazsiPlN1Ympl
Y3Q6UmU6CkZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQ8L3NwYW4+PC9wPgo8L2Rpdj4K
PGRpdj4KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjogMC4wcHg7Zm9udC1zaXpl
OiAxNC43cHg7Zm9udC1mYW1pbHk6IGNhbGlicmkgLCBzYW5zLXNlcmlmOyI+CjxzcGFuIHN0eWxl
PSJmb250LXNpemU6IDE0LjBweDtmb250LWZhbWlseTogdGFob21hICwgc2Fucy1zZXJpZjtjb2xv
cjogYmxhY2s7Ij4mbmJzcDs8L3NwYW4+PC9wPgo8L2Rpdj4KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1hcmdpbjogMC4wcHg7Zm9udC1zaXplOiAxNC43cHg7Zm9udC1mYW1pbHk6IGNhbGli
cmkgLCBzYW5zLXNlcmlmOyI+CjxzcGFuIHN0eWxlPSJmb250LXNpemU6IDE0LjBweDtmb250LWZh
bWlseTogdGFob21hICwgc2Fucy1zZXJpZjtjb2xvcjogYmxhY2s7Ij5BbHNvJm5ic3A7bm90ZSZu
YnNwO3RoYXQmbmJzcDtleGNoYW5nZSZuYnNwO29mJm5ic3A7SGFuZHNoYWtlJm5ic3A7cGFja2V0
cyZuYnNwO3Byb3ZpZGVzJm5ic3A7cHJvb2YmbmJzcDtvZiZuYnNwO3JldHVybiZuYnNwO3JvdXRl
YWJpbGl0eSZuYnNwO3ZpYSZuYnNwO3RoZSZuYnNwO3VzZSZuYnNwO29mJm5ic3A7dGhlJm5ic3A7
ZW5jcnlwdGlvbiZuYnNwO2tleXMsJm5ic3A7c28mbmJzcDt0aGVyZSZuYnNwO2lzJm5ic3A7bm8m
bmJzcDtuZWVkJm5ic3A7dG8mbmJzcDtleGNoYW5nZSZuYnNwO3Rva2VucyZuYnNwO2F0Jm5ic3A7
dGhhdCZuYnNwO2xldmVsLjxicj4KCjxicj4KT24mbmJzcDtUaHUsJm5ic3A7T2N0Jm5ic3A7MzEs
Jm5ic3A7MjAxOSwmbmJzcDthdCZuYnNwOzAzOjI5LCZuYnNwO01pa2UmbmJzcDtCaXNob3AmbmJz
cDt3cm90ZTo8YnI+CgomZ3Q7Jm5ic3A7Jm5ic3A7PGJyPgomZ3Q7Jm5ic3A7VGhlJm5ic3A7YWR2
YW50YWdlJm5ic3A7b2YmbmJzcDt1c2luZyZuYnNwO1JldHJ5LCZuYnNwO2hvd2V2ZXIsJm5ic3A7
aXMmbmJzcDt0aGF0Jm5ic3A7dGhlJm5ic3A7c2VydmVyJm5ic3A7aXMmbmJzcDthYmxlJm5ic3A7
dG8mbmJzcDs8YnI+CgomZ3Q7Jm5ic3A7a2VlcCZuYnNwO21pbmltYWwmbmJzcDsoaWYmbmJzcDth
bnkpJm5ic3A7c3RhdGUmbmJzcDthYm91dCZuYnNwO3RoZSZuYnNwO2NsaWVudC4mbmJzcDtFeGNo
YW5naW5nJm5ic3A7dGhlJm5ic3A7dG9rZW4mbmJzcDthdCZuYnNwOzxicj4KCiZndDsmbmJzcDt0
aGUmbmJzcDtIYW5kc2hha2UmbmJzcDtlbmNyeXB0aW9uJm5ic3A7bGV2ZWwmbmJzcDttZWFucyZu
YnNwO3RoZSZuYnNwO3NlcnZlciZuYnNwO2lzJm5ic3A7YWxyZWFkeSZuYnNwO2RvaW5nJm5ic3A7
d29yayZuYnNwOzxicj4KCiZndDsmbmJzcDthbmQmbmJzcDttYWludGFpbmluZyZuYnNwO3N0YXRl
Jm5ic3A7aW4mbmJzcDtvcmRlciZuYnNwO3RvJm5ic3A7cHJvY2VzcyZuYnNwO3RoZSZuYnNwO2hh
bmRzaGFrZSwmbmJzcDt3aGljaCZuYnNwO2lzJm5ic3A7PGJyPgoKJmd0OyZuYnNwO2V4YWN0bHkm
bmJzcDt3aGF0Jm5ic3A7dGhlJm5ic3A7c2VydmVyJm5ic3A7aXMmbmJzcDt0cnlpbmcmbmJzcDt0
byZuYnNwO2F2b2lkLjxicj4KCiZndDsmbmJzcDs8YnI+CiZndDsmbmJzcDs8YnI+CiZndDsmbmJz
cDsqRnJvbToqJm5ic3A7UVVJQyZuYnNwOyZsdDs8YSBocmVmPSJtYWlsdG86cXVpYy1ib3VuY2Vz
QGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayIgc3R5bGU9ImNvbG9yOiAjMDAwMGZmO3RleHQtZGVj
b3JhdGlvbjogdW5kZXJsaW5lICMwMDAwZmY7Ij5xdWljLWJvdW5jZXNAaWV0Zi5vcmc8L2E+Jmd0
OyZuYnNwOypPbiZuYnNwO0JlaGFsZiZuYnNwO09mJm5ic3A7KiZuYnNwO1FpbmcmbmJzcDtBbjxi
cj4KCiZndDsmbmJzcDsqU2VudDoqJm5ic3A7V2VkbmVzZGF5LCZuYnNwO09jdG9iZXImbmJzcDsz
MCwmbmJzcDsyMDE5Jm5ic3A7OTo0MSZuYnNwO0FNPGJyPgoKJmd0OyZuYnNwOypUbzoqJm5ic3A7
cXVpYyZuYnNwOyZsdDs8YSBocmVmPSJtYWlsdG86cXVpY0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxh
bmsiIHN0eWxlPSJjb2xvcjogIzAwMDBmZjt0ZXh0LWRlY29yYXRpb246IHVuZGVybGluZSAjMDAw
MGZmOyI+cXVpY0BpZXRmLm9yZzwvYT4mZ3Q7OyZuYnNwO2pyaS5pZXRmJm5ic3A7Jmx0OzxhIGhy
ZWY9Im1haWx0bzpqcmkuaWV0ZkBnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIiBzdHlsZT0iY29s
b3I6ICMwMDAwZmY7dGV4dC1kZWNvcmF0aW9uOiB1bmRlcmxpbmUgIzAwMDBmZjsiPmpyaS5pZXRm
QGdtYWlsLmNvbTwvYT4mZ3Q7OyZuYnNwO210Jm5ic3A7PGJyPgoKJmd0OyZuYnNwOyZsdDs8YSBo
cmVmPSJtYWlsdG86bXRAbG93ZW50cm9weS5uZXQiIHRhcmdldD0iX2JsYW5rIiBzdHlsZT0iY29s
b3I6ICMwMDAwZmY7dGV4dC1kZWNvcmF0aW9uOiB1bmRlcmxpbmUgIzAwMDBmZjsiPm10QGxvd2Vu
dHJvcHkubmV0PC9hPiZndDs8YnI+CgomZ3Q7Jm5ic3A7KkNjOiombmJzcDs8L3NwYW4+PHNwYW4g
c3R5bGU9ImZvbnQtc2l6ZTogMTQuMHB4O2ZvbnQtZmFtaWx5OiBtcyBnb3RoaWM7Y29sb3I6IGJs
YWNrOyI+5YiY5aSnPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6IDE0LjBweDtmb250LWZh
bWlseTogbWljcm9zb2Z0IGpoZW5naGVpICwgc2Fucy1zZXJpZjtjb2xvcjogYmxhY2s7Ij7puY88
L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTQuMHB4O2ZvbnQtZmFtaWx5OiB0YWhvbWEg
LCBzYW5zLXNlcmlmO2NvbG9yOiBibGFjazsiPig8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZTogMTQuMHB4O2ZvbnQtZmFtaWx5OiBtaWNyb3NvZnQgamhlbmdoZWkgLCBzYW5zLXNlcmlmO2Nv
bG9yOiBibGFjazsiPum5j+aIkDwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxNC4wcHg7
Zm9udC1mYW1pbHk6IHRhaG9tYSAsIHNhbnMtc2VyaWY7Y29sb3I6IGJsYWNrOyI+KSZuYnNwOyZs
dDs8YSBocmVmPSJtYWlsdG86bWF4LmxkcEBhbGliYWJhLWluYy5jb20iIHRhcmdldD0iX2JsYW5r
IiBzdHlsZT0iY29sb3I6ICMwMDAwZmY7dGV4dC1kZWNvcmF0aW9uOiB1bmRlcmxpbmUgIzAwMDBm
ZjsiPm1heC5sZHBAYWxpYmFiYS1pbmMuY29tPC9hPiZndDs8YnI+CgomZ3Q7Jm5ic3A7KlN1Ympl
Y3Q6KiZuYnNwO0Zhc3QmbmJzcDtBZGRyZXNzJm5ic3A7VmFsaWRhdGlvbiZuYnNwOy0mbmJzcDth
Ym91dDxicj4KCiZndDsmbmJzcDs8YnI+CiZndDsmbmJzcDs8YnI+CiZndDsmbmJzcDs8YnI+CiZn
dDsmbmJzcDs8YnI+CiZndDsmbmJzcDtIaSZuYnNwO01hcnRpbiwmbmJzcDtKYW5hLCZuYnNwOzxi
cj4KJmd0OyZuYnNwOzxicj4KJmd0OyZuYnNwO0kmbmJzcDtyZWFkJm5ic3A7dGhyb3VnaCZuYnNw
OzxhIGhyZWY9Imh0dHBzOi8vd3d3LmlldGYub3JnL2lkL2RyYWZ0LWlldGYtcXVpYy10cmFuc3Bv
cnQtMjMudHh0IiB0YXJnZXQ9Il9ibGFuayIgc3R5bGU9ImNvbG9yOiAjMDAwMGZmO3RleHQtZGVj
b3JhdGlvbjogdW5kZXJsaW5lICMwMDAwZmY7Ij5odHRwczovL3d3dy5pZXRmLm9yZy9pZC9kcmFm
dC1pZXRmLXF1aWMtdHJhbnNwb3J0LTIzLnR4dDwvYT4mbmJzcDs8YnI+CgomZ3Q7Jm5ic3A7YW5k
Jm5ic3A7aGF2ZSZuYnNwO2EmbmJzcDtmZXcmbmJzcDtjb21tZW50cyZuYnNwO2FuZCZuYnNwO2lk
ZWFzJm5ic3A7dG8mbmJzcDtkaXNjdXNzLjxicj4KCiZndDsmbmJzcDs8YnI+CiZndDsmbmJzcDs8
YnI+CiZndDsmbmJzcDtbUVVJQy1UcmFuc10mbmJzcDtkZWZpbmVzJm5ic3A7YSZuYnNwO3Rva2Vu
Jm5ic3A7YmFzZWQmbmJzcDtzY2hlbWUmbmJzcDt0byZuYnNwO2ZhY2lsaXRhdGUmbmJzcDthZGRy
ZXNzJm5ic3A7PGJyPgoKJmd0OyZuYnNwO3ZhbGlkYXRpb24mbmJzcDtvZiZuYnNwO2EmbmJzcDtj
bGllbnQuJm5ic3A7VGhlJm5ic3A7dG9rZW4mbmJzcDtNVVNUJm5ic3A7YmUmbmJzcDtjb3ZlcmVk
Jm5ic3A7YnkmbmJzcDtpbnRlZ3JpdHkmbmJzcDs8YnI+CgomZ3Q7Jm5ic3A7cHJvdGVjdGlvbiZu
YnNwO2FnYWluc3QmbmJzcDttb2RpZmljYXRpb24mbmJzcDtvciZuYnNwO2ZhbHNpZmljYXRpb24m
bmJzcDtieSZuYnNwO2NsaWVudHMuJm5ic3A7VGhlJm5ic3A7c2VydmVyJm5ic3A7PGJyPgoKJmd0
OyZuYnNwO3JlbWVtYmVycyZuYnNwO3RoZSZuYnNwO3ZhbHVlJm5ic3A7aXQmbmJzcDtzZW5kcyZu
YnNwO3RvJm5ic3A7Y2xpZW50cyZuYnNwO2FuZCZuYnNwO3ZhbGlkYXRlcyZuYnNwO3RoZSZuYnNw
O3Rva2VuJm5ic3A7c2VudCZuYnNwOzxicj4KCiZndDsmbmJzcDtiYWNrJm5ic3A7ZnJvbSZuYnNw
O2EmbmJzcDtjbGllbnQuJm5ic3A7SW4mbmJzcDtpdHMmbmJzcDtkZXNpZ24sJm5ic3A7UmV0cnkm
bmJzcDtwYWNrZXQmbmJzcDtpcyZuYnNwO3VzZWQmbmJzcDt0byZuYnNwO2RlbGl2ZXImbmJzcDt0
aGUmbmJzcDs8YnI+CgomZ3Q7Jm5ic3A7dG9rZW4mbmJzcDt0byZuYnNwO2EmbmJzcDtjbGllbnQm
bmJzcDt3aGljaCZuYnNwO2FkZHJlc3MmbmJzcDtoYXMmbmJzcDtub3QmbmJzcDt5ZXQmbmJzcDti
ZWVuJm5ic3A7dmFsaWRhdGVkLiZuYnNwO0l0Jm5ic3A7dm9pZHMmbmJzcDs8YnI+CgomZ3Q7Jm5i
c3A7dGhlJm5ic3A7Zmlyc3QmbmJzcDt0cmFuc21pc3Npb24mbmJzcDtvZiZuYnNwO3RoZSZuYnNw
O0luaXRpYWwmbmJzcDtwYWNrZXQmbmJzcDtzZW50Jm5ic3A7YnkmbmJzcDt0aGUmbmJzcDtjbGll
bnQsJm5ic3A7YW5kJm5ic3A7PGJyPgoKJmd0OyZuYnNwO3RyaWdnZXJzJm5ic3A7YSZuYnNwO3Nl
Y29uZCZuYnNwO0luaXRpYWwmbmJzcDtwYWNrZXQmbmJzcDt0byZuYnNwO2JlJm5ic3A7c2VudCZu
YnNwO3dpdGgmbmJzcDt0aGUmbmJzcDt0b2tlbi4mbmJzcDtUaGUmbmJzcDs8YnI+CgomZ3Q7Jm5i
c3A7ZXhjaGFuZ2UmbmJzcDtvZiZuYnNwO3Rva2VuJm5ic3A7d2lsbCZuYnNwO2NhdXNlJm5ic3A7
bG9uZ2VyJm5ic3A7Y29ubmVjdGlvbiZuYnNwO2VzdGFibGlzaG1lbnQmbmJzcDtkZWxheSZuYnNw
O2ZvciZuYnNwOzxicj4KCiZndDsmbmJzcDthJm5ic3A7Y2xpZW50Ljxicj4KJmd0OyZuYnNwOzxi
cj4KJmd0OyZuYnNwOzxicj4KJmd0OyZuYnNwO1RvJm5ic3A7aW1wcm92ZSZuYnNwO3RoZSZuYnNw
O2VmZmljaWVuY3kmbmJzcDtvZiZuYnNwO2FkZHJlc3MmbmJzcDt2YWxpZGF0aW9uJm5ic3A7ZHVy
aW5nJm5ic3A7aGFuZHNoYWtlLCZuYnNwO29uZSZuYnNwOzxicj4KCiZndDsmbmJzcDtpZGVhJm5i
c3A7aXMmbmJzcDt0aGF0Jm5ic3A7dGhlJm5ic3A7c2FtZSZuYnNwO3Rva2VuJm5ic3A7Y2FuJm5i
c3A7YmUmbmJzcDtleGNoYW5nZWQmbmJzcDt2aWEmbmJzcDthJm5ic3A7ZGlmZmVyZW50Jm5ic3A7
Y29udGFpbmVyJm5ic3A7PGJyPgoKJmd0OyZuYnNwO2kuZS4mbmJzcDt0aGUmbmJzcDtIYW5kc2hh
a2UmbmJzcDtwYWNrZXQsJm5ic3A7dGhhdCZuYnNwO2VsaW1pbmF0ZXMmbmJzcDt0aGUmbmJzcDt1
c2UmbmJzcDtvZiZuYnNwO1JldHJ5Jm5ic3A7cGFja2V0Jm5ic3A7Zm9yJm5ic3A7PGJyPgoKJmd0
OyZuYnNwO3Rva2VuJm5ic3A7ZGVsaXZlcnkuJm5ic3A7PGJyPgomZ3Q7Jm5ic3A7PGJyPgomZ3Q7
Jm5ic3A7PGJyPgomZ3Q7Jm5ic3A7SSZuYnNwO2FtJm5ic3A7d29ya2luZyZuYnNwO29uJm5ic3A7
dGhlJm5ic3A7Y29tcGxldGUmbmJzcDtkcmFmdCZuYnNwO2FuZCZuYnNwO3dpbGwmbmJzcDtzdWJt
aXQmbmJzcDtpdCZuYnNwO2J5Jm5ic3A7RnJpZGF5LiZuYnNwO0JlZm9yZSZuYnNwOzxicj4KCiZn
dDsmbmJzcDt0aGF0LCZuYnNwO2hvcGUmbmJzcDt0aGlzJm5ic3A7Y2FuJm5ic3A7YmUmbmJzcDtk
aXNjdXNzZWQmbmJzcDtpbiZuYnNwO2VtYWlsJm5ic3A7Zmlyc3QuPGJyPgoKJmd0OyZuYnNwOzxi
cj4KJmd0OyZuYnNwOzxicj4KJmd0OyZuYnNwO0JSLDxicj4KJmd0OyZuYnNwOzxicj4KJmd0OyZu
YnNwO1FpbmcmbmJzcDtBbjxicj4KJmd0Ozwvc3Bhbj48L3A+CjwvZGl2Pgo8ZGl2Pgo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOiAwLjBweDtmb250LXNpemU6IDE0LjdweDtmb250
LWZhbWlseTogY2FsaWJyaSAsIHNhbnMtc2VyaWY7bGluZS1oZWlnaHQ6IDIwLjBweDsiPgo8c3Bh
biBzdHlsZT0iZm9udC1zaXplOiAxNC4wcHg7Zm9udC1mYW1pbHk6IHRhaG9tYSAsIHNhbnMtc2Vy
aWY7Y29sb3I6IGJsYWNrOyI+Jm5ic3A7PC9zcGFuPjwvcD4KPC9kaXY+CjwvZGl2Pgo8L2Rpdj4K
PGRpdiBzdHlsZT0ibGluZS1oZWlnaHQ6IDIwLjBweDtjbGVhcjogYm90aDsiPjxicj48L2Rpdj4K
PC9kaXY+CjwvZGl2Pgo8L2Rpdj4KPC9ibG9ja3F1b3RlPgo8ZGl2IHN0eWxlPSJsaW5lLWhlaWdo
dDogMjAuMHB4O2NsZWFyOiBib3RoOyI+PGJyPjwvZGl2Pgo8L2Rpdj4KPC9kaXY+CgoKPC9kaXY+
PC9kaXY+PC9zcGFuPjwvYmxvY2txdW90ZT4KPC9ibG9ja3F1b3RlPjwvZGl2PjwvYmxvY2txdW90
ZT48L2Rpdj4=
------=ALIBOUNDARY_46354_4ec69940_5dbc4747_3544bd--



From nobody Fri Nov  1 08:19:33 2019
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 7B5531208A6; Fri,  1 Nov 2019 08:19:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.986
X-Spam-Level: 
X-Spam-Status: No, score=-1.986 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_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 IoME9Fh7ZM-U; Fri,  1 Nov 2019 08:19:29 -0700 (PDT)
Received: from mail-ed1-x544.google.com (mail-ed1-x544.google.com [IPv6:2a00:1450:4864:20::544]) (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 B37F4120154; Fri,  1 Nov 2019 08:19:28 -0700 (PDT)
Received: by mail-ed1-x544.google.com with SMTP id f25so7795353edw.10; Fri, 01 Nov 2019 08:19:28 -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=/4J85np3gy2WLkbdP27XLUAbFG8aDGu3k+NGCVVmE/0=; b=S+cW+kd0V/+Tb/+gMp4Wq5Yxt5SmmICpzBl8Uj53UjLn/Podrt+iBcPp7Mu8fxoZ3G vXrpnipsoBLW5yBQC88bcNW1hs3aZMnE7ZsWibU1C527rpf79j0RljtD+WGoA/QP+mXQ vVUWyv8UCme+0zeoWaQvHr580kt+DqM/wvNht7wybdr4k8LwmZiAN0azAFD8Tejd1Qmx tgNq6RxetU6+qaS9vSJ5+fE4ywmQ5HMSSbWnbBPGXljrBS+DZGQCUIPH166KaEQIK2a5 +EdHcCusoSJ5sSJ8tKN5j/NNFytBFPJRSH4e12F+CrFFp5QvAekz3G5g7L9aaPOK1TI8 ckrg==
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=/4J85np3gy2WLkbdP27XLUAbFG8aDGu3k+NGCVVmE/0=; b=n42HM+tYwspemmCSNQ50ppoRvF7BPkVICU5VKe+ZeCge+XFHie6SLYL2N1KjZQwLQ6 vwCCTj/GC9Etd0cY3YauSF9IAXIN+1gBifMjb2ZCNHUSoAorJhiWam1T1TLIHQaj2BRo 5bLbFa6rApA0xBcsz4DwLZJ33gUwd/61EekT6E/yzWXRX49CxNBSTvi92twdZEM1Lo5U yOdUxDbFzZNOppJwUx+AkXIBM14ayazKmCDyHVzU722mHPOMZzd6YjxzgRvWx/AkMH4S nw96J2HoyOmFXVTbI4K7knDWrm9ecpGhQ7Zqw1+5v23YurGhtGz/CoZB6rMxeCJokSpd Mqgw==
X-Gm-Message-State: APjAAAVVJOclVzwp2JwcUkJAtXQimdNpVI6Hsb64OZ6olakjQNNi9aus HZFe7ndndTlCiSwnB3YNpq+RQBKcy9MH5vKyCaI=
X-Google-Smtp-Source: APXvYqx2YV304yDant6Nfp3wSxaR+ksawSgDV7D2I9vSwhg9l/UDl8s6qgWrCmyVXs5t7bji5Mi6ptZ02XQj1cH03tY=
X-Received: by 2002:a17:906:2961:: with SMTP id x1mr10274495ejd.91.1572621567163;  Fri, 01 Nov 2019 08:19:27 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Fri, 1 Nov 2019 08:19:26 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <8f87c3ce-d9c0-4017-be6d-4a411daeaa2d.anqing.aq@alibaba-inc.com>
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com> <BN6PR2201MB1700F72F3DC8F6C3CF79902CDA600@BN6PR2201MB1700.namprd22.prod.outlook.com> <bd15f357-8e7a-42af-bf28-79f7177da385@www.fastmail.com> <f55efb80-1a95-4190-84e5-b81948a7f081.anqing.aq@alibaba-inc.com> <BN6PR2201MB17005571E88F1C68769091A3DA630@BN6PR2201MB1700.namprd22.prod.outlook.com> <69d1a917-b1f9-4142-afb0-f5c67abe7334.anqing.aq@alibaba-inc.com> <CAOYVs2r0zJzbfw5L2Mck8VEJhtyfQtHwF-db5VG45HDTF0WoOQ@mail.gmail.com> <7ac8ad51-c1a2-461b-bc47-021b3875eab8.anqing.aq@alibaba-inc.com> <CAN1APddvVeqXeWCZbe9WrLrOyVOWM5-1Dg8x5B4UpNwP6YOGrA@mail.gmail.com> <8f87c3ce-d9c0-4017-be6d-4a411daeaa2d.anqing.aq@alibaba-inc.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Fri, 1 Nov 2019 08:19:26 -0700
Message-ID: <CAN1APdd4WuMGAusz3EnCc4+BsT+hBfC9oMmAmhhwDc75wxMGiw@mail.gmail.com>
Subject: Re:Re: Fast Address Validation - about
To: Qing An <anqing.aq@alibaba-inc.com>, Marten Seemann <martenseemann@gmail.com>
Cc: "jri.ietf" <jri.ietf@gmail.com>, QUIC <quic-bounces@ietf.org>, quic <quic@ietf.org>,  mt <mt@lowentropy.net>, Max <max.ldp@alibaba-inc.com>
Content-Type: multipart/alternative; boundary="000000000000e0803405964a7d9d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2UF912BD2mSwcf37jtoCRINT8AI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 15:19:32 -0000

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

But what do you need to the token for in this case? The token is to prove
that you previously spoken to the server. But the TLS handshake provides
the same proof (but cannot redirect and must carry state). Any additional
information the token might carry is only interesting in Initial packets
where the connection can be stopped early or (in ongoing work) to encrypt
the initial packet. That is not relevant during handshake. The Diffie
Helman key exchange takes care of all this. Since you proposal also cannot
redirect and must carry state, I don=E2=80=99t see the purpose. I do agree =
you can
deliver that token, but since it is not obvious what the token is needed
for, the purpose is unclear.

You appear to assume that address validation only happens if you have a
Retry token, bu that is not correct, it just happens with less server
resources.

On 1 November 2019 at 15.55.09, Qing An (anqing.aq@alibaba-inc.com) wrote:


Again, the fast address validation is to provide another option for server,
not to drop the Retry approach.

I think if choose not to send a Retry, it is necessary to define how to
deliver token from server to client. In this case,  via new_token frame in
handshake can be an approach.


------------------Original Mail ------------------
Sender:Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@gmail.com>
Send Date:Fri Nov 1 21:37:42 2019
Recipients:Qing An <anqing.aq@alibaba-inc.com>, Marten Seemann <
martenseemann@gmail.com>
CC:jri.ietf <jri.ietf@gmail.com>, QUIC <quic-bounces@ietf.org>, quic <
quic@ietf.org>, mt <mt@lowentropy.net>, =E5=88=98=E5=A4=A7=E9=B9=8F(=E9=B9=
=8F=E6=88=90) <max.ldp@alibaba-inc.com>
Subject:Re: Fast Address Validation - about

> You only save a roundtrip because you do not send a Retry.
>
> If you choose not to send a Retry, the client eventually gets validated
> anyway because otherwise the handshake could not complete. Therefore a
> Retry token is not needed if you go down that path. In this case the RTT
> overhead with fast address validation is the same as ordinary QUIC 1-RTT
> handshake.
>
> On the other hand, in the case where Retry is needed, the fast address
> validation approach does not solve the problem which is one of 1) defer
> handshake processing and server state until after the address is verified=
,
> or 2) redirect the client to another server through a change in
> ConnectionID.
>
>
>
> On 1 November 2019 at 14.26.24, Qing An (anqing.aq@alibaba-inc.com) wrote=
:
>
>
> I believe this can save 1-RTT.
>
> As for the privacy risk, new_token frame can be delivered via handshake
>
>
> ------------------------------------------------------------------
> From:Marten Seemann <martenseemann@gmail.com>
> Send Time:2019=E5=B9=B411=E6=9C=881=E6=97=A5(=E6=98=9F=E6=9C=9F=E4=BA=94)=
 20:54
> To:=E5=AE=89=E5=8B=8D(=E8=8E=B3=E9=80=B8) <anqing.aq@alibaba-inc.com>
> Cc:QUIC <quic-bounces@ietf.org>; quic <quic@ietf.org>; jri.ietf <
> jri.ietf@gmail.com>; mt <mt@lowentropy.net>; mikkelfj <mikkelfj@gmail.com=
>;
> =E5=88=98=E5=A4=A7=E9=B9=8F(=E9=B9=8F=E6=88=90) <max.ldp@alibaba-inc.com>
> Subject:Re: Fast Address Validation - about
>
> I don't see any enhanced client experience, since the handshake takes
> exactly the same number of round trips with your proposal as with the
> current version of the QUIC draft.
> Sending NEW_TOKEN in Initial packets provides no benefit over sending it
> in 1-RTT packets, but comes with worse privacy properties, since Initial
> packets are not encrypted and can therefore be read by on-path observers.
>
> On Fri, Nov 1, 2019 at 7:37 PM Qing An <anqing.aq@alibaba-inc.com> wrote:
>
> If so, for the first connection between client and server, server can
> choose to eliminate the use of Retry packet for token delivery, and
> rely on handshake encryption layer to prove return routability.
> In addition, New_Token frame is used by
> server, via i.e. the Initial packet, to provide the client with an
> address validation token that can be used to validate future connections.
>
> It can enhance the experience in client side for the first connection
> establishment.
>
> I submitted the draft,
> https://datatracker.ietf.org/doc/draft-an-fast-address-validation/
>
> Qing
>
>
>
> ------------------------------------------------------------------
> From:Mike Bishop <mbishop@evequefou.be>
> Send Time:2019=E5=B9=B411=E6=9C=881=E6=97=A5(=E6=98=9F=E6=9C=9F=E4=BA=94)=
 00:06
> To:=E5=AE=89=E5=8B=8D(=E8=8E=B3=E9=80=B8) <anqing.aq@alibaba-inc.com>; qu=
ic <quic@ietf.org>; jri.ietf <
> jri.ietf@gmail.com>; mt <mt@lowentropy.net>; mikkelfj <mikkelfj@gmail.com=
>
> Subject:RE: Fast Address Validation - about
>
> As Martin pointed out in the e-mail you replied to, if the server is
> willing to maintain state, any packet at the Handshake encryption layer
> proves return routability.  There seems to be no need for a separate
> address validation mechanism if the server is willing to proceed with the
> handshake.
>
>
>
> *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of* Qing An
> *Sent:* Thursday, October 31, 2019 8:56 AM
> *To:* quic <quic@ietf.org>; jri.ietf <jri.ietf@gmail.com>; mt <
> mt@lowentropy.net>; mikkelfj <mikkelfj@gmail.com>
> *Subject:* Re: Fast Address Validation - about
>
>
>
>
>
>
>
> To clarify, the proposal is not to replace the existing Retry-based
> validation, but to provide another option for server to do the client
> validation.
>
>
>
> I understand that in server side, exchanging the token at the Handshake e=
ncryption level
> will make the server start to maintain handshake states. But in client
> side, it can accelerate the connection establishment from client to serve=
r.
>
>
>
> And it is the server's decision whether to exchange token in Retry or in
> Handshake. If server chooses to accept the cost brought by token exchangi=
ng
> in Handshake, it will bring more enhanced experience in client side.
>
>
>
>
>
> BR,
>
> Qing
>
>
>
>
>
> ------------------------------------------------------------------
>
> From:Martin Thomson <mt@lowentropy.net>
>
> Send Time:2019=E5=B9=B410=E6=9C=8831=E6=97=A5(=E6=98=9F=E6=9C=9F=E5=9B=9B=
) 06:07
>
> To:quic <quic@ietf.org>
>
> Subject:Re: Fast Address Validation - about
>
>
>
>
> Also note that exchange of Handshake packets provides proof of return rou=
teability via the use of the encryption keys, so there is no need to exchan=
ge tokens at that level.
>
> On Thu, Oct 31, 2019, at 03:29, Mike Bishop wrote:
> >
> > The advantage of using Retry, however, is that the server is able to
> > keep minimal (if any) state about the client. Exchanging the token at
> > the Handshake encryption level means the server is already doing work
> > and maintaining state in order to process the handshake, which is
> > exactly what the server is trying to avoid.
> >
> >
> > *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of * Qing An
> > *Sent:* Wednesday, October 30, 2019 9:41 AM
> > *To:* quic <quic@ietf.org>; jri.ietf <jri.ietf@gmail.com>; mt
> > <mt@lowentropy.net>
> > *Cc:* =E5=88=98=E5=A4=A7=E9=B9=8F(=E9=B9=8F=E6=88=90) <max.ldp@alibaba-=
inc.com>
> > *Subject:* Fast Address Validation - about
> >
> >
> >
> >
> > Hi Martin, Jana,
> >
> > I read through https://www.ietf.org/id/draft-ietf-quic-transport-23.txt
> > and have a few comments and ideas to discuss.
> >
> >
> > [QUIC-Trans] defines a token based scheme to facilitate address
> > validation of a client. The token MUST be covered by integrity
> > protection against modification or falsification by clients. The server
> > remembers the value it sends to clients and validates the token sent
> > back from a client. In its design, Retry packet is used to deliver the
> > token to a client which address has not yet been validated. It voids
> > the first transmission of the Initial packet sent by the client, and
> > triggers a second Initial packet to be sent with the token. The
> > exchange of token will cause longer connection establishment delay for
> > a client.
> >
> >
> > To improve the efficiency of address validation during handshake, one
> > idea is that the same token can be exchanged via a different container
> > i.e. the Handshake packet, that eliminates the use of Retry packet for
> > token delivery.
> >
> >
> > I am working on the complete draft and will submit it by Friday. Before
> > that, hope this can be discussed in email first.
> >
> >
> > BR,
> >
> > Qing An
> >
>
>
>
>
>

--000000000000e0803405964a7d9d
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">But what do you need=
 to the token for in this case? The token is to prove that you previously s=
poken to the server. But the TLS handshake provides the same proof (but can=
not redirect and must carry state). Any additional information the token mi=
ght carry is only interesting in Initial packets where the connection can b=
e stopped early or (in ongoing work) to encrypt the initial packet. That is=
 not relevant during handshake. The Diffie Helman key exchange takes care o=
f all this. Since you proposal also cannot redirect and must carry state, I=
 don=E2=80=99t see the purpose. I do agree you can deliver that token, but =
since it is not obvious what the token is needed for, the purpose is unclea=
r.</div> <div id=3D"bloop_sign_1572621244365565952" class=3D"bloop_sign"><d=
iv style=3D"font-family:helvetica,arial;font-size:13px"><br></div><div styl=
e=3D"font-family:helvetica,arial;font-size:13px">You appear to assume that =
address validation only happens if you have a Retry token, bu that is not c=
orrect, it just happens with less server resources.</div></div> <br><p clas=
s=3D"airmail_on">On 1 November 2019 at 15.55.09, Qing An (<a href=3D"mailto=
:anqing.aq@alibaba-inc.com">anqing.aq@alibaba-inc.com</a>) wrote:</p> <bloc=
kquote type=3D"cite" class=3D"clean_bq"><span><div><div></div><div>


<title></title>


<div id=3D"mailbox-conversation">
<div><br></div>
<div>Again, the fast address validation is to provide another
option for server, not to drop the Retry approach.</div>
<div><br></div>
<div>I think if choose not to send a Retry, it is necessary to
define how to deliver token from server to client. In this case,
=C2=A0via new_token frame in handshake can be an approach.</div>
<div><br></div>
<div><br></div>
<blockquote>
<div>
<div style=3D"font-size:70%">------------------Original Mail
------------------</div>
<div><span class=3D"forward-header-title">Sender:</span>Mikkel Fahn=C3=B8e
J=C3=B8rgensen &lt;<a href=3D"mailto:mikkelfj@gmail.com">mikkelfj@gmail.com=
</a>&gt;</div>
<div><span class=3D"forward-header-title">Send Date:</span>Fri Nov 1
21:37:42 2019</div>
<div><span class=3D"forward-header-title">Recipients:</span>Qing An
&lt;<a href=3D"mailto:anqing.aq@alibaba-inc.com">anqing.aq@alibaba-inc.com<=
/a>&gt;, Marten Seemann
&lt;<a href=3D"mailto:martenseemann@gmail.com">martenseemann@gmail.com</a>&=
gt;</div>
<div><span class=3D"forward-header-title">CC:</span>jri.ietf
&lt;<a href=3D"mailto:jri.ietf@gmail.com">jri.ietf@gmail.com</a>&gt;, QUIC =
&lt;<a href=3D"mailto:quic-bounces@ietf.org">quic-bounces@ietf.org</a>&gt;,
quic &lt;<a href=3D"mailto:quic@ietf.org">quic@ietf.org</a>&gt;, mt &lt;<a =
href=3D"mailto:mt@lowentropy.net">mt@lowentropy.net</a>&gt;, =E5=88=98=E5=
=A4=A7=E9=B9=8F(=E9=B9=8F=E6=88=90)
&lt;<a href=3D"mailto:max.ldp@alibaba-inc.com">max.ldp@alibaba-inc.com</a>&=
gt;</div>
<div><span class=3D"forward-header-title">Subject:</span>Re: Fast
Address Validation - about</div>
</div>
<div>
<blockquote class=3D"gmail_quote">

<div id=3D"bloop_customfont" style=3D"font-family: helvetica , arial;font-s=
ize: 13.0px;color: ;margin: 0.0px;line-height: auto;">
You only save a roundtrip because you do not send a Retry.</div>
<div id=3D"bloop_customfont" style=3D"font-family: helvetica , arial;font-s=
ize: 13.0px;color: ;margin: 0.0px;line-height: auto;">
<br></div>
<div id=3D"bloop_customfont" style=3D"font-family: helvetica , arial;font-s=
ize: 13.0px;color: ;margin: 0.0px;line-height: auto;">
If you choose not to send a Retry, the client eventually gets
validated anyway because otherwise the handshake could not
complete. Therefore a Retry token is not needed if you go down that
path. In this case the RTT overhead with fast address validation is
the same as ordinary QUIC 1-RTT handshake.</div>
<div id=3D"bloop_customfont" style=3D"font-family: helvetica , arial;font-s=
ize: 13.0px;color: ;margin: 0.0px;line-height: auto;">
<br></div>
<div id=3D"bloop_customfont" style=3D"font-family: helvetica , arial;font-s=
ize: 13.0px;color: ;margin: 0.0px;line-height: auto;">
On the other hand, in the case where Retry is needed, the fast
address validation approach does not solve the problem which is one
of 1) defer handshake processing and server state until after the
address is verified, or 2) redirect the client to another server
through a change in ConnectionID.</div>
<div id=3D"bloop_customfont" style=3D"font-family: helvetica , arial;font-s=
ize: 13.0px;color: ;margin: 0.0px;line-height: auto;">
<br></div>
<div id=3D"bloop_sign_1572615124613484032" class=3D"bloop_sign">
<div style=3D"font-family:helvetica,arial;font-size:13.0px">
<br></div>
</div>
<br>
<p class=3D"airmail_on">On 1 November 2019 at 14.26.24, Qing An
(<a href=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_blank">anqing.aq@a=
libaba-inc.com</a>) wrote:</p>
<blockquote class=3D"clean_bq">
<div>
<div>
<div class=3D"__aliyun_email_body_block">
<div style=3D"line-height:1.7;font-family:tahoma,arial,stheiti,simsun;font-=
size:14.0px;color:#000000">
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>I believe this can save
1-RTT.</span></div>
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>As for the privacy risk, new_token
frame can be delivered via handshake</span></div>
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span><br></span></div>
<blockquote style=3D"margin-right:0.0px;margin-top:0.0px;margin-bottom:0.0p=
x;font-family:tahoma,arial,stheiti,simsun;font-size:14.0px;color:#000000">
<div style=3D"clear:both">
<span>------------------------------------------------------------------</s=
pan></div>
<div style=3D"clear:both"><span>From:Marten Seemann &lt;<a href=3D"mailto:m=
artenseemann@gmail.com" target=3D"_blank">martenseemann@gmail.com</a>&gt;</=
span></div>
<div style=3D"clear:both"><span>Send Time:2019=E5=B9=B411=E6=9C=881=E6=97=
=A5(=E6=98=9F=E6=9C=9F=E4=BA=94)
20:54</span></div>
<div style=3D"clear:both"><span>To:=E5=AE=89=E5=8B=8D(=E8=8E=B3=E9=80=B8) &=
lt;<a href=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_blank">anqing.aq=
@alibaba-inc.com</a>&gt;</span></div>
<div style=3D"clear:both"><span>Cc:QUIC &lt;<a href=3D"mailto:quic-bounces@=
ietf.org" target=3D"_blank">quic-bounces@ietf.org</a>&gt;; quic &lt;<a href=
=3D"mailto:quic@ietf.org" target=3D"_blank">quic@ietf.org</a>&gt;;
jri.ietf &lt;<a href=3D"mailto:jri.ietf@gmail.com" target=3D"_blank">jri.ie=
tf@gmail.com</a>&gt;; mt &lt;<a href=3D"mailto:mt@lowentropy.net" target=3D=
"_blank">mt@lowentropy.net</a>&gt;; mikkelfj &lt;<a href=3D"mailto:mikkelfj=
@gmail.com" target=3D"_blank">mikkelfj@gmail.com</a>&gt;; =E5=88=98=E5=A4=
=A7=E9=B9=8F(=E9=B9=8F=E6=88=90) &lt;<a href=3D"mailto:max.ldp@alibaba-inc.=
com" target=3D"_blank">max.ldp@alibaba-inc.com</a>&gt;</span></div>
<div style=3D"clear:both"><span>Subject:Re: Fast Address Validation
- about</span></div>
<div style=3D"clear:both"><span><br></span></div>
<div>
<div><span>I don&#39;t see any enhanced client experience, since the
handshake takes exactly the same number of round trips with your
proposal as with the current version of the QUIC
draft.<br></span></div>
<div><span>Sending NEW_TOKEN in Initial packets provides no benefit
over sending it in 1-RTT packets, but comes with worse privacy
properties, since Initial packets are not encrypted and can
therefore be read by on-path observers.<br></span></div>
</div>
<span><br></span>
<div class=3D"gmail_quote">
<div class=3D"gmail_attr"><span>On Fri, Nov 1, 2019 at 7:37 PM Qing
An &lt;<a href=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_blank">anqin=
g.aq@alibaba-inc.com</a>&gt;
wrote:<br></span></div>
<div style=3D"margin:14.0px 0.0px">
<div style=3D"line-height:1.7;font-family:tahoma,arial,stheiti,simsun;font-=
size:14.0px;color:#000000">
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>If so,
f<span>or=C2=A0the=C2=A0first</span>=C2=A0connection=C2=A0between=C2=A0clie=
nt=C2=A0and=C2=A0server,
server can choose to eliminate=C2=A0the=C2=A0use=C2=A0of=C2=A0Retry
packet=C2=A0for=C2=A0token=C2=A0delivery, and
rely=C2=A0on=C2=A0handshake=C2=A0encryption=C2=A0layer=C2=A0to
prove=C2=A0return routability.=C2=A0 In=C2=A0addition, New_Token
frame is=C2=A0used=C2=A0by
server,=C2=A0via=C2=A0i.e.=C2=A0the=C2=A0Initial=C2=A0packet,=C2=A0to=C2=A0=
provide=C2=A0the=C2=A0client=C2=A0with=C2=A0an
address=C2=A0validation=C2=A0token=C2=A0that=C2=A0can=C2=A0be=C2=A0used=C2=
=A0to=C2=A0validate=C2=A0future<span>=C2=A0connections.</span></span></div>
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>It can enhance the experience in
client side for the first connection establishment.</span></div>
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>I submitted the
draft,=C2=A0<a href=3D"https://datatracker.ietf.org/doc/draft-an-fast-addre=
ss-validation/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-an=
-fast-address-validation/</a></span></div>
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>Qing</span></div>
<div style=3D"clear:both"></div>
<div style=3D"clear:both"><br></div>
<div style=3D"clear:both"><br></div>
<div style=3D"clear:both"><br></div>
<div style=3D"clear:both">
------------------------------------------------------------------</div>
<div style=3D"clear:both">From:Mike Bishop &lt;<a href=3D"mailto:mbishop@ev=
equefou.be" target=3D"_blank">mbishop@evequefou.be</a>&gt;</div>
<div style=3D"clear:both">Send Time:2019=E5=B9=B411=E6=9C=881=E6=97=A5(=E6=
=98=9F=E6=9C=9F=E4=BA=94) 00:06</div>
<div style=3D"clear:both">To:=E5=AE=89=E5=8B=8D(=E8=8E=B3=E9=80=B8) &lt;<a =
href=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_blank">anqing.aq@aliba=
ba-inc.com</a>&gt;; quic &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_bl=
ank">quic@ietf.org</a>&gt;;
jri.ietf &lt;<a href=3D"mailto:jri.ietf@gmail.com" target=3D"_blank">jri.ie=
tf@gmail.com</a>&gt;; mt &lt;<a href=3D"mailto:mt@lowentropy.net" target=3D=
"_blank">mt@lowentropy.net</a>&gt;; mikkelfj &lt;<a href=3D"mailto:mikkelfj=
@gmail.com" target=3D"_blank">mikkelfj@gmail.com</a>&gt;</div>
<div style=3D"clear:both">Subject:RE: Fast Address Validation -
about</div>
<div style=3D"clear:both"><br></div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
As Martin pointed out in the e-mail you replied to, if the server
is willing to maintain state, any packet at the Handshake
encryption layer proves return routability.=C2=A0 There seems to be
no need for a separate address validation mechanism if the server
is willing to proceed with the handshake.</p>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
=C2=A0</p>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<b>From:</b> QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_b=
lank">quic-bounces@ietf.org</a>&gt; <b>On Behalf Of</b>
Qing An<br>
<b>Sent:</b> Thursday, October 31, 2019 8:56 AM<br>
<b>To:</b> quic &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic=
@ietf.org</a>&gt;; jri.ietf &lt;<a href=3D"mailto:jri.ietf@gmail.com" targe=
t=3D"_blank">jri.ietf@gmail.com</a>&gt;; mt &lt;<a href=3D"mailto:mt@lowent=
ropy.net" target=3D"_blank">mt@lowentropy.net</a>&gt;; mikkelfj &lt;<a href=
=3D"mailto:mikkelfj@gmail.com" target=3D"_blank">mikkelfj@gmail.com</a>&gt;=
<br>
<b>Subject:</b> Re: Fast Address Validation - about</p>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
=C2=A0</p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
To
clarify, the proposal is not to replace the existing Retry-based
validation, but to provide another option for server to do the
client validation.</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
I
understand that in server side, e<span style=3D"background:none 0.0% 0.0% r=
epeat scroll white">xchanging=C2=A0the=C2=A0token=C2=A0at=C2=A0the=C2=A0Han=
dshake=C2=A0encryption=C2=A0level
will make the server start to maintain handshake states. But in
client side, it can accelerate the connection establishment from
client to server.</span></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black;b=
ackground:none 0.0% 0.0% repeat scroll white">
And it is the server&#39;s decision whether to exchange token in Retry
or in Handshake. If server chooses to accept the cost brought by
token exchanging in Handshake, it will bring more enhanced
experience in client side.</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black;b=
ackground:none 0.0% 0.0% repeat scroll white">
BR,</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black;b=
ackground:none 0.0% 0.0% repeat scroll white">
Qing</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div style=3D"margin:14.0px 0.0px">
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
------------------------------------------------------------------</span></=
p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
From:Martin
Thomson &lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"_blank" style=3D=
"color:#0000ff;text-decoration:underline #0000ff">mt@lowentropy.net</a>&gt;=
</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
Send
Time:2019</span><span style=3D"font-size:14.0px;font-family:ms gothic;color=
:black">=E5=B9=B4</span><span style=3D"font-size:14.0px;font-family:tahoma,=
sans-serif;color:black">10</span><span style=3D"font-size:14.0px;font-famil=
y:ms gothic;color:black">=E6=9C=88</span><span style=3D"font-size:14.0px;fo=
nt-family:tahoma,sans-serif;color:black">31</span><span style=3D"font-size:=
14.0px;font-family:ms gothic;color:black">=E6=97=A5</span><span style=3D"fo=
nt-size:14.0px;font-family:tahoma,sans-serif;color:black">(</span><span sty=
le=3D"font-size:14.0px;font-family:ms gothic;color:black">=E6=98=9F=E6=9C=
=9F=E5=9B=9B</span><span style=3D"font-size:14.0px;font-family:tahoma,sans-=
serif;color:black">)
06:07</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
To:quic
&lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank" style=3D"color:#0000=
ff;text-decoration:underline #0000ff">quic@ietf.org</a>&gt;</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
Subject:Re:
Fast Address Validation - about</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
Also=C2=A0note=C2=A0that=C2=A0exchange=C2=A0of=C2=A0Handshake=C2=A0packets=
=C2=A0provides=C2=A0proof=C2=A0of=C2=A0return=C2=A0routeability=C2=A0via=C2=
=A0the=C2=A0use=C2=A0of=C2=A0the=C2=A0encryption=C2=A0keys,=C2=A0so=C2=A0th=
ere=C2=A0is=C2=A0no=C2=A0need=C2=A0to=C2=A0exchange=C2=A0tokens=C2=A0at=C2=
=A0that=C2=A0level.<br>

<br>
On=C2=A0Thu,=C2=A0Oct=C2=A031,=C2=A02019,=C2=A0at=C2=A003:29,=C2=A0Mike=C2=
=A0Bishop=C2=A0wrote:<br>

&gt;=C2=A0=C2=A0<br>
&gt;=C2=A0The=C2=A0advantage=C2=A0of=C2=A0using=C2=A0Retry,=C2=A0however,=
=C2=A0is=C2=A0that=C2=A0the=C2=A0server=C2=A0is=C2=A0able=C2=A0to=C2=A0<br>

&gt;=C2=A0keep=C2=A0minimal=C2=A0(if=C2=A0any)=C2=A0state=C2=A0about=C2=A0t=
he=C2=A0client.=C2=A0Exchanging=C2=A0the=C2=A0token=C2=A0at=C2=A0<br>

&gt;=C2=A0the=C2=A0Handshake=C2=A0encryption=C2=A0level=C2=A0means=C2=A0the=
=C2=A0server=C2=A0is=C2=A0already=C2=A0doing=C2=A0work=C2=A0<br>

&gt;=C2=A0and=C2=A0maintaining=C2=A0state=C2=A0in=C2=A0order=C2=A0to=C2=A0p=
rocess=C2=A0the=C2=A0handshake,=C2=A0which=C2=A0is=C2=A0<br>

&gt;=C2=A0exactly=C2=A0what=C2=A0the=C2=A0server=C2=A0is=C2=A0trying=C2=A0t=
o=C2=A0avoid.<br>

&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0*From:*=C2=A0QUIC=C2=A0&lt;<a href=3D"mailto:quic-bounces@ietf.or=
g" target=3D"_blank" style=3D"color:#0000ff;text-decoration:underline #0000=
ff">quic-bounces@ietf.org</a>&gt;=C2=A0*On=C2=A0Behalf=C2=A0Of=C2=A0*=C2=A0=
Qing=C2=A0An<br>

&gt;=C2=A0*Sent:*=C2=A0Wednesday,=C2=A0October=C2=A030,=C2=A02019=C2=A09:41=
=C2=A0AM<br>

&gt;=C2=A0*To:*=C2=A0quic=C2=A0&lt;<a href=3D"mailto:quic@ietf.org" target=
=3D"_blank" style=3D"color:#0000ff;text-decoration:underline #0000ff">quic@=
ietf.org</a>&gt;;=C2=A0jri.ietf=C2=A0&lt;<a href=3D"mailto:jri.ietf@gmail.c=
om" target=3D"_blank" style=3D"color:#0000ff;text-decoration:underline #000=
0ff">jri.ietf@gmail.com</a>&gt;;=C2=A0mt=C2=A0<br>

&gt;=C2=A0&lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"_blank" style=
=3D"color:#0000ff;text-decoration:underline #0000ff">mt@lowentropy.net</a>&=
gt;<br>

&gt;=C2=A0*Cc:*=C2=A0</span><span style=3D"font-size:14.0px;font-family:ms =
gothic;color:black">=E5=88=98=E5=A4=A7</span><span style=3D"font-size:14.0p=
x;font-family:microsoft jhenghei,sans-serif;color:black">=E9=B9=8F</span><s=
pan style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">(<=
/span><span style=3D"font-size:14.0px;font-family:microsoft jhenghei,sans-s=
erif;color:black">=E9=B9=8F=E6=88=90</span><span style=3D"font-size:14.0px;=
font-family:tahoma,sans-serif;color:black">)=C2=A0&lt;<a href=3D"mailto:max=
.ldp@alibaba-inc.com" target=3D"_blank" style=3D"color:#0000ff;text-decorat=
ion:underline #0000ff">max.ldp@alibaba-inc.com</a>&gt;<br>

&gt;=C2=A0*Subject:*=C2=A0Fast=C2=A0Address=C2=A0Validation=C2=A0-=C2=A0abo=
ut<br>

&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0Hi=C2=A0Martin,=C2=A0Jana,=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0I=C2=A0read=C2=A0through=C2=A0<a href=3D"https://www.ietf.org/id/=
draft-ietf-quic-transport-23.txt" target=3D"_blank" style=3D"color:#0000ff;=
text-decoration:underline #0000ff">https://www.ietf.org/id/draft-ietf-quic-=
transport-23.txt</a>=C2=A0<br>

&gt;=C2=A0and=C2=A0have=C2=A0a=C2=A0few=C2=A0comments=C2=A0and=C2=A0ideas=
=C2=A0to=C2=A0discuss.<br>

&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0[QUIC-Trans]=C2=A0defines=C2=A0a=C2=A0token=C2=A0based=C2=A0schem=
e=C2=A0to=C2=A0facilitate=C2=A0address=C2=A0<br>

&gt;=C2=A0validation=C2=A0of=C2=A0a=C2=A0client.=C2=A0The=C2=A0token=C2=A0M=
UST=C2=A0be=C2=A0covered=C2=A0by=C2=A0integrity=C2=A0<br>

&gt;=C2=A0protection=C2=A0against=C2=A0modification=C2=A0or=C2=A0falsificat=
ion=C2=A0by=C2=A0clients.=C2=A0The=C2=A0server=C2=A0<br>

&gt;=C2=A0remembers=C2=A0the=C2=A0value=C2=A0it=C2=A0sends=C2=A0to=C2=A0cli=
ents=C2=A0and=C2=A0validates=C2=A0the=C2=A0token=C2=A0sent=C2=A0<br>

&gt;=C2=A0back=C2=A0from=C2=A0a=C2=A0client.=C2=A0In=C2=A0its=C2=A0design,=
=C2=A0Retry=C2=A0packet=C2=A0is=C2=A0used=C2=A0to=C2=A0deliver=C2=A0the=C2=
=A0<br>

&gt;=C2=A0token=C2=A0to=C2=A0a=C2=A0client=C2=A0which=C2=A0address=C2=A0has=
=C2=A0not=C2=A0yet=C2=A0been=C2=A0validated.=C2=A0It=C2=A0voids=C2=A0<br>

&gt;=C2=A0the=C2=A0first=C2=A0transmission=C2=A0of=C2=A0the=C2=A0Initial=C2=
=A0packet=C2=A0sent=C2=A0by=C2=A0the=C2=A0client,=C2=A0and=C2=A0<br>

&gt;=C2=A0triggers=C2=A0a=C2=A0second=C2=A0Initial=C2=A0packet=C2=A0to=C2=
=A0be=C2=A0sent=C2=A0with=C2=A0the=C2=A0token.=C2=A0The=C2=A0<br>

&gt;=C2=A0exchange=C2=A0of=C2=A0token=C2=A0will=C2=A0cause=C2=A0longer=C2=
=A0connection=C2=A0establishment=C2=A0delay=C2=A0for=C2=A0<br>

&gt;=C2=A0a=C2=A0client.<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0To=C2=A0improve=C2=A0the=C2=A0efficiency=C2=A0of=C2=A0address=C2=
=A0validation=C2=A0during=C2=A0handshake,=C2=A0one=C2=A0<br>

&gt;=C2=A0idea=C2=A0is=C2=A0that=C2=A0the=C2=A0same=C2=A0token=C2=A0can=C2=
=A0be=C2=A0exchanged=C2=A0via=C2=A0a=C2=A0different=C2=A0container=C2=A0<br=
>

&gt;=C2=A0i.e.=C2=A0the=C2=A0Handshake=C2=A0packet,=C2=A0that=C2=A0eliminat=
es=C2=A0the=C2=A0use=C2=A0of=C2=A0Retry=C2=A0packet=C2=A0for=C2=A0<br>

&gt;=C2=A0token=C2=A0delivery.=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0I=C2=A0am=C2=A0working=C2=A0on=C2=A0the=C2=A0complete=C2=A0draft=
=C2=A0and=C2=A0will=C2=A0submit=C2=A0it=C2=A0by=C2=A0Friday.=C2=A0Before=C2=
=A0<br>

&gt;=C2=A0that,=C2=A0hope=C2=A0this=C2=A0can=C2=A0be=C2=A0discussed=C2=A0in=
=C2=A0email=C2=A0first.<br>

&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0BR,<br>
&gt;=C2=A0<br>
&gt;=C2=A0Qing=C2=A0An<br>
&gt;</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif;line-height:20.0px">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
</div>
</div>
<div style=3D"line-height:20.0px;clear:both"><br></div>
</div>
</div>
</div>
</blockquote>
<div style=3D"line-height:20.0px;clear:both"><br></div>
</div>
</div>
</div>
</div>
</blockquote>
</blockquote>
</div>
</blockquote>
</div>


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

--000000000000e0803405964a7d9d--


From nobody Fri Nov  1 09:13:19 2019
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 8701E120946 for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 09:13:17 -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, 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 gMuA_dHiG8Mh for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 09:13:13 -0700 (PDT)
Received: from NAM02-CY1-obe.outbound.protection.outlook.com (mail-eopbgr760099.outbound.protection.outlook.com [40.107.76.99]) (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 9B0071208FA for <quic@ietf.org>; Fri,  1 Nov 2019 09:13:13 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=AKx6XxtDBIxVS0oEdiPLDQj3jlGKEXVcJyhkzNQxcBiUX9txzRJDOGcCdu365Km5Npm2nevSyozNz7D6jT5pigAsbDMASZ4FDZ9clAc0VvPl6cjNM50ERq59QmAF8Qq7bODcbyO9JYtm7tZ849SAJynW3DN4GBtPhvoXChI3jfX+lmkr9fgz9bIHl+AywJyaDQU5BClDsFm1Cgykfegh2YB7RdrvhCaITwt9P4ooAvVE1TaYUKzPJDdBe8ZiUYZ7G/Mq9epkBkaz21BENgSQ5JnxB78IsElREzbgkUupF5D8SUnDD1OT4kYRN6x3MmaNh0lht/gQisKZeWOUnb8I7Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NiqRAGNoOKmbf7ipv2tTyOH2w/ZsqLNJzmD3aF9TKe4=; b=NjbqhXTIwb0KMy3Wp8QSxUGG+PMkYA3b3FJihWuym56gQNXC92zZ+neuZbf7k9PvX8AwqG687cM2W3FFSee/RUng3Fj6FONHec1yv8LtOPf3BOHj751BBOyGCDM+JEu5ak8j6yEoaHoV/nt4+8O6tDjbS79+ZSFRkwZ7xrwNlD6ZX3iGoN8HlochSMXgNtPLC7EuiAFmJN5WyMco4DzZUrCJitdUtnsbemPgpkhQE1kuouZ4i3af2kv/Bm8Y/fS4mfB2e2DDN4lZ+H6CT5pZLlV4X6M3mXXQexpT5VicxWsUJwO5tRLw1EHffJ9qZdl3VBc/EBCMRuoEyjQY3Nmb2w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=evequefou.be; dmarc=pass action=none header.from=evequefou.be; dkim=pass header.d=evequefou.be; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector2-evequefou-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NiqRAGNoOKmbf7ipv2tTyOH2w/ZsqLNJzmD3aF9TKe4=; b=U5Sd+/Pu0hNYLzzTQ3QIVdc8VaglQUTLPEtuUtms2c0/3FT7DQOhNM9rXa8xOTuNCgJq6zeQZUceVPQOi5qNvcE/fALAsJ3lAWDDRg2Mt1XGoIsEE9pQTXIxru+IHHtim9SvXVRSw9HOaZZhlXS60TAUxtnG4rqWn2afrJOqcHg=
Received: from BN6PR2201MB1700.namprd22.prod.outlook.com (10.161.152.144) by BN6PR2201MB1265.namprd22.prod.outlook.com (10.174.82.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2387.24; Fri, 1 Nov 2019 16:13:10 +0000
Received: from BN6PR2201MB1700.namprd22.prod.outlook.com ([fe80::7cb4:5e4e:334c:a737]) by BN6PR2201MB1700.namprd22.prod.outlook.com ([fe80::7cb4:5e4e:334c:a737%7]) with mapi id 15.20.2387.028; Fri, 1 Nov 2019 16:13:10 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Kazuho Oku <kazuhooku@gmail.com>, David Schinazi <dschinazi.ietf@gmail.com>
CC: QUIC <quic@ietf.org>
Subject: RE: Version Ossification: Intended Scope for QUICv1
Thread-Topic: Version Ossification: Intended Scope for QUICv1
Thread-Index: AQHVkDACwTgP/lZwVUOZm0QUJca1i6d1RWIAgAE1I2A=
Date: Fri, 1 Nov 2019 16:13:09 +0000
Message-ID: <BN6PR2201MB1700184D81061E2CBFD77BFBDA620@BN6PR2201MB1700.namprd22.prod.outlook.com>
References: <CAPDSy+6E79OySoOLbJ8eWp0J-+3yeB5iGvj6sW19bEDn_V7-NA@mail.gmail.com> <CANatvzzaWFgrvnaV=VeZRAVvxqSBeMSZT5aMUu7-Vh9raeZJFw@mail.gmail.com>
In-Reply-To: <CANatvzzaWFgrvnaV=VeZRAVvxqSBeMSZT5aMUu7-Vh9raeZJFw@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: [2600:2b00:931f:a301:44f1:b2d7:ebd1:d973]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: be233a1a-bf43-46dc-a03d-08d75ee6637b
x-ms-traffictypediagnostic: BN6PR2201MB1265:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <BN6PR2201MB1265C4BDB7CF6BC5D86AA1F6DA620@BN6PR2201MB1265.namprd22.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 020877E0CB
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(136003)(366004)(39830400003)(346002)(376002)(189003)(199004)(76116006)(66946007)(606006)(6246003)(86362001)(2906002)(52536014)(71200400001)(14454004)(6116002)(790700001)(476003)(11346002)(316002)(5660300002)(25786009)(508600001)(71190400001)(446003)(110136005)(8676002)(64756008)(66446008)(4326008)(229853002)(74316002)(76176011)(6306002)(7736002)(33656002)(102836004)(99286004)(8936002)(486006)(561944003)(236005)(66476007)(9686003)(54896002)(6436002)(55016002)(6506007)(53546011)(186003)(66556008)(46003)(14444005)(256004)(81166006)(7696005)(81156014); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR2201MB1265; H:BN6PR2201MB1700.namprd22.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: gi4Khg1tcRfQY+q43urWl0uanX3GBatNFAl1QboBVC7IP2k27t2wzar3whaZkvImlbS1S7jj1wGP1a4gly7U/p64y6K2A/nCjcraSPn4QcovsAktPQlZpRszeVF/L86ZJs1auk3dWm9in9hvoHKKBjjNt6bL48A2+b2YQZT5R50jjQOit1e1XFqOvWVDRJXPEfyD/Q3yMY2fQypPEEoCkTemgdmAT9cBTY3yHYRDLdQu9BkJ/rUzNWMWP9XKSK2/DWAoV0cpU/knt05gSlXyUd3Pg1HC34c5LKBfsIGJ7EIC3V3/2TRguWc602TKjeBCOJFmyWygDV4gzjFhBR9k4WYwf5/YZWZwvGJ2L/ptowtQe3ZzKFuv1GG5aZ5TndGXB45SvDzkullDCrPN5J02W9AzJtEmM/J3infnsWZuflIytqGlvCRlKl8G7S8xud2AKWU2+DkHPrJ5ULOlAFNOWMnNkHgQgbqqiA6BlyHjXX8=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BN6PR2201MB1700184D81061E2CBFD77BFBDA620BN6PR2201MB1700_"
MIME-Version: 1.0
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: be233a1a-bf43-46dc-a03d-08d75ee6637b
X-MS-Exchange-CrossTenant-originalarrivaltime: 01 Nov 2019 16:13:09.9680 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: AkPtrlKKpAoDd3/arBnF58inxR2kgQ/iA6oJfsmrdFORMB4l/WuLxtF3XnfYo6QjLbd2py87Gc1/Sl1esPXz4A==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR2201MB1265
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/delzgnbVVVRCjCcvm8e12bHQE5I>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 16:13:17 -0000

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

VGhlIGZ1bmRhbWVudGFsIHByb2JsZW0gaW4gYWxsIHRoaXMgaXMgd2hhdCBoYXBwZW5zIHdoZW4g
YSBzZXJ2ZXIgaXMgbm8gbG9uZ2VyIGluIHBvc3Nlc3Npb24gb2YgdGhlIG1hcHBpbmcgaXQgc2Vu
dCB0byB0aGUgY2xpZW50LiAgT25lIG9wdGlvbiBpcyB0byBzYXkgdGhhdCBzZXJ2ZXJzIHNpbXBs
eSBNVVNUIHBlcnNpc3QgdGhpcywgYW5kIGlmIHRoZXkgZG9u4oCZdCwgaGFuZHNoYWtlcyB3aWxs
IGZhaWwg4oCTIHdlIHRyaWVkIHRoYXQgd2l0aCBIU1RTLCBhbmQgd2UgZm91bmQgdGhhdCBzZXJ2
ZXJzIGRvbuKAmXQgbGlrZSB0aGluZ3MgdGhhdCBjYW4gbGVhdmUgdGhlIHNpdGUgYnJva2VuLiAg
SSBkb27igJl0IHRoaW5rIHRoYXTigJlzIGEgZ29vZCBwYXRoLiAgRWl0aGVyIGl0IHdpbGwgYnJl
YWsgdGhpbmdzLCBvciBzZXJ2ZXJzIHdvbuKAmXQgdXNlIHRoaXMgbWVjaGFuaXNtLCBvciBtb3Jl
IGxpa2VseSBib3RoIGluIHNlcXVlbmNlLg0KDQpUaGUgbmV4dCBvYnZpb3VzIHNvbHV0aW9uLCBz
ZW5kaW5nIGEgVk4gcGFja2V0IHRlbGxpbmcgdGhlIGNsaWVudCB0byBjb21lIGJhY2sgdG8gdjEg
YW5kIHRoZSBzcGVjLWRlZmluZWQgc2FsdCwgY29udGFpbnMgYSBzaW1wbGUgdmVyc2lvbiBkb3du
Z3JhZGUgYXR0YWNrIGJ5IGEgbWlkZGxlYm94LiAgVGhlcmUgYXJlIHBvc3NpYmxlIG1pdGlnYXRp
b25zIOKAkyB0aGUgY2xpZW50IGNvdWxkIGNvbnRpbnVlIHByZXNlbnRpbmcgdGhlIHRva2VuLCBt
ZWFuaW5nIHRoZSBzZXJ2ZXIgd291bGQgYmUgYWJsZSB0byB0ZWxsIHdoZXRoZXIgYSBkb3duZ3Jh
ZGUg4oCcYWN0dWFsbHkgaGFwcGVuZWTigJ0gb3Igbm90LiAgKEkuZS4gd2hldGhlciBpdCBjb3Vs
ZCBzdGlsbCBoYXZlIHBhcnNlZCB0aGUgdmVyc2lvbiBhc3NvY2lhdGVkIHdpdGggdGhlIHRva2Vu
KSAgSWYgdGhlIGRvd25ncmFkZSB3YXMgaWxsZWdpdGltYXRlLCB0aGF0IGNvdWxkIGJlIGNvbW11
bmljYXRlZC4gIEhvd2V2ZXIsIHRoYXQgbGlrZWx5IG1lYW5zIGZpZ3VyaW5nIG91dCBRVUlD4oCZ
cyBvd24gdmVyc2lvbiBuZWdvdGlhdGlvbiBzdG9yeSBhbmQgZG93bmdyYWRlIG1pdGlnYXRpb24g
YW5kIGp1c3QgdXNpbmcgdGhhdC4NCg0KV2UgY291bGQgYWxzbyB0cnkgdG8gYnVpbGQgc29tZXRo
aW5nIGxpa2UgRVNOSeKAmXMgcmVjb3ZlcnkgcGF0aCwgd2hlcmUgdGhlIGluZm9ybWF0aW9uIGlu
Y2x1ZGVzIHdoYXQgaGFzIHRvIGJlIGRlbW9uc3RyYXRlZCBmb3IgYSByZWNvdmVyeSB2YWx1ZS4g
IFRoZSB0cm91YmxlIGlzIHRoYXQsIHdoaWxlIFRMUyBjYW4gdHJhbnNmZXIgYSBjZXJ0aWZpY2F0
ZSBhbmQgcmVseSBvbiBQS0kgYXMgdGhhdCByZWNvdmVyeSBwYXRoLCB3ZeKAmXJlIGluIGEgbGl0
dGxlIGJpdCBtb3JlIHVuY2hhcnRlZCB0ZXJyaXRvcnkuICBUaGUgb25seSByZWFkeSBzb2x1dGlv
biBJIHNlZSBpbiB0aGlzIHNwYWNlIGlzIHNvbWUga2luZCBvZiBsb25nZXItbGl2ZWQga2V5cGFp
ciB0aGF0IHRoZSBzZXJ2ZXIgaXMgc29tZWhvdyDigJxsZXNzIGxpa2VseeKAnSB0byBsb3NlLCBi
dXQgaWYgeW91IGNhbiBwZXJzaXN0IHRoYXQga2V5LCB5b3UgY2FuIHByb2JhYmx5IGFsc28gcGVy
c2lzdCB0aGUgb3JpZ2luYWwgY29uZmlndXJhdGlvbi4gIChQbHVzLCB5b3UgZG9u4oCZdCB3YW50
IHRvIGJlIGRvaW5nIGFzeW1tZXRyaWMgY3J5cHRvIGJlZm9yZSB5b3XigJl2ZSBldmVuIGRlY2lk
ZWQgd2hldGhlciB0byBwcm9jZXNzIHRoZSBoYW5kc2hha2UuKQ0KDQpJIHJlbWFpbiBhIGxpdHRs
ZSB1bmNvbWZvcnRhYmxlIHRoYXQgd2UgZW50aXJlbHkgcHVudGVkIG91ciB2ZXJzaW9uIG5lZ290
aWF0aW9uIHN0b3J5IGZyb20gdjEsIGFuZCBJIHRoaW5rIHRoZSBjbGVhbmVzdCBzb2x1dGlvbiBp
cyB0byBicmluZyBpdCBiYWNrIGluIHN1cHBvcnQgb2YgIzMxNjYuICBIb3dldmVyLCB0aGF0IGhh
cyBib3RoIHNjaGVkdWxlIGFuZCBzZWN1cml0eSBpbXBsaWNhdGlvbnMg4oCTIHdlIGRvbuKAmXQg
d2FudCB0byBnZXQgdGhpcyBwYXJ0IHdyb25nLg0KDQpGcm9tOiBRVUlDIDxxdWljLWJvdW5jZXNA
aWV0Zi5vcmc+IE9uIEJlaGFsZiBPZiBLYXp1aG8gT2t1DQpTZW50OiBUaHVyc2RheSwgT2N0b2Jl
ciAzMSwgMjAxOSA1OjM0IFBNDQpUbzogRGF2aWQgU2NoaW5hemkgPGRzY2hpbmF6aS5pZXRmQGdt
YWlsLmNvbT4NCkNjOiBRVUlDIDxxdWljQGlldGYub3JnPg0KU3ViamVjdDogUmU6IFZlcnNpb24g
T3NzaWZpY2F0aW9uOiBJbnRlbmRlZCBTY29wZSBmb3IgUVVJQ3YxDQoNCkhpIERhdmlkLA0KDQpU
aGFuayB5b3UgZm9yIHN1bW1hcml6aW5nIHRoZSBoaWdoLWxldmVsIG9wdGlvbnMuIEkgdGhpbmsg
aXQncyB2ZXJ5IHVzZWZ1bCB0byBoYXZlIHRoaXMgZGlzY3Vzc2lvbi4NCg0KUGxlYXNlIHNlZSBt
eSBjb21tZW50cyBiZWxvdy4NCg0KMjAxOeW5tDEx5pyIMeaXpSjph5EpIDY6MTMgRGF2aWQgU2No
aW5hemkgPGRzY2hpbmF6aS5pZXRmQGdtYWlsLmNvbTxtYWlsdG86ZHNjaGluYXppLmlldGZAZ21h
aWwuY29tPj46DQpIaSBmb2xrcywNCg0KVGhlIGNvbnZlcnNhdGlvbiBhcm91bmQgdmVyc2lvbiBv
c3NpZmljYXRpb24gaGFzIGJlZW4gcmVhbGx5IGludGVyZXN0aW5nIHNpbmNlIEN1cGVydGluby4g
QnV0IGF0IGxlYXN0IGZvciBtZSBpdCdzIHJlYWNoZWQgYSBsZXZlbCBvZiBjb21wbGV4aXR5IHRo
YXQgd2FycmFudHMgdGFraW5nIGEgc3RlcCBiYWNrIGFuZCBsb29raW5nIGF0IHdoYXQgd2UncmUg
dHJ5aW5nIHRvIHNvbHZlLiBIZXJlJ3MgbXkgdW5kZXJzdGFuZGluZyBvZiB3aGVyZSB3ZSBhcmU6
DQoNCjEpIEluIEN1cGVydGlubyB0aGVyZSB3YXMgY29uc2Vuc3VzIGluIHRoZSByb29tIHRvIGRv
IHNvbWV0aGluZyB0byBtaXRpZ2F0ZSBvc3NpZmljYXRpb24gb2YgUVVJQ3YxLg0KDQoyKSBUaGUg
c29sdXRpb24gdGhhdCBmb2xrcyBsaWtlZCB3YXMgdG8gaGF2ZSBhIGNvbmNlcHQgb2YgYWx0ZXJu
YXRpdmUgdmVyc2lvbnMgYW5kIGFsdGVybmF0aXZlIHNhbHRzIHRoYXQgYWN0IGxpa2UgUVVJQ3Yx
IGJ1dCBhcmUgZW5jb2RlZCBkaWZmZXJlbnRseSBvdmVyIHRoZSB3aXJlLg0KDQozKSBBIGNvbmNy
ZXRlIHByb3Bvc2FsIGZvciAoMikgd2FzIGZvciBzZXJ2ZXJzIHRvIGhhdmUgdGhlaXIgb3duIHNl
dCBvZiAoYWx0ZXJuYXRpdmVfdmVyc2lvbiwgYWx0ZXJuYXRpdmVfc2FsdCkgcGFpcnMsIHRoZW4g
dHJhbnNtaXQgYSByYW5kb20gcGFpciBmcm9tIHRoYXQgc2V0IHRvIGVhY2ggY2xpZW50IChpLmUu
IHZpYSB0cmFuc3BvcnQgcGFyYW1ldGVycykuIFRoZSBzZXJ2ZXIgY2FuIHRoZW4gcmVjb25zdHJ1
Y3QgdGhlIGFsdGVybmF0aXZlX3NhbHQganVzdCBieSBzZWVpbmcgdGhlIGFsdGVybmF0aXZlX3Zl
cnNpb24uDQoNCjQpIEthenVobyBwcm9wb3NlZCBhIHNvbHV0aW9uICgjMzE2NjxodHRwczovL2dp
dGh1Yi5jb20vcXVpY3dnL2Jhc2UtZHJhZnRzL3B1bGwvMzE2Nj4pIHRoYXQgd2FzIGJvdGggbW9y
ZSBwb3dlcmZ1bCBhbmQgbW9yZSBjb21wbGV4OiB0aWUgdGhlIChhbHRlcm5hdGl2ZV92ZXJzaW9u
LCBhbHRlcm5hdGl2ZV9zYWx0KSBwYWlyIHRvIE5FV19UT0tFTiBmcmFtZXMsIHRvIGFsbG93IHNl
cnZlcnMgdG8gZ2VuZXJhdGUgYSB1bmlxdWUgYWx0ZXJuYXRpdmVfc2FsdCBwZXIgY2xpZW50IGFu
ZCBlbmNvZGUgaXQgaW4gdGhlIHRva2VuLg0KDQpJIGRpc3B1dGUgdGhlIGFyZ3VtZW50IHRoYXQg
IzMxNjYgaXMgbW9yZSBjb21wbGV4LiBNeSB2aWV3IGlzIHRoYXQgIzMxNjYgaXMgbW9yZSBwb3dl
cmZ1bCBhbmQgc2ltcGxlciB0aGFuICgzKSAodGhlIFBSIGJlaW5nICMyNTczKS4NCg0KUmVhc29u
czoNCiogRm9yIGEgc2VydmVyIGFzc29jaWF0aW5nIG9uZSBpbml0aWFsIHNhbHQgd2l0aCBvbmUg
YWx0ZXJuYXRpdmUgdmVyc2lvbiwgIzMxNjYgYW5kICMyNTczIGFyZSBpZGVudGljYWwgd2l0aCB0
aGUgZXhjZXB0aW9uIGJlaW5nIGhvdyB0aGUgaW5mb3JtYXRpb24gaXMgY2FycnlpZWQgKGkuZS4g
VFAgdnMuIE5FV19UT0tFTikuDQoqIEZvciBhIGNsaWVudCwgYnVuZGxpbmcgdGhlIGFsdGVybmF0
aXZlIHNlZWRzIGluIGEgTkVXX1RPS0VOIG1ha2VzIHRoaW5ncyBzaW1wbGVyLCBhcyBjbGllbnRz
IGFyZSBub3QgcmVxdWlyZWQgdG8gaGF2ZSBhIG5ldyBzdGF0ZSB0aGF0IGhhcyB0byBiZSByZXRh
aW5lZCBhY3Jvc3MgbXVsdGlwbGUgY29ubmVjdGlvbnMuDQoNCg0KNSkgQWZ0ZXIgc29tZSBpbnRl
cmVzdGluZyBiYWNrIGFuZCBmb3J0aCBvbiB0aGF0IFBSLCBpdCBiZWNhbWUgY2xlYXIgdGhhdCB0
aGlzIGlzIGEgaGFyZCBwcm9ibGVtIHRvIHNvbHZlOiB0aGlzIGNvdWxkIGNhdXNlIGZhaWx1cmVz
IGlmIHNlcnZlcnMgZm9yZ2V0IHRoZWlyIHRva2VuIGtleXMsIGFuZCBtaXRpZ2F0aW9ucyBmb3Ig
dGhhdCBwcm9ibGVtIGNhbiBiZWNvbWUgZG93bmdyYWRlIGF0dGFjayB2ZWN0b3JzDQoNClRoZSBw
cm9wb3NhbCBmb3IgMyBoYXMgdGhpcyBwcm9ibGVtLiBJdCBsZWFkcyB0byBhIGZhaWx1cmUgd2hl
biBhIHNlcnZlciBmb3JnZXRzIHRoZSBhbHRlcm5hdGl2ZSBpbml0aWFsIHNhbHRzLg0KDQoNCjYp
IFdoaWxlIHRoZXJlIHdhcyBjbGVhciBXRyBhcHBldGl0ZSBmb3IgKDEpLCBJJ20gbm90IHN1cmUg
d2UgaGF2ZSBjb25zZW5zdXMgdG8gYnVpbGQgYSBtb3JlIHBvd2VyZnVsIHNvbHV0aW9uIGxpa2Ug
KDQpDQoNCkkgZmVhciB0aGF0IHNvbHZpbmcgKDUpIGNvdWxkIHRha2Ugc29tZSB0aW1lLCB3aGlj
aCB3b3VsZCBkZWxheSBRVUlDdjEuIEluc3RlYWQgSSdkIGxpa2UgdG8gcHJvcG9zZSB0aGUgZm9s
bG93aW5nIHBsYW46DQphKSB3ZSB0YWtlIHRoZSBzaW1wbGVyIHNvbHV0aW9uICgzKSBhbmQgYWRk
IHRoYXQgdG8gdGhlIHNwZWMNCmIpIHdlIHRha2UgdGhlIG1vcmUgcG93ZXJmdWwvY29tcGxleCBz
b2x1dGlvbiAoNSkgYSB0dXJuIGl0IGludG8gYSBRVUlDIGV4dGVuc2lvbg0KDQpUaGF0IHdvdWxk
IGFsbG93IHVzIHRvIHNoaXAgUVVJQ3YxIHdpdGggc29tZSBsZXZlbCBvZiBvc3NpZmljYXRpb24g
bWl0aWdhdGlvbnMgd2l0aG91dCBkZWxheS4NCg0KQXMgc3RhdGVkLCB0aGUgcHJvcG9zZWQgc29s
dXRpb24gZm9yICg0KSBpcyBzaW1wbGVyIHRoYW4gKDMpLCBjYW4gYmUgdXNlZCB0byBpbXBsZW1l
bnQgKDMpLCBhbmQgYWxzbyBwcm92aWRlcyBhIHN0cm9uZ2VyIHByb3RlY3Rpb24gZm9yIHNlcnZl
cnMgY2VydGFpbiB0aGF0IHRoZXkgY2FuIHJldGFpbiB0aGUgdG9rZW4gdW5wcm90ZWN0aW9uIGtl
eXMuDQoNCkkgYWdyZWUgdGhhdCBzb2x2aW5nICg1KSBmb3IgYWxsIHBhcnRpZXMgbWlnaHQgYmUg
aGFyZCwgYW5kIHRoYXQgd2UgbWlnaHQgd2FudCB0byBwdW50IHRoYXQgdG8gdjIuIEJ1dCwgSSB0
aGluayB3ZSBzaG91bGQgYWRvcHQgKDQpIHRoYW4gKDMpIGR1ZSB0byB0aGUgYWZvcmVtZW50aW9u
ZWQgcmVhc29ucy4NCg0KDQpUaG91Z2h0cz8NCg0KRGF2aWQNCg0KDQoNCg0KLS0NCkthenVobyBP
a3UNCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
Ik1TIEdvdGhpYyI7DQoJcGFub3NlLTE6MiAxMSA2IDkgNyAyIDUgOCAyIDQ7fQ0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQE1TIEdv
dGhpYyI7DQoJcGFub3NlLTE6MiAxMSA2IDkgNyAyIDUgOCAyIDQ7fQ0KLyogU3R5bGUgRGVmaW5p
dGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWwsIGRpdi5Nc29Ob3JtYWwNCgl7bWFy
Z2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJZm9udC1zaXplOjExLjBwdDsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJs
aW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3Jh
dGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJ
e21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9u
OnVuZGVybGluZTt9DQpwLm1zb25vcm1hbDAsIGxpLm1zb25vcm1hbDAsIGRpdi5tc29ub3JtYWww
DQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsN
CgltYXJnaW4tcmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdp
bi1sZWZ0OjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixz
YW5zLXNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFs
LXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRv
d3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJ
Zm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJ
e3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpk
aXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtp
ZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4
PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8
bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0i
MSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5
IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9Ildv
cmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGUgZnVuZGFtZW50YWwgcHJvYmxl
bSBpbiBhbGwgdGhpcyBpcyB3aGF0IGhhcHBlbnMgd2hlbiBhIHNlcnZlciBpcyBubyBsb25nZXIg
aW4gcG9zc2Vzc2lvbiBvZiB0aGUgbWFwcGluZyBpdCBzZW50IHRvIHRoZSBjbGllbnQuJm5ic3A7
IE9uZSBvcHRpb24gaXMgdG8gc2F5IHRoYXQgc2VydmVycyBzaW1wbHkgTVVTVCBwZXJzaXN0IHRo
aXMsIGFuZCBpZiB0aGV5IGRvbuKAmXQsIGhhbmRzaGFrZXMgd2lsbCBmYWlsIOKAkyB3ZQ0KIHRy
aWVkIHRoYXQgd2l0aCBIU1RTLCBhbmQgd2UgZm91bmQgdGhhdCBzZXJ2ZXJzIGRvbuKAmXQgbGlr
ZSB0aGluZ3MgdGhhdCBjYW4gbGVhdmUgdGhlIHNpdGUgYnJva2VuLiZuYnNwOyBJIGRvbuKAmXQg
dGhpbmsgdGhhdOKAmXMgYSBnb29kIHBhdGguJm5ic3A7IEVpdGhlciBpdCB3aWxsIGJyZWFrIHRo
aW5ncywgb3Igc2VydmVycyB3b27igJl0IHVzZSB0aGlzIG1lY2hhbmlzbSwgb3IgbW9yZSBsaWtl
bHkgYm90aCBpbiBzZXF1ZW5jZS48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhlIG5leHQgb2J2
aW91cyBzb2x1dGlvbiwgc2VuZGluZyBhIFZOIHBhY2tldCB0ZWxsaW5nIHRoZSBjbGllbnQgdG8g
Y29tZSBiYWNrIHRvIHYxIGFuZCB0aGUgc3BlYy1kZWZpbmVkIHNhbHQsIGNvbnRhaW5zIGEgc2lt
cGxlIHZlcnNpb24gZG93bmdyYWRlIGF0dGFjayBieSBhIG1pZGRsZWJveC4mbmJzcDsgVGhlcmUg
YXJlIHBvc3NpYmxlIG1pdGlnYXRpb25zIOKAkyB0aGUgY2xpZW50IGNvdWxkIGNvbnRpbnVlIHBy
ZXNlbnRpbmcNCiB0aGUgdG9rZW4sIG1lYW5pbmcgdGhlIHNlcnZlciB3b3VsZCBiZSBhYmxlIHRv
IHRlbGwgd2hldGhlciBhIGRvd25ncmFkZSDigJxhY3R1YWxseSBoYXBwZW5lZOKAnSBvciBub3Qu
Jm5ic3A7IChJLmUuIHdoZXRoZXIgaXQgY291bGQgc3RpbGwgaGF2ZSBwYXJzZWQgdGhlIHZlcnNp
b24gYXNzb2NpYXRlZCB3aXRoIHRoZSB0b2tlbikmbmJzcDsgSWYgdGhlIGRvd25ncmFkZSB3YXMg
aWxsZWdpdGltYXRlLCB0aGF0IGNvdWxkIGJlIGNvbW11bmljYXRlZC4mbmJzcDsgSG93ZXZlciwg
dGhhdA0KIGxpa2VseSBtZWFucyBmaWd1cmluZyBvdXQgUVVJQ+KAmXMgb3duIHZlcnNpb24gbmVn
b3RpYXRpb24gc3RvcnkgYW5kIGRvd25ncmFkZSBtaXRpZ2F0aW9uIGFuZCBqdXN0IHVzaW5nIHRo
YXQuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPldlIGNvdWxkIGFsc28gdHJ5IHRvIGJ1aWxkIHNv
bWV0aGluZyBsaWtlIEVTTknigJlzIHJlY292ZXJ5IHBhdGgsIHdoZXJlIHRoZSBpbmZvcm1hdGlv
biBpbmNsdWRlcyB3aGF0IGhhcyB0byBiZSBkZW1vbnN0cmF0ZWQgZm9yIGEgcmVjb3ZlcnkgdmFs
dWUuJm5ic3A7IFRoZSB0cm91YmxlIGlzIHRoYXQsIHdoaWxlIFRMUyBjYW4gdHJhbnNmZXIgYSBj
ZXJ0aWZpY2F0ZSBhbmQgcmVseSBvbiBQS0kgYXMgdGhhdCByZWNvdmVyeQ0KIHBhdGgsIHdl4oCZ
cmUgaW4gYSBsaXR0bGUgYml0IG1vcmUgdW5jaGFydGVkIHRlcnJpdG9yeS4mbmJzcDsgVGhlIG9u
bHkgcmVhZHkgc29sdXRpb24gSSBzZWUgaW4gdGhpcyBzcGFjZSBpcyBzb21lIGtpbmQgb2YgbG9u
Z2VyLWxpdmVkIGtleXBhaXIgdGhhdCB0aGUgc2VydmVyIGlzIHNvbWVob3cg4oCcbGVzcyBsaWtl
bHnigJ0gdG8gbG9zZSwgYnV0IGlmIHlvdSBjYW4gcGVyc2lzdCB0aGF0IGtleSwgeW91IGNhbiBw
cm9iYWJseSBhbHNvIHBlcnNpc3QgdGhlIG9yaWdpbmFsDQogY29uZmlndXJhdGlvbi4mbmJzcDsg
KFBsdXMsIHlvdSBkb27igJl0IHdhbnQgdG8gYmUgZG9pbmcgYXN5bW1ldHJpYyBjcnlwdG8gYmVm
b3JlIHlvdeKAmXZlIGV2ZW4gZGVjaWRlZCB3aGV0aGVyIHRvIHByb2Nlc3MgdGhlIGhhbmRzaGFr
ZS4pPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkgcmVtYWluIGEgbGl0dGxlIHVuY29tZm9ydGFi
bGUgdGhhdCB3ZSBlbnRpcmVseSBwdW50ZWQgb3VyIHZlcnNpb24gbmVnb3RpYXRpb24gc3Rvcnkg
ZnJvbSB2MSwgYW5kIEkgdGhpbmsgdGhlIGNsZWFuZXN0IHNvbHV0aW9uIGlzIHRvIGJyaW5nIGl0
IGJhY2sgaW4gc3VwcG9ydCBvZiAjMzE2Ni4gJm5ic3A7SG93ZXZlciwgdGhhdCBoYXMgYm90aCBz
Y2hlZHVsZSBhbmQgc2VjdXJpdHkgaW1wbGljYXRpb25zIOKAkyB3ZSBkb27igJl0DQogd2FudCB0
byBnZXQgdGhpcyBwYXJ0IHdyb25nLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj5Gcm9tOjwv
Yj4gUVVJQyAmbHQ7cXVpYy1ib3VuY2VzQGlldGYub3JnJmd0OyA8Yj5PbiBCZWhhbGYgT2YgPC9i
Pg0KS2F6dWhvIE9rdTxicj4NCjxiPlNlbnQ6PC9iPiBUaHVyc2RheSwgT2N0b2JlciAzMSwgMjAx
OSA1OjM0IFBNPGJyPg0KPGI+VG86PC9iPiBEYXZpZCBTY2hpbmF6aSAmbHQ7ZHNjaGluYXppLmll
dGZAZ21haWwuY29tJmd0Ozxicj4NCjxiPkNjOjwvYj4gUVVJQyAmbHQ7cXVpY0BpZXRmLm9yZyZn
dDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFZlcnNpb24gT3NzaWZpY2F0aW9uOiBJbnRlbmRl
ZCBTY29wZSBmb3IgUVVJQ3YxPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
SGkgRGF2aWQsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
VGhhbmsgeW91IGZvciBzdW1tYXJpemluZyB0aGUgaGlnaC1sZXZlbCBvcHRpb25zLiBJIHRoaW5r
IGl0J3MgdmVyeSB1c2VmdWwgdG8gaGF2ZSB0aGlzIGRpc2N1c3Npb24uPG86cD48L286cD48L3A+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5QbGVhc2Ugc2VlIG15IGNvbW1lbnRzIGJl
bG93LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjIwMTk8c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7TVMgR290aGljJnF1b3Q7Ij7lubQ8
L3NwYW4+MTE8c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7TVMgR290aGljJnF1b3Q7Ij7m
nIg8L3NwYW4+MTxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtNUyBHb3RoaWMmcXVvdDsi
PuaXpTwvc3Bhbj4oPHNwYW4gc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O01TIEdvdGhpYyZxdW90
OyI+6YeRPC9zcGFuPikgNjoxMyBEYXZpZCBTY2hpbmF6aSAmbHQ7PGEgaHJlZj0ibWFpbHRvOmRz
Y2hpbmF6aS5pZXRmQGdtYWlsLmNvbSI+ZHNjaGluYXppLmlldGZAZ21haWwuY29tPC9hPiZndDs6
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTti
b3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7
bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+SGkgZm9sa3MsPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj5UaGUgY29udmVyc2F0aW9uIGFyb3VuZCB2ZXJzaW9uIG9zc2lmaWNhdGlvbiBoYXMg
YmVlbiByZWFsbHkgaW50ZXJlc3Rpbmcgc2luY2UgQ3VwZXJ0aW5vLiBCdXQgYXQgbGVhc3QgZm9y
IG1lIGl0J3MgcmVhY2hlZCBhIGxldmVsIG9mIGNvbXBsZXhpdHkgdGhhdCB3YXJyYW50cyB0YWtp
bmcgYSBzdGVwIGJhY2sgYW5kIGxvb2tpbmcgYXQgd2hhdCB3ZSdyZSB0cnlpbmcgdG8gc29sdmUu
IEhlcmUncyBteSB1bmRlcnN0YW5kaW5nDQogb2Ygd2hlcmUgd2UgYXJlOjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4xKSBJbiBDdXBlcnRpbm8g
dGhlcmUgd2FzIGNvbnNlbnN1cyBpbiB0aGUgcm9vbSB0byBkbyBzb21ldGhpbmcgdG8gbWl0aWdh
dGUgb3NzaWZpY2F0aW9uIG9mIFFVSUN2MS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+MikgVGhlIHNvbHV0aW9uIHRoYXQgZm9sa3MgbGlrZWQg
d2FzIHRvIGhhdmUgYSBjb25jZXB0IG9mIGFsdGVybmF0aXZlIHZlcnNpb25zIGFuZCBhbHRlcm5h
dGl2ZSBzYWx0cyB0aGF0IGFjdCBsaWtlIFFVSUN2MSBidXQgYXJlIGVuY29kZWQgZGlmZmVyZW50
bHkgb3ZlciB0aGUgd2lyZS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+MykgQSBjb25jcmV0ZSBwcm9wb3NhbCBmb3IgKDIpIHdhcyBmb3Igc2Vy
dmVycyB0byBoYXZlIHRoZWlyIG93biBzZXQgb2YgKGFsdGVybmF0aXZlX3ZlcnNpb24sIGFsdGVy
bmF0aXZlX3NhbHQpIHBhaXJzLCB0aGVuIHRyYW5zbWl0IGEgcmFuZG9tIHBhaXIgZnJvbSB0aGF0
IHNldCB0byBlYWNoIGNsaWVudCAoaS5lLiB2aWEgdHJhbnNwb3J0IHBhcmFtZXRlcnMpLiBUaGUg
c2VydmVyIGNhbiB0aGVuIHJlY29uc3RydWN0DQogdGhlIGFsdGVybmF0aXZlX3NhbHQganVzdCBi
eSBzZWVpbmcgdGhlJm5ic3A7YWx0ZXJuYXRpdmVfdmVyc2lvbi48bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+NCkgS2F6dWhvIHByb3Bvc2VkIGEg
c29sdXRpb24gKDxhIGhyZWY9Imh0dHBzOi8vZ2l0aHViLmNvbS9xdWljd2cvYmFzZS1kcmFmdHMv
cHVsbC8zMTY2IiB0YXJnZXQ9Il9ibGFuayI+IzMxNjY8L2E+KSB0aGF0IHdhcyBib3RoIG1vcmUg
cG93ZXJmdWwgYW5kIG1vcmUgY29tcGxleDogdGllIHRoZSZuYnNwOyhhbHRlcm5hdGl2ZV92ZXJz
aW9uLCBhbHRlcm5hdGl2ZV9zYWx0KSBwYWlyIHRvIE5FV19UT0tFTiBmcmFtZXMsDQogdG8gYWxs
b3cgc2VydmVycyB0byBnZW5lcmF0ZSBhIHVuaXF1ZSZuYnNwO2FsdGVybmF0aXZlX3NhbHQgcGVy
IGNsaWVudCBhbmQgZW5jb2RlIGl0IGluIHRoZSB0b2tlbi48bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5J
IGRpc3B1dGUgdGhlIGFyZ3VtZW50IHRoYXQgIzMxNjYgaXMgbW9yZSBjb21wbGV4LiBNeSB2aWV3
IGlzIHRoYXQgIzMxNjYgaXMgbW9yZSBwb3dlcmZ1bCBhbmQgc2ltcGxlciB0aGFuICgzKSAodGhl
IFBSIGJlaW5nICMyNTczKS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+UmVhc29uczo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPiogRm9yIGEgc2VydmVyIGFzc29jaWF0aW5nIG9uZSBpbml0aWFs
IHNhbHQgd2l0aCBvbmUgYWx0ZXJuYXRpdmUgdmVyc2lvbiwgIzMxNjYgYW5kICMyNTczIGFyZSBp
ZGVudGljYWwgd2l0aCB0aGUgZXhjZXB0aW9uIGJlaW5nIGhvdyB0aGUgaW5mb3JtYXRpb24gaXMg
Y2FycnlpZWQgKGkuZS4gVFAgdnMuIE5FV19UT0tFTikuPG86cD48L286cD48L3A+DQo8L2Rpdj4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj4qIEZvciBhIGNsaWVudCwgYnVuZGxpbmcgdGhl
IGFsdGVybmF0aXZlIHNlZWRzIGluIGEgTkVXX1RPS0VOIG1ha2VzIHRoaW5ncyBzaW1wbGVyLCBh
cyBjbGllbnRzIGFyZSBub3QgcmVxdWlyZWQgdG8gaGF2ZSBhIG5ldyBzdGF0ZSB0aGF0IGhhcyB0
byBiZSByZXRhaW5lZCBhY3Jvc3MgbXVsdGlwbGUgY29ubmVjdGlvbnMuPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNv
bGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0
LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj41KSBBZnRlciBzb21lIGludGVyZXN0aW5nIGJhY2sgYW5kIGZvcnRoIG9uIHRoYXQgUFIs
IGl0IGJlY2FtZSBjbGVhciB0aGF0IHRoaXMgaXMgYSBoYXJkIHByb2JsZW0gdG8gc29sdmU6IHRo
aXMgY291bGQgY2F1c2UgZmFpbHVyZXMgaWYgc2VydmVycyBmb3JnZXQgdGhlaXIgdG9rZW4ga2V5
cywgYW5kIG1pdGlnYXRpb25zIGZvciB0aGF0IHByb2JsZW0gY2FuIGJlY29tZSBkb3duZ3JhZGUg
YXR0YWNrIHZlY3RvcnM8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVv
dGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGUgcHJvcG9zYWwgZm9yIDMgaGFz
IHRoaXMgcHJvYmxlbS4gSXQgbGVhZHMgdG8gYSBmYWlsdXJlIHdoZW4gYSBzZXJ2ZXIgZm9yZ2V0
cyB0aGUgYWx0ZXJuYXRpdmUgaW5pdGlhbCBzYWx0cy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0ND
QyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdp
bi1yaWdodDowaW4iPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjYpIFdo
aWxlIHRoZXJlIHdhcyBjbGVhciBXRyBhcHBldGl0ZSBmb3IgKDEpLCBJJ20gbm90IHN1cmUgd2Ug
aGF2ZSBjb25zZW5zdXMgdG8gYnVpbGQgYSBtb3JlIHBvd2VyZnVsIHNvbHV0aW9uIGxpa2UgKDQp
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpw
PiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkg
ZmVhciB0aGF0IHNvbHZpbmcgKDUpIGNvdWxkIHRha2Ugc29tZSB0aW1lLCB3aGljaCB3b3VsZCBk
ZWxheSBRVUlDdjEuIEluc3RlYWQgSSdkIGxpa2UgdG8gcHJvcG9zZSB0aGUgZm9sbG93aW5nIHBs
YW46PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5h
KSB3ZSB0YWtlIHRoZSBzaW1wbGVyIHNvbHV0aW9uICgzKSBhbmQgYWRkIHRoYXQgdG8gdGhlIHNw
ZWM8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPmIp
IHdlIHRha2UgdGhlIG1vcmUgcG93ZXJmdWwvY29tcGxleCBzb2x1dGlvbiAoNSkgYSB0dXJuIGl0
IGludG8gYSBRVUlDIGV4dGVuc2lvbjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGF0IHdvdWxkIGFsbG93IHVzIHRvIHNoaXAgUVVJQ3YxIHdp
dGggc29tZSBsZXZlbCBvZiBvc3NpZmljYXRpb24gbWl0aWdhdGlvbnMgd2l0aG91dCBkZWxheS48
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5BcyBzdGF0ZWQsIHRoZSBwcm9wb3NlZCBzb2x1dGlvbiBmb3Ig
KDQpIGlzIHNpbXBsZXIgdGhhbiAoMyksIGNhbiBiZSB1c2VkIHRvIGltcGxlbWVudCAoMyksIGFu
ZCBhbHNvIHByb3ZpZGVzIGEgc3Ryb25nZXIgcHJvdGVjdGlvbiBmb3Igc2VydmVycyBjZXJ0YWlu
IHRoYXQgdGhleSBjYW4gcmV0YWluIHRoZSB0b2tlbiB1bnByb3RlY3Rpb24ga2V5cy48bzpwPjwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSBhZ3JlZSB0
aGF0IHNvbHZpbmcgKDUpIGZvciBhbGwgcGFydGllcyBtaWdodCBiZSBoYXJkLCBhbmQgdGhhdCB3
ZSBtaWdodCB3YW50IHRvIHB1bnQgdGhhdCB0byB2Mi4gQnV0LCBJIHRoaW5rIHdlIHNob3VsZCBh
ZG9wdCAoNCkgdGhhbiAoMykgZHVlIHRvIHRoZSBhZm9yZW1lbnRpb25lZCByZWFzb25zLjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3Jk
ZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFy
Z2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+VGhvdWdodHM/PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPkRhdmlkPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8
L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGJyIGNs
ZWFyPSJhbGwiPg0KPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPi0tIDxv
OnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkthenVobyBPa3U8bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9o
dG1sPg0K

--_000_BN6PR2201MB1700184D81061E2CBFD77BFBDA620BN6PR2201MB1700_--


From nobody Fri Nov  1 09:35:25 2019
Return-Path: <ximaera@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 52E95120A1D for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 09:35:22 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 zk2rVEweboUH for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 09:35:20 -0700 (PDT)
Received: from mail-yb1-xb2b.google.com (mail-yb1-xb2b.google.com [IPv6:2607:f8b0:4864:20::b2b]) (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 C3092120A08 for <quic@ietf.org>; Fri,  1 Nov 2019 09:35:20 -0700 (PDT)
Received: by mail-yb1-xb2b.google.com with SMTP id g38so3763741ybe.11 for <quic@ietf.org>; Fri, 01 Nov 2019 09:35:20 -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=YQ6hErgG9o9h6FHQQtuwtOhv/cD4WTyAucPFiYfaj84=; b=WV1YR68A5SF2BtnnttDzcvXLWxgNvf987EOw9sXWTYuEDLnPinR73AUiELgXzuUpBT qAN4twXskXQRzYqgBI8kFetxw1+DygqrhgwmAQA5cRVQec32rmswifIhQDmvPo6npXgN So7fecRWHCkrmhgLdiuOajz1t3JtWGpZSl4YrBmd15rE0aQOrd+WfUJ/wVb771r9NsPw vkDWAPH4j9hv48XOKhm1zHWu3jqctnY8RQHjasSBqfafsxY3PRhH5qNk+olBOZTeOiw0 UIzfH7AGjnotI3K1FktrDoF7iYXi5XeI0Y1kZaYBQqcXoHZGKPX7zXaifcB3T1HoskuF nDYg==
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=YQ6hErgG9o9h6FHQQtuwtOhv/cD4WTyAucPFiYfaj84=; b=K3We/zRZZpycbcTqqZeqWyD975EEzTrJCSPgR+MLpAfidNN9sa8CZM/QEkmZbml8P3 fm9+SJgGihpveyyTES1c5wLwMrcCAl1hWJi3O7KM4L5CWl6vGNoD88MqX2KkRAfnOdsP nkfBfOIPyJ1RcJ/GFYTAoaxSM0K3CCBNLH9tmwP6773tzn5FCfWrMJF47e+4TLDBssEj F0VWm2EfJzFhCEAEpBXYO5me6yDnSYS+1K8fei5/jIdJ0yoxA9Ni6hFVj1FA1kLXwmux DDnzZa/aOYfkwv9jJamHuMZDixajD8elDrUbCN+O4cLIj/gW3QG2zw27WBu46luGgnvi dQ3Q==
X-Gm-Message-State: APjAAAVWcTfAHui06ziCHCjFBZOwLWaPwXZHH01Zcl/IOfjzi9M2noaa C5Q8pEZh5eCp3L8JR2tBF3Q2EZ0iLCYmm+paV4E=
X-Google-Smtp-Source: APXvYqwxsau2XkJPjiNgX4Mv6hSCiria/kfh4bhDxGvHscHrMxhB+DdrYe2EYE+fXFUtnRnlzt6r+erTtCWLxUFJPQA=
X-Received: by 2002:a25:14d6:: with SMTP id 205mr9604686ybu.230.1572626119465;  Fri, 01 Nov 2019 09:35:19 -0700 (PDT)
MIME-Version: 1.0
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com> <CALZ3u+YyOQxA5zBxkhDj9-wObfqjxPxPyXH9PumaW79DNkKjsg@mail.gmail.com> <6ab3b6d6-7638-4b96-b2a3-4212f747a7af.anqing.aq@alibaba-inc.com> <CALZ3u+ZaHzbNEzUsUa2bYXy2eB+fgkyzSDQir_mtTyLrrcAm7A@mail.gmail.com> <cee17fee-fed3-497b-82fc-5deda3d0f565.anqing.aq@alibaba-inc.com>
In-Reply-To: <cee17fee-fed3-497b-82fc-5deda3d0f565.anqing.aq@alibaba-inc.com>
From: =?UTF-8?Q?T=C3=B6ma_Gavrichenkov?= <ximaera@gmail.com>
Date: Fri, 1 Nov 2019 19:35:05 +0300
Message-ID: <CALZ3u+ZdOrdAJXDEemsemEuikdfeEWkeBfYhPW1CfwFsn-Ahzg@mail.gmail.com>
Subject: Re: Re: Fast Address Validation - about
To: Qing An <anqing.aq@alibaba-inc.com>
Cc: IETF QUIC WG <quic@ietf.org>, "jri.ietf" <jri.ietf@gmail.com>, mt <mt@lowentropy.net>, Max <max.ldp@alibaba-inc.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/nnf-UtEzCKbL4N2YmA6gD_If9Gw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 16:35:22 -0000

On Fri, Nov 1, 2019 at 5:47 PM Qing An <anqing.aq@alibaba-inc.com> wrote:
> For initial flood, there are approaches like
> source address statistics

This is a very rough and biased method at best.  Generally (which
would be IMNSHO 98% of the cases), the statistics about past events
doesn't tell you with an accuracy anywhere close to being reliable if
this particular new packet could be from spoofed source or not.

E.g. an attacker who would generate spoofed packets from the typical
source addresses for your type of business in your country (e.g.
popular cellular NAT pools for news sites) would circumvent that check
easily.  With the overwhelming majority of HTTPS resources there's
hardly any point in giving the latter a shot.

> and speed limitation.

And you'll be limiting the speed for legitimate clients as well in the
above example (and many other scenarios).  This is a nice way to
amplify the effects of an attack, much less to handle those.

***

With the greatest of respect, speaking more broadly, please take into
account that a good engineering practice (no matter if it's Internet
engineering or whatever) must not rely on the assumption that
something which is perceived as typical would always happen, and
something perceived as non-typical would never occur just because it
has to date never occurred in the past.

The example commonly seen in university books on engineering would be
e.g. the Oppau explosion =E2=80=94 caused by the factory workers tearing
through ammonium with dynamite, just because ammonium has never
detonated during that operation before and was thus believed to be
unlikely to explode in future.  An example more close to the content
of this WG would be middlebox vendors hard-coding "typical" protocol
behaviour into their products (causing transport protocol ossification
which the WG spends I believe no less than 50% of time fighting
against) just because the said vendors do not appear to see the
standard but non-typical behaviour in their sample network dumps.

Both approaches you propose are vulnerable to a few simple
circumvention techniques, and while I totally accept that probably
you've never seen those techniques applied against your network, they
are quite extensively documented.  Therefore it's hard to see, at
least for me, why the IETF should account for the flawed mitigation
approaches during the transport protocol design.

--
T=C3=B6ma


From nobody Fri Nov  1 10:34:39 2019
Return-Path: <ximaera@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 DA2BA120977; Fri,  1 Nov 2019 10:34:33 -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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 ggBlj-ilEa90; Fri,  1 Nov 2019 10:34:31 -0700 (PDT)
Received: from mail-yb1-xb30.google.com (mail-yb1-xb30.google.com [IPv6:2607:f8b0:4864:20::b30]) (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 23F35120806; Fri,  1 Nov 2019 10:34:30 -0700 (PDT)
Received: by mail-yb1-xb30.google.com with SMTP id h202so4163390ybg.13; Fri, 01 Nov 2019 10:34: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=5opmrgYkbqGZ2ml6fbH5rdCed55on1iNqz6dEpbamf8=; b=laRf5Pdm95Z59V99yfWtKnFVnf5ljfRg2hR4l/Dqxqv7v/bZL4CKf2QHzy2Y4kIqNf qPAQfEBX//jdSY0ClOuhDYQv1UZy3tt+5UQJKKfBB+T/SCjkm55Gw4I9keZmIAC0dY8H pFkwDW+1dBNzhN0vlbShouiFK5Kky26jpFgde47RzGuLrbfjLqX4rxlaT+a1OpcftDnY XhUodPh+T8W9mylJHhYEqWekIs/49s3J/um6CfRoDoQVbPu/lXrrUi3+e0Eumwz9g128 6iFTHpekl2csf5yHzc5P1GT8Kw7y4Zab65Z65VKk12cje4TuSF+aIRSRvfoJQnYRgRp8 hfrg==
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=5opmrgYkbqGZ2ml6fbH5rdCed55on1iNqz6dEpbamf8=; b=AYOb/drAq7Fmb5fDdKXmUNGFAVbXYGyMSvGSdixhsUA0wLNQc4N3qNN4XD8zLlZ9kE +a1KiprQS/w1lABw0gi+beBw83r4/mCJSEEumUr/+dgps9ay4i8T2fAfbxbgg3xcgEEN HsgYZ1GGJTKdDPrbJmCC6xC4J+5ibmzVDZCOl/rfIa6GSlSPII2Q5Ys6HRHN7Lt0j3HD YRNfGvsspy2Y1oxvhissWa0wkOboNZBnHb22iRi3/eEOSgJtXNtuFgBki3r2RoqwISAz lW+Rb5JZzYfkFf018Pw8hJ17CRVew018rC9CXtgCE0G2dCTUFYF70nfNFJ35wWrRIzNN y8gQ==
X-Gm-Message-State: APjAAAXnlKkw930rm3zzdxooItJDuQ3QMyaoM+G1/omgH7D7zgJZiq4u UV66YJW2H9gQ4XBQb6kBRL5Xb3av0T68jC60GNo=
X-Google-Smtp-Source: APXvYqwwUnbDyR+igFsgcAoddWFU6+u6qnEzxPtMUx+q7iQE15zkiZSfiXTedT48O+Qy9vn+SA7WgdqAIsgVETnjTGo=
X-Received: by 2002:a25:db46:: with SMTP id g67mr9967797ybf.312.1572629668813;  Fri, 01 Nov 2019 10:34:28 -0700 (PDT)
MIME-Version: 1.0
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com> <BN6PR2201MB1700F72F3DC8F6C3CF79902CDA600@BN6PR2201MB1700.namprd22.prod.outlook.com> <bd15f357-8e7a-42af-bf28-79f7177da385@www.fastmail.com> <f55efb80-1a95-4190-84e5-b81948a7f081.anqing.aq@alibaba-inc.com> <BN6PR2201MB17005571E88F1C68769091A3DA630@BN6PR2201MB1700.namprd22.prod.outlook.com> <69d1a917-b1f9-4142-afb0-f5c67abe7334.anqing.aq@alibaba-inc.com>
In-Reply-To: <69d1a917-b1f9-4142-afb0-f5c67abe7334.anqing.aq@alibaba-inc.com>
From: =?UTF-8?Q?T=C3=B6ma_Gavrichenkov?= <ximaera@gmail.com>
Date: Fri, 1 Nov 2019 20:34:14 +0300
Message-ID: <CALZ3u+YDo7jTJzZj=W45s0zyJoun_+1gMkq7oMVM+DNRnyDZRg@mail.gmail.com>
Subject: Re: Fast Address Validation - about
To: Qing An <anqing.aq@alibaba-inc.com>
Cc: QUIC <quic-bounces@ietf.org>, quic <quic@ietf.org>,  "jri.ietf" <jri.ietf@gmail.com>, mt <mt@lowentropy.net>, mikkelfj <mikkelfj@gmail.com>,  =?UTF-8?B?5YiY5aSn6bmPKOm5j+aIkCk=?= <max.ldp@alibaba-inc.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/J2s9ap1Mab1A-I4f0YdEA_Ob5kw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 17:34:34 -0000

Peace,

On Fri, Nov 1, 2019 at 3:37 PM Qing An <anqing.aq@alibaba-inc.com> wrote:
> I submitted the draft, https://datatracker.ietf.org/doc/draft-an-fast-add=
ress-validation/

A quick review goes below:

> The server remembers the value it sends to
> clients and validates the token sent back from a client.

As discussed before, this description of the Retry mechanism is
inaccurate to the point it defeats its very purpose.

> Address validation is used by QUIC to avoid being used for a traffic
> amplification attack.

This is also inaccurate; the lower bound for the Initial packet size
prevents amplification.  Retry token is there to mitigate Initial
packet floods.  Neither prevent trivial reflection, if you will.

> If server chooses to
> accept the cost brought by token exchanging in Handshake
> [..]
> Adding token field to Handshake packet does not add new security
> concerns.

At least one security concern I see here is what data the server is
expected to derive its decision to accept the cost from.

E.g. with the aforementioned 300 Mpps Initial packet flood, what is
the approximate cost of keeping the state, per second?  If you would
just be storing 16 octets of an IPv6 address plus 2 octets of the
client's ephemeral port for any Rx packet, that'd be more than 5
Gbytes of RAM consumed *per second* of the attack, not including the
pointers, hashes etc.  Next, I haven't exactly done the math, but I
think that the draft implies that the state kept would be hardly less
than an order of magnitude bigger than that.  Also, the cost of
processing every spoofed packet through the whole handshake pipeline,
and so on.  I believe this is where the authors need to come up with
benchmarks and implementation hints on garbage collection methods etc.

I know the amount of RAM available is destined to grow but the floods
are not expected to shrink any time soon just as well.

--
T=C3=B6ma


From nobody Fri Nov  1 14:36:33 2019
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 A9DD3120801 for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 14:36:31 -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_HELO_NONE=0.001, 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 MMB1Z-eLqJxW for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 14:36:29 -0700 (PDT)
Received: from mail-lj1-x232.google.com (mail-lj1-x232.google.com [IPv6:2a00:1450:4864:20::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 1ABF5120013 for <quic@ietf.org>; Fri,  1 Nov 2019 14:36:29 -0700 (PDT)
Received: by mail-lj1-x232.google.com with SMTP id t5so11648694ljk.0 for <quic@ietf.org>; Fri, 01 Nov 2019 14:36: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=SeF7vH+PwKur7F2PnltFq9BpTNfQrY8fxrK7Vw8AyuU=; b=W92edBF2kIPrpPsCudFc+3nw6sGnnTX3mWXJsN7AdIcots+Rf2aiA7T8rkS0MW8iD3 fvFIyrBFzB82+MGimjR60+c79oNDpxL+Zv5TzJjidd57TksO8UZBkNrfUzzqZI0VAEBo x006XvZ2m9WLUsv5PLmyca0NWNgXR7b52RKcHr+PEtKaek0KVxTmjl7dGRBa3ymmoz28 4tOdP/FR5mRzdHN41HXM6uX6nm7vs7Qa3PWzk9REKu9H4v+gWe5Ua2fTEsTQhKKXa68s pZ8jU5CzCfo8o51Dw/pAkCkomKwHQwjii1XPitxtt+7lRjIJRCgDlHcYBpAeuu6QFWpK J9rg==
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=SeF7vH+PwKur7F2PnltFq9BpTNfQrY8fxrK7Vw8AyuU=; b=j2BuXB9cgzkQBpSl7ud0PEWdMnarYyjPWsmEemyjOVwKYGBIXYD/tHnAzLSj3ultIy 2qoCWUUAjwH+GXxcLBCLZBA8RRE6jqF+77o0BfVH8U/UYz3PdMjBTuFORGxk2qX4Ai6P Q1S2mT9CYezVCCHIejySk3U3x2yr4WyhBDmK3FZVxB+OGXrcAsTfjxwLwQhhyJMLbe7s c2076u1JKzIikevkcOgVK1YgD80l8xuT1+KbcF/kVJ2jRFPu/L1NS7oWlAkBVWehsREB iwj7M0UCnA41/rnp74pAQwY14OpxcCC7uEot5ntXh8yOShrj4YYSQBetjkNFKKTT4MdQ co4w==
X-Gm-Message-State: APjAAAVIoPxG0LHhhOP5vyn7lXH6sHiGh/yto2D/wk1maoJvq5sKWIxS Cs9OxeGimlhv+VPT8LwEI9l4+AXFMXoWF149lCY=
X-Google-Smtp-Source: APXvYqwbM1Tk8sVIIwFOYszcZx6tuzr/V2+bTFqmi6VfDTKkLXVYVQlsoCMAKCKkrMYOh/Yuep3i3TaDvUSSmes4+aY=
X-Received: by 2002:a2e:9954:: with SMTP id r20mr7308872ljj.197.1572644187328;  Fri, 01 Nov 2019 14:36:27 -0700 (PDT)
MIME-Version: 1.0
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com> <BN6PR2201MB1700F72F3DC8F6C3CF79902CDA600@BN6PR2201MB1700.namprd22.prod.outlook.com> <bd15f357-8e7a-42af-bf28-79f7177da385@www.fastmail.com> <f55efb80-1a95-4190-84e5-b81948a7f081.anqing.aq@alibaba-inc.com> <BN6PR2201MB17005571E88F1C68769091A3DA630@BN6PR2201MB1700.namprd22.prod.outlook.com> <69d1a917-b1f9-4142-afb0-f5c67abe7334.anqing.aq@alibaba-inc.com> <CALZ3u+YDo7jTJzZj=W45s0zyJoun_+1gMkq7oMVM+DNRnyDZRg@mail.gmail.com>
In-Reply-To: <CALZ3u+YDo7jTJzZj=W45s0zyJoun_+1gMkq7oMVM+DNRnyDZRg@mail.gmail.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Fri, 1 Nov 2019 14:36:16 -0700
Message-ID: <CACpbDce7EU+9gTkyBnvLqinLQST42ch=SRUJe6N9ZraiakkGzw@mail.gmail.com>
Subject: Re: Fast Address Validation - about
To: Qing An <anqing.aq@alibaba-inc.com>
Cc: quic <quic@ietf.org>, =?UTF-8?B?5YiY5aSn6bmPKOm5j+aIkCk=?= <max.ldp@alibaba-inc.com>
Content-Type: multipart/alternative; boundary="00000000000024d54605964fc2ad"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/HwmAkOw5TDH6jrF_CDPXWnHPMVA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 21:36:32 -0000

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

Qing,

Thank you for writing up the draft.

As several others have noted, the RTT spent with Retry is not unnecessary,
it is fundamental to the purpose of Retry. If the server is willing to
maintain state, it doesn't need to send a Retry packet at all. If the
server is willing to maintain state and therefore does not send a Retry at
all, what is the value of your proposal?

- jana

On Fri, Nov 1, 2019 at 10:34 AM T=C3=B6ma Gavrichenkov <ximaera@gmail.com> =
wrote:

> Peace,
>
> On Fri, Nov 1, 2019 at 3:37 PM Qing An <anqing.aq@alibaba-inc.com> wrote:
> > I submitted the draft,
> https://datatracker.ietf.org/doc/draft-an-fast-address-validation/
>
> A quick review goes below:
>
> > The server remembers the value it sends to
> > clients and validates the token sent back from a client.
>
> As discussed before, this description of the Retry mechanism is
> inaccurate to the point it defeats its very purpose.
>
> > Address validation is used by QUIC to avoid being used for a traffic
> > amplification attack.
>
> This is also inaccurate; the lower bound for the Initial packet size
> prevents amplification.  Retry token is there to mitigate Initial
> packet floods.  Neither prevent trivial reflection, if you will.
>
> > If server chooses to
> > accept the cost brought by token exchanging in Handshake
> > [..]
> > Adding token field to Handshake packet does not add new security
> > concerns.
>
> At least one security concern I see here is what data the server is
> expected to derive its decision to accept the cost from.
>
> E.g. with the aforementioned 300 Mpps Initial packet flood, what is
> the approximate cost of keeping the state, per second?  If you would
> just be storing 16 octets of an IPv6 address plus 2 octets of the
> client's ephemeral port for any Rx packet, that'd be more than 5
> Gbytes of RAM consumed *per second* of the attack, not including the
> pointers, hashes etc.  Next, I haven't exactly done the math, but I
> think that the draft implies that the state kept would be hardly less
> than an order of magnitude bigger than that.  Also, the cost of
> processing every spoofed packet through the whole handshake pipeline,
> and so on.  I believe this is where the authors need to come up with
> benchmarks and implementation hints on garbage collection methods etc.
>
> I know the amount of RAM available is destined to grow but the floods
> are not expected to shrink any time soon just as well.
>
> --
> T=C3=B6ma
>

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

<div dir=3D"ltr">Qing,<div><br></div><div>Thank you for writing up the draf=
t.</div><div><br></div><div>As several others have noted, the RTT spent wit=
h Retry is not unnecessary, it is fundamental to the purpose of Retry. If t=
he server is willing to maintain state, it doesn&#39;t need to send a Retry=
 packet at all. If the server is willing to maintain state and therefore do=
es not send a Retry at all, what is the value of your proposal?</div><div><=
br></div><div>- jana</div></div><br><div class=3D"gmail_quote"><div dir=3D"=
ltr" class=3D"gmail_attr">On Fri, Nov 1, 2019 at 10:34 AM T=C3=B6ma Gavrich=
enkov &lt;<a href=3D"mailto:ximaera@gmail.com">ximaera@gmail.com</a>&gt; wr=
ote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px=
 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Peace,<br>
<br>
On Fri, Nov 1, 2019 at 3:37 PM Qing An &lt;<a href=3D"mailto:anqing.aq@alib=
aba-inc.com" target=3D"_blank">anqing.aq@alibaba-inc.com</a>&gt; wrote:<br>
&gt; I submitted the draft, <a href=3D"https://datatracker.ietf.org/doc/dra=
ft-an-fast-address-validation/" rel=3D"noreferrer" target=3D"_blank">https:=
//datatracker.ietf.org/doc/draft-an-fast-address-validation/</a><br>
<br>
A quick review goes below:<br>
<br>
&gt; The server remembers the value it sends to<br>
&gt; clients and validates the token sent back from a client.<br>
<br>
As discussed before, this description of the Retry mechanism is<br>
inaccurate to the point it defeats its very purpose.<br>
<br>
&gt; Address validation is used by QUIC to avoid being used for a traffic<b=
r>
&gt; amplification attack.<br>
<br>
This is also inaccurate; the lower bound for the Initial packet size<br>
prevents amplification.=C2=A0 Retry token is there to mitigate Initial<br>
packet floods.=C2=A0 Neither prevent trivial reflection, if you will.<br>
<br>
&gt; If server chooses to<br>
&gt; accept the cost brought by token exchanging in Handshake<br>
&gt; [..]<br>
&gt; Adding token field to Handshake packet does not add new security<br>
&gt; concerns.<br>
<br>
At least one security concern I see here is what data the server is<br>
expected to derive its decision to accept the cost from.<br>
<br>
E.g. with the aforementioned 300 Mpps Initial packet flood, what is<br>
the approximate cost of keeping the state, per second?=C2=A0 If you would<b=
r>
just be storing 16 octets of an IPv6 address plus 2 octets of the<br>
client&#39;s ephemeral port for any Rx packet, that&#39;d be more than 5<br=
>
Gbytes of RAM consumed *per second* of the attack, not including the<br>
pointers, hashes etc.=C2=A0 Next, I haven&#39;t exactly done the math, but =
I<br>
think that the draft implies that the state kept would be hardly less<br>
than an order of magnitude bigger than that.=C2=A0 Also, the cost of<br>
processing every spoofed packet through the whole handshake pipeline,<br>
and so on.=C2=A0 I believe this is where the authors need to come up with<b=
r>
benchmarks and implementation hints on garbage collection methods etc.<br>
<br>
I know the amount of RAM available is destined to grow but the floods<br>
are not expected to shrink any time soon just as well.<br>
<br>
--<br>
T=C3=B6ma<br>
</blockquote></div>

--00000000000024d54605964fc2ad--


From nobody Fri Nov  1 15:06:01 2019
Return-Path: <anqing.aq@alibaba-inc.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 BD45112082F; Fri,  1 Nov 2019 15:05:59 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 (1024-bit key) header.d=alibaba-inc.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 2BMvgBwOQ_4H; Fri,  1 Nov 2019 15:05:58 -0700 (PDT)
Received: from out0-141.mail.aliyun.com (out0-141.mail.aliyun.com [140.205.0.141]) (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 7AC8C120130; Fri,  1 Nov 2019 15:05:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1572645953; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=bkc4MJUWIscKYcAFCxN5kz1SiyPBTHp47WgxaAPdM4Y=; b=lvxjPgR4YPkpIYcqEeXdvqkKeAMi8FE2ZbBlrjfYdDeH7ATCVJDZfPI257AquwxaAx6RUIkhC3Z9bKW3wWolBgUdwaBDRSrSpSRZb8COBvc65iHhgteTVOatTohaVQffO3uXtlWex8h2eOL0+IXKE8RokoF9NoHgdLVIk2AZVmM=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R201e4; CH=green; DM=||false|; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e01l07447; MF=anqing.aq@alibaba-inc.com; NM=1; PH=DW; RN=7; SR=0; TI=alimail_ios_2.COREAPIfd5945c8d5e34b12a52862035679252f; 
Received: from WS-web (anqing.aq@alibaba-inc.com[alimail_ios_2.COREAPIfd5945c8d5e34b12a52862035679252f]) by e01l07404.eu6 at Sat, 02 Nov 2019 06:05:51 +0800
Date: Sat, 02 Nov 2019 06:05:51 +0800
From: "Qing An" <anqing.aq@alibaba-inc.com>
To: "=?UTF-8?B?VMO2bWEgR2F2cmljaGVua292?=" <ximaera@gmail.com>
Cc: "QUIC" <quic-bounces@ietf.org>, "quic" <quic@ietf.org>, "jri.ietf" <jri.ietf@gmail.com>, "mt" <mt@lowentropy.net>, "mikkelfj" <mikkelfj@gmail.com>, "=?UTF-8?B?5YiY5aSn6bmPKOm5j+aIkCk=?=" <max.ldp@alibaba-inc.com>
Message-ID: <4985b277-e390-4187-836b-0a13ad885c88.anqing.aq@alibaba-inc.com>
Subject: =?UTF-8?B?UmU6UmU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQ=?=
X-Priority: 3
X-Mailer: [Alimail-Mailagent revision 2765257]
MIME-Version: 1.0
In-Reply-To: <CALZ3u+YDo7jTJzZj=W45s0zyJoun_+1gMkq7oMVM+DNRnyDZRg@mail.gmail.com>
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com> <BN6PR2201MB1700F72F3DC8F6C3CF79902CDA600@BN6PR2201MB1700.namprd22.prod.outlook.com> <bd15f357-8e7a-42af-bf28-79f7177da385@www.fastmail.com> <f55efb80-1a95-4190-84e5-b81948a7f081.anqing.aq@alibaba-inc.com> <BN6PR2201MB17005571E88F1C68769091A3DA630@BN6PR2201MB1700.namprd22.prod.outlook.com> <69d1a917-b1f9-4142-afb0-f5c67abe7334.anqing.aq@alibaba-inc.com>, <CALZ3u+YDo7jTJzZj=W45s0zyJoun_+1gMkq7oMVM+DNRnyDZRg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_34679_46023940_5dbcac3f_3581ee"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/QNvB36BX-w481kZsOO-WEL1tPSo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 22:06:00 -0000

------=ALIBOUNDARY_34679_46023940_5dbcac3f_3581ee
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

ClRoYW5rcyBmb3IgdGhlIGVsYWJvcmF0ZSBleHBsYW5hdGlvbi4KClRoZSBzZWN1cml0eSAmIHBy
aXZhY3kgYXBwcm9hY2hlcyBJIGxpc3RlZCBhcmUganVzdCBzb21lIGV4YW1wbGVzLiBJbiB0b2Rh
eeKAmXMgbmV0d29yaywgaXQgd291bGQgYmUgaGFyZCB0byBkZWZlbmQgdGhvc2UgYXR0YWNrcyB5
b3UgbWVudGlvbmVkIGp1c3QgcmVseWluZyBvbmUgc3BlY2lmaWMgYXBwcm9hY2guIEhvdyB0byBw
cmV2ZW50IHRob3NlIGF0dGFja3MgbWF5IGJlIGEgYnJvYWRlciBzdG9yeSwgbm90IGp1c3Qgc3Bl
Y2lmaWMgdG8gUVVJQy4KCkFuZCBiYXNlZCBvbiB0aGUgbXkgY29tcGFueeKAmXMgZGVwbG95bWVu
dCBleHBlcmllbmNlLCBmb3JjaW5nIHRvIHVzZSBSZXRyeSBmb3IgYWRkcmVzcyB2YWxpZGF0aW9u
IGRvZXMgY2F1c2Ugc29tZSBleHBlcmllbmNlIGZsYXcgaW4gY2xpZW50IHNpZGUuIFRoZXJlZm9y
ZSwgaXQgaXMgcmVjb21tZW5kZWQgdG8gYWxsb3cgYW4gYXBwcm9hY2ggdGhhdCBjYW4gYWNjZWxl
cmF0ZSB0aGUgZmlyc3QgY29ubmVjdGlvbiBlc3RhYmxpc2htZW50LgoKUWluZwoKCgogLS0tLS0t
LS0tLS0tLS0tLS0tT3JpZ2luYWwgTWFpbCAtLS0tLS0tLS0tLS0tLS0tLS0KU2VuZGVyOlTDtm1h
IEdhdnJpY2hlbmtvdiA8eGltYWVyYUBnbWFpbC5jb20+ClNlbmQgRGF0ZTpTYXQgTm92IDIgMDE6
MzQ6MzEgMjAxOQpSZWNpcGllbnRzOlFpbmcgQW4gPGFucWluZy5hcUBhbGliYWJhLWluYy5jb20+
CkNDOlFVSUMgPHF1aWMtYm91bmNlc0BpZXRmLm9yZz4sIHF1aWMgPHF1aWNAaWV0Zi5vcmc+LCBq
cmkuaWV0ZiA8anJpLmlldGZAZ21haWwuY29tPiwgbXQgPG10QGxvd2VudHJvcHkubmV0PiwgbWlr
a2VsZmogPG1pa2tlbGZqQGdtYWlsLmNvbT4sIOWImOWkp+m5jyjpuY/miJApIDxtYXgubGRwQGFs
aWJhYmEtaW5jLmNvbT4KU3ViamVjdDpSZTogRmFzdCBBZGRyZXNzIFZhbGlkYXRpb24gLSBhYm91
dApQZWFjZSwKCk9uIEZyaSwgTm92IDEsIDIwMTkgYXQgMzozNyBQTSBRaW5nIEFuIDxhbnFpbmcu
YXFAYWxpYmFiYS1pbmMuY29tPiB3cm90ZToKPiBJIHN1Ym1pdHRlZCB0aGUgZHJhZnQsIGh0dHBz
Oi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWFuLWZhc3QtYWRkcmVzcy12YWxpZGF0
aW9uLwoKQSBxdWljayByZXZpZXcgZ29lcyBiZWxvdzoKCj4gVGhlIHNlcnZlciByZW1lbWJlcnMg
dGhlIHZhbHVlIGl0IHNlbmRzIHRvCj4gY2xpZW50cyBhbmQgdmFsaWRhdGVzIHRoZSB0b2tlbiBz
ZW50IGJhY2sgZnJvbSBhIGNsaWVudC4KCkFzIGRpc2N1c3NlZCBiZWZvcmUsIHRoaXMgZGVzY3Jp
cHRpb24gb2YgdGhlIFJldHJ5IG1lY2hhbmlzbSBpcwppbmFjY3VyYXRlIHRvIHRoZSBwb2ludCBp
dCBkZWZlYXRzIGl0cyB2ZXJ5IHB1cnBvc2UuCgo+IEFkZHJlc3MgdmFsaWRhdGlvbiBpcyB1c2Vk
IGJ5IFFVSUMgdG8gYXZvaWQgYmVpbmcgdXNlZCBmb3IgYSB0cmFmZmljCj4gYW1wbGlmaWNhdGlv
biBhdHRhY2suCgpUaGlzIGlzIGFsc28gaW5hY2N1cmF0ZTsgdGhlIGxvd2VyIGJvdW5kIGZvciB0
aGUgSW5pdGlhbCBwYWNrZXQgc2l6ZQpwcmV2ZW50cyBhbXBsaWZpY2F0aW9uLiAgUmV0cnkgdG9r
ZW4gaXMgdGhlcmUgdG8gbWl0aWdhdGUgSW5pdGlhbApwYWNrZXQgZmxvb2RzLiAgTmVpdGhlciBw
cmV2ZW50IHRyaXZpYWwgcmVmbGVjdGlvbiwgaWYgeW91IHdpbGwuCgo+IElmIHNlcnZlciBjaG9v
c2VzIHRvCj4gYWNjZXB0IHRoZSBjb3N0IGJyb3VnaHQgYnkgdG9rZW4gZXhjaGFuZ2luZyBpbiBI
YW5kc2hha2UKPiBbLi5dCj4gQWRkaW5nIHRva2VuIGZpZWxkIHRvIEhhbmRzaGFrZSBwYWNrZXQg
ZG9lcyBub3QgYWRkIG5ldyBzZWN1cml0eQo+IGNvbmNlcm5zLgoKQXQgbGVhc3Qgb25lIHNlY3Vy
aXR5IGNvbmNlcm4gSSBzZWUgaGVyZSBpcyB3aGF0IGRhdGEgdGhlIHNlcnZlciBpcwpleHBlY3Rl
ZCB0byBkZXJpdmUgaXRzIGRlY2lzaW9uIHRvIGFjY2VwdCB0aGUgY29zdCBmcm9tLgoKRS5nLiB3
aXRoIHRoZSBhZm9yZW1lbnRpb25lZCAzMDAgTXBwcyBJbml0aWFsIHBhY2tldCBmbG9vZCwgd2hh
dCBpcwp0aGUgYXBwcm94aW1hdGUgY29zdCBvZiBrZWVwaW5nIHRoZSBzdGF0ZSwgcGVyIHNlY29u
ZD8gIElmIHlvdSB3b3VsZApqdXN0IGJlIHN0b3JpbmcgMTYgb2N0ZXRzIG9mIGFuIElQdjYgYWRk
cmVzcyBwbHVzIDIgb2N0ZXRzIG9mIHRoZQpjbGllbnQncyBlcGhlbWVyYWwgcG9ydCBmb3IgYW55
IFJ4IHBhY2tldCwgdGhhdCdkIGJlIG1vcmUgdGhhbiA1CkdieXRlcyBvZiBSQU0gY29uc3VtZWQg
KnBlciBzZWNvbmQqIG9mIHRoZSBhdHRhY2ssIG5vdCBpbmNsdWRpbmcgdGhlCnBvaW50ZXJzLCBo
YXNoZXMgZXRjLiAgTmV4dCwgSSBoYXZlbid0IGV4YWN0bHkgZG9uZSB0aGUgbWF0aCwgYnV0IEkK
dGhpbmsgdGhhdCB0aGUgZHJhZnQgaW1wbGllcyB0aGF0IHRoZSBzdGF0ZSBrZXB0IHdvdWxkIGJl
IGhhcmRseSBsZXNzCnRoYW4gYW4gb3JkZXIgb2YgbWFnbml0dWRlIGJpZ2dlciB0aGFuIHRoYXQu
ICBBbHNvLCB0aGUgY29zdCBvZgpwcm9jZXNzaW5nIGV2ZXJ5IHNwb29mZWQgcGFja2V0IHRocm91
Z2ggdGhlIHdob2xlIGhhbmRzaGFrZSBwaXBlbGluZSwKYW5kIHNvIG9uLiAgSSBiZWxpZXZlIHRo
aXMgaXMgd2hlcmUgdGhlIGF1dGhvcnMgbmVlZCB0byBjb21lIHVwIHdpdGgKYmVuY2htYXJrcyBh
bmQgaW1wbGVtZW50YXRpb24gaGludHMgb24gZ2FyYmFnZSBjb2xsZWN0aW9uIG1ldGhvZHMgZXRj
LgoKSSBrbm93IHRoZSBhbW91bnQgb2YgUkFNIGF2YWlsYWJsZSBpcyBkZXN0aW5lZCB0byBncm93
IGJ1dCB0aGUgZmxvb2RzCmFyZSBub3QgZXhwZWN0ZWQgdG8gc2hyaW5rIGFueSB0aW1lIHNvb24g
anVzdCBhcyB3ZWxsLgoKLS0KVMO2bWE=
------=ALIBOUNDARY_34679_46023940_5dbcac3f_3581ee
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64

PGRpdiBpZD0ibWFpbGJveC1jb252ZXJzYXRpb24iPjxkaXY+PGJyPjwvZGl2PjxkaXY+VGhhbmtz
IGZvciB0aGUgZWxhYm9yYXRlIGV4cGxhbmF0aW9uLjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+
VGhlIHNlY3VyaXR5ICZhbXA7IHByaXZhY3kgYXBwcm9hY2hlcyBJIGxpc3RlZCBhcmUganVzdCBz
b21lIGV4YW1wbGVzLiBJbiB0b2RheeKAmXMgbmV0d29yaywgaXQgd291bGQgYmUgaGFyZCB0byBk
ZWZlbmQgdGhvc2UgYXR0YWNrcyB5b3UgbWVudGlvbmVkIGp1c3QgcmVseWluZyBvbmUgc3BlY2lm
aWMgYXBwcm9hY2guIEhvdyB0byBwcmV2ZW50IHRob3NlIGF0dGFja3MgbWF5IGJlIGEgYnJvYWRl
ciBzdG9yeSwgbm90IGp1c3Qgc3BlY2lmaWMgdG8gUVVJQy48L2Rpdj48ZGl2Pjxicj48L2Rpdj48
ZGl2PkFuZCBiYXNlZCBvbiB0aGUgbXkgY29tcGFueeKAmXMgZGVwbG95bWVudCBleHBlcmllbmNl
LCBmb3JjaW5nIHRvIHVzZSBSZXRyeSBmb3IgYWRkcmVzcyB2YWxpZGF0aW9uIGRvZXMgY2F1c2Ug
c29tZSBleHBlcmllbmNlIGZsYXcgaW4gY2xpZW50IHNpZGUuIFRoZXJlZm9yZSwgaXQgaXMgcmVj
b21tZW5kZWQgdG8gYWxsb3cgYW4gYXBwcm9hY2ggdGhhdCBjYW4gYWNjZWxlcmF0ZSB0aGUgZmly
c3QgY29ubmVjdGlvbiBlc3RhYmxpc2htZW50LjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+UWlu
ZzwvZGl2PjxkaXY+PGJyPjwvZGl2PjxkaXY+PGJyPjwvZGl2PjxibG9ja3F1b3RlPjxkaXY+PGRp
diBzdHlsZT0iZm9udC1zaXplOiA3MCUiPiAtLS0tLS0tLS0tLS0tLS0tLS1PcmlnaW5hbCBNYWls
IC0tLS0tLS0tLS0tLS0tLS0tLTwvZGl2PjxkaXY+PHNwYW4gY2xhc3M9ImZvcndhcmQtaGVhZGVy
LXRpdGxlIj5TZW5kZXI6PC9zcGFuPlTDtm1hIEdhdnJpY2hlbmtvdiAmbHQ7eGltYWVyYUBnbWFp
bC5jb20mZ3Q7PC9kaXY+PGRpdj48c3BhbiBjbGFzcz0iZm9yd2FyZC1oZWFkZXItdGl0bGUiPlNl
bmQgRGF0ZTo8L3NwYW4+U2F0IE5vdiAgMiAwMTozNDozMSAyMDE5PC9kaXY+PGRpdj48c3BhbiBj
bGFzcz0iZm9yd2FyZC1oZWFkZXItdGl0bGUiPlJlY2lwaWVudHM6PC9zcGFuPlFpbmcgQW4gJmx0
O2FucWluZy5hcUBhbGliYWJhLWluYy5jb20mZ3Q7PC9kaXY+PGRpdj48c3BhbiBjbGFzcz0iZm9y
d2FyZC1oZWFkZXItdGl0bGUiPkNDOjwvc3Bhbj5RVUlDICZsdDtxdWljLWJvdW5jZXNAaWV0Zi5v
cmcmZ3Q7LCBxdWljICZsdDtxdWljQGlldGYub3JnJmd0OywganJpLmlldGYgJmx0O2pyaS5pZXRm
QGdtYWlsLmNvbSZndDssIG10ICZsdDttdEBsb3dlbnRyb3B5Lm5ldCZndDssIG1pa2tlbGZqICZs
dDttaWtrZWxmakBnbWFpbC5jb20mZ3Q7LCDliJjlpKfpuY8o6bmP5oiQKSAmbHQ7bWF4LmxkcEBh
bGliYWJhLWluYy5jb20mZ3Q7PC9kaXY+PGRpdj48c3BhbiBjbGFzcz0iZm9yd2FyZC1oZWFkZXIt
dGl0bGUiPlN1YmplY3Q6PC9zcGFuPlJlOiBGYXN0IEFkZHJlc3MgVmFsaWRhdGlvbiAtIGFib3V0
PC9kaXY+PC9kaXY+PGRpdj48YmxvY2txdW90ZSBjbGFzcz0iZ21haWxfcXVvdGUiPlBlYWNlLDxi
cj48YnI+T24mbmJzcDtGcmksJm5ic3A7Tm92Jm5ic3A7MSwmbmJzcDsyMDE5Jm5ic3A7YXQmbmJz
cDszOjM3Jm5ic3A7UE0mbmJzcDtRaW5nJm5ic3A7QW4mbmJzcDsmbHQ7YW5xaW5nLmFxQGFsaWJh
YmEtaW5jLmNvbSZndDsmbmJzcDt3cm90ZTo8YnI+Jmd0OyZuYnNwO0kmbmJzcDtzdWJtaXR0ZWQm
bmJzcDt0aGUmbmJzcDtkcmFmdCwmbmJzcDtodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2Rv
Yy9kcmFmdC1hbi1mYXN0LWFkZHJlc3MtdmFsaWRhdGlvbi88YnI+PGJyPkEmbmJzcDtxdWljayZu
YnNwO3JldmlldyZuYnNwO2dvZXMmbmJzcDtiZWxvdzo8YnI+PGJyPiZndDsmbmJzcDtUaGUmbmJz
cDtzZXJ2ZXImbmJzcDtyZW1lbWJlcnMmbmJzcDt0aGUmbmJzcDt2YWx1ZSZuYnNwO2l0Jm5ic3A7
c2VuZHMmbmJzcDt0bzxicj4mZ3Q7Jm5ic3A7Y2xpZW50cyZuYnNwO2FuZCZuYnNwO3ZhbGlkYXRl
cyZuYnNwO3RoZSZuYnNwO3Rva2VuJm5ic3A7c2VudCZuYnNwO2JhY2smbmJzcDtmcm9tJm5ic3A7
YSZuYnNwO2NsaWVudC48YnI+PGJyPkFzJm5ic3A7ZGlzY3Vzc2VkJm5ic3A7YmVmb3JlLCZuYnNw
O3RoaXMmbmJzcDtkZXNjcmlwdGlvbiZuYnNwO29mJm5ic3A7dGhlJm5ic3A7UmV0cnkmbmJzcDtt
ZWNoYW5pc20mbmJzcDtpczxicj5pbmFjY3VyYXRlJm5ic3A7dG8mbmJzcDt0aGUmbmJzcDtwb2lu
dCZuYnNwO2l0Jm5ic3A7ZGVmZWF0cyZuYnNwO2l0cyZuYnNwO3ZlcnkmbmJzcDtwdXJwb3NlLjxi
cj48YnI+Jmd0OyZuYnNwO0FkZHJlc3MmbmJzcDt2YWxpZGF0aW9uJm5ic3A7aXMmbmJzcDt1c2Vk
Jm5ic3A7YnkmbmJzcDtRVUlDJm5ic3A7dG8mbmJzcDthdm9pZCZuYnNwO2JlaW5nJm5ic3A7dXNl
ZCZuYnNwO2ZvciZuYnNwO2EmbmJzcDt0cmFmZmljPGJyPiZndDsmbmJzcDthbXBsaWZpY2F0aW9u
Jm5ic3A7YXR0YWNrLjxicj48YnI+VGhpcyZuYnNwO2lzJm5ic3A7YWxzbyZuYnNwO2luYWNjdXJh
dGU7Jm5ic3A7dGhlJm5ic3A7bG93ZXImbmJzcDtib3VuZCZuYnNwO2ZvciZuYnNwO3RoZSZuYnNw
O0luaXRpYWwmbmJzcDtwYWNrZXQmbmJzcDtzaXplPGJyPnByZXZlbnRzJm5ic3A7YW1wbGlmaWNh
dGlvbi4mbmJzcDsmbmJzcDtSZXRyeSZuYnNwO3Rva2VuJm5ic3A7aXMmbmJzcDt0aGVyZSZuYnNw
O3RvJm5ic3A7bWl0aWdhdGUmbmJzcDtJbml0aWFsPGJyPnBhY2tldCZuYnNwO2Zsb29kcy4mbmJz
cDsmbmJzcDtOZWl0aGVyJm5ic3A7cHJldmVudCZuYnNwO3RyaXZpYWwmbmJzcDtyZWZsZWN0aW9u
LCZuYnNwO2lmJm5ic3A7eW91Jm5ic3A7d2lsbC48YnI+PGJyPiZndDsmbmJzcDtJZiZuYnNwO3Nl
cnZlciZuYnNwO2Nob29zZXMmbmJzcDt0bzxicj4mZ3Q7Jm5ic3A7YWNjZXB0Jm5ic3A7dGhlJm5i
c3A7Y29zdCZuYnNwO2Jyb3VnaHQmbmJzcDtieSZuYnNwO3Rva2VuJm5ic3A7ZXhjaGFuZ2luZyZu
YnNwO2luJm5ic3A7SGFuZHNoYWtlPGJyPiZndDsmbmJzcDtbLi5dPGJyPiZndDsmbmJzcDtBZGRp
bmcmbmJzcDt0b2tlbiZuYnNwO2ZpZWxkJm5ic3A7dG8mbmJzcDtIYW5kc2hha2UmbmJzcDtwYWNr
ZXQmbmJzcDtkb2VzJm5ic3A7bm90Jm5ic3A7YWRkJm5ic3A7bmV3Jm5ic3A7c2VjdXJpdHk8YnI+
Jmd0OyZuYnNwO2NvbmNlcm5zLjxicj48YnI+QXQmbmJzcDtsZWFzdCZuYnNwO29uZSZuYnNwO3Nl
Y3VyaXR5Jm5ic3A7Y29uY2VybiZuYnNwO0kmbmJzcDtzZWUmbmJzcDtoZXJlJm5ic3A7aXMmbmJz
cDt3aGF0Jm5ic3A7ZGF0YSZuYnNwO3RoZSZuYnNwO3NlcnZlciZuYnNwO2lzPGJyPmV4cGVjdGVk
Jm5ic3A7dG8mbmJzcDtkZXJpdmUmbmJzcDtpdHMmbmJzcDtkZWNpc2lvbiZuYnNwO3RvJm5ic3A7
YWNjZXB0Jm5ic3A7dGhlJm5ic3A7Y29zdCZuYnNwO2Zyb20uPGJyPjxicj5FLmcuJm5ic3A7d2l0
aCZuYnNwO3RoZSZuYnNwO2Fmb3JlbWVudGlvbmVkJm5ic3A7MzAwJm5ic3A7TXBwcyZuYnNwO0lu
aXRpYWwmbmJzcDtwYWNrZXQmbmJzcDtmbG9vZCwmbmJzcDt3aGF0Jm5ic3A7aXM8YnI+dGhlJm5i
c3A7YXBwcm94aW1hdGUmbmJzcDtjb3N0Jm5ic3A7b2YmbmJzcDtrZWVwaW5nJm5ic3A7dGhlJm5i
c3A7c3RhdGUsJm5ic3A7cGVyJm5ic3A7c2Vjb25kPyZuYnNwOyZuYnNwO0lmJm5ic3A7eW91Jm5i
c3A7d291bGQ8YnI+anVzdCZuYnNwO2JlJm5ic3A7c3RvcmluZyZuYnNwOzE2Jm5ic3A7b2N0ZXRz
Jm5ic3A7b2YmbmJzcDthbiZuYnNwO0lQdjYmbmJzcDthZGRyZXNzJm5ic3A7cGx1cyZuYnNwOzIm
bmJzcDtvY3RldHMmbmJzcDtvZiZuYnNwO3RoZTxicj5jbGllbnQncyZuYnNwO2VwaGVtZXJhbCZu
YnNwO3BvcnQmbmJzcDtmb3ImbmJzcDthbnkmbmJzcDtSeCZuYnNwO3BhY2tldCwmbmJzcDt0aGF0
J2QmbmJzcDtiZSZuYnNwO21vcmUmbmJzcDt0aGFuJm5ic3A7NTxicj5HYnl0ZXMmbmJzcDtvZiZu
YnNwO1JBTSZuYnNwO2NvbnN1bWVkJm5ic3A7KnBlciZuYnNwO3NlY29uZCombmJzcDtvZiZuYnNw
O3RoZSZuYnNwO2F0dGFjaywmbmJzcDtub3QmbmJzcDtpbmNsdWRpbmcmbmJzcDt0aGU8YnI+cG9p
bnRlcnMsJm5ic3A7aGFzaGVzJm5ic3A7ZXRjLiZuYnNwOyZuYnNwO05leHQsJm5ic3A7SSZuYnNw
O2hhdmVuJ3QmbmJzcDtleGFjdGx5Jm5ic3A7ZG9uZSZuYnNwO3RoZSZuYnNwO21hdGgsJm5ic3A7
YnV0Jm5ic3A7STxicj50aGluayZuYnNwO3RoYXQmbmJzcDt0aGUmbmJzcDtkcmFmdCZuYnNwO2lt
cGxpZXMmbmJzcDt0aGF0Jm5ic3A7dGhlJm5ic3A7c3RhdGUmbmJzcDtrZXB0Jm5ic3A7d291bGQm
bmJzcDtiZSZuYnNwO2hhcmRseSZuYnNwO2xlc3M8YnI+dGhhbiZuYnNwO2FuJm5ic3A7b3JkZXIm
bmJzcDtvZiZuYnNwO21hZ25pdHVkZSZuYnNwO2JpZ2dlciZuYnNwO3RoYW4mbmJzcDt0aGF0LiZu
YnNwOyZuYnNwO0Fsc28sJm5ic3A7dGhlJm5ic3A7Y29zdCZuYnNwO29mPGJyPnByb2Nlc3Npbmcm
bmJzcDtldmVyeSZuYnNwO3Nwb29mZWQmbmJzcDtwYWNrZXQmbmJzcDt0aHJvdWdoJm5ic3A7dGhl
Jm5ic3A7d2hvbGUmbmJzcDtoYW5kc2hha2UmbmJzcDtwaXBlbGluZSw8YnI+YW5kJm5ic3A7c28m
bmJzcDtvbi4mbmJzcDsmbmJzcDtJJm5ic3A7YmVsaWV2ZSZuYnNwO3RoaXMmbmJzcDtpcyZuYnNw
O3doZXJlJm5ic3A7dGhlJm5ic3A7YXV0aG9ycyZuYnNwO25lZWQmbmJzcDt0byZuYnNwO2NvbWUm
bmJzcDt1cCZuYnNwO3dpdGg8YnI+YmVuY2htYXJrcyZuYnNwO2FuZCZuYnNwO2ltcGxlbWVudGF0
aW9uJm5ic3A7aGludHMmbmJzcDtvbiZuYnNwO2dhcmJhZ2UmbmJzcDtjb2xsZWN0aW9uJm5ic3A7
bWV0aG9kcyZuYnNwO2V0Yy48YnI+PGJyPkkmbmJzcDtrbm93Jm5ic3A7dGhlJm5ic3A7YW1vdW50
Jm5ic3A7b2YmbmJzcDtSQU0mbmJzcDthdmFpbGFibGUmbmJzcDtpcyZuYnNwO2Rlc3RpbmVkJm5i
c3A7dG8mbmJzcDtncm93Jm5ic3A7YnV0Jm5ic3A7dGhlJm5ic3A7Zmxvb2RzPGJyPmFyZSZuYnNw
O25vdCZuYnNwO2V4cGVjdGVkJm5ic3A7dG8mbmJzcDtzaHJpbmsmbmJzcDthbnkmbmJzcDt0aW1l
Jm5ic3A7c29vbiZuYnNwO2p1c3QmbmJzcDthcyZuYnNwO3dlbGwuPGJyPjxicj4tLTxicj5Uw7Zt
YTwvYmxvY2txdW90ZT48L2Rpdj48L2Jsb2NrcXVvdGU+PC9kaXY+
------=ALIBOUNDARY_34679_46023940_5dbcac3f_3581ee--


From nobody Fri Nov  1 15:28:14 2019
Return-Path: <anqing.aq@alibaba-inc.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 4E93812088C; Fri,  1 Nov 2019 15:28:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.987
X-Spam-Level: 
X-Spam-Status: No, score=-1.987 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_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, UNPARSEABLE_RELAY=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=alibaba-inc.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 9GA4iRksnUYO; Fri,  1 Nov 2019 15:28:09 -0700 (PDT)
Received: from out0-146.mail.aliyun.com (out0-146.mail.aliyun.com [140.205.0.146]) (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 49A4D12088B; Fri,  1 Nov 2019 15:28:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1572647278; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=tpDyEq3oE9hBBEUwpXYhb19/rTX8b9AXGBuPmQSwrVE=; b=rpVBgQC315zCuAEjzKLOeWf7WSm55ejKv3mMFLChyBDKrij8ppSbMq20MI+L0Bma+tKzjq3sYFMQmYwzVrKcS7ExBaX0lucia76WnVA4V4gM4bt3hi/dJYAX/uTt6VirfRLPjcD4hMKhQtCsUYyjBmsZwLNMtaWdFYGz/EV0Z/E=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R201e4; CH=green; DM=||false|; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03289; MF=anqing.aq@alibaba-inc.com; NM=1; PH=DW; RN=7; SR=0; TI=alimail_ios_2.COREAPI24b5529d4f414c59aeb7bd4420111713; 
Received: from WS-web (anqing.aq@alibaba-inc.com[alimail_ios_2.COREAPI24b5529d4f414c59aeb7bd4420111713]) by e02c03289.eu6 at Sat, 02 Nov 2019 06:27:56 +0800
Date: Sat, 02 Nov 2019 06:27:56 +0800
From: "Qing An" <anqing.aq@alibaba-inc.com>
To: "=?UTF-8?B?TWlra2VsIEZhaG7DuGUgSsO4cmdlbnNlbg==?=" <mikkelfj@gmail.com>, "Marten Seemann" <martenseemann@gmail.com>
Cc: "jri.ietf" <jri.ietf@gmail.com>, "QUIC" <quic-bounces@ietf.org>, "quic" <quic@ietf.org>, "mt" <mt@lowentropy.net>, "=?UTF-8?B?5YiY5aSn6bmPKOm5j+aIkCk=?=" <max.ldp@alibaba-inc.com>
Message-ID: <880446e2-3bd9-4c47-8d66-fd582c0ae473.anqing.aq@alibaba-inc.com>
Subject: =?UTF-8?B?UmU6UmU6UmU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQ=?=
X-Priority: 3
X-Mailer: [Alimail-Mailagent revision 2765257]
MIME-Version: 1.0
In-Reply-To: <CAN1APdd4WuMGAusz3EnCc4+BsT+hBfC9oMmAmhhwDc75wxMGiw@mail.gmail.com>
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com> <BN6PR2201MB1700F72F3DC8F6C3CF79902CDA600@BN6PR2201MB1700.namprd22.prod.outlook.com> <bd15f357-8e7a-42af-bf28-79f7177da385@www.fastmail.com> <f55efb80-1a95-4190-84e5-b81948a7f081.anqing.aq@alibaba-inc.com> <BN6PR2201MB17005571E88F1C68769091A3DA630@BN6PR2201MB1700.namprd22.prod.outlook.com> <69d1a917-b1f9-4142-afb0-f5c67abe7334.anqing.aq@alibaba-inc.com> <CAOYVs2r0zJzbfw5L2Mck8VEJhtyfQtHwF-db5VG45HDTF0WoOQ@mail.gmail.com> <7ac8ad51-c1a2-461b-bc47-021b3875eab8.anqing.aq@alibaba-inc.com> <CAN1APddvVeqXeWCZbe9WrLrOyVOWM5-1Dg8x5B4UpNwP6YOGrA@mail.gmail.com> <8f87c3ce-d9c0-4017-be6d-4a411daeaa2d.anqing.aq@alibaba-inc.com>, <CAN1APdd4WuMGAusz3EnCc4+BsT+hBfC9oMmAmhhwDc75wxMGiw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_82422_47432940_5dbcb16c_358c93"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/YZ-YgOKhS-EyQ6a_-5-eYkBLKWY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 22:28:13 -0000

------=ALIBOUNDARY_82422_47432940_5dbcb16c_358c93
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

CkJhc2VkIG9uIGRpc2N1c3Npb24sIHRoZSBwcm9wb3NhbCBpcyBmb3IgZmlyc3QgY29ubmVjdGlv
biBlc3RhYmxpc2htZW50LCBzZXJ2ZXIgY2hvb3NlcyB0byBlbGltaW5hdGUgUmV0cnkgYW5kIHJl
bHkgb24gaGFuZHNoYWtlLiBCdXQgc2VydmVyIGNhbiBhbHNvIHVzZSBOZXdfVG9rZW4gZnJhbWUg
dmlhIEhhbmRzaGFrZSBvciBJbml0aWFsIHRvIGRlbGl2ZXIgdG9rZW4gZm9yIGZ1dHVyZSBjb25u
ZWN0aW9uLgoKCgogLS0tLS0tLS0tLS0tLS0tLS0tT3JpZ2luYWwgTWFpbCAtLS0tLS0tLS0tLS0t
LS0tLS0KU2VuZGVyOk1pa2tlbCBGYWhuw7hlIErDuHJnZW5zZW4gPG1pa2tlbGZqQGdtYWlsLmNv
bT4KU2VuZCBEYXRlOkZyaSBOb3YgMSAyMzoxOTozMCAyMDE5ClJlY2lwaWVudHM6UWluZyBBbiA8
YW5xaW5nLmFxQGFsaWJhYmEtaW5jLmNvbT4sIE1hcnRlbiBTZWVtYW5uIDxtYXJ0ZW5zZWVtYW5u
QGdtYWlsLmNvbT4KQ0M6anJpLmlldGYgPGpyaS5pZXRmQGdtYWlsLmNvbT4sIFFVSUMgPHF1aWMt
Ym91bmNlc0BpZXRmLm9yZz4sIHF1aWMgPHF1aWNAaWV0Zi5vcmc+LCBtdCA8bXRAbG93ZW50cm9w
eS5uZXQ+LCDliJjlpKfpuY8o6bmP5oiQKSA8bWF4LmxkcEBhbGliYWJhLWluYy5jb20+ClN1Ympl
Y3Q6UmU6UmU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQKCkJ1dCB3aGF0IGRvIHlv
dSBuZWVkIHRvIHRoZSB0b2tlbiBmb3IgaW4gdGhpcyBjYXNlPyBUaGUgdG9rZW4gaXMgdG8gcHJv
dmUgdGhhdCB5b3UgcHJldmlvdXNseSBzcG9rZW4gdG8gdGhlIHNlcnZlci4gQnV0IHRoZSBUTFMg
aGFuZHNoYWtlIHByb3ZpZGVzIHRoZSBzYW1lIHByb29mIChidXQgY2Fubm90IHJlZGlyZWN0IGFu
ZCBtdXN0IGNhcnJ5IHN0YXRlKS4gQW55IGFkZGl0aW9uYWwgaW5mb3JtYXRpb24gdGhlIHRva2Vu
IG1pZ2h0IGNhcnJ5IGlzIG9ubHkgaW50ZXJlc3RpbmcgaW4gSW5pdGlhbCBwYWNrZXRzIHdoZXJl
IHRoZSBjb25uZWN0aW9uIGNhbiBiZSBzdG9wcGVkIGVhcmx5IG9yIChpbiBvbmdvaW5nIHdvcmsp
IHRvIGVuY3J5cHQgdGhlIGluaXRpYWwgcGFja2V0LiBUaGF0IGlzIG5vdCByZWxldmFudCBkdXJp
bmcgaGFuZHNoYWtlLiBUaGUgRGlmZmllIEhlbG1hbiBrZXkgZXhjaGFuZ2UgdGFrZXMgY2FyZSBv
ZiBhbGwgdGhpcy4gU2luY2UgeW91IHByb3Bvc2FsIGFsc28gY2Fubm90IHJlZGlyZWN0IGFuZCBt
dXN0IGNhcnJ5IHN0YXRlLCBJIGRvbuKAmXQgc2VlIHRoZSBwdXJwb3NlLiBJIGRvIGFncmVlIHlv
dSBjYW4gZGVsaXZlciB0aGF0IHRva2VuLCBidXQgc2luY2UgaXQgaXMgbm90IG9idmlvdXMgd2hh
dCB0aGUgdG9rZW4gaXMgbmVlZGVkIGZvciwgdGhlIHB1cnBvc2UgaXMgdW5jbGVhci4KCllvdSBh
cHBlYXIgdG8gYXNzdW1lIHRoYXQgYWRkcmVzcyB2YWxpZGF0aW9uIG9ubHkgaGFwcGVucyBpZiB5
b3UgaGF2ZSBhIFJldHJ5IHRva2VuLCBidSB0aGF0IGlzIG5vdCBjb3JyZWN0LCBpdCBqdXN0IGhh
cHBlbnMgd2l0aCBsZXNzIHNlcnZlciByZXNvdXJjZXMuIApPbiAxIE5vdmVtYmVyIDIwMTkgYXQg
MTUuNTUuMDksIFFpbmcgQW4gKGFucWluZy5hcUBhbGliYWJhLWluYy5jb20pIHdyb3RlOiAKCkFn
YWluLCB0aGUgZmFzdCBhZGRyZXNzIHZhbGlkYXRpb24gaXMgdG8gcHJvdmlkZSBhbm90aGVyIG9w
dGlvbiBmb3Igc2VydmVyLCBub3QgdG8gZHJvcCB0aGUgUmV0cnkgYXBwcm9hY2guCgpJIHRoaW5r
IGlmIGNob29zZSBub3QgdG8gc2VuZCBhIFJldHJ5LCBpdCBpcyBuZWNlc3NhcnkgdG8gZGVmaW5l
IGhvdyB0byBkZWxpdmVyIHRva2VuIGZyb20gc2VydmVyIHRvIGNsaWVudC4gSW4gdGhpcyBjYXNl
LCAgdmlhIG5ld190b2tlbiBmcmFtZSBpbiBoYW5kc2hha2UgY2FuIGJlIGFuIGFwcHJvYWNoLgoK
CgotLS0tLS0tLS0tLS0tLS0tLS1PcmlnaW5hbCBNYWlsIC0tLS0tLS0tLS0tLS0tLS0tLQpTZW5k
ZXI6TWlra2VsIEZhaG7DuGUgSsO4cmdlbnNlbiA8bWlra2VsZmpAZ21haWwuY29tPgpTZW5kIERh
dGU6RnJpIE5vdiAxIDIxOjM3OjQyIDIwMTkKUmVjaXBpZW50czpRaW5nIEFuIDxhbnFpbmcuYXFA
YWxpYmFiYS1pbmMuY29tPiwgTWFydGVuIFNlZW1hbm4gPG1hcnRlbnNlZW1hbm5AZ21haWwuY29t
PgpDQzpqcmkuaWV0ZiA8anJpLmlldGZAZ21haWwuY29tPiwgUVVJQyA8cXVpYy1ib3VuY2VzQGll
dGYub3JnPiwgcXVpYyA8cXVpY0BpZXRmLm9yZz4sIG10IDxtdEBsb3dlbnRyb3B5Lm5ldD4sIOWI
mOWkp+m5jyjpuY/miJApIDxtYXgubGRwQGFsaWJhYmEtaW5jLmNvbT4KU3ViamVjdDpSZTogRmFz
dCBBZGRyZXNzIFZhbGlkYXRpb24gLSBhYm91dCAKCiBZb3Ugb25seSBzYXZlIGEgcm91bmR0cmlw
IGJlY2F1c2UgeW91IGRvIG5vdCBzZW5kIGEgUmV0cnkuCgogSWYgeW91IGNob29zZSBub3QgdG8g
c2VuZCBhIFJldHJ5LCB0aGUgY2xpZW50IGV2ZW50dWFsbHkgZ2V0cyB2YWxpZGF0ZWQgYW55d2F5
IGJlY2F1c2Ugb3RoZXJ3aXNlIHRoZSBoYW5kc2hha2UgY291bGQgbm90IGNvbXBsZXRlLiBUaGVy
ZWZvcmUgYSBSZXRyeSB0b2tlbiBpcyBub3QgbmVlZGVkIGlmIHlvdSBnbyBkb3duIHRoYXQgcGF0
aC4gSW4gdGhpcyBjYXNlIHRoZSBSVFQgb3ZlcmhlYWQgd2l0aCBmYXN0IGFkZHJlc3MgdmFsaWRh
dGlvbiBpcyB0aGUgc2FtZSBhcyBvcmRpbmFyeSBRVUlDIDEtUlRUIGhhbmRzaGFrZS4KCiBPbiB0
aGUgb3RoZXIgaGFuZCwgaW4gdGhlIGNhc2Ugd2hlcmUgUmV0cnkgaXMgbmVlZGVkLCB0aGUgZmFz
dCBhZGRyZXNzIHZhbGlkYXRpb24gYXBwcm9hY2ggZG9lcyBub3Qgc29sdmUgdGhlIHByb2JsZW0g
d2hpY2ggaXMgb25lIG9mIDEpIGRlZmVyIGhhbmRzaGFrZSBwcm9jZXNzaW5nIGFuZCBzZXJ2ZXIg
c3RhdGUgdW50aWwgYWZ0ZXIgdGhlIGFkZHJlc3MgaXMgdmVyaWZpZWQsIG9yIDIpIHJlZGlyZWN0
IHRoZSBjbGllbnQgdG8gYW5vdGhlciBzZXJ2ZXIgdGhyb3VnaCBhIGNoYW5nZSBpbiBDb25uZWN0
aW9uSUQuCgoKCk9uIDEgTm92ZW1iZXIgMjAxOSBhdCAxNC4yNi4yNCwgUWluZyBBbiAoYW5xaW5n
LmFxQGFsaWJhYmEtaW5jLmNvbSkgd3JvdGU6IAoKSSBiZWxpZXZlIHRoaXMgY2FuIHNhdmUgMS1S
VFQuCgpBcyBmb3IgdGhlIHByaXZhY3kgcmlzaywgbmV3X3Rva2VuIGZyYW1lIGNhbiBiZSBkZWxp
dmVyZWQgdmlhIGhhbmRzaGFrZQoKCgotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0KRnJvbTpNYXJ0ZW4gU2VlbWFubiA8bWFy
dGVuc2VlbWFubkBnbWFpbC5jb20+ClNlbmQgVGltZToyMDE55bm0MTHmnIgx5pelKOaYn+acn+S6
lCkgMjA6NTQKVG865a6J5YuNKOiOs+mAuCkgPGFucWluZy5hcUBhbGliYWJhLWluYy5jb20+CkNj
OlFVSUMgPHF1aWMtYm91bmNlc0BpZXRmLm9yZz47IHF1aWMgPHF1aWNAaWV0Zi5vcmc+OyBqcmku
aWV0ZiA8anJpLmlldGZAZ21haWwuY29tPjsgbXQgPG10QGxvd2VudHJvcHkubmV0PjsgbWlra2Vs
ZmogPG1pa2tlbGZqQGdtYWlsLmNvbT47IOWImOWkp+m5jyjpuY/miJApIDxtYXgubGRwQGFsaWJh
YmEtaW5jLmNvbT4KU3ViamVjdDpSZTogRmFzdCBBZGRyZXNzIFZhbGlkYXRpb24gLSBhYm91dAoK
SSBkb24ndCBzZWUgYW55IGVuaGFuY2VkIGNsaWVudCBleHBlcmllbmNlLCBzaW5jZSB0aGUgaGFu
ZHNoYWtlIHRha2VzIGV4YWN0bHkgdGhlIHNhbWUgbnVtYmVyIG9mIHJvdW5kIHRyaXBzIHdpdGgg
eW91ciBwcm9wb3NhbCBhcyB3aXRoIHRoZSBjdXJyZW50IHZlcnNpb24gb2YgdGhlIFFVSUMgZHJh
ZnQuClNlbmRpbmcgTkVXX1RPS0VOIGluIEluaXRpYWwgcGFja2V0cyBwcm92aWRlcyBubyBiZW5l
Zml0IG92ZXIgc2VuZGluZyBpdCBpbiAxLVJUVCBwYWNrZXRzLCBidXQgY29tZXMgd2l0aCB3b3Jz
ZSBwcml2YWN5IHByb3BlcnRpZXMsIHNpbmNlIEluaXRpYWwgcGFja2V0cyBhcmUgbm90IGVuY3J5
cHRlZCBhbmQgY2FuIHRoZXJlZm9yZSBiZSByZWFkIGJ5IG9uLXBhdGggb2JzZXJ2ZXJzLgoKT24g
RnJpLCBOb3YgMSwgMjAxOSBhdCA3OjM3IFBNIFFpbmcgQW4gPGFucWluZy5hcUBhbGliYWJhLWlu
Yy5jb20+IHdyb3RlOgoKSWYgc28sIGZvciB0aGUgZmlyc3QgY29ubmVjdGlvbiBiZXR3ZWVuIGNs
aWVudCBhbmQgc2VydmVyLCBzZXJ2ZXIgY2FuIGNob29zZSB0byBlbGltaW5hdGUgdGhlIHVzZSBv
ZiBSZXRyeSBwYWNrZXQgZm9yIHRva2VuIGRlbGl2ZXJ5LCBhbmQgcmVseSBvbiBoYW5kc2hha2Ug
ZW5jcnlwdGlvbiBsYXllciB0byBwcm92ZSByZXR1cm4gcm91dGFiaWxpdHkuICBJbiBhZGRpdGlv
biwgTmV3X1Rva2VuIGZyYW1lIGlzIHVzZWQgYnkgc2VydmVyLCB2aWEgaS5lLiB0aGUgSW5pdGlh
bCBwYWNrZXQsIHRvIHByb3ZpZGUgdGhlIGNsaWVudCB3aXRoIGFuIGFkZHJlc3MgdmFsaWRhdGlv
biB0b2tlbiB0aGF0IGNhbiBiZSB1c2VkIHRvIHZhbGlkYXRlIGZ1dHVyZSBjb25uZWN0aW9ucy4K
Ckl0IGNhbiBlbmhhbmNlIHRoZSBleHBlcmllbmNlIGluIGNsaWVudCBzaWRlIGZvciB0aGUgZmly
c3QgY29ubmVjdGlvbiBlc3RhYmxpc2htZW50LgoKSSBzdWJtaXR0ZWQgdGhlIGRyYWZ0LCBodHRw
czovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1hbi1mYXN0LWFkZHJlc3MtdmFsaWRh
dGlvbi8KClFpbmcKCgoKIC0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQpGcm9tOk1pa2UgQmlzaG9wIDxtYmlzaG9wQGV2ZXF1
ZWZvdS5iZT4KU2VuZCBUaW1lOjIwMTnlubQxMeaciDHml6Uo5pif5pyf5LqUKSAwMDowNgpUbzrl
ronli40o6I6z6YC4KSA8YW5xaW5nLmFxQGFsaWJhYmEtaW5jLmNvbT47IHF1aWMgPHF1aWNAaWV0
Zi5vcmc+OyBqcmkuaWV0ZiA8anJpLmlldGZAZ21haWwuY29tPjsgbXQgPG10QGxvd2VudHJvcHku
bmV0PjsgbWlra2VsZmogPG1pa2tlbGZqQGdtYWlsLmNvbT4KU3ViamVjdDpSRTogRmFzdCBBZGRy
ZXNzIFZhbGlkYXRpb24gLSBhYm91dAoKIEFzIE1hcnRpbiBwb2ludGVkIG91dCBpbiB0aGUgZS1t
YWlsIHlvdSByZXBsaWVkIHRvLCBpZiB0aGUgc2VydmVyIGlzIHdpbGxpbmcgdG8gbWFpbnRhaW4g
c3RhdGUsIGFueSBwYWNrZXQgYXQgdGhlIEhhbmRzaGFrZSBlbmNyeXB0aW9uIGxheWVyIHByb3Zl
cyByZXR1cm4gcm91dGFiaWxpdHkuICBUaGVyZSBzZWVtcyB0byBiZSBubyBuZWVkIGZvciBhIHNl
cGFyYXRlIGFkZHJlc3MgdmFsaWRhdGlvbiBtZWNoYW5pc20gaWYgdGhlIHNlcnZlciBpcyB3aWxs
aW5nIHRvIHByb2NlZWQgd2l0aCB0aGUgaGFuZHNoYWtlLgpGcm9tOiBRVUlDIDxxdWljLWJvdW5j
ZXNAaWV0Zi5vcmc+IE9uIEJlaGFsZiBPZiBRaW5nIEFuClNlbnQ6IFRodXJzZGF5LCBPY3RvYmVy
IDMxLCAyMDE5IDg6NTYgQU0KVG86IHF1aWMgPHF1aWNAaWV0Zi5vcmc+OyBqcmkuaWV0ZiA8anJp
LmlldGZAZ21haWwuY29tPjsgbXQgPG10QGxvd2VudHJvcHkubmV0PjsgbWlra2VsZmogPG1pa2tl
bGZqQGdtYWlsLmNvbT4KU3ViamVjdDogUmU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJv
dXQKICAKICAKVG8gY2xhcmlmeSwgdGhlIHByb3Bvc2FsIGlzIG5vdCB0byByZXBsYWNlIHRoZSBl
eGlzdGluZyBSZXRyeS1iYXNlZCB2YWxpZGF0aW9uLCBidXQgdG8gcHJvdmlkZSBhbm90aGVyIG9w
dGlvbiBmb3Igc2VydmVyIHRvIGRvIHRoZSBjbGllbnQgdmFsaWRhdGlvbi4gCiAgCkkgdW5kZXJz
dGFuZCB0aGF0IGluIHNlcnZlciBzaWRlLCBleGNoYW5naW5nIHRoZSB0b2tlbiBhdCB0aGUgSGFu
ZHNoYWtlIGVuY3J5cHRpb24gbGV2ZWwgd2lsbCBtYWtlIHRoZSBzZXJ2ZXIgc3RhcnQgdG8gbWFp
bnRhaW4gaGFuZHNoYWtlIHN0YXRlcy4gQnV0IGluIGNsaWVudCBzaWRlLCBpdCBjYW4gYWNjZWxl
cmF0ZSB0aGUgY29ubmVjdGlvbiBlc3RhYmxpc2htZW50IGZyb20gY2xpZW50IHRvIHNlcnZlci4g
CiAgCiBBbmQgaXQgaXMgdGhlIHNlcnZlcidzIGRlY2lzaW9uIHdoZXRoZXIgdG8gZXhjaGFuZ2Ug
dG9rZW4gaW4gUmV0cnkgb3IgaW4gSGFuZHNoYWtlLiBJZiBzZXJ2ZXIgY2hvb3NlcyB0byBhY2Nl
cHQgdGhlIGNvc3QgYnJvdWdodCBieSB0b2tlbiBleGNoYW5naW5nIGluIEhhbmRzaGFrZSwgaXQg
d2lsbCBicmluZyBtb3JlIGVuaGFuY2VkIGV4cGVyaWVuY2UgaW4gY2xpZW50IHNpZGUuIAogIAog
IAogQlIsIAogUWluZyAKICAKICAKLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tIApGcm9tOk1hcnRpbiBUaG9tc29uIDxtdEBs
b3dlbnRyb3B5Lm5ldD4gClNlbmQgVGltZToyMDE55bm0MTDmnIgzMeaXpSjmmJ/mnJ/lm5spIDA2
OjA3IApUbzpxdWljIDxxdWljQGlldGYub3JnPiAKU3ViamVjdDpSZTogRmFzdCBBZGRyZXNzIFZh
bGlkYXRpb24gLSBhYm91dCAKICAKQWxzbyBub3RlIHRoYXQgZXhjaGFuZ2Ugb2YgSGFuZHNoYWtl
IHBhY2tldHMgcHJvdmlkZXMgcHJvb2Ygb2YgcmV0dXJuIHJvdXRlYWJpbGl0eSB2aWEgdGhlIHVz
ZSBvZiB0aGUgZW5jcnlwdGlvbiBrZXlzLCBzbyB0aGVyZSBpcyBubyBuZWVkIHRvIGV4Y2hhbmdl
IHRva2VucyBhdCB0aGF0IGxldmVsLgoKIE9uIFRodSwgT2N0IDMxLCAyMDE5LCBhdCAwMzoyOSwg
TWlrZSBCaXNob3Agd3JvdGU6CiA+ICAKID4gVGhlIGFkdmFudGFnZSBvZiB1c2luZyBSZXRyeSwg
aG93ZXZlciwgaXMgdGhhdCB0aGUgc2VydmVyIGlzIGFibGUgdG8gCiA+IGtlZXAgbWluaW1hbCAo
aWYgYW55KSBzdGF0ZSBhYm91dCB0aGUgY2xpZW50LiBFeGNoYW5naW5nIHRoZSB0b2tlbiBhdCAK
ID4gdGhlIEhhbmRzaGFrZSBlbmNyeXB0aW9uIGxldmVsIG1lYW5zIHRoZSBzZXJ2ZXIgaXMgYWxy
ZWFkeSBkb2luZyB3b3JrIAogPiBhbmQgbWFpbnRhaW5pbmcgc3RhdGUgaW4gb3JkZXIgdG8gcHJv
Y2VzcyB0aGUgaGFuZHNoYWtlLCB3aGljaCBpcyAKID4gZXhhY3RseSB3aGF0IHRoZSBzZXJ2ZXIg
aXMgdHJ5aW5nIHRvIGF2b2lkLgogPiAKID4gCiA+ICpGcm9tOiogUVVJQyA8cXVpYy1ib3VuY2Vz
QGlldGYub3JnPiAqT24gQmVoYWxmIE9mICogUWluZyBBbgogPiAqU2VudDoqIFdlZG5lc2RheSwg
T2N0b2JlciAzMCwgMjAxOSA5OjQxIEFNCiA+ICpUbzoqIHF1aWMgPHF1aWNAaWV0Zi5vcmc+OyBq
cmkuaWV0ZiA8anJpLmlldGZAZ21haWwuY29tPjsgbXQgCiA+IDxtdEBsb3dlbnRyb3B5Lm5ldD4K
ID4gKkNjOiog5YiY5aSn6bmPKOm5j+aIkCkgPG1heC5sZHBAYWxpYmFiYS1pbmMuY29tPgogPiAq
U3ViamVjdDoqIEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQKID4gCiA+IAogPiAKID4g
CiA+IEhpIE1hcnRpbiwgSmFuYSwgCiA+IAogPiBJIHJlYWQgdGhyb3VnaCBodHRwczovL3d3dy5p
ZXRmLm9yZy9pZC9kcmFmdC1pZXRmLXF1aWMtdHJhbnNwb3J0LTIzLnR4dCAKID4gYW5kIGhhdmUg
YSBmZXcgY29tbWVudHMgYW5kIGlkZWFzIHRvIGRpc2N1c3MuCiA+IAogPiAKID4gW1FVSUMtVHJh
bnNdIGRlZmluZXMgYSB0b2tlbiBiYXNlZCBzY2hlbWUgdG8gZmFjaWxpdGF0ZSBhZGRyZXNzIAog
PiB2YWxpZGF0aW9uIG9mIGEgY2xpZW50LiBUaGUgdG9rZW4gTVVTVCBiZSBjb3ZlcmVkIGJ5IGlu
dGVncml0eSAKID4gcHJvdGVjdGlvbiBhZ2FpbnN0IG1vZGlmaWNhdGlvbiBvciBmYWxzaWZpY2F0
aW9uIGJ5IGNsaWVudHMuIFRoZSBzZXJ2ZXIgCiA+IHJlbWVtYmVycyB0aGUgdmFsdWUgaXQgc2Vu
ZHMgdG8gY2xpZW50cyBhbmQgdmFsaWRhdGVzIHRoZSB0b2tlbiBzZW50IAogPiBiYWNrIGZyb20g
YSBjbGllbnQuIEluIGl0cyBkZXNpZ24sIFJldHJ5IHBhY2tldCBpcyB1c2VkIHRvIGRlbGl2ZXIg
dGhlIAogPiB0b2tlbiB0byBhIGNsaWVudCB3aGljaCBhZGRyZXNzIGhhcyBub3QgeWV0IGJlZW4g
dmFsaWRhdGVkLiBJdCB2b2lkcyAKID4gdGhlIGZpcnN0IHRyYW5zbWlzc2lvbiBvZiB0aGUgSW5p
dGlhbCBwYWNrZXQgc2VudCBieSB0aGUgY2xpZW50LCBhbmQgCiA+IHRyaWdnZXJzIGEgc2Vjb25k
IEluaXRpYWwgcGFja2V0IHRvIGJlIHNlbnQgd2l0aCB0aGUgdG9rZW4uIFRoZSAKID4gZXhjaGFu
Z2Ugb2YgdG9rZW4gd2lsbCBjYXVzZSBsb25nZXIgY29ubmVjdGlvbiBlc3RhYmxpc2htZW50IGRl
bGF5IGZvciAKID4gYSBjbGllbnQuCiA+IAogPiAKID4gVG8gaW1wcm92ZSB0aGUgZWZmaWNpZW5j
eSBvZiBhZGRyZXNzIHZhbGlkYXRpb24gZHVyaW5nIGhhbmRzaGFrZSwgb25lIAogPiBpZGVhIGlz
IHRoYXQgdGhlIHNhbWUgdG9rZW4gY2FuIGJlIGV4Y2hhbmdlZCB2aWEgYSBkaWZmZXJlbnQgY29u
dGFpbmVyIAogPiBpLmUuIHRoZSBIYW5kc2hha2UgcGFja2V0LCB0aGF0IGVsaW1pbmF0ZXMgdGhl
IHVzZSBvZiBSZXRyeSBwYWNrZXQgZm9yIAogPiB0b2tlbiBkZWxpdmVyeS4gCiA+IAogPiAKID4g
SSBhbSB3b3JraW5nIG9uIHRoZSBjb21wbGV0ZSBkcmFmdCBhbmQgd2lsbCBzdWJtaXQgaXQgYnkg
RnJpZGF5LiBCZWZvcmUgCiA+IHRoYXQsIGhvcGUgdGhpcyBjYW4gYmUgZGlzY3Vzc2VkIGluIGVt
YWlsIGZpcnN0LgogPiAKID4gCiA+IEJSLAogPiAKID4gUWluZyBBbgogPiAKICAgIAoKCg==
------=ALIBOUNDARY_82422_47432940_5dbcb16c_358c93
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64

PGRpdiBpZD0ibWFpbGJveC1jb252ZXJzYXRpb24iPjxkaXY+PGJyPjwvZGl2PjxkaXY+QmFzZWQg
b24gZGlzY3Vzc2lvbiwgdGhlIHByb3Bvc2FsIGlzIGZvciBmaXJzdCBjb25uZWN0aW9uIGVzdGFi
bGlzaG1lbnQsIHNlcnZlciBjaG9vc2VzIHRvIGVsaW1pbmF0ZSBSZXRyeSBhbmQgcmVseSBvbiBo
YW5kc2hha2UuIEJ1dCBzZXJ2ZXIgY2FuIGFsc28gdXNlIE5ld19Ub2tlbiBmcmFtZSB2aWEgSGFu
ZHNoYWtlIG9yIEluaXRpYWwgdG8gZGVsaXZlciB0b2tlbiBmb3IgZnV0dXJlIGNvbm5lY3Rpb24u
PC9kaXY+PGRpdj48YnI+PC9kaXY+PGRpdj48YnI+PC9kaXY+PGJsb2NrcXVvdGU+PGRpdj48ZGl2
IHN0eWxlPSJmb250LXNpemU6IDcwJSI+IC0tLS0tLS0tLS0tLS0tLS0tLU9yaWdpbmFsIE1haWwg
LS0tLS0tLS0tLS0tLS0tLS0tPC9kaXY+PGRpdj48c3BhbiBjbGFzcz0iZm9yd2FyZC1oZWFkZXIt
dGl0bGUiPlNlbmRlcjo8L3NwYW4+TWlra2VsIEZhaG7DuGUgSsO4cmdlbnNlbiAmbHQ7bWlra2Vs
ZmpAZ21haWwuY29tJmd0OzwvZGl2PjxkaXY+PHNwYW4gY2xhc3M9ImZvcndhcmQtaGVhZGVyLXRp
dGxlIj5TZW5kIERhdGU6PC9zcGFuPkZyaSBOb3YgIDEgMjM6MTk6MzAgMjAxOTwvZGl2PjxkaXY+
PHNwYW4gY2xhc3M9ImZvcndhcmQtaGVhZGVyLXRpdGxlIj5SZWNpcGllbnRzOjwvc3Bhbj5RaW5n
IEFuICZsdDthbnFpbmcuYXFAYWxpYmFiYS1pbmMuY29tJmd0OywgTWFydGVuIFNlZW1hbm4gJmx0
O21hcnRlbnNlZW1hbm5AZ21haWwuY29tJmd0OzwvZGl2PjxkaXY+PHNwYW4gY2xhc3M9ImZvcndh
cmQtaGVhZGVyLXRpdGxlIj5DQzo8L3NwYW4+anJpLmlldGYgJmx0O2pyaS5pZXRmQGdtYWlsLmNv
bSZndDssIFFVSUMgJmx0O3F1aWMtYm91bmNlc0BpZXRmLm9yZyZndDssIHF1aWMgJmx0O3F1aWNA
aWV0Zi5vcmcmZ3Q7LCBtdCAmbHQ7bXRAbG93ZW50cm9weS5uZXQmZ3Q7LCDliJjlpKfpuY8o6bmP
5oiQKSAmbHQ7bWF4LmxkcEBhbGliYWJhLWluYy5jb20mZ3Q7PC9kaXY+PGRpdj48c3BhbiBjbGFz
cz0iZm9yd2FyZC1oZWFkZXItdGl0bGUiPlN1YmplY3Q6PC9zcGFuPlJlOlJlOiBGYXN0IEFkZHJl
c3MgVmFsaWRhdGlvbiAtIGFib3V0PC9kaXY+PC9kaXY+PGRpdj48YmxvY2txdW90ZSBjbGFzcz0i
Z21haWxfcXVvdGUiPjxzdHlsZT4KYm9keSB7Zm9udC1mYW1pbHk6IGhlbHZldGljYSAsIGFyaWFs
O2ZvbnQtc2l6ZTogMTMuMHB4O30KPC9zdHlsZT48ZGl2IGlkPSJibG9vcF9jdXN0b21mb250IiBz
dHlsZT0iZm9udC1mYW1pbHk6IGhlbHZldGljYSAsIGFyaWFsO2ZvbnQtc2l6ZTogMTMuMHB4O2Nv
bG9yOiA7bWFyZ2luOiAwLjBweDtsaW5lLWhlaWdodDogYXV0bzsiPkJ1dCB3aGF0IGRvIHlvdSBu
ZWVkIHRvIHRoZSB0b2tlbiBmb3IgaW4gdGhpcyBjYXNlPyBUaGUgdG9rZW4gaXMgdG8gcHJvdmUg
dGhhdCB5b3UgcHJldmlvdXNseSBzcG9rZW4gdG8gdGhlIHNlcnZlci4gQnV0IHRoZSBUTFMgaGFu
ZHNoYWtlIHByb3ZpZGVzIHRoZSBzYW1lIHByb29mIChidXQgY2Fubm90IHJlZGlyZWN0IGFuZCBt
dXN0IGNhcnJ5IHN0YXRlKS4gQW55IGFkZGl0aW9uYWwgaW5mb3JtYXRpb24gdGhlIHRva2VuIG1p
Z2h0IGNhcnJ5IGlzIG9ubHkgaW50ZXJlc3RpbmcgaW4gSW5pdGlhbCBwYWNrZXRzIHdoZXJlIHRo
ZSBjb25uZWN0aW9uIGNhbiBiZSBzdG9wcGVkIGVhcmx5IG9yIChpbiBvbmdvaW5nIHdvcmspIHRv
IGVuY3J5cHQgdGhlIGluaXRpYWwgcGFja2V0LiBUaGF0IGlzIG5vdCByZWxldmFudCBkdXJpbmcg
aGFuZHNoYWtlLiBUaGUgRGlmZmllIEhlbG1hbiBrZXkgZXhjaGFuZ2UgdGFrZXMgY2FyZSBvZiBh
bGwgdGhpcy4gU2luY2UgeW91IHByb3Bvc2FsIGFsc28gY2Fubm90IHJlZGlyZWN0IGFuZCBtdXN0
IGNhcnJ5IHN0YXRlLCBJIGRvbuKAmXQgc2VlIHRoZSBwdXJwb3NlLiBJIGRvIGFncmVlIHlvdSBj
YW4gZGVsaXZlciB0aGF0IHRva2VuLCBidXQgc2luY2UgaXQgaXMgbm90IG9idmlvdXMgd2hhdCB0
aGUgdG9rZW4gaXMgbmVlZGVkIGZvciwgdGhlIHB1cnBvc2UgaXMgdW5jbGVhci48L2Rpdj4gPGRp
diBpZD0iYmxvb3Bfc2lnbl8xNTcyNjIxMjQ0MzY1NTY1OTUyIiBjbGFzcz0iYmxvb3Bfc2lnbiI+
PGRpdiBzdHlsZT0iZm9udC1mYW1pbHk6IGhlbHZldGljYSAsIGFyaWFsO2ZvbnQtc2l6ZTogMTMu
MHB4OyI+PGJyPjwvZGl2PjxkaXYgc3R5bGU9ImZvbnQtZmFtaWx5OiBoZWx2ZXRpY2EgLCBhcmlh
bDtmb250LXNpemU6IDEzLjBweDsiPllvdSBhcHBlYXIgdG8gYXNzdW1lIHRoYXQgYWRkcmVzcyB2
YWxpZGF0aW9uIG9ubHkgaGFwcGVucyBpZiB5b3UgaGF2ZSBhIFJldHJ5IHRva2VuLCBidSB0aGF0
IGlzIG5vdCBjb3JyZWN0LCBpdCBqdXN0IGhhcHBlbnMgd2l0aCBsZXNzIHNlcnZlciByZXNvdXJj
ZXMuPC9kaXY+PC9kaXY+IDxicj48cCBjbGFzcz0iYWlybWFpbF9vbiI+T24gMSBOb3ZlbWJlciAy
MDE5IGF0IDE1LjU1LjA5LCBRaW5nIEFuICg8YSBocmVmPSJtYWlsdG86YW5xaW5nLmFxQGFsaWJh
YmEtaW5jLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmFucWluZy5hcUBhbGliYWJhLWluYy5jb208L2E+
KSB3cm90ZTo8L3A+IDxibG9ja3F1b3RlIGNsYXNzPSJjbGVhbl9icSI+PHNwYW4+PGRpdj48ZGl2
PjwvZGl2PjxkaXY+CgoKCgoKPGRpdiBpZD0ibWFpbGJveC1jb252ZXJzYXRpb24iPgo8ZGl2Pjxi
cj48L2Rpdj4KPGRpdj5BZ2FpbiwgdGhlIGZhc3QgYWRkcmVzcyB2YWxpZGF0aW9uIGlzIHRvIHBy
b3ZpZGUgYW5vdGhlcgpvcHRpb24gZm9yIHNlcnZlciwgbm90IHRvIGRyb3AgdGhlIFJldHJ5IGFw
cHJvYWNoLjwvZGl2Pgo8ZGl2Pjxicj48L2Rpdj4KPGRpdj5JIHRoaW5rIGlmIGNob29zZSBub3Qg
dG8gc2VuZCBhIFJldHJ5LCBpdCBpcyBuZWNlc3NhcnkgdG8KZGVmaW5lIGhvdyB0byBkZWxpdmVy
IHRva2VuIGZyb20gc2VydmVyIHRvIGNsaWVudC4gSW4gdGhpcyBjYXNlLAombmJzcDt2aWEgbmV3
X3Rva2VuIGZyYW1lIGluIGhhbmRzaGFrZSBjYW4gYmUgYW4gYXBwcm9hY2guPC9kaXY+CjxkaXY+
PGJyPjwvZGl2Pgo8ZGl2Pjxicj48L2Rpdj4KPGJsb2NrcXVvdGU+CjxkaXY+CjxkaXYgc3R5bGU9
ImZvbnQtc2l6ZTogNzAuMCU7Ij4tLS0tLS0tLS0tLS0tLS0tLS1PcmlnaW5hbCBNYWlsCi0tLS0t
LS0tLS0tLS0tLS0tLTwvZGl2Pgo8ZGl2PjxzcGFuIGNsYXNzPSJmb3J3YXJkLWhlYWRlci10aXRs
ZSI+U2VuZGVyOjwvc3Bhbj5NaWtrZWwgRmFobsO4ZQpKw7hyZ2Vuc2VuICZsdDs8YSBocmVmPSJt
YWlsdG86bWlra2VsZmpAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+bWlra2VsZmpAZ21haWwu
Y29tPC9hPiZndDs8L2Rpdj4KPGRpdj48c3BhbiBjbGFzcz0iZm9yd2FyZC1oZWFkZXItdGl0bGUi
PlNlbmQgRGF0ZTo8L3NwYW4+RnJpIE5vdiAxCjIxOjM3OjQyIDIwMTk8L2Rpdj4KPGRpdj48c3Bh
biBjbGFzcz0iZm9yd2FyZC1oZWFkZXItdGl0bGUiPlJlY2lwaWVudHM6PC9zcGFuPlFpbmcgQW4K
Jmx0OzxhIGhyZWY9Im1haWx0bzphbnFpbmcuYXFAYWxpYmFiYS1pbmMuY29tIiB0YXJnZXQ9Il9i
bGFuayI+YW5xaW5nLmFxQGFsaWJhYmEtaW5jLmNvbTwvYT4mZ3Q7LCBNYXJ0ZW4gU2VlbWFubgom
bHQ7PGEgaHJlZj0ibWFpbHRvOm1hcnRlbnNlZW1hbm5AZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFu
ayI+bWFydGVuc2VlbWFubkBnbWFpbC5jb208L2E+Jmd0OzwvZGl2Pgo8ZGl2PjxzcGFuIGNsYXNz
PSJmb3J3YXJkLWhlYWRlci10aXRsZSI+Q0M6PC9zcGFuPmpyaS5pZXRmCiZsdDs8YSBocmVmPSJt
YWlsdG86anJpLmlldGZAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+anJpLmlldGZAZ21haWwu
Y29tPC9hPiZndDssIFFVSUMgJmx0OzxhIGhyZWY9Im1haWx0bzpxdWljLWJvdW5jZXNAaWV0Zi5v
cmciIHRhcmdldD0iX2JsYW5rIj5xdWljLWJvdW5jZXNAaWV0Zi5vcmc8L2E+Jmd0OywKcXVpYyAm
bHQ7PGEgaHJlZj0ibWFpbHRvOnF1aWNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5xdWljQGll
dGYub3JnPC9hPiZndDssIG10ICZsdDs8YSBocmVmPSJtYWlsdG86bXRAbG93ZW50cm9weS5uZXQi
IHRhcmdldD0iX2JsYW5rIj5tdEBsb3dlbnRyb3B5Lm5ldDwvYT4mZ3Q7LCDliJjlpKfpuY8o6bmP
5oiQKQombHQ7PGEgaHJlZj0ibWFpbHRvOm1heC5sZHBAYWxpYmFiYS1pbmMuY29tIiB0YXJnZXQ9
Il9ibGFuayI+bWF4LmxkcEBhbGliYWJhLWluYy5jb208L2E+Jmd0OzwvZGl2Pgo8ZGl2PjxzcGFu
IGNsYXNzPSJmb3J3YXJkLWhlYWRlci10aXRsZSI+U3ViamVjdDo8L3NwYW4+UmU6IEZhc3QKQWRk
cmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQ8L2Rpdj4KPC9kaXY+CjxkaXY+CjxibG9ja3F1b3RlIGNs
YXNzPSJnbWFpbF9xdW90ZSI+Cgo8ZGl2IGlkPSJibG9vcF9jdXN0b21mb250IiBzdHlsZT0iZm9u
dC1mYW1pbHk6IGhlbHZldGljYSAsIGFyaWFsO2ZvbnQtc2l6ZTogMTMuMHB4O21hcmdpbjogMC4w
cHg7bGluZS1oZWlnaHQ6IGF1dG87Ij4KWW91IG9ubHkgc2F2ZSBhIHJvdW5kdHJpcCBiZWNhdXNl
IHlvdSBkbyBub3Qgc2VuZCBhIFJldHJ5LjwvZGl2Pgo8ZGl2IGlkPSJibG9vcF9jdXN0b21mb250
IiBzdHlsZT0iZm9udC1mYW1pbHk6IGhlbHZldGljYSAsIGFyaWFsO2ZvbnQtc2l6ZTogMTMuMHB4
O21hcmdpbjogMC4wcHg7bGluZS1oZWlnaHQ6IGF1dG87Ij4KPGJyPjwvZGl2Pgo8ZGl2IGlkPSJi
bG9vcF9jdXN0b21mb250IiBzdHlsZT0iZm9udC1mYW1pbHk6IGhlbHZldGljYSAsIGFyaWFsO2Zv
bnQtc2l6ZTogMTMuMHB4O21hcmdpbjogMC4wcHg7bGluZS1oZWlnaHQ6IGF1dG87Ij4KSWYgeW91
IGNob29zZSBub3QgdG8gc2VuZCBhIFJldHJ5LCB0aGUgY2xpZW50IGV2ZW50dWFsbHkgZ2V0cwp2
YWxpZGF0ZWQgYW55d2F5IGJlY2F1c2Ugb3RoZXJ3aXNlIHRoZSBoYW5kc2hha2UgY291bGQgbm90
CmNvbXBsZXRlLiBUaGVyZWZvcmUgYSBSZXRyeSB0b2tlbiBpcyBub3QgbmVlZGVkIGlmIHlvdSBn
byBkb3duIHRoYXQKcGF0aC4gSW4gdGhpcyBjYXNlIHRoZSBSVFQgb3ZlcmhlYWQgd2l0aCBmYXN0
IGFkZHJlc3MgdmFsaWRhdGlvbiBpcwp0aGUgc2FtZSBhcyBvcmRpbmFyeSBRVUlDIDEtUlRUIGhh
bmRzaGFrZS48L2Rpdj4KPGRpdiBpZD0iYmxvb3BfY3VzdG9tZm9udCIgc3R5bGU9ImZvbnQtZmFt
aWx5OiBoZWx2ZXRpY2EgLCBhcmlhbDtmb250LXNpemU6IDEzLjBweDttYXJnaW46IDAuMHB4O2xp
bmUtaGVpZ2h0OiBhdXRvOyI+Cjxicj48L2Rpdj4KPGRpdiBpZD0iYmxvb3BfY3VzdG9tZm9udCIg
c3R5bGU9ImZvbnQtZmFtaWx5OiBoZWx2ZXRpY2EgLCBhcmlhbDtmb250LXNpemU6IDEzLjBweDtt
YXJnaW46IDAuMHB4O2xpbmUtaGVpZ2h0OiBhdXRvOyI+Ck9uIHRoZSBvdGhlciBoYW5kLCBpbiB0
aGUgY2FzZSB3aGVyZSBSZXRyeSBpcyBuZWVkZWQsIHRoZSBmYXN0CmFkZHJlc3MgdmFsaWRhdGlv
biBhcHByb2FjaCBkb2VzIG5vdCBzb2x2ZSB0aGUgcHJvYmxlbSB3aGljaCBpcyBvbmUKb2YgMSkg
ZGVmZXIgaGFuZHNoYWtlIHByb2Nlc3NpbmcgYW5kIHNlcnZlciBzdGF0ZSB1bnRpbCBhZnRlciB0
aGUKYWRkcmVzcyBpcyB2ZXJpZmllZCwgb3IgMikgcmVkaXJlY3QgdGhlIGNsaWVudCB0byBhbm90
aGVyIHNlcnZlcgp0aHJvdWdoIGEgY2hhbmdlIGluIENvbm5lY3Rpb25JRC48L2Rpdj4KPGRpdiBp
ZD0iYmxvb3BfY3VzdG9tZm9udCIgc3R5bGU9ImZvbnQtZmFtaWx5OiBoZWx2ZXRpY2EgLCBhcmlh
bDtmb250LXNpemU6IDEzLjBweDttYXJnaW46IDAuMHB4O2xpbmUtaGVpZ2h0OiBhdXRvOyI+Cjxi
cj48L2Rpdj4KPGRpdiBpZD0iYmxvb3Bfc2lnbl8xNTcyNjE1MTI0NjEzNDg0MDMyIiBjbGFzcz0i
Ymxvb3Bfc2lnbiI+CjxkaXYgc3R5bGU9ImZvbnQtZmFtaWx5OiBoZWx2ZXRpY2EgLCBhcmlhbDtm
b250LXNpemU6IDEzLjBweDsiPgo8YnI+PC9kaXY+CjwvZGl2Pgo8YnI+CjxwIGNsYXNzPSJhaXJt
YWlsX29uIj5PbiAxIE5vdmVtYmVyIDIwMTkgYXQgMTQuMjYuMjQsIFFpbmcgQW4KKDxhIGhyZWY9
Im1haWx0bzphbnFpbmcuYXFAYWxpYmFiYS1pbmMuY29tIiB0YXJnZXQ9Il9ibGFuayI+YW5xaW5n
LmFxQGFsaWJhYmEtaW5jLmNvbTwvYT4pIHdyb3RlOjwvcD4KPGJsb2NrcXVvdGUgY2xhc3M9ImNs
ZWFuX2JxIj4KPGRpdj4KPGRpdj4KPGRpdiBjbGFzcz0iX19hbGl5dW5fZW1haWxfYm9keV9ibG9j
ayI+CjxkaXYgc3R5bGU9ImxpbmUtaGVpZ2h0OiAxLjc7Zm9udC1mYW1pbHk6IHRhaG9tYSAsIGFy
aWFsICwgc3RoZWl0aSAsIHNpbXN1bjtmb250LXNpemU6IDE0LjBweDtjb2xvcjogIzAwMDAwMDsi
Pgo8ZGl2IHN0eWxlPSJjbGVhcjogYm90aDsiPjxzcGFuPjxicj48L3NwYW4+PC9kaXY+CjxkaXYg
c3R5bGU9ImNsZWFyOiBib3RoOyI+PHNwYW4+SSBiZWxpZXZlIHRoaXMgY2FuIHNhdmUKMS1SVFQu
PC9zcGFuPjwvZGl2Pgo8ZGl2IHN0eWxlPSJjbGVhcjogYm90aDsiPjxzcGFuPjxicj48L3NwYW4+
PC9kaXY+CjxkaXYgc3R5bGU9ImNsZWFyOiBib3RoOyI+PHNwYW4+QXMgZm9yIHRoZSBwcml2YWN5
IHJpc2ssIG5ld190b2tlbgpmcmFtZSBjYW4gYmUgZGVsaXZlcmVkIHZpYSBoYW5kc2hha2U8L3Nw
YW4+PC9kaXY+CjxkaXYgc3R5bGU9ImNsZWFyOiBib3RoOyI+PHNwYW4+PGJyPjwvc3Bhbj48L2Rp
dj4KPGRpdiBzdHlsZT0iY2xlYXI6IGJvdGg7Ij48c3Bhbj48YnI+PC9zcGFuPjwvZGl2Pgo8Ymxv
Y2txdW90ZSBzdHlsZT0ibWFyZ2luLXJpZ2h0OiAwLjBweDttYXJnaW4tdG9wOiAwLjBweDttYXJn
aW4tYm90dG9tOiAwLjBweDtmb250LWZhbWlseTogdGFob21hICwgYXJpYWwgLCBzdGhlaXRpICwg
c2ltc3VuO2ZvbnQtc2l6ZTogMTQuMHB4O2NvbG9yOiAjMDAwMDAwOyI+CjxkaXYgc3R5bGU9ImNs
ZWFyOiBib3RoOyI+CjxzcGFuPi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLTwvc3Bhbj48L2Rpdj4KPGRpdiBzdHlsZT0iY2xl
YXI6IGJvdGg7Ij48c3Bhbj5Gcm9tOk1hcnRlbiBTZWVtYW5uICZsdDs8YSBocmVmPSJtYWlsdG86
bWFydGVuc2VlbWFubkBnbWFpbC5jb20iIHRhcmdldD0iX2JsYW5rIj5tYXJ0ZW5zZWVtYW5uQGdt
YWlsLmNvbTwvYT4mZ3Q7PC9zcGFuPjwvZGl2Pgo8ZGl2IHN0eWxlPSJjbGVhcjogYm90aDsiPjxz
cGFuPlNlbmQgVGltZToyMDE55bm0MTHmnIgx5pelKOaYn+acn+S6lCkKMjA6NTQ8L3NwYW4+PC9k
aXY+CjxkaXYgc3R5bGU9ImNsZWFyOiBib3RoOyI+PHNwYW4+VG865a6J5YuNKOiOs+mAuCkgJmx0
OzxhIGhyZWY9Im1haWx0bzphbnFpbmcuYXFAYWxpYmFiYS1pbmMuY29tIiB0YXJnZXQ9Il9ibGFu
ayI+YW5xaW5nLmFxQGFsaWJhYmEtaW5jLmNvbTwvYT4mZ3Q7PC9zcGFuPjwvZGl2Pgo8ZGl2IHN0
eWxlPSJjbGVhcjogYm90aDsiPjxzcGFuPkNjOlFVSUMgJmx0OzxhIGhyZWY9Im1haWx0bzpxdWlj
LWJvdW5jZXNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5xdWljLWJvdW5jZXNAaWV0Zi5vcmc8
L2E+Jmd0OzsgcXVpYyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnF1aWNAaWV0Zi5vcmciIHRhcmdldD0i
X2JsYW5rIj5xdWljQGlldGYub3JnPC9hPiZndDs7CmpyaS5pZXRmICZsdDs8YSBocmVmPSJtYWls
dG86anJpLmlldGZAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+anJpLmlldGZAZ21haWwuY29t
PC9hPiZndDs7IG10ICZsdDs8YSBocmVmPSJtYWlsdG86bXRAbG93ZW50cm9weS5uZXQiIHRhcmdl
dD0iX2JsYW5rIj5tdEBsb3dlbnRyb3B5Lm5ldDwvYT4mZ3Q7OyBtaWtrZWxmaiAmbHQ7PGEgaHJl
Zj0ibWFpbHRvOm1pa2tlbGZqQGdtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPm1pa2tlbGZqQGdt
YWlsLmNvbTwvYT4mZ3Q7OyDliJjlpKfpuY8o6bmP5oiQKSAmbHQ7PGEgaHJlZj0ibWFpbHRvOm1h
eC5sZHBAYWxpYmFiYS1pbmMuY29tIiB0YXJnZXQ9Il9ibGFuayI+bWF4LmxkcEBhbGliYWJhLWlu
Yy5jb208L2E+Jmd0Ozwvc3Bhbj48L2Rpdj4KPGRpdiBzdHlsZT0iY2xlYXI6IGJvdGg7Ij48c3Bh
bj5TdWJqZWN0OlJlOiBGYXN0IEFkZHJlc3MgVmFsaWRhdGlvbgotIGFib3V0PC9zcGFuPjwvZGl2
Pgo8ZGl2IHN0eWxlPSJjbGVhcjogYm90aDsiPjxzcGFuPjxicj48L3NwYW4+PC9kaXY+CjxkaXY+
CjxkaXY+PHNwYW4+SSBkb24ndCBzZWUgYW55IGVuaGFuY2VkIGNsaWVudCBleHBlcmllbmNlLCBz
aW5jZSB0aGUKaGFuZHNoYWtlIHRha2VzIGV4YWN0bHkgdGhlIHNhbWUgbnVtYmVyIG9mIHJvdW5k
IHRyaXBzIHdpdGggeW91cgpwcm9wb3NhbCBhcyB3aXRoIHRoZSBjdXJyZW50IHZlcnNpb24gb2Yg
dGhlIFFVSUMKZHJhZnQuPGJyPjwvc3Bhbj48L2Rpdj4KPGRpdj48c3Bhbj5TZW5kaW5nIE5FV19U
T0tFTiBpbiBJbml0aWFsIHBhY2tldHMgcHJvdmlkZXMgbm8gYmVuZWZpdApvdmVyIHNlbmRpbmcg
aXQgaW4gMS1SVFQgcGFja2V0cywgYnV0IGNvbWVzIHdpdGggd29yc2UgcHJpdmFjeQpwcm9wZXJ0
aWVzLCBzaW5jZSBJbml0aWFsIHBhY2tldHMgYXJlIG5vdCBlbmNyeXB0ZWQgYW5kIGNhbgp0aGVy
ZWZvcmUgYmUgcmVhZCBieSBvbi1wYXRoIG9ic2VydmVycy48YnI+PC9zcGFuPjwvZGl2Pgo8L2Rp
dj4KPHNwYW4+PGJyPjwvc3Bhbj4KPGRpdiBjbGFzcz0iZ21haWxfcXVvdGUiPgo8ZGl2IGNsYXNz
PSJnbWFpbF9hdHRyIj48c3Bhbj5PbiBGcmksIE5vdiAxLCAyMDE5IGF0IDc6MzcgUE0gUWluZwpB
biAmbHQ7PGEgaHJlZj0ibWFpbHRvOmFucWluZy5hcUBhbGliYWJhLWluYy5jb20iIHRhcmdldD0i
X2JsYW5rIj5hbnFpbmcuYXFAYWxpYmFiYS1pbmMuY29tPC9hPiZndDsKd3JvdGU6PGJyPjwvc3Bh
bj48L2Rpdj4KPGRpdiBzdHlsZT0ibWFyZ2luOiAxNC4wcHggMC4wcHg7Ij4KPGRpdiBzdHlsZT0i
bGluZS1oZWlnaHQ6IDEuNztmb250LWZhbWlseTogdGFob21hICwgYXJpYWwgLCBzdGhlaXRpICwg
c2ltc3VuO2ZvbnQtc2l6ZTogMTQuMHB4O2NvbG9yOiAjMDAwMDAwOyI+CjxkaXYgc3R5bGU9ImNs
ZWFyOiBib3RoOyI+PHNwYW4+PGJyPjwvc3Bhbj48L2Rpdj4KPGRpdiBzdHlsZT0iY2xlYXI6IGJv
dGg7Ij48c3Bhbj5JZiBzbywKZjxzcGFuPm9yJm5ic3A7dGhlJm5ic3A7Zmlyc3Q8L3NwYW4+Jm5i
c3A7Y29ubmVjdGlvbiZuYnNwO2JldHdlZW4mbmJzcDtjbGllbnQmbmJzcDthbmQmbmJzcDtzZXJ2
ZXIsCnNlcnZlciBjYW4gY2hvb3NlIHRvIGVsaW1pbmF0ZSZuYnNwO3RoZSZuYnNwO3VzZSZuYnNw
O29mJm5ic3A7UmV0cnkKcGFja2V0Jm5ic3A7Zm9yJm5ic3A7dG9rZW4mbmJzcDtkZWxpdmVyeSwg
YW5kCnJlbHkmbmJzcDtvbiZuYnNwO2hhbmRzaGFrZSZuYnNwO2VuY3J5cHRpb24mbmJzcDtsYXll
ciZuYnNwO3RvCnByb3ZlJm5ic3A7cmV0dXJuIHJvdXRhYmlsaXR5LiZuYnNwOyBJbiZuYnNwO2Fk
ZGl0aW9uLCBOZXdfVG9rZW4KZnJhbWUgaXMmbmJzcDt1c2VkJm5ic3A7YnkKc2VydmVyLCZuYnNw
O3ZpYSZuYnNwO2kuZS4mbmJzcDt0aGUmbmJzcDtJbml0aWFsJm5ic3A7cGFja2V0LCZuYnNwO3Rv
Jm5ic3A7cHJvdmlkZSZuYnNwO3RoZSZuYnNwO2NsaWVudCZuYnNwO3dpdGgmbmJzcDthbgphZGRy
ZXNzJm5ic3A7dmFsaWRhdGlvbiZuYnNwO3Rva2VuJm5ic3A7dGhhdCZuYnNwO2NhbiZuYnNwO2Jl
Jm5ic3A7dXNlZCZuYnNwO3RvJm5ic3A7dmFsaWRhdGUmbmJzcDtmdXR1cmU8c3Bhbj4mbmJzcDtj
b25uZWN0aW9ucy48L3NwYW4+PC9zcGFuPjwvZGl2Pgo8ZGl2IHN0eWxlPSJjbGVhcjogYm90aDsi
PjxzcGFuPjxicj48L3NwYW4+PC9kaXY+CjxkaXYgc3R5bGU9ImNsZWFyOiBib3RoOyI+PHNwYW4+
SXQgY2FuIGVuaGFuY2UgdGhlIGV4cGVyaWVuY2UgaW4KY2xpZW50IHNpZGUgZm9yIHRoZSBmaXJz
dCBjb25uZWN0aW9uIGVzdGFibGlzaG1lbnQuPC9zcGFuPjwvZGl2Pgo8ZGl2IHN0eWxlPSJjbGVh
cjogYm90aDsiPjxzcGFuPjxicj48L3NwYW4+PC9kaXY+CjxkaXYgc3R5bGU9ImNsZWFyOiBib3Ro
OyI+PHNwYW4+SSBzdWJtaXR0ZWQgdGhlCmRyYWZ0LCZuYnNwOzxhIGhyZWY9Imh0dHBzOi8vZGF0
YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWFuLWZhc3QtYWRkcmVzcy12YWxpZGF0aW9uLyIg
dGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWFu
LWZhc3QtYWRkcmVzcy12YWxpZGF0aW9uLzwvYT48L3NwYW4+PC9kaXY+CjxkaXYgc3R5bGU9ImNs
ZWFyOiBib3RoOyI+PHNwYW4+PGJyPjwvc3Bhbj48L2Rpdj4KPGRpdiBzdHlsZT0iY2xlYXI6IGJv
dGg7Ij48c3Bhbj5RaW5nPC9zcGFuPjwvZGl2Pgo8ZGl2IHN0eWxlPSJjbGVhcjogYm90aDsiPjwv
ZGl2Pgo8ZGl2IHN0eWxlPSJjbGVhcjogYm90aDsiPjxicj48L2Rpdj4KPGRpdiBzdHlsZT0iY2xl
YXI6IGJvdGg7Ij48YnI+PC9kaXY+CjxkaXYgc3R5bGU9ImNsZWFyOiBib3RoOyI+PGJyPjwvZGl2
Pgo8ZGl2IHN0eWxlPSJjbGVhcjogYm90aDsiPgotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08L2Rpdj4KPGRpdiBzdHlsZT0i
Y2xlYXI6IGJvdGg7Ij5Gcm9tOk1pa2UgQmlzaG9wICZsdDs8YSBocmVmPSJtYWlsdG86bWJpc2hv
cEBldmVxdWVmb3UuYmUiIHRhcmdldD0iX2JsYW5rIj5tYmlzaG9wQGV2ZXF1ZWZvdS5iZTwvYT4m
Z3Q7PC9kaXY+CjxkaXYgc3R5bGU9ImNsZWFyOiBib3RoOyI+U2VuZCBUaW1lOjIwMTnlubQxMeac
iDHml6Uo5pif5pyf5LqUKSAwMDowNjwvZGl2Pgo8ZGl2IHN0eWxlPSJjbGVhcjogYm90aDsiPlRv
OuWuieWLjSjojrPpgLgpICZsdDs8YSBocmVmPSJtYWlsdG86YW5xaW5nLmFxQGFsaWJhYmEtaW5j
LmNvbSIgdGFyZ2V0PSJfYmxhbmsiPmFucWluZy5hcUBhbGliYWJhLWluYy5jb208L2E+Jmd0Ozsg
cXVpYyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnF1aWNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5x
dWljQGlldGYub3JnPC9hPiZndDs7CmpyaS5pZXRmICZsdDs8YSBocmVmPSJtYWlsdG86anJpLmll
dGZAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+anJpLmlldGZAZ21haWwuY29tPC9hPiZndDs7
IG10ICZsdDs8YSBocmVmPSJtYWlsdG86bXRAbG93ZW50cm9weS5uZXQiIHRhcmdldD0iX2JsYW5r
Ij5tdEBsb3dlbnRyb3B5Lm5ldDwvYT4mZ3Q7OyBtaWtrZWxmaiAmbHQ7PGEgaHJlZj0ibWFpbHRv
Om1pa2tlbGZqQGdtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPm1pa2tlbGZqQGdtYWlsLmNvbTwv
YT4mZ3Q7PC9kaXY+CjxkaXYgc3R5bGU9ImNsZWFyOiBib3RoOyI+U3ViamVjdDpSRTogRmFzdCBB
ZGRyZXNzIFZhbGlkYXRpb24gLQphYm91dDwvZGl2Pgo8ZGl2IHN0eWxlPSJjbGVhcjogYm90aDsi
Pjxicj48L2Rpdj4KPGRpdj4KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjogMC4w
cHg7Zm9udC1zaXplOiAxNC43cHg7Zm9udC1mYW1pbHk6IGNhbGlicmkgLCBzYW5zLXNlcmlmOyI+
CkFzIE1hcnRpbiBwb2ludGVkIG91dCBpbiB0aGUgZS1tYWlsIHlvdSByZXBsaWVkIHRvLCBpZiB0
aGUgc2VydmVyCmlzIHdpbGxpbmcgdG8gbWFpbnRhaW4gc3RhdGUsIGFueSBwYWNrZXQgYXQgdGhl
IEhhbmRzaGFrZQplbmNyeXB0aW9uIGxheWVyIHByb3ZlcyByZXR1cm4gcm91dGFiaWxpdHkuJm5i
c3A7IFRoZXJlIHNlZW1zIHRvIGJlCm5vIG5lZWQgZm9yIGEgc2VwYXJhdGUgYWRkcmVzcyB2YWxp
ZGF0aW9uIG1lY2hhbmlzbSBpZiB0aGUgc2VydmVyCmlzIHdpbGxpbmcgdG8gcHJvY2VlZCB3aXRo
IHRoZSBoYW5kc2hha2UuPC9wPgo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOiAw
LjBweDtmb250LXNpemU6IDE0LjdweDtmb250LWZhbWlseTogY2FsaWJyaSAsIHNhbnMtc2VyaWY7
Ij4KJm5ic3A7PC9wPgo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOiAwLjBweDtm
b250LXNpemU6IDE0LjdweDtmb250LWZhbWlseTogY2FsaWJyaSAsIHNhbnMtc2VyaWY7Ij4KPGI+
RnJvbTo8L2I+IFFVSUMgJmx0OzxhIGhyZWY9Im1haWx0bzpxdWljLWJvdW5jZXNAaWV0Zi5vcmci
IHRhcmdldD0iX2JsYW5rIj5xdWljLWJvdW5jZXNAaWV0Zi5vcmc8L2E+Jmd0OyA8Yj5PbiBCZWhh
bGYgT2Y8L2I+ClFpbmcgQW48YnI+CjxiPlNlbnQ6PC9iPiBUaHVyc2RheSwgT2N0b2JlciAzMSwg
MjAxOSA4OjU2IEFNPGJyPgo8Yj5Ubzo8L2I+IHF1aWMgJmx0OzxhIGhyZWY9Im1haWx0bzpxdWlj
QGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+cXVpY0BpZXRmLm9yZzwvYT4mZ3Q7OyBqcmkuaWV0
ZiAmbHQ7PGEgaHJlZj0ibWFpbHRvOmpyaS5pZXRmQGdtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsi
PmpyaS5pZXRmQGdtYWlsLmNvbTwvYT4mZ3Q7OyBtdCAmbHQ7PGEgaHJlZj0ibWFpbHRvOm10QGxv
d2VudHJvcHkubmV0IiB0YXJnZXQ9Il9ibGFuayI+bXRAbG93ZW50cm9weS5uZXQ8L2E+Jmd0Ozsg
bWlra2VsZmogJmx0OzxhIGhyZWY9Im1haWx0bzptaWtrZWxmakBnbWFpbC5jb20iIHRhcmdldD0i
X2JsYW5rIj5taWtrZWxmakBnbWFpbC5jb208L2E+Jmd0Ozxicj4KPGI+U3ViamVjdDo8L2I+IFJl
OiBGYXN0IEFkZHJlc3MgVmFsaWRhdGlvbiAtIGFib3V0PC9wPgo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibWFyZ2luOiAwLjBweDtmb250LXNpemU6IDE0LjdweDtmb250LWZhbWlseTogY2Fs
aWJyaSAsIHNhbnMtc2VyaWY7Ij4KJm5ic3A7PC9wPgo8ZGl2Pgo8ZGl2Pgo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibWFyZ2luOiAwLjBweDtmb250LXNpemU6IDE0LjdweDtmb250LWZhbWls
eTogY2FsaWJyaSAsIHNhbnMtc2VyaWY7Ij4KPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTQuMHB4
O2ZvbnQtZmFtaWx5OiB0YWhvbWEgLCBzYW5zLXNlcmlmO2NvbG9yOiBibGFjazsiPiZuYnNwOzwv
c3Bhbj48L3A+CjwvZGl2Pgo8ZGl2Pgo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2lu
OiAwLjBweDtmb250LXNpemU6IDE0LjdweDtmb250LWZhbWlseTogY2FsaWJyaSAsIHNhbnMtc2Vy
aWY7Ij4KPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTQuMHB4O2ZvbnQtZmFtaWx5OiB0YWhvbWEg
LCBzYW5zLXNlcmlmO2NvbG9yOiBibGFjazsiPiZuYnNwOzwvc3Bhbj48L3A+CjwvZGl2Pgo8ZGl2
Pgo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOiAwLjBweDtmb250LXNpemU6IDE0
LjdweDtmb250LWZhbWlseTogY2FsaWJyaSAsIHNhbnMtc2VyaWY7Ij4KPHNwYW4gc3R5bGU9ImZv
bnQtc2l6ZTogMTQuMHB4O2ZvbnQtZmFtaWx5OiB0YWhvbWEgLCBzYW5zLXNlcmlmO2NvbG9yOiBi
bGFjazsiPlRvCmNsYXJpZnksIHRoZSBwcm9wb3NhbCBpcyBub3QgdG8gcmVwbGFjZSB0aGUgZXhp
c3RpbmcgUmV0cnktYmFzZWQKdmFsaWRhdGlvbiwgYnV0IHRvIHByb3ZpZGUgYW5vdGhlciBvcHRp
b24gZm9yIHNlcnZlciB0byBkbyB0aGUKY2xpZW50IHZhbGlkYXRpb24uPC9zcGFuPjwvcD4KPC9k
aXY+CjxkaXY+CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46IDAuMHB4O2ZvbnQt
c2l6ZTogMTQuN3B4O2ZvbnQtZmFtaWx5OiBjYWxpYnJpICwgc2Fucy1zZXJpZjsiPgo8c3BhbiBz
dHlsZT0iZm9udC1zaXplOiAxNC4wcHg7Zm9udC1mYW1pbHk6IHRhaG9tYSAsIHNhbnMtc2VyaWY7
Y29sb3I6IGJsYWNrOyI+Jm5ic3A7PC9zcGFuPjwvcD4KPC9kaXY+CjxkaXY+CjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46IDAuMHB4O2ZvbnQtc2l6ZTogMTQuN3B4O2ZvbnQtZmFt
aWx5OiBjYWxpYnJpICwgc2Fucy1zZXJpZjsiPgo8c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxNC4w
cHg7Zm9udC1mYW1pbHk6IHRhaG9tYSAsIHNhbnMtc2VyaWY7Y29sb3I6IGJsYWNrOyI+SQp1bmRl
cnN0YW5kIHRoYXQgaW4gc2VydmVyIHNpZGUsIGU8c3BhbiBzdHlsZT0iYmFja2dyb3VuZDogbm9u
ZSAwLjAlIDAuMCUgcmVwZWF0IHNjcm9sbCB3aGl0ZTsiPnhjaGFuZ2luZyZuYnNwO3RoZSZuYnNw
O3Rva2VuJm5ic3A7YXQmbmJzcDt0aGUmbmJzcDtIYW5kc2hha2UmbmJzcDtlbmNyeXB0aW9uJm5i
c3A7bGV2ZWwKd2lsbCBtYWtlIHRoZSBzZXJ2ZXIgc3RhcnQgdG8gbWFpbnRhaW4gaGFuZHNoYWtl
IHN0YXRlcy4gQnV0IGluCmNsaWVudCBzaWRlLCBpdCBjYW4gYWNjZWxlcmF0ZSB0aGUgY29ubmVj
dGlvbiBlc3RhYmxpc2htZW50IGZyb20KY2xpZW50IHRvIHNlcnZlci48L3NwYW4+PC9zcGFuPjwv
cD4KPC9kaXY+CjxkaXY+CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46IDAuMHB4
O2ZvbnQtc2l6ZTogMTQuN3B4O2ZvbnQtZmFtaWx5OiBjYWxpYnJpICwgc2Fucy1zZXJpZjsiPgo8
c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxNC4wcHg7Zm9udC1mYW1pbHk6IHRhaG9tYSAsIHNhbnMt
c2VyaWY7Y29sb3I6IGJsYWNrOyI+Jm5ic3A7PC9zcGFuPjwvcD4KPC9kaXY+CjxkaXY+CjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46IDAuMHB4O2ZvbnQtc2l6ZTogMTQuN3B4O2Zv
bnQtZmFtaWx5OiBjYWxpYnJpICwgc2Fucy1zZXJpZjsiPgo8c3BhbiBzdHlsZT0iZm9udC1zaXpl
OiAxNC4wcHg7Zm9udC1mYW1pbHk6IHRhaG9tYSAsIHNhbnMtc2VyaWY7Y29sb3I6IGJsYWNrO2Jh
Y2tncm91bmQ6IG5vbmUgMC4wJSAwLjAlIHJlcGVhdCBzY3JvbGwgd2hpdGU7Ij4KQW5kIGl0IGlz
IHRoZSBzZXJ2ZXIncyBkZWNpc2lvbiB3aGV0aGVyIHRvIGV4Y2hhbmdlIHRva2VuIGluIFJldHJ5
Cm9yIGluIEhhbmRzaGFrZS4gSWYgc2VydmVyIGNob29zZXMgdG8gYWNjZXB0IHRoZSBjb3N0IGJy
b3VnaHQgYnkKdG9rZW4gZXhjaGFuZ2luZyBpbiBIYW5kc2hha2UsIGl0IHdpbGwgYnJpbmcgbW9y
ZSBlbmhhbmNlZApleHBlcmllbmNlIGluIGNsaWVudCBzaWRlLjwvc3Bhbj48L3A+CjwvZGl2Pgo8
ZGl2Pgo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOiAwLjBweDtmb250LXNpemU6
IDE0LjdweDtmb250LWZhbWlseTogY2FsaWJyaSAsIHNhbnMtc2VyaWY7Ij4KPHNwYW4gc3R5bGU9
ImZvbnQtc2l6ZTogMTQuMHB4O2ZvbnQtZmFtaWx5OiB0YWhvbWEgLCBzYW5zLXNlcmlmO2NvbG9y
OiBibGFjazsiPiZuYnNwOzwvc3Bhbj48L3A+CjwvZGl2Pgo8ZGl2Pgo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibWFyZ2luOiAwLjBweDtmb250LXNpemU6IDE0LjdweDtmb250LWZhbWlseTog
Y2FsaWJyaSAsIHNhbnMtc2VyaWY7Ij4KPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTQuMHB4O2Zv
bnQtZmFtaWx5OiB0YWhvbWEgLCBzYW5zLXNlcmlmO2NvbG9yOiBibGFjazsiPiZuYnNwOzwvc3Bh
bj48L3A+CjwvZGl2Pgo8ZGl2Pgo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luOiAw
LjBweDtmb250LXNpemU6IDE0LjdweDtmb250LWZhbWlseTogY2FsaWJyaSAsIHNhbnMtc2VyaWY7
Ij4KPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTQuMHB4O2ZvbnQtZmFtaWx5OiB0YWhvbWEgLCBz
YW5zLXNlcmlmO2NvbG9yOiBibGFjaztiYWNrZ3JvdW5kOiBub25lIDAuMCUgMC4wJSByZXBlYXQg
c2Nyb2xsIHdoaXRlOyI+CkJSLDwvc3Bhbj48L3A+CjwvZGl2Pgo8ZGl2Pgo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibWFyZ2luOiAwLjBweDtmb250LXNpemU6IDE0LjdweDtmb250LWZhbWls
eTogY2FsaWJyaSAsIHNhbnMtc2VyaWY7Ij4KPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTQuMHB4
O2ZvbnQtZmFtaWx5OiB0YWhvbWEgLCBzYW5zLXNlcmlmO2NvbG9yOiBibGFjaztiYWNrZ3JvdW5k
OiBub25lIDAuMCUgMC4wJSByZXBlYXQgc2Nyb2xsIHdoaXRlOyI+ClFpbmc8L3NwYW4+PC9wPgo8
L2Rpdj4KPGRpdj4KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjogMC4wcHg7Zm9u
dC1zaXplOiAxNC43cHg7Zm9udC1mYW1pbHk6IGNhbGlicmkgLCBzYW5zLXNlcmlmOyI+CjxzcGFu
IHN0eWxlPSJmb250LXNpemU6IDE0LjBweDtmb250LWZhbWlseTogdGFob21hICwgc2Fucy1zZXJp
Zjtjb2xvcjogYmxhY2s7Ij4mbmJzcDs8L3NwYW4+PC9wPgo8L2Rpdj4KPGRpdj4KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjogMC4wcHg7Zm9udC1zaXplOiAxNC43cHg7Zm9udC1m
YW1pbHk6IGNhbGlicmkgLCBzYW5zLXNlcmlmOyI+CjxzcGFuIHN0eWxlPSJmb250LXNpemU6IDE0
LjBweDtmb250LWZhbWlseTogdGFob21hICwgc2Fucy1zZXJpZjtjb2xvcjogYmxhY2s7Ij4mbmJz
cDs8L3NwYW4+PC9wPgo8L2Rpdj4KPGRpdiBzdHlsZT0ibWFyZ2luOiAxNC4wcHggMC4wcHg7Ij4K
PGRpdj4KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjogMC4wcHg7Zm9udC1zaXpl
OiAxNC43cHg7Zm9udC1mYW1pbHk6IGNhbGlicmkgLCBzYW5zLXNlcmlmOyI+CjxzcGFuIHN0eWxl
PSJmb250LXNpemU6IDE0LjBweDtmb250LWZhbWlseTogdGFob21hICwgc2Fucy1zZXJpZjtjb2xv
cjogYmxhY2s7Ij4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS08L3NwYW4+PC9wPgo8L2Rpdj4KPGRpdj4KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1hcmdpbjogMC4wcHg7Zm9udC1zaXplOiAxNC43cHg7Zm9udC1mYW1p
bHk6IGNhbGlicmkgLCBzYW5zLXNlcmlmOyI+CjxzcGFuIHN0eWxlPSJmb250LXNpemU6IDE0LjBw
eDtmb250LWZhbWlseTogdGFob21hICwgc2Fucy1zZXJpZjtjb2xvcjogYmxhY2s7Ij5Gcm9tOk1h
cnRpbgpUaG9tc29uICZsdDs8YSBocmVmPSJtYWlsdG86bXRAbG93ZW50cm9weS5uZXQiIHRhcmdl
dD0iX2JsYW5rIiBzdHlsZT0iY29sb3I6ICMwMDAwZmY7dGV4dC1kZWNvcmF0aW9uOiB1bmRlcmxp
bmUgIzAwMDBmZjsiPm10QGxvd2VudHJvcHkubmV0PC9hPiZndDs8L3NwYW4+PC9wPgo8L2Rpdj4K
PGRpdj4KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbjogMC4wcHg7Zm9udC1zaXpl
OiAxNC43cHg7Zm9udC1mYW1pbHk6IGNhbGlicmkgLCBzYW5zLXNlcmlmOyI+CjxzcGFuIHN0eWxl
PSJmb250LXNpemU6IDE0LjBweDtmb250LWZhbWlseTogdGFob21hICwgc2Fucy1zZXJpZjtjb2xv
cjogYmxhY2s7Ij5TZW5kClRpbWU6MjAxOTwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiAx
NC4wcHg7Zm9udC1mYW1pbHk6IG1zIGdvdGhpYztjb2xvcjogYmxhY2s7Ij7lubQ8L3NwYW4+PHNw
YW4gc3R5bGU9ImZvbnQtc2l6ZTogMTQuMHB4O2ZvbnQtZmFtaWx5OiB0YWhvbWEgLCBzYW5zLXNl
cmlmO2NvbG9yOiBibGFjazsiPjEwPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6IDE0LjBw
eDtmb250LWZhbWlseTogbXMgZ290aGljO2NvbG9yOiBibGFjazsiPuaciDwvc3Bhbj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOiAxNC4wcHg7Zm9udC1mYW1pbHk6IHRhaG9tYSAsIHNhbnMtc2VyaWY7
Y29sb3I6IGJsYWNrOyI+MzE8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTQuMHB4O2Zv
bnQtZmFtaWx5OiBtcyBnb3RoaWM7Y29sb3I6IGJsYWNrOyI+5pelPC9zcGFuPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6IDE0LjBweDtmb250LWZhbWlseTogdGFob21hICwgc2Fucy1zZXJpZjtjb2xv
cjogYmxhY2s7Ij4oPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6IDE0LjBweDtmb250LWZh
bWlseTogbXMgZ290aGljO2NvbG9yOiBibGFjazsiPuaYn+acn+Wbmzwvc3Bhbj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOiAxNC4wcHg7Zm9udC1mYW1pbHk6IHRhaG9tYSAsIHNhbnMtc2VyaWY7Y29s
b3I6IGJsYWNrOyI+KQowNjowNzwvc3Bhbj48L3A+CjwvZGl2Pgo8ZGl2Pgo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibWFyZ2luOiAwLjBweDtmb250LXNpemU6IDE0LjdweDtmb250LWZhbWls
eTogY2FsaWJyaSAsIHNhbnMtc2VyaWY7Ij4KPHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTQuMHB4
O2ZvbnQtZmFtaWx5OiB0YWhvbWEgLCBzYW5zLXNlcmlmO2NvbG9yOiBibGFjazsiPlRvOnF1aWMK
Jmx0OzxhIGhyZWY9Im1haWx0bzpxdWljQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayIgc3R5bGU9
ImNvbG9yOiAjMDAwMGZmO3RleHQtZGVjb3JhdGlvbjogdW5kZXJsaW5lICMwMDAwZmY7Ij5xdWlj
QGlldGYub3JnPC9hPiZndDs8L3NwYW4+PC9wPgo8L2Rpdj4KPGRpdj4KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1hcmdpbjogMC4wcHg7Zm9udC1zaXplOiAxNC43cHg7Zm9udC1mYW1pbHk6
IGNhbGlicmkgLCBzYW5zLXNlcmlmOyI+CjxzcGFuIHN0eWxlPSJmb250LXNpemU6IDE0LjBweDtm
b250LWZhbWlseTogdGFob21hICwgc2Fucy1zZXJpZjtjb2xvcjogYmxhY2s7Ij5TdWJqZWN0OlJl
OgpGYXN0IEFkZHJlc3MgVmFsaWRhdGlvbiAtIGFib3V0PC9zcGFuPjwvcD4KPC9kaXY+CjxkaXY+
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW46IDAuMHB4O2ZvbnQtc2l6ZTogMTQu
N3B4O2ZvbnQtZmFtaWx5OiBjYWxpYnJpICwgc2Fucy1zZXJpZjsiPgo8c3BhbiBzdHlsZT0iZm9u
dC1zaXplOiAxNC4wcHg7Zm9udC1mYW1pbHk6IHRhaG9tYSAsIHNhbnMtc2VyaWY7Y29sb3I6IGJs
YWNrOyI+Jm5ic3A7PC9zcGFuPjwvcD4KPC9kaXY+CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtYXJnaW46IDAuMHB4O2ZvbnQtc2l6ZTogMTQuN3B4O2ZvbnQtZmFtaWx5OiBjYWxpYnJpICwg
c2Fucy1zZXJpZjsiPgo8c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxNC4wcHg7Zm9udC1mYW1pbHk6
IHRhaG9tYSAsIHNhbnMtc2VyaWY7Y29sb3I6IGJsYWNrOyI+QWxzbyZuYnNwO25vdGUmbmJzcDt0
aGF0Jm5ic3A7ZXhjaGFuZ2UmbmJzcDtvZiZuYnNwO0hhbmRzaGFrZSZuYnNwO3BhY2tldHMmbmJz
cDtwcm92aWRlcyZuYnNwO3Byb29mJm5ic3A7b2YmbmJzcDtyZXR1cm4mbmJzcDtyb3V0ZWFiaWxp
dHkmbmJzcDt2aWEmbmJzcDt0aGUmbmJzcDt1c2UmbmJzcDtvZiZuYnNwO3RoZSZuYnNwO2VuY3J5
cHRpb24mbmJzcDtrZXlzLCZuYnNwO3NvJm5ic3A7dGhlcmUmbmJzcDtpcyZuYnNwO25vJm5ic3A7
bmVlZCZuYnNwO3RvJm5ic3A7ZXhjaGFuZ2UmbmJzcDt0b2tlbnMmbmJzcDthdCZuYnNwO3RoYXQm
bmJzcDtsZXZlbC48YnI+Cgo8YnI+Ck9uJm5ic3A7VGh1LCZuYnNwO09jdCZuYnNwOzMxLCZuYnNw
OzIwMTksJm5ic3A7YXQmbmJzcDswMzoyOSwmbmJzcDtNaWtlJm5ic3A7QmlzaG9wJm5ic3A7d3Jv
dGU6PGJyPgoKJmd0OyZuYnNwOyZuYnNwOzxicj4KJmd0OyZuYnNwO1RoZSZuYnNwO2FkdmFudGFn
ZSZuYnNwO29mJm5ic3A7dXNpbmcmbmJzcDtSZXRyeSwmbmJzcDtob3dldmVyLCZuYnNwO2lzJm5i
c3A7dGhhdCZuYnNwO3RoZSZuYnNwO3NlcnZlciZuYnNwO2lzJm5ic3A7YWJsZSZuYnNwO3RvJm5i
c3A7PGJyPgoKJmd0OyZuYnNwO2tlZXAmbmJzcDttaW5pbWFsJm5ic3A7KGlmJm5ic3A7YW55KSZu
YnNwO3N0YXRlJm5ic3A7YWJvdXQmbmJzcDt0aGUmbmJzcDtjbGllbnQuJm5ic3A7RXhjaGFuZ2lu
ZyZuYnNwO3RoZSZuYnNwO3Rva2VuJm5ic3A7YXQmbmJzcDs8YnI+CgomZ3Q7Jm5ic3A7dGhlJm5i
c3A7SGFuZHNoYWtlJm5ic3A7ZW5jcnlwdGlvbiZuYnNwO2xldmVsJm5ic3A7bWVhbnMmbmJzcDt0
aGUmbmJzcDtzZXJ2ZXImbmJzcDtpcyZuYnNwO2FscmVhZHkmbmJzcDtkb2luZyZuYnNwO3dvcmsm
bmJzcDs8YnI+CgomZ3Q7Jm5ic3A7YW5kJm5ic3A7bWFpbnRhaW5pbmcmbmJzcDtzdGF0ZSZuYnNw
O2luJm5ic3A7b3JkZXImbmJzcDt0byZuYnNwO3Byb2Nlc3MmbmJzcDt0aGUmbmJzcDtoYW5kc2hh
a2UsJm5ic3A7d2hpY2gmbmJzcDtpcyZuYnNwOzxicj4KCiZndDsmbmJzcDtleGFjdGx5Jm5ic3A7
d2hhdCZuYnNwO3RoZSZuYnNwO3NlcnZlciZuYnNwO2lzJm5ic3A7dHJ5aW5nJm5ic3A7dG8mbmJz
cDthdm9pZC48YnI+CgomZ3Q7Jm5ic3A7PGJyPgomZ3Q7Jm5ic3A7PGJyPgomZ3Q7Jm5ic3A7KkZy
b206KiZuYnNwO1FVSUMmbmJzcDsmbHQ7PGEgaHJlZj0ibWFpbHRvOnF1aWMtYm91bmNlc0BpZXRm
Lm9yZyIgdGFyZ2V0PSJfYmxhbmsiIHN0eWxlPSJjb2xvcjogIzAwMDBmZjt0ZXh0LWRlY29yYXRp
b246IHVuZGVybGluZSAjMDAwMGZmOyI+cXVpYy1ib3VuY2VzQGlldGYub3JnPC9hPiZndDsmbmJz
cDsqT24mbmJzcDtCZWhhbGYmbmJzcDtPZiZuYnNwOyombmJzcDtRaW5nJm5ic3A7QW48YnI+Cgom
Z3Q7Jm5ic3A7KlNlbnQ6KiZuYnNwO1dlZG5lc2RheSwmbmJzcDtPY3RvYmVyJm5ic3A7MzAsJm5i
c3A7MjAxOSZuYnNwOzk6NDEmbmJzcDtBTTxicj4KCiZndDsmbmJzcDsqVG86KiZuYnNwO3F1aWMm
bmJzcDsmbHQ7PGEgaHJlZj0ibWFpbHRvOnF1aWNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIiBz
dHlsZT0iY29sb3I6ICMwMDAwZmY7dGV4dC1kZWNvcmF0aW9uOiB1bmRlcmxpbmUgIzAwMDBmZjsi
PnF1aWNAaWV0Zi5vcmc8L2E+Jmd0OzsmbmJzcDtqcmkuaWV0ZiZuYnNwOyZsdDs8YSBocmVmPSJt
YWlsdG86anJpLmlldGZAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayIgc3R5bGU9ImNvbG9yOiAj
MDAwMGZmO3RleHQtZGVjb3JhdGlvbjogdW5kZXJsaW5lICMwMDAwZmY7Ij5qcmkuaWV0ZkBnbWFp
bC5jb208L2E+Jmd0OzsmbmJzcDttdCZuYnNwOzxicj4KCiZndDsmbmJzcDsmbHQ7PGEgaHJlZj0i
bWFpbHRvOm10QGxvd2VudHJvcHkubmV0IiB0YXJnZXQ9Il9ibGFuayIgc3R5bGU9ImNvbG9yOiAj
MDAwMGZmO3RleHQtZGVjb3JhdGlvbjogdW5kZXJsaW5lICMwMDAwZmY7Ij5tdEBsb3dlbnRyb3B5
Lm5ldDwvYT4mZ3Q7PGJyPgoKJmd0OyZuYnNwOypDYzoqJm5ic3A7PC9zcGFuPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6IDE0LjBweDtmb250LWZhbWlseTogbXMgZ290aGljO2NvbG9yOiBibGFjazsi
PuWImOWkpzwvc3Bhbj48c3BhbiBzdHlsZT0iZm9udC1zaXplOiAxNC4wcHg7Zm9udC1mYW1pbHk6
IG1pY3Jvc29mdCBqaGVuZ2hlaSAsIHNhbnMtc2VyaWY7Y29sb3I6IGJsYWNrOyI+6bmPPC9zcGFu
PjxzcGFuIHN0eWxlPSJmb250LXNpemU6IDE0LjBweDtmb250LWZhbWlseTogdGFob21hICwgc2Fu
cy1zZXJpZjtjb2xvcjogYmxhY2s7Ij4oPC9zcGFuPjxzcGFuIHN0eWxlPSJmb250LXNpemU6IDE0
LjBweDtmb250LWZhbWlseTogbWljcm9zb2Z0IGpoZW5naGVpICwgc2Fucy1zZXJpZjtjb2xvcjog
YmxhY2s7Ij7puY/miJA8L3NwYW4+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZTogMTQuMHB4O2ZvbnQt
ZmFtaWx5OiB0YWhvbWEgLCBzYW5zLXNlcmlmO2NvbG9yOiBibGFjazsiPikmbmJzcDsmbHQ7PGEg
aHJlZj0ibWFpbHRvOm1heC5sZHBAYWxpYmFiYS1pbmMuY29tIiB0YXJnZXQ9Il9ibGFuayIgc3R5
bGU9ImNvbG9yOiAjMDAwMGZmO3RleHQtZGVjb3JhdGlvbjogdW5kZXJsaW5lICMwMDAwZmY7Ij5t
YXgubGRwQGFsaWJhYmEtaW5jLmNvbTwvYT4mZ3Q7PGJyPgoKJmd0OyZuYnNwOypTdWJqZWN0Oiom
bmJzcDtGYXN0Jm5ic3A7QWRkcmVzcyZuYnNwO1ZhbGlkYXRpb24mbmJzcDstJm5ic3A7YWJvdXQ8
YnI+CgomZ3Q7Jm5ic3A7PGJyPgomZ3Q7Jm5ic3A7PGJyPgomZ3Q7Jm5ic3A7PGJyPgomZ3Q7Jm5i
c3A7PGJyPgomZ3Q7Jm5ic3A7SGkmbmJzcDtNYXJ0aW4sJm5ic3A7SmFuYSwmbmJzcDs8YnI+CiZn
dDsmbmJzcDs8YnI+CiZndDsmbmJzcDtJJm5ic3A7cmVhZCZuYnNwO3Rocm91Z2gmbmJzcDs8YSBo
cmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9pZC9kcmFmdC1pZXRmLXF1aWMtdHJhbnNwb3J0LTIz
LnR4dCIgdGFyZ2V0PSJfYmxhbmsiIHN0eWxlPSJjb2xvcjogIzAwMDBmZjt0ZXh0LWRlY29yYXRp
b246IHVuZGVybGluZSAjMDAwMGZmOyI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvaWQvZHJhZnQtaWV0
Zi1xdWljLXRyYW5zcG9ydC0yMy50eHQ8L2E+Jm5ic3A7PGJyPgoKJmd0OyZuYnNwO2FuZCZuYnNw
O2hhdmUmbmJzcDthJm5ic3A7ZmV3Jm5ic3A7Y29tbWVudHMmbmJzcDthbmQmbmJzcDtpZGVhcyZu
YnNwO3RvJm5ic3A7ZGlzY3Vzcy48YnI+CgomZ3Q7Jm5ic3A7PGJyPgomZ3Q7Jm5ic3A7PGJyPgom
Z3Q7Jm5ic3A7W1FVSUMtVHJhbnNdJm5ic3A7ZGVmaW5lcyZuYnNwO2EmbmJzcDt0b2tlbiZuYnNw
O2Jhc2VkJm5ic3A7c2NoZW1lJm5ic3A7dG8mbmJzcDtmYWNpbGl0YXRlJm5ic3A7YWRkcmVzcyZu
YnNwOzxicj4KCiZndDsmbmJzcDt2YWxpZGF0aW9uJm5ic3A7b2YmbmJzcDthJm5ic3A7Y2xpZW50
LiZuYnNwO1RoZSZuYnNwO3Rva2VuJm5ic3A7TVVTVCZuYnNwO2JlJm5ic3A7Y292ZXJlZCZuYnNw
O2J5Jm5ic3A7aW50ZWdyaXR5Jm5ic3A7PGJyPgoKJmd0OyZuYnNwO3Byb3RlY3Rpb24mbmJzcDth
Z2FpbnN0Jm5ic3A7bW9kaWZpY2F0aW9uJm5ic3A7b3ImbmJzcDtmYWxzaWZpY2F0aW9uJm5ic3A7
YnkmbmJzcDtjbGllbnRzLiZuYnNwO1RoZSZuYnNwO3NlcnZlciZuYnNwOzxicj4KCiZndDsmbmJz
cDtyZW1lbWJlcnMmbmJzcDt0aGUmbmJzcDt2YWx1ZSZuYnNwO2l0Jm5ic3A7c2VuZHMmbmJzcDt0
byZuYnNwO2NsaWVudHMmbmJzcDthbmQmbmJzcDt2YWxpZGF0ZXMmbmJzcDt0aGUmbmJzcDt0b2tl
biZuYnNwO3NlbnQmbmJzcDs8YnI+CgomZ3Q7Jm5ic3A7YmFjayZuYnNwO2Zyb20mbmJzcDthJm5i
c3A7Y2xpZW50LiZuYnNwO0luJm5ic3A7aXRzJm5ic3A7ZGVzaWduLCZuYnNwO1JldHJ5Jm5ic3A7
cGFja2V0Jm5ic3A7aXMmbmJzcDt1c2VkJm5ic3A7dG8mbmJzcDtkZWxpdmVyJm5ic3A7dGhlJm5i
c3A7PGJyPgoKJmd0OyZuYnNwO3Rva2VuJm5ic3A7dG8mbmJzcDthJm5ic3A7Y2xpZW50Jm5ic3A7
d2hpY2gmbmJzcDthZGRyZXNzJm5ic3A7aGFzJm5ic3A7bm90Jm5ic3A7eWV0Jm5ic3A7YmVlbiZu
YnNwO3ZhbGlkYXRlZC4mbmJzcDtJdCZuYnNwO3ZvaWRzJm5ic3A7PGJyPgoKJmd0OyZuYnNwO3Ro
ZSZuYnNwO2ZpcnN0Jm5ic3A7dHJhbnNtaXNzaW9uJm5ic3A7b2YmbmJzcDt0aGUmbmJzcDtJbml0
aWFsJm5ic3A7cGFja2V0Jm5ic3A7c2VudCZuYnNwO2J5Jm5ic3A7dGhlJm5ic3A7Y2xpZW50LCZu
YnNwO2FuZCZuYnNwOzxicj4KCiZndDsmbmJzcDt0cmlnZ2VycyZuYnNwO2EmbmJzcDtzZWNvbmQm
bmJzcDtJbml0aWFsJm5ic3A7cGFja2V0Jm5ic3A7dG8mbmJzcDtiZSZuYnNwO3NlbnQmbmJzcDt3
aXRoJm5ic3A7dGhlJm5ic3A7dG9rZW4uJm5ic3A7VGhlJm5ic3A7PGJyPgoKJmd0OyZuYnNwO2V4
Y2hhbmdlJm5ic3A7b2YmbmJzcDt0b2tlbiZuYnNwO3dpbGwmbmJzcDtjYXVzZSZuYnNwO2xvbmdl
ciZuYnNwO2Nvbm5lY3Rpb24mbmJzcDtlc3RhYmxpc2htZW50Jm5ic3A7ZGVsYXkmbmJzcDtmb3Im
bmJzcDs8YnI+CgomZ3Q7Jm5ic3A7YSZuYnNwO2NsaWVudC48YnI+CiZndDsmbmJzcDs8YnI+CiZn
dDsmbmJzcDs8YnI+CiZndDsmbmJzcDtUbyZuYnNwO2ltcHJvdmUmbmJzcDt0aGUmbmJzcDtlZmZp
Y2llbmN5Jm5ic3A7b2YmbmJzcDthZGRyZXNzJm5ic3A7dmFsaWRhdGlvbiZuYnNwO2R1cmluZyZu
YnNwO2hhbmRzaGFrZSwmbmJzcDtvbmUmbmJzcDs8YnI+CgomZ3Q7Jm5ic3A7aWRlYSZuYnNwO2lz
Jm5ic3A7dGhhdCZuYnNwO3RoZSZuYnNwO3NhbWUmbmJzcDt0b2tlbiZuYnNwO2NhbiZuYnNwO2Jl
Jm5ic3A7ZXhjaGFuZ2VkJm5ic3A7dmlhJm5ic3A7YSZuYnNwO2RpZmZlcmVudCZuYnNwO2NvbnRh
aW5lciZuYnNwOzxicj4KCiZndDsmbmJzcDtpLmUuJm5ic3A7dGhlJm5ic3A7SGFuZHNoYWtlJm5i
c3A7cGFja2V0LCZuYnNwO3RoYXQmbmJzcDtlbGltaW5hdGVzJm5ic3A7dGhlJm5ic3A7dXNlJm5i
c3A7b2YmbmJzcDtSZXRyeSZuYnNwO3BhY2tldCZuYnNwO2ZvciZuYnNwOzxicj4KCiZndDsmbmJz
cDt0b2tlbiZuYnNwO2RlbGl2ZXJ5LiZuYnNwOzxicj4KJmd0OyZuYnNwOzxicj4KJmd0OyZuYnNw
Ozxicj4KJmd0OyZuYnNwO0kmbmJzcDthbSZuYnNwO3dvcmtpbmcmbmJzcDtvbiZuYnNwO3RoZSZu
YnNwO2NvbXBsZXRlJm5ic3A7ZHJhZnQmbmJzcDthbmQmbmJzcDt3aWxsJm5ic3A7c3VibWl0Jm5i
c3A7aXQmbmJzcDtieSZuYnNwO0ZyaWRheS4mbmJzcDtCZWZvcmUmbmJzcDs8YnI+CgomZ3Q7Jm5i
c3A7dGhhdCwmbmJzcDtob3BlJm5ic3A7dGhpcyZuYnNwO2NhbiZuYnNwO2JlJm5ic3A7ZGlzY3Vz
c2VkJm5ic3A7aW4mbmJzcDtlbWFpbCZuYnNwO2ZpcnN0Ljxicj4KCiZndDsmbmJzcDs8YnI+CiZn
dDsmbmJzcDs8YnI+CiZndDsmbmJzcDtCUiw8YnI+CiZndDsmbmJzcDs8YnI+CiZndDsmbmJzcDtR
aW5nJm5ic3A7QW48YnI+CiZndDs8L3NwYW4+PC9wPgo8L2Rpdj4KPGRpdj4KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1hcmdpbjogMC4wcHg7Zm9udC1zaXplOiAxNC43cHg7Zm9udC1mYW1p
bHk6IGNhbGlicmkgLCBzYW5zLXNlcmlmO2xpbmUtaGVpZ2h0OiAyMC4wcHg7Ij4KPHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZTogMTQuMHB4O2ZvbnQtZmFtaWx5OiB0YWhvbWEgLCBzYW5zLXNlcmlmO2Nv
bG9yOiBibGFjazsiPiZuYnNwOzwvc3Bhbj48L3A+CjwvZGl2Pgo8L2Rpdj4KPC9kaXY+CjxkaXYg
c3R5bGU9ImxpbmUtaGVpZ2h0OiAyMC4wcHg7Y2xlYXI6IGJvdGg7Ij48YnI+PC9kaXY+CjwvZGl2
Pgo8L2Rpdj4KPC9kaXY+CjwvYmxvY2txdW90ZT4KPGRpdiBzdHlsZT0ibGluZS1oZWlnaHQ6IDIw
LjBweDtjbGVhcjogYm90aDsiPjxicj48L2Rpdj4KPC9kaXY+CjwvZGl2Pgo8L2Rpdj4KPC9kaXY+
CjwvYmxvY2txdW90ZT4KPC9ibG9ja3F1b3RlPgo8L2Rpdj4KPC9ibG9ja3F1b3RlPgo8L2Rpdj4K
Cgo8L2Rpdj48L2Rpdj48L3NwYW4+PC9ibG9ja3F1b3RlPgo8L2Jsb2NrcXVvdGU+PC9kaXY+PC9i
bG9ja3F1b3RlPjwvZGl2Pg==
------=ALIBOUNDARY_82422_47432940_5dbcb16c_358c93--



From nobody Fri Nov  1 15:42:03 2019
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 35524120801 for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 15:42:02 -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, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 0VVDnLGj0Ndy for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 15:42:01 -0700 (PDT)
Received: from mx36-out10.antispamcloud.com (mx36-out10.antispamcloud.com [209.126.121.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 25FFA120861 for <quic@ietf.org>; Fri,  1 Nov 2019 15:41:59 -0700 (PDT)
Received: from xse218.mail2web.com ([66.113.196.218] helo=xse.mail2web.com) by mx62.antispamcloud.com with esmtp (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1iQfcC-00063D-0h for quic@ietf.org; Fri, 01 Nov 2019 23:41:57 +0100
Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 474cc91P3Zz1RWR for <quic@ietf.org>; Fri,  1 Nov 2019 15:41:13 -0700 (PDT)
Received: from [10.5.2.31] (helo=xmail09.myhosting.com) by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1iQfbV-0005oP-2S for quic@ietf.org; Fri, 01 Nov 2019 15:41:13 -0700
Received: (qmail 4217 invoked from network); 1 Nov 2019 22:41:12 -0000
Received: from unknown (HELO [192.168.1.101]) (Authenticated-user:_huitema@huitema.net@[172.58.43.199]) (envelope-sender <huitema@huitema.net>) by xmail09.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 1 Nov 2019 22:41:12 -0000
To: Qing An <anqing.aq@alibaba-inc.com>, =?UTF-8?Q?Mikkel_Fahn=c3=b8e_J=c3=b8rgensen?= <mikkelfj@gmail.com>, Marten Seemann <martenseemann@gmail.com>
Cc: "jri.ietf" <jri.ietf@gmail.com>, =?UTF-8?B?5YiY5aSn6bmPKOm5j+aIkCk=?= <max.ldp@alibaba-inc.com>, QUIC <quic-bounces@ietf.org>, mt <mt@lowentropy.net>, quic <quic@ietf.org>
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com> <BN6PR2201MB1700F72F3DC8F6C3CF79902CDA600@BN6PR2201MB1700.namprd22.prod.outlook.com> <bd15f357-8e7a-42af-bf28-79f7177da385@www.fastmail.com> <f55efb80-1a95-4190-84e5-b81948a7f081.anqing.aq@alibaba-inc.com> <BN6PR2201MB17005571E88F1C68769091A3DA630@BN6PR2201MB1700.namprd22.prod.outlook.com> <69d1a917-b1f9-4142-afb0-f5c67abe7334.anqing.aq@alibaba-inc.com> <CAOYVs2r0zJzbfw5L2Mck8VEJhtyfQtHwF-db5VG45HDTF0WoOQ@mail.gmail.com> <7ac8ad51-c1a2-461b-bc47-021b3875eab8.anqing.aq@alibaba-inc.com> <CAN1APddvVeqXeWCZbe9WrLrOyVOWM5-1Dg8x5B4UpNwP6YOGrA@mail.gmail.com> <8f87c3ce-d9c0-4017-be6d-4a411daeaa2d.anqing.aq@alibaba-inc.com> <CAN1APdd4WuMGAusz3EnCc4+BsT+hBfC9oMmAmhhwDc75wxMGiw@mail.gmail.com> <880446e2-3bd9-4c47-8d66-fd582c0ae473.anqing.aq@alibaba-inc.com>
From: Christian Huitema <huitema@huitema.net>
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mQENBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAG0J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PokBOQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1a5AQ0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAYkCPgQYAQIACQUCUhFfyAIb 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=
Subject: Re: Fast Address Validation - about
Message-ID: <8fd451af-9e31-37b7-5d86-f134192924d9@huitema.net>
Date: Fri, 1 Nov 2019 15:41:12 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.0
MIME-Version: 1.0
In-Reply-To: <880446e2-3bd9-4c47-8d66-fd582c0ae473.anqing.aq@alibaba-inc.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
X-Originating-IP: 66.113.196.218
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.218/32
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.218/32@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0eT2jivapI8P7M2alpZfRhCpSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDcnqpk5VeF3xR4kF6iVwRtbgN zB/4Jkrw1eDLcif59ftw3KxDQRgBQBtzvOtDKRPaU7Tmz6iKnkQL9gqsxD347235Nhqq+/HvroPq 8GSPg+5aB4itzNZ07CdqP+KMfGjQfOdU2kQFJEzfkq4ITozmM46jSvfpO+1kZkomjtjB6X5Q5Q9f RUeIpTIC2ySfqvnqLwoxlgatmaBb0rBiK9xbkDrUqzcKIief90MVLZY9LbIZh9+IQ1oS9LBn3VIP 95Jz7ujRlJ9wSMlhvaudJXZ9EIBG/qaR+8r9SKFMmPJLf850OvZYsmoVQuOIhwKLK6IKBNB4LZ0v UHHKTzJX7b1JhMjx7v77N42Z/zX3DQBtZa/0j9rMdVQseW3F+doIupqmER9E+btGG8Xk1uugE/FU 4J9TrjYo22Tif+7yfJXbGyN6EipRzMVZ5LqwTx7Vvn9SP+LiFhV9TEgXGI3XmDfDnOu9dHI/x63E XXKWrOjLtA8sNZwhM6uDR3EMnhsXoo7KPq5g2VJsEgBpGtwBzAOsUTKR6RgQ6scM/oDJnhhySxn2 gW+eKF5pnsOtFDWHKIOxmhlKb/lC+C9AijoWgc8vkIGThCScvU0cCIiHSQbmcVIh/qThZ/l9rrrK aNF1dJDcde0+sZxmlLkZlQRRl3/ru8zO9jkpm3KO2unVpqAXWIYrI/ryFSxqUAHvxLHZsF7mXPWl FdaGOH191uXjgjQN/RTaYTLUj/RFhcnr3QktcdjQ9EVfqxuasbU8tM1A2ruF1vEjHyvS2QZiR+AZ YvfxEvZFKu+ZM2mB1CpThxyaBpbeNHk15VolAGHS5rCXQKDyCQUljhSWDhWh87HBSLhNUo4qiB0X MVQG2R7iUfOzATaF5R3hQJk8CwyURYKQ0Ye0iR3bHfnMCIEU+nrglojKwJanfcoq9IsR6l/OZb9V MEM=
X-Report-Abuse-To: spam@quarantine9.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/It1z60tQfsGvxCiTZNwAkdxiZms>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 22:42:02 -0000

On 11/1/2019 3:27 PM, Qing An wrote:
> Based on discussion, the proposal is for first connection
> establishment, server chooses to eliminate Retry and rely on
> handshake. But server can also use New_Token frame via Handshake or
> Initial to deliver token for future connection.


We have discussed before that sending a token in the Initial packet is
bad for privacy and also for security, because the initial packets are
encrypted with a well known key. The current specification allows you to
send the New_Token frame in 1-RTT, whether or not the connection was
preceded by a Retry attempt.

There would be some disadvantage to sending the frame in an Handshake
packet. Many implementations stop processing the content of handshake
packets once the handshake is complete. The crypto frames would be all
received before the New_Token frame, and the new token frame would then
be ignored.

It seems simpler to keep the current specification, and transmit the
New_Token frame in 1-RTT.

-- Christian Huitema



From nobody Fri Nov  1 16:03:59 2019
Return-Path: <anqing.aq@alibaba-inc.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 C1758120861 for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 16:03:57 -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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 (1024-bit key) header.d=alibaba-inc.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 HcIwOh9lLSNC for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 16:03:55 -0700 (PDT)
Received: from out0-142.mail.aliyun.com (out0-142.mail.aliyun.com [140.205.0.142]) (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 4A1F01201CE for <quic@ietf.org>; Fri,  1 Nov 2019 16:03:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1572649432; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=TJGf4HmP7tvFUFWpTI0WfbcAaIZBJpcvgKQdVUiwJbw=; b=V9olmP/NEVJPoRLSA+Us+9jcEDdLfWzsDZEx0GsS2VL2hjRZzD0IEp9aOf7Rj333tbOBKo90EE06QMdiV5bOJ2lj2S4UFjVDZ3MQw7KT9mOZdw0pvWkj1prt6mAYt6CXqXUQ+fRf1QJ6u2ptEEQWBbTZrX3yVbCsiQqZcPvDYuw=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R291e4; CH=green; DM=||false|; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03302; MF=anqing.aq@alibaba-inc.com; NM=1; PH=DW; RN=3; SR=0; TI=alimail_ios_2.COREAPI9fb61c2e80ed45e992018ddda54005ae; 
Received: from WS-web (anqing.aq@alibaba-inc.com[alimail_ios_2.COREAPI9fb61c2e80ed45e992018ddda54005ae]) by e02c03276.eu6 at Sat, 02 Nov 2019 07:03:51 +0800
Date: Sat, 02 Nov 2019 07:03:51 +0800
From: "Qing An" <anqing.aq@alibaba-inc.com>
To: "Jana Iyengar" <jri.ietf@gmail.com>
Cc: "quic" <quic@ietf.org>, "=?UTF-8?B?5YiY5aSn6bmPKOm5j+aIkCk=?=" <max.ldp@alibaba-inc.com>
Message-ID: <abc3a804-5026-4b25-bf8f-7f23851312fb.anqing.aq@alibaba-inc.com>
Subject: =?UTF-8?B?UmU6UmU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQ=?=
X-Priority: 3
X-Mailer: [Alimail-Mailagent revision 2765257]
MIME-Version: 1.0
In-Reply-To: <CACpbDce7EU+9gTkyBnvLqinLQST42ch=SRUJe6N9ZraiakkGzw@mail.gmail.com>
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com> <BN6PR2201MB1700F72F3DC8F6C3CF79902CDA600@BN6PR2201MB1700.namprd22.prod.outlook.com> <bd15f357-8e7a-42af-bf28-79f7177da385@www.fastmail.com> <f55efb80-1a95-4190-84e5-b81948a7f081.anqing.aq@alibaba-inc.com> <BN6PR2201MB17005571E88F1C68769091A3DA630@BN6PR2201MB1700.namprd22.prod.outlook.com> <69d1a917-b1f9-4142-afb0-f5c67abe7334.anqing.aq@alibaba-inc.com> <CALZ3u+YDo7jTJzZj=W45s0zyJoun_+1gMkq7oMVM+DNRnyDZRg@mail.gmail.com>, <CACpbDce7EU+9gTkyBnvLqinLQST42ch=SRUJe6N9ZraiakkGzw@mail.gmail.com>
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_58861_4626c940_5dbcb9d7_3589f6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/m7-TfKyTt2ObxTX8QgcMr-KSEUI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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 Nov 2019 23:03:58 -0000

------=ALIBOUNDARY_58861_4626c940_5dbcb9d7_3589f6
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64

ClRoZSBwcm9wb3NhbCBpcyB0bywgaWYgc2VydmVyIGNob29zZXMgbm90IHRvIHNlbmQgYSBSZXRy
eSwgZm9yIGZpcnN0IGNvbm5lY3Rpb24sIGRlZmluZSBob3cgdG8gdXNlIG5ld190b2tlbiBmcmFt
ZSB0byBkZWxpdmVyIHRva2VuIHRvIGNsaWVudCBmb3IgZnV0dXJlIGNvbm5lY3Rpb24uCgoKCiAt
LS0tLS0tLS0tLS0tLS0tLS1PcmlnaW5hbCBNYWlsIC0tLS0tLS0tLS0tLS0tLS0tLQpTZW5kZXI6
SmFuYSBJeWVuZ2FyIDxqcmkuaWV0ZkBnbWFpbC5jb20+ClNlbmQgRGF0ZTpTYXQgTm92IDIgMDU6
MzY6MzAgMjAxOQpSZWNpcGllbnRzOlFpbmcgQW4gPGFucWluZy5hcUBhbGliYWJhLWluYy5jb20+
CkNDOnF1aWMgPHF1aWNAaWV0Zi5vcmc+LCDliJjlpKfpuY8o6bmP5oiQKSA8bWF4LmxkcEBhbGli
YWJhLWluYy5jb20+ClN1YmplY3Q6UmU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJvdXQK
ClFpbmcsCgpUaGFuayB5b3UgZm9yIHdyaXRpbmcgdXAgdGhlIGRyYWZ0LgoKQXMgc2V2ZXJhbCBv
dGhlcnMgaGF2ZSBub3RlZCwgdGhlIFJUVCBzcGVudCB3aXRoIFJldHJ5IGlzIG5vdCB1bm5lY2Vz
c2FyeSwgaXQgaXMgZnVuZGFtZW50YWwgdG8gdGhlIHB1cnBvc2Ugb2YgUmV0cnkuIElmIHRoZSBz
ZXJ2ZXIgaXMgd2lsbGluZyB0byBtYWludGFpbiBzdGF0ZSwgaXQgZG9lc24ndCBuZWVkIHRvIHNl
bmQgYSBSZXRyeSBwYWNrZXQgYXQgYWxsLiBJZiB0aGUgc2VydmVyIGlzIHdpbGxpbmcgdG8gbWFp
bnRhaW4gc3RhdGUgYW5kIHRoZXJlZm9yZSBkb2VzIG5vdCBzZW5kIGEgUmV0cnkgYXQgYWxsLCB3
aGF0IGlzIHRoZSB2YWx1ZSBvZiB5b3VyIHByb3Bvc2FsPwoKLSBqYW5hCk9uIEZyaSwgTm92IDEs
IDIwMTkgYXQgMTA6MzQgQU0gVMO2bWEgR2F2cmljaGVua292IDx4aW1hZXJhQGdtYWlsLmNvbT4g
d3JvdGU6ClBlYWNlLAoKIE9uIEZyaSwgTm92IDEsIDIwMTkgYXQgMzozNyBQTSBRaW5nIEFuIDxh
bnFpbmcuYXFAYWxpYmFiYS1pbmMuY29tPiB3cm90ZToKID4gSSBzdWJtaXR0ZWQgdGhlIGRyYWZ0
LCBodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1hbi1mYXN0LWFkZHJlc3Mt
dmFsaWRhdGlvbi8KCiBBIHF1aWNrIHJldmlldyBnb2VzIGJlbG93OgoKID4gVGhlIHNlcnZlciBy
ZW1lbWJlcnMgdGhlIHZhbHVlIGl0IHNlbmRzIHRvCiA+IGNsaWVudHMgYW5kIHZhbGlkYXRlcyB0
aGUgdG9rZW4gc2VudCBiYWNrIGZyb20gYSBjbGllbnQuCgogQXMgZGlzY3Vzc2VkIGJlZm9yZSwg
dGhpcyBkZXNjcmlwdGlvbiBvZiB0aGUgUmV0cnkgbWVjaGFuaXNtIGlzCiBpbmFjY3VyYXRlIHRv
IHRoZSBwb2ludCBpdCBkZWZlYXRzIGl0cyB2ZXJ5IHB1cnBvc2UuCgogPiBBZGRyZXNzIHZhbGlk
YXRpb24gaXMgdXNlZCBieSBRVUlDIHRvIGF2b2lkIGJlaW5nIHVzZWQgZm9yIGEgdHJhZmZpYwog
PiBhbXBsaWZpY2F0aW9uIGF0dGFjay4KCiBUaGlzIGlzIGFsc28gaW5hY2N1cmF0ZTsgdGhlIGxv
d2VyIGJvdW5kIGZvciB0aGUgSW5pdGlhbCBwYWNrZXQgc2l6ZQogcHJldmVudHMgYW1wbGlmaWNh
dGlvbi4gIFJldHJ5IHRva2VuIGlzIHRoZXJlIHRvIG1pdGlnYXRlIEluaXRpYWwKIHBhY2tldCBm
bG9vZHMuICBOZWl0aGVyIHByZXZlbnQgdHJpdmlhbCByZWZsZWN0aW9uLCBpZiB5b3Ugd2lsbC4K
CiA+IElmIHNlcnZlciBjaG9vc2VzIHRvCiA+IGFjY2VwdCB0aGUgY29zdCBicm91Z2h0IGJ5IHRv
a2VuIGV4Y2hhbmdpbmcgaW4gSGFuZHNoYWtlCiA+IFsuLl0KID4gQWRkaW5nIHRva2VuIGZpZWxk
IHRvIEhhbmRzaGFrZSBwYWNrZXQgZG9lcyBub3QgYWRkIG5ldyBzZWN1cml0eQogPiBjb25jZXJu
cy4KCiBBdCBsZWFzdCBvbmUgc2VjdXJpdHkgY29uY2VybiBJIHNlZSBoZXJlIGlzIHdoYXQgZGF0
YSB0aGUgc2VydmVyIGlzCiBleHBlY3RlZCB0byBkZXJpdmUgaXRzIGRlY2lzaW9uIHRvIGFjY2Vw
dCB0aGUgY29zdCBmcm9tLgoKIEUuZy4gd2l0aCB0aGUgYWZvcmVtZW50aW9uZWQgMzAwIE1wcHMg
SW5pdGlhbCBwYWNrZXQgZmxvb2QsIHdoYXQgaXMKIHRoZSBhcHByb3hpbWF0ZSBjb3N0IG9mIGtl
ZXBpbmcgdGhlIHN0YXRlLCBwZXIgc2Vjb25kPyAgSWYgeW91IHdvdWxkCiBqdXN0IGJlIHN0b3Jp
bmcgMTYgb2N0ZXRzIG9mIGFuIElQdjYgYWRkcmVzcyBwbHVzIDIgb2N0ZXRzIG9mIHRoZQogY2xp
ZW50J3MgZXBoZW1lcmFsIHBvcnQgZm9yIGFueSBSeCBwYWNrZXQsIHRoYXQnZCBiZSBtb3JlIHRo
YW4gNQogR2J5dGVzIG9mIFJBTSBjb25zdW1lZCAqcGVyIHNlY29uZCogb2YgdGhlIGF0dGFjaywg
bm90IGluY2x1ZGluZyB0aGUKIHBvaW50ZXJzLCBoYXNoZXMgZXRjLiAgTmV4dCwgSSBoYXZlbid0
IGV4YWN0bHkgZG9uZSB0aGUgbWF0aCwgYnV0IEkKIHRoaW5rIHRoYXQgdGhlIGRyYWZ0IGltcGxp
ZXMgdGhhdCB0aGUgc3RhdGUga2VwdCB3b3VsZCBiZSBoYXJkbHkgbGVzcwogdGhhbiBhbiBvcmRl
ciBvZiBtYWduaXR1ZGUgYmlnZ2VyIHRoYW4gdGhhdC4gIEFsc28sIHRoZSBjb3N0IG9mCiBwcm9j
ZXNzaW5nIGV2ZXJ5IHNwb29mZWQgcGFja2V0IHRocm91Z2ggdGhlIHdob2xlIGhhbmRzaGFrZSBw
aXBlbGluZSwKIGFuZCBzbyBvbi4gIEkgYmVsaWV2ZSB0aGlzIGlzIHdoZXJlIHRoZSBhdXRob3Jz
IG5lZWQgdG8gY29tZSB1cCB3aXRoCiBiZW5jaG1hcmtzIGFuZCBpbXBsZW1lbnRhdGlvbiBoaW50
cyBvbiBnYXJiYWdlIGNvbGxlY3Rpb24gbWV0aG9kcyBldGMuCgogSSBrbm93IHRoZSBhbW91bnQg
b2YgUkFNIGF2YWlsYWJsZSBpcyBkZXN0aW5lZCB0byBncm93IGJ1dCB0aGUgZmxvb2RzCiBhcmUg
bm90IGV4cGVjdGVkIHRvIHNocmluayBhbnkgdGltZSBzb29uIGp1c3QgYXMgd2VsbC4KCiAtLQog
VMO2bWEK
------=ALIBOUNDARY_58861_4626c940_5dbcb9d7_3589f6
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64

PGRpdiBpZD0ibWFpbGJveC1jb252ZXJzYXRpb24iPjxkaXY+PGJyPjwvZGl2PjxkaXY+PHNwYW4g
c3R5bGU9ImNhcmV0LWNvbG9yOiByZ2IoMCwgMCwgMCk7IGNvbG9yOiByZ2IoMCwgMCwgMCk7IGZv
bnQtZmFtaWx5OiBoZWx2ZXRpY2EsIGFyaWFsOyBmb250LXNpemU6IDEzcHg7IGZvbnQtc3R5bGU6
IG5vcm1hbDsgZm9udC12YXJpYW50LWNhcHM6IG5vcm1hbDsgZm9udC13ZWlnaHQ6IG5vcm1hbDsg
bGV0dGVyLXNwYWNpbmc6IG5vcm1hbDsgb3JwaGFuczogYXV0bzsgdGV4dC1hbGlnbjogc3RhcnQ7
IHRleHQtaW5kZW50OiAwcHg7IHRleHQtdHJhbnNmb3JtOiBub25lOyB3aGl0ZS1zcGFjZTogbm9y
bWFsOyB3aWRvd3M6IGF1dG87IHdvcmQtc3BhY2luZzogMHB4OyAtd2Via2l0LXRhcC1oaWdobGln
aHQtY29sb3I6IHJnYmEoMjYsIDI2LCAyNiwgMC4zMDE5NjEpOyAtd2Via2l0LXRleHQtc2l6ZS1h
ZGp1c3Q6IGF1dG87IC13ZWJraXQtdGV4dC1zdHJva2Utd2lkdGg6IDBweDsgYmFja2dyb3VuZC1j
b2xvcjogcmdiKDI1NSwgMjU1LCAyNTUpOyB0ZXh0LWRlY29yYXRpb246IG5vbmU7IGRpc3BsYXk6
IGlubGluZSAhaW1wb3J0YW50OyBmbG9hdDogbm9uZTsiPlRoZSBwcm9wb3NhbCBpcyB0bywgaWYg
c2VydmVyIGNob29zZXMgbm90IHRvIHNlbmQgYSBSZXRyeSwgZm9yIGZpcnN0IGNvbm5lY3Rpb24s
IGRlZmluZSBob3cgdG8gdXNlIG5ld190b2tlbiBmcmFtZSB0byBkZWxpdmVyIHRva2VuIHRvIGNs
aWVudCBmb3IgZnV0dXJlIGNvbm5lY3Rpb24uPC9zcGFuPjwvZGl2PjxkaXY+PGJyPjwvZGl2Pjxk
aXY+PGJyPjwvZGl2PjxibG9ja3F1b3RlPjxkaXY+PGRpdiBzdHlsZT0iZm9udC1zaXplOiA3MCUi
PiAtLS0tLS0tLS0tLS0tLS0tLS1PcmlnaW5hbCBNYWlsIC0tLS0tLS0tLS0tLS0tLS0tLTwvZGl2
PjxkaXY+PHNwYW4gY2xhc3M9ImZvcndhcmQtaGVhZGVyLXRpdGxlIj5TZW5kZXI6PC9zcGFuPkph
bmEgSXllbmdhciAmbHQ7anJpLmlldGZAZ21haWwuY29tJmd0OzwvZGl2PjxkaXY+PHNwYW4gY2xh
c3M9ImZvcndhcmQtaGVhZGVyLXRpdGxlIj5TZW5kIERhdGU6PC9zcGFuPlNhdCBOb3YgIDIgMDU6
MzY6MzAgMjAxOTwvZGl2PjxkaXY+PHNwYW4gY2xhc3M9ImZvcndhcmQtaGVhZGVyLXRpdGxlIj5S
ZWNpcGllbnRzOjwvc3Bhbj5RaW5nIEFuICZsdDthbnFpbmcuYXFAYWxpYmFiYS1pbmMuY29tJmd0
OzwvZGl2PjxkaXY+PHNwYW4gY2xhc3M9ImZvcndhcmQtaGVhZGVyLXRpdGxlIj5DQzo8L3NwYW4+
cXVpYyAmbHQ7cXVpY0BpZXRmLm9yZyZndDssIOWImOWkp+m5jyjpuY/miJApICZsdDttYXgubGRw
QGFsaWJhYmEtaW5jLmNvbSZndDs8L2Rpdj48ZGl2PjxzcGFuIGNsYXNzPSJmb3J3YXJkLWhlYWRl
ci10aXRsZSI+U3ViamVjdDo8L3NwYW4+UmU6IEZhc3QgQWRkcmVzcyBWYWxpZGF0aW9uIC0gYWJv
dXQ8L2Rpdj48L2Rpdj48ZGl2PjxibG9ja3F1b3RlIGNsYXNzPSJnbWFpbF9xdW90ZSI+PGRpdj5R
aW5nLDxkaXY+PGJyPjwvZGl2PjxkaXY+VGhhbmsgeW91IGZvciB3cml0aW5nIHVwIHRoZSBkcmFm
dC48L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2PkFzIHNldmVyYWwgb3RoZXJzIGhhdmUgbm90ZWQs
IHRoZSBSVFQgc3BlbnQgd2l0aCBSZXRyeSBpcyBub3QgdW5uZWNlc3NhcnksIGl0IGlzIGZ1bmRh
bWVudGFsIHRvIHRoZSBwdXJwb3NlIG9mIFJldHJ5LiBJZiB0aGUgc2VydmVyIGlzIHdpbGxpbmcg
dG8gbWFpbnRhaW4gc3RhdGUsIGl0IGRvZXNuJ3QgbmVlZCB0byBzZW5kIGEgUmV0cnkgcGFja2V0
IGF0IGFsbC4gSWYgdGhlIHNlcnZlciBpcyB3aWxsaW5nIHRvIG1haW50YWluIHN0YXRlIGFuZCB0
aGVyZWZvcmUgZG9lcyBub3Qgc2VuZCBhIFJldHJ5IGF0IGFsbCwgd2hhdCBpcyB0aGUgdmFsdWUg
b2YgeW91ciBwcm9wb3NhbD88L2Rpdj48ZGl2Pjxicj48L2Rpdj48ZGl2Pi0gamFuYTwvZGl2Pjwv
ZGl2Pjxicj48ZGl2IGNsYXNzPSJnbWFpbF9xdW90ZSI+PGRpdiBjbGFzcz0iZ21haWxfYXR0ciI+
T24gRnJpLCBOb3YgMSwgMjAxOSBhdCAxMDozNCBBTSBUw7ZtYSBHYXZyaWNoZW5rb3YgJmx0Ozxh
IGhyZWY9Im1haWx0bzp4aW1hZXJhQGdtYWlsLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPnhpbWFlcmFA
Z21haWwuY29tPC9hPiZndDsgd3JvdGU6PGJyPjwvZGl2PjxibG9ja3F1b3RlIGNsYXNzPSJnbWFp
bF9xdW90ZSIgc3R5bGU9Im1hcmdpbjogMC4wcHggMC4wcHggMC4wcHggMC44ZXg7Ym9yZGVyLWxl
ZnQ6IDEuMHB4IHNvbGlkICNjY2NjY2M7cGFkZGluZy1sZWZ0OiAxLjBleDsiPlBlYWNlLDxicj4K
PGJyPgpPbiBGcmksIE5vdiAxLCAyMDE5IGF0IDM6MzcgUE0gUWluZyBBbiAmbHQ7PGEgaHJlZj0i
bWFpbHRvOmFucWluZy5hcUBhbGliYWJhLWluYy5jb20iIHRhcmdldD0iX2JsYW5rIj5hbnFpbmcu
YXFAYWxpYmFiYS1pbmMuY29tPC9hPiZndDsgd3JvdGU6PGJyPgomZ3Q7IEkgc3VibWl0dGVkIHRo
ZSBkcmFmdCwgPGEgaHJlZj0iaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQt
YW4tZmFzdC1hZGRyZXNzLXZhbGlkYXRpb24vIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly9kYXRh
dHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtYW4tZmFzdC1hZGRyZXNzLXZhbGlkYXRpb24vPC9h
Pjxicj4KPGJyPgpBIHF1aWNrIHJldmlldyBnb2VzIGJlbG93Ojxicj4KPGJyPgomZ3Q7IFRoZSBz
ZXJ2ZXIgcmVtZW1iZXJzIHRoZSB2YWx1ZSBpdCBzZW5kcyB0bzxicj4KJmd0OyBjbGllbnRzIGFu
ZCB2YWxpZGF0ZXMgdGhlIHRva2VuIHNlbnQgYmFjayBmcm9tIGEgY2xpZW50Ljxicj4KPGJyPgpB
cyBkaXNjdXNzZWQgYmVmb3JlLCB0aGlzIGRlc2NyaXB0aW9uIG9mIHRoZSBSZXRyeSBtZWNoYW5p
c20gaXM8YnI+CmluYWNjdXJhdGUgdG8gdGhlIHBvaW50IGl0IGRlZmVhdHMgaXRzIHZlcnkgcHVy
cG9zZS48YnI+Cjxicj4KJmd0OyBBZGRyZXNzIHZhbGlkYXRpb24gaXMgdXNlZCBieSBRVUlDIHRv
IGF2b2lkIGJlaW5nIHVzZWQgZm9yIGEgdHJhZmZpYzxicj4KJmd0OyBhbXBsaWZpY2F0aW9uIGF0
dGFjay48YnI+Cjxicj4KVGhpcyBpcyBhbHNvIGluYWNjdXJhdGU7IHRoZSBsb3dlciBib3VuZCBm
b3IgdGhlIEluaXRpYWwgcGFja2V0IHNpemU8YnI+CnByZXZlbnRzIGFtcGxpZmljYXRpb24uJm5i
c3A7IFJldHJ5IHRva2VuIGlzIHRoZXJlIHRvIG1pdGlnYXRlIEluaXRpYWw8YnI+CnBhY2tldCBm
bG9vZHMuJm5ic3A7IE5laXRoZXIgcHJldmVudCB0cml2aWFsIHJlZmxlY3Rpb24sIGlmIHlvdSB3
aWxsLjxicj4KPGJyPgomZ3Q7IElmIHNlcnZlciBjaG9vc2VzIHRvPGJyPgomZ3Q7IGFjY2VwdCB0
aGUgY29zdCBicm91Z2h0IGJ5IHRva2VuIGV4Y2hhbmdpbmcgaW4gSGFuZHNoYWtlPGJyPgomZ3Q7
IFsuLl08YnI+CiZndDsgQWRkaW5nIHRva2VuIGZpZWxkIHRvIEhhbmRzaGFrZSBwYWNrZXQgZG9l
cyBub3QgYWRkIG5ldyBzZWN1cml0eTxicj4KJmd0OyBjb25jZXJucy48YnI+Cjxicj4KQXQgbGVh
c3Qgb25lIHNlY3VyaXR5IGNvbmNlcm4gSSBzZWUgaGVyZSBpcyB3aGF0IGRhdGEgdGhlIHNlcnZl
ciBpczxicj4KZXhwZWN0ZWQgdG8gZGVyaXZlIGl0cyBkZWNpc2lvbiB0byBhY2NlcHQgdGhlIGNv
c3QgZnJvbS48YnI+Cjxicj4KRS5nLiB3aXRoIHRoZSBhZm9yZW1lbnRpb25lZCAzMDAgTXBwcyBJ
bml0aWFsIHBhY2tldCBmbG9vZCwgd2hhdCBpczxicj4KdGhlIGFwcHJveGltYXRlIGNvc3Qgb2Yg
a2VlcGluZyB0aGUgc3RhdGUsIHBlciBzZWNvbmQ/Jm5ic3A7IElmIHlvdSB3b3VsZDxicj4KanVz
dCBiZSBzdG9yaW5nIDE2IG9jdGV0cyBvZiBhbiBJUHY2IGFkZHJlc3MgcGx1cyAyIG9jdGV0cyBv
ZiB0aGU8YnI+CmNsaWVudCdzIGVwaGVtZXJhbCBwb3J0IGZvciBhbnkgUnggcGFja2V0LCB0aGF0
J2QgYmUgbW9yZSB0aGFuIDU8YnI+CkdieXRlcyBvZiBSQU0gY29uc3VtZWQgKnBlciBzZWNvbmQq
IG9mIHRoZSBhdHRhY2ssIG5vdCBpbmNsdWRpbmcgdGhlPGJyPgpwb2ludGVycywgaGFzaGVzIGV0
Yy4mbmJzcDsgTmV4dCwgSSBoYXZlbid0IGV4YWN0bHkgZG9uZSB0aGUgbWF0aCwgYnV0IEk8YnI+
CnRoaW5rIHRoYXQgdGhlIGRyYWZ0IGltcGxpZXMgdGhhdCB0aGUgc3RhdGUga2VwdCB3b3VsZCBi
ZSBoYXJkbHkgbGVzczxicj4KdGhhbiBhbiBvcmRlciBvZiBtYWduaXR1ZGUgYmlnZ2VyIHRoYW4g
dGhhdC4mbmJzcDsgQWxzbywgdGhlIGNvc3Qgb2Y8YnI+CnByb2Nlc3NpbmcgZXZlcnkgc3Bvb2Zl
ZCBwYWNrZXQgdGhyb3VnaCB0aGUgd2hvbGUgaGFuZHNoYWtlIHBpcGVsaW5lLDxicj4KYW5kIHNv
IG9uLiZuYnNwOyBJIGJlbGlldmUgdGhpcyBpcyB3aGVyZSB0aGUgYXV0aG9ycyBuZWVkIHRvIGNv
bWUgdXAgd2l0aDxicj4KYmVuY2htYXJrcyBhbmQgaW1wbGVtZW50YXRpb24gaGludHMgb24gZ2Fy
YmFnZSBjb2xsZWN0aW9uIG1ldGhvZHMgZXRjLjxicj4KPGJyPgpJIGtub3cgdGhlIGFtb3VudCBv
ZiBSQU0gYXZhaWxhYmxlIGlzIGRlc3RpbmVkIHRvIGdyb3cgYnV0IHRoZSBmbG9vZHM8YnI+CmFy
ZSBub3QgZXhwZWN0ZWQgdG8gc2hyaW5rIGFueSB0aW1lIHNvb24ganVzdCBhcyB3ZWxsLjxicj4K
PGJyPgotLTxicj4KVMO2bWE8YnI+CjwvYmxvY2txdW90ZT48L2Rpdj4KPC9ibG9ja3F1b3RlPjwv
ZGl2PjwvYmxvY2txdW90ZT48L2Rpdj4=
------=ALIBOUNDARY_58861_4626c940_5dbcb9d7_3589f6--


From nobody Fri Nov  1 20:17:27 2019
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 BB938120B9E for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 20:17:25 -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, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 lqdJpp7ASEXC for <quic@ietfa.amsl.com>; Fri,  1 Nov 2019 20:17:24 -0700 (PDT)
Received: from mx36-out10.antispamcloud.com (mx36-out10.antispamcloud.com [209.126.121.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 2E51F120B25 for <quic@ietf.org>; Fri,  1 Nov 2019 20:17:14 -0700 (PDT)
Received: from xse212.mail2web.com ([66.113.196.212] helo=xse.mail2web.com) by mx148.antispamcloud.com with esmtp (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1iQjuZ-000lNk-RF for quic@ietf.org; Sat, 02 Nov 2019 04:17:13 +0100
Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 474kkY1PQvz38VL for <quic@ietf.org>; Fri,  1 Nov 2019 20:17:09 -0700 (PDT)
Received: from [10.5.2.17] (helo=xmail07.myhosting.com) by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1iQjuX-0005E4-22 for quic@ietf.org; Fri, 01 Nov 2019 20:17:09 -0700
Received: (qmail 12059 invoked from network); 2 Nov 2019 03:17:08 -0000
Received: from unknown (HELO [192.168.1.101]) (Authenticated-user:_huitema@huitema.net@[172.58.43.199]) (envelope-sender <huitema@huitema.net>) by xmail07.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 2 Nov 2019 03:17:08 -0000
Subject: Re: Fast Address Validation - about
To: Qing An <anqing.aq@alibaba-inc.com>, Jana Iyengar <jri.ietf@gmail.com>
Cc: =?UTF-8?B?5YiY5aSn6bmPKOm5j+aIkCk=?= <max.ldp@alibaba-inc.com>, quic <quic@ietf.org>
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com> <BN6PR2201MB1700F72F3DC8F6C3CF79902CDA600@BN6PR2201MB1700.namprd22.prod.outlook.com> <bd15f357-8e7a-42af-bf28-79f7177da385@www.fastmail.com> <f55efb80-1a95-4190-84e5-b81948a7f081.anqing.aq@alibaba-inc.com> <BN6PR2201MB17005571E88F1C68769091A3DA630@BN6PR2201MB1700.namprd22.prod.outlook.com> <69d1a917-b1f9-4142-afb0-f5c67abe7334.anqing.aq@alibaba-inc.com> <CALZ3u+YDo7jTJzZj=W45s0zyJoun_+1gMkq7oMVM+DNRnyDZRg@mail.gmail.com> <CACpbDce7EU+9gTkyBnvLqinLQST42ch=SRUJe6N9ZraiakkGzw@mail.gmail.com> <abc3a804-5026-4b25-bf8f-7f23851312fb.anqing.aq@alibaba-inc.com>
From: Christian Huitema <huitema@huitema.net>
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mQENBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAG0J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PokBOQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1a5AQ0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAYkCPgQYAQIACQUCUhFfyAIb 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: <d0a2459b-17af-fa63-eca8-704edb655fd5@huitema.net>
Date: Fri, 1 Nov 2019 20:17:09 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.0
MIME-Version: 1.0
In-Reply-To: <abc3a804-5026-4b25-bf8f-7f23851312fb.anqing.aq@alibaba-inc.com>
Content-Type: multipart/alternative; boundary="------------06DB5C2B4D564B94AF535AC2"
Content-Language: en-US
X-Originating-IP: 66.113.196.212
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.212/32
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.212/32@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.13)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0eT2jivapI8P7M2alpZfRhCpSDasLI4SayDByyq9LIhVG1YotTr4Wc2T ayDLGra4w0TNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDcnqpk5VeF3xR4kF6iVwRtbgN zB/4Jkrw1eDLcif59fuYu9lJeLmXPOBsxdg3VZ2KU7Tmz6iKnkQL9gqsxD347235Nhqq+/HvroPq 8GSPg+60/QPNqXybIny9WGhadIo/ixIHpNwYH6dG/jiqllt/T7yme9ldZJ7uNXfg/GfS8fUvP/L5 rCqHDsKZM+xa1iwJX+gRCHfMVnsAk591zk0uilUI+ZL4xWiN8NS6C+dmX6OEdA4u1aThyWrQ/ou2 +v/lmX4Em37yFgrCB6NHRn1g+f3uncIqYSL3lhh5c81YyJqFoLZMmkWsaurVZfvqROaDnDtHb8z5 dpPkEuJ8SnwqlUrBK2R/GBg9vCpMGFHw53FxnHnL50HZvyS1o3x98IkV0bm2vWdo8usP65i82q1C dZgGrpL44wdx9eXqjQjbvUopOMQJvQ/Ck3iiU+4DQAj3fuQgzT3K9JUHTNiGwfwAm2uprb+vd2Fz Rl4tm4DfGPPYb7x0LxPWX7Xb47z6RVoq+/Ns2Gna1qGxHkWdHB0MtweYUOp7A73HI6oJg7w/Vody ZOdhGVEAXrAmVqtPwyUyXNl2PZeaHdj4N+5hPjCDVF1677oPXF7r5zsW33ZNlioeEsGOJOKU/kLG nxJMOi7de34TY+s3lj/RgDQoaICKQ9Q84QG89JN6MvpNdzLqW7qgItpsB9R718A3NbXRoxutHHAS JNUmoOHSoqgqxfHmWRWcrRhLeB34s3hUb32GO+0a9cEkmc8ndMFrmbB27OjV08QV3No+S2msRDep v5w/kkG0v17AmegcpQ0tml/sN9lmMy/o83jVXTcfb9k0nLWblJy7uxV6dw8jzlsaNZe6hynMJcjx DydxsJEju76A7X1QIVydqXpZ6MHhiKws9Iiut28r9wo4SqUIg8Yh9hAM0n3LLzx/F2gT3wl8JQJv Bho=
X-Report-Abuse-To: spam@quarantine9.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/TIVVXbIOH4h6coaV-3uhXQ3-9r8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 02 Nov 2019 03:17:26 -0000

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


On 11/1/2019 4:03 PM, Qing An wrote:
>
> The proposal is to, if server chooses not to send a Retry, for first
> connection, define how to use new_token frame to deliver token to
> client for future connection.

This is already supported. Just send a "NEW TOKEN" frame in an 1 RTT
packet, once the handshake is complete. The clients should remember
that, and use it on their next connections.

-- Christian Huitema



--------------06DB5C2B4D564B94AF535AC2
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>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 11/1/2019 4:03 PM, Qing An wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:abc3a804-5026-4b25-bf8f-7f23851312fb.anqing.aq@alibaba-inc.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div id="mailbox-conversation">
        <div><br>
        </div>
        <div><span style="caret-color: rgb(0, 0, 0); color: rgb(0, 0,
            0); font-family: helvetica, arial; font-size: 13px;
            font-style: normal; font-variant-caps: normal; font-weight:
            normal; letter-spacing: normal; orphans: auto; text-align:
            start; text-indent: 0px; text-transform: none; white-space:
            normal; widows: auto; word-spacing: 0px;
            -webkit-tap-highlight-color: rgba(26, 26, 26, 0.301961);
            -webkit-text-size-adjust: auto; -webkit-text-stroke-width:
            0px; background-color: rgb(255, 255, 255); text-decoration:
            none; display: inline !important; float: none;">The proposal
            is to, if server chooses not to send a Retry, for first
            connection, define how to use new_token frame to deliver
            token to client for future connection.</span></div>
      </div>
    </blockquote>
    <br>
    <p>This is already supported. Just send a "NEW TOKEN" frame in an 1
      RTT packet, once the handshake is complete. The clients should
      remember that, and use it on their next connections.</p>
    <p>-- Christian Huitema</p>
    <br>
  </body>
</html>

--------------06DB5C2B4D564B94AF535AC2--


From nobody Fri Nov  1 23:51:16 2019
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 BAE34120AC0; Fri,  1 Nov 2019 23:51:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.986
X-Spam-Level: 
X-Spam-Status: No, score=-1.986 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_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 n4enwwkmh8Lp; Fri,  1 Nov 2019 23:51:10 -0700 (PDT)
Received: from mail-ed1-x541.google.com (mail-ed1-x541.google.com [IPv6:2a00:1450:4864:20::541]) (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 C074412089B; Fri,  1 Nov 2019 23:51:09 -0700 (PDT)
Received: by mail-ed1-x541.google.com with SMTP id b18so9128008edr.11; Fri, 01 Nov 2019 23:51: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=SJP3OI0Rry6TWCHbW4fDpmLO2qMqLuAafIi8f6VX3qc=; b=vZKUa/i6/lQ7hlUIV91fvehqFW8SDvaF1TkmZShvBvzBLv+gbBwsxCCjrjuA/FcabK DWWKhCEGXQYQtKh+VmIcL4navfZYsOoJv3Ogmf+AHWY20+bY6qYEUamX0WucbeL9pYhl wl3QgBNo5nnq6ARPgJWseXPRz0n1asskF328Ny1fmfU98TCzTxNyFngOuANy86lVu4Br kPmiXkpfR2LACycCclyay9qODMZMd+QftusKOhDK3lzgcjwgGsmVS+fsNlT2vokvZ6bf aZSWe/F5KtDko868upPmibLWaA6h3DHJHS+AEHj/lxYWtAvXNlAK96WxCvaUgNnpwPXZ tniQ==
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=SJP3OI0Rry6TWCHbW4fDpmLO2qMqLuAafIi8f6VX3qc=; b=JMGNbOmjG7WeYhTqdE5mHcbR01Br8OUaljI+E0gBBfZCH6wEKuXvKdw5XwJxRn2+Kr 50gbwEu1BcrPLJVfMnosU9kW5uZDHLUw+EcYinwQU4ynkZcrAHc3zQSTpiuhyMvwRyVP WjsRmkyjoNzQzcH5L5I7Ls0GI3ybIM/fE+cvqjVlgJtSAn5EzSJxgyoVed93uzDV+7Jw 7v1HnvE3hfpnnDS5sJY6abRv5QyJYTD3f1Cgqiuoy4JP1lrZzHHTQOyn5sYNG1QJGACJ shuBCCFrT29R2CaOUaoKK1RbPKS9RXJXik+kRj/ZGUkDCbES0kQjpgpvo0KCipSJuPWd fmcg==
X-Gm-Message-State: APjAAAUAf86dHSeIr/8Kgjk3HHWVER2thDsRfxV0tiW4+Osm52VaZEa7 LnA2yqJw/AGYgUlyLTk7w2hqR4XZvFChY3qGhJU=
X-Google-Smtp-Source: APXvYqz2++9ragbWS8TDVmqg3WfxJA6KhOil+i8zyGAXiwEY5litdjeSAgbZ9dbzAFU2ybcpvMKCWsQg5EEsabiDWuo=
X-Received: by 2002:a50:9930:: with SMTP id k45mr17122747edb.134.1572677468314;  Fri, 01 Nov 2019 23:51:08 -0700 (PDT)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Fri, 1 Nov 2019 23:51:07 -0700
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <880446e2-3bd9-4c47-8d66-fd582c0ae473.anqing.aq@alibaba-inc.com>
References: <4974ed86-0fa9-435d-880f-80af637ef180.anqing.aq@alibaba-inc.com> <BN6PR2201MB1700F72F3DC8F6C3CF79902CDA600@BN6PR2201MB1700.namprd22.prod.outlook.com> <bd15f357-8e7a-42af-bf28-79f7177da385@www.fastmail.com> <f55efb80-1a95-4190-84e5-b81948a7f081.anqing.aq@alibaba-inc.com> <BN6PR2201MB17005571E88F1C68769091A3DA630@BN6PR2201MB1700.namprd22.prod.outlook.com> <69d1a917-b1f9-4142-afb0-f5c67abe7334.anqing.aq@alibaba-inc.com> <CAOYVs2r0zJzbfw5L2Mck8VEJhtyfQtHwF-db5VG45HDTF0WoOQ@mail.gmail.com> <7ac8ad51-c1a2-461b-bc47-021b3875eab8.anqing.aq@alibaba-inc.com> <CAN1APddvVeqXeWCZbe9WrLrOyVOWM5-1Dg8x5B4UpNwP6YOGrA@mail.gmail.com> <8f87c3ce-d9c0-4017-be6d-4a411daeaa2d.anqing.aq@alibaba-inc.com> <CAN1APdd4WuMGAusz3EnCc4+BsT+hBfC9oMmAmhhwDc75wxMGiw@mail.gmail.com> <880446e2-3bd9-4c47-8d66-fd582c0ae473.anqing.aq@alibaba-inc.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Fri, 1 Nov 2019 23:51:07 -0700
Message-ID: <CAN1APdeo78H5cfoDOcwiS3AJ9mx2jYEJB3X0qD3LBP8xQYc3Vw@mail.gmail.com>
Subject: Re:Re:Re: Fast Address Validation - about
To: Qing An <anqing.aq@alibaba-inc.com>, Marten Seemann <martenseemann@gmail.com>
Cc: "jri.ietf" <jri.ietf@gmail.com>, QUIC <quic-bounces@ietf.org>, quic <quic@ietf.org>, mt <mt@lowentropy.net>, =?UTF-8?B?5YiY5aSn6bmPKOm5j+aIkCk=?= <max.ldp@alibaba-inc.com>
Content-Type: multipart/alternative; boundary="000000000000d860b50596578180"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/J-Wzzev1njtoFV2PgFh7R7UVg18>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 02 Nov 2019 06:51:14 -0000

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

I can see how a token in the initial packet can speed up a second
connection because you can drop the handshake if you do not like the token.

But isn=E2=80=99t that exactly what 0-RTT connections / tokens are supposed=
 to do?

And for delivering new tokens for future use it does not really matter if
it is delivered in the handshake from a performance perspective because 1)
you are likely to continue doing more work anyway, and 2) if not, you still
need to confirm the handshake before trusting the connection, and 3)
coalescing 1-RTT packets are not usually slower than sending in handshake.

>From a security perspective there are other concerns as Christian has
discussed.

Delivering Retry tokens for future use (as you mention your next mail) may
be problematic due to life time concerns. 0-RTT tokens are expected to live
longer than Retry and Retry tokens and the Connection ID associated with
it, reflects the current server farms load such that new connections can
redirect immediately, not sometime later.

On 1 November 2019 at 23.28.03, Qing An (anqing.aq@alibaba-inc.com) wrote:


Based on discussion, the proposal is for first connection establishment,
server chooses to eliminate Retry and rely on handshake. But server can
also use New_Token frame via Handshake or Initial to deliver token for
future connection.


------------------Original Mail ------------------
Sender:Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@gmail.com>
Send Date:Fri Nov 1 23:19:30 2019
Recipients:Qing An <anqing.aq@alibaba-inc.com>, Marten Seemann <
martenseemann@gmail.com>
CC:jri.ietf <jri.ietf@gmail.com>, QUIC <quic-bounces@ietf.org>, quic <
quic@ietf.org>, mt <mt@lowentropy.net>, =E5=88=98=E5=A4=A7=E9=B9=8F(=E9=B9=
=8F=E6=88=90) <max.ldp@alibaba-inc.com>
Subject:Re:Re: Fast Address Validation - about

> But what do you need to the token for in this case? The token is to prove
> that you previously spoken to the server. But the TLS handshake provides
> the same proof (but cannot redirect and must carry state). Any additional
> information the token might carry is only interesting in Initial packets
> where the connection can be stopped early or (in ongoing work) to encrypt
> the initial packet. That is not relevant during handshake. The Diffie
> Helman key exchange takes care of all this. Since you proposal also canno=
t
> redirect and must carry state, I don=E2=80=99t see the purpose. I do agre=
e you can
> deliver that token, but since it is not obvious what the token is needed
> for, the purpose is unclear.
>
> You appear to assume that address validation only happens if you have a
> Retry token, bu that is not correct, it just happens with less server
> resources.
>
> On 1 November 2019 at 15.55.09, Qing An (anqing.aq@alibaba-inc.com) wrote=
:
>
>
> Again, the fast address validation is to provide another option for
> server, not to drop the Retry approach.
>
> I think if choose not to send a Retry, it is necessary to define how to
> deliver token from server to client. In this case,  via new_token frame i=
n
> handshake can be an approach.
>
>
> ------------------Original Mail ------------------
> Sender:Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@gmail.com>
> Send Date:Fri Nov 1 21:37:42 2019
> Recipients:Qing An <anqing.aq@alibaba-inc.com>, Marten Seemann <
> martenseemann@gmail.com>
> CC:jri.ietf <jri.ietf@gmail.com>, QUIC <quic-bounces@ietf.org>, quic <
> quic@ietf.org>, mt <mt@lowentropy.net>, =E5=88=98=E5=A4=A7=E9=B9=8F(=E9=
=B9=8F=E6=88=90) <max.ldp@alibaba-inc.com>
> Subject:Re: Fast Address Validation - about
>
>> You only save a roundtrip because you do not send a Retry.
>>
>> If you choose not to send a Retry, the client eventually gets validated
>> anyway because otherwise the handshake could not complete. Therefore a
>> Retry token is not needed if you go down that path. In this case the RTT
>> overhead with fast address validation is the same as ordinary QUIC 1-RTT
>> handshake.
>>
>> On the other hand, in the case where Retry is needed, the fast address
>> validation approach does not solve the problem which is one of 1) defer
>> handshake processing and server state until after the address is verifie=
d,
>> or 2) redirect the client to another server through a change in
>> ConnectionID.
>>
>>
>>
>> On 1 November 2019 at 14.26.24, Qing An (anqing.aq@alibaba-inc.com)
>> wrote:
>>
>>
>> I believe this can save 1-RTT.
>>
>> As for the privacy risk, new_token frame can be delivered via handshake
>>
>>
>> ------------------------------------------------------------------
>> From:Marten Seemann <martenseemann@gmail.com>
>> Send Time:2019=E5=B9=B411=E6=9C=881=E6=97=A5(=E6=98=9F=E6=9C=9F=E4=BA=94=
) 20:54
>> To:=E5=AE=89=E5=8B=8D(=E8=8E=B3=E9=80=B8) <anqing.aq@alibaba-inc.com>
>> Cc:QUIC <quic-bounces@ietf.org>; quic <quic@ietf.org>; jri.ietf <
>> jri.ietf@gmail.com>; mt <mt@lowentropy.net>; mikkelfj <mikkelfj@gmail.co=
m>;
>> =E5=88=98=E5=A4=A7=E9=B9=8F(=E9=B9=8F=E6=88=90) <max.ldp@alibaba-inc.com=
>
>> Subject:Re: Fast Address Validation - about
>>
>> I don't see any enhanced client experience, since the handshake takes
>> exactly the same number of round trips with your proposal as with the
>> current version of the QUIC draft.
>> Sending NEW_TOKEN in Initial packets provides no benefit over sending it
>> in 1-RTT packets, but comes with worse privacy properties, since Initial
>> packets are not encrypted and can therefore be read by on-path observers=
.
>>
>> On Fri, Nov 1, 2019 at 7:37 PM Qing An <anqing.aq@alibaba-inc.com> wrote=
:
>>
>> If so, for the first connection between client and server, server can
>> choose to eliminate the use of Retry packet for token delivery, and
>> rely on handshake encryption layer to prove return routability.
>> In addition, New_Token frame is used by
>> server, via i.e. the Initial packet, to provide the client with an
>> address validation token that can be used to validate future connections=
.
>>
>> It can enhance the experience in client side for the first connection
>> establishment.
>>
>> I submitted the draft,
>> https://datatracker.ietf.org/doc/draft-an-fast-address-validation/
>>
>> Qing
>>
>>
>>
>> ------------------------------------------------------------------
>> From:Mike Bishop <mbishop@evequefou.be>
>> Send Time:2019=E5=B9=B411=E6=9C=881=E6=97=A5(=E6=98=9F=E6=9C=9F=E4=BA=94=
) 00:06
>> To:=E5=AE=89=E5=8B=8D(=E8=8E=B3=E9=80=B8) <anqing.aq@alibaba-inc.com>; q=
uic <quic@ietf.org>; jri.ietf <
>> jri.ietf@gmail.com>; mt <mt@lowentropy.net>; mikkelfj <mikkelfj@gmail.co=
m
>> >
>> Subject:RE: Fast Address Validation - about
>>
>> As Martin pointed out in the e-mail you replied to, if the server is
>> willing to maintain state, any packet at the Handshake encryption layer
>> proves return routability.  There seems to be no need for a separate
>> address validation mechanism if the server is willing to proceed with th=
e
>> handshake.
>>
>>
>>
>> *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of* Qing An
>> *Sent:* Thursday, October 31, 2019 8:56 AM
>> *To:* quic <quic@ietf.org>; jri.ietf <jri.ietf@gmail.com>; mt <
>> mt@lowentropy.net>; mikkelfj <mikkelfj@gmail.com>
>> *Subject:* Re: Fast Address Validation - about
>>
>>
>>
>>
>>
>>
>>
>> To clarify, the proposal is not to replace the existing Retry-based
>> validation, but to provide another option for server to do the client
>> validation.
>>
>>
>>
>> I understand that in server side, exchanging the token at the Handshake =
encryption level
>> will make the server start to maintain handshake states. But in client
>> side, it can accelerate the connection establishment from client to serv=
er.
>>
>>
>>
>> And it is the server's decision whether to exchange token in Retry or in
>> Handshake. If server chooses to accept the cost brought by token exchang=
ing
>> in Handshake, it will bring more enhanced experience in client side.
>>
>>
>>
>>
>>
>> BR,
>>
>> Qing
>>
>>
>>
>>
>>
>> ------------------------------------------------------------------
>>
>> From:Martin Thomson <mt@lowentropy.net>
>>
>> Send Time:2019=E5=B9=B410=E6=9C=8831=E6=97=A5(=E6=98=9F=E6=9C=9F=E5=9B=
=9B) 06:07
>>
>> To:quic <quic@ietf.org>
>>
>> Subject:Re: Fast Address Validation - about
>>
>>
>>
>>
>> Also note that exchange of Handshake packets provides proof of return ro=
uteability via the use of the encryption keys, so there is no need to excha=
nge tokens at that level.
>>
>> On Thu, Oct 31, 2019, at 03:29, Mike Bishop wrote:
>> >
>> > The advantage of using Retry, however, is that the server is able to
>> > keep minimal (if any) state about the client. Exchanging the token at
>> > the Handshake encryption level means the server is already doing work
>> > and maintaining state in order to process the handshake, which is
>> > exactly what the server is trying to avoid.
>> >
>> >
>> > *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of * Qing An
>> > *Sent:* Wednesday, October 30, 2019 9:41 AM
>> > *To:* quic <quic@ietf.org>; jri.ietf <jri.ietf@gmail.com>; mt
>> > <mt@lowentropy.net>
>> > *Cc:* =E5=88=98=E5=A4=A7=E9=B9=8F(=E9=B9=8F=E6=88=90) <max.ldp@alibaba=
-inc.com>
>> > *Subject:* Fast Address Validation - about
>> >
>> >
>> >
>> >
>> > Hi Martin, Jana,
>> >
>> > I read through https://www.ietf.org/id/draft-ietf-quic-transport-23.tx=
t
>>
>> > and have a few comments and ideas to discuss.
>> >
>> >
>> > [QUIC-Trans] defines a token based scheme to facilitate address
>> > validation of a client. The token MUST be covered by integrity
>> > protection against modification or falsification by clients. The serve=
r
>> > remembers the value it sends to clients and validates the token sent
>> > back from a client. In its design, Retry packet is used to deliver the
>> > token to a client which address has not yet been validated. It voids
>> > the first transmission of the Initial packet sent by the client, and
>> > triggers a second Initial packet to be sent with the token. The
>> > exchange of token will cause longer connection establishment delay for
>> > a client.
>> >
>> >
>> > To improve the efficiency of address validation during handshake, one
>> > idea is that the same token can be exchanged via a different container
>> > i.e. the Handshake packet, that eliminates the use of Retry packet for
>> > token delivery.
>> >
>> >
>> > I am working on the complete draft and will submit it by Friday. Befor=
e
>> > that, hope this can be discussed in email first.
>> >
>> >
>> > BR,
>> >
>> > Qing An
>> >
>>
>>
>>
>>
>>

--000000000000d860b50596578180
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">I can see how a toke=
n in the initial packet can speed up a second connection because you can dr=
op the handshake if you do not like the token.</div><div id=3D"bloop_custom=
font" 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" st=
yle=3D"font-family:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);mar=
gin:0px;line-height:auto">But isn=E2=80=99t that exactly what 0-RTT connect=
ions / tokens are supposed to do?</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;lin=
e-height:auto">And for delivering new tokens for future use it does not rea=
lly matter if it is delivered in the handshake from a performance perspecti=
ve because 1) you are likely to continue doing more work anyway, and 2) if =
not, you still need to confirm the handshake before trusting the connection=
, and 3) coalescing 1-RTT packets are not usually slower than sending in ha=
ndshake.</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_sign_1572676888210266112" class=3D"bloop_sign"><div=
 style=3D"font-family:helvetica,arial;font-size:13px">From a security persp=
ective there are other concerns as Christian has discussed.</div></div> <di=
v><br></div>Delivering Retry tokens for future use (as you mention your nex=
t mail) may be problematic due to life time concerns. 0-RTT tokens are expe=
cted to live longer than Retry and Retry tokens and the Connection ID assoc=
iated with it, reflects the current server farms load such that new connect=
ions can redirect immediately, not sometime later.<div><br></div><div><p cl=
ass=3D"airmail_on">On 1 November 2019 at 23.28.03, Qing An (<a href=3D"mail=
to:anqing.aq@alibaba-inc.com">anqing.aq@alibaba-inc.com</a>) wrote:</p> <bl=
ockquote type=3D"cite" class=3D"clean_bq"><span><div><div></div><div>


<title></title>


<div id=3D"mailbox-conversation">
<div><br></div>
<div>Based on discussion, the proposal is for first connection
establishment, server chooses to eliminate Retry and rely on
handshake. But server can also use New_Token frame via Handshake or
Initial to deliver token for future connection.</div>
<div><br></div>
<div><br></div>
<blockquote>
<div>
<div style=3D"font-size:70%">------------------Original Mail
------------------</div>
<div><span class=3D"forward-header-title">Sender:</span>Mikkel Fahn=C3=B8e
J=C3=B8rgensen &lt;<a href=3D"mailto:mikkelfj@gmail.com">mikkelfj@gmail.com=
</a>&gt;</div>
<div><span class=3D"forward-header-title">Send Date:</span>Fri Nov 1
23:19:30 2019</div>
<div><span class=3D"forward-header-title">Recipients:</span>Qing An
&lt;<a href=3D"mailto:anqing.aq@alibaba-inc.com">anqing.aq@alibaba-inc.com<=
/a>&gt;, Marten Seemann
&lt;<a href=3D"mailto:martenseemann@gmail.com">martenseemann@gmail.com</a>&=
gt;</div>
<div><span class=3D"forward-header-title">CC:</span>jri.ietf
&lt;<a href=3D"mailto:jri.ietf@gmail.com">jri.ietf@gmail.com</a>&gt;, QUIC =
&lt;<a href=3D"mailto:quic-bounces@ietf.org">quic-bounces@ietf.org</a>&gt;,
quic &lt;<a href=3D"mailto:quic@ietf.org">quic@ietf.org</a>&gt;, mt &lt;<a =
href=3D"mailto:mt@lowentropy.net">mt@lowentropy.net</a>&gt;, =E5=88=98=E5=
=A4=A7=E9=B9=8F(=E9=B9=8F=E6=88=90)
&lt;<a href=3D"mailto:max.ldp@alibaba-inc.com">max.ldp@alibaba-inc.com</a>&=
gt;</div>
<div><span class=3D"forward-header-title">Subject:</span>Re:Re: Fast
Address Validation - about</div>
</div>
<div>
<blockquote class=3D"gmail_quote">

<div id=3D"bloop_customfont" style=3D"font-family: helvetica , arial;font-s=
ize: 13.0px;color: ;margin: 0.0px;line-height: auto;">
But what do you need to the token for in this case? The token is to
prove that you previously spoken to the server. But the TLS
handshake provides the same proof (but cannot redirect and must
carry state). Any additional information the token might carry is
only interesting in Initial packets where the connection can be
stopped early or (in ongoing work) to encrypt the initial packet.
That is not relevant during handshake. The Diffie Helman key
exchange takes care of all this. Since you proposal also cannot
redirect and must carry state, I don=E2=80=99t see the purpose. I do agree
you can deliver that token, but since it is not obvious what the
token is needed for, the purpose is unclear.</div>
<div id=3D"bloop_sign_1572621244365565952" class=3D"bloop_sign">
<div style=3D"font-family:helvetica,arial;font-size:13.0px">
<br></div>
<div style=3D"font-family:helvetica,arial;font-size:13.0px">You
appear to assume that address validation only happens if you have a
Retry token, bu that is not correct, it just happens with less
server resources.</div>
</div>
<br>
<p class=3D"airmail_on">On 1 November 2019 at 15.55.09, Qing An
(<a href=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_blank">anqing.aq@a=
libaba-inc.com</a>) wrote:</p>
<blockquote class=3D"clean_bq">
<div>
<div>
<div id=3D"mailbox-conversation">
<div><span><br></span></div>
<div><span>Again, the fast address validation is to provide another
option for server, not to drop the Retry approach.</span></div>
<div><span><br></span></div>
<div><span>I think if choose not to send a Retry, it is necessary
to define how to deliver token from server to client. In this case,
=C2=A0via new_token frame in handshake can be an
approach.</span></div>
<div><span><br></span></div>
<div><span><br></span></div>
<blockquote>
<div>
<div style=3D"font-size:70.0%"><span>------------------Original
Mail ------------------</span></div>
<div><span><span class=3D"forward-header-title">Sender:</span>Mikkel
Fahn=C3=B8e J=C3=B8rgensen &lt;<a href=3D"mailto:mikkelfj@gmail.com" target=
=3D"_blank">mikkelfj@gmail.com</a>&gt;</span></div>
<div><span class=3D"forward-header-title">Send Date:</span>Fri Nov 1
21:37:42 2019</div>
<div><span class=3D"forward-header-title">Recipients:</span>Qing An
&lt;<a href=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_blank">anqing.a=
q@alibaba-inc.com</a>&gt;, Marten Seemann
&lt;<a href=3D"mailto:martenseemann@gmail.com" target=3D"_blank">martenseem=
ann@gmail.com</a>&gt;</div>
<div><span class=3D"forward-header-title">CC:</span>jri.ietf
&lt;<a href=3D"mailto:jri.ietf@gmail.com" target=3D"_blank">jri.ietf@gmail.=
com</a>&gt;, QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_b=
lank">quic-bounces@ietf.org</a>&gt;, quic &lt;<a href=3D"mailto:quic@ietf.o=
rg" target=3D"_blank">quic@ietf.org</a>&gt;, mt
&lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"_blank">mt@lowentropy.ne=
t</a>&gt;, =E5=88=98=E5=A4=A7=E9=B9=8F(=E9=B9=8F=E6=88=90) &lt;<a href=3D"m=
ailto:max.ldp@alibaba-inc.com" target=3D"_blank">max.ldp@alibaba-inc.com</a=
>&gt;</div>
<div><span class=3D"forward-header-title">Subject:</span>Re: Fast
Address Validation - about</div>
</div>
<div>
<blockquote class=3D"gmail_quote">
<div id=3D"bloop_customfont" style=3D"font-family:helvetica,arial;font-size=
:13.0px;margin:0.0px;line-height:auto">
You only save a roundtrip because you do not send a Retry.</div>
<div id=3D"bloop_customfont" style=3D"font-family:helvetica,arial;font-size=
:13.0px;margin:0.0px;line-height:auto">
<br></div>
<div id=3D"bloop_customfont" style=3D"font-family:helvetica,arial;font-size=
:13.0px;margin:0.0px;line-height:auto">
If you choose not to send a Retry, the client eventually gets
validated anyway because otherwise the handshake could not
complete. Therefore a Retry token is not needed if you go down that
path. In this case the RTT overhead with fast address validation is
the same as ordinary QUIC 1-RTT handshake.</div>
<div id=3D"bloop_customfont" style=3D"font-family:helvetica,arial;font-size=
:13.0px;margin:0.0px;line-height:auto">
<br></div>
<div id=3D"bloop_customfont" style=3D"font-family:helvetica,arial;font-size=
:13.0px;margin:0.0px;line-height:auto">
On the other hand, in the case where Retry is needed, the fast
address validation approach does not solve the problem which is one
of 1) defer handshake processing and server state until after the
address is verified, or 2) redirect the client to another server
through a change in ConnectionID.</div>
<div id=3D"bloop_customfont" style=3D"font-family:helvetica,arial;font-size=
:13.0px;margin:0.0px;line-height:auto">
<br></div>
<div id=3D"bloop_sign_1572615124613484032" class=3D"bloop_sign">
<div style=3D"font-family:helvetica,arial;font-size:13.0px">
<br></div>
</div>
<br>
<p class=3D"airmail_on">On 1 November 2019 at 14.26.24, Qing An
(<a href=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_blank">anqing.aq@a=
libaba-inc.com</a>) wrote:</p>
<blockquote class=3D"clean_bq">
<div>
<div>
<div class=3D"__aliyun_email_body_block">
<div style=3D"line-height:1.7;font-family:tahoma,arial,stheiti,simsun;font-=
size:14.0px;color:#000000">
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>I believe this can save
1-RTT.</span></div>
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>As for the privacy risk, new_token
frame can be delivered via handshake</span></div>
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span><br></span></div>
<blockquote style=3D"margin-right:0.0px;margin-top:0.0px;margin-bottom:0.0p=
x;font-family:tahoma,arial,stheiti,simsun;font-size:14.0px;color:#000000">
<div style=3D"clear:both">
<span>------------------------------------------------------------------</s=
pan></div>
<div style=3D"clear:both"><span>From:Marten Seemann &lt;<a href=3D"mailto:m=
artenseemann@gmail.com" target=3D"_blank">martenseemann@gmail.com</a>&gt;</=
span></div>
<div style=3D"clear:both"><span>Send Time:2019=E5=B9=B411=E6=9C=881=E6=97=
=A5(=E6=98=9F=E6=9C=9F=E4=BA=94)
20:54</span></div>
<div style=3D"clear:both"><span>To:=E5=AE=89=E5=8B=8D(=E8=8E=B3=E9=80=B8) &=
lt;<a href=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_blank">anqing.aq=
@alibaba-inc.com</a>&gt;</span></div>
<div style=3D"clear:both"><span>Cc:QUIC &lt;<a href=3D"mailto:quic-bounces@=
ietf.org" target=3D"_blank">quic-bounces@ietf.org</a>&gt;; quic &lt;<a href=
=3D"mailto:quic@ietf.org" target=3D"_blank">quic@ietf.org</a>&gt;;
jri.ietf &lt;<a href=3D"mailto:jri.ietf@gmail.com" target=3D"_blank">jri.ie=
tf@gmail.com</a>&gt;; mt &lt;<a href=3D"mailto:mt@lowentropy.net" target=3D=
"_blank">mt@lowentropy.net</a>&gt;; mikkelfj &lt;<a href=3D"mailto:mikkelfj=
@gmail.com" target=3D"_blank">mikkelfj@gmail.com</a>&gt;; =E5=88=98=E5=A4=
=A7=E9=B9=8F(=E9=B9=8F=E6=88=90) &lt;<a href=3D"mailto:max.ldp@alibaba-inc.=
com" target=3D"_blank">max.ldp@alibaba-inc.com</a>&gt;</span></div>
<div style=3D"clear:both"><span>Subject:Re: Fast Address Validation
- about</span></div>
<div style=3D"clear:both"><span><br></span></div>
<div>
<div><span>I don&#39;t see any enhanced client experience, since the
handshake takes exactly the same number of round trips with your
proposal as with the current version of the QUIC
draft.<br></span></div>
<div><span>Sending NEW_TOKEN in Initial packets provides no benefit
over sending it in 1-RTT packets, but comes with worse privacy
properties, since Initial packets are not encrypted and can
therefore be read by on-path observers.<br></span></div>
</div>
<span><br></span>
<div class=3D"gmail_quote">
<div class=3D"gmail_attr"><span>On Fri, Nov 1, 2019 at 7:37 PM Qing
An &lt;<a href=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_blank">anqin=
g.aq@alibaba-inc.com</a>&gt;
wrote:<br></span></div>
<div style=3D"margin:14.0px 0.0px">
<div style=3D"line-height:1.7;font-family:tahoma,arial,stheiti,simsun;font-=
size:14.0px;color:#000000">
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>If so,
f<span>or=C2=A0the=C2=A0first</span>=C2=A0connection=C2=A0between=C2=A0clie=
nt=C2=A0and=C2=A0server,
server can choose to eliminate=C2=A0the=C2=A0use=C2=A0of=C2=A0Retry
packet=C2=A0for=C2=A0token=C2=A0delivery, and
rely=C2=A0on=C2=A0handshake=C2=A0encryption=C2=A0layer=C2=A0to
prove=C2=A0return routability.=C2=A0 In=C2=A0addition, New_Token
frame is=C2=A0used=C2=A0by
server,=C2=A0via=C2=A0i.e.=C2=A0the=C2=A0Initial=C2=A0packet,=C2=A0to=C2=A0=
provide=C2=A0the=C2=A0client=C2=A0with=C2=A0an
address=C2=A0validation=C2=A0token=C2=A0that=C2=A0can=C2=A0be=C2=A0used=C2=
=A0to=C2=A0validate=C2=A0future<span>=C2=A0connections.</span></span></div>
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>It can enhance the experience in
client side for the first connection establishment.</span></div>
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>I submitted the
draft,=C2=A0<a href=3D"https://datatracker.ietf.org/doc/draft-an-fast-addre=
ss-validation/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-an=
-fast-address-validation/</a></span></div>
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>Qing</span></div>
<div style=3D"clear:both"></div>
<div style=3D"clear:both"><br></div>
<div style=3D"clear:both"><br></div>
<div style=3D"clear:both"><br></div>
<div style=3D"clear:both">
------------------------------------------------------------------</div>
<div style=3D"clear:both">From:Mike Bishop &lt;<a href=3D"mailto:mbishop@ev=
equefou.be" target=3D"_blank">mbishop@evequefou.be</a>&gt;</div>
<div style=3D"clear:both">Send Time:2019=E5=B9=B411=E6=9C=881=E6=97=A5(=E6=
=98=9F=E6=9C=9F=E4=BA=94) 00:06</div>
<div style=3D"clear:both">To:=E5=AE=89=E5=8B=8D(=E8=8E=B3=E9=80=B8) &lt;<a =
href=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_blank">anqing.aq@aliba=
ba-inc.com</a>&gt;; quic &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_bl=
ank">quic@ietf.org</a>&gt;;
jri.ietf &lt;<a href=3D"mailto:jri.ietf@gmail.com" target=3D"_blank">jri.ie=
tf@gmail.com</a>&gt;; mt &lt;<a href=3D"mailto:mt@lowentropy.net" target=3D=
"_blank">mt@lowentropy.net</a>&gt;; mikkelfj &lt;<a href=3D"mailto:mikkelfj=
@gmail.com" target=3D"_blank">mikkelfj@gmail.com</a>&gt;</div>
<div style=3D"clear:both">Subject:RE: Fast Address Validation -
about</div>
<div style=3D"clear:both"><br></div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
As Martin pointed out in the e-mail you replied to, if the server
is willing to maintain state, any packet at the Handshake
encryption layer proves return routability.=C2=A0 There seems to be
no need for a separate address validation mechanism if the server
is willing to proceed with the handshake.</p>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
=C2=A0</p>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<b>From:</b> QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_b=
lank">quic-bounces@ietf.org</a>&gt; <b>On Behalf Of</b>
Qing An<br>
<b>Sent:</b> Thursday, October 31, 2019 8:56 AM<br>
<b>To:</b> quic &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic=
@ietf.org</a>&gt;; jri.ietf &lt;<a href=3D"mailto:jri.ietf@gmail.com" targe=
t=3D"_blank">jri.ietf@gmail.com</a>&gt;; mt &lt;<a href=3D"mailto:mt@lowent=
ropy.net" target=3D"_blank">mt@lowentropy.net</a>&gt;; mikkelfj &lt;<a href=
=3D"mailto:mikkelfj@gmail.com" target=3D"_blank">mikkelfj@gmail.com</a>&gt;=
<br>
<b>Subject:</b> Re: Fast Address Validation - about</p>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
=C2=A0</p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
To
clarify, the proposal is not to replace the existing Retry-based
validation, but to provide another option for server to do the
client validation.</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
I
understand that in server side, e<span style=3D"background:none 0.0% 0.0% r=
epeat scroll white">xchanging=C2=A0the=C2=A0token=C2=A0at=C2=A0the=C2=A0Han=
dshake=C2=A0encryption=C2=A0level
will make the server start to maintain handshake states. But in
client side, it can accelerate the connection establishment from
client to server.</span></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black;b=
ackground:none 0.0% 0.0% repeat scroll white">
And it is the server&#39;s decision whether to exchange token in Retry
or in Handshake. If server chooses to accept the cost brought by
token exchanging in Handshake, it will bring more enhanced
experience in client side.</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black;b=
ackground:none 0.0% 0.0% repeat scroll white">
BR,</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black;b=
ackground:none 0.0% 0.0% repeat scroll white">
Qing</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<div style=3D"margin:14.0px 0.0px">
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
------------------------------------------------------------------</span></=
p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
From:Martin
Thomson &lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"_blank" style=3D=
"color:#0000ff;text-decoration:underline #0000ff">mt@lowentropy.net</a>&gt;=
</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
Send
Time:2019</span><span style=3D"font-size:14.0px;font-family:ms gothic;color=
:black">=E5=B9=B4</span><span style=3D"font-size:14.0px;font-family:tahoma,=
sans-serif;color:black">10</span><span style=3D"font-size:14.0px;font-famil=
y:ms gothic;color:black">=E6=9C=88</span><span style=3D"font-size:14.0px;fo=
nt-family:tahoma,sans-serif;color:black">31</span><span style=3D"font-size:=
14.0px;font-family:ms gothic;color:black">=E6=97=A5</span><span style=3D"fo=
nt-size:14.0px;font-family:tahoma,sans-serif;color:black">(</span><span sty=
le=3D"font-size:14.0px;font-family:ms gothic;color:black">=E6=98=9F=E6=9C=
=9F=E5=9B=9B</span><span style=3D"font-size:14.0px;font-family:tahoma,sans-=
serif;color:black">)
06:07</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
To:quic
&lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank" style=3D"color:#0000=
ff;text-decoration:underline #0000ff">quic@ietf.org</a>&gt;</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
Subject:Re:
Fast Address Validation - about</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
Also=C2=A0note=C2=A0that=C2=A0exchange=C2=A0of=C2=A0Handshake=C2=A0packets=
=C2=A0provides=C2=A0proof=C2=A0of=C2=A0return=C2=A0routeability=C2=A0via=C2=
=A0the=C2=A0use=C2=A0of=C2=A0the=C2=A0encryption=C2=A0keys,=C2=A0so=C2=A0th=
ere=C2=A0is=C2=A0no=C2=A0need=C2=A0to=C2=A0exchange=C2=A0tokens=C2=A0at=C2=
=A0that=C2=A0level.<br>

<br>
On=C2=A0Thu,=C2=A0Oct=C2=A031,=C2=A02019,=C2=A0at=C2=A003:29,=C2=A0Mike=C2=
=A0Bishop=C2=A0wrote:<br>

&gt;=C2=A0=C2=A0<br>
&gt;=C2=A0The=C2=A0advantage=C2=A0of=C2=A0using=C2=A0Retry,=C2=A0however,=
=C2=A0is=C2=A0that=C2=A0the=C2=A0server=C2=A0is=C2=A0able=C2=A0to=C2=A0<br>

&gt;=C2=A0keep=C2=A0minimal=C2=A0(if=C2=A0any)=C2=A0state=C2=A0about=C2=A0t=
he=C2=A0client.=C2=A0Exchanging=C2=A0the=C2=A0token=C2=A0at=C2=A0<br>

&gt;=C2=A0the=C2=A0Handshake=C2=A0encryption=C2=A0level=C2=A0means=C2=A0the=
=C2=A0server=C2=A0is=C2=A0already=C2=A0doing=C2=A0work=C2=A0<br>

&gt;=C2=A0and=C2=A0maintaining=C2=A0state=C2=A0in=C2=A0order=C2=A0to=C2=A0p=
rocess=C2=A0the=C2=A0handshake,=C2=A0which=C2=A0is=C2=A0<br>

&gt;=C2=A0exactly=C2=A0what=C2=A0the=C2=A0server=C2=A0is=C2=A0trying=C2=A0t=
o=C2=A0avoid.<br>

&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0*From:*=C2=A0QUIC=C2=A0&lt;<a href=3D"mailto:quic-bounces@ietf.or=
g" target=3D"_blank" style=3D"color:#0000ff;text-decoration:underline #0000=
ff">quic-bounces@ietf.org</a>&gt;=C2=A0*On=C2=A0Behalf=C2=A0Of=C2=A0*=C2=A0=
Qing=C2=A0An<br>

&gt;=C2=A0*Sent:*=C2=A0Wednesday,=C2=A0October=C2=A030,=C2=A02019=C2=A09:41=
=C2=A0AM<br>

&gt;=C2=A0*To:*=C2=A0quic=C2=A0&lt;<a href=3D"mailto:quic@ietf.org" target=
=3D"_blank" style=3D"color:#0000ff;text-decoration:underline #0000ff">quic@=
ietf.org</a>&gt;;=C2=A0jri.ietf=C2=A0&lt;<a href=3D"mailto:jri.ietf@gmail.c=
om" target=3D"_blank" style=3D"color:#0000ff;text-decoration:underline #000=
0ff">jri.ietf@gmail.com</a>&gt;;=C2=A0mt=C2=A0<br>

&gt;=C2=A0&lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"_blank" style=
=3D"color:#0000ff;text-decoration:underline #0000ff">mt@lowentropy.net</a>&=
gt;<br>

&gt;=C2=A0*Cc:*=C2=A0</span><span style=3D"font-size:14.0px;font-family:ms =
gothic;color:black">=E5=88=98=E5=A4=A7</span><span style=3D"font-size:14.0p=
x;font-family:microsoft jhenghei,sans-serif;color:black">=E9=B9=8F</span><s=
pan style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">(<=
/span><span style=3D"font-size:14.0px;font-family:microsoft jhenghei,sans-s=
erif;color:black">=E9=B9=8F=E6=88=90</span><span style=3D"font-size:14.0px;=
font-family:tahoma,sans-serif;color:black">)=C2=A0&lt;<a href=3D"mailto:max=
.ldp@alibaba-inc.com" target=3D"_blank" style=3D"color:#0000ff;text-decorat=
ion:underline #0000ff">max.ldp@alibaba-inc.com</a>&gt;<br>

&gt;=C2=A0*Subject:*=C2=A0Fast=C2=A0Address=C2=A0Validation=C2=A0-=C2=A0abo=
ut<br>

&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0Hi=C2=A0Martin,=C2=A0Jana,=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0I=C2=A0read=C2=A0through=C2=A0<a href=3D"https://www.ietf.org/id/=
draft-ietf-quic-transport-23.txt" target=3D"_blank" style=3D"color:#0000ff;=
text-decoration:underline #0000ff">https://www.ietf.org/id/draft-ietf-quic-=
transport-23.txt</a>=C2=A0<br>

&gt;=C2=A0and=C2=A0have=C2=A0a=C2=A0few=C2=A0comments=C2=A0and=C2=A0ideas=
=C2=A0to=C2=A0discuss.<br>

&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0[QUIC-Trans]=C2=A0defines=C2=A0a=C2=A0token=C2=A0based=C2=A0schem=
e=C2=A0to=C2=A0facilitate=C2=A0address=C2=A0<br>

&gt;=C2=A0validation=C2=A0of=C2=A0a=C2=A0client.=C2=A0The=C2=A0token=C2=A0M=
UST=C2=A0be=C2=A0covered=C2=A0by=C2=A0integrity=C2=A0<br>

&gt;=C2=A0protection=C2=A0against=C2=A0modification=C2=A0or=C2=A0falsificat=
ion=C2=A0by=C2=A0clients.=C2=A0The=C2=A0server=C2=A0<br>

&gt;=C2=A0remembers=C2=A0the=C2=A0value=C2=A0it=C2=A0sends=C2=A0to=C2=A0cli=
ents=C2=A0and=C2=A0validates=C2=A0the=C2=A0token=C2=A0sent=C2=A0<br>

&gt;=C2=A0back=C2=A0from=C2=A0a=C2=A0client.=C2=A0In=C2=A0its=C2=A0design,=
=C2=A0Retry=C2=A0packet=C2=A0is=C2=A0used=C2=A0to=C2=A0deliver=C2=A0the=C2=
=A0<br>

&gt;=C2=A0token=C2=A0to=C2=A0a=C2=A0client=C2=A0which=C2=A0address=C2=A0has=
=C2=A0not=C2=A0yet=C2=A0been=C2=A0validated.=C2=A0It=C2=A0voids=C2=A0<br>

&gt;=C2=A0the=C2=A0first=C2=A0transmission=C2=A0of=C2=A0the=C2=A0Initial=C2=
=A0packet=C2=A0sent=C2=A0by=C2=A0the=C2=A0client,=C2=A0and=C2=A0<br>

&gt;=C2=A0triggers=C2=A0a=C2=A0second=C2=A0Initial=C2=A0packet=C2=A0to=C2=
=A0be=C2=A0sent=C2=A0with=C2=A0the=C2=A0token.=C2=A0The=C2=A0<br>

&gt;=C2=A0exchange=C2=A0of=C2=A0token=C2=A0will=C2=A0cause=C2=A0longer=C2=
=A0connection=C2=A0establishment=C2=A0delay=C2=A0for=C2=A0<br>

&gt;=C2=A0a=C2=A0client.<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0To=C2=A0improve=C2=A0the=C2=A0efficiency=C2=A0of=C2=A0address=C2=
=A0validation=C2=A0during=C2=A0handshake,=C2=A0one=C2=A0<br>

&gt;=C2=A0idea=C2=A0is=C2=A0that=C2=A0the=C2=A0same=C2=A0token=C2=A0can=C2=
=A0be=C2=A0exchanged=C2=A0via=C2=A0a=C2=A0different=C2=A0container=C2=A0<br=
>

&gt;=C2=A0i.e.=C2=A0the=C2=A0Handshake=C2=A0packet,=C2=A0that=C2=A0eliminat=
es=C2=A0the=C2=A0use=C2=A0of=C2=A0Retry=C2=A0packet=C2=A0for=C2=A0<br>

&gt;=C2=A0token=C2=A0delivery.=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0I=C2=A0am=C2=A0working=C2=A0on=C2=A0the=C2=A0complete=C2=A0draft=
=C2=A0and=C2=A0will=C2=A0submit=C2=A0it=C2=A0by=C2=A0Friday.=C2=A0Before=C2=
=A0<br>

&gt;=C2=A0that,=C2=A0hope=C2=A0this=C2=A0can=C2=A0be=C2=A0discussed=C2=A0in=
=C2=A0email=C2=A0first.<br>

&gt;=C2=A0<br>
&gt;=C2=A0<br>
&gt;=C2=A0BR,<br>
&gt;=C2=A0<br>
&gt;=C2=A0Qing=C2=A0An<br>
&gt;</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:c=
alibri,sans-serif;line-height:20.0px">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">=
=C2=A0</span></p>
</div>
</div>
</div>
<div style=3D"line-height:20.0px;clear:both"><br></div>
</div>
</div>
</div>
</blockquote>
<div style=3D"line-height:20.0px;clear:both"><br></div>
</div>
</div>
</div>
</div>
</blockquote>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</blockquote>
</div>
</blockquote>
</div>


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

--000000000000d860b50596578180--


From nobody Sat Nov  2 00:27:09 2019
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 8B0B8120F7A for <quic@ietfa.amsl.com>; Sat,  2 Nov 2019 00:27:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.587
X-Spam-Level: 
X-Spam-Status: No, score=-2.587 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_HELO_NONE=0.001, 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 14iqwsXDzH2D for <quic@ietfa.amsl.com>; Sat,  2 Nov 2019 00:27:04 -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 545F2120F6F for <quic@ietf.org>; Sat,  2 Nov 2019 00:26:49 -0700 (PDT)
Received: from xse1.mail2web.com ([66.113.196.1] helo=xse.mail2web.com) by mx37.antispamcloud.com with esmtp (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1iQno4-00052T-7I for quic@ietf.org; Sat, 02 Nov 2019 08:26:45 +0100
Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 474rGV5LDBz26Yb for <quic@ietf.org>; Sat,  2 Nov 2019 00:26:42 -0700 (PDT)
Received: from [10.5.2.31] (helo=xmail09.myhosting.com) by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1iQno2-0000GK-K2 for quic@ietf.org; Sat, 02 Nov 2019 00:26:42 -0700
Received: (qmail 14468 invoked from network); 2 Nov 2019 07:26:42 -0000
Received: from unknown (HELO [192.168.1.103]) (Authenticated-user:_huitema@huitema.net@[172.58.43.199]) (envelope-sender <huitema@huitema.net>) by xmail09.myhosting.com (qmail-ldap-1.03) with ESMTPA for <anqing.aq@alibaba-inc.com>; 2 Nov 2019 07:26:41 -0000
Content-Type: multipart/alternative; boundary=Apple-Mail-221D5986-567F-4BD9-999C-06EEB9E03C0C
Content-Transfer-Encoding: 7bit
From: Christian Huitema <huitema@huitema.net>
Mime-Version: 1.0 (1.0)
Subject: Re: Fast Address Validation - about
Date: Sat, 2 Nov 2019 00:26:40 -0700
Message-Id: <375F3961-B73B-4457-923F-7FA4DDF796F8@huitema.net>
References: <CAN1APdeo78H5cfoDOcwiS3AJ9mx2jYEJB3X0qD3LBP8xQYc3Vw@mail.gmail.com>
Cc: Qing An <anqing.aq@alibaba-inc.com>, Marten Seemann <martenseemann@gmail.com>, "jri.ietf" <jri.ietf@gmail.com>, =?utf-8?B?IuWImOWkp+m5jyjpuY/miJApIg==?= <max.ldp@alibaba-inc.com>, QUIC <quic-bounces@ietf.org>, mt <mt@lowentropy.net>, quic <quic@ietf.org>
In-Reply-To: <CAN1APdeo78H5cfoDOcwiS3AJ9mx2jYEJB3X0qD3LBP8xQYc3Vw@mail.gmail.com>
To: =?utf-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
X-Mailer: iPhone Mail (17A878)
X-Originating-IP: 66.113.196.1
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.1/32
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.1/32@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0eT2jivapI8P7M2alpZfRhCpSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDcnqpk5VeF3xR4kF6iVwRtbgN zB/4Jkrw1eDLcif59ftAvp/1ifpaG8i7GymIyD1pU7Tmz6iKnkQL9gqsxD347235Nhqq+/HvroPq 8GSPg+7KJix/R2qbtdH2ZflMjNgfMm/JD3cPBOX47Hg3FEpDo46jSvfpO+1kZkomjtjB6X5Q5Q9f RUeIpTIC2ySfqvnqLwoxlgatmaBb0rBiK9xbkDrUqzcKIief90MVLZY9LbIZh9+IQ1oS9LBn3VIP 95Jz7ujRlJ9wSMlhvaudJXZ9EIBG/qaR+8r9SKFMmPJLf850OvZYsmoVQuOIhwKLK6IKBNB4LZ0v UHHKTzJX7b1JhMjx7v77N42Z/zX3DQBtZa/0j9rMdVQseW3F+doIupqmER9E+btGG8Xk1uugE/FU 4J9TrjYo22Tif+7yfJXbGyN6EipRzMVZ5LqwTx7Vvn9SP+LiFhV9TEgXGI3XmDfDnB5aBPiMI+5j SdCRNhQ7VQKZusCm1UASYxmQqsGnM7tlFes1lrjuf/yms9xisrbG3zKR6RgQ6scM/oDJnhhySxmG 2fTOgpcK8g6VLh2DhW3+8YhI0T+E7bfVzyzh3DkvygyEZ9MYp5iiF2omUcFCWyHfp5jvIRkgf1tp JI7UlnPwuzTaGSeL3jmx6uXmdFXlkT4Lel6+lRVXf9ufYOgEjsm2LIu4VpW9PnyVI47sBfejIbtf 63VNbf0lrvssY+k7ANT9RVml4guvn3w4lnA08DXdRWSFfvxlx1m1Ym2uLiVdLjn318QNPUYQ2jrZ 34OoP6Bq8RrgJ/UgukAoEtIMdAQ2COlcvbL8404LTj9gR9O7Wyz6fZ9+dDG3ponuSVlpvwK85PZi OWsDG95exPBTMJOSJfirJfZ3lrXFsN6NSPKpFV6IlDleOcfiDMC4IxDxpTEvuGslKTrRIXcXpFg5 ivY=
X-Report-Abuse-To: spam@quarantine9.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/4RUMVYdgFRkaXa-qDqWOSpWY1qo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 02 Nov 2019 07:27:08 -0000

--Apple-Mail-221D5986-567F-4BD9-999C-06EEB9E03C0C
Content-Type: text/plain;
	charset=utf-8
Content-Transfer-Encoding: quoted-printable

There may be scenarios in which having address proof tokens would help. For e=
xample, provision the token during normal operation but only enforce them wh=
en under attack. I assume that's what Qing An has in mind. But it is safer a=
nd more reliable to provision the tokens using 1rtt packets, after the hands=
hake is verified.

-- Christian Huitema=20

> On Nov 1, 2019, at 11:51 PM, Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@g=
mail.com> wrote:
>=20
> =EF=BB=BF
> I can see how a token in the initial packet can speed up a second connecti=
on because you can drop the handshake if you do not like the token.
>=20
> But isn=E2=80=99t that exactly what 0-RTT connections / tokens are suppose=
d to do?
>=20
> And for delivering new tokens for future use it does not really matter if i=
t is delivered in the handshake from a performance perspective because 1) yo=
u are likely to continue doing more work anyway, and 2) if not, you still ne=
ed to confirm the handshake before trusting the connection, and 3) coalescin=
g 1-RTT packets are not usually slower than sending in handshake.
>=20
> =46rom a security perspective there are other concerns as Christian has di=
scussed.
>=20
> Delivering Retry tokens for future use (as you mention your next mail) may=
 be problematic due to life time concerns. 0-RTT tokens are expected to live=
 longer than Retry and Retry tokens and the Connection ID associated with it=
, reflects the current server farms load such that new connections can redir=
ect immediately, not sometime later.
>=20
>> On 1 November 2019 at 23.28.03, Qing An (anqing.aq@alibaba-inc.com) wrote=
:
>>=20
>>=20
>> Based on discussion, the proposal is for first connection establishment, s=
erver chooses to eliminate Retry and rely on handshake. But server can also u=
se New_Token frame via Handshake or Initial to deliver token for future conn=
ection.
>>=20
>>=20
>> ------------------Original Mail ------------------
>> Sender:Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@gmail.com>
>> Send Date:Fri Nov 1 23:19:30 2019
>> Recipients:Qing An <anqing.aq@alibaba-inc.com>, Marten Seemann <martensee=
mann@gmail.com>
>> CC:jri.ietf <jri.ietf@gmail.com>, QUIC <quic-bounces@ietf.org>, quic <qui=
c@ietf.org>, mt <mt@lowentropy.net>, =E5=88=98=E5=A4=A7=E9=B9=8F(=E9=B9=8F=E6=
=88=90) <max.ldp@alibaba-inc.com>
>> Subject:Re:Re: Fast Address Validation - about
>>> But what do you need to the token for in this case? The token is to prov=
e that you previously spoken to the server. But the TLS handshake provides t=
he same proof (but cannot redirect and must carry state). Any additional inf=
ormation the token might carry is only interesting in Initial packets where t=
he connection can be stopped early or (in ongoing work) to encrypt the initi=
al packet. That is not relevant during handshake. The Diffie Helman key exch=
ange takes care of all this. Since you proposal also cannot redirect and mus=
t carry state, I don=E2=80=99t see the purpose. I do agree you can deliver t=
hat token, but since it is not obvious what the token is needed for, the pur=
pose is unclear.
>>>=20
>>> You appear to assume that address validation only happens if you have a R=
etry token, bu that is not correct, it just happens with less server resourc=
es.
>>>=20
>>> On 1 November 2019 at 15.55.09, Qing An (anqing.aq@alibaba-inc.com) wrot=
e:
>>>=20
>>>=20
>>> Again, the fast address validation is to provide another option for serv=
er, not to drop the Retry approach.
>>>=20
>>> I think if choose not to send a Retry, it is necessary to define how to d=
eliver token from server to client. In this case,  via new_token frame in ha=
ndshake can be an approach.
>>>=20
>>>=20
>>> ------------------Original Mail ------------------
>>> Sender:Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@gmail.com>
>>> Send Date:Fri Nov 1 21:37:42 2019
>>> Recipients:Qing An <anqing.aq@alibaba-inc.com>, Marten Seemann <martense=
emann@gmail.com>
>>> CC:jri.ietf <jri.ietf@gmail.com>, QUIC <quic-bounces@ietf.org>, quic <qu=
ic@ietf.org>, mt <mt@lowentropy.net>, =E5=88=98=E5=A4=A7=E9=B9=8F(=E9=B9=8F=E6=
=88=90) <max.ldp@alibaba-inc.com>
>>> Subject:Re: Fast Address Validation - about
>>>> You only save a roundtrip because you do not send a Retry.
>>>>=20
>>>> If you choose not to send a Retry, the client eventually gets validated=
 anyway because otherwise the handshake could not complete. Therefore a Retr=
y token is not needed if you go down that path. In this case the RTT overhea=
d with fast address validation is the same as ordinary QUIC 1-RTT handshake.=

>>>>=20
>>>> On the other hand, in the case where Retry is needed, the fast address v=
alidation approach does not solve the problem which is one of 1) defer hands=
hake processing and server state until after the address is verified, or 2) r=
edirect the client to another server through a change in ConnectionID.
>>>>=20
>>>>=20
>>>>=20
>>>> On 1 November 2019 at 14.26.24, Qing An (anqing.aq@alibaba-inc.com) wro=
te:
>>>>=20
>>>>=20
>>>> I believe this can save 1-RTT.
>>>>=20
>>>> As for the privacy risk, new_token frame can be delivered via handshake=

>>>>=20
>>>>=20
>>>> ------------------------------------------------------------------
>>>> From:Marten Seemann <martenseemann@gmail.com>
>>>> Send Time:2019=E5=B9=B411=E6=9C=881=E6=97=A5(=E6=98=9F=E6=9C=9F=E4=BA=94=
) 20:54
>>>> To:=E5=AE=89=E5=8B=8D(=E8=8E=B3=E9=80=B8) <anqing.aq@alibaba-inc.com>
>>>> Cc:QUIC <quic-bounces@ietf.org>; quic <quic@ietf.org>; jri.ietf <jri.ie=
tf@gmail.com>; mt <mt@lowentropy.net>; mikkelfj <mikkelfj@gmail.com>; =E5=88=
=98=E5=A4=A7=E9=B9=8F(=E9=B9=8F=E6=88=90) <max.ldp@alibaba-inc.com>
>>>> Subject:Re: Fast Address Validation - about
>>>>=20
>>>> I don't see any enhanced client experience, since the handshake takes e=
xactly the same number of round trips with your proposal as with the current=
 version of the QUIC draft.
>>>> Sending NEW_TOKEN in Initial packets provides no benefit over sending i=
t in 1-RTT packets, but comes with worse privacy properties, since Initial p=
ackets are not encrypted and can therefore be read by on-path observers.
>>>>=20
>>>> On Fri, Nov 1, 2019 at 7:37 PM Qing An <anqing.aq@alibaba-inc.com> wrot=
e:
>>>>=20
>>>> If so, for the first connection between client and server, server can c=
hoose to eliminate the use of Retry packet for token delivery, and rely on h=
andshake encryption layer to prove return routability.  In addition, New_Tok=
en frame is used by server, via i.e. the Initial packet, to provide the clie=
nt with an address validation token that can be used to validate future conn=
ections.
>>>>=20
>>>> It can enhance the experience in client side for the first connection e=
stablishment.
>>>>=20
>>>> I submitted the draft, https://datatracker.ietf.org/doc/draft-an-fast-a=
ddress-validation/
>>>>=20
>>>> Qing
>>>>=20
>>>>=20
>>>>=20
>>>> ------------------------------------------------------------------
>>>> From:Mike Bishop <mbishop@evequefou.be>
>>>> Send Time:2019=E5=B9=B411=E6=9C=881=E6=97=A5(=E6=98=9F=E6=9C=9F=E4=BA=94=
) 00:06
>>>> To:=E5=AE=89=E5=8B=8D(=E8=8E=B3=E9=80=B8) <anqing.aq@alibaba-inc.com>; q=
uic <quic@ietf.org>; jri.ietf <jri.ietf@gmail.com>; mt <mt@lowentropy.net>; m=
ikkelfj <mikkelfj@gmail.com>
>>>> Subject:RE: Fast Address Validation - about
>>>>=20
>>>> As Martin pointed out in the e-mail you replied to, if the server is wi=
lling to maintain state, any packet at the Handshake encryption layer proves=
 return routability.  There seems to be no need for a separate address valid=
ation mechanism if the server is willing to proceed with the handshake.
>>>> =20
>>>> From: QUIC <quic-bounces@ietf.org> On Behalf Of Qing An
>>>> Sent: Thursday, October 31, 2019 8:56 AM
>>>> To: quic <quic@ietf.org>; jri.ietf <jri.ietf@gmail.com>; mt <mt@lowentr=
opy.net>; mikkelfj <mikkelfj@gmail.com>
>>>> Subject: Re: Fast Address Validation - about
>>>> =20
>>>> =20
>>>> =20
>>>> To clarify, the proposal is not to replace the existing Retry-based val=
idation, but to provide another option for server to do the client validatio=
n.
>>>> =20
>>>> I understand that in server side, exchanging the token at the Handshake=
 encryption level will make the server start to maintain handshake states. B=
ut in client side, it can accelerate the connection establishment from clien=
t to server.
>>>> =20
>>>> And it is the server's decision whether to exchange token in Retry or i=
n Handshake. If server chooses to accept the cost brought by token exchangin=
g in Handshake, it will bring more enhanced experience in client side.
>>>> =20
>>>> =20
>>>> BR,
>>>> Qing
>>>> =20
>>>> =20
>>>> ------------------------------------------------------------------
>>>> From:Martin Thomson <mt@lowentropy.net>
>>>> Send Time:2019=E5=B9=B410=E6=9C=8831=E6=97=A5(=E6=98=9F=E6=9C=9F=E5=9B=9B=
) 06:07
>>>> To:quic <quic@ietf.org>
>>>> Subject:Re: Fast Address Validation - about
>>>> =20
>>>> Also note that exchange of Handshake packets provides proof of return r=
outeability via the use of the encryption keys, so there is no need to excha=
nge tokens at that level.
>>>>=20
>>>> On Thu, Oct 31, 2019, at 03:29, Mike Bishop wrote:
>>>> > =20
>>>> > The advantage of using Retry, however, is that the server is able to=20=

>>>> > keep minimal (if any) state about the client. Exchanging the token at=
=20
>>>> > the Handshake encryption level means the server is already doing work=
=20
>>>> > and maintaining state in order to process the handshake, which is=20
>>>> > exactly what the server is trying to avoid.
>>>> >=20
>>>> >=20
>>>> > *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of * Qing An
>>>> > *Sent:* Wednesday, October 30, 2019 9:41 AM
>>>> > *To:* quic <quic@ietf.org>; jri.ietf <jri.ietf@gmail.com>; mt=20
>>>> > <mt@lowentropy.net>
>>>> > *Cc:* =E5=88=98=E5=A4=A7=E9=B9=8F(=E9=B9=8F=E6=88=90) <max.ldp@alibab=
a-inc.com>
>>>> > *Subject:* Fast Address Validation - about
>>>> >=20
>>>> >=20
>>>> >=20
>>>> >=20
>>>> > Hi Martin, Jana,=20
>>>> >=20
>>>> > I read through https://www.ietf.org/id/draft-ietf-quic-transport-23.t=
xt=20
>>>> > and have a few comments and ideas to discuss.
>>>> >=20
>>>> >=20
>>>> > [QUIC-Trans] defines a token based scheme to facilitate address=20
>>>> > validation of a client. The token MUST be covered by integrity=20
>>>> > protection against modification or falsification by clients. The serv=
er=20
>>>> > remembers the value it sends to clients and validates the token sent=20=

>>>> > back from a client. In its design, Retry packet is used to deliver th=
e=20
>>>> > token to a client which address has not yet been validated. It voids=20=

>>>> > the first transmission of the Initial packet sent by the client, and=20=

>>>> > triggers a second Initial packet to be sent with the token. The=20
>>>> > exchange of token will cause longer connection establishment delay fo=
r=20
>>>> > a client.
>>>> >=20
>>>> >=20
>>>> > To improve the efficiency of address validation during handshake, one=
=20
>>>> > idea is that the same token can be exchanged via a different containe=
r=20
>>>> > i.e. the Handshake packet, that eliminates the use of Retry packet fo=
r=20
>>>> > token delivery.=20
>>>> >=20
>>>> >=20
>>>> > I am working on the complete draft and will submit it by Friday. Befo=
re=20
>>>> > that, hope this can be discussed in email first.
>>>> >=20
>>>> >=20
>>>> > BR,
>>>> >=20
>>>> > Qing An
>>>> >
>>>> =20
>>>>=20
>>>>=20

--Apple-Mail-221D5986-567F-4BD9-999C-06EEB9E03C0C
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">There may be scenarios in which having addr=
ess proof tokens would help. For example, provision the token during normal o=
peration but only enforce them when under attack. I assume that's what Qing A=
n has in mind. But it is safer and more reliable to provision the tokens usi=
ng 1rtt packets, after the handshake is verified.<br><br><div dir=3D"ltr">--=
 Christian Huitema&nbsp;</div><div dir=3D"ltr"><br><blockquote type=3D"cite"=
>On Nov 1, 2019, at 11:51 PM, Mikkel Fahn=C3=B8e J=C3=B8rgensen &lt;mikkelfj=
@gmail.com&gt; wrote:<br><br></blockquote></div><blockquote type=3D"cite"><d=
iv dir=3D"ltr">=EF=BB=BF<style>body{font-family:Helvetica,Arial;font-size:13=
px}</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">I can see=
 how a token in the initial packet can speed up a second connection because y=
ou can drop the handshake if you do not like the token.</div><div id=3D"bloo=
p_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">But isn=E2=80=99t that exactly what 0-RTT con=
nections / tokens are supposed to do?</div><div id=3D"bloop_customfont" styl=
e=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">And for delivering new tokens for future use it does not really=
 matter if it is delivered in the handshake from a performance perspective b=
ecause 1) you are likely to continue doing more work anyway, and 2) if not, y=
ou still need to confirm the handshake before trusting the connection, and 3=
) coalescing 1-RTT packets are not usually slower than sending in handshake.=
</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> <di=
v id=3D"bloop_sign_1572676888210266112" class=3D"bloop_sign"><div style=3D"f=
ont-family:helvetica,arial;font-size:13px">=46rom a security perspective the=
re are other concerns as Christian has discussed.</div></div> <div><br></div=
>Delivering Retry tokens for future use (as you mention your next mail) may b=
e problematic due to life time concerns. 0-RTT tokens are expected to live l=
onger than Retry and Retry tokens and the Connection ID associated with it, r=
eflects the current server farms load such that new connections can redirect=
 immediately, not sometime later.<div><br></div><div><p class=3D"airmail_on"=
>On 1 November 2019 at 23.28.03, Qing An (<a href=3D"mailto:anqing.aq@alibab=
a-inc.com">anqing.aq@alibaba-inc.com</a>) wrote:</p> <blockquote type=3D"cit=
e" class=3D"clean_bq"><span><div><div></div><div>


<title></title>


<div id=3D"mailbox-conversation">
<div><br></div>
<div>Based on discussion, the proposal is for first connection
establishment, server chooses to eliminate Retry and rely on
handshake. But server can also use New_Token frame via Handshake or
Initial to deliver token for future connection.</div>
<div><br></div>
<div><br></div>
<blockquote>
<div>
<div style=3D"font-size:70%">------------------Original Mail
------------------</div>
<div><span class=3D"forward-header-title">Sender:</span>Mikkel Fahn=C3=B8e
J=C3=B8rgensen &lt;<a href=3D"mailto:mikkelfj@gmail.com">mikkelfj@gmail.com<=
/a>&gt;</div>
<div><span class=3D"forward-header-title">Send Date:</span>Fri Nov 1
23:19:30 2019</div>
<div><span class=3D"forward-header-title">Recipients:</span>Qing An
&lt;<a href=3D"mailto:anqing.aq@alibaba-inc.com">anqing.aq@alibaba-inc.com</=
a>&gt;, Marten Seemann
&lt;<a href=3D"mailto:martenseemann@gmail.com">martenseemann@gmail.com</a>&g=
t;</div>
<div><span class=3D"forward-header-title">CC:</span>jri.ietf
&lt;<a href=3D"mailto:jri.ietf@gmail.com">jri.ietf@gmail.com</a>&gt;, QUIC &=
lt;<a href=3D"mailto:quic-bounces@ietf.org">quic-bounces@ietf.org</a>&gt;,
quic &lt;<a href=3D"mailto:quic@ietf.org">quic@ietf.org</a>&gt;, mt &lt;<a h=
ref=3D"mailto:mt@lowentropy.net">mt@lowentropy.net</a>&gt;, =E5=88=98=E5=A4=A7=
=E9=B9=8F(=E9=B9=8F=E6=88=90)
&lt;<a href=3D"mailto:max.ldp@alibaba-inc.com">max.ldp@alibaba-inc.com</a>&g=
t;</div>
<div><span class=3D"forward-header-title">Subject:</span>Re:Re: Fast
Address Validation - about</div>
</div>
<div>
<blockquote class=3D"gmail_quote">

<div id=3D"bloop_customfont" style=3D"font-family: helvetica , arial;font-si=
ze: 13.0px;color: ;margin: 0.0px;line-height: auto;">
But what do you need to the token for in this case? The token is to
prove that you previously spoken to the server. But the TLS
handshake provides the same proof (but cannot redirect and must
carry state). Any additional information the token might carry is
only interesting in Initial packets where the connection can be
stopped early or (in ongoing work) to encrypt the initial packet.
That is not relevant during handshake. The Diffie Helman key
exchange takes care of all this. Since you proposal also cannot
redirect and must carry state, I don=E2=80=99t see the purpose. I do agree
you can deliver that token, but since it is not obvious what the
token is needed for, the purpose is unclear.</div>
<div id=3D"bloop_sign_1572621244365565952" class=3D"bloop_sign">
<div style=3D"font-family:helvetica,arial;font-size:13.0px">
<br></div>
<div style=3D"font-family:helvetica,arial;font-size:13.0px">You
appear to assume that address validation only happens if you have a
Retry token, bu that is not correct, it just happens with less
server resources.</div>
</div>
<br>
<p class=3D"airmail_on">On 1 November 2019 at 15.55.09, Qing An
(<a href=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_blank">anqing.aq@al=
ibaba-inc.com</a>) wrote:</p>
<blockquote class=3D"clean_bq">
<div>
<div>
<div id=3D"mailbox-conversation">
<div><span><br></span></div>
<div><span>Again, the fast address validation is to provide another
option for server, not to drop the Retry approach.</span></div>
<div><span><br></span></div>
<div><span>I think if choose not to send a Retry, it is necessary
to define how to deliver token from server to client. In this case,
&nbsp;via new_token frame in handshake can be an
approach.</span></div>
<div><span><br></span></div>
<div><span><br></span></div>
<blockquote>
<div>
<div style=3D"font-size:70.0%"><span>------------------Original
Mail ------------------</span></div>
<div><span><span class=3D"forward-header-title">Sender:</span>Mikkel
Fahn=C3=B8e J=C3=B8rgensen &lt;<a href=3D"mailto:mikkelfj@gmail.com" target=3D=
"_blank">mikkelfj@gmail.com</a>&gt;</span></div>
<div><span class=3D"forward-header-title">Send Date:</span>Fri Nov 1
21:37:42 2019</div>
<div><span class=3D"forward-header-title">Recipients:</span>Qing An
&lt;<a href=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_blank">anqing.aq=
@alibaba-inc.com</a>&gt;, Marten Seemann
&lt;<a href=3D"mailto:martenseemann@gmail.com" target=3D"_blank">martenseema=
nn@gmail.com</a>&gt;</div>
<div><span class=3D"forward-header-title">CC:</span>jri.ietf
&lt;<a href=3D"mailto:jri.ietf@gmail.com" target=3D"_blank">jri.ietf@gmail.c=
om</a>&gt;, QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_bla=
nk">quic-bounces@ietf.org</a>&gt;, quic &lt;<a href=3D"mailto:quic@ietf.org"=
 target=3D"_blank">quic@ietf.org</a>&gt;, mt
&lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"_blank">mt@lowentropy.net=
</a>&gt;, =E5=88=98=E5=A4=A7=E9=B9=8F(=E9=B9=8F=E6=88=90) &lt;<a href=3D"mai=
lto:max.ldp@alibaba-inc.com" target=3D"_blank">max.ldp@alibaba-inc.com</a>&g=
t;</div>
<div><span class=3D"forward-header-title">Subject:</span>Re: Fast
Address Validation - about</div>
</div>
<div>
<blockquote class=3D"gmail_quote">
<div id=3D"bloop_customfont" style=3D"font-family:helvetica,arial;font-size:=
13.0px;margin:0.0px;line-height:auto">
You only save a roundtrip because you do not send a Retry.</div>
<div id=3D"bloop_customfont" style=3D"font-family:helvetica,arial;font-size:=
13.0px;margin:0.0px;line-height:auto">
<br></div>
<div id=3D"bloop_customfont" style=3D"font-family:helvetica,arial;font-size:=
13.0px;margin:0.0px;line-height:auto">
If you choose not to send a Retry, the client eventually gets
validated anyway because otherwise the handshake could not
complete. Therefore a Retry token is not needed if you go down that
path. In this case the RTT overhead with fast address validation is
the same as ordinary QUIC 1-RTT handshake.</div>
<div id=3D"bloop_customfont" style=3D"font-family:helvetica,arial;font-size:=
13.0px;margin:0.0px;line-height:auto">
<br></div>
<div id=3D"bloop_customfont" style=3D"font-family:helvetica,arial;font-size:=
13.0px;margin:0.0px;line-height:auto">
On the other hand, in the case where Retry is needed, the fast
address validation approach does not solve the problem which is one
of 1) defer handshake processing and server state until after the
address is verified, or 2) redirect the client to another server
through a change in ConnectionID.</div>
<div id=3D"bloop_customfont" style=3D"font-family:helvetica,arial;font-size:=
13.0px;margin:0.0px;line-height:auto">
<br></div>
<div id=3D"bloop_sign_1572615124613484032" class=3D"bloop_sign">
<div style=3D"font-family:helvetica,arial;font-size:13.0px">
<br></div>
</div>
<br>
<p class=3D"airmail_on">On 1 November 2019 at 14.26.24, Qing An
(<a href=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_blank">anqing.aq@al=
ibaba-inc.com</a>) wrote:</p>
<blockquote class=3D"clean_bq">
<div>
<div>
<div class=3D"__aliyun_email_body_block">
<div style=3D"line-height:1.7;font-family:tahoma,arial,stheiti,simsun;font-s=
ize:14.0px;color:#000000">
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>I believe this can save
1-RTT.</span></div>
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>As for the privacy risk, new_token
frame can be delivered via handshake</span></div>
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span><br></span></div>
<blockquote style=3D"margin-right:0.0px;margin-top:0.0px;margin-bottom:0.0px=
;font-family:tahoma,arial,stheiti,simsun;font-size:14.0px;color:#000000">
<div style=3D"clear:both">
<span>------------------------------------------------------------------</sp=
an></div>
<div style=3D"clear:both"><span>From:Marten Seemann &lt;<a href=3D"mailto:ma=
rtenseemann@gmail.com" target=3D"_blank">martenseemann@gmail.com</a>&gt;</sp=
an></div>
<div style=3D"clear:both"><span>Send Time:2019=E5=B9=B411=E6=9C=881=E6=97=A5=
(=E6=98=9F=E6=9C=9F=E4=BA=94)
20:54</span></div>
<div style=3D"clear:both"><span>To:=E5=AE=89=E5=8B=8D(=E8=8E=B3=E9=80=B8) &l=
t;<a href=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_blank">anqing.aq@a=
libaba-inc.com</a>&gt;</span></div>
<div style=3D"clear:both"><span>Cc:QUIC &lt;<a href=3D"mailto:quic-bounces@i=
etf.org" target=3D"_blank">quic-bounces@ietf.org</a>&gt;; quic &lt;<a href=3D=
"mailto:quic@ietf.org" target=3D"_blank">quic@ietf.org</a>&gt;;
jri.ietf &lt;<a href=3D"mailto:jri.ietf@gmail.com" target=3D"_blank">jri.iet=
f@gmail.com</a>&gt;; mt &lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"_=
blank">mt@lowentropy.net</a>&gt;; mikkelfj &lt;<a href=3D"mailto:mikkelfj@gm=
ail.com" target=3D"_blank">mikkelfj@gmail.com</a>&gt;; =E5=88=98=E5=A4=A7=E9=
=B9=8F(=E9=B9=8F=E6=88=90) &lt;<a href=3D"mailto:max.ldp@alibaba-inc.com" ta=
rget=3D"_blank">max.ldp@alibaba-inc.com</a>&gt;</span></div>
<div style=3D"clear:both"><span>Subject:Re: Fast Address Validation
- about</span></div>
<div style=3D"clear:both"><span><br></span></div>
<div>
<div><span>I don't see any enhanced client experience, since the
handshake takes exactly the same number of round trips with your
proposal as with the current version of the QUIC
draft.<br></span></div>
<div><span>Sending NEW_TOKEN in Initial packets provides no benefit
over sending it in 1-RTT packets, but comes with worse privacy
properties, since Initial packets are not encrypted and can
therefore be read by on-path observers.<br></span></div>
</div>
<span><br></span>
<div class=3D"gmail_quote">
<div class=3D"gmail_attr"><span>On Fri, Nov 1, 2019 at 7:37 PM Qing
An &lt;<a href=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_blank">anqing=
.aq@alibaba-inc.com</a>&gt;
wrote:<br></span></div>
<div style=3D"margin:14.0px 0.0px">
<div style=3D"line-height:1.7;font-family:tahoma,arial,stheiti,simsun;font-s=
ize:14.0px;color:#000000">
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>If so,
f<span>or&nbsp;the&nbsp;first</span>&nbsp;connection&nbsp;between&nbsp;clien=
t&nbsp;and&nbsp;server,
server can choose to eliminate&nbsp;the&nbsp;use&nbsp;of&nbsp;Retry
packet&nbsp;for&nbsp;token&nbsp;delivery, and
rely&nbsp;on&nbsp;handshake&nbsp;encryption&nbsp;layer&nbsp;to
prove&nbsp;return routability.&nbsp; In&nbsp;addition, New_Token
frame is&nbsp;used&nbsp;by
server,&nbsp;via&nbsp;i.e.&nbsp;the&nbsp;Initial&nbsp;packet,&nbsp;to&nbsp;p=
rovide&nbsp;the&nbsp;client&nbsp;with&nbsp;an
address&nbsp;validation&nbsp;token&nbsp;that&nbsp;can&nbsp;be&nbsp;used&nbsp=
;to&nbsp;validate&nbsp;future<span>&nbsp;connections.</span></span></div>
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>It can enhance the experience in
client side for the first connection establishment.</span></div>
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>I submitted the
draft,&nbsp;<a href=3D"https://datatracker.ietf.org/doc/draft-an-fast-addres=
s-validation/" target=3D"_blank">https://datatracker.ietf.org/doc/draft-an-f=
ast-address-validation/</a></span></div>
<div style=3D"clear:both"><span><br></span></div>
<div style=3D"clear:both"><span>Qing</span></div>
<div style=3D"clear:both"></div>
<div style=3D"clear:both"><br></div>
<div style=3D"clear:both"><br></div>
<div style=3D"clear:both"><br></div>
<div style=3D"clear:both">
------------------------------------------------------------------</div>
<div style=3D"clear:both">From:Mike Bishop &lt;<a href=3D"mailto:mbishop@eve=
quefou.be" target=3D"_blank">mbishop@evequefou.be</a>&gt;</div>
<div style=3D"clear:both">Send Time:2019=E5=B9=B411=E6=9C=881=E6=97=A5(=E6=98=
=9F=E6=9C=9F=E4=BA=94) 00:06</div>
<div style=3D"clear:both">To:=E5=AE=89=E5=8B=8D(=E8=8E=B3=E9=80=B8) &lt;<a h=
ref=3D"mailto:anqing.aq@alibaba-inc.com" target=3D"_blank">anqing.aq@alibaba=
-inc.com</a>&gt;; quic &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank=
">quic@ietf.org</a>&gt;;
jri.ietf &lt;<a href=3D"mailto:jri.ietf@gmail.com" target=3D"_blank">jri.iet=
f@gmail.com</a>&gt;; mt &lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"_=
blank">mt@lowentropy.net</a>&gt;; mikkelfj &lt;<a href=3D"mailto:mikkelfj@gm=
ail.com" target=3D"_blank">mikkelfj@gmail.com</a>&gt;</div>
<div style=3D"clear:both">Subject:RE: Fast Address Validation -
about</div>
<div style=3D"clear:both"><br></div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
As Martin pointed out in the e-mail you replied to, if the server
is willing to maintain state, any packet at the Handshake
encryption layer proves return routability.&nbsp; There seems to be
no need for a separate address validation mechanism if the server
is willing to proceed with the handshake.</p>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
&nbsp;</p>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<b>From:</b> QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_bl=
ank">quic-bounces@ietf.org</a>&gt; <b>On Behalf Of</b>
Qing An<br>
<b>Sent:</b> Thursday, October 31, 2019 8:56 AM<br>
<b>To:</b> quic &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic@=
ietf.org</a>&gt;; jri.ietf &lt;<a href=3D"mailto:jri.ietf@gmail.com" target=3D=
"_blank">jri.ietf@gmail.com</a>&gt;; mt &lt;<a href=3D"mailto:mt@lowentropy.=
net" target=3D"_blank">mt@lowentropy.net</a>&gt;; mikkelfj &lt;<a href=3D"ma=
ilto:mikkelfj@gmail.com" target=3D"_blank">mikkelfj@gmail.com</a>&gt;<br>
<b>Subject:</b> Re: Fast Address Validation - about</p>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
&nbsp;</p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">&=
nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">&=
nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">T=
o
clarify, the proposal is not to replace the existing Retry-based
validation, but to provide another option for server to do the
client validation.</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">&=
nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">I=

understand that in server side, e<span style=3D"background:none 0.0% 0.0% re=
peat scroll white">xchanging&nbsp;the&nbsp;token&nbsp;at&nbsp;the&nbsp;Hands=
hake&nbsp;encryption&nbsp;level
will make the server start to maintain handshake states. But in
client side, it can accelerate the connection establishment from
client to server.</span></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">&=
nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black;ba=
ckground:none 0.0% 0.0% repeat scroll white">
And it is the server's decision whether to exchange token in Retry
or in Handshake. If server chooses to accept the cost brought by
token exchanging in Handshake, it will bring more enhanced
experience in client side.</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">&=
nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">&=
nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black;ba=
ckground:none 0.0% 0.0% repeat scroll white">
BR,</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black;ba=
ckground:none 0.0% 0.0% repeat scroll white">
Qing</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">&=
nbsp;</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">&=
nbsp;</span></p>
</div>
<div style=3D"margin:14.0px 0.0px">
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">-=
-----------------------------------------------------------------</span></p>=

</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">From:=
Martin
Thomson &lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"_blank" style=3D"=
color:#0000ff;text-decoration:underline #0000ff">mt@lowentropy.net</a>&gt;</=
span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">S=
end
Time:2019</span><span style=3D"font-size:14.0px;font-family:ms gothic;color:=
black">=E5=B9=B4</span><span style=3D"font-size:14.0px;font-family:tahoma,sa=
ns-serif;color:black">10</span><span style=3D"font-size:14.0px;font-family:m=
s gothic;color:black">=E6=9C=88</span><span style=3D"font-size:14.0px;font-f=
amily:tahoma,sans-serif;color:black">31</span><span style=3D"font-size:14.0p=
x;font-family:ms gothic;color:black">=E6=97=A5</span><span style=3D"font-siz=
e:14.0px;font-family:tahoma,sans-serif;color:black">(</span><span style=3D"f=
ont-size:14.0px;font-family:ms gothic;color:black">=E6=98=9F=E6=9C=9F=E5=9B=9B=
</span><span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:b=
lack">)
06:07</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">T=
o:quic
&lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank" style=3D"color:#0000f=
f;text-decoration:underline #0000ff">quic@ietf.org</a>&gt;</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">S=
ubject:Re:
Fast Address Validation - about</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">&=
nbsp;</span></p>
</div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">A=
lso&nbsp;note&nbsp;that&nbsp;exchange&nbsp;of&nbsp;Handshake&nbsp;packets&nb=
sp;provides&nbsp;proof&nbsp;of&nbsp;return&nbsp;routeability&nbsp;via&nbsp;t=
he&nbsp;use&nbsp;of&nbsp;the&nbsp;encryption&nbsp;keys,&nbsp;so&nbsp;there&n=
bsp;is&nbsp;no&nbsp;need&nbsp;to&nbsp;exchange&nbsp;tokens&nbsp;at&nbsp;that=
&nbsp;level.<br>

<br>
On&nbsp;Thu,&nbsp;Oct&nbsp;31,&nbsp;2019,&nbsp;at&nbsp;03:29,&nbsp;Mike&nbsp=
;Bishop&nbsp;wrote:<br>

&gt;&nbsp;&nbsp;<br>
&gt;&nbsp;The&nbsp;advantage&nbsp;of&nbsp;using&nbsp;Retry,&nbsp;however,&nb=
sp;is&nbsp;that&nbsp;the&nbsp;server&nbsp;is&nbsp;able&nbsp;to&nbsp;<br>

&gt;&nbsp;keep&nbsp;minimal&nbsp;(if&nbsp;any)&nbsp;state&nbsp;about&nbsp;th=
e&nbsp;client.&nbsp;Exchanging&nbsp;the&nbsp;token&nbsp;at&nbsp;<br>

&gt;&nbsp;the&nbsp;Handshake&nbsp;encryption&nbsp;level&nbsp;means&nbsp;the&=
nbsp;server&nbsp;is&nbsp;already&nbsp;doing&nbsp;work&nbsp;<br>

&gt;&nbsp;and&nbsp;maintaining&nbsp;state&nbsp;in&nbsp;order&nbsp;to&nbsp;pr=
ocess&nbsp;the&nbsp;handshake,&nbsp;which&nbsp;is&nbsp;<br>

&gt;&nbsp;exactly&nbsp;what&nbsp;the&nbsp;server&nbsp;is&nbsp;trying&nbsp;to=
&nbsp;avoid.<br>

&gt;&nbsp;<br>
&gt;&nbsp;<br>
&gt;&nbsp;*From:*&nbsp;QUIC&nbsp;&lt;<a href=3D"mailto:quic-bounces@ietf.org=
" target=3D"_blank" style=3D"color:#0000ff;text-decoration:underline #0000ff=
">quic-bounces@ietf.org</a>&gt;&nbsp;*On&nbsp;Behalf&nbsp;Of&nbsp;*&nbsp;Qin=
g&nbsp;An<br>

&gt;&nbsp;*Sent:*&nbsp;Wednesday,&nbsp;October&nbsp;30,&nbsp;2019&nbsp;9:41&=
nbsp;AM<br>

&gt;&nbsp;*To:*&nbsp;quic&nbsp;&lt;<a href=3D"mailto:quic@ietf.org" target=3D=
"_blank" style=3D"color:#0000ff;text-decoration:underline #0000ff">quic@ietf=
.org</a>&gt;;&nbsp;jri.ietf&nbsp;&lt;<a href=3D"mailto:jri.ietf@gmail.com" t=
arget=3D"_blank" style=3D"color:#0000ff;text-decoration:underline #0000ff">j=
ri.ietf@gmail.com</a>&gt;;&nbsp;mt&nbsp;<br>

&gt;&nbsp;&lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"_blank" style=3D=
"color:#0000ff;text-decoration:underline #0000ff">mt@lowentropy.net</a>&gt;<=
br>

&gt;&nbsp;*Cc:*&nbsp;</span><span style=3D"font-size:14.0px;font-family:ms g=
othic;color:black">=E5=88=98=E5=A4=A7</span><span style=3D"font-size:14.0px;=
font-family:microsoft jhenghei,sans-serif;color:black">=E9=B9=8F</span><span=
 style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">(</spa=
n><span style=3D"font-size:14.0px;font-family:microsoft jhenghei,sans-serif;=
color:black">=E9=B9=8F=E6=88=90</span><span style=3D"font-size:14.0px;font-f=
amily:tahoma,sans-serif;color:black">)&nbsp;&lt;<a href=3D"mailto:max..ldp@a=
libaba-inc.com" target=3D"_blank" style=3D"color:#0000ff;text-decoration:und=
erline #0000ff">max.ldp@alibaba-inc.com</a>&gt;<br>

&gt;&nbsp;*Subject:*&nbsp;Fast&nbsp;Address&nbsp;Validation&nbsp;-&nbsp;abou=
t<br>

&gt;&nbsp;<br>
&gt;&nbsp;<br>
&gt;&nbsp;<br>
&gt;&nbsp;<br>
&gt;&nbsp;Hi&nbsp;Martin,&nbsp;Jana,&nbsp;<br>
&gt;&nbsp;<br>
&gt;&nbsp;I&nbsp;read&nbsp;through&nbsp;<a href=3D"https://www.ietf.org/id/d=
raft-ietf-quic-transport-23.txt" target=3D"_blank" style=3D"color:#0000ff;te=
xt-decoration:underline #0000ff">https://www.ietf.org/id/draft-ietf-quic-tra=
nsport-23.txt</a>&nbsp;<br>

&gt;&nbsp;and&nbsp;have&nbsp;a&nbsp;few&nbsp;comments&nbsp;and&nbsp;ideas&nb=
sp;to&nbsp;discuss.<br>

&gt;&nbsp;<br>
&gt;&nbsp;<br>
&gt;&nbsp;[QUIC-Trans]&nbsp;defines&nbsp;a&nbsp;token&nbsp;based&nbsp;scheme=
&nbsp;to&nbsp;facilitate&nbsp;address&nbsp;<br>

&gt;&nbsp;validation&nbsp;of&nbsp;a&nbsp;client.&nbsp;The&nbsp;token&nbsp;MU=
ST&nbsp;be&nbsp;covered&nbsp;by&nbsp;integrity&nbsp;<br>

&gt;&nbsp;protection&nbsp;against&nbsp;modification&nbsp;or&nbsp;falsificati=
on&nbsp;by&nbsp;clients.&nbsp;The&nbsp;server&nbsp;<br>

&gt;&nbsp;remembers&nbsp;the&nbsp;value&nbsp;it&nbsp;sends&nbsp;to&nbsp;clie=
nts&nbsp;and&nbsp;validates&nbsp;the&nbsp;token&nbsp;sent&nbsp;<br>

&gt;&nbsp;back&nbsp;from&nbsp;a&nbsp;client.&nbsp;In&nbsp;its&nbsp;design,&n=
bsp;Retry&nbsp;packet&nbsp;is&nbsp;used&nbsp;to&nbsp;deliver&nbsp;the&nbsp;<=
br>

&gt;&nbsp;token&nbsp;to&nbsp;a&nbsp;client&nbsp;which&nbsp;address&nbsp;has&=
nbsp;not&nbsp;yet&nbsp;been&nbsp;validated.&nbsp;It&nbsp;voids&nbsp;<br>

&gt;&nbsp;the&nbsp;first&nbsp;transmission&nbsp;of&nbsp;the&nbsp;Initial&nbs=
p;packet&nbsp;sent&nbsp;by&nbsp;the&nbsp;client,&nbsp;and&nbsp;<br>

&gt;&nbsp;triggers&nbsp;a&nbsp;second&nbsp;Initial&nbsp;packet&nbsp;to&nbsp;=
be&nbsp;sent&nbsp;with&nbsp;the&nbsp;token.&nbsp;The&nbsp;<br>

&gt;&nbsp;exchange&nbsp;of&nbsp;token&nbsp;will&nbsp;cause&nbsp;longer&nbsp;=
connection&nbsp;establishment&nbsp;delay&nbsp;for&nbsp;<br>

&gt;&nbsp;a&nbsp;client.<br>
&gt;&nbsp;<br>
&gt;&nbsp;<br>
&gt;&nbsp;To&nbsp;improve&nbsp;the&nbsp;efficiency&nbsp;of&nbsp;address&nbsp=
;validation&nbsp;during&nbsp;handshake,&nbsp;one&nbsp;<br>

&gt;&nbsp;idea&nbsp;is&nbsp;that&nbsp;the&nbsp;same&nbsp;token&nbsp;can&nbsp=
;be&nbsp;exchanged&nbsp;via&nbsp;a&nbsp;different&nbsp;container&nbsp;<br>

&gt;&nbsp;i.e.&nbsp;the&nbsp;Handshake&nbsp;packet,&nbsp;that&nbsp;eliminate=
s&nbsp;the&nbsp;use&nbsp;of&nbsp;Retry&nbsp;packet&nbsp;for&nbsp;<br>

&gt;&nbsp;token&nbsp;delivery.&nbsp;<br>
&gt;&nbsp;<br>
&gt;&nbsp;<br>
&gt;&nbsp;I&nbsp;am&nbsp;working&nbsp;on&nbsp;the&nbsp;complete&nbsp;draft&n=
bsp;and&nbsp;will&nbsp;submit&nbsp;it&nbsp;by&nbsp;Friday.&nbsp;Before&nbsp;=
<br>

&gt;&nbsp;that,&nbsp;hope&nbsp;this&nbsp;can&nbsp;be&nbsp;discussed&nbsp;in&=
nbsp;email&nbsp;first.<br>

&gt;&nbsp;<br>
&gt;&nbsp;<br>
&gt;&nbsp;BR,<br>
&gt;&nbsp;<br>
&gt;&nbsp;Qing&nbsp;An<br>
&gt;</span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin:0.0px;font-size:14.7px;font-family:ca=
libri,sans-serif;line-height:20.0px">
<span style=3D"font-size:14.0px;font-family:tahoma,sans-serif;color:black">&=
nbsp;</span></p>
</div>
</div>
</div>
<div style=3D"line-height:20.0px;clear:both"><br></div>
</div>
</div>
</div>
</blockquote>
<div style=3D"line-height:20.0px;clear:both"><br></div>
</div>
</div>
</div>
</div>
</blockquote>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</blockquote>
</blockquote>
</div>
</blockquote>
</div>


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

--Apple-Mail-221D5986-567F-4BD9-999C-06EEB9E03C0C--


From nobody Sun Nov  3 00:33:14 2019
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 344C512001A for <quic@ietfa.amsl.com>; Sun,  3 Nov 2019 00:33:12 -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=2ifFR9kg; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=aUmecRyO
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 02X5hENxRjYT for <quic@ietfa.amsl.com>; Sun,  3 Nov 2019 00:33:08 -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 86A9F1200E3 for <quic@ietf.org>; Sun,  3 Nov 2019 00:33:08 -0700 (PDT)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 3D59220E72 for <quic@ietf.org>; Sun,  3 Nov 2019 02:33:06 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sun, 03 Nov 2019 02:33:06 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject:message-id:date; s= fm1; bh=TIczgO3cFV5GhzgxXVRU8NJQA+/vkegTIHeCKgflzyg=; b=2ifFR9kg pdCr7eKSw798D5Q5xrfGEWq1/ZCO+hG0Byqu7ZRWZCUwwYF1fecfaePicPFxOp2x N8/r6c81ZJ4W4P+EOHuZET/S2mNpTkhELKwccpwAebb/0U5craUkSZtEyoJ26zjw r6rN2JZyoNZWNKJWQm+QmgSXfy1kOEHgNw78y/AbDeksxYaZJRQxdA1HYwqvboMO G3CBtxXJnX3xLgkkki1qwLRG2131nXP9avas69Sh9zYCwm6LvL5vGDpRK6Nq8Yfk YFgdYCWkm0IC1TK0tt8wiAZrKhN5mNgB6aJcPxdNXBdkK+o9EYQ8LpxEDYpqUtJG L6nWkIp/m5uIxA==
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-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=TIczgO3cFV5GhzgxXVRU8NJQA+/vk egTIHeCKgflzyg=; b=aUmecRyOPO5dMk3ZH/FNNd7GnpudLNEczGMuz2E+UAWRi ZjaFIRW6dhdSAb68KsooT7ZX1bsAcdziN1354U2qACFtyp2FWB/FBJelmn4qph+M Kba0BibrxVo8dZz3pIV+VhKmNPRk59CHNPZD+dnMhd6GeY6hpSSy1HbirBAKBKsX GWy6c/MwY9PT4zg0LeMmTXdVAKvhJQ8JgcWNb+zpJFxQrWulc716U+1GDY8qXy+x HMtn3OkmqFJQEbXNbolEe9VjxjJVtvFQTwe+AZg4BNd9kt1ARW+zhvd05yB7FReH Yp+zyd435uFBTkbPKANhIEobQ/wxL3lDwI8PTHWwA==
X-ME-Sender: <xms:sYK-XWJjmrEXpL_IhunyKwCkZCfCh-W0SOCHYT3rXJXkfyy2eOvkqQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedruddutddgjeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtggfhvffusegrtddtredttdejne cuhfhrohhmpeftvghpohhsihhtohhrhicutegtthhivhhithihucfuuhhmmhgrrhihuceu ohhtuceoughopghnohhtpghrvghplhihsehmnhhothdrnhgvtheqnecuffhomhgrihhnpe hgihhthhhusgdrtghomhenucfkphepuddtgedrvddtkedrudegtddrudefleenucfrrghr rghmpehmrghilhhfrhhomhepughopghnohhtpghrvghplhihsehmnhhothdrnhgvthenuc evlhhushhtvghrufhiiigvpedu
X-ME-Proxy: <xmx:sYK-XZRNRWUIXaclsuhBkDF_nsOZGd5KlbDatWH84NMzul6cTHfThw> <xmx:sYK-XRAwGRbyZCyVrWYzXYOtOVvB2o-exEpMIYYbFVwQRs1BuzSxVw> <xmx:sYK-XX_OcNcYySXHcjYDKHqTAqTd3Rrj1YI9TglCcyPbi72Vv58YYg> <xmx:soK-XTovu3AZnftaqyzrguBR7sHf9DcM9oLB01PMYdXIkBip5xz4lw>
Received: from [10.1.0.4] (unknown [104.208.140.139]) by mail.messagingengine.com (Postfix) with ESMTPA id BE125306005C for <quic@ietf.org>; Sun,  3 Nov 2019 02:33:05 -0500 (EST)
Content-Type: multipart/alternative; boundary="===============2291551005938582497=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: quic@ietf.org
Subject: Weekly github digest ( Activity Summary)
Message-Id: <20191103073305.BE125306005C@mailuser.nyi.internal>
Date: Sun,  3 Nov 2019 02:33:05 -0500 (EST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/1AuiZGyvn5u07O-obAlXV6-AooM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Nov 2019 07:33:12 -0000

--===============2291551005938582497==
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 (+1/-9/=F0=9F=92=AC28)
  1 issues created:
  - Duplicate NEW_TOKEN should only be on same connection (by mikkelfj)
    https://github.com/quicwg/base-drafts/issues/3179=20

  5 issues received 28 new comments:
  - #3173 TLS MUST NOT deliver server 1RTT Rx keys until getting Finished (=
10 by ghedo, kazuho, martinduke)
    https://github.com/quicwg/base-drafts/issues/3173 [-tls]=20
  - #3159 Server should not accept 1-RTT traffic before handshake completio=
n (11 by ad-l, ghedo, ianswett, mikkelfj)
    https://github.com/quicwg/base-drafts/issues/3159 [-tls]=20
  - #3155 The method of identifying "the same server" (2 by kazuho, mikkelf=
j)
    https://github.com/quicwg/base-drafts/issues/3155 [-transport] [design]=
 [proposal-ready]=20
  - #3151 loss detection timer description could be simplified by defininin=
g a timer mode (4 by ianswett, janaiyengar, marten-seemann)
    https://github.com/quicwg/base-drafts/issues/3151 [-recovery]=20
  - #3135 allow sending PADDING after receiving a non-ack-eliciting packet =
(1 by mnot)
    https://github.com/quicwg/base-drafts/issues/3135 [-transport]=20

  9 issues closed:
  - kMaxDatagramSize should use the PMTU rather than be fixed https://githu=
b.com/quicwg/base-drafts/issues/3041 [-recovery] [design]=20
  - Lift single-packet ClientHello requirement? https://github.com/quicwg/b=
ase-drafts/issues/2928 [-tls] [design] [has-consensus]=20
  - Do Initial secrets change after Retry packet? https://github.com/quicwg=
/base-drafts/issues/2823 [-tls] [design] [has-consensus]=20
  - Handling of Retire Prior To field https://github.com/quicwg/base-drafts=
/issues/3046 [-transport] [design] [has-consensus]=20
  - Stateless reset detection should be datagram-based https://github.com/q=
uicwg/base-drafts/issues/3085 [-transport] [design] [has-consensus]=20
  - Why does stateless reset have to be checked after MAC failure https://g=
ithub.com/quicwg/base-drafts/issues/2152 [-transport] [design] [has-consens=
us]=20
  - Is CONNECTION_CLOSE ACK-eliciting? https://github.com/quicwg/base-draft=
s/issues/3097 [-recovery] [-transport] [design] [has-consensus]=20
  - Re-visit initial keys discard https://github.com/quicwg/base-drafts/iss=
ues/2741 [-tls] [-transport] [design] [has-consensus]=20
  - Layout of PreferredAddress https://github.com/quicwg/base-drafts/issues=
/2944 [-transport] [design] [has-consensus]=20



Pull requests
-------------
* quicwg/base-drafts (+3/-5/=F0=9F=92=AC14)
  3 pull requests submitted:
  - Limit CWND increase in slow start (by ianswett)
    https://github.com/quicwg/base-drafts/pull/3183 [-recovery]=20
  - Add an enum indicating the timer_mode (by ianswett)
    https://github.com/quicwg/base-drafts/pull/3182 [-recovery]=20
  - token-based greasing / initial packet protection (downgradable variant)=
 (by kazuho)
    https://github.com/quicwg/base-drafts/pull/3178=20

  8 pull requests received 14 new comments:
  - #3183 Limit CWND increase in slow start (2 by ianswett, janaiyengar)
    https://github.com/quicwg/base-drafts/pull/3183 [-recovery]=20
  - #3182 Add an enum indicating the timer_mode (2 by ianswett, marten-seem=
ann)
    https://github.com/quicwg/base-drafts/pull/3182 [-recovery]=20
  - #3166 token-based greasing / initial packet protection (1 by kazuho)
    https://github.com/quicwg/base-drafts/pull/3166 [-transport] [design]=20
  - #3120 Add retry integrity tag (3 by kazuho, martinthomson, mikkelfj)
    https://github.com/quicwg/base-drafts/pull/3120 [-tls] [-transport]=20
  - #3099 Idle timeout indicates you will timeout (1 by ianswett)
    https://github.com/quicwg/base-drafts/pull/3099 [-transport]=20
  - #3066 Change PTO to be per packet number space (1 by marten-seemann)
    https://github.com/quicwg/base-drafts/pull/3066 [-recovery] [design]=20
  - #3050 Rewrite key update section (3 by DavidSchinazi, martinthomson)
    https://github.com/quicwg/base-drafts/pull/3050 [-tls] [design]=20
  - #3042 Use the FRAME_ENCODING_ERROR for errors in frame encoding (1 by m=
artinthomson)
    https://github.com/quicwg/base-drafts/pull/3042 [-transport] [design]=20

  5 pull requests merged:
  - kMaxDatagramSize -> max_datagram_size
    https://github.com/quicwg/base-drafts/pull/3167 [-recovery]=20
  - Allow ClientHello to span multiple QUIC packets
    https://github.com/quicwg/base-drafts/pull/3045 [-tls]=20
  - MUST retire Connection IDs becoming stale
    https://github.com/quicwg/base-drafts/pull/3096 [-transport] [design]=20
  - Stateless reset comparisons (constant time/any order/datagram)
    https://github.com/quicwg/base-drafts/pull/2993 [-transport] [design]=20
  - CONNECTION_CLOSE is non-ack-eliciting
    https://github.com/quicwg/base-drafts/pull/3098 [-recovery] [-transport=
] [design]=20


Repositories tracked by this digest:
-----------------------------------
* https://github.com/quicwg/base-drafts

--===============2291551005938582497==
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 ( Activity Summary)</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 November 03, 2019</h1>

<p>Events without label "editorial"</p>

<h2>Issues</h2>

<h3>quicwg/base-drafts (+1/-9/=F0=9F=92=AC28)</h3>
  <p class=3D"new">1 issues created:</p>
  <ul>
  <li>#3179 <a href=3D"https://github.com/quicwg/base-drafts/issues/3179">D=
uplicate NEW_TOKEN should only be on same connection</a> (by mikkelfj) </li>
  </ul>

  <p>5 issues received 28 new comments:</p>
  <ul>
  <li>#3173 <a href=3D"https://github.com/quicwg/base-drafts/issues/3173">T=
LS MUST NOT deliver server 1RTT Rx keys until getting Finished</a> (10 by g=
hedo, kazuho, martinduke) <span class=3D"label" style=3D"background-color: =
#fbca04; color: #000000">-tls</span> </li>
 =20
  <li>#3159 <a href=3D"https://github.com/quicwg/base-drafts/issues/3159">S=
erver should not accept 1-RTT traffic before handshake completion</a> (11 b=
y ad-l, ghedo, ianswett, mikkelfj) <span class=3D"label" style=3D"backgroun=
d-color: #fbca04; color: #000000">-tls</span> </li>
 =20
  <li>#3155 <a href=3D"https://github.com/quicwg/base-drafts/issues/3155">T=
he method of identifying &quot;the same server&quot;</a> (2 by kazuho, mikk=
elfj) <span class=3D"label" style=3D"background-color: #fbca04; color: #000=
000">-transport</span> <span class=3D"label" style=3D"background-color: #1d=
76db; color: #ffffff">design</span> <span class=3D"label" style=3D"backgrou=
nd-color: #c5def5; color: #000000">proposal-ready</span> </li>
 =20
  <li>#3151 <a href=3D"https://github.com/quicwg/base-drafts/issues/3151">l=
oss detection timer description could be simplified by definining a timer m=
ode</a> (4 by ianswett, janaiyengar, marten-seemann) <span class=3D"label" =
style=3D"background-color: #fbca04; color: #000000">-recovery</span> </li>
 =20
  <li>#3135 <a href=3D"https://github.com/quicwg/base-drafts/issues/3135">a=
llow sending PADDING after receiving a non-ack-eliciting packet</a> (1 by m=
not) <span class=3D"label" style=3D"background-color: #fbca04; color: #0000=
00">-transport</span> </li>
  </ul>

  <p>9 issues closed:</p>
  <ul>
  <li>#3041 <a href=3D"https://github.com/quicwg/base-drafts/issues/3041">k=
MaxDatagramSize should use the PMTU rather than be fixed</a> <span class=3D=
"label" style=3D"background-color: #fbca04; color: #000000">-recovery</span=
> <span class=3D"label" style=3D"background-color: #1d76db; color: #ffffff"=
>design</span> </li>
 =20
  <li>#2928 <a href=3D"https://github.com/quicwg/base-drafts/issues/2928">L=
ift single-packet ClientHello requirement?</a> <span class=3D"label" style=
=3D"background-color: #fbca04; color: #000000">-tls</span> <span class=3D"l=
abel" style=3D"background-color: #1d76db; color: #ffffff">design</span> <sp=
an class=3D"label" style=3D"background-color: #5319e7; color: #ffffff">has-=
consensus</span> </li>
 =20
  <li>#2823 <a href=3D"https://github.com/quicwg/base-drafts/issues/2823">D=
o Initial secrets change after Retry packet?</a> <span class=3D"label" styl=
e=3D"background-color: #fbca04; color: #000000">-tls</span> <span class=3D"=
label" style=3D"background-color: #1d76db; color: #ffffff">design</span> <s=
pan class=3D"label" style=3D"background-color: #5319e7; color: #ffffff">has=
-consensus</span> </li>
 =20
  <li>#3046 <a href=3D"https://github.com/quicwg/base-drafts/issues/3046">H=
andling of Retire Prior To field</a> <span class=3D"label" style=3D"backgro=
und-color: #fbca04; color: #000000">-transport</span> <span class=3D"label"=
 style=3D"background-color: #1d76db; color: #ffffff">design</span> <span cl=
ass=3D"label" style=3D"background-color: #5319e7; color: #ffffff">has-conse=
nsus</span> </li>
 =20
  <li>#3085 <a href=3D"https://github.com/quicwg/base-drafts/issues/3085">S=
tateless reset detection should be datagram-based</a> <span class=3D"label"=
 style=3D"background-color: #fbca04; color: #000000">-transport</span> <spa=
n class=3D"label" style=3D"background-color: #1d76db; color: #ffffff">desig=
n</span> <span class=3D"label" style=3D"background-color: #5319e7; color: #=
ffffff">has-consensus</span> </li>
 =20
  <li>#2152 <a href=3D"https://github.com/quicwg/base-drafts/issues/2152">W=
hy does stateless reset have to be checked after MAC failure</a> <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> <span class=3D"label" style=3D"background-color: #5319e=
7; color: #ffffff">has-consensus</span> </li>
 =20
  <li>#3097 <a href=3D"https://github.com/quicwg/base-drafts/issues/3097">I=
s CONNECTION_CLOSE ACK-eliciting?</a> <span class=3D"label" style=3D"backgr=
ound-color: #fbca04; color: #000000">-recovery</span> <span class=3D"label"=
 style=3D"background-color: #fbca04; color: #000000">-transport</span> <spa=
n class=3D"label" style=3D"background-color: #1d76db; color: #ffffff">desig=
n</span> <span class=3D"label" style=3D"background-color: #5319e7; color: #=
ffffff">has-consensus</span> </li>
 =20
  <li>#2741 <a href=3D"https://github.com/quicwg/base-drafts/issues/2741">R=
e-visit initial keys discard</a> <span class=3D"label" style=3D"background-=
color: #fbca04; color: #000000">-tls</span> <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> <=
span class=3D"label" style=3D"background-color: #5319e7; color: #ffffff">ha=
s-consensus</span> </li>
 =20
  <li>#2944 <a href=3D"https://github.com/quicwg/base-drafts/issues/2944">L=
ayout of PreferredAddress</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> <span class=3D=
"label" style=3D"background-color: #5319e7; color: #ffffff">has-consensus</=
span> </li>
  </ul>



<h2>Pull requests</h2>
<h3>quicwg/base-drafts (+3/-5/=F0=9F=92=AC14)</h3>
  <p class=3D"new">3 pull requests submitted:</p>
  <ul>
  <li>#3183 <a href=3D"https://github.com/quicwg/base-drafts/pull/3183">Lim=
it CWND increase in slow start</a> (by ianswett) <span class=3D"label" styl=
e=3D"background-color: #fbca04; color: #">-recovery</span> </li>
 =20
  <li>#3182 <a href=3D"https://github.com/quicwg/base-drafts/pull/3182">Add=
 an enum indicating the timer_mode</a> (by ianswett) <span class=3D"label" =
style=3D"background-color: #fbca04; color: #">-recovery</span> </li>
 =20
  <li>#3178 <a href=3D"https://github.com/quicwg/base-drafts/pull/3178">tok=
en-based greasing / initial packet protection (downgradable variant)</a> (b=
y kazuho) </li>
  </ul>

  <p>8 pull requests received 14 new comments:</p>
  <ul>
  <li>#3183 <a href=3D"https://github.com/quicwg/base-drafts/pull/3183">Lim=
it CWND increase in slow start</a> (2 by ianswett, janaiyengar) <span class=
=3D"label" style=3D"background-color: #fbca04; color: #000000">-recovery</s=
pan> </li>
 =20
  <li>#3182 <a href=3D"https://github.com/quicwg/base-drafts/pull/3182">Add=
 an enum indicating the timer_mode</a> (2 by ianswett, marten-seemann) <spa=
n class=3D"label" style=3D"background-color: #fbca04; color: #000000">-reco=
very</span> </li>
 =20
  <li>#3166 <a href=3D"https://github.com/quicwg/base-drafts/pull/3166">tok=
en-based greasing / initial packet protection</a> (1 by kazuho) <span class=
=3D"label" style=3D"background-color: #fbca04; color: #000000">-transport</=
span> <span class=3D"label" style=3D"background-color: #1d76db; color: #fff=
fff">design</span> </li>
 =20
  <li>#3120 <a href=3D"https://github.com/quicwg/base-drafts/pull/3120">Add=
 retry integrity tag</a> (3 by kazuho, martinthomson, mikkelfj) <span class=
=3D"label" style=3D"background-color: #fbca04; color: #000000">-tls</span> =
<span class=3D"label" style=3D"background-color: #fbca04; color: #000000">-=
transport</span> </li>
 =20
  <li>#3099 <a href=3D"https://github.com/quicwg/base-drafts/pull/3099">Idl=
e timeout indicates you will timeout</a> (1 by ianswett) <span class=3D"lab=
el" style=3D"background-color: #fbca04; color: #000000">-transport</span> <=
/li>
 =20
  <li>#3066 <a href=3D"https://github.com/quicwg/base-drafts/pull/3066">Cha=
nge PTO to be per packet number space</a> (1 by marten-seemann) <span class=
=3D"label" style=3D"background-color: #fbca04; color: #000000">-recovery</s=
pan> <span class=3D"label" style=3D"background-color: #1d76db; color: #ffff=
ff">design</span> </li>
 =20
  <li>#3050 <a href=3D"https://github.com/quicwg/base-drafts/pull/3050">Rew=
rite key update section</a> (3 by DavidSchinazi, martinthomson) <span class=
=3D"label" style=3D"background-color: #fbca04; color: #000000">-tls</span> =
<span class=3D"label" style=3D"background-color: #1d76db; color: #ffffff">d=
esign</span> </li>
 =20
  <li>#3042 <a href=3D"https://github.com/quicwg/base-drafts/pull/3042">Use=
 the FRAME_ENCODING_ERROR for errors in frame encoding</a> (1 by martinthom=
son) <span class=3D"label" style=3D"background-color: #fbca04; color: #0000=
00">-transport</span> <span class=3D"label" style=3D"background-color: #1d7=
6db; color: #ffffff">design</span> </li>
  </ul>

  <p>5 pull requests merged:</p>
  <ul>
  <li>#3167 <a href=3D"https://github.com/quicwg/base-drafts/pull/3167">kMa=
xDatagramSize -&gt; max_datagram_size</a> <span class=3D"label" style=3D"ba=
ckground-color: #fbca04; color: #">-recovery</span> </li>
 =20
  <li>#3045 <a href=3D"https://github.com/quicwg/base-drafts/pull/3045">All=
ow ClientHello to span multiple QUIC packets</a> <span class=3D"label" styl=
e=3D"background-color: #fbca04; color: #">-tls</span> </li>
 =20
  <li>#3096 <a href=3D"https://github.com/quicwg/base-drafts/pull/3096">MUS=
T retire Connection IDs becoming stale</a> <span class=3D"label" style=3D"b=
ackground-color: #fbca04; color: #">-transport</span> <span class=3D"label"=
 style=3D"background-color: #1d76db; color: #">design</span> </li>
 =20
  <li>#2993 <a href=3D"https://github.com/quicwg/base-drafts/pull/2993">Sta=
teless reset comparisons (constant time/any order/datagram)</a> <span class=
=3D"label" style=3D"background-color: #fbca04; color: #">-transport</span> =
<span class=3D"label" style=3D"background-color: #1d76db; color: #">design<=
/span> </li>
 =20
  <li>#3098 <a href=3D"https://github.com/quicwg/base-drafts/pull/3098">CON=
NECTION_CLOSE is non-ack-eliciting</a> <span class=3D"label" style=3D"backg=
round-color: #fbca04; color: #">-recovery</span> <span class=3D"label" styl=
e=3D"background-color: #fbca04; color: #">-transport</span> <span class=3D"=
label" style=3D"background-color: #1d76db; color: #">design</span> </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>

--===============2291551005938582497==--


From nobody Sun Nov  3 13:46:13 2019
Return-Path: <mt@lowentropy.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 3C500120024 for <quic@ietfa.amsl.com>; Sun,  3 Nov 2019 13:46:12 -0800 (PST)
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=lowentropy.net header.b=lco/hY6R; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=AEt3y200
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 mopeIiBhCkST for <quic@ietfa.amsl.com>; Sun,  3 Nov 2019 13:46:10 -0800 (PST)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 06BC312001E for <quic@ietf.org>; Sun,  3 Nov 2019 13:46:10 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 4AB7C3F5 for <quic@ietf.org>; Sun,  3 Nov 2019 16:46:09 -0500 (EST)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Sun, 03 Nov 2019 16:46:09 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type:content-transfer-encoding; s=fm3; bh=uJGLt /rnvdeBlVRVaQKWv4SGbpYeb1Ji07deJRK0xYg=; b=lco/hY6R5y7aLE7JkBWBn CYRc9/tI8nLrsx8cUrnLeryEDpXKPLanph/j9ApL5p0Gb/gVmFV8BRX9O2KbrlDd VBA0GGbTpGGY4HwmQ6oNOyBDp4HI750Hf0wB+y6lzRoL0h2Sthl6Qd3UIqiKOfmn nC/2vLiL1c3pkhO/x73zF4yZ2n4eqejmzH4ixyUYlax3qgYXpAVoPMUR3ZgdVjw8 QFGEr/G4QI+7HQi6yv9bLD4JgX+a4+8AbjEwR5b2rSwJPcToJ3MSOy0Ckqiutkg3 JmiCQM79NwAaszOZwIB6uwGL+lNOkFDecS9Dxpcqd5suIVbNXC0qzw47rs6aCUxd Q==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=uJGLt/rnvdeBlVRVaQKWv4SGbpYeb1Ji07deJRK0x Yg=; b=AEt3y200hI/dQ0by4rEpIwSoC7KZ3iIqdWKHAULwTDn6Af1aIi14NyTud W912F864n1yD2DGd+1jsRa+vdpLNwofy2Hzix3GdYEEtxwy8vjpjTYyhDXdKrudI /Jtt/aA8rOjyHvVeT9XYKRelsl4Lcr1YY+6qvxPqIVvABMgnpnvZOzPwRfagLM3y P5g4LQikRNST1eWtiGXL66xFLmGKsy4/JM2evjjflRvpLM/cGJdZyNeCHJknRT2E tlvOWRBAGSN5SDNbqcfOOqhCKPAFxhrnSqlKlpRzn/fYcxrhyxOmB4ocoJn/51Ys m3/z4agcGkQbzsZYCkdcJS3Q6O/jw==
X-ME-Sender: <xms:oEq_XcLAv6A5GeTdbAHxxNyd2Hrar4tKaKUd51Q5Fbs2Is_DMNLHGQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudduuddgudehjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgfgse htqhertderreejnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmthes lhhofigvnhhtrhhophihrdhnvghtqeenucffohhmrghinhepghhithhhuhgsrdgtohhmne curfgrrhgrmhepmhgrihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrdhnvghtnecu vehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:oEq_XVnil6581CSvQgproUqS8ihlJyAN4U2lXSmX60nt0Z1LTNJhFg> <xmx:oEq_Xdiw9XM-NtZbI7HYINPbV0DHLViUe-Ed8_lCCL3xb1ebDX8pRg> <xmx:oEq_XUuxCdAQKOP-EqhL8PEFLsOWn5GTLTZBioGTcstFKFHqMBkqyA> <xmx:oEq_XcUZKpm3hb4ASBLEazYegl0u_jVy_LPdo_Bs5isIDaFlrhs2hQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 6322BE00A5; Sun,  3 Nov 2019 16:46:08 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-509-ge3ec61c-fmstable-20191030v1
Mime-Version: 1.0
Message-Id: <e24ecddd-139d-4669-be96-b3de57557c4e@www.fastmail.com>
In-Reply-To: <BN6PR2201MB1700184D81061E2CBFD77BFBDA620@BN6PR2201MB1700.namprd22.prod.outlook.com>
References: <CAPDSy+6E79OySoOLbJ8eWp0J-+3yeB5iGvj6sW19bEDn_V7-NA@mail.gmail.com> <CANatvzzaWFgrvnaV=VeZRAVvxqSBeMSZT5aMUu7-Vh9raeZJFw@mail.gmail.com> <BN6PR2201MB1700184D81061E2CBFD77BFBDA620@BN6PR2201MB1700.namprd22.prod.outlook.com>
Date: Mon, 04 Nov 2019 08:45:41 +1100
From: "Martin Thomson" <mt@lowentropy.net>
To: quic@ietf.org
Subject: Re: Version Ossification: Intended Scope for QUICv1
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/qXJHW0gWnEK8tiD9nIZSxasWn_8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 03 Nov 2019 21:46:12 -0000

Why can't servers just bake the "keys" into binaries?  I mean, that's no=
t something that is likely to get lost.  And it isn't really the case th=
at keys need to be secret, they just have to change often enough to frus=
trate attempts to fixate on them.

On Sat, Nov 2, 2019, at 03:13, Mike Bishop wrote:
> =20
> The fundamental problem in all this is what happens when a server is n=
o=20
> longer in possession of the mapping it sent to the client. One option=20=

> is to say that servers simply MUST persist this, and if they don=E2=80=
=99t,=20
> handshakes will fail =E2=80=93 we tried that with HSTS, and we found t=
hat=20
> servers don=E2=80=99t like things that can leave the site broken. I do=
n=E2=80=99t think=20
> that=E2=80=99s a good path. Either it will break things, or servers wo=
n=E2=80=99t use=20
> this mechanism, or more likely both in sequence.
>=20
>=20
> The next obvious solution, sending a VN packet telling the client to=20=

> come back to v1 and the spec-defined salt, contains a simple version=20=

> downgrade attack by a middlebox. There are possible mitigations =E2=80=
=93 the=20
> client could continue presenting the token, meaning the server would b=
e=20
> able to tell whether a downgrade =E2=80=9Cactually happened=E2=80=9D o=
r not. (I.e.=20
> whether it could still have parsed the version associated with the=20
> token) If the downgrade was illegitimate, that could be communicated.=20=

> However, that likely means figuring out QUIC=E2=80=99s own version neg=
otiation=20
> story and downgrade mitigation and just using that.
>=20
>=20
> We could also try to build something like ESNI=E2=80=99s recovery path=
, where=20
> the information includes what has to be demonstrated for a recovery=20=

> value. The trouble is that, while TLS can transfer a certificate and=20=

> rely on PKI as that recovery path, we=E2=80=99re in a little bit more =
uncharted=20
> territory. The only ready solution I see in this space is some kind of=
=20
> longer-lived keypair that the server is somehow =E2=80=9Cless likely=E2=
=80=9D to lose,=20
> but if you can persist that key, you can probably also persist the=20
> original configuration. (Plus, you don=E2=80=99t want to be doing asym=
metric=20
> crypto before you=E2=80=99ve even decided whether to process the hands=
hake.)
>=20
>=20
> I remain a little uncomfortable that we entirely punted our version=20=

> negotiation story from v1, and I think the cleanest solution is to=20
> bring it back in support of #3166. However, that has both schedule and=
=20
> security implications =E2=80=93 we don=E2=80=99t want to get this part=
 wrong.
>=20
>=20
> *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of * Kazuho Oku
> *Sent:* Thursday, October 31, 2019 5:34 PM
> *To:* David Schinazi <dschinazi.ietf@gmail.com>
> *Cc:* QUIC <quic@ietf.org>
> *Subject:* Re: Version Ossification: Intended Scope for QUICv1
>=20
>=20
> Hi David,
>=20
>=20
> Thank you for summarizing the high-level options. I think it's very=20=

> useful to have this discussion.
>=20
>=20
> Please see my comments below.
>=20
>=20
> 2019=E5=B9=B411=E6=9C=881=E6=97=A5(=E9=87=91) 6:13 David Schinazi <dsc=
hinazi.ietf@gmail.com>:
>=20
> > Hi folks,
>=20
>=20
> > The conversation around version ossification has been really interes=
ting since Cupertino. But at least for me it's reached a level of comple=
xity that warrants taking a step back and looking at what we're trying t=
o solve. Here's my understanding of where we are:
>=20
>=20
> > 1) In Cupertino there was consensus in the room to do something to m=
itigate ossification of QUICv1.
>=20
>=20
> > 2) The solution that folks liked was to have a concept of alternativ=
e versions and alternative salts that act like QUICv1 but are encoded di=
fferently over the wire.
>=20
>=20
> > 3) A concrete proposal for (2) was for servers to have their own set=
 of (alternative_version, alternative_salt) pairs, then transmit a rando=
m pair from that set to each client (i.e. via transport parameters). The=
 server can then reconstruct the alternative_salt just by seeing the alt=
ernative_version.
>=20
>=20
> > 4) Kazuho proposed a solution (#3166 <https://github.com/quicwg/base=
-drafts/pull/3166>) that was both more powerful and more complex: tie th=
e (alternative_version, alternative_salt) pair to NEW_TOKEN frames, to a=
llow servers to generate a unique alternative_salt per client and encode=
 it in the token.
>=20
>=20
> I dispute the argument that #3166 is more complex. My view is that=20
> #3166 is more powerful and simpler than (3) (the PR being #2573).
>=20
>=20
> Reasons:
>=20
> * For a server associating one initial salt with one alternative=20
> version, #3166 and #2573 are identical with the exception being how th=
e=20
> information is carryied (i.e. TP vs. NEW_TOKEN).
>=20
> * For a client, bundling the alternative seeds in a NEW_TOKEN makes=20=

> things simpler, as clients are not required to have a new state that=20=

> has to be retained across multiple connections.
>=20
>=20
>=20
> > 5) After some interesting back and forth on that PR, it became clear=
 that this is a hard problem to solve: this could cause failures if serv=
ers forget their token keys, and mitigations for that problem can become=
 downgrade attack vectors
>=20
>=20
> The proposal for 3 has this problem. It leads to a failure when a=20
> server forgets the alternative initial salts.
>=20
>=20
>=20
> > 6) While there was clear WG appetite for (1), I'm not sure we have c=
onsensus to build a more powerful solution like (4)
>=20
>=20
> > I fear that solving (5) could take some time, which would delay QUIC=
v1. Instead I'd like to propose the following plan:
>=20
> > a) we take the simpler solution (3) and add that to the spec
>=20
> > b) we take the more powerful/complex solution (5) a turn it into a Q=
UIC extension
>=20
>=20
> > That would allow us to ship QUICv1 with some level of ossification m=
itigations without delay.
>=20
>=20
> As stated, the proposed solution for (4) is simpler than (3), can be=20=

> used to implement (3), and also provides a stronger protection for=20
> servers certain that they can retain the token unprotection keys.
>=20
>=20
> I agree that solving (5) for all parties might be hard, and that we=20=

> might want to punt that to v2. But, I think we should adopt (4) than=20=

> (3) due to the aforementioned reasons.
>=20
>=20
>=20
> > Thoughts?
>=20
>=20
> > David
>=20
>=20
>=20
>=20
>=20
>=20
> --=20
>=20
> Kazuho Oku
>


From nobody Sun Nov  3 20:16:29 2019
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 1AA21120251; Sun,  3 Nov 2019 20:16:18 -0800 (PST)
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-24.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.108.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <157284097806.13428.3959681128468187700@ietfa.amsl.com>
Date: Sun, 03 Nov 2019 20:16:18 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/a97OrjDI3yMoc4AtWGvIVZnkPro>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 04:16:18 -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-24.txt
	Pages           : 156
	Date            : 2019-11-03

Abstract:
   This document defines the core of the QUIC transport protocol.
   Accompanying documents describe QUIC's loss detection and congestion
   control and the use of TLS for key negotiation.

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

   Working Group information can be found at <https://github.com/
   quicwg>; source code and issues list for this draft can be found at
   <https://github.com/quicwg/base-drafts/labels/-transport>.


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-24
https://datatracker.ietf.org/doc/html/draft-ietf-quic-transport-24

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-transport-24


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 Sun Nov  3 20:16:51 2019
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 59A3B1209C3; Sun,  3 Nov 2019 20:16:36 -0800 (PST)
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-24.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.108.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <157284099630.13436.17238984465035648690@ietfa.amsl.com>
Date: Sun, 03 Nov 2019 20:16:36 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/IHDBU5MwE83hmS45YPxVmHJxfp8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 04:16: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           : Using TLS to Secure QUIC
        Authors         : Martin Thomson
                          Sean Turner
	Filename        : draft-ietf-quic-tls-24.txt
	Pages           : 49
	Date            : 2019-11-03

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-24
https://datatracker.ietf.org/doc/html/draft-ietf-quic-tls-24

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-tls-24


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 Mon Nov  4 03:22:38 2019
Return-Path: <lars@eggert.org>
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 228AF120104 for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 03:22:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 2HV_zKhaAGVN for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 03:22:30 -0800 (PST)
Received: from emh07.mail.saunalahti.fi (emh07.mail.saunalahti.fi [62.142.5.117]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DAF4C1200B1 for <quic@ietf.org>; Mon,  4 Nov 2019 03:22:29 -0800 (PST)
Received: from eggert.org (unknown [62.248.255.8]) by emh07.mail.saunalahti.fi (Postfix) with ESMTP id E0F00B004C for <quic@ietf.org>; Mon,  4 Nov 2019 13:22:27 +0200 (EET)
Received: from slate.eggert.org (Slate.eggert.org [172.19.235.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by eggert.org (Postfix) with ESMTPSA id 7452388E681 for <quic@ietf.org>; Mon,  4 Nov 2019 13:22:20 +0200 (EET)
From: Lars Eggert <lars@eggert.org>
Content-Type: multipart/alternative; boundary="Apple-Mail=_216CC251-06CA-47F4-8EF3-28FA0E38B1E0"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: Fwd: [Pearg] New Version Notification for draft-andersdotter-rrm-for-rrt-in-http3-00.txt
Message-Id: <2E363B7F-DE31-478F-8670-91610E78472B@eggert.org>
References: <cdcafeda-4ddb-c102-0851-42cf6261f7e9@article19.org>
To: QUIC IETF mailing list <quic@ietf.org>
Date: Mon, 4 Nov 2019 13:22:20 +0200
X-MailScanner-ID: 7452388E681.A28C6
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/umrFjA4LFJgOgneKldDABQziras>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 11:22:32 -0000

--Apple-Mail=_216CC251-06CA-47F4-8EF3-28FA0E38B1E0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Potentially of interest to the WG.

Begin forwarded message:
>=20
> From: Amelia Andersdotter <amelia@article19.org>
> Subject: [Pearg] Fwd: New Version Notification for =
draft-andersdotter-rrm-for-rrt-in-http3-00.txt
> Date: November 3, 2019 at 21:46:45 GMT+2
> To: pearg@irtf.org
>=20
> Dear all,
>=20
> Since this spring, I've had a conversation with Shivan about the
> possibility of using differential privacy tools in QUIC to alleviate
> privacy concerns with the spin bit. We were not able to establish any
> immediate reason for differential privacy being an appropriate
> additional tool for this purpose.
>=20
> The resulting inquiry is this draft, which is now posted with a view =
to
> gathering comments from all of you (we hope).
>=20
> It will not be presented in Singapore, but we're hoping to develop it
> over the upcoming months. Please reach out with any questions or =
comments!
>=20
> best regards,
>=20
> Amelia
>=20
>=20
> -------- Forwarded Message --------
> Subject: 	New Version Notification for
> draft-andersdotter-rrm-for-rrt-in-http3-00.txt
> Date: 	Sun, 03 Nov 2019 11:42:01 -0800
> From: 	internet-drafts@ietf.org
> To: 	Shivan Sahib <shivankaulsahib@gmail.com>, Amelia Andersdotter
> <amelia@article19.org>
>=20
>=20
>=20
>=20
> A new version of I-D, draft-andersdotter-rrm-for-rrt-in-http3-00.txt
> has been successfully submitted by Amelia Andersdotter and posted to =
the
> IETF repository.
>=20
> Name: draft-andersdotter-rrm-for-rrt-in-http3
> Revision: 00
> Title: Randomized Response Mechanisms in RRT Measurements for HTTP/3
> Document date: 2019-11-03
> Group: Individual Submission
> Pages: 15
> URL:
> =
https://www.ietf.org/internet-drafts/draft-andersdotter-rrm-for-rrt-in-htt=
p3-00.txt
> Status:
> =
https://datatracker.ietf.org/doc/draft-andersdotter-rrm-for-rrt-in-http3/
> Htmlized:
> https://tools.ietf.org/html/draft-andersdotter-rrm-for-rrt-in-http3-00
> Htmlized:
> =
https://datatracker.ietf.org/doc/html/draft-andersdotter-rrm-for-rrt-in-ht=
tp3
>=20
>=20
> Abstract:
> The latency spin bit is an optional feature included in the QUIC
> transport protocol [I-D-QUIC]. It enables passive, on-path
> observations for estimation of latency. This document presents the
> results of an inquiry into the potential of using randomized response
> mechanisms (RRM) to reduce privacy loss in latency measurements. It
> concludes that RRM could be used to introduce choice for clients in
> preserving privacy in latency measurements. But the trade-offs,
> especially since the latency spin bit is already optional, do not
> favour RRM.
>=20
>=20
>=20
> 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.
>=20
> The IETF Secretariat
>=20
> --=20
> Pearg mailing list
> Pearg@irtf.org
> https://www.irtf.org/mailman/listinfo/pearg


--Apple-Mail=_216CC251-06CA-47F4-8EF3-28FA0E38B1E0
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=us-ascii

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" =
class=3D"">Potentially of interest to the WG.<br class=3D""><div><br =
class=3D""></div><div>Begin forwarded message:<br class=3D""><blockquote =
type=3D"cite" class=3D""><br class=3D"Apple-interchange-newline"><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">From: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">Amelia Andersdotter &lt;<a =
href=3D"mailto:amelia@article19.org" =
class=3D"">amelia@article19.org</a>&gt;<br class=3D""></span></div><div =
style=3D"margin-top: 0px; margin-right: 0px; margin-bottom: 0px; =
margin-left: 0px;" class=3D""><span style=3D"font-family: =
-webkit-system-font, Helvetica Neue, Helvetica, sans-serif; =
color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Subject: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><b class=3D"">[Pearg] Fwd: New =
Version Notification for =
draft-andersdotter-rrm-for-rrt-in-http3-00.txt</b><br =
class=3D""></span></div><div style=3D"margin-top: 0px; margin-right: =
0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span =
style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">Date: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D"">November 3, 2019 at 21:46:45 =
GMT+2<br class=3D""></span></div><div style=3D"margin-top: 0px; =
margin-right: 0px; margin-bottom: 0px; margin-left: 0px;" class=3D""><span=
 style=3D"font-family: -webkit-system-font, Helvetica Neue, Helvetica, =
sans-serif; color:rgba(0, 0, 0, 1.0);" class=3D""><b class=3D"">To: =
</b></span><span style=3D"font-family: -webkit-system-font, Helvetica =
Neue, Helvetica, sans-serif;" class=3D""><a href=3D"mailto:pearg@irtf.org"=
 class=3D"">pearg@irtf.org</a><br class=3D""></span></div><br =
class=3D""><div class=3D""><div class=3D"">Dear all,<br class=3D""><br =
class=3D"">Since this spring, I've had a conversation with Shivan about =
the<br class=3D"">possibility of using differential privacy tools in =
QUIC to alleviate<br class=3D"">privacy concerns with the spin bit. We =
were not able to establish any<br class=3D"">immediate reason for =
differential privacy being an appropriate<br class=3D"">additional tool =
for this purpose.<br class=3D""><br class=3D"">The resulting inquiry is =
this draft, which is now posted with a view to<br class=3D"">gathering =
comments from all of you (we hope).<br class=3D""><br class=3D"">It will =
not be presented in Singapore, but we're hoping to develop it<br =
class=3D"">over the upcoming months. Please reach out with any questions =
or comments!<br class=3D""><br class=3D"">best regards,<br class=3D""><br =
class=3D"">Amelia<br class=3D""><br class=3D""><br class=3D"">-------- =
Forwarded Message --------<br class=3D"">Subject: <span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>New =
Version Notification for<br =
class=3D"">draft-andersdotter-rrm-for-rrt-in-http3-00.txt<br =
class=3D"">Date: <span class=3D"Apple-tab-span" style=3D"white-space:pre">=
	</span>Sun, 03 Nov 2019 11:42:01 -0800<br class=3D"">From: <span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span><a =
href=3D"mailto:internet-drafts@ietf.org" =
class=3D"">internet-drafts@ietf.org</a><br class=3D"">To: <span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	</span>Shivan =
Sahib &lt;shivankaulsahib@gmail.com&gt;, Amelia Andersdotter<br =
class=3D"">&lt;amelia@article19.org&gt;<br class=3D""><br class=3D""><br =
class=3D""><br class=3D""><br class=3D"">A new version of I-D, =
draft-andersdotter-rrm-for-rrt-in-http3-00.txt<br class=3D"">has been =
successfully submitted by Amelia Andersdotter and posted to the<br =
class=3D"">IETF repository.<br class=3D""><br class=3D"">Name: =
draft-andersdotter-rrm-for-rrt-in-http3<br class=3D"">Revision: 00<br =
class=3D"">Title: Randomized Response Mechanisms in RRT Measurements for =
HTTP/3<br class=3D"">Document date: 2019-11-03<br class=3D"">Group: =
Individual Submission<br class=3D"">Pages: 15<br class=3D"">URL:<br =
class=3D"">https://www.ietf.org/internet-drafts/draft-andersdotter-rrm-for=
-rrt-in-http3-00.txt<br class=3D"">Status:<br =
class=3D"">https://datatracker.ietf.org/doc/draft-andersdotter-rrm-for-rrt=
-in-http3/<br class=3D"">Htmlized:<br =
class=3D"">https://tools.ietf.org/html/draft-andersdotter-rrm-for-rrt-in-h=
ttp3-00<br class=3D"">Htmlized:<br =
class=3D"">https://datatracker.ietf.org/doc/html/draft-andersdotter-rrm-fo=
r-rrt-in-http3<br class=3D""><br class=3D""><br class=3D"">Abstract:<br =
class=3D"">The latency spin bit is an optional feature included in the =
QUIC<br class=3D"">transport protocol [I-D-QUIC]. It enables passive, =
on-path<br class=3D"">observations for estimation of latency. This =
document presents the<br class=3D"">results of an inquiry into the =
potential of using randomized response<br class=3D"">mechanisms (RRM) to =
reduce privacy loss in latency measurements. It<br class=3D"">concludes =
that RRM could be used to introduce choice for clients in<br =
class=3D"">preserving privacy in latency measurements. But the =
trade-offs,<br class=3D"">especially since the latency spin bit is =
already optional, do not<br class=3D"">favour RRM.<br class=3D""><br =
class=3D""><br class=3D""><br class=3D"">Please note that it may take a =
couple of minutes from the time of submission<br class=3D"">until the =
htmlized version and diff are available at tools.ietf.org.<br =
class=3D""><br class=3D"">The IETF Secretariat<br class=3D""><br =
class=3D"">-- <br class=3D"">Pearg mailing list<br =
class=3D"">Pearg@irtf.org<br =
class=3D"">https://www.irtf.org/mailman/listinfo/pearg<br =
class=3D""></div></div></blockquote></div><br class=3D""></body></html>=

--Apple-Mail=_216CC251-06CA-47F4-8EF3-28FA0E38B1E0--


From nobody Mon Nov  4 06:30:43 2019
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 6E3051208B4; Mon,  4 Nov 2019 06:30:32 -0800 (PST)
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-24.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.108.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <157287783235.16491.13235950151277932890@ietfa.amsl.com>
Date: Mon, 04 Nov 2019 06:30:32 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2ybONZnR9C2OYIywcmSTfWCXu5s>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 14:30:36 -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 Version 3 (HTTP/3)
        Author          : Mike Bishop
	Filename        : draft-ietf-quic-http-24.txt
	Pages           : 58
	Date            : 2019-11-03

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 HTTP/3.


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-24
https://datatracker.ietf.org/doc/html/draft-ietf-quic-http-24

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-http-24


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 Mon Nov  4 06:30:59 2019
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 A3F801209EA; Mon,  4 Nov 2019 06:30:54 -0800 (PST)
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-11.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.108.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <157287785461.16487.8602052883957603879@ietfa.amsl.com>
Date: Mon, 04 Nov 2019 06:30:54 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/1ZnikUWKoAGT2fWst0iX6fM-gaw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 14:30: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           : QPACK: Header Compression for HTTP/3
        Authors         : Charles 'Buck' Krasic
                          Mike Bishop
                          Alan Frindell
	Filename        : draft-ietf-quic-qpack-11.txt
	Pages           : 38
	Date            : 2019-11-03

Abstract:
   This specification defines QPACK, a compression format for
   efficiently representing HTTP header fields, to be used in HTTP/3.
   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-11
https://datatracker.ietf.org/doc/html/draft-ietf-quic-qpack-11

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-qpack-11


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 Mon Nov  4 06:47:40 2019
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 C134F120236; Mon,  4 Nov 2019 06:47:32 -0800 (PST)
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-24.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 6.108.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <157287885270.16580.10232785430162607708@ietfa.amsl.com>
Date: Mon, 04 Nov 2019 06:47:32 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/qtStN7HBk_gtEF4ClDxGzAbUpyM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 14:47:39 -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-24.txt
	Pages           : 40
	Date            : 2019-11-03

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-24
https://datatracker.ietf.org/doc/html/draft-ietf-quic-recovery-24

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-ietf-quic-recovery-24


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 Mon Nov  4 08:58:20 2019
Return-Path: <mirja.kuehlewind@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 A18CC120B1A; Mon,  4 Nov 2019 08:58:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_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=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 1kXAzl2klza1; Mon,  4 Nov 2019 08:58:13 -0800 (PST)
Received: from EUR02-AM5-obe.outbound.protection.outlook.com (mail-eopbgr00065.outbound.protection.outlook.com [40.107.0.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id ABAC2120AF2; Mon,  4 Nov 2019 08:58:12 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=MKsP7OFNQqu/hR6oqKPjciAZApSMOBfOBs3pWd5pOR7tmtp78exiY1c3BuERgB19U78+TfilL6Wq3jU8TOjjVblNspicab/9c2ceWV8KhUxYILeSr7a6H8vkHHn8pDOkCJRqfyCRJCKtIR7pJDf/LgW0fOKpbLd2Z3s2y7jzG2L7vrLMomx2imy9JTtzw/FVFe+tn2y3bU2I3vhEHPeno+5heYXZpZKfJwYszZMx7dfPymUpOOtsaTfDzrs5z5gzjBoJTBSA8aS9nMtJAYpbxGBsLUFuQomCq6WCIv+67XgtlGWbS8+3/rxTEWY/4T14B+VG7g6f0YuySl1uLufSbw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DAYoDClKa3cxv65hGtCfanUieTdNUUq1/bdwTsuFSIM=; b=SZU2npUDnXIB5pn3hQSa2gI4HZ5MNDjzXOqLUbarFauj+XAKfM8vUZJ13/30kO3lBOS6pZk2xd9GptHxK7KK5C4BCW5B8jwIslPUEvXBN+KHm8SsJUsr+/pAR8RoVbQelesKDmw69QgPYZzNA4sQbI5HL13xFr8sk8pTd0xuicOP9KIEs6Paoax4hV2qDxjPr0Zef2CGQn3xrJvDM94F1lAGQY65AUBHcLPCyDMDJHr9DtO+ldN7kF4DKJANHUepOD7jbduj5MO3/LU67N/0DKRzKpInDrYrlMI9pEnGuixG5eWokwqx9xTxmhO2NpZcf2flAq0t++xCylYVGylnUQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=DAYoDClKa3cxv65hGtCfanUieTdNUUq1/bdwTsuFSIM=; b=UK6ogWQ8aYZqh3qeZciHiRyoviFBp6wtX0y4Gk5SkaoIvfx1qTRbURR/LGfW82Sm8G+HTiN4Q1U22kAg9ZYI2dc4IhmnJBA8+ThlC5GSihuk07FaUajX0Xpp4XGun14/vEW/anvZtFMw8QrBlCOn2mpLIUEk4JsA7z/FWUiFJus=
Received: from AM0PR07MB4691.eurprd07.prod.outlook.com (52.135.149.158) by AM0PR07MB5170.eurprd07.prod.outlook.com (20.178.17.206) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2430.16; Mon, 4 Nov 2019 16:58:10 +0000
Received: from AM0PR07MB4691.eurprd07.prod.outlook.com ([fe80::4189:4ef8:bfc1:ec58]) by AM0PR07MB4691.eurprd07.prod.outlook.com ([fe80::4189:4ef8:bfc1:ec58%7]) with mapi id 15.20.2430.013; Mon, 4 Nov 2019 16:58:10 +0000
From: Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>
To: "quic@ietf.org" <quic@ietf.org>, "masque@ietf.org" <masque@ietf.org>
CC: Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Subject: FW: New Version Notification for draft-kuehlewind-quic-proxy-discovery-00.txt
Thread-Topic: New Version Notification for draft-kuehlewind-quic-proxy-discovery-00.txt
Thread-Index: AQHVkzBtXqSCGBS1QEWLK0BXXTrwWKd7THMA
Date: Mon, 4 Nov 2019 16:58:10 +0000
Message-ID: <CA5EB3C0-F510-4883-B50B-51A3E46B47CA@ericsson.com>
References: <157288641719.16495.4218503379126128243.idtracker@ietfa.amsl.com>
In-Reply-To: <157288641719.16495.4218503379126128243.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mirja.kuehlewind@ericsson.com; 
x-originating-ip: [2003:eb:4700:cf00:3d57:7e7e:af67:8db2]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b498d8fa-8011-4583-f899-08d761482c32
x-ms-traffictypediagnostic: AM0PR07MB5170:|AM0PR07MB5170:
x-ms-exchange-purlcount: 4
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <AM0PR07MB51701A4DC994367F34C216A5F47F0@AM0PR07MB5170.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-forefront-prvs: 0211965D06
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(396003)(136003)(376002)(39860400002)(366004)(346002)(199004)(189003)(25584004)(53754006)(7736002)(305945005)(6436002)(229853002)(36756003)(33656002)(2501003)(2906002)(256004)(6486002)(6116002)(14454004)(71190400001)(71200400001)(25786009)(966005)(478600001)(81166006)(81156014)(8676002)(450100002)(8936002)(99286004)(66946007)(66476007)(64756008)(66556008)(66446008)(14444005)(46003)(5660300002)(110136005)(11346002)(44832011)(446003)(476003)(486006)(6506007)(2473003)(102836004)(6306002)(186003)(66574012)(86362001)(76176011)(76116006)(6512007)(107886003)(4326008)(316002)(2616005); DIR:OUT; SFP:1101; SCL:1; SRVR:AM0PR07MB5170; H:AM0PR07MB4691.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: TLn4YMmge/I0kGjjPEl5Bt+9f78zDPnJ0RuOdYnzAhz3djO6FoSitFWGxbqfMz+s/F2RGQ3QLCBayZKMTH7aIyolltp23bGWshMTYXZxPxL/HEamjMqo2Ugpf2RwqMM3YDd9uxF7WS0NJAmrWDhjns/Kvdk/V051alHCe5bcv9jzk036w5lUk65UyMTCKckTRRb8+30Lfu6G2Vgc3LnD7ccYAylSseEcDG0BkG088ZqZcRALCMhpZS2hE3hPLY9XWl7Yp3zU3Vr7EJYO9Rq/3O3SCBRze6Bng/EJwtj2i02V1KDSqFqtXZ5FJZfHNME4v8y/KDc51+3ydv54d7LlqQ635KLLAyoszFsGLZK5MVF+FhFxC8YuEk9vZul3KOhOcjxEBNalxdZihbdbiavz6hl6t8gZmuQoauOx21K7OKAct0jwfm/6Nwty7iM9zs+Lwh0QGdiAlfPmkxl+xHQRlTr1Qf4F1BO+oc5roB83J1k=
Content-Type: text/plain; charset="utf-8"
Content-ID: <7C1B7259E3D1C344B7146F9460CD7CF1@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b498d8fa-8011-4583-f899-08d761482c32
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Nov 2019 16:58:10.2092 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: J+0fUe3aBya8eyneMjxnNg1cy5tbF70r2yv67vlaLOEN5dxRzAH5TV/iCVg3J67lZIb0u+8k4ru8Tq0eGwVxnGoeZKLWQbcUok00+GfVrqc=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB5170
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/qT3pdFbVRFU65Dulu1TCFXdk-JE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 16:58:19 -0000

SGkgYWxsLA0KDQp3ZSBzdWJtaXR0ZWQgYSBuZXcgZHJhZnQgdGhhdCBsaXN0cyBkaXNjb3Zlcnkg
bWVjaGFuaXNtcyBmb3IgUVVJQy1iYXNlZCBwcm94aWVzIChzZWUgYmVsb3cpLiBUaGlzIGlzIG9u
ZSBwaWVjZSBvZiB3b3JrIHRoYXQgaXMgbmVlZGVkIGZvciBtb3N0IG9mIHRoZSB1c2UgY2FzZXMg
aW4gZHJhZnQta3VlaGxld2luZC1xdWljLXN1YnN0cmF0ZS4gDQoNCkxldCBtZSBrbm93IGlmIHlv
dSBoYXZlIGFueSBxdWVzdGlvbnMgb3IgY29tbWVudHMhDQoNCk1pcmphDQoNCg0K77u/T24gMDQu
MTEuMTksIDE3OjUzLCAiaW50ZXJuZXQtZHJhZnRzQGlldGYub3JnIiA8aW50ZXJuZXQtZHJhZnRz
QGlldGYub3JnPiB3cm90ZToNCg0KICAgIA0KICAgIEEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFm
dC1rdWVobGV3aW5kLXF1aWMtcHJveHktZGlzY292ZXJ5LTAwLnR4dA0KICAgIGhhcyBiZWVuIHN1
Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkgTWlyamEgS3VlaGxld2luZCBhbmQgcG9zdGVkIHRvIHRo
ZQ0KICAgIElFVEYgcmVwb3NpdG9yeS4NCiAgICANCiAgICBOYW1lOgkJZHJhZnQta3VlaGxld2lu
ZC1xdWljLXByb3h5LWRpc2NvdmVyeQ0KICAgIFJldmlzaW9uOgkwMA0KICAgIFRpdGxlOgkJRGlz
Y292ZXJ5IE1lY2hhbmlzbSBmb3IgUVVJQy1iYXNlZCwgTm9uLXRyYW5zcGFyZW50IFByb3h5IFNl
cnZpY2VzDQogICAgRG9jdW1lbnQgZGF0ZToJMjAxOS0xMS0wNA0KICAgIEdyb3VwOgkJSW5kaXZp
ZHVhbCBTdWJtaXNzaW9uDQogICAgUGFnZXM6CQkxMQ0KICAgIFVSTDogICAgICAgICAgICBodHRw
czovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQta3VlaGxld2luZC1xdWljLXBy
b3h5LWRpc2NvdmVyeS0wMC50eHQNCiAgICBTdGF0dXM6ICAgICAgICAgaHR0cHM6Ly9kYXRhdHJh
Y2tlci5pZXRmLm9yZy9kb2MvZHJhZnQta3VlaGxld2luZC1xdWljLXByb3h5LWRpc2NvdmVyeS8N
CiAgICBIdG1saXplZDogICAgICAgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWt1
ZWhsZXdpbmQtcXVpYy1wcm94eS1kaXNjb3ZlcnktMDANCiAgICBIdG1saXplZDogICAgICAgaHR0
cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvaHRtbC9kcmFmdC1rdWVobGV3aW5kLXF1aWMt
cHJveHktZGlzY292ZXJ5DQogICAgDQogICAgDQogICAgQWJzdHJhY3Q6DQogICAgICAgT2Z0ZW4g
YW4gaW50ZXJtZWRpYXRlIGluc3RhbmNlIChzdWNoIGFzIGEgcHJveHkgc2VydmVyKSBpcyB1c2Vk
IHRvDQogICAgICAgY29ubmVjdCB0byBhIHdlYiBzZXJ2ZXIgb3IgYSBjb21tdW5pY2F0aW5nIHBl
ZXIgaWYgYSBkaXJlY3QgZW5kLXRvLQ0KICAgICAgIGVuZCBJUCBjb25uZWN0aXZpdHkgaXMgbm90
IHBvc3NpYmxlIG9yIHRoZSBwcm94eSBjYW4gcHJvdmlkZSBhDQogICAgICAgc3VwcG9ydCBzZXJ2
aWNlIGxpa2UsIGUuZy4sIGFkZHJlc3MgYW5vbnltaXNhdGlvbi4gIFRvIHVzZSBhIG5vbi0NCiAg
ICAgICB0cmFuc3BhcmVudCBwcm94eSBhIGNsaWVudCBleHBsaWNpdGx5IGNvbm5lY3RzIHRvIGl0
IGFuZCByZXF1ZXN0cw0KICAgICAgIGZvcndhcmRpbmcgdG8gdGhlIGZpbmFsIHRhcmdldCBzZXJ2
ZXIuICBUaGUgY2xpZW50IGVpdGhlciBrbm93cyB0aGUNCiAgICAgICBwcm94eSBhZGRyZXNzIGFz
IHByZWNvbmZpZ3VyZWQgaW4gdGhlIGFwcGxpY2F0aW9uIG9yIGNhbiBkeW5hbWljYWxseQ0KICAg
ICAgIGxlYXJuIGFib3V0IGF2YWlsYWJsZSBwcm94eSBzZXJ2aWNlcy4gIFRoaXMgZG9jdW1lbnQg
ZGVzY3JpYmVzDQogICAgICAgZGlmZmVyZW50IGRpc2NvdmVyeSBtZWNoYW5pc21zIGZvciBub24t
dHJhbnNwYXJlbnQgcHJveGllcyB0aGF0IGFyZQ0KICAgICAgIGVpdGhlciBsb2NhdGVkIGluIHRo
ZSBsb2NhbCBuZXR3b3JrLCBlLmcuIGhvbWUgb3IgZW50ZXJwcmlzZSBuZXR3b3JrLA0KICAgICAg
IGluIHRoZSBhY2Nlc3MgbmV0d29yaywgb3Igc29tZXdoZXJlIGVsc2Ugb24gdGhlIEludGVybmV0
IHVzdWFsbHkNCiAgICAgICBjbG9zZSB0byB0aGUgdGFyZ2V0IHNlcnZlciBvciBldmVuIGluIHRo
ZSBzYW1lIG5ldHdvcmsgYXMgdGhlIHRhcmdldA0KICAgICAgIHNlcnZlci4NCiAgICANCiAgICAg
ICBUaGlzIGRvY3VtZW50IGFzc3VtZXMgdGhhdCB0aGUgbm9uLXRyYW5zcGFyZW50IHByb3h5IHNl
cnZlciBpcw0KICAgICAgIGNvbm5lY3RlZCB2aWEgUVVJQyBhbmQgZGlzY3Vzc2VzIHBvdGVudGlh
bCBkaXNjb3ZlcnkgbWVjaGFuaXNtcyBmb3INCiAgICAgICBzdWNoIGEgUVVJQy1iYXNlZCwgbm9u
LXRyYW5zcGFyZW50IHByb3h5Lg0KICAgIA0KICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAN
CiAgICANCiAgICANCiAgICBQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9m
IG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uDQogICAgdW50aWwgdGhlIGh0bWxp
emVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZy4NCiAg
ICANCiAgICBUaGUgSUVURiBTZWNyZXRhcmlhdA0KICAgIA0KICAgIA0KDQo=


From nobody Mon Nov  4 09:06:55 2019
Return-Path: <lucaspardue.24.7@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 54254120AEA; Mon,  4 Nov 2019 09:06:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level: 
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 Ki8kJ88OcL59; Mon,  4 Nov 2019 09:06:43 -0800 (PST)
Received: from mail-ua1-x933.google.com (mail-ua1-x933.google.com [IPv6:2607:f8b0:4864:20::933]) (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 3E641120A8C; Mon,  4 Nov 2019 09:06:43 -0800 (PST)
Received: by mail-ua1-x933.google.com with SMTP id i13so5179136uaq.7; Mon, 04 Nov 2019 09:06:43 -0800 (PST)
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=SAsatSC/qhG5EQOYWY3ilN0zBfpZn90VOXMY9yXe5nA=; b=d81tDx5vvMHHuqRjrzGk987w/oWhg0++u2VRoyKAcWielp3ibICv/bc4Tzdcb7Kata ungkVzE1BvXDpiWeCdErQDi6fqsKiIKFerO2m1xBWqNCfguSu+CHrLosNCykMEIkVTn3 FaMU4vCsyhpvVtKq7sdD/QOw64X1DNO3SIp0hTsqXql44dHpTA/mvPzHxtDcpzxz50AX Yov+VUkVqHRaDIZJBLYkYbyLzGvzyurpXhXx0q2GRLI+MY0DHtM95is92qOQmoUhFupK vTFKVXlrRFoqjiZ6MRSPeEYrp1jzuGivUUMShhswj12E/trY4L2aLKclrw4JWyRC8Q00 TXjA==
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=SAsatSC/qhG5EQOYWY3ilN0zBfpZn90VOXMY9yXe5nA=; b=S6IYKNqcDpSTw6ZO3RY9+jrIZFufc4HDVzXJ0pJKF6ypSP/Ls5zVUx62OvabOArCn5 2b2jTvrieF/fJc/yWo6BHBr0xRQKEyb/9/hn4WgJ/zFdhb+G6d8NXDBzUHpQ3jiSW02p yNd0tiyMwH/jJrIkVXcy71BxVBdRsvmpVHsuKQpkDQXU75AyjQ28Hm8OqWww+cwX/+Nb DzUVR2iFZYBe01HrLWEfZFmpD6uk2Ma1XxV8Bw5RtK3/zmdEnDImWEMyIW9jzuxLVvo9 45ZpMxOvS8PacyQSAjEfwQX1AVaTtgxLuIoMaqdbxTUGWuZ28QbnNqMkfbptLX6fL38a BL9g==
X-Gm-Message-State: APjAAAXEjGp/sak8s5S5E+eAnDQqP4EuFJR8/sL6KiHtAOxXC0yKVBLh zbuBf9D2bdl6vLOOStLN/ksG7vApnXqQ9DnKAWg=
X-Google-Smtp-Source: APXvYqw8SWz1cJEItskzNJtw4N81QJnxbrLJfTMeYO4P2O+S8LHrT1VfnYw35Qv3vFZ4yXhPXRZXVqj/fiy3Ov6M/ZA=
X-Received: by 2002:a9f:28a8:: with SMTP id d37mr10432811uad.102.1572887202140;  Mon, 04 Nov 2019 09:06:42 -0800 (PST)
MIME-Version: 1.0
References: <157288641719.16495.4218503379126128243.idtracker@ietfa.amsl.com> <CA5EB3C0-F510-4883-B50B-51A3E46B47CA@ericsson.com>
In-Reply-To: <CA5EB3C0-F510-4883-B50B-51A3E46B47CA@ericsson.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Mon, 4 Nov 2019 17:06:30 +0000
Message-ID: <CALGR9obp-YARLEXDVWvTqZ_h=Ocbn6m2On+uovK-SL-6TaOSXg@mail.gmail.com>
Subject: Re: [Masque] FW: New Version Notification for draft-kuehlewind-quic-proxy-discovery-00.txt
To: Mirja Kuehlewind <mirja.kuehlewind=40ericsson.com@dmarc.ietf.org>
Cc: "quic@ietf.org" <quic@ietf.org>, "masque@ietf.org" <masque@ietf.org>,  Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Content-Type: multipart/alternative; boundary="000000000000f4969d05968856cd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/jhTxslkIZfz8xDWYcoAueV9Mjng>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 17:06:45 -0000

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

Thanks for sharing this.

I wonder if you considered WPAD (Web Proxy Autodiscovery) or PAC (Proxy
auto-config)? Although targetted at the application layer, it might help to
comment on how those forms of discovery would relate to the methods
outlined in your draft.

Cheers,
Lucas

On Mon, Nov 4, 2019 at 4:58 PM Mirja Kuehlewind <mirja.kuehlewind=3D
40ericsson.com@dmarc.ietf.org> wrote:

> Hi all,
>
> we submitted a new draft that lists discovery mechanisms for QUIC-based
> proxies (see below). This is one piece of work that is needed for most of
> the use cases in draft-kuehlewind-quic-substrate.
>
> Let me know if you have any questions or comments!
>
> Mirja
>
>
> =EF=BB=BFOn 04.11.19, 17:53, "internet-drafts@ietf.org" <internet-drafts@=
ietf.org>
> wrote:
>
>
>     A new version of I-D, draft-kuehlewind-quic-proxy-discovery-00.txt
>     has been successfully submitted by Mirja Kuehlewind and posted to the
>     IETF repository.
>
>     Name:               draft-kuehlewind-quic-proxy-discovery
>     Revision:   00
>     Title:              Discovery Mechanism for QUIC-based,
> Non-transparent Proxy Services
>     Document date:      2019-11-04
>     Group:              Individual Submission
>     Pages:              11
>     URL:
> https://www.ietf.org/internet-drafts/draft-kuehlewind-quic-proxy-discover=
y-00.txt
>     Status:
> https://datatracker.ietf.org/doc/draft-kuehlewind-quic-proxy-discovery/
>     Htmlized:
> https://tools.ietf.org/html/draft-kuehlewind-quic-proxy-discovery-00
>     Htmlized:
> https://datatracker.ietf.org/doc/html/draft-kuehlewind-quic-proxy-discove=
ry
>
>
>     Abstract:
>        Often an intermediate instance (such as a proxy server) is used to
>        connect to a web server or a communicating peer if a direct end-to=
-
>        end IP connectivity is not possible or the proxy can provide a
>        support service like, e.g., address anonymisation.  To use a non-
>        transparent proxy a client explicitly connects to it and requests
>        forwarding to the final target server.  The client either knows th=
e
>        proxy address as preconfigured in the application or can dynamical=
ly
>        learn about available proxy services.  This document describes
>        different discovery mechanisms for non-transparent proxies that ar=
e
>        either located in the local network, e.g. home or enterprise
> network,
>        in the access network, or somewhere else on the Internet usually
>        close to the target server or even in the same network as the targ=
et
>        server.
>
>        This document assumes that the non-transparent proxy server is
>        connected via QUIC and discusses potential discovery mechanisms fo=
r
>        such a QUIC-based, non-transparent proxy.
>
>
>
>
>     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.
>
>     The IETF Secretariat
>
>
>
> --
> Masque mailing list
> Masque@ietf.org
> https://www.ietf.org/mailman/listinfo/masque
>

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

<div dir=3D"ltr"><div>Thanks for sharing this.</div><div><br></div><div>I w=
onder if you considered WPAD (Web Proxy Autodiscovery) or PAC (Proxy auto-c=
onfig)? Although targetted at the application layer, it might help to comme=
nt on how those forms of discovery would relate to the methods outlined in =
your draft.</div><div><br></div><div>Cheers,</div><div>Lucas<br></div></div=
><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mo=
n, Nov 4, 2019 at 4:58 PM Mirja Kuehlewind &lt;mirja.kuehlewind=3D<a href=
=3D"mailto:40ericsson.com@dmarc.ietf.org">40ericsson.com@dmarc.ietf.org</a>=
&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi a=
ll,<br>
<br>
we submitted a new draft that lists discovery mechanisms for QUIC-based pro=
xies (see below). This is one piece of work that is needed for most of the =
use cases in draft-kuehlewind-quic-substrate. <br>
<br>
Let me know if you have any questions or comments!<br>
<br>
Mirja<br>
<br>
<br>
=EF=BB=BFOn 04.11.19, 17:53, &quot;<a href=3D"mailto:internet-drafts@ietf.o=
rg" target=3D"_blank">internet-drafts@ietf.org</a>&quot; &lt;<a href=3D"mai=
lto:internet-drafts@ietf.org" target=3D"_blank">internet-drafts@ietf.org</a=
>&gt; wrote:<br>
<br>
<br>
=C2=A0 =C2=A0 A new version of I-D, draft-kuehlewind-quic-proxy-discovery-0=
0.txt<br>
=C2=A0 =C2=A0 has been successfully submitted by Mirja Kuehlewind and poste=
d to the<br>
=C2=A0 =C2=A0 IETF repository.<br>
<br>
=C2=A0 =C2=A0 Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0d=
raft-kuehlewind-quic-proxy-discovery<br>
=C2=A0 =C2=A0 Revision:=C2=A0 =C2=A000<br>
=C2=A0 =C2=A0 Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Discov=
ery Mechanism for QUIC-based, Non-transparent Proxy Services<br>
=C2=A0 =C2=A0 Document date:=C2=A0 =C2=A0 =C2=A0 2019-11-04<br>
=C2=A0 =C2=A0 Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Indivi=
dual Submission<br>
=C2=A0 =C2=A0 Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 11<br>
=C2=A0 =C2=A0 URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http=
s://www.ietf.org/internet-drafts/draft-kuehlewind-quic-proxy-discovery-00.t=
xt" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.org/internet-draf=
ts/draft-kuehlewind-quic-proxy-discovery-00.txt</a><br>
=C2=A0 =C2=A0 Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://d=
atatracker.ietf.org/doc/draft-kuehlewind-quic-proxy-discovery/" rel=3D"nore=
ferrer" target=3D"_blank">https://datatracker.ietf.org/doc/draft-kuehlewind=
-quic-proxy-discovery/</a><br>
=C2=A0 =C2=A0 Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.=
ietf.org/html/draft-kuehlewind-quic-proxy-discovery-00" rel=3D"noreferrer" =
target=3D"_blank">https://tools.ietf.org/html/draft-kuehlewind-quic-proxy-d=
iscovery-00</a><br>
=C2=A0 =C2=A0 Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatr=
acker.ietf.org/doc/html/draft-kuehlewind-quic-proxy-discovery" rel=3D"noref=
errer" target=3D"_blank">https://datatracker.ietf.org/doc/html/draft-kuehle=
wind-quic-proxy-discovery</a><br>
<br>
<br>
=C2=A0 =C2=A0 Abstract:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0Often an intermediate instance (such as a proxy =
server) is used to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0connect to a web server or a communicating peer =
if a direct end-to-<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0end IP connectivity is not possible or the proxy=
 can provide a<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0support service like, e.g., address anonymisatio=
n.=C2=A0 To use a non-<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0transparent proxy a client explicitly connects t=
o it and requests<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0forwarding to the final target server.=C2=A0 The=
 client either knows the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0proxy address as preconfigured in the applicatio=
n or can dynamically<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0learn about available proxy services.=C2=A0 This=
 document describes<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0different discovery mechanisms for non-transpare=
nt proxies that are<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0either located in the local network, e.g. home o=
r enterprise network,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0in the access network, or somewhere else on the =
Internet usually<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0close to the target server or even in the same n=
etwork as the target<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0server.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0This document assumes that the non-transparent p=
roxy server is<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0connected via QUIC and discusses potential disco=
very mechanisms for<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0such a QUIC-based, non-transparent proxy.<br>
<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 Please note that it may take a couple of minutes from the tim=
e of submission<br>
=C2=A0 =C2=A0 until the htmlized version and diff are available at <a href=
=3D"http://tools.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.=
org</a>.<br>
<br>
=C2=A0 =C2=A0 The IETF Secretariat<br>
<br>
<br>
<br>
-- <br>
Masque mailing list<br>
<a href=3D"mailto:Masque@ietf.org" target=3D"_blank">Masque@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/masque" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/masque</a><br>
</blockquote></div>

--000000000000f4969d05968856cd--


From nobody Mon Nov  4 09:10:00 2019
Return-Path: <mirja.kuehlewind@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 1E6B3120AEA; Mon,  4 Nov 2019 09:09:53 -0800 (PST)
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,  DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_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=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 wlsmShcM_E24; Mon,  4 Nov 2019 09:09:49 -0800 (PST)
Received: from EUR02-VE1-obe.outbound.protection.outlook.com (mail-eopbgr20061.outbound.protection.outlook.com [40.107.2.61]) (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 55723120A7A; Mon,  4 Nov 2019 09:09:49 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=n8rWFpPTDfFqCHh/y7SRKaUpIY4uiEknu90ogjDVNSHc8Wm/VHG2n7KpQAczy+c2UNur/18RcYAo9A3cbPSHHn9EHLABD84c22Scs78tNctX5m3q7URuajdAzTk8d2zhNnA+V5JqppTVDO2hegnaEx3r0l1d1Cgg8iaS3ssvns3lrfJyOObn77uKnaliaXDrmdNyPYNpQ1EW8uqRzuERbUOvjFiskM9MyOty7mS+7CMXrJ1AzcN4fTtIk6GV2BjqdRir1xGa50lsfy28j1BLyg9HYzx95SEac0ee3AdG78VYZqWVShlXJeeoEVMKYDt28R6tYIY1PHMzh2kk3+1JQg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=G7MV32zjACqf9xDP3tO/D3rCB86h/ofpwJrMMPSA8Ak=; b=Tci2zETfNwOfP3ltqDj4liSdNtieqAmVfGt2007oISBifLzflrUGfyUcUFRI/CqMheNgaSAkZyibk6DrD4J9jr8bGk4FPn3IBEUCg4f0tVz569nnvap/rhY1oyfUOAzc0+Tqvnw3QW3+kM0EhzYYtF1bdw8oZ2/EiEEtSLwje0ftt4cgvFujfpTU+bxcfGZls7Ciq5Qh74AUI89T4POVZFiw2m7NRZNJWC7jFWSXIovCYSr/Avo5CFIYozqeGbVCP5Ph5x8IsCkbjOE4txL3HwQ0MxsOinlU5+YvLxqaDMhYFKVTRPLYkP7QkoEXGNXdFSw/QcG3tLc1BkmxS4HDtA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=G7MV32zjACqf9xDP3tO/D3rCB86h/ofpwJrMMPSA8Ak=; b=QZDSdQJA0cfpXOQULzVBO7YjkiBRbc8mCRwQLYqe9/chApECEOcw1wZW9CXTPCseS5I43JBe39/azKbzyQQ6m1ppYY8gOFJKBrszKXTyjQV2wP6ykRUq4Z8GrBfFJkVv9KCKVHl3ATuUgSSpL+wVRocfL+C2gtAhvxZERx9jOHQ=
Received: from AM0PR07MB4691.eurprd07.prod.outlook.com (52.135.149.158) by AM0PR07MB3971.eurprd07.prod.outlook.com (52.134.82.155) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2430.16; Mon, 4 Nov 2019 17:09:47 +0000
Received: from AM0PR07MB4691.eurprd07.prod.outlook.com ([fe80::4189:4ef8:bfc1:ec58]) by AM0PR07MB4691.eurprd07.prod.outlook.com ([fe80::4189:4ef8:bfc1:ec58%7]) with mapi id 15.20.2430.013; Mon, 4 Nov 2019 17:09:46 +0000
From: Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
CC: "quic@ietf.org" <quic@ietf.org>, "masque@ietf.org" <masque@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Subject: Re: [Masque] FW: New Version Notification for draft-kuehlewind-quic-proxy-discovery-00.txt
Thread-Topic: [Masque] FW: New Version Notification for draft-kuehlewind-quic-proxy-discovery-00.txt
Thread-Index: AQHVkzBtXqSCGBS1QEWLK0BXXTrwWKd7THMA///xkwCAABGsgA==
Date: Mon, 4 Nov 2019 17:09:46 +0000
Message-ID: <3F20108D-DEED-4AEF-89D3-55F11058110B@ericsson.com>
References: <157288641719.16495.4218503379126128243.idtracker@ietfa.amsl.com> <CA5EB3C0-F510-4883-B50B-51A3E46B47CA@ericsson.com> <CALGR9obp-YARLEXDVWvTqZ_h=Ocbn6m2On+uovK-SL-6TaOSXg@mail.gmail.com>
In-Reply-To: <CALGR9obp-YARLEXDVWvTqZ_h=Ocbn6m2On+uovK-SL-6TaOSXg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mirja.kuehlewind@ericsson.com; 
x-originating-ip: [2003:eb:4700:cf00:3d57:7e7e:af67:8db2]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 97f73b05-d8c4-4fdd-2076-08d76149cb6d
x-ms-traffictypediagnostic: AM0PR07MB3971:|AM0PR07MB3971:
x-ms-exchange-purlcount: 7
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <AM0PR07MB3971D711D8E4A934B6391D35F47F0@AM0PR07MB3971.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0211965D06
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(366004)(39860400002)(136003)(396003)(346002)(376002)(25584004)(53754006)(189003)(199004)(54094003)(6486002)(2906002)(6306002)(76176011)(15650500001)(2420400007)(6246003)(478600001)(6916009)(102836004)(6436002)(6506007)(53546011)(316002)(66574012)(54906003)(14454004)(71190400001)(71200400001)(229853002)(6512007)(7110500001)(256004)(81166006)(44832011)(486006)(7736002)(966005)(236005)(186003)(25786009)(86362001)(14444005)(11346002)(46003)(606006)(2616005)(107886003)(36756003)(446003)(66476007)(66556008)(476003)(64756008)(76116006)(66446008)(8936002)(66946007)(33656002)(99286004)(54896002)(81156014)(5660300002)(8676002)(6116002)(4326008); DIR:OUT; SFP:1101; SCL:1; SRVR:AM0PR07MB3971; H:AM0PR07MB4691.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: YQ8WkqRc0qqJX+6cD5Y8j7N3z02kvg/JaDail6JqTYBFqxiFfx8Aouu+QKciGDpc0aJNgqtECSR7mVd2b4K1l3wVJnsenFtyClnO47XYgdKZUBE7qd1lcaeF+IunqRUjW9SEVL5dLyTrWBJ+3tYqRJ4LPD7GJ7y18BfkHU3Y9mfsiTifGoPSmYPbT78u5F8AcdJBZZHYEAbJiqH1wItydNrF5ZFrluJiKZqpQoxKnQCetBv9S54pEbk3U+jff1rOrxqhtzZRxnnceMM4Y/xBqoX3KKZbOwiQAXXsGXqxTKNpahIaBlU7A57NEqJF+TqxSj/h1mQUK97gQK4GXB87oLpjUxJlgMp30CbGofUH26D51SNZeuf0c6Eo60JRk7v664+bZg5XwkCMIxBlDMwZD7xtZ4PKXf3+G0Ln251sD6kJ/HGnNaFLp+enaLA9+rR6PkizvmyfVi8Kh5f8YB6QGrihjdmWN0c/iKZbaQsB680=
Content-Type: multipart/alternative; boundary="_000_3F20108DDEED4AEF89D355F11058110Bericssoncom_"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 97f73b05-d8c4-4fdd-2076-08d76149cb6d
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Nov 2019 17:09:46.8898 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: k1RFMZPJ4phz/HTFSBo1BA4td2iZwB4U09b10QJHy7k+7mEVLcBi1Or0jBUDDTQQP3XbRQYw03fputm0Zsp8bl+BwDYT5EC4nPn7pxb4Oc4=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB3971
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/UYLDRr6QJAs1aJPqR2mt1ACwYag>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 17:09:53 -0000

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

SGkgTHVjYXMsDQoNCm5vLCB3ZSBkaWRu4oCZdCBjb25zaWRlciB0aGlzIHlldCBidXQgb25seSBi
ZWNhdXNlIHdlIHdlcmUgbm90IHJlYWxseSBhd2FyZSBvZiB0aGF0LiBEbyB5b3UgaGF2ZSBhIHBv
aW50ZXI/IE9yIHNlbmQgYSBQUiDwn5iKDQoNCmh0dHBzOi8vZ2l0aHViLmNvbS9taXJqYWsvZHJh
ZnQta3VlaGxld2luZC1xdWljLXByb3h5LWRpc2NvdmVyeQ0KDQpNaXJqYQ0KDQoNCkZyb206IEx1
Y2FzIFBhcmR1ZSA8bHVjYXNwYXJkdWUuMjQuN0BnbWFpbC5jb20+DQpEYXRlOiBNb25kYXksIDQu
IE5vdmVtYmVyIDIwMTkgYXQgMTg6MDYNClRvOiBNaXJqYSBLdWVobGV3aW5kIDxtaXJqYS5rdWVo
bGV3aW5kQGVyaWNzc29uLmNvbT4NCkNjOiAicXVpY0BpZXRmLm9yZyIgPHF1aWNAaWV0Zi5vcmc+
LCAibWFzcXVlQGlldGYub3JnIiA8bWFzcXVlQGlldGYub3JnPiwgWmFoZWR1enphbWFuIFNhcmtl
ciA8emFoZWR1enphbWFuLnNhcmtlckBlcmljc3Nvbi5jb20+DQpTdWJqZWN0OiBSZTogW01hc3F1
ZV0gRlc6IE5ldyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQta3VlaGxld2luZC1xdWlj
LXByb3h5LWRpc2NvdmVyeS0wMC50eHQNCg0KVGhhbmtzIGZvciBzaGFyaW5nIHRoaXMuDQoNCkkg
d29uZGVyIGlmIHlvdSBjb25zaWRlcmVkIFdQQUQgKFdlYiBQcm94eSBBdXRvZGlzY292ZXJ5KSBv
ciBQQUMgKFByb3h5IGF1dG8tY29uZmlnKT8gQWx0aG91Z2ggdGFyZ2V0dGVkIGF0IHRoZSBhcHBs
aWNhdGlvbiBsYXllciwgaXQgbWlnaHQgaGVscCB0byBjb21tZW50IG9uIGhvdyB0aG9zZSBmb3Jt
cyBvZiBkaXNjb3Zlcnkgd291bGQgcmVsYXRlIHRvIHRoZSBtZXRob2RzIG91dGxpbmVkIGluIHlv
dXIgZHJhZnQuDQoNCkNoZWVycywNCkx1Y2FzDQoNCk9uIE1vbiwgTm92IDQsIDIwMTkgYXQgNDo1
OCBQTSBNaXJqYSBLdWVobGV3aW5kIDxtaXJqYS5rdWVobGV3aW5kPTQwZXJpY3Nzb24uY29tQGRt
YXJjLmlldGYub3JnPG1haWx0bzo0MGVyaWNzc29uLmNvbUBkbWFyYy5pZXRmLm9yZz4+IHdyb3Rl
Og0KSGkgYWxsLA0KDQp3ZSBzdWJtaXR0ZWQgYSBuZXcgZHJhZnQgdGhhdCBsaXN0cyBkaXNjb3Zl
cnkgbWVjaGFuaXNtcyBmb3IgUVVJQy1iYXNlZCBwcm94aWVzIChzZWUgYmVsb3cpLiBUaGlzIGlz
IG9uZSBwaWVjZSBvZiB3b3JrIHRoYXQgaXMgbmVlZGVkIGZvciBtb3N0IG9mIHRoZSB1c2UgY2Fz
ZXMgaW4gZHJhZnQta3VlaGxld2luZC1xdWljLXN1YnN0cmF0ZS4NCg0KTGV0IG1lIGtub3cgaWYg
eW91IGhhdmUgYW55IHF1ZXN0aW9ucyBvciBjb21tZW50cyENCg0KTWlyamENCg0KDQpPbiAwNC4x
MS4xOSwgMTc6NTMsICJpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmc8bWFpbHRvOmludGVybmV0LWRy
YWZ0c0BpZXRmLm9yZz4iIDxpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmc8bWFpbHRvOmludGVybmV0
LWRyYWZ0c0BpZXRmLm9yZz4+IHdyb3RlOg0KDQoNCiAgICBBIG5ldyB2ZXJzaW9uIG9mIEktRCwg
ZHJhZnQta3VlaGxld2luZC1xdWljLXByb3h5LWRpc2NvdmVyeS0wMC50eHQNCiAgICBoYXMgYmVl
biBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IE1pcmphIEt1ZWhsZXdpbmQgYW5kIHBvc3RlZCB0
byB0aGUNCiAgICBJRVRGIHJlcG9zaXRvcnkuDQoNCiAgICBOYW1lOiAgICAgICAgICAgICAgIGRy
YWZ0LWt1ZWhsZXdpbmQtcXVpYy1wcm94eS1kaXNjb3ZlcnkNCiAgICBSZXZpc2lvbjogICAwMA0K
ICAgIFRpdGxlOiAgICAgICAgICAgICAgRGlzY292ZXJ5IE1lY2hhbmlzbSBmb3IgUVVJQy1iYXNl
ZCwgTm9uLXRyYW5zcGFyZW50IFByb3h5IFNlcnZpY2VzDQogICAgRG9jdW1lbnQgZGF0ZTogICAg
ICAyMDE5LTExLTA0DQogICAgR3JvdXA6ICAgICAgICAgICAgICBJbmRpdmlkdWFsIFN1Ym1pc3Np
b24NCiAgICBQYWdlczogICAgICAgICAgICAgIDExDQogICAgVVJMOiAgICAgICAgICAgIGh0dHBz
Oi8vd3d3LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1rdWVobGV3aW5kLXF1aWMtcHJv
eHktZGlzY292ZXJ5LTAwLnR4dA0KICAgIFN0YXR1czogICAgICAgICBodHRwczovL2RhdGF0cmFj
a2VyLmlldGYub3JnL2RvYy9kcmFmdC1rdWVobGV3aW5kLXF1aWMtcHJveHktZGlzY292ZXJ5Lw0K
ICAgIEh0bWxpemVkOiAgICAgICBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQta3Vl
aGxld2luZC1xdWljLXByb3h5LWRpc2NvdmVyeS0wMA0KICAgIEh0bWxpemVkOiAgICAgICBodHRw
czovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9odG1sL2RyYWZ0LWt1ZWhsZXdpbmQtcXVpYy1w
cm94eS1kaXNjb3ZlcnkNCg0KDQogICAgQWJzdHJhY3Q6DQogICAgICAgT2Z0ZW4gYW4gaW50ZXJt
ZWRpYXRlIGluc3RhbmNlIChzdWNoIGFzIGEgcHJveHkgc2VydmVyKSBpcyB1c2VkIHRvDQogICAg
ICAgY29ubmVjdCB0byBhIHdlYiBzZXJ2ZXIgb3IgYSBjb21tdW5pY2F0aW5nIHBlZXIgaWYgYSBk
aXJlY3QgZW5kLXRvLQ0KICAgICAgIGVuZCBJUCBjb25uZWN0aXZpdHkgaXMgbm90IHBvc3NpYmxl
IG9yIHRoZSBwcm94eSBjYW4gcHJvdmlkZSBhDQogICAgICAgc3VwcG9ydCBzZXJ2aWNlIGxpa2Us
IGUuZy4sIGFkZHJlc3MgYW5vbnltaXNhdGlvbi4gIFRvIHVzZSBhIG5vbi0NCiAgICAgICB0cmFu
c3BhcmVudCBwcm94eSBhIGNsaWVudCBleHBsaWNpdGx5IGNvbm5lY3RzIHRvIGl0IGFuZCByZXF1
ZXN0cw0KICAgICAgIGZvcndhcmRpbmcgdG8gdGhlIGZpbmFsIHRhcmdldCBzZXJ2ZXIuICBUaGUg
Y2xpZW50IGVpdGhlciBrbm93cyB0aGUNCiAgICAgICBwcm94eSBhZGRyZXNzIGFzIHByZWNvbmZp
Z3VyZWQgaW4gdGhlIGFwcGxpY2F0aW9uIG9yIGNhbiBkeW5hbWljYWxseQ0KICAgICAgIGxlYXJu
IGFib3V0IGF2YWlsYWJsZSBwcm94eSBzZXJ2aWNlcy4gIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVz
DQogICAgICAgZGlmZmVyZW50IGRpc2NvdmVyeSBtZWNoYW5pc21zIGZvciBub24tdHJhbnNwYXJl
bnQgcHJveGllcyB0aGF0IGFyZQ0KICAgICAgIGVpdGhlciBsb2NhdGVkIGluIHRoZSBsb2NhbCBu
ZXR3b3JrLCBlLmcuIGhvbWUgb3IgZW50ZXJwcmlzZSBuZXR3b3JrLA0KICAgICAgIGluIHRoZSBh
Y2Nlc3MgbmV0d29yaywgb3Igc29tZXdoZXJlIGVsc2Ugb24gdGhlIEludGVybmV0IHVzdWFsbHkN
CiAgICAgICBjbG9zZSB0byB0aGUgdGFyZ2V0IHNlcnZlciBvciBldmVuIGluIHRoZSBzYW1lIG5l
dHdvcmsgYXMgdGhlIHRhcmdldA0KICAgICAgIHNlcnZlci4NCg0KICAgICAgIFRoaXMgZG9jdW1l
bnQgYXNzdW1lcyB0aGF0IHRoZSBub24tdHJhbnNwYXJlbnQgcHJveHkgc2VydmVyIGlzDQogICAg
ICAgY29ubmVjdGVkIHZpYSBRVUlDIGFuZCBkaXNjdXNzZXMgcG90ZW50aWFsIGRpc2NvdmVyeSBt
ZWNoYW5pc21zIGZvcg0KICAgICAgIHN1Y2ggYSBRVUlDLWJhc2VkLCBub24tdHJhbnNwYXJlbnQg
cHJveHkuDQoNCg0KDQoNCiAgICBQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxl
IG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uDQogICAgdW50aWwgdGhlIGh0
bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZzxo
dHRwOi8vdG9vbHMuaWV0Zi5vcmc+Lg0KDQogICAgVGhlIElFVEYgU2VjcmV0YXJpYXQNCg0KDQoN
Ci0tDQpNYXNxdWUgbWFpbGluZyBsaXN0DQpNYXNxdWVAaWV0Zi5vcmc8bWFpbHRvOk1hc3F1ZUBp
ZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vbWFzcXVlDQo=

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

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2
IDMgMiA0O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToy
IDE1IDUgMiAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3Jt
YWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1i
b3R0b206LjAwMDFwdDsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
IixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnAubXNv
bm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1hbDANCgl7bXNvLXN0eWxlLW5hbWU6
bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowY207
DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGNtOw0KCWZvbnQt
c2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5F
bWFpbFN0eWxlMTgNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJZm9udC1mYW1p
bHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVm
YXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6MTAuMHB0O30N
CkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQgNzkyLjBwdDsNCgltYXJnaW46NzAu
ODVwdCA3MC44NXB0IDIuMGNtIDcwLjg1cHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldv
cmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iREUiIGxpbms9
ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFu
Z3VhZ2U6RU4tVVMiPkhpIEx1Y2FzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6
RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPm5v
LCB3ZSBkaWRu4oCZdCBjb25zaWRlciB0aGlzIHlldCBidXQgb25seSBiZWNhdXNlIHdlIHdlcmUg
bm90IHJlYWxseSBhd2FyZSBvZiB0aGF0LiBEbyB5b3UgaGF2ZSBhIHBvaW50ZXI/IE9yIHNlbmQg
YSBQUg0KPC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7
QXBwbGUgQ29sb3IgRW1vamkmcXVvdDs7bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPiYjMTI4
NTIyOzwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdl
OkVOLVVTIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48YSBocmVmPSJodHRwczov
L2dpdGh1Yi5jb20vbWlyamFrL2RyYWZ0LWt1ZWhsZXdpbmQtcXVpYy1wcm94eS1kaXNjb3Zlcnki
Pmh0dHBzOi8vZ2l0aHViLmNvbS9taXJqYWsvZHJhZnQta3VlaGxld2luZC1xdWljLXByb3h5LWRp
c2NvdmVyeTwvYT48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5NaXJqYTxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0ibXNv
LWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxk
aXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0I1QzRERiAxLjBwdDtwYWRk
aW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJn
aW4tbGVmdDozNi4wcHQiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTIuMHB0O2NvbG9yOmJs
YWNrIj5Gcm9tOg0KPC9zcGFuPjwvYj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEyLjBwdDtjb2xv
cjpibGFjayI+THVjYXMgUGFyZHVlICZsdDtsdWNhc3BhcmR1ZS4yNC43QGdtYWlsLmNvbSZndDs8
YnI+DQo8Yj5EYXRlOiA8L2I+TW9uZGF5LCA0LiBOb3ZlbWJlciAyMDE5IGF0IDE4OjA2PGJyPg0K
PGI+VG86IDwvYj5NaXJqYSBLdWVobGV3aW5kICZsdDttaXJqYS5rdWVobGV3aW5kQGVyaWNzc29u
LmNvbSZndDs8YnI+DQo8Yj5DYzogPC9iPiZxdW90O3F1aWNAaWV0Zi5vcmcmcXVvdDsgJmx0O3F1
aWNAaWV0Zi5vcmcmZ3Q7LCAmcXVvdDttYXNxdWVAaWV0Zi5vcmcmcXVvdDsgJmx0O21hc3F1ZUBp
ZXRmLm9yZyZndDssIFphaGVkdXp6YW1hbiBTYXJrZXIgJmx0O3phaGVkdXp6YW1hbi5zYXJrZXJA
ZXJpY3Nzb24uY29tJmd0Ozxicj4NCjxiPlN1YmplY3Q6IDwvYj5SZTogW01hc3F1ZV0gRlc6IE5l
dyBWZXJzaW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQta3VlaGxld2luZC1xdWljLXByb3h5LWRp
c2NvdmVyeS0wMC50eHQ8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij48bzpwPiZuYnNwOzwv
bzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij5UaGFua3MgZm9yIHNoYXJpbmcgdGhpcy48bzpwPjwvbzpw
PjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4t
bGVmdDozNi4wcHQiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjM2LjBwdCI+SSB3b25kZXIgaWYgeW91
IGNvbnNpZGVyZWQgV1BBRCAoV2ViIFByb3h5IEF1dG9kaXNjb3ZlcnkpIG9yIFBBQyAoUHJveHkg
YXV0by1jb25maWcpPyBBbHRob3VnaCB0YXJnZXR0ZWQgYXQgdGhlIGFwcGxpY2F0aW9uIGxheWVy
LCBpdCBtaWdodCBoZWxwIHRvIGNvbW1lbnQgb24gaG93IHRob3NlIGZvcm1zIG9mIGRpc2NvdmVy
eSB3b3VsZCByZWxhdGUgdG8gdGhlIG1ldGhvZHMNCiBvdXRsaW5lZCBpbiB5b3VyIGRyYWZ0Ljxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1hcmdpbi1sZWZ0OjM2LjBwdCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij5DaGVlcnMs
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij5MdWNhczxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tbGVmdDozNi4wcHQiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij5PbiBNb24sIE5vdiA0LCAyMDE5IGF0IDQ6NTggUE0gTWly
amEgS3VlaGxld2luZCAmbHQ7bWlyamEua3VlaGxld2luZD08YSBocmVmPSJtYWlsdG86NDBlcmlj
c3Nvbi5jb21AZG1hcmMuaWV0Zi5vcmciPjQwZXJpY3Nzb24uY29tQGRtYXJjLmlldGYub3JnPC9h
PiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJi
b3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGNtIDBj
bSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MzYuMHB0Ij5IaSBhbGwsPGJyPg0KPGJy
Pg0Kd2Ugc3VibWl0dGVkIGEgbmV3IGRyYWZ0IHRoYXQgbGlzdHMgZGlzY292ZXJ5IG1lY2hhbmlz
bXMgZm9yIFFVSUMtYmFzZWQgcHJveGllcyAoc2VlIGJlbG93KS4gVGhpcyBpcyBvbmUgcGllY2Ug
b2Ygd29yayB0aGF0IGlzIG5lZWRlZCBmb3IgbW9zdCBvZiB0aGUgdXNlIGNhc2VzIGluIGRyYWZ0
LWt1ZWhsZXdpbmQtcXVpYy1zdWJzdHJhdGUuDQo8YnI+DQo8YnI+DQpMZXQgbWUga25vdyBpZiB5
b3UgaGF2ZSBhbnkgcXVlc3Rpb25zIG9yIGNvbW1lbnRzITxicj4NCjxicj4NCk1pcmphPGJyPg0K
PGJyPg0KPGJyPg0KT24gMDQuMTEuMTksIDE3OjUzLCAmcXVvdDs8YSBocmVmPSJtYWlsdG86aW50
ZXJuZXQtZHJhZnRzQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+aW50ZXJuZXQtZHJhZnRzQGll
dGYub3JnPC9hPiZxdW90OyAmbHQ7PGEgaHJlZj0ibWFpbHRvOmludGVybmV0LWRyYWZ0c0BpZXRm
Lm9yZyIgdGFyZ2V0PSJfYmxhbmsiPmludGVybmV0LWRyYWZ0c0BpZXRmLm9yZzwvYT4mZ3Q7IHdy
b3RlOjxicj4NCjxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgQSBuZXcgdmVyc2lvbiBvZiBJLUQs
IGRyYWZ0LWt1ZWhsZXdpbmQtcXVpYy1wcm94eS1kaXNjb3ZlcnktMDAudHh0PGJyPg0KJm5ic3A7
ICZuYnNwOyBoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IE1pcmphIEt1ZWhsZXdp
bmQgYW5kIHBvc3RlZCB0byB0aGU8YnI+DQombmJzcDsgJm5ic3A7IElFVEYgcmVwb3NpdG9yeS48
YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7IE5hbWU6Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO2RyYWZ0LWt1ZWhsZXdpbmQtcXVpYy1wcm94eS1k
aXNjb3Zlcnk8YnI+DQombmJzcDsgJm5ic3A7IFJldmlzaW9uOiZuYnNwOyAmbmJzcDswMDxicj4N
CiZuYnNwOyAmbmJzcDsgVGl0bGU6Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7IERpc2NvdmVyeSBNZWNoYW5pc20gZm9yIFFVSUMtYmFzZWQsIE5vbi10cmFu
c3BhcmVudCBQcm94eSBTZXJ2aWNlczxicj4NCiZuYnNwOyAmbmJzcDsgRG9jdW1lbnQgZGF0ZTom
bmJzcDsgJm5ic3A7ICZuYnNwOyAyMDE5LTExLTA0PGJyPg0KJm5ic3A7ICZuYnNwOyBHcm91cDom
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgSW5kaXZpZHVh
bCBTdWJtaXNzaW9uPGJyPg0KJm5ic3A7ICZuYnNwOyBQYWdlczombmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgMTE8YnI+DQombmJzcDsgJm5ic3A7IFVSTDom
bmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyA8YSBocmVmPSJodHRwczov
L3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQta3VlaGxld2luZC1xdWljLXByb3h5
LWRpc2NvdmVyeS0wMC50eHQiIHRhcmdldD0iX2JsYW5rIj4NCmh0dHBzOi8vd3d3LmlldGYub3Jn
L2ludGVybmV0LWRyYWZ0cy9kcmFmdC1rdWVobGV3aW5kLXF1aWMtcHJveHktZGlzY292ZXJ5LTAw
LnR4dDwvYT48YnI+DQombmJzcDsgJm5ic3A7IFN0YXR1czombmJzcDsgJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7PGEgaHJlZj0iaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJh
ZnQta3VlaGxld2luZC1xdWljLXByb3h5LWRpc2NvdmVyeS8iIHRhcmdldD0iX2JsYW5rIj5odHRw
czovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1rdWVobGV3aW5kLXF1aWMtcHJveHkt
ZGlzY292ZXJ5LzwvYT48YnI+DQombmJzcDsgJm5ic3A7IEh0bWxpemVkOiZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOzxhIGhyZWY9Imh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1r
dWVobGV3aW5kLXF1aWMtcHJveHktZGlzY292ZXJ5LTAwIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6
Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWt1ZWhsZXdpbmQtcXVpYy1wcm94eS1kaXNjb3Zl
cnktMDA8L2E+PGJyPg0KJm5ic3A7ICZuYnNwOyBIdG1saXplZDombmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDs8YSBocmVmPSJodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9odG1sL2Ry
YWZ0LWt1ZWhsZXdpbmQtcXVpYy1wcm94eS1kaXNjb3ZlcnkiIHRhcmdldD0iX2JsYW5rIj5odHRw
czovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9odG1sL2RyYWZ0LWt1ZWhsZXdpbmQtcXVpYy1w
cm94eS1kaXNjb3Zlcnk8L2E+PGJyPg0KPGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyBBYnN0cmFj
dDo8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtPZnRlbiBhbiBpbnRlcm1lZGlhdGUg
aW5zdGFuY2UgKHN1Y2ggYXMgYSBwcm94eSBzZXJ2ZXIpIGlzIHVzZWQgdG88YnI+DQombmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDtjb25uZWN0IHRvIGEgd2ViIHNlcnZlciBvciBhIGNvbW11bmlj
YXRpbmcgcGVlciBpZiBhIGRpcmVjdCBlbmQtdG8tPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ZW5kIElQIGNvbm5lY3Rpdml0eSBpcyBub3QgcG9zc2libGUgb3IgdGhlIHByb3h5IGNh
biBwcm92aWRlIGE8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtzdXBwb3J0IHNlcnZp
Y2UgbGlrZSwgZS5nLiwgYWRkcmVzcyBhbm9ueW1pc2F0aW9uLiZuYnNwOyBUbyB1c2UgYSBub24t
PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7dHJhbnNwYXJlbnQgcHJveHkgYSBjbGll
bnQgZXhwbGljaXRseSBjb25uZWN0cyB0byBpdCBhbmQgcmVxdWVzdHM8YnI+DQombmJzcDsgJm5i
c3A7ICZuYnNwOyAmbmJzcDtmb3J3YXJkaW5nIHRvIHRoZSBmaW5hbCB0YXJnZXQgc2VydmVyLiZu
YnNwOyBUaGUgY2xpZW50IGVpdGhlciBrbm93cyB0aGU8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDtwcm94eSBhZGRyZXNzIGFzIHByZWNvbmZpZ3VyZWQgaW4gdGhlIGFwcGxpY2F0aW9u
IG9yIGNhbiBkeW5hbWljYWxseTxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO2xlYXJu
IGFib3V0IGF2YWlsYWJsZSBwcm94eSBzZXJ2aWNlcy4mbmJzcDsgVGhpcyBkb2N1bWVudCBkZXNj
cmliZXM8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtkaWZmZXJlbnQgZGlzY292ZXJ5
IG1lY2hhbmlzbXMgZm9yIG5vbi10cmFuc3BhcmVudCBwcm94aWVzIHRoYXQgYXJlPGJyPg0KJm5i
c3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ZWl0aGVyIGxvY2F0ZWQgaW4gdGhlIGxvY2FsIG5ldHdv
cmssIGUuZy4gaG9tZSBvciBlbnRlcnByaXNlIG5ldHdvcmssPGJyPg0KJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7aW4gdGhlIGFjY2VzcyBuZXR3b3JrLCBvciBzb21ld2hlcmUgZWxzZSBvbiB0
aGUgSW50ZXJuZXQgdXN1YWxseTxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO2Nsb3Nl
IHRvIHRoZSB0YXJnZXQgc2VydmVyIG9yIGV2ZW4gaW4gdGhlIHNhbWUgbmV0d29yayBhcyB0aGUg
dGFyZ2V0PGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7c2VydmVyLjxicj4NCjxicj4N
CiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO1RoaXMgZG9jdW1lbnQgYXNzdW1lcyB0aGF0IHRo
ZSBub24tdHJhbnNwYXJlbnQgcHJveHkgc2VydmVyIGlzPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7Y29ubmVjdGVkIHZpYSBRVUlDIGFuZCBkaXNjdXNzZXMgcG90ZW50aWFsIGRpc2Nv
dmVyeSBtZWNoYW5pc21zIGZvcjxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO3N1Y2gg
YSBRVUlDLWJhc2VkLCBub24tdHJhbnNwYXJlbnQgcHJveHkuPGJyPg0KPGJyPg0KPGJyPg0KPGJy
Pg0KPGJyPg0KJm5ic3A7ICZuYnNwOyBQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291
cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uPGJyPg0KJm5ic3A7ICZu
YnNwOyB1bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0
IDxhIGhyZWY9Imh0dHA6Ly90b29scy5pZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPg0KdG9vbHMu
aWV0Zi5vcmc8L2E+Ljxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgVGhlIElFVEYgU2VjcmV0YXJp
YXQ8YnI+DQo8YnI+DQo8YnI+DQo8YnI+DQotLSA8YnI+DQpNYXNxdWUgbWFpbGluZyBsaXN0PGJy
Pg0KPGEgaHJlZj0ibWFpbHRvOk1hc3F1ZUBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPk1hc3F1
ZUBpZXRmLm9yZzwvYT48YnI+DQo8YSBocmVmPSJodHRwczovL3d3dy5pZXRmLm9yZy9tYWlsbWFu
L2xpc3RpbmZvL21hc3F1ZSIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vd3d3LmlldGYub3JnL21h
aWxtYW4vbGlzdGluZm8vbWFzcXVlPC9hPjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0K
PC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_3F20108DDEED4AEF89D355F11058110Bericssoncom_--


From nobody Mon Nov  4 09:16:01 2019
Return-Path: <lucaspardue.24.7@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 A4FBA120824; Mon,  4 Nov 2019 09:15:52 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.747
X-Spam-Level: 
X-Spam-Status: No, score=-1.747 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 Z6qPNpLgVBpj; Mon,  4 Nov 2019 09:15:49 -0800 (PST)
Received: from mail-ua1-x931.google.com (mail-ua1-x931.google.com [IPv6:2607:f8b0:4864:20::931]) (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 B62BE120AF4; Mon,  4 Nov 2019 09:15:49 -0800 (PST)
Received: by mail-ua1-x931.google.com with SMTP id k11so2536320ual.10; Mon, 04 Nov 2019 09:15:49 -0800 (PST)
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=8hczRM5IfxYUI9AixS7XXZ7Wlm3oCBTuXjDHST8y2zI=; b=ejSLxNSroR7+YaglkntTY1hVMewXxWxlzOWgC9hvwqTGaPDbK51YpcfixDWRaj151D G2OmUCzf82yRUXxNkBjxC7lkEbcHyup2QfYsLTBNGVZsqSLx9JUntON+yX7ZaHYrsWUf f+SBp/9TqHSyzraiW0b4QJvo8Zyy5zq+mCNs0gXkE0eEmhFnam2cJCvD0ZevtESxwG42 NOqwDgDDNfi4hNybHHSUXuCRmUFzIdW6PeSJjvXHqQ8Kvu5H1jLpUN1nDmlEsqAJ5AIT pKs5HF51cIJ9DSOXbq1u9Bxm/LMekzH2fMQ3HYc4CWDfpliTgiYDCDz7SansLsFoIH5d aUew==
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=8hczRM5IfxYUI9AixS7XXZ7Wlm3oCBTuXjDHST8y2zI=; b=jefW4IzisvKDtiFPHFaqSX9SguMcXC9/dHXs5io+KYBWhaOQFBN/lCmQJAw3D11kYm BrCCKTyDhsmD4nHdYCVisxaOcFYb77jHnXnsz3+C8Cs2GdcUkjcVZxAu/WXbPiYdJ69d ED6JNmXlFCn9T+sGLwOplQubT6W+Kz9Q/9ZvywfgIK5c52f9mAMNbawpcjJP+Ixo8Fak yL8bBrIxygoa2El65mfP0fBbI6snLvev4k6Pc1GQ5rRcRIfHVhzSa/LzafqrSXfB3ICf fa/W1lEoUi8wDETnjE2T12Yhfq/rtCBg2eDLCTbSRlcXZNQ4GExj+1nNvykbKOtVmkHa snAg==
X-Gm-Message-State: APjAAAVTSQgmNTy1A+TP2JWCmamvu8FH2S5DV/csJKGgrWlDDgSe+6Hx GC7N/mW9wr0GxPz4nFY6exHfKmJTSkuRIHwNbvM=
X-Google-Smtp-Source: APXvYqwnFCEBM9l87u4JbivnKaqdOFp4HxFi+HnPJwzi5qr7vAGkkdd6k74lKHQy9flEKvfSRVSt4LN18fp4ZMGzeBE=
X-Received: by 2002:a9f:2304:: with SMTP id 4mr12812543uae.69.1572887748569; Mon, 04 Nov 2019 09:15:48 -0800 (PST)
MIME-Version: 1.0
References: <157288641719.16495.4218503379126128243.idtracker@ietfa.amsl.com> <CA5EB3C0-F510-4883-B50B-51A3E46B47CA@ericsson.com> <CALGR9obp-YARLEXDVWvTqZ_h=Ocbn6m2On+uovK-SL-6TaOSXg@mail.gmail.com> <3F20108D-DEED-4AEF-89D3-55F11058110B@ericsson.com>
In-Reply-To: <3F20108D-DEED-4AEF-89D3-55F11058110B@ericsson.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Mon, 4 Nov 2019 17:15:37 +0000
Message-ID: <CALGR9oYHce0mnkj5Kz13EoR-zN3-xSr0igkJF2Z_dJ2vgfVNSQ@mail.gmail.com>
Subject: Re: [Masque] FW: New Version Notification for draft-kuehlewind-quic-proxy-discovery-00.txt
To: Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>
Cc: "quic@ietf.org" <quic@ietf.org>, "masque@ietf.org" <masque@ietf.org>,  Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
Content-Type: multipart/alternative; boundary="000000000000866f3d05968877bb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/uRcTrVVudgRvrW4ESOjr0CKoMSM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 17:15:53 -0000

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

I'm not an expert in either WPAD [1] or PAC [2], but I am an expert in
feeling their pain as a user on Windows. Part of their pain comes from lack
of formal standardization, resulting in some word-of-mouth approaches to
problem solving, especially how they work (or don't) with the standardised
approaches such as DHCP.

In looking this up, I did discover draft-ietf-wrec-wpad-01, a > 20 I-D for
WPAD [3], wow!

[1] - https://en.wikipedia.org/wiki/Web_Proxy_Auto-Discovery_Protocol
[2] - https://en.wikipedia.org/wiki/Proxy_auto-config
[3] - https://tools.ietf.org/html/draft-ietf-wrec-wpad-01

On Mon, Nov 4, 2019 at 5:09 PM Mirja Kuehlewind <
mirja.kuehlewind@ericsson.com> wrote:

> Hi Lucas,
>
>
>
> no, we didn=E2=80=99t consider this yet but only because we were not real=
ly aware
> of that. Do you have a pointer? Or send a PR =F0=9F=98=8A
>
>
>
> https://github.com/mirjak/draft-kuehlewind-quic-proxy-discovery
>
>
>
> Mirja
>
>
>
>
>
> *From: *Lucas Pardue <lucaspardue.24.7@gmail.com>
> *Date: *Monday, 4. November 2019 at 18:06
> *To: *Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>
> *Cc: *"quic@ietf.org" <quic@ietf.org>, "masque@ietf.org" <masque@ietf.org=
>,
> Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
> *Subject: *Re: [Masque] FW: New Version Notification for
> draft-kuehlewind-quic-proxy-discovery-00.txt
>
>
>
> Thanks for sharing this.
>
>
>
> I wonder if you considered WPAD (Web Proxy Autodiscovery) or PAC (Proxy
> auto-config)? Although targetted at the application layer, it might help =
to
> comment on how those forms of discovery would relate to the methods
> outlined in your draft.
>
>
>
> Cheers,
>
> Lucas
>
>
>
> On Mon, Nov 4, 2019 at 4:58 PM Mirja Kuehlewind <mirja.kuehlewind=3D
> 40ericsson.com@dmarc.ietf.org> wrote:
>
> Hi all,
>
> we submitted a new draft that lists discovery mechanisms for QUIC-based
> proxies (see below). This is one piece of work that is needed for most of
> the use cases in draft-kuehlewind-quic-substrate.
>
> Let me know if you have any questions or comments!
>
> Mirja
>
>
> On 04.11.19, 17:53, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
> wrote:
>
>
>     A new version of I-D, draft-kuehlewind-quic-proxy-discovery-00.txt
>     has been successfully submitted by Mirja Kuehlewind and posted to the
>     IETF repository.
>
>     Name:               draft-kuehlewind-quic-proxy-discovery
>     Revision:   00
>     Title:              Discovery Mechanism for QUIC-based,
> Non-transparent Proxy Services
>     Document date:      2019-11-04
>     Group:              Individual Submission
>     Pages:              11
>     URL:
> https://www.ietf.org/internet-drafts/draft-kuehlewind-quic-proxy-discover=
y-00.txt
>     Status:
> https://datatracker.ietf.org/doc/draft-kuehlewind-quic-proxy-discovery/
>     Htmlized:
> https://tools.ietf.org/html/draft-kuehlewind-quic-proxy-discovery-00
>     Htmlized:
> https://datatracker.ietf.org/doc/html/draft-kuehlewind-quic-proxy-discove=
ry
>
>
>     Abstract:
>        Often an intermediate instance (such as a proxy server) is used to
>        connect to a web server or a communicating peer if a direct end-to=
-
>        end IP connectivity is not possible or the proxy can provide a
>        support service like, e.g., address anonymisation.  To use a non-
>        transparent proxy a client explicitly connects to it and requests
>        forwarding to the final target server.  The client either knows th=
e
>        proxy address as preconfigured in the application or can dynamical=
ly
>        learn about available proxy services.  This document describes
>        different discovery mechanisms for non-transparent proxies that ar=
e
>        either located in the local network, e.g. home or enterprise
> network,
>        in the access network, or somewhere else on the Internet usually
>        close to the target server or even in the same network as the targ=
et
>        server.
>
>        This document assumes that the non-transparent proxy server is
>        connected via QUIC and discusses potential discovery mechanisms fo=
r
>        such a QUIC-based, non-transparent proxy.
>
>
>
>
>     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.
>
>     The IETF Secretariat
>
>
>
> --
> Masque mailing list
> Masque@ietf.org
> https://www.ietf.org/mailman/listinfo/masque
>
>

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

<div dir=3D"ltr"><div>I&#39;m not an expert in either WPAD [1] or PAC [2], =
but I am an expert in feeling their pain as a user on Windows. Part of thei=
r pain comes from lack of formal standardization, resulting in some word-of=
-mouth approaches to problem solving, especially how they work (or don&#39;=
t) with the standardised approaches such as DHCP.</div><div><br></div><div>=
In looking this up, I did discover draft-ietf-wrec-wpad-01, a &gt; 20 I-D f=
or WPAD [3], wow!<br></div><div><br></div><div>[1] - <a href=3D"https://en.=
wikipedia.org/wiki/Web_Proxy_Auto-Discovery_Protocol">https://en.wikipedia.=
org/wiki/Web_Proxy_Auto-Discovery_Protocol</a></div><div>[2] - <a href=3D"h=
ttps://en.wikipedia.org/wiki/Proxy_auto-config">https://en.wikipedia.org/wi=
ki/Proxy_auto-config</a></div><div>[3] - <a href=3D"https://tools.ietf.org/=
html/draft-ietf-wrec-wpad-01">https://tools.ietf.org/html/draft-ietf-wrec-w=
pad-01</a></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Mon, Nov 4, 2019 at 5:09 PM Mirja Kuehlewind &lt;<a href=
=3D"mailto:mirja.kuehlewind@ericsson.com">mirja.kuehlewind@ericsson.com</a>=
&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"DE">
<div class=3D"gmail-m_-6694524503981748293WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi Lucas,<u></u><u></u></span><=
/p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">no, we didn=E2=80=99t consider =
this yet but only because we were not really aware of that. Do you have a p=
ointer? Or send a PR
</span><span style=3D"font-family:&quot;Apple Color Emoji&quot;" lang=3D"EN=
-US">=F0=9F=98=8A</span><span lang=3D"EN-US"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><a href=3D"https://github.com/m=
irjak/draft-kuehlewind-quic-proxy-discovery" target=3D"_blank">https://gith=
ub.com/mirjak/draft-kuehlewind-quic-proxy-discovery</a><u></u><u></u></span=
></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Mirja<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<div style=3D"border-color:rgb(181,196,223) currentcolor currentcolor;borde=
r-style:solid none none;border-width:1pt medium medium;padding:3pt 0cm 0cm"=
>
<p class=3D"MsoNormal" style=3D"margin-left:36pt"><b><span style=3D"font-si=
ze:12pt;color:black">From:
</span></b><span style=3D"font-size:12pt;color:black">Lucas Pardue &lt;<a h=
ref=3D"mailto:lucaspardue.24.7@gmail.com" target=3D"_blank">lucaspardue.24.=
7@gmail.com</a>&gt;<br>
<b>Date: </b>Monday, 4. November 2019 at 18:06<br>
<b>To: </b>Mirja Kuehlewind &lt;<a href=3D"mailto:mirja.kuehlewind@ericsson=
.com" target=3D"_blank">mirja.kuehlewind@ericsson.com</a>&gt;<br>
<b>Cc: </b>&quot;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic@ie=
tf.org</a>&quot; &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">qui=
c@ietf.org</a>&gt;, &quot;<a href=3D"mailto:masque@ietf.org" target=3D"_bla=
nk">masque@ietf.org</a>&quot; &lt;<a href=3D"mailto:masque@ietf.org" target=
=3D"_blank">masque@ietf.org</a>&gt;, Zaheduzzaman Sarker &lt;<a href=3D"mai=
lto:zaheduzzaman.sarker@ericsson.com" target=3D"_blank">zaheduzzaman.sarker=
@ericsson.com</a>&gt;<br>
<b>Subject: </b>Re: [Masque] FW: New Version Notification for draft-kuehlew=
ind-quic-proxy-discovery-00.txt<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt"><u></u>=C2=A0<u></u></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">Thanks for sharing this.<=
u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">I wonder if you considere=
d WPAD (Web Proxy Autodiscovery) or PAC (Proxy auto-config)? Although targe=
tted at the application layer, it might help to comment on how those forms =
of discovery would relate to the methods
 outlined in your draft.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">Cheers,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">Lucas<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:36pt">On Mon, Nov 4, 2019 at 4:=
58 PM Mirja Kuehlewind &lt;mirja.kuehlewind=3D<a href=3D"mailto:40ericsson.=
com@dmarc.ietf.org" target=3D"_blank">40ericsson.com@dmarc.ietf.org</a>&gt;=
 wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-color:currentcolor currentcolor currentcolor rg=
b(204,204,204);border-style:none none none solid;border-width:medium medium=
 medium 1pt;padding:0cm 0cm 0cm 6pt;margin-left:4.8pt;margin-right:0cm">
<p class=3D"MsoNormal" style=3D"margin-left:36pt">Hi all,<br>
<br>
we submitted a new draft that lists discovery mechanisms for QUIC-based pro=
xies (see below). This is one piece of work that is needed for most of the =
use cases in draft-kuehlewind-quic-substrate.
<br>
<br>
Let me know if you have any questions or comments!<br>
<br>
Mirja<br>
<br>
<br>
On 04.11.19, 17:53, &quot;<a href=3D"mailto:internet-drafts@ietf.org" targe=
t=3D"_blank">internet-drafts@ietf.org</a>&quot; &lt;<a href=3D"mailto:inter=
net-drafts@ietf.org" target=3D"_blank">internet-drafts@ietf.org</a>&gt; wro=
te:<br>
<br>
<br>
=C2=A0 =C2=A0 A new version of I-D, draft-kuehlewind-quic-proxy-discovery-0=
0.txt<br>
=C2=A0 =C2=A0 has been successfully submitted by Mirja Kuehlewind and poste=
d to the<br>
=C2=A0 =C2=A0 IETF repository.<br>
<br>
=C2=A0 =C2=A0 Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0d=
raft-kuehlewind-quic-proxy-discovery<br>
=C2=A0 =C2=A0 Revision:=C2=A0 =C2=A000<br>
=C2=A0 =C2=A0 Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Discov=
ery Mechanism for QUIC-based, Non-transparent Proxy Services<br>
=C2=A0 =C2=A0 Document date:=C2=A0 =C2=A0 =C2=A0 2019-11-04<br>
=C2=A0 =C2=A0 Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Indivi=
dual Submission<br>
=C2=A0 =C2=A0 Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 11<br>
=C2=A0 =C2=A0 URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http=
s://www.ietf.org/internet-drafts/draft-kuehlewind-quic-proxy-discovery-00.t=
xt" target=3D"_blank">
https://www.ietf.org/internet-drafts/draft-kuehlewind-quic-proxy-discovery-=
00.txt</a><br>
=C2=A0 =C2=A0 Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://d=
atatracker.ietf.org/doc/draft-kuehlewind-quic-proxy-discovery/" target=3D"_=
blank">https://datatracker.ietf.org/doc/draft-kuehlewind-quic-proxy-discove=
ry/</a><br>
=C2=A0 =C2=A0 Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.=
ietf.org/html/draft-kuehlewind-quic-proxy-discovery-00" target=3D"_blank">h=
ttps://tools.ietf.org/html/draft-kuehlewind-quic-proxy-discovery-00</a><br>
=C2=A0 =C2=A0 Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatr=
acker.ietf.org/doc/html/draft-kuehlewind-quic-proxy-discovery" target=3D"_b=
lank">https://datatracker.ietf.org/doc/html/draft-kuehlewind-quic-proxy-dis=
covery</a><br>
<br>
<br>
=C2=A0 =C2=A0 Abstract:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0Often an intermediate instance (such as a proxy =
server) is used to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0connect to a web server or a communicating peer =
if a direct end-to-<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0end IP connectivity is not possible or the proxy=
 can provide a<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0support service like, e.g., address anonymisatio=
n.=C2=A0 To use a non-<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0transparent proxy a client explicitly connects t=
o it and requests<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0forwarding to the final target server.=C2=A0 The=
 client either knows the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0proxy address as preconfigured in the applicatio=
n or can dynamically<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0learn about available proxy services.=C2=A0 This=
 document describes<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0different discovery mechanisms for non-transpare=
nt proxies that are<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0either located in the local network, e.g. home o=
r enterprise network,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0in the access network, or somewhere else on the =
Internet usually<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0close to the target server or even in the same n=
etwork as the target<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0server.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0This document assumes that the non-transparent p=
roxy server is<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0connected via QUIC and discusses potential disco=
very mechanisms for<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0such a QUIC-based, non-transparent proxy.<br>
<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 Please note that it may take a couple of minutes from the tim=
e of submission<br>
=C2=A0 =C2=A0 until the htmlized version and diff are available at <a href=
=3D"http://tools.ietf.org" target=3D"_blank">
tools.ietf.org</a>.<br>
<br>
=C2=A0 =C2=A0 The IETF Secretariat<br>
<br>
<br>
<br>
-- <br>
Masque mailing list<br>
<a href=3D"mailto:Masque@ietf.org" target=3D"_blank">Masque@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/masque" target=3D"_blank">=
https://www.ietf.org/mailman/listinfo/masque</a><u></u><u></u></p>
</blockquote>
</div>
</div>
</div>

</blockquote></div>

--000000000000866f3d05968877bb--


From nobody Mon Nov  4 12:29:58 2019
Return-Path: <dschinazi.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 E94EA120288 for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 12:29:56 -0800 (PST)
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_HELO_NONE=0.001, 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 zl4V7HX_DdfM for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 12:29:55 -0800 (PST)
Received: from mail-lf1-x12e.google.com (mail-lf1-x12e.google.com [IPv6:2a00:1450:4864:20::12e]) (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 EC50E120219 for <quic@ietf.org>; Mon,  4 Nov 2019 12:29:54 -0800 (PST)
Received: by mail-lf1-x12e.google.com with SMTP id y127so13277004lfc.0 for <quic@ietf.org>; Mon, 04 Nov 2019 12:29:54 -0800 (PST)
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=dy+WollR7c1RToNZQTaGfY7HMSzons9LiO0E/TM/+o8=; b=EgXBbHdR0rrK87Pvm4Ts+FDHAbUqBKrIsdjHhuDsOmb177VKbRgew7EuPJ7qYPihwi HfPGfe+vR3kMEKQsHB962480p2mxfKJJ2xsKCVqJjDQ2EiGlIBPbrB+g+qMeaQGWheum Jm6LJFKkrkwkFwj4TUqLF1edJllGQasC1t1toqUEolzD4Xxl2lgtRYN2ggmpaJJzRmVF 6VMeNM3pHFsMf6D5dKvvFfYHzYD5q3u5v0tl4dbe7hrxDlxOFJyP+KUmippHYRbxBBBf OHESBu57zQ47ELYYtOBQuf7+N4SjqVB9/JsKBRPQTJULkcQ7qymxzP/N4thIuaH5A4Wv IhHQ==
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=dy+WollR7c1RToNZQTaGfY7HMSzons9LiO0E/TM/+o8=; b=b8v7oRDSyopUJEVXAkZvS8qYOUhBB+8T5EIEWduWzt6tHsehJr1w7nWErrrpPvcR1h zLYWLf6nUtaCIkQyVtotY8U1xvG+ijvL6POvEub3n5mahOv/DGlA4pOyXzE0KhjEipro FU5NBjz2AgZpQ5xyQHZiEG7Ex+ZeE1a9z+s3ZRMtAoMpKlUMPIArCD3zvSlpS89vVI/g VBkXIOlh3jYVUVixa9/6tIjQ2Mtpw7mJPreOuMrNTS2u4QMMpftnopPrV8ZdRXgC871Q D5qYgj4eb5XHyGJfS6krRmgLL9cmqRFmafVxod8YQYYdOX90iiVHcAqdxj0ro5LKV/4K Jlsg==
X-Gm-Message-State: APjAAAW+MYAYX2O98jvd1/gTdFc+tcoUTX+N0u6N/g4XLxX1yj3LypCt Oxb2dDazSdPhaVsSH76m/MvSkrDcO2nyqWNJ70OkascF
X-Google-Smtp-Source: APXvYqy+tNfdjFQdC1LAU134iAHgftXkOcJud+bOH7kAsI8qdyD4BGryf2fFJg6ccp0KzglfNONpsXRFj2ovCgwopWs=
X-Received: by 2002:a19:3f0a:: with SMTP id m10mr18464003lfa.67.1572899392845;  Mon, 04 Nov 2019 12:29:52 -0800 (PST)
MIME-Version: 1.0
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Mon, 4 Nov 2019 12:29:41 -0800
Message-ID: <CAPDSy+4wrhqejh9k8=G7W267EgcT5Z2sDK7ZBGKtNn5kkbXGfg@mail.gmail.com>
Subject: QUIC Version Negotiation Extension
To: QUIC <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000093fc6405968b2d8d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/SCikyY021_sJP8fu0vkiMvCtN9Y>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 20:29:57 -0000

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

Hi everyone,

>From the recent discussion on multiple PRs, it appears that there might be
a need for downgrade-safe QUIC version negotiation, earlier than we
expected.

EKR and I updated our extension to hopefully suit these needs:
https://tools.ietf.org/html/draft-schinazi-quic-version-negotiation-02

Comments welcome here or on the GitHub (link in draft).

Thanks,
David

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

<div dir=3D"ltr">Hi everyone,<br><div><br></div><div>From the recent discus=
sion on multiple PRs, it appears that there might be a need for downgrade-s=
afe QUIC version negotiation, earlier than we expected.</div><div><br></div=
><div>EKR and I updated our extension to hopefully suit these needs:</div><=
div><a href=3D"https://tools.ietf.org/html/draft-schinazi-quic-version-nego=
tiation-02">https://tools.ietf.org/html/draft-schinazi-quic-version-negotia=
tion-02</a><br></div><div><br></div><div>Comments welcome here or on the Gi=
tHub (link in draft).</div><div><br></div><div>Thanks,</div><div>David</div=
></div>

--00000000000093fc6405968b2d8d--


From nobody Mon Nov  4 12:34:23 2019
Return-Path: <rch@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 87F35120041 for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 12:34:22 -0800 (PST)
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, DKIMWL_WL_MED=-0.001, 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_HELO_NONE=0.001, SPF_PASS=-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 3xtIcmDleaQp for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 12:34:21 -0800 (PST)
Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) (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 C11CF120018 for <quic@ietf.org>; Mon,  4 Nov 2019 12:34:20 -0800 (PST)
Received: by mail-wm1-x32c.google.com with SMTP id m17so8948548wmi.5 for <quic@ietf.org>; Mon, 04 Nov 2019 12:34:20 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=FqwXcOXhRdNA0/ZjlFXkXyvpc997v3+m4vlV5KV0X/A=; b=uEv0WpfLPW89axelB9FOlExGrtlSuS+EeiaHfGrmgLziOLhhjpqV9qo6e/bDkbSQGW t5jeLsZAq0LaKjlGw4nHDSG0TnA/uefjdFtZmtZVdgSHDQl6Cce4AXRa0lAOkKnAITbt URXTSmMQxgpcnybBlfB+7yy/WBGpIoF6FnVD4lIv4j1DTsANK0opZVlkYGY9r6nzOyPX D9/OE0i7/ZWO99XSgtKXJaPwsmk4rMxntOlNmwF8hhMKs85zjYIyTmw2UP3kGbqMDcU3 UCLa/X8VwjOpY/wRlEO+p9JWaVKpLtiVNGbXM+1bcQPuHyM3edGkYXvWfmDt/E/iBlJp nH7Q==
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=FqwXcOXhRdNA0/ZjlFXkXyvpc997v3+m4vlV5KV0X/A=; b=PyfPmF1O6uaJuIUxh0DePfZZhSvpCnPkyie8C6rMDKfhBW//1p1k8YzYksushpajzz phDM4biB4w7o0fH/DGIfVSUASuyaGhlD1t8qAEOgb5U0gcbwfGPEXrkzWnSjV9V6VJ3J OkRY7CyWOha+9hogI4V4Ew5fp159Md7pfsSfZ4OJXFadbYvW4jniFdX1ErTk5kFowBBY qRPWSlHRIMqa4Iv4BmJE5c7JoPRcsE5iPxO29fnyar8O5RKeGT9GS6+l18FVU1ojG/9k ppAaS9TGYMfIh3kxrKAUlq+uGSjpygnDmFmf4JvN6KFRsmqrvIxyDac1YZOKs4xshPfd lBCQ==
X-Gm-Message-State: APjAAAWZINi4Pv+pNGjRrEpZKNPsAWLUgBAT/Zp0BGaDHhG6FyrlS6nu 3F9nsALlR7RF/8f21XtVrmNxdb7dkhM5Ei2BVusZgiuN910=
X-Google-Smtp-Source: APXvYqxNsJiRC4BmC8YBhmYw1x05RUtndAEVzJBMDuSCn9sgiiAR+wQP2r9FU56sLfh/x9Yff3ybTHC3+CzFKxcd8Hk=
X-Received: by 2002:a05:600c:2944:: with SMTP id n4mr826247wmd.57.1572899658244;  Mon, 04 Nov 2019 12:34:18 -0800 (PST)
MIME-Version: 1.0
From: Ryan Hamilton <rch@google.com>
Date: Mon, 4 Nov 2019 12:34:06 -0800
Message-ID: <CAJ_4DfTN-25ZpDmGBFXxmz9RZCT=8JbpFoDX71eyhE1rEtPkMg@mail.gmail.com>
Subject: Alternate Version + Salt in Alt-Svc
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000066279605968b3d9f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/YJWsqLK2HAQEtpHGY8VbmR4lmHc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 20:34:23 -0000

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

Howdy Folks,

We've discussed the idea of attempting to reduce ossification by allowing
the server to deliver an alternative version and initial salt to the client
which can be used to speak "QUIC v1". One such mechanism for delivering
this version to the client is Alt-Svc. In the context of HTTP/3 this has
the wonderful property that even the first connection from a client to the
server can use this alternative version.

However, it seems that there might be a privacy/linkability issue with this
approach that I'm curious to get the groups' take on. If this information
were delivered via Alt-Svc, I would imagine that the na=C3=AFve implementat=
ion
would be to cache the Alt-Svc info as until it expires (via the ma=3D
attribute) and use the alternative version/salt in each subsequent QUIC
connection. Since the version field is 32 bits, that potentially allows
each user to use a distinct version. This is great for anti-ossification,
but seems problematic for linkability/privacy.

I can think of solutions/mitigations for this issue (like restricting the
number of bits which can be flipped by the server, or expiring the
alternative version in the client on first use, etc) but I'd be curious if
this seems like an issue to other folks first.

Cheers,

Ryan

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:trebuche=
t ms,sans-serif">Howdy Folks,<br></div><div class=3D"gmail_default" style=
=3D"font-family:trebuchet ms,sans-serif"><br></div><div class=3D"gmail_defa=
ult" style=3D"font-family:trebuchet ms,sans-serif">We&#39;ve discussed the =
idea of attempting to reduce ossification by allowing the server to deliver=
 an alternative version and initial salt to the client which can be used to=
 speak &quot;QUIC v1&quot;. One such mechanism for delivering this version =
to the client is Alt-Svc. In the context of HTTP/3 this has the wonderful p=
roperty that even the first connection from a client to the server can use =
this alternative version.</div><div class=3D"gmail_default" style=3D"font-f=
amily:trebuchet ms,sans-serif"><br></div><div class=3D"gmail_default" style=
=3D"font-family:trebuchet ms,sans-serif">However, it seems that there might=
 be a privacy/linkability issue with this approach that I&#39;m curious to =
get the groups&#39; take on. If this information were delivered via Alt-Svc=
, I would imagine that the na=C3=AFve implementation would be to cache the =
Alt-Svc info as until it expires (via the ma=3D attribute) and use the alte=
rnative version/salt in each subsequent QUIC connection. Since the version =
field is 32 bits, that potentially allows each user to use a distinct versi=
on. This is great for anti-ossification, but seems problematic=C2=A0for lin=
kability/privacy.</div><div class=3D"gmail_default" style=3D"font-family:tr=
ebuchet ms,sans-serif"><br></div><div class=3D"gmail_default" style=3D"font=
-family:trebuchet ms,sans-serif">I can think of solutions/mitigations for t=
his issue (like restricting the number of bits which can be flipped by the =
server, or expiring the alternative version in the client on first use, etc=
) but I&#39;d be curious if this seems like an issue to other folks first.<=
/div><div class=3D"gmail_default" style=3D"font-family:trebuchet ms,sans-se=
rif"><br></div><div class=3D"gmail_default" style=3D"font-family:trebuchet =
ms,sans-serif">Cheers,</div><div class=3D"gmail_default" style=3D"font-fami=
ly:trebuchet ms,sans-serif"><br></div><div class=3D"gmail_default" style=3D=
"font-family:trebuchet ms,sans-serif">Ryan</div></div>

--00000000000066279605968b3d9f--


From nobody Mon Nov  4 12:35:19 2019
Return-Path: <prvs=9211bbc757=chi-jiun.su@hughes.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 1DDE11208E5; Mon,  4 Nov 2019 12:34:44 -0800 (PST)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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=hughes.com header.b=n7b6iZOJ; dkim=pass (1024-bit key) header.d=hughes.com header.b=E0Vxa0sF
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 GvOME6225mNz; Mon,  4 Nov 2019 12:34:41 -0800 (PST)
Received: from mx0b-00115402.pphosted.com (mx0b-00115402.pphosted.com [148.163.153.174]) (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 EF2F51201E4; Mon,  4 Nov 2019 12:34:40 -0800 (PST)
Received: from pps.filterd (m0118427.ppops.net [127.0.0.1]) by mx0b-00115402.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id xA4KWjRa006406; Mon, 4 Nov 2019 20:34:36 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hughes.com; h=from : to : cc : subject : date : message-id : references : in-reply-to : content-type : mime-version; s=3152018; bh=79Aqoe2p/B9KX9ZKdWaHEwd8tw997WK4rj8ToCKymwU=; b=n7b6iZOJZnDtltOc4lAgMOh7cGrKNPqdezCn1VrrnHFRkLRscNCbvQS4AVbV54eakfC+ +Sou21AkQI5x+wQhDBQOE7W8AqSt1rhD3dKqOMsMdyf1mC4wp/M6tVWkEH3Px/2GrfDH 5H2nCrTMuncAUrFxLdGZ+rQXV7O7exIhrc3aJbbRzf+83XtZbfW1me+kX2QE4LFZ3mFu UeWrip4KOKkRpvNqs763exQ1AEzbDWI5TGYs38nXiAVZZa4+kjKeyrDdUdSheCbeYKwL klc/XvMNgwh86Pvp6j1GQ4SnIQ+8SgG6YBQkkkkXxei4z9Kdi5myFKTT9X6cQ5Zb8pnA JQ== 
Received: from nam04-sn1-obe.outbound.protection.outlook.com (mail-sn1nam04lp2057.outbound.protection.outlook.com [104.47.44.57]) by mx0b-00115402.pphosted.com with ESMTP id 2w1509jbue-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Mon, 04 Nov 2019 20:34:35 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=JeAjPvoyvB77CiLqwAnLRNDzf3PRemnfHDW6rl0vGPSP668BbU0+0S+XR8P2twV4zDcJVqh3hmO42R2nczJaTuxT/RtH8rpwe4YQty8qPUZRnKs4DGFzkUuGC1FJHeLKlKB2mrYA9ESi0YLD/VwGaMWHaP1vtfiuEbcWhG2ZVdn6ttF6OWxD+dikK3Q3/6C9tkgK1++slQTfOs2dM6FiuLWEEpUtmLOwl5o5zrfNunCyaoq9YfyKjzW8DPGa2jiLgwjAw3HMxL8ttg0qxg2jx/14JgR+zLsCmE1pX1Qgpij15OSJn02kGFPvH0VIZzEl4CKQnXibJuBVi0v5ofPNtQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=79Aqoe2p/B9KX9ZKdWaHEwd8tw997WK4rj8ToCKymwU=; b=eAseNnyh+4eDAyvgznZSABH4LqNt6bvxkYtWP4k4v2g/VnjX0TZEQeoctbSiUyURl+PHKMKjzVxeiFAcDRJVjzfyTBLdAhgjdqGWVu8F0+LPcwqwzUbIa0LOUUfdVkp8IUvz0Q0A/1aPp2f0eIB/AwVwV32umbY/JPpLvDeAryt817oCgKOszTo/lmFBLY4bYHJAU39QetOc4J47nsPGLCUHM5NYAyHr6N69fXmeBwVDU+5RC0aNSfgc3UpZNtTqf4b/eYBKgiAdc5I+013c1JwS8nXnx6sDHCol2aAp4JvlcMQvLUOo9XacvHDDZgV/bbTdaooORCtVMZmqywj98w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=hughes.com; dmarc=pass action=none header.from=hughes.com; dkim=pass header.d=hughes.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hughes.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=79Aqoe2p/B9KX9ZKdWaHEwd8tw997WK4rj8ToCKymwU=; b=E0Vxa0sF55y97FI4omN9WrFecUEgnrQdFlU/cS9tp2PjL+uYGBBAQioWrcTy8cxOxXDikr1pO2GzNN5ZpZBGT24hq21fzri+vtrnIO9XN7K+NSIDEm9wwRwcB8adVbY3QEQB7odpBVRXbM2YyGV+mxQFb+zLtY+KnVs8z2tzA38=
Received: from SN6PR11MB3087.namprd11.prod.outlook.com (52.135.126.143) by SN6PR11MB3198.namprd11.prod.outlook.com (52.135.112.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2408.24; Mon, 4 Nov 2019 20:34:33 +0000
Received: from SN6PR11MB3087.namprd11.prod.outlook.com ([fe80::992d:7b3f:7493:21e4]) by SN6PR11MB3087.namprd11.prod.outlook.com ([fe80::992d:7b3f:7493:21e4%4]) with mapi id 15.20.2408.024; Mon, 4 Nov 2019 20:34:33 +0000
From: "Su, Chi-Jiun" <Chi-Jiun.Su@hughes.com>
To: Lucas Pardue <lucaspardue.24.7@gmail.com>, Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>
CC: "quic@ietf.org" <quic@ietf.org>, Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, "masque@ietf.org" <masque@ietf.org>
Subject: RE: [Masque] FW: New Version Notification for draft-kuehlewind-quic-proxy-discovery-00.txt
Thread-Topic: [Masque] FW: New Version Notification for draft-kuehlewind-quic-proxy-discovery-00.txt
Thread-Index: AQHVkzBtXqSCGBS1QEWLK0BXXTrwWKd7THMA///xkwCAABGsgP//8OCAgAA2fIA=
Date: Mon, 4 Nov 2019 20:34:33 +0000
Message-ID: <SN6PR11MB3087D25371090E7E40FA32B2CE7F0@SN6PR11MB3087.namprd11.prod.outlook.com>
References: <157288641719.16495.4218503379126128243.idtracker@ietfa.amsl.com> <CA5EB3C0-F510-4883-B50B-51A3E46B47CA@ericsson.com> <CALGR9obp-YARLEXDVWvTqZ_h=Ocbn6m2On+uovK-SL-6TaOSXg@mail.gmail.com> <3F20108D-DEED-4AEF-89D3-55F11058110B@ericsson.com> <CALGR9oYHce0mnkj5Kz13EoR-zN3-xSr0igkJF2Z_dJ2vgfVNSQ@mail.gmail.com>
In-Reply-To: <CALGR9oYHce0mnkj5Kz13EoR-zN3-xSr0igkJF2Z_dJ2vgfVNSQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [139.85.223.11]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 12234c9f-3dda-426e-6b30-08d7616666e6
x-ms-traffictypediagnostic: SN6PR11MB3198:
x-ms-exchange-purlcount: 12
x-microsoft-antispam-prvs: <SN6PR11MB319854325B01FE1ACE3417FECE7F0@SN6PR11MB3198.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0211965D06
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(366004)(136003)(396003)(39860400002)(346002)(25584004)(53754006)(199004)(54094003)(189003)(99286004)(2906002)(229853002)(81156014)(55016002)(5660300002)(76176011)(7696005)(11346002)(966005)(476003)(6506007)(53546011)(71190400001)(71200400001)(4326008)(66574012)(446003)(86362001)(186003)(606006)(256004)(26005)(14454004)(102836004)(5024004)(25786009)(66066001)(14444005)(486006)(8676002)(236005)(54896002)(6306002)(81166006)(9686003)(15650500001)(52536014)(2420400007)(66446008)(54906003)(478600001)(66556008)(66476007)(76116006)(66946007)(110136005)(6116002)(790700001)(3846002)(7110500001)(316002)(7736002)(74316002)(6436002)(8936002)(33656002)(6246003)(64756008); DIR:OUT; SFP:1102; SCL:1; SRVR:SN6PR11MB3198; H:SN6PR11MB3087.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: hughes.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: isSzBiO0Aie3HNfpTMsM0NB92XJmJ+BbY5OYF9oUAVClqe0idjJVIDmvWLlegdBSymA7heAT4RXcdt3mYjuB8cn39H61RdU57hfmQ3s2EIlfP/xfYLsSv8RlOGTc4Irfnsvwl6h021bR+YDa3NGLOqQhYocR0vvaMluga638lzuJYXByYgz99SLpVZWNUrubdjWjvERXPPqe4KHMh4LzS94YdWZdHMy/ro5EK0pdIDnnv9tO1Ig3hcbXsgZggegdHgWI6ndEIsBHd6oXp210t1KHeWodNBv6uKHJEbPsYu1F5tnYP0APXRAbg2hbLbPSrDZON6fX+CIo/VLz1Y/pfHcdPpgIjHZgTA9fPNJ4Ct91XkikTuDJGxA9771wYn8qvgHtrBxujG14qbtiFCKmTS46aC+cXPJOxgskc+4qAa2FIF6HLgyq56OK4mR74m7wY0j4lER7pQ2c0hAUgWE47qDDZ56TeWg8LyZxTeedA5A=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_SN6PR11MB3087D25371090E7E40FA32B2CE7F0SN6PR11MB3087namp_"
MIME-Version: 1.0
X-OriginatorOrg: hughes.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 12234c9f-3dda-426e-6b30-08d7616666e6
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Nov 2019 20:34:33.5820 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0e1f3187-4610-4ce2-bad1-b92f4ba36ab3
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: L06oMiqFq8qbwXBHLgeASN0R2mvDlv6bLnKi6FPNNrwqQa9ps4q4ozAARjafxfbwQc/5Z86qFgUnYFQkzYzKTQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: SN6PR11MB3198
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,1.0.8 definitions=2019-11-04_11:2019-11-04,2019-11-04 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 lowpriorityscore=0 mlxlogscore=999 impostorscore=0 phishscore=0 priorityscore=1501 mlxscore=0 adultscore=0 malwarescore=0 spamscore=0 suspectscore=0 bulkscore=0 clxscore=1011 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1908290000 definitions=main-1911040198
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/wqA-2nWDRr3kXyG8R1XyH6feAFI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 20:34:53 -0000

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

SGVyZSBhcmUgc29tZSBtb3JlIHJlbGF0ZWQgdG8gd3BkIGZvciBodHRwOg0KDQpodHRwczovL3Rv
b2xzLmlldGYub3JnL2h0bWwvZHJhZnQtY2hvdy1odHRwYmlzLXByb3h5LWRpc2NvdmVyeS0wMA0K
DQpodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtbm90dGluZ2hhbS13ZWItcHJveHkt
ZGVzYy0wMQ0KDQoNCg0KRnJvbTogTWFzcXVlIDxtYXNxdWUtYm91bmNlc0BpZXRmLm9yZz4gT24g
QmVoYWxmIE9mIEx1Y2FzIFBhcmR1ZQ0KU2VudDogTW9uZGF5LCBOb3ZlbWJlciA0LCAyMDE5IDEy
OjE2IFBNDQpUbzogTWlyamEgS3VlaGxld2luZCA8bWlyamEua3VlaGxld2luZEBlcmljc3Nvbi5j
b20+DQpDYzogcXVpY0BpZXRmLm9yZzsgWmFoZWR1enphbWFuIFNhcmtlciA8emFoZWR1enphbWFu
LnNhcmtlckBlcmljc3Nvbi5jb20+OyBtYXNxdWVAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBbTWFz
cXVlXSBGVzogTmV3IFZlcnNpb24gTm90aWZpY2F0aW9uIGZvciBkcmFmdC1rdWVobGV3aW5kLXF1
aWMtcHJveHktZGlzY292ZXJ5LTAwLnR4dA0KDQpDQVVUSU9OOiBUaGlzIGVtYWlsIG9yaWdpbmF0
ZWQgZnJvbSBvdXRzaWRlIG9mIHRoZSBvcmdhbml6YXRpb24uIERvIG5vdCBjbGljayBsaW5rcyBv
ciBvcGVuIGF0dGFjaG1lbnRzIHVubGVzcyB5b3UgcmVjb2duaXplIHRoZSBzZW5kZXIgYW5kIGtu
b3cgdGhlIGNvbnRlbnQgaXMgc2FmZS4NCkknbSBub3QgYW4gZXhwZXJ0IGluIGVpdGhlciBXUEFE
IFsxXSBvciBQQUMgWzJdLCBidXQgSSBhbSBhbiBleHBlcnQgaW4gZmVlbGluZyB0aGVpciBwYWlu
IGFzIGEgdXNlciBvbiBXaW5kb3dzLiBQYXJ0IG9mIHRoZWlyIHBhaW4gY29tZXMgZnJvbSBsYWNr
IG9mIGZvcm1hbCBzdGFuZGFyZGl6YXRpb24sIHJlc3VsdGluZyBpbiBzb21lIHdvcmQtb2YtbW91
dGggYXBwcm9hY2hlcyB0byBwcm9ibGVtIHNvbHZpbmcsIGVzcGVjaWFsbHkgaG93IHRoZXkgd29y
ayAob3IgZG9uJ3QpIHdpdGggdGhlIHN0YW5kYXJkaXNlZCBhcHByb2FjaGVzIHN1Y2ggYXMgREhD
UC4NCg0KSW4gbG9va2luZyB0aGlzIHVwLCBJIGRpZCBkaXNjb3ZlciBkcmFmdC1pZXRmLXdyZWMt
d3BhZC0wMSwgYSA+IDIwIEktRCBmb3IgV1BBRCBbM10sIHdvdyENCg0KWzFdIC0gaHR0cHM6Ly9l
bi53aWtpcGVkaWEub3JnL3dpa2kvV2ViX1Byb3h5X0F1dG8tRGlzY292ZXJ5X1Byb3RvY29sPGh0
dHBzOi8vdXJsZGVmZW5zZS5jb20vdjMvX19odHRwczovZW4ud2lraXBlZGlhLm9yZy93aWtpL1dl
Yl9Qcm94eV9BdXRvLURpc2NvdmVyeV9Qcm90b2NvbF9fOyEwckx4bmM1b2g0cyFqUG9zUXQyNkVh
alNjZ1V1cG9pQ0lNS090dTFldTlSMHRnMkNFa01YTnE4Q3g1NnNDbWtMN1BtSTlQTjdnY0FHeEEk
Pg0KWzJdIC0gaHR0cHM6Ly9lbi53aWtpcGVkaWEub3JnL3dpa2kvUHJveHlfYXV0by1jb25maWc8
aHR0cHM6Ly91cmxkZWZlbnNlLmNvbS92My9fX2h0dHBzOi9lbi53aWtpcGVkaWEub3JnL3dpa2kv
UHJveHlfYXV0by1jb25maWdfXzshMHJMeG5jNW9oNHMhalBvc1F0MjZFYWpTY2dVdXBvaUNJTUtP
dHUxZXU5UjB0ZzJDRWtNWE5xOEN4NTZzQ21rTDdQbUk5UE9oZGRsbUJBJD4NClszXSAtIGh0dHBz
Oi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1pZXRmLXdyZWMtd3BhZC0wMTxodHRwczovL3Vy
bGRlZmVuc2UuY29tL3YzL19faHR0cHM6L3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi13
cmVjLXdwYWQtMDFfXzshMHJMeG5jNW9oNHMhalBvc1F0MjZFYWpTY2dVdXBvaUNJTUtPdHUxZXU5
UjB0ZzJDRWtNWE5xOEN4NTZzQ21rTDdQbUk5UE9KaVhrOW9BJD4NCg0KT24gTW9uLCBOb3YgNCwg
MjAxOSBhdCA1OjA5IFBNIE1pcmphIEt1ZWhsZXdpbmQgPG1pcmphLmt1ZWhsZXdpbmRAZXJpY3Nz
b24uY29tPG1haWx0bzptaXJqYS5rdWVobGV3aW5kQGVyaWNzc29uLmNvbT4+IHdyb3RlOg0KSGkg
THVjYXMsDQoNCm5vLCB3ZSBkaWRu4oCZdCBjb25zaWRlciB0aGlzIHlldCBidXQgb25seSBiZWNh
dXNlIHdlIHdlcmUgbm90IHJlYWxseSBhd2FyZSBvZiB0aGF0LiBEbyB5b3UgaGF2ZSBhIHBvaW50
ZXI/IE9yIHNlbmQgYSBQUiDwn5iKDQoNCmh0dHBzOi8vZ2l0aHViLmNvbS9taXJqYWsvZHJhZnQt
a3VlaGxld2luZC1xdWljLXByb3h5LWRpc2NvdmVyeTxodHRwczovL3VybGRlZmVuc2UuY29tL3Yz
L19faHR0cHM6L2dpdGh1Yi5jb20vbWlyamFrL2RyYWZ0LWt1ZWhsZXdpbmQtcXVpYy1wcm94eS1k
aXNjb3ZlcnlfXzshMHJMeG5jNW9oNHMhalBvc1F0MjZFYWpTY2dVdXBvaUNJTUtPdHUxZXU5UjB0
ZzJDRWtNWE5xOEN4NTZzQ21rTDdQbUk5UE1WZzMxQWJ3JD4NCg0KTWlyamENCg0KDQpGcm9tOiBM
dWNhcyBQYXJkdWUgPGx1Y2FzcGFyZHVlLjI0LjdAZ21haWwuY29tPG1haWx0bzpsdWNhc3BhcmR1
ZS4yNC43QGdtYWlsLmNvbT4+DQpEYXRlOiBNb25kYXksIDQuIE5vdmVtYmVyIDIwMTkgYXQgMTg6
MDYNClRvOiBNaXJqYSBLdWVobGV3aW5kIDxtaXJqYS5rdWVobGV3aW5kQGVyaWNzc29uLmNvbTxt
YWlsdG86bWlyamEua3VlaGxld2luZEBlcmljc3Nvbi4uY29tPj4NCkNjOiAicXVpY0BpZXRmLm9y
ZzxtYWlsdG86cXVpY0BpZXRmLm9yZz4iIDxxdWljQGlldGYub3JnPG1haWx0bzpxdWljQGlldGYu
b3JnPj4sICJtYXNxdWVAaWV0Zi5vcmc8bWFpbHRvOm1hc3F1ZUBpZXRmLm9yZz4iIDxtYXNxdWVA
aWV0Zi5vcmc8bWFpbHRvOm1hc3F1ZUBpZXRmLm9yZz4+LCBaYWhlZHV6emFtYW4gU2Fya2VyIDx6
YWhlZHV6emFtYW4uc2Fya2VyQGVyaWNzc29uLmNvbTxtYWlsdG86emFoZWR1enphbWFuLnNhcmtl
ckBlcmljc3Nvbi5jb20+Pg0KU3ViamVjdDogUmU6IFtNYXNxdWVdIEZXOiBOZXcgVmVyc2lvbiBO
b3RpZmljYXRpb24gZm9yIGRyYWZ0LWt1ZWhsZXdpbmQtcXVpYy1wcm94eS1kaXNjb3ZlcnktMDAu
dHh0DQoNClRoYW5rcyBmb3Igc2hhcmluZyB0aGlzLg0KDQpJIHdvbmRlciBpZiB5b3UgY29uc2lk
ZXJlZCBXUEFEIChXZWIgUHJveHkgQXV0b2Rpc2NvdmVyeSkgb3IgUEFDIChQcm94eSBhdXRvLWNv
bmZpZyk/IEFsdGhvdWdoIHRhcmdldHRlZCBhdCB0aGUgYXBwbGljYXRpb24gbGF5ZXIsIGl0IG1p
Z2h0IGhlbHAgdG8gY29tbWVudCBvbiBob3cgdGhvc2UgZm9ybXMgb2YgZGlzY292ZXJ5IHdvdWxk
IHJlbGF0ZSB0byB0aGUgbWV0aG9kcyBvdXRsaW5lZCBpbiB5b3VyIGRyYWZ0Lg0KDQpDaGVlcnMs
DQpMdWNhcw0KDQpPbiBNb24sIE5vdiA0LCAyMDE5IGF0IDQ6NTggUE0gTWlyamEgS3VlaGxld2lu
ZCA8bWlyamEua3VlaGxld2luZD00MGVyaWNzc29uLmNvbUBkbWFyYy5pZXRmLm9yZzxtYWlsdG86
NDBlcmljc3Nvbi5jb21AZG1hcmMuaWV0Zi5vcmc+PiB3cm90ZToNCkhpIGFsbCwNCg0Kd2Ugc3Vi
bWl0dGVkIGEgbmV3IGRyYWZ0IHRoYXQgbGlzdHMgZGlzY292ZXJ5IG1lY2hhbmlzbXMgZm9yIFFV
SUMtYmFzZWQgcHJveGllcyAoc2VlIGJlbG93KS4gVGhpcyBpcyBvbmUgcGllY2Ugb2Ygd29yayB0
aGF0IGlzIG5lZWRlZCBmb3IgbW9zdCBvZiB0aGUgdXNlIGNhc2VzIGluIGRyYWZ0LWt1ZWhsZXdp
bmQtcXVpYy1zdWJzdHJhdGUuDQoNCkxldCBtZSBrbm93IGlmIHlvdSBoYXZlIGFueSBxdWVzdGlv
bnMgb3IgY29tbWVudHMhDQoNCk1pcmphDQoNCg0KT24gMDQuMTEuMTksIDE3OjUzLCAiaW50ZXJu
ZXQtZHJhZnRzQGlldGYub3JnPG1haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmc+IiA8aW50
ZXJuZXQtZHJhZnRzQGlldGYub3JnPG1haWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmc+PiB3
cm90ZToNCg0KDQogICAgQSBuZXcgdmVyc2lvbiBvZiBJLUQsIGRyYWZ0LWt1ZWhsZXdpbmQtcXVp
Yy1wcm94eS1kaXNjb3ZlcnktMDAudHh0DQogICAgaGFzIGJlZW4gc3VjY2Vzc2Z1bGx5IHN1Ym1p
dHRlZCBieSBNaXJqYSBLdWVobGV3aW5kIGFuZCBwb3N0ZWQgdG8gdGhlDQogICAgSUVURiByZXBv
c2l0b3J5Lg0KDQogICAgTmFtZTogICAgICAgICAgICAgICBkcmFmdC1rdWVobGV3aW5kLXF1aWMt
cHJveHktZGlzY292ZXJ5DQogICAgUmV2aXNpb246ICAgMDANCiAgICBUaXRsZTogICAgICAgICAg
ICAgIERpc2NvdmVyeSBNZWNoYW5pc20gZm9yIFFVSUMtYmFzZWQsIE5vbi10cmFuc3BhcmVudCBQ
cm94eSBTZXJ2aWNlcw0KICAgIERvY3VtZW50IGRhdGU6ICAgICAgMjAxOS0xMS0wNA0KICAgIEdy
b3VwOiAgICAgICAgICAgICAgSW5kaXZpZHVhbCBTdWJtaXNzaW9uDQogICAgUGFnZXM6ICAgICAg
ICAgICAgICAxMQ0KICAgIFVSTDogICAgICAgICAgICBodHRwczovL3d3dy5pZXRmLm9yZy9pbnRl
cm5ldC1kcmFmdHMvZHJhZnQta3VlaGxld2luZC1xdWljLXByb3h5LWRpc2NvdmVyeS0wMC50eHQ8
aHR0cHM6Ly91cmxkZWZlbnNlLmNvbS92My9fX2h0dHBzOi93d3cuaWV0Zi5vcmcvaW50ZXJuZXQt
ZHJhZnRzL2RyYWZ0LWt1ZWhsZXdpbmQtcXVpYy1wcm94eS1kaXNjb3ZlcnktMDAudHh0X187ITBy
THhuYzVvaDRzIWpQb3NRdDI2RWFqU2NnVXVwb2lDSU1LT3R1MWV1OVIwdGcyQ0VrTVhOcThDeDU2
c0Nta0w3UG1JOVBQNmZPdEZmdyQ+DQogICAgU3RhdHVzOiAgICAgICAgIGh0dHBzOi8vZGF0YXRy
YWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWt1ZWhsZXdpbmQtcXVpYy1wcm94eS1kaXNjb3Zlcnkv
PGh0dHBzOi8vdXJsZGVmZW5zZS5jb20vdjMvX19odHRwczovZGF0YXRyYWNrZXIuaWV0Zi5vcmcv
ZG9jL2RyYWZ0LWt1ZWhsZXdpbmQtcXVpYy1wcm94eS1kaXNjb3ZlcnkvX187ITByTHhuYzVvaDRz
IWpQb3NRdDI2RWFqU2NnVXVwb2lDSU1LT3R1MWV1OVIwdGcyQ0VrTVhOcThDeDU2c0Nta0w3UG1J
OVBOaXJKQm5LUSQ+DQogICAgSHRtbGl6ZWQ6ICAgICAgIGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcv
aHRtbC9kcmFmdC1rdWVobGV3aW5kLXF1aWMtcHJveHktZGlzY292ZXJ5LTAwPGh0dHBzOi8vdXJs
ZGVmZW5zZS5jb20vdjMvX19odHRwczovdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1rdWVobGV3
aW5kLXF1aWMtcHJveHktZGlzY292ZXJ5LTAwX187ITByTHhuYzVvaDRzIWpQb3NRdDI2RWFqU2Nn
VXVwb2lDSU1LT3R1MWV1OVIwdGcyQ0VrTVhOcThDeDU2c0Nta0w3UG1JOVBOdDJsaldWUSQ+DQog
ICAgSHRtbGl6ZWQ6ICAgICAgIGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2h0bWwv
ZHJhZnQta3VlaGxld2luZC1xdWljLXByb3h5LWRpc2NvdmVyeTxodHRwczovL3VybGRlZmVuc2Uu
Y29tL3YzL19faHR0cHM6L2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9odG1sL2RyYWZ0LWt1ZWhs
ZXdpbmQtcXVpYy1wcm94eS1kaXNjb3ZlcnlfXzshMHJMeG5jNW9oNHMhalBvc1F0MjZFYWpTY2dV
dXBvaUNJTUtPdHUxZXU5UjB0ZzJDRWtNWE5xOEN4NTZzQ21rTDdQbUk5UE5Ma293d1B3JD4NCg0K
DQogICAgQWJzdHJhY3Q6DQogICAgICAgT2Z0ZW4gYW4gaW50ZXJtZWRpYXRlIGluc3RhbmNlIChz
dWNoIGFzIGEgcHJveHkgc2VydmVyKSBpcyB1c2VkIHRvDQogICAgICAgY29ubmVjdCB0byBhIHdl
YiBzZXJ2ZXIgb3IgYSBjb21tdW5pY2F0aW5nIHBlZXIgaWYgYSBkaXJlY3QgZW5kLXRvLQ0KICAg
ICAgIGVuZCBJUCBjb25uZWN0aXZpdHkgaXMgbm90IHBvc3NpYmxlIG9yIHRoZSBwcm94eSBjYW4g
cHJvdmlkZSBhDQogICAgICAgc3VwcG9ydCBzZXJ2aWNlIGxpa2UsIGUuZy4sIGFkZHJlc3MgYW5v
bnltaXNhdGlvbi4gIFRvIHVzZSBhIG5vbi0NCiAgICAgICB0cmFuc3BhcmVudCBwcm94eSBhIGNs
aWVudCBleHBsaWNpdGx5IGNvbm5lY3RzIHRvIGl0IGFuZCByZXF1ZXN0cw0KICAgICAgIGZvcndh
cmRpbmcgdG8gdGhlIGZpbmFsIHRhcmdldCBzZXJ2ZXIuICBUaGUgY2xpZW50IGVpdGhlciBrbm93
cyB0aGUNCiAgICAgICBwcm94eSBhZGRyZXNzIGFzIHByZWNvbmZpZ3VyZWQgaW4gdGhlIGFwcGxp
Y2F0aW9uIG9yIGNhbiBkeW5hbWljYWxseQ0KICAgICAgIGxlYXJuIGFib3V0IGF2YWlsYWJsZSBw
cm94eSBzZXJ2aWNlcy4gIFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzDQogICAgICAgZGlmZmVyZW50
IGRpc2NvdmVyeSBtZWNoYW5pc21zIGZvciBub24tdHJhbnNwYXJlbnQgcHJveGllcyB0aGF0IGFy
ZQ0KICAgICAgIGVpdGhlciBsb2NhdGVkIGluIHRoZSBsb2NhbCBuZXR3b3JrLCBlLmcuIGhvbWUg
b3IgZW50ZXJwcmlzZSBuZXR3b3JrLA0KICAgICAgIGluIHRoZSBhY2Nlc3MgbmV0d29yaywgb3Ig
c29tZXdoZXJlIGVsc2Ugb24gdGhlIEludGVybmV0IHVzdWFsbHkNCiAgICAgICBjbG9zZSB0byB0
aGUgdGFyZ2V0IHNlcnZlciBvciBldmVuIGluIHRoZSBzYW1lIG5ldHdvcmsgYXMgdGhlIHRhcmdl
dA0KICAgICAgIHNlcnZlci4NCg0KICAgICAgIFRoaXMgZG9jdW1lbnQgYXNzdW1lcyB0aGF0IHRo
ZSBub24tdHJhbnNwYXJlbnQgcHJveHkgc2VydmVyIGlzDQogICAgICAgY29ubmVjdGVkIHZpYSBR
VUlDIGFuZCBkaXNjdXNzZXMgcG90ZW50aWFsIGRpc2NvdmVyeSBtZWNoYW5pc21zIGZvcg0KICAg
ICAgIHN1Y2ggYSBRVUlDLWJhc2VkLCBub24tdHJhbnNwYXJlbnQgcHJveHkuDQoNCg0KDQoNCiAg
ICBQbGVhc2Ugbm90ZSB0aGF0IGl0IG1heSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0
aGUgdGltZSBvZiBzdWJtaXNzaW9uDQogICAgdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5k
IGRpZmYgYXJlIGF2YWlsYWJsZSBhdCB0b29scy5pZXRmLm9yZzxodHRwczovL3VybGRlZmVuc2Uu
Y29tL3YzL19faHR0cDovdG9vbHMuaWV0Zi5vcmdfXzshMHJMeG5jNW9oNHMhalBvc1F0MjZFYWpT
Y2dVdXBvaUNJTUtPdHUxZXU5UjB0ZzJDRWtNWE5xOEN4NTZzQ21rTDdQbUk5UE5RaDdOa3VBJD4u
DQoNCiAgICBUaGUgSUVURiBTZWNyZXRhcmlhdA0KDQoNCg0KLS0NCk1hc3F1ZSBtYWlsaW5nIGxp
c3QNCk1hc3F1ZUBpZXRmLm9yZzxtYWlsdG86TWFzcXVlQGlldGYub3JnPg0KaHR0cHM6Ly93d3cu
aWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tYXNxdWU8aHR0cHM6Ly91cmxkZWZlbnNlLmNvbS92
My9fX2h0dHBzOi93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9tYXNxdWVfXzshMHJMeG5j
NW9oNHMhalBvc1F0MjZFYWpTY2dVdXBvaUNJTUtPdHUxZXU5UjB0ZzJDRWtNWE5xOEN4NTZzQ21r
TDdQbUk5UE80STZBcGR3JD4NCg==

--_000_SN6PR11MB3087D25371090E7E40FA32B2CE7F0SN6PR11MB3087namp_
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
cGFuLkVtYWlsU3R5bGUxOA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250
LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5
bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9
DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGlu
IDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlv
bjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVs
dHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0t
W2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlk
bWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2Vu
ZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJw
dXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PkhlcmUgYXJlIHNvbWUgbW9yZSByZWxhdGVkIHRvIHdwZCBmb3IgaHR0cDo8bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWNo
b3ctaHR0cGJpcy1wcm94eS1kaXNjb3ZlcnktMDAiPmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRt
bC9kcmFmdC1jaG93LWh0dHBiaXMtcHJveHktZGlzY292ZXJ5LTAwPC9hPjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtbm90
dGluZ2hhbS13ZWItcHJveHktZGVzYy0wMSI+aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2Ry
YWZ0LW5vdHRpbmdoYW0td2ViLXByb3h5LWRlc2MtMDE8L2E+PG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJz
cDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj5Gcm9tOjwvYj4gTWFzcXVlICZs
dDttYXNxdWUtYm91bmNlc0BpZXRmLm9yZyZndDsgPGI+T24gQmVoYWxmIE9mDQo8L2I+THVjYXMg
UGFyZHVlPGJyPg0KPGI+U2VudDo8L2I+IE1vbmRheSwgTm92ZW1iZXIgNCwgMjAxOSAxMjoxNiBQ
TTxicj4NCjxiPlRvOjwvYj4gTWlyamEgS3VlaGxld2luZCAmbHQ7bWlyamEua3VlaGxld2luZEBl
cmljc3Nvbi5jb20mZ3Q7PGJyPg0KPGI+Q2M6PC9iPiBxdWljQGlldGYub3JnOyBaYWhlZHV6emFt
YW4gU2Fya2VyICZsdDt6YWhlZHV6emFtYW4uc2Fya2VyQGVyaWNzc29uLmNvbSZndDs7IG1hc3F1
ZUBpZXRmLm9yZzxicj4NCjxiPlN1YmplY3Q6PC9iPiBSZTogW01hc3F1ZV0gRlc6IE5ldyBWZXJz
aW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQta3VlaGxld2luZC1xdWljLXByb3h5LWRpc2NvdmVy
eS0wMC50eHQ8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXYgYWxpZ249ImNlbnRlciI+DQo8dGFibGUgY2xhc3M9Ik1z
b05vcm1hbFRhYmxlIiBib3JkZXI9IjAiIGNlbGxwYWRkaW5nPSIwIiB3aWR0aD0iMTAwJSIgc3R5
bGU9IndpZHRoOjEwMC4wJTtiYWNrZ3JvdW5kOiNGRkVCOUMiPg0KPHRib2R5Pg0KPHRyPg0KPHRk
IHN0eWxlPSJwYWRkaW5nOi43NXB0IC43NXB0IC43NXB0IC43NXB0Ij4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJjb2xvcjpyZWQiPkNBVVRJT046PC9zcGFuPjwvYj4gVGhp
cyBlbWFpbCBvcmlnaW5hdGVkIGZyb20gb3V0c2lkZSBvZiB0aGUgb3JnYW5pemF0aW9uLiBEbyBu
b3QgY2xpY2sgbGlua3Mgb3Igb3BlbiBhdHRhY2htZW50cyB1bmxlc3MgeW91IHJlY29nbml6ZSB0
aGUgc2VuZGVyIGFuZCBrbm93IHRoZSBjb250ZW50IGlzIHNhZmUuPG86cD48L286cD48L3A+DQo8
L3RkPg0KPC90cj4NCjwvdGJvZHk+DQo8L3RhYmxlPg0KPC9kaXY+DQo8L2Rpdj4NCjxkaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSdtIG5vdCBhbiBleHBlcnQgaW4gZWl0aGVyIFdQ
QUQgWzFdIG9yIFBBQyBbMl0sIGJ1dCBJIGFtIGFuIGV4cGVydCBpbiBmZWVsaW5nIHRoZWlyIHBh
aW4gYXMgYSB1c2VyIG9uIFdpbmRvd3MuIFBhcnQgb2YgdGhlaXIgcGFpbiBjb21lcyBmcm9tIGxh
Y2sgb2YgZm9ybWFsIHN0YW5kYXJkaXphdGlvbiwgcmVzdWx0aW5nIGluIHNvbWUgd29yZC1vZi1t
b3V0aCBhcHByb2FjaGVzIHRvIHByb2JsZW0gc29sdmluZywNCiBlc3BlY2lhbGx5IGhvdyB0aGV5
IHdvcmsgKG9yIGRvbid0KSB3aXRoIHRoZSBzdGFuZGFyZGlzZWQgYXBwcm9hY2hlcyBzdWNoIGFz
IERIQ1AuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPkluIGxvb2tpbmcgdGhpcyB1cCwgSSBkaWQgZGlzY292ZXIgZHJhZnQtaWV0Zi13cmVjLXdw
YWQtMDEsIGEgJmd0OyAyMCBJLUQgZm9yIFdQQUQgWzNdLCB3b3chPG86cD48L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlsxXSAtIDxhIGhyZWY9Imh0dHBz
Oi8vdXJsZGVmZW5zZS5jb20vdjMvX19odHRwczovZW4ud2lraXBlZGlhLm9yZy93aWtpL1dlYl9Q
cm94eV9BdXRvLURpc2NvdmVyeV9Qcm90b2NvbF9fOyEwckx4bmM1b2g0cyFqUG9zUXQyNkVhalNj
Z1V1cG9pQ0lNS090dTFldTlSMHRnMkNFa01YTnE4Q3g1NnNDbWtMN1BtSTlQTjdnY0FHeEEkIj4N
Cmh0dHBzOi8vZW4ud2lraXBlZGlhLm9yZy93aWtpL1dlYl9Qcm94eV9BdXRvLURpc2NvdmVyeV9Q
cm90b2NvbDwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPlsyXSAtIDxhIGhyZWY9Imh0dHBzOi8vdXJsZGVmZW5zZS5jb20vdjMvX19odHRwczov
ZW4ud2lraXBlZGlhLm9yZy93aWtpL1Byb3h5X2F1dG8tY29uZmlnX187ITByTHhuYzVvaDRzIWpQ
b3NRdDI2RWFqU2NnVXVwb2lDSU1LT3R1MWV1OVIwdGcyQ0VrTVhOcThDeDU2c0Nta0w3UG1JOVBP
aGRkbG1CQSQiPg0KaHR0cHM6Ly9lbi53aWtpcGVkaWEub3JnL3dpa2kvUHJveHlfYXV0by1jb25m
aWc8L2E+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5bM10gLSA8YSBocmVmPSJodHRwczovL3VybGRlZmVuc2UuY29tL3YzL19faHR0cHM6L3Rvb2xz
LmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi13cmVjLXdwYWQtMDFfXzshMHJMeG5jNW9oNHMhalBv
c1F0MjZFYWpTY2dVdXBvaUNJTUtPdHUxZXU5UjB0ZzJDRWtNWE5xOEN4NTZzQ21rTDdQbUk5UE9K
aVhrOW9BJCI+DQpodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi13cmVjLXdw
YWQtMDE8L2E+PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPk9uIE1vbiwgTm92IDQsIDIwMTkgYXQgNTowOSBQTSBNaXJqYSBLdWVobGV3aW5kICZs
dDs8YSBocmVmPSJtYWlsdG86bWlyamEua3VlaGxld2luZEBlcmljc3Nvbi5jb20iPm1pcmphLmt1
ZWhsZXdpbmRAZXJpY3Nzb24uY29tPC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0ND
Q0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFy
Z2luLXJpZ2h0OjBpbiI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+SGkg
THVjYXMsPHNwYW4gbGFuZz0iREUiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0byI+Jm5ic3A7PHNwYW4gbGFuZz0iREUiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28t
bWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+bm8sIHdlIGRpZG7igJl0IGNvbnNpZGVyIHRoaXMgeWV0
IGJ1dCBvbmx5IGJlY2F1c2Ugd2Ugd2VyZSBub3QgcmVhbGx5IGF3YXJlIG9mIHRoYXQuIERvIHlv
dSBoYXZlIGEgcG9pbnRlcj8gT3Igc2VuZCBhIFBSDQo8c3BhbiBzdHlsZT0iZm9udC1mYW1pbHk6
JnF1b3Q7U2Vnb2UgVUkgRW1vamkmcXVvdDssc2Fucy1zZXJpZiI+JiMxMjg1MjI7PC9zcGFuPjxz
cGFuIGxhbmc9IkRFIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPiZuYnNwOzxzcGFuIGxhbmc9IkRFIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1i
b3R0b20tYWx0OmF1dG8iPjxhIGhyZWY9Imh0dHBzOi8vdXJsZGVmZW5zZS5jb20vdjMvX19odHRw
czovZ2l0aHViLmNvbS9taXJqYWsvZHJhZnQta3VlaGxld2luZC1xdWljLXByb3h5LWRpc2NvdmVy
eV9fOyEwckx4bmM1b2g0cyFqUG9zUXQyNkVhalNjZ1V1cG9pQ0lNS090dTFldTlSMHRnMkNFa01Y
TnE4Q3g1NnNDbWtMN1BtSTlQTVZnMzFBYnckIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly9naXRo
dWIuY29tL21pcmphay9kcmFmdC1rdWVobGV3aW5kLXF1aWMtcHJveHktZGlzY292ZXJ5PC9hPjxz
cGFuIGxhbmc9IkRFIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPiZuYnNwOzxzcGFuIGxhbmc9IkRFIj48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1i
b3R0b20tYWx0OmF1dG8iPk1pcmphPHNwYW4gbGFuZz0iREUiPjxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PHNwYW4gbGFuZz0iREUiPjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PHNwYW4gbGFuZz0i
REUiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRl
ci10b3A6c29saWQgd2luZG93dGV4dCAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluO2Jv
cmRlci1jb2xvcjpjdXJyZW50Y29sb3IgY3VycmVudGNvbG9yIj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0bzttYXJnaW4tbGVmdDouNWluIj4NCjxiPjxzcGFuIGxhbmc9IkRFIiBzdHlsZT0iZm9udC1z
aXplOjEyLjBwdDtjb2xvcjpibGFjayI+RnJvbTogPC9zcGFuPjwvYj48c3BhbiBsYW5nPSJERSIg
c3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Y29sb3I6YmxhY2siPkx1Y2FzIFBhcmR1ZSAmbHQ7PGEg
aHJlZj0ibWFpbHRvOmx1Y2FzcGFyZHVlLjI0LjdAZ21haWwuY29tIiB0YXJnZXQ9Il9ibGFuayI+
bHVjYXNwYXJkdWUuMjQuN0BnbWFpbC5jb208L2E+Jmd0Ozxicj4NCjxiPkRhdGU6IDwvYj5Nb25k
YXksIDQuIE5vdmVtYmVyIDIwMTkgYXQgMTg6MDY8YnI+DQo8Yj5UbzogPC9iPk1pcmphIEt1ZWhs
ZXdpbmQgJmx0OzxhIGhyZWY9Im1haWx0bzptaXJqYS5rdWVobGV3aW5kQGVyaWNzc29uLi5jb20i
IHRhcmdldD0iX2JsYW5rIj5taXJqYS5rdWVobGV3aW5kQGVyaWNzc29uLmNvbTwvYT4mZ3Q7PGJy
Pg0KPGI+Q2M6IDwvYj4mcXVvdDs8YSBocmVmPSJtYWlsdG86cXVpY0BpZXRmLm9yZyIgdGFyZ2V0
PSJfYmxhbmsiPnF1aWNAaWV0Zi5vcmc8L2E+JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86cXVp
Y0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPnF1aWNAaWV0Zi5vcmc8L2E+Jmd0OywgJnF1b3Q7
PGEgaHJlZj0ibWFpbHRvOm1hc3F1ZUBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPm1hc3F1ZUBp
ZXRmLm9yZzwvYT4mcXVvdDsgJmx0OzxhIGhyZWY9Im1haWx0bzptYXNxdWVAaWV0Zi5vcmciIHRh
cmdldD0iX2JsYW5rIj5tYXNxdWVAaWV0Zi5vcmc8L2E+Jmd0OywNCiBaYWhlZHV6emFtYW4gU2Fy
a2VyICZsdDs8YSBocmVmPSJtYWlsdG86emFoZWR1enphbWFuLnNhcmtlckBlcmljc3Nvbi5jb20i
IHRhcmdldD0iX2JsYW5rIj56YWhlZHV6emFtYW4uc2Fya2VyQGVyaWNzc29uLmNvbTwvYT4mZ3Q7
PGJyPg0KPGI+U3ViamVjdDogPC9iPlJlOiBbTWFzcXVlXSBGVzogTmV3IFZlcnNpb24gTm90aWZp
Y2F0aW9uIGZvciBkcmFmdC1rdWVobGV3aW5kLXF1aWMtcHJveHktZGlzY292ZXJ5LTAwLnR4dDwv
c3Bhbj48c3BhbiBsYW5nPSJERSI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0Oi41aW4iPg0KPHNwYW4gbGFuZz0i
REUiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1h
cmdpbi1ib3R0b20tYWx0OmF1dG87bWFyZ2luLWxlZnQ6LjVpbiI+DQo8c3BhbiBsYW5nPSJERSI+
VGhhbmtzIGZvciBzaGFyaW5nIHRoaXMuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0Oi41aW4iPg0KPHNwYW4gbGFu
Zz0iREUiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0bzttYXJnaW4tbGVmdDouNWluIj4NCjxzcGFuIGxhbmc9IkRFIj5JIHdv
bmRlciBpZiB5b3UgY29uc2lkZXJlZCBXUEFEIChXZWIgUHJveHkgQXV0b2Rpc2NvdmVyeSkgb3Ig
UEFDIChQcm94eSBhdXRvLWNvbmZpZyk/IEFsdGhvdWdoIHRhcmdldHRlZCBhdCB0aGUgYXBwbGlj
YXRpb24gbGF5ZXIsIGl0IG1pZ2h0IGhlbHAgdG8gY29tbWVudCBvbiBob3cgdGhvc2UgZm9ybXMg
b2YgZGlzY292ZXJ5IHdvdWxkIHJlbGF0ZSB0byB0aGUgbWV0aG9kcyBvdXRsaW5lZCBpbiB5b3Vy
IGRyYWZ0LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRv
bS1hbHQ6YXV0bzttYXJnaW4tbGVmdDouNWluIj4NCjxzcGFuIGxhbmc9IkRFIj4mbmJzcDs8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87
bWFyZ2luLWxlZnQ6LjVpbiI+DQo8c3BhbiBsYW5nPSJERSI+Q2hlZXJzLDxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzttYXJnaW4tbGVm
dDouNWluIj4NCjxzcGFuIGxhbmc9IkRFIj5MdWNhczxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3At
YWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87bWFyZ2luLWxlZnQ6LjVpbiI+DQo8
c3BhbiBsYW5nPSJERSI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG87bWFyZ2luLWxlZnQ6LjVpbiI+DQo8c3BhbiBsYW5nPSJE
RSI+T24gTW9uLCBOb3YgNCwgMjAxOSBhdCA0OjU4IFBNIE1pcmphIEt1ZWhsZXdpbmQgJmx0O21p
cmphLmt1ZWhsZXdpbmQ9PGEgaHJlZj0ibWFpbHRvOjQwZXJpY3Nzb24uY29tQGRtYXJjLmlldGYu
b3JnIiB0YXJnZXQ9Il9ibGFuayI+NDBlcmljc3Nvbi5jb21AZG1hcmMuaWV0Zi5vcmc8L2E+Jmd0
OyB3cm90ZTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxl
PSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCB3aW5kb3d0ZXh0IDEuMHB0O3BhZGRpbmc6
MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXRvcDo1LjBwdDttYXJn
aW4tcmlnaHQ6MGluO21hcmdpbi1ib3R0b206NS4wcHQ7Ym9yZGVyLWNvbG9yOmN1cnJlbnRjb2xv
ciBjdXJyZW50Y29sb3IgY3VycmVudGNvbG9yIHJnYigyMDQsMjA0LDIwNCkiPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvO21hcmdpbi1sZWZ0Oi41aW4iPg0KPHNwYW4gbGFuZz0iREUiPkhpIGFsbCw8
YnI+DQo8YnI+DQp3ZSBzdWJtaXR0ZWQgYSBuZXcgZHJhZnQgdGhhdCBsaXN0cyBkaXNjb3Zlcnkg
bWVjaGFuaXNtcyBmb3IgUVVJQy1iYXNlZCBwcm94aWVzIChzZWUgYmVsb3cpLiBUaGlzIGlzIG9u
ZSBwaWVjZSBvZiB3b3JrIHRoYXQgaXMgbmVlZGVkIGZvciBtb3N0IG9mIHRoZSB1c2UgY2FzZXMg
aW4gZHJhZnQta3VlaGxld2luZC1xdWljLXN1YnN0cmF0ZS4NCjxicj4NCjxicj4NCkxldCBtZSBr
bm93IGlmIHlvdSBoYXZlIGFueSBxdWVzdGlvbnMgb3IgY29tbWVudHMhPGJyPg0KPGJyPg0KTWly
amE8YnI+DQo8YnI+DQo8YnI+DQpPbiAwNC4xMS4xOSwgMTc6NTMsICZxdW90OzxhIGhyZWY9Im1h
aWx0bzppbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmciIHRhcmdldD0iX2JsYW5rIj5pbnRlcm5ldC1k
cmFmdHNAaWV0Zi5vcmc8L2E+JnF1b3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86aW50ZXJuZXQtZHJh
ZnRzQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+aW50ZXJuZXQtZHJhZnRzQGlldGYub3JnPC9h
PiZndDsgd3JvdGU6PGJyPg0KPGJyPg0KPGJyPg0KJm5ic3A7ICZuYnNwOyBBIG5ldyB2ZXJzaW9u
IG9mIEktRCwgZHJhZnQta3VlaGxld2luZC1xdWljLXByb3h5LWRpc2NvdmVyeS0wMC50eHQ8YnI+
DQombmJzcDsgJm5ic3A7IGhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkgTWlyamEg
S3VlaGxld2luZCBhbmQgcG9zdGVkIHRvIHRoZTxicj4NCiZuYnNwOyAmbmJzcDsgSUVURiByZXBv
c2l0b3J5Ljxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgTmFtZTombmJzcDsgJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ZHJhZnQta3VlaGxld2luZC1xdWlj
LXByb3h5LWRpc2NvdmVyeTxicj4NCiZuYnNwOyAmbmJzcDsgUmV2aXNpb246Jm5ic3A7ICZuYnNw
OzAwPGJyPg0KJm5ic3A7ICZuYnNwOyBUaXRsZTombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgRGlzY292ZXJ5IE1lY2hhbmlzbSBmb3IgUVVJQy1iYXNlZCwg
Tm9uLXRyYW5zcGFyZW50IFByb3h5IFNlcnZpY2VzPGJyPg0KJm5ic3A7ICZuYnNwOyBEb2N1bWVu
dCBkYXRlOiZuYnNwOyAmbmJzcDsgJm5ic3A7IDIwMTktMTEtMDQ8YnI+DQombmJzcDsgJm5ic3A7
IEdyb3VwOiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBJ
bmRpdmlkdWFsIFN1Ym1pc3Npb248YnI+DQombmJzcDsgJm5ic3A7IFBhZ2VzOiZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAxMTxicj4NCiZuYnNwOyAmbmJz
cDsgVVJMOiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7IDxhIGhyZWY9
Imh0dHBzOi8vdXJsZGVmZW5zZS5jb20vdjMvX19odHRwczovd3d3LmlldGYub3JnL2ludGVybmV0
LWRyYWZ0cy9kcmFmdC1rdWVobGV3aW5kLXF1aWMtcHJveHktZGlzY292ZXJ5LTAwLnR4dF9fOyEw
ckx4bmM1b2g0cyFqUG9zUXQyNkVhalNjZ1V1cG9pQ0lNS090dTFldTlSMHRnMkNFa01YTnE4Q3g1
NnNDbWtMN1BtSTlQUDZmT3RGZnckIiB0YXJnZXQ9Il9ibGFuayI+DQpodHRwczovL3d3dy5pZXRm
Lm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQta3VlaGxld2luZC1xdWljLXByb3h5LWRpc2NvdmVy
eS0wMC50eHQ8L2E+PGJyPg0KJm5ic3A7ICZuYnNwOyBTdGF0dXM6Jm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwOzxhIGhyZWY9Imh0dHBzOi8vdXJsZGVmZW5zZS5jb20vdjMvX19odHRw
czovZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWt1ZWhsZXdpbmQtcXVpYy1wcm94eS1k
aXNjb3ZlcnkvX187ITByTHhuYzVvaDRzIWpQb3NRdDI2RWFqU2NnVXVwb2lDSU1LT3R1MWV1OVIw
dGcyQ0VrTVhOcThDeDU2c0Nta0w3UG1JOVBOaXJKQm5LUSQiIHRhcmdldD0iX2JsYW5rIj5odHRw
czovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1rdWVobGV3aW5kLXF1aWMtcHJveHkt
ZGlzY292ZXJ5LzwvYT48YnI+DQombmJzcDsgJm5ic3A7IEh0bWxpemVkOiZuYnNwOyAmbmJzcDsg
Jm5ic3A7ICZuYnNwOzxhIGhyZWY9Imh0dHBzOi8vdXJsZGVmZW5zZS5jb20vdjMvX19odHRwczov
dG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1rdWVobGV3aW5kLXF1aWMtcHJveHktZGlzY292ZXJ5
LTAwX187ITByTHhuYzVvaDRzIWpQb3NRdDI2RWFqU2NnVXVwb2lDSU1LT3R1MWV1OVIwdGcyQ0Vr
TVhOcThDeDU2c0Nta0w3UG1JOVBOdDJsaldWUSQiIHRhcmdldD0iX2JsYW5rIj5odHRwczovL3Rv
b2xzLmlldGYub3JnL2h0bWwvZHJhZnQta3VlaGxld2luZC1xdWljLXByb3h5LWRpc2NvdmVyeS0w
MDwvYT48YnI+DQombmJzcDsgJm5ic3A7IEh0bWxpemVkOiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwOzxhIGhyZWY9Imh0dHBzOi8vdXJsZGVmZW5zZS5jb20vdjMvX19odHRwczovZGF0YXRyYWNr
ZXIuaWV0Zi5vcmcvZG9jL2h0bWwvZHJhZnQta3VlaGxld2luZC1xdWljLXByb3h5LWRpc2NvdmVy
eV9fOyEwckx4bmM1b2g0cyFqUG9zUXQyNkVhalNjZ1V1cG9pQ0lNS090dTFldTlSMHRnMkNFa01Y
TnE4Q3g1NnNDbWtMN1BtSTlQTkxrb3d3UHckIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly9kYXRh
dHJhY2tlci5pZXRmLm9yZy9kb2MvaHRtbC9kcmFmdC1rdWVobGV3aW5kLXF1aWMtcHJveHktZGlz
Y292ZXJ5PC9hPjxicj4NCjxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgQWJzdHJhY3Q6PGJyPg0K
Jm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7T2Z0ZW4gYW4gaW50ZXJtZWRpYXRlIGluc3RhbmNl
IChzdWNoIGFzIGEgcHJveHkgc2VydmVyKSBpcyB1c2VkIHRvPGJyPg0KJm5ic3A7ICZuYnNwOyAm
bmJzcDsgJm5ic3A7Y29ubmVjdCB0byBhIHdlYiBzZXJ2ZXIgb3IgYSBjb21tdW5pY2F0aW5nIHBl
ZXIgaWYgYSBkaXJlY3QgZW5kLXRvLTxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO2Vu
ZCBJUCBjb25uZWN0aXZpdHkgaXMgbm90IHBvc3NpYmxlIG9yIHRoZSBwcm94eSBjYW4gcHJvdmlk
ZSBhPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7c3VwcG9ydCBzZXJ2aWNlIGxpa2Us
IGUuZy4sIGFkZHJlc3MgYW5vbnltaXNhdGlvbi4mbmJzcDsgVG8gdXNlIGEgbm9uLTxicj4NCiZu
YnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO3RyYW5zcGFyZW50IHByb3h5IGEgY2xpZW50IGV4cGxp
Y2l0bHkgY29ubmVjdHMgdG8gaXQgYW5kIHJlcXVlc3RzPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJz
cDsgJm5ic3A7Zm9yd2FyZGluZyB0byB0aGUgZmluYWwgdGFyZ2V0IHNlcnZlci4mbmJzcDsgVGhl
IGNsaWVudCBlaXRoZXIga25vd3MgdGhlPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7
cHJveHkgYWRkcmVzcyBhcyBwcmVjb25maWd1cmVkIGluIHRoZSBhcHBsaWNhdGlvbiBvciBjYW4g
ZHluYW1pY2FsbHk8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtsZWFybiBhYm91dCBh
dmFpbGFibGUgcHJveHkgc2VydmljZXMuJm5ic3A7IFRoaXMgZG9jdW1lbnQgZGVzY3JpYmVzPGJy
Pg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ZGlmZmVyZW50IGRpc2NvdmVyeSBtZWNoYW5p
c21zIGZvciBub24tdHJhbnNwYXJlbnQgcHJveGllcyB0aGF0IGFyZTxicj4NCiZuYnNwOyAmbmJz
cDsgJm5ic3A7ICZuYnNwO2VpdGhlciBsb2NhdGVkIGluIHRoZSBsb2NhbCBuZXR3b3JrLCBlLmcu
IGhvbWUgb3IgZW50ZXJwcmlzZSBuZXR3b3JrLDxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZu
YnNwO2luIHRoZSBhY2Nlc3MgbmV0d29yaywgb3Igc29tZXdoZXJlIGVsc2Ugb24gdGhlIEludGVy
bmV0IHVzdWFsbHk8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtjbG9zZSB0byB0aGUg
dGFyZ2V0IHNlcnZlciBvciBldmVuIGluIHRoZSBzYW1lIG5ldHdvcmsgYXMgdGhlIHRhcmdldDxi
cj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwO3NlcnZlci48YnI+DQo8YnI+DQombmJzcDsg
Jm5ic3A7ICZuYnNwOyAmbmJzcDtUaGlzIGRvY3VtZW50IGFzc3VtZXMgdGhhdCB0aGUgbm9uLXRy
YW5zcGFyZW50IHByb3h5IHNlcnZlciBpczxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNw
O2Nvbm5lY3RlZCB2aWEgUVVJQyBhbmQgZGlzY3Vzc2VzIHBvdGVudGlhbCBkaXNjb3ZlcnkgbWVj
aGFuaXNtcyBmb3I8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDtzdWNoIGEgUVVJQy1i
YXNlZCwgbm9uLXRyYW5zcGFyZW50IHByb3h5Ljxicj4NCjxicj4NCjxicj4NCjxicj4NCjxicj4N
CiZuYnNwOyAmbmJzcDsgUGxlYXNlIG5vdGUgdGhhdCBpdCBtYXkgdGFrZSBhIGNvdXBsZSBvZiBt
aW51dGVzIGZyb20gdGhlIHRpbWUgb2Ygc3VibWlzc2lvbjxicj4NCiZuYnNwOyAmbmJzcDsgdW50
aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWlsYWJsZSBhdCA8YSBocmVm
PSJodHRwczovL3VybGRlZmVuc2UuY29tL3YzL19faHR0cDovdG9vbHMuaWV0Zi5vcmdfXzshMHJM
eG5jNW9oNHMhalBvc1F0MjZFYWpTY2dVdXBvaUNJTUtPdHUxZXU5UjB0ZzJDRWtNWE5xOEN4NTZz
Q21rTDdQbUk5UE5RaDdOa3VBJCIgdGFyZ2V0PSJfYmxhbmsiPg0KdG9vbHMuaWV0Zi5vcmc8L2E+
Ljxicj4NCjxicj4NCiZuYnNwOyAmbmJzcDsgVGhlIElFVEYgU2VjcmV0YXJpYXQ8YnI+DQo8YnI+
DQo8YnI+DQo8YnI+DQotLSA8YnI+DQpNYXNxdWUgbWFpbGluZyBsaXN0PGJyPg0KPGEgaHJlZj0i
bWFpbHRvOk1hc3F1ZUBpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPk1hc3F1ZUBpZXRmLm9yZzwv
YT48YnI+DQo8YSBocmVmPSJodHRwczovL3VybGRlZmVuc2UuY29tL3YzL19faHR0cHM6L3d3dy5p
ZXRmLm9yZy9tYWlsbWFuL2xpc3RpbmZvL21hc3F1ZV9fOyEwckx4bmM1b2g0cyFqUG9zUXQyNkVh
alNjZ1V1cG9pQ0lNS090dTFldTlSMHRnMkNFa01YTnE4Q3g1NnNDbWtMN1BtSTlQTzRJNkFwZHck
IiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9t
YXNxdWU8L2E+PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8
L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwv
aHRtbD4NCg==

--_000_SN6PR11MB3087D25371090E7E40FA32B2CE7F0SN6PR11MB3087namp_--


From nobody Mon Nov  4 12:41:20 2019
Return-Path: <tpauly@apple.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 6AC8112002E for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 12:41:18 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7
X-Spam-Level: 
X-Spam-Status: No, score=-7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, 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=apple.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 OmgKyRZ29_hz for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 12:41:17 -0800 (PST)
Received: from ma1-aaemail-dr-lapp02.apple.com (ma1-aaemail-dr-lapp02.apple.com [17.171.2.68]) (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 D371A120018 for <quic@ietf.org>; Mon,  4 Nov 2019 12:41:16 -0800 (PST)
Received: from pps.filterd (ma1-aaemail-dr-lapp02.apple.com [127.0.0.1]) by ma1-aaemail-dr-lapp02.apple.com (8.16.0.27/8.16.0.27) with SMTP id xA4KajrN034533; Mon, 4 Nov 2019 12:41:14 -0800
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=apple.com; h=sender : from : message-id : content-type : mime-version : subject : date : in-reply-to : cc : to : references; s=20180706; bh=Y4fJQlxfUM4+OYXqItA7RC1GN7GZynxV5QEiRMllQ08=; b=IyMygh5Ra99+0kB/j9EAQD9fqKe5/Za974EGU2C+D3CkkqR6YUfDCTq2e9n+Rrf+7Ky5 ouVRYTAS8BqssAoVbTWV2x6xdZu7ZgNYMwghFrNg+QRR02/Q5moibxeUMZsFh8VpeAw9 s1EduxFH6N+Vvx/bmYDn4UzpbhcJvqepBar0ufFWiJmsuu+QDTVL4oFGbhRqJUVyzDu0 8T+Q33gTQb+UQj4o2BEPg1NkSuc84DY0izmaG9gLicDuyT3r/kjSC95Zu/+7Xd7UgvU8 qHiz4YpnoHbPhi0cKW5RlbMAdlk2zZC1GXK1AtfODpo2dcRTtUWNZpk61qjZvgegbKNA tw== 
Received: from mr2-mtap-s01.rno.apple.com (mr2-mtap-s01.rno.apple.com [17.179.226.133]) by ma1-aaemail-dr-lapp02.apple.com with ESMTP id 2w16ftptxb-2 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128 verify=NO); Mon, 04 Nov 2019 12:41:14 -0800
Received: from nwk-mmpp-sz12.apple.com (nwk-mmpp-sz12.apple.com [17.128.115.204]) by mr2-mtap-s01.rno.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May  7 2019)) with ESMTPS id <0Q0G00N8NPGQ2KA0@mr2-mtap-s01.rno.apple.com>; Mon, 04 Nov 2019 12:41:14 -0800 (PST)
Received: from process_milters-daemon.nwk-mmpp-sz12.apple.com by nwk-mmpp-sz12.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May  7 2019)) id <0Q0G00B00P36Z700@nwk-mmpp-sz12.apple.com>; Mon, 04 Nov 2019 12:41:14 -0800 (PST)
X-Va-A: 
X-Va-T-CD: fd7fa2cf43a24f878f649a9cdf606cb8
X-Va-E-CD: 66b6aa0fce50738e37fdc0243428133e
X-Va-R-CD: a9cadcb32177681a04248ce6c161c5f1
X-Va-CD: 0
X-Va-ID: 35403bd1-c961-4f7d-8f24-1a39ecfbbf2a
X-V-A: 
X-V-T-CD: fd7fa2cf43a24f878f649a9cdf606cb8
X-V-E-CD: 66b6aa0fce50738e37fdc0243428133e
X-V-R-CD: a9cadcb32177681a04248ce6c161c5f1
X-V-CD: 0
X-V-ID: 1344633f-fa0f-420b-a59a-384a7504ab2b
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2019-11-04_11:,, signatures=0
Received: from [17.230.5.121] by nwk-mmpp-sz12.apple.com (Oracle Communications Messaging Server 8.0.2.4.20190507 64bit (built May  7 2019)) with ESMTPSA id <0Q0G002KLPGPRA90@nwk-mmpp-sz12.apple.com>; Mon, 04 Nov 2019 12:41:14 -0800 (PST)
Sender: tpauly@apple.com
From: Tommy Pauly <tpauly@apple.com>
Message-id: <540E0152-57EA-4B96-8E8E-F07143CD8A58@apple.com>
Content-type: multipart/alternative; boundary="Apple-Mail=_42479E83-94F7-4916-B419-830321BEAD20"
MIME-version: 1.0 (Mac OS X Mail 13.0 \(3594.4.17\))
Subject: Re: Alternate Version + Salt in Alt-Svc
Date: Mon, 04 Nov 2019 12:41:12 -0800
In-reply-to: <CAJ_4DfTN-25ZpDmGBFXxmz9RZCT=8JbpFoDX71eyhE1rEtPkMg@mail.gmail.com>
Cc: IETF QUIC WG <quic@ietf.org>
To: Ryan Hamilton <rch=40google.com@dmarc.ietf.org>
References: <CAJ_4DfTN-25ZpDmGBFXxmz9RZCT=8JbpFoDX71eyhE1rEtPkMg@mail.gmail.com>
X-Mailer: Apple Mail (2.3594.4.17)
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-11-04_11:, , signatures=0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/3Ry0t4Zd9AxEyE274zWUmO90Lfs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 20:41:19 -0000

--Apple-Mail=_42479E83-94F7-4916-B419-830321BEAD20
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

I do think that this privacy concern is a valid issue to think about and =
try to mitigate, or at least reduce in scope. Good to discuss!

Clients could of course choose to not use a version received via Alt-Svc =
when they don't want to be linked (in which case they would also not =
want to do 0-RTT, etc). So there could be guidance on when to use these =
versions. That may reduce the amount that the alternate version gets =
used, though; and even end up causing failures only of some categories =
of connections.

Another way out here is to use the Alt-Svc value that comes from another =
source, like the proposal in HTTPSSVC. That would be harder to target =
users with.

Best,
Tommy

> On Nov 4, 2019, at 12:34 PM, Ryan Hamilton =
<rch=3D40google.com@dmarc.ietf.org> wrote:
>=20
> Howdy Folks,
>=20
> We've discussed the idea of attempting to reduce ossification by =
allowing the server to deliver an alternative version and initial salt =
to the client which can be used to speak "QUIC v1". One such mechanism =
for delivering this version to the client is Alt-Svc. In the context of =
HTTP/3 this has the wonderful property that even the first connection =
from a client to the server can use this alternative version.
>=20
> However, it seems that there might be a privacy/linkability issue with =
this approach that I'm curious to get the groups' take on. If this =
information were delivered via Alt-Svc, I would imagine that the na=C3=AFv=
e implementation would be to cache the Alt-Svc info as until it expires =
(via the ma=3D attribute) and use the alternative version/salt in each =
subsequent QUIC connection. Since the version field is 32 bits, that =
potentially allows each user to use a distinct version. This is great =
for anti-ossification, but seems problematic for linkability/privacy.
>=20
> I can think of solutions/mitigations for this issue (like restricting =
the number of bits which can be flipped by the server, or expiring the =
alternative version in the client on first use, etc) but I'd be curious =
if this seems like an issue to other folks first.
>=20
> Cheers,
>=20
> Ryan


--Apple-Mail=_42479E83-94F7-4916-B419-830321BEAD20
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
	charset=utf-8

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; =
charset=3Dutf-8"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; line-break: after-white-space;" class=3D"">I =
do think that this privacy concern is a valid issue to think about and =
try to mitigate, or at least reduce in scope. Good to discuss!<div =
class=3D""><br class=3D""></div><div class=3D"">Clients could of course =
choose to not use a version received via Alt-Svc when they don't want to =
be linked (in which case they would also not want to do 0-RTT, etc). So =
there could be guidance on when to use these versions. That may reduce =
the amount that the alternate version gets used, though; and even end up =
causing failures only of some categories of connections.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Another way out here is =
to use the Alt-Svc value that comes from another source, like the =
proposal in HTTPSSVC. That would be harder to target users =
with.</div><div class=3D""><br class=3D""></div><div =
class=3D"">Best,</div><div class=3D"">Tommy<br class=3D""><div><br =
class=3D""><blockquote type=3D"cite" class=3D""><div class=3D"">On Nov =
4, 2019, at 12:34 PM, Ryan Hamilton &lt;<a =
href=3D"mailto:rch=3D40google.com@dmarc.ietf.org" =
class=3D"">rch=3D40google.com@dmarc.ietf.org</a>&gt; wrote:</div><br =
class=3D"Apple-interchange-newline"><div class=3D""><div dir=3D"ltr" =
class=3D""><div class=3D"gmail_default" style=3D"font-family:trebuchet =
ms,sans-serif">Howdy Folks,<br class=3D""></div><div =
class=3D"gmail_default" style=3D"font-family:trebuchet =
ms,sans-serif"><br class=3D""></div><div class=3D"gmail_default" =
style=3D"font-family:trebuchet ms,sans-serif">We've discussed the idea =
of attempting to reduce ossification by allowing the server to deliver =
an alternative version and initial salt to the client which can be used =
to speak "QUIC v1". One such mechanism for delivering this version to =
the client is Alt-Svc. In the context of HTTP/3 this has the wonderful =
property that even the first connection from a client to the server can =
use this alternative version.</div><div class=3D"gmail_default" =
style=3D"font-family:trebuchet ms,sans-serif"><br class=3D""></div><div =
class=3D"gmail_default" style=3D"font-family:trebuchet =
ms,sans-serif">However, it seems that there might be a =
privacy/linkability issue with this approach that I'm curious to get the =
groups' take on. If this information were delivered via Alt-Svc, I would =
imagine that the na=C3=AFve implementation would be to cache the Alt-Svc =
info as until it expires (via the ma=3D attribute) and use the =
alternative version/salt in each subsequent QUIC connection. Since the =
version field is 32 bits, that potentially allows each user to use a =
distinct version. This is great for anti-ossification, but seems =
problematic&nbsp;for linkability/privacy.</div><div =
class=3D"gmail_default" style=3D"font-family:trebuchet =
ms,sans-serif"><br class=3D""></div><div class=3D"gmail_default" =
style=3D"font-family:trebuchet ms,sans-serif">I can think of =
solutions/mitigations for this issue (like restricting the number of =
bits which can be flipped by the server, or expiring the alternative =
version in the client on first use, etc) but I'd be curious if this =
seems like an issue to other folks first.</div><div =
class=3D"gmail_default" style=3D"font-family:trebuchet =
ms,sans-serif"><br class=3D""></div><div class=3D"gmail_default" =
style=3D"font-family:trebuchet ms,sans-serif">Cheers,</div><div =
class=3D"gmail_default" style=3D"font-family:trebuchet =
ms,sans-serif"><br class=3D""></div><div class=3D"gmail_default" =
style=3D"font-family:trebuchet ms,sans-serif">Ryan</div></div>
</div></blockquote></div><br class=3D""></div></body></html>=

--Apple-Mail=_42479E83-94F7-4916-B419-830321BEAD20--


From nobody Mon Nov  4 13:36:58 2019
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 1EB8C120836 for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 13:36:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level: 
X-Spam-Status: No, score=-1.996 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_HELO_NONE=0.001, 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 oETa0ufHMMWr for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 13:36:48 -0800 (PST)
Received: from mail-ed1-x535.google.com (mail-ed1-x535.google.com [IPv6:2a00:1450:4864:20::535]) (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 EE8C212002E for <quic@ietf.org>; Mon,  4 Nov 2019 13:36:47 -0800 (PST)
Received: by mail-ed1-x535.google.com with SMTP id b72so14409233edf.1 for <quic@ietf.org>; Mon, 04 Nov 2019 13:36:47 -0800 (PST)
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=B4ruVr/fKSzgbI+Fmv5LtJLLsn+hoZH4P5ulS5wUHKo=; b=TVj8PTdYNO9RZhafQE+v2EFDXjAirNa+3q45+IrxK1L0g15ZnhDmx9vLjz8eSM1AD5 voV82Uufc6LEHB/pyJfQLOlzsu/zJBwBRCLO1lvHA8WjGQc6yt96Dt6JKdx1KgHazs1K wWy2DRZDkSID1ZIGHaR1ZXjoZOge87qNzTO6NNz08ZoNz/IB6kCQF3UbKfvDxZBCg5iA cfRctIYqKOzImSGm8v6YYm5krajUrGpAfBIv0jHnDeTZXyyq4ycBFcOGJrgHiNM8O5i1 VvUIlA3RhLPW9suniBaZZohXWGczRX50AS9HpjnQqX/49I8iCWwN+ocydCA76zWW7Bqi kSHg==
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=B4ruVr/fKSzgbI+Fmv5LtJLLsn+hoZH4P5ulS5wUHKo=; b=XFnCF3XlZ1s9zGJ19Nl5mpDohMlZ3jhk4D1jnb56H+Pl/u44hnwat5ZA23nyQPCVp0 uRCn59L5sk9nNd/kLGadM2460TMrhgkT58lohv+pkNIqRistnjZwosRBP8sLJzWK9VZ7 RFEcxaQ9nw1Ea9LS1di6fIs22GWxEdD7P55o4jLv6yn4FdUZgcUKqHWH+d2wfFOVfXgV RAeusG7XEUak4rzEi9I1lwngkTZpff6kL4UEzB8oYcxpEwafAi6WE5BPZ51ucQLp9pVu /4hmctqEIt8M2J3IF6nDq+tjv4gHbRUFAaYkkKZd0FTJnO9Fb73LZBEZonGY7E/uprdr GZLw==
X-Gm-Message-State: APjAAAU//nUAZpt1nXjT5n9mOMBfXnhOEf9l+b/D+TNFoje0wIkX6FaB QheCZAREiRcHGjJAtu7Sr21+MMPzbyqNk14Sz51ikGTH
X-Google-Smtp-Source: APXvYqxlUh7oG6ZPp3dowJSlT922Wqr6KZeMZ1q1l6OdMRpUe0UFWDR3cvnztiljMQJUowYbffYbz91nRjeKOnAiupQ=
X-Received: by 2002:a05:6402:512:: with SMTP id m18mr30667819edv.250.1572903406356;  Mon, 04 Nov 2019 13:36:46 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Mon, 4 Nov 2019 13:36:45 -0800
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <540E0152-57EA-4B96-8E8E-F07143CD8A58@apple.com>
References: <CAJ_4DfTN-25ZpDmGBFXxmz9RZCT=8JbpFoDX71eyhE1rEtPkMg@mail.gmail.com> <540E0152-57EA-4B96-8E8E-F07143CD8A58@apple.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Mon, 4 Nov 2019 13:36:45 -0800
Message-ID: <CAN1APdeykg0icmjQ7dx1_AthGxLvPwe9_O6hGFQMEe_zKn9bgg@mail.gmail.com>
Subject: Re: Alternate Version + Salt in Alt-Svc
To: Tommy Pauly <tpauly=40apple.com@dmarc.ietf.org>,  Ryan Hamilton <rch=40google.com@dmarc.ietf.org>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cd4e9a05968c1cf4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/3q8YQpn-sSOKds3WgdU503X_cWk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 21:36:57 -0000

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

Some random observations reading through the document

- Is the order relevant in the receiver version list?

- It is tempting to just hash the received version list, but that requires
agreeing on an algorithm, unless the algorithm is stated to be specific to
that version, which is complicated.

- VERSION_NEGOTIATION_ERROR vs drop - I=E2=80=99m not sure it is a good ide=
a to
close the connection. The initials are public so it is possible to inject
false versions. There are probably many other similar attacks we don=E2=80=
=99t
bother with, but still =E2=80=A6

- Checking that a transport parameter field is the same as the long header
version seems redundant - why have those fields? Is it because the Initial
header fields are not sufficiently protected via TLS magic (or similar)?

- We generally use varint, but why have varints mixed with 32-bit version
lists? I suggest making the list length 32-bit for easier processing.

- Downgrade - I=E2=80=99m a bit worried about state management and server
redeployments. A server could reject a valid packet because an Initial was
routed to a new server. (Reading further, I see this is addressed). This is
probably a pragmatic solution, but it has an assumption about eventual
global coordination. I suspect something could be done here with tokens or
CID routing, but it is not trivial.

- Security Considerations - perhaps it is worth noting the transport
parameters need additional protection beyond the Initial packet protection?
This follows from TLS, but if TLS is not being used, this can version
negotiation even if other parts of the protocol version is not sensitive to
this in that particular version.

- Greasing 0x?a?a?a?a - I=E2=80=99m not really sure about the point of this=
.
Especially if we get salted versions in separate proposal.

- It is not immediately obvious if version negotiation can go on and on, or
if it settles after at most one roundtrip one way or the other. This might
depend on the client QUIC version, but that is a fuzzy term in this context=
.

- Improve discussion of Previously Attempted Version. While the
requirements are readable, the purpose of doing this check is less obvious.
Presumably this deals with downgrade attacks, but more explanation would be
appreciated.

Mikkel

On 4 November 2019 at 21.41.30, Tommy Pauly (
tpauly=3D40apple.com@dmarc.ietf.org) wrote:

I do think that this privacy concern is a valid issue to think about and
try to mitigate, or at least reduce in scope. Good to discuss!

Clients could of course choose to not use a version received via Alt-Svc
when they don't want to be linked (in which case they would also not want
to do 0-RTT, etc). So there could be guidance on when to use these
versions. That may reduce the amount that the alternate version gets used,
though; and even end up causing failures only of some categories of
connections.

Another way out here is to use the Alt-Svc value that comes from another
source, like the proposal in HTTPSSVC. That would be harder to target users
with.

Best,
Tommy

On Nov 4, 2019, at 12:34 PM, Ryan Hamilton <rch=3D40google.com@dmarc.ietf.o=
rg>
wrote:

Howdy Folks,

We've discussed the idea of attempting to reduce ossification by allowing
the server to deliver an alternative version and initial salt to the client
which can be used to speak "QUIC v1". One such mechanism for delivering
this version to the client is Alt-Svc. In the context of HTTP/3 this has
the wonderful property that even the first connection from a client to the
server can use this alternative version.

However, it seems that there might be a privacy/linkability issue with this
approach that I'm curious to get the groups' take on. If this information
were delivered via Alt-Svc, I would imagine that the na=C3=AFve implementat=
ion
would be to cache the Alt-Svc info as until it expires (via the ma=3D
attribute) and use the alternative version/salt in each subsequent QUIC
connection. Since the version field is 32 bits, that potentially allows
each user to use a distinct version. This is great for anti-ossification,
but seems problematic for linkability/privacy.

I can think of solutions/mitigations for this issue (like restricting the
number of bits which can be flipped by the server, or expiring the
alternative version in the client on first use, etc) but I'd be curious if
this seems like an issue to other folks first.

Cheers,

Ryan

--000000000000cd4e9a05968c1cf4
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 random observat=
ions reading through the document</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;lin=
e-height:auto">- Is the order relevant in the receiver version list?</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;c=
olor:rgba(0,0,0,1.0);margin:0px;line-height:auto">- It is tempting to just =
hash the received version list, but that requires agreeing on an algorithm,=
 unless the algorithm is stated to be specific to that version, which is co=
mplicated.</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"><b=
r></div><div id=3D"bloop_customfont" style=3D"margin:0px">-=C2=A0<span styl=
e=3D"orphans: 2; widows: 2;"><font size=3D"3">VERSION_NEGOTIATION_ERROR vs =
drop - I=E2=80=99m not sure it is a good idea to close the connection. The =
initials are public so it is possible to inject false versions. There are p=
robably many other similar attacks we don=E2=80=99t bother with, but still=
=C2=A0</font></span><font size=3D"3">=E2=80=A6</font></div><div id=3D"bloop=
_customfont" style=3D"margin:0px"><span style=3D"orphans: 2; widows: 2;"><f=
ont size=3D"3"><br></font></span></div><div id=3D"bloop_customfont" style=
=3D"margin:0px"><span style=3D"orphans: 2; widows: 2;"><font size=3D"3">- C=
hecking that a transport parameter field is the same as the long header ver=
sion seems redundant - why have those fields? Is it because the Initial hea=
der fields are not sufficiently protected via TLS magic (or similar)?</font=
></span></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">- We general=
ly use varint, but why have varints mixed with 32-bit version lists? I sugg=
est making the list length 32-bit for easier processing.</div><div id=3D"bl=
oop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;color:r=
gba(0,0,0,1.0);margin:0px;line-height:auto"><br></div> <div>- Downgrade - I=
=E2=80=99m a bit worried about state management and server redeployments. A=
 server could reject a valid packet because an Initial was routed to a new =
server. (Reading further, I see this is addressed). This is probably a prag=
matic solution, but it has an assumption about eventual global coordination=
. I suspect something could be done here with tokens or CID routing, but it=
 is not trivial.</div><div><br></div>- Security Considerations - perhaps it=
 is worth noting the transport parameters need additional protection beyond=
 the Initial packet protection? This follows from TLS, but if TLS is not be=
ing used, this can version negotiation even if other parts of the protocol =
version is not sensitive to this in that particular version.<div><br><div>-=
 Greasing 0x?a?a?a?a - I=E2=80=99m not really sure about the point of this.=
 Especially if we get salted versions in separate proposal.</div><div><br><=
/div><div>- It is not immediately obvious if version negotiation can go on =
and on, or if it settles after at most one roundtrip one way or the other. =
This might depend on the client QUIC version, but that is a fuzzy term in t=
his context.</div><div><br></div><div>- Improve discussion of Previously At=
tempted Version. While the requirements are readable, the purpose of doing =
this check is less obvious. Presumably this deals with downgrade attacks, b=
ut more explanation would be appreciated.</div><div><br></div><div>Mikkel<b=
r> <br><p class=3D"airmail_on">On 4 November 2019 at 21.41.30, Tommy Pauly =
(<a href=3D"mailto:tpauly=3D40apple.com@dmarc.ietf.org">tpauly=3D40apple.co=
m@dmarc.ietf.org</a>) wrote:</p> <blockquote type=3D"cite" class=3D"clean_b=
q"><span><div style=3D"word-wrap:break-word;line-break:after-white-space" c=
lass=3D""><div></div><div>



<title></title>


I do think that this privacy concern is a valid issue to think
about and try to mitigate, or at least reduce in scope. Good to
discuss!
<div class=3D""><br class=3D""></div>
<div class=3D"">Clients could of course choose to not use a version
received via Alt-Svc when they don&#39;t want to be linked (in which
case they would also not want to do 0-RTT, etc). So there could be
guidance on when to use these versions. That may reduce the amount
that the alternate version gets used, though; and even end up
causing failures only of some categories of connections.</div>
<div class=3D""><br class=3D""></div>
<div class=3D"">Another way out here is to use the Alt-Svc value that
comes from another source, like the proposal in HTTPSSVC. That
would be harder to target users with.</div>
<div class=3D""><br class=3D""></div>
<div class=3D"">Best,</div>
<div class=3D"">Tommy<br class=3D"">
<div><br class=3D"">
<blockquote type=3D"cite" class=3D"">
<div class=3D"">On Nov 4, 2019, at 12:34 PM, Ryan Hamilton
&lt;<a href=3D"mailto:rch=3D40google.com@dmarc.ietf.org" class=3D"">rch=3D4=
0google.com@dmarc.ietf.org</a>&gt; wrote:</div>
<br class=3D"Apple-interchange-newline">
<div class=3D"">
<div dir=3D"ltr" class=3D"">
<div class=3D"gmail_default" style=3D"font-family:trebuchet ms,sans-serif">=
Howdy Folks,<br class=3D""></div>
<div class=3D"gmail_default" style=3D"font-family:trebuchet ms,sans-serif">=
<br class=3D""></div>
<div class=3D"gmail_default" style=3D"font-family:trebuchet ms,sans-serif">=
We&#39;ve discussed the idea of
attempting to reduce ossification by allowing the server to deliver
an alternative version and initial salt to the client which can be
used to speak &quot;QUIC v1&quot;. One such mechanism for delivering this
version to the client is Alt-Svc. In the context of HTTP/3 this has
the wonderful property that even the first connection from a client
to the server can use this alternative version.</div>
<div class=3D"gmail_default" style=3D"font-family:trebuchet ms,sans-serif">=
<br class=3D""></div>
<div class=3D"gmail_default" style=3D"font-family:trebuchet ms,sans-serif">=
However, it seems that there
might be a privacy/linkability issue with this approach that I&#39;m
curious to get the groups&#39; take on. If this information were
delivered via Alt-Svc, I would imagine that the na=C3=AFve
implementation would be to cache the Alt-Svc info as until it
expires (via the ma=3D attribute) and use the alternative
version/salt in each subsequent QUIC connection. Since the version
field is 32 bits, that potentially allows each user to use a
distinct version. This is great for anti-ossification, but seems
problematic=C2=A0for linkability/privacy.</div>
<div class=3D"gmail_default" style=3D"font-family:trebuchet ms,sans-serif">=
<br class=3D""></div>
<div class=3D"gmail_default" style=3D"font-family:trebuchet ms,sans-serif">=
I can think of
solutions/mitigations for this issue (like restricting the number
of bits which can be flipped by the server, or expiring the
alternative version in the client on first use, etc) but I&#39;d be
curious if this seems like an issue to other folks first.</div>
<div class=3D"gmail_default" style=3D"font-family:trebuchet ms,sans-serif">=
<br class=3D""></div>
<div class=3D"gmail_default" style=3D"font-family:trebuchet ms,sans-serif">=
Cheers,</div>
<div class=3D"gmail_default" style=3D"font-family:trebuchet ms,sans-serif">=
<br class=3D""></div>
<div class=3D"gmail_default" style=3D"font-family:trebuchet ms,sans-serif">=
Ryan</div>
</div>
</div>
</blockquote>
</div>
<br class=3D""></div>


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

--000000000000cd4e9a05968c1cf4--


From nobody Mon Nov  4 13:43:19 2019
Return-Path: <mt@lowentropy.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 777A2120091 for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 13:43:06 -0800 (PST)
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=lowentropy.net header.b=ePogQO26; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=nnHTtF7T
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 dnW9ZnDLDqIQ for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 13:43:05 -0800 (PST)
Received: from wout2-smtp.messagingengine.com (wout2-smtp.messagingengine.com [64.147.123.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 139DE120121 for <quic@ietf.org>; Mon,  4 Nov 2019 13:43:05 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 79CB855C for <quic@ietf.org>; Mon,  4 Nov 2019 16:43:04 -0500 (EST)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Mon, 04 Nov 2019 16:43:04 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=rUWCdvK9ZULzN7mgKt57aybfPBRwd3B NBbpDetF1ZYY=; b=ePogQO267/X8GVuNLmWnGkd8iNe+dRUXd/fnPybQbjmjApd 7mJmiyZyO3m3Q1HwlDNjbW7zn8hjWKeMb/oej4Nkvb4C6rDhe42X5Ihs37EeO4dQ NqR3tzMjZTy7viur3PXww2jQ7fAdnK6Rj6R81eY1/W9gTWfdH2W6u6APY5F6hYQs VNqCXDiFFkwHhCf2vhtQNyD5rhVYu6glBTodUrrlVtPhOhzG9lm4hXCXeod81uNL ehGPu6KmGF5t4ufJXMIso/XKoK34G72k0jfguBF51A7Nwl9Wtx8+adLbKwWTaiXK 0+TmS1K9rOGCrF5vMVltuEqOXS2hO/oa3AUZArw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=rUWCdv K9ZULzN7mgKt57aybfPBRwd3BNBbpDetF1ZYY=; b=nnHTtF7TK/KhCSf7+ebhCV HR1uk4CeXP2todirfJsywudXNLdPp4ErGNnrkFyFZnvLl7ftLjTpl7KfqGW74SjP F7NyfJgdg3QeeT0NJw1IsFo8+u6jDU8E2JYlWu0aJiED3/czriaXmNWPmVcM4My9 IB4U7sDMzyowSmF4NnMBH5DKqVR2P6GnyjgMbsPGFJsq+A6KHrAgfUTCmsVhzUc4 VZ4zyz+gGFPHMsDlqGoOaXrkKPPhKMmKUW9t75FToTtuQjn+SWmpd1S00p9NGdx1 ab39jJaA+C2EmDOb9rqbs+OnMii48LK28P0rGg0LPYVMvBZxV9Y9Y60EEjFUDRWQ ==
X-ME-Sender: <xms:Z5vAXevGnlsMkUSE5Ln-3f6m_20xwqcuB_OFl_TdQArM-CSmhL8pVg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedruddufedgudehfecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesth dtredtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehl ohifvghnthhrohhphidrnhgvtheqnecurfgrrhgrmhepmhgrihhlfhhrohhmpehmtheslh hofigvnhhtrhhophihrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:Z5vAXUCIpuYeUjzCNCegjE1a2BoMV-DwcjeZmVkGuYSAaD6JVTdvAg> <xmx:Z5vAXVKWY1kx-Sl5UTorQ4IMbzm5adBdEddgqC-CmVYwt02QAqh3SQ> <xmx:Z5vAXb25pngvnAkdfZU5YXygtVvxSWNv7HZR3EhrJr_JYw6-kM9JIQ> <xmx:aJvAXXOccMHmjpfUMq3TLjhr56BAzypsqcmi7qVte6283qO8o2A5mg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id D0683E00A3; Mon,  4 Nov 2019 16:43:03 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-509-ge3ec61c-fmstable-20191030v1
Mime-Version: 1.0
Message-Id: <d7dc1be9-2eab-47cb-9fcb-3a0503014d0c@www.fastmail.com>
In-Reply-To: <CAJ_4DfTN-25ZpDmGBFXxmz9RZCT=8JbpFoDX71eyhE1rEtPkMg@mail.gmail.com>
References: <CAJ_4DfTN-25ZpDmGBFXxmz9RZCT=8JbpFoDX71eyhE1rEtPkMg@mail.gmail.com>
Date: Tue, 05 Nov 2019 08:42:44 +1100
From: "Martin Thomson" <mt@lowentropy.net>
To: quic@ietf.org
Subject: Re: Alternate Version + Salt in Alt-Svc
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/8UoJaAaGO7WLqkZafv4LvVeDCjI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 21:43:08 -0000

On Tue, Nov 5, 2019, at 07:34, Ryan Hamilton wrote:
> I can think of solutions/mitigations for this issue (like restricting 
> the number of bits which can be flipped by the server, or expiring the 
> alternative version in the client on first use, etc) but I'd be curious 
> if this seems like an issue to other folks first.

Yes, this is an issue.  Thanks for identifying it.  We hadn't gotten to Alt-Svc for this yet, we're having enough trouble with NEW_TOKEN :)

The general rule we follow for these things is to require confidentiality for the initial signaling and to only use the value once.  That works for session tickets, it works for NEW_TOKEN, and I see no reason not to have it apply here also.  That means falling back to version==1 for connection attempts after the first.

That diminishes the value of the addition a little, but I don't think that it is enough to be concerned.  The alternative service still exists and can be used, and successful connection attempts should provision the client with more tokens for future connections.


From nobody Mon Nov  4 13:47:35 2019
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 E996A1209AF for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 13:47:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level: 
X-Spam-Status: No, score=-1.996 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_HELO_NONE=0.001, 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 Q4RpgQ6OqIiz for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 13:47:08 -0800 (PST)
Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (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 197EC1209C8 for <quic@ietf.org>; Mon,  4 Nov 2019 13:47:08 -0800 (PST)
Received: by mail-ed1-x52e.google.com with SMTP id k14so5527647eds.4 for <quic@ietf.org>; Mon, 04 Nov 2019 13:47:08 -0800 (PST)
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=mEgQdMwWbVqxFvVfJSPYs5ZW51Q6QNXCspa60T86UK8=; b=JXYiVAYyuE7EDXsoKoK+nTRQHYULy19nT835bW9LBABCU5Ow+ShMkVKu9DM4LDPnAG omGpIIQgeR336owdlIjhohdWNW0uo0EIVhjRHysGdJqTjsGSk2encegBEECr1UVzEMTc AuMRBEoiQj4DSYD+ItV/I8i2YkWlh4xrGJubu13PZlPcT/hyMZCRsul9MFL8BmWEfvoG +wbbvZg1WHqMlhqEZs90/TCYB0lyObnV0bAObZllU4Z6K6VjH9A/Y63POWLYjIk/A1TV DyFIwQzRf/2aLi6ZxVt4ttX36XlVRGXWfQaRhyrIAhDJD8QLwixSjm7sQr+lydeLsBWX 2IhA==
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=mEgQdMwWbVqxFvVfJSPYs5ZW51Q6QNXCspa60T86UK8=; b=FGVgS+oBa+tVucWfCcBpX0oV+alaMWmB5uHzMs/uVefqWSZUHAMKPMFMtsZcxdz4J+ KOikXJkYan3H6KhIekogUg78lqb7Kt1T+PNCPV/DRji779DCInK3soL3LF3bXI4rUWGF Cl2LkZ0mbKZ1RlLsb/MVKUqLzvfj1Ma+ShDt4A04xb1zL9WUySE84oAhTqKOpOUzcRRA /vVClcMOdx3ziJVpyi5d+v+qfGZ6Iir/J4xzBwGG+RjbFO+4qSPrDsycNoJgrbgpTvUT sbb8zjkWYxFGdBRKDdsVLRQEdI2mTjXF/HwzG1NYIrvxLfXvVAtGvJ534DvQPjKEueNz 5YOw==
X-Gm-Message-State: APjAAAXklqYd6JbJNLjOl9pS5VdX6sgkS1qCaypYGt0EhgAElbEpYBS2 RcSsbclalNg2pkJwEJecefr0lAwpIb5h7v9yZKI8CuU7
X-Google-Smtp-Source: APXvYqz22RU5frx+5aJnzYIbExnKKyI6WzCgWlv+B6sgApeul44mzbf13d/l37A4AgSOZmdu4HoznfqnMo7jLyXV9vc=
X-Received: by 2002:a05:6402:488:: with SMTP id k8mr31816429edv.293.1572904026510;  Mon, 04 Nov 2019 13:47:06 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Mon, 4 Nov 2019 22:47:05 +0100
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <d7dc1be9-2eab-47cb-9fcb-3a0503014d0c@www.fastmail.com>
References: <CAJ_4DfTN-25ZpDmGBFXxmz9RZCT=8JbpFoDX71eyhE1rEtPkMg@mail.gmail.com> <d7dc1be9-2eab-47cb-9fcb-3a0503014d0c@www.fastmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Mon, 4 Nov 2019 22:47:05 +0100
Message-ID: <CAN1APdckCy1698hoASZOpzSs8fNzfcwH=rbmP1cS52-Lt6djRQ@mail.gmail.com>
Subject: Re: Alternate Version + Salt in Alt-Svc
To: Martin Thomson <mt@lowentropy.net>, quic@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c41b6705968c415e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/5U6ud7PgiLN9iP4XuZ2UA-wOZxA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 21:47:16 -0000

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

Sorry, my response was on the wrong topic. It was in relation to version
negotation.

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


On 4 November 2019 at 22.43.42, Martin Thomson (mt@lowentropy.net) wrote:

Some random observations reading through the document

- Is the order relevant in the receiver version list?

- It is tempting to just hash the received version list, but that requires
agreeing on an algorithm, unless the algorithm is stated to be specific to
that version, which is complicated.

- VERSION_NEGOTIATION_ERROR vs drop - I=E2=80=99m not sure it is a good ide=
a to
close the connection. The initials are public so it is possible to inject
false versions. There are probably many other similar attacks we don=E2=80=
=99t
bother with, but still =E2=80=A6

- Checking that a transport parameter field is the same as the long header
version seems redundant - why have those fields? Is it because the Initial
header fields are not sufficiently protected via TLS magic (or similar)?

- We generally use varint, but why have varints mixed with 32-bit version
lists? I suggest making the list length 32-bit for easier processing.

- Downgrade - I=E2=80=99m a bit worried about state management and server
redeployments. A server could reject a valid packet because an Initial was
routed to a new server. (Reading further, I see this is addressed). This is
probably a pragmatic solution, but it has an assumption about eventual
global coordination. I suspect something could be done here with tokens or
CID routing, but it is not trivial.

- Security Considerations - perhaps it is worth noting the transport
parameters need additional protection beyond the Initial packet protection?
This follows from TLS, but if TLS is not being used, this can version
negotiation even if other parts of the protocol version is not sensitive to
this in that particular version.

- Greasing 0x?a?a?a?a - I=E2=80=99m not really sure about the point of this=
.
Especially if we get salted versions in separate proposal.

- It is not immediately obvious if version negotiation can go on and on, or
if it settles after at most one roundtrip one way or the other. This might
depend on the client QUIC version, but that is a fuzzy term in this context=
.

- Improve discussion of Previously Attempted Version. While the
requirements are readable, the purpose of doing this check is less obvious.
Presumably this deals with downgrade attacks, but more explanation would be
appreciated.

Mikkel

--000000000000c41b6705968c415e
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">Sorry, my response w=
as on the wrong topic. It was in relation to version negotation.</div> <br>=
 <div id=3D"bloop_sign_1572903992865332224" class=3D"bloop_sign"><div style=
=3D"font-family:helvetica,arial;font-size:13px">Kind Regards,</div><div sty=
le=3D"font-family:helvetica,arial;font-size:13px">Mikkel Fahn=C3=B8e J=C3=
=B8rgensen<br><br></div></div> <br><p class=3D"airmail_on">On 4 November 20=
19 at 22.43.42, Martin Thomson (<a href=3D"mailto:mt@lowentropy.net">mt@low=
entropy.net</a>) wrote:</p> <blockquote type=3D"cite" class=3D"clean_bq"><s=
pan><div><div id=3D"bloop_customfont" style=3D"color:rgb(0,0,0);font-style:=
normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;te=
xt-align:start;text-indent:0px;text-transform:none;white-space:normal;word-=
spacing:0px;text-decoration:none;font-family:Helvetica,Arial;font-size:13px=
;margin:0px">Some random observations reading through the document</div><di=
v id=3D"bloop_customfont" style=3D"color:rgb(0,0,0);font-style:normal;font-=
variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:sta=
rt;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;=
text-decoration:none;font-family:Helvetica,Arial;font-size:13px;margin:0px"=
><br></div><div id=3D"bloop_customfont" style=3D"color:rgb(0,0,0);font-styl=
e:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;=
text-align:start;text-indent:0px;text-transform:none;white-space:normal;wor=
d-spacing:0px;text-decoration:none;font-family:Helvetica,Arial;font-size:13=
px;margin:0px">- Is the order relevant in the receiver version list?</div><=
div id=3D"bloop_customfont" style=3D"color:rgb(0,0,0);font-style:normal;fon=
t-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:s=
tart;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0p=
x;text-decoration:none;font-family:Helvetica,Arial;font-size:13px;margin:0p=
x"><br></div><div id=3D"bloop_customfont" style=3D"color:rgb(0,0,0);font-st=
yle:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:norma=
l;text-align:start;text-indent:0px;text-transform:none;white-space:normal;w=
ord-spacing:0px;text-decoration:none;font-family:Helvetica,Arial;font-size:=
13px;margin:0px">- It is tempting to just hash the received version list, b=
ut that requires agreeing on an algorithm, unless the algorithm is stated t=
o be specific to that version, which is complicated.</div><div id=3D"bloop_=
customfont" style=3D"color:rgb(0,0,0);font-style:normal;font-variant-caps:n=
ormal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent=
:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoratio=
n:none;font-family:Helvetica,Arial;font-size:13px;margin:0px"><br></div><di=
v id=3D"bloop_customfont" style=3D"color:rgb(0,0,0);font-family:&quot;helve=
tica Neue&quot;,helvetica;font-size:14px;font-style:normal;font-variant-cap=
s:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-ind=
ent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decora=
tion:none;margin:0px">-=C2=A0<span style=3D"orphans: 2; widows: 2;"><font s=
ize=3D"3">VERSION_NEGOTIATION_ERROR vs drop - I=E2=80=99m not sure it is a =
good idea to close the connection. The initials are public so it is possibl=
e to inject false versions. There are probably many other similar attacks w=
e don=E2=80=99t bother with, but still=C2=A0</font></span><font size=3D"3">=
=E2=80=A6</font></div><div id=3D"bloop_customfont" style=3D"color:rgb(0,0,0=
);font-family:&quot;helvetica Neue&quot;,helvetica;font-size:14px;font-styl=
e:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;=
text-align:start;text-indent:0px;text-transform:none;white-space:normal;wor=
d-spacing:0px;text-decoration:none;margin:0px"><span style=3D"orphans: 2; w=
idows: 2;"><font size=3D"3"><br></font></span></div><div id=3D"bloop_custom=
font" style=3D"color:rgb(0,0,0);font-family:&quot;helvetica Neue&quot;,helv=
etica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight=
:normal;letter-spacing:normal;text-align:start;text-indent:0px;text-transfo=
rm:none;white-space:normal;word-spacing:0px;text-decoration:none;margin:0px=
"><span style=3D"orphans: 2; widows: 2;"><font size=3D"3">- Checking that a=
 transport parameter field is the same as the long header version seems red=
undant - why have those fields? Is it because the Initial header fields are=
 not sufficiently protected via TLS magic (or similar)?</font></span></div>=
<div id=3D"bloop_customfont" style=3D"color:rgb(0,0,0);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;font-family:Helvetica,Arial;font-size:13px;margin:0=
px"><br></div><div id=3D"bloop_customfont" style=3D"color:rgb(0,0,0);font-s=
tyle:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:norm=
al;text-align:start;text-indent:0px;text-transform:none;white-space:normal;=
word-spacing:0px;text-decoration:none;font-family:Helvetica,Arial;font-size=
:13px;margin:0px">- We generally use varint, but why have varints mixed wit=
h 32-bit version lists? I suggest making the list length 32-bit for easier =
processing.</div><div id=3D"bloop_customfont" style=3D"color:rgb(0,0,0);fon=
t-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:n=
ormal;text-align:start;text-indent:0px;text-transform:none;white-space:norm=
al;word-spacing:0px;text-decoration:none;font-family:Helvetica,Arial;font-s=
ize:13px;margin:0px"><br></div><div style=3D"color:rgb(0,0,0);font-family:&=
quot;helvetica Neue&quot;,helvetica;font-size:14px;font-style:normal;font-v=
ariant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:star=
t;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;t=
ext-decoration:none">- Downgrade - I=E2=80=99m a bit worried about state ma=
nagement and server redeployments. A server could reject a valid packet bec=
ause an Initial was routed to a new server. (Reading further, I see this is=
 addressed). This is probably a pragmatic solution, but it has an assumptio=
n about eventual global coordination. I suspect something could be done her=
e with tokens or CID routing, but it is not trivial.</div><div style=3D"col=
or:rgb(0,0,0);font-family:&quot;helvetica Neue&quot;,helvetica;font-size:14=
px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spa=
cing:normal;text-align:start;text-indent:0px;text-transform:none;white-spac=
e:normal;word-spacing:0px;text-decoration:none"><br></div><span style=3D"co=
lor:rgb(0,0,0);font-family:&quot;helvetica Neue&quot;,helvetica;font-size:1=
4px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-sp=
acing:normal;text-align:start;text-indent:0px;text-transform:none;white-spa=
ce:normal;word-spacing:0px;background-color:rgb(255,255,255);text-decoratio=
n:none;display:inline!important;float:none">- Security Considerations - per=
haps it is worth noting the transport parameters need additional protection=
 beyond the Initial packet protection? This follows from TLS, but if TLS is=
 not being used, this can version negotiation even if other parts of the pr=
otocol version is not sensitive to this in that particular version.</span><=
div style=3D"color:rgb(0,0,0);font-family:&quot;helvetica Neue&quot;,helvet=
ica;font-size:14px;font-style:normal;font-variant-caps:normal;font-weight:n=
ormal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;white-space:normal;word-spacing:0px;text-decoration:none"><br><div>- =
Greasing 0x?a?a?a?a - I=E2=80=99m not really sure about the point of this. =
Especially if we get salted versions in separate proposal.</div><div><br></=
div><div>- It is not immediately obvious if version negotiation can go on a=
nd on, or if it settles after at most one roundtrip one way or the other. T=
his might depend on the client QUIC version, but that is a fuzzy term in th=
is context.</div><div><br></div><div>- Improve discussion of Previously Att=
empted Version. While the requirements are readable, the purpose of doing t=
his check is less obvious. Presumably this deals with downgrade attacks, bu=
t more explanation would be appreciated.</div><div><br></div><div>Mikkel<br=
></div></div></div></span></blockquote></body></html>

--000000000000c41b6705968c415e--


From nobody Mon Nov  4 13:47:41 2019
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 6D597120A2F for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 13:47:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.996
X-Spam-Level: 
X-Spam-Status: No, score=-0.996 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_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 evIiV9AOoyAF for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 13:47:31 -0800 (PST)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 7DC251209FF for <quic@ietf.org>; Mon,  4 Nov 2019 13:47:31 -0800 (PST)
Received: by mail-ed1-x529.google.com with SMTP id a67so2284637edf.11 for <quic@ietf.org>; Mon, 04 Nov 2019 13:47:31 -0800 (PST)
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=Yld9NGtn9HnRHRStD/Hm2p0fe2Kphx9gn1Uynq6+Zqo=; b=Da+HEMXUED0BHOmabpJxK0GuevrCiUPRg66QTa4I9Dr37O2wCT/iPc94Z/oPBwmt+g RNhX9X4/v+m/cAZBGgoWYbW/XNfw4g+Ka72JcfYEoQ3e39JXjDE0KTMt+X6NhrHAGjUB 7D5jrAs6BxD8NJtbv3LeBzJ1YG5jm9cNsfDdmJnsuUrQZDIELPvWlrppUEQAiPXXl+Ep H1K6hGssc/O6zkVF/vOy60zBZV1uiPlBgPVuLJ5uek1T2sZMb3iBMuzw1WD8k0v4q1Oh 2RSpyLvZnJTkys7StRNhADTQ3nGt3dtrlmThJx8qS0QMIkcfTsPc/Ob1CufPSm5Hp9dB 0HVg==
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=Yld9NGtn9HnRHRStD/Hm2p0fe2Kphx9gn1Uynq6+Zqo=; b=DjDrfxIeqU0r4PH/NEtrubHQhldFXr2XIYXTpE5REQURfSW4Oqkdxzy7FPWF/4bD0l fed1Q1Ov8RV8J7UT2La2Gon4ypJr+arvL8r2kdccK9EW2qGIg7ybdGgXnDrqj6/OmQBs avhIcT+2hmSaCIaygxNtBvUEXm16iMIig5vO3Mc4QpOzcfqK4Bh2LA1KHjCs2pU4+qJC fIsNBNYY9FJGOVG7lB5ctD0GQlZ3pCUIGz/S0L42nwXtHfTauh/xpXbl4Nn4nURp/9fv YyV5g6FJtQd99oA+cepKT1YRk7sFHNrMG+04AK6yMq2qHSxKAtGT+S9ASb48qLDQL4ye 0VSA==
X-Gm-Message-State: APjAAAXco/mYsWpH2gH3G5mnRwATsv8Y+y6SFXrldUDRx1focsk/zd4D KFOT7USadC/G6cAGYrAgUH/1Zgr0W9nvvBXU8wih3+mL
X-Google-Smtp-Source: APXvYqyOAaF+lsX2WFq3QO3oQQp5wgx+ZROdLpDUCh/OnpVDDHy1AEahN8ZM/5razS/CR89wHscESM/b74Or0zk1Yww=
X-Received: by 2002:a17:906:1b41:: with SMTP id p1mr20680265ejg.65.1572904049654;  Mon, 04 Nov 2019 13:47:29 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Mon, 4 Nov 2019 22:47:29 +0100
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <CAPDSy+4wrhqejh9k8=G7W267EgcT5Z2sDK7ZBGKtNn5kkbXGfg@mail.gmail.com>
References: <CAPDSy+4wrhqejh9k8=G7W267EgcT5Z2sDK7ZBGKtNn5kkbXGfg@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Mon, 4 Nov 2019 22:47:29 +0100
Message-ID: <CAN1APdcZv-MtwRT77++r6EKdzJUc1NKEJfY4CZeOSaK50nPZYg@mail.gmail.com>
Subject: Re: QUIC Version Negotiation Extension
To: QUIC <quic@ietf.org>, David Schinazi <dschinazi.ietf@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000253f7305968c433b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/dwfeIcp1X7Qq9E8Hc2aNjB7d_RQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 21:47:40 -0000

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

(reposting on proper topic)

Some random observations reading through the document

- Is the order relevant in the receiver version list?

- It is tempting to just hash the received version list, but that requires
agreeing on an algorithm, unless the algorithm is stated to be specific to
that version, which is complicated.

- VERSION_NEGOTIATION_ERROR vs drop - I=E2=80=99m not sure it is a good ide=
a to
close the connection. The initials are public so it is possible to inject
false versions. There are probably many other similar attacks we don=E2=80=
=99t
bother with, but still =E2=80=A6

- Checking that a transport parameter field is the same as the long header
version seems redundant - why have those fields? Is it because the Initial
header fields are not sufficiently protected via TLS magic (or similar)?

- We generally use varint, but why have varints mixed with 32-bit version
lists? I suggest making the list length 32-bit for easier processing.

- Downgrade - I=E2=80=99m a bit worried about state management and server
redeployments. A server could reject a valid packet because an Initial was
routed to a new server. (Reading further, I see this is addressed). This is
probably a pragmatic solution, but it has an assumption about eventual
global coordination. I suspect something could be done here with tokens or
CID routing, but it is not trivial.

- Security Considerations - perhaps it is worth noting the transport
parameters need additional protection beyond the Initial packet protection?
This follows from TLS, but if TLS is not being used, this can version
negotiation even if other parts of the protocol version is not sensitive to
this in that particular version.

- Greasing 0x?a?a?a?a - I=E2=80=99m not really sure about the point of this=
.
Especially if we get salted versions in separate proposal.

- It is not immediately obvious if version negotiation can go on and on, or
if it settles after at most one roundtrip one way or the other. This might
depend on the client QUIC version, but that is a fuzzy term in this context=
.

- Improve discussion of Previously Attempted Version. While the
requirements are readable, the purpose of doing this check is less obvious.
Presumably this deals with downgrade attacks, but more explanation would be
appreciated.

Mikkel


On 4 November 2019 at 21.30.10, David Schinazi (dschinazi.ietf@gmail.com)
wrote:

Hi everyone,

>From the recent discussion on multiple PRs, it appears that there might be
a need for downgrade-safe QUIC version negotiation, earlier than we
expected.

EKR and I updated our extension to hopefully suit these needs:
https://tools.ietf.org/html/draft-schinazi-quic-version-negotiation-02

Comments welcome here or on the GitHub (link in draft).

Thanks,
David

--000000000000253f7305968c433b
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"><div id=3D"bloop_cus=
tomfont" style=3D"margin:0px">(reposting on proper topic)</div><div id=3D"b=
loop_customfont" style=3D"margin:0px"><br></div><div id=3D"bloop_customfont=
" style=3D"margin:0px">Some random observations reading through the documen=
t</div><div id=3D"bloop_customfont" style=3D"margin:0px"><br></div><div id=
=3D"bloop_customfont" style=3D"margin:0px">- Is the order relevant in the r=
eceiver version list?</div><div id=3D"bloop_customfont" style=3D"margin:0px=
"><br></div><div id=3D"bloop_customfont" style=3D"margin:0px">- It is tempt=
ing to just hash the received version list, but that requires agreeing on a=
n algorithm, unless the algorithm is stated to be specific to that version,=
 which is complicated.</div><div id=3D"bloop_customfont" style=3D"margin:0p=
x"><br></div><div id=3D"bloop_customfont" style=3D"font-family:&quot;helvet=
ica Neue&quot;,helvetica;font-size:14px;margin:0px">-=C2=A0<font size=3D"3"=
>VERSION_NEGOTIATION_ERROR vs drop - I=E2=80=99m not sure it is a good idea=
 to close the connection. The initials are public so it is possible to inje=
ct false versions. There are probably many other similar attacks we don=E2=
=80=99t bother with, but still=C2=A0</font><font size=3D"3">=E2=80=A6</font=
></div><div id=3D"bloop_customfont" style=3D"font-family:&quot;helvetica Ne=
ue&quot;,helvetica;font-size:14px;margin:0px"><font size=3D"3"><br></font><=
/div><div id=3D"bloop_customfont" style=3D"font-family:&quot;helvetica Neue=
&quot;,helvetica;font-size:14px;margin:0px"><font size=3D"3">- Checking tha=
t a transport parameter field is the same as the long header version seems =
redundant - why have those fields? Is it because the Initial header fields =
are not sufficiently protected via TLS magic (or similar)?</font></div><div=
 id=3D"bloop_customfont" style=3D"margin:0px"><br></div><div id=3D"bloop_cu=
stomfont" style=3D"margin:0px">- We generally use varint, but why have vari=
nts mixed with 32-bit version lists? I suggest making the list length 32-bi=
t for easier processing.</div><div id=3D"bloop_customfont" style=3D"margin:=
0px"><br></div><div style=3D"font-family:&quot;helvetica Neue&quot;,helveti=
ca;font-size:14px">- Downgrade - I=E2=80=99m a bit worried about state mana=
gement and server redeployments. A server could reject a valid packet becau=
se an Initial was routed to a new server. (Reading further, I see this is a=
ddressed). This is probably a pragmatic solution, but it has an assumption =
about eventual global coordination. I suspect something could be done here =
with tokens or CID routing, but it is not trivial.</div><div style=3D"font-=
family:&quot;helvetica Neue&quot;,helvetica;font-size:14px"><br></div><span=
 style=3D"font-family:&quot;helvetica Neue&quot;,helvetica;font-size:14px">=
- Security Considerations - perhaps it is worth noting the transport parame=
ters need additional protection beyond the Initial packet protection? This =
follows from TLS, but if TLS is not being used, this can version negotiatio=
n even if other parts of the protocol version is not sensitive to this in t=
hat particular version.</span><div style=3D"font-family:&quot;helvetica Neu=
e&quot;,helvetica;font-size:14px"><br><div>- Greasing 0x?a?a?a?a - I=E2=80=
=99m not really sure about the point of this. Especially if we get salted v=
ersions in separate proposal.</div><div><br></div><div>- It is not immediat=
ely obvious if version negotiation can go on and on, or if it settles after=
 at most one roundtrip one way or the other. This might depend on the clien=
t QUIC version, but that is a fuzzy term in this context.</div><div><br></d=
iv><div>- Improve discussion of Previously Attempted Version. While the req=
uirements are readable, the purpose of doing this check is less obvious. Pr=
esumably this deals with downgrade attacks, but more explanation would be a=
ppreciated.</div><div><br></div><div>Mikkel<br></div></div></div> <div id=
=3D"bloop_sign_1572904028770166784" class=3D"bloop_sign"><div style=3D"font=
-family:helvetica,arial;font-size:13px"><br></div></div> <br><p class=3D"ai=
rmail_on">On 4 November 2019 at 21.30.10, David Schinazi (<a href=3D"mailto=
:dschinazi.ietf@gmail.com">dschinazi.ietf@gmail.com</a>) wrote:</p> <blockq=
uote type=3D"cite" class=3D"clean_bq"><span><div><div></div><div>


<title></title>


<div dir=3D"ltr">Hi everyone,<br>
<div><br></div>
<div>From the recent discussion on multiple PRs, it appears that
there might be a need for downgrade-safe QUIC version negotiation,
earlier than we expected.</div>
<div><br></div>
<div>EKR and I updated our extension to hopefully suit these
needs:</div>
<div><a href=3D"https://tools.ietf.org/html/draft-schinazi-quic-version-neg=
otiation-02">
https://tools.ietf.org/html/draft-schinazi-quic-version-negotiation-02</a><=
br>
</div>
<div><br></div>
<div>Comments welcome here or on the GitHub (link in draft).</div>
<div><br></div>
<div>Thanks,</div>
<div>David</div>
</div>


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

--000000000000253f7305968c433b--


From nobody Mon Nov  4 14:03:39 2019
Return-Path: <martin.h.duke@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 468F5120154 for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 14:03:38 -0800 (PST)
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_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 jCejmo6cKDf1 for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 14:03:34 -0800 (PST)
Received: from mail-wr1-x431.google.com (mail-wr1-x431.google.com [IPv6:2a00:1450:4864:20::431]) (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 82CAC1200C4 for <quic@ietf.org>; Mon,  4 Nov 2019 14:03:34 -0800 (PST)
Received: by mail-wr1-x431.google.com with SMTP id n1so18907584wra.10 for <quic@ietf.org>; Mon, 04 Nov 2019 14:03:34 -0800 (PST)
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=1qLThQ+EfDsN5k8g8XrhTeNtRiABo9a6mN6D0G1qGpw=; b=M058+IC0eMRdpBHE4TPJP1uLdPqXnN0fmbbOYaeKKONVKX4SmCNM4zBkZHmuANQtIV w1ZhRwa0yPq53NPN3Ra4t2LWozJ/T613wK2TUOOVfQRufN4N0tU4TihtifYrI7dGky2T v2VFWFTAhuIsJw/YSoy32imyfXunbtygXtezJPoZznWdGtXnZokLpDZoHbUScMrprK6c WvSkNPAucoAtQZZdEg/s4l3WE0YS73H7fzg2CW8NPal39E/80NMj5eYN4rrOj0EUgKt+ NdYoA25BxXlmeCPR+18VXOrQ+5vKD3JUTlZ4ymbZkTwe/SaTFkPmACleHAU5if8UntVO tmGQ==
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=1qLThQ+EfDsN5k8g8XrhTeNtRiABo9a6mN6D0G1qGpw=; b=XvPvX0cT85xHuGqbPoHAb1G/5kdtgk6F8/PzRxsW8eZmcRkXroklFrPSDH3k4SM5SO xJTIeZLM3+LJUiV+9j8QRd/zu0tuurWHsURz4xMp41DmQRonf0vd4jL1Qb+g29QdoWiv pfacjL2M3QHX+3lOiAgZzQB03tIcuDCKn4hGOwVUlWcxswXzIo77W30BuRPtrx40UW1Y GlTm5tzpuPzoSdiz3iiRFkc9rbnr6RQ4d8i0ZY7HyN3AzXX8VvGJ4Jl/NLv/g41AGksk 2xKk6EuvYSqWeKHG8M/KAchvJlH9T43cw0OoO66zUqcAJIWFTDDXImOeoOXnLW5afoJx hn9w==
X-Gm-Message-State: APjAAAUOWjYozlodL+7xYgbnO/aQC/xBf/vxnh9K6yHM3KHM9E+nGGVP hhFeqSP6mWwX50ND/TI8kFuxNUadaCP9PrP2Kno=
X-Google-Smtp-Source: APXvYqzX3ndJnnTrksyEUZ6JpwCEyD8F4cNsSdJWn9K36b/fymqrKEQI0rsOEwfUTaLv2gcQolTSkrhNbJQrdIbcVV4=
X-Received: by 2002:a05:6000:12c4:: with SMTP id l4mr9452041wrx.110.1572905011097;  Mon, 04 Nov 2019 14:03:31 -0800 (PST)
MIME-Version: 1.0
References: <20191028194956.GC420@gmail.com> <CAM4esxTJUFD-G-WUOwZQbgSafpMJXHVtYCm1eF=_1g8tDxru=A@mail.gmail.com> <20191029210428.GA119@gmail.com>
In-Reply-To: <20191029210428.GA119@gmail.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Mon, 4 Nov 2019 14:03:19 -0800
Message-ID: <CAM4esxSaZdryVtem=iywADpTUhkjuNAyWgCC3-K1k715j3rQ-w@mail.gmail.com>
Subject: Re: draft-duke-quic-load-balancers-05.txt
To: Sowmini Varadhan <sowmini05@gmail.com>
Cc: IETF QUIC WG <quic@ietf.org>, Nick Banks <nibanks@microsoft.com>, sovaradh@microsoft.com
Content-Type: multipart/alternative; boundary="00000000000073b60705968c7c15"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/zjDGUM_CpfJjSITAi0t2wjfAG4Y>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 22:03:38 -0000

--00000000000073b60705968c7c15
Content-Type: text/plain; charset="UTF-8"

Sowmini,

Hopefully draft-06 addresses your concerns.

Thanks again for reviewing

On Tue, Oct 29, 2019 at 2:04 PM Sowmini Varadhan <sowmini05@gmail.com>
wrote:

> On (10/29/19 13:25), Martin Duke wrote:
> >    Hi Sowmini,
> >    Thanks for the review. I'll file a PR for your editorial changes.
>
> sounds good, thanks for doing this!
>
> >    0b11 is 2 bits. The '0b' notation indicates each digit is a bit; '0x'
> >    would be hexadecimal, where 2 characters = 1 Bytes.
>
> ah, this is the NIC data-sheet notation, that got me by surprise.
> If there is no strong objection, can we just list the code-points
> as "11" (I think this is the convention followed in other ietf rfcs,
> e.g., 3168, for the ECT code-points).
>
> >    In section 4, it says: " The load balancer SHOULD route Initial and
> 0-RTT
> >    packets from the client using an alternate algorithm". The point here
> is
> >    that the destination CID for these packets is chosen by the client.
> It may
> >    not be long enough to apply the chosen algorithm, so something else
> should
> >    be done. However, " This algorithm SHOULD generate consistent results
> for
> >    Initial and 0RTT packets that arrive with the same source and
> destination
> >    connection ID" so they all end up at the same place. If the LB
> doesn't do
> >    this, then the 0RTT packets will be lost. This is suboptimal but
> doesn't
> >    break the protocol.
>
> ok, perhaps it would be helpful to add some discussion around this
> in the draft.
>
> [discussion for "Section 4.3.1 refers to "token"]
> >    This is the QUIC-LB authentication token, which I should clarify. In
> any
> >    case, I don't believe that servers get this token if there's
> out-of-band
> >    configuration, so I need to fix this.
>
> Ok.
>
> [discussion around Section 5]
> >    This is for the benefit of the QUIC server. When the server gets an
> >    Initial Packet with a Retry token in it, it needs to extract the ODCID
> >    from that token so that it can send it back in a transport parameter.
> If
> >    the client got a Retry but then doesn't get the ODCID transport
> parameter,
> >    it means there's an unauthorized man in the middle and the client
> should
> >    terminate the connection.
>
> I see. In general, it would help to provide some context in this section
> about why any tweaks in the Retry Service are needed at all, along with
> your explanation above.
>
> Thanks!
>
> --Sowmini
>
>

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

<div dir=3D"ltr"><div>Sowmini,</div><div><br></div><div>Hopefully draft-06 =
addresses your concerns.</div><div><br></div><div>Thanks again for reviewin=
g<br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"g=
mail_attr">On Tue, Oct 29, 2019 at 2:04 PM Sowmini Varadhan &lt;<a href=3D"=
mailto:sowmini05@gmail.com">sowmini05@gmail.com</a>&gt; wrote:<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t:1px solid rgb(204,204,204);padding-left:1ex">On (10/29/19 13:25), Martin =
Duke wrote:<br>
&gt;=C2=A0 =C2=A0 Hi Sowmini,<br>
&gt;=C2=A0 =C2=A0 Thanks for the review. I&#39;ll file a PR for your editor=
ial changes.<br>
<br>
sounds good, thanks for doing this!<br>
<br>
&gt;=C2=A0 =C2=A0 0b11 is 2 bits. The &#39;0b&#39; notation indicates each =
digit is a bit; &#39;0x&#39;<br>
&gt;=C2=A0 =C2=A0 would be hexadecimal, where 2 characters =3D 1 Bytes.<br>
<br>
ah, this is the NIC data-sheet notation, that got me by surprise.<br>
If there is no strong objection, can we just list the code-points<br>
as &quot;11&quot; (I think this is the convention followed in other ietf rf=
cs,<br>
e.g., 3168, for the ECT code-points). <br>
<br>
&gt;=C2=A0 =C2=A0 In section 4, it says: &quot; The load balancer SHOULD ro=
ute Initial and 0-RTT<br>
&gt;=C2=A0 =C2=A0 packets from the client using an alternate algorithm&quot=
;. The point here is<br>
&gt;=C2=A0 =C2=A0 that the destination CID for these packets is chosen by t=
he client. It may<br>
&gt;=C2=A0 =C2=A0 not be long enough to apply the chosen algorithm, so some=
thing else should<br>
&gt;=C2=A0 =C2=A0 be done. However, &quot; This algorithm SHOULD generate c=
onsistent results for<br>
&gt;=C2=A0 =C2=A0 Initial and 0RTT packets that arrive with the same source=
 and destination<br>
&gt;=C2=A0 =C2=A0 connection ID&quot; so they all end up at the same place.=
 If the LB doesn&#39;t do<br>
&gt;=C2=A0 =C2=A0 this, then the 0RTT packets will be lost. This is subopti=
mal but doesn&#39;t<br>
&gt;=C2=A0 =C2=A0 break the protocol.<br>
<br>
ok, perhaps it would be helpful to add some discussion around this<br>
in the draft.<br>
<br>
[discussion for &quot;Section 4.3.1 refers to &quot;token&quot;]<br>
&gt;=C2=A0 =C2=A0 This is the QUIC-LB authentication token, which I should =
clarify. In any<br>
&gt;=C2=A0 =C2=A0 case, I don&#39;t believe that servers get this token if =
there&#39;s out-of-band<br>
&gt;=C2=A0 =C2=A0 configuration, so I need to fix this.<br>
<br>
Ok.<br>
<br>
[discussion around Section 5]<br>
&gt;=C2=A0 =C2=A0 This is for the benefit of the QUIC server. When the serv=
er gets an<br>
&gt;=C2=A0 =C2=A0 Initial Packet with a Retry token in it, it needs to extr=
act the ODCID<br>
&gt;=C2=A0 =C2=A0 from that token so that it can send it back in a transpor=
t parameter. If<br>
&gt;=C2=A0 =C2=A0 the client got a Retry but then doesn&#39;t get the ODCID=
 transport parameter,<br>
&gt;=C2=A0 =C2=A0 it means there&#39;s an unauthorized man in the middle an=
d the client should<br>
&gt;=C2=A0 =C2=A0 terminate the connection.<br>
<br>
I see. In general, it would help to provide some context in this section <b=
r>
about why any tweaks in the Retry Service are needed at all, along with <br=
>
your explanation above.<br>
<br>
Thanks!<br>
<br>
--Sowmini<br>
<br>
</blockquote></div>

--00000000000073b60705968c7c15--


From nobody Mon Nov  4 14:09:47 2019
Return-Path: <dschinazi.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 22FA5120B10 for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 14:09:38 -0800 (PST)
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_HELO_NONE=0.001, 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 4dV3Jbw4gHK7 for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 14:09:34 -0800 (PST)
Received: from mail-lf1-x130.google.com (mail-lf1-x130.google.com [IPv6:2a00:1450:4864:20::130]) (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 A3903120AB7 for <quic@ietf.org>; Mon,  4 Nov 2019 14:09:33 -0800 (PST)
Received: by mail-lf1-x130.google.com with SMTP id j14so13463711lfb.8 for <quic@ietf.org>; Mon, 04 Nov 2019 14:09:33 -0800 (PST)
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=mfnisDyRIVW7eDzYB99yOk97IR/LDGbl8AKw3bepw1I=; b=ND3u8KRvw+ZB1O3otmcLf34W5s+9u6lXLLjnKSC6QzRjXMdku/VULcqzv5NzIhh/+0 v0Oqj41TCDSvU+aalFrpPVj+dcaVxP04tYX//yf+zRxWCY/VAbjycJp+IwZzYMeH2Bqh P7ONNWKS0FAW1Mp5Q/24TUOvsExQu6ZqzPwb+V+GLLzP1207bWh7mt1h/EUoGwbDY79r H+NvclUDwLB23TVE2ELCgEuzCovjKUgQxcB9r1LWKM2e1isqs06Bo/hC5gynopR61of5 JA99x+x2yCYx85yz0FDqe+8HWG0NnHs63xQovipaepr9p60pf5PBaB04l0hqn7jpZest 2QaQ==
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=mfnisDyRIVW7eDzYB99yOk97IR/LDGbl8AKw3bepw1I=; b=kKcFSgiD8Dmn3cRWnG1LXO+N1w7Br4HJIDvhKw8fQo/E8YZ6vZQgyR6Smn1ROW0w7m Q2Hytyw4hOCXa2KI3RFzrNeF8wPLXI6cS/q1g1eNC0jWbJcQHKCBNostmxJBs1QD/keO GKQ1dETVKcrntRTllA1dK7cqpHDC0s4tj0laQDOP/+8quH+E12BAtqsE6fV1OqN9vDP6 tVA4fowu8ChXGhOyUolcn3dxvlbgy54kZTTTdE4tRlOscpn3gdG6+Bzr0QgQej3oWCbN FYz1+UCeEv4W8LaWRaM6+M/DqjQSP1NQWmOvWEfZICByN8ONyJlutlRRYqxwjh68Fis3 MmUA==
X-Gm-Message-State: APjAAAXfIywer3h6x1pSWaVBAnsNrWPxIlMVjQaBurUHGCZHnRDJLKtI wWMse7pdbRJtTDhwRbA3+FfsjQWiIaOtNbkOEi0esQM7
X-Google-Smtp-Source: APXvYqwRj3Q/N4ENifavWu0lZClVhRDx15Fw8B5VMQbXVAW4nCLr4Ryfpnr5EFxPskMsVEuTx5+EeTLAKQWQnMzBvlw=
X-Received: by 2002:ac2:434c:: with SMTP id o12mr18588477lfl.33.1572905371785;  Mon, 04 Nov 2019 14:09:31 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+4wrhqejh9k8=G7W267EgcT5Z2sDK7ZBGKtNn5kkbXGfg@mail.gmail.com> <CAN1APdcZv-MtwRT77++r6EKdzJUc1NKEJfY4CZeOSaK50nPZYg@mail.gmail.com>
In-Reply-To: <CAN1APdcZv-MtwRT77++r6EKdzJUc1NKEJfY4CZeOSaK50nPZYg@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Mon, 4 Nov 2019 14:09:20 -0800
Message-ID: <CAPDSy+5obMbiLDKYKXXg1ZthoMqyg60KD+6HR69CQqiEHb6W7g@mail.gmail.com>
Subject: Re: QUIC Version Negotiation Extension
To: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
Cc: QUIC <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f35ea205968c91dc"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/tn-u5liMHiwute7pfWqGu_1wC2E>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 22:09:43 -0000

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

Thanks for reading Mikkel! Responses inline.

On Mon, Nov 4, 2019 at 1:47 PM Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@=
gmail.com>
wrote:

> (reposting on proper topic)
>
> Some random observations reading through the document
>
> - Is the order relevant in the receiver version list?
>

Yes all lists of versions are ordered.


> - It is tempting to just hash the received version list, but that require=
s
> agreeing on an algorithm, unless the algorithm is stated to be specific t=
o
> that version, which is complicated.
>

Which list are you referring to? For all the ones in the draft, the peer
needs access to all the elements so I don't think a hash would help.


> - VERSION_NEGOTIATION_ERROR vs drop - I=E2=80=99m not sure it is a good i=
dea to
> close the connection. The initials are public so it is possible to inject
> false versions. There are probably many other similar attacks we don=E2=
=80=99t
> bother with, but still =E2=80=A6
>

Once we're this far in the handshake, we cannot recover from this error.
Dropping the packet will only make things worse.


> - Checking that a transport parameter field is the same as the long heade=
r
> version seems redundant - why have those fields? Is it because the Initia=
l
> header fields are not sufficiently protected via TLS magic (or similar)?
>

Yes, this makes sure an attacker cannot spoof the version field in initial
packets.


> - We generally use varint, but why have varints mixed with 32-bit version
> lists? I suggest making the list length 32-bit for easier processing.
>

QUICv1 uses varints pretty much everywhere, we're sticking to that design
here.


> - Downgrade - I=E2=80=99m a bit worried about state management and server
> redeployments. A server could reject a valid packet because an Initial wa=
s
> routed to a new server. (Reading further, I see this is addressed). This =
is
> probably a pragmatic solution, but it has an assumption about eventual
> global coordination. I suspect something could be done here with tokens o=
r
> CID routing, but it is not trivial.
>

Sounds interesting. Do you have a concrete proposal?


> - Security Considerations - perhaps it is worth noting the transport
> parameters need additional protection beyond the Initial packet protectio=
n?
> This follows from TLS, but if TLS is not being used, this can version
> negotiation even if other parts of the protocol version is not sensitive =
to
> this in that particular version.
>

draft-ietf-quic-transport section 7 requires transport parameters to be
authenticated.


> - Greasing 0x?a?a?a?a - I=E2=80=99m not really sure about the point of th=
is.
> Especially if we get salted versions in separate proposal.
>

We follow the QUIC reserved version design here.


> - It is not immediately obvious if version negotiation can go on and on,
> or if it settles after at most one roundtrip one way or the other. This
> might depend on the client QUIC version, but that is a fuzzy term in this
> context.
>

It can only happen once, though it might be a good idea to make that
clearer.


> - Improve discussion of Previously Attempted Version. While the
> requirements are readable, the purpose of doing this check is less obviou=
s.
> Presumably this deals with downgrade attacks, but more explanation would =
be
> appreciated.
>

The downgrade prevention section discusses the purpose of this field. What
details do you think we should add?

Mikkel
>
>
> On 4 November 2019 at 21.30.10, David Schinazi (dschinazi.ietf@gmail.com)
> wrote:
>
> Hi everyone,
>
> From the recent discussion on multiple PRs, it appears that there might b=
e
> a need for downgrade-safe QUIC version negotiation, earlier than we
> expected.
>
> EKR and I updated our extension to hopefully suit these needs:
> https://tools.ietf.org/html/draft-schinazi-quic-version-negotiation-02
>
> Comments welcome here or on the GitHub (link in draft).
>
> Thanks,
> David
>
>

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

<div dir=3D"ltr"><div>Thanks for reading Mikkel! Responses inline.</div><br=
><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, N=
ov 4, 2019 at 1:47 PM Mikkel Fahn=C3=B8e J=C3=B8rgensen &lt;<a href=3D"mail=
to:mikkelfj@gmail.com">mikkelfj@gmail.com</a>&gt; wrote:<br></div><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"><div style=3D"overflow-wrap: break=
-word;"><div id=3D"gmail-m_-6391629696368244571bloop_customfont" style=3D"f=
ont-family:Helvetica,Arial;font-size:13px;color:rgb(0,0,0);margin:0px"><div=
 id=3D"gmail-m_-6391629696368244571bloop_customfont" style=3D"margin:0px">(=
reposting on proper topic)</div><div id=3D"gmail-m_-6391629696368244571bloo=
p_customfont" style=3D"margin:0px"><br></div><div id=3D"gmail-m_-6391629696=
368244571bloop_customfont" style=3D"margin:0px">Some random observations re=
ading through the document</div><div id=3D"gmail-m_-6391629696368244571bloo=
p_customfont" style=3D"margin:0px"><br></div><div id=3D"gmail-m_-6391629696=
368244571bloop_customfont" style=3D"margin:0px">- Is the order relevant in =
the receiver version list?</div></div></div></blockquote><div><br></div><di=
v>Yes all lists of versions are ordered.</div><div>=C2=A0</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><div style=3D"overflow-wrap: break-wo=
rd;"><div id=3D"gmail-m_-6391629696368244571bloop_customfont" style=3D"font=
-family:Helvetica,Arial;font-size:13px;color:rgb(0,0,0);margin:0px"><div id=
=3D"gmail-m_-6391629696368244571bloop_customfont" style=3D"margin:0px">- It=
 is tempting to just hash the received version list, but that requires agre=
eing on an algorithm, unless the algorithm is stated to be specific to that=
 version, which is complicated.</div></div></div></blockquote><div><br></di=
v><div>Which list are you=C2=A0referring to? For all the ones in the draft,=
 the peer needs access to all the elements so I don&#39;t think a hash woul=
d help.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div style=3D"overflow-wrap: break-word;"><div id=3D"gmail-m_-63916296=
96368244571bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size=
:13px;color:rgb(0,0,0);margin:0px"><div id=3D"gmail-m_-6391629696368244571b=
loop_customfont" style=3D"font-family:&quot;helvetica Neue&quot;,helvetica;=
font-size:14px;margin:0px">-=C2=A0<font size=3D"3">VERSION_NEGOTIATION_ERRO=
R vs drop - I=E2=80=99m not sure it is a good idea to close the connection.=
 The initials are public so it is possible to inject false versions. There =
are probably many other similar attacks we don=E2=80=99t bother with, but s=
till=C2=A0</font><font size=3D"3">=E2=80=A6</font></div></div></div></block=
quote><div><br></div><div>Once we&#39;re this far in the handshake, we cann=
ot recover from this error. Dropping the packet will only make things worse=
.</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><=
div style=3D"overflow-wrap: break-word;"><div id=3D"gmail-m_-63916296963682=
44571bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;=
color:rgb(0,0,0);margin:0px"><div id=3D"gmail-m_-6391629696368244571bloop_c=
ustomfont" style=3D"font-family:&quot;helvetica Neue&quot;,helvetica;font-s=
ize:14px;margin:0px"><font size=3D"3">- Checking that a transport parameter=
 field is the same as the long header version seems redundant - why have th=
ose fields? Is it because the Initial header fields are not sufficiently pr=
otected via TLS magic (or similar)?</font></div></div></div></blockquote><d=
iv><br></div><div>Yes, this makes sure an attacker cannot spoof the version=
 field in initial packets.</div><div>=C2=A0</div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex"><div style=3D"overflow-wrap: break-word;"><div id=
=3D"gmail-m_-6391629696368244571bloop_customfont" style=3D"font-family:Helv=
etica,Arial;font-size:13px;color:rgb(0,0,0);margin:0px"><div id=3D"gmail-m_=
-6391629696368244571bloop_customfont" style=3D"margin:0px">- We generally u=
se varint, but why have varints mixed with 32-bit version lists? I suggest =
making the list length 32-bit for easier processing.</div></div></div></blo=
ckquote><div><br></div><div>QUICv1 uses varints pretty much everywhere, we&=
#39;re sticking to that design here.</div><div>=C2=A0</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex"><div style=3D"overflow-wrap: break-word;"=
><div id=3D"gmail-m_-6391629696368244571bloop_customfont" style=3D"font-fam=
ily:Helvetica,Arial;font-size:13px;color:rgb(0,0,0);margin:0px"><div style=
=3D"font-family:&quot;helvetica Neue&quot;,helvetica;font-size:14px">- Down=
grade - I=E2=80=99m a bit worried about state management and server redeplo=
yments. A server could reject a valid packet because an Initial was routed =
to a new server. (Reading further, I see this is addressed). This is probab=
ly a pragmatic solution, but it has an assumption about eventual global coo=
rdination. I suspect something could be done here with tokens or CID routin=
g, but it is not trivial.</div></div></div></blockquote><div><br></div><div=
>Sounds interesting. Do you have a concrete proposal?</div><div>=C2=A0</div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex"><div style=3D"overflow-w=
rap: break-word;"><div id=3D"gmail-m_-6391629696368244571bloop_customfont" =
style=3D"font-family:Helvetica,Arial;font-size:13px;color:rgb(0,0,0);margin=
:0px"><span style=3D"font-family:&quot;helvetica Neue&quot;,helvetica;font-=
size:14px">- Security Considerations - perhaps it is worth noting the trans=
port parameters need additional protection beyond the Initial packet protec=
tion? This follows from TLS, but if TLS is not being used, this can version=
 negotiation even if other parts of the protocol version is not sensitive t=
o this in that particular version.</span></div></div></blockquote><div><br>=
</div><div>draft-ietf-quic-transport section 7 requires transport parameter=
s to be authenticated.</div><div>=C2=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div style=3D"overflow-wrap: break-word;"><div id=3D"gm=
ail-m_-6391629696368244571bloop_customfont" style=3D"font-family:Helvetica,=
Arial;font-size:13px;color:rgb(0,0,0);margin:0px"><div style=3D"font-family=
:&quot;helvetica Neue&quot;,helvetica;font-size:14px"><div>- Greasing 0x?a?=
a?a?a - I=E2=80=99m not really sure about the point of this. Especially if =
we get salted versions in separate proposal.</div></div></div></div></block=
quote><div><br></div><div>We follow the QUIC reserved version design here.<=
/div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><di=
v style=3D"overflow-wrap: break-word;"><div id=3D"gmail-m_-6391629696368244=
571bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;co=
lor:rgb(0,0,0);margin:0px"><div style=3D"font-family:&quot;helvetica Neue&q=
uot;,helvetica;font-size:14px"><div>- It is not immediately obvious if vers=
ion negotiation can go on and on, or if it settles after at most one roundt=
rip one way or the other. This might depend on the client QUIC version, but=
 that is a fuzzy term in this context.</div></div></div></div></blockquote>=
<div><br></div><div>It can only happen once, though it might be a good idea=
 to make that clearer.</div><div>=C2=A0</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div style=3D"overflow-wrap: break-word;"><div id=3D"gm=
ail-m_-6391629696368244571bloop_customfont" style=3D"font-family:Helvetica,=
Arial;font-size:13px;color:rgb(0,0,0);margin:0px"><div style=3D"font-family=
:&quot;helvetica Neue&quot;,helvetica;font-size:14px"><div>- Improve discus=
sion of Previously Attempted Version. While the requirements are readable, =
the purpose of doing this check is less obvious. Presumably this deals with=
 downgrade attacks, but more explanation would be appreciated.</div></div><=
/div></div></blockquote><div><br></div><div>The downgrade prevention sectio=
n discusses the purpose of this field. What details do you think we should =
add?</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:=
0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">=
<div style=3D"overflow-wrap: break-word;"><div id=3D"gmail-m_-6391629696368=
244571bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px=
;color:rgb(0,0,0);margin:0px"><div style=3D"font-family:&quot;helvetica Neu=
e&quot;,helvetica;font-size:14px"><div>Mikkel<br></div></div></div> <div id=
=3D"gmail-m_-6391629696368244571bloop_sign_1572904028770166784"><div style=
=3D"font-family:helvetica,arial;font-size:13px"><br></div></div> <br><p>On =
4 November 2019 at 21.30.10, David Schinazi (<a href=3D"mailto:dschinazi.ie=
tf@gmail.com" target=3D"_blank">dschinazi.ietf@gmail.com</a>) wrote:</p> <b=
lockquote type=3D"cite"><span><div><div></div><div>





<div dir=3D"ltr">Hi everyone,<br>
<div><br></div>
<div>From the recent discussion on multiple PRs, it appears that
there might be a need for downgrade-safe QUIC version negotiation,
earlier than we expected.</div>
<div><br></div>
<div>EKR and I updated our extension to hopefully suit these
needs:</div>
<div><a href=3D"https://tools.ietf.org/html/draft-schinazi-quic-version-neg=
otiation-02" target=3D"_blank">
https://tools.ietf.org/html/draft-schinazi-quic-version-negotiation-02</a><=
br>
</div>
<div><br></div>
<div>Comments welcome here or on the GitHub (link in draft).</div>
<div><br></div>
<div>Thanks,</div>
<div>David</div>
</div>


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

--000000000000f35ea205968c91dc--


From nobody Mon Nov  4 14:33:04 2019
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 7596F120A9F for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 14:33:02 -0800 (PST)
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, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 66syWbSS8bUz for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 14:33:00 -0800 (PST)
Received: from mx36-out10.antispamcloud.com (mx36-out10.antispamcloud.com [209.126.121.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 8AA45120127 for <quic@ietf.org>; Mon,  4 Nov 2019 14:33:00 -0800 (PST)
Received: from xse187.mail2web.com ([66.113.196.187] helo=xse.mail2web.com) by mx65.antispamcloud.com with esmtp (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1iRkuA-0000Rc-4B for quic@ietf.org; Mon, 04 Nov 2019 23:32:58 +0100
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 476SFT2jCcz2xg7 for <quic@ietf.org>; Mon,  4 Nov 2019 14:31:25 -0800 (PST)
Received: from [10.5.2.16] (helo=xmail06.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1iRksf-0002OU-8k for quic@ietf.org; Mon, 04 Nov 2019 14:31:25 -0800
Received: (qmail 18369 invoked from network); 4 Nov 2019 22:31:24 -0000
Received: from unknown (HELO [192.168.1.101]) (Authenticated-user:_huitema@huitema.net@[172.58.43.152]) (envelope-sender <huitema@huitema.net>) by xmail06.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 4 Nov 2019 22:31:24 -0000
To: David Schinazi <dschinazi.ietf@gmail.com>, =?UTF-8?Q?Mikkel_Fahn=c3=b8e_J=c3=b8rgensen?= <mikkelfj@gmail.com>
Cc: QUIC <quic@ietf.org>
References: <CAPDSy+4wrhqejh9k8=G7W267EgcT5Z2sDK7ZBGKtNn5kkbXGfg@mail.gmail.com> <CAN1APdcZv-MtwRT77++r6EKdzJUc1NKEJfY4CZeOSaK50nPZYg@mail.gmail.com> <CAPDSy+5obMbiLDKYKXXg1ZthoMqyg60KD+6HR69CQqiEHb6W7g@mail.gmail.com>
From: Christian Huitema <huitema@huitema.net>
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mQENBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAG0J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PokBOQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1a5AQ0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAYkCPgQYAQIACQUCUhFfyAIb 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=
Subject: Re: QUIC Version Negotiation Extension
Message-ID: <aa6be7bc-e4c3-e14f-8064-f511e8fbfb70@huitema.net>
Date: Mon, 4 Nov 2019 14:31:25 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1
MIME-Version: 1.0
In-Reply-To: <CAPDSy+5obMbiLDKYKXXg1ZthoMqyg60KD+6HR69CQqiEHb6W7g@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------BC2EC1221426F0E13FCBD6B9"
Content-Language: en-US
X-Originating-IP: 66.113.196.187
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.187/32
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.187/32@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0T9zDZOvA8ND4p2eQxdfzLSpSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDcnqpk5VeF3xR4kF6iVwRtbgN zB/4Jkrw1eDLcif59ftnAcGotDcF23HNAfAuOcqIU7Tmz6iKnkQL9gqsxD347235Nhqq+/HvroPq 8GSPg+5aB4itzNZ07CdqP+KMfGjQUz0sPgnpAk2KA2vJwMd1uY6jSvfpO+1kZkomjtjB6X5Q5Q9f RUeIpTIC2ySfqvnqLwoxlgatmaBb0rBiK9xbkDrUqzcKIief90MVLZY9LbIZh9+IQ1oS9LBn3VIP 95Jz7ujRlJ9wSMlhvaudJXZ9EIBG/qaR+8r9SKFMmPJLf850OvZYsmoVQuOIhwKLK6IKBNB4LZ0v UHHKTzJX7b1JhLSQQ4vSj0QEim26t/Moy0UPX5E73H1QfrH/5kkrV/Cr0bm2vWdo8usP65i82q1C dZgGrpL44wdx9eXqjQjbvUopOMQJvQ/Ck3iiU+4DQAj3fuQgzT3K9JUHTNiGwfwAm3OZmI6+6AcH EU4XbMnrDarMCwbYZSDsvW0enk+rZHRdlv0GJCQopQ9KJL0fDLG3h96m3sWV/ImezRNfIOqOPfQM 7OYFXYdC3tRq275m/U3VpR20WA4qxE8HEf6BOpfbvrdCp3Zd9clP8wSiJZWbJCj+xRrjVmRxpGtS cvUmgj1Lx5YQ3PLxPZj1HhRc9GBo2V2jZAOanSBpz6Rja2u/0jJEd39dY9VDdK4BT5IQDl1l2Pw9 G+41ufxzuq6KbIukdfysta6u1iHEyuS7GD1uvcrX/ngr5O18X2gUzhLy4NGZJOYIJd4MvQ0Nf4Ec bvHO1diDanHV9KirFAIIecsyj+YNTo81GR+jDXFsz/ZQnbbTizvwlZsrbltGiZoUh+c+5pFVgpT1 b21uZVckGp0ccOa2XhkGbmsUNPNkere1WheNsVXmhO8BzADiszcWR9bz/SDtF09JpSbuuCeiIDK0 C/0=
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Dhg5sUnHwLmrPWG58ZeqWzSpRIw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 22:33:02 -0000

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


On 11/4/2019 2:09 PM, David Schinazi wrote:
> Thanks for reading Mikkel! Responses inline.
>
> On Mon, Nov 4, 2019 at 1:47 PM Mikkel Fahn=C3=B8e J=C3=B8rgensen
> <mikkelfj@gmail.com <mailto:mikkelfj@gmail.com>> wrote:
>
>     (reposting on proper topic)
>
>     Some random observations reading through the document
>
>     - Is the order relevant in the receiver version list?
>
>
> Yes all lists of versions are ordered.
> =C2=A0
>
>     - It is tempting to just hash the received version list, but that
>     requires agreeing on an algorithm, unless the algorithm is stated
>     to be specific to that version, which is complicated.
>
>
> Which list are you=C2=A0referring to? For all the ones in the draft, th=
e
> peer needs access to all the elements so I don't think a hash would hel=
p.
> =C2=A0
>
>     -=C2=A0VERSION_NEGOTIATION_ERROR vs drop - I=E2=80=99m not sure it =
is a good
>     idea to close the connection. The initials are public so it is
>     possible to inject false versions. There are probably many other
>     similar attacks we don=E2=80=99t bother with, but still=C2=A0=E2=80=
=A6
>
>
> Once we're this far in the handshake, we cannot recover from this
> error. Dropping the packet will only make things worse..

Can we think about that some more?

It is true that there are many ways to wreck a connection if the
attacker can freely tweak bits in the client hello. There is no need to
mess with transport parameters -- just changing the value of the client
Random will do that. The server will create a connection context and
send a reply, but the client won't compute the proper handshake key and
the connection will fail.

An attacker on path can kill all packets and close the connection, but
an attacker on the side can only inject "magic" packets. The VN could
become one such magic packet. Can the man on the side send the VN
quickly, so the client sends a "VN inspired" client hello? What would it
take to ensure that the connection is robust against such attacks?

-- Christian Huitema


--------------BC2EC1221426F0E13FCBD6B9
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>
    <p><br>
    </p>
    <div class="moz-cite-prefix">On 11/4/2019 2:09 PM, David Schinazi
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAPDSy+5obMbiLDKYKXXg1ZthoMqyg60KD+6HR69CQqiEHb6W7g@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div>Thanks for reading Mikkel! Responses inline.</div>
        <br>
        <div class="gmail_quote">
          <div dir="ltr" class="gmail_attr">On Mon, Nov 4, 2019 at 1:47
            PM Mikkel FahnÃ¸e JÃ¸rgensen &lt;<a
              href="mailto:mikkelfj@gmail.com" moz-do-not-send="true">mikkelfj@gmail.com</a>&gt;
            wrote:<br>
          </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div style="overflow-wrap: break-word;">
              <div id="gmail-m_-6391629696368244571bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px;color:rgb(0,0,0);margin:0px">
                <div id="gmail-m_-6391629696368244571bloop_customfont"
                  style="margin:0px">(reposting on proper topic)</div>
                <div id="gmail-m_-6391629696368244571bloop_customfont"
                  style="margin:0px"><br>
                </div>
                <div id="gmail-m_-6391629696368244571bloop_customfont"
                  style="margin:0px">Some random observations reading
                  through the document</div>
                <div id="gmail-m_-6391629696368244571bloop_customfont"
                  style="margin:0px"><br>
                </div>
                <div id="gmail-m_-6391629696368244571bloop_customfont"
                  style="margin:0px">- Is the order relevant in the
                  receiver version list?</div>
              </div>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>Yes all lists of versions are ordered.</div>
          <div>Â </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div style="overflow-wrap: break-word;">
              <div id="gmail-m_-6391629696368244571bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px;color:rgb(0,0,0);margin:0px">
                <div id="gmail-m_-6391629696368244571bloop_customfont"
                  style="margin:0px">- It is tempting to just hash the
                  received version list, but that requires agreeing on
                  an algorithm, unless the algorithm is stated to be
                  specific to that version, which is complicated.</div>
              </div>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>Which list are youÂ referring to? For all the ones in the
            draft, the peer needs access to all the elements so I don't
            think a hash would help.</div>
          <div>Â </div>
          <blockquote class="gmail_quote" style="margin:0px 0px 0px
            0.8ex;border-left:1px solid
            rgb(204,204,204);padding-left:1ex">
            <div style="overflow-wrap: break-word;">
              <div id="gmail-m_-6391629696368244571bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px;color:rgb(0,0,0);margin:0px">
                <div id="gmail-m_-6391629696368244571bloop_customfont"
                  style="font-family:&quot;helvetica
                  Neue&quot;,helvetica;font-size:14px;margin:0px">-Â <font
                    size="3">VERSION_NEGOTIATION_ERROR vs drop - Iâ€™m not
                    sure it is a good idea to close the connection. The
                    initials are public so it is possible to inject
                    false versions. There are probably many other
                    similar attacks we donâ€™t bother with, but stillÂ </font><font
                    size="3">â€¦</font></div>
              </div>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>Once we're this far in the handshake, we cannot recover
            from this error. Dropping the packet will only make things
            worse..</div>
        </div>
      </div>
    </blockquote>
    <p>Can we think about that some more?</p>
    <p>It is true that there are many ways to wreck a connection if the
      attacker can freely tweak bits in the client hello. There is no
      need to mess with transport parameters -- just changing the value
      of the client Random will do that. The server will create a
      connection context and send a reply, but the client won't compute
      the proper handshake key and the connection will fail.</p>
    <p>An attacker on path can kill all packets and close the
      connection, but an attacker on the side can only inject "magic"
      packets. The VN could become one such magic packet. Can the man on
      the side send the VN quickly, so the client sends a "VN inspired"
      client hello? What would it take to ensure that the connection is
      robust against such attacks?</p>
    <p>-- Christian Huitema<br>
    </p>
  </body>
</html>

--------------BC2EC1221426F0E13FCBD6B9--


From nobody Mon Nov  4 14:35:30 2019
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 C57BF120043 for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 14:35:28 -0800 (PST)
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_HELO_NONE=0.001, 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 2k3oltW0sxcB for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 14:35:25 -0800 (PST)
Received: from mail-ed1-x532.google.com (mail-ed1-x532.google.com [IPv6:2a00:1450:4864:20::532]) (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 8010912009C for <quic@ietf.org>; Mon,  4 Nov 2019 14:35:24 -0800 (PST)
Received: by mail-ed1-x532.google.com with SMTP id d23so11793996edr.5 for <quic@ietf.org>; Mon, 04 Nov 2019 14:35:24 -0800 (PST)
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=p2ieLO38DUkHjnoyxH2AyanDZCwUDmB/dFqpo0Pm/KU=; b=Ik9NkOuQx2yd1MiexHdEEEQ5xr/9cYTgx1aZeV4R77Y/7ilgJYcBKZYk3XDEopIIV3 UoIAwDTWvwpIlYHVXZ6ulIpFF5OzSLFUvUhVyTzZDqlmFOrX/TtINMdg49DFlZinW61e 0HU01KoncTiTZM8ln7Nl1iDjwS6bEtkSaj8PFN+VAh2zetb8HvQRKN0t183uWP/HAlp1 ymW+tBiWukeK/Zopx3ghGE1p/kihkkPJiEdiq7Hhg0GrDxw91rCiEfMMiKZnVP5WPOSw 4SAfpODP5IJW1XcWSh3y+S8v9G158TT9uKTYGuxJqjiTrr3DwGagR1cAocWv+z7Tiu7R mQ2w==
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=p2ieLO38DUkHjnoyxH2AyanDZCwUDmB/dFqpo0Pm/KU=; b=gJlyAMCQ31gAYBGGCNszPlPXPO9eZNDrqBDVlEwdl3vhLxHwqfAZ0NKhGIrJ/zLPOq wFJG/g7CBvBKyusjSOf+DnNQGqs/Nhv0EXof4kuICFPbvt8FYQrYsqorJYa5JHscIjO6 Dioh85lz4e3hdToCO8ugpDyRLdlFDEqqe5G46H2Y1Y525OdbLBm7HXtxVj5wsMzQfbR7 ++/ZtBl50zbIpHh9yF87fjVYinqpzWLjF09kBTdYUnL5qTmK8UNXCI/E3SqWEnTx0qDo yAdVZrvwe0zbzpbH1qq7Ie/RFMhcONiWr9KL4l7rMpZrLchKXINXMk6J62u2p5QB8PyJ +qxQ==
X-Gm-Message-State: APjAAAXlLq+pe8V2ZbTfpaGdULAOKel3FgzrFSXKbvgU86GVmouIZLC8 12SdEc5XBQWrChyymYhMfrTM8M1KuuVuYojMiJM=
X-Google-Smtp-Source: APXvYqwvCWUF+PTWzYSujy1BsyJa9tMQuBFC7L95siEjAYLcN8IqyFQOaNhIkx4nKQcLccw7XeaPulrhUMFEwbomh4g=
X-Received: by 2002:a17:906:1da1:: with SMTP id u1mr27081213ejh.275.1572906923013;  Mon, 04 Nov 2019 14:35:23 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Mon, 4 Nov 2019 23:35:22 +0100
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <CAPDSy+5obMbiLDKYKXXg1ZthoMqyg60KD+6HR69CQqiEHb6W7g@mail.gmail.com>
References: <CAPDSy+4wrhqejh9k8=G7W267EgcT5Z2sDK7ZBGKtNn5kkbXGfg@mail.gmail.com> <CAN1APdcZv-MtwRT77++r6EKdzJUc1NKEJfY4CZeOSaK50nPZYg@mail.gmail.com> <CAPDSy+5obMbiLDKYKXXg1ZthoMqyg60KD+6HR69CQqiEHb6W7g@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Mon, 4 Nov 2019 23:35:22 +0100
Message-ID: <CAN1APdence3-Hme+q-B_tasXJJpdxMqFpYFuR0gOgM8tMc-HNQ@mail.gmail.com>
Subject: Re: QUIC Version Negotiation Extension
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: QUIC <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000693cab05968cee05"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/SZtg2ChpsG1_QT7ICfEwaNkPuMY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 22:35:29 -0000

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

Response also inline


On Mon, Nov 4, 2019 at 1:47 PM Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@=
gmail.com>
wrote:

> (reposting on proper topic)
>
> Some random observations reading through the document
>
> - Is the order relevant in the receiver version list?
>

Yes all lists of versions are ordered.

I might have missed it, but otherwise I think this should be mentioned
explicitly.



> - It is tempting to just hash the received version list, but that require=
s
> agreeing on an algorithm, unless the algorithm is stated to be specific t=
o
> that version, which is complicated.
>

Which list are you referring to? For all the ones in the draft, the peer
needs access to all the elements so I don't think a hash would help.

I am referring the received list. The client receives the list. The server
(modulo redeployment/routing) knows its own list and does not need to read
it, it just needs proof that the response matches what it initially sent.
This could be done with a hash. (If I understand correctly). But maybe not
because the list is filtered by clients input so that would be many hashes
to track.



> - VERSION_NEGOTIATION_ERROR vs drop - I=E2=80=99m not sure it is a good i=
dea to
> close the connection. The initials are public so it is possible to inject
> false versions. There are probably many other similar attacks we don=E2=
=80=99t
> bother with, but still =E2=80=A6
>

Once we're this far in the handshake, we cannot recover from this error.
Dropping the packet will only make things worse.

It is that a given across all versions, without mentioning it explicitly
here? This links to the at most one roundtrip.



> - Downgrade - I=E2=80=99m a bit worried about state management and server
> redeployments. A server could reject a valid packet because an Initial wa=
s
> routed to a new server. (Reading further, I see this is addressed). This =
is
> probably a pragmatic solution, but it has an assumption about eventual
> global coordination. I suspect something could be done here with tokens o=
r
> CID routing, but it is not trivial.
>

Sounds interesting. Do you have a concrete proposal?

Not off hand, but the idea is that the server encodes some context in a
token, that an upgraded server can understand such that it can either
impersonate the old version or reject the handshake. As for CID routing: (I
don=E2=80=99t recall if new initials with new version must carry same origi=
nal CID,
and this might be version specific) - but if the a second Initial routes
the same place, similar to 0-RTT, you can limit the impact of server
deployment coordination to the one or the few servers affected by that CID.
If a version negotiation packet decides a new CID via the destination CID
field, a server farm is also able to route traffic to a segment with a
predictable version scope - for example by never updating some servers on
even hours and always redirect vneg to a subcluster that is not upgrading
and which therefor has a predictable version scope.




> - Security Considerations - perhaps it is worth noting the transport
> parameters need additional protection beyond the Initial packet protectio=
n?
> This follows from TLS, but if TLS is not being used, this can version
> negotiation even if other parts of the protocol version is not sensitive =
to
> this in that particular version.
>

draft-ietf-quic-transport section 7 requires transport parameters to be
authenticated.

but that is for QUIC v1. QUIC v3 might be for constrained devices that do
not use TLS and which do not migrate and which only has two non-hardcoded
transport parameters which are verified in 1-RTT in order to achieve a
light handshake. What would vneg do then? Notably such a version would
depend heavily on vneg because it really needs the one version that works
with its hardware accelerator, or whatever.

- Improve discussion of Previously Attempted Version. While the
> requirements are readable, the purpose of doing this check is less obviou=
s.
> Presumably this deals with downgrade attacks, but more explanation would =
be
> appreciated.
>

The downgrade prevention section discusses the purpose of this field. What
details do you think we should add?

Generally QUIC does not argue why something is done, although sometimes
providing motivation (like you do here - downgrade prevention), but I=E2=80=
=99d
still like to better understand why this prevents a downgrade and why a
downgrade is such a bad thing, and how such an attack could happen, and why
comparing the previous version would prevent that from happening. Because
this is such a core element if the entire document.

--000000000000693cab05968cee05
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">Response also inline=
</div> <div><blockquote type=3D"cite" class=3D"clean_bq" style=3D"font-fami=
ly:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-caps:norma=
l;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px=
;text-transform:none;white-space:normal;word-spacing:0px;text-decoration:no=
ne"><span><div><div><div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D=
"ltr" class=3D"gmail_attr"><br class=3D"Apple-interchange-newline">On Mon, =
Nov 4, 2019 at 1:47 PM Mikkel Fahn=C3=B8e J=C3=B8rgensen &lt;<a href=3D"mai=
lto:mikkelfj@gmail.com">mikkelfj@gmail.com</a>&gt; wrote:<br></div><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-wid=
th:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padding-l=
eft:1ex"><div style=3D"overflow-wrap: break-word;"><div id=3D"gmail-m_-6391=
629696368244571bloop_customfont" style=3D"font-family:Helvetica,Arial;font-=
size:13px;color:rgb(0,0,0);margin:0px"><div id=3D"gmail-m_-6391629696368244=
571bloop_customfont" style=3D"margin:0px">(reposting on proper topic)</div>=
<div id=3D"gmail-m_-6391629696368244571bloop_customfont" style=3D"margin:0p=
x"><br></div><div id=3D"gmail-m_-6391629696368244571bloop_customfont" style=
=3D"margin:0px">Some random observations reading through the document</div>=
<div id=3D"gmail-m_-6391629696368244571bloop_customfont" style=3D"margin:0p=
x"><br></div><div id=3D"gmail-m_-6391629696368244571bloop_customfont" style=
=3D"margin:0px">- Is the order relevant in the receiver version list?</div>=
</div></div></blockquote><div><br></div><div>Yes all lists of versions are =
ordered.</div></div></div></div></div></span></blockquote></div><p>I might =
have missed it, but otherwise I think this should be mentioned explicitly.<=
/p><div><div><div><blockquote type=3D"cite" class=3D"clean_bq" style=3D"fon=
t-family:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-caps=
:normal;font-weight:normal;letter-spacing:normal;text-align:start;text-inde=
nt:0px;text-transform:none;white-space:normal;word-spacing:0px;text-decorat=
ion:none"><span><div><div><div dir=3D"ltr"><div class=3D"gmail_quote"><div>=
=C2=A0</div><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(20=
4,204,204);padding-left:1ex"><div style=3D"overflow-wrap: break-word;"><div=
 id=3D"gmail-m_-6391629696368244571bloop_customfont" style=3D"font-family:H=
elvetica,Arial;font-size:13px;color:rgb(0,0,0);margin:0px"><div id=3D"gmail=
-m_-6391629696368244571bloop_customfont" style=3D"margin:0px">- It is tempt=
ing to just hash the received version list, but that requires agreeing on a=
n algorithm, unless the algorithm is stated to be specific to that version,=
 which is complicated.</div></div></div></blockquote><div><br></div><div>Wh=
ich list are you=C2=A0referring to? For all the ones in the draft, the peer=
 needs access to all the elements so I don&#39;t think a hash would help.</=
div></div></div></div></div></span></blockquote></div><p>I am referring the=
 received list. The client receives the list. The server (modulo redeployme=
nt/routing) knows its own list and does not need to read it, it just needs =
proof that the response matches what it initially sent. This could be done =
with a hash. (If I understand correctly). But maybe not because the list is=
 filtered by clients input so that would be many hashes to track.</p></div>=
<div><div><blockquote type=3D"cite" class=3D"clean_bq" style=3D"font-family=
:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-caps:normal;=
font-weight:normal;letter-spacing:normal;text-align:start;text-indent:0px;t=
ext-transform:none;white-space:normal;word-spacing:0px;text-decoration:none=
"><span><div><div><div dir=3D"ltr"><div class=3D"gmail_quote"><div>=C2=A0</=
div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bor=
der-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,20=
4);padding-left:1ex"><div style=3D"overflow-wrap: break-word;"><div id=3D"g=
mail-m_-6391629696368244571bloop_customfont" style=3D"font-family:Helvetica=
,Arial;font-size:13px;color:rgb(0,0,0);margin:0px"><div id=3D"gmail-m_-6391=
629696368244571bloop_customfont" style=3D"font-family:&quot;helvetica Neue&=
quot;,helvetica;font-size:14px;margin:0px">-=C2=A0<font size=3D"3">VERSION_=
NEGOTIATION_ERROR vs drop - I=E2=80=99m not sure it is a good idea to close=
 the connection. The initials are public so it is possible to inject false =
versions. There are probably many other similar attacks we don=E2=80=99t bo=
ther with, but still=C2=A0</font><font size=3D"3">=E2=80=A6</font></div></d=
iv></div></blockquote><div><br></div><div>Once we&#39;re this far in the ha=
ndshake, we cannot recover from this error. Dropping the packet will only m=
ake things worse.</div></div></div></div></div></span></blockquote></div><p=
>It is that a given across all versions, without mentioning it explicitly h=
ere? This links to the at most one roundtrip.</p><div><div><blockquote type=
=3D"cite" class=3D"clean_bq" style=3D"font-family:Helvetica,Arial;font-size=
:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-=
spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-s=
pace:normal;word-spacing:0px;text-decoration:none"><span><div><div><div dir=
=3D"ltr"><div class=3D"gmail_quote"><div>=C2=A0</div><blockquote class=3D"g=
mail_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 =
style=3D"overflow-wrap: break-word;"><div id=3D"gmail-m_-639162969636824457=
1bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;colo=
r:rgb(0,0,0);margin:0px"><div style=3D"font-family:&quot;helvetica Neue&quo=
t;,helvetica;font-size:14px">- Downgrade - I=E2=80=99m a bit worried about =
state management and server redeployments. A server could reject a valid pa=
cket because an Initial was routed to a new server. (Reading further, I see=
 this is addressed). This is probably a pragmatic solution, but it has an a=
ssumption about eventual global coordination. I suspect something could be =
done here with tokens or CID routing, but it is not trivial.</div></div></d=
iv></blockquote><div><br></div><div>Sounds interesting. Do you have a concr=
ete proposal?</div></div></div></div></div></span></blockquote></div><p>Not=
 off hand, but the idea is that the server encodes some context in a token,=
 that an upgraded server can understand such that it can either impersonate=
 the old version or reject the handshake. As for CID routing: (I don=E2=80=
=99t recall if new initials with new version must carry same original CID, =
and this might be version specific) - but if the a second Initial routes th=
e same place, similar to 0-RTT, you can limit the impact of server deployme=
nt coordination to the one or the few servers affected by that CID. If a ve=
rsion negotiation packet decides a new CID via the destination CID field, a=
 server farm is also able to route traffic to a segment with a predictable =
version scope - for example by never updating some servers on even hours an=
d always redirect vneg to a subcluster that is not upgrading and which ther=
efor has a predictable version scope.</p><div><div><blockquote type=3D"cite=
" class=3D"clean_bq" style=3D"font-family:Helvetica,Arial;font-size:13px;fo=
nt-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:=
normal;text-align:start;text-indent:0px;text-transform:none;white-space:nor=
mal;word-spacing:0px;text-decoration:none"><span><div><div><div dir=3D"ltr"=
><div class=3D"gmail_quote"><div><br class=3D"Apple-interchange-newline">=
=C2=A0</div><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(20=
4,204,204);padding-left:1ex"><div style=3D"overflow-wrap: break-word;"><div=
 id=3D"gmail-m_-6391629696368244571bloop_customfont" style=3D"font-family:H=
elvetica,Arial;font-size:13px;color:rgb(0,0,0);margin:0px"><span style=3D"f=
ont-family:&quot;helvetica Neue&quot;,helvetica;font-size:14px">- Security =
Considerations - perhaps it is worth noting the transport parameters need a=
dditional protection beyond the Initial packet protection? This follows fro=
m TLS, but if TLS is not being used, this can version negotiation even if o=
ther parts of the protocol version is not sensitive to this in that particu=
lar version.</span></div></div></blockquote><div><br></div><div>draft-ietf-=
quic-transport section 7 requires transport parameters to be authenticated.=
</div></div></div></div></div></span></blockquote></div><p>but that is for =
QUIC v1. QUIC v3 might be for constrained devices that do not use TLS and w=
hich do not migrate and which only has two non-hardcoded transport paramete=
rs which are verified in 1-RTT in order to achieve a light handshake. What =
would vneg do then? Notably such a version would depend heavily on vneg bec=
ause it really needs the one version that works with its hardware accelerat=
or, or whatever.</p><div><div><blockquote type=3D"cite" class=3D"clean_bq" =
style=3D"font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-=
variant-caps:normal;font-weight:normal;letter-spacing:normal;text-align:sta=
rt;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;=
text-decoration:none"><span><div><div><div dir=3D"ltr"><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 style=3D"overflow-wrap: break-word;"><div id=
=3D"gmail-m_-6391629696368244571bloop_customfont" style=3D"font-family:Helv=
etica,Arial;font-size:13px;color:rgb(0,0,0);margin:0px"><div style=3D"font-=
family:&quot;helvetica Neue&quot;,helvetica;font-size:14px"><div>- Improve =
discussion of Previously Attempted Version. While the requirements are read=
able, the purpose of doing this check is less obvious. Presumably this deal=
s with downgrade attacks, but more explanation would be appreciated.</div><=
/div></div></div></blockquote><div><br></div><div>The downgrade prevention =
section discusses the purpose of this field. What details do you think we s=
hould add?</div></div></div></div></div></span></blockquote></div><p>Genera=
lly QUIC does not argue why something is done, although sometimes providing=
 motivation (like you do here - downgrade prevention), but I=E2=80=99d stil=
l like to better understand why this prevents a downgrade and why a downgra=
de is such a bad thing, and how such an attack could happen, and why compar=
ing the previous version would prevent that from happening. Because this is=
 such a core element if the entire document.</p><div><br></div></div></div>=
</div></div></div></body></html>

--000000000000693cab05968cee05--


From nobody Mon Nov  4 14:45:57 2019
Return-Path: <dschinazi.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 5EC291207FC for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 14:45:51 -0800 (PST)
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_HELO_NONE=0.001, 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 4_kLlZRAigpo for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 14:45:49 -0800 (PST)
Received: from mail-lf1-x135.google.com (mail-lf1-x135.google.com [IPv6:2a00:1450:4864:20::135]) (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 9177E12022E for <quic@ietf.org>; Mon,  4 Nov 2019 14:45:48 -0800 (PST)
Received: by mail-lf1-x135.google.com with SMTP id j5so13514835lfh.10 for <quic@ietf.org>; Mon, 04 Nov 2019 14:45:48 -0800 (PST)
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=mu4rdKK2D25XV4Y79uMK1+yTAAuBlifVvw9S5klDuHg=; b=Ej8wAqbxfrwXYXiEfkOMKoOZoYiJFF20gtbFTU4dcFYOPL6UnPlOjEvrJbnp6TEUP9 SyaYElDxaCYKf/LZn6WlH4x2wyzht3tXCEcjFEtgFUJ4GSy+W7O1K8XeFl7iH+PQ55p3 L54oS2z8VkJ+wiFhhUSs4nd8n84faaxBqez/5freTcfBpTJzPHpkFkCwbL0YS4qn0Q8F SUdpyAjukJCXE9IUV+YUhxPwoE/uhu6wS9E9oUNUF8zdX5r134prfwKkg/P402UU3QPD dxh7pQG3JVj7j2xCVhvpRkH/fX0YNY6R0QFTbEhcRn0hfpQbrDMcKHBkQzox/fioIvEZ rObA==
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=mu4rdKK2D25XV4Y79uMK1+yTAAuBlifVvw9S5klDuHg=; b=hNoKivlhcG9Up7Pnf/vN6e3jetako7WD3z28fOS5HzoKPdDtPy0j2SO2In3eZspJuE 3WrwDreBbcFYQlXDqxH4eFRY1o6VO7PmhkWTUv8WywQx9Oj8MqSoipuQq3k8g6ajX84p xakMIbkTC7eOLBryqvhIubWKip8n8CXLeW6jyS4xtYKE2D4dvkGBuP/X2ITDgIr+SiuF 96TFq7+zX4Sfsh0pxewTRf3JsFvN3QwknQhlIFuLReOazQw3iDGeE+cfrv4bIAO2aJ+0 cByMGTkfKBCEDKxvWsKlnHDZfmDpI3YIXOTy8fCI+6kEzUByv4p2di2jr0GXeJFCVBKG cplA==
X-Gm-Message-State: APjAAAUZzng32HcFI4zDrw2AiPKH/XUsBl3BW/46hDwWX13DPYxzth6c TogRkyqsvLlrJexfJwSK3dgOgRr565dkIgGSaAQ=
X-Google-Smtp-Source: APXvYqyyQTbGp/xqcu56q6VXWkUwnoQ8/2gV/Z/SJw5siFLadTywPc4MPugFXoQIFJGZtF6D2r1OgyxY9DoyoMXPJP8=
X-Received: by 2002:a19:3f0a:: with SMTP id m10mr18775116lfa.67.1572907546699;  Mon, 04 Nov 2019 14:45:46 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+4wrhqejh9k8=G7W267EgcT5Z2sDK7ZBGKtNn5kkbXGfg@mail.gmail.com> <CAN1APdcZv-MtwRT77++r6EKdzJUc1NKEJfY4CZeOSaK50nPZYg@mail.gmail.com> <CAPDSy+5obMbiLDKYKXXg1ZthoMqyg60KD+6HR69CQqiEHb6W7g@mail.gmail.com> <aa6be7bc-e4c3-e14f-8064-f511e8fbfb70@huitema.net>
In-Reply-To: <aa6be7bc-e4c3-e14f-8064-f511e8fbfb70@huitema.net>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Mon, 4 Nov 2019 14:45:35 -0800
Message-ID: <CAPDSy+6rW=rr7R_0Qa_41t3cAe9D-ctzz60Au-jO0-Er1mr5Yg@mail.gmail.com>
Subject: Re: QUIC Version Negotiation Extension
To: Christian Huitema <huitema@huitema.net>
Cc: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>,  QUIC <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000095ed6505968d134c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/eyglPdgO0otIUWFc-zRsGD-dyW4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 22:45:55 -0000

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

On Mon, Nov 4, 2019 at 2:33 PM Christian Huitema <huitema@huitema.net>
wrote:

> - VERSION_NEGOTIATION_ERROR vs drop - I=E2=80=99m not sure it is a good i=
dea to
>> close the connection. The initials are public so it is possible to injec=
t
>> false versions. There are probably many other similar attacks we don=E2=
=80=99t
>> bother with, but still =E2=80=A6
>>
>
> Once we're this far in the handshake, we cannot recover from this error.
> Dropping the packet will only make things worse..
>
> Can we think about that some more?
>
> It is true that there are many ways to wreck a connection if the attacker
> can freely tweak bits in the client hello. There is no need to mess with
> transport parameters -- just changing the value of the client Random will
> do that. The server will create a connection context and send a reply, bu=
t
> the client won't compute the proper handshake key and the connection will
> fail.
>
> An attacker on path can kill all packets and close the connection, but an
> attacker on the side can only inject "magic" packets. The VN could become
> one such magic packet. Can the man on the side send the VN quickly, so th=
e
> client sends a "VN inspired" client hello? What would it take to ensure
> that the connection is robust against such attacks?
>
While I agree it would be nice to prevent these attacks, I don't think it's
an achievable goal in QUICv1 at this point. The injection-only attacker can
already break the connection by sending a forged ServerHello, Version
Negotiation doesn't really change that. I'm not coming up with an easy way
to remove this issue.

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Mon, Nov 4, 2019 at 2:33 PM Christ=
ian Huitema &lt;<a href=3D"mailto:huitema@huitema.net">huitema@huitema.net<=
/a>&gt; wrote:</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>=
<blockquote type=3D"cite"><div dir=3D"ltr"><div class=3D"gmail_quote">
          <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
            <div>
              <div id=3D"gmail-m_949189554107658310gmail-m_-639162969636824=
4571bloop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;c=
olor:rgb(0,0,0);margin:0px">
                <div id=3D"gmail-m_949189554107658310gmail-m_-6391629696368=
244571bloop_customfont">-=C2=A0<font size=3D"3">VERSION_NEGOTIATION_ERROR v=
s drop - I=E2=80=99m not
                    sure it is a good idea to close the connection. The
                    initials are public so it is possible to inject
                    false versions. There are probably many other
                    similar attacks we don=E2=80=99t bother with, but still=
=C2=A0</font><font size=3D"3">=E2=80=A6</font></div>
              </div>
            </div>
          </blockquote>
          <div><br>
          </div>
          <div>Once we&#39;re this far in the handshake, we cannot recover
            from this error. Dropping the packet will only make things
            worse..</div>
        </div>
      </div>
    </blockquote>
    <p>Can we think about that some more?</p>
    <p>It is true that there are many ways to wreck a connection if the
      attacker can freely tweak bits in the client hello. There is no
      need to mess with transport parameters -- just changing the value
      of the client Random will do that. The server will create a
      connection context and send a reply, but the client won&#39;t compute
      the proper handshake key and the connection will fail.</p>
    <p>An attacker on path can kill all packets and close the
      connection, but an attacker on the side can only inject &quot;magic&q=
uot;
      packets. The VN could become one such magic packet. Can the man on
      the side send the VN quickly, so the client sends a &quot;VN inspired=
&quot;
      client hello? What would it take to ensure that the connection is
      robust against such attacks?</p></div></blockquote><div>While I agree=
 it would be nice to prevent these attacks, I don&#39;t think it&#39;s an a=
chievable goal in QUICv1 at this point. The injection-only attacker can alr=
eady break the connection by sending a forged ServerHello, Version Negotiat=
ion doesn&#39;t really change that. I&#39;m not coming up with an easy way =
to remove this issue.</div></div></div>

--00000000000095ed6505968d134c--


From nobody Mon Nov  4 14:56:28 2019
Return-Path: <dschinazi.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 8804D1208E6 for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 14:56:15 -0800 (PST)
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_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 zsJ6MFCYE-m8 for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 14:56:11 -0800 (PST)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::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 99133120884 for <quic@ietf.org>; Mon,  4 Nov 2019 14:56:10 -0800 (PST)
Received: by mail-lj1-x22d.google.com with SMTP id v8so3882400ljh.5 for <quic@ietf.org>; Mon, 04 Nov 2019 14:56:10 -0800 (PST)
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=kW0kOXnOZ3SkF4WEml7Z/YpKolA6LxnHRGZvvHTQdkw=; b=YWzHePGlbzMpTUmW6rsp3TfMWnf5mV+0Ur7P+OaYLE4IBgbbfx48fJjw6J2Z97Ry2U XCn++y9tyhZbSFesceWKJBFPa+KsM3AAx5Ux2NHuOZ1qnqnSXxO0b184iUv5pdo3P2ki y4zZ/vUGxq02TvaauZpIsHZgbJ5oLOW7foQxOM7H3cOWk2YbgIDnUq7czDZFF5moMNXX MaVNNB3qcPoNtJ2cX5iNp3Wwqx7XtyiWTqYT2tKmfddUj5ZHuT5bK5H2WAb94alEXaIL rdpw5k+98xccqBFznJUpcVQlIwDPuSSKHoytRc/VUcq8rmCW39Gt1l22M3CJSpdfHlb6 HTfw==
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=kW0kOXnOZ3SkF4WEml7Z/YpKolA6LxnHRGZvvHTQdkw=; b=EbWaAuY35S76OS1Qx5JhtceJ+BbAt6n6OG2pKTjN2BZ8S67cTGaURyPy2meU8/jBzA cLlZDimA83aDBLvcQaWDeoASLWj7qJYjwfbUft5Cqn/S5u7o8xPYHcpChMIuRytt9kqh Ig1/4oMuS459mGjnkthPp7HvypFb1r6EvjpWOzSeskkQbkH1vbYdN9BwdeKV7urpKJ2m NkHPcF+Vp5uKyhnUA2n28VQaz7tODAdgVnvMqgoqzJ8swtBXdoBsOjqmiQCIlQfmvPq2 s8XQBonBa8GAG2SG7Nb0x6i+xRLnFWZY+mpWlsWmiZLIjxCzvNGyrm/S4BgUfQHeNg/o L0tg==
X-Gm-Message-State: APjAAAW+Kwx+6yutGPsse7kUr2/vHmj7jEErV/AJXSrOCtK365B1B2hY niy9vS7z3zfZb8cmM5wh9C+sGHfAHpzwYl0eooc=
X-Google-Smtp-Source: APXvYqzF/6k9hXE1vmkBU4IHNTEHRy9mO1ccmzpPkzBi9MeoQK7q2dtbdoevt1dTv0NzEtMWz4q+2Fq0OYRoy4CpaPc=
X-Received: by 2002:a2e:2c19:: with SMTP id s25mr4954872ljs.26.1572908168803;  Mon, 04 Nov 2019 14:56:08 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+4wrhqejh9k8=G7W267EgcT5Z2sDK7ZBGKtNn5kkbXGfg@mail.gmail.com> <CAN1APdcZv-MtwRT77++r6EKdzJUc1NKEJfY4CZeOSaK50nPZYg@mail.gmail.com> <CAPDSy+5obMbiLDKYKXXg1ZthoMqyg60KD+6HR69CQqiEHb6W7g@mail.gmail.com> <CAN1APdence3-Hme+q-B_tasXJJpdxMqFpYFuR0gOgM8tMc-HNQ@mail.gmail.com>
In-Reply-To: <CAN1APdence3-Hme+q-B_tasXJJpdxMqFpYFuR0gOgM8tMc-HNQ@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Mon, 4 Nov 2019 14:55:57 -0800
Message-ID: <CAPDSy+6y2gQmiCdLhVXXU3d0ER=mt7+R0s5cA=EAH3HfT+k_JA@mail.gmail.com>
Subject: Re: QUIC Version Negotiation Extension
To: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
Cc: QUIC <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000aa788505968d38fd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/RPxiX-D01iAhiyin_ETEVSizDWg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 22:56:24 -0000

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

On Mon, Nov 4, 2019 at 2:35 PM Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@=
gmail.com>
wrote:

> Response also inline
>
>
> On Mon, Nov 4, 2019 at 1:47 PM Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelf=
j@gmail.com>
> wrote:
>
>> (reposting on proper topic)
>>
>> Some random observations reading through the document
>>
>> - Is the order relevant in the receiver version list?
>>
>
> Yes all lists of versions are ordered.
>
> I might have missed it, but otherwise I think this should be mentioned
> explicitly.
>
Isn't it mentioned in the definitions of these fields?

> - It is tempting to just hash the received version list, but that require=
s
>> agreeing on an algorithm, unless the algorithm is stated to be specific =
to
>> that version, which is complicated.
>>
>
> Which list are you referring to? For all the ones in the draft, the peer
> needs access to all the elements so I don't think a hash would help.
>
> I am referring the received list. The client receives the list. The serve=
r
> (modulo redeployment/routing) knows its own list and does not need to rea=
d
> it, it just needs proof that the response matches what it initially sent.
> This could be done with a hash. (If I understand correctly). But maybe no=
t
> because the list is filtered by clients input so that would be many hashe=
s
> to track.
>
I don't know what the received list is, there's nothing with that name in
the draft.

> - VERSION_NEGOTIATION_ERROR vs drop - I=E2=80=99m not sure it is a good i=
dea to
>> close the connection. The initials are public so it is possible to injec=
t
>> false versions. There are probably many other similar attacks we don=E2=
=80=99t
>> bother with, but still =E2=80=A6
>>
>
> Once we're this far in the handshake, we cannot recover from this error.
> Dropping the packet will only make things worse.
>
> It is that a given across all versions, without mentioning it explicitly
> here? This links to the at most one roundtrip.
>
That's a given across all current versions. New versions can override the
text in this spec.

> - Downgrade - I=E2=80=99m a bit worried about state management and server
>> redeployments. A server could reject a valid packet because an Initial w=
as
>> routed to a new server. (Reading further, I see this is addressed). This=
 is
>> probably a pragmatic solution, but it has an assumption about eventual
>> global coordination. I suspect something could be done here with tokens =
or
>> CID routing, but it is not trivial.
>>
>
> Sounds interesting. Do you have a concrete proposal?
>
> Not off hand, but the idea is that the server encodes some context in a
> token, that an upgraded server can understand such that it can either
> impersonate the old version or reject the handshake. As for CID routing: =
(I
> don=E2=80=99t recall if new initials with new version must carry same ori=
ginal CID,
> and this might be version specific) - but if the a second Initial routes
> the same place, similar to 0-RTT, you can limit the impact of server
> deployment coordination to the one or the few servers affected by that CI=
D.
> If a version negotiation packet decides a new CID via the destination CID
> field, a server farm is also able to route traffic to a segment with a
> predictable version scope - for example by never updating some servers on
> even hours and always redirect vneg to a subcluster that is not upgrading
> and which therefor has a predictable version scope.
>
The current design of connection IDs does not guarantee consistent routing
on client-generated server connection IDs, so I don't think we can rely on
it.

> - Security Considerations - perhaps it is worth noting the transport
>> parameters need additional protection beyond the Initial packet protecti=
on?
>> This follows from TLS, but if TLS is not being used, this can version
>> negotiation even if other parts of the protocol version is not sensitive=
 to
>> this in that particular version.
>>
>
> draft-ietf-quic-transport section 7 requires transport parameters to be
> authenticated.
>
> but that is for QUIC v1. QUIC v3 might be for constrained devices that do
> not use TLS and which do not migrate and which only has two non-hardcoded
> transport parameters which are verified in 1-RTT in order to achieve a
> light handshake. What would vneg do then? Notably such a version would
> depend heavily on vneg because it really needs the one version that works
> with its hardware accelerator, or whatever.
>
I think QUICv3 should also provide this property, otherwise it'll be likely
to be unsafe. If a future version doesn't have authenticated transport
parameters then we'll have to create a separate downgrade prevention
mechanism. But we can cross that bridge when we get there.

> - Improve discussion of Previously Attempted Version. While the
>> requirements are readable, the purpose of doing this check is less obvio=
us.
>> Presumably this deals with downgrade attacks, but more explanation would=
 be
>> appreciated.
>>
>
> The downgrade prevention section discusses the purpose of this field. Wha=
t
> details do you think we should add?
>
> Generally QUIC does not argue why something is done, although sometimes
> providing motivation (like you do here - downgrade prevention), but I=E2=
=80=99d
> still like to better understand why this prevents a downgrade and why a
> downgrade is such a bad thing, and how such an attack could happen, and w=
hy
> comparing the previous version would prevent that from happening. Because
> this is such a core element if the entire document.
>
It sounds like we could be clearer. Would you be able to send us a PR?

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Mon, Nov 4, 2019 at 2:35 PM Mikkel=
 Fahn=C3=B8e J=C3=B8rgensen &lt;<a href=3D"mailto:mikkelfj@gmail.com">mikke=
lfj@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><div style=3D"overflow-wrap: break-word;"><div id=3D"gmail-m_5=
351075036621202963bloop_customfont" style=3D"font-family:Helvetica,Arial;fo=
nt-size:13px;color:rgb(0,0,0);margin:0px">Response also inline</div> <div><=
blockquote type=3D"cite" style=3D"font-family:Helvetica,Arial;font-size:13p=
x;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spac=
ing:normal;text-align:start;text-indent:0px;text-transform:none;white-space=
:normal;word-spacing:0px;text-decoration:none"><span><div><div><div dir=3D"=
ltr"><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr"><br>O=
n Mon, Nov 4, 2019 at 1:47 PM Mikkel Fahn=C3=B8e J=C3=B8rgensen &lt;<a href=
=3D"mailto:mikkelfj@gmail.com" target=3D"_blank">mikkelfj@gmail.com</a>&gt;=
 wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><di=
v id=3D"gmail-m_5351075036621202963gmail-m_-6391629696368244571bloop_custom=
font" style=3D"font-family:Helvetica,Arial;font-size:13px;color:rgb(0,0,0);=
margin:0px"><div id=3D"gmail-m_5351075036621202963gmail-m_-6391629696368244=
571bloop_customfont" style=3D"margin:0px">(reposting on proper topic)</div>=
<div id=3D"gmail-m_5351075036621202963gmail-m_-6391629696368244571bloop_cus=
tomfont" style=3D"margin:0px"><br></div><div id=3D"gmail-m_5351075036621202=
963gmail-m_-6391629696368244571bloop_customfont" style=3D"margin:0px">Some =
random observations reading through the document</div><div id=3D"gmail-m_53=
51075036621202963gmail-m_-6391629696368244571bloop_customfont" style=3D"mar=
gin:0px"><br></div><div id=3D"gmail-m_5351075036621202963gmail-m_-639162969=
6368244571bloop_customfont" style=3D"margin:0px">- Is the order relevant in=
 the receiver version list?</div></div></div></blockquote><div><br></div><d=
iv>Yes all lists of versions are ordered.</div></div></div></div></div></sp=
an></blockquote></div><p>I might have missed it, but otherwise I think this=
 should be mentioned explicitly.</p></div></blockquote><div>Isn&#39;t it me=
ntioned in the definitions of these fields?</div><blockquote class=3D"gmail=
_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204=
,204);padding-left:1ex"><div style=3D"overflow-wrap: break-word;"><div><div=
><blockquote type=3D"cite" style=3D"font-family:Helvetica,Arial;font-size:1=
3px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-sp=
acing:normal;text-align:start;text-indent:0px;text-transform:none;white-spa=
ce:normal;word-spacing:0px;text-decoration:none"><span><div dir=3D"ltr"><di=
v class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0=
px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><=
div><div id=3D"gmail-m_5351075036621202963gmail-m_-6391629696368244571bloop=
_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;color:rgb(=
0,0,0);margin:0px"><div id=3D"gmail-m_5351075036621202963gmail-m_-639162969=
6368244571bloop_customfont" style=3D"margin:0px">- It is tempting to just h=
ash the received version list, but that requires agreeing on an algorithm, =
unless the algorithm is stated to be specific to that version, which is com=
plicated.</div></div></div></blockquote><div><br></div><div>Which list are =
you=C2=A0referring to? For all the ones in the draft, the peer needs access=
 to all the elements so I don&#39;t think a hash would help.</div></div></d=
iv></span></blockquote></div><p>I am referring the received list. The clien=
t receives the list. The server (modulo redeployment/routing) knows its own=
 list and does not need to read it, it just needs proof that the response m=
atches what it initially sent. This could be done with a hash. (If I unders=
tand correctly). But maybe not because the list is filtered by clients inpu=
t so that would be many hashes to track.</p></div></div></blockquote><div>I=
 don&#39;t know what the received list is, there&#39;s nothing with that na=
me in the draft.</div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><di=
v style=3D"overflow-wrap: break-word;"><div><blockquote type=3D"cite" style=
=3D"font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-varia=
nt-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;te=
xt-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-=
decoration:none"><span><div dir=3D"ltr"><div class=3D"gmail_quote"><blockqu=
ote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px=
 solid rgb(204,204,204);padding-left:1ex"><div><div id=3D"gmail-m_535107503=
6621202963gmail-m_-6391629696368244571bloop_customfont" style=3D"font-famil=
y:Helvetica,Arial;font-size:13px;color:rgb(0,0,0);margin:0px"><div id=3D"gm=
ail-m_5351075036621202963gmail-m_-6391629696368244571bloop_customfont" styl=
e=3D"font-family:&quot;helvetica Neue&quot;,helvetica;font-size:14px;margin=
:0px">-=C2=A0<font size=3D"3">VERSION_NEGOTIATION_ERROR vs drop - I=E2=80=
=99m not sure it is a good idea to close the connection. The initials are p=
ublic so it is possible to inject false versions. There are probably many o=
ther similar attacks we don=E2=80=99t bother with, but still=C2=A0</font><f=
ont size=3D"3">=E2=80=A6</font></div></div></div></blockquote><div><br></di=
v><div>Once we&#39;re this far in the handshake, we cannot recover from thi=
s error. Dropping the packet will only make things worse.</div></div></div>=
</span></blockquote></div><p>It is that a given across all versions, withou=
t mentioning it explicitly here? This links to the at most one roundtrip.</=
p></div></blockquote><div>That&#39;s a given across all current versions. N=
ew versions can override the text in this spec.</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"><div style=3D"overflow-wrap: break-word;"><div>=
<blockquote type=3D"cite" style=3D"font-family:Helvetica,Arial;font-size:13=
px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spa=
cing:normal;text-align:start;text-indent:0px;text-transform:none;white-spac=
e:normal;word-spacing:0px;text-decoration:none"><span><div dir=3D"ltr"><div=
 class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><d=
iv><div id=3D"gmail-m_5351075036621202963gmail-m_-6391629696368244571bloop_=
customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;color:rgb(0=
,0,0);margin:0px"><div style=3D"font-family:&quot;helvetica Neue&quot;,helv=
etica;font-size:14px">- Downgrade - I=E2=80=99m a bit worried about state m=
anagement and server redeployments. A server could reject a valid packet be=
cause an Initial was routed to a new server. (Reading further, I see this i=
s addressed). This is probably a pragmatic solution, but it has an assumpti=
on about eventual global coordination. I suspect something could be done he=
re with tokens or CID routing, but it is not trivial.</div></div></div></bl=
ockquote><div><br></div><div>Sounds interesting. Do you have a concrete pro=
posal?</div></div></div></span></blockquote></div><p>Not off hand, but the =
idea is that the server encodes some context in a token, that an upgraded s=
erver can understand such that it can either impersonate the old version or=
 reject the handshake. As for CID routing: (I don=E2=80=99t recall if new i=
nitials with new version must carry same original CID, and this might be ve=
rsion specific) - but if the a second Initial routes the same place, simila=
r to 0-RTT, you can limit the impact of server deployment coordination to t=
he one or the few servers affected by that CID. If a version negotiation pa=
cket decides a new CID via the destination CID field, a server farm is also=
 able to route traffic to a segment with a predictable version scope - for =
example by never updating some servers on even hours and always redirect vn=
eg to a subcluster that is not upgrading and which therefor has a predictab=
le version scope.</p></div></blockquote><div>The current design of connecti=
on IDs does not guarantee consistent routing on client-generated server con=
nection IDs, so I don&#39;t think we can rely on it.</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 style=3D"overflow-wrap: break-word;">=
<div><blockquote type=3D"cite" style=3D"font-family:Helvetica,Arial;font-si=
ze:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;lette=
r-spacing:normal;text-align:start;text-indent:0px;text-transform:none;white=
-space:normal;word-spacing:0px;text-decoration:none"><span><div dir=3D"ltr"=
><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"marg=
in:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1e=
x"><div><div id=3D"gmail-m_5351075036621202963gmail-m_-6391629696368244571b=
loop_customfont" style=3D"font-family:Helvetica,Arial;font-size:13px;color:=
rgb(0,0,0);margin:0px"><span style=3D"font-family:&quot;helvetica Neue&quot=
;,helvetica;font-size:14px">- Security Considerations - perhaps it is worth=
 noting the transport parameters need additional protection beyond the Init=
ial packet protection? This follows from TLS, but if TLS is not being used,=
 this can version negotiation even if other parts of the protocol version i=
s not sensitive to this in that particular version.</span></div></div></blo=
ckquote><div><br></div><div>draft-ietf-quic-transport section 7 requires tr=
ansport parameters to be authenticated.</div></div></div></span></blockquot=
e></div><p>but that is for QUIC v1. QUIC v3 might be for constrained device=
s that do not use TLS and which do not migrate and which only has two non-h=
ardcoded transport parameters which are verified in 1-RTT in order to achie=
ve a light handshake. What would vneg do then? Notably such a version would=
 depend heavily on vneg because it really needs the one version that works =
with its hardware accelerator, or whatever.</p></div></blockquote><div>I th=
ink QUICv3 should also provide this property, otherwise it&#39;ll be likely=
 to be unsafe. If a future version doesn&#39;t have authenticated transport=
 parameters then we&#39;ll have to create a separate downgrade prevention m=
echanism. But we can cross that bridge when we get there.</div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><div style=3D"overflow-wrap: break-wo=
rd;"><div><div><blockquote type=3D"cite" style=3D"font-family:Helvetica,Ari=
al;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:no=
rmal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:=
none;white-space:normal;word-spacing:0px;text-decoration:none"><span><div><=
div><div dir=3D"ltr"><div class=3D"gmail_quote"><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex"><div><div id=3D"gmail-m_5351075036621202963gmail-m_-=
6391629696368244571bloop_customfont" style=3D"font-family:Helvetica,Arial;f=
ont-size:13px;color:rgb(0,0,0);margin:0px"><div style=3D"font-family:&quot;=
helvetica Neue&quot;,helvetica;font-size:14px"><div>- Improve discussion of=
 Previously Attempted Version. While the requirements are readable, the pur=
pose of doing this check is less obvious. Presumably this deals with downgr=
ade attacks, but more explanation would be appreciated.</div></div></div></=
div></blockquote><div><br></div><div>The downgrade prevention section discu=
sses the purpose of this field. What details do you think we should add?</d=
iv></div></div></div></div></span></blockquote></div><p>Generally QUIC does=
 not argue why something is done, although sometimes providing motivation (=
like you do here - downgrade prevention), but I=E2=80=99d still like to bet=
ter understand why this prevents a downgrade and why a downgrade is such a =
bad thing, and how such an attack could happen, and why comparing the previ=
ous version would prevent that from happening. Because this is such a core =
element if the entire document.</p></div></div></blockquote><div>It sounds =
like we could be clearer. Would you be able to send us a PR?</div></div></d=
iv>

--000000000000aa788505968d38fd--


From nobody Mon Nov  4 15:07:06 2019
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 0C6751207FB for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 15:07:06 -0800 (PST)
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_HELO_NONE=0.001, 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 9vENS3MjZtJK for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 15:07:04 -0800 (PST)
Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) (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 D93381200FA for <quic@ietf.org>; Mon,  4 Nov 2019 15:07:03 -0800 (PST)
Received: by mail-ed1-x52e.google.com with SMTP id w3so12219946edt.2 for <quic@ietf.org>; Mon, 04 Nov 2019 15:07:03 -0800 (PST)
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=Yfkv6Evd2xoLXjCI7c2F2kJ8rWrGEU5cYJK9KrsOVa0=; b=bRRGYdp2Nfh9hPggPG5ubXdpc3yfvMZXPm2nfnRPqQXX51Sw4jZ/IF3wWaVZOs6CUN 1NdDSaDh1QlSqtpVz+wmAR6C2Gc+23lWFe4m0X+5gAcaahBTNtX+lKdt9I9wTgj/kbUG 8Sz6RW/taxh2Bdi8XpuVY7QbBDCwwM4lBZzv5viCN1UgGoxWbdweriIYjhK9CJGD4kBq 9gWW6ouEmSjTD+CGq3buK7KOuGta8Led58XmWz0yFx6L1EYQNyalQ3r5arEsrKDJreNQ vwwF9BVdaYdmbOY8SBpXllGM6nlRIbZy7Hfr+NQ+IDQNVgRrecLIiOCBIyP+d8Tljb+F p0lw==
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=Yfkv6Evd2xoLXjCI7c2F2kJ8rWrGEU5cYJK9KrsOVa0=; b=PHa68OulqTzYXyTZ0ScyKo7OrCKBi9sJil1B2f2RIgBjKH+iZSMR4tFcw/UnAu/RtM jmm1GCHg6h462ohZClKUwGX7HvjSGjX8YipIhS+DoJpqZXhbKMqswOAb7t2zf+sAid4L O8UeKzzFE9oc5SBhMae+XsLYMW1P7tRpWxRu0NBxfxTarR9wfyr/6YjezSqUTGxgzv0V Kj7HzwgMzjmxy4RcesTBSsA2IAsbYA9j7KQTcGNcBVuk1LzTdTTz2iRrVH9gQnwbbkWv XehNlmrxf5CErKxwXuaGEbVmdj0yEFDCtX5C6PTlE7dE9zLI4xNs6fGzlp7FGTeSRAnA flvg==
X-Gm-Message-State: APjAAAUT4y+xHCkvSJJo6qxXrBlCWBELvuN80gYnzQ+x2Xc+0/UrAI8E Hha7mitCCkTVaejNTbU0K1eJUpsx1DeI1VMvaaA=
X-Google-Smtp-Source: APXvYqx5GE00XoM9EHbNoey7y6B6LSRqJIf8An2V+uYxnQOkBKcVnlBXzxG16uUC/gM6dc3hD33WuRQ5Qho1N5g93qE=
X-Received: by 2002:a50:9930:: with SMTP id k45mr32196558edb.134.1572908822536;  Mon, 04 Nov 2019 15:07:02 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 5 Nov 2019 00:07:01 +0100
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <CAPDSy+6y2gQmiCdLhVXXU3d0ER=mt7+R0s5cA=EAH3HfT+k_JA@mail.gmail.com>
References: <CAPDSy+4wrhqejh9k8=G7W267EgcT5Z2sDK7ZBGKtNn5kkbXGfg@mail.gmail.com> <CAN1APdcZv-MtwRT77++r6EKdzJUc1NKEJfY4CZeOSaK50nPZYg@mail.gmail.com> <CAPDSy+5obMbiLDKYKXXg1ZthoMqyg60KD+6HR69CQqiEHb6W7g@mail.gmail.com> <CAN1APdence3-Hme+q-B_tasXJJpdxMqFpYFuR0gOgM8tMc-HNQ@mail.gmail.com> <CAPDSy+6y2gQmiCdLhVXXU3d0ER=mt7+R0s5cA=EAH3HfT+k_JA@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Tue, 5 Nov 2019 00:07:01 +0100
Message-ID: <CAN1APdczRvpargzKELJXOgYg1Yp+iv-5v_7RbvJZMWNHFDqCrw@mail.gmail.com>
Subject: Re: QUIC Version Negotiation Extension
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: QUIC <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a1a76905968d5f1d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/iPnOeffD2pbh65rylkotaBL-BDU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 23:07:06 -0000

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

Yes all lists of versions are ordered.
>
> I might have missed it, but otherwise I think this should be mentioned
> explicitly.
>
Isn't it mentioned in the definitions of these fields?

Yes, rereading that passage, it does mention order.


>> - It is tempting to just hash the received version list, but that
>> requires agreeing on an algorithm, unless the algorithm is stated to be
>> specific to that version, which is complicated.
>>
>
> Which list are you referring to? For all the ones in the draft, the peer
> needs access to all the elements so I don't think a hash would help.
>
> I am referring the received list. The client receives the list. The serve=
r
> (modulo redeployment/routing) knows its own list and does not need to rea=
d
> it, it just needs proof that the response matches what it initially sent.
> This could be done with a hash. (If I understand correctly). But maybe no=
t
> because the list is filtered by clients input so that would be many hashe=
s
> to track.
>
I don't know what the received list is, there's nothing with that name in
the draft.


Received Negotiation Version Count + following element


The current design of connection IDs does not guarantee consistent routing
on client-generated server connection IDs, so I don't think we can rely on
it.

So this is where I=E2=80=99m not 100% on how it works, but VNEG packet does=
, at
least in principle, allow for a return destination CID, so the next Initial
packet can use that destination instead of a random original CID. And
likewise, if the response is not via VNEG, the servers initial can the same
(on known versions).

I think QUICv3 should also provide this property, otherwise it'll be likely
to be unsafe. If a future version doesn't have authenticated transport
parameters then we'll have to create a separate downgrade prevention
mechanism. But we can cross that bridge when we get there.

Sure, but perhaps mention in Security Considerations, that the design
depends on this, if it is not considered blatantly obvious.

It sounds like we could be clearer. Would you be able to send us a PR?

I=E2=80=99ll consider, but I=E2=80=99m stretched a bit thin as it is.

--000000000000a1a76905968d5f1d
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_quote"><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;borde=
r-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"><di=
v style=3D"overflow-wrap: break-word;"><div><blockquote type=3D"cite" style=
=3D"font-family:Helvetica,Arial;font-size:13px;font-style:normal;font-varia=
nt-caps:normal;font-weight:normal;letter-spacing:normal;text-align:start;te=
xt-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;text-=
decoration:none"><div><div><div dir=3D"ltr"><div class=3D"gmail_quote"><div=
><span>Yes all lists of versions are ordered.</span></div></div></div></div=
></div></blockquote></div><p>I might have missed it, but otherwise I think =
this should be mentioned explicitly.</p></div></blockquote><div>Isn&#39;t i=
t mentioned in the definitions of these fields?</div></div></div></div></di=
v></span></blockquote></div><p>Yes, rereading that passage, it does mention=
 order.</p><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><div><div dir=3D"ltr"><div class=3D"gmail_quote"><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);pad=
ding-left:1ex"><div style=3D"overflow-wrap: break-word;"><div><div><blockqu=
ote type=3D"cite" style=3D"font-family:Helvetica,Arial;font-size:13px;font-=
style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:nor=
mal;text-align:start;text-indent:0px;text-transform:none;white-space:normal=
;word-spacing:0px;text-decoration:none"><div dir=3D"ltr"><div class=3D"gmai=
l_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left-width:1px;border-left-style:solid;border-left-color:rgb(204,2=
04,204);padding-left:1ex"><div><div id=3D"gmail-m_5351075036621202963gmail-=
m_-6391629696368244571bloop_customfont" style=3D"font-family:Helvetica,Aria=
l;font-size:13px;color:rgb(0,0,0);margin:0px"><div id=3D"gmail-m_5351075036=
621202963gmail-m_-6391629696368244571bloop_customfont" style=3D"margin:0px"=
><span><br class=3D"Apple-interchange-newline">- It is tempting to just has=
h the received version list, but that requires agreeing on an algorithm, un=
less the algorithm is stated to be specific to that version, which is compl=
icated.</span></div></div></div></blockquote><div><span><br></span></div><d=
iv><span>Which list are you=C2=A0referring to? For all the ones in the draf=
t, the peer needs access to all the elements so I don&#39;t think a hash wo=
uld help.</span></div></div></div></blockquote></div><p>I am referring the =
received list. The client receives the list. The server (modulo redeploymen=
t/routing) knows its own list and does not need to read it, it just needs p=
roof that the response matches what it initially sent. This could be done w=
ith a hash. (If I understand correctly). But maybe not because the list is =
filtered by clients input so that would be many hashes to track.</p></div><=
/div></blockquote><div>I don&#39;t know what the received list is, there&#3=
9;s nothing with that name in the draft.</div></div></div></div></div></spa=
n></blockquote></div><pre class=3D"newpage" style=3D"font-size:13.3333px;ma=
rgin-top:0px;margin-bottom:0px;break-before:page;font-variant-ligatures:nor=
mal"><br></pre><pre class=3D"newpage" style=3D"font-size:13.3333px;margin-t=
op:0px;margin-bottom:0px;break-before:page;font-variant-ligatures:normal">R=
eceived Negotiation Version Count + following element</pre><pre class=3D"ne=
wpage" style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-=
before:page;font-variant-ligatures:normal"><br></pre><div><div><blockquote =
type=3D"cite" class=3D"clean_bq" style=3D"font-family:Helvetica,Arial;font-=
size:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;let=
ter-spacing:normal;text-align:start;text-indent:0px;text-transform:none;whi=
te-space:normal;word-spacing:0px;text-decoration:none"><span><div><div><div=
 dir=3D"ltr"><div class=3D"gmail_quote"><div>The current design of connecti=
on IDs does not guarantee consistent routing on client-generated server con=
nection IDs, so I don&#39;t think we can rely on it.</div></div></div></div=
></div></span></blockquote></div><p>So this is where I=E2=80=99m not 100% o=
n how it works, but VNEG packet does, at least in principle, allow for a re=
turn destination CID, so the next Initial packet can use that destination i=
nstead of a random original CID. And likewise, if the response is not via V=
NEG, the servers initial can the same (on known versions).</p><div><div><bl=
ockquote type=3D"cite" class=3D"clean_bq" style=3D"font-family:Helvetica,Ar=
ial;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:n=
ormal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform=
:none;white-space:normal;word-spacing:0px;text-decoration:none"><span><div =
dir=3D"ltr"><div class=3D"gmail_quote"><div>I think QUICv3 should also prov=
ide this property, otherwise it&#39;ll be likely to be unsafe. If a future =
version doesn&#39;t have authenticated transport parameters then we&#39;ll =
have to create a separate downgrade prevention mechanism. But we can cross =
that bridge when we get there.</div></div></div></span></blockquote></div><=
p>Sure, but perhaps mention in Security Considerations, that the design dep=
ends on this, if it is not considered blatantly obvious.</p><div><div><bloc=
kquote type=3D"cite" class=3D"clean_bq" style=3D"font-family:Helvetica,Aria=
l;font-size:13px;font-style:normal;font-variant-caps:normal;font-weight:nor=
mal;letter-spacing:normal;text-align:start;text-indent:0px;text-transform:n=
one;white-space:normal;word-spacing:0px;text-decoration:none"><span><div di=
r=3D"ltr"><div class=3D"gmail_quote"><div>It sounds like we could be cleare=
r. Would you be able to send us a PR?</div></div></div></span></blockquote>=
</div><p>I=E2=80=99ll consider, but I=E2=80=99m stretched a bit thin as it =
is.</p><div></div></div></div></div></div></body></html>

--000000000000a1a76905968d5f1d--


From nobody Mon Nov  4 15:11:43 2019
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 9B7741208D8 for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 15:11:41 -0800 (PST)
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_HELO_NONE=0.001, 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 kOIQ0mLYdnu9 for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 15:11:40 -0800 (PST)
Received: from mail-ed1-x52a.google.com (mail-ed1-x52a.google.com [IPv6:2a00:1450:4864:20::52a]) (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 DD1091207FB for <quic@ietf.org>; Mon,  4 Nov 2019 15:11:39 -0800 (PST)
Received: by mail-ed1-x52a.google.com with SMTP id l25so14548503edt.6 for <quic@ietf.org>; Mon, 04 Nov 2019 15:11:39 -0800 (PST)
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=yMFhNgDFKAbUmye4oqFPkTCBGLBhldVp2sjYWy9nSqI=; b=En+BF9F33jcdK20YQmm863ip22lbIS5Yno6D8m6jxfyuaLxRyWCQasldoPCaYIdqkl e+xLAoGB6ylMnDmgF3h6HDrDt8QryB7uNJes0Eai5WMCvo+bk3nei4zVvcMbB8v6gSWD 2sXFn6f0DAHF4QBHaZbROCf8r+u+7F85ui30z1vcwdB5fmNIPi+JFJoHPAlWVQlnIGBA 71yiceSMDNmBVhA1pY+LCRVuNRXYm4CFjx5/itQIuupgEW0E/nenJHoTWcp0YdiSlaQl +IyTCEsYSCF91mcvxAVQX7maFS2caKMx7hOfv2pw9sN/1mKROrnRUbuagx2xOMGD3caf QSMA==
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=yMFhNgDFKAbUmye4oqFPkTCBGLBhldVp2sjYWy9nSqI=; b=ITAce+NYytK8r3bKsRz20KTRpsq3CRtBfHUQWE4L+vVZIrkuXaV8b15Oyn2hJdoFeZ YHE+QUkV7QU4o3LCzUbsDugo8QxkNXF/xdRkrQvDk91jDyOhtujPTKztP2YoAUoeEZg2 qcARuwMU/w+6IEA2htbUk9NBqAVVInyn3aC8Z7+VTKqM7G/rF0I2c/68EOQjm85YhDyh wczE/sA4Ip0i+1/UvFeeBCOoAAv2oXbCel68QQWkp92QhzJc3NiH7l3vOAbhwpwxW0cR DvQz1lSzxI0GliKbFb5KhHYqruHll9uQmBjKxub2giESkV4chMMzCVzeZkNLPLjqWF1J DKWQ==
X-Gm-Message-State: APjAAAXgf87hQRKyx1R0fjhwdQMDgweZLSkB+sVrAC3JfF4ceYiAXXDq 87tWe6/EWB3U5WXpdxAnNY0Vf8NsL6DBMG0QJlY=
X-Google-Smtp-Source: APXvYqy/cqTBmFCpXAEgoELZBSk9Koqkv+mofcRIlHmE0jIL8LKtwf/npdJ/AOWps82mS61tociMrg/3KG5t75gj38w=
X-Received: by 2002:a17:906:2961:: with SMTP id x1mr26397743ejd.91.1572909098492;  Mon, 04 Nov 2019 15:11:38 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 5 Nov 2019 00:11:38 +0100
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <CAN1APdczRvpargzKELJXOgYg1Yp+iv-5v_7RbvJZMWNHFDqCrw@mail.gmail.com>
References: <CAPDSy+4wrhqejh9k8=G7W267EgcT5Z2sDK7ZBGKtNn5kkbXGfg@mail.gmail.com> <CAN1APdcZv-MtwRT77++r6EKdzJUc1NKEJfY4CZeOSaK50nPZYg@mail.gmail.com> <CAPDSy+5obMbiLDKYKXXg1ZthoMqyg60KD+6HR69CQqiEHb6W7g@mail.gmail.com> <CAN1APdence3-Hme+q-B_tasXJJpdxMqFpYFuR0gOgM8tMc-HNQ@mail.gmail.com> <CAPDSy+6y2gQmiCdLhVXXU3d0ER=mt7+R0s5cA=EAH3HfT+k_JA@mail.gmail.com> <CAN1APdczRvpargzKELJXOgYg1Yp+iv-5v_7RbvJZMWNHFDqCrw@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Tue, 5 Nov 2019 00:11:38 +0100
Message-ID: <CAN1APdfHKdUM5HWmNLV1quF5++DOwvUCH8nD+u1EVerWNQg5mg@mail.gmail.com>
Subject: Re: QUIC Version Negotiation Extension
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: QUIC <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001466a105968d7064"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ONO7-71dCoT_l0qFo6t7vIWHSjc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 23:11:42 -0000

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

Below

On 5 November 2019 at 00.07.01, Mikkel Fahn=C3=B8e J=C3=B8rgensen (mikkelfj=
@gmail.com)
wrote:

So this is where I=E2=80=99m not 100% on how it works, but VNEG packet does=
, at
least in principle, allow for a return destination CID, so the next Initial
packet can use that destination instead of a random original CID. And
likewise, if the response is not via VNEG, the servers initial can the same
(on known versions).


I came to think that because VNEG is open, an attacker could inject a VNEG
with a specific desitination CID to multiple clients and those trigger an
indirect flooding attack by concentrating traffic via previously aquired
destination CIDs. Because the servers router would/should randomize
unauthenticated CIDs an attacker cannot just inject a random CID.

--0000000000001466a105968d7064
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">Below</div> <br><p c=
lass=3D"airmail_on">On 5 November 2019 at 00.07.01, Mikkel Fahn=C3=B8e J=C3=
=B8rgensen (<a href=3D"mailto:mikkelfj@gmail.com">mikkelfj@gmail.com</a>) w=
rote:</p> <div><blockquote type=3D"cite" class=3D"clean_bq" style=3D"font-f=
amily:Helvetica,Arial;font-size:13px;font-style:normal;font-variant-caps:no=
rmal;font-weight:normal;letter-spacing:normal;text-align:start;text-indent:=
0px;text-transform:none;white-space:normal;word-spacing:0px;text-decoration=
:none"><span><div><span style=3D"color:rgb(0,0,0);font-family:&quot;helveti=
ca 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-co=
lor:rgb(255,255,255);text-decoration:none;float:none;display:inline!importa=
nt">So this is where I=E2=80=99m not 100% on how it works, but VNEG packet =
does, at least in principle, allow for a return destination CID, so the nex=
t Initial packet can use that destination instead of a random original CID.=
 And likewise, if the response is not via VNEG, the servers initial can the=
 same (on known versions).</span></div></span></blockquote></div><p><br></p=
><p>I came to think that because VNEG is open, an attacker could inject a V=
NEG with a specific desitination CID to multiple clients and those trigger =
an indirect flooding attack by concentrating traffic via previously aquired=
 destination CIDs. Because the servers router would/should randomize unauth=
enticated CIDs an attacker cannot just inject a random CID.</p><div></div><=
/body></html>

--0000000000001466a105968d7064--


From nobody Mon Nov  4 15:13:37 2019
Return-Path: <dschinazi.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 2D21F120A74 for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 15:13:31 -0800 (PST)
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_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 T_lRYXSxoWRY for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 15:13:29 -0800 (PST)
Received: from mail-lf1-x12a.google.com (mail-lf1-x12a.google.com [IPv6:2a00:1450:4864:20::12a]) (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 9DFA6120AC2 for <quic@ietf.org>; Mon,  4 Nov 2019 15:13:28 -0800 (PST)
Received: by mail-lf1-x12a.google.com with SMTP id y6so13580167lfj.2 for <quic@ietf.org>; Mon, 04 Nov 2019 15:13:28 -0800 (PST)
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=fls9EfnmSmVdtSTNeBYwT2f7KLcnOyxd2gUxO9iqpyk=; b=jp/VkIXdwdgOO/9ye2Ee0goCFvLA9d9G59TQ5xrazHykixGyW7o5vSqsW0LwM3bHg0 E2ZTiL0beRFq3+ZYUMfS4NaknqAti91hc/jOhMSG+uE8mNYlnFSQK4SmuIndJnZv4BUH R3xo+OFgZrjOhUSxqKdW78Mwif1+aAfdgGT48ICXD5NxdsuKS5dRzbekKEgbbQNJT3Db QgNOb+uVClQi44HWUloAyzXmo2muBLf6bSDF2VoLd7UFybajoz12DsBS5wWNTnJVRD2G EPMi8p2e9lD9dsXG/Dqr39PnJWnl6CfmYj3AbzVimWgp9KmuL7CuDnQ8zlVhPvcocw8y ja3Q==
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=fls9EfnmSmVdtSTNeBYwT2f7KLcnOyxd2gUxO9iqpyk=; b=LV1knZkCmLPFwh32psSbClWEJ3F9jCH/w+fgwCRaNjyhCvYNo+lfFFLpMJspEhLdbc vEInV9tqQ91fs3oEf8Y+O1Xqry/BdIhZT8kONokcnYvDksjn+9BBUQtrZlStMG2CXgOo plG8v5BwlwVse3UrwvlJVSQMQvtsGn7JkeeSPUqbxl0YbNaYrbPPTC6BhHrFxdXSEQ+1 T10l3nrpr/6fWfAGX5LbotI+Sr8FNzQDEJlkxRXOmitBSxp3aaI4FR1DkqkZ8n10Z8JU qrjF4n1XZTEwo1RE7MJ3GZGivZy8hn9fwu8ljKg0SVYY/TJm5/pUXNECD2BjNcIi7BWf 0pPw==
X-Gm-Message-State: APjAAAWW2VakKKqywxp/YCboNufl829/+adKQluyZRGmjrcu1KE7PpLq Ue0ik2u8K89PNYf8WX9/boOdZrrVKuANMjtC2y8=
X-Google-Smtp-Source: APXvYqxD3+A5ZDiDF4mgttfcOSlFHIVj5mFAv9YhqmJTJSyHYScccdfiHF3azlcLAm6/3KMsx4Sg5SF8WUwG77XLdR4=
X-Received: by 2002:ac2:434c:: with SMTP id o12mr18720673lfl.33.1572909206881;  Mon, 04 Nov 2019 15:13:26 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+4wrhqejh9k8=G7W267EgcT5Z2sDK7ZBGKtNn5kkbXGfg@mail.gmail.com> <CAN1APdcZv-MtwRT77++r6EKdzJUc1NKEJfY4CZeOSaK50nPZYg@mail.gmail.com> <CAPDSy+5obMbiLDKYKXXg1ZthoMqyg60KD+6HR69CQqiEHb6W7g@mail.gmail.com> <CAN1APdence3-Hme+q-B_tasXJJpdxMqFpYFuR0gOgM8tMc-HNQ@mail.gmail.com> <CAPDSy+6y2gQmiCdLhVXXU3d0ER=mt7+R0s5cA=EAH3HfT+k_JA@mail.gmail.com> <CAN1APdczRvpargzKELJXOgYg1Yp+iv-5v_7RbvJZMWNHFDqCrw@mail.gmail.com>
In-Reply-To: <CAN1APdczRvpargzKELJXOgYg1Yp+iv-5v_7RbvJZMWNHFDqCrw@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Mon, 4 Nov 2019 15:13:15 -0800
Message-ID: <CAPDSy+4pzQTL_+NCLJ6HA9mLXYXNxFVMuK6o0MPRaSnD5fhr=w@mail.gmail.com>
Subject: Re: QUIC Version Negotiation Extension
To: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
Cc: QUIC <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008a4ac705968d76ca"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/i6Vc7FbAXs4A01ykppXPpn0UN14>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 23:13:35 -0000

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

On Mon, Nov 4, 2019 at 3:07 PM Mikkel Fahn=C3=B8e J=C3=B8rgensen <mikkelfj@=
gmail.com>
wrote:

> Yes all lists of versions are ordered.
>>
>> I might have missed it, but otherwise I think this should be mentioned
>> explicitly.
>>
> Isn't it mentioned in the definitions of these fields?
>
> Yes, rereading that passage, it does mention order.
>
>
>>> - It is tempting to just hash the received version list, but that
>>> requires agreeing on an algorithm, unless the algorithm is stated to be
>>> specific to that version, which is complicated.
>>>
>>
>> Which list are you referring to? For all the ones in the draft, the peer
>> needs access to all the elements so I don't think a hash would help.
>>
>> I am referring the received list. The client receives the list. The
>> server (modulo redeployment/routing) knows its own list and does not nee=
d
>> to read it, it just needs proof that the response matches what it initia=
lly
>> sent. This could be done with a hash. (If I understand correctly). But
>> maybe not because the list is filtered by clients input so that would be
>> many hashes to track.
>>
> I don't know what the received list is, there's nothing with that name in
> the draft.
>
>
> Received Negotiation Version Count + following element
>
>
Those are received by the server. And the server needs to access all the
the versions there in case it randomizes the reserved versions or has
different versions on different servers in the fleet.

> The current design of connection IDs does not guarantee consistent routin=
g
> on client-generated server connection IDs, so I don't think we can rely o=
n
> it.
>
> So this is where I=E2=80=99m not 100% on how it works, but VNEG packet do=
es, at
> least in principle, allow for a return destination CID, so the next Initi=
al
> packet can use that destination instead of a random original CID. And
> likewise, if the response is not via VNEG, the servers initial can the sa=
me
> (on known versions).
>
Version Negotiation packets MUST use the same CIDs as the client's initial.

> I think QUICv3 should also provide this property, otherwise it'll be
> likely to be unsafe. If a future version doesn't have authenticated
> transport parameters then we'll have to create a separate downgrade
> prevention mechanism. But we can cross that bridge when we get there.
>
> Sure, but perhaps mention in Security Considerations, that the design
> depends on this, if it is not considered blatantly obvious.
>
I'll admit I thought this was obvious, since it relies on transport
parameters. We'll take a PR though.

> It sounds like we could be clearer. Would you be able to send us a PR?
>
> I=E2=80=99ll consider, but I=E2=80=99m stretched a bit thin as it is.
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Mon, Nov 4, 2019 at 3:07 PM Mikkel=
 Fahn=C3=B8e J=C3=B8rgensen &lt;<a href=3D"mailto:mikkelfj@gmail.com">mikke=
lfj@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex"><div style=3D"overflow-wrap: break-word;"><div><blockquote typ=
e=3D"cite" 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_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><d=
iv><blockquote type=3D"cite" style=3D"font-family:Helvetica,Arial;font-size=
:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-=
spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-s=
pace:normal;word-spacing:0px;text-decoration:none"><div><div><div dir=3D"lt=
r"><div class=3D"gmail_quote"><div><span>Yes all lists of versions are orde=
red.</span></div></div></div></div></div></blockquote></div><p>I might have=
 missed it, but otherwise I think this should be mentioned explicitly.</p><=
/div></blockquote><div>Isn&#39;t it mentioned in the definitions of these f=
ields?</div></div></div></div></div></span></blockquote></div><p>Yes, rerea=
ding that passage, it does mention order.</p><div><div><blockquote type=3D"=
cite" style=3D"font-family:Helvetica,Arial;font-size:13px;font-style:normal=
;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-ali=
gn:start;text-indent:0px;text-transform:none;white-space:normal;word-spacin=
g:0px;text-decoration:none"><span><div><div><div dir=3D"ltr"><div class=3D"=
gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div><d=
iv><blockquote type=3D"cite" style=3D"font-family:Helvetica,Arial;font-size=
:13px;font-style:normal;font-variant-caps:normal;font-weight:normal;letter-=
spacing:normal;text-align:start;text-indent:0px;text-transform:none;white-s=
pace:normal;word-spacing:0px;text-decoration:none"><div dir=3D"ltr"><div cl=
ass=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0=
px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div>=
<div id=3D"gmail-m_4498536181264177478gmail-m_5351075036621202963gmail-m_-6=
391629696368244571bloop_customfont" style=3D"font-family:Helvetica,Arial;fo=
nt-size:13px;color:rgb(0,0,0);margin:0px"><div id=3D"gmail-m_44985361812641=
77478gmail-m_5351075036621202963gmail-m_-6391629696368244571bloop_customfon=
t" style=3D"margin:0px"><span><br>- It is tempting to just hash the receive=
d version list, but that requires agreeing on an algorithm, unless the algo=
rithm is stated to be specific to that version, which is complicated.</span=
></div></div></div></blockquote><div><span><br></span></div><div><span>Whic=
h list are you=C2=A0referring to? For all the ones in the draft, the peer n=
eeds access to all the elements so I don&#39;t think a hash would help.</sp=
an></div></div></div></blockquote></div><p>I am referring the received list=
. The client receives the list. The server (modulo redeployment/routing) kn=
ows its own list and does not need to read it, it just needs proof that the=
 response matches what it initially sent. This could be done with a hash. (=
If I understand correctly). But maybe not because the list is filtered by c=
lients input so that would be many hashes to track.</p></div></div></blockq=
uote><div>I don&#39;t know what the received list is, there&#39;s nothing w=
ith that name in the draft.</div></div></div></div></div></span></blockquot=
e></div><pre style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;=
break-before:page;font-variant-ligatures:normal"><br></pre><pre style=3D"fo=
nt-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;font-v=
ariant-ligatures:normal">Received Negotiation Version Count + following ele=
ment</pre></div></div></blockquote><div><br></div><div>Those are received b=
y the server. And the server needs to access all the the versions there in =
case it randomizes the reserved versions or has different versions on diffe=
rent servers in the fleet.</div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex"><div style=3D"overflow-wrap: break-word;"><div><div><div><blockquote=
 type=3D"cite" style=3D"font-family:Helvetica,Arial;font-size:13px;font-sty=
le:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:normal=
;text-align:start;text-indent:0px;text-transform:none;white-space:normal;wo=
rd-spacing:0px;text-decoration:none"><span><div><div><div dir=3D"ltr"><div =
class=3D"gmail_quote"><div>The current design of connection IDs does not gu=
arantee consistent routing on client-generated server connection IDs, so I =
don&#39;t think we can rely on it.</div></div></div></div></div></span></bl=
ockquote></div><p>So this is where I=E2=80=99m not 100% on how it works, bu=
t VNEG packet does, at least in principle, allow for a return destination C=
ID, so the next Initial packet can use that destination instead of a random=
 original CID. And likewise, if the response is not via VNEG, the servers i=
nitial can the same (on known versions).</p></div></div></div></blockquote>=
<div>Version Negotiation packets MUST use the same CIDs as the client&#39;s=
 initial.</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0p=
x 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div style=
=3D"overflow-wrap: break-word;"><div><div><div><div><blockquote type=3D"cit=
e" 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 dir=3D"ltr"><div class=3D"gmail_quote">=
<div>I think QUICv3 should also provide this property, otherwise it&#39;ll =
be likely to be unsafe. If a future version doesn&#39;t have authenticated =
transport parameters then we&#39;ll have to create a separate downgrade pre=
vention mechanism. But we can cross that bridge when we get there.</div></d=
iv></div></span></blockquote></div><p>Sure, but perhaps mention in Security=
 Considerations, that the design depends on this, if it is not considered b=
latantly obvious.</p></div></div></div></div></blockquote><div>I&#39;ll adm=
it I thought this was obvious, since it relies on transport parameters. We&=
#39;ll take a PR though.</div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div style=3D"overflow-wrap: break-word;"><div><div><div><div><div><bl=
ockquote type=3D"cite" style=3D"font-family:Helvetica,Arial;font-size:13px;=
font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacin=
g:normal;text-align:start;text-indent:0px;text-transform:none;white-space:n=
ormal;word-spacing:0px;text-decoration:none"><span><div dir=3D"ltr"><div cl=
ass=3D"gmail_quote"><div>It sounds like we could be clearer. Would you be a=
ble to send us a PR?</div></div></div></span></blockquote></div><p>I=E2=80=
=99ll consider, but I=E2=80=99m stretched a bit thin as it is.</p><div></di=
v></div></div></div></div></div>
</blockquote></div></div>

--0000000000008a4ac705968d76ca--


From nobody Mon Nov  4 15:16:25 2019
Return-Path: <mt@lowentropy.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 DF96A12091B for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 15:16:23 -0800 (PST)
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=lowentropy.net header.b=lszGOL3j; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Ayxo47gY
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 TjWAiugwoxiH for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 15:16:22 -0800 (PST)
Received: from wout3-smtp.messagingengine.com (wout3-smtp.messagingengine.com [64.147.123.19]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D94641207FB for <quic@ietf.org>; Mon,  4 Nov 2019 15:16:21 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 2904B694 for <quic@ietf.org>; Mon,  4 Nov 2019 18:16:21 -0500 (EST)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Mon, 04 Nov 2019 18:16:21 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=+bhOz8rm85LOwn+ADF7csGfxFSrDiE9 pnFvffYgvftE=; b=lszGOL3jhPGbJVMdegZ+TZ75TZJpy++B11Kaf6BkEPa+aMh owwYalVzfychowGRsJvwy4VGMz11mHCRqjMwMFABYmqMBDfpea16cirnJnh9KLs4 1pt498yV7/BLpqVS09Ct1brJHu2F80RSw78Ccw2sU55ziAm48DDIdilNKXOLz9pT tpJLrxx27f9JKE+f0ghUdB1jzEEXAKWZj6Fck8IRrNIdUK8ByWeWgp2R5pxP70Df O7sC6NVrsnZKCliKp5A/XY3crVAU+rVAWwk+ormudTkwC+F5GxkJ0Q9myXV7fziW i+/BIJvJpLd57vagGBSq00PatLen5Vhs8EK2+vw==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=+bhOz8 rm85LOwn+ADF7csGfxFSrDiE9pnFvffYgvftE=; b=Ayxo47gY0LH1Wmbp1p8WnW RJrT5CGHVCWjwdyqR6HTzCFwc9G8VWGb95Y/iQpFUJzb6XTextkDcgS/hXTxNl8q I2P9lmoISlJdRp4YedGtH1jbYG/xt0elPbb4swWnrAVL5ewviRmCVPt1bb5d3M4l Yunts1R0LTKpoMGYGLr/ekmtSLFFSJnDUk1/8Sv9h9kOSnocyZgmKNX8MX4axumx 5Y4Z4RwVnCWsYYifXxwbgsUsYcaZ7vdEuraQRCF47c/m5hKHYBfDt0ZZB+2Z6PaQ ZdPK2xuY3hS0kT4YcBcm5tABtbW1zDIgZxPhjcywhSQIuoeO8NqEN+LkrRA1UdPw ==
X-ME-Sender: <xms:RLHAXfi23gVwdauc63HqIoGeoqQa29r0q-fusZ2u2B_QgmKxJzm26g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedruddugedgtdekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucffohhmrghinhepihgvthhfrdhorhhgnecurfgrrh grmhepmhgrihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrdhnvghtnecuvehluhhs thgvrhfuihiivgeptd
X-ME-Proxy: <xmx:RLHAXbMH9EC1y74tuIcESuwe93gwTXd97nI9KGTNieQcmSN5xvBlBA> <xmx:RLHAXVR2SLoEZWDlesTLk_HGeW1IDkByje93aC_k7tZ8gmO9x2mMzw> <xmx:RLHAXdwjTxIM5V_zNiD2BHuWoiN0PBTY1LmN-i5mFCyPRYwlpnBOFA> <xmx:RLHAXQdWfiaZ2_EeAPZnvMLkglV6Y43Yps2cl06kJExrOShG7wumaA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 18A8BE00A3; Mon,  4 Nov 2019 18:16:20 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-509-ge3ec61c-fmstable-20191030v1
Mime-Version: 1.0
Message-Id: <6ee87e10-ef61-46be-b29d-3d6c0aef39b7@www.fastmail.com>
In-Reply-To: <CAPDSy+4wrhqejh9k8=G7W267EgcT5Z2sDK7ZBGKtNn5kkbXGfg@mail.gmail.com>
References: <CAPDSy+4wrhqejh9k8=G7W267EgcT5Z2sDK7ZBGKtNn5kkbXGfg@mail.gmail.com>
Date: Tue, 05 Nov 2019 10:16:01 +1100
From: "Martin Thomson" <mt@lowentropy.net>
To: quic@ietf.org
Subject: Re: QUIC Version Negotiation Extension
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/x-P5DpFQovPTHi_pkaLVsiC8j10>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 04 Nov 2019 23:16:24 -0000

Hi David,

I think that this is broadly the right mechanism.  It would be good to validate it more thoroughly.  

The model and framing could use a little work.

I struggled a little with the framing here because the split between incompatible and compatible versions is very important, but also unclear.  The definition of "compatible" is left for Section 7, but it seems like it should be right up front.

The framing I would choose puts the model up front.  The model that you have have two layers that are applied progressively:

1. incompatible version negotiation, where the server sends a Version Negotiation packet in response to a version it does not understand.

2. compatible version negotiation, where the server can generate interpret a version X Initial packet and continue with version Y.

Regarding the model, the definition of "compatible" needs work.

I observe that you only need a mapping from "Initial"-equivalent packets in X to the same in Y - and maybe the ability to generate a Retry in version X (more below) - in order for this to work.  That's where there is a clear functional mapping from a version X packets that initiate the connection to something that fills the same purpose in version Y.  

But the definition you have for "compatible" implies that the mapping is bijective, which I don't think is necessary.  As the draft says, version Y might define (and allow) new frame types in its Initial-equivalent packet(s), but as long as those are either optional or can be synthesized from X, that's OK.  It isn't necessary that every Y have a functional representation in X.  We might not want to define a way to negotiate an older version from a newer one (or at least not for every case).

The ability to generate a Retry stretches this definition a little.  Can you explain why you can't generate a version Y Retry?  I have an inkling, but it's not fully formed.  It complicates the model more than I'd like to have it this way around.

On Tue, Nov 5, 2019, at 07:29, David Schinazi wrote:
> Hi everyone,
> 
> From the recent discussion on multiple PRs, it appears that there might 
> be a need for downgrade-safe QUIC version negotiation, earlier than we 
> expected.
> 
> EKR and I updated our extension to hopefully suit these needs:
> https://tools.ietf.org/html/draft-schinazi-quic-version-negotiation-02
> 
> Comments welcome here or on the GitHub (link in draft).
> 
> Thanks,
> David


From nobody Mon Nov  4 16:51:06 2019
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 64DDF120114 for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 16:51:05 -0800 (PST)
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_HELO_NONE=0.001, 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 61a4SlnMl_Pa for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 16:51:03 -0800 (PST)
Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::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 353A412006F for <quic@ietf.org>; Mon,  4 Nov 2019 16:51:03 -0800 (PST)
Received: by mail-lj1-x22f.google.com with SMTP id e9so6451462ljp.13 for <quic@ietf.org>; Mon, 04 Nov 2019 16:51:03 -0800 (PST)
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=2XBb2HdZ9OxbKCVKqVi7PgThcu+UxeO+HGjl1FKLQxg=; b=iHLHllxqwCTPjBT/1IUsHVjRsE0GB3ID08TN9XytAze/HB+Kxmqrpr64LG5jfB8pjR 02lAlBIWamc4CHh/yLFf42v+fV4bW3QjTaWXCKoeGoh74WtFuXdtRsJY/bchV5gzDQd9 e5T1IHkizL1zCzIoUzyZhIboUpN2dU+Z3ZDXkbidReoTqSDy52H2t7KCBg35mQWayvhw x8MZZKMm1bhqHQVh9z1yszNsuOjS06QGsccUnKedXxqRc4/Z+rYhXkt3kM+Vtx7y8Mlv XABpHo5hh2mUu2IjaLb4muz6it8EcKsJPcVoaIGi+jkm/u0qDZ9+4MWVybaAjkP6U1ZM 8jNg==
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=2XBb2HdZ9OxbKCVKqVi7PgThcu+UxeO+HGjl1FKLQxg=; b=qBntEk3CajUkufIbRlnFlhCTWl0m2sOcTyYseIeGXclQ38/TBbITLj4AFA757uKTm/ niwgf1saerDzRqCGlnr9x6RHVTnIuBa/wsWK5LHyeM3KWhIRT/KwF5B7QjXYFrz8u6Lv MTp8L13yz09QjGfuwwX/DE3BuFfN9kiFAsvm5LCgaLW7dQy1Y1CbhYD5QCYexX8g5MxL 13EkzVidkm/yfonlKdWV+WquN+h4xQhb4tr4tP9cdiT8AAGp5Lb5wDbeFff6BlY0JLCD CsHa/CPLfG5aFlXkeZIMp0RWus1FoFQ6mqlXadnC3C5SWC2R+sAI/VrG+q2Sq56t1NGg 8uYQ==
X-Gm-Message-State: APjAAAWDHbN6YoAkfABv1MRlnpTq3TUFXsFpUbuS0vGX3ZXhNYI0Sl/t RlYjobK/MegWxUtO4LoJiyVW8FHLvnTBhQY9PgI=
X-Google-Smtp-Source: APXvYqyiijG3/iQbWRrddn7qOrW9B2/N3Xfq8SBNSBlsf/Y5lL4nc+FrPz0oKjMLeiEDdE5k6OEsk8i5SAV4hpMJC4U=
X-Received: by 2002:a2e:9954:: with SMTP id r20mr2809119ljj.197.1572915061451;  Mon, 04 Nov 2019 16:51:01 -0800 (PST)
MIME-Version: 1.0
References: <3218A80B-DAFD-43EF-8200-F99C660DF9C9@mnot.net> <5557f717-ae03-46a2-aa9f-54f019a07533@www.fastmail.com> <CA+9kkMBbuG+4309XfZoVb69Pz_s3=RPv2JWZS8zrkVFBkDMJuw@mail.gmail.com> <614379f7e12f46c6b38b7928e999cbab@ustx2ex-dag1mb5.msg.corp.akamai.com> <CAPDSy+6PHwfVReNsAFMHE3KsvM2K_ACD7sUtqikri7oG-QGfLg@mail.gmail.com> <E68585EA-E67A-4C4D-8BE3-5E5880B24056@akamai.com>
In-Reply-To: <E68585EA-E67A-4C4D-8BE3-5E5880B24056@akamai.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Mon, 4 Nov 2019 16:50:50 -0800
Message-ID: <CACpbDccE4OubiRQAAUyxthrmtdQJsaSKNmuV+HkFiJKXCJtOow@mail.gmail.com>
Subject: Re: Proposed response to the 3GPP Liaison Statement
To: "Salz, Rich" <rsalz@akamai.com>
Cc: David Schinazi <dschinazi.ietf@gmail.com>, "Lubashev, Igor" <ilubashe@akamai.com>,  Ted Hardie <ted.ietf@gmail.com>, IETF QUIC WG <quic@ietf.org>, Martin Thomson <mt@lowentropy.net>
Content-Type: multipart/alternative; boundary="0000000000007ff12b05968ed375"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/4tWkgZ2cyJSE4JF1_me-sfvobo0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 00:51:05 -0000

--0000000000007ff12b05968ed375
Content-Type: text/plain; charset="UTF-8"

The response looks sensible and accurate.

I would suggest just one change: move the point about HTTP/3 focus (maybe
the last two paras) to the top of the response, adding to it that the QUIC
wg is currently chartered to focus on HTTP. Without getting into the use
case that they are trying to fit QUIC into, it's difficult to understand
the importance of the loss bits. And we surely do not want to block QUICv1
trying to understand that use case.

On Thu, Oct 31, 2019 at 3:57 PM Salz, Rich <rsalz@akamai.com> wrote:

> Maybe we should suggest that they write an I-D for what they think their
> requirements are?
>
>
>

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

<div dir=3D"ltr">The response looks sensible and accurate.<br><br>I would s=
uggest just one change: move the point about HTTP/3 focus (maybe the last t=
wo paras) to the top of the response, adding to it that the QUIC wg is curr=
ently chartered to focus on HTTP. Without getting=C2=A0into the use case th=
at they are trying to fit QUIC into, it&#39;s difficult to understand the i=
mportance of the loss bits. And we surely do not want to block QUICv1 tryin=
g to understand that use case.</div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Thu, Oct 31, 2019 at 3:57 PM Salz, Rich &l=
t;<a href=3D"mailto:rsalz@akamai.com" target=3D"_blank">rsalz@akamai.com</a=
>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">May=
be we should suggest that they write an I-D for what they think their requi=
rements are?<br>
<br>
<br>
</blockquote></div>

--0000000000007ff12b05968ed375--


From nobody Mon Nov  4 17:23:38 2019
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 27B7F12000F for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 17:23:26 -0800 (PST)
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_HELO_NONE=0.001, 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 dO5N_IoJ7Zud for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 17:23:24 -0800 (PST)
Received: from mail-lj1-x22a.google.com (mail-lj1-x22a.google.com [IPv6:2a00:1450:4864:20::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 88B7212003E for <quic@ietf.org>; Mon,  4 Nov 2019 17:23:24 -0800 (PST)
Received: by mail-lj1-x22a.google.com with SMTP id 139so19860731ljf.1 for <quic@ietf.org>; Mon, 04 Nov 2019 17:23:24 -0800 (PST)
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=68BjOS54g8/tRi4v7kG5rTppS49JdOJxUvmqYmm5st0=; b=MnisOJbchb+L6AR5Y67VL2qgE/nXheHRUvH09wqA+bhx8KI3bIeje3XpFy/m2z4nSs wbjwST6iL94bAH+MJwDtDpPd/cCmbEktOV+ue9t5H83obABMohup6va8qTKCs8vpzUnA /nBt5/5zE60Y4VIGzrLbJBEQutqReeGCE+QJclkssNP+RKmp3VpyHSAi6Be4S2o+B3LB E8rprDTIwXPXq4VZwJiNfHAPnwv49ifiTjC5W/2tsbq72f6WUFp1KJk0dBMvpfCBqBPD 9thA1WzS9QBh9wbpT00aXwurAsH82b0a8FID20px/MenAmMK0HHUwyKTnDsmT/4T7LUw uRSA==
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=68BjOS54g8/tRi4v7kG5rTppS49JdOJxUvmqYmm5st0=; b=AwgH240qVNvFofuHDdKJ2k5bCkp7jEpBZYHWu1z/EwRW/bT/GUV6RN+kXwLA4mxFwi Kul+Lx3jRmfQ89q/sOce/RBbGFpANCWJt4a8YLk0K3HeIfFnL52AdaphdyD3srUu6zJ9 kBphdJd6Sd1Cnp6wixO9QX3AlcYt7snMB1x2Ea1kXJCfeGe1ZqPbpVLWxhJ19mVu2UwK Pzs2wsPV8UfJYneeF5GQWmJWFeKXguqIN885Fde4vvk7SIecVkmSg6z8iCTcpt71mwKt T0u0mXRwJ6yyow2exc8NsL+8cXjyxj9gYyZFzhnF9OaYnIyvagMX048n4mtIPjwDOTkS sDaA==
X-Gm-Message-State: APjAAAWiTVsY5g/gI2gFLYGvFIFgDf5mWFMUXwvDZDaJfWx5tOTodScY DPN57+WgAwKlX8ige3uznY5nQ5MiiqZCuoGVlBU=
X-Google-Smtp-Source: APXvYqx6XwI01ueuYo+EjQD3BNm/m6JKKIpFrZtCDJFY907AR3qlxOVq8LSazr+jwXhZ2h6kO0tO4vvqx+DXwa7kAnQ=
X-Received: by 2002:a2e:b0f6:: with SMTP id h22mr10297858ljl.171.1572917002698;  Mon, 04 Nov 2019 17:23:22 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+6E79OySoOLbJ8eWp0J-+3yeB5iGvj6sW19bEDn_V7-NA@mail.gmail.com> <CANatvzzaWFgrvnaV=VeZRAVvxqSBeMSZT5aMUu7-Vh9raeZJFw@mail.gmail.com> <BN6PR2201MB1700184D81061E2CBFD77BFBDA620@BN6PR2201MB1700.namprd22.prod.outlook.com> <e24ecddd-139d-4669-be96-b3de57557c4e@www.fastmail.com>
In-Reply-To: <e24ecddd-139d-4669-be96-b3de57557c4e@www.fastmail.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Mon, 4 Nov 2019 17:23:11 -0800
Message-ID: <CACpbDcci5R7Szti7LbpH7GEm9jT2fP_Jz99Mx-bBcSe8RT43cQ@mail.gmail.com>
Subject: Re: Version Ossification: Intended Scope for QUICv1
To: Martin Thomson <mt@lowentropy.net>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000035037505968f47e2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/pylt1JfvufTHSlPfZ3JRsPkE3BE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 01:23:26 -0000

--00000000000035037505968f47e2
Content-Type: text/plain; charset="UTF-8"

On Sun, Nov 3, 2019 at 1:46 PM Martin Thomson <mt@lowentropy.net> wrote:

> Why can't servers just bake the "keys" into binaries?  I mean, that's not
> something that is likely to get lost.  And it isn't really the case that
> keys need to be secret, they just have to change often enough to frustrate
> attempts to fixate on them.
>

This is a fine idea, but how does it change anything? Whenever the keys are
rotated at the server, you would still have to deal with old versions
appearing at the server, no?

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

<div dir=3D"ltr"><div dir=3D"ltr">On Sun, Nov 3, 2019 at 1:46 PM Martin Tho=
mson &lt;<a href=3D"mailto:mt@lowentropy.net">mt@lowentropy.net</a>&gt; wro=
te:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex">Why can&#39;t servers just bake the &quot;keys&quot; into bi=
naries?=C2=A0 I mean, that&#39;s not something that is likely to get lost.=
=C2=A0 And it isn&#39;t really the case that keys need to be secret, they j=
ust have to change often enough to frustrate attempts to fixate on them.<br=
></blockquote><div><br></div><div>This is a fine idea, but how does it chan=
ge anything? Whenever the keys are rotated at the server, you would still h=
ave to deal with old versions appearing at the server, no?</div></div></div=
>

--00000000000035037505968f47e2--


From nobody Mon Nov  4 17:44:24 2019
Return-Path: <pgut001@cs.auckland.ac.nz>
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 2A16612000F; Mon,  4 Nov 2019 17:44:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level: 
X-Spam-Status: No, score=-4.197 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_MED=-2.3, SPF_HELO_NONE=0.001, SPF_NONE=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=auckland.ac.nz
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 pzfhV7cqoDPA; Mon,  4 Nov 2019 17:44:13 -0800 (PST)
Received: from mx4-int.auckland.ac.nz (mx4-int.auckland.ac.nz [130.216.125.246]) (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 824ED120033; Mon,  4 Nov 2019 17:44:09 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=mail; t=1572918253; x=1604454253; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=v06AubMYBI63No/+e/4pe+PhkbntGMz4rHlASP9wNeM=; b=2xabdLa9qfvut/zf7AT+nTf5CUMW7z9HbSQcMt1v8Vmh8U+koBo6y5+Q 88WSVWiMMMnynXWG20k7DWfQWMmnA7IjW3hR1b6XYoThAYKYgVPDlY0zN m/XRjbrFC68I72d0Dzo6JgVrwgtnfNufGOFEL673h63Vo5Rugs8wfUds8 vmqXcFPvCwIfrsuu0GG4b51e5WKjKSqf4NqDayn5VYQct1qzDnSvxmIUU CAoEdgXD11i0Vj/BlhvU1GyECBUcSrZXbVv2aJSMbYUBUZkVwnbNs/pt1 SiZA3R5XWSTObpHhgGHw2SWi7a9o0SPGfyCVh+MTufz36VxuC9JVWV4VR g==;
X-IronPort-AV: E=Sophos; i="5.68,269,1569240000"; d="scan'208,217"; a="98116100"
X-Ironport-HAT: MAIL-SERVERS - $RELAYED
X-Ironport-Source: 10.6.2.2 - Outgoing - Outgoing
Received: from smtp.uoa.auckland.ac.nz (HELO uxcn13-ogg-a.UoA.auckland.ac.nz) ([10.6.2.2]) by mx4-int.auckland.ac.nz with ESMTP/TLS/AES256-SHA; 05 Nov 2019 14:44:07 +1300
Received: from uxcn13-ogg-d.UoA.auckland.ac.nz (10.6.2.5) by uxcn13-ogg-a.UoA.auckland.ac.nz (10.6.2.2) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 5 Nov 2019 14:44:06 +1300
Received: from uxcn13-ogg-d.UoA.auckland.ac.nz ([10.6.2.5]) by uxcn13-ogg-d.UoA.auckland.ac.nz ([10.6.2.5]) with mapi id 15.00.1395.000; Tue, 5 Nov 2019 14:44:06 +1300
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: "emile.stephan@orange.com" <emile.stephan@orange.com>, "Gorry Fairhurst (gorry@erg.abdn.ac.uk)" <gorry@erg.abdn.ac.uk>, tsvwg-chairs <tsvwg-chairs@ietf.org>, "Black, David" <David.Black@dell.com>
CC: "tsvwg@ietf.org" <tsvwg@ietf.org>, "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>, "etosat@ietf.org" <etosat@ietf.org>, "saag@ietf.org" <saag@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, "quic@ietf.org" <quic@ietf.org>
Subject: Re: TSVWG WGLC: draft-ietf-tsvwg-transport-encrypt-08, closes 23 October 2019
Thread-Topic: TSVWG WGLC: draft-ietf-tsvwg-transport-encrypt-08, closes 23 October 2019
Thread-Index: AdV+HJIZhebOrRcXTIK6bGArgFWweQEbzmAgAfqMkPACQR0OKQ==
Date: Tue, 5 Nov 2019 01:44:06 +0000
Message-ID: <1572918247420.10381@cs.auckland.ac.nz>
References: <CE03DB3D7B45C245BCA0D2432779493630766752@MX307CL04.corp.emc.com> ,  <4460_1571933453_5DB1CD0D_4460_57_4_5AE9CCAA1B4A2248AB61B4C7F0AD5FB931F030A0@OPEXCAUBM44.corporate.adroot.infra.ftgroup>
In-Reply-To: <4460_1571933453_5DB1CD0D_4460_57_4_5AE9CCAA1B4A2248AB61B4C7F0AD5FB931F030A0@OPEXCAUBM44.corporate.adroot.infra.ftgroup>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [130.216.158.4]
Content-Type: multipart/alternative; boundary="_000_157291824742010381csaucklandacnz_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ASZzLpGQ_h_kXaqVymnrTkE55ZA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 01:44:15 -0000

--_000_157291824742010381csaucklandacnz_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I actually think it's a pretty good summary, and delivers exactly what's
promised in the title.  OTOH I can also see that it's going to get bikeshed=
ded
to death, and will probably never be editable into a form where people won'=
t
complain about it no matter how many changes are made.  Alternatively, it'l=
l
end up watered down to a point where no-one can complain any more but it wo=
n't
say anything terribly useful by then.

Perhaps it could be published as is with a comment that it represents the
opinions of the authors?  Although given that it's Informational and not
Standards-track or a BCP, that should be a given anyway.

Peter.




--_000_157291824742010381csaucklandacnz_
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">
<style type=3D"text/css" style=3D"display:none"><!-- p { margin-top: 0px; m=
argin-bottom: 0px; } @font-face { font-family: Wingdings; } @font-face { fo=
nt-family: Calibri; } @font-face { font-family: Tahoma; } @font-face { font=
-family: Consolas; } p.MsoNormal, li.MsoNormal, div.MsoNormal { margin: 0cm=
 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; } a:link,=
 span.MsoHyperlink { color: rgb(5, 99, 193); text-decoration: underline; } =
a:visited, span.MsoHyperlinkFollowed { color: rgb(149, 79, 114); text-decor=
ation: underline; } p.MsoPlainText, li.MsoPlainText, div.MsoPlainText { mar=
gin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; }=
 p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph { margin: 0c=
m 0cm 0.0001pt 36pt; font-size: 11pt; font-family: Calibri, sans-serif; } s=
pan.TextebrutCar { font-family: Consolas; } p.msonormal0, li.msonormal0, di=
v.msonormal0 { margin-right: 0cm; margin-left: 0cm; font-size: 11pt; font-f=
amily: Calibri, sans-serif; } span.PlainTextChar { font-family: Calibri, sa=
ns-serif; } p.PlainText, li.PlainText, div.PlainText { margin: 0cm 0cm 0.00=
01pt; font-size: 11pt; font-family: Calibri, sans-serif; } span.EmailStyle2=
3 { font-family: Calibri, sans-serif; color: windowtext; font-weight: norma=
l; font-style: normal; } span.EmailStyle24 { font-family: Calibri, sans-ser=
if; color: rgb(153, 51, 102); font-weight: normal; font-style: normal; } sp=
an.EmailStyle25 { font-family: Arial, sans-serif; color: black; font-weight=
: normal; font-style: normal; } span.EmailStyle26 { font-family: Arial, san=
s-serif; color: black; font-weight: normal; font-style: normal; } @page Wor=
dSection1 { margin: 72pt; } div.WordSection1 { } ol { margin-bottom: 0cm; }=
 ul { margin-bottom: 0cm; }--></style>
</head>
<body dir=3D"ltr" style=3D"font-size:12pt;color:#000000;background-color:#F=
FFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<p></p>
<div>I actually think it's a pretty good summary, and delivers exactly what=
's</div>
<div>promised in the title.&nbsp; OTOH I can also see that it's going to ge=
t bikeshedded</div>
<div>to death, and will probably never be editable into a form where people=
 won't</div>
<div>complain about it no matter how many changes are made.&nbsp; Alternati=
vely, it'll</div>
<div>end up watered down to a point where no-one can complain any more but =
it won't</div>
<div>say anything terribly useful by then.</div>
<div><br>
</div>
<div>Perhaps it could be published as is with a comment that it represents =
the</div>
<div>opinions of the authors?&nbsp; Although given that it's Informational =
and not</div>
<div>Standards-track or a BCP, that should be a given anyway.</div>
<div><br>
</div>
<div>Peter.</div>
<div><br>
<br>
</div>
<p><br>
</p>
</body>
</html>

--_000_157291824742010381csaucklandacnz_--


From nobody Mon Nov  4 17:58:31 2019
Return-Path: <mt@lowentropy.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 EAB3912000F for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 17:58:29 -0800 (PST)
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=lowentropy.net header.b=gfgUjtNT; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=yFgNJbe0
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 Mf7q1n9O2XVj for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 17:58:28 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 989DD12003E for <quic@ietf.org>; Mon,  4 Nov 2019 17:58:28 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D33C622017; Mon,  4 Nov 2019 20:58:27 -0500 (EST)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Mon, 04 Nov 2019 20:58:27 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type; s=fm3; bh=n7S6rtgjmQSpL1vVFzzLqtHNoP01 Y/OyjE/sIYU4vf0=; b=gfgUjtNTkXXXVCkQ7SSd09/MAyskDzZI/gu15aX4w43P u/JxiZcR23ZHPhnNXCMmFCQ81JKgWbz3VCnliyt3r2FqTIRa9tXjii+CwShjV3Nw ja1OEB6NmKuROEJW+FXar4MJ18hTQB81zxRrB+lKVxq6gtN1wmVL5zKA97aaS4Ly ZEwsCm/uXzF22fg0c8fMO8lGiqH3CSPEmUU+paekXOCAEdgovte3/a44R/+AmO5P FjyNUJlKSURjaIWPYZ/sPIF/iS7Lljohul90thdt5MkHN/bbtT05/nfUhpJj+cbO DwScwnMBQBnQ6E9M6ti3N/jy8XOH1nHh26IO+o3hIA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=n7S6rt gjmQSpL1vVFzzLqtHNoP01Y/OyjE/sIYU4vf0=; b=yFgNJbe0OkjVLUYqDoO7Ck RU3LMr2LGfGSyLlAH45lGDSg0QHD3zgdSZr44nKl3j1Ct9OjZ2w6+Hnah5TgH8c/ rM/gLaQ+ZQgqmkvhsKQqiangx3I0w/Kzq4r+Pna+ARVGBSmRXa/mIe2HXDMPhSVv iuCYvXc5l4KPIS8vLPPO2TtQx4pRp7wIC8YixLtU6w7q93X1+tNwvT7LszAZOL3i IyyqLFDOvGNQBijDaagncwkLusq4I37Z23pssvwJ9t+EhoRmrQbX3zC2wrkNj86/ cMbOKyNah1Y5VEBSff81tuoU8ew5KXITEz0n/qUTdHz/vJs2hFQqTWLxlP6mWYGA ==
X-ME-Sender: <xms:Q9fAXZ7cfn4oU0xZ43z0xDG37zoVgyPJ79A9wSEXMdtVNrhnTGL2dw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedruddugedggeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreertdenucfhrhhomhepfdforghr thhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnthhrohhphidrnhgvtheqnecurf grrhgrmhepmhgrihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrdhnvghtnecuvehl uhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:Q9fAXSAJXqJsfp2WHyBazG35a3K-GaKBWmwyrDywWdtputBJj6ASvA> <xmx:Q9fAXV29RvIQpYDYaeANorRUkIvajSL7yYXXNRvhVmfdetufOKrwpg> <xmx:Q9fAXR_uQe7Z3WqulsAKDkbmT42n2BmjRh0nrKzGaX9k2n_hoG6aXw> <xmx:Q9fAXb9tGnNs-ct1va_5qqv7M0d7yecE_sGVoXMYuQ8hx67CegJVmA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 723C0E00A3; Mon,  4 Nov 2019 20:58:27 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-509-ge3ec61c-fmstable-20191030v1
Mime-Version: 1.0
Message-Id: <d5c3b4d3-2202-41d7-9ebe-3541ceec1b78@www.fastmail.com>
In-Reply-To: <CACpbDcci5R7Szti7LbpH7GEm9jT2fP_Jz99Mx-bBcSe8RT43cQ@mail.gmail.com>
References: <CAPDSy+6E79OySoOLbJ8eWp0J-+3yeB5iGvj6sW19bEDn_V7-NA@mail.gmail.com> <CANatvzzaWFgrvnaV=VeZRAVvxqSBeMSZT5aMUu7-Vh9raeZJFw@mail.gmail.com> <BN6PR2201MB1700184D81061E2CBFD77BFBDA620@BN6PR2201MB1700.namprd22.prod.outlook.com> <e24ecddd-139d-4669-be96-b3de57557c4e@www.fastmail.com> <CACpbDcci5R7Szti7LbpH7GEm9jT2fP_Jz99Mx-bBcSe8RT43cQ@mail.gmail.com>
Date: Tue, 05 Nov 2019 12:58:08 +1100
From: "Martin Thomson" <mt@lowentropy.net>
To: "Jana Iyengar" <jri.ietf@gmail.com>
Cc: "QUIC WG" <quic@ietf.org>
Subject: Re: Version Ossification: Intended Scope for QUICv1
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/uNVtwE6ymBx-h17w55RUAzXERbc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 01:58:30 -0000

On Tue, Nov 5, 2019, at 12:23, Jana Iyengar wrote:
> On Sun, Nov 3, 2019 at 1:46 PM Martin Thomson <mt@lowentropy.net> wrote:
> > Why can't servers just bake the "keys" into binaries? I mean, that's not something that is likely to get lost. And it isn't really the case that keys need to be secret, they just have to change often enough to frustrate attempts to fixate on them.
> 
> This is a fine idea, but how does it change anything? Whenever the keys 
> are rotated at the server, you would still have to deal with old 
> versions appearing at the server, no?

I'm assuming that you can a) limit the time over which a token could appear, b) use a key identifier so that keys can be changed, and c) keep old keys in the code until the associated tokens are all expired.


From nobody Mon Nov  4 18:22:20 2019
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 94C63120033 for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 18:22:19 -0800 (PST)
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_HELO_NONE=0.001, 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 UWLzWWAgrf8V for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 18:22:17 -0800 (PST)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::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 7716412000F for <quic@ietf.org>; Mon,  4 Nov 2019 18:22:17 -0800 (PST)
Received: by mail-lj1-x22d.google.com with SMTP id r7so11242963ljg.2 for <quic@ietf.org>; Mon, 04 Nov 2019 18:22:17 -0800 (PST)
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=25Iefp8JlE4JxPk7FXWGE7TBegF9tDIBYOj9ZCct98M=; b=EwirZIGySl5wWnZ6lBz8g32NiMSU1ur2no9g34fHO+EoYuFt+wPHjlT7R7d2hs2vpv Cifjp5d/bKAggrVYTfBppIdeQmZgz761g2EHTinHPO1+SErqZoW6Knuw9VuIUWSO0DU0 j+pFMZTl5r4vN5NTwhTf9wsQVRkoqWVhVoN6XBmx1v+irGQuI027mGPzQtoUEtG/LqiV L6e7xcjV283SYBr5B2KL3zm+ndFDxrMQWtfuR8CY4S1tyNa4uiV8WdtVUOu+sMoVPqOo tBsw2UwTf5d88xnht6u57i1jNRxX4HkyiPVfnlRYWDFQGTNiBAKmFlt0qZuP7GrcYm8/ vMOw==
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=25Iefp8JlE4JxPk7FXWGE7TBegF9tDIBYOj9ZCct98M=; b=eSrJqv+np/7G7wMCT8UeYkiyAhtitZdR2a4wlm2K3pjhUXCURF07C81++xatt5udNH Ahbm94iqFTTfzHyWqQ9s1FzeRO79F7A7D8hIjEe4K5ME4eHFJQ0LnXACje4sYJUlINcN M6hREmd71JcZ6Lsh0RtNLkpnL+G+A4pRgCtKUkmDLf06qCHxlBrOerTrWiUcOA8JaMKO SY4xny82vjCuRyNH37WtV0eeel7oJKWPKB/VgvMMI7o3s+AnZNbgIb11hFPlLcc4o4iG Zo5smnopub/SD/N8igDkf4DWPC4+nBiVpEfOTpOs9QeaOV5/8PszNR3bJkgQ/K/K4G6J w0uA==
X-Gm-Message-State: APjAAAUbvxAlOVfUxyyC6wP/vrBFdaYUCrJR4ncfgQmZDwM90RtJSXIK pHE/jLPf8n+G810F/0kADwhpqopaniNVZ/SvJUNy+Q==
X-Google-Smtp-Source: APXvYqw82Nre5IEchZNhe7NNP28E+dQcdeAJNwHdR7jJTmQNRxtLlpmfvBqgooWobbTTpW//f6qyPCSSwiQuswAES4Y=
X-Received: by 2002:a2e:b0f6:: with SMTP id h22mr10421517ljl.171.1572920535615;  Mon, 04 Nov 2019 18:22:15 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+6E79OySoOLbJ8eWp0J-+3yeB5iGvj6sW19bEDn_V7-NA@mail.gmail.com> <CANatvzzaWFgrvnaV=VeZRAVvxqSBeMSZT5aMUu7-Vh9raeZJFw@mail.gmail.com> <BN6PR2201MB1700184D81061E2CBFD77BFBDA620@BN6PR2201MB1700.namprd22.prod.outlook.com> <e24ecddd-139d-4669-be96-b3de57557c4e@www.fastmail.com> <CACpbDcci5R7Szti7LbpH7GEm9jT2fP_Jz99Mx-bBcSe8RT43cQ@mail.gmail.com> <d5c3b4d3-2202-41d7-9ebe-3541ceec1b78@www.fastmail.com>
In-Reply-To: <d5c3b4d3-2202-41d7-9ebe-3541ceec1b78@www.fastmail.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Mon, 4 Nov 2019 18:22:04 -0800
Message-ID: <CACpbDcetR7e01oDZ7_hihB2mpbKbOuydp6mHd474bduaMA5rbA@mail.gmail.com>
Subject: Re: Version Ossification: Intended Scope for QUICv1
To: Martin Thomson <mt@lowentropy.net>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c90abb05969019d0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/gAqsNsXyKZj_T9i18m7KQvEMW9M>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 02:22:20 -0000

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

On Mon, Nov 4, 2019 at 5:58 PM Martin Thomson <mt@lowentropy.net> wrote:

> On Tue, Nov 5, 2019, at 12:23, Jana Iyengar wrote:
> > On Sun, Nov 3, 2019 at 1:46 PM Martin Thomson <mt@lowentropy.net> wrote:
> > > Why can't servers just bake the "keys" into binaries? I mean, that's
> not something that is likely to get lost. And it isn't really the case that
> keys need to be secret, they just have to change often enough to frustrate
> attempts to fixate on them.
> >
> > This is a fine idea, but how does it change anything? Whenever the keys
> > are rotated at the server, you would still have to deal with old
> > versions appearing at the server, no?
>
> I'm assuming that you can a) limit the time over which a token could
> appear, b) use a key identifier so that keys can be changed, and c) keep
> old keys in the code until the associated tokens are all expired.
>

Right, that makes sense. I think your point about not requiring this to be
rotated frequently is a good one, and we might even want to suggest your
idea of baking the key into the binary.

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

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Nov 4, 2019 at 5:58 PM Martin Tho=
mson &lt;<a href=3D"mailto:mt@lowentropy.net">mt@lowentropy.net</a>&gt; wro=
te:<br></div><div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" s=
tyle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);pad=
ding-left:1ex">On Tue, Nov 5, 2019, at 12:23, Jana Iyengar wrote:<br>
&gt; On Sun, Nov 3, 2019 at 1:46 PM Martin Thomson &lt;<a href=3D"mailto:mt=
@lowentropy.net" target=3D"_blank">mt@lowentropy.net</a>&gt; wrote:<br>
&gt; &gt; Why can&#39;t servers just bake the &quot;keys&quot; into binarie=
s? I mean, that&#39;s not something that is likely to get lost. And it isn&=
#39;t really the case that keys need to be secret, they just have to change=
 often enough to frustrate attempts to fixate on them.<br>
&gt; <br>
&gt; This is a fine idea, but how does it change anything? Whenever the key=
s <br>
&gt; are rotated at the server, you would still have to deal with old <br>
&gt; versions appearing at the server, no?<br>
<br>
I&#39;m assuming that you can a) limit the time over which a token could ap=
pear, b) use a key identifier so that keys can be changed, and c) keep old =
keys in the code until the associated tokens are all expired.<br></blockquo=
te><div><br></div><div>Right, that makes sense. I think your point about no=
t requiring this to be rotated frequently is a good one, and we might even =
want to suggest your idea of baking the key into the binary.=C2=A0</div></d=
iv></div>

--000000000000c90abb05969019d0--


From nobody Mon Nov  4 18:35:45 2019
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 5E85E12007A for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 18:35:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 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_HELO_NONE=0.001, SPF_NONE=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=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 QkXdhzEb9UkI for <quic@ietfa.amsl.com>; Mon,  4 Nov 2019 18:35:36 -0800 (PST)
Received: from mail-lf1-x134.google.com (mail-lf1-x134.google.com [IPv6:2a00:1450:4864:20::134]) (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 61F6612006F for <quic@ietf.org>; Mon,  4 Nov 2019 18:35:36 -0800 (PST)
Received: by mail-lf1-x134.google.com with SMTP id j14so13829165lfb.8 for <quic@ietf.org>; Mon, 04 Nov 2019 18:35:36 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=6CtuZCErZWIlvQlP8U6/r+0Lss1CXFNRNhLUvq7R2Ic=; b=v0xuM26HjUUO6khZ657q+fbTvZTtG6aDQPn1Mh5XoW49sv1BjcmLL99ZpsLq72uX0t S2CctrWm1OHMs7VbZmymFdy+y0RfE3RnpGBO9QAqfrl8wzG2L0p+C18gBneffCNMoqsO E8hwevX7wk/TMw2hJ2saA5RyFfjDgkhabeLfebfpGtBNCNGLVCT1JuM8GYiR5YYORmWN c2w8fcQG6bGdU9f4ql74WnUqLlpIVLPlsxYVqzJ6AWOGzEXZccw9gwm+vJm5upZGXgrF n3diCtJJKwBr9QUh2HfcB945cWhThm68nsxnJyg8NlJdxbMjSma0qjfa+K8mbwMT1d44 79/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:references:in-reply-to:from:date :message-id:subject:to:cc; bh=6CtuZCErZWIlvQlP8U6/r+0Lss1CXFNRNhLUvq7R2Ic=; b=LyVZGhwTgM8NyaM4EF8uoTUPfptE5RAZ3QjZUQXCSSIKO+xee7vvhZ8+eCdV2mAznC fw2r4rqOCB/98En3wDoehM5AJoOCzyFPVIO6384VtiYALIP+ORIQYJMLetg9uhXEbIke EWg8BvG/G1fbOA/8xrKThPGxypiyTCuEsJO1yzLHhOqia8nImzbCz9+oGMDpvqb3QXkW r/d8FJGz7mpGlLLMfQw9xKWleqD/I911UfQ+60r+t2TCJecAgOYgQvTyY5UhcP/RFDwm qk3WFn0IZipeeOWd/gq0IIl135HBnUe5oo0fb/TZKvJtxSA2sVGhy1Y7nS9a6B1tOtWX 2/vQ==
X-Gm-Message-State: APjAAAWygy3oEf+K1fnxtcRS9HAQwRNPkdJa0Da9ZuJeJa3N8IrVQot6 ZY8TIJ2IkxpT02e0WNqho3QBtH6/CFsAoTpvGJpB/A==
X-Google-Smtp-Source: APXvYqwi1FyyRGlyfwiqVtuZx9EGPncLwaugCYGhoJBx6n22ljg3ojU4hPd4yK03iA1VmR/mimb+Ypr9HcnHVPS71Xs=
X-Received: by 2002:a19:c6d6:: with SMTP id w205mr17284236lff.17.1572921334550;  Mon, 04 Nov 2019 18:35:34 -0800 (PST)
MIME-Version: 1.0
References: <CE03DB3D7B45C245BCA0D2432779493630766752@MX307CL04.corp.emc.com> <4460_1571933453_5DB1CD0D_4460_57_4_5AE9CCAA1B4A2248AB61B4C7F0AD5FB931F030A0@OPEXCAUBM44.corporate.adroot.infra.ftgroup> <1572918247420.10381@cs.auckland.ac.nz>
In-Reply-To: <1572918247420.10381@cs.auckland.ac.nz>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 4 Nov 2019 18:34:58 -0800
Message-ID: <CABcZeBPy_39o37snzy8F6iyLQMg1aGkYbhy0A1N-PxFUmAmB0g@mail.gmail.com>
Subject: Re: TSVWG WGLC: draft-ietf-tsvwg-transport-encrypt-08, closes 23 October 2019
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
Cc: "emile.stephan@orange.com" <emile.stephan@orange.com>,  "Gorry Fairhurst (gorry@erg.abdn.ac.uk)" <gorry@erg.abdn.ac.uk>, tsvwg-chairs <tsvwg-chairs@ietf.org>,  "Black, David" <David.Black@dell.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>,  "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>, "etosat@ietf.org" <etosat@ietf.org>, "saag@ietf.org" <saag@ietf.org>,  "opsawg@ietf.org" <opsawg@ietf.org>, "quic@ietf.org" <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000067e6fa0596904939"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/U5imeQXzLCGx5d9GxslOFNR1Y34>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 02:35:39 -0000

--00000000000067e6fa0596904939
Content-Type: text/plain; charset="UTF-8"

On Mon, Nov 4, 2019 at 5:44 PM Peter Gutmann <pgut001@cs.auckland.ac.nz>
wrote:

> I actually think it's a pretty good summary, and delivers exactly what's
> promised in the title.  OTOH I can also see that it's going to get
> bikeshedded
> to death, and will probably never be editable into a form where people
> won't
> complain about it no matter how many changes are made.  Alternatively,
> it'll
> end up watered down to a point where no-one can complain any more but it
> won't
> say anything terribly useful by then.
>
> Perhaps it could be published as is with a comment that it represents the
> opinions of the authors?  Although given that it's Informational and not
> Standards-track or a BCP, that should be a given anyway.
>

Actually, no. Most IETF documents, even informational ones, bear a
statement that they have IETF Consensus.

See: https://tools.ietf.org/html/rfc5741#section-3.2.1

-Ekr


> Peter.
>
>
>
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Mon, Nov 4, 2019 at 5:44 PM Peter =
Gutmann &lt;<a href=3D"mailto:pgut001@cs.auckland.ac.nz">pgut001@cs.aucklan=
d.ac.nz</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"=
margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-lef=
t:1ex">




<div dir=3D"ltr" style=3D"font-size:12pt;color:rgb(0,0,0);background-color:=
rgb(255,255,255);font-family:Calibri,Arial,Helvetica,sans-serif">
<p></p>
<div>I actually think it&#39;s a pretty good summary, and delivers exactly =
what&#39;s</div>
<div>promised in the title.=C2=A0 OTOH I can also see that it&#39;s going t=
o get bikeshedded</div>
<div>to death, and will probably never be editable into a form where people=
 won&#39;t</div>
<div>complain about it no matter how many changes are made.=C2=A0 Alternati=
vely, it&#39;ll</div>
<div>end up watered down to a point where no-one can complain any more but =
it won&#39;t</div>
<div>say anything terribly useful by then.</div>
<div><br>
</div>
<div>Perhaps it could be published as is with a comment that it represents =
the</div>
<div>opinions of the authors?=C2=A0 Although given that it&#39;s Informatio=
nal and not</div>
<div>Standards-track or a BCP, that should be a given anyway.</div></div></=
blockquote><div><br></div><div>Actually, no. Most IETF documents, even info=
rmational ones, bear a statement that they have IETF Consensus.</div><div><=
br></div><div>See: <a href=3D"https://tools.ietf.org/html/rfc5741#section-3=
.2.1">https://tools.ietf.org/html/rfc5741#section-3.2.1</a></div><div><br><=
/div><div>-Ekr</div><div><br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex"><div dir=3D"ltr" style=3D"font-size:12pt;color:rgb(0,0,0);backgr=
ound-color:rgb(255,255,255);font-family:Calibri,Arial,Helvetica,sans-serif"=
>
<div><br>
</div>
<div>Peter.</div>
<div><br>
<br>
</div>
<p><br>
</p>
</div>

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

--00000000000067e6fa0596904939--


From nobody Mon Nov  4 18:39:46 2019
Return-Path: <jmh@joelhalpern.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 E8A4C12006B; Mon,  4 Nov 2019 18:39:34 -0800 (PST)
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 (1024-bit key) header.d=joelhalpern.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 y4tiSY55vOb4; Mon,  4 Nov 2019 18:39:33 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 3788612004D; Mon,  4 Nov 2019 18:39:33 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 476Ylm6fF1z1x0PZ; Mon,  4 Nov 2019 18:39:32 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1572921572; bh=YB4ILCq09o4Qo0v6Y3Y8wTn9YfNPZjU1TjWHDryiBJk=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=YbzHKabWBtBqyTwSHKdmO/hqvpbRZtYIRwMwDKT8kZTQCAQX6helyR4kBgE+ft9B5 PpTfcvuX7NcRnz/vIyGBdujxfSq93lobq/nODprgCF4E2PWgzy6crMHPZBSc6d76aA TVd2vyNrrMsBwUQB/fNDM0lpDkf0P05GG1Mn28JM=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 476Yll59n1z1x0PY; Mon,  4 Nov 2019 18:39:31 -0800 (PST)
Subject: Re: [OPSAWG] TSVWG WGLC: draft-ietf-tsvwg-transport-encrypt-08, closes 23 October 2019
To: Peter Gutmann <pgut001@cs.auckland.ac.nz>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>, tsvwg-chairs <tsvwg-chairs@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, "quic@ietf.org" <quic@ietf.org>, "saag@ietf.org" <saag@ietf.org>
References: <CE03DB3D7B45C245BCA0D2432779493630766752@MX307CL04.corp.emc.com> <4460_1571933453_5DB1CD0D_4460_57_4_5AE9CCAA1B4A2248AB61B4C7F0AD5FB931F030A0@OPEXCAUBM44.corporate.adroot.infra.ftgroup> <1572918247420.10381@cs.auckland.ac.nz> <CABcZeBPy_39o37snzy8F6iyLQMg1aGkYbhy0A1N-PxFUmAmB0g@mail.gmail.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <f2b1f803-b559-a166-8009-baff551bec5c@joelhalpern.com>
Date: Mon, 4 Nov 2019 21:39:28 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <CABcZeBPy_39o37snzy8F6iyLQMg1aGkYbhy0A1N-PxFUmAmB0g@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/XyHRZ8G0s6QdlUZmIDnvuYgjVJU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 02:39:35 -0000

If the authors want to publish it as an RFC so as to comment on other 
RFCs, they could approach the Independent Stream Editor.  That sort of 
publication is one of the explicit purposes of the Independent Stream.

Yours,
Joel

On 11/4/2019 9:34 PM, Eric Rescorla wrote:
> 
> 
> On Mon, Nov 4, 2019 at 5:44 PM Peter Gutmann <pgut001@cs.auckland.ac.nz 
> <mailto:pgut001@cs.auckland.ac.nz>> wrote:
> 
>     I actually think it's a pretty good summary, and delivers exactly what's
>     promised in the title.Â  OTOH I can also see that it's going to get
>     bikeshedded
>     to death, and will probably never be editable into a form where
>     people won't
>     complain about it no matter how many changes are made. 
>     Alternatively, it'll
>     end up watered down to a point where no-one can complain any more
>     but it won't
>     say anything terribly useful by then.
> 
>     Perhaps it could be published as is with a comment that it
>     represents the
>     opinions of the authors?Â  Although given that it's Informational and not
>     Standards-track or a BCP, that should be a given anyway.
> 
> 
> Actually, no. Most IETF documents, even informational ones, bear a 
> statement that they have IETF Consensus.
> 
> See: https://tools.ietf.org/html/rfc5741#section-3.2.1 
> <https://tools.ietf.org/html/rfc5741#section-3..2.1>
> 
> -Ekr
> 
> 
>     Peter.
> 
> 
> 
> 
> _______________________________________________
> OPSAWG mailing list
> OPSAWG@ietf.org
> https://www.ietf.org/mailman/listinfo/opsawg
> 


From nobody Mon Nov  4 18:41:15 2019
Return-Path: <pgut001@cs.auckland.ac.nz>
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 38162120147; Mon,  4 Nov 2019 18:40:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.197
X-Spam-Level: 
X-Spam-Status: No, score=-4.197 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_HELO_NONE=0.001, SPF_NONE=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=auckland.ac.nz
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 j3USHftv-oT0; Mon,  4 Nov 2019 18:40:52 -0800 (PST)
Received: from mx4-int.auckland.ac.nz (mx4-int.auckland.ac.nz [130.216.125.246]) (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 3D1A512006B; Mon,  4 Nov 2019 18:40:51 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=auckland.ac.nz; i=@auckland.ac.nz; q=dns/txt; s=mail; t=1572921653; x=1604457653; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=uiXm5m3IwH0Ms7tsP06Xt+EDWbDLmLQ6ZLvD6l1dqqM=; b=MGFOQRqdl9jIuM4XL6LkwwgqdqCanw7imDbPH0CMKfAZ1J0kgAVofwkG vQzBb/UkAPE42i6ucb7w5Dn4qYx6mqKiIf9qDIC2T3HniLIDz9NpnGTY7 /aYY7rVDR4L7TNeGMmLrjvl889CepVEkX036zRVolAkX7fQNGQZtu23xM O38ykVaoSq+T6QMQL5KlMURpaXwWKtnLmFeizAaUp/zCs7+6vL1HXCOoe zu4e5o7xP/ODPC3YbeTLZnjCwX64xouTlxW72NMNd4y0Y/EEoD710+ybv ba0IYFm8ZYT8B8glW3B2gW8e/dAGeXhWFDrMgW3u7J99mohFK0gyyFE1w w==;
X-IronPort-AV: E=Sophos;i="5.68,269,1569240000"; d="scan'208";a="98130017"
X-Ironport-HAT: MAIL-SERVERS - $RELAYED
X-Ironport-Source: 10.6.3.3 - Outgoing - Outgoing
Received: from smtp.uoa.auckland.ac.nz (HELO uxcn13-tdc-b.UoA.auckland.ac.nz) ([10.6.3.3]) by mx4-int.auckland.ac.nz with ESMTP/TLS/AES256-SHA; 05 Nov 2019 15:40:49 +1300
Received: from uxcn13-ogg-d.UoA.auckland.ac.nz (10.6.2.5) by uxcn13-tdc-b.UoA.auckland.ac.nz (10.6.3.3) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 5 Nov 2019 15:40:48 +1300
Received: from uxcn13-ogg-d.UoA.auckland.ac.nz ([10.6.2.5]) by uxcn13-ogg-d.UoA.auckland.ac.nz ([10.6.2.5]) with mapi id 15.00.1395.000; Tue, 5 Nov 2019 15:40:48 +1300
From: Peter Gutmann <pgut001@cs.auckland.ac.nz>
To: Eric Rescorla <ekr@rtfm.com>
CC: "emile.stephan@orange.com" <emile.stephan@orange.com>, "Gorry Fairhurst (gorry@erg.abdn.ac.uk)" <gorry@erg.abdn.ac.uk>, tsvwg-chairs <tsvwg-chairs@ietf.org>, "Black, David" <David.Black@dell.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>, "etosat@ietf.org" <etosat@ietf.org>, "saag@ietf.org" <saag@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, "quic@ietf.org" <quic@ietf.org>
Subject: Re: TSVWG WGLC: draft-ietf-tsvwg-transport-encrypt-08, closes 23 October 2019
Thread-Topic: TSVWG WGLC: draft-ietf-tsvwg-transport-encrypt-08, closes 23 October 2019
Thread-Index: AdV+HJIZhebOrRcXTIK6bGArgFWweQEbzmAgAfqMkPACQR0OKf//NGgAgADai0A=
Date: Tue, 5 Nov 2019 02:40:48 +0000
Message-ID: <1572921649364.66797@cs.auckland.ac.nz>
References: <CE03DB3D7B45C245BCA0D2432779493630766752@MX307CL04.corp.emc.com> <4460_1571933453_5DB1CD0D_4460_57_4_5AE9CCAA1B4A2248AB61B4C7F0AD5FB931F030A0@OPEXCAUBM44.corporate.adroot.infra.ftgroup> <1572918247420.10381@cs.auckland.ac.nz>, <CABcZeBPy_39o37snzy8F6iyLQMg1aGkYbhy0A1N-PxFUmAmB0g@mail.gmail.com>
In-Reply-To: <CABcZeBPy_39o37snzy8F6iyLQMg1aGkYbhy0A1N-PxFUmAmB0g@mail.gmail.com>
Accept-Language: en-NZ, en-GB, en-US
Content-Language: en-NZ
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [130.216.158.4]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ie1Vm5Jy4vr4oSOs35eBOGoDH2M>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 02:40:59 -0000

Eric Rescorla <ekr@rtfm.com> writes:=0A=
=0A=
>Actually, no. Most IETF documents, even informational ones, bear a stateme=
nt=0A=
>that they have IETF Consensus.=0A=
=0A=
Ah, OK.  In that case publish it with a statement that commentators couldn'=
t=0A=
agree on what it should say, which I think is better than watering it down =
to=0A=
a level where commentators can't disagree with what it says.  It's an=0A=
interesting document which makes good points, and worth putting out there=
=0A=
while it still has good points to make.=0A=
=0A=
Peter.=0A=
=0A=
=0A=
        =


From nobody Mon Nov  4 18:48:18 2019
Return-Path: <touch@strayalpha.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 D20A812004D; Mon,  4 Nov 2019 18:48:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.219
X-Spam-Level: 
X-Spam-Status: No, score=-1.219 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_HELO_NONE=0.001, SPF_NEUTRAL=0.779, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=strayalpha.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 juEw0VAwdU6y; Mon,  4 Nov 2019 18:48:15 -0800 (PST)
Received: from server217-3.web-hosting.com (server217-3.web-hosting.com [198.54.115.226]) (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 84D0112006B; Mon,  4 Nov 2019 18:48:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=strayalpha.com; s=default; h=To:References:Message-Id: Content-Transfer-Encoding:Cc:Date:In-Reply-To:From:Subject:Mime-Version: Content-Type:Sender:Reply-To:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=MI9VPaT4MWXUkvZ3EDHHG7c+aFzawpuCBeYNDUjeBPM=; b=S99XQZIcmaScOKcfk6ijkkKHA mEQumxwXHoDAp6H0f4AYW2QRSB5VfmOr8SciQDbMAFR1angMb16MPgJ84ncLJz9pgrwfzNVwJxv6U n6JASNY8QoXSJsQpz4pFnBST1pq1qYXcprmUUqjiNEuCBFg0Bx6UgIoB+abfuzCHYgvfcKZkwyGdx ZC8RjQgezhg2YcHFBuwuPTSIM3vXWxPogrOfCbGwDPnSh9yYRQl1iqGpXh5WsqnJ/gkD9Q9y0qyv8 e4zBd4oYdZBn1Xz8LpPSUp45vc2TYF8C4JMsIkHcr8sQZSR2x6Wzs3v8+xx0BW4o+LtfCMGkcsW49 ghxULFubg==;
Received: from cpe-172-250-225-198.socal.res.rr.com ([172.250.225.198]:59561 helo=[192.168.1.10]) by server217.web-hosting.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92) (envelope-from <touch@strayalpha.com>) id 1iRot8-0021UN-2s; Mon, 04 Nov 2019 21:48:14 -0500
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\))
Subject: Re: [tsvwg] [OPSAWG] TSVWG WGLC: draft-ietf-tsvwg-transport-encrypt-08, closes 23 October 2019
From: Joe Touch <touch@strayalpha.com>
In-Reply-To: <f2b1f803-b559-a166-8009-baff551bec5c@joelhalpern.com>
Date: Mon, 4 Nov 2019 18:48:09 -0800
Cc: Peter Gutmann <pgut001@cs.auckland.ac.nz>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>, tsvwg-chairs <tsvwg-chairs@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, "quic@ietf.org" <quic@ietf.org>, "saag@ietf.org" <saag@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <7E9CB639-6CAD-4152-8927-86EC44DF5B9A@strayalpha.com>
References: <CE03DB3D7B45C245BCA0D2432779493630766752@MX307CL04.corp.emc.com> <4460_1571933453_5DB1CD0D_4460_57_4_5AE9CCAA1B4A2248AB61B4C7F0AD5FB931F030A0@OPEXCAUBM44.corporate.adroot.infra.ftgroup> <1572918247420.10381@cs.auckland.ac.nz> <CABcZeBPy_39o37snzy8F6iyLQMg1aGkYbhy0A1N-PxFUmAmB0g@mail.gmail.com> <f2b1f803-b559-a166-8009-baff551bec5c@joelhalpern.com>
To: "Joel M. Halpern" <jmh@joelhalpern.com>
X-Mailer: Apple Mail (2.3445.9.1)
X-OutGoing-Spam-Status: No, score=-1.0
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server217.web-hosting.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - strayalpha.com
X-Get-Message-Sender-Via: server217.web-hosting.com: authenticated_id: touch@strayalpha.com
X-Authenticated-Sender: server217.web-hosting.com: touch@strayalpha.com
X-Source: 
X-Source-Args: 
X-Source-Dir: 
X-From-Rewrite: unmodified, already matched
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/b8gfB29C3ytC0buUG0dGHqo4IXs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 02:48:17 -0000

> On Nov 4, 2019, at 6:39 PM, Joel M. Halpern <jmh@joelhalpern.com> =
wrote:
>=20
> If the authors want to publish it as an RFC so as to comment on other =
RFCs, they could approach the Independent Stream Editor.  That sort of =
publication is one of the explicit purposes of the Independent Stream.

That only happens if the WG and IESG say this is out of scope for the =
IETF. I.e., the ISE isn=E2=80=99t an end-run.

IMO, given the fact that this is squarely within TSVWG and there=E2=80=99s=
 no consensus, the way forward is clear.

Not every ID turns into an RFC, nor should it.

Joe=


From nobody Mon Nov  4 20:06:19 2019
Return-Path: <jmh@joelhalpern.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 B10BD12003F; Mon,  4 Nov 2019 20:06:17 -0800 (PST)
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 (1024-bit key) header.d=joelhalpern.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 u73f2vGFNedt; Mon,  4 Nov 2019 20:06:16 -0800 (PST)
Received: from maila2.tigertech.net (maila2.tigertech.net [208.80.4.152]) (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 108F312002F; Mon,  4 Nov 2019 20:06:16 -0800 (PST)
Received: from localhost (localhost [127.0.0.1]) by maila2.tigertech.net (Postfix) with ESMTP id 476bgr00GWz1x0MG; Mon,  4 Nov 2019 20:06:16 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=joelhalpern.com; s=2.tigertech; t=1572926776; bh=Lje+uXNlnXInbUhNE/+tD+X7+7fIBoMR2+dA7T66uSs=; h=Subject:To:Cc:References:From:Date:In-Reply-To:From; b=ZlGlZ52OVBWzkCIcwIXUT0dpICycA6pyVwaS049+drHqSnjzQOLZJKR5/XTZ0lh/A 4cVUVFUvlTCSUIphb0dk2GppRuYYhKnVrzg3L7Gzw8m9P44CUGnqalaVSKbLHUDCy5 shen4pDYRJFAeODXp9TEO+xPUsRxHx9ubDihmVFI=
X-Virus-Scanned: Debian amavisd-new at maila2.tigertech.net
Received: from [192.168.128.43] (209-255-163-147.ip.mcleodusa.net [209.255.163.147]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by maila2.tigertech.net (Postfix) with ESMTPSA id 476bgp1XHfz1x0M3; Mon,  4 Nov 2019 20:06:14 -0800 (PST)
Subject: Re: [tsvwg] [OPSAWG] TSVWG WGLC: draft-ietf-tsvwg-transport-encrypt-08, closes 23 October 2019
To: Joe Touch <touch@strayalpha.com>
Cc: Peter Gutmann <pgut001@cs.auckland.ac.nz>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>, tsvwg-chairs <tsvwg-chairs@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, "quic@ietf.org" <quic@ietf.org>, "saag@ietf.org" <saag@ietf.org>
References: <CE03DB3D7B45C245BCA0D2432779493630766752@MX307CL04.corp.emc.com> <4460_1571933453_5DB1CD0D_4460_57_4_5AE9CCAA1B4A2248AB61B4C7F0AD5FB931F030A0@OPEXCAUBM44.corporate.adroot.infra.ftgroup> <1572918247420.10381@cs.auckland.ac.nz> <CABcZeBPy_39o37snzy8F6iyLQMg1aGkYbhy0A1N-PxFUmAmB0g@mail.gmail.com> <f2b1f803-b559-a166-8009-baff551bec5c@joelhalpern.com> <7E9CB639-6CAD-4152-8927-86EC44DF5B9A@strayalpha.com>
From: "Joel M. Halpern" <jmh@joelhalpern.com>
Message-ID: <fe8c3f2f-3a8d-0ec6-d491-559521422aa6@joelhalpern.com>
Date: Mon, 4 Nov 2019 23:06:10 -0500
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <7E9CB639-6CAD-4152-8927-86EC44DF5B9A@strayalpha.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/TrxnyPba2ksIQfjOyOayUXBk65M>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 04:06:18 -0000

Actually Joe, the rules clearly allow the case wehre an Independent 
Stream I-D disagrees with the IETF rough consensus.  Many such have been 
published.  Some of them were held so that they were not published until 
the relevant IETF work was published.

To be explicit, while the IESG can request that the ISE not publish 
something, and can provide a note they wish to have included if it is 
published, they do not have the power to enforce a do-not-publish if the 
ISE disagrees.
And Joe, you have lived aspects of this more closely than I have, so I 
am sure you are aware of it.

Yours,
Joel

On 11/4/2019 9:48 PM, Joe Touch wrote:
> 
> 
>> On Nov 4, 2019, at 6:39 PM, Joel M. Halpern <jmh@joelhalpern.com> wrote:
>>
>> If the authors want to publish it as an RFC so as to comment on other RFCs, they could approach the Independent Stream Editor.  That sort of publication is one of the explicit purposes of the Independent Stream.
> 
> That only happens if the WG and IESG say this is out of scope for the IETF. I.e., the ISE isnâ€™t an end-run.
> 
> IMO, given the fact that this is squarely within TSVWG and thereâ€™s no consensus, the way forward is clear.
> 
> Not every ID turns into an RFC, nor should it.
> 
> Joe
> 


From nobody Tue Nov  5 00:49:20 2019
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 7B86B120289 for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 00:49:11 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.996
X-Spam-Level: 
X-Spam-Status: No, score=-0.996 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_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=0.001, URIBL_BLOCKED=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 o6XhlPwtGmie for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 00:49:10 -0800 (PST)
Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 A03201207FB for <quic@ietf.org>; Tue,  5 Nov 2019 00:49:09 -0800 (PST)
Received: by mail-ed1-x534.google.com with SMTP id c4so15500564edl.0 for <quic@ietf.org>; Tue, 05 Nov 2019 00:49:09 -0800 (PST)
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=WDVcj/zkxtAp9DCuqfyS3606kQOWOdd14ESkNCxxvxY=; b=HgHqIeI05DCABRv0AW7+t5J5dHv4CJJh/LZfPiHhCUm89eT2JojVQWiX68PK/q6l49 9AmkeB8niH0FyqaJF0z8GFBznOiCLzksIUQZKZNMaEFfUyUoKiuzjcfsOfuXc6VFFphK 1ArC0qTN1MGNfRYtdaIheLopNip2QeKS+P6aQCwiSpcbOrRmccInJ3GqwMzya+RxRNqk ehkAEcVfUovBbmygKopEx/eFVUTnaQrGGdWnRzotY/zrRnbJ2egIxNe+USdidR2qvlg5 xV3OWvUkmKLs9aPV9mqsWeI2TKfl6DwoPYAU7zzQcqx25/h7udNC+SXSRKQLiakSvOCc LfUw==
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=WDVcj/zkxtAp9DCuqfyS3606kQOWOdd14ESkNCxxvxY=; b=SxGnOX+gH/N3AUz2gtJkND+aCQqVmBQwYUirkl6LxSE3q+ntYZxrjj/pC8oQMuijmx LdHy9KLXzw3/pUeDCWzq6RzCQh94v9Gf9yxTBSKSSyoacgIIkpLAfoXxyMuDkuVcd4EV Wrz9g1dVNURwtY4ZdBZXWuzMx0698fOKVH77nIzpPuvvleOc22MeeiHhlBPOfxJLxiTA CYOLL8teZcPz3M8mK9BWaXyPwmMp5C5kpuIFBUnVMb+9bpNnYiCFAVJP9esjzb/cSdzT 7guWI9FujWuYoEE6PxuJxqfktbEDyfn2ggzhlBt3uE8YXsPCVk7GKH/O0ohkqrkgpeE/ yU+g==
X-Gm-Message-State: APjAAAVBxOde+UcO/E9fhDHe6jYbZ9gSnJmG7wUbqvqeqOx+Zlz8rVrQ OQz0eZCJDguK1MGdkcdtMAHg6UeiI5ViznBS5KNtXNbH
X-Google-Smtp-Source: APXvYqzuatedgNH1QZu1dw2ZoTkgRVCeIynwrPJEhitUfVDWFObmvk+kjCJ2ScveZXIR2XnYZWWmu1HuP73xRw5PS+k=
X-Received: by 2002:a17:906:4d93:: with SMTP id s19mr17370225eju.285.1572943748116;  Tue, 05 Nov 2019 00:49:08 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 5 Nov 2019 09:49:07 +0100
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <CACpbDcetR7e01oDZ7_hihB2mpbKbOuydp6mHd474bduaMA5rbA@mail.gmail.com>
References: <CAPDSy+6E79OySoOLbJ8eWp0J-+3yeB5iGvj6sW19bEDn_V7-NA@mail.gmail.com> <CANatvzzaWFgrvnaV=VeZRAVvxqSBeMSZT5aMUu7-Vh9raeZJFw@mail.gmail.com> <BN6PR2201MB1700184D81061E2CBFD77BFBDA620@BN6PR2201MB1700.namprd22.prod.outlook.com> <e24ecddd-139d-4669-be96-b3de57557c4e@www.fastmail.com> <CACpbDcci5R7Szti7LbpH7GEm9jT2fP_Jz99Mx-bBcSe8RT43cQ@mail.gmail.com> <d5c3b4d3-2202-41d7-9ebe-3541ceec1b78@www.fastmail.com> <CACpbDcetR7e01oDZ7_hihB2mpbKbOuydp6mHd474bduaMA5rbA@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Tue, 5 Nov 2019 09:49:07 +0100
Message-ID: <CAN1APdfGjt=rzU+iP+iDQvpPpCu5LCq94eUxxei7qWHZKsbNJA@mail.gmail.com>
Subject: Re: Version Ossification: Intended Scope for QUICv1
To: Jana Iyengar <jri.ietf@gmail.com>, Martin Thomson <mt@lowentropy.net>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005bb5d5059695811a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/wBAD89Jx9rJfPCIoa4ojKZLcfVU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 08:49:12 -0000

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

I really don=E2=80=99t think the draft should recommend key deployments lik=
e that.
It may be that baked into the binary works, but sound deployment advise is
to use an environment variable for such things, then you can bake it into
you deployment script if you wish. Point being, the WG should not be too
specific here.


On 5 November 2019 at 03.22.32, Jana Iyengar (jri.ietf@gmail.com) wrote:

On Mon, Nov 4, 2019 at 5:58 PM Martin Thomson <mt@lowentropy.net> wrote:

> On Tue, Nov 5, 2019, at 12:23, Jana Iyengar wrote:
> > On Sun, Nov 3, 2019 at 1:46 PM Martin Thomson <mt@lowentropy.net> wrote=
:
> > > Why can't servers just bake the "keys" into binaries? I mean, that's
> not something that is likely to get lost. And it isn't really the case th=
at
> keys need to be secret, they just have to change often enough to frustrat=
e
> attempts to fixate on them.
> >
> > This is a fine idea, but how does it change anything? Whenever the keys
> > are rotated at the server, you would still have to deal with old
> > versions appearing at the server, no?
>
> I'm assuming that you can a) limit the time over which a token could
> appear, b) use a key identifier so that keys can be changed, and c) keep
> old keys in the code until the associated tokens are all expired.
>

Right, that makes sense. I think your point about not requiring this to be
rotated frequently is a good one, and we might even want to suggest your
idea of baking the key into the binary.

--0000000000005bb5d5059695811a
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">I really don=E2=80=
=99t think the draft should recommend key deployments like that.</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">It may be that baked in=
to the binary works, but sound deployment advise is to use an environment v=
ariable for such things, then you can bake it into you deployment script if=
 you wish. Point being, the WG should not be too specific here.</div> <div =
id=3D"bloop_sign_1572943567280581120" class=3D"bloop_sign"><div style=3D"fo=
nt-family:helvetica,arial;font-size:13px"><br></div></div> <br><p class=3D"=
airmail_on">On 5 November 2019 at 03.22.32, Jana Iyengar (<a href=3D"mailto=
:jri.ietf@gmail.com">jri.ietf@gmail.com</a>) wrote:</p> <blockquote type=3D=
"cite" class=3D"clean_bq"><span><div><div></div><div>


<title></title>


<div dir=3D"ltr">
<div dir=3D"ltr">On Mon, Nov 4, 2019 at 5:58 PM Martin Thomson
&lt;<a href=3D"mailto:mt@lowentropy.net">mt@lowentropy.net</a>&gt;
wrote:<br></div>
<div class=3D"gmail_quote">
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-=
left:1px solid rgb(204,204,204);padding-left:1ex">
On Tue, Nov 5, 2019, at 12:23, Jana Iyengar wrote:<br>
&gt; On Sun, Nov 3, 2019 at 1:46 PM Martin Thomson &lt;<a href=3D"mailto:mt=
@lowentropy.net" target=3D"_blank">mt@lowentropy.net</a>&gt; wrote:<br>
&gt; &gt; Why can&#39;t servers just bake the &quot;keys&quot; into binarie=
s? I
mean, that&#39;s not something that is likely to get lost. And it isn&#39;t
really the case that keys need to be secret, they just have to
change often enough to frustrate attempts to fixate on them.<br>
&gt;<br>
&gt; This is a fine idea, but how does it change anything? Whenever
the keys<br>
&gt; are rotated at the server, you would still have to deal with
old<br>
&gt; versions appearing at the server, no?<br>
<br>
I&#39;m assuming that you can a) limit the time over which a token
could appear, b) use a key identifier so that keys can be changed,
and c) keep old keys in the code until the associated tokens are
all expired.<br></blockquote>
<div><br></div>
<div>Right, that makes sense. I think your point about not
requiring this to be rotated frequently is a good one, and we might
even want to suggest your idea of baking the key into the
binary.=C2=A0</div>
</div>
</div>


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

--0000000000005bb5d5059695811a--


From nobody Tue Nov  5 00:58:34 2019
Return-Path: <Nicolas.Kuhn@cnes.fr>
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 02C19120811; Tue,  5 Nov 2019 00:58:19 -0800 (PST)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 Pv_ZeXP7Rwno; Tue,  5 Nov 2019 00:58:17 -0800 (PST)
Received: from mx2.cnes.fr (mx2.cnes.fr [194.199.174.201]) (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 B8010120073; Tue,  5 Nov 2019 00:58:15 -0800 (PST)
X-IronPort-AV: E=Sophos; i="5.68,270,1569283200"; d="scan'208,217"; a="30612494"
X-IPAS-Result: =?us-ascii?q?A2H0AQBeOMFd/wIBeApmGwEBAQEBAQEFAQEBEQEBAwMBA?= =?us-ascii?q?QGBfYEcgQRZE3USNKhciAsJAQEBAQEBAQEBLQcBAgEBhEAChA8kOBMCDgEBA?= =?us-ascii?q?QQBAQEBAQUCAQECAmmEa0wMhikBMEwSAQUQFVYmAQQBDQ0TgwiBeX4PsH8ag?= =?us-ascii?q?3IBASsBhgwGgTaBZYoRgjSBEUaBTlCBcIFeAgIBF4ExGINAgiwEjQSIM5g9B?= =?us-ascii?q?4E4b4I0hF6FVIhtdYFHh1qEHgOLMI5DiC6TOyMqgS4zGieDOU8RjCGFCAE2R?= =?us-ascii?q?IFQCIw3AYENAQE?=
X-URL-LookUp-ScanningError: 1
From: Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>
To: "etosat@ietf.org" <etosat@ietf.org>, IETF QUIC WG <quic@ietf.org>, "iccrg@irtf.org" <iccrg@irtf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "nwcrg@irtf.org" <nwcrg@irtf.org>, "'ippm@ietf.org'" <ippm@ietf.org>
CC: "'gorry@erg.abdn.ac.uk'" <gorry@erg.abdn.ac.uk>, Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>, STEPHAN Emile RD-CORE-LAN <emile.stephan@orange.com>
Subject: [IETF106] Proposed workshop on QUIC performance over high BDP 
Thread-Topic: [IETF106] Proposed workshop on QUIC performance over high BDP 
Thread-Index: AdWTswmtyrTk4rMVQHq6iFdj1DlU3g==
Date: Tue, 5 Nov 2019 08:57:10 +0000
Deferred-Delivery: Tue, 5 Nov 2019 08:58:10 +0000
Message-ID: <F3B0A07CFD358240926B78A680E166FF1ECE4F1F@TW-MBX-P03.cnesnet.ad.cnes.fr>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-tm-as-product-ver: SMEX-11.0.0.4255-8.100.1062-25022.005
x-tm-as-result: No--17.598900-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_F3B0A07CFD358240926B78A680E166FF1ECE4F1FTWMBXP03cnesnet_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/hUFrvhHg0yry3mUIGFpJ_9q4azY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 08:58:19 -0000

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

Hi,

There are multiple drafts related to the performance of QUIC over large BDP=
 networks (draft-kuhn-quic-4-sat, draft-kuhn-quic-0rtt-bdp, draft-ietf-quic=
-recovery) or related to the performance of encrypted protocols in general =
(draft-fairhurst-tsvwg-cc).
The objective of this workshop is to gather people interested in such activ=
ity and discuss the best way towards better end user experience in this use=
 case.

Details : https://trac.ietf.org/trac/ietf/meeting/wiki/106sidemeetings
Time : 3pm30 - 4pm30 on Wednesday
Where : Bras Basah https://datatracker.ietf.org/meeting/106/floor-plan?room=
=3Dbras-basah#raffles-city-convention-center

Proposed agenda:
Introduction : contributions that showed performance issues with QUIC over =
satellite links
draft-kuhn-quic-0rtt-bdp : solution to let both client and server know the =
path characteristics
draft-kuhn-quic-4-sat : what can be done once both client and server have t=
his information
draft-fairhurst-tsvwg-cc : generalization to any transport and best current=
 practice on internet congestion control at end points
If time permits: sharing experimental results (interaction between transpor=
t and high BDP systems)

If there is anything you would like to present please let us know.

Kind regards,

Nico, Gorry and Emile

--_000_F3B0A07CFD358240926B78A680E166FF1ECE4F1FTWMBXP03cnesnet_
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<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:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
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;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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"FR" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi, <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">There are multiple drafts relat=
ed to the performance of QUIC over large BDP networks (draft-kuhn-quic-4-sa=
t, draft-kuhn-quic-0rtt-bdp, draft-ietf-quic-recovery) or related to the pe=
rformance of encrypted protocols in
 general (draft-fairhurst-tsvwg-cc). <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The objective of this workshop =
is to gather people interested in such activity and discuss the best way to=
wards better end user experience in this use case.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Details : <a href=3D"https://tr=
ac.ietf.org/trac/ietf/meeting/wiki/106sidemeetings">
https://trac.ietf.org/trac/ietf/meeting/wiki/106sidemeetings</a> <o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Time : 3pm30 &#8211; 4pm30 on W=
ednesday <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Where : Bras Basah </span><a hr=
ef=3D"https://datatracker.ietf.org/meeting/106/floor-plan?room=3Dbras-basah=
#raffles-city-convention-center"><span lang=3D"EN-US">https://datatracker.i=
etf.org/meeting/106/floor-plan?room=3Dbras-basah#raffles-city-convention-ce=
nter</span></a>
<span lang=3D"EN-US"><o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Proposed agenda:&nbsp; <o:p></o=
:p></span></p>
<p class=3D"MsoNormal" style=3D"text-indent:35.4pt"><span lang=3D"EN-US">In=
troduction : contributions that showed performance issues with QUIC over sa=
tellite links<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:35.4pt"><span lang=3D"EN-US">dr=
aft-kuhn-quic-0rtt-bdp : solution to let both client and server know the pa=
th characteristics
<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:35.4pt"><span lang=3D"EN-US">dr=
aft-kuhn-quic-4-sat : what can be done once both client and server have thi=
s information<o:p></o:p></span></p>
<p class=3D"MsoNormal" style=3D"margin-left:35.4pt"><span lang=3D"EN-US">dr=
aft-fairhurst-tsvwg-cc : generalization to any transport and best current p=
ractice on internet congestion control at end points
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">If time permits: sharing experi=
mental results (interaction between transport and high BDP systems)<o:p></o=
:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">If there is anything you would =
like to present please let us know.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><br>
Kind regards,<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Nico, Gorry and Emile<o:p></o:p=
></span></p>
</div>
</body>
</html>

--_000_F3B0A07CFD358240926B78A680E166FF1ECE4F1FTWMBXP03cnesnet_--


From nobody Tue Nov  5 01:13:04 2019
Return-Path: <hannu.flinck@nokia-bell-labs.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 256FF120844 for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 01:13:02 -0800 (PST)
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, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 (1024-bit key) header.d=nokia.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 OUmJLBuHFcZe for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 01:12:59 -0800 (PST)
Received: from EUR04-DB3-obe.outbound.protection.outlook.com (mail-eopbgr60124.outbound.protection.outlook.com [40.107.6.124]) (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 8FF10120841 for <quic@ietf.org>; Tue,  5 Nov 2019 01:12:59 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=G56Hmzoc7yTYDoK7aRw4Mdj26e6/SsX75q78CknHL/qqBfsWvaGcFf1lZlsMA+3g4VCA9fglJoADXCxChDm94NHu7OoPITX+xNM8km5PVrib2iOkVrkbpqs+Fc/LfbI/VwGqGY5F+19CWDiJNMSEOIdP/6YL6Mf1hu0OpROdYSpBhm/DxnSUW38RGZnKmuf+nhZ2Pv9EcfEDeuTj49jSLZkXLs/7EtAx3GIa3Pus9u6tP7OD9/VOAjczUTkMFNOIrRxX+EOn0EMgr+U/oeL9K4JD5yRKwpgSJpcJ7Uesa/jnl08FCn06HK9rq+DnUjY5zOkQOSJubBE6IBlLwdoQbQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=IiYN8TkfaykYRBKFYs5+KJBofka2BVeRPef9nN26gmQ=; b=MtoMxc7sq+Puu1/lQ4+PdU7ft1A5dqGsFLmlQmg0eveiRnjhO/sWdi4Q5TDBteuEZoh4ukYLU2t5kn7efSK1tEo8RGK1D4vyVyTmC2c7Hr5SQ2gjqE3GtwC121IhzB+CFwIY43iTaL9e9trcj3JJUNltcKYhU5dn4tePzefKGr8F5e7ehs5sS1XQNV/DKUJJw70DD9GxbnXOE2eaV4NXTgxgEE0cBdCpFMAscwN/LlWPXAg6i0ix6PjcqO7EVgHTV8eDDNQWbRzVczT2FHofGoiszabQoRB+6tFmMa785HXF/RbN9y82HnX1lK7pO6c/av5MKwi1P+5oZ6kBCqGKFw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=nokia-bell-labs.com; dmarc=pass action=none header.from=nokia-bell-labs.com; dkim=pass header.d=nokia-bell-labs.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=nokia.onmicrosoft.com;  s=selector1-nokia-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=IiYN8TkfaykYRBKFYs5+KJBofka2BVeRPef9nN26gmQ=; b=RUkfK/QzA1j6/JvIM/fwR5xCyO0l+BBTKhaGIA7nolEFmNDjbhLDuU30/l7htD2Zp28qv29UkPjT4Rl67bDvSoyurydoJRCdNMGxJBTKzUNj6gaSGhGsXi3kSlZ5AM6QFVAQaTptxDRgX6ym7lQDyDRO0jNYCzhIL8gDh4KzBTQ=
Received: from HE1PR07MB3306.eurprd07.prod.outlook.com (10.170.242.27) by HE1PR07MB3385.eurprd07.prod.outlook.com (10.170.244.146) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2408.15; Tue, 5 Nov 2019 09:12:54 +0000
Received: from HE1PR07MB3306.eurprd07.prod.outlook.com ([fe80::ed4e:9a7a:99c3:f4c1]) by HE1PR07MB3306.eurprd07.prod.outlook.com ([fe80::ed4e:9a7a:99c3:f4c1%6]) with mapi id 15.20.2408.016; Tue, 5 Nov 2019 09:12:54 +0000
From: "Flinck, Hannu (Nokia - FI/Espoo)" <hannu.flinck@nokia-bell-labs.com>
To: Jana Iyengar <jri.ietf@gmail.com>, "Salz, Rich" <rsalz@akamai.com>
CC: David Schinazi <dschinazi.ietf@gmail.com>, Ted Hardie <ted.ietf@gmail.com>, "Lubashev, Igor" <ilubashe@akamai.com>, Martin Thomson <mt@lowentropy.net>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Proposed response to the 3GPP Liaison Statement
Thread-Topic: Proposed response to the 3GPP Liaison Statement
Thread-Index: AQHVk3MjNniwyX9WDk+/sAGVUFFHQ6d8SWsw
Date: Tue, 5 Nov 2019 09:12:54 +0000
Message-ID: <HE1PR07MB3306A309F29ED901A2957D1D9B7E0@HE1PR07MB3306.eurprd07.prod.outlook.com>
References: <3218A80B-DAFD-43EF-8200-F99C660DF9C9@mnot.net> <5557f717-ae03-46a2-aa9f-54f019a07533@www.fastmail.com> <CA+9kkMBbuG+4309XfZoVb69Pz_s3=RPv2JWZS8zrkVFBkDMJuw@mail.gmail.com> <614379f7e12f46c6b38b7928e999cbab@ustx2ex-dag1mb5.msg.corp.akamai.com> <CAPDSy+6PHwfVReNsAFMHE3KsvM2K_ACD7sUtqikri7oG-QGfLg@mail.gmail.com> <E68585EA-E67A-4C4D-8BE3-5E5880B24056@akamai.com> <CACpbDccE4OubiRQAAUyxthrmtdQJsaSKNmuV+HkFiJKXCJtOow@mail.gmail.com>
In-Reply-To: <CACpbDccE4OubiRQAAUyxthrmtdQJsaSKNmuV+HkFiJKXCJtOow@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=hannu.flinck@nokia-bell-labs.com; 
x-originating-ip: [131.228.2.14]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 7773b87b-ccdf-4365-15fb-08d761d05754
x-ms-traffictypediagnostic: HE1PR07MB3385:
x-microsoft-antispam-prvs: <HE1PR07MB3385AF323E455069F58FD9BF9B7E0@HE1PR07MB3385.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7219;
x-forefront-prvs: 0212BDE3BE
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(366004)(346002)(396003)(376002)(39860400002)(189003)(199004)(81166006)(25786009)(55016002)(236005)(9686003)(186003)(71190400001)(446003)(53546011)(6506007)(7696005)(76176011)(66556008)(14454004)(2906002)(3846002)(102836004)(66066001)(6306002)(86362001)(8676002)(26005)(66946007)(76116006)(66446008)(790700001)(64756008)(4326008)(71200400001)(6116002)(52536014)(5660300002)(66476007)(7736002)(11346002)(81156014)(8936002)(478600001)(6246003)(476003)(486006)(74316002)(99286004)(229853002)(110136005)(54906003)(33656002)(6436002)(256004)(54896002)(316002); DIR:OUT; SFP:1102; SCL:1; SRVR:HE1PR07MB3385; H:HE1PR07MB3306.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:0; 
received-spf: None (protection.outlook.com: nokia-bell-labs.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: FhqsbpoXFHmt7RT8ttwJvXUXC3eITAecuwVTF0913gsIgXDkDBdkjm0oWDmo9zi2p/PghpxMNdGIjcCFreeaEPhHiNddFuP1rlJTs2zaTg3YEMdl6V+Y87BWvgm0jY8m7mAQ8KRgaKUb/jZJ40hrCs5xc6YWZMjHOoT1guhhKbMJ0by3Y0/2zxJhZ/yNp6h+0X1vzX8Zh9NgSytcsTU84vxN1etPR2WJPYVe2pJElb9RgBcdO3S+Zud5LfPPDRsDzkZjxw2TUg9kvcjbnp2wCgBl/Ph+RuqXAbDw9oGy584dU6GUYEEViakMC2zOOYfCbQhBPcXnuaoD6s18YUceDqADQFogLPO92MFR+Co3Xp1+Ll+mqFPiqQMWC3ut4xR5YzYD3Jc2d+gHwsVSLKr7R3rUbBs1qCL2Xta31e6Rq1xtEXB5ugk7i40ZqU67L4FS
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_HE1PR07MB3306A309F29ED901A2957D1D9B7E0HE1PR07MB3306eurp_"
MIME-Version: 1.0
X-OriginatorOrg: nokia-bell-labs.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 7773b87b-ccdf-4365-15fb-08d761d05754
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Nov 2019 09:12:54.1035 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5d471751-9675-428d-917b-70f44f9630b0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 8x6x1L8yMgx+9hZoZroill6ZXvzkwhGyuqweTCSx04KVOanJXq/tWiHnKaZ8QRN2iyfciqbs8ZT9hCNNsZrLL8mTSbUeATYIDyVW1fE0M9hCMORO/qLl8dCUVJiXC6Uo
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR07MB3385
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/31lCL90mv_Xf1Kc-c7-0F73WrJw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 09:13:02 -0000

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

M0dQUCBpcyB1c2luZyBIVFBQIHZlcnkgd2VsbCBpbiB0aGVpciB1c2UgY2FzZSAoc2VlIG1vcmUg
aW4gM0dQUCAyOS41MDAsIFRlY2huaWNhbCBSZWFsaXphdGlvbiBvZiBTZXJ2aWNlIEJhc2VkIEFy
Y2hpdGVjdHVyZS4pLiBJbnNpc3RpbmcgZm9jdXMgb24gSFRUUCBpbiB0aGUgcmVzcG9uc2UgaXMg
bm90IGhlbHBmdWwsIGJ1dCBjb25mdXNpbmcgaW5zdGVhZC4NCg0KQmVzdCByZWdhcmRzDQpIYW5u
dQ0KDQpGcm9tOiBRVUlDIDxxdWljLWJvdW5jZXNAaWV0Zi5vcmc+IE9uIEJlaGFsZiBPZiBKYW5h
IEl5ZW5nYXINClNlbnQ6IFR1ZXNkYXksIE5vdmVtYmVyIDUsIDIwMTkgMjo1MSBBTQ0KVG86IFNh
bHosIFJpY2ggPHJzYWx6QGFrYW1haS5jb20+DQpDYzogRGF2aWQgU2NoaW5hemkgPGRzY2hpbmF6
aS5pZXRmQGdtYWlsLmNvbT47IFRlZCBIYXJkaWUgPHRlZC5pZXRmQGdtYWlsLmNvbT47IEx1YmFz
aGV2LCBJZ29yIDxpbHViYXNoZUBha2FtYWkuY29tPjsgTWFydGluIFRob21zb24gPG10QGxvd2Vu
dHJvcHkubmV0PjsgSUVURiBRVUlDIFdHIDxxdWljQGlldGYub3JnPg0KU3ViamVjdDogUmU6IFBy
b3Bvc2VkIHJlc3BvbnNlIHRvIHRoZSAzR1BQIExpYWlzb24gU3RhdGVtZW50DQoNClRoZSByZXNw
b25zZSBsb29rcyBzZW5zaWJsZSBhbmQgYWNjdXJhdGUuDQoNCkkgd291bGQgc3VnZ2VzdCBqdXN0
IG9uZSBjaGFuZ2U6IG1vdmUgdGhlIHBvaW50IGFib3V0IEhUVFAvMyBmb2N1cyAobWF5YmUgdGhl
IGxhc3QgdHdvIHBhcmFzKSB0byB0aGUgdG9wIG9mIHRoZSByZXNwb25zZSwgYWRkaW5nIHRvIGl0
IHRoYXQgdGhlIFFVSUMgd2cgaXMgY3VycmVudGx5IGNoYXJ0ZXJlZCB0byBmb2N1cyBvbiBIVFRQ
LiBXaXRob3V0IGdldHRpbmcgaW50byB0aGUgdXNlIGNhc2UgdGhhdCB0aGV5IGFyZSB0cnlpbmcg
dG8gZml0IFFVSUMgaW50bywgaXQncyBkaWZmaWN1bHQgdG8gdW5kZXJzdGFuZCB0aGUgaW1wb3J0
YW5jZSBvZiB0aGUgbG9zcyBiaXRzLiBBbmQgd2Ugc3VyZWx5IGRvIG5vdCB3YW50IHRvIGJsb2Nr
IFFVSUN2MSB0cnlpbmcgdG8gdW5kZXJzdGFuZCB0aGF0IHVzZSBjYXNlLg0KDQpPbiBUaHUsIE9j
dCAzMSwgMjAxOSBhdCAzOjU3IFBNIFNhbHosIFJpY2ggPHJzYWx6QGFrYW1haS5jb208bWFpbHRv
OnJzYWx6QGFrYW1haS5jb20+PiB3cm90ZToNCk1heWJlIHdlIHNob3VsZCBzdWdnZXN0IHRoYXQg
dGhleSB3cml0ZSBhbiBJLUQgZm9yIHdoYXQgdGhleSB0aGluayB0aGVpciByZXF1aXJlbWVudHMg
YXJlPw0KDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBjbTsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQph
OmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xv
cjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2aXNpdGVkLCBzcGFuLk1z
b0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xvcjpwdXJw
bGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLm1zb25vcm1hbDAsIGxpLm1zb25v
cm1hbDAsIGRpdi5tc29ub3JtYWwwDQoJe21zby1zdHlsZS1uYW1lOm1zb25vcm1hbDsNCgltc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4tcmlnaHQ6MGNtOw0KCW1zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBjbTsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZv
bnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCnNwYW4uRW1haWxTdHlsZTE4DQoJe21z
by1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5z
LXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNvLXN0eWxl
LXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJ
bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVM7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6
NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3MC44NXB0IDIuMGNtIDcwLjg1cHQgMi4wY207fQ0K
ZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1b
aWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1h
eD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0K
PG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9
IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9k
eSBsYW5nPSJGSSIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3Jk
U2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxl
PSJtc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+M0dQUCBpcyB1c2luZyBIVFBQIHZlcnkgd2Vs
bCBpbiB0aGVpciB1c2UgY2FzZSAoc2VlIG1vcmUgaW4gM0dQUCAyOS41MDAsDQo8L3NwYW4+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpaSC1DTiI+VGVjaG5p
Y2FsIFJlYWxpemF0aW9uIG9mIFNlcnZpY2UgQmFzZWQgQXJjaGl0ZWN0dXJlLjwvc3Bhbj48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4pLiBJbnNp
c3RpbmcgZm9jdXMgb24gSFRUUCBpbiB0aGUgcmVzcG9uc2UgaXMgbm90IGhlbHBmdWwsIGJ1dCBj
b25mdXNpbmcgaW5zdGVhZC4NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4t
VVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkJlc3Qg
cmVnYXJkczxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IGxhbmc9IkVOLVVTIiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPkhhbm51IDxv
OnA+DQo8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0i
RU4tVVMiIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFuZz0iRU4tVVMi
PkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyI+IFFVSUMgJmx0O3F1aWMtYm91bmNl
c0BpZXRmLm9yZyZndDsNCjxiPk9uIEJlaGFsZiBPZiA8L2I+SmFuYSBJeWVuZ2FyPGJyPg0KPGI+
U2VudDo8L2I+IFR1ZXNkYXksIE5vdmVtYmVyIDUsIDIwMTkgMjo1MSBBTTxicj4NCjxiPlRvOjwv
Yj4gU2FseiwgUmljaCAmbHQ7cnNhbHpAYWthbWFpLmNvbSZndDs8YnI+DQo8Yj5DYzo8L2I+IERh
dmlkIFNjaGluYXppICZsdDtkc2NoaW5hemkuaWV0ZkBnbWFpbC5jb20mZ3Q7OyBUZWQgSGFyZGll
ICZsdDt0ZWQuaWV0ZkBnbWFpbC5jb20mZ3Q7OyBMdWJhc2hldiwgSWdvciAmbHQ7aWx1YmFzaGVA
YWthbWFpLmNvbSZndDs7IE1hcnRpbiBUaG9tc29uICZsdDttdEBsb3dlbnRyb3B5Lm5ldCZndDs7
IElFVEYgUVVJQyBXRyAmbHQ7cXVpY0BpZXRmLm9yZyZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4g
UmU6IFByb3Bvc2VkIHJlc3BvbnNlIHRvIHRoZSAzR1BQIExpYWlzb24gU3RhdGVtZW50PG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhlIHJlc3BvbnNlIGxvb2tzIHNlbnNp
YmxlIGFuZCBhY2N1cmF0ZS48YnI+DQo8YnI+DQpJIHdvdWxkIHN1Z2dlc3QganVzdCBvbmUgY2hh
bmdlOiBtb3ZlIHRoZSBwb2ludCBhYm91dCBIVFRQLzMgZm9jdXMgKG1heWJlIHRoZSBsYXN0IHR3
byBwYXJhcykgdG8gdGhlIHRvcCBvZiB0aGUgcmVzcG9uc2UsIGFkZGluZyB0byBpdCB0aGF0IHRo
ZSBRVUlDIHdnIGlzIGN1cnJlbnRseSBjaGFydGVyZWQgdG8gZm9jdXMgb24gSFRUUC4gV2l0aG91
dCBnZXR0aW5nJm5ic3A7aW50byB0aGUgdXNlIGNhc2UgdGhhdCB0aGV5IGFyZSB0cnlpbmcgdG8g
Zml0IFFVSUMNCiBpbnRvLCBpdCdzIGRpZmZpY3VsdCB0byB1bmRlcnN0YW5kIHRoZSBpbXBvcnRh
bmNlIG9mIHRoZSBsb3NzIGJpdHMuIEFuZCB3ZSBzdXJlbHkgZG8gbm90IHdhbnQgdG8gYmxvY2sg
UVVJQ3YxIHRyeWluZyB0byB1bmRlcnN0YW5kIHRoYXQgdXNlIGNhc2UuPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBUaHUsIE9jdCAzMSwgMjAxOSBhdCAz
OjU3IFBNIFNhbHosIFJpY2ggJmx0OzxhIGhyZWY9Im1haWx0bzpyc2FsekBha2FtYWkuY29tIiB0
YXJnZXQ9Il9ibGFuayI+cnNhbHpAYWthbWFpLmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6
c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdpbi1sZWZ0
OjQuOHB0O21hcmdpbi1yaWdodDowY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1h
cmdpbi1ib3R0b206MTIuMHB0Ij5NYXliZSB3ZSBzaG91bGQgc3VnZ2VzdCB0aGF0IHRoZXkgd3Jp
dGUgYW4gSS1EIGZvciB3aGF0IHRoZXkgdGhpbmsgdGhlaXIgcmVxdWlyZW1lbnRzIGFyZT88YnI+
DQo8YnI+DQo8bzpwPjwvbzpwPjwvcD4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8
L2JvZHk+DQo8L2h0bWw+DQo=

--_000_HE1PR07MB3306A309F29ED901A2957D1D9B7E0HE1PR07MB3306eurp_--


From nobody Tue Nov  5 01:38:35 2019
Return-Path: <ott@in.tum.de>
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 B5F1B120863; Tue,  5 Nov 2019 01:38:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.199
X-Spam-Level: 
X-Spam-Status: No, score=-4.199 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_HELO_NONE=0.001, 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 g4atOR24TqXV; Tue,  5 Nov 2019 01:38:14 -0800 (PST)
Received: from mail-out1.informatik.tu-muenchen.de (mail-out1.in.tum.de [131.159.0.8]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 5F7631201E5; Tue,  5 Nov 2019 01:38:14 -0800 (PST)
Received: by mail.in.tum.de (Postfix, from userid 107) id B695D1C0405; Tue,  5 Nov 2019 10:38:11 +0100 (CET)
Received: (Authenticated sender: ott) by mail.in.tum.de (Postfix) with ESMTPSA id 41EF61C0403; Tue,  5 Nov 2019 10:38:08 +0100 (CET) (Extended-Queue-bit tech_mewyo@fff.in.tum.de)
Subject: Re: [IETF106] Proposed workshop on QUIC performance over high BDP
To: Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>, "etosat@ietf.org" <etosat@ietf.org>,  IETF QUIC WG <quic@ietf.org>, "iccrg@irtf.org" <iccrg@irtf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "nwcrg@irtf.org" <nwcrg@irtf.org>, "'ippm@ietf.org'" <ippm@ietf.org>
Cc: "'gorry@erg.abdn.ac.uk'" <gorry@erg.abdn.ac.uk>, STEPHAN Emile RD-CORE-LAN <emile.stephan@orange.com>
References: <F3B0A07CFD358240926B78A680E166FF1ECE4F1F@TW-MBX-P03.cnesnet.ad.cnes.fr>
From: Joerg Ott <ott@in.tum.de>
Message-ID: <314f4a3c-9e56-26b6-fda3-bc2694f75d3e@in.tum.de>
Date: Tue, 5 Nov 2019 10:38:06 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <F3B0A07CFD358240926B78A680E166FF1ECE4F1F@TW-MBX-P03.cnesnet.ad.cnes.fr>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/5kh5cWaRYo-CqtPpe8jU0zUO25w>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 09:38:17 -0000

Hi guys,

great activity -- we also did extensive emulation studies for QUIC
over satellites in a controlled environment.  Would be happy to
share those findings if room.

Cheers,
Jörg

On 05.11.19 09:57, Kuhn Nicolas wrote:
> Hi,
> 
> There are multiple drafts related to the performance of QUIC over large 
> BDP networks (draft-kuhn-quic-4-sat, draft-kuhn-quic-0rtt-bdp, 
> draft-ietf-quic-recovery) or related to the performance of encrypted 
> protocols in general (draft-fairhurst-tsvwg-cc).
> 
> The objective of this workshop is to gather people interested in such 
> activity and discuss the best way towards better end user experience in 
> this use case.
> 
> Details : https://trac.ietf.org/trac/ietf/meeting/wiki/106sidemeetings
> 
> Time : 3pm30 – 4pm30 on Wednesday
> 
> Where : Bras Basah 
> https://datatracker.ietf.org/meeting/106/floor-plan?room=bras-basah#raffles-city-convention-center 
> 
> 
> Proposed agenda:
> 
> Introduction : contributions that showed performance issues with QUIC 
> over satellite links
> 
> draft-kuhn-quic-0rtt-bdp : solution to let both client and server know 
> the path characteristics
> 
> draft-kuhn-quic-4-sat : what can be done once both client and server 
> have this information
> 
> draft-fairhurst-tsvwg-cc : generalization to any transport and best 
> current practice on internet congestion control at end points
> 
> If time permits: sharing experimental results (interaction between 
> transport and high BDP systems)
> 
> If there is anything you would like to present please let us know.
> 
> 
> Kind regards,
> 
> Nico, Gorry and Emile
> 


From nobody Tue Nov  5 02:12:13 2019
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 5FB5B12088C; Tue,  5 Nov 2019 02:12:05 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 MS0qiq0hE-KT; Tue,  5 Nov 2019 02:12:03 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id 524BE12088B; Tue,  5 Nov 2019 02:12:03 -0800 (PST)
Received: from gorry-mac.erg.abdn.ac.uk (unknown [IPv6:2001:630:42:110:e55f:a14f:6fbb:b4cc]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 97E291B001D2; Tue,  5 Nov 2019 10:11:55 +0000 (GMT)
Subject: Re: [IETF106] Proposed workshop on QUIC performance over high BDP
To: Joerg Ott <ott@in.tum.de>, "etosat@ietf.org" <etosat@ietf.org>, IETF QUIC WG <quic@ietf.org>, "iccrg@irtf.org" <iccrg@irtf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Cc: STEPHAN Emile RD-CORE-LAN <emile.stephan@orange.com>
References: <F3B0A07CFD358240926B78A680E166FF1ECE4F1F@TW-MBX-P03.cnesnet.ad.cnes.fr> <314f4a3c-9e56-26b6-fda3-bc2694f75d3e@in.tum.de>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <05fcdc09-4d86-980c-ced7-30fbc544569e@erg.abdn.ac.uk>
Date: Tue, 5 Nov 2019 10:11:53 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <314f4a3c-9e56-26b6-fda3-bc2694f75d3e@in.tum.de>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/PgMRpashTgLO_oelre2zjHB_P5c>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 10:12:05 -0000

Yes, that sounds fun! - which QUIC implementation were you using, just 
so we can make sure we compare like-with-like, and did you use an 
operational satellite system or an emulation, or something in-between?

Gorry

On 05/11/2019 09:38, Joerg Ott wrote:
> Hi guys,
>
> great activity -- we also did extensive emulation studies for QUIC
> over satellites in a controlled environment.  Would be happy to
> share those findings if room.
>
> Cheers,
> Jörg
>
> On 05.11.19 09:57, Kuhn Nicolas wrote:
>> Hi,
>>
>> There are multiple drafts related to the performance of QUIC over 
>> large BDP networks (draft-kuhn-quic-4-sat, draft-kuhn-quic-0rtt-bdp, 
>> draft-ietf-quic-recovery) or related to the performance of encrypted 
>> protocols in general (draft-fairhurst-tsvwg-cc).
>>
>> The objective of this workshop is to gather people interested in such 
>> activity and discuss the best way towards better end user experience 
>> in this use case.
>>
>> Details : https://trac.ietf.org/trac/ietf/meeting/wiki/106sidemeetings
>>
>> Time : 3pm30 – 4pm30 on Wednesday
>>
>> Where : Bras Basah 
>> https://datatracker.ietf.org/meeting/106/floor-plan?room=bras-basah#raffles-city-convention-center 
>>
>>
>> Proposed agenda:
>>
>> Introduction : contributions that showed performance issues with QUIC 
>> over satellite links
>>
>> draft-kuhn-quic-0rtt-bdp : solution to let both client and server 
>> know the path characteristics
>>
>> draft-kuhn-quic-4-sat : what can be done once both client and server 
>> have this information
>>
>> draft-fairhurst-tsvwg-cc : generalization to any transport and best 
>> current practice on internet congestion control at end points
>>
>> If time permits: sharing experimental results (interaction between 
>> transport and high BDP systems)
>>
>> If there is anything you would like to present please let us know.
>>
>>
>> Kind regards,
>>
>> Nico, Gorry and Emile
>>


From nobody Tue Nov  5 02:26:55 2019
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 57CB01208B1; Tue,  5 Nov 2019 02:26:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 96pqZCMY__5d; Tue,  5 Nov 2019 02:26:51 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:42:150::2]) by ietfa.amsl.com (Postfix) with ESMTP id 12B661208AA; Tue,  5 Nov 2019 02:26:50 -0800 (PST)
Received: from gorry-mac.erg.abdn.ac.uk (unknown [IPv6:2001:630:42:110:e55f:a14f:6fbb:b4cc]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id BF6AB1B001D2; Tue,  5 Nov 2019 10:26:39 +0000 (GMT)
Subject: Re: [OPSAWG] TSVWG WGLC: draft-ietf-tsvwg-transport-encrypt-08, closes 23 October 2019
To: "Joel M. Halpern" <jmh@joelhalpern.com>, Peter Gutmann <pgut001@cs.auckland.ac.nz>
Cc: "tsvwg@ietf.org" <tsvwg@ietf.org>, "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>, tsvwg-chairs <tsvwg-chairs@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, "quic@ietf.org" <quic@ietf.org>, "saag@ietf.org" <saag@ietf.org>
References: <CE03DB3D7B45C245BCA0D2432779493630766752@MX307CL04.corp.emc.com> <4460_1571933453_5DB1CD0D_4460_57_4_5AE9CCAA1B4A2248AB61B4C7F0AD5FB931F030A0@OPEXCAUBM44.corporate.adroot.infra.ftgroup> <1572918247420.10381@cs.auckland.ac.nz> <CABcZeBPy_39o37snzy8F6iyLQMg1aGkYbhy0A1N-PxFUmAmB0g@mail.gmail.com> <f2b1f803-b559-a166-8009-baff551bec5c@joelhalpern.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <5df30dd2-6841-7140-43bf-8c1b9603653f@erg.abdn.ac.uk>
Date: Tue, 5 Nov 2019 10:26:39 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <f2b1f803-b559-a166-8009-baff551bec5c@joelhalpern.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/qLg-KrWRk6rxf4SGCLxw_urAH4k>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 10:26:53 -0000

Thanks for the various comments on process.

I expect both editors and the Chairs to work with our AD to confirm the 
intended scope, and then to decide on the next steps. This author wants 
to clarify how IETF transport protocols have been designed and have 
been/are being used.

Gorry (as one of the editors of this document).


On 05/11/2019 02:39, Joel M. Halpern wrote:
> If the authors want to publish it as an RFC so as to comment on other 
> RFCs, they could approach the Independent Stream Editor.Â  That sort of 
> publication is one of the explicit purposes of the Independent Stream.
>
> Yours,
> Joel
>
> On 11/4/2019 9:34 PM, Eric Rescorla wrote:
>>
>>
>> On Mon, Nov 4, 2019 at 5:44 PM Peter Gutmann 
>> <pgut001@cs.auckland.ac.nz <mailto:pgut001@cs.auckland.ac.nz>> wrote:
>>
>> Â Â Â  I actually think it's a pretty good summary, and delivers exactly 
>> what's
>> Â Â Â  promised in the title.Â  OTOH I can also see that it's going to get
>> Â Â Â  bikeshedded
>> Â Â Â  to death, and will probably never be editable into a form where
>> Â Â Â  people won't
>> Â Â Â  complain about it no matter how many changes are made. 
>> Alternatively, it'll
>> Â Â Â  end up watered down to a point where no-one can complain any more
>> Â Â Â  but it won't
>> Â Â Â  say anything terribly useful by then.
>>
>> Â Â Â  Perhaps it could be published as is with a comment that it
>> Â Â Â  represents the
>> Â Â Â  opinions of the authors?Â  Although given that it's Informational 
>> and not
>> Â Â Â  Standards-track or a BCP, that should be a given anyway.
>>
>>
>> Actually, no. Most IETF documents, even informational ones, bear a 
>> statement that they have IETF Consensus.
>>
>> See: https://tools.ietf.org/html/rfc5741#section-3.2.1 
>> <https://tools.ietf.org/html/rfc5741#section-3..2.1>
>>
>> -Ekr
>>
>>
>> Â Â Â  Peter.
>>
>>
>>
>>
>> _______________________________________________
>> OPSAWG mailing list
>> OPSAWG@ietf.org
>> https://www.ietf.org/mailman/listinfo/opsawg
>>


From nobody Tue Nov  5 04:11:26 2019
Return-Path: <lucaspardue.24.7@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 6EB1A1208ED for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 04:11:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.647
X-Spam-Level: 
X-Spam-Status: No, score=-1.647 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, MIME_BOUND_DIGITS_15=0.1, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=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 9WbTD22oz2Uz for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 04:11:23 -0800 (PST)
Received: from mail-vs1-xe2f.google.com (mail-vs1-xe2f.google.com [IPv6:2607:f8b0:4864:20::e2f]) (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 BF9391208A9 for <quic@ietf.org>; Tue,  5 Nov 2019 04:11:22 -0800 (PST)
Received: by mail-vs1-xe2f.google.com with SMTP id m6so6707680vsn.13 for <quic@ietf.org>; Tue, 05 Nov 2019 04:11:22 -0800 (PST)
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;  bh=3+JtT7gqFn+WsOY0lm2UyHXF1SNRmCtAOmycreAn4mc=; b=VTixmARp+oeKmvG0joKRKxDcbN18msuH0F2M7Cw5b/4ato0C3C5gwJsNi6WzNGwfxz NWFj/kT/KjOAwHT9dR606Kj2mDl4LF/ggkpgOUjcgGlWjejAURaYk2Aa3D96ciUczcuZ V9mOv5kgU5JhSdLQMoxLqAHiLdLDNpwnKld4u/56RDBkQekDq9nWZPoph0VgGg0OwzoS PFwi50IiPLnTxuudl/cBjQEu1fmzxJ4aQ1Z54RxFR8r2TEJkWsu6voV/ehTYQwdaajsm 7vXN3KLDCdpfIkLNwKerNLyGvAgZBkeUadFfqBGZLgLwd++wakhxv5vRDBbpIOMjPH/W RUTg==
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; bh=3+JtT7gqFn+WsOY0lm2UyHXF1SNRmCtAOmycreAn4mc=; b=SiT+K4WpUQppfmudcecCGYcScNet1MAdaBzkmAXAYY0tx6KaqoZP3MwnmEorlT70uk IeZqx6UzX1hPgM1JjWd+2LEWBDZ+bj8CeXnLw7BXH2CvIfLiNXf9ZGXbSb6SA9erJDSR TpW4EqDmb6gQxsbpEC/1YOmsl7lYr5XDTRePoc4mjZQhzsyKGMFt4YNHTZb8UisUsr+W oAF84kGeVYDo9Gb8pOmT08E9K1duB/sSKp4OebOGErKILBfYZy9avWHCUu6jaRVb7dlC GQI2Y/+B60+GRtxnNwsJIQLJRZRCg84P4ueM+vv0vl6RSZ3ZhpdC+KOIiB5U0MpAho1s UTEw==
X-Gm-Message-State: APjAAAXaDLEiKpuo8zQk94M1J5yGz0ZEHMl+CZKo9R5ubFG3Qo1oI6Fn h/lL1acL0tUv7GFG2kBp7gvQuie7qPjY8J2HfyQNMsY3
X-Google-Smtp-Source: APXvYqxIvh0I+2tCo7rkEXTRdriW/k85SM/D0su11m+BojptRidYFzYTGuXs3dbeCh+H/9JD8V1aoKXin8DLb+8iPPc=
X-Received: by 2002:a05:6102:2041:: with SMTP id q1mr15236094vsr.15.1572955881626;  Tue, 05 Nov 2019 04:11:21 -0800 (PST)
MIME-Version: 1.0
References: <157291052116.13928.17523145259269241429.idtracker@ietfa.amsl.com>
In-Reply-To: <157291052116.13928.17523145259269241429.idtracker@ietfa.amsl.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Tue, 5 Nov 2019 12:11:10 +0000
Message-ID: <CALGR9obHr8-iwVooru5BrrYuK4jQRkHEpVwsMMtjpDBj8eFZhQ@mail.gmail.com>
Subject: Fwd: New Version Notification for draft-kazuho-httpbis-priority-03.txt
To: HTTP Working Group <ietf-http-wg@w3.org>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009260610596985454"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/-JMjWsiZEMOjUMu1UBZKB9P1srI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 12:11:24 -0000

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

Greetings Gentlefolk,

During IETF 105 in Montreal it was decided to form an HTTP Design Team.
Since then the team has had some good discussion [1] and made some
progress, which was presented by the team lead Ian Sweet during the QUIC
Interim meeting in Cupertino [2]. To summarise, the design team believe
that draft-kazuho-httpbis-priority is a good starting point for a priority
scheme that offers an alternative to HTTP/2 priorities, that a negotiation
mechanism for selecting the desired priority scheme for use in an HTTP/2 or
HTTP/3 connection is useful, and that reprioritization is useful.

Kazuho and I have released draft-kazuho-httpbis-priority-03. For ease of
reference and review, draft 03 incorporates a negotiation mechanism based
on a design modification to draft-lassey-priority-setting-00 [3] along with
updates based on the design team and community's feedback so far. In future
we may split these facets back out of the document.

The major changes in draft 03 are:

* A motivation section that consolidates several problems statements
presented to the HTTP community [4] [5] [6]
* A fuller negotiation mechanism based on a new SETTINGS_PRIORITIES setting
for HTTP/2 and HTTP/3.
    * Endpoints send an size-bound ordered list of their preferred schemes,
if a compatible scheme is found the server's preference order prevails.
* Fully specify how reprioritization works using a new frame called
PRIORITY_UPDATE for HTTP/2 and HTTP/3.
* Expanded guidance for intermediaries, especially those that coalesce
client connections to an origin.

We would appreciate any comment from the HTTP, or wider, community either
on the lists or directly on the GitHub repository [7].

Thanks again to all the contributors so far.

Lucas

[1] https://groups.google.com/forum/#!forum/http-priorities-design-team
[2]
https://github.com/quicwg/wg-materials/blob/master/interim-19-10/HTTP%20Priorities%20Update.pdf
[3] https://tools.ietf.org/html/draft-lassey-priority-setting-00
[4] https://tools.ietf.org/html/draft-peon-httpbis-h2-priority-one-less-00
[5]
https://h3.edm.uhasselt.be/files/HTTP3_Prioritization_extended_3jul2019.pdf
[6]
https://github.com/Netflix/security-bulletins/blob/master/advisories/third-party/2019-002.md
[7] https://github.com/kazuho/draft-kazuho-httpbis-priority

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: Mon, Nov 4, 2019 at 11:35 PM
Subject: New Version Notification for draft-kazuho-httpbis-priority-03.txt
To: Kazuho Oku <kazuhooku@gmail.com>, Lucas Pardue <
lucaspardue.24.7@gmail.com>



A new version of I-D, draft-kazuho-httpbis-priority-03.txt
has been successfully submitted by Kazuho Oku and posted to the
IETF repository.

Name:           draft-kazuho-httpbis-priority
Revision:       03
Title:          Extensible Prioritization Scheme for HTTP
Document date:  2019-11-05
Group:          Individual Submission
Pages:          19
URL:
https://www.ietf.org/internet-drafts/draft-kazuho-httpbis-priority-03.txt
Status:
https://datatracker.ietf.org/doc/draft-kazuho-httpbis-priority/
Htmlized:       https://tools.ietf.org/html/draft-kazuho-httpbis-priority-03
Htmlized:
https://datatracker.ietf.org/doc/html/draft-kazuho-httpbis-priority
Diff:
https://www.ietf.org/rfcdiff?url2=draft-kazuho-httpbis-priority-03

Abstract:
   This document describes a scheme for prioritizing HTTP responses.
   This scheme expresses the priority of each HTTP response using
   absolute values, rather than as a relative relationship between a
   group of HTTP responses.

   This document defines the Priority header field for communicating the
   initial priority in an HTTP version-independent manner, as well as
   HTTP/2 and HTTP/3 frames for reprioritizing the responses.  These
   share a common format structure that is designed to provide future
   extensibility.




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.

The IETF Secretariat

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

<div dir=3D"ltr"><div>Greetings Gentlefolk,</div><div><br></div><div>During=
 IETF 105 in Montreal it was decided to form an HTTP Design Team. Since the=
n the team has had some good discussion [1] and made some progress, which w=
as presented by the team lead Ian Sweet during the QUIC Interim meeting in =
Cupertino [2]. To summarise, the design team believe that draft-kazuho-http=
bis-priority is a good starting point for a priority scheme that offers an =
alternative to HTTP/2 priorities, that a negotiation mechanism for selectin=
g the desired priority scheme for use in an HTTP/2 or HTTP/3 connection is =
useful, and that reprioritization is useful.<br></div><div><br></div><div>K=
azuho and I have released draft-kazuho-httpbis-priority-03. For ease of ref=
erence and review, draft 03 incorporates a negotiation mechanism based on a=
 design modification to draft-lassey-priority-setting-00 [3] along with upd=
ates based on the design team and community&#39;s feedback so far. In futur=
e we may split these facets back out of the document.<br></div><div><br></d=
iv><div>The major changes in draft 03 are:</div><div><br></div><div>* A mot=
ivation section that consolidates several problems statements presented to =
the HTTP community [4] [5] [6]</div><div>* A fuller negotiation mechanism b=
ased on a new <span class=3D"gmail-insert">SETTINGS_PRIORITIES</span> setti=
ng for HTTP/2 and HTTP/3. <br></div><div>=C2=A0=C2=A0=C2=A0 * Endpoints sen=
d an size-bound ordered list of their preferred schemes, if a compatible sc=
heme is found the server&#39;s preference order prevails.</div><div>* Fully=
 specify how reprioritization works using a new frame called PRIORITY_UPDAT=
E for HTTP/2 and HTTP/3.</div><div>* Expanded guidance for intermediaries, =
especially those that coalesce client connections to an origin.<br></div><d=
iv><br></div><div>We would appreciate any comment from the HTTP, or wider, =
community either on the lists or directly on the GitHub repository [7].<br>=
</div><div><br></div><div>Thanks again to all the contributors so far.</div=
><div><br></div><div>Lucas<br></div><div><br></div><div>[1] <a href=3D"http=
s://groups.google.com/forum/#!forum/http-priorities-design-team">https://gr=
oups.google.com/forum/#!forum/http-priorities-design-team</a></div><div>[2]=
 <a href=3D"https://github.com/quicwg/wg-materials/blob/master/interim-19-1=
0/HTTP%20Priorities%20Update.pdf">https://github.com/quicwg/wg-materials/bl=
ob/master/interim-19-10/HTTP%20Priorities%20Update.pdf</a></div><div>[3] <a=
 href=3D"https://tools.ietf.org/html/draft-lassey-priority-setting-00">http=
s://tools.ietf.org/html/draft-lassey-priority-setting-00</a></div><div>[4] =
<a href=3D"https://tools.ietf.org/html/draft-peon-httpbis-h2-priority-one-l=
ess-00">https://tools.ietf.org/html/draft-peon-httpbis-h2-priority-one-less=
-00</a></div><div>[5] <a href=3D"https://h3.edm.uhasselt.be/files/HTTP3_Pri=
oritization_extended_3jul2019.pdf">https://h3.edm.uhasselt.be/files/HTTP3_P=
rioritization_extended_3jul2019.pdf</a></div><div>[6] <a href=3D"https://gi=
thub.com/Netflix/security-bulletins/blob/master/advisories/third-party/2019=
-002.md">https://github.com/Netflix/security-bulletins/blob/master/advisori=
es/third-party/2019-002.md</a></div><div>[7] <a href=3D"https://github.com/=
kazuho/draft-kazuho-httpbis-priority">https://github.com/kazuho/draft-kazuh=
o-httpbis-priority</a></div><div><br><div class=3D"gmail_quote"><div dir=3D=
"ltr" class=3D"gmail_attr">---------- Forwarded message ---------<br>From: =
<span dir=3D"auto">&lt;<a href=3D"mailto:internet-drafts@ietf.org">internet=
-drafts@ietf.org</a>&gt;</span><br>Date: Mon, Nov 4, 2019 at 11:35 PM<br>Su=
bject: New Version Notification for draft-kazuho-httpbis-priority-03.txt<br=
>To: Kazuho Oku &lt;<a href=3D"mailto:kazuhooku@gmail.com">kazuhooku@gmail.=
com</a>&gt;, Lucas Pardue &lt;<a href=3D"mailto:lucaspardue.24.7@gmail.com"=
>lucaspardue.24.7@gmail.com</a>&gt;<br></div><br><br><br>
A new version of I-D, draft-kazuho-httpbis-priority-03.txt<br>
has been successfully submitted by Kazuho Oku and posted to the<br>
IETF repository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-kazuho-httpbis-priority=
<br>
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A003<br>
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Extensible Prioritization Scheme f=
or HTTP<br>
Document date:=C2=A0 2019-11-05<br>
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission<br>
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 19<br>
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.ietf.o=
rg/internet-drafts/draft-kazuho-httpbis-priority-03.txt" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/internet-drafts/draft-kazuho-httpbi=
s-priority-03.txt</a><br>
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.iet=
f.org/doc/draft-kazuho-httpbis-priority/" rel=3D"noreferrer" target=3D"_bla=
nk">https://datatracker.ietf.org/doc/draft-kazuho-httpbis-priority/</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/html/=
draft-kazuho-httpbis-priority-03" rel=3D"noreferrer" target=3D"_blank">http=
s://tools.ietf.org/html/draft-kazuho-httpbis-priority-03</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.ietf.org=
/doc/html/draft-kazuho-httpbis-priority" rel=3D"noreferrer" target=3D"_blan=
k">https://datatracker.ietf.org/doc/html/draft-kazuho-httpbis-priority</a><=
br>
Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.ietf.o=
rg/rfcdiff?url2=3Ddraft-kazuho-httpbis-priority-03" rel=3D"noreferrer" targ=
et=3D"_blank">https://www.ietf.org/rfcdiff?url2=3Ddraft-kazuho-httpbis-prio=
rity-03</a><br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document describes a scheme for prioritizing HTTP respons=
es.<br>
=C2=A0 =C2=A0This scheme expresses the priority of each HTTP response using=
<br>
=C2=A0 =C2=A0absolute values, rather than as a relative relationship betwee=
n a<br>
=C2=A0 =C2=A0group of HTTP responses.<br>
<br>
=C2=A0 =C2=A0This document defines the Priority header field for communicat=
ing the<br>
=C2=A0 =C2=A0initial priority in an HTTP version-independent manner, as wel=
l as<br>
=C2=A0 =C2=A0HTTP/2 and HTTP/3 frames for reprioritizing the responses.=C2=
=A0 These<br>
=C2=A0 =C2=A0share a common format structure that is designed to provide fu=
ture<br>
=C2=A0 =C2=A0extensibility.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
</div></div></div>

--0000000000009260610596985454--


From nobody Tue Nov  5 04:18:56 2019
Return-Path: <mirja.kuehlewind@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 908F01208A9; Tue,  5 Nov 2019 04:18:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.001
X-Spam-Level: 
X-Spam-Status: No, score=-2.001 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_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=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 t7aU1BrtyrKK; Tue,  5 Nov 2019 04:18:53 -0800 (PST)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-eopbgr140042.outbound.protection.outlook.com [40.107.14.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 008901200B1; Tue,  5 Nov 2019 04:18:52 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=W2RVdREqnSe2nCyFUGnPVh08/n1DaHjE422kduFQwPvQzbZw3OO4QE/IRWZ8IOmqvvsiYImxVx3+mFeWTJu+OXRlQ8UXs9RzUCgso6wIRPabHjmIoNjHjp2lM4pEuUA8ecxTfPUv4Af/kX8D82skf7pZz+HMmSbXwm+Uuk0QJIQMmZMkkZlAmKTTiJiJKvSAJnGf3ZCs23TQE8V51OdFYqRmW35qhbrXEkko61ZuggiAj0Nla2arIrI9GGZijpYkAXsqstPHyRfpNIgfotsV3Qu+/GPnThulBsQddT9VZG/5OpUNPKibajCs6Xp4avK7VPITm2liC7jLPMfWkq0g7w==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SguyfFya5ZJ9v99dERH3l+AG+qIOt5dw1X3Wg168PWk=; b=WeUoCppWft4Q+Rf5xWgo9SsY/7QPRIpenoC/yyVO2IdifF1nGuU5JL1f8f3PMjJjWcZgrowNjJPjYhCBgO1u2i0Yaxvb7Vb/0o1YZZy3YKSBUevnTB4pFWORvNi4GNuvg3FffFIpx4wtTsaBr0T98vVNZzG0UWOHZCvWAuHFom2w/eENsGMEIRrFDXcvAGHKjBriZcwn6taM9GjbxmLxiF31/vUarsIKZTbKFyzuWqJu5ru/5OTbSNx8vpoXD9bhaEn9SjOXYxbxJXWyKrNyEimqQ6XbqWf6yFB0ZYl6eTr5Pnl+Bz/UPmnfCH+uCja5Kwqqcj4spnYYfNkKhbSr2w==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=ericsson.com; dmarc=pass action=none header.from=ericsson.com; dkim=pass header.d=ericsson.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ericsson.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=SguyfFya5ZJ9v99dERH3l+AG+qIOt5dw1X3Wg168PWk=; b=Up1o0W2/u4f1W7AnyS1pzAcq4Fkc8yoSle5xNalexzqNJQnaq6j+bg5IoY7go/uSePBdU1jSzChHN23LS96pW4I75mZZp3Lx20qCDDMK7b6lHx+09bilj2Jt1JVQFMDmZvrCO/z3OYtu0kqtk6+8cpsjOS+vSZxUKpPvLdlzyMg=
Received: from AM0PR07MB4691.eurprd07.prod.outlook.com (52.135.149.158) by AM0PR07MB6145.eurprd07.prod.outlook.com (20.178.112.97) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2430.13; Tue, 5 Nov 2019 12:18:50 +0000
Received: from AM0PR07MB4691.eurprd07.prod.outlook.com ([fe80::4189:4ef8:bfc1:ec58]) by AM0PR07MB4691.eurprd07.prod.outlook.com ([fe80::4189:4ef8:bfc1:ec58%7]) with mapi id 15.20.2430.014; Tue, 5 Nov 2019 12:18:50 +0000
From: Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>
To: "masque@ietf.org" <masque@ietf.org>, "quic@ietf.org" <quic@ietf.org>
Subject: FW: New Version Notification for draft-kuehlewind-quic-substrate-02.txt
Thread-Topic: New Version Notification for draft-kuehlewind-quic-substrate-02.txt
Thread-Index: AQHVk1j+yHToOYpe6EC/AmS+KSdRgKd8kG0A
Date: Tue, 5 Nov 2019 12:18:50 +0000
Message-ID: <33E53266-FAB6-4D18-80E6-794B35D9D7ED@ericsson.com>
References: <157290383959.13855.4395621889875726313.idtracker@ietfa.amsl.com>
In-Reply-To: <157290383959.13855.4395621889875726313.idtracker@ietfa.amsl.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: spf=none (sender IP is ) smtp.mailfrom=mirja.kuehlewind@ericsson.com; 
x-originating-ip: [2001:16b8:2c01:4700:a964:b2bd:eb9c:5dad]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: c425780a-97d7-4d09-44fe-08d761ea5109
x-ms-traffictypediagnostic: AM0PR07MB6145:
x-ms-exchange-purlcount: 5
x-microsoft-antispam-prvs: <AM0PR07MB6145DFAFCF4E119BD142542CF47E0@AM0PR07MB6145.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0212BDE3BE
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(4636009)(346002)(136003)(366004)(376002)(39860400002)(396003)(189003)(53754006)(199004)(86362001)(15650500001)(6306002)(2906002)(2473003)(229853002)(6512007)(66574012)(6116002)(99286004)(36756003)(110136005)(14454004)(66946007)(2501003)(316002)(81156014)(76116006)(11346002)(91956017)(446003)(486006)(44832011)(5660300002)(76176011)(305945005)(46003)(33656002)(7736002)(966005)(2616005)(186003)(66446008)(66556008)(450100002)(64756008)(478600001)(81166006)(71200400001)(6436002)(6486002)(71190400001)(8936002)(8676002)(256004)(14444005)(476003)(6506007)(25786009)(66476007)(102836004); DIR:OUT; SFP:1101; SCL:1; SRVR:AM0PR07MB6145; H:AM0PR07MB4691.eurprd07.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: ericsson.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: k78DT0VQG+AhfHJHO9Any5oZ42L3izy6CBVOiwWc7ftg6Qug1YH3PYM49jWWIowgiZDMx49saeAQUb/RpN3vZrIZ/PoYlwmIWGXB4rVI9eDilJGuHldut3q9n2yPiuCJ5fjZ0X11LDK7hT00+hKflZ169yVpnOnAxydHaej3a3QqLGm/9QCzVb0LB6Tk1GduxDPCKbUs6wnUWLh96aRWEJnDnrUq8ss4bJPfhoY+8KxWU4su24tFG0MirMzds0VA3FDp22BZUawdkNPmJXkkgH56/iZ0r0yrm8J7bg+ugoAPJtVXOZ1QABVuQt2dvES/VcO82bC3V7GFbc3ueonwWHEurGUQng+AGtnTf2khe0zwtGuV6sk7+uRyWW3GkqoclavnJzuXvDh7fv4H1FdtdjRP1jXvl/Xv7mnSjU6W5RzvDPWcoUqaXTlYD5BXYxS19ROkuOec1O2WDkD0/HuDN7/5Wq9sT+VsvsXUKkriu4E=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <2D75F1EFF9B41543B386902733E668E9@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-Network-Message-Id: c425780a-97d7-4d09-44fe-08d761ea5109
X-MS-Exchange-CrossTenant-originalarrivaltime: 05 Nov 2019 12:18:50.4408 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 92e84ceb-fbfd-47ab-be52-080c6b87953f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ORV5F1v1QOk5gPRqjULYUxUDwzmvDwAn+hkiUUOOnNLLQS44Osg5ym+c/AkKV2jctJiMffnq0L7bZWyVuyahXuR1oH/Xpfafz5mDmVKpXK8=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB6145
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/rym5Q3qXE7VEUc6CskJcpB1fAfg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 12:18:56 -0000

SGkgYWxsLA0KDQp3ZSBoYXZlIGFsc28gdXBkYXRlZCB0aGUgdXNlIGNhc2VzIGZvciBRVUlDIGFz
IGEgc3Vic3RyYXRlIGRvY3VtZW50IGFzIFRvbW15IGNvbnRyaWJ1dGVkIHNvbWUgdGV4dCBvbiBj
b25zaWRlcmF0aW9ucyBmb3IgbXVsdGlwbGUgZW5jcnlwdGlvbi4gVGhhbmtzIFRvbW15IQ0KDQpN
aXJqYQ0KDQoNCu+7v09uIDA0LjExLjE5LCAyMjo0NCwgImludGVybmV0LWRyYWZ0c0BpZXRmLm9y
ZyIgPGludGVybmV0LWRyYWZ0c0BpZXRmLm9yZz4gd3JvdGU6DQoNCiAgICANCiAgICBBIG5ldyB2
ZXJzaW9uIG9mIEktRCwgZHJhZnQta3VlaGxld2luZC1xdWljLXN1YnN0cmF0ZS0wMi50eHQNCiAg
ICBoYXMgYmVlbiBzdWNjZXNzZnVsbHkgc3VibWl0dGVkIGJ5IE1pcmphIEt1ZWhsZXdpbmQgYW5k
IHBvc3RlZCB0byB0aGUNCiAgICBJRVRGIHJlcG9zaXRvcnkuDQogICAgDQogICAgTmFtZToJCWRy
YWZ0LWt1ZWhsZXdpbmQtcXVpYy1zdWJzdHJhdGUNCiAgICBSZXZpc2lvbjoJMDINCiAgICBUaXRs
ZToJCVVzZSBDYXNlcyBhbmQgUmVxdWlyZW1lbnRzIGZvciBRVUlDIGFzIGEgU3Vic3RyYXRlDQog
ICAgRG9jdW1lbnQgZGF0ZToJMjAxOS0xMS0wNA0KICAgIEdyb3VwOgkJSW5kaXZpZHVhbCBTdWJt
aXNzaW9uDQogICAgUGFnZXM6CQkxMA0KICAgIFVSTDogICAgICAgICAgICBodHRwczovL3d3dy5p
ZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQta3VlaGxld2luZC1xdWljLXN1YnN0cmF0ZS0w
Mi50eHQNCiAgICBTdGF0dXM6ICAgICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9k
b2MvZHJhZnQta3VlaGxld2luZC1xdWljLXN1YnN0cmF0ZS8NCiAgICBIdG1saXplZDogICAgICAg
aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWt1ZWhsZXdpbmQtcXVpYy1zdWJzdHJh
dGUtMDINCiAgICBIdG1saXplZDogICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9k
b2MvaHRtbC9kcmFmdC1rdWVobGV3aW5kLXF1aWMtc3Vic3RyYXRlDQogICAgRGlmZjogICAgICAg
ICAgIGh0dHBzOi8vd3d3LmlldGYub3JnL3JmY2RpZmY/dXJsMj1kcmFmdC1rdWVobGV3aW5kLXF1
aWMtc3Vic3RyYXRlLTAyDQogICAgDQogICAgQWJzdHJhY3Q6DQogICAgICAgVENQIGlzIG9mdGVu
IHVzZWQgYXMgYSBwcm94eWluZyBvciB0dW5uZWxpbmcgcHJvdG9jb2wuICBRVUlDIGlzIGENCiAg
ICAgICBuZXcsIGVtZXJnaW5nIHRyYW5zcG9ydCBwcm90b2NvbCBhbmQgdGhlcmUgaXMgYSBzaW1p
bGFyIGV4cGVjdGF0aW9uDQogICAgICAgdGhhdCBpdCB0b28gd2lsbCBiZSB1c2VkIGFzIGEgc3Vi
c3RyYXRlIG9uY2UgaXQgaXMgd2lkZWx5IGRlcGxveWVkLg0KICAgICAgIFVzaW5nIFFVSUMgaW5z
dGVhZCBvZiBUQ1AgaW4gZXhpc3Rpbmcgc2NlbmFyaW9zIHdpbGwgYWxsb3cgcHJveHlpbmcNCiAg
ICAgICBhbmQgdHVubmVsaW5nIHNlcnZpY2VzIHRvIG1haW50YWluIHRoZSBiZW5lZml0cyBvZiBR
VUlDIG5hdGl2ZWx5LA0KICAgICAgIHdpdGhvdXQgZGVncmFkaW5nIHRoZSBwZXJmb3JtYW5jZSBh
bmQgc2VjdXJpdHkgY2hhcmFjdGVyaXN0aWNzLiAgUVVJQw0KICAgICAgIGFsc28gb3BlbnMgdXAg
bmV3IG9wcG9ydHVuaXRpZXMgZm9yIHRoZXNlIHNlcnZpY2VzIHRvIGhhdmUgbG93ZXINCiAgICAg
ICBsYXRlbmN5IGFuZCBiZXR0ZXIgbXVsdGlzdHJlYW1pbmcgc3VwcG9ydC4gIFRoaXMgZG9jdW1l
bnQgc3VtbWFyaXplcw0KICAgICAgIGN1cnJlbnQgYW5kIGZ1dHVyZSB1c2FnZSBzY2VuYXJpb3Mg
dG8gZGVyaXZlIHJlcXVpcmVtZW50cyBmb3IgUVVJQw0KICAgICAgIGFuZCB0byBwcm92aWRlIGFk
ZGl0aW9uYWwgcHJvdG9jb2wgY29uc2lkZXJhdGlvbnMuDQogICAgDQogICAgICAgICAgICAgICAg
ICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAgICAg
ICAgICAgICAgICAgIA0KICAgIA0KICAgIA0KICAgIFBsZWFzZSBub3RlIHRoYXQgaXQgbWF5IHRh
a2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1Ym1pc3Npb24NCiAgICB1
bnRpbCB0aGUgaHRtbGl6ZWQgdmVyc2lvbiBhbmQgZGlmZiBhcmUgYXZhaWxhYmxlIGF0IHRvb2xz
LmlldGYub3JnLg0KICAgIA0KICAgIFRoZSBJRVRGIFNlY3JldGFyaWF0DQogICAgDQogICAgDQoN
Cg==


From nobody Tue Nov  5 07:44:50 2019
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 6BC4B120108 for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 07:44:48 -0800 (PST)
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, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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 SnwIcRxSHTWz for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 07:44:46 -0800 (PST)
Received: from mx0b-00190b01.pphosted.com (mx0b-00190b01.pphosted.com [67.231.157.127]) (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 ED5A11200FF for <quic@ietf.org>; Tue,  5 Nov 2019 07:44:45 -0800 (PST)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id xA5FMcVa027389; Tue, 5 Nov 2019 15:42:41 GMT
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=mDUuqSk1zwzcAyvTsSdwIw0oneLpUwzpo9WONr6FzF4=; b=BuUsLkOl7KmxwgWjuG9mF6N1fMSCPpwNSrMoB15CrMAVHjLdg4J38qgK3+4SSueqe1IV iSBkefaljXo6MXeIMMulaD7zipJbNKFGVIYJIdp5V8pDSL1LH8oK4tRm087rF/e5Sap3 Iu6+6aejh++DwW9rudnWt1hVvGpIDbJCZyz+9wgNRLbEHHcG8+4Ud5G5Jp4v7CALgoGv axRmT6qBzqgBTuTnw38UMj9kaK7Ly3y7AN7LQwYGoGh1DCq7GCKaWXX6wQjhk0TsPGib i+eLxNLXu1JG7nvaKk0jzN1qy9fZVCEdJF43IzsKOnh8WLhUBf///cNdOGtGRgxdDgZ2 FA== 
Received: from prod-mail-ppoint3 (prod-mail-ppoint3.akamai.com [96.6.114.86] (may be forged)) by m0050102.ppops.net-00190b01. with ESMTP id 2w0yrmev6h-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 05 Nov 2019 15:42:41 +0000
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.27/8.16.0.27) with SMTP id xA5FWZWm017951; Tue, 5 Nov 2019 10:42:40 -0500
Received: from email.msg.corp.akamai.com ([172.27.165.118]) by prod-mail-ppoint3.akamai.com with ESMTP id 2w154y60x5-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 05 Nov 2019 10:42:33 -0500
Received: from USTX2EX-DAG1MB5.msg.corp.akamai.com (172.27.165.123) by ustx2ex-dag1mb4.msg.corp.akamai.com (172.27.165.122) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 5 Nov 2019 09:41:59 -0600
Received: from USTX2EX-DAG1MB5.msg.corp.akamai.com ([172.27.165.123]) by ustx2ex-dag1mb5.msg.corp.akamai.com ([172.27.165.123]) with mapi id 15.00.1473.005; Tue, 5 Nov 2019 09:41:58 -0600
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: =?utf-8?B?TWlra2VsIEZhaG7DuGUgSsO4cmdlbnNlbg==?= <mikkelfj@gmail.com>, Jana Iyengar <jri.ietf@gmail.com>, Martin Thomson <mt@lowentropy.net>
CC: QUIC WG <quic@ietf.org>
Subject: RE: Version Ossification: Intended Scope for QUICv1
Thread-Topic: Version Ossification: Intended Scope for QUICv1
Thread-Index: AQHVkC//YCVRiFXs+UeDN5d6EnIKa6d1mTQAgAE4voCAA5JWgIABzxmAgAAJxACAAAawAIAAbCSAgAANYnA=
Date: Tue, 5 Nov 2019 15:41:57 +0000
Message-ID: <19e740a5aef449dfa58bbac56edef014@ustx2ex-dag1mb5.msg.corp.akamai.com>
References: <CAPDSy+6E79OySoOLbJ8eWp0J-+3yeB5iGvj6sW19bEDn_V7-NA@mail.gmail.com> <CANatvzzaWFgrvnaV=VeZRAVvxqSBeMSZT5aMUu7-Vh9raeZJFw@mail.gmail.com> <BN6PR2201MB1700184D81061E2CBFD77BFBDA620@BN6PR2201MB1700.namprd22.prod.outlook.com> <e24ecddd-139d-4669-be96-b3de57557c4e@www.fastmail.com> <CACpbDcci5R7Szti7LbpH7GEm9jT2fP_Jz99Mx-bBcSe8RT43cQ@mail.gmail.com> <d5c3b4d3-2202-41d7-9ebe-3541ceec1b78@www.fastmail.com> <CACpbDcetR7e01oDZ7_hihB2mpbKbOuydp6mHd474bduaMA5rbA@mail.gmail.com> <CAN1APdfGjt=rzU+iP+iDQvpPpCu5LCq94eUxxei7qWHZKsbNJA@mail.gmail.com>
In-Reply-To: <CAN1APdfGjt=rzU+iP+iDQvpPpCu5LCq94eUxxei7qWHZKsbNJA@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.238]
Content-Type: multipart/alternative; boundary="_000_19e740a5aef449dfa58bbac56edef014ustx2exdag1mb5msgcorpak_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-11-05_05:, , signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1908290000 definitions=main-1911050127
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,1.0.8 definitions=2019-11-05_05:2019-11-05,2019-11-05 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 bulkscore=0 priorityscore=1501 suspectscore=0 phishscore=0 clxscore=1011 spamscore=0 mlxlogscore=999 adultscore=0 malwarescore=0 lowpriorityscore=0 mlxscore=0 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1908290000 definitions=main-1911050127
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/UBVmkGc6rHBpScmFP-20shF-lX8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 15:44:48 -0000

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

SSB0aGluayB0aGUgaW50ZW50IHdhcyBjbGVhciDigJMgc2luY2UgdGhlIGtleXPigJkgcHVycG9z
ZSBpcyBub3Qgc2VjcmVjeSBidXQgb2NjYXNpb25hbCBwZXJ0dXJiYXRpb24gb2YgYml0cywgaXQg
c2hvdWxkIGJlIGVhc3kgdG8gbWFrZSDigJxmb3JnZXR0aW5n4oCdIGEga2V5IGltcG9zc2libGUu
ICBBbGwgZGVwbG95bWVudHMgaGF2ZSBzb21lIHNvcnQgb2YgY3JpdGljYWwgY29uZmlndXJhdGlv
biBhbmQgaGVuY2UgY29uZmlndXJhdGlvbiBtYW5hZ2VtZW50IHN5c3RlbS4gIENvbW1pdHRpbmcg
c3VjaCBrZXlzIHRvIHRoYXQgY29uZmlndXJhdGlvbiBtYW5hZ2VtZW50IHN5c3RlbSBzaG91bGQg
ZG8gdGhlIHRyaWNrIG9mIHRoZSBrZXlzIGJlY29taW5nIHVuZm9yZ2V0dGFibGUuIDopDQoNCg0K
ICAqICAgSWdvcg0KDQpGcm9tOiBNaWtrZWwgRmFobsO4ZSBKw7hyZ2Vuc2VuIDxtaWtrZWxmakBn
bWFpbC5jb20+DQpTZW50OiBUdWVzZGF5LCBOb3ZlbWJlciA1LCAyMDE5IDM6NDkgQU0NClRvOiBK
YW5hIEl5ZW5nYXIgPGpyaS5pZXRmQGdtYWlsLmNvbT47IE1hcnRpbiBUaG9tc29uIDxtdEBsb3dl
bnRyb3B5Lm5ldD4NCkNjOiBRVUlDIFdHIDxxdWljQGlldGYub3JnPg0KU3ViamVjdDogUmU6IFZl
cnNpb24gT3NzaWZpY2F0aW9uOiBJbnRlbmRlZCBTY29wZSBmb3IgUVVJQ3YxDQoNCkkgcmVhbGx5
IGRvbuKAmXQgdGhpbmsgdGhlIGRyYWZ0IHNob3VsZCByZWNvbW1lbmQga2V5IGRlcGxveW1lbnRz
IGxpa2UgdGhhdC4NCkl0IG1heSBiZSB0aGF0IGJha2VkIGludG8gdGhlIGJpbmFyeSB3b3Jrcywg
YnV0IHNvdW5kIGRlcGxveW1lbnQgYWR2aXNlIGlzIHRvIHVzZSBhbiBlbnZpcm9ubWVudCB2YXJp
YWJsZSBmb3Igc3VjaCB0aGluZ3MsIHRoZW4geW91IGNhbiBiYWtlIGl0IGludG8geW91IGRlcGxv
eW1lbnQgc2NyaXB0IGlmIHlvdSB3aXNoLiBQb2ludCBiZWluZywgdGhlIFdHIHNob3VsZCBub3Qg
YmUgdG9vIHNwZWNpZmljIGhlcmUuDQoNCg0KDQpPbiA1IE5vdmVtYmVyIDIwMTkgYXQgMDMuMjIu
MzIsIEphbmEgSXllbmdhciAoanJpLmlldGZAZ21haWwuY29tPG1haWx0bzpqcmkuaWV0ZkBnbWFp
bC5jb20+KSB3cm90ZToNCk9uIE1vbiwgTm92IDQsIDIwMTkgYXQgNTo1OCBQTSBNYXJ0aW4gVGhv
bXNvbiA8bXRAbG93ZW50cm9weS5uZXQ8bWFpbHRvOm10QGxvd2VudHJvcHkubmV0Pj4gd3JvdGU6
DQpPbiBUdWUsIE5vdiA1LCAyMDE5LCBhdCAxMjoyMywgSmFuYSBJeWVuZ2FyIHdyb3RlOg0KPiBP
biBTdW4sIE5vdiAzLCAyMDE5IGF0IDE6NDYgUE0gTWFydGluIFRob21zb24gPG10QGxvd2VudHJv
cHkubmV0PG1haWx0bzptdEBsb3dlbnRyb3B5Lm5ldD4+IHdyb3RlOg0KPiA+IFdoeSBjYW4ndCBz
ZXJ2ZXJzIGp1c3QgYmFrZSB0aGUgImtleXMiIGludG8gYmluYXJpZXM/IEkgbWVhbiwgdGhhdCdz
IG5vdCBzb21ldGhpbmcgdGhhdCBpcyBsaWtlbHkgdG8gZ2V0IGxvc3QuIEFuZCBpdCBpc24ndCBy
ZWFsbHkgdGhlIGNhc2UgdGhhdCBrZXlzIG5lZWQgdG8gYmUgc2VjcmV0LCB0aGV5IGp1c3QgaGF2
ZSB0byBjaGFuZ2Ugb2Z0ZW4gZW5vdWdoIHRvIGZydXN0cmF0ZSBhdHRlbXB0cyB0byBmaXhhdGUg
b24gdGhlbS4NCj4NCj4gVGhpcyBpcyBhIGZpbmUgaWRlYSwgYnV0IGhvdyBkb2VzIGl0IGNoYW5n
ZSBhbnl0aGluZz8gV2hlbmV2ZXIgdGhlIGtleXMNCj4gYXJlIHJvdGF0ZWQgYXQgdGhlIHNlcnZl
ciwgeW91IHdvdWxkIHN0aWxsIGhhdmUgdG8gZGVhbCB3aXRoIG9sZA0KPiB2ZXJzaW9ucyBhcHBl
YXJpbmcgYXQgdGhlIHNlcnZlciwgbm8/DQoNCkknbSBhc3N1bWluZyB0aGF0IHlvdSBjYW4gYSkg
bGltaXQgdGhlIHRpbWUgb3ZlciB3aGljaCBhIHRva2VuIGNvdWxkIGFwcGVhciwgYikgdXNlIGEg
a2V5IGlkZW50aWZpZXIgc28gdGhhdCBrZXlzIGNhbiBiZSBjaGFuZ2VkLCBhbmQgYykga2VlcCBv
bGQga2V5cyBpbiB0aGUgY29kZSB1bnRpbCB0aGUgYXNzb2NpYXRlZCB0b2tlbnMgYXJlIGFsbCBl
eHBpcmVkLg0KDQpSaWdodCwgdGhhdCBtYWtlcyBzZW5zZS4gSSB0aGluayB5b3VyIHBvaW50IGFi
b3V0IG5vdCByZXF1aXJpbmcgdGhpcyB0byBiZSByb3RhdGVkIGZyZXF1ZW50bHkgaXMgYSBnb29k
IG9uZSwgYW5kIHdlIG1pZ2h0IGV2ZW4gd2FudCB0byBzdWdnZXN0IHlvdXIgaWRlYSBvZiBiYWtp
bmcgdGhlIGtleSBpbnRvIHRoZSBiaW5hcnkuDQo=

--_000_19e740a5aef449dfa58bbac56edef014ustx2exdag1mb5msgcorpak_
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
aW5lO30NCnAubXNvbm9ybWFsMCwgbGkubXNvbm9ybWFsMCwgZGl2Lm1zb25vcm1hbDANCgl7bXNv
LXN0eWxlLW5hbWU6bXNvbm9ybWFsOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdp
bi1yaWdodDowaW47DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6
MGluOw0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2Vy
aWY7fQ0KcC5haXJtYWlsb24sIGxpLmFpcm1haWxvbiwgZGl2LmFpcm1haWxvbg0KCXttc28tc3R5
bGUtbmFtZTphaXJtYWlsX29uOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1y
aWdodDowaW47DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGlu
Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7
fQ0Kc3Bhbi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtcmVwbHk7DQoJ
Zm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQou
TXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglmb250LXNpemU6
MTAuMHB0O30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJn
aW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldv
cmRTZWN0aW9uMTt9DQovKiBMaXN0IERlZmluaXRpb25zICovDQpAbGlzdCBsMA0KCXttc28tbGlz
dC1pZDo1Mjc5MTI1MDc7DQoJbXNvLWxpc3QtdHlwZTpoeWJyaWQ7DQoJbXNvLWxpc3QtdGVtcGxh
dGUtaWRzOjIwODUyNjIyNjIgLTEyNTg4ODcxNTAgNjc2OTg2OTEgNjc2OTg2OTMgNjc2OTg2ODkg
Njc2OTg2OTEgNjc2OTg2OTMgNjc2OTg2ODkgNjc2OTg2OTEgNjc2OTg2OTM7fQ0KQGxpc3QgbDA6
bGV2ZWwxDQoJe21zby1sZXZlbC1zdGFydC1hdDowOw0KCW1zby1sZXZlbC1udW1iZXItZm9ybWF0
OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDotOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0K
CW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJ
Zm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJbXNvLWZhcmVhc3QtZm9udC1mYW1p
bHk6Q2FsaWJyaTt9DQpAbGlzdCBsMDpsZXZlbDINCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6
YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJ
bXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglm
b250LWZhbWlseToiQ291cmllciBOZXciO30NCkBsaXN0IGwwOmxldmVsMw0KCXttc28tbGV2ZWwt
bnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10
YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWlu
ZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6V2luZ2RpbmdzO30NCkBsaXN0IGwwOmxldmVsNA0K
CXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0K
CW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVm
dDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGww
OmxldmVsNQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRl
eHQ6bzsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0
aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5l
dyI7fQ0KQGxpc3QgbDA6bGV2ZWw2DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsN
Cgltc28tbGV2ZWwtdGV4dDrvgqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxl
dmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZh
bWlseTpXaW5nZGluZ3M7fQ0KQGxpc3QgbDA6bGV2ZWw3DQoJe21zby1sZXZlbC1udW1iZXItZm9y
bWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5v
bmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVp
bjsNCglmb250LWZhbWlseTpTeW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWw4DQoJe21zby1sZXZlbC1u
dW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWIt
c3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVu
dDotLjI1aW47DQoJZm9udC1mYW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMDpsZXZlbDkN
Cgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsN
Cgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxl
ZnQ7DQoJdGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpvbA0K
CXttYXJnaW4tYm90dG9tOjBpbjt9DQp1bA0KCXttYXJnaW4tYm90dG9tOjBpbjt9DQotLT48L3N0
eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRp
dCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5
XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVk
aXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hl
YWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2
IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSB0aGluayB0aGUg
aW50ZW50IHdhcyBjbGVhciDigJMgc2luY2UgdGhlIGtleXPigJkgcHVycG9zZSBpcyBub3Qgc2Vj
cmVjeSBidXQgb2NjYXNpb25hbCBwZXJ0dXJiYXRpb24gb2YgYml0cywgaXQgc2hvdWxkIGJlIGVh
c3kgdG8gbWFrZSDigJxmb3JnZXR0aW5n4oCdIGEga2V5IGltcG9zc2libGUuJm5ic3A7IEFsbCBk
ZXBsb3ltZW50cyBoYXZlIHNvbWUgc29ydCBvZiBjcml0aWNhbCBjb25maWd1cmF0aW9uIGFuZCBo
ZW5jZSBjb25maWd1cmF0aW9uDQogbWFuYWdlbWVudCBzeXN0ZW0uJm5ic3A7IENvbW1pdHRpbmcg
c3VjaCBrZXlzIHRvIHRoYXQgY29uZmlndXJhdGlvbiBtYW5hZ2VtZW50IHN5c3RlbSBzaG91bGQg
ZG8gdGhlIHRyaWNrIG9mIHRoZSBrZXlzIGJlY29taW5nIHVuZm9yZ2V0dGFibGUuIDopPG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjx1
bCBzdHlsZT0ibWFyZ2luLXRvcDowaW4iIHR5cGU9ImRpc2MiPg0KPGxpIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbGlzdDpsMCBsZXZlbDEgbGZvMSI+SWdvcjxvOnA+PC9vOnA+PC9saT48
L3VsPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2IHN0
eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCBibHVlIDEuNXB0O3BhZGRpbmc6MGlu
IDBpbiAwaW4gNC4wcHQiPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10
b3A6c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxiPkZyb206PC9iPiBNaWtrZWwgRmFobsO4ZSBKw7hyZ2Vuc2VuICZs
dDttaWtrZWxmakBnbWFpbC5jb20mZ3Q7IDxicj4NCjxiPlNlbnQ6PC9iPiBUdWVzZGF5LCBOb3Zl
bWJlciA1LCAyMDE5IDM6NDkgQU08YnI+DQo8Yj5Ubzo8L2I+IEphbmEgSXllbmdhciAmbHQ7anJp
LmlldGZAZ21haWwuY29tJmd0OzsgTWFydGluIFRob21zb24gJmx0O210QGxvd2VudHJvcHkubmV0
Jmd0Ozxicj4NCjxiPkNjOjwvYj4gUVVJQyBXRyAmbHQ7cXVpY0BpZXRmLm9yZyZndDs8YnI+DQo8
Yj5TdWJqZWN0OjwvYj4gUmU6IFZlcnNpb24gT3NzaWZpY2F0aW9uOiBJbnRlbmRlZCBTY29wZSBm
b3IgUVVJQ3YxPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2IGlkPSJibG9vcF9jdXN0b21mb250Ij4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0O2ZvbnQt
ZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmIj5JIHJlYWxseSBkb27igJl0
IHRoaW5rIHRoZSBkcmFmdCBzaG91bGQgcmVjb21tZW5kIGtleSBkZXBsb3ltZW50cyBsaWtlIHRo
YXQuPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2IGlkPSJibG9vcF9jdXN0b21m
b250Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAuMHB0
O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmIj5JdCBtYXkgYmUg
dGhhdCBiYWtlZCBpbnRvIHRoZSBiaW5hcnkgd29ya3MsIGJ1dCBzb3VuZCBkZXBsb3ltZW50IGFk
dmlzZSBpcyB0byB1c2UgYW4gZW52aXJvbm1lbnQgdmFyaWFibGUgZm9yIHN1Y2ggdGhpbmdzLCB0
aGVuIHlvdSBjYW4gYmFrZSBpdCBpbnRvIHlvdSBkZXBsb3ltZW50IHNjcmlwdA0KIGlmIHlvdSB3
aXNoLiBQb2ludCBiZWluZywgdGhlIFdHIHNob3VsZCBub3QgYmUgdG9vIHNwZWNpZmljIGhlcmUu
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8ZGl2IGlkPSJibG9vcF9zaWduXzE1NzI5
NDM1NjcyODA1ODExMjAiPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJmb250LXNpemU6MTAuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5z
LXNlcmlmIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJhaXJtYWlsb24iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTAu
MHB0O2ZvbnQtZmFtaWx5OiZxdW90O0hlbHZldGljYSZxdW90OyxzYW5zLXNlcmlmIj5PbiA1IE5v
dmVtYmVyIDIwMTkgYXQgMDMuMjIuMzIsIEphbmEgSXllbmdhciAoPGEgaHJlZj0ibWFpbHRvOmpy
aS5pZXRmQGdtYWlsLmNvbSI+anJpLmlldGZAZ21haWwuY29tPC9hPikgd3JvdGU6PG86cD48L286
cD48L3NwYW4+PC9wPg0KPGJsb2NrcXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2lu
LWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7
SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYiPk9uIE1vbiwgTm92IDQsIDIwMTkgYXQgNTo1OCBQ
TSBNYXJ0aW4gVGhvbXNvbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOm10QGxvd2VudHJvcHkubmV0Ij5t
dEBsb3dlbnRyb3B5Lm5ldDwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwv
ZGl2Pg0KPGRpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpz
b2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6
NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtIZWx2ZXRpY2EmcXVvdDssc2Fu
cy1zZXJpZiI+T24gVHVlLCBOb3YgNSwgMjAxOSwgYXQgMTI6MjMsIEphbmEgSXllbmdhciB3cm90
ZTo8YnI+DQomZ3Q7IE9uIFN1biwgTm92IDMsIDIwMTkgYXQgMTo0NiBQTSBNYXJ0aW4gVGhvbXNv
biAmbHQ7PGEgaHJlZj0ibWFpbHRvOm10QGxvd2VudHJvcHkubmV0IiB0YXJnZXQ9Il9ibGFuayI+
bXRAbG93ZW50cm9weS5uZXQ8L2E+Jmd0OyB3cm90ZTo8YnI+DQomZ3Q7ICZndDsgV2h5IGNhbid0
IHNlcnZlcnMganVzdCBiYWtlIHRoZSAmcXVvdDtrZXlzJnF1b3Q7IGludG8gYmluYXJpZXM/IEkg
bWVhbiwgdGhhdCdzIG5vdCBzb21ldGhpbmcgdGhhdCBpcyBsaWtlbHkgdG8gZ2V0IGxvc3QuIEFu
ZCBpdCBpc24ndCByZWFsbHkgdGhlIGNhc2UgdGhhdCBrZXlzIG5lZWQgdG8gYmUgc2VjcmV0LCB0
aGV5IGp1c3QgaGF2ZSB0byBjaGFuZ2Ugb2Z0ZW4gZW5vdWdoIHRvIGZydXN0cmF0ZSBhdHRlbXB0
cyB0byBmaXhhdGUgb24gdGhlbS48YnI+DQomZ3Q7PGJyPg0KJmd0OyBUaGlzIGlzIGEgZmluZSBp
ZGVhLCBidXQgaG93IGRvZXMgaXQgY2hhbmdlIGFueXRoaW5nPyBXaGVuZXZlciB0aGUga2V5czxi
cj4NCiZndDsgYXJlIHJvdGF0ZWQgYXQgdGhlIHNlcnZlciwgeW91IHdvdWxkIHN0aWxsIGhhdmUg
dG8gZGVhbCB3aXRoIG9sZDxicj4NCiZndDsgdmVyc2lvbnMgYXBwZWFyaW5nIGF0IHRoZSBzZXJ2
ZXIsIG5vPzxicj4NCjxicj4NCkknbSBhc3N1bWluZyB0aGF0IHlvdSBjYW4gYSkgbGltaXQgdGhl
IHRpbWUgb3ZlciB3aGljaCBhIHRva2VuIGNvdWxkIGFwcGVhciwgYikgdXNlIGEga2V5IGlkZW50
aWZpZXIgc28gdGhhdCBrZXlzIGNhbiBiZSBjaGFuZ2VkLCBhbmQgYykga2VlcCBvbGQga2V5cyBp
biB0aGUgY29kZSB1bnRpbCB0aGUgYXNzb2NpYXRlZCB0b2tlbnMgYXJlIGFsbCBleHBpcmVkLjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEwLjBwdDtmb250LWZhbWlseTomcXVvdDtI
ZWx2ZXRpY2EmcXVvdDssc2Fucy1zZXJpZiI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6
ZToxMC4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7SGVsdmV0aWNhJnF1b3Q7LHNhbnMtc2VyaWYiPlJp
Z2h0LCB0aGF0IG1ha2VzIHNlbnNlLiBJIHRoaW5rIHlvdXIgcG9pbnQgYWJvdXQgbm90IHJlcXVp
cmluZyB0aGlzIHRvIGJlIHJvdGF0ZWQgZnJlcXVlbnRseSBpcyBhIGdvb2Qgb25lLCBhbmQgd2Ug
bWlnaHQgZXZlbiB3YW50IHRvIHN1Z2dlc3QgeW91ciBpZGVhIG9mIGJha2luZyB0aGUga2V5DQog
aW50byB0aGUgYmluYXJ5LiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_19e740a5aef449dfa58bbac56edef014ustx2exdag1mb5msgcorpak_--


From nobody Tue Nov  5 08:57:56 2019
Return-Path: <sowmini05@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 EB4CB120827 for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 08:57:54 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.297
X-Spam-Level: *
X-Spam-Status: No, score=1.297 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, FSL_HELO_FAKE=3.046, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 Bt2gTdKXE6Ls for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 08:57:54 -0800 (PST)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (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 E63BE120818 for <quic@ietf.org>; Tue,  5 Nov 2019 08:57:53 -0800 (PST)
Received: by mail-qt1-x82e.google.com with SMTP id o49so30249212qta.7 for <quic@ietf.org>; Tue, 05 Nov 2019 08:57:53 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=CMgCNBOfirLfLOhGNLVguy6XW4XoxN27SucLVMy0Cro=; b=iZ5cCQ3Mp/3hNZlzoQD4QBH2UShCZ+pinJrST67BCZB12v+9CEl9TjGN2UKPM5btCM kx1dx8s8UePXzjWYI+BEDln1gFrZIKki9Pl440S4iTl1nZJZz5iA6obOTcetPmkyHFeJ 03/PWdH5cWLk/JaZ/2/GIFWhPoTlBBUe/R1ryvwR/k/TC0YZ7x/A7Wig8IXMCIxuZ6+M FIxCxeioj5WfiUe3i5/3WPYV2B03mJPwt9vjXMffV2aBafbtY1YaMokcFduZamA1pER4 1G/jGUVx1agWj7LHUe9gLMWlSvJQzhgH2NWHsV+br+LygAnfJL9mxWG3yNor/vEql3pU eGIg==
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:references :mime-version:content-disposition:in-reply-to:user-agent; bh=CMgCNBOfirLfLOhGNLVguy6XW4XoxN27SucLVMy0Cro=; b=lBETVDCsNnDBlQoSo3G4hJEdVNsMfuAUqaDCLrbmG3mp0yG1ZDMBbml8bIDAs22IVS SJ9yr4/Hppd4Iitt9FjY0e8BL43U77ZBYbprj0eW2n8D0EP3IYl/WZymcfkut/TO+2vS bu2PtlEoJi36S0vJBKVthdG2ucQau+WLz93iMGKeNLOW69ca4Kd4b+Bk9X4ufQ4K1ypq kQwMiXHDnlxY3c9VT/wP4f78nCagGGHAQhRSVXQh3G45tuxj26A+xNRGwo/VhikPCaEO WRHvTv+Fy74akCuWnZENiaU6NnYowqcY511NWEyZouoWZO3k6QJcl9ck3LI1Zxe6HnZu TADQ==
X-Gm-Message-State: APjAAAVb1qtgoDDutaCNT0TxOpg5zthUFUyYAGFHqDidCFkLTmV/3igM gdBFra1IxPd36MvkfaHCo/A=
X-Google-Smtp-Source: APXvYqys5dEx/D8w5ZAXic+yMQ+tU77Oiamktp8WCZLRzjVgb6GJXuT0pKp03CR+xs9s0NGLBUpzeg==
X-Received: by 2002:ac8:4517:: with SMTP id q23mr19008624qtn.359.1572973073035;  Tue, 05 Nov 2019 08:57:53 -0800 (PST)
Received: from gmail.com (pool-74-104-133-20.bstnma.fios.verizon.net. [74.104.133.20]) by smtp.gmail.com with ESMTPSA id b135sm12423041qkg.91.2019.11.05.08.57.51 (version=TLS1_2 cipher=ECDHE-RSA-CHACHA20-POLY1305 bits=256/256); Tue, 05 Nov 2019 08:57:52 -0800 (PST)
Date: Tue, 5 Nov 2019 11:57:45 -0500
From: Sowmini Varadhan <sowmini05@gmail.com>
To: Martin Duke <martin.h.duke@gmail.com>
Cc: IETF QUIC WG <quic@ietf.org>, Nick Banks <nibanks@microsoft.com>, sovaradh@microsoft.com
Subject: Re: draft-duke-quic-load-balancers-05.txt
Message-ID: <20191105165745.GA136@gmail.com>
References: <20191028194956.GC420@gmail.com> <CAM4esxTJUFD-G-WUOwZQbgSafpMJXHVtYCm1eF=_1g8tDxru=A@mail.gmail.com> <20191029210428.GA119@gmail.com> <CAM4esxSaZdryVtem=iywADpTUhkjuNAyWgCC3-K1k715j3rQ-w@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAM4esxSaZdryVtem=iywADpTUhkjuNAyWgCC3-K1k715j3rQ-w@mail.gmail.com>
User-Agent: Mutt/1.9.4 (2018-02-28)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/r4MM5_WN4aCWV3_zkD0LhwgxTI0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 16:57:55 -0000

On (11/04/19 14:03), Martin Duke wrote:
>    Sowmini,
>    Hopefully draft-06 addresses your concerns.
>    Thanks again for reviewing

Yes, I took a quick look and thanks for addressing the concerns.
I'll read the draft more carefully over the next week or so and 
get back if I have additional questions. 

One nit that either I misunderstood, or went under the radar:

Section 4.3.2 ("Server Actions") is about the encryption side, 
right? So the second paragraph in that section should say
   "The server encrypts the server ID..
instead of "server decrypts.."?

thanks!

--Sowmini

 







From nobody Tue Nov  5 13:37:07 2019
Return-Path: <mcmanus@ducksong.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 E748D1208CB for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 13:37:00 -0800 (PST)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=ducksong.com header.b=EqH13H3v; dkim=pass (2048-bit key) header.d=outbound.mailhop.org header.b=eknpRsy0
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 1wN-e-BhvegX for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 13:36:57 -0800 (PST)
Received: from outbound1b.ore.mailhop.org (outbound1b.ore.mailhop.org [54.200.247.200]) (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 8D2EF120B7E for <quic@ietf.org>; Tue,  5 Nov 2019 13:36:57 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; t=1572989816; cv=none; d=outbound.mailhop.org; s=arc-outbound20181012; b=D45konUt+AWNENOGClB40mekpvr/uSb6pFiE2LMFulHKdn0WiFn0lwpZMR14kz2j78cXvy7RMFy9O GvQL6m0PC+RftLr5WVrZe0+C3G74j5tR4Mle6eRsQGcs8vZJMreLqYLD0IMVwtnVT+ReNOCYbhuE/8 HjiuNBRl78PCf0tZQhwoPsB7L31vs/1nxy8e7ASi6rt6JVfM4FB99uDmIvRDIN1nRbRiZVwv/54M/X ageeIWN3YjHTPqWUnaRJVpKhVfv6IbTnqIRhUH0spaOjU2i47VR18gZlauwFDjkGl6ObOlST5AVZU+ CnoADmC1W/0t72sDXJ1b3W3QTq12l+A==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=arc-outbound20181012; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:dkim-signature:dkim-signature:from; bh=ndFPt93WfX78vT/GYP3fZ1Xedf/ZtJzu7Ke3HXfbU7w=; b=dViCp9B7VJpTWlNaN8o93hfg99YtLwVS1j1+FJBWTJx6Od/cKq8t1e6SUmEtmZMW/cXPPO4TgPAen OXmAu1WJ3P5vPMDxIO3pHEiCnxC2/wH7g+ghInmCjDGN+CYeDMEH1gIu17rRiOm6NO9yWb7LgHf+OX cf9Gjpxahgyc5KBAVBLDzt99Fxxvm3UzNIxYejrNLAtyS+T9kUHLs7W2pFWI2/UXetBlG0L3Epf3iT 10hxqYPXBP0Ds6YYyIpF20bxIblVTRQ1xBedQVD534LfKEELrSd0TN7Zyj7WPy79TraLZdL0wbjVhh oHGjMj4tz0eVEhHg3O5spGjIth5gzlw==
ARC-Authentication-Results: i=1; outbound3.ore.mailhop.org; spf=pass smtp.mailfrom=ducksong.com smtp.remote-ip=209.85.210.46; dmarc=none header.from=ducksong.com; arc=none header.oldest-pass=0;
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=ducksong.com; s=duo-1537391512170-ea99bbb3; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:from; bh=ndFPt93WfX78vT/GYP3fZ1Xedf/ZtJzu7Ke3HXfbU7w=; b=EqH13H3vzjmJ9Q+bg+gbb55U+qMMxChwX9M20U63zw4Ze77ML8l4k9iH8AweWTzBS74mWmwsQGOVW ZzccmKt1NjiKd2nmPu9QZi7crMB2CcOq2LbAIvXlCjguRkBR9/w5xnRfSSeN+pyoXOrJrR1gnc7PqW HNAYavRjJySkXi1A=
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=outbound.mailhop.org; s=dkim-high; h=content-type:cc:to:subject:message-id:date:from:in-reply-to:references: mime-version:from; bh=ndFPt93WfX78vT/GYP3fZ1Xedf/ZtJzu7Ke3HXfbU7w=; b=eknpRsy0XuFrJlg4ck++n08FKPNzcxia6/DzBnF4C28xYcqFfHdfTE76Oj0K0iAHIBQYP/ngRPxWy 5y23qoxMPRQmgtzXc4a6szfQl+SCHqV6Ltj6rrdedALP0iJgHcNa/7f3XpdYFQ9k2fyXxUnSI2uho4 7bEbvp1pw/P7QNBddDSjnjC+PLLn8SVFYv0CtVdrGoIE1Ps77N1jF8xSgC1eUyKOgcngD3C+LUKwWb lB4Sgrgr1pxq9xsn87ReE/FrAG4kz4MybfC18Ab43PqKAeALD0vKj0wSt9Ga1gMtpX0RGcwtLnwb4T YThrMPg7QzpkLv7fj8yGmOEMv7R4VKA==
X-MHO-RoutePath: bWNtYW51cw==
X-MHO-User: 62a1ddfe-0014-11ea-b80b-052b4a66b6b2
X-Report-Abuse-To: https://support.duocircle.com/support/solutions/articles/5000540958-duocircle-standard-smtp-abuse-information
X-Originating-IP: 209.85.210.46
X-Mail-Handler: DuoCircle Outbound SMTP
Received: from mail-ot1-f46.google.com (unknown [209.85.210.46]) by outbound3.ore.mailhop.org (Halon) with ESMTPSA id 62a1ddfe-0014-11ea-b80b-052b4a66b6b2; Tue, 05 Nov 2019 21:36:54 +0000 (UTC)
Received: by mail-ot1-f46.google.com with SMTP id l14so4653323oti.10; Tue, 05 Nov 2019 13:36:54 -0800 (PST)
X-Gm-Message-State: APjAAAVvSPLKPWCWcGe1fRykYfvpH7qttlTEVVOg4KZ9dL1V8bZfqN5h CfklE+6bmB9NcMNVrncNf8+PTOeWxZCA+Cb2ms4=
X-Google-Smtp-Source: APXvYqxIe7efKivjsrrXd/IPzAk4HInJleen+pApGKmyGa36A8GxRBjaN+fF8h2d8MiKERVwLW3bvrFtDrlM/qGTHgk=
X-Received: by 2002:a9d:6f96:: with SMTP id h22mr3388549otq.45.1572989814022;  Tue, 05 Nov 2019 13:36:54 -0800 (PST)
MIME-Version: 1.0
References: <157288641719.16495.4218503379126128243.idtracker@ietfa.amsl.com> <CA5EB3C0-F510-4883-B50B-51A3E46B47CA@ericsson.com> <CALGR9obp-YARLEXDVWvTqZ_h=Ocbn6m2On+uovK-SL-6TaOSXg@mail.gmail.com> <3F20108D-DEED-4AEF-89D3-55F11058110B@ericsson.com> <CALGR9oYHce0mnkj5Kz13EoR-zN3-xSr0igkJF2Z_dJ2vgfVNSQ@mail.gmail.com> <SN6PR11MB3087D25371090E7E40FA32B2CE7F0@SN6PR11MB3087.namprd11.prod.outlook.com>
In-Reply-To: <SN6PR11MB3087D25371090E7E40FA32B2CE7F0@SN6PR11MB3087.namprd11.prod.outlook.com>
From: Patrick McManus <mcmanus@ducksong.com>
Date: Tue, 5 Nov 2019 16:36:42 -0500
X-Gmail-Original-Message-ID: <CAOdDvNruDZuBYp2ABfWCKMF4o6rY5Qk6x6ofH1qCJgLfKpsCUg@mail.gmail.com>
Message-ID: <CAOdDvNruDZuBYp2ABfWCKMF4o6rY5Qk6x6ofH1qCJgLfKpsCUg@mail.gmail.com>
Subject: Re: [Masque] FW: New Version Notification for draft-kuehlewind-quic-proxy-discovery-00.txt
To: "Su, Chi-Jiun" <Chi-Jiun.Su@hughes.com>
Cc: Lucas Pardue <lucaspardue.24.7@gmail.com>,  Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>, "quic@ietf.org" <quic@ietf.org>,  Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>, "masque@ietf.org" <masque@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000019a84a0596a03b5b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/4rCs638UXyfVMisp7XpSNUmun2Y>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 05 Nov 2019 21:37:01 -0000

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

wpad is mostly an anti-pattern these days for important reasons - there is
no authentication. When there was less https it was chronically responsible
for people getting owned.

If the client is explicitly using a proxy it must have a reason to use and
trust a particular one (or class of one). quic of course provides
authentication to the peer and in the normal http way of things this auth
is linked to the origin which is rooted in some kind of out of band
information (i.e. the url obtained from a secure source such as an input
box, a bookmark, the command line, or transitively by finding the url
embedded in a resource found in those ways). unsecured broadcast mechanisms
like dhcp on (mostly) unauthenticated local networks don't satisfy that
which is why proxy config is generally viewed as an end host configuration
requirement that can't be autodiscovered. (often done right via enterprise
config).

even scenarios that only envision a series of CONNECT tunnels to the proxy
are giving up the end to end security of transport features that QUIC has
added and so I would think use of a untrusted proxy (i.e. one not rooted in
a trust anchor in some meaningful way) should be discouraged.

On Mon, Nov 4, 2019 at 3:35 PM Su, Chi-Jiun <Chi-Jiun.Su@hughes.com> wrote:

> Here are some more related to wpd for http:
>
>
>
> https://tools.ietf.org/html/draft-chow-httpbis-proxy-discovery-00
>
>
>
> https://tools.ietf.org/html/draft-nottingham-web-proxy-desc-01
>
>
>
>
>
>
>
> *From:* Masque <masque-bounces@ietf.org> *On Behalf Of *Lucas Pardue
> *Sent:* Monday, November 4, 2019 12:16 PM
> *To:* Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>
> *Cc:* quic@ietf.org; Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.co=
m>;
> masque@ietf.org
> *Subject:* Re: [Masque] FW: New Version Notification for
> draft-kuehlewind-quic-proxy-discovery-00.txt
>
>
>
> *CAUTION:* This email originated from outside of the organization. Do not
> click links or open attachments unless you recognize the sender and know
> the content is safe.
>
> I'm not an expert in either WPAD [1] or PAC [2], but I am an expert in
> feeling their pain as a user on Windows. Part of their pain comes from la=
ck
> of formal standardization, resulting in some word-of-mouth approaches to
> problem solving, especially how they work (or don't) with the standardise=
d
> approaches such as DHCP.
>
>
>
> In looking this up, I did discover draft-ietf-wrec-wpad-01, a > 20 I-D fo=
r
> WPAD [3], wow!
>
>
>
> [1] - https://en.wikipedia.org/wiki/Web_Proxy_Auto-Discovery_Protocol
> <https://urldefense.com/v3/__https:/en.wikipedia.org/wiki/Web_Proxy_Auto-=
Discovery_Protocol__;!0rLxnc5oh4s!jPosQt26EajScgUupoiCIMKOtu1eu9R0tg2CEkMXN=
q8Cx56sCmkL7PmI9PN7gcAGxA$>
>
> [2] - https://en.wikipedia.org/wiki/Proxy_auto-config
> <https://urldefense.com/v3/__https:/en.wikipedia.org/wiki/Proxy_auto-conf=
ig__;!0rLxnc5oh4s!jPosQt26EajScgUupoiCIMKOtu1eu9R0tg2CEkMXNq8Cx56sCmkL7PmI9=
POhddlmBA$>
>
> [3] - https://tools.ietf.org/html/draft-ietf-wrec-wpad-01
> <https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-ietf-wrec-w=
pad-01__;!0rLxnc5oh4s!jPosQt26EajScgUupoiCIMKOtu1eu9R0tg2CEkMXNq8Cx56sCmkL7=
PmI9POJiXk9oA$>
>
>
>
> On Mon, Nov 4, 2019 at 5:09 PM Mirja Kuehlewind <
> mirja.kuehlewind@ericsson.com> wrote:
>
> Hi Lucas,
>
>
>
> no, we didn=E2=80=99t consider this yet but only because we were not real=
ly aware
> of that. Do you have a pointer? Or send a PR =F0=9F=98=8A
>
>
>
> https://github.com/mirjak/draft-kuehlewind-quic-proxy-discovery
> <https://urldefense.com/v3/__https:/github.com/mirjak/draft-kuehlewind-qu=
ic-proxy-discovery__;!0rLxnc5oh4s!jPosQt26EajScgUupoiCIMKOtu1eu9R0tg2CEkMXN=
q8Cx56sCmkL7PmI9PMVg31Abw$>
>
>
>
> Mirja
>
>
>
>
>
> *From: *Lucas Pardue <lucaspardue.24.7@gmail.com>
> *Date: *Monday, 4. November 2019 at 18:06
> *To: *Mirja Kuehlewind <mirja.kuehlewind@ericsson.com
> <mirja.kuehlewind@ericsson..com>>
> *Cc: *"quic@ietf.org" <quic@ietf.org>, "masque@ietf.org" <masque@ietf.org=
>,
> Zaheduzzaman Sarker <zaheduzzaman.sarker@ericsson.com>
> *Subject: *Re: [Masque] FW: New Version Notification for
> draft-kuehlewind-quic-proxy-discovery-00.txt
>
>
>
> Thanks for sharing this.
>
>
>
> I wonder if you considered WPAD (Web Proxy Autodiscovery) or PAC (Proxy
> auto-config)? Although targetted at the application layer, it might help =
to
> comment on how those forms of discovery would relate to the methods
> outlined in your draft.
>
>
>
> Cheers,
>
> Lucas
>
>
>
> On Mon, Nov 4, 2019 at 4:58 PM Mirja Kuehlewind <mirja.kuehlewind=3D
> 40ericsson.com@dmarc.ietf.org> wrote:
>
> Hi all,
>
> we submitted a new draft that lists discovery mechanisms for QUIC-based
> proxies (see below). This is one piece of work that is needed for most of
> the use cases in draft-kuehlewind-quic-substrate.
>
> Let me know if you have any questions or comments!
>
> Mirja
>
>
> On 04.11.19, 17:53, "internet-drafts@ietf.org" <internet-drafts@ietf.org>
> wrote:
>
>
>     A new version of I-D, draft-kuehlewind-quic-proxy-discovery-00.txt
>     has been successfully submitted by Mirja Kuehlewind and posted to the
>     IETF repository.
>
>     Name:               draft-kuehlewind-quic-proxy-discovery
>     Revision:   00
>     Title:              Discovery Mechanism for QUIC-based,
> Non-transparent Proxy Services
>     Document date:      2019-11-04
>     Group:              Individual Submission
>     Pages:              11
>     URL:
> https://www.ietf.org/internet-drafts/draft-kuehlewind-quic-proxy-discover=
y-00.txt
> <https://urldefense.com/v3/__https:/www.ietf.org/internet-drafts/draft-ku=
ehlewind-quic-proxy-discovery-00.txt__;!0rLxnc5oh4s!jPosQt26EajScgUupoiCIMK=
Otu1eu9R0tg2CEkMXNq8Cx56sCmkL7PmI9PP6fOtFfw$>
>     Status:
> https://datatracker.ietf.org/doc/draft-kuehlewind-quic-proxy-discovery/
> <https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-kuehle=
wind-quic-proxy-discovery/__;!0rLxnc5oh4s!jPosQt26EajScgUupoiCIMKOtu1eu9R0t=
g2CEkMXNq8Cx56sCmkL7PmI9PNirJBnKQ$>
>     Htmlized:
> https://tools.ietf.org/html/draft-kuehlewind-quic-proxy-discovery-00
> <https://urldefense.com/v3/__https:/tools.ietf.org/html/draft-kuehlewind-=
quic-proxy-discovery-00__;!0rLxnc5oh4s!jPosQt26EajScgUupoiCIMKOtu1eu9R0tg2C=
EkMXNq8Cx56sCmkL7PmI9PNt2ljWVQ$>
>     Htmlized:
> https://datatracker.ietf.org/doc/html/draft-kuehlewind-quic-proxy-discove=
ry
> <https://urldefense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-k=
uehlewind-quic-proxy-discovery__;!0rLxnc5oh4s!jPosQt26EajScgUupoiCIMKOtu1eu=
9R0tg2CEkMXNq8Cx56sCmkL7PmI9PNLkowwPw$>
>
>
>     Abstract:
>        Often an intermediate instance (such as a proxy server) is used to
>        connect to a web server or a communicating peer if a direct end-to=
-
>        end IP connectivity is not possible or the proxy can provide a
>        support service like, e.g., address anonymisation.  To use a non-
>        transparent proxy a client explicitly connects to it and requests
>        forwarding to the final target server.  The client either knows th=
e
>        proxy address as preconfigured in the application or can dynamical=
ly
>        learn about available proxy services.  This document describes
>        different discovery mechanisms for non-transparent proxies that ar=
e
>        either located in the local network, e.g. home or enterprise
> network,
>        in the access network, or somewhere else on the Internet usually
>        close to the target server or even in the same network as the targ=
et
>        server.
>
>        This document assumes that the non-transparent proxy server is
>        connected via QUIC and discusses potential discovery mechanisms fo=
r
>        such a QUIC-based, non-transparent proxy.
>
>
>
>
>     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
> <https://urldefense.com/v3/__http:/tools.ietf.org__;!0rLxnc5oh4s!jPosQt26=
EajScgUupoiCIMKOtu1eu9R0tg2CEkMXNq8Cx56sCmkL7PmI9PNQh7NkuA$>
> .
>
>     The IETF Secretariat
>
>
>
> --
> Masque mailing list
> Masque@ietf.org
> https://www.ietf.org/mailman/listinfo/masque
> <https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo/masque_=
_;!0rLxnc5oh4s!jPosQt26EajScgUupoiCIMKOtu1eu9R0tg2CEkMXNq8Cx56sCmkL7PmI9PO4=
I6Apdw$>
>
> --
> Masque mailing list
> Masque@ietf.org
> https://www.ietf.org/mailman/listinfo/masque
>

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

<div dir=3D"ltr">wpad is mostly an anti-pattern these days for important re=
asons - there is no authentication. When there was less https it was chroni=
cally responsible for people getting owned.<div><br></div><div>If the clien=
t is explicitly using a proxy it must have a reason to use and trust a part=
icular one (or class of one). quic of course provides authentication to the=
 peer and in the normal http way of things this auth is linked to the origi=
n which is rooted in some kind of out of band information (i.e. the url obt=
ained from a secure source such as an input box, a bookmark, the command li=
ne, or transitively by finding the url embedded in a resource found in thos=
e ways). unsecured broadcast mechanisms like dhcp on (mostly) unauthenticat=
ed local networks don&#39;t satisfy that which is why proxy config is gener=
ally viewed as an end host configuration requirement that can&#39;t be auto=
discovered. (often done right via enterprise config).</div><div><br></div><=
div>even scenarios that only envision a series of CONNECT tunnels to the pr=
oxy are giving up the end to end security of transport features that QUIC h=
as added and so I would think use of a untrusted proxy (i.e. one not rooted=
 in a trust anchor in some meaningful way) should be discouraged.</div></di=
v><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On M=
on, Nov 4, 2019 at 3:35 PM Su, Chi-Jiun &lt;<a href=3D"mailto:Chi-Jiun.Su@h=
ughes.com">Chi-Jiun.Su@hughes.com</a>&gt; wrote:<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 lang=3D"EN-US">
<div class=3D"gmail-m_3211793246764681348WordSection1">
<p class=3D"MsoNormal">Here are some more related to wpd for http:<u></u><u=
></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><a href=3D"https://tools.ietf.org/html/draft-chow-ht=
tpbis-proxy-discovery-00" target=3D"_blank">https://tools.ietf.org/html/dra=
ft-chow-httpbis-proxy-discovery-00</a><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><a href=3D"https://tools.ietf.org/html/draft-notting=
ham-web-proxy-desc-01" target=3D"_blank">https://tools.ietf.org/html/draft-=
nottingham-web-proxy-desc-01</a><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><b>From:</b> Masque &lt;<a href=3D"mailto:masque-bou=
nces@ietf.org" target=3D"_blank">masque-bounces@ietf.org</a>&gt; <b>On Beha=
lf Of
</b>Lucas Pardue<br>
<b>Sent:</b> Monday, November 4, 2019 12:16 PM<br>
<b>To:</b> Mirja Kuehlewind &lt;<a href=3D"mailto:mirja.kuehlewind@ericsson=
.com" target=3D"_blank">mirja.kuehlewind@ericsson.com</a>&gt;<br>
<b>Cc:</b> <a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic@ietf.org=
</a>; Zaheduzzaman Sarker &lt;<a href=3D"mailto:zaheduzzaman.sarker@ericsso=
n.com" target=3D"_blank">zaheduzzaman.sarker@ericsson.com</a>&gt;; <a href=
=3D"mailto:masque@ietf.org" target=3D"_blank">masque@ietf.org</a><br>
<b>Subject:</b> Re: [Masque] FW: New Version Notification for draft-kuehlew=
ind-quic-proxy-discovery-00.txt<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div align=3D"center">
<table border=3D"0" cellpadding=3D"0" width=3D"100%" style=3D"width:100%;ba=
ckground:rgb(255,235,156)">
<tbody>
<tr>
<td style=3D"padding:0.75pt">
<p class=3D"MsoNormal"><b><span style=3D"color:red">CAUTION:</span></b> Thi=
s email originated from outside of the organization. Do not click links or =
open attachments unless you recognize the sender and know the content is sa=
fe.<u></u><u></u></p>
</td>
</tr>
</tbody>
</table>
</div>
</div>
<div>
<div>
<p class=3D"MsoNormal">I&#39;m not an expert in either WPAD [1] or PAC [2],=
 but I am an expert in feeling their pain as a user on Windows. Part of the=
ir pain comes from lack of formal standardization, resulting in some word-o=
f-mouth approaches to problem solving,
 especially how they work (or don&#39;t) with the standardised approaches s=
uch as DHCP.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">In looking this up, I did discover draft-ietf-wrec-w=
pad-01, a &gt; 20 I-D for WPAD [3], wow!<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[1] - <a href=3D"https://urldefense.com/v3/__https:/=
en.wikipedia.org/wiki/Web_Proxy_Auto-Discovery_Protocol__;!0rLxnc5oh4s!jPos=
Qt26EajScgUupoiCIMKOtu1eu9R0tg2CEkMXNq8Cx56sCmkL7PmI9PN7gcAGxA$" target=3D"=
_blank">
https://en.wikipedia.org/wiki/Web_Proxy_Auto-Discovery_Protocol</a><u></u><=
u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[2] - <a href=3D"https://urldefense.com/v3/__https:/=
en.wikipedia.org/wiki/Proxy_auto-config__;!0rLxnc5oh4s!jPosQt26EajScgUupoiC=
IMKOtu1eu9R0tg2CEkMXNq8Cx56sCmkL7PmI9POhddlmBA$" target=3D"_blank">
https://en.wikipedia.org/wiki/Proxy_auto-config</a><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">[3] - <a href=3D"https://urldefense.com/v3/__https:/=
tools.ietf.org/html/draft-ietf-wrec-wpad-01__;!0rLxnc5oh4s!jPosQt26EajScgUu=
poiCIMKOtu1eu9R0tg2CEkMXNq8Cx56sCmkL7PmI9POJiXk9oA$" target=3D"_blank">
https://tools.ietf.org/html/draft-ietf-wrec-wpad-01</a><u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Mon, Nov 4, 2019 at 5:09 PM Mirja Kuehlewind &lt;=
<a href=3D"mailto:mirja.kuehlewind@ericsson.com" target=3D"_blank">mirja.ku=
ehlewind@ericsson.com</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4=
.8pt;margin-right:0in">
<div>
<div>
<p class=3D"MsoNormal">Hi Lucas,<span lang=3D"DE"><u></u><u></u></span></p>
<p class=3D"MsoNormal">=C2=A0<span lang=3D"DE"><u></u><u></u></span></p>
<p class=3D"MsoNormal">no, we didn=E2=80=99t consider this yet but only bec=
ause we were not really aware of that. Do you have a pointer? Or send a PR
<span style=3D"font-family:&quot;Segoe UI Emoji&quot;,sans-serif">=F0=9F=98=
=8A</span><span lang=3D"DE"><u></u><u></u></span></p>
<p class=3D"MsoNormal">=C2=A0<span lang=3D"DE"><u></u><u></u></span></p>
<p class=3D"MsoNormal"><a href=3D"https://urldefense.com/v3/__https:/github=
.com/mirjak/draft-kuehlewind-quic-proxy-discovery__;!0rLxnc5oh4s!jPosQt26Ea=
jScgUupoiCIMKOtu1eu9R0tg2CEkMXNq8Cx56sCmkL7PmI9PMVg31Abw$" target=3D"_blank=
">https://github.com/mirjak/draft-kuehlewind-quic-proxy-discovery</a><span =
lang=3D"DE"><u></u><u></u></span></p>
<p class=3D"MsoNormal">=C2=A0<span lang=3D"DE"><u></u><u></u></span></p>
<p class=3D"MsoNormal">Mirja<span lang=3D"DE"><u></u><u></u></span></p>
<p class=3D"MsoNormal">=C2=A0<span lang=3D"DE"><u></u><u></u></span></p>
<p class=3D"MsoNormal">=C2=A0<span lang=3D"DE"><u></u><u></u></span></p>
<div style=3D"border-right:none currentcolor;border-bottom:none currentcolo=
r;border-left:none currentcolor;border-top:1pt solid currentcolor;padding:3=
pt 0in 0in">
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">
<b><span lang=3D"DE" style=3D"font-size:12pt;color:black">From: </span></b>=
<span lang=3D"DE" style=3D"font-size:12pt;color:black">Lucas Pardue &lt;<a =
href=3D"mailto:lucaspardue.24.7@gmail.com" target=3D"_blank">lucaspardue.24=
.7@gmail.com</a>&gt;<br>
<b>Date: </b>Monday, 4. November 2019 at 18:06<br>
<b>To: </b>Mirja Kuehlewind &lt;<a href=3D"mailto:mirja.kuehlewind@ericsson=
..com" target=3D"_blank">mirja.kuehlewind@ericsson.com</a>&gt;<br>
<b>Cc: </b>&quot;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic@ie=
tf.org</a>&quot; &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">qui=
c@ietf.org</a>&gt;, &quot;<a href=3D"mailto:masque@ietf.org" target=3D"_bla=
nk">masque@ietf.org</a>&quot; &lt;<a href=3D"mailto:masque@ietf.org" target=
=3D"_blank">masque@ietf.org</a>&gt;,
 Zaheduzzaman Sarker &lt;<a href=3D"mailto:zaheduzzaman.sarker@ericsson.com=
" target=3D"_blank">zaheduzzaman.sarker@ericsson.com</a>&gt;<br>
<b>Subject: </b>Re: [Masque] FW: New Version Notification for draft-kuehlew=
ind-quic-proxy-discovery-00.txt</span><span lang=3D"DE"><u></u><u></u></spa=
n></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">
<span lang=3D"DE">=C2=A0<u></u><u></u></span></p>
</div>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">
<span lang=3D"DE">Thanks for sharing this.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">
<span lang=3D"DE">=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">
<span lang=3D"DE">I wonder if you considered WPAD (Web Proxy Autodiscovery)=
 or PAC (Proxy auto-config)? Although targetted at the application layer, i=
t might help to comment on how those forms of discovery would relate to the=
 methods outlined in your draft.<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">
<span lang=3D"DE">=C2=A0<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">
<span lang=3D"DE">Cheers,<u></u><u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">
<span lang=3D"DE">Lucas<u></u><u></u></span></p>
</div>
</div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">
<span lang=3D"DE">=C2=A0<u></u><u></u></span></p>
<div>
<div>
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">
<span lang=3D"DE">On Mon, Nov 4, 2019 at 4:58 PM Mirja Kuehlewind &lt;mirja=
.kuehlewind=3D<a href=3D"mailto:40ericsson.com@dmarc.ietf.org" target=3D"_b=
lank">40ericsson.com@dmarc.ietf.org</a>&gt; wrote:<u></u><u></u></span></p>
</div>
<blockquote style=3D"border-top:none currentcolor;border-right:none current=
color;border-bottom:none currentcolor;border-left:1pt solid rgb(204,204,204=
);padding:0in 0in 0in 6pt;margin:5pt 0in 5pt 4.8pt">
<p class=3D"MsoNormal" style=3D"margin-left:0.5in">
<span lang=3D"DE">Hi all,<br>
<br>
we submitted a new draft that lists discovery mechanisms for QUIC-based pro=
xies (see below). This is one piece of work that is needed for most of the =
use cases in draft-kuehlewind-quic-substrate.
<br>
<br>
Let me know if you have any questions or comments!<br>
<br>
Mirja<br>
<br>
<br>
On 04.11.19, 17:53, &quot;<a href=3D"mailto:internet-drafts@ietf.org" targe=
t=3D"_blank">internet-drafts@ietf.org</a>&quot; &lt;<a href=3D"mailto:inter=
net-drafts@ietf.org" target=3D"_blank">internet-drafts@ietf.org</a>&gt; wro=
te:<br>
<br>
<br>
=C2=A0 =C2=A0 A new version of I-D, draft-kuehlewind-quic-proxy-discovery-0=
0.txt<br>
=C2=A0 =C2=A0 has been successfully submitted by Mirja Kuehlewind and poste=
d to the<br>
=C2=A0 =C2=A0 IETF repository.<br>
<br>
=C2=A0 =C2=A0 Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0d=
raft-kuehlewind-quic-proxy-discovery<br>
=C2=A0 =C2=A0 Revision:=C2=A0 =C2=A000<br>
=C2=A0 =C2=A0 Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Discov=
ery Mechanism for QUIC-based, Non-transparent Proxy Services<br>
=C2=A0 =C2=A0 Document date:=C2=A0 =C2=A0 =C2=A0 2019-11-04<br>
=C2=A0 =C2=A0 Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Indivi=
dual Submission<br>
=C2=A0 =C2=A0 Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 11<br>
=C2=A0 =C2=A0 URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"http=
s://urldefense.com/v3/__https:/www.ietf.org/internet-drafts/draft-kuehlewin=
d-quic-proxy-discovery-00.txt__;!0rLxnc5oh4s!jPosQt26EajScgUupoiCIMKOtu1eu9=
R0tg2CEkMXNq8Cx56sCmkL7PmI9PP6fOtFfw$" target=3D"_blank">
https://www.ietf.org/internet-drafts/draft-kuehlewind-quic-proxy-discovery-=
00.txt</a><br>
=C2=A0 =C2=A0 Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://u=
rldefense.com/v3/__https:/datatracker.ietf.org/doc/draft-kuehlewind-quic-pr=
oxy-discovery/__;!0rLxnc5oh4s!jPosQt26EajScgUupoiCIMKOtu1eu9R0tg2CEkMXNq8Cx=
56sCmkL7PmI9PNirJBnKQ$" target=3D"_blank">https://datatracker.ietf.org/doc/=
draft-kuehlewind-quic-proxy-discovery/</a><br>
=C2=A0 =C2=A0 Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://urldef=
ense.com/v3/__https:/tools.ietf.org/html/draft-kuehlewind-quic-proxy-discov=
ery-00__;!0rLxnc5oh4s!jPosQt26EajScgUupoiCIMKOtu1eu9R0tg2CEkMXNq8Cx56sCmkL7=
PmI9PNt2ljWVQ$" target=3D"_blank">https://tools.ietf.org/html/draft-kuehlew=
ind-quic-proxy-discovery-00</a><br>
=C2=A0 =C2=A0 Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://urldef=
ense.com/v3/__https:/datatracker.ietf.org/doc/html/draft-kuehlewind-quic-pr=
oxy-discovery__;!0rLxnc5oh4s!jPosQt26EajScgUupoiCIMKOtu1eu9R0tg2CEkMXNq8Cx5=
6sCmkL7PmI9PNLkowwPw$" target=3D"_blank">https://datatracker.ietf.org/doc/h=
tml/draft-kuehlewind-quic-proxy-discovery</a><br>
<br>
<br>
=C2=A0 =C2=A0 Abstract:<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0Often an intermediate instance (such as a proxy =
server) is used to<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0connect to a web server or a communicating peer =
if a direct end-to-<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0end IP connectivity is not possible or the proxy=
 can provide a<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0support service like, e.g., address anonymisatio=
n.=C2=A0 To use a non-<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0transparent proxy a client explicitly connects t=
o it and requests<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0forwarding to the final target server.=C2=A0 The=
 client either knows the<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0proxy address as preconfigured in the applicatio=
n or can dynamically<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0learn about available proxy services.=C2=A0 This=
 document describes<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0different discovery mechanisms for non-transpare=
nt proxies that are<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0either located in the local network, e.g. home o=
r enterprise network,<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0in the access network, or somewhere else on the =
Internet usually<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0close to the target server or even in the same n=
etwork as the target<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0server.<br>
<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0This document assumes that the non-transparent p=
roxy server is<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0connected via QUIC and discusses potential disco=
very mechanisms for<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0such a QUIC-based, non-transparent proxy.<br>
<br>
<br>
<br>
<br>
=C2=A0 =C2=A0 Please note that it may take a couple of minutes from the tim=
e of submission<br>
=C2=A0 =C2=A0 until the htmlized version and diff are available at <a href=
=3D"https://urldefense.com/v3/__http:/tools.ietf.org__;!0rLxnc5oh4s!jPosQt2=
6EajScgUupoiCIMKOtu1eu9R0tg2CEkMXNq8Cx56sCmkL7PmI9PNQh7NkuA$" target=3D"_bl=
ank">
tools.ietf.org</a>.<br>
<br>
=C2=A0 =C2=A0 The IETF Secretariat<br>
<br>
<br>
<br>
-- <br>
Masque mailing list<br>
<a href=3D"mailto:Masque@ietf.org" target=3D"_blank">Masque@ietf.org</a><br=
>
<a href=3D"https://urldefense.com/v3/__https:/www.ietf.org/mailman/listinfo=
/masque__;!0rLxnc5oh4s!jPosQt26EajScgUupoiCIMKOtu1eu9R0tg2CEkMXNq8Cx56sCmkL=
7PmI9PO4I6Apdw$" target=3D"_blank">https://www.ietf.org/mailman/listinfo/ma=
sque</a><u></u><u></u></span></p>
</blockquote>
</div>
</div>
</div>
</blockquote>
</div>
</div>
</div>

-- <br>
Masque mailing list<br>
<a href=3D"mailto:Masque@ietf.org" target=3D"_blank">Masque@ietf.org</a><br=
>
<a href=3D"https://www.ietf.org/mailman/listinfo/masque" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/mailman/listinfo/masque</a><br>
</blockquote></div>

--00000000000019a84a0596a03b5b--


From nobody Tue Nov  5 17:02:41 2019
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 DAEB612011B for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 17:02:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.69
X-Spam-Level: 
X-Spam-Status: No, score=-2.69 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, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=GJqJja9Y; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=A82z0Ye+
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 B6Zar4hr4udd for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 17:02:32 -0800 (PST)
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 861A71200C3 for <quic@ietf.org>; Tue,  5 Nov 2019 17:01:43 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id E52B920BF5; Tue,  5 Nov 2019 20:01:42 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Tue, 05 Nov 2019 20:01:42 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=from :content-type:content-transfer-encoding:mime-version:subject :message-id:date:cc:to; s=fm1; bh=RG1yH9Ze+kSNuxyrcBmz9/AjFrO10H 45SO8M3J2KQbI=; b=GJqJja9Y2OF5FwH7BJp1t3qcPgmAdSvH1S/EQtcjRSkVS3 G7Fv9v0aS+KkZ0Gm/aq5hD9AvNmOHsJr4JS7bP5sQUpYM7Hv0VwmzPMdEHaglTJ+ bUVlg6caZLpLXCle65q1ug774yJFLCcZzy25xlYfpVcWJ/ISNjx/wbO54YUQnHXi L8bBb7DnR+87rqx3752uVg3ld8gMH2EitmKf2VEGaagqM9X6hHnc9vSE44JgsTOd Muu2lOYQlxRbmmg7CqIudT3zgb7w18EfXO6206AD3X2fwFZ7fhznCjcA1bHYI9sd SSJZzx0nocbubDcqKq/aqLJ2cn1oeASjDsKht3CA==
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-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=RG1yH9 Ze+kSNuxyrcBmz9/AjFrO10H45SO8M3J2KQbI=; b=A82z0Ye+h957s17LbD9Ob+ PeJziXQfd1+GPoV54j61EEco06J4WShmBonWqGIKGxtX0ZDOh94/Pp/Fv3ErsDsW A0RhpcAJnb/+EpAsrrn90jp76BmAsDRr4JA2kaJkaSts1ecv2NI5b1N72F9uW4dx tBOLbgxGsTtyiilxGYF5/8o2wvlx2cle4Ki6KcIZG57FiKEVmoQfexhCbCo1S0p1 mGtN9J1YGLcdozk+9TBD1bpOgHixs0zB45Wyi/fuzN3ksrGg3M1Wc8izhiLIvw2j XTThl/dbvSMrCdp7NC4jziCR3ull3uBnQgYpAF8xe5Aj+aK6f42kJ3cCIyz7Q/Pg ==
X-ME-Sender: <xms:dRvCXeOx-O3zVgoAWSK9SBSN6J4JIQaMFVBP5wcHR-dHMo4OysZtSg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudduiedgfedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephfgtgfgguffkfffvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhkucfp ohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinhephh htthhpfegrnhguqhhprggtkhgurhgrfhhtshhtohhthhgrthhprhhotggvshhsrghsfigv lhhlrdgrshdpghhithhhuhgsrdgtohhmnecukfhppeduudelrddujedrudehkedrvdehud enucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnhhothdrnhgvthenucevlhhu shhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:dRvCXfZpQs5sECSeIlP4VA9JwJ61b310ev5pielo452UvvXn1SGEqA> <xmx:dRvCXVfn5p-v4aWhY73aIQjTVuN5u717Cvzqv-oEBPjWGuEpqA6vtA> <xmx:dRvCXWNbk8667ti_CjhAfDgZceh_POBYu-6bfvlOli9bAuxjZM9CRQ> <xmx:dhvCXYj_Vl52i4ukJyPnGZh4Ru5kr26tsZqkbIb3Dy0fIhUaEbW_iA>
Received: from macbook-pro.mnot.net (unknown [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id 8615C80061; Tue,  5 Nov 2019 20:01:40 -0500 (EST)
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 13.0 \(3601.0.10\))
Subject: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
Message-Id: <6A43BEC7-F9DE-40C9-BF70-BF1618EAFE01@mnot.net>
Date: Wed, 6 Nov 2019 12:01:34 +1100
Cc: Lars Eggert <lars@eggert.org>
To: IETF QUIC WG <quic@ietf.org>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/nEOfQdn10b1MIGyHA286lHu7Ulg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 06 Nov 2019 01:02:39 -0000

Previously, we've moved to the 'late-stage process' documented at [1] =
for the Transport and TLS drafts. The chairs and editors now feel that =
it's time to move the Recovery, HTTP/3, and QPACK drafts to that process =
as well.

As before, this is because we're getting to a stage we feel the =
documents would benefit from slower and slightly more formal process, so =
that the rate of change is not so high, changes that do occur are =
well-vetted, and the documents get closer to reflecting consensus in the =
working group.

If we do this, we're saying that we have gained consensus on what =
remains in these documents, excepting their outstanding issues. As per =
our charter:

"""
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 doesn't mean that new issues can't be raised against those drafts. =
However, new issues against them will be judged for whether they contain =
new information (in particular, security or interoperability impact), a =
clear technical defect, or have significant (in the judgement of the =
chairs) support for further discussion. If the issue isn't =
well-described or atomic, it may be closed with a request to refactor, =
or refactored for you.

Again, this does not affect editorial issues.

Practically speaking, it means that new issues will be triaged by the =
Chairs -- not the editors (although they can still "claim" purely =
editorial issues) -- and those that don't meet the criteria above will =
be closed. Those that do will be labeled (again, by the Chairs only) as =
`design`.

It also means that all of the closed `design` issues against these =
drafts will be marked as `has-consensus`. Additionally, the `quicv2` =
issues against them will be closed and marked `has-consensus`.

The issues that will be labeled `has-consensus` (and closed, if still =
open) are listed here:
 =20
=
https://github.com/quicwg/base-drafts/issues?q=3Dis%3Aissue+is%3Aclosed+la=
bel%3Adesign+-label%3Ahas-consensus+-label%3A-transport+-label%3A-tls

We believe that all of these issues have been discussed and the group =
has formed consensus on them; this only formalises that.

If you have concerns or questions, please discuss them on-list; barring =
pushback, we'll adopt this on 15-Nov-2019.

Cheers,

1. =
https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md#late-sta=
ge-process

--
Mark and Lars, QUIC WG Chairs


From nobody Tue Nov  5 17:36:48 2019
Return-Path: <rch@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 A5C1A120154 for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 17:36:47 -0800 (PST)
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, DKIMWL_WL_MED=-0.001, 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_HELO_NONE=0.001, SPF_PASS=-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 xYUNkf4K7zOw for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 17:36:45 -0800 (PST)
Received: from mail-wm1-x32f.google.com (mail-wm1-x32f.google.com [IPv6:2a00:1450:4864:20::32f]) (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 2ED42120041 for <quic@ietf.org>; Tue,  5 Nov 2019 17:35:58 -0800 (PST)
Received: by mail-wm1-x32f.google.com with SMTP id t26so1506438wmi.4 for <quic@ietf.org>; Tue, 05 Nov 2019 17:35:58 -0800 (PST)
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=anwoqdWzFr0SVd2T9Nn/JPq2JPCLjRhHa2QbGe0BP+M=; b=EWcWTfoFa1h1v6Y6dZpQddw8OEEXD6KRigmgB7WB0MKKNekiPUtJjRr4nc0nCDTlrr cpAorHDPWTJ3oItijLIcjeh0/k44Mc2RIn9qFRO7+/NHYqpl9Iv3DGX/DPcq/kB4N2pr /5oggIz/+m4Xc5F8nksDyJVmo56PAVkFBfhD/TtsHoo9Hyaez+sO6wzOY2CJZvmTxT0C zUFGeLersr/OURTSw18KZjRKYgmsgnO3GEV6XEL07bynoQbBUDFNRQLXp5x7d6oqozhN H+Je6Q5u59qRbsZMZueh4c1ETSGKmUZO8yCaVm3k7nz3xQfbFoe3sJn2okBUC/k4lMyr q9cg==
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=anwoqdWzFr0SVd2T9Nn/JPq2JPCLjRhHa2QbGe0BP+M=; b=S5issJvGkPfqTGYfYIffV2qbH3wRl5rrSgzjWkyF4EvI4KQM+vdPpKmpT5+j73DSJm XGjH9MQFYKCAJxUTK9fRnFas6ffBiNOYrdwg+SBaRseq6BANIFbwnmRT4dB9p4dxcXXz t8dSXnEj32MuMcIjccSrzIMPRLRquk1KGTb2+SNIH0v/auXPtWfRNDfXH4zwH9aXv1ps fxVMz6HJSX08om+uCzLAytp8Huaq7tQ94zu1J5CQRyI93/5Nt+Ns4aeI9bzvqbCGl3vH wCXHtZpPPOuadrPjegJWGyidZt05pK7N36MJbbb/X+EEws7Pnx7CtFJKOAGcdmRg4QVH OEqg==
X-Gm-Message-State: APjAAAU1tWuD2nej+XsH9sLIlU15LLxyiuC8vq0222Ef1SBkMdSoCz0s eDnTFl5QZed6ideK78VaV5GeCohT6ZbMqPunWtSj7bq77bg=
X-Google-Smtp-Source: APXvYqyyTtMHHkfagotXHw8ha5UTD7pbZ2Q2LIvobCU/Qk0lElSscdwQS/NiNwCN4eiuDhoC6edsT08oGdPetInEjCQ=
X-Received: by 2002:a05:600c:12:: with SMTP id g18mr166538wmc.44.1573004156068;  Tue, 05 Nov 2019 17:35:56 -0800 (PST)
MIME-Version: 1.0
References: <6A43BEC7-F9DE-40C9-BF70-BF1618EAFE01@mnot.net>
In-Reply-To: <6A43BEC7-F9DE-40C9-BF70-BF1618EAFE01@mnot.net>
From: Ryan Hamilton <rch@google.com>
Date: Tue, 5 Nov 2019 17:35:43 -0800
Message-ID: <CAJ_4DfQocLyL=3j_xDS_b5Jj_U62Dt8wH=Ymi6tEKHJwcwVJtA@mail.gmail.com>
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
To: Mark Nottingham <mnot@mnot.net>
Cc: IETF QUIC WG <quic@ietf.org>, Lars Eggert <lars@eggert.org>
Content-Type: multipart/alternative; boundary="000000000000f443460596a39145"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/OnkPcLADAReCcY4oWNQ5sJFBfXM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 06 Nov 2019 01:36:48 -0000

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

For QPACK and Recovery, this sounds great to me. For  HTTP/3, as I
understand it, we still have a design team working on priorities. Can you
clarify how this effort is affected by the late stage process? (Or is is
basically unaffected as it is an open issue?)

On Tue, Nov 5, 2019 at 5:02 PM Mark Nottingham <mnot@mnot.net> wrote:

> Previously, we've moved to the 'late-stage process' documented at [1] for
> the Transport and TLS drafts. The chairs and editors now feel that it's
> time to move the Recovery, HTTP/3, and QPACK drafts to that process as well.
>
> As before, this is because we're getting to a stage we feel the documents
> would benefit from slower and slightly more formal process, so that the
> rate of change is not so high, changes that do occur are well-vetted, and
> the documents get closer to reflecting consensus in the working group.
>
> If we do this, we're saying that we have gained consensus on what remains
> in these documents, excepting their outstanding issues. As per our charter:
>
> """
> 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 doesn't mean that new issues can't be raised against those drafts.
> However, new issues against them will be judged for whether they contain
> new information (in particular, security or interoperability impact), a
> clear technical defect, or have significant (in the judgement of the
> chairs) support for further discussion. If the issue isn't well-described
> or atomic, it may be closed with a request to refactor, or refactored for
> you.
>
> Again, this does not affect editorial issues.
>
> Practically speaking, it means that new issues will be triaged by the
> Chairs -- not the editors (although they can still "claim" purely editorial
> issues) -- and those that don't meet the criteria above will be closed.
> Those that do will be labeled (again, by the Chairs only) as `design`.
>
> It also means that all of the closed `design` issues against these drafts
> will be marked as `has-consensus`. Additionally, the `quicv2` issues
> against them will be closed and marked `has-consensus`.
>
> The issues that will be labeled `has-consensus` (and closed, if still
> open) are listed here:
>
>
> https://github.com/quicwg/base-drafts/issues?q=is%3Aissue+is%3Aclosed+label%3Adesign+-label%3Ahas-consensus+-label%3A-transport+-label%3A-tls
>
> We believe that all of these issues have been discussed and the group has
> formed consensus on them; this only formalises that.
>
> If you have concerns or questions, please discuss them on-list; barring
> pushback, we'll adopt this on 15-Nov-2019.
>
> Cheers,
>
> 1.
> https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md#late-stage-process
>
> --
> Mark and Lars, QUIC WG Chairs
>
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:trebuche=
t ms,sans-serif">For QPACK and Recovery, this sounds great to me. For=C2=A0=
 HTTP/3, as I understand it, we still have a design team working on priorit=
ies. Can you clarify how this effort is affected by the late stage process?=
 (Or is is basically unaffected as it is an open issue?)</div></div><br><di=
v class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Nov 5=
, 2019 at 5:02 PM Mark Nottingham &lt;<a href=3D"mailto:mnot@mnot.net">mnot=
@mnot.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">Previously, we&#39;ve moved to the &#39;late-stage process&#39; =
documented at [1] for the Transport and TLS drafts. The chairs and editors =
now feel that it&#39;s time to move the Recovery, HTTP/3, and QPACK drafts =
to that process as well.<br>
<br>
As before, this is because we&#39;re getting to a stage we feel the documen=
ts would benefit from slower and slightly more formal process, so that the =
rate of change is not so high, changes that do occur are well-vetted, and t=
he documents get closer to reflecting consensus in the working group.<br>
<br>
If we do this, we&#39;re saying that we have gained consensus on what remai=
ns in these documents, excepting their outstanding issues. As per our chart=
er:<br>
<br>
&quot;&quot;&quot;<br>
Note that consensus is required both for changes to the current protocol me=
chanisms and retention of current mechanisms. In particular, because someth=
ing is in the initial document set does not imply that there is consensus a=
round the feature or around how it is specified.<br>
&quot;&quot;&quot;<br>
<br>
That doesn&#39;t mean that new issues can&#39;t be raised against those dra=
fts. However, new issues against them will be judged for whether they conta=
in new information (in particular, security or interoperability impact), a =
clear technical defect, or have significant (in the judgement of the chairs=
) support for further discussion. If the issue isn&#39;t well-described or =
atomic, it may be closed with a request to refactor, or refactored for you.=
<br>
<br>
Again, this does not affect editorial issues.<br>
<br>
Practically speaking, it means that new issues will be triaged by the Chair=
s -- not the editors (although they can still &quot;claim&quot; purely edit=
orial issues) -- and those that don&#39;t meet the criteria above will be c=
losed. Those that do will be labeled (again, by the Chairs only) as `design=
`.<br>
<br>
It also means that all of the closed `design` issues against these drafts w=
ill be marked as `has-consensus`. Additionally, the `quicv2` issues against=
 them will be closed and marked `has-consensus`.<br>
<br>
The issues that will be labeled `has-consensus` (and closed, if still open)=
 are listed here:<br>
<br>
<a href=3D"https://github.com/quicwg/base-drafts/issues?q=3Dis%3Aissue+is%3=
Aclosed+label%3Adesign+-label%3Ahas-consensus+-label%3A-transport+-label%3A=
-tls" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-d=
rafts/issues?q=3Dis%3Aissue+is%3Aclosed+label%3Adesign+-label%3Ahas-consens=
us+-label%3A-transport+-label%3A-tls</a><br>
<br>
We believe that all of these issues have been discussed and the group has f=
ormed consensus on them; this only formalises that.<br>
<br>
If you have concerns or questions, please discuss them on-list; barring pus=
hback, we&#39;ll adopt this on 15-Nov-2019.<br>
<br>
Cheers,<br>
<br>
1. <a href=3D"https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTIN=
G.md#late-stage-process" rel=3D"noreferrer" target=3D"_blank">https://githu=
b.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md#late-stage-process</a>=
<br>
<br>
--<br>
Mark and Lars, QUIC WG Chairs<br>
<br>
</blockquote></div>

--000000000000f443460596a39145--


From nobody Tue Nov  5 17:41:50 2019
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 07363120041 for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 17:41:49 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.69
X-Spam-Level: 
X-Spam-Status: No, score=-2.69 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, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=n2qTu5+R; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=LZaDCHa1
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 7q2rkOMlHDOw for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 17:41:37 -0800 (PST)
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 E4926120154 for <quic@ietf.org>; Tue,  5 Nov 2019 17:41:34 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 1E8C221EAF; Tue,  5 Nov 2019 20:41:34 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Tue, 05 Nov 2019 20:41:34 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=d hHxy6rjp423nbcwA2AsULYblJ8+qXZGxi1qQNlRhfo=; b=n2qTu5+RnldSO+hjQ NRVmEJ26vDYHvH9ABVkhCPJHsKXUOhQIptEHWkv2cSdbum1zaiTa9rEYRX2oPl/j OAgTgy/bIR3zn6eaB0+TMwT60WotCPAm92905A+KkpPRCszibF9H7KynhrAOcX/9 rInM08xCw81qE0Fe5LnYHsHVeyZKbltA6MyEK7DDva5iWco1+OiRmC/kGHLLWo5H KVmgYLXbQT1Fcpg8fJJ2RWbI0nW8SueFgip/PPN6tpKIdImE5hOmVN/r1aVhT/wM JjkZnroPJ2SnaG9xbIFkuX7ez37qJB0kYfcRL23EKeDu1T6FM7zbqfg4d918E1RF 96uvg==
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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=dhHxy6rjp423nbcwA2AsULYblJ8+qXZGxi1qQNlRh fo=; b=LZaDCHa1SmO41mZHcMZAqn6/EyY7/5vDnJZQiXRqQkfiNSuu0qVdvKK1s t4hhzkzm3bR+aNQ/1zrPcONWUoS7N1IaVy1Cuj2ftVJfnTixT8g1eZoOaXrLgU7F /KEdfxd2yHtvW5ul7DFj9DaRySI1hMfx+aTW2ZuUZHwlhhCLQFIKK3SGcrSPmbw6 RUrj1GkKvhvCD8IE2o3TJAQOoGlkhsa6dj8HuaIC2KTE+ERLQ/E89/L1j+EJ0fP/ ZJ6o/C136GtdBvx6Ankqx02TjIVjhIHG6uN33NRYM3Rb9omFeVmtdTLJYGy0m2O1 asl5xYl4lxxtZafiBAg15v4+zTBpw==
X-ME-Sender: <xms:zSTCXZLVCBcClpAf_eeFaCiN9zd7TL4PMLHU-1kZlG5WN5LTip9Uqw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudduiedgfeekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhk ucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinh ephhhtthhpfegrnhguqhhprggtkhgurhgrfhhtshhtohhthhgrthhprhhotggvshhsrghs figvlhhlrdgrshdpghhithhhuhgsrdgtohhmpdhmnhhothdrnhgvthenucfkphepuddule drudejrdduheekrddvhedunecurfgrrhgrmhepmhgrihhlfhhrohhmpehmnhhothesmhhn ohhtrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:zSTCXQE6bMzdFj5AdkmIZ-BiLzrro5d_8jM2pQ8fZKPCUKj94E3svA> <xmx:zSTCXQsPJqvtrgxYgvSd287Nrd4u9EhcAJPRs1XEGslkELqiHH9MPQ> <xmx:zSTCXftNqnf33jJASVs1C79NCCQMQ0knjrjCkjMMWfGAN1iHeu5DUA> <xmx:ziTCXWI_aHSqqAdNbserlt87roxTPoQmmkmDNZO3sFj9tVebFj5f2Q>
Received: from macbook-pro.mnot.net (unknown [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id 54AD33060074; Tue,  5 Nov 2019 20:41:32 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <CAJ_4DfQocLyL=3j_xDS_b5Jj_U62Dt8wH=Ymi6tEKHJwcwVJtA@mail.gmail.com>
Date: Wed, 6 Nov 2019 12:41:27 +1100
Cc: IETF QUIC WG <quic@ietf.org>, Lars Eggert <lars@eggert.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <9DDD10B1-424F-4A62-837E-A93EA7594781@mnot.net>
References: <6A43BEC7-F9DE-40C9-BF70-BF1618EAFE01@mnot.net> <CAJ_4DfQocLyL=3j_xDS_b5Jj_U62Dt8wH=Ymi6tEKHJwcwVJtA@mail.gmail.com>
To: Ryan Hamilton <rch@google.com>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/m5GdNyP081fz9T22IoBLchpzRyk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 06 Nov 2019 01:41:49 -0000

Hi Ryan,

I think our intent was that it's an open issue, but I see that we =
haven't captured that in the current issues list. Good catch; let's go =
ahead and open one.

Cheers,


> On 6 Nov 2019, at 12:35 pm, Ryan Hamilton <rch@google.com> wrote:
>=20
> For QPACK and Recovery, this sounds great to me. For  HTTP/3, as I =
understand it, we still have a design team working on priorities. Can =
you clarify how this effort is affected by the late stage process? (Or =
is is basically unaffected as it is an open issue?)
>=20
> On Tue, Nov 5, 2019 at 5:02 PM Mark Nottingham <mnot@mnot.net> wrote:
> Previously, we've moved to the 'late-stage process' documented at [1] =
for the Transport and TLS drafts. The chairs and editors now feel that =
it's time to move the Recovery, HTTP/3, and QPACK drafts to that process =
as well.
>=20
> As before, this is because we're getting to a stage we feel the =
documents would benefit from slower and slightly more formal process, so =
that the rate of change is not so high, changes that do occur are =
well-vetted, and the documents get closer to reflecting consensus in the =
working group.
>=20
> If we do this, we're saying that we have gained consensus on what =
remains in these documents, excepting their outstanding issues. As per =
our charter:
>=20
> """
> 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.
> """
>=20
> That doesn't mean that new issues can't be raised against those =
drafts. However, new issues against them will be judged for whether they =
contain new information (in particular, security or interoperability =
impact), a clear technical defect, or have significant (in the judgement =
of the chairs) support for further discussion. If the issue isn't =
well-described or atomic, it may be closed with a request to refactor, =
or refactored for you.
>=20
> Again, this does not affect editorial issues.
>=20
> Practically speaking, it means that new issues will be triaged by the =
Chairs -- not the editors (although they can still "claim" purely =
editorial issues) -- and those that don't meet the criteria above will =
be closed. Those that do will be labeled (again, by the Chairs only) as =
`design`.
>=20
> It also means that all of the closed `design` issues against these =
drafts will be marked as `has-consensus`. Additionally, the `quicv2` =
issues against them will be closed and marked `has-consensus`.
>=20
> The issues that will be labeled `has-consensus` (and closed, if still =
open) are listed here:
>=20
> =
https://github.com/quicwg/base-drafts/issues?q=3Dis%3Aissue+is%3Aclosed+la=
bel%3Adesign+-label%3Ahas-consensus+-label%3A-transport+-label%3A-tls
>=20
> We believe that all of these issues have been discussed and the group =
has formed consensus on them; this only formalises that.
>=20
> If you have concerns or questions, please discuss them on-list; =
barring pushback, we'll adopt this on 15-Nov-2019.
>=20
> Cheers,
>=20
> 1. =
https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md#late-sta=
ge-process
>=20
> --
> Mark and Lars, QUIC WG Chairs
>=20

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


From nobody Tue Nov  5 18:11:10 2019
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 7B9E6120236 for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 18:11:09 -0800 (PST)
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_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 xc0mvATnyW9u for <quic@ietfa.amsl.com>; Tue,  5 Nov 2019 18:11:06 -0800 (PST)
Received: from mail-lj1-x22c.google.com (mail-lj1-x22c.google.com [IPv6:2a00:1450:4864:20::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 4319A120154 for <quic@ietf.org>; Tue,  5 Nov 2019 18:11:06 -0800 (PST)
Received: by mail-lj1-x22c.google.com with SMTP id e9so10882861ljp.13 for <quic@ietf.org>; Tue, 05 Nov 2019 18:11:06 -0800 (PST)
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=08rrQjK51oQw8ytW6wUrBK2mxABbOBDNLwJDSIUFNLA=; b=QfOdsNI7t3nax1dx6k/Ve8oUWIB8wwIrQPLbykb3LsXRGJpEpb9P7NGio6EWw1ZtpO Uny3RpvQnZSwTN8ggD2F0BuooDx8HQtr2QuHaNIhqnq3sOYw90pYM5dHUS4BIg6/J5aM xP2YTD3pFgE32CRTuT7D78QDgyB0zfQiIEUMJafj+CPKZBfAb64c9jdlwgkdmZoeiVYT MDmReI2cJJVS5/BEm2iYp/DSbNzEivLgL4qSBZ79DtRkIxQJAnerwe136VX29AL4VvNM 6T3xHlyjYxdlKZxiwh99AgyTvZ2Otnodli6GE2PsCQUAbFvZlVrPfZbkgG7ZKBwKNx1Q pSFw==
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=08rrQjK51oQw8ytW6wUrBK2mxABbOBDNLwJDSIUFNLA=; b=fdjZeaY8yUZI5WGwKkS0ydWtpy3yXS9ElLf9KVAdK2vIRYGUoGb0NUkTva/IfdGpJT oZFMcoeG5q1kCj2bIkQn/pToXLb4albOQBhXLtrNyssdVw+1mv6KrMkw93MXszvG+y3t DhGcxEV/x+BhE5hWKgluwBe9ZQ2XM61BEHGxUEI4gFW9PVy1iGR/Pplru4BG0Vt4RN7Z e/TuD0gfyh1K3jHWY74M1Np90pJOnuilL1Mekh5wfISTq+kLqAG11mWIvQ0mcNvfGbT3 5PmWvDsH6Llt/0pqBKVsLeXIoMPis3/BActe2cz9p7u3QyGDylBlfVU3QasxxJB2xyg+ 06gg==
X-Gm-Message-State: APjAAAVw9X+yb0KMsc5T0iq5OgmlRlHbQOKcAJ3+M6aPD8lMEM4GZrul trcFiolizZlQi6fudoybUQPqIuuihALvCY3pF30=
X-Google-Smtp-Source: APXvYqxrJWR11AJdHOIZAtP/bZ7W9bPXs01/n6RcPkiYBpkj2nKj79pud1lYrxZvG+ATGvFLox8hn/6IaI4X6R/O4aQ=
X-Received: by 2002:a2e:481:: with SMTP id a1mr25589908ljf.209.1573006264568;  Tue, 05 Nov 2019 18:11:04 -0800 (PST)
MIME-Version: 1.0
References: <3218A80B-DAFD-43EF-8200-F99C660DF9C9@mnot.net> <5557f717-ae03-46a2-aa9f-54f019a07533@www.fastmail.com> <CA+9kkMBbuG+4309XfZoVb69Pz_s3=RPv2JWZS8zrkVFBkDMJuw@mail.gmail.com> <614379f7e12f46c6b38b7928e999cbab@ustx2ex-dag1mb5.msg.corp.akamai.com> <CAPDSy+6PHwfVReNsAFMHE3KsvM2K_ACD7sUtqikri7oG-QGfLg@mail.gmail.com> <E68585EA-E67A-4C4D-8BE3-5E5880B24056@akamai.com> <CACpbDccE4OubiRQAAUyxthrmtdQJsaSKNmuV+HkFiJKXCJtOow@mail.gmail.com> <HE1PR07MB3306A309F29ED901A2957D1D9B7E0@HE1PR07MB3306.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR07MB3306A309F29ED901A2957D1D9B7E0@HE1PR07MB3306.eurprd07.prod.outlook.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Tue, 5 Nov 2019 18:10:53 -0800
Message-ID: <CACpbDceF2mbVc63CKHNYbUDwdpJ2eMWgmoqkqbAkBwBxJ8g_pQ@mail.gmail.com>
Subject: Re: Proposed response to the 3GPP Liaison Statement
To: "Flinck, Hannu (Nokia - FI/Espoo)" <hannu.flinck@nokia-bell-labs.com>
Cc: "Salz, Rich" <rsalz@akamai.com>, David Schinazi <dschinazi.ietf@gmail.com>, Ted Hardie <ted.ietf@gmail.com>, "Lubashev, Igor" <ilubashe@akamai.com>,  Martin Thomson <mt@lowentropy.net>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a110310596a40fb5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/e8v7szkmtuM8iTxMLI26yFnll_4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 06 Nov 2019 02:11:09 -0000

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

Hannu,

The request from 3GPP was about a non-HTTP use case.

- jana

On Tue, Nov 5, 2019 at 1:12 AM Flinck, Hannu (Nokia - FI/Espoo) <
hannu.flinck@nokia-bell-labs.com> wrote:

> 3GPP is using HTPP very well in their use case (see more in 3GPP 29.500, Technical
> Realization of Service Based Architecture.). Insisting focus on HTTP in
> the response is not helpful, but confusing instead.
>
>
>
> Best regards
>
> Hannu
>
>
>
> *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of *Jana Iyengar
> *Sent:* Tuesday, November 5, 2019 2:51 AM
> *To:* Salz, Rich <rsalz@akamai.com>
> *Cc:* David Schinazi <dschinazi.ietf@gmail.com>; Ted Hardie <
> ted.ietf@gmail.com>; Lubashev, Igor <ilubashe@akamai.com>; Martin Thomson
> <mt@lowentropy.net>; IETF QUIC WG <quic@ietf.org>
> *Subject:* Re: Proposed response to the 3GPP Liaison Statement
>
>
>
> The response looks sensible and accurate.
>
> I would suggest just one change: move the point about HTTP/3 focus (maybe
> the last two paras) to the top of the response, adding to it that the QUIC
> wg is currently chartered to focus on HTTP. Without getting into the use
> case that they are trying to fit QUIC into, it's difficult to understand
> the importance of the loss bits. And we surely do not want to block QUICv1
> trying to understand that use case.
>
>
>
> On Thu, Oct 31, 2019 at 3:57 PM Salz, Rich <rsalz@akamai.com> wrote:
>
> Maybe we should suggest that they write an I-D for what they think their
> requirements are?
>
>

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

<div dir=3D"ltr">Hannu,<div><br></div><div>The request from 3GPP was about =
a non-HTTP use case.</div><div><br></div><div>- jana</div></div><br><div cl=
ass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Nov 5, 20=
19 at 1:12 AM Flinck, Hannu (Nokia - FI/Espoo) &lt;<a href=3D"mailto:hannu.=
flinck@nokia-bell-labs.com">hannu.flinck@nokia-bell-labs.com</a>&gt; wrote:=
<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8=
ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"FI">
<div class=3D"gmail-m_4390856408518304648WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">3GPP is using HTPP very well in=
 their use case (see more in 3GPP 29.500,
</span><span lang=3D"EN-US">Technical Realization of Service Based Architec=
ture.</span><span lang=3D"EN-US">). Insisting focus on HTTP in the response=
 is not helpful, but confusing instead.
<u></u><u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Best regards<u></u><u></u></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hannu <u></u>
<u></u></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><u></u>=C2=A0<u></u></span></p>
<p class=3D"MsoNormal"><b><span lang=3D"EN-US">From:</span></b><span lang=
=3D"EN-US"> QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_bl=
ank">quic-bounces@ietf.org</a>&gt;
<b>On Behalf Of </b>Jana Iyengar<br>
<b>Sent:</b> Tuesday, November 5, 2019 2:51 AM<br>
<b>To:</b> Salz, Rich &lt;<a href=3D"mailto:rsalz@akamai.com" target=3D"_bl=
ank">rsalz@akamai.com</a>&gt;<br>
<b>Cc:</b> David Schinazi &lt;<a href=3D"mailto:dschinazi.ietf@gmail.com" t=
arget=3D"_blank">dschinazi.ietf@gmail.com</a>&gt;; Ted Hardie &lt;<a href=
=3D"mailto:ted.ietf@gmail.com" target=3D"_blank">ted.ietf@gmail.com</a>&gt;=
; Lubashev, Igor &lt;<a href=3D"mailto:ilubashe@akamai.com" target=3D"_blan=
k">ilubashe@akamai.com</a>&gt;; Martin Thomson &lt;<a href=3D"mailto:mt@low=
entropy.net" target=3D"_blank">mt@lowentropy.net</a>&gt;; IETF QUIC WG &lt;=
<a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic@ietf.org</a>&gt;<br=
>
<b>Subject:</b> Re: Proposed response to the 3GPP Liaison Statement<u></u><=
u></u></span></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">The response looks sensible and accurate.<br>
<br>
I would suggest just one change: move the point about HTTP/3 focus (maybe t=
he last two paras) to the top of the response, adding to it that the QUIC w=
g is currently chartered to focus on HTTP. Without getting=C2=A0into the us=
e case that they are trying to fit QUIC
 into, it&#39;s difficult to understand the importance of the loss bits. An=
d we surely do not want to block QUICv1 trying to understand that use case.=
<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Thu, Oct 31, 2019 at 3:57 PM Salz, Rich &lt;<a hr=
ef=3D"mailto:rsalz@akamai.com" target=3D"_blank">rsalz@akamai.com</a>&gt; w=
rote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-top:none;border-right:none;border-bottom:none;b=
order-left:1pt solid rgb(204,204,204);padding:0cm 0cm 0cm 6pt;margin-left:4=
.8pt;margin-right:0cm">
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt">Maybe we should suggest=
 that they write an I-D for what they think their requirements are?<br>
<br>
<u></u><u></u></p>
</blockquote>
</div>
</div>
</div>

</blockquote></div>

--000000000000a110310596a40fb5--


From nobody Wed Nov  6 01:53:57 2019
Return-Path: <statements@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 07156120810; Wed,  6 Nov 2019 01:53:57 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 8bit
From: Liaison Statement Management Tool <statements@ietf.org>
To: <georg.mayer.huawei@gmx.com>, <3GPPLiaison@etsi.org>
Cc: =?utf-8?q?Mirja_K=C3=BChlewind?= <ietf@kuehlewind.net>, Mark Nottingham <mnot@mnot.net>, QUIC Discussion List <quic@ietf.org>, Lars Eggert <lars@eggert.org>, Magnus Westerlund <magnus.westerlund@ericsson.com>, Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Subject: New Liaison Statement, "Response to questions about QUIC network level troubleshooting capabilities"
X-Test-IDTracker: no
X-IETF-IDTracker: 6.110.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <157303403695.27429.14590132790034125800.idtracker@ietfa.amsl.com>
Date: Wed, 06 Nov 2019 01:53:56 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/_L4FrhBwN8Snuo0xRK-5LCj84WI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 06 Nov 2019 09:53:57 -0000

Title: Response to questions about QUIC network level troubleshooting capabilities
Submission Date: 2019-11-05
URL of the IETF Web page: https://datatracker.ietf.org/liaison/1661/

From: Mark Nottingham <mnot@mnot.net>
To: georg.mayer.huawei@gmx.com,3GPPLiaison@etsi.org
Cc: Mark Nottingham <mnot@mnot.net>,QUIC Discussion List <quic@ietf.org>,Mirja KÃ¼hlewind <ietf@kuehlewind.net>,Lars Eggert <lars@eggert.org>,Magnus Westerlund <magnus.westerlund@ericsson.com>,Gonzalo Camarillo <gonzalo.camarillo@ericsson.com>
Response Contacts: Lars Eggert <lars@eggert.org>,Mark Nottingham <mnot@mnot.net>
Technical Contacts: 
Purpose: In response

Referenced liaison: LS on 3GPP CT WG4 feedback on QUIC network level troubleshooting capabilities (https://datatracker.ietf.org/liaison/1655/)

Body: Thank you for your input to our specifications.

Regarding the encryption of headers in addition to payload, this was a conscious design decision by the Working Group. Transport header encryption prevents modification by middleboxes, thereby avoiding ossification of the protocol, and also makes traffic analysis more difficult. The impact upon network operators was discussed extensively as part of that decision.

Regarding the spin bit, we believe that your characterisation is correct.

Regarding packet loss measurements, QUIC does support them, but only by the endpoints of communication -- not by third parties observing it. Keys may be exported by one of the endpoints to allow decoding of packet traces (e.g., with Wireshark), but that is not part of the QUIC standard.

Regarding performance analysis, it would be helpful if you described your use case in more detail. However, it's important to know that the Working Group decided early on that QUICv1 would focus on the use case of HTTP/3.

In turn, HTTP standardisation focuses primarily on the Web browsing use case; while we acknowledge that there are other uses of the protocol, and we accommodate them where possible, we cannot change the protocol in ways that harms that use. Exposing transport metadata would likely do so.

Kind regards,

Mark Nottingham and Lars Eggert, QUIC Working Group chairs
Attachments:

No document has been attached


From nobody Wed Nov  6 07:59:38 2019
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 6ED00120869 for <quic@ietfa.amsl.com>; Wed,  6 Nov 2019 07:59:36 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 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] 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 Jm8IW8B1fdHw for <quic@ietfa.amsl.com>; Wed,  6 Nov 2019 07:59:32 -0800 (PST)
Received: from NAM03-DM3-obe.outbound.protection.outlook.com (mail-dm3nam03on071e.outbound.protection.outlook.com [IPv6:2a01:111:f400:fe49::71e]) (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 DFF3E1200B3 for <quic@ietf.org>; Wed,  6 Nov 2019 07:59:31 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Hpp9hguCEZ6TCIHQNeSKjuf7/9gokqrrxbbHAasf+u1Q+Nmotm5p8HRPKOMARM13Ixt/jNyWvyYfUWWF0BT5eDeqIL+2Z+kw8lUGO5Ct8OA0H3JQ4oQpYvTukUdVDR5PFXQBaL6wX314z8/5wb3ZyXVjR6M1txsHGjIQYFt877++h2Nq+4eGkXtbbadUHIYqFwKB84uMTu9VnJQr5eQbdEPNreraHfYySkpvh2SPHbvLCOM5ZkPJvfsTl+C75IU68sxKCUvYShKpFnfOvOe5mAgOGwgRre6IKgtuMicQPHMpynA87oZl2hJ9DWJdNyWjjSLbdvcgbSdJRGtBq3Q08Q==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ky/ts2hG5dVO92kk6uBTvuJ/BJzvP2LsIMhUxnk4ZuQ=; b=M4ddrduXbnRgaGQnqTCUhX4g/E/ACr8ROzdPAuGsbhGWBlG+SyXKRUsq0XHd3nVhqp4ZfgKrstGolgdOAm2YbYj3tHxVPyxOpyeBgWz1VLAjVpa6r/Qpd1Ndg3LPq4rLGC8kRRlfUMV/6/q4msPaF9thWrm2HsnLdaA2skTeylhGj/kdRP6SFag0UZ9Cds77IPH/E2H4m8rPpM9zjJyYfXq/kKKuK/Dx7BJSSvRGmtB6Qf9rI3h8EZ2eWteb9LBpkh2rGWDOxtkAajmwKzN5VhaCwtakZEwt4hP55m062GeAh/q9fnp0pjcbpJAL7mUhw3ZSHeGrsAhlCTtF24N6dA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=evequefou.be; dmarc=pass action=none header.from=evequefou.be; dkim=pass header.d=evequefou.be; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector2-evequefou-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=ky/ts2hG5dVO92kk6uBTvuJ/BJzvP2LsIMhUxnk4ZuQ=; b=UvNrIasP7dCZzi8//OjayYMo9sx1ieg+i8f0v9QP6/9bTq4lXNzNSaMrxo1tNJnZmtM/P/XAuKDvg7KOKkK/K8wX/KnA6lKqC6MAc82HZ1O7wpkJKelKiI209TqlA6TKR3xQhoLYIfqw943traO6M8aKUM9yOtbVEvtzAs6ZsoI=
Received: from BN6PR2201MB1700.namprd22.prod.outlook.com (10.161.152.144) by BN6PR2201MB1027.namprd22.prod.outlook.com (10.174.88.33) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2408.24; Wed, 6 Nov 2019 15:59:28 +0000
Received: from BN6PR2201MB1700.namprd22.prod.outlook.com ([fe80::7cb4:5e4e:334c:a737]) by BN6PR2201MB1700.namprd22.prod.outlook.com ([fe80::7cb4:5e4e:334c:a737%7]) with mapi id 15.20.2408.024; Wed, 6 Nov 2019 15:59:28 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Mark Nottingham <mnot@mnot.net>, Ryan Hamilton <rch@google.com>
CC: Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
Thread-Topic: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
Thread-Index: AQHVlD3tOlesd/HkOkytkq7/DuTcZKd9XIaAgAABmoCAAO734A==
Date: Wed, 6 Nov 2019 15:59:28 +0000
Message-ID: <BN6PR2201MB1700F28E83B7E752473192D7DA790@BN6PR2201MB1700.namprd22.prod.outlook.com>
References: <6A43BEC7-F9DE-40C9-BF70-BF1618EAFE01@mnot.net> <CAJ_4DfQocLyL=3j_xDS_b5Jj_U62Dt8wH=Ymi6tEKHJwcwVJtA@mail.gmail.com> <9DDD10B1-424F-4A62-837E-A93EA7594781@mnot.net>
In-Reply-To: <9DDD10B1-424F-4A62-837E-A93EA7594781@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: [2600:2b00:931f:a301:90ae:6813:89d6:cddc]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 81321a43-7a42-482e-9354-08d762d24e06
x-ms-traffictypediagnostic: BN6PR2201MB1027:
x-ms-exchange-purlcount: 3
x-microsoft-antispam-prvs: <BN6PR2201MB10275EE35C624806FCEE6B62DA790@BN6PR2201MB1027.namprd22.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 02135EB356
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(396003)(346002)(366004)(136003)(376002)(39830400003)(189003)(199004)(13464003)(26424002)(186003)(256004)(53546011)(110136005)(46003)(14444005)(11346002)(446003)(14454004)(7736002)(74316002)(81166006)(81156014)(305945005)(8676002)(6436002)(71200400001)(229853002)(966005)(25786009)(5660300002)(6116002)(52536014)(2906002)(76176011)(486006)(476003)(102836004)(508600001)(71190400001)(4326008)(8936002)(33656002)(76116006)(55016002)(9686003)(66556008)(99286004)(64756008)(316002)(6246003)(66476007)(66946007)(66446008)(6306002)(7696005)(6506007)(86362001)(54906003); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR2201MB1027; H:BN6PR2201MB1700.namprd22.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: AQwllBTNjD/duxfqIQW7pAFCgRMtKzP1vljHsgZpy6vvTf7ErljBJ+5nbW5QcNNBHhDOTHXz0uZyPkUWCeq7mg6BeO4ra6UEuJZBzx6IUe93DzWUecaixL1VDbNZaKKnR3s1xUjeztQZtQMAL+2P6hE79JZnMu1YsMWbernjM0uLgBu9YXu0HiU047sbtTW/WZKWzmXPdyjykfMlC5rTg3T/edSeaQ1xrlvnfP0a12jJkSx06FwuphrMMJjj3KvTXHsuwSWREvHV5Ch8WWAvSeGcAuMevl4EtynDrUONgPrurqB5ofsDe9wdMptrqHSqzl5rAH44rRQV4s762O+YTE+ZAvYeEyjmgw7bdImQG4O6q60pi+LUsKUoJkAXTo3mz1uf/IiH+kQdWEZk50by3JMIy0+CxpTo2jMa4aczTMc8D0diky2g5eoRtSRf+CFhZns6JYUJBH858F0v3mu01qTZKEVkXHVDZPTzAbFptzh0LIcwYLA4ukGH8JF0QtKX
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: 81321a43-7a42-482e-9354-08d762d24e06
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Nov 2019 15:59:28.6683 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ykJw3YPXRwpA6ncfQE/Lkun2Av5HeZdNh570OZXKkfCW2tS7JxkYYR03E7243rx9zqU7dqQUFT63Uky2Lcbsrw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR2201MB1027
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ibF0QAdgMdt7te_07GlpeILnFs8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 06 Nov 2019 15:59:36 -0000

Also, the design team is an HTTP design team focused on having a coherent s=
tory around prioritization across HTTP versions.  They/we might propose tex=
t back to HTTP/3, or they might define HTTP/3 extensions in an HTTPbis docu=
ment, or they might do something else entirely.  This working group should =
consider the design team output if it comes before the document is done, an=
d if not will need to make a decision about whether to proceed without it.

-----Original Message-----
From: QUIC <quic-bounces@ietf.org> On Behalf Of Mark Nottingham
Sent: Tuesday, November 5, 2019 8:41 PM
To: Ryan Hamilton <rch@google.com>
Cc: Lars Eggert <lars@eggert.org>; IETF QUIC WG <quic@ietf.org>
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the L=
ate-Stage Process

Hi Ryan,

I think our intent was that it's an open issue, but I see that we haven't c=
aptured that in the current issues list. Good catch; let's go ahead and ope=
n one.

Cheers,


> On 6 Nov 2019, at 12:35 pm, Ryan Hamilton <rch@google.com> wrote:
>=20
> For QPACK and Recovery, this sounds great to me. For  HTTP/3, as I unders=
tand it, we still have a design team working on priorities. Can you clarify=
 how this effort is affected by the late stage process? (Or is is basically=
 unaffected as it is an open issue?)
>=20
> On Tue, Nov 5, 2019 at 5:02 PM Mark Nottingham <mnot@mnot.net> wrote:
> Previously, we've moved to the 'late-stage process' documented at [1] for=
 the Transport and TLS drafts. The chairs and editors now feel that it's ti=
me to move the Recovery, HTTP/3, and QPACK drafts to that process as well.
>=20
> As before, this is because we're getting to a stage we feel the documents=
 would benefit from slower and slightly more formal process, so that the ra=
te of change is not so high, changes that do occur are well-vetted, and the=
 documents get closer to reflecting consensus in the working group.
>=20
> If we do this, we're saying that we have gained consensus on what remains=
 in these documents, excepting their outstanding issues. As per our charter=
:
>=20
> """
> Note that consensus is required both for changes to the current protocol =
mechanisms and retention of current mechanisms. In particular, because some=
thing is in the initial document set does not imply that there is consensus=
 around the feature or around how it is specified.
> """
>=20
> That doesn't mean that new issues can't be raised against those drafts. H=
owever, new issues against them will be judged for whether they contain new=
 information (in particular, security or interoperability impact), a clear =
technical defect, or have significant (in the judgement of the chairs) supp=
ort for further discussion. If the issue isn't well-described or atomic, it=
 may be closed with a request to refactor, or refactored for you.
>=20
> Again, this does not affect editorial issues.
>=20
> Practically speaking, it means that new issues will be triaged by the Cha=
irs -- not the editors (although they can still "claim" purely editorial is=
sues) -- and those that don't meet the criteria above will be closed. Those=
 that do will be labeled (again, by the Chairs only) as `design`.
>=20
> It also means that all of the closed `design` issues against these drafts=
 will be marked as `has-consensus`. Additionally, the `quicv2` issues again=
st them will be closed and marked `has-consensus`.
>=20
> The issues that will be labeled `has-consensus` (and closed, if still ope=
n) are listed here:
>=20
> https://github.com/quicwg/base-drafts/issues?q=3Dis%3Aissue+is%3Aclosed+l=
abel%3Adesign+-label%3Ahas-consensus+-label%3A-transport+-label%3A-tls
>=20
> We believe that all of these issues have been discussed and the group has=
 formed consensus on them; this only formalises that.
>=20
> If you have concerns or questions, please discuss them on-list; barring p=
ushback, we'll adopt this on 15-Nov-2019.
>=20
> Cheers,
>=20
> 1. https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md#late=
-stage-process
>=20
> --
> Mark and Lars, QUIC WG Chairs
>=20

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


From nobody Wed Nov  6 10:29:40 2019
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 C763C12018D for <quic@ietfa.amsl.com>; Wed,  6 Nov 2019 10:29:38 -0800 (PST)
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] 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 4uS8olHUtDY0 for <quic@ietfa.amsl.com>; Wed,  6 Nov 2019 10:29:35 -0800 (PST)
Received: from NAM03-CO1-obe.outbound.protection.outlook.com (mail-eopbgr790137.outbound.protection.outlook.com [40.107.79.137]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 68A3A120901 for <quic@ietf.org>; Wed,  6 Nov 2019 10:29:35 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=M6gSmUwCMYhfnH3LArBLH7SAQsRK5ltbAXIoFYNKY7lwxtfHv68/zAHrgwFuTfrV/sV949LYMFF6RE+ndA7L98elnYUBKBZSy7JqtCZJdB4DB/PAgZLgmMcOqlLx6Vgd+AWCZg3DjW0LE5tWEa3806gXDvw9viHcY/Wu1nJqbG609IsnjDMFjSptvOkMRdVjFRlDWqkzRBdsexeEcHYDLVkF+2RBozegHojcFVifpoqEaNV3IbvANkAhJwPUX3rL4hl/UW51a5Vy9U+uB6uRbJr+fI6lWZ1LO3R9jrRinjURB/EOxqrh8DnF0sJJqRHuU445fRvNC6uq9u7bPfK7VQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=eYRYwqk1rPVCu8QpEvkG34x2xVcEOI7TCh1LTL8jWCE=; b=HlyJya5xgSYBKV3Sg939JIGdyuZX3jeSbTD4sHE9l0uxhckJ4XZhlV6gjRU/urba+pQzAx03+LGeiBFTcPcI4c+u9YxsZI1oN6eQS1XTUfW/v6AkgR/uAd1Yh+0BiurlcM8DmaODpNUF7Qdc+sJsny6kf8ShawD4aJ7ir7y0bdrK11Tm1t/Vb4pwsjvbblXdGjjtSPDoxJ57vAJ0x6Jg4GsW/I7hcAoulphHa8DAQDdNgIk8Bumynt7UExcAjUIcSUCcTnb4CpXseY1A/tpOAOxcpEV4PMS6uxoWhXhkIfzBk9WPbvMi2VWXLfmUnI3Kz9pouRLAzzv8AfO6J8tZjA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=evequefou.be; dmarc=pass action=none header.from=evequefou.be; dkim=pass header.d=evequefou.be; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector2-evequefou-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=eYRYwqk1rPVCu8QpEvkG34x2xVcEOI7TCh1LTL8jWCE=; b=gx914GMk/gm8cCL1tJYNAbBOMwdXR2HNmVNZTuYQipOmq4r8RA78fJEpD8ftCiYG4NLTQgDmHblu81YA3GofQSkepGdFX/pvKn4T1lyLm9iYo7r7pgAZjzLgzwl94S6C3Y5tTwlwG7dl/8eAjIfk0+iW4dzzAASw4+pssaS5Hl8=
Received: from BN6PR2201MB1700.namprd22.prod.outlook.com (10.161.152.144) by BN6PR2201MB1377.namprd22.prod.outlook.com (10.174.82.22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2408.24; Wed, 6 Nov 2019 18:29:32 +0000
Received: from BN6PR2201MB1700.namprd22.prod.outlook.com ([fe80::7cb4:5e4e:334c:a737]) by BN6PR2201MB1700.namprd22.prod.outlook.com ([fe80::7cb4:5e4e:334c:a737%7]) with mapi id 15.20.2408.024; Wed, 6 Nov 2019 18:29:31 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: David Schinazi <dschinazi.ietf@gmail.com>, QUIC <quic@ietf.org>
Subject: RE: QUIC Version Negotiation Extension
Thread-Topic: QUIC Version Negotiation Extension
Thread-Index: AQHVk06pHyyhhmroy0SVmtb9ABkIw6d+UXLg
Date: Wed, 6 Nov 2019 18:29:31 +0000
Message-ID: <BN6PR2201MB1700BB1DAD2872A2FA50059FDA790@BN6PR2201MB1700.namprd22.prod.outlook.com>
References: <CAPDSy+4wrhqejh9k8=G7W267EgcT5Z2sDK7ZBGKtNn5kkbXGfg@mail.gmail.com>
In-Reply-To: <CAPDSy+4wrhqejh9k8=G7W267EgcT5Z2sDK7ZBGKtNn5kkbXGfg@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: [2600:2b00:931f:a301:90ae:6813:89d6:cddc]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: db01aff8-6505-4d38-ce98-08d762e74434
x-ms-traffictypediagnostic: BN6PR2201MB1377:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <BN6PR2201MB13774307FAB9BF4DBFA3A763DA790@BN6PR2201MB1377.namprd22.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 02135EB356
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(979002)(366004)(396003)(39830400003)(136003)(376002)(346002)(53754006)(199004)(189003)(76176011)(7696005)(236005)(186003)(790700001)(46003)(2906002)(6116002)(7736002)(606006)(86362001)(74316002)(486006)(81166006)(8676002)(3480700005)(81156014)(476003)(99286004)(6246003)(5660300002)(33656002)(52536014)(25786009)(66476007)(55016002)(508600001)(64756008)(66556008)(66446008)(110136005)(9686003)(256004)(6306002)(54896002)(6506007)(102836004)(446003)(53546011)(11346002)(229853002)(8936002)(316002)(71200400001)(71190400001)(66946007)(76116006)(14454004)(6436002)(966005)(969003)(989001)(999001)(1009001)(1019001); DIR:OUT; SFP:1102; SCL:1; SRVR:BN6PR2201MB1377; H:BN6PR2201MB1700.namprd22.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: R7Z5C0K5NpEMf5T9Gq5XXm/OUsMZOwZdJK5kBGnq2gKGnyfH08xX726Hw8rOxH9/JZ90XGeg3YX0RrnyioW0kRpBwBAwqu8k49Do3fAOqe3l5lBpiYp5XnO8ByVDWfpH7Ua6zMrUPMpmt3rpjXHxorcY2Qoydu5L7nBkdWUxYJj9LFr+V3JzWTvstmlPKbiJdK7Qi1CkqWeLVpBn4QrGWUz+ptMEPGBFpvjs+S5oNSMDhzFtA4qcmL4KeErIKQ1E+4mZzFMP4OWrehXEB1AcSTyk/WFR3q1f+vBSQNv/+PXaaDnejKag7ymLv2HaVf6vBPy8IIZTipPGGASq7QzXfMwA/QxPfG8dLH+0c1F7Mnc9NIa9yLqc3Y7AGn/wcoSY8hgmaYVMNCbTjT2ApUbFmQEyCzKfisib2NBkeuyuSdGpols+y9E9kchA3f1rCkWhBV/kg0OAV7wsrshzmp78fbtcRxUCeX8FmlirCMx8KEI=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BN6PR2201MB1700BB1DAD2872A2FA50059FDA790BN6PR2201MB1700_"
MIME-Version: 1.0
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: db01aff8-6505-4d38-ce98-08d762e74434
X-MS-Exchange-CrossTenant-originalarrivaltime: 06 Nov 2019 18:29:31.4874 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: ruPzDzuqtyQiRNA19o1+P2XXv92jfoNIU665TylpKFSTtVdgHFcyo2OIkPg7CTr/i1LlJUeY6r3so2OaquRexw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR2201MB1377
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/0iAgoaoDaKyY_hsSYyyODe8o6HI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 06 Nov 2019 18:29:39 -0000

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

U29tZSBub3RlczoNCg0KICAqICAgU2VjdGlvbiAzOiAg4oCcVmVyc2lvbiBuZWdvdGlhdGlvbiB0
YWtlcyBwbGFjZSBhZnRlciB0aGUgcmV0cnkgY3ljbGUgaXMgb3Zlci7igJ0gIFRoaXMgaXMgb25s
eSBwb3NzaWJsZSBmb3IgY29tcGF0aWJsZSB2ZXJzaW9uczsgaWYgdGhlIHNlcnZlciBkb2VzIG5v
dCBzdXBwb3J0IHRoZSB2ZXJzaW9uIHRoZSBjbGllbnQgYXR0ZW1wdGVkLCBpdCBvYnZpb3VzbHkg
Y2Fubm90IHNlbmQgYSBSZXRyeSBwYWNrZXQgaW4gdGhhdCB2ZXJzaW9uLCBiZWNhdXNlIFJldHJ5
IHBhY2tldHMgYXJlIHZlcnNpb24tc3BlY2lmaWMuDQogICogICBTZWN0aW9uIDM6ICDigJxTZXJ2
ZXJzIG11c3QgcmV0YWluIHRoZSBhYmlsaXR5IHRvIHByb2Nlc3MgdGhlIEluaXRpYWwgcGFja2V0
IGZyb20gb2xkZXIgdmVyc2lvbnPigKYu4oCdICBObywgaXQgbWVhbnMgdGhhdCBpZiB0aGUgc2Vy
dmVyIHdhbnRzIHRvIGF2b2lkIGEgVk4gcGFja2V0LCBpdCBuZWVkcyB0byBiZSBhYmxlIHRvIHBy
b2Nlc3MgdGhlIEluaXRpYWwgcGFja2V0IGZyb20gdGhlIHZlcnNpb24gdGhlIGNsaWVudCB0cmll
ZC4NCiAgKiAgIFNlY3Rpb24gNDogIFJhdGhlciB0aGFuIHB1dHRpbmcgYSBjb3VudC1wcmVmaXhl
ZCBsaXN0IG9mIHZlcnNpb25zLCBwZXJoYXBzIGNvbnNpZGVyIGp1c3QgZW1iZWRkaW5nIHRoZSBW
TiBwYWNrZXQgcGF5bG9hZD8gIEl04oCZcyBlcXVpdmFsZW50LCBidXQgZWFzaWVyIHRvIGV4cGxh
aW4uDQogICogICBTZWN0aW9uIDc6ICBDbGVhcmx5IGl0IGlzIHBvc3NpYmxlIHRvIHBvc3NpYmxl
IHRvIGFkZCBuZXcgZnJhbWUgdHlwZXMgdG8gSW5pdGlhbCBwYWNrZXRzIGluIGEgZnV0dXJlIHZl
cnNpb24sIEkgdGhpbmsgd2hhdCB5b3UgbWVhbiB0byBzYXkgaXMgdGhhdCB0aGlzIGlzIGEgY2hh
bmdlIHRoYXQgd291bGQgYnJlYWsgY29tcGF0aWJpbGl0eSBiZXR3ZWVuIHZlcnNpb25zLg0KDQpB
cyBhIGdlbmVyYWwgc3RhdGVtZW50IG9uIHRoZSBkb2N1bWVudCwgeW91IGFzc3VtZSB0aHJvdWdo
b3V0IHRoYXQgYWxsIHZlcnNpb25zIGhhdmUgcGFja2V0IHR5cGVzLCBjb250YWluIHBhY2tldCB0
eXBlcyBjYWxsZWQgSW5pdGlhbCBhbmQgUmV0cnksIGFuZCB0aGF0IEluaXRpYWwgcGFja2V0cyBj
b250YWluIGZyYW1lcy4gIFRoZSBvZGRzIG9mIHRob3NlIHRoaW5ncyBiZWluZyB0cnVlIGFjcm9z
cyBRVUlDIHZlcnNpb25zIGlzIGxpa2VseSBoaWdoLCBidXQgdGhleeKAmXJlIG5vdCBpbnZhcmlh
bnRzLCBzbyB5b3UgY2Fu4oCZdCBhc3N1bWUgdGhlbSBoZXJlLiAgWW91IG5lZWQgdG8gc3RhdGUg
Z2VuZXJhbCBwcmluY2lwbGVzLCBhbmQgdGhlbiB1c2UgY29uY2VwdHMgZnJvbSBRVUlDdjEgYXMg
ZXhhbXBsZXMgb2YgdGhlIHByaW5jaXBsZS4NCg0KRm9yIGV4YW1wbGUsIHJhdGhlciB0aGFuIGRp
c2N1c3NpbmcgdmVyc2lvbiBjb21wYXRpYmlsaXR5IGluIHRlcm1zIG9mIEluaXRpYWwgcGFja2V0
cywgeW91IG1pZ2h0IHdhbnQgdG8gc2F5IHRoYXQgdmVyc2lvbnMgQSBhbmQgQiBhcmUg4oCcY29t
cGF0aWJsZeKAnSBpZiB0aGUgZmlyc3QgZmxpZ2h0IG9mIHBhY2tldHMgc2VudCBieSB0aGUgY2xp
ZW50IGluIHZlcnNpb24gQSBjYXJyaWVzIGVub3VnaCBpbmZvcm1hdGlvbiBmb3IgdGhlIHNlcnZl
ciB0byBnZW5lcmF0ZSB0aGUgY29ycmVzcG9uZGluZyBmbGlnaHQgaW4gdmVyc2lvbiBCLCB0aGUg
c2VydmVyIHNwZWFrcyB2ZXJzaW9uIEIsIGFuZCBpcyBhYmxlIHRvIHBhcnNlIGF0IGxlYXN0IHRo
ZSBmaXJzdCBmbGlnaHQgb2YgdmVyc2lvbiBBLg0KDQpBbHNvIG5vdCBkaXNjdXNzZWQgaXMgdGhl
IGNhc2Ugd2hlcmUgdGhlIHNlcnZlciBzcGVha3MgdmVyc2lvbihzKSB3aGljaCBhcmUgY29tcGF0
aWJsZSB3aXRoIHdoYXQgdGhlIGNsaWVudCBvZmZlcmVkLCBidXQgZG9lc27igJl0IHNwZWFrIHRo
ZSB2ZXJzaW9uIHRoZSBjbGllbnQgb2ZmZXJlZCwgZXZlbiBlbm91Z2ggdG8gZ2VuZXJhdGUgdGhl
IHJlc3BvbnNlLiAgV2l0aCB0aGUgcmlnaHQgZGVmaW5pdGlvbiBvZiDigJxjb21wYXRpYmxlLOKA
nSB0aGlzIGp1c3QgZmFsbHMgaW50byB0aGUg4oCcaW5jb21wYXRpYmxl4oCdIHBhdGggYW5kIHdv
cmtzIGZvciB0aGUgc2VydmVyLCBidXQgeW91IG5lZWQgdG8gY2FsbCBvdXQgdGhlIGZhY3QgdGhh
dCB0aGUgY2xpZW50IHNob3VsZG7igJl0IGNvbnNpZGVyIGl0IGFuIGVycm9yIGlmIHRoZSBzZXJ2
ZXIgdXNlcyB0aGUgaW5jb21wYXRpYmxlIHBhdGggYmV0d2VlbiB2ZXJzaW9ucyB0aGF0IHRoZSBj
bGllbnQgdGhpbmtzIGFyZSBjb21wYXRpYmxlLg0KDQpGcm9tOiBRVUlDIDxxdWljLWJvdW5jZXNA
aWV0Zi5vcmc+IE9uIEJlaGFsZiBPZiBEYXZpZCBTY2hpbmF6aQ0KU2VudDogTW9uZGF5LCBOb3Zl
bWJlciA0LCAyMDE5IDM6MzAgUE0NClRvOiBRVUlDIDxxdWljQGlldGYub3JnPg0KU3ViamVjdDog
UVVJQyBWZXJzaW9uIE5lZ290aWF0aW9uIEV4dGVuc2lvbg0KDQpIaSBldmVyeW9uZSwNCg0KRnJv
bSB0aGUgcmVjZW50IGRpc2N1c3Npb24gb24gbXVsdGlwbGUgUFJzLCBpdCBhcHBlYXJzIHRoYXQg
dGhlcmUgbWlnaHQgYmUgYSBuZWVkIGZvciBkb3duZ3JhZGUtc2FmZSBRVUlDIHZlcnNpb24gbmVn
b3RpYXRpb24sIGVhcmxpZXIgdGhhbiB3ZSBleHBlY3RlZC4NCg0KRUtSIGFuZCBJIHVwZGF0ZWQg
b3VyIGV4dGVuc2lvbiB0byBob3BlZnVsbHkgc3VpdCB0aGVzZSBuZWVkczoNCmh0dHBzOi8vdG9v
bHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1zY2hpbmF6aS1xdWljLXZlcnNpb24tbmVnb3RpYXRpb24t
MDINCg0KQ29tbWVudHMgd2VsY29tZSBoZXJlIG9yIG9uIHRoZSBHaXRIdWIgKGxpbmsgaW4gZHJh
ZnQpLg0KDQpUaGFua3MsDQpEYXZpZA0K

--_000_BN6PR2201MB1700BB1DAD2872A2FA50059FDA790BN6PR2201MB1700_
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
Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7
fQ0Kc3Bhbi5FbWFpbFN0eWxlMjANCgl7bXNvLXN0eWxlLXR5cGU6cGVyc29uYWwtY29tcG9zZTsN
Cglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30N
Ci5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtZmFt
aWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjgu
NWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0KZGl2LldvcmRT
ZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQovKiBMaXN0IERlZmluaXRpb25zICovDQpA
bGlzdCBsMA0KCXttc28tbGlzdC1pZDoxOTkxMzk4NzcyOw0KCW1zby1saXN0LXR5cGU6aHlicmlk
Ow0KCW1zby1saXN0LXRlbXBsYXRlLWlkczoxOTQ2NzQyMTYgNjc2OTg2ODkgNjc2OTg2OTEgNjc2
OTg2OTMgNjc2OTg2ODkgNjc2OTg2OTEgNjc2OTg2OTMgNjc2OTg2ODkgNjc2OTg2OTEgNjc2OTg2
OTM7fQ0KQGxpc3QgbDA6bGV2ZWwxDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsN
Cgltc28tbGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxl
dmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZh
bWlseTpTeW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWwyDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0
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
diBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlNvbWUgbm90ZXM6
PG86cD48L286cD48L3A+DQo8dWwgc3R5bGU9Im1hcmdpbi10b3A6MGluIiB0eXBlPSJkaXNjIj4N
CjxsaSBjbGFzcz0iTXNvTGlzdFBhcmFncmFwaCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjBpbjttc28t
bGlzdDpsMCBsZXZlbDEgbGZvMSI+PGI+U2VjdGlvbiAzOiZuYnNwOw0KPC9iPuKAnFZlcnNpb24g
bmVnb3RpYXRpb24gdGFrZXMgcGxhY2UgYWZ0ZXIgdGhlIHJldHJ5IGN5Y2xlIGlzIG92ZXIu4oCd
Jm5ic3A7IFRoaXMgaXMgb25seSBwb3NzaWJsZSBmb3IgY29tcGF0aWJsZSB2ZXJzaW9uczsgaWYg
dGhlIHNlcnZlciBkb2VzIG5vdCBzdXBwb3J0IHRoZSB2ZXJzaW9uIHRoZSBjbGllbnQgYXR0ZW1w
dGVkLCBpdCBvYnZpb3VzbHkgY2Fubm90IHNlbmQgYSBSZXRyeSBwYWNrZXQgaW4gdGhhdCB2ZXJz
aW9uLCBiZWNhdXNlIFJldHJ5IHBhY2tldHMNCiBhcmUgdmVyc2lvbi1zcGVjaWZpYy48bzpwPjwv
bzpwPjwvbGk+PGxpIGNsYXNzPSJNc29MaXN0UGFyYWdyYXBoIiBzdHlsZT0ibWFyZ2luLWxlZnQ6
MGluO21zby1saXN0OmwwIGxldmVsMSBsZm8xIj48Yj5TZWN0aW9uIDM6Jm5ic3A7DQo8L2I+4oCc
U2VydmVycyBtdXN0IHJldGFpbiB0aGUgYWJpbGl0eSB0byBwcm9jZXNzIHRoZSBJbml0aWFsIHBh
Y2tldCBmcm9tIG9sZGVyIHZlcnNpb25z4oCmLuKAnSZuYnNwOyBObywgaXQgbWVhbnMgdGhhdA0K
PGk+aWYgdGhlIHNlcnZlciB3YW50cyB0byBhdm9pZCBhIFZOIHBhY2tldDwvaT4sIGl0IG5lZWRz
IHRvIGJlIGFibGUgdG8gcHJvY2VzcyB0aGUgSW5pdGlhbCBwYWNrZXQgZnJvbSB0aGUgdmVyc2lv
biB0aGUgY2xpZW50IHRyaWVkLjxvOnA+PC9vOnA+PC9saT48bGkgY2xhc3M9Ik1zb0xpc3RQYXJh
Z3JhcGgiIHN0eWxlPSJtYXJnaW4tbGVmdDowaW47bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzEiPjxi
PlNlY3Rpb24gNDombmJzcDsNCjwvYj5SYXRoZXIgdGhhbiBwdXR0aW5nIGEgY291bnQtcHJlZml4
ZWQgbGlzdCBvZiB2ZXJzaW9ucywgcGVyaGFwcyBjb25zaWRlciBqdXN0IGVtYmVkZGluZyB0aGUg
Vk4gcGFja2V0IHBheWxvYWQ/Jm5ic3A7IEl04oCZcyBlcXVpdmFsZW50LCBidXQgZWFzaWVyIHRv
IGV4cGxhaW4uPG86cD48L286cD48L2xpPjxsaSBjbGFzcz0iTXNvTGlzdFBhcmFncmFwaCIgc3R5
bGU9Im1hcmdpbi1sZWZ0OjBpbjttc28tbGlzdDpsMCBsZXZlbDEgbGZvMSI+PGI+U2VjdGlvbiA3
OiZuYnNwOw0KPC9iPkNsZWFybHkgaXQgaXMgcG9zc2libGUgdG8gcG9zc2libGUgdG8gYWRkIG5l
dyBmcmFtZSB0eXBlcyB0byBJbml0aWFsIHBhY2tldHMgaW4gYSBmdXR1cmUgdmVyc2lvbiwgSSB0
aGluayB3aGF0IHlvdSBtZWFuIHRvIHNheSBpcyB0aGF0IHRoaXMgaXMgYSBjaGFuZ2UgdGhhdCB3
b3VsZCBicmVhayBjb21wYXRpYmlsaXR5IGJldHdlZW4gdmVyc2lvbnMuPG86cD48L286cD48L2xp
PjwvdWw+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPkFzIGEgZ2VuZXJhbCBzdGF0ZW1lbnQgb24gdGhlIGRvY3VtZW50LCB5
b3UgYXNzdW1lIHRocm91Z2hvdXQgdGhhdCBhbGwgdmVyc2lvbnMgaGF2ZSBwYWNrZXQgdHlwZXMs
IGNvbnRhaW4gcGFja2V0IHR5cGVzIGNhbGxlZCBJbml0aWFsIGFuZCBSZXRyeSwgYW5kIHRoYXQg
SW5pdGlhbCBwYWNrZXRzIGNvbnRhaW4gZnJhbWVzLiZuYnNwOyBUaGUgb2RkcyBvZiB0aG9zZSB0
aGluZ3MgYmVpbmcgdHJ1ZSBhY3Jvc3MgUVVJQw0KIHZlcnNpb25zIGlzIGxpa2VseSBoaWdoLCBi
dXQgdGhleeKAmXJlIG5vdCBpbnZhcmlhbnRzLCBzbyB5b3UgY2Fu4oCZdCBhc3N1bWUgdGhlbSBo
ZXJlLiZuYnNwOyBZb3UgbmVlZCB0byBzdGF0ZSBnZW5lcmFsIHByaW5jaXBsZXMsIGFuZCB0aGVu
IHVzZSBjb25jZXB0cyBmcm9tIFFVSUN2MSBhcyBleGFtcGxlcyBvZiB0aGUgcHJpbmNpcGxlLjxv
OnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Gb3IgZXhhbXBsZSwgcmF0aGVyIHRoYW4gZGlzY3Vzc2lu
ZyB2ZXJzaW9uIGNvbXBhdGliaWxpdHkgaW4gdGVybXMgb2YgSW5pdGlhbCBwYWNrZXRzLCB5b3Ug
bWlnaHQgd2FudCB0byBzYXkgdGhhdCB2ZXJzaW9ucyBBIGFuZCBCIGFyZSDigJxjb21wYXRpYmxl
4oCdIGlmIHRoZSBmaXJzdCBmbGlnaHQgb2YgcGFja2V0cyBzZW50IGJ5IHRoZSBjbGllbnQgaW4g
dmVyc2lvbiBBIGNhcnJpZXMgZW5vdWdoIGluZm9ybWF0aW9uDQogZm9yIHRoZSBzZXJ2ZXIgdG8g
Z2VuZXJhdGUgdGhlIGNvcnJlc3BvbmRpbmcgZmxpZ2h0IGluIHZlcnNpb24gQiwgdGhlIHNlcnZl
ciBzcGVha3MgdmVyc2lvbiBCLCBhbmQgaXMgYWJsZSB0byBwYXJzZSBhdCBsZWFzdCB0aGUgZmly
c3QgZmxpZ2h0IG9mIHZlcnNpb24gQS48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QWxzbyBub3Qg
ZGlzY3Vzc2VkIGlzIHRoZSBjYXNlIHdoZXJlIHRoZSBzZXJ2ZXIgc3BlYWtzIHZlcnNpb24ocykg
d2hpY2ggYXJlIGNvbXBhdGlibGUgd2l0aCB3aGF0IHRoZSBjbGllbnQgb2ZmZXJlZCwgYnV0IGRv
ZXNu4oCZdCBzcGVhayB0aGUgdmVyc2lvbiB0aGUgY2xpZW50IG9mZmVyZWQsIGV2ZW4gZW5vdWdo
IHRvIGdlbmVyYXRlIHRoZSByZXNwb25zZS4mbmJzcDsgV2l0aCB0aGUgcmlnaHQgZGVmaW5pdGlv
biBvZiDigJxjb21wYXRpYmxlLOKAnQ0KIHRoaXMganVzdCBmYWxscyBpbnRvIHRoZSDigJxpbmNv
bXBhdGlibGXigJ0gcGF0aCBhbmQgd29ya3MgZm9yIHRoZSBzZXJ2ZXIsIGJ1dCB5b3UgbmVlZCB0
byBjYWxsIG91dCB0aGUgZmFjdCB0aGF0IHRoZSBjbGllbnQgc2hvdWxkbuKAmXQgY29uc2lkZXIg
aXQgYW4gZXJyb3IgaWYgdGhlIHNlcnZlciB1c2VzIHRoZSBpbmNvbXBhdGlibGUgcGF0aCBiZXR3
ZWVuIHZlcnNpb25zIHRoYXQgdGhlIGNsaWVudCB0aGlua3MgYXJlIGNvbXBhdGlibGUuPG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxiPkZyb206PC9iPiBRVUlDICZsdDtxdWljLWJvdW5jZXNAaWV0
Zi5vcmcmZ3Q7IDxiPk9uIEJlaGFsZiBPZiA8L2I+DQpEYXZpZCBTY2hpbmF6aTxicj4NCjxiPlNl
bnQ6PC9iPiBNb25kYXksIE5vdmVtYmVyIDQsIDIwMTkgMzozMCBQTTxicj4NCjxiPlRvOjwvYj4g
UVVJQyAmbHQ7cXVpY0BpZXRmLm9yZyZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUVVJQyBWZXJz
aW9uIE5lZ290aWF0aW9uIEV4dGVuc2lvbjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
SGkgZXZlcnlvbmUsPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5Gcm9tIHRoZSByZWNlbnQgZGlzY3Vzc2lvbiBvbiBtdWx0aXBsZSBQUnMsIGl0IGFwcGVhcnMg
dGhhdCB0aGVyZSBtaWdodCBiZSBhIG5lZWQgZm9yIGRvd25ncmFkZS1zYWZlIFFVSUMgdmVyc2lv
biBuZWdvdGlhdGlvbiwgZWFybGllciB0aGFuIHdlIGV4cGVjdGVkLjxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5FS1IgYW5kIEkgdXBkYXRlZCBv
dXIgZXh0ZW5zaW9uIHRvIGhvcGVmdWxseSBzdWl0IHRoZXNlIG5lZWRzOjxvOnA+PC9vOnA+PC9w
Pg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGEgaHJlZj0iaHR0cHM6Ly90
b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXNjaGluYXppLXF1aWMtdmVyc2lvbi1uZWdvdGlhdGlv
bi0wMiI+aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LXNjaGluYXppLXF1aWMtdmVy
c2lvbi1uZWdvdGlhdGlvbi0wMjwvYT48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+Q29tbWVudHMgd2VsY29tZSBoZXJlIG9yIG9uIHRoZSBHaXRI
dWIgKGxpbmsgaW4gZHJhZnQpLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5UaGFua3MsPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5EYXZpZDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4N
CjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_BN6PR2201MB1700BB1DAD2872A2FA50059FDA790BN6PR2201MB1700_--


From nobody Wed Nov  6 10:39:45 2019
Return-Path: <fielding@gbiv.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 CCC6112011C for <quic@ietfa.amsl.com>; Wed,  6 Nov 2019 10:39:44 -0800 (PST)
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_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=gbiv.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 slgBwedTzFwv for <quic@ietfa.amsl.com>; Wed,  6 Nov 2019 10:39:42 -0800 (PST)
Received: from butterfly.birch.relay.mailchannels.net (butterfly.birch.relay.mailchannels.net [23.83.209.27]) (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 933491200F1 for <quic@ietf.org>; Wed,  6 Nov 2019 10:39:42 -0800 (PST)
X-Sender-Id: dreamhost|x-authsender|fielding@gbiv.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id ADD465E0EF2; Wed,  6 Nov 2019 18:39:41 +0000 (UTC)
Received: from pdx1-sub0-mail-a34.g.dreamhost.com (100-96-18-10.trex.outbound.svc.cluster.local [100.96.18.10]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 062E75E2349; Wed,  6 Nov 2019 18:39:41 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|fielding@gbiv.com
Received: from pdx1-sub0-mail-a34.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.5); Wed, 06 Nov 2019 18:39:41 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|fielding@gbiv.com
X-MailChannels-Auth-Id: dreamhost
X-Reaction-Trail: 304e5e8b5da404ba_1573065581480_463340236
X-MC-Loop-Signature: 1573065581479:3720797441
X-MC-Ingress-Time: 1573065581479
Received: from pdx1-sub0-mail-a34.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a34.g.dreamhost.com (Postfix) with ESMTP id A466FA1C3E; Wed,  6 Nov 2019 10:39:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=content-type :mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=gbiv.com; bh=cXyL2vzb4EWKTcofSDzOmk55dJg=; b=kK2kpCVxKXDtflmu6IWCSNWHdeeg 9EDOrWSFD50z9kBhbWTXy/jhqfOQhmWP+ysKvhHOCh6JAG+jltm+boem1cX1Of1V 5LA9VCfRkMmlMr8VH2HoCCx4IotZVsQg/tT1lGtyrXfReudDNogz8vrbcsRPlbtx UgXhoLH/cpxbHAs=
Received: from [192.168.1.4] (ip68-228-81-25.oc.oc.cox.net [68.228.81.25]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by pdx1-sub0-mail-a34.g.dreamhost.com (Postfix) with ESMTPSA id 3AA4EA1C61; Wed,  6 Nov 2019 10:39:35 -0800 (PST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
X-DH-BACKEND: pdx1-sub0-mail-a34
From: "Roy T. Fielding" <fielding@gbiv.com>
In-Reply-To: <6A43BEC7-F9DE-40C9-BF70-BF1618EAFE01@mnot.net>
Date: Wed, 6 Nov 2019 10:39:35 -0800
Cc: IETF QUIC WG <quic@ietf.org>, Lars Eggert <lars@eggert.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <88BCFF39-6F9D-4E03-8787-561EECBBACE4@gbiv.com>
References: <6A43BEC7-F9DE-40C9-BF70-BF1618EAFE01@mnot.net>
To: Mark Nottingham <mnot@mnot.net>
X-Mailer: Apple Mail (2.3445.104.11)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/6kAqVJ8byzMqrY57-pcZMB2mGWQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 06 Nov 2019 18:39:45 -0000

> On Nov 5, 2019, at 5:01 PM, Mark Nottingham <mnot@mnot.net> wrote:
>=20
> Previously, we've moved to the 'late-stage process' documented at [1] =
for the Transport and TLS drafts. The chairs and editors now feel that =
it's time to move the Recovery, HTTP/3, and QPACK drafts to that process =
as well.
>=20
> As before, this is because we're getting to a stage we feel the =
documents would benefit from slower and slightly more formal process, so =
that the rate of change is not so high, changes that do occur are =
well-vetted, and the documents get closer to reflecting consensus in the =
working group.

I don't think that process has worked well for QUIC.

There are specific issues that are contentious enough to timebox
and conclude, in a formal (and faster) fashion than was done before.
That makes sense when needed for a specific issue. I don't know
of any such issues for those three drafts. IOW, I don't know of any
issues for which it makes sense for the Chairs to pre-empt the
specification authors in deciding what can or cannot result in
changes to the drafts just because of the timing of when the
issue was raised.

The late-stage process seems to focus all of our energy into
in/out-of-scope arguments rather than actual text in the specifications.
The last interim spent easily twice as much time discussing process
and process planning than it did HTTP/3. Prior interims were worse.
I don't even recall the last time contents of the HTTP/3 spec being
discussed on list, outside of very specific issues related to transport.

I would like to see HTTP/3 written with HTTP in mind, not as a set
of diffs against h2. I would like this working group to shift its focus
away from transport issues (now that they are largely resolved and
awaiting final edits) and into active discussion of HTTP/3. The only
example we have of that is the https discussion, which revealed a
necessary issue for http-core to resolve and is expected to iterate
back onto HTTP/3.

This is not a small undertaking, but it isn't a massive one either.
Basically, import the bits of h2 that are necessary to explain HTTP/3's
operation and intent, and then start referencing the http-core drafts
instead of 723x. Yes, I know that is risky, but it is the right thing to =
do.
And it needs to be done before http-core is finished, since that effort
exists largely to place the right content (in the right places) for
HTTP/3 to reference.

That's a far better use of our time than arguing about what stage
the HTTP/3 documents are in.

I would also like to see the details of interop testing reported on =
list,
to the extent that people are willing/able to report them in public
(i.e., nothing specific to vendors or products). In particular,
I'd like to know how much of HTTP practice has actually been
exercised by those tests. Is it still limited to HTTP/0.9 interop?
Have we looked at long sessions interleaved with short spatter?
What about API-driven, non-browser traffic?

I have no idea what the status is with QPACK, but we should
learn a lesson from the last time and make sure the fixed
compression dictionary (if any) is based on traffic at more than
one proxy or origin server. Or at least have each of the major
deployments generate their local "best" encoding and do some
cross-testing of the N choices (plus one or two based on a
hand-crafted expert merge).

I would like for HTTP/3 to have a mechanism for communicating
metadata (like trailers) in mid-stream, both for requests (e.g., =
priority)
and responses (e.g., chained sigs). That has been a design goal for HTTP
since 1995 or so. HTTP/1.1 had it, albeit limited to chunked extensions.
It has been proposed multiple times and keeps getting postponed
because of "concern about scope". This is not a semantics issue
(they are just optional trailers that arrive early) -- it is a multiplex
framing issue (a new frame type and expectation to process).

> If we do this, we're saying that we have gained consensus on what =
remains in these documents, excepting their outstanding issues. As per =
our charter:
>=20
> """
> 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.
> """

-1  I don't think the non-transport issues have been discussed to the
     point where most issues could be reasonably opened, so saying
     we have consensus on the initial document is premature.
     We have been waiting for a transport consensus.
     Let's get that consensus and spend more energy on HTTP/3.

....Roy


From nobody Wed Nov  6 11:17:49 2019
Return-Path: <dschinazi.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 CD8C8120104 for <quic@ietfa.amsl.com>; Wed,  6 Nov 2019 11:17:47 -0800 (PST)
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_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 ZjkxMt1_x5Mw for <quic@ietfa.amsl.com>; Wed,  6 Nov 2019 11:17:45 -0800 (PST)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::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 F2731120044 for <quic@ietf.org>; Wed,  6 Nov 2019 11:17:44 -0800 (PST)
Received: by mail-lj1-x230.google.com with SMTP id n5so16424096ljc.9 for <quic@ietf.org>; Wed, 06 Nov 2019 11:17:44 -0800 (PST)
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=f7bNM/4LhVY97m2NbS8gHZVYud9KK9INDKygjMtWsPw=; b=cka7knVkPcHz6MDyUwXWT6jALpSKIy0BIa3+C3vh7XOJ41XMXpdyO3TWKiyBmepvOG 2EWIbL5nZloaZd6V8y0B9hXIykWSjmlo/fO6U6ZhvfVrdqp86uIUUBPDz30XBSnYAkaj n/JP8moQf/eMRkJuovt7T5urriQf8pu1CfziKEnfvlgO8pqybtDQOVzn+dB3usRHDpwA yZRMcN8BqLw28ZS9nC/0mo4LISn/vcEw4GdT6ys3F7Dq03r6XPxqptgk7xGPocfV8LRb M1o1FG+ZNaSPAe/TUbklGhmoRjFudzhuzyUGanqXTgyJtpDTvz7W5WZz9ykSof5s5406 3J0Q==
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=f7bNM/4LhVY97m2NbS8gHZVYud9KK9INDKygjMtWsPw=; b=CPVgaoUzzgF6sZbErjZc+qIJlJz19Ph7c8IqaL7OYTxoqZhEgJQSduIHFKEIryN5TY lQzydsfL1suIJ8X0VrMzuslJ/zZWEanB6lbTYkk96EhPS1ZN/zw7nr9gm/C1GWVBQArB cI2847cUZAc+LO70OHlgZTR1t4G900hWK51BRGT+l4uOwGVI2xXnf2nIOzllGAtxpfnR 2QjCI61RfMo8a39ipendeFmM/dWsR2I4P31WGL4UdZyuJDjKQxJB4DwxYVgUR4vnIbEs WAgrNWqz8LkJ8rMYEM0+RJ2JGSS3YD5+f/jM2LPpRKr1IeMKEQQ8K/hDKzzfFvgcW6Vu uPIg==
X-Gm-Message-State: APjAAAUAZZnzuTczxBodBsUHO/6PWoqQChHf7YMLolyIigEK6euq3ptc tDKQFFT5XsQ92d/uvXKdg0t0AaHU4qOKHRjdWNU=
X-Google-Smtp-Source: APXvYqy9jOKWGVx4O/EpYHPAn6UWhUhL91Yrw5xALg3BqME+RubNUo4X5Abt5kyZ5PxMxUCNKSidmt7+8HmUgF8ptL0=
X-Received: by 2002:a2e:b5a2:: with SMTP id f2mr3068733ljn.108.1573067863142;  Wed, 06 Nov 2019 11:17:43 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+4wrhqejh9k8=G7W267EgcT5Z2sDK7ZBGKtNn5kkbXGfg@mail.gmail.com> <BN6PR2201MB1700BB1DAD2872A2FA50059FDA790@BN6PR2201MB1700.namprd22.prod.outlook.com>
In-Reply-To: <BN6PR2201MB1700BB1DAD2872A2FA50059FDA790@BN6PR2201MB1700.namprd22.prod.outlook.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Wed, 6 Nov 2019 11:17:32 -0800
Message-ID: <CAPDSy+5GgGHMCtVM5DAjNnfdr4KjAtC2EezVeJYjRkGwUrRCRg@mail.gmail.com>
Subject: Re: QUIC Version Negotiation Extension
To: Mike Bishop <mbishop@evequefou.be>, Martin Thomson <mt@lowentropy.net>
Cc: QUIC <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000030b6c10596b26785"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/pLt7cED4KSN3jLPyUYeGsFgfef8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 06 Nov 2019 19:17:48 -0000

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

Thanks Mike and Martin.

I agree with your comments. The current draft evolved from the previous
revision that only supported compatible versions, and I agree that more of
the text needs to be refactored or rewritten. I've filed GitHub issues to
make sure we don't lose track of your specific comments:
https://github.com/ekr/draft-schinazi-quic-version-negotiation/issues/4
https://github.com/ekr/draft-schinazi-quic-version-negotiation/issues/5

David

On Wed, Nov 6, 2019 at 10:29 AM Mike Bishop <mbishop@evequefou.be> wrote:

> Some notes:
>
>    - *Section 3:  *=E2=80=9CVersion negotiation takes place after the ret=
ry cycle
>    is over.=E2=80=9D  This is only possible for compatible versions; if t=
he server
>    does not support the version the client attempted, it obviously cannot=
 send
>    a Retry packet in that version, because Retry packets are version-spec=
ific.
>    - *Section 3:  *=E2=80=9CServers must retain the ability to process th=
e
>    Initial packet from older versions=E2=80=A6.=E2=80=9D  No, it means th=
at *if the
>    server wants to avoid a VN packet*, it needs to be able to process the
>    Initial packet from the version the client tried.
>    - *Section 4:  *Rather than putting a count-prefixed list of versions,
>    perhaps consider just embedding the VN packet payload?  It=E2=80=99s e=
quivalent,
>    but easier to explain.
>    - *Section 7:  *Clearly it is possible to possible to add new frame
>    types to Initial packets in a future version, I think what you mean to=
 say
>    is that this is a change that would break compatibility between versio=
ns.
>
>
>
> As a general statement on the document, you assume throughout that all
> versions have packet types, contain packet types called Initial and Retry=
,
> and that Initial packets contain frames.  The odds of those things being
> true across QUIC versions is likely high, but they=E2=80=99re not invaria=
nts, so
> you can=E2=80=99t assume them here.  You need to state general principles=
, and then
> use concepts from QUICv1 as examples of the principle.
>
>
>
> For example, rather than discussing version compatibility in terms of
> Initial packets, you might want to say that versions A and B are
> =E2=80=9Ccompatible=E2=80=9D if the first flight of packets sent by the c=
lient in version A
> carries enough information for the server to generate the corresponding
> flight in version B, the server speaks version B, and is able to parse at
> least the first flight of version A.
>
>
>
> Also not discussed is the case where the server speaks version(s) which
> are compatible with what the client offered, but doesn=E2=80=99t speak th=
e version
> the client offered, even enough to generate the response.  With the right
> definition of =E2=80=9Ccompatible,=E2=80=9D this just falls into the =E2=
=80=9Cincompatible=E2=80=9D path
> and works for the server, but you need to call out the fact that the clie=
nt
> shouldn=E2=80=99t consider it an error if the server uses the incompatibl=
e path
> between versions that the client thinks are compatible.
>
>
>
> *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of * David Schinazi
> *Sent:* Monday, November 4, 2019 3:30 PM
> *To:* QUIC <quic@ietf.org>
> *Subject:* QUIC Version Negotiation Extension
>
>
>
> Hi everyone,
>
>
>
> From the recent discussion on multiple PRs, it appears that there might b=
e
> a need for downgrade-safe QUIC version negotiation, earlier than we
> expected.
>
>
>
> EKR and I updated our extension to hopefully suit these needs:
>
> https://tools.ietf.org/html/draft-schinazi-quic-version-negotiation-02
>
>
>
> Comments welcome here or on the GitHub (link in draft).
>
>
>
> Thanks,
>
> David
>

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

<div dir=3D"ltr">Thanks Mike and Martin.<div><br></div><div>I agree with yo=
ur comments. The current draft evolved from the previous revision that only=
 supported compatible versions, and I agree that more of the text needs to =
be refactored or rewritten. I&#39;ve filed GitHub issues to make sure we do=
n&#39;t lose track of your specific comments:</div><div><a href=3D"https://=
github.com/ekr/draft-schinazi-quic-version-negotiation/issues/4">https://gi=
thub.com/ekr/draft-schinazi-quic-version-negotiation/issues/4</a><br></div>=
<div><a href=3D"https://github.com/ekr/draft-schinazi-quic-version-negotiat=
ion/issues/5">https://github.com/ekr/draft-schinazi-quic-version-negotiatio=
n/issues/5</a><br></div><div><br></div><div>David</div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Nov 6, 2019 =
at 10:29 AM Mike Bishop &lt;<a href=3D"mailto:mbishop@evequefou.be">mbishop=
@evequefou.be</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">





<div lang=3D"EN-US">
<div class=3D"gmail-m_1109847572577351247WordSection1">
<p class=3D"MsoNormal">Some notes:<u></u><u></u></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"gmail-m_1109847572577351247MsoListParagraph" style=3D"margin-l=
eft:0in"><b>Section 3:=C2=A0
</b>=E2=80=9CVersion negotiation takes place after the retry cycle is over.=
=E2=80=9D=C2=A0 This is only possible for compatible versions; if the serve=
r does not support the version the client attempted, it obviously cannot se=
nd a Retry packet in that version, because Retry packets
 are version-specific.<u></u><u></u></li><li class=3D"gmail-m_1109847572577=
351247MsoListParagraph" style=3D"margin-left:0in"><b>Section 3:=C2=A0
</b>=E2=80=9CServers must retain the ability to process the Initial packet =
from older versions=E2=80=A6.=E2=80=9D=C2=A0 No, it means that
<i>if the server wants to avoid a VN packet</i>, it needs to be able to pro=
cess the Initial packet from the version the client tried.<u></u><u></u></l=
i><li class=3D"gmail-m_1109847572577351247MsoListParagraph" style=3D"margin=
-left:0in"><b>Section 4:=C2=A0
</b>Rather than putting a count-prefixed list of versions, perhaps consider=
 just embedding the VN packet payload?=C2=A0 It=E2=80=99s equivalent, but e=
asier to explain.<u></u><u></u></li><li class=3D"gmail-m_110984757257735124=
7MsoListParagraph" style=3D"margin-left:0in"><b>Section 7:=C2=A0
</b>Clearly it is possible to possible to add new frame types to Initial pa=
ckets in a future version, I think what you mean to say is that this is a c=
hange that would break compatibility between versions.<u></u><u></u></li></=
ul>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">As a general statement on the document, you assume t=
hroughout that all versions have packet types, contain packet types called =
Initial and Retry, and that Initial packets contain frames.=C2=A0 The odds =
of those things being true across QUIC
 versions is likely high, but they=E2=80=99re not invariants, so you can=E2=
=80=99t assume them here.=C2=A0 You need to state general principles, and t=
hen use concepts from QUICv1 as examples of the principle.<u></u><u></u></p=
>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">For example, rather than discussing version compatib=
ility in terms of Initial packets, you might want to say that versions A an=
d B are =E2=80=9Ccompatible=E2=80=9D if the first flight of packets sent by=
 the client in version A carries enough information
 for the server to generate the corresponding flight in version B, the serv=
er speaks version B, and is able to parse at least the first flight of vers=
ion A.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Also not discussed is the case where the server spea=
ks version(s) which are compatible with what the client offered, but doesn=
=E2=80=99t speak the version the client offered, even enough to generate th=
e response.=C2=A0 With the right definition of =E2=80=9Ccompatible,=E2=80=
=9D
 this just falls into the =E2=80=9Cincompatible=E2=80=9D path and works for=
 the server, but you need to call out the fact that the client shouldn=E2=
=80=99t consider it an error if the server uses the incompatible path betwe=
en versions that the client thinks are compatible.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal"><b>From:</b> QUIC &lt;<a href=3D"mailto:quic-bounces=
@ietf.org" target=3D"_blank">quic-bounces@ietf.org</a>&gt; <b>On Behalf Of =
</b>
David Schinazi<br>
<b>Sent:</b> Monday, November 4, 2019 3:30 PM<br>
<b>To:</b> QUIC &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic=
@ietf.org</a>&gt;<br>
<b>Subject:</b> QUIC Version Negotiation Extension<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">Hi everyone,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">From the recent discussion on multiple PRs, it appea=
rs that there might be a need for downgrade-safe QUIC version negotiation, =
earlier than we expected.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">EKR and I updated our extension to hopefully suit th=
ese needs:<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><a href=3D"https://tools.ietf.org/html/draft-schinaz=
i-quic-version-negotiation-02" target=3D"_blank">https://tools.ietf.org/htm=
l/draft-schinazi-quic-version-negotiation-02</a><u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Comments welcome here or on the GitHub (link in draf=
t).<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Thanks,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">David<u></u><u></u></p>
</div>
</div>
</div>
</div>

</blockquote></div>

--00000000000030b6c10596b26785--


From nobody Wed Nov  6 11:46:40 2019
Return-Path: <ott@in.tum.de>
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 7EFBD120104; Wed,  6 Nov 2019 11:46:27 -0800 (PST)
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_HELO_NONE=0.001, 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 xEp4Wy_q_B4C; Wed,  6 Nov 2019 11:46:25 -0800 (PST)
Received: from mail-out2.informatik.tu-muenchen.de (mail-out2.in.tum.de [131.159.0.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EC0BD120110; Wed,  6 Nov 2019 11:46:24 -0800 (PST)
Received: by mail.in.tum.de (Postfix, from userid 107) id 182AD1C0406; Wed,  6 Nov 2019 20:46:22 +0100 (CET)
Received: (Authenticated sender: ott) by mail.in.tum.de (Postfix) with ESMTPSA id 596A71C0405; Wed,  6 Nov 2019 20:46:19 +0100 (CET) (Extended-Queue-bit tech_vdhdr@fff.in.tum.de)
Subject: Re: [IETF106] Proposed workshop on QUIC performance over high BDP
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, "etosat@ietf.org" <etosat@ietf.org>, IETF QUIC WG <quic@ietf.org>, "iccrg@irtf.org" <iccrg@irtf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Cc: STEPHAN Emile RD-CORE-LAN <emile.stephan@orange.com>, =?UTF-8?Q?Robert_Br=c3=bcnig?= <robert.bruenig@gmail.com>
References: <F3B0A07CFD358240926B78A680E166FF1ECE4F1F@TW-MBX-P03.cnesnet.ad.cnes.fr> <314f4a3c-9e56-26b6-fda3-bc2694f75d3e@in.tum.de> <05fcdc09-4d86-980c-ced7-30fbc544569e@erg.abdn.ac.uk>
From: Joerg Ott <ott@in.tum.de>
Message-ID: <d63df043-9478-1124-3698-47181be6a12e@in.tum.de>
Date: Wed, 6 Nov 2019 20:46:18 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <05fcdc09-4d86-980c-ced7-30fbc544569e@erg.abdn.ac.uk>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Language: en-US
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/FybybB0iLdc_gKDNCXp64FNk8HI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 06 Nov 2019 19:46:28 -0000

We used quicly as QUIC implementation and built our own little
qperf (https://github.com/rbruenig/qperf) for running our experiments.

We did not use a full-blown satellite simulator but rather focused on
latency and capacity caps as well as (random) packet losses.  We just
used tc/netem qdisc for link emulation.

Jörg

On 05.11.19 11:11, Gorry Fairhurst wrote:
> 
> Yes, that sounds fun! - which QUIC implementation were you using, just 
> so we can make sure we compare like-with-like, and did you use an 
> operational satellite system or an emulation, or something in-between?
> 
> Gorry
> 
> On 05/11/2019 09:38, Joerg Ott wrote:
>> Hi guys,
>>
>> great activity -- we also did extensive emulation studies for QUIC
>> over satellites in a controlled environment.  Would be happy to
>> share those findings if room.
>>
>> Cheers,
>> Jörg
>>
>> On 05.11.19 09:57, Kuhn Nicolas wrote:
>>> Hi,
>>>
>>> There are multiple drafts related to the performance of QUIC over 
>>> large BDP networks (draft-kuhn-quic-4-sat, draft-kuhn-quic-0rtt-bdp, 
>>> draft-ietf-quic-recovery) or related to the performance of encrypted 
>>> protocols in general (draft-fairhurst-tsvwg-cc).
>>>
>>> The objective of this workshop is to gather people interested in such 
>>> activity and discuss the best way towards better end user experience 
>>> in this use case.
>>>
>>> Details : https://trac.ietf.org/trac/ietf/meeting/wiki/106sidemeetings
>>>
>>> Time : 3pm30 – 4pm30 on Wednesday
>>>
>>> Where : Bras Basah 
>>> https://datatracker.ietf.org/meeting/106/floor-plan?room=bras-basah#raffles-city-convention-center 
>>>
>>>
>>> Proposed agenda:
>>>
>>> Introduction : contributions that showed performance issues with QUIC 
>>> over satellite links
>>>
>>> draft-kuhn-quic-0rtt-bdp : solution to let both client and server 
>>> know the path characteristics
>>>
>>> draft-kuhn-quic-4-sat : what can be done once both client and server 
>>> have this information
>>>
>>> draft-fairhurst-tsvwg-cc : generalization to any transport and best 
>>> current practice on internet congestion control at end points
>>>
>>> If time permits: sharing experimental results (interaction between 
>>> transport and high BDP systems)
>>>
>>> If there is anything you would like to present please let us know.
>>>
>>>
>>> Kind regards,
>>>
>>> Nico, Gorry and Emile
>>>
> 


From nobody Wed Nov  6 12:56:38 2019
Return-Path: <rch@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 22C4F1200A4 for <quic@ietfa.amsl.com>; Wed,  6 Nov 2019 12:56:37 -0800 (PST)
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, DKIMWL_WL_MED=-0.001, 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_HELO_NONE=0.001, SPF_PASS=-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 F8OPFHSE4Snm for <quic@ietfa.amsl.com>; Wed,  6 Nov 2019 12:56:35 -0800 (PST)
Received: from mail-wm1-x32e.google.com (mail-wm1-x32e.google.com [IPv6:2a00:1450:4864:20::32e]) (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 73170120072 for <quic@ietf.org>; Wed,  6 Nov 2019 12:56:35 -0800 (PST)
Received: by mail-wm1-x32e.google.com with SMTP id x4so5572704wmi.3 for <quic@ietf.org>; Wed, 06 Nov 2019 12:56:35 -0800 (PST)
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=qsUI4DXxHuQSorl20ibxfURY80ifkmrzNajrtY09O7Q=; b=rff8OrbpKSo8VSdViNvFdYDY+0/HkzlTJb13ZUsd1/Z6qlZVh+ZK4G520bS41U9iNY hDlkMwMw4zTVW5J1pKaLvmPBpCMGXdqscxBIwuuq4NT5S/fdaDgrvg35coI3JzwrAVuo XVvXRra73bdGFoqmVIN2NK9WNh6YicyBtyEehUSymu7aoKmLlPSTLetrFsiQesv2uekQ VoGHErfTYg9VFKVtvXRA/ELqM0Hs8c+StHBhUmS4f27pc1rMr/eaafqIl4CrknG1gUxR sq4n9KsKCeFbEiExeDS0EcI9Vnic+rAFyQDC8ZaeioPOYWv2z+7Kz3zboFUFLype6rmN wcPA==
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=qsUI4DXxHuQSorl20ibxfURY80ifkmrzNajrtY09O7Q=; b=pRtYCyLNIk6UrzfSyvV5RTKAA0kcn5GKg/ItMjlPwNjJqWTvLIpfDXe+6gpFj7xY02 nQCtgXMk9EbMXPPjSDf8t2dWWZUAno2kpRT9iGwN/3KlD2nDiRiNkhY8/4Hcu5ff+dbt g7B5gQBPKsA1CxTNO7zM7tyD2u/OVpbF5/vTJ/lfz6hKqJixdViUkK64Ia7T5+qBx6iK MzYr4ewftDOc0d96iag/lv3MX/C9vN/xv5HQ1dxhM87ri7vM2heEvpy6WJD4KE/buRGk HkrbxKygRUjSdiu2olbyuKkha/0o3FrIvg2EorugCKNDuFAhrYmTsb5yYTBrSYOKagc0 97cA==
X-Gm-Message-State: APjAAAV7rETB7Ulyo9YudustP9jNz7t8XV6Nc54hATOe0Jq7QjXgD8nH Wkgy2OxMKqsKRDLMVBtdPGS3QSiLE6sMcpEEY9WhTldyHJR37A==
X-Google-Smtp-Source: APXvYqwRwHMKOKv3W4l2ut5qOgVWFiCeNl9/3oc2DS1Q+3R8qIxrBav3H/BzdjFHqzSFYlCvdMBSOzdzYBhFv5j4pus=
X-Received: by 2002:a7b:cae2:: with SMTP id t2mr4103037wml.161.1573073793417;  Wed, 06 Nov 2019 12:56:33 -0800 (PST)
MIME-Version: 1.0
References: <6A43BEC7-F9DE-40C9-BF70-BF1618EAFE01@mnot.net> <CAJ_4DfQocLyL=3j_xDS_b5Jj_U62Dt8wH=Ymi6tEKHJwcwVJtA@mail.gmail.com> <9DDD10B1-424F-4A62-837E-A93EA7594781@mnot.net>
In-Reply-To: <9DDD10B1-424F-4A62-837E-A93EA7594781@mnot.net>
From: Ryan Hamilton <rch@google.com>
Date: Wed, 6 Nov 2019 12:56:21 -0800
Message-ID: <CAJ_4DfT+hjH-ja5NohveACi7XmDx0jTy6JqRnXAkSQ3ePp54jw@mail.gmail.com>
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
To: Mark Nottingham <mnot@mnot.net>
Cc: IETF QUIC WG <quic@ietf.org>, Lars Eggert <lars@eggert.org>
Content-Type: multipart/alternative; boundary="000000000000aa09c40596b3c8b3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Z8GzJX_f0OsmaVophdMqSgkCVmc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 06 Nov 2019 20:56:37 -0000

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

On Tue, Nov 5, 2019 at 5:41 PM Mark Nottingham <mnot@mnot.net> wrote:

>
> I think our intent was that it's an open issue, but I see that we haven't
> captured that in the current issues list. Good catch; let's go ahead and
> open one.
>

Done. https://github.com/quicwg/base-drafts/issues/3198

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

<div dir=3D"ltr"><div dir=3D"ltr"><div class=3D"gmail_default" style=3D"fon=
t-family:trebuchet ms,sans-serif"><span style=3D"font-family:Arial,Helvetic=
a,sans-serif">On Tue, Nov 5, 2019 at 5:41 PM Mark Nottingham &lt;<a href=3D=
"mailto:mnot@mnot.net">mnot@mnot.net</a>&gt; wrote:</span><br></div></div><=
div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
><br>
I think our intent was that it&#39;s an open issue, but I see that we haven=
&#39;t captured that in the current issues list. Good catch; let&#39;s go a=
head and open one.<br></blockquote><div><br></div><div class=3D"gmail_defau=
lt" style=3D"font-family:&quot;trebuchet ms&quot;,sans-serif">Done.=C2=A0<a=
 href=3D"https://github.com/quicwg/base-drafts/issues/3198" class=3D"cremed=
" style=3D"font-family:Arial,Helvetica,sans-serif">https://github.com/quicw=
g/base-drafts/issues/3198</a><span style=3D"font-family:Arial,Helvetica,san=
s-serif">=C2=A0</span></div></div></div>

--000000000000aa09c40596b3c8b3--


From nobody Thu Nov  7 04:38:31 2019
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 BEA76120251 for <quic@ietfa.amsl.com>; Thu,  7 Nov 2019 04:38:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 W2-XeQ9JKR-a for <quic@ietfa.amsl.com>; Thu,  7 Nov 2019 04:38:27 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:42:150::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0C970120152 for <quic@ietf.org>; Thu,  7 Nov 2019 04:38:26 -0800 (PST)
Received: from gorry-mac.erg.abdn.ac.uk (unknown [IPv6:2001:630:42:110:f9a2:f494:9c7a:603c]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id DF7201B00064; Thu,  7 Nov 2019 12:38:18 +0000 (GMT)
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
To: Mike Bishop <mbishop@evequefou.be>, Mark Nottingham <mnot@mnot.net>, Ryan Hamilton <rch@google.com>
Cc: Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
References: <6A43BEC7-F9DE-40C9-BF70-BF1618EAFE01@mnot.net> <CAJ_4DfQocLyL=3j_xDS_b5Jj_U62Dt8wH=Ymi6tEKHJwcwVJtA@mail.gmail.com> <9DDD10B1-424F-4A62-837E-A93EA7594781@mnot.net> <BN6PR2201MB1700F28E83B7E752473192D7DA790@BN6PR2201MB1700.namprd22.prod.outlook.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <0693b533-a492-de2b-7a96-64c5f56d6882@erg.abdn.ac.uk>
Date: Thu, 7 Nov 2019 12:38:18 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <BN6PR2201MB1700F28E83B7E752473192D7DA790@BN6PR2201MB1700.namprd22.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/UKwai9hvt4x8bioXZh6UZwhJfoU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 07 Nov 2019 12:38:30 -0000

I don't think Recovery has that level of maturity yet.

To me, QUIC transport contains protocol specs that are the same as other 
protocols - albeit inter-twined with the encryption model and 
HTTP-specific aspects, but the recovery spec is focused on the protocol 
mechanisms, and needs to be correct with respect to the implications on 
other transport flows sharing capacity with QUIC.

In that space, we indeed need to get the spec correct. That may mean 
late comments (alas); but hopefully things will move faster if we focus 
on resolving issues and if work separates a little to http3 v recovery 
topic, actually most of the comments seem to come from a few people. If 
the process somehow impeded that I would be concerned.

Maybe I might feel happier after a detailed review of the latest text in 
24 and a check through the issues -Â  I undertake to do this before the 
Singapore meeting!

Gorry


On 06/11/2019 15:59, Mike Bishop wrote:
> Also, the design team is an HTTP design team focused on having a coherent story around prioritization across HTTP versions.  They/we might propose text back to HTTP/3, or they might define HTTP/3 extensions in an HTTPbis document, or they might do something else entirely.  This working group should consider the design team output if it comes before the document is done, and if not will need to make a decision about whether to proceed without it.
>
> -----Original Message-----
> From: QUIC <quic-bounces@ietf.org> On Behalf Of Mark Nottingham
> Sent: Tuesday, November 5, 2019 8:41 PM
> To: Ryan Hamilton <rch@google.com>
> Cc: Lars Eggert <lars@eggert.org>; IETF QUIC WG <quic@ietf.org>
> Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
>
> Hi Ryan,
>
> I think our intent was that it's an open issue, but I see that we haven't captured that in the current issues list. Good catch; let's go ahead and open one.
>
> Cheers,
>
>
>> On 6 Nov 2019, at 12:35 pm, Ryan Hamilton <rch@google.com> wrote:
>>
>> For QPACK and Recovery, this sounds great to me. For  HTTP/3, as I understand it, we still have a design team working on priorities. Can you clarify how this effort is affected by the late stage process? (Or is is basically unaffected as it is an open issue?)
>>
>> On Tue, Nov 5, 2019 at 5:02 PM Mark Nottingham <mnot@mnot.net> wrote:
>> Previously, we've moved to the 'late-stage process' documented at [1] for the Transport and TLS drafts. The chairs and editors now feel that it's time to move the Recovery, HTTP/3, and QPACK drafts to that process as well.
>>
>> As before, this is because we're getting to a stage we feel the documents would benefit from slower and slightly more formal process, so that the rate of change is not so high, changes that do occur are well-vetted, and the documents get closer to reflecting consensus in the working group.
>>
>> If we do this, we're saying that we have gained consensus on what remains in these documents, excepting their outstanding issues. As per our charter:
>>
>> """
>> 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 doesn't mean that new issues can't be raised against those drafts. However, new issues against them will be judged for whether they contain new information (in particular, security or interoperability impact), a clear technical defect, or have significant (in the judgement of the chairs) support for further discussion. If the issue isn't well-described or atomic, it may be closed with a request to refactor, or refactored for you.
>>
>> Again, this does not affect editorial issues.
>>
>> Practically speaking, it means that new issues will be triaged by the Chairs -- not the editors (although they can still "claim" purely editorial issues) -- and those that don't meet the criteria above will be closed. Those that do will be labeled (again, by the Chairs only) as `design`.
>>
>> It also means that all of the closed `design` issues against these drafts will be marked as `has-consensus`. Additionally, the `quicv2` issues against them will be closed and marked `has-consensus`.
>>
>> The issues that will be labeled `has-consensus` (and closed, if still open) are listed here:
>>
>> https://github.com/quicwg/base-drafts/issues?q=is%3Aissue+is%3Aclosed+label%3Adesign+-label%3Ahas-consensus+-label%3A-transport+-label%3A-tls
>>
>> We believe that all of these issues have been discussed and the group has formed consensus on them; this only formalises that.
>>
>> If you have concerns or questions, please discuss them on-list; barring pushback, we'll adopt this on 15-Nov-2019.
>>
>> Cheers,
>>
>> 1. https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md#late-stage-process
>>
>> --
>> Mark and Lars, QUIC WG Chairs
>>
> --
> Mark Nottingham   https://www.mnot.net/



From nobody Fri Nov  8 06:12:41 2019
Return-Path: <iesg-secretary@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 A3FDF120105; Fri,  8 Nov 2019 06:12:39 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: IESG Secretary <iesg-secretary@ietf.org>
To: "IETF-Announce" <ietf-announce@ietf.org>
Cc: quic@ietf.org
Subject: QUIC (quic) WG Interim Meeting: 2020-02-05
X-Test-IDTracker: no
X-IETF-IDTracker: 6.110.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <157322235949.23423.10790460052498505337@ietfa.amsl.com>
Date: Fri, 08 Nov 2019 06:12:39 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/geSNOnvWc0f1m_RJkN0PilpLeks>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 08 Nov 2019 14:12:40 -0000

The QUIC (quic) Working Group will hold
a multi-day interim meeting.

Session 1:
2020-02-05     09:30 to 16:30  Europe/Zurich
Session 2:
2020-02-06     09:30 to 16:30  Europe/Zurich

Meeting Location:
Zurich, CH

Agenda:
Discussion of the QUIC transport, TLS, recovery, HTTP/3, manageability and operability drafts, and other drafts adopted by the WG at that time.

Information about remote participation:
See arrangements page

Arrangements at: https://github.com/quicwg/wg-materials/blob/master/interim-20-02/arrangements.md


From nobody Sat Nov  9 23:32:15 2019
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 C6493120033 for <quic@ietfa.amsl.com>; Sat,  9 Nov 2019 23:32:13 -0800 (PST)
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=stsA3drK; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ykfQrGWS
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 G7k0oT6OeN6b for <quic@ietfa.amsl.com>; Sat,  9 Nov 2019 23:32:10 -0800 (PST)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 43000120013 for <quic@ietf.org>; Sat,  9 Nov 2019 23:32:10 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.west.internal (Postfix) with ESMTP id 4A587376 for <quic@ietf.org>; Sun, 10 Nov 2019 02:32:09 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sun, 10 Nov 2019 02:32:09 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject:message-id:date; s= fm1; bh=Lk35Q+fA35pKfEzQpjunGQChsTdEZE6NKxXTPoBLQS8=; b=stsA3drK tmecL8wG3m3w/iDNA0v2Ggzkp5H0XngpKiLZQZybSOjN+o93YbVlDjWD8W9mJPYl hecWcsjVlQbmiKb0wWoIISIaRMcbliATDjq7OrRKSbafZ+trvbR46fc7y9bUefim s21j29u2P2vtzvQnHQ73qHSAYgul5X/fcmxd83yrXNiNoid1FDLB0WnWbXyP77X8 QYLRfLJ5i8AT5Iq/cdID3AsdrMeg8GO68YAz6wEXCeozMAdaNKyAfe97rdV/omc6 WUR2oQAM+dL6H/gQCxTe1h1eblaQckgQuzHDme76hgZ65CebpfHdckqmgw/jEpxD H9zHhBrS/TP+eQ==
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-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=Lk35Q+fA35pKfEzQpjunGQChsTdEZ E6NKxXTPoBLQS8=; b=ykfQrGWSO9W0Cj3IXNUVCkDBO1lXXZtlkGB36QoZORLST UetRih+OUtHG+M9kaxF27Mvf3aDABn7b59W32F9sGkZPLj1ytdk/iWuD0EGkhwLT j40OU6yleYAP8U5G2M0EJeLqU15n7gzkFREKat4o9k2N1DcrwKAqOJd2kwGniz8g inynrLhLDGsklGADusk6iDJVF14dTe2npFFAwLNIy9THx+MKjVa7zW6a9O1/TZgy 5J1C9l9S2Hbw6d/d9FwMTpAqiiXWOhSNabJHzCiUJ8PwSyZ4ji+X+QnHqrMk2Tp3 9Ck92kp1NvAlPxDC+xZ1E9BllmgVDDxlBPU9fiE0Q==
X-ME-Sender: <xms:-LzHXTaU6ZkJaX_NCl-Vw6AktLD475zNfmXRWZaYftprqMSMRJ4DxA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedruddvgedguddtiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurheptggghffvufesrgdttdertddtje enucfhrhhomheptfgvphhoshhithhorhihucettghtihhvihhthicuufhumhhmrghrhicu uehothcuoeguohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvghtqeenucffohhmrghinh epghhithhhuhgsrdgtohhmnecukfhppedufedrledtrddvuddurdejleenucfrrghrrghm pehmrghilhhfrhhomhepughopghnohhtpghrvghplhihsehmnhhothdrnhgvthenucevlh hushhtvghrufhiiigvpedu
X-ME-Proxy: <xmx:-LzHXYiJmWWh6T464mqD2glLLOeseAg_Hiccve5Boy_IxRav_0k4vg> <xmx:-LzHXYoPq-dWx5GDkE6zK4booUPMrSiPfDzm0bhl0Epc2cAbczoI_Q> <xmx:-LzHXXeoXqPTQREnOt_lMTRh-sbwiI-4LNcFOz2KK5ZpCDZK5U3WIg> <xmx:-LzHXdj7FRVftlE6trthxtYvxOQG0XZ17kTbhpwK_IfJpaRyaXlGWQ>
Received: from [10.1.0.4] (unknown [13.90.211.79]) by mail.messagingengine.com (Postfix) with ESMTPA id 82C4980059 for <quic@ietf.org>; Sun, 10 Nov 2019 02:32:08 -0500 (EST)
Content-Type: multipart/alternative; boundary="===============0936204220549311285=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: quic@ietf.org
Subject: Weekly github digest ( Activity Summary)
Message-Id: <20191110073208.82C4980059@mailuser.nyi.internal>
Date: Sun, 10 Nov 2019 02:32:08 -0500 (EST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/xeCNoM8tz4pR0dHrzIuOyWxSVvg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 10 Nov 2019 07:32:14 -0000

--===============0936204220549311285==
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 (+9/-4/=F0=9F=92=AC58)
  9 issues created:
  - 3.1.3 loss epoch (by rpaulo)
    https://github.com/quicwg/base-drafts/issues/3210=20
  - max_datagram_size being a variable means other constants become variabl=
es (by larseggert)
    https://github.com/quicwg/base-drafts/issues/3205 [-recovery]=20
  - Definition of "active connection ID" is misleading (or the name is) (by=
 kazuho)
    https://github.com/quicwg/base-drafts/issues/3200=20
  - ChaCha20 header protection sample (by martinthomson)
    https://github.com/quicwg/base-drafts/issues/3199 [-tls]=20
  - HTTP/3 is lacking priorities (by RyanAtGoogle)
    https://github.com/quicwg/base-drafts/issues/3198=20
  - active_connection_id_limit defaults to 0 (by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/3197 [-transport]=20
  - conflicting advice how to handle Retire Prior To (by marten-seemann)
    https://github.com/quicwg/base-drafts/issues/3195=20
  - reordered NEW_CONNECTION_ID frames with retired sequence numbers should=
n't be used (by marten-seemann)
    https://github.com/quicwg/base-drafts/issues/3194=20
  - active_connection_id_limit interacts poorly with Retire Prior To (by ma=
rten-seemann)
    https://github.com/quicwg/base-drafts/issues/3193=20

  16 issues received 58 new comments:
  - #3205 max_datagram_size being a variable means other constants become v=
ariables (1 by ianswett)
    https://github.com/quicwg/base-drafts/issues/3205 [-recovery]=20
  - #3200 Definition of "active connection ID" is misleading (or the name i=
s) (4 by kazuho, marten-seemann, martinthomson)
    https://github.com/quicwg/base-drafts/issues/3200 [-transport]=20
  - #3199 ChaCha20 header protection sample (4 by kazuho, martinthomson)
    https://github.com/quicwg/base-drafts/issues/3199 [-tls]=20
  - #3198 HTTP/3 is lacking priorities (3 by LPardue, RyanAtGoogle, martint=
homson)
    https://github.com/quicwg/base-drafts/issues/3198 [-http]=20
  - #3197 active_connection_id_limit defaults to 0 (3 by kazuho, marten-see=
mann, martinthomson)
    https://github.com/quicwg/base-drafts/issues/3197 [-transport]=20
  - #3195 conflicting advice how to handle Retire Prior To (1 by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/3195=20
  - #3194 reordered NEW_CONNECTION_ID frames with retired sequence numbers =
shouldn't be used (2 by erickinnear, martinthomson)
    https://github.com/quicwg/base-drafts/issues/3194=20
  - #3193 active_connection_id_limit interacts poorly with Retire Prior To =
(17 by MikeBishop, erickinnear, ianswett, kazuho, marten-seemann, nibanks)
    https://github.com/quicwg/base-drafts/issues/3193=20
  - #3189 QUIC lacks on-path exposure of packet loss (10 by britram, ferrie=
ux, igorlord, janaiyengar, jesusmamartin, mikkelfj, mnot)
    https://github.com/quicwg/base-drafts/issues/3189 [-transport]=20
  - #3176 Maximum packet size should be per 4-tuple (1 by martinthomson)
    https://github.com/quicwg/base-drafts/issues/3176 [-transport]=20
  - #3161 Simplify the client's PTO code by allowing the server to send a P=
ING (2 by ianswett, janaiyengar)
    https://github.com/quicwg/base-drafts/issues/3161 [-recovery] [-transpo=
rt]=20
  - #3159 Server should not accept 1-RTT traffic before handshake completio=
n (1 by huitema)
    https://github.com/quicwg/base-drafts/issues/3159 [-tls] [design]=20
  - #3158 Application close should be disallowed in Initial or Handshake (1=
 by mikkelfj)
    https://github.com/quicwg/base-drafts/issues/3158 [-transport] [design]=
 [proposal-ready]=20
  - #3155 The method of identifying "the same server" (3 by kazuho, martint=
homson, mikkelfj)
    https://github.com/quicwg/base-drafts/issues/3155 [-transport] [design]=
 [proposal-ready]=20
  - #2863 unrecoverable loss pattern leads to deadlock (1 by janaiyengar)
    https://github.com/quicwg/base-drafts/issues/2863 [-transport] [design]=
=20
  - #253 HTTP/QUIC without Alt-Svc? (4 by LPardue, MikeBishop, fbifido)
    https://github.com/quicwg/base-drafts/issues/253 [-http] [design]=20

  4 issues closed:
  - Require peers to check if RETIRE_CONNECTION_ID sequence number is valid=
 https://github.com/quicwg/base-drafts/issues/3037 [-transport] [design] [h=
as-consensus]=20
  - unrecoverable loss pattern leads to deadlock https://github.com/quicwg/=
base-drafts/issues/2863 [-transport] [design]=20
  - Probe packet section needs to suggest a crypto context https://github.c=
om/quicwg/base-drafts/issues/3074 [-recovery] [design]=20
  - 0RTT or 0.5RTT data extends the PTO before handshake completion https:/=
/github.com/quicwg/base-drafts/issues/3067 [-recovery] [design]=20



Pull requests
-------------
* quicwg/base-drafts (+7/-4/=F0=9F=92=AC28)
  7 pull requests submitted:
  - PING in all contexts (by martinduke)
    https://github.com/quicwg/base-drafts/pull/3209=20
  - Recommend H3_NO_ERROR for early responses (by MikeBishop)
    https://github.com/quicwg/base-drafts/pull/3208 [-http]=20
  - Resolve conflicting advice on how to handle Retire Prior To (by erickin=
near)
    https://github.com/quicwg/base-drafts/pull/3204=20
  - Add Retry CID change requirement to transport changelog (by dtikhonov)
    https://github.com/quicwg/base-drafts/pull/3203=20
  - handle reordered NEW_CONNECTION_ID frames (by marten-seemann)
    https://github.com/quicwg/base-drafts/pull/3202=20
  - enforce the active_connection_id_limit (by marten-seemann)
    https://github.com/quicwg/base-drafts/pull/3201=20
  - Add ClientHello changes to transport changelog since -23 (by dtikhonov)
    https://github.com/quicwg/base-drafts/pull/3191=20

  7 pull requests received 28 new comments:
  - #3202 handle reordered NEW_CONNECTION_ID frames (9 by MikeBishop, erick=
innear, ianswett, marten-seemann)
    https://github.com/quicwg/base-drafts/pull/3202 [-transport] [design]=20
  - #3201 enforce the active_connection_id_limit (1 by marten-seemann)
    https://github.com/quicwg/base-drafts/pull/3201 [-transport] [design]=20
  - #3188 Correct overflow checks on packet number decoding algorithm (1 by=
 martinthomson)
    https://github.com/quicwg/base-drafts/pull/3188 [-transport] [design]=20
  - #3186 allow CRYPTO_BUFFER_EXCEEDED when overflowing a CRYPTO frame (12 =
by ianswett, janaiyengar, kazuho, marten-seemann)
    https://github.com/quicwg/base-drafts/pull/3186 [-transport]=20
  - #3185 Recovery changelog for -24 (1 by janaiyengar)
    https://github.com/quicwg/base-drafts/pull/3185 [-recovery]=20
  - #3170 Allow provisional registrations for all registries (1 by martinth=
omson)
    https://github.com/quicwg/base-drafts/pull/3170 [-transport] [design]=20
  - #3131 Improve language on blocking entries. (3 by MikeBishop, afrind, b=
encebeky)
    https://github.com/quicwg/base-drafts/pull/3131 [-qpack]=20

  4 pull requests merged:
  - require peers to check if RETIRE_CONNECTION_ID sequence number is valid
    https://github.com/quicwg/base-drafts/pull/3036 [-transport] [design]=20
  - Fix bug in Insert Count Increment description.
    https://github.com/quicwg/base-drafts/pull/3132 [-qpack]=20
  - Change PTO to be per packet number space
    https://github.com/quicwg/base-drafts/pull/3066 [-recovery] [design]=20
  - Correct overflow checks on packet number decoding algorithm
    https://github.com/quicwg/base-drafts/pull/3188 [-transport] [design]=20


Repositories tracked by this digest:
-----------------------------------
* https://github.com/quicwg/base-drafts

--===============0936204220549311285==
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 ( Activity Summary)</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 November 10, 2019</h1>

<p>Events without label "editorial"</p>

<h2>Issues</h2>

<h3>quicwg/base-drafts (+9/-4/=F0=9F=92=AC58)</h3>
  <p class=3D"new">9 issues created:</p>
  <ul>
  <li>#3210 <a href=3D"https://github.com/quicwg/base-drafts/issues/3210">3=
.1.3 loss epoch</a> (by rpaulo) </li>
 =20
  <li>#3205 <a href=3D"https://github.com/quicwg/base-drafts/issues/3205">m=
ax_datagram_size being a variable means other constants become variables</a=
> (by larseggert) <span class=3D"label" style=3D"background-color: #fbca04;=
 color: #000000">-recovery</span> </li>
 =20
  <li>#3200 <a href=3D"https://github.com/quicwg/base-drafts/issues/3200">D=
efinition of &quot;active connection ID&quot; is misleading (or the name is=
)</a> (by kazuho) </li>
 =20
  <li>#3199 <a href=3D"https://github.com/quicwg/base-drafts/issues/3199">C=
haCha20 header protection sample</a> (by martinthomson) <span class=3D"labe=
l" style=3D"background-color: #fbca04; color: #000000">-tls</span> </li>
 =20
  <li>#3198 <a href=3D"https://github.com/quicwg/base-drafts/issues/3198">H=
TTP/3 is lacking priorities</a> (by RyanAtGoogle) </li>
 =20
  <li>#3197 <a href=3D"https://github.com/quicwg/base-drafts/issues/3197">a=
ctive_connection_id_limit defaults to 0</a> (by MikeBishop) <span class=3D"=
label" style=3D"background-color: #fbca04; color: #000000">-transport</span=
> </li>
 =20
  <li>#3195 <a href=3D"https://github.com/quicwg/base-drafts/issues/3195">c=
onflicting advice how to handle Retire Prior To</a> (by marten-seemann) </l=
i>
 =20
  <li>#3194 <a href=3D"https://github.com/quicwg/base-drafts/issues/3194">r=
eordered NEW_CONNECTION_ID frames with retired sequence numbers shouldn&#x2=
7;t be used</a> (by marten-seemann) </li>
 =20
  <li>#3193 <a href=3D"https://github.com/quicwg/base-drafts/issues/3193">a=
ctive_connection_id_limit interacts poorly with Retire Prior To</a> (by mar=
ten-seemann) </li>
  </ul>

  <p>16 issues received 58 new comments:</p>
  <ul>
  <li>#3205 <a href=3D"https://github.com/quicwg/base-drafts/issues/3205">m=
ax_datagram_size being a variable means other constants become variables</a=
> (1 by ianswett) <span class=3D"label" style=3D"background-color: #fbca04;=
 color: #000000">-recovery</span> </li>
 =20
  <li>#3200 <a href=3D"https://github.com/quicwg/base-drafts/issues/3200">D=
efinition of &quot;active connection ID&quot; is misleading (or the name is=
)</a> (4 by kazuho, marten-seemann, martinthomson) <span class=3D"label" st=
yle=3D"background-color: #fbca04; color: #000000">-transport</span> </li>
 =20
  <li>#3199 <a href=3D"https://github.com/quicwg/base-drafts/issues/3199">C=
haCha20 header protection sample</a> (4 by kazuho, martinthomson) <span cla=
ss=3D"label" style=3D"background-color: #fbca04; color: #000000">-tls</span=
> </li>
 =20
  <li>#3198 <a href=3D"https://github.com/quicwg/base-drafts/issues/3198">H=
TTP/3 is lacking priorities</a> (3 by LPardue, RyanAtGoogle, martinthomson)=
 <span class=3D"label" style=3D"background-color: #fbca04; color: #000000">=
-http</span> </li>
 =20
  <li>#3197 <a href=3D"https://github.com/quicwg/base-drafts/issues/3197">a=
ctive_connection_id_limit defaults to 0</a> (3 by kazuho, marten-seemann, m=
artinthomson) <span class=3D"label" style=3D"background-color: #fbca04; col=
or: #000000">-transport</span> </li>
 =20
  <li>#3195 <a href=3D"https://github.com/quicwg/base-drafts/issues/3195">c=
onflicting advice how to handle Retire Prior To</a> (1 by MikeBishop) </li>
 =20
  <li>#3194 <a href=3D"https://github.com/quicwg/base-drafts/issues/3194">r=
eordered NEW_CONNECTION_ID frames with retired sequence numbers shouldn&#x2=
7;t be used</a> (2 by erickinnear, martinthomson) </li>
 =20
  <li>#3193 <a href=3D"https://github.com/quicwg/base-drafts/issues/3193">a=
ctive_connection_id_limit interacts poorly with Retire Prior To</a> (17 by =
MikeBishop, erickinnear, ianswett, kazuho, marten-seemann, nibanks) </li>
 =20
  <li>#3189 <a href=3D"https://github.com/quicwg/base-drafts/issues/3189">Q=
UIC lacks on-path exposure of packet loss</a> (10 by britram, ferrieux, igo=
rlord, janaiyengar, jesusmamartin, mikkelfj, mnot) <span class=3D"label" st=
yle=3D"background-color: #fbca04; color: #000000">-transport</span> </li>
 =20
  <li>#3176 <a href=3D"https://github.com/quicwg/base-drafts/issues/3176">M=
aximum packet size should be per 4-tuple</a> (1 by martinthomson) <span cla=
ss=3D"label" style=3D"background-color: #fbca04; color: #000000">-transport=
</span> </li>
 =20
  <li>#3161 <a href=3D"https://github.com/quicwg/base-drafts/issues/3161">S=
implify the client&#x27;s PTO code by allowing the server to send a PING</a=
> (2 by ianswett, janaiyengar) <span class=3D"label" style=3D"background-co=
lor: #fbca04; color: #000000">-recovery</span> <span class=3D"label" style=
=3D"background-color: #fbca04; color: #000000">-transport</span> </li>
 =20
  <li>#3159 <a href=3D"https://github.com/quicwg/base-drafts/issues/3159">S=
erver should not accept 1-RTT traffic before handshake completion</a> (1 by=
 huitema) <span class=3D"label" style=3D"background-color: #fbca04; color: =
#000000">-tls</span> <span class=3D"label" style=3D"background-color: #1d76=
db; color: #ffffff">design</span> </li>
 =20
  <li>#3158 <a href=3D"https://github.com/quicwg/base-drafts/issues/3158">A=
pplication close should be disallowed in Initial or Handshake</a> (1 by mik=
kelfj) <span class=3D"label" style=3D"background-color: #fbca04; color: #00=
0000">-transport</span> <span class=3D"label" style=3D"background-color: #1=
d76db; color: #ffffff">design</span> <span class=3D"label" style=3D"backgro=
und-color: #c5def5; color: #000000">proposal-ready</span> </li>
 =20
  <li>#3155 <a href=3D"https://github.com/quicwg/base-drafts/issues/3155">T=
he method of identifying &quot;the same server&quot;</a> (3 by kazuho, mart=
inthomson, mikkelfj) <span class=3D"label" style=3D"background-color: #fbca=
04; color: #000000">-transport</span> <span class=3D"label" style=3D"backgr=
ound-color: #1d76db; color: #ffffff">design</span> <span class=3D"label" st=
yle=3D"background-color: #c5def5; color: #000000">proposal-ready</span> </l=
i>
 =20
  <li>#2863 <a href=3D"https://github.com/quicwg/base-drafts/issues/2863">u=
nrecoverable loss pattern leads to deadlock</a> (1 by janaiyengar) <span cl=
ass=3D"label" style=3D"background-color: #fbca04; color: #000000">-transpor=
t</span> <span class=3D"label" style=3D"background-color: #1d76db; color: #=
ffffff">design</span> </li>
 =20
  <li>#253 <a href=3D"https://github.com/quicwg/base-drafts/issues/253">HTT=
P/QUIC without Alt-Svc?</a> (4 by LPardue, MikeBishop, fbifido) <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>
  </ul>

  <p>4 issues closed:</p>
  <ul>
  <li>#3037 <a href=3D"https://github.com/quicwg/base-drafts/issues/3037">R=
equire peers to check if RETIRE_CONNECTION_ID sequence number is valid</a> =
<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> <span class=3D"label" style=3D"background-col=
or: #5319e7; color: #ffffff">has-consensus</span> </li>
 =20
  <li>#2863 <a href=3D"https://github.com/quicwg/base-drafts/issues/2863">u=
nrecoverable loss pattern leads to deadlock</a> <span class=3D"label" style=
=3D"background-color: #fbca04; color: #000000">-transport</span> <span clas=
s=3D"label" style=3D"background-color: #1d76db; color: #ffffff">design</spa=
n> </li>
 =20
  <li>#3074 <a href=3D"https://github.com/quicwg/base-drafts/issues/3074">P=
robe packet section needs to suggest a crypto context</a> <span class=3D"la=
bel" style=3D"background-color: #fbca04; color: #000000">-recovery</span> <=
span class=3D"label" style=3D"background-color: #1d76db; color: #ffffff">de=
sign</span> </li>
 =20
  <li>#3067 <a href=3D"https://github.com/quicwg/base-drafts/issues/3067">0=
RTT or 0.5RTT data extends the PTO before handshake completion</a> <span cl=
ass=3D"label" style=3D"background-color: #fbca04; color: #000000">-recovery=
</span> <span class=3D"label" style=3D"background-color: #1d76db; color: #f=
fffff">design</span> </li>
  </ul>



<h2>Pull requests</h2>
<h3>quicwg/base-drafts (+7/-4/=F0=9F=92=AC28)</h3>
  <p class=3D"new">7 pull requests submitted:</p>
  <ul>
  <li>#3209 <a href=3D"https://github.com/quicwg/base-drafts/pull/3209">PIN=
G in all contexts</a> (by martinduke) </li>
 =20
  <li>#3208 <a href=3D"https://github.com/quicwg/base-drafts/pull/3208">Rec=
ommend H3_NO_ERROR for early responses</a> (by MikeBishop) <span class=3D"l=
abel" style=3D"background-color: #fbca04; color: #">-http</span> </li>
 =20
  <li>#3204 <a href=3D"https://github.com/quicwg/base-drafts/pull/3204">Res=
olve conflicting advice on how to handle Retire Prior To</a> (by erickinnea=
r) </li>
 =20
  <li>#3203 <a href=3D"https://github.com/quicwg/base-drafts/pull/3203">Add=
 Retry CID change requirement to transport changelog</a> (by dtikhonov) </l=
i>
 =20
  <li>#3202 <a href=3D"https://github.com/quicwg/base-drafts/pull/3202">han=
dle reordered NEW_CONNECTION_ID frames</a> (by marten-seemann) </li>
 =20
  <li>#3201 <a href=3D"https://github.com/quicwg/base-drafts/pull/3201">enf=
orce the active_connection_id_limit</a> (by marten-seemann) </li>
 =20
  <li>#3191 <a href=3D"https://github.com/quicwg/base-drafts/pull/3191">Add=
 ClientHello changes to transport changelog since -23</a> (by dtikhonov) </=
li>
  </ul>

  <p>7 pull requests received 28 new comments:</p>
  <ul>
  <li>#3202 <a href=3D"https://github.com/quicwg/base-drafts/pull/3202">han=
dle reordered NEW_CONNECTION_ID frames</a> (9 by MikeBishop, erickinnear, i=
answett, marten-seemann) <span class=3D"label" style=3D"background-color: #=
fbca04; color: #000000">-transport</span> <span class=3D"label" style=3D"ba=
ckground-color: #1d76db; color: #ffffff">design</span> </li>
 =20
  <li>#3201 <a href=3D"https://github.com/quicwg/base-drafts/pull/3201">enf=
orce the active_connection_id_limit</a> (1 by marten-seemann) <span class=
=3D"label" style=3D"background-color: #fbca04; color: #000000">-transport</=
span> <span class=3D"label" style=3D"background-color: #1d76db; color: #fff=
fff">design</span> </li>
 =20
  <li>#3188 <a href=3D"https://github.com/quicwg/base-drafts/pull/3188">Cor=
rect overflow checks on packet number decoding algorithm</a> (1 by martinth=
omson) <span class=3D"label" style=3D"background-color: #fbca04; color: #00=
0000">-transport</span> <span class=3D"label" style=3D"background-color: #1=
d76db; color: #ffffff">design</span> </li>
 =20
  <li>#3186 <a href=3D"https://github.com/quicwg/base-drafts/pull/3186">all=
ow CRYPTO_BUFFER_EXCEEDED when overflowing a CRYPTO frame</a> (12 by ianswe=
tt, janaiyengar, kazuho, marten-seemann) <span class=3D"label" style=3D"bac=
kground-color: #fbca04; color: #000000">-transport</span> </li>
 =20
  <li>#3185 <a href=3D"https://github.com/quicwg/base-drafts/pull/3185">Rec=
overy changelog for -24</a> (1 by janaiyengar) <span class=3D"label" style=
=3D"background-color: #fbca04; color: #000000">-recovery</span> </li>
 =20
  <li>#3170 <a href=3D"https://github.com/quicwg/base-drafts/pull/3170">All=
ow provisional registrations for all registries</a> (1 by martinthomson) <s=
pan class=3D"label" style=3D"background-color: #fbca04; color: #000000">-tr=
ansport</span> <span class=3D"label" style=3D"background-color: #1d76db; co=
lor: #ffffff">design</span> </li>
 =20
  <li>#3131 <a href=3D"https://github.com/quicwg/base-drafts/pull/3131">Imp=
rove language on blocking entries.</a> (3 by MikeBishop, afrind, bencebeky)=
 <span class=3D"label" style=3D"background-color: #fbca04; color: #000000">=
-qpack</span> </li>
  </ul>

  <p>4 pull requests merged:</p>
  <ul>
  <li>#3036 <a href=3D"https://github.com/quicwg/base-drafts/pull/3036">req=
uire peers to check if RETIRE_CONNECTION_ID sequence number is valid</a> <s=
pan class=3D"label" style=3D"background-color: #fbca04; color: #">-transpor=
t</span> <span class=3D"label" style=3D"background-color: #1d76db; color: #=
">design</span> </li>
 =20
  <li>#3132 <a href=3D"https://github.com/quicwg/base-drafts/pull/3132">Fix=
 bug in Insert Count Increment description.</a> <span class=3D"label" style=
=3D"background-color: #fbca04; color: #">-qpack</span> </li>
 =20
  <li>#3066 <a href=3D"https://github.com/quicwg/base-drafts/pull/3066">Cha=
nge PTO to be per packet number space</a> <span class=3D"label" style=3D"ba=
ckground-color: #fbca04; color: #">-recovery</span> <span class=3D"label" s=
tyle=3D"background-color: #1d76db; color: #">design</span> </li>
 =20
  <li>#3188 <a href=3D"https://github.com/quicwg/base-drafts/pull/3188">Cor=
rect overflow checks on packet number decoding algorithm</a> <span class=3D=
"label" style=3D"background-color: #fbca04; color: #">-transport</span> <sp=
an class=3D"label" style=3D"background-color: #1d76db; color: #">design</sp=
an> </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>

--===============0936204220549311285==--


From nobody Sun Nov 10 14:54:10 2019
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 6E4051200E0 for <quic@ietfa.amsl.com>; Sun, 10 Nov 2019 14:54:08 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 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_HELO_NONE=0.001, SPF_NONE=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 zBHURfU5kpjd for <quic@ietfa.amsl.com>; Sun, 10 Nov 2019 14:54:06 -0800 (PST)
Received: from mail-lf1-x129.google.com (mail-lf1-x129.google.com [IPv6:2a00:1450:4864:20::129]) (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 CEB72120090 for <quic@ietf.org>; Sun, 10 Nov 2019 14:54:05 -0800 (PST)
Received: by mail-lf1-x129.google.com with SMTP id y6so8376599lfj.2 for <quic@ietf.org>; Sun, 10 Nov 2019 14:54:05 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dUBa5a8Ot09W5mIAaAyLwOj7kyd023RxBwhVNWRzE2k=; b=ml7O/teHb+Ae7auxEuVAHgLAMpjDFQrwaC6W1t//0qHE7oNiEexdhul57lUCKNAvOK gaxPnDbXGJkDQgX+Z+BEBLaZpoEPbtlQ9Bu6b+bSQcBYBD9aYvk6iaExSbBL6O32ajBV dY9yMi7d90bgCidzipqTzv9Ap2pPuBG99TG82uL6W8kmySsThoVIm2MhitTvvDRUhBn4 x9Zug8D5UTqFeL2hsgU86MXH051jR2hko27rORDXV3+B+be5QfmFYOyQlnZ80Jt08T6G SjPl+geig7K0MZzwcdc4hezDlz4V+O1+4gFTF8FnZlDLKyIBVhPLG5Vf0SrcA51qXdvA Dlfw==
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=dUBa5a8Ot09W5mIAaAyLwOj7kyd023RxBwhVNWRzE2k=; b=nAullaEFhlSMK8FiVQzfmJTI2Q0+hpGqZMUV0xMVzuuvTtWg/J6MzZn1sDPGicbbLy 716eyybieIrR8Qc3S3wTjWMgbNKY56ihGk3NqNdLZ7NZpFfs6pdQT/bA4FuPvkX+PEMp 5E5OfTOdm9YgUhb2e+phKmJpW/vgRzV1T6saEA7HsP3RejTVJLAZWkkvmXN3e7pADnPa K5NY80rX6ace0gDsA+rftj8VC6HuWPXE7cVg/xi0YZkttjRCnD1cZ1o9HEgQ/CEiZWf4 BNG4lEXcWHJWWa7zFwk81wfLFHumz4cCFqghM/Sph/sVosiNhUJcFNZwW32BwbaZtWzz vHEQ==
X-Gm-Message-State: APjAAAXbQzebsObonFaWL/ybBRG+c8RifMX7LvMqR/mETItiUKP4NYfb lPoqk+nYKgqoSYseu7fgzj21NQLSUQJq3BQ5L5inUw==
X-Google-Smtp-Source: APXvYqwwjG4qHIE1jg2pY3W0+sgvGElX7bMdQDcTyXbI7va0uRcbux+BUVToWe9OZBun0WzdxKkq84t4fU9u5trAkf8=
X-Received: by 2002:a19:6d19:: with SMTP id i25mr8104628lfc.178.1573426444020;  Sun, 10 Nov 2019 14:54:04 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+6E79OySoOLbJ8eWp0J-+3yeB5iGvj6sW19bEDn_V7-NA@mail.gmail.com>
In-Reply-To: <CAPDSy+6E79OySoOLbJ8eWp0J-+3yeB5iGvj6sW19bEDn_V7-NA@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Sun, 10 Nov 2019 14:53:26 -0800
Message-ID: <CABcZeBN+6p2k+Kj4K5oKNEqKV50aAU6FLGkiZG0dGPNkg1s_-A@mail.gmail.com>
Subject: Re: Version Ossification: Intended Scope for QUICv1
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: QUIC <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000046bdc7059705e4fa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/z0_qzvD309FuBcQURFAy1r3zb5k>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 10 Nov 2019 22:54:09 -0000

--00000000000046bdc7059705e4fa
Content-Type: text/plain; charset="UTF-8"

I would actually like to suggest something more aggressive (or,
conservative, if you prefer), namely that we punt version ossification
entirely to the future, whether to an extension or QUIVc2. In support
of this proposal, I would make three points:

- We are actually going to be running concurrent versions for quite
  some time. Even if everyone were to aggressively (say 6-12 months)
  deprecate all the draft versions upon shipping the RFC, we're
  looking at something that's 18-24 months out. And of course,
  I expect people to do some simple version greasing. So, that
  probably buys us some time before real bad ossification sets
  in.

- It's turning out to be surprisingly hard to design a mechanism that
  works, as evidenced by David's mechanism. And to that, I would add
  that anything that involves having a server hand out some new set of
  keys/salts is going to run into the same kind of multi-CDN problems
  we had with ESNI (i.e., failures when you get switched between
  CDNs). And then recovering from that cleanly either seems to mean
  some ESNI-style fallback or allowing a middlebox to forge VN to
  force you back to the published version/salt.

- It seems like this would all be a lot easier if we had ESNI, because
  you could tie the use of the new salt/version to the ESNIConfig
  (either as a public or symmetric key, depending on taste).

So what I would propose is that we put this problem on ice for now and
then revisit it as an extension. All of the proposals that we have
seen seem like they could be done as an extension, and then we can (1)
get QUICv1 done and (2) hopefully leverage ESNI once we have some
experience.

-Ekr

On Thu, Oct 31, 2019 at 2:13 PM David Schinazi <dschinazi.ietf@gmail.com>
wrote:

> Hi folks,
>
> The conversation around version ossification has been really interesting
> since Cupertino. But at least for me it's reached a level of complexity
> that warrants taking a step back and looking at what we're trying to solve.
> Here's my understanding of where we are:
>
> 1) In Cupertino there was consensus in the room to do something to
> mitigate ossification of QUICv1.
>
> 2) The solution that folks liked was to have a concept of alternative
> versions and alternative salts that act like QUICv1 but are encoded
> differently over the wire.
>
> 3) A concrete proposal for (2) was for servers to have their own set of
> (alternative_version, alternative_salt) pairs, then transmit a random pair
> from that set to each client (i.e. via transport parameters). The server
> can then reconstruct the alternative_salt just by seeing
> the alternative_version.
>
> 4) Kazuho proposed a solution (#3166
> <https://github.com/quicwg/base-drafts/pull/3166>) that was both more
> powerful and more complex: tie the (alternative_version, alternative_salt)
> pair to NEW_TOKEN frames, to allow servers to generate a
> unique alternative_salt per client and encode it in the token.
>
> 5) After some interesting back and forth on that PR, it became clear that
> this is a hard problem to solve: this could cause failures if servers
> forget their token keys, and mitigations for that problem can become
> downgrade attack vectors
>
> 6) While there was clear WG appetite for (1), I'm not sure we have
> consensus to build a more powerful solution like (4)
>
> I fear that solving (5) could take some time, which would delay QUICv1.
> Instead I'd like to propose the following plan:
> a) we take the simpler solution (3) and add that to the spec
> b) we take the more powerful/complex solution (5) a turn it into a QUIC
> extension
>
> That would allow us to ship QUICv1 with some level of ossification
> mitigations without delay.
>
> Thoughts?
>
> David
>
>
>

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

<div dir=3D"ltr">I would actually like to suggest something more aggressive=
 (or,<br>conservative, if you prefer), namely that we punt version ossifica=
tion<br>entirely to the future, whether to an extension or QUIVc2. In suppo=
rt<br>of this proposal, I would make three points:<br><br>- We are actually=
 going to be running concurrent versions for quite<br>=C2=A0 some time. Eve=
n if everyone were to aggressively (say 6-12 months)<br>=C2=A0 deprecate al=
l the draft versions upon shipping the RFC, we&#39;re<br>=C2=A0 looking at =
something that&#39;s 18-24 months out. And of course,<br>=C2=A0 I expect pe=
ople to do some simple version greasing. So, that<br>=C2=A0 probably buys u=
s some time before real bad ossification sets<br>=C2=A0 in.<br><br>- It&#39=
;s turning out to be surprisingly hard to design a mechanism that<br>=C2=A0=
 works, as evidenced by David&#39;s mechanism. And to that, I would add<br>=
=C2=A0 that anything that involves having a server hand out some new set of=
<br>=C2=A0 keys/salts is going to run into the same kind of multi-CDN probl=
ems<br>=C2=A0 we had with ESNI (i.e., failures when you get switched betwee=
n<br>=C2=A0 CDNs). And then recovering from that cleanly either seems to me=
an<br>=C2=A0 some ESNI-style fallback or allowing a middlebox to forge VN t=
o<br>=C2=A0 force you back to the published version/salt.<br><br>- It seems=
 like this would all be a lot easier if we had ESNI, because<br>=C2=A0 you =
could tie the use of the new salt/version to the ESNIConfig<br>=C2=A0 (eith=
er as a public or symmetric key, depending on taste).<br><br>So what I woul=
d propose is that we put this problem on ice for now and<br>then revisit it=
 as an extension. All of the proposals that we have<br>seen seem like they =
could be done as an extension, and then we can (1)<br>get QUICv1 done and (=
2) hopefully leverage ESNI once we have some<br>experience.<br><br>-Ekr<br>=
</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">=
On Thu, Oct 31, 2019 at 2:13 PM David Schinazi &lt;<a href=3D"mailto:dschin=
azi.ietf@gmail.com" target=3D"_blank">dschinazi.ietf@gmail.com</a>&gt; wrot=
e:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0=
.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"l=
tr">Hi folks,<div><br></div><div>The conversation around version ossificati=
on has been really interesting since Cupertino. But at least for me it&#39;=
s reached a level of complexity that warrants taking a step back and lookin=
g at what we&#39;re trying to solve. Here&#39;s my understanding of where w=
e are:</div><div><br></div><div>1) In Cupertino there was consensus in the =
room to do something to mitigate ossification of QUICv1.</div><div><br></di=
v><div>2) The solution that folks liked was to have a concept of alternativ=
e versions and alternative salts that act like QUICv1 but are encoded diffe=
rently over the wire.</div><div><br></div><div>3) A concrete proposal for (=
2) was for servers to have their own set of (alternative_version, alternati=
ve_salt) pairs, then transmit a random pair from that set to each client (i=
.e. via transport parameters). The server can then reconstruct the alternat=
ive_salt just by seeing the=C2=A0alternative_version.</div><div><br></div><=
div>4) Kazuho proposed a solution (<a href=3D"https://github.com/quicwg/bas=
e-drafts/pull/3166" target=3D"_blank">#3166</a>) that was both more powerfu=
l and more complex: tie the=C2=A0(alternative_version, alternative_salt) pa=
ir to NEW_TOKEN frames, to allow servers to generate a unique=C2=A0alternat=
ive_salt per client and encode it in the token.</div><div><br></div><div>5)=
 After some interesting back and forth on that PR, it became clear that thi=
s is a hard problem to solve: this could cause failures if servers forget t=
heir token keys, and mitigations for that problem can become downgrade atta=
ck vectors</div><div><br></div><div>6) While there was clear WG appetite fo=
r (1), I&#39;m not sure we have consensus to build a more powerful solution=
 like (4)</div><div><br></div><div>I fear that solving (5) could take some =
time, which would delay QUICv1. Instead I&#39;d like to propose the followi=
ng plan:</div><div>a) we take the simpler solution (3) and add that to the =
spec</div><div>b) we take the more powerful/complex solution (5) a turn it =
into a QUIC extension</div><div><br></div><div>That would allow us to ship =
QUICv1 with some level of ossification mitigations without delay.</div><div=
><br></div><div>Thoughts?</div><div><br></div><div>David</div><div><br></di=
v><div><br></div></div>
</blockquote></div>

--00000000000046bdc7059705e4fa--


From nobody Sun Nov 10 16:48:22 2019
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 445A51200E5 for <quic@ietfa.amsl.com>; Sun, 10 Nov 2019 16:48:21 -0800 (PST)
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, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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 eKUCOU-hywAC for <quic@ietfa.amsl.com>; Sun, 10 Nov 2019 16:48:20 -0800 (PST)
Received: from mx36-out10.antispamcloud.com (mx36-out10.antispamcloud.com [209.126.121.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 F1CDE12001A for <quic@ietf.org>; Sun, 10 Nov 2019 16:48:19 -0800 (PST)
Received: from xse234.mail2web.com ([66.113.196.234] helo=xse.mail2web.com) by mx147.antispamcloud.com with esmtp (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1iTxsO-000dRL-Us for quic@ietf.org; Mon, 11 Nov 2019 01:48:19 +0100
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 47BC0b4LFKz2bgn for <quic@ietf.org>; Sun, 10 Nov 2019 16:48:15 -0800 (PST)
Received: from [10.5.2.13] (helo=xmail03.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1iTxsN-0008Le-Fq for quic@ietf.org; Sun, 10 Nov 2019 16:48:15 -0800
Received: (qmail 30426 invoked from network); 11 Nov 2019 00:48:15 -0000
Received: from unknown (HELO [192.168.1.106]) (Authenticated-user:_huitema@huitema.net@[172.58.43.113]) (envelope-sender <huitema@huitema.net>) by xmail03.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 11 Nov 2019 00:48:14 -0000
Subject: Re: Version Ossification: Intended Scope for QUICv1
To: Eric Rescorla <ekr@rtfm.com>, David Schinazi <dschinazi.ietf@gmail.com>
Cc: QUIC <quic@ietf.org>
References: <CAPDSy+6E79OySoOLbJ8eWp0J-+3yeB5iGvj6sW19bEDn_V7-NA@mail.gmail.com> <CABcZeBN+6p2k+Kj4K5oKNEqKV50aAU6FLGkiZG0dGPNkg1s_-A@mail.gmail.com>
From: Christian Huitema <huitema@huitema.net>
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mQENBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAG0J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PokBOQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1a5AQ0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAYkCPgQYAQIACQUCUhFfyAIb 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: <376bcf21-b18f-9199-8054-47122419e1d4@huitema.net>
Date: Sun, 10 Nov 2019 16:48:14 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.1
MIME-Version: 1.0
In-Reply-To: <CABcZeBN+6p2k+Kj4K5oKNEqKV50aAU6FLGkiZG0dGPNkg1s_-A@mail.gmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 8bit
Content-Language: en-US
X-Originating-IP: 66.113.196.234
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.234/32
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.234/32@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0T9zDZOvA8ND4p2eQxdfzLSpSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDcnqpk5VeF3xR4kF6iVwRtbgN zB/4Jkrw1eDLcif59fuvmGJHBnoppfri2I+STuMbU7Tmz6iKnkQL9gqsxD347235Nhqq+/HvroPq 8GSPg+60/QPNqXybIny9WGhadIo/GLPGseHORnR7zfibQ2DIPryme9ldZJ7uNXfg/GfS8fUvP/L5 rCqHDsKZM+xa1iwJX+gRCHfMVnsAk591zk0uilUI+ZL4xWiN8NS6C+dmX6OEdA4u1aThyWrQ/ou2 +v/lmX4Em37yFgrCB6NHRn1g+f3uncIqYSL3lhh5c81YyJqFoLZMmkWsaurVZfvqROaDnDtHb8z5 dpPkEuJ8Snwqla7jUnW3hy14Yji8fo+4xCnSRo4Rcu5Z37rMuDjCny5fE9ykbJ7I9co1MAEE3ruN Xsm8UJsAPvDcVSKtDCYkioPY5Qx4fJOk03R5fJtf/Dv/dkIzS7m4GUpXCY1Y3j3ileOfMnQTuxRu w7b3K/aRb5igZQ+n9Vd4zr6nNv8/QtdB41jAa5ZJHsyYKPxQUcgmPsI2xtGD/+Y3SMXx1KpmI3hk DBiQWxoMMt9CeSOhI+q1RoC7cBJJy7fzup1OBG+nHxg66gs5OuzYxJgw5atIxeNDvjI/CYe5WPy0 +t1RP0azI5nA+66xZXfktM0swgtUg5xMPnetLBJMh51NiRRoHIAS7RQseocMIfvNQhzDF3yFmiK7 x42VjdzChZMe6O/Did+/hGXTmfhE+Dx2/NyzMXr9cDkA9FC6vflMJMBD/+V+vOnCUbNPgcPcQwzM gKHyQxUo+ql2ySTkvEFH/23XMww2BnTTFGX5/yI4Ky+1ZJcbGqc5H4PEZHeoI/d6LWFf332z7LMw LGdoi9FMQ5j9dQUvMi1YKAun15JQSJLyCT5k+MTObVKxHy/dols381l9r9ft9daDonlwd6LnuX+J u10=
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/qYB6qsHOJmqi9fPdTrGsLzPhInI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Nov 2019 00:48:21 -0000

On 11/10/2019 2:53 PM, Eric Rescorla wrote:
> I would actually like to suggest something more aggressive (or,
> conservative, if you prefer), namely that we punt version ossification
> entirely to the future, whether to an extension or QUIVc2. In support
> of this proposal, I would make three points:
>
> - We are actually going to be running concurrent versions for quite
> Â  some time. Even if everyone were to aggressively (say 6-12 months)
> Â  deprecate all the draft versions upon shipping the RFC, we're
> Â  looking at something that's 18-24 months out. And of course,
> Â  I expect people to do some simple version greasing. So, that
> Â  probably buys us some time before real bad ossification sets
> Â  in.
>
> - It's turning out to be surprisingly hard to design a mechanism that
> Â  works, as evidenced by David's mechanism. And to that, I would add
> Â  that anything that involves having a server hand out some new set of
> Â  keys/salts is going to run into the same kind of multi-CDN problems
> Â  we had with ESNI (i.e., failures when you get switched between
> Â  CDNs). And then recovering from that cleanly either seems to mean
> Â  some ESNI-style fallback or allowing a middlebox to forge VN to
> Â  force you back to the published version/salt.
>
> - It seems like this would all be a lot easier if we had ESNI, because
> Â  you could tie the use of the new salt/version to the ESNIConfig
> Â  (either as a public or symmetric key, depending on taste).
>
> So what I would propose is that we put this problem on ice for now and
> then revisit it as an extension. All of the proposals that we have
> seen seem like they could be done as an extension, and then we can (1)
> get QUICv1 done and (2) hopefully leverage ESNI once we have some
> experience.

+1

-- Christian Huitema


From nobody Sun Nov 10 17:01:11 2019
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 4CC1E12001A for <quic@ietfa.amsl.com>; Sun, 10 Nov 2019 17:01:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.69
X-Spam-Level: 
X-Spam-Status: No, score=-2.69 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, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=F2i75tl/; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=niDuEtDm
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 Ux0Iao-8Cbgs for <quic@ietfa.amsl.com>; Sun, 10 Nov 2019 17:01:03 -0800 (PST)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 9DE5C1200E5 for <quic@ietf.org>; Sun, 10 Nov 2019 17:01:03 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id C09D7481; Sun, 10 Nov 2019 20:01:02 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sun, 10 Nov 2019 20:01:03 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=f Bhmb0zeBNR5VAOnhnLk0dfOcjuvaj3nxG/1ulw1e04=; b=F2i75tl/f3jukGszF 3qbjkGClrFlnG+fLQ6gTbfjuwWoh2TyqKZM55vZ2N+TSo7NEwV58iyPpHCpH+BDl Gt8oU/BAKva9l1H7+Qj47t+PJGY7jCqNYvWjMCE6xuwCTyJ0bp2ERVNIxH5dIEp3 y+fwDwTP7jCLJQ3eoHXffwP+KdeR5o2oJkh37T8Np6YWGNEJm7k8UgyzVzahgb9N 81NUF2tfvP5KRuXq+1NPAaaFye1GJEjEtCNDwJSHEeR8RobsR2aNEKxT3Y0XxFkU f+7i4l2yg0wwzAiCEfxXIGDRAxVU9x+LALqM2aBg1VbAlhvUFLfxRPNRneFLjFGB B9L5Q==
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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=fBhmb0zeBNR5VAOnhnLk0dfOcjuvaj3nxG/1ulw1e 04=; b=niDuEtDmlDqpi5Ug3qEyutP9WfhRNUSfnnjucIsaEeIPhRfa9zWkr9Efu GqkYRU19wmXVd+4/NDlDNIHZKQzixeWna5RvVhD//aeeNJkNNefILP1JkF8RXMS7 5EE5koCaNohVD8ly0AFyGPjQzBuHng+FqcDzXTK740OdDUfYLsYi39a/lX1UMWsZ 2a97OYzfC+Ifb3GuxAJNrNA+yIk8DxsC4sD9g5OflQIQvSbEhOrT3yYFM+DxQQl6 wL+UmMWcyu6Bnh/BJGdsw7LJxSRFgc6sZvq2ekeSZszl7Dwylll1BEHrzca8N4Dm cu7XxFBjTsXor0zlA0W6VdjKqXBYA==
X-ME-Sender: <xms:tbLIXcE0u_5waat1kmRJvXI9F-0JQr2x8v0LllGmKQHIBG34fnSFbQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedruddviedgfedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhk ucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinh ephhhtthhpfegrnhguqhhprggtkhgurhgrfhhtshhtohhthhgrthhprhhotggvshhsrghs figvlhhlrdgrshdpudhhrgguihhtrghlsggvihhtlhhimhhithgvughtohgthhhunhhkvg guvgigthgvnhhsihhonhhsrdhithdpmhhnohhtrdhnvghtnecukfhppeduudelrddujedr udehkedrvdehudenucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnhhothdrnh gvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:tbLIXZYJiArW4ZZYrDgasOHNOdWNeVqH2Ik5MEjhVJNIdFWdvhZ7eA> <xmx:tbLIXQ1R472aqApexXf_Bll6956OjBnRkPFEOY7dGpkxKExoD3uF-w> <xmx:tbLIXdbG-b7q63-LiYLyBhUVXi107_4qVkPYm2hXYBewirtLxPry8g> <xmx:zrLIXQE2d2VxKgCih46tD4KGqIv_WTzTjY-rotM0r6KSkScbfBqQgA>
Received: from attitudadjuster.mnot.net (unknown [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id 028043060064; Sun, 10 Nov 2019 20:00:35 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <88BCFF39-6F9D-4E03-8787-561EECBBACE4@gbiv.com>
Date: Mon, 11 Nov 2019 12:00:30 +1100
Cc: IETF QUIC WG <quic@ietf.org>, Lars Eggert <lars@eggert.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <FD5201A5-C179-4302-B437-57561FB8DB24@mnot.net>
References: <6A43BEC7-F9DE-40C9-BF70-BF1618EAFE01@mnot.net> <88BCFF39-6F9D-4E03-8787-561EECBBACE4@gbiv.com>
To: Roy Fielding <fielding@gbiv.com>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/78s6-ARMtJfDGpEMjoJsJu3p904>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Nov 2019 01:01:09 -0000

Hi Roy,

Responding to the parts relevant to this CfC.

> On 7 Nov 2019, at 5:39 am, Roy T. Fielding <fielding@gbiv.com> wrote:
>=20
>> On Nov 5, 2019, at 5:01 PM, Mark Nottingham <mnot@mnot.net> wrote:
>>=20
>> Previously, we've moved to the 'late-stage process' documented at [1] =
for the Transport and TLS drafts. The chairs and editors now feel that =
it's time to move the Recovery, HTTP/3, and QPACK drafts to that process =
as well.
>>=20
>> As before, this is because we're getting to a stage we feel the =
documents would benefit from slower and slightly more formal process, so =
that the rate of change is not so high, changes that do occur are =
well-vetted, and the documents get closer to reflecting consensus in the =
working group.
>=20
> I don't think that process has worked well for QUIC.

Noted.

> There are specific issues that are contentious enough to timebox
> and conclude, in a formal (and faster) fashion than was done before.
> That makes sense when needed for a specific issue. I don't know
> of any such issues for those three drafts. IOW, I don't know of any
> issues for which it makes sense for the Chairs to pre-empt the
> specification authors in deciding what can or cannot result in
> changes to the drafts just because of the timing of when the
> issue was raised.

You misunderstand the process; the Chairs aren't pre-empting anything, =
the group is attempting to agree to a path to completing this work.

> The late-stage process seems to focus all of our energy into
> in/out-of-scope arguments rather than actual text in the =
specifications.

I don't see any evidence for that claim; what makes you believe that?

> The last interim spent easily twice as much time discussing process
> and process planning than it did HTTP/3. Prior interims were worse.

We spent a day talking about transport and TLS, part of a morning =
talking about planning the future of our work (if you want to call that =
"process and process planning") and the bulk of the (longer) afternoon =
session talking about H3. This isn't surprising, since our goal for the =
meeting was to get the Transport and TLS documents close to finished.

> I don't even recall the last time contents of the HTTP/3 spec being
> discussed on list, outside of very specific issues related to =
transport.
> I would like to see HTTP/3 written with HTTP in mind, not as a set
> of diffs against h2.

That is by charter; we're largely limited to mapping H2 onto QUIC.=20

> This is not a small undertaking, but it isn't a massive one either.
> Basically, import the bits of h2 that are necessary to explain =
HTTP/3's
> operation and intent, and then start referencing the http-core drafts
> instead of 723x. Yes, I know that is risky, but it is the right thing =
to do.
> And it needs to be done before http-core is finished, since that =
effort
> exists largely to place the right content (in the right places) for
> HTTP/3 to reference.

AIUI that is still our intent, and shouldn't be impeded by the =
late-stage process, since that work should be editorial.

> I have no idea what the status is with QPACK, but we should
> learn a lesson from the last time and make sure the fixed
> compression dictionary (if any) is based on traffic at more than
> one proxy or origin server. Or at least have each of the major
> deployments generate their local "best" encoding and do some
> cross-testing of the N choices (plus one or two based on a
> hand-crafted expert merge).
>=20
> I would like for HTTP/3 to have a mechanism for communicating
> metadata (like trailers) in mid-stream, both for requests (e.g., =
priority)
> and responses (e.g., chained sigs). That has been a design goal for =
HTTP
> since 1995 or so. HTTP/1.1 had it, albeit limited to chunked =
extensions.
> It has been proposed multiple times and keeps getting postponed
> because of "concern about scope". This is not a semantics issue
> (they are just optional trailers that arrive early) -- it is a =
multiplex
> framing issue (a new frame type and expectation to process).

Where are the multiple proposals you refer to? We've been working on h3 =
now for more than three years. If you submit them now, they'll be design =
issues.

I'd say that the Late-Stage process (or at least the proposal of =
adopting it) is working exactly as intended here -- making people =
realise that if they still have issues / changes that they want =
discussed, they need to bring them to our attention now, not as we go to =
WGLC.

Cheers,

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


From nobody Sun Nov 10 17:01:38 2019
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 2965F1200F4 for <quic@ietfa.amsl.com>; Sun, 10 Nov 2019 17:01:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.69
X-Spam-Level: 
X-Spam-Status: No, score=-2.69 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, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=zgCDn3Ej; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=yydV22Rv
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 D-M9YWX2TMce for <quic@ietfa.amsl.com>; Sun, 10 Nov 2019 17:01:31 -0800 (PST)
Received: from out5-smtp.messagingengine.com (out5-smtp.messagingengine.com [66.111.4.29]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 6F9041200E5 for <quic@ietf.org>; Sun, 10 Nov 2019 17:01:31 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 6373D21B10; Sun, 10 Nov 2019 20:01:30 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sun, 10 Nov 2019 20:01:30 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=i b39KCe29g0ywekDhcgk9O/xVX9Anb2/kRrv3vZEIMI=; b=zgCDn3EjdEom9nF1L yNm1VfLJ/GDREa4l+nq0NDQpchuHiV5S6Ktvavt1rjnxubOg7GV4phVs4K2Cqzw1 t1kiclg9/OqxP+5uwfYodtrJ46Iwq7fAdbnnzqNvlPXAY1eONXHTxPGCNDJ+jSxX bSa1p9e98699AbWspNO+ihc3GHoMRaiDFY4GZ4vl9ZXAMIEwKHuib3nUG2igaUNL jTesDyFXXJLXfs4dJNajGgUXCJB/Tj/791pdoFDEyvlr2+flay+XRmXJgBhqJuCm 3kayeWIbKeuk5g2zi3NZyTb3rWqKsX3YhOC0ng5Q/XD+W022Al1MpCAzy6EJ/4i+ rwCfw==
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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=ib39KCe29g0ywekDhcgk9O/xVX9Anb2/kRrv3vZEI MI=; b=yydV22RvGBzgWy878h5/30ESGiHQBqaKsr+XxQS8b1Yy7KEE4qwnfVKp+ mtt4zEIVdhk6rAKgDwRdmVOWUeTnPIQdHyNVrrJ4ol/hen7MTH70z8uOLVWjmvgv KPeKbeSyFMnQFP5Ly1aLwWiI5s30FN7vohn+b0rZ0lwDmWi9O7QmZH5yC+I6l6oi rQb8FXUIofrYoN6x3Jd9STpaD2Y/uTwLCTdxGx/QBKCv82ceKkg9egzyLf/o5ZlI CVhpzCuJeBLi1fxPI6KHZ8wpN9voQLvOSaqPcpU/+ds9jx//EMpneB7IQeyG2oR0 dc1rsQdknHgXG4Dwq0EpO+6b5UI6Q==
X-ME-Sender: <xms:6bLIXU8bX3AZu9T2gaXyGreI6M26ygeQ38TvV8M4A1HnEKW_OQgmbg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedruddviedgfedtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhk ucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinh ephhhtthhpfegrnhguqhhprggtkhgurhgrfhhtshhtohhthhgrthhprhhotggvshhsrghs figvlhhlrdgrshdpghhithhhuhgsrdgtohhmpdhmnhhothdrnhgvthenucfkphepuddule drudejrdduheekrddvhedunecurfgrrhgrmhepmhgrihhlfhhrohhmpehmnhhothesmhhn ohhtrdhnvghtnecuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:6bLIXY3_sxOdyn7CUIufjlrQzCqPyqVD-RZMs_2B0yzWjcumHh3juA> <xmx:6bLIXWLw7WSC_HSMgHLXEiATkaqdstoOty3mde6rEPbRR6zw-lejbg> <xmx:6bLIXZFZTZ-tjoa2qRa7ZdXUVKG7B_FRNRRihon0yN-KRgTjbjog3g> <xmx:6rLIXSoj5ujSx5w2DFpRUnSTxa5eJs8iZhnJu7WiwAzSet7Wmf3VoA>
Received: from attitudadjuster.mnot.net (unknown [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id E2C87306005E; Sun, 10 Nov 2019 20:01:27 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <0693b533-a492-de2b-7a96-64c5f56d6882@erg.abdn.ac.uk>
Date: Mon, 11 Nov 2019 12:01:25 +1100
Cc: Mike Bishop <mbishop@evequefou.be>, Ryan Hamilton <rch@google.com>, Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <91C83829-AEA2-4EB3-9A74-318150B9F75B@mnot.net>
References: <6A43BEC7-F9DE-40C9-BF70-BF1618EAFE01@mnot.net> <CAJ_4DfQocLyL=3j_xDS_b5Jj_U62Dt8wH=Ymi6tEKHJwcwVJtA@mail.gmail.com> <9DDD10B1-424F-4A62-837E-A93EA7594781@mnot.net> <BN6PR2201MB1700F28E83B7E752473192D7DA790@BN6PR2201MB1700.namprd22.prod.outlook.com> <0693b533-a492-de2b-7a96-64c5f56d6882@erg.abdn.ac.uk>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/vi1Hf2Lszex54s-pnav178pX6Ig>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Nov 2019 01:01:37 -0000

Hi Gorry,

> On 7 Nov 2019, at 11:38 pm, Gorry Fairhurst <gorry@erg.abdn.ac.uk> =
wrote:
>=20
> I don't think Recovery has that level of maturity yet.
>=20
> To me, QUIC transport contains protocol specs that are the same as =
other protocols - albeit inter-twined with the encryption model and =
HTTP-specific aspects, but the recovery spec is focused on the protocol =
mechanisms, and needs to be correct with respect to the implications on =
other transport flows sharing capacity with QUIC.
>=20
> In that space, we indeed need to get the spec correct. That may mean =
late comments (alas); but hopefully things will move faster if we focus =
on resolving issues and if work separates a little to http3 v recovery =
topic, actually most of the comments seem to come from a few people. If =
the process somehow impeded that I would be concerned.

I think the group would easily consider an issue regarding fairness to =
be worth discussion, so adopting the late-stage process shouldn't cause =
concern along these lines. The goal here is to beat any remaining issues =
out of the bushes (so to speak), and assure that we don't have an =
onslaught of "well, I would have done it this way..." issues crop up.

> Maybe I might feel happier after a detailed review of the latest text =
in 24 and a check through the issues -  I undertake to do this before =
the Singapore meeting!

That's reasonable; I think we can delay making a decision until then.

Cheers,


>=20
> Gorry
>=20
>=20
> On 06/11/2019 15:59, Mike Bishop wrote:
>> Also, the design team is an HTTP design team focused on having a =
coherent story around prioritization across HTTP versions.  They/we =
might propose text back to HTTP/3, or they might define HTTP/3 =
extensions in an HTTPbis document, or they might do something else =
entirely.  This working group should consider the design team output if =
it comes before the document is done, and if not will need to make a =
decision about whether to proceed without it.
>>=20
>> -----Original Message-----
>> From: QUIC <quic-bounces@ietf.org> On Behalf Of Mark Nottingham
>> Sent: Tuesday, November 5, 2019 8:41 PM
>> To: Ryan Hamilton <rch@google.com>
>> Cc: Lars Eggert <lars@eggert.org>; IETF QUIC WG <quic@ietf.org>
>> Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to =
the Late-Stage Process
>>=20
>> Hi Ryan,
>>=20
>> I think our intent was that it's an open issue, but I see that we =
haven't captured that in the current issues list. Good catch; let's go =
ahead and open one.
>>=20
>> Cheers,
>>=20
>>=20
>>> On 6 Nov 2019, at 12:35 pm, Ryan Hamilton <rch@google.com> wrote:
>>>=20
>>> For QPACK and Recovery, this sounds great to me. For  HTTP/3, as I =
understand it, we still have a design team working on priorities. Can =
you clarify how this effort is affected by the late stage process? (Or =
is is basically unaffected as it is an open issue?)
>>>=20
>>> On Tue, Nov 5, 2019 at 5:02 PM Mark Nottingham <mnot@mnot.net> =
wrote:
>>> Previously, we've moved to the 'late-stage process' documented at =
[1] for the Transport and TLS drafts. The chairs and editors now feel =
that it's time to move the Recovery, HTTP/3, and QPACK drafts to that =
process as well.
>>>=20
>>> As before, this is because we're getting to a stage we feel the =
documents would benefit from slower and slightly more formal process, so =
that the rate of change is not so high, changes that do occur are =
well-vetted, and the documents get closer to reflecting consensus in the =
working group.
>>>=20
>>> If we do this, we're saying that we have gained consensus on what =
remains in these documents, excepting their outstanding issues. As per =
our charter:
>>>=20
>>> """
>>> 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.
>>> """
>>>=20
>>> That doesn't mean that new issues can't be raised against those =
drafts. However, new issues against them will be judged for whether they =
contain new information (in particular, security or interoperability =
impact), a clear technical defect, or have significant (in the judgement =
of the chairs) support for further discussion. If the issue isn't =
well-described or atomic, it may be closed with a request to refactor, =
or refactored for you.
>>>=20
>>> Again, this does not affect editorial issues.
>>>=20
>>> Practically speaking, it means that new issues will be triaged by =
the Chairs -- not the editors (although they can still "claim" purely =
editorial issues) -- and those that don't meet the criteria above will =
be closed. Those that do will be labeled (again, by the Chairs only) as =
`design`.
>>>=20
>>> It also means that all of the closed `design` issues against these =
drafts will be marked as `has-consensus`. Additionally, the `quicv2` =
issues against them will be closed and marked `has-consensus`.
>>>=20
>>> The issues that will be labeled `has-consensus` (and closed, if =
still open) are listed here:
>>>=20
>>> =
https://github.com/quicwg/base-drafts/issues?q=3Dis%3Aissue+is%3Aclosed+la=
bel%3Adesign+-label%3Ahas-consensus+-label%3A-transport+-label%3A-tls
>>>=20
>>> We believe that all of these issues have been discussed and the =
group has formed consensus on them; this only formalises that.
>>>=20
>>> If you have concerns or questions, please discuss them on-list; =
barring pushback, we'll adopt this on 15-Nov-2019.
>>>=20
>>> Cheers,
>>>=20
>>> 1. =
https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md#late-sta=
ge-process
>>>=20
>>> --
>>> Mark and Lars, QUIC WG Chairs
>>>=20
>> --
>> Mark Nottingham   https://www.mnot.net/
>=20
>=20

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


From nobody Mon Nov 11 07:40:39 2019
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 E3A281208AB for <quic@ietfa.amsl.com>; Mon, 11 Nov 2019 07:40:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 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] 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 ZLhzpHxSuYUq for <quic@ietfa.amsl.com>; Mon, 11 Nov 2019 07:40:35 -0800 (PST)
Received: from NAM05-CO1-obe.outbound.protection.outlook.com (mail-eopbgr720120.outbound.protection.outlook.com [40.107.72.120]) (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 016D91208AA for <quic@ietf.org>; Mon, 11 Nov 2019 07:40:34 -0800 (PST)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=IY3RhHpyOgZPT4WJHW1zY01373RDxW71TQihCWNMag7soOc0xthpQs8CbyAmd3Jrx2XJWFbAwERcMgNvTcQ84qH9VYyEuqxqmq7gg9GczB5eMsqNh4tfWI7caaI7wzeju/crm9mszJJcAZqOIur4OtMVhdl61KhOmTvqCYzFMOYRjmJq1peFmhER5FgXFG3r0fLg7Wx1K/tRNIVmHBPmD/R4NhR406nFQQGLw1IBSPbPbbL0aHff0roeOBy8b8gK+1T1Nos6g4bc7NeHegbkJ+VSZy5wRbJKYSwKKlpuA1cUywqqAV5LvhcuetdIFfZy+HLDpIuBRSQz78E7zA0pCg==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=si0JOoq6m87GSun8Ui0Pw7Hv+8CpxZKXPy/atMXGzxg=; b=IfSs09KPCjYKqlmWg+CTYP+QarTtYguIXIs5YmogBWuvAWTSmMawyGJawRp12QeygCculgOQ0C21jgfGNJ7ZaZQySQRvrJj+HYORGNb8cI2KryKqpcbSOqoqNiUT4ycvGiT20LJ0QQG2fz9jShV38SbooIOHYKQRzDdpd18jZuOopHWvTANu8grlqlbhjXMVqQZrharME6sQYRMc7r7SlRGm2jXEZ77ebIn24HvL/oXyuREaabfYe71Q0RADDOcbJDiXJTwqEvhrkmrAzGP8vcRvvFG4PFWDW3EOwCeriCCprhlel7pr79z7LmajafxeTWpsisoGhJuLboVLBaZ5PA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=evequefou.be; dmarc=pass action=none header.from=evequefou.be; dkim=pass header.d=evequefou.be; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=evequefou.onmicrosoft.com; s=selector2-evequefou-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=si0JOoq6m87GSun8Ui0Pw7Hv+8CpxZKXPy/atMXGzxg=; b=kbqbU93dmd6Uti8W7zh1UAPQv5izsxyUfMw+fhBZLB7riIF5IDTBCTbUI1cIdFHjFihXOG8BOdZ+W1uAdMtCQ+0WUflu5Zojrsd/wbV5f5szDCZinjO8+8pSpJlFcyLcMHLjyaNs6GpF/x3V1wTNNLMzrXpcbuJt85g9JddEyNw=
Received: from DM6PR22MB2010.namprd22.prod.outlook.com (20.180.22.24) by DM6PR22MB1995.namprd22.prod.outlook.com (20.180.22.15) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2430.20; Mon, 11 Nov 2019 15:40:32 +0000
Received: from DM6PR22MB2010.namprd22.prod.outlook.com ([fe80::90a7:a476:168f:f85e]) by DM6PR22MB2010.namprd22.prod.outlook.com ([fe80::90a7:a476:168f:f85e%5]) with mapi id 15.20.2430.027; Mon, 11 Nov 2019 15:40:32 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Mark Nottingham <mnot@mnot.net>, Roy Fielding <fielding@gbiv.com>
CC: Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
Thread-Topic: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
Thread-Index: AQHVlD3tOlesd/HkOkytkq7/DuTcZKd+epaAgAazwQCAAPUcMA==
Date: Mon, 11 Nov 2019 15:40:32 +0000
Message-ID: <DM6PR22MB20101F0D1CC9867D5F3EE865DA740@DM6PR22MB2010.namprd22.prod.outlook.com>
References: <6A43BEC7-F9DE-40C9-BF70-BF1618EAFE01@mnot.net> <88BCFF39-6F9D-4E03-8787-561EECBBACE4@gbiv.com> <FD5201A5-C179-4302-B437-57561FB8DB24@mnot.net>
In-Reply-To: <FD5201A5-C179-4302-B437-57561FB8DB24@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: [2600:2b00:931f:a301:c4a5:f2a0:f9fe:398f]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: fb27c5d9-b9a1-4081-8675-08d766bd7d01
x-ms-traffictypediagnostic: DM6PR22MB1995:
x-ms-exchange-purlcount: 1
x-microsoft-antispam-prvs: <DM6PR22MB1995E76292AF7AAE1609478FDA740@DM6PR22MB1995.namprd22.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0218A015FA
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(136003)(346002)(376002)(366004)(396003)(39830400003)(52314003)(13464003)(189003)(199004)(53546011)(186003)(54906003)(6436002)(86362001)(66446008)(6116002)(305945005)(55016002)(66946007)(66476007)(66556008)(76116006)(64756008)(102836004)(14444005)(256004)(508600001)(316002)(6246003)(71200400001)(71190400001)(229853002)(110136005)(74316002)(81156014)(7736002)(6506007)(25786009)(76176011)(7696005)(561944003)(81166006)(9686003)(14454004)(33656002)(46003)(99286004)(11346002)(476003)(2906002)(4326008)(966005)(6306002)(5660300002)(8676002)(446003)(52536014)(486006)(8936002); DIR:OUT; SFP:1102; SCL:1; SRVR:DM6PR22MB1995; H:DM6PR22MB2010.namprd22.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; MX:1; A:1; 
received-spf: None (protection.outlook.com: evequefou.be does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: ykcZ5sEk0D2NfHL+RXZXwNSgIFbNnHWnQYGhnTPV+sE/7BSWCmqtCTcidbXkpQrg3VlPyB36NGgfB1FzIhCthhdygbwoEvrxM5Zv+3Z20M244FONDgdBpIpKe5CypQo4upvLwrp+1HCA4bx8onyRcxwYMCSx9Y2PGyNdsYo8yRTFU62F4i/pgRcMA+rez4TJcBktcLOI/iFXVBCM1o8kvCTGOJA54M7inycyixyaMf8xzLAjaEQMe9ND9Rergh0yZqEPtACDsX+b2FWOzcR3WVQbANqTyKQPUNdCLblqXQqJ5FrbTJWzx09OErSxoBCUAvYFW8/QrST3u2czXaQ0oj8O085MGhy+/1L/tjU++P9tWdP+fzarwGaxysBp8SQnN0cmEFQfNq63l6ifqF4r6ih+TY6wKNZw0krWCfIbbRe7EOXuVSRSozv52Nos5Os9zYeyITNoYWtR9agHm5FQx5KuQLFTQdJ3m8sWP0U0+J4=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-Network-Message-Id: fb27c5d9-b9a1-4081-8675-08d766bd7d01
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Nov 2019 15:40:32.7233 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 41eaf50b-882d-47eb-8c4c-0b5b76a9da8f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: vcjdXwX3cCPatP0OmYDOH9nRyDik563CVqVARq/50Qmdu7Q//TkoPjeTzzmEf8hxtfFQkNp7n+XatmyZf94Cdw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR22MB1995
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/URiz_VSr-riLgOEaFW0xb21ICTc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Nov 2019 15:40:38 -0000

I'll also note that it's relatively easy from a spec perspective to allow t=
railers to arrive before the end of the body, or to allow multiple sets of =
trailers to arrive.  I suspect most clients won't process trailers until th=
ey have the body anyway, but the real question is what clients do with mult=
iple trailer sets.  I'm not certain whether that's in our scope or not, but=
 that's a separate conversation.  Feel free to open an issue for that speci=
fic discussion.

-----Original Message-----
From: QUIC <quic-bounces@ietf.org> On Behalf Of Mark Nottingham
Sent: Sunday, November 10, 2019 8:01 PM
To: Roy Fielding <fielding@gbiv.com>
Cc: Lars Eggert <lars@eggert.org>; IETF QUIC WG <quic@ietf.org>
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the L=
ate-Stage Process

Hi Roy,

Responding to the parts relevant to this CfC.

> On 7 Nov 2019, at 5:39 am, Roy T. Fielding <fielding@gbiv.com> wrote:
>=20
>> On Nov 5, 2019, at 5:01 PM, Mark Nottingham <mnot@mnot.net> wrote:
>>=20
>> Previously, we've moved to the 'late-stage process' documented at [1] fo=
r the Transport and TLS drafts. The chairs and editors now feel that it's t=
ime to move the Recovery, HTTP/3, and QPACK drafts to that process as well.
>>=20
>> As before, this is because we're getting to a stage we feel the document=
s would benefit from slower and slightly more formal process, so that the r=
ate of change is not so high, changes that do occur are well-vetted, and th=
e documents get closer to reflecting consensus in the working group.
>=20
> I don't think that process has worked well for QUIC.

Noted.

> There are specific issues that are contentious enough to timebox and=20
> conclude, in a formal (and faster) fashion than was done before.
> That makes sense when needed for a specific issue. I don't know of any=20
> such issues for those three drafts. IOW, I don't know of any issues=20
> for which it makes sense for the Chairs to pre-empt the specification=20
> authors in deciding what can or cannot result in changes to the drafts=20
> just because of the timing of when the issue was raised.

You misunderstand the process; the Chairs aren't pre-empting anything, the =
group is attempting to agree to a path to completing this work.

> The late-stage process seems to focus all of our energy into=20
> in/out-of-scope arguments rather than actual text in the specifications.

I don't see any evidence for that claim; what makes you believe that?

> The last interim spent easily twice as much time discussing process=20
> and process planning than it did HTTP/3. Prior interims were worse.

We spent a day talking about transport and TLS, part of a morning talking a=
bout planning the future of our work (if you want to call that "process and=
 process planning") and the bulk of the (longer) afternoon session talking =
about H3. This isn't surprising, since our goal for the meeting was to get =
the Transport and TLS documents close to finished.

> I don't even recall the last time contents of the HTTP/3 spec being=20
> discussed on list, outside of very specific issues related to transport.
> I would like to see HTTP/3 written with HTTP in mind, not as a set of=20
> diffs against h2.

That is by charter; we're largely limited to mapping H2 onto QUIC.=20

> This is not a small undertaking, but it isn't a massive one either.
> Basically, import the bits of h2 that are necessary to explain=20
> HTTP/3's operation and intent, and then start referencing the=20
> http-core drafts instead of 723x. Yes, I know that is risky, but it is th=
e right thing to do.
> And it needs to be done before http-core is finished, since that=20
> effort exists largely to place the right content (in the right places)=20
> for
> HTTP/3 to reference.

AIUI that is still our intent, and shouldn't be impeded by the late-stage p=
rocess, since that work should be editorial.

> I have no idea what the status is with QPACK, but we should learn a=20
> lesson from the last time and make sure the fixed compression=20
> dictionary (if any) is based on traffic at more than one proxy or=20
> origin server. Or at least have each of the major deployments generate=20
> their local "best" encoding and do some cross-testing of the N choices=20
> (plus one or two based on a hand-crafted expert merge).
>=20
> I would like for HTTP/3 to have a mechanism for communicating metadata=20
> (like trailers) in mid-stream, both for requests (e.g., priority) and=20
> responses (e.g., chained sigs). That has been a design goal for HTTP=20
> since 1995 or so. HTTP/1.1 had it, albeit limited to chunked extensions.
> It has been proposed multiple times and keeps getting postponed=20
> because of "concern about scope". This is not a semantics issue (they=20
> are just optional trailers that arrive early) -- it is a multiplex=20
> framing issue (a new frame type and expectation to process).

Where are the multiple proposals you refer to? We've been working on h3 now=
 for more than three years. If you submit them now, they'll be design issue=
s.

I'd say that the Late-Stage process (or at least the proposal of adopting i=
t) is working exactly as intended here -- making people realise that if the=
y still have issues / changes that they want discussed, they need to bring =
them to our attention now, not as we go to WGLC.

Cheers,

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


From nobody Mon Nov 11 08:58:00 2019
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 E7EA1120A17 for <quic@ietfa.amsl.com>; Mon, 11 Nov 2019 08:57:58 -0800 (PST)
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, DKIMWL_WL_MED=-0.001, 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_HELO_NONE=0.001, SPF_PASS=-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 ZSnDg94AwuXw for <quic@ietfa.amsl.com>; Mon, 11 Nov 2019 08:57:56 -0800 (PST)
Received: from mail-wm1-x32c.google.com (mail-wm1-x32c.google.com [IPv6:2a00:1450:4864:20::32c]) (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 87565120A0E for <quic@ietf.org>; Mon, 11 Nov 2019 08:57:56 -0800 (PST)
Received: by mail-wm1-x32c.google.com with SMTP id b11so12879wmb.5 for <quic@ietf.org>; Mon, 11 Nov 2019 08:57:56 -0800 (PST)
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=m2xHm/M3DEfBdwV5ZdywobemmWeOEtM1fd4OWHtOQUQ=; b=qtjTEqzXHixCI7uQu0EKXIBA/Ds/U6NIkHrCojXFk1oPcYfgk2RUFaycaFtGQGsLFh x4dDVDmVF8xsK5llQLZw3rNBmshOu11mTC/NWfr0DKbN4etFRFRe9rYXMIKLWoVSbqL+ hh/fYnR0klDfHHTSsQZpo/jM+eNi80M4zinCuWroFp/8+taqq9PtmBUoo7gHwc/AVjKT af8ZxhHic43ZDY+MJx1uijB+FQiP5KRLEBI1DNiSBZLPc+KCyvzq3QCeiXOiQhmTFMNS xKET1NEmUARveGr2XdsciT4y+qJkVxUkIeGny7rZtqaNOUAgtGkdVYGVfZpZ3N2H8J/G 37KQ==
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=m2xHm/M3DEfBdwV5ZdywobemmWeOEtM1fd4OWHtOQUQ=; b=sa/H9NE4NW47wOFuiCmuc4vx5EHdzh8pPAJKqrmVmcYXNQsKknRgyhX9EUWM3kGOp8 0P/WsvQkId6DUHoPEY9TNIRMe6qAOw3mXgdY5+YvynlnyYhYlEzRFOz1qkGdoFgB183j eOe25eeLadBaaZpp/DQtrRRor2IqG2YiFIKQvHhA6r9IUoTyrIjJz4ik61TGfheoM4m/ l4/pSF4dz8mAoR5dnS1qZsYzuH8rkoiqG3PyeN896R5OlGXuiRFBfV1BZhO7wxAX+amm dXo7mR+pD0VGd9+CfyM4AFC9Q4+vc8f9GbdsZEqneqiLseuhChoGXyXXuwa+dQ+RPvaS k1dA==
X-Gm-Message-State: APjAAAWpVrhjmQbfZaKbg3rFTfxliqz4aEJng0em1MyzobfKGUEnug3e FE7AcfndKAmVT3ZY1vxoSgLUNi6yistRi+HNxloTfw==
X-Google-Smtp-Source: APXvYqx8N4DA7ereCCTAip36WxcCDxlVGCiaGzdBwr+U2WtyytGXz0P2F+N2LtzwCS9wBCR5kP3w79sKede/Bpcamfo=
X-Received: by 2002:a1c:4e1a:: with SMTP id g26mr21930067wmh.138.1573491474681;  Mon, 11 Nov 2019 08:57:54 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+6E79OySoOLbJ8eWp0J-+3yeB5iGvj6sW19bEDn_V7-NA@mail.gmail.com> <CABcZeBN+6p2k+Kj4K5oKNEqKV50aAU6FLGkiZG0dGPNkg1s_-A@mail.gmail.com> <376bcf21-b18f-9199-8054-47122419e1d4@huitema.net>
In-Reply-To: <376bcf21-b18f-9199-8054-47122419e1d4@huitema.net>
From: Ian Swett <ianswett@google.com>
Date: Mon, 11 Nov 2019 11:57:40 -0500
Message-ID: <CAKcm_gM370SxB1UAt3HYfepzQTH4Z+_H8=zAVMdZu322VsONyQ@mail.gmail.com>
Subject: Re: Version Ossification: Intended Scope for QUICv1
To: Christian Huitema <huitema@huitema.net>
Cc: Eric Rescorla <ekr@rtfm.com>, David Schinazi <dschinazi.ietf@gmail.com>, QUIC <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000068613d059715083d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/vwW17zz3gdSVXGL9YKdwEV-QYII>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Nov 2019 16:57:59 -0000

--00000000000068613d059715083d
Content-Type: text/plain; charset="UTF-8"

+1 from me as well.

I think this is useful work and I support the QUIC WG working on it, but I
don't believe it needs to be included in v1 and I'd like to get some
deployment experience with it before standardizing it.

On Sun, Nov 10, 2019 at 7:48 PM Christian Huitema <huitema@huitema.net>
wrote:

>
> On 11/10/2019 2:53 PM, Eric Rescorla wrote:
> > I would actually like to suggest something more aggressive (or,
> > conservative, if you prefer), namely that we punt version ossification
> > entirely to the future, whether to an extension or QUIVc2. In support
> > of this proposal, I would make three points:
> >
> > - We are actually going to be running concurrent versions for quite
> >   some time. Even if everyone were to aggressively (say 6-12 months)
> >   deprecate all the draft versions upon shipping the RFC, we're
> >   looking at something that's 18-24 months out. And of course,
> >   I expect people to do some simple version greasing. So, that
> >   probably buys us some time before real bad ossification sets
> >   in.
> >
> > - It's turning out to be surprisingly hard to design a mechanism that
> >   works, as evidenced by David's mechanism. And to that, I would add
> >   that anything that involves having a server hand out some new set of
> >   keys/salts is going to run into the same kind of multi-CDN problems
> >   we had with ESNI (i.e., failures when you get switched between
> >   CDNs). And then recovering from that cleanly either seems to mean
> >   some ESNI-style fallback or allowing a middlebox to forge VN to
> >   force you back to the published version/salt.
> >
> > - It seems like this would all be a lot easier if we had ESNI, because
> >   you could tie the use of the new salt/version to the ESNIConfig
> >   (either as a public or symmetric key, depending on taste).
> >
> > So what I would propose is that we put this problem on ice for now and
> > then revisit it as an extension. All of the proposals that we have
> > seen seem like they could be done as an extension, and then we can (1)
> > get QUICv1 done and (2) hopefully leverage ESNI once we have some
> > experience.
>
> +1
>
> -- Christian Huitema
>
>

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

<div dir=3D"ltr">+1 from me as well.<br><div><br></div><div>I think this is=
 useful work and I support the QUIC WG working on it, but I don&#39;t belie=
ve it needs to be included in v1 and I&#39;d like to get some deployment ex=
perience=C2=A0with it before standardizing it.</div></div><br><div class=3D=
"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Nov 10, 2019 at=
 7:48 PM Christian Huitema &lt;<a href=3D"mailto:huitema@huitema.net">huite=
ma@huitema.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex"><br>
On 11/10/2019 2:53 PM, Eric Rescorla wrote:<br>
&gt; I would actually like to suggest something more aggressive (or,<br>
&gt; conservative, if you prefer), namely that we punt version ossification=
<br>
&gt; entirely to the future, whether to an extension or QUIVc2. In support<=
br>
&gt; of this proposal, I would make three points:<br>
&gt;<br>
&gt; - We are actually going to be running concurrent versions for quite<br=
>
&gt; =C2=A0 some time. Even if everyone were to aggressively (say 6-12 mont=
hs)<br>
&gt; =C2=A0 deprecate all the draft versions upon shipping the RFC, we&#39;=
re<br>
&gt; =C2=A0 looking at something that&#39;s 18-24 months out. And of course=
,<br>
&gt; =C2=A0 I expect people to do some simple version greasing. So, that<br=
>
&gt; =C2=A0 probably buys us some time before real bad ossification sets<br=
>
&gt; =C2=A0 in.<br>
&gt;<br>
&gt; - It&#39;s turning out to be surprisingly hard to design a mechanism t=
hat<br>
&gt; =C2=A0 works, as evidenced by David&#39;s mechanism. And to that, I wo=
uld add<br>
&gt; =C2=A0 that anything that involves having a server hand out some new s=
et of<br>
&gt; =C2=A0 keys/salts is going to run into the same kind of multi-CDN prob=
lems<br>
&gt; =C2=A0 we had with ESNI (i.e., failures when you get switched between<=
br>
&gt; =C2=A0 CDNs). And then recovering from that cleanly either seems to me=
an<br>
&gt; =C2=A0 some ESNI-style fallback or allowing a middlebox to forge VN to=
<br>
&gt; =C2=A0 force you back to the published version/salt.<br>
&gt;<br>
&gt; - It seems like this would all be a lot easier if we had ESNI, because=
<br>
&gt; =C2=A0 you could tie the use of the new salt/version to the ESNIConfig=
<br>
&gt; =C2=A0 (either as a public or symmetric key, depending on taste).<br>
&gt;<br>
&gt; So what I would propose is that we put this problem on ice for now and=
<br>
&gt; then revisit it as an extension. All of the proposals that we have<br>
&gt; seen seem like they could be done as an extension, and then we can (1)=
<br>
&gt; get QUICv1 done and (2) hopefully leverage ESNI once we have some<br>
&gt; experience.<br>
<br>
+1<br>
<br>
-- Christian Huitema<br>
<br>
</blockquote></div>

--00000000000068613d059715083d--


From nobody Mon Nov 11 14:39:43 2019
Return-Path: <prvs=6218ac5d69=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 91714120020 for <quic@ietfa.amsl.com>; Mon, 11 Nov 2019 14:39:41 -0800 (PST)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=fb.com header.b=oFsNoSKv; dkim=pass (1024-bit key) header.d=fb.onmicrosoft.com header.b=OTND1Dsl
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 YIHL3frRDUy6 for <quic@ietfa.amsl.com>; Mon, 11 Nov 2019 14:39:39 -0800 (PST)
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 87EE1120041 for <quic@ietf.org>; Mon, 11 Nov 2019 14:39:39 -0800 (PST)
Received: from pps.filterd (m0148460.ppops.net [127.0.0.1]) by mx0a-00082601.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id xABMdMTI012366; Mon, 11 Nov 2019 14:39:30 -0800
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=x6xNTygMlBLZRlxtzv1rELklrfl1HeiykvSwxf9YpB0=; b=oFsNoSKvCiuZ06ipsB24ccddEtIp6sroYXmsOeK8qT0hHLVWKr3MmH5KnAocr2hSZCfW 4aP1vKnooe6RlQg8j3A3f9LXM8sfkK93EYkLQ/A/4AQ5qbUeKvpfW5Z0JHm7YS/lfYxn gloELF8c7Kd9pfLnSMBbDq9Uz8J8Ts+4KTY= 
Received: from mail.thefacebook.com (mailout.thefacebook.com [199.201.64.23]) by mx0a-00082601.pphosted.com with ESMTP id 2w5uup3r29-8 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Mon, 11 Nov 2019 14:39:30 -0800
Received: from prn-mbx06.TheFacebook.com (2620:10d:c081:6::20) by prn-hub02.TheFacebook.com (2620:10d:c081:35::126) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1713.5; Mon, 11 Nov 2019 14:39:20 -0800
Received: from prn-hub04.TheFacebook.com (2620:10d:c081:35::128) by prn-mbx06.TheFacebook.com (2620:10d:c081:6::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1713.5; Mon, 11 Nov 2019 14:39:20 -0800
Received: from NAM04-SN1-obe.outbound.protection.outlook.com (192.168.54.28) by o365-in.thefacebook.com (192.168.16.28) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1713.5 via Frontend Transport; Mon, 11 Nov 2019 14:39:19 -0800
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=DRpT7wWRlcwsJjxhn5cyrTrNtZNpKtwofmOrN73k41Iqf3Qjg9TD9Yj3CCh5LRw8A1WrPNSUwbIfbbw9K2fzTqbMJtddg5xVE24r3GuSTT4kyzwTdI/cZ+COEZyWjl+ivuGqKrX7s0DCLqk9VWWWWQNxxV1aFzh9U0yEGwOawpx2HrMtTRyZRTmqSgdEUrF6GB0vEWpyS2a0QgMoAwX61vVZcKO1xP7mhAbJNiTBfrNfJbDjAQicU126E/b/+SbQCxa2mWg3r6F1XcTOZRGmDJJ1ka/2viEhinoHcPhfuV6i2hN3wDGtQDJsTdVBPNtCVy0hEIeIPIBlTvZUNpB5Dw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=x6xNTygMlBLZRlxtzv1rELklrfl1HeiykvSwxf9YpB0=; b=XY/fj88qlVvEHhvqypKopkfEBn20tbZr6qf6VJaRdjmAxdnrbi5acNOT+H8F32P1lhqAj/aEA5EN5cI6TYpW3iv6K4wxG2G5mblRlt3CHJQWJ43IoCIeRpYH+PQCsG5QNClMmWM1k1vyTVN/6SAa8l0So9yXxcHHTkuCNi7OsqiPEUtu5j/j6RmAyL+e9wLTroDbnJYUuZcIdp5xcbUvx+RLLhskRc5Tmivs27x0C2bfVxcveNxLdHlWEi3OpqMjsZfxllKjS3Ro2VHFtuoXDSDI2yLnSQMvF8sezK6cx+QLCHm5N95dUTv2MgljsGr/seQF21e/666IgRhR/n2zow==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=fb.com; dmarc=pass action=none header.from=fb.com; dkim=pass header.d=fb.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fb.onmicrosoft.com; s=selector2-fb-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=x6xNTygMlBLZRlxtzv1rELklrfl1HeiykvSwxf9YpB0=; b=OTND1DslTEMBYerRxGnjVpPM/iDIFf6lAu+v+LF0RdW5KIkuvqfHvn7D5lfLZgiN9x5ua+qQFlQzljHqiqnWfVE3hQdMpKVrBibLUa6y8A8CJj/DkhaznZI2DoL1si6IRDFI68205GjdYJb3M/rieTGVKBpJctuzyfbdgnYXjX8=
Received: from CY4PR15MB1542.namprd15.prod.outlook.com (10.172.160.9) by CY4PR15MB1896.namprd15.prod.outlook.com (10.172.78.147) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2430.23; Mon, 11 Nov 2019 22:39:16 +0000
Received: from CY4PR15MB1542.namprd15.prod.outlook.com ([fe80::402f:bad9:499:3990]) by CY4PR15MB1542.namprd15.prod.outlook.com ([fe80::402f:bad9:499:3990%7]) with mapi id 15.20.2430.027; Mon, 11 Nov 2019 22:39:16 +0000
From: Roberto Peon <fenix@fb.com>
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Christian Huitema <huitema@huitema.net>
CC: David Schinazi <dschinazi.ietf@gmail.com>, Eric Rescorla <ekr@rtfm.com>, QUIC <quic@ietf.org>
Subject: Re: Version Ossification: Intended Scope for QUICv1
Thread-Topic: Version Ossification: Intended Scope for QUICv1
Thread-Index: AQHVkDAO7yzpycYWtkiZjN24Gl8Z2KeFEvIAgAAgEwCAAQ7bAP//2VSA
Date: Mon, 11 Nov 2019 22:39:16 +0000
Message-ID: <CB0D90CE-39AB-4FFA-BF9C-8967D5F73FF2@fb.com>
References: <CAPDSy+6E79OySoOLbJ8eWp0J-+3yeB5iGvj6sW19bEDn_V7-NA@mail.gmail.com> <CABcZeBN+6p2k+Kj4K5oKNEqKV50aAU6FLGkiZG0dGPNkg1s_-A@mail.gmail.com> <376bcf21-b18f-9199-8054-47122419e1d4@huitema.net> <CAKcm_gM370SxB1UAt3HYfepzQTH4Z+_H8=zAVMdZu322VsONyQ@mail.gmail.com>
In-Reply-To: <CAKcm_gM370SxB1UAt3HYfepzQTH4Z+_H8=zAVMdZu322VsONyQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/10.1e.1.191020
x-originating-ip: [199.201.64.137]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 2dec8a78-84c1-4abe-6511-08d766f7fc15
x-ms-traffictypediagnostic: CY4PR15MB1896:
x-microsoft-antispam-prvs: <CY4PR15MB189678B484ABF63DFEBC3F04CD740@CY4PR15MB1896.namprd15.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-forefront-prvs: 0218A015FA
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(366004)(136003)(346002)(376002)(39860400002)(396003)(189003)(199004)(186003)(66946007)(76116006)(66476007)(229853002)(91956017)(66556008)(6486002)(561944003)(66446008)(86362001)(64756008)(236005)(8676002)(7736002)(81156014)(6306002)(54896002)(6512007)(33656002)(81166006)(4326008)(256004)(6436002)(8936002)(6246003)(316002)(54906003)(110136005)(58126008)(99286004)(26005)(76176011)(3846002)(6116002)(6506007)(53546011)(2906002)(102836004)(486006)(478600001)(5660300002)(66066001)(14454004)(2616005)(11346002)(71200400001)(446003)(36756003)(71190400001)(25786009)(476003); DIR:OUT; SFP:1102; SCL:1; SRVR:CY4PR15MB1896; H:CY4PR15MB1542.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-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: CaIgExCi1nYlQqJsxS8yPkv4DeEoPr40nwbaTnL29iC4fslYRQTUsh7QfcBmbwPH7xqfMEH2tWFolhpZqRe9Fox2jDcH8DjE1ZLuwhoSQkHkkV0H+uVqoekFtc9lSCgbmogDg+Bp4aUIjWu+tvUEx0GuEOhKws/e0BE8J+v3t7aUzwO1JSHKd4NjzC3RRgYG2Ib3RgDzIxLVUzsO+3wHmhDUfSPddFP4c+W7hvIyehInLwsMW/GREQ6/JSrOCGEBqRfuHN28k3m+Ex0vlPryYi04nbAuV/hHDyM1R1iYbH9kLdrmtYo1ObTwsQ5VfpasgCvjN5ZdfwFYc/ku06/Fx6LDuTR2TtUV4SM8WyTyf6vTQH7GU4pMXMZ9bMpA6/dMMwY8fjTB3FtnYa/scw/SO6jE9nHTwifql+/2+WlnrW1GSg3D2aegQz6uOPNcWI+l
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CB0D90CE39AB4FFABF9C8967D5F73FF2fbcom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 2dec8a78-84c1-4abe-6511-08d766f7fc15
X-MS-Exchange-CrossTenant-originalarrivaltime: 11 Nov 2019 22:39:16.7710 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 8ae927fe-1255-47a7-a2af-5f3a069daaa2
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: tLE6dI9bFpK3M9sSnjKq5J06IQJvfNvEHBcI8TEokP/TEFdMCOHjwFVKD++G+zDB
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY4PR15MB1896
X-OriginatorOrg: fb.com
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-11-11_07:2019-11-11,2019-11-11 signatures=0
X-Proofpoint-Spam-Details: rule=fb_default_notspam policy=fb_default score=0 adultscore=0 phishscore=0 mlxlogscore=914 priorityscore=1501 malwarescore=0 lowpriorityscore=0 spamscore=0 suspectscore=0 mlxscore=0 impostorscore=0 bulkscore=0 clxscore=1011 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1911110192
X-FB-Internal: deliver
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/MX5C9zXXS5mLr76lPEz7XUpt1Lw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 11 Nov 2019 22:39:42 -0000

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

SSB3b3VsZCBsb3ZlIHRvIHNlZSBhIHYyIHRoYXQgaW50ZW5kcyB0byBhZGRyZXNzIHRoaXMgY2hh
cnRlcmVkIGJlZm9yZSBhZ3JlZWluZyB0aGF0IHRoaXMgc2hvdWxkbuKAmXQgYmUgaW5jbHVkZWQu
DQotPVINCg0KRnJvbTogUVVJQyA8cXVpYy1ib3VuY2VzQGlldGYub3JnPiBvbiBiZWhhbGYgb2Yg
SWFuIFN3ZXR0IDxpYW5zd2V0dD00MGdvb2dsZS5jb21AZG1hcmMuaWV0Zi5vcmc+DQpEYXRlOiBN
b25kYXksIE5vdmVtYmVyIDExLCAyMDE5IGF0IDg6NTggQU0NClRvOiBDaHJpc3RpYW4gSHVpdGVt
YSA8aHVpdGVtYUBodWl0ZW1hLm5ldD4NCkNjOiBEYXZpZCBTY2hpbmF6aSA8ZHNjaGluYXppLmll
dGZAZ21haWwuY29tPiwgRXJpYyBSZXNjb3JsYSA8ZWtyQHJ0Zm0uY29tPiwgUVVJQyA8cXVpY0Bp
ZXRmLm9yZz4NClN1YmplY3Q6IFJlOiBWZXJzaW9uIE9zc2lmaWNhdGlvbjogSW50ZW5kZWQgU2Nv
cGUgZm9yIFFVSUN2MQ0KDQorMSBmcm9tIG1lIGFzIHdlbGwuDQoNCkkgdGhpbmsgdGhpcyBpcyB1
c2VmdWwgd29yayBhbmQgSSBzdXBwb3J0IHRoZSBRVUlDIFdHIHdvcmtpbmcgb24gaXQsIGJ1dCBJ
IGRvbid0IGJlbGlldmUgaXQgbmVlZHMgdG8gYmUgaW5jbHVkZWQgaW4gdjEgYW5kIEknZCBsaWtl
IHRvIGdldCBzb21lIGRlcGxveW1lbnQgZXhwZXJpZW5jZSB3aXRoIGl0IGJlZm9yZSBzdGFuZGFy
ZGl6aW5nIGl0Lg0KDQpPbiBTdW4sIE5vdiAxMCwgMjAxOSBhdCA3OjQ4IFBNIENocmlzdGlhbiBI
dWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PG1haWx0bzpodWl0ZW1hQGh1aXRlbWEubmV0Pj4g
d3JvdGU6DQoNCk9uIDExLzEwLzIwMTkgMjo1MyBQTSwgRXJpYyBSZXNjb3JsYSB3cm90ZToNCj4g
SSB3b3VsZCBhY3R1YWxseSBsaWtlIHRvIHN1Z2dlc3Qgc29tZXRoaW5nIG1vcmUgYWdncmVzc2l2
ZSAob3IsDQo+IGNvbnNlcnZhdGl2ZSwgaWYgeW91IHByZWZlciksIG5hbWVseSB0aGF0IHdlIHB1
bnQgdmVyc2lvbiBvc3NpZmljYXRpb24NCj4gZW50aXJlbHkgdG8gdGhlIGZ1dHVyZSwgd2hldGhl
ciB0byBhbiBleHRlbnNpb24gb3IgUVVJVmMyLiBJbiBzdXBwb3J0DQo+IG9mIHRoaXMgcHJvcG9z
YWwsIEkgd291bGQgbWFrZSB0aHJlZSBwb2ludHM6DQo+DQo+IC0gV2UgYXJlIGFjdHVhbGx5IGdv
aW5nIHRvIGJlIHJ1bm5pbmcgY29uY3VycmVudCB2ZXJzaW9ucyBmb3IgcXVpdGUNCj4gICBzb21l
IHRpbWUuIEV2ZW4gaWYgZXZlcnlvbmUgd2VyZSB0byBhZ2dyZXNzaXZlbHkgKHNheSA2LTEyIG1v
bnRocykNCj4gICBkZXByZWNhdGUgYWxsIHRoZSBkcmFmdCB2ZXJzaW9ucyB1cG9uIHNoaXBwaW5n
IHRoZSBSRkMsIHdlJ3JlDQo+ICAgbG9va2luZyBhdCBzb21ldGhpbmcgdGhhdCdzIDE4LTI0IG1v
bnRocyBvdXQuIEFuZCBvZiBjb3Vyc2UsDQo+ICAgSSBleHBlY3QgcGVvcGxlIHRvIGRvIHNvbWUg
c2ltcGxlIHZlcnNpb24gZ3JlYXNpbmcuIFNvLCB0aGF0DQo+ICAgcHJvYmFibHkgYnV5cyB1cyBz
b21lIHRpbWUgYmVmb3JlIHJlYWwgYmFkIG9zc2lmaWNhdGlvbiBzZXRzDQo+ICAgaW4uDQo+DQo+
IC0gSXQncyB0dXJuaW5nIG91dCB0byBiZSBzdXJwcmlzaW5nbHkgaGFyZCB0byBkZXNpZ24gYSBt
ZWNoYW5pc20gdGhhdA0KPiAgIHdvcmtzLCBhcyBldmlkZW5jZWQgYnkgRGF2aWQncyBtZWNoYW5p
c20uIEFuZCB0byB0aGF0LCBJIHdvdWxkIGFkZA0KPiAgIHRoYXQgYW55dGhpbmcgdGhhdCBpbnZv
bHZlcyBoYXZpbmcgYSBzZXJ2ZXIgaGFuZCBvdXQgc29tZSBuZXcgc2V0IG9mDQo+ICAga2V5cy9z
YWx0cyBpcyBnb2luZyB0byBydW4gaW50byB0aGUgc2FtZSBraW5kIG9mIG11bHRpLUNETiBwcm9i
bGVtcw0KPiAgIHdlIGhhZCB3aXRoIEVTTkkgKGkuZS4sIGZhaWx1cmVzIHdoZW4geW91IGdldCBz
d2l0Y2hlZCBiZXR3ZWVuDQo+ICAgQ0ROcykuIEFuZCB0aGVuIHJlY292ZXJpbmcgZnJvbSB0aGF0
IGNsZWFubHkgZWl0aGVyIHNlZW1zIHRvIG1lYW4NCj4gICBzb21lIEVTTkktc3R5bGUgZmFsbGJh
Y2sgb3IgYWxsb3dpbmcgYSBtaWRkbGVib3ggdG8gZm9yZ2UgVk4gdG8NCj4gICBmb3JjZSB5b3Ug
YmFjayB0byB0aGUgcHVibGlzaGVkIHZlcnNpb24vc2FsdC4NCj4NCj4gLSBJdCBzZWVtcyBsaWtl
IHRoaXMgd291bGQgYWxsIGJlIGEgbG90IGVhc2llciBpZiB3ZSBoYWQgRVNOSSwgYmVjYXVzZQ0K
PiAgIHlvdSBjb3VsZCB0aWUgdGhlIHVzZSBvZiB0aGUgbmV3IHNhbHQvdmVyc2lvbiB0byB0aGUg
RVNOSUNvbmZpZw0KPiAgIChlaXRoZXIgYXMgYSBwdWJsaWMgb3Igc3ltbWV0cmljIGtleSwgZGVw
ZW5kaW5nIG9uIHRhc3RlKS4NCj4NCj4gU28gd2hhdCBJIHdvdWxkIHByb3Bvc2UgaXMgdGhhdCB3
ZSBwdXQgdGhpcyBwcm9ibGVtIG9uIGljZSBmb3Igbm93IGFuZA0KPiB0aGVuIHJldmlzaXQgaXQg
YXMgYW4gZXh0ZW5zaW9uLiBBbGwgb2YgdGhlIHByb3Bvc2FscyB0aGF0IHdlIGhhdmUNCj4gc2Vl
biBzZWVtIGxpa2UgdGhleSBjb3VsZCBiZSBkb25lIGFzIGFuIGV4dGVuc2lvbiwgYW5kIHRoZW4g
d2UgY2FuICgxKQ0KPiBnZXQgUVVJQ3YxIGRvbmUgYW5kICgyKSBob3BlZnVsbHkgbGV2ZXJhZ2Ug
RVNOSSBvbmNlIHdlIGhhdmUgc29tZQ0KPiBleHBlcmllbmNlLg0KDQorMQ0KDQotLSBDaHJpc3Rp
YW4gSHVpdGVtYQ0K

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

PGh0bWwgeG1sbnM6bz0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6b2ZmaWNlIiB4
bWxuczp3PSJ1cm46c2NoZW1hcy1taWNyb3NvZnQtY29tOm9mZmljZTp3b3JkIiB4bWxuczptPSJo
dHRwOi8vc2NoZW1hcy5taWNyb3NvZnQuY29tL29mZmljZS8yMDA0LzEyL29tbWwiIHhtbG5zPSJo
dHRwOi8vd3d3LnczLm9yZy9UUi9SRUMtaHRtbDQwIj4NCjxoZWFkPg0KPG1ldGEgaHR0cC1lcXVp
dj0iQ29udGVudC1UeXBlIiBjb250ZW50PSJ0ZXh0L2h0bWw7IGNoYXJzZXQ9dXRmLTgiPg0KPG1l
dGEgbmFtZT0iR2VuZXJhdG9yIiBjb250ZW50PSJNaWNyb3NvZnQgV29yZCAxNSAoZmlsdGVyZWQg
bWVkaXVtKSI+DQo8c3R5bGU+PCEtLQ0KLyogRm9udCBEZWZpbml0aW9ucyAqLw0KQGZvbnQtZmFj
ZQ0KCXtmb250LWZhbWlseTpNYW5nYWw7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDIgMyAzIDIgMjt9
DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJDYW1icmlhIE1hdGgiOw0KCXBhbm9zZS0xOjIg
NCA1IDMgNSA0IDYgMyAyIDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDYWxpYnJpOw0K
CXBhbm9zZS0xOjIgMTUgNSAyIDIgMiA0IDMgMiA0O30NCi8qIFN0eWxlIERlZmluaXRpb25zICov
DQpwLk1zb05vcm1hbCwgbGkuTXNvTm9ybWFsLCBkaXYuTXNvTm9ybWFsDQoJe21hcmdpbjowaW47
DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1p
bHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBzcGFuLk1zb0h5cGVybGluaw0KCXtt
c28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0ZXh0LWRlY29yYXRpb246dW5k
ZXJsaW5lO30NCmE6dmlzaXRlZCwgc3Bhbi5Nc29IeXBlcmxpbmtGb2xsb3dlZA0KCXttc28tc3R5
bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6cHVycGxlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxp
bmU7fQ0KcC5tc29ub3JtYWwwLCBsaS5tc29ub3JtYWwwLCBkaXYubXNvbm9ybWFsMA0KCXttc28t
c3R5bGUtbmFtZTptc29ub3JtYWw7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2lu
LXJpZ2h0OjBpbjsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDow
aW47DQoJZm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJp
Zjt9DQpzcGFuLkVtYWlsU3R5bGUxOA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsN
Cglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30N
Ci5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6
ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1h
cmdpbjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6
V29yZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJFTi1VUyIg
bGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlvbjEiPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+SSB3b3VsZCBsb3ZlIHRvIHNlZSBhIHYyIHRoYXQgaW50ZW5k
cyB0byBhZGRyZXNzIHRoaXMgY2hhcnRlcmVkIGJlZm9yZSBhZ3JlZWluZyB0aGF0IHRoaXMgc2hv
dWxkbuKAmXQgYmUgaW5jbHVkZWQuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij4tPVI8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9v
OnA+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjQjVDNERG
IDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Y29sb3I6YmxhY2siPkZyb206IDwvc3Bh
bj48L2I+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMi4wcHQ7Y29sb3I6YmxhY2siPlFVSUMgJmx0
O3F1aWMtYm91bmNlc0BpZXRmLm9yZyZndDsgb24gYmVoYWxmIG9mIElhbiBTd2V0dCAmbHQ7aWFu
c3dldHQ9NDBnb29nbGUuY29tQGRtYXJjLmlldGYub3JnJmd0Ozxicj4NCjxiPkRhdGU6IDwvYj5N
b25kYXksIE5vdmVtYmVyIDExLCAyMDE5IGF0IDg6NTggQU08YnI+DQo8Yj5UbzogPC9iPkNocmlz
dGlhbiBIdWl0ZW1hICZsdDtodWl0ZW1hQGh1aXRlbWEubmV0Jmd0Ozxicj4NCjxiPkNjOiA8L2I+
RGF2aWQgU2NoaW5hemkgJmx0O2RzY2hpbmF6aS5pZXRmQGdtYWlsLmNvbSZndDssIEVyaWMgUmVz
Y29ybGEgJmx0O2VrckBydGZtLmNvbSZndDssIFFVSUMgJmx0O3F1aWNAaWV0Zi5vcmcmZ3Q7PGJy
Pg0KPGI+U3ViamVjdDogPC9iPlJlOiBWZXJzaW9uIE9zc2lmaWNhdGlvbjogSW50ZW5kZWQgU2Nv
cGUgZm9yIFFVSUN2MTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+JiM0MzsxIGZyb20gbWUgYXMgd2VsbC48bzpwPjwvbzpwPjwvcD4N
CjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkgdGhpbmsgdGhpcyBpcyB1c2VmdWwgd29y
ayBhbmQgSSBzdXBwb3J0IHRoZSBRVUlDIFdHIHdvcmtpbmcgb24gaXQsIGJ1dCBJIGRvbid0IGJl
bGlldmUgaXQgbmVlZHMgdG8gYmUgaW5jbHVkZWQgaW4gdjEgYW5kIEknZCBsaWtlIHRvIGdldCBz
b21lIGRlcGxveW1lbnQgZXhwZXJpZW5jZSZuYnNwO3dpdGggaXQgYmVmb3JlIHN0YW5kYXJkaXpp
bmcgaXQuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPk9uIFN1biwgTm92IDEwLCAyMDE5IGF0IDc6NDggUE0gQ2hyaXN0aWFuIEh1aXRlbWEgJmx0
OzxhIGhyZWY9Im1haWx0bzpodWl0ZW1hQGh1aXRlbWEubmV0Ij5odWl0ZW1hQGh1aXRlbWEubmV0
PC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxl
PSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGlu
IDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPjxicj4NCk9uIDEx
LzEwLzIwMTkgMjo1MyBQTSwgRXJpYyBSZXNjb3JsYSB3cm90ZTo8YnI+DQomZ3Q7IEkgd291bGQg
YWN0dWFsbHkgbGlrZSB0byBzdWdnZXN0IHNvbWV0aGluZyBtb3JlIGFnZ3Jlc3NpdmUgKG9yLDxi
cj4NCiZndDsgY29uc2VydmF0aXZlLCBpZiB5b3UgcHJlZmVyKSwgbmFtZWx5IHRoYXQgd2UgcHVu
dCB2ZXJzaW9uIG9zc2lmaWNhdGlvbjxicj4NCiZndDsgZW50aXJlbHkgdG8gdGhlIGZ1dHVyZSwg
d2hldGhlciB0byBhbiBleHRlbnNpb24gb3IgUVVJVmMyLiBJbiBzdXBwb3J0PGJyPg0KJmd0OyBv
ZiB0aGlzIHByb3Bvc2FsLCBJIHdvdWxkIG1ha2UgdGhyZWUgcG9pbnRzOjxicj4NCiZndDs8YnI+
DQomZ3Q7IC0gV2UgYXJlIGFjdHVhbGx5IGdvaW5nIHRvIGJlIHJ1bm5pbmcgY29uY3VycmVudCB2
ZXJzaW9ucyBmb3IgcXVpdGU8YnI+DQomZ3Q7ICZuYnNwOyBzb21lIHRpbWUuIEV2ZW4gaWYgZXZl
cnlvbmUgd2VyZSB0byBhZ2dyZXNzaXZlbHkgKHNheSA2LTEyIG1vbnRocyk8YnI+DQomZ3Q7ICZu
YnNwOyBkZXByZWNhdGUgYWxsIHRoZSBkcmFmdCB2ZXJzaW9ucyB1cG9uIHNoaXBwaW5nIHRoZSBS
RkMsIHdlJ3JlPGJyPg0KJmd0OyAmbmJzcDsgbG9va2luZyBhdCBzb21ldGhpbmcgdGhhdCdzIDE4
LTI0IG1vbnRocyBvdXQuIEFuZCBvZiBjb3Vyc2UsPGJyPg0KJmd0OyAmbmJzcDsgSSBleHBlY3Qg
cGVvcGxlIHRvIGRvIHNvbWUgc2ltcGxlIHZlcnNpb24gZ3JlYXNpbmcuIFNvLCB0aGF0PGJyPg0K
Jmd0OyAmbmJzcDsgcHJvYmFibHkgYnV5cyB1cyBzb21lIHRpbWUgYmVmb3JlIHJlYWwgYmFkIG9z
c2lmaWNhdGlvbiBzZXRzPGJyPg0KJmd0OyAmbmJzcDsgaW4uPGJyPg0KJmd0Ozxicj4NCiZndDsg
LSBJdCdzIHR1cm5pbmcgb3V0IHRvIGJlIHN1cnByaXNpbmdseSBoYXJkIHRvIGRlc2lnbiBhIG1l
Y2hhbmlzbSB0aGF0PGJyPg0KJmd0OyAmbmJzcDsgd29ya3MsIGFzIGV2aWRlbmNlZCBieSBEYXZp
ZCdzIG1lY2hhbmlzbS4gQW5kIHRvIHRoYXQsIEkgd291bGQgYWRkPGJyPg0KJmd0OyAmbmJzcDsg
dGhhdCBhbnl0aGluZyB0aGF0IGludm9sdmVzIGhhdmluZyBhIHNlcnZlciBoYW5kIG91dCBzb21l
IG5ldyBzZXQgb2Y8YnI+DQomZ3Q7ICZuYnNwOyBrZXlzL3NhbHRzIGlzIGdvaW5nIHRvIHJ1biBp
bnRvIHRoZSBzYW1lIGtpbmQgb2YgbXVsdGktQ0ROIHByb2JsZW1zPGJyPg0KJmd0OyAmbmJzcDsg
d2UgaGFkIHdpdGggRVNOSSAoaS5lLiwgZmFpbHVyZXMgd2hlbiB5b3UgZ2V0IHN3aXRjaGVkIGJl
dHdlZW48YnI+DQomZ3Q7ICZuYnNwOyBDRE5zKS4gQW5kIHRoZW4gcmVjb3ZlcmluZyBmcm9tIHRo
YXQgY2xlYW5seSBlaXRoZXIgc2VlbXMgdG8gbWVhbjxicj4NCiZndDsgJm5ic3A7IHNvbWUgRVNO
SS1zdHlsZSBmYWxsYmFjayBvciBhbGxvd2luZyBhIG1pZGRsZWJveCB0byBmb3JnZSBWTiB0bzxi
cj4NCiZndDsgJm5ic3A7IGZvcmNlIHlvdSBiYWNrIHRvIHRoZSBwdWJsaXNoZWQgdmVyc2lvbi9z
YWx0Ljxicj4NCiZndDs8YnI+DQomZ3Q7IC0gSXQgc2VlbXMgbGlrZSB0aGlzIHdvdWxkIGFsbCBi
ZSBhIGxvdCBlYXNpZXIgaWYgd2UgaGFkIEVTTkksIGJlY2F1c2U8YnI+DQomZ3Q7ICZuYnNwOyB5
b3UgY291bGQgdGllIHRoZSB1c2Ugb2YgdGhlIG5ldyBzYWx0L3ZlcnNpb24gdG8gdGhlIEVTTklD
b25maWc8YnI+DQomZ3Q7ICZuYnNwOyAoZWl0aGVyIGFzIGEgcHVibGljIG9yIHN5bW1ldHJpYyBr
ZXksIGRlcGVuZGluZyBvbiB0YXN0ZSkuPGJyPg0KJmd0Ozxicj4NCiZndDsgU28gd2hhdCBJIHdv
dWxkIHByb3Bvc2UgaXMgdGhhdCB3ZSBwdXQgdGhpcyBwcm9ibGVtIG9uIGljZSBmb3Igbm93IGFu
ZDxicj4NCiZndDsgdGhlbiByZXZpc2l0IGl0IGFzIGFuIGV4dGVuc2lvbi4gQWxsIG9mIHRoZSBw
cm9wb3NhbHMgdGhhdCB3ZSBoYXZlPGJyPg0KJmd0OyBzZWVuIHNlZW0gbGlrZSB0aGV5IGNvdWxk
IGJlIGRvbmUgYXMgYW4gZXh0ZW5zaW9uLCBhbmQgdGhlbiB3ZSBjYW4gKDEpPGJyPg0KJmd0OyBn
ZXQgUVVJQ3YxIGRvbmUgYW5kICgyKSBob3BlZnVsbHkgbGV2ZXJhZ2UgRVNOSSBvbmNlIHdlIGhh
dmUgc29tZTxicj4NCiZndDsgZXhwZXJpZW5jZS48YnI+DQo8YnI+DQomIzQzOzE8YnI+DQo8YnI+
DQotLSBDaHJpc3RpYW4gSHVpdGVtYTxvOnA+PC9vOnA+PC9wPg0KPC9ibG9ja3F1b3RlPg0KPC9k
aXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_CB0D90CE39AB4FFABF9C8967D5F73FF2fbcom_--


From nobody Mon Nov 11 18:01:25 2019
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 BA4811200CE for <quic@ietfa.amsl.com>; Mon, 11 Nov 2019 18:01:22 -0800 (PST)
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_HELO_NONE=0.001, 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 wyhg3Bknw70U for <quic@ietfa.amsl.com>; Mon, 11 Nov 2019 18:01:20 -0800 (PST)
Received: from mail-lj1-x243.google.com (mail-lj1-x243.google.com [IPv6:2a00:1450:4864:20::243]) (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 C0DA6120041 for <quic@ietf.org>; Mon, 11 Nov 2019 18:01:19 -0800 (PST)
Received: by mail-lj1-x243.google.com with SMTP id d22so4397591lji.8 for <quic@ietf.org>; Mon, 11 Nov 2019 18:01:19 -0800 (PST)
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=/7Cl/O5ZO+eOXsEM2/nPiTtUj4MdHjUeNsvmia7ewU8=; b=YEcEjk4Y1Yt9ttLtMAvbhMxmzb0w5sqHnh6DK5H+sAS44z7VK5UyT9DuR11q8/DDCh vponSqHUX43LHUv5Nk99mXDSDldvmmv8nG8+nbHEKzm+liIviL8J0JpFR8EGThDhkbyU kWNWfUz5e6XbDsFeGgwDYwLlvcfhQGKyWKwi4im93WE29nVzgtgr6ItUAYWBAShR3Oi5 i2FJKSKHKJecM9WaYVyrqKL2T/32l46pB47HlVOfy5l6d2/AGZEQsn1lgRCM/AnnksUz W4zgxZK9M3dfPGsWEWhE+3RBK9gakvGEz9+wua5varQZDq8Yek2W1dlOR4UGUwutpXGw GgjQ==
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=/7Cl/O5ZO+eOXsEM2/nPiTtUj4MdHjUeNsvmia7ewU8=; b=Ukj85xJc8BNDxhL7eZIHuZzFvFfF1eQTWr9et4A1SVovPTTE4pUwVbEtG+lO2mCBS6 VkqvwMcldn93Ou326fviMMxjYIJ0ggJ6QXb1YTO8Jih6I3ns0RiFY76/fyB+3RR2D79L l44n9kpolM83GIjcRVtsOKNm6wRbSRbbEBeGiK9/odjVQuahfumY9topbWc0I21UFasa ESqmrkFw05/WWLhMzh/OQ7i/1DU5Z324cw8EdM+JBl5k3FHfy1mQkb3t+xcYeq/4so7I NCNKPfGqJsfWyPdF3DKjPo542yrvnFd5b4rCcuXVf2PHmw59IwtuNZ40ji6j96QZHxXa DYoA==
X-Gm-Message-State: APjAAAVejFewn/4lI7mL/SKaTiD/CcnshrvyFQpRzVvYkQExZLUrqOUZ hpmdATMkSbmoQiJqdYochX52ACx0QFK59M2gIxI=
X-Google-Smtp-Source: APXvYqx4w8cXaXVddWwtIktJgP2MKqM8LM7TyBxbWzAZxfE4JBH8r6XR/CUQkehGoHSG/c1xvugyuuQMrQOhTsn8ar0=
X-Received: by 2002:a2e:b4da:: with SMTP id r26mr3819951ljm.153.1573524077765;  Mon, 11 Nov 2019 18:01:17 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+6E79OySoOLbJ8eWp0J-+3yeB5iGvj6sW19bEDn_V7-NA@mail.gmail.com> <CABcZeBN+6p2k+Kj4K5oKNEqKV50aAU6FLGkiZG0dGPNkg1s_-A@mail.gmail.com> <376bcf21-b18f-9199-8054-47122419e1d4@huitema.net> <CAKcm_gM370SxB1UAt3HYfepzQTH4Z+_H8=zAVMdZu322VsONyQ@mail.gmail.com> <CB0D90CE-39AB-4FFA-BF9C-8967D5F73FF2@fb.com>
In-Reply-To: <CB0D90CE-39AB-4FFA-BF9C-8967D5F73FF2@fb.com>
From: Marten Seemann <martenseemann@gmail.com>
Date: Tue, 12 Nov 2019 09:01:06 +0700
Message-ID: <CAOYVs2p3iTdxqQ76WDxYMZbn_oL6Gvvvvsvzn0UJxyXvzY+Uqw@mail.gmail.com>
Subject: Re: Version Ossification: Intended Scope for QUICv1
To: Roberto Peon <fenix@fb.com>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>,  Christian Huitema <huitema@huitema.net>, David Schinazi <dschinazi.ietf@gmail.com>,  Eric Rescorla <ekr@rtfm.com>, QUIC <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b3679f05971c9f41"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/qpE6U4ZvPwcoJsYRt1miYCq8_EE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Nov 2019 02:01:23 -0000

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

>
> I would actually like to suggest something more aggressive (or,
> conservative, if you prefer), namely that we punt version ossification
> entirely to the future, whether to an extension or QUIVc2.


I'm not sure if I can agree with this assessment. While we will have
multiple QUIC versions deployed at the same time, the salts used to encrypt
the Initial packets are all public. Middlebox vendors can easily build a
device that is able to decrypt any of these versions. The fact that draft
versions + QUIC v1 will (hopefully) work tells us little about how
middleboxes will handle unknown version, i.e. versions that they don't know
how to decrypt. This suggests to me that building a greasing mechanisms
which ensures that packets with unknown version numbers are sent over the
wire is essential for QUIC v1.

On Tue, Nov 12, 2019 at 5:39 AM Roberto Peon <fenix@fb.com> wrote:

> I would love to see a v2 that intends to address this chartered before
> agreeing that this shouldn=E2=80=99t be included.
>
> -=3DR
>
>
>
> *From: *QUIC <quic-bounces@ietf.org> on behalf of Ian Swett <ianswett=3D
> 40google.com@dmarc.ietf.org>
> *Date: *Monday, November 11, 2019 at 8:58 AM
> *To: *Christian Huitema <huitema@huitema.net>
> *Cc: *David Schinazi <dschinazi.ietf@gmail.com>, Eric Rescorla <
> ekr@rtfm.com>, QUIC <quic@ietf.org>
> *Subject: *Re: Version Ossification: Intended Scope for QUICv1
>
>
>
> +1 from me as well.
>
>
>
> I think this is useful work and I support the QUIC WG working on it, but =
I
> don't believe it needs to be included in v1 and I'd like to get some
> deployment experience with it before standardizing it.
>
>
>
> On Sun, Nov 10, 2019 at 7:48 PM Christian Huitema <huitema@huitema.net>
> wrote:
>
>
> On 11/10/2019 2:53 PM, Eric Rescorla wrote:
> > I would actually like to suggest something more aggressive (or,
> > conservative, if you prefer), namely that we punt version ossification
> > entirely to the future, whether to an extension or QUIVc2. In support
> > of this proposal, I would make three points:
> >
> > - We are actually going to be running concurrent versions for quite
> >   some time. Even if everyone were to aggressively (say 6-12 months)
> >   deprecate all the draft versions upon shipping the RFC, we're
> >   looking at something that's 18-24 months out. And of course,
> >   I expect people to do some simple version greasing. So, that
> >   probably buys us some time before real bad ossification sets
> >   in.
> >
> > - It's turning out to be surprisingly hard to design a mechanism that
> >   works, as evidenced by David's mechanism. And to that, I would add
> >   that anything that involves having a server hand out some new set of
> >   keys/salts is going to run into the same kind of multi-CDN problems
> >   we had with ESNI (i.e., failures when you get switched between
> >   CDNs). And then recovering from that cleanly either seems to mean
> >   some ESNI-style fallback or allowing a middlebox to forge VN to
> >   force you back to the published version/salt.
> >
> > - It seems like this would all be a lot easier if we had ESNI, because
> >   you could tie the use of the new salt/version to the ESNIConfig
> >   (either as a public or symmetric key, depending on taste).
> >
> > So what I would propose is that we put this problem on ice for now and
> > then revisit it as an extension. All of the proposals that we have
> > seen seem like they could be done as an extension, and then we can (1)
> > get QUICv1 done and (2) hopefully leverage ESNI once we have some
> > experience.
>
> +1
>
> -- Christian Huitema
>
>

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

<div dir=3D"ltr"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I would =
actually like to suggest something more aggressive (or,<br>conservative, if=
 you prefer), namely that we punt version ossification<br>entirely to the f=
uture, whether to an extension or QUIVc2.</blockquote><div><br></div><div>I=
&#39;m not sure if I can agree with this assessment. While we will have mul=
tiple QUIC versions deployed at the same time, the salts used to encrypt th=
e Initial packets are all public. Middlebox vendors can easily build a devi=
ce that is able to decrypt any of these versions. The fact that draft versi=
ons=C2=A0+ QUIC v1 will (hopefully) work tells us little about how middlebo=
xes will handle unknown version, i.e. versions that they don&#39;t know how=
 to decrypt. This suggests to me that building a greasing mechanisms which =
ensures that packets with unknown version numbers are sent over the wire is=
 essential for QUIC v1.<br></div></div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D"gmail_attr">On Tue, Nov 12, 2019 at 5:39 AM Roberto Pe=
on &lt;<a href=3D"mailto:fenix@fb.com">fenix@fb.com</a>&gt; wrote:<br></div=
><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border=
-left:1px solid rgb(204,204,204);padding-left:1ex">





<div lang=3D"EN-US">
<div class=3D"gmail-m_3457971078829826757WordSection1">
<p class=3D"MsoNormal">I would love to see a v2 that intends to address thi=
s chartered before agreeing that this shouldn=E2=80=99t be included.<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-color:rgb(181,196,223) currentcolor currentcolor;borde=
r-style:solid none none;border-width:1pt medium medium;padding:3pt 0in 0in"=
>
<p class=3D"MsoNormal"><b><span style=3D"font-size:12pt;color:black">From: =
</span></b><span style=3D"font-size:12pt;color:black">QUIC &lt;<a href=3D"m=
ailto:quic-bounces@ietf.org" target=3D"_blank">quic-bounces@ietf.org</a>&gt=
; on behalf of Ian Swett &lt;ianswett=3D<a href=3D"mailto:40google.com@dmar=
c.ietf.org" target=3D"_blank">40google.com@dmarc.ietf.org</a>&gt;<br>
<b>Date: </b>Monday, November 11, 2019 at 8:58 AM<br>
<b>To: </b>Christian Huitema &lt;<a href=3D"mailto:huitema@huitema.net" tar=
get=3D"_blank">huitema@huitema.net</a>&gt;<br>
<b>Cc: </b>David Schinazi &lt;<a href=3D"mailto:dschinazi.ietf@gmail.com" t=
arget=3D"_blank">dschinazi.ietf@gmail.com</a>&gt;, Eric Rescorla &lt;<a hre=
f=3D"mailto:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt;, QUIC &lt;=
<a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic@ietf.org</a>&gt;<br=
>
<b>Subject: </b>Re: Version Ossification: Intended Scope for QUICv1<u></u><=
u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">+1 from me as well.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I think this is useful work and I support the QUIC W=
G working on it, but I don&#39;t believe it needs to be included in v1 and =
I&#39;d like to get some deployment experience=C2=A0with it before standard=
izing it.<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Sun, Nov 10, 2019 at 7:48 PM Christian Huitema &l=
t;<a href=3D"mailto:huitema@huitema.net" target=3D"_blank">huitema@huitema.=
net</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-color:currentcolor currentcolor currentcolor rg=
b(204,204,204);border-style:none none none solid;border-width:medium medium=
 medium 1pt;padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt"><br>
On 11/10/2019 2:53 PM, Eric Rescorla wrote:<br>
&gt; I would actually like to suggest something more aggressive (or,<br>
&gt; conservative, if you prefer), namely that we punt version ossification=
<br>
&gt; entirely to the future, whether to an extension or QUIVc2. In support<=
br>
&gt; of this proposal, I would make three points:<br>
&gt;<br>
&gt; - We are actually going to be running concurrent versions for quite<br=
>
&gt; =C2=A0 some time. Even if everyone were to aggressively (say 6-12 mont=
hs)<br>
&gt; =C2=A0 deprecate all the draft versions upon shipping the RFC, we&#39;=
re<br>
&gt; =C2=A0 looking at something that&#39;s 18-24 months out. And of course=
,<br>
&gt; =C2=A0 I expect people to do some simple version greasing. So, that<br=
>
&gt; =C2=A0 probably buys us some time before real bad ossification sets<br=
>
&gt; =C2=A0 in.<br>
&gt;<br>
&gt; - It&#39;s turning out to be surprisingly hard to design a mechanism t=
hat<br>
&gt; =C2=A0 works, as evidenced by David&#39;s mechanism. And to that, I wo=
uld add<br>
&gt; =C2=A0 that anything that involves having a server hand out some new s=
et of<br>
&gt; =C2=A0 keys/salts is going to run into the same kind of multi-CDN prob=
lems<br>
&gt; =C2=A0 we had with ESNI (i.e., failures when you get switched between<=
br>
&gt; =C2=A0 CDNs). And then recovering from that cleanly either seems to me=
an<br>
&gt; =C2=A0 some ESNI-style fallback or allowing a middlebox to forge VN to=
<br>
&gt; =C2=A0 force you back to the published version/salt.<br>
&gt;<br>
&gt; - It seems like this would all be a lot easier if we had ESNI, because=
<br>
&gt; =C2=A0 you could tie the use of the new salt/version to the ESNIConfig=
<br>
&gt; =C2=A0 (either as a public or symmetric key, depending on taste).<br>
&gt;<br>
&gt; So what I would propose is that we put this problem on ice for now and=
<br>
&gt; then revisit it as an extension. All of the proposals that we have<br>
&gt; seen seem like they could be done as an extension, and then we can (1)=
<br>
&gt; get QUICv1 done and (2) hopefully leverage ESNI once we have some<br>
&gt; experience.<br>
<br>
+1<br>
<br>
-- Christian Huitema<u></u><u></u></p>
</blockquote>
</div>
</div>
</div>

</blockquote></div>

--000000000000b3679f05971c9f41--


From nobody Mon Nov 11 21:11:47 2019
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 2A9941200FB for <quic@ietfa.amsl.com>; Mon, 11 Nov 2019 21:11:45 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 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_HELO_NONE=0.001, SPF_NONE=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=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 jlFalEYFV357 for <quic@ietfa.amsl.com>; Mon, 11 Nov 2019 21:11:41 -0800 (PST)
Received: from mail-lj1-x229.google.com (mail-lj1-x229.google.com [IPv6:2a00:1450:4864:20::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 5C0011200F6 for <quic@ietf.org>; Mon, 11 Nov 2019 21:11:41 -0800 (PST)
Received: by mail-lj1-x229.google.com with SMTP id d5so6759027ljl.4 for <quic@ietf.org>; Mon, 11 Nov 2019 21:11:41 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=g16WNIejUk8/0O8K+V83r5WQw15kUARmZGK/aTJjPtw=; b=gjX6I3lTnmJjp+cs1C7tUoU3dvc02BnylUP4TmQ2lC9dLwj7zTxRXlK+H63QJSQeHB 9/pVStmUz/a0+EBSqQkEWncQHTDzXAt5brajozqIzqycU6D98GsXFcK9BzopHKBz7xIE Ezk5ikgvTpyhvBQ78Pyl3ws9G48UHI+6z5btd8xXWHGrrx4nDaH0BSp2sEZHUc9fAd3k OO5qgyGO2fhHpf06PSsSWDTE5j1XVOc3mpISBvgiNeUaQgyH6P5SEb8DhP9E95vAKS0b CBAKsOlilhhnerCy7f7WzE6/Nnowz0LOh/BuZtutUVxhTNubXp8LKXoshNPn0axSlPk7 dPPQ==
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=g16WNIejUk8/0O8K+V83r5WQw15kUARmZGK/aTJjPtw=; b=pwRFnSyvy/t6iad/CQvr15mO1meGb9SzP72Oer78g8mhDwp/F6gzzB06AHHTyhtf7F ou91Jl49QhnB8m8/sy7BtxXHKVsPuJ3kQ96sot06z6FRdRxURw56tOhAlCJqqSLseBez uTZ1ZK5topRdDIDHQQw9O7vnHIm50JmfsFkNLUNwtxoA05jWrVAyJe53nHJk3rkD/qTH iRhyuSmI/H8CRr8JLQxBXwVROk/qZ0kVmLURyyn9SLSLhVFqTwZtWImHtLBrTL5M/8A2 MOwkHduPa2iOT8shtpf/s1v/U4MrahVNWnAt2Pxk9NM8T7Iws1KRPd4EYb01Z/4qEN4a EieQ==
X-Gm-Message-State: APjAAAVw7sehGyE2qrn8H8veTGqj9hpmvPYfsz8hvHWLW6rg6k5vsPsn hOEA7iRbwvNPa/vigNUqGBIaajbCEcNMxg348hNonQ==
X-Google-Smtp-Source: APXvYqy4/8dSahtvACLrPH9oL1PyaLAa5+GKojPD1LTIUXaaQXw1oYcFw6H2bu7H5+2I1GFrtw0ND/hTGuP9g9dniwk=
X-Received: by 2002:a2e:864f:: with SMTP id i15mr6433627ljj.29.1573535499363;  Mon, 11 Nov 2019 21:11:39 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+6E79OySoOLbJ8eWp0J-+3yeB5iGvj6sW19bEDn_V7-NA@mail.gmail.com> <CABcZeBN+6p2k+Kj4K5oKNEqKV50aAU6FLGkiZG0dGPNkg1s_-A@mail.gmail.com> <376bcf21-b18f-9199-8054-47122419e1d4@huitema.net> <CAKcm_gM370SxB1UAt3HYfepzQTH4Z+_H8=zAVMdZu322VsONyQ@mail.gmail.com> <CB0D90CE-39AB-4FFA-BF9C-8967D5F73FF2@fb.com> <CAOYVs2p3iTdxqQ76WDxYMZbn_oL6Gvvvvsvzn0UJxyXvzY+Uqw@mail.gmail.com>
In-Reply-To: <CAOYVs2p3iTdxqQ76WDxYMZbn_oL6Gvvvvsvzn0UJxyXvzY+Uqw@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Mon, 11 Nov 2019 21:11:02 -0800
Message-ID: <CABcZeBMVKtFAkkd14Xkwo=HRCmVs7OasVh5+SGYkXUoQ6bXgSg@mail.gmail.com>
Subject: Re: Version Ossification: Intended Scope for QUICv1
To: Marten Seemann <martenseemann@gmail.com>
Cc: Roberto Peon <fenix@fb.com>, Ian Swett <ianswett=40google.com@dmarc.ietf.org>,  Christian Huitema <huitema@huitema.net>, David Schinazi <dschinazi.ietf@gmail.com>, QUIC <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007b403005971f4860"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/y86DL1I7vMEiykycYzv96jgXAKM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Nov 2019 05:11:45 -0000

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

On Mon, Nov 11, 2019 at 6:01 PM Marten Seemann <martenseemann@gmail.com>
wrote:

> I would actually like to suggest something more aggressive (or,
>> conservative, if you prefer), namely that we punt version ossification
>> entirely to the future, whether to an extension or QUIVc2.
>
>
> I'm not sure if I can agree with this assessment. While we will have
> multiple QUIC versions deployed at the same time, the salts used to encry=
pt
> the Initial packets are all public. Middlebox vendors can easily build a
> device that is able to decrypt any of these versions.
>

ISTM that this is the scenario of interest for QUICv2 as well, namely that
the protocol will be public but vendors will have to adapt. If they do that
by reading specs and updating prompt, that seems not ideal but acceptable.

-Ekr

The fact that draft versions + QUIC v1 will (hopefully) work tells us
> little about how middleboxes will handle unknown version, i.e. versions
> that they don't know how to decrypt. This suggests to me that building a
> greasing mechanisms which ensures that packets with unknown version numbe=
rs
> are sent over the wire is essential for QUIC v1.
>
> On Tue, Nov 12, 2019 at 5:39 AM Roberto Peon <fenix@fb.com> wrote:
>
>> I would love to see a v2 that intends to address this chartered before
>> agreeing that this shouldn=E2=80=99t be included.
>>
>> -=3DR
>>
>>
>>
>> *From: *QUIC <quic-bounces@ietf.org> on behalf of Ian Swett <ianswett=3D
>> 40google.com@dmarc.ietf.org>
>> *Date: *Monday, November 11, 2019 at 8:58 AM
>> *To: *Christian Huitema <huitema@huitema.net>
>> *Cc: *David Schinazi <dschinazi.ietf@gmail.com>, Eric Rescorla <
>> ekr@rtfm.com>, QUIC <quic@ietf.org>
>> *Subject: *Re: Version Ossification: Intended Scope for QUICv1
>>
>>
>>
>> +1 from me as well.
>>
>>
>>
>> I think this is useful work and I support the QUIC WG working on it, but
>> I don't believe it needs to be included in v1 and I'd like to get some
>> deployment experience with it before standardizing it.
>>
>>
>>
>> On Sun, Nov 10, 2019 at 7:48 PM Christian Huitema <huitema@huitema.net>
>> wrote:
>>
>>
>> On 11/10/2019 2:53 PM, Eric Rescorla wrote:
>> > I would actually like to suggest something more aggressive (or,
>> > conservative, if you prefer), namely that we punt version ossification
>> > entirely to the future, whether to an extension or QUIVc2. In support
>> > of this proposal, I would make three points:
>> >
>> > - We are actually going to be running concurrent versions for quite
>> >   some time. Even if everyone were to aggressively (say 6-12 months)
>> >   deprecate all the draft versions upon shipping the RFC, we're
>> >   looking at something that's 18-24 months out. And of course,
>> >   I expect people to do some simple version greasing. So, that
>> >   probably buys us some time before real bad ossification sets
>> >   in.
>> >
>> > - It's turning out to be surprisingly hard to design a mechanism that
>> >   works, as evidenced by David's mechanism. And to that, I would add
>> >   that anything that involves having a server hand out some new set of
>> >   keys/salts is going to run into the same kind of multi-CDN problems
>> >   we had with ESNI (i.e., failures when you get switched between
>> >   CDNs). And then recovering from that cleanly either seems to mean
>> >   some ESNI-style fallback or allowing a middlebox to forge VN to
>> >   force you back to the published version/salt.
>> >
>> > - It seems like this would all be a lot easier if we had ESNI, because
>> >   you could tie the use of the new salt/version to the ESNIConfig
>> >   (either as a public or symmetric key, depending on taste).
>> >
>> > So what I would propose is that we put this problem on ice for now and
>> > then revisit it as an extension. All of the proposals that we have
>> > seen seem like they could be done as an extension, and then we can (1)
>> > get QUICv1 done and (2) hopefully leverage ESNI once we have some
>> > experience.
>>
>> +1
>>
>> -- Christian Huitema
>>
>>

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

<div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Mon, Nov 11, 2019 at 6:01 PM Marte=
n Seemann &lt;<a href=3D"mailto:martenseemann@gmail.com">martenseemann@gmai=
l.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"ma=
rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:=
1ex"><div dir=3D"ltr"><blockquote class=3D"gmail_quote" style=3D"margin:0px=
 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I w=
ould actually like to suggest something more aggressive (or,<br>conservativ=
e, if you prefer), namely that we punt version ossification<br>entirely to =
the future, whether to an extension or QUIVc2.</blockquote><div><br></div><=
div>I&#39;m not sure if I can agree with this assessment. While we will hav=
e multiple QUIC versions deployed at the same time, the salts used to encry=
pt the Initial packets are all public. Middlebox vendors can easily build a=
 device that is able to decrypt any of these versions. </div></div></blockq=
uote><div><br></div><div>ISTM that this is the scenario of interest for QUI=
Cv2 as well, namely that the protocol will be public but vendors will have =
to adapt. If they do that by reading specs and updating prompt, that seems =
not ideal but acceptable.<br></div><div><br></div><div>-Ekr</div><div><br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><di=
v>The fact that draft versions=C2=A0+ QUIC v1 will (hopefully) work tells u=
s little about how middleboxes will handle unknown version, i.e. versions t=
hat they don&#39;t know how to decrypt. This suggests to me that building a=
 greasing mechanisms which ensures that packets with unknown version number=
s are sent over the wire is essential for QUIC v1.<br></div></div><br><div =
class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Nov 12,=
 2019 at 5:39 AM Roberto Peon &lt;<a href=3D"mailto:fenix@fb.com" target=3D=
"_blank">fenix@fb.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_qu=
ote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,20=
4);padding-left:1ex">





<div lang=3D"EN-US">
<div>
<p class=3D"MsoNormal">I would love to see a v2 that intends to address thi=
s chartered before agreeing that this shouldn=E2=80=99t be included.<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-color:rgb(181,196,223) currentcolor currentcolor;borde=
r-style:solid none none;border-width:1pt medium medium;padding:3pt 0in 0in"=
>
<p class=3D"MsoNormal"><b><span style=3D"font-size:12pt;color:black">From: =
</span></b><span style=3D"font-size:12pt;color:black">QUIC &lt;<a href=3D"m=
ailto:quic-bounces@ietf.org" target=3D"_blank">quic-bounces@ietf.org</a>&gt=
; on behalf of Ian Swett &lt;ianswett=3D<a href=3D"mailto:40google.com@dmar=
c.ietf.org" target=3D"_blank">40google.com@dmarc.ietf.org</a>&gt;<br>
<b>Date: </b>Monday, November 11, 2019 at 8:58 AM<br>
<b>To: </b>Christian Huitema &lt;<a href=3D"mailto:huitema@huitema.net" tar=
get=3D"_blank">huitema@huitema.net</a>&gt;<br>
<b>Cc: </b>David Schinazi &lt;<a href=3D"mailto:dschinazi.ietf@gmail.com" t=
arget=3D"_blank">dschinazi.ietf@gmail.com</a>&gt;, Eric Rescorla &lt;<a hre=
f=3D"mailto:ekr@rtfm.com" target=3D"_blank">ekr@rtfm.com</a>&gt;, QUIC &lt;=
<a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic@ietf.org</a>&gt;<br=
>
<b>Subject: </b>Re: Version Ossification: Intended Scope for QUICv1<u></u><=
u></u></span></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">+1 from me as well.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I think this is useful work and I support the QUIC W=
G working on it, but I don&#39;t believe it needs to be included in v1 and =
I&#39;d like to get some deployment experience=C2=A0with it before standard=
izing it.<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Sun, Nov 10, 2019 at 7:48 PM Christian Huitema &l=
t;<a href=3D"mailto:huitema@huitema.net" target=3D"_blank">huitema@huitema.=
net</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-color:currentcolor currentcolor currentcolor rg=
b(204,204,204);border-style:none none none solid;border-width:medium medium=
 medium 1pt;padding:0in 0in 0in 6pt;margin-left:4.8pt;margin-right:0in">
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt"><br>
On 11/10/2019 2:53 PM, Eric Rescorla wrote:<br>
&gt; I would actually like to suggest something more aggressive (or,<br>
&gt; conservative, if you prefer), namely that we punt version ossification=
<br>
&gt; entirely to the future, whether to an extension or QUIVc2. In support<=
br>
&gt; of this proposal, I would make three points:<br>
&gt;<br>
&gt; - We are actually going to be running concurrent versions for quite<br=
>
&gt; =C2=A0 some time. Even if everyone were to aggressively (say 6-12 mont=
hs)<br>
&gt; =C2=A0 deprecate all the draft versions upon shipping the RFC, we&#39;=
re<br>
&gt; =C2=A0 looking at something that&#39;s 18-24 months out. And of course=
,<br>
&gt; =C2=A0 I expect people to do some simple version greasing. So, that<br=
>
&gt; =C2=A0 probably buys us some time before real bad ossification sets<br=
>
&gt; =C2=A0 in.<br>
&gt;<br>
&gt; - It&#39;s turning out to be surprisingly hard to design a mechanism t=
hat<br>
&gt; =C2=A0 works, as evidenced by David&#39;s mechanism. And to that, I wo=
uld add<br>
&gt; =C2=A0 that anything that involves having a server hand out some new s=
et of<br>
&gt; =C2=A0 keys/salts is going to run into the same kind of multi-CDN prob=
lems<br>
&gt; =C2=A0 we had with ESNI (i.e., failures when you get switched between<=
br>
&gt; =C2=A0 CDNs). And then recovering from that cleanly either seems to me=
an<br>
&gt; =C2=A0 some ESNI-style fallback or allowing a middlebox to forge VN to=
<br>
&gt; =C2=A0 force you back to the published version/salt.<br>
&gt;<br>
&gt; - It seems like this would all be a lot easier if we had ESNI, because=
<br>
&gt; =C2=A0 you could tie the use of the new salt/version to the ESNIConfig=
<br>
&gt; =C2=A0 (either as a public or symmetric key, depending on taste).<br>
&gt;<br>
&gt; So what I would propose is that we put this problem on ice for now and=
<br>
&gt; then revisit it as an extension. All of the proposals that we have<br>
&gt; seen seem like they could be done as an extension, and then we can (1)=
<br>
&gt; get QUICv1 done and (2) hopefully leverage ESNI once we have some<br>
&gt; experience.<br>
<br>
+1<br>
<br>
-- Christian Huitema<u></u><u></u></p>
</blockquote>
</div>
</div>
</div>

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

--0000000000007b403005971f4860--


From nobody Mon Nov 11 21:44:35 2019
Return-Path: <mt@lowentropy.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 1D8021200C7 for <quic@ietfa.amsl.com>; Mon, 11 Nov 2019 21:44:34 -0800 (PST)
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=lowentropy.net header.b=ZbHs7+7s; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=i+nls09z
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 0Kh4uHvXd_j0 for <quic@ietfa.amsl.com>; Mon, 11 Nov 2019 21:44:32 -0800 (PST)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 87D9412001E for <quic@ietf.org>; Mon, 11 Nov 2019 21:44:32 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id C180C4DC for <quic@ietf.org>; Tue, 12 Nov 2019 00:44:31 -0500 (EST)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Tue, 12 Nov 2019 00:44:31 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type; s=fm3; bh=VdqTvf61HHUSmDzIXum166txY38cTpe SiSxraaTbpK8=; b=ZbHs7+7sT3K5VS//yY+z/UsVV6BSJO3M9/E29zPk0ufnn0S T39b1HWtmFx4L1KW6G2VsbjAo5DPsIK+74URJ22gverXx/8rSVR1EajlFL8MnlmC fn+N63jWjaU1YtPU/Q9Wr9IlUyISGhiQBVVP3JUEN+jv4lAyRI2sWM7OfWMY8ln6 xueDeAi/lh4iHPKHmrY+Us+PyobYTXdLtxkWVh0oXkHm0NrNo2U1l2OcllwhOGQu MCsq5gBtck8i0vNj1ADqcMtffR0nq5WwT01c7NwoYixoSXBKfgeTXk884NKsOmOi hUe1Ak3/n8oM/Kh7o/CInHVIus3ByLgq0wrqbNg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=VdqTvf 61HHUSmDzIXum166txY38cTpeSiSxraaTbpK8=; b=i+nls09zvKH3WPMi2c+2fL EhTsc4Mw3NSVxtMUydRJKalDWuG9Stb0o9Ef79Cm35Z/E8ZgPhJVoF/FUg7BzSGx bK7gig47Li8uD4E4Ox3U6DwZaIDqkMz+hDaRswh6j+PGFCOYsx+Q4+x/mi46IUB0 iyYzDlktELD4qy00b6aR+acueISsQpQEJpj5YDEbqhyw/i9Zq9fVm4uFaeNJmThH IDE8GPbaK6BAZdTk5SinPR2RC91kJsRJeWHx/LA7h1lTrOVT3xU8ZNwB5bXe9Ir1 2AxLQdn2nZygniswtyqRXPrZLR0FwolLwAfiNRaOskbCEPvxadGED3JLL9WVmXbw ==
X-ME-Sender: <xms:vkbKXQ9A2HbmWqZe-VG9XG0Tik_byXpJ3Wx7zHhBot4Jhr1gkK-7GA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedruddvkedgfedvucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtsehttd ertderredtnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehloh ifvghnthhrohhphidrnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:vkbKXS_5ZY9DG9_KN38uLe4ugN5i7URYcqdxeGR4CrrmQwNeX_H4zA> <xmx:vkbKXU__4yK0ZRUM1_fJPdLuHO_ef9D_eJV2DA7AxkZ60BzYuAeoNw> <xmx:vkbKXYHNh6-FEfHS5_fSMVE1HKZbuYkBDGqJSxBvlvgrKSWiTXPRNg> <xmx:v0bKXVBQQhbZPW0j-KrRUz8WvM5FOTt187J-7FDb8RshrmjReB4eOg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id DB6E2E00A3; Tue, 12 Nov 2019 00:44:30 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-509-ge3ec61c-fmstable-20191030v1
Mime-Version: 1.0
Message-Id: <c851dd42-d67b-4aae-bf16-96c0363a0c22@www.fastmail.com>
In-Reply-To: <CABcZeBMVKtFAkkd14Xkwo=HRCmVs7OasVh5+SGYkXUoQ6bXgSg@mail.gmail.com>
References: <CAPDSy+6E79OySoOLbJ8eWp0J-+3yeB5iGvj6sW19bEDn_V7-NA@mail.gmail.com> <CABcZeBN+6p2k+Kj4K5oKNEqKV50aAU6FLGkiZG0dGPNkg1s_-A@mail.gmail.com> <376bcf21-b18f-9199-8054-47122419e1d4@huitema.net> <CAKcm_gM370SxB1UAt3HYfepzQTH4Z+_H8=zAVMdZu322VsONyQ@mail.gmail.com> <CB0D90CE-39AB-4FFA-BF9C-8967D5F73FF2@fb.com> <CAOYVs2p3iTdxqQ76WDxYMZbn_oL6Gvvvvsvzn0UJxyXvzY+Uqw@mail.gmail.com> <CABcZeBMVKtFAkkd14Xkwo=HRCmVs7OasVh5+SGYkXUoQ6bXgSg@mail.gmail.com>
Date: Tue, 12 Nov 2019 16:44:00 +1100
From: "Martin Thomson" <mt@lowentropy.net>
To: quic@ietf.org
Subject: Re: Version Ossification: Intended Scope for QUICv1
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/MDxOVQ7V-3FLtlXayB-ooC7cRqs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Nov 2019 05:44:34 -0000

On Tue, Nov 12, 2019, at 16:11, Eric Rescorla wrote:
> ISTM that this is the scenario of interest for QUICv2 as well, namely 
> that the protocol will be public but vendors will have to adapt. If 
> they do that by reading specs and updating prompt, that seems not ideal 
> but acceptable.

Yes, that would be tolerable.  The concern is that they stop at v1 and we can't properly rely on v2 working.


From nobody Mon Nov 11 23:36:15 2019
Return-Path: <lars@eggert.org>
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 82E2D1201AA for <quic@ietfa.amsl.com>; Mon, 11 Nov 2019 23:36:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 MMDHY57Sl2V0 for <quic@ietfa.amsl.com>; Mon, 11 Nov 2019 23:36:10 -0800 (PST)
Received: from emh01.mail.saunalahti.fi (emh01.mail.saunalahti.fi [62.142.5.107]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 38DAE1200A1 for <quic@ietf.org>; Mon, 11 Nov 2019 23:36:10 -0800 (PST)
Received: from eggert.org (unknown [62.248.255.8]) by emh01.mail.saunalahti.fi (Postfix) with ESMTP id 2E3DF2003D for <quic@ietf.org>; Tue, 12 Nov 2019 09:36:07 +0200 (EET)
Received: from slate.eggert.org (Slate.eggert.org [172.19.235.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by eggert.org (Postfix) with ESMTPSA id 30CEA61AD8D for <quic@ietf.org>; Tue, 12 Nov 2019 09:36:03 +0200 (EET)
From: Lars Eggert <lars@eggert.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: Fwd: [tsvwg] New revision of DPLPMTU - Asking for WGLG in Sinagpore
Message-Id: <7435AF2C-9931-4FF7-A2F6-AB1A1C441EA8@eggert.org>
References: <5DC9AE0A.20707@erg.abdn.ac.uk>
To: QUIC IETF mailing list <quic@ietf.org>
Date: Tue, 12 Nov 2019 09:36:03 +0200
X-MailScanner-ID: 30CEA61AD8D.A58D9
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/nPnWJ1fKUenxOOZ_OPhw-ebCsFc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Nov 2019 07:36:13 -0000

This I-D intends to cover QUIC, please review.

Lars

> Begin forwarded message:
>=20
> From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
> Subject: [tsvwg] New revision of DPLPMTU - Asking for WGLG in =
Sinagpore
> Date: November 11, 2019 at 20:52:58 GMT+2
> To: "tsvwg@ietf.org" <tsvwg@ietf.org>
> Reply-To: gorry@erg.abdn.ac.uk
>=20
>=20
> Hi TSVWG'ers and people who helped us get to this stage,
>=20
> Could I ask ask you to look at the latest spec for DLPMTUD?
> https://tools.ietf.org/pdf/draft-ietf-tsvwg-datagram-plpmtud-09.pdf
>=20
> (Please excuse the errors in the table-of-contents - that was not our =
fault).
>=20
> This draft has been around for some time, mainly waiting for us =
editors to get the details correct and readable (at the same time). We =
plan to ask the WG to start the WGLC process at the Singapore IETF =
meeting for draft -09, and it would be great to know that people had =
seen the latest version!
>=20
> best wishes
>=20
> Gorry & the editing team.
>=20


From nobody Tue Nov 12 04:54:23 2019
Return-Path: <lars@eggert.org>
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 032F6120813 for <quic@ietfa.amsl.com>; Tue, 12 Nov 2019 04:54:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.587
X-Spam-Level: 
X-Spam-Status: No, score=-0.587 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_RP_RNBL=1.31, SPF_HELO_NONE=0.001, SPF_NONE=0.001, 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 HPytkoo6CfR1 for <quic@ietfa.amsl.com>; Tue, 12 Nov 2019 04:54:20 -0800 (PST)
Received: from emh02.mail.saunalahti.fi (emh02.mail.saunalahti.fi [62.142.5.108]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 78E3A12013C for <quic@ietf.org>; Tue, 12 Nov 2019 04:54:20 -0800 (PST)
Received: from eggert.org (unknown [62.248.255.8]) by emh02.mail.saunalahti.fi (Postfix) with ESMTP id 0F92E20069 for <quic@ietf.org>; Tue, 12 Nov 2019 14:54:18 +0200 (EET)
From: Lars Eggert <lars@eggert.org>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: Fwd: TSVAREA agenda for IETF-106
Message-Id: <F613BAC3-8744-49CB-8860-8652F7DA56ED@eggert.org>
References: <3015EFF3-A0C6-4725-A13B-CAE4F1E5F9D1@kuehlewind.net>
To: QUIC IETF mailing list <quic@ietf.org>
Date: Tue, 12 Nov 2019 14:54:13 +0200
X-MailScanner-ID: 939C36699CD.A1F7B
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/HTkbqQZXtPWt0Qzeh3lfwcCqBTs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Nov 2019 12:54:22 -0000

Note that there will be chunk of time dedicated in TSVAREA to discuss =
how the IETF might want to split up future work on QUIC application =
bindings and QUIC extensions and maintenance into existing and new WGs.

Lars

> Begin forwarded message:
>=20
> From: Mirja Kuehlewind <ietf@kuehlewind.net>
> Subject: TSVAREA agenda for IETF-106
> Date: November 12, 2019 at 14:46:43 GMT+2
> To: tsv-area@ietf.org
>=20
> Hi all,
>=20
> The agenda for our next tsvarea meeting is online (actually since =
beginning of last week already):
>=20
> https://datatracker.ietf.org/meeting/106/materials/agenda-106-tsvarea
>=20
> We only have a short slot but will take some time to discuss new work =
topics related to QUIC. The TSV ADs will meeting before the session with =
the ART ADs and QUIC chairs and we should be able to report back for =
that.
>=20
> See you soon in Singapore or remotely!
>=20
> Mirja and Margnus (from remote)
>=20
>=20


From nobody Tue Nov 12 05:19:24 2019
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 4FE781200DB for <quic@ietfa.amsl.com>; Tue, 12 Nov 2019 05:19:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level: 
X-Spam-Status: No, score=-1.996 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_HELO_NONE=0.001, 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 pyEMs9XZXAU4 for <quic@ietfa.amsl.com>; Tue, 12 Nov 2019 05:19:18 -0800 (PST)
Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (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 1528112002E for <quic@ietf.org>; Tue, 12 Nov 2019 05:19:18 -0800 (PST)
Received: by mail-ed1-x533.google.com with SMTP id a21so14869917edj.8 for <quic@ietf.org>; Tue, 12 Nov 2019 05:19:18 -0800 (PST)
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=M8W956sIkDbuMuImUTi9V8uFM5NCQ/YI3OR8B0hc9JU=; b=Sjoanft4pRuBHk9NsEXhTzE8tccVg5G1vRMSstyun4ifBgfXAWVKJitraE9Yez3zE2 pebmWoM+egthWffVwz+TXXZ80WF5x5eWN9jmQazldF5F25Rr24O0g8blTI9G9ZKysiB+ 7h4vNVhfnlOJQjn2r6ZPaIQTFd8W7CL2zps+WOp1X1ILES3lBnDX4K7uCURytCGVHq1E LoW6crM3q9ziRIxilA4uVGNvTlbj6obhOXoYxtPKOSqGHNuUbyUMbUc6+Mdy0KkvpscH uQleciVDbcQ1Knp6k+1OkuZkhkB15JjCsmDnbeMEoepT0i6USakSRsHIq23gdkdP8sTG hCnQ==
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=M8W956sIkDbuMuImUTi9V8uFM5NCQ/YI3OR8B0hc9JU=; b=edithoR2wMb9h6L4EDl7ENjKAIzOM9FaWQYwbX28/R311/6vY7xQPIipxRdZe3wZ0m isjFVXw0Fhdc25Fu/RJh/gPUamBaxpfVusefJ1GYbLR9kF4WupVDBm0vLXIf00rWGc6p Ia1Zojmcp6EEg3uSKoUGMN3mzOGwMZNNumfo5ZnoeRBt4PTL9JLbR3U2lJjuLWRfsAf8 /n/g/BN8Gzxa5RiJf5EzITcXjpcONj2SxqcxGG6wmqb5sRRqMu6ZzJgBCmX3WGiRMsg8 PsA/XltwLxni3Gv1HJh92HTsXo4WnvrB6RndS8M3fMW1e+Q2HFdmHDSQeNefNuqNnRJW 7OjA==
X-Gm-Message-State: APjAAAXhlmIsDjl30ojRz6oKdGg6xsDu+ZquwvQj72oaqX/oe0qdHbZu lNBt3h3Hlx0m0wctSm0dAwbyzs4VSwi0x7yopCXNtBn5
X-Google-Smtp-Source: APXvYqyoHTXi0b+BfST3HXD1f3SKNKorLT+wZqigzvDEhEkWhsJztB4hfmbk2SHa/3n6EAol8fYcmdq5PDtKMuj5M88=
X-Received: by 2002:a05:6402:488:: with SMTP id k8mr32530366edv.293.1573564756598;  Tue, 12 Nov 2019 05:19:16 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Tue, 12 Nov 2019 14:19:15 +0100
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <F613BAC3-8744-49CB-8860-8652F7DA56ED@eggert.org>
References: <3015EFF3-A0C6-4725-A13B-CAE4F1E5F9D1@kuehlewind.net> <F613BAC3-8744-49CB-8860-8652F7DA56ED@eggert.org>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Tue, 12 Nov 2019 14:19:15 +0100
Message-ID: <CAN1APde49R0Dgfdf1k7h=Gfcu=Ny-zgP9s+G9qhnUj+FET5UYw@mail.gmail.com>
Subject: Re: Fwd: TSVAREA agenda for IETF-106
To: Lars Eggert <lars@eggert.org>, QUIC IETF mailing list <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005922b6059726189e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/3kskh0XEsjpdqNdqieEhp4cqYhg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Nov 2019 13:19:22 -0000

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

After fast read through the document I am a bit concerned about the
proposed search algorithm: chose a set of sizes to progressively inspect
until MAX is accepted or a black hole is detected.

Another search pattern would be to use exponential search where gaps become
increasingly larger, but when a black hole is detected, smaller sizes are
tested by choosing a probe size between the smallest known black hole and
the larges known valid packet size, rather than stopping immediately after
first black hole.



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


On 12 November 2019 at 13.54.32, Lars Eggert (lars@eggert.org) wrote:

Note that there will be chunk of time dedicated in TSVAREA to discuss how
the IETF might want to split up future work on QUIC application bindings
and QUIC extensions and maintenance into existing and new WGs.

Lars

> Begin forwarded message:
>
> From: Mirja Kuehlewind <ietf@kuehlewind.net>
> Subject: TSVAREA agenda for IETF-106
> Date: November 12, 2019 at 14:46:43 GMT+2
> To: tsv-area@ietf.org
>
> Hi all,
>
> The agenda for our next tsvarea meeting is online (actually since
beginning of last week already):
>
> https://datatracker.ietf.org/meeting/106/materials/agenda-106-tsvarea
>
> We only have a short slot but will take some time to discuss new work
topics related to QUIC. The TSV ADs will meeting before the session with
the ART ADs and QUIC chairs and we should be able to report back for that.
>
> See you soon in Singapore or remotely!
>
> Mirja and Margnus (from remote)
>
>

--0000000000005922b6059726189e
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">After fast read thro=
ugh the document I am a bit concerned about the proposed search algorithm: =
chose a set of sizes to progressively inspect until MAX is accepted or a bl=
ack hole is detected.</div><div id=3D"bloop_customfont" style=3D"font-famil=
y:Helvetica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-heig=
ht:auto"><br></div><div id=3D"bloop_customfont" style=3D"font-family:Helvet=
ica,Arial;font-size:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto"=
>Another search pattern would be to use exponential search where gaps becom=
e increasingly larger, but when a black hole is detected, smaller sizes are=
 tested by choosing a probe size between the smallest known black hole and =
the larges known valid packet size, rather than stopping immediately after =
first black hole.</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"><br=
></div> <br> <div id=3D"bloop_sign_1573564572088410880" class=3D"bloop_sign=
"><div style=3D"font-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=B8rgensen<br><br></div></div> <br><p class=3D"airmail_on">On 1=
2 November 2019 at 13.54.32, Lars Eggert (<a href=3D"mailto:lars@eggert.org=
">lars@eggert.org</a>) wrote:</p> <blockquote type=3D"cite" class=3D"clean_=
bq"><span><div><div></div><div>Note that there will be chunk of time dedica=
ted in TSVAREA to discuss how the IETF might want to split up future work o=
n QUIC application bindings and QUIC extensions and maintenance into existi=
ng and new WGs.
<br>
<br>Lars
<br>
<br>&gt; Begin forwarded message:
<br>&gt; =20
<br>&gt; From: Mirja Kuehlewind &lt;<a href=3D"mailto:ietf@kuehlewind.net">=
ietf@kuehlewind.net</a>&gt;
<br>&gt; Subject: TSVAREA agenda for IETF-106
<br>&gt; Date: November 12, 2019 at 14:46:43 GMT+2
<br>&gt; To: <a href=3D"mailto:tsv-area@ietf.org">tsv-area@ietf.org</a>
<br>&gt; =20
<br>&gt; Hi all,
<br>&gt; =20
<br>&gt; The agenda for our next tsvarea meeting is online (actually since =
beginning of last week already):
<br>&gt; =20
<br>&gt; <a href=3D"https://datatracker.ietf.org/meeting/106/materials/agen=
da-106-tsvarea">https://datatracker.ietf.org/meeting/106/materials/agenda-1=
06-tsvarea</a>
<br>&gt; =20
<br>&gt; We only have a short slot but will take some time to discuss new w=
ork topics related to QUIC. The TSV ADs will meeting before the session wit=
h the ART ADs and QUIC chairs and we should be able to report back for that=
.
<br>&gt; =20
<br>&gt; See you soon in Singapore or remotely!
<br>&gt; =20
<br>&gt; Mirja and Margnus (from remote)
<br>&gt; =20
<br>&gt; =20
<br>
<br></div></div></span></blockquote></body></html>

--0000000000005922b6059726189e--


From nobody Tue Nov 12 08:00:35 2019
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 D443612006F for <quic@ietfa.amsl.com>; Tue, 12 Nov 2019 08:00:33 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.499
X-Spam-Level: 
X-Spam-Status: No, score=-17.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, 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_HELO_NONE=0.001, SPF_PASS=-0.001, 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 vh1PU4bCz_5U for <quic@ietfa.amsl.com>; Tue, 12 Nov 2019 08:00:31 -0800 (PST)
Received: from mail-wm1-x336.google.com (mail-wm1-x336.google.com [IPv6:2a00:1450:4864:20::336]) (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 4232612006E for <quic@ietf.org>; Tue, 12 Nov 2019 08:00:31 -0800 (PST)
Received: by mail-wm1-x336.google.com with SMTP id b11so3769194wmb.5 for <quic@ietf.org>; Tue, 12 Nov 2019 08:00:31 -0800 (PST)
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=U5YGRYHyM98g4Ndh37ecZCKz5ZTYCkw1eKH9yltnwe0=; b=I5BtZYivTYoBAqbwgbExQmNftIJs+tZUaZDlpPyfuddsOIph+rNG4o0cDnbPVOoFmq X6emHkcya+e6G7/BFyTSqzR/b333RB1paCe8Z5q3Eh1qnab5PCVOXF3Ym81Mx0nCfWRG geTnEk9amFdTtMktf92kLKG7fh96DPIvxT9XH3o9T6DMgwxmGouyAes9XsAggHgh3Oz2 UFgSp7Edk0Ek0ETs0o5Huj0hvWq39rkPIqt4/AEgNjlF3paCtFTu8b7fPoeZbZtoRF3b Ki/NWNLPG+LSSXQycNta8FJJ7OcRZLn4rwst9je7NzZon2smThXoMV308VgaFZyyBqaL o48g==
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=U5YGRYHyM98g4Ndh37ecZCKz5ZTYCkw1eKH9yltnwe0=; b=ZmOKut9QnRKkZtoP4P47I9uyvgzDvikR7OVJ1MV94gsQ8ap2yPDrMoJXZvd7tNitDv 17L9JVzh4PB6M1RRuAMFm0WpH28998PrhlR4opgowvMpu7aH5Ha78kPlhhZ9BwXoDU9I gwk1XikjP7F+ploYavsml708gYoI7KzsCFz0jBPKdsVrcBinzYVvu9hiuK0jBlHT+sJH ifQt+xQqzLLj8nn/SNY4EH15rHicZrNsJ0MlS+5lC/QuLJN4Qvol3Wof0MoUgxKXhgbw iqB0FkvtdGxTfodl9fD1DF8lwnyACS3+qA0blVmvhj7VXRqx6HdcMP3hk0wByha6xjaa /anA==
X-Gm-Message-State: APjAAAUudNjvFnaLVfI7IB1B5GFEwpMLFzPAMcWb9zr7FcD2Eawfepkd 3CwFXoQUNq+feqZ5agIFIhQKmkjKNtVDvh15koiMf8ScYBA=
X-Google-Smtp-Source: APXvYqxV7KxWSRt9Xz2+/GnQArPvcFhqo0jrL0zJrNVpnsb1358FXbSFCU+5G09QZs6vXAgv/vdjellQn4WkVKfj/dM=
X-Received: by 2002:a1c:7d47:: with SMTP id y68mr4537176wmc.157.1573574429465;  Tue, 12 Nov 2019 08:00:29 -0800 (PST)
MIME-Version: 1.0
References: <CAPDSy+6E79OySoOLbJ8eWp0J-+3yeB5iGvj6sW19bEDn_V7-NA@mail.gmail.com> <CABcZeBN+6p2k+Kj4K5oKNEqKV50aAU6FLGkiZG0dGPNkg1s_-A@mail.gmail.com> <376bcf21-b18f-9199-8054-47122419e1d4@huitema.net> <CAKcm_gM370SxB1UAt3HYfepzQTH4Z+_H8=zAVMdZu322VsONyQ@mail.gmail.com> <CB0D90CE-39AB-4FFA-BF9C-8967D5F73FF2@fb.com> <CAOYVs2p3iTdxqQ76WDxYMZbn_oL6Gvvvvsvzn0UJxyXvzY+Uqw@mail.gmail.com> <CABcZeBMVKtFAkkd14Xkwo=HRCmVs7OasVh5+SGYkXUoQ6bXgSg@mail.gmail.com> <c851dd42-d67b-4aae-bf16-96c0363a0c22@www.fastmail.com>
In-Reply-To: <c851dd42-d67b-4aae-bf16-96c0363a0c22@www.fastmail.com>
From: Ian Swett <ianswett@google.com>
Date: Tue, 12 Nov 2019 10:59:58 -0500
Message-ID: <CAKcm_gNO=YinyB8+Q12_ga3b=FY=RdBdrmYMuXgsMsuSRj+b0g@mail.gmail.com>
Subject: Re: Version Ossification: Intended Scope for QUICv1
To: Martin Thomson <mt@lowentropy.net>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e5df2805972858dd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ssB2QYHa9QmQkSg0tn0yjEmPinI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Nov 2019 16:00:34 -0000

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

Past experience indicates if we don't use joints, they will not work, both
internal(ie: SETTINGS) and external ones.
It also indicates that middleboxes will want to identify QUIC.  I'm happy
to sacrifice the invariants and QUIC bit for that purpose.

I have seen no evidence that if we continue using multiple versions in
production, future version numbers with the same invariants won't work.
Google is starting to deploy the 4th public header format in the last 2
years(current IETF invariants).  These public header changes require more
outreach, but even they are still possible.

On Tue, Nov 12, 2019 at 12:44 AM Martin Thomson <mt@lowentropy.net> wrote:

> On Tue, Nov 12, 2019, at 16:11, Eric Rescorla wrote:
> > ISTM that this is the scenario of interest for QUICv2 as well, namely
> > that the protocol will be public but vendors will have to adapt. If
> > they do that by reading specs and updating prompt, that seems not ideal
> > but acceptable.
>
> Yes, that would be tolerable.  The concern is that they stop at v1 and we
> can't properly rely on v2 working.
>
>

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

<div dir=3D"ltr">Past experience=C2=A0indicates if we don&#39;t use joints,=
 they will not work, both internal(ie: SETTINGS) and external ones.<div>It =
also indicates that middleboxes will want to identify QUIC.=C2=A0 I&#39;m h=
appy to sacrifice the invariants and QUIC bit for that purpose.</div><div><=
br></div><div>I have seen no evidence that if we continue using multiple ve=
rsions in production, future version numbers with the same invariants won&#=
39;t work.=C2=A0 Google is starting to deploy the 4th public header format =
in the last 2 years(current IETF invariants).=C2=A0 These public header cha=
nges require more outreach, but even they are still possible.</div></div><b=
r><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, =
Nov 12, 2019 at 12:44 AM Martin Thomson &lt;<a href=3D"mailto:mt@lowentropy=
.net">mt@lowentropy.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_=
quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,=
204);padding-left:1ex">On Tue, Nov 12, 2019, at 16:11, Eric Rescorla wrote:=
<br>
&gt; ISTM that this is the scenario of interest for QUICv2 as well, namely =
<br>
&gt; that the protocol will be public but vendors will have to adapt. If <b=
r>
&gt; they do that by reading specs and updating prompt, that seems not idea=
l <br>
&gt; but acceptable.<br>
<br>
Yes, that would be tolerable.=C2=A0 The concern is that they stop at v1 and=
 we can&#39;t properly rely on v2 working.<br>
<br>
</blockquote></div>

--000000000000e5df2805972858dd--


From nobody Tue Nov 12 09:10:16 2019
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 0F3C01200DB for <quic@ietfa.amsl.com>; Tue, 12 Nov 2019 09:10:15 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 HjAt_oVgqJs2 for <quic@ietfa.amsl.com>; Tue, 12 Nov 2019 09:10:10 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id 70CA3120836 for <quic@ietf.org>; Tue, 12 Nov 2019 09:10:10 -0800 (PST)
Received: from gorry-mac.erg.abdn.ac.uk (unknown [IPv6:2001:630:42:110:a065:fd0e:a1dc:e8bc]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 1ADC11B0017A; Tue, 12 Nov 2019 17:10:01 +0000 (GMT)
Subject: DPLPMTUD - searching algorithm
To: =?UTF-8?Q?Mikkel_Fahn=c3=b8e_J=c3=b8rgensen?= <mikkelfj@gmail.com>, Lars Eggert <lars@eggert.org>, QUIC IETF mailing list <quic@ietf.org>
References: <3015EFF3-A0C6-4725-A13B-CAE4F1E5F9D1@kuehlewind.net> <F613BAC3-8744-49CB-8860-8652F7DA56ED@eggert.org> <CAN1APde49R0Dgfdf1k7h=Gfcu=Ny-zgP9s+G9qhnUj+FET5UYw@mail.gmail.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <27d2c910-bb06-23b3-7bfa-aba4008792f7@erg.abdn.ac.uk>
Date: Tue, 12 Nov 2019 17:09:56 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.11; rv:60.0) Gecko/20100101 Thunderbird/60.8.0
MIME-Version: 1.0
In-Reply-To: <CAN1APde49R0Dgfdf1k7h=Gfcu=Ny-zgP9s+G9qhnUj+FET5UYw@mail.gmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/iHHVi1ORWBAiZd4QtKQGezIw-Bk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Nov 2019 17:10:15 -0000

Many thanks - because you spotted a couple of lingering mistakes.

On 12/11/2019 13:19, Mikkel FahnÃ¸e JÃ¸rgensen wrote:
> After fast read through the document I am a bit concerned about the 
> proposed search algorithm: chose a set of sizes to progressively 
> inspect until MAX is accepted or a black hole is detected.
>
This was meant to consistently say the search terminates after MAX 
probes fail in succession (of any size). It then terminates without 
increasing the PLPMTU. This bounds unproductive work. This was discussed 
in TSVWG for an earlier revision, and various parts updated and I'll 
make sure the remaining errant text reads this way before WGLC.

> Another search pattern would be to use exponential search where gaps 
> become increasingly larger, but when a black hole is detected, smaller 
> sizes are tested by choosing a probe size between the smallest known 
> black hole and the larges known valid packet size, rather than 
> stopping immediately after first black hole.
>
>
Sure - you can choose to do that.Â  You could decide to use any method 
you like to choose a probe size when searching. I suspect you will find 
more pleasure in using a simple list of preferred sizes (possibly with a 
second refinement stage), but there are plenty of ways you can propose 
new searches!

If you do have information from any real experiments using other search 
methods, it would be fun to know - please use the TSVWG list to discuss 
that.

Gorry

(I updated the subject line)

>
> Kind Regards,
> Mikkel FahnÃ¸e JÃ¸rgensen
>
>
> On 12 November 2019 at 13.54.32, Lars Eggert (lars@eggert.org 
> <mailto:lars@eggert.org>) wrote:
>
>> Note that there will be chunk of time dedicated in TSVAREA to discuss 
>> how the IETF might want to split up future work on QUIC application 
>> bindings and QUIC extensions and maintenance into existing and new WGs.
>>
>> Lars
>>
>> > Begin forwarded message:
>> >
>> > From: Mirja Kuehlewind <ietf@kuehlewind.net 
>> <mailto:ietf@kuehlewind.net>>
>> > Subject: TSVAREA agenda for IETF-106
>> > Date: November 12, 2019 at 14:46:43 GMT+2
>> > To: tsv-area@ietf.org <mailto:tsv-area@ietf.org>
>> >
>> > Hi all,
>> >
>> > The agenda for our next tsvarea meeting is online (actually since 
>> beginning of last week already):
>> >
>> > https://datatracker.ietf.org/meeting/106/materials/agenda-106-tsvarea
>> >
>> > We only have a short slot but will take some time to discuss new 
>> work topics related to QUIC. The TSV ADs will meeting before the 
>> session with the ART ADs and QUIC chairs and we should be able to 
>> report back for that..
>> >
>> > See you soon in Singapore or remotely!
>> >
>> > Mirja and Margnus (from remote)
>> >
>> >
>>


From nobody Tue Nov 12 09:18:04 2019
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 18345120842 for <quic@ietfa.amsl.com>; Tue, 12 Nov 2019 09:18:02 -0800 (PST)
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_HELO_NONE=0.001, 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 fI5rHtMitWyx for <quic@ietfa.amsl.com>; Tue, 12 Nov 2019 09:17:59 -0800 (PST)
Received: from mail-yw1-xc2f.google.com (mail-yw1-xc2f.google.com [IPv6:2607:f8b0:4864:20::c2f]) (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 8B528120837 for <quic@ietf.org>; Tue, 12 Nov 2019 09:17:59 -0800 (PST)
Received: by mail-yw1-xc2f.google.com with SMTP id y18so6704894ywk.1 for <quic@ietf.org>; Tue, 12 Nov 2019 09:17:59 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=from:to:subject:thread-topic:thread-index:date:message-id :references:in-reply-to:accept-language:content-language :mime-version; bh=0LT2PRrGDL6a2uQNnZl5wL4ayZt3mgAFA/7gmy+14w0=; b=eLsU6fe2+haAkbLK2a0z0n58YxHpsIXp498AiYw3Blls2Gr1gVaNWSJb/OVtTWtoOr qgeOpHGlly/Chn8u4wZKixcljEPnzR9Y70uAObuhnPa6fCMcYGHFlUMhE+rbEC9tn3Pl xM6twGh5L60Wmx07HCtPw7XWrThAGIWa0BLffqax0KVDD98snt6xH26t2Y2KRT0Ziu/W zuqSM7GhFvWi8HseAlU3WsBnkiqxT9/SxxiEArH95pW8OpPFPmYW8oc2p+0AqRLEqrSX Ghkpadi2QihjYKJoRFB4tWPlrUFY9gD30VG0XgRIcgJ//wcRz8nF0Pfw6sLnQiPOBmij xtMg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:subject:thread-topic:thread-index:date :message-id:references:in-reply-to:accept-language:content-language :mime-version; bh=0LT2PRrGDL6a2uQNnZl5wL4ayZt3mgAFA/7gmy+14w0=; b=UyMlWg41nkx3uT49/TVmwDBPN/2hbTaTZdQ7dNuZ7i31/f3WXmL6lZ3uWrnOpnCy2r iXxCfszMEcsNYiW/+2LhkkQlB0ZE4KSXUqe2zQzG6gKSe/PJA5PXGsAKLnqk+8bhDAp6 8O/qnz0Hp+2YIogWHBX2rpLW+PkxlsWOfQDMu6hWfhVeyTN50XskunOvRDLzO65yr3yP AetPomUx+gx8/zG+Gdjs8R/rmOd/Y44aaQk2d9Tt5emYtMKPt2d1hSf4C5Ar34TjL4A5 ODxyoHLguvbfbvylmLulUrQ+YvqEA5JarhFdnKB0A1jJi1OehkIcYpQocUHaVQFQHxdF tCZg==
X-Gm-Message-State: APjAAAU3dVclMmHR8tCD51JN6kIOLUECSm7W4abTVwf/5wL8OJv7d5OK EGoapvEccIBsq20q0Ew6ppQ=
X-Google-Smtp-Source: APXvYqxi+leb6jU191IWGjNlasREEZ2Y5qC1Kr6pBh90HCqFyOIT9d3mAfbTMEInfgexbbgzS66YgA==
X-Received: by 2002:a81:4104:: with SMTP id o4mr19771753ywa.353.1573579077549;  Tue, 12 Nov 2019 09:17:57 -0800 (PST)
Received: from DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM ([2603:1026:6:38::5]) by smtp.gmail.com with ESMTPSA id s18sm9096843ywk.33.2019.11.12.09.17.56 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 12 Nov 2019 09:17:56 -0800 (PST)
From: =?iso-8859-1?Q?Mikkel_Fahn=F8e_J=F8rgensen?= <mikkelfj@gmail.com>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Lars Eggert <lars@eggert.org>, QUIC IETF mailing list <quic@ietf.org>
Subject: Re: DPLPMTUD - searching algorithm
Thread-Topic: DPLPMTUD - searching algorithm
Thread-Index: AQHVmXwOHXYaYEw3U0SUmiW4o80686eHxpeH
X-MS-Exchange-MessageSentRepresentingType: 1
Date: Tue, 12 Nov 2019 17:17:54 +0000
Message-ID: <DB6PR10MB17666DB39ACF173E47E89790AC770@DB6PR10MB1766.EURPRD10.PROD.OUTLOOK.COM>
References: <3015EFF3-A0C6-4725-A13B-CAE4F1E5F9D1@kuehlewind.net> <F613BAC3-8744-49CB-8860-8652F7DA56ED@eggert.org> <CAN1APde49R0Dgfdf1k7h=Gfcu=Ny-zgP9s+G9qhnUj+FET5UYw@mail.gmail.com>, <27d2c910-bb06-23b3-7bfa-aba4008792f7@erg.abdn.ac.uk>
In-Reply-To: <27d2c910-bb06-23b3-7bfa-aba4008792f7@erg.abdn.ac.uk>
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_DB6PR10MB17666DB39ACF173E47E89790AC770DB6PR10MB1766EURP_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/zvO9pV__lKDI1X7Lc5NtVyXeCNo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 12 Nov 2019 17:18:02 -0000

--_000_DB6PR10MB17666DB39ACF173E47E89790AC770DB6PR10MB1766EURP_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I have not tried this search with PMTU, but I have used it elsewhere such a=
s finding the last valid record in a large file post crash.


________________________________
Fra: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Sendt: tirsdag, november 12, 2019 6:10 PM
Til: Mikkel Fahn=F8e J=F8rgensen; Lars Eggert; QUIC IETF mailing list
Emne: DPLPMTUD - searching algorithm

Many thanks - because you spotted a couple of lingering mistakes.

On 12/11/2019 13:19, Mikkel Fahn=F8e J=F8rgensen wrote:
> After fast read through the document I am a bit concerned about the
> proposed search algorithm: chose a set of sizes to progressively
> inspect until MAX is accepted or a black hole is detected.
>
This was meant to consistently say the search terminates after MAX
probes fail in succession (of any size). It then terminates without
increasing the PLPMTU. This bounds unproductive work. This was discussed
in TSVWG for an earlier revision, and various parts updated and I'll
make sure the remaining errant text reads this way before WGLC.

> Another search pattern would be to use exponential search where gaps
> become increasingly larger, but when a black hole is detected, smaller
> sizes are tested by choosing a probe size between the smallest known
> black hole and the larges known valid packet size, rather than
> stopping immediately after first black hole.
>
>
Sure - you can choose to do that.  You could decide to use any method
you like to choose a probe size when searching. I suspect you will find
more pleasure in using a simple list of preferred sizes (possibly with a
second refinement stage), but there are plenty of ways you can propose
new searches!

If you do have information from any real experiments using other search
methods, it would be fun to know - please use the TSVWG list to discuss
that.

Gorry

(I updated the subject line)

>
> Kind Regards,
> Mikkel Fahn=F8e J=F8rgensen
>
>
> On 12 November 2019 at 13.54.32, Lars Eggert (lars@eggert.org
> <mailto:lars@eggert.org>) wrote:
>
>> Note that there will be chunk of time dedicated in TSVAREA to discuss
>> how the IETF might want to split up future work on QUIC application
>> bindings and QUIC extensions and maintenance into existing and new WGs.
>>
>> Lars
>>
>> > Begin forwarded message:
>> >
>> > From: Mirja Kuehlewind <ietf@kuehlewind.net
>> <mailto:ietf@kuehlewind.net>>
>> > Subject: TSVAREA agenda for IETF-106
>> > Date: November 12, 2019 at 14:46:43 GMT+2
>> > To: tsv-area@ietf.org <mailto:tsv-area@ietf.org>
>> >
>> > Hi all,
>> >
>> > The agenda for our next tsvarea meeting is online (actually since
>> beginning of last week already):
>> >
>> > https://datatracker.ietf.org/meeting/106/materials/agenda-106-tsvarea
>> >
>> > We only have a short slot but will take some time to discuss new
>> work topics related to QUIC. The TSV ADs will meeting before the
>> session with the ART ADs and QUIC chairs and we should be able to
>> report back for that..
>> >
>> > See you soon in Singapore or remotely!
>> >
>> > Mirja and Margnus (from remote)
>> >
>> >
>>


--_000_DB6PR10MB17666DB39ACF173E47E89790AC770DB6PR10MB1766EURP_
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">
</head>
<body>
<div>
<div>
<div>
<div style=3D"direction: ltr;">I have not tried this search with PMTU, but =
I have used it elsewhere such as finding the last valid record in a large f=
ile post crash.
</div>
</div>
<div><br>
</div>
<div class=3D"ms-outlook-ios-signature"></div>
</div>
<div>&nbsp;</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"><b=
>Fra:</b> Gorry Fairhurst &lt;gorry@erg.abdn.ac.uk&gt;<br>
<b>Sendt:</b> tirsdag, november 12, 2019 6:10 PM<br>
<b>Til:</b> Mikkel Fahn=F8e J=F8rgensen; Lars Eggert; QUIC IETF mailing lis=
t<br>
<b>Emne:</b> DPLPMTUD - searching algorithm
<div>&nbsp;</div>
</font></div>
Many thanks - because you spotted a couple of lingering mistakes. <br>
<br>
On 12/11/2019 13:19, Mikkel Fahn=F8e J=F8rgensen wrote: <br>
&gt; After fast read through the document I am a bit concerned about the <b=
r>
&gt; proposed search algorithm: chose a set of sizes to progressively <br>
&gt; inspect until MAX is accepted or a black hole is detected. <br>
&gt; <br>
This was meant to consistently say the search terminates after MAX <br>
probes fail in succession (of any size). It then terminates without <br>
increasing the PLPMTU. This bounds unproductive work. This was discussed <b=
r>
in TSVWG for an earlier revision, and various parts updated and I'll <br>
make sure the remaining errant text reads this way before WGLC. <br>
<br>
&gt; Another search pattern would be to use exponential search where gaps <=
br>
&gt; become increasingly larger, but when a black hole is detected, smaller=
 <br>
&gt; sizes are tested by choosing a probe size between the smallest known <=
br>
&gt; black hole and the larges known valid packet size, rather than <br>
&gt; stopping immediately after first black hole. <br>
&gt; <br>
&gt; <br>
Sure - you can choose to do that.&nbsp; You could decide to use any method =
<br>
you like to choose a probe size when searching. I suspect you will find <br=
>
more pleasure in using a simple list of preferred sizes (possibly with a <b=
r>
second refinement stage), but there are plenty of ways you can propose <br>
new searches! <br>
<br>
If you do have information from any real experiments using other search <br=
>
methods, it would be fun to know - please use the TSVWG list to discuss <br=
>
that. <br>
<br>
Gorry <br>
<br>
(I updated the subject line) <br>
<br>
&gt; <br>
&gt; Kind Regards, <br>
&gt; Mikkel Fahn=F8e J=F8rgensen <br>
&gt; <br>
&gt; <br>
&gt; On 12 November 2019 at 13.54.32, Lars Eggert (lars@eggert.org <br>
&gt; &lt;mailto:lars@eggert.org&gt;) wrote: <br>
&gt; <br>
&gt;&gt; Note that there will be chunk of time dedicated in TSVAREA to disc=
uss <br>
&gt;&gt; how the IETF might want to split up future work on QUIC applicatio=
n <br>
&gt;&gt; bindings and QUIC extensions and maintenance into existing and new=
 WGs. <br>
&gt;&gt; <br>
&gt;&gt; Lars <br>
&gt;&gt; <br>
&gt;&gt; &gt; Begin forwarded message: <br>
&gt;&gt; &gt; <br>
&gt;&gt; &gt; From: Mirja Kuehlewind &lt;ietf@kuehlewind.net <br>
&gt;&gt; &lt;mailto:ietf@kuehlewind.net&gt;&gt; <br>
&gt;&gt; &gt; Subject: TSVAREA agenda for IETF-106 <br>
&gt;&gt; &gt; Date: November 12, 2019 at 14:46:43 GMT&#43;2 <br>
&gt;&gt; &gt; To: tsv-area@ietf.org &lt;mailto:tsv-area@ietf.org&gt; <br>
&gt;&gt; &gt; <br>
&gt;&gt; &gt; Hi all, <br>
&gt;&gt; &gt; <br>
&gt;&gt; &gt; The agenda for our next tsvarea meeting is online (actually s=
ince <br>
&gt;&gt; beginning of last week already): <br>
&gt;&gt; &gt; <br>
&gt;&gt; &gt; https://datatracker.ietf.org/meeting/106/materials/agenda-106=
-tsvarea <br>
&gt;&gt; &gt; <br>
&gt;&gt; &gt; We only have a short slot but will take some time to discuss =
new <br>
&gt;&gt; work topics related to QUIC. The TSV ADs will meeting before the <=
br>
&gt;&gt; session with the ART ADs and QUIC chairs and we should be able to =
<br>
&gt;&gt; report back for that.. <br>
&gt;&gt; &gt; <br>
&gt;&gt; &gt; See you soon in Singapore or remotely! <br>
&gt;&gt; &gt; <br>
&gt;&gt; &gt; Mirja and Margnus (from remote) <br>
&gt;&gt; &gt; <br>
&gt;&gt; &gt; <br>
&gt;&gt; <br>
<br>
</div>
</body>
</html>

--_000_DB6PR10MB17666DB39ACF173E47E89790AC770DB6PR10MB1766EURP_--


From nobody Tue Nov 12 16:42:31 2019
Return-Path: <martin.h.duke@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 922801200B5 for <quic@ietfa.amsl.com>; Tue, 12 Nov 2019 16:42:28 -0800 (PST)
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_HELO_NONE=0.001, 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 SnooTssaTMD4 for <quic@ietfa.amsl.com>; Tue, 12 Nov 2019 16:42:25 -0800 (PST)
Received: from mail-wm1-x329.google.com (mail-wm1-x329.google.com [IPv6:2a00:1450:4864:20::329]) (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 B63C3120091 for <quic@ietf.org>; Tue, 12 Nov 2019 16:42:24 -0800 (PST)
Received: by mail-wm1-x329.google.com with SMTP id b17so129658wmj.2 for <quic@ietf.org>; Tue, 12 Nov 2019 16:42:24 -0800 (PST)
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=t5bs9BOBb0qp3H07uPfggiidmhp7bS6Yf2BgVwGlfRk=; b=XuczZNc8kOzYq+5x9FtMhbvH+RwTAw0ZGpgLpE2CzJDJw/BBZ2VzJaoOU74IUoW5ff qx5/s0fzvJt7ozmQDW5mKVsmjr4iYmG7fWTQl8qxVGE9IUKY00gKzwrek0u8HKHmQSG5 69huCbiuHhZVjrH2VNLrVRxhGVQ+V+bM4bYKB2vXsQiH9ghf8iWo7c7mxF2ct0M4YiuK dt0tnUEZFa3aeGu3Hlvmm01CYf3cCjrnHn+wRyjn13NXiIBkcmVYPUEXgneMXrnTaawX jRvW6GhDZ5Wmz/6fQbJJa+A0uJReN343MecYn+kFszNBkLJd/c/vQrIURqXh8eNHNwkb 8K7A==
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=t5bs9BOBb0qp3H07uPfggiidmhp7bS6Yf2BgVwGlfRk=; b=UK19qYEbZbhcIFcndHTDPlZdjoQ5VoqInN9TKcupvZqsxXSVJ4VYud3VJhlDpXRGsK 1nBXJUeuOuBPWDI69oAAQSbh2T2p6p5EUEEAhi3Y7Qd5ixp0AsM+5HICn9d07Oc0HExQ 35g0dOoAZHxBIPGp/ieNr+wx53gSOPuk8qyIzKDqpkHlPMQaydF+5jA4YMOQLnv/0Fui TlYcdLjB+aPnUrJPO9wxxMvNZ8eG8+pXvtMDLmWf3JdbRl9nOIGARVKsTzsxHWqTxNi5 bjejIrO2ncXjzsfvmfL2bGPRUiQSSBRTJBiN25wLoewb/PCTEvy2V33i4VUllFRaAFmQ 0LOA==
X-Gm-Message-State: APjAAAUBcnbncVdkr1sKA7ZwNmDSMKhr1sMMyrX5UndWS5T/ve62HcBF xGDj7R20G+7FYUKml7w/y7iBMyEgyTewH1sI4IrZcw==
X-Google-Smtp-Source: APXvYqw9wei2FguG3zuFvEvSr13vMEyRDF3rAq9q6DUAaR6ljSkUSrzGjLQ9lIBt5HNwnWzdIKT6UXPZVD+3He/gpaI=
X-Received: by 2002:a05:600c:3cc:: with SMTP id z12mr217392wmd.151.1573605743127;  Tue, 12 Nov 2019 16:42:23 -0800 (PST)
MIME-Version: 1.0
References: <6A43BEC7-F9DE-40C9-BF70-BF1618EAFE01@mnot.net> <88BCFF39-6F9D-4E03-8787-561EECBBACE4@gbiv.com> <FD5201A5-C179-4302-B437-57561FB8DB24@mnot.net> <DM6PR22MB20101F0D1CC9867D5F3EE865DA740@DM6PR22MB2010.namprd22.prod.outlook.com>
In-Reply-To: <DM6PR22MB20101F0D1CC9867D5F3EE865DA740@DM6PR22MB2010.namprd22.prod.outlook.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Tue, 12 Nov 2019 16:42:12 -0800
Message-ID: <CAM4esxTYYJiPBgEdj278k2ZggZ_+D8CDd2rOjM14JRCLESowPg@mail.gmail.com>
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
To: Mike Bishop <mbishop@evequefou.be>
Cc: Mark Nottingham <mnot@mnot.net>, Roy Fielding <fielding@gbiv.com>, Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000055f2ca05972fa35c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/6qsEfXBdMeEUZN5TylaeFO4B7Hg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Nov 2019 00:42:29 -0000

--00000000000055f2ca05972fa35c
Content-Type: text/plain; charset="UTF-8"

IMO the recovery draft is in the midst of a major revision dealing with the
aftereffects of discarding the crypto timeout. Ian still has a bunch of
stuff in flight for this. When all of those PRs land I would like to have a
short period to review the working draft and see if it looks good.

On Mon, Nov 11, 2019 at 7:40 AM Mike Bishop <mbishop@evequefou.be> wrote:

> I'll also note that it's relatively easy from a spec perspective to allow
> trailers to arrive before the end of the body, or to allow multiple sets of
> trailers to arrive.  I suspect most clients won't process trailers until
> they have the body anyway, but the real question is what clients do with
> multiple trailer sets.  I'm not certain whether that's in our scope or not,
> but that's a separate conversation.  Feel free to open an issue for that
> specific discussion.
>
> -----Original Message-----
> From: QUIC <quic-bounces@ietf.org> On Behalf Of Mark Nottingham
> Sent: Sunday, November 10, 2019 8:01 PM
> To: Roy Fielding <fielding@gbiv.com>
> Cc: Lars Eggert <lars@eggert.org>; IETF QUIC WG <quic@ietf.org>
> Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the
> Late-Stage Process
>
> Hi Roy,
>
> Responding to the parts relevant to this CfC.
>
> > On 7 Nov 2019, at 5:39 am, Roy T. Fielding <fielding@gbiv.com> wrote:
> >
> >> On Nov 5, 2019, at 5:01 PM, Mark Nottingham <mnot@mnot.net> wrote:
> >>
> >> Previously, we've moved to the 'late-stage process' documented at [1]
> for the Transport and TLS drafts. The chairs and editors now feel that it's
> time to move the Recovery, HTTP/3, and QPACK drafts to that process as well.
> >>
> >> As before, this is because we're getting to a stage we feel the
> documents would benefit from slower and slightly more formal process, so
> that the rate of change is not so high, changes that do occur are
> well-vetted, and the documents get closer to reflecting consensus in the
> working group.
> >
> > I don't think that process has worked well for QUIC.
>
> Noted.
>
> > There are specific issues that are contentious enough to timebox and
> > conclude, in a formal (and faster) fashion than was done before.
> > That makes sense when needed for a specific issue. I don't know of any
> > such issues for those three drafts. IOW, I don't know of any issues
> > for which it makes sense for the Chairs to pre-empt the specification
> > authors in deciding what can or cannot result in changes to the drafts
> > just because of the timing of when the issue was raised.
>
> You misunderstand the process; the Chairs aren't pre-empting anything, the
> group is attempting to agree to a path to completing this work.
>
> > The late-stage process seems to focus all of our energy into
> > in/out-of-scope arguments rather than actual text in the specifications.
>
> I don't see any evidence for that claim; what makes you believe that?
>
> > The last interim spent easily twice as much time discussing process
> > and process planning than it did HTTP/3. Prior interims were worse.
>
> We spent a day talking about transport and TLS, part of a morning talking
> about planning the future of our work (if you want to call that "process
> and process planning") and the bulk of the (longer) afternoon session
> talking about H3. This isn't surprising, since our goal for the meeting was
> to get the Transport and TLS documents close to finished.
>
> > I don't even recall the last time contents of the HTTP/3 spec being
> > discussed on list, outside of very specific issues related to transport.
> > I would like to see HTTP/3 written with HTTP in mind, not as a set of
> > diffs against h2.
>
> That is by charter; we're largely limited to mapping H2 onto QUIC.
>
> > This is not a small undertaking, but it isn't a massive one either.
> > Basically, import the bits of h2 that are necessary to explain
> > HTTP/3's operation and intent, and then start referencing the
> > http-core drafts instead of 723x. Yes, I know that is risky, but it is
> the right thing to do.
> > And it needs to be done before http-core is finished, since that
> > effort exists largely to place the right content (in the right places)
> > for
> > HTTP/3 to reference.
>
> AIUI that is still our intent, and shouldn't be impeded by the late-stage
> process, since that work should be editorial.
>
> > I have no idea what the status is with QPACK, but we should learn a
> > lesson from the last time and make sure the fixed compression
> > dictionary (if any) is based on traffic at more than one proxy or
> > origin server. Or at least have each of the major deployments generate
> > their local "best" encoding and do some cross-testing of the N choices
> > (plus one or two based on a hand-crafted expert merge).
> >
> > I would like for HTTP/3 to have a mechanism for communicating metadata
> > (like trailers) in mid-stream, both for requests (e.g., priority) and
> > responses (e.g., chained sigs). That has been a design goal for HTTP
> > since 1995 or so. HTTP/1.1 had it, albeit limited to chunked extensions.
> > It has been proposed multiple times and keeps getting postponed
> > because of "concern about scope". This is not a semantics issue (they
> > are just optional trailers that arrive early) -- it is a multiplex
> > framing issue (a new frame type and expectation to process).
>
> Where are the multiple proposals you refer to? We've been working on h3
> now for more than three years. If you submit them now, they'll be design
> issues.
>
> I'd say that the Late-Stage process (or at least the proposal of adopting
> it) is working exactly as intended here -- making people realise that if
> they still have issues / changes that they want discussed, they need to
> bring them to our attention now, not as we go to WGLC.
>
> Cheers,
>
> --
> Mark Nottingham   https://www.mnot.net/
>
>

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

<div dir=3D"ltr">IMO the recovery draft is in the midst of a major revision=
 dealing with the aftereffects of discarding the crypto timeout. Ian still =
has a bunch of stuff in flight for this. When all of those PRs land I would=
 like to have a short period to review the working draft and see if it look=
s good.<br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"g=
mail_attr">On Mon, Nov 11, 2019 at 7:40 AM Mike Bishop &lt;<a href=3D"mailt=
o:mbishop@evequefou.be">mbishop@evequefou.be</a>&gt; wrote:<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex">I&#39;ll also note that it&#39;=
s relatively easy from a spec perspective to allow trailers to arrive befor=
e the end of the body, or to allow multiple sets of trailers to arrive.=C2=
=A0 I suspect most clients won&#39;t process trailers until they have the b=
ody anyway, but the real question is what clients do with multiple trailer =
sets.=C2=A0 I&#39;m not certain whether that&#39;s in our scope or not, but=
 that&#39;s a separate conversation.=C2=A0 Feel free to open an issue for t=
hat specific discussion.<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 Mark Nottingham<br>
Sent: Sunday, November 10, 2019 8:01 PM<br>
To: Roy Fielding &lt;<a href=3D"mailto:fielding@gbiv.com" target=3D"_blank"=
>fielding@gbiv.com</a>&gt;<br>
Cc: Lars Eggert &lt;<a href=3D"mailto:lars@eggert.org" target=3D"_blank">la=
rs@eggert.org</a>&gt;; IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" ta=
rget=3D"_blank">quic@ietf.org</a>&gt;<br>
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the L=
ate-Stage Process<br>
<br>
Hi Roy,<br>
<br>
Responding to the parts relevant to this CfC.<br>
<br>
&gt; On 7 Nov 2019, at 5:39 am, Roy T. Fielding &lt;<a href=3D"mailto:field=
ing@gbiv.com" target=3D"_blank">fielding@gbiv.com</a>&gt; wrote:<br>
&gt; <br>
&gt;&gt; On Nov 5, 2019, at 5:01 PM, Mark Nottingham &lt;<a href=3D"mailto:=
mnot@mnot.net" target=3D"_blank">mnot@mnot.net</a>&gt; wrote:<br>
&gt;&gt; <br>
&gt;&gt; Previously, we&#39;ve moved to the &#39;late-stage process&#39; do=
cumented at [1] for the Transport and TLS drafts. The chairs and editors no=
w feel that it&#39;s time to move the Recovery, HTTP/3, and QPACK drafts to=
 that process as well.<br>
&gt;&gt; <br>
&gt;&gt; As before, this is because we&#39;re getting to a stage we feel th=
e documents would benefit from slower and slightly more formal process, so =
that the rate of change is not so high, changes that do occur are well-vett=
ed, and the documents get closer to reflecting consensus in the working gro=
up.<br>
&gt; <br>
&gt; I don&#39;t think that process has worked well for QUIC.<br>
<br>
Noted.<br>
<br>
&gt; There are specific issues that are contentious enough to timebox and <=
br>
&gt; conclude, in a formal (and faster) fashion than was done before.<br>
&gt; That makes sense when needed for a specific issue. I don&#39;t know of=
 any <br>
&gt; such issues for those three drafts. IOW, I don&#39;t know of any issue=
s <br>
&gt; for which it makes sense for the Chairs to pre-empt the specification =
<br>
&gt; authors in deciding what can or cannot result in changes to the drafts=
 <br>
&gt; just because of the timing of when the issue was raised.<br>
<br>
You misunderstand the process; the Chairs aren&#39;t pre-empting anything, =
the group is attempting to agree to a path to completing this work.<br>
<br>
&gt; The late-stage process seems to focus all of our energy into <br>
&gt; in/out-of-scope arguments rather than actual text in the specification=
s.<br>
<br>
I don&#39;t see any evidence for that claim; what makes you believe that?<b=
r>
<br>
&gt; The last interim spent easily twice as much time discussing process <b=
r>
&gt; and process planning than it did HTTP/3. Prior interims were worse.<br=
>
<br>
We spent a day talking about transport and TLS, part of a morning talking a=
bout planning the future of our work (if you want to call that &quot;proces=
s and process planning&quot;) and the bulk of the (longer) afternoon sessio=
n talking about H3. This isn&#39;t surprising, since our goal for the meeti=
ng was to get the Transport and TLS documents close to finished.<br>
<br>
&gt; I don&#39;t even recall the last time contents of the HTTP/3 spec bein=
g <br>
&gt; discussed on list, outside of very specific issues related to transpor=
t.<br>
&gt; I would like to see HTTP/3 written with HTTP in mind, not as a set of =
<br>
&gt; diffs against h2.<br>
<br>
That is by charter; we&#39;re largely limited to mapping H2 onto QUIC. <br>
<br>
&gt; This is not a small undertaking, but it isn&#39;t a massive one either=
.<br>
&gt; Basically, import the bits of h2 that are necessary to explain <br>
&gt; HTTP/3&#39;s operation and intent, and then start referencing the <br>
&gt; http-core drafts instead of 723x. Yes, I know that is risky, but it is=
 the right thing to do.<br>
&gt; And it needs to be done before http-core is finished, since that <br>
&gt; effort exists largely to place the right content (in the right places)=
 <br>
&gt; for<br>
&gt; HTTP/3 to reference.<br>
<br>
AIUI that is still our intent, and shouldn&#39;t be impeded by the late-sta=
ge process, since that work should be editorial.<br>
<br>
&gt; I have no idea what the status is with QPACK, but we should learn a <b=
r>
&gt; lesson from the last time and make sure the fixed compression <br>
&gt; dictionary (if any) is based on traffic at more than one proxy or <br>
&gt; origin server. Or at least have each of the major deployments generate=
 <br>
&gt; their local &quot;best&quot; encoding and do some cross-testing of the=
 N choices <br>
&gt; (plus one or two based on a hand-crafted expert merge).<br>
&gt; <br>
&gt; I would like for HTTP/3 to have a mechanism for communicating metadata=
 <br>
&gt; (like trailers) in mid-stream, both for requests (e.g., priority) and =
<br>
&gt; responses (e.g., chained sigs). That has been a design goal for HTTP <=
br>
&gt; since 1995 or so. HTTP/1.1 had it, albeit limited to chunked extension=
s.<br>
&gt; It has been proposed multiple times and keeps getting postponed <br>
&gt; because of &quot;concern about scope&quot;. This is not a semantics is=
sue (they <br>
&gt; are just optional trailers that arrive early) -- it is a multiplex <br=
>
&gt; framing issue (a new frame type and expectation to process).<br>
<br>
Where are the multiple proposals you refer to? We&#39;ve been working on h3=
 now for more than three years. If you submit them now, they&#39;ll be desi=
gn issues.<br>
<br>
I&#39;d say that the Late-Stage process (or at least the proposal of adopti=
ng it) is working exactly as intended here -- making people realise that if=
 they still have issues / changes that they want discussed, they need to br=
ing them to our attention now, not as we go to WGLC.<br>
<br>
Cheers,<br>
<br>
--<br>
Mark Nottingham=C2=A0 =C2=A0<a href=3D"https://www.mnot.net/" rel=3D"norefe=
rrer" target=3D"_blank">https://www.mnot.net/</a><br>
<br>
</blockquote></div>

--00000000000055f2ca05972fa35c--


From nobody Tue Nov 12 16:43:09 2019
Return-Path: <martin.h.duke@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 92F651200B5 for <quic@ietfa.amsl.com>; Tue, 12 Nov 2019 16:43:08 -0800 (PST)
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_HELO_NONE=0.001, 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 Yz7BOrU2Dh4Y for <quic@ietfa.amsl.com>; Tue, 12 Nov 2019 16:43:03 -0800 (PST)
Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) (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 CDB851200E3 for <quic@ietf.org>; Tue, 12 Nov 2019 16:43:02 -0800 (PST)
Received: by mail-wr1-x433.google.com with SMTP id z10so282404wrs.12 for <quic@ietf.org>; Tue, 12 Nov 2019 16:43:02 -0800 (PST)
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=LHZ9u7b1jUeDpPvZ0NZ0zlAMcORZB8H+Q1OMiwWs9p4=; b=GWEm7UDTrR3lxIh9pd8Aalh8Bm2OzIZIjLvqAVBxrEQ/Tav2gNDWdkTJ5LCQQTd3Ip j3sRnXOBf+58emayhrDAvj51v04f0rc1vybJook0ZkfBQm3T2LSdFB31pUKScphXM0ai ETnZa800fERcSRBy1zHbFKhfr13EAzBcNX6b3Xl3bbDqHNBeT/ae2xJxOD6LYO8pduXM Pb+12F/IsuQoh15M+tohlyf4rfw7IIMDCWK/I2vrXC2HefCW9bYalTc6iawZ7BYvS+Sl 9C4Kq7yTwTQ53gbnnWn2zgN+78XmScnMRI951OzkuJev7TMGlAp0fgEkW+LVwnzmgIeh vl3g==
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=LHZ9u7b1jUeDpPvZ0NZ0zlAMcORZB8H+Q1OMiwWs9p4=; b=VoKt1Mi5bRTN8murhoZ8hr97FEXYBEnTBKqXvCW83x5a5k7qLuGKSINejuTyzDu+Vl /MfQSVYKP3QGs+tCwhlpx1WZGrcR6LmoMU4Zx+AvPRDBKV4xiYhRdTWO2wWGA+h25whk eGW0z1/ivlBHrJ9HuPj/n3uHNKmCsXNC1Km3OVqFZhdNyV7M7nHcOEEb30nzHjffPBHJ lvkUsyBE/fy3XEAfpiBXnTN/32Rix5EhWLU1QRIPz8r5BK5PWcXuzq5iQZvmslgkJ6j8 7agDaaiCUIKYGBPW1A7hGTzy7sKOTmr1FiqOPHrNUmw8Hyg4PbQKHNKS2oNAOdr16nBf 3EUA==
X-Gm-Message-State: APjAAAXZGAyQUECGfJ2D4W5WEULTrAvFQQA+9mElzaN4ndi1nEh5oo8c EW1wajGyAA3JEh1FJ969ywP0wBxIh4sHzvDcbjs=
X-Google-Smtp-Source: APXvYqxcr1r4eC7/GMEB6eqtUhpZBklxfQ0aZDOy7AabKSCvM7444nFDjcAxRHx8NCF8KW26jml09ABaK4okljLcBEQ=
X-Received: by 2002:a5d:55c7:: with SMTP id i7mr149084wrw.64.1573605781229; Tue, 12 Nov 2019 16:43:01 -0800 (PST)
MIME-Version: 1.0
References: <6A43BEC7-F9DE-40C9-BF70-BF1618EAFE01@mnot.net> <88BCFF39-6F9D-4E03-8787-561EECBBACE4@gbiv.com> <FD5201A5-C179-4302-B437-57561FB8DB24@mnot.net> <DM6PR22MB20101F0D1CC9867D5F3EE865DA740@DM6PR22MB2010.namprd22.prod.outlook.com> <CAM4esxTYYJiPBgEdj278k2ZggZ_+D8CDd2rOjM14JRCLESowPg@mail.gmail.com>
In-Reply-To: <CAM4esxTYYJiPBgEdj278k2ZggZ_+D8CDd2rOjM14JRCLESowPg@mail.gmail.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Tue, 12 Nov 2019 16:42:49 -0800
Message-ID: <CAM4esxRXnWj_D==G2qLc39W+73xt+gw64qPxSbW=2RGyD_=wNw@mail.gmail.com>
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
To: Mike Bishop <mbishop@evequefou.be>
Cc: Mark Nottingham <mnot@mnot.net>, Roy Fielding <fielding@gbiv.com>, Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009b559505972fa5e9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/71Kp3Q1H2Yuzf-M2KC8w58OXEVU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Nov 2019 00:43:09 -0000

--0000000000009b559505972fa5e9
Content-Type: text/plain; charset="UTF-8"

Put another way, I think Gorry's planned review of draft-24 is probably
premature.

On Tue, Nov 12, 2019 at 4:42 PM Martin Duke <martin.h.duke@gmail.com> wrote:

> IMO the recovery draft is in the midst of a major revision dealing with
> the aftereffects of discarding the crypto timeout. Ian still has a bunch of
> stuff in flight for this. When all of those PRs land I would like to have a
> short period to review the working draft and see if it looks good.
>
> On Mon, Nov 11, 2019 at 7:40 AM Mike Bishop <mbishop@evequefou.be> wrote:
>
>> I'll also note that it's relatively easy from a spec perspective to allow
>> trailers to arrive before the end of the body, or to allow multiple sets of
>> trailers to arrive.  I suspect most clients won't process trailers until
>> they have the body anyway, but the real question is what clients do with
>> multiple trailer sets.  I'm not certain whether that's in our scope or not,
>> but that's a separate conversation.  Feel free to open an issue for that
>> specific discussion.
>>
>> -----Original Message-----
>> From: QUIC <quic-bounces@ietf.org> On Behalf Of Mark Nottingham
>> Sent: Sunday, November 10, 2019 8:01 PM
>> To: Roy Fielding <fielding@gbiv.com>
>> Cc: Lars Eggert <lars@eggert.org>; IETF QUIC WG <quic@ietf.org>
>> Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the
>> Late-Stage Process
>>
>> Hi Roy,
>>
>> Responding to the parts relevant to this CfC.
>>
>> > On 7 Nov 2019, at 5:39 am, Roy T. Fielding <fielding@gbiv.com> wrote:
>> >
>> >> On Nov 5, 2019, at 5:01 PM, Mark Nottingham <mnot@mnot.net> wrote:
>> >>
>> >> Previously, we've moved to the 'late-stage process' documented at [1]
>> for the Transport and TLS drafts. The chairs and editors now feel that it's
>> time to move the Recovery, HTTP/3, and QPACK drafts to that process as well.
>> >>
>> >> As before, this is because we're getting to a stage we feel the
>> documents would benefit from slower and slightly more formal process, so
>> that the rate of change is not so high, changes that do occur are
>> well-vetted, and the documents get closer to reflecting consensus in the
>> working group.
>> >
>> > I don't think that process has worked well for QUIC.
>>
>> Noted.
>>
>> > There are specific issues that are contentious enough to timebox and
>> > conclude, in a formal (and faster) fashion than was done before.
>> > That makes sense when needed for a specific issue. I don't know of any
>> > such issues for those three drafts. IOW, I don't know of any issues
>> > for which it makes sense for the Chairs to pre-empt the specification
>> > authors in deciding what can or cannot result in changes to the drafts
>> > just because of the timing of when the issue was raised.
>>
>> You misunderstand the process; the Chairs aren't pre-empting anything,
>> the group is attempting to agree to a path to completing this work.
>>
>> > The late-stage process seems to focus all of our energy into
>> > in/out-of-scope arguments rather than actual text in the specifications.
>>
>> I don't see any evidence for that claim; what makes you believe that?
>>
>> > The last interim spent easily twice as much time discussing process
>> > and process planning than it did HTTP/3. Prior interims were worse.
>>
>> We spent a day talking about transport and TLS, part of a morning talking
>> about planning the future of our work (if you want to call that "process
>> and process planning") and the bulk of the (longer) afternoon session
>> talking about H3. This isn't surprising, since our goal for the meeting was
>> to get the Transport and TLS documents close to finished.
>>
>> > I don't even recall the last time contents of the HTTP/3 spec being
>> > discussed on list, outside of very specific issues related to transport.
>> > I would like to see HTTP/3 written with HTTP in mind, not as a set of
>> > diffs against h2.
>>
>> That is by charter; we're largely limited to mapping H2 onto QUIC.
>>
>> > This is not a small undertaking, but it isn't a massive one either.
>> > Basically, import the bits of h2 that are necessary to explain
>> > HTTP/3's operation and intent, and then start referencing the
>> > http-core drafts instead of 723x. Yes, I know that is risky, but it is
>> the right thing to do.
>> > And it needs to be done before http-core is finished, since that
>> > effort exists largely to place the right content (in the right places)
>> > for
>> > HTTP/3 to reference.
>>
>> AIUI that is still our intent, and shouldn't be impeded by the late-stage
>> process, since that work should be editorial.
>>
>> > I have no idea what the status is with QPACK, but we should learn a
>> > lesson from the last time and make sure the fixed compression
>> > dictionary (if any) is based on traffic at more than one proxy or
>> > origin server. Or at least have each of the major deployments generate
>> > their local "best" encoding and do some cross-testing of the N choices
>> > (plus one or two based on a hand-crafted expert merge).
>> >
>> > I would like for HTTP/3 to have a mechanism for communicating metadata
>> > (like trailers) in mid-stream, both for requests (e.g., priority) and
>> > responses (e.g., chained sigs). That has been a design goal for HTTP
>> > since 1995 or so. HTTP/1.1 had it, albeit limited to chunked extensions.
>> > It has been proposed multiple times and keeps getting postponed
>> > because of "concern about scope". This is not a semantics issue (they
>> > are just optional trailers that arrive early) -- it is a multiplex
>> > framing issue (a new frame type and expectation to process).
>>
>> Where are the multiple proposals you refer to? We've been working on h3
>> now for more than three years. If you submit them now, they'll be design
>> issues.
>>
>> I'd say that the Late-Stage process (or at least the proposal of adopting
>> it) is working exactly as intended here -- making people realise that if
>> they still have issues / changes that they want discussed, they need to
>> bring them to our attention now, not as we go to WGLC.
>>
>> Cheers,
>>
>> --
>> Mark Nottingham   https://www.mnot.net/
>>
>>

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

<div dir=3D"ltr">Put another way, I think Gorry&#39;s planned review of dra=
ft-24 is probably premature.<br></div><br><div class=3D"gmail_quote"><div d=
ir=3D"ltr" class=3D"gmail_attr">On Tue, Nov 12, 2019 at 4:42 PM Martin Duke=
 &lt;<a href=3D"mailto:martin.h.duke@gmail.com">martin.h.duke@gmail.com</a>=
&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div=
 dir=3D"ltr">IMO the recovery draft is in the midst of a major revision dea=
ling with the aftereffects of discarding the crypto timeout. Ian still has =
a bunch of stuff in flight for this. When all of those PRs land I would lik=
e to have a short period to review the working draft and see if it looks go=
od.<br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Mon, Nov 11, 2019 at 7:40 AM Mike Bishop &lt;<a href=3D"mailto:mb=
ishop@evequefou.be" target=3D"_blank">mbishop@evequefou.be</a>&gt; wrote:<b=
r></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex=
;border-left:1px solid rgb(204,204,204);padding-left:1ex">I&#39;ll also not=
e that it&#39;s relatively easy from a spec perspective to allow trailers t=
o arrive before the end of the body, or to allow multiple sets of trailers =
to arrive.=C2=A0 I suspect most clients won&#39;t process trailers until th=
ey have the body anyway, but the real question is what clients do with mult=
iple trailer sets.=C2=A0 I&#39;m not certain whether that&#39;s in our scop=
e or not, but that&#39;s a separate conversation.=C2=A0 Feel free to open a=
n issue for that specific discussion.<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 Mark Nottingham<br>
Sent: Sunday, November 10, 2019 8:01 PM<br>
To: Roy Fielding &lt;<a href=3D"mailto:fielding@gbiv.com" target=3D"_blank"=
>fielding@gbiv.com</a>&gt;<br>
Cc: Lars Eggert &lt;<a href=3D"mailto:lars@eggert.org" target=3D"_blank">la=
rs@eggert.org</a>&gt;; IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" ta=
rget=3D"_blank">quic@ietf.org</a>&gt;<br>
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the L=
ate-Stage Process<br>
<br>
Hi Roy,<br>
<br>
Responding to the parts relevant to this CfC.<br>
<br>
&gt; On 7 Nov 2019, at 5:39 am, Roy T. Fielding &lt;<a href=3D"mailto:field=
ing@gbiv.com" target=3D"_blank">fielding@gbiv.com</a>&gt; wrote:<br>
&gt; <br>
&gt;&gt; On Nov 5, 2019, at 5:01 PM, Mark Nottingham &lt;<a href=3D"mailto:=
mnot@mnot.net" target=3D"_blank">mnot@mnot.net</a>&gt; wrote:<br>
&gt;&gt; <br>
&gt;&gt; Previously, we&#39;ve moved to the &#39;late-stage process&#39; do=
cumented at [1] for the Transport and TLS drafts. The chairs and editors no=
w feel that it&#39;s time to move the Recovery, HTTP/3, and QPACK drafts to=
 that process as well.<br>
&gt;&gt; <br>
&gt;&gt; As before, this is because we&#39;re getting to a stage we feel th=
e documents would benefit from slower and slightly more formal process, so =
that the rate of change is not so high, changes that do occur are well-vett=
ed, and the documents get closer to reflecting consensus in the working gro=
up.<br>
&gt; <br>
&gt; I don&#39;t think that process has worked well for QUIC.<br>
<br>
Noted.<br>
<br>
&gt; There are specific issues that are contentious enough to timebox and <=
br>
&gt; conclude, in a formal (and faster) fashion than was done before.<br>
&gt; That makes sense when needed for a specific issue. I don&#39;t know of=
 any <br>
&gt; such issues for those three drafts. IOW, I don&#39;t know of any issue=
s <br>
&gt; for which it makes sense for the Chairs to pre-empt the specification =
<br>
&gt; authors in deciding what can or cannot result in changes to the drafts=
 <br>
&gt; just because of the timing of when the issue was raised.<br>
<br>
You misunderstand the process; the Chairs aren&#39;t pre-empting anything, =
the group is attempting to agree to a path to completing this work.<br>
<br>
&gt; The late-stage process seems to focus all of our energy into <br>
&gt; in/out-of-scope arguments rather than actual text in the specification=
s.<br>
<br>
I don&#39;t see any evidence for that claim; what makes you believe that?<b=
r>
<br>
&gt; The last interim spent easily twice as much time discussing process <b=
r>
&gt; and process planning than it did HTTP/3. Prior interims were worse.<br=
>
<br>
We spent a day talking about transport and TLS, part of a morning talking a=
bout planning the future of our work (if you want to call that &quot;proces=
s and process planning&quot;) and the bulk of the (longer) afternoon sessio=
n talking about H3. This isn&#39;t surprising, since our goal for the meeti=
ng was to get the Transport and TLS documents close to finished.<br>
<br>
&gt; I don&#39;t even recall the last time contents of the HTTP/3 spec bein=
g <br>
&gt; discussed on list, outside of very specific issues related to transpor=
t.<br>
&gt; I would like to see HTTP/3 written with HTTP in mind, not as a set of =
<br>
&gt; diffs against h2.<br>
<br>
That is by charter; we&#39;re largely limited to mapping H2 onto QUIC. <br>
<br>
&gt; This is not a small undertaking, but it isn&#39;t a massive one either=
.<br>
&gt; Basically, import the bits of h2 that are necessary to explain <br>
&gt; HTTP/3&#39;s operation and intent, and then start referencing the <br>
&gt; http-core drafts instead of 723x. Yes, I know that is risky, but it is=
 the right thing to do.<br>
&gt; And it needs to be done before http-core is finished, since that <br>
&gt; effort exists largely to place the right content (in the right places)=
 <br>
&gt; for<br>
&gt; HTTP/3 to reference.<br>
<br>
AIUI that is still our intent, and shouldn&#39;t be impeded by the late-sta=
ge process, since that work should be editorial.<br>
<br>
&gt; I have no idea what the status is with QPACK, but we should learn a <b=
r>
&gt; lesson from the last time and make sure the fixed compression <br>
&gt; dictionary (if any) is based on traffic at more than one proxy or <br>
&gt; origin server. Or at least have each of the major deployments generate=
 <br>
&gt; their local &quot;best&quot; encoding and do some cross-testing of the=
 N choices <br>
&gt; (plus one or two based on a hand-crafted expert merge).<br>
&gt; <br>
&gt; I would like for HTTP/3 to have a mechanism for communicating metadata=
 <br>
&gt; (like trailers) in mid-stream, both for requests (e.g., priority) and =
<br>
&gt; responses (e.g., chained sigs). That has been a design goal for HTTP <=
br>
&gt; since 1995 or so. HTTP/1.1 had it, albeit limited to chunked extension=
s.<br>
&gt; It has been proposed multiple times and keeps getting postponed <br>
&gt; because of &quot;concern about scope&quot;. This is not a semantics is=
sue (they <br>
&gt; are just optional trailers that arrive early) -- it is a multiplex <br=
>
&gt; framing issue (a new frame type and expectation to process).<br>
<br>
Where are the multiple proposals you refer to? We&#39;ve been working on h3=
 now for more than three years. If you submit them now, they&#39;ll be desi=
gn issues.<br>
<br>
I&#39;d say that the Late-Stage process (or at least the proposal of adopti=
ng it) is working exactly as intended here -- making people realise that if=
 they still have issues / changes that they want discussed, they need to br=
ing them to our attention now, not as we go to WGLC.<br>
<br>
Cheers,<br>
<br>
--<br>
Mark Nottingham=C2=A0 =C2=A0<a href=3D"https://www.mnot.net/" rel=3D"norefe=
rrer" target=3D"_blank">https://www.mnot.net/</a><br>
<br>
</blockquote></div>
</blockquote></div>

--0000000000009b559505972fa5e9--


From bilal.cybrog@gmail.com  Tue Nov 12 22:59:29 2019
Return-Path: <bilal.cybrog@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 48461120851 for <quic@ietfa.amsl.com>; Tue, 12 Nov 2019 22:59:29 -0800 (PST)
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_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 bZskv7Q2amMh for <quic@ietfa.amsl.com>; Tue, 12 Nov 2019 22:59:27 -0800 (PST)
Received: from mail-il1-x132.google.com (mail-il1-x132.google.com [IPv6:2607:f8b0:4864:20::132]) (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 C29551200CD for <quic@ietfa.amsl.com>; Tue, 12 Nov 2019 22:59:27 -0800 (PST)
Received: by mail-il1-x132.google.com with SMTP id o18so776613ils.12 for <quic@ietfa.amsl.com>; Tue, 12 Nov 2019 22:59:27 -0800 (PST)
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;  bh=vTaJNE/MIki1U4jYuNObbwYPyZtzavbQ92wTBW+lMmQ=; b=KySlFsuzzzgY2PkeI7O7iTeDsnHW+aEIr/+wNlhBk9aVxe9gU83TKL17/zyB72BCGY cYMtXhjqA2tUWyRP/mXdjoPNUb+DzlUfcvZGHizaSxXXUFJvMI1B5JT9+djZxsD90sqj QVRfVp1Zjua2Abvx10Bkbo7cfb02nNgT5Y1vkvJGaaRT3SLAe+E0V+81MfS/Rj2r4lrc S91/0N3LEmuX1rDdeL592hfr9rWFMfz8EizuLVrQkRW4wPqxeE9cy8YKizzB+u1sRXWW wmqhxdFnTxWLGguEa9L5LyiMdzUx7srchNg3nQIablqJ8MlH+17aWBVMSlE72v4jwkcz lqCw==
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; bh=vTaJNE/MIki1U4jYuNObbwYPyZtzavbQ92wTBW+lMmQ=; b=l3h8dCDPc97pHLGrbg+feaWM+5xdZce8l9/uOzsHNrdkKKHLeW5QTe6BExSb7ZzJw1 Y67YMVAoOJOL9vCEULT6K8TKjvl+6xwkU+6aOxwSNSJ6V2mOyNaojBdDyJHKRFy6J2PY XSrasbEJsWTcDzokRAispeySEH4d28gI/HgMqAl0MGQHxz63b2iv3TJEnNx0FnikIy40 ivJePP1CisEM/slPMjj3D/ZYAPzc8fIGWFom5+FUdH9F/x/lzv8mn4wNc+GRQXiyLm0c JjziUBuTtSG6It/pcnEv7WdGkRnkzbAnsKa1259+4r+hghBIWibNi35li2Bb5fXjXi26 /yDg==
X-Gm-Message-State: APjAAAUqMEf9n7FnQCvD19mOimTBHyEP+P1WbaF/VCcLOANWhrHus5Df QR98SHRkYcnuOnp53LPrA1E/kzQSu2rf3R0BT+DVLvNASuA=
X-Google-Smtp-Source: APXvYqy21p7LEsYpQjzaYBdMV/uOelDNT9zwIhfIxiJDRIn9+LNL9maWUUvSI4JXk1UCy1C+k3B13x1Cnes30USiw9Q=
X-Received: by 2002:a92:ce03:: with SMTP id b3mr2003528ilo.179.1573628366578;  Tue, 12 Nov 2019 22:59:26 -0800 (PST)
MIME-Version: 1.0
References: <CAP6FE_Lm6rtY9Fwr0UkrrxCn_hHFra03GrUGeo7LcETYZSwHcA@mail.gmail.com>
In-Reply-To: <CAP6FE_Lm6rtY9Fwr0UkrrxCn_hHFra03GrUGeo7LcETYZSwHcA@mail.gmail.com>
From: Bilal Ahmad <bilal.cybrog@gmail.com>
Date: Wed, 13 Nov 2019 11:59:14 +0500
Message-ID: <CAP6FE_LZ-LXDzaF+=45T6hvZQ8P52wnXpJ9Hb71tmAO9N7+omg@mail.gmail.com>
Subject: QUIC help
To: quic@ietfa.amsl.com
Content-Type: multipart/alternative; boundary="000000000000cc6b47059734e7cb"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/JMZEtS2C_BngCNDB-I0fzVuxMEw>
X-Mailman-Approved-At: Wed, 13 Nov 2019 00:24:46 -0800
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Nov 2019 08:09:11 -0000

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

Hi,
I am a research student I want to do research in QUIC protocol.
please guide me how to implement it on a pc.

also can you please help in establishing a direction as to what aspect
of quic should i be focusing on?

your help will be much appreciated for me.

Regards
Bilal Ahmad.

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

<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr">Hi,<div>I am a=
 research student I want to do research in QUIC protocol.</div><div>please =
guide me how to implement it on a pc.</div><div><br></div><div>also can you=
 please help in establishing a direction as to what aspect</div><div>of qui=
c should i be focusing on?</div><div><br></div><div>your help will be=C2=A0=
much appreciated for me.</div><div><br></div><div>Regards=C2=A0</div><div>B=
ilal Ahmad.</div></div>
</div></div>

--000000000000cc6b47059734e7cb--


From nobody Wed Nov 13 01:34:14 2019
Return-Path: <bortzmeyer@nic.fr>
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 1EE2E120169 for <quic@ietfa.amsl.com>; Wed, 13 Nov 2019 01:34:13 -0800 (PST)
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, RCVD_IN_DNSWL_HI=-5, SPF_HELO_NONE=0.001, 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 9DY1AIVTH-oO for <quic@ietfa.amsl.com>; Wed, 13 Nov 2019 01:34:11 -0800 (PST)
Received: from mx4.nic.fr (mx4.nic.fr [IPv6:2001:67c:2218:2::4:12]) (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 171091200EF for <quic@ietfa.amsl.com>; Wed, 13 Nov 2019 01:34:11 -0800 (PST)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id ED83F280161; Wed, 13 Nov 2019 10:34:07 +0100 (CET)
Received: by mx4.nic.fr (Postfix, from userid 500) id E76A5280716; Wed, 13 Nov 2019 10:34:07 +0100 (CET)
Received: from relay01.prive.nic.fr (unknown [10.1.50.11]) by mx4.nic.fr (Postfix) with ESMTP id DF9FF280161; Wed, 13 Nov 2019 10:34:07 +0100 (CET)
Received: from b12.nic.fr (b12.tech.ipv6.nic.fr [IPv6:2001:67c:1348:7::86:133]) by relay01.prive.nic.fr (Postfix) with ESMTP id DC504642BE40; Wed, 13 Nov 2019 10:34:07 +0100 (CET)
Received: by b12.nic.fr (Postfix, from userid 1000) id C829F3FFE3; Wed, 13 Nov 2019 10:34:07 +0100 (CET)
Date: Wed, 13 Nov 2019 10:34:07 +0100
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Bilal Ahmad <bilal.cybrog@gmail.com>
Cc: quic@ietfa.amsl.com
Subject: Re: QUIC help
Message-ID: <20191113093407.GA4508@nic.fr>
References: <CAP6FE_Lm6rtY9Fwr0UkrrxCn_hHFra03GrUGeo7LcETYZSwHcA@mail.gmail.com> <CAP6FE_LZ-LXDzaF+=45T6hvZQ8P52wnXpJ9Hb71tmAO9N7+omg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAP6FE_LZ-LXDzaF+=45T6hvZQ8P52wnXpJ9Hb71tmAO9N7+omg@mail.gmail.com>
X-Operating-System: Debian GNU/Linux 10.1
X-Kernel: Linux 4.19.0-6-amd64 x86_64
X-Charlie: Je suis Charlie
Organization: NIC France
X-URL: http://www.nic.fr/
User-Agent: Mutt/1.10.1 (2018-07-13)
X-Bogosity: No, tests=bogofilter, spamicity=0.000105, version=1.2.2
X-PMX-Version: 6.0.0.2142326, Antispam-Engine: 2.7.2.2107409, Antispam-Data: 2019.11.5.63017
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/-Xap6xEu5_ZCL9VSxd8rWZRbQZo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Nov 2019 09:34:13 -0000

On Wed, Nov 13, 2019 at 11:59:14AM +0500,
 Bilal Ahmad <bilal.cybrog@gmail.com> wrote 
 a message of 29 lines which said:

> I am a research student I want to do research in QUIC protocol.
> please guide me how to implement it on a pc.

Well, QUIC is a complicated protcol, with a lot of things to take care
of, so implementing QUIC from scratch seems a daunting task.

It may be easier to start from existing implementations. See
<https://github.com/ngtcp2/ngtcp2> and
<https://github.com/ngtcp2/nghttp3> and <https://github.com/cloudflare/quiche>.

> also can you please help in establishing a direction as to what aspect
> of quic should i be focusing on?

There are many. It depends on your abilities / tastes. Cryptography?
Congestion? HTTP?

Which documents did you read? The Internet-Drafts are of course
necessary but they may be hard for a complete beginner. I recommend
<https://daniel.haxx.se/blog/2018/11/26/http3-explained/> for a start.



From nobody Wed Nov 13 06:39:44 2019
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 232E712080A for <quic@ietfa.amsl.com>; Wed, 13 Nov 2019 06:39:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.499
X-Spam-Level: 
X-Spam-Status: No, score=-17.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, 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_HELO_NONE=0.001, SPF_PASS=-0.001, 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 2LPUoNzrs6XJ for <quic@ietfa.amsl.com>; Wed, 13 Nov 2019 06:39:40 -0800 (PST)
Received: from mail-ua1-x932.google.com (mail-ua1-x932.google.com [IPv6:2607:f8b0:4864:20::932]) (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 4DBC9120808 for <quic@ietf.org>; Wed, 13 Nov 2019 06:39:40 -0800 (PST)
Received: by mail-ua1-x932.google.com with SMTP id l38so720228uad.4 for <quic@ietf.org>; Wed, 13 Nov 2019 06:39:40 -0800 (PST)
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=6AQV+le2Sc6xFGowDoKA/P0kcc2xNSaUGj3Vs8i4l1A=; b=i8KXpP6TG70FZFuCtaG/+n6Gv4JqtQ4hqXFbh8lI0c8FF1oH+YStJWlZjfbYVMd5HW ecaSxkp/H+bXl1lRpJZ5pPHsz2agU2Vq2gnnnngLvKF0FuQ+Ys0Jp+rWmgbPGUl40nwL aID6uIWR7r+pOGr6f+O+5hjDL5wUXdVes7H8oUQjPpyCVbJNbPv3WOZzkpp4ANCpQHa/ WKWnTuxARvmc3gp/g/GnfskdqSoc/4tQfg+2vcwPfZ8rLrOB5a6UZj2flZ/P4P2n62Bw As81D3pmSqMb2nWC1frx8TzjLJTpIXdt2jfdNMUrAE+VbCfZtZmihJYhwd2wa0cCBzbl GA5w==
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=6AQV+le2Sc6xFGowDoKA/P0kcc2xNSaUGj3Vs8i4l1A=; b=U5/zNihRxOaGLjXTY+Fv2D+9qx5R6/4WQQS9EoJ30XszVuthiiudp6nar1wyTkud8j jm+k9R08W6dZQXpn9itKLRnWHIuc1GY1cvI9nUn1DNpZjBbxqWdU7+sewgpgUKo8PPgZ ISCv4QuoUW2beW4t6YO0c7skMIFH8e1okV3B0QUhKHWQ8sk8VFKe6Ox9FTqIWm6wLqwg IwzcGcdbymaBx/ypNrJtjAY66vIFJfiujbgp0ja6Ny0vmsXew7jTHM/RbJFn95Zp+Cv7 hq4HeqN5sJIEo93esJsCqZixRwtJH+4Yx9RasDTepWLFY5yaYHEamzZ+fK6ohETwt9xA 0WSg==
X-Gm-Message-State: APjAAAX/b6DNPaEzFV0XADxP8NsIhGX8Qb0Mc8dQq12FwVD9FLe4KrxK YDaPR67XjtgLxvFUXDDLz9irCKQkFo4ZltNs0eEUJQ==
X-Google-Smtp-Source: APXvYqykKZ6+A/FCeTg9G30/4A09ATXCS941MalZ1m/J7O0HbsG0BYpCy8WdFrMc4AeiIr7K9HulTP/hV3Q+FecYC/k=
X-Received: by 2002:ab0:5a8f:: with SMTP id w15mr2003731uae.91.1573655978729;  Wed, 13 Nov 2019 06:39:38 -0800 (PST)
MIME-Version: 1.0
References: <6A43BEC7-F9DE-40C9-BF70-BF1618EAFE01@mnot.net> <88BCFF39-6F9D-4E03-8787-561EECBBACE4@gbiv.com> <FD5201A5-C179-4302-B437-57561FB8DB24@mnot.net> <DM6PR22MB20101F0D1CC9867D5F3EE865DA740@DM6PR22MB2010.namprd22.prod.outlook.com> <CAM4esxTYYJiPBgEdj278k2ZggZ_+D8CDd2rOjM14JRCLESowPg@mail.gmail.com> <CAM4esxRXnWj_D==G2qLc39W+73xt+gw64qPxSbW=2RGyD_=wNw@mail.gmail.com>
In-Reply-To: <CAM4esxRXnWj_D==G2qLc39W+73xt+gw64qPxSbW=2RGyD_=wNw@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Wed, 13 Nov 2019 09:39:26 -0500
Message-ID: <CAKcm_gPJw3rNgTRCATN9==Nno4Q--X433r4LCjiGytr_VJ3pGg@mail.gmail.com>
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
To: Martin Duke <martin.h.duke@gmail.com>
Cc: Mike Bishop <mbishop@evequefou.be>, Lars Eggert <lars@eggert.org>,  Mark Nottingham <mnot@mnot.net>, IETF QUIC WG <quic@ietf.org>, Roy Fielding <fielding@gbiv.com>
Content-Type: multipart/alternative; boundary="0000000000009cf09305973b5548"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/VFUmnY1UZDQC6YtbEHx1dzGQPmI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Nov 2019 14:39:43 -0000

--0000000000009cf09305973b5548
Content-Type: text/plain; charset="UTF-8"

I'm not aware of anything important in-flight( :) ) for recovery.  #3066
<https://github.com/quicwg/base-drafts/pull/3066> has been in the editor's
copy for over a week now, and did not quite make -24, so I would recommend
reading the editors copy.  There is one handshake optimization PR(#3080
<https://github.com/quicwg/base-drafts/pull/3080>) and an alternate
solution to the amplification deadlock(#3162
<https://github.com/quicwg/base-drafts/pull/3162>), but neither is critical
in my opinion.

There is a possibility of the discard keys conversation changing recovery,
though at least one solution(HANDSHAKE_DONE
<https://github.com/quicwg/base-drafts/pull/3145>) does not require any
changes.  If changes are required, I expect them to be ~2-3 sentences.

On Tue, Nov 12, 2019 at 7:43 PM Martin Duke <martin.h.duke@gmail.com> wrote:

> Put another way, I think Gorry's planned review of draft-24 is probably
> premature.
>
> On Tue, Nov 12, 2019 at 4:42 PM Martin Duke <martin.h.duke@gmail.com>
> wrote:
>
>> IMO the recovery draft is in the midst of a major revision dealing with
>> the aftereffects of discarding the crypto timeout. Ian still has a bunch of
>> stuff in flight for this. When all of those PRs land I would like to have a
>> short period to review the working draft and see if it looks good.
>>
>> On Mon, Nov 11, 2019 at 7:40 AM Mike Bishop <mbishop@evequefou.be> wrote:
>>
>>> I'll also note that it's relatively easy from a spec perspective to
>>> allow trailers to arrive before the end of the body, or to allow multiple
>>> sets of trailers to arrive.  I suspect most clients won't process trailers
>>> until they have the body anyway, but the real question is what clients do
>>> with multiple trailer sets.  I'm not certain whether that's in our scope or
>>> not, but that's a separate conversation.  Feel free to open an issue for
>>> that specific discussion.
>>>
>>> -----Original Message-----
>>> From: QUIC <quic-bounces@ietf.org> On Behalf Of Mark Nottingham
>>> Sent: Sunday, November 10, 2019 8:01 PM
>>> To: Roy Fielding <fielding@gbiv.com>
>>> Cc: Lars Eggert <lars@eggert.org>; IETF QUIC WG <quic@ietf.org>
>>> Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to
>>> the Late-Stage Process
>>>
>>> Hi Roy,
>>>
>>> Responding to the parts relevant to this CfC.
>>>
>>> > On 7 Nov 2019, at 5:39 am, Roy T. Fielding <fielding@gbiv.com> wrote:
>>> >
>>> >> On Nov 5, 2019, at 5:01 PM, Mark Nottingham <mnot@mnot.net> wrote:
>>> >>
>>> >> Previously, we've moved to the 'late-stage process' documented at [1]
>>> for the Transport and TLS drafts. The chairs and editors now feel that it's
>>> time to move the Recovery, HTTP/3, and QPACK drafts to that process as well.
>>> >>
>>> >> As before, this is because we're getting to a stage we feel the
>>> documents would benefit from slower and slightly more formal process, so
>>> that the rate of change is not so high, changes that do occur are
>>> well-vetted, and the documents get closer to reflecting consensus in the
>>> working group.
>>> >
>>> > I don't think that process has worked well for QUIC.
>>>
>>> Noted.
>>>
>>> > There are specific issues that are contentious enough to timebox and
>>> > conclude, in a formal (and faster) fashion than was done before.
>>> > That makes sense when needed for a specific issue. I don't know of any
>>> > such issues for those three drafts. IOW, I don't know of any issues
>>> > for which it makes sense for the Chairs to pre-empt the specification
>>> > authors in deciding what can or cannot result in changes to the drafts
>>> > just because of the timing of when the issue was raised.
>>>
>>> You misunderstand the process; the Chairs aren't pre-empting anything,
>>> the group is attempting to agree to a path to completing this work.
>>>
>>> > The late-stage process seems to focus all of our energy into
>>> > in/out-of-scope arguments rather than actual text in the
>>> specifications.
>>>
>>> I don't see any evidence for that claim; what makes you believe that?
>>>
>>> > The last interim spent easily twice as much time discussing process
>>> > and process planning than it did HTTP/3. Prior interims were worse.
>>>
>>> We spent a day talking about transport and TLS, part of a morning
>>> talking about planning the future of our work (if you want to call that
>>> "process and process planning") and the bulk of the (longer) afternoon
>>> session talking about H3. This isn't surprising, since our goal for the
>>> meeting was to get the Transport and TLS documents close to finished.
>>>
>>> > I don't even recall the last time contents of the HTTP/3 spec being
>>> > discussed on list, outside of very specific issues related to
>>> transport.
>>> > I would like to see HTTP/3 written with HTTP in mind, not as a set of
>>> > diffs against h2.
>>>
>>> That is by charter; we're largely limited to mapping H2 onto QUIC.
>>>
>>> > This is not a small undertaking, but it isn't a massive one either..
>>> > Basically, import the bits of h2 that are necessary to explain
>>> > HTTP/3's operation and intent, and then start referencing the
>>> > http-core drafts instead of 723x. Yes, I know that is risky, but it is
>>> the right thing to do.
>>> > And it needs to be done before http-core is finished, since that
>>> > effort exists largely to place the right content (in the right places)
>>> > for
>>> > HTTP/3 to reference.
>>>
>>> AIUI that is still our intent, and shouldn't be impeded by the
>>> late-stage process, since that work should be editorial.
>>>
>>> > I have no idea what the status is with QPACK, but we should learn a
>>> > lesson from the last time and make sure the fixed compression
>>> > dictionary (if any) is based on traffic at more than one proxy or
>>> > origin server. Or at least have each of the major deployments generate
>>> > their local "best" encoding and do some cross-testing of the N choices
>>> > (plus one or two based on a hand-crafted expert merge).
>>> >
>>> > I would like for HTTP/3 to have a mechanism for communicating metadata
>>> > (like trailers) in mid-stream, both for requests (e.g., priority) and
>>> > responses (e.g., chained sigs). That has been a design goal for HTTP
>>> > since 1995 or so. HTTP/1.1 had it, albeit limited to chunked
>>> extensions.
>>> > It has been proposed multiple times and keeps getting postponed
>>> > because of "concern about scope". This is not a semantics issue (they
>>> > are just optional trailers that arrive early) -- it is a multiplex
>>> > framing issue (a new frame type and expectation to process).
>>>
>>> Where are the multiple proposals you refer to? We've been working on h3
>>> now for more than three years. If you submit them now, they'll be design
>>> issues.
>>>
>>> I'd say that the Late-Stage process (or at least the proposal of
>>> adopting it) is working exactly as intended here -- making people realise
>>> that if they still have issues / changes that they want discussed, they
>>> need to bring them to our attention now, not as we go to WGLC.
>>>
>>> Cheers,
>>>
>>> --
>>> Mark Nottingham   https://www.mnot.net/
>>>
>>>

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

<div dir=3D"ltr">I&#39;m not aware of anything important in-flight( :) ) fo=
r recovery.=C2=A0 <a href=3D"https://github.com/quicwg/base-drafts/pull/306=
6">#3066</a> has been in the editor&#39;s copy for over a week now, and did=
 not quite make -24, so I would recommend reading the editors copy.=C2=A0 T=
here is one handshake optimization PR(<a href=3D"https://github.com/quicwg/=
base-drafts/pull/3080">#3080</a>) and an alternate solution to the amplific=
ation deadlock(<a href=3D"https://github.com/quicwg/base-drafts/pull/3162">=
#3162</a>), but neither is critical in my opinion.<div><br></div><div>There=
 is a possibility=C2=A0of the discard keys conversation=C2=A0changing recov=
ery, though at least one solution(<a href=3D"https://github.com/quicwg/base=
-drafts/pull/3145">HANDSHAKE_DONE</a>) does not require any changes.=C2=A0 =
If changes are required, I expect them to be ~2-3 sentences.</div></div><br=
><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, N=
ov 12, 2019 at 7:43 PM Martin Duke &lt;<a href=3D"mailto:martin.h.duke@gmai=
l.com">martin.h.duke@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex"><div dir=3D"ltr">Put another way, I think Gor=
ry&#39;s planned review of draft-24 is probably premature.<br></div><br><di=
v class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Nov 1=
2, 2019 at 4:42 PM Martin Duke &lt;<a href=3D"mailto:martin.h.duke@gmail.co=
m" target=3D"_blank">martin.h.duke@gmail.com</a>&gt; wrote:<br></div><block=
quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1=
px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">IMO the recove=
ry draft is in the midst of a major revision dealing with the aftereffects =
of discarding the crypto timeout. Ian still has a bunch of stuff in flight =
for this. When all of those PRs land I would like to have a short period to=
 review the working draft and see if it looks good.<br></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Nov 11, 2019=
 at 7:40 AM Mike Bishop &lt;<a href=3D"mailto:mbishop@evequefou.be" target=
=3D"_blank">mbishop@evequefou.be</a>&gt; wrote:<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">I&#39;ll also note that it&#39;s relativel=
y easy from a spec perspective to allow trailers to arrive before the end o=
f the body, or to allow multiple sets of trailers to arrive.=C2=A0 I suspec=
t most clients won&#39;t process trailers until they have the body anyway, =
but the real question is what clients do with multiple trailer sets.=C2=A0 =
I&#39;m not certain whether that&#39;s in our scope or not, but that&#39;s =
a separate conversation.=C2=A0 Feel free to open an issue for that specific=
 discussion.<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 Mark Nottingham<br>
Sent: Sunday, November 10, 2019 8:01 PM<br>
To: Roy Fielding &lt;<a href=3D"mailto:fielding@gbiv.com" target=3D"_blank"=
>fielding@gbiv.com</a>&gt;<br>
Cc: Lars Eggert &lt;<a href=3D"mailto:lars@eggert.org" target=3D"_blank">la=
rs@eggert.org</a>&gt;; IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" ta=
rget=3D"_blank">quic@ietf.org</a>&gt;<br>
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the L=
ate-Stage Process<br>
<br>
Hi Roy,<br>
<br>
Responding to the parts relevant to this CfC.<br>
<br>
&gt; On 7 Nov 2019, at 5:39 am, Roy T. Fielding &lt;<a href=3D"mailto:field=
ing@gbiv.com" target=3D"_blank">fielding@gbiv.com</a>&gt; wrote:<br>
&gt; <br>
&gt;&gt; On Nov 5, 2019, at 5:01 PM, Mark Nottingham &lt;<a href=3D"mailto:=
mnot@mnot.net" target=3D"_blank">mnot@mnot.net</a>&gt; wrote:<br>
&gt;&gt; <br>
&gt;&gt; Previously, we&#39;ve moved to the &#39;late-stage process&#39; do=
cumented at [1] for the Transport and TLS drafts. The chairs and editors no=
w feel that it&#39;s time to move the Recovery, HTTP/3, and QPACK drafts to=
 that process as well.<br>
&gt;&gt; <br>
&gt;&gt; As before, this is because we&#39;re getting to a stage we feel th=
e documents would benefit from slower and slightly more formal process, so =
that the rate of change is not so high, changes that do occur are well-vett=
ed, and the documents get closer to reflecting consensus in the working gro=
up.<br>
&gt; <br>
&gt; I don&#39;t think that process has worked well for QUIC.<br>
<br>
Noted.<br>
<br>
&gt; There are specific issues that are contentious enough to timebox and <=
br>
&gt; conclude, in a formal (and faster) fashion than was done before.<br>
&gt; That makes sense when needed for a specific issue. I don&#39;t know of=
 any <br>
&gt; such issues for those three drafts. IOW, I don&#39;t know of any issue=
s <br>
&gt; for which it makes sense for the Chairs to pre-empt the specification =
<br>
&gt; authors in deciding what can or cannot result in changes to the drafts=
 <br>
&gt; just because of the timing of when the issue was raised.<br>
<br>
You misunderstand the process; the Chairs aren&#39;t pre-empting anything, =
the group is attempting to agree to a path to completing this work.<br>
<br>
&gt; The late-stage process seems to focus all of our energy into <br>
&gt; in/out-of-scope arguments rather than actual text in the specification=
s.<br>
<br>
I don&#39;t see any evidence for that claim; what makes you believe that?<b=
r>
<br>
&gt; The last interim spent easily twice as much time discussing process <b=
r>
&gt; and process planning than it did HTTP/3. Prior interims were worse.<br=
>
<br>
We spent a day talking about transport and TLS, part of a morning talking a=
bout planning the future of our work (if you want to call that &quot;proces=
s and process planning&quot;) and the bulk of the (longer) afternoon sessio=
n talking about H3. This isn&#39;t surprising, since our goal for the meeti=
ng was to get the Transport and TLS documents close to finished.<br>
<br>
&gt; I don&#39;t even recall the last time contents of the HTTP/3 spec bein=
g <br>
&gt; discussed on list, outside of very specific issues related to transpor=
t.<br>
&gt; I would like to see HTTP/3 written with HTTP in mind, not as a set of =
<br>
&gt; diffs against h2.<br>
<br>
That is by charter; we&#39;re largely limited to mapping H2 onto QUIC. <br>
<br>
&gt; This is not a small undertaking, but it isn&#39;t a massive one either=
..<br>
&gt; Basically, import the bits of h2 that are necessary to explain <br>
&gt; HTTP/3&#39;s operation and intent, and then start referencing the <br>
&gt; http-core drafts instead of 723x. Yes, I know that is risky, but it is=
 the right thing to do.<br>
&gt; And it needs to be done before http-core is finished, since that <br>
&gt; effort exists largely to place the right content (in the right places)=
 <br>
&gt; for<br>
&gt; HTTP/3 to reference.<br>
<br>
AIUI that is still our intent, and shouldn&#39;t be impeded by the late-sta=
ge process, since that work should be editorial.<br>
<br>
&gt; I have no idea what the status is with QPACK, but we should learn a <b=
r>
&gt; lesson from the last time and make sure the fixed compression <br>
&gt; dictionary (if any) is based on traffic at more than one proxy or <br>
&gt; origin server. Or at least have each of the major deployments generate=
 <br>
&gt; their local &quot;best&quot; encoding and do some cross-testing of the=
 N choices <br>
&gt; (plus one or two based on a hand-crafted expert merge).<br>
&gt; <br>
&gt; I would like for HTTP/3 to have a mechanism for communicating metadata=
 <br>
&gt; (like trailers) in mid-stream, both for requests (e.g., priority) and =
<br>
&gt; responses (e.g., chained sigs). That has been a design goal for HTTP <=
br>
&gt; since 1995 or so. HTTP/1.1 had it, albeit limited to chunked extension=
s.<br>
&gt; It has been proposed multiple times and keeps getting postponed <br>
&gt; because of &quot;concern about scope&quot;. This is not a semantics is=
sue (they <br>
&gt; are just optional trailers that arrive early) -- it is a multiplex <br=
>
&gt; framing issue (a new frame type and expectation to process).<br>
<br>
Where are the multiple proposals you refer to? We&#39;ve been working on h3=
 now for more than three years. If you submit them now, they&#39;ll be desi=
gn issues.<br>
<br>
I&#39;d say that the Late-Stage process (or at least the proposal of adopti=
ng it) is working exactly as intended here -- making people realise that if=
 they still have issues / changes that they want discussed, they need to br=
ing them to our attention now, not as we go to WGLC.<br>
<br>
Cheers,<br>
<br>
--<br>
Mark Nottingham=C2=A0 =C2=A0<a href=3D"https://www.mnot.net/" rel=3D"norefe=
rrer" target=3D"_blank">https://www.mnot.net/</a><br>
<br>
</blockquote></div>
</blockquote></div>
</blockquote></div>

--0000000000009cf09305973b5548--


From nobody Wed Nov 13 06:47:58 2019
Return-Path: <olivier.bonaventure@tessares.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 91EC6120809 for <quic@ietfa.amsl.com>; Wed, 13 Nov 2019 06:47:57 -0800 (PST)
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, SPF_HELO_NONE=0.001, 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=tessares-net.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 OvoqP_HKdc1o for <quic@ietfa.amsl.com>; Wed, 13 Nov 2019 06:47:55 -0800 (PST)
Received: from mail-wr1-x436.google.com (mail-wr1-x436.google.com [IPv6:2a00:1450:4864:20::436]) (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 236E712003E for <quic@ietfa.amsl.com>; Wed, 13 Nov 2019 06:47:55 -0800 (PST)
Received: by mail-wr1-x436.google.com with SMTP id r10so2694904wrx.3 for <quic@ietfa.amsl.com>; Wed, 13 Nov 2019 06:47:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tessares-net.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=wjaU9DP+omd2QNZNMQSJD+n4NmXnBCeb5WI0ereCpik=; b=WpYgrnA2RoMaPUevW7cnHLSV/UfvJEG/1Y6+sGyvshUiUZsnR+ciGlXuJEeSchGccg ikBZXVbXoB5Yev8AWJ51dlqdm9lKSZGm3oR9tu9+cyTqvbkujxf58/OOkCUaLqaZAePW Utk/lnPyz+JO8PrLc3fKKLrHNB08lKMGpZ8p6av8dPbkHtABkgsAp47LN88bSrocNF63 OeNyypJGsUkxQLJHKH+NEEc2DUP/HHRbrjamX2L/wFnpgiJvNM4uAn0S49VXoT538sYc q58TzMsZmnI2ILFZzp1b77+G0gxZVg59sCf1w4yLnWYDY/0UX7PqLxYyKryFBlCyhmS/ RruA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=wjaU9DP+omd2QNZNMQSJD+n4NmXnBCeb5WI0ereCpik=; b=d9tI3/xECXd9Md3FmWVsAJVkYrPo0T/ILTFoo1BqzNCkxtsBhTV2OTDCQPC/NNuIsw BIGJnoi2h+qDmDn5reVmzRx6oxsuCQZKM2vG999bEa/y5/1zPTIf1wRDcGRwj00eFN8a UK3Ce6GRJrL0q5WQJ3km+41P8H9SIlY/h2UFBaebixdM7fdiGcCHAdk6ReqZgy6IV88c /B3fQCrOWYBEzPbwPIpCS9BRHIe2nBq/H2B2HyIlbC74HgcZslnkh+qwDWmlqK46vGrl nd9Ez4kH92KX7fpGpMmb7qwlKg+9TOfL0ikjot9o/F3OYrlHd3mTMxJUVehaqyIZ/uCo ggUw==
X-Gm-Message-State: APjAAAVsCr+eT4ia4fY5b2/puiNwnEYzIRaDgp1nNIrRHHjfN+3195DH LG/++ClfU7rSr4+hRStbJP9z9SEF+NeKGCsYsuHnH6Z9AixWlBtGH5d+AYHazczUaZ4hYDXihZk Bb/JM
X-Google-Smtp-Source: APXvYqwvMClZScDOVgTaO/oLhpm2q2PcOh8EU5pNZN1tFMac5tTQFdGwt+tPxv8nMF2Cit8fsDXvZg==
X-Received: by 2002:a5d:4201:: with SMTP id n1mr2949504wrq.372.1573656473455;  Wed, 13 Nov 2019 06:47:53 -0800 (PST)
Received: from ?IPv6:2001:6a8:308f:2:d100:c578:f529:d141? ([2001:6a8:308f:2:d100:c578:f529:d141]) by smtp.gmail.com with ESMTPSA id t5sm2970347wro.76.2019.11.13.06.47.51 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Nov 2019 06:47:51 -0800 (PST)
From: Olivier Bonaventure <olivier.bonaventure@tessares.net>
Message-Id: <F6AB011B-FCC5-4545-B11F-827234E86FFB@tessares.net>
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: QUIC help
Date: Wed, 13 Nov 2019 15:47:50 +0100
In-Reply-To: <CAP6FE_LZ-LXDzaF+=45T6hvZQ8P52wnXpJ9Hb71tmAO9N7+omg@mail.gmail.com>
Cc: quic@ietfa.amsl.com
To: Bilal Ahmad <bilal.cybrog@gmail.com>
References: <CAP6FE_Lm6rtY9Fwr0UkrrxCn_hHFra03GrUGeo7LcETYZSwHcA@mail.gmail.com> <CAP6FE_LZ-LXDzaF+=45T6hvZQ8P52wnXpJ9Hb71tmAO9N7+omg@mail.gmail.com>
X-Mailer: Apple Mail (2.3445.104.11)
Content-Type: multipart/alternative; boundary="Apple-Mail=_273479D2-24C2-4FCB-A064-2E45A6E43D74"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/WNuwUgL2U67LeI6uHnrRbBauI7c>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Nov 2019 14:47:58 -0000

--Apple-Mail=_273479D2-24C2-4FCB-A064-2E45A6E43D74
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset="UTF-8"

Hello,

>=20
> I am a research student I want to do research in QUIC protocol.
> please guide me how to implement it on a pc.
>=20
> also can you please help in establishing a direction as to what aspect
> of quic should i be focusing on?
>=20

If you=E2=80=99d like to look beyond the version of QUIC that is currently =
being finalised within this working group, you might want to check Pluginiz=
ed QUIC that was presented at SIGCOMM=E2=80=9919 in August, see https://pqu=
ic.org <https://pquic.org/>

This article and the associated code demonstrate how it is possible to crea=
te a truly extensible protocol on top of QUIC.


Olivier


--=20


Disclaimer: https://www.tessares.net/mail-disclaimer/=20
<https://www.tessares.net/mail-disclaimer/>



--Apple-Mail=_273479D2-24C2-4FCB-A064-2E45A6E43D74
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset="UTF-8"

<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html; charset=
=3Dutf-8"></head><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: s=
pace; line-break: after-white-space;" class=3D"">Hello,<br class=3D""><div>=
<br class=3D""><blockquote type=3D"cite" class=3D""><div class=3D""><br cla=
ss=3D""></div><div class=3D""><div dir=3D"ltr" class=3D""><div class=3D"gma=
il_quote"><div dir=3D"ltr" class=3D""><div class=3D"">I am a research stude=
nt I want to do research in QUIC protocol.</div><div class=3D"">please guid=
e me how to implement it on a pc.</div><div class=3D""><br class=3D""></div=
><div class=3D"">also can you please help in establishing a direction as to=
 what aspect</div><div class=3D"">of quic should i be focusing on?</div><di=
v class=3D""><br class=3D""></div></div></div></div></div></blockquote><br =
class=3D""></div><div>If you=E2=80=99d like to look beyond the version of Q=
UIC that is currently being finalised within this working group, you might =
want to check Pluginized QUIC that was presented at SIGCOMM=E2=80=9919 in A=
ugust, see&nbsp;<a href=3D"https://pquic.org" class=3D"">https://pquic.org<=
/a></div><div><br class=3D""></div><div>This article and the associated cod=
e demonstrate how it is possible to create a truly extensible protocol on t=
op of QUIC.</div><div><br class=3D""></div><div><br class=3D""></div><div>O=
livier</div><br class=3D""></body></html>
<br>
<div><hr><br></div><div>Disclaimer: <a href=3D"https://www.tessares.net/mai=
l-disclaimer/" target=3D"_blank">https://www.tessares.net/mail-<wbr>disclai=
mer/</a></div><br><br>
--Apple-Mail=_273479D2-24C2-4FCB-A064-2E45A6E43D74--


From nobody Wed Nov 13 10:07:46 2019
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 4A87A12083E for <quic@ietfa.amsl.com>; Wed, 13 Nov 2019 10:07:45 -0800 (PST)
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, SPF_HELO_NONE=0.001, 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 0OMQ4fwvNKKk for <quic@ietfa.amsl.com>; Wed, 13 Nov 2019 10:07:41 -0800 (PST)
Received: from mx36-out10.antispamcloud.com (mx36-out10.antispamcloud.com [209.126.121.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 E509F1201E4 for <quic@ietfa.amsl.com>; Wed, 13 Nov 2019 10:07:40 -0800 (PST)
Received: from xse37.mail2web.com ([66.113.196.37] helo=xse.mail2web.com) by mx147.antispamcloud.com with esmtp (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1iUx3G-000vK7-5d for quic@ietfa.amsl.com; Wed, 13 Nov 2019 19:07:38 +0100
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 47Csyb6TNmzPGX for <quic@ietfa.amsl.com>; Wed, 13 Nov 2019 10:07:19 -0800 (PST)
Received: from [10.5.2.17] (helo=xmail07.myhosting.com) by xsmtp22.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1iUx31-0007h3-PX for quic@ietfa.amsl.com; Wed, 13 Nov 2019 10:07:19 -0800
Received: (qmail 4701 invoked from network); 13 Nov 2019 18:07:19 -0000
Received: from unknown (HELO [192.168.1.101]) (Authenticated-user:_huitema@huitema.net@[172.58.43.57]) (envelope-sender <huitema@huitema.net>) by xmail07.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietfa.amsl.com>; 13 Nov 2019 18:07:18 -0000
To: Stephane Bortzmeyer <bortzmeyer@nic.fr>, Bilal Ahmad <bilal.cybrog@gmail.com>
Cc: quic@ietfa.amsl.com
References: <CAP6FE_Lm6rtY9Fwr0UkrrxCn_hHFra03GrUGeo7LcETYZSwHcA@mail.gmail.com> <CAP6FE_LZ-LXDzaF+=45T6hvZQ8P52wnXpJ9Hb71tmAO9N7+omg@mail.gmail.com> <20191113093407.GA4508@nic.fr>
From: Christian Huitema <huitema@huitema.net>
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mQENBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAG0J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PokBOQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1a5AQ0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAYkCPgQYAQIACQUCUhFfyAIb 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=
Subject: Re: QUIC help
Message-ID: <f488238a-65ee-b9c1-f968-a28e4cb28a7b@huitema.net>
Date: Wed, 13 Nov 2019 10:07:21 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <20191113093407.GA4508@nic.fr>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
X-Originating-IP: 66.113.196.37
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.37/32
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.37/32@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0Z++tGVgV1MWB9kSxAKl4kKpSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDceGzv+wS9oC4Vk5rw8X9cnYe n+J8LbmTFZJbF1CZD7v+aOyE94bCJzSkl84geWnweJpLxjaPHE1A/OyZ+V+dxC9s3DgKO4QdUxeG AAnmp0CDwIE7VKe+bqpcdCns72R1URzHV2UpApfApmkkDNjbLA7GrRD93GuKsil0DsNlfaQNjS91 xLLHjz8tOnVewUzjKn6AaXxoL/FjeXc4guU5t5coTPkiAq+E/1gvF2d40ruQVyADaS6UpCBADjTx teudCa15Ytj/yAhGv8ezOASMHW/bWfgucjnNmABpGhD9TTsjQT2BGVI0EbGkW8Q42wJCdCZm6kTr qH+fmxyzQoG+NtezYqxGMqsKjARq8PBC4qjRn0hhkccum+xyb3k4eNalTAas0edmB2q/yBRqnQY9 Wp4oEuFb796V1/nl3YbqwU/VPb6Z51AWQAUvAUQbV3oqEaMjfjmXaBok2IyAEprch60jiD6XqsJZ tjQxlyCdsewQZJiID0Ba06Dnbk5+bPUDoBpdWj8QLYr5sN4Ugz0tezZ/mxJplDU/MSz6JmS6ZDab JmbLKfimc9IY7lEctyyjLbzWAQKOlhY3a+u7MCOwIEXw8BMIsfBCWTvqwtHGsGbsxBoFbdIyTZwD 0tTyhMSsnV/1XRbqau8px5I6KMdIbmre/hsBBxzR0ZxLcHZ9dOjdlboxOb/r1ZAig7SSZFWHqz5x NrvQl6RVRjtcqn4T4UstzZkoLPdHmQi52IQXpttQ1PPVpj0QExLpVlfUns1Ufqb5R4VemuUI6bcE ARsm0De6PaZO6/JToEyx4tmc5OljkPSpPXAVjl2oMr8a1xm0wfXUFMjTH2DyD8i5kO5bZlYFvf25 LVONYbYifH5OzZCwIgD/xDehea09OpnwSuobZrrGExMR7eTbBjMGDKI3ijhhJn7Muv/NHXl0o++8 3wM=
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/O1_ljOAjbuoKiEGi8duB6n7JbWA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 13 Nov 2019 18:07:45 -0000

On 11/13/2019 1:34 AM, Stephane Bortzmeyer wrote:
> On Wed, Nov 13, 2019 at 11:59:14AM +0500,
>  Bilal Ahmad <bilal.cybrog@gmail.com> wrote=20
>  a message of 29 lines which said:
>
>> I am a research student I want to do research in QUIC protocol.
>> please guide me how to implement it on a pc.
> Well, QUIC is a complicated protcol, with a lot of things to take care
> of, so implementing QUIC from scratch seems a daunting task.
>
> It may be easier to start from existing implementations. See
> <https://github.com/ngtcp2/ngtcp2> and
> <https://github.com/ngtcp2/nghttp3> and <https://github.com/cloudflare/=
quiche>.

The Quic WG maintains a list of implementations is at
https://github.com/quicwg/base-drafts/wiki/Implementations. There are
many of these to chose from, in a variety of programming languages and
with different objectives, not just two...

>> also can you please help in establishing a direction as to what aspect=

>> of quic should i be focusing on?
> There are many. It depends on your abilities / tastes. Cryptography?
> Congestion? HTTP?
>
> Which documents did you read? The Internet-Drafts are of course
> necessary but they may be hard for a complete beginner. I recommend
> <https://daniel.haxx.se/blog/2018/11/26/http3-explained/> for a start.

Several of the implementations listed above were done by academics, with
focus such as tests or studies. If the goal is to conduct studies, I
would suggest contacting these teams.

-- Christian Huitema




From nobody Wed Nov 13 17:25:56 2019
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 4C2C512004E for <quic@ietfa.amsl.com>; Wed, 13 Nov 2019 17:25:54 -0800 (PST)
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=zMeGTAXP; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=OM9gXxGB
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 K56tz_N4f8l7 for <quic@ietfa.amsl.com>; Wed, 13 Nov 2019 17:25:52 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EDCD2120044 for <quic@ietf.org>; Wed, 13 Nov 2019 17:25:51 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id 0E7A022076; Wed, 13 Nov 2019 20:25:51 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Wed, 13 Nov 2019 20:25:51 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=from :content-type:content-transfer-encoding:mime-version:subject :message-id:date:cc:to; s=fm1; bh=joS9LUq+3WRQwhos7iRmO4LFBH7eu5 TufdoJd2IcyGg=; b=zMeGTAXPjNjTx/DcwFm7fqB8arMp6K8Mft0C6q5n6dcVT7 KX+DmAfOn4SZRMhKmowBG3CQZPntT457lrWAG9yLIgskTRCRCGYBkZhJ/weS/ByV R/zUzmXrdnge1lEkf08EN/KEdhm8IaErzC3E9zkzRaCgt3who7TFt4Ptem6Hrw2o kwTHGIGWJo5RdF2iAMIZRKnP+KL4AQAYc0X6xHZzE01S3G+Ds3s9ldMkHGoOzuga Q63tuqVHrT9ZD3L+fwSFcaUdj8nyixIEatVjMLO0SaCUpP/unYBwyxXVR53S2rGG 7d6ytxT03BF8SRJDFrqlVxDtIEuFrlxe2Q0IWlvg==
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-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=joS9LU q+3WRQwhos7iRmO4LFBH7eu5TufdoJd2IcyGg=; b=OM9gXxGB5taJI0pZkrvTjM /1zdYtCiQu8EapQlxyAe6jA5hTCXO7wzkSi0TEw+CUV5NdkPodI3+TchS/nwOtlE oczUQqH3tgL2uHQnkxjsBCbaxHOALP9bJbOw+X3g12YtrGveDbjAbJYLcsK/538v X/TPQOGWGaZjSOH/b6rjYi4IDwXjCK0jL9COY5OpNlj0IB4Uer4ALpodgPq3kwFn VtFu+oxGXKIEBNzsZkzT8OuRztr8VDC2ZYjZEzjrTk6ScL9MaqNffafbGo8Mfcqg HNtLv6i29B/kVEKixRGjv174QqWHl6/S1SJpGefGLyQi0Q35ZxjEYP7P5GAftxlQ ==
X-ME-Sender: <xms:Hq3MXVwMCm7k7rj9jqGIyBpBXrdIk4nTfOSiHqkjY4tI2bCBFYCuVA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudefvddgfeegucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephfgtgfgguffkfffvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhkucfp ohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinhepgh hithhhuhgsrdgtohhmpdhmnhhothdrnhgvthenucfkphepudduledrudejrdduheekrddv hedunecurfgrrhgrmhepmhgrihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvghtnecuve hluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:Hq3MXQKgbMAKw98iOcUk1XZHj8MHW0csKYx3HZWqZa6eYtrt2lBEbQ> <xmx:Hq3MXSMJvuXwOu4PgPxu1zum1ECOrvFzHuO5JqNH2iLMgxGOByIS9A> <xmx:Hq3MXRMLBR-57rDp_Jz2qH7zOhvZYIsZq73wjzOe5atyW0F9dh4MTg> <xmx:Hq3MXRV0P9OPHkgUjJjd0_erK4j0zCLn5_PdOJQ2k68DGJndFQTltA>
Received: from attitudadjuster.mnot.net (unknown [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id 6A73B80061; Wed, 13 Nov 2019 20:25:49 -0500 (EST)
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 13.0 \(3601.0.10\))
Subject: Consensus Calls for Transport/TLS issues, pre-Singapore
Message-Id: <67289EB8-3A37-4231-A3F9-FB46509152A0@mnot.net>
Date: Thu, 14 Nov 2019 12:25:46 +1100
Cc: Lars Eggert <lars@eggert.org>
To: IETF QUIC WG <quic@ietf.org>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/IqpTYWaDXdaJsXhZfJlAYhDs1TY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Nov 2019 01:25:54 -0000

The following issues have proposals for resolution, and discussion so =
far seems to support consensus to accept them. If you object, please do =
so on the issue or in response to this message (changing the Subject =
appropriately!). Absent any pushback, we'll direct the editors to =
incorporate them late next week. Note that by default we won't discuss =
these issues in Singapore, unless something comes up.

See <https://github.com/quicwg/base-drafts/projects/5> for the current =
state of issues in the Late Stage process, itself defined at =
<https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md>.

* #3127: NEW_TOKEN and Retry tokens must be distinguishable
  Proposal: https://github.com/quicwg/base-drafts/pull/3128

* #3158: Application close should be disallowed in Initial or Handshake
  Proposal: https://github.com/quicwg/base-drafts/pull/3164

* #3155: The method of identifying "the same server"
  Proposal: https://github.com/quicwg/base-drafts/pull/3156

* #2475: Invalid CONNECTION_CLOSE frames
  Proposal: https://github.com/quicwg/base-drafts/pull/3231

* #3168: Allow servers to close connections immediately when the token =
is corrupted
  Proposal: https://github.com/quicwg/base-drafts/pull/3107

* #3194: reordered NEW_CONNECTION_ID frames with retired sequence =
numbers shouldn't be used
  Proposal: https://github.com/quicwg/base-drafts/pull/3202

* #3014: Handling of corrupt Retry packets
  Proposal: https://github.com/quicwg/base-drafts/pull/3120

* #3095: Backoff of CONNECTION_CLOSE needs to be a MUST
  Proposal: https://github.com/quicwg/base-drafts/pull/3157


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


From nobody Thu Nov 14 00:51:18 2019
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 A06D712010C for <quic@ietfa.amsl.com>; Thu, 14 Nov 2019 00:51:17 -0800 (PST)
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_HELO_NONE=0.001, 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 Tl7M6UOtj5zQ for <quic@ietfa.amsl.com>; Thu, 14 Nov 2019 00:51:15 -0800 (PST)
Received: from mail-ed1-x536.google.com (mail-ed1-x536.google.com [IPv6:2a00:1450:4864:20::536]) (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 1C1CD120945 for <quic@ietf.org>; Thu, 14 Nov 2019 00:51:15 -0800 (PST)
Received: by mail-ed1-x536.google.com with SMTP id x11so4282221eds.13 for <quic@ietf.org>; Thu, 14 Nov 2019 00:51:15 -0800 (PST)
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=XIS4GWh0/EycLCcGXW26sk/KZhFcRL+U2QYUe6ijvHw=; b=Xf8UX500Udh+3LGeKa9ojnmt9JGhjaRDTqBTluMFRen33zlhrtUrWWI7GCPUlh6tHT jRuUbMLuy5yM66AifDVII6Njb1EAGpD6MqKmDV+qJ1rfAfkJoFKwpwE0lP6XtM2BeZ09 /Af+yab2ip9F+YCAJ8jp0NYfPLLd8l6eoGWp2iYvb3KOqK/VFAQyoDdnXWlND0NjO1GJ 54Fp9YMTKJf4ydVBKXEnzBYoSUQ7PpAIbhqA+yqJaNXPgXGQpW+HJ9p/XgFk7srMsyhX /PjgeFmdOPjusexe5vj7CrWPBwuYeAgud7mlkCbcfXWiKiq/k8+GtuFHjak38Cl2nHjP otXQ==
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=XIS4GWh0/EycLCcGXW26sk/KZhFcRL+U2QYUe6ijvHw=; b=XKnZJ01kNfG1FQGY0qolXoqQfISWheeYejn6dO71M48lhBT6XTQqs4o9E9Z1ObyZsR Ke9p4MRQ2fJK3a9bgfZo669fBBwaNeas9jaX3IW1CE+/sUBlEQD+kfG97SpZ9HufUQTQ MSiCWdDdp1YS45sNnFEFbgfUA2uCXoqfTv8D13q6TMCVB7AYvBYTDWrgmPjV3MgNrtoH yyoitqj6LT022Qr3m1g2luwd1rFLKvMw0zAvR4Z1yb7StVV/Wr0w1hRBI+NHXVpnKoDb MjYMPaN9tfp+q8/JTlFJ1x7cD2c8Y5/XX5KhK4Pesr2dxDwY6hFGTZErRtC4iImfcfaz yiYg==
X-Gm-Message-State: APjAAAVhVEP9vPtzQX4eSVr1nrvZV0iTlbqde/+Yf8tnOtwr2jpt+4oB ptp4r8uQRViQpP1m1ZBcl9dv02E/WvhOjYzHYgvlwoeS
X-Google-Smtp-Source: APXvYqzP/GMlLr1nlVzxXWI4OhzKI+vLaw2AIi8nrGOGmZx/MRA7J5fY/7GrS9paZTCLqPypibHleyglPaoTgzuUf2s=
X-Received: by 2002:aa7:ce96:: with SMTP id y22mr8794570edv.100.1573721473461;  Thu, 14 Nov 2019 00:51:13 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 14 Nov 2019 09:51:12 +0100
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <67289EB8-3A37-4231-A3F9-FB46509152A0@mnot.net>
References: <67289EB8-3A37-4231-A3F9-FB46509152A0@mnot.net>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Thu, 14 Nov 2019 09:51:12 +0100
Message-ID: <CAN1APdcnfQyoy3PQt=3ztp7uOvHob__C633NvJyqHQmdxriMbg@mail.gmail.com>
Subject: Re: Consensus Calls for Transport/TLS issues, pre-Singapore
To: IETF QUIC WG <quic@ietf.org>, Mark Nottingham <mnot@mnot.net>
Cc: Lars Eggert <lars@eggert.org>
Content-Type: multipart/alternative; boundary="00000000000066b14a05974a9579"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/dZFrOvN0Hcr9_ZWKJqVtGcZoJuo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Nov 2019 08:51:18 -0000

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

I added a comment to

 #3155: The method of identifying "the same server"


https://github.com/quicwg/base-drafts/pull/3156/files#r346186298

I=E2=80=99m not sure the MUST / SHOULD is correct in this case. Although I =
do agree
that server identify should not be limited to server certificates (I
proposed that myself).

Mikkel

On 14 November 2019 at 02.26.05, Mark Nottingham (mnot@mnot.net) wrote:

The following issues have proposals for resolution, and discussion so far
seems to support consensus to accept them. If you object, please do so on
the issue or in response to this message (changing the Subject
appropriately!). Absent any pushback, we'll direct the editors to
incorporate them late next week. Note that by default we won't discuss
these issues in Singapore, unless something comes up.

See <https://github.com/quicwg/base-drafts/projects/5> for the current
state of issues in the Late Stage process, itself defined at <
https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md>.

* #3127: NEW_TOKEN and Retry tokens must be distinguishable
Proposal: https://github.com/quicwg/base-drafts/pull/3128

* #3158: Application close should be disallowed in Initial or Handshake
Proposal: https://github.com/quicwg/base-drafts/pull/3164

* #3155: The method of identifying "the same server"
Proposal: https://github.com/quicwg/base-drafts/pull/3156

* #2475: Invalid CONNECTION_CLOSE frames
Proposal: https://github.com/quicwg/base-drafts/pull/3231

* #3168: Allow servers to close connections immediately when the token is
corrupted
Proposal: https://github.com/quicwg/base-drafts/pull/3107

* #3194: reordered NEW_CONNECTION_ID frames with retired sequence numbers
shouldn't be used
Proposal: https://github.com/quicwg/base-drafts/pull/3202

* #3014: Handling of corrupt Retry packets
Proposal: https://github.com/quicwg/base-drafts/pull/3120

* #3095: Backoff of CONNECTION_CLOSE needs to be a MUST
Proposal: https://github.com/quicwg/base-drafts/pull/3157


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

--00000000000066b14a05974a9579
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">I added a comment to=
</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"><blockquote type=3D"=
cite" class=3D"clean_bq">=C2=A0#3155: The method of identifying &quot;the s=
ame server&quot;=C2=A0</blockquote></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;lin=
e-height:auto"><a href=3D"https://github.com/quicwg/base-drafts/pull/3156/f=
iles#r346186298">https://github.com/quicwg/base-drafts/pull/3156/files#r346=
186298</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"><b=
r></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">I=E2=80=99=
m not sure the MUST / SHOULD is correct in this case. Although I do agree t=
hat server identify should not be limited to server certificates (I propose=
d that myself).</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"><br></div> <div id=3D"bloop_sign_1573721383938867200" class=3D"bloop_sig=
n"><div style=3D"font-size:13px">Mikkel</div></div> <br><p class=3D"airmail=
_on">On 14 November 2019 at 02.26.05, Mark Nottingham (<a href=3D"mailto:mn=
ot@mnot.net">mnot@mnot.net</a>) wrote:</p> <blockquote type=3D"cite" class=
=3D"clean_bq"><span><div><div></div><div>The following issues have proposal=
s for resolution, and discussion so far seems to support consensus to accep=
t them. If you object, please do so on the issue or in response to this mes=
sage (changing the Subject appropriately!). Absent any pushback, we&#39;ll =
direct the editors to incorporate them late next week. Note that by default=
 we won&#39;t discuss these issues in Singapore, unless something comes up.
<br>
<br>See &lt;<a href=3D"https://github.com/quicwg/base-drafts/projects/5">ht=
tps://github.com/quicwg/base-drafts/projects/5</a>&gt; for the current stat=
e of issues in the Late Stage process, itself defined at &lt;<a href=3D"htt=
ps://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md">https://git=
hub.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md</a>&gt;.
<br>
<br>* #3127: NEW_TOKEN and Retry tokens must be distinguishable
<br>  Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3128"=
>https://github.com/quicwg/base-drafts/pull/3128</a>
<br>
<br>* #3158: Application close should be disallowed in Initial or Handshake
<br>  Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3164"=
>https://github.com/quicwg/base-drafts/pull/3164</a>
<br>
<br>* #3155: The method of identifying &quot;the same server&quot;
<br>  Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3156"=
>https://github.com/quicwg/base-drafts/pull/3156</a>
<br>
<br>* #2475: Invalid CONNECTION_CLOSE frames
<br>  Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3231"=
>https://github.com/quicwg/base-drafts/pull/3231</a>
<br>
<br>* #3168: Allow servers to close connections immediately when the token =
is corrupted
<br>  Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3107"=
>https://github.com/quicwg/base-drafts/pull/3107</a>
<br>
<br>* #3194: reordered NEW_CONNECTION_ID frames with retired sequence numbe=
rs shouldn&#39;t be used
<br>  Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3202"=
>https://github.com/quicwg/base-drafts/pull/3202</a>
<br>
<br>* #3014: Handling of corrupt Retry packets
<br>  Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3120"=
>https://github.com/quicwg/base-drafts/pull/3120</a>
<br>
<br>* #3095: Backoff of CONNECTION_CLOSE needs to be a MUST
<br>  Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3157"=
>https://github.com/quicwg/base-drafts/pull/3157</a>
<br>
<br>
<br>--
<br>Mark Nottingham   <a href=3D"https://www.mnot.net/">https://www.mnot.ne=
t/</a>
<br>
<br></div></div></span></blockquote></body></html>

--00000000000066b14a05974a9579--


From nobody Thu Nov 14 02:27:39 2019
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 2974D120879 for <quic@ietfa.amsl.com>; Thu, 14 Nov 2019 02:27:37 -0800 (PST)
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_HELO_NONE=0.001, 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 nZe8cHN2xZCb for <quic@ietfa.amsl.com>; Thu, 14 Nov 2019 02:27:34 -0800 (PST)
Received: from mail-ed1-x529.google.com (mail-ed1-x529.google.com [IPv6:2a00:1450:4864:20::529]) (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 3AB9B120857 for <quic@ietf.org>; Thu, 14 Nov 2019 02:27:34 -0800 (PST)
Received: by mail-ed1-x529.google.com with SMTP id k14so4551338eds.4 for <quic@ietf.org>; Thu, 14 Nov 2019 02:27:34 -0800 (PST)
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=cy2Mbp7rFwj2ferR6ybafCQZLPyOT3uTbVaHJbh5A5g=; b=ZNtkZZ+gsli9NJgUUdqUCrjII12R3qeha7KtEsaRhCQimaD446qL3a62nHyKlPblUO 28An+/6UU0b/tEtYhEhcmrUJIdiTSnFv1TycNMzityc8Rm/O4WGvt3ZICyv80vEeE3nI 3sZ+9xbm1qKaxM8w/0AvDj5Gv9q2Fg2BfFND6czJKgrq80CV2f+9xcdZeM+G/d/wRuVe BVfHWN/FzMf+xXJlQ1xM0YNrilC2z3fizrSIV3Enccs2N5/m12QhBraDQ2yssfK0KjEl y2q2EpdzTlHSmojQXmePzMAZVNsW6RzqEhhT1E8eJr0K+f/Z0jl+nRSax5CHjJ2SI+YZ Mr7w==
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=cy2Mbp7rFwj2ferR6ybafCQZLPyOT3uTbVaHJbh5A5g=; b=mQQxPfyi4gVhBteyScrGlqHwevAj/mXmB+eXcxmwn8Yj8f6wMeAOmOxljW/u0fMS8C TduFPm6VV72QpmwRohs3UM8O7cmrd2XTKoZg+P2Pq9DKjV2B9x85ikqlbAYyuBFmXYMl 0oMHym9QQGJRMozVjLDPQ7K9G6Qm3F25+yHS20lIhG9uu9vBAMq7I5h/0K8xmxNLWUff 0XQjSQtD6GPRvj8QLpH9zxzwwJwLZD+TjOOc+xBkM0feIwREDeZPpaw0lC2YI88Gj43o zKET7qXR777ZemRFnAsMdEZXDqWVfWG/MbobLjGaQ0LStxCQ+Jg4xa2ydJADTkFnmSxX 9l5w==
X-Gm-Message-State: APjAAAWEjrPk6OnAQuXfsX9A9FXT09LEmrmNVEp08JxuiomXjwUgrll7 XM9+Z42pULnOrLJ+yzraeIuYHWb/QisOn9udkoHGl7ue
X-Google-Smtp-Source: APXvYqxUcT7V7igy8kEx7gauvaMRVG+O/DAZ0ue/REGuYkIdPg8Hql5WEoA3TlEeAIDwoVsBh311o8dKESUI+a3OsMo=
X-Received: by 2002:a50:91f6:: with SMTP id h51mr273520eda.99.1573727252760; Thu, 14 Nov 2019 02:27:32 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Thu, 14 Nov 2019 11:27:32 +0100
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <CAN1APdcnfQyoy3PQt=3ztp7uOvHob__C633NvJyqHQmdxriMbg@mail.gmail.com>
References: <67289EB8-3A37-4231-A3F9-FB46509152A0@mnot.net> <CAN1APdcnfQyoy3PQt=3ztp7uOvHob__C633NvJyqHQmdxriMbg@mail.gmail.com>
X-Mailer: Airmail (420)
MIME-Version: 1.0
Date: Thu, 14 Nov 2019 11:27:32 +0100
Message-ID: <CAN1APdeM=Q86bAUwQ2zCw+JTns8nmt0Oo=LAKFq493WavZEtTw@mail.gmail.com>
Subject: Re: Consensus Calls for Transport/TLS issues, pre-Singapore
To: Mark Nottingham <mnot@mnot.net>, IETF QUIC WG <quic@ietf.org>
Cc: Lars Eggert <lars@eggert.org>
Content-Type: multipart/alternative; boundary="000000000000dfcf8705974bed2e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/wGhOlvPxn671T0YSlTXYxLP-baM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Nov 2019 10:27:37 -0000

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

Kazuho pointed out that the MUST is a privacy concern for the client, so it
does make sense.

On 14 November 2019 at 09.51.12, Mikkel Fahn=C3=B8e J=C3=B8rgensen (mikkelf=
j@gmail.com)
wrote:

I added a comment to

 #3155: The method of identifying "the same server"


https://github.com/quicwg/base-drafts/pull/3156/files#r346186298

I=E2=80=99m not sure the MUST / SHOULD is correct in this case. Although I =
do agree
that server identify should not be limited to server certificates (I
proposed that myself).

Mikkel

On 14 November 2019 at 02.26.05, Mark Nottingham (mnot@mnot.net) wrote:

The following issues have proposals for resolution, and discussion so far
seems to support consensus to accept them. If you object, please do so on
the issue or in response to this message (changing the Subject
appropriately!). Absent any pushback, we'll direct the editors to
incorporate them late next week. Note that by default we won't discuss
these issues in Singapore, unless something comes up.

See <https://github.com/quicwg/base-drafts/projects/5> for the current
state of issues in the Late Stage process, itself defined at <
https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md>.

* #3127: NEW_TOKEN and Retry tokens must be distinguishable
Proposal: https://github.com/quicwg/base-drafts/pull/3128

* #3158: Application close should be disallowed in Initial or Handshake
Proposal: https://github.com/quicwg/base-drafts/pull/3164

* #3155: The method of identifying "the same server"
Proposal: https://github.com/quicwg/base-drafts/pull/3156

* #2475: Invalid CONNECTION_CLOSE frames
Proposal: https://github.com/quicwg/base-drafts/pull/3231

* #3168: Allow servers to close connections immediately when the token is
corrupted
Proposal: https://github.com/quicwg/base-drafts/pull/3107

* #3194: reordered NEW_CONNECTION_ID frames with retired sequence numbers
shouldn't be used
Proposal: https://github.com/quicwg/base-drafts/pull/3202

* #3014: Handling of corrupt Retry packets
Proposal: https://github.com/quicwg/base-drafts/pull/3120

* #3095: Backoff of CONNECTION_CLOSE needs to be a MUST
Proposal: https://github.com/quicwg/base-drafts/pull/3157


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

--000000000000dfcf8705974bed2e
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">Kazuho pointed out t=
hat the MUST is a privacy concern for the client, so it does make sense.</d=
iv><p class=3D"airmail_on">On 14 November 2019 at 09.51.12, Mikkel Fahn=C3=
=B8e J=C3=B8rgensen (<a href=3D"mailto:mikkelfj@gmail.com">mikkelfj@gmail.c=
om</a>) wrote:</p> <blockquote type=3D"cite" class=3D"clean_bq"><span><div =
style=3D"word-wrap:break-word;line-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">
I added a comment to</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">
<blockquote type=3D"cite" class=3D"clean_bq">=C2=A0#3155: The method of
identifying &quot;the same server&quot;=C2=A0</blockquote>
</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">
<a href=3D"https://github.com/quicwg/base-drafts/pull/3156/files#r346186298=
">https://github.com/quicwg/base-drafts/pull/3156/files#r346186298</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_customfont" style=3D"font-family:Helvetica,Arial;font-size=
:13px;color:rgba(0,0,0,1.0);margin:0px;line-height:auto">
I=E2=80=99m not sure the MUST / SHOULD is correct in this case. Although I
do agree that server identify should not be limited to server
certificates (I proposed that myself).</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_sign_1573721383938867200" class=3D"bloop_sign">
<div style=3D"font-size:13px">Mikkel</div>
</div>
<br>
<p class=3D"airmail_on">On 14 November 2019 at 02.26.05, Mark
Nottingham (<a href=3D"mailto:mnot@mnot.net">mnot@mnot.net</a>)
wrote:</p>
<blockquote type=3D"cite" class=3D"clean_bq">
<div>
<div><span>The following issues have proposals for resolution, and
discussion so far seems to support consensus to accept them. If you
object, please do so on the issue or in response to this message
(changing the Subject appropriately!). Absent any pushback, we&#39;ll
direct the editors to incorporate them late next week. Note that by
default we won&#39;t discuss these issues in Singapore, unless
something comes up.<br>
<br>
See &lt;<a href=3D"https://github.com/quicwg/base-drafts/projects/5">https:=
//github.com/quicwg/base-drafts/projects/5</a>&gt; for
the current state of issues in the Late Stage process, itself
defined at
&lt;<a href=3D"https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTI=
NG.md">https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md</a=
>&gt;.<br>

<br>
* #3127: NEW_TOKEN and Retry tokens must be distinguishable<br>
Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3128">https=
://github.com/quicwg/base-drafts/pull/3128</a><br>
<br>
* #3158: Application close should be disallowed in Initial or
Handshake<br>
Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3164">https=
://github.com/quicwg/base-drafts/pull/3164</a><br>
<br>
* #3155: The method of identifying &quot;the same server&quot;<br>
Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3156">https=
://github.com/quicwg/base-drafts/pull/3156</a><br>
<br>
* #2475: Invalid CONNECTION_CLOSE frames<br>
Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3231">https=
://github.com/quicwg/base-drafts/pull/3231</a><br>
<br>
* #3168: Allow servers to close connections immediately when the
token is corrupted<br>
Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3107">https=
://github.com/quicwg/base-drafts/pull/3107</a><br>
<br>
* #3194: reordered NEW_CONNECTION_ID frames with retired sequence
numbers shouldn&#39;t be used<br>
Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3202">https=
://github.com/quicwg/base-drafts/pull/3202</a><br>
<br>
* #3014: Handling of corrupt Retry packets<br>
Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3120">https=
://github.com/quicwg/base-drafts/pull/3120</a><br>
<br>
* #3095: Backoff of CONNECTION_CLOSE needs to be a MUST<br>
Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3157">https=
://github.com/quicwg/base-drafts/pull/3157</a><br>
<br>
<br>
--<br>
Mark Nottingham <a href=3D"https://www.mnot.net/">https://www.mnot.net/</a>=
<br>
<br></span></div>
</div>
</blockquote>


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

--000000000000dfcf8705974bed2e--


From nobody Thu Nov 14 03:19:03 2019
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 41E67120019 for <quic@ietfa.amsl.com>; Thu, 14 Nov 2019 03:19:01 -0800 (PST)
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, SPF_HELO_NONE=0.001, SPF_NONE=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 0GAx7hUdJpn8 for <quic@ietfa.amsl.com>; Thu, 14 Nov 2019 03:18:58 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:42:150::2]) by ietfa.amsl.com (Postfix) with ESMTP id 0A42F1200A3 for <quic@ietf.org>; Thu, 14 Nov 2019 03:18:57 -0800 (PST)
Received: from G-MacBook.local (unknown [132.147.98.37]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 0A9421B0022C; Thu, 14 Nov 2019 11:18:51 +0000 (GMT)
Message-ID: <5DCD3819.5050300@erg.abdn.ac.uk>
Date: Thu, 14 Nov 2019 19:18:49 +0800
From: G Fairhurst <gorry@erg.abdn.ac.uk>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: "quic@ietf.org" <quic@ietf.org>,  gorry Fairhurst <gorry@erg.abdn.ac.uk>
Subject: comments on QUIC Recovery -24.
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/hOcCwfhtedAJix8ZBgy3Mtp1VhM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Nov 2019 11:19:01 -0000

QUIC Recovery

I have comments on QUIC Recovery -24. These sets of come join two parts, 
this is the first. I hope most of the comments below are easy to resolve:

Section 3, Para 1 last sentence. This sentence is true from the sender 
perspective, but the monotonic increase is not necessarily true at the 
receiver.

Section 3.1.2, Para 1
/is declared is acknowledged/
- maybe would be easier to read as /is declared as acknowledged/.

Section 3.1.2, Para 1
/QUIC will do it correctly once/
- There is an inference that TCP does not, and I would argue with that, 
because TCP measures the TCP loss recovery, that is often a larger 
interval than it could have been had TCP been designed differently, but 
this document is not a thesis on TCP. I would like to suggest / QUIC 
will appropriately reduce once/ as a more neutral text.

Section 3.1.6, Para 1
/allowing a peer to maintain a more accurate/ is I think an unnecessary 
judgment on TCP again, it would be fairer to say/allowing a peer to 
maintain an accurate/

The term /host delay/ appears several times, but there is no discussion 
of hosts, only endpoints. The term host delay seems odd, can we call it 
endpoint delay or perhaps even “ACK delay” which I think is closer to 
the field used for this later in the spec?

Section 4.1, final sentence
/Ensuring that RTT estimates retain sufficient history is an open 
research question/
- This is fine for an IRTF experiment, but really rests very 
uncomfortably in a standards track specification. I suggest this alone 
is not sufficient. An alternate could be to set some bound here that at 
least mitigates this - which could otherwise result in odd pathologies.

Somewhere there is this (it's in several places):
/smoothed RTT = latest RTT/
- This needs to cite an RFC.
- I'm not a huge fan of just assigning a RTT (without taking account of 
the variance) as a starting timeout. We've in the past been caught so 
many times with things being slightly or vastly different when the next 
flow starts and simply assigning the value seems like it could be the 
wrong thing to do.

Section 4 pseudo code uses both Ack_Delay and ack_delay, I don’t 
understand the difference.

Section 5
This uses /ack/ and /ACK/
- is there a difference?

Section 5.1.
/was sent long enough in the past/
- This isn’t clear, please improve the text here to explain what is 
intended.

/sent later was delivered, while …. /
- Text should be improved. I suggest /while/ is reworked to avoid the 
inference these occur in parallel.

Section 5.1.1
There is no minimum dupack threshold specified. Why not? I could be 
persuaded that the recommendation was for 3, and that more is possible, 
but when would less than 3 fit with current other recommendations in the 
RFC series ?
- also mentioned in B.1

Also 5.4 final sentence
- section 6 (last para -1) reads like this is intended as one “probe” 
packet, XXX what does RACK do in this cased with respect to CC?

Section 5.3, final sentence:
/may never be/
- seems like it would avoid all possible ambiguity in whether this is 
allowed by using /could/.

/Sending two packets on a PTO expiration increases resilience…/
- and arguably doubles the non-congestion-controlled load.

Section 6.1
/endpoints are permitted to experiment/
- This is much more than intent of RFC8311. The intent was that the IETF 
can publish experimental specs for other behaviours. That’s not the 
same, and I think the wording needs to be modified a little to reflect 
the actual consensus of the RFC.

Section 6.2
/anytime/any time/

Section 6.9
- the new text on pacing seems to be heading in the correct direction, 
but I don’t really understand how the congestion window will be managed 
if pacing is used and the connection becomes application-limited. The 
basic TCP spec would respond aggressively reducing the window; cwv would 
loosen this; what does QUIC say when pacing *is* used.

Section 7.3
/as having being marked/ should I think be /as having being CE-marked or 
lost/
- add loss.

section A.1 para 2.
- I suggest text is added that mentions the actual reordering could be 
larger and how QUIC handles this.

Section A4 - could the initialisation be clearer? - e.g. showing initial 
values for RTT etc.


From nobody Thu Nov 14 07:30:23 2019
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 12E0D120129 for <quic@ietfa.amsl.com>; Thu, 14 Nov 2019 07:30:22 -0800 (PST)
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, DKIMWL_WL_MED=-0.001, 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_HELO_NONE=0.001, SPF_PASS=-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 i3n2WDqM2flZ for <quic@ietfa.amsl.com>; Thu, 14 Nov 2019 07:30:20 -0800 (PST)
Received: from mail-ua1-x932.google.com (mail-ua1-x932.google.com [IPv6:2607:f8b0:4864:20::932]) (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 D78BB120113 for <quic@ietf.org>; Thu, 14 Nov 2019 07:30:19 -0800 (PST)
Received: by mail-ua1-x932.google.com with SMTP id k11so1981950ual.10 for <quic@ietf.org>; Thu, 14 Nov 2019 07:30:19 -0800 (PST)
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=zwMxXL710ITM5PZy83dO6ctt3eNhWOCT7WL9piWFhPk=; b=k3Wi7csgoDXhrLWKzquUpOp3Sy7carI4lXTyFmg7PR37g5CvaiMDHQNQrcHYg/WqMj 08tKsQQjwG3tiutSGO0I0MO0Fcwq5l01MMEODbZwqJXYavP3BFzmQdOjXsPzEuYV32rM ApJLIw8PNhC1RxTnQI853pLNBzSSXu/26JjANf8XPPzPZabla1TZ8ALkiOT/P4nKsv5o SsLmzC974TSF8Vj3T0DKNEddHfJf3NywqYMj7HclN4kCwtmQWtx6jlAueVjuG0r4mlH2 8BPFaEwc4Dj1TYr9ssGaf7y54SU+vjOT325QrQyvh1hAdV8f5CvGzYK30zzHA2mAM+P0 VaVw==
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=zwMxXL710ITM5PZy83dO6ctt3eNhWOCT7WL9piWFhPk=; b=FJJ3bu9zecH1dhukgA0DzlXcVSzKgn30s99xT3AIoHaikqXcFq+Jkb5+VZ93FWLvsb Nk9Iy/c/aRPK21usEeBUyOvw6OFqYKteajvPFuIG3BBGXoDCqtA0UQ/lcYm0IbCJLhKb PoArBTzK3g5rhwFdK+7ALMBAAR6RGJrPtkzO7SlVC9tYZIQYKYNjEQWsHeDmF4fmZ8kw 6tTmrHHcuMVHoUvqdKlLlT4FvLbYrkQUZC8w7ujkpodLUpu4o1OS0la0aU/E4ZBOi4Th k/jsoBsnXMhuvVa4Yua4IPM0+8v+4THD+5dDAyQr2M6MLwXZqa8azXH2N75dhLLP4DJ2 IIHg==
X-Gm-Message-State: APjAAAWMRvfaLEs4B3aO3vamlXV2Cj81aDXDHH6JlgL3GcvDPLdw0tMq 1EWjJ7Ovi23UCiBhkqX5B8ocK3mR2h1+1EG346vkM8bjPmc=
X-Google-Smtp-Source: APXvYqzfxvucxBkUMOucfnizAaVm8uffLqu7bdudm5h6iFUrOqEc/LTWhnrwhCSz0jAjYtoPPU9jHpqca8TvbHcZgaA=
X-Received: by 2002:a9f:27a4:: with SMTP id b33mr5998580uab.24.1573745418480;  Thu, 14 Nov 2019 07:30:18 -0800 (PST)
MIME-Version: 1.0
References: <5DCD3819.5050300@erg.abdn.ac.uk>
In-Reply-To: <5DCD3819.5050300@erg.abdn.ac.uk>
From: Ian Swett <ianswett@google.com>
Date: Thu, 14 Nov 2019 10:30:07 -0500
Message-ID: <CAKcm_gMuRJheKb7k7nNHuDj2-yp5s9k4jq8v+Q4kG_=_seneaA@mail.gmail.com>
Subject: Re: comments on QUIC Recovery -24.
To: G Fairhurst <gorry@erg.abdn.ac.uk>
Cc: "quic@ietf.org" <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a3306a0597502870"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/kW8HnFHQy9ddmD5vX7YNgikDAtM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 14 Nov 2019 15:30:22 -0000

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

Thanks for the review Gorry.  I'll try to fix the editorial issues in a PR
tonight and then file issues for the non-editorial comments or comments I'm
not sure how to resolve.

On Thu, Nov 14, 2019 at 6:19 AM G Fairhurst <gorry@erg.abdn.ac.uk> wrote:

> QUIC Recovery
>
> I have comments on QUIC Recovery -24. These sets of come join two parts,
> this is the first. I hope most of the comments below are easy to resolve:
>
> Section 3, Para 1 last sentence. This sentence is true from the sender
> perspective, but the monotonic increase is not necessarily true at the
> receiver.
>
> Section 3.1.2, Para 1
> /is declared is acknowledged/
> - maybe would be easier to read as /is declared as acknowledged/.
>
> Section 3.1.2, Para 1
> /QUIC will do it correctly once/
> - There is an inference that TCP does not, and I would argue with that,
> because TCP measures the TCP loss recovery, that is often a larger
> interval than it could have been had TCP been designed differently, but
> this document is not a thesis on TCP. I would like to suggest / QUIC
> will appropriately reduce once/ as a more neutral text.
>
> Section 3.1.6, Para 1
> /allowing a peer to maintain a more accurate/ is I think an unnecessary
> judgment on TCP again, it would be fairer to say/allowing a peer to
> maintain an accurate/
>
> The term /host delay/ appears several times, but there is no discussion
> of hosts, only endpoints. The term host delay seems odd, can we call it
> endpoint delay or perhaps even =E2=80=9CACK delay=E2=80=9D which I think =
is closer to
> the field used for this later in the spec?
>
> Section 4.1, final sentence
> /Ensuring that RTT estimates retain sufficient history is an open
> research question/
> - This is fine for an IRTF experiment, but really rests very
> uncomfortably in a standards track specification. I suggest this alone
> is not sufficient. An alternate could be to set some bound here that at
> least mitigates this - which could otherwise result in odd pathologies.
>
> Somewhere there is this (it's in several places):
> /smoothed RTT =3D latest RTT/
> - This needs to cite an RFC.
> - I'm not a huge fan of just assigning a RTT (without taking account of
> the variance) as a starting timeout. We've in the past been caught so
> many times with things being slightly or vastly different when the next
> flow starts and simply assigning the value seems like it could be the
> wrong thing to do.
>
> Section 4 pseudo code uses both Ack_Delay and ack_delay, I don=E2=80=99t
> understand the difference.
>
> Section 5
> This uses /ack/ and /ACK/
> - is there a difference?
>
> Section 5.1.
> /was sent long enough in the past/
> - This isn=E2=80=99t clear, please improve the text here to explain what =
is
> intended.
>
> /sent later was delivered, while =E2=80=A6. /
> - Text should be improved. I suggest /while/ is reworked to avoid the
> inference these occur in parallel.
>
> Section 5.1.1
> There is no minimum dupack threshold specified. Why not? I could be
> persuaded that the recommendation was for 3, and that more is possible,
> but when would less than 3 fit with current other recommendations in the
> RFC series ?
> - also mentioned in B.1
>
> Also 5.4 final sentence
> - section 6 (last para -1) reads like this is intended as one =E2=80=9Cpr=
obe=E2=80=9D
> packet, XXX what does RACK do in this cased with respect to CC?
>
> Section 5.3, final sentence:
> /may never be/
> - seems like it would avoid all possible ambiguity in whether this is
> allowed by using /could/.
>
> /Sending two packets on a PTO expiration increases resilience=E2=80=A6/
> - and arguably doubles the non-congestion-controlled load.
>
> Section 6.1
> /endpoints are permitted to experiment/
> - This is much more than intent of RFC8311. The intent was that the IETF
> can publish experimental specs for other behaviours. That=E2=80=99s not t=
he
> same, and I think the wording needs to be modified a little to reflect
> the actual consensus of the RFC.
>
> Section 6.2
> /anytime/any time/
>
> Section 6.9
> - the new text on pacing seems to be heading in the correct direction,
> but I don=E2=80=99t really understand how the congestion window will be m=
anaged
> if pacing is used and the connection becomes application-limited. The
> basic TCP spec would respond aggressively reducing the window; cwv would
> loosen this; what does QUIC say when pacing *is* used.
>
> Section 7.3
> /as having being marked/ should I think be /as having being CE-marked or
> lost/
> - add loss.
>
> section A.1 para 2.
> - I suggest text is added that mentions the actual reordering could be
> larger and how QUIC handles this.
>
> Section A4 - could the initialisation be clearer? - e.g. showing initial
> values for RTT etc.
>
>

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

<div dir=3D"ltr">Thanks for the review Gorry.=C2=A0 I&#39;ll try to fix the=
 editorial issues in a PR tonight and then file issues for the non-editoria=
l comments or comments I&#39;m not sure how to resolve.</div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Nov 14, 2019=
 at 6:19 AM G Fairhurst &lt;<a href=3D"mailto:gorry@erg.abdn.ac.uk">gorry@e=
rg.abdn.ac.uk</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddi=
ng-left:1ex">QUIC Recovery<br>
<br>
I have comments on QUIC Recovery -24. These sets of come join two parts, <b=
r>
this is the first. I hope most of the comments below are easy to resolve:<b=
r>
<br>
Section 3, Para 1 last sentence. This sentence is true from the sender <br>
perspective, but the monotonic increase is not necessarily true at the <br>
receiver.<br>
<br>
Section 3.1.2, Para 1<br>
/is declared is acknowledged/<br>
- maybe would be easier to read as /is declared as acknowledged/.<br>
<br>
Section 3.1.2, Para 1<br>
/QUIC will do it correctly once/<br>
- There is an inference that TCP does not, and I would argue with that, <br=
>
because TCP measures the TCP loss recovery, that is often a larger <br>
interval than it could have been had TCP been designed differently, but <br=
>
this document is not a thesis on TCP. I would like to suggest / QUIC <br>
will appropriately reduce once/ as a more neutral text.<br>
<br>
Section 3.1.6, Para 1<br>
/allowing a peer to maintain a more accurate/ is I think an unnecessary <br=
>
judgment on TCP again, it would be fairer to say/allowing a peer to <br>
maintain an accurate/<br>
<br>
The term /host delay/ appears several times, but there is no discussion <br=
>
of hosts, only endpoints. The term host delay seems odd, can we call it <br=
>
endpoint delay or perhaps even =E2=80=9CACK delay=E2=80=9D which I think is=
 closer to <br>
the field used for this later in the spec?<br>
<br>
Section 4.1, final sentence<br>
/Ensuring that RTT estimates retain sufficient history is an open <br>
research question/<br>
- This is fine for an IRTF experiment, but really rests very <br>
uncomfortably in a standards track specification. I suggest this alone <br>
is not sufficient. An alternate could be to set some bound here that at <br=
>
least mitigates this - which could otherwise result in odd pathologies.<br>
<br>
Somewhere there is this (it&#39;s in several places):<br>
/smoothed RTT =3D latest RTT/<br>
- This needs to cite an RFC.<br>
- I&#39;m not a huge fan of just assigning a RTT (without taking account of=
 <br>
the variance) as a starting timeout. We&#39;ve in the past been caught so <=
br>
many times with things being slightly or vastly different when the next <br=
>
flow starts and simply assigning the value seems like it could be the <br>
wrong thing to do.<br>
<br>
Section 4 pseudo code uses both Ack_Delay and ack_delay, I don=E2=80=99t <b=
r>
understand the difference.<br>
<br>
Section 5<br>
This uses /ack/ and /ACK/<br>
- is there a difference?<br>
<br>
Section 5.1.<br>
/was sent long enough in the past/<br>
- This isn=E2=80=99t clear, please improve the text here to explain what is=
 <br>
intended.<br>
<br>
/sent later was delivered, while =E2=80=A6. /<br>
- Text should be improved. I suggest /while/ is reworked to avoid the <br>
inference these occur in parallel.<br>
<br>
Section 5.1.1<br>
There is no minimum dupack threshold specified. Why not? I could be <br>
persuaded that the recommendation was for 3, and that more is possible, <br=
>
but when would less than 3 fit with current other recommendations in the <b=
r>
RFC series ?<br>
- also mentioned in B.1<br>
<br>
Also 5.4 final sentence<br>
- section 6 (last para -1) reads like this is intended as one =E2=80=9Cprob=
e=E2=80=9D <br>
packet, XXX what does RACK do in this cased with respect to CC?<br>
<br>
Section 5.3, final sentence:<br>
/may never be/<br>
- seems like it would avoid all possible ambiguity in whether this is <br>
allowed by using /could/.<br>
<br>
/Sending two packets on a PTO expiration increases resilience=E2=80=A6/<br>
- and arguably doubles the non-congestion-controlled load.<br>
<br>
Section 6.1<br>
/endpoints are permitted to experiment/<br>
- This is much more than intent of RFC8311. The intent was that the IETF <b=
r>
can publish experimental specs for other behaviours. That=E2=80=99s not the=
 <br>
same, and I think the wording needs to be modified a little to reflect <br>
the actual consensus of the RFC.<br>
<br>
Section 6.2<br>
/anytime/any time/<br>
<br>
Section 6.9<br>
- the new text on pacing seems to be heading in the correct direction, <br>
but I don=E2=80=99t really understand how the congestion window will be man=
aged <br>
if pacing is used and the connection becomes application-limited. The <br>
basic TCP spec would respond aggressively reducing the window; cwv would <b=
r>
loosen this; what does QUIC say when pacing *is* used.<br>
<br>
Section 7.3<br>
/as having being marked/ should I think be /as having being CE-marked or <b=
r>
lost/<br>
- add loss.<br>
<br>
section A.1 para 2.<br>
- I suggest text is added that mentions the actual reordering could be <br>
larger and how QUIC handles this.<br>
<br>
Section A4 - could the initialisation be clearer? - e.g. showing initial <b=
r>
values for RTT etc.<br>
<br>
</blockquote></div>

--000000000000a3306a0597502870--


From nobody Fri Nov 15 00:58:55 2019
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 53EC5120144 for <quic@ietfa.amsl.com>; Fri, 15 Nov 2019 00:58:53 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.896
X-Spam-Level: 
X-Spam-Status: No, score=-1.896 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_HELO_NONE=0.001, SPF_NONE=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=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 jYjalZcPKPq5 for <quic@ietfa.amsl.com>; Fri, 15 Nov 2019 00:58:51 -0800 (PST)
Received: from mail-lj1-x231.google.com (mail-lj1-x231.google.com [IPv6:2a00:1450:4864:20::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 EB634120143 for <quic@ietf.org>; Fri, 15 Nov 2019 00:58:50 -0800 (PST)
Received: by mail-lj1-x231.google.com with SMTP id n5so9830475ljc.9 for <quic@ietf.org>; Fri, 15 Nov 2019 00:58:50 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=rtfm-com.20150623.gappssmtp.com; s=20150623; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=UFdb6p6LB45+L7UacoNCQBq2u0gml6d/aOfhUNMGubM=; b=aIiz4EBKWZZMEbB5pr9IynlgmqUSkRUBvnmJ5YhOtptZaBsWrxDdWxgAmZgPiT56I5 sGa2B8j9sOkND7GDHRx7uip9Z/nFtwnJ9JskueTOiUig8q3Ly6ZN0+B1oHht7Ci0A29H oMsn+p/kcCiKElyJ/IEO/g2AJN0ZT18Y0riZHvAHTRXalwilLChJciiprg723xIXsxS1 yvCOsETQ4qF5OndJ/DWDnOcEYVRN+45+cwoPxfuvXr+3FXZRtcWt4f5QKfoTvAYSzE/f iwYffyPWstcVi5zshhgN+0c+7KxtEOlEbeUKZDqhS5YISzkihH78rmW2XhUlAH9x50he CUNw==
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=UFdb6p6LB45+L7UacoNCQBq2u0gml6d/aOfhUNMGubM=; b=H68LNWvD5EUuPCrI2NX8tFCA5mtubijXWbP4KDVqKdQpMVD24WM/vU4pCY/m0+wt8g +kpGa4AJ1EFWaWaOSTpCxhHXsn4Wcx/Hz6unwTjwvgXgSWScON03BnUNr9QvpGO/QUYE /b3Sty9WP071QSyGdIh9CDGT2jMFTNUFFAblN8uO8hsM6/npwApt1mpviaKEPG0E2BmZ Vv7Pyz7gN70DQaBFTHbczpeayqNaovQ+c9uc2MEC2gvHjANLH9HZ3qFCsGClIuOA6mt2 NGSfQlc+WP091U7ZTENFUSx4+fJeXTV3tIcCd7PErjSQC0U1zNxiD9EZ7yaZC7m3hdCg jnZw==
X-Gm-Message-State: APjAAAWS89v1l5YRN9wn6i6hQxkRwuPydUc2zh78QTVyXBJzWyEPhh4i 8dO7tWhR4eoXDHQIL5yrcL3LaUQMD4RoZNUzAjLbKw==
X-Google-Smtp-Source: APXvYqwMi/oYNiirnbJzQbbIpTAC5Sh+9fFV9PtYi2EgUNoHo6Era/6efGauyzN2VquHdVTU75h3FDjgeWHXI4pJvv0=
X-Received: by 2002:a2e:982:: with SMTP id 124mr10564483ljj.48.1573808328519;  Fri, 15 Nov 2019 00:58:48 -0800 (PST)
MIME-Version: 1.0
References: <67289EB8-3A37-4231-A3F9-FB46509152A0@mnot.net>
In-Reply-To: <67289EB8-3A37-4231-A3F9-FB46509152A0@mnot.net>
From: Eric Rescorla <ekr@rtfm.com>
Date: Fri, 15 Nov 2019 00:58:12 -0800
Message-ID: <CABcZeBNP7KjMp-usoa6P+KEBg-wz7uOhMjQZxjOEQi2V65ZJ6A@mail.gmail.com>
Subject: Re: Consensus Calls for Transport/TLS issues, pre-Singapore
To: Mark Nottingham <mnot@mnot.net>
Cc: IETF QUIC WG <quic@ietf.org>, Lars Eggert <lars@eggert.org>
Content-Type: multipart/alternative; boundary="0000000000005dcc2805975ecebf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/dapz-2PU5Tk0BAnuRbYWOK5NnQ4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 15 Nov 2019 08:58:53 -0000

--0000000000005dcc2805975ecebf
Content-Type: text/plain; charset="UTF-8"

I think some changes are in order in 3155 and 3014. Comments made in the PR

On Wed, Nov 13, 2019 at 5:26 PM Mark Nottingham <mnot@mnot.net> wrote:

> The following issues have proposals for resolution, and discussion so far
> seems to support consensus to accept them. If you object, please do so on
> the issue or in response to this message (changing the Subject
> appropriately!). Absent any pushback, we'll direct the editors to
> incorporate them late next week. Note that by default we won't discuss
> these issues in Singapore, unless something comes up.
>
> See <https://github.com/quicwg/base-drafts/projects/5> for the current
> state of issues in the Late Stage process, itself defined at <
> https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md>.
>
> * #3127: NEW_TOKEN and Retry tokens must be distinguishable
>   Proposal: https://github.com/quicwg/base-drafts/pull/3128
>
> * #3158: Application close should be disallowed in Initial or Handshake
>   Proposal: https://github.com/quicwg/base-drafts/pull/3164
>
> * #3155: The method of identifying "the same server"
>   Proposal: https://github.com/quicwg/base-drafts/pull/3156
>
> * #2475: Invalid CONNECTION_CLOSE frames
>   Proposal: https://github.com/quicwg/base-drafts/pull/3231
>
> * #3168: Allow servers to close connections immediately when the token is
> corrupted
>   Proposal: https://github.com/quicwg/base-drafts/pull/3107
>
> * #3194: reordered NEW_CONNECTION_ID frames with retired sequence numbers
> shouldn't be used
>   Proposal: https://github.com/quicwg/base-drafts/pull/3202
>
> * #3014: Handling of corrupt Retry packets
>   Proposal: https://github.com/quicwg/base-drafts/pull/3120
>
> * #3095: Backoff of CONNECTION_CLOSE needs to be a MUST
>   Proposal: https://github.com/quicwg/base-drafts/pull/3157
>
>
> --
> Mark Nottingham   https://www.mnot.net/
>
>

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

<div dir=3D"ltr"><div>I think some changes are in order in 3155 and 3014. C=
omments made in the PR<br></div><br><div class=3D"gmail_quote"><div dir=3D"=
ltr" class=3D"gmail_attr">On Wed, Nov 13, 2019 at 5:26 PM Mark Nottingham &=
lt;<a href=3D"mailto:mnot@mnot.net">mnot@mnot.net</a>&gt; wrote:<br></div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex">The following issues have =
proposals for resolution, and discussion so far seems to support consensus =
to accept them. If you object, please do so on the issue or in response to =
this message (changing the Subject appropriately!). Absent any pushback, we=
&#39;ll direct the editors to incorporate them late next week. Note that by=
 default we won&#39;t discuss these issues in Singapore, unless something c=
omes up.<br>
<br>
See &lt;<a href=3D"https://github.com/quicwg/base-drafts/projects/5" rel=3D=
"noreferrer" target=3D"_blank">https://github.com/quicwg/base-drafts/projec=
ts/5</a>&gt; for the current state of issues in the Late Stage process, its=
elf defined at &lt;<a href=3D"https://github.com/quicwg/base-drafts/blob/ma=
ster/CONTRIBUTING.md" rel=3D"noreferrer" target=3D"_blank">https://github.c=
om/quicwg/base-drafts/blob/master/CONTRIBUTING.md</a>&gt;.<br>
<br>
* #3127: NEW_TOKEN and Retry tokens must be distinguishable<br>
=C2=A0 Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3128=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/3128</a><br>
<br>
* #3158: Application close should be disallowed in Initial or Handshake<br>
=C2=A0 Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3164=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/3164</a><br>
<br>
* #3155: The method of identifying &quot;the same server&quot;<br>
=C2=A0 Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3156=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/3156</a><br>
<br>
* #2475: Invalid CONNECTION_CLOSE frames<br>
=C2=A0 Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3231=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/3231</a><br>
<br>
* #3168: Allow servers to close connections immediately when the token is c=
orrupted<br>
=C2=A0 Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3107=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/3107</a><br>
<br>
* #3194: reordered NEW_CONNECTION_ID frames with retired sequence numbers s=
houldn&#39;t be used<br>
=C2=A0 Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3202=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/3202</a><br>
<br>
* #3014: Handling of corrupt Retry packets<br>
=C2=A0 Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3120=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/3120</a><br>
<br>
* #3095: Backoff of CONNECTION_CLOSE needs to be a MUST<br>
=C2=A0 Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3157=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/3157</a><br>
<br>
<br>
--<br>
Mark Nottingham=C2=A0 =C2=A0<a href=3D"https://www.mnot.net/" rel=3D"norefe=
rrer" target=3D"_blank">https://www.mnot.net/</a><br>
<br>
</blockquote></div></div>

--0000000000005dcc2805975ecebf--


From nobody Sat Nov 16 03:05:48 2019
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 CD3D91200CD for <quic@ietfa.amsl.com>; Sat, 16 Nov 2019 03:05:46 -0800 (PST)
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, DKIMWL_WL_MED=-0.001, 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_HELO_NONE=0.001, SPF_PASS=-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 PvFFuWgaiBnF for <quic@ietfa.amsl.com>; Sat, 16 Nov 2019 03:05:43 -0800 (PST)
Received: from mail-ua1-x92c.google.com (mail-ua1-x92c.google.com [IPv6:2607:f8b0:4864:20::92c]) (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 7129C120019 for <quic@ietf.org>; Sat, 16 Nov 2019 03:05:43 -0800 (PST)
Received: by mail-ua1-x92c.google.com with SMTP id z9so3812795uan.3 for <quic@ietf.org>; Sat, 16 Nov 2019 03:05:43 -0800 (PST)
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=06sl8StJQZ7csImMXJqnA61Mxa75nKiqqFX2+8xjOlA=; b=NjdfcdOTTshvDnmJQ9NZmF0Ymis5pWejQwZbeP4StbVfuTvSiDcIbLc/bghIufNQ5b Y7DT3sbxZ7deSmLHISO1fGrvV73SfWYNpg/74gilkT4I7J2swnvXFDOxSC23UungXJoa t2y9SgttxzVLE5WvPVYY3eftCQIR2KQVBMylWak6H1xVF46msvrggUnQtu2/9Slu/030 Yj8nkjwcz5b8l1OB28aQpsG0pLV+bXjlCbZeA6OfAyCdy4kRlWoZoQUEzVXX2tQitz28 JlH977YAko49waB2k2fLtsneAJCUyXdXri4N07y/7/qdwezEEGYNJr1nv2vsed7+/YF+ Ix4g==
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=06sl8StJQZ7csImMXJqnA61Mxa75nKiqqFX2+8xjOlA=; b=P+tfjgHqySNdY11djGxPrWJ6qsBwkHKYxgF4ec20PefsRNw8qffipKcpvlAHRRzKtQ yLoZGXRn/rgpuwtsg3v7LNPFhAN2p6mX7S0Bwa8DUzD2VMZGdYCa92PR/5JFepUEwCA8 xZRY4pmeYcVuxlugJgK+wD8r294UQSf9ByzwsmTWrcuaoO6ZNCc5RLBJSwpW+Qg5vWvN KquzLrjYQsg6K56p1/bB9ksXYlQjfSjKh5B8+u29Pg5QTUZZX6EznKjTF/JCa8ae4jJh w1q6Zd9ExPnE/BKv8aICJlQm2iJgkavj+3PY9tn8cYAkKrk3+9NRKCixSX9/yAY3WYpY g8+w==
X-Gm-Message-State: APjAAAXWDReTkJFiB9mGmpk0KffxJagpI1JzKyE5qlas8EadC3d4qmjr dB4VCtKbGh0tS+cyKHINoniE/rypRI6RfzPB9u4xwocUGXbHgxsX
X-Google-Smtp-Source: APXvYqz2flhVEF5QMGqWQL5x/Bw/u8Vla2rh8NIbjfb4+aHQpXaIOJOeijKgZqQwZQK230HujnJJZ9yGDgAL2h0+CjY=
X-Received: by 2002:a9f:27a4:: with SMTP id b33mr11982678uab.24.1573902341822;  Sat, 16 Nov 2019 03:05:41 -0800 (PST)
MIME-Version: 1.0
References: <5DCD3819.5050300@erg.abdn.ac.uk>
In-Reply-To: <5DCD3819.5050300@erg.abdn.ac.uk>
From: Ian Swett <ianswett@google.com>
Date: Sat, 16 Nov 2019 06:05:29 -0500
Message-ID: <CAKcm_gNX8oMa=0q-RmCQXfwESksS+VH7ZEZhFB23uNM4LCHOLw@mail.gmail.com>
Subject: Re: comments on QUIC Recovery -24.
To: G Fairhurst <gorry@erg.abdn.ac.uk>
Cc: "quic@ietf.org" <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ff5f75059774b1d4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2TecSR1s4f9Syp11P9SMj_UlHV0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 16 Nov 2019 11:05:47 -0000

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

Thanks for the review, comments below and fixes in PR #3237
<https://github.com/quicwg/base-drafts/pull/3237>

On Thu, Nov 14, 2019 at 6:19 AM G Fairhurst <gorry@erg.abdn.ac.uk> wrote:

> QUIC Recovery
>
> I have comments on QUIC Recovery -24. These sets of come join two parts,
> this is the first. I hope most of the comments below are easy to resolve:
>
> Section 3, Para 1 last sentence. This sentence is true from the sender
> perspective, but the monotonic increase is not necessarily true at the
> receiver.
>

Fixed.

>
> Section 3.1.2, Para 1
> /is declared is acknowledged/
> - maybe would be easier to read as /is declared as acknowledged/.
>
> These were 3.1.3, not 3.1.3 FYI.  This has already been improved to
"QUIC starts a loss epoch when a packet is lost and ends one when any packe=
t
sent after the epoch starts is acknowledged." in the editor's copy.


> Section 3.1.2, Para 1
> /QUIC will do it correctly once/
> - There is an inference that TCP does not, and I would argue with that,
> because TCP measures the TCP loss recovery, that is often a larger
> interval than it could have been had TCP been designed differently, but
> this document is not a thesis on TCP. I would like to suggest / QUIC
> will appropriately reduce once/ as a more neutral text.
>
>
 Removed "correctly"

Section 3.1.6, Para 1
> /allowing a peer to maintain a more accurate/ is I think an unnecessary
> judgment on TCP again, it would be fairer to say/allowing a peer to
> maintain an accurate/
>

I disagree.  This is a new mechanism(explicit ack delay in the ACK frame)
to improve the accuracy of RTT which TCP does not have.  If it's not more
accurate, QUIC is wasting bytes sending it.


> The term /host delay/ appears several times, but there is no discussion
> of hosts, only endpoints. The term host delay seems odd, can we call it
> endpoint delay or perhaps even =E2=80=9CACK delay=E2=80=9D which I think =
is closer to
> the field used for this later in the spec?
>

Good point.  It seems like ACK delay is a reasonable substitute, but you
can verify in my PR.


>
> Section 4.1, final sentence
> /Ensuring that RTT estimates retain sufficient history is an open
> research question/
> - This is fine for an IRTF experiment, but really rests very
> uncomfortably in a standards track specification. I suggest this alone
> is not sufficient. An alternate could be to set some bound here that at
> least mitigates this - which could otherwise result in odd pathologies.
>

I'm not sure how to address this, but I also don't have a problem with the
existing text.  Do you have a specific suggestion?

>
> Somewhere there is this (it's in several places):
> /smoothed RTT =3D latest RTT/
> - This needs to cite an RFC.
>

RFC6298 is cited twice in section 4 "Estimating the Round-Trip Time",
particularly in regards to smoothed RTT.  Is there another RFC you have in
mind?

- I'm not a huge fan of just assigning a RTT (without taking account of
> the variance) as a starting timeout. We've in the past been caught so
> many times with things being slightly or vastly different when the next
> flow starts and simply assigning the value seems like it could be the
> wrong thing to do.
>

The timeout is twice the initial RTT if there are no RTT samples or the
PTO(SRTT+4*RTTVAR) if there is an RTT sample.  Which of those cases
concerns you?
I believe Issue #2789 <https://github.com/quicwg/base-drafts/issues/2789>
is open for this?


> Section 4 pseudo code uses both Ack_Delay and ack_delay, I don=E2=80=99t
> understand the difference.
>

I can't find a spot in the psuedocode where Ack_Delay is used, but I do see
the use of "Ack Delay" in some text and ack_delay in others.  Are you
suggesting changes there?

>
> Section 5
> This uses /ack/ and /ACK/
> - is there a difference?
>

ACK frame is used in some cases and acknowledgement should be used in
others.  I tried to fix the issues I found in the PR.

>
> Section 5.1.
> /was sent long enough in the past/
> - This isn=E2=80=99t clear, please improve the text here to explain what =
is
> intended.
>
> Section 5.1.2 is referenced in this section and explains this in detail.
Do you have a suggested reword for this sentence?


> /sent later was delivered, while =E2=80=A6. /
> - Text should be improved. I suggest /while/ is reworked to avoid the
> inference these occur in parallel.
>

'while' changed to 'and'.

>
> Section 5.1.1
> There is no minimum dupack threshold specified. Why not? I could be
> persuaded that the recommendation was for 3, and that more is possible,
> but when would less than 3 fit with current other recommendations in the
> RFC series ?
> - also mentioned in B.1
>

Is there an RFC I can cite that specifies a minimum?  5681 specifies 3, but
I can't see any discussion of minimum.

>
> Also 5.4 final sentence
> - section 6 (last para -1) reads like this is intended as one =E2=80=9Cpr=
obe=E2=80=9D
> packet, XXX what does RACK do in this cased with respect to CC?
>

Maybe you can quote the sentence and clarify your concerns?  I'm not sure
of the question here.

>
> Section 5.3, final sentence:
> /may never be/
> - seems like it would avoid all possible ambiguity in whether this is
> allowed by using /could/.
>

It's certainly allowed.  Are you suggesting 'could never be'?


>
> /Sending two packets on a PTO expiration increases resilience=E2=80=A6/
> - and arguably doubles the non-congestion-controlled load.


> Section 6.1
> /endpoints are permitted to experiment/
> - This is much more than intent of RFC8311. The intent was that the IETF
> can publish experimental specs for other behaviours. That=E2=80=99s not t=
he
> same, and I think the wording needs to be modified a little to reflect
> the actual consensus of the RFC.
>

Do you have suggested text?

>
> Section 6.2
> /anytime/any time/
>
> Good call.


> Section 6.9
> - the new text on pacing seems to be heading in the correct direction,
> but I don=E2=80=99t really understand how the congestion window will be m=
anaged
> if pacing is used and the connection becomes application-limited. The
> basic TCP spec would respond aggressively reducing the window; cwv would
> loosen this; what does QUIC say when pacing *is* used.
>

I believe this is the relevant text:
 A sender MAY implement alternative mechanisms to update its
 congestion window after periods of under-utilization, such as those
 proposed for TCP in [RFC7661].

ie: You can reduce it, but you don't have to.


> Section 7.3
> /as having being marked/ should I think be /as having being CE-marked or
> lost/
> - add loss.
>
> I believe "when the packet is acknowledged" takes care of this case, sinc=
e
if a packet is acknowledged it is not lost.


> section A.1 para 2.
> - I suggest text is added that mentions the actual reordering could be
> larger and how QUIC handles this.
>

Larger than what?  1RTT?


> Section A4 - could the initialisation be clearer? - e.g. showing initial
> values for RTT etc.
>

The initial RTT never changes during a connection, since it's only used
prior to measuring the RTT, so the pseudocode uses kIntialRtt and
smoothed_rtt is initialized to 0 to indicate its unknown.

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

<div dir=3D"ltr"><div>Thanks for the review, comments below and fixes in PR=
 <a href=3D"https://github.com/quicwg/base-drafts/pull/3237">#3237</a></div=
><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Th=
u, Nov 14, 2019 at 6:19 AM G Fairhurst &lt;<a href=3D"mailto:gorry@erg.abdn=
.ac.uk">gorry@erg.abdn.ac.uk</a>&gt; wrote:<br></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">QUIC Recovery<br>
<br>
I have comments on QUIC Recovery -24. These sets of come join two parts, <b=
r>
this is the first. I hope most of the comments below are easy to resolve:<b=
r>
<br>
Section 3, Para 1 last sentence. This sentence is true from the sender <br>
perspective, but the monotonic increase is not necessarily true at the <br>
receiver.<br></blockquote><div><br></div><div>Fixed.=C2=A0</div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex">
<br>
Section 3.1.2, Para 1<br>
/is declared is acknowledged/<br>
- maybe would be easier to read as /is declared as acknowledged/.<br>
<br></blockquote><div>These were 3.1.3, not 3.1.3 FYI.=C2=A0 This has alrea=
dy been improved to=C2=A0</div><div>&quot;QUIC starts a loss epoch when a p=
acket is lost and ends one when any packet</div>sent after the epoch starts=
 is acknowledged.&quot; in the editor&#39;s copy.<div>=C2=A0</div><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">
Section 3.1.2, Para 1<br>
/QUIC will do it correctly once/<br>
- There is an inference that TCP does not, and I would argue with that, <br=
>
because TCP measures the TCP loss recovery, that is often a larger <br>
interval than it could have been had TCP been designed differently, but <br=
>
this document is not a thesis on TCP. I would like to suggest / QUIC <br>
will appropriately reduce once/ as a more neutral text.<br>
<br></blockquote><div><br></div><div>=C2=A0Removed &quot;correctly&quot;</d=
iv><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
Section 3.1.6, Para 1<br>
/allowing a peer to maintain a more accurate/ is I think an unnecessary <br=
>
judgment on TCP again, it would be fairer to say/allowing a peer to <br>
maintain an accurate/<br></blockquote><div><br></div><div>I disagree.=C2=A0=
 This is a new mechanism(explicit ack delay in the ACK frame) to improve th=
e accuracy of RTT which TCP does not have.=C2=A0 If it&#39;s not more accur=
ate, QUIC is wasting bytes sending it.</div><div><br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex">
<br>
The term /host delay/ appears several times, but there is no discussion <br=
>
of hosts, only endpoints. The term host delay seems odd, can we call it <br=
>
endpoint delay or perhaps even =E2=80=9CACK delay=E2=80=9D which I think is=
 closer to <br>
the field used for this later in the spec?<br></blockquote><div><br></div><=
div>Good point.=C2=A0 It seems like ACK delay is a reasonable substitute, b=
ut you can verify in my PR.</div><div>=C2=A0</div><blockquote class=3D"gmai=
l_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,20=
4,204);padding-left:1ex">
<br>
Section 4.1, final sentence<br>
/Ensuring that RTT estimates retain sufficient history is an open <br>
research question/<br>
- This is fine for an IRTF experiment, but really rests very <br>
uncomfortably in a standards track specification. I suggest this alone <br>
is not sufficient. An alternate could be to set some bound here that at <br=
>
least mitigates this - which could otherwise result in odd pathologies.<br>=
</blockquote><div><br></div><div>I&#39;m not sure how to address this, but =
I also don&#39;t have a problem with the existing text.=C2=A0 Do you have a=
 specific suggestion?</div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
">
<br>
Somewhere there is this (it&#39;s in several places):<br>
/smoothed RTT =3D latest RTT/<br>
- This needs to cite an RFC.<br></blockquote><div><br></div><div>RFC6298 is=
 cited twice in section 4 &quot;Estimating the Round-Trip Time&quot;, parti=
cularly in regards to smoothed RTT.=C2=A0 Is there another RFC you have in =
mind?</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"=
>
- I&#39;m not a huge fan of just assigning a RTT (without taking account of=
 <br>
the variance) as a starting timeout. We&#39;ve in the past been caught so <=
br>
many times with things being slightly or vastly different when the next <br=
>
flow starts and simply assigning the value seems like it could be the <br>
wrong thing to do.<br></blockquote><div><br></div><div>The timeout is twice=
 the initial RTT if there are no RTT samples or the PTO(SRTT+4*RTTVAR) if t=
here is an RTT sample.=C2=A0 Which of those cases concerns you?</div><div>I=
 believe Issue <a href=3D"https://github.com/quicwg/base-drafts/issues/2789=
">#2789</a> is open for this?<br></div><div><br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex">
<br>
Section 4 pseudo code uses both Ack_Delay and ack_delay, I don=E2=80=99t <b=
r>
understand the difference.<br></blockquote><div><br></div><div>I can&#39;t =
find a spot in the psuedocode where Ack_Delay is used, but I do see the use=
 of &quot;Ack Delay&quot; in some text and ack_delay in others.=C2=A0 Are y=
ou suggesting changes there?</div><blockquote class=3D"gmail_quote" style=
=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding=
-left:1ex">
<br>
Section 5<br>
This uses /ack/ and /ACK/<br>
- is there a difference?<br></blockquote><div><br></div><div>ACK frame is u=
sed in some cases and acknowledgement should be used in others.=C2=A0 I tri=
ed to fix the issues I found in the PR.</div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex">
<br>
Section 5.1.<br>
/was sent long enough in the past/<br>
- This isn=E2=80=99t clear, please improve the text here to explain what is=
 <br>
intended.<br>
<br></blockquote><div>Section 5.1.2 is referenced in this section and expla=
ins this in detail.=C2=A0 Do you have a suggested reword for this sentence?=
</div><div>=C2=A0<br></div><blockquote class=3D"gmail_quote" style=3D"margi=
n:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex=
">
/sent later was delivered, while =E2=80=A6. /<br>
- Text should be improved. I suggest /while/ is reworked to avoid the <br>
inference these occur in parallel.<br></blockquote><div><br></div><div>&#39=
;while&#39; changed to &#39;and&#39;.</div><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex">
<br>
Section 5.1.1<br>
There is no minimum dupack threshold specified. Why not? I could be <br>
persuaded that the recommendation was for 3, and that more is possible, <br=
>
but when would less than 3 fit with current other recommendations in the <b=
r>
RFC series ?<br>
- also mentioned in B.1<br></blockquote><div><br></div><div>Is there an RFC=
 I can cite that specifies a minimum?=C2=A0 5681 specifies 3, but I can&#39=
;t see any discussion of minimum.</div><blockquote class=3D"gmail_quote" st=
yle=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padd=
ing-left:1ex">
<br>
Also 5.4 final sentence<br>
- section 6 (last para -1) reads like this is intended as one =E2=80=9Cprob=
e=E2=80=9D <br>
packet, XXX what does RACK do in this cased with respect to CC?<br></blockq=
uote><div><br></div><div>Maybe you can quote the sentence and clarify your =
concerns?=C2=A0 I&#39;m not sure of the question here.=C2=A0</div><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">
<br>
Section 5.3, final sentence:<br>
/may never be/<br>
- seems like it would avoid all possible ambiguity in whether this is <br>
allowed by using /could/.<br></blockquote><div><br></div><div>It&#39;s cert=
ainly allowed.=C2=A0 Are you suggesting &#39;could never be&#39;?</div><div=
>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px =
0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
/Sending two packets on a PTO expiration increases resilience=E2=80=A6/<br>
- and arguably doubles the non-congestion-controlled load.=C2=A0</blockquot=
e><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex">
<br>
Section 6.1<br>
/endpoints are permitted to experiment/<br>
- This is much more than intent of RFC8311. The intent was that the IETF <b=
r>
can publish experimental specs for other behaviours. That=E2=80=99s not the=
 <br>
same, and I think the wording needs to be modified a little to reflect <br>
the actual consensus of the RFC.<br></blockquote><div><br></div><div>Do you=
 have suggested text?=C2=A0</div><blockquote class=3D"gmail_quote" style=3D=
"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-le=
ft:1ex">
<br>
Section 6.2<br>
/anytime/any time/<br>
<br></blockquote><div>Good call.</div><div>=C2=A0</div><blockquote class=3D=
"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(2=
04,204,204);padding-left:1ex">
Section 6.9<br>
- the new text on pacing seems to be heading in the correct direction, <br>
but I don=E2=80=99t really understand how the congestion window will be man=
aged <br>
if pacing is used and the connection becomes application-limited. The <br>
basic TCP spec would respond aggressively reducing the window; cwv would <b=
r>
loosen this; what does QUIC say when pacing *is* used.<br></blockquote><div=
><br></div><div>I believe this is the relevant text:</div><div>=C2=A0A send=
er MAY implement alternative mechanisms to update its<br>=C2=A0congestion w=
indow after periods of under-utilization, such as those</div><div>=C2=A0pro=
posed for TCP in [RFC7661].<br></div><div><br></div><div>ie: You can reduce=
 it, but you don&#39;t have to.</div><div><br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,=
204,204);padding-left:1ex">
<br>
Section 7.3<br>
/as having being marked/ should I think be /as having being CE-marked or <b=
r>
lost/<br>
- add loss.<br>
<br></blockquote><div>I believe &quot;when the packet is acknowledged&quot;=
 takes care of this case, since if a packet is acknowledged it is not lost.=
</div><div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0p=
x 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
section A.1 para 2.<br>
- I suggest text is added that mentions the actual reordering could be <br>
larger and how QUIC handles this.<br></blockquote><div><br></div><div>Large=
r than what?=C2=A0 1RTT?</div><div><br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex">
<br>
Section A4 - could the initialisation be clearer? - e.g. showing initial <b=
r>
values for RTT etc.<br></blockquote><div><br></div><div>The initial RTT nev=
er changes during a connection, since it&#39;s only used prior to measuring=
 the RTT, so the pseudocode uses kIntialRtt and smoothed_rtt is initialized=
 to 0 to indicate its unknown.</div></div></div>

--000000000000ff5f75059774b1d4--


From nobody Sat Nov 16 22:24:30 2019
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 8E1BD120088 for <quic@ietfa.amsl.com>; Sat, 16 Nov 2019 22:24:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, SPF_HELO_NONE=0.001, SPF_NONE=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 P05c2G400gBu for <quic@ietfa.amsl.com>; Sat, 16 Nov 2019 22:24:25 -0800 (PST)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id 3EEC912007C for <quic@ietf.org>; Sat, 16 Nov 2019 22:24:24 -0800 (PST)
Received: from dhcp-8f24.meeting.ietf.org (dhcp-8f24.meeting.ietf.org [31.133.143.36]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id A91AB1B002B3; Sun, 17 Nov 2019 06:24:20 +0000 (GMT)
Message-ID: <5DD0E791.6000501@erg.abdn.ac.uk>
Date: Sun, 17 Nov 2019 14:24:17 +0800
From: G Fairhurst <gorry@erg.abdn.ac.uk>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:12.0) Gecko/20120428 Thunderbird/12.0.1
MIME-Version: 1.0
To: Ian Swett <ianswett@google.com>
CC: "quic@ietf.org" <quic@ietf.org>
Subject: Re: comments on QUIC Recovery -24.
References: <5DCD3819.5050300@erg.abdn.ac.uk> <CAKcm_gNX8oMa=0q-RmCQXfwESksS+VH7ZEZhFB23uNM4LCHOLw@mail.gmail.com>
In-Reply-To: <CAKcm_gNX8oMa=0q-RmCQXfwESksS+VH7ZEZhFB23uNM4LCHOLw@mail.gmail.com>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/1KIoGmQDq0CccLEupD9YY_5vE9E>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 17 Nov 2019 06:24:28 -0000

I now believe these will be fixed in the next revision.

Gorry

(P.S. The timer initialisation issue was tracked down to one word and 
other edit, rather than a real issue - both now resolved in new text 
from Jana.)

On 16/11/2019, 19:05, Ian Swett wrote:
> Thanks for the review, comments below and fixes in PR #3237 
> <https://github.com/quicwg/base-drafts/pull/3237>
>
> On Thu, Nov 14, 2019 at 6:19 AM G Fairhurst <gorry@erg.abdn.ac.uk 
> <mailto:gorry@erg.abdn.ac.uk>> wrote:
>
>     QUIC Recovery
>
>     I have comments on QUIC Recovery -24. These sets of come join two
>     parts,
>     this is the first. I hope most of the comments below are easy to
>     resolve:
>
>     Section 3, Para 1 last sentence. This sentence is true from the
>     sender
>     perspective, but the monotonic increase is not necessarily true at
>     the
>     receiver.
>
>
> Fixed.
>
>
>     Section 3.1.2, Para 1
>     /is declared is acknowledged/
>     - maybe would be easier to read as /is declared as acknowledged/.
>
> These were 3.1.3, not 3.1.3 FYI.  This has already been improved to
> "QUIC starts a loss epoch when a packet is lost and ends one when any 
> packet
> sent after the epoch starts is acknowledged." in the editor's copy.
>
>     Section 3.1.2, Para 1
>     /QUIC will do it correctly once/
>     - There is an inference that TCP does not, and I would argue with
>     that,
>     because TCP measures the TCP loss recovery, that is often a larger
>     interval than it could have been had TCP been designed
>     differently, but
>     this document is not a thesis on TCP. I would like to suggest / QUIC
>     will appropriately reduce once/ as a more neutral text.
>
>
>  Removed "correctly"
>
>     Section 3.1.6, Para 1
>     /allowing a peer to maintain a more accurate/ is I think an
>     unnecessary
>     judgment on TCP again, it would be fairer to say/allowing a peer to
>     maintain an accurate/
>
>
> I disagree.  This is a new mechanism(explicit ack delay in the ACK 
> frame) to improve the accuracy of RTT which TCP does not have.  If 
> it's not more accurate, QUIC is wasting bytes sending it.
>
>
>     The term /host delay/ appears several times, but there is no
>     discussion
>     of hosts, only endpoints. The term host delay seems odd, can we
>     call it
>     endpoint delay or perhaps even â€œACK delayâ€� which I think is closer to
>     the field used for this later in the spec?
>
>
> Good point.  It seems like ACK delay is a reasonable substitute, but 
> you can verify in my PR.
>
>
>     Section 4.1, final sentence
>     /Ensuring that RTT estimates retain sufficient history is an open
>     research question/
>     - This is fine for an IRTF experiment, but really rests very
>     uncomfortably in a standards track specification. I suggest this
>     alone
>     is not sufficient. An alternate could be to set some bound here
>     that at
>     least mitigates this - which could otherwise result in odd
>     pathologies.
>
>
> I'm not sure how to address this, but I also don't have a problem with 
> the existing text.  Do you have a specific suggestion?
>
>
>     Somewhere there is this (it's in several places):
>     /smoothed RTT = latest RTT/
>     - This needs to cite an RFC.
>
>
> RFC6298 is cited twice in section 4 "Estimating the Round-Trip Time", 
> particularly in regards to smoothed RTT.  Is there another RFC you 
> have in mind?
>
>     - I'm not a huge fan of just assigning a RTT (without taking
>     account of
>     the variance) as a starting timeout. We've in the past been caught so
>     many times with things being slightly or vastly different when the
>     next
>     flow starts and simply assigning the value seems like it could be the
>     wrong thing to do.
>
>
> The timeout is twice the initial RTT if there are no RTT samples or 
> the PTO(SRTT+4*RTTVAR) if there is an RTT sample.  Which of those 
> cases concerns you?
> I believe Issue #2789 
> <https://github.com/quicwg/base-drafts/issues/2789> is open for this?
>
>
>     Section 4 pseudo code uses both Ack_Delay and ack_delay, I donâ€™t
>     understand the difference.
>
>
> I can't find a spot in the psuedocode where Ack_Delay is used, but I 
> do see the use of "Ack Delay" in some text and ack_delay in others.  
> Are you suggesting changes there?
>
>
>     Section 5
>     This uses /ack/ and /ACK/
>     - is there a difference?
>
>
> ACK frame is used in some cases and acknowledgement should be used in 
> others.  I tried to fix the issues I found in the PR.
>
>
>     Section 5.1.
>     /was sent long enough in the past/
>     - This isnâ€™t clear, please improve the text here to explain what is
>     intended.
>
> Section 5.1.2 is referenced in this section and explains this in 
> detail.  Do you have a suggested reword for this sentence?
>
>     /sent later was delivered, while â€¦. /
>     - Text should be improved. I suggest /while/ is reworked to avoid the
>     inference these occur in parallel.
>
>
> 'while' changed to 'and'.
>
>
>     Section 5.1.1
>     There is no minimum dupack threshold specified. Why not? I could be
>     persuaded that the recommendation was for 3, and that more is
>     possible,
>     but when would less than 3 fit with current other recommendations
>     in the
>     RFC series ?
>     - also mentioned in B.1
>
>
> Is there an RFC I can cite that specifies a minimum?  5681 specifies 
> 3, but I can't see any discussion of minimum.
>
>
>     Also 5.4 final sentence
>     - section 6 (last para -1) reads like this is intended as one â€œprobeâ€�
>     packet, XXX what does RACK do in this cased with respect to CC?
>
>
> Maybe you can quote the sentence and clarify your concerns?  I'm not 
> sure of the question here.
>
>
>     Section 5.3, final sentence:
>     /may never be/
>     - seems like it would avoid all possible ambiguity in whether this is
>     allowed by using /could/.
>
>
> It's certainly allowed.  Are you suggesting 'could never be'?
>
>
>     /Sending two packets on a PTO expiration increases resilienceâ€¦/
>     - and arguably doubles the non-congestion-controlled load. 
>
>
>     Section 6.1
>     /endpoints are permitted to experiment/
>     - This is much more than intent of RFC8311. The intent was that
>     the IETF
>     can publish experimental specs for other behaviours. Thatâ€™s not the
>     same, and I think the wording needs to be modified a little to
>     reflect
>     the actual consensus of the RFC.
>
>
> Do you have suggested text?
>
>
>     Section 6.2
>     /anytime/any time/
>
> Good call.
>
>     Section 6.9
>     - the new text on pacing seems to be heading in the correct
>     direction,
>     but I donâ€™t really understand how the congestion window will be
>     managed
>     if pacing is used and the connection becomes application-limited. The
>     basic TCP spec would respond aggressively reducing the window; cwv
>     would
>     loosen this; what does QUIC say when pacing *is* used.
>
>
> I believe this is the relevant text:
>  A sender MAY implement alternative mechanisms to update its
>  congestion window after periods of under-utilization, such as those
>  proposed for TCP in [RFC7661].
>
> ie: You can reduce it, but you don't have to.
>
>
>     Section 7.3
>     /as having being marked/ should I think be /as having being
>     CE-marked or
>     lost/
>     - add loss.
>
> I believe "when the packet is acknowledged" takes care of this case, 
> since if a packet is acknowledged it is not lost.
>
>     section A.1 para 2.
>     - I suggest text is added that mentions the actual reordering
>     could be
>     larger and how QUIC handles this.
>
>
> Larger than what?  1RTT?
>
>
>     Section A4 - could the initialisation be clearer? - e.g. showing
>     initial
>     values for RTT etc.
>
>
> The initial RTT never changes during a connection, since it's only 
> used prior to measuring the RTT, so the pseudocode uses kIntialRtt and 
> smoothed_rtt is initialized to 0 to indicate its unknown.


From nobody Sat Nov 16 23:32:07 2019
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 2937F120033 for <quic@ietfa.amsl.com>; Sat, 16 Nov 2019 23:32:06 -0800 (PST)
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=4Lpz8qcG; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=ZMxrsqBK
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 FWfjJPJUaufI for <quic@ietfa.amsl.com>; Sat, 16 Nov 2019 23:32:03 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4DB9A120098 for <quic@ietf.org>; Sat, 16 Nov 2019 23:32:03 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 6FF3E21B84 for <quic@ietf.org>; Sun, 17 Nov 2019 02:32:02 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sun, 17 Nov 2019 02:32:02 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject:message-id:date; s= fm1; bh=2UNVqylwRCPun0NXlX3fqtorOaXAmLg3HLV2TKsQL1Q=; b=4Lpz8qcG ImbkxMue4PDG16BwPDNr1E41kIn9FXuWA5CYxWtd0CUfqc3AhNeaPq28hoiJ0QpS vkKhEf2PpKti41r0YYn8pmcVj4qGabk4Vt56roVEAP+e7MMH0CK97qxiDvSRoecV MbJLqlQX48lrPs9/p+pk+PyPOSLl5xNuPfRAtlMOVpFBZoGCQU3d8mARuU0sB2Kp DlQ46bMk243bowlXqHNDVDGmKJCoSjfC7nmkLyepz+Gm9rwc9alvEqgTxeuC8ghC AC3EyrsoUYisxbGsv/+NNQtHgCJjGN/0jBD/ptgqlYO+5sjgh6AhHa88W7AxXV0g wbfBwCEtQ0eQJg==
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-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=2UNVqylwRCPun0NXlX3fqtorOaXAm Lg3HLV2TKsQL1Q=; b=ZMxrsqBKAHWxGG9x8NjVkwj4dedUWqhIxQGJzwGee4EQn GxgFMxf1Gtu6fMw+zm2uvCXFxtxF3L38f+6WZCScLiR2szhb0FbE+JNOBGMWUGPK H/TsvhlzwAv9FcAqtZ8x7zpgk8sRinMvsrObxaldkN7ulCNxj8cGCIkj74QmtyHr 0LLR39XDGEZWRDT0iXVDeu+JnFo2mP0ztHc+O/w5IvxZgeUJB4trR3yuNrlXQmF0 hDokF2FbJJuw2dwEJdW4iLZ/SNFGwpJXlhyq+b48tJ44tW/mH+2xJlthVoCApMD/ TPkQ0A62c/rH/32++gsXiHSjlh1KeAO3W9Aozs3vw==
X-ME-Sender: <xms:cffQXVbyPsYd9gE0plKTlnKNM5yjHvvSnr8BUikwtSs_1cvD0e2sbw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudegtddguddthecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurheptggghffvufesrgdttdertddtje enucfhrhhomheptfgvphhoshhithhorhihucettghtihhvihhthicuufhumhhmrghrhicu uehothcuoeguohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvghtqeenucffohhmrghinh epghhithhhuhgsrdgtohhmnecukfhppeegtddruddujedrudejhedrieehnecurfgrrhgr mhepmhgrihhlfhhrohhmpeguohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvghtnecuve hluhhsthgvrhfuihiivgepud
X-ME-Proxy: <xmx:cffQXfHHOU57lOjqjerFrzbcbJnRE-S7d0nHgv6XikoCjKFTLNtmeQ> <xmx:cffQXVfVoOrwdaeHfifMiMJUZP8K4f71D44C4iFvDw8QojlsJT4SAg> <xmx:cffQXaByfxh8XsPq_8tiOhcOW-9H5m9o4rncRBc-b_ke1BqkKt-1ow> <xmx:cvfQXTR96Onlo1f_kojMwa_cMf7Ld8pDYcgNcSP2OJsSYScKZJLo-g>
Received: from [10.1.0.4] (unknown [40.117.175.65]) by mail.messagingengine.com (Postfix) with ESMTPA id 39E7B306005C for <quic@ietf.org>; Sun, 17 Nov 2019 02:32:01 -0500 (EST)
Content-Type: multipart/alternative; boundary="===============6014700161201442472=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: quic@ietf.org
Subject: Weekly github digest ( Activity Summary)
Message-Id: <20191117073201.39E7B306005C@mailuser.nyi.internal>
Date: Sun, 17 Nov 2019 02:32:01 -0500 (EST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/jwOts-LdKq279pFcDYegr_04psg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 17 Nov 2019 07:32:06 -0000

--===============6014700161201442472==
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 (+6/-1/=F0=9F=92=AC10)
  6 issues created:
  - I am concerned the congestion control text is too permissive. (by gorry=
fair)
    https://github.com/quicwg/base-drafts/issues/3247=20
  - Make RFC 6928 normative (by janaiyengar)
    https://github.com/quicwg/base-drafts/issues/3245 [-recovery]=20
  - Can we make a normative ref to  RFC8085? (by gorryfair)
    https://github.com/quicwg/base-drafts/issues/3244=20
  - Add caution when using IW10 and fragmentation  (by janaiyengar)
    https://github.com/quicwg/base-drafts/issues/3243 [-recovery]=20
  - OnPacketAcknowledgment pseudocode is unclear (by martinduke)
    https://github.com/quicwg/base-drafts/issues/3236=20
  - Terminology QUIC-Transport-24 (by kazu-yamamoto)
    https://github.com/quicwg/base-drafts/issues/3233=20

  7 issues received 10 new comments:
  - #3247 I am concerned the congestion control text is too permissive. (1 =
by gorryfair)
    https://github.com/quicwg/base-drafts/issues/3247=20
  - #3215 Timer interval for retire the connection IDs (2 by MikeBishop, ka=
zuho)
    https://github.com/quicwg/base-drafts/issues/3215 [-transport]=20
  - #3211 Remove SHOULD for advice to pre-generate KeyUpdate (1 by mnot)
    https://github.com/quicwg/base-drafts/issues/3211 [-tls]=20
  - #3199 ChaCha20 header protection sample (3 by martinthomson, mikkelfj)
    https://github.com/quicwg/base-drafts/issues/3199 [-tls] [invalid]=20
  - #3173 TLS MUST NOT deliver server 1RTT Rx keys until getting Finished (=
1 by mnot)
    https://github.com/quicwg/base-drafts/issues/3173 [-tls]=20
  - #3155 The method of identifying "the same server" (1 by igorlord)
    https://github.com/quicwg/base-drafts/issues/3155 [-transport] [design]=
 [proposal-ready]=20
  - #3117 Recouple QUIC version and ALPN (1 by martinthomson)
    https://github.com/quicwg/base-drafts/issues/3117 [-http] [design]=20

  1 issues closed:
  - Remove SHOULD for advice to pre-generate KeyUpdate https://github.com/q=
uicwg/base-drafts/issues/3211 [-tls]=20



Pull requests
-------------
* quicwg/base-drafts (+11/-3/=F0=9F=92=AC16)
  11 pull requests submitted:
  - endpoints never requests a CID (by kazuho)
    https://github.com/quicwg/base-drafts/pull/3252=20
  - Set, not seed (by janaiyengar)
    https://github.com/quicwg/base-drafts/pull/3251=20
  - Fix incorrect time-threshold expression (by janaiyengar)
    https://github.com/quicwg/base-drafts/pull/3250=20
  - Fix congestion control permissiveness (by janaiyengar)
    https://github.com/quicwg/base-drafts/pull/3248=20
  - Make RFC6928 normative (by janaiyengar)
    https://github.com/quicwg/base-drafts/pull/3246=20
  - Reference 3168 for ECN (by ianswett)
    https://github.com/quicwg/base-drafts/pull/3241 [-recovery]=20
  - MUST NOT use a reordering theshold less than 3 (by ianswett)
    https://github.com/quicwg/base-drafts/pull/3240 [-recovery] [design]=20
  - HTTP: Tweak wording about unknown error codes (by SamB)
    https://github.com/quicwg/base-drafts/pull/3239=20
  - HTTP: server may interleave DUPLICATE_PUSH frames as well (by dtikhonov)
    https://github.com/quicwg/base-drafts/pull/3235=20
  - Limit CWND increase in slow start (by goelvidhi)
    https://github.com/quicwg/base-drafts/pull/3232=20
  - Bad CONNECTION_CLOSE isn't special (by martinthomson)
    https://github.com/quicwg/base-drafts/pull/3231 [-transport] [design]=20

  7 pull requests received 16 new comments:
  - #3248 Fix congestion control permissiveness (1 by ianswett)
    https://github.com/quicwg/base-drafts/pull/3248 [-recovery]=20
  - #3232 Limit CWND increase in slow start (1 by ianswett)
    https://github.com/quicwg/base-drafts/pull/3232=20
  - #3221 [HTTP/3] [editorial] s/do not need to/do not/ (1 by bencebeky)
    https://github.com/quicwg/base-drafts/pull/3221=20
  - #3218 [HTTP/3] [editorial] 421 and future connection reuse. (2 by MikeB=
ishop, bencebeky)
    https://github.com/quicwg/base-drafts/pull/3218=20
  - #3186 allow CRYPTO_BUFFER_EXCEEDED when overflowing a CRYPTO frame (2 b=
y ianswett, kazuho)
    https://github.com/quicwg/base-drafts/pull/3186 [-transport]=20
  - #3156 clarify the scope of a NEW_TOKEN token (3 by ekr, kazuho, mikkelf=
j)
    https://github.com/quicwg/base-drafts/pull/3156 [-transport]=20
  - #3120 Add retry integrity tag (6 by DavidSchinazi, ekr, huitema, kazuho)
    https://github.com/quicwg/base-drafts/pull/3120 [-tls] [-transport] [de=
sign]=20

  3 pull requests merged:
  - Fix incorrect time-threshold expression
    https://github.com/quicwg/base-drafts/pull/3250 [-recovery]=20
  - Clarify that initial RTT is set, not seeded into something
    https://github.com/quicwg/base-drafts/pull/3251=20
  - Reference 3168 for ECN
    https://github.com/quicwg/base-drafts/pull/3241 [-recovery]=20


Repositories tracked by this digest:
-----------------------------------
* https://github.com/quicwg/base-drafts

--===============6014700161201442472==
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 ( Activity Summary)</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 November 17, 2019</h1>

<p>Events without label "editorial"</p>

<h2>Issues</h2>

<h3>quicwg/base-drafts (+6/-1/=F0=9F=92=AC10)</h3>
  <p class=3D"new">6 issues created:</p>
  <ul>
  <li>#3247 <a href=3D"https://github.com/quicwg/base-drafts/issues/3247">I=
 am concerned the congestion control text is too permissive.</a> (by gorryf=
air) </li>
 =20
  <li>#3245 <a href=3D"https://github.com/quicwg/base-drafts/issues/3245">M=
ake RFC 6928 normative</a> (by janaiyengar) <span class=3D"label" style=3D"=
background-color: #fbca04; color: #000000">-recovery</span> </li>
 =20
  <li>#3244 <a href=3D"https://github.com/quicwg/base-drafts/issues/3244">C=
an we make a normative ref to  RFC8085?</a> (by gorryfair) </li>
 =20
  <li>#3243 <a href=3D"https://github.com/quicwg/base-drafts/issues/3243">A=
dd caution when using IW10 and fragmentation </a> (by janaiyengar) <span cl=
ass=3D"label" style=3D"background-color: #fbca04; color: #000000">-recovery=
</span> </li>
 =20
  <li>#3236 <a href=3D"https://github.com/quicwg/base-drafts/issues/3236">O=
nPacketAcknowledgment pseudocode is unclear</a> (by martinduke) </li>
 =20
  <li>#3233 <a href=3D"https://github.com/quicwg/base-drafts/issues/3233">T=
erminology QUIC-Transport-24</a> (by kazu-yamamoto) </li>
  </ul>

  <p>7 issues received 10 new comments:</p>
  <ul>
  <li>#3247 <a href=3D"https://github.com/quicwg/base-drafts/issues/3247">I=
 am concerned the congestion control text is too permissive.</a> (1 by gorr=
yfair) </li>
 =20
  <li>#3215 <a href=3D"https://github.com/quicwg/base-drafts/issues/3215">T=
imer interval for retire the connection IDs</a> (2 by MikeBishop, kazuho) <=
span class=3D"label" style=3D"background-color: #fbca04; color: #000000">-t=
ransport</span> </li>
 =20
  <li>#3211 <a href=3D"https://github.com/quicwg/base-drafts/issues/3211">R=
emove SHOULD for advice to pre-generate KeyUpdate</a> (1 by mnot) <span cla=
ss=3D"label" style=3D"background-color: #fbca04; color: #000000">-tls</span=
> </li>
 =20
  <li>#3199 <a href=3D"https://github.com/quicwg/base-drafts/issues/3199">C=
haCha20 header protection sample</a> (3 by martinthomson, mikkelfj) <span c=
lass=3D"label" style=3D"background-color: #fbca04; color: #000000">-tls</sp=
an> <span class=3D"label" style=3D"background-color: #cccccc; color: #00000=
0">invalid</span> </li>
 =20
  <li>#3173 <a href=3D"https://github.com/quicwg/base-drafts/issues/3173">T=
LS MUST NOT deliver server 1RTT Rx keys until getting Finished</a> (1 by mn=
ot) <span class=3D"label" style=3D"background-color: #fbca04; color: #00000=
0">-tls</span> </li>
 =20
  <li>#3155 <a href=3D"https://github.com/quicwg/base-drafts/issues/3155">T=
he method of identifying &quot;the same server&quot;</a> (1 by igorlord) <s=
pan class=3D"label" style=3D"background-color: #fbca04; color: #000000">-tr=
ansport</span> <span class=3D"label" style=3D"background-color: #1d76db; co=
lor: #ffffff">design</span> <span class=3D"label" style=3D"background-color=
: #c5def5; color: #000000">proposal-ready</span> </li>
 =20
  <li>#3117 <a href=3D"https://github.com/quicwg/base-drafts/issues/3117">R=
ecouple QUIC version and ALPN</a> (1 by martinthomson) <span class=3D"label=
" style=3D"background-color: #fbca04; color: #000000">-http</span> <span cl=
ass=3D"label" style=3D"background-color: #1d76db; color: #ffffff">design</s=
pan> </li>
  </ul>

  <p>1 issues closed:</p>
  <ul>
  <li>#3211 <a href=3D"https://github.com/quicwg/base-drafts/issues/3211">R=
emove SHOULD for advice to pre-generate KeyUpdate</a> <span class=3D"label"=
 style=3D"background-color: #fbca04; color: #000000">-tls</span> </li>
  </ul>



<h2>Pull requests</h2>
<h3>quicwg/base-drafts (+11/-3/=F0=9F=92=AC16)</h3>
  <p class=3D"new">11 pull requests submitted:</p>
  <ul>
  <li>#3252 <a href=3D"https://github.com/quicwg/base-drafts/pull/3252">end=
points never requests a CID</a> (by kazuho) </li>
 =20
  <li>#3251 <a href=3D"https://github.com/quicwg/base-drafts/pull/3251">Set=
, not seed</a> (by janaiyengar) </li>
 =20
  <li>#3250 <a href=3D"https://github.com/quicwg/base-drafts/pull/3250">Fix=
 incorrect time-threshold expression</a> (by janaiyengar) </li>
 =20
  <li>#3248 <a href=3D"https://github.com/quicwg/base-drafts/pull/3248">Fix=
 congestion control permissiveness</a> (by janaiyengar) </li>
 =20
  <li>#3246 <a href=3D"https://github.com/quicwg/base-drafts/pull/3246">Mak=
e RFC6928 normative</a> (by janaiyengar) </li>
 =20
  <li>#3241 <a href=3D"https://github.com/quicwg/base-drafts/pull/3241">Ref=
erence 3168 for ECN</a> (by ianswett) <span class=3D"label" style=3D"backgr=
ound-color: #fbca04; color: #">-recovery</span> </li>
 =20
  <li>#3240 <a href=3D"https://github.com/quicwg/base-drafts/pull/3240">MUS=
T NOT use a reordering theshold less than 3</a> (by ianswett) <span class=
=3D"label" style=3D"background-color: #fbca04; color: #">-recovery</span> <=
span class=3D"label" style=3D"background-color: #1d76db; color: #">design</=
span> </li>
 =20
  <li>#3239 <a href=3D"https://github.com/quicwg/base-drafts/pull/3239">HTT=
P: Tweak wording about unknown error codes</a> (by SamB) </li>
 =20
  <li>#3235 <a href=3D"https://github.com/quicwg/base-drafts/pull/3235">HTT=
P: server may interleave DUPLICATE_PUSH frames as well</a> (by dtikhonov) <=
/li>
 =20
  <li>#3232 <a href=3D"https://github.com/quicwg/base-drafts/pull/3232">Lim=
it CWND increase in slow start</a> (by goelvidhi) </li>
 =20
  <li>#3231 <a href=3D"https://github.com/quicwg/base-drafts/pull/3231">Bad=
 CONNECTION_CLOSE isn&#x27;t special</a> (by martinthomson) <span class=3D"=
label" style=3D"background-color: #fbca04; color: #">-transport</span> <spa=
n class=3D"label" style=3D"background-color: #1d76db; color: #">design</spa=
n> </li>
  </ul>

  <p>7 pull requests received 16 new comments:</p>
  <ul>
  <li>#3248 <a href=3D"https://github.com/quicwg/base-drafts/pull/3248">Fix=
 congestion control permissiveness</a> (1 by ianswett) <span class=3D"label=
" style=3D"background-color: #fbca04; color: #000000">-recovery</span> </li>
 =20
  <li>#3232 <a href=3D"https://github.com/quicwg/base-drafts/pull/3232">Lim=
it CWND increase in slow start</a> (1 by ianswett) </li>
 =20
  <li>#3221 <a href=3D"https://github.com/quicwg/base-drafts/pull/3221">[HT=
TP/3] [editorial] s/do not need to/do not/</a> (1 by bencebeky) </li>
 =20
  <li>#3218 <a href=3D"https://github.com/quicwg/base-drafts/pull/3218">[HT=
TP/3] [editorial] 421 and future connection reuse.</a> (2 by MikeBishop, be=
ncebeky) </li>
 =20
  <li>#3186 <a href=3D"https://github.com/quicwg/base-drafts/pull/3186">all=
ow CRYPTO_BUFFER_EXCEEDED when overflowing a CRYPTO frame</a> (2 by ianswet=
t, kazuho) <span class=3D"label" style=3D"background-color: #fbca04; color:=
 #000000">-transport</span> </li>
 =20
  <li>#3156 <a href=3D"https://github.com/quicwg/base-drafts/pull/3156">cla=
rify the scope of a NEW_TOKEN token</a> (3 by ekr, kazuho, mikkelfj) <span =
class=3D"label" style=3D"background-color: #fbca04; color: #000000">-transp=
ort</span> </li>
 =20
  <li>#3120 <a href=3D"https://github.com/quicwg/base-drafts/pull/3120">Add=
 retry integrity tag</a> (6 by DavidSchinazi, ekr, huitema, kazuho) <span c=
lass=3D"label" style=3D"background-color: #fbca04; color: #000000">-tls</sp=
an> <span class=3D"label" style=3D"background-color: #fbca04; color: #00000=
0">-transport</span> <span class=3D"label" style=3D"background-color: #1d76=
db; color: #ffffff">design</span> </li>
  </ul>

  <p>3 pull requests merged:</p>
  <ul>
  <li>#3250 <a href=3D"https://github.com/quicwg/base-drafts/pull/3250">Fix=
 incorrect time-threshold expression</a> <span class=3D"label" style=3D"bac=
kground-color: #fbca04; color: #">-recovery</span> </li>
 =20
  <li>#3251 <a href=3D"https://github.com/quicwg/base-drafts/pull/3251">Cla=
rify that initial RTT is set, not seeded into something</a> </li>
 =20
  <li>#3241 <a href=3D"https://github.com/quicwg/base-drafts/pull/3241">Ref=
erence 3168 for ECN</a> <span class=3D"label" style=3D"background-color: #f=
bca04; color: #">-recovery</span> </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>

--===============6014700161201442472==--


From nobody Sun Nov 17 16:24:39 2019
Return-Path: <martin.h.duke@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 8792C12000F for <quic@ietfa.amsl.com>; Sun, 17 Nov 2019 16:24:37 -0800 (PST)
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_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 Eh3Kd7uHuLbO for <quic@ietfa.amsl.com>; Sun, 17 Nov 2019 16:24:34 -0800 (PST)
Received: from mail-wm1-x334.google.com (mail-wm1-x334.google.com [IPv6:2a00:1450:4864:20::334]) (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 7C3E312020A for <quic@ietf.org>; Sun, 17 Nov 2019 16:24:34 -0800 (PST)
Received: by mail-wm1-x334.google.com with SMTP id z26so15504103wmi.4 for <quic@ietf.org>; Sun, 17 Nov 2019 16:24:34 -0800 (PST)
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=M9kwcja5kkECsZmFRag8YoLhrtl9eXSfqwRowoD0IYw=; b=s7LWCYGj5S5vbRIdLNjkXtURRdPpKduML8qjPwboYbcEwEhb2gD9UUJThQwyNXntGE /by9BuEXwLvL26piQtI3rmr/ej5yU4q4mG6iTXvhSObj9xbUjOT4vXlg/QgjeMhyq7RF MZXR1sdoOXXmYYzpySHi5c3RUEIJGq9R1Nz7FAtwIWFMurT4fH8rctq4epxNe42+kk6U 9aOsJQFokOp+35XkDoAUktvQLNMHJPEzFkse22I5AhlGoipN2BLIy/B+qfK3re5oEw5B An3CQNLvINDGrM5SEB/nxpIIFEvMo1gMvwcitFh+7TFkEVold5cf9wy91/3YVDH6LI0n G0tA==
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=M9kwcja5kkECsZmFRag8YoLhrtl9eXSfqwRowoD0IYw=; b=XfDf9rgBCLO7F7r8yHV+23hYgZBI1KOIfnGGgdxqqYqQ2XYk6fwkVGRNaV+qkxYRjz HoWVEUz1KrnMWhY+q7fIBlfZLke5NtE6sGO8KlBOrFSWglxxEREsqPWmrpNtIHhrhRaZ CMnYu2S/9dvGCWRvkrlrJQU0Ajq6OV3tYpZmRXlDTz7Z5JX5hnZ4Ve/E1QxAfkKkMPGI twPyGQ1gX/9eixrtOzp+fIPpMdJkTFtKbEiSdorr0zeffH7sfPlesLXH8KLtn9AmNBNV OkyKXEuGPk/+Eb4ZHqLaAgNz8QQ601xWH/YcnbWmVJipNLiljbWiWSv7Xw06/6ZncklW QzUQ==
X-Gm-Message-State: APjAAAWUurRqDGOz7wOiNhElI43OV9WURtBN0Utuv0PTz4POrUSJ8FuE V6GRuBGL+4pA54di4ObWBs6S1brMeCmDTphLU7LvPMpB
X-Google-Smtp-Source: APXvYqxz0Ku1iKbLkr4JKWiVU9XvbufVmOZ0nlD0XTbxNCkUbZlXhLO1+9JqN3zFt+GiuSXC3qSUqzZqV6dmc2gKnUM=
X-Received: by 2002:a1c:2846:: with SMTP id o67mr26465950wmo.7.1574036672791;  Sun, 17 Nov 2019 16:24:32 -0800 (PST)
MIME-Version: 1.0
References: <6A43BEC7-F9DE-40C9-BF70-BF1618EAFE01@mnot.net> <88BCFF39-6F9D-4E03-8787-561EECBBACE4@gbiv.com> <FD5201A5-C179-4302-B437-57561FB8DB24@mnot.net> <DM6PR22MB20101F0D1CC9867D5F3EE865DA740@DM6PR22MB2010.namprd22.prod.outlook.com> <CAM4esxTYYJiPBgEdj278k2ZggZ_+D8CDd2rOjM14JRCLESowPg@mail.gmail.com> <CAM4esxRXnWj_D==G2qLc39W+73xt+gw64qPxSbW=2RGyD_=wNw@mail.gmail.com> <CAKcm_gPJw3rNgTRCATN9==Nno4Q--X433r4LCjiGytr_VJ3pGg@mail.gmail.com>
In-Reply-To: <CAKcm_gPJw3rNgTRCATN9==Nno4Q--X433r4LCjiGytr_VJ3pGg@mail.gmail.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Mon, 18 Nov 2019 08:24:21 +0800
Message-ID: <CAM4esxSmKDmkO+7rPRwnCSMk0jY4qho=CFAzV6MD-+-_Wf5biA@mail.gmail.com>
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
To: Ian Swett <ianswett@google.com>
Cc: Mike Bishop <mbishop@evequefou.be>, Lars Eggert <lars@eggert.org>,  Mark Nottingham <mnot@mnot.net>, IETF QUIC WG <quic@ietf.org>, Roy Fielding <fielding@gbiv.com>
Content-Type: multipart/alternative; boundary="000000000000becb22059793f81b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/pwLcy-b6TbUrnAolo8m7LK1dAHg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 18 Nov 2019 00:24:38 -0000

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

OK, I apparently missed taht a few of these pushed to master. Yes, let's
move for late-stage

On Wed, Nov 13, 2019 at 10:39 PM Ian Swett <ianswett@google.com> wrote:

> I'm not aware of anything important in-flight( :) ) for recovery.  #3066
> <https://github.com/quicwg/base-drafts/pull/3066> has been in the
> editor's copy for over a week now, and did not quite make -24, so I would
> recommend reading the editors copy.  There is one handshake optimization PR(
> #3080 <https://github.com/quicwg/base-drafts/pull/3080>) and an alternate
> solution to the amplification deadlock(#3162
> <https://github.com/quicwg/base-drafts/pull/3162>), but neither is
> critical in my opinion.
>
> There is a possibility of the discard keys conversation changing recovery,
> though at least one solution(HANDSHAKE_DONE
> <https://github.com/quicwg/base-drafts/pull/3145>) does not require any
> changes.  If changes are required, I expect them to be ~2-3 sentences.
>
> On Tue, Nov 12, 2019 at 7:43 PM Martin Duke <martin.h.duke@gmail.com>
> wrote:
>
>> Put another way, I think Gorry's planned review of draft-24 is probably
>> premature.
>>
>> On Tue, Nov 12, 2019 at 4:42 PM Martin Duke <martin.h.duke@gmail.com>
>> wrote:
>>
>>> IMO the recovery draft is in the midst of a major revision dealing with
>>> the aftereffects of discarding the crypto timeout. Ian still has a bunch of
>>> stuff in flight for this. When all of those PRs land I would like to have a
>>> short period to review the working draft and see if it looks good.
>>>
>>> On Mon, Nov 11, 2019 at 7:40 AM Mike Bishop <mbishop@evequefou.be>
>>> wrote:
>>>
>>>> I'll also note that it's relatively easy from a spec perspective to
>>>> allow trailers to arrive before the end of the body, or to allow multiple
>>>> sets of trailers to arrive.  I suspect most clients won't process trailers
>>>> until they have the body anyway, but the real question is what clients do
>>>> with multiple trailer sets.  I'm not certain whether that's in our scope or
>>>> not, but that's a separate conversation.  Feel free to open an issue for
>>>> that specific discussion.
>>>>
>>>> -----Original Message-----
>>>> From: QUIC <quic-bounces@ietf.org> On Behalf Of Mark Nottingham
>>>> Sent: Sunday, November 10, 2019 8:01 PM
>>>> To: Roy Fielding <fielding@gbiv.com>
>>>> Cc: Lars Eggert <lars@eggert.org>; IETF QUIC WG <quic@ietf.org>
>>>> Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to
>>>> the Late-Stage Process
>>>>
>>>> Hi Roy,
>>>>
>>>> Responding to the parts relevant to this CfC.
>>>>
>>>> > On 7 Nov 2019, at 5:39 am, Roy T. Fielding <fielding@gbiv.com> wrote:
>>>> >
>>>> >> On Nov 5, 2019, at 5:01 PM, Mark Nottingham <mnot@mnot.net> wrote:
>>>> >>
>>>> >> Previously, we've moved to the 'late-stage process' documented at
>>>> [1] for the Transport and TLS drafts. The chairs and editors now feel that
>>>> it's time to move the Recovery, HTTP/3, and QPACK drafts to that process as
>>>> well.
>>>> >>
>>>> >> As before, this is because we're getting to a stage we feel the
>>>> documents would benefit from slower and slightly more formal process, so
>>>> that the rate of change is not so high, changes that do occur are
>>>> well-vetted, and the documents get closer to reflecting consensus in the
>>>> working group.
>>>> >
>>>> > I don't think that process has worked well for QUIC.
>>>>
>>>> Noted.
>>>>
>>>> > There are specific issues that are contentious enough to timebox and
>>>> > conclude, in a formal (and faster) fashion than was done before.
>>>> > That makes sense when needed for a specific issue. I don't know of
>>>> any
>>>> > such issues for those three drafts. IOW, I don't know of any issues
>>>> > for which it makes sense for the Chairs to pre-empt the specification
>>>> > authors in deciding what can or cannot result in changes to the
>>>> drafts
>>>> > just because of the timing of when the issue was raised.
>>>>
>>>> You misunderstand the process; the Chairs aren't pre-empting anything,
>>>> the group is attempting to agree to a path to completing this work.
>>>>
>>>> > The late-stage process seems to focus all of our energy into
>>>> > in/out-of-scope arguments rather than actual text in the
>>>> specifications.
>>>>
>>>> I don't see any evidence for that claim; what makes you believe that?
>>>>
>>>> > The last interim spent easily twice as much time discussing process
>>>> > and process planning than it did HTTP/3. Prior interims were worse.
>>>>
>>>> We spent a day talking about transport and TLS, part of a morning
>>>> talking about planning the future of our work (if you want to call that
>>>> "process and process planning") and the bulk of the (longer) afternoon
>>>> session talking about H3. This isn't surprising, since our goal for the
>>>> meeting was to get the Transport and TLS documents close to finished.
>>>>
>>>> > I don't even recall the last time contents of the HTTP/3 spec being
>>>> > discussed on list, outside of very specific issues related to
>>>> transport.
>>>> > I would like to see HTTP/3 written with HTTP in mind, not as a set of
>>>> > diffs against h2.
>>>>
>>>> That is by charter; we're largely limited to mapping H2 onto QUIC.
>>>>
>>>> > This is not a small undertaking, but it isn't a massive one either..
>>>> > Basically, import the bits of h2 that are necessary to explain
>>>> > HTTP/3's operation and intent, and then start referencing the
>>>> > http-core drafts instead of 723x. Yes, I know that is risky, but it
>>>> is the right thing to do.
>>>> > And it needs to be done before http-core is finished, since that
>>>> > effort exists largely to place the right content (in the right
>>>> places)
>>>> > for
>>>> > HTTP/3 to reference.
>>>>
>>>> AIUI that is still our intent, and shouldn't be impeded by the
>>>> late-stage process, since that work should be editorial.
>>>>
>>>> > I have no idea what the status is with QPACK, but we should learn a
>>>> > lesson from the last time and make sure the fixed compression
>>>> > dictionary (if any) is based on traffic at more than one proxy or
>>>> > origin server. Or at least have each of the major deployments
>>>> generate
>>>> > their local "best" encoding and do some cross-testing of the N
>>>> choices
>>>> > (plus one or two based on a hand-crafted expert merge).
>>>> >
>>>> > I would like for HTTP/3 to have a mechanism for communicating
>>>> metadata
>>>> > (like trailers) in mid-stream, both for requests (e.g., priority) and
>>>> > responses (e.g., chained sigs). That has been a design goal for HTTP
>>>> > since 1995 or so. HTTP/1.1 had it, albeit limited to chunked
>>>> extensions.
>>>> > It has been proposed multiple times and keeps getting postponed
>>>> > because of "concern about scope". This is not a semantics issue (they
>>>> > are just optional trailers that arrive early) -- it is a multiplex
>>>> > framing issue (a new frame type and expectation to process).
>>>>
>>>> Where are the multiple proposals you refer to? We've been working on h3
>>>> now for more than three years. If you submit them now, they'll be design
>>>> issues.
>>>>
>>>> I'd say that the Late-Stage process (or at least the proposal of
>>>> adopting it) is working exactly as intended here -- making people realise
>>>> that if they still have issues / changes that they want discussed, they
>>>> need to bring them to our attention now, not as we go to WGLC.
>>>>
>>>> Cheers,
>>>>
>>>> --
>>>> Mark Nottingham   https://www.mnot.net/
>>>>
>>>>

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

<div dir=3D"ltr">OK, I apparently missed taht a few of these pushed to mast=
er. Yes, let&#39;s move for late-stage</div><br><div class=3D"gmail_quote">=
<div dir=3D"ltr" class=3D"gmail_attr">On Wed, Nov 13, 2019 at 10:39 PM Ian =
Swett &lt;<a href=3D"mailto:ianswett@google.com">ianswett@google.com</a>&gt=
; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px=
 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div di=
r=3D"ltr">I&#39;m not aware of anything important in-flight( :) ) for recov=
ery.=C2=A0 <a href=3D"https://github.com/quicwg/base-drafts/pull/3066" targ=
et=3D"_blank">#3066</a> has been in the editor&#39;s copy for over a week n=
ow, and did not quite make -24, so I would recommend reading the editors co=
py.=C2=A0 There is one handshake optimization PR(<a href=3D"https://github.=
com/quicwg/base-drafts/pull/3080" target=3D"_blank">#3080</a>) and an alter=
nate solution to the amplification deadlock(<a href=3D"https://github.com/q=
uicwg/base-drafts/pull/3162" target=3D"_blank">#3162</a>), but neither is c=
ritical in my opinion.<div><br></div><div>There is a possibility=C2=A0of th=
e discard keys conversation=C2=A0changing recovery, though at least one sol=
ution(<a href=3D"https://github.com/quicwg/base-drafts/pull/3145" target=3D=
"_blank">HANDSHAKE_DONE</a>) does not require any changes.=C2=A0 If changes=
 are required, I expect them to be ~2-3 sentences.</div></div><br><div clas=
s=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Nov 12, 201=
9 at 7:43 PM Martin Duke &lt;<a href=3D"mailto:martin.h.duke@gmail.com" tar=
get=3D"_blank">martin.h.duke@gmail.com</a>&gt; wrote:<br></div><blockquote =
class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px sol=
id rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">Put another way, I t=
hink Gorry&#39;s planned review of draft-24 is probably premature.<br></div=
><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tu=
e, Nov 12, 2019 at 4:42 PM Martin Duke &lt;<a href=3D"mailto:martin.h.duke@=
gmail.com" target=3D"_blank">martin.h.duke@gmail.com</a>&gt; wrote:<br></di=
v><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;borde=
r-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">IMO th=
e recovery draft is in the midst of a major revision dealing with the after=
effects of discarding the crypto timeout. Ian still has a bunch of stuff in=
 flight for this. When all of those PRs land I would like to have a short p=
eriod to review the working draft and see if it looks good.<br></div><br><d=
iv class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Nov =
11, 2019 at 7:40 AM Mike Bishop &lt;<a href=3D"mailto:mbishop@evequefou.be"=
 target=3D"_blank">mbishop@evequefou.be</a>&gt; wrote:<br></div><blockquote=
 class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px so=
lid rgb(204,204,204);padding-left:1ex">I&#39;ll also note that it&#39;s rel=
atively easy from a spec perspective to allow trailers to arrive before the=
 end of the body, or to allow multiple sets of trailers to arrive.=C2=A0 I =
suspect most clients won&#39;t process trailers until they have the body an=
yway, but the real question is what clients do with multiple trailer sets.=
=C2=A0 I&#39;m not certain whether that&#39;s in our scope or not, but that=
&#39;s a separate conversation.=C2=A0 Feel free to open an issue for that s=
pecific discussion.<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 Mark Nottingham<br>
Sent: Sunday, November 10, 2019 8:01 PM<br>
To: Roy Fielding &lt;<a href=3D"mailto:fielding@gbiv.com" target=3D"_blank"=
>fielding@gbiv.com</a>&gt;<br>
Cc: Lars Eggert &lt;<a href=3D"mailto:lars@eggert.org" target=3D"_blank">la=
rs@eggert.org</a>&gt;; IETF QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" ta=
rget=3D"_blank">quic@ietf.org</a>&gt;<br>
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the L=
ate-Stage Process<br>
<br>
Hi Roy,<br>
<br>
Responding to the parts relevant to this CfC.<br>
<br>
&gt; On 7 Nov 2019, at 5:39 am, Roy T. Fielding &lt;<a href=3D"mailto:field=
ing@gbiv.com" target=3D"_blank">fielding@gbiv.com</a>&gt; wrote:<br>
&gt; <br>
&gt;&gt; On Nov 5, 2019, at 5:01 PM, Mark Nottingham &lt;<a href=3D"mailto:=
mnot@mnot.net" target=3D"_blank">mnot@mnot.net</a>&gt; wrote:<br>
&gt;&gt; <br>
&gt;&gt; Previously, we&#39;ve moved to the &#39;late-stage process&#39; do=
cumented at [1] for the Transport and TLS drafts. The chairs and editors no=
w feel that it&#39;s time to move the Recovery, HTTP/3, and QPACK drafts to=
 that process as well.<br>
&gt;&gt; <br>
&gt;&gt; As before, this is because we&#39;re getting to a stage we feel th=
e documents would benefit from slower and slightly more formal process, so =
that the rate of change is not so high, changes that do occur are well-vett=
ed, and the documents get closer to reflecting consensus in the working gro=
up.<br>
&gt; <br>
&gt; I don&#39;t think that process has worked well for QUIC.<br>
<br>
Noted.<br>
<br>
&gt; There are specific issues that are contentious enough to timebox and <=
br>
&gt; conclude, in a formal (and faster) fashion than was done before.<br>
&gt; That makes sense when needed for a specific issue. I don&#39;t know of=
 any <br>
&gt; such issues for those three drafts. IOW, I don&#39;t know of any issue=
s <br>
&gt; for which it makes sense for the Chairs to pre-empt the specification =
<br>
&gt; authors in deciding what can or cannot result in changes to the drafts=
 <br>
&gt; just because of the timing of when the issue was raised.<br>
<br>
You misunderstand the process; the Chairs aren&#39;t pre-empting anything, =
the group is attempting to agree to a path to completing this work.<br>
<br>
&gt; The late-stage process seems to focus all of our energy into <br>
&gt; in/out-of-scope arguments rather than actual text in the specification=
s.<br>
<br>
I don&#39;t see any evidence for that claim; what makes you believe that?<b=
r>
<br>
&gt; The last interim spent easily twice as much time discussing process <b=
r>
&gt; and process planning than it did HTTP/3. Prior interims were worse.<br=
>
<br>
We spent a day talking about transport and TLS, part of a morning talking a=
bout planning the future of our work (if you want to call that &quot;proces=
s and process planning&quot;) and the bulk of the (longer) afternoon sessio=
n talking about H3. This isn&#39;t surprising, since our goal for the meeti=
ng was to get the Transport and TLS documents close to finished.<br>
<br>
&gt; I don&#39;t even recall the last time contents of the HTTP/3 spec bein=
g <br>
&gt; discussed on list, outside of very specific issues related to transpor=
t.<br>
&gt; I would like to see HTTP/3 written with HTTP in mind, not as a set of =
<br>
&gt; diffs against h2.<br>
<br>
That is by charter; we&#39;re largely limited to mapping H2 onto QUIC. <br>
<br>
&gt; This is not a small undertaking, but it isn&#39;t a massive one either=
..<br>
&gt; Basically, import the bits of h2 that are necessary to explain <br>
&gt; HTTP/3&#39;s operation and intent, and then start referencing the <br>
&gt; http-core drafts instead of 723x. Yes, I know that is risky, but it is=
 the right thing to do.<br>
&gt; And it needs to be done before http-core is finished, since that <br>
&gt; effort exists largely to place the right content (in the right places)=
 <br>
&gt; for<br>
&gt; HTTP/3 to reference.<br>
<br>
AIUI that is still our intent, and shouldn&#39;t be impeded by the late-sta=
ge process, since that work should be editorial.<br>
<br>
&gt; I have no idea what the status is with QPACK, but we should learn a <b=
r>
&gt; lesson from the last time and make sure the fixed compression <br>
&gt; dictionary (if any) is based on traffic at more than one proxy or <br>
&gt; origin server. Or at least have each of the major deployments generate=
 <br>
&gt; their local &quot;best&quot; encoding and do some cross-testing of the=
 N choices <br>
&gt; (plus one or two based on a hand-crafted expert merge).<br>
&gt; <br>
&gt; I would like for HTTP/3 to have a mechanism for communicating metadata=
 <br>
&gt; (like trailers) in mid-stream, both for requests (e.g., priority) and =
<br>
&gt; responses (e.g., chained sigs). That has been a design goal for HTTP <=
br>
&gt; since 1995 or so. HTTP/1.1 had it, albeit limited to chunked extension=
s.<br>
&gt; It has been proposed multiple times and keeps getting postponed <br>
&gt; because of &quot;concern about scope&quot;. This is not a semantics is=
sue (they <br>
&gt; are just optional trailers that arrive early) -- it is a multiplex <br=
>
&gt; framing issue (a new frame type and expectation to process).<br>
<br>
Where are the multiple proposals you refer to? We&#39;ve been working on h3=
 now for more than three years. If you submit them now, they&#39;ll be desi=
gn issues.<br>
<br>
I&#39;d say that the Late-Stage process (or at least the proposal of adopti=
ng it) is working exactly as intended here -- making people realise that if=
 they still have issues / changes that they want discussed, they need to br=
ing them to our attention now, not as we go to WGLC.<br>
<br>
Cheers,<br>
<br>
--<br>
Mark Nottingham=C2=A0 =C2=A0<a href=3D"https://www.mnot.net/" rel=3D"norefe=
rrer" target=3D"_blank">https://www.mnot.net/</a><br>
<br>
</blockquote></div>
</blockquote></div>
</blockquote></div>
</blockquote></div>

--000000000000becb22059793f81b--


From liu-zw16@mails.tsinghua.edu.cn  Mon Nov 18 15:35:53 2019
Return-Path: <liu-zw16@mails.tsinghua.edu.cn>
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 94B2B12018B for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 15:35:53 -0800 (PST)
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_FONT_FACE_BAD=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, 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 DiCDRy8hSDCB for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 15:35:49 -0800 (PST)
Received: from zg8tmtu5ljy1ljeznc42.icoremail.net (zg8tmtu5ljy1ljeznc42.icoremail.net [159.65.134.6]) by ietfa.amsl.com (Postfix) with SMTP id 854C2120115 for <quic@ietf.org>; Mon, 18 Nov 2019 15:35:48 -0800 (PST)
Received: by ajax-webmail-app-4 (Coremail) ; Tue, 19 Nov 2019 07:35:39 +0800 (GMT+08:00)
X-Originating-IP: [111.223.107.195]
Date: Tue, 19 Nov 2019 07:35:39 +0800 (GMT+08:00)
X-CM-HeaderCharset: UTF-8
From: =?UTF-8?B?5YiY5b+X5paH?= <liu-zw16@mails.tsinghua.edu.cn>
To: quic@ietf.org
Subject: New draft and welcome any comments
X-Priority: 3
X-Mailer: Coremail Webmail Server Version XT3.0.8 dev build 20190909(dad6f454) Copyright (c) 2002-2019 www.mailtech.cn tsinghua.edu.cn
Content-Type: multipart/alternative;  boundary="----=_Part_491550_1843797635.1574120139846"
MIME-Version: 1.0
Message-ID: <58831a79.22ab6.16e80df2c46.Coremail.liu-zw16@mails.tsinghua.edu.cn>
X-Coremail-Locale: en_US
X-CM-TRANSID: EgQGZQAXWBHLKtNdBSVxAg--.38212W
X-CM-SenderInfo: polxg6rzrwqzpdlo2hxwvl0wxkxdhvlgxou0/1tbiAgYSDFEw99wZ NQAAs8
X-Coremail-Antispam: 1Ur529EdanIXcx71UUUUU7IcSsGvfJ3iIAIbVAYjsxI4VW7Jw CS07vEb4IE77IF4wCS07vE1I0E4x80FVAKz4kxMIAIbVAFxVCaYxvI4VCIwcAKzIAtYxBI daVFxhVjvjDU=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/qgaK_FHyoXd_hy5UP4KhUWWQBEo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Nov 2019 00:38:07 -0000

------=_Part_491550_1843797635.1574120139846
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: base64

RGVhciBhbGwsCgoKV2UgYXJlIFFVSUMgZmFucyBmcm9tIFRzaW5naHVhIFVuaXZlcnNpdHkgYW5k
IHdlIGFyZSB0cnlpbmcgdG8gbWFrZSB1c2VmdWwgZXh0ZW5zaW9uIGF0b3AgUVVJQy4gV2UgaGF2
ZSBidWlsdCBhIG5ldyBwcm90b2NvbCBuYW1lZCBEZWFkbGluZS1hd2FyZSBUcmFuc3BvcnQgUHJv
dG9jb2wgYW5kIGhhdmUgbWFkZSBzb21lIHByb2dyZXNzIGluIHN1cHBvcnRpbmcgdGltZWxpbmVz
cyBkYXRhIHRyYW5zbWlzc2lvbi4gQW5kIHdlIGhhdmUgc3VibWl0dGVkIG91ciBwZXJzb25hbCBk
cmFmdCB0byBRVUlDIFdHLiBJdCdzIG15IGhvbm9yIHRvIHNoYXJlIG91ciB3b3JrIGluIFFVSUMg
bWFpbGluZyBsaXN0IGFuZCB3ZSBhcHByZWNpYXRlIGFueSByZWNvbW1lbmRzIG9uIGl0LiAKCgpI
ZXJlIGlzIG91ciBkcmFmdDoKTmFtZTogZHJhZnQtc2hpLXF1aWMtZHRwClJldmlzaW9uOiAwMApU
aXRsZTogRGVhZGxpbmUtYXdhcmUgVHJhbnNwb3J0IFByb3RvY29sCkRvY3VtZW50IGRhdGU6IDIw
MTktMTEtMTcKR3JvdXA6IEluZGl2aWR1YWwgU3VibWlzc2lvbgpQYWdlczogMTIKVVJMOiBodHRw
czovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtc2hpLXF1aWMtZHRwLTAwLnR4
dApTdGF0dXM6IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LXNoaS1xdWlj
LWR0cC8KSHRtbGl6ZWQ6IGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1zaGktcXVp
Yy1kdHAtMDAKSHRtbGl6ZWQ6IGh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2h0bWwv
ZHJhZnQtc2hpLXF1aWMtZHRwCkFic3RyYWN0OgpUaGlzIGRvY3VtZW50IGRlZmluZXMgRGVhZGxp
bmUtYXdhcmUgVHJhbnNwb3J0IFByb3RvY29sIChEVFApIHRvCnByb3ZpZGUgYmxvY2stYmFzZWQg
ZGVsaXZlci1iZWZvcmUtZGVhZGxpbmUgdHJhbnNtaXNzaW9uLiBUaGUKaW50ZW50aW9uIG9mIHRo
aXMgbWVtbyBpcyB0byBkZXNjcmliZSBhIG1lY2hhbmlzbSB0byBmdWxmaWxsCnVucmVsaWFibGUg
dHJhbnNtaXNzaW9uIGJhc2VkIG9uIFFVSUMgYXMgd2VsbCBhcyBob3cgdG8gZW5oYW5jZQp0aW1l
bGluZXNzIG9mIGRhdGEgZGVsaXZlcnkuCgoKQlRXLCBJJ20gb24gc2l0ZSBmb3IgSUVURiAxMDYg
YW5kIGlmIGFueW9uZSBpcyBpbnRlcmVzdGVkIGluIG91ciB3b3JrLCBwbGVhc2UgZW1haWwgbWUg
b3IgY2F0Y2ggbWUgZHVyaW5nIHRoaXMgd2Vlay4KCgpUaGFua3MgZm9yIHlvdXIgdGltZS4KCgrl
iJjlv5fmlofvvZxaaGl3ZW4gTGl1IArmiYvmnLrvvZxNb2JpbGU6Kzg2IDE1OTAxMDgyNjUxCua4
heWNjuWkp+Wtpu+9nFRzaW5naHVhIFVuaXZlcnNpdHk=
------=_Part_491550_1843797635.1574120139846
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: base64

PGRpdiBzdHlsZT0iY29sb3I6IHJnYig0OSwgNTMsIDU5KTsgZm9udC1mYW1pbHk6IOW+rui9r+mb
hem7kSwgVmVyZGFuYSwgJnF1b3Q7TWljcm9zb2Z0IFlhaGVpJnF1b3Q7LCBTaW1TdW4sIHNhbnMt
c2VyaWY7IGZvbnQtdmFyaWFudC1udW1lcmljOiBub3JtYWw7IGZvbnQtdmFyaWFudC1lYXN0LWFz
aWFuOiBub3JtYWw7IGxpbmUtaGVpZ2h0OiAyMi40cHg7IHdpZG93czogMTsiPkRlYXIgYWxsLDwv
ZGl2PjxkaXYgc3R5bGU9ImNvbG9yOiByZ2IoNDksIDUzLCA1OSk7IGZvbnQtZmFtaWx5OiDlvq7o
va/pm4Xpu5EsIFZlcmRhbmEsICZxdW90O01pY3Jvc29mdCBZYWhlaSZxdW90OywgU2ltU3VuLCBz
YW5zLXNlcmlmOyBmb250LXZhcmlhbnQtbnVtZXJpYzogbm9ybWFsOyBmb250LXZhcmlhbnQtZWFz
dC1hc2lhbjogbm9ybWFsOyBsaW5lLWhlaWdodDogMjIuNHB4OyB3aWRvd3M6IDE7Ij48YnI+PC9k
aXY+PGRpdiBzdHlsZT0iY29sb3I6IHJnYig0OSwgNTMsIDU5KTsgZm9udC1mYW1pbHk6IOW+rui9
r+mbhem7kSwgVmVyZGFuYSwgJnF1b3Q7TWljcm9zb2Z0IFlhaGVpJnF1b3Q7LCBTaW1TdW4sIHNh
bnMtc2VyaWY7IGZvbnQtdmFyaWFudC1udW1lcmljOiBub3JtYWw7IGZvbnQtdmFyaWFudC1lYXN0
LWFzaWFuOiBub3JtYWw7IGxpbmUtaGVpZ2h0OiAyMi40cHg7IHdpZG93czogMTsiPldlIGFyZSBR
VUlDIGZhbnMgZnJvbSBUc2luZ2h1YSBVbml2ZXJzaXR5IGFuZCB3ZSBhcmUgdHJ5aW5nIHRvIG1h
a2UgdXNlZnVsIGV4dGVuc2lvbiBhdG9wIFFVSUMuIFdlIGhhdmUgYnVpbHQgYSBuZXcgcHJvdG9j
b2wgbmFtZWQgRGVhZGxpbmUtYXdhcmUgVHJhbnNwb3J0IFByb3RvY29sIGFuZCBoYXZlIG1hZGUg
c29tZSBwcm9ncmVzcyBpbiBzdXBwb3J0aW5nIHRpbWVsaW5lc3MgZGF0YSB0cmFuc21pc3Npb24u
IEFuZCB3ZSBoYXZlIHN1Ym1pdHRlZCBvdXIgcGVyc29uYWwgZHJhZnQgdG8gUVVJQyBXRy4gSXQn
cyBteSBob25vciB0byBzaGFyZSBvdXIgd29yayBpbiBRVUlDIG1haWxpbmcgbGlzdCBhbmQgd2Ug
YXBwcmVjaWF0ZSBhbnkgcmVjb21tZW5kcyBvbiBpdC4mbmJzcDs8L2Rpdj48ZGl2IHN0eWxlPSJj
b2xvcjogcmdiKDQ5LCA1MywgNTkpOyBmb250LWZhbWlseTog5b6u6L2v6ZuF6buRLCBWZXJkYW5h
LCAmcXVvdDtNaWNyb3NvZnQgWWFoZWkmcXVvdDssIFNpbVN1biwgc2Fucy1zZXJpZjsgZm9udC12
YXJpYW50LW51bWVyaWM6IG5vcm1hbDsgZm9udC12YXJpYW50LWVhc3QtYXNpYW46IG5vcm1hbDsg
bGluZS1oZWlnaHQ6IDIyLjRweDsgd2lkb3dzOiAxOyI+PGJyPjwvZGl2PjxkaXYgc3R5bGU9ImNv
bG9yOiByZ2IoNDksIDUzLCA1OSk7IGZvbnQtZmFtaWx5OiDlvq7ova/pm4Xpu5EsIFZlcmRhbmEs
ICZxdW90O01pY3Jvc29mdCBZYWhlaSZxdW90OywgU2ltU3VuLCBzYW5zLXNlcmlmOyBmb250LXZh
cmlhbnQtbnVtZXJpYzogbm9ybWFsOyBmb250LXZhcmlhbnQtZWFzdC1hc2lhbjogbm9ybWFsOyBs
aW5lLWhlaWdodDogMjIuNHB4OyB3aWRvd3M6IDE7Ij5IZXJlIGlzIG91ciBkcmFmdDo8L2Rpdj48
ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDQ5LCA1MywgNTkpOyBmb250LWZhbWlseTog5b6u6L2v6ZuF
6buRLCBWZXJkYW5hLCAmcXVvdDtNaWNyb3NvZnQgWWFoZWkmcXVvdDssIFNpbVN1biwgc2Fucy1z
ZXJpZjsgZm9udC12YXJpYW50LW51bWVyaWM6IG5vcm1hbDsgZm9udC12YXJpYW50LWVhc3QtYXNp
YW46IG5vcm1hbDsgbGluZS1oZWlnaHQ6IDIyLjRweDsgd2lkb3dzOiAxOyI+TmFtZTogZHJhZnQt
c2hpLXF1aWMtZHRwPC9kaXY+PGRpdiBzdHlsZT0iY29sb3I6IHJnYig0OSwgNTMsIDU5KTsgZm9u
dC1mYW1pbHk6IOW+rui9r+mbhem7kSwgVmVyZGFuYSwgJnF1b3Q7TWljcm9zb2Z0IFlhaGVpJnF1
b3Q7LCBTaW1TdW4sIHNhbnMtc2VyaWY7IGZvbnQtdmFyaWFudC1udW1lcmljOiBub3JtYWw7IGZv
bnQtdmFyaWFudC1lYXN0LWFzaWFuOiBub3JtYWw7IGxpbmUtaGVpZ2h0OiAyMi40cHg7IHdpZG93
czogMTsiPlJldmlzaW9uOiAwMDwvZGl2PjxkaXYgc3R5bGU9ImNvbG9yOiByZ2IoNDksIDUzLCA1
OSk7IGZvbnQtZmFtaWx5OiDlvq7ova/pm4Xpu5EsIFZlcmRhbmEsICZxdW90O01pY3Jvc29mdCBZ
YWhlaSZxdW90OywgU2ltU3VuLCBzYW5zLXNlcmlmOyBmb250LXZhcmlhbnQtbnVtZXJpYzogbm9y
bWFsOyBmb250LXZhcmlhbnQtZWFzdC1hc2lhbjogbm9ybWFsOyBsaW5lLWhlaWdodDogMjIuNHB4
OyB3aWRvd3M6IDE7Ij5UaXRsZTogRGVhZGxpbmUtYXdhcmUgVHJhbnNwb3J0IFByb3RvY29sPC9k
aXY+PGRpdiBzdHlsZT0iY29sb3I6IHJnYig0OSwgNTMsIDU5KTsgZm9udC1mYW1pbHk6IOW+rui9
r+mbhem7kSwgVmVyZGFuYSwgJnF1b3Q7TWljcm9zb2Z0IFlhaGVpJnF1b3Q7LCBTaW1TdW4sIHNh
bnMtc2VyaWY7IGZvbnQtdmFyaWFudC1udW1lcmljOiBub3JtYWw7IGZvbnQtdmFyaWFudC1lYXN0
LWFzaWFuOiBub3JtYWw7IGxpbmUtaGVpZ2h0OiAyMi40cHg7IHdpZG93czogMTsiPkRvY3VtZW50
IGRhdGU6IDIwMTktMTEtMTc8L2Rpdj48ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDQ5LCA1MywgNTkp
OyBmb250LWZhbWlseTog5b6u6L2v6ZuF6buRLCBWZXJkYW5hLCAmcXVvdDtNaWNyb3NvZnQgWWFo
ZWkmcXVvdDssIFNpbVN1biwgc2Fucy1zZXJpZjsgZm9udC12YXJpYW50LW51bWVyaWM6IG5vcm1h
bDsgZm9udC12YXJpYW50LWVhc3QtYXNpYW46IG5vcm1hbDsgbGluZS1oZWlnaHQ6IDIyLjRweDsg
d2lkb3dzOiAxOyI+R3JvdXA6IEluZGl2aWR1YWwgU3VibWlzc2lvbjwvZGl2PjxkaXYgc3R5bGU9
ImNvbG9yOiByZ2IoNDksIDUzLCA1OSk7IGZvbnQtZmFtaWx5OiDlvq7ova/pm4Xpu5EsIFZlcmRh
bmEsICZxdW90O01pY3Jvc29mdCBZYWhlaSZxdW90OywgU2ltU3VuLCBzYW5zLXNlcmlmOyBmb250
LXZhcmlhbnQtbnVtZXJpYzogbm9ybWFsOyBmb250LXZhcmlhbnQtZWFzdC1hc2lhbjogbm9ybWFs
OyBsaW5lLWhlaWdodDogMjIuNHB4OyB3aWRvd3M6IDE7Ij5QYWdlczogMTI8L2Rpdj48ZGl2IHN0
eWxlPSJjb2xvcjogcmdiKDQ5LCA1MywgNTkpOyBmb250LWZhbWlseTog5b6u6L2v6ZuF6buRLCBW
ZXJkYW5hLCAmcXVvdDtNaWNyb3NvZnQgWWFoZWkmcXVvdDssIFNpbVN1biwgc2Fucy1zZXJpZjsg
Zm9udC12YXJpYW50LW51bWVyaWM6IG5vcm1hbDsgZm9udC12YXJpYW50LWVhc3QtYXNpYW46IG5v
cm1hbDsgbGluZS1oZWlnaHQ6IDIyLjRweDsgd2lkb3dzOiAxOyI+VVJMOiBodHRwczovL3d3dy5p
ZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtc2hpLXF1aWMtZHRwLTAwLnR4dDwvZGl2Pjxk
aXYgc3R5bGU9ImNvbG9yOiByZ2IoNDksIDUzLCA1OSk7IGZvbnQtZmFtaWx5OiDlvq7ova/pm4Xp
u5EsIFZlcmRhbmEsICZxdW90O01pY3Jvc29mdCBZYWhlaSZxdW90OywgU2ltU3VuLCBzYW5zLXNl
cmlmOyBmb250LXZhcmlhbnQtbnVtZXJpYzogbm9ybWFsOyBmb250LXZhcmlhbnQtZWFzdC1hc2lh
bjogbm9ybWFsOyBsaW5lLWhlaWdodDogMjIuNHB4OyB3aWRvd3M6IDE7Ij5TdGF0dXM6IGh0dHBz
Oi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LXNoaS1xdWljLWR0cC88L2Rpdj48ZGl2
IHN0eWxlPSJjb2xvcjogcmdiKDQ5LCA1MywgNTkpOyBmb250LWZhbWlseTog5b6u6L2v6ZuF6buR
LCBWZXJkYW5hLCAmcXVvdDtNaWNyb3NvZnQgWWFoZWkmcXVvdDssIFNpbVN1biwgc2Fucy1zZXJp
ZjsgZm9udC12YXJpYW50LW51bWVyaWM6IG5vcm1hbDsgZm9udC12YXJpYW50LWVhc3QtYXNpYW46
IG5vcm1hbDsgbGluZS1oZWlnaHQ6IDIyLjRweDsgd2lkb3dzOiAxOyI+SHRtbGl6ZWQ6IGh0dHBz
Oi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1zaGktcXVpYy1kdHAtMDA8L2Rpdj48ZGl2IHN0
eWxlPSJjb2xvcjogcmdiKDQ5LCA1MywgNTkpOyBmb250LWZhbWlseTog5b6u6L2v6ZuF6buRLCBW
ZXJkYW5hLCAmcXVvdDtNaWNyb3NvZnQgWWFoZWkmcXVvdDssIFNpbVN1biwgc2Fucy1zZXJpZjsg
Zm9udC12YXJpYW50LW51bWVyaWM6IG5vcm1hbDsgZm9udC12YXJpYW50LWVhc3QtYXNpYW46IG5v
cm1hbDsgbGluZS1oZWlnaHQ6IDIyLjRweDsgd2lkb3dzOiAxOyI+SHRtbGl6ZWQ6IGh0dHBzOi8v
ZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2h0bWwvZHJhZnQtc2hpLXF1aWMtZHRwPC9kaXY+PGRp
diBzdHlsZT0iY29sb3I6IHJnYig0OSwgNTMsIDU5KTsgZm9udC1mYW1pbHk6IOW+rui9r+mbhem7
kSwgVmVyZGFuYSwgJnF1b3Q7TWljcm9zb2Z0IFlhaGVpJnF1b3Q7LCBTaW1TdW4sIHNhbnMtc2Vy
aWY7IGZvbnQtdmFyaWFudC1udW1lcmljOiBub3JtYWw7IGZvbnQtdmFyaWFudC1lYXN0LWFzaWFu
OiBub3JtYWw7IGxpbmUtaGVpZ2h0OiAyMi40cHg7IHdpZG93czogMTsiPjwvZGl2PjxkaXYgc3R5
bGU9ImNvbG9yOiByZ2IoNDksIDUzLCA1OSk7IGZvbnQtZmFtaWx5OiDlvq7ova/pm4Xpu5EsIFZl
cmRhbmEsICZxdW90O01pY3Jvc29mdCBZYWhlaSZxdW90OywgU2ltU3VuLCBzYW5zLXNlcmlmOyBm
b250LXZhcmlhbnQtbnVtZXJpYzogbm9ybWFsOyBmb250LXZhcmlhbnQtZWFzdC1hc2lhbjogbm9y
bWFsOyBsaW5lLWhlaWdodDogMjIuNHB4OyB3aWRvd3M6IDE7Ij5BYnN0cmFjdDo8L2Rpdj48ZGl2
IHN0eWxlPSJjb2xvcjogcmdiKDQ5LCA1MywgNTkpOyBmb250LWZhbWlseTog5b6u6L2v6ZuF6buR
LCBWZXJkYW5hLCAmcXVvdDtNaWNyb3NvZnQgWWFoZWkmcXVvdDssIFNpbVN1biwgc2Fucy1zZXJp
ZjsgZm9udC12YXJpYW50LW51bWVyaWM6IG5vcm1hbDsgZm9udC12YXJpYW50LWVhc3QtYXNpYW46
IG5vcm1hbDsgbGluZS1oZWlnaHQ6IDIyLjRweDsgd2lkb3dzOiAxOyI+VGhpcyBkb2N1bWVudCBk
ZWZpbmVzIERlYWRsaW5lLWF3YXJlIFRyYW5zcG9ydCBQcm90b2NvbCAoRFRQKSB0bzwvZGl2Pjxk
aXYgc3R5bGU9ImNvbG9yOiByZ2IoNDksIDUzLCA1OSk7IGZvbnQtZmFtaWx5OiDlvq7ova/pm4Xp
u5EsIFZlcmRhbmEsICZxdW90O01pY3Jvc29mdCBZYWhlaSZxdW90OywgU2ltU3VuLCBzYW5zLXNl
cmlmOyBmb250LXZhcmlhbnQtbnVtZXJpYzogbm9ybWFsOyBmb250LXZhcmlhbnQtZWFzdC1hc2lh
bjogbm9ybWFsOyBsaW5lLWhlaWdodDogMjIuNHB4OyB3aWRvd3M6IDE7Ij5wcm92aWRlIGJsb2Nr
LWJhc2VkIGRlbGl2ZXItYmVmb3JlLWRlYWRsaW5lIHRyYW5zbWlzc2lvbi4gVGhlPC9kaXY+PGRp
diBzdHlsZT0iY29sb3I6IHJnYig0OSwgNTMsIDU5KTsgZm9udC1mYW1pbHk6IOW+rui9r+mbhem7
kSwgVmVyZGFuYSwgJnF1b3Q7TWljcm9zb2Z0IFlhaGVpJnF1b3Q7LCBTaW1TdW4sIHNhbnMtc2Vy
aWY7IGZvbnQtdmFyaWFudC1udW1lcmljOiBub3JtYWw7IGZvbnQtdmFyaWFudC1lYXN0LWFzaWFu
OiBub3JtYWw7IGxpbmUtaGVpZ2h0OiAyMi40cHg7IHdpZG93czogMTsiPmludGVudGlvbiBvZiB0
aGlzIG1lbW8gaXMgdG8gZGVzY3JpYmUgYSBtZWNoYW5pc20gdG8gZnVsZmlsbDwvZGl2PjxkaXYg
c3R5bGU9ImNvbG9yOiByZ2IoNDksIDUzLCA1OSk7IGZvbnQtZmFtaWx5OiDlvq7ova/pm4Xpu5Es
IFZlcmRhbmEsICZxdW90O01pY3Jvc29mdCBZYWhlaSZxdW90OywgU2ltU3VuLCBzYW5zLXNlcmlm
OyBmb250LXZhcmlhbnQtbnVtZXJpYzogbm9ybWFsOyBmb250LXZhcmlhbnQtZWFzdC1hc2lhbjog
bm9ybWFsOyBsaW5lLWhlaWdodDogMjIuNHB4OyB3aWRvd3M6IDE7Ij51bnJlbGlhYmxlIHRyYW5z
bWlzc2lvbiBiYXNlZCBvbiBRVUlDIGFzIHdlbGwgYXMgaG93IHRvIGVuaGFuY2U8L2Rpdj48ZGl2
IHN0eWxlPSJjb2xvcjogcmdiKDQ5LCA1MywgNTkpOyBmb250LWZhbWlseTog5b6u6L2v6ZuF6buR
LCBWZXJkYW5hLCAmcXVvdDtNaWNyb3NvZnQgWWFoZWkmcXVvdDssIFNpbVN1biwgc2Fucy1zZXJp
ZjsgZm9udC12YXJpYW50LW51bWVyaWM6IG5vcm1hbDsgZm9udC12YXJpYW50LWVhc3QtYXNpYW46
IG5vcm1hbDsgbGluZS1oZWlnaHQ6IDIyLjRweDsgd2lkb3dzOiAxOyI+dGltZWxpbmVzcyBvZiBk
YXRhIGRlbGl2ZXJ5LjwvZGl2PjxkaXYgc3R5bGU9ImNvbG9yOiByZ2IoNDksIDUzLCA1OSk7IGZv
bnQtZmFtaWx5OiDlvq7ova/pm4Xpu5EsIFZlcmRhbmEsICZxdW90O01pY3Jvc29mdCBZYWhlaSZx
dW90OywgU2ltU3VuLCBzYW5zLXNlcmlmOyBmb250LXZhcmlhbnQtbnVtZXJpYzogbm9ybWFsOyBm
b250LXZhcmlhbnQtZWFzdC1hc2lhbjogbm9ybWFsOyBsaW5lLWhlaWdodDogMjIuNHB4OyB3aWRv
d3M6IDE7Ij48YnI+PC9kaXY+PGRpdiBzdHlsZT0iY29sb3I6IHJnYig0OSwgNTMsIDU5KTsgZm9u
dC1mYW1pbHk6IOW+rui9r+mbhem7kSwgVmVyZGFuYSwgJnF1b3Q7TWljcm9zb2Z0IFlhaGVpJnF1
b3Q7LCBTaW1TdW4sIHNhbnMtc2VyaWY7IGZvbnQtdmFyaWFudC1udW1lcmljOiBub3JtYWw7IGZv
bnQtdmFyaWFudC1lYXN0LWFzaWFuOiBub3JtYWw7IGxpbmUtaGVpZ2h0OiAyMi40cHg7IHdpZG93
czogMTsiPkJUVywgSSdtIG9uIHNpdGUgZm9yIElFVEYgMTA2IGFuZCBpZiBhbnlvbmUgaXMgaW50
ZXJlc3RlZCBpbiBvdXIgd29yaywgcGxlYXNlIGVtYWlsIG1lIG9yIGNhdGNoIG1lIGR1cmluZyB0
aGlzIHdlZWsuPC9kaXY+PGRpdiBzdHlsZT0iY29sb3I6IHJnYig0OSwgNTMsIDU5KTsgZm9udC1m
YW1pbHk6IOW+rui9r+mbhem7kSwgVmVyZGFuYSwgJnF1b3Q7TWljcm9zb2Z0IFlhaGVpJnF1b3Q7
LCBTaW1TdW4sIHNhbnMtc2VyaWY7IGZvbnQtdmFyaWFudC1udW1lcmljOiBub3JtYWw7IGZvbnQt
dmFyaWFudC1lYXN0LWFzaWFuOiBub3JtYWw7IGxpbmUtaGVpZ2h0OiAyMi40cHg7IHdpZG93czog
MTsiPjxicj48L2Rpdj48ZGl2IHN0eWxlPSJjb2xvcjogcmdiKDQ5LCA1MywgNTkpOyBmb250LWZh
bWlseTog5b6u6L2v6ZuF6buRLCBWZXJkYW5hLCAmcXVvdDtNaWNyb3NvZnQgWWFoZWkmcXVvdDss
IFNpbVN1biwgc2Fucy1zZXJpZjsgZm9udC12YXJpYW50LW51bWVyaWM6IG5vcm1hbDsgZm9udC12
YXJpYW50LWVhc3QtYXNpYW46IG5vcm1hbDsgbGluZS1oZWlnaHQ6IDIyLjRweDsgd2lkb3dzOiAx
OyI+VGhhbmtzIGZvciB5b3VyIHRpbWUuPC9kaXY+PGRpdiBzdHlsZT0iY29sb3I6IHJnYig0OSwg
NTMsIDU5KTsgZm9udC1mYW1pbHk6IOW+rui9r+mbhem7kSwgVmVyZGFuYSwgJnF1b3Q7TWljcm9z
b2Z0IFlhaGVpJnF1b3Q7LCBTaW1TdW4sIHNhbnMtc2VyaWY7IGZvbnQtdmFyaWFudC1udW1lcmlj
OiBub3JtYWw7IGZvbnQtdmFyaWFudC1lYXN0LWFzaWFuOiBub3JtYWw7IGxpbmUtaGVpZ2h0OiAy
Mi40cHg7IHdpZG93czogMTsiPjxicj48L2Rpdj48ZGl2IGlkPSJudGVzLXBjbWFjLXNpZ25hdHVy
ZSIgc3R5bGU9ImNvbG9yOiByZ2IoNDksIDUzLCA1OSk7IGZvbnQtZmFtaWx5OiDlvq7ova/pm4Xp
u5EsIFZlcmRhbmEsICZxdW90O01pY3Jvc29mdCBZYWhlaSZxdW90OywgU2ltU3VuLCBzYW5zLXNl
cmlmOyBmb250LXZhcmlhbnQtbnVtZXJpYzogbm9ybWFsOyBmb250LXZhcmlhbnQtZWFzdC1hc2lh
bjogbm9ybWFsOyBsaW5lLWhlaWdodDogMjIuNHB4OyB3aWRvd3M6IDE7Ij48ZGl2IHN0eWxlPSJw
YWRkaW5nOiAwcHg7IG1hcmdpbjogMHB4OyI+PGRpdiBzdHlsZT0icGFkZGluZy1ib3R0b206IDEw
cHg7IG1hcmdpbi1ib3R0b206IDEwcHg7IGRpc3BsYXk6IGlubGluZS1ibG9jazsiPjxkaXYgc3R5
bGU9Im91dGxpbmU6IDBweDsgY29sb3I6IHJnYig1MSwgNTEsIDUxKTsgZm9udC1mYW1pbHk6ICdN
aWNyb3NvZnQgWWFoZWknLCB2ZXJkYW5hOyBmb250LXNpemU6IDEycHg7Ij48Zm9udCBzaXplPSIy
IiBmYWNlPSLlrovkvZMiIHN0eWxlPSJsaW5lLWhlaWdodDogMS42OyI+5YiY5b+X5paH772cWmhp
d2VuIExpdTwvZm9udD48c3BhbiBzdHlsZT0ib3V0bGluZTogMHB4OyBmb250LWZhbWlseTog5a6L
5L2TOyBmb250LXNpemU6IHNtYWxsOyI+Jm5ic3A7PC9zcGFuPjwvZGl2PjxkaXYgc3R5bGU9Im91
dGxpbmU6IDBweDsgY29sb3I6IHJnYig1MSwgNTEsIDUxKTsgZm9udC1zaXplOiAxMnB4OyBmb250
LWZhbWlseTogVmVyZGFuYTsiPjxmb250IHNpemU9IjIiIGZhY2U9IuWui+S9kyIgc3R5bGU9Imxp
bmUtaGVpZ2h0OiAxLjY7Ij7miYvmnLrvvZxNb2JpbGU6Kzg2IDE1OTAxMDgyNjUxPC9mb250Pjwv
ZGl2PjxkaXYgc3R5bGU9Im91dGxpbmU6IDBweDsgY29sb3I6IHJnYig1MSwgNTEsIDUxKTsgZm9u
dC1zaXplOiAxMnB4OyBmb250LWZhbWlseTogVmVyZGFuYTsiPjxmb250IHNpemU9IjIiIGZhY2U9
IuWui+S9kyIgc3R5bGU9ImxpbmUtaGVpZ2h0OiAxLjY7Ij7muIXljY7lpKflrabvvZxUc2luZ2h1
YSBVbml2ZXJzaXR5PC9mb250PjwvZGl2PjwvZGl2PjwvZGl2PjwvZGl2Pg==
------=_Part_491550_1843797635.1574120139846--


From nobody Mon Nov 18 19:34:16 2019
Return-Path: <prvs=9226755b97=john.border@hughes.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 8449412084C for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 19:34:15 -0800 (PST)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=hughes.com header.b=kdLp/BMb; dkim=pass (1024-bit key) header.d=hughes.com header.b=olW1KIm8
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 FcixqgxMrC16 for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 19:34:13 -0800 (PST)
Received: from mx0b-00115402.pphosted.com (mx0b-00115402.pphosted.com [148.163.153.174]) (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 352E4120843 for <quic@ietf.org>; Mon, 18 Nov 2019 19:34:13 -0800 (PST)
Received: from pps.filterd (m0118427.ppops.net [127.0.0.1]) by mx0b-00115402.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id xAJ3VSai020352 for <quic@ietf.org>; Tue, 19 Nov 2019 03:34:12 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hughes.com; h=from : to : subject : date : message-id : content-type : mime-version; s=3152018; bh=L4C34HOxpNTXJFGPOpWKSqgQ1IgUS2xCbWUjj0WRoyU=; b=kdLp/BMbEi6eMAjNWbBA/6w21vgWGRRWiXO2K8H3YNqKPUArXCvnMJXEjuSsubNXeXvS C3e/d3p6lzZKmSOyPk683Y9DgIusN8pSQtqss2GiTaE5jRrzfO+IDXJeCYvKKcJZdYBF G0UrA78lrVKq1TupQvqTfv9GSEI35fMDHr0TAepXRRm7O/IUTZtZ8vhmgMeBwo6Mbb4h xmALgGouGWxuydojts8Fz6/nRR8UzDiS3SKnJTUgLPgjkt5WAofTnypa8WOkFjEt2bd9 NkxS7tKa62ZgThDdngcW2mnXMkW5E3JyRPb1Am2bV6bVTzcv7VS0609fB/lLSiUyxB03 eg== 
Received: from nam05-dm3-obe.outbound.protection.outlook.com (mail-dm3nam05lp2053.outbound.protection.outlook.com [104.47.49.53]) by mx0b-00115402.pphosted.com with ESMTP id 2wage3b6ke-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT) for <quic@ietf.org>; Tue, 19 Nov 2019 03:34:12 +0000
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=kQGZP4Jscn1MnUxhgvFZj6RUXSzLjBhe/BVZK+tQ8KfrabIDF/WbpfKMrpK9+ZHho+Hv0QSjePAEgGph3eVLDYqEtrPdGLFS1A8XhZwq6Z/lcxvXViomY/JmoPVNT68IDmRBSwInhgT1NcH6bb/NRBokmm6OE5UrOsIik8ClEybToMXM6qALyxUYcOunSPKYjWTtiSDwxWcECVBbfG15q3yQk7LGdRRgjco7y27vTLCGQkGjgx0bkbhsLGNrT3gykyrpvXwaCd/fRe+YnabXCy18aaO0AmEgs4QCc4wSCzzsV9UWH/9FBwPJ9sunnlSSj9bkYDW/QP3H+j6J1/Z0Fw==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com;  s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=L4C34HOxpNTXJFGPOpWKSqgQ1IgUS2xCbWUjj0WRoyU=; b=EdNfsQxFzbIqI1U7/j8kCyLzy2SvKO8006gLzK+6nUlykenroX7cfie27iDj4OHfBw2dteiYij+jGLUi04kmANFPYWtrBvHtZwlr8OBZsxl6mt4DFdEuhmQlR7FzczGUjbPaZSxzqbN+oMAZj+M8QAxv8loPFmN5HpuY+RubSYqoknZ5p2J/0eTN05ce8RsIBW43wm43sa9O4SEjuxJdlN9CX3xlDQcKNtFnSCy1i5v+x5e53bjVP+Dg6b1omln2ZA+Fc991BJ7hc+2jJQbuwM60ivWp5FxMzWZc2/9/8HgS5+Z68O4sJcOwTn+ysbo92qRLx3s87uxSGx0rpjaccg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=hughes.com; dmarc=pass action=none header.from=hughes.com; dkim=pass header.d=hughes.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=hughes.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=L4C34HOxpNTXJFGPOpWKSqgQ1IgUS2xCbWUjj0WRoyU=; b=olW1KIm85KP296EZ3s0gtkuuTyiGKlF6HZaX/w4bpIW9Z6Lj+55x4noLC9FzW7vyW7FTK3IKhdLnJFKfzXJQvwMExBJ+IHnPh6nAGCUCAt8yokvzVIRQn0Kw/flsLSW0WGRzCD/ueQFEEkXWjf4ezoWpunhS5h8XhVLgl6mZ67E=
Received: from BL0PR11MB3394.namprd11.prod.outlook.com (10.167.240.143) by BL0PR11MB3250.namprd11.prod.outlook.com (10.167.233.141) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.2451.23; Tue, 19 Nov 2019 03:34:08 +0000
Received: from BL0PR11MB3394.namprd11.prod.outlook.com ([fe80::39d2:ce7c:d144:a37f]) by BL0PR11MB3394.namprd11.prod.outlook.com ([fe80::39d2:ce7c:d144:a37f%6]) with mapi id 15.20.2451.031; Tue, 19 Nov 2019 03:34:08 +0000
From: "Border, John" <John.Border@hughes.com>
To: "quic@ietf.org" <quic@ietf.org>
Subject: What CSRs Do
Thread-Topic: What CSRs Do
Thread-Index: AdWeiLnP74voAASmTy29ATmkahTsZQ==
Date: Tue, 19 Nov 2019 03:34:08 +0000
Message-ID: <BL0PR11MB3394D769128DEFEEFBC3CA71904C0@BL0PR11MB3394.namprd11.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [139.85.223.11]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1421ebcd-2269-4776-eaa8-08d76ca155f6
x-ms-traffictypediagnostic: BL0PR11MB3250:
x-microsoft-antispam-prvs: <BL0PR11MB32507210EF8054A63BC390D5904C0@BL0PR11MB3250.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-forefront-prvs: 022649CC2C
x-forefront-antispam-report: SFV:NSPM; SFS:(10019020)(376002)(136003)(396003)(366004)(346002)(39860400002)(199004)(189003)(14444005)(256004)(186003)(5660300002)(74316002)(52536014)(476003)(26005)(102836004)(4744005)(25786009)(66946007)(6506007)(66556008)(66066001)(486006)(64756008)(66446008)(76116006)(33656002)(2351001)(66476007)(7696005)(790700001)(9686003)(3846002)(55016002)(3480700005)(54896002)(6306002)(6116002)(86362001)(6916009)(71200400001)(478600001)(71190400001)(2501003)(8676002)(2906002)(8936002)(7736002)(99286004)(316002)(6436002)(7116003)(5640700003)(1730700003)(81156014)(81166006)(14454004); DIR:OUT; SFP:1102; SCL:1; SRVR:BL0PR11MB3250; H:BL0PR11MB3394.namprd11.prod.outlook.com; FPR:; SPF:None; LANG:en; PTR:InfoNoRecords; A:1; MX:1; 
received-spf: None (protection.outlook.com: hughes.com does not designate permitted sender hosts)
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 3Knr3zHA6F+4tyrDC+tzd3xxNC0/+1qwmQCvVs7JX8gviizpArTlthblghnBUyMwFpe4iID+CD6NeBCu+jirwAhojg20BnLmLSR2GVNptfbb8vp4lWbTaEMqaRMe8ARkLjD/ff4Ll8OYxMpovugek/iw0tLdkPfL0Ym+HCMaItCKn+fg+HYicygQ/G/wq7qz1jQTCs6IUJwzDA62kNsNH16C67HcdmNh8EIS5UiUPXFgxBxnkcjs9D/I9zHV5DcNi/dlradxYfhPQ2CNQJi+yPFM9LGFns9N2Lt3L+qw1n4KPK1o3uz00hJ2lknp6Xg80vVfqqmowLD8O1nTxzbjXESYodAQuZGfnDLvbVg9/VH16opeGTzNhfq8pk4kMq3dW3fdq+L1Hgw39GSKZPnK1+yNCbUSzebTgodL5NI56ktZQBZOwg5MK8Rn0bnvQHYA
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_BL0PR11MB3394D769128DEFEEFBC3CA71904C0BL0PR11MB3394namp_"
MIME-Version: 1.0
X-OriginatorOrg: hughes.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 1421ebcd-2269-4776-eaa8-08d76ca155f6
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Nov 2019 03:34:08.1735 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 0e1f3187-4610-4ce2-bad1-b92f4ba36ab3
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: hZD4usROw4to+xVoLE73SF78yP/O0YsQbh2rs2zCuALPNVcyBSya9PxEPvyHwktTKyN0nvpYnJaWbmcYq2z4CQ==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR11MB3250
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-11-18_08:2019-11-15,2019-11-18 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 adultscore=0 malwarescore=0 phishscore=0 mlxscore=0 spamscore=0 lowpriorityscore=0 suspectscore=0 bulkscore=0 mlxlogscore=624 priorityscore=1501 clxscore=1011 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1911190029
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Gl7Hu28SY4s3veWogn4SFXIKCpQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Nov 2019 03:34:15 -0000

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


     I agree that it is too late to solve problems like troubleshooting pac=
ket loss for v1.  Plus, we want a good solution (which takes time).  But, w=
e need to solve this problem or it will impact QUICv1 deployment...

     When a customer calls reporting that an application does not work, the=
 Customer Service Representative is trained to do whatever it takes to fix =
the problem as quickly as possible.  Time on the phone equals money.  And, =
unhappy customers equal churn.  There is a lot of anecdotal learning involv=
ed with the troubleshooting process.  If the CSRs learn that disabling QUIC=
 fixes the problem (because the application falls back to TCP), eventually =
this will become the first thing that is tried every time.  Eventually, the=
ir supervisors will push for disabling it across the board.  Once disabled,=
 it is a lot of work to get it reenabled.


John


--_000_BL0PR11MB3394D769128DEFEEFBC3CA71904C0BL0PR11MB3394namp_
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:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:m=3D"http://schema=
s.microsoft.com/office/2004/12/omml" xmlns=3D"http://www.w3.org/TR/REC-html=
40">
<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;}
.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"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp;&nbsp; I agree that it is too late=
 to solve problems like troubleshooting packet loss for v1.&nbsp; Plus, we =
want a good solution (which takes time).&nbsp; But, we need to solve this p=
roblem or it will impact QUICv1 deployment&#8230;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&nbsp;&nbsp;&nbsp; &nbsp;When a customer calls repor=
ting that an application does not work, the Customer Service Representative=
 is trained to do whatever it takes to fix the problem as quickly as possib=
le.&nbsp; Time on the phone equals money.&nbsp; And, unhappy customers
 equal churn.&nbsp; There is a lot of anecdotal learning involved with the =
troubleshooting process.&nbsp; If the CSRs learn that disabling QUIC fixes =
the problem (because the application falls back to TCP), eventually this wi=
ll become the first thing that is tried every
 time.&nbsp; Eventually, their supervisors will push for disabling it acros=
s the board.&nbsp; Once disabled, it is a lot of work to get it reenabled.&=
nbsp; &nbsp;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">John<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_BL0PR11MB3394D769128DEFEEFBC3CA71904C0BL0PR11MB3394namp_--


From nobody Mon Nov 18 19:51:27 2019
Return-Path: <frodek@tele.no>
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 20659120048 for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 19:51:25 -0800 (PST)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tele.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 yTNOcktnTdJj for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 19:51:23 -0800 (PST)
Received: from gorgon.tele.no (gorgon.tele.no [IPv6:2001:700:800::70]) (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 C5272120044 for <quic@ietf.org>; Mon, 18 Nov 2019 19:51:22 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tele.no; s=20180731; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=TCitX3tS9l8iiOBgDiFQHGfxzhK14IjThgnRjgpUcyo=; b=aXJ7CAXBEqpfxzteTbix6d+/jX hinpjtqcIzvVBd9MOb90Ic6E5z4ozvP/4FpIVuMwnTDeiLYs4Y36pNFUnDki8MJzVi8liRqRdCuYL 1cV1SGtiMieTh20iEyw5S5KGw0UcktKKBB+mcLbQ1yemhBvQ7G9+HEdfw01p4HQmT7Xnd+OZ4/BHf mH0jTYmc8oDol+KAZUG/sQqEAhSyUVUUl/NfkpuHtSCL6ZsxgDhQDIlk0SRi0dOhU8CVauXZJFmyx 2qvOga/lww7w6kkJ79pncTQkzZoAU7agDre8NF16b5eE9H2QRWAQxIghqXQaZnU5l9y7S6UsSd781 YqtFngSQ==;
Received: from pilt1.tele.no ([2001:700:800::20] helo=[IPv6:::1]) by gorgon.tele.no with esmtp (Exim 4.92) (envelope-from <frodek@tele.no>) id 1iWuXt-0004Ss-PW; Tue, 19 Nov 2019 04:51:18 +0100
Subject: Re: What CSRs Do
To: "Border, John" <John.Border@hughes.com>, "quic@ietf.org" <quic@ietf.org>
References: <BL0PR11MB3394D769128DEFEEFBC3CA71904C0@BL0PR11MB3394.namprd11.prod.outlook.com>
From: Frode Kileng <frodek@tele.no>
Message-ID: <0cf4d3ad-0f64-0ae4-2d95-77a39f40639d@tele.no>
Date: Tue, 19 Nov 2019 04:51:14 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <BL0PR11MB3394D769128DEFEEFBC3CA71904C0@BL0PR11MB3394.namprd11.prod.outlook.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/gpQDSrFrXZ1RoGjLzfMEnhsIufY>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Nov 2019 03:51:25 -0000

On 19/11/2019 04:34, Border, John wrote:
>
> Â Â Â Â  I agree that it is too late to solve problems like 
> troubleshooting packet loss for v1.Â  Plus, we want a good solution 
> (which takes time).Â  But, we need to solve this problem or it will 
> impact QUICv1 deploymentâ€¦
>
> Â Â Â  Â When a customer calls reporting that an application does not 
> work, the Customer Service Representative is trained to do whatever it 
> takes to fix the problem as quickly as possible.Â  Time on the phone 
> equals money.Â  And, unhappy customers equal churn.Â  There is a lot of 
> anecdotal learning involved with the troubleshooting process. If the 
> CSRs learn that disabling QUIC fixes the problem (because the 
> application falls back to TCP), eventually this will become the first 
> thing that is tried every time. Eventually, their supervisors will 
> push for disabling it across the board.Â  Once disabled, it is a lot of 
> work to get it reenabled.
>
I do think this exemplifies that some network operators have operational 
practices they want to preserve and requests "packet loss" signal 
support in v1. Other operators use alternative operational practices. 
Should the WGÂ  make efforts to contribute to preserving current 
practices of some network operators?

Frode



From nobody Mon Nov 18 20:29:14 2019
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 29A5712081A for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 20:29:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 DD5nwds3Lc8a for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 20:29:11 -0800 (PST)
Received: from 1wt.eu (wtarreau.pck.nerim.net [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id AC5E212008A for <quic@ietf.org>; Mon, 18 Nov 2019 20:29:10 -0800 (PST)
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id xAJ4T463005686; Tue, 19 Nov 2019 05:29:04 +0100
Date: Tue, 19 Nov 2019 05:29:04 +0100
From: Willy Tarreau <w@1wt.eu>
To: Frode Kileng <frodek@tele.no>
Cc: "Border, John" <John.Border@hughes.com>, "quic@ietf.org" <quic@ietf.org>
Subject: Re: What CSRs Do
Message-ID: <20191119042904.GC5602@1wt.eu>
References: <BL0PR11MB3394D769128DEFEEFBC3CA71904C0@BL0PR11MB3394.namprd11.prod.outlook.com> <0cf4d3ad-0f64-0ae4-2d95-77a39f40639d@tele.no>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <0cf4d3ad-0f64-0ae4-2d95-77a39f40639d@tele.no>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2rtHlpuIpjkegE1Dr1o5nt0MkP8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Nov 2019 04:29:13 -0000

On Tue, Nov 19, 2019 at 04:51:14AM +0100, Frode Kileng wrote:
> 
> On 19/11/2019 04:34, Border, John wrote:
> > 
> >      I agree that it is too late to solve problems like troubleshooting
> > packet loss for v1.  Plus, we want a good solution (which takes time). 
> > But, we need to solve this problem or it will impact QUICv1
> > deployment...
> > 
> >      When a customer calls reporting that an application does not work,
> > the Customer Service Representative is trained to do whatever it takes
> > to fix the problem as quickly as possible.  Time on the phone equals
> > money.  And, unhappy customers equal churn.  There is a lot of anecdotal
> > learning involved with the troubleshooting process. If the CSRs learn
> > that disabling QUIC fixes the problem (because the application falls
> > back to TCP), eventually this will become the first thing that is tried
> > every time. Eventually, their supervisors will push for disabling it
> > across the board.  Once disabled, it is a lot of work to get it
> > reenabled.
> > 
> I do think this exemplifies that some network operators have operational
> practices they want to preserve and requests "packet loss" signal support in
> v1. Other operators use alternative operational practices.

The only known alternative is to claim "we have no loss here" and point the
finger at the next step in the chain operated by someone else. Actually
this is already what incompetent operators do, hence the common need for
captures to know whether everything is OK at one point or not. Usually
this has to be done within the operator's infrastructure once others
around managed to prove that something is already missing on their side.

> Should the WG 
> make efforts to contribute to preserving current practices of some network
> operators?

It will depend how long some operators will want to troubleshoot the issues
before claiming the protocol doesn't work :-/  Worse, since the network stack
will be implemented in browsers and servers, they will simply point the
fingers at these components, proving that just changing them (hence the
protocol as well) solves the issue. My personal take on this has been
expressed many times, which is that network must be observable if you want
to fix it, otherwise it degrades by itself till a point of poor quality
that "works enough" for most users (e.g. public WiFi access points). Things
as simple as detecting packet reordering caused by multiple paths is trivial
at the TCP level, it's way harder when you cannot say what the packet is
about.

> Frode

Willy


From nobody Mon Nov 18 21:57:16 2019
Return-Path: <frodeki@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 94CF3120801 for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 21:57:14 -0800 (PST)
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_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 bpbYedeZhMfw for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 21:57:12 -0800 (PST)
Received: from mail-pl1-x629.google.com (mail-pl1-x629.google.com [IPv6:2607:f8b0:4864:20::629]) (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 2C795120046 for <quic@ietf.org>; Mon, 18 Nov 2019 21:57:12 -0800 (PST)
Received: by mail-pl1-x629.google.com with SMTP id az9so11145645plb.11 for <quic@ietf.org>; Mon, 18 Nov 2019 21:57:12 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=zJtEqTO7GC43oJvbpUgxkumHXB6RxC86xdSXcOZXhj8=; b=D3+R1eW96UtDhxeN0yqV0fLrXLYtGz+HvSXBynXznhnRAOC2z+pJnQYMUG40DuiqPt 2OSyHqSucj05rellaMtOMQXzVb0Md2Y+mDfUjUa4LWQGOPs4jHaYMAuYmt/xz+QVwfKB nQGcNPcE/syWThCM9Ro/sFX4LLcBETizkM1mqvo9WsSLU5q0XM7Fu1jtm4Aycg2Mh/eo 9MqLTYOg8hr9pYdWGQl9MKP18KObxG1mpCpRTWa/QsdrOrju3bfBU8SwZZznMvpndDmx lSvDuOu9pZzFDVUqcnifaR1QcJOMYRy/IN8JcceOVf/5zw8Muo7anP6PCVph7FIOc7+n ypjg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=zJtEqTO7GC43oJvbpUgxkumHXB6RxC86xdSXcOZXhj8=; b=FMZ3A4fudAQ94YDayodpI/kNMXRk0mxekWoV7F3d2kZsG9sCVm1qEkEdEVNHdSWJzM X/phliYT8pvfmb4/BIFUgzHelOV4LtDsIhwveze/gynhNqyGTw8Ek25FKCYN/VMRwT8z SNY7oGYSU0jh4DYCtzZcdCVzrAyiYXGUBh27a1h4vIqkCtbFTC+JzSnu+dLn64KJtml5 TeIay9VYc1y/80CLDanWOnF1dBbtYTwJHlNOUPl8Dq1VqEj+5h1R7FH0ekCwc9E2yQAZ 9+SbrCpzvyg3RCpHg4c2TfCnPxFMCGdUIdQ3RO0huXHWoXvNXWMXMFPWp44zvI+0tszY IRYQ==
X-Gm-Message-State: APjAAAW4zWla5m5EVBC+AOTHmikUtB5x9LIbaEzh9aDPWXfuGtniABME C2Pp6Kx6Dxe7L3bUgL4QXIFChtQ4
X-Google-Smtp-Source: APXvYqyn2pLkAiZNFyMpS959+HyPPimBLu6uqtsA3xMVd/I/6uTbSF23ytjQC8QTOGio3geZc+BD0w==
X-Received: by 2002:a17:902:74c6:: with SMTP id f6mr33674062plt.167.1574143031151;  Mon, 18 Nov 2019 21:57:11 -0800 (PST)
Received: from ?IPv6:2001:67c:370:128:deb:727b:9d2c:94c1? ([2001:67c:370:128:deb:727b:9d2c:94c1]) by smtp.googlemail.com with ESMTPSA id c9sm25493105pfb.114.2019.11.18.21.57.09 for <quic@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 18 Nov 2019 21:57:10 -0800 (PST)
Subject: Re: What CSRs Do
To: quic@ietf.org
References: <BL0PR11MB3394D769128DEFEEFBC3CA71904C0@BL0PR11MB3394.namprd11.prod.outlook.com> <0cf4d3ad-0f64-0ae4-2d95-77a39f40639d@tele.no> <20191119042904.GC5602@1wt.eu>
From: Frode Kileng <frodeki@gmail.com>
Message-ID: <4003626d-8966-6772-7df0-e76549320430@gmail.com>
Date: Tue, 19 Nov 2019 06:57:07 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <20191119042904.GC5602@1wt.eu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ejHl4v7S-56hhd94e9hQ2sb7Pyo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Nov 2019 05:57:15 -0000

On 19/11/2019 05:29, Willy Tarreau wrote:
>
> The only known alternative is to claim "we have no loss here" and point the
> finger at the next step in the chain operated by someone else.

What additional value can "loss bit(s)" provide beyond confirming that 
the source is within your network domain or somewhere else, i.e. 
information that is available from other "loss sources". How would 
network operators use this loss bit(s) signal when providing such 
"excellent customer support" when the problem source is external?

frodek




From nobody Mon Nov 18 22:26:15 2019
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 5EAC2120872 for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 22:26:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.701
X-Spam-Level: 
X-Spam-Status: No, score=-2.701 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=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 hxUh7BSmr8R9 for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 22:26:11 -0800 (PST)
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 1F0D6120834 for <quic@ietf.org>; Mon, 18 Nov 2019 22:25:59 -0800 (PST)
Received: from pps.filterd (m0050102.ppops.net [127.0.0.1]) by m0050102.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id xAJ6PSI7007189; Tue, 19 Nov 2019 06:25:55 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=jan2016.eng; bh=2wvM+kD2Qz0s80aNk2IZ03DENgqj5h+glbkEPG/yOBk=; b=kdoI4ScFopP5SJdCvhheZDNLIW2Z1HLAIGzaQvGnRiUPFIGrwZggHDuspHQhFWo7C9Ln 8h/vjZPR0nirHfuqm/PZaK2dyGtCKvYJbngQJntNH5/YvY/aQ4mUPzCgRvGvxpIbx4Dq /wHGps7WlDCktsx474FGdhaD3jejqinRHn7OUx0h2xF9dyW8PSVpdYWOuqZl9hde8tvQ /bwirylFQJC/U2cvXumtEvbSyBpzrcSItk80r0gocGg97rxzkR7WCT7ri1dn1fD7S5DQ p97tXljtBW89EFo0bduYOj3nt3SV4sUwWmWzT+deh9l6UU/jQhqtmkOfTOQE2w6jcklF UQ== 
Received: from prod-mail-ppoint7 (prod-mail-ppoint7.akamai.com [96.6.114.121] (may be forged)) by m0050102.ppops.net-00190b01. with ESMTP id 2wafywc2an-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 19 Nov 2019 06:25:54 +0000
Received: from pps.filterd (prod-mail-ppoint7.akamai.com [127.0.0.1]) by prod-mail-ppoint7.akamai.com (8.16.0.27/8.16.0.27) with SMTP id xAJ6HF3A016534; Tue, 19 Nov 2019 01:25:54 -0500
Received: from email.msg.corp.akamai.com ([172.27.165.112]) by prod-mail-ppoint7.akamai.com with ESMTP id 2wadb3r4e5-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 19 Nov 2019 01:25:53 -0500
Received: from USTX2EX-DAG1MB5.msg.corp.akamai.com (172.27.165.123) by ustx2ex-dag1mb3.msg.corp.akamai.com (172.27.165.121) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 19 Nov 2019 00:25:52 -0600
Received: from USTX2EX-DAG1MB5.msg.corp.akamai.com ([172.27.165.123]) by ustx2ex-dag1mb5.msg.corp.akamai.com ([172.27.165.123]) with mapi id 15.00.1473.005; Tue, 19 Nov 2019 00:25:52 -0600
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: Frode Kileng <frodeki@gmail.com>, "quic@ietf.org" <quic@ietf.org>
Subject: Re: What CSRs Do
Thread-Topic: What CSRs Do
Thread-Index: AdWeiLnP74voAASmTy29ATmkahTsZQANieYAAAFSQgAAAxM6gP//nbXW
Date: Tue, 19 Nov 2019 06:25:51 +0000
Message-ID: <1574144751435.15844@akamai.com>
References: <BL0PR11MB3394D769128DEFEEFBC3CA71904C0@BL0PR11MB3394.namprd11.prod.outlook.com> <0cf4d3ad-0f64-0ae4-2d95-77a39f40639d@tele.no> <20191119042904.GC5602@1wt.eu>, <4003626d-8966-6772-7df0-e76549320430@gmail.com>
In-Reply-To: <4003626d-8966-6772-7df0-e76549320430@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.218.207]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-11-19_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=443 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140001 definitions=main-1911190057
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-11-19_01:2019-11-15,2019-11-19 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 priorityscore=1501 malwarescore=0 bulkscore=0 spamscore=0 phishscore=0 adultscore=0 lowpriorityscore=0 suspectscore=0 clxscore=1011 mlxscore=0 mlxlogscore=415 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1911190058
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ngnZBUVA9-pWBVmI7gL-WXR4g3I>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Nov 2019 06:26:13 -0000

On Tue, Nov 19, 2019 at 12:57 AM, Frode Kileng <frodeki@gmail.com> wrote:=
=0A=
> On 19/11/2019 05:29, Willy Tarreau wrote:=0A=
>>=0A=
>> The only known alternative is to claim "we have no loss here" and point =
the=0A=
>> finger at the next step in the chain operated by someone else.=0A=
>=0A=
> What additional value can "loss bit(s)" provide beyond confirming that=0A=
> the source is within your network domain or somewhere else, i.e.=0A=
> information that is available from other "loss sources".=0A=
> How would network operators use this loss bit(s) signal when providing su=
ch=0A=
> "excellent customer support" when the problem source is external?=0A=
=0A=
This is assuming there is a robust set of "other 'loss source'" available. =
This is far from reality for the vast majority of cases.=0A=
=0A=
Also, the loss bits(s) would allow one to determine whether the loss is ups=
tream or downstream.  That would allow you to know "whom do you call".  I.e=
. is the loss in your transit or peer? Is it in the user's own home WiFi ne=
twork?  Or is it really in your network?=0A=
=0A=
In general, it is important to keep in mind that we live in the world as it=
 "is" and not in a world as it "should be".  I know little of ISP tech supp=
ort business, but if ISPs says they have no other tools, I believe that the=
y have no other tools currently. We can to encourage change, but if you pus=
h too hard, the reality has a way of pushing back.=0A=
=0A=
> frodek=0A=
=0A=
- Igor=


From nobody Mon Nov 18 22:42:17 2019
Return-Path: <frodek@tele.no>
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 7912D1200A4 for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 22:42:15 -0800 (PST)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tele.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 KWqH3eHgyzYw for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 22:42:14 -0800 (PST)
Received: from gorgon.tele.no (gorgon.tele.no [IPv6:2001:700:800::70]) (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 0F6D7120876 for <quic@ietf.org>; Mon, 18 Nov 2019 22:42:14 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tele.no; s=20180731; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=AOJrLZ2ZR811zJjBO+xhBxpicgWp1pcOojdsNitNyvs=; b=JRrxh0ZdimHXiV+TFWwVY6Hn+L yXaXoW3A1To2NL7wFwTeqYNVGa9qlquIzDxTAP7BCDm1n4j0bMBmIuBVQ+Sz4Qpc3Lpd++ypHGgtr pR6+l9f4X6GogNm1ElRd4yz6Qb5lelYaQNYZ3fw9OeYqdJ/1RthgI5jryVGqS2NjboF+tDc10OyT5 ksxZtODfFGFc4dyxDUaVGRKejOv8psC6gGo2xjQJFlDEdQw1QoaAc84zlWtBwTcwvY4eWoaEx7/qV KtewRq69NG5KhfM9IsbB2DB7Sf2NnGJXkyEnpRWQlZIt6H3Cp3ZnlDh3wH6zxyyieJRKtV/46B4/Z t9mG8cJA==;
Received: from pilt1.tele.no ([2001:700:800::20] helo=[127.0.0.1]) by gorgon.tele.no with esmtp (Exim 4.92) (envelope-from <frodek@tele.no>) id 1iWxDH-0004gm-KT for quic@ietf.org; Tue, 19 Nov 2019 07:42:12 +0100
Subject: Re: What CSRs Do
To: quic@ietf.org
References: <BL0PR11MB3394D769128DEFEEFBC3CA71904C0@BL0PR11MB3394.namprd11.prod.outlook.com> <0cf4d3ad-0f64-0ae4-2d95-77a39f40639d@tele.no> <20191119042904.GC5602@1wt.eu> <4003626d-8966-6772-7df0-e76549320430@gmail.com> <1574144751435.15844@akamai.com>
From: Frode Kileng <frodek@tele.no>
Message-ID: <bc0cf83f-16d6-3200-5d6e-091311ccf9a7@tele.no>
Date: Tue, 19 Nov 2019 07:42:08 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <1574144751435.15844@akamai.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/xz9Saou6lrN0t3sVj9q2JkN9hGI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Nov 2019 06:42:15 -0000

On 19/11/2019 07:25, Lubashev, Igor wrote:
>
> This is assuming there is a robust set of "other 'loss source'" available. This is far from reality for the vast majority of cases.

So then there's two alternatives: a) Standardize a "loss-signal" option 
in QUIC and hope this is implemented and supported. b) Network operators 
lacking a "robust set of other loss sources" obtain such sources.

frodek



From nobody Mon Nov 18 23:03:36 2019
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 3DF81120BA7 for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 23:03:09 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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=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 ylSJ8cmvKwym for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 23:03:03 -0800 (PST)
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 94058120927 for <quic@ietf.org>; Mon, 18 Nov 2019 23:03:03 -0800 (PST)
Received: from pps.filterd (m0122330.ppops.net [127.0.0.1]) by mx0b-00190b01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id xAJ71ONN012128; Tue, 19 Nov 2019 07:03:00 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=jan2016.eng; bh=+122sFy13GyP78ObSf1/6808AJIsfC/9W1eBs31KK0I=; b=Bzr4RYLkr5PCZ0OC8hitmHxetsFCr+iCKJgwLpMOFTqbZLuO0QaoVfANH7gpC6mPTCE6 K3v5WvuIwr5yqIwc2PAD/ngPT9M7/gaZP7nP622vdy3SLwiXPfXgfywJkTHGMe2vpY8Z gU87hjEw5UB+5IuG1c/bvhJK7Ew8vNOW9WQTBIwxUl0JQQ+DDllRFwn4axpwEhDy6Eip rZGsvg41mxrWUyPohzz6SIQIasGia6y9YXn4IYv4O5wHej/sKpwTLjQAA05KEwIAg8hQ hOcTSXaX13rBnwku7RzTAdjtCRmyVlSfU4PkMSMCLnbgzlsIegi3We+ehbVOct6D5Yrg qA== 
Received: from prod-mail-ppoint3 (prod-mail-ppoint3.akamai.com [96.6.114.86] (may be forged)) by mx0b-00190b01.pphosted.com with ESMTP id 2wag31km25-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 19 Nov 2019 07:02:59 +0000
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.27/8.16.0.27) with SMTP id xAJ72RF9013275; Tue, 19 Nov 2019 02:02:59 -0500
Received: from email.msg.corp.akamai.com ([172.27.165.114]) by prod-mail-ppoint3.akamai.com with ESMTP id 2wadb1a43f-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 19 Nov 2019 02:02:59 -0500
Received: from USTX2EX-DAG1MB5.msg.corp.akamai.com (172.27.165.123) by ustx2ex-dag1mb5.msg.corp.akamai.com (172.27.165.123) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 19 Nov 2019 01:02:58 -0600
Received: from USTX2EX-DAG1MB5.msg.corp.akamai.com ([172.27.165.123]) by ustx2ex-dag1mb5.msg.corp.akamai.com ([172.27.165.123]) with mapi id 15.00.1473.005; Tue, 19 Nov 2019 01:02:58 -0600
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: Frode Kileng <frodek@tele.no>, "quic@ietf.org" <quic@ietf.org>
Subject: RE: What CSRs Do
Thread-Topic: What CSRs Do
Thread-Index: AdWeiLnP74voAASmTy29ATmkahTsZQANieYAAAFSQgAAAxM6gP//nbXWgABu3gCAAGD/EA==
Date: Tue, 19 Nov 2019 07:02:57 +0000
Message-ID: <c73b86c40c574ad099d7245a2b5712da@ustx2ex-dag1mb5.msg.corp.akamai.com>
References: <BL0PR11MB3394D769128DEFEEFBC3CA71904C0@BL0PR11MB3394.namprd11.prod.outlook.com> <0cf4d3ad-0f64-0ae4-2d95-77a39f40639d@tele.no> <20191119042904.GC5602@1wt.eu> <4003626d-8966-6772-7df0-e76549320430@gmail.com> <1574144751435.15844@akamai.com> <bc0cf83f-16d6-3200-5d6e-091311ccf9a7@tele.no>
In-Reply-To: <bc0cf83f-16d6-3200-5d6e-091311ccf9a7@tele.no>
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.218.207]
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=2019-11-19_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=381 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140001 definitions=main-1911190065
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-11-19_01:2019-11-15,2019-11-19 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 priorityscore=1501 malwarescore=0 mlxlogscore=352 adultscore=0 mlxscore=0 bulkscore=0 lowpriorityscore=0 clxscore=1011 spamscore=0 phishscore=0 impostorscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1911190064
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/8be6keIfFatHm27bc8HHokMNIiU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Nov 2019 07:03:12 -0000

PiBPbiBUdWUsIE5vdiAxOSwgMjAxOSBhdCAyOjQyIFBNLCBGcm9kZSBLaWxlbmcgPGZyb2Rla0B0
ZWxlLm5vPiB3cm90ZToNCj4gDQo+IE9uIDE5LzExLzIwMTkgMDc6MjUsIEx1YmFzaGV2LCBJZ29y
IHdyb3RlOg0KPiA+DQo+ID4gVGhpcyBpcyBhc3N1bWluZyB0aGVyZSBpcyBhIHJvYnVzdCBzZXQg
b2YgIm90aGVyICdsb3NzIHNvdXJjZSciIGF2YWlsYWJsZS4gVGhpcyBpcw0KPiBmYXIgZnJvbSBy
ZWFsaXR5IGZvciB0aGUgdmFzdCBtYWpvcml0eSBvZiBjYXNlcy4NCj4gDQo+IFNvIHRoZW4gdGhl
cmUncyB0d28gYWx0ZXJuYXRpdmVzOiBhKSBTdGFuZGFyZGl6ZSBhICJsb3NzLXNpZ25hbCIgb3B0
aW9uIGluIFFVSUMNCj4gYW5kIGhvcGUgdGhpcyBpcyBpbXBsZW1lbnRlZCBhbmQgc3VwcG9ydGVk
LiBiKSBOZXR3b3JrIG9wZXJhdG9ycyBsYWNraW5nIGENCj4gInJvYnVzdCBzZXQgb2Ygb3RoZXIg
bG9zcyBzb3VyY2VzIiBvYnRhaW4gc3VjaCBzb3VyY2VzLg0KDQpJIGRvIG5vdCB0aGluayB0aGVz
ZSBhcmUgY29uZmxpY3RpbmcgYWx0ZXJuYXRpdmVzLiAgSSBhbSBzdXJlIHZlbmRvcnMgd2lsbCB0
cnkgdG8gaW52ZW50IG5ldyB0b29scywgd2hpY2ggaXMgZ3JlYXQuDQoNCkFzIGZvciBsb3NzLXNp
Z25hbCAoYXMgd2VsbCBhcyBkZWxheSBzaWduYWwpLCB0aGVzZSBhcmUgZGVmaW5pdGVseSAiZXhw
ZXJpbWVudGFsIiBmZWF0dXJlcy4gVGhlcmUgYXJlIG1hbnkgZmVhdHVyZXMgdGhhdCBJRVRGIHN0
YW5kYXJkaXplZCBhbmQgbmV2ZXIgZ290IHdpZGVzcHJlYWQgYWRvcHRpb24uIFRoZSBiZW5lZml0
IG9mIFFVSUMgaXMgdGhhdCBpdCBsb29rcyBwb2lzZWQgZm9yIGEgcXVpY2sgcHJvdG9jb2wgZXZv
bHV0aW9uLiBJZiBhIGZlYXR1cmUgZ2FpbnMgd2lkZXNwcmVhZCBzdXBwb3J0LCBpdCB3b3VsZCBy
ZW1haW47IGlmIG5vdCwgaXQgd291bGQgbm90IG1ha2UgYSBmdXR1cmUgUVVJQyB2ZXJzaW9uIGFu
ZCB0aGUgYml0cyBvY2N1cGllZCBieSBsb3NzLSBhbmQgZGVsYXktIGJpdHMgd291bGQgYmUgcmV1
c2VkIGZvciBzb21ldGhpbmcgZWxzZS4NCg0KPiBmcm9kZWsNCg0KLSBJZ29yDQo=


From nobody Mon Nov 18 23:32:30 2019
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 27B29120089 for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 23:32:29 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 946Ftkzjti4z for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 23:32:26 -0800 (PST)
Received: from 1wt.eu (wtarreau.pck.nerim.net [62.212.114.60]) by ietfa.amsl.com (Postfix) with ESMTP id 0D6A612088B for <quic@ietf.org>; Mon, 18 Nov 2019 23:32:25 -0800 (PST)
Received: (from willy@localhost) by pcw.home.local (8.15.2/8.15.2/Submit) id xAJ7WKFg005890; Tue, 19 Nov 2019 08:32:20 +0100
Date: Tue, 19 Nov 2019 08:32:20 +0100
From: Willy Tarreau <w@1wt.eu>
To: Frode Kileng <frodeki@gmail.com>
Cc: quic@ietf.org
Subject: Re: What CSRs Do
Message-ID: <20191119073220.GA5824@1wt.eu>
References: <BL0PR11MB3394D769128DEFEEFBC3CA71904C0@BL0PR11MB3394.namprd11.prod.outlook.com> <0cf4d3ad-0f64-0ae4-2d95-77a39f40639d@tele.no> <20191119042904.GC5602@1wt.eu> <4003626d-8966-6772-7df0-e76549320430@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4003626d-8966-6772-7df0-e76549320430@gmail.com>
User-Agent: Mutt/1.6.1 (2016-04-27)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/xhxWF7rqZ9gNi-VaKuiHBpiJ788>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Nov 2019 07:32:29 -0000

On Tue, Nov 19, 2019 at 06:57:07AM +0100, Frode Kileng wrote:
> On 19/11/2019 05:29, Willy Tarreau wrote:
> > 
> > The only known alternative is to claim "we have no loss here" and point the
> > finger at the next step in the chain operated by someone else.
> 
> What additional value can "loss bit(s)" provide beyond confirming that the
> source is within your network domain or somewhere else, i.e. information
> that is available from other "loss sources". How would network operators use
> this loss bit(s) signal when providing such "excellent customer support"
> when the problem source is external?

I find your condescending tone inappropriate to discuss technical matters.

But since you asked, when I'm invited to troubleshooting sessions when
people experience issues ranging from "seems slow" to "sometimes hangs"
on TCP, I look at IP+ports, sequence numbers, ACK numbers, flags, window
sizes, timestamps and SACK fields, to figure what's happening. It just
happens that in QUIC all of them except IP+ports are encrypted, which
basically means my only solution will be to ask people "does it still
happen when you block UDP port 443?". And that's really sad. Network
issues are never white-or-black. Large buffers in VM environments cause
retransmits without losses, resulting in apparent loss on one side and
duplicate on the other one. Packets can get corrupted on their way from
one side to the other one, and guess what ? Some devices even manage to
reconstruct a valid checksum, but from inspection you cannot tell whether
the packet is OK or not. Some packets can be dropped past a certain size
(typical problem of PPPoE whose encapsulation takes 8 bytes), resulting
in only full packets not to be delivered. On the side experiencing the
miss, usually you immediately spot this thanks to the sequence number as
you notice a hole of 1460 bytes. Here you still see packets coming but
you don't know anything about them so you can just guess. Did you know
that you can even lose packets between two processes on the loopback
under sustained load ?

Debuggability is a key to any protocol's health. The vast majority of
the fixes that go into any network stack come from observations in the
field resulting in captures exhibiting a bad behavior. Here such captures
will never exist so there will be nothing to fix. This is still what I
really do not like at all in this way of designing a protocol.

Just my two cents,
Willy


From nobody Mon Nov 18 23:44:27 2019
Return-Path: <frodek@tele.no>
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 71E1512087C for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 23:44:26 -0800 (PST)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=tele.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 4_3G6BPbt9TK for <quic@ietfa.amsl.com>; Mon, 18 Nov 2019 23:44:24 -0800 (PST)
Received: from gorgon.tele.no (gorgon.tele.no [IPv6:2001:700:800::70]) (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 8552A12084A for <quic@ietf.org>; Mon, 18 Nov 2019 23:44:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=tele.no; s=20180731; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:To:Subject:Sender:Reply-To:Cc:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=zGx50eJW2O6+cNETe6a88pkXKJMFJTQuRoCyUR+FJyI=; b=Wo9p0v4s+APFcQxNa4YlKZq6rn nLYxpoX7uYtFb2hShWHVojR98H4bCqzzTYx8tz8oryiPvBiAOUE1H3mqMRhQpRiLQWgevtmv98Utv Fjq8K87adgqwwBNjqCVjeI7ZKYFrM+juGM4PdlCGmPR1AhT/tFm0MgT9B/qtgFp5hphy37NzWlh4P vHmbNCBPUmTz5zUba2xxsvQnnxNncf8lQdfYuH/6qGa6BmJ+EJZQfyl2AtjRFCuXYYnekAfU3UtYn 3tECITJpnOvOTS+FEOaJDPiBU+Li3Qh8DMBlY8HZKjjA8e4rLgWpwZYefhr2aL+g7OQh+GkJim79Q 8oOJ6fMw==;
Received: from pilt1.tele.no ([2001:700:800::20] helo=[127.0.0.1]) by gorgon.tele.no with esmtp (Exim 4.92) (envelope-from <frodek@tele.no>) id 1iWyBQ-0004ic-Tc; Tue, 19 Nov 2019 08:44:21 +0100
Subject: Re: What CSRs Do
To: quic@ietf.org, w@1wt.eu
References: <BL0PR11MB3394D769128DEFEEFBC3CA71904C0@BL0PR11MB3394.namprd11.prod.outlook.com> <0cf4d3ad-0f64-0ae4-2d95-77a39f40639d@tele.no> <20191119042904.GC5602@1wt.eu> <4003626d-8966-6772-7df0-e76549320430@gmail.com> <20191119073220.GA5824@1wt.eu>
From: Frode Kileng <frodek@tele.no>
Message-ID: <f40867ba-37ba-1be9-a00b-e61dfb23187e@tele.no>
Date: Tue, 19 Nov 2019 08:44:17 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <20191119073220.GA5824@1wt.eu>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7jTflU24Q25it976ryC1bfUtE0w>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Nov 2019 07:44:26 -0000

On 19/11/2019 08:32, Willy Tarreau wrote:
> On Tue, Nov 19, 2019 at 06:57:07AM +0100, Frode Kileng wrote:
>> On 19/11/2019 05:29, Willy Tarreau wrote:
>>> The only known alternative is to claim "we have no loss here" and point the
>>> finger at the next step in the chain operated by someone else.
>> What additional value can "loss bit(s)" provide beyond confirming that the
>> source is within your network domain or somewhere else, i.e. information
>> that is available from other "loss sources". How would network operators use
>> this loss bit(s) signal when providing such "excellent customer support"
>> when the problem source is external?
> I find your condescending tone inappropriate to discuss technical matters.

I'm very surprised as this was questions I asked trying to understand 
the benefits of the loss bit(s). As a non-native speaker, and after 
having lookedÂ  up the word "condescending", I understand that I should 
avoid further discussion on this topic in fear of being misinterpreted.

frodek






From nobody Tue Nov 19 06:32:29 2019
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 4D307120934 for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 06:32:27 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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=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 hUAgn2OQFCC6 for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 06:32:25 -0800 (PST)
Received: from mail-qt1-x832.google.com (mail-qt1-x832.google.com [IPv6:2607:f8b0:4864:20::832]) (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 F24601200B1 for <quic@ietf.org>; Tue, 19 Nov 2019 06:32:24 -0800 (PST)
Received: by mail-qt1-x832.google.com with SMTP id r20so24737705qtp.13 for <quic@ietf.org>; Tue, 19 Nov 2019 06:32:24 -0800 (PST)
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=eOBDoCw1ux/stOgnbE7riNx4dhTdeTaMBDt8DrzyrZ4=; b=XknWf3JUgYcRJ//uIGzTZgkp9Bo7kd0lN1kWyGUf9rTbeCOa/4Wx8gYkx1IzrC0UyB lHkLacYgOhbBfsWcMly9bqT84bXJUUgFHPEjjc7UMNp2WHyfFW5bm1YgEWyrEalr9B1H D+ivI5je0ajk9Mxei5FafItCsSj8of9JR8H3XmUS8RN066FazECOG9kvkzNCBiULOo3W OPzXZYfCPw4k7hQK97pxRfFrBPD+qMGkBGWaUF3yIf0fO5l0ccQnwdXFk/KTtPTyGzvp aReiRFUaQa+g5IMHO00k6HKuSxAkdgul0lveDgTFpQ4qrMNK3E7i8/C3DIzUzmYW5Jke 8uLA==
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=eOBDoCw1ux/stOgnbE7riNx4dhTdeTaMBDt8DrzyrZ4=; b=chonvhSkW2X3Ky/1WTJIBOniXo3KtkWuQ5v9+tmd/labW3Wq0/oyEeDHvHmsAs1H9q k6h9Xdd1i1C4TavZC6+tNBGTA6sDWNDsorpVYKpH9FHo4TP+wllLQui3qVRXDkJ24NLl LoEcHy0p4akvujI8ZQndbYLhQISzmSeedwhpeKXZoeEVCqmgLNLyKwMWHbdYWSa8g6yc ggZxBfiRWOJIA37Ilk5pTrSBfjQqVuq8dn7tr1/NP18PCLW9GjpkXIOuonrTMQZ8GLVN WxFQAsAoavuBqb9MUE6yjrmfNdlyY1lZdzlMtG8EmkPvgBqdf6VbAmeudaMaNFfi3aa9 nsHQ==
X-Gm-Message-State: APjAAAU8nuXjbNHSAkZP9FE4Dj9EGqxbSC5s6Qm7PeYeuKZPhESweoGG MI8b5Sy/eeXpbYIbT53W2jkhIf3+ypk=
X-Google-Smtp-Source: APXvYqwRhmlWIuFWV3uWzctrxPiAxOdDOfViFNSdsmtW+wcP/dBznUMdWMHZII+SR5XdGrvoQtohPQ==
X-Received: by 2002:ac8:6bd9:: with SMTP id b25mr29269859qtt.295.1574173943866;  Tue, 19 Nov 2019 06:32:23 -0800 (PST)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id z17sm11595959qtq.69.2019.11.19.06.32.23 for <quic@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Nov 2019 06:32:23 -0800 (PST)
Date: Tue, 19 Nov 2019 09:32:19 -0500
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: IETF QUIC WG <quic@ietf.org>
Subject: Q and L loss bits: which is which?
Message-ID: <20191119143218.GB2789@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/0qmVseFECOibQwgNYXGyJWNBy0Y>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Nov 2019 14:32:27 -0000

Hello,

I've read the loss bits draft [1] and the basic functionality (a single
counter per connection, ignoring the per-CID or per-tuple nuances) is
very doable.  I can set up a separate public endpoint that generates
these bits for experimentation.

One stumbling block is that the draft does not specify which short header
R bit [2] is L and which is Q.

  - Dmitri.

1. https://tools.ietf.org/html/draft-ferrieuxhamchaoui-quic-lossbits-02
2. https://tools.ietf.org/html/draft-ietf-quic-transport-24#section-17.3


From nobody Tue Nov 19 06:48:58 2019
Return-Path: <alexandre.ferrieux@orange.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 4AFDC12092A for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 06:48:56 -0800 (PST)
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, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 obkj5UxI9hfN for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 06:48:54 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.36]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 88E1A120915 for <quic@ietf.org>; Tue, 19 Nov 2019 06:48:54 -0800 (PST)
Received: from opfednr01.francetelecom.fr (unknown [xx.xx.xx.65]) by opfednr20.francetelecom.fr (ESMTP service) with ESMTP id 47HTGr3g9hz1ynt; Tue, 19 Nov 2019 15:48:52 +0100 (CET)
Received: from Exchangemail-eme3.itn.ftgroup (unknown [xx.xx.50.92]) by opfednr01.francetelecom.fr (ESMTP service) with ESMTP id 47HTGq73YYzDq7x; Tue, 19 Nov 2019 15:48:51 +0100 (CET)
Received: from lat6466.rd.francetelecom.fr (10.114.50.247) by OPEXCNORMAC.corporate.adroot.infra.ftgroup (10.114.50.92) with Microsoft SMTP Server (TLS) id 14.3.468.0; Tue, 19 Nov 2019 15:48:51 +0100
Message-ID: <24388_1574174932_5DD400D4_24388_372_7_1574174948.30247.49.camel@orange.com>
Subject: Re: Q and L loss bits: which is which?
From: <alexandre.ferrieux@orange.com>
To: Dmitri Tikhonov <dtikhonov@litespeedtech.com>, IETF QUIC WG <quic@ietf.org>
In-Reply-To: <20191119143218.GB2789@ubuntu-dmitri>
References: <20191119143218.GB2789@ubuntu-dmitri>
Content-Type: text/plain; charset="ISO-8859-1"
Date: Tue, 19 Nov 2019 15:49:08 +0100
MIME-Version: 1.0
X-Mailer: Evolution 3.22.6-1+deb9u2 
Content-Transfer-Encoding: 8bit
X-Originating-IP: [10.114.50.247]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/3uw29NvvOctix7JK01IlTHajiVs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Nov 2019 14:48:56 -0000

Hello Dmitri,

Thanks for your offer: experimentations are very welcome !
You're right we forgot to just define which is what, we'll fix the
draft shortly. We'll choose: 0x10 for Q and 0x08 for L.
This means the first byte layout becomes:
 |0|1|S|Q|L|K|P P|

Note the WG meeting yesterday concluded these should be controlled by a
negotiated option. But in the meantime, that does not prevent you from
running an experiment as long as you also modify the client, so that it
does not enforce the drafted constraint on the reserved bits.


On Tue, 2019-11-19 at 09:32 -0500, Dmitri Tikhonov wrote:
> Hello,
> 
> I've read the loss bits draft [1] and the basic functionality (a
> single
> counter per connection, ignoring the per-CID or per-tuple nuances) is
> very doable.  I can set up a separate public endpoint that generates
> these bits for experimentation.
> 
> One stumbling block is that the draft does not specify which short
> header
> R bit [2] is L and which is Q.
> 
>   - Dmitri.
> 
> 1. https://tools.ietf.org/html/draft-ferrieuxhamchaoui-quic-lossbits-
> 02
> 2. https://tools.ietf.org/html/draft-ietf-quic-transport-24#section-1
> 7.3
> 

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


From nobody Tue Nov 19 07:08:36 2019
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 89B7A12092C for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 07:08:34 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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=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 lAnSC12fmKw5 for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 07:08:33 -0800 (PST)
Received: from mail-qk1-x72c.google.com (mail-qk1-x72c.google.com [IPv6:2607:f8b0:4864:20::72c]) (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 E860312093C for <quic@ietf.org>; Tue, 19 Nov 2019 07:08:32 -0800 (PST)
Received: by mail-qk1-x72c.google.com with SMTP id 15so18066043qkh.6 for <quic@ietf.org>; Tue, 19 Nov 2019 07:08:32 -0800 (PST)
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=HBD4lVojko/CD4sPjsqpsgxTRnRTCKDpQUGndKhQIuI=; b=m1CuUOX4rWGPy84iJomN3saKimv2BVfJVqXVAmNukVZjKCVLGs70bQyJAEqGY8YwHY ta1GNrM9nYAOfFvwr/mAm7rfd1saV7LTupTXBczTxjJ4VdnJZZ0XXzcdmxEV1xSFyJXn oywiuFAnZD+b4KOaTvuWu4MRip507jy2g9vbAOyCtl4SyvKjQuKUAZvmrkwi6yr7df+x QY0RgjPdzMdp1DwRxrIQ2OMhcM4m48I8H0orS14zP6lEbDGGEAB/dhsTON0j9P7+Rvkz IaB4qhg5K3IP83Oha9Ogu3BLSoiZxe+3/cIA4WJAr2EFFARfFHDHg0/pJUnYVgOz7c/1 60/g==
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=HBD4lVojko/CD4sPjsqpsgxTRnRTCKDpQUGndKhQIuI=; b=Jbe8hgmzAGeDpvquyPerYAFb1MjJne8er8uoQunGFc8hejoVk+7C2NG4P0FdD1sg3G JE7azTfePuyogi/wt1J9IGu8YlKty5E3fNtrz8nvhpECNC2UcP2RC50JwVBs+kI3T2xO mG3ogFLVd6jONOGvQPJ8pgXQoRkaao5RPmQU/cMfrWxG3KZUAIpcmmUWpO9t67/G6a9a 1bveEaYyVhH4AJcxjxez6s0k6JVNOao9keiOiQx4jo3h0GBbZe9kHY4dNgB6XsKHIMt2 4DvBKSZGDpIfTHdweG/hJotdlL7C1jaNEbTan7kjsX/VLSkvJBQlBH6tn+mFCdjxPgsf LKqA==
X-Gm-Message-State: APjAAAUJnkvtsrkkvo4Gd9qS1zY3Tz0/Tp0rwZ8fTjmrIfqjQVmI6H3A ePSemulbNWd6kGC+m8ZsWqGMqw==
X-Google-Smtp-Source: APXvYqwQV4fmZsVA0AAUBw8sghp7CE49SoDoVJJYB3FylZQcRw+6rV608tcP8ro1fwWUp3sGutHQWg==
X-Received: by 2002:a37:6d41:: with SMTP id i62mr16802376qkc.211.1574176111993;  Tue, 19 Nov 2019 07:08:31 -0800 (PST)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id g11sm10148736qkm.82.2019.11.19.07.08.31 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Nov 2019 07:08:31 -0800 (PST)
Date: Tue, 19 Nov 2019 10:08:29 -0500
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: alexandre.ferrieux@orange.com
Cc: IETF QUIC WG <quic@ietf.org>
Subject: Re: Q and L loss bits: which is which?
Message-ID: <20191119150829.GD2789@ubuntu-dmitri>
Mail-Followup-To: alexandre.ferrieux@orange.com, IETF QUIC WG <quic@ietf.org>
References: <20191119143218.GB2789@ubuntu-dmitri> <24388_1574174932_5DD400D4_24388_372_7_1574174948.30247.49.camel@orange.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <24388_1574174932_5DD400D4_24388_372_7_1574174948.30247.49.camel@orange.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/zse1M01VPjddYWo648RbmOabb78>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Nov 2019 15:08:34 -0000

On Tue, Nov 19, 2019 at 03:49:08PM +0100, alexandre.ferrieux@orange.com wrote:
> Thanks for your offer: experimentations are very welcome !
> You're right we forgot to just define which is what, we'll fix the
> draft shortly. We'll choose: 0x10 for Q and 0x08 for L.
> This means the first byte layout becomes:
>  |0|1|S|Q|L|K|P P|

Thank you!

I also assume that these two bits would now be outside of the header
protection?  That is, the short header header protection mask [1] is
now 0x7 instead of 0x1F?  This is not mentioned in your draft, but I
don't see how an observer could get at those bits otherwise.

  - Dmitri.

1. https://tools.ietf.org/html/draft-ietf-quic-tls-24#section-5.4.1


From nobody Tue Nov 19 09:18:52 2019
Return-Path: <alexandre.ferrieux@orange.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 8AC6B12007C for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 09:18:51 -0800 (PST)
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, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 6gETuL2gg5uG for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 09:18:49 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.40]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8F5CE120111 for <quic@ietf.org>; Tue, 19 Nov 2019 09:18:49 -0800 (PST)
Received: from opfedar06.francetelecom.fr (unknown [xx.xx.xx.8]) by opfedar21.francetelecom.fr (ESMTP service) with ESMTP id 47HXbq6djtz7vGr; Tue, 19 Nov 2019 18:18:47 +0100 (CET)
Received: from Exchangemail-eme3.itn.ftgroup (unknown [xx.xx.50.92]) by opfedar06.francetelecom.fr (ESMTP service) with ESMTP id 47HXbq5ZbPz3wbN; Tue, 19 Nov 2019 18:18:47 +0100 (CET)
Received: from lat6466.rd.francetelecom.fr (10.114.50.247) by OPEXCNORMAC.corporate.adroot.infra.ftgroup (10.114.50.92) with Microsoft SMTP Server (TLS) id 14.3.468.0; Tue, 19 Nov 2019 18:18:47 +0100
Message-ID: <6505_1574183927_5DD423F7_6505_245_3_1574183944.11100.4.camel@orange.com>
Subject: Re: Q and L loss bits: which is which?
From: <alexandre.ferrieux@orange.com>
To: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
CC: IETF QUIC WG <quic@ietf.org>
In-Reply-To: <20191119150829.GD2789@ubuntu-dmitri>
References: <20191119143218.GB2789@ubuntu-dmitri> <24388_1574174932_5DD400D4_24388_372_7_1574174948.30247.49.camel@orange.com> <20191119150829.GD2789@ubuntu-dmitri>
Content-Type: text/plain; charset="ISO-8859-1"
Date: Tue, 19 Nov 2019 18:19:04 +0100
MIME-Version: 1.0
X-Mailer: Evolution 3.22.6-1+deb9u2 
Content-Transfer-Encoding: 8bit
X-Originating-IP: [10.114.50.247]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/E4hAuCg8QPVv68oU1PoUhj2HCfM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Nov 2019 17:18:52 -0000

Yes, you're right again. Those bits are definitely to be sent in clear:
     |0|1|S|Q|L|E E E|
Of course, the whole header remains part of the AD so is integrity
protected. Hence Q&L are no more subject to middlebox tampering than
the rest.

On Tue, 2019-11-19 at 10:08 -0500, Dmitri Tikhonov wrote:
> On Tue, Nov 19, 2019 at 03:49:08PM +0100, alexandre.ferrieux@orange.c
> om wrote:
> > Thanks for your offer: experimentations are very welcome !
> > You're right we forgot to just define which is what, we'll fix the
> > draft shortly. We'll choose: 0x10 for Q and 0x08 for L.
> > This means the first byte layout becomes:
> >  |0|1|S|Q|L|K|P P|
> 
> Thank you!
> 
> I also assume that these two bits would now be outside of the header
> protection?  That is, the short header header protection mask [1] is
> now 0x7 instead of 0x1F?  This is not mentioned in your draft, but I
> don't see how an observer could get at those bits otherwise.
> 
>   - Dmitri.
> 
> 1. https://tools.ietf.org/html/draft-ietf-quic-tls-24#section-5.4.1

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


From nobody Tue Nov 19 11:26:29 2019
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 0BEE012089D for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 11:26:28 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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=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 HZOsNtYfvBIX for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 11:26:26 -0800 (PST)
Received: from mail-qk1-x735.google.com (mail-qk1-x735.google.com [IPv6:2607:f8b0:4864:20::735]) (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 6593812029C for <quic@ietf.org>; Tue, 19 Nov 2019 11:26:26 -0800 (PST)
Received: by mail-qk1-x735.google.com with SMTP id i19so18933832qki.2 for <quic@ietf.org>; Tue, 19 Nov 2019 11:26:26 -0800 (PST)
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:references :mime-version:content-disposition:in-reply-to:user-agent; bh=wj6iVJzhAuEYt+0UiAe9lop1EGC3NrBxjvkaZwep9uM=; b=0u4tp1Ztado2KnLm/k1SAuh68JDyT9T1csZvrAby6MNEkCYBAxQPWmaEOKRbl4vuwb 4wWE/kHefvs+MjmUzalVNlG1/xxSWHlLN9AGzZ+sfgweGVOYxuhKoMv6zlzbrVxyfWby N0y8Pwh7lE0CznHP8KRvTJzacFZRwQpM3AzVS3Zr6B7BSQxbNnzMaqYGK9BojZCY+gzV nuEHTuXByhMoD/Uh1ACBNDRSQmj7AnlegxpQVgWjDOKFaG7Of7+7PVdHksLgZyDf6UwL 1CBQE48nOY9YkjPKgHjZRPZ2g2iBcLjyA4sMNLQJI3b/1YcjMrhKrhkmXdOGR7TLNCfy AQ9w==
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 :references:mime-version:content-disposition:in-reply-to:user-agent; bh=wj6iVJzhAuEYt+0UiAe9lop1EGC3NrBxjvkaZwep9uM=; b=s0krCSfJbqQhje8hm5VBSv8q5gvsaa2md52H9yzAz7p1bGZpEzz4kKoGkngLFxW9dn 4XXwT6QjW4zw5UDFVdXfu7G03K04NfWNO+QWHioniVVP+oX8vEantB0ZzXJurra1XlvO A2bn04HoMAazDjtCJNUZAaKGLshDv2aegfCUT+ft7XwWkpDHrBR0s/xEb46YlmSPcLMl a0q4+UqwRKw/ZvHpvcTBCxVPHnrmruyQ+cywbIOyYx8/RVwB1MSQ/vrECCcxrsaQutBZ tTy/18a4aDa2Mtn/3HzTrqXui8bYGUvzohgiBdVqGqEdkHmbiA31ULVGYVkkp8kV6H7I Xt8A==
X-Gm-Message-State: APjAAAUBaNGkgFpb1KnMinzOFrpZHMxlSQ52/AXYwlRZepH6705fNRg+ 0qpkOM/YCckAgb5+KNiJQ6s+JQ==
X-Google-Smtp-Source: APXvYqwQouNphZ2AVWGBA7m0Be4h/jQrKbV2vRpZmd/4AsoIyPTazJdOantx72v3QIXV2u0u/0T+zA==
X-Received: by 2002:a37:7f87:: with SMTP id a129mr30779919qkd.122.1574191585518;  Tue, 19 Nov 2019 11:26:25 -0800 (PST)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id w2sm10572231qkw.31.2019.11.19.11.26.24 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Nov 2019 11:26:25 -0800 (PST)
Date: Tue, 19 Nov 2019 14:26:23 -0500
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: alexandre.ferrieux@orange.com, IETF QUIC WG <quic@ietf.org>
Subject: Re: Q and L loss bits: which is which?
Message-ID: <20191119192622.GE2789@ubuntu-dmitri>
Mail-Followup-To: alexandre.ferrieux@orange.com, IETF QUIC WG <quic@ietf.org>
References: <20191119143218.GB2789@ubuntu-dmitri> <24388_1574174932_5DD400D4_24388_372_7_1574174948.30247.49.camel@orange.com> <20191119150829.GD2789@ubuntu-dmitri>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20191119150829.GD2789@ubuntu-dmitri>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/3N-wqpFjzTcc6bP1zLa2ZugDv1g>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Nov 2019 19:26:28 -0000

I added a loss bits server on

    http3-test.litespeedtech.com:4440

Feel free to give it a shot!

Both lsquic server and client can be compiled with loss bits support
by doing

    EXTRA_CLFAGS=-DLSQUIC_LOSS_BITS=1 cmake ....

The code is on a branch for now:

    https://github.com/litespeedtech/lsquic/commit/0b83dfa304bcd9750b67e6297416ce493d9fb5b1

  - Dmitri.

On Tue, Nov 19, 2019 at 10:08:29AM -0500, Dmitri Tikhonov wrote:
> On Tue, Nov 19, 2019 at 03:49:08PM +0100, alexandre.ferrieux@orange.com wrote:
> > Thanks for your offer: experimentations are very welcome !
> > You're right we forgot to just define which is what, we'll fix the
> > draft shortly. We'll choose: 0x10 for Q and 0x08 for L.
> > This means the first byte layout becomes:
> >  |0|1|S|Q|L|K|P P|
> 
> Thank you!
> 
> I also assume that these two bits would now be outside of the header
> protection?  That is, the short header header protection mask [1] is
> now 0x7 instead of 0x1F?  This is not mentioned in your draft, but I
> don't see how an observer could get at those bits otherwise.
> 
>   - Dmitri.
> 
> 1. https://tools.ietf.org/html/draft-ietf-quic-tls-24#section-5.4.1


From nobody Tue Nov 19 15:19:20 2019
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 63002120A81 for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 15:19:16 -0800 (PST)
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, SPF_HELO_NONE=0.001, 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 QsAdh_bwxSco for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 15:19:14 -0800 (PST)
Received: from mx36-out10.antispamcloud.com (mx36-out10.antispamcloud.com [209.126.121.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 B9B57120A6D for <quic@ietf.org>; Tue, 19 Nov 2019 15:19:14 -0800 (PST)
Received: from xse324.mail2web.com ([66.113.197.70] helo=xse.mail2web.com) by mx114.antispamcloud.com with esmtp (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1iXCmA-000hjd-O3 for quic@ietf.org; Wed, 20 Nov 2019 00:19:15 +0100
Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 47Hhbg1Pr7z2DbD for <quic@ietf.org>; Tue, 19 Nov 2019 15:19:11 -0800 (PST)
Received: from [10.5.2.49] (helo=xmail11.myhosting.com) by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1iXCm7-0000pX-2Z for quic@ietf.org; Tue, 19 Nov 2019 15:19:11 -0800
Received: (qmail 5120 invoked from network); 19 Nov 2019 23:19:10 -0000
Received: from unknown (HELO [172.16.138.209]) (Authenticated-user:_huitema@huitema.net@[101.100.166.3]) (envelope-sender <huitema@huitema.net>) by xmail11.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 19 Nov 2019 23:19:10 -0000
To: alexandre.ferrieux@orange.com, IETF QUIC WG <quic@ietf.org>
References: <20191119143218.GB2789@ubuntu-dmitri> <24388_1574174932_5DD400D4_24388_372_7_1574174948.30247.49.camel@orange.com> <20191119150829.GD2789@ubuntu-dmitri> <20191119192622.GE2789@ubuntu-dmitri>
From: Christian Huitema <huitema@huitema.net>
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mQENBFIRX8gBCAC26usy/Ya38IqaLBSu33vKD6hP5Yw390XsWLaAZTeQR64OJEkoOdXpvcOS HWfMIlD5s5+oHfLe8jjmErFAXYJ8yytPj1fD2OdSKAe1TccUBiOXT8wdVxSr5d0alExVv/LO I/vA2aU1TwOkVHKSapD7j8/HZBrqIWRrXUSj2f5n9tY2nJzG9KRzSG0giaJWBfUFiGb4lvsy IaCaIU0YpfkDDk6PtK5YYzuCeF0B+O7N9LhDu/foUUc4MNq4K3EKDPb2FL1Hrv0XHpkXeMRZ olpH8SUFUJbmi+zYRuUgcXgMZRmZFL1tu6z9h6gY4/KPyF9aYot6zG28Qk/BFQRtj7V1ABEB AAG0J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PokBOQQTAQIAIwUC UhFfyAIbLwcLCQgHAwIBBhUIAgkKCwQWAgMBAh4BAheAAAoJEJNDCbJVyA1yhbYH/1ud6x6m VqGIp0JcZUfSQO8w+TjugqxCyGNn+w/6Qb5O/xENxNQ4HaMQ5uSRK9n8WKKDDRSzwZ4syKKf wbkfj05vgFxrjCynVbm1zs2X2aGXh+PxPL/WHUaxzEP7KjYbLtCUZDRzOOrm+0LMktngT/k3 6+EZoLEM52hwwpIAzJoscyEz7QfqMOZtFm6xQnlvDQeIrHx0KUvwo/vgDLK3SuruG1CSHcR0 D24kEEUa044AIUKBS3b0b8AR7f6mP2NcnLpdsibtpabi9BzqAidcY/EjTaoea46HXALk/eJd 6OLkLE6UQe1PPzQC4jB7rErX2BxnSkHDw50xMgLRcl5/b1a5AQ0EUhFfyAEIAKp7Cp8lqKTV CC9QiAf6QTIjW+lie5J44Ad++0k8gRgANZVWubQuCQ71gxDWLtxYfFkEXjG4TXV/MUtnOliG 5rc2E+ih6Dg61Y5PQakm9OwPIsOx+2R+iSW325ngln2UQrVPgloO83QiUoi7mBJPbcHlxkhZ bd3+EjFxSLIQogt29sTcg2oSh4oljUpz5niTt69IOfZx21kf29NfDE+Iw56gfrxI2ywZbu5o G+d0ZSp0lsovygpk4jK04fDTq0vxjEU5HjPcsXC4CSZdq5E2DrF4nOh1UHkHzeaXdYR2Bn1Y wTePfaHBFlvQzI+Li/Q6AD/uxbTM0vIcsUxrv3MNHCUAEQEAAYkCPgQYAQIACQUCUhFfyAIb 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=
Subject: Re: Q and L loss bits: which is which?
Message-ID: <a21bc373-1fda-836e-7efc-599832ae575d@huitema.net>
Date: Wed, 20 Nov 2019 07:19:09 +0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <20191119192622.GE2789@ubuntu-dmitri>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
X-Originating-IP: 66.113.197.70
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.197.0/24
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.197.0/24@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0fIjBzH0XxYvWQgWH/ix0mSpSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDcnqpk5VeF3xR4kF6iVwRtbgN zB/4Jkrw1eDLcif59fsmc6JWUMsohSZs3/w3kxA6U7Tmz6iKnkQL9gqsxD347235Nhqq+/HvroPq 8GSPg+60/QPNqXybIny9WGhadIo/d/hBjqsxautjlVXfyJaQKbyme9ldZJ7uNXfg/GfS8fUvP/L5 rCqHDsKZM+xa1iwJX+gRCHfMVnsAk591zk0uilUI+ZL4xWiN8NS6C+dmX6OEdA4u1aThyWrQ/ou2 +v/lmX4Em37yFgrCB6NHRn1g+f3uncIqYSL3lhh5c81YyJqFoLZMmkWsaurVZfvqROaDnDtHb8z5 dpPkEuJ8Snwqla7jUnW3hy14Yji8fo+4xCnSRo4Rcu5Z37rMuDjCny5fE9ykbJ7I9co1MAEE3ruN Xsm8UJsAPvDcVSKtDCYkioPY5Qx4fJOk03R5fJtf/Dv/dkIzS7m4GUpXCY1Y3j3ilUN7TTX3qb0a 8RNcOLCOSd5csd6/DQyP1F2MXqSxFa+QQg9msI6rsyff6hB7UpUkB/yrwGG1lVk6xicgc7dahDwv UwPy3x0FYtCNEb10sHyQCLHEvD1OqP6bgZ4L66GcgBg66gs5OuzYxJgw5atIxeNDvjI/CYe5WPy0 +t1RP0azoFDUztYEACkIvtiCCpI/4JxMPnetLBJMh51NiRRoHIC1T9HnzvLN61S2+60ZuJDnmiK7 x42VjdzChZMe6O/DiWiiIzuXMTE3l4bIsk+O50sPHBzwcRWk2x0IZOz6Ob5N08QV3No+S2msRDep v5w/kkG0v17AmegcpQ0tml/sN9lmMy/o83jVXTcfb9k0nLWblJy7uxV6dw8jzlsaNZe6hynMJcjx DydxsJEju76A7X1QIVydqXpZ6MHhiKws9Iiut28r9wo4SqUIg8Yh9hAM0n3LLzx/F2gT3wl8JQJv Bho=
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/gWAxERhRWmLZabfmBKK1VWVrdKI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Nov 2019 23:19:19 -0000

I am willing to do the same in Picoquic, but I would really like to get
the transport parameter defined first.

Also, I would like some clarification. The loss counter is supposedly
incremented using Quic's loss detection machinery, but the loss
detection mechanism sometimes err on the false positive side. This is
detected if an ack arrive late for a packet that was supposed lost, and
the loss is classified as spurious.

Any guidance on how to handle spurious loss detection?

-- Christian Huitema

On 11/20/2019 3:26 AM, Dmitri Tikhonov wrote:
> I added a loss bits server on
>
>     http3-test.litespeedtech.com:4440
>
> Feel free to give it a shot!
>
> Both lsquic server and client can be compiled with loss bits support
> by doing
>
>     EXTRA_CLFAGS=3D-DLSQUIC_LOSS_BITS=3D1 cmake ....
>
> The code is on a branch for now:
>
>     https://github.com/litespeedtech/lsquic/commit/0b83dfa304bcd9750b67=
e6297416ce493d9fb5b1
>
>   - Dmitri.
>
> On Tue, Nov 19, 2019 at 10:08:29AM -0500, Dmitri Tikhonov wrote:
>> On Tue, Nov 19, 2019 at 03:49:08PM +0100, alexandre.ferrieux@orange.co=
m wrote:
>>> Thanks for your offer: experimentations are very welcome !
>>> You're right we forgot to just define which is what, we'll fix the
>>> draft shortly. We'll choose: 0x10 for Q and 0x08 for L.
>>> This means the first byte layout becomes:
>>>  |0|1|S|Q|L|K|P P|
>> Thank you!
>>
>> I also assume that these two bits would now be outside of the header
>> protection?  That is, the short header header protection mask [1] is
>> now 0x7 instead of 0x1F?  This is not mentioned in your draft, but I
>> don't see how an observer could get at those bits otherwise.
>>
>>   - Dmitri.
>>
>> 1. https://tools.ietf.org/html/draft-ietf-quic-tls-24#section-5.4.1


From nobody Tue Nov 19 15:56:19 2019
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 7DCDD12008C for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 15:56:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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=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 rYHzJ9kimfGc for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 15:56:13 -0800 (PST)
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 A966D12006B for <quic@ietf.org>; Tue, 19 Nov 2019 15:56:13 -0800 (PST)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id xAJNrT2p004963; Tue, 19 Nov 2019 23:56:12 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=jan2016.eng; bh=645TbTr7KcMaKAYT0dUEIOurTrTfWjh31HyopHpw2gI=; b=H6ww2Rvq6kamlSQe8l6s+UWGPMDiiXTwBHG4XzC7XNeLm7j3LDeHOHEYnWNCpdXU/Cft dfvi4+Fsi5dZSzFdEORGJwPclYzOcCWc72OEl9dz1bU+vj+QM4B9lBQgpNsQGm2QrlUD b/8AvqCnfTNt740+JvQcsD1KYdFlGidD7xUA8C0xX1Lxv9GKUk5N/G2rB7UlpLdg9xKD /gqxp37ssRp5sFY/yWShv5X1tFvvO6SpjXZYD3osi4oA15QlBOessIrW1ZU4tRLJf2nu WYBYsTGO7kF3j3vZ2eIOopLMlReWEkvyevczHaLdcSM02pC//V1rdQeiaNNBlQK+K0cU qA== 
Received: from prod-mail-ppoint8 (prod-mail-ppoint8.akamai.com [96.6.114.122] (may be forged)) by m0050095.ppops.net-00190b01. with ESMTP id 2wafwvfsw2-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Tue, 19 Nov 2019 23:56:11 +0000
Received: from pps.filterd (prod-mail-ppoint8.akamai.com [127.0.0.1]) by prod-mail-ppoint8.akamai.com (8.16.0.27/8.16.0.27) with SMTP id xAJNl24k003352; Tue, 19 Nov 2019 18:56:10 -0500
Received: from email.msg.corp.akamai.com ([172.27.165.117]) by prod-mail-ppoint8.akamai.com with ESMTP id 2wadb132cf-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 19 Nov 2019 18:56:09 -0500
Received: from USTX2EX-DAG1MB5.msg.corp.akamai.com (172.27.165.123) by ustx2ex-dag1mb1.msg.corp.akamai.com (172.27.165.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 19 Nov 2019 17:56:07 -0600
Received: from USTX2EX-DAG1MB5.msg.corp.akamai.com ([172.27.165.123]) by ustx2ex-dag1mb5.msg.corp.akamai.com ([172.27.165.123]) with mapi id 15.00.1473.005; Tue, 19 Nov 2019 17:56:07 -0600
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: Christian Huitema <huitema@huitema.net>, "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Q and L loss bits: which is which?
Thread-Topic: Q and L loss bits: which is which?
Thread-Index: AQHVnuYxGYRqnRW1T0W5CpBoQ1gaSaeS98cAgAAFaICAAEgOgIAAQQmA//+iQwA=
Date: Tue, 19 Nov 2019 23:56:05 +0000
Message-ID: <ffa583fd76c44ad9b99427341841d740@ustx2ex-dag1mb5.msg.corp.akamai.com>
References: <20191119143218.GB2789@ubuntu-dmitri> <24388_1574174932_5DD400D4_24388_372_7_1574174948.30247.49.camel@orange.com> <20191119150829.GD2789@ubuntu-dmitri> <20191119192622.GE2789@ubuntu-dmitri> <a21bc373-1fda-836e-7efc-599832ae575d@huitema.net>
In-Reply-To: <a21bc373-1fda-836e-7efc-599832ae575d@huitema.net>
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.216.50]
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=2019-11-19_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=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140001 definitions=main-1911190187
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-11-19_08:2019-11-15,2019-11-19 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 lowpriorityscore=0 priorityscore=1501 phishscore=0 clxscore=1015 mlxlogscore=999 impostorscore=0 suspectscore=0 bulkscore=0 malwarescore=0 adultscore=0 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1911190187
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/PWJzImo5bfsceaz9cLOWBClp35w>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 19 Nov 2019 23:56:18 -0000

Q2hyaXN0aWFuLCBJIGFjdHVhbGx5IHRob3VnaHQgYWJvdXQgdGhpcywgYW5kIGRlY2lkZWQgdGhh
dCB0aGUgcmVjb21tZW5kYXRpb24gaXMgbm90IHRvIGRlY3JlbWVudCBMIGNvdW50ZXIuICBJdCBp
cyBpbiB0aGUgLXRzdndnLSB2ZXJzaW9uIG9mIHRoZSBkcmFmdCBidXQgc29tZWhvdyBkaWQgbm90
IGhhdmUgaXQgaW50byB0aGUgLXF1aWMtIHZlcnNpb24gKGtlZXBpbmcgdHdvIHZlcnNpb25zIGlu
IHN5bmMgaXMgYXBwYXJlbnRseSBoYXJkKSwgc29ycnkuIChodHRwczovL3Rvb2xzLmlldGYub3Jn
L2h0bWwvZHJhZnQtZmVycmlldXhoYW1jaGFvdWktdHN2d2ctbG9zc2JpdHMtMDIjc2VjdGlvbi0z
LjIpDQoNCiINCklmIHRoZSBwcm90b2NvbCBpcyBhYmxlIHRvIHJlc2NpbmQgdGhlIGxvc3MgZGV0
ZXJtaW5hdGlvbiBsYXRlciwgdGhlIFVucmVwb3J0ZWQgTG9zcyBjb3VudGVyIFNIT1VMRCBOT1Qg
YmUgZGVjcmVtZW50ZWQgZHVlIHRvIHRoZSByZXNjaXNzaW9uLg0KIg0KDQpJIHRob3VnaHQgdGhp
cyBydWxlIHdvdWxkIGxpbWl0IHRoZSBjb25mdXNpb24gb2YgdGhlIG9ic2VydmVyIHdobyBpcyB0
cnlpbmcgdG8gY29ycmVsYXRlIFEgYW5kIEwgYml0cy4gSSdtIGhhcHB5IHRvIGhlYXIgYWx0ZXJu
YXRpdmUgb3BpbmlvbnMgb24gdGhpcy4NCg0KLSBJZ29yDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNz
YWdlLS0tLS0NCj4gRnJvbTogQ2hyaXN0aWFuIEh1aXRlbWEgPGh1aXRlbWFAaHVpdGVtYS5uZXQ+
DQo+IFNlbnQ6IFdlZG5lc2RheSwgTm92ZW1iZXIgMjAsIDIwMTkgNzoxOSBBTQ0KPiBUbzogYWxl
eGFuZHJlLmZlcnJpZXV4QG9yYW5nZS5jb207IElFVEYgUVVJQyBXRyA8cXVpY0BpZXRmLm9yZz4N
Cj4gU3ViamVjdDogUmU6IFEgYW5kIEwgbG9zcyBiaXRzOiB3aGljaCBpcyB3aGljaD8NCj4gDQo+
IEkgYW0gd2lsbGluZyB0byBkbyB0aGUgc2FtZSBpbiBQaWNvcXVpYywgYnV0IEkgd291bGQgcmVh
bGx5IGxpa2UgdG8gZ2V0IHRoZQ0KPiB0cmFuc3BvcnQgcGFyYW1ldGVyIGRlZmluZWQgZmlyc3Qu
DQo+IA0KPiBBbHNvLCBJIHdvdWxkIGxpa2Ugc29tZSBjbGFyaWZpY2F0aW9uLiBUaGUgbG9zcyBj
b3VudGVyIGlzIHN1cHBvc2VkbHkNCj4gaW5jcmVtZW50ZWQgdXNpbmcgUXVpYydzIGxvc3MgZGV0
ZWN0aW9uIG1hY2hpbmVyeSwgYnV0IHRoZSBsb3NzIGRldGVjdGlvbg0KPiBtZWNoYW5pc20gc29t
ZXRpbWVzIGVyciBvbiB0aGUgZmFsc2UgcG9zaXRpdmUgc2lkZS4gVGhpcyBpcyBkZXRlY3RlZCBp
ZiBhbiBhY2sNCj4gYXJyaXZlIGxhdGUgZm9yIGEgcGFja2V0IHRoYXQgd2FzIHN1cHBvc2VkIGxv
c3QsIGFuZCB0aGUgbG9zcyBpcyBjbGFzc2lmaWVkIGFzDQo+IHNwdXJpb3VzLg0KPiANCj4gQW55
IGd1aWRhbmNlIG9uIGhvdyB0byBoYW5kbGUgc3B1cmlvdXMgbG9zcyBkZXRlY3Rpb24/DQo+IA0K
PiAtLSBDaHJpc3RpYW4gSHVpdGVtYQ0KPiANCj4gT24gMTEvMjAvMjAxOSAzOjI2IEFNLCBEbWl0
cmkgVGlraG9ub3Ygd3JvdGU6DQo+ID4gSSBhZGRlZCBhIGxvc3MgYml0cyBzZXJ2ZXIgb24NCj4g
Pg0KPiA+ICAgICBodHRwMy10ZXN0LmxpdGVzcGVlZHRlY2guY29tOjQ0NDANCj4gPg0KPiA+IEZl
ZWwgZnJlZSB0byBnaXZlIGl0IGEgc2hvdCENCj4gPg0KPiA+IEJvdGggbHNxdWljIHNlcnZlciBh
bmQgY2xpZW50IGNhbiBiZSBjb21waWxlZCB3aXRoIGxvc3MgYml0cyBzdXBwb3J0DQo+ID4gYnkg
ZG9pbmcNCj4gPg0KPiA+ICAgICBFWFRSQV9DTEZBR1M9LURMU1FVSUNfTE9TU19CSVRTPTEgY21h
a2UgLi4uLg0KPiA+DQo+ID4gVGhlIGNvZGUgaXMgb24gYSBicmFuY2ggZm9yIG5vdzoNCj4gPg0K
PiA+DQo+ID4NCj4gaHR0cHM6Ly9naXRodWIuY29tL2xpdGVzcGVlZHRlY2gvbHNxdWljL2NvbW1p
dC8wYjgzZGZhMzA0YmNkOTc1MGI2N2U2Mg0KPiA+IDk3NDE2Y2U0OTNkOWZiNWIxDQo+ID4NCj4g
PiAgIC0gRG1pdHJpLg0KPiA+DQo+ID4gT24gVHVlLCBOb3YgMTksIDIwMTkgYXQgMTA6MDg6MjlB
TSAtMDUwMCwgRG1pdHJpIFRpa2hvbm92IHdyb3RlOg0KPiA+PiBPbiBUdWUsIE5vdiAxOSwgMjAx
OSBhdCAwMzo0OTowOFBNICswMTAwLA0KPiBhbGV4YW5kcmUuZmVycmlldXhAb3JhbmdlLmNvbSB3
cm90ZToNCj4gPj4+IFRoYW5rcyBmb3IgeW91ciBvZmZlcjogZXhwZXJpbWVudGF0aW9ucyBhcmUg
dmVyeSB3ZWxjb21lICENCj4gPj4+IFlvdSdyZSByaWdodCB3ZSBmb3Jnb3QgdG8ganVzdCBkZWZp
bmUgd2hpY2ggaXMgd2hhdCwgd2UnbGwgZml4IHRoZQ0KPiA+Pj4gZHJhZnQgc2hvcnRseS4gV2Un
bGwgY2hvb3NlOiAweDEwIGZvciBRIGFuZCAweDA4IGZvciBMLg0KPiA+Pj4gVGhpcyBtZWFucyB0
aGUgZmlyc3QgYnl0ZSBsYXlvdXQgYmVjb21lczoNCj4gPj4+ICB8MHwxfFN8UXxMfEt8UCBQfA0K
PiA+PiBUaGFuayB5b3UhDQo+ID4+DQo+ID4+IEkgYWxzbyBhc3N1bWUgdGhhdCB0aGVzZSB0d28g
Yml0cyB3b3VsZCBub3cgYmUgb3V0c2lkZSBvZiB0aGUgaGVhZGVyDQo+ID4+IHByb3RlY3Rpb24/
ICBUaGF0IGlzLCB0aGUgc2hvcnQgaGVhZGVyIGhlYWRlciBwcm90ZWN0aW9uIG1hc2sgWzFdIGlz
DQo+ID4+IG5vdyAweDcgaW5zdGVhZCBvZiAweDFGPyAgVGhpcyBpcyBub3QgbWVudGlvbmVkIGlu
IHlvdXIgZHJhZnQsIGJ1dCBJDQo+ID4+IGRvbid0IHNlZSBob3cgYW4gb2JzZXJ2ZXIgY291bGQg
Z2V0IGF0IHRob3NlIGJpdHMgb3RoZXJ3aXNlLg0KPiA+Pg0KPiA+PiAgIC0gRG1pdHJpLg0KPiA+
Pg0KPiA+PiAxLiBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaWV0Zi1xdWljLXRs
cy0yNCNzZWN0aW9uLTUuNC4xDQoNCg==


From nobody Tue Nov 19 16:16:48 2019
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 255E7120133 for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 16:16:47 -0800 (PST)
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, SPF_HELO_NONE=0.001, 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 d1FobO_a4DUs for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 16:16:44 -0800 (PST)
Received: from smtp-sh.infomaniak.ch (smtp-sh.infomaniak.ch [128.65.195.4]) (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 A8F04120115 for <quic@ietf.org>; Tue, 19 Nov 2019 16:16:43 -0800 (PST)
Received: from smtp-3-0000.mail.infomaniak.ch ([10.4.36.107]) by smtp-sh.infomaniak.ch (8.14.5/8.14.5) with ESMTP id xAK0GWGK005888 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Wed, 20 Nov 2019 01:16:32 +0100
Received: from [10.128.30.18] (unknown [61.8.238.244]) by smtp-3-0000.mail.infomaniak.ch (Postfix) with ESMTPA id 4B4BC1013CEF6; Wed, 20 Nov 2019 01:16:30 +0100 (CET)
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (1.0)
Subject: Re: Q and L loss bits: which is which?
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
X-Mailer: iPhone Mail (16G102)
In-Reply-To: <ffa583fd76c44ad9b99427341841d740@ustx2ex-dag1mb5.msg.corp.akamai.com>
Date: Wed, 20 Nov 2019 08:16:28 +0800
Cc: Christian Huitema <huitema@huitema.net>, "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, IETF QUIC WG <quic@ietf.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <EFE60BCA-89EE-4A78-8E5B-EB8B8ED25DD9@trammell.ch>
References: <20191119143218.GB2789@ubuntu-dmitri> <24388_1574174932_5DD400D4_24388_372_7_1574174948.30247.49.camel@orange.com> <20191119150829.GD2789@ubuntu-dmitri> <20191119192622.GE2789@ubuntu-dmitri> <a21bc373-1fda-836e-7efc-599832ae575d@huitema.net> <ffa583fd76c44ad9b99427341841d740@ustx2ex-dag1mb5.msg.corp.akamai.com>
To: "Lubashev, Igor" <ilubashe@akamai.com>
X-Antivirus: Dr.Web (R) for Unix mail servers drweb plugin ver.6.0.2.8
X-Antivirus-Code: 0x100000
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/dY54o-dRaLLu9q2WTObxaH8FbZQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 20 Nov 2019 00:16:47 -0000

Hi Igor, all,

Sent from my iPhone

> On 20 Nov 2019, at 07:56, Lubashev, Igor <ilubashe@akamai.com> wrote:
>=20
> Christian, I actually thought about this, and decided that the recommendat=
ion is not to decrement L counter.  It is in the -tsvwg- version of the draf=
t but somehow did not have it into the -quic- version (keeping two versions i=
n sync is apparently hard), sorry. (https://tools.ietf.org/html/draft-ferrie=
uxhamchaoui-tsvwg-lossbits-02#section-3.2)

FWIW I agree that these are the right semantics.

With these semantics, if I follow correctly, the L bit is basically signalin=
g that the sender has detected a loss _to which it will react_ (or rather, t=
o which it would react if it were already network limited), by reducing the c=
ongestion window, updating its loss estimate or capacity model, or whatever s=
ending-rate-relevant parameters its congestion control and avoidance scheme u=
ses.=20

This makes the condition it is signaling pretty close to the CWR bit (if the=
 CWR bit covered all such reactions, not just those triggered by ECN), which=
 is basically the proposal I (poorly and cryptically) alluded to in the issu=
e and the mic.

(Two nice properties of exposing loss reaction as opposed to raw loss: one, y=
ou=E2=80=99re closer to measuring what you actually care about =E2=80=94 poo=
r transport performance =E2=80=94 and two, since the signal is correlated wi=
th the time series of the sending rate, statistical techniques are applicabl=
e to verifying the signal: it=E2=80=99s harder to lie.)

Cheers, B

> "
> If the protocol is able to rescind the loss determination later, the Unrep=
orted Loss counter SHOULD NOT be decremented due to the rescission.
> "
>=20
> I thought this rule would limit the confusion of the observer who is tryin=
g to correlate Q and L bits. I'm happy to hear alternative opinions on this.=

>=20
> - Igor
>=20
>> -----Original Message-----
>> From: Christian Huitema <huitema@huitema.net>
>> Sent: Wednesday, November 20, 2019 7:19 AM
>> To: alexandre.ferrieux@orange.com; IETF QUIC WG <quic@ietf.org>
>> Subject: Re: Q and L loss bits: which is which?
>>=20
>> I am willing to do the same in Picoquic, but I would really like to get t=
he
>> transport parameter defined first.
>>=20
>> Also, I would like some clarification. The loss counter is supposedly
>> incremented using Quic's loss detection machinery, but the loss detection=

>> mechanism sometimes err on the false positive side. This is detected if a=
n ack
>> arrive late for a packet that was supposed lost, and the loss is classifi=
ed as
>> spurious.
>>=20
>> Any guidance on how to handle spurious loss detection?
>>=20
>> -- Christian Huitema
>>=20
>>> On 11/20/2019 3:26 AM, Dmitri Tikhonov wrote:
>>> I added a loss bits server on
>>>=20
>>>    http3-test.litespeedtech.com:4440
>>>=20
>>> Feel free to give it a shot!
>>>=20
>>> Both lsquic server and client can be compiled with loss bits support
>>> by doing
>>>=20
>>>    EXTRA_CLFAGS=3D-DLSQUIC_LOSS_BITS=3D1 cmake ....
>>>=20
>>> The code is on a branch for now:
>>>=20
>>>=20
>>>=20
>> https://github.com/litespeedtech/lsquic/commit/0b83dfa304bcd9750b67e62
>>> 97416ce493d9fb5b1
>>>=20
>>>  - Dmitri.
>>>=20
>>>> On Tue, Nov 19, 2019 at 10:08:29AM -0500, Dmitri Tikhonov wrote:
>>>> On Tue, Nov 19, 2019 at 03:49:08PM +0100,
>> alexandre.ferrieux@orange.com wrote:
>>>>> Thanks for your offer: experimentations are very welcome !
>>>>> You're right we forgot to just define which is what, we'll fix the
>>>>> draft shortly. We'll choose: 0x10 for Q and 0x08 for L.
>>>>> This means the first byte layout becomes:
>>>>> |0|1|S|Q|L|K|P P|
>>>> Thank you!
>>>>=20
>>>> I also assume that these two bits would now be outside of the header
>>>> protection?  That is, the short header header protection mask [1] is
>>>> now 0x7 instead of 0x1F?  This is not mentioned in your draft, but I
>>>> don't see how an observer could get at those bits otherwise.
>>>>=20
>>>>  - Dmitri.
>>>>=20
>>>> 1. https://tools.ietf.org/html/draft-ietf-quic-tls-24#section-5.4.1
>=20
>=20


From nobody Tue Nov 19 16:18:41 2019
Return-Path: <alexandre.ferrieux@orange.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 CDF8B12018B for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 16:18:39 -0800 (PST)
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, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 M7_OUjX9fsiy for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 16:18:37 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.70.35]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A11A6120115 for <quic@ietf.org>; Tue, 19 Nov 2019 16:18:36 -0800 (PST)
Received: from opfednr00.francetelecom.fr (unknown [xx.xx.xx.64]) by opfednr25.francetelecom.fr (ESMTP service) with ESMTP id 47HjwC26BQzCrl3; Wed, 20 Nov 2019 01:18:35 +0100 (CET)
Received: from Exchangemail-eme3.itn.ftgroup (unknown [xx.xx.50.92]) by opfednr00.francetelecom.fr (ESMTP service) with ESMTP id 47HjwC1LlJzDq7S; Wed, 20 Nov 2019 01:18:35 +0100 (CET)
Received: from lat6466.rd.francetelecom.fr (10.114.50.247) by OPEXCNORMAC.corporate.adroot.infra.ftgroup (10.114.50.92) with Microsoft SMTP Server (TLS) id 14.3.468.0; Wed, 20 Nov 2019 01:18:34 +0100
Message-ID: <24075_1574209115_5DD4865B_24075_288_1_1574209131.11100.44.camel@orange.com>
Subject: Re: Q and L loss bits: which is which?
From: <alexandre.ferrieux@orange.com>
To: Christian Huitema <huitema@huitema.net>, IETF QUIC WG <quic@ietf.org>
In-Reply-To: <a21bc373-1fda-836e-7efc-599832ae575d@huitema.net>
References: <20191119143218.GB2789@ubuntu-dmitri> <24388_1574174932_5DD400D4_24388_372_7_1574174948.30247.49.camel@orange.com> <20191119150829.GD2789@ubuntu-dmitri> <20191119192622.GE2789@ubuntu-dmitri> <a21bc373-1fda-836e-7efc-599832ae575d@huitema.net>
Content-Type: text/plain; charset="ISO-8859-1"
Date: Wed, 20 Nov 2019 01:18:51 +0100
MIME-Version: 1.0
X-Mailer: Evolution 3.22.6-1+deb9u2 
Content-Transfer-Encoding: 8bit
X-Originating-IP: [10.114.50.247]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Y8X1f3LAh1zeHCgBzTNFrxSPIB4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 20 Nov 2019 00:18:40 -0000

On Wed, 2019-11-20 at 07:19 +0800, Christian Huitema wrote:
> I am willing to do the same in Picoquic, but I would really like to
> get
> the transport parameter defined first.

Sure, working on it :)
By the way, in what shape is the IANA registry announced for TPs ? Is
it opened yet ?

> Also, I would like some clarification. The loss counter is supposedly
> incremented using Quic's loss detection machinery, but the loss
> detection mechanism sometimes err on the false positive side. This is
> detected if an ack arrive late for a packet that was supposed lost,
> and
> the loss is classified as spurious.
> 
> Any guidance on how to handle spurious loss detection?

One way would be to just decrement the "yet unreported loss"  counter
whenever the stack decides a loss was spurious. This may when the
counter is zero, bringing it to negative values. This does not affect
the rule for setting L=1, namely that the counter be >0. This way,
assuming spurious events are a fraction of genuine ones, the total
count at the end of the connection is accurate (except for spurious
after the last genuine).

A refinement would be to somehow delay sending L=1, to let a chance to
the counter to become >=0 again. The problem being, of course, that we
can't guarantee to have enough outgoing packets before the end of a
connection, leading to underestimation of loss at the end; this may be
workable in practice, as the Q halfperiod granularity has a similar
effect for upstream loss anyway.


> 
> -- Christian Huitema
> 
> On 11/20/2019 3:26 AM, Dmitri Tikhonov wrote:
> > I added a loss bits server on
> > 
> >     http3-test.litespeedtech.com:4440
> > 
> > Feel free to give it a shot!
> > 
> > Both lsquic server and client can be compiled with loss bits
> > support
> > by doing
> > 
> >     EXTRA_CLFAGS=-DLSQUIC_LOSS_BITS=1 cmake ....
> > 
> > The code is on a branch for now:
> > 
> >     https://github.com/litespeedtech/lsquic/commit/0b83dfa304bcd975
> > 0b67e6297416ce493d9fb5b1
> > 
> >   - Dmitri.
> > 
> > On Tue, Nov 19, 2019 at 10:08:29AM -0500, Dmitri Tikhonov wrote:
> > > On Tue, Nov 19, 2019 at 03:49:08PM +0100, alexandre.ferrieux@oran
> > > ge.com wrote:
> > > > Thanks for your offer: experimentations are very welcome !
> > > > You're right we forgot to just define which is what, we'll fix
> > > > the
> > > > draft shortly. We'll choose: 0x10 for Q and 0x08 for L.
> > > > This means the first byte layout becomes:
> > > >  |0|1|S|Q|L|K|P P|
> > > 
> > > Thank you!
> > > 
> > > I also assume that these two bits would now be outside of the
> > > header
> > > protection?  That is, the short header header protection mask [1]
> > > is
> > > now 0x7 instead of 0x1F?  This is not mentioned in your draft,
> > > but I
> > > don't see how an observer could get at those bits otherwise.
> > > 
> > >   - Dmitri.
> > > 
> > > 1. https://tools.ietf.org/html/draft-ietf-quic-tls-24#section-5.4
> > > .1
> 
> 

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


From nobody Tue Nov 19 16:25:41 2019
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 2A31B120861 for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 16:25:39 -0800 (PST)
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, SPF_HELO_NONE=0.001, 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 ROcRieXimzg4 for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 16:25:36 -0800 (PST)
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 86982120115 for <quic@ietf.org>; Tue, 19 Nov 2019 16:25:36 -0800 (PST)
Received: from xse254.mail2web.com ([66.113.196.254] helo=xse.mail2web.com) by mx148.antispamcloud.com with esmtp (Exim 4.89) (envelope-from <huitema@huitema.net>) id 1iXDoJ-000QxJ-L5 for quic@ietf.org; Wed, 20 Nov 2019 01:25:33 +0100
Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 47Hk4B09Zkz5ZGf for <quic@ietf.org>; Tue, 19 Nov 2019 16:25:30 -0800 (PST)
Received: from [10.5.2.49] (helo=xmail11.myhosting.com) by xsmtp21.mail2web.com with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1iXDoH-0003VN-TC for quic@ietf.org; Tue, 19 Nov 2019 16:25:29 -0800
Received: (qmail 3923 invoked from network); 20 Nov 2019 00:25:29 -0000
Received: from unknown (HELO [31.133.158.247]) (Authenticated-user:_huitema@huitema.net@[31.133.158.247]) (envelope-sender <huitema@huitema.net>) by xmail11.myhosting.com (qmail-ldap-1.03) with ESMTPA for <alexandre.ferrieux@orange.com>; 20 Nov 2019 00:25:29 -0000
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
From: Christian Huitema <huitema@huitema.net>
Mime-Version: 1.0 (1.0)
Subject: Re: Q and L loss bits: which is which?
Date: Wed, 20 Nov 2019 08:25:27 +0800
Message-Id: <9F90F822-7B26-4B59-9F6E-F43D7935867E@huitema.net>
References: <EFE60BCA-89EE-4A78-8E5B-EB8B8ED25DD9@trammell.ch>
Cc: "Lubashev, Igor" <ilubashe@akamai.com>, "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, IETF QUIC WG <quic@ietf.org>
In-Reply-To: <EFE60BCA-89EE-4A78-8E5B-EB8B8ED25DD9@trammell.ch>
To: "Brian Trammell (IETF)" <ietf@trammell.ch>
X-Mailer: iPhone Mail (17A878)
X-Originating-IP: 66.113.196.254
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.254/32
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.254/32@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0fIjBzH0XxYvWQgWH/ix0mSpSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDcnqpk5VeF3xR4kF6iVwRtbgN zB/4Jkrw1eDLcif59ftpG9/zGtVI2YbAW6fM7X/iU7Tmz6iKnkQL9gqsxD347235Nhqq+/HvroPq 8GSPg+60/QPNqXybIny9WGhadIo/ixIHpNwYH6dG/jiqllt/T7yme9ldZJ7uNXfg/GfS8fUvP/L5 rCqHDsKZM+xa1iwJX+gRCHfMVnsAk591zk0uilUI+ZL4xWiN8NS6C+dmX6OEdA4u1aThyWrQ/ou2 +v/lmX4Em37yFgrCB6NHRn1g+f3uncIqYSL3lhh5c81YyJqFoLZMmkWsaurVZfvqROaDnDtHb8z5 dpPkEuJ8Snwqla7jUnW3hy14Yji8fo+4xCnSRo4Rcu5Z37rMuDjCny5fE9ykbJ7I9co1MAEE3ruN Xsm8UJsAPvDcVSKtDCYkioPY5Qx4fJOk03R5fJtf/Dv/dkIzS7m4GUpXCY1Y3j3ileOfMnQTuxRu w7b3K/aRb5jEMDQiNsTxs76hah9Uw3RGHerzGYx3lbKcnUHqcAAMrw7bwXKhbO3XgEkM+HUxN0pk DBiQWxoMMt9CeSOhI+q1vuydj6574Qj/KQ6KJOr9yRg66gs5OuzYxJgw5atIxeNDvjI/CYe5WPy0 +t1RP0azkyYKiy9qNR2btN6gmm3rB5xMPnetLBJMh51NiRRoHIBYv+CNt6auslsbKXf9/qcQmiK7 x42VjdzChZMe6O/Did+/hGXTmfhE+Dx2/NyzMXoleVZgRNSf42vfZoEWDMFTvOnCUbNPgcPcQwzM gKHyQxUo+ql2ySTkvEFH/23XMww2BnTTFGX5/yI4Ky+1ZJcbGqc5H4PEZHeoI/d6LWFf332z7LMw LGdoi9FMQ5j9dQUvMi1YKAun15JQSJLyCT5k+MTObVKxHy/dols381l9r9ft9daDonlwd6LnuX+J u10=
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/reCfGh8Z8KDsyMVxWOIP_4OPRBQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 20 Nov 2019 00:25:39 -0000

>=20
> On Nov 20, 2019, at 8:16 AM, Brian Trammell (IETF) <ietf@trammell.ch> wrot=
e:
>=20
> =EF=BB=BFHi Igor, all,
>=20
> Sent from my iPhone
>=20
>> On 20 Nov 2019, at 07:56, Lubashev, Igor <ilubashe@akamai.com> wrote:
>>=20
>> Christian, I actually thought about this, and decided that the recommenda=
tion is not to decrement L counter.  It is in the -tsvwg- version of the dra=
ft but somehow did not have it into the -quic- version (keeping two versions=
 in sync is apparently hard), sorry. (https://tools.ietf.org/html/draft-ferr=
ieuxhamchaoui-tsvwg-lossbits-02#section-3.2)
>=20
> FWIW I agree that these are the right semantics.
>=20
> With these semantics, if I follow correctly, the L bit is basically signal=
ing that the sender has detected a loss _to which it will react_ (or rather,=
 to which it would react if it were already network limited), by reducing th=
e congestion window, updating its loss estimate or capacity model, or whatev=
er sending-rate-relevant parameters its congestion control and avoidance sch=
eme uses.=20
>=20
> This makes the condition it is signaling pretty close to the CWR bit (if t=
he CWR bit covered all such reactions, not just those triggered by ECN), whi=
ch is basically the proposal I (poorly and cryptically) alluded to in the is=
sue and the mic.
>=20
> (Two nice properties of exposing loss reaction as opposed to raw loss: one=
, you=E2=80=99re closer to measuring what you actually care about =E2=80=94 p=
oor transport performance =E2=80=94 and two, since the signal is correlated w=
ith the time series of the sending rate, statistical techniques are applicab=
le to verifying the signal: it=E2=80=99s harder to lie.)

OK, but if I determine that a loss is spurious I revert the congestion contr=
ol state to what it would be if the loss did not happen.=20



>=20
> Cheers, B
>=20
>> "
>> If the protocol is able to rescind the loss determination later, the Unre=
ported Loss counter SHOULD NOT be decremented due to the rescission.
>> "
>>=20
>> I thought this rule would limit the confusion of the observer who is tryi=
ng to correlate Q and L bits. I'm happy to hear alternative opinions on this=
.
>>=20

I am in the rescind case. But maintaining a single counter is simpler, so I w=
ill do that.

-- Christian=20


>> - Igor
>>=20
>>> -----Original Message-----
>>> From: Christian Huitema <huitema@huitema.net>
>>> Sent: Wednesday, November 20, 2019 7:19 AM
>>> To: alexandre.ferrieux@orange.com; IETF QUIC WG <quic@ietf.org>
>>> Subject: Re: Q and L loss bits: which is which?
>>>=20
>>> I am willing to do the same in Picoquic, but I would really like to get t=
he
>>> transport parameter defined first.
>>>=20
>>> Also, I would like some clarification. The loss counter is supposedly
>>> incremented using Quic's loss detection machinery, but the loss detectio=
n
>>> mechanism sometimes err on the false positive side. This is detected if a=
n ack
>>> arrive late for a packet that was supposed lost, and the loss is classif=
ied as
>>> spurious.
>>>=20
>>> Any guidance on how to handle spurious loss detection?
>>>=20
>>> -- Christian Huitema
>>>=20
>>>>> On 11/20/2019 3:26 AM, Dmitri Tikhonov wrote:
>>>>> I added a loss bits server on
>>>>>=20
>>>>>   http3-test.litespeedtech.com:4440
>>>>>=20
>>>>> Feel free to give it a shot!
>>>>>=20
>>>>> Both lsquic server and client can be compiled with loss bits support
>>>>> by doing
>>>>>=20
>>>>>   EXTRA_CLFAGS=3D-DLSQUIC_LOSS_BITS=3D1 cmake ....
>>>>>=20
>>>>> The code is on a branch for now:
>>>>>=20
>>>>>=20
>>>>>=20
>>> https://github.com/litespeedtech/lsquic/commit/0b83dfa304bcd9750b67e62
>>>> 97416ce493d9fb5b1
>>>>=20
>>>> - Dmitri.
>>>>=20
>>>>> On Tue, Nov 19, 2019 at 10:08:29AM -0500, Dmitri Tikhonov wrote:
>>>>> On Tue, Nov 19, 2019 at 03:49:08PM +0100,
>>> alexandre.ferrieux@orange.com wrote:
>>>>>> Thanks for your offer: experimentations are very welcome !
>>>>>> You're right we forgot to just define which is what, we'll fix the
>>>>>> draft shortly. We'll choose: 0x10 for Q and 0x08 for L.
>>>>>> This means the first byte layout becomes:
>>>>>> |0|1|S|Q|L|K|P P|
>>>>> Thank you!
>>>>>=20
>>>>> I also assume that these two bits would now be outside of the header
>>>>> protection?  That is, the short header header protection mask [1] is
>>>>> now 0x7 instead of 0x1F?  This is not mentioned in your draft, but I
>>>>> don't see how an observer could get at those bits otherwise.
>>>>>=20
>>>>> - Dmitri.
>>>>>=20
>>>>> 1. https://tools.ietf.org/html/draft-ietf-quic-tls-24#section-5.4.1
>>=20
>>=20
>=20


From nobody Tue Nov 19 16:37:08 2019
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 F132D120861 for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 16:37:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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=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 TfnToefvi8KW for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 16:37:05 -0800 (PST)
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 6AC2212018B for <quic@ietf.org>; Tue, 19 Nov 2019 16:37:05 -0800 (PST)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id xAK0Zoeq020886; Wed, 20 Nov 2019 00:37:04 GMT
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=5vrlzAmMmaiGgGXGz2BmSdKCmaBwf6/gEljxuloGmQs=; b=Uz6yTT51TiXe96T9E5eqcvV0E23QBnhecHemfXLXI11RnGfh2lamsG5Xn30u+e4d8kqC 9hhu8iJx2I7Mw8eHfLK/qXbu9B2R3OfKr/fL9KSrr2/ITyKxxAd1c9K022iA9xqNBv38 AvsIGDndtYqGBic+xOSXMyet8j8fyQrP/Xo5L66lpII0kS2Xp8/D7JedyvpZ/qD2oRC2 MTB2XWSOaSYfAjRUMsZXTEP7llqhhZLiMTYTrzx/Gq1D5ZLSLe4cTZMnKrpGC4HMIJOo xNu1HeebcG4Jvhtj3LhBKoZQwcQlYZlz6MrM0fQcjHadHPo08mXA6XA5HFsxp0AmXkAZ BQ== 
Received: from prod-mail-ppoint3 (prod-mail-ppoint3.akamai.com [96.6.114.86] (may be forged)) by m0050095.ppops.net-00190b01. with ESMTP id 2wafwvg0my-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 20 Nov 2019 00:37:04 +0000
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.27/8.16.0.27) with SMTP id xAK0WKlU023834; Tue, 19 Nov 2019 19:37:02 -0500
Received: from email.msg.corp.akamai.com ([172.27.165.114]) by prod-mail-ppoint3.akamai.com with ESMTP id 2wadb1s1hd-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 19 Nov 2019 19:37:02 -0500
Received: from USTX2EX-DAG1MB5.msg.corp.akamai.com (172.27.165.123) by ustx2ex-dag1mb5.msg.corp.akamai.com (172.27.165.123) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 19 Nov 2019 18:37:01 -0600
Received: from USTX2EX-DAG1MB5.msg.corp.akamai.com ([172.27.165.123]) by ustx2ex-dag1mb5.msg.corp.akamai.com ([172.27.165.123]) with mapi id 15.00.1473.005; Tue, 19 Nov 2019 18:37:01 -0600
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: Christian Huitema <huitema@huitema.net>, "Brian Trammell (IETF)" <ietf@trammell.ch>
CC: IETF QUIC WG <quic@ietf.org>, "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>
Subject: RE: Q and L loss bits: which is which?
Thread-Topic: Q and L loss bits: which is which?
Thread-Index: AQHVnuYxGYRqnRW1T0W5CpBoQ1gaSaeS98cAgAAFaICAAEgOgIAAQQmA//+iQwCAAG3AAIAAAoOA//+dbSA=
Date: Wed, 20 Nov 2019 00:37:01 +0000
Message-ID: <d699f1998e8a44109c5513f6e8a4fe55@ustx2ex-dag1mb5.msg.corp.akamai.com>
References: <EFE60BCA-89EE-4A78-8E5B-EB8B8ED25DD9@trammell.ch> <9F90F822-7B26-4B59-9F6E-F43D7935867E@huitema.net>
In-Reply-To: <9F90F822-7B26-4B59-9F6E-F43D7935867E@huitema.net>
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.216.50]
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=2019-11-19_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=701 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140001 definitions=main-1911200004
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-11-19_08:2019-11-15,2019-11-19 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 lowpriorityscore=0 priorityscore=1501 phishscore=0 clxscore=1011 mlxlogscore=671 impostorscore=0 suspectscore=0 bulkscore=0 malwarescore=0 adultscore=0 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1911200003
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/a17u7-Zm99M0dJ0TqpLxqkG7iC0>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 20 Nov 2019 00:37:07 -0000

PiBPbiBXZWQsIE5vdiAyMCwgMjAxOSBhdCA4OjI1IEFNLCBDaHJpc3RpYW4gSHVpdGVtYSA8aHVp
dGVtYUBodWl0ZW1hLm5ldD4gd3JvdGU6DQo+DQo+IE9LLCBidXQgaWYgSSBkZXRlcm1pbmUgdGhh
dCBhIGxvc3MgaXMgc3B1cmlvdXMgSSByZXZlcnQgdGhlIGNvbmdlc3Rpb24gY29udHJvbA0KPiBz
dGF0ZSB0byB3aGF0IGl0IHdvdWxkIGJlIGlmIHRoZSBsb3NzIGRpZCBub3QgaGFwcGVuLg0KDQpP
aywgSSB0aGluayB0aGVyZSBpcyBhIGJldHRlciBtaWRkbGUgZ3JvdW5kLiAgSWYgdGhlIGNvdW50
ZXIgaXMgPiAwLCBzdXJlLCBkZWNyZW1lbnQgaXQgKHNpbmNlIHRoZSBsb3NzIGhhcyBub3QgeWV0
IGJlZW4gcmVwb3J0ZWQpLiAgQnV0IGlmIHRoZSBjb3VudGVyIGlzIGFscmVhZHkgMCwgZG8gbm90
IGxldCBpdCBnbyBuZWdhdGl2ZSwgYmVjYXVzZSB0aGVuIHlvdSB3b3VsZCBub3QgYmUgYWJsZSB0
byByZXBvcnQgYW4gYWN0dWFsIGZ1dHVyZSBsb3NzIGV2ZW50IChhbmQgYW4gYWN0dWFsIGZ1dHVy
ZSBjb25nZXN0aW9uIGNvbnRyb2xsZXIgcmVzcG9uc2UpLg0KDQotIElnb3INCg==


From nobody Tue Nov 19 17:48:57 2019
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 02C3A12093B for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 17:48:55 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 F80lA5RGBevc for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 17:48:53 -0800 (PST)
Received: from mail-qt1-x831.google.com (mail-qt1-x831.google.com [IPv6:2607:f8b0:4864:20::831]) (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 7451D12092A for <quic@ietf.org>; Tue, 19 Nov 2019 17:48:53 -0800 (PST)
Received: by mail-qt1-x831.google.com with SMTP id t20so27123133qtn.9 for <quic@ietf.org>; Tue, 19 Nov 2019 17:48:53 -0800 (PST)
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=7tlHXPdxdRI6LTbixIbcbE5VcvRYjYoXHU01kT2gaX8=; b=qS5DNJksfRESGKD+cD8EN3xXvgwDcMG67YgogZK+N+BurIRDKFHzQsoj1KB2SvuJBo weaS3cWQEN65JuZ0GuNbPp1GR9b3ASTZLCkXihsFI+Anrp9irFAOlYRxpF0eblTXjGFO PWbUK7IBu4mcB9spDkHiYf586GIQFgTFadY7BB/hjdCdBZ64JuoLN9SziqeCnSA8kNGe qweXyGxlMn34FZ4LuY6wF5+i5gVRD9OJhL6txCn0HTgQl42mqg8tiQcwEzXTv4PmASDo A+WgXLPPqG2IPz6ci7Ly9qIciTEDJOVB10cMXbTB5eZwuA2z3HUV16YYsU72Va1l0sJq 6iGA==
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=7tlHXPdxdRI6LTbixIbcbE5VcvRYjYoXHU01kT2gaX8=; b=LFvzdD9/WlESdM0XVxdXCGomEutzElemFJmrjjcj9qnxZbC71WZz5s9hNr6VjLDkP+ qwGXobMjl7Y/5fq5K4gkuAJK30yh6f7bVLxPj4asWqp0VqG+40C+y64aRNeyMMZObErt N+SPha/nLSlozzuylz712yQI9ww5gFHMPSAjbAoMbK3/3mtEOGTtqIgexIfwDGhAxmuj +m+MwwW3NpEI7HvUOpvKvsB1+SF41x3+HneUxGaIOwW3oWaLnED+pEfoysmXqQaxJT06 k+RlUl2ki3W5eVVmsnhnqoY7rEpJtFPMhTJsQX+QfADZbGVLEYctsunxXvNjMB6yj8e7 365g==
X-Gm-Message-State: APjAAAVuqlx4hr46Bx7oNYftybvqF0FN6zZUEtLnbgWpU/ixUJ6zg2hP QzwYL4qB4HyMuwmkoJuiPNLlzw==
X-Google-Smtp-Source: APXvYqyjTKfZDEsWtKhQkExtZ3njGQMCV5+rWRCCtg3Zq8ylLNzbxCWxYnf+EY29VjSv0ZaqEkDosg==
X-Received: by 2002:ac8:3209:: with SMTP id x9mr330502qta.293.1574214532494; Tue, 19 Nov 2019 17:48:52 -0800 (PST)
Received: from ubuntu-dmitri (ool-44c1d219.dyn.optonline.net. [68.193.210.25]) by smtp.gmail.com with ESMTPSA id w23sm13904214qtw.87.2019.11.19.17.48.52 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 19 Nov 2019 17:48:52 -0800 (PST)
Date: Tue, 19 Nov 2019 20:48:50 -0500
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Christian Huitema <huitema@huitema.net>
Cc: alexandre.ferrieux@orange.com, IETF QUIC WG <quic@ietf.org>
Subject: Re: Q and L loss bits: which is which?
Message-ID: <20191120014850.GC16017@ubuntu-dmitri>
Mail-Followup-To: Christian Huitema <huitema@huitema.net>, alexandre.ferrieux@orange.com, IETF QUIC WG <quic@ietf.org>
References: <20191119143218.GB2789@ubuntu-dmitri> <24388_1574174932_5DD400D4_24388_372_7_1574174948.30247.49.camel@orange.com> <20191119150829.GD2789@ubuntu-dmitri> <20191119192622.GE2789@ubuntu-dmitri> <a21bc373-1fda-836e-7efc-599832ae575d@huitema.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <a21bc373-1fda-836e-7efc-599832ae575d@huitema.net>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/W75mWl52BDx78WVqfEdDq94YAZQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 20 Nov 2019 01:48:55 -0000

On Wed, Nov 20, 2019 at 07:19:09AM +0800, Christian Huitema wrote:
> I am willing to do the same in Picoquic, but I would really like to get
> the transport parameter defined first.

Once there is a TP and a draft, we plan to include this option into
main line of lsquic.

  - Dmitri.


From nobody Tue Nov 19 18:06:21 2019
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 811171207FF for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 18:06:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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=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 8bMBv1wnkQJx for <quic@ietfa.amsl.com>; Tue, 19 Nov 2019 18:06:18 -0800 (PST)
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 58D5C12012C for <quic@ietf.org>; Tue, 19 Nov 2019 18:06:17 -0800 (PST)
Received: from pps.filterd (m0050095.ppops.net [127.0.0.1]) by m0050095.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id xAK260ZH030108; Wed, 20 Nov 2019 02:06:16 GMT
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=DoV/mmYPRzRnkUTv5dy0KqBp8ovMdC66QaNQ2fRlxXs=; b=GS9lvcpQoyFGPZ745CHSxrvNpeZ2mMAf927lTBPp48F/IwpMpLZVQJ+X01JE+WpyVyqD tpfNmERdHYS0kf/pe3bKy5BkZmuECOGjqmTmE/v7jV1oJLY5JAGrrrWo3nExIzyJyXR/ Y5woYYiFy7bzkIDZBTsso+HSqOuBNy+knafunBdeb6h+2HzuEJbWi3VlH1YCu5gVA0IY j81RjNwBciCTT+CyrT3JZrAzL3imHywgN67DPEIO9mnins4E4ecoVz8yFkh5BrAnF5D0 7bSb8UOVamEV3VVBa/3TlXkk96Md2+2lLDuOIlDKI0nWxSuUU2IGgcXDlvR1+MgI9hOI 0g== 
Received: from prod-mail-ppoint3 (prod-mail-ppoint3.akamai.com [96.6.114.86] (may be forged)) by m0050095.ppops.net-00190b01. with ESMTP id 2wafwvgam1-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Wed, 20 Nov 2019 02:06:16 +0000
Received: from pps.filterd (prod-mail-ppoint3.akamai.com [127.0.0.1]) by prod-mail-ppoint3.akamai.com (8.16.0.27/8.16.0.27) with SMTP id xAK22sM6008781; Tue, 19 Nov 2019 21:06:15 -0500
Received: from email.msg.corp.akamai.com ([172.27.165.116]) by prod-mail-ppoint3.akamai.com with ESMTP id 2wadb1tbk4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Tue, 19 Nov 2019 21:06:14 -0500
Received: from USTX2EX-DAG1MB5.msg.corp.akamai.com (172.27.165.123) by ustx2ex-dag1mb2.msg.corp.akamai.com (172.27.165.120) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Tue, 19 Nov 2019 20:06:12 -0600
Received: from USTX2EX-DAG1MB5.msg.corp.akamai.com ([172.27.165.123]) by ustx2ex-dag1mb5.msg.corp.akamai.com ([172.27.165.123]) with mapi id 15.00.1473.005; Tue, 19 Nov 2019 20:06:12 -0600
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Christian Huitema <huitema@huitema.net>
CC: IETF QUIC WG <quic@ietf.org>, "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>
Subject: RE: Q and L loss bits: which is which?
Thread-Topic: Q and L loss bits: which is which?
Thread-Index: AQHVnuYxGYRqnRW1T0W5CpBoQ1gaSaeS98cAgAAFaICAAEgOgIAAQQmAgAAp0gD//58nEA==
Date: Wed, 20 Nov 2019 02:06:11 +0000
Message-ID: <cd2e9389a61d49eabad2b0fac2f4db96@ustx2ex-dag1mb5.msg.corp.akamai.com>
References: <20191119143218.GB2789@ubuntu-dmitri> <24388_1574174932_5DD400D4_24388_372_7_1574174948.30247.49.camel@orange.com> <20191119150829.GD2789@ubuntu-dmitri> <20191119192622.GE2789@ubuntu-dmitri> <a21bc373-1fda-836e-7efc-599832ae575d@huitema.net> <20191120014850.GC16017@ubuntu-dmitri>
In-Reply-To: <20191120014850.GC16017@ubuntu-dmitri>
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.216.181]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-11-19_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=903 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140001 definitions=main-1911200019
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-11-19_08:2019-11-15,2019-11-19 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 lowpriorityscore=0 priorityscore=1501 phishscore=0 clxscore=1011 mlxlogscore=873 impostorscore=0 suspectscore=0 bulkscore=0 malwarescore=0 adultscore=0 mlxscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1911200018
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/BJxs-uUWucLHvN0ioS2D8UJrRWk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 20 Nov 2019 02:06:19 -0000

> On Wed, Nov 20, 2019 at 9:49 AM, Dmitri Tikhonov <dtikhonov@litespeedtech=
.com> wrote:
>=20
> On Wed, Nov 20, 2019 at 07:19:09AM +0800, Christian Huitema wrote:
> > I am willing to do the same in Picoquic, but I would really like to
> > get the transport parameter defined first.
>=20
> Once there is a TP and a draft, we plan to include this option into main =
line of
> lsquic.

Thanks, Dmitri and Christian.  We are getting great feedback now, which we =
are absorbing.  Plus, there are privacy guidelines to carefully consider an=
d refine.  So I'd expect a draft in about 2-3 weeks.

- Igor


From nobody Tue Nov 19 18:43:06 2019
Return-Path: <Nicolas.Kuhn@cnes.fr>
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 7D10C1201E0; Tue, 19 Nov 2019 18:42:53 -0800 (PST)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 lLn8Hea0FylL; Tue, 19 Nov 2019 18:42:50 -0800 (PST)
Received: from mx2.cnes.fr (mx2.cnes.fr [194.199.174.201]) (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 DFE9E120220; Tue, 19 Nov 2019 18:42:49 -0800 (PST)
X-IronPort-AV: E=Sophos; i="5.69,220,1571702400"; d="scan'208,217"; a="30974844"
X-IPAS-Result: =?us-ascii?q?A2HCAwB2ptRd/wIBeAplHAEBAQEBBwEBEQEEBAEBgX6BH?= =?us-ascii?q?IFdE4ExCqhZiAsJAQEBAQEBAQEBNwEBhEACgko4EwIQAQEBBAEBAQEBBQIBA?= =?us-ascii?q?QIChVRYhikBMEELEgEVFR05FBIBBAENBQgTgwiBebQKGoNzAYY8gTaBZYoTg?= =?us-ascii?q?jSBEUaBTlCFM4NAgiwEjVOIA5hTB4E8cgOCNJMzdYFJh2iEJwOHBYQ8jkicG?= =?us-ascii?q?U2BLjMaJ0yCbFARap5TATZ0jiqBDwEB?=
X-URL-LookUp-ScanningError: 1
From: Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>
To: "etosat@ietf.org" <etosat@ietf.org>, "iccrg@irtf.org" <iccrg@irtf.org>, IETF QUIC WG <quic@ietf.org>, "nwcrg@irtf.org" <nwcrg@irtf.org>, "dtn@ietf.org" <dtn@ietf.org>
CC: G Fairhurst <gorry@erg.abdn.ac.uk>, 'STEPHAN Emile RD-CORE-LAN' <emile.stephan@orange.com>
Subject: Side meeting on QUIC performance over high BDP networks
Thread-Topic: Side meeting on QUIC performance over high BDP networks
Thread-Index: AdWfSmKmhf9YofXhT8ubjjpspqEzKw==
Date: Wed, 20 Nov 2019 02:41:45 +0000
Deferred-Delivery: Wed, 20 Nov 2019 02:42:40 +0000
Message-ID: <F3B0A07CFD358240926B78A680E166FF1ED02F8B@TW-MBX-P03.cnesnet.ad.cnes.fr>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-tm-as-product-ver: SMEX-11.0.0.4255-8.100.1062-25054.003
x-tm-as-result: No--14.790100-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_F3B0A07CFD358240926B78A680E166FF1ED02F8BTWMBXP03cnesnet_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/AcLVRgRDxq3vB9lqjji-3d5fI28>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 20 Nov 2019 02:42:54 -0000

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

Hi,

Satellites are fun and we are sending bits in space ! However, this can com=
e with some challenges.
To speak about these challenges, we are organizing a side meeting on QUIC p=
erformance over high BDP networks :
               Today at 3pm30 in Bras Basah

=3D=3D Objective =3D=3D
There are multiple drafts related to the performance of QUIC over large BDP=
 networks (draft -kuhn-quic-4-sat, draft-kuhn-quic-0rtt-bdp, draft-ietf-qui=
c-recovery) or related to the performance of encrypted protocols in general=
 (draft-fairhurst-tsvwg-cc). The objective of this workshop is to gather pe=
ople interested in such activity and discuss the best way towards better en=
d user experience in this use case.

=3D=3D Agenda =3D=3D
High BDP : focus on SATCOM challenges for QUIC
Challenge : SWOT analysis of QUIC in SATCOM
What are the problems ?
What are our options to go forward ?
Any other activity on QUIC over SATCOM we are/were not aware of ?
Open questions for discussion

=3D=3D Remote participation =3D=3D
We are working on a solution for potential remote participants.
If you are interested in remote participation, please let us know.
The meeting will not be recorded, but meeting material will be shared (see =
below).

=3D=3D Meeting material =3D=3D
Meeting material (slides and minutes) will be sent to the etosat@ietf.org<m=
ailto:etosat@ietf.org> mailing list.
Join the mailing list if you are interested.

Thanks,

Nico, Gorry and Emile


--_000_F3B0A07CFD358240926B78A680E166FF1ED02F8BTWMBXP03cnesnet_
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:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
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-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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"FR" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi, <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Satellites are fun and we are s=
ending bits in space ! However, this can come with some challenges.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">To speak about these challenges=
, we are organizing a side meeting on QUIC performance over high BDP networ=
ks :
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Today at 3pm30 in Bra=
s Basah<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=3D=3D Objective =3D=3D <o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">There are multiple drafts relat=
ed to the performance of QUIC over large BDP networks (draft -kuhn-quic-4-s=
at, draft-kuhn-quic-0rtt-bdp, draft-ietf-quic-recovery) or related to the p=
erformance of encrypted protocols in
 general (draft-fairhurst-tsvwg-cc). The objective of this workshop is to g=
ather people interested in such activity and discuss the best way towards b=
etter end user experience in this use case.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=3D=3D Agenda =3D=3D <o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">High BDP : focus on SATCOM chal=
lenges for QUIC<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Challenge : SWOT analysis of QU=
IC in SATCOM<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">What are the problems ? <o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">What are our options to go forw=
ard ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Any other activity on QUIC over=
 SATCOM we are/were not aware of ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Open questions for discussion<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=3D=3D Remote participation =3D=
=3D <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">We are working on a solution fo=
r potential remote participants.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">If you are interested in remote=
 participation, please let us know.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The meeting will not be recorde=
d, but meeting material will be shared (see below).
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=3D=3D Meeting material =3D=3D<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Meeting material (slides and mi=
nutes) will be sent to the
<a href=3D"mailto:etosat@ietf.org">etosat@ietf.org</a> mailing list. <o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Join the mailing list if you ar=
e interested.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thanks, <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"mso-fareast-language:F=
R">Nico, Gorry and Emile<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_F3B0A07CFD358240926B78A680E166FF1ED02F8BTWMBXP03cnesnet_--


From nobody Wed Nov 20 04:05:11 2019
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 0754B120052 for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 04:05:10 -0800 (PST)
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_HELO_NONE=0.001, 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 dHnkFdJC1Qsj for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 04:05:08 -0800 (PST)
Received: from mail-lj1-x235.google.com (mail-lj1-x235.google.com [IPv6:2a00:1450:4864:20::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 E0E56120043 for <quic@ietf.org>; Wed, 20 Nov 2019 04:05:07 -0800 (PST)
Received: by mail-lj1-x235.google.com with SMTP id v8so27231116ljh.5 for <quic@ietf.org>; Wed, 20 Nov 2019 04:05:07 -0800 (PST)
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;  bh=IRCAVRVx2xZ9Ser6y5Ty8HzsoT2n/9yLjSLE1lkGYHU=; b=Sq0h7aDIL+ADyt631yeYZEOoxhrP3BcEh+DnvhunEg5ykokKxhBTZ71If0h6JDAUhv fVkILOqU2gatrFgIVzdPgA4HUAPK51tmttO/VE8K+aiVt1dBIXdraON2vsCrEd2mqvFD cOnjs+qP/uBPRbIviNFmvdP6jigEwnutaQv7dXZN/Aw0Ft8IYz/WQCmYSF/8MJmLjzrk WYAk0kDQYwV4xFv0dRwNNhd/foOpx4Wd+7OLIBGLvNkfxH0KyiAKGUrMD1cei2g8PXpY YXGqveIgu9rrbUX5UC4fNCcnPwDUSkBcow8KRhtw/UxVzEEggFqzjCN0HCBcxcl/LdUF o58w==
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; bh=IRCAVRVx2xZ9Ser6y5Ty8HzsoT2n/9yLjSLE1lkGYHU=; b=AIArp3pEwAlnG6BAWP23hupibKO4fdBCQRWmlq253M6nPEelWVOiMtcjbHUfawr2Q5 /nGgZO3izzXWD2Komx7OBXNSimN0oQ8l/Ly2lwYYHodHt+xabW4KyKrf4MxD7UN41l7G BBx108x4ZdXCcGf+Rxt8veWUmQv2IQhRybxfT5OGDJLAgPAo8RnKKDsD+gGo6acvTbBl 75wUQ33plOCmd+Y+iqjxqWwoRXRStXE7A4ABM1U876X7eGINO3bOXxKI5iOtnzXOj0DF ewC1mdlNDXA6QfX13ArK2T3vlTYKHIoqFaBzdudffqAa7HirpcMVBafpJbLLhJH1EGQP qGFQ==
X-Gm-Message-State: APjAAAXic9i9J1300QI73/byaiUFnsVsyUklC8CcPqHRbR/GAMRqfuBM i1h5tfbcN2XC8XN7WjvvTMKvZJqDrsRaSyG2gKqEHlnqcbMcqg==
X-Google-Smtp-Source: APXvYqz5g+NxpQoOAEfiaCX232tIUiBp++XH2FgHXPCQazkuOzHonPWicZ0qIgub5qNNMLo+1Ca/2BWjyNEXMN340FY=
X-Received: by 2002:a2e:9c8f:: with SMTP id x15mr2461521lji.204.1574251506143;  Wed, 20 Nov 2019 04:05:06 -0800 (PST)
MIME-Version: 1.0
References: <157425081947.30550.7403247942771684795.idtracker@ietfa.amsl.com>
In-Reply-To: <157425081947.30550.7403247942771684795.idtracker@ietfa.amsl.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Wed, 20 Nov 2019 20:04:54 +0800
Message-ID: <CANatvzyk6xaDby-VVvtuOJ66=YPMqynB9=WMAMxYPxGXYa=BPA@mail.gmail.com>
Subject: Priorities I-D for Thursday HTTPbis meeting (Fwd: New Version Notification for draft-kazuho-httpbis-priority-04.txt)
To: HTTP Working Group <ietf-http-wg@w3.org>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000cf998b0597c5fd6c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/3fUNTSTU30mmMf4v9qgwh7-xofo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 20 Nov 2019 12:05:10 -0000

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

Dear working groups members,

After the HTTPbis meeting on Monday, the priorities design team as well as
others have had discussions, and have converged on a particular design
(header-based, as well as allowing intermediaries to send frames to express
per-hop priorities).

We have submitted a new revision of the I-D that reflects the emerging
consensus, that clarifies more about the corner cases and how they should
be handled.

It can be found at:
https://tools.ietf.org/html/draft-kazuho-httpbis-priority-04
HTML version is:
https://kazuho.github.io/draft-kazuho-httpbis-priority/draft-kazuho-httpbis=
-priority.html

We have asked chairs to give us some time in tomorrow's HTTPbis meeting
that we can use to provide an update on the status.

We are looking forward to hearing your comments either face-to-face, or on
the mailing list.

Thank you in advance.

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: 2019=E5=B9=B411=E6=9C=8820=E6=97=A5(=E6=B0=B4) 19:53
Subject: New Version Notification for draft-kazuho-httpbis-priority-04.txt
To: Kazuho Oku <kazuhooku@gmail.com>, Lucas Pardue <
lucaspardue.24.7@gmail.com>



A new version of I-D, draft-kazuho-httpbis-priority-04.txt
has been successfully submitted by Kazuho Oku and posted to the
IETF repository.

Name:           draft-kazuho-httpbis-priority
Revision:       04
Title:          Extensible Prioritization Scheme for HTTP
Document date:  2019-11-20
Group:          Individual Submission
Pages:          20
URL:
https://www.ietf.org/internet-drafts/draft-kazuho-httpbis-priority-04.txt
Status:
https://datatracker.ietf.org/doc/draft-kazuho-httpbis-priority/
Htmlized:       https://tools.ietf.org/html/draft-kazuho-httpbis-priority-0=
4
Htmlized:
https://datatracker.ietf.org/doc/html/draft-kazuho-httpbis-priority
Diff:
https://www.ietf.org/rfcdiff?url2=3Ddraft-kazuho-httpbis-priority-04

Abstract:
   This document describes a scheme for prioritizing HTTP responses.
   This scheme expresses the priority of each HTTP response using
   absolute values, rather than as a relative relationship between a
   group of HTTP responses.

   This document defines the Priority header field for communicating the
   initial priority in an HTTP version-independent manner, as well as
   HTTP/2 and HTTP/3 frames for reprioritizing the responses.  These
   share a common format structure that is designed to provide future
   extensibility.




Please note that it may take a couple of minutes from the time of submissio=
n
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat



--=20
Kazuho Oku

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

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr">Dear working groups memb=
ers,<div><br></div><div>After the HTTPbis meeting on Monday, the priorities=
 design team as well as others have had discussions, and have converged on =
a particular design (header-based, as well as allowing intermediaries to se=
nd frames to express per-hop priorities).</div><div><br></div><div>We have =
submitted a new revision of the I-D that reflects the emerging consensus, t=
hat clarifies more about the corner cases and how they should be handled.</=
div><div><br></div><div>It can be found at: <a href=3D"https://tools.ietf.o=
rg/html/draft-kazuho-httpbis-priority-04">https://tools.ietf.org/html/draft=
-kazuho-httpbis-priority-04</a></div><div>HTML version is:=C2=A0<a href=3D"=
https://kazuho.github.io/draft-kazuho-httpbis-priority/draft-kazuho-httpbis=
-priority.html">https://kazuho.github.io/draft-kazuho-httpbis-priority/draf=
t-kazuho-httpbis-priority.html</a></div><div><br></div><div>We have asked c=
hairs to give us some time in tomorrow&#39;s HTTPbis meeting that we can us=
e to provide an update on the status.</div><div><br></div><div>We are looki=
ng forward to hearing your comments either face-to-face, or on the mailing =
list.</div><div><br></div><div>Thank you in advance.</div><div><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">---------- Forward=
ed message ---------<br>From: <span dir=3D"auto">&lt;<a href=3D"mailto:inte=
rnet-drafts@ietf.org">internet-drafts@ietf.org</a>&gt;</span><br>Date: 2019=
=E5=B9=B411=E6=9C=8820=E6=97=A5(=E6=B0=B4) 19:53<br>Subject: New Version No=
tification for draft-kazuho-httpbis-priority-04.txt<br>To: Kazuho Oku &lt;<=
a href=3D"mailto:kazuhooku@gmail.com">kazuhooku@gmail.com</a>&gt;, Lucas Pa=
rdue &lt;<a href=3D"mailto:lucaspardue.24.7@gmail.com">lucaspardue.24.7@gma=
il.com</a>&gt;<br></div><br><br><br>
A new version of I-D, draft-kazuho-httpbis-priority-04.txt<br>
has been successfully submitted by Kazuho Oku and posted to the<br>
IETF repository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0draft-kazuho-httpbis-priority=
<br>
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A004<br>
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Extensible Prioritization Scheme f=
or HTTP<br>
Document date:=C2=A0 2019-11-20<br>
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual Submission<br>
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 20<br>
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.ietf.o=
rg/internet-drafts/draft-kazuho-httpbis-priority-04.txt" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/internet-drafts/draft-kazuho-httpbi=
s-priority-04.txt</a><br>
Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.iet=
f.org/doc/draft-kazuho-httpbis-priority/" rel=3D"noreferrer" target=3D"_bla=
nk">https://datatracker.ietf.org/doc/draft-kazuho-httpbis-priority/</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/html/=
draft-kazuho-httpbis-priority-04" rel=3D"noreferrer" target=3D"_blank">http=
s://tools.ietf.org/html/draft-kazuho-httpbis-priority-04</a><br>
Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.ietf.org=
/doc/html/draft-kazuho-httpbis-priority" rel=3D"noreferrer" target=3D"_blan=
k">https://datatracker.ietf.org/doc/html/draft-kazuho-httpbis-priority</a><=
br>
Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.ietf.o=
rg/rfcdiff?url2=3Ddraft-kazuho-httpbis-priority-04" rel=3D"noreferrer" targ=
et=3D"_blank">https://www.ietf.org/rfcdiff?url2=3Ddraft-kazuho-httpbis-prio=
rity-04</a><br>
<br>
Abstract:<br>
=C2=A0 =C2=A0This document describes a scheme for prioritizing HTTP respons=
es.<br>
=C2=A0 =C2=A0This scheme expresses the priority of each HTTP response using=
<br>
=C2=A0 =C2=A0absolute values, rather than as a relative relationship betwee=
n a<br>
=C2=A0 =C2=A0group of HTTP responses.<br>
<br>
=C2=A0 =C2=A0This document defines the Priority header field for communicat=
ing the<br>
=C2=A0 =C2=A0initial priority in an HTTP version-independent manner, as wel=
l as<br>
=C2=A0 =C2=A0HTTP/2 and HTTP/3 frames for reprioritizing the responses.=C2=
=A0 These<br>
=C2=A0 =C2=A0share a common format structure that is designed to provide fu=
ture<br>
=C2=A0 =C2=A0extensibility.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of submissio=
n<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br>
</div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr" class=3D"gma=
il_signature">Kazuho Oku</div></div></div></div></div>

--000000000000cf998b0597c5fd6c--


From nobody Wed Nov 20 04:57:28 2019
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 D5B6512081A for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 04:57:26 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.996
X-Spam-Level: 
X-Spam-Status: No, score=-1.996 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_HELO_NONE=0.001, 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 yRTH-AR2dzYY for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 04:57:24 -0800 (PST)
Received: from mail-ed1-x534.google.com (mail-ed1-x534.google.com [IPv6:2a00:1450:4864:20::534]) (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 7DA3712004D for <quic@ietf.org>; Wed, 20 Nov 2019 04:57:23 -0800 (PST)
Received: by mail-ed1-x534.google.com with SMTP id m13so20174589edv.9 for <quic@ietf.org>; Wed, 20 Nov 2019 04:57:23 -0800 (PST)
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=TXNacDotYymF7FGscS+0Ddv7TuIk6/yokRqMtfIdYzk=; b=NWDZMAvcJFdzBHeWFjbux7IGE9jMv7maEd8FJaw2ZYNtvX/xYJB7teR7CAmoVC9Ade JDl9TSdM8NBOfY5aaiqDxfk9VJ/rPfXtT9TWXyM2s84iK0RwiNc/lxmNr0nAyInH0nFp Og2J8wvMAU+SQgC999sv+pWWpBTPg04/WI9mj/QHviSEevJ+QK+LED0k4uAc5SQpiAhC oSN3xxxWXVTP9mnxGqucffq0Na7O81FbB4+eg9+lFoZJuoq2KC4VEZYpeTTO9BGceWaY 8lbpI5I/9DoHZ/ZlmECQW3GaAjRgKW77jJRl/i/OgYhcRRUw1aiPqt29IuUg2AiqjcL4 ZoMA==
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=TXNacDotYymF7FGscS+0Ddv7TuIk6/yokRqMtfIdYzk=; b=j82DlBiif+DLm/zii6Nn6Yl72Qlnakqb9QbMZEF1jvalmNB3Z4hZT29saJqXy7RRav m6sk1wYI0iRjJTffcz6zB8P4JSUcdw44YMluWkBLemJfuE4o4vmbDez/AJ+dEWIFqyz1 oRMwAU0PYYjTZRjksckzZbrDhwwStXZrWLYgnTHXKQrZxyS+9h4mjpYWo6OitUHhD8XS VG7F0pOayQLik7WfWQCpfdm0oi/BtmLCPBnVcI5h9EzW5WDIMZ/Fs4arBt2DaIZiPwPv GrgKjGbcmRxdPmNTye5WXzCE9UeQQ4Q6pGTvZ3ae1OQWY2rNHfxBrX9RMYtSXKPSAmMD Q6uA==
X-Gm-Message-State: APjAAAXhWrE/yZXYHBVW5wYrqDz+AhnFvfSbuUJ5n37sZYpxni1caErZ HP+3QgZ7T4twUad+3H7pkhvwAezKGW/FfklT8jXnLzPq
X-Google-Smtp-Source: APXvYqzBFCK0TDa6A44Wb7eX7aUFSCYpDkJ9KrpfMqVo1Zq/2Y/F3ieFed5yXsM2HhYtPcFhTSiMTLcTjlPwWeAJG28=
X-Received: by 2002:a17:906:4d93:: with SMTP id s19mr5180881eju.285.1574254641824;  Wed, 20 Nov 2019 04:57:21 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Wed, 20 Nov 2019 04:57:20 -0800
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <CANatvzyk6xaDby-VVvtuOJ66=YPMqynB9=WMAMxYPxGXYa=BPA@mail.gmail.com>
References: <157425081947.30550.7403247942771684795.idtracker@ietfa.amsl.com> <CANatvzyk6xaDby-VVvtuOJ66=YPMqynB9=WMAMxYPxGXYa=BPA@mail.gmail.com>
MIME-Version: 1.0
Date: Wed, 20 Nov 2019 04:57:20 -0800
Message-ID: <CAN1APddw53xtus9Z86H4rw2CRXA3MR+fxhLWPf3Bh_=qB-O7Aw@mail.gmail.com>
Subject: Re: Priorities I-D for Thursday HTTPbis meeting (Fwd: New Version Notification for draft-kazuho-httpbis-priority-04.txt)
To: HTTP Working Group <ietf-http-wg@w3.org>, IETF QUIC WG <quic@ietf.org>, Kazuho Oku <kazuhooku@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000b649b80597c6b892"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/DtT_JyVo3G6o9rtxGVudSrx2dGM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 20 Nov 2019 12:57:27 -0000

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

Looking forward to digging further into this.

This is not a feedback in the actual design, only the document structure
and presentation. While this may come across a bit negative, I=E2=80=99m re=
ally
happy with simplifying the priority scheme of HTTP/2..

Some quick observation when approaching the document initially. I writing
this before having a full grasp of the concepts because that is the only
time to provide a newcomer perspective.

I think the document could be reorganised and much earlier specify how it
achieves prioritisation and use less text (initially) on HTTP/2 by mere
stating the the scheme can work with both HTTP/1, 2, 3 and possibly future
versions while stating that special mechanisms can be used to opt-out of
existing HTTP/2, and leave it at that.

After reading 1/3 of document, I still have no clue how the priority scheme
works (except I have some guess based on earlier ideas that have floatet)
and I have had to deal with a lot of HTTP/2 legacy that I am not
necessarily interested in. HTTP/3 doc has also move away from implicit
HTTP/2 familiarity, at least last time I checked.

The document talks about intermediate hop reprioritisation without making
clear what that is or what purpose it serves. I can only assume load
balancers and reverse proxies. From a QUIC background that also leaves me
wondering what that means - since each hop is necessarily also end to end,
unless there is an extension wrapper frame, but that makes no sense.

Once I got to the business end of the document, the document starts by
telling which headers not send when it is not at all clear what those
headers are about in th first place.

It=E2=80=99s also confusing what a protocol specific frame means, or why it=
 cannot
all be done with HTTP headers.



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


On 20 November 2019 at 13.05.19, Kazuho Oku (kazuhooku@gmail.com) wrote:

Dear working groups members,

After the HTTPbis meeting on Monday, the priorities design team as well as
others have had discussions, and have converged on a particular design
(header-based, as well as allowing intermediaries to send frames to express
per-hop priorities).

We have submitted a new revision of the I-D that reflects the emerging
consensus, that clarifies more about the corner cases and how they should
be handled.

It can be found at:
https://tools.ietf.org/html/draft-kazuho-httpbis-priority-04
HTML version is:
https://kazuho.github.io/draft-kazuho-httpbis-priority/draft-kazuho-httpbis=
-priority.html

We have asked chairs to give us some time in tomorrow's HTTPbis meeting
that we can use to provide an update on the status.

We are looking forward to hearing your comments either face-to-face, or on
the mailing list.

Thank you in advance.

---------- Forwarded message ---------
From: <internet-drafts@ietf.org>
Date: 2019=E5=B9=B411=E6=9C=8820=E6=97=A5(=E6=B0=B4) 19:53
Subject: New Version Notification for draft-kazuho-httpbis-priority-04.txt
To: Kazuho Oku <kazuhooku@gmail.com>, Lucas Pardue <
lucaspardue.24.7@gmail.com>



A new version of I-D, draft-kazuho-httpbis-priority-04.txt
has been successfully submitted by Kazuho Oku and posted to the
IETF repository.

Name:           draft-kazuho-httpbis-priority
Revision:       04
Title:          Extensible Prioritization Scheme for HTTP
Document date:  2019-11-20
Group:          Individual Submission
Pages:          20
URL:
https://www.ietf.org/internet-drafts/draft-kazuho-httpbis-priority-04.txt
Status:
https://datatracker.ietf.org/doc/draft-kazuho-httpbis-priority/
Htmlized:       https://tools.ietf.org/html/draft-kazuho-httpbis-priority-0=
4
Htmlized:
https://datatracker.ietf.org/doc/html/draft-kazuho-httpbis-priority
Diff:
https://www.ietf.org/rfcdiff?url2=3Ddraft-kazuho-httpbis-priority-04

Abstract:
   This document describes a scheme for prioritizing HTTP responses.
   This scheme expresses the priority of each HTTP response using
   absolute values, rather than as a relative relationship between a
   group of HTTP responses.

   This document defines the Priority header field for communicating the
   initial priority in an HTTP version-independent manner, as well as
   HTTP/2 and HTTP/3 frames for reprioritizing the responses.  These
   share a common format structure that is designed to provide future
   extensibility.




Please note that it may take a couple of minutes from the time of submissio=
n
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat



--
Kazuho Oku

--000000000000b649b80597c6b892
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><div style=3D"font-family:Helvetica,Arial;font-size:13px">Look=
ing forward to digging further into this.</div><div style=3D"font-family:He=
lvetica,Arial;font-size:13px"><br></div><div style=3D"font-family:Helvetica=
,Arial;font-size:13px">This is not a feedback in the actual design, only th=
e document structure and presentation. While this may come across a bit neg=
ative, I=E2=80=99m really happy with simplifying the priority scheme of HTT=
P/2..</div><div style=3D"font-family:Helvetica,Arial;font-size:13px"><br></=
div><div style=3D"font-family:Helvetica,Arial;font-size:13px">Some quick ob=
servation when approaching the document initially. I writing this before ha=
ving a full grasp of the concepts because that is the only time to provide =
a newcomer perspective.</div><div style=3D"font-family:Helvetica,Arial;font=
-size:13px"><br></div><div style=3D"font-family:Helvetica,Arial;font-size:1=
3px">I think the document could be reorganised and much earlier specify how=
 it achieves prioritisation and use less text (initially) on HTTP/2 by mere=
 stating the the scheme can work with both HTTP/1, 2, 3 and possibly future=
 versions while stating that special mechanisms can be used to opt-out of e=
xisting HTTP/2, and leave it at that.</div><div style=3D"font-family:Helvet=
ica,Arial;font-size:13px"><br></div><div style=3D"font-family:Helvetica,Ari=
al;font-size:13px">After reading 1/3 of document, I still have no clue how =
the priority scheme works (except I have some guess based on earlier ideas =
that have floatet) and I have had to deal with a lot of HTTP/2 legacy that =
I am not necessarily interested in. HTTP/3 doc has also move away from impl=
icit HTTP/2 familiarity, at least last time I checked.</div><div style=3D"f=
ont-family:Helvetica,Arial;font-size:13px"><br></div><div style=3D"font-fam=
ily:Helvetica,Arial;font-size:13px">The document talks about intermediate h=
op reprioritisation without making clear what that is or what purpose it se=
rves. I can only assume load balancers and reverse proxies. From a QUIC bac=
kground that also leaves me wondering what that means - since each hop is n=
ecessarily also end to end, unless there is an extension wrapper frame, but=
 that makes no sense.</div><div style=3D"font-family:Helvetica,Arial;font-s=
ize:13px"><br></div><div style=3D"font-family:Helvetica,Arial;font-size:13p=
x">Once I got to the business end of the document, the document starts by t=
elling which headers not send when it is not at all clear what those header=
s are about in th first place.</div><div style=3D"font-family:Helvetica,Ari=
al;font-size:13px"><br></div><div style=3D"font-family:Helvetica,Arial;font=
-size:13px">It=E2=80=99s also confusing what a protocol specific frame mean=
s, or why it cannot all be done with HTTP headers.</div> <div><br></div><di=
v><br></div><br> <div class=3D"gmail_signature"><div style=3D"font-family:h=
elvetica,arial;font-size:13px">Kind Regards,</div><div style=3D"font-family=
:helvetica,arial;font-size:13px">Mikkel Fahn=C3=B8e J=C3=B8rgensen<br><br><=
/div></div> <br><p class=3D"airmail_on">On 20 November 2019 at 13.05.19, Ka=
zuho Oku (<a href=3D"mailto:kazuhooku@gmail.com">kazuhooku@gmail.com</a>) w=
rote:</p> <blockquote type=3D"cite" class=3D"clean_bq"><span><div><div></di=
v><div>


<title></title>


<div dir=3D"ltr">
<div dir=3D"ltr">
<div dir=3D"ltr">Dear working groups members,
<div><br></div>
<div>After the HTTPbis meeting on Monday, the priorities design
team as well as others have had discussions, and have converged on
a particular design (header-based, as well as allowing
intermediaries to send frames to express per-hop priorities).</div>
<div><br></div>
<div>We have submitted a new revision of the I-D that reflects the
emerging consensus, that clarifies more about the corner cases and
how they should be handled.</div>
<div><br></div>
<div>It can be found at: <a href=3D"https://tools.ietf.org/html/draft-kazuh=
o-httpbis-priority-04">https://tools.ietf.org/html/draft-kazuho-httpbis-pri=
ority-04</a></div>
<div>HTML version is:=C2=A0<a href=3D"https://kazuho.github.io/draft-kazuho=
-httpbis-priority/draft-kazuho-httpbis-priority.html">https://kazuho.github=
.io/draft-kazuho-httpbis-priority/draft-kazuho-httpbis-priority.html</a></d=
iv>
<div><br></div>
<div>We have asked chairs to give us some time in tomorrow&#39;s
HTTPbis meeting that we can use to provide an update on the
status.</div>
<div><br></div>
<div>We are looking forward to hearing your comments either
face-to-face, or on the mailing list.</div>
<div><br></div>
<div>Thank you in advance.</div>
<div><br>
<div class=3D"gmail_quote">
<div dir=3D"ltr" class=3D"gmail_attr">---------- Forwarded message
---------<br>
From: <span dir=3D"auto">&lt;<a href=3D"mailto:internet-drafts@ietf.org">in=
ternet-drafts@ietf.org</a>&gt;</span><br>

Date: 2019=E5=B9=B411=E6=9C=8820=E6=97=A5(=E6=B0=B4) 19:53<br>
Subject: New Version Notification for
draft-kazuho-httpbis-priority-04.txt<br>
To: Kazuho Oku &lt;<a href=3D"mailto:kazuhooku@gmail.com">kazuhooku@gmail.c=
om</a>&gt;, Lucas
Pardue &lt;<a href=3D"mailto:lucaspardue.24.7@gmail.com">lucaspardue.24.7@g=
mail.com</a>&gt;<br>
</div>
<br>
<br>
<br>
A new version of I-D, draft-kazuho-httpbis-priority-04.txt<br>
has been successfully submitted by Kazuho Oku and posted to
the<br>
IETF repository.<br>
<br>
Name:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0
=C2=A0draft-kazuho-httpbis-priority<br>
Revision:=C2=A0 =C2=A0 =C2=A0 =C2=A004<br>
Title:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Extensible Prioritization
Scheme for HTTP<br>
Document date:=C2=A0 2019-11-20<br>
Group:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 Individual
Submission<br>
Pages:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 20<br>
URL:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 <a href=3D"https://www.ietf.o=
rg/internet-drafts/draft-kazuho-httpbis-priority-04.txt" rel=3D"noreferrer"=
 target=3D"_blank">https://www.ietf.org/internet-drafts/draft-kazuho-httpbi=
s-priority-04.txt</a><br>

Status:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.iet=
f.org/doc/draft-kazuho-httpbis-priority/" rel=3D"noreferrer" target=3D"_bla=
nk">https://datatracker.ietf.org/doc/draft-kazuho-httpbis-priority/</a><br>

Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://tools.ietf.org/html/=
draft-kazuho-httpbis-priority-04" rel=3D"noreferrer" target=3D"_blank">http=
s://tools.ietf.org/html/draft-kazuho-httpbis-priority-04</a><br>

Htmlized:=C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://datatracker.ietf.org=
/doc/html/draft-kazuho-httpbis-priority" rel=3D"noreferrer" target=3D"_blan=
k">https://datatracker.ietf.org/doc/html/draft-kazuho-httpbis-priority</a><=
br>

Diff:=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0<a href=3D"https://www.ietf.o=
rg/rfcdiff?url2=3Ddraft-kazuho-httpbis-priority-04" rel=3D"noreferrer" targ=
et=3D"_blank">https://www.ietf.org/rfcdiff?url2=3Ddraft-kazuho-httpbis-prio=
rity-04</a><br>

<br>
Abstract:<br>
=C2=A0 =C2=A0This document describes a scheme for prioritizing HTTP
responses.<br>
=C2=A0 =C2=A0This scheme expresses the priority of each HTTP
response using<br>
=C2=A0 =C2=A0absolute values, rather than as a relative
relationship between a<br>
=C2=A0 =C2=A0group of HTTP responses.<br>
<br>
=C2=A0 =C2=A0This document defines the Priority header field for
communicating the<br>
=C2=A0 =C2=A0initial priority in an HTTP version-independent
manner, as well as<br>
=C2=A0 =C2=A0HTTP/2 and HTTP/3 frames for reprioritizing the
responses.=C2=A0 These<br>
=C2=A0 =C2=A0share a common format structure that is designed to
provide future<br>
=C2=A0 =C2=A0extensibility.<br>
<br>
<br>
<br>
<br>
Please note that it may take a couple of minutes from the time of
submission<br>
until the htmlized version and diff are available at <a href=3D"http://tool=
s.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a>.<br>
<br>
The IETF Secretariat<br>
<br></div>
<br clear=3D"all">
<div><br></div>
--<br>
<div dir=3D"ltr" class=3D"gmail_signature">Kazuho Oku</div>
</div>
</div>
</div>
</div>


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

--000000000000b649b80597c6b892--


From nobody Wed Nov 20 11:18:50 2019
Return-Path: <lucaspardue.24.7@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 C627812008D for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 11:18:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level: 
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 E4SJO7l2AUxi for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 11:18:47 -0800 (PST)
Received: from mail-vs1-xe2c.google.com (mail-vs1-xe2c.google.com [IPv6:2607:f8b0:4864:20::e2c]) (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 4F8F8120020 for <quic@ietf.org>; Wed, 20 Nov 2019 11:18:47 -0800 (PST)
Received: by mail-vs1-xe2c.google.com with SMTP id b16so433813vso.10 for <quic@ietf.org>; Wed, 20 Nov 2019 11:18:47 -0800 (PST)
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=seXsJN2/dE+2iPfTWvZwtzlCu/SsIcevwfjEC5NcbJY=; b=RqiYKMeS10MinVa2qJjpbq2bZD/lXmvrnDeUGZlnagDFXaISzcL/4Tf8DgB6TidmIJ fXmLWb9ZGUH+nPtDsQvQ90kuwgdHsMKQ8xx4cCkZDyAq7TtP4fcfqAdDJhK8AddJTx9f nU0hI7MyUaZubbTtQNqOB7f2p7nXflDH3tao/FN4WPDNAgoqP+CY+0ckj3C28mz7LN/T 58XenRKD+fT0vHqpvn3HsysFzf79OPNT6C/NEjxqh47b29dAk2U3Cks+jmJQ5ZNg9FLK 5MnjkSEhg8WTH3sR9uIxuIsyynDksqb9p39iV3mpCCd9qprpoU7CTGbMA197cYmG/WYc 6cCg==
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=seXsJN2/dE+2iPfTWvZwtzlCu/SsIcevwfjEC5NcbJY=; b=XLma8q7b+7THNBZX6HZdQLCEy0Zh7KVM1YjuexHl8C26VzJciP5dcx/9htLIOIOFNO KIGOZ2Q9ch3l9VOY1dac3/QbkhY/bzSuJpnQ7yAIXvjNWrK6wha+x/lWKKuLorTF9ZyL R2vKPcXl/L8ql+IVbp8PJcgzqYgdv46ZbWus+kFYRPqQ/Pxqrm8bSeIkpUubHod5TC4d b+91G300Dpi5JM4wEqlFQYa9du45xqazpnZ1lltamb+zAFIJ47RS6NxA5TudbQPNIZ8M g2j+4xjNnH08e42zFXx898ZtzPwTNMd9lmgTHooa8M1F49COwzP5hsTSkXE5ejYAzgvb e3Ug==
X-Gm-Message-State: APjAAAWmgbwjnSzEVBHPATt3YRZrawzYBuFeNivvwRdFWjmVvkLiqdpk /VmFd+0rNTzyRvPc5NcImfpAXMxw/AdRuIi5xBE=
X-Google-Smtp-Source: APXvYqzC5K9ZGEHkIy6EK367awx4UAlVs2tf2vUtgGBSLlNgUr4pL1yKlyClI2H/tYF6OxAYzX7z9yz4s2V7DhPN6Nk=
X-Received: by 2002:a05:6102:2041:: with SMTP id q1mr2961977vsr.15.1574277526336;  Wed, 20 Nov 2019 11:18:46 -0800 (PST)
MIME-Version: 1.0
References: <157425081947.30550.7403247942771684795.idtracker@ietfa.amsl.com> <CANatvzyk6xaDby-VVvtuOJ66=YPMqynB9=WMAMxYPxGXYa=BPA@mail.gmail.com> <CAN1APddw53xtus9Z86H4rw2CRXA3MR+fxhLWPf3Bh_=qB-O7Aw@mail.gmail.com>
In-Reply-To: <CAN1APddw53xtus9Z86H4rw2CRXA3MR+fxhLWPf3Bh_=qB-O7Aw@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Wed, 20 Nov 2019 19:18:34 +0000
Message-ID: <CALGR9obRoQ56Jcf_UMW0qiHgGmeRt1y8+8A_8T55XrtgUsWR1g@mail.gmail.com>
Subject: Re: Priorities I-D for Thursday HTTPbis meeting (Fwd: New Version Notification for draft-kazuho-httpbis-priority-04.txt)
To: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
Cc: HTTP Working Group <ietf-http-wg@w3.org>, QUIC WG <quic@ietf.org>, Kazuho Oku <kazuhooku@gmail.com>
Content-Type: multipart/alternative; boundary="000000000000bc3a3d0597cc0cc7"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/8d9im1aXvX38u44Ix0hlz2hHbLQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 20 Nov 2019 19:18:49 -0000

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

Hi Mikkel,

To comment as a co-author but speaking only for myself:

On Wed, 20 Nov 2019, 20:57 Mikkel Fahn=C3=B8e J=C3=B8rgensen, <mikkelfj@gma=
il.com>
wrote:

> Looking forward to digging further into this.
>
> This is not a feedback in the actual design, only the document structure
> and presentation. While this may come across a bit negative, I=E2=80=99m =
really
> happy with simplifying the priority scheme of HTTP/2..
>
> Some quick observation when approaching the document initially. I writing
> this before having a full grasp of the concepts because that is the only
> time to provide a newcomer perspective.
>


Thanks for taking the time to review, fresh eyes are great.


> I think the document could be reorganised and much earlier specify how it
> achieves prioritisation and use less text (initially) on HTTP/2 by mere
> stating the the scheme can work with both HTTP/1, 2, 3 and possibly futur=
e
> versions while stating that special mechanisms can be used to opt-out of
> existing HTTP/2, and leave it at that.
>

I agree here. The present document is an amalgamation of several doc, this
has acted as a mechanism to support the design team and improve the
iteration seed. As a specification we can make improvements here, both in
structure and modularity.


> After reading 1/3 of document, I still have no clue how the priority
> scheme works (except I have some guess based on earlier ideas that have
> floatet) and I have had to deal with a lot of HTTP/2 legacy that I am not
> necessarily interested in. HTTP/3 doc has also move away from implicit
> HTTP/2 familiarity, at least last time I checked.
>

To reinterpret you point, I think that the concepts of urgency and
precedence would benefit from better description (issues #31[1] and
#32[2]). But I also wonder if you are saying that there is too much or too
little HTTP/2 specific/related content? Or am I missing out on your point
here?


> The document talks about intermediate hop reprioritisation without making
> clear what that is or what purpose it serves. I can only assume load
> balancers and reverse proxies. From a QUIC background that also leaves me
> wondering what that means - since each hop is necessarily also end to end=
,
> unless there is an extension wrapper frame, but that makes no sense.
>

The intent is to address the HTTP semantic layer but dip into HTTP
version-specifics where necessary. We rely on readers being familiar with
HTTP semantic concepts and terminology but can probably do a better job of
referencing. Since QUIC has no concept of priority, but the serialisation
of HTTP does and is ultimately coupled to the transport layer, it can be a
bit tricky to pick the subject. Happy to take some suggestions on specific
ways to improve here


> Once I got to the business end of the document, the document starts by
> telling which headers not send when it is not at all clear what those
> headers are about in th first place.
>
> It=E2=80=99s also confusing what a protocol specific frame means, or why =
it cannot
> all be done with HTTP headers.
>

It would help to point to a specific section or paragraph. RFC 7540 Section
8 and HTTP/3 draft 24 section 4.1 detail message exchanges - I don't
especially feel the need to duplicate text in this document but accept that
it might help to reference these in the text.

Cheers
Lucas

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

<div dir=3D"ltr"><div dir=3D"auto"><div>Hi Mikkel,=C2=A0<div dir=3D"auto"><=
br></div><div dir=3D"auto">To comment as a co-author but speaking only for =
myself:</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Wed, 20 Nov 2019, 20:57 Mikkel Fahn=C3=B8e J=C3=B8rgensen, &lt;<a=
 href=3D"mailto:mikkelfj@gmail.com" target=3D"_blank">mikkelfj@gmail.com</a=
>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0=
 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div style=3D"fon=
t-family:Helvetica,Arial;font-size:13px">Looking forward to digging further=
 into this.</div><div style=3D"font-family:Helvetica,Arial;font-size:13px">=
<br></div><div style=3D"font-family:Helvetica,Arial;font-size:13px">This is=
 not a feedback in the actual design, only the document structure and prese=
ntation. While this may come across a bit negative, I=E2=80=99m really happ=
y with simplifying the priority scheme of HTTP/2..</div><div style=3D"font-=
family:Helvetica,Arial;font-size:13px"><br></div><div style=3D"font-family:=
Helvetica,Arial;font-size:13px">Some quick observation when approaching the=
 document initially. I writing this before having a full grasp of the conce=
pts because that is the only time to provide a newcomer perspective.</div><=
/div></blockquote></div></div><div dir=3D"auto"><br></div><div dir=3D"auto"=
><div dir=3D"auto"><br></div><div dir=3D"auto">Thanks for taking the time t=
o review, fresh eyes are great.=C2=A0</div></div><div dir=3D"auto"><br></di=
v><div dir=3D"auto"><div class=3D"gmail_quote"><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x"><div><div style=3D"font-family:Helvetica,Arial;font-size:13px"><br></div=
><div style=3D"font-family:Helvetica,Arial;font-size:13px">I think the docu=
ment could be reorganised and much earlier specify how it achieves prioriti=
sation and use less text (initially) on HTTP/2 by mere stating the the sche=
me can work with both HTTP/1, 2, 3 and possibly future versions while stati=
ng that special mechanisms can be used to opt-out of existing HTTP/2, and l=
eave it at that.</div></div></blockquote></div></div><div dir=3D"auto"><br>=
</div><div dir=3D"auto">I agree here. The present document is an amalgamati=
on of several doc, this has acted as a mechanism to support the design team=
 and improve the iteration seed. As a specification we can make improvement=
s here, both in structure and modularity.<br></div><div dir=3D"auto"><br></=
div><div dir=3D"auto"><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><div style=3D"font-family:Helvetica,Arial;font-size:13px"><br></d=
iv><div style=3D"font-family:Helvetica,Arial;font-size:13px">After reading =
1/3 of document, I still have no clue how the priority scheme works (except=
 I have some guess based on earlier ideas that have floatet) and I have had=
 to deal with a lot of HTTP/2 legacy that I am not necessarily interested i=
n. HTTP/3 doc has also move away from implicit HTTP/2 familiarity, at least=
 last time I checked.</div></div></blockquote></div></div><div dir=3D"auto"=
><br></div><div dir=3D"auto">To reinterpret you point, I think that the con=
cepts of urgency and precedence would benefit from better description (issu=
es #31[1] and #32[2]). But I also wonder if you are saying that there is to=
o much or too little HTTP/2 specific/related content? Or am I missing out o=
n your point here?<br></div><div dir=3D"auto"><br></div><div dir=3D"auto"><=
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><div style=3D=
"font-family:Helvetica,Arial;font-size:13px"><br></div><div style=3D"font-f=
amily:Helvetica,Arial;font-size:13px">The document talks about intermediate=
 hop reprioritisation without making clear what that is or what purpose it =
serves. I can only assume load balancers and reverse proxies. From a QUIC b=
ackground that also leaves me wondering what that means - since each hop is=
 necessarily also end to end, unless there is an extension wrapper frame, b=
ut that makes no sense.</div></div></blockquote></div></div><div dir=3D"aut=
o"><br></div><div dir=3D"auto">The intent is to address the HTTP semantic l=
ayer but dip into HTTP version-specifics where necessary. We rely on reader=
s being familiar with HTTP semantic concepts and terminology but can probab=
ly do a better job of referencing. Since QUIC has no concept of priority, b=
ut the serialisation of HTTP does and is ultimately coupled to the transpor=
t layer, it can be a bit tricky to pick the subject. Happy to take some sug=
gestions on specific ways to improve here<br></div><div dir=3D"auto"><br></=
div><div dir=3D"auto"><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><div style=3D"font-family:Helvetica,Arial;font-size:13px"><br></d=
iv><div style=3D"font-family:Helvetica,Arial;font-size:13px">Once I got to =
the business end of the document, the document starts by telling which head=
ers not send when it is not at all clear what those headers are about in th=
 first place.</div><div style=3D"font-family:Helvetica,Arial;font-size:13px=
"><br></div><div style=3D"font-family:Helvetica,Arial;font-size:13px">It=E2=
=80=99s also confusing what a protocol specific frame means, or why it cann=
ot all be done with HTTP headers.</div></div></blockquote></div></div><div =
dir=3D"auto"><br></div><div>It would help to point to a specific section or=
 paragraph. RFC 7540 Section 8 and HTTP/3 draft 24 section 4.1 detail messa=
ge exchanges - I don&#39;t especially feel the need to duplicate text in th=
is document but accept that it might help to reference these in the text.</=
div><div><br></div>Cheers</div><div>Lucas<br></div>
</div>

--000000000000bc3a3d0597cc0cc7--


From nobody Wed Nov 20 16:17:27 2019
Return-Path: <mt@lowentropy.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 0F9D21208B5 for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 16:17:26 -0800 (PST)
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=lowentropy.net header.b=d/KAhBWS; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=noxgPNY7
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 32xm9TBD1eaE for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 16:17:23 -0800 (PST)
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 518F6120118 for <quic@ietf.org>; Wed, 20 Nov 2019 16:17:23 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id AFAE222063 for <quic@ietf.org>; Wed, 20 Nov 2019 19:17:21 -0500 (EST)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Wed, 20 Nov 2019 19:17:21 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :subject:content-type:content-transfer-encoding; s=fm3; bh=SQGl+ 44hPSkRQFUy9XKlQS37XaHES6XdLIG1BjMN+es=; b=d/KAhBWSkSNSq1SPf07oq 7KIk2NV9iI9SHoNObg7i5SaQfWdY9T+FbEA2teZrSjaGQT9wy4kmBfjQgRnrHYnN JjQEUVpAGeCDlT284CYhv4/dK7fWmtEWv9+z2VDUnyruAEfk41up+h6EkknML6jK fMTPWBiiE7gc6/bcZR8BoFpduV2qMz0CfqTyq6vUVCw+t1bmMHuRcF9EeryNXhR1 bteb1YFZWB8tK4hZWECcDzddHIVdq8gNv/nh7QSddvXfx0xE2TCu++tKZZVVLguE 0KyEawiIgr3eMTpaDBK5d9C8Fdnw+DXX2TWtDGsIBffAYk/0pKK7++7F5U3Dy7l8 w==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=SQGl+44hPSkRQFUy9XKlQS37XaHES6XdLIG1BjMN+ es=; b=noxgPNY7peQ5rNQAOg2mqzHYy6qgl8KiRtgCWA9upjArI4ZtvQ8KzieX6 TvjNesLvDJPeXVF6BMmU0ImJhGovEYHSgiNCy/N0s7cgZvsaa6Hszvr040e05AkQ idnE8KqJjCMdAEAYESiyrcSR7b54kqI4dpI9Uq1b1HgZJPpNDo40F1gdZ4ZKulrw 0GHDm8wSAindWlh1cKBgTILa3cXR3RnQ8pDO4Qj8FcCXl7LlfoCzmSz1jDtiuV9q ATD+Pp2CYV6krlSMc+u/az+cflhf+pifHArrKJKC1ykJ0s34g/QeRHApIO3Kqdm2 aHBJOldK8/oaJyOX5ruhbrIvFsxHg==
X-ME-Sender: <xms:kdfVXeZeLEu9EpA8gt4xgDB3Jt6W9JsbVihTYN7XkfD-3LBPp0Tjdw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudehuddgudelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucgoufhushhpvggtthffohhmrghinhculdegledmne cujfgurhepofgfggfkjghffffhvffutgfgsehtqhertderreejnecuhfhrohhmpedfofgr rhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhhofigvnhhtrhhophihrdhnvghtqeenuc ffohhmrghinhepghhithhhuhgsrdhiohdpihgvthhfrdhorhhgnecurfgrrhgrmhepmhgr ihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrdhnvghtnecuvehluhhsthgvrhfuih iivgeptd
X-ME-Proxy: <xmx:kdfVXZBnCUMIjH1nAEWFa7Px9hNE7IDY9V39mG36LlE-Oc311rmQtg> <xmx:kdfVXWlzNeWQ2abZvjuTPH3348axtnqo4GRkiobqiWysggzaijSSvQ> <xmx:kdfVXaw3y6M-WTCoqCCc3lnIIa3YRlFlVh6jCF4pWgbGAOwOMMRDJg> <xmx:kdfVXaPPmGPWbGLjLHrtrFLAkX45wogMEfZxNPouTPEif-5yNSPq1g>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 42812E00A3; Wed, 20 Nov 2019 19:17:21 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-578-g826f590-fmstable-20191119v1
Mime-Version: 1.0
Message-Id: <d651767a-8b6c-4e45-b154-ef1ad0bf34a3@www.fastmail.com>
In-Reply-To: <CANatvzyk6xaDby-VVvtuOJ66=YPMqynB9=WMAMxYPxGXYa=BPA@mail.gmail.com>
References: <157425081947.30550.7403247942771684795.idtracker@ietfa.amsl.com> <CANatvzyk6xaDby-VVvtuOJ66=YPMqynB9=WMAMxYPxGXYa=BPA@mail.gmail.com>
Date: Thu, 21 Nov 2019 08:17:03 +0800
From: "Martin Thomson" <mt@lowentropy.net>
To: quic@ietf.org
Subject: =?UTF-8?Q?Re:_Priorities_I-D_for_Thursday_HTTPbis_meeting_(Fwd:_New_Vers?= =?UTF-8?Q?ion_Notification_for_draft-kazuho-httpbis-priority-04.txt)?=
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Mu_j4_1LmoNsZ6hORwUS_WNwzJs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2019 00:17:26 -0000

Kazuho,

Thanks for putting this together.  I only looked briefly, but this appea=
rs to faithfully capture what we discussed.

Why did you choose to express this with a dictionary `u=3D4, i=3D?1`** r=
ather than a numeric item `4;i=3D?1`?

Can we look to simplifying this a little more?  I understand that reprio=
ritization was identified as being important by the design team, but I d=
on't recall seeing ever any evidence to support that view.  Can we split=
 that piece out and maybe pursue it separately?

I would prefer to frame the way in which priorities are "merged" (Sectio=
n 6) differently.  I would instead say that the priority information is =
input to prioritization decisions that endpoints/intermediaries/etc.. ma=
ke.  So I would instead say that these entities simply make their own de=
cision about the way to incorporate these signals into their decision.  =
That's probably a systemic thing that affects more than Section 6; I see=
 that the draft uses "obey" in Section 7.1.1, for example.

There seems - at least to me - to be an assumption on the part of some p=
eople involved in this that Priority will be interpreted as an imperativ=
e.  That is, that a client might be able to tell a server to act in a pa=
rticular way and expect to have that instruction complied with.  Same fo=
r servers and proxies.  That might be an appealing, but I can't see any =
way in which we can rely on that.  To the example in the draft, as a CDN=
, I would expect that the server's view carries more weight than the cli=
ent's, but I wouldn't necessarily say that this something as absolute as=
 is currently implied.

** The draft is unclear as to whether it is `u=3D4,i=3D?1` or `u=3D4;i=3D=
?1`, which you might want to double-check.

On Wed, Nov 20, 2019, at 20:04, Kazuho Oku wrote:
> Dear working groups members,
>=20
> After the HTTPbis meeting on Monday, the priorities design team as wel=
l=20
> as others have had discussions, and have converged on a particular=20
> design (header-based, as well as allowing intermediaries to send frame=
s=20
> to express per-hop priorities).
>=20
> We have submitted a new revision of the I-D that reflects the emerging=
=20
> consensus, that clarifies more about the corner cases and how they=20
> should be handled.
>=20
> It can be found at:=20
> https://tools.ietf.org/html/draft-kazuho-httpbis-priority-04
> HTML version is:=20
> https://kazuho.github.io/draft-kazuho-httpbis-priority/draft-kazuho-ht=
tpbis-priority.html
>=20
> We have asked chairs to give us some time in tomorrow's HTTPbis meetin=
g=20
> that we can use to provide an update on the status.
>=20
> We are looking forward to hearing your comments either face-to-face, o=
r=20
> on the mailing list.
>=20
> Thank you in advance.
>=20
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org>
> Date: 2019=E5=B9=B411=E6=9C=8820=E6=97=A5(=E6=B0=B4) 19:53
> Subject: New Version Notification for draft-kazuho-httpbis-priority-04=
.txt
> To: Kazuho Oku <kazuhooku@gmail.com>, Lucas Pardue <lucaspardue.24.7@g=
mail.com>
>=20
>=20
>=20
>  A new version of I-D, draft-kazuho-httpbis-priority-04.txt
>  has been successfully submitted by Kazuho Oku and posted to the
>  IETF repository.
>=20
>  Name: draft-kazuho-httpbis-priority
>  Revision: 04
>  Title: Extensible Prioritization Scheme for HTTP
>  Document date: 2019-11-20
>  Group: Individual Submission
>  Pages: 20
>  URL: https://www.ietf.org/internet-drafts/draft-kazuho-httpbis-priori=
ty-04.txt
>  Status: https://datatracker.ietf.org/doc/draft-kazuho-httpbis-priorit=
y/
>  Htmlized: https://tools.ietf.org/html/draft-kazuho-httpbis-priority-0=
4
>  Htmlized: https://datatracker.ietf.org/doc/html/draft-kazuho-httpbis-=
priority
>  Diff: https://www.ietf.org/rfcdiff?url2=3Ddraft-kazuho-httpbis-priori=
ty-04
>=20
>  Abstract:
>  This document describes a scheme for prioritizing HTTP responses.
>  This scheme expresses the priority of each HTTP response using
>  absolute values, rather than as a relative relationship between a
>  group of HTTP responses.
>=20
>  This document defines the Priority header field for communicating the=

>  initial priority in an HTTP version-independent manner, as well as
>  HTTP/2 and HTTP/3 frames for reprioritizing the responses. These
>  share a common format structure that is designed to provide future
>  extensibility.
>=20
>=20
>=20
>=20
>  Please note that it may take a couple of minutes from the time of sub=
mission
>  until the htmlized version and diff are available at tools.ietf.org.
>=20
>  The IETF Secretariat
>=20
>=20
>=20
> --=20
> Kazuho Oku


From nobody Wed Nov 20 17:53:58 2019
Return-Path: <fielding@gbiv.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 F3F79120938 for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 17:53:43 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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=gbiv.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 1zNtqq3ijzOF for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 17:53:41 -0800 (PST)
Received: from fossa.birch.relay.mailchannels.net (fossa.birch.relay.mailchannels.net [23.83.209.62]) (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 54C7E12012E for <quic@ietf.org>; Wed, 20 Nov 2019 17:53:41 -0800 (PST)
X-Sender-Id: dreamhost|x-authsender|fielding@gbiv.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id AD11D500EA4; Thu, 21 Nov 2019 01:53:40 +0000 (UTC)
Received: from pdx1-sub0-mail-a66.g.dreamhost.com (100-96-4-107.trex.outbound.svc.cluster.local [100.96.4.107]) (Authenticated sender: dreamhost) by relay.mailchannels.net (Postfix) with ESMTPA id 0EEB9500DB0; Thu, 21 Nov 2019 01:53:40 +0000 (UTC)
X-Sender-Id: dreamhost|x-authsender|fielding@gbiv.com
Received: from pdx1-sub0-mail-a66.g.dreamhost.com ([TEMPUNAVAIL]. [64.90.62.162]) (using TLSv1.2 with cipher DHE-RSA-AES256-GCM-SHA384) by 0.0.0.0:2500 (trex/5.18.5); Thu, 21 Nov 2019 01:53:40 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: dreamhost|x-authsender|fielding@gbiv.com
X-MailChannels-Auth-Id: dreamhost
X-Spill-Name: 1838b92c014f0d24_1574301220474_3882142941
X-MC-Loop-Signature: 1574301220474:4174877184
X-MC-Ingress-Time: 1574301220473
Received: from pdx1-sub0-mail-a66.g.dreamhost.com (localhost [127.0.0.1]) by pdx1-sub0-mail-a66.g.dreamhost.com (Postfix) with ESMTP id C283A99373; Wed, 20 Nov 2019 17:53:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=gbiv.com; h=content-type :content-transfer-encoding:from:mime-version:subject:date :message-id:references:cc:in-reply-to:to; s=gbiv.com; bh=Bz3tB69 R9ibKkJ0dck7gDh/lPl4=; b=ZjPnGP1QOj23fmHW1q7PIEfXzDiHBtaCNqaYFeB 4Zm36HNT3o6NSfhVFgW60ou2tISukquG80OwAr3zwqQiXVRwJ5LW7wat8h/x6pCZ cnzLz6yw1kjZk8HatdhGfMJ0Ept9egWsVHTS7ZBJB8942kQkxu3Ro6hweC2oEab6 bKow=
Received: from [31.133.147.208] (dhcp-93d0.meeting.ietf.org [31.133.147.208]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) (Authenticated sender: fielding@gbiv.com) by pdx1-sub0-mail-a66.g.dreamhost.com (Postfix) with ESMTPSA id C3DD39629F; Wed, 20 Nov 2019 17:53:17 -0800 (PST)
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-DH-BACKEND: pdx1-sub0-mail-a66
From: "Roy T. Fielding" <fielding@gbiv.com>
Mime-Version: 1.0 (1.0)
Subject: Re: Priorities I-D for Thursday HTTPbis meeting (Fwd: New Version Notification for draft-kazuho-httpbis-priority-04.txt)
Date: Thu, 21 Nov 2019 09:53:11 +0800
Message-Id: <421180B5-6939-4EB5-B2CA-1A97BA9BAEA9@gbiv.com>
References: <d651767a-8b6c-4e45-b154-ef1ad0bf34a3@www.fastmail.com>
Cc: quic@ietf.org
In-Reply-To: <d651767a-8b6c-4e45-b154-ef1ad0bf34a3@www.fastmail.com>
To: Martin Thomson <mt@lowentropy.net>
X-Mailer: iPhone Mail (17A878)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/UVWVD6ctypJHqKvS4WjqOggjnfc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2019 01:53:46 -0000

I agree with Martin=E2=80=99s comments. We really should emphasize that thes=
e are suggestions for improving the user experience that may need to be adju=
sted based on external knowledge by recipients.

Also, there is a spot in the document where Vary is mentioned as being appro=
priate. I don=E2=80=99t agree that Vary is ever appropriate for this feature=
 because that changes the semantics of the priority in ways that are terribl=
y unpredictable, nor is content negotiation on the basis of received Priorit=
y a good idea. I would simply require that Priority not be included in preem=
ptive content negotiation and be done.

Even with these minor issues, I think this draft is a great improvement and i=
s ready for adoption by the WG.

....Roy


> On Nov 21, 2019, at 8:17 AM, Martin Thomson <mt@lowentropy.net> wrote:
>=20
> =EF=BB=BFKazuho,
>=20
> Thanks for putting this together.  I only looked briefly, but this appears=
 to faithfully capture what we discussed.
>=20
> Why did you choose to express this with a dictionary `u=3D4, i=3D?1`** rat=
her than a numeric item `4;i=3D?1`?
>=20
> Can we look to simplifying this a little more?  I understand that repriori=
tization was identified as being important by the design team, but I don't r=
ecall seeing ever any evidence to support that view.  Can we split that piec=
e out and maybe pursue it separately?
>=20
> I would prefer to frame the way in which priorities are "merged" (Section 6=
) differently.  I would instead say that the priority information is input t=
o prioritization decisions that endpoints/intermediaries/etc.. make.  So I w=
ould instead say that these entities simply make their own decision about th=
e way to incorporate these signals into their decision.  That's probably a s=
ystemic thing that affects more than Section 6; I see that the draft uses "o=
bey" in Section 7.1.1, for example.
>=20
> There seems - at least to me - to be an assumption on the part of some peo=
ple involved in this that Priority will be interpreted as an imperative.  Th=
at is, that a client might be able to tell a server to act in a particular w=
ay and expect to have that instruction complied with.  Same for servers and p=
roxies.  That might be an appealing, but I can't see any way in which we can=
 rely on that.  To the example in the draft, as a CDN, I would expect that t=
he server's view carries more weight than the client's, but I wouldn't neces=
sarily say that this something as absolute as is currently implied.
>=20
> ** The draft is unclear as to whether it is `u=3D4,i=3D?1` or `u=3D4;i=3D?=
1`, which you might want to double-check.
>=20
>> On Wed, Nov 20, 2019, at 20:04, Kazuho Oku wrote:
>> Dear working groups members,
>>=20
>> After the HTTPbis meeting on Monday, the priorities design team as well=20=

>> as others have had discussions, and have converged on a particular=20
>> design (header-based, as well as allowing intermediaries to send frames
>> to express per-hop priorities).
>>=20
>> We have submitted a new revision of the I-D that reflects the emerging=20=

>> consensus, that clarifies more about the corner cases and how they=20
>> should be handled.
>>=20
>> It can be found at:=20
>> https://tools.ietf.org/html/draft-kazuho-httpbis-priority-04
>> HTML version is:=20
>> https://kazuho.github.io/draft-kazuho-httpbis-priority/draft-kazuho-httpb=
is-priority.html
>>=20
>> We have asked chairs to give us some time in tomorrow's HTTPbis meeting=20=

>> that we can use to provide an update on the status.
>>=20
>> We are looking forward to hearing your comments either face-to-face, or=20=

>> on the mailing list.
>>=20
>> Thank you in advance.
>>=20
>> ---------- Forwarded message ---------
>> From: <internet-drafts@ietf.org>
>> Date: 2019=E5=B9=B411=E6=9C=8820=E6=97=A5(=E6=B0=B4) 19:53
>> Subject: New Version Notification for draft-kazuho-httpbis-priority-04..t=
xt
>> To: Kazuho Oku <kazuhooku@gmail.com>, Lucas Pardue <lucaspardue.24.7@gmai=
l.com>
>>=20
>>=20
>>=20
>> A new version of I-D, draft-kazuho-httpbis-priority-04.txt
>> has been successfully submitted by Kazuho Oku and posted to the
>> IETF repository.
>>=20
>> Name: draft-kazuho-httpbis-priority
>> Revision: 04
>> Title: Extensible Prioritization Scheme for HTTP
>> Document date: 2019-11-20
>> Group: Individual Submission
>> Pages: 20
>> URL: https://www.ietf.org/internet-drafts/draft-kazuho-httpbis-priority-0=
4.txt
>> Status: https://datatracker.ietf.org/doc/draft-kazuho-httpbis-priority/
>> Htmlized: https://tools.ietf.org/html/draft-kazuho-httpbis-priority-04
>> Htmlized: https://datatracker.ietf.org/doc/html/draft-kazuho-httpbis-prio=
rity
>> Diff: https://www.ietf.org/rfcdiff?url2=3Ddraft-kazuho-httpbis-priority-0=
4
>>=20
>> Abstract:
>> This document describes a scheme for prioritizing HTTP responses.
>> This scheme expresses the priority of each HTTP response using
>> absolute values, rather than as a relative relationship between a
>> group of HTTP responses.
>>=20
>> This document defines the Priority header field for communicating the
>> initial priority in an HTTP version-independent manner, as well as
>> HTTP/2 and HTTP/3 frames for reprioritizing the responses. These
>> share a common format structure that is designed to provide future
>> extensibility.
>>=20
>>=20
>>=20
>>=20
>> Please note that it may take a couple of minutes from the time of submiss=
ion
>> until the htmlized version and diff are available at tools.ietf.org.
>>=20
>> The IETF Secretariat
>>=20
>>=20
>>=20
>> --=20
>> Kazuho Oku
>=20


From nobody Wed Nov 20 18:00:28 2019
Return-Path: <mt@lowentropy.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 435B012012E for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 18:00:27 -0800 (PST)
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=lowentropy.net header.b=eIQ9Jc9q; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=XRFe8Zr2
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 hCzZTuDpxAWq for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 18:00:26 -0800 (PST)
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 A7CC8120144 for <quic@ietf.org>; Wed, 20 Nov 2019 18:00:24 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id D4890223F1; Wed, 20 Nov 2019 21:00:22 -0500 (EST)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Wed, 20 Nov 2019 21:00:22 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type; s=fm3; bh=tzd0mbdxMwkkwC4Fvnuq+Rwn6q+v amC12jA95+SW9GU=; b=eIQ9Jc9qUQFOWBWmbS0kXB93hLgGKek3XJqqEiS2X5QA sKkoWNKd3gXaPEGy3MA1HJpKjTLVtgcOWiwj32MzKPntLDpxbBCHpJxrT4PyeO/j 67b5hw22GEIwT8Mvr7ozpcop3g8xGTQHzERdZrlFjif+a8hZ4gibr9Oax3/TgAc1 G0KuDV752nBfvNGAptLb0wDoe1lPJExl4MwgyjJffzgbBUSkgWdsyjWKILloCBPS ADwJFYcFao9sVRXPSdC7JEnkhi/5LGqwZSBhxm1QZjeHrt5DkyicS6iiwEIIJ7Sg AncM/Rf+lJdP7zK2gQOstws6jaDfYdM6/cfJxSzm6g==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=tzd0mb dxMwkkwC4Fvnuq+Rwn6q+vamC12jA95+SW9GU=; b=XRFe8Zr2gdJ3Emf/kLkOBU TWBffyduio0TmFrr47+uJFTwVw6jDzldhIeDrwF7ta1cUtpPGn6a8r/VZsxjcNWU 0xfysov1hWs4IL78biCVzl9B/NnR/t45Isno7outadwb0mYKDvdF7Zmu2PDVbznh CJyuHViYYzg6xTZaRBfEQEnZ+mqBUcKKHI/OP+IZsmGMT4z6qXRn893oV1iX9Bc4 1yULzZ1zuMJw0sH4L7S+BibzVLUZobnau+uT3Crjj8eYMUlU17totWAZhHRQ8H5B MqeYYsu4IFRfBsYCxnl6oDcZx61sajLvoD1HxIOPPhjEpDU/3XUxOjRujWF9VG+A ==
X-ME-Sender: <xms:tu_VXbNQyREPRXOrEh0RuzemxHDQb29noqJVgK3qi_fe4G9_LYfS5A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudehuddggeduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreerjeenucfhrhhomhepfdforghr thhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnthhrohhphidrnhgvtheqnecurf grrhgrmhepmhgrihhlfhhrohhmpehmtheslhhofigvnhhtrhhophihrdhnvghtnecuvehl uhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:tu_VXdOUDBXwXN-6EcMnGzBkmx_FXHgXy9JGoMUuuwY76ivehopLSw> <xmx:tu_VXS1SIF-FW-q7Un-qzhh68S89jI9_w13wL8lNjt0mAd-KchSBiQ> <xmx:tu_VXdEKhzPTWqB5MVtASnFuKrGTw-LYKb7JfKwFI7NeJeukpJPzuQ> <xmx:tu_VXY7ApUhHgv6830Vp62PHvXb77A36QNEWgzPtauFXJGb5zUbRWQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 6CD35E00A3; Wed, 20 Nov 2019 21:00:22 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-578-g826f590-fmstable-20191119v1
Mime-Version: 1.0
Message-Id: <a8f57134-114e-4d56-9076-7d880897b842@www.fastmail.com>
In-Reply-To: <421180B5-6939-4EB5-B2CA-1A97BA9BAEA9@gbiv.com>
References: <d651767a-8b6c-4e45-b154-ef1ad0bf34a3@www.fastmail.com> <421180B5-6939-4EB5-B2CA-1A97BA9BAEA9@gbiv.com>
Date: Thu, 21 Nov 2019 10:00:04 +0800
From: "Martin Thomson" <mt@lowentropy.net>
To: "Roy Fielding" <fielding@gbiv.com>
Cc: quic@ietf.org
Subject: =?UTF-8?Q?Re:_Priorities_I-D_for_Thursday_HTTPbis_meeting_(Fwd:_New_Vers?= =?UTF-8?Q?ion_Notification_for_draft-kazuho-httpbis-priority-04.txt)?=
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/W8rOH8TfDdZnZvBDPDF3eLQGHrM>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2019 02:00:27 -0000

On Thu, Nov 21, 2019, at 09:53, Roy T. Fielding wrote:
> Even with these minor issues, I think this draft is a great improvement 
> and is ready for adoption by the WG.

Oh, I forgot this.  I agree with Roy, we should definitely adopt this now.  The issues I raise are minor enough that we can work them out in the working group.


From nobody Wed Nov 20 18:11:46 2019
Return-Path: <robin.marx@uhasselt.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 B8CF512090F for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 18:11:45 -0800 (PST)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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=uhasselt.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 UsXqj9F_-Eq8 for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 18:11:43 -0800 (PST)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::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 0D105120917 for <quic@ietf.org>; Wed, 20 Nov 2019 18:11:43 -0800 (PST)
Received: by mail-lj1-x230.google.com with SMTP id t5so1401839ljk.0 for <quic@ietf.org>; Wed, 20 Nov 2019 18:11:42 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=uhasselt.be; s=google;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=RVIiPLUBRLUkcv63jQhE2qIjGmGjYXLvhg5I0+02sNY=; b=ULBOUBhUhzKyluFrLHaJPWm/u17N+7ZejkKY8iGz52Pypvm8tBpYWzWDJFiBrTp56g UyPoiq9RI7R99FXqt0buUuHclf4OCGaXSUyLPAFMMIJgwvgI1r7tD1geI8ZRvtTE5uoS yMvKhW1jd5kzhlNjgCYMPjugyZAp6MRSlIjC0=
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=RVIiPLUBRLUkcv63jQhE2qIjGmGjYXLvhg5I0+02sNY=; b=EG2eVHOZZpDa87XC4e+EYyiRsqtCA/eNVdurYFHYAAsz2YHgFWemDNxA52CB2RUido jwOLuICPIGnf21g7/CTC9R8Mg3fHgsAXZtPJtMrfM0JhhWr77XVDMqTU3TFYsUo+fu9g HmxzC7RAgwRTioZcg9WCvPRxBeBqzPQFUPXtxpVmJvOvELjdHByvfpR6eccoLsrGGIoM Mzr/9tTGj8FzksnB1pXAPK25jbT14eSwe3UlxgOxbDKSjExPV7BKhqXJEQgeFSkOjjkb LFytMTCbKh4SWte9lK0xyc+5ujHOnnv8fwEk5NvCaw8sA/5/a2jVO4DLFY7zddshvCCD ECgg==
X-Gm-Message-State: APjAAAW1VxsitF9W1v74PYPmOXB57r02A6BnXWs2/MjAvr1oJI1HoVqy 19VtUGvKdtcVwyC7DWzyuxbxpvqmmOjAou/NUvRpBiTf9fw=
X-Google-Smtp-Source: APXvYqyedb9PimZcsmZnkXox3WJQkFx+jU0b2p9teJ4DBi/ShjjA7pCBiljM3rH7GlPpNOEw4bHNh7hz4RGGQ7ULeUw=
X-Received: by 2002:a2e:8654:: with SMTP id i20mr5233946ljj.224.1574302301183;  Wed, 20 Nov 2019 18:11:41 -0800 (PST)
MIME-Version: 1.0
References: <d651767a-8b6c-4e45-b154-ef1ad0bf34a3@www.fastmail.com> <421180B5-6939-4EB5-B2CA-1A97BA9BAEA9@gbiv.com> <a8f57134-114e-4d56-9076-7d880897b842@www.fastmail.com>
In-Reply-To: <a8f57134-114e-4d56-9076-7d880897b842@www.fastmail.com>
From: Robin MARX <robin.marx@uhasselt.be>
Date: Thu, 21 Nov 2019 10:11:29 +0800
Message-ID: <CAC7UV9bqo=jFearFt-yTr5M6q7noywvicG-bW6k4UQGq7bikuQ@mail.gmail.com>
Subject: Re: Priorities I-D for Thursday HTTPbis meeting (Fwd: New Version Notification for draft-kazuho-httpbis-priority-04.txt)
To: Martin Thomson <mt@lowentropy.net>
Cc: Roy Fielding <fielding@gbiv.com>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000006e79f10597d1d141"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2LdPmu17JVga_EhErpJNn9bnXVU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2019 02:11:46 -0000

--0000000000006e79f10597d1d141
Content-Type: text/plain; charset="UTF-8"

Hello Martin,

 > I understand that reprioritization was identified as being important by
the design team, but I don't recall seeing ever any evidence to support
that view.  Can we split that piece out and maybe pursue it separately?

Could you expand on this statement a bit more?
In my view, reprioritization has two sides: reprioritization from the
client after sending an initial priority and server-side reprioritization,
overriding the client's initial priority.

The first side comes into play when doing things like video/media streaming
when switching qualities (see e.g.,
https://github.com/kazuho/draft-kazuho-httpbis-priority/issues/92) or for
the "switching tabs" use case that e.g., Ian keeps mentioning.

The second side was discussed at some length in our paper (
https://h3.edm.uhasselt.be/files/HTTP3_Prioritization_extended_3jul2019.pdf)
and also in a series of Cloudflare blogposts (e.g.,
https://blog.cloudflare.com/better-http-2-prioritization-for-a-faster-web/).
It is also imo mirrored in the intent of the priority hints proposal from
the W3C (https://github.com/WICG/priority-hints/blob/master/EXPLAINER.md).
One of the main reasons for simplifying the H2 scheme (next to
implementation complexity) is to provide an "absolute" priority indication
so that it's easier to reprioritize the responses on the server side.

Are you talking about both or one of these sides?
While I would agree we have less data for the 1st side, I do feel everyone
on the design team agrees this should be kept in.
Removing the PRIORITY_UPDATE frame would also lead to significant push back
from the Chrome team, as I understood from Ian (though I don't want to put
words in his mouth), and would make the proxy-to-origin case difficult
again.

With best regards,
Robin


On Thu, 21 Nov 2019 at 10:00, Martin Thomson <mt@lowentropy.net> wrote:

> On Thu, Nov 21, 2019, at 09:53, Roy T. Fielding wrote:
> > Even with these minor issues, I think this draft is a great improvement
> > and is ready for adoption by the WG.
>
> Oh, I forgot this.  I agree with Roy, we should definitely adopt this
> now.  The issues I raise are minor enough that we can work them out in the
> working group.
>
>

-- 

Robin Marx
PhD researcher - web performance
Expertise centre for Digital Media

T +32(0)11 26 84 79 - GSM +32(0)497 72 86 94

www.uhasselt.be
Universiteit Hasselt - Campus Diepenbeek
Agoralaan Gebouw D - B-3590 Diepenbeek
Kantoor EDM-2.05

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

<div dir=3D"ltr"><div>Hello Martin,</div><div><br></div><div>=C2=A0&gt; I u=
nderstand that reprioritization was identified as being important by the de=
sign team, but I don&#39;t recall seeing ever any evidence to support that =
view.=C2=A0 Can we split that piece out and maybe pursue it separately?=C2=
=A0=C2=A0<br></div><div><br></div><div>Could you expand on this statement a=
 bit more?=C2=A0</div><div>In my view, reprioritization has two sides: repr=
ioritization from the client after sending an initial priority and server-s=
ide reprioritization, overriding the client&#39;s initial priority.</div><d=
iv><br></div><div>The first side comes into play when doing things like vid=
eo/media streaming when switching qualities (see e.g.,=C2=A0<a href=3D"http=
s://github.com/kazuho/draft-kazuho-httpbis-priority/issues/92">https://gith=
ub.com/kazuho/draft-kazuho-httpbis-priority/issues/92</a>) or for the &quot=
;switching tabs&quot; use case that e.g., Ian keeps mentioning.</div><div><=
br></div><div>The second side was discussed at some length in our paper (<a=
 href=3D"https://h3.edm.uhasselt.be/files/HTTP3_Prioritization_extended_3ju=
l2019.pdf">https://h3.edm.uhasselt.be/files/HTTP3_Prioritization_extended_3=
jul2019.pdf</a>) and also in a series of Cloudflare blogposts (e.g.,=C2=A0<=
a href=3D"https://blog.cloudflare.com/better-http-2-prioritization-for-a-fa=
ster-web/">https://blog.cloudflare.com/better-http-2-prioritization-for-a-f=
aster-web/</a>).</div><div>It is also imo mirrored in the intent of the pri=
ority hints proposal from the W3C (<a href=3D"https://github.com/WICG/prior=
ity-hints/blob/master/EXPLAINER.md">https://github.com/WICG/priority-hints/=
blob/master/EXPLAINER.md</a>).</div><div>One of the main reasons for simpli=
fying the H2 scheme (next to implementation complexity) is to provide an &q=
uot;absolute&quot; priority indication so that it&#39;s easier to repriorit=
ize the responses on the server side.</div><div><br></div><div>Are you talk=
ing about both or one of these sides?=C2=A0</div><div>While I would agree w=
e have less data for the 1st side, I do feel everyone on the design team ag=
rees this should be kept in.</div><div>Removing the PRIORITY_UPDATE frame w=
ould also lead to significant push back from the Chrome team, as I understo=
od from Ian (though I don&#39;t want to put words in his mouth), and would =
make the proxy-to-origin case difficult again.=C2=A0</div><div><br></div><d=
iv>With best regards,</div><div>Robin</div><div dir=3D"ltr"><br></div><br><=
div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, 21 =
Nov 2019 at 10:00, Martin Thomson &lt;<a href=3D"mailto:mt@lowentropy.net">=
mt@lowentropy.net</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote"=
 style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);p=
adding-left:1ex">On Thu, Nov 21, 2019, at 09:53, Roy T. Fielding wrote:<br>
&gt; Even with these minor issues, I think this draft is a great improvemen=
t <br>
&gt; and is ready for adoption by the WG.<br>
<br>
Oh, I forgot this.=C2=A0 I agree with Roy, we should definitely adopt this =
now.=C2=A0 The issues I raise are minor enough that we can work them out in=
 the working group.<br>
<br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><div dir=3D"ltr"><div><br><table border=3D"0" ce=
llpadding=3D"0" cellspacing=3D"0" style=3D"width:600px;vertical-align:top;f=
ont-size:12px;color:rgb(0,0,0);text-align:left;padding:0px;font-family:Verd=
ana,Geneva,sans-serif"><tbody><tr><td style=3D"font-weight:bold;font-size:1=
6px;color:rgb(231,59,43);line-height:1.1em;padding:0px;font-family:Verdana,=
Geneva,sans-serif">Robin=C2=A0Marx</td></tr><tr><td style=3D"font-family:Ve=
rdana,Geneva,sans-serif">PhD researcher - web performance</td></tr><tr><td =
style=3D"font-family:Verdana,Geneva,sans-serif">Expertise centre for Digita=
l Media</td></tr><tr><td>=C2=A0</td></tr><tr><td style=3D"font-family:Verda=
na,Geneva,sans-serif"><span style=3D"color:rgb(231,59,43);font-weight:bold;=
font-family:Verdana,Geneva,sans-serif">T</span> +32(0)11 26 84 79 - <span s=
tyle=3D"color:rgb(231,59,43);font-weight:bold">GSM</span> +32(0)497 72 86 9=
4 </td></tr><tr><td>=C2=A0</td></tr><tr><td style=3D"font-family:Verdana,Ge=
neva,sans-serif"><a href=3D"http://www.uhasselt.be" target=3D"_blank"><span=
>www.uhasselt.be</span></a></td></tr><tr><td style=3D"font-family:Verdana,G=
eneva,sans-serif">Universiteit Hasselt  -  Campus Diepenbeek</td></tr><tr><=
td style=3D"font-family:Verdana,Geneva,sans-serif">Agoralaan  Gebouw D  -  =
B-3590 Diepenbeek</td></tr><tr><td style=3D"font-family:Verdana,Geneva,sans=
-serif">Kantoor=C2=A0EDM-2.05</td></tr><tr><td>=C2=A0</td></tr><tr><td styl=
e=3D"font-family:Verdana,Geneva,sans-serif"><div style=3D"width:100%;text-a=
lign:left"><img src=3D"https://www.uhasselt.be/images/nieuwsbrief/dcm/UHass=
elt-liggend.jpg" style=3D"float: none;" alt=3D""></div></td></tr></tbody></=
table></div></div></div></div>

--0000000000006e79f10597d1d141--


From nobody Wed Nov 20 18:15:59 2019
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 DD54A12018B for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 18:15:57 -0800 (PST)
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_HELO_NONE=0.001, 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 UJYje-l7CUvg for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 18:15:55 -0800 (PST)
Received: from mail-lj1-x234.google.com (mail-lj1-x234.google.com [IPv6:2a00:1450:4864:20::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 E508F120077 for <quic@ietf.org>; Wed, 20 Nov 2019 18:15:54 -0800 (PST)
Received: by mail-lj1-x234.google.com with SMTP id g3so1327403ljl.11 for <quic@ietf.org>; Wed, 20 Nov 2019 18:15:54 -0800 (PST)
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=GlENh9k5sHGhOg/Wo9vn2qWBflSJMiYDJkw0NBx1Bnw=; b=FoUT28bbnF/YUf5z9DUSWfTK4GPZQxnxLVqw8bwKiDUC2o8ty6Rr8Mui+22xJn98d/ gLg1a2qn0yoxw0zLRBNwYum57pJMO5w9SQeCizl1F1pxF9424ErANV1jVV9KgWK51It9 5z+zSW9IBTRm77+P+pmkKLel2qveN5x5u3AQNefiva40Hn9NZg9pSrUcAOiEqVddM55u kttf6U8t3UJiT9ApeHP9SBnYO/trCAYphID9jz3OtTsO62VqOt30+MN7j2wBObV0VPwo EnKVtnHVZVdB9yD36s3BHuj12R+6kaZliVgF1g5+CeSQR7znVCk518DWQX39VKUxpvQ8 1Dew==
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=GlENh9k5sHGhOg/Wo9vn2qWBflSJMiYDJkw0NBx1Bnw=; b=TlionDA4eDQpNGvyEqPWy5pwKy1OFEuDOIP/KWVMDZ7q58u7Fhgm7bVd1Mwv2caVuW mHPZM6gX9j8u4JSpcjcbtMX+OlwZGdrNARRiZs+dyUpJin+BLWhao7IHAmXRVnxDC7VE C/uBvK1bFnuNHaRTxYqtlYIGJQI4nK9YTtapgULlAShgYKsENwkriWMbt0zrAkEBbLLV yq5c06dxQtluYQbbwJDj6hVLrokvo38P7UbUYVyvwsFLhRgMf6zAelKfKEXoXI6Ws6YY u7+Ho/qxbeZKwblxpJnO7M0ntb6hjI1J7/TVxkzdzx0OFF3duPGzkVSwIHyGB2YdljG9 4YGQ==
X-Gm-Message-State: APjAAAVaDljJoz4kAYx37GinlQawT8xYQCvLI7bXSUzpHJZCCnPSCa6X e5FwzYiev7lsZORhSxJxmAEtKmefvkClQxeipTs=
X-Google-Smtp-Source: APXvYqxU0iWLEZHiUmyEI+1E9sUF0CG8xDoYPvKK08igpJX9tlCqJP24ykTWyegXOJnnjziii/YCVXxz4IgDdUxiAS4=
X-Received: by 2002:a2e:9e8f:: with SMTP id f15mr5130966ljk.9.1574302553172; Wed, 20 Nov 2019 18:15:53 -0800 (PST)
MIME-Version: 1.0
References: <157425081947.30550.7403247942771684795.idtracker@ietfa.amsl.com> <CANatvzyk6xaDby-VVvtuOJ66=YPMqynB9=WMAMxYPxGXYa=BPA@mail.gmail.com> <d651767a-8b6c-4e45-b154-ef1ad0bf34a3@www.fastmail.com>
In-Reply-To: <d651767a-8b6c-4e45-b154-ef1ad0bf34a3@www.fastmail.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Thu, 21 Nov 2019 10:15:40 +0800
Message-ID: <CANatvzwqzrkf_JpAcR+K=T5RbHtTAXyL7ZPE7NTcCfXfEB5JSw@mail.gmail.com>
Subject: Re: Priorities I-D for Thursday HTTPbis meeting (Fwd: New Version Notification for draft-kazuho-httpbis-priority-04.txt)
To: Martin Thomson <mt@lowentropy.net>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000007371cf0597d1e0fd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/q8DKc7Lj4WuyTlgRj3qXdDMh2dk>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2019 02:15:58 -0000

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

Hi Martin,

Thank you for your comments. My personal responses inline.

2019=E5=B9=B411=E6=9C=8821=E6=97=A5(=E6=9C=A8) 8:17 Martin Thomson <mt@lowe=
ntropy.net>:

> Kazuho,
>
> Thanks for putting this together.  I only looked briefly, but this appear=
s
> to faithfully capture what we discussed.
>
> Why did you choose to express this with a dictionary `u=3D4, i=3D?1`** ra=
ther
> than a numeric item `4;i=3D?1`?
>

The primary benefit is to let the server update the "i" (interleaved)
parameter only. Sometimes, only the server knows If the response is
incrementally processible in a meaningful way (e.g., progressive JPEG vs.
baseline JPEG). It is therefore beneficial to let the server specify the
"i" parameter without messing with "u" (urgency).

The other benefit would be that providing room for future extensions to
define new parameters as SH Dictionary members rather than parameters, as
only the former can take be accompanied with a compound value.


>
> Can we look to simplifying this a little more?  I understand that
> reprioritization was identified as being important by the design team, bu=
t
> I don't recall seeing ever any evidence to support that view.  Can we spl=
it
> that piece out and maybe pursue it separately?
>

There seemed to be certain amount of agreement that three features
(client-driven prioritization, server intervention, reprioritization) was
necessary. That said, I agree that we can cleanly split reprioritization
from the scope of the draft, and at the moment I would not oppose to that
if that is the preference of HTTP WG.


>
> I would prefer to frame the way in which priorities are "merged" (Section
> 6) differently.  I would instead say that the priority information is inp=
ut
> to prioritization decisions that endpoints/intermediaries/etc.. make.  So=
 I
> would instead say that these entities simply make their own decision abou=
t
> the way to incorporate these signals into their decision.  That's probabl=
y
> a systemic thing that affects more than Section 6; I see that the draft
> uses "obey" in Section 7.1.1, for example.
>
> There seems - at least to me - to be an assumption on the part of some
> people involved in this that Priority will be interpreted as an
> imperative.  That is, that a client might be able to tell a server to act
> in a particular way and expect to have that instruction complied with.
> Same for servers and proxies.  That might be an appealing, but I can't se=
e
> any way in which we can rely on that.  To the example in the draft, as a
> CDN, I would expect that the server's view carries more weight than the
> client's, but I wouldn't necessarily say that this something as absolute =
as
> is currently implied.
>

I agree that the priority parameters are merely hints, and that we do not
need to mandate exactly how they would be implemented. Though I think we
need to provide expectations on how H2/H3 terminators are expected to
prioritize is important for other endpoints using the signal.


> ** The draft is unclear as to whether it is `u=3D4,i=3D?1` or `u=3D4;i=3D=
?1`,
> which you might want to double-check.
>

The parameters are SH dictionary members. Therefore `,` is the correct
answer.


> On Wed, Nov 20, 2019, at 20:04, Kazuho Oku wrote:
> > Dear working groups members,
> >
> > After the HTTPbis meeting on Monday, the priorities design team as well
> > as others have had discussions, and have converged on a particular
> > design (header-based, as well as allowing intermediaries to send frames
> > to express per-hop priorities).
> >
> > We have submitted a new revision of the I-D that reflects the emerging
> > consensus, that clarifies more about the corner cases and how they
> > should be handled.
> >
> > It can be found at:
> > https://tools.ietf.org/html/draft-kazuho-httpbis-priority-04
> > HTML version is:
> >
> https://kazuho.github.io/draft-kazuho-httpbis-priority/draft-kazuho-httpb=
is-priority.html
> >
> > We have asked chairs to give us some time in tomorrow's HTTPbis meeting
> > that we can use to provide an update on the status.
> >
> > We are looking forward to hearing your comments either face-to-face, or
> > on the mailing list.
> >
> > Thank you in advance.
> >
> > ---------- Forwarded message ---------
> > From: <internet-drafts@ietf.org>
> > Date: 2019=E5=B9=B411=E6=9C=8820=E6=97=A5(=E6=B0=B4) 19:53
> > Subject: New Version Notification for
> draft-kazuho-httpbis-priority-04..txt
> > To: Kazuho Oku <kazuhooku@gmail.com>, Lucas Pardue <
> lucaspardue.24.7@gmail.com>
> >
> >
> >
> >  A new version of I-D, draft-kazuho-httpbis-priority-04.txt
> >  has been successfully submitted by Kazuho Oku and posted to the
> >  IETF repository.
> >
> >  Name: draft-kazuho-httpbis-priority
> >  Revision: 04
> >  Title: Extensible Prioritization Scheme for HTTP
> >  Document date: 2019-11-20
> >  Group: Individual Submission
> >  Pages: 20
> >  URL:
> https://www.ietf.org/internet-drafts/draft-kazuho-httpbis-priority-04.txt
> >  Status: https://datatracker.ietf.org/doc/draft-kazuho-httpbis-priority=
/
> >  Htmlized: https://tools.ietf.org/html/draft-kazuho-httpbis-priority-04
> >  Htmlized:
> https://datatracker.ietf.org/doc/html/draft-kazuho-httpbis-priority
> >  Diff:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-kazuho-httpbis-priority-04
> >
> >  Abstract:
> >  This document describes a scheme for prioritizing HTTP responses.
> >  This scheme expresses the priority of each HTTP response using
> >  absolute values, rather than as a relative relationship between a
> >  group of HTTP responses.
> >
> >  This document defines the Priority header field for communicating the
> >  initial priority in an HTTP version-independent manner, as well as
> >  HTTP/2 and HTTP/3 frames for reprioritizing the responses. These
> >  share a common format structure that is designed to provide future
> >  extensibility.
> >
> >
> >
> >
> >  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.
> >
> >  The IETF Secretariat
> >
> >
> >
> > --
> > Kazuho Oku
>
>

--=20
Kazuho Oku

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

<div dir=3D"ltr"><div dir=3D"ltr">Hi Martin,</div><div dir=3D"ltr"><br></di=
v><div dir=3D"ltr">Thank you for your comments. My personal responses inlin=
e.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr=
">2019=E5=B9=B411=E6=9C=8821=E6=97=A5(=E6=9C=A8) 8:17 Martin Thomson &lt;<a=
 href=3D"mailto:mt@lowentropy.net">mt@lowentropy.net</a>&gt;:<br></div><blo=
ckquote 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);paddi=
ng-left:1ex">Kazuho,<br>
<br>
Thanks for putting this together.=C2=A0 I only looked briefly, but this app=
ears to faithfully capture what we discussed.<br>
<br>
Why did you choose to express this with a dictionary `u=3D4, i=3D?1`** rath=
er than a numeric item `4;i=3D?1`?<br></blockquote><div><br></div><div>The =
primary benefit is to let the server update the &quot;i&quot; (interleaved)=
 parameter only. Sometimes, only the server knows If the response is increm=
entally processible in a meaningful way (e.g., progressive JPEG vs. baselin=
e JPEG). It is therefore beneficial to let the server specify the &quot;i&q=
uot; parameter without messing with &quot;u&quot; (urgency).</div><div><br>=
</div><div>The other benefit would be that providing room for future extens=
ions to define new parameters as SH Dictionary members rather than paramete=
rs, as only the former can take be accompanied with a compound value.</div>=
<div>=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px =
0px 0.8ex;border-left-width:1px;border-left-style:solid;border-left-color:r=
gb(204,204,204);padding-left:1ex">
<br>
Can we look to simplifying this a little more?=C2=A0 I understand that repr=
ioritization was identified as being important by the design team, but I do=
n&#39;t recall seeing ever any evidence to support that view.=C2=A0 Can we =
split that piece out and maybe pursue it separately?<br></blockquote><div><=
br></div><div>There seemed to be certain amount of agreement that three fea=
tures (client-driven prioritization, server intervention, reprioritization)=
 was necessary. That said, I agree that we can cleanly split reprioritizati=
on from the scope of the draft, and at the moment I would not oppose to tha=
t if that is the preference of HTTP WG.</div><div>=C2=A0</div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1p=
x;border-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1=
ex">
<br>
I would prefer to frame the way in which priorities are &quot;merged&quot; =
(Section 6) differently.=C2=A0 I would instead say that the priority inform=
ation is input to prioritization decisions that endpoints/intermediaries/et=
c.. make.=C2=A0 So I would instead say that these entities simply make thei=
r own decision about the way to incorporate these signals into their decisi=
on.=C2=A0 That&#39;s probably a systemic thing that affects more than Secti=
on 6; I see that the draft uses &quot;obey&quot; in Section 7.1.1, for exam=
ple.<br>
<br>
There seems - at least to me - to be an assumption on the part of some peop=
le involved in this that Priority will be interpreted as an imperative.=C2=
=A0 That is, that a client might be able to tell a server to act in a parti=
cular way and expect to have that instruction complied with.=C2=A0 Same for=
 servers and proxies.=C2=A0 That might be an appealing, but I can&#39;t see=
 any way in which we can rely on that.=C2=A0 To the example in the draft, a=
s a CDN, I would expect that the server&#39;s view carries more weight than=
 the client&#39;s, but I wouldn&#39;t necessarily say that this something a=
s absolute as is currently implied.<br></blockquote><div><br></div><div>I a=
gree that the priority parameters are merely hints, and that we do not need=
 to mandate exactly how they would be implemented. Though I think we need t=
o provide expectations on how H2/H3 terminators are expected to prioritize =
is important for other endpoints using the signal.</div><div><br></div><blo=
ckquote 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);paddi=
ng-left:1ex">
<br>
** The draft is unclear as to whether it is `u=3D4,i=3D?1` or `u=3D4;i=3D?1=
`, which you might want to double-check.<br></blockquote><div><br></div><di=
v>The parameters are SH dictionary members. Therefore `,` is the correct an=
swer.</div><div><br></div><blockquote class=3D"gmail_quote" style=3D"margin=
:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;border-lef=
t-color:rgb(204,204,204);padding-left:1ex">
<br>
On Wed, Nov 20, 2019, at 20:04, Kazuho Oku wrote:<br>
&gt; Dear working groups members,<br>
&gt; <br>
&gt; After the HTTPbis meeting on Monday, the priorities design team as wel=
l <br>
&gt; as others have had discussions, and have converged on a particular <br=
>
&gt; design (header-based, as well as allowing intermediaries to send frame=
s <br>
&gt; to express per-hop priorities).<br>
&gt; <br>
&gt; We have submitted a new revision of the I-D that reflects the emerging=
 <br>
&gt; consensus, that clarifies more about the corner cases and how they <br=
>
&gt; should be handled.<br>
&gt; <br>
&gt; It can be found at: <br>
&gt; <a href=3D"https://tools.ietf.org/html/draft-kazuho-httpbis-priority-0=
4" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/draft-k=
azuho-httpbis-priority-04</a><br>
&gt; HTML version is: <br>
&gt; <a href=3D"https://kazuho.github.io/draft-kazuho-httpbis-priority/draf=
t-kazuho-httpbis-priority.html" rel=3D"noreferrer" target=3D"_blank">https:=
//kazuho.github.io/draft-kazuho-httpbis-priority/draft-kazuho-httpbis-prior=
ity.html</a><br>
&gt; <br>
&gt; We have asked chairs to give us some time in tomorrow&#39;s HTTPbis me=
eting <br>
&gt; that we can use to provide an update on the status.<br>
&gt; <br>
&gt; We are looking forward to hearing your comments either face-to-face, o=
r <br>
&gt; on the mailing list.<br>
&gt; <br>
&gt; Thank you in advance.<br>
&gt; <br>
&gt; ---------- Forwarded message ---------<br>
&gt; From: &lt;<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_blank=
">internet-drafts@ietf.org</a>&gt;<br>
&gt; Date: 2019=E5=B9=B411=E6=9C=8820=E6=97=A5(=E6=B0=B4) 19:53<br>
&gt; Subject: New Version Notification for draft-kazuho-httpbis-priority-04=
..txt<br>
&gt; To: Kazuho Oku &lt;<a href=3D"mailto:kazuhooku@gmail.com" target=3D"_b=
lank">kazuhooku@gmail.com</a>&gt;, Lucas Pardue &lt;<a href=3D"mailto:lucas=
pardue.24.7@gmail.com" target=3D"_blank">lucaspardue.24.7@gmail.com</a>&gt;=
<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt;=C2=A0 A new version of I-D, draft-kazuho-httpbis-priority-04.txt<br>
&gt;=C2=A0 has been successfully submitted by Kazuho Oku and posted to the<=
br>
&gt;=C2=A0 IETF repository.<br>
&gt; <br>
&gt;=C2=A0 Name: draft-kazuho-httpbis-priority<br>
&gt;=C2=A0 Revision: 04<br>
&gt;=C2=A0 Title: Extensible Prioritization Scheme for HTTP<br>
&gt;=C2=A0 Document date: 2019-11-20<br>
&gt;=C2=A0 Group: Individual Submission<br>
&gt;=C2=A0 Pages: 20<br>
&gt;=C2=A0 URL: <a href=3D"https://www.ietf.org/internet-drafts/draft-kazuh=
o-httpbis-priority-04.txt" rel=3D"noreferrer" target=3D"_blank">https://www=
.ietf.org/internet-drafts/draft-kazuho-httpbis-priority-04.txt</a><br>
&gt;=C2=A0 Status: <a href=3D"https://datatracker.ietf.org/doc/draft-kazuho=
-httpbis-priority/" rel=3D"noreferrer" target=3D"_blank">https://datatracke=
r.ietf.org/doc/draft-kazuho-httpbis-priority/</a><br>
&gt;=C2=A0 Htmlized: <a href=3D"https://tools.ietf.org/html/draft-kazuho-ht=
tpbis-priority-04" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.=
org/html/draft-kazuho-httpbis-priority-04</a><br>
&gt;=C2=A0 Htmlized: <a href=3D"https://datatracker.ietf.org/doc/html/draft=
-kazuho-httpbis-priority" rel=3D"noreferrer" target=3D"_blank">https://data=
tracker.ietf.org/doc/html/draft-kazuho-httpbis-priority</a><br>
&gt;=C2=A0 Diff: <a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-kazuh=
o-httpbis-priority-04" rel=3D"noreferrer" target=3D"_blank">https://www.iet=
f.org/rfcdiff?url2=3Ddraft-kazuho-httpbis-priority-04</a><br>
&gt; <br>
&gt;=C2=A0 Abstract:<br>
&gt;=C2=A0 This document describes a scheme for prioritizing HTTP responses=
.<br>
&gt;=C2=A0 This scheme expresses the priority of each HTTP response using<b=
r>
&gt;=C2=A0 absolute values, rather than as a relative relationship between =
a<br>
&gt;=C2=A0 group of HTTP responses.<br>
&gt; <br>
&gt;=C2=A0 This document defines the Priority header field for communicatin=
g the<br>
&gt;=C2=A0 initial priority in an HTTP version-independent manner, as well =
as<br>
&gt;=C2=A0 HTTP/2 and HTTP/3 frames for reprioritizing the responses. These=
<br>
&gt;=C2=A0 share a common format structure that is designed to provide futu=
re<br>
&gt;=C2=A0 extensibility.<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt;=C2=A0 Please note that it may take a couple of minutes from the time o=
f submission<br>
&gt;=C2=A0 until the htmlized version and diff are available at <a href=3D"=
http://tools.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org<=
/a>.<br>
&gt; <br>
&gt;=C2=A0 The IETF Secretariat<br>
&gt; <br>
&gt; <br>
&gt; <br>
&gt; -- <br>
&gt; Kazuho Oku<br>
<br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature">Kazuho Oku</div></div>

--0000000000007371cf0597d1e0fd--


From nobody Wed Nov 20 18:54:07 2019
Return-Path: <lucaspardue.24.7@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 2DD2F12091F for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 18:54:07 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.748
X-Spam-Level: 
X-Spam-Status: No, score=-1.748 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 nWCwO-Vysir5 for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 18:54:05 -0800 (PST)
Received: from mail-vk1-xa32.google.com (mail-vk1-xa32.google.com [IPv6:2607:f8b0:4864:20::a32]) (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 9F429120840 for <quic@ietf.org>; Wed, 20 Nov 2019 18:54:05 -0800 (PST)
Received: by mail-vk1-xa32.google.com with SMTP id t184so379621vka.1 for <quic@ietf.org>; Wed, 20 Nov 2019 18:54:05 -0800 (PST)
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=auyYUZzFdGv5mqRWRprKllOITZOPKThfviYjocKp4pg=; b=hqbu48kPyiiAj4WIA8TBgiO41Sd6UwzBN48+HOslq/P4qRMk+/YmEnv6yI4apV3I55 FU5n2ckTGtNJGjA6GwE1dXe7KIxscQoKqqGweeYLw26jQXq+wBan9Zb1rlCs/eXVGn2J RfEg7cP5djV+oR1GsQwL+YKlrGHlPPRUKzEY5898iwFDQ0y07nHdC7mjgiPIhTX1Jcxh XWb2B+2/khC7ozotoAhmX/hAzaYGxg9YMwksuALJ9i+koJl//BA8sjrWjlFmsRba68xk 4GG7mdJ8/d+uzn0nDit/M9x3hbDy3lRbyd+aPssqwWHyc6wliK2WPxAEGw5Ad6rD84Rd FW9A==
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=auyYUZzFdGv5mqRWRprKllOITZOPKThfviYjocKp4pg=; b=J3NLgebruyPRbSG3vYo1K2N2Y5vc2LDllG6efF1+J4Myx4DxDvzYwfb4s3FiMSOkBi oLgvqIUu5bQufEWY8PwvMN49qGDijnJixpFJB7VI+bf7X6Tm7relFxR6Lh4hED4G6mUS dH5P7CaDmlX1+UKonDy2ngEb9VJjiW7f9BVa87GEaTRyDMGporBMI7bE9QaMZerpVoH3 Xgw8udcj9AQM6Br5W8phVhYZ5+lXEaOgFN2creoi9G0CvPsh7XXj0wxvriyOdQVRmy4f XVIniUQSVkF+sO16RYnHauGk0Pgx4IX+09k+EJ1xZYrLoQeCr3pzWkQniz0bTwgmJSH1 4tcg==
X-Gm-Message-State: APjAAAU0kjIohiPzmMNV5iYj8wfpnPDlGZvDetLpBlk/kptzuwZIWMqe uvTwGOU60G6EVHxrnptYt4Ei6+o1ulvld8glWSE=
X-Google-Smtp-Source: APXvYqxFpbZlD74uzjoNhDYc9d4tqAt5kdLC73vUxh0++BU//GUeULliMH/rHqml6yP6ofzlTJdcT+Dw3AEh5laomEA=
X-Received: by 2002:a1f:a752:: with SMTP id q79mr4054769vke.67.1574304844648;  Wed, 20 Nov 2019 18:54:04 -0800 (PST)
MIME-Version: 1.0
References: <157425081947.30550.7403247942771684795.idtracker@ietfa.amsl.com> <CANatvzyk6xaDby-VVvtuOJ66=YPMqynB9=WMAMxYPxGXYa=BPA@mail.gmail.com> <d651767a-8b6c-4e45-b154-ef1ad0bf34a3@www.fastmail.com> <CANatvzwqzrkf_JpAcR+K=T5RbHtTAXyL7ZPE7NTcCfXfEB5JSw@mail.gmail.com>
In-Reply-To: <CANatvzwqzrkf_JpAcR+K=T5RbHtTAXyL7ZPE7NTcCfXfEB5JSw@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Thu, 21 Nov 2019 02:53:53 +0000
Message-ID: <CALGR9oYECqXarT+pdCKG5QuQ26KxvSifmmtbpbAujYENJpOOOQ@mail.gmail.com>
Subject: Re: Priorities I-D for Thursday HTTPbis meeting (Fwd: New Version Notification for draft-kazuho-httpbis-priority-04.txt)
To: Kazuho Oku <kazuhooku@gmail.com>
Cc: Martin Thomson <mt@lowentropy.net>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000896c40597d26991"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/pkmC4b4wA2RCE_HIbGJzGAEnBd8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2019 02:54:07 -0000

--0000000000000896c40597d26991
Content-Type: text/plain; charset="UTF-8"

To put my own thoughts on top of some of Kazuho's

On Thu, Nov 21, 2019 at 2:16 AM Kazuho Oku <kazuhooku@gmail.com> wrote:

>
> Can we look to simplifying this a little more?  I understand that
>> reprioritization was identified as being important by the design team, but
>> I don't recall seeing ever any evidence to support that view.  Can we split
>> that piece out and maybe pursue it separately?
>>
>
> There seemed to be certain amount of agreement that three features
> (client-driven prioritization, server intervention, reprioritization) was
> necessary. That said, I agree that we can cleanly split reprioritization
> from the scope of the draft, and at the moment I would not oppose to that
> if that is the preference of HTTP WG.
>

I opened issue #1 on draft 00 as a question on reprioritiation. But I think
the important question to ask is, if we as WG agree to deprecate "HTTP/2
priorities" does that mean the signal, the tree-based model, the features
(setting, mutating, etc) or all of the above. My own view is that we are
not deprecating the features but instead grandparenting them in
unquestionably. The question of importance of reprioritization is totally
valid but I think it is unfair to place the burden of proving its
importance in a replacement, when RFC 7540 does not describe why it was
important in the first place. That said, I would be willing to explore this
further, and support the notion of a separate document but will caution
that carving the feature set too much will increase the chance that
implementers get this new scheme wrong by making assumptions based only on
initial priority. This is not a theoretical risk, there is a large survey
of reprioritization in the wild for some specific cases [1].


>  I would prefer to frame the way in which priorities are "merged" (Section
> 6) differently.  I would instead say that the priority information is input
> to prioritization decisions that endpoints/intermediaries/etc.. make.  So I
> would instead say that these entities simply make their own decision about
> the way to incorporate these signals into their decision.  That's probably
> a systemic thing that affects more than Section 6; I see that the draft
> uses "obey" in Section 7.1.1, for example.
>
>>
>> There seems - at least to me - to be an assumption on the part of some
>> people involved in this that Priority will be interpreted as an
>> imperative.  That is, that a client might be able to tell a server to act
>> in a particular way and expect to have that instruction complied with.
>> Same for servers and proxies.  That might be an appealing, but I can't see
>> any way in which we can rely on that.  To the example in the draft, as a
>> CDN, I would expect that the server's view carries more weight than the
>> client's, but I wouldn't necessarily say that this something as absolute as
>> is currently implied.
>>
>
> I agree that the priority parameters are merely hints, and that we do not
> need to mandate exactly how they would be implemented. Though I think we
> need to provide expectations on how H2/H3 terminators are expected to
> prioritize is important for other endpoints using the signal.
>
>
I started a PR to tackle explanation some of the issues about merging
/collaboartion. I closed that closed it because I wasn't sure if useful,
but it sounds like there is some value and I can resurrect it.

Cheers
Lucas

[1] https://github.com/andydavies/http2-prioritization-issues

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

<div dir=3D"ltr"><div>To put my own thoughts on top of some of Kazuho&#39;s=
<br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_at=
tr">On Thu, Nov 21, 2019 at 2:16 AM Kazuho Oku &lt;<a href=3D"mailto:kazuho=
oku@gmail.com">kazuhooku@gmail.com</a>&gt; wrote:<br></div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid r=
gb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div class=3D"gmail_quot=
e"><br><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;=
border-left:1px solid rgb(204,204,204);padding-left:1ex">

Can we look to simplifying this a little more?=C2=A0 I understand that repr=
ioritization was identified as being important by the design team, but I do=
n&#39;t recall seeing ever any evidence to support that view.=C2=A0 Can we =
split that piece out and maybe pursue it separately?<br></blockquote><div><=
br></div><div>There seemed to be certain amount of agreement that three fea=
tures (client-driven prioritization, server intervention, reprioritization)=
 was necessary. That said, I agree that we can cleanly split reprioritizati=
on from the scope of the draft, and at the moment I would not oppose to tha=
t if that is the preference of HTTP WG.</div></div></div></blockquote><div>=
<br></div><div>I opened issue #1 on draft 00 as a question on reprioritiati=
on. But I think the important question to ask is, if we as WG agree to depr=
ecate &quot;HTTP/2 priorities&quot; does that mean the signal, the tree-bas=
ed model, the features (setting, mutating, etc) or all of the above. My own=
 view is that we are not deprecating the features but instead grandparentin=
g them in unquestionably. The question of importance of reprioritization is=
 totally valid but I think it is unfair to place the burden of proving its =
importance in a replacement, when RFC 7540 does not describe why it was imp=
ortant in the first place. That said, I would be willing to explore this fu=
rther, and support the notion of a separate document but will caution that =
carving the feature set too much will increase the chance that implementers=
 get this new scheme wrong by making assumptions based only on initial prio=
rity. This is not a theoretical risk, there is a large survey of reprioriti=
zation in the wild for some specific cases [1].<br></div><div>=C2=A0</div><=
blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-l=
eft:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div clas=
s=3D"gmail_quote"><div>=C2=A0I would prefer to frame the way in which prior=
ities are &quot;merged&quot; (Section 6) differently.=C2=A0 I would instead=
 say that the priority information is input to prioritization decisions tha=
t endpoints/intermediaries/etc.. make.=C2=A0 So I would instead say that th=
ese entities simply make their own decision about the way to incorporate th=
ese signals into their decision.=C2=A0 That&#39;s probably a systemic thing=
 that affects more than Section 6; I see that the draft uses &quot;obey&quo=
t; in Section 7.1.1, for example.<br></div><blockquote class=3D"gmail_quote=
" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);=
padding-left:1ex">
<br>
There seems - at least to me - to be an assumption on the part of some peop=
le involved in this that Priority will be interpreted as an imperative.=C2=
=A0 That is, that a client might be able to tell a server to act in a parti=
cular way and expect to have that instruction complied with.=C2=A0 Same for=
 servers and proxies.=C2=A0 That might be an appealing, but I can&#39;t see=
 any way in which we can rely on that.=C2=A0 To the example in the draft, a=
s a CDN, I would expect that the server&#39;s view carries more weight than=
 the client&#39;s, but I wouldn&#39;t necessarily say that this something a=
s absolute as is currently implied.<br></blockquote><div><br></div><div>I a=
gree that the priority parameters are merely hints, and that we do not need=
 to mandate exactly how they would be implemented. Though I think we need t=
o provide expectations on how H2/H3 terminators are expected to prioritize =
is important for other endpoints using the signal.</div><div><br></div></di=
v></div></blockquote><div><br></div><div>I started a PR to tackle explanati=
on some of the issues about merging /collaboartion. I closed that closed it=
 because I wasn&#39;t sure if useful, but it sounds like there is some valu=
e and I can resurrect it.</div><div><br></div><div>Cheers</div><div>Lucas<b=
r></div><div><br></div><div>[1] <a href=3D"https://github.com/andydavies/ht=
tp2-prioritization-issues">https://github.com/andydavies/http2-prioritizati=
on-issues</a> </div></div></div>

--0000000000000896c40597d26991--


From nobody Wed Nov 20 20:46:07 2019
Return-Path: <mt@lowentropy.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 3AB88120232 for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 20:46:05 -0800 (PST)
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=lowentropy.net header.b=EXi6rIs5; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=wpqU+qBC
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 tKgdranrTAGU for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 20:46:02 -0800 (PST)
Received: from out2-smtp.messagingengine.com (out2-smtp.messagingengine.com [66.111.4.26]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4B419120133 for <quic@ietf.org>; Wed, 20 Nov 2019 20:46:02 -0800 (PST)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 474DB223E8; Wed, 20 Nov 2019 23:46:01 -0500 (EST)
Received: from imap2 ([10.202.2.52]) by compute1.internal (MEProxy); Wed, 20 Nov 2019 23:46:01 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:in-reply-to:references:date:from:to :cc:subject:content-type; s=fm3; bh=iCrzpVpW1ujJi5MjF3PeZvAuG7VI tL/n8Kp4A9u+YLk=; b=EXi6rIs5u/2DSDSpcKjioVUJeMGT95uOuxDZEd/Jf0Ml AiCo1oMRA4KNqNrmgz/AfJ40Mmrz8Pk2PUzGRJVriXYGA3wQ0/EgTDc8s+fwD1m2 eHvSr5wpJkM9UnBISBzNZokWfjnLEf+qx3VxJkM5ZXr0LwjJP/XywRWgbFDJyQu2 Y4K3ooAR7YhHWeygqkkqQV8Pjztl45ktrm1B6P5L1bXrGtKHAmrv22AMXVyQvJZE DzhrcrGOg4u0WHLQjH3mktU+N/Z+ZGHVzkTl5l4fMbKzrUX17k9maHgV91f0EWie St9zaQXveOUSyJYXzOAPPayv76L0wy3mjFm6ky8hHA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=iCrzpV pW1ujJi5MjF3PeZvAuG7VItL/n8Kp4A9u+YLk=; b=wpqU+qBCV5jgoY+lZOlF2d EsZ0XOGwnE5BActtTOJHLBdwjFDBVuDkHn11a8gUvdUHJuy/QAI37S4lzYF/RRAS G8ddbkoERrxcc1wlOw0Z8/rTX3ExUmpaHF7GWNzXRoFpNl7n0gxUyfNtzfO/UJ2q S54umeYSMLhYEYdbI9OSlYm0fHn/VVYF7vwgGyIAR6mffhZb+eEB9Z5clPhsfC0j RrSMksSyiuG6A/srYjNCHXswmsck5uqmxMwlLLu0SqoPBeKBTnc7Afe06EWk8Qam HS/nGJxRoh+pKj5quHhiYmubVi2MmZYgKwsZ516IsZpS0u2OJPoLLYdEEO4pxbkg ==
X-ME-Sender: <xms:iBbWXdbtPTOu2IO3_AZ0syFIx8XOpfQoNJVOpnUqYms307GRKeTK3g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudehuddgjeehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepofgfggfkjghffffhvffutgesthdtredtreerjeenucfhrhhomhepfdforghr thhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghnthhrohhphidrnhgvtheqnecuff homhgrihhnpehgihhthhhusgdrtghomhenucfrrghrrghmpehmrghilhhfrhhomhepmhht sehlohifvghnthhrohhphidrnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:iBbWXZie-NMg6DOmMLeBTjFrXVVY_Ma1arHrwAKd4uohbW4xZBMMoA> <xmx:iBbWXXMgKfNhYDR-1RJwAV6Amft5tNykAhgJA8lbXhW48_BmsbX9dg> <xmx:iBbWXTMEXB1mZzvJnVsESxI6vg55PAKFA8Iuf1Df_CT4bP9adxIR3Q> <xmx:iRbWXUFyZgTNSdYscPqz87YtOfrBkRf7ns6BVhpi8AvTmkfKjpzKLg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 33183E00A3; Wed, 20 Nov 2019 23:46:00 -0500 (EST)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.1.7-578-g826f590-fmstable-20191119v1
Mime-Version: 1.0
Message-Id: <fed8fbb4-69aa-4b8b-bde2-21b1eaeb6ff8@www.fastmail.com>
In-Reply-To: <CAC7UV9bqo=jFearFt-yTr5M6q7noywvicG-bW6k4UQGq7bikuQ@mail.gmail.com>
References: <d651767a-8b6c-4e45-b154-ef1ad0bf34a3@www.fastmail.com> <421180B5-6939-4EB5-B2CA-1A97BA9BAEA9@gbiv.com> <a8f57134-114e-4d56-9076-7d880897b842@www.fastmail.com> <CAC7UV9bqo=jFearFt-yTr5M6q7noywvicG-bW6k4UQGq7bikuQ@mail.gmail.com>
Date: Thu, 21 Nov 2019 12:45:39 +0800
From: "Martin Thomson" <mt@lowentropy.net>
To: "Robin MARX" <robin.marx@uhasselt.be>
Cc: "IETF QUIC WG" <quic@ietf.org>
Subject: =?UTF-8?Q?Re:_Priorities_I-D_for_Thursday_HTTPbis_meeting_(Fwd:_New_Vers?= =?UTF-8?Q?ion_Notification_for_draft-kazuho-httpbis-priority-04.txt)?=
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7LJDmtkUDarDNbBQlCUc4XVz2LQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2019 04:46:05 -0000

Hi Robin,

On Thu, Nov 21, 2019, at 10:11, Robin MARX wrote:
>  > I understand that reprioritization was identified as being important 
> by the design team, but I don't recall seeing ever any evidence to 
> support that view. Can we split that piece out and maybe pursue it 
> separately? 
> 
> Could you expand on this statement a bit more? 
> In my view, reprioritization has two sides: reprioritization from the 
> client after sending an initial priority and server-side 
> reprioritization, overriding the client's initial priority.

I refer specifically to the frame.

> The first side comes into play when doing things like video/media 
> streaming when switching qualities (see e.g., 
> https://github.com/kazuho/draft-kazuho-httpbis-priority/issues/92) or 
> for the "switching tabs" use case that e.g., Ian keeps mentioning.

These seem fairly obvious, but I realized recently that a lot of our thinking hasn't been grounded in any data.  That is, we're intuiting things about the value of the signal, but we never got firm reasons.


From nobody Wed Nov 20 22:42:44 2019
Return-Path: <lars@eggert.org>
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 972EC1200B5 for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 22:42:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.897
X-Spam-Level: 
X-Spam-Status: No, score=-1.897 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_NONE=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 WaTeAbK1_64S for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 22:42:42 -0800 (PST)
Received: from emh02.mail.saunalahti.fi (emh02.mail.saunalahti.fi [62.142.5.108]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id DD28D12000F for <quic@ietf.org>; Wed, 20 Nov 2019 22:42:41 -0800 (PST)
Received: from eggert.org (unknown [62.248.255.8]) by emh02.mail.saunalahti.fi (Postfix) with ESMTP id B12B5200D2; Thu, 21 Nov 2019 08:42:37 +0200 (EET)
Received: from slate.eggert.org (Slate.eggert.org [172.19.235.111]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by eggert.org (Postfix) with ESMTPSA id E206D613195; Thu, 21 Nov 2019 08:42:31 +0200 (EET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: CONEX? (was: Re: Q and L loss bits)
From: Lars Eggert <lars@eggert.org>
In-Reply-To: <cd2e9389a61d49eabad2b0fac2f4db96@ustx2ex-dag1mb5.msg.corp.akamai.com>
Date: Thu, 21 Nov 2019 08:42:31 +0200
Cc: Dmitri Tikhonov <dtikhonov@litespeedtech.com>, Christian Huitema <huitema@huitema.net>, IETF QUIC WG <quic@ietf.org>, "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A5687771-2F40-419F-A8A2-00FFF919B3FA@eggert.org>
References: <20191119143218.GB2789@ubuntu-dmitri> <24388_1574174932_5DD400D4_24388_372_7_1574174948.30247.49.camel@orange.com> <20191119150829.GD2789@ubuntu-dmitri> <20191119192622.GE2789@ubuntu-dmitri> <a21bc373-1fda-836e-7efc-599832ae575d@huitema.net> <20191120014850.GC16017@ubuntu-dmitri> <cd2e9389a61d49eabad2b0fac2f4db96@ustx2ex-dag1mb5.msg.corp.akamai.com>
To: "Lubashev, Igor" <ilubashe@akamai.com>
X-MailScanner-ID: E206D613195.A1C1B
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/XSlhx6ky7Qc1genwLhCtdgYXnGU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2019 06:42:44 -0000

Hi,

I'm wondering whether specifying a CONEX mapping for QUIC would satisfy =
the needs that quic-lossbits attempts to address? We could reuse an =
existing piece of IETF work.

See https://tools.ietf.org/html/rfc7713 for an overview and =
https://tools.ietf.org/html/rfc7786 for the TCP mapping.

Lars=


From nobody Wed Nov 20 22:44:38 2019
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 93E5B120124 for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 22:44:37 -0800 (PST)
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, SPF_HELO_NONE=0.001, 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 z0XJhmiK1wsM for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 22:44:34 -0800 (PST)
Received: from smtp-sh.infomaniak.ch (smtp-sh.infomaniak.ch [128.65.195.4]) (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 1FE7612000F for <quic@ietf.org>; Wed, 20 Nov 2019 22:44:33 -0800 (PST)
Received: from smtp-2-0001.mail.infomaniak.ch ([10.5.36.108]) by smtp-sh.infomaniak.ch (8.14.5/8.14.5) with ESMTP id xAL6iJBR026073 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 21 Nov 2019 07:44:19 +0100
Received: from [IPv6:2401:fa00:2d:11:98db:c89c:b4db:c241] (unknown [IPV6:2401:fa00:2d:11:98db:c89c:b4db:c241]) by smtp-2-0001.mail.infomaniak.ch (Postfix) with ESMTPA id 330CB10032D68; Thu, 21 Nov 2019 07:44:15 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: CONEX? (was: Re: Q and L loss bits)
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
In-Reply-To: <A5687771-2F40-419F-A8A2-00FFF919B3FA@eggert.org>
Date: Thu, 21 Nov 2019 14:44:11 +0800
Cc: "Lubashev, Igor" <ilubashe@akamai.com>, IETF QUIC WG <quic@ietf.org>, Christian Huitema <huitema@huitema.net>, "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <A6DB3084-447B-467A-B164-310C83A6526C@trammell.ch>
References: <20191119143218.GB2789@ubuntu-dmitri> <24388_1574174932_5DD400D4_24388_372_7_1574174948.30247.49.camel@orange.com> <20191119150829.GD2789@ubuntu-dmitri> <20191119192622.GE2789@ubuntu-dmitri> <a21bc373-1fda-836e-7efc-599832ae575d@huitema.net> <20191120014850.GC16017@ubuntu-dmitri> <cd2e9389a61d49eabad2b0fac2f4db96@ustx2ex-dag1mb5.msg.corp.akamai.com> <A5687771-2F40-419F-A8A2-00FFF919B3FA@eggert.org>
To: Lars Eggert <lars@eggert.org>
X-Mailer: Apple Mail (2.3445.104.11)
X-Antivirus: Dr.Web (R) for Unix mail servers drweb plugin ver.6.0.2.8
X-Antivirus-Code: 0x100000
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/aOKpPxxj0_3fZzkq3HXWF6ks5yA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2019 06:44:37 -0000

hi Lars,

This is kind of where I was going with the "expose CWR-like semantics =
for loss" thing; "just do conex" is a much better shorthand for that.

Thanks, cheers,

Brian

> On 21 Nov 2019, at 14:42, Lars Eggert <lars@eggert.org> wrote:
>=20
> Hi,
>=20
> I'm wondering whether specifying a CONEX mapping for QUIC would =
satisfy the needs that quic-lossbits attempts to address? We could reuse =
an existing piece of IETF work.
>=20
> See https://tools.ietf.org/html/rfc7713 for an overview and =
https://tools.ietf.org/html/rfc7786 for the TCP mapping.
>=20
> Lars
>=20


From nobody Wed Nov 20 23:11:43 2019
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 73BF71209EE for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 23:11:38 -0800 (PST)
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_HELO_NONE=0.001, 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 fUf9xe_xWt-E for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 23:11:35 -0800 (PST)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::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 0CFDB1209D2 for <quic@ietf.org>; Wed, 20 Nov 2019 23:11:35 -0800 (PST)
Received: by mail-lj1-x230.google.com with SMTP id q2so1975523ljg.7 for <quic@ietf.org>; Wed, 20 Nov 2019 23:11:34 -0800 (PST)
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=1SP4sQSgsyLCQVhONJtx+4otGC5giBOnLac+FArgpWw=; b=UqMW2yAeO47N2V+jpOm5GP4P0i+3WHgSdeIB7dzKZC9MRqVZA64+4hPhqwuLczLArz eRJf/XTukwZEU5Ey2+hKBFo1k3gKI69hsqRqrCrZ+Hj/dVsrskQX/G3iI7/YR02XrcVF dxTg2PyBw3gi/9dg6ClnRCcISRvZgT1kENHpGNRK5QJceciVhUTKxZlLTGexulOSOMu5 ekRF8jW6L4PFxGJ5+YM64uz6ODWUedlfsSFnR78IgwVgl/rdVUnyOSGG+dz/MNdvniex d8ck+IxU9Ky92Td0gMzgCqy8j8wll7R5qUXt4s6p0Kb4insxjsIxweIHoMM2DHgpfRQn tpEA==
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=1SP4sQSgsyLCQVhONJtx+4otGC5giBOnLac+FArgpWw=; b=hXTNrNr1MDS+eI2aI6tKBcVuGCJRMMEAEqpJ0disuAft9bZXxLAGl/xLsTBuWcLJUI KmU9L2K1Fm1/wJZRzR2i6DwaP9zBksddCJn5mH8yCmePYaBpP7/PT8tG1HDKfRwDssiy 092aidcZvV7mnliQeWQ+vV1rbfG/3W+aGVxy5U+ieXsLLrmXdP4ZbZNDXuUlqx96AAY5 sOFeycdYOh8AwixQF/YAGrWDj1QdfkmKCLruYTFc/F3Ltuos/s5wvAGH/O8VeewR8Hzn cCnBfzCvkG7bsGqequVWPlIPlyPtY/HR21P5VT78M3ginRn5UCanZwXBUn5vgasUBLja bsCA==
X-Gm-Message-State: APjAAAWqbWZdoAelaht+dTwhO8HQjt//5QFQbd/XzdhGTlKuyVIlkmin gN7M13qZuI5tJk5whFxlbu0vQLccrKGWXAEyhBT8Xs0a2DuWqg==
X-Google-Smtp-Source: APXvYqx0pPf+XgyjyaBMDiJ51iXCz34duE0G5JoXyOHpfzVokic4L1ovOcEvTFwHzh1gluRabPHa7OPUiKO5/yhie9Q=
X-Received: by 2002:a05:651c:326:: with SMTP id b6mr5912556ljp.119.1574320293283;  Wed, 20 Nov 2019 23:11:33 -0800 (PST)
MIME-Version: 1.0
References: <d651767a-8b6c-4e45-b154-ef1ad0bf34a3@www.fastmail.com> <421180B5-6939-4EB5-B2CA-1A97BA9BAEA9@gbiv.com>
In-Reply-To: <421180B5-6939-4EB5-B2CA-1A97BA9BAEA9@gbiv.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Thu, 21 Nov 2019 15:11:20 +0800
Message-ID: <CANatvzzxRvfHNjAW+fJ_Mx3Lex_cUoyhtJqAXsiKnmxERuuTPg@mail.gmail.com>
Subject: Re: Priorities I-D for Thursday HTTPbis meeting (Fwd: New Version Notification for draft-kazuho-httpbis-priority-04.txt)
To: "Roy T. Fielding" <fielding@gbiv.com>
Cc: Martin Thomson <mt@lowentropy.net>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d80ec10597d601e3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/qmdKsOEhRTztblDmtKmW1ub-zRo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2019 07:11:41 -0000

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

2019=E5=B9=B411=E6=9C=8821=E6=97=A5(=E6=9C=A8) 9:54 Roy T. Fielding <fieldi=
ng@gbiv.com>:

> I agree with Martin=E2=80=99s comments. We really should emphasize that t=
hese are
> suggestions for improving the user experience that may need to be adjuste=
d
> based on external knowledge by recipients.
>
> Also, there is a spot in the document where Vary is mentioned as being
> appropriate. I don=E2=80=99t agree that Vary is ever appropriate for this=
 feature
> because that changes the semantics of the priority in ways that are
> terribly unpredictable, nor is content negotiation on the basis of receiv=
ed
> Priority a good idea. I would simply require that Priority not be include=
d
> in preemptive content negotiation and be done.
>

Roy, thank you for the review and the suggestion. I think you are correct,
I have opened
https://github.com/kazuho/draft-kazuho-httpbis-priority/pull/119 to address
the issue.


>
> Even with these minor issues, I think this draft is a great improvement
> and is ready for adoption by the WG.
>
> .....Roy
>
>
> > On Nov 21, 2019, at 8:17 AM, Martin Thomson <mt@lowentropy.net> wrote:
> >
> > =EF=BB=BFKazuho,
> >
> > Thanks for putting this together.  I only looked briefly, but this
> appears to faithfully capture what we discussed.
> >
> > Why did you choose to express this with a dictionary `u=3D4, i=3D?1`**
> rather than a numeric item `4;i=3D?1`?
> >
> > Can we look to simplifying this a little more?  I understand that
> reprioritization was identified as being important by the design team, bu=
t
> I don't recall seeing ever any evidence to support that view.  Can we spl=
it
> that piece out and maybe pursue it separately?
> >
> > I would prefer to frame the way in which priorities are "merged"
> (Section 6) differently.  I would instead say that the priority informati=
on
> is input to prioritization decisions that endpoints/intermediaries/etc..
> make.  So I would instead say that these entities simply make their own
> decision about the way to incorporate these signals into their decision.
> That's probably a systemic thing that affects more than Section 6; I see
> that the draft uses "obey" in Section 7.1.1, for example.
> >
> > There seems - at least to me - to be an assumption on the part of some
> people involved in this that Priority will be interpreted as an
> imperative.  That is, that a client might be able to tell a server to act
> in a particular way and expect to have that instruction complied with.
> Same for servers and proxies.  That might be an appealing, but I can't se=
e
> any way in which we can rely on that.  To the example in the draft, as a
> CDN, I would expect that the server's view carries more weight than the
> client's, but I wouldn't necessarily say that this something as absolute =
as
> is currently implied.
> >
> > ** The draft is unclear as to whether it is `u=3D4,i=3D?1` or `u=3D4;i=
=3D?1`,
> which you might want to double-check.
> >
> >> On Wed, Nov 20, 2019, at 20:04, Kazuho Oku wrote:
> >> Dear working groups members,
> >>
> >> After the HTTPbis meeting on Monday, the priorities design team as wel=
l
> >> as others have had discussions, and have converged on a particular
> >> design (header-based, as well as allowing intermediaries to send frame=
s
> >> to express per-hop priorities).
> >>
> >> We have submitted a new revision of the I-D that reflects the emerging
> >> consensus, that clarifies more about the corner cases and how they
> >> should be handled.
> >>
> >> It can be found at:
> >> https://tools.ietf.org/html/draft-kazuho-httpbis-priority-04
> >> HTML version is:
> >>
> https://kazuho.github.io/draft-kazuho-httpbis-priority/draft-kazuho-httpb=
is-priority.html
> >>
> >> We have asked chairs to give us some time in tomorrow's HTTPbis meetin=
g
> >> that we can use to provide an update on the status.
> >>
> >> We are looking forward to hearing your comments either face-to-face, o=
r
> >> on the mailing list.
> >>
> >> Thank you in advance.
> >>
> >> ---------- Forwarded message ---------
> >> From: <internet-drafts@ietf.org>
> >> Date: 2019=E5=B9=B411=E6=9C=8820=E6=97=A5(=E6=B0=B4) 19:53
> >> Subject: New Version Notification for
> draft-kazuho-httpbis-priority-04..txt
> >> To: Kazuho Oku <kazuhooku@gmail.com>, Lucas Pardue <
> lucaspardue.24.7@gmail.com>
> >>
> >>
> >>
> >> A new version of I-D, draft-kazuho-httpbis-priority-04.txt
> >> has been successfully submitted by Kazuho Oku and posted to the
> >> IETF repository.
> >>
> >> Name: draft-kazuho-httpbis-priority
> >> Revision: 04
> >> Title: Extensible Prioritization Scheme for HTTP
> >> Document date: 2019-11-20
> >> Group: Individual Submission
> >> Pages: 20
> >> URL:
> https://www.ietf.org/internet-drafts/draft-kazuho-httpbis-priority-04.txt
> >> Status: https://datatracker.ietf.org/doc/draft-kazuho-httpbis-priority=
/
> >> Htmlized: https://tools.ietf.org/html/draft-kazuho-httpbis-priority-04
> >> Htmlized:
> https://datatracker.ietf.org/doc/html/draft-kazuho-httpbis-priority
> >> Diff:
> https://www.ietf.org/rfcdiff?url2=3Ddraft-kazuho-httpbis-priority-04
> >>
> >> Abstract:
> >> This document describes a scheme for prioritizing HTTP responses.
> >> This scheme expresses the priority of each HTTP response using
> >> absolute values, rather than as a relative relationship between a
> >> group of HTTP responses.
> >>
> >> This document defines the Priority header field for communicating the
> >> initial priority in an HTTP version-independent manner, as well as
> >> HTTP/2 and HTTP/3 frames for reprioritizing the responses. These
> >> share a common format structure that is designed to provide future
> >> extensibility.
> >>
> >>
> >>
> >>
> >> 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.
> >>
> >> The IETF Secretariat
> >>
> >>
> >>
> >> --
> >> Kazuho Oku
> >
>
>

--=20
Kazuho Oku

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

<div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><br></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">2019=E5=B9=B411=E6=
=9C=8821=E6=97=A5(=E6=9C=A8) 9:54 Roy T. Fielding &lt;<a href=3D"mailto:fie=
lding@gbiv.com">fielding@gbiv.com</a>&gt;:<br></div><blockquote class=3D"gm=
ail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;border-l=
eft-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex">I agre=
e with Martin=E2=80=99s comments. We really should emphasize that these are=
 suggestions for improving the user experience that may need to be adjusted=
 based on external knowledge by recipients.<br>
<br>
Also, there is a spot in the document where Vary is mentioned as being appr=
opriate. I don=E2=80=99t agree that Vary is ever appropriate for this featu=
re because that changes the semantics of the priority in ways that are terr=
ibly unpredictable, nor is content negotiation on the basis of received Pri=
ority a good idea. I would simply require that Priority not be included in =
preemptive content negotiation and be done.<br></blockquote><div><br></div>=
<div>Roy, thank you for the review and the suggestion. I think you are corr=
ect, I have opened <a href=3D"https://github.com/kazuho/draft-kazuho-httpbi=
s-priority/pull/119">https://github.com/kazuho/draft-kazuho-httpbis-priorit=
y/pull/119</a> to address the issue.</div><div>=C2=A0</div><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;b=
order-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"=
>
<br>
Even with these minor issues, I think this draft is a great improvement and=
 is ready for adoption by the WG.<br>
<br>
.....Roy<br>
<br>
<br>
&gt; On Nov 21, 2019, at 8:17 AM, Martin Thomson &lt;<a href=3D"mailto:mt@l=
owentropy.net" target=3D"_blank">mt@lowentropy.net</a>&gt; wrote:<br>
&gt; <br>
&gt; =EF=BB=BFKazuho,<br>
&gt; <br>
&gt; Thanks for putting this together.=C2=A0 I only looked briefly, but thi=
s appears to faithfully capture what we discussed.<br>
&gt; <br>
&gt; Why did you choose to express this with a dictionary `u=3D4, i=3D?1`**=
 rather than a numeric item `4;i=3D?1`?<br>
&gt; <br>
&gt; Can we look to simplifying this a little more?=C2=A0 I understand that=
 reprioritization was identified as being important by the design team, but=
 I don&#39;t recall seeing ever any evidence to support that view.=C2=A0 Ca=
n we split that piece out and maybe pursue it separately?<br>
&gt; <br>
&gt; I would prefer to frame the way in which priorities are &quot;merged&q=
uot; (Section 6) differently.=C2=A0 I would instead say that the priority i=
nformation is input to prioritization decisions that endpoints/intermediari=
es/etc.. make.=C2=A0 So I would instead say that these entities simply make=
 their own decision about the way to incorporate these signals into their d=
ecision.=C2=A0 That&#39;s probably a systemic thing that affects more than =
Section 6; I see that the draft uses &quot;obey&quot; in Section 7.1.1, for=
 example.<br>
&gt; <br>
&gt; There seems - at least to me - to be an assumption on the part of some=
 people involved in this that Priority will be interpreted as an imperative=
.=C2=A0 That is, that a client might be able to tell a server to act in a p=
articular way and expect to have that instruction complied with.=C2=A0 Same=
 for servers and proxies.=C2=A0 That might be an appealing, but I can&#39;t=
 see any way in which we can rely on that.=C2=A0 To the example in the draf=
t, as a CDN, I would expect that the server&#39;s view carries more weight =
than the client&#39;s, but I wouldn&#39;t necessarily say that this somethi=
ng as absolute as is currently implied.<br>
&gt; <br>
&gt; ** The draft is unclear as to whether it is `u=3D4,i=3D?1` or `u=3D4;i=
=3D?1`, which you might want to double-check.<br>
&gt; <br>
&gt;&gt; On Wed, Nov 20, 2019, at 20:04, Kazuho Oku wrote:<br>
&gt;&gt; Dear working groups members,<br>
&gt;&gt; <br>
&gt;&gt; After the HTTPbis meeting on Monday, the priorities design team as=
 well <br>
&gt;&gt; as others have had discussions, and have converged on a particular=
 <br>
&gt;&gt; design (header-based, as well as allowing intermediaries to send f=
rames<br>
&gt;&gt; to express per-hop priorities).<br>
&gt;&gt; <br>
&gt;&gt; We have submitted a new revision of the I-D that reflects the emer=
ging <br>
&gt;&gt; consensus, that clarifies more about the corner cases and how they=
 <br>
&gt;&gt; should be handled.<br>
&gt;&gt; <br>
&gt;&gt; It can be found at: <br>
&gt;&gt; <a href=3D"https://tools.ietf.org/html/draft-kazuho-httpbis-priori=
ty-04" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/dra=
ft-kazuho-httpbis-priority-04</a><br>
&gt;&gt; HTML version is: <br>
&gt;&gt; <a href=3D"https://kazuho.github.io/draft-kazuho-httpbis-priority/=
draft-kazuho-httpbis-priority.html" rel=3D"noreferrer" target=3D"_blank">ht=
tps://kazuho.github.io/draft-kazuho-httpbis-priority/draft-kazuho-httpbis-p=
riority.html</a><br>
&gt;&gt; <br>
&gt;&gt; We have asked chairs to give us some time in tomorrow&#39;s HTTPbi=
s meeting <br>
&gt;&gt; that we can use to provide an update on the status.<br>
&gt;&gt; <br>
&gt;&gt; We are looking forward to hearing your comments either face-to-fac=
e, or <br>
&gt;&gt; on the mailing list.<br>
&gt;&gt; <br>
&gt;&gt; Thank you in advance.<br>
&gt;&gt; <br>
&gt;&gt; ---------- Forwarded message ---------<br>
&gt;&gt; From: &lt;<a href=3D"mailto:internet-drafts@ietf.org" target=3D"_b=
lank">internet-drafts@ietf.org</a>&gt;<br>
&gt;&gt; Date: 2019=E5=B9=B411=E6=9C=8820=E6=97=A5(=E6=B0=B4) 19:53<br>
&gt;&gt; Subject: New Version Notification for draft-kazuho-httpbis-priorit=
y-04..txt<br>
&gt;&gt; To: Kazuho Oku &lt;<a href=3D"mailto:kazuhooku@gmail.com" target=
=3D"_blank">kazuhooku@gmail.com</a>&gt;, Lucas Pardue &lt;<a href=3D"mailto=
:lucaspardue.24.7@gmail.com" target=3D"_blank">lucaspardue.24.7@gmail.com</=
a>&gt;<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; A new version of I-D, draft-kazuho-httpbis-priority-04.txt<br>
&gt;&gt; has been successfully submitted by Kazuho Oku and posted to the<br=
>
&gt;&gt; IETF repository.<br>
&gt;&gt; <br>
&gt;&gt; Name: draft-kazuho-httpbis-priority<br>
&gt;&gt; Revision: 04<br>
&gt;&gt; Title: Extensible Prioritization Scheme for HTTP<br>
&gt;&gt; Document date: 2019-11-20<br>
&gt;&gt; Group: Individual Submission<br>
&gt;&gt; Pages: 20<br>
&gt;&gt; URL: <a href=3D"https://www.ietf.org/internet-drafts/draft-kazuho-=
httpbis-priority-04.txt" rel=3D"noreferrer" target=3D"_blank">https://www.i=
etf.org/internet-drafts/draft-kazuho-httpbis-priority-04.txt</a><br>
&gt;&gt; Status: <a href=3D"https://datatracker.ietf.org/doc/draft-kazuho-h=
ttpbis-priority/" rel=3D"noreferrer" target=3D"_blank">https://datatracker.=
ietf.org/doc/draft-kazuho-httpbis-priority/</a><br>
&gt;&gt; Htmlized: <a href=3D"https://tools.ietf.org/html/draft-kazuho-http=
bis-priority-04" rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.or=
g/html/draft-kazuho-httpbis-priority-04</a><br>
&gt;&gt; Htmlized: <a href=3D"https://datatracker.ietf.org/doc/html/draft-k=
azuho-httpbis-priority" rel=3D"noreferrer" target=3D"_blank">https://datatr=
acker.ietf.org/doc/html/draft-kazuho-httpbis-priority</a><br>
&gt;&gt; Diff: <a href=3D"https://www.ietf.org/rfcdiff?url2=3Ddraft-kazuho-=
httpbis-priority-04" rel=3D"noreferrer" target=3D"_blank">https://www.ietf.=
org/rfcdiff?url2=3Ddraft-kazuho-httpbis-priority-04</a><br>
&gt;&gt; <br>
&gt;&gt; Abstract:<br>
&gt;&gt; This document describes a scheme for prioritizing HTTP responses.<=
br>
&gt;&gt; This scheme expresses the priority of each HTTP response using<br>
&gt;&gt; absolute values, rather than as a relative relationship between a<=
br>
&gt;&gt; group of HTTP responses.<br>
&gt;&gt; <br>
&gt;&gt; This document defines the Priority header field for communicating =
the<br>
&gt;&gt; initial priority in an HTTP version-independent manner, as well as=
<br>
&gt;&gt; HTTP/2 and HTTP/3 frames for reprioritizing the responses. These<b=
r>
&gt;&gt; share a common format structure that is designed to provide future=
<br>
&gt;&gt; extensibility.<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; Please note that it may take a couple of minutes from the time of =
submission<br>
&gt;&gt; until the htmlized version and diff are available at <a href=3D"ht=
tp://tools.ietf.org" rel=3D"noreferrer" target=3D"_blank">tools.ietf.org</a=
>.<br>
&gt;&gt; <br>
&gt;&gt; The IETF Secretariat<br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; <br>
&gt;&gt; -- <br>
&gt;&gt; Kazuho Oku<br>
&gt; <br>
<br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature">Kazuho Oku</div></div></div>

--000000000000d80ec10597d601e3--


From nobody Wed Nov 20 23:23:23 2019
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 C001C12094E for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 23:23:22 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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=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 v176jEwBD1YF for <quic@ietfa.amsl.com>; Wed, 20 Nov 2019 23:23:20 -0800 (PST)
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 D9649120048 for <quic@ietf.org>; Wed, 20 Nov 2019 23:23:20 -0800 (PST)
Received: from pps.filterd (m0122332.ppops.net [127.0.0.1]) by mx0a-00190b01.pphosted.com (8.16.0.42/8.16.0.42) with SMTP id xAL7N3nn000539; Thu, 21 Nov 2019 07:23:12 GMT
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=3AtgYvPckOsox6c/vAoKGefggNWndhLveax4KRPSTHs=; b=GUb8YVvIIBWM/7RX+nLQk3jQDp88DCgK6Y7+lJC3aKQdJTS3189RLYW8wWof7PzdbOeY kJSu+952PO/No2kTIc7iFo9K3LJ5bU3R2G9hYi7AZnFjKDEUGIjXuU4Bc3l8HSKY4yYv vlqRHGi/5lLIRJgs4ukArsO6Gkm+oftGFpTeOFWYXff1/+fHBhABXtx2VXwss2hEs/lH iy3h59iL2Gaw2UNWznNASBjUxxUrqSwJYgxQ5ZUBuzx5HupKkaH3BbSqC2jstSnGl2NX UH7lTrRxKt8SKeDx/hB5bor7c5iBpUy4z9vSol8z26HazGUIPBwX7C2oQnQhvbKJVJVk Vg== 
Received: from prod-mail-ppoint6 (prod-mail-ppoint6.akamai.com [184.51.33.61] (may be forged)) by mx0a-00190b01.pphosted.com with ESMTP id 2wafutx7cu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Thu, 21 Nov 2019 07:23:11 +0000
Received: from pps.filterd (prod-mail-ppoint6.akamai.com [127.0.0.1]) by prod-mail-ppoint6.akamai.com (8.16.0.27/8.16.0.27) with SMTP id xAL7Gu88024750; Thu, 21 Nov 2019 02:23:10 -0500
Received: from email.msg.corp.akamai.com ([172.27.165.114]) by prod-mail-ppoint6.akamai.com with ESMTP id 2wadaxu21t-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 21 Nov 2019 02:23:08 -0500
Received: from USTX2EX-DAG1MB5.msg.corp.akamai.com (172.27.165.123) by ustx2ex-dag1mb1.msg.corp.akamai.com (172.27.165.119) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 21 Nov 2019 01:23:06 -0600
Received: from USTX2EX-DAG1MB5.msg.corp.akamai.com ([172.27.165.123]) by ustx2ex-dag1mb5.msg.corp.akamai.com ([172.27.165.123]) with mapi id 15.00.1473.005; Thu, 21 Nov 2019 01:23:06 -0600
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: "Brian Trammell (IETF)" <ietf@trammell.ch>, Lars Eggert <lars@eggert.org>
CC: IETF QUIC WG <quic@ietf.org>, Christian Huitema <huitema@huitema.net>, "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, "Dmitri Tikhonov" <dtikhonov@litespeedtech.com>
Subject: RE: CONEX? (was: Re: Q and L loss bits)
Thread-Topic: CONEX? (was: Re: Q and L loss bits)
Thread-Index: AQHVoDbg9/uTCNZtvUmvO6ZyW7zzuaeVklGA//+feYA=
Date: Thu, 21 Nov 2019 07:23:06 +0000
Message-ID: <b87ec28d39004c07a05662e200f82108@ustx2ex-dag1mb5.msg.corp.akamai.com>
References: <20191119143218.GB2789@ubuntu-dmitri> <24388_1574174932_5DD400D4_24388_372_7_1574174948.30247.49.camel@orange.com> <20191119150829.GD2789@ubuntu-dmitri> <20191119192622.GE2789@ubuntu-dmitri> <a21bc373-1fda-836e-7efc-599832ae575d@huitema.net> <20191120014850.GC16017@ubuntu-dmitri> <cd2e9389a61d49eabad2b0fac2f4db96@ustx2ex-dag1mb5.msg.corp.akamai.com> <A5687771-2F40-419F-A8A2-00FFF919B3FA@eggert.org> <A6DB3084-447B-467A-B164-310C83A6526C@trammell.ch>
In-Reply-To: <A6DB3084-447B-467A-B164-310C83A6526C@trammell.ch>
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.219.86]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:, , definitions=2019-11-20_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=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140001 definitions=main-1911210064
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-11-20_08:2019-11-20,2019-11-20 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 phishscore=0 spamscore=0 mlxscore=0 priorityscore=1501 mlxlogscore=999 adultscore=0 bulkscore=0 malwarescore=0 lowpriorityscore=0 clxscore=1015 impostorscore=0 suspectscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1911210064
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/TOQATWeTnkyU8HgSgvKGdHfONSw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2019 07:23:23 -0000

A few things about the ConEx vs QL-lossbits

1. ConEx has a mechanism that is similar to L-bit (we mention ConEx RFC7713=
 in the draft).  But it has no equivalent of the Q-bit signal.  It is very =
hard to tell upstream loss from downstream loss with ConEx.

2. ConEx reports bytes, while QL-loss reports packets.  There is a trade-of=
f here, as bytes may be more valuable, but reporting bytes can be imprecise=
, if the packets marked are of different size from the packets lost.  Overa=
ll, both work well enough.

3. ConEx requires more bits than what we have in QUICv1, so it would be a s=
ignificant disruption to QUICv1 header format to properly implement all Con=
Ex bits.  The Q- and L- bits are enough for the purpose.

4. CWR is an interesting signal, and I actually have a separate CWR bit (I =
call it "E-bit") in https://tools.ietf.org/html/draft-ferrieuxhamchaoui-tsv=
wg-lossbits-02#section-5 -- the -tsvwg- version of the draft.  However, it =
is not very closely related to loss for networks with ECN.  On an ECN-capab=
le network for ECN-capable flows, downstream loss would become indistinguis=
hable from downstream congestion that marks CE.  Ultimately, it seemed that=
 given just two bits to work with, Q-bit plus a pure loss bit seemed prefer=
able to Q-bit plus "loss-or-CE_echo" bit.  But I am happy to discuss this!

- Igor

> On Thu, Nov 21, 2019 at 2:44 PM, Brian Trammell (IETF) <ietf@trammell.ch>=
 wrote:
>=20
> hi Lars,
>=20
> This is kind of where I was going with the "expose CWR-like semantics for=
 loss"
> thing; "just do conex" is a much better shorthand for that.
>=20
> Thanks, cheers,
>=20
> Brian
>=20
> > On 21 Nov 2019, at 14:42, Lars Eggert <lars@eggert.org> wrote:
> >
> > Hi,
> >
> > I'm wondering whether specifying a CONEX mapping for QUIC would satisfy
> the needs that quic-lossbits attempts to address? We could reuse an exist=
ing
> piece of IETF work.
> >
> > See https://tools.ietf.org/html/rfc7713 for an overview and
> https://tools.ietf.org/html/rfc7786 for the TCP mapping.
> >
> > Lars
> >


From nobody Thu Nov 21 01:16:16 2019
Return-Path: <stefan.eissing@greenbytes.de>
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 C798A1209C8 for <quic@ietfa.amsl.com>; Thu, 21 Nov 2019 01:16:15 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 SCtnCRASaJ5z for <quic@ietfa.amsl.com>; Thu, 21 Nov 2019 01:16:14 -0800 (PST)
Received: from mail.greenbytes.de (mail.greenbytes.de [217.91.35.233]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E292B120936 for <quic@ietf.org>; Thu, 21 Nov 2019 01:16:13 -0800 (PST)
Received: by mail.greenbytes.de (Postfix, from userid 119) id 00EE598465A; Thu, 21 Nov 2019 10:16:11 +0100 (CET)
Received: from resistance.greenbytes.local (unknown [192.168.1.65]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mail.greenbytes.de (Postfix) with ESMTPSA id B1F80980A5B for <quic@ietf.org>; Thu, 21 Nov 2019 10:16:11 +0100 (CET)
From: Stefan Eissing <stefan.eissing@greenbytes.de>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: quoted-printable
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: Re: Priorities I-D for Thursday HTTPbis meeting (Fwd: New Version Notification for draft-kazuho-httpbis-priority-04.txt)
Date: Thu, 21 Nov 2019 10:16:11 +0100
References: <d651767a-8b6c-4e45-b154-ef1ad0bf34a3@www.fastmail.com> <421180B5-6939-4EB5-B2CA-1A97BA9BAEA9@gbiv.com> <a8f57134-114e-4d56-9076-7d880897b842@www.fastmail.com> <CAC7UV9bqo=jFearFt-yTr5M6q7noywvicG-bW6k4UQGq7bikuQ@mail.gmail.com> <fed8fbb4-69aa-4b8b-bde2-21b1eaeb6ff8@www.fastmail.com>
To: IETF QUIC WG <quic@ietf.org>
In-Reply-To: <fed8fbb4-69aa-4b8b-bde2-21b1eaeb6ff8@www.fastmail.com>
Message-Id: <85821A5D-FE1E-4B3F-88E5-D03779634257@greenbytes.de>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/KpjMORzHFxu31-ryP_fbd7jCr6s>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2019 09:16:16 -0000

First of all, thanks for Kazuho and Lucas for putting this together!

I agree with most of what has been already said, especially that it
should be adopted by the WG.

There seems to be consensus that priorities are hints for server and
not laws to obey.

The interleave setting is a new thing (yes, we had weights) and I am=20
not sure if it is really something that clients want. I understood=20
the mentioned use case, but before implementing this feature, I would=20
really like to know more about the effects it has in various scenarios.

Cheers, Stefan

> Am 21.11.2019 um 05:45 schrieb Martin Thomson <mt@lowentropy.net>:
>=20
> Hi Robin,
>=20
> On Thu, Nov 21, 2019, at 10:11, Robin MARX wrote:
>>> I understand that reprioritization was identified as being important=20=

>> by the design team, but I don't recall seeing ever any evidence to=20
>> support that view. Can we split that piece out and maybe pursue it=20
>> separately?=20
>>=20
>> Could you expand on this statement a bit more?=20
>> In my view, reprioritization has two sides: reprioritization from the=20=

>> client after sending an initial priority and server-side=20
>> reprioritization, overriding the client's initial priority.
>=20
> I refer specifically to the frame.
>=20
>> The first side comes into play when doing things like video/media=20
>> streaming when switching qualities (see e.g.,=20
>> https://github.com/kazuho/draft-kazuho-httpbis-priority/issues/92) or=20=

>> for the "switching tabs" use case that e.g., Ian keeps mentioning.
>=20
> These seem fairly obvious, but I realized recently that a lot of our =
thinking hasn't been grounded in any data.  That is, we're intuiting =
things about the value of the signal, but we never got firm reasons.
>=20


From nobody Thu Nov 21 02:07:31 2019
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 7C4611209FE for <quic@ietfa.amsl.com>; Thu, 21 Nov 2019 02:07:29 -0800 (PST)
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, SPF_HELO_NONE=0.001, 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 YPOgMcpHhwlV for <quic@ietfa.amsl.com>; Thu, 21 Nov 2019 02:07:27 -0800 (PST)
Received: from smtp-sh.infomaniak.ch (smtp-sh.infomaniak.ch [128.65.195.4]) (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 1F33A1208D9 for <quic@ietf.org>; Thu, 21 Nov 2019 02:07:25 -0800 (PST)
Received: from smtp-3-0000.mail.infomaniak.ch ([10.4.36.107]) by smtp-sh.infomaniak.ch (8.14.5/8.14.5) with ESMTP id xALA7Ed9024423 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Thu, 21 Nov 2019 11:07:14 +0100
Received: from [IPv6:2001:67c:370:128:2125:c8a4:62c3:bef5] (unknown [IPV6:2001:67c:370:128:2125:c8a4:62c3:bef5]) by smtp-3-0000.mail.infomaniak.ch (Postfix) with ESMTPA id CC3B610035677; Thu, 21 Nov 2019 11:07:10 +0100 (CET)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: CONEX? (was: Re: Q and L loss bits)
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
In-Reply-To: <b87ec28d39004c07a05662e200f82108@ustx2ex-dag1mb5.msg.corp.akamai.com>
Date: Thu, 21 Nov 2019 18:07:08 +0800
Cc: Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>, Christian Huitema <huitema@huitema.net>, "alexandre.ferrieux@orange.com" <alexandre.ferrieux@orange.com>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>
Content-Transfer-Encoding: quoted-printable
Message-Id: <55785142-03C8-48E0-B497-419AED1D1F15@trammell.ch>
References: <20191119143218.GB2789@ubuntu-dmitri> <24388_1574174932_5DD400D4_24388_372_7_1574174948.30247.49.camel@orange.com> <20191119150829.GD2789@ubuntu-dmitri> <20191119192622.GE2789@ubuntu-dmitri> <a21bc373-1fda-836e-7efc-599832ae575d@huitema.net> <20191120014850.GC16017@ubuntu-dmitri> <cd2e9389a61d49eabad2b0fac2f4db96@ustx2ex-dag1mb5.msg.corp.akamai.com> <A5687771-2F40-419F-A8A2-00FFF919B3FA@eggert.org> <A6DB3084-447B-467A-B164-310C83A6526C@trammell.ch> <b87ec28d39004c07a05662e200f82108@ustx2ex-dag1mb5.msg.corp.akamai.com>
To: "Lubashev, Igor" <ilubashe@akamai.com>
X-Mailer: Apple Mail (2.3445.104.11)
X-Antivirus: Dr.Web (R) for Unix mail servers drweb plugin ver.6.0.2.8
X-Antivirus-Code: 0x100000
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/UiqzUtslhhilHDgE_3-DoFmslHQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2019 10:07:29 -0000

> On 21 Nov 2019, at 15:23, Lubashev, Igor <ilubashe@akamai.com> wrote:
>=20
> A few things about the ConEx vs QL-lossbits
>=20
> 1. ConEx has a mechanism that is similar to L-bit (we mention ConEx =
RFC7713 in the draft).  But it has no equivalent of the Q-bit signal.  =
It is very hard to tell upstream loss from downstream loss with ConEx.

Yep, at least when I talk about this proposal I mean "replace L with =
ConEx". We can leave Q as it is. (The question as to the independent =
utility of Q and L is a separate discussion).

> 2. ConEx reports bytes, while QL-loss reports packets.  There is a =
trade-off here, as bytes may be more valuable, but reporting bytes can =
be imprecise, if the packets marked are of different size from the =
packets lost.  Overall, both work well enough.

IIRC ConEx spent an inordinate amount of time on the bytes versus =
packets bikeshed so let's not :)

> 3. ConEx requires more bits than what we have in QUICv1, so it would =
be a significant disruption to QUICv1 header format to properly =
implement all ConEx bits.  The Q- and L- bits are enough for the =
purpose.

What I'd like to look at is a one-bit encoding for L that exposes the =
same signals ConEx did. It turns out this might be about the same thing =
as L as currently defined when L doesn't count losses determined to be =
spurious.=20

> 4. CWR is an interesting signal, and I actually have a separate CWR =
bit (I call it "E-bit") in =
https://tools.ietf.org/html/draft-ferrieuxhamchaoui-tsvwg-lossbits-02#sect=
ion-5 -- the -tsvwg- version of the draft.  However, it is not very =
closely related to loss for networks with ECN.

This raises the other question: whether what we really want to measure =
is "this packet is lost" (which network operations activities use loss =
as an indication of lower-layer issues they need to fix) or "this packet =
caused the transport difficulty" (which is more of an indication of =
endpoint-visible performance, interesting to a different department in =
network operations). Or, "if a packet is dropped in the woods, and =
nobody cares about it, does it make a sound?"

On most networks with most deployed CC algorithms these generate =
basically the same metric, so the distinction is maybe philosophical. It =
is less true for nonelastic traffic and for newer CC algorithms.

Cheers,

Brian

>  On an ECN-capable network for ECN-capable flows, downstream loss =
would become indistinguishable from downstream congestion that marks CE. =
 Ultimately, it seemed that given just two bits to work with, Q-bit plus =
a pure loss bit seemed preferable to Q-bit plus "loss-or-CE_echo" bit.  =
But I am happy to discuss this!
>=20
> - Igor
>=20
>> On Thu, Nov 21, 2019 at 2:44 PM, Brian Trammell (IETF) =
<ietf@trammell.ch> wrote:
>>=20
>> hi Lars,
>>=20
>> This is kind of where I was going with the "expose CWR-like semantics =
for loss"
>> thing; "just do conex" is a much better shorthand for that.
>>=20
>> Thanks, cheers,
>>=20
>> Brian
>>=20
>>> On 21 Nov 2019, at 14:42, Lars Eggert <lars@eggert.org> wrote:
>>>=20
>>> Hi,
>>>=20
>>> I'm wondering whether specifying a CONEX mapping for QUIC would =
satisfy
>> the needs that quic-lossbits attempts to address? We could reuse an =
existing
>> piece of IETF work.
>>>=20
>>> See https://tools.ietf.org/html/rfc7713 for an overview and
>> https://tools.ietf.org/html/rfc7786 for the TCP mapping.
>>>=20
>>> Lars
>>>=20
>=20
>=20


From nobody Thu Nov 21 04:16:33 2019
Return-Path: <alexandre.ferrieux@orange.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 0FC3F1208A7 for <quic@ietfa.amsl.com>; Thu, 21 Nov 2019 04:16:31 -0800 (PST)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 ozAB8hkYZRUh for <quic@ietfa.amsl.com>; Thu, 21 Nov 2019 04:16:29 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 7A44B12087B for <quic@ietf.org>; Thu, 21 Nov 2019 04:16:29 -0800 (PST)
Received: from opfedar06.francetelecom.fr (unknown [xx.xx.xx.8]) by opfedar26.francetelecom.fr (ESMTP service) with ESMTP id 47Jdp41WjwzFq0w; Thu, 21 Nov 2019 13:16:28 +0100 (CET)
Received: from Exchangemail-eme3.itn.ftgroup (unknown [xx.xx.50.92]) by opfedar06.francetelecom.fr (ESMTP service) with ESMTP id 47Jdp373Szz3wbD; Thu, 21 Nov 2019 13:16:27 +0100 (CET)
Received: from lat6466.rd.francetelecom.fr (10.114.50.247) by OPEXCNORMAC.corporate.adroot.infra.ftgroup (10.114.50.92) with Microsoft SMTP Server (TLS) id 14.3.468.0; Thu, 21 Nov 2019 13:16:27 +0100
Message-ID: <32472_1574338588_5DD6801C_32472_5_1_1574338604.25904.2.camel@orange.com>
Subject: Re: CONEX? (was: Re: Q and L loss bits)
From: <alexandre.ferrieux@orange.com>
To: "Brian Trammell (IETF)" <ietf@trammell.ch>, "Lubashev, Igor" <ilubashe@akamai.com>
CC: Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>, "Christian Huitema" <huitema@huitema.net>, Dmitri Tikhonov <dtikhonov@litespeedtech.com>
In-Reply-To: <55785142-03C8-48E0-B497-419AED1D1F15@trammell.ch>
References: <20191119143218.GB2789@ubuntu-dmitri> <24388_1574174932_5DD400D4_24388_372_7_1574174948.30247.49.camel@orange.com> <20191119150829.GD2789@ubuntu-dmitri> <20191119192622.GE2789@ubuntu-dmitri> <a21bc373-1fda-836e-7efc-599832ae575d@huitema.net> <20191120014850.GC16017@ubuntu-dmitri> <cd2e9389a61d49eabad2b0fac2f4db96@ustx2ex-dag1mb5.msg.corp.akamai.com> <A5687771-2F40-419F-A8A2-00FFF919B3FA@eggert.org> <A6DB3084-447B-467A-B164-310C83A6526C@trammell.ch> <b87ec28d39004c07a05662e200f82108@ustx2ex-dag1mb5.msg.corp.akamai.com> <55785142-03C8-48E0-B497-419AED1D1F15@trammell.ch>
Content-Type: text/plain; charset="ISO-8859-1"
Date: Thu, 21 Nov 2019 13:16:44 +0100
MIME-Version: 1.0
X-Mailer: Evolution 3.22.6-1+deb9u2 
Content-Transfer-Encoding: 8bit
X-Originating-IP: [10.114.50.247]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/HU8-xhMNdn6keZCEfeKKgM_ibsA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2019 12:16:31 -0000

On Thu, 2019-11-21 at 18:07 +0800, Brian Trammell (IETF) wrote:
> What I'd like to look at is a one-bit encoding for L that exposes the
> same signals ConEx did. It turns out this might be about the same
> thing as L as currently defined when L doesn't count losses
> determined to be spurious.

It might very well :)

Any other signal than loss is out of scope in many real-life scenarii:
a router that loses packets well below capacity due to internal
implementation limitations (read "bugs") will certainly *not* CE-mark
any packet; it will just drop in sheer panic. The "pre-ECN world" is
not dead.

Regarding spurious losses: you're right, it would be better if we had a
sure-fire method to eliminate them from L. Attempts to do that were
recently mentioned here. A reasonable, conservative one was proposed by
Igor yesterday:

"Ok, I think there is a better middle ground.  If the counter is > 0,
sure, decrement it (since the loss has not yet been reported).  But if
the counter is already 0, do not let it go negative, because then you
would not be able to report an actual future loss event (and an actual
future congestion controller response)."

To judge the importance of this issue, it would be good to have an idea
of the frequency of such (DSACK-like) spurious events under varied
assumptions.

_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


From nobody Thu Nov 21 05:59:00 2019
Return-Path: <alexandre.ferrieux@orange.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 DE858120867 for <quic@ietfa.amsl.com>; Thu, 21 Nov 2019 05:58:57 -0800 (PST)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, UNPARSEABLE_RELAY=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 HK9hXfiynycz for <quic@ietfa.amsl.com>; Thu, 21 Nov 2019 05:58:56 -0800 (PST)
Received: from relais-inet.orange.com (relais-inet.orange.com [80.12.66.39]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42A86120811 for <quic@ietf.org>; Thu, 21 Nov 2019 05:58:56 -0800 (PST)
Received: from opfedar00.francetelecom.fr (unknown [xx.xx.xx.11]) by opfedar23.francetelecom.fr (ESMTP service) with ESMTP id 47Jh4G4cVdzBrsT; Thu, 21 Nov 2019 14:58:54 +0100 (CET)
Received: from Exchangemail-eme3.itn.ftgroup (unknown [xx.xx.50.92]) by opfedar00.francetelecom.fr (ESMTP service) with ESMTP id 47Jh4G37XWzCqjj; Thu, 21 Nov 2019 14:58:54 +0100 (CET)
Received: from lat6466.rd.francetelecom.fr (10.114.50.247) by OPEXCNORMAC.corporate.adroot.infra.ftgroup (10.114.50.92) with Microsoft SMTP Server (TLS) id 14.3.468.0; Thu, 21 Nov 2019 14:58:54 +0100
Message-ID: <7268_1574344734_5DD6981E_7268_134_1_1574344750.3872.4.camel@orange.com>
Subject: Re: What CSRs Do
From: <alexandre.ferrieux@orange.com>
To: Frode Kileng <frodek@tele.no>, <quic@ietf.org>
In-Reply-To: <bc0cf83f-16d6-3200-5d6e-091311ccf9a7@tele.no>
References: <BL0PR11MB3394D769128DEFEEFBC3CA71904C0@BL0PR11MB3394.namprd11.prod.outlook.com> <0cf4d3ad-0f64-0ae4-2d95-77a39f40639d@tele.no> <20191119042904.GC5602@1wt.eu> <4003626d-8966-6772-7df0-e76549320430@gmail.com> <1574144751435.15844@akamai.com> <bc0cf83f-16d6-3200-5d6e-091311ccf9a7@tele.no>
Content-Type: text/plain; charset="TIS-620"
Date: Thu, 21 Nov 2019 14:59:10 +0100
MIME-Version: 1.0
X-Mailer: Evolution 3.22.6-1+deb9u2 
Content-Transfer-Encoding: 7bit
X-Originating-IP: [10.114.50.247]
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/zzQonesMlINcAzr5dgRs47JsO3w>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2019 13:58:58 -0000

On Tue, 2019-11-19 at 07:42 +0100, Frode Kileng wrote:
> On 19/11/2019 07:25, Lubashev, Igor wrote:
> > 
> > This is assuming there is a robust set of "other 'loss source'"
> > available. This is far from reality for the vast majority of cases.
> 
> So then there's two alternatives: a) Standardize a "loss-signal"
> option in QUIC and hope this is implemented and supported. b) Network
> operators lacking a "robust set of other loss sources" obtain such
> sources.
> 
> frodek

To *lack* these sources, one might be incompetent, as you are
suggesting many people are. Alternatively, one might simply care about
a long end-to-end path with several responsibility boundaries, which by
definition are opaque. In this case, as Igor said, the
upstream/downstream location is absolutely crucial.


_________________________________________________________________________________________________________________________

Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.


From nobody Thu Nov 21 06:06:23 2019
Return-Path: <jiuhai.zhang@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 E645C1208BA for <quic@ietfa.amsl.com>; Thu, 21 Nov 2019 06:06:21 -0800 (PST)
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_HELO_NONE=0.001, 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 HRMV_c1fDAt1 for <quic@ietfa.amsl.com>; Thu, 21 Nov 2019 06:06:20 -0800 (PST)
Received: from mail-lj1-x22d.google.com (mail-lj1-x22d.google.com [IPv6:2a00:1450:4864:20::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 17D701201AA for <quic@ietf.org>; Thu, 21 Nov 2019 06:06:20 -0800 (PST)
Received: by mail-lj1-x22d.google.com with SMTP id v8so3366547ljh.5 for <quic@ietf.org>; Thu, 21 Nov 2019 06:06:20 -0800 (PST)
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=t506votQVQ4i0kD3k8EDISzz5RBrtd6UaQQR87A9QGE=; b=EF6SgnY0U1OiwuFi8ab/eTUZvJgS9YmZJFPOcZ2+EOZEYwPDD7xFTunIvM9rgi2QbY 385FqFNPxKxqvRWCPoesiIC2Fb0FjhxlS2JOOKqaTUDXRTlT3TIr67UIKnnXxadGL6T5 OaRzQoaROwCl3iyrN/c9iWh5TTGj/V3USS9U38vQAahVg5ELCFqTRpDYYpCAIKHamxPV inQ7OwnS2izLiH2v9YYcz1BIxhLoBegLtbSi9G1uNkxUlY62f5BcJ/ROPp7rpgW6WjKr WDXQB+Kl5BrSzBB/wQVCa1BMBIM5mp2v8C6DHTKwLtk8DbwTZPZMNw4V8fPrCEvFMnfg ikuw==
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=t506votQVQ4i0kD3k8EDISzz5RBrtd6UaQQR87A9QGE=; b=AV9zqr14wP76v4pSEMd3qVQlQgMQYkWFz55bvoGZRO71i6+sHbdQuZUDksBWohwb4n nsxXY6pQoc3h/TqK2EdO8huBimFdL269WBx3nSRnBHMm9hZxcCZC2/TVobJ0Z5e16j+g 2K5bCL15Uui2J//KS8Mgi+mhwbeAsXyHg8maPXxUqcoAO+1j3FXxQ78wAwdntEcOxQQp mr7ewHmHiwC23uBAgpnzL43eVqs2ONGWx2/neCVrka9pDd06d3hrwVy9sSP1vH0iPh6c O1kezT7Ktd5w31nUaiTJiNxI3QMJuL2NTVyoJxgK6ibaIgnANsqFXPqNYWfMmnuQl5iH UJnQ==
X-Gm-Message-State: APjAAAXe1x0Z9wUicPAiIgEc0cX0fSS1SP0gVOrbeZB20RAWyYmiuniB M09aDayDU5ic2OtMaTxaXt3CEjI51TyyjN5gKE2I7Ypa
X-Google-Smtp-Source: APXvYqyo/Npow8j+GHhZIOdGF4yvcEM4ZYURie8el0RZPdkGE2i1vSiguByrFvS1igE2Yip2WGtaqZ/guuQTrpS61OM=
X-Received: by 2002:a2e:2c1a:: with SMTP id s26mr7787863ljs.239.1574345177592;  Thu, 21 Nov 2019 06:06:17 -0800 (PST)
MIME-Version: 1.0
From: Jiuhai Zhang <jiuhai.zhang@gmail.com>
Date: Thu, 21 Nov 2019 22:06:04 +0800
Message-ID: <CAG9+TpYtZniZ63xc3Wpb7NNpkVyj1G9_p-rtCjspdCr+oz8edg@mail.gmail.com>
Subject: Questions about QPACK
To: quic@ietf.org
Cc: 78690842@qq.com
Content-Type: multipart/alternative; boundary="0000000000001077660597dbcdc3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/k4YhSASgRVFeOCKMpv-NTGc6vi8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2019 14:06:22 -0000

--0000000000001077660597dbcdc3
Content-Type: text/plain; charset="UTF-8"

https://tools.ietf.org/html/draft-ietf-quic-qpack-11#section-4.4.3

   0   1   2   3   4   5   6   7
      +---+---+---+---+---+---+---+---+
      | 0 | 1 | N | T |Name Index (4+)|
      +---+---+---+---+---------------+
      | H |     Value Length (7+)     |
      +---+---------------------------+
      |  Value String (Length bytes)  |
      +-------------------------------+

Q1:why we send N bit to peer? it seems we don't need to send the bit,
if sender don't want to put in dynamic table.


https://tools.ietf.org/html/draft-ietf-quic-qpack-11#section-4.5.4

        0   1   2   3   4   5   6   7
      +---+---+---+---+---+---+---+---+
      | 0 | 1 | N | T |Name Index (4+)|
      +---+---+---+---+---------------+
      | H |     Value Length (7+)     |
      +---+---------------------------+
      |  Value String (Length bytes)  |
      +-------------------------------+

Q2:when we encode new name, new value, we should insert name,value
pair into dynamic table, should we insert name only into dynamic
table?

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

<div dir=3D"ltr"><div><a href=3D"https://tools.ietf.org/html/draft-ietf-qui=
c-qpack-11#section-4.4.3">https://tools.ietf.org/html/draft-ietf-quic-qpack=
-11#section-4.4.3</a><br></div><div><pre class=3D"gmail-newpage" style=3D"f=
ont-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:page;color=
:rgb(0,0,0)">   0   1   2   3   4   5   6   7
      +---+---+---+---+---+---+---+---+
      | 0 | 1 | N | T |Name Index (4+)|
      +---+---+---+---+---------------+
      | H |     Value Length (7+)     |
      +---+---------------------------+
      |  Value String (Length bytes)  |
      +-------------------------------+</pre><pre class=3D"gmail-newpage" s=
tyle=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:p=
age;color:rgb(0,0,0)">Q1:why we send N bit to peer? it seems we don&#39;t n=
eed to send the bit, if sender don&#39;t want to put in dynamic table.</pre=
><pre class=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;m=
argin-bottom:0px;break-before:page;color:rgb(0,0,0)"><br></pre><pre class=
=3D"gmail-newpage" style=3D"font-size:13.3333px;margin-top:0px;margin-botto=
m:0px;break-before:page;color:rgb(0,0,0)"><a href=3D"https://tools.ietf.org=
/html/draft-ietf-quic-qpack-11#section-4.5.4">https://tools.ietf.org/html/d=
raft-ietf-quic-qpack-11#section-4.5.4</a></pre><pre class=3D"gmail-newpage"=
 style=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before=
:page;color:rgb(0,0,0)"><pre class=3D"gmail-newpage" style=3D"font-size:13.=
3333px;margin-top:0px;margin-bottom:0px;break-before:page">        0   1   =
2   3   4   5   6   7
      +---+---+---+---+---+---+---+---+
      | 0 | 1 | N | T |Name Index (4+)|
      +---+---+---+---+---------------+
      | H |     Value Length (7+)     |
      +---+---------------------------+
      |  Value String (Length bytes)  |
      +-------------------------------+</pre><pre class=3D"gmail-newpage" s=
tyle=3D"font-size:13.3333px;margin-top:0px;margin-bottom:0px;break-before:p=
age">Q2:when we encode new name, new value, we should insert name,value pai=
r into dynamic table, should we insert name only into dynamic table?</pre><=
/pre></div></div>

--0000000000001077660597dbcdc3--


From nobody Thu Nov 21 07:25:44 2019
Return-Path: <bnc@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 B0AFC120878 for <quic@ietfa.amsl.com>; Thu, 21 Nov 2019 06:57:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.252
X-Spam-Level: 
X-Spam-Status: No, score=-9.252 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.249, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_SPF_WL=-7.5] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=chromium.org
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 22WCtWk9zh0u for <quic@ietfa.amsl.com>; Thu, 21 Nov 2019 06:57:37 -0800 (PST)
Received: from mail-vk1-xa2f.google.com (mail-vk1-xa2f.google.com [IPv6:2607:f8b0:4864:20::a2f]) (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 A69AB120843 for <quic@ietf.org>; Thu, 21 Nov 2019 06:57:37 -0800 (PST)
Received: by mail-vk1-xa2f.google.com with SMTP id p78so800141vkp.8 for <quic@ietf.org>; Thu, 21 Nov 2019 06:57:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=C7VoYYUgZ8J8aK84Yyl1lrq95gKKt+3DA6MnPAnmOKc=; b=oFcBd6DuNlnRH6H23OtYM3Wsvvdd/O4KQnlP/wAYrW8EiHkUcnOehyylaZQOzHuzoW B7oINdUVDnGE+TDFDbKUYqKJ//Aj6nnWO9EsVSTQ9VgckNUEOHaOGrRhaL9Yu4+TlchT vXkDws0qXAgGTwjFucqfs2Z6PRSpUwnZeK7dg=
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=C7VoYYUgZ8J8aK84Yyl1lrq95gKKt+3DA6MnPAnmOKc=; b=tqgNbKg5tGCywne7ujs3ol5+s9ZDJx0/Dp6WhlgaSktzq3MZTAD1xDacRPNAoG5Mp9 AaZhO4QM5reyvajKvqE0kYE1SQ83bYVdiVVdazvTP7n13lHmAsvwmC3ltoFBPGEOsJGG sA84Pm9qrF0cwZwTGpPlSj/8CcIptVbOVwzh5JNCB6vw8J5vevS6PaTruD1DRz3tct8K FcQUOjkxvsloWpPvCXZ7WsNogBVeb8eJdOXJ8fLOZ8ZBpdAZIiz1ub+i86iq4WDmb6TE 1+lHs76pfUs9DhkVXocg4K3i4pIhuLscWDBOFvfcnalOLU0mZvww835NnT2mziUpw4Ph Yl1g==
X-Gm-Message-State: APjAAAWOz7AyAapLcP2vH5nuqqx9Oze0hIwA0igQnler1JT5eCqvar7U gRv6WDymhDlI972tiPy1WBLVyMjV+dR327HlYGfilQ==
X-Google-Smtp-Source: APXvYqygxbV8ExSrLB2xfjmUI7/WdWyao9nkHof9haVh/MBgxGp9fYxUu9nkl5bOrm5OkDHVwb6CmHBdQZJapGnB8bk=
X-Received: by 2002:a1f:5106:: with SMTP id f6mr5832286vkb.88.1574348255882; Thu, 21 Nov 2019 06:57:35 -0800 (PST)
MIME-Version: 1.0
References: <CAG9+TpYtZniZ63xc3Wpb7NNpkVyj1G9_p-rtCjspdCr+oz8edg@mail.gmail.com>
In-Reply-To: <CAG9+TpYtZniZ63xc3Wpb7NNpkVyj1G9_p-rtCjspdCr+oz8edg@mail.gmail.com>
From: =?UTF-8?Q?Bence_B=C3=A9ky?= <bnc@chromium.org>
Date: Thu, 21 Nov 2019 09:57:24 -0500
Message-ID: <CACMu3tq6q+UDyyUqQHC_VK0gxGSnBj_=1DsnmRMHPChgawL0tw@mail.gmail.com>
Subject: Re: Questions about QPACK
To: Jiuhai Zhang <jiuhai.zhang@gmail.com>
Cc: quic@ietf.org, 78690842@qq.com
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ubx7IMbwIESy0YgxNGNlGwEauzU>
X-Mailman-Approved-At: Thu, 21 Nov 2019 07:25:44 -0800
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2019 14:57:39 -0000

Hi,

Great questions.

>
> Q1:why we send N bit to peer? it seems we don't need to send the bit, if sender don't want to put in dynamic table.
>

QPACK is hop-to-hop, that is, client to intermediary, intermediary to
intermediary, intermediary to server, all separately (and the other
way around).  Intermediary can be locally installed
firewall/antivirus, proxy, reverse proxy, load balancer etc.
Intermediaries are allowed to recompress headers using different
algorithms using QPACK, or they might relay to an HTTP/2 connection
using HPACK, etc.  The N bit is to inform intermediaries whether the
original sender of the headers deems that the header MUST always be
encoded using literals.

>
> Q2:when we encode new name, new value, we should insert name,value pair into dynamic table, should we insert name only into dynamic table?
>

Header block representations do not mutate the dynamic table: they do
not insert or duplicate or evict entries or change dynamic table
capacity.  Mutating of the dynamic table only happens on the dedicated
encoder stream.  This is because the order of delivery between header
blocks on different requests streams is not guaranteed, so if
insertions were allowed in header blocks, the order in which these
insertions could arrive would be undefined.

Bence


From nobody Thu Nov 21 08:25:53 2019
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 2D504120888 for <quic@ietfa.amsl.com>; Thu, 21 Nov 2019 08:25:52 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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=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 eyYEgRSiBvWd for <quic@ietfa.amsl.com>; Thu, 21 Nov 2019 08:25:50 -0800 (PST)
Received: from mail-qt1-x829.google.com (mail-qt1-x829.google.com [IPv6:2607:f8b0:4864:20::829]) (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 78ADA120125 for <quic@ietf.org>; Thu, 21 Nov 2019 08:25:50 -0800 (PST)
Received: by mail-qt1-x829.google.com with SMTP id y10so4332035qto.3 for <quic@ietf.org>; Thu, 21 Nov 2019 08:25:50 -0800 (PST)
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=m9jTSFC2u1FVaLE+UtzO3QKSK1cwjZv+QW7ATAPiWlA=; b=0GntcTnPjET3qRUj6cvmZqbMhWO9PzVPfm7OrOzAdnpROAIK8Nzn1j3J2JHF+iWeeM pph88zCxPp6fbaNu4ibrDKjcCfdWctV6Xq8EAe0urBGY91/fHoBw6Pkw5zuycRBeJpbg +zeL98+QgNfKTZA55cSrDZs/6S8ihMTqVBnoKSFRZK9vM9PjNha7PyIC5ak160ASReOv fk+w3TyFWwBR4r808176CtJ7yOTn75xB6+sZzT/YFXdA3YAVduqTmF18EI49Mgrvn7Jd HDPNbDVYoWASAMyC7iCn0R8CA2mCGqfTmgzSdaWckzmRprXVp3+iyFsxO7EVP3io+99u 9TNw==
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=m9jTSFC2u1FVaLE+UtzO3QKSK1cwjZv+QW7ATAPiWlA=; b=X+QaM1fNdOoKJ5thecGSAWyFkB3BSDID0wza+vC2lTRKmQYsH/IdYwaXOJtE/wzATW uhx5dNhATkKsJm79IcyzQRUX5gH+AhvxsTS+4z+e8rmRG84t10f+X3pWsKKymocCjjH5 C3rmBxwFF/eKcm06p2ErBVbSPtsrhzHYgBOw3GID60WK12sq7TD0llM19CJMcrh+47Mr ZM1UcOjwu65T931jgknx53DkrbR64T+HJRURHsxcgIoiInWRvuXE+l+HcrdmGcSNguRb IAHP/xQ8yghF1iJCL0qkhbWkapy3UlOZkr4p51IiXj3972F44c52d+c+IT0ZGnqtYK6X 2egg==
X-Gm-Message-State: APjAAAXEmm0KA8N2pStIKuqjamr9aL9Komd6bxfJT5r3I7wBWG3PCNms T/NC8uuVveuuCvqCzhGAUK7EjQ==
X-Google-Smtp-Source: APXvYqyQXFM1Dh1ztxxjn05Knpp34kk2vbuRh7csfpgBzj1oHziTmkSqFBgUI9DpgJkuzJNc9CRUaw==
X-Received: by 2002:ac8:23d3:: with SMTP id r19mr9799815qtr.297.1574353549637;  Thu, 21 Nov 2019 08:25:49 -0800 (PST)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id h37sm1791998qth.78.2019.11.21.08.25.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 21 Nov 2019 08:25:48 -0800 (PST)
Date: Thu, 21 Nov 2019 11:25:47 -0500
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Bence =?iso-8859-1?Q?B=E9ky?= <bnc@chromium.org>
Cc: Jiuhai Zhang <jiuhai.zhang@gmail.com>, quic@ietf.org, 78690842@qq.com
Subject: Re: Questions about QPACK
Message-ID: <20191121162545.GB27974@ubuntu-dmitri>
Mail-Followup-To: Bence =?iso-8859-1?Q?B=E9ky?= <bnc@chromium.org>, Jiuhai Zhang <jiuhai.zhang@gmail.com>, quic@ietf.org, 78690842@qq.com
References: <CAG9+TpYtZniZ63xc3Wpb7NNpkVyj1G9_p-rtCjspdCr+oz8edg@mail.gmail.com> <CACMu3tq6q+UDyyUqQHC_VK0gxGSnBj_=1DsnmRMHPChgawL0tw@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <CACMu3tq6q+UDyyUqQHC_VK0gxGSnBj_=1DsnmRMHPChgawL0tw@mail.gmail.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/stc1zU7qnFL-tpdhoiVnuAL62K4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 21 Nov 2019 16:25:52 -0000

On Thu, Nov 21, 2019 at 09:57:24AM -0500, Bence Béky wrote:
> > Q1:why we send N bit to peer? it seems we don't need to send the
> > bit, if sender don't want to put in dynamic table.
> 
> QPACK is hop-to-hop, that is, client to intermediary, intermediary to
> intermediary, intermediary to server, all separately (and the other
> way around).  Intermediary can be locally installed
> firewall/antivirus, proxy, reverse proxy, load balancer etc.
> Intermediaries are allowed to recompress headers using different
> algorithms using QPACK, or they might relay to an HTTP/2 connection
> using HPACK, etc.  The N bit is to inform intermediaries whether the
> original sender of the headers deems that the header MUST always be
> encoded using literals.

The HPACK RFC has a whole subsection [1] dedicated to the never-indexed
literals.  The QPACK draft refers to (and subsumes?) [2] the HPACK's
security considerations.

  - Dmitri.

1. https://tools.ietf.org/html/rfc7541#section-7.1.3
2. https://tools.ietf.org/html/draft-ietf-quic-qpack-11#section-7


From nobody Thu Nov 21 19:07:59 2019
Return-Path: <frodeki@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 68570120836 for <quic@ietfa.amsl.com>; Thu, 21 Nov 2019 19:07:57 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 Bo03NBw7xvq5 for <quic@ietfa.amsl.com>; Thu, 21 Nov 2019 19:07:55 -0800 (PST)
Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) (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 7F1F412018B for <quic@ietf.org>; Thu, 21 Nov 2019 19:07:55 -0800 (PST)
Received: by mail-pf1-x431.google.com with SMTP id z4so2746257pfn.12 for <quic@ietf.org>; Thu, 21 Nov 2019 19:07:55 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-transfer-encoding:content-language; bh=IsA+/DpLX/8nB5tgtRdiOmuSAeh4022ezydhXZpiUJM=; b=Wn4XcN7BwF9kF91vdaT18jgiJ6n68fvE+Seghtr52SbcGLEn5RiNldlFQRmYDVHki9 dkgGU+2kqMDO+Btd8nbfFBEBlFF2W6wvXBGuvnfinqzfZOVWk9SWmQPCsfC4rA0wQ8MB YfYe2X3M5QMRhHcMEhSv7eEvXZJVI05TsQOP8U58V+FLlifID3rRv9o8EAp+1PAGII8B vpIjdH+UYRm7ed4vnrWRAJ+Lsi7eCBkBgNAllSLrUumX/QAk5Ls/aZoJHbdkVNgo3jWG +iw9OJ4ejy6U0GsVaVBWR9iamC4STucLXAUSCdl4evt5O+Wczb40zzqpweLcL3rqdhhH 5x7Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-transfer-encoding :content-language; bh=IsA+/DpLX/8nB5tgtRdiOmuSAeh4022ezydhXZpiUJM=; b=VhXj+Rdkb2YNd/QX5da7fxZxtyHbGT46NQMmcd3akQmUKZ41DdEGprxLd9VL5xQkXQ bagZogw8W9/xx8Qws8yrQOJlvPkBV4NYzdsqZZWEPe7i1+FYMjTw63uJwuEtIqsWXW/M cde8V+rSIC/lR3qWnNLF39DKLUzSY5thR+Ssky9WdNWgpkd7fbRnHe/uHdgzbX3v/X09 Fv6e/+F3Y8qgZs9P+4qGW7TNd31Vhtvcsu7JqOulsucQsqXdNNITp7Q6UoWZs/eQstOq fpNM7CR9WLh8mP3ipYqNcnFSuVvI61cKqnB6przX7EEMJz77FSFDRZeWesv17ju3BOWC rL3Q==
X-Gm-Message-State: APjAAAWUcM0M0sC09ElBrlLf88OD4/On59zIT+FlKmFeJTBcobnTUioo gQD+7pE6bvns8duIC/eiNI0Ws1Tr
X-Google-Smtp-Source: APXvYqwMu7DcoUWXEGFUEO7QJCAsSBWhRW1ThRdVJKTA0gCrNbW0IJZGW0FrvPtmGVr2eurZXVXn3Q==
X-Received: by 2002:a63:cf4f:: with SMTP id b15mr13311905pgj.216.1574392074889;  Thu, 21 Nov 2019 19:07:54 -0800 (PST)
Received: from ?IPv6:2001:67c:370:128:deb:727b:9d2c:94c1? ([2001:67c:370:128:deb:727b:9d2c:94c1]) by smtp.googlemail.com with ESMTPSA id e59sm877274pjk.28.2019.11.21.19.07.53 for <quic@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Thu, 21 Nov 2019 19:07:54 -0800 (PST)
Subject: Re: What CSRs Do
To: quic@ietf.org
References: <BL0PR11MB3394D769128DEFEEFBC3CA71904C0@BL0PR11MB3394.namprd11.prod.outlook.com> <0cf4d3ad-0f64-0ae4-2d95-77a39f40639d@tele.no> <20191119042904.GC5602@1wt.eu> <4003626d-8966-6772-7df0-e76549320430@gmail.com> <1574144751435.15844@akamai.com> <bc0cf83f-16d6-3200-5d6e-091311ccf9a7@tele.no> <7268_1574344734_5DD6981E_7268_134_1_1574344750.3872.4.camel@orange.com>
From: Frode Kileng <frodeki@gmail.com>
Message-ID: <ff683bc6-6b10-8720-8e18-b448bb0dfd21@gmail.com>
Date: Fri, 22 Nov 2019 04:07:46 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.2.2
MIME-Version: 1.0
In-Reply-To: <7268_1574344734_5DD6981E_7268_134_1_1574344750.3872.4.camel@orange.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/vR4mO7YtIk6U-ByYginNEEDUyp8>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 22 Nov 2019 03:07:57 -0000

On 21/11/2019 14:59, alexandre.ferrieux@orange.com wrote:
> To *lack* these sources, one might be incompetent, as you are
> suggesting many people are. Alternatively, one might simply care about
> a long end-to-end path with several responsibility boundaries, which by
> definition are opaque. In this case, as Igor said, the
> upstream/downstream location is absolutely crucial.


When in https://github.com/quicwg/base-drafts/issues/3189 stating that 
"Shipping v1 without loss observation support would undermine day-to-day 
network maintenance work in at least that part of the ecosystem", naming 
a list of "supporters" and "The list is growing daily", I do think in 
all fairness it is important to indicate that this view is not 
necessarily an universal truth and a view is supported by everyone in 
"this part of the ecosystem". And that it should be possible to indicate 
this, giving a rationale and without being accused for claiming someone 
is "incompetent".

frodek


From nobody Thu Nov 21 20:03:12 2019
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 BAEB4120025 for <quic@ietfa.amsl.com>; Thu, 21 Nov 2019 20:03:06 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level: 
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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=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 Dx79Ii3rPm5E for <quic@ietfa.amsl.com>; Thu, 21 Nov 2019 20:03:05 -0800 (PST)
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 3887D12008C for <quic@ietf.org>; Thu, 21 Nov 2019 20:03:05 -0800 (PST)
Received: from pps.filterd (m0050093.ppops.net [127.0.0.1]) by m0050093.ppops.net-00190b01. (8.16.0.42/8.16.0.42) with SMTP id xAM402uN022733; Fri, 22 Nov 2019 04:03:04 GMT
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=akamai.com; h=from : to : subject : date : message-id : references : in-reply-to : content-type : content-transfer-encoding : mime-version; s=jan2016.eng; bh=gR1j6HgiuVGkKPl9XFiQDoHgpbxzMTxPbWgf0PlmQ5o=; b=YFCWfCRAcjN4rb0L7m5YNz3j6JbCuRiya5xE39qE0KdbNKrhVcNhF6xW2yXjLtodnIuL iEgRBhe+XyqmMPT8f/+o+1fM8HgQlwITxNlsQoC8PJFWlJD4rGmfplvVSWtpW1s1Om8M opI2F9cYWNBLlG9lrP7fO7fKAZh4R98mjQ7oY0ZDhEosEy0oXCATvmgxAY70vFoPlaug Dm0QXNW1JoCsyu9cirj5HZm3YiV/IrR1+MVQejj0ifSfscs2uQEN0qcX+2R32skqESPR YU7ED55zFjOztGJy0cj/2LV9riMS77ep/rG9wFA1TPIv5M5KFV50H2Hd/9NJrrCSImP8 Yw== 
Received: from prod-mail-ppoint7 (prod-mail-ppoint7.akamai.com [96.6.114.121] (may be forged)) by m0050093.ppops.net-00190b01. with ESMTP id 2we3gh94p4-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Fri, 22 Nov 2019 04:03:04 +0000
Received: from pps.filterd (prod-mail-ppoint7.akamai.com [127.0.0.1]) by prod-mail-ppoint7.akamai.com (8.16.0.27/8.16.0.27) with SMTP id xAM42WE6015219; Thu, 21 Nov 2019 23:03:02 -0500
Received: from email.msg.corp.akamai.com ([172.27.165.116]) by prod-mail-ppoint7.akamai.com with ESMTP id 2wadb56fmu-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=NOT); Thu, 21 Nov 2019 23:02:53 -0500
Received: from USTX2EX-DAG1MB5.msg.corp.akamai.com (172.27.165.123) by ustx2ex-dag1mb3.msg.corp.akamai.com (172.27.165.121) with Microsoft SMTP Server (TLS) id 15.0.1473.3; Thu, 21 Nov 2019 22:02:38 -0600
Received: from USTX2EX-DAG1MB5.msg.corp.akamai.com ([172.27.165.123]) by ustx2ex-dag1mb5.msg.corp.akamai.com ([172.27.165.123]) with mapi id 15.00.1473.005; Thu, 21 Nov 2019 22:02:38 -0600
From: "Lubashev, Igor" <ilubashe@akamai.com>
To: Frode Kileng <frodeki@gmail.com>, "quic@ietf.org" <quic@ietf.org>
Subject: RE: What CSRs Do
Thread-Topic: What CSRs Do
Thread-Index: AdWeiLnP74voAASmTy29ATmkahTsZQANieYAAAFSQgAAAxM6gP//nbXWgABu3gCAA57FAIAA3FUAgABaDtA=
Date: Fri, 22 Nov 2019 04:02:37 +0000
Message-ID: <4aaf3c3ddd4344928a37922cdc0c3667@ustx2ex-dag1mb5.msg.corp.akamai.com>
References: <BL0PR11MB3394D769128DEFEEFBC3CA71904C0@BL0PR11MB3394.namprd11.prod.outlook.com> <0cf4d3ad-0f64-0ae4-2d95-77a39f40639d@tele.no> <20191119042904.GC5602@1wt.eu> <4003626d-8966-6772-7df0-e76549320430@gmail.com> <1574144751435.15844@akamai.com> <bc0cf83f-16d6-3200-5d6e-091311ccf9a7@tele.no> <7268_1574344734_5DD6981E_7268_134_1_1574344750.3872.4.camel@orange.com> <ff683bc6-6b10-8720-8e18-b448bb0dfd21@gmail.com>
In-Reply-To: <ff683bc6-6b10-8720-8e18-b448bb0dfd21@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.217.165]
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=2019-11-21_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=999 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1911140001 definitions=main-1911220035
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-11-21_07:2019-11-21,2019-11-21 signatures=0
X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 impostorscore=0 malwarescore=0 adultscore=0 mlxscore=0 bulkscore=0 clxscore=1015 mlxlogscore=999 suspectscore=0 phishscore=0 spamscore=0 priorityscore=1501 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1911220034
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/y5tPkCJeJJplwm9CbUKU9hFNu08>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 22 Nov 2019 04:03:07 -0000

RnJvZGUsIEFsZXgsDQoNClRoZSB1bmhlbHBmdWwgZGlzY3Vzc2lvbiBvZiB0b25lIG9yIHdvcmQg
Y2hvaWNlIGFzaWRlLCBJIHRoaW5rIHRoYXQgYm90aCBvZiB5b3UgbWFrZSB2YWxpZCBwb2ludHMu
ICBJJ3ZlIGhlYXJkIHNpbWlsYXIgdmlld3Mgb24gYm90aCBzaWRlcyBmcm9tIG11bHRpcGxlIHBl
b3BsZS4NCg0KSSB3b3VsZCByZXBlYXQgd2hhdCBJIHNhaWQgeWVzdGVyZGF5IGluIE1PUFMuICBR
VUlDIGhlYWRlciBlbmNyeXB0aW9uIGlzIGEgc2lnbmlmaWNhbnQgY2hhbmdlIGluIHRoZSB3YXkg
dHJhbnNwb3J0IHdvcmtzLCBhbmQgd2UgaGF2ZSBubyBleHBlcmllbmNlIG9wZXJhdGluZyBpdCBh
dCBhIHNjYWxlIHdoZXJlIGl0IGlzIG1vcmUgdGhhbiBhIHNpbmdsZS1kaWdpdCBwZXJjZW50YWdl
IG9mIEludGVybmV0IHRyYWZmaWMuICBTb21lIHBlb3BsZSBiZWxpZXZlIHRoYXQgdGhleSBuZWVk
IG5ldyB0b29sczsgb3RoZXJzIGJlbGlldmUgdGhhdCB0aGV5IGRvIG5vdC4gIEEgbG90IG9mIGVm
Zm9ydCB3ZW50IGludG8gUVVJQyB0byBlbnN1cmUgaXQgd2lsbCBjb250aW51ZSB0byBldm9sdmUu
ICBTbyB0aGUgYmVzdCB0aGluZyB3ZSBjYW4gZG8gaXMgdG8gZ2l2ZSB0aGUgdG9vbCB0byBwZW9w
bGUgd2hvIGNsYWltIHRoZXkgbmVlZCBpdCBhbmQgc2VlIGlmIGl0IGdldHMgdXNlZC4gIElmIHRo
ZSB0b29scyByZW1haW5zIGxhcmdlbHkgdW51c2VkLCBpdCB3aWxsIG5hdHVyYWxseSBkaXNhcHBl
YXIgZnJvbSBRVUlDIChpdCB3aWxsIGJlIGEgbmVnb3RpYXRlZCBleHRlbnNpb24gYWZ0ZXIgYWxs
ISkuIA0KDQotIElnb3INCg0KPiBGcm9tOiBGcm9kZSBLaWxlbmcgPGZyb2Rla2lAZ21haWwuY29t
Pg0KPiANCj4gT24gMjEvMTEvMjAxOSAxNDo1OSwgYWxleGFuZHJlLmZlcnJpZXV4QG9yYW5nZS5j
b20gd3JvdGU6DQo+ID4gVG8gKmxhY2sqIHRoZXNlIHNvdXJjZXMsIG9uZSBtaWdodCBiZSBpbmNv
bXBldGVudCwgYXMgeW91IGFyZQ0KPiA+IHN1Z2dlc3RpbmcgbWFueSBwZW9wbGUgYXJlLiBBbHRl
cm5hdGl2ZWx5LCBvbmUgbWlnaHQgc2ltcGx5IGNhcmUgYWJvdXQNCj4gPiBhIGxvbmcgZW5kLXRv
LWVuZCBwYXRoIHdpdGggc2V2ZXJhbCByZXNwb25zaWJpbGl0eSBib3VuZGFyaWVzLCB3aGljaA0K
PiA+IGJ5IGRlZmluaXRpb24gYXJlIG9wYXF1ZS4gSW4gdGhpcyBjYXNlLCBhcyBJZ29yIHNhaWQs
IHRoZQ0KPiA+IHVwc3RyZWFtL2Rvd25zdHJlYW0gbG9jYXRpb24gaXMgYWJzb2x1dGVseSBjcnVj
aWFsLg0KPiANCj4gDQo+IFdoZW4gaW4gaHR0cHM6Ly9naXRodWIuY29tL3F1aWN3Zy9iYXNlLWRy
YWZ0cy9pc3N1ZXMvMzE4OSBzdGF0aW5nIHRoYXQNCj4gIlNoaXBwaW5nIHYxIHdpdGhvdXQgbG9z
cyBvYnNlcnZhdGlvbiBzdXBwb3J0IHdvdWxkIHVuZGVybWluZSBkYXktdG8tZGF5DQo+IG5ldHdv
cmsgbWFpbnRlbmFuY2Ugd29yayBpbiBhdCBsZWFzdCB0aGF0IHBhcnQgb2YgdGhlIGVjb3N5c3Rl
bSIsIG5hbWluZyBhDQo+IGxpc3Qgb2YgInN1cHBvcnRlcnMiIGFuZCAiVGhlIGxpc3QgaXMgZ3Jv
d2luZyBkYWlseSIsIEkgZG8gdGhpbmsgaW4gYWxsIGZhaXJuZXNzIGl0IGlzDQo+IGltcG9ydGFu
dCB0byBpbmRpY2F0ZSB0aGF0IHRoaXMgdmlldyBpcyBub3QgbmVjZXNzYXJpbHkgYW4gdW5pdmVy
c2FsIHRydXRoIGFuZCBhDQo+IHZpZXcgaXMgc3VwcG9ydGVkIGJ5IGV2ZXJ5b25lIGluICJ0aGlz
IHBhcnQgb2YgdGhlIGVjb3N5c3RlbSIuIEFuZCB0aGF0IGl0DQo+IHNob3VsZCBiZSBwb3NzaWJs
ZSB0byBpbmRpY2F0ZSB0aGlzLCBnaXZpbmcgYSByYXRpb25hbGUgYW5kIHdpdGhvdXQgYmVpbmcN
Cj4gYWNjdXNlZCBmb3IgY2xhaW1pbmcgc29tZW9uZSBpcyAiaW5jb21wZXRlbnQiLg0KPiANCj4g
ZnJvZGVrDQoNCg==


From nobody Fri Nov 22 10:51:28 2019
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 388A01208D2 for <quic@ietfa.amsl.com>; Fri, 22 Nov 2019 10:51:27 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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=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 uQ9W-oF3DOcB for <quic@ietfa.amsl.com>; Fri, 22 Nov 2019 10:51:25 -0800 (PST)
Received: from mail-qt1-x835.google.com (mail-qt1-x835.google.com [IPv6:2607:f8b0:4864:20::835]) (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 231341208A1 for <quic@ietf.org>; Fri, 22 Nov 2019 10:51:25 -0800 (PST)
Received: by mail-qt1-x835.google.com with SMTP id r20so8891830qtp.13 for <quic@ietf.org>; Fri, 22 Nov 2019 10:51:25 -0800 (PST)
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=WSFO0IylimsSSJNuWpX3HIUjKhukUTvDoWHR1NmBr2E=; b=FfPe4lyqporWjirBoAuLRdUTAst6DYkAYDYlNHBoqFcBH0k5M0ifjAxQQ8CpNO9D+U MQnLKxPNUC/zXXO4FCVNr7fOZJbsfZYJpuSvzvcw8Nv9r4hvdMMO/7OMN0aOvU4s+aYw 34F9b86g66d1wq1iNINz6bJmwMiizh+AMrZj/g5+4KGGbhuU8wCyBkCM+7h6NE5mU6Zi vmXmUTdZYUy1Wuw632QdChUnN3f0D4gDiquaOTVo2UbvbIR/+W/vznUK91CP3Z5jfxDZ LwiBOt7IVkcXll392pMBYeUUoLAAmRZnzsNiUSDKUv6rsSt0+Svu8daILnaeEoc6quTE B+Qw==
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=WSFO0IylimsSSJNuWpX3HIUjKhukUTvDoWHR1NmBr2E=; b=HmqNJ3BKXEwWe+isKIBZC79s/0ymTR3zoStEK7E6iDuv1E+SYvwTeVgOPbaNPmH58z cLxrueWbTD7+cIuCu1ynKSSzjKlu9cXrmNERwWxPMYFQSUtrFYcv/KQV/r2+fQgU2/BZ k08TBXGX8CSRaTsZ7hVGd/cvtG5hX48d8fsIkGzme2vsou0NxgtBx6JkbIuAGS15gYsK Vf7kvP5gkTJWwHdr7JQXeaMmuvlsfQys/q2brZDr0/uGrL2ZELzhiHkRZ7jdBmjtYiM+ 6nvTAK+9lcZ7nxy1wqOjbONJJNLesVHcdu65e8RpkyxK6vMRYsftboS3XgEeHMIYuR79 AYwg==
X-Gm-Message-State: APjAAAWpKnksISIOxeOhamX1KPJmwSqc2IFhst01/1PPRsqm15ULZbPR zc2HeWuX37j/4Sz5C4VCxKL3zQ==
X-Google-Smtp-Source: APXvYqw88EyA+evCZsB2b/d6o50CNZ4LT+f9uBeec87gtSTSthKMmhmee6gcKCbsQY0L8Kvs+Za3UQ==
X-Received: by 2002:ac8:5412:: with SMTP id b18mr16153629qtq.34.1574448684218;  Fri, 22 Nov 2019 10:51:24 -0800 (PST)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id w12sm3449951qka.130.2019.11.22.10.51.23 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Nov 2019 10:51:23 -0800 (PST)
Date: Fri, 22 Nov 2019 13:51:19 -0500
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: =?utf-8?B?5ryC5rOK55qE5qKm?= <78690842@qq.com>
Cc: Bence =?iso-8859-1?B?Qulr?= <bnc@chromium.org>, Jiuhai Zhang <jiuhai.zhang@gmail.com>, quic <quic@ietf.org>
Subject: Re: Questions about QPACK
Message-ID: <20191122185118.GA26949@ubuntu-dmitri>
Mail-Followup-To: =?utf-8?B?5ryC5rOK55qE5qKm?= <78690842@qq.com>, Bence =?iso-8859-1?B?Qulr?= <bnc@chromium.org>, Jiuhai Zhang <jiuhai.zhang@gmail.com>, quic <quic@ietf.org>
References: <CAG9+TpYtZniZ63xc3Wpb7NNpkVyj1G9_p-rtCjspdCr+oz8edg@mail.gmail.com> <CACMu3tq6q+UDyyUqQHC_VK0gxGSnBj_=1DsnmRMHPChgawL0tw@mail.gmail.com> <20191121162545.GB27974@ubuntu-dmitri> <tencent_DB09B2AF02DB80EEDA41023F6A968A1E3509@qq.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <tencent_DB09B2AF02DB80EEDA41023F6A968A1E3509@qq.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/YK4ix5nUYQlGS8ukQUsnX-QqHJo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 22 Nov 2019 18:51:27 -0000

On Sat, Nov 23, 2019 at 01:23:41AM +0800, æ¼‚æ³Šçš„æ¢¦ wrote:
> Thanks for your reply. There is some misunderstanding about Q2.

To quote Q2 from the original email:

>> https://tools.ietf.org/html/draft-ietf-quic-qpack-11#section-4.5.4
>> 
>>         0   1   2   3   4   5   6   7
>>       +---+---+---+---+---+---+---+---+
>>       | 0 | 1 | N | T |Name Index (4+)|
>>       +---+---+---+---+---------------+
>>       | H |     Value Length (7+)     |
>>       +---+---------------------------+
>>       |  Value String (Length bytes)  |
>>       +-------------------------------+
>> 
>> Q2:when we encode new name, new value, we should insert name,value
>> pair into dynamic table, should we insert name only into dynamic
>> table?

The answer to "should" is "depends on what you want to do."  (See below).

> The background is that when the sender inserts the pair of name &amp;
> value into dynamic table, it should also send the pair of name &amp;
> value and index to recipient through encoder stream.&nbsp; In case
> that the pair of name &amp; value cannot be found, we can search by
> name only.&nbsp; The question is that in order to search by name only,
> can we&nbsp;insert name only (without value or with 0-length value)
> and index into the dynamic table, and then send the name and index to
> recipient through encoder stream?  If we don't insert name only and
> index into the dynamic table, how can we search by name only?

Yes, it is valid to insert into the dynamic table an entry with 0-length.
This is useful when the header name repeats, but the value does not.  In
that case, you can reference the dynamic table from the header block via
the Literal Header Field With Name Reference instruction (listed in the
original Q2 above).

  - Dmitri.


From nobody Fri Nov 22 10:52:16 2019
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 24C481208B2 for <quic@ietfa.amsl.com>; Fri, 22 Nov 2019 10:52:15 -0800 (PST)
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, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 8aIsf3nA9D_h for <quic@ietfa.amsl.com>; Fri, 22 Nov 2019 10:52:14 -0800 (PST)
Received: from mail-qv1-xf36.google.com (mail-qv1-xf36.google.com [IPv6:2607:f8b0:4864:20::f36]) (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 E40001208A1 for <quic@ietf.org>; Fri, 22 Nov 2019 10:52:13 -0800 (PST)
Received: by mail-qv1-xf36.google.com with SMTP id g18so3297460qvp.8 for <quic@ietf.org>; Fri, 22 Nov 2019 10:52:13 -0800 (PST)
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:references :mime-version:content-disposition:in-reply-to:user-agent; bh=JAQidrqF73T2mIYGEo2Md1KnoxYg/m+d2+XawAljOhA=; b=PLUKkIlGvGp2byTV2NYGtmjRSmv4AKBpcnKD/GYUkRyUtRreIZO6xFCn8UoYqnpSRR h2JFNSLDEuftPvDO6fGwDvNRvcq2bZtKIaVdH47MbCUqM3H2CHS1o26O5nbvKrQhgZPr 5zNth58uMc5eUtSwgWEdbL8DqpYMTgFQOg8bFzDPYs2cotD4sMjXiIJVsdFfRyAsp5gX +xawNnwX9H3FpHlPhVNc2x2PBENgbVGmebAEDarrc1hXmrOjjMjRGvvDJKokap6yrVjY wAJ6gQDRVFwBx9TS3tK/HM6Ei+Cv90BBfns40DYd8fpiMhlrsnDLpwxJEBkNKPJcutk8 xOfg==
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 :references:mime-version:content-disposition:in-reply-to:user-agent; bh=JAQidrqF73T2mIYGEo2Md1KnoxYg/m+d2+XawAljOhA=; b=OxHNA++lOmOAVJx+a/WzlBTSP5iAxw51yTB/e0hoqnbBfWLBLBtFis1SDR8m9z/3b3 y7qw6Cy0qdBeL/rN+0VFWL8ZQQkvMIvoIYEaDjAp0Y9d2g8D5j5FPEuDSdP87BTfCLh4 tlsDeULuPj5HDbl+13sgOtSs+66IpzXPz3uG3iuhyoVO/xSQMZf3RWiv3vCVWZa/O09D gLgIlwjv//qLqpdevOP9b6vjYDci5ImM8OnwZ7D9kvpaHgMiXQxV+dXZ1lHvi6cSQJ8w zkPB8e+OVoyFpKHdMaajDZbwa9Ap2QA1CiXtWXTK7SzQc46FCtaelTS89HrRjxH5Zf5H 1TCg==
X-Gm-Message-State: APjAAAVWmfnZNknoV1rBP3mbOIv0juoxEsKHARJUB7DX3cEmzOyovNHp seo8xfZKBRVetYizRf6b2NRcog==
X-Google-Smtp-Source: APXvYqzKbfTGtn8K44gRBNXkx8Z0b6RVUfQogrxx9zE6561IGbKTCvQYRMzd4knYnxiVieRKMjsj/w==
X-Received: by 2002:ad4:5441:: with SMTP id h1mr962321qvt.120.1574448733034; Fri, 22 Nov 2019 10:52:13 -0800 (PST)
Received: from ubuntu-dmitri (ool-2f1636b6.static.optonline.net. [47.22.54.182]) by smtp.gmail.com with ESMTPSA id q20sm3823986qtp.41.2019.11.22.10.52.12 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 22 Nov 2019 10:52:12 -0800 (PST)
Date: Fri, 22 Nov 2019 13:52:10 -0500
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: =?utf-8?B?5ryC5rOK55qE5qKm?= <78690842@qq.com>, Bence =?iso-8859-1?B?Qulr?= <bnc@chromium.org>, Jiuhai Zhang <jiuhai.zhang@gmail.com>, quic <quic@ietf.org>
Subject: Re: Questions about QPACK
Message-ID: <20191122185209.GB26949@ubuntu-dmitri>
Mail-Followup-To: =?utf-8?B?5ryC5rOK55qE5qKm?= <78690842@qq.com>, Bence =?iso-8859-1?B?Qulr?= <bnc@chromium.org>, Jiuhai Zhang <jiuhai.zhang@gmail.com>, quic <quic@ietf.org>
References: <CAG9+TpYtZniZ63xc3Wpb7NNpkVyj1G9_p-rtCjspdCr+oz8edg@mail.gmail.com> <CACMu3tq6q+UDyyUqQHC_VK0gxGSnBj_=1DsnmRMHPChgawL0tw@mail.gmail.com> <20191121162545.GB27974@ubuntu-dmitri> <tencent_DB09B2AF02DB80EEDA41023F6A968A1E3509@qq.com> <20191122185118.GA26949@ubuntu-dmitri>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20191122185118.GA26949@ubuntu-dmitri>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/p8O5HrKrHGExejBxu_DG46PsdUI>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 22 Nov 2019 18:52:15 -0000

On Fri, Nov 22, 2019 at 01:51:18PM -0500, Dmitri Tikhonov wrote:
> Yes, it is valid to insert into the dynamic table an entry with 0-length.

It should read "with 0-length value."

  - Dmitri.


From nobody Sat Nov 23 02:52:41 2019
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 80F8112011E for <quic@ietfa.amsl.com>; Sat, 23 Nov 2019 02:52:39 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.997
X-Spam-Level: 
X-Spam-Status: No, score=-0.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, FREEMAIL_REPLY=1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 rqFXRQtweJPC for <quic@ietfa.amsl.com>; Sat, 23 Nov 2019 02:52:38 -0800 (PST)
Received: from mail-ed1-x533.google.com (mail-ed1-x533.google.com [IPv6:2a00:1450:4864:20::533]) (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 A691A120106 for <quic@ietf.org>; Sat, 23 Nov 2019 02:52:37 -0800 (PST)
Received: by mail-ed1-x533.google.com with SMTP id a21so8222604edj.8 for <quic@ietf.org>; Sat, 23 Nov 2019 02:52:37 -0800 (PST)
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=TO5gZG6dZC44uYURMcL845Y3eQI10cTo7+JWGPm7cC0=; b=EBIEDeeC41FTD/WC67a1w7sxj+brDwHoqJ7RrT0766+83y5F/qRWdwuxdiCZevvP5I JDzTO55T42bqisi7wHdCifznB2V0zMYPTYeQvCpMGn+9r4g7bBF4Fy2/MjrrmAtSb/j8 eCQxxiruxHerm+Qf4ep4q8cZ6+RJfaGSXVt6XjlYdtHN0hshp+zmjP50wTdXYKlT4Ke7 nNqc3q5jVPlQstTVlYn0myG2qOulfTtCBXepSIsbDdzsF3C9STO8Ol2kyikJI37cv/uV G2tThmvOv98Ngt8rz+7UCfzIB+w+qRVM4h09lAh/yx26UMb/cukk1z4mEdONsEMPLFPS CfVA==
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=TO5gZG6dZC44uYURMcL845Y3eQI10cTo7+JWGPm7cC0=; b=pLm4PFhiXk+FPISCVTjYNE2A0UvP3ZgtP9wgUQwEr6CG3qcHKmkO+oxCUr1OCeqguv qB22lhSuaxfLW6WVjcuhwAQ7ASjVkoriEt0YVqTMzL9HS5xY2mKJE81cBW/PUuIhnCTT 4odwiEtJA4oDB09HlNmnbwgxKofAXO5W/WlIikmNKUqLl0ITsOjO8+bWHL8ZvBtYdTg1 wgU+a/5K7HGC2eHgWGOyYKUszwFZYJa/VY88syAE9MftZdCP9gsm6p3MYW6qObTj+LUF 2rxLtggSXBJ2OwJOeaTiyynppOo2n7xWe8KX0Vu7xQq3fDsLHnmLdnCtKkf9/4rPvWRz 2UZA==
X-Gm-Message-State: APjAAAV89Bja/c1EXHA/0XzCZAj7AmtuAeyOr7B63nmrFKwABK4QRw69 uhE+BNuiUPpRY9gjUi2T2eChlVA5me0JHWBfOB0=
X-Google-Smtp-Source: APXvYqwtaA7HGE3kqT9bH8L+Hqfm9vVV6WjEeO/zeJABQGLiwJTsw0mfxTllzSnyeyc2jQ1JKEnb/UFo91kbhBdnsNg=
X-Received: by 2002:a17:906:1b41:: with SMTP id p1mr26502471ejg.65.1574506355957;  Sat, 23 Nov 2019 02:52:35 -0800 (PST)
Received: from 1058052472880 named unknown by gmailapi.google.com with HTTPREST; Sat, 23 Nov 2019 05:52:35 -0500
From: =?UTF-8?Q?Mikkel_Fahn=C3=B8e_J=C3=B8rgensen?= <mikkelfj@gmail.com>
In-Reply-To: <CALGR9obRoQ56Jcf_UMW0qiHgGmeRt1y8+8A_8T55XrtgUsWR1g@mail.gmail.com>
References: <157425081947.30550.7403247942771684795.idtracker@ietfa.amsl.com> <CANatvzyk6xaDby-VVvtuOJ66=YPMqynB9=WMAMxYPxGXYa=BPA@mail.gmail.com> <CAN1APddw53xtus9Z86H4rw2CRXA3MR+fxhLWPf3Bh_=qB-O7Aw@mail.gmail.com> <CALGR9obRoQ56Jcf_UMW0qiHgGmeRt1y8+8A_8T55XrtgUsWR1g@mail.gmail.com>
MIME-Version: 1.0
Date: Sat, 23 Nov 2019 05:52:35 -0500
Message-ID: <CAN1APdcPf3EZDRyhVFJdUK9o5UtZYbzMWfJM_MAbhgZh=U2L1Q@mail.gmail.com>
Subject: Re: Priorities I-D for Thursday HTTPbis meeting (Fwd: New Version Notification for draft-kazuho-httpbis-priority-04.txt)
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: QUIC WG <quic@ietf.org>, Kazuho Oku <kazuhooku@gmail.com>,  HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="0000000000000b275d059801544a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/HjZ47szyAyYp8J66xM3fR4HkpKo>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 23 Nov 2019 10:52:39 -0000

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

comments inline

On 20 November 2019 at 20.18.46, Lucas Pardue (lucaspardue.24.7@gmail.com)
wrote:

Hi Mikkel,

To comment as a co-author but speaking only for myself:

On Wed, 20 Nov 2019, 20:57 Mikkel Fahn=C3=B8e J=C3=B8rgensen, <mikkelfj@gma=
il.com>
wrote:

> Looking forward to digging further into this.
> ...
>

>
> After reading 1/3 of document, I still have no clue how the priority
> scheme works (except I have some guess based on earlier ideas that have
> floatet) and I have had to deal with a lot of HTTP/2 legacy that I am not
> necessarily interested in. HTTP/3 doc has also move away from implicit
> HTTP/2 familiarity, at least last time I checked.
>

To reinterpret you point, I think that the concepts of urgency and
precedence would benefit from better description (issues #31[1] and
#32[2]). But I also wonder if you are saying that there is too much or too
little HTTP/2 specific/related content? Or am I missing out on your point
here?

Yes, I think an overview of the mechanism is needed. This email was up to
section 3.

On HTTP/2 I think it is warranted with a good explanation. I don=E2=80=99t =
think
more is necessary, and perhaps there is enough, but it is placed too early,
forcing focus on things that may not be material to the reader and confuses
grasping the core concepts.

Reading further, I don=E2=80=99t bother to comment, but a general observati=
on was
the each section raised questions that were answered in later sections -
it=E2=80=99s hard to address all at once, but worth keeping in mind. A mino=
r thing
is the inline graphics which intuitively, to me, means hex encoded SVG og
PNG, but that is not what is meant, and at the very end that becomes clear.
A larger issues are why servers send priorities in the first place (it is
eventually explained).





> The document talks about intermediate hop reprioritisation without making
> clear what that is or what purpose it serves. I can only assume load
> balancers and reverse proxies. From a QUIC background that also leaves me
> wondering what that means - since each hop is necessarily also end to end=
,
> unless there is an extension wrapper frame, but that makes no sense.
>

The intent is to address the HTTP semantic layer but dip into HTTP
version-specifics where necessary. We rely on readers being familiar with
HTTP semantic concepts and terminology but can probably do a better job of
referencing. Since QUIC has no concept of priority, but the serialisation
of HTTP does and is ultimately coupled to the transport layer, it can be a
bit tricky to pick the subject. Happy to take some suggestions on specific
ways to improve here

Intermediates are explained when reading all the way to the end, but it is
an example of confusion that arises while reading through the document. On
HTTP version neutrality I think that is fine, but it would help to be more
expliciit bout this, and mention why there are frames in some versions,
without going into details. As it is, the text appears a mixture of general
headers, and constructs (frames) that do not necessarily make sense, and
misleading because the heavy text HTTP/2 might lead one to think that it is
possibly only, or mostly, intended for HTTP/2.


> Once I got to the business end of the document, the document starts by
> telling which headers not send when it is not at all clear what those
> headers are about in th first place.
>
> It=E2=80=99s also confusing what a protocol specific frame means, or why =
it cannot
> all be done with HTTP headers.
>

It would help to point to a specific section or paragraph. RFC 7540 Section
8 and HTTP/3 draft 24 section 4.1 detail message exchanges - I don't
especially feel the need to duplicate text in this document but accept that
it might help to reference these in the text.



Start of section 3, quote below. This text assumes detailed knowledge of
later text. It would be better to state that certain restrictions apply as
discussed in section (whaterever later section).

" If

   intermediaries want to specify prioritizaton on a multiplexed HTTP
   connection, it SHOULD use a PRIORITY_UPDATE frame and SHOULD NOT
   change the Priority header field.

=E2=80=9C



Cheers
Lucas

--0000000000000b275d059801544a
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><div style=3D"font-family:Helvetica,Arial;font-size:13px">comm=
ents inline</div> <br><p class=3D"airmail_on">On 20 November 2019 at 20.18.=
46, Lucas Pardue (<a href=3D"mailto:lucaspardue.24.7@gmail.com">lucaspardue=
.24.7@gmail.com</a>) wrote:</p> <div><blockquote type=3D"cite" class=3D"cle=
an_bq" style=3D"font-family:Helvetica,Arial;font-size:13px;font-style:norma=
l;font-variant-caps:normal;font-weight:normal;letter-spacing:normal;text-al=
ign:start;text-indent:0px;text-transform:none;white-space:normal;word-spaci=
ng:0px;text-decoration:none"><span><div><div></div><div><div dir=3D"ltr"><d=
iv dir=3D"auto"><div>Hi Mikkel,=C2=A0<div dir=3D"auto"><br></div><div dir=
=3D"auto">To comment as a co-author but speaking only for myself:</div><br>=
<div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, 20=
 Nov 2019, 20:57 Mikkel Fahn=C3=B8e J=C3=B8rgensen, &lt;<a href=3D"mailto:m=
ikkelfj@gmail.com" target=3D"_blank">mikkelfj@gmail.com</a>&gt; wrote:<br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left-width:1px;border-left-style:solid;border-left-color:rgb(204,204,2=
04);padding-left:1ex"><div><div style=3D"font-family:Helvetica,Arial;font-s=
ize:13px">Looking forward to digging further into this.</div><div style=3D"=
font-family:Helvetica,Arial;font-size:13px">...</div></div></blockquote></d=
iv></div><div dir=3D"auto"><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=
><div style=3D"font-family:Helvetica,Arial;font-size:13px"><br></div></div>=
</blockquote></div></div><div dir=3D"auto"><div class=3D"gmail_quote"><bloc=
kquote 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);paddin=
g-left:1ex"><div><div style=3D"font-family:Helvetica,Arial;font-size:13px">=
<br></div><div style=3D"font-family:Helvetica,Arial;font-size:13px">After r=
eading 1/3 of document, I still have no clue how the priority scheme works =
(except I have some guess based on earlier ideas that have floatet) and I h=
ave had to deal with a lot of HTTP/2 legacy that I am not necessarily inter=
ested in. HTTP/3 doc has also move away from implicit HTTP/2 familiarity, a=
t least last time I checked.</div></div></blockquote></div></div><div dir=
=3D"auto"><br></div><div dir=3D"auto">To reinterpret you point, I think tha=
t the concepts of urgency and precedence would benefit from better descript=
ion (issues #31[1] and #32[2]). But I also wonder if you are saying that th=
ere is too much or too little HTTP/2 specific/related content? Or am I miss=
ing out on your point here?</div></div></div></div></div></span></blockquot=
e></div><p>Yes, I think an overview of the mechanism is needed. This email =
was up to section 3.</p><p>On HTTP/2 I think it is warranted with a good ex=
planation. I don=E2=80=99t think more is necessary, and perhaps there is en=
ough, but it is placed too early, forcing focus on things that may not be m=
aterial to the reader and confuses grasping the core concepts.</p><p>Readin=
g further, I don=E2=80=99t bother to comment, but a general observation was=
 the each section raised questions that were answered in later sections - i=
t=E2=80=99s hard to address all at once, but worth keeping in mind. A minor=
 thing is the inline graphics which intuitively, to me, means hex encoded S=
VG og PNG, but that is not what is meant, and at the very end that becomes =
clear. A larger issues are why servers send priorities in the first place (=
it is eventually explained).</p><p><br></p><div><div><blockquote type=3D"ci=
te" class=3D"clean_bq" style=3D"font-family:Helvetica,Arial;font-size:13px;=
font-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacin=
g:normal;text-align:start;text-indent:0px;text-transform:none;white-space:n=
ormal;word-spacing:0px;text-decoration:none"><span><div><div><div dir=3D"lt=
r"><div dir=3D"auto"><div dir=3D"auto"><br class=3D"Apple-interchange-newli=
ne"><br></div><div dir=3D"auto"><div class=3D"gmail_quote"><blockquote clas=
s=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1px;b=
order-left-style:solid;border-left-color:rgb(204,204,204);padding-left:1ex"=
><div><div style=3D"font-family:Helvetica,Arial;font-size:13px"><br></div><=
div style=3D"font-family:Helvetica,Arial;font-size:13px">The document talks=
 about intermediate hop reprioritisation without making clear what that is =
or what purpose it serves. I can only assume load balancers and reverse pro=
xies. From a QUIC background that also leaves me wondering what that means =
- since each hop is necessarily also end to end, unless there is an extensi=
on wrapper frame, but that makes no sense.</div></div></blockquote></div></=
div><div dir=3D"auto"><br></div><div dir=3D"auto">The intent is to address =
the HTTP semantic layer but dip into HTTP version-specifics where necessary=
. We rely on readers being familiar with HTTP semantic concepts and termino=
logy but can probably do a better job of referencing. Since QUIC has no con=
cept of priority, but the serialisation of HTTP does and is ultimately coup=
led to the transport layer, it can be a bit tricky to pick the subject. Hap=
py to take some suggestions on specific ways to improve here</div></div></d=
iv></div></div></span></blockquote></div><p>Intermediates are explained whe=
n reading all the way to the end, but it is an example of confusion that ar=
ises while reading through the document. On HTTP version neutrality I think=
 that is fine, but it would help to be more expliciit bout this, and mentio=
n why there are frames in some versions, without going into details. As it =
is, the text appears a mixture of general headers, and constructs (frames) =
that do not necessarily make sense, and misleading because the heavy text H=
TTP/2 might lead one to think that it is possibly only, or mostly, intended=
 for HTTP/2.</p><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><div><div dir=3D"ltr"><div dir=3D"auto"><div dir=3D=
"auto"><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><div style=3D"fon=
t-family:Helvetica,Arial;font-size:13px"><br></div><div style=3D"font-famil=
y:Helvetica,Arial;font-size:13px">Once I got to the business end of the doc=
ument, the document starts by telling which headers not send when it is not=
 at all clear what those headers are about in th first place.</div><div sty=
le=3D"font-family:Helvetica,Arial;font-size:13px"><br></div><div style=3D"f=
ont-family:Helvetica,Arial;font-size:13px">It=E2=80=99s also confusing what=
 a protocol specific frame means, or why it cannot all be done with HTTP he=
aders.</div></div></blockquote></div></div><div dir=3D"auto"><br></div><div=
>It would help to point to a specific section or paragraph. RFC 7540 Sectio=
n 8 and HTTP/3 draft 24 section 4.1 detail message exchanges - I don&#39;t =
especially feel the need to duplicate text in this document but accept that=
 it might help to reference these in the text.</div><div><br></div></div></=
div></div></div></span></blockquote><div><br></div><div><br></div>Start of =
section 3, quote below. This text assumes detailed knowledge of later text.=
 It would be better to state that certain restrictions apply as discussed i=
n section (whaterever later section).</div><div><br></div><div>&quot;<span =
style=3D"white-space:pre-wrap"> If</span><pre style=3D"font-variant-ligatur=
es:normal;white-space:pre-wrap">   intermediaries want to specify prioritiz=
aton on a multiplexed HTTP
   connection, it SHOULD use a PRIORITY_UPDATE frame and SHOULD NOT
   change the Priority header field.</pre><pre style=3D"font-variant-ligatu=
res:normal;white-space:pre-wrap">=E2=80=9C</pre><pre style=3D"font-variant-=
ligatures:normal;white-space:pre-wrap"><br></pre><pre style=3D"font-variant=
-ligatures:normal;white-space:pre-wrap"><br></pre><blockquote type=3D"cite"=
 class=3D"clean_bq" style=3D"font-family:Helvetica,Arial;font-size:13px;fon=
t-style:normal;font-variant-caps:normal;font-weight:normal;letter-spacing:n=
ormal;text-align:start;text-indent:0px;text-transform:none;white-space:norm=
al;word-spacing:0px;text-decoration:none"><span><div><div><div dir=3D"ltr">=
<div dir=3D"auto">Cheers</div><div>Lucas<br></div></div></div></div></span>=
</blockquote></div></div></body></html>

--0000000000000b275d059801544a--


From nobody Sat Nov 23 17:48:42 2019
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 E37BE120013 for <quic@ietfa.amsl.com>; Sat, 23 Nov 2019 17:48:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.499
X-Spam-Level: 
X-Spam-Status: No, score=-17.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, 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_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] 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 kNz43KaJgynt for <quic@ietfa.amsl.com>; Sat, 23 Nov 2019 17:48:31 -0800 (PST)
Received: from mail-vs1-xe2f.google.com (mail-vs1-xe2f.google.com [IPv6:2607:f8b0:4864:20::e2f]) (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 7D405120045 for <quic@ietf.org>; Sat, 23 Nov 2019 17:48:31 -0800 (PST)
Received: by mail-vs1-xe2f.google.com with SMTP id y23so7608420vso.1 for <quic@ietf.org>; Sat, 23 Nov 2019 17:48:31 -0800 (PST)
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=bOR6UovPst7G2nTFYlF/FvrqxJCHgfoBtmK4NOKgzWs=; b=NHDNX6FNyzF87nn6YywhLlL+2VWrvb3IUG6HYll4JvSwLQcYKg0d2NT2knmwqP34UT P3DoGvFTfWQLwmNYP80G9Qyqq2gIHC/72NfrwzDXZoOfFRagqqStp/HWWi6UwOVVc5Ld 0UElOEIz4XPjpuGRl+8M65hW+bp/hPJSy3ALLUhEfba9ueSM/08m7hAtsf1/SHHo9Ej7 sJ3tk4HxIrE1nAI+1CFzsM4/as3sZrpn7K9F/Jfmx5P/3I5tk2oLlRCOUPgAYW6/bB1B PnQ1m8/Ltc/3uhvcUfvPdtT2uxAJp1RKodFGJ9P8J16471mxw+feFwNgql03u40GXVOO tRPQ==
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=bOR6UovPst7G2nTFYlF/FvrqxJCHgfoBtmK4NOKgzWs=; b=ftcrRMVWjbiFdGQh2C2HOcLytw6hicV+sRIkl0NRpjYgu5e81NxuyhCosZblBXAT1a YnwVIpjxrlyvHNBJ1U4S8ABCahGNJ/Rrso1uJqasZvbQ2A+02n5QSDBXT/dynYUO/S0s uXFXpOM9HiwYFkCpbDkRlsAxgKBrOZj3L0k7aMwEKWDOK/O7jFsy99tWyaA0d81H/56h +Z6e3JcIxsJIuAYDtQzqekhJ29y4x/APGZdvqefAMufpIv+CUKgKRzbUPBX1aZi2j1yy C070mgGAKjSoXb5AI9Cd4m2VTToRT4S274HH/lT5mwVDfzvSndB+uXswv5IPsx1IJwbV TKxQ==
X-Gm-Message-State: APjAAAXzPYBzGhNwG4uNSjGLVJQYD8J+ebldI4NxKJoPXkqcyUofYSoH jqMqqNKDk6WiQZBRzqmjqWMyrkVTEeDeFf3i35TQXw==
X-Google-Smtp-Source: APXvYqxvLW0PLf/sKrZNLuLeJU/D8CBoPmVlWHCNElECLku/2qKzAyRXjmPFGjZwxfEFny9bI0gOaXMl/skruv93KmI=
X-Received: by 2002:a67:e417:: with SMTP id d23mr4093118vsf.208.1574560109944;  Sat, 23 Nov 2019 17:48:29 -0800 (PST)
MIME-Version: 1.0
References: <CE03DB3D7B45C245BCA0D2432779493630766752@MX307CL04.corp.emc.com> <4460_1571933453_5DB1CD0D_4460_57_4_5AE9CCAA1B4A2248AB61B4C7F0AD5FB931F030A0@OPEXCAUBM44.corporate.adroot.infra.ftgroup> <1572918247420.10381@cs.auckland.ac.nz> <CABcZeBPy_39o37snzy8F6iyLQMg1aGkYbhy0A1N-PxFUmAmB0g@mail.gmail.com> <f2b1f803-b559-a166-8009-baff551bec5c@joelhalpern.com> <5df30dd2-6841-7140-43bf-8c1b9603653f@erg.abdn.ac.uk>
In-Reply-To: <5df30dd2-6841-7140-43bf-8c1b9603653f@erg.abdn.ac.uk>
From: Ian Swett <ianswett@google.com>
Date: Sat, 23 Nov 2019 20:48:17 -0500
Message-ID: <CAKcm_gM33z6njR1U5f8Lh3=cMzEnQQVWLVYui9zHHqz0kPc2Nw@mail.gmail.com>
Subject: Re: [OPSAWG] TSVWG WGLC: draft-ietf-tsvwg-transport-encrypt-08, closes 23 October 2019
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Cc: "Joel M. Halpern" <jmh@joelhalpern.com>, Peter Gutmann <pgut001@cs.auckland.ac.nz>,  "tsvwg@ietf.org" <tsvwg@ietf.org>, "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>, tsvwg-chairs <tsvwg-chairs@ietf.org>,  "opsawg@ietf.org" <opsawg@ietf.org>, "quic@ietf.org" <quic@ietf.org>, "saag@ietf.org" <saag@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000008409405980dd87a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/RimdLVSP6l35Uplh42UXsxqd27E>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 24 Nov 2019 01:48:35 -0000

--00000000000008409405980dd87a
Content-Type: text/plain; charset="UTF-8"

I think it's ok to publish a document with the stated goals, but I think
this needs to be done with great care and the current document implies some
value judgements and implications I don't think are fully justified by the
document.  A 3rd author with a slightly different perspective may help
achieve the right balance.

In section 2, I believe you should note that the reason transport headers
have been exposed in the past is largely an accident, and what is exposed
may not be optimal for network monitoring and management purposes.  For
example, TCPs ACKs are a suboptimal way to measure network RTT unless
timestamps are available. And tracking losses requires substantial state
and assumptions about the loss detection algorithm on the part of the
observer.

The section(2.1) on transport ossification and middleboxes is well done,
thanks!


*Detailed points: *

2: Context and Rationale
 "To achieve stable Internet operations, the IETF transport community
   has to date relied heavily on the results of measurements and the
   insights of the network operations.."

The use of 'stable' here implies that without these measurements the
internet would be unstable.  I understand what you're trying to say, but
this needs a reword to avoid the implied collapse of the internet.  I'd
suggest you remove the word stable from this document, as it occurs 2 other
times in similar context.

2.3

I think this section is too vague.  The phrase "can be used" is used
frequently, but without a clear understanding of what the transport headers
are used for.  After reading further, some of this is defined in section
3.1.2, so maybe a forward reference is in order.

3.1.2:

"Throughput and Goodput" - Throughput seems to overlap with "Traffic Rate
and Volume".   I'd suggest reorganizing these into two items, one for
Goodput and one for Throughput/Traffic Rate/etc.

6.5:

"Concealing transport header..." Do you mean encrypting, or is there some
other method you have in mind?  This word is used 9 times in the document
and I don't think it's a good word choice.

7:

 "To achieve stable Internet operations, the IETF transport community
   has, to date, relied heavily on measurement and insights of the
   network operations community to understand the trade-offs, and to
   inform selection of appropriate mechanisms, to ensure a safe,
   reliable, and robust Internet (e.g., [RFC1273],[RFC2914])."

I don't believe RFC2914 should be grouped with RFC1273.  2914 is about
principles, and 1273 is about measurement.  Based on my reading, 2914 does
not provide evidence that measurement is necessary in order to achieve the
desired principles.

Also, one of these RFCs is almost 20 years old and the other is almost 30.
I don't think these are good support for the thesis that network operators
measurement abilities have been critical to what you're claiming, even if
it is still true today.

Thanks, Ian


On Tue, Nov 5, 2019 at 5:27 AM Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:

> Thanks for the various comments on process.
>
> I expect both editors and the Chairs to work with our AD to confirm the
> intended scope, and then to decide on the next steps. This author wants
> to clarify how IETF transport protocols have been designed and have
> been/are being used.
>
> Gorry (as one of the editors of this document).
>
>
> On 05/11/2019 02:39, Joel M. Halpern wrote:
> > If the authors want to publish it as an RFC so as to comment on other
> > RFCs, they could approach the Independent Stream Editor.  That sort of
> > publication is one of the explicit purposes of the Independent Stream.
> >
> > Yours,
> > Joel
> >
> > On 11/4/2019 9:34 PM, Eric Rescorla wrote:
> >>
> >>
> >> On Mon, Nov 4, 2019 at 5:44 PM Peter Gutmann
> >> <pgut001@cs.auckland.ac.nz <mailto:pgut001@cs.auckland.ac.nz>> wrote:
> >>
> >>     I actually think it's a pretty good summary, and delivers exactly
> >> what's
> >>     promised in the title.  OTOH I can also see that it's going to get
> >>     bikeshedded
> >>     to death, and will probably never be editable into a form where
> >>     people won't
> >>     complain about it no matter how many changes are made.
> >> Alternatively, it'll
> >>     end up watered down to a point where no-one can complain any more
> >>     but it won't
> >>     say anything terribly useful by then.
> >>
> >>     Perhaps it could be published as is with a comment that it
> >>     represents the
> >>     opinions of the authors?  Although given that it's Informational
> >> and not
> >>     Standards-track or a BCP, that should be a given anyway.
> >>
> >>
> >> Actually, no. Most IETF documents, even informational ones, bear a
> >> statement that they have IETF Consensus.
> >>
> >> See: https://tools.ietf.org/html/rfc5741#section-3.2.1
> >> <https://tools.ietf.org/html/rfc5741#section-3..2.1>
> >>
> >> -Ekr
> >>
> >>
> >>     Peter.
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> OPSAWG mailing list
> >> OPSAWG@ietf.org
> >> https://www.ietf.org/mailman/listinfo/opsawg
> >>
>
>

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

<div dir=3D"ltr"><div>I think it&#39;s ok to publish a document with the st=
ated goals, but I think this needs to be done with great care and the curre=
nt document implies some value judgements and implications I don&#39;t thin=
k are fully justified by the document.=C2=A0 A 3rd author with a slightly d=
ifferent perspective may help achieve the right balance.</div><div><br></di=
v><div>In section 2, I believe you should note that the reason transport he=
aders have been exposed in the past is largely an accident, and what is exp=
osed may not be optimal for network monitoring and management purposes.=C2=
=A0 For example, TCPs ACKs are a suboptimal way to measure network RTT unle=
ss timestamps are available. And tracking losses requires substantial state=
 and assumptions about the loss detection algorithm on the part of the obse=
rver.<br></div><div><br></div><div><div>The section(2.1) on transport ossif=
ication and middleboxes is well done, thanks!</div><div><br></div><div></di=
v></div><div><div><br></div><div><u>Detailed points:=C2=A0</u>=C2=A0</div><=
div><br></div><div>2: Context and Rationale</div><div>=C2=A0&quot;To achiev=
e stable Internet operations, the IETF transport community</div>=C2=A0 =C2=
=A0has to date relied heavily on the results of measurements and the<br>=C2=
=A0 =C2=A0insights of the network operations..&quot;<div><br></div><div>The=
 use of &#39;stable&#39; here implies that without these measurements the i=
nternet would be unstable.=C2=A0 I understand what you&#39;re trying to say=
, but this needs a reword to avoid the implied collapse of the internet.=C2=
=A0 I&#39;d suggest you remove the word stable from this document, as it oc=
curs 2 other times in similar context.</div><div><br></div></div><div>2.3</=
div><div><br></div><div>I think this section is too vague.=C2=A0 The phrase=
 &quot;can be used&quot; is used frequently, but without a clear understand=
ing of what the transport headers are used for.=C2=A0 After reading further=
, some of this is defined in section 3.1.2, so maybe a forward reference is=
 in order.</div><div><br></div><div>3.1.2:</div><div><br></div><div>&quot;T=
hroughput and Goodput&quot; - Throughput seems to overlap with &quot;Traffi=
c Rate and Volume&quot;.=C2=A0 =C2=A0I&#39;d suggest reorganizing these int=
o two items, one for Goodput and one for Throughput/Traffic Rate/etc.</div>=
<div><br></div><div>6.5:</div><div><br></div><div>&quot;Concealing transpor=
t header...&quot; Do you mean encrypting, or is there some other method you=
 have in mind?=C2=A0 This word is used 9 times in the document and I don&#3=
9;t think it&#39;s a good word choice.</div><div><br></div><div>7:</div><di=
v><br></div><div>=C2=A0&quot;To achieve stable Internet operations, the IET=
F transport community<br>=C2=A0 =C2=A0has, to date, relied heavily on measu=
rement and insights of the<br>=C2=A0 =C2=A0network operations community to =
understand the trade-offs, and to<br>=C2=A0 =C2=A0inform selection of appro=
priate mechanisms, to ensure a safe,<br>=C2=A0 =C2=A0reliable, and robust I=
nternet (e.g., [RFC1273],[RFC2914]).&quot;<br></div><div><br></div><div>I d=
on&#39;t believe RFC2914 should be grouped with RFC1273.=C2=A0 2914 is abou=
t principles, and 1273 is about measurement.=C2=A0 Based on my reading, 291=
4 does not provide evidence that measurement is necessary in order to achie=
ve=C2=A0the desired principles.</div><div><br></div><div>Also, one of these=
 RFCs is almost 20 years old and the other is almost 30.=C2=A0 I don&#39;t =
think these are good support for the thesis that network operators measurem=
ent abilities have been critical to what you&#39;re claiming, even if it is=
 still true today.</div><div><br></div><div>Thanks, Ian</div><div><br></div=
></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr"=
>On Tue, Nov 5, 2019 at 5:27 AM Gorry Fairhurst &lt;<a href=3D"mailto:gorry=
@erg.abdn.ac.uk" target=3D"_blank">gorry@erg.abdn.ac.uk</a>&gt; wrote:<br><=
/div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bo=
rder-left:1px solid rgb(204,204,204);padding-left:1ex">Thanks for the vario=
us comments on process.<br>
<br>
I expect both editors and the Chairs to work with our AD to confirm the <br=
>
intended scope, and then to decide on the next steps. This author wants <br=
>
to clarify how IETF transport protocols have been designed and have <br>
been/are being used.<br>
<br>
Gorry (as one of the editors of this document).<br>
<br>
<br>
On 05/11/2019 02:39, Joel M. Halpern wrote:<br>
&gt; If the authors want to publish it as an RFC so as to comment on other =
<br>
&gt; RFCs, they could approach the Independent Stream Editor.=C2=A0 That so=
rt of <br>
&gt; publication is one of the explicit purposes of the Independent Stream.=
<br>
&gt;<br>
&gt; Yours,<br>
&gt; Joel<br>
&gt;<br>
&gt; On 11/4/2019 9:34 PM, Eric Rescorla wrote:<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; On Mon, Nov 4, 2019 at 5:44 PM Peter Gutmann <br>
&gt;&gt; &lt;<a href=3D"mailto:pgut001@cs.auckland.ac.nz" target=3D"_blank"=
>pgut001@cs.auckland.ac.nz</a> &lt;mailto:<a href=3D"mailto:pgut001@cs.auck=
land.ac.nz" target=3D"_blank">pgut001@cs.auckland.ac.nz</a>&gt;&gt; wrote:<=
br>
&gt;&gt;<br>
&gt;&gt; =C2=A0=C2=A0=C2=A0 I actually think it&#39;s a pretty good summary=
, and delivers exactly <br>
&gt;&gt; what&#39;s<br>
&gt;&gt; =C2=A0=C2=A0=C2=A0 promised in the title.=C2=A0 OTOH I can also se=
e that it&#39;s going to get<br>
&gt;&gt; =C2=A0=C2=A0=C2=A0 bikeshedded<br>
&gt;&gt; =C2=A0=C2=A0=C2=A0 to death, and will probably never be editable i=
nto a form where<br>
&gt;&gt; =C2=A0=C2=A0=C2=A0 people won&#39;t<br>
&gt;&gt; =C2=A0=C2=A0=C2=A0 complain about it no matter how many changes ar=
e made. <br>
&gt;&gt; Alternatively, it&#39;ll<br>
&gt;&gt; =C2=A0=C2=A0=C2=A0 end up watered down to a point where no-one can=
 complain any more<br>
&gt;&gt; =C2=A0=C2=A0=C2=A0 but it won&#39;t<br>
&gt;&gt; =C2=A0=C2=A0=C2=A0 say anything terribly useful by then.<br>
&gt;&gt;<br>
&gt;&gt; =C2=A0=C2=A0=C2=A0 Perhaps it could be published as is with a comm=
ent that it<br>
&gt;&gt; =C2=A0=C2=A0=C2=A0 represents the<br>
&gt;&gt; =C2=A0=C2=A0=C2=A0 opinions of the authors?=C2=A0 Although given t=
hat it&#39;s Informational <br>
&gt;&gt; and not<br>
&gt;&gt; =C2=A0=C2=A0=C2=A0 Standards-track or a BCP, that should be a give=
n anyway.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; Actually, no. Most IETF documents, even informational ones, bear a=
 <br>
&gt;&gt; statement that they have IETF Consensus.<br>
&gt;&gt;<br>
&gt;&gt; See: <a href=3D"https://tools.ietf.org/html/rfc5741#section-3.2.1"=
 rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/rfc5741#s=
ection-3.2.1</a> <br>
&gt;&gt; &lt;<a href=3D"https://tools.ietf.org/html/rfc5741#section-3..2.1"=
 rel=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/rfc5741#s=
ection-3..2.1</a>&gt;<br>
&gt;&gt;<br>
&gt;&gt; -Ekr<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; =C2=A0=C2=A0=C2=A0 Peter.<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt;<br>
&gt;&gt; _______________________________________________<br>
&gt;&gt; OPSAWG mailing list<br>
&gt;&gt; <a href=3D"mailto:OPSAWG@ietf.org" target=3D"_blank">OPSAWG@ietf.o=
rg</a><br>
&gt;&gt; <a href=3D"https://www.ietf.org/mailman/listinfo/opsawg" rel=3D"no=
referrer" target=3D"_blank">https://www.ietf.org/mailman/listinfo/opsawg</a=
><br>
&gt;&gt;<br>
<br>
</blockquote></div>

--00000000000008409405980dd87a--


From nobody Sat Nov 23 19:08:05 2019
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 93E51120091 for <quic@ietfa.amsl.com>; Sat, 23 Nov 2019 19:08:02 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 o4seWqGdicAp for <quic@ietfa.amsl.com>; Sat, 23 Nov 2019 19:08:00 -0800 (PST)
Received: from mail-qt1-x82e.google.com (mail-qt1-x82e.google.com [IPv6:2607:f8b0:4864:20::82e]) (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 943A112008B for <quic@ietf.org>; Sat, 23 Nov 2019 19:08:00 -0800 (PST)
Received: by mail-qt1-x82e.google.com with SMTP id i17so12975428qtq.1 for <quic@ietf.org>; Sat, 23 Nov 2019 19:08:00 -0800 (PST)
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=zpXqfCWlUHUycuYrZTWb+azfwKtTjoPNUOGGdIbX5CU=; b=K5toLdHomqsTEPcYIL1UOayu/nFgqHDpN9BuhjhiI/x/Iu3vZNaQ2U63oZ1nQiu5sj awHO9RtRtwXLxWsIJj5u9D9PHTDT4ahnfFVIZ6tvTHbVTPSOH+HLDYTxEPHD+5xUFnn+ GzXDr6jVx7pQoF028QWSjQAgiIyeP5tpnI0thhp/J2BmljMeQWykabm1jKOC6abtSw4v 3ZYgAo1e7HsPohq6WbxTpxr4DGPFIaxg+Cc0KDtsysVV+lOIRnsJmwxALkA6kVXDahqP ygIiUrCMkBIVQGJNCV0xbSCwiUqb1F7kORqLaersHZg6/iYb0B/PXeK8Ez14WpUH/xOf 223Q==
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=zpXqfCWlUHUycuYrZTWb+azfwKtTjoPNUOGGdIbX5CU=; b=McgjQ6B1YEwpBo79gAqcEvJCABMFaaugxfWmBGjhLNH9tZxB4MPWWaPrWGjXpXnWwl 7y7o9GjCX9lwbu1cRt7hMvTiaFYJw9WzYP7xZrkoSzxlSioGB2RCaoGRfjFPv7PBIE41 MX/bHFf2f5Zec+nI7k0GG0PysBLgoeDYzaW3RZ32b3NnhEJ2JvsMlEW5QhHixdsnwNg1 VUy5ipvJd54+DzI5CUttNCMaWWdi5rzW/TwGlN7Ie9co8g4cKagXd0kzi9tJOkeyDyo3 d7/yNtpP1p24tsjWDccgYR8EXsjM/BaUsXLDajcCfrquppIHqbNco4m4YZlzie9YDrhR pH2g==
X-Gm-Message-State: APjAAAW6ucDZZv6AFxzE8Q8VMRZwPpV0lcBmhvqWM+O+jeHxa4Lvc38/ IO82Qe2EZhjLvM9goY+rG4gvhg==
X-Google-Smtp-Source: APXvYqysC5hJISr8X4JWog31JS6YQ8wqzhTAMV7k8ERFdAOQsww9zJqB2hgXBCSiygJQjSFrdCzR+Q==
X-Received: by 2002:ac8:1403:: with SMTP id k3mr22459243qtj.58.1574564879567;  Sat, 23 Nov 2019 19:07:59 -0800 (PST)
Received: from ubuntu-dmitri (ool-44c1d219.dyn.optonline.net. [68.193.210.25]) by smtp.gmail.com with ESMTPSA id h186sm1265978qkf.64.2019.11.23.19.07.58 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sat, 23 Nov 2019 19:07:59 -0800 (PST)
Date: Sat, 23 Nov 2019 22:07:57 -0500
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: =?utf-8?B?5ryC5rOK55qE5qKm?= <78690842@qq.com>
Cc: Bence =?iso-8859-1?B?Qulr?= <bnc@chromium.org>, Jiuhai Zhang <jiuhai.zhang@gmail.com>, quic <quic@ietf.org>
Subject: Re: =?utf-8?B?5Zue5aSN?= =?utf-8?B?77ya?= Questions about QPACK
Message-ID: <20191124030756.GD25462@ubuntu-dmitri>
Mail-Followup-To: =?utf-8?B?5ryC5rOK55qE5qKm?= <78690842@qq.com>, Bence =?iso-8859-1?B?Qulr?= <bnc@chromium.org>, Jiuhai Zhang <jiuhai.zhang@gmail.com>, quic <quic@ietf.org>
References: <tencent_6865D1996656F65720369049BB7960478D06@qq.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: 8bit
In-Reply-To: <tencent_6865D1996656F65720369049BB7960478D06@qq.com>
User-Agent: Mutt/1.5.24 (2015-08-30)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/KRMuLC1r3AbIIC_TSJIz19Q8SMc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 24 Nov 2019 03:08:03 -0000

On Sun, Nov 24, 2019 at 01:14:04AM +0800, æ¼‚æ³Šçš„æ¢¦ wrote:
> I think it is not such a good idea to insert name with 0-length entry
> into dynamic table, because it needs to transmit more information to
> recipient through the encoder stream for synchronization of dynamic
> table between the sender and recipient.

I am afraid I don't understand what you mean here.

> In my option, it never need to insert name with 0-length entry into
> dynamic table. When we need reference the name only index in the
> Literal Header Field, we can use the index of the entry with the same
> name and a different value we first find in the dynamic table.

It is possible only to insert full name/value pairs into the dynamic
table, but it's not always the best thing to do.  If the value never
repeats again, it will just waste space in the dynamic table.

A good example of the header field whose name is not in the static
table and whose value rarely repeats is X-FB-Debug from the Facebook
server QIF file used for the QPACK interop [1].  ls-qpack inserts
such entries into the dynamic table with zero-length values [2].
This has a beneficial effect on compression ratio.  Without it (I
commented out this code for this test), encoding this QIF file [3]
makes compression ratio worse: from 0.176 to 0.178.

Now, if x-fb-debug is always inserted full -- including the value --
into the dynamic table, the compression ratio drops to 0.287.

> Could you please advise if this is a good idea or which method is
> better in the real situation?

There is no perfect method as different applications will produce
different header patterns.  ls-qpack uses history to decide which
entries to index; other implementations use hard-coded assumptions
(e.g. "user-agent" header never changes.).  This is an interesting
question.  A better method may yet be uncovered.

  - Dmitri.

1. https://github.com/qpackers/qifs/blob/master/qifs/fb-resp.qif
2. https://github.com/litespeedtech/ls-qpack/blob/d79ab9ae19d25bdb6e14d10bb76dbc9d7bcfcf21/lsqpack.c#L1795
3. Table size 4096, no risk, immediate ack.


From nobody Sat Nov 23 23:31:35 2019
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 3510212002E for <quic@ietfa.amsl.com>; Sat, 23 Nov 2019 23:31:34 -0800 (PST)
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=qful3igF; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=oEqKw8VO
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 NoR5SPCE4Nho for <quic@ietfa.amsl.com>; Sat, 23 Nov 2019 23:31:30 -0800 (PST)
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 B5307120025 for <quic@ietf.org>; Sat, 23 Nov 2019 23:31:30 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id D9FBD222C9 for <quic@ietf.org>; Sun, 24 Nov 2019 02:31:29 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Sun, 24 Nov 2019 02:31:29 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject:message-id:date; s= fm1; bh=beEyGaFUEI+A5pK8VhOWp4fzwaJlVjppOUMDKuPshqk=; b=qful3igF /uKe4ooAZRQmGZ0ibDF1alDu78NdewnVWGrb37I6uM/CZZILfB6CFGfeXrt/2S44 /F8Sv7j6ASqslDbKdgcr3xLWCwTu/qD92wVed1KzbT3MIGsOpo6dVEFsATqi0QWJ Mk7U94LfXwFUukwOYRFKQQYXfqyHWNpf5BpcPZOjjt2QfnKbrdFX6Ukb3oBylzeK PDAWpFKiB4BTQP8KdsKg+VBYnAjCbNpQFVXvcDDrggy+mnU6SLIGIrVw0ydXKLmm Dd64NWZwDk+95dEvlaD48X5kF4ZqcWV1yhr1LkUSwVbKvfgLRxshNQfW4liz1Gfl 6v5g0tDdAsJ19Q==
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-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=beEyGaFUEI+A5pK8VhOWp4fzwaJlV jppOUMDKuPshqk=; b=oEqKw8VOPiBVDDPWzCHXmyGCELqAEZNadhy0iBecWJWM+ ROkrTDUljuxvcY+p8sQOhsGJ/JgWbi2a2p4kidnjGUqDOOzSr/StDfl5vdPPGn8L FV2NMQnM96LtgDwTlmyKl0vwoYXQJhKySIcq5jy7MV6sD63FmmGrCtW664EgssX1 XB5aHkDd+Rm0R86KEYbWo6pszAW4NDMLQssjIQRvz+NgW9EtnyZ+4ti2k//91ELD JzKZ0Ac7mQPfErkyIlKSQzHfYs1Z8nKaEOqgmDemsq82CyBxEtLQxkEzF4wmPTW0 n1cN/GRHUiew2rs3M0CNse8QWhCqyJHJa4rRs2L+Q==
X-ME-Sender: <xms:0THaXcNvpeiJjI_VGfeq0lB6aJD4xg2saTZHs-TyvxPBGRWNblhkXA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudehjedguddtiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurheptggghffvufesrgdttdertddtje enucfhrhhomheptfgvphhoshhithhorhihucettghtihhvihhthicuufhumhhmrghrhicu uehothcuoeguohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvghtqeenucffohhmrghinh epghhithhhuhgsrdgtohhmnecukfhppeegtddruddugedrfeefrddvudehnecurfgrrhgr mhepmhgrihhlfhhrohhmpeguohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvghtnecuve hluhhsthgvrhfuihiivgepud
X-ME-Proxy: <xmx:0THaXTK-5gYm1OeJhiqEtCEd3Rk4wKUQPTDwtjeNVH8R3bzjXpQaLQ> <xmx:0THaXVEwEhmOC0j6N4PSAZ-DdnFP0ZBhCuI2dFdbHW-YrTWWAuRnrw> <xmx:0THaXTTWmbZzeCggKUga3UOAJUzY8BZK0CbKYbB1KTn1lncumqBSig> <xmx:0THaXSpxAgA6NIoahOoqNpyWGzs59u927B0Kt9l4LBTKFYZLa8KcNw>
Received: from [10.1.0.4] (unknown [40.114.33.215]) by mail.messagingengine.com (Postfix) with ESMTPA id 5867580059 for <quic@ietf.org>; Sun, 24 Nov 2019 02:31:29 -0500 (EST)
Content-Type: multipart/alternative; boundary="===============2879749712625664066=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: quic@ietf.org
Subject: Weekly github digest ( Activity Summary)
Message-Id: <20191124073129.5867580059@mailuser.nyi.internal>
Date: Sun, 24 Nov 2019 02:31:29 -0500 (EST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/JtXiX34ILhWalll7rji413u6jjg>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 24 Nov 2019 07:31:34 -0000

--===============2879749712625664066==
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 (+15/-2/=F0=9F=92=AC56)
  15 issues created:
  - HTTP/3 references QUIC Stream IDs directly, allowing illegal references=
 (by ianswett)
    https://github.com/quicwg/base-drafts/issues/3273=20
  - pto_count should be reset when dropping a packet number space (by marte=
n-seemann)
    https://github.com/quicwg/base-drafts/issues/3272=20
  - Retry packet with zero-length token doesn't make sense (by marten-seema=
nn)
    https://github.com/quicwg/base-drafts/issues/3271=20
  - CONNECTION_CLOSE for unpadded Initial (by martinthomson)
    https://github.com/quicwg/base-drafts/issues/3269=20
  - Prevent a connection from idle timing out while blocked (by ianswett)
    https://github.com/quicwg/base-drafts/issues/3268 [-transport]=20
  - Add capability for sending HTTP metadata (trailer fields) in mid-stream=
 (by royfielding)
    https://github.com/quicwg/base-drafts/issues/3265=20
  - Reduce HTTP/3 editorial dependence on HTTP/2 (by royfielding)
    https://github.com/quicwg/base-drafts/issues/3264=20
  - Justify or reconcile deviation from TCP kMinimumWindow value (by pravb)
    https://github.com/quicwg/base-drafts/issues/3261=20
  - Justify or reconcile deviation from TCP TLP timeout calculation (by pra=
vb)
    https://github.com/quicwg/base-drafts/issues/3260=20
  - Safety issue during incipient persistent congestion episode (by pravb)
    https://github.com/quicwg/base-drafts/issues/3259=20
  - Allow CRYPTO_BUFFER_EXCEEEDED error when CRYPTO frame goes beyond 2^62 =
bytes (by kazuho)
    https://github.com/quicwg/base-drafts/issues/3258=20
  - Disabling Spin bit for what percentage of connections? (by igorlord)
    https://github.com/quicwg/base-drafts/issues/3257=20
  - Packet reordering thresholds less than 3 are not sufficiently reorderin=
g tolerant (by ianswett)
    https://github.com/quicwg/base-drafts/issues/3256 [-recovery]=20
  - Clarify padding of INITIAL packets (by rmarx)
    https://github.com/quicwg/base-drafts/issues/3255=20
  - Contradictory language regarding multiplexing connections with zero-len=
gth IDs (by Ralith)
    https://github.com/quicwg/base-drafts/issues/3254=20

  24 issues received 56 new comments:
  - #3272 pto_count should be reset when dropping a packet number space (2 =
by ianswett, janaiyengar)
    https://github.com/quicwg/base-drafts/issues/3272=20
  - #3268 Prevent a connection from idle timing out while blocked (1 by ian=
swett)
    https://github.com/quicwg/base-drafts/issues/3268 [-transport]=20
  - #3264 Reduce HTTP/3 editorial dependence on HTTP/2 (2 by MikeBishop, ia=
nswett)
    https://github.com/quicwg/base-drafts/issues/3264 [-http]=20
  - #3258 Allow CRYPTO_BUFFER_EXCEEEDED error when CRYPTO frame goes beyond=
 2^62 bytes (1 by martinthomson)
    https://github.com/quicwg/base-drafts/issues/3258 [-transport] [proposa=
l-ready]=20
  - #3257 Disabling Spin bit for what percentage of connections? (1 by brit=
ram)
    https://github.com/quicwg/base-drafts/issues/3257=20
  - #3256 Packet reordering thresholds less than 3 are not sufficiently reo=
rdering tolerant (1 by ianswett)
    https://github.com/quicwg/base-drafts/issues/3256 [-recovery]=20
  - #3255 Clarify padding of INITIAL packets (8 by RyanAtGoogle, ianswett, =
janaiyengar, kazuho, martinthomson, rmarx)
    https://github.com/quicwg/base-drafts/issues/3255=20
  - #3245 Make RFC 6928 normative (7 by gorryfair, huitema, ianswett, janai=
yengar)
    https://github.com/quicwg/base-drafts/issues/3245 [-recovery]=20
  - #3244 Can we make a normative ref to  RFC8085? (8 by gorryfair, ianswet=
t, janaiyengar, martinthomson)
    https://github.com/quicwg/base-drafts/issues/3244 [-recovery]=20
  - #3243 Add caution when using IW10 and fragmentation  (4 by ianswett, ja=
naiyengar, martinthomson, pravb)
    https://github.com/quicwg/base-drafts/issues/3243 [-transport]=20
  - #3205 max_datagram_size being a variable means other constants become v=
ariables (4 by gorryfair, ianswett)
    https://github.com/quicwg/base-drafts/issues/3205 [-recovery]=20
  - #3197 active_connection_id_limit defaults to 0 (1 by mnot)
    https://github.com/quicwg/base-drafts/issues/3197 [-transport] [design]=
=20
  - #3193 active_connection_id_limit interacts poorly with Retire Prior To =
(2 by erickinnear, janaiyengar)
    https://github.com/quicwg/base-drafts/issues/3193=20
  - #3189 QUIC lacks on-path exposure of packet loss (1 by mnot)
    https://github.com/quicwg/base-drafts/issues/3189 [-transport]=20
  - #3159 Server should not accept 1-RTT traffic before handshake completio=
n (1 by mnot)
    https://github.com/quicwg/base-drafts/issues/3159 [-tls] [design]=20
  - #3111 [Version Ossification] Alternative version and Initial Salt shoul=
d be part of NEW_TOKEN (1 by mnot)
    https://github.com/quicwg/base-drafts/issues/3111 [-transport] [design]=
=20
  - #3102 Add provisional registration for all registries (1 by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/3102 [-http] [-transport] =

  - #3094 congestion window increase on every ACKed packet could result in =
bursty sends (3 by gorryfair, ianswett, pravb)
    https://github.com/quicwg/base-drafts/issues/3094 [-recovery] [design] =

  - #3014 Handling of corrupt Retry packets (2 by DavidSchinazi, martinthom=
son)
    https://github.com/quicwg/base-drafts/issues/3014 [-transport] [design]=
 [proposal-ready]=20
  - #2863 unrecoverable loss pattern leads to deadlock (1 by mnot)
    https://github.com/quicwg/base-drafts/issues/2863 [-transport] [design]=
=20
  - #2792 Timing side-channel on key updates (1 by mnot)
    https://github.com/quicwg/base-drafts/issues/2792 [-tls] [design]=20
  - #2744 Idle Timer Can Fire Even with Outstanding Data to Send (1 by jana=
iyengar)
    https://github.com/quicwg/base-drafts/issues/2744 [-transport]=20
  - #2496 QUIC Version Ossification (1 by mnot)
    https://github.com/quicwg/base-drafts/issues/2496 [-transport] [design]=
=20
  - #1978 Sender-Controlled Delayed ACK Ratio (1 by c-taylor)
    https://github.com/quicwg/base-drafts/issues/1978 [-recovery] [-transpo=
rt] [design] [parked] [quicv2]=20

  2 issues closed:
  - Prevent a connection from idle timing out while blocked https://github.=
com/quicwg/base-drafts/issues/3268 [-transport]=20
  - QUIC lacks on-path exposure of packet loss https://github.com/quicwg/ba=
se-drafts/issues/3189 [-transport]=20



Pull requests
-------------
* quicwg/base-drafts (+4/-0/=F0=9F=92=AC12)
  4 pull requests submitted:
  - Disabling Spin bit for what percentage of connections? (by igorlord)
    https://github.com/quicwg/base-drafts/pull/3270=20
  - TLS: fix references to registries (by Lekensteyn)
    https://github.com/quicwg/base-drafts/pull/3267=20
  - Prevent Idle Timeout while Blocked (by nibanks)
    https://github.com/quicwg/base-drafts/pull/3266=20
  - Key generation for updates MAY be deferred (by martinthomson)
    https://github.com/quicwg/base-drafts/pull/3263 [-tls] [design]=20

  7 pull requests received 12 new comments:
  - #3266 Prevent Idle Timeout while Blocked (1 by martinthomson)
    https://github.com/quicwg/base-drafts/pull/3266 [-transport]=20
  - #3248 Fix congestion control permissiveness (1 by janaiyengar)
    https://github.com/quicwg/base-drafts/pull/3248 [-recovery]=20
  - #3232 Limit CWND increase in slow start (2 by goelvidhi, janaiyengar)
    https://github.com/quicwg/base-drafts/pull/3232 [-recovery] [design]=20
  - #3186 allow CRYPTO_BUFFER_EXCEEDED when overflowing a CRYPTO frame (2 b=
y kazuho, martinthomson)
    https://github.com/quicwg/base-drafts/pull/3186 [-transport] [design]=20
  - #3145 use a HANDSHAKE_DONE frame to drive the handshake to confirmation=
 (1 by RyanAtGoogle)
    https://github.com/quicwg/base-drafts/pull/3145 [-tls] [-transport]=20
  - #3120 Add retry integrity tag (4 by DavidSchinazi, ekr, marten-seemann)
    https://github.com/quicwg/base-drafts/pull/3120 [-tls] [-transport] [de=
sign]=20
  - #3099 Change idle_timeout to max_idle_timeout (1 by ianswett)
    https://github.com/quicwg/base-drafts/pull/3099 [-transport]=20


Repositories tracked by this digest:
-----------------------------------
* https://github.com/quicwg/base-drafts

--===============2879749712625664066==
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 ( Activity Summary)</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 November 24, 2019</h1>

<p>Events without label "editorial"</p>

<h2>Issues</h2>

<h3>quicwg/base-drafts (+15/-2/=F0=9F=92=AC56)</h3>
  <p class=3D"new">15 issues created:</p>
  <ul>
  <li>#3273 <a href=3D"https://github.com/quicwg/base-drafts/issues/3273">H=
TTP/3 references QUIC Stream IDs directly, allowing illegal references</a> =
(by ianswett) </li>
 =20
  <li>#3272 <a href=3D"https://github.com/quicwg/base-drafts/issues/3272">p=
to_count should be reset when dropping a packet number space</a> (by marten=
-seemann) </li>
 =20
  <li>#3271 <a href=3D"https://github.com/quicwg/base-drafts/issues/3271">R=
etry packet with zero-length token doesn&#x27;t make sense</a> (by marten-s=
eemann) </li>
 =20
  <li>#3269 <a href=3D"https://github.com/quicwg/base-drafts/issues/3269">C=
ONNECTION_CLOSE for unpadded Initial</a> (by martinthomson) </li>
 =20
  <li>#3268 <a href=3D"https://github.com/quicwg/base-drafts/issues/3268">P=
revent a connection from idle timing out while blocked</a> (by ianswett) <s=
pan class=3D"label" style=3D"background-color: #fbca04; color: #000000">-tr=
ansport</span> </li>
 =20
  <li>#3265 <a href=3D"https://github.com/quicwg/base-drafts/issues/3265">A=
dd capability for sending HTTP metadata (trailer fields) in mid-stream</a> =
(by royfielding) </li>
 =20
  <li>#3264 <a href=3D"https://github.com/quicwg/base-drafts/issues/3264">R=
educe HTTP/3 editorial dependence on HTTP/2</a> (by royfielding) </li>
 =20
  <li>#3261 <a href=3D"https://github.com/quicwg/base-drafts/issues/3261">J=
ustify or reconcile deviation from TCP kMinimumWindow value</a> (by pravb) =
</li>
 =20
  <li>#3260 <a href=3D"https://github.com/quicwg/base-drafts/issues/3260">J=
ustify or reconcile deviation from TCP TLP timeout calculation</a> (by prav=
b) </li>
 =20
  <li>#3259 <a href=3D"https://github.com/quicwg/base-drafts/issues/3259">S=
afety issue during incipient persistent congestion episode</a> (by pravb) <=
/li>
 =20
  <li>#3258 <a href=3D"https://github.com/quicwg/base-drafts/issues/3258">A=
llow CRYPTO_BUFFER_EXCEEEDED error when CRYPTO frame goes beyond 2^62 bytes=
</a> (by kazuho) </li>
 =20
  <li>#3257 <a href=3D"https://github.com/quicwg/base-drafts/issues/3257">D=
isabling Spin bit for what percentage of connections?</a> (by igorlord) </l=
i>
 =20
  <li>#3256 <a href=3D"https://github.com/quicwg/base-drafts/issues/3256">P=
acket reordering thresholds less than 3 are not sufficiently reordering tol=
erant</a> (by ianswett) <span class=3D"label" style=3D"background-color: #f=
bca04; color: #000000">-recovery</span> </li>
 =20
  <li>#3255 <a href=3D"https://github.com/quicwg/base-drafts/issues/3255">C=
larify padding of INITIAL packets</a> (by rmarx) </li>
 =20
  <li>#3254 <a href=3D"https://github.com/quicwg/base-drafts/issues/3254">C=
ontradictory language regarding multiplexing connections with zero-length I=
Ds</a> (by Ralith) </li>
  </ul>

  <p>24 issues received 56 new comments:</p>
  <ul>
  <li>#3272 <a href=3D"https://github.com/quicwg/base-drafts/issues/3272">p=
to_count should be reset when dropping a packet number space</a> (2 by ians=
wett, janaiyengar) </li>
 =20
  <li>#3268 <a href=3D"https://github.com/quicwg/base-drafts/issues/3268">P=
revent a connection from idle timing out while blocked</a> (1 by ianswett) =
<span class=3D"label" style=3D"background-color: #fbca04; color: #000000">-=
transport</span> </li>
 =20
  <li>#3264 <a href=3D"https://github.com/quicwg/base-drafts/issues/3264">R=
educe HTTP/3 editorial dependence on HTTP/2</a> (2 by MikeBishop, ianswett)=
 <span class=3D"label" style=3D"background-color: #fbca04; color: #000000">=
-http</span> </li>
 =20
  <li>#3258 <a href=3D"https://github.com/quicwg/base-drafts/issues/3258">A=
llow CRYPTO_BUFFER_EXCEEEDED error when CRYPTO frame goes beyond 2^62 bytes=
</a> (1 by martinthomson) <span class=3D"label" style=3D"background-color: =
#fbca04; color: #000000">-transport</span> <span class=3D"label" style=3D"b=
ackground-color: #c5def5; color: #000000">proposal-ready</span> </li>
 =20
  <li>#3257 <a href=3D"https://github.com/quicwg/base-drafts/issues/3257">D=
isabling Spin bit for what percentage of connections?</a> (1 by britram) </=
li>
 =20
  <li>#3256 <a href=3D"https://github.com/quicwg/base-drafts/issues/3256">P=
acket reordering thresholds less than 3 are not sufficiently reordering tol=
erant</a> (1 by ianswett) <span class=3D"label" style=3D"background-color: =
#fbca04; color: #000000">-recovery</span> </li>
 =20
  <li>#3255 <a href=3D"https://github.com/quicwg/base-drafts/issues/3255">C=
larify padding of INITIAL packets</a> (8 by RyanAtGoogle, ianswett, janaiye=
ngar, kazuho, martinthomson, rmarx) </li>
 =20
  <li>#3245 <a href=3D"https://github.com/quicwg/base-drafts/issues/3245">M=
ake RFC 6928 normative</a> (7 by gorryfair, huitema, ianswett, janaiyengar)=
 <span class=3D"label" style=3D"background-color: #fbca04; color: #000000">=
-recovery</span> </li>
 =20
  <li>#3244 <a href=3D"https://github.com/quicwg/base-drafts/issues/3244">C=
an we make a normative ref to  RFC8085?</a> (8 by gorryfair, ianswett, jana=
iyengar, martinthomson) <span class=3D"label" style=3D"background-color: #f=
bca04; color: #000000">-recovery</span> </li>
 =20
  <li>#3243 <a href=3D"https://github.com/quicwg/base-drafts/issues/3243">A=
dd caution when using IW10 and fragmentation </a> (4 by ianswett, janaiyeng=
ar, martinthomson, pravb) <span class=3D"label" style=3D"background-color: =
#fbca04; color: #000000">-transport</span> </li>
 =20
  <li>#3205 <a href=3D"https://github.com/quicwg/base-drafts/issues/3205">m=
ax_datagram_size being a variable means other constants become variables</a=
> (4 by gorryfair, ianswett) <span class=3D"label" style=3D"background-colo=
r: #fbca04; color: #000000">-recovery</span> </li>
 =20
  <li>#3197 <a href=3D"https://github.com/quicwg/base-drafts/issues/3197">a=
ctive_connection_id_limit defaults to 0</a> (1 by mnot) <span class=3D"labe=
l" style=3D"background-color: #fbca04; color: #000000">-transport</span> <s=
pan class=3D"label" style=3D"background-color: #1d76db; color: #ffffff">des=
ign</span> </li>
 =20
  <li>#3193 <a href=3D"https://github.com/quicwg/base-drafts/issues/3193">a=
ctive_connection_id_limit interacts poorly with Retire Prior To</a> (2 by e=
rickinnear, janaiyengar) </li>
 =20
  <li>#3189 <a href=3D"https://github.com/quicwg/base-drafts/issues/3189">Q=
UIC lacks on-path exposure of packet loss</a> (1 by mnot) <span class=3D"la=
bel" style=3D"background-color: #fbca04; color: #000000">-transport</span> =
</li>
 =20
  <li>#3159 <a href=3D"https://github.com/quicwg/base-drafts/issues/3159">S=
erver should not accept 1-RTT traffic before handshake completion</a> (1 by=
 mnot) <span class=3D"label" style=3D"background-color: #fbca04; color: #00=
0000">-tls</span> <span class=3D"label" style=3D"background-color: #1d76db;=
 color: #ffffff">design</span> </li>
 =20
  <li>#3111 <a href=3D"https://github.com/quicwg/base-drafts/issues/3111">[=
Version Ossification] Alternative version and Initial Salt should be part o=
f NEW_TOKEN</a> (1 by mnot) <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>
 =20
  <li>#3102 <a href=3D"https://github.com/quicwg/base-drafts/issues/3102">A=
dd provisional registration for all registries</a> (1 by MikeBishop) <span =
class=3D"label" style=3D"background-color: #fbca04; color: #000000">-http</=
span> <span class=3D"label" style=3D"background-color: #fbca04; color: #000=
000">-transport</span> </li>
 =20
  <li>#3094 <a href=3D"https://github.com/quicwg/base-drafts/issues/3094">c=
ongestion window increase on every ACKed packet could result in bursty send=
s</a> (3 by gorryfair, ianswett, pravb) <span class=3D"label" style=3D"back=
ground-color: #fbca04; color: #000000">-recovery</span> <span class=3D"labe=
l" style=3D"background-color: #1d76db; color: #ffffff">design</span> </li>
 =20
  <li>#3014 <a href=3D"https://github.com/quicwg/base-drafts/issues/3014">H=
andling of corrupt Retry packets</a> (2 by DavidSchinazi, martinthomson) <s=
pan class=3D"label" style=3D"background-color: #fbca04; color: #000000">-tr=
ansport</span> <span class=3D"label" style=3D"background-color: #1d76db; co=
lor: #ffffff">design</span> <span class=3D"label" style=3D"background-color=
: #c5def5; color: #000000">proposal-ready</span> </li>
 =20
  <li>#2863 <a href=3D"https://github.com/quicwg/base-drafts/issues/2863">u=
nrecoverable loss pattern leads to deadlock</a> (1 by mnot) <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>
 =20
  <li>#2792 <a href=3D"https://github.com/quicwg/base-drafts/issues/2792">T=
iming side-channel on key updates</a> (1 by mnot) <span class=3D"label" sty=
le=3D"background-color: #fbca04; color: #000000">-tls</span> <span class=3D=
"label" style=3D"background-color: #1d76db; color: #ffffff">design</span> <=
/li>
 =20
  <li>#2744 <a href=3D"https://github.com/quicwg/base-drafts/issues/2744">I=
dle Timer Can Fire Even with Outstanding Data to Send</a> (1 by janaiyengar=
) <span class=3D"label" style=3D"background-color: #fbca04; color: #000000"=
>-transport</span> </li>
 =20
  <li>#2496 <a href=3D"https://github.com/quicwg/base-drafts/issues/2496">Q=
UIC Version Ossification</a> (1 by mnot) <span class=3D"label" style=3D"bac=
kground-color: #fbca04; color: #000000">-transport</span> <span class=3D"la=
bel" style=3D"background-color: #1d76db; color: #ffffff">design</span> </li>
 =20
  <li>#1978 <a href=3D"https://github.com/quicwg/base-drafts/issues/1978">S=
ender-Controlled Delayed ACK Ratio</a> (1 by c-taylor) <span class=3D"label=
" style=3D"background-color: #fbca04; color: #000000">-recovery</span> <spa=
n class=3D"label" style=3D"background-color: #fbca04; color: #000000">-tran=
sport</span> <span class=3D"label" style=3D"background-color: #1d76db; colo=
r: #ffffff">design</span> <span class=3D"label" style=3D"background-color: =
#f9d0c4; color: #000000">parked</span> <span class=3D"label" style=3D"backg=
round-color: #8e64e0; color: #ffffff">quicv2</span> </li>
  </ul>

  <p>2 issues closed:</p>
  <ul>
  <li>#3268 <a href=3D"https://github.com/quicwg/base-drafts/issues/3268">P=
revent a connection from idle timing out while blocked</a> <span class=3D"l=
abel" style=3D"background-color: #fbca04; color: #000000">-transport</span>=
 </li>
 =20
  <li>#3189 <a href=3D"https://github.com/quicwg/base-drafts/issues/3189">Q=
UIC lacks on-path exposure of packet loss</a> <span class=3D"label" style=
=3D"background-color: #fbca04; color: #000000">-transport</span> </li>
  </ul>



<h2>Pull requests</h2>
<h3>quicwg/base-drafts (+4/-0/=F0=9F=92=AC12)</h3>
  <p class=3D"new">4 pull requests submitted:</p>
  <ul>
  <li>#3270 <a href=3D"https://github.com/quicwg/base-drafts/pull/3270">Dis=
abling Spin bit for what percentage of connections?</a> (by igorlord) </li>
 =20
  <li>#3267 <a href=3D"https://github.com/quicwg/base-drafts/pull/3267">TLS=
: fix references to registries</a> (by Lekensteyn) </li>
 =20
  <li>#3266 <a href=3D"https://github.com/quicwg/base-drafts/pull/3266">Pre=
vent Idle Timeout while Blocked</a> (by nibanks) </li>
 =20
  <li>#3263 <a href=3D"https://github.com/quicwg/base-drafts/pull/3263">Key=
 generation for updates MAY be deferred</a> (by martinthomson) <span class=
=3D"label" style=3D"background-color: #fbca04; color: #">-tls</span> <span =
class=3D"label" style=3D"background-color: #1d76db; color: #">design</span>=
 </li>
  </ul>

  <p>7 pull requests received 12 new comments:</p>
  <ul>
  <li>#3266 <a href=3D"https://github.com/quicwg/base-drafts/pull/3266">Pre=
vent Idle Timeout while Blocked</a> (1 by martinthomson) <span class=3D"lab=
el" style=3D"background-color: #fbca04; color: #000000">-transport</span> <=
/li>
 =20
  <li>#3248 <a href=3D"https://github.com/quicwg/base-drafts/pull/3248">Fix=
 congestion control permissiveness</a> (1 by janaiyengar) <span class=3D"la=
bel" style=3D"background-color: #fbca04; color: #000000">-recovery</span> <=
/li>
 =20
  <li>#3232 <a href=3D"https://github.com/quicwg/base-drafts/pull/3232">Lim=
it CWND increase in slow start</a> (2 by goelvidhi, janaiyengar) <span clas=
s=3D"label" style=3D"background-color: #fbca04; color: #000000">-recovery</=
span> <span class=3D"label" style=3D"background-color: #1d76db; color: #fff=
fff">design</span> </li>
 =20
  <li>#3186 <a href=3D"https://github.com/quicwg/base-drafts/pull/3186">all=
ow CRYPTO_BUFFER_EXCEEDED when overflowing a CRYPTO frame</a> (2 by kazuho,=
 martinthomson) <span class=3D"label" style=3D"background-color: #fbca04; c=
olor: #000000">-transport</span> <span class=3D"label" style=3D"background-=
color: #1d76db; color: #ffffff">design</span> </li>
 =20
  <li>#3145 <a href=3D"https://github.com/quicwg/base-drafts/pull/3145">use=
 a HANDSHAKE_DONE frame to drive the handshake to confirmation</a> (1 by Ry=
anAtGoogle) <span class=3D"label" style=3D"background-color: #fbca04; color=
: #000000">-tls</span> <span class=3D"label" style=3D"background-color: #fb=
ca04; color: #000000">-transport</span> </li>
 =20
  <li>#3120 <a href=3D"https://github.com/quicwg/base-drafts/pull/3120">Add=
 retry integrity tag</a> (4 by DavidSchinazi, ekr, marten-seemann) <span cl=
ass=3D"label" style=3D"background-color: #fbca04; color: #000000">-tls</spa=
n> <span class=3D"label" style=3D"background-color: #fbca04; color: #000000=
">-transport</span> <span class=3D"label" style=3D"background-color: #1d76d=
b; color: #ffffff">design</span> </li>
 =20
  <li>#3099 <a href=3D"https://github.com/quicwg/base-drafts/pull/3099">Cha=
nge idle_timeout to max_idle_timeout</a> (1 by ianswett) <span class=3D"lab=
el" style=3D"background-color: #fbca04; color: #000000">-transport</span> <=
/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>

--===============2879749712625664066==--


From nobody Sun Nov 24 04:52:51 2019
Return-Path: <acm@research.att.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 6B1521200B3; Sun, 24 Nov 2019 04:52:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.498
X-Spam-Level: 
X-Spam-Status: No, score=-2.498 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_HELO_NONE=0.001, 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 wQ66iKY9Xi9z; Sun, 24 Nov 2019 04:52:42 -0800 (PST)
Received: from mx0a-00191d01.pphosted.com (mx0b-00191d01.pphosted.com [67.231.157.136]) (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 E456D120137; Sun, 24 Nov 2019 04:52:41 -0800 (PST)
Received: from pps.filterd (m0049463.ppops.net [127.0.0.1]) by m0049463.ppops.net-00191d01. (8.16.0.42/8.16.0.42) with SMTP id xAOCZAbU014999; Sun, 24 Nov 2019 07:52:23 -0500
Received: from tlpd255.enaf.dadc.sbc.com (sbcsmtp3.sbc.com [144.160.112.28]) by m0049463.ppops.net-00191d01. with ESMTP id 2wf219pdhm-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 24 Nov 2019 07:52:22 -0500
Received: from enaf.dadc.sbc.com (localhost [127.0.0.1]) by tlpd255.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id xAOCqLuW031242; Sun, 24 Nov 2019 06:52:21 -0600
Received: from zlp30494.vci.att.com (zlp30494.vci.att.com [135.46.181.159]) by tlpd255.enaf.dadc.sbc.com (8.14.5/8.14.5) with ESMTP id xAOCqFRF031135 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Sun, 24 Nov 2019 06:52:15 -0600
Received: from zlp30494.vci.att.com (zlp30494.vci.att.com [127.0.0.1]) by zlp30494.vci.att.com (Service) with ESMTP id 3A2EE4009E7D; Sun, 24 Nov 2019 12:52:15 +0000 (GMT)
Received: from clpi183.sldc.sbc.com (unknown [135.41.1.46]) by zlp30494.vci.att.com (Service) with ESMTP id 1452B4009E71; Sun, 24 Nov 2019 12:52:15 +0000 (GMT)
Received: from sldc.sbc.com (localhost [127.0.0.1]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id xAOCqEbV011077; Sun, 24 Nov 2019 06:52:14 -0600
Received: from mail-azure.research.att.com (mail-azure.research.att.com [135.207.255.18]) by clpi183.sldc.sbc.com (8.14.5/8.14.5) with ESMTP id xAOCq4FO010213; Sun, 24 Nov 2019 06:52:05 -0600
Received: from exchange.research.att.com (njbdcas1.research.att.com [135.197.255.61]) by mail-azure.research.att.com (Postfix) with ESMTP id 24548E12A2; Sun, 24 Nov 2019 07:50:53 -0500 (EST)
Received: from njmtexg5.research.att.com ([fe80::b09c:ff13:4487:78b6]) by njbdcas1.research.att.com ([fe80::8c6b:4b77:618f:9a01%11]) with mapi id 14.03.0468.000; Sun, 24 Nov 2019 07:52:03 -0500
From: "MORTON, ALFRED C (AL)" <acm@research.att.com>
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>
CC: "quic@ietf.org" <quic@ietf.org>, "tsvwg@ietf.org" <tsvwg@ietf.org>, "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>, Peter Gutmann <pgut001@cs.auckland.ac.nz>, tsvwg-chairs <tsvwg-chairs@ietf.org>, "opsawg@ietf.org" <opsawg@ietf.org>, "Joel M. Halpern" <jmh@joelhalpern.com>, "saag@ietf.org" <saag@ietf.org>
Subject: RE: [ippm] [OPSAWG] TSVWG WGLC: draft-ietf-tsvwg-transport-encrypt-08, closes 23 October 2019
Thread-Topic: [ippm] [OPSAWG] TSVWG WGLC: draft-ietf-tsvwg-transport-encrypt-08, closes 23 October 2019
Thread-Index: AQHVk8OXusCW74gvz0mDwZDg62wUHaeZ/saAgABcwdA=
Date: Sun, 24 Nov 2019 12:52:03 +0000
Message-ID: <4D7F4AD313D3FC43A053B309F97543CFA6F001FB@njmtexg5.research.att.com>
References: <CE03DB3D7B45C245BCA0D2432779493630766752@MX307CL04.corp.emc.com> <4460_1571933453_5DB1CD0D_4460_57_4_5AE9CCAA1B4A2248AB61B4C7F0AD5FB931F030A0@OPEXCAUBM44.corporate.adroot.infra.ftgroup> <1572918247420.10381@cs.auckland.ac.nz> <CABcZeBPy_39o37snzy8F6iyLQMg1aGkYbhy0A1N-PxFUmAmB0g@mail.gmail.com> <f2b1f803-b559-a166-8009-baff551bec5c@joelhalpern.com> <5df30dd2-6841-7140-43bf-8c1b9603653f@erg.abdn.ac.uk> <CAKcm_gM33z6njR1U5f8Lh3=cMzEnQQVWLVYui9zHHqz0kPc2Nw@mail.gmail.com>
In-Reply-To: <CAKcm_gM33z6njR1U5f8Lh3=cMzEnQQVWLVYui9zHHqz0kPc2Nw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [69.141.203.172]
Content-Type: multipart/alternative; boundary="_000_4D7F4AD313D3FC43A053B309F97543CFA6F001FBnjmtexg5researc_"
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:6.0.95,18.0.572 definitions=2019-11-23_06:2019-11-21,2019-11-23 signatures=0
X-Proofpoint-Spam-Details: rule=outbound_policy_notspam policy=outbound_policy score=0 phishscore=0 malwarescore=0 spamscore=0 bulkscore=0 impostorscore=0 priorityscore=1501 adultscore=0 mlxscore=0 clxscore=1011 mlxlogscore=999 suspectscore=0 lowpriorityscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.12.0-1910280000 definitions=main-1911240126
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/0TE4VN22i-YzjDKGvCmiuvlrw_A>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 24 Nov 2019 12:52:44 -0000

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

SGkgSWFuLCBHb3JyeSBhbmQgQ29saW4sDQoNCnBsZWFzZSBzZWUgYSBmZXcgaGFyZC1lYXJuZWQg
Y29tbWVudHMgYmVsb3csIG1hcmtlZCBbYWNtXSwNCg0KQWwNCg0KRnJvbTogaXBwbSBbbWFpbHRv
OmlwcG0tYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxmIE9mIElhbiBTd2V0dA0KU2VudDogU2F0
dXJkYXksIE5vdmVtYmVyIDIzLCAyMDE5IDg6NDggUE0NClRvOiBHb3JyeSBGYWlyaHVyc3QgPGdv
cnJ5QGVyZy5hYmRuLmFjLnVrPg0KQ2M6IHF1aWNAaWV0Zi5vcmc7IHRzdndnQGlldGYub3JnOyBJ
RVRGIElQUE0gV0cgKGlwcG1AaWV0Zi5vcmcpIDxpcHBtQGlldGYub3JnPjsgUGV0ZXIgR3V0bWFu
biA8cGd1dDAwMUBjcy5hdWNrbGFuZC5hYy5uej47IHRzdndnLWNoYWlycyA8dHN2d2ctY2hhaXJz
QGlldGYub3JnPjsgb3BzYXdnQGlldGYub3JnOyBKb2VsIE0uIEhhbHBlcm4gPGptaEBqb2VsaGFs
cGVybi5jb20+OyBzYWFnQGlldGYub3JnDQpTdWJqZWN0OiBSZTogW2lwcG1dIFtPUFNBV0ddIFRT
VldHIFdHTEM6IGRyYWZ0LWlldGYtdHN2d2ctdHJhbnNwb3J0LWVuY3J5cHQtMDgsIGNsb3NlcyAy
MyBPY3RvYmVyIDIwMTkNCg0KSSB0aGluayBpdCdzIG9rIHRvIHB1Ymxpc2ggYSBkb2N1bWVudCB3
aXRoIHRoZSBzdGF0ZWQgZ29hbHMsIGJ1dCBJIHRoaW5rIHRoaXMgbmVlZHMgdG8gYmUgZG9uZSB3
aXRoIGdyZWF0IGNhcmUgYW5kIHRoZSBjdXJyZW50IGRvY3VtZW50IGltcGxpZXMgc29tZSB2YWx1
ZSBqdWRnZW1lbnRzIGFuZCBpbXBsaWNhdGlvbnMgSSBkb24ndCB0aGluayBhcmUgZnVsbHkganVz
dGlmaWVkIGJ5IHRoZSBkb2N1bWVudC4gIEEgM3JkIGF1dGhvciB3aXRoIGEgc2xpZ2h0bHkgZGlm
ZmVyZW50IHBlcnNwZWN0aXZlIG1heSBoZWxwIGFjaGlldmUgdGhlIHJpZ2h0IGJhbGFuY2UuDQpb
YWNtXQ0KSXTigJlzIGEgZGlmZmljdWx0IGJ1dCB3b3J0aHdoaWxlIHRoaW5nIHRvIGFjaGlldmUg
TlBPViBvbiBhIGNvbnRyb3ZlcnNpYWwgdG9waWMuDQoNCklNTywgdGhpcyBjYW4gYmUgYXBwcm9h
Y2hlZCBieSBhc2tpbmcgYWxsIGNvbW1lbnRlcnMgdG8gcHJvdmlkZSB0ZXh0IGZvciB0aGUgbWVt
bw0Kb24gdGhlIHRvcGljIG9mIGludGVyZXN0LCB3aGljaCB3aWxsIHJldmVhbCB0aGVpciB2YWx1
ZSBqdWRnZW1lbnRzIGFuZCBvcGluaW9ucw0KZm9yIHRoZSByZXZpZXdpbmcgY29tbXVuaXR5LiBF
ZGl0aW5nIHByb2NlZWRzIGJ5IHRha2luZyBtYW55IFBPViBpbnRvIGFjY291bnQsDQppbiB0aGUg
Zm9ybSBvZiB0ZXh0IGNvbnRyaWJ1dGlvbnMgcmV2aXNlZCBtYW55IHRpbWVzLCBub3Qgb3Bpbmlv
biBvbmx5Lg0KDQo8c25pcCBsb3RzIG9mIHByZXZpb3VzIG1lc3NhZ2VzPg0KPj4gT24gTW9uLCBO
b3YgNCwgMjAxOSBhdCA1OjQ0IFBNIFBldGVyIEd1dG1hbm4NCj4+IDxwZ3V0MDAxQGNzLmF1Y2ts
YW5kLmFjLm56PG1haWx0bzpwZ3V0MDAxQGNzLmF1Y2tsYW5kLmFjLm56PiA8bWFpbHRvOnBndXQw
MDFAY3MuYXVja2xhbmQuYWMubno8bWFpbHRvOnBndXQwMDFAY3MuYXVja2xhbmQuYWMubno+Pj4g
d3JvdGU6DQo+Pg0KPj4gICAgIEkgYWN0dWFsbHkgdGhpbmsgaXQncyBhIHByZXR0eSBnb29kIHN1
bW1hcnksIGFuZCBkZWxpdmVycyBleGFjdGx5DQo+PiB3aGF0J3MNCj4+ICAgICBwcm9taXNlZCBp
biB0aGUgdGl0bGUuICBPVE9IIEkgY2FuIGFsc28gc2VlIHRoYXQgaXQncyBnb2luZyB0byBnZXQN
Cj4+ICAgICBiaWtlc2hlZGRlZA0KPj4gICAgIHRvIGRlYXRoLCBhbmQgd2lsbCBwcm9iYWJseSBu
ZXZlciBiZSBlZGl0YWJsZSBpbnRvIGEgZm9ybSB3aGVyZQ0KPj4gICAgIHBlb3BsZSB3b24ndA0K
Pj4gICAgIGNvbXBsYWluIGFib3V0IGl0IG5vIG1hdHRlciBob3cgbWFueSBjaGFuZ2VzIGFyZSBt
YWRlLg0KPj4gQWx0ZXJuYXRpdmVseSwgaXQnbGwNCj4+ICAgICBlbmQgdXAgd2F0ZXJlZCBkb3du
IHRvIGEgcG9pbnQgd2hlcmUgbm8tb25lIGNhbiBjb21wbGFpbiBhbnkgbW9yZQ0KPj4gICAgIGJ1
dCBpdCB3b24ndA0KPj4gICAgIHNheSBhbnl0aGluZyB0ZXJyaWJseSB1c2VmdWwgYnkgdGhlbi4N
Cj4+DQo+PiAgICAgUGVyaGFwcyBpdCBjb3VsZCBiZSBwdWJsaXNoZWQgYXMgaXMgd2l0aCBhIGNv
bW1lbnQgdGhhdCBpdA0KPj4gICAgIHJlcHJlc2VudHMgdGhlDQo+PiAgICAgb3BpbmlvbnMgb2Yg
dGhlIGF1dGhvcnM/ICBBbHRob3VnaCBnaXZlbiB0aGF0IGl0J3MgSW5mb3JtYXRpb25hbA0KPj4g
YW5kIG5vdA0KPj4gICAgIFN0YW5kYXJkcy10cmFjayBvciBhIEJDUCwgdGhhdCBzaG91bGQgYmUg
YSBnaXZlbiBhbnl3YXkuDQo+Pg0KPj4NCj4+IEFjdHVhbGx5LCBuby4gTW9zdCBJRVRGIGRvY3Vt
ZW50cywgZXZlbiBpbmZvcm1hdGlvbmFsIG9uZXMsIGJlYXIgYQ0KPj4gc3RhdGVtZW50IHRoYXQg
dGhleSBoYXZlIElFVEYgQ29uc2Vuc3VzLg0KPj4NCj4+IFNlZTogaHR0cHM6Ly90b29scy5pZXRm
Lm9yZy9odG1sL3JmYzU3NDEjc2VjdGlvbi0zLjIuMTxodHRwczovL3VybGRlZmVuc2UucHJvb2Zw
b2ludC5jb20vdjIvdXJsP3U9aHR0cHMtM0FfX3Rvb2xzLmlldGYub3JnX2h0bWxfcmZjNTc0MS0y
M3NlY3Rpb24tMkQzLjIuMSZkPUR3TUZhUSZjPUxGWVotbzlfSFVNZU1UU1FpY3ZqSWcmcj1PZnNT
dThrVElsdFZ5RDFvTDcyY0J3Jm09VDVMZ3NNQnpGT3M0S1JkaVdJeFg1cFpRN3hiV0FYZ3VMa0gz
Z1gxRFNyZyZzPWVIeTR3OGxWRjNfNVJWTmRpV1FhY1RYeElIOVF1MUNRMFVRNmJEN3lSME0mZT0+
DQo+PiA8aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzU3NDEjc2VjdGlvbi0zLi4yLjE8
aHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3VybD91PWh0dHBzLTNBX190b29s
cy5pZXRmLm9yZ19odG1sX3JmYzU3NDEtMjNzZWN0aW9uLTJEMy4uMi4xJmQ9RHdNRmFRJmM9TEZZ
Wi1vOV9IVU1lTVRTUWljdmpJZyZyPU9mc1N1OGtUSWx0VnlEMW9MNzJjQncmbT1UNUxnc01CekZP
czRLUmRpV0l4WDVwWlE3eGJXQVhndUxrSDNnWDFEU3JnJnM9Mm5qemZUYWJDSVRFRk9QNHlDbDJp
SVl4VUN1MGd1dGxOYXVHWWk4MU85QSZlPT4+DQo+Pg0KPj4gLUVrcg0KPj4NCj4+DQo+PiAgICAg
UGV0ZXIuDQpbYWNtXSBBY3R1YWxseSwgdGhpcyBpcyB0aGUgcmVsZXZhbnQgY2xhc3NpZmljYXRp
b246DQoNCjQuMi4yIEluZm9ybWF0aW9uYWwNCg0KQW4gIkluZm9ybWF0aW9uYWwiIHNwZWNpZmlj
YXRpb24gaXMgcHVibGlzaGVkIGZvciB0aGUgZ2VuZXJhbCBpbmZvcm1hdGlvbiBvZiB0aGUgSW50
ZXJuZXQgY29tbXVuaXR5LCBhbmQgZG9lcyBub3QgcmVwcmVzZW50IGFuIEludGVybmV0IGNvbW11
bml0eSBjb25zZW5zdXMgb3IgcmVjb21tZW5kYXRpb24uDQpGcm9tIGh0dHBzOi8vaWV0Zi5vcmcv
c3RhbmRhcmRzL3Byb2Nlc3MvaW5mb3JtYXRpb25hbC12cy1leHBlcmltZW50YWwvDQpDaG9vc2lu
ZyBiZXR3ZWVuIEluZm9ybWF0aW9uYWwgYW5kIEV4cGVyaW1lbnRhbCBTdGF0dXMNClRoaXMgZG9j
dW1lbnQgcmVwcm9kdWNlcyB0aGUgcnVsZXMgZm9yIGNsYXNzaWZ5aW5nIGRvY3VtZW50cyBhcyBJ
bmZvcm1hdGlvbmFsIGFuZCBFeHBlcmltZW50YWwgZnJvbSBSRkMgMjAyNiwgYW5kIGFtcGxpZmll
cyB0aG9zZSBydWxlcyB3aXRoIGd1aWRlbGluZXMgcmVsZXZhbnQgdG8gb25nb2luZyBJRVNHIGV2
YWx1YXRpb25zLiBJdCBpcyBub3QgaW50ZW5kZWQgdG8gY2hhbmdlIGFueSBvZiB0aGUgdW5kZXJs
eWluZyBwcmluY2lwbGVzLg0KYW5kIGl04oCZcyBhIGTDqWrDoCB2dSBtb21lbnQgZm9yIG1lLg0K
DQo+Pg0KPj4NCj4+DQo+Pg0KPj4gX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX18NCj4+IE9QU0FXRyBtYWlsaW5nIGxpc3QNCj4+IE9QU0FXR0BpZXRmLm9yZzxt
YWlsdG86T1BTQVdHQGlldGYub3JnPg0KPj4gaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9s
aXN0aW5mby9vcHNhd2c8aHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3VybD91
PWh0dHBzLTNBX193d3cuaWV0Zi5vcmdfbWFpbG1hbl9saXN0aW5mb19vcHNhd2cmZD1Ed01GYVEm
Yz1MRllaLW85X0hVTWVNVFNRaWN2aklnJnI9T2ZzU3U4a1RJbHRWeUQxb0w3MmNCdyZtPVQ1TGdz
TUJ6Rk9zNEtSZGlXSXhYNXBaUTd4YldBWGd1TGtIM2dYMURTcmcmcz1MRlB6ZFZwRUxNd2VFNUp6
aFNsZi1NQ2ktMV9UZlVHd3ZqWGVTQjFPVDg0JmU9Pg0KPj4NCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQpoMQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTsNCgltc28tc3R5bGUtbGluazoiSGVhZGluZyAx
IENoYXIiOw0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdpbi1yaWdodDowaW47DQoJ
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6MGluOw0KCWZvbnQtc2l6
ZToyNC4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIsc2VyaWY7DQoJZm9udC13
ZWlnaHQ6Ym9sZDt9DQphOmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlv
cml0eTo5OTsNCgljb2xvcjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KYTp2
aXNpdGVkLCBzcGFuLk1zb0h5cGVybGlua0ZvbGxvd2VkDQoJe21zby1zdHlsZS1wcmlvcml0eTo5
OTsNCgljb2xvcjpwdXJwbGU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwDQoJe21z
by1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzsNCgltYXJnaW4t
cmlnaHQ6MGluOw0KCW1zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvOw0KCW1hcmdpbi1sZWZ0OjBp
bjsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcgUm9tYW4iLHNl
cmlmO30NCnNwYW4uRW1haWxTdHlsZTE3DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5
Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7DQoJY29sb3I6YmxhY2s7fQ0Kc3Bhbi5IZWFk
aW5nMUNoYXINCgl7bXNvLXN0eWxlLW5hbWU6IkhlYWRpbmcgMSBDaGFyIjsNCgltc28tc3R5bGUt
cHJpb3JpdHk6OTsNCgltc28tc3R5bGUtbGluazoiSGVhZGluZyAxIjsNCglmb250LWZhbWlseToi
VGltZXMgTmV3IFJvbWFuIixzZXJpZjsNCglmb250LXdlaWdodDpib2xkO30NCnAuaW50cm8sIGxp
LmludHJvLCBkaXYuaW50cm8NCgl7bXNvLXN0eWxlLW5hbWU6aW50cm87DQoJbXNvLW1hcmdpbi10
b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0OjBpbjsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0bzsNCgltYXJnaW4tbGVmdDowaW47DQoJZm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWls
eToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUt
dHlwZTpleHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpA
cGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEu
MGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7
fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMg
djpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lm
IGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFw
IHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlm
XS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJw
bGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3
JnF1b3Q7O2NvbG9yOmJsYWNrIj5IaSBJYW4sIEdvcnJ5IGFuZCBDb2xpbiw8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjEx
LjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86
cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5
bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7
Y29sb3I6YmxhY2siPnBsZWFzZSBzZWUgYSBmZXcgaGFyZC1lYXJuZWQgY29tbWVudHMgYmVsb3cs
IG1hcmtlZCBbYWNtXSw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVy
IE5ldyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1p
bHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPkFsPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGEgbmFtZT0iX01haWxFbmRDb21wb3NlIj48
c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5l
dyZxdW90Oztjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9hPjwvcD4NCjxk
aXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkIGJsdWUgMS41cHQ7cGFkZGlu
ZzowaW4gMGluIDBpbiA0LjBwdCI+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9y
ZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9u
dC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZxdW90OyxzYW5zLXNlcmlmIj5Gcm9tOjwvc3Bhbj48L2I+
PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6JnF1b3Q7Q2FsaWJyaSZx
dW90OyxzYW5zLXNlcmlmIj4gaXBwbSBbbWFpbHRvOmlwcG0tYm91bmNlc0BpZXRmLm9yZ10NCjxi
Pk9uIEJlaGFsZiBPZiA8L2I+SWFuIFN3ZXR0PGJyPg0KPGI+U2VudDo8L2I+IFNhdHVyZGF5LCBO
b3ZlbWJlciAyMywgMjAxOSA4OjQ4IFBNPGJyPg0KPGI+VG86PC9iPiBHb3JyeSBGYWlyaHVyc3Qg
Jmx0O2dvcnJ5QGVyZy5hYmRuLmFjLnVrJmd0Ozxicj4NCjxiPkNjOjwvYj4gcXVpY0BpZXRmLm9y
ZzsgdHN2d2dAaWV0Zi5vcmc7IElFVEYgSVBQTSBXRyAoaXBwbUBpZXRmLm9yZykgJmx0O2lwcG1A
aWV0Zi5vcmcmZ3Q7OyBQZXRlciBHdXRtYW5uICZsdDtwZ3V0MDAxQGNzLmF1Y2tsYW5kLmFjLm56
Jmd0OzsgdHN2d2ctY2hhaXJzICZsdDt0c3Z3Zy1jaGFpcnNAaWV0Zi5vcmcmZ3Q7OyBvcHNhd2dA
aWV0Zi5vcmc7IEpvZWwgTS4gSGFscGVybiAmbHQ7am1oQGpvZWxoYWxwZXJuLmNvbSZndDs7IHNh
YWdAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFtpcHBtXSBbT1BTQVdHXSBUU1ZX
RyBXR0xDOiBkcmFmdC1pZXRmLXRzdndnLXRyYW5zcG9ydC1lbmNyeXB0LTA4LCBjbG9zZXMgMjMg
T2N0b2JlciAyMDE5PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj5JIHRoaW5rIGl0J3Mgb2sgdG8gcHVibGlzaCBhIGRvY3VtZW50IHdp
dGggdGhlIHN0YXRlZCBnb2FscywgYnV0IEkgdGhpbmsgdGhpcyBuZWVkcyB0byBiZSBkb25lIHdp
dGggZ3JlYXQgY2FyZSBhbmQgdGhlIGN1cnJlbnQgZG9jdW1lbnQgaW1wbGllcyBzb21lIHZhbHVl
IGp1ZGdlbWVudHMgYW5kIGltcGxpY2F0aW9ucyBJIGRvbid0IHRoaW5rIGFyZSBmdWxseSBqdXN0
aWZpZWQgYnkgdGhlIGRvY3VtZW50LiZuYnNwOyBBDQogM3JkIGF1dGhvciB3aXRoIGEgc2xpZ2h0
bHkgZGlmZmVyZW50IHBlcnNwZWN0aXZlIG1heSBoZWxwIGFjaGlldmUgdGhlIHJpZ2h0IGJhbGFu
Y2UuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj48aT48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztj
b2xvcjpibGFjayI+W2FjbV0NCjxvOnA+PC9vOnA+PC9zcGFuPjwvaT48L2I+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7Zm9udC1mYW1pbHk6
JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPkl04oCZcyBhIGRpZmZpY3VsdCBi
dXQgd29ydGh3aGlsZSB0aGluZyB0byBhY2hpZXZlIE5QT1Ygb24gYSBjb250cm92ZXJzaWFsIHRv
cGljLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7
O2NvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtD
b3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+SU1PLCB0aGlzIGNhbiBiZSBhcHByb2FjaGVk
IGJ5IGFza2luZyBhbGwgY29tbWVudGVycyB0byBwcm92aWRlIHRleHQgZm9yIHRoZSBtZW1vDQo8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
Zm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xv
cjpibGFjayI+b24gdGhlIHRvcGljIG9mIGludGVyZXN0LCB3aGljaCB3aWxsIHJldmVhbCB0aGVp
ciB2YWx1ZSBqdWRnZW1lbnRzIGFuZCBvcGluaW9uczxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFt
aWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5mb3IgdGhlIHJldmlld2lu
ZyBjb21tdW5pdHkuIEVkaXRpbmcgcHJvY2VlZHMgYnkgdGFraW5nIG1hbnkgUE9WIGludG8gYWNj
b3VudCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90
Oztjb2xvcjpibGFjayI+aW4gdGhlIGZvcm0gb2YgdGV4dCBjb250cmlidXRpb25zIHJldmlzZWQg
bWFueSB0aW1lcywgbm90IG9waW5pb24gb25seS48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPC9kaXY+DQo8ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRl
ci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJn
aW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj4mbHQ7
c25pcCBsb3RzIG9mIHByZXZpb3VzIG1lc3NhZ2VzJmd0OzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+Jmd0OyZn
dDsgT24gTW9uLCBOb3YgNCwgMjAxOSBhdCA1OjQ0IFBNIFBldGVyIEd1dG1hbm4NCjxicj4NCiZn
dDsmZ3Q7ICZsdDs8YSBocmVmPSJtYWlsdG86cGd1dDAwMUBjcy5hdWNrbGFuZC5hYy5ueiIgdGFy
Z2V0PSJfYmxhbmsiPnBndXQwMDFAY3MuYXVja2xhbmQuYWMubno8L2E+ICZsdDttYWlsdG86PGEg
aHJlZj0ibWFpbHRvOnBndXQwMDFAY3MuYXVja2xhbmQuYWMubnoiIHRhcmdldD0iX2JsYW5rIj5w
Z3V0MDAxQGNzLmF1Y2tsYW5kLmFjLm56PC9hPiZndDsmZ3Q7IHdyb3RlOjxicj4NCiZndDsmZ3Q7
PGJyPg0KJmd0OyZndDsgJm5ic3A7Jm5ic3A7Jm5ic3A7IEkgYWN0dWFsbHkgdGhpbmsgaXQncyBh
IHByZXR0eSBnb29kIHN1bW1hcnksIGFuZCBkZWxpdmVycyBleGFjdGx5IDxicj4NCiZndDsmZ3Q7
IHdoYXQnczxicj4NCiZndDsmZ3Q7ICZuYnNwOyZuYnNwOyZuYnNwOyBwcm9taXNlZCBpbiB0aGUg
dGl0bGUuJm5ic3A7IE9UT0ggSSBjYW4gYWxzbyBzZWUgdGhhdCBpdCdzIGdvaW5nIHRvIGdldDxi
cj4NCiZndDsmZ3Q7ICZuYnNwOyZuYnNwOyZuYnNwOyBiaWtlc2hlZGRlZDxicj4NCiZndDsmZ3Q7
ICZuYnNwOyZuYnNwOyZuYnNwOyB0byBkZWF0aCwgYW5kIHdpbGwgcHJvYmFibHkgbmV2ZXIgYmUg
ZWRpdGFibGUgaW50byBhIGZvcm0gd2hlcmU8YnI+DQomZ3Q7Jmd0OyAmbmJzcDsmbmJzcDsmbmJz
cDsgcGVvcGxlIHdvbid0PGJyPg0KJmd0OyZndDsgJm5ic3A7Jm5ic3A7Jm5ic3A7IGNvbXBsYWlu
IGFib3V0IGl0IG5vIG1hdHRlciBob3cgbWFueSBjaGFuZ2VzIGFyZSBtYWRlLiA8YnI+DQomZ3Q7
Jmd0OyBBbHRlcm5hdGl2ZWx5LCBpdCdsbDxicj4NCiZndDsmZ3Q7ICZuYnNwOyZuYnNwOyZuYnNw
OyBlbmQgdXAgd2F0ZXJlZCBkb3duIHRvIGEgcG9pbnQgd2hlcmUgbm8tb25lIGNhbiBjb21wbGFp
biBhbnkgbW9yZTxicj4NCiZndDsmZ3Q7ICZuYnNwOyZuYnNwOyZuYnNwOyBidXQgaXQgd29uJ3Q8
YnI+DQomZ3Q7Jmd0OyAmbmJzcDsmbmJzcDsmbmJzcDsgc2F5IGFueXRoaW5nIHRlcnJpYmx5IHVz
ZWZ1bCBieSB0aGVuLjxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDsgJm5ic3A7Jm5ic3A7Jm5i
c3A7IFBlcmhhcHMgaXQgY291bGQgYmUgcHVibGlzaGVkIGFzIGlzIHdpdGggYSBjb21tZW50IHRo
YXQgaXQ8YnI+DQomZ3Q7Jmd0OyAmbmJzcDsmbmJzcDsmbmJzcDsgcmVwcmVzZW50cyB0aGU8YnI+
DQomZ3Q7Jmd0OyAmbmJzcDsmbmJzcDsmbmJzcDsgb3BpbmlvbnMgb2YgdGhlIGF1dGhvcnM/Jm5i
c3A7IEFsdGhvdWdoIGdpdmVuIHRoYXQgaXQncyBJbmZvcm1hdGlvbmFsIDxicj4NCiZndDsmZ3Q7
IGFuZCBub3Q8YnI+DQomZ3Q7Jmd0OyAmbmJzcDsmbmJzcDsmbmJzcDsgU3RhbmRhcmRzLXRyYWNr
IG9yIGEgQkNQLCB0aGF0IHNob3VsZCBiZSBhIGdpdmVuIGFueXdheS48YnI+DQomZ3Q7Jmd0Ozxi
cj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDsgQWN0dWFsbHksIG5vLiBNb3N0IElFVEYgZG9jdW1l
bnRzLCBldmVuIGluZm9ybWF0aW9uYWwgb25lcywgYmVhciBhIDxicj4NCiZndDsmZ3Q7IHN0YXRl
bWVudCB0aGF0IHRoZXkgaGF2ZSBJRVRGIENvbnNlbnN1cy48YnI+DQomZ3Q7Jmd0Ozxicj4NCiZn
dDsmZ3Q7IFNlZTogPGEgaHJlZj0iaHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3Yy
L3VybD91PWh0dHBzLTNBX190b29scy5pZXRmLm9yZ19odG1sX3JmYzU3NDEtMjNzZWN0aW9uLTJE
My4yLjEmYW1wO2Q9RHdNRmFRJmFtcDtjPUxGWVotbzlfSFVNZU1UU1FpY3ZqSWcmYW1wO3I9T2Zz
U3U4a1RJbHRWeUQxb0w3MmNCdyZhbXA7bT1UNUxnc01CekZPczRLUmRpV0l4WDVwWlE3eGJXQVhn
dUxrSDNnWDFEU3JnJmFtcDtzPWVIeTR3OGxWRjNfNVJWTmRpV1FhY1RYeElIOVF1MUNRMFVRNmJE
N3lSME0mYW1wO2U9IiB0YXJnZXQ9Il9ibGFuayI+DQpodHRwczovL3Rvb2xzLmlldGYub3JnL2h0
bWwvcmZjNTc0MSNzZWN0aW9uLTMuMi4xPC9hPiA8YnI+DQomZ3Q7Jmd0OyAmbHQ7PGEgaHJlZj0i
aHR0cHM6Ly91cmxkZWZlbnNlLnByb29mcG9pbnQuY29tL3YyL3VybD91PWh0dHBzLTNBX190b29s
cy5pZXRmLm9yZ19odG1sX3JmYzU3NDEtMjNzZWN0aW9uLTJEMy4uMi4xJmFtcDtkPUR3TUZhUSZh
bXA7Yz1MRllaLW85X0hVTWVNVFNRaWN2aklnJmFtcDtyPU9mc1N1OGtUSWx0VnlEMW9MNzJjQncm
YW1wO209VDVMZ3NNQnpGT3M0S1JkaVdJeFg1cFpRN3hiV0FYZ3VMa0gzZ1gxRFNyZyZhbXA7cz0y
bmp6ZlRhYkNJVEVGT1A0eUNsMmlJWXhVQ3UwZ3V0bE5hdUdZaTgxTzlBJmFtcDtlPSIgdGFyZ2V0
PSJfYmxhbmsiPmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9yZmM1NzQxI3NlY3Rpb24tMy4u
Mi4xPC9hPiZndDs8YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7IC1Fa3I8YnI+DQomZ3Q7Jmd0
Ozxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDsgJm5ic3A7Jm5ic3A7Jm5ic3A7IFBldGVyLjxz
cGFuIHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48Yj48aT48c3BhbiBzdHls
ZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztj
b2xvcjpibGFjayI+W2FjbV0NCjwvc3Bhbj48L2k+PC9iPjxzcGFuIHN0eWxlPSJmb250LXNpemU6
MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7O2NvbG9yOmJsYWNrIj5B
Y3R1YWxseSwgdGhpcyBpcyB0aGUgcmVsZXZhbnQgY2xhc3NpZmljYXRpb246PG86cD48L286cD48
L3NwYW4+PC9wPg0KPHA+PGI+NC4yLjIgSW5mb3JtYXRpb25hbDwvYj48bzpwPjwvbzpwPjwvcD4N
CjxwPkFuICZxdW90O0luZm9ybWF0aW9uYWwmcXVvdDsgc3BlY2lmaWNhdGlvbiBpcyBwdWJsaXNo
ZWQgZm9yIHRoZSBnZW5lcmFsIGluZm9ybWF0aW9uIG9mIHRoZSBJbnRlcm5ldCBjb21tdW5pdHks
IGFuZCBkb2VzIG5vdCByZXByZXNlbnQgYW4gSW50ZXJuZXQgY29tbXVuaXR5IGNvbnNlbnN1cyBv
ciByZWNvbW1lbmRhdGlvbi48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PHNwYW4gc3R5bGU9ImZvbnQtc2l6ZToxMS4wcHQ7
Zm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcmcXVvdDs7Y29sb3I6YmxhY2siPkZyb20NCjxh
IGhyZWY9Imh0dHBzOi8vaWV0Zi5vcmcvc3RhbmRhcmRzL3Byb2Nlc3MvaW5mb3JtYXRpb25hbC12
cy1leHBlcmltZW50YWwvIj5odHRwczovL2lldGYub3JnL3N0YW5kYXJkcy9wcm9jZXNzL2luZm9y
bWF0aW9uYWwtdnMtZXhwZXJpbWVudGFsLzwvYT48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdp
bi1ib3R0b20tYWx0OmF1dG8iPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTguMHB0Ij5DaG9v
c2luZyBiZXR3ZWVuIEluZm9ybWF0aW9uYWwgYW5kIEV4cGVyaW1lbnRhbCBTdGF0dXM8bzpwPjwv
bzpwPjwvc3Bhbj48L2I+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5UaGlzIGRvY3VtZW50
IHJlcHJvZHVjZXMgdGhlIHJ1bGVzIGZvciBjbGFzc2lmeWluZyBkb2N1bWVudHMgYXMgSW5mb3Jt
YXRpb25hbCBhbmQgRXhwZXJpbWVudGFsIGZyb20gUkZDIDIwMjYsIGFuZCBhbXBsaWZpZXMgdGhv
c2UgcnVsZXMgd2l0aCBndWlkZWxpbmVzIHJlbGV2YW50IHRvIG9uZ29pbmcgSUVTRw0KIGV2YWx1
YXRpb25zLiBJdCBpcyBub3QgaW50ZW5kZWQgdG8gY2hhbmdlIGFueSBvZiB0aGUgdW5kZXJseWlu
ZyBwcmluY2lwbGVzLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1hcmdpbi1ib3R0b206MTIuMHB0Ij48c3BhbiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250
LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90Oztjb2xvcjpibGFjayI+YW5kIGl04oCZcyBh
IGTDqWrDoCB2dSBtb21lbnQgZm9yIG1lLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9tOjEyLjBwdCI+PGJyPg0KJmd0OyZndDs8
YnI+DQomZ3Q7Jmd0Ozxicj4NCiZndDsmZ3Q7PGJyPg0KJmd0OyZndDs8YnI+DQomZ3Q7Jmd0OyBf
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fXzxicj4NCiZndDsm
Z3Q7IE9QU0FXRyBtYWlsaW5nIGxpc3Q8YnI+DQomZ3Q7Jmd0OyA8YSBocmVmPSJtYWlsdG86T1BT
QVdHQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+T1BTQVdHQGlldGYub3JnPC9hPjxicj4NCiZn
dDsmZ3Q7IDxhIGhyZWY9Imh0dHBzOi8vdXJsZGVmZW5zZS5wcm9vZnBvaW50LmNvbS92Mi91cmw/
dT1odHRwcy0zQV9fd3d3LmlldGYub3JnX21haWxtYW5fbGlzdGluZm9fb3BzYXdnJmFtcDtkPUR3
TUZhUSZhbXA7Yz1MRllaLW85X0hVTWVNVFNRaWN2aklnJmFtcDtyPU9mc1N1OGtUSWx0VnlEMW9M
NzJjQncmYW1wO209VDVMZ3NNQnpGT3M0S1JkaVdJeFg1cFpRN3hiV0FYZ3VMa0gzZ1gxRFNyZyZh
bXA7cz1MRlB6ZFZwRUxNd2VFNUp6aFNsZi1NQ2ktMV9UZlVHd3ZqWGVTQjFPVDg0JmFtcDtlPSIg
dGFyZ2V0PSJfYmxhbmsiPg0KaHR0cHM6Ly93d3cuaWV0Zi5vcmcvbWFpbG1hbi9saXN0aW5mby9v
cHNhd2c8L2E+PGJyPg0KJmd0OyZndDs8bzpwPjwvbzpwPjwvcD4NCjwvYmxvY2txdW90ZT4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_4D7F4AD313D3FC43A053B309F97543CFA6F001FBnjmtexg5researc_--


From nobody Sun Nov 24 19:34:22 2019
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 4178D1201EF for <quic@ietfa.amsl.com>; Sun, 24 Nov 2019 19:34:21 -0800 (PST)
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=dRrLDKVr; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=kvE8drHL
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 YY8tim56dnjq for <quic@ietfa.amsl.com>; Sun, 24 Nov 2019 19:34:18 -0800 (PST)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id B70A912020A for <quic@ietf.org>; Sun, 24 Nov 2019 19:34:18 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id BA2AE565; Sun, 24 Nov 2019 22:34:17 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Sun, 24 Nov 2019 22:34:17 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=from :content-type:content-transfer-encoding:mime-version:subject :message-id:date:cc:to; s=fm1; bh=nM0VWDZq0CN/raj4WkRDw/SDoxbl0N ASuhSMKg67fLQ=; b=dRrLDKVrfrCUO05kE6UobIbjHHcQm27Lnu9s+648DaBpKp wsqRCMQs6JwP7HMzdBCRwRVW9SKgxCsE2WNPV+y6k1jO5TS/49X6fHGBnoZEJiCY ww5dgAdQnLsT5S2Tk90Y3/AyapRUrZE65FVy2HH32BRNSg28KKwfZxn2nquTFDbD kr8yCKr3urWZ6hxChKhAkLUBqlkA3gBJDqU8EedBI1HpkTVgk+Pfpy3eNDs3BbNg 2PXqHpxFzTi6r3VGKlH5RKeLgbW4hKzSsjUc7i4vuHQ4Hegsj4gOSfhcW6qTLhqq pUUDzczPfdi/+rCAHqF1dXNmLmsmomoufCd3W7kA==
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-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=nM0VWD Zq0CN/raj4WkRDw/SDoxbl0NASuhSMKg67fLQ=; b=kvE8drHLJqoIwl0Bm79W74 KLiITE/45qOQ9TBBgL4EtQuLJRWOi7015UuaSFKprc+yDyqbMjNAK1QDT6rvzTZ4 n0tVSOy6ux7Xoa/hc0iOlRfNOROF0PtnUCXGg30puBJtpHqDbQ7LWBX3xQo3sMja aq/HtrjFQavClMOOHdfgb6WCNi4AgkSnufcKlZHJNVAB5U4oR3yKM+y8/WaXzdAF R5L1B3QS7CwbKEVdT3BF0Ldx/KLtAx7C4kJUYIqiWSbevgin7v7KMuhAgFNf+IGi BplsRyv5tmEyW2g4IhX/+1z+GEUayFoCd2FvS4J5J3x4BDA5uuJgQ7FyPGeN8kgA ==
X-ME-Sender: <xms:uEvbXXj_JyQfqDpXHikziHfE3rllOr7rkJ1cekpdtaXOnhj9XIq_bQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudeitdcutefuodetggdotefrodftvfcurf hrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecuuegr ihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenucfjug hrpefhtgfgggfukfffvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghrkhcupfhothht ihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuffhomhgrihhnpehgihhthh husgdrtghomhdpmhhnohhtrdhnvghtnecukfhppeduudelrddujedrudehkedrvdehuden ucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnhhothdrnhgvthenucevlhhush htvghrufhiiigvpedt
X-ME-Proxy: <xmx:uEvbXdoZeWMmSb3e40vqsVjC-hifJa2UsXw6B0RmUavN1Did8l5mCg> <xmx:uEvbXahFJzWPFGTihs1bC9puVPl2guRilCLKO62XhiDiK4Vm2rHdyQ> <xmx:uEvbXbJ4NT9ond6dd9C5kGj0uE7N5CSlpgnwNQIAgw-geMAhcPnrEw> <xmx:uUvbXQGKlmRD_UKorMmTncrz61Gca3hxE-5zsuhe28FLHFjoFzYOvA>
Received: from attitudadjuster.mnot.net (unknown [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id 4604B3060060; Sun, 24 Nov 2019 22:34:15 -0500 (EST)
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 13.0 \(3601.0.10\))
Subject: DRAFT minutes from Singapore
Message-Id: <C773EAD0-846A-4B45-93D8-5F3A3D681020@mnot.net>
Date: Mon, 25 Nov 2019 14:34:11 +1100
Cc: Lars Eggert <lars@eggert.org>
To: IETF QUIC WG <quic@ietf.org>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/txLIs2ecS1VKInFGo4rX5CgCzhc>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 25 Nov 2019 03:34:21 -0000

... are available at:
  https://github.com/quicwg/wg-materials/blob/master/ietf106/minutes.md

As always, thanks to our scribes. Corrections and suggestions welcome as =
Pull Requests (preferred), or via e-mail.

Regards,

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


From nobody Mon Nov 25 06:13:19 2019
Return-Path: <Nicolas.Kuhn@cnes.fr>
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 6FBA3120880; Mon, 25 Nov 2019 06:13:09 -0800 (PST)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 SMR8yO7U6Ku4; Mon, 25 Nov 2019 06:13:06 -0800 (PST)
Received: from mx2.cnes.fr (mx2.cnes.fr [194.199.174.201]) (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 3F7DD120960; Mon, 25 Nov 2019 06:13:06 -0800 (PST)
X-IronPort-AV: E=Sophos; i="5.69,241,1571702400"; d="scan'208,217"; a="31098712"
X-IPAS-Result: =?us-ascii?q?A2EjBQCX4Ntd/wIBeAplHAEBAQEBBwEBEQEEBAEBgX6BH?= =?us-ascii?q?IEEWRN1EioKlTiBAYI8j2WIAwgJAQEBAQEBAQEBIAEKCQECAQGDe0UCgi8kO?= =?us-ascii?q?BMCEAEBAQQBAQEBAQUCAQECAmmEa0wMhigCAQMBAStBCxACAQUDDRUCGwcnC?= =?us-ascii?q?xQRAQEEAQ0FCBODCIF5fg+yHhqKMQaBNoFlihSCNoERR4FOSQcuPoJkAQGBZ?= =?us-ascii?q?TSDDIIsBI1XiAWBBJdSB4E8coI4ikGIdnWBSodqhCsDhweEPo5InCEjKoEuM?= =?us-ascii?q?xonTIJsUBFqhX4XiGSFP0QwgSAIjBYBgQ4BAQ?=
X-URL-LookUp-ScanningError: 1
From: Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>
To: "'etosat@ietf.org'" <etosat@ietf.org>, 'IETF QUIC WG' <quic@ietf.org>, "'nwcrg@irtf.org'" <nwcrg@irtf.org>
CC: 'G Fairhurst' <gorry@erg.abdn.ac.uk>, 'STEPHAN Emile RD-CORE-LAN' <emile.stephan@orange.com>
Subject: RE: Side meeting on QUIC performance over high BDP networks
Thread-Topic: Side meeting on QUIC performance over high BDP networks
Thread-Index: AdWfSmKmhf9YofXhT8ubjjpspqEzKwETv5vQ
Date: Mon, 25 Nov 2019 14:12:01 +0000
Deferred-Delivery: Mon, 25 Nov 2019 14:13:01 +0000
Message-ID: <F3B0A07CFD358240926B78A680E166FF1ED06AF0@TW-MBX-P03.cnesnet.ad.cnes.fr>
References: <F3B0A07CFD358240926B78A680E166FF1ED02F8B@TW-MBX-P03.cnesnet.ad.cnes.fr>
In-Reply-To: <F3B0A07CFD358240926B78A680E166FF1ED02F8B@TW-MBX-P03.cnesnet.ad.cnes.fr>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-tm-as-product-ver: SMEX-11.0.0.4255-8.100.1062-25064.007
x-tm-as-result: No--27.270900-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_F3B0A07CFD358240926B78A680E166FF1ED06AF0TWMBXP03cnesnet_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/suZ1ZI7thQy8ERSTwpgzYzHpPXs>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 25 Nov 2019 14:13:10 -0000

--_000_F3B0A07CFD358240926B78A680E166FF1ED06AF0TWMBXP03cnesnet_
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,

Thank you all for coming to the "QUIC for high BDP" side-meeting.
We hope you found it positive and useful - at least, we did and have plans =
for future, thanks a lot.
If you are interesting in the topic, please subscribe to the EToSat mailing=
 list [https://www.ietf.org/mailman/listinfo/etosat].
Slides for all talks will be posted to a web page and a link sent to the et=
osat@ietf.org mailing list.

Time was flying for our 1 hour slot and we could not dedicate more time to =
discuss how the proxy approach could be combined with a satellite network.
We propose to continue the discussion on that topic on the MASQUE mailing l=
ist [https://www.ietf.org/mailman/listinfo/masque].
Even if SATCOM is not the core target of this work, it seems to be a releva=
nt use-case (among others) for MASQUE.

Kind regards,

Nicolas, Gorry and Emile

De : Kuhn Nicolas
Envoy=E9 : mercredi 20 novembre 2019 03:42
=C0 : etosat@ietf.org; iccrg@irtf.org; IETF QUIC WG <quic@ietf.org>; nwcrg@=
irtf.org; dtn@ietf.org
Cc : G Fairhurst <gorry@erg.abdn.ac.uk>; 'STEPHAN Emile RD-CORE-LAN' <emile=
.stephan@orange.com>
Objet : Side meeting on QUIC performance over high BDP networks

Hi,

Satellites are fun and we are sending bits in space ! However, this can com=
e with some challenges.
To speak about these challenges, we are organizing a side meeting on QUIC p=
erformance over high BDP networks :
               Today at 3pm30 in Bras Basah

=3D=3D Objective =3D=3D
There are multiple drafts related to the performance of QUIC over large BDP=
 networks (draft -kuhn-quic-4-sat, draft-kuhn-quic-0rtt-bdp, draft-ietf-qui=
c-recovery) or related to the performance of encrypted protocols in general=
 (draft-fairhurst-tsvwg-cc). The objective of this workshop is to gather pe=
ople interested in such activity and discuss the best way towards better en=
d user experience in this use case.

=3D=3D Agenda =3D=3D
High BDP : focus on SATCOM challenges for QUIC
Challenge : SWOT analysis of QUIC in SATCOM
What are the problems ?
What are our options to go forward ?
Any other activity on QUIC over SATCOM we are/were not aware of ?
Open questions for discussion

=3D=3D Remote participation =3D=3D
We are working on a solution for potential remote participants.
If you are interested in remote participation, please let us know.
The meeting will not be recorded, but meeting material will be shared (see =
below).

=3D=3D Meeting material =3D=3D
Meeting material (slides and minutes) will be sent to the etosat@ietf.org<m=
ailto:etosat@ietf.org> mailing list.
Join the mailing list if you are interested.

Thanks,

Nico, Gorry and Emile


--_000_F3B0A07CFD358240926B78A680E166FF1ED06AF0TWMBXP03cnesnet_
Content-Type: text/html; charset="iso-8859-1"
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=3Diso-8859-=
1">
<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:0cm;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
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.msonormal0, li.msonormal0, div.msonormal0
	{mso-style-name:msonormal;
	mso-margin-top-alt:auto;
	margin-right:0cm;
	mso-margin-bottom-alt:auto;
	margin-left:0cm;
	font-size:12.0pt;
	font-family:"Times New Roman",serif;}
span.EmailStyle18
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle19
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:#1F497D;}
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:612.0pt 792.0pt;
	margin:70.85pt 70.85pt 70.85pt 70.85pt;}
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"FR" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span style=3D"color:#1F497D">Hi,<o:p></o:p></span><=
/p>
<p class=3D"MsoNormal"><span style=3D"color:#1F497D"><o:p>&nbsp;</o:p></spa=
n></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Thank y=
ou all for coming to the &quot;QUIC for high BDP&quot; side-meeting.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">We hope=
 you found it positive and useful - at least, we did and have plans for fut=
ure, thanks a lot.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">If you =
are interesting in the topic, please subscribe to the EToSat mailing list [=
https://www.ietf.org/mailman/listinfo/etosat].<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Slides =
for all talks will be posted to a web page and a link sent to the etosat@ie=
tf.org mailing list.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Time wa=
s flying for our 1 hour slot and we could not dedicate more time to discuss=
 how the proxy approach could be combined with a satellite network.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">We prop=
ose to continue the discussion on that topic on the MASQUE mailing list [ht=
tps://www.ietf.org/mailman/listinfo/masque].
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Even if=
 SATCOM is not the core target of this work, it seems to be a relevant use-=
case (among others) for MASQUE.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D">Kind re=
gards, <o:p>
</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D;mso-fare=
ast-language:FR">Nicolas, Gorry and Emile
<o:p></o:p></span></p>
</div>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"color:#1F497D"><o:p>&n=
bsp;</o:p></span></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0cm =
0cm 0cm">
<p class=3D"MsoNormal"><b><span style=3D"mso-fareast-language:FR">De&nbsp;:=
</span></b><span style=3D"mso-fareast-language:FR"> Kuhn Nicolas
<br>
<b>Envoy=E9&nbsp;:</b> mercredi 20 novembre 2019 03:42<br>
<b>=C0&nbsp;:</b> etosat@ietf.org; iccrg@irtf.org; IETF QUIC WG &lt;quic@ie=
tf.org&gt;; nwcrg@irtf.org; dtn@ietf.org<br>
<b>Cc&nbsp;:</b> G Fairhurst &lt;gorry@erg.abdn.ac.uk&gt;; 'STEPHAN Emile R=
D-CORE-LAN' &lt;emile.stephan@orange.com&gt;<br>
<b>Objet&nbsp;:</b> Side meeting on QUIC performance over high BDP networks=
<o:p></o:p></span></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Hi, <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Satellites are fun and we are s=
ending bits in space ! However, this can come with some challenges.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">To speak about these challenges=
, we are organizing a side meeting on QUIC performance over high BDP networ=
ks :
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Today at 3pm30 in Bra=
s Basah<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=3D=3D Objective =3D=3D <o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">There are multiple drafts relat=
ed to the performance of QUIC over large BDP networks (draft -kuhn-quic-4-s=
at, draft-kuhn-quic-0rtt-bdp, draft-ietf-quic-recovery) or related to the p=
erformance of encrypted protocols in
 general (draft-fairhurst-tsvwg-cc). The objective of this workshop is to g=
ather people interested in such activity and discuss the best way towards b=
etter end user experience in this use case.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=3D=3D Agenda =3D=3D <o:p></o:p=
></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">High BDP : focus on SATCOM chal=
lenges for QUIC<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Challenge : SWOT analysis of QU=
IC in SATCOM<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">What are the problems ? <o:p></=
o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">What are our options to go forw=
ard ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Any other activity on QUIC over=
 SATCOM we are/were not aware of ?<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Open questions for discussion<o=
:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=3D=3D Remote participation =3D=
=3D <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">We are working on a solution fo=
r potential remote participants.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">If you are interested in remote=
 participation, please let us know.
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">The meeting will not be recorde=
d, but meeting material will be shared (see below).
<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">=3D=3D Meeting material =3D=3D<=
o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Meeting material (slides and mi=
nutes) will be sent to the
<a href=3D"mailto:etosat@ietf.org">etosat@ietf.org</a> mailing list. <o:p><=
/o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Join the mailing list if you ar=
e interested.<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Thanks, <o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US" style=3D"mso-fareast-language:F=
R">Nico, Gorry and Emile<o:p></o:p></span></p>
<p class=3D"MsoNormal"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
</div>
</body>
</html>

--_000_F3B0A07CFD358240926B78A680E166FF1ED06AF0TWMBXP03cnesnet_--


From nobody Mon Nov 25 13:58:31 2019
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 A882D120FA1 for <quic@ietfa.amsl.com>; Mon, 25 Nov 2019 13:58:29 -0800 (PST)
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=J36u0cWX; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=Q5aRxaWi
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 iRLLmZPMdBaq for <quic@ietfa.amsl.com>; Mon, 25 Nov 2019 13:58:28 -0800 (PST)
Received: from wout4-smtp.messagingengine.com (wout4-smtp.messagingengine.com [64.147.123.20]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E5EFD120F97 for <quic@ietf.org>; Mon, 25 Nov 2019 13:58:27 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 0CCDC95A; Mon, 25 Nov 2019 16:58:26 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Mon, 25 Nov 2019 16:58:27 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=U /MwSve5QsP2Jv7Of1GVhJxJdLcsVURHcXN8fo7cYAo=; b=J36u0cWXMwnzcoAeo 40bvRzAigNmCqLYomAgYwgOs+5EvW3m97GeuHBuUYoqqqOSc1ZiiGfEAvALPiAKb JH6Vypo1do1UI1PGnEhDHhNv/Eq9ivN3gwjZxlYwtvE55eb5RJBzLEfklhcoHrcM xFOWQmINBz9+f+qIws576rkgpbIcHiKh8hXK7bPakQ1EKzAP4nPxhLMlQcOph4uv RXMebwC5gunlX6aFHIf8fH/OJSzRPk8nQ26ldXXaFHi9ovqShoj3UHrSzJKRz2lq 6oX0igU6wuabWovm99qd3nFJm6uSUANFKChX1P4mdjy+sFVET5x6jqkj2Pv1TIgt DfPog==
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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=U/MwSve5QsP2Jv7Of1GVhJxJdLcsVURHcXN8fo7cY Ao=; b=Q5aRxaWioG8ctE7g5Fl9cggdTW4TLUkbjAYYfO0JBN3+6KaDnTh3aGana kq+3JbGpHVFfpE7/y6Eez0W5GPBhQKkD7tHnXzi64oOWk/8jsUpvd0Q9/e1zJ+UA SoFTNjyZR3TyE1lAoGMr5nx/tgTbTlhlAvzPQ/s8G4pWu+p1UhlNKDyK1fqyXyfR lu3tPPDhjxZxOItlwsAApRMSwoboKlzgRGHyk3PA0DpehkR/yrsKWNBVzXof6i6G SSO0I6W1t5M7VMVwQ9orjY5BVzlQT5W22xXq02OoCWdiPDjld0j7jZBkOLh+KR+C 6TFlSothV0npMbZCBQEYlhCaY+f/w==
X-ME-Sender: <xms:gU7cXfPlcWcaIh6ob_rQGVf5X4v9OB4ADuEZt3yk8m8S8reQT7xvwA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudeiuddgudehiecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghr khcupfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuffhomhgrih hnpehhthhtphefrghnughqphgrtghkughrrghfthhsthhothhhrghtphhrohgtvghsshgr shifvghllhdrrghspdhgihhthhhusgdrtghomhdpmhhnohhtrdhnvghtnecukfhppeduud elrddujedrudehkedrvdehudenucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehm nhhothdrnhgvthenucevlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:gk7cXYkuy4bA1dKoIqdpM2uODu4zavn8yzJh7q9pvtJxCvFDuckIMg> <xmx:gk7cXd51WOlX-Vg7friMDpDukyEV5rVrfxWeIua-2qREFtP7EjpIYw> <xmx:gk7cXZ4EwYHE5mPZneR5Arb91uVzSQu6GJ1xWtEj_xrIIocu8KI-PA> <xmx:gk7cXWKImr-uQTf8w95gro9CVVAK0fK4VYtPpLeM3KLKLiwhP5qb4g>
Received: from attitudadjuster.mnot.net (unknown [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id CEA7D8005A; Mon, 25 Nov 2019 16:58:23 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: Re: Call for Consensus: Moving HTTP/3, QPACK and Recovery to the Late-Stage Process
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <6A43BEC7-F9DE-40C9-BF70-BF1618EAFE01@mnot.net>
Date: Tue, 26 Nov 2019 08:58:20 +1100
Cc: Lars Eggert <lars@eggert.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <F08E3248-76B2-4158-B57E-139B5B0E5006@mnot.net>
References: <6A43BEC7-F9DE-40C9-BF70-BF1618EAFE01@mnot.net>
To: IETF QUIC WG <quic@ietf.org>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/hxadXDI53V83dCiNe-bKGaws8-A>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 25 Nov 2019 21:58:29 -0000

These documents are now in the late-stage process.

Thanks,


> On 6 Nov 2019, at 12:01 pm, Mark Nottingham <mnot@mnot.net> wrote:
>=20
> Previously, we've moved to the 'late-stage process' documented at [1] =
for the Transport and TLS drafts. The chairs and editors now feel that =
it's time to move the Recovery, HTTP/3, and QPACK drafts to that process =
as well.
>=20
> As before, this is because we're getting to a stage we feel the =
documents would benefit from slower and slightly more formal process, so =
that the rate of change is not so high, changes that do occur are =
well-vetted, and the documents get closer to reflecting consensus in the =
working group.
>=20
> If we do this, we're saying that we have gained consensus on what =
remains in these documents, excepting their outstanding issues. As per =
our charter:
>=20
> """
> 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.
> """
>=20
> That doesn't mean that new issues can't be raised against those =
drafts. However, new issues against them will be judged for whether they =
contain new information (in particular, security or interoperability =
impact), a clear technical defect, or have significant (in the judgement =
of the chairs) support for further discussion. If the issue isn't =
well-described or atomic, it may be closed with a request to refactor, =
or refactored for you.
>=20
> Again, this does not affect editorial issues.
>=20
> Practically speaking, it means that new issues will be triaged by the =
Chairs -- not the editors (although they can still "claim" purely =
editorial issues) -- and those that don't meet the criteria above will =
be closed. Those that do will be labeled (again, by the Chairs only) as =
`design`.
>=20
> It also means that all of the closed `design` issues against these =
drafts will be marked as `has-consensus`. Additionally, the `quicv2` =
issues against them will be closed and marked `has-consensus`.
>=20
> The issues that will be labeled `has-consensus` (and closed, if still =
open) are listed here:
>=20
> =
https://github.com/quicwg/base-drafts/issues?q=3Dis%3Aissue+is%3Aclosed+la=
bel%3Adesign+-label%3Ahas-consensus+-label%3A-transport+-label%3A-tls
>=20
> We believe that all of these issues have been discussed and the group =
has formed consensus on them; this only formalises that.
>=20
> If you have concerns or questions, please discuss them on-list; =
barring pushback, we'll adopt this on 15-Nov-2019.
>=20
> Cheers,
>=20
> 1. =
https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md#late-sta=
ge-process
>=20
> --
> Mark and Lars, QUIC WG Chairs
>=20

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


From nobody Wed Nov 27 16:59:01 2019
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 4051D120BBE for <quic@ietfa.amsl.com>; Wed, 27 Nov 2019 16:58:59 -0800 (PST)
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_HELO_NONE=0.001, 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 AvHT10MHLUnN for <quic@ietfa.amsl.com>; Wed, 27 Nov 2019 16:58:57 -0800 (PST)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::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 C7F201208F8 for <quic@ietf.org>; Wed, 27 Nov 2019 16:58:56 -0800 (PST)
Received: by mail-lj1-x236.google.com with SMTP id m6so19140411ljc.1 for <quic@ietf.org>; Wed, 27 Nov 2019 16:58:56 -0800 (PST)
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=MuyAQ7BlQlDL6Fy7AFM5sBRybzppCVudqgQvHQ9+sb8=; b=K7ZiUaZvTHzM/XJo6kyvX1nrQvvVAFD1igUYQokY8TljyM8ry9KoP1C9N0LLk1VQjR SfILC6j55FXVrimOX529VHcAZ/RrxNztXlZT7od5jXdjwuuBf5jj8rEk0e4BwP9nQXa4 3LQGpW247eDwTwJgZsMGGSZMkw+9bjoRAuqBNUTVh9sJbkBwVUGxzcAo8ImQz9efMJp9 V87imJZEx8GSRnaxhD76P/asZ0yWPcFOhp6A2q0tAIiQctxz/DZFYjfIRmlYE4C2kJR/ craX4apK9NKkv1c6USQCP4mQNa/Z9E7V4vK/1NMbmmgU1tHw9duHjUIHUneOAH8pYwYS XERA==
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=MuyAQ7BlQlDL6Fy7AFM5sBRybzppCVudqgQvHQ9+sb8=; b=MydsGQNYotlRzmxaQk1IctygTQpDuRag5VwiRex7uMmlaSN5wZSmPIQgKd6pN9DcxT d4mvKXlkm4DRyzX59rLlgD9cFd3lZpKkG4j3l6F129l2frDN4xpFIJwSqmNeFtDBv+n0 jDa7fcUD15j0At38DTdJMlcpXCdsEeGhjsRtYtkKbL7Apr8SlOjboHCE3uJ5CMBW77qq 6ROsR/4hA7Q68N1j+JiF2BZebuKhSAesQJZrXaBFRTbAlYM7h4ZX6E2FfSmJHTksz8Xs 38Z+acV4QxIw85Z1by6Q1oBeW0yrmIsplBuecUArwtfQChbk+/KfSPCYJK3dLzo6KIaC iajQ==
X-Gm-Message-State: APjAAAV8yPoeTfkU44i1JQpOWqZKbtDhTmj+iyL36Sf8K9qN5mUKkPgM jacVhnTokOcIrxHkJaEMkH2D75Q4sSHbJNIwZtA=
X-Google-Smtp-Source: APXvYqx2LHHX18Qx1W4xfE8TQuRLG1QcLXHH/jswANrfARoSDwL7rWRs7ONhLXaGB9FwAALtfVmkLlqxuQJYtKcWbEE=
X-Received: by 2002:a2e:9356:: with SMTP id m22mr20314366ljh.160.1574902734802;  Wed, 27 Nov 2019 16:58:54 -0800 (PST)
MIME-Version: 1.0
References: <67289EB8-3A37-4231-A3F9-FB46509152A0@mnot.net> <CABcZeBNP7KjMp-usoa6P+KEBg-wz7uOhMjQZxjOEQi2V65ZJ6A@mail.gmail.com>
In-Reply-To: <CABcZeBNP7KjMp-usoa6P+KEBg-wz7uOhMjQZxjOEQi2V65ZJ6A@mail.gmail.com>
From: Marten Seemann <martenseemann@gmail.com>
Date: Thu, 28 Nov 2019 07:58:43 +0700
Message-ID: <CAOYVs2r8jOxanOiE5TQUSVvnQAmgG00y13NcCO3=15eT2K0vbw@mail.gmail.com>
Subject: Re: Consensus Calls for Transport/TLS issues, pre-Singapore
To: Eric Rescorla <ekr@rtfm.com>
Cc: Mark Nottingham <mnot@mnot.net>, Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001052b905985d9e3f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/VD-dd8L-T0YIS3mY91DiRpJJj18>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 28 Nov 2019 00:58:59 -0000

--0000000000001052b905985d9e3f
Content-Type: text/plain; charset="UTF-8"

I commented on #3107 a couple of days ago:
https://github.com/quicwg/base-drafts/pull/3107#pullrequestreview-321895279.

On Fri, Nov 15, 2019 at 3:59 PM Eric Rescorla <ekr@rtfm.com> wrote:

> I think some changes are in order in 3155 and 3014. Comments made in the PR
>
> On Wed, Nov 13, 2019 at 5:26 PM Mark Nottingham <mnot@mnot.net> wrote:
>
>> The following issues have proposals for resolution, and discussion so far
>> seems to support consensus to accept them. If you object, please do so on
>> the issue or in response to this message (changing the Subject
>> appropriately!). Absent any pushback, we'll direct the editors to
>> incorporate them late next week. Note that by default we won't discuss
>> these issues in Singapore, unless something comes up.
>>
>> See <https://github.com/quicwg/base-drafts/projects/5> for the current
>> state of issues in the Late Stage process, itself defined at <
>> https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md>.
>>
>> * #3127: NEW_TOKEN and Retry tokens must be distinguishable
>>   Proposal: https://github.com/quicwg/base-drafts/pull/3128
>>
>> * #3158: Application close should be disallowed in Initial or Handshake
>>   Proposal: https://github.com/quicwg/base-drafts/pull/3164
>>
>> * #3155: The method of identifying "the same server"
>>   Proposal: https://github.com/quicwg/base-drafts/pull/3156
>>
>> * #2475: Invalid CONNECTION_CLOSE frames
>>   Proposal: https://github.com/quicwg/base-drafts/pull/3231
>>
>> * #3168: Allow servers to close connections immediately when the token is
>> corrupted
>>   Proposal: https://github.com/quicwg/base-drafts/pull/3107
>>
>> * #3194: reordered NEW_CONNECTION_ID frames with retired sequence numbers
>> shouldn't be used
>>   Proposal: https://github.com/quicwg/base-drafts/pull/3202
>>
>> * #3014: Handling of corrupt Retry packets
>>   Proposal: https://github.com/quicwg/base-drafts/pull/3120
>>
>> * #3095: Backoff of CONNECTION_CLOSE needs to be a MUST
>>   Proposal: https://github.com/quicwg/base-drafts/pull/3157
>>
>>
>> --
>> Mark Nottingham   https://www.mnot.net/
>>
>>

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

<div dir=3D"ltr"><div>I commented on #3107 a couple of days ago: <a href=3D=
"https://github.com/quicwg/base-drafts/pull/3107#pullrequestreview-32189527=
9">https://github.com/quicwg/base-drafts/pull/3107#pullrequestreview-321895=
279</a>.</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Fri, Nov 15, 2019 at 3:59 PM Eric Rescorla &lt;<a href=
=3D"mailto:ekr@rtfm.com">ekr@rtfm.com</a>&gt; wrote:<br></div><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px soli=
d rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div>I think some cha=
nges are in order in 3155 and 3014. Comments made in the PR<br></div><br><d=
iv class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Nov =
13, 2019 at 5:26 PM Mark Nottingham &lt;<a href=3D"mailto:mnot@mnot.net" ta=
rget=3D"_blank">mnot@mnot.net</a>&gt; wrote:<br></div><blockquote class=3D"=
gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(20=
4,204,204);padding-left:1ex">The following issues have proposals for resolu=
tion, and discussion so far seems to support consensus to accept them. If y=
ou object, please do so on the issue or in response to this message (changi=
ng the Subject appropriately!). Absent any pushback, we&#39;ll direct the e=
ditors to incorporate them late next week. Note that by default we won&#39;=
t discuss these issues in Singapore, unless something comes up.<br>
<br>
See &lt;<a href=3D"https://github.com/quicwg/base-drafts/projects/5" rel=3D=
"noreferrer" target=3D"_blank">https://github.com/quicwg/base-drafts/projec=
ts/5</a>&gt; for the current state of issues in the Late Stage process, its=
elf defined at &lt;<a href=3D"https://github.com/quicwg/base-drafts/blob/ma=
ster/CONTRIBUTING.md" rel=3D"noreferrer" target=3D"_blank">https://github.c=
om/quicwg/base-drafts/blob/master/CONTRIBUTING.md</a>&gt;.<br>
<br>
* #3127: NEW_TOKEN and Retry tokens must be distinguishable<br>
=C2=A0 Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3128=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/3128</a><br>
<br>
* #3158: Application close should be disallowed in Initial or Handshake<br>
=C2=A0 Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3164=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/3164</a><br>
<br>
* #3155: The method of identifying &quot;the same server&quot;<br>
=C2=A0 Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3156=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/3156</a><br>
<br>
* #2475: Invalid CONNECTION_CLOSE frames<br>
=C2=A0 Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3231=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/3231</a><br>
<br>
* #3168: Allow servers to close connections immediately when the token is c=
orrupted<br>
=C2=A0 Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3107=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/3107</a><br>
<br>
* #3194: reordered NEW_CONNECTION_ID frames with retired sequence numbers s=
houldn&#39;t be used<br>
=C2=A0 Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3202=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/3202</a><br>
<br>
* #3014: Handling of corrupt Retry packets<br>
=C2=A0 Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3120=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/3120</a><br>
<br>
* #3095: Backoff of CONNECTION_CLOSE needs to be a MUST<br>
=C2=A0 Proposal: <a href=3D"https://github.com/quicwg/base-drafts/pull/3157=
" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/3157</a><br>
<br>
<br>
--<br>
Mark Nottingham=C2=A0 =C2=A0<a href=3D"https://www.mnot.net/" rel=3D"norefe=
rrer" target=3D"_blank">https://www.mnot.net/</a><br>
<br>
</blockquote></div></div>
</blockquote></div>

--0000000000001052b905985d9e3f--


From nobody Thu Nov 28 16:54:48 2019
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 C7C1B12013B for <quic@ietfa.amsl.com>; Thu, 28 Nov 2019 16:54:46 -0800 (PST)
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=z3DCsGBQ; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=uaht+RrE
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 En0cEIvye1lC for <quic@ietfa.amsl.com>; Thu, 28 Nov 2019 16:54:43 -0800 (PST)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4182A1200B7 for <quic@ietf.org>; Thu, 28 Nov 2019 16:54:43 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 7DEC07DC; Thu, 28 Nov 2019 19:54:42 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 28 Nov 2019 19:54:42 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=j CJ53gEVtbRq5TGC4xkAmuABcp32xhGUoTMdXcGLo/4=; b=z3DCsGBQU/UMpRNWK QlHn14fZPnPp3HnodXuiy67/5/FvA6YyrfzSNtrx+ESLiaO3nOWCafzl5KzczReA gG6PhTGujcgO0+bGt0+TBrDjX3VPaZczQoIpineDG4Hz5+6ivcHaxg56757pS5KT RrtOprib622U8fTzxiWdtza+zDUVj6Mdl1OkUtl/HUfk2NoUE5QkOEQfMtWkEmX+ SVrD0i8XHO0sSTSXukP4px87yYfcz9eqUxTa7nw3T2zh6yYzO11N7CZgpVM397Ux jOSW/bViXzUNjnaks8/ZY5CkSXU2vkTMpMSrmpKJQjJHnTjyxmlMAXEDPvT+vUNY H+jSg==
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-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=jCJ53gEVtbRq5TGC4xkAmuABcp32xhGUoTMdXcGLo /4=; b=uaht+RrEgvzPFGhdYIWImxZ63zENZo+r3cOKXXWtlGzuLr6JMTRYsjZ/9 Ffpa+B8aCXVIOsuFwXLndGVXvsdwzxeb36sQR8SSX6ZcpgceJMkbTk2eNp8MoZdG NR6new2NIKFZCEfAwTAKqYKZivgS4jbKcN6bWUHDY1Yamg99aGvh0UYUoYt6Df07 2Oy7LrmZFRcIsuOoqfSkt6Riz7Y6PDGJRDX3GHoRE+c03Bg5BqMafgmB+eGrf6sJ 7JKvxTUKJoswH5FV8anGucc+sd/3/Jy3W4CEPkueNhSVjNAMQB76LrDOLTh0nrwN W+nfB0I5Kx/NGmwAQSn4pqv6f9++A==
X-ME-Sender: <xms:T2zgXSbF6TY55ENnGx4S_-zDBz2mGeqqw_wHVZ4NXuO3Fqu26NQpwQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudeikedgvdejucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurheptggguffhjgffgffkfhfvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhk ucfpohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinh epghhithhhuhgsrdgtohhmpdhmnhhothdrnhgvthenucfkphepudduledrudejrdduheek rddvhedunecurfgrrhgrmhepmhgrihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvghtne cuvehluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:T2zgXdPQATqmkhgg5Hl-TRGu3HG71ffCDT2qggOX8wPQaLltHY00IQ> <xmx:T2zgXYUULDsccv7sJupgJCO7BAbNgHaR9tcItwjOtHT3rC-DHdU88g> <xmx:T2zgXeeSlDfp1XnjftYv1M0cvswxx4Et8XD9DvVvPVQnYBKwy0B_eA> <xmx:UmzgXSG7OI3rbR4iwH71qTlVy5zf35PyJPwxcWs9DcngfzdN_2jakA>
Received: from attitudadjuster.mnot.net (unknown [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id C62B23060074; Thu, 28 Nov 2019 19:54:38 -0500 (EST)
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: Re: Consensus Calls for Transport/TLS issues, pre-Singapore
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <67289EB8-3A37-4231-A3F9-FB46509152A0@mnot.net>
Date: Fri, 29 Nov 2019 11:54:34 +1100
Cc: Lars Eggert <lars@eggert.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <046BDEE5-802B-4455-82AE-2DA361D2A124@mnot.net>
References: <67289EB8-3A37-4231-A3F9-FB46509152A0@mnot.net>
To: IETF QUIC WG <quic@ietf.org>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/brPb1Lsjp1ysmBLB_6UHnobfxaA>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 29 Nov 2019 00:54:47 -0000

Consensus declared for all *except* #3014; we'll continue to discuss =
that.

Cheers,


> On 14 Nov 2019, at 12:25 pm, Mark Nottingham <mnot@mnot.net> wrote:
>=20
> The following issues have proposals for resolution, and discussion so =
far seems to support consensus to accept them. If you object, please do =
so on the issue or in response to this message (changing the Subject =
appropriately!). Absent any pushback, we'll direct the editors to =
incorporate them late next week. Note that by default we won't discuss =
these issues in Singapore, unless something comes up.
>=20
> See <https://github.com/quicwg/base-drafts/projects/5> for the current =
state of issues in the Late Stage process, itself defined at =
<https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md>.
>=20
> * #3127: NEW_TOKEN and Retry tokens must be distinguishable
>  Proposal: https://github.com/quicwg/base-drafts/pull/3128
>=20
> * #3158: Application close should be disallowed in Initial or =
Handshake
>  Proposal: https://github.com/quicwg/base-drafts/pull/3164
>=20
> * #3155: The method of identifying "the same server"
>  Proposal: https://github.com/quicwg/base-drafts/pull/3156
>=20
> * #2475: Invalid CONNECTION_CLOSE frames
>  Proposal: https://github.com/quicwg/base-drafts/pull/3231
>=20
> * #3168: Allow servers to close connections immediately when the token =
is corrupted
>  Proposal: https://github.com/quicwg/base-drafts/pull/3107
>=20
> * #3194: reordered NEW_CONNECTION_ID frames with retired sequence =
numbers shouldn't be used
>  Proposal: https://github.com/quicwg/base-drafts/pull/3202
>=20
> * #3014: Handling of corrupt Retry packets
>  Proposal: https://github.com/quicwg/base-drafts/pull/3120
>=20
> * #3095: Backoff of CONNECTION_CLOSE needs to be a MUST
>  Proposal: https://github.com/quicwg/base-drafts/pull/3157
>=20
>=20
> --
> Mark Nottingham   https://www.mnot.net/
>=20

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


From nobody Thu Nov 28 17:40:50 2019
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 BAB3A1208E4 for <quic@ietfa.amsl.com>; Thu, 28 Nov 2019 17:40:48 -0800 (PST)
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=y7bmBYv4; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=VHh9zvM7
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 11FiEZ82V4DP for <quic@ietfa.amsl.com>; Thu, 28 Nov 2019 17:40:47 -0800 (PST)
Received: from wout5-smtp.messagingengine.com (wout5-smtp.messagingengine.com [64.147.123.21]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 42881120024 for <quic@ietf.org>; Thu, 28 Nov 2019 17:40:47 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.west.internal (Postfix) with ESMTP id 9B0A0803; Thu, 28 Nov 2019 20:40:46 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute3.internal (MEProxy); Thu, 28 Nov 2019 20:40:46 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h=from :content-type:content-transfer-encoding:mime-version:subject :message-id:date:cc:to; s=fm1; bh=U3OhbxBBGFubmxG0Zbt68t5P/3J6L2 4ML6aLh4tzLnY=; b=y7bmBYv4OHo0DMMfzBP8ahMcQr6Z55dzQJ8LdZJa749Nxs zU896TGNhd25+UjBGgUT0dNGtiI9uD6KqsvGRGgBRBBVo/a+kdh0hS8ibTv9PYXL IjW5Xg2Pb0RWNXPNxE7im0MT4RqA6p2TbiSe3XsoY0yn1ejnFcrI13QNW1sij7Xw cOkFnzfJdvrr8Ez7eN7km9Eatx6DpElnYOt+z9zGgueZ2qpMqI9X37xX2S3OytoP tKgPGFIDbJ/tUtbQuxh5qfsRIMyhAEWOr4JqoC+Ffyhqj1qxbCEWWC7t+aIf6zCR MeYS+/FFmibgevhoW+KKowMkX4OeCUSvO2aAi+1w==
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-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=U3Ohbx BBGFubmxG0Zbt68t5P/3J6L24ML6aLh4tzLnY=; b=VHh9zvM72Z1h7QCh/6Xpu8 lnDC4vjN4TnUzNjck+m+9VtDZR6eYsU54rbcXOq/dgf6RTQtYKWhJS6oQxQJ7Wxo Vn1Q4+X5YDkolRYSUhmn8JMen3NnB7YoCnlWI+OHV3334cqWLq1UBkhewEAuB7xz TSF36Gaj1KgK7d0MU9446tZv5QhSQcGNzocDHf5VigVU5c07Y4I6N2aMgMukdlR5 5wG5x91QNhWM5GDOEpO+jYz/XxJ7C1iAKf6GS/x74WXYP4xQn6VGAauI5t8I3KwB NhEz1cowB9KaUCxW4uR0Mahus6hKjKYYbJhu6qDMw2Rv8WNyTgEV1BQd6noJ5knA ==
X-ME-Sender: <xms:HXfgXRACaLQJIU1HnLWeKXcOL1Tlk9Z6ZByTglhuzKi1li6NEm8vAQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudeikedgfeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhephfgtgfgguffkfffvofesthhqmhdthhdtvdenucfhrhhomhepofgrrhhkucfp ohhtthhinhhghhgrmhcuoehmnhhothesmhhnohhtrdhnvghtqeenucffohhmrghinhepgh hithhhuhgsrdgtohhmpdhmnhhothdrnhgvthenucfkphepudduledrudejrdduheekrddv hedunecurfgrrhgrmhepmhgrihhlfhhrohhmpehmnhhothesmhhnohhtrdhnvghtnecuve hluhhsthgvrhfuihiivgeptd
X-ME-Proxy: <xmx:HXfgXX-bplF3AD2ysF2hCfXOZQx2289d-A81sqs2Txu9oFlwCXJ_8Q> <xmx:HXfgXdC-pdKAFrjxE9_1a8Zib0hgzPUE-VCaCY4bT8jvIRcix4w3vQ> <xmx:HXfgXcTtNkh9RPLLRiK1jEBKXUWrrXt01msDw2aG5fyXB2u4Rj19jQ> <xmx:HnfgXQW8m667xMc9kaaN3HUyVkUEVh28hvqWZMIu4sBj8Msp4cNH8Q>
Received: from attitudadjuster.mnot.net (unknown [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id E31EF306009F; Thu, 28 Nov 2019 20:40:43 -0500 (EST)
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 13.0 \(3601.0.10\))
Subject: Consensus calls, Post-Singapore
Message-Id: <CCD077BB-2276-4375-BCBF-CB51DDE6DCE7@mnot.net>
Date: Fri, 29 Nov 2019 12:40:38 +1100
Cc: Lars Eggert <lars@eggert.org>
To: IETF QUIC WG <quic@ietf.org>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/o88bVOI0q0esN26a-kv-j2Vz8mQ>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 29 Nov 2019 01:40:49 -0000

The following issues have proposals for resolution, and discussion so =
far seems to support consensus to accept them. If you object, please do =
so on the issue or in response to this message (changing the Subject =
appropriately!). Absent any pushback, we'll direct the editors to =
incorporate them late next week.

Note that this group of issues includes some HTTP and recovery issues, =
as those documents are now under the Late Stage Process.

See <https://github.com/quicwg/base-drafts/projects/5> for the current =
state of issues in the Late Stage process, itself defined at =
<https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md>.

* #3258: Allow CRYPTO_BUFFER_EXCEEEDED error when CRYPTO frame goes =
beyond 2^62 bytes
   The proposal is <https://github.com/quicwg/base-drafts/pull/3186>

* #3256: Packet reordering thresholds less than 3 are not sufficiently =
reordering tolerant
   The proposal is <https://github.com/quicwg/base-drafts/pull/3240>

* #3200: Definition of "active connection ID" is misleading (or the name =
is)
   The proposal is <https://github.com/quicwg/base-drafts/pull/3201>

* #3197: active_connection_id_limit defaults to 0
   The proposal is <https://github.com/quicwg/base-drafts/pull/3201>

* #3193: active_connection_id_limit interacts poorly with Retire Prior =
To
   The proposal is <https://github.com/quicwg/base-drafts/pull/3201>

* #3159: Server should not accept 1-RTT traffic before handshake =
completion
   The proposal is <https://github.com/quicwg/base-drafts/pull/3224>

* #3130: Does it matter if the the STOP_SENDING error code is something =
other than EARLY RESPONSE?
   The proposal is <https://github.com/quicwg/base-drafts/pull/3208>

* #3111: [Version Ossification] Alternative version and Initial Salt =
should be part of NEW_TOKEN
   The proposal is to close this with no action, but we may consider it =
for QUICv2 and/or an extension in the future.

* #3102: Add provisional registration for all registries
   The proposal is <https://github.com/quicwg/base-drafts/pull/3170>

* #3020: Transport parameter registry is too constraining for innovation
   The proposal is <https://github.com/quicwg/base-drafts/pull/3170>

* #2792: Timing side-channel on key updates
   The proposal is <https://github.com/quicwg/base-drafts/pull/3263>

* #2496: QUIC Version Ossification
   The proposal is to close this with no action, but we may consider it =
for QUICv2 and/or an extension in the future.


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


From nobody Fri Nov 29 04:53:12 2019
Return-Path: <jiuhai.zhang@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 AA6D4120273 for <quic@ietfa.amsl.com>; Fri, 29 Nov 2019 04:53:11 -0800 (PST)
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_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 1OBj9I5ybjTp for <quic@ietfa.amsl.com>; Fri, 29 Nov 2019 04:53:10 -0800 (PST)
Received: from mail-lj1-x233.google.com (mail-lj1-x233.google.com [IPv6:2a00:1450:4864:20::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 5807112008B for <quic@ietf.org>; Fri, 29 Nov 2019 04:53:10 -0800 (PST)
Received: by mail-lj1-x233.google.com with SMTP id k15so31932546lja.3 for <quic@ietf.org>; Fri, 29 Nov 2019 04:53:10 -0800 (PST)
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=rzcGicWORjqyxQfJw3nR43gRavPXYaMCk+zDFYoPc5g=; b=s/ncfxSq5Cjc2BiduLfy7kyJa3+TE1o3bibIDSkcMFcCsmLpbrHf8vl/nXEBq9MEip FlCYtN9Xrzh5MGvBvinGX0THQA+W0r9YBQl25022W8MHh26gDW9pIiIXu09xgnWLDdpz o9y/GYRxZBFmDcgujovN3CaNrwdYv5hzf9Uk42y45eIGck82CqyBjva9CLLiwcAoD9jv HBSwAMBseCmXTqeQIs2nobMN7GTlgBkknKullP9eVgina4fx0ndvzYD0OHe+6dBh7miE lJ+etTXXtv8UtxxcQAqsiWuf52Mm+u6VAYcV3ldEMxzQR7aLRbyjGwYv08/OmVcROAD0 Ot9w==
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=rzcGicWORjqyxQfJw3nR43gRavPXYaMCk+zDFYoPc5g=; b=mpmUVqSKuRSnZEOkIu+0da7PBGRu9sIbaDj1iV8w1wNQSLi3dQTe66r8519mWnMo08 uiK1o6xxt06oEogntWb0FHzMxVA3yX59Gv9uj6ifAL/dP+LHks2DnVn5zj1+5rdmSbaj iRdXGbnzdDOWIOld7OitE01RN9ph6rhZOqI7IcTOM63AfTN3nHdAPC1W47U7xjH7RPNm 3xFI2f4d7Mp6473lbKJOxuQl4K0MX+bP308JVE8zKeKEniV+jrkNjqWLcNTcWJ1twtgg qHT9jM3Gg5zgvH1sigJ/txA982itKFVOCMtQxqMvBSJKlJ+odmYjTZ4Aw5dXmSxT/g4U v1RQ==
X-Gm-Message-State: APjAAAWFmEKxOJYkQGgptlMhKq/+EeDZe8v39W3xEZbx+KGylSpQlm1M 5+C1/lZhRrYHCIhShR0zAmQZpNH6B6YVEHOEXJc5+g==
X-Google-Smtp-Source: APXvYqyXdA9chfRIW6k9xeOQKvQkNkGyxllZEuFKmdcSLIwCWqHkXymwRDWZLpa5/xrByNIwA2ztLZ4GJJbUsXVEpGg=
X-Received: by 2002:a2e:2c1a:: with SMTP id s26mr38245627ljs.239.1575031988436;  Fri, 29 Nov 2019 04:53:08 -0800 (PST)
MIME-Version: 1.0
From: Jiuhai Zhang <jiuhai.zhang@gmail.com>
Date: Fri, 29 Nov 2019 20:52:57 +0800
Message-ID: <CAG9+TpZgm1zbW2Zq9oPCprmgUr-Rh29RTmGyEcVfE+T-i1WvaA@mail.gmail.com>
Subject: How to avoid kernel's receive buff full , then UDP packet dropped by kernel?
To: quic@ietf.org
Content-Type: multipart/alternative; boundary="0000000000002e43d505987bb62e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/bviS7w86NeOF-Sr2uI67aSDJHiU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 29 Nov 2019 12:53:12 -0000

--0000000000002e43d505987bb62e
Content-Type: text/plain; charset="UTF-8"

Is there any good idea to solve this? How can we do flow control like TCP
receive window size? User space can not get how many receive buff is used

--0000000000002e43d505987bb62e
Content-Type: text/html; charset="UTF-8"

<div dir="ltr">Is there any good idea to solve this? How can we do flow control like TCP receive window size? User space can not get how many receive buff is used</div>

--0000000000002e43d505987bb62e--


From nobody Fri Nov 29 05:04:09 2019
Return-Path: <jiuhai.zhang@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 E3BA6120289 for <quic@ietfa.amsl.com>; Fri, 29 Nov 2019 05:04:07 -0800 (PST)
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_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=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 sXzTni3gvVdF for <quic@ietfa.amsl.com>; Fri, 29 Nov 2019 05:04:06 -0800 (PST)
Received: from mail-lj1-x230.google.com (mail-lj1-x230.google.com [IPv6:2a00:1450:4864:20::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 534F812008B for <quic@ietf.org>; Fri, 29 Nov 2019 05:04:06 -0800 (PST)
Received: by mail-lj1-x230.google.com with SMTP id j6so22929666lja.2 for <quic@ietf.org>; Fri, 29 Nov 2019 05:04:06 -0800 (PST)
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=vxuOJpXEWoF/luvPCFSkZHJJyVv/UwHNxVZeKkFzoWc=; b=K3RaHojOSIFqyId1WnsVZM/ajmChpxTpDKI/w1tSnID0ULMgC+3fJ95vluQY077Jck gi66Ua5Szzyl308fXxelLS1G77LVnf8NGwnqzzWvQUDGenENGM6lDM1tRD4Zi7D1IIOd ZODIsZ/TrthQvJyW0mW+XnwGRG27F8odn9GfZFBWrLre3LM0ahRDodIvfBqgeiV+iHdB fmFABUF/XuSB1dtl8rrLJ43/F2x6L5tOSeOI0NfM5NWTwsEiKgVDXkxoGrLYD4SBKDVJ 7eYzj14QVkmeS9qDOuzzBV1fKGdxYHppvfoPAE2WvWxbct0U5Zd9lB7bx30OYHcEEvyp s9iw==
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=vxuOJpXEWoF/luvPCFSkZHJJyVv/UwHNxVZeKkFzoWc=; b=Z3HQ3be7ICfkCbWbkS1yp4i3VWQyjxscWgMrsQJXWcyDjSTXRspLpW2a3Y3wZ6aG+L l2rAmqPhW4AkAffQ2i0J6VuMloLl81cYOvXeJ3L3YyWNnye4g5U8HZmv1QNofiMnbAjD n5KhxP9PSn663gTcZjVqPM70qlWNw6PkR7xxwXrKjJxKj2qrDTc66vfGtnyj9E/AF2E2 9GqaA+5RdBT/EHV8qbVOo46XWhBWNaoa4+BmRJIySZT9yx/vIZ8PnI8QQoQpIdKW68ez jpk23C3KGz6L3kuzgS2PrhRS795u2DbabUj7drxeGw1ehADSgqMgCNNZKCsAtKZvhu84 K4pg==
X-Gm-Message-State: APjAAAX5pE6FTRZhN5+DPR/aRA4ysUsU9636qtMyenc+B6D4fMhWIwUV eZAKNi+Eqt4eNPiN/3xEHekcoNv32tuHYf7WpsLz4jYW
X-Google-Smtp-Source: APXvYqxbf1H7y5oNSfKEvgte7uLJz23nF9KQ1FUnPhhlbaRinmIcF/UjYGB7DC5ICeORucpcdUl/0jWTYJQ91isV7xA=
X-Received: by 2002:a2e:91c7:: with SMTP id u7mr12810491ljg.249.1575032644285;  Fri, 29 Nov 2019 05:04:04 -0800 (PST)
MIME-Version: 1.0
From: Jiuhai Zhang <jiuhai.zhang@gmail.com>
Date: Fri, 29 Nov 2019 21:03:53 +0800
Message-ID: <CAG9+TpaFDpoPCXkLVBRMYUF4sCcFqzEeuNSFX4n2VY3A0LN09A@mail.gmail.com>
Subject: CRYPTO_ERROR (0x1XX) conflict with HTTP/3 Error Codes
To: quic@ietf.org
Content-Type: multipart/alternative; boundary="00000000000045baba05987bdde1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/0v8DblBPRA0QunKG5EgYXOLlvh4>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 29 Nov 2019 13:04:08 -0000

--00000000000045baba05987bdde1
Content-Type: text/plain; charset="UTF-8"

Transport error CRYPTO_ERROR (0x1XX)
HTTP/3 error range 0x100 from 0x110

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

<div dir=3D"ltr">Transport error CRYPTO_ERROR (0x1XX)<div>HTTP/3 error rang=
e=C2=A0<span style=3D"color:rgb(0,0,0);font-size:13.3333px">0x100=C2=A0</sp=
an>from=C2=A0<span style=3D"color:rgb(0,0,0);font-size:13.3333px">0x110</sp=
an></div></div>

--00000000000045baba05987bdde1--


From nobody Fri Nov 29 15:52:41 2019
Return-Path: <rch@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 C795F120133 for <quic@ietfa.amsl.com>; Fri, 29 Nov 2019 15:52:39 -0800 (PST)
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, DKIMWL_WL_MED=-0.001, 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_HELO_NONE=0.001, SPF_PASS=-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 cKfJ-0_jsyUa for <quic@ietfa.amsl.com>; Fri, 29 Nov 2019 15:52:38 -0800 (PST)
Received: from mail-wr1-x435.google.com (mail-wr1-x435.google.com [IPv6:2a00:1450:4864:20::435]) (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 DA64B120033 for <quic@ietf.org>; Fri, 29 Nov 2019 15:52:37 -0800 (PST)
Received: by mail-wr1-x435.google.com with SMTP id z7so33555189wrl.13 for <quic@ietf.org>; Fri, 29 Nov 2019 15:52:37 -0800 (PST)
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=iXPxZ3Wu65X9eiZ9WyVCuR00ptiRDJyeDmqpWPNE6jU=; b=nrOVNa+WPW8K/SLEoIu9sGQFvYNi6S2sYUKksmyUtpIJWDXZVSc6JE1Dd976TKxplR bFOWqUNXNLyGpfZjZhsyoVSXR0aRipCdKDfvheeuavZG030DLNN26KPVgunPqX5b2mzi aUqGP2+AYrOn3IPgzW5sJ7x6gft8jWvGnAncrwOXMYUpEVPOu72/jYK3vTHaxS1z2Qzv mlIY24CqlKG74Odycllcpap1zlCD5THsrnKDeh7pazD6d831Clqri4cy/fwp6FmgIhiA 7n86c2W52QE0WNfyNceE1Z031Xlzn53jubqQwLgaDSFGjUouCimmRU2zJkgLtOaK4xsB CllA==
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=iXPxZ3Wu65X9eiZ9WyVCuR00ptiRDJyeDmqpWPNE6jU=; b=td0Hrl++o8UeoOaCmfEaXuh76VOXWjmYc7LHyX7cFqHZk2u/faQ8WzPj+jS/qFjf9M 7PbuLYaoSQUgp6LShLAO+7fJunPaKY0rhJSU+OgHfR+uFIFIjvu/fkZLT/VRrktDFAK5 WCy31Zrgwwa1IFHYfGg/jTTqwdy2bJH/I7ESWXJX9UyHARWRPTKZRxDH0c2htt5AtCRE PAW3UidtIDRfibryUpCSNsgc2G1yECFbR25tz+DOiGqb9S9A6MTqrvtId56nS6Ym+Md0 IhfaahkiIvBepJ6rUACzIJBvFmbwS2Td8oKQD/rZJmJ+wNIg+Fh3WsWDFXXPVu4Ncd54 RZFQ==
X-Gm-Message-State: APjAAAXEjc0PNC7H2sJh0Ocb0gYCuxrECRI/Edt1Bk4Mv+dE+fd8bh98 mQlNpXAXxm0lNPljzKWe/Rm8RorFMqTepcchmyVA2w==
X-Google-Smtp-Source: APXvYqxIkMjq8CSoZ6Rsbj3slj8mybhutvAOe1uqB1K/5N9QIt42nyg0xxLMocJazrZBBrEp4jOF4QcDYugv2eoUHxE=
X-Received: by 2002:a05:6000:50:: with SMTP id k16mr55402801wrx.145.1575071555833;  Fri, 29 Nov 2019 15:52:35 -0800 (PST)
MIME-Version: 1.0
References: <CAG9+TpZgm1zbW2Zq9oPCprmgUr-Rh29RTmGyEcVfE+T-i1WvaA@mail.gmail.com>
In-Reply-To: <CAG9+TpZgm1zbW2Zq9oPCprmgUr-Rh29RTmGyEcVfE+T-i1WvaA@mail.gmail.com>
From: Ryan Hamilton <rch@google.com>
Date: Fri, 29 Nov 2019 15:52:24 -0800
Message-ID: <CAJ_4DfTk11C60LsRhv8Fr_jypxQiweyx0hQnumY_fQHBey-42Q@mail.gmail.com>
Subject: Re: How to avoid kernel's receive buff full , then UDP packet dropped by kernel?
To: Jiuhai Zhang <jiuhai.zhang@gmail.com>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000009558bd059884ecb1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/0p3_hM-3C2oo6xk233aYarTfsng>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 29 Nov 2019 23:52:40 -0000

--0000000000009558bd059884ecb1
Content-Type: text/plain; charset="UTF-8"

On the server side of a QUIC connection, the UDP socket (and hence the
kernel receive buffer) is shared across multiple connections. As such it'd
be incredibly complicated to come up with a system to handle this and would
likely result in unnecessarily throttling throughput. On the client side
(where there is once QUIC connection per socket) this is unlikely to happen
if the receive buffer is larger than the BDP of the link. Of course, in
reality, if the application is reading from the socket frequently enough,
this is likely a non-issue.

On Fri, Nov 29, 2019 at 4:53 AM Jiuhai Zhang <jiuhai.zhang@gmail.com> wrote:

> Is there any good idea to solve this? How can we do flow control like TCP
> receive window size? User space can not get how many receive buff is used
>

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

<div dir=3D"ltr"><div class=3D"gmail_default" style=3D"font-family:trebuche=
t ms,sans-serif">On the server side of a QUIC connection, the UDP socket (a=
nd hence the kernel receive buffer) is shared across multiple connections. =
As such it&#39;d be incredibly complicated to come up with a system to hand=
le this and would likely result in unnecessarily throttling throughput. On =
the client side (where there is once QUIC connection per socket) this is un=
likely to happen if the receive=C2=A0buffer is larger than the BDP of the l=
ink. Of course, in reality, if the application is reading from the socket f=
requently enough, this is likely a non-issue.=C2=A0</div></div><br><div cla=
ss=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Nov 29, 20=
19 at 4:53 AM Jiuhai Zhang &lt;<a href=3D"mailto:jiuhai.zhang@gmail.com">ji=
uhai.zhang@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quo=
te" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204=
);padding-left:1ex"><div dir=3D"ltr">Is there any good idea to solve this? =
How can we do flow control like TCP receive window size? User space can not=
 get how many receive buff is used</div>
</blockquote></div>

--0000000000009558bd059884ecb1--


From nobody Fri Nov 29 16:33:27 2019
Return-Path: <matt.joras@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 12F7A1200D6 for <quic@ietfa.amsl.com>; Fri, 29 Nov 2019 16:33:26 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 pvTL2pkImRbQ for <quic@ietfa.amsl.com>; Fri, 29 Nov 2019 16:33:24 -0800 (PST)
Received: from mail-vs1-xe2f.google.com (mail-vs1-xe2f.google.com [IPv6:2607:f8b0:4864:20::e2f]) (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 3BBDC120033 for <quic@ietf.org>; Fri, 29 Nov 2019 16:33:24 -0800 (PST)
Received: by mail-vs1-xe2f.google.com with SMTP id y195so6772690vsy.5 for <quic@ietf.org>; Fri, 29 Nov 2019 16:33:24 -0800 (PST)
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=plrksV4ijFGKXnvXAcOD2YKFIWQcUvuWyGnokipry/Y=; b=Ul9kgFfFUKf56i8l0y0azNxB0ITK7BseliwbQmB2ebvg8pplpo6NIuF9qguBBwDQ9J hNPOTh3I35XnikgAmqJcZRQ/TfxCSuYlKuhj6xoVgTytEH3bCZfDyrfq3EnjcXf8t5L4 ITTP/xJhIsT5AvuLOe0Vd4pHPKO1ADFIoBRzm4rdz9r+lKeVGk8lFwvSG3n4p64QblqF byEAcdpKIvpmZC/r8KPmkzKCIDvACDX7co7AAauPvBYK9O4aTfhcoa750oD4dPxMJ7cF 6kD9mwA2oTZKKv1U0BammpAr/qKV53/iir7PqABU4VOZkfI/n22FfLboaVHD8wxZwDT/ kSNw==
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=plrksV4ijFGKXnvXAcOD2YKFIWQcUvuWyGnokipry/Y=; b=o38wAHAH+IRbRLT89YKgsd7RS0lH3QSGtO0pZyjsp27XIqWCagIe0UVE3CcIgRM8PP kabgPJMyRYmEGC0OqP+f/xuzyyDmJoVIV3DMdrWx1f036PWRkg6aOvKG+i/+6v/HWZjr ZqFhGPnVFdd1v1CjsAFTsSDW0etMp5FvbV8x6ES5ive1M5gaVwPSb/LbhLwDZyAx3Zlq cSJ3LdfV6pno5+2BZDxlNraqtNb01gJY1IoT5KA3wrH+n+HOmfC9L8xXntuPpnvB0TgS dtRh5dgqwWHuAdshconbqP+1HLws3Qb7B2Ydilucsgd/ZwCTkHVDqPjQWKOJbBNsuJ4V ilZQ==
X-Gm-Message-State: APjAAAXV9WOsXkpSMp2kZCT6j1E0vr4sM0sMof7WnUiCQLOJ9M1RWu8i sbE9SjIVw96GwQanS5deQZToYkn+n4NLXDlL/8Q=
X-Google-Smtp-Source: APXvYqzD4vdVzhtU2bYyx/ZrjI2AF4e6ldwJlJbqBgk1cJXycGR9KmK0JFlGdhY0PCP5tIePAYyTk8ltteEi0KIsFkg=
X-Received: by 2002:a67:ee49:: with SMTP id g9mr34481979vsp.105.1575074002860;  Fri, 29 Nov 2019 16:33:22 -0800 (PST)
MIME-Version: 1.0
References: <CAG9+TpaFDpoPCXkLVBRMYUF4sCcFqzEeuNSFX4n2VY3A0LN09A@mail.gmail.com>
In-Reply-To: <CAG9+TpaFDpoPCXkLVBRMYUF4sCcFqzEeuNSFX4n2VY3A0LN09A@mail.gmail.com>
From: Matt Joras <matt.joras@gmail.com>
Date: Fri, 29 Nov 2019 16:33:11 -0800
Message-ID: <CADdTf+jOgQK-A5kX+ubiY+XdW9n26KLyzxicW-9iLEDMLoF1jA@mail.gmail.com>
Subject: Re: CRYPTO_ERROR (0x1XX) conflict with HTTP/3 Error Codes
To: Jiuhai Zhang <jiuhai.zhang@gmail.com>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/eOt6crVxNs9c6IJtgxc0NtxYCBw>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 30 Nov 2019 00:33:26 -0000

On Fri, Nov 29, 2019 at 5:04 AM Jiuhai Zhang <jiuhai.zhang@gmail.com> wrote:
>
> Transport error CRYPTO_ERROR (0x1XX)
> HTTP/3 error range 0x100 from 0x110
They're different spaces, in the case of a close they are
distinguished by which variant of the CONNECTION_CLOSE frame carries
the error. See:
https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#connection-errors
https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#frame-connection-close
https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#error-codes
https://quicwg.org/base-drafts/draft-ietf-quic-transport.html#app-error-codes


From nobody Sat Nov 30 23:32:39 2019
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 062CB120048 for <quic@ietfa.amsl.com>; Sat, 30 Nov 2019 23:32:38 -0800 (PST)
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, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=SC5Dc54m; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=cUjZzX2O
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 TWBGcOExRetN for <quic@ietfa.amsl.com>; Sat, 30 Nov 2019 23:32:35 -0800 (PST)
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 F25A212001A for <quic@ietf.org>; Sat, 30 Nov 2019 23:32:34 -0800 (PST)
Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailout.nyi.internal (Postfix) with ESMTP id 6FEB922A4F for <quic@ietf.org>; Sun,  1 Dec 2019 02:32:33 -0500 (EST)
Received: from mailfrontend2 ([10.202.2.163]) by compute4.internal (MEProxy); Sun, 01 Dec 2019 02:32:33 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:from:to:subject:message-id:date; s= fm1; bh=1GSXH328OJ8b4KWPloHERgQE0v6p/1a9jaebU7TCHOI=; b=SC5Dc54m DxUZ+znaCzlGYpq73qOsBcWzSQaAYICOQVTHOmAUc3cLUGtKAyx75RcPF3zVwDKE SU6sd4i2wiIbnGOeBl2Iy9sscHuEu1qjeEEW5EZIl1TC+bycCZqWZjTxTjdZVvOi 6Kc3i+HQchwhFjuN/3Ago84NFGMpHu9Phg7EZuGIVL+Bdhd57xTxgXWHCXlexr6h R5DOibzcRdsvF29+j1O00KBoccqGZnCH6GykQb7tto2BAWsfKV830d2gQtvRsUfW a6krn7siyXhCbFgvqj6Z5c60YLn6MNPcuIgIyzIl0oydNIfux0WCGNXZaXRpsDVS qqqs3AMrdTlJQA==
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-proxy:x-me-proxy:x-me-sender :x-me-sender:x-sasl-enc; s=fm1; bh=1GSXH328OJ8b4KWPloHERgQE0v6p/ 1a9jaebU7TCHOI=; b=cUjZzX2OmDI/ntchDVDiediOEZIKS8wX5xk9LqObA3WnL 8r4G9lsVqHunXyU/UQ9zfsi6nAfs16PBhR6ajQr5vqCkjN2Y9Ta974enjy+nBkcB IMJ9L9IfERy6kwVFWeO4DLeJcQhZyu2OJ4eQ4E9deEF2UjXISo2A3bEy5v8176Hj gz7cBFIdUSNUkQECDw/f87YQU8aPt+0zJmY3x9xz5u2amNORRZXsMlXiGa42olm+ BOb7JjCmT08pvKCX+JklFUx4ZRgu2BvtNKGdWM6oM0Inb6u747oWVDT+9+iP2uOa WOfsJfbAR5A/TRtXw2hoQ6YelS/lVIT95vzu82zww==
X-ME-Sender: <xms:kWzjXTsdPkMoCpzq0I3DQ-FAxFSoLYMcl2yS7TYifTqxR7nzUWDbLA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudejvddguddtjecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecunecujfgurheptggghffvufesrgdttdertddtje enucfhrhhomheptfgvphhoshhithhorhihucettghtihhvihhthicuufhumhhmrghrhicu uehothcuoeguohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvghtqeenucffohhmrghinh epghhithhhuhgsrdgtohhmnecukfhppedufeejrdduudejrdejuddrudekfeenucfrrghr rghmpehmrghilhhfrhhomhepughopghnohhtpghrvghplhihsehmnhhothdrnhgvthenuc evlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:kWzjXbq59E6JaR_gSxbd6GbfImNXTNtsoqrlkRMoCvtTmzVEvFSi2Q> <xmx:kWzjXbIm56j001qtMDUM-oVS7BOECJpURpemWc2pDm0u3t-HhfqJNg> <xmx:kWzjXa7PybnqJFIyz9dC_Mn5Kzzl1DyDK-O2KhwINIxugMTrjAeYDg> <xmx:kWzjXfEi68qrIZgmf6nQB9Es085y0Z7YHhZO3UR4ocCF_RNmEHkcGA>
Received: from [10.1.0.4] (unknown [137.117.71.183]) by mail.messagingengine.com (Postfix) with ESMTPA id 03FCD30600CB for <quic@ietf.org>; Sun,  1 Dec 2019 02:32:33 -0500 (EST)
Content-Type: multipart/alternative; boundary="===============4244850175753052454=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: quic@ietf.org
Subject: Weekly github digest ( Activity Summary)
Message-Id: <20191201073233.03FCD30600CB@mailuser.nyi.internal>
Date: Sun,  1 Dec 2019 02:32:33 -0500 (EST)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/VsQ6diaUR3MCAGI7D8OhWHerAEE>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
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, 01 Dec 2019 07:32:38 -0000

--===============4244850175753052454==
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 (+3/-6/=F0=9F=92=AC48)
  3 issues created:
  - Ambiguous wording about error codes in HTTP/3 (by LPardue)
    https://github.com/quicwg/base-drafts/issues/3276=20
  - Why are there two ways of associating push with requests? (by kazuho)
    https://github.com/quicwg/base-drafts/issues/3275=20
  - Encrypting Retry token (by martinthomson)
    https://github.com/quicwg/base-drafts/issues/3274 [-tls]=20

  11 issues received 48 new comments:
  - #3276 Ambiguous wording about error codes in HTTP/3 (2 by LPardue, kazu=
ho)
    https://github.com/quicwg/base-drafts/issues/3276=20
  - #3275 Why are there two ways of associating push with requests? (20 by =
LPardue, RyanAtGoogle, dtikhonov, kazuho, martinthomson)
    https://github.com/quicwg/base-drafts/issues/3275 [-http]=20
  - #3274 Encrypting Retry token (5 by kazuho, martinthomson)
    https://github.com/quicwg/base-drafts/issues/3274 [-tls]=20
  - #3273 HTTP/3 references QUIC Stream IDs directly, allowing illegal refe=
rences (7 by LPardue, RyanAtGoogle, dtikhonov, ianswett, kazuho, martinthom=
son)
    https://github.com/quicwg/base-drafts/issues/3273 [-http] [design]=20
  - #3272 pto_count should be reset when dropping a packet number space (5 =
by ianswett, janaiyengar, kazuho)
    https://github.com/quicwg/base-drafts/issues/3272 [-recovery] [design] =

  - #3265 Add capability for sending HTTP metadata (trailer fields) in mid-=
stream (1 by mnot)
    https://github.com/quicwg/base-drafts/issues/3265 [-http] [design]=20
  - #3247 I am concerned the congestion control text is too permissive. (1 =
by janaiyengar)
    https://github.com/quicwg/base-drafts/issues/3247 [-recovery]=20
  - #3244 Can we make a normative ref to  RFC8085? (1 by janaiyengar)
    https://github.com/quicwg/base-drafts/issues/3244 [-recovery]=20
  - #3216 Flow Control Tuning (2 by gorryfair, martinthomson)
    https://github.com/quicwg/base-drafts/issues/3216 [-transport]=20
  - #3212 Remove handshake confirmed test for KeyUpdate (2 by kazuho, marti=
nthomson)
    https://github.com/quicwg/base-drafts/issues/3212 [-tls] [design]=20
  - #3142 It is unspecified how a server sends Handshake packets during / a=
fter migration (2 by kazuho, martinthomson)
    https://github.com/quicwg/base-drafts/issues/3142 [-transport]=20

  6 issues closed:
  - reordered NEW_CONNECTION_ID frames with retired sequence numbers should=
n't be used https://github.com/quicwg/base-drafts/issues/3194 [-transport] =
[design] [has-consensus]=20
  - NEW_TOKEN and Retry tokens must be distinguishable https://github.com/q=
uicwg/base-drafts/issues/3127 [-transport] [design] [has-consensus]=20
  - Application close should be disallowed in Initial or Handshake https://=
github.com/quicwg/base-drafts/issues/3158 [-transport] [design] [has-consen=
sus]=20
  - The method of identifying "the same server" https://github.com/quicwg/b=
ase-drafts/issues/3155 [-transport] [design] [has-consensus]=20
  - Invalid CONNECTION_CLOSE frames https://github.com/quicwg/base-drafts/i=
ssues/2475 [-transport] [design] [has-consensus]=20
  - Backoff of CONNECTION_CLOSE needs to be a MUST https://github.com/quicw=
g/base-drafts/issues/3095 [-transport] [design] [has-consensus]=20



Pull requests
-------------
* quicwg/base-drafts (+0/-6/=F0=9F=92=AC12)
  5 pull requests received 12 new comments:
  - #3266 Prevent Idle Timeout while Blocked (1 by nibanks)
    https://github.com/quicwg/base-drafts/pull/3266 [-transport]=20
  - #3248 Fix congestion control permissiveness (6 by gorryfair, hardie, ia=
nswett, janaiyengar, martinthomson, mirjak)
    https://github.com/quicwg/base-drafts/pull/3248 [-recovery]=20
  - #3239 HTTP: Tweak wording about unknown error codes (2 by LPardue, jana=
iyengar)
    https://github.com/quicwg/base-drafts/pull/3239=20
  - #3201 enforce the active_connection_id_limit (1 by martinthomson)
    https://github.com/quicwg/base-drafts/pull/3201 [-transport] [design]=20
  - #3120 Add retry integrity tag (2 by huitema, martinthomson)
    https://github.com/quicwg/base-drafts/pull/3120 [-tls] [-transport] [de=
sign]=20

  6 pull requests merged:
  - handle reordered NEW_CONNECTION_ID frames
    https://github.com/quicwg/base-drafts/pull/3202 [-transport] [design]=20
  - Mandatory distinction between token types
    https://github.com/quicwg/base-drafts/pull/3128 [-transport] [design]=20
  - Forbid use of application-level close in Initial, Handshake packets
    https://github.com/quicwg/base-drafts/pull/3164 [-transport] [design]=20
  - clarify the scope of a NEW_TOKEN token
    https://github.com/quicwg/base-drafts/pull/3156 [-transport] [design]=20
  - Bad CONNECTION_CLOSE isn't special
    https://github.com/quicwg/base-drafts/pull/3231 [-transport] [design]=20
  - Backoff on CONNECTION_CLOSE
    https://github.com/quicwg/base-drafts/pull/3157 [-transport] [design]=20


Repositories tracked by this digest:
-----------------------------------
* https://github.com/quicwg/base-drafts

--===============4244850175753052454==
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 ( Activity Summary)</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 December 01, 2019</h1>

<p>Events without label "editorial"</p>

<h2>Issues</h2>

<h3>quicwg/base-drafts (+3/-6/=F0=9F=92=AC48)</h3>
  <p class=3D"new">3 issues created:</p>
  <ul>
  <li>#3276 <a href=3D"https://github.com/quicwg/base-drafts/issues/3276">A=
mbiguous wording about error codes in HTTP/3</a> (by LPardue) </li>
 =20
  <li>#3275 <a href=3D"https://github.com/quicwg/base-drafts/issues/3275">W=
hy are there two ways of associating push with requests?</a> (by kazuho) </=
li>
 =20
  <li>#3274 <a href=3D"https://github.com/quicwg/base-drafts/issues/3274">E=
ncrypting Retry token</a> (by martinthomson) <span class=3D"label" style=3D=
"background-color: #fbca04; color: #000000">-tls</span> </li>
  </ul>

  <p>11 issues received 48 new comments:</p>
  <ul>
  <li>#3276 <a href=3D"https://github.com/quicwg/base-drafts/issues/3276">A=
mbiguous wording about error codes in HTTP/3</a> (2 by LPardue, kazuho) </l=
i>
 =20
  <li>#3275 <a href=3D"https://github.com/quicwg/base-drafts/issues/3275">W=
hy are there two ways of associating push with requests?</a> (20 by LPardue=
, RyanAtGoogle, dtikhonov, kazuho, martinthomson) <span class=3D"label" sty=
le=3D"background-color: #fbca04; color: #000000">-http</span> </li>
 =20
  <li>#3274 <a href=3D"https://github.com/quicwg/base-drafts/issues/3274">E=
ncrypting Retry token</a> (5 by kazuho, martinthomson) <span class=3D"label=
" style=3D"background-color: #fbca04; color: #000000">-tls</span> </li>
 =20
  <li>#3273 <a href=3D"https://github.com/quicwg/base-drafts/issues/3273">H=
TTP/3 references QUIC Stream IDs directly, allowing illegal references</a> =
(7 by LPardue, RyanAtGoogle, dtikhonov, ianswett, kazuho, martinthomson) <s=
pan class=3D"label" style=3D"background-color: #fbca04; color: #000000">-ht=
tp</span> <span class=3D"label" style=3D"background-color: #1d76db; color: =
#ffffff">design</span> </li>
 =20
  <li>#3272 <a href=3D"https://github.com/quicwg/base-drafts/issues/3272">p=
to_count should be reset when dropping a packet number space</a> (5 by ians=
wett, janaiyengar, kazuho) <span class=3D"label" style=3D"background-color:=
 #fbca04; color: #000000">-recovery</span> <span class=3D"label" style=3D"b=
ackground-color: #1d76db; color: #ffffff">design</span> </li>
 =20
  <li>#3265 <a href=3D"https://github.com/quicwg/base-drafts/issues/3265">A=
dd capability for sending HTTP metadata (trailer fields) in mid-stream</a> =
(1 by mnot) <span class=3D"label" style=3D"background-color: #fbca04; color=
: #000000">-http</span> <span class=3D"label" style=3D"background-color: #1=
d76db; color: #ffffff">design</span> </li>
 =20
  <li>#3247 <a href=3D"https://github.com/quicwg/base-drafts/issues/3247">I=
 am concerned the congestion control text is too permissive.</a> (1 by jana=
iyengar) <span class=3D"label" style=3D"background-color: #fbca04; color: #=
000000">-recovery</span> </li>
 =20
  <li>#3244 <a href=3D"https://github.com/quicwg/base-drafts/issues/3244">C=
an we make a normative ref to  RFC8085?</a> (1 by janaiyengar) <span class=
=3D"label" style=3D"background-color: #fbca04; color: #000000">-recovery</s=
pan> </li>
 =20
  <li>#3216 <a href=3D"https://github.com/quicwg/base-drafts/issues/3216">F=
low Control Tuning</a> (2 by gorryfair, martinthomson) <span class=3D"label=
" style=3D"background-color: #fbca04; color: #000000">-transport</span> </l=
i>
 =20
  <li>#3212 <a href=3D"https://github.com/quicwg/base-drafts/issues/3212">R=
emove handshake confirmed test for KeyUpdate</a> (2 by kazuho, martinthomso=
n) <span class=3D"label" style=3D"background-color: #fbca04; color: #000000=
">-tls</span> <span class=3D"label" style=3D"background-color: #1d76db; col=
or: #ffffff">design</span> </li>
 =20
  <li>#3142 <a href=3D"https://github.com/quicwg/base-drafts/issues/3142">I=
t is unspecified how a server sends Handshake packets during / after migrat=
ion</a> (2 by kazuho, martinthomson) <span class=3D"label" style=3D"backgro=
und-color: #fbca04; color: #000000">-transport</span> </li>
  </ul>

  <p>6 issues closed:</p>
  <ul>
  <li>#3194 <a href=3D"https://github.com/quicwg/base-drafts/issues/3194">r=
eordered NEW_CONNECTION_ID frames with retired sequence numbers shouldn&#x2=
7;t be used</a> <span class=3D"label" style=3D"background-color: #fbca04; c=
olor: #000000">-transport</span> <span class=3D"label" style=3D"background-=
color: #1d76db; color: #ffffff">design</span> <span class=3D"label" style=
=3D"background-color: #5319e7; color: #ffffff">has-consensus</span> </li>
 =20
  <li>#3127 <a href=3D"https://github.com/quicwg/base-drafts/issues/3127">N=
EW_TOKEN and Retry tokens must be distinguishable</a> <span class=3D"label"=
 style=3D"background-color: #fbca04; color: #000000">-transport</span> <spa=
n class=3D"label" style=3D"background-color: #1d76db; color: #ffffff">desig=
n</span> <span class=3D"label" style=3D"background-color: #5319e7; color: #=
ffffff">has-consensus</span> </li>
 =20
  <li>#3158 <a href=3D"https://github.com/quicwg/base-drafts/issues/3158">A=
pplication close should be disallowed in Initial or Handshake</a> <span cla=
ss=3D"label" style=3D"background-color: #fbca04; color: #000000">-transport=
</span> <span class=3D"label" style=3D"background-color: #1d76db; color: #f=
fffff">design</span> <span class=3D"label" style=3D"background-color: #5319=
e7; color: #ffffff">has-consensus</span> </li>
 =20
  <li>#3155 <a href=3D"https://github.com/quicwg/base-drafts/issues/3155">T=
he method of identifying &quot;the same server&quot;</a> <span class=3D"lab=
el" style=3D"background-color: #fbca04; color: #000000">-transport</span> <=
span class=3D"label" style=3D"background-color: #1d76db; color: #ffffff">de=
sign</span> <span class=3D"label" style=3D"background-color: #5319e7; color=
: #ffffff">has-consensus</span> </li>
 =20
  <li>#2475 <a href=3D"https://github.com/quicwg/base-drafts/issues/2475">I=
nvalid CONNECTION_CLOSE frames</a> <span class=3D"label" style=3D"backgroun=
d-color: #fbca04; color: #000000">-transport</span> <span class=3D"label" s=
tyle=3D"background-color: #1d76db; color: #ffffff">design</span> <span clas=
s=3D"label" style=3D"background-color: #5319e7; color: #ffffff">has-consens=
us</span> </li>
 =20
  <li>#3095 <a href=3D"https://github.com/quicwg/base-drafts/issues/3095">B=
ackoff of CONNECTION_CLOSE needs to be a MUST</a> <span class=3D"label" sty=
le=3D"background-color: #fbca04; color: #000000">-transport</span> <span cl=
ass=3D"label" style=3D"background-color: #1d76db; color: #ffffff">design</s=
pan> <span class=3D"label" style=3D"background-color: #5319e7; color: #ffff=
ff">has-consensus</span> </li>
  </ul>



<h2>Pull requests</h2>
<h3>quicwg/base-drafts (+0/-6/=F0=9F=92=AC12)</h3>

  <p>5 pull requests received 12 new comments:</p>
  <ul>
  <li>#3266 <a href=3D"https://github.com/quicwg/base-drafts/pull/3266">Pre=
vent Idle Timeout while Blocked</a> (1 by nibanks) <span class=3D"label" st=
yle=3D"background-color: #fbca04; color: #000000">-transport</span> </li>
 =20
  <li>#3248 <a href=3D"https://github.com/quicwg/base-drafts/pull/3248">Fix=
 congestion control permissiveness</a> (6 by gorryfair, hardie, ianswett, j=
anaiyengar, martinthomson, mirjak) <span class=3D"label" style=3D"backgroun=
d-color: #fbca04; color: #000000">-recovery</span> </li>
 =20
  <li>#3239 <a href=3D"https://github.com/quicwg/base-drafts/pull/3239">HTT=
P: Tweak wording about unknown error codes</a> (2 by LPardue, janaiyengar) =
</li>
 =20
  <li>#3201 <a href=3D"https://github.com/quicwg/base-drafts/pull/3201">enf=
orce the active_connection_id_limit</a> (1 by martinthomson) <span class=3D=
"label" style=3D"background-color: #fbca04; color: #000000">-transport</spa=
n> <span class=3D"label" style=3D"background-color: #1d76db; color: #ffffff=
">design</span> </li>
 =20
  <li>#3120 <a href=3D"https://github.com/quicwg/base-drafts/pull/3120">Add=
 retry integrity tag</a> (2 by huitema, martinthomson) <span class=3D"label=
" style=3D"background-color: #fbca04; color: #000000">-tls</span> <span cla=
ss=3D"label" style=3D"background-color: #fbca04; color: #000000">-transport=
</span> <span class=3D"label" style=3D"background-color: #1d76db; color: #f=
fffff">design</span> </li>
  </ul>

  <p>6 pull requests merged:</p>
  <ul>
  <li>#3202 <a href=3D"https://github.com/quicwg/base-drafts/pull/3202">han=
dle reordered NEW_CONNECTION_ID frames</a> <span class=3D"label" style=3D"b=
ackground-color: #fbca04; color: #">-transport</span> <span class=3D"label"=
 style=3D"background-color: #1d76db; color: #">design</span> </li>
 =20
  <li>#3128 <a href=3D"https://github.com/quicwg/base-drafts/pull/3128">Man=
datory distinction between token types</a> <span class=3D"label" style=3D"b=
ackground-color: #fbca04; color: #">-transport</span> <span class=3D"label"=
 style=3D"background-color: #1d76db; color: #">design</span> </li>
 =20
  <li>#3164 <a href=3D"https://github.com/quicwg/base-drafts/pull/3164">For=
bid use of application-level close in Initial, Handshake packets</a> <span =
class=3D"label" style=3D"background-color: #fbca04; color: #">-transport</s=
pan> <span class=3D"label" style=3D"background-color: #1d76db; color: #">de=
sign</span> </li>
 =20
  <li>#3156 <a href=3D"https://github.com/quicwg/base-drafts/pull/3156">cla=
rify the scope of a NEW_TOKEN token</a> <span class=3D"label" style=3D"back=
ground-color: #fbca04; color: #">-transport</span> <span class=3D"label" st=
yle=3D"background-color: #1d76db; color: #">design</span> </li>
 =20
  <li>#3231 <a href=3D"https://github.com/quicwg/base-drafts/pull/3231">Bad=
 CONNECTION_CLOSE isn&#x27;t special</a> <span class=3D"label" style=3D"bac=
kground-color: #fbca04; color: #">-transport</span> <span class=3D"label" s=
tyle=3D"background-color: #1d76db; color: #">design</span> </li>
 =20
  <li>#3157 <a href=3D"https://github.com/quicwg/base-drafts/pull/3157">Bac=
koff on CONNECTION_CLOSE</a> <span class=3D"label" style=3D"background-colo=
r: #fbca04; color: #">-transport</span> <span class=3D"label" style=3D"back=
ground-color: #1d76db; color: #">design</span> </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>

--===============4244850175753052454==--

