
From nobody Wed Jul  1 01:30:23 2020
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 1FB643A0B1C for <quic@ietfa.amsl.com>; Wed,  1 Jul 2020 01:30:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 NYHEXO6g6p1k for <quic@ietfa.amsl.com>; Wed,  1 Jul 2020 01:30:19 -0700 (PDT)
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 F10263A0B16 for <quic@ietf.org>; Wed,  1 Jul 2020 01:30:18 -0700 (PDT)
Received: from GF-MacBook-Pro.lan (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id DC0501B00331; Wed,  1 Jul 2020 09:30:15 +0100 (BST)
Subject: WGLC comments: draft-ietf-quic-recovery-29
To: quic@ietf.org
References: <159174926905.11646.1975231547639763889@ietfa.amsl.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <4228f506-9b96-4872-177b-120be77920f8@erg.abdn.ac.uk>
Date: Wed, 1 Jul 2020 09:30:15 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <159174926905.11646.1975231547639763889@ietfa.amsl.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/jFRIW1Yh-VOqdbFovLfcutwkdt4>
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, 01 Jul 2020 08:30:22 -0000

This is a WGLC review of draft-ietf-quic-recovery-29. This version of 
the specification seems mature, and this email includes some WGLC 
comments, preceded by some things that I think are issues.

(Editors I could raise a set of github issues for the issues, please 
advise how you would like to proceed).

Best wishes,

Gorry

ISSUE:

8.2. Traffic Analysis
/Packets that carry only ACK frames can be heuristically identified by 
observing packet size. Acknowledgement patterns may expose information 
about link characteristics or application behavior. Endpoints can use 
PADDING frames or bundle acknowledgments with other frames to reduce 
leaked information./
- I think this needs a warning: This could also increase the return path 
traffic, which for asymmetric paths could impact the performance of the 
forward path or of other flows that share a restricted return path.

ISSUE:

/Re-ordering could be more common with QUIC than TCP, because network 
elements cannot observe and fix the order of out-of-order packets./
- They can if they add network-layer sequence numbers, as some 
tunnels/encaps for example can... This seems like an odd statement. Is 
it necessary? If so, please explain more.

ISSUE:
/When a loss or ECN-CE marking is detected, NewReno halves the 
congestion window, sets the slow start threshold to the new congestion 
window, and then enters the recovery period./
- The requirement is that TCP needs to reduce after CE, The RFC series 
does not now say it needs to halve, it could for example follow the 
reduction method specified in RFC8511. e.g. /When a loss or ECN-CE 
marking is detected, the sender must reduce the cwnd. NewReno halves the 
congestion window, sets the slow start threshold to the new congestion 
window, and then enters the recovery period. [RFC8511] specifies an 
alternate cwnd reduction./

ISSUE:
Similar comment in 8.3:
/Though congestion controllers generally treat reports of ECN-CE 
markings as equivalent to loss [RFC8311], the exact response for each 
controller could be different. /
- This does not seem correct. Could I suggest:
/Congestion controllers respond to reports of ECN-CE by reducing their 
rate. Markings can be treated as equivalent to loss [RFC3168], but other 
responses can be specified (e.g. [RFC8511]) [RFC8311]. /

ISSUE:
In B.5,
           // Congestion avoidance.
           congestion_window += max_datagram_size * acked_packet.size
               / congestion_window
- is this calculation correct? I was thinking of what might happen when 
the PMTU is large and the sender generates a sequence of small packets… 
would this result in overestimating cwnd?

ISSUE:

/Endpoints SHOULD use an initial congestion window of 10 times the 
maximum datagram size (max_datagram_size), limited to the larger of 
14720 or twice the maximum datagram size./

- I would like to revist this. We talked in Montreal and at that time I 
understood the equivalence to TCP for the case where a large MSS was 
supported by the path, as per RFC6928. I have since revisited this topic 
and would like to suggest the present IETF advice for TCP is in fact 
wrong for the large initial MSS case, and that this draft should not 
perputate that mistake for QUIC. The issue comes when IW is initialiased 
for a path with a very large PMTU, but that PMTU is not in fact 
supported by the path.

- (i) I observe the TCP case where the path does actually support the 
large PMTU, and a receiver advertises an appropiately large MSS. The 
path then uses the large MSS naturally and all is OK, but stands the 
risk of (ii) below, since the path might not be the same as a previous 
case.

- (ii) if the receiver interface supports a large MTU, and the the 
receiver advertises a large MSS, but the sender does not have a large 
MTU, the advertised large MSS changes the IW, and can vastly increase 
the number of packets in the initial window. This was not intended. It 
should not happen by default and can cause congestion and increase 
latency. This is wrong.

- (iii) if the receiver interface supports a large MTU, and the the 
receiver advertises a large MSS, the sender has a large MTU, but the 
path does not support this large PMTU. Sending with the large MSS causes 
packet loss (or possibly IP-Frag if that was allowed). This was not 
intended, and may well predjudice performance. Retransmission with a 
more appropiate PMTU does not change the IW, which then sends too many 
segments/packets. For TCP it would probably have resulted in a RTO and 
collapsing cwnd. This can cause congestion and increase latency. This is 
wrong.

... So why was this was not seen as a real-life problem. I think the 
advice in RFC6928 should have considered the impact of PMTU failure, but 
I conclude it doesn't normally hurt TCP. At the time this was written, 
few interfaces really did support more than a 1500B MTU (it may still be 
so), and MSS was often effectively limited by the server (sometimes by 
config). For servers that did advertise a larger MSS, or where the path 
supports less than 1500B, then MSS-clamping by routers along a path 
would often have triggered. Still, the sender would normally receiver 
only a feasible advertised MSS.

... QUIC is different :-). There is no middlebox intervention for MSS 
clamping - therefore QUIC is unable to avoid (iii), and likely would be 
impacted by (ii). I therefore suggest that QUIC chooses either to 
eliminate the /or twice the maximum datagram size./ clause, **or** 
provides a requirement that if this datagram size is not confirmed, then 
the IW needs to be limited to 14720 B.

... Finally, I would expect QUIC to perform better if it were to set up 
the connection, and then immediately probe for the larger size, since 
DPLPMTUD is anyway needed to utliise a larger PMTU and avoid 
blackholing. However, I don't think we need to explain this in the ID.

---

NiT:
/ACK delay/ /Ack Delay/  and /ack delay/ are both used, it seems the 
/ACK/ is more consistent with other usage.

NiT (Missing word):
/and are expected to at least as useful in QUIC/and are expected to be 
at least as useful in QUIC/

REF:

/When a PTO timer expires, the PTO backoff MUST be increased, resulting 
in the PTO period being set to twice its current value. The PTO backoff 
factor is reset when an acknowledgement is received, except in the 
following case./
- Please consider a reference to draft-ietf-tcpm-rto-consider-16, which 
provides BCP on use of timers?

The life of a connection that is experiencing consecutive PTOs is 
limited by the endpoint's idle timeout.
- what does /life/ mean here?

/send an Initial packet in a UDP datagram of at least 1200 bytes./
- At what layer is the datagram size measured? Should this be a datagram 
with /payload 1200 bytes/?

/Peers can also use coalesced packets to ensure that each datagram elicits /
- A cross reference would be valuable to the section on /coalesced packets/

/If the sender wants to elicit a faster acknowledgement on PTO, it can 
skip a packet number to eliminate the ack delay./
- Explain: this causes the sender to see an out of order packet, which 
eliminates the ACK delay.

/limited to the larger of 14720/
- Please add the word /bytes/?

/Endpoints MAY ignore the loss of Handshake, 0-RTT, and 1-RTT packets 
that might have arrived before the peer had packet protection keys to 
process those packets. Endpoints MUST NOT ignore the loss of packets 
that were sent after the earliest acknowledged packet in a given packet 
number space./
- Can you clarify what is intended by the word /ignore/? This is in a 
section on CC, so I was hoping that the word ignore meant that the 
endpoint did not need to make a CC change, otherwise it MUST update the CC?

/7.7. Probe Timeout
Probe packets MUST NOT be blocked by the congestion controller. /
- Can you clarify what is intended by the word /blocked/? I was assuming 
the transmission was not constrained by the congestion controller?
- Would these packets consume flow credit, i.e. are they also not flow 
controlled?

7.8. Persistent Congestion
- Could you add text explaining what happens? I think I understand, but 
to be clear. If the persistent congestion persists, then I think the 
congestion is not further reduced, but I would expect the PTO to 
back-off the interval between packets exponentially, is that true? -

Are  appendix A and B normative or informative?

Section A.5.  On Sending a Packet; and section A.6.  On Receiving a 
Datagram. If the intention is to talk about datagrams in A.6, can A.5 
explain that packets are sent in datagrams?

Sections A.8, A.9, A.10  seem to be sender functions. It would perhaps 
avoid doubt to state this.


From nobody Wed Jul  1 04:26:52 2020
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 074A03A0E69 for <quic@ietfa.amsl.com>; Wed,  1 Jul 2020 04:26:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 P3N79r34-bCI for <quic@ietfa.amsl.com>; Wed,  1 Jul 2020 04:26:49 -0700 (PDT)
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 313B23A0E66 for <quic@ietf.org>; Wed,  1 Jul 2020 04:26:49 -0700 (PDT)
Received: by mail-wm1-x32f.google.com with SMTP id j18so21998666wmi.3 for <quic@ietf.org>; Wed, 01 Jul 2020 04:26:49 -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=5+DZMVM4oEjPL5Puxqzn52clEhTaRzpH9V6J8/lFuds=; b=HdylxwdaxGlyGI6dyS9Kf2m1EuNaTP8bHKMiP2RdtOb9of81l2Vdglc/j2XP+NMEG8 FrdvdSNN7nJSKpZjrsZANpTgBzpjF45kxipQA/ORA0WqCe22wgpD4tb48QpHHkK5Z/zK OtcdrlOEEPjLXNlGTB1X9pOaoy+Oa2Twy4z4H2OtQ5Fkxur1hX4XREz4IoA+K4cL2bWJ xMmwBNVEiziXcudtbvY4ShQ31+YQvryhTXz2b/djfU37kt/xZpfk121/P8ukL79+sal5 9Sl9fWYY1leS/fASPG+eCEkEvzUPQuAlRQQVSnV8DluO6AqWIF8rSZ9yJri6AKJ3ggaX om8Q==
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=5+DZMVM4oEjPL5Puxqzn52clEhTaRzpH9V6J8/lFuds=; b=p44mBxVDiXOsMtMX57ajajnmCi8oTZuGBZjqKB6Q0l5EQTDcva4M9NmEqrnbqRoy2I ntt26zebRZ1vHKmNh1HFSFKy/OSAd6Q9fMWEWGbE6QTH2+mEWDdmZ8mljqstHLIxOSOY UP+ve+vgb6Mry9+GgMR3/0Gjsu9oLOFi9iamtHcvFbAUQ5BcL3CDpa+MNGp1WK07V9mE h5By/dVWnqEmVOr1knDVAEjCnylbiYrnIBU662W0UWaQ57OB60PqyTR8uk357gP7ZtvP K+FI0uqnmufefqzfJ6LRNR/mdl/Sa6+DwnHdr0481OQEwQBamHMBqVbSdGyn2ZfMDe+d AFbg==
X-Gm-Message-State: AOAM531AYX3BDnY4JviJ9WZ0gegjBnbpkzC/tWo70I86IRZ/F8FLhBgZ FtxieGoOhLi5K43q7DHDFfEu4OhrYuJoUo3TBHHWlg==
X-Google-Smtp-Source: ABdhPJwHRabio2UDVC/EfSxS7dNA3ZPzjTPGhq9UFx+a5iVSfoNI1sljaP0LoJ2uOL96Si6Y/Xno5IhxKiNL5xbWY3c=
X-Received: by 2002:a1c:9e45:: with SMTP id h66mr1241544wme.15.1593602807171;  Wed, 01 Jul 2020 04:26:47 -0700 (PDT)
MIME-Version: 1.0
References: <CALGR9oZ9u=huobnQig0mMPS=-Fu7Mu3q8GHLTBOxd2W5u0h_kw@mail.gmail.com>
In-Reply-To: <CALGR9oZ9u=huobnQig0mMPS=-Fu7Mu3q8GHLTBOxd2W5u0h_kw@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Wed, 1 Jul 2020 12:26:36 +0100
Message-ID: <CALGR9oa0h3qcFmwqJwfaPQ460ZVpa+URsJmcDKkQuaHwib4Fqg@mail.gmail.com>
Subject: Re: Working Group Last Call: QUIC protocol drafts
To: QUIC WG <quic@ietf.org>
Cc: Lars Eggert <lars@eggert.org>, Mark Nottingham <mnot@mnot.net>
Content-Type: multipart/alternative; boundary="0000000000003c11bd05a95f91f8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/B5HaYlN5NULjc4p0617B69OgZ1M>
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, 01 Jul 2020 11:26:51 -0000

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

Reminder: the QUIC WGLC ends on July 8 2020

If you have review comments please raise them in accordance with the
instructions in the original announcement (attached).

Cheers,
Lucas, on behalf of the QUIC WG chairs

On Wed, Jun 10, 2020 at 2:36 AM Lucas Pardue <lucaspardue.24.7@gmail.com>
wrote:

> Hello,
>
> After more than three and a half years and substantial discussion, all 84=
5
> of the design issues raised against the QUIC protocol drafts have gained
> consensus or have a proposed resolution. In that time the protocol has be=
en
> considerably transformed; it has become more secure, much more widely
> implemented, and has been shown to be interoperable. Both the Chairs and
> the Editors feel that it is ready to proceed in standardisation.
>
> Therefore, this email announces a Working Group Last Call (WGLC) for the
> following QUIC documents:
>
> * QUIC Transport
>   https://tools.ietf.org/html/draft-ietf-quic-transport-29
>
> * QUIC Loss Detection and Congestion Control
>   https://tools.ietf.org/html/draft-ietf-quic-recovery-29
>
> * Using TLS to Secure QUIC
>   https://tools.ietf.org/html/draft-ietf-quic-tls-29
>
> * Version-Independent Properties of QUIC
>   https://tools.ietf.org/html/draft-ietf-quic-invariants-09
>
> * HTTP/3
>   https://tools.ietf.org/html/draft-ietf-quic-http-29
>
> * QPACK Header Compression for HTTP/3
>   https://tools.ietf.org/html/draft-ietf-quic-qpack-16
>
> The WGLC will run for four weeks, ending on 8 July 2020.
>
> As a reminder, we have been operating under the Late-Stage Process; see
> https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md#late-st=
age-process.
> In theory, this means that the contents of the drafts above already have
> consensus. However, the Chairs would like to actively reaffirm that
> consensus and start the process of wider review through a formal WGLC.
>
> Please review the documents above and open issues for your review comment=
s
> in our repository at https://github.com/quicwg/base-drafts. You may also
> send comments to quic@ietf.org.
>
> Issues raised during WGLC will be handled in accordance with the
> Late-Stage Process defined in the Contribution Guidelines (see link above=
).
> Please note that design issues that revisit a topic where there's already
> declared consensus (see
> https://github.com/quicwg/base-drafts/issues?q=3Dis%3Aclosed+label%3Ahas-=
consensus)
> need to provide compelling reasons to warrant reopening the discussion.
>
> As part of this WGLC, we seek consensus on the remaining open design issu=
e
> #3661 =E2=80=9CInclude epoch in the AAD or the nonce?=E2=80=9D (
> https://github.com/quicwg/base-drafts/issues/3661). The proposed
> resolution for this issue is to close with no action, which means that th=
e
> drafts above already reflect this emerging consensus.
>
> Subject to the feedback received during this WGLC, a subsequent smaller
> WGLC may be run in the near future to confirm any changes to the drafts
> made between now and then.
>
> The Applicability and Manageability drafts have some dependencies on the
> core drafts, so we'll run separate WGLCs for them.
>
> Cheers,
>
> Lars, Lucas and Mark
> QUIC WG Chairs
>

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

<div dir=3D"ltr"><div>Reminder: the QUIC WGLC ends on July 8 2020</div><div=
><br></div><div>If you have review comments please raise them in accordance=
 with the instructions in the original announcement (attached).<br></div><d=
iv><br></div><div>Cheers,</div><div>Lucas, on behalf of the QUIC WG chairs<=
br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_att=
r">On Wed, Jun 10, 2020 at 2:36 AM Lucas Pardue &lt;<a href=3D"mailto:lucas=
pardue.24.7@gmail.com">lucaspardue.24.7@gmail.com</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"><div dir=3D"ltr">Hello,<br=
><br>After more than three and a half years and substantial discussion, all=
 845 of the design issues raised against the QUIC protocol drafts have gain=
ed consensus or have a proposed resolution. In that time the protocol has b=
een considerably transformed; it has become more secure, much more widely i=
mplemented, and has been shown to be interoperable. Both the Chairs and the=
 Editors feel that it is ready to proceed in standardisation.<br><br>Theref=
ore, this email announces a Working Group Last Call (WGLC) for the followin=
g QUIC documents:<br><br>* QUIC Transport<br>=C2=A0 <a href=3D"https://tool=
s.ietf.org/html/draft-ietf-quic-transport-29" target=3D"_blank">https://too=
ls.ietf.org/html/draft-ietf-quic-transport-29</a><br><br>* QUIC Loss Detect=
ion and Congestion Control<br>=C2=A0 <a href=3D"https://tools.ietf.org/html=
/draft-ietf-quic-recovery-29" target=3D"_blank">https://tools.ietf.org/html=
/draft-ietf-quic-recovery-29</a><br><br>* Using TLS to Secure QUIC<br>=C2=
=A0 <a href=3D"https://tools.ietf.org/html/draft-ietf-quic-tls-29" target=
=3D"_blank">https://tools.ietf.org/html/draft-ietf-quic-tls-29</a><br><br>*=
 Version-Independent Properties of QUIC<br>=C2=A0 <a href=3D"https://tools.=
ietf.org/html/draft-ietf-quic-invariants-09" target=3D"_blank">https://tool=
s.ietf.org/html/draft-ietf-quic-invariants-09</a><br><br>* HTTP/3<br>=C2=A0=
 <a href=3D"https://tools.ietf.org/html/draft-ietf-quic-http-29" target=3D"=
_blank">https://tools.ietf.org/html/draft-ietf-quic-http-29</a><br><br>* QP=
ACK Header Compression for HTTP/3<br>=C2=A0 <a href=3D"https://tools.ietf.o=
rg/html/draft-ietf-quic-qpack-16" target=3D"_blank">https://tools.ietf.org/=
html/draft-ietf-quic-qpack-16</a><br><br>The WGLC will run for four weeks, =
ending on 8 July 2020.<br><br>As a reminder, we have been operating under t=
he Late-Stage Process; see <a href=3D"https://github.com/quicwg/base-drafts=
/blob/master/CONTRIBUTING.md#late-stage-process" target=3D"_blank">https://=
github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md#late-stage-proces=
s</a><span></span><span></span>. In theory, this means that the contents of=
 the drafts above already have consensus. However, the Chairs would like to=
 actively reaffirm that consensus and start the process of wider review thr=
ough a formal WGLC.<br><br>Please review the documents above and open issue=
s for your review comments in our repository at <a href=3D"https://github.c=
om/quicwg/base-drafts" target=3D"_blank">https://github.com/quicwg/base-dra=
fts</a>. You may also send comments to <a href=3D"mailto:quic@ietf.org" tar=
get=3D"_blank">quic@ietf.org</a>.<br><br>Issues raised during WGLC will be =
handled in accordance with the Late-Stage Process defined in the Contributi=
on Guidelines (see link above). Please note that design issues that revisit=
 a topic where there&#39;s already declared consensus (see <a href=3D"https=
://github.com/quicwg/base-drafts/issues?q=3Dis%3Aclosed+label%3Ahas-consens=
us" target=3D"_blank">https://github.com/quicwg/base-drafts/issues?q=3Dis%3=
Aclosed+label%3Ahas-consensus</a>) need to provide compelling reasons to wa=
rrant reopening the discussion.<br><br>As part of this WGLC, we seek consen=
sus on the remaining open design issue #3661 =E2=80=9CInclude epoch in the =
AAD or the nonce?=E2=80=9D (<a href=3D"https://github.com/quicwg/base-draft=
s/issues/3661" target=3D"_blank">https://github.com/quicwg/base-drafts/issu=
es/3661</a>). The proposed resolution for this issue is to close with no ac=
tion, which means that the drafts above already reflect this emerging conse=
nsus.<br><br>Subject to the feedback received during this WGLC, a subsequen=
t smaller WGLC may be run in the near future to confirm any changes to the =
drafts made between now and then.<br><br>The Applicability and Manageabilit=
y drafts have some dependencies on the core drafts, so we&#39;ll run separa=
te WGLCs for them.<br><br>Cheers,<br><br>Lars, Lucas and Mark<br>QUIC WG Ch=
airs<br></div>
</blockquote></div></div>

--0000000000003c11bd05a95f91f8--


From nobody Wed Jul  1 05:03:51 2020
Return-Path: <Jan.Rueth@comsys.rwth-aachen.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 4DE6A3A0B84 for <quic@ietfa.amsl.com>; Wed,  1 Jul 2020 05:03:49 -0700 (PDT)
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 v_x-U1N6kyYz for <quic@ietfa.amsl.com>; Wed,  1 Jul 2020 05:03:45 -0700 (PDT)
Received: from mail-out-4.itc.rwth-aachen.de (mail-out-4.itc.rwth-aachen.de [IPv6:2a00:8a60:1:e501::5:49]) (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 031E43A0B50 for <quic@ietf.org>; Wed,  1 Jul 2020 05:03:44 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A2CwBACkevxe/xUN4olgDg8BAQEBCQESA?= =?us-ascii?q?QUFAUCBSoFSgTOFeJERiwGRAwsBAQEBAQEBAQEHAS0CBAEBhEcCF4F9AiQ4EwI?= =?us-ascii?q?QAQEGAQEBAQEGBIZUhW8BBAEjEUUFCwIBCBoCJgICAjAVEAIEDoMrgl0gAa5Ng?= =?us-ascii?q?TKFUYQkgQWBDiqMaIIagREnDw2BT34+hBSDPzOCLQSSNYZom2UHgVmBBplCAx2?= =?us-ascii?q?RFY4FsDICAgICCQIVgTM3S4EtcXkBgj9PFwINjicajWY+gSsCBgEHAQEDCXyMf?= =?us-ascii?q?IJGAQE?=
X-IPAS-Result: =?us-ascii?q?A2CwBACkevxe/xUN4olgDg8BAQEBCQESAQUFAUCBSoFSgTO?= =?us-ascii?q?FeJERiwGRAwsBAQEBAQEBAQEHAS0CBAEBhEcCF4F9AiQ4EwIQAQEGAQEBAQEGB?= =?us-ascii?q?IZUhW8BBAEjEUUFCwIBCBoCJgICAjAVEAIEDoMrgl0gAa5NgTKFUYQkgQWBDiq?= =?us-ascii?q?MaIIagREnDw2BT34+hBSDPzOCLQSSNYZom2UHgVmBBplCAx2RFY4FsDICAgICC?= =?us-ascii?q?QIVgTM3S4EtcXkBgj9PFwINjicajWY+gSsCBgEHAQEDCXyMfIJGAQE?=
X-IronPort-AV: E=Sophos;i="5.75,300,1589234400"; d="scan'208";a="76713949"
Received: from lists.comsys.rwth-aachen.de ([137.226.13.21]) by mail-in-4.itc.rwth-aachen.de with ESMTP; 01 Jul 2020 14:03:41 +0200
Received: from messenger-mbx.win.comsys.rwth-aachen.de (messenger-mbx.win.comsys.rwth-aachen.de [137.226.13.43]) by lists.comsys.rwth-aachen.de (Postfix) with ESMTPS id 3A809C08D4; Wed,  1 Jul 2020 14:03:41 +0200 (CEST)
Received: from HERMES-MBX.win.comsys.rwth-aachen.de (2a00:8a60:1014::41) by messenger-mbx.win.comsys.rwth-aachen.de (2a00:8a60:1014::43) with Microsoft SMTP Server (TLS) id 15.0.1347.2; Wed, 1 Jul 2020 14:03:41 +0200
Received: from MESSENGER-MBX.win.comsys.rwth-aachen.de (2a00:8a60:1014::43) by HERMES-MBX.win.comsys.rwth-aachen.de (2a00:8a60:1014::41) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256) id 15.1.2044.4; Wed, 1 Jul 2020 14:03:21 +0200
Received: from MESSENGER-MBX.win.comsys.rwth-aachen.de ([fe80::c109:b55e:3715:5c2c]) by messenger-mbx.win.comsys.rwth-aachen.de ([fe80::c109:b55e:3715:5c2c%12]) with mapi id 15.00.1347.000; Wed, 1 Jul 2020 14:03:40 +0200
From: =?utf-8?B?SmFuIFLDvHRo?= <Jan.Rueth@comsys.rwth-aachen.de>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
CC: "quic@ietf.org" <quic@ietf.org>
Subject: Re: WGLC comments: draft-ietf-quic-recovery-29
Thread-Topic: WGLC comments: draft-ietf-quic-recovery-29
Thread-Index: AQHWT4Hq0QAc7QDSMEe/bbcfG7COfKjyfsSA
Date: Wed, 1 Jul 2020 12:03:40 +0000
Message-ID: <0BEE2393-B27B-49FC-B982-3EA6FB8B0A6C@comsys.rwth-aachen.de>
References: <159174926905.11646.1975231547639763889@ietfa.amsl.com> <4228f506-9b96-4872-177b-120be77920f8@erg.abdn.ac.uk>
In-Reply-To: <4228f506-9b96-4872-177b-120be77920f8@erg.abdn.ac.uk>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [2a00:8a60:1014:10:c5a5:57a9:219:a5d2]
Content-Type: text/plain; charset="utf-8"
Content-ID: <FDD07255F6BA1E49A2176779331800AA@comsys.rwth-aachen.de>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/SbBmgfxCEVaA_CdLfc-zjS8Uxfs>
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, 01 Jul 2020 12:03:49 -0000

SGksDQoNCnRvIGFkZCB0byBHb3JyeeKAmXMgcmV2aWV3Og0KDQoNCj4gSVNTVUU6DQo+IEluIEIu
NSwNCj4gICAgICAgICAgIC8vIENvbmdlc3Rpb24gYXZvaWRhbmNlLg0KPiAgICAgICAgICAgY29u
Z2VzdGlvbl93aW5kb3cgKz0gbWF4X2RhdGFncmFtX3NpemUgKiBhY2tlZF9wYWNrZXQuc2l6ZQ0K
PiAgICAgICAgICAgICAgIC8gY29uZ2VzdGlvbl93aW5kb3cNCj4gLSBpcyB0aGlzIGNhbGN1bGF0
aW9uIGNvcnJlY3Q/IEkgd2FzIHRoaW5raW5nIG9mIHdoYXQgbWlnaHQgaGFwcGVuIHdoZW4gdGhl
IFBNVFUgaXMgbGFyZ2UgYW5kIHRoZSBzZW5kZXIgZ2VuZXJhdGVzIGEgc2VxdWVuY2Ugb2Ygc21h
bGwgcGFja2V0c+KApiB3b3VsZCB0aGlzIHJlc3VsdCBpbiBvdmVyZXN0aW1hdGluZyBjd25kPw0K
PiANCg0KTW9yZW92ZXIsIGFja2VkX3BhY2tldCBpcyBub3QgZGVmaW5lZCB0aGVyZS4NCg0KT25s
eSBhY2tlZF9wYWNrZXRzIChzIGF0IHRoZSBlbmQpIGlzLCBhbmQgZG9lcyA+PnNpemU8PCBkZW5v
dGUgdGhlIG51bWJlciBvZiBwYWNrZXRzIChjb3VudCBtaWdodCBiZSBhIGJldHRlciBuYW1lIGlu
IHRoaXMgY2FzZSkgb3IgdGhlaXIgY3VtdWxhdGl2ZSBzaXplPw0KDQpBbHNvIHRoZSBwYXJ0IHRo
YXQgR29ycnkgcXVvdGVkIGlzIHBlcmZvcm1lZCB3aXRoaW4gdGhlIGxvb3AsIHdoaWNoIHdvdWxk
IG5vdCBsZWFkIHRvIGEgbGluZWFyIGluY3JlYXNlIEkgZ3Vlc3MuDQoNCkkgYmVsaWV2ZSwgaWYg
aXQgcmVmZXJzIHRvIHRoZSBhY3R1YWxseSBhY2tlZCBieXRlcyBhbmQgdGhlIHN0YXRlbWVudCBp
cyBvdXRzaWRlIG9mIHRoZSBsb29wLCBldmVyeXRoaW5nIGlzIGZpbmUgYW5kIHRoZSBwYWNrZXQg
c2l6ZSBvciBhIGxhcmdlIFBNVFUgZG9lcyBub3QgYWZmZWN0IHRoaXMuDQooYWxzbyB0aGUgbGlu
ZSBsZW5ndGggb2YgdGhlIFJGQyBtYWRlIG1lIGxvb2sgNSB0aW1lcyB1bnRpbCBJIHNhdyB0aGUg
4oCcZGl2aWRlZCBieSBjd25k4oCdKQ0KDQoNCj4gSVNTVUU6DQo+IA0KPiAvRW5kcG9pbnRzIFNI
T1VMRCB1c2UgYW4gaW5pdGlhbCBjb25nZXN0aW9uIHdpbmRvdyBvZiAxMCB0aW1lcyB0aGUgbWF4
aW11bSBkYXRhZ3JhbSBzaXplIChtYXhfZGF0YWdyYW1fc2l6ZSksIGxpbWl0ZWQgdG8gdGhlIGxh
cmdlciBvZiAxNDcyMCBvciB0d2ljZSB0aGUgbWF4aW11bSBkYXRhZ3JhbSBzaXplLi8NCj4gDQo+
IC0gSSB3b3VsZCBsaWtlIHRvIHJldmlzdCB0aGlzLiBXZSB0YWxrZWQgaW4gTW9udHJlYWwgYW5k
IGF0IHRoYXQgdGltZSBJIHVuZGVyc3Rvb2QgdGhlIGVxdWl2YWxlbmNlIHRvIFRDUCBmb3IgdGhl
IGNhc2Ugd2hlcmUgYSBsYXJnZSBNU1Mgd2FzIHN1cHBvcnRlZCBieSB0aGUgcGF0aCwgYXMgcGVy
IFJGQzY5MjguIEkgaGF2ZSBzaW5jZSByZXZpc2l0ZWQgdGhpcyB0b3BpYyBhbmQgd291bGQgbGlr
ZSB0byBzdWdnZXN0IHRoZSBwcmVzZW50IElFVEYgYWR2aWNlIGZvciBUQ1AgaXMgaW4gZmFjdCB3
cm9uZyBmb3IgdGhlIGxhcmdlIGluaXRpYWwgTVNTIGNhc2UsIGFuZCB0aGF0IHRoaXMgZHJhZnQg
c2hvdWxkIG5vdCBwZXJwdXRhdGUgdGhhdCBtaXN0YWtlIGZvciBRVUlDLiBUaGUgaXNzdWUgY29t
ZXMgd2hlbiBJVyBpcyBpbml0aWFsaWFzZWQgZm9yIGEgcGF0aCB3aXRoIGEgdmVyeSBsYXJnZSBQ
TVRVLCBidXQgdGhhdCBQTVRVIGlzIG5vdCBpbiBmYWN0IHN1cHBvcnRlZCBieSB0aGUgcGF0aC4N
Cg0KRG8gbmV0d29ya3MgdGhhdCBzdXBwb3J0IGxhcmdlIE1UVXMgdXN1YWxseSBhbHNvIGhhdmUg
bW9yZSBxdWV1ZSBtZW1vcnkgb3Igd2h5IGlzIHRoaXMgbGlua2VkIHRvIHRoZSBQTVRVIGF0IGFs
bD8NCkFwYXJ0IGZyb20gdGhpcywgSSBhZ3JlZSB3aXRoIEdvcnJ5IGhlcmUuDQoNCkJlc3QNCiBK
YW4NCg0K


From nobody Thu Jul  2 04:01:33 2020
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 A15483A0ACD for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 04:01:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=lowentropy.net header.b=L3X+e5S1; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=hqoLe7sg
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id spzxAbMoLkrh for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 04:01:30 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 54F463A0990 for <quic@ietf.org>; Thu,  2 Jul 2020 04:01:30 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 8C66F5C0134 for <quic@ietf.org>; Thu,  2 Jul 2020 07:01:29 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Thu, 02 Jul 2020 07:01:29 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:date:from:to:subject:content-type; s= fm2; bh=u03hA8z3nCq2FaXETB0gXIXyFvDirZR3jtT4wBKnjuQ=; b=L3X+e5S1 ZrDrYLhZnJoWhVRsWmRgyCz1O2lBr8w1VmP47DzX+9G+0iCrMErWuRETwJ2Q1r4E OcFrvXRLmI4N3Fiiob+8st82oJYSQ3Jaq/nCa3YQFgdl5G8nknIBO7K0URDINsYW v37THlpvqceYW3V0CiCQye4ToDU3k5uSgtFfh4Pcc8p3pyajCapqa7G+/c8ok18r mJlO/S4ub4n/MKmGTChz0e7x+M8UpCHwAXF4t4v54/+Ko/NEww8/TtuOiZ7Q1zgA IHNiO5DESkB9IPekUyJCmv+yl785QbomJdHUOZcTB6xL44Chr/PA94C8637yQ9nE NOAijc2D9HbQyw==
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=fm3; bh=u03hA8z3nCq2FaXETB0gXIXyFvDir ZR3jtT4wBKnjuQ=; b=hqoLe7sgDlBcPoyA1vcEQ8U/M1Mk5auOsYgOiaSqiqVZl cn6FsMfxFlJUrxmkV2XZGWpFHdiF3crxG/MGfKHV9edOrG67aXc9Nu0TWhX88An5 dwRsOEdE/mEWPpnyHowABjIQu3mfCM4+4hBP2n1Ky2ZiRp//UCLO4EPXaO5VOEMw GFZhLpdOhnjh+KmkPF6KZj21ndeEJhGnW5laU0n3iuvY40dYG4R1HwnZCHNhr22G 08kbYzpLlQ3hpiqzv3XsLtRSEk4OWJzil2zFrDLwfODcFikgb2hmIXF76mJgYhJQ Mp8iAIlG33xQeOXcNHeY5pCqAxON9gAW0nT3Tb9qw==
X-ME-Sender: <xms:iL79XrPvh_E48DvIs6M_DrmCnpdujb835aSr26_YERQgKaPPwiD7ow>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrtdeggdeftdcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkfffhvffutgesthdtredtre ertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohifvghn thhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepgfehieeggfeileekhfdthfdtff egjeffvdekudffgfeltddujefhieeihffhveegnecuffhomhgrihhnpehivghtfhdrohhr ghenucevlhhushhtvghrufhiiigvpedunecurfgrrhgrmhepmhgrihhlfhhrohhmpehmth eslhhofigvnhhtrhhophihrdhnvght
X-ME-Proxy: <xmx:iL79Xl_9NXNm3U_v43uRmFm2Uys5tvTtkV4MICVi72BAoKCrZ7-VbA> <xmx:iL79XqSTlHxoQZKCMGBr6D7dXYdRumZL70ZvCdZM0ohq_fhsSD0FUg> <xmx:iL79Xvug-x8MhcpBKE0-tSyHhkPAXY6hoKHaS2A1VvYdMDLGBUyUIA> <xmx:ib79Xm-Aw-NCojJzbguGrTXCmAu0P-zPG19vsCIZ7dK5ILl85FuEkA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 5C65AE00B3; Thu,  2 Jul 2020 07:01:28 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-576-gfe2cd66-fm-20200629.001-gfe2cd668
Mime-Version: 1.0
Message-Id: <5943e1bd-fba9-473b-a20f-7992ad0579ab@www.fastmail.com>
Date: Thu, 02 Jul 2020 21:01:08 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: quic@ietf.org
Subject: Greasing the QUIC Bit
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Rd_SbFEMU3WXLms9aqw5v69MIKc>
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, 02 Jul 2020 11:01:32 -0000

The QUIC Bit (aka. the bit in the first byte that is fixed to 1) is one of the few things that doesn't change in QUIC.

That's a shame, so I wrote a draft explaining how that might not need to be true forever.  This might be a little too optimistic for some, but I thought that it was worth the time needed to write it up:

https://tools.ietf.org/html/draft-thomson-quic-bit-grease-00

Mostly this is so I had something to work with while I was working out GitHub Actions.  But I am considering implementing it still.


From nobody Thu Jul  2 05:26:59 2020
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 3B82E3A0C3B for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 05:26:57 -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, 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 Pbf9hVQdXAHn for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 05:26:56 -0700 (PDT)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 D59A03A0C38 for <quic@ietf.org>; Thu,  2 Jul 2020 05:26:55 -0700 (PDT)
Received: by mail-qt1-x82b.google.com with SMTP id v19so20991930qtq.10 for <quic@ietf.org>; Thu, 02 Jul 2020 05:26:55 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=bkdECXQz2KRPL+Lgrgp+5BcX8TFb8Iu+XXUJCYlUWxQ=; b=jdQi5+nnC6YcoBn4+Ih2fSFTWPMqXGcZDPO+cvRTj+ewbsH9Y7qQHns/ZmOGrz1Tg/ tTkPbuytw3COGq5feR0bJBaF4B0dpNF7aE/5wvs93LZdKghLvF8wbQ5tagk3NJ779LYi 7RUsZj+LOrSioNWRTtTwep2l+Bheb5pwOeCmmIkADYfin+Z1PgvCXDyHZCq58EZZ1A4k Xu0Ezdrnos1w68rlGUO7R34/hdh9dV3hxKYES5P0rC1MZbjSXVa+/5oYCrgPe6iNVzlX AADK4/AA4qGDXDXTiGcpP/CD3DHCh7nan6uo8y7qQzuHBV045/+fh4vQiRp5wVp0o5i4 S46w==
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=bkdECXQz2KRPL+Lgrgp+5BcX8TFb8Iu+XXUJCYlUWxQ=; b=nWYPnkuovrTS669kEKC9eMd10XiSSm+YpfFzm+bCc74H0DW6k3+7Amq7kiUaH9l/2H IuWNMfFYk28WRBQISLQS9AoGNRgGS7gJ6kJGSk9VoDGIKzNrlV1plLYEB3LIJUyv2D6A iB7Pa1+LFTTZEvHWNX1oT5mn+7irxxaO5cSk1BD9tW9apmaj8OYUs8BamwIO86EZ6U5+ indexBTVCqYxe2WRw0/6RpjWDa5QXJHXpH8J2+gdXQxRjK99+lhbtdEbYQ7p0D91nJZL MB6km+ifB4OO7B06qqr0PuHlpD2uAJ/FJdCwatmru0hlQ7+22yiK3JKBSYHjn1iGIzvw 1NXQ==
X-Gm-Message-State: AOAM530lAmf5cejFT5PhESly1t+WaNFhSa2lKBeg/6pePaq7OPAbJd0f IGnEAMwNf3ZKfXFe1WwUxa40MBOAcoVTSw==
X-Google-Smtp-Source: ABdhPJxLgd54wiv1s/cf0Nm1IkCm1gtcjelL9h4r6zn7iRlrIET99whSyzjX8COnOf+RFAITXg1gKw==
X-Received: by 2002:aed:3201:: with SMTP id y1mr30679013qtd.156.1593692814913;  Thu, 02 Jul 2020 05:26:54 -0700 (PDT)
Received: from lubuntu (ool-44c1d219.dyn.optonline.net. [68.193.210.25]) by smtp.gmail.com with ESMTPSA id x13sm7346399qkx.10.2020.07.02.05.26.53 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 02 Jul 2020 05:26:54 -0700 (PDT)
Date: Thu, 2 Jul 2020 08:26:44 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: quic@ietf.org
Subject: Re: Greasing the QUIC Bit
Message-ID: <20200702122643.GF11763@lubuntu>
Mail-Followup-To: Martin Thomson <mt@lowentropy.net>, quic@ietf.org
References: <5943e1bd-fba9-473b-a20f-7992ad0579ab@www.fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5943e1bd-fba9-473b-a20f-7992ad0579ab@www.fastmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/wtnm2aInkgdFzBzpxkG-YjWmz3A>
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, 02 Jul 2020 12:26:57 -0000

+1 -- I like it.

  - Dmitri.

On Thu, Jul 02, 2020 at 09:01:08PM +1000, Martin Thomson wrote:
> The QUIC Bit (aka. the bit in the first byte that is fixed to 1) is one of the few things that doesn't change in QUIC.
> 
> That's a shame, so I wrote a draft explaining how that might not need to be true forever.  This might be a little too optimistic for some, but I thought that it was worth the time needed to write it up:
> 
> https://tools.ietf.org/html/draft-thomson-quic-bit-grease-00
> 
> Mostly this is so I had something to work with while I was working out GitHub Actions.  But I am considering implementing it still.
> 


From nobody Thu Jul  2 05:57:41 2020
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 998E83A0857 for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 05:57:39 -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, 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 gmZOOmwHT1Up for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 05:57:38 -0700 (PDT)
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 D8C253A0852 for <quic@ietf.org>; Thu,  2 Jul 2020 05:57:37 -0700 (PDT)
Received: from mx4.nic.fr (localhost [127.0.0.1]) by mx4.nic.fr (Postfix) with SMTP id AA1BB280668; Thu,  2 Jul 2020 14:57:35 +0200 (CEST)
Received: by mx4.nic.fr (Postfix, from userid 500) id A3BF42806AB; Thu,  2 Jul 2020 14:57:35 +0200 (CEST)
Received: from relay01.prive.nic.fr (unknown [10.1.50.11]) by mx4.nic.fr (Postfix) with ESMTP id 9C505280668; Thu,  2 Jul 2020 14:57:35 +0200 (CEST)
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 97F6364C6C03; Thu,  2 Jul 2020 14:57:35 +0200 (CEST)
Received: by b12.nic.fr (Postfix, from userid 1000) id 85D9E3FCDB; Thu,  2 Jul 2020 14:57:35 +0200 (CEST)
Date: Thu, 2 Jul 2020 14:57:35 +0200
From: Stephane Bortzmeyer <bortzmeyer@nic.fr>
To: Martin Thomson <mt@lowentropy.net>
Cc: quic@ietf.org
Subject: Re: Greasing the QUIC Bit
Message-ID: <20200702125735.GA31502@nic.fr>
References: <5943e1bd-fba9-473b-a20f-7992ad0579ab@www.fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <5943e1bd-fba9-473b-a20f-7992ad0579ab@www.fastmail.com>
X-Operating-System: Debian GNU/Linux 10.4
X-Kernel: Linux 4.19.0-9-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.000000, 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/BKZtJiSfuFXksSoosfLPsF9JaNA>
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, 02 Jul 2020 12:57:40 -0000

On Thu, Jul 02, 2020 at 09:01:08PM +1000,
 Martin Thomson <mt@lowentropy.net> wrote 
 a message of 7 lines which said:

> That's a shame, so I wrote a draft explaining how that might not
> need to be true forever.

Isn't it the point of draft-ietf-quic-invariants? If it is not an
invariant, it may change.


From nobody Thu Jul  2 06:19:27 2020
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 B48B73A0CC3 for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 06:19:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=trammell.ch
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id xXf3YS1AtORc for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 06:19:16 -0700 (PDT)
Received: from smtp-8fae.mail.infomaniak.ch (smtp-8fae.mail.infomaniak.ch [IPv6:2001:1600:4:17::8fae]) (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 9254C3A09D8 for <quic@ietf.org>; Thu,  2 Jul 2020 06:19:03 -0700 (PDT)
Received: from smtp-2-0001.mail.infomaniak.ch (unknown [10.5.36.108]) by smtp-3-3000.mail.infomaniak.ch (Postfix) with ESMTPS id 49yJZr5QRhzlhhHW; Thu,  2 Jul 2020 15:19:00 +0200 (CEST)
Received: from [IPv6:2a02:169:17b2:0:428:9418:160f:9895] (unknown [IPV6:2a02:169:17b2:0:428:9418:160f:9895]) by smtp-2-0001.mail.infomaniak.ch (Postfix) with ESMTPA id 49yJZr1pl3zlh8Tx; Thu,  2 Jul 2020 15:19:00 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=trammell.ch; s=20191114; t=1593695940; bh=Km+u3nBfzWgRo8Bwa+2cTSET5feApeFX3qUFix+ryPo=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=h51OIphMc4NsIKOf3v+KHQRG+mHR3E+J/E/YNYdL8hrJcvHcnra6yQN65VoMUReOm TZ3xwm5tLybvYT7yczj+kpQWAk15xI/AGg6VFofyf+iA4pBpm8aM/8YUg7kIi/N4+R sB+lLxeYbdrKa9nR0cIX7sayNFmnQx0ilvnjmNns=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: Greasing the QUIC Bit
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
In-Reply-To: <20200702125735.GA31502@nic.fr>
Date: Thu, 2 Jul 2020 15:18:59 +0200
Cc: Martin Thomson <mt@lowentropy.net>, Stephane Bortzmeyer <bortzmeyer@nic.fr>
Content-Transfer-Encoding: quoted-printable
Message-Id: <96495211-4618-4169-A45C-96EBD421AF18@trammell.ch>
References: <5943e1bd-fba9-473b-a20f-7992ad0579ab@www.fastmail.com> <20200702125735.GA31502@nic.fr>
To: IETF QUIC WG <quic@ietf.org>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
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/cw7e-o2-n4aKQs_iVHFF_a853d0>
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, 02 Jul 2020 13:19:26 -0000

> On 2 Jul 2020, at 14:57, Stephane Bortzmeyer <bortzmeyer@nic.fr> =
wrote:
>=20
> On Thu, Jul 02, 2020 at 09:01:08PM +1000,
> Martin Thomson <mt@lowentropy.net> wrote=20
> a message of 7 lines which said:
>=20
>> That's a shame, so I wrote a draft explaining how that might not
>> need to be true forever.
>=20
> Isn't it the point of draft-ietf-quic-invariants? If it is not an
> invariant, it may change.

Invariants is a normative declaration of what we won't change in the =
future. This draft is a proof of concept showing that we can keep the =
"QUIC bit" from being an accidental invariant (i.e., a practical =
invariant not normatively declared as such).

I continue to fear that the demand for on-path discrimination of QUIC =
traffic will remain such that if:

- there is no intentional invariant for distinguishing QUIC traffic from =
non-QUIC traffic by arbitrary on-path devices; AND
- there is a trivially deployable method for blocking QUIC traffic which =
will result in negligible end-to-end availability risk and low impact on =
quality of experience, i.e. that blocking will come at no cost to access =
networks that choose to do so (which given TCP fallback is indeed the =
case in the majority of networks, unless things have changed since I =
last looked)

then we remain at risk of a rapid reversal of fortune on deployment. =
Sorry, hadn't said that at a mic for about a year now, felt a need to =
repeat it for the record. :)

As this view is incapable of gaining consensus within this working =
group, I'm fully in support of this approach to greasing the QUIC bit: =
we should be intentional about our invariants, and back them up with =
running code. And this appears to be a perfectly reasonable way to do =
that.

Cheers,

Brian



From nobody Thu Jul  2 06:36:21 2020
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 74EEF3A0789 for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 06:36:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 TNt-a0-nGrvr for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 06:36:17 -0700 (PDT)
Received: from mail-lj1-x22b.google.com (mail-lj1-x22b.google.com [IPv6:2a00:1450:4864:20::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 89E453A079B for <quic@ietf.org>; Thu,  2 Jul 2020 06:36:17 -0700 (PDT)
Received: by mail-lj1-x22b.google.com with SMTP id n23so32204317ljh.7 for <quic@ietf.org>; Thu, 02 Jul 2020 06:36:17 -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=7HmKu+FvIdAUv1KUnLA61K6QJaTrQZytR+/G4mXNemM=; b=HDHdSFLvAAhwPqhGTJl3jwtOvbgC3jLT8kGTexOfi6oCdbhFnwSCmK3ZjpC+6NYgAD iMhIqs7SIf3zt+amb9705a6C89I/BWsStMyIdKYdkPax/+V61VFT/5GWhtmCho8doeyh iskUMKXzUFrTSX94TGwxZgKssmly+Aj1PEUuL3Dc+4tDdS9ugnaxLoTVod35qrvNDnNr kKjV9UhAme4iAA7FqK6QD7jHoebz1iCuYllFxE22/l1kArOk4fJqlBFUVJhzYfxUD5rW MNX7RhmRyQrTsdvxMna8bqKXPbfAjgBnmXLKao+JpOJzmLL+PDKl6P61i39ws4q4TRPL +iag==
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=7HmKu+FvIdAUv1KUnLA61K6QJaTrQZytR+/G4mXNemM=; b=TZgf4e3Vzfpl+ke/C62pe+7DFx3RW6jgcIbqkTPUZzkVtSVVIHEWPowZSm+GdKyoF6 n/iNE7VsAs7ue8R8e8H1U/Sz/0m3rAmBEFRy//uw/ngPUUyb2qTM7Jou2X8Lc5VROlu+ afIVR2H5juNa2069mSXTpcYHLcx4Kqbq4rp5vOmdmSIEVtwTpuztiYaNxkSGNTUz6hL9 7qncY7AeCiSjLcYPKt6FAEY9FVE1jShhGHMMCXswHc7boGms4pt1oCpMY7+XNJtZfN+Q 7wLTUPrwbUQV2wH9T0bupVwHjFk7Fz3tVQ3kpHQannBPEYLPma7wv7UGdOsP8LaAq77t Achg==
X-Gm-Message-State: AOAM5330JYMxLf+hG9PTpxNXjFf7GG1k2hZEt9jaOhGsJXpcmMCFzi17 /rur72OxIedwWJj783/8VKDnu5+Q8ZVKFQFai7TM6BBO
X-Google-Smtp-Source: ABdhPJwcafYcLHOEBkEN4KOqdvNPfZrFcXT/GnocfjmYTXFmdhN8ic1KW99gyaDjVgqPv7Lf0iQHVf+7it/1aIUfLrs=
X-Received: by 2002:a2e:9b42:: with SMTP id o2mr15877388ljj.102.1593696975771;  Thu, 02 Jul 2020 06:36:15 -0700 (PDT)
MIME-Version: 1.0
References: <5943e1bd-fba9-473b-a20f-7992ad0579ab@www.fastmail.com> <20200702125735.GA31502@nic.fr> <96495211-4618-4169-A45C-96EBD421AF18@trammell.ch>
In-Reply-To: <96495211-4618-4169-A45C-96EBD421AF18@trammell.ch>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 2 Jul 2020 08:35:48 -0500
Message-ID: <CAKKJt-f+w5DpQ7KoQXduB5q7DDqnwvJsqs7UwJ7KdsmvvZ23aA@mail.gmail.com>
Subject: Re: Greasing the QUIC Bit
To: "Brian Trammell (IETF)" <ietf@trammell.ch>
Cc: IETF QUIC WG <quic@ietf.org>, Stephane Bortzmeyer <bortzmeyer@nic.fr>, Martin Thomson <mt@lowentropy.net>
Content-Type: multipart/alternative; boundary="0000000000001edd9205a9757e3e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/3jXb928oomRP0Evbd538jxevrJA>
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, 02 Jul 2020 13:36:19 -0000

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

Hi, Brian,

On Thu, Jul 2, 2020 at 8:21 AM Brian Trammell (IETF) <ietf@trammell.ch>
wrote:

>
> > On 2 Jul 2020, at 14:57, Stephane Bortzmeyer <bortzmeyer@nic.fr> wrote:
> >
> > On Thu, Jul 02, 2020 at 09:01:08PM +1000,
> > Martin Thomson <mt@lowentropy.net> wrote
> > a message of 7 lines which said:
> >
> >> That's a shame, so I wrote a draft explaining how that might not
> >> need to be true forever.
> >
> > Isn't it the point of draft-ietf-quic-invariants? If it is not an
> > invariant, it may change.
>
> Invariants is a normative declaration of what we won't change in the
> future. This draft is a proof of concept showing that we can keep the "QUIC
> bit" from being an accidental invariant (i.e., a practical invariant not
> normatively declared as such).
>
> I continue to fear that the demand for on-path discrimination of QUIC
> traffic will remain such that if:
>
> - there is no intentional invariant for distinguishing QUIC traffic from
> non-QUIC traffic by arbitrary on-path devices; AND
> - there is a trivially deployable method for blocking QUIC traffic which
> will result in negligible end-to-end availability risk and low impact on
> quality of experience, i.e. that blocking will come at no cost to access
> networks that choose to do so (which given TCP fallback is indeed the case
> in the majority of networks, unless things have changed since I last looked)
>
> then we remain at risk of a rapid reversal of fortune on deployment.
> Sorry, hadn't said that at a mic for about a year now, felt a need to
> repeat it for the record. :)
>

Thank you for the important reminder.


> As this view is incapable of gaining consensus within this working group,
> I'm fully in support of this approach to greasing the QUIC bit: we should
> be intentional about our invariants, and back them up with running code.
> And this appears to be a perfectly reasonable way to do that.
>

Before I read this ^ paragraph, I was planning to ask you whether "blocking
QUIC" merited a mention in
https://tools.ietf.org/html/draft-ietf-quic-manageability-06, because we
are in the awkward position with HTTP/3 that operators will face less
blowback blocking HTTP/3-QUIC and forcing a fallback to HTTP/2-TCP than
they will face blocking almost any non-HTTP/3 QUIC protocol (with less
clearly defined fallbacks) (see: MASQUE).

ISTM that at a minimum, the "accidental invariants" might be mentioned in
https://tools.ietf.org/html/draft-ietf-quic-manageability-06, which targets
operators.

Does any of that make sense?

Best,

Spencer


> Cheers,
>
> Brian
>
>
>

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

<div dir=3D"ltr"><div dir=3D"ltr">Hi, Brian,=C2=A0</div><br><div class=3D"g=
mail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jul 2, 2020 at 8:=
21 AM Brian Trammell (IETF) &lt;<a href=3D"mailto:ietf@trammell.ch">ietf@tr=
ammell.ch</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"><br>
&gt; On 2 Jul 2020, at 14:57, Stephane Bortzmeyer &lt;<a href=3D"mailto:bor=
tzmeyer@nic.fr" target=3D"_blank">bortzmeyer@nic.fr</a>&gt; wrote:<br>
&gt; <br>
&gt; On Thu, Jul 02, 2020 at 09:01:08PM +1000,<br>
&gt; Martin Thomson &lt;<a href=3D"mailto:mt@lowentropy.net" target=3D"_bla=
nk">mt@lowentropy.net</a>&gt; wrote <br>
&gt; a message of 7 lines which said:<br>
&gt; <br>
&gt;&gt; That&#39;s a shame, so I wrote a draft explaining how that might n=
ot<br>
&gt;&gt; need to be true forever.<br>
&gt; <br>
&gt; Isn&#39;t it the point of draft-ietf-quic-invariants? If it is not an<=
br>
&gt; invariant, it may change.<br>
<br>
Invariants is a normative declaration of what we won&#39;t change in the fu=
ture. This draft is a proof of concept showing that we can keep the &quot;Q=
UIC bit&quot; from being an accidental invariant (i.e., a practical invaria=
nt not normatively declared as such).<br>
<br>
I continue to fear that the demand for on-path discrimination of QUIC traff=
ic will remain such that if:<br>
<br>
- there is no intentional invariant for distinguishing QUIC traffic from no=
n-QUIC traffic by arbitrary on-path devices; AND<br>
- there is a trivially deployable method for blocking QUIC traffic which wi=
ll result in negligible end-to-end availability risk and low impact on qual=
ity of experience, i.e. that blocking will come at no cost to access networ=
ks that choose to do so (which given TCP fallback is indeed the case in the=
 majority of networks, unless things have changed since I last looked)<br>
<br>
then we remain at risk of a rapid reversal of fortune on deployment. Sorry,=
 hadn&#39;t said that at a mic for about a year now, felt a need to repeat =
it for the record. :)<br></blockquote><div><br></div><div>Thank you for the=
 important reminder.=C2=A0</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">As this view is incapable of gaining consensus with=
in this working group, I&#39;m fully in support of this approach to greasin=
g the QUIC bit: we should be intentional about our invariants, and back the=
m up with running code. And this appears to be a perfectly reasonable way t=
o do that.<br></blockquote><div><br></div><div>Before I read this ^ paragra=
ph, I was planning to ask you whether &quot;blocking QUIC&quot; merited a m=
ention in=C2=A0<a href=3D"https://tools.ietf.org/html/draft-ietf-quic-manag=
eability-06">https://tools.ietf.org/html/draft-ietf-quic-manageability-06</=
a>, because we are in the awkward position with HTTP/3 that operators will =
face less blowback blocking HTTP/3-QUIC and forcing a fallback to HTTP/2-TC=
P than they will face blocking almost any non-HTTP/3 QUIC protocol (with le=
ss clearly defined fallbacks) (see: MASQUE).=C2=A0</div><div><br></div><div=
>ISTM that at a minimum, the &quot;accidental invariants&quot; might be men=
tioned in=C2=A0<a href=3D"https://tools.ietf.org/html/draft-ietf-quic-manag=
eability-06">https://tools.ietf.org/html/draft-ietf-quic-manageability-06</=
a>, which targets operators.=C2=A0</div><div><br></div><div>Does any of tha=
t make sense?</div><div><br></div><div>Best,</div><div><br></div><div>Spenc=
er</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">=
Cheers,<br>
<br>
Brian<br>
<br>
<br>
</blockquote></div></div>

--0000000000001edd9205a9757e3e--


From nobody Thu Jul  2 08:16:17 2020
Return-Path: <paul@redbarn.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 1FACA3A087B for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 08:16:16 -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, 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 B2K4ZpzMzONn for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 08:16:13 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3ECE93A0838 for <quic@ietf.org>; Thu,  2 Jul 2020 08:16:13 -0700 (PDT)
Received: from linux-9daj.localnet (dhcp-166.access.rits.tisf.net [24.104.150.166]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (1024 bits) server-digest SHA256) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 0F83EB0588 for <quic@ietf.org>; Thu,  2 Jul 2020 15:16:10 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: IETF QUIC WG <quic@ietf.org>
Subject: Re: Greasing the QUIC Bit
Date: Thu, 02 Jul 2020 15:16:08 +0000
Message-ID: <4717330.G4jNEy2Xmo@linux-9daj>
Organization: none
In-Reply-To: <96495211-4618-4169-A45C-96EBD421AF18@trammell.ch>
References: <5943e1bd-fba9-473b-a20f-7992ad0579ab@www.fastmail.com> <20200702125735.GA31502@nic.fr> <96495211-4618-4169-A45C-96EBD421AF18@trammell.ch>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/9NWbWv6GPRDsv-p9IODaKUPG8nQ>
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, 02 Jul 2020 15:16:16 -0000

On Thursday, 2 July 2020 13:18:59 UTC Brian Trammell (IETF) wrote:
> ...
> 
> I continue to fear that the demand for on-path discrimination of QUIC
> traffic will remain such that if:
> 
> - there is no intentional invariant for distinguishing QUIC traffic from
> non-QUIC traffic by arbitrary on-path devices; AND - there is a trivially
> deployable method for blocking QUIC traffic which will result in negligible
> end-to-end availability risk and low impact on quality of experience, i.e.
> that blocking will come at no cost to access networks that choose to do so
> (which given TCP fallback is indeed the case in the majority of networks,
> unless things have changed since I last looked)
> 
> then we remain at risk of a rapid reversal of fortune on deployment. Sorry,
> hadn't said that at a mic for about a year now, felt a need to repeat it
> for the record. :)
> 
> As this view is incapable of gaining consensus within this working group,
> I'm fully in support of this approach to greasing the QUIC bit: we should
> be intentional about our invariants, and back them up with running code.
> And this appears to be a perfectly reasonable way to do that.

among the SASE (secure access service edge), such as enterprise, home, and 
other privately operated networks, QUIC is going to face accidental reverse 
discrimination. UDP is privileged here, only permitted if it is recognizably 
permitted. if QUIC offers no way to be recognized, then the fortunes of its 
deployment will be moderate.

when i say privileged, i mean default-deny in both host-based firewalls and 
perimeter gateways. i hope to be able to use QUIC on such networks, but i 
won't do so if it's an all or nothing proposition-- allow any unknown traffic 
or disallow QUIC, means to me, disallow QUIC. my position will be typical 
among CISO's. if QUIC is intended only for public (ISP or mobile IP), then i 
withdraw my concern.

the QUIC bit isn't enough to hook onto, so greasing that doesn't hurt the SASE 
use case. but i think we'll all be better off if we don't have SASE networks 
using destination UDP port number as the hook for "allow this traffic".

see also:

https://techspective.net/2020/06/23/the-four-horsemen-of-sase-secure-access-service-edge/

-- 
Paul



From nobody Thu Jul  2 09:37:16 2020
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 5FDD43A0A99 for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 09:37:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=trammell.ch
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RFbBV0P9jwxJ for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 09:37:12 -0700 (PDT)
Received: from smtp-bc09.mail.infomaniak.ch (smtp-bc09.mail.infomaniak.ch [IPv6:2001:1600:3:17::bc09]) (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 91C5C3A0A98 for <quic@ietf.org>; Thu,  2 Jul 2020 09:37:11 -0700 (PDT)
Received: from smtp-3-0000.mail.infomaniak.ch (unknown [10.4.36.107]) by smtp-2-3000.mail.infomaniak.ch (Postfix) with ESMTPS id 49yNzS0gBrzlhT7V; Thu,  2 Jul 2020 18:37:08 +0200 (CEST)
Received: from [IPv6:2a02:169:17b2:0:e915:a04f:d295:badc] (unknown [IPV6:2a02:169:17b2:0:e915:a04f:d295:badc]) by smtp-3-0000.mail.infomaniak.ch (Postfix) with ESMTPA id 49yNzR56Yczlh8TM; Thu,  2 Jul 2020 18:37:07 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=trammell.ch; s=20191114; t=1593707827; bh=lQ/W5/YHeT911/1eAXCT2sF7h9Hr2qLpuCseLiM2p8k=; h=Subject:From:In-Reply-To:Date:Cc:References:To:From; b=y0LhQcpNtom5Ipkk9hXxmOERgI4bsAA36jFKe/eK5KC6Ss73uLFuEmPHHaFh9oI9A aFH6PlmJJQ50kv0Vnx+qC/nX7r8F0i07J/UgFuHvDXDVBjqT72BgS5XBPIxmyxOSsS DJp7FcF9iVLwlHIaM7quTOa1CMg9PXikjSGfa/5Y=
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.80.23.2.2\))
Subject: Re: Greasing the QUIC Bit
From: "Brian Trammell (IETF)" <ietf@trammell.ch>
In-Reply-To: <CAKKJt-f+w5DpQ7KoQXduB5q7DDqnwvJsqs7UwJ7KdsmvvZ23aA@mail.gmail.com>
Date: Thu, 2 Jul 2020 18:37:07 +0200
Cc: IETF QUIC WG <quic@ietf.org>, Stephane Bortzmeyer <bortzmeyer@nic.fr>, Martin Thomson <mt@lowentropy.net>
Content-Transfer-Encoding: quoted-printable
Message-Id: <DF7D839F-B373-475A-858F-897E55C685B0@trammell.ch>
References: <5943e1bd-fba9-473b-a20f-7992ad0579ab@www.fastmail.com> <20200702125735.GA31502@nic.fr> <96495211-4618-4169-A45C-96EBD421AF18@trammell.ch> <CAKKJt-f+w5DpQ7KoQXduB5q7DDqnwvJsqs7UwJ7KdsmvvZ23aA@mail.gmail.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
X-Mailer: Apple Mail (2.3608.80.23.2.2)
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/OceJ4YbynVIqOG1r_8wfZQjZVUU>
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, 02 Jul 2020 16:37:16 -0000

hi Spencer,

> On 2 Jul 2020, at 15:35, Spencer Dawkins at IETF =
<spencerdawkins.ietf@gmail.com> wrote:
>=20
> Hi, Brian,=20
>=20
> On Thu, Jul 2, 2020 at 8:21 AM Brian Trammell (IETF) =
<ietf@trammell.ch> wrote:
>=20
> > On 2 Jul 2020, at 14:57, Stephane Bortzmeyer <bortzmeyer@nic.fr> =
wrote:
> >=20
> > On Thu, Jul 02, 2020 at 09:01:08PM +1000,
> > Martin Thomson <mt@lowentropy.net> wrote=20
> > a message of 7 lines which said:
> >=20
> >> That's a shame, so I wrote a draft explaining how that might not
> >> need to be true forever.
> >=20
> > Isn't it the point of draft-ietf-quic-invariants? If it is not an
> > invariant, it may change.
>=20
> Invariants is a normative declaration of what we won't change in the =
future. This draft is a proof of concept showing that we can keep the =
"QUIC bit" from being an accidental invariant (i.e., a practical =
invariant not normatively declared as such).
>=20
> I continue to fear that the demand for on-path discrimination of QUIC =
traffic will remain such that if:
>=20
> - there is no intentional invariant for distinguishing QUIC traffic =
from non-QUIC traffic by arbitrary on-path devices; AND
> - there is a trivially deployable method for blocking QUIC traffic =
which will result in negligible end-to-end availability risk and low =
impact on quality of experience, i.e. that blocking will come at no cost =
to access networks that choose to do so (which given TCP fallback is =
indeed the case in the majority of networks, unless things have changed =
since I last looked)
>=20
> then we remain at risk of a rapid reversal of fortune on deployment. =
Sorry, hadn't said that at a mic for about a year now, felt a need to =
repeat it for the record. :)
>=20
> Thank you for the important reminder.=20
> =20
> As this view is incapable of gaining consensus within this working =
group, I'm fully in support of this approach to greasing the QUIC bit: =
we should be intentional about our invariants, and back them up with =
running code. And this appears to be a perfectly reasonable way to do =
that.
>=20
> Before I read this ^ paragraph, I was planning to ask you whether =
"blocking QUIC" merited a mention in =
https://tools.ietf.org/html/draft-ietf-quic-manageability-06, because we =
are in the awkward position with HTTP/3 that operators will face less =
blowback blocking HTTP/3-QUIC and forcing a fallback to HTTP/2-TCP than =
they will face blocking almost any non-HTTP/3 QUIC protocol (with less =
clearly defined fallbacks) (see: MASQUE).=20
>=20
> ISTM that at a minimum, the "accidental invariants" might be mentioned =
in https://tools.ietf.org/html/draft-ietf-quic-manageability-06, which =
targets operators.=20
>=20
> Does any of that make sense?

Yep; have had limited cycles of late to devote to things IETF, but Mirja =
and I are picking up applicability and manageability again next week (to =
finally sync with the core documents which I presume will not change =
that much in WGLC).

This is tracked in https://github.com/quicwg/ops-drafts/issues/96

Cheers,

Brian



> Best,
>=20
> Spencer
> =20
> Cheers,
>=20
> Brian


From nobody Thu Jul  2 13:20:47 2020
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 D3ECA3A0AAA for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 13:20:45 -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, 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 hHYA19MxJal9 for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 13:20:44 -0700 (PDT)
Received: from mail-qv1-xf2f.google.com (mail-qv1-xf2f.google.com [IPv6:2607:f8b0:4864:20::f2f]) (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 52BE53A0AA9 for <quic@ietf.org>; Thu,  2 Jul 2020 13:20:44 -0700 (PDT)
Received: by mail-qv1-xf2f.google.com with SMTP id d12so13336679qvn.0 for <quic@ietf.org>; Thu, 02 Jul 2020 13:20:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=2wvuBLNCXf9u7kUVtZxKq1WaDQ7mD5Th8o8MMMzEwns=; b=WtkDl80Hnr6rn0k7ST+dP4qYIZYi2UBqZYNJRv2AbSzRGhjLLj76Ulv2cLr4gyakaF HsQ0CXoWYNjDDFaoLGay94x86PHTvcunNkisU98sNohYg7k7Tj2/VdYDB1NWvxnXkSMV BywV4milpCjjKhp0vpDmP1e/1F4I2VyA3lhwWLRLDVHU4Mr1/y4WiouxUq5Dl4lB4r9y ENexi+4pB3sjS/wUlz1WSK9g0A5soJE/TXthU8bLHueYCoVaX5LdYXgUrlY9q3PO4N4w S4/kULeBRmlBjiFtT1neqp2YYc0rVRgiaaG/rX/ASReagxTnNxhBvzFu4YArA411H0oA Xbig==
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=2wvuBLNCXf9u7kUVtZxKq1WaDQ7mD5Th8o8MMMzEwns=; b=oIEACFf1SeFw4eCTb6zVOyuNKSu49BEvVwn3rY+v8Tyw7uNOOyuxKF0PMH+YR1+6st d78kA+JKNHWjYekO9e3wX8P7SYvGhkHy5AJRU5A1Qnqg6h/vn5x3W+5iOFkgswTr4kjN +gh6fXU9kTTia4vv7+EtTU6cxwEE2Je6DkbQmaIp9x40JNys8Uw393eDQxUdubKslKTo 8fXyIa8igavptBQpCbzcdYTq/Z2SfaSwSR/7HwkoIbcu9txD6LKT6ABrgdNqrFPnOBmc P9M/ShJrYIrHOvbiETRnjFhUMAKdMCQOoFbN/GudVRBnKEiXPADu3ClVmfwTSAaWL67j wqXw==
X-Gm-Message-State: AOAM531n9LBTnQRzrw5QLWQuTh+YMde4OcRfpaIOta9LYE3XAP9RAo5f 1/CzU7vmBl6+mc2mG89fyVWqM2e4mQCMpw==
X-Google-Smtp-Source: ABdhPJzEyW3y290FIMepqvZxyn0dCHCJ6cWMxcA7QCVXhYkAVn+1+SscunSdXolxAy55PpwFp5Ukvw==
X-Received: by 2002:a05:6214:14e5:: with SMTP id k5mr8324238qvw.125.1593721242933;  Thu, 02 Jul 2020 13:20:42 -0700 (PDT)
Received: from lubuntu (ool-44c1d219.dyn.optonline.net. [68.193.210.25]) by smtp.gmail.com with ESMTPSA id i57sm10604429qte.75.2020.07.02.13.20.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 02 Jul 2020 13:20:42 -0700 (PDT)
Date: Thu, 2 Jul 2020 16:20:27 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: quic@ietf.org
Cc: Martin Thomson <mt@lowentropy.net>
Subject: Re: Greasing the QUIC Bit
Message-ID: <20200702202026.GA26580@lubuntu>
Mail-Followup-To: quic@ietf.org, Martin Thomson <mt@lowentropy.net>
References: <5943e1bd-fba9-473b-a20f-7992ad0579ab@www.fastmail.com> <20200702122643.GF11763@lubuntu>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20200702122643.GF11763@lubuntu>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/cLJUdgQ8XdIzpuSLNvAugjsBVV8>
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, 02 Jul 2020 20:20:46 -0000

Martin,

Why don't you pick a TP number -- let's interop on it during the
upcoming Interop.

  - Dmitri.

On Thu, Jul 02, 2020 at 08:26:43AM -0400, Dmitri Tikhonov wrote:
> +1 -- I like it.
> 
>   - Dmitri.
> 
> On Thu, Jul 02, 2020 at 09:01:08PM +1000, Martin Thomson wrote:
> > The QUIC Bit (aka. the bit in the first byte that is fixed to 1) is one of the few things that doesn't change in QUIC.
> > 
> > That's a shame, so I wrote a draft explaining how that might not need to be true forever.  This might be a little too optimistic for some, but I thought that it was worth the time needed to write it up:
> > 
> > https://tools.ietf.org/html/draft-thomson-quic-bit-grease-00
> > 
> > Mostly this is so I had something to work with while I was working out GitHub Actions.  But I am considering implementing it still.
> > 


From nobody Thu Jul  2 13:38:47 2020
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 DFEF33A0AB1 for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 13:38:44 -0700 (PDT)
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_MSPIKE_H2=-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=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 gAZIPNjGbocz for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 13:38:43 -0700 (PDT)
Received: from NAM12-DM6-obe.outbound.protection.outlook.com (mail-dm6nam12on2092.outbound.protection.outlook.com [40.107.243.92]) (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 1E7C63A0AAF for <quic@ietf.org>; Thu,  2 Jul 2020 13:38:42 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=TsWZNShRlr2ljjRJRa7o7TZi5hZ0AJwDQI/ajZaxpzc4UXAaYJ2qKfPwEsAxWrGdBvucm3hTrRB1fcz7W8abIkUm0xCqsr3R9ZpyUJo8lR+5TRmLiZRgGhvGJXLH9wYVY3GyS+NEkU5pWMxB49D/PM4Tmv5JVFvE7iD2b7PS5GTR8UH59IOu5y5PzaCehZwDTo+RshDv74xfXZLcxrh6ra/FOjX1QW1T16jTQTGP1ZxcCinbvJ18Ud5GWtffX1phODeIcedLjx7YJngk9toGdyHLf5cubxJWNhvc1j0ahI1X7Mm3dCYa7/8QItXieswHP8s/8od3CPU4zGtgLnmNBw==
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=3ZATvRt6msp32AVjcvGE1PSJi01yctxLZgw9/R6S1Uo=; b=irhTxIBFsADAlSi4BzeHfjDftm7We4HuCYHuLA26a7cxJhXhBPz2Jv5CStwbg/0XMzTuXvitpRoI6x2fPeUj4B9CyXcXBE7N9n7BFMouzVoKQREtntSmTpNgbJTF9igPBzfS3NlpiiVZZSeUfmK6Qt9hyS9+neZ8uECSQWy6aGAgDTCGC1otNMzvtRp8X9U6eEIpncfz3bWWiChyHD7HSW/kCBznCYgBot7nWSETb/qV371WC/zhNz5/jZW3mV7g+sYbhyElbjw0sz93r8VGr9TXMvzLP8ef+ygg8euAzVJyonjOPhmS0yDVCTls00RklxaFNgn0QDJ/2SmIsWoI5w==
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=3ZATvRt6msp32AVjcvGE1PSJi01yctxLZgw9/R6S1Uo=; b=XogIsnf85PphF5OaaeHtGUXXgSruDr8zaWy6mZM6s8z5H1KxdjQeun3APdeupp7Vv6McrJl6XvDkf8uX3ddWbM1i9MO3ThHRkLRlisAnuM4k9LWqAYxAQyj9CFjjnZvc2JNzQ7vUlAdChTFEiK+LK6e2hxxlXZD6BwzZB36a+oo=
Received: from CH2PR22MB2086.namprd22.prod.outlook.com (2603:10b6:610:8c::8) by CH2PR22MB2070.namprd22.prod.outlook.com (2603:10b6:610:5c::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3153.20; Thu, 2 Jul 2020 20:38:41 +0000
Received: from CH2PR22MB2086.namprd22.prod.outlook.com ([fe80::f0e6:8202:6056:a596]) by CH2PR22MB2086.namprd22.prod.outlook.com ([fe80::f0e6:8202:6056:a596%3]) with mapi id 15.20.3153.022; Thu, 2 Jul 2020 20:38:40 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Martin Thomson <mt@lowentropy.net>, "quic@ietf.org" <quic@ietf.org>
Subject: RE: Greasing the QUIC Bit
Thread-Topic: Greasing the QUIC Bit
Thread-Index: AQHWUGAyASHAGcBTf06DhEh5hoRNmKj0wDxA
Date: Thu, 2 Jul 2020 20:38:40 +0000
Message-ID: <CH2PR22MB2086FD91E42AC403D85DC42FDA6D0@CH2PR22MB2086.namprd22.prod.outlook.com>
References: <5943e1bd-fba9-473b-a20f-7992ad0579ab@www.fastmail.com>
In-Reply-To: <5943e1bd-fba9-473b-a20f-7992ad0579ab@www.fastmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: lowentropy.net; dkim=none (message not signed) header.d=none;lowentropy.net; dmarc=none action=none header.from=evequefou.be;
x-originating-ip: [72.49.212.17]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ca753c76-bc58-4ff2-1d3b-08d81ec7e7c5
x-ms-traffictypediagnostic: CH2PR22MB2070:
x-microsoft-antispam-prvs: <CH2PR22MB207053B9BCB4F94AD0981983DA6D0@CH2PR22MB2070.namprd22.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:7691;
x-forefront-prvs: 0452022BE1
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: AG+gNeWNpG1kCjmuYBYmOF85cN2nsw9iEspywe0pG0Km5l7cGI4sgThN/RaYEJr7E9mwLEPdd3ke/vVbr6nNginW25x9GTmcx0wA4T6dZNnCrNZGWMTucHrqENtqh3dw/B1FdZkQFGPm5y9f1G5P4eFAXRnKO/8ZiluY7lUVnJSQuP9w7Uc+bGC5Xf5RD4sbeVv2W2m80V14JXzwiyHjWkIIPewDLp7n0xRHYA4QAfvcFnGgikgDZKdJ8s30Jo6tTz9mc7BmVBRrgn9eaHPvzQYyS9ZFewoeCZXIIopIzdzmRYu1O4GYL0YtOmi8b77yrYXmKv9JUqrXD4DoHkMtuJqqh2uYMg6+U6mvmQWzS/YnTxnYWEmlfOB96udU9378s03c4A7OfnTgeTLdkHpetA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:CH2PR22MB2086.namprd22.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(346002)(396003)(376002)(39830400003)(136003)(366004)(186003)(64756008)(66446008)(66556008)(66476007)(83380400001)(76116006)(7696005)(3480700007)(71200400001)(5660300002)(966005)(33656002)(2906002)(508600001)(8936002)(8676002)(9686003)(316002)(55016002)(86362001)(52536014)(66946007)(110136005)(53546011)(26005)(6506007); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: irpsI+wFx8cbXg+BVW3nrnWSlNLLnxyhnlBbpIcVFxk4VK9nOKf9Qu3dY/zV4J0WU2RGs23dZRu8OQsI442g3Pr8OxXhfvCrHdkJvuha+apM0IgoT5zDVMbFxflfbRwEK5jktf2Snn2NVTlGHkMGpKEd4VYRbPjCtKhrOQN5IL0Qz+HzV1Ghas7Y9ymS9nHFNS8R9OkMBkQ4GbxiKP6C7RUzAChuTQN61Q3LwT43P5ibnTxyubQEpn+R7po5mDTZZB8TPToLOu55fO3SgmwWaCdKjUMpjy6hC3nFZ+P5bFusZeJ/feWH3RnVQFkd+S/cUA+o766EgT5Bfr5kUGEBCjW6UnVu6Wc/ZMhcvU+eD5kJMlIeSN4lta6lPshQqvf8xA1rIdCU4ovOovaoHZs6iDHuyvFMRsU+656KU43A9EoiopZdQ2n0h0oJTsZoMv/xif3uTmP41H/nDRyuPyxW5ztqVTSAwQipYNcH6US6E28=
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-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CH2PR22MB2086.namprd22.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ca753c76-bc58-4ff2-1d3b-08d81ec7e7c5
X-MS-Exchange-CrossTenant-originalarrivaltime: 02 Jul 2020 20:38:40.6823 (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: IqVPMrNvjX2OLazQJpoZm4ZXZRrGJ/T+YIsM+1jV5QFe8hswcMhP7M9kLBRMvqCBseQbe0fppAt5rL3Rob3UbA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR22MB2070
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/_7LNBA9lisLK9a-OAB3VRrPDdlQ>
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, 02 Jul 2020 20:38:45 -0000

Seems like the most straightforward way to grease it to be extending header=
 protection to cover that bit as well.  It's always set to 1, but you chang=
e the mask you're using on the first byte of header protection and get inst=
ant variability, just like the reserved bits.  I'm surprised the document d=
oesn't mention that way of implementing it, even if it's hardly the only wa=
y to achieve an "unpredictable value."

-----Original Message-----
From: QUIC <quic-bounces@ietf.org> On Behalf Of Martin Thomson
Sent: Thursday, July 2, 2020 7:01 AM
To: quic@ietf.org
Subject: Greasing the QUIC Bit

The QUIC Bit (aka. the bit in the first byte that is fixed to 1) is one of =
the few things that doesn't change in QUIC.

That's a shame, so I wrote a draft explaining how that might not need to be=
 true forever.  This might be a little too optimistic for some, but I thoug=
ht that it was worth the time needed to write it up:

https://tools.ietf.org/html/draft-thomson-quic-bit-grease-00

Mostly this is so I had something to work with while I was working out GitH=
ub Actions.  But I am considering implementing it still.


From nobody Thu Jul  2 17:21:37 2020
Return-Path: <agenda@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 BA79D3A0937; Thu,  2 Jul 2020 17:20:31 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: "\"IETF Secretariat\"" <agenda@ietf.org>
To: <lars@eggert.org>, <quic-chairs@ietf.org>
Cc: magnus.westerlund@ericsson.com, quic@ietf.org
Subject: quic - Requested session has been scheduled for IETF 108
X-Test-IDTracker: no
X-IETF-IDTracker: 7.7.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <159373563174.30173.4966801879055667371@ietfa.amsl.com>
Date: Thu, 02 Jul 2020 17:20:31 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/NI77IA0hZYwGoYNHB8S3fDImMmk>
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, 03 Jul 2020 00:20:39 -0000

Dear Lars Eggert,

The session(s) that you have requested have been scheduled.
Below is the scheduled session information followed by
the original request. 


    quic Session 1 (1:40 requested)
    Wednesday, 29 July 2020, Session I 1100-1240
    Room Name: Room 7 size: 7
    ---------------------------------------------


iCalendar: https://datatracker.ietf.org/meeting/108/sessions/quic.ics

Request Information:


---------------------------------------------------------
Working Group Name: QUIC
Area Name: Transport Area
Session Requester: Lars Eggert


Number of Sessions: 1
Length of Session(s):  100 Minutes
Number of Attendees: 200
Conflicts to Avoid: 
 Chair Conflict: masque webtrans httpbis ript
 Technology Overlap: tls iccrg tcpm tsvwg tsvarea saag
 Key Participant Conflict: capport add





People who must be present:
  Sean Turner
  Mark Nottingham
  Magnus Westerlund
  Jana Iyengar
  Martin Thomson
  Brian Trammell
  Mirja Kuehlewind
  Lars Eggert
  Mike Bishop
  Ian Swett
  Lucas Pardue
  Alan Frindell

Resources Requested:

Special Requests:
  
---------------------------------------------------------



From nobody Thu Jul  2 17:41:32 2020
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 2C8C63A0972 for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 17:41:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=lowentropy.net header.b=lKlrJHKV; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=L1YLYIyC
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Q0Yo2CNkKBzE for <quic@ietfa.amsl.com>; Thu,  2 Jul 2020 17:41:28 -0700 (PDT)
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 509753A096B for <quic@ietf.org>; Thu,  2 Jul 2020 17:41:28 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 68A5D5C01BE for <quic@ietf.org>; Thu,  2 Jul 2020 20:41:27 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Thu, 02 Jul 2020 20:41:27 -0400
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=fm2; bh=eOIEkqGlHm1PIFBbXp8wR+0SHdbl2ii CApZRzvLgqlM=; b=lKlrJHKVOG+tkc/Ym1jHc7lkBJd0eKzsnGEZQUbtVNdsLU9 3AsyfBXF6azb0tztqdl/N3Nlamc0iD0FBm3GPEP0HhALBVUYBEJuoAsFfbFAWeNS FRVjZnKR9s7068tQYjrKTP1XbQoWne+fK24EOfcLw8+eWcKQ+OYhqNygoTqdUhxD SzLIR8fI+tZqb7t38SzQTGsuw/CClp0lwGB2yo9D93C8ACQu725qrRyu11uE/fDa EB9oLNppjJWahWepOhHmLzwoClJM++GqivMDm83gbZN0zjwIyqqKaFpWOuXN8rY7 G7rksDqKIoyLKrPrzdLsH04Ni+SxBHAddkHStqg==
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=fm3; bh=eOIEkq GlHm1PIFBbXp8wR+0SHdbl2iiCApZRzvLgqlM=; b=L1YLYIyCcSXj1GTCEP+GT9 wCQw8WBzlEwgvrEnJAhk4ZV48FIf2X1/eEFjCbr1AfYkwN603yLPaX2yAHGXHSd6 osqt4GqV+QxzQlGC4seHy+H+1M58HtV8N0jCb4Jh4ruj+PTA8gju+FucuMcyA6+Z bAK2of2pgUgbnk7CP3X8LMpfsGeTyqLc68MAyz8i+hGk3qliMZ913ssxwBXggGaC RTOdTvZFQZfJX6pju52bbx5YR1saynTlk71proV+Tv05gBZRqrnrkRvhk9Oc+aLW 1HtMNuNlZtUArDsbCdujiETdyjUow5EpiRWRzRkSQ1IU7tdGqSdnO8PPpPhHtXsQ ==
X-ME-Sender: <xms:tn7-XqtJjH8H3-Qdkjf4bVDNler80AVIURBuyBPTDBgOSKXVMCXHcw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrtdehgdefiecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif vghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepkeetueeikedtkeelfeekve fhkeffvedvvefgkefgleeugfdvjeejgeffieegtdejnecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:tn7-XvcbhdSvqxXyhI7mp37GEqYV2KIkzVEWckITJpbj0Drlr6xQaQ> <xmx:tn7-Xlwq4QQnoXdbvgDEla7YbGYRt3Mq7Xi9ZZSPyJoLDZnEQU4eHw> <xmx:tn7-XlMdoXk6C2NARO8H1vzt_oFpQ1i8Z_7oqyjGYtRdG9ZhowRu0Q> <xmx:t37-XkdqBYiWWpO0H-8fmRdGfGO7uQEpaRXY2nuDDGH7xnV5kjeYug>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id C4940E00D4; Thu,  2 Jul 2020 20:41:26 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-576-gfe2cd66-fm-20200629.001-gfe2cd668
Mime-Version: 1.0
Message-Id: <65c908df-7123-46ee-838c-575f8154c811@www.fastmail.com>
In-Reply-To: <CH2PR22MB2086FD91E42AC403D85DC42FDA6D0@CH2PR22MB2086.namprd22.prod.outlook.com>
References: <5943e1bd-fba9-473b-a20f-7992ad0579ab@www.fastmail.com> <CH2PR22MB2086FD91E42AC403D85DC42FDA6D0@CH2PR22MB2086.namprd22.prod.outlook.com>
Date: Fri, 03 Jul 2020 10:41:08 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: quic@ietf.org
Subject: Re: Greasing the QUIC Bit
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/D-oJZhApqhcp5qH9M-8utL3fnWw>
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, 03 Jul 2020 00:41:30 -0000

Multi-reply, inline...

On Thu, Jul 2, 2020, at 22:57, Stephane Bortzmeyer wrote:
> Isn't it the point of draft-ietf-quic-invariants? If it is not an
> invariant, it may change.

Indeed it is the point of that document, and we do not promise that the value is constant.  But actions are louder than words and QUIC version 1 fixes the bit, so there is the concern that the words in -invariants won't have an effect.


On Thu, Jul 2, 2020, at 23:18, Brian Trammell (IETF) wrote:
> I continue to fear that the demand for on-path discrimination of QUIC 
> traffic will remain [...]

Ack.  The question for me is how much this bit was ever likely to sufficient for that purpose.


On Fri, Jul 3, 2020, at 06:20, Dmitri Tikhonov wrote:
> Why don't you pick a TP number -- let's interop on it during the
> upcoming Interop.

As the rules for the registries allow, the draft has a number in it.  I'll see about implementation.  It shouldn't take too long :)


On Fri, Jul 3, 2020, at 06:38, Mike Bishop wrote:
> Seems like the most straightforward way to grease it to be extending 
> header protection to cover that bit as well.  It's always set to 1, but 
> you change the mask you're using on the first byte of header protection 
> and get instant variability, just like the reserved bits.  I'm 
> surprised the document doesn't mention that way of implementing it, 
> even if it's hardly the only way to achieve an "unpredictable value."

This remains the most difficult question for me.  I spent a good amount of time thinking about this and never really reached a conclusion I was happy with.

The use of the masking to generate an unpredictable value might sound good, but it isn't good.  Unless you can meet some very particular constraints - and you disassemble your AEAD - the value of the mask depends on the value of the bit, so you can't use masking bits to decide the value.  You might save bits from the last packet for the next one, I guess, but that's just an RNG.

It's this that makes the question of masking difficult.

If you mask the bit, then you need to be sure that recipients know when it is masked.  That means you can't apply the new rule for generating the bit prior to negotiating the extension.  In practice, that means you can only realistically affect 1-RTT packets (and maybe 0-RTT packets).

If you don't mask the bit, then you can toggle the value of bit any time you think your peer might be OK with it, including for new connections.  The value you send is what is authenticated.  But that prevents you from masking the value of the bit.  Or at least it makes it much more difficult to use the bit to carry a value for which you require end-to-end confidentiality.  I can think of a couple of tricks, but they require some crypto-juju to avoid some fairly nasty costs.

In the end, not masking is easier to specify and implement, so that was the decider :)  The effect is that this is better suited to path signals than end-to-end signals.


From nobody Thu Jul  2 19:27:07 2020
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2EA483A0B2F; Thu,  2 Jul 2020 19:27:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 7bAvBCCpZ7Iw; Thu,  2 Jul 2020 19:27:03 -0700 (PDT)
Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (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 2F4B93A0B2E; Thu,  2 Jul 2020 19:27:03 -0700 (PDT)
Received: by mail-lf1-x131.google.com with SMTP id g139so17471350lfd.10; Thu, 02 Jul 2020 19:27:03 -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=prn5nxwnwLO7yAaiUu2UuDJ5ZuNfCO7r+BUxs7DkC78=; b=tBDoF/Y23RpeL4OOj2PRftZzy4ieuoq1oBfyWhTNh9wPD10TY1FzaCWqnzuRBDE4Zo S3K4d1r1dlNVZhwQZ08ob/TyLS7/NXbFXOYUajihiSmNccOwvq+CR7MX2bUXFjFj1ZLy MgakzwUl8ZN+MjuAn1CuanoNu6gA4Wyvp/5DN5jAeXCeYVd4aQdouKM8G1vZFcOM7RL4 5rCkDb18RGI2QWRbC7cvczcvk5uiPokr0ZYCpcCR/EHuVzL0+lFAnxoozHRLceOlldzH yrJo2Hpy19iZXFn21d7BgpSpldrr0emSU8al+q1090r9LP2aeul6mR0Vok2wnmZgofMn qJfg==
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=prn5nxwnwLO7yAaiUu2UuDJ5ZuNfCO7r+BUxs7DkC78=; b=HO4hRSrVoPL5Qq7ErXUJeeTDA0gy8YBaEQcGdd8H5HmGh50+Pf0pIS0xM1dtNvKXH5 LTkSbp0dxQ/Htr38xNO6dqu6elwN88hLDS7MKHfxJ1JArVoLsPMcxtWo5bA4Mcmj3Rqb eqxilzpGUesYCtutHuIis460of8UqRi7CbSln46zbHMGDXADOsBrwv9cmExp4rN+NvDs RAUdv8ho5wwSMAlrDlOLmjYcvYNDo4xOhME1OiJFpFakbZdQJ1xgnOEd+12UIHmckl1Y xMaRAxSbtIZFGRlSF4ElVlGiHhJ930Imw/QvTFeaVhhBS1T7T3oQyWGqK3fmXojcbOke St+Q==
X-Gm-Message-State: AOAM5329GbsYUVg1w7du5okMBxrnm4x/+jM34uL6FDwpi+dhdyQQ3Iit IcQRnaOTKceX9LAR7uH1n3dB+rHHddSeFYPKL50fQw==
X-Google-Smtp-Source: ABdhPJyJctmn0MJdgJWHa+JdQ9nDxpl+Krek+oea0GGjiW5ZLFt0nc0tNOKYWdQUtB8hz4RUkX9OrQFFHbvJDpGCGso=
X-Received: by 2002:a19:4143:: with SMTP id o64mr20111064lfa.157.1593743221051;  Thu, 02 Jul 2020 19:27:01 -0700 (PDT)
MIME-Version: 1.0
References: <81DED556-AAAB-4833-A0CE-5F4DA2AE4869@eggert.org>
In-Reply-To: <81DED556-AAAB-4833-A0CE-5F4DA2AE4869@eggert.org>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 2 Jul 2020 21:26:34 -0500
Message-ID: <CAKKJt-cGDjstb8TKze+ktikakkzisQuv9HcY1_Or0tiF8ZZnPQ@mail.gmail.com>
Subject: Re: Please send agenda request for IETF-108
To: WG Chairs <quic-chairs@ietf.org>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000008dd6c505a98042ad"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/K6OPdbGYFGgOmD_jLRR639Jk-lo>
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, 03 Jul 2020 02:27:05 -0000

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

Dear QUIC Chairs,

On Tue, Jun 30, 2020 at 1:55 AM Lars Eggert <lars@eggert.org> wrote:

> Hi,
>
> please send your agenda requests for IETF-108 to quic-chairs@ietf.org.
>
> Please note that we'll strictly prioritize items that will let us progress
> the drafts currently in WGLC towards IETF LC, followed by requests related
> to adopted WG drafts, followed by everything else. As a tie breaker, we'll
> prioritize things that have seen active discussion in the recent past.
>

Under "everything else", the authors of
https://datatracker.ietf.org/doc/draft-bonaventure-quic-atsss-overview/
would like to get on the list to (1) summarize feedback we've gotten from
the mailing list, (2) summarize the current state of 3GPP Rel-17 proposals
which were influenced by this draft.

We recognize that this will be toward the end of a short session, and we
will do what we can to minimize the time required.

Best,

Spencer

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

<div dir=3D"ltr"><div>Dear QUIC Chairs,</div><br><div class=3D"gmail_quote"=
><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jun 30, 2020 at 1:55 AM Lars=
 Eggert &lt;<a href=3D"mailto:lars@eggert.org" target=3D"_blank">lars@egger=
t.org</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">Hi,<br>
<br>
please send your agenda requests for IETF-108 to <a href=3D"mailto:quic-cha=
irs@ietf.org" target=3D"_blank">quic-chairs@ietf.org</a>.<br>
<br>
Please note that we&#39;ll strictly prioritize items that will let us progr=
ess the drafts currently in WGLC towards IETF LC, followed by requests rela=
ted to adopted WG drafts, followed by everything else. As a tie breaker, we=
&#39;ll prioritize things that have seen active discussion in the recent pa=
st.<br></blockquote><div><br></div><div>Under &quot;everything=C2=A0else&qu=
ot;, the authors of=C2=A0<a href=3D"https://datatracker.ietf.org/doc/draft-=
bonaventure-quic-atsss-overview/" target=3D"_blank">https://datatracker.iet=
f.org/doc/draft-bonaventure-quic-atsss-overview/</a> would like to get on t=
he list to (1) summarize feedback we&#39;ve gotten from the mailing list, (=
2) summarize the current state of 3GPP Rel-17 proposals which were influenc=
ed by this draft.</div><div><br></div><div>We recognize that this will be t=
oward the end of a short session, and we will do what we can to minimize th=
e time required.=C2=A0</div><div><br></div><div>Best,</div><div><br></div><=
div>Spencer</div></div></div>

--0000000000008dd6c505a98042ad--


From nobody Fri Jul  3 04:56:23 2020
Return-Path: <fabio.bulgarella@guest.telecomitalia.it>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 014A93A0CFC for <quic@ietfa.amsl.com>; Fri,  3 Jul 2020 04:56:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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=guest.telecomitalia.it
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ieavWPt60ksz for <quic@ietfa.amsl.com>; Fri,  3 Jul 2020 04:56:17 -0700 (PDT)
Received: from mx05.telecomitalia.it (mx05.telecomitalia.it [156.54.232.21]) (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 6EF453A0CF9 for <quic@ietf.org>; Fri,  3 Jul 2020 04:56:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=guest.telecomitalia.it; s=selector1; c=relaxed/relaxed;  q=dns/txt; i=@guest.telecomitalia.it; t=1593777371; x=2457690971; h=MIME-Version:From:Date:Message-ID:Subject:To; bh=9G+mjG+k6+TdNR8pNIjoARhM1EHDuir6I0iJCO+538w=; b=d5pkzBEido50TEmEwWEUYPixdGWNkalGlDSkMp9oaibRhoO1rHmyOyXfIngOi9qc GZCVAGiZwZCxQU0mfd7kfsT2AoRkELM9VS1eHzT07GqzMfJLcoyHfR8gpHeJTfnV s/Zyyre3sfz+85FsL0UC3G40J5P9a7S4s3f9fjK6usG9I+pN85JQ+2WEDI9UcJzG okeyC/RUO6/3lvGz21ZhJdteOkZuIJ0UrEsmP3aBh9QJ7daIlU57b6qOCDRQGb3Y bhkKFUT4DlNgdJU303chLE+Qkj7Sevf9clyejMkuWHwGL3GsMz/dm486BhPqMz2K QLfnuoazpbQHWMd5cixAzA==;
X-AuditID: 0a5a2d15-e2bff70000008cc1-6f-5eff1cdb07da
Received: from TELMBXD09BA020.telecomitalia.local ( [10.90.43.41]) by mx05.telecomitalia.it () with SMTP id 32.F1.36033.BDC1FFE5; Fri,  3 Jul 2020 13:56:11 +0200 (CEST)
From: "Bulgarella Fabio (Guest)" <fabio.bulgarella@guest.telecomitalia.it>
To: IETF IPPM WG <ippm@ietf.org>
CC: "quic@ietf.org" <quic@ietf.org>, Cociglio Mauro <mauro.cociglio@telecomitalia.it>, Nilo Massimo <massimo.nilo@telecomitalia.it>, Giuseppe Fioccola <giuseppe.fioccola@huawei.com>, 'Riccardo Sisto' <riccardo.sisto@polito.it>
Subject: Updates on draft-cfb-ippm-spinbit-measurements-02
Thread-Topic: Updates on draft-cfb-ippm-spinbit-measurements-02
Thread-Index: AQHWUTDxEvoB5nunVUGZ4wJfU/JiaQ==
Date: Fri, 3 Jul 2020 11:56:10 +0000
Message-ID: <1593777370876.61872@guest.telecomitalia.it>
Accept-Language: it-IT, en-US
Content-Language: it-IT
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [188.219.222.222]
Content-Type: multipart/alternative; boundary="_000_159377737087661872guesttelecomitaliait_"
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFmplkeLIzCtJLcpLzFFi42LhitLW1L0t8z/OYMUseYs1c1YwWfQ8eMds 0bOA2+Ln7Z3sDiweLUfesnosWfKTyeP0yuIA5igum5TUnMyy1CJ9uwSujGsvowp6+CvuvDvM 2MDYwtvFyMkhIWAisWvddLYuRi4OIYFVjBJr/jWzdDFycLAJeEnMvqMMYooIKEhMeuwPUsIs 8IJR4u7172wgvcICVhKdW3azgtgiAvYSq/dMZoKo15O4PjMNJMwioCLRvf0NWDmvgIXE0QPb GUFsRgFZiQm7F4HZzALiEi+mn2CHOEdAYsme88wQtqjEy8f/WCFsA4mtS/exQNjKEqvvXGOF 6I2TaF+6gxFivqDEyZlPwGqEgN76sPIcywRG4VlIVsxC0jILSQtEXE/ixtQpbBC2tsSyha+Z IWxdiRn/DrEgiy9gZF/FKJpbYWCqV5Kak5qcn5tZkpiTmaiXWbKJERxTuqI7GLeteKN3iJGJ g/EQowQHs5IIb4Lqvzgh3pTEyqrUovz4otKc1OJDjNIcLErivB8e/o0TEkhPLEnNTk0tSC2C yTJxcEo1MO2snXDnoOBqJuGpbrkvXjfYVM6/G3pc5Zduw44HRRK3zXedipJmFV0n0FuXo1D+ Tqwn5fCilEULHh0/1/b76LG05qVLdBjbar6veGSrUcOy5qmTNsOWA8ufLa6/19cu/PrC/E9H VLJOCoaY6x2bmBUfdbdCf24k41Tum3OqK15lWj3w+5f6/P6JFYp71jb1vPqdpPlr2W21smU6 75mU9E03b70azXrp9YRtl5p6dbeufmZsrPjmyx0H/4qZh3Z+2Xf/UNF/9XJj/ZSwd7aCD+xu id/8taZ4yf10gai3b5wWKLtbbQyse/c+6kTu+QtPZju22xmmX8uelN+wnHO62O9TagHb62Q9 XyXMNnr9MMVQiaU4I9FQi7moOBEAlz/qLRgDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/daMzvh1R3Q6_Nv2WhOr7C2KEubI>
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, 03 Jul 2020 11:56:21 -0000

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

Dear IPPM and QUIC WG members,
we have just submitted an updated version of our draft on explicit measurem=
ents
(https://tools.ietf.org/html/draft-cfb-ippm-spinbit-measurements-02).

Taking into account the comments received in the past months on the mailing=
 lists,
we have introduced a short paragraph that explains how it is possible to im=
prove
the resistance of the 2-bits loss algorithm against out of sequence.

Comments are welcome.

Best Regards,
Fabio, Mauro, Massimo, Giuseppe, Riccardo


--_000_159377737087661872guesttelecomitaliait_
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; }--></style>
</head>
<body dir=3D"ltr" style=3D"font-size:12pt;color:#000000;background-color:#F=
FFFFF;font-family:Calibri,Arial,Helvetica,sans-serif;">
<div>Dear IPPM and QUIC WG members,</div>
<div>we have just submitted an updated version of our draft on explicit mea=
surements</div>
<div>(https://tools.ietf.org/html/draft-cfb-ippm-spinbit-measurements-02).<=
br>
</div>
<div><br>
</div>
<div>Taking into account the comments received in the past months on the ma=
iling lists,</div>
<div>we have introduced a short paragraph that explains how it is possible =
to improve</div>
<div>the resistance of the 2-bits loss algorithm against out of sequence.</=
div>
<div><br>
</div>
<div>Comments are welcome.</div>
<div><br>
</div>
<div>Best Regards,</div>
<div>Fabio, Mauro, Massimo, Giuseppe, Riccardo<br>
</div>
<div><br>
</div>
</body>
</html>

--_000_159377737087661872guesttelecomitaliait_--


From nobody Fri Jul  3 05:33:31 2020
Return-Path: <mauro.cociglio@telecomitalia.it>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C44203A0D40 for <quic@ietfa.amsl.com>; Fri,  3 Jul 2020 05:33:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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=telecomitalia.it
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id inJh1t7qe-OE for <quic@ietfa.amsl.com>; Fri,  3 Jul 2020 05:33:27 -0700 (PDT)
Received: from mx06.telecomitalia.it (mx06.telecomitalia.it [156.54.232.22]) (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 DEA383A0D39 for <quic@ietf.org>; Fri,  3 Jul 2020 05:33:26 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=telecomitalia.it; s=selector1; c=relaxed/relaxed;  q=dns/txt; i=@telecomitalia.it; t=1593779603; x=2457693203; h=MIME-Version:From:Date:Message-ID:Subject:To; bh=e2wciT7jDUIaEB9MyJKO1pXtE1vPEZSG569CNZ6Oqn0=; b=MFpc3MW8GGw1HM0Zi3L8Xwjt06kxOR9iou7H7An5uCQxfnxmRpUkO7TtQzkA9YJE SILud5nIQgZqH89c9Tn8tZXUr6fOShbQJHASD6qxb97tQ4hVQ6erxagx4fYYGGes /TMsACcYfVQ3RHJe8uPL5Pqz62ICEU8jBCEtk1zo7obp8CpZLuexJm6pk5jTeOOz TluSXgT3leT8+eQv2P8hyZ3RsFVlIFN0dqZViim6ngP28s84GF9H5wehi94JmO7k +1JqsQTvtTMhwbV9Fq31ByNrXpOThA6DiVZkkZjYTOqSbiYBZw7XQVy8Jxybh3dI zzYbqhQ2OvSvvBypBcbANA==;
X-AuditID: 0a5a2d16-937ff70000006b76-78-5eff259355de
Received: from TELMBXC02BA020.telecomitalia.local ( [10.90.43.26]) by mx06.telecomitalia.it () with SMTP id 7A.D3.27510.3952FFE5; Fri,  3 Jul 2020 14:33:23 +0200 (CEST)
From: Cociglio Mauro <mauro.cociglio@telecomitalia.it>
To: "IETF IPPM WG (ippm@ietf.org)" <ippm@ietf.org>, "quic@ietf.org" <quic@ietf.org>
CC: Nilo Massimo <massimo.nilo@telecomitalia.it>, "Bulgarella Fabio (Guest)" <fabio.bulgarella@guest.telecomitalia.it>, "giuseppe.fioccola@huawei.com" <giuseppe.fioccola@huawei.com>, 'Riccardo Sisto' <riccardo.sisto@polito.it>
Subject: About to measure Explicit Performances on user devices (mobile phones, PCs)
Thread-Topic: About to measure Explicit Performances on user devices (mobile phones, PCs)
Thread-Index: AdZQhy9WxJZw9I9ETrSFmbU5QsD6MA==
Date: Fri, 3 Jul 2020 12:33:22 +0000
Message-ID: <8c2df3da5f8c4450b272e3224dd23e46@TELMBXD14BA020.telecomitalia.local>
Accept-Language: it-IT, en-US
Content-Language: it-IT
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.171.45.146]
x-ti-disclaimer: ADBanner
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprNKsWRmVeSWpSXmKPExsXCFaUtpTtZ9X+cwaRd6hZr5qxgsuh58I7Z omcBtwOzR8uRt6weS5b8ZApgimpgtEnMy8svSSxJVUhJLU62VXLJLE7OSczMTS1ScHRxAkqm FikpZKbYKpkpKRTkJCan5qbmldgqJRYUpOalKNlxKWAAG6CyzDyF1Lzk/JTMvHRbJc9gf10L C1NLXUMlu8DS1OKSfIXc1OLixPT0zHyFhFciGUuuxhccFKn4MeM8awPjD4EuRg4OCQETif/L IrsYuTiEBFYxSvxefIKpi5GTg03ATOLMlmdsILaIQKjEnw3/GEGKmAWeMUrc2PiHESQhLBAm cevdP2aIomiJJ8tnsEPYehIP3m1lBbFZBFQkfs09BzaUVyBQYuGrDhYQm1FAVmLC7kVgc5gF xCVeTD8B1ishICCxZM95ZghbVOLl43+sELaBxNal+1ggbEWJT7MWQNVIShw+vIkNYo6exI2p U6BsbYllC18zQ+wVlDg58wlYr5CAjsTl+4fYJjCKzkKyehaS9llI2mchaV/AyLKKUTS3wsBM ryQ1JzU5PzezJDEnM1Evs2QTIzg56IrtYHyw/o3eIUYmDsZDjBIczEoivAmq/+KEeFMSK6tS i/Lji0pzUosPMfoAA2Yis5Rocj4wPeWVxBuampmaGxuZmRqYmlniEFYS5/3w8G+ckEA6MBll p6YWpBbBjGPi4JRqYErqiFpxd479xldnCmJ2PG1x3/LgmZPFlz7OH74rGF2SuOezlb5q93h7 9NeOzmnsSx98X3F3xckZr+vtL/O5LGC7zPWRWVb51PUrsbOXnjrs3KTZtOmc/o6cT+Kt0cxx x1a7HnNuPt1uxcdewOxjsDutRKBvvZTmPtf6xzsXXZosYrrrgmH67f1SNZ0HHjJmMh/J7jON ZGkIOKcyf5LdtCNNV+b9LoqbUMDw57a5+s6oZrGlj/K5Tv4UfPxfiJFTj33dtAvBodOVLz5a ZrMhRPsNM7/npJ9Cu1WvTXPYVShRJrwwfoOdke5hqW9NtkrZosby59zbjHLPts4WP8ewlvmg 8BOVBy/lNNUPTljL1qHEUpyRaKjFXFScCAC9mteOrgMAAA==
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/dvLr2p4mGfPen0uCofsajF0J5Ww>
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, 03 Jul 2020 12:33:30 -0000

Dear QUIC and IPPM WG members.
=A0
After Spin bit introduction, and now with packet loss measurement proposals*=
, the Explicit Performance Monitoring on client-server protocols (e.g. QUIC)=
 becomes an interesting topic for Telco.
Explicit Performance Monitoring enables a passive Observer to measure delay=
 and packet loss only watching the marking (a few bits) of production traffi=
c packets.
=A0
We propose that the first place where to put the Explicit Performance Observ=
er is on the user device (e.g. mobile phones, PCs).
Main reasons of this choice.
1. Scalability. On the user device there are few connections to monitor.
2. The Observer can monitor both directions: upload and download (inside the=
 network is not always possible).
3. Some measurements, natively not end2end, became E2E (e.g. packet loss Q-b=
it)
4. It's possible to set alarm thresholds on the user device (and to signal t=
o network probes to monitor only the sessions with impairments, in order to=
 segment the performance measurements and to locate the faults). In this cas=
e observers, also embedded into network nodes, need to monitor only a limite=
d number of connections (the ones that have problems).
=A0
Of course, to do this, the decision whether to activate the marking=A0(e.g.=
 Spin Bit) or not=A0must be made by=A0the device owner configuring the=A0app=
lications (e.g. browsers) based on protocols that supports Explicit Performa=
nce Monitoring (e.g. QUIC).
=A0
All applications should therefore provide for the activation or deactivation=
 of the marking for the Explicit Performance Monitoring.
=A0
So, from this point of view, in the Client-Server handshake it should be the=
 Client who decides whether the marking is active or not within a session an=
d the Server should adapt.
=A0
The performance information thus obtained could then be kept on the user dev=
ice or sent to "external bodies" according to the will of the device owner.
The main recipient would be the Internet Service Provider (see point 4 of th=
e previous list), but these data could also be of interest to the national r=
egulatory authorities and perhaps others.
=A0
Feedbacks are welcomed.
Best regards.
=A0
Mauro

* Explicit packet loss measurements proposals:
1) https://tools.ietf.org/html/draft-cfb-ippm-spinbit-measurements-02
2) https://tools.ietf.org/html/draft-ferrieuxhamchaoui-quic-lossbits-03

=A0
_____________________
Mauro Cociglio
Telecom Italia-TIM
Via G. Reiss Romoli, 274
10148 - Torino (Italy)
Tel.: +390112285028
Mobile: +393357669751
_____________________
=A0


Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle pers=
one indicate. La diffusione, copia o qualsiasi altra azione derivante dalla=
 conoscenza di queste informazioni sono rigorosamente vietate. Qualora abbia=
te ricevuto questo documento per errore siete cortesemente pregati di darne=
 immediata comunicazione al mittente e di provvedere alla sua distruzione, G=
razie. 

This e-mail and any attachments is confidential and may contain privileged i=
nformation intended for the addressee(s) only. Dissemination, copying, print=
ing or use by anybody else is unauthorised. If you are not the intended reci=
pient, please delete this message and any attachments and advise the sender=
 by return e-mail, Thanks. 

Rispetta l'ambiente. Non stampare questa mail se non =E8 necessario.


From nobody Fri Jul  3 19:04:00 2020
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 B54783A09F1 for <quic@ietfa.amsl.com>; Fri,  3 Jul 2020 19:03:58 -0700 (PDT)
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, 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 pZmB_ToAa1Up for <quic@ietfa.amsl.com>; Fri,  3 Jul 2020 19:03:57 -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 39BBE3A09EC for <quic@ietf.org>; Fri,  3 Jul 2020 19:03:56 -0700 (PDT)
Received: from xse44.mail2web.com ([66.113.196.44] helo=xse.mail2web.com) by mx105.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1jrXWy-0000bd-HW for quic@ietf.org; Sat, 04 Jul 2020 04:03:56 +0200
Received: from xsmtp21.mail2web.com (unknown [10.100.68.60]) by xse.mail2web.com (Postfix) with ESMTPS id 49zFTr18rbzsy6 for <quic@ietf.org>; Fri,  3 Jul 2020 19:02:56 -0700 (PDT)
Received: from [10.5.2.12] (helo=xmail02.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 1jrXW4-0008Rv-19 for quic@ietf.org; Fri, 03 Jul 2020 19:02:56 -0700
Received: (qmail 11240 invoked from network); 4 Jul 2020 02:02:55 -0000
Received: from unknown (HELO [192.168.1.107]) (Authenticated-user:_huitema@huitema.net@[172.58.46.187]) (envelope-sender <huitema@huitema.net>) by xmail02.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 4 Jul 2020 02:02:55 -0000
To: Martin Thomson <mt@lowentropy.net>, quic@ietf.org
References: <5943e1bd-fba9-473b-a20f-7992ad0579ab@www.fastmail.com> <CH2PR22MB2086FD91E42AC403D85DC42FDA6D0@CH2PR22MB2086.namprd22.prod.outlook.com> <65c908df-7123-46ee-838c-575f8154c811@www.fastmail.com>
From: Christian Huitema <huitema@huitema.net>
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mDMEXtavGxYJKwYBBAHaRw8BAQdA1ou9A5MHTP9N3jfsWzlDZ+jPnQkusmc7sfLmWVz1Rmu0 J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PoiWBBMWCAA+FiEEw3G4 Nwi4QEpAAXUUELAmqKBYtJQFAl7WrxsCGwMFCQlmAYAFCwkIBwIGFQoJCAsCBBYCAwECHgEC F4AACgkQELAmqKBYtJQbMwD/ebj/qnSbthC/5kD5DxZ/Ip0CGJw5QBz/+fJp3R8iAlsBAMjK r2tmyWyJz0CUkVG24WaR5EAJDvgwDv8h22U6QVkAuDgEXtavGxIKKwYBBAGXVQEFAQEHQJoM 6MUAIqpoqdCIiACiEynZf7nlJg2Eu0pXIhbUGONdAwEIB4h+BBgWCAAmFiEEw3G4Nwi4QEpA AXUUELAmqKBYtJQFAl7WrxsCGwwFCQlmAYAACgkQELAmqKBYtJRm2wD7BzeK5gEXSmBcBf0j BYdSaJcXNzx4yPLbP4GnUMAyl2cBAJzcsR4RkwO4dCRqM9CHpVJCwHtbUDJaa55//E0kp+gH
Subject: Re: Greasing the QUIC Bit
Message-ID: <9db597a6-5e75-4df6-5447-8204d052100c@huitema.net>
Date: Fri, 3 Jul 2020 19:02:55 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <65c908df-7123-46ee-838c-575f8154c811@www.fastmail.com>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Content-Language: en-US
X-Originating-IP: 66.113.196.44
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.44/32
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.44/32@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0f6LF1GdvkEexklpcFpSF5apSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDcnqpk5VeF3xR4kF6iVwRtbgN zB/4Jkrw1eDLcif59fvM/3F/AXWdXzEQzS8FaCI6U7Tmz6iKnkQL9gqsxD347235Nhqq+/HvroPq 8GSPg+60/QPNqXybIny9WGhadIo/G0KF6HkLuWi8fS7fvK7Hsbyme9ldZJ7uNXfg/GfS8fUvP/L5 rCqHDsKZM+xa1iwJX+gRCHfMVnsAk591zk0uilUI+ZL4xWiN8NS6C+dmX6OEdA4u1aThyWrQ/ou2 +v/lmX4Em37yFgrCB6NHRn1g+f3uncIqYSL3lhh5c81YyJqFoLZMmkWsaurVZfvqROaDnDtHb8z5 dpPkEuJ8Snwqla7jUnW3hy14Yji8fo+4xCnSRo4Rcu5Z37rMuDjCny5fE9ykbJ7I9co1MAEE3ruN Xsm8UJsAPvDcVSKtDCYkioPY5Qx4fJOk03R5fJtf/Dv/dkIzS7m4GUpXCY1Y3j3ilU9uaDsIPkO9 NcV2UWdi7rYNgfslPwgLMPeV3suSDRJVQ7lpL9conbe783Tp56fR5xPXEv3EDaPA1IUvTVmP7JuH gbVpRK3T9+h2PwMALJBC8U0Qc2cItWeQn0hrqUcNc7dCp3Zd9clP8wSiJZWbJCg35R5vCGCRun6Y x0PkyFKGUmJL8/wiW6IDBeXl/RY0UzXg724gFzhHYUe+7aKm0vWiWEaYW9QKOiKrsHvklItbTi+J 2sBvM/O0p+zizleC4lU8fDj1CnRx+r4b/1Q/PZ/Um5+9cYZbxLoI+xclcaT5vOnCUbNPgcPcQwzM 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/RLU3nfnEGx0tayfLe5LttjsZbFI>
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, 04 Jul 2020 02:03:59 -0000

I am almost done implementing this in picoquic, I just have a question
about to set the quic bit if the option is negotiated

The spec says "use an unpredictable value", and I am hesitating between
three options:

1) flip a coin upon negotiation of the TP, and set all Quic Bits for the
connection to the selected value.

2) flip the bit at every packet.

3) run a random number generator for each packet.

The problem is that it has to be both unpredictable and testable.
Testable would mean "run a test connection, and check that the Quic bit
is zero some of the time". This kind of rules out the "one coin per
connection" option, because then some connections will never set the bit
to zero. Flip on every packet is testable, but is hardly unpredictable.
The RNG is a statistical test. It can still statistically fail, unless I
run the test for long connections. Also, it is hard to make it
repetitive. I will probably end up with some RNG variant, but this does
not make me too happy...

-- Christian Huitema

On 7/2/2020 5:41 PM, Martin Thomson wrote:
> Multi-reply, inline...
>
> On Thu, Jul 2, 2020, at 22:57, Stephane Bortzmeyer wrote:
>> Isn't it the point of draft-ietf-quic-invariants? If it is not an
>> invariant, it may change.
> Indeed it is the point of that document, and we do not promise that the=
 value is constant.  But actions are louder than words and QUIC version 1=
 fixes the bit, so there is the concern that the words in -invariants won=
't have an effect.
>
>
> On Thu, Jul 2, 2020, at 23:18, Brian Trammell (IETF) wrote:
>> I continue to fear that the demand for on-path discrimination of QUIC =

>> traffic will remain [...]
> Ack.  The question for me is how much this bit was ever likely to suffi=
cient for that purpose.
>
>
> On Fri, Jul 3, 2020, at 06:20, Dmitri Tikhonov wrote:
>> Why don't you pick a TP number -- let's interop on it during the
>> upcoming Interop.
> As the rules for the registries allow, the draft has a number in it.  I=
'll see about implementation.  It shouldn't take too long :)
>
>
> On Fri, Jul 3, 2020, at 06:38, Mike Bishop wrote:
>> Seems like the most straightforward way to grease it to be extending=20
>> header protection to cover that bit as well.  It's always set to 1, bu=
t=20
>> you change the mask you're using on the first byte of header protectio=
n=20
>> and get instant variability, just like the reserved bits.  I'm=20
>> surprised the document doesn't mention that way of implementing it,=20
>> even if it's hardly the only way to achieve an "unpredictable value."
> This remains the most difficult question for me.  I spent a good amount=
 of time thinking about this and never really reached a conclusion I was =
happy with.
>
> The use of the masking to generate an unpredictable value might sound g=
ood, but it isn't good.  Unless you can meet some very particular constra=
ints - and you disassemble your AEAD - the value of the mask depends on t=
he value of the bit, so you can't use masking bits to decide the value.  =
You might save bits from the last packet for the next one, I guess, but t=
hat's just an RNG.
>
> It's this that makes the question of masking difficult.
>
> If you mask the bit, then you need to be sure that recipients know when=
 it is masked.  That means you can't apply the new rule for generating th=
e bit prior to negotiating the extension.  In practice, that means you ca=
n only realistically affect 1-RTT packets (and maybe 0-RTT packets).
>
> If you don't mask the bit, then you can toggle the value of bit any tim=
e you think your peer might be OK with it, including for new connections.=
  The value you send is what is authenticated.  But that prevents you fro=
m masking the value of the bit.  Or at least it makes it much more diffic=
ult to use the bit to carry a value for which you require end-to-end conf=
identiality.  I can think of a couple of tricks, but they require some cr=
ypto-juju to avoid some fairly nasty costs.
>
> In the end, not masking is easier to specify and implement, so that was=
 the decider :)  The effect is that this is better suited to path signals=
 than end-to-end signals.
>


From nobody Fri Jul  3 23:05:45 2020
Return-Path: <kangjiao@huawei.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6428E3A0BCE; Fri,  3 Jul 2020 23:05:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level: 
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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 QQOZiDBoCDNw; Fri,  3 Jul 2020 23:05:41 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 3B6B03A0BCB; Fri,  3 Jul 2020 23:05:41 -0700 (PDT)
Received: from lhreml737-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id E5A914C82814C1684A53; Sat,  4 Jul 2020 07:05:38 +0100 (IST)
Received: from lhreml737-chm.china.huawei.com (10.201.108.187) by lhreml737-chm.china.huawei.com (10.201.108.187) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Sat, 4 Jul 2020 07:05:38 +0100
Received: from DGGEMM404-HUB.china.huawei.com (10.3.20.212) by lhreml737-chm.china.huawei.com (10.201.108.187) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Sat, 4 Jul 2020 07:05:38 +0100
Received: from DGGEMM534-MBS.china.huawei.com ([169.254.7.44]) by DGGEMM404-HUB.china.huawei.com ([10.3.20.212]) with mapi id 14.03.0487.000; Sat, 4 Jul 2020 14:05:28 +0800
From: Kangjiao <kangjiao@huawei.com>
To: "quic@ietf.org" <quic@ietf.org>
CC: "quic-chairs@ietf.org" <quic-chairs@ietf.org>, "Litong (2012 Labs)" <li.tong@huawei.com>
Subject: Hope a discussion for draft-li-quic-optimizing-ack-in-wlan-00
Thread-Topic: Hope a discussion for draft-li-quic-optimizing-ack-in-wlan-00
Thread-Index: AdZRyGcTBCKzXYE+TnatOw5glQUhXg==
Date: Sat, 4 Jul 2020 06:05:28 +0000
Message-ID: <719A2C1D4AC73847B6E1BF21DF1545EAE5C7CE04@dggemm534-mbs.china.huawei.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.45.86.35]
Content-Type: multipart/alternative; boundary="_000_719A2C1D4AC73847B6E1BF21DF1545EAE5C7CE04dggemm534mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/zCVg5eySzaXajO5O-JEbpO4ZGSA>
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, 04 Jul 2020 06:05:44 -0000

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

Dear QUIC WG members,


We uploaded a draft describing a mechanism for ACK optimization to QUIC gro=
up. The link is https://datatracker.ietf.org/doc/draft-li-quic-optimizing-a=
ck-in-wlan/. This solution comes from our practice and the results show it =
is a good replacement of the traditional ACK mechanism to compensate for sc=
enarios where the acknowledgement overhead is non-negligible (i.e., wireles=
s scenarios).



The key points for this solution can be:



1. We conclude the formula of the minimum ACK intensity required for QUIC t=
ransport.



2. In order to alleviate the error in RTT estimation, we use protocol exten=
sions and a one-way delay factor. We think this round-trip timing method ca=
n also be applicable for the ack thinning mechanisms (such as "Changing the=
 Default QUIC ACK Policy" #3529) that have been discussed in QUIC group.



3. For implementation and interoperability, we define a new ACK-INTENSITY F=
rame in which ACK Intensity is set. ACK Intensity is a variable-length inte=
ger indicating the updated intensity of QUIC ACK Frame calculated by our fo=
rmula.



We look forward to your valuable comments and suggestions. Thanks.

Sincerely,
Jiao

--_000_719A2C1D4AC73847B6E1BF21DF1545EAE5C7CE04dggemm534mbschi_
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:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:SimSun;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"\7EAF\6587\672C Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.Char
	{mso-style-name:"\7EAF\6587\672C Char";
	mso-style-priority:99;
	mso-style-link:\7EAF\6587\672C;
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
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"ZH-CN" link=3D"#0563C1" vlink=3D"#954F72" style=3D"text-justi=
fy-trim:punctuation">
<div class=3D"WordSection1">
<p class=3D"MsoNormal"><span lang=3D"EN-US">Dear QUIC WG members,<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"MsoPlainText"><span lang=3D"EN-US">We uploaded a draft describi=
ng a mechanism for ACK optimization to QUIC group. The link is
<a href=3D"https://datatracker.ietf.org/doc/draft-li-quic-optimizing-ack-in=
-wlan/">
<span style=3D"color:windowtext;text-decoration:none">https://datatracker.i=
etf.org/doc/draft-li-quic-optimizing-ack-in-wlan/</span></a>. This solution=
 comes from our practice and the results show it is a good replacement of t=
he traditional ACK mechanism to compensate
 for scenarios where the acknowledgement overhead is non-negligible (i.e., =
wireless scenarios).<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">The key points for this solu=
tion can be:<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">1. We conclude the formula o=
f the minimum ACK<span style=3D"color:black"> intensity required for QUIC t=
ransport.<o:p></o:p></span></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">2. In order to alleviate the=
 error in RTT estimation, we use protocol extensions and a one-way delay fa=
ctor. We think this round-trip timing method can also be applicable for the=
 ack thinning mechanisms (such as
</span><span lang=3D"EN-US" style=3D"font-family:&quot;Courier New&quot;">&=
#8221;</span><span lang=3D"EN-US">Changing the Default QUIC ACK Policy</spa=
n><span lang=3D"EN-US" style=3D"font-family:&quot;Courier New&quot;">&#8221=
;</span><span lang=3D"EN-US"> #3529) that have been discussed in QUIC group=
.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US">3.&nbsp;For implementation a=
nd interoperability, we define a new ACK-INTENSITY Frame in which ACK Inten=
sity is set. ACK Intensity is a variable-length integer indicat<span style=
=3D"color:black">ing the updated intensity of
</span>QUIC ACK Frame calculated by our formula.<o:p></o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US"><o:p>&nbsp;</o:p></span></p>
<p class=3D"MsoPlainText"><span lang=3D"EN-US" style=3D"color:black">We loo=
k forward to your valuable comments and suggestions. Thanks.<o:p></o:p></sp=
an></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">Sincerely,<o:p></o:p></span></p=
>
<p class=3D"MsoNormal"><span lang=3D"EN-US">Jiao<span style=3D"color:#1F497=
D"><o:p></o:p></span></span></p>
</div>
</body>
</html>

--_000_719A2C1D4AC73847B6E1BF21DF1545EAE5C7CE04dggemm534mbschi_--


From nobody Sun Jul  5 00:32:25 2020
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 501FF3A0AA9 for <quic@ietfa.amsl.com>; Sun,  5 Jul 2020 00:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=mnot.net header.b=hPyx7GpC; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=PDv+Ragc
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N8sCiswTTwAK for <quic@ietfa.amsl.com>; Sun,  5 Jul 2020 00:32:21 -0700 (PDT)
Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D49623A0AA7 for <quic@ietf.org>; Sun,  5 Jul 2020 00:32:20 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 28DA15C0085 for <quic@ietf.org>; Sun,  5 Jul 2020 03:32:20 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sun, 05 Jul 2020 03:32:20 -0400
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= fm3; bh=e9PA2v9syzjoRcLHtCRsmIQ+t8dYWhp5IPP5HWxdcDM=; b=hPyx7GpC VQa7DWFh+d1FP83GM9VJXRCqzm/G9uHVAfCx/4GQdu9b+N5HSUx9yEx2fw0fYG8h z1smmQEm4qUlScN2kfTzoLfYBBMmdcHMf4c6RIDRkRJh2IHBUNIw9oU31apobF6k ZLVabt7EkLKurFeLYdA0794QepQPVN0GyV56s36iW4btJ1WzBmZogNOgOriP0VkT IHNQI2VFRQOv+Ketz0KAXYxlzNIEjZReb2D2JoY22sOmMrWcRWRiwwK+uhnpmkjg nq0i/lo2uUN0mVfKH62tVKMyCS9OQrd/LNvuYUBj8ZMqxLUxi8gMKsLPSOv17uMn kt8vZGuRJhj9Og==
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=fm3; bh=e9PA2v9syzjoRcLHtCRsmIQ+t8dYW hp5IPP5HWxdcDM=; b=PDv+RagcO30FFdRCkIqJoVc8yUGjEIblKBmb8+uz2Hyke vq5T4r2GTSsF/uvNn9Fc2G22clwjq7oP9hXiKZc5dB6HP08owe8soqi3f5A1XYpx MOkiQL7epOi2kIFCchVsAx7PLiBLIC48dt7Q0FmccdNXFrFXbckopzekzAUxPKzj QzPLTtYbzgcb4NqZHSZc439v7PdOnFTYHjPargQBG+kJ1B3CKjrpF8q98nVJTGJv CAzhbi2cEpYkhAZz1d4sKht27/wS8089pRbE3tyn+ec1e5ufXxFxGfWG/FsYz67O j9DY6Wz0+ef0Sbv74yWH2FD5VHHItAwW5Oy2TV/YQ==
X-ME-Sender: <xms:A4IBX_nBRd0wxAl7DMpMz4XKLkLQxPy6rnyBq2R6M6n0rNB8vX2UiQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedruddtgddvfecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurheptggghffvufesrgdttdertddtjeenuc fhrhhomheptfgvphhoshhithhorhihucettghtihhvihhthicuufhumhhmrghrhicuueho thcuoeguohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvghtqeenucggtffrrghtthgvrh hnpeekfedvudetjedvfeekheeiveeugfefhfetteevgeffkefffeetffdvleehudeiteen ucffohhmrghinhepghhithhhuhgsrdgtohhmnecukfhppeehvddrudejhedrvdegjedrle efnecuvehluhhsthgvrhfuihiivgepudenucfrrghrrghmpehmrghilhhfrhhomhepugho pghnohhtpghrvghplhihsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:A4IBXy1pe-rYAR1ZFo4-1PV1UEkrzo0acIFiK9bVVQTu8wbGQFsRXw> <xmx:A4IBX1qO5qm5kv0M1momKNsYx30XnEv1KF8yL81As_ccXHLfFzTsNQ> <xmx:A4IBX3nk6gbKcDzP6QIwFL2wLWsRiz9wHVa-PBUkqDR55Nr3rSMhng> <xmx:BIIBX69ccbo6NzkyhJz3TzDLFQNBs_6t0f248BbYFwENcG2G-s3R8g>
Received: from fv-az131.internal.cloudapp.net (unknown [52.175.247.93]) by mail.messagingengine.com (Postfix) with ESMTPA id 8F73D30682FD for <quic@ietf.org>; Sun,  5 Jul 2020 03:32:19 -0400 (EDT)
Content-Type: multipart/alternative; boundary="===============8867287642935453448=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: quic@ietf.org
Subject: Weekly github digest (QUIC Activity Summary)
Message-Id: <20200705073219.8F73D30682FD@mailuser.nyi.internal>
Date: Sun,  5 Jul 2020 03:32:19 -0400 (EDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/pEYvEv4BgC--vtg3b_I1sBw-DNw>
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, 05 Jul 2020 07:32:23 -0000

--===============8867287642935453448==
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 (+11/-0/=F0=9F=92=AC21)
  11 issues created:
  - Desirable behavior when it takes time to derive the traffic keys for th=
e next PN space (by kazuho)
    https://github.com/quicwg/base-drafts/issues/3821=20
  - Editorial Fiexes for HTTP-QUIC (by Jxck)
    https://github.com/quicwg/base-drafts/issues/3815=20
  - Broken Link in HTTP3 draft (by Jxck)
    https://github.com/quicwg/base-drafts/issues/3814=20
  - Minor fixes for the recovery draft (by kazu-yamamoto)
    https://github.com/quicwg/base-drafts/issues/3813=20
  - Versions are for endpoints (by martinthomson)
    https://github.com/quicwg/base-drafts/issues/3808 [-invariants]=20
  - Reset spin bit when probing (by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/3802 [-transport]=20
  - Which packet number spaces can't be reset? (by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/3801 [-transport]=20
  - Coalescing different CIDs for same connection (by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/3800 [-transport]=20
  - Draining after Idle Timeout? (by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/3798 [-transport]=20
  - PATH_RESPONSE isn't path-tied (by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/3797 [-transport]=20
  - Editorial nit: References to "CID" in transport draft (by tfpauly)
    https://github.com/quicwg/base-drafts/issues/3794=20

  10 issues received 21 new comments:
  - #3808 Versions are for endpoints (5 by LPardue, MikeBishop, larseggert)
    https://github.com/quicwg/base-drafts/issues/3808 [-invariants]=20
  - #3802 Reset spin bit when probing (1 by larseggert)
    https://github.com/quicwg/base-drafts/issues/3802 [-transport]=20
  - #3801 Which packet number spaces can't be reset? (3 by MikeBishop, kazu=
ho, larseggert)
    https://github.com/quicwg/base-drafts/issues/3801 [-transport]=20
  - #3800 Coalescing different CIDs for same connection (2 by larseggert, m=
artinthomson)
    https://github.com/quicwg/base-drafts/issues/3800 [-transport]=20
  - #3798 Draining after Idle Timeout? (2 by martinthomson)
    https://github.com/quicwg/base-drafts/issues/3798 [-transport]=20
  - #3788 New confidentiality and integrity limits (1 by larseggert)
    https://github.com/quicwg/base-drafts/issues/3788 [-tls]=20
  - #3784 Improve Large Server Certificate Scenario (3 by LPardue, larsegge=
rt)
    https://github.com/quicwg/base-drafts/issues/3784 [-transport]=20
  - #3765 disable_active_migration with SPA (2 by igorlord, larseggert)
    https://github.com/quicwg/base-drafts/issues/3765 [-transport]=20
  - #3722 QUIC Transport: Flow Control (1 by larseggert)
    https://github.com/quicwg/base-drafts/issues/3722 [-transport]=20
  - #3690 How to reject a connection attempt (1 by larseggert)
    https://github.com/quicwg/base-drafts/issues/3690 [-transport]=20

* quicwg/ops-drafts (+1/-0/=F0=9F=92=AC0)
  1 issues created:
  - Mention accidental invariants and the calculus of blocking (by britram)
    https://github.com/quicwg/ops-drafts/issues/96 [-manageability]=20

* quicwg/load-balancers (+3/-3/=F0=9F=92=AC5)
  3 issues created:
  - Make it clear the server might do length encoding on its own (by martin=
duke)
    https://github.com/quicwg/load-balancers/issues/38=20
  - Using ECB for retry tokens seems sub optimal (by huitema)
    https://github.com/quicwg/load-balancers/issues/35=20
  - Support of server generated HCID with retry tokens (by huitema)
    https://github.com/quicwg/load-balancers/issues/34=20

  4 issues received 5 new comments:
  - #35 Using ECB for retry tokens seems sub optimal (1 by huitema)
    https://github.com/quicwg/load-balancers/issues/35=20
  - #34 Support of server generated HCID with retry tokens (2 by huitema, m=
artinduke)
    https://github.com/quicwg/load-balancers/issues/34=20
  - #12 Configuration ID might be too small (1 by martinduke)
    https://github.com/quicwg/load-balancers/issues/12 [needs-discussion]=20
  - #8 Unguessable connection IDs (1 by martinduke)
    https://github.com/quicwg/load-balancers/issues/8 [needs-discussion]=20

  3 issues closed:
  - Support of server generated HCID with retry tokens https://github.com/q=
uicwg/load-balancers/issues/34=20
  - Tweak non-compliant DCID recommendation https://github.com/quicwg/load-=
balancers/issues/22=20
  - Add retry_source_connection_id to Retry Service Token Format https://gi=
thub.com/quicwg/load-balancers/issues/31=20



Pull requests
-------------
* quicwg/base-drafts (+1/-0/=F0=9F=92=AC4)
  1 pull requests submitted:
  - Update pseudocode references to removed function DetectLostPackets (by =
Ralith)
    https://github.com/quicwg/base-drafts/pull/3795=20

  1 pull requests received 4 new comments:
  - #3785 Version field <-> Version is not invariant (4 by ekr, martinduke,=
 martinthomson)
    https://github.com/quicwg/base-drafts/pull/3785 [-invariants] [design] =


* quicwg/load-balancers (+3/-3/=F0=9F=92=AC18)
  3 pull requests submitted:
  - One more config rotation bit. (by martinduke)
    https://github.com/quicwg/load-balancers/pull/37=20
  - Remove version-specific text (by martinduke)
    https://github.com/quicwg/load-balancers/pull/36=20
  - Describe 3 pass stream cipher. (by huitema)
    https://github.com/quicwg/load-balancers/pull/33=20

  3 pull requests received 18 new comments:
  - #37 One more config rotation bit. (8 by huitema, martinduke)
    https://github.com/quicwg/load-balancers/pull/37=20
  - #33 Describe 3 pass stream cipher. (8 by huitema, martinduke)
    https://github.com/quicwg/load-balancers/pull/33=20
  - #29 New Security Considerations (2 by martinduke, martinthomson)
    https://github.com/quicwg/load-balancers/pull/29=20

  3 pull requests merged:
  - Remove version-specific text
    https://github.com/quicwg/load-balancers/pull/36=20
  - Update text on Version Independence
    https://github.com/quicwg/load-balancers/pull/25=20
  - Add retry_source_connection_id to tokens
    https://github.com/quicwg/load-balancers/pull/32=20


Repositories tracked by this digest:
-----------------------------------
* https://github.com/quicwg/base-drafts
* https://github.com/quicwg/ops-drafts
* https://github.com/quicwg/datagram
* https://github.com/quicwg/load-balancers
* https://github.com/quicwg/version-negotiation

--===============8867287642935453448==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (QUIC 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 July 05, 2020</h1>

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

<h2>Issues</h2>

<h3>quicwg/base-drafts (+11/-0/=F0=9F=92=AC21)</h3>
  <p class=3D"new">11 issues created:</p>
  <ul>
  <li>#3821 <a href=3D"https://github.com/quicwg/base-drafts/issues/3821">D=
esirable behavior when it takes time to derive the traffic keys for the nex=
t PN space</a> (by kazuho) </li>
 =20
  <li>#3815 <a href=3D"https://github.com/quicwg/base-drafts/issues/3815">E=
ditorial Fiexes for HTTP-QUIC</a> (by Jxck) </li>
 =20
  <li>#3814 <a href=3D"https://github.com/quicwg/base-drafts/issues/3814">B=
roken Link in HTTP3 draft</a> (by Jxck) </li>
 =20
  <li>#3813 <a href=3D"https://github.com/quicwg/base-drafts/issues/3813">M=
inor fixes for the recovery draft</a> (by kazu-yamamoto) </li>
 =20
  <li>#3808 <a href=3D"https://github.com/quicwg/base-drafts/issues/3808">V=
ersions are for endpoints</a> (by martinthomson) <span class=3D"label" styl=
e=3D"background-color: #fbca04; color: #000000">-invariants</span> </li>
 =20
  <li>#3802 <a href=3D"https://github.com/quicwg/base-drafts/issues/3802">R=
eset spin bit when probing</a> (by MikeBishop) <span class=3D"label" style=
=3D"background-color: #fbca04; color: #000000">-transport</span> </li>
 =20
  <li>#3801 <a href=3D"https://github.com/quicwg/base-drafts/issues/3801">W=
hich packet number spaces can&#x27;t be reset?</a> (by MikeBishop) <span cl=
ass=3D"label" style=3D"background-color: #fbca04; color: #000000">-transpor=
t</span> </li>
 =20
  <li>#3800 <a href=3D"https://github.com/quicwg/base-drafts/issues/3800">C=
oalescing different CIDs for same connection</a> (by MikeBishop) <span clas=
s=3D"label" style=3D"background-color: #fbca04; color: #000000">-transport<=
/span> </li>
 =20
  <li>#3798 <a href=3D"https://github.com/quicwg/base-drafts/issues/3798">D=
raining after Idle Timeout?</a> (by MikeBishop) <span class=3D"label" style=
=3D"background-color: #fbca04; color: #000000">-transport</span> </li>
 =20
  <li>#3797 <a href=3D"https://github.com/quicwg/base-drafts/issues/3797">P=
ATH_RESPONSE isn&#x27;t path-tied</a> (by MikeBishop) <span class=3D"label"=
 style=3D"background-color: #fbca04; color: #000000">-transport</span> </li>
 =20
  <li>#3794 <a href=3D"https://github.com/quicwg/base-drafts/issues/3794">E=
ditorial nit: References to &quot;CID&quot; in transport draft</a> (by tfpa=
uly) </li>
  </ul>

  <p>10 issues received 21 new comments:</p>
  <ul>
  <li>#3808 <a href=3D"https://github.com/quicwg/base-drafts/issues/3808">V=
ersions are for endpoints</a> (5 by LPardue, MikeBishop, larseggert) <span =
class=3D"label" style=3D"background-color: #fbca04; color: #000000">-invari=
ants</span> </li>
 =20
  <li>#3802 <a href=3D"https://github.com/quicwg/base-drafts/issues/3802">R=
eset spin bit when probing</a> (1 by larseggert) <span class=3D"label" styl=
e=3D"background-color: #fbca04; color: #000000">-transport</span> </li>
 =20
  <li>#3801 <a href=3D"https://github.com/quicwg/base-drafts/issues/3801">W=
hich packet number spaces can&#x27;t be reset?</a> (3 by MikeBishop, kazuho=
, larseggert) <span class=3D"label" style=3D"background-color: #fbca04; col=
or: #000000">-transport</span> </li>
 =20
  <li>#3800 <a href=3D"https://github.com/quicwg/base-drafts/issues/3800">C=
oalescing different CIDs for same connection</a> (2 by larseggert, martinth=
omson) <span class=3D"label" style=3D"background-color: #fbca04; color: #00=
0000">-transport</span> </li>
 =20
  <li>#3798 <a href=3D"https://github.com/quicwg/base-drafts/issues/3798">D=
raining after Idle Timeout?</a> (2 by martinthomson) <span class=3D"label" =
style=3D"background-color: #fbca04; color: #000000">-transport</span> </li>
 =20
  <li>#3788 <a href=3D"https://github.com/quicwg/base-drafts/issues/3788">N=
ew confidentiality and integrity limits</a> (1 by larseggert) <span class=
=3D"label" style=3D"background-color: #fbca04; color: #000000">-tls</span> =
</li>
 =20
  <li>#3784 <a href=3D"https://github.com/quicwg/base-drafts/issues/3784">I=
mprove Large Server Certificate Scenario</a> (3 by LPardue, larseggert) <sp=
an class=3D"label" style=3D"background-color: #fbca04; color: #000000">-tra=
nsport</span> </li>
 =20
  <li>#3765 <a href=3D"https://github.com/quicwg/base-drafts/issues/3765">d=
isable_active_migration with SPA</a> (2 by igorlord, larseggert) <span clas=
s=3D"label" style=3D"background-color: #fbca04; color: #000000">-transport<=
/span> </li>
 =20
  <li>#3722 <a href=3D"https://github.com/quicwg/base-drafts/issues/3722">Q=
UIC Transport: Flow Control</a> (1 by larseggert) <span class=3D"label" sty=
le=3D"background-color: #fbca04; color: #000000">-transport</span> </li>
 =20
  <li>#3690 <a href=3D"https://github.com/quicwg/base-drafts/issues/3690">H=
ow to reject a connection attempt</a> (1 by larseggert) <span class=3D"labe=
l" style=3D"background-color: #fbca04; color: #000000">-transport</span> </=
li>
  </ul>


<h3>quicwg/ops-drafts (+1/-0/=F0=9F=92=AC0)</h3>
  <p class=3D"new">1 issues created:</p>
  <ul>
  <li>#96 <a href=3D"https://github.com/quicwg/ops-drafts/issues/96">Mentio=
n accidental invariants and the calculus of blocking</a> (by britram) <span=
 class=3D"label" style=3D"background-color: #fbca04; color: #000000">-manag=
eability</span> </li>
  </ul>



<h3>quicwg/load-balancers (+3/-3/=F0=9F=92=AC5)</h3>
  <p class=3D"new">3 issues created:</p>
  <ul>
  <li>#38 <a href=3D"https://github.com/quicwg/load-balancers/issues/38">Ma=
ke it clear the server might do length encoding on its own</a> (by martindu=
ke) </li>
 =20
  <li>#35 <a href=3D"https://github.com/quicwg/load-balancers/issues/35">Us=
ing ECB for retry tokens seems sub optimal</a> (by huitema) </li>
 =20
  <li>#34 <a href=3D"https://github.com/quicwg/load-balancers/issues/34">Su=
pport of server generated HCID with retry tokens</a> (by huitema) </li>
  </ul>

  <p>4 issues received 5 new comments:</p>
  <ul>
  <li>#35 <a href=3D"https://github.com/quicwg/load-balancers/issues/35">Us=
ing ECB for retry tokens seems sub optimal</a> (1 by huitema) </li>
 =20
  <li>#34 <a href=3D"https://github.com/quicwg/load-balancers/issues/34">Su=
pport of server generated HCID with retry tokens</a> (2 by huitema, martind=
uke) </li>
 =20
  <li>#12 <a href=3D"https://github.com/quicwg/load-balancers/issues/12">Co=
nfiguration ID might be too small</a> (1 by martinduke) <span class=3D"labe=
l" style=3D"background-color: #32d5db; color: #000000">needs-discussion</sp=
an> </li>
 =20
  <li>#8 <a href=3D"https://github.com/quicwg/load-balancers/issues/8">Ungu=
essable connection IDs</a> (1 by martinduke) <span class=3D"label" style=3D=
"background-color: #32d5db; color: #000000">needs-discussion</span> </li>
  </ul>

  <p>3 issues closed:</p>
  <ul>
  <li>#34 <a href=3D"https://github.com/quicwg/load-balancers/issues/34">Su=
pport of server generated HCID with retry tokens</a> </li>
 =20
  <li>#22 <a href=3D"https://github.com/quicwg/load-balancers/issues/22">Tw=
eak non-compliant DCID recommendation</a> </li>
 =20
  <li>#31 <a href=3D"https://github.com/quicwg/load-balancers/issues/31">Ad=
d retry_source_connection_id to Retry Service Token Format</a> </li>
  </ul>



<h2>Pull requests</h2>
<h3>quicwg/base-drafts (+1/-0/=F0=9F=92=AC4)</h3>
  <p class=3D"new">1 pull requests submitted:</p>
  <ul>
  <li>#3795 <a href=3D"https://github.com/quicwg/base-drafts/pull/3795">Upd=
ate pseudocode references to removed function DetectLostPackets</a> (by Ral=
ith) </li>
  </ul>

  <p>1 pull requests received 4 new comments:</p>
  <ul>
  <li>#3785 <a href=3D"https://github.com/quicwg/base-drafts/pull/3785">Ver=
sion field &lt;-&gt; Version is not invariant</a> (4 by ekr, martinduke, ma=
rtinthomson) <span class=3D"label" style=3D"background-color: #fbca04; colo=
r: #000000">-invariants</span> <span class=3D"label" style=3D"background-co=
lor: #1d76db; color: #ffffff">design</span> </li>
  </ul>


<h3>quicwg/load-balancers (+3/-3/=F0=9F=92=AC18)</h3>
  <p class=3D"new">3 pull requests submitted:</p>
  <ul>
  <li>#37 <a href=3D"https://github.com/quicwg/load-balancers/pull/37">One =
more config rotation bit.</a> (by martinduke) </li>
 =20
  <li>#36 <a href=3D"https://github.com/quicwg/load-balancers/pull/36">Remo=
ve version-specific text</a> (by martinduke) </li>
 =20
  <li>#33 <a href=3D"https://github.com/quicwg/load-balancers/pull/33">Desc=
ribe 3 pass stream cipher.</a> (by huitema) </li>
  </ul>

  <p>3 pull requests received 18 new comments:</p>
  <ul>
  <li>#37 <a href=3D"https://github.com/quicwg/load-balancers/pull/37">One =
more config rotation bit.</a> (8 by huitema, martinduke) </li>
 =20
  <li>#33 <a href=3D"https://github.com/quicwg/load-balancers/pull/33">Desc=
ribe 3 pass stream cipher.</a> (8 by huitema, martinduke) </li>
 =20
  <li>#29 <a href=3D"https://github.com/quicwg/load-balancers/pull/29">New =
Security Considerations</a> (2 by martinduke, martinthomson) </li>
  </ul>

  <p>3 pull requests merged:</p>
  <ul>
  <li>#36 <a href=3D"https://github.com/quicwg/load-balancers/pull/36">Remo=
ve version-specific text</a> </li>
 =20
  <li>#25 <a href=3D"https://github.com/quicwg/load-balancers/pull/25">Upda=
te text on Version Independence</a> </li>
 =20
  <li>#32 <a href=3D"https://github.com/quicwg/load-balancers/pull/32">Add =
retry_source_connection_id to tokens</a> </li>
  </ul>


<h2>Repositories tracked by this digest:</h2>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/quicwg/base-drafts">https://github.com/=
quicwg/base-drafts</a></li>
  <li><a href=3D"https://github.com/quicwg/ops-drafts">https://github.com/q=
uicwg/ops-drafts</a></li>
  <li><a href=3D"https://github.com/quicwg/datagram">https://github.com/qui=
cwg/datagram</a></li>
  <li><a href=3D"https://github.com/quicwg/load-balancers">https://github.c=
om/quicwg/load-balancers</a></li>
  <li><a href=3D"https://github.com/quicwg/version-negotiation">https://git=
hub.com/quicwg/version-negotiation</a></li>
  </ul>
</body>
</html>

--===============8867287642935453448==--


From nobody Sun Jul  5 13:27:08 2020
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 499433A0AE5 for <quic@ietfa.amsl.com>; Sun,  5 Jul 2020 13:27:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 UKsp5qWzdS33 for <quic@ietfa.amsl.com>; Sun,  5 Jul 2020 13:27:05 -0700 (PDT)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 0BB7D3A0AE3 for <quic@ietf.org>; Sun,  5 Jul 2020 13:27:04 -0700 (PDT)
Received: by mail-qt1-x82b.google.com with SMTP id b25so6123838qto.2 for <quic@ietf.org>; Sun, 05 Jul 2020 13:27:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=RjrzA3obfITttu+1O9Pa2a67iTP0cGwFGBW0GOKg0Bg=; b=Uf8D7/R7qmwlw97GjIU8hHrf/9bCV20h2gOzudUDxuO1f22+mgs6Hy/2klKvSEWJZu 0uou3pnar5Qzkfyd8R0yb+ENUbxCSTzsGSH9WXPgK4V+2KlIR3pHzao/SO2v0hYxsPwB st4fSPFH/TULk+LV/5EwNUT/MqXo7Duo1nCmJBa/BavCFrwg3gxlKrhAEmZn80vVqfyZ rkAquSD+xeGYbFNC8b8mp33vy2lKEGyfEZ9hfnin3q+HyMY4pLiZwkoNTEYoKWNaqXmm mRFXvGAZWSjE5KZ2lX+TJ9iYqS8c4CDwGME4IkCAKQQNcNGKIxnO9xASbYhHFlhGNXhU XsnA==
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=RjrzA3obfITttu+1O9Pa2a67iTP0cGwFGBW0GOKg0Bg=; b=tXs/u7394+9q7LD1bOAK9i0a4h511KrysWjdkWplZFFh2qIOQ/p8UPF2L246zO83Ap GjBJlA/t1bja4oP0SPSqAdOUS23zX1ulo1H2Y3erG3uD5n3FosafiCPo3TqZlCiwE1Bq Wa6rVv0eN9Uz9zf/DZJhOpSF2I2pkNb5UEBUuGZKt9AA2fWra+sE2BTgXlbkps6QFgNv 0XI03XKqEiwkWncWPLAM4QHotK3pt2HAQyBj06knFKhKHmV0XpvZ7DbaFE0mwJu8G9N8 u1JU2sU5m8p98lG/c3TbQzwMHm8BFYj9JLngHiCTI8z4kMrctQZmtlVGm4H3HHzlEFBb juaA==
X-Gm-Message-State: AOAM533pSxxca5to3S7Coz/QlyqSJ3dTajz29FYAwUi2Bs1iVQUxUScS L/3+P+agJhatKSZloBnEdd9GykiiwpeGfg==
X-Google-Smtp-Source: ABdhPJy6p1kiwAgIzhA5kTHajFI/LeU/VGr2Yvx1ogcZG4JiEyDVkVRsEGq2dUwu7C8iY0XQPA0LMg==
X-Received: by 2002:aed:35d8:: with SMTP id d24mr47956042qte.246.1593980823832;  Sun, 05 Jul 2020 13:27:03 -0700 (PDT)
Received: from lubuntu (ool-44c1d219.dyn.optonline.net. [68.193.210.25]) by smtp.gmail.com with ESMTPSA id z4sm17055127qkb.66.2020.07.05.13.27.02 for <quic@ietf.org> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sun, 05 Jul 2020 13:27:03 -0700 (PDT)
Date: Sun, 5 Jul 2020 16:26:53 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: quic@ietf.org
Subject: Re: Greasing the QUIC Bit
Message-ID: <20200705202652.GB3335@lubuntu>
Mail-Followup-To: quic@ietf.org
References: <5943e1bd-fba9-473b-a20f-7992ad0579ab@www.fastmail.com> <CH2PR22MB2086FD91E42AC403D85DC42FDA6D0@CH2PR22MB2086.namprd22.prod.outlook.com> <65c908df-7123-46ee-838c-575f8154c811@www.fastmail.com> <9db597a6-5e75-4df6-5447-8204d052100c@huitema.net>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9db597a6-5e75-4df6-5447-8204d052100c@huitema.net>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/V3wyihLy6pbktILRSI8H_ZwDzKY>
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, 05 Jul 2020 20:27:06 -0000

On Fri, Jul 03, 2020 at 07:02:55PM -0700, Christian Huitema wrote:
> I am almost done implementing this in picoquic, I just have a question
> about to set the quic bit if the option is negotiated
> 
> The spec says "use an unpredictable value", and I am hesitating between
> three options:
> 
> 1) flip a coin upon negotiation of the TP, and set all Quic Bits for the
> connection to the selected value.
> 
> 2) flip the bit at every packet.
> 
> 3) run a random number generator for each packet.

The draft does not make it clear whether the "unpredicable value" is
per connection or per packet:

 " Endpoints that receive the grease_quic_bit transport parameter from a
 " peer MAY set the QUIC Bit to any value in packets they sent to that
 " peer.  Endpoints SHOULD set the QUIC Bit to an unpredictable value
 " unless another extension assigns specific meaning to the value of the
 " bit.

When I read it the first time around, I interpreted it as "per packet."
If one interprets it as "per connection," it makes for the most efficient
method, which would be my preference.

  - Dmitri.


From nobody Sun Jul  5 17:25:57 2020
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 D608E3A0C57 for <quic@ietfa.amsl.com>; Sun,  5 Jul 2020 17:25:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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=lowentropy.net header.b=B0KfzEzw; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=AnpsTn2l
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KAY3T6diPdXw for <quic@ietfa.amsl.com>; Sun,  5 Jul 2020 17:25:54 -0700 (PDT)
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 B829D3A0C52 for <quic@ietf.org>; Sun,  5 Jul 2020 17:25:54 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 13F8842D for <quic@ietf.org>; Sun,  5 Jul 2020 20:25:54 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Sun, 05 Jul 2020 20:25:54 -0400
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=fm2; bh=lGGvVkEXdVy6qmCQJaopk/ZbQ3T4CKu kAuzYxyFI9Rc=; b=B0KfzEzwvDFjtxgkAgBSP0ROFAZ1UckwVYHUeZmjv+zGBGB BeIxoV49+Zn5zcAkUQxcT74jSxB7yOV+8VjZEOktOjhJKx0e0lGSriaEbdpL/VtE DgpqCONNERqaBLBo7aIgeDsEKllWdaCyVDrnzZ1XlC5jTSl+vXLRzh3kTjkO86SC qQ32YiBAHZqIByMiBNzJzY9zG9OrVdiB+QKozEU6P3ansBd+dvzUy5QSeAcJ7mQf Q93CHlhtWCfiuumx+JKG4Fueuljcu+QR+vysrxYEiFjRVWyBLHC/HONJMyr/uiVl Fhd3h1jhbv0gp/VOTJ5W2FJsaCo6yftREwC86dw==
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=fm3; bh=lGGvVk EXdVy6qmCQJaopk/ZbQ3T4CKukAuzYxyFI9Rc=; b=AnpsTn2l9pf5fKJRTRHOR3 YZUcNVfdoewtd0n5oaJjqKr5LmCx+lglS0dkfG6bK2DQGsZsTH5740M91nj1xnKQ gUp6wArkl7AV6EOKE8Z/gM98R5beiUZmaPjX8wQnE9bEg8bw0iDLlPCpi4GGiJix aW3IDrL1OWU+XK2Heanu9EIQYgypPpPC/R3t10QPPABL2PEkaGSSacRI70edi1X9 UPAoq/wINDMJzlPbKwg7pDZfvLoyqHD4IFi77NLvxygha/EwiF0dPjjOOiQvMtWD jC7VR4JGxhjjML3TPgaTOIqtMoolQdzGXjgLaVtmr11blnP16a1AQ0j9YF9WXTCw ==
X-ME-Sender: <xms:j28CX2gTXMvewjRbUL0692JXcYY2aJbhFrJyvsfv_WQpzYnyBDlg3g>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedruddvgdefudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif vghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepkeetueeikedtkeelfeekve fhkeffvedvvefgkefgleeugfdvjeejgeffieegtdejnecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:kG8CX3DPeat2mus2y_YRLimZ3WCAlTf5SB8rjD0UF3mmEIfM9CpQ4A> <xmx:kG8CX-FK3MW9XQbvJlD7Cuflx-0gaXBTbAR5_8isB5gsD2m9k81esg> <xmx:kG8CX_RzYZSlelNi-z5L-U-N9uZ6XYakGUq6cXY7JqdZ7HXtMLGfqg> <xmx:kW8CX_jpnGlsYr_NvL73GuEvrBzWynwhWyWpX44FVzhQlIo8XK4WvQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id DBE92E00AA; Sun,  5 Jul 2020 20:25:51 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-576-gfe2cd66-fm-20200629.001-gfe2cd668
Mime-Version: 1.0
Message-Id: <b709d886-d217-4988-8286-53af77fd04b2@www.fastmail.com>
In-Reply-To: <20200705202652.GB3335@lubuntu>
References: <5943e1bd-fba9-473b-a20f-7992ad0579ab@www.fastmail.com> <CH2PR22MB2086FD91E42AC403D85DC42FDA6D0@CH2PR22MB2086.namprd22.prod.outlook.com> <65c908df-7123-46ee-838c-575f8154c811@www.fastmail.com> <9db597a6-5e75-4df6-5447-8204d052100c@huitema.net> <20200705202652.GB3335@lubuntu>
Date: Mon, 06 Jul 2020 10:25:32 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: quic@ietf.org
Subject: Re: Greasing the QUIC Bit
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/eCFigohrx2zXLYmY5loxcaF_koQ>
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, 06 Jul 2020 00:25:56 -0000

On Mon, Jul 6, 2020, at 06:26, Dmitri Tikhonov wrote:
> When I read it the first time around, I interpreted it as "per packet."
> If one interprets it as "per connection," it makes for the most efficient
> method, which would be my preference.

I had intended per packet, but I see how how you might interpret that differently.  I think that you achieve the desired outcome if you make it "per connection ID".  Using per connection adds a bit of entropy that can be used to link activity across paths.  Whatever scope you choose it needs to be based on something everyone knows.  Changing daily across all connections would also likely work (and would produce some interesting stats).


From nobody Sun Jul  5 17:41:08 2020
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 E40E83A0C7D for <quic@ietfa.amsl.com>; Sun,  5 Jul 2020 17:41:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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=lowentropy.net header.b=WVK4RKQQ; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=O0lZz68S
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id L54Tcg-gWIx5 for <quic@ietfa.amsl.com>; Sun,  5 Jul 2020 17:41:06 -0700 (PDT)
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 8AC543A0C7C for <quic@ietf.org>; Sun,  5 Jul 2020 17:41:06 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 28C22453 for <quic@ietf.org>; Sun,  5 Jul 2020 20:41:05 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Sun, 05 Jul 2020 20:41:05 -0400
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=fm2; bh=UbOD8 D6gN8g769mJxHqg94qciIPVB+Wkf40vinZGbGI=; b=WVK4RKQQ1RdWOSU7THgO0 yyJgJPW9rYe1jOIZL9J4kaPyUmyU68TiFr/mpmxMl6GL3V7rXXISxr39maTvChUH k3zO8dYflZMGV9cTAz93znfBQsU7Ag30OD1/G4wNEOd4L4bBL3STWCUSkWkFpUYE kT6i99PojFx83ntCLp991LpXzskg/vKbzmGuMbfQWNsnff8oEN2PUM03PTvqJHTv kC/6FapTXs8Vf4Pwe4lpOSus1LohQIjnYh2GoEiyxXG6MyaGjPO2l42rkVqz7DrO d6P2ZcDkMkuyLnGzEqZUjbUqzMSRvaY9Zmb0XniLqp66xYlcCEFBz/2JmfwuuA38 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=fm3; bh=UbOD8D6gN8g769mJxHqg94qciIPVB+Wkf40vinZGb GI=; b=O0lZz68SjWx03IGMdvmICIvo1i37ycgUxFC2xTJO7WEHxNdCm4v/UwJYk bCQDXVmJ6shvYvGt2VptByQM/ciiBLFSJHq18YMCOf51PdX5lV7RhwmrcdExYr7d U9+yQOqZSlDDBaw1lwhFT++SvY0bOo63uMR+DdDVMA91/gM1C0vTjCj2BeBhqYm9 +VL57Sfxw6u/+4qD5QoGph3EhX6V9y+R+3ryCI7wjq8j+WxQKLQSlS8U6BHbYGFN V1GG9T+SAMuJdWGk1EApF/0JcVoAt1Ky7gk2rLy09ShQf2/l+hdtZgBbakSe5Akl iUzbkM5zjsNsuAB18ShrQ98mSVk6Q==
X-ME-Sender: <xms:IHMCXxb6Sr0HE1tifmZ0ieI-R0Ishm8oPBdCM_h2GawQ7y68zj2Tjg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedruddvgdefgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgfgsehtqh ertderreejnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhho figvnhhtrhhophihrdhnvghtqeenucggtffrrghtthgvrhhnpefftefgvedvhfdtffehje dufefhhfevhedufefhgfelleetieefgeefgffgleehgfenucffohhmrghinhepihgvthhf rdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh epmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:IHMCX4Zb2t2ZK0hd2Y-84FT5RajuLi35J8qZ9cIOxBTux1GYJaou1g> <xmx:IHMCXz-0Gy9iO-g73bWtQbElYiQUFX2FuUEocFjqoEzc4qFJuMUCHw> <xmx:IHMCX_rEswNTFjMri2Fiw-7FkN1grHTB6Doz8pO796k0LCQoet8iCQ> <xmx:IHMCX16FLRFnPTjr1VZ8MbB_0p49Zz-ZQjyXiMwBIZna2ZjamJapRQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 68BB4E00AA; Sun,  5 Jul 2020 20:41:04 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-576-gfe2cd66-fm-20200629.001-gfe2cd668
Mime-Version: 1.0
Message-Id: <cd99a66b-6478-4b15-b6fc-0c512e92e118@www.fastmail.com>
In-Reply-To: <719A2C1D4AC73847B6E1BF21DF1545EAE5C7CE04@dggemm534-mbs.china.huawei.com>
References: <719A2C1D4AC73847B6E1BF21DF1545EAE5C7CE04@dggemm534-mbs.china.huawei.com>
Date: Mon, 06 Jul 2020 10:40:44 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: quic@ietf.org
Subject: Re: Hope a discussion for draft-li-quic-optimizing-ack-in-wlan-00
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7hSt5o7ZH7s5TQXhhyX2U24JguM>
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, 06 Jul 2020 00:41:08 -0000

Can you speak a little about the relationship with draft-iyengar-quic-de=
layed-ack ?

On Sat, Jul 4, 2020, at 16:05, Kangjiao wrote:
> =20
> Dear QUIC WG members,
>=20
>=20
> We uploaded a draft describing a mechanism for ACK optimization to QUI=
C=20
> group. The link is=20
> https://datatracker.ietf.org/doc/draft-li-quic-optimizing-ack-in-wlan/=
.=20
> This solution comes from our practice and the results show it is a goo=
d=20
> replacement of the traditional ACK mechanism to compensate for=20
> scenarios where the acknowledgement overhead is non-negligible (i.e.,=20=

> wireless scenarios).
>=20
>=20
> The key points for this solution can be:
>=20
>=20
> 1. We conclude the formula of the minimum ACK intensity required for=20=

> QUIC transport.
>=20
>=20
> 2. In order to alleviate the error in RTT estimation, we use protocol=20=

> extensions and a one-way delay factor. We think this round-trip timing=
=20
> method can also be applicable for the ack thinning mechanisms (such as=
=20
> =E2=80=9DChanging the Default QUIC ACK Policy=E2=80=9D #3529) that hav=
e been discussed=20
> in QUIC group..
>=20
>=20
> 3. For implementation and interoperability, we define a new=20
> ACK-INTENSITY Frame in which ACK Intensity is set. ACK Intensity is a=20=

> variable-length integer indicating the updated intensity of QUIC ACK=20=

> Frame calculated by our formula.
>=20
>=20
> We look forward to your valuable comments and suggestions. Thanks.
>=20
>=20
> Sincerely,
>=20
> Jiao
>


From nobody Mon Jul  6 07:35:28 2020
Return-Path: <kangjiao@huawei.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1750F3A1572 for <quic@ietfa.amsl.com>; Mon,  6 Jul 2020 07:35:26 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level: 
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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 wL9oM1S8Jb9M for <quic@ietfa.amsl.com>; Mon,  6 Jul 2020 07:35:23 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 9D3F83A1501 for <quic@ietf.org>; Mon,  6 Jul 2020 07:35:23 -0700 (PDT)
Received: from lhreml712-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id C21BFCD5A7F243ACD695 for <quic@ietf.org>; Mon,  6 Jul 2020 15:35:18 +0100 (IST)
Received: from lhreml712-chm.china.huawei.com (10.201.108.63) by lhreml712-chm.china.huawei.com (10.201.108.63) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1913.5; Mon, 6 Jul 2020 15:35:18 +0100
Received: from DGGEMM406-HUB.china.huawei.com (10.3.20.214) by lhreml712-chm.china.huawei.com (10.201.108.63) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA) id 15.1.1913.5 via Frontend Transport; Mon, 6 Jul 2020 15:35:17 +0100
Received: from DGGEMM534-MBS.china.huawei.com ([169.254.7.44]) by DGGEMM406-HUB.china.huawei.com ([10.3.20.214]) with mapi id 14.03.0487.000; Mon, 6 Jul 2020 22:35:12 +0800
From: Kangjiao <kangjiao@huawei.com>
To: Martin Thomson <mt@lowentropy.net>
CC: "quic@ietf.org" <quic@ietf.org>
Subject: RE: Hope a discussion for draft-li-quic-optimizing-ack-in-wlan-00
Thread-Topic: Hope a discussion for draft-li-quic-optimizing-ack-in-wlan-00
Thread-Index: AdZRyGcTBCKzXYE+TnatOw5glQUhXgBIp/IAAC2b1RA=
Date: Mon, 6 Jul 2020 14:35:12 +0000
Message-ID: <719A2C1D4AC73847B6E1BF21DF1545EAE5C7EDFD@dggemm534-mbs.china.huawei.com>
References: <719A2C1D4AC73847B6E1BF21DF1545EAE5C7CE04@dggemm534-mbs.china.huawei.com> <cd99a66b-6478-4b15-b6fc-0c512e92e118@www.fastmail.com>
In-Reply-To: <cd99a66b-6478-4b15-b6fc-0c512e92e118@www.fastmail.com>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.46.118.154]
Content-Type: multipart/alternative; boundary="_000_719A2C1D4AC73847B6E1BF21DF1545EAE5C7EDFDdggemm534mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/CapRKuku9na1bCxIjUTlSH6Y8sc>
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, 06 Jul 2020 14:35:26 -0000

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

RGVhciBNYXJ0aW4sDQoNCg0KDQpIZXJlIGFyZSB0aGUgdHdvIGRyYWZ0czoNCg0KZHJhZnQtbGkt
cXVpYy1vcHRpbWl6aW5nLWFjay1pbi13bGFuLTAwOiBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0
bWwvZHJhZnQtbGktcXVpYy1vcHRpbWl6aW5nLWFjay1pbi13bGFuLTAwDQoNCmRyYWZ0LWl5ZW5n
YXItcXVpYy1kZWxheWVkLWFjay0wMDogaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0
LWl5ZW5nYXItcXVpYy1kZWxheWVkLWFjay0wMA0KDQoNCg0KSSBoYXZlIG91dGxpbmVkIHNvbWUg
ZGlzdGluY3Rpb24gYW5kIGNvbm5lY3Rpb24gYmV0d2VlbiB0aGVzZSB0d28gZHJhZnRzOg0KDQoN
Cg0KYSkgICAgICAgQm90aCBkcmFmdC1saS1xdWljLW9wdGltaXppbmctYWNrLWluLXdsYW4tMDAg
YW5kIGRyYWZ0LWl5ZW5nYXItcXVpYy1kZWxheWVkLWFjay0wMCBwcm9wb3NlIGEgc29sdXRpb24g
dG8gcmVkdWNlIHRoZSBBQ0sgZnJlcXVlbmN5IGZvciBRVUlDLiBkcmFmdC1peWVuZ2FyLXF1aWMt
ZGVsYXllZC1hY2stMDAgbWFrZXMgdGhlIHR3byBwYXJhbWV0ZXJzIGluIGRlbGF5ZWQgQUNLLCBp
LmUuLCAiUGFja2V0IFRvbGVyYW5jZSIgYW5kICJNYXggQWNrIERlbGF5IiwgYmUgdHVuYWJsZSBi
eSB0aGUgc2VuZGVyLiBUaGVzZSB0d28gdHVuYWJsZSBwYXJhbWV0ZXJzIGRvIG5vdCBpbmNsdWRl
IFJUVCBhcyBhIGZhY3Rvci4gU2FyYSBMYW5kc3Ryb20gZXQgYWwuIFsxXSBoYXMgZGVtb25zdHJh
dGVkIHRoYXQsIGluIHRoZW9yeSwgdGhlIGVuZHBvaW50IHNob3VsZCBhY2tub3dsZWRnZSBkYXRh
IGF0IGxlYXN0IHR3aWNlIHBlciBzZW5kIHdpbmRvdyAoUlRUKSB0byBlbnN1cmUgdXRpbGl6YXRp
b24uIEluIHRoaXMgY2FzZSwgcmVkdWNpbmcgQUNLIGZyZXF1ZW5jeSB3aXRob3V0IGNvbnNpZGVy
aW5nIHRoZSBSVFQgYXMgYSBmYWN0b3Igb2YgTWF4IEFjayBEZWxheSwgbWlnaHQgY2F1c2UgcGVy
Zm9ybWFuY2UgaXNzdWVzLiBPbiB0aGUgb3RoZXIgaGFuZCwgdGhlIHB1cnBvc2UgaW4gZHJhZnQt
bGktcXVpYy1vcHRpbWl6aW5nLWFjay1pbi13bGFuLTAwIGlzIHRvIG1pbmltaXplIHRoZSBBQ0sg
ZnJlcXVlbmN5IHJlcXVpcmVkIGJ5IHRoZSB0cmFuc3BvcnQsIHRodXMgdGhlIEFDSyBmcmVxdWVu
Y3kgaXMgY29tcHV0ZWQgYXMgTUlOe2J3LyhwYWNrZXRfdG9sZXJhbmNlICptYXhfcGFja2V0X3Np
emUpLCBiZXRhL1JUVG1pbn0gKGJldGEgaW5kaWNhdGVzIHRoZSBudW1iZXIgb2YgQUNLcyBwZXIg
UlRUKS4gV2hpbGUgZHJhZnQtaXllbmdhci1xdWljLWRlbGF5ZWQtYWNrLTAwIGFkb3B0cyB0aGUg
ZXh0ZW5kZWQgZGVsYXllZCBBQ0sgYXMgc3BlY2lmaWVkIGluIHRoZSBsZWdhY3kgVENQLCB3aG9z
ZSBBQ0sgZnJlcXVlbmN5IGlzIGNvbXB1dGVkIGFzIE1BWHtidy8oIHBhY2tldF90b2xlcmFuY2Ug
Km1heF9wYWNrZXRfc2l6ZSksIDEvIG1heF9hY2tfZGVsYXl9LiBBIHBhcGVyIFsyXSAodG8gYmUg
YXBwZWFyZWQgaW4gU0lHQ09NTTIwMjApIGhhcyBkZW1vbnN0cmF0ZWQgdGhhdCB1c2luZyBhIE1J
TiBpbnN0ZWFkIG9mIGEgTUFYIGNhbiBhbHNvIGFjaGlldmUgZXF1YWxseSBnb29kIHBlcmZvcm1h
bmNlLg0KDQoNCg0KYikgICAgICAgZHJhZnQtaXllbmdhci1xdWljLWRlbGF5ZWQtYWNrLTAwIHBy
b3ZpZGVzIGEgd2F5IGZvciB0aGUgc2VuZGVyIHRvIGN1c3RvbWl6ZSB0aGUgQUNLIGZyZXF1ZW5j
eS4gVGhpcyBtZWFucyB0aGUgQUNLcyBtaWdodCBiZSBleGNlc3NpdmVseSBkZWxheWVkIHdoZW4g
dGhlIE1heCBBY2sgRGVsYXkgaXMgbGFyZ2UuIFdoZW4gc2VuZGluZyBmZXdlciBBQ0sgZnJhbWVz
LCBtYW55IGRhdGEgcGFja2V0cyBtaWdodCBiZSByZWNlaXZlZCBkdXJpbmcgdGhlIEFDSyBpbnRl
cnZhbCwgZ2VuZXJhdGluZyBvbmx5IG9uZSBSVFQgc2FtcGxlIGFtb25nIG11bHRpcGxlIHBhY2tl
dHMgaXMgbGlrZWx5IHRvIHJlc3VsdCBpbiBiaWFzZXMuIEZvciBleGFtcGxlLCBhIGxhcmdlciBt
aW5pbXVtIFJUVCBlc3RpbWF0ZS4gSW4gZHJhZnQtbGktcXVpYy1vcHRpbWl6aW5nLWFjay1pbi13
bGFuLTAwLCB3ZSBwcm9wb3NlIGEgb25lLXdheS1kZWxheS1iYXNlZCBtZXRob2QgdG8gY29tcHV0
ZSB0aGUgbWluaW11bSBSVFQgbW9yZSBhY2N1cmF0ZWx5LiBBcGFydCBmcm9tIHRoZSBBQ0sgc2No
ZW1lLCB0aGlzIGlzIGFub3RoZXIgcG9pbnQgdGhhdCB3ZSB3b3VsZCBsaWtlIHRvIGRpc2N1c3Mg
YW5kIGdldCBmZWVkYmFjayBmcm9tIFFVSUMgV0cuDQoNCg0KDQpjKSAgICAgICBXaXRoIHNvbWUg
bWlub3IgZXh0ZW5zaW9ucyBzdWNoIGFzIGFkZGluZyBvbmUgbW9yZSBmaWVsZCBvZiBBQ0stSU5U
RU5TSVRZLCB0aGUgcHJvcG9zZWQgQUNLIHNjaGVtZSBpbiBkcmFmdC1saS1xdWljLW9wdGltaXpp
bmctYWNrLWluLXdsYW4tMDAgbWF5IGJlIGFibGUgdG8gcmV1c2UgdGhlIEFDSy1GRVFVRU5DWSBm
cmFtZSBzcGVjaWZpZWQgaW4gZHJhZnQtaXllbmdhci1xdWljLWRlbGF5ZWQtYWNrLTAwIHRvIHN5
bmMgdGhlIEFDSyBpbnRlbnNpdHkgYmV0d2VlbiBzZW5kZXIgYW5kIHJlY2VpdmVyLg0KDQoNCg0K
U29tZSByZWZlcmVuY2UgbWVudGlvbmVkIGFib3ZlOg0KDQpbMV0gU2FyYSBMYW5kc3Ryb20gYW5k
IExhcnMtQWtlIExhcnpvbi4gMjAwNy4gUmVkdWNpbmcgdGhlIFRDUCBhY2tub3dsZWRnbWVudCBm
cmVxdWVuY3kuIEFDTSBTSUdDT01NIENDUiAzNywgMyAoMjAwNyksIDXigJMxNi4NCg0KWzJdIFRv
bmcgTGksIEthaSBaaGVuZywgS2UgWHUsIFJhaHVsIEFydmluZCBKYWRoYXYsIFRhbyBYaW9uZywg
S2VpdGggV2luc3RlaW4sIEt1biBUYW4uICJUQUNLOiBJbXByb3ZpbmcgV2lyZWxlc3MgVHJhbnNw
b3J0IFBlcmZvcm1hbmNlIGJ5IFRhbWluZyBBY2tub3dsZWRnbWVudHMiLCBBQ00gU0lHQ09NTSwg
MjAyMC4gKCBodHRwOi8vd3d3LnRodWNzbmV0Lm9yZy91cGxvYWRzLzIvNS8yLzgvMjUyODk3OTUv
dG9uZ19zaWdjb21tMjAucGRmICkNCg0KDQoNCkJlc3QgUmVnYXJkcywNCg0KSmlhbw0KDQoNCg0K
LS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206IFFVSUMgW21haWx0bzpxdWljLWJvdW5j
ZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBNYXJ0aW4gVGhvbXNvbg0KU2VudDogTW9uZGF5LCBK
dWx5IDYsIDIwMjAgODo0MSBBTQ0KVG86IHF1aWNAaWV0Zi5vcmcNClN1YmplY3Q6IFJlOiBIb3Bl
IGEgZGlzY3Vzc2lvbiBmb3IgZHJhZnQtbGktcXVpYy1vcHRpbWl6aW5nLWFjay1pbi13bGFuLTAw
DQoNCg0KDQpDYW4geW91IHNwZWFrIGEgbGl0dGxlIGFib3V0IHRoZSByZWxhdGlvbnNoaXAgd2l0
aCBkcmFmdC1peWVuZ2FyLXF1aWMtZGVsYXllZC1hY2sgPw0KDQoNCg0KT24gU2F0LCBKdWwgNCwg
MjAyMCwgYXQgMTY6MDUsIEthbmdqaWFvIHdyb3RlOg0KDQo+DQoNCj4gRGVhciBRVUlDIFdHIG1l
bWJlcnMsDQoNCj4NCg0KPg0KDQo+IFdlIHVwbG9hZGVkIGEgZHJhZnQgZGVzY3JpYmluZyBhIG1l
Y2hhbmlzbSBmb3IgQUNLIG9wdGltaXphdGlvbiB0bw0KDQo+IFFVSUMgZ3JvdXAuIFRoZSBsaW5r
IGlzDQoNCj4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtbGktcXVpYy1v
cHRpbWl6aW5nLWFjay1pbi13bGFuLy4uDQoNCj4gVGhpcyBzb2x1dGlvbiBjb21lcyBmcm9tIG91
ciBwcmFjdGljZSBhbmQgdGhlIHJlc3VsdHMgc2hvdyBpdCBpcyBhDQoNCj4gZ29vZCByZXBsYWNl
bWVudCBvZiB0aGUgdHJhZGl0aW9uYWwgQUNLIG1lY2hhbmlzbSB0byBjb21wZW5zYXRlIGZvcg0K
DQo+IHNjZW5hcmlvcyB3aGVyZSB0aGUgYWNrbm93bGVkZ2VtZW50IG92ZXJoZWFkIGlzIG5vbi1u
ZWdsaWdpYmxlIChpLmUuLA0KDQo+IHdpcmVsZXNzIHNjZW5hcmlvcykuDQoNCj4NCg0KPg0KDQo+
IFRoZSBrZXkgcG9pbnRzIGZvciB0aGlzIHNvbHV0aW9uIGNhbiBiZToNCg0KPg0KDQo+DQoNCj4g
MS4gV2UgY29uY2x1ZGUgdGhlIGZvcm11bGEgb2YgdGhlIG1pbmltdW0gQUNLIGludGVuc2l0eSBy
ZXF1aXJlZCBmb3INCg0KPiBRVUlDIHRyYW5zcG9ydC4NCg0KPg0KDQo+DQoNCj4gMi4gSW4gb3Jk
ZXIgdG8gYWxsZXZpYXRlIHRoZSBlcnJvciBpbiBSVFQgZXN0aW1hdGlvbiwgd2UgdXNlIHByb3Rv
Y29sDQoNCj4gZXh0ZW5zaW9ucyBhbmQgYSBvbmUtd2F5IGRlbGF5IGZhY3Rvci4gV2UgdGhpbmsg
dGhpcyByb3VuZC10cmlwIHRpbWluZw0KDQo+IG1ldGhvZCBjYW4gYWxzbyBiZSBhcHBsaWNhYmxl
IGZvciB0aGUgYWNrIHRoaW5uaW5nIG1lY2hhbmlzbXMgKHN1Y2ggYXMNCg0KPiDigJ1DaGFuZ2lu
ZyB0aGUgRGVmYXVsdCBRVUlDIEFDSyBQb2xpY3nigJ0gIzM1MjkpIHRoYXQgaGF2ZSBiZWVuIGRp
c2N1c3NlZA0KDQo+IGluIFFVSUMgZ3JvdXAuLg0KDQo+DQoNCj4NCg0KPiAzLiBGb3IgaW1wbGVt
ZW50YXRpb24gYW5kIGludGVyb3BlcmFiaWxpdHksIHdlIGRlZmluZSBhIG5ldw0KDQo+IEFDSy1J
TlRFTlNJVFkgRnJhbWUgaW4gd2hpY2ggQUNLIEludGVuc2l0eSBpcyBzZXQuIEFDSyBJbnRlbnNp
dHkgaXMgYQ0KDQo+IHZhcmlhYmxlLWxlbmd0aCBpbnRlZ2VyIGluZGljYXRpbmcgdGhlIHVwZGF0
ZWQgaW50ZW5zaXR5IG9mIFFVSUMgQUNLDQoNCj4gRnJhbWUgY2FsY3VsYXRlZCBieSBvdXIgZm9y
bXVsYS4NCg0KPg0KDQo+DQoNCj4gV2UgbG9vayBmb3J3YXJkIHRvIHlvdXIgdmFsdWFibGUgY29t
bWVudHMgYW5kIHN1Z2dlc3Rpb25zLiBUaGFua3MuDQoNCj4NCg0KPg0KDQo+IFNpbmNlcmVseSwN
Cg0KPg0KDQo+IEppYW8NCg0KPg0KDQoNCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
5a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQOWui+S9kyI7DQoJ
cGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0K
cC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0K
CW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCgl0ZXh0LWFsaWduOmp1c3RpZnk7DQoJdGV4dC1qdXN0
aWZ5OmludGVyLWlkZW9ncmFwaDsNCglmb250LXNpemU6MTAuNXB0Ow0KCWZvbnQtZmFtaWx5OiJD
YWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0
eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVy
bGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxl
LXByaW9yaXR5Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGlu
ZTt9DQpwLk1zb1BsYWluVGV4dCwgbGkuTXNvUGxhaW5UZXh0LCBkaXYuTXNvUGxhaW5UZXh0DQoJ
e21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoi57qv5paH5pysIENoYXIi
Ow0KCW1hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMC41
cHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5DaGFyDQoJe21z
by1zdHlsZS1uYW1lOiLnuq/mlofmnKwgQ2hhciI7DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0K
CW1zby1zdHlsZS1saW5rOue6r+aWh+acrDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1z
ZXJpZjt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlwZTpleHBvcnQtb25seTsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQovKiBQYWdlIERlZmluaXRpb25zICov
DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo2MTIuMHB0IDc5Mi4wcHQ7DQoJbWFyZ2luOjcy
LjBwdCA5MC4wcHQgNzIuMHB0IDkwLjBwdDt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29y
ZFNlY3Rpb24xO30NCi8qIExpc3QgRGVmaW5pdGlvbnMgKi8NCkBsaXN0IGwwDQoJe21zby1saXN0
LWlkOjEzNzk3NDEwMzQ7DQoJbXNvLWxpc3QtdHlwZTpoeWJyaWQ7DQoJbXNvLWxpc3QtdGVtcGxh
dGUtaWRzOi0xNjczNzcxNjk0IC0xNjYyNzYyNjQ4IDY3Njk4NzEzIDY3Njk4NzE1IDY3Njk4NzAz
IDY3Njk4NzEzIDY3Njk4NzE1IDY3Njk4NzAzIDY3Njk4NzEzIDY3Njk4NzE1O30NCkBsaXN0IGww
OmxldmVsMQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDphbHBoYS1sb3dlcjsNCgltc28tbGV2
ZWwtdGV4dDoiJTFcKSI7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51
bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCW1hcmdpbi1sZWZ0OjI4LjVwdDsNCgl0ZXh0LWluZGVudDot
MTguMHB0O30NCkBsaXN0IGwwOmxldmVsMg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDphbHBo
YS1sb3dlcjsNCgltc28tbGV2ZWwtdGV4dDoiJTJcKSI7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5v
bmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCW1hcmdpbi1sZWZ0OjUyLjVw
dDsNCgl0ZXh0LWluZGVudDotMjEuMHB0O30NCkBsaXN0IGwwOmxldmVsMw0KCXttc28tbGV2ZWwt
bnVtYmVyLWZvcm1hdDpyb21hbi1sb3dlcjsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCglt
c28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOnJpZ2h0Ow0KCW1hcmdpbi1sZWZ0OjczLjVwdDsNCgl0
ZXh0LWluZGVudDotMjEuMHB0O30NCkBsaXN0IGwwOmxldmVsNA0KCXttc28tbGV2ZWwtdGFiLXN0
b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJbWFyZ2luLWxlZnQ6
OTQuNXB0Ow0KCXRleHQtaW5kZW50Oi0yMS4wcHQ7fQ0KQGxpc3QgbDA6bGV2ZWw1DQoJe21zby1s
ZXZlbC1udW1iZXItZm9ybWF0OmFscGhhLWxvd2VyOw0KCW1zby1sZXZlbC10ZXh0OiIlNVwpIjsN
Cgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxl
ZnQ7DQoJbWFyZ2luLWxlZnQ6MTE1LjVwdDsNCgl0ZXh0LWluZGVudDotMjEuMHB0O30NCkBsaXN0
IGwwOmxldmVsNg0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpyb21hbi1sb3dlcjsNCgltc28t
bGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOnJpZ2h0Ow0K
CW1hcmdpbi1sZWZ0OjEzNi41cHQ7DQoJdGV4dC1pbmRlbnQ6LTIxLjBwdDt9DQpAbGlzdCBsMDps
ZXZlbDcNCgl7bXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3Np
dGlvbjpsZWZ0Ow0KCW1hcmdpbi1sZWZ0OjE1Ny41cHQ7DQoJdGV4dC1pbmRlbnQ6LTIxLjBwdDt9
DQpAbGlzdCBsMDpsZXZlbDgNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YWxwaGEtbG93ZXI7
DQoJbXNvLWxldmVsLXRleHQ6IiU4XCkiOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1z
by1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgltYXJnaW4tbGVmdDoxNzguNXB0Ow0KCXRl
eHQtaW5kZW50Oi0yMS4wcHQ7fQ0KQGxpc3QgbDA6bGV2ZWw5DQoJe21zby1sZXZlbC1udW1iZXIt
Zm9ybWF0OnJvbWFuLWxvd2VyOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZl
bC1udW1iZXItcG9zaXRpb246cmlnaHQ7DQoJbWFyZ2luLWxlZnQ6MTk5LjVwdDsNCgl0ZXh0LWlu
ZGVudDotMjEuMHB0O30NCm9sDQoJe21hcmdpbi1ib3R0b206MGNtO30NCnVsDQoJe21hcmdpbi1i
b3R0b206MGNtO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFw
ZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZd
LS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+
DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3ht
bD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IlpILUNOIiBsaW5rPSIjMDU2M0Mx
IiB2bGluaz0iIzk1NEY3MiIgc3R5bGU9InRleHQtanVzdGlmeS10cmltOnB1bmN0dWF0aW9uIj4N
CjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3Bh
biBsYW5nPSJFTi1VUyI+RGVhciBNYXJ0aW4sPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5IZXJl
IGFyZSB0aGUgdHdvIGRyYWZ0czo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+ZHJhZnQtbGktcXVpYy1vcHRpbWl6aW5nLWFj
ay1pbi13bGFuLTAwOg0KPGEgaHJlZj0iaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0
LWxpLXF1aWMtb3B0aW1pemluZy1hY2staW4td2xhbi0wMCI+aHR0cHM6Ly90b29scy5pZXRmLm9y
Zy9odG1sL2RyYWZ0LWxpLXF1aWMtb3B0aW1pemluZy1hY2staW4td2xhbi0wMDwvYT4gJm5ic3A7
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFu
Zz0iRU4tVVMiPmRyYWZ0LWl5ZW5nYXItcXVpYy1kZWxheWVkLWFjay0wMDogPGEgaHJlZj0iaHR0
cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWl5ZW5nYXItcXVpYy1kZWxheWVkLWFjay0w
MCI+DQpodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaXllbmdhci1xdWljLWRlbGF5
ZWQtYWNrLTAwPC9hPiA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPkkgaGF2ZSBvdXRsaW5lZCBz
b21lIGRpc3RpbmN0aW9uIGFuZCBjb25uZWN0aW9uIGJldHdlZW4gdGhlc2UgdHdvIGRyYWZ0czo8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5n
PSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjI4LjVwdDt0ZXh0LWluZGVudDotMTguMHB0O21zby1s
aXN0OmwwIGxldmVsMSBsZm8xIj4NCjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIGxhbmc9IkVO
LVVTIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3JlIj5hKTxzcGFuIHN0eWxlPSJmb250Ojcu
MHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4gbGFuZz0i
RU4tVVMiPkJvdGggZHJhZnQtbGktcXVpYy1vcHRpbWl6aW5nLWFjay1pbi13bGFuLTAwIGFuZCBk
cmFmdC1peWVuZ2FyLXF1aWMtZGVsYXllZC1hY2stMDAgcHJvcG9zZSBhIHNvbHV0aW9uIHRvIHJl
ZHVjZSB0aGUgQUNLIGZyZXF1ZW5jeSBmb3IgUVVJQy4gZHJhZnQtaXllbmdhci1xdWljLWRlbGF5
ZWQtYWNrLTAwIG1ha2VzIHRoZSB0d28gcGFyYW1ldGVycyBpbiBkZWxheWVkDQogQUNLLCBpLmUu
LCAmcXVvdDtQYWNrZXQgVG9sZXJhbmNlJnF1b3Q7IGFuZCAmcXVvdDtNYXggQWNrIERlbGF5JnF1
b3Q7LCBiZSB0dW5hYmxlIGJ5IHRoZSBzZW5kZXIuIFRoZXNlIHR3byB0dW5hYmxlIHBhcmFtZXRl
cnMgZG8gbm90IGluY2x1ZGUgUlRUIGFzIGEgZmFjdG9yLiBTYXJhIExhbmRzdHJvbSBldCBhbC4g
WzFdIGhhcyBkZW1vbnN0cmF0ZWQgdGhhdCwgaW4gdGhlb3J5LCB0aGUgZW5kcG9pbnQgc2hvdWxk
IGFja25vd2xlZGdlIGRhdGEgYXQgbGVhc3QgdHdpY2UgcGVyIHNlbmQNCiB3aW5kb3cgKFJUVCkg
dG8gZW5zdXJlIHV0aWxpemF0aW9uLiBJbiB0aGlzIGNhc2UsIHJlZHVjaW5nIEFDSyBmcmVxdWVu
Y3kgd2l0aG91dCBjb25zaWRlcmluZyB0aGUgUlRUIGFzIGEgZmFjdG9yIG9mIE1heCBBY2sgRGVs
YXksIG1pZ2h0IGNhdXNlIHBlcmZvcm1hbmNlIGlzc3Vlcy4gT24gdGhlIG90aGVyIGhhbmQsIHRo
ZSBwdXJwb3NlIGluIGRyYWZ0LWxpLXF1aWMtb3B0aW1pemluZy1hY2staW4td2xhbi0wMCBpcyB0
byBtaW5pbWl6ZSB0aGUNCiBBQ0sgZnJlcXVlbmN5IHJlcXVpcmVkIGJ5IHRoZSB0cmFuc3BvcnQs
IHRodXMgdGhlIEFDSyBmcmVxdWVuY3kgaXMgY29tcHV0ZWQgYXMgPGI+DQpNSU48L2I+e2J3Lyhw
YWNrZXRfdG9sZXJhbmNlICptYXhfcGFja2V0X3NpemUpLCBiZXRhL1JUVG1pbn0gKGJldGEgaW5k
aWNhdGVzIHRoZSBudW1iZXIgb2YgQUNLcyBwZXIgUlRUKS4gV2hpbGUgZHJhZnQtaXllbmdhci1x
dWljLWRlbGF5ZWQtYWNrLTAwIGFkb3B0cyB0aGUgZXh0ZW5kZWQgZGVsYXllZCBBQ0sgYXMgc3Bl
Y2lmaWVkIGluIHRoZSBsZWdhY3kgVENQLCB3aG9zZSBBQ0sgZnJlcXVlbmN5IGlzIGNvbXB1dGVk
IGFzDQo8Yj5NQVg8L2I+e2J3LyggcGFja2V0X3RvbGVyYW5jZSAqbWF4X3BhY2tldF9zaXplKSwg
MS8gbWF4X2Fja19kZWxheX0uIEEgcGFwZXIgWzJdICh0byBiZSBhcHBlYXJlZCBpbiBTSUdDT01N
MjAyMCkgaGFzIGRlbW9uc3RyYXRlZCB0aGF0IHVzaW5nIGENCjxiPk1JTjwvYj4gaW5zdGVhZCBv
ZiBhIDxiPk1BWDwvYj4gY2FuIGFsc28gYWNoaWV2ZSBlcXVhbGx5IGdvb2QgcGVyZm9ybWFuY2Uu
IDxvOnA+DQo8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCIgc3R5bGU9
Im1hcmdpbi1sZWZ0OjEwLjVwdDttc28tcGFyYS1tYXJnaW4tbGVmdDoxLjBnZCI+PHNwYW4gbGFu
Zz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiIHN0eWxlPSJtYXJnaW4tbGVmdDoyOC41cHQ7dGV4dC1pbmRlbnQ6LTE4LjBwdDttc28t
bGlzdDpsMCBsZXZlbDEgbGZvMSI+DQo8IVtpZiAhc3VwcG9ydExpc3RzXT48c3BhbiBsYW5nPSJF
Ti1VUyI+PHNwYW4gc3R5bGU9Im1zby1saXN0Oklnbm9yZSI+Yik8c3BhbiBzdHlsZT0iZm9udDo3
LjBwdCAmcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOw0KPC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFbZW5kaWZdPjxzcGFuIGxhbmc9
IkVOLVVTIj5kcmFmdC1peWVuZ2FyLXF1aWMtZGVsYXllZC1hY2stMDAgcHJvdmlkZXMgYSB3YXkg
Zm9yIHRoZSBzZW5kZXIgdG8gY3VzdG9taXplIHRoZSBBQ0sgZnJlcXVlbmN5LiBUaGlzIG1lYW5z
IHRoZSBBQ0tzIG1pZ2h0IGJlIGV4Y2Vzc2l2ZWx5IGRlbGF5ZWQgd2hlbiB0aGUgTWF4IEFjayBE
ZWxheSBpcyBsYXJnZS4gV2hlbiBzZW5kaW5nIGZld2VyIEFDSyBmcmFtZXMsDQogbWFueSBkYXRh
IHBhY2tldHMgbWlnaHQgYmUgcmVjZWl2ZWQgZHVyaW5nIHRoZSBBQ0sgaW50ZXJ2YWwsIGdlbmVy
YXRpbmcgb25seSBvbmUgUlRUIHNhbXBsZSBhbW9uZyBtdWx0aXBsZSBwYWNrZXRzIGlzIGxpa2Vs
eSB0byByZXN1bHQgaW4gYmlhc2VzLiBGb3IgZXhhbXBsZSwgYSBsYXJnZXIgbWluaW11bSBSVFQg
ZXN0aW1hdGUuIEluIGRyYWZ0LWxpLXF1aWMtb3B0aW1pemluZy1hY2staW4td2xhbi0wMCwgd2Ug
cHJvcG9zZSBhIG9uZS13YXktZGVsYXktYmFzZWQNCiBtZXRob2QgdG8gY29tcHV0ZSB0aGUgbWlu
aW11bSBSVFQgbW9yZSBhY2N1cmF0ZWx5LiBBcGFydCBmcm9tIHRoZSBBQ0sgc2NoZW1lLCB0aGlz
IGlzIGFub3RoZXIgcG9pbnQgdGhhdCB3ZSB3b3VsZCBsaWtlIHRvIGRpc2N1c3MgYW5kIGdldCBm
ZWVkYmFjayBmcm9tIFFVSUMgV0cuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjEwLjVwdDttc28tcGFyYS1tYXJnaW4tbGVm
dDoxLjBnZCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29QbGFpblRleHQiIHN0eWxlPSJtYXJnaW4tbGVmdDoyOC41cHQ7dGV4dC1p
bmRlbnQ6LTE4LjBwdDttc28tbGlzdDpsMCBsZXZlbDEgbGZvMSI+DQo8IVtpZiAhc3VwcG9ydExp
c3RzXT48c3BhbiBsYW5nPSJFTi1VUyI+PHNwYW4gc3R5bGU9Im1zby1saXN0Oklnbm9yZSI+Yyk8
c3BhbiBzdHlsZT0iZm9udDo3LjBwdCAmcXVvdDtUaW1lcyBOZXcgUm9tYW4mcXVvdDsiPiZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOw0KPC9zcGFuPjwvc3Bhbj48L3NwYW4+PCFb
ZW5kaWZdPjxzcGFuIGxhbmc9IkVOLVVTIj5XaXRoIHNvbWUgbWlub3IgZXh0ZW5zaW9ucyBzdWNo
IGFzIGFkZGluZyBvbmUgbW9yZSBmaWVsZCBvZiBBQ0stSU5URU5TSVRZLCB0aGUgcHJvcG9zZWQg
QUNLIHNjaGVtZSBpbiBkcmFmdC1saS1xdWljLW9wdGltaXppbmctYWNrLWluLXdsYW4tMDAgbWF5
IGJlIGFibGUgdG8gcmV1c2UgdGhlIEFDSy1GRVFVRU5DWSBmcmFtZSBzcGVjaWZpZWQgaW4gZHJh
ZnQtaXllbmdhci1xdWljLWRlbGF5ZWQtYWNrLTAwDQogdG8gc3luYyB0aGUgQUNLIGludGVuc2l0
eSBiZXR3ZWVuIHNlbmRlciBhbmQgcmVjZWl2ZXIuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5T
b21lIHJlZmVyZW5jZSBtZW50aW9uZWQgYWJvdmU6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPlsxXSBTYXJhIExhbmRzdHJv
bSBhbmQgTGFycy1Ba2UgTGFyem9uLiAyMDA3LiBSZWR1Y2luZyB0aGUgVENQIGFja25vd2xlZGdt
ZW50IGZyZXF1ZW5jeS4gQUNNIFNJR0NPTU0gQ0NSIDM3LCAzICgyMDA3KSwgNTwvc3Bhbj48c3Bh
biBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7
Ij7igJM8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPjE2LjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5bMl0gVG9uZyBMaSwg
S2FpIFpoZW5nLCBLZSBYdSwgUmFodWwgQXJ2aW5kIEphZGhhdiwgVGFvIFhpb25nLCBLZWl0aCBX
aW5zdGVpbiwgS3VuIFRhbi4gJnF1b3Q7VEFDSzogSW1wcm92aW5nIFdpcmVsZXNzIFRyYW5zcG9y
dCBQZXJmb3JtYW5jZSBieSBUYW1pbmcgQWNrbm93bGVkZ21lbnRzJnF1b3Q7LCBBQ00gU0lHQ09N
TSwgMjAyMC4gKA0KPGEgaHJlZj0iaHR0cDovL3d3dy50aHVjc25ldC5vcmcvdXBsb2Fkcy8yLzUv
Mi84LzI1Mjg5Nzk1L3Rvbmdfc2lnY29tbTIwLnBkZiI+aHR0cDovL3d3dy50aHVjc25ldC5vcmcv
dXBsb2Fkcy8yLzUvMi84LzI1Mjg5Nzk1L3Rvbmdfc2lnY29tbTIwLnBkZjwvYT4gKTxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVT
Ij48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48
c3BhbiBsYW5nPSJFTi1VUyI+QmVzdCBSZWdhcmRzLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5KaWFvPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFu
IGxhbmc9IkVOLVVTIj4tLS0tLU9yaWdpbmFsIE1lc3NhZ2UtLS0tLTxicj4NCkZyb206IFFVSUMg
W21haWx0bzpxdWljLWJvdW5jZXNAaWV0Zi5vcmddIE9uIEJlaGFsZiBPZiBNYXJ0aW4gVGhvbXNv
bjxicj4NClNlbnQ6IE1vbmRheSwgSnVseSA2LCAyMDIwIDg6NDEgQU08YnI+DQpUbzogcXVpY0Bp
ZXRmLm9yZzxicj4NClN1YmplY3Q6IFJlOiBIb3BlIGEgZGlzY3Vzc2lvbiBmb3IgZHJhZnQtbGkt
cXVpYy1vcHRpbWl6aW5nLWFjay1pbi13bGFuLTAwPC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Q2FuIHlvdSBzcGVh
ayBhIGxpdHRsZSBhYm91dCB0aGUgcmVsYXRpb25zaGlwIHdpdGggZHJhZnQtaXllbmdhci1xdWlj
LWRlbGF5ZWQtYWNrID88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5U
ZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPk9uIFNhdCwgSnVsIDQsIDIw
MjAsIGF0IDE2OjA1LCBLYW5namlhbyB3cm90ZTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jmd0OyZuYnNwOyA8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1V
UyI+Jmd0OyBEZWFyIFFVSUMgV0cgbWVtYmVycyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jmd0OyA8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jmd0
OyA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBs
YW5nPSJFTi1VUyI+Jmd0OyBXZSB1cGxvYWRlZCBhIGRyYWZ0IGRlc2NyaWJpbmcgYSBtZWNoYW5p
c20gZm9yIEFDSyBvcHRpbWl6YXRpb24gdG8NCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mZ3Q7IFFVSUMgZ3JvdXAuIFRo
ZSBsaW5rIGlzIDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQi
PjxzcGFuIGxhbmc9IkVOLVVTIj4mZ3Q7IDxhIGhyZWY9Imh0dHBzOi8vZGF0YXRyYWNrZXIuaWV0
Zi5vcmcvZG9jL2RyYWZ0LWxpLXF1aWMtb3B0aW1pemluZy1hY2staW4td2xhbi8iPg0KPHNwYW4g
c3R5bGU9ImNvbG9yOndpbmRvd3RleHQ7dGV4dC1kZWNvcmF0aW9uOm5vbmUiPmh0dHBzOi8vZGF0
YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWxpLXF1aWMtb3B0aW1pemluZy1hY2staW4td2xh
bi88L3NwYW4+PC9hPi4uPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsgVGhpcyBzb2x1dGlvbiBjb21lcyBmcm9tIG91
ciBwcmFjdGljZSBhbmQgdGhlIHJlc3VsdHMgc2hvdyBpdCBpcyBhDQo8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jmd0OyBn
b29kIHJlcGxhY2VtZW50IG9mIHRoZSB0cmFkaXRpb25hbCBBQ0sgbWVjaGFuaXNtIHRvIGNvbXBl
bnNhdGUgZm9yDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jmd0OyBzY2VuYXJpb3Mgd2hlcmUgdGhlIGFja25vd2xlZGdl
bWVudCBvdmVyaGVhZCBpcyBub24tbmVnbGlnaWJsZSAoaS5lLiwNCjxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mZ3Q7IHdp
cmVsZXNzIHNjZW5hcmlvcykuPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsgPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsgPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMi
PiZndDsgVGhlIGtleSBwb2ludHMgZm9yIHRoaXMgc29sdXRpb24gY2FuIGJlOjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4m
Z3Q7IDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFu
IGxhbmc9IkVOLVVTIj4mZ3Q7IDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mZ3Q7IDEuIFdlIGNvbmNsdWRlIHRoZSBmb3Jt
dWxhIG9mIHRoZSBtaW5pbXVtIEFDSyBpbnRlbnNpdHkgcmVxdWlyZWQgZm9yDQo8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+
Jmd0OyBRVUlDIHRyYW5zcG9ydC48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jmd0OyA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jmd0OyA8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1V
UyI+Jmd0OyAyLiBJbiBvcmRlciB0byBhbGxldmlhdGUgdGhlIGVycm9yIGluIFJUVCBlc3RpbWF0
aW9uLCB3ZSB1c2UgcHJvdG9jb2wNCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mZ3Q7IGV4dGVuc2lvbnMgYW5kIGEgb25l
LXdheSBkZWxheSBmYWN0b3IuIFdlIHRoaW5rIHRoaXMgcm91bmQtdHJpcCB0aW1pbmcNCjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVO
LVVTIj4mZ3Q7IG1ldGhvZCBjYW4gYWxzbyBiZSBhcHBsaWNhYmxlIGZvciB0aGUgYWNrIHRoaW5u
aW5nIG1lY2hhbmlzbXMgKHN1Y2ggYXMNCjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mZ3Q7IDwvc3Bhbj48c3BhbiBsYW5n
PSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0NvdXJpZXIgTmV3JnF1b3Q7Ij7igJ08
L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPkNoYW5naW5nIHRoZSBEZWZhdWx0IFFVSUMgQUNLIFBv
bGljeTwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImZvbnQtZmFtaWx5OiZxdW90O0Nv
dXJpZXIgTmV3JnF1b3Q7Ij7igJ08L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiPiAjMzUyOSkNCiB0
aGF0IGhhdmUgYmVlbiBkaXNjdXNzZWQgPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsgaW4gUVVJQyBncm91cC4uPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0i
RU4tVVMiPiZndDsgPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4
dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsgPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsgMy4gRm9yIGltcGxlbWVu
dGF0aW9uIGFuZCBpbnRlcm9wZXJhYmlsaXR5LCB3ZSBkZWZpbmUgYSBuZXcNCjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4m
Z3Q7IEFDSy1JTlRFTlNJVFkgRnJhbWUgaW4gd2hpY2ggQUNLIEludGVuc2l0eSBpcyBzZXQuIEFD
SyBJbnRlbnNpdHkgaXMgYQ0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1Bs
YWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsgdmFyaWFibGUtbGVuZ3RoIGludGVnZXIg
aW5kaWNhdGluZyB0aGUgdXBkYXRlZCBpbnRlbnNpdHkgb2YgUVVJQyBBQ0sNCjxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4m
Z3Q7IEZyYW1lIGNhbGN1bGF0ZWQgYnkgb3VyIGZvcm11bGEuPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsgPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4t
VVMiPiZndDsgPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsgV2UgbG9vayBmb3J3YXJkIHRvIHlvdXIgdmFsdWFibGUg
Y29tbWVudHMgYW5kIHN1Z2dlc3Rpb25zLiBUaGFua3MuPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsgPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMi
PiZndDsgPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNw
YW4gbGFuZz0iRU4tVVMiPiZndDsgU2luY2VyZWx5LDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mZ3Q7IDxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4m
Z3Q7IEppYW88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48
c3BhbiBsYW5nPSJFTi1VUyI+Jmd0OzxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwv
c3Bhbj48L3A+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_719A2C1D4AC73847B6E1BF21DF1545EAE5C7EDFDdggemm534mbschi_--


From nobody Mon Jul  6 14:08:01 2020
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 EA3FF3A0AD9 for <quic@ietfa.amsl.com>; Mon,  6 Jul 2020 14:07:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.889
X-Spam-Level: 
X-Spam-Status: No, score=-1.889 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-0.001, 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 JjsCMWSfriuQ for <quic@ietfa.amsl.com>; Mon,  6 Jul 2020 14:07:57 -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 EF9CB3A0AD8 for <quic@ietf.org>; Mon,  6 Jul 2020 14:07:56 -0700 (PDT)
Received: from xse371.mail2web.com ([66.113.197.117] helo=xse.mail2web.com) by mx36.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1jsYKu-00074b-86 for quic@ietf.org; Mon, 06 Jul 2020 23:07:51 +0200
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 4B0ynH2rD8z6FB2 for <quic@ietf.org>; Mon,  6 Jul 2020 14:07:15 -0700 (PDT)
Received: from [10.5.2.15] (helo=xmail05.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 1jsYKZ-0008EO-8z for quic@ietf.org; Mon, 06 Jul 2020 14:07:15 -0700
Received: (qmail 22268 invoked from network); 6 Jul 2020 21:07:15 -0000
Received: from unknown (HELO [192.168.1.107]) (Authenticated-user:_huitema@huitema.net@[172.58.46.187]) (envelope-sender <huitema@huitema.net>) by xmail05.myhosting.com (qmail-ldap-1.03) with ESMTPA for <quic@ietf.org>; 6 Jul 2020 21:07:14 -0000
To: Kangjiao <kangjiao@huawei.com>, Martin Thomson <mt@lowentropy.net>
Cc: "quic@ietf.org" <quic@ietf.org>
References: <719A2C1D4AC73847B6E1BF21DF1545EAE5C7CE04@dggemm534-mbs.china.huawei.com> <cd99a66b-6478-4b15-b6fc-0c512e92e118@www.fastmail.com> <719A2C1D4AC73847B6E1BF21DF1545EAE5C7EDFD@dggemm534-mbs.china.huawei.com>
From: Christian Huitema <huitema@huitema.net>
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mDMEXtavGxYJKwYBBAHaRw8BAQdA1ou9A5MHTP9N3jfsWzlDZ+jPnQkusmc7sfLmWVz1Rmu0 J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PoiWBBMWCAA+FiEEw3G4 Nwi4QEpAAXUUELAmqKBYtJQFAl7WrxsCGwMFCQlmAYAFCwkIBwIGFQoJCAsCBBYCAwECHgEC F4AACgkQELAmqKBYtJQbMwD/ebj/qnSbthC/5kD5DxZ/Ip0CGJw5QBz/+fJp3R8iAlsBAMjK r2tmyWyJz0CUkVG24WaR5EAJDvgwDv8h22U6QVkAuDgEXtavGxIKKwYBBAGXVQEFAQEHQJoM 6MUAIqpoqdCIiACiEynZf7nlJg2Eu0pXIhbUGONdAwEIB4h+BBgWCAAmFiEEw3G4Nwi4QEpA AXUUELAmqKBYtJQFAl7WrxsCGwwFCQlmAYAACgkQELAmqKBYtJRm2wD7BzeK5gEXSmBcBf0j BYdSaJcXNzx4yPLbP4GnUMAyl2cBAJzcsR4RkwO4dCRqM9CHpVJCwHtbUDJaa55//E0kp+gH
Subject: Re: Hope a discussion for draft-li-quic-optimizing-ack-in-wlan-00
Message-ID: <98c0a7a0-2dfa-a327-33d3-5c337c390fd2@huitema.net>
Date: Mon, 6 Jul 2020 14:07:14 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.9.0
MIME-Version: 1.0
In-Reply-To: <719A2C1D4AC73847B6E1BF21DF1545EAE5C7EDFD@dggemm534-mbs.china.huawei.com>
Content-Type: multipart/alternative; boundary="------------9DAEB3FD897038C12194E73F"
Content-Language: en-US
X-Originating-IP: 66.113.197.117
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/gcnlw0f6LF1GdvkEexklpcFpSF5apSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDcnqpk5VeF3xR4kF6iVwRtbgN zB/4Jkrw1eDLcif59ftlPGAYnoChmvr7MHhb7Z5TU7Tmz6iKnkQL9gqsxD347235Nhqq+/HvroPq 8GSPg+7KJix/R2qbtdH2ZflMjNgfX2XX9bIsGDSYq5OAASmskY6jSvfpO+1kZkomjtjB6X5Q5Q9f RUeIpTIC2ySfqvnqLwoxlgatmaBb0rBiK9xbkDrUqzcKIief90MVLZY9LbIZh9+IQ1oS9LBn3VIP 95Jz7ujRlJ9wSMlhvaudJXZ9EIBG/qaR+8r9SKFMmPJLf850OvZYsmoVQuOIhwKLK6IKBNB4LZ0v UHHKTzJX7b1JhLSQQ4vSj0QEim26t/Moy0UPX5E73H1QfrH/5kkrV/Cr0bm2vWdo8usP65i82q1C dZgGrpL44wdx9eXqjQjbvUopOMQJvQ/Ck3iiU+4DQAj3fuQgzT3K9JUHTNiGwfwAmxx/Wk8McinP JEkgAVrOMpYt4o3CgqJq+7GLH3LDcCCXn4KxIMmLKkg5fu+h86FP7+F98Qs+KGQ0tfoeDSAfzCMv UwPy3x0FYtCNEb10sHyQCLHEvD1OqP6bgZ4L66GcgBg66gs5OuzYxJgw5atIxeNDvjI/CYe5WPy0 +t1RP0azWadFjuzwPVVLsuYPIFYAx5xMPnetLBJMh51NiRRoHICAC6iPKDrKIWN2yNyuqa9KmiK7 x42VjdzChZMe6O/Did+/hGXTmfhE+Dx2/NyzMXo75ntICbS+BvGEZ0Xy7wYWvOnCUbNPgcPcQwzM 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/iEeZvuJjUgi637WI9hS-E82vs3M>
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, 06 Jul 2020 21:08:00 -0000

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

Hello Jiao,

Your draft is motivated by specific data about running high bandwidth
applications over wireless local area network. It would be interesting
to compare behavior of these applications using different
acknowledgement policies, probably using simulations. Do you have
definitions of the application and of the WLAN that we could enter in
simulations?

The draft draft-iyengar-quic-delayed-ack-00 provides a way for senders
to specify both the maximum delay between acknowledgements and the
maximum number of packets between acknowledgement, with receivers
sending acknowledgements when one of the conditions is true. Several
servers set the delay to a fraction of the RTT, and the number of
packets to a corresponding fraction of the number of packets per
congestion window -- RTT/8 is often suggested. How is that different
from setting the "ACK intensity" suggested in
draft-li-quic-optimizing-ack-in-wlan-00?

The draft draft-li-quic-optimizing-ack-in-wlan-00 mentions using one way
delay measurements. Is that a reference to draft-huitema-quic-ts-00 ?

-- Christian Huitema

On 7/6/2020 7:35 AM, Kangjiao wrote:
>
> Dear Martin,
>
> =C2=A0
>
> Here are the two drafts:
>
> draft-li-quic-optimizing-ack-in-wlan-00:
> https://tools.ietf.org/html/draft-li-quic-optimizing-ack-in-wlan-00 =C2=
=A0
>
> draft-iyengar-quic-delayed-ack-00:
> https://tools.ietf.org/html/draft-iyengar-quic-delayed-ack-00
>
> =C2=A0
>
> I have outlined some distinction and connection between these two draft=
s:
>
> =C2=A0
>
> a)=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 Both draft-li-quic-optimizing-ac=
k-in-wlan-00 and
> draft-iyengar-quic-delayed-ack-00 propose a solution to reduce the ACK
> frequency for QUIC. draft-iyengar-quic-delayed-ack-00 makes the two
> parameters in delayed ACK, i.e., "Packet Tolerance" and "Max Ack
> Delay", be tunable by the sender. These two tunable parameters do not
> include RTT as a factor. Sara Landstrom et al. [1] has demonstrated
> that, in theory, the endpoint should acknowledge data at least twice
> per send window (RTT) to ensure utilization. In this case, reducing
> ACK frequency without considering the RTT as a factor of Max Ack
> Delay, might cause performance issues. On the other hand, the purpose
> in draft-li-quic-optimizing-ack-in-wlan-00 is to minimize the ACK
> frequency required by the transport, thus the ACK frequency is
> computed as *MIN*{bw/(packet_tolerance *max_packet_size), beta/RTTmin}
> (beta indicates the number of ACKs per RTT). While
> draft-iyengar-quic-delayed-ack-00 adopts the extended delayed ACK as
> specified in the legacy TCP, whose ACK frequency is computed as
> *MAX*{bw/( packet_tolerance *max_packet_size), 1/ max_ack_delay}. A
> paper [2] (to be appeared in SIGCOMM2020) has demonstrated that using
> a *MIN* instead of a *MAX* can also achieve equally good performance.
>
> =C2=A0
>
> b)=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 draft-iyengar-quic-delayed-ack-0=
0 provides a way for the
> sender to customize the ACK frequency. This means the ACKs might be
> excessively delayed when the Max Ack Delay is large. When sending
> fewer ACK frames, many data packets might be received during the ACK
> interval, generating only one RTT sample among multiple packets is
> likely to result in biases. For example, a larger minimum RTT
> estimate. In draft-li-quic-optimizing-ack-in-wlan-00, we propose a
> one-way-delay-based method to compute the minimum RTT more accurately.
> Apart from the ACK scheme, this is another point that we would like to
> discuss and get feedback from QUIC WG.
>
> =C2=A0
>
> c)=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 With some minor extensions such =
as adding one more field of
> ACK-INTENSITY, the proposed ACK scheme in
> draft-li-quic-optimizing-ack-in-wlan-00 may be able to reuse the
> ACK-FEQUENCY frame specified in draft-iyengar-quic-delayed-ack-00 to
> sync the ACK intensity between sender and receiver.
>
> =C2=A0
>
> Some reference mentioned above:
>
> [1] Sara Landstrom and Lars-Ake Larzon. 2007. Reducing the TCP
> acknowledgment frequency. ACM SIGCOMM CCR 37, 3 (2007), 5=E2=80=9316.
>
> [2] Tong Li, Kai Zheng, Ke Xu, Rahul Arvind Jadhav, Tao Xiong, Keith
> Winstein, Kun Tan. "TACK: Improving Wireless Transport Performance by
> Taming Acknowledgments", ACM SIGCOMM, 2020. (
> http://www.thucsnet.org/uploads/2/5/2/8/25289795/tong_sigcomm20.pdf )
>
> =C2=A0
>
> Best Regards,
>
> Jiao
>
> =C2=A0
>
> -----Original Message-----
> From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of Martin Thomson
> Sent: Monday, July 6, 2020 8:41 AM
> To: quic@ietf.org
> Subject: Re: Hope a discussion for draft-li-quic-optimizing-ack-in-wlan=
-00
>
> =C2=A0
>
> Can you speak a little about the relationship with
> draft-iyengar-quic-delayed-ack ?
>
> =C2=A0
>
> On Sat, Jul 4, 2020, at 16:05, Kangjiao wrote:
>
> >=C2=A0=20
>
> > Dear QUIC WG members,
>
> >=20
>
> >=20
>
> > We uploaded a draft describing a mechanism for ACK optimization to
>
> > QUIC group. The link is
>
> > https://datatracker.ietf.org/doc/draft-li-quic-optimizing-ack-in-wlan=
/..
>
> > This solution comes from our practice and the results show it is a
>
> > good replacement of the traditional ACK mechanism to compensate for
>
> > scenarios where the acknowledgement overhead is non-negligible (i.e.,=

>
> > wireless scenarios).
>
> >=20
>
> >=20
>
> > The key points for this solution can be:
>
> >=20
>
> >=20
>
> > 1. We conclude the formula of the minimum ACK intensity required for
>
> > QUIC transport.
>
> >=20
>
> >=20
>
> > 2. In order to alleviate the error in RTT estimation, we use protocol=

>
> > extensions and a one-way delay factor. We think this round-trip timin=
g
>
> > method can also be applicable for the ack thinning mechanisms (such a=
s
>
> > =E2=80=9DChanging the Default QUIC ACK Policy=E2=80=9D#3529) that hav=
e been discussed
>
> > in QUIC group..
>
> >=20
>
> >=20
>
> > 3. For implementation and interoperability, we define a new
>
> > ACK-INTENSITY Frame in which ACK Intensity is set. ACK Intensity is a=

>
> > variable-length integer indicating the updated intensity of QUIC ACK
>
> > Frame calculated by our formula.
>
> >=20
>
> >=20
>
> > We look forward to your valuable comments and suggestions. Thanks.
>
> >=20
>
> >=20
>
> > Sincerely,
>
> >=20
>
> > Jiao
>
> >=C2=A0
>
> =C2=A0
>

--------------9DAEB3FD897038C12194E73F
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>Hello Jiao,</p>
    <p>Your draft is motivated by specific data about running high
      bandwidth applications over wireless local area network. It would
      be interesting to compare behavior of these applications using
      different acknowledgement policies, probably using simulations. Do
      you have definitions of the application and of the WLAN that we
      could enter in simulations?<br>
    </p>
    <p>The draft <span lang="EN-US">draft-iyengar-quic-delayed-ack-00
        provides a way for senders to specify both the maximum delay
        between acknowledgements and the maximum number of packets
        between acknowledgement, with receivers sending acknowledgements
        when one of the conditions is true. Several servers set the
        delay to a fraction of the RTT, and the number of packets to a
        corresponding fraction of the number of packets per congestion
        window -- RTT/8 is often suggested. How is that different from
        setting the "ACK intensity" suggested in </span><span
        lang="EN-US"><span lang="EN-US">draft-li-quic-optimizing-ack-in-wlan-00?</span></span></p>
    <p><span lang="EN-US"><span lang="EN-US">The draft </span></span><span
        lang="EN-US"><span lang="EN-US"><span lang="EN-US"><span
              lang="EN-US">draft-li-quic-optimizing-ack-in-wlan-00
              mentions using one way delay measurements. Is that a
              reference to draft-huitema-quic-ts-00 ?</span></span></span></span></p>
    <p><span lang="EN-US"><span lang="EN-US"><span lang="EN-US"><span
              lang="EN-US">-- Christian Huitema<br>
            </span></span></span></span></p>
    <div class="moz-cite-prefix">On 7/6/2020 7:35 AM, Kangjiao wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:719A2C1D4AC73847B6E1BF21DF1545EAE5C7EDFD@dggemm534-mbs.china.huawei.com">
      <meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
      <meta name="Generator" content="Microsoft Word 15 (filtered
        medium)">
      <style><!--
/* Font Definitions */
@font-face
	{font-family:宋体;
	panose-1:2 1 6 0 3 1 1 1 1 1;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:"\@宋体";
	panose-1:2 1 6 0 3 1 1 1 1 1;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0cm;
	margin-bottom:.0001pt;
	text-align:justify;
	text-justify:inter-ideograph;
	font-size:10.5pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:#0563C1;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:#954F72;
	text-decoration:underline;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"纯文本 Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.5pt;
	font-family:"Calibri",sans-serif;}
span.Char
	{mso-style-name:"纯文本 Char";
	mso-style-priority:99;
	mso-style-link:纯文本;
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;}
/* Page Definitions */
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 90.0pt 72.0pt 90.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:1379741034;
	mso-list-type:hybrid;
	mso-list-template-ids:-1673771694 -1662762648 67698713 67698715 67698703 67698713 67698715 67698703 67698713 67698715;}
@list l0:level1
	{mso-level-number-format:alpha-lower;
	mso-level-text:"%1\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:28.5pt;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-number-format:alpha-lower;
	mso-level-text:"%2\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:52.5pt;
	text-indent:-21.0pt;}
@list l0:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:73.5pt;
	text-indent:-21.0pt;}
@list l0:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:94.5pt;
	text-indent:-21.0pt;}
@list l0:level5
	{mso-level-number-format:alpha-lower;
	mso-level-text:"%5\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:115.5pt;
	text-indent:-21.0pt;}
@list l0:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:136.5pt;
	text-indent:-21.0pt;}
@list l0:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:157.5pt;
	text-indent:-21.0pt;}
@list l0:level8
	{mso-level-number-format:alpha-lower;
	mso-level-text:"%8\)";
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	margin-left:178.5pt;
	text-indent:-21.0pt;}
@list l0:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	margin-left:199.5pt;
	text-indent:-21.0pt;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoPlainText"><span lang="EN-US">Dear Martin,<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">Here are the two
            drafts:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">draft-li-quic-optimizing-ack-in-wlan-00:
            <a
href="https://tools.ietf.org/html/draft-li-quic-optimizing-ack-in-wlan-00"
              moz-do-not-send="true">https://tools.ietf.org/html/draft-li-quic-optimizing-ack-in-wlan-00</a>
             <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">draft-iyengar-quic-delayed-ack-00:
            <a
              href="https://tools.ietf.org/html/draft-iyengar-quic-delayed-ack-00"
              moz-do-not-send="true">
https://tools.ietf.org/html/draft-iyengar-quic-delayed-ack-00</a> <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">I have outlined some
            distinction and connection between these two drafts:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoPlainText"
          style="margin-left:28.5pt;text-indent:-18.0pt;mso-list:l0
          level1 lfo1">
          <!--[if !supportLists]--><span lang="EN-US"><span
              style="mso-list:Ignore">a)<span style="font:7.0pt
                &quot;Times New Roman&quot;">      
              </span></span></span><!--[endif]--><span lang="EN-US">Both
            draft-li-quic-optimizing-ack-in-wlan-00 and
            draft-iyengar-quic-delayed-ack-00 propose a solution to
            reduce the ACK frequency for QUIC.
            draft-iyengar-quic-delayed-ack-00 makes the two parameters
            in delayed ACK, i.e., "Packet Tolerance" and "Max Ack
            Delay", be tunable by the sender. These two tunable
            parameters do not include RTT as a factor. Sara Landstrom et
            al. [1] has demonstrated that, in theory, the endpoint
            should acknowledge data at least twice per send window (RTT)
            to ensure utilization. In this case, reducing ACK frequency
            without considering the RTT as a factor of Max Ack Delay,
            might cause performance issues. On the other hand, the
            purpose in draft-li-quic-optimizing-ack-in-wlan-00 is to
            minimize the ACK frequency required by the transport, thus
            the ACK frequency is computed as <b>
              MIN</b>{bw/(packet_tolerance *max_packet_size),
            beta/RTTmin} (beta indicates the number of ACKs per RTT).
            While draft-iyengar-quic-delayed-ack-00 adopts the extended
            delayed ACK as specified in the legacy TCP, whose ACK
            frequency is computed as
            <b>MAX</b>{bw/( packet_tolerance *max_packet_size), 1/
            max_ack_delay}. A paper [2] (to be appeared in SIGCOMM2020)
            has demonstrated that using a
            <b>MIN</b> instead of a <b>MAX</b> can also achieve equally
            good performance. <o:p>
            </o:p></span></p>
        <p class="MsoPlainText"
          style="margin-left:10.5pt;mso-para-margin-left:1.0gd"><span
            lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoPlainText"
          style="margin-left:28.5pt;text-indent:-18.0pt;mso-list:l0
          level1 lfo1">
          <!--[if !supportLists]--><span lang="EN-US"><span
              style="mso-list:Ignore">b)<span style="font:7.0pt
                &quot;Times New Roman&quot;">      
              </span></span></span><!--[endif]--><span lang="EN-US">draft-iyengar-quic-delayed-ack-00
            provides a way for the sender to customize the ACK
            frequency. This means the ACKs might be excessively delayed
            when the Max Ack Delay is large. When sending fewer ACK
            frames, many data packets might be received during the ACK
            interval, generating only one RTT sample among multiple
            packets is likely to result in biases. For example, a larger
            minimum RTT estimate. In
            draft-li-quic-optimizing-ack-in-wlan-00, we propose a
            one-way-delay-based method to compute the minimum RTT more
            accurately. Apart from the ACK scheme, this is another point
            that we would like to discuss and get feedback from QUIC WG.<o:p></o:p></span></p>
        <p class="MsoPlainText"
          style="margin-left:10.5pt;mso-para-margin-left:1.0gd"><span
            lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoPlainText"
          style="margin-left:28.5pt;text-indent:-18.0pt;mso-list:l0
          level1 lfo1">
          <!--[if !supportLists]--><span lang="EN-US"><span
              style="mso-list:Ignore">c)<span style="font:7.0pt
                &quot;Times New Roman&quot;">      
              </span></span></span><!--[endif]--><span lang="EN-US">With
            some minor extensions such as adding one more field of
            ACK-INTENSITY, the proposed ACK scheme in
            draft-li-quic-optimizing-ack-in-wlan-00 may be able to reuse
            the ACK-FEQUENCY frame specified in
            draft-iyengar-quic-delayed-ack-00 to sync the ACK intensity
            between sender and receiver.<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">Some reference
            mentioned above:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">[1] Sara Landstrom
            and Lars-Ake Larzon. 2007. Reducing the TCP acknowledgment
            frequency. ACM SIGCOMM CCR 37, 3 (2007), 5</span><span
            style="font-family:&quot;Courier New&quot;" lang="EN-US">–</span><span
            lang="EN-US">16.<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">[2] Tong Li, Kai
            Zheng, Ke Xu, Rahul Arvind Jadhav, Tao Xiong, Keith
            Winstein, Kun Tan. "TACK: Improving Wireless Transport
            Performance by Taming Acknowledgments", ACM SIGCOMM, 2020. (
            <a
href="http://www.thucsnet.org/uploads/2/5/2/8/25289795/tong_sigcomm20.pdf"
              moz-do-not-send="true">http://www.thucsnet.org/uploads/2/5/2/8/25289795/tong_sigcomm20.pdf</a>
            )<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">Best Regards,<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">Jiao<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">-----Original
            Message-----<br>
            From: QUIC [<a class="moz-txt-link-freetext" href="mailto:quic-bounces@ietf.org">mailto:quic-bounces@ietf.org</a>] On Behalf Of
            Martin Thomson<br>
            Sent: Monday, July 6, 2020 8:41 AM<br>
            To: <a class="moz-txt-link-abbreviated" href="mailto:quic@ietf.org">quic@ietf.org</a><br>
            Subject: Re: Hope a discussion for
            draft-li-quic-optimizing-ack-in-wlan-00</span></p>
        <p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">Can you speak a
            little about the relationship with
            draft-iyengar-quic-delayed-ack ?<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">On Sat, Jul 4, 2020,
            at 16:05, Kangjiao wrote:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt;  <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; Dear QUIC WG
            members,<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; We uploaded a
            draft describing a mechanism for ACK optimization to
            <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; QUIC group. The
            link is <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; <a
href="https://datatracker.ietf.org/doc/draft-li-quic-optimizing-ack-in-wlan/"
              moz-do-not-send="true">
              <span style="color:windowtext;text-decoration:none">https://datatracker.ietf.org/doc/draft-li-quic-optimizing-ack-in-wlan/</span></a>..<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; This solution
            comes from our practice and the results show it is a
            <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; good replacement
            of the traditional ACK mechanism to compensate for
            <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; scenarios where
            the acknowledgement overhead is non-negligible (i.e.,
            <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; wireless
            scenarios).<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; The key points
            for this solution can be:<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; 1. We conclude
            the formula of the minimum ACK intensity required for
            <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; QUIC transport.<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; 2. In order to
            alleviate the error in RTT estimation, we use protocol
            <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; extensions and a
            one-way delay factor. We think this round-trip timing
            <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; method can also
            be applicable for the ack thinning mechanisms (such as
            <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; </span><span
            style="font-family:&quot;Courier New&quot;" lang="EN-US">”</span><span
            lang="EN-US">Changing the Default QUIC ACK Policy</span><span
            style="font-family:&quot;Courier New&quot;" lang="EN-US">”</span><span
            lang="EN-US"> #3529) that have been discussed <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; in QUIC group..<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; 3. For
            implementation and interoperability, we define a new
            <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; ACK-INTENSITY
            Frame in which ACK Intensity is set. ACK Intensity is a
            <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; variable-length
            integer indicating the updated intensity of QUIC ACK
            <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; Frame calculated
            by our formula.<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; We look forward
            to your valuable comments and suggestions. Thanks.<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; Sincerely,<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; <o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt; Jiao<o:p></o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US">&gt;<o:p> </o:p></span></p>
        <p class="MsoPlainText"><span lang="EN-US"><o:p> </o:p></span></p>
      </div>
    </blockquote>
  </body>
</html>

--------------9DAEB3FD897038C12194E73F--


From nobody Mon Jul  6 21:45:10 2020
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 146653A07F0; Mon,  6 Jul 2020 21:45:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, 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 5ZO-ikbxlPbU; Mon,  6 Jul 2020 21:45:03 -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 D36EB3A07E6; Mon,  6 Jul 2020 21:45:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=alibaba-inc.com; s=default; t=1594097099; h=Date:From:To:Message-ID:Subject:MIME-Version:Content-Type; bh=aX8jnRJpr/UWzJF/bQY0bK/PIfiCQZGKI/vaSywyjjQ=; b=oGogishNIlZsBXIsF/dxJZ5EIExHNYrbSu959mH8gvAxfhYRp1S7k1J0OxvXZR/pHKQ3dMEuQvV/OxrOEfUkrI0O7MTZArog6UZXpPAMonjSG7NLLVWY45W/j8XD2BXm5dYAwFafwOqLvTokkOWniaAeK22sRuBpzsv3LWMhYpU=
X-Alimail-AntiSpam: AC=PASS; BC=-1|-1; BR=01201311R181e4; CH=green; DM=||false|; DS=||; FP=0|-1|-1|-1|0|-1|-1|-1; HT=e02c03308; MF=anqing.aq@alibaba-inc.com; NM=1; PH=DW; RN=2; SR=0; TI=W4_5922738_v5ForWebDing_0A93269A_1594096642187_o7001c241c; 
Received: from WS-web (anqing.aq@alibaba-inc.com[W4_5922738_v5ForWebDing_0A93269A_1594096642187_o7001c241c]) by e02c03275.eu6 at Tue, 07 Jul 2020 12:44:57 +0800
Date: Tue, 07 Jul 2020 12:44:57 +0800
From: "Qing An" <anqing.aq@alibaba-inc.com>
To: "quic" <quic@ietf.org>
Cc: "quic-chairs" <quic-chairs@ietf.org>
Reply-To: "Qing An" <anqing.aq@alibaba-inc.com>
Message-ID: <b771e8b6-fd24-48be-94a8-25fa9fa49ff4.anqing.aq@alibaba-inc.com>
Subject: =?UTF-8?B?SG9wZSBzb21lIGRpc2N1c3Npb24gZm9yIGRyYWZ0ICJFbmFibGluZyBhcHBsaWNhdGlvbiBw?= =?UTF-8?B?b2xpY3ktYXdhcmVuZXNzIGluIE11bHRpcGF0aCBRVUlDIiAvLyBOZXcgVmVyc2lvbiBOb3Rp?= =?UTF-8?B?ZmljYXRpb24gZm9yIGRyYWZ0LWFuLW11bHRpcGF0aC1xdWljLWFwcGxpY2F0aW9uLXBvbGlj?= =?UTF-8?B?eS0wMC50eHQ=?=
X-Mailer: [Alimail-Mailagent][W4_5922738][v5ForWebDing][Chrome]
MIME-Version: 1.0
x-aliyun-mail-creator: W4_5922738_v5ForWebDing_NTMTW96aWxsYS81LjAgKE1hY2ludG9zaDsgSW50ZWwgTWFjIE9TIFggMTBfMTVfNSkgQXBwbGVXZWJLaXQvNTM3LjM2IChLSFRNTCwgbGlrZSBHZWNrbykgQ2hyb21lLzgzLjAuNDEwMy45NyBTYWZhcmkvNTM3LjM2XQ
Content-Type: multipart/alternative; boundary="----=ALIBOUNDARY_20716_4b9ac940_5f03fdc9_11f45a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/OekESpEPzdl-R3E4YABybfci7QM>
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, 07 Jul 2020 04:45:08 -0000

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

CkhpIFFVSUMgV0cgbWVtYmVycywKCldlIHVwbG9hZGVkIGEgZHJhZnQgZGVzY3JpYmluZyBhbiBh
cHBsaWNhdGlvbiBwb2xpY3ktYXdhcmVuZXNzIG1ldGhvZCBmb3IgTXVsdGlwYXRoIFFVSUMuIGh0
dHBzOi8vZGF0YXRyYWNrZXIuaWV0Zi5vcmcvZG9jL2RyYWZ0LWFuLW11bHRpcGF0aC1xdWljLWFw
cGxpY2F0aW9uLXBvbGljeS8KClRoZSBnb2FsIGlzIHRvIGVuYWJsZSB0YWtpbmcgYXBwbGljYXRp
b25zJyBkZW1hbmRzIGludG8gYWNjb3VudCB3aGVuIG1hbmFnaW5nIHBhdGhzIG9yIHNjaGVkdWxp
bmcgcGFja2V0cyBpbiBNdWx0aXBhdGggUVVJQy4gCgpUaGUgZHJhZnQgZGVzY3JpYmVzOgpQZXIt
Y29ubmVjdGlvbiBQb2xpY3kgaW1wb3NlZCBieSBhcHBsaWNhdGlvbiB0byBpbmRpY2F0ZSB0aGUg
cGFja2V0IHNjaGVkdWxpbmcgY29tcG9uZW50IGFuZCB0aGUgcGF0aCBtYW5hZ2VyIGZvciBwYXRo
IHNlbGVjdGlvbiBhbmQgZGF0YSB0cmFuc21pc3Npb24KUGVyLXN0cmVhbSBJbnRlbnQgaW1wbGVt
ZW50ZWQgdGhyb3VnaCB0aGUgbXVsdGlwbGUgc3RyZWFtcyBpbiBRVUlDIHRvIHV0aWxpemUgcHJp
b3JpdGllcyB0byBpbXBsZW1lbnQgYXBwbGljYXRpb25zIGludGVudAoKTG9vayBmb3J3YXJkIHRv
IHlvdXIgY29tbWVudHMuIAoKVGhhbmtzCkJlc3QgcmVnYXJkcyxRaW5nCgoKCi0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLUEg
bmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1hbi1tdWx0aXBhdGgtcXVpYy1hcHBsaWNhdGlvbi1w
b2xpY3ktMDAudHh0CmhhcyBiZWVuIHN1Y2Nlc3NmdWxseSBzdWJtaXR0ZWQgYnkgUWluZyBBbiBh
bmQgcG9zdGVkIHRvIHRoZQpJRVRGIHJlcG9zaXRvcnkuCgpOYW1lOiAgZHJhZnQtYW4tbXVsdGlw
YXRoLXF1aWMtYXBwbGljYXRpb24tcG9saWN5ClJldmlzaW9uOiAwMApUaXRsZTogIEVuYWJsaW5n
IGFwcGxpY2F0aW9uIHBvbGljeS1hd2FyZW5lc3MgaW4gTXVsdGlwYXRoIFFVSUMKRG9jdW1lbnQg
ZGF0ZTogMjAyMC0wNy0wNgpHcm91cDogIEluZGl2aWR1YWwgU3VibWlzc2lvbgpQYWdlczogIDEw
ClVSTDogICAgICAgICAgICBodHRwczovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJh
ZnQtYW4tbXVsdGlwYXRoLXF1aWMtYXBwbGljYXRpb24tcG9saWN5LTAwLnR4dApTdGF0dXM6ICAg
ICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtYW4tbXVsdGlwYXRo
LXF1aWMtYXBwbGljYXRpb24tcG9saWN5LwpIdG1saXplZDogICAgICAgaHR0cHM6Ly90b29scy5p
ZXRmLm9yZy9odG1sL2RyYWZ0LWFuLW11bHRpcGF0aC1xdWljLWFwcGxpY2F0aW9uLXBvbGljeS0w
MApIdG1saXplZDogICAgICAgaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvaHRtbC9k
cmFmdC1hbi1tdWx0aXBhdGgtcXVpYy1hcHBsaWNhdGlvbi1wb2xpY3kKCgpBYnN0cmFjdDoKICAg
VGhpcyBkb2N1bWVudCBkZXNjcmliZXMgYW4gYXBwbGljYXRpb24gcG9saWN5LWF3YXJlbmVzcyBt
ZXRob2QgZm9yCiAgIE11bHRpcGF0aCBRVUlDLCB0byBlbmFibGUgdGFraW5nIGFwcGxpY2F0aW9u
cycgZGVtYW5kcyBpbnRvIGFjY291bnQKICAgd2hlbiBtYW5hZ2luZyBwYXRocyBvciBzY2hlZHVs
aW5nIHBhY2tldHMgaW4gTXVsdGlwYXRoIFFVSUMuCgoKCgpQbGVhc2Ugbm90ZSB0aGF0IGl0IG1h
eSB0YWtlIGEgY291cGxlIG9mIG1pbnV0ZXMgZnJvbSB0aGUgdGltZSBvZiBzdWJtaXNzaW9uCnVu
dGlsIHRoZSBodG1saXplZCB2ZXJzaW9uIGFuZCBkaWZmIGFyZSBhdmFpbGFibGUgYXQgdG9vbHMu
aWV0Zi5vcmcuCgpUaGUgSUVURiBTZWNyZXRhcmlhdAoK
------=ALIBOUNDARY_20716_4b9ac940_5f03fdc9_11f45a
Content-Type: text/html; charset="UTF-8"
Content-Transfer-Encoding: base64

PGRpdiBjbGFzcz0iX19hbGl5dW5fZW1haWxfYm9keV9ibG9jayI+PGRpdiAgc3R5bGU9ImxpbmUt
aGVpZ2h0OjEuNztmb250LWZhbWlseTpUYWhvbWEsQXJpYWwsU1RIZWl0aSxTaW1TdW47Zm9udC1z
aXplOjE0LjBweDtjb2xvcjojMDAwMDAwOyI+PGRpdiAgc3R5bGU9ImNsZWFyOmJvdGg7Ij48c3Bh
biAgc3R5bGU9ImZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjt0ZXh0LWFsaWduOmp1c3Rp
Znk7Ij48YnIgPjwvc3Bhbj48L2Rpdj48ZGl2ICBzdHlsZT0iY2xlYXI6Ym90aDsiPjxzcGFuICBz
dHlsZT0iZm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmO3RleHQtYWxpZ246anVzdGlmeTsi
PkhpIFFVSUMgV0cgbWVtYmVycyw8L3NwYW4+PGJyID48L2Rpdj48ZGl2ICBzdHlsZT0iY2xlYXI6
Ym90aDsiPjxkaXYgIHN0eWxlPSJtYXJnaW46LjBweDtwYWRkaW5nOi4wcHg7Ym9yZGVyOi4wcHg7
b3V0bGluZTouMHB4O2NsZWFyOmJvdGg7Ij48c3BhbiAgc3R5bGU9Im1hcmdpbjouMHB4O3BhZGRp
bmc6LjBweDtib3JkZXI6LjBweDtvdXRsaW5lOi4wcHg7Y29sb3I6IzAwMDAwMDtmb250LWZhbWls
eTpDYWxpYnJpLHNhbnMtc2VyaWY7Zm9udC1zaXplOjE0LjBweDtmb250LXN0eWxlOm5vcm1hbDtm
b250LXZhcmlhbnQtbGlnYXR1cmVzOm5vcm1hbDtmb250LXZhcmlhbnQtY2Fwczpub3JtYWw7Zm9u
dC13ZWlnaHQ6NDAwO3RleHQtYWxpZ246anVzdGlmeTt0ZXh0LWluZGVudDouMHB4O3RleHQtdHJh
bnNmb3JtOm5vbmU7dGV4dC1kZWNvcmF0aW9uLXN0eWxlOmluaXRpYWw7dGV4dC1kZWNvcmF0aW9u
LWNvbG9yOmluaXRpYWw7ZmxvYXQ6bm9uZTtkaXNwbGF5OmlubGluZTsiPjxiciA+PC9zcGFuPjwv
ZGl2PjxkaXYgIHN0eWxlPSJtYXJnaW46LjBweDtwYWRkaW5nOi4wcHg7Ym9yZGVyOi4wcHg7b3V0
bGluZTouMHB4O2NsZWFyOmJvdGg7Ij48c3BhbiAgc3R5bGU9Im1hcmdpbjouMHB4O3BhZGRpbmc6
LjBweDtib3JkZXI6LjBweDtvdXRsaW5lOi4wcHg7Y29sb3I6IzAwMDAwMDtmb250LWZhbWlseTpD
YWxpYnJpLHNhbnMtc2VyaWY7Zm9udC1zaXplOjE0LjBweDtmb250LXN0eWxlOm5vcm1hbDtmb250
LXZhcmlhbnQtbGlnYXR1cmVzOm5vcm1hbDtmb250LXZhcmlhbnQtY2Fwczpub3JtYWw7Zm9udC13
ZWlnaHQ6NDAwO3RleHQtYWxpZ246anVzdGlmeTt0ZXh0LWluZGVudDouMHB4O3RleHQtdHJhbnNm
b3JtOm5vbmU7dGV4dC1kZWNvcmF0aW9uLXN0eWxlOmluaXRpYWw7dGV4dC1kZWNvcmF0aW9uLWNv
bG9yOmluaXRpYWw7ZmxvYXQ6bm9uZTtkaXNwbGF5OmlubGluZTsiPldlJm5ic3A7PHNwYW4gIHN0
eWxlPSJtYXJnaW46LjBweDtwYWRkaW5nOi4wcHg7Ym9yZGVyOi4wcHg7b3V0bGluZTouMHB4O2Nv
bG9yOiMwMDAwMDA7Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmO2ZvbnQtc2l6ZToxNC4w
cHg7Zm9udC1zdHlsZTpub3JtYWw7Zm9udC12YXJpYW50LWxpZ2F0dXJlczpub3JtYWw7Zm9udC12
YXJpYW50LWNhcHM6bm9ybWFsO2ZvbnQtd2VpZ2h0OjQwMDt0ZXh0LWFsaWduOnN0YXJ0O3RleHQt
aW5kZW50Oi4wcHg7dGV4dC10cmFuc2Zvcm06bm9uZTt0ZXh0LWRlY29yYXRpb24tc3R5bGU6aW5p
dGlhbDt0ZXh0LWRlY29yYXRpb24tY29sb3I6aW5pdGlhbDtmbG9hdDpub25lO2Rpc3BsYXk6aW5s
aW5lOyI+dXBsb2FkZWQgYSBkcmFmdCBkZXNjcmliaW5nJm5ic3A7PHNwYW4gIHN0eWxlPSJtYXJn
aW46LjBweDtwYWRkaW5nOi4wcHg7Ym9yZGVyOi4wcHg7b3V0bGluZTouMHB4OyI+YW4mbmJzcDth
cHBsaWNhdGlvbiZuYnNwO3BvbGljeS1hd2FyZW5lc3MmbmJzcDttZXRob2QmbmJzcDtmb3I8L3Nw
YW4+PHNwYW4gIHN0eWxlPSJtYXJnaW46LjBweDtwYWRkaW5nOi4wcHg7Ym9yZGVyOi4wcHg7b3V0
bGluZTouMHB4OyI+Jm5ic3A7TXVsdGlwYXRoJm5ic3A7UVVJQy4mbmJzcDs8YSAgaHJlZj0iaHR0
cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtYW4tbXVsdGlwYXRoLXF1aWMtYXBw
bGljYXRpb24tcG9saWN5LyI+aHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQt
YW4tbXVsdGlwYXRoLXF1aWMtYXBwbGljYXRpb24tcG9saWN5LzwvYT48L3NwYW4+PC9zcGFuPjwv
c3Bhbj48L2Rpdj48ZGl2ICBzdHlsZT0ibWFyZ2luOi4wcHg7cGFkZGluZzouMHB4O2JvcmRlcjou
MHB4O291dGxpbmU6LjBweDtjbGVhcjpib3RoOyI+PHNwYW4gIHN0eWxlPSJtYXJnaW46LjBweDtw
YWRkaW5nOi4wcHg7Ym9yZGVyOi4wcHg7b3V0bGluZTouMHB4O2ZvbnQtZmFtaWx5OkNhbGlicmks
c2Fucy1zZXJpZjsiPjxiciA+PC9zcGFuPjwvZGl2PjxkaXYgIHN0eWxlPSJtYXJnaW46LjBweDtw
YWRkaW5nOi4wcHg7Ym9yZGVyOi4wcHg7b3V0bGluZTouMHB4O2NsZWFyOmJvdGg7Ij48c3BhbiAg
c3R5bGU9Im1hcmdpbjouMHB4O3BhZGRpbmc6LjBweDtib3JkZXI6LjBweDtvdXRsaW5lOi4wcHg7
Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyI+VGhlIGdvYWwgaXMgdG8gZTwvc3Bhbj48
c3BhbiAgc3R5bGU9Im1hcmdpbjouMHB4O3BhZGRpbmc6LjBweDtib3JkZXI6LjBweDtvdXRsaW5l
Oi4wcHg7Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyI+bmFibGUmbmJzcDt0YWtpbmcm
bmJzcDthcHBsaWNhdGlvbnMnJm5ic3A7ZGVtYW5kcyZuYnNwO2ludG8mbmJzcDthY2NvdW50PC9z
cGFuPjxzcGFuICBzdHlsZT0ibWFyZ2luOi4wcHg7cGFkZGluZzouMHB4O2JvcmRlcjouMHB4O291
dGxpbmU6LjBweDtmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7Ij4mbmJzcDt3aGVuJm5i
c3A7bWFuYWdpbmcmbmJzcDtwYXRocyBvciBzY2hlZHVsaW5nIHBhY2tldHMmbmJzcDtpbiZuYnNw
O011bHRpcGF0aCBRVUlDLiZuYnNwOzwvc3Bhbj48L2Rpdj48ZGl2ICBzdHlsZT0ibWFyZ2luOi4w
cHg7cGFkZGluZzouMHB4O2JvcmRlcjouMHB4O291dGxpbmU6LjBweDtjbGVhcjpib3RoOyI+PHNw
YW4gIHN0eWxlPSJtYXJnaW46LjBweDtwYWRkaW5nOi4wcHg7Ym9yZGVyOi4wcHg7b3V0bGluZTou
MHB4O2ZvbnQtZmFtaWx5OkNhbGlicmksc2Fucy1zZXJpZjsiPjxiciA+PC9zcGFuPjwvZGl2Pjxk
aXYgIHN0eWxlPSJtYXJnaW46LjBweDtwYWRkaW5nOi4wcHg7Ym9yZGVyOi4wcHg7b3V0bGluZTou
MHB4O2NsZWFyOmJvdGg7Ij48c3BhbiAgc3R5bGU9Im1hcmdpbjouMHB4O3BhZGRpbmc6LjBweDti
b3JkZXI6LjBweDtvdXRsaW5lOi4wcHg7Zm9udC1mYW1pbHk6Q2FsaWJyaSxzYW5zLXNlcmlmOyI+
VGhlIGRyYWZ0IGRlc2NyaWJlczo8L3NwYW4+PC9kaXY+PG9sICBzdHlsZT0icGFkZGluZzouMHB4
IC4wcHggLjBweCAyNC4wcHg7bWFyZ2luOjIuMHB4IC4wcHg7bGlzdC1zdHlsZS10eXBlOmRlY2lt
YWw7Ij48bGkgPjxkaXYgIHN0eWxlPSJtYXJnaW46LjBweDtwYWRkaW5nOi4wcHg7Ym9yZGVyOi4w
cHg7b3V0bGluZTouMHB4O2NsZWFyOmJvdGg7Ij48c3BhbiAgc3R5bGU9Im1hcmdpbjouMHB4O3Bh
ZGRpbmc6LjBweDtib3JkZXI6LjBweDtvdXRsaW5lOi4wcHg7Zm9udC1mYW1pbHk6Q2FsaWJyaSxz
YW5zLXNlcmlmOyI+UGVyLWNvbm5lY3Rpb24mbmJzcDtQb2xpY3kgaW1wb3NlZCBieSBhcHBsaWNh
dGlvbiB0byBpbmRpY2F0ZSB0aGUmbmJzcDs8c3BhbiAgc3R5bGU9Im1hcmdpbjouMHB4O3BhZGRp
bmc6LjBweDtib3JkZXI6LjBweDtvdXRsaW5lOi4wcHg7Ij5wYWNrZXQ8L3NwYW4+PHNwYW4gIHN0
eWxlPSJtYXJnaW46LjBweDtwYWRkaW5nOi4wcHg7Ym9yZGVyOi4wcHg7b3V0bGluZTouMHB4OyI+
Jm5ic3A7c2NoZWR1bGluZyZuYnNwO2NvbXBvbmVudCZuYnNwO2FuZCZuYnNwO3RoZSZuYnNwO3Bh
dGgmbmJzcDttYW5hZ2VyJm5ic3A7PHNwYW4gIHN0eWxlPSJtYXJnaW46LjBweDtwYWRkaW5nOi4w
cHg7Ym9yZGVyOi4wcHg7b3V0bGluZTouMHB4OyI+Zm9yJm5ic3A7cGF0aCZuYnNwO3NlbGVjdGlv
biZuYnNwO2FuZCZuYnNwO2RhdGEmbmJzcDt0cmFuc21pc3Npb248L3NwYW4+PC9zcGFuPjwvc3Bh
bj48L2Rpdj48L2xpPjxsaSA+PGRpdiAgc3R5bGU9Im1hcmdpbjouMHB4O3BhZGRpbmc6LjBweDti
b3JkZXI6LjBweDtvdXRsaW5lOi4wcHg7Y2xlYXI6Ym90aDsiPjxzcGFuICBzdHlsZT0ibWFyZ2lu
Oi4wcHg7cGFkZGluZzouMHB4O2JvcmRlcjouMHB4O291dGxpbmU6LjBweDtmb250LWZhbWlseTpD
YWxpYnJpLHNhbnMtc2VyaWY7Ij5QZXItc3RyZWFtJm5ic3A7SW50ZW50Jm5ic3A7PHNwYW4gIHN0
eWxlPSJtYXJnaW46LjBweDtwYWRkaW5nOi4wcHg7Ym9yZGVyOi4wcHg7b3V0bGluZTouMHB4OyI+
aW1wbGVtZW50ZWQmbmJzcDt0aHJvdWdoJm5ic3A7dGhlJm5ic3A7bXVsdGlwbGUmbmJzcDtzdHJl
YW1zJm5ic3A7aW4mbmJzcDtRVUlDIHRvIHV0aWxpemUmbmJzcDs8c3BhbiAgc3R5bGU9Im1hcmdp
bjouMHB4O3BhZGRpbmc6LjBweDtib3JkZXI6LjBweDtvdXRsaW5lOi4wcHg7Ij5wcmlvcml0aWVz
Jm5ic3A7dG8mbmJzcDtpbXBsZW1lbnQmbmJzcDthcHBsaWNhdGlvbnMmbmJzcDtpbnRlbnQ8L3Nw
YW4+PC9zcGFuPjwvc3Bhbj48L2Rpdj48L2xpPjwvb2w+PGRpdiAgc3R5bGU9Im1hcmdpbjouMHB4
O3BhZGRpbmc6LjBweDtib3JkZXI6LjBweDtvdXRsaW5lOi4wcHg7Y2xlYXI6Ym90aDsiPjxzcGFu
ICBzdHlsZT0ibWFyZ2luOi4wcHg7cGFkZGluZzouMHB4O2JvcmRlcjouMHB4O291dGxpbmU6LjBw
eDtmb250LWZhbWlseTpDYWxpYnJpLHNhbnMtc2VyaWY7Ij48L3NwYW4+PGJyID48L2Rpdj48ZGl2
ICBzdHlsZT0ibWFyZ2luOi4wcHg7cGFkZGluZzouMHB4O2JvcmRlcjouMHB4O291dGxpbmU6LjBw
eDtjbGVhcjpib3RoOyI+PHNwYW4gIHN0eWxlPSJtYXJnaW46LjBweDtwYWRkaW5nOi4wcHg7Ym9y
ZGVyOi4wcHg7b3V0bGluZTouMHB4OyI+TG9vayZuYnNwO2ZvcndhcmQmbmJzcDt0byB5b3VyIGNv
bW1lbnRzLiZuYnNwOzwvc3Bhbj48L2Rpdj48ZGl2ICBzdHlsZT0ibWFyZ2luOi4wcHg7cGFkZGlu
ZzouMHB4O2JvcmRlcjouMHB4O291dGxpbmU6LjBweDtjbGVhcjpib3RoOyI+PHNwYW4gIHN0eWxl
PSJtYXJnaW46LjBweDtwYWRkaW5nOi4wcHg7Ym9yZGVyOi4wcHg7b3V0bGluZTouMHB4OyI+PGJy
ID48L3NwYW4+PC9kaXY+PGRpdiAgc3R5bGU9Im1hcmdpbjouMHB4O3BhZGRpbmc6LjBweDtib3Jk
ZXI6LjBweDtvdXRsaW5lOi4wcHg7Y2xlYXI6Ym90aDsiPjxzcGFuICBzdHlsZT0ibWFyZ2luOi4w
cHg7cGFkZGluZzouMHB4O2JvcmRlcjouMHB4O291dGxpbmU6LjBweDsiPlRoYW5rczwvc3Bhbj4m
bmJzcDs8ZGl2ICBzdHlsZT0ibWFyZ2luOi4wcHg7cGFkZGluZzouMHB4O2JvcmRlcjouMHB4O291
dGxpbmU6LjBweDtjbGVhcjpib3RoOyI+QmVzdCByZWdhcmRzLDwvZGl2PlFpbmc8L2Rpdj48ZGl2
ICBzdHlsZT0ibWFyZ2luOi4wcHg7cGFkZGluZzouMHB4O2JvcmRlcjouMHB4O291dGxpbmU6LjBw
eDtjbGVhcjpib3RoOyI+PGJyICBzdHlsZT0iY29sb3I6IzAwMDAwMDtmb250LWZhbWlseTpUYWhv
bWEsQXJpYWwsU1RIZWl0aSxTaW1TdW47Zm9udC1zaXplOjE0LjBweDtmb250LXN0eWxlOm5vcm1h
bDtmb250LXZhcmlhbnQtbGlnYXR1cmVzOm5vcm1hbDtmb250LXZhcmlhbnQtY2Fwczpub3JtYWw7
Zm9udC13ZWlnaHQ6NDAwO2xldHRlci1zcGFjaW5nOm5vcm1hbDtvcnBoYW5zOjI7dGV4dC1hbGln
bjpzdGFydDt0ZXh0LWluZGVudDouMHB4O3RleHQtdHJhbnNmb3JtOm5vbmU7d2hpdGUtc3BhY2U6
bm9ybWFsO3dpZG93czoyO3dvcmQtc3BhY2luZzouMHB4OyI+PC9kaXY+PC9kaXY+PGRpdiAgc3R5
bGU9ImNsZWFyOmJvdGg7Ij48YnIgPjwvZGl2PjxibG9ja3F1b3RlICBzdHlsZT0ibWFyZ2luLXJp
Z2h0Oi4wcHg7bWFyZ2luLXRvcDouMHB4O21hcmdpbi1ib3R0b206LjBweDtmb250LWZhbWlseTpU
YWhvbWEsQXJpYWwsU1RIZWl0aSxTaW1TdW47Zm9udC1zaXplOjE0LjBweDtjb2xvcjojMDAwMDAw
OyI+PGRpdiAgc3R5bGU9ImNsZWFyOmJvdGg7Ij4tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS08L2Rpdj5BJm5ic3A7bmV3Jm5i
c3A7dmVyc2lvbiZuYnNwO29mJm5ic3A7SS1ELCZuYnNwO2RyYWZ0LWFuLW11bHRpcGF0aC1xdWlj
LWFwcGxpY2F0aW9uLXBvbGljeS0wMC50eHQ8YnIgPmhhcyZuYnNwO2JlZW4mbmJzcDtzdWNjZXNz
ZnVsbHkmbmJzcDtzdWJtaXR0ZWQmbmJzcDtieSZuYnNwO1FpbmcmbmJzcDtBbiZuYnNwO2FuZCZu
YnNwO3Bvc3RlZCZuYnNwO3RvJm5ic3A7dGhlPGJyID5JRVRGJm5ic3A7cmVwb3NpdG9yeS48YnIg
PjxiciA+TmFtZTombmJzcDsmbmJzcDtkcmFmdC1hbi1tdWx0aXBhdGgtcXVpYy1hcHBsaWNhdGlv
bi1wb2xpY3k8YnIgPlJldmlzaW9uOiZuYnNwOzAwPGJyID5UaXRsZTombmJzcDsmbmJzcDtFbmFi
bGluZyZuYnNwO2FwcGxpY2F0aW9uJm5ic3A7cG9saWN5LWF3YXJlbmVzcyZuYnNwO2luJm5ic3A7
TXVsdGlwYXRoJm5ic3A7UVVJQzxiciA+RG9jdW1lbnQmbmJzcDtkYXRlOiZuYnNwOzIwMjAtMDct
MDY8YnIgPkdyb3VwOiZuYnNwOyZuYnNwO0luZGl2aWR1YWwmbmJzcDtTdWJtaXNzaW9uPGJyID5Q
YWdlczombmJzcDsmbmJzcDsxMDxiciA+VVJMOiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxhICBocmVmPSJodHRw
czovL3d3dy5pZXRmLm9yZy9pbnRlcm5ldC1kcmFmdHMvZHJhZnQtYW4tbXVsdGlwYXRoLXF1aWMt
YXBwbGljYXRpb24tcG9saWN5LTAwLnR4dCIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vd3d3Lmll
dGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1hbi1tdWx0aXBhdGgtcXVpYy1hcHBsaWNhdGlv
bi1wb2xpY3ktMDAudHh0PC9hPjxiciA+U3RhdHVzOiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxhICBocmVmPSJodHRwczovL2RhdGF0cmFja2Vy
LmlldGYub3JnL2RvYy9kcmFmdC1hbi1tdWx0aXBhdGgtcXVpYy1hcHBsaWNhdGlvbi1wb2xpY3kv
IiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQt
YW4tbXVsdGlwYXRoLXF1aWMtYXBwbGljYXRpb24tcG9saWN5LzwvYT48YnIgPkh0bWxpemVkOiZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxhICBocmVmPSJodHRwczov
L3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtYW4tbXVsdGlwYXRoLXF1aWMtYXBwbGljYXRpb24t
cG9saWN5LTAwIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2Ry
YWZ0LWFuLW11bHRpcGF0aC1xdWljLWFwcGxpY2F0aW9uLXBvbGljeS0wMDwvYT48YnIgPkh0bWxp
emVkOiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOzxhICBocmVmPSJo
dHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9odG1sL2RyYWZ0LWFuLW11bHRpcGF0aC1x
dWljLWFwcGxpY2F0aW9uLXBvbGljeSIgdGFyZ2V0PSJfYmxhbmsiPmh0dHBzOi8vZGF0YXRyYWNr
ZXIuaWV0Zi5vcmcvZG9jL2h0bWwvZHJhZnQtYW4tbXVsdGlwYXRoLXF1aWMtYXBwbGljYXRpb24t
cG9saWN5PC9hPjxiciA+PGJyID48YnIgPkFic3RyYWN0OjxiciA+Jm5ic3A7Jm5ic3A7Jm5ic3A7
VGhpcyZuYnNwO2RvY3VtZW50Jm5ic3A7ZGVzY3JpYmVzJm5ic3A7YW4mbmJzcDthcHBsaWNhdGlv
biZuYnNwO3BvbGljeS1hd2FyZW5lc3MmbmJzcDttZXRob2QmbmJzcDtmb3I8YnIgPiZuYnNwOyZu
YnNwOyZuYnNwO011bHRpcGF0aCZuYnNwO1FVSUMsJm5ic3A7dG8mbmJzcDtlbmFibGUmbmJzcDt0
YWtpbmcmbmJzcDthcHBsaWNhdGlvbnMnJm5ic3A7ZGVtYW5kcyZuYnNwO2ludG8mbmJzcDthY2Nv
dW50PGJyID4mbmJzcDsmbmJzcDsmbmJzcDt3aGVuJm5ic3A7bWFuYWdpbmcmbmJzcDtwYXRocyZu
YnNwO29yJm5ic3A7c2NoZWR1bGluZyZuYnNwO3BhY2tldHMmbmJzcDtpbiZuYnNwO011bHRpcGF0
aCZuYnNwO1FVSUMuPGJyID48YnIgPiZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OzxiciA+PGJyID48YnIgPlBsZWFzZSZuYnNwO25vdGUmbmJzcDt0aGF0Jm5ic3A7aXQmbmJzcDtt
YXkmbmJzcDt0YWtlJm5ic3A7YSZuYnNwO2NvdXBsZSZuYnNwO29mJm5ic3A7bWludXRlcyZuYnNw
O2Zyb20mbmJzcDt0aGUmbmJzcDt0aW1lJm5ic3A7b2YmbmJzcDtzdWJtaXNzaW9uPGJyID51bnRp
bCZuYnNwO3RoZSZuYnNwO2h0bWxpemVkJm5ic3A7dmVyc2lvbiZuYnNwO2FuZCZuYnNwO2RpZmYm
bmJzcDthcmUmbmJzcDthdmFpbGFibGUmbmJzcDthdCZuYnNwO3Rvb2xzLmlldGYub3JnLjxiciA+
PGJyID5UaGUmbmJzcDtJRVRGJm5ic3A7U2VjcmV0YXJpYXQ8YnIgPjwvYmxvY2txdW90ZT48ZGl2
ICBzdHlsZT0ibGluZS1oZWlnaHQ6MjAuMHB4O2NsZWFyOmJvdGg7Ij48YnIgPjwvZGl2PjwvZGl2
PjwvZGl2Pg==
------=ALIBOUNDARY_20716_4b9ac940_5f03fdc9_11f45a--


From nobody Mon Jul  6 22:34:35 2020
Return-Path: <vasilvv@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 285163A09C9 for <quic@ietfa.amsl.com>; Mon,  6 Jul 2020 12:13:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level: 
X-Spam-Status: No, score=-17.599 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, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, 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 JhFobOb7hdsb for <quic@ietfa.amsl.com>; Mon,  6 Jul 2020 12:12:59 -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 277183A09C6 for <quic@ietf.org>; Mon,  6 Jul 2020 12:12:59 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id e8so12550354ljb.0 for <quic@ietf.org>; Mon, 06 Jul 2020 12:12:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=gpF5lo7bAddunoqXtCAWWG5b8eN1zv6R+OQomFo6SZ8=; b=DgSos9Up71p445RYLMblv+4iOEeuJhxFKMqlmoz57ddQ2t2eCWSfxmtCymYm5KYoM6 SSqYYgkqwvJAEA6RacbOdUOB62eB89kD9LAHxyjJGugjwrj3ZY6CQyd6GzcwDTbM5rVB +/nrVqMXXRLQRLrvFY1XWp9ihGxIKWTTdL0k6qnRbVcwFroZTDC50bGf3uuG6jfv/No9 EcuJ5IQwD0mTrSZzc3BNQkuJkcG0v4DKK3FQRxaa8CJr+PnfPK/CCam+KnxdESXwi7VM fNAfDXlKQCkmaTGZlgjU6RFcS3enSGcThEMVFD9jwcXhdxd8fAXsXy2d5AI6YRn+Xg/V DDqw==
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=gpF5lo7bAddunoqXtCAWWG5b8eN1zv6R+OQomFo6SZ8=; b=lcCO/Qhvsgw+Tj+m2tdOIwbjUxRqGNcKiOTPEBD0ueJj0pkXG1EFVWXNo2JmMpLGCQ i2Pxq1DaEsuJUXzBdkDUCfsodusWZnCq75TK3BIR0j5a+vuaLF446Bsb/+55nYZq9klr 0s70/x6EfkKZsss9ShoVb7QUgnqdqiz/LjRMwWSfjnJySnmeq788YOhosPrWByKUdwqG HOBoQEyiMgEE0A7F5fvxuKBHSE5j0laY/KxPG0OYvoaa2UFZYLy1OPxnmDbouibWpnt9 UjbxI39VRDqq1kpiuxuGWGHDXvI6nOSAa4LcPRYxBQnhG7G58vMSlOhvmKLMhYFQ7+tI MOsw==
X-Gm-Message-State: AOAM533LsAMupjk81c5jKQHvvMyi0hjZZK9wUTGjNSnn6uwjzREwmLOj +jdkPGRDt9fyCe33O9ZnPJ7LsvTAcMb3MC/8dxRJpA==
X-Google-Smtp-Source: ABdhPJzmPpPGvJEaorPZysEl0nwIQ1kqmPpJqgYroNEiQxaSYNfsQ+J7eIrV3ky4TLi1eSQLO65Q8e1qSGD987TjfqM=
X-Received: by 2002:a05:651c:106e:: with SMTP id y14mr1971885ljm.381.1594062776729;  Mon, 06 Jul 2020 12:12:56 -0700 (PDT)
MIME-Version: 1.0
From: Victor Vasiliev <vasilvv@google.com>
Date: Mon, 6 Jul 2020 15:12:45 -0400
Message-ID: <CAAZdMaf2dKab0dJU8MLZc9JzEcVSvf8s9kgeZFo3tmsRtx2sNQ@mail.gmail.com>
Subject: Application-Layer Protocol Settings
To: "tls@ietf.org" <TLS@ietf.org>, HTTP Working Group <ietf-http-wg@w3.org>
Content-Type: multipart/alternative; boundary="0000000000008f08ac05a9caa908"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/3SsC_nkF4D9Mn4ReEnE0fAQz-PU>
X-Mailman-Approved-At: Mon, 06 Jul 2020 22:34:34 -0700
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, 06 Jul 2020 19:13:01 -0000

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

Hello TLS and HTTP working groups,

(QUIC WG bcc'd as this has been discussed there before)

Currently, we use SETTINGS frames as an extensibility mechanism in HTTP/2
and HTTP/3.  The SETTINGS frame is sent at the very beginning of TLS
application data; this approach, while simple, has some drawbacks.  The
most notable one is that when SETTINGS are used to negotiate extensions,
there is an entire round-trip where the client can send requests, but
doesn't know yet about any server extensions, thus making any
extension-dependant requests take an extra RTT.

The proposed solution to this problem is to move HTTP SETTINGS frame into
the TLS handshake.  Here are some issues where this has been discussed
before:

   - https://github.com/quicwg/base-drafts/issues/3086
   - https://github.com/quicwg/base-drafts/issues/3622
   - https://github.com/WICG/client-hints-infrastructure/pull/30

I wrote up a draft for the TLS extension that would solve this problem:
https://tools.ietf.org/html/draft-vvv-tls-alps-00

I also wrote up a draft that explains how to use that extension with HTTP,
and defines some settings (the ones discussed here
<https://github.com/quicwg/base-drafts/issues/3622>) that would not be
possible without it: https://tools.ietf.org/html/draft-vvv-httpbis-alps-00

I would appreciate feedback on those drafts.

Thanks,
  Victor.

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

<div dir=3D"ltr">Hello TLS=C2=A0and HTTP working groups,<div><br><div>(QUIC=
 WG bcc&#39;d as this has been discussed there before)<br><div><br></div><d=
iv>Currently, we use SETTINGS frames as an extensibility mechanism in HTTP/=
2 and HTTP/3.=C2=A0 The SETTINGS frame is sent at the very beginning of TLS=
 application data; this approach, while simple, has some drawbacks.=C2=A0 T=
he most notable one is that when SETTINGS are used to negotiate extensions,=
 there is an entire round-trip where the client can send requests, but does=
n&#39;t know yet about any server extensions, thus making any extension-dep=
endant requests take an extra RTT.<br></div><div><br></div><div>The propose=
d solution to this problem is to move HTTP SETTINGS frame into the TLS hand=
shake.=C2=A0 Here are some issues where this has been discussed before:</di=
v><div><ul><li><a href=3D"https://github.com/quicwg/base-drafts/issues/3086=
" target=3D"_blank">https://github.com/quicwg/base-drafts/issues/3086</a><b=
r></li><li><a href=3D"https://github.com/quicwg/base-drafts/issues/3622" ta=
rget=3D"_blank">https://github.com/quicwg/base-drafts/issues/3622</a><br></=
li><li><a href=3D"https://github.com/WICG/client-hints-infrastructure/pull/=
30">https://github.com/WICG/client-hints-infrastructure/pull/30</a><br></li=
></ul><div>I wrote up a draft for the TLS extension that would solve this p=
roblem:=C2=A0<a href=3D"https://tools.ietf.org/html/draft-vvv-tls-alps-00" =
target=3D"_blank">https://tools.ietf.org/html/draft-vvv-tls-alps-00</a></di=
v></div><div><br></div><div>I also wrote up a draft that explains how to us=
e that extension with HTTP, and defines some settings (the ones discussed <=
a href=3D"https://github.com/quicwg/base-drafts/issues/3622" target=3D"_bla=
nk">here</a>) that would not be possible without it:=C2=A0<a href=3D"https:=
//tools.ietf.org/html/draft-vvv-httpbis-alps-00" target=3D"_blank">https://=
tools.ietf.org/html/draft-vvv-httpbis-alps-00</a></div><div><br></div><div>=
I would appreciate feedback on those drafts.</div><div><br></div><div>Thank=
s,</div><div>=C2=A0 Victor.</div><div></div></div></div></div>

--0000000000008f08ac05a9caa908--


From nobody Tue Jul  7 21:00:23 2020
Return-Path: <kangjiao@huawei.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 249063A0044 for <quic@ietfa.amsl.com>; Tue,  7 Jul 2020 21:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Level: 
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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 jgsvq4B-RFML for <quic@ietfa.amsl.com>; Tue,  7 Jul 2020 21:00:18 -0700 (PDT)
Received: from huawei.com (lhrrgout.huawei.com [185.176.76.210]) (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 D01703A05A0 for <quic@ietf.org>; Tue,  7 Jul 2020 20:59:59 -0700 (PDT)
Received: from lhreml703-chm.china.huawei.com (unknown [172.18.7.106]) by Forcepoint Email with ESMTP id 83593AEBB6C614A2306E for <quic@ietf.org>; Wed,  8 Jul 2020 04:59:58 +0100 (IST)
Received: from lhreml703-chm.china.huawei.com (10.201.108.52) by lhreml703-chm.china.huawei.com (10.201.108.52) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1913.5; Wed, 8 Jul 2020 04:59:58 +0100
Received: from DGGEMM421-HUB.china.huawei.com (10.1.198.38) by lhreml703-chm.china.huawei.com (10.201.108.52) with Microsoft SMTP Server (version=TLS1_0, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA_P256) id 15.1.1913.5 via Frontend Transport; Wed, 8 Jul 2020 04:59:57 +0100
Received: from DGGEMM534-MBS.china.huawei.com ([169.254.7.44]) by dggemm421-hub.china.huawei.com ([10.1.198.38]) with mapi id 14.03.0487.000; Wed, 8 Jul 2020 11:59:34 +0800
From: Kangjiao <kangjiao@huawei.com>
To: Christian Huitema <huitema@huitema.net>, Martin Thomson <mt@lowentropy.net>
CC: "quic@ietf.org" <quic@ietf.org>
Subject: RE: Hope a discussion for draft-li-quic-optimizing-ack-in-wlan-00
Thread-Topic: Hope a discussion for draft-li-quic-optimizing-ack-in-wlan-00
Thread-Index: AdZRyGcTBCKzXYE+TnatOw5glQUhXgBIp/IAAC2b1RD//+nPAP/9dcEA
Date: Wed, 8 Jul 2020 03:59:33 +0000
Message-ID: <719A2C1D4AC73847B6E1BF21DF1545EAE5C802D6@dggemm534-mbs.china.huawei.com>
References: <719A2C1D4AC73847B6E1BF21DF1545EAE5C7CE04@dggemm534-mbs.china.huawei.com> <cd99a66b-6478-4b15-b6fc-0c512e92e118@www.fastmail.com> <719A2C1D4AC73847B6E1BF21DF1545EAE5C7EDFD@dggemm534-mbs.china.huawei.com> <98c0a7a0-2dfa-a327-33d3-5c337c390fd2@huitema.net>
In-Reply-To: <98c0a7a0-2dfa-a327-33d3-5c337c390fd2@huitema.net>
Accept-Language: zh-CN, en-US
Content-Language: zh-CN
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.67.102.89]
Content-Type: multipart/alternative; boundary="_000_719A2C1D4AC73847B6E1BF21DF1545EAE5C802D6dggemm534mbschi_"
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/lzOQ146aVs1VvH4NkMsevEb-_B0>
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, 08 Jul 2020 04:00:21 -0000

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

SGkgQ2hyaXN0aWFuLA0KDQpRdWVzdGlvbiAxOg0KV2UgaGF2ZSBhIHVkcC1iYXNlZCBzaW11bGF0
aW9uIHRvb2wgaW4gZ2l0aHViICggaHR0cHM6Ly9naXRodWIuY29tL2ZpbGx0aGVwaXBlL2Fja2Vt
dSApLiBZb3UgY2FuIGFsc28gZGlyZWN0bHkgcmVmZXIgdG8gRmlndXJlIDkoYikgaW4gdGhlIHBh
cGVyIFsyXSBmb3IgdGhlIHNpbXVsYXRpb24gcmVzdWx0cy4gQW4gYWNrbm93bGVkZ2VtZW50IHBv
bGljeSB0aGF0IHNlbmRzIGxlc3MgQUNLcyBhY2hpZXZlcyBoaWdoZXIgdGhvdWdocHV0LiBBbHNv
IHRoZSBwb2xpY3kgcHJvcG9zZWQgaW4gZHJhZnQtbGktcXVpYy1vcHRpbWl6aW5nLWFjay1pbi13
bGFuLTAwIGFwcHJvYWNoZXMgdGhlIHRyYW5zcG9ydCB1cHBlciBib3VuZCB3aXRoIGEgbWluaW1p
emVkIEFDSyBmcmVxdWVuY3kgKDgwMi4xMW4pLg0KDQpRdWVzdGlvbiAyOg0KQ29tcGFyaW5nIHRv
IGRyYWZ0LWl5ZW5nYXItcXVpYy1kZWxheWVkLWFjay0wMCwgaWYgdGhlIGRlbGF5IGlzIHNldCB0
byBhIGZyYWN0aW9uIG9mIHRoZSBSVFQsIHdlIHRoaW5rIHRoZSBkaWZmZXJlbmNlIG1pZ2h0IGJl
IHRoYXQ6DQpGb3IgZHJhZnQtaXllbmdhci1xdWljLWRlbGF5ZWQtYWNrLTAwLCBBQ0sgZnJlcXVl
bmN5IGlzIGNvbXB1dGVkIGFzOiBNQVh7YncvKCBwYWNrZXRfdG9sZXJhbmNlICptYXhfcGFja2V0
X3NpemUpLCAxLyBtYXhfYWNrX2RlbGF5fS4NCkZvciBkcmFmdC1saS1xdWljLW9wdGltaXppbmct
YWNrLWluLXdsYW4tMDAsIEFDSyBmcmVxdWVuY3kgaXMgY29tcHV0ZWQgYXM6IE1JTntidy8ocGFj
a2V0X3RvbGVyYW5jZSAqbWF4X3BhY2tldF9zaXplKSwgYmV0YS9SVFRtaW59IChiZXRhIGluZGlj
YXRlcyB0aGUgbnVtYmVyIG9mIEFDS3MgcGVyIFJUVCwgUlRULzQgaXMgcmVjb21tZW5kZWQgaW4g
b3VyIHNvbHV0aW9uKS4NCkluIHByYWN0aWNlLCB3ZSBoYXZlIHByb3ZlZCB0aGF0IHVzaW5nIGEg
TUlOIGluc3RlYWQgb2YgYSBNQVggY2FuIGFsc28gYWNoaWV2ZSBlcXVhbGx5IGdvb2QgcGVyZm9y
bWFuY2UuDQoNClF1ZXN0aW9uIDM6DQoNCkluIGRlbGF5ZWQgQUNLLCB0cmFkaXRpb25hbCBSVFQg
Y2FsY3VsYXRpb24gbWVldHMgdGhlIGNoYWxsZW5nZSBvZiBiaWFzZXMgZm9yIHRoZSBzZW5kZXIg
Y2FuIGhhcmRseSBnZW5lcmF0ZSBwZXItcGFja2V0IFJUVCBzYW1wbGVzOg0KDQpUaGUgYWxnb3Jp
dGhtIGluIGRyYWZ0LWh1aXRlbWEtcXVpYy10cy0wMCBpcyBpbnRlcmVzdGluZy4gSWYgbXkgdW5k
ZXJzdGFuZGluZyBpcyByaWdodCwgdGhlIE9XRCBpcyBjb21wdXRlZCBhbGwgb24gc2VuZGVyIHNp
ZGUgYW5kIHRoZSBmb3JtdWxhcyBpbmNsdWRlOg0KDQpsYXRlc3RfT1dEID0gdDMgKGxhcmdlc3Qg
YWNrZWQgcGFja2V0IGFycml2YWwpIOKAkyB0MSAobGFyZ2VzdCBhY2tlZCBwYWNrZXQgZGVwYXJ0
dXJlKSAtIHBoYXNlX3NoaWZ0Lg0KcGhhc2Vfc2hpZnQgPSB0MyAobGFyZ2VzdCBhY2tlZCBwYWNr
ZXQgYXJyaXZhbCkg4oCTIHQxIChsYXJnZXN0IGFja2VkIHBhY2tldCBkZXBhcnR1cmUpIC0gbGF0
ZXN0X3J0dC8yDQoNCkZvciBkcmFmdC1saS1xdWljLW9wdGltaXppbmctYWNrLWluLXdsYW4tMDAs
IFJUVG1pbiBpcyBhIGZhY3RvciB1c2VkIHRvIHVwZGF0ZSBBQ0sgaW50ZW5zaXR5LiBJbiBvcmRl
ciB0byBpbXByb3ZlIGFjY3VyYWN5LCB3ZSBhZG9wdCBPV0QtYmFzZWQgUlRUbWluIGVzdGltYXRp
b24gaW5zdGVhZCBvZiByZXBvcnRpbmcgQUNLIGRlbGF5cyBmb3IgdGhlIGxhcmdlc3QgYWNrbm93
bGVkZ2VkIHBhY2tldCBpbiBBQ0sgZnJhbWUgaW4gUVVJQyBwcm90b2NvbC4gVGhlIGZvcm11bGFz
IGluY2x1ZGU6DQoNClJUVG1pbl9zYW1wbGUgPSB0MiAoQUNLIGFycml2YWwpIOKAkyB0MSAocGFj
a2V0IHdpdGggT1dEbWluIGRlcGFydHVyZSkgLSBkZWx0YV90IChBQ0sgRGVsYXkpICAgLS0tLSBv
biBzZW5kZXIgc2lkZQ0KZGVsdGFfdCA9IHQzIChwYWNrZXQgd2l0aCBPV0RtaW4gYXJyaXZhbCkg
4oCTIHQ0IChBQ0sgZGVwYXJ0dXJlKSAgIC0tLSBvbiByZWNlaXZlciBzaWRlICggSWYgdGhlIHJl
Y2VpdmVyIGNhbiBzZW5kIHQzIGFuZCB0NCB0byB0aGUgc2VuZGVyLCBkZWx0YV90IGNhbiBhbHNv
IGJlIGNhbGN1bGF0ZWQgb24gc2VuZGVyIHNpZGUuKQ0KDQpGb3IgbW9yZSBkZXRhaWxzLCBwbGVh
c2UgcmVmZXIgdG8gb3VyIHBhcGVyIGFuZCBkcmFmdC4gVGhhbmtzDQoNClNpbmNlcmVseSwNCkpp
YW8NCkZyb206IENocmlzdGlhbiBIdWl0ZW1hIFttYWlsdG86aHVpdGVtYUBodWl0ZW1hLm5ldF0N
ClNlbnQ6IFR1ZXNkYXksIEp1bHkgNywgMjAyMCA1OjA3IEFNDQpUbzogS2FuZ2ppYW8gPGthbmdq
aWFvQGh1YXdlaS5jb20+OyBNYXJ0aW4gVGhvbXNvbiA8bXRAbG93ZW50cm9weS5uZXQ+DQpDYzog
cXVpY0BpZXRmLm9yZw0KU3ViamVjdDogUmU6IEhvcGUgYSBkaXNjdXNzaW9uIGZvciBkcmFmdC1s
aS1xdWljLW9wdGltaXppbmctYWNrLWluLXdsYW4tMDANCg0KDQpIZWxsbyBKaWFvLA0KDQpZb3Vy
IGRyYWZ0IGlzIG1vdGl2YXRlZCBieSBzcGVjaWZpYyBkYXRhIGFib3V0IHJ1bm5pbmcgaGlnaCBi
YW5kd2lkdGggYXBwbGljYXRpb25zIG92ZXIgd2lyZWxlc3MgbG9jYWwgYXJlYSBuZXR3b3JrLiBJ
dCB3b3VsZCBiZSBpbnRlcmVzdGluZyB0byBjb21wYXJlIGJlaGF2aW9yIG9mIHRoZXNlIGFwcGxp
Y2F0aW9ucyB1c2luZyBkaWZmZXJlbnQgYWNrbm93bGVkZ2VtZW50IHBvbGljaWVzLCBwcm9iYWJs
eSB1c2luZyBzaW11bGF0aW9ucy4gRG8geW91IGhhdmUgZGVmaW5pdGlvbnMgb2YgdGhlIGFwcGxp
Y2F0aW9uIGFuZCBvZiB0aGUgV0xBTiB0aGF0IHdlIGNvdWxkIGVudGVyIGluIHNpbXVsYXRpb25z
Pw0KDQpUaGUgZHJhZnQgZHJhZnQtaXllbmdhci1xdWljLWRlbGF5ZWQtYWNrLTAwIHByb3ZpZGVz
IGEgd2F5IGZvciBzZW5kZXJzIHRvIHNwZWNpZnkgYm90aCB0aGUgbWF4aW11bSBkZWxheSBiZXR3
ZWVuIGFja25vd2xlZGdlbWVudHMgYW5kIHRoZSBtYXhpbXVtIG51bWJlciBvZiBwYWNrZXRzIGJl
dHdlZW4gYWNrbm93bGVkZ2VtZW50LCB3aXRoIHJlY2VpdmVycyBzZW5kaW5nIGFja25vd2xlZGdl
bWVudHMgd2hlbiBvbmUgb2YgdGhlIGNvbmRpdGlvbnMgaXMgdHJ1ZS4gU2V2ZXJhbCBzZXJ2ZXJz
IHNldCB0aGUgZGVsYXkgdG8gYSBmcmFjdGlvbiBvZiB0aGUgUlRULCBhbmQgdGhlIG51bWJlciBv
ZiBwYWNrZXRzIHRvIGEgY29ycmVzcG9uZGluZyBmcmFjdGlvbiBvZiB0aGUgbnVtYmVyIG9mIHBh
Y2tldHMgcGVyIGNvbmdlc3Rpb24gd2luZG93IC0tIFJUVC84IGlzIG9mdGVuIHN1Z2dlc3RlZC4g
SG93IGlzIHRoYXQgZGlmZmVyZW50IGZyb20gc2V0dGluZyB0aGUgIkFDSyBpbnRlbnNpdHkiIHN1
Z2dlc3RlZCBpbiBkcmFmdC1saS1xdWljLW9wdGltaXppbmctYWNrLWluLXdsYW4tMDA/DQoNClRo
ZSBkcmFmdCBkcmFmdC1saS1xdWljLW9wdGltaXppbmctYWNrLWluLXdsYW4tMDAgbWVudGlvbnMg
dXNpbmcgb25lIHdheSBkZWxheSBtZWFzdXJlbWVudHMuIElzIHRoYXQgYSByZWZlcmVuY2UgdG8g
ZHJhZnQtaHVpdGVtYS1xdWljLXRzLTAwID8NCg0KLS0gQ2hyaXN0aWFuIEh1aXRlbWENCk9uIDcv
Ni8yMDIwIDc6MzUgQU0sIEthbmdqaWFvIHdyb3RlOg0KDQpEZWFyIE1hcnRpbiwNCg0KDQoNCkhl
cmUgYXJlIHRoZSB0d28gZHJhZnRzOg0KDQpkcmFmdC1saS1xdWljLW9wdGltaXppbmctYWNrLWlu
LXdsYW4tMDA6IGh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1saS1xdWljLW9wdGlt
aXppbmctYWNrLWluLXdsYW4tMDANCg0KZHJhZnQtaXllbmdhci1xdWljLWRlbGF5ZWQtYWNrLTAw
OiBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaXllbmdhci1xdWljLWRlbGF5ZWQt
YWNrLTAwDQoNCg0KDQpJIGhhdmUgb3V0bGluZWQgc29tZSBkaXN0aW5jdGlvbiBhbmQgY29ubmVj
dGlvbiBiZXR3ZWVuIHRoZXNlIHR3byBkcmFmdHM6DQoNCg0KDQphKSAgICAgICBCb3RoIGRyYWZ0
LWxpLXF1aWMtb3B0aW1pemluZy1hY2staW4td2xhbi0wMCBhbmQgZHJhZnQtaXllbmdhci1xdWlj
LWRlbGF5ZWQtYWNrLTAwIHByb3Bvc2UgYSBzb2x1dGlvbiB0byByZWR1Y2UgdGhlIEFDSyBmcmVx
dWVuY3kgZm9yIFFVSUMuIGRyYWZ0LWl5ZW5nYXItcXVpYy1kZWxheWVkLWFjay0wMCBtYWtlcyB0
aGUgdHdvIHBhcmFtZXRlcnMgaW4gZGVsYXllZCBBQ0ssIGkuZS4sICJQYWNrZXQgVG9sZXJhbmNl
IiBhbmQgIk1heCBBY2sgRGVsYXkiLCBiZSB0dW5hYmxlIGJ5IHRoZSBzZW5kZXIuIFRoZXNlIHR3
byB0dW5hYmxlIHBhcmFtZXRlcnMgZG8gbm90IGluY2x1ZGUgUlRUIGFzIGEgZmFjdG9yLiBTYXJh
IExhbmRzdHJvbSBldCBhbC4gWzFdIGhhcyBkZW1vbnN0cmF0ZWQgdGhhdCwgaW4gdGhlb3J5LCB0
aGUgZW5kcG9pbnQgc2hvdWxkIGFja25vd2xlZGdlIGRhdGEgYXQgbGVhc3QgdHdpY2UgcGVyIHNl
bmQgd2luZG93IChSVFQpIHRvIGVuc3VyZSB1dGlsaXphdGlvbi4gSW4gdGhpcyBjYXNlLCByZWR1
Y2luZyBBQ0sgZnJlcXVlbmN5IHdpdGhvdXQgY29uc2lkZXJpbmcgdGhlIFJUVCBhcyBhIGZhY3Rv
ciBvZiBNYXggQWNrIERlbGF5LCBtaWdodCBjYXVzZSBwZXJmb3JtYW5jZSBpc3N1ZXMuIE9uIHRo
ZSBvdGhlciBoYW5kLCB0aGUgcHVycG9zZSBpbiBkcmFmdC1saS1xdWljLW9wdGltaXppbmctYWNr
LWluLXdsYW4tMDAgaXMgdG8gbWluaW1pemUgdGhlIEFDSyBmcmVxdWVuY3kgcmVxdWlyZWQgYnkg
dGhlIHRyYW5zcG9ydCwgdGh1cyB0aGUgQUNLIGZyZXF1ZW5jeSBpcyBjb21wdXRlZCBhcyBNSU57
YncvKHBhY2tldF90b2xlcmFuY2UgKm1heF9wYWNrZXRfc2l6ZSksIGJldGEvUlRUbWlufSAoYmV0
YSBpbmRpY2F0ZXMgdGhlIG51bWJlciBvZiBBQ0tzIHBlciBSVFQpLiBXaGlsZSBkcmFmdC1peWVu
Z2FyLXF1aWMtZGVsYXllZC1hY2stMDAgYWRvcHRzIHRoZSBleHRlbmRlZCBkZWxheWVkIEFDSyBh
cyBzcGVjaWZpZWQgaW4gdGhlIGxlZ2FjeSBUQ1AsIHdob3NlIEFDSyBmcmVxdWVuY3kgaXMgY29t
cHV0ZWQgYXMgTUFYe2J3LyggcGFja2V0X3RvbGVyYW5jZSAqbWF4X3BhY2tldF9zaXplKSwgMS8g
bWF4X2Fja19kZWxheX0uIEEgcGFwZXIgWzJdICh0byBiZSBhcHBlYXJlZCBpbiBTSUdDT01NMjAy
MCkgaGFzIGRlbW9uc3RyYXRlZCB0aGF0IHVzaW5nIGEgTUlOIGluc3RlYWQgb2YgYSBNQVggY2Fu
IGFsc28gYWNoaWV2ZSBlcXVhbGx5IGdvb2QgcGVyZm9ybWFuY2UuDQoNCg0KDQpiKSAgICAgICBk
cmFmdC1peWVuZ2FyLXF1aWMtZGVsYXllZC1hY2stMDAgcHJvdmlkZXMgYSB3YXkgZm9yIHRoZSBz
ZW5kZXIgdG8gY3VzdG9taXplIHRoZSBBQ0sgZnJlcXVlbmN5LiBUaGlzIG1lYW5zIHRoZSBBQ0tz
IG1pZ2h0IGJlIGV4Y2Vzc2l2ZWx5IGRlbGF5ZWQgd2hlbiB0aGUgTWF4IEFjayBEZWxheSBpcyBs
YXJnZS4gV2hlbiBzZW5kaW5nIGZld2VyIEFDSyBmcmFtZXMsIG1hbnkgZGF0YSBwYWNrZXRzIG1p
Z2h0IGJlIHJlY2VpdmVkIGR1cmluZyB0aGUgQUNLIGludGVydmFsLCBnZW5lcmF0aW5nIG9ubHkg
b25lIFJUVCBzYW1wbGUgYW1vbmcgbXVsdGlwbGUgcGFja2V0cyBpcyBsaWtlbHkgdG8gcmVzdWx0
IGluIGJpYXNlcy4gRm9yIGV4YW1wbGUsIGEgbGFyZ2VyIG1pbmltdW0gUlRUIGVzdGltYXRlLiBJ
biBkcmFmdC1saS1xdWljLW9wdGltaXppbmctYWNrLWluLXdsYW4tMDAsIHdlIHByb3Bvc2UgYSBv
bmUtd2F5LWRlbGF5LWJhc2VkIG1ldGhvZCB0byBjb21wdXRlIHRoZSBtaW5pbXVtIFJUVCBtb3Jl
IGFjY3VyYXRlbHkuIEFwYXJ0IGZyb20gdGhlIEFDSyBzY2hlbWUsIHRoaXMgaXMgYW5vdGhlciBw
b2ludCB0aGF0IHdlIHdvdWxkIGxpa2UgdG8gZGlzY3VzcyBhbmQgZ2V0IGZlZWRiYWNrIGZyb20g
UVVJQyBXRy4NCg0KDQoNCmMpICAgICAgIFdpdGggc29tZSBtaW5vciBleHRlbnNpb25zIHN1Y2gg
YXMgYWRkaW5nIG9uZSBtb3JlIGZpZWxkIG9mIEFDSy1JTlRFTlNJVFksIHRoZSBwcm9wb3NlZCBB
Q0sgc2NoZW1lIGluIGRyYWZ0LWxpLXF1aWMtb3B0aW1pemluZy1hY2staW4td2xhbi0wMCBtYXkg
YmUgYWJsZSB0byByZXVzZSB0aGUgQUNLLUZFUVVFTkNZIGZyYW1lIHNwZWNpZmllZCBpbiBkcmFm
dC1peWVuZ2FyLXF1aWMtZGVsYXllZC1hY2stMDAgdG8gc3luYyB0aGUgQUNLIGludGVuc2l0eSBi
ZXR3ZWVuIHNlbmRlciBhbmQgcmVjZWl2ZXIuDQoNCg0KDQpTb21lIHJlZmVyZW5jZSBtZW50aW9u
ZWQgYWJvdmU6DQoNClsxXSBTYXJhIExhbmRzdHJvbSBhbmQgTGFycy1Ba2UgTGFyem9uLiAyMDA3
LiBSZWR1Y2luZyB0aGUgVENQIGFja25vd2xlZGdtZW50IGZyZXF1ZW5jeS4gQUNNIFNJR0NPTU0g
Q0NSIDM3LCAzICgyMDA3KSwgNeKAkzE2Lg0KDQpbMl0gVG9uZyBMaSwgS2FpIFpoZW5nLCBLZSBY
dSwgUmFodWwgQXJ2aW5kIEphZGhhdiwgVGFvIFhpb25nLCBLZWl0aCBXaW5zdGVpbiwgS3VuIFRh
bi4gIlRBQ0s6IEltcHJvdmluZyBXaXJlbGVzcyBUcmFuc3BvcnQgUGVyZm9ybWFuY2UgYnkgVGFt
aW5nIEFja25vd2xlZGdtZW50cyIsIEFDTSBTSUdDT01NLCAyMDIwLiAoIGh0dHA6Ly93d3cudGh1
Y3NuZXQub3JnL3VwbG9hZHMvMi81LzIvOC8yNTI4OTc5NS90b25nX3NpZ2NvbW0yMC5wZGYgKQ0K
DQoNCg0KQmVzdCBSZWdhcmRzLA0KDQpKaWFvDQoNCg0KDQotLS0tLU9yaWdpbmFsIE1lc3NhZ2Ut
LS0tLQ0KRnJvbTogUVVJQyBbbWFpbHRvOnF1aWMtYm91bmNlc0BpZXRmLm9yZ10gT24gQmVoYWxm
IE9mIE1hcnRpbiBUaG9tc29uDQpTZW50OiBNb25kYXksIEp1bHkgNiwgMjAyMCA4OjQxIEFNDQpU
bzogcXVpY0BpZXRmLm9yZzxtYWlsdG86cXVpY0BpZXRmLm9yZz4NClN1YmplY3Q6IFJlOiBIb3Bl
IGEgZGlzY3Vzc2lvbiBmb3IgZHJhZnQtbGktcXVpYy1vcHRpbWl6aW5nLWFjay1pbi13bGFuLTAw
DQoNCg0KDQpDYW4geW91IHNwZWFrIGEgbGl0dGxlIGFib3V0IHRoZSByZWxhdGlvbnNoaXAgd2l0
aCBkcmFmdC1peWVuZ2FyLXF1aWMtZGVsYXllZC1hY2sgPw0KDQoNCg0KT24gU2F0LCBKdWwgNCwg
MjAyMCwgYXQgMTY6MDUsIEthbmdqaWFvIHdyb3RlOg0KDQo+DQoNCj4gRGVhciBRVUlDIFdHIG1l
bWJlcnMsDQoNCj4NCg0KPg0KDQo+IFdlIHVwbG9hZGVkIGEgZHJhZnQgZGVzY3JpYmluZyBhIG1l
Y2hhbmlzbSBmb3IgQUNLIG9wdGltaXphdGlvbiB0bw0KDQo+IFFVSUMgZ3JvdXAuIFRoZSBsaW5r
IGlzDQoNCj4gaHR0cHM6Ly9kYXRhdHJhY2tlci5pZXRmLm9yZy9kb2MvZHJhZnQtbGktcXVpYy1v
cHRpbWl6aW5nLWFjay1pbi13bGFuLy4uDQoNCj4gVGhpcyBzb2x1dGlvbiBjb21lcyBmcm9tIG91
ciBwcmFjdGljZSBhbmQgdGhlIHJlc3VsdHMgc2hvdyBpdCBpcyBhDQoNCj4gZ29vZCByZXBsYWNl
bWVudCBvZiB0aGUgdHJhZGl0aW9uYWwgQUNLIG1lY2hhbmlzbSB0byBjb21wZW5zYXRlIGZvcg0K
DQo+IHNjZW5hcmlvcyB3aGVyZSB0aGUgYWNrbm93bGVkZ2VtZW50IG92ZXJoZWFkIGlzIG5vbi1u
ZWdsaWdpYmxlIChpLmUuLA0KDQo+IHdpcmVsZXNzIHNjZW5hcmlvcykuDQoNCj4NCg0KPg0KDQo+
IFRoZSBrZXkgcG9pbnRzIGZvciB0aGlzIHNvbHV0aW9uIGNhbiBiZToNCg0KPg0KDQo+DQoNCj4g
MS4gV2UgY29uY2x1ZGUgdGhlIGZvcm11bGEgb2YgdGhlIG1pbmltdW0gQUNLIGludGVuc2l0eSBy
ZXF1aXJlZCBmb3INCg0KPiBRVUlDIHRyYW5zcG9ydC4NCg0KPg0KDQo+DQoNCj4gMi4gSW4gb3Jk
ZXIgdG8gYWxsZXZpYXRlIHRoZSBlcnJvciBpbiBSVFQgZXN0aW1hdGlvbiwgd2UgdXNlIHByb3Rv
Y29sDQoNCj4gZXh0ZW5zaW9ucyBhbmQgYSBvbmUtd2F5IGRlbGF5IGZhY3Rvci4gV2UgdGhpbmsg
dGhpcyByb3VuZC10cmlwIHRpbWluZw0KDQo+IG1ldGhvZCBjYW4gYWxzbyBiZSBhcHBsaWNhYmxl
IGZvciB0aGUgYWNrIHRoaW5uaW5nIG1lY2hhbmlzbXMgKHN1Y2ggYXMNCg0KPiDigJ1DaGFuZ2lu
ZyB0aGUgRGVmYXVsdCBRVUlDIEFDSyBQb2xpY3nigJ0gIzM1MjkpIHRoYXQgaGF2ZSBiZWVuIGRp
c2N1c3NlZA0KDQo+IGluIFFVSUMgZ3JvdXAuLg0KDQo+DQoNCj4NCg0KPiAzLiBGb3IgaW1wbGVt
ZW50YXRpb24gYW5kIGludGVyb3BlcmFiaWxpdHksIHdlIGRlZmluZSBhIG5ldw0KDQo+IEFDSy1J
TlRFTlNJVFkgRnJhbWUgaW4gd2hpY2ggQUNLIEludGVuc2l0eSBpcyBzZXQuIEFDSyBJbnRlbnNp
dHkgaXMgYQ0KDQo+IHZhcmlhYmxlLWxlbmd0aCBpbnRlZ2VyIGluZGljYXRpbmcgdGhlIHVwZGF0
ZWQgaW50ZW5zaXR5IG9mIFFVSUMgQUNLDQoNCj4gRnJhbWUgY2FsY3VsYXRlZCBieSBvdXIgZm9y
bXVsYS4NCg0KPg0KDQo+DQoNCj4gV2UgbG9vayBmb3J3YXJkIHRvIHlvdXIgdmFsdWFibGUgY29t
bWVudHMgYW5kIHN1Z2dlc3Rpb25zLiBUaGFua3MuDQoNCj4NCg0KPg0KDQo+IFNpbmNlcmVseSwN
Cg0KPg0KDQo+IEppYW8NCg0KPg0KDQoNCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
5a6L5L2TOw0KCXBhbm9zZS0xOjIgMSA2IDAgMyAxIDEgMSAxIDE7fQ0KQGZvbnQtZmFjZQ0KCXtm
b250LWZhbWlseToiQ2FtYnJpYSBNYXRoIjsNCglwYW5vc2UtMToyIDQgNSAzIDUgNCA2IDMgMiA0
O30NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6Q2FsaWJyaTsNCglwYW5vc2UtMToyIDE1IDUg
MiAyIDIgNCAzIDIgNDt9DQpAZm9udC1mYWNlDQoJe2ZvbnQtZmFtaWx5OiJcQOWui+S9kyI7DQoJ
cGFub3NlLTE6MiAxIDYgMCAzIDEgMSAxIDEgMTt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0K
cC5Nc29Ob3JtYWwsIGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0K
CW1hcmdpbi1ib3R0b206LjAwMDFwdDsNCgl0ZXh0LWFsaWduOmp1c3RpZnk7DQoJdGV4dC1qdXN0
aWZ5OmludGVyLWlkZW9ncmFwaDsNCglmb250LXNpemU6MTAuNXB0Ow0KCWZvbnQtZmFtaWx5OiJD
YWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0
eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOiMwNTYzQzE7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVy
bGluZTt9DQphOnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxl
LXByaW9yaXR5Ojk5Ow0KCWNvbG9yOiM5NTRGNzI7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGlu
ZTt9DQpwLk1zb1BsYWluVGV4dCwgbGkuTXNvUGxhaW5UZXh0LCBkaXYuTXNvUGxhaW5UZXh0DQoJ
e21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoi57qv5paH5pysIENoYXIi
Ow0KCW1hcmdpbjowY207DQoJbWFyZ2luLWJvdHRvbTouMDAwMXB0Ow0KCXRleHQtYWxpZ246bGVm
dDsNCglmb250LXNpemU6MTAuNXB0Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlm
O30NCnANCgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRv
Ow0KCW1hcmdpbi1yaWdodDowY207DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFy
Z2luLWxlZnQ6MGNtOw0KCXRleHQtYWxpZ246anVzdGlmeTsNCgl0ZXh0LWp1c3RpZnk6aW50ZXIt
aWRlb2dyYXBoOw0KCWZvbnQtc2l6ZToxMC41cHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNh
bnMtc2VyaWY7fQ0Kc3Bhbi5DaGFyDQoJe21zby1zdHlsZS1uYW1lOiLnuq/mlofmnKwgQ2hhciI7
DQoJbXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1zdHlsZS1saW5rOue6r+aWh+acrDsNCglm
b250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpzcGFuLkVtYWlsU3R5bGUyMA0KCXtt
c28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fu
cy1zZXJpZjsNCgljb2xvcjojMUY0OTdEO30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10
eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24x
DQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgOTAuMHB0IDcyLjBwdCA5
MC4wcHQ7fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQovKiBMaXN0
IERlZmluaXRpb25zICovDQpAbGlzdCBsMA0KCXttc28tbGlzdC1pZDoxMzc5NzQxMDM0Ow0KCW1z
by1saXN0LXR5cGU6aHlicmlkOw0KCW1zby1saXN0LXRlbXBsYXRlLWlkczotMTY3Mzc3MTY5NCAt
MTY2Mjc2MjY0OCA2NzY5ODcxMyA2NzY5ODcxNSA2NzY5ODcwMyA2NzY5ODcxMyA2NzY5ODcxNSA2
NzY5ODcwMyA2NzY5ODcxMyA2NzY5ODcxNTt9DQpAbGlzdCBsMDpsZXZlbDENCgl7bXNvLWxldmVs
LW51bWJlci1mb3JtYXQ6YWxwaGEtbG93ZXI7DQoJbXNvLWxldmVsLXRleHQ6IiUxXCkiOw0KCW1z
by1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsN
CgltYXJnaW4tbGVmdDoyOC41cHQ7DQoJdGV4dC1pbmRlbnQ6LTE4LjBwdDt9DQpAbGlzdCBsMDps
ZXZlbDINCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YWxwaGEtbG93ZXI7DQoJbXNvLWxldmVs
LXRleHQ6IiUyXCkiOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1i
ZXItcG9zaXRpb246bGVmdDsNCgltYXJnaW4tbGVmdDo1Mi41cHQ7DQoJdGV4dC1pbmRlbnQ6LTIx
LjBwdDt9DQpAbGlzdCBsMDpsZXZlbDMNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6cm9tYW4t
bG93ZXI7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3Np
dGlvbjpyaWdodDsNCgltYXJnaW4tbGVmdDo3My41cHQ7DQoJdGV4dC1pbmRlbnQ6LTIxLjBwdDt9
DQpAbGlzdCBsMDpsZXZlbDQNCgl7bXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVs
LW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCW1hcmdpbi1sZWZ0Ojk0LjVwdDsNCgl0ZXh0LWluZGVu
dDotMjEuMHB0O30NCkBsaXN0IGwwOmxldmVsNQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDph
bHBoYS1sb3dlcjsNCgltc28tbGV2ZWwtdGV4dDoiJTVcKSI7DQoJbXNvLWxldmVsLXRhYi1zdG9w
Om5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCW1hcmdpbi1sZWZ0OjEx
NS41cHQ7DQoJdGV4dC1pbmRlbnQ6LTIxLjBwdDt9DQpAbGlzdCBsMDpsZXZlbDYNCgl7bXNvLWxl
dmVsLW51bWJlci1mb3JtYXQ6cm9tYW4tbG93ZXI7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7
DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjpyaWdodDsNCgltYXJnaW4tbGVmdDoxMzYuNXB0
Ow0KCXRleHQtaW5kZW50Oi0yMS4wcHQ7fQ0KQGxpc3QgbDA6bGV2ZWw3DQoJe21zby1sZXZlbC10
YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgltYXJnaW4t
bGVmdDoxNTcuNXB0Ow0KCXRleHQtaW5kZW50Oi0yMS4wcHQ7fQ0KQGxpc3QgbDA6bGV2ZWw4DQoJ
e21zby1sZXZlbC1udW1iZXItZm9ybWF0OmFscGhhLWxvd2VyOw0KCW1zby1sZXZlbC10ZXh0OiIl
OFwpIjsNCgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0
aW9uOmxlZnQ7DQoJbWFyZ2luLWxlZnQ6MTc4LjVwdDsNCgl0ZXh0LWluZGVudDotMjEuMHB0O30N
CkBsaXN0IGwwOmxldmVsOQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpyb21hbi1sb3dlcjsN
Cgltc28tbGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOnJp
Z2h0Ow0KCW1hcmdpbi1sZWZ0OjE5OS41cHQ7DQoJdGV4dC1pbmRlbnQ6LTIxLjBwdDt9DQpvbA0K
CXttYXJnaW4tYm90dG9tOjBjbTt9DQp1bA0KCXttYXJnaW4tYm90dG9tOjBjbTt9DQotLT48L3N0
eWxlPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRp
dCIgc3BpZG1heD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5
XT48eG1sPg0KPG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVk
aXQiIGRhdGE9IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hl
YWQ+DQo8Ym9keSBsYW5nPSJaSC1DTiIgbGluaz0iIzA1NjNDMSIgdmxpbms9IiM5NTRGNzIiPg0K
PGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxh
bmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6YmxhY2siPkhpIENocmlzdGlhbiw8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9
ImNvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBhbGlnbj0ibGVmdCIgc3R5bGU9InRleHQtYWxpZ246bGVmdDtsaW5lLWhlaWdodDox
NTAlIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOmJsYWNrIj5RdWVzdGlvbiAxOg0K
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgYWxpZ249ImxlZnQi
IHN0eWxlPSJ0ZXh0LWFsaWduOmxlZnQ7bGluZS1oZWlnaHQ6MTUwJSI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJjb2xvcjpibGFjayI+V2UgaGF2ZSBhIHVkcC1iYXNlZCBzaW11bGF0aW9uIHRv
b2wgaW4gZ2l0aHViICgNCjxhIGhyZWY9Imh0dHBzOi8vZ2l0aHViLmNvbS9maWxsdGhlcGlwZS9h
Y2tlbXUiPjxzcGFuIHN0eWxlPSJjb2xvcjpibGFjayI+aHR0cHM6Ly9naXRodWIuY29tL2ZpbGx0
aGVwaXBlL2Fja2VtdTwvc3Bhbj48L2E+ICkuIFlvdSBjYW4gYWxzbyBkaXJlY3RseSByZWZlciB0
byBGaWd1cmUgOShiKSBpbiB0aGUgcGFwZXIgWzJdIGZvciB0aGUgc2ltdWxhdGlvbiByZXN1bHRz
LiBBbiBhY2tub3dsZWRnZW1lbnQgcG9saWN5IHRoYXQgc2VuZHMgbGVzcyBBQ0tzDQogYWNoaWV2
ZXMgaGlnaGVyIHRob3VnaHB1dC4gQWxzbyB0aGUgcG9saWN5IHByb3Bvc2VkIGluIGRyYWZ0LWxp
LXF1aWMtb3B0aW1pemluZy1hY2staW4td2xhbi0wMCBhcHByb2FjaGVzIHRoZSB0cmFuc3BvcnQg
dXBwZXIgYm91bmQgd2l0aCBhIG1pbmltaXplZCBBQ0sgZnJlcXVlbmN5ICg4MDIuMTFuKS48bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibGluZS1oZWlnaHQ6MTUwJSI+PHNwYW4gbGFuZz0iRU4t
VVMiIHN0eWxlPSJjb2xvcjpibGFjayI+UXVlc3Rpb24gMjo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibGluZS1oZWlnaHQ6MTUwJSI+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJjb2xvcjpibGFjayI+Q29tcGFyaW5nIHRvIGRyYWZ0LWl5ZW5nYXIt
cXVpYy1kZWxheWVkLWFjay0wMCwgaWYgdGhlIGRlbGF5IGlzIHNldCB0byBhIGZyYWN0aW9uIG9m
IHRoZSBSVFQsIHdlIHRoaW5rIHRoZSBkaWZmZXJlbmNlIG1pZ2h0IGJlIHRoYXQ6PG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9InRleHQtaW5kZW50OjE1
Ljc1cHQ7bGluZS1oZWlnaHQ6MTUwJSI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjpi
bGFjayI+Rm9yIGRyYWZ0LWl5ZW5nYXItcXVpYy1kZWxheWVkLWFjay0wMCwgQUNLIGZyZXF1ZW5j
eSBpcyBjb21wdXRlZCBhczoNCjxiPk1BWDwvYj57YncvKCBwYWNrZXRfdG9sZXJhbmNlICptYXhf
cGFja2V0X3NpemUpLCAxLyBtYXhfYWNrX2RlbGF5fS4gPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9InRleHQtaW5kZW50OjE1Ljc1cHQ7bGluZS1oZWln
aHQ6MTUwJSI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjpibGFjayI+Rm9yIGRyYWZ0
LWxpLXF1aWMtb3B0aW1pemluZy1hY2staW4td2xhbi0wMCwgQUNLIGZyZXF1ZW5jeSBpcyBjb21w
dXRlZCBhczoNCjxiPk1JTjwvYj57YncvKHBhY2tldF90b2xlcmFuY2UgKm1heF9wYWNrZXRfc2l6
ZSksIGJldGEvUlRUbWlufSAoYmV0YSBpbmRpY2F0ZXMgdGhlIG51bWJlciBvZiBBQ0tzIHBlciBS
VFQsIFJUVC80IGlzIHJlY29tbWVuZGVkIGluIG91ciBzb2x1dGlvbikuDQo8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibGluZS1oZWlnaHQ6MTUwJSI+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjpibGFjayI+SW4gcHJhY3RpY2UsIHdlIGhh
dmUgcHJvdmVkIHRoYXQgdXNpbmcgYQ0KPGI+TUlOPC9iPiBpbnN0ZWFkIG9mIGEgPGI+TUFYPC9i
PiBjYW4gYWxzbyBhY2hpZXZlIGVxdWFsbHkgZ29vZCBwZXJmb3JtYW5jZS4gPG86cD4NCjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5
bGU9ImNvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOmJsYWNrIj5RdWVzdGlv
biAzOiA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBs
YW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9y
OmJsYWNrIj5JbiBkZWxheWVkIEFDSywgdHJhZGl0aW9uYWwgUlRUIGNhbGN1bGF0aW9uIG1lZXRz
IHRoZSBjaGFsbGVuZ2Ugb2YgYmlhc2VzIGZvciB0aGUgc2VuZGVyIGNhbiBoYXJkbHkgZ2VuZXJh
dGUgcGVyLXBhY2tldCBSVFQgc2FtcGxlczo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpw
PiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0idGV4
dC1pbmRlbnQ6MTUuNzVwdCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjpibGFjayI+
VGhlIGFsZ29yaXRobSBpbiBkcmFmdC1odWl0ZW1hLXF1aWMtdHMtMDAgaXMgaW50ZXJlc3Rpbmcu
IElmIG15IHVuZGVyc3RhbmRpbmcgaXMgcmlnaHQsIHRoZSBPV0QgaXMgY29tcHV0ZWQgYWxsIG9u
IHNlbmRlciBzaWRlIGFuZCB0aGUgZm9ybXVsYXMgaW5jbHVkZTo8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0idGV4dC1pbmRlbnQ6MTUuNzVwdCI+PHNw
YW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjpibGFjayI+PG86cD4mbmJzcDs8L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9InRleHQtaW5kZW50OjE1Ljc1cHQ7
bGluZS1oZWlnaHQ6MTUwJSI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjpibGFjayI+
bGF0ZXN0X09XRCA9IHQzIChsYXJnZXN0IGFja2VkIHBhY2tldCBhcnJpdmFsKSDigJMgdDEgKGxh
cmdlc3QgYWNrZWQgcGFja2V0IGRlcGFydHVyZSkgLSBwaGFzZV9zaGlmdC48bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0idGV4dC1pbmRlbnQ6MTUuNzVw
dDtsaW5lLWhlaWdodDoxNTAlIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOmJsYWNr
Ij5waGFzZV9zaGlmdCA9IHQzIChsYXJnZXN0IGFja2VkIHBhY2tldCBhcnJpdmFsKSDigJMgdDEg
KGxhcmdlc3QgYWNrZWQgcGFja2V0IGRlcGFydHVyZSkgLSBsYXRlc3RfcnR0LzINCjxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iY29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJ0ZXh0LWluZGVudDoxNS43NXB0Ij48c3BhbiBsYW5nPSJFTi1V
UyIgc3R5bGU9ImNvbG9yOmJsYWNrIj5Gb3IgZHJhZnQtbGktcXVpYy1vcHRpbWl6aW5nLWFjay1p
bi13bGFuLTAwLCBSVFRtaW4gaXMgYSBmYWN0b3IgdXNlZCB0byB1cGRhdGUgQUNLIGludGVuc2l0
eS4gSW4gb3JkZXIgdG8gaW1wcm92ZSBhY2N1cmFjeSwgd2UgYWRvcHQgT1dELWJhc2VkIFJUVG1p
biBlc3RpbWF0aW9uIGluc3RlYWQNCiBvZiByZXBvcnRpbmcgQUNLIGRlbGF5cyBmb3IgdGhlIGxh
cmdlc3QgYWNrbm93bGVkZ2VkIHBhY2tldCBpbiBBQ0sgZnJhbWUgaW4gUVVJQyBwcm90b2NvbC4g
VGhlIGZvcm11bGFzIGluY2x1ZGU6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9InRleHQtaW5kZW50OjE1Ljc1cHQiPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iY29sb3I6YmxhY2siPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJ0ZXh0LWluZGVudDoxNS43NXB0O2xpbmUtaGVpZ2h0OjE1MCUi
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iY29sb3I6YmxhY2siPlJUVG1pbl9zYW1wbGUgPSB0
MiAoQUNLIGFycml2YWwpIOKAkyB0MSAocGFja2V0IHdpdGggT1dEbWluIGRlcGFydHVyZSkgLSBk
ZWx0YV90IChBQ0sgRGVsYXkpJm5ic3A7Jm5ic3A7IC0tLS0gb24gc2VuZGVyIHNpZGU8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0idGV4dC1pbmRlbnQ6
MTUuNzVwdDtsaW5lLWhlaWdodDoxNTAlIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9y
OmJsYWNrIj5kZWx0YV90ID0gdDMgKHBhY2tldCB3aXRoIE9XRG1pbiBhcnJpdmFsKSDigJMgdDQg
KEFDSyBkZXBhcnR1cmUpJm5ic3A7Jm5ic3A7IC0tLSBvbiByZWNlaXZlciBzaWRlICggSWYgdGhl
IHJlY2VpdmVyIGNhbiBzZW5kIHQzIGFuZCB0NCB0byB0aGUgc2VuZGVyLCBkZWx0YV90IGNhbiBh
bHNvDQogYmUgY2FsY3VsYXRlZCBvbiBzZW5kZXIgc2lkZS4pPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjpi
bGFjayI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjpibGFjayI+Rm9yIG1vcmUgZGV0YWlscywg
cGxlYXNlIHJlZmVyIHRvIG91ciBwYXBlciBhbmQgZHJhZnQuIFRoYW5rcyAmbmJzcDs8bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIg
c3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48c3BhbiBsYW5nPSJFTi1VUyIgc3R5bGU9ImNvbG9yOmJsYWNrIj5TaW5j
ZXJlbHksPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
bGFuZz0iRU4tVVMiIHN0eWxlPSJjb2xvcjpibGFjayI+Smlhbzwvc3Bhbj48c3BhbiBsYW5nPSJF
Ti1VUyIgc3R5bGU9ImNvbG9yOiMxRjQ5N0QiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+
DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7
cGFkZGluZzozLjBwdCAwY20gMGNtIDBjbSI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBhbGlnbj0i
bGVmdCIgc3R5bGU9InRleHQtYWxpZ246bGVmdCI+PGI+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxl
PSJmb250LXNpemU6MTEuMHB0Ij5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0
eWxlPSJmb250LXNpemU6MTEuMHB0Ij4gQ2hyaXN0aWFuIEh1aXRlbWEgW21haWx0bzpodWl0ZW1h
QGh1aXRlbWEubmV0XQ0KPGJyPg0KPGI+U2VudDo8L2I+IFR1ZXNkYXksIEp1bHkgNywgMjAyMCA1
OjA3IEFNPGJyPg0KPGI+VG86PC9iPiBLYW5namlhbyAmbHQ7a2FuZ2ppYW9AaHVhd2VpLmNvbSZn
dDs7IE1hcnRpbiBUaG9tc29uICZsdDttdEBsb3dlbnRyb3B5Lm5ldCZndDs8YnI+DQo8Yj5DYzo8
L2I+IHF1aWNAaWV0Zi5vcmc8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IEhvcGUgYSBkaXNjdXNz
aW9uIGZvciBkcmFmdC1saS1xdWljLW9wdGltaXppbmctYWNrLWluLXdsYW4tMDA8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgYWxpZ249
ImxlZnQiIHN0eWxlPSJ0ZXh0LWFsaWduOmxlZnQiPjxzcGFuIGxhbmc9IkVOLVVTIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8cD48c3BhbiBsYW5nPSJFTi1VUyI+SGVsbG8gSmlhbyw8
L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTIuMHB0Ij48bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cD48c3BhbiBsYW5nPSJFTi1VUyI+WW91ciBkcmFmdCBpcyBtb3Rp
dmF0ZWQgYnkgc3BlY2lmaWMgZGF0YSBhYm91dCBydW5uaW5nIGhpZ2ggYmFuZHdpZHRoIGFwcGxp
Y2F0aW9ucyBvdmVyIHdpcmVsZXNzIGxvY2FsIGFyZWEgbmV0d29yay4gSXQgd291bGQgYmUgaW50
ZXJlc3RpbmcgdG8gY29tcGFyZSBiZWhhdmlvciBvZiB0aGVzZSBhcHBsaWNhdGlvbnMgdXNpbmcg
ZGlmZmVyZW50IGFja25vd2xlZGdlbWVudCBwb2xpY2llcywgcHJvYmFibHkgdXNpbmcNCiBzaW11
bGF0aW9ucy4gRG8geW91IGhhdmUgZGVmaW5pdGlvbnMgb2YgdGhlIGFwcGxpY2F0aW9uIGFuZCBv
ZiB0aGUgV0xBTiB0aGF0IHdlIGNvdWxkIGVudGVyIGluIHNpbXVsYXRpb25zPzxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwPjxzcGFuIGxhbmc9IkVOLVVTIj5UaGUgZHJhZnQgZHJhZnQtaXllbmdh
ci1xdWljLWRlbGF5ZWQtYWNrLTAwIHByb3ZpZGVzIGEgd2F5IGZvciBzZW5kZXJzIHRvIHNwZWNp
ZnkgYm90aCB0aGUgbWF4aW11bSBkZWxheSBiZXR3ZWVuIGFja25vd2xlZGdlbWVudHMgYW5kIHRo
ZSBtYXhpbXVtIG51bWJlciBvZiBwYWNrZXRzIGJldHdlZW4gYWNrbm93bGVkZ2VtZW50LCB3aXRo
IHJlY2VpdmVycyBzZW5kaW5nIGFja25vd2xlZGdlbWVudHMgd2hlbiBvbmUNCiBvZiB0aGUgY29u
ZGl0aW9ucyBpcyB0cnVlLiBTZXZlcmFsIHNlcnZlcnMgc2V0IHRoZSBkZWxheSB0byBhIGZyYWN0
aW9uIG9mIHRoZSBSVFQsIGFuZCB0aGUgbnVtYmVyIG9mIHBhY2tldHMgdG8gYSBjb3JyZXNwb25k
aW5nIGZyYWN0aW9uIG9mIHRoZSBudW1iZXIgb2YgcGFja2V0cyBwZXIgY29uZ2VzdGlvbiB3aW5k
b3cgLS0gUlRULzggaXMgb2Z0ZW4gc3VnZ2VzdGVkLiBIb3cgaXMgdGhhdCBkaWZmZXJlbnQgZnJv
bSBzZXR0aW5nIHRoZSAmcXVvdDtBQ0sNCiBpbnRlbnNpdHkmcXVvdDsgc3VnZ2VzdGVkIGluIGRy
YWZ0LWxpLXF1aWMtb3B0aW1pemluZy1hY2staW4td2xhbi0wMD88bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cD48c3BhbiBsYW5nPSJFTi1VUyI+VGhlIGRyYWZ0IGRyYWZ0LWxpLXF1aWMtb3B0aW1p
emluZy1hY2staW4td2xhbi0wMCBtZW50aW9ucyB1c2luZyBvbmUgd2F5IGRlbGF5IG1lYXN1cmVt
ZW50cy4gSXMgdGhhdCBhIHJlZmVyZW5jZSB0byBkcmFmdC1odWl0ZW1hLXF1aWMtdHMtMDAgPzxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwPjxzcGFuIGxhbmc9IkVOLVVTIj4tLSBDaHJpc3RpYW4g
SHVpdGVtYTxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBsYW5nPSJFTi1VUyI+T24gNy82LzIwMjAgNzozNSBBTSwgS2FuZ2ppYW8gd3JvdGU6
PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2lu
LXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQi
PjxzcGFuIGxhbmc9IkVOLVVTIj5EZWFyIE1hcnRpbiw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7PG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMi
PkhlcmUgYXJlIHRoZSB0d28gZHJhZnRzOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5kcmFmdC1saS1xdWljLW9wdGltaXpp
bmctYWNrLWluLXdsYW4tMDA6DQo8YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwv
ZHJhZnQtbGktcXVpYy1vcHRpbWl6aW5nLWFjay1pbi13bGFuLTAwIj5odHRwczovL3Rvb2xzLmll
dGYub3JnL2h0bWwvZHJhZnQtbGktcXVpYy1vcHRpbWl6aW5nLWFjay1pbi13bGFuLTAwPC9hPiAm
bmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3Bh
biBsYW5nPSJFTi1VUyI+ZHJhZnQtaXllbmdhci1xdWljLWRlbGF5ZWQtYWNrLTAwOiA8YSBocmVm
PSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtaXllbmdhci1xdWljLWRlbGF5ZWQt
YWNrLTAwIj4NCmh0dHBzOi8vdG9vbHMuaWV0Zi5vcmcvaHRtbC9kcmFmdC1peWVuZ2FyLXF1aWMt
ZGVsYXllZC1hY2stMDA8L2E+IDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Q
bGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+SSBoYXZlIG91dGxp
bmVkIHNvbWUgZGlzdGluY3Rpb24gYW5kIGNvbm5lY3Rpb24gYmV0d2VlbiB0aGVzZSB0d28gZHJh
ZnRzOjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFu
IGxhbmc9IkVOLVVTIj4mbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0IiBzdHlsZT0ibWFyZ2luLWxlZnQ6MjguNXB0O3RleHQtaW5kZW50Oi0xOC4wcHQ7
bXNvLWxpc3Q6bDAgbGV2ZWwxIGxmbzIiPg0KPCFbaWYgIXN1cHBvcnRMaXN0c10+PHNwYW4gbGFu
Zz0iRU4tVVMiPjxzcGFuIHN0eWxlPSJtc28tbGlzdDpJZ25vcmUiPmEpPHNwYW4gc3R5bGU9ImZv
bnQ6Ny4wcHQgJnF1b3Q7VGltZXMgTmV3IFJvbWFuJnF1b3Q7Ij4mbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsNCjwvc3Bhbj48L3NwYW4+PC9zcGFuPjwhW2VuZGlmXT48c3BhbiBs
YW5nPSJFTi1VUyI+Qm90aCBkcmFmdC1saS1xdWljLW9wdGltaXppbmctYWNrLWluLXdsYW4tMDAg
YW5kIGRyYWZ0LWl5ZW5nYXItcXVpYy1kZWxheWVkLWFjay0wMCBwcm9wb3NlIGEgc29sdXRpb24g
dG8gcmVkdWNlIHRoZSBBQ0sgZnJlcXVlbmN5IGZvciBRVUlDLiBkcmFmdC1peWVuZ2FyLXF1aWMt
ZGVsYXllZC1hY2stMDAgbWFrZXMgdGhlIHR3byBwYXJhbWV0ZXJzIGluIGRlbGF5ZWQNCiBBQ0ss
IGkuZS4sICZxdW90O1BhY2tldCBUb2xlcmFuY2UmcXVvdDsgYW5kICZxdW90O01heCBBY2sgRGVs
YXkmcXVvdDssIGJlIHR1bmFibGUgYnkgdGhlIHNlbmRlci4gVGhlc2UgdHdvIHR1bmFibGUgcGFy
YW1ldGVycyBkbyBub3QgaW5jbHVkZSBSVFQgYXMgYSBmYWN0b3IuIFNhcmEgTGFuZHN0cm9tIGV0
IGFsLiBbMV0gaGFzIGRlbW9uc3RyYXRlZCB0aGF0LCBpbiB0aGVvcnksIHRoZSBlbmRwb2ludCBz
aG91bGQgYWNrbm93bGVkZ2UgZGF0YSBhdCBsZWFzdCB0d2ljZSBwZXIgc2VuZA0KIHdpbmRvdyAo
UlRUKSB0byBlbnN1cmUgdXRpbGl6YXRpb24uIEluIHRoaXMgY2FzZSwgcmVkdWNpbmcgQUNLIGZy
ZXF1ZW5jeSB3aXRob3V0IGNvbnNpZGVyaW5nIHRoZSBSVFQgYXMgYSBmYWN0b3Igb2YgTWF4IEFj
ayBEZWxheSwgbWlnaHQgY2F1c2UgcGVyZm9ybWFuY2UgaXNzdWVzLiBPbiB0aGUgb3RoZXIgaGFu
ZCwgdGhlIHB1cnBvc2UgaW4gZHJhZnQtbGktcXVpYy1vcHRpbWl6aW5nLWFjay1pbi13bGFuLTAw
IGlzIHRvIG1pbmltaXplIHRoZQ0KIEFDSyBmcmVxdWVuY3kgcmVxdWlyZWQgYnkgdGhlIHRyYW5z
cG9ydCwgdGh1cyB0aGUgQUNLIGZyZXF1ZW5jeSBpcyBjb21wdXRlZCBhcyA8Yj4NCk1JTjwvYj57
YncvKHBhY2tldF90b2xlcmFuY2UgKm1heF9wYWNrZXRfc2l6ZSksIGJldGEvUlRUbWlufSAoYmV0
YSBpbmRpY2F0ZXMgdGhlIG51bWJlciBvZiBBQ0tzIHBlciBSVFQpLiBXaGlsZSBkcmFmdC1peWVu
Z2FyLXF1aWMtZGVsYXllZC1hY2stMDAgYWRvcHRzIHRoZSBleHRlbmRlZCBkZWxheWVkIEFDSyBh
cyBzcGVjaWZpZWQgaW4gdGhlIGxlZ2FjeSBUQ1AsIHdob3NlIEFDSyBmcmVxdWVuY3kgaXMgY29t
cHV0ZWQgYXMNCjxiPk1BWDwvYj57YncvKCBwYWNrZXRfdG9sZXJhbmNlICptYXhfcGFja2V0X3Np
emUpLCAxLyBtYXhfYWNrX2RlbGF5fS4gQSBwYXBlciBbMl0gKHRvIGJlIGFwcGVhcmVkIGluIFNJ
R0NPTU0yMDIwKSBoYXMgZGVtb25zdHJhdGVkIHRoYXQgdXNpbmcgYQ0KPGI+TUlOPC9iPiBpbnN0
ZWFkIG9mIGEgPGI+TUFYPC9iPiBjYW4gYWxzbyBhY2hpZXZlIGVxdWFsbHkgZ29vZCBwZXJmb3Jt
YW5jZS4gPG86cD4NCjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0IiBz
dHlsZT0ibWFyZ2luLWxlZnQ6MTAuNXB0O21zby1wYXJhLW1hcmdpbi1sZWZ0OjEuMGdkIj48c3Bh
biBsYW5nPSJFTi1VUyI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjI4LjVwdDt0ZXh0LWluZGVudDotMTguMHB0
O21zby1saXN0OmwwIGxldmVsMSBsZm8yIj4NCjwhW2lmICFzdXBwb3J0TGlzdHNdPjxzcGFuIGxh
bmc9IkVOLVVTIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3JlIj5iKTxzcGFuIHN0eWxlPSJm
b250OjcuMHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+Jm5ic3A7Jm5ic3A7Jm5ic3A7
Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwvc3Bhbj48IVtlbmRpZl0+PHNwYW4g
bGFuZz0iRU4tVVMiPmRyYWZ0LWl5ZW5nYXItcXVpYy1kZWxheWVkLWFjay0wMCBwcm92aWRlcyBh
IHdheSBmb3IgdGhlIHNlbmRlciB0byBjdXN0b21pemUgdGhlIEFDSyBmcmVxdWVuY3kuIFRoaXMg
bWVhbnMgdGhlIEFDS3MgbWlnaHQgYmUgZXhjZXNzaXZlbHkgZGVsYXllZCB3aGVuIHRoZSBNYXgg
QWNrIERlbGF5IGlzIGxhcmdlLiBXaGVuIHNlbmRpbmcgZmV3ZXIgQUNLIGZyYW1lcywNCiBtYW55
IGRhdGEgcGFja2V0cyBtaWdodCBiZSByZWNlaXZlZCBkdXJpbmcgdGhlIEFDSyBpbnRlcnZhbCwg
Z2VuZXJhdGluZyBvbmx5IG9uZSBSVFQgc2FtcGxlIGFtb25nIG11bHRpcGxlIHBhY2tldHMgaXMg
bGlrZWx5IHRvIHJlc3VsdCBpbiBiaWFzZXMuIEZvciBleGFtcGxlLCBhIGxhcmdlciBtaW5pbXVt
IFJUVCBlc3RpbWF0ZS4gSW4gZHJhZnQtbGktcXVpYy1vcHRpbWl6aW5nLWFjay1pbi13bGFuLTAw
LCB3ZSBwcm9wb3NlIGEgb25lLXdheS1kZWxheS1iYXNlZA0KIG1ldGhvZCB0byBjb21wdXRlIHRo
ZSBtaW5pbXVtIFJUVCBtb3JlIGFjY3VyYXRlbHkuIEFwYXJ0IGZyb20gdGhlIEFDSyBzY2hlbWUs
IHRoaXMgaXMgYW5vdGhlciBwb2ludCB0aGF0IHdlIHdvdWxkIGxpa2UgdG8gZGlzY3VzcyBhbmQg
Z2V0IGZlZWRiYWNrIGZyb20gUVVJQyBXRy48bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0IiBzdHlsZT0ibWFyZ2luLWxlZnQ6MTAuNXB0O21zby1wYXJhLW1hcmdp
bi1sZWZ0OjEuMGdkIj48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCIgc3R5bGU9Im1hcmdpbi1sZWZ0OjI4LjVwdDt0
ZXh0LWluZGVudDotMTguMHB0O21zby1saXN0OmwwIGxldmVsMSBsZm8yIj4NCjwhW2lmICFzdXBw
b3J0TGlzdHNdPjxzcGFuIGxhbmc9IkVOLVVTIj48c3BhbiBzdHlsZT0ibXNvLWxpc3Q6SWdub3Jl
Ij5jKTxzcGFuIHN0eWxlPSJmb250OjcuMHB0ICZxdW90O1RpbWVzIE5ldyBSb21hbiZxdW90OyI+
Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7DQo8L3NwYW4+PC9zcGFuPjwvc3Bh
bj48IVtlbmRpZl0+PHNwYW4gbGFuZz0iRU4tVVMiPldpdGggc29tZSBtaW5vciBleHRlbnNpb25z
IHN1Y2ggYXMgYWRkaW5nIG9uZSBtb3JlIGZpZWxkIG9mIEFDSy1JTlRFTlNJVFksIHRoZSBwcm9w
b3NlZCBBQ0sgc2NoZW1lIGluIGRyYWZ0LWxpLXF1aWMtb3B0aW1pemluZy1hY2staW4td2xhbi0w
MCBtYXkgYmUgYWJsZSB0byByZXVzZSB0aGUgQUNLLUZFUVVFTkNZIGZyYW1lIHNwZWNpZmllZCBp
biBkcmFmdC1peWVuZ2FyLXF1aWMtZGVsYXllZC1hY2stMDANCiB0byBzeW5jIHRoZSBBQ0sgaW50
ZW5zaXR5IGJldHdlZW4gc2VuZGVyIGFuZCByZWNlaXZlci48bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7PG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4t
VVMiPlNvbWUgcmVmZXJlbmNlIG1lbnRpb25lZCBhYm92ZTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+WzFdIFNhcmEgTGFu
ZHN0cm9tIGFuZCBMYXJzLUFrZSBMYXJ6b24uIDIwMDcuIFJlZHVjaW5nIHRoZSBUQ1AgYWNrbm93
bGVkZ21lbnQgZnJlcXVlbmN5LiBBQ00gU0lHQ09NTSBDQ1IgMzcsIDMgKDIwMDcpLCA1PC9zcGFu
PjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1mYW1pbHk6JnF1b3Q7Q291cmllciBOZXcm
cXVvdDsiPuKAkzwvc3Bhbj48c3BhbiBsYW5nPSJFTi1VUyI+MTYuPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPlsyXSBUb25n
IExpLCBLYWkgWmhlbmcsIEtlIFh1LCBSYWh1bCBBcnZpbmQgSmFkaGF2LCBUYW8gWGlvbmcsIEtl
aXRoIFdpbnN0ZWluLCBLdW4gVGFuLiAmcXVvdDtUQUNLOiBJbXByb3ZpbmcgV2lyZWxlc3MgVHJh
bnNwb3J0IFBlcmZvcm1hbmNlIGJ5IFRhbWluZyBBY2tub3dsZWRnbWVudHMmcXVvdDssIEFDTSBT
SUdDT01NLCAyMDIwLiAoDQo8YSBocmVmPSJodHRwOi8vd3d3LnRodWNzbmV0Lm9yZy91cGxvYWRz
LzIvNS8yLzgvMjUyODk3OTUvdG9uZ19zaWdjb21tMjAucGRmIj5odHRwOi8vd3d3LnRodWNzbmV0
Lm9yZy91cGxvYWRzLzIvNS8yLzgvMjUyODk3OTUvdG9uZ19zaWdjb21tMjAucGRmPC9hPiApPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0i
RU4tVVMiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRl
eHQiPjxzcGFuIGxhbmc9IkVOLVVTIj5CZXN0IFJlZ2FyZHMsPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPkppYW88bzpwPjwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1V
UyI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
PHNwYW4gbGFuZz0iRU4tVVMiPi0tLS0tT3JpZ2luYWwgTWVzc2FnZS0tLS0tPGJyPg0KRnJvbTog
UVVJQyBbPGEgaHJlZj0ibWFpbHRvOnF1aWMtYm91bmNlc0BpZXRmLm9yZyI+bWFpbHRvOnF1aWMt
Ym91bmNlc0BpZXRmLm9yZzwvYT5dIE9uIEJlaGFsZiBPZiBNYXJ0aW4gVGhvbXNvbjxicj4NClNl
bnQ6IE1vbmRheSwgSnVseSA2LCAyMDIwIDg6NDEgQU08YnI+DQpUbzogPGEgaHJlZj0ibWFpbHRv
OnF1aWNAaWV0Zi5vcmciPnF1aWNAaWV0Zi5vcmc8L2E+PGJyPg0KU3ViamVjdDogUmU6IEhvcGUg
YSBkaXNjdXNzaW9uIGZvciBkcmFmdC1saS1xdWljLW9wdGltaXppbmctYWNrLWluLXdsYW4tMDA8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5n
PSJFTi1VUyI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPkNhbiB5b3Ugc3BlYWsgYSBsaXR0bGUgYWJvdXQgdGhl
IHJlbGF0aW9uc2hpcCB3aXRoIGRyYWZ0LWl5ZW5nYXItcXVpYy1kZWxheWVkLWFjayA/PG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4t
VVMiPiZuYnNwOzxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQi
PjxzcGFuIGxhbmc9IkVOLVVTIj5PbiBTYXQsIEp1bCA0LCAyMDIwLCBhdCAxNjowNSwgS2FuZ2pp
YW8gd3JvdGU6PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsmbmJzcDsgPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsgRGVhciBRVUlDIFdH
IG1lbWJlcnMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+
PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsgPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsgPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsgV2Ug
dXBsb2FkZWQgYSBkcmFmdCBkZXNjcmliaW5nIGEgbWVjaGFuaXNtIGZvciBBQ0sgb3B0aW1pemF0
aW9uIHRvDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48
c3BhbiBsYW5nPSJFTi1VUyI+Jmd0OyBRVUlDIGdyb3VwLiBUaGUgbGluayBpcyA8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+
Jmd0OyA8YSBocmVmPSJodHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9kcmFmdC1saS1x
dWljLW9wdGltaXppbmctYWNrLWluLXdsYW4vIj4NCjxzcGFuIHN0eWxlPSJjb2xvcjp3aW5kb3d0
ZXh0O3RleHQtZGVjb3JhdGlvbjpub25lIj5odHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2Rv
Yy9kcmFmdC1saS1xdWljLW9wdGltaXppbmctYWNrLWluLXdsYW4vPC9zcGFuPjwvYT4uLjxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVO
LVVTIj4mZ3Q7IFRoaXMgc29sdXRpb24gY29tZXMgZnJvbSBvdXIgcHJhY3RpY2UgYW5kIHRoZSBy
ZXN1bHRzIHNob3cgaXQgaXMgYQ0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1z
b1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsgZ29vZCByZXBsYWNlbWVudCBvZiB0
aGUgdHJhZGl0aW9uYWwgQUNLIG1lY2hhbmlzbSB0byBjb21wZW5zYXRlIGZvcg0KPG86cD48L286
cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMi
PiZndDsgc2NlbmFyaW9zIHdoZXJlIHRoZSBhY2tub3dsZWRnZW1lbnQgb3ZlcmhlYWQgaXMgbm9u
LW5lZ2xpZ2libGUgKGkuZS4sDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
UGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jmd0OyB3aXJlbGVzcyBzY2VuYXJpb3MpLjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9
IkVOLVVTIj4mZ3Q7IDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRl
eHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mZ3Q7IDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mZ3Q7IFRoZSBrZXkgcG9pbnRz
IGZvciB0aGlzIHNvbHV0aW9uIGNhbiBiZTo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jmd0OyA8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jmd0OyA8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5n
PSJFTi1VUyI+Jmd0OyAxLiBXZSBjb25jbHVkZSB0aGUgZm9ybXVsYSBvZiB0aGUgbWluaW11bSBB
Q0sgaW50ZW5zaXR5IHJlcXVpcmVkIGZvcg0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsgUVVJQyB0cmFuc3BvcnQu
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFu
Zz0iRU4tVVMiPiZndDsgPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWlu
VGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsgPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAg
Y2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZndDsgMi4gSW4gb3JkZXIg
dG8gYWxsZXZpYXRlIHRoZSBlcnJvciBpbiBSVFQgZXN0aW1hdGlvbiwgd2UgdXNlIHByb3RvY29s
DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBs
YW5nPSJFTi1VUyI+Jmd0OyBleHRlbnNpb25zIGFuZCBhIG9uZS13YXkgZGVsYXkgZmFjdG9yLiBX
ZSB0aGluayB0aGlzIHJvdW5kLXRyaXAgdGltaW5nDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jmd0OyBtZXRob2QgY2Fu
IGFsc28gYmUgYXBwbGljYWJsZSBmb3IgdGhlIGFjayB0aGlubmluZyBtZWNoYW5pc21zIChzdWNo
IGFzDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48c3Bh
biBsYW5nPSJFTi1VUyI+Jmd0OyA8L3NwYW4+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250
LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+4oCdPC9zcGFuPjxzcGFuIGxhbmc9IkVO
LVVTIj5DaGFuZ2luZyB0aGUgRGVmYXVsdCBRVUlDIEFDSyBQb2xpY3k8L3NwYW4+PHNwYW4gbGFu
Zz0iRU4tVVMiIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtDb3VyaWVyIE5ldyZxdW90OyI+4oCd
PC9zcGFuPjxzcGFuIGxhbmc9IkVOLVVTIj4gIzM1MjkpDQogdGhhdCBoYXZlIGJlZW4gZGlzY3Vz
c2VkIDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFu
IGxhbmc9IkVOLVVTIj4mZ3Q7IGluIFFVSUMgZ3JvdXAuLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mZ3Q7IDxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVT
Ij4mZ3Q7IDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxz
cGFuIGxhbmc9IkVOLVVTIj4mZ3Q7IDMuIEZvciBpbXBsZW1lbnRhdGlvbiBhbmQgaW50ZXJvcGVy
YWJpbGl0eSwgd2UgZGVmaW5lIGEgbmV3DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jmd0OyBBQ0stSU5URU5TSVRZIEZy
YW1lIGluIHdoaWNoIEFDSyBJbnRlbnNpdHkgaXMgc2V0LiBBQ0sgSW50ZW5zaXR5IGlzIGENCjxv
OnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9
IkVOLVVTIj4mZ3Q7IHZhcmlhYmxlLWxlbmd0aCBpbnRlZ2VyIGluZGljYXRpbmcgdGhlIHVwZGF0
ZWQgaW50ZW5zaXR5IG9mIFFVSUMgQUNLDQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jmd0OyBGcmFtZSBjYWxjdWxhdGVk
IGJ5IG91ciBmb3JtdWxhLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFp
blRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mZ3Q7IDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mZ3Q7IDxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4m
Z3Q7IFdlIGxvb2sgZm9yd2FyZCB0byB5b3VyIHZhbHVhYmxlIGNvbW1lbnRzIGFuZCBzdWdnZXN0
aW9ucy4gVGhhbmtzLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRl
eHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mZ3Q7IDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNs
YXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mZ3Q7IDxvOnA+PC9vOnA+PC9z
cGFuPjwvcD4NCjxwIGNsYXNzPSJNc29QbGFpblRleHQiPjxzcGFuIGxhbmc9IkVOLVVTIj4mZ3Q7
IFNpbmNlcmVseSw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0
Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jmd0OyA8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFz
cz0iTXNvUGxhaW5UZXh0Ij48c3BhbiBsYW5nPSJFTi1VUyI+Jmd0OyBKaWFvPG86cD48L286cD48
L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb1BsYWluVGV4dCI+PHNwYW4gbGFuZz0iRU4tVVMiPiZn
dDsmbmJzcDs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvUGxhaW5UZXh0Ij48
c3BhbiBsYW5nPSJFTi1VUyI+Jm5ic3A7PG86cD48L286cD48L3NwYW4+PC9wPg0KPC9ibG9ja3F1
b3RlPg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_719A2C1D4AC73847B6E1BF21DF1545EAE5C802D6dggemm534mbschi_--


From nobody Tue Jul  7 23:35:05 2020
Return-Path: <Ruediger.Geib@telekom.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 EDE403A0982; Tue,  7 Jul 2020 23:34:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=telekom.de
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Z8HxZ9Isv1di; Tue,  7 Jul 2020 23:34:58 -0700 (PDT)
Received: from mailout31.telekom.de (mailout31.telekom.de [194.25.225.143]) (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 1F05C3A097E; Tue,  7 Jul 2020 23:34:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1594190097; x=1625726097; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=uLUYbADDufzT0yZtFaVnNIoFvkCzzYXMzTpgo1TxFgY=; b=c46CR1t3ZyAo5eEeEbNErKaQFdC2Fwq6j/tf2T0l5gYbB9WKNbvF2rJR Lad2ZfVCcX97i+FJHAgxksRlH/deYV1p5BxSzpBLiKyAdfj/KFliQLlHN BFNPLDlhBoYmv7BCOrX6mYgvNXfgdEc/bSxrnDTZx6RzLU6Kl/vUnx7na Qx/yYx2l0CFjISn2jiy59HDw6RLw8Sf4uN8fg6L9ZGWzkMJnqT4AGkZbr 9QwfJ/odizlqHF0TrcwKbciOgq+cAgbuFhlV0+2UwFjWlIU0gDc1bggrb zTgGZbGHAtSu1n6KAw/bSRgDh2nzjQV62RCLCw5ePlZ6cmm28KkRiMgLE g==;
IronPort-SDR: esbw0fM3uwyNxc6zi/pFkt30B5cbO2xxYsbpxGQq6Vy2FBvgywlgPPTkUD1DkIb5c8MiaE2BCp 2We1yYbja5xQ==
Received: from qde9xy.de.t-internal.com ([10.171.254.32]) by MAILOUT31.dmznet.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Jul 2020 08:34:53 +0200
IronPort-SDR: JhinP/wniYhS7U9ju8MUJ+Yo3E+J6zdZfEJpbOar/k0xpGWjGQuc1k01Po6IpmveuJi1BOB9m8 vFPA5El5yGzTeA5qTtIFmAgwD68BeExFM=
X-IronPort-AV: E=Sophos;i="5.75,326,1589234400"; d="scan'208";a="135121134"
X-MGA-submission: =?us-ascii?q?MDFTVqZGFRdYDFpGFTSmCEgfHJYArwQFuNeDj5?= =?us-ascii?q?G/st6D4vDNzUSZTHX7ZchZp9+cLQvGVCimWnoCYiXYuNyCjJ2xj/OizK?= =?us-ascii?q?+3VggJ6/Onkl+OF3wFwryQZuJjm5fhsiVgR2gTIb8z/SnWOFNEXIfMzA?= =?us-ascii?q?6D+Z0DgptrIA+kHNpRLEeFzg=3D=3D?=
Received: from he105709.emea1.cds.t-internal.com ([10.169.118.41]) by QDE9Y1.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES256-SHA384; 08 Jul 2020 08:34:53 +0200
Received: from HE105717.EMEA1.cds.t-internal.com (10.169.118.53) by HE105709.emea1.cds.t-internal.com (10.169.118.41) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 8 Jul 2020 08:34:52 +0200
Received: from HE104164.emea1.cds.t-internal.com (10.171.40.35) by HE105717.EMEA1.cds.t-internal.com (10.169.118.53) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Wed, 8 Jul 2020 08:34:52 +0200
Received: from GER01-LEJ-obe.outbound.protection.outlook.de (51.5.80.20) by O365mail06.telekom.de (172.30.0.233) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Wed, 8 Jul 2020 08:34:48 +0200
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=NSM2atjAe4CZ/XPszCzRFP+koWM4kEq6QhJm7twys5jJwzQsAof8cV/rExpzotswMlO/a/PzUQQrXT/Bcpki1cl7DNlrU3eZu1e6FCkcnX1WxnAcHy3pZKEFML7uE1WxLA1WANdX4ggopIu8eZcNm2cmupZfv3Cqzj+y3mwLjyrRq4CW+ta1ssI8uosIWaR6ln92A6Rya1z9qVcwHgGcyc68FTYgPdMIy8qTjU+X1rVAEiRywUQxXjTWwWjtluIHfnHw9HCkZsMpwovR7dASD2e+AKwfMpYKGi/ZBik/l5UEcEsU/so2Q/vtaxygIojKbjk9yFwOlwhfIOp3VSKmKA==
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=uLUYbADDufzT0yZtFaVnNIoFvkCzzYXMzTpgo1TxFgY=; b=Fg/E//lsdWdzmw1hLmTcYOFQgF8m0AKKRhRKoX9wTMibCyPEyMpTwAurgsULeRuFLhAwo0w0ineZ9EIqWlSq+0QK1GihqLp5xKL+xf+Z3uOOjmLvTEAYq+Xe/JHasQzvZifXjgnTeofuHBDwD51VRBhQZsnSvxD7HXAO1frPtuvQenGft7IVw+zEpefVaCtgxsjFtTq3yWL0RX/HR5R77eFzS1Z4hiHGbbW+IslKmLkTc03cI0VAIL3IIX1xdcVfIkWYYXU4H/FGo+wchdYNakJ7XU5bmuTG16ah4W3IJ3UE5Kw0xCju6tfv0YaLP00EhaC+7uE5TN31+kAo8i1xcQ==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=telekom.de; dmarc=pass action=none header.from=telekom.de; dkim=pass header.d=telekom.de; arc=none
Received: from LEXPR01MB1040.DEUPRD01.PROD.OUTLOOK.DE (2a01:4180:c013:10::18) by LEXPR01MB1166.DEUPRD01.PROD.OUTLOOK.DE (2a01:4180:c013:a::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3174.17; Wed, 8 Jul 2020 06:34:50 +0000
Received: from LEXPR01MB1040.DEUPRD01.PROD.OUTLOOK.DE ([fe80::9570:5376:d64e:6584]) by LEXPR01MB1040.DEUPRD01.PROD.OUTLOOK.DE ([fe80::9570:5376:d64e:6584%8]) with mapi id 15.20.3174.021; Wed, 8 Jul 2020 06:34:50 +0000
From: <Ruediger.Geib@telekom.de>
To: <mauro.cociglio=40telecomitalia.it@dmarc.ietf.org>
CC: <riccardo.sisto@polito.it>, <ippm@ietf.org>, <quic@ietf.org>
Subject: AW: About to measure Explicit Performances on user devices (mobile phones, PCs)
Thread-Topic: About to measure Explicit Performances on user devices (mobile phones, PCs)
Thread-Index: AdZQhy9WxJZw9I9ETrSFmbU5QsD6MAEZxd9w
Date: Wed, 8 Jul 2020 06:34:50 +0000
Message-ID: <LEXPR01MB1040583A254B9FCEE49FF50D9C670@LEXPR01MB1040.DEUPRD01.PROD.OUTLOOK.DE>
References: <8c2df3da5f8c4450b272e3224dd23e46@TELMBXD14BA020.telecomitalia.local>
In-Reply-To: <8c2df3da5f8c4450b272e3224dd23e46@TELMBXD14BA020.telecomitalia.local>
Accept-Language: de-DE, en-US
Content-Language: de-DE
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=telekom.de;
x-originating-ip: [84.136.92.75]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: fe14e291-7fca-47c9-069c-08d82309047a
x-ms-traffictypediagnostic: LEXPR01MB1166:
x-microsoft-antispam-prvs: <LEXPR01MB116671DF2522B1E995B106CF9C670@LEXPR01MB1166.DEUPRD01.PROD.OUTLOOK.DE>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 6ABFeNbN7uQ+FFhCONSKSKDqyjaPcqR7Xhp4y4xglrm+Tm7a+covdlddcOjfsidWW30jJ9AVbfRc2+fn4RF5cZmO5hcgFi4UCjL7axOYfVaf/Un91QlDqqFC0BOBbpEq6ornZFNd5pBTXM6njJjzCl13Pa4KSe8jp1YMq3ZSsPKyLBsO9LMjUGbbM9nTMjvKJyXlFhGkBqcCuE+9OXGN0f72B9sBpb0lS2z9jVuFgoTE87ronHga0gvJvwgb83YcgGpymJxXVPRiP7HjPBR4OdIzZCp0tUXka4cVS/dKCUaYkUO8Svuetx4LKqNvZ4+UYGAhve736KjDThgbjd4R7wntOjJSAOphoyYtpywKAW0=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:LEXPR01MB1040.DEUPRD01.PROD.OUTLOOK.DE; PTR:; CAT:NONE;  SFTY:; SFS:(39860400002)(136003)(376002)(346002)(396003)(366004)(66476007)(66946007)(66446008)(64756008)(66556008)(9686003)(478600001)(8676002)(86362001)(5660300002)(8936002)(7696005)(966005)(55016002)(71200400001)(33656002)(54906003)(316002)(76116006)(4326008)(66574015)(83380400001)(186003)(2906002)(26005); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: IaMR+Ut3o52l4VYTRKjnq1eiYTYMF4HJIZ0kPaxBanA/0Nr94GABOaO1K9TTvZQgMG7Rqg2hjN9l7/7mnU1N9doT/qIw538aMMxR2UUf4YCAqjs8DzvmnxvwQd3SiF3kC3QFFSAcmWXi58Pq8y7xGBr3dz8wLbVLdcDCm4lMivfYrZj3qOyb3+0aRe7vWO1Y1NPwRNJ9ARRz43dr336ENf9v1QVpix6MHNRri+EIGA1C0FTU06vvtIv3RDtRkxq90fN8fOAuzq4KiC87USpNxfhFaBGPK/x4mP6rZOpOt49Pesd6+Hq9/d0I2jPo37SKdnSr8tkGmeu0KJzxvCKvHk0TFTPa/YLCPWqyZBskWVUm2lX2k2P26XDbOEQTkk55BMdSfqML6MPXt8bnQoBBzosUu9DD+5HcYsInCDx+2QO0HPlCAAcUn7NdSxv2y6gOSHCe2ithGgChID67uYQwLHUCADb4e0V2I93m6Zt57Uc=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: LEXPR01MB1040.DEUPRD01.PROD.OUTLOOK.DE
X-MS-Exchange-CrossTenant-Network-Message-Id: fe14e291-7fca-47c9-069c-08d82309047a
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jul 2020 06:34:50.8659 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: TvrTGCkou7rcVraV6t1pQ16lKVQePvay9Rmgn+gjS1ujpqluz4qyNQ4jI1xLAkihTla1yuXHi7lb09b6xojDAauGYNjiJTruUO4v+oFI0M0=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LEXPR01MB1166
X-TM-SNTS-SMTP: 4F9F513DABF01F97293504790F9C89A4209F0998EED1559DC6F0950B78984A202000:8
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/hNPXaTsgQGxN_3gwbx3FkWpmdqc>
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, 08 Jul 2020 06:35:00 -0000

Hi Mauro,

You suggest to base activation of the spin bit marking on a terminal config=
uration or on a user decision. That is reasonable, I think. An additional o=
ption is to activate the spin bit randomly on a number of connections. That=
 might help to avoid situations where a set spin bit indicates that the per=
formance of this flow is "rather likely" reported. A bit indicating that a =
flow's performance is likely to be reported to one or more interested parti=
es should be taken as an incentive for preferential treatment.

The number of flows with randomly activated spin bit should be higher than =
those reporting performance, if this option is pursued.

Regards,

Ruediger

-----Urspr=FCngliche Nachricht-----
Von: ippm <ippm-bounces@ietf.org> Im Auftrag von Cociglio Mauro
Gesendet: Freitag, 3. Juli 2020 14:33
An: IETF IPPM WG (ippm@ietf.org) <ippm@ietf.org>; quic@ietf.org
Cc: 'Riccardo Sisto' <riccardo.sisto@polito.it>
Betreff: [ippm] About to measure Explicit Performances on user devices (mob=
ile phones, PCs)

Dear QUIC and IPPM WG members.
=A0
After Spin bit introduction, and now with packet loss measurement proposals=
*, the Explicit Performance Monitoring on client-server protocols (e.g. QUI=
C) becomes an interesting topic for Telco.
Explicit Performance Monitoring enables a passive Observer to measure delay=
 and packet loss only watching the marking (a few bits) of production traff=
ic packets.
=A0
We propose that the first place where to put the Explicit Performance Obser=
ver is on the user device (e.g. mobile phones, PCs).
Main reasons of this choice.
1. Scalability. On the user device there are few connections to monitor.
2. The Observer can monitor both directions: upload and download (inside th=
e network is not always possible).
3. Some measurements, natively not end2end, became E2E (e.g. packet loss Q-=
bit) 4. It's possible to set alarm thresholds on the user device (and to si=
gnal to network probes to monitor only the sessions with impairments, in or=
der to segment the performance measurements and to locate the faults). In t=
his case observers, also embedded into network nodes, need to monitor only =
a limited number of connections (the ones that have problems).
=A0
Of course, to do this, the decision whether to activate the marking=A0(e.g.=
 Spin Bit) or not=A0must be made by=A0the device owner configuring the=A0ap=
plications (e.g. browsers) based on protocols that supports Explicit Perfor=
mance Monitoring (e.g. QUIC).
=A0
All applications should therefore provide for the activation or deactivatio=
n of the marking for the Explicit Performance Monitoring.
=A0
So, from this point of view, in the Client-Server handshake it should be th=
e Client who decides whether the marking is active or not within a session =
and the Server should adapt.
=A0
The performance information thus obtained could then be kept on the user de=
vice or sent to "external bodies" according to the will of the device owner=
.
The main recipient would be the Internet Service Provider (see point 4 of t=
he previous list), but these data could also be of interest to the national=
 regulatory authorities and perhaps others.
=A0
Feedbacks are welcomed.
Best regards.
=A0
Mauro

* Explicit packet loss measurements proposals:
1) https://tools.ietf.org/html/draft-cfb-ippm-spinbit-measurements-02
2) https://tools.ietf.org/html/draft-ferrieuxhamchaoui-quic-lossbits-03

=A0
_____________________
Mauro Cociglio
Telecom Italia-TIM
Via G. Reiss Romoli, 274
10148 - Torino (Italy)
Tel.: +390112285028
Mobile: +393357669751
_____________________
=A0


Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.=20

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.=20

Rispetta l'ambiente. Non stampare questa mail se non =E8 necessario.

_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm


From nobody Wed Jul  8 02:08:28 2020
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 1D3033A0CE7; Wed,  8 Jul 2020 02:08:11 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-applicability-07.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 7.7.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <159419929103.4646.16434347621508226048@ietfa.amsl.com>
Date: Wed, 08 Jul 2020 02:08:11 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/jgvtKV5pd1aqKMs-hR3MjzzpUvM>
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, 08 Jul 2020 09:08:11 -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           : Applicability of the QUIC Transport Protocol
        Authors         : Mirja Kuehlewind
                          Brian Trammell
	Filename        : draft-ietf-quic-applicability-07.txt
	Pages           : 17
	Date            : 2020-07-08

Abstract:
   This document discusses the applicability of the QUIC transport
   protocol, focusing on caveats impacting application protocol
   development and deployment over QUIC.  Its intended audience is
   designers of application protocol mappings to QUIC, and implementors
   of these application protocols.


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

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-applicability-07
https://datatracker.ietf.org/doc/html/draft-ietf-quic-applicability-07

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


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 Wed Jul  8 02:08:32 2020
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 8FC5E3A0CC9; Wed,  8 Jul 2020 02:08:12 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-manageability-07.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 7.7.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <159419929254.4883.14756237673400185551@ietfa.amsl.com>
Date: Wed, 08 Jul 2020 02:08:12 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/PVRNjrjRoT0Hmt4ZyMWQcZVy3Ls>
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, 08 Jul 2020 09:08:13 -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           : Manageability of the QUIC Transport Protocol
        Authors         : Mirja Kuehlewind
                          Brian Trammell
	Filename        : draft-ietf-quic-manageability-07.txt
	Pages           : 23
	Date            : 2020-07-08

Abstract:
   This document discusses manageability of the QUIC transport protocol,
   focusing on caveats impacting network operations involving QUIC
   traffic.  Its intended audience is network operators, as well as
   content providers that rely on the use of QUIC-aware middleboxes,
   e.g. for load balancing.


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

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-manageability-07
https://datatracker.ietf.org/doc/html/draft-ietf-quic-manageability-07

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


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 Wed Jul  8 11:04:50 2020
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1D9FD3A059F for <quic@ietfa.amsl.com>; Wed,  8 Jul 2020 11:04:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 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, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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=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 rryYYdsyOnln for <quic@ietfa.amsl.com>; Wed,  8 Jul 2020 11:04:45 -0700 (PDT)
Received: from EUR05-AM6-obe.outbound.protection.outlook.com (mail-am6eur05on2078.outbound.protection.outlook.com [40.107.22.78]) (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 8E0703A0542 for <quic@ietf.org>; Wed,  8 Jul 2020 11:04:44 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=RbUchu0WXKzfqiwK+E8f2ScKZIB1LAz2h95r8ZrElZd3kaXZaF9JkAelwLSWQeOn4D6lEhCr0kZU97fZnIaQMBaoYo857Ihm8FVvFqbFcjqRiRWpGEEoIVP0KSru56qytHmRTuJLBRRL782haFdhnqDvR+OngdFR+yBSzG1al5ci4Z5VHRNiu+Z9+zr/ilBqF2QYjXrsK8/niP4yaZk20EmHQXiA9BH1CSD+hy/ssjZwanSiPppmsDkoDZp2A5IQZ5tujldUf4AutQMl71nCCaKv1eQ5JsxreZED5YUc03SiHrGp0EReWxIEBfLVvVzdf1yoRgP0bWxPnVjX0AEXTQ==
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=wiNm1FFMKBGzcfrcD+0cuWXUdF0naJP4V9iZ87RWr34=; b=MCUQdoJSwqnBMoo0TyYAJOZ03vmJnCkPuXRkRXBy2MjEakHLhXSvQcw+hv/eGdKnYE5Fz/MWKlkLCY+GjbBRQScCsRuZhOWP+Y0oIZG9237jQlu8Qd/rIv/vtKsliwL54T1dOQdDe1j4bFoHdmLRNDecYVzhRDSBwiQ2F1bo1dYRBXWDPQALJ3HMm7Fmy65KfxM/JUy/bzPEyYzbGS+3OU3nEPoRxNjrmiwoPI9DO/f7ydniUwlNgx6h5clvTsP2Z9Cx2hU4Sa2gu3qMRax6jN+TBkBHNxtLOOGzQHbi+V/Ucgale1wIWnatko93Ob1yqgb6UTBLaJnIfBwFPHdclA==
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=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=wiNm1FFMKBGzcfrcD+0cuWXUdF0naJP4V9iZ87RWr34=; b=Gu/JQrh8khA+AuPoTjgROVORbD1PDy5jIEaReWIQwDZrmg+FCRTtNB2Iod2KtiUxS8hT5IMv6O7JiqXYJXXVj4FEjTp9PSQI2Df0/E//RO1FV6FmuOAzW1eHwsKvl29sfNCCWbfAlxeIp4/6XXLXM7tylOohtcQ1ZQtSo75gn5k=
Received: from HE1PR0702MB3772.eurprd07.prod.outlook.com (2603:10a6:7:8e::14) by HE1PR0701MB2795.eurprd07.prod.outlook.com (2603:10a6:3:9b::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3174.8; Wed, 8 Jul 2020 18:04:37 +0000
Received: from HE1PR0702MB3772.eurprd07.prod.outlook.com ([fe80::546c:3b3:9193:3351]) by HE1PR0702MB3772.eurprd07.prod.outlook.com ([fe80::546c:3b3:9193:3351%6]) with mapi id 15.20.3174.020; Wed, 8 Jul 2020 18:04:37 +0000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
To: "quic@ietf.org" <quic@ietf.org>, "draft-ietf-quic-transport@ietf.rog" <draft-ietf-quic-transport@ietf.rog>
Subject: WG last call comments on draft-ietf-quic-transport-29
Thread-Topic: WG last call comments on draft-ietf-quic-transport-29
Thread-Index: AdZVSFz+OetpiiZFSvGMix+HsfHEEg==
Date: Wed, 8 Jul 2020 18:04:37 +0000
Message-ID: <HE1PR0702MB37720D42E58ACB56A14E679495670@HE1PR0702MB3772.eurprd07.prod.outlook.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [158.174.104.67]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 456f5aa7-993a-445a-ae12-08d8236960a3
x-ms-traffictypediagnostic: HE1PR0701MB2795:
x-microsoft-antispam-prvs: <HE1PR0701MB27956D6C5D776590F36AA23C95670@HE1PR0701MB2795.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: MwxObVRBGZr6je0abB96vWXnq6gz1pmlMMio3GoWvxKXy34tseCOsG6c5/3jV9xV1e1G3EVjHHZ1ef8TAeUvXKdj9Ky1ZfbUgRW6Ia/ZzoQXNWGZ9Hk3hw4wXTbtEvyTrQ6F2lt+EueOvwVpUsysWyQcCC7dVSHHTLQKnQDiJj07nHcYOXjX4ajSSfXLh+4c6A7ZU+9LVBfzb3K029ohNiewQsEvMV7dTcEY8FvZ1s0noDN5uatdsTshx7Sih0h9DPbyncSRn0chdDhQKp2sritHY+qFbk6S2tEXFMmkBSLPI1Rsk2W0roGAvtBopQa/C6mpTem9s5UvQw27uqhdlFwY9Pn4QQuliLWYww6Mq4ldirj2/P1lX/AtF9SALLaAfCn0pZZmw0Zkic88YhB+Tw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR0702MB3772.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(346002)(376002)(366004)(39860400002)(136003)(396003)(7696005)(33656002)(99936003)(9686003)(316002)(55016002)(110136005)(66476007)(66616009)(76116006)(66446008)(66946007)(66556008)(64756008)(186003)(8936002)(8676002)(26005)(6506007)(966005)(478600001)(83380400001)(5660300002)(2906002)(71200400001)(44832011)(52536014)(86362001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: Sk1LSDY1FxNU2P0X8wUJz6qwpedaY9Nz8oE2/5GfMh+CxXeb5Bf4FFMsZNlx7sV6VWf2bsJZlZsbmiboM7lxhCE0WDSFdpfHcQnIP/u+tcI4IXzt3zTICW0iyJj390hOFUQavb+Il8cTehCs04ajk80v+oMsYa7NbqavA4vf/wbtQ6zYyS+dHSiQgllnp5kYCLSzDtjZYFZuF+iypL7HP+719o2NmkwHl5TJM6/B8+TRkmstOka+CuJ3hpTAx3/RCWewN/wQb0O/YDu4k8tTuzKVzBd5A+4rScKlI45kvPoBwG8h0RpeqOq2Bwafik9mP9fZX0UjZdu+zu4jhxJRZGujrgKYh031ISepuc3k+IZ1rv42JshKI2La0IwvKr0Q2wpf2QFTaUwbg2jMXYf3xct2MVpbNFyQt2b7+onzQkQCUvsCQQIvwTQ1av0k+BWz5c22Jp+kmAVQ7bdHxXWrkwYBPq1oaT3694C29/PdSfJxqPh6oJH2FhluAKeCIr4W
x-ms-exchange-transport-forked: True
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_013B_01D65563.0098DE70"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR0702MB3772.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 456f5aa7-993a-445a-ae12-08d8236960a3
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jul 2020 18:04:37.1583 (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: hUoFYDtb8CFn9K3xicQcpUwA8vSVKfbtT2iYtqRB9GxDYMB66vzXfaGWwdkASRZfyf4cIfZhDMklJcyESfFsCOXeS9pivJIelr+yBeR1TFo=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2795
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/3eajkpwoaIpZlEcPBkSGavVWhqc>
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, 08 Jul 2020 18:04:48 -0000

------=_NextPart_000_013B_01D65563.0098DE70
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_013C_01D65563.0098DE70"


------=_NextPart_001_013C_01D65563.0098DE70
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Hi

 

Sorry for not filing issues and instead giving you this dump. A bit short of
time so I wanted to get these in before the end of the last call. 

 

And I have noticed that some are really edge cases. So think them through
and then it is fine to say this is not relevant because of .

 

 

1.       Section 1.3: 

x (A..B):  Indicates that x can be any length from A to B; A can be
      omitted to indicate a minimum of zero bits and B can be omitted to
      indicate no set upper limit; values in this format always end on
      an octet boundary

There is an upper limit based on the protocol even in these cases, either
due to encoding restrictions or the protocol. 2^62-1 bytes in most cases for
length or data limits or the per packet limit where MPS will be a
restriction. Should that be made more explicit. 

 

2.       Section 3.2, Figure 3: 
The top most RESET_STREAM which leads to the Recv state. Shouldn't that go
to the RESET Recvd state immediately. If I interpret the figure it will take
two RESET_STREAMS until one end up in RESET RECVD
 

3.       Section 4.1: "

If a sender is blocked
   for a period longer than the idle timeout (Section 10.2), the
   connection might be closed even when data is available for
   transmission."

Who may close the conenction? both peers, or the sender that is blocked or
the receiver?

 

4.       Section 7.4.1: "

   In particular, a server that accepts 0-RTT data
   MUST NOT set values for the following parameters (Section 18.2) that
   are smaller than the remembered value of the parameters."

 

So far I have not seen any definition for how long TP parameters will be
remembered. I guess that there is a time limit on the 0-RTT keying material
stored in the client that is relevant her, however this is not at all
referenced here. Should there be a pointer or explanation? Because the above
normative statement appears to be missing the tie into how long the client
will remember theses remembered values.

 

5.       Section 8.1.3 and 8.1.4:

First of all I got the wrong impression of this section as the details about
address validation part, that you actually include the address is in the
next section 8.1.4. I don't know if there should be something done about
this or not. But my impression after 8.1.3 and before I read 8.1.4 that this
was not address validation, only client validation, i.e. this is a client I
talked to before. 

My actual question I have on these section is if it there should be
clarification on that the client should keep track of the token on a server
authority + client address/network scope. So that the client will not send
the token unless it is on the same network it was before. 

But maybe this last is unnecessary as the server will ignore the token if it
doesn't match. 
 

6.       Section 9.2:
 

  Receiving acknowledgments for data sent on the new path serves as
   proof of the peer's reachability from the new address.

 

This contradicts the text in Section 8.5:

 

Receipt of an acknowledgment for a packet containing

   a PATH_CHALLENGE frame is not adequate validation, since the

   acknowledgment can be spoofed by a malicious peer.

So this might be an intended differenation between path validation and
indication of basic reachability (assuming no hostility). Maybe that
exception also needs to be noted in the last paragraph in Section 9.2.

 

7.       Section 9.3.1: 

   If an endpoint skips validation of a peer address as described in
   Section 9.3, it does not need to limit its sending rate.
 

So I assume what is referenced in Section 9.3 is this: 
 

An endpoint MAY skip validation of a peer address if
   that address has been seen recently.  In particular, if an endpoint
   returns to a previously-validated path after detecting some form of
   spurious migration, skipping address validation and restoring loss
   detection and congestion state can reduce the performance impact of
   the attack.

 

So the question here is what is considered recently. I think the lifetime of
a address validation is significantly longer than the validity of the
congestion control state. 

 

8.       Section 10.1: 
"Endpoints that have some alternative
   means to ensure that late-arriving packets on the connection do not
   induce a response, such as those that are able to close the UDP
   socket, MAY use an abbreviated draining period which can allow for
   faster resource recovery."

 

So to me this assumes that the underlying system will not reuse the local
UDP port in the time it takes to drain the network. I assume even
applications may shoot itself in the foot if it insist on a local source
port for an outgoing QUIC connections and that was recently used. I assume
that this will not have any significant impact on a QUIC instance, and what
it does to another UDP protocol is all dependent.

 

10.   Section 10.2: "

If a max_idle_timeout is specified by either peer in its transport
   parameters (Section 18.2), the connection is silently closed and its
   state is discarded when it remains idle for longer than the minimum
   of both peers max_idle_timeout values and three times the current
   Probe Timeout (PTO)."

 

Should this really be the minimum and not the maximum. For very low values
of MAX_IDLE_TIMEOUT the QUIC stack is not even given a fair chance of
probing if the path is still there or not? And for larger value the 3*PTO
will always be setting the value. I would have expected the maximum, that
below 3*PTO it will not timeout, and when MAX_IDLE_TIMEOUT > 3*PTO that
value will be limit for how long probing is done. 

 

Doesn't the rule also prevent a stack being silent for longer than 3*PTOs?
That appears wasteful to force continuos communication if there  are no data
be sent. 

 

11.   Section 10.3:

Such an
   endpoint SHOULD limit the number of packets it generates containing a
   CONNECTION_CLOSE frame.

 

To what level should it be limited, e.g. one packet per 1/4 RTT? Or is the
argument that 

Any reduction is sufficient. To me it looks like a simple packet mirror on
path that sends the packets back to the sender will maintain the number of
packets in flight unless there is a reduction factor.

 

12.   Section 12.4:

Packet Payload {
     Frame (..) ...,
   }

   The payload of a packet that contains frames MUST contain at least
   one frame, and MAY contain multiple frames and multiple frame types.

 

Shouldn't the above be written as:

 

Packet Payload {
     Frame (1..) 1...,
   }

 

Each frame has  a minimal length of one octet, and there is a requirement of
at least one frame. I did note that there are no x.y definition. And that
the definition says there are 0 or more entries which isn't true here. I
don't know how much to do about the inconsistency in the notation for this
case?

 

13.   Section 17.2.2:

Length field for the Packet header is undefined. I would guess that it
contains the total length of the Initial Packet in bytes but that should be
defined. Applies also to the 0-RTT and Handshake packet.
 

14.   Section 17.2.5:

The value in the Unused field is selected randomly by the
   server.

Should this say that the receiver should ignore the value in the field?

 

 

15.   Section 19.9:

The Maximum Data (i) field as currently defined will be in many connections
the upper limit for how many packets can be sent in any connection due to
its bit limit. As this is a maximum value due to usage of the variable
encoding to 2^62-1 bytes. It is possible that this value could be reached as
around 2^52 packets approximately. An QUIC packet will be possible to
contain at least 1024 bytes, i.e. 10 bits worth of bytes. In a DC center
network with larger MTUs it is possible that already after 2^50 packets this
value will be exhausted.

Should I simply assume that this amount of data is such a big number that if
an application runs into the limit forcing it to restart the connection is a
minor issue. However considering that the limit in packets are relatively
more discussed, this limit is not much discussed and in fact there are no
mention in 19.9 what to do if that value reaches maximum that can be
encoded, i.e. close the connection. 
 


 16. Section 22.1.4: 

 

   All registrations in this document are assigned a permanent status

   and list as contact both the IESG (ietf@ietf.org) and the QUIC

   working group (quic@ietf.org (mailto:quic@ietf.org)).

 

The IESG is recommending that registration owner for IETF STD documents are
IETF. The arguments are in this doc: 

https://datatracker.ietf.org/doc/draft-leiba-ietf-iana-registrations/

 

17.	Section 22:

 

An important question that for the high level structure of the registries
are the question if these registries are Version 1 specific, or  expected to
be used across multiple versions of QUIC? Because if the former then the
general heading for the registries should say QUIC Version 1. If they are
intended to be for multiple versions, what type of indication for which
version particular entries are valid are needed? 

 

 

 

 

 

 

Editorials:

 

A.      Section 8.2 uses PMTU without expansion. Before this point it is
only used in TOC. 

 

B.      Section 9.1: 

An endpoint MAY probe for peer reachability from a new local address
   using path validation Section 8.2 prior to migrating the connection
   to the new local address.

 

Missing parenthis around Section ref. 

 

C.      Section 9.6.3:

"

If the connection to the server's preferred address is not from the
   same client address, the server MUST protect against potential
   attacks as described in Section 9.3.1 and Section 9.3.2."

 

Shouldn't it say something more like:

If the client's packet flow to the server's preferred address for the
connection is not from the same client address, the server MUST protect
against potential attacks as described in Section 9.3.1 and Section 9.3.2.

 


------=_NextPart_001_013C_01D65563.0098DE70
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-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
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=3DGenerator 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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";
	mso-fareast-language:SV;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:48117755;
	mso-list-template-ids:-1737691218;}
@list l1
	{mso-list-id:89815573;
	mso-list-template-ids:-2086125792;}
@list l1:level1
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level2
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level3
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level4
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level5
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level6
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level7
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level8
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level9
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2
	{mso-list-id:259991596;
	mso-list-template-ids:-1024305688;}
@list l2:level1
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level2
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level3
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level4
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level5
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level6
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level7
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level8
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level9
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3
	{mso-list-id:284510036;
	mso-list-template-ids:612653602;}
@list l3:level1
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level2
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level3
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level4
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level5
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level6
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level7
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level8
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level9
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4
	{mso-list-id:331297180;
	mso-list-template-ids:-191828984;}
@list l5
	{mso-list-id:432168385;
	mso-list-template-ids:254328628;}
@list l6
	{mso-list-id:828449538;
	mso-list-template-ids:2129587564;}
@list l7
	{mso-list-id:856116927;
	mso-list-template-ids:-1817015316;}
@list l8
	{mso-list-id:992294888;
	mso-list-template-ids:47746728;}
@list l9
	{mso-list-id:1008291809;
	mso-list-template-ids:1271284754;}
@list l10
	{mso-list-id:1294942753;
	mso-list-type:hybrid;
	mso-list-template-ids:2043084140 69009423 69009433 69009435 69009423 =
69009433 69009435 69009423 69009433 69009435;}
@list l10:level1
	{mso-level-start-at:17;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l10:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l10:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l10:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l10:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l10:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l10:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l10:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l10:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l11
	{mso-list-id:1545556071;
	mso-list-template-ids:-1970267712;}
@list l12
	{mso-list-id:1805005215;
	mso-list-template-ids:-1054304174;}
@list l13
	{mso-list-id:1876773561;
	mso-list-template-ids:-1519213824;}
@list l14
	{mso-list-id:1922793040;
	mso-list-template-ids:645560602;}
@list l4:level1 lfo2
	{mso-level-start-at:2;}
@list l9:level1 lfo3
	{mso-level-start-at:4;}
@list l14:level1 lfo4
	{mso-level-start-at:5;}
@list l6:level1 lfo5
	{mso-level-start-at:7;}
@list l0:level1 lfo6
	{mso-level-start-at:8;}
@list l7:level1 lfo7
	{mso-level-start-at:10;}
@list l8:level1 lfo8
	{mso-level-start-at:11;}
@list l5:level1 lfo9
	{mso-level-start-at:12;}
@list l13:level1 lfo10
	{mso-level-start-at:13;}
@list l11:level1 lfo11
	{mso-level-start-at:15;}
@list l1:level1 lfo13
	{mso-level-start-at:2;}
@list l3:level1 lfo14
	{mso-level-start-at:3;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></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=3DSV =
link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoNormal><span lang=3DEN-US>Hi<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>Sorry for not filing issues and =
instead giving you this dump. A bit short of time so I wanted to get =
these in before the end of the last call. <o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US>And I have noticed that some are =
really edge cases. So think them through and then it is fine to say this =
is not relevant because of &#8230;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l12 level1 =
lfo1;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 1.3: <o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>x (A..B):&nbsp; Indicates that x can =
be any length from A to B; A can be<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
omitted to indicate a minimum of zero bits and B can be omitted =
to<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; indicate no set upper limit; values =
in this format always end on<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; an octet =
boundary<br><br>There is an upper limit based on the protocol even in =
these cases, either due to encoding restrictions or the protocol. 2^62-1 =
bytes in most cases for length or data limits or the per packet limit =
where MPS will be a restriction. Should that be made more explicit. =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l4 level1 =
lfo2;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 3.2, Figure 3: <br>The top =
most RESET_STREAM which leads to the Recv state. Shouldn't that go to =
the RESET Recvd state immediately. If I interpret the figure it will =
take two RESET_STREAMS until one end up in RESET =
RECVD<br>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l4 level1 =
lfo2;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 4.1: =
&quot;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>If a sender is blocked<br>&nbsp;&nbsp; =
for a period longer than the idle timeout (Section 10.2), =
the<br>&nbsp;&nbsp; connection might be closed even when data is =
available for<br>&nbsp;&nbsp; transmission.&quot;<br><br>Who may close =
the conenction? both peers, or the sender that is blocked or the =
receiver?<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l9 level1 =
lfo3;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>4.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 7.4.1: =
&quot;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;&nbsp; In particular, a server =
that accepts 0-RTT data<br>&nbsp;&nbsp; MUST NOT set values for the =
following parameters (Section 18.2) that<br>&nbsp;&nbsp; are smaller =
than the remembered value of the =
parameters.&quot;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>So far I have not seen any definition =
for how long TP parameters will be remembered. I guess that there is a =
time limit on the 0-RTT keying material stored in the client that is =
relevant her, however this is not at all referenced here. Should there =
be a pointer or explanation? Because the above normative statement =
appears to be missing the tie into how long the client will remember =
theses remembered values.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l14 level1 =
lfo4;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>5.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 8.1.3 and 8.1.4:<br><br>First =
of all I got the wrong impression of this section as the details about =
address validation part, that you actually include the address is in the =
next section 8.1.4. I don't know if there should be something done about =
this or not. But my impression after 8.1.3 and before I read 8.1.4 that =
this was not address validation, only client validation, i.e. this is a =
client I talked to before. <br><br>My actual question I have on these =
section is if it there should be clarification on that the client should =
keep track of the token on a server authority + client address/network =
scope. So that the client will not send the token unless it is on the =
same network it was before. <br><br>But maybe this last is unnecessary =
as the server will ignore the token if it doesn't match. =
<br>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l14 level1 =
lfo4;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>6.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section =
9.2:<br>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp; Receiving acknowledgments for =
data sent on the new path serves as<br>&nbsp;&nbsp; proof of the peer's =
reachability from the new address.<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>This contradicts the text in Section =
8.5:<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Receipt of an acknowledgment for a =
packet containing<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;&nbsp; a PATH_CHALLENGE frame is =
not adequate validation, since the<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;&nbsp; acknowledgment can be =
spoofed by a malicious peer.<br><br>So this might be an intended =
differenation between path validation and indication of basic =
reachability (assuming no hostility). Maybe that exception also needs to =
be noted in the last paragraph in Section 9.2.<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l6 level1 =
lfo5;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>7.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 9.3.1: =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;&nbsp;&nbsp;If an endpoint skips =
validation of a peer address as described in<br>&nbsp;&nbsp; Section =
9.3, it does not need to limit its sending =
rate.<br>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>So I assume what is referenced in =
Section 9.3 is this: <br>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>An endpoint MAY skip validation of a =
peer address if<br>&nbsp;&nbsp; that address has been seen =
recently.&nbsp; In particular, if an endpoint<br>&nbsp;&nbsp; returns to =
a previously-validated path after detecting some form of<br>&nbsp;&nbsp; =
spurious migration, skipping address validation and restoring =
loss<br>&nbsp;&nbsp; detection and congestion state can reduce the =
performance impact of<br>&nbsp;&nbsp; the =
attack.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>So the question here is what is =
considered recently. I think the lifetime of a address validation is =
significantly longer than the validity of the congestion control state. =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo6;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>8.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 10.1: <br>&quot;Endpoints that =
have some alternative<br>&nbsp;&nbsp; means to ensure that late-arriving =
packets on the connection do not<br>&nbsp;&nbsp; induce a response, such =
as those that are able to close the UDP<br>&nbsp;&nbsp; socket, MAY use =
an abbreviated draining period which can allow for<br>&nbsp;&nbsp; =
faster resource recovery.&quot;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>So to me this assumes that the =
underlying system will not reuse the local UDP port in the time it takes =
to drain the network. I assume even applications may shoot itself in the =
foot if it insist on a local source port for an outgoing QUIC =
connections and that was recently used. I assume that this will not have =
any significant impact on a QUIC instance, and what it does to another =
UDP protocol is all dependent.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l7 level1 =
lfo7;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>10.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 10.2: =
&quot;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>If a max_idle_timeout is specified by =
either peer in its transport<br>&nbsp;&nbsp; parameters (Section 18.2), =
the connection is silently closed and its<br>&nbsp;&nbsp; state is =
discarded when it remains idle for longer than the =
minimum<br>&nbsp;&nbsp; of both peers max_idle_timeout values and three =
times the current<br>&nbsp;&nbsp; Probe Timeout =
(PTO).&quot;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Should this really be the minimum and =
not the maximum. For very low values of MAX_IDLE_TIMEOUT the QUIC stack =
is not even given a fair chance of probing if the path is still there or =
not? And for larger value the 3*PTO will always be setting the value. I =
would have expected the maximum, that below 3*PTO it will not timeout, =
and when MAX_IDLE_TIMEOUT &gt; 3*PTO that value will be limit for how =
long probing is done. <o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Doesn't the rule also prevent a stack =
being silent for longer than 3*PTOs? That appears wasteful to force =
continuos communication if there&nbsp; are no data be sent. =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l8 level1 =
lfo8;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>11.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 10.3:<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Such an<br>&nbsp;&nbsp; endpoint =
SHOULD limit the number of packets it generates containing =
a<br>&nbsp;&nbsp; CONNECTION_CLOSE frame.<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>To what level should it be limited, =
e.g. one packet per 1/4 RTT? Or is the argument that =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Any reduction is sufficient. To me it =
looks like a simple packet mirror on path that sends the packets back to =
the sender will maintain the number of packets in flight unless there is =
a reduction factor.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l5 level1 =
lfo9;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>12.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 12.4:<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'> Packet Payload =
{<br>&nbsp;&nbsp;&nbsp;&nbsp; Frame (..) ...,<br>&nbsp;&nbsp; =
}<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;&nbsp; The payload of a packet =
that contains frames MUST contain at least<br>&nbsp;&nbsp; one frame, =
and MAY contain multiple frames and multiple frame =
types.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Shouldn't the above be written =
as:<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'> Packet Payload =
{<br>&nbsp;&nbsp;&nbsp;&nbsp; Frame (1..) 1...,<br>&nbsp;&nbsp; =
}<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Each frame has&nbsp; a minimal length =
of one octet, and there is a requirement of at least one frame. I did =
note that there are no x&#8230;y definition. And that the definition =
says there are 0 or more entries which isn't true here. I don't know how =
much to do about the inconsistency in the notation for this =
case?<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l13 level1 =
lfo10;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>13.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 17.2.2:<br><br>Length field =
for the Packet header is undefined. I would guess that it contains the =
total length of the Initial Packet in bytes but that should be defined. =
Applies also to the 0-RTT and Handshake =
packet.<br>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l13 level1 =
lfo10;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>14.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 17.2.5:<br><br>The value in =
the Unused field is selected randomly by the<br>&nbsp;&nbsp; =
server.<br><br>Should this say that the receiver should ignore the value =
in the field?<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><i><span =
lang=3DEN-US =
style=3D'font-size:9.0pt;color:#595959;mso-fareast-language:SV'>&nbsp;</s=
pan></i><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l11 level1 =
lfo11;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>15.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 19.9:<br><br>The Maximum Data =
(i) field as currently defined will be in many connections the upper =
limit for how many packets can be sent in any connection due to its bit =
limit. As this is a maximum value due to usage of the variable encoding =
to 2^62-1 bytes. It is possible that this value could be reached as =
around 2^52 packets approximately. An QUIC packet will be possible to =
contain at least 1024 bytes, i.e. 10 bits worth of bytes. In a DC center =
network with larger MTUs it is possible that already after 2^50 packets =
this value will be exhausted.<br><br>Should I simply assume that this =
amount of data is such a big number that if an application runs into the =
limit forcing it to restart the connection is a minor issue. However =
considering that the limit in packets are relatively more discussed, =
this limit is not much discussed and in fact there are no mention in =
19.9 what to do if that value reaches maximum that can be encoded, i.e. =
close the connection. <br>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><br>&nbsp;16. Section 22.1.4: =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p>&nbsp;</o:p></span></p><pre><span =
lang=3DEN-US>&nbsp;&nbsp; All registrations in this document are =
assigned a permanent status<o:p></o:p></span></pre><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-fareast-language:SV'>&nbsp;&nbsp; and list as contact both the =
IESG (ietf@ietf.org) and the QUIC<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-fareast-language:SV'>&nbsp;&nbsp; working group (quic@ietf.org =
(mailto:quic@ietf.org)).<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'text-indent:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>The IESG is recommending that =
registration owner for IETF STD documents are IETF. The arguments are in =
this doc: <o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-indent:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>https://datatracker.ietf.org/doc/draft-=
leiba-ietf-iana-registrations/<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p>&nbsp;</o:p></span></p><ol =
style=3D'margin-top:0cm' start=3D17 type=3D1><li =
class=3DMsoListParagraph style=3D'margin-left:0cm;mso-list:l10 level1 =
lfo15'><span lang=3DEN-US style=3D'mso-fareast-language:SV'>Section =
22:<o:p></o:p></span></li></ol><p class=3DMsoNormal =
style=3D'margin-left:36.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:36.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>An important question that for the =
high level structure of the registries are the question if these =
registries are Version 1 specific, or &nbsp;expected to be used across =
multiple versions of QUIC? Because if the former then the general =
heading for the registries should say QUIC Version 1. If they are =
intended to be for multiple versions, what type of indication for which =
version particular entries are valid are needed? =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:36.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:36.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:36.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:36.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Editorials:<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l2 level1 =
lfo12;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>A.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 8.2 uses PMTU without =
expansion. Before this point it is only used in TOC. =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l1 level1 =
lfo13;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>B.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 9.1: <o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>An endpoint MAY probe for peer =
reachability from a new local address<br>&nbsp;&nbsp; using path =
validation Section 8.2 prior to migrating the connection<br>&nbsp;&nbsp; =
to the new local address.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Missing parenthis around Section ref. =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l3 level1 =
lfo14;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>C.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 9.6.3:<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&quot;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>If the connection to the server's =
preferred address is not from the<br>&nbsp;&nbsp; same client address, =
the server MUST protect against potential<br>&nbsp;&nbsp; attacks as =
described in Section 9.3.1 and Section =
9.3.2.&quot;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Shouldn't it say something more =
like:<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>If the client's packet flow to the =
server's preferred address for the connection is not from the same =
client address, the server MUST protect against potential attacks as =
described in Section 9.3.1 and Section 9.3.2.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></body></html>
------=_NextPart_001_013C_01D65563.0098DE70--

------=_NextPart_000_013B_01D65563.0098DE70
Content-Type: application/pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIVdjCCAyAw
ggIIoAMCAQICAR0wDQYJKoZIhvcNAQEFBQAwOTELMAkGA1UEBhMCRkkxDzANBgNVBAoTBlNvbmVy
YTEZMBcGA1UEAxMQU29uZXJhIENsYXNzMiBDQTAeFw0wMTA0MDYwNzI5NDBaFw0yMTA0MDYwNzI5
NDBaMDkxCzAJBgNVBAYTAkZJMQ8wDQYDVQQKEwZTb25lcmExGTAXBgNVBAMTEFNvbmVyYSBDbGFz
czIgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCQF0o1ncrwDZbHRPoWN/xIvb1/
gC01O+FvqGepvwMcTYxvMkfVQWikEwTBNQyahEP8XB3/ibPoFxjNkV/7iePqv05dfBsm03V57eaE
41flrSnE9Doo56V7hDZps/1edr2jLZnTkE4jKH0YY/FUOyaddluXQrL/rvBO7N05lU6DBn/nSUDI
xQGyVFpmHT38+ek8Cp6BuHDwAYvkI1R8yK74kB4AlnLUVM9hI7zq+50CldG2uXE6aQg/D7ThQseI
9T+YqKe6HOBxce9YV4FQelxrdEYOgwOYw46obvJ2Mm4ng8Jz89wY6LST6nVEawRgIHFXh53zvqCQ
Iz2KJOHaIdvDAgMBAAGjMzAxMA8GA1UdEwEB/wQFMAMBAf8wEQYDVR0OBAoECEqgqliE0148MAsG
A1UdDwQEAwIBBjANBgkqhkiG9w0BAQUFAAOCAQEAWs6H+RZyFVdLHdmb56ImMOyTZ9/WLdI0r/c4
pc6rFrmrL3w1y6zQD7RMK/yA72uMkV82dvfbsxsZ6vSyEf1hcUS/KLM6Hb+zQ+ifv9wxCHGwnY3W
NEcykMZlJPegSnwEc485bxeMcrW9S8h6+HuDwyhOnAnqZz+yZwQbwxTa+OdJJJHQHWr6YTnva+ch
dQYH2BK0ISBwQnGB2jyaNr6mWw1qbJofkXv5+e9Cuk5OnswMjZTc2UWcXuxCUGOu9F3EsRLcyjuo
Lp0UWgV1t+zXY+K6NbYECJHo2p2c9ma1GKwKplQmNDPSG8HUfxo6jguqMm7b/E8ln9kyx5ZacKzf
TDCCBX0wggRloAMCAQICEQCH7S4aKCZKxRmqOuu5DaLLMA0GCSqGSIb3DQEBCwUAMDkxCzAJBgNV
BAYTAkZJMQ8wDQYDVQQKEwZTb25lcmExGTAXBgNVBAMTEFNvbmVyYSBDbGFzczIgQ0EwHhcNMTQx
MjA1MDgxOTE1WhcNMjEwNDA1MTAyOTAwWjA3MRQwEgYDVQQKDAtUZWxpYVNvbmVyYTEfMB0GA1UE
AwwWVGVsaWFTb25lcmEgUm9vdCBDQSB2MTCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIB
AMK+6yfwIaPzaSZVfp3FVRaRXP3vIb9TgHot0pGMYzHw7CTww6XScnwQbfQ3t+XmfHnqjLWCi65I
tqwA3GV17CpNX8GH9SBlK4GoRz6JI5UwFpB/6FcHSOcZrr9FZ7E3GwYq/t75rH2D+1665I+XZ75L
jo1kB1c4VWk0Nj0TSO9P4tNmHqTPGrdeNjPUtAa9GAH9d4RQAEX1jF3oI7x+/jXh7VB7qTCNGdMJ
jmhnXb88lxhTuylixcpecsHHltTbLaC0H2kD7OriUPEMPPCs81Mt8Bz17Ww5OXOAFshSsCPN4D7c
3TxHoLs1iuKYaIu+5b9y7tL6pe0S7fyYGKkmdtwoSxAgHNN/Fnct7W+A90m7UwW7XWjH1Mh1Fj+J
Wov3F0fUTPHSiXk+TT2YqGHeOh7S+F4D4MHJHIzTjU3TlTazN19jY5szFPAtJmtTfImMMsJu7D0h
ADnJoWjiUIMusDor8zagrC/kb2HCUQk5PotTubtn2txTuXZZNp1D5SDgPTJghSJRt8czu90VL6R4
pgd7gUY2BIbdeTXHlSw7sKMXNeVzH7RcWe/a6hBle3rQf5+ztCo3O3CLm1u5K7fsslESl1MpWtTw
EhDcTwK7EpIvYtQ/aUN8Ddb8WHUBiJ1YFkveupD/RwGJBmr2X7KQarMCpgKIv7NHfirZ1fpoeDVN
AgMBAAGjggGAMIIBfDBOBggrBgEFBQcBAQRCMEAwPgYIKwYBBQUHMAKGMmh0dHA6Ly9jYS50cnVz
dC50ZWxpYXNvbmVyYS5jb20vc29uZXJhY2xhc3MyY2EuY2VyMA8GA1UdEwEB/wQFMAMBAf8wGQYD
VR0gBBIwEDAOBgwrBgEEAYIPAgMBAQIwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBTwj1k4ALP1
j5qWDNXr+nuqF+gTEjCBuQYDVR0fBIGxMIGuMG+gbaBrhmlsZGFwOi8vY3JsLTEudHJ1c3QudGVs
aWFzb25lcmEuY29tL2NuPVNvbmVyYSUyMENsYXNzMiUyMENBLG89U29uZXJhLGM9Rkk/Y2VydGlm
aWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnkwO6A5oDeGNWh0dHA6Ly9jcmwtMi50cnVzdC50ZWxp
YXNvbmVyYS5jb20vc29uZXJhY2xhc3MyY2EuY3JsMBMGA1UdIwQMMAqACEqgqliE0148MA0GCSqG
SIb3DQEBCwUAA4IBAQAQ1elFTM6fGkQ/aRKdkUZicO3Cb9uzBJOpOtFctw+1El0/17lsjoVvJkZB
D3KnUobnrriFdAa+7FAN55KLmZeB/3Y2bG0bB4toSyaVHjOQnQY9M0dv8U852w0Q7GwchKfebLUI
bh9TMt2hI3Xc6j4knFTBUo7C1WAfO51K4bn1irmX6/Ej2VTgiOFsvOAny28W6enFSEQpSHw60VhN
fSttSqTOxyrRR/7kW7Y8yb/3DZDZ/dH6ZCfx/y+BNIv2NuSd85M9HXUzplXXohti4Ql/qeaMn6by
Ius6XlMWZZfkdVRvTuk2PkeC7UmAJ2+/DUWOPpawaytMXVfF4Hvxk34NMIIGBzCCA++gAwIBAgIQ
C0ZtzXB7bjBlrrZreXF57TANBgkqhkiG9w0BAQsFADBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwI
RXJpY3Nzb24xJTAjBgNVBAMMHEVyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMwHhcNMTcxMjE1
MDcyMjIzWhcNMjAxMjE1MDcyMjIyWjBwMREwDwYDVQQKDAhFcmljc3NvbjEaMBgGA1UEAwwRTWFn
bnVzIFdlc3Rlcmx1bmQxLTArBgkqhkiG9w0BCQEWHm1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29u
LmNvbTEQMA4GA1UEBRMHZXJhbXN3ZDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALCp
R2bwd07JixA7T0ohRSgIe90tsAKbfpWqoOXl06qJ6p80/cpBBi9ncfZgU/tlmYiCsaOMNrIrFZdx
BGE6l05HLabq+3DdvYCwvBd7SRxiNrFFaTvQMKVazflLhxFXrR7e4XcVvbmHdCySfEz+v8BpCHwB
WmcZWVJ+/TtnhxJX4odYlSIk2Vy3BHtawSbc4VDUR1oDptr0JQyeLAqYoBhaucPl0kb4hEDJEGUb
8NQkJm9+UEvwv09+qIMyERw7gHZKEmolDmP0tnS6eB5MLzjoPrQA6Wh5K23ZnZ4yhq2EpyYoJscN
eKSboMS/1W9hHlXIKQH1VbLey5uDzj0SPPsCAwEAAaOCAcQwggHAMEgGA1UdHwRBMD8wPaA7oDmG
N2h0dHA6Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2My5jcmww
gYIGCCsGAQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNv
bTBIBggrBgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5s
aW5kaXZpZHVhbGNhdjMuY2VyMCkGA1UdEQQiMCCBHm1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29u
LmNvbTBVBgNVHSAETjBMMEoGDCsGAQQBgg8CAwEBEjA6MDgGCCsGAQUFBwIBFixodHRwczovL3Jl
cG9zaXRvcnkudHJ1c3QudGVsaWFzb25lcmEuY29tL0NQUzAdBgNVHSUEFjAUBggrBgEFBQcDBAYI
KwYBBQUHAwIwHQYDVR0OBBYEFOYr7oaVOdVuFIQQwVsH/F7FPN+2MB8GA1UdIwQYMBaAFBx7GZ6X
nHasID3Y3OORauPbLaZTMA4GA1UdDwEB/wQEAwIFoDANBgkqhkiG9w0BAQsFAAOCAgEAZ9BSrpIN
NFDf3PxEqcUiGmE67HfJYhxzLuay6TgTTmnKRjQTBjYFAw7eEIoYaEEd3L4WFwqwDOfTU78NBzZY
Kh2aBHlWO2JySWJyVwwi1H5CuQ59vBN0K88pJBeoIlDlw8hfZoVmG0gJCcsdGI9F3PHp98GDcqBW
BKo5SrWa3VdKXIBcxHl1S0vA1q80su/in1LQzhIjOh98zt57KvvigZrDokipFp+KGBEWYOShJRAB
4rPWr/tyiGhD5zgLfEEVkaRXxmeHfPRdeqhbxJbqeZ+5fOuBasZwtn64g6OIS0GOhDWjmmCIoV4W
5dlGMQBg5PPWiZv0uaWMqu8M5viityHFJetK5nPEiZbekFysNMFxDhNTLm2rmCjLGndrPIw/qxJF
6fmoE0ZfrHs1mkcRwacblCg3ejIcA4oN0mYtaj+w/w7OFfiSyI41CXNuZfbbzBgvfpaiND/rzCN2
cq6LtDTX2+ebi0GqtfDvuwWfCr+47xXcWMlIG8UNEjxIsocpXCxwJiXiwkGomR5gkRAZAiykn9Du
JRNk61c3Tg9/MI87kNu1N1HXVQg/REN7Re6OhFYacSSVJQesXv9lFsMuGZWu9XSi1IWpHVazeWm8
8ahVr8zgE/ZwWth82FQbaW3Luihoe9mCfjO/X2vYiJHEAoFJ8N4CAHlnf/5+GG2NkIQwggbCMIIE
qqADAgECAhBTuH6D4ZyZKJOwm0kc7LjrMA0GCSqGSIb3DQEBCwUAMDcxFDASBgNVBAoMC1RlbGlh
U29uZXJhMR8wHQYDVQQDDBZUZWxpYVNvbmVyYSBSb290IENBIHYxMB4XDTE1MTAyNzEyMTY0NloX
DTI1MTAyNzEyMTY0NlowRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYzMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIIC
CgKCAgEA7PLfAAC4UPKnu9hUt8aT9+PBqjvUw0Y0tLPOXkO2NC0y2XZks9nJfpWKrNM30k5vu5no
rG4ZKlF5C+3xc6HuIiGQof1bmFGluNOwmZQwl3rOJ+E6k0rqJJTerjj4WOxAvWVW1yC5S4Ubppk3
Q3cYVVuC3qNGsBIXy3/fDL1sc8Ah8zI/JumDpjY8fn/U3CRN6mgNKYrr0sZX6VXYgrpT05ZrJldk
UgUgMKgbIWWEXEASA36pnb5GqD/RMzSgIe8o7YQtIaYB2cmTCLNHjaOL9j1JhNK4bvmbNJ7o58IZ
YzwNv/G/L/bRosQ9c27U+86DNjrdZnpyaRaeMyVUn3SlYLaFqoObdh/xNF2NS8CXs/PVtO57HBKH
MgZqQvsyQJisSocxFqiMj9VK2WhCBbvoTvrNDZvLDlDGuE5RuKwFIpHOVOU5lCBgUUBsbpWIXwM6
kmH/KC1DC5MtQzmvXkbt7KdBXUAxM0JZxf4dS+ACtTDpF9b0vny4DrwaOS0VNXyz1GUOxSqw1wup
5dpXbxLZYx1rLRgZqr9uWhLwAPsq66ZQof5GL0gY72Ym8/Tm28MeMqku+/zRzdYsmclT9rOdgdgS
3b6OMoc5Op0ZPEv/Mx2lFJAVK674ozw2hiuRTVUmoqBr5AuyCoqCEyn32C7U/V7oqyqx5Yd1c5Gs
xuOqQFcCAwEAAaOCAbgwggG0MIGKBggrBgEFBQcBAQR+MHwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9v
Y3NwLnRydXN0LnRlbGlhc29uZXJhLmNvbTBLBggrBgEFBQcwAoY/aHR0cDovL3JlcG9zaXRvcnku
dHJ1c3QudGVsaWFzb25lcmEuY29tL3RlbGlhc29uZXJhcm9vdGNhdjEuY2VyMBIGA1UdEwEB/wQI
MAYBAf8CAQAwVQYDVR0gBE4wTDBKBgwrBgEEAYIPAgMBAQIwOjA4BggrBgEFBQcCARYsaHR0cHM6
Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwSwYDVR0fBEQwQjBAoD6gPIY6
aHR0cDovL2NybC0zLnRydXN0LnRlbGlhc29uZXJhLmNvbS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNy
bDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQW
BBQcexmel5x2rCA92NzjkWrj2y2mUzAfBgNVHSMEGDAWgBTwj1k4ALP1j5qWDNXr+nuqF+gTEjAN
BgkqhkiG9w0BAQsFAAOCAgEAUFhr8dWMO7Quq1dDyIynw8sWmpyF/jWSxBjpHUCyhltoFS7Q1CUB
D0bOULWmYjmzRwme5pkjTFXpOJZLf9Han1SBbrVcP0JMhRsAvfWZjcF0l/c/jqDMqBARxr8OUWOr
0ZWa49Lir3QEs2C+CjGge5tzcLqzQ5pjWxudrLkSGe+sAThDnXUWXGYk8udGZAamJ55drdw96AV9
jWQkMrLIVHKkXVG5Etdx0wiAoTLk1fVtLcz11DiaCZSZVPZ3fdSIpIRhDqz8H4sVprPgvLBdK/aj
dbiRsehCzzohay3zbXDDTDGwKkR8KUi8Xt8HDZCRsb/U/C7MC4tVK0SEPOQCo6swZy0rI0RoGzIC
fsSrZ4JrxANeeSZqCn1A+w0Wz+iqdeP2PVxW0f1rg4/OG2DSl3uB3Q3NT/lDGJtepti+i5CCKEZc
dAOZoviu43sLhqsxSpGjzZidESwovuHeP+O2bNwwtz1DTsXThBB3+JJHVjmkiLo900GITb/i7IBd
Loo4gZms9s1BQ2tm3CJCmpA2XwBTOB6B8/CtgWUWhyloXd3Wbmv7ZUoqqJFBV9g8Zh5mdZ+RzPTo
mgCFz/2aNsddI/2G9ZjN4tG6hmocZR2M5f0MhBv3bo6d5XsLlYwiNJjw5GRqYb8cqqeCaPKkveBJ
zqgb8ToH7WLoOzmPRCmPlpAxggMCMIIC/gIBATBbMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MwIQC0ZtzXB7bjBl
rrZreXF57TAJBgUrDgMCGgUAoIIBfDAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0yMDA3MDgxODA0MzVaMCMGCSqGSIb3DQEJBDEWBBS/nHwAkB97jtHuKx87eraPEX6L
SDBDBgkqhkiG9w0BCQ8xNjA0MAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0D
AgIBQDAHBgUrDgMCGjBqBgkrBgEEAYI3EAQxXTBbMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MwIQC0ZtzXB7bjBl
rrZreXF57TBsBgsqhkiG9w0BCRACCzFdoFswRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNz
c29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYzAhALRm3NcHtuMGWutmt5
cXntMA0GCSqGSIb3DQEBAQUABIIBAHvqP18gCmwZ31edQ5qhzaDQ8MhGs/9NH9ihsOKvmAhPcVtB
jBYArNyIFjnXEPfhvR7imiCyG0aw6xyTriwG09tYBE+yBkjl7+GF8qVfrx/OVSOWCj4HN7v5nAys
NbCx5S2QK9LnvZj428dtDrGfuvyeqQxSW8gTI9MMeXDfqa1dQzB+GA95Mo1oXdtSG/oj8z3vUeX+
tydl2Gqsccy5Qvv2xq99aQEZ0Ok1elr0rF+VqLLwLdZGxb4V0ffEEcqYCwi+skBbcS/C14hq1rhh
L4hT+SHY/odHyBz0vNbttKyw7QpcLjvUKVM8AoT7JjgiuZE3rXbT+COKO/AimRxdyVQAAAAAAAA=

------=_NextPart_000_013B_01D65563.0098DE70--


From nobody Wed Jul  8 11:05:44 2020
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E7EEC3A0794; Wed,  8 Jul 2020 11:05:36 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 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, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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=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 Z_kDYr4luIxz; Wed,  8 Jul 2020 11:05:34 -0700 (PDT)
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-eopbgr140051.outbound.protection.outlook.com [40.107.14.51]) (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 578733A07AA; Wed,  8 Jul 2020 11:05:33 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=OFpkYXalLi1xuCG1o3d9vK6zGLj1Vf5G3t1j4AkAA8/hQn03W1hspegq/SJQecLN3YWWjD4R3Mh897SNsqWOJbUsuzxXM1qI0J9s2+7FchZ8m5YORYfhfU/weVp2U2ly+5t6K3njLELg6G35fTombwBohM+QyC130xAUEYGnSmopp4bxJSd7/MAk/oPtEKef8oyV+Awn9k841w48Alirt3i1trxEjaN/h2k/lkCdRZ4SpgRd6fr5X0ZEPbaaBr3hLVFcIsoJCsc4IGoHE5zQZN+xShFRRXsadAyb1DF7U6y6SZOtKp8wEaQhl4TTRCkFVcGeYL+y80FF/MEyje3tng==
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=xrWAwFRDwA52HPwMFrERMjHFlk5sKSrzZuLDiZpdJaw=; b=KqeQ0nAPr8XiQmr0mOV8eXlxUkB5zRO6pl6qYwFYUXkciv/VqmUEWHe8mcnArqVEK7FJvTD5O7217Mf4fHcKBHi1zaubPKwWSGr4gUlAdHBmDz2dVKaoLFoH5WCx6X1ak6eyUaurIcugSK7MCOIvJPwzYn9M3Oy/lDx3+/6oTIHidZfHelbaSFguCSH6NKkeKHEfFyJF9OZkK27RV3+K5Nj8JERHIuV/UgXizJQ0XNITdPCA6A6Zho5CIf6UvO6CmS7fpNms61eST1HMrvdLL68mVUF1Mqy7IMeMIz6LCWpFUhaC8ZMxHFJwqsqedR85xVTpbvZJDszdz+O1aq7Ttg==
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=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=xrWAwFRDwA52HPwMFrERMjHFlk5sKSrzZuLDiZpdJaw=; b=BmaWceP8rh9T3Bzsm+/rFHZLsZolnsfeo6fSnYxtizkvhmZ4LdYCOFwCA/KJ5rtFHPzpX5wxNlRNo51PlmY51SFVAphkxYOV2wmcQBqB9TJr4fP9ZCWqr/Pq3/W7wCXh/UhvCuYQg43FQv2wIAb6QQ75rKkQFFJq7rDoPc1veY0=
Received: from HE1PR0702MB3772.eurprd07.prod.outlook.com (2603:10a6:7:8e::14) by HE1PR0701MB2795.eurprd07.prod.outlook.com (2603:10a6:3:9b::17) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3174.8; Wed, 8 Jul 2020 18:05:30 +0000
Received: from HE1PR0702MB3772.eurprd07.prod.outlook.com ([fe80::546c:3b3:9193:3351]) by HE1PR0702MB3772.eurprd07.prod.outlook.com ([fe80::546c:3b3:9193:3351%6]) with mapi id 15.20.3174.020; Wed, 8 Jul 2020 18:05:30 +0000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
To: "quic@ietf.org" <quic@ietf.org>, "draft-ietf-quic-transport@ietf.org" <draft-ietf-quic-transport@ietf.org>
Subject: RE: WG last call comments on draft-ietf-quic-transport-29
Thread-Topic: WG last call comments on draft-ietf-quic-transport-29
Thread-Index: AdZVSFz+OetpiiZFSvGMix+HsfHEEgACfGJg
Date: Wed, 8 Jul 2020 18:05:29 +0000
Message-ID: <HE1PR0702MB3772880CC294F1F4884A473895670@HE1PR0702MB3772.eurprd07.prod.outlook.com>
References: <HE1PR0702MB37720D42E58ACB56A14E679495670@HE1PR0702MB3772.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR0702MB37720D42E58ACB56A14E679495670@HE1PR0702MB3772.eurprd07.prod.outlook.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: yes
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [158.174.104.67]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ef611861-9fd6-4f8f-8b90-08d82369801e
x-ms-traffictypediagnostic: HE1PR0701MB2795:
x-microsoft-antispam-prvs: <HE1PR0701MB2795C53CF09F8658E9A9F8CE95670@HE1PR0701MB2795.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: EMT3Py5+RMEhlS5TSb8XDsv+E2X3xhRQMOIV2wu+oF5Xjm1cHeCFQWPmx7utTw3q0+wjUp/vqId+jsj5lzJ2Y7XYkVi9KD2FpU0OeoLTyLgTeEadWo+gJoi+oYbt3Yf9WWU0Bjrx3JznFjDTaWhu2UNF81OTthprkUNQqQnV4ARIQrjU2wwR9Km5VmkAC8ntuivJo7mMd8mI7vHzayqx19sBKYlhWWdffe7FFnDFKlxo6POSlR2Gyl9EsJrFTrXBBPibJTPVdiS4cp7VngWXPXhBxQ+Aa4iiAHRwsCLfHUvIo4szbhN+9rQ/eGnK9Vk/ZgK49l0BkmR2wqCvubilJzI3u4yPUv8HwHdF+LpTuSru/SPUdfO93Mp2/QGjL259/0nMQKvN6EUsm887V75QOQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR0702MB3772.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(346002)(376002)(366004)(39860400002)(136003)(396003)(7696005)(33656002)(99936003)(450100002)(9686003)(316002)(55016002)(110136005)(66476007)(66616009)(76116006)(66446008)(66946007)(66556008)(64756008)(186003)(8936002)(8676002)(26005)(2940100002)(6506007)(53546011)(166002)(966005)(478600001)(83380400001)(5660300002)(2906002)(71200400001)(44832011)(52536014)(86362001)(579004); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: mi8gi/OX2PjWF0Ph0unR+axc0J8PHnqRGLkK0A6JLM2iIvgnYdsNI84qTBDnLQx7s+GOSgdTVKPyFsbkWSXNq5/xDd2YK9FLQHoQoM3w3hkDlVFLX+5TMD2AGGfKkhiNQhTWKARmahT1fAU1wyqN8wAHm58vXMFh4TeHl8BgxIVVfGO8Oa0dOsHnDaee1iy0Vqk0qAX0taywQc7TOAb6N/DqB/gbMWHYd63bSi47O0ItivqSgEdzfjJedFSR7xwNLtpIBcsoe77RZTFPcj7Pzsj4s4F+79FmgQUig/fxFmkh6kNhTosQlU4jeSGxCvurkELpoUZ8Hv19W3hfEB/85KXlyeOIj9CMxi+rWz3glV7I/KNx8mI8mjejq+wXowZw1zs8j7RZlonqIyFaOc2pKi+jbeHsjHnVs1atjpF2VJ6JntjdsI0EL63yHnlve0yuMJrOyNRjZHNDpmIWWoYfTRZj2WXHKeozNqnD0FZI8iIL36FV20d0zo2GIv7MPBi/
x-ms-exchange-transport-forked: True
Content-Type: multipart/signed; protocol="application/x-pkcs7-signature"; micalg=SHA1; boundary="----=_NextPart_000_0149_01D65563.2042F2B0"
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR0702MB3772.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ef611861-9fd6-4f8f-8b90-08d82369801e
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jul 2020 18:05:29.9709 (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: AtVI6Ga+iW4A50pMfvfl5ebc1JF2/dRAdA+hvgMwH8pJmcKIod8SA4prPqiD8y8B2+LhKUuGBd9QAGZ3yXcJHfp51zUgHxl8ayUNJJduDyY=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2795
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/F4L8MRfuKtZDKen1RMZr6Q2jGM0>
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, 08 Jul 2020 18:05:43 -0000

------=_NextPart_000_0149_01D65563.2042F2B0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_001_014A_01D65563.2042F2B0"


------=_NextPart_001_014A_01D65563.2042F2B0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

Fixing draft alias.

 

/Magnus

 

From: Magnus Westerlund 
Sent: den 8 juli 2020 20:05
To: quic@ietf.org; draft-ietf-quic-transport@ietf.rog
Subject: WG last call comments on draft-ietf-quic-transport-29

 

Hi

 

Sorry for not filing issues and instead giving you this dump. A bit short of
time so I wanted to get these in before the end of the last call. 

 

And I have noticed that some are really edge cases. So think them through
and then it is fine to say this is not relevant because of .

 

 

1.       Section 1.3: 

x (A..B):  Indicates that x can be any length from A to B; A can be
      omitted to indicate a minimum of zero bits and B can be omitted to
      indicate no set upper limit; values in this format always end on
      an octet boundary

There is an upper limit based on the protocol even in these cases, either
due to encoding restrictions or the protocol. 2^62-1 bytes in most cases for
length or data limits or the per packet limit where MPS will be a
restriction. Should that be made more explicit. 

 

2.       Section 3.2, Figure 3: 
The top most RESET_STREAM which leads to the Recv state. Shouldn't that go
to the RESET Recvd state immediately. If I interpret the figure it will take
two RESET_STREAMS until one end up in RESET RECVD
 

3.       Section 4.1: "

If a sender is blocked
   for a period longer than the idle timeout (Section 10.2), the
   connection might be closed even when data is available for
   transmission."

Who may close the conenction? both peers, or the sender that is blocked or
the receiver?

 

4.       Section 7.4.1: "

   In particular, a server that accepts 0-RTT data
   MUST NOT set values for the following parameters (Section 18.2) that
   are smaller than the remembered value of the parameters."

 

So far I have not seen any definition for how long TP parameters will be
remembered. I guess that there is a time limit on the 0-RTT keying material
stored in the client that is relevant her, however this is not at all
referenced here. Should there be a pointer or explanation? Because the above
normative statement appears to be missing the tie into how long the client
will remember theses remembered values.

 

5.       Section 8.1.3 and 8.1.4:

First of all I got the wrong impression of this section as the details about
address validation part, that you actually include the address is in the
next section 8.1.4. I don't know if there should be something done about
this or not. But my impression after 8.1.3 and before I read 8.1.4 that this
was not address validation, only client validation, i.e. this is a client I
talked to before. 

My actual question I have on these section is if it there should be
clarification on that the client should keep track of the token on a server
authority + client address/network scope. So that the client will not send
the token unless it is on the same network it was before. 

But maybe this last is unnecessary as the server will ignore the token if it
doesn't match. 
 

6.       Section 9.2:
 

  Receiving acknowledgments for data sent on the new path serves as
   proof of the peer's reachability from the new address.

 

This contradicts the text in Section 8.5:

 

Receipt of an acknowledgment for a packet containing

   a PATH_CHALLENGE frame is not adequate validation, since the

   acknowledgment can be spoofed by a malicious peer.

So this might be an intended differenation between path validation and
indication of basic reachability (assuming no hostility). Maybe that
exception also needs to be noted in the last paragraph in Section 9.2.

 

7.       Section 9.3.1: 

   If an endpoint skips validation of a peer address as described in
   Section 9.3, it does not need to limit its sending rate.
 

So I assume what is referenced in Section 9.3 is this: 
 

An endpoint MAY skip validation of a peer address if
   that address has been seen recently.  In particular, if an endpoint
   returns to a previously-validated path after detecting some form of
   spurious migration, skipping address validation and restoring loss
   detection and congestion state can reduce the performance impact of
   the attack.

 

So the question here is what is considered recently. I think the lifetime of
a address validation is significantly longer than the validity of the
congestion control state. 

 

8.       Section 10.1: 
"Endpoints that have some alternative
   means to ensure that late-arriving packets on the connection do not
   induce a response, such as those that are able to close the UDP
   socket, MAY use an abbreviated draining period which can allow for
   faster resource recovery."

 

So to me this assumes that the underlying system will not reuse the local
UDP port in the time it takes to drain the network. I assume even
applications may shoot itself in the foot if it insist on a local source
port for an outgoing QUIC connections and that was recently used. I assume
that this will not have any significant impact on a QUIC instance, and what
it does to another UDP protocol is all dependent.

 

10.   Section 10.2: "

If a max_idle_timeout is specified by either peer in its transport
   parameters (Section 18.2), the connection is silently closed and its
   state is discarded when it remains idle for longer than the minimum
   of both peers max_idle_timeout values and three times the current
   Probe Timeout (PTO)."

 

Should this really be the minimum and not the maximum. For very low values
of MAX_IDLE_TIMEOUT the QUIC stack is not even given a fair chance of
probing if the path is still there or not? And for larger value the 3*PTO
will always be setting the value. I would have expected the maximum, that
below 3*PTO it will not timeout, and when MAX_IDLE_TIMEOUT > 3*PTO that
value will be limit for how long probing is done. 

 

Doesn't the rule also prevent a stack being silent for longer than 3*PTOs?
That appears wasteful to force continuos communication if there  are no data
be sent. 

 

11.   Section 10.3:

Such an
   endpoint SHOULD limit the number of packets it generates containing a
   CONNECTION_CLOSE frame.

 

To what level should it be limited, e.g. one packet per 1/4 RTT? Or is the
argument that 

Any reduction is sufficient. To me it looks like a simple packet mirror on
path that sends the packets back to the sender will maintain the number of
packets in flight unless there is a reduction factor.

 

12.   Section 12.4:

Packet Payload {
     Frame (..) ...,
   }

   The payload of a packet that contains frames MUST contain at least
   one frame, and MAY contain multiple frames and multiple frame types.

 

Shouldn't the above be written as:

 

Packet Payload {
     Frame (1..) 1...,
   }

 

Each frame has  a minimal length of one octet, and there is a requirement of
at least one frame. I did note that there are no x.y definition. And that
the definition says there are 0 or more entries which isn't true here. I
don't know how much to do about the inconsistency in the notation for this
case?

 

13.   Section 17.2.2:

Length field for the Packet header is undefined. I would guess that it
contains the total length of the Initial Packet in bytes but that should be
defined. Applies also to the 0-RTT and Handshake packet.
 

14.   Section 17.2.5:

The value in the Unused field is selected randomly by the
   server.

Should this say that the receiver should ignore the value in the field?

 

 

15.   Section 19.9:

The Maximum Data (i) field as currently defined will be in many connections
the upper limit for how many packets can be sent in any connection due to
its bit limit. As this is a maximum value due to usage of the variable
encoding to 2^62-1 bytes. It is possible that this value could be reached as
around 2^52 packets approximately. An QUIC packet will be possible to
contain at least 1024 bytes, i.e. 10 bits worth of bytes. In a DC center
network with larger MTUs it is possible that already after 2^50 packets this
value will be exhausted.

Should I simply assume that this amount of data is such a big number that if
an application runs into the limit forcing it to restart the connection is a
minor issue. However considering that the limit in packets are relatively
more discussed, this limit is not much discussed and in fact there are no
mention in 19.9 what to do if that value reaches maximum that can be
encoded, i.e. close the connection. 
 


 16. Section 22.1.4: 

 

   All registrations in this document are assigned a permanent status

   and list as contact both the IESG (ietf@ietf.org <mailto:ietf@ietf.org> )
and the QUIC

   working group (quic@ietf.org <mailto:quic@ietf.org>
(mailto:quic@ietf.org)).

 

The IESG is recommending that registration owner for IETF STD documents are
IETF. The arguments are in this doc: 

https://datatracker.ietf.org/doc/draft-leiba-ietf-iana-registrations/

 

17.	Section 22:

 

An important question that for the high level structure of the registries
are the question if these registries are Version 1 specific, or  expected to
be used across multiple versions of QUIC? Because if the former then the
general heading for the registries should say QUIC Version 1. If they are
intended to be for multiple versions, what type of indication for which
version particular entries are valid are needed? 

 

 

 

 

 

 

Editorials:

 

A.      Section 8.2 uses PMTU without expansion. Before this point it is
only used in TOC. 

 

2.       Section 9.1: 

An endpoint MAY probe for peer reachability from a new local address
   using path validation Section 8.2 prior to migrating the connection
   to the new local address.

 

Missing parenthis around Section ref. 

 

3.       Section 9.6.3:

"

If the connection to the server's preferred address is not from the
   same client address, the server MUST protect against potential
   attacks as described in Section 9.3.1 and Section 9.3.2."

 

Shouldn't it say something more like:

If the client's packet flow to the server's preferred address for the
connection is not from the same client address, the server MUST protect
against potential attacks as described in Section 9.3.1 and Section 9.3.2.

 


------=_NextPart_001_014A_01D65563.2042F2B0
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-microsoft-com:office:office" =
xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" =
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=3DGenerator 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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
	{mso-style-priority:34;
	margin-top:0cm;
	margin-right:0cm;
	margin-bottom:0cm;
	margin-left:36.0pt;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";
	mso-fareast-language:SV;}
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:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle21
	{mso-style-type:personal;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.EmailStyle23
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
div.WordSection1
	{page:WordSection1;}
/* List Definitions */
@list l0
	{mso-list-id:48117755;
	mso-list-template-ids:-1737691218;}
@list l0:level1
	{mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l0:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1
	{mso-list-id:259991596;
	mso-list-template-ids:-1024305688;}
@list l1:level1
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level2
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level3
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level4
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level5
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level6
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level7
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level8
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l1:level9
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2
	{mso-list-id:331297180;
	mso-list-template-ids:-191828984;}
@list l2:level1
	{mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3
	{mso-list-id:432168385;
	mso-list-template-ids:254328628;}
@list l3:level1
	{mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l3:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4
	{mso-list-id:828449538;
	mso-list-template-ids:2129587564;}
@list l4:level1
	{mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l4:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5
	{mso-list-id:856116927;
	mso-list-template-ids:-1817015316;}
@list l5:level1
	{mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l5:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l6
	{mso-list-id:921766986;
	mso-list-template-ids:-2086125792;}
@list l6:level1
	{mso-level-start-at:2;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l6:level2
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l6:level3
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l6:level4
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l6:level5
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l6:level6
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l6:level7
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l6:level8
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l6:level9
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l7
	{mso-list-id:992294888;
	mso-list-template-ids:47746728;}
@list l7:level1
	{mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l7:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l7:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l7:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l7:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l7:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l7:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l7:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l7:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l8
	{mso-list-id:1008291809;
	mso-list-template-ids:1271284754;}
@list l8:level1
	{mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l8:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l8:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l8:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l8:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l8:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l8:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l8:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l8:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l9
	{mso-list-id:1294942753;
	mso-list-type:hybrid;
	mso-list-template-ids:2043084140 69009423 69009433 69009435 69009423 =
69009433 69009435 69009423 69009433 69009435;}
@list l9:level1
	{mso-level-start-at:17;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l9:level2
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l9:level3
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l9:level4
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l9:level5
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l9:level6
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l9:level7
	{mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l9:level8
	{mso-level-number-format:alpha-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l9:level9
	{mso-level-number-format:roman-lower;
	mso-level-tab-stop:none;
	mso-level-number-position:right;
	text-indent:-9.0pt;}
@list l10
	{mso-list-id:1545556071;
	mso-list-template-ids:-1970267712;}
@list l10:level1
	{mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l10:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l10:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l10:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l10:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l10:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l10:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l10:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l10:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l11
	{mso-list-id:1805005215;
	mso-list-template-ids:-1054304174;}
@list l11:level1
	{mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l11:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l11:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l11:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l11:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l11:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l11:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l11:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l11:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l12
	{mso-list-id:1876773561;
	mso-list-template-ids:-1519213824;}
@list l12:level1
	{mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l12:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l12:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l12:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l12:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l12:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l12:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l12:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l12:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l13
	{mso-list-id:1922793040;
	mso-list-template-ids:645560602;}
@list l13:level1
	{mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l13:level2
	{mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l13:level3
	{mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l13:level4
	{mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l13:level5
	{mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l13:level6
	{mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l13:level7
	{mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l13:level8
	{mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l13:level9
	{mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l14
	{mso-list-id:1925450704;
	mso-list-template-ids:612653602;}
@list l14:level1
	{mso-level-start-at:3;
	mso-level-tab-stop:36.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l14:level2
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:72.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l14:level3
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:108.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l14:level4
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:144.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l14:level5
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:180.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l14:level6
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:216.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l14:level7
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:252.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l14:level8
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:288.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l14:level9
	{mso-level-number-format:alpha-upper;
	mso-level-tab-stop:324.0pt;
	mso-level-number-position:left;
	text-indent:-18.0pt;}
@list l2:level1 lfo2
	{mso-level-start-at:2;}
@list l8:level1 lfo3
	{mso-level-start-at:4;}
@list l13:level1 lfo4
	{mso-level-start-at:5;}
@list l4:level1 lfo5
	{mso-level-start-at:7;}
@list l0:level1 lfo6
	{mso-level-start-at:8;}
@list l5:level1 lfo7
	{mso-level-start-at:10;}
@list l7:level1 lfo8
	{mso-level-start-at:11;}
@list l3:level1 lfo9
	{mso-level-start-at:12;}
@list l12:level1 lfo10
	{mso-level-start-at:13;}
@list l10:level1 lfo11
	{mso-level-start-at:15;}
ol
	{margin-bottom:0cm;}
ul
	{margin-bottom:0cm;}
--></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=3DSV =
link=3D"#0563C1" vlink=3D"#954F72"><div class=3DWordSection1><p =
class=3DMsoNormal>Fixing draft alias.<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p =
class=3DMsoNormal>/Magnus<o:p></o:p></p><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><div =
style=3D'border:none;border-left:solid blue 1.5pt;padding:0cm 0cm 0cm =
4.0pt'><div><div style=3D'border:none;border-top:solid #E1E1E1 =
1.0pt;padding:3.0pt 0cm 0cm 0cm'><p class=3DMsoNormal><b><span =
lang=3DEN-US style=3D'mso-fareast-language:SV'>From:</span></b><span =
lang=3DEN-US style=3D'mso-fareast-language:SV'> Magnus Westerlund =
<br><b>Sent:</b> den 8 juli 2020 20:05<br><b>To:</b> quic@ietf.org; =
draft-ietf-quic-transport@ietf.rog<br><b>Subject:</b> WG last call =
comments on =
draft-ietf-quic-transport-29<o:p></o:p></span></p></div></div><p =
class=3DMsoNormal><o:p>&nbsp;</o:p></p><p class=3DMsoNormal><span =
lang=3DEN-US>Hi<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>Sorry for not filing issues and instead giving you this =
dump. A bit short of time so I wanted to get these in before the end of =
the last call. <o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US>And I have noticed that some are really edge cases. So =
think them through and then it is fine to say this is not relevant =
because of &#8230;<o:p></o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p><p class=3DMsoNormal><span =
lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l11 level1 =
lfo1;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>1.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 1.3: <o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>x (A..B):&nbsp; Indicates that x can =
be any length from A to B; A can be<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
omitted to indicate a minimum of zero bits and B can be omitted =
to<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; indicate no set upper limit; values =
in this format always end on<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; an octet =
boundary<br><br>There is an upper limit based on the protocol even in =
these cases, either due to encoding restrictions or the protocol. 2^62-1 =
bytes in most cases for length or data limits or the per packet limit =
where MPS will be a restriction. Should that be made more explicit. =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l2 level1 =
lfo2;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 3.2, Figure 3: <br>The top =
most RESET_STREAM which leads to the Recv state. Shouldn't that go to =
the RESET Recvd state immediately. If I interpret the figure it will =
take two RESET_STREAMS until one end up in RESET =
RECVD<br>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l2 level1 =
lfo2;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 4.1: =
&quot;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>If a sender is blocked<br>&nbsp;&nbsp; =
for a period longer than the idle timeout (Section 10.2), =
the<br>&nbsp;&nbsp; connection might be closed even when data is =
available for<br>&nbsp;&nbsp; transmission.&quot;<br><br>Who may close =
the conenction? both peers, or the sender that is blocked or the =
receiver?<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l8 level1 =
lfo3;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>4.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 7.4.1: =
&quot;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;&nbsp; In particular, a server =
that accepts 0-RTT data<br>&nbsp;&nbsp; MUST NOT set values for the =
following parameters (Section 18.2) that<br>&nbsp;&nbsp; are smaller =
than the remembered value of the =
parameters.&quot;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>So far I have not seen any definition =
for how long TP parameters will be remembered. I guess that there is a =
time limit on the 0-RTT keying material stored in the client that is =
relevant her, however this is not at all referenced here. Should there =
be a pointer or explanation? Because the above normative statement =
appears to be missing the tie into how long the client will remember =
theses remembered values.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l13 level1 =
lfo4;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>5.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 8.1.3 and 8.1.4:<br><br>First =
of all I got the wrong impression of this section as the details about =
address validation part, that you actually include the address is in the =
next section 8.1.4. I don't know if there should be something done about =
this or not. But my impression after 8.1.3 and before I read 8.1.4 that =
this was not address validation, only client validation, i.e. this is a =
client I talked to before. <br><br>My actual question I have on these =
section is if it there should be clarification on that the client should =
keep track of the token on a server authority + client address/network =
scope. So that the client will not send the token unless it is on the =
same network it was before. <br><br>But maybe this last is unnecessary =
as the server will ignore the token if it doesn't match. =
<br>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l13 level1 =
lfo4;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>6.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section =
9.2:<br>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp; Receiving acknowledgments for =
data sent on the new path serves as<br>&nbsp;&nbsp; proof of the peer's =
reachability from the new address.<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>This contradicts the text in Section =
8.5:<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Receipt of an acknowledgment for a =
packet containing<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;&nbsp; a PATH_CHALLENGE frame is =
not adequate validation, since the<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;&nbsp; acknowledgment can be =
spoofed by a malicious peer.<br><br>So this might be an intended =
differenation between path validation and indication of basic =
reachability (assuming no hostility). Maybe that exception also needs to =
be noted in the last paragraph in Section 9.2.<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l4 level1 =
lfo5;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>7.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 9.3.1: =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;&nbsp;&nbsp;If an endpoint skips =
validation of a peer address as described in<br>&nbsp;&nbsp; Section =
9.3, it does not need to limit its sending =
rate.<br>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>So I assume what is referenced in =
Section 9.3 is this: <br>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>An endpoint MAY skip validation of a =
peer address if<br>&nbsp;&nbsp; that address has been seen =
recently.&nbsp; In particular, if an endpoint<br>&nbsp;&nbsp; returns to =
a previously-validated path after detecting some form of<br>&nbsp;&nbsp; =
spurious migration, skipping address validation and restoring =
loss<br>&nbsp;&nbsp; detection and congestion state can reduce the =
performance impact of<br>&nbsp;&nbsp; the =
attack.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>So the question here is what is =
considered recently. I think the lifetime of a address validation is =
significantly longer than the validity of the congestion control state. =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l0 level1 =
lfo6;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>8.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 10.1: <br>&quot;Endpoints that =
have some alternative<br>&nbsp;&nbsp; means to ensure that late-arriving =
packets on the connection do not<br>&nbsp;&nbsp; induce a response, such =
as those that are able to close the UDP<br>&nbsp;&nbsp; socket, MAY use =
an abbreviated draining period which can allow for<br>&nbsp;&nbsp; =
faster resource recovery.&quot;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>So to me this assumes that the =
underlying system will not reuse the local UDP port in the time it takes =
to drain the network. I assume even applications may shoot itself in the =
foot if it insist on a local source port for an outgoing QUIC =
connections and that was recently used. I assume that this will not have =
any significant impact on a QUIC instance, and what it does to another =
UDP protocol is all dependent.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l5 level1 =
lfo7;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>10.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 10.2: =
&quot;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>If a max_idle_timeout is specified by =
either peer in its transport<br>&nbsp;&nbsp; parameters (Section 18.2), =
the connection is silently closed and its<br>&nbsp;&nbsp; state is =
discarded when it remains idle for longer than the =
minimum<br>&nbsp;&nbsp; of both peers max_idle_timeout values and three =
times the current<br>&nbsp;&nbsp; Probe Timeout =
(PTO).&quot;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Should this really be the minimum and =
not the maximum. For very low values of MAX_IDLE_TIMEOUT the QUIC stack =
is not even given a fair chance of probing if the path is still there or =
not? And for larger value the 3*PTO will always be setting the value. I =
would have expected the maximum, that below 3*PTO it will not timeout, =
and when MAX_IDLE_TIMEOUT &gt; 3*PTO that value will be limit for how =
long probing is done. <o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Doesn't the rule also prevent a stack =
being silent for longer than 3*PTOs? That appears wasteful to force =
continuos communication if there&nbsp; are no data be sent. =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l7 level1 =
lfo8;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>11.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 10.3:<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Such an<br>&nbsp;&nbsp; endpoint =
SHOULD limit the number of packets it generates containing =
a<br>&nbsp;&nbsp; CONNECTION_CLOSE frame.<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>To what level should it be limited, =
e.g. one packet per 1/4 RTT? Or is the argument that =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Any reduction is sufficient. To me it =
looks like a simple packet mirror on path that sends the packets back to =
the sender will maintain the number of packets in flight unless there is =
a reduction factor.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l3 level1 =
lfo9;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>12.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 12.4:<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Packet Payload =
{<br>&nbsp;&nbsp;&nbsp;&nbsp; Frame (..) ...,<br>&nbsp;&nbsp; =
}<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;&nbsp; The payload of a packet =
that contains frames MUST contain at least<br>&nbsp;&nbsp; one frame, =
and MAY contain multiple frames and multiple frame =
types.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Shouldn't the above be written =
as:<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Packet Payload =
{<br>&nbsp;&nbsp;&nbsp;&nbsp; Frame (1..) 1...,<br>&nbsp;&nbsp; =
}<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Each frame has&nbsp; a minimal length =
of one octet, and there is a requirement of at least one frame. I did =
note that there are no x&#8230;y definition. And that the definition =
says there are 0 or more entries which isn't true here. I don't know how =
much to do about the inconsistency in the notation for this =
case?<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l12 level1 =
lfo10;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>13.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 17.2.2:<br><br>Length field =
for the Packet header is undefined. I would guess that it contains the =
total length of the Initial Packet in bytes but that should be defined. =
Applies also to the 0-RTT and Handshake =
packet.<br>&nbsp;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l12 level1 =
lfo10;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>14.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 17.2.5:<br><br>The value in =
the Unused field is selected randomly by the<br>&nbsp;&nbsp; =
server.<br><br>Should this say that the receiver should ignore the value =
in the field?<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><i><span =
lang=3DEN-US =
style=3D'font-size:9.0pt;color:#595959;mso-fareast-language:SV'>&nbsp;</s=
pan></i><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l10 level1 =
lfo11;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>15.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp; </span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 19.9:<br><br>The Maximum Data =
(i) field as currently defined will be in many connections the upper =
limit for how many packets can be sent in any connection due to its bit =
limit. As this is a maximum value due to usage of the variable encoding =
to 2^62-1 bytes. It is possible that this value could be reached as =
around 2^52 packets approximately. An QUIC packet will be possible to =
contain at least 1024 bytes, i.e. 10 bits worth of bytes. In a DC center =
network with larger MTUs it is possible that already after 2^50 packets =
this value will be exhausted.<br><br>Should I simply assume that this =
amount of data is such a big number that if an application runs into the =
limit forcing it to restart the connection is a minor issue. However =
considering that the limit in packets are relatively more discussed, =
this limit is not much discussed and in fact there are no mention in =
19.9 what to do if that value reaches maximum that can be encoded, i.e. =
close the connection. <br>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><br>&nbsp;16. Section 22.1.4: =
<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p>&nbsp;</o:p></span></p><pre><span =
lang=3DEN-US>&nbsp;&nbsp; All registrations in this document are =
assigned a permanent status<o:p></o:p></span></pre><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-fareast-language:SV'>&nbsp;&nbsp; and list as contact both the =
IESG (<a href=3D"mailto:ietf@ietf.org">ietf@ietf.org</a>) and the =
QUIC<o:p></o:p></span></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'font-size:10.0pt;font-family:"Courier =
New";mso-fareast-language:SV'>&nbsp;&nbsp; working group (<a =
href=3D"mailto:quic@ietf.org">quic@ietf.org</a> (<a =
href=3D"mailto:quic@ietf.org)">mailto:quic@ietf.org)</a>).<o:p></o:p></sp=
an></p><p class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'text-indent:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>The IESG is recommending that =
registration owner for IETF STD documents are IETF. The arguments are in =
this doc: <o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'text-indent:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><a =
href=3D"https://datatracker.ietf.org/doc/draft-leiba-ietf-iana-registrati=
ons/">https://datatracker.ietf.org/doc/draft-leiba-ietf-iana-registration=
s/</a><o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p>&nbsp;</o:p></span></p><ol =
style=3D'margin-top:0cm' start=3D17 type=3D1><li =
class=3DMsoListParagraph style=3D'margin-left:0cm;mso-list:l9 level1 =
lfo12'><span lang=3DEN-US style=3D'mso-fareast-language:SV'>Section =
22:<o:p></o:p></span></li></ol><p class=3DMsoNormal =
style=3D'margin-left:36.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:36.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>An important question that for the =
high level structure of the registries are the question if these =
registries are Version 1 specific, or &nbsp;expected to be used across =
multiple versions of QUIC? Because if the former then the general =
heading for the registries should say QUIC Version 1. If they are =
intended to be for multiple versions, what type of indication for which =
version particular entries are valid are needed? =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:36.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:36.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:36.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:36.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><o:p>&nbsp;</o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Editorials:<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l1 level1 =
lfo13;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>A.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 8.2 uses PMTU without =
expansion. Before this point it is only used in TOC. =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l6 level1 =
lfo14;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>2.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 9.1: <o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>An endpoint MAY probe for peer =
reachability from a new local address<br>&nbsp;&nbsp; using path =
validation Section 8.2 prior to migrating the connection<br>&nbsp;&nbsp; =
to the new local address.<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Missing parenthis around Section ref. =
<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal =
style=3D'margin-left:27.0pt;text-indent:-18.0pt;mso-list:l14 level1 =
lfo15;vertical-align:middle'><![if !supportLists]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'><span =
style=3D'mso-list:Ignore'>3.<span style=3D'font:7.0pt "Times New =
Roman"'>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; =
</span></span></span><![endif]><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Section 9.6.3:<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&quot;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>If the connection to the server's =
preferred address is not from the<br>&nbsp;&nbsp; same client address, =
the server MUST protect against potential<br>&nbsp;&nbsp; attacks as =
described in Section 9.3.1 and Section =
9.3.2.&quot;<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>&nbsp;<o:p></o:p></span></p><p =
class=3DMsoNormal style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>Shouldn't it say something more =
like:<o:p></o:p></span></p><p class=3DMsoNormal =
style=3D'margin-left:27.0pt'><span lang=3DEN-US =
style=3D'mso-fareast-language:SV'>If the client's packet flow to the =
server's preferred address for the connection is not from the same =
client address, the server MUST protect against potential attacks as =
described in Section 9.3.1 and Section 9.3.2.<o:p></o:p></span></p><p =
class=3DMsoNormal><span =
lang=3DEN-US><o:p>&nbsp;</o:p></span></p></div></div></body></html>
------=_NextPart_001_014A_01D65563.2042F2B0--

------=_NextPart_000_0149_01D65563.2042F2B0
Content-Type: application/pkcs7-signature;
	name="smime.p7s"
Content-Transfer-Encoding: base64
Content-Disposition: attachment;
	filename="smime.p7s"

MIAGCSqGSIb3DQEHAqCAMIACAQExCzAJBgUrDgMCGgUAMIAGCSqGSIb3DQEHAQAAoIIVdjCCAyAw
ggIIoAMCAQICAR0wDQYJKoZIhvcNAQEFBQAwOTELMAkGA1UEBhMCRkkxDzANBgNVBAoTBlNvbmVy
YTEZMBcGA1UEAxMQU29uZXJhIENsYXNzMiBDQTAeFw0wMTA0MDYwNzI5NDBaFw0yMTA0MDYwNzI5
NDBaMDkxCzAJBgNVBAYTAkZJMQ8wDQYDVQQKEwZTb25lcmExGTAXBgNVBAMTEFNvbmVyYSBDbGFz
czIgQ0EwggEiMA0GCSqGSIb3DQEBAQUAA4IBDwAwggEKAoIBAQCQF0o1ncrwDZbHRPoWN/xIvb1/
gC01O+FvqGepvwMcTYxvMkfVQWikEwTBNQyahEP8XB3/ibPoFxjNkV/7iePqv05dfBsm03V57eaE
41flrSnE9Doo56V7hDZps/1edr2jLZnTkE4jKH0YY/FUOyaddluXQrL/rvBO7N05lU6DBn/nSUDI
xQGyVFpmHT38+ek8Cp6BuHDwAYvkI1R8yK74kB4AlnLUVM9hI7zq+50CldG2uXE6aQg/D7ThQseI
9T+YqKe6HOBxce9YV4FQelxrdEYOgwOYw46obvJ2Mm4ng8Jz89wY6LST6nVEawRgIHFXh53zvqCQ
Iz2KJOHaIdvDAgMBAAGjMzAxMA8GA1UdEwEB/wQFMAMBAf8wEQYDVR0OBAoECEqgqliE0148MAsG
A1UdDwQEAwIBBjANBgkqhkiG9w0BAQUFAAOCAQEAWs6H+RZyFVdLHdmb56ImMOyTZ9/WLdI0r/c4
pc6rFrmrL3w1y6zQD7RMK/yA72uMkV82dvfbsxsZ6vSyEf1hcUS/KLM6Hb+zQ+ifv9wxCHGwnY3W
NEcykMZlJPegSnwEc485bxeMcrW9S8h6+HuDwyhOnAnqZz+yZwQbwxTa+OdJJJHQHWr6YTnva+ch
dQYH2BK0ISBwQnGB2jyaNr6mWw1qbJofkXv5+e9Cuk5OnswMjZTc2UWcXuxCUGOu9F3EsRLcyjuo
Lp0UWgV1t+zXY+K6NbYECJHo2p2c9ma1GKwKplQmNDPSG8HUfxo6jguqMm7b/E8ln9kyx5ZacKzf
TDCCBX0wggRloAMCAQICEQCH7S4aKCZKxRmqOuu5DaLLMA0GCSqGSIb3DQEBCwUAMDkxCzAJBgNV
BAYTAkZJMQ8wDQYDVQQKEwZTb25lcmExGTAXBgNVBAMTEFNvbmVyYSBDbGFzczIgQ0EwHhcNMTQx
MjA1MDgxOTE1WhcNMjEwNDA1MTAyOTAwWjA3MRQwEgYDVQQKDAtUZWxpYVNvbmVyYTEfMB0GA1UE
AwwWVGVsaWFTb25lcmEgUm9vdCBDQSB2MTCCAiIwDQYJKoZIhvcNAQEBBQADggIPADCCAgoCggIB
AMK+6yfwIaPzaSZVfp3FVRaRXP3vIb9TgHot0pGMYzHw7CTww6XScnwQbfQ3t+XmfHnqjLWCi65I
tqwA3GV17CpNX8GH9SBlK4GoRz6JI5UwFpB/6FcHSOcZrr9FZ7E3GwYq/t75rH2D+1665I+XZ75L
jo1kB1c4VWk0Nj0TSO9P4tNmHqTPGrdeNjPUtAa9GAH9d4RQAEX1jF3oI7x+/jXh7VB7qTCNGdMJ
jmhnXb88lxhTuylixcpecsHHltTbLaC0H2kD7OriUPEMPPCs81Mt8Bz17Ww5OXOAFshSsCPN4D7c
3TxHoLs1iuKYaIu+5b9y7tL6pe0S7fyYGKkmdtwoSxAgHNN/Fnct7W+A90m7UwW7XWjH1Mh1Fj+J
Wov3F0fUTPHSiXk+TT2YqGHeOh7S+F4D4MHJHIzTjU3TlTazN19jY5szFPAtJmtTfImMMsJu7D0h
ADnJoWjiUIMusDor8zagrC/kb2HCUQk5PotTubtn2txTuXZZNp1D5SDgPTJghSJRt8czu90VL6R4
pgd7gUY2BIbdeTXHlSw7sKMXNeVzH7RcWe/a6hBle3rQf5+ztCo3O3CLm1u5K7fsslESl1MpWtTw
EhDcTwK7EpIvYtQ/aUN8Ddb8WHUBiJ1YFkveupD/RwGJBmr2X7KQarMCpgKIv7NHfirZ1fpoeDVN
AgMBAAGjggGAMIIBfDBOBggrBgEFBQcBAQRCMEAwPgYIKwYBBQUHMAKGMmh0dHA6Ly9jYS50cnVz
dC50ZWxpYXNvbmVyYS5jb20vc29uZXJhY2xhc3MyY2EuY2VyMA8GA1UdEwEB/wQFMAMBAf8wGQYD
VR0gBBIwEDAOBgwrBgEEAYIPAgMBAQIwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQWBBTwj1k4ALP1
j5qWDNXr+nuqF+gTEjCBuQYDVR0fBIGxMIGuMG+gbaBrhmlsZGFwOi8vY3JsLTEudHJ1c3QudGVs
aWFzb25lcmEuY29tL2NuPVNvbmVyYSUyMENsYXNzMiUyMENBLG89U29uZXJhLGM9Rkk/Y2VydGlm
aWNhdGVyZXZvY2F0aW9ubGlzdDtiaW5hcnkwO6A5oDeGNWh0dHA6Ly9jcmwtMi50cnVzdC50ZWxp
YXNvbmVyYS5jb20vc29uZXJhY2xhc3MyY2EuY3JsMBMGA1UdIwQMMAqACEqgqliE0148MA0GCSqG
SIb3DQEBCwUAA4IBAQAQ1elFTM6fGkQ/aRKdkUZicO3Cb9uzBJOpOtFctw+1El0/17lsjoVvJkZB
D3KnUobnrriFdAa+7FAN55KLmZeB/3Y2bG0bB4toSyaVHjOQnQY9M0dv8U852w0Q7GwchKfebLUI
bh9TMt2hI3Xc6j4knFTBUo7C1WAfO51K4bn1irmX6/Ej2VTgiOFsvOAny28W6enFSEQpSHw60VhN
fSttSqTOxyrRR/7kW7Y8yb/3DZDZ/dH6ZCfx/y+BNIv2NuSd85M9HXUzplXXohti4Ql/qeaMn6by
Ius6XlMWZZfkdVRvTuk2PkeC7UmAJ2+/DUWOPpawaytMXVfF4Hvxk34NMIIGBzCCA++gAwIBAgIQ
C0ZtzXB7bjBlrrZreXF57TANBgkqhkiG9w0BAQsFADBHMQswCQYDVQQGEwJTRTERMA8GA1UECgwI
RXJpY3Nzb24xJTAjBgNVBAMMHEVyaWNzc29uIE5MIEluZGl2aWR1YWwgQ0EgdjMwHhcNMTcxMjE1
MDcyMjIzWhcNMjAxMjE1MDcyMjIyWjBwMREwDwYDVQQKDAhFcmljc3NvbjEaMBgGA1UEAwwRTWFn
bnVzIFdlc3Rlcmx1bmQxLTArBgkqhkiG9w0BCQEWHm1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29u
LmNvbTEQMA4GA1UEBRMHZXJhbXN3ZDCCASIwDQYJKoZIhvcNAQEBBQADggEPADCCAQoCggEBALCp
R2bwd07JixA7T0ohRSgIe90tsAKbfpWqoOXl06qJ6p80/cpBBi9ncfZgU/tlmYiCsaOMNrIrFZdx
BGE6l05HLabq+3DdvYCwvBd7SRxiNrFFaTvQMKVazflLhxFXrR7e4XcVvbmHdCySfEz+v8BpCHwB
WmcZWVJ+/TtnhxJX4odYlSIk2Vy3BHtawSbc4VDUR1oDptr0JQyeLAqYoBhaucPl0kb4hEDJEGUb
8NQkJm9+UEvwv09+qIMyERw7gHZKEmolDmP0tnS6eB5MLzjoPrQA6Wh5K23ZnZ4yhq2EpyYoJscN
eKSboMS/1W9hHlXIKQH1VbLey5uDzj0SPPsCAwEAAaOCAcQwggHAMEgGA1UdHwRBMD8wPaA7oDmG
N2h0dHA6Ly9jcmwudHJ1c3QudGVsaWEuY29tL2VyaWNzc29ubmxpbmRpdmlkdWFsY2F2My5jcmww
gYIGCCsGAQUFBwEBBHYwdDAoBggrBgEFBQcwAYYcaHR0cDovL29jc3AyLnRydXN0LnRlbGlhLmNv
bTBIBggrBgEFBQcwAoY8aHR0cDovL2NhLnRydXN0LnRlbGlhc29uZXJhLmNvbS9lcmljc3Nvbm5s
aW5kaXZpZHVhbGNhdjMuY2VyMCkGA1UdEQQiMCCBHm1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29u
LmNvbTBVBgNVHSAETjBMMEoGDCsGAQQBgg8CAwEBEjA6MDgGCCsGAQUFBwIBFixodHRwczovL3Jl
cG9zaXRvcnkudHJ1c3QudGVsaWFzb25lcmEuY29tL0NQUzAdBgNVHSUEFjAUBggrBgEFBQcDBAYI
KwYBBQUHAwIwHQYDVR0OBBYEFOYr7oaVOdVuFIQQwVsH/F7FPN+2MB8GA1UdIwQYMBaAFBx7GZ6X
nHasID3Y3OORauPbLaZTMA4GA1UdDwEB/wQEAwIFoDANBgkqhkiG9w0BAQsFAAOCAgEAZ9BSrpIN
NFDf3PxEqcUiGmE67HfJYhxzLuay6TgTTmnKRjQTBjYFAw7eEIoYaEEd3L4WFwqwDOfTU78NBzZY
Kh2aBHlWO2JySWJyVwwi1H5CuQ59vBN0K88pJBeoIlDlw8hfZoVmG0gJCcsdGI9F3PHp98GDcqBW
BKo5SrWa3VdKXIBcxHl1S0vA1q80su/in1LQzhIjOh98zt57KvvigZrDokipFp+KGBEWYOShJRAB
4rPWr/tyiGhD5zgLfEEVkaRXxmeHfPRdeqhbxJbqeZ+5fOuBasZwtn64g6OIS0GOhDWjmmCIoV4W
5dlGMQBg5PPWiZv0uaWMqu8M5viityHFJetK5nPEiZbekFysNMFxDhNTLm2rmCjLGndrPIw/qxJF
6fmoE0ZfrHs1mkcRwacblCg3ejIcA4oN0mYtaj+w/w7OFfiSyI41CXNuZfbbzBgvfpaiND/rzCN2
cq6LtDTX2+ebi0GqtfDvuwWfCr+47xXcWMlIG8UNEjxIsocpXCxwJiXiwkGomR5gkRAZAiykn9Du
JRNk61c3Tg9/MI87kNu1N1HXVQg/REN7Re6OhFYacSSVJQesXv9lFsMuGZWu9XSi1IWpHVazeWm8
8ahVr8zgE/ZwWth82FQbaW3Luihoe9mCfjO/X2vYiJHEAoFJ8N4CAHlnf/5+GG2NkIQwggbCMIIE
qqADAgECAhBTuH6D4ZyZKJOwm0kc7LjrMA0GCSqGSIb3DQEBCwUAMDcxFDASBgNVBAoMC1RlbGlh
U29uZXJhMR8wHQYDVQQDDBZUZWxpYVNvbmVyYSBSb290IENBIHYxMB4XDTE1MTAyNzEyMTY0NloX
DTI1MTAyNzEyMTY0NlowRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNzc29uMSUwIwYDVQQD
DBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYzMIICIjANBgkqhkiG9w0BAQEFAAOCAg8AMIIC
CgKCAgEA7PLfAAC4UPKnu9hUt8aT9+PBqjvUw0Y0tLPOXkO2NC0y2XZks9nJfpWKrNM30k5vu5no
rG4ZKlF5C+3xc6HuIiGQof1bmFGluNOwmZQwl3rOJ+E6k0rqJJTerjj4WOxAvWVW1yC5S4Ubppk3
Q3cYVVuC3qNGsBIXy3/fDL1sc8Ah8zI/JumDpjY8fn/U3CRN6mgNKYrr0sZX6VXYgrpT05ZrJldk
UgUgMKgbIWWEXEASA36pnb5GqD/RMzSgIe8o7YQtIaYB2cmTCLNHjaOL9j1JhNK4bvmbNJ7o58IZ
YzwNv/G/L/bRosQ9c27U+86DNjrdZnpyaRaeMyVUn3SlYLaFqoObdh/xNF2NS8CXs/PVtO57HBKH
MgZqQvsyQJisSocxFqiMj9VK2WhCBbvoTvrNDZvLDlDGuE5RuKwFIpHOVOU5lCBgUUBsbpWIXwM6
kmH/KC1DC5MtQzmvXkbt7KdBXUAxM0JZxf4dS+ACtTDpF9b0vny4DrwaOS0VNXyz1GUOxSqw1wup
5dpXbxLZYx1rLRgZqr9uWhLwAPsq66ZQof5GL0gY72Ym8/Tm28MeMqku+/zRzdYsmclT9rOdgdgS
3b6OMoc5Op0ZPEv/Mx2lFJAVK674ozw2hiuRTVUmoqBr5AuyCoqCEyn32C7U/V7oqyqx5Yd1c5Gs
xuOqQFcCAwEAAaOCAbgwggG0MIGKBggrBgEFBQcBAQR+MHwwLQYIKwYBBQUHMAGGIWh0dHA6Ly9v
Y3NwLnRydXN0LnRlbGlhc29uZXJhLmNvbTBLBggrBgEFBQcwAoY/aHR0cDovL3JlcG9zaXRvcnku
dHJ1c3QudGVsaWFzb25lcmEuY29tL3RlbGlhc29uZXJhcm9vdGNhdjEuY2VyMBIGA1UdEwEB/wQI
MAYBAf8CAQAwVQYDVR0gBE4wTDBKBgwrBgEEAYIPAgMBAQIwOjA4BggrBgEFBQcCARYsaHR0cHM6
Ly9yZXBvc2l0b3J5LnRydXN0LnRlbGlhc29uZXJhLmNvbS9DUFMwSwYDVR0fBEQwQjBAoD6gPIY6
aHR0cDovL2NybC0zLnRydXN0LnRlbGlhc29uZXJhLmNvbS90ZWxpYXNvbmVyYXJvb3RjYXYxLmNy
bDAdBgNVHSUEFjAUBggrBgEFBQcDAgYIKwYBBQUHAwQwDgYDVR0PAQH/BAQDAgEGMB0GA1UdDgQW
BBQcexmel5x2rCA92NzjkWrj2y2mUzAfBgNVHSMEGDAWgBTwj1k4ALP1j5qWDNXr+nuqF+gTEjAN
BgkqhkiG9w0BAQsFAAOCAgEAUFhr8dWMO7Quq1dDyIynw8sWmpyF/jWSxBjpHUCyhltoFS7Q1CUB
D0bOULWmYjmzRwme5pkjTFXpOJZLf9Han1SBbrVcP0JMhRsAvfWZjcF0l/c/jqDMqBARxr8OUWOr
0ZWa49Lir3QEs2C+CjGge5tzcLqzQ5pjWxudrLkSGe+sAThDnXUWXGYk8udGZAamJ55drdw96AV9
jWQkMrLIVHKkXVG5Etdx0wiAoTLk1fVtLcz11DiaCZSZVPZ3fdSIpIRhDqz8H4sVprPgvLBdK/aj
dbiRsehCzzohay3zbXDDTDGwKkR8KUi8Xt8HDZCRsb/U/C7MC4tVK0SEPOQCo6swZy0rI0RoGzIC
fsSrZ4JrxANeeSZqCn1A+w0Wz+iqdeP2PVxW0f1rg4/OG2DSl3uB3Q3NT/lDGJtepti+i5CCKEZc
dAOZoviu43sLhqsxSpGjzZidESwovuHeP+O2bNwwtz1DTsXThBB3+JJHVjmkiLo900GITb/i7IBd
Loo4gZms9s1BQ2tm3CJCmpA2XwBTOB6B8/CtgWUWhyloXd3Wbmv7ZUoqqJFBV9g8Zh5mdZ+RzPTo
mgCFz/2aNsddI/2G9ZjN4tG6hmocZR2M5f0MhBv3bo6d5XsLlYwiNJjw5GRqYb8cqqeCaPKkveBJ
zqgb8ToH7WLoOzmPRCmPlpAxggMCMIIC/gIBATBbMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MwIQC0ZtzXB7bjBl
rrZreXF57TAJBgUrDgMCGgUAoIIBfDAYBgkqhkiG9w0BCQMxCwYJKoZIhvcNAQcBMBwGCSqGSIb3
DQEJBTEPFw0yMDA3MDgxODA1MjhaMCMGCSqGSIb3DQEJBDEWBBQ8HrQzfnBv6RC+PQ3yRybin/je
8jBDBgkqhkiG9w0BCQ8xNjA0MAoGCCqGSIb3DQMHMA4GCCqGSIb3DQMCAgIAgDANBggqhkiG9w0D
AgIBQDAHBgUrDgMCGjBqBgkrBgEEAYI3EAQxXTBbMEcxCzAJBgNVBAYTAlNFMREwDwYDVQQKDAhF
cmljc3NvbjElMCMGA1UEAwwcRXJpY3Nzb24gTkwgSW5kaXZpZHVhbCBDQSB2MwIQC0ZtzXB7bjBl
rrZreXF57TBsBgsqhkiG9w0BCRACCzFdoFswRzELMAkGA1UEBhMCU0UxETAPBgNVBAoMCEVyaWNz
c29uMSUwIwYDVQQDDBxFcmljc3NvbiBOTCBJbmRpdmlkdWFsIENBIHYzAhALRm3NcHtuMGWutmt5
cXntMA0GCSqGSIb3DQEBAQUABIIBADh8v1DmTSiwvcTHTvng4jrNFAnThP6QT9f0XYzJ4hj7DnMZ
OyB0YGdeRXRzCOK8BrPOkVmnud2T/J7Az9xW6G2vDV72oRWNF4NqWNRhZxgD7IB8WhVIybumJPQo
BxjN61xFrcn2+V9zJUBzB9iPMHk4sJeE1kZ9ByPQBRekM6ER45LpIyAnUC2HNB+OMiPLw9ap+JED
Qr504zF0Sv4UaepQUNzunVKKBrx3nDqSjfx5H3foFDWs9PuZFOzBWjPP6SDP913SJepNUCfH/tJo
7ggm6ekqhI3UmimTIKnwlPfmrCaak66XgoGKzup5vs3d7ByjYmXTP8Yd49O9UT2X8YkAAAAAAAA=

------=_NextPart_000_0149_01D65563.2042F2B0--


From nobody Wed Jul  8 14:30:15 2020
Return-Path: <pravb@microsoft.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 7AD973A00E4 for <quic@ietfa.amsl.com>; Wed,  8 Jul 2020 14:30:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 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, DKIM_VALID_EF=-0.1, HTML_MESSAGE=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=microsoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id foaiBuMLkrkh for <quic@ietfa.amsl.com>; Wed,  8 Jul 2020 14:30:11 -0700 (PDT)
Received: from NAM06-BL2-obe.outbound.protection.outlook.com (mail-eopbgr650121.outbound.protection.outlook.com [40.107.65.121]) (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 64FE63A00E3 for <quic@ietf.org>; Wed,  8 Jul 2020 14:30:10 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=TAIKD1pRqPzKHrJWnI4bW5tfMaKdKACwfcqhZhgUdjJ7WPHz0hZSoSAmK1GOOlMYhqtRPteOYv+GPvHpOdI18a7IEXeR7eICEk7OEAhvedvxCAZPmvgkNVmvrwP7AxlRmtKMCb5MDyTYRbcvh/tlJjV09UG6/SRwJpTnlIiSYoiWHK1S4cbXndRZGEATqWOksYrGUK5TyOZaSEoKYJULakoR3Mi25CylOo+hazlcBfU4lcN7/iW/KfBHKTQbipdclhBJs18U4MlF+cZhDZb/7L+UR//r/4NzOXjTFJrOTf1XpHVSwTkgsEiV9JaryKxXtDPmkwIaep2zYZe+EdXXMQ==
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=fma25seJqYV+GsqSNDKIGAd6OYn0ci9w67tCxXb+8so=; b=h3x+6Q4cCSr35FU/FSOecU8bbVqjEj6Ca88AaE6Y6QORSQ0nv549Qm+ldp38pYw7fcGNCIgeM9Ecq6gfcWccfrkFGzth8Etnd7pXBToZ9M4wNehpM4AKabZjcwW4pWJWDOAOHL/GHnUGQmpqKSeyKfTN7zXLdgUNZ+KbU6iteSrW3GKqDzdRlKBPhoA5lu8gXn+2NvAZwNWPlUlxViCAqhPiMl8JnYRe98wwnuRxr4vwnOFdsUFVrzdV9J3yyrBKbsKpbdiqC1gKsPVLxlgOFeGx2cKqC2szMgOcEEjpB8SpKdpIO9hRNjF1naapxHDBoICP09HJdzUaUKwzK7ZQBA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=fma25seJqYV+GsqSNDKIGAd6OYn0ci9w67tCxXb+8so=; b=R308UJNyCZzoNtkzhf5RAYftiT98IerKg8czgOHgg3xNZV9k2z+ZiFz7zLEh12XMZhwlibJMCVQoXeUMYNOJHZc2qLm+AzJuGbHTzsGohRXF87zkFDIH+1tQz5YjQJlChnrs4QxIu3NvSZ8Sxf4BXa/Gx2wHftijOAWqhIYCplQ=
Received: from MN2PR00MB0736.namprd00.prod.outlook.com (2603:10b6:208:1dc::17) by BL0PR00MB0817.namprd00.prod.outlook.com (2603:10b6:208:1c8::8) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3214.0; Wed, 8 Jul 2020 21:30:00 +0000
Received: from MN2PR00MB0736.namprd00.prod.outlook.com ([fe80::180c:4e10:79a8:e18e]) by MN2PR00MB0736.namprd00.prod.outlook.com ([fe80::180c:4e10:79a8:e18e%9]) with mapi id 15.20.3207.000; Wed, 8 Jul 2020 21:30:00 +0000
From: Praveen Balasubramanian <pravb@microsoft.com>
To: IETF QUIC WG <quic@ietf.org>
Subject: WGLC review of draft-ietf-quic-recovery-29
Thread-Topic: WGLC review of draft-ietf-quic-recovery-29
Thread-Index: AdZVbt/Rv8RxmVSLQP+4+5gZJ/6HOg==
Date: Wed, 8 Jul 2020 21:29:59 +0000
Message-ID: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=true; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2020-07-08T21:29:58Z;  MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=38f37264-26b9-4a32-8fcb-b59ba0732dd4; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [2001:4898:80e8:3:95d5:3f73:f682:d302]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 686a6004-d7ab-4cc2-d7dc-08d823861197
x-ms-traffictypediagnostic: BL0PR00MB0817:
x-microsoft-antispam-prvs: <BL0PR00MB0817A9304DCCB5AA4D5482CAB6670@BL0PR00MB0817.namprd00.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: BQb2fUTUtCAWKYeg/ypCY/9GEkCzDPp3BH5ng2rwSCZ1JCU4OGqAkbBjeKQludp+1HxuQbklSgew1TwlnhcH7tOXB9nsoZMAwkb8aQzo96rsJyWJJVulhGOTVJbVJs63rNP/pU8pcNV/tYSvq4kbAxFFb1C02lmfOnV9G/ZZ7jbpiSCtPL0mj6VyUK9Eq54F92xaTpnn/sTxlIbdCeuhTPjBlKCsHe0ecdF2Px8ACKYPHtjZs4QQOLjX79MhXcbMpEaHXE5CrJQf5zKDhq3VYNvGCkUi1fDotKCQztJ9o3BRayUuE4FkhnrDH6rNkKVqDKePlufqtNZK6S6IRvj+gg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:MN2PR00MB0736.namprd00.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(366004)(396003)(376002)(346002)(136003)(39860400002)(33656002)(478600001)(7696005)(86362001)(52536014)(8676002)(8990500004)(83380400001)(5660300002)(9686003)(66476007)(76116006)(66446008)(64756008)(66556008)(66946007)(2906002)(186003)(8936002)(6916009)(6506007)(10290500003)(55016002)(82950400001)(82960400001)(71200400001)(316002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: 9a1mGpoWsy3Z10l/oZDfwc0wwLODG5r83hrwDgzQvduxg/0L+hdOX5r/wkS3Wt4oU+ZL0Pscw0Uny7SkqchQhLxYJrxg9jMrUXGKryRWRVtzTiMeaXkBAuGXZFT2P1GZDfrJwLt41TA2ny3HLo4vcQHWI0kfqGl4Bp+TGolBnka3V7PEifHIiEhn4FzZ0wZZsqGvMIqGhelSove5XMvbtyxRw2VaW8Q9vs93HHAvvtxytlCpUo7mxB0dS5KGH2GDUOZbUj8twaUDvbddYceSyJfo0Mvpt0pTSHEF+ncpgK/TSbg2gYzRWZZZ1p58NPh7hx1MO4961Qrnh5g6VMX4hxdy5lzWIpRBTYzV2wBP9E7d6bLrXJFzA2hWCXSUNYVCz2HWwOV/ACnmArllJJi2OwYZhzQk/PNyAn73Qp/32/y5nznxMU6FdYg4DFXnW4Q02fQiFFWNqs6DLxo85Hc+6VtFjzS4s2mafVkvL2KRU0vJC9ZpylhhrmF+kdtS8EZ+/UGfqodH090xaCNiaIzIBMb5PZ880HsTuHAIGoNsE0w=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_MN2PR00MB073663726DB5AFE6885D0A6BB6670MN2PR00MB0736namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: MN2PR00MB0736.namprd00.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 686a6004-d7ab-4cc2-d7dc-08d823861197
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 Jul 2020 21:29:59.9165 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 4rH/upfLF5jZ8+66pRA2UTX8+1YZBAdJZZE4sIwyLQ0R3BB9TJby1lJnKtXfe+ReROhPx51iWY6g6lD8zp05knpVpOipdQu2aKcuDdCb4ms=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR00MB0817
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/DYjeywiWYuWPF3iTX9_T3R3sI-s>
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, 08 Jul 2020 21:30:14 -0000

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

This is a WGLC review of draft-ietf-quic-recovery-29. Mostly editorial but =
some issues.


Section 2
" are not acknowledged, declared lost, or abandoned along with old keys." -=
->  are not acknowledged, declared lost, or discarded along with old keys."
Discarding is the term used in the rest of the doc notably in section 2.4. =
I see some reference to "abandon packets" in the transport draft as well. W=
ould be good to use the same term for consistency everywhere.

Section 4.4.
 "does not allow any acked packet to be reneged" --> "does not allow any ac=
knowledged packet to be reneged"

Section 4.7
"QUIC uses a probe timeout (see Section 6.2)," --> "QUIC uses a Probe Timeo=
ut (PTO) (see Section 6.2),"

Section 5.2 "If the path's actual RTT increases, the min_rtt will not adapt=
 to it, allowing future RTT samples that are smaller than the  new RTT be i=
ncluded in smoothed_rtt."
Would it safer to reset min_rtt after persistent congestion is declared. Th=
is is important so we can adapt to a consistent spike in RTT as a result of=
 a path change.

Section 6.1.1

"Algorithms that increase the reordering threshold after spuriously detecti=
ng losses, such as TCP-NCR [RFC4653], have proven to be useful in TCP and a=
re expected to at least as useful in QUIC."
It might be better to refer to RACK here which has an optional feature to i=
ncrease reorder threshold in time. I don't know of any major implementation=
s that do TCP-NCR but maybe I am mistaken.

Section 6.2.1
"time threshold Section 6.1.2" --> time threshold (Section 6.1.2)

"The life of a connection that is experiencing consecutive PTOs is limited =
by the endpoint's idle timeout."
Is there any specification of recommended values for idle timeout? Any valu=
es lower than 9 seconds could adversely impact preserving of connectivity d=
uring VM live migration.

Section 6.2.4
"If the sender wants to elicit a faster acknowledgement on PTO, it can skip=
 a packet number to eliminate the ack delay."
This adds some unnecessary complexity. Given that endpoint MAY send two ful=
l-sized datagrams, isn't that a better technique than skipping packet numbe=
rs?

Section 7.8
"The congestion period is calculated as the time between the oldest and new=
est lost packets: (3 - 0) =3D 3." --> "The congestion period is calculated =
as the sent time difference between the oldest and newest lost packets: (3 =
- 0) =3D 3."
It might be worth noting that persistent congestion can be declared without=
 sending a PTO. Particularly because the example assumes PTOs. In the case =
where app kept on periodically sending new data and no ACKs came back for t=
he threshold and then an ACK came back and declared all packets sent before=
 it as lost.

Section 7.9
"Implementations MUST either use pacing or another method to limit such bur=
sts to the initial congestion window; see Section 7.2."
This seems to preclude use of segmentation offload of sizes greater than IW=
. In datacenters we routinely send bursts that are higher without causing l=
oss. The MUST here seems unnecessary. It also conflicts with the RECOMMENDE=
D in an earlier sentence.

Section 8.2
"Endpoints can use PADDING frames or bundle acknowledgments with other fram=
es to reduce leaked information."
A reminder should be added here that PADDING counts towards in-flight so th=
ere is a possible impact on performance.

Section B.8
The function AreAllPacketsLost does not have any pseudocode.


Thanks

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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
p.MsoPlainText, li.MsoPlainText, div.MsoPlainText
	{mso-style-priority:99;
	mso-style-link:"Plain Text Char";
	margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.PlainTextChar
	{mso-style-name:"Plain Text Char";
	mso-style-priority:99;
	mso-style-link:"Plain Text";
	font-family:"Calibri",sans-serif;}
.MsoChpDefault
	{mso-style-type:export-only;}
@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"MsoPlainText">This is a WGLC review of draft-ietf-quic-recovery=
-29. Mostly editorial but some issues.<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">Section 2<o:p></o:p></p>
<p class=3D"MsoNormal">&quot; are not acknowledged, declared lost, or aband=
oned along with old keys.&quot; --&gt;&nbsp; are not acknowledged, declared=
 lost, or discarded along with old keys.&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">Discarding is the term used in the rest of the doc n=
otably in section 2.4. I see some reference to &quot;abandon packets&quot; =
in the transport draft as well. Would be good to use the same term for cons=
istency everywhere.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 4.4.&nbsp; <o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;&quot;does not allow any acked packet to be re=
neged&quot; --&gt; &quot;does not allow any acknowledged packet to be reneg=
ed&quot;<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 4.7<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;QUIC uses a probe timeout (see Section 6.2),&q=
uot; --&gt; &quot;QUIC uses a Probe Timeout (PTO) (see Section 6.2),&quot;
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 5.2 &quot;If the path's actual RTT increases=
, the min_rtt will not adapt to it, allowing future RTT samples that are sm=
aller than the&nbsp; new RTT be included in smoothed_rtt.&quot;
<o:p></o:p></p>
<p class=3D"MsoNormal">Would it safer to reset min_rtt after persistent con=
gestion is declared. This is important so we can adapt to a consistent spik=
e in RTT as a result of a path change.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 6.1.1<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&quot;Algorithms that increase the reordering thresh=
old after spuriously detecting losses, such as TCP-NCR [RFC4653], have prov=
en to be useful in TCP and are expected to at least as useful in QUIC.&quot=
;
<o:p></o:p></p>
<p class=3D"MsoNormal">It might be better to refer to RACK here which has a=
n optional feature to increase reorder threshold in time. I don't know of a=
ny major implementations that do TCP-NCR but maybe I am mistaken.<o:p></o:p=
></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 6.2.1<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;time threshold Section 6.1.2&quot; --&gt; time=
 threshold (Section 6.1.2)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">&#8220;The life of a connection that is experiencing=
 consecutive PTOs is limited by the endpoint's idle timeout.&#8221;<o:p></o=
:p></p>
<p class=3D"MsoNormal">Is there any specification of recommended values for=
 idle timeout? Any values lower than 9 seconds could adversely impact prese=
rving of connectivity during VM live migration.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 6.2.4<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;If the sender wants to elicit a faster acknowl=
edgement on PTO, it can skip a packet number to eliminate the ack delay.&qu=
ot;
<o:p></o:p></p>
<p class=3D"MsoNormal">This adds some unnecessary complexity. Given that en=
dpoint MAY send two full-sized datagrams, isn't that a better technique tha=
n skipping packet numbers?<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 7.8<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;The congestion period is calculated as the tim=
e between the oldest and newest lost packets: (3 - 0) =3D 3.&quot; --&gt; &=
quot;The congestion period is calculated as the sent time difference betwee=
n the oldest and newest lost packets: (3 - 0) =3D 3.&quot;<o:p></o:p></p>
<p class=3D"MsoNormal">It might be worth noting that persistent congestion =
can be declared without sending a PTO. Particularly because the example ass=
umes PTOs. In the case where app kept on periodically sending new data and =
no ACKs came back for the threshold
 and then an ACK came back and declared all packets sent before it as lost.=
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 7.9<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;Implementations MUST either use pacing or anot=
her method to limit such bursts to the initial congestion window; see Secti=
on 7.2.&quot;
<o:p></o:p></p>
<p class=3D"MsoNormal">This seems to preclude use of segmentation offload o=
f sizes greater than IW. In datacenters we routinely send bursts that are h=
igher without causing loss. The MUST here seems unnecessary. It also confli=
cts with the RECOMMENDED in an earlier
 sentence.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section 8.2<o:p></o:p></p>
<p class=3D"MsoNormal">&quot;Endpoints can use PADDING frames or bundle ack=
nowledgments with other frames to reduce leaked information.&quot;
<o:p></o:p></p>
<p class=3D"MsoNormal">A reminder should be added here that PADDING counts =
towards in-flight so there is a possible impact on performance.<o:p></o:p><=
/p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Section B.8<o:p></o:p></p>
<p class=3D"MsoNormal">The function AreAllPacketsLost does not have any pse=
udocode.<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">Thanks<o:p></o:p></p>
</div>
</body>
</html>

--_000_MN2PR00MB073663726DB5AFE6885D0A6BB6670MN2PR00MB0736namp_--


From nobody Wed Jul  8 23:28:09 2020
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 EB5633A0FC4 for <quic@ietfa.amsl.com>; Wed,  8 Jul 2020 23:28:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H4=0.001, RCVD_IN_MSPIKE_WL=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=lowentropy.net header.b=jLvtHWqf; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=qCOHIn/X
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Eq68JUAWoiw3 for <quic@ietfa.amsl.com>; Wed,  8 Jul 2020 23:28:05 -0700 (PDT)
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id A61FA3A0FC5 for <quic@ietf.org>; Wed,  8 Jul 2020 23:28:05 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id EA2855C02F2 for <quic@ietf.org>; Thu,  9 Jul 2020 02:28:04 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Thu, 09 Jul 2020 02:28:04 -0400
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=fm2; bh=u0lXY IwVtNYHd2TvnATQAZVIRsW/FOgiqK2yh5Ylyg8=; b=jLvtHWqfgGcBcacOCbUAX ttXbrtQARKWXyz3LdS0ApXX6cG4jljUtcHm4fepBs1McpHJjLG+c9SMj9DbB4ufX K200/9oFHeAcFfEGZqM4y4D7wx04HV86+aOq3LtT1LnRNM36/7QoKQwDnAcSymAB Zh8hB8KTHLPCO/92gWfGXFW6ZvBzh8diKwoT+ojLQJUj9RUtGuk+Z2kTw6VKq7e2 2/3NTJKkP+h3/Kfra+bNhXLPyCWWRADA4B82VP0Hu7mJKauEaCJlrFQTVxfSGP0p 7x2YhXXg2wzCoq768QD5rcGxXe0iu6ctF8jZ7OqOaJR7ZyNlkElzxmauxHLEJXjg A==
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=fm3; bh=u0lXYIwVtNYHd2TvnATQAZVIRsW/FOgiqK2yh5Yly g8=; b=qCOHIn/XI5CXLDkIpfQ54PWdF0NdQQFqh/AR3HFxg/idqr1t19ZzTvFvr N4t8gOGrmZ1B8CCYBfrG8/U0AMnxhuGXLg69Z3VWCJttVksPiQ6HvQdAv2cjXX65 OOaG1W1zYwnE3bwkfDF2FOECu46V6UA729RxG7pBAFMAtEumtyV/rrH6TYf0hzfG jGmiBQAhuyWk2VEDNJzQilCifCMhwsepDBdZv3qC7V+wlUyEjRnz8h4QYxaGju5L 8hclX76kdPmOAAWhM9r5OAu/SQR5yCh5TImT4Jrwjr6dgZ13qp6MqAuxfHQ9z80Q aVFLMjtb/Aecg23rJsRFgioUVVmAw==
X-ME-Sender: <xms:9LgGX8NGwb02hDXhUKuT7BBBDPqf9QV9tYg03eSikYlXBaX4svQjXA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrudekgdduudduucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfgjfhffhffvufgtgfesth hqredtreerjeenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehl ohifvghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepheehvdfhheevgfegje dtgeejudevteeljedvkeejjefhkeeikeduleffvddufeffnecuffhomhgrihhnpehgihht hhhusgdrtghomhdpihgvthhfrdhorhhgnecuvehluhhsthgvrhfuihiivgeptdenucfrrg hrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:9LgGXy9vmA7os3yK8GoeJpCAUWweT6wm3oJYETgoJ7E3WF5IzepthA> <xmx:9LgGXzTpf2MBAT_8eDV83yEINndVxVY-Y8cHotg5JM4HV3yKrovvog> <xmx:9LgGX0tvzqFcTJfoy61EJm78k975_ALVZnRaudZhLTTu0AwfWPevTg> <xmx:9LgGX7_jEmPRRO2LZge1e_C0AOSZNxyjhFdK5rUVarIWZmVG-NMLFw>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 61599E00B3; Thu,  9 Jul 2020 02:28:04 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-613-g8a73ad6-fm-20200709.001-g8a73ad6e
Mime-Version: 1.0
Message-Id: <b6a4e0ee-bc04-4722-a73c-b0253b1de2c4@www.fastmail.com>
In-Reply-To: <HE1PR0702MB37720D42E58ACB56A14E679495670@HE1PR0702MB3772.eurprd07.prod.outlook.com>
References: <HE1PR0702MB37720D42E58ACB56A14E679495670@HE1PR0702MB3772.eurprd07.prod.outlook.com>
Date: Thu, 09 Jul 2020 16:27:42 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: quic@ietf.org
Subject: Re: WG last call comments on draft-ietf-quic-transport-29
Content-Type: text/plain;charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/-T1q6B84NaWzaHhxehNU3kFPhRQ>
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, 09 Jul 2020 06:28:08 -0000

Hi Magnus,

Thanks for taking the time to review.  These are all good.  I've opened =
a PR that addresses most of these, but some might require some discussio=
n.

https://github.com/quicwg/base-drafts/pull/3881

On Thu, Jul 9, 2020, at 04:04, Magnus Westerlund wrote:
...
> 1. Section 1.3:=20
>=20
> x (A..B): Indicates that x can be any length from A to B; A can be
>  omitted to indicate a minimum of zero bits and B can be omitted to
>  indicate no set upper limit; values in this format always end on
>  an octet boundary
>=20
> There is an upper limit based on the protocol even in these cases,=20
> either due to encoding restrictions or the protocol. 2^62-1 bytes in=20=

> most cases for length or data limits or the per packet limit where MPS=
=20
> will be a restriction. Should that be made more explicit.=20

This is a length of a field in bits, which means that "no set upper limi=
t" is fine in my view.  There is often an upper limit, but it depends on=
 how much space is left in the packet.  Note that the 2^62 cap doesn't h=
ave to apply to lengths in bits.

> 2. Section 3.2, Figure 3:=20
> The top most RESET_STREAM which leads to the Recv state. Shouldn't tha=
t=20
> go to the RESET Recvd state immediately. If I interpret the figure it=20=

> will take two RESET_STREAMS until one end up in RESET RECVD

There are a few places in the diagrams where a single event causes multi=
ple transitions.  For instance, receiving STREAM with FIN can cause a tr=
ansition from the starting state, through Recv and Size Known, to Data R=
ecvd.  I thought that we had noted that this can happen, but I see that =
this didn't happen.

> 3. Section 4.1: "
>=20
> If a sender is blocked
>  for a period longer than the idle timeout (Section 10.2), the
>  connection might be closed even when data is available for
>  transmission."
>=20
> Who may close the conenction? both peers, or the sender that is blocke=
d=20
> or the receiver?

The receiver.  Addressed in the PR.

> 4. Section 7.4.1: "
>=20
>  In particular, a server that accepts 0-RTT data
>  MUST NOT set values for the following parameters (Section 18.2) that
>  are smaller than the remembered value of the parameters."
>=20
>=20
> So far I have not seen any definition for how long TP parameters will=20=

> be remembered. I guess that there is a time limit on the 0-RTT keying=20=

> material stored in the client that is relevant her, however this is no=
t=20
> at all referenced here. Should there be a pointer or explanation?=20
> Because the above normative statement appears to be missing the tie=20=

> into how long the client will remember theses remembered values.

The rule is that when you remember a ticket, you need to remember a bunc=
h of stuff with that in order for 0-RTT to work.  You don't get to remem=
ber part of that and expect to have 0-RTT work.  I've added a little mor=
e context.

I've also opened https://github.com/quicwg/base-drafts/pull/3879 to impr=
ove on the context in the -tls draft.

> 5. Section 8.1.3 and 8.1.4:
>=20
> First of all I got the wrong impression of this section as the details=
=20
> about address validation part, that you actually include the address i=
s=20
> in the next section 8.1.4. I don't know if there should be something=20=

> done about this or not. But my impression after 8.1.3 and before I rea=
d=20
> 8.1.4 that this was not address validation, only client validation,=20=

> i.e. this is a client I talked to before.=20
>=20
> My actual question I have on these section is if it there should be=20=

> clarification on that the client should keep track of the token on a=20=

> server authority + client address/network scope. So that the client=20=

> will not send the token unless it is on the same network it was before=
.=20
>
> But maybe this last is unnecessary as the server will ignore the token=
=20
> if it doesn't match.=20

Right.  The cost to the client is:

1. The server can correlate the attempt with a previous connection.
2. The client uses up the token.

I think that the text in 8.1.3 is adequate on this point.

> 6. Section 9.2:
>=20
>  Receiving acknowledgments for data sent on the new path serves as
>  proof of the peer's reachability from the new address.

> So this might be an intended differenation between path validation and=
=20
> indication of basic reachability (assuming no hostility). Maybe that=20=

> exception also needs to be noted in the last paragraph in Section 9.2.=


Oh, good catch.  The point about acknowledgments is just wrong.  This is=
 just old text that should have been fixed.

> 7. Section 9.3.1:=20
>=20
>  If an endpoint skips validation of a peer address as described in
>  Section 9.3, it does not need to limit its sending rate.
> ...
> So the question here is what is considered recently. I think the=20
> lifetime of a address validation is significantly longer than the=20
> validity of the congestion control state.=20

This is a tough question, and entirely subjective.  No number is good he=
re.  I've heard that some implementations limit this to a day, other to =
an hour.  I suspect that we just have to live with this.

I've opened an issue: https://github.com/quicwg/base-drafts/issues/3880

> 8. Section 10.1:=20
> "Endpoints that have some alternative
>  means to ensure that late-arriving packets on the connection do not
>  induce a response, such as those that are able to close the UDP
>  socket, MAY use an abbreviated draining period which can allow for
>  faster resource recovery."
>=20
> So to me this assumes that the underlying system will not reuse the=20=

> local UDP port in the time it takes to drain the network. I assume eve=
n=20
> applications may shoot itself in the foot if it insist on a local=20
> source port for an outgoing QUIC connections and that was recently=20
> used. I assume that this will not have any significant impact on a QUI=
C=20
> instance, and what it does to another UDP protocol is all dependent.

Yes.  I think that this generally only applies to use of ephemeral ports=
 on client systems, where the reuse period is relatively long.=20

More importantly, the consequence is that the new user of the port has t=
o filter out some residual garbage.  As everything in QUIC is authentica=
ted, this is not a serious problem in the same way that it might be for =
another protocol.

> 10. Section 10.2: "
...
> Should this really be the minimum and not the maximum. For very low=20=

> values of MAX_IDLE_TIMEOUT the QUIC stack is not even given a fair=20
> chance of probing if the path is still there or not? And for larger=20=

> value the 3*PTO will always be setting the value. I would have expecte=
d=20
> the maximum, that below 3*PTO it will not timeout, and when=20
> MAX_IDLE_TIMEOUT > 3*PTO that value will be limit for how long probing=
=20
> is done.=20
This was found and a fix prepared already: https://github.com/quicwg/bas=
e-drafts/pull/3847

> Doesn't the rule also prevent a stack being silent for longer than=20
> 3*PTOs? That appears wasteful to force continuos communication if ther=
e=20
> are no data be sent.=20

The 3PTO was a backstop for cases where the idle timeout was set too low=
 relative to the RTT.  Our advice on keeping connections alive is not to=
 do that unless you have committed state that you don't want to lose.  F=
or instance, an HTTP client might send keep-alives only while it is wait=
ing for a response to a request.

> 11. Section 10.3:
>=20
> Such an
>  endpoint SHOULD limit the number of packets it generates containing a=

>  CONNECTION_CLOSE frame.
>=20
>=20
> To what level should it be limited, e.g. one packet per 1/4 RTT? Or is=
=20
> the argument that=20
> Any reduction is sufficient. To me it looks like a simple packet mirro=
r=20
> on path that sends the packets back to the sender will maintain the=20=

> number of packets in flight unless there is a reduction factor.

This was raised in https://github.com/quicwg/base-drafts/issues/3845

I agree that this is vague.  I have proposed a solution here based on ou=
r anti-amplification limit: https://github.com/quicwg/base-drafts/pull/3=
864

Note also that this is limited to the duration of the closing period, so=
 this is not a permanent state.  A small amount of amplification is like=
ly tolerable on that time frame.

> 12. Section 12.4:
...
>  Packet Payload {
>  Frame (1..) 1...,
>  }

Yes.  Frame (8..) ..., But I don't think that we can capture the require=
ment to include at least one frame.  That's OK, it's just for illustrati=
on purposes :)

> 13. Section 17.2.2:
>=20
> Length field for the Packet header is undefined. I would guess that it=
=20
> contains the total length of the Initial Packet in bytes but that=20
> should be defined. Applies also to the 0-RTT and Handshake packet.

They are mentioned and defined earlier, but their mentions don't referen=
ce the definition.  Fixed.

> 14. Section 17.2.5:
>=20
> The value in the Unused field is selected randomly by the
>  server.
>=20
> Should this say that the receiver should ignore the value in the field=
?

Fixed.  Thanks.

> 15. Section 19.9:
>=20
> The Maximum Data (i) field as currently defined will be in many=20
> connections the upper limit for how many packets can be sent in any=20=

> connection due to its bit limit. As this is a maximum value due to=20
> usage of the variable encoding to 2^62-1 bytes. It is possible that=20=

> this value could be reached as around 2^52 packets approximately. An=20=

> QUIC packet will be possible to contain at least 1024 bytes, i.e. 10=20=

> bits worth of bytes. In a DC center network with larger MTUs it is=20
> possible that already after 2^50 packets this value will be exhausted.=

>=20
> Should I simply assume that this amount of data is such a big number=20=

> that if an application runs into the limit forcing it to restart the=20=

> connection is a minor issue. However considering that the limit in=20
> packets are relatively more discussed, this limit is not much discusse=
d=20
> and in fact there are no mention in 19.9 what to do if that value=20
> reaches maximum that can be encoded, i.e. close the connection.=20

Yes, that is the current thinking.  Note that there were proposals to sc=
ale the values in MAX_DATA to allow for more data to be sent.  However, =
this proposal wasn't that favourably viewed as it increased complexity q=
uite a bit, and 2^62 is really a very big number and having to create an=
other connection at that rate isn't that much of an imposition.

(Also, I've learned that you don't get to make many such connections bef=
ore you wear out the AEAD functions we have here.)

>  16. Section 22.1.4:=20
>=20
>=20
> =C2=A0=C2=A0 All registrations in this document are assigned a permane=
nt status
>  and list as contact both the IESG (ietf@ietf.org) and the QUIC
>=20
>  working group (quic@ietf.org (mailto:quic@ietf.org)).
>=20
>=20
> The IESG is recommending that registration owner for IETF STD document=
s=20
> are IETF. The arguments are in this doc:=20
>=20
> https://datatracker.ietf.org/doc/draft-leiba-ietf-iana-registrations/

Corrected.  Thanks.

>  1. Section 22:
>=20
> An important question that for the high level structure of the=20
> registries are the question if these registries are Version 1 specific=
,=20
> or expected to be used across multiple versions of QUIC? Because if th=
e=20
> former then the general heading for the registries should say QUIC=20
> Version 1. If they are intended to be for multiple versions, what type=
=20
> of indication for which version particular entries are valid are=20
> needed?=20

I think that leaving that problem to future iterations of this group is =
best.  I know that future me will have ample cause to resent the decisio=
ns of present me anyway.

If QUICv2 wants to reuse these, then no change is necessary.  However, i=
f they/we want to make new registries, then renaming these registries re=
quires little effort.


From nobody Thu Jul  9 01:39:34 2020
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 BCFD93A0928 for <quic@ietfa.amsl.com>; Thu,  9 Jul 2020 01:39:33 -0700 (PDT)
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_BLOCKED=0.001, SPF_HELO_NONE=0.001, SPF_NONE=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 0k9r50Iz_rnZ for <quic@ietfa.amsl.com>; Thu,  9 Jul 2020 01:39:32 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id DEACC3A0912 for <quic@ietf.org>; Thu,  9 Jul 2020 01:39:31 -0700 (PDT)
Received: from GF-MacBook-Pro.lan (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 5F4611B0007F; Thu,  9 Jul 2020 09:39:28 +0100 (BST)
Subject: Re: WGLC review of draft-ietf-quic-recovery-29
To: Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>, IETF QUIC WG <quic@ietf.org>
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <53187d65-f7b9-b99a-f68b-b267303ab399@erg.abdn.ac.uk>
Date: Thu, 9 Jul 2020 09:39:27 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------8F2993EF6B57BD3E039F3D27"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/SnZdrDu4gMyxCnBVUDTMnnc1lVg>
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, 09 Jul 2020 08:39:34 -0000

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

Hi Praveen,

On 08/07/2020 22:29, Praveen Balasubramanian wrote:
>
> Section 7.9
>
> "Implementations MUST either use pacing or another method to limit 
> such bursts to the initial congestion window; see Section 7.2."
>
> This seems to preclude use of segmentation offload of sizes greater 
> than IW. In datacenters we routinely send bursts that are higher 
> without causing loss.
>
Is that within data centres? or from data centres to Internet 
destinations? ... if the latter, how can the sender be sure this is not 
impacting other traffic?
>
> The MUST here seems unnecessary. It also conflicts with the 
> RECOMMENDED in an earlier sentence.
>
I actually don't see this as conflicting. The recommendation in this 
section is to pace. The requirement is that sender limits burst, using 
some method, to the size of IW.

Gorry



--------------8F2993EF6B57BD3E039F3D27
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 7bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body>
    <p>Hi Praveen,<br>
    </p>
    <div class="moz-cite-prefix">On 08/07/2020 22:29, Praveen
      Balasubramanian wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com">
      <p class="MsoNormal">Section 7.9<o:p></o:p></p>
      <p class="MsoNormal">"Implementations MUST either use pacing or
        another method to limit such bursts to the initial congestion
        window; see Section 7.2."
        <o:p></o:p></p>
      <p class="MsoNormal">This seems to preclude use of segmentation
        offload of sizes greater than IW. In datacenters we routinely
        send bursts that are higher without causing loss. </p>
    </blockquote>
    Is that within data centres? or from data centres to Internet
    destinations? ... if the latter, how can the sender be sure this is
    not impacting other traffic?<br>
    <blockquote type="cite"
cite="mid:MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com">
      <p class="MsoNormal">The MUST here seems unnecessary. It also
        conflicts with the RECOMMENDED in an earlier sentence.</p>
    </blockquote>
    <p>I actually don't see this as conflicting. The recommendation in
      this section is to pace. The requirement is that sender limits
      burst, using some method, to the size of IW.</p>
    <p>Gorry<br>
    </p>
    <p><br>
    </p>
  </body>
</html>

--------------8F2993EF6B57BD3E039F3D27--


From nobody Thu Jul  9 05:49:07 2020
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 2582E3A09D3 for <quic@ietfa.amsl.com>; Thu,  9 Jul 2020 05:49:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level: 
X-Spam-Status: No, score=-2.102 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, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-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=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 MkNJNcUtehta for <quic@ietfa.amsl.com>; Thu,  9 Jul 2020 05:49:03 -0700 (PDT)
Received: from EUR05-DB8-obe.outbound.protection.outlook.com (mail-db8eur05on2086.outbound.protection.outlook.com [40.107.20.86]) (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 9D9303A09D1 for <quic@ietf.org>; Thu,  9 Jul 2020 05:49:03 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=AhFTW0Y9jz6B60bPAKoXlMtJ81Jd4Kiz++LLGBWJ/qow8cukGzaHVlQu34fgnYR/tHTrHyziS9JcrylG00b3xBanGtudLTdlWhaV41dHl7nr8mpPQP/td8nvJThJeFOUcVcF1U+z1xXXYyGIvVVZPhioxDyfjUv64VkqvS8CnsD9Zh8KToXuK+bOQa+Hm7tKAdXms/zE+nzSNZR+VoFAUW4zCpH0y1pWhPrileGK9XM1iR/vWKnrN19ZvyRtt4BS2jUiW2YrcBKG/uHIDVNHhHEPRlHp8ge3YnrK9cex/1aoOnhh9/HEKgN3nG29epB2crIOTeavqDbT3ULt4taAMA==
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=rHnzIdmExbO86YGvqvkK3WlDq3gY0+uFBxMeK8dPCN0=; b=As1q5XVlnhEfsUCHAtQFjMtMB4CKjCbUlQrNVJNLL3ZAYf0UNF3FMXO1PkksRfdzGT5ezft6nGUubTAshL04PQVJrpra8n8lFb5GJNsMuW6V8CB8i0AGuMii9zzEBnSfgeIi40ndf9IaqVGLwZ7TvWqkyiwOGYDgbF6gso4QRPsEyEuvm8K12CJzRw3gC6SZ5QwD/HJN81fb3cnof/vkkUntmgbGXG979d4IReAoyNX5F53as3obAavSpnhkMIOW1axbQyBwFV/C2Guu2FUWOK+kIh5+fIYW7otOhr7jljEB0EfA1qs2a0knf0Zrg1Rk6s/aVtjzXbQbH8oN9A6Ocg==
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=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rHnzIdmExbO86YGvqvkK3WlDq3gY0+uFBxMeK8dPCN0=; b=IhriIEu0iU7kKnjoTd96UKN+uotlwfhkY2AM7j2asNPanV0H+Y+yfGsJ9FRgoFDacZe5qA+ZdSm8Z9Gke42QSoIuT3nBWq5CRTSTqqSB3NzT/DAb2llx/xYhFYawspoRWg7t9jpZrIQ59mHK/vudatIJd5o1wlSSrGEz0Za+Kks=
Received: from AM0PR0702MB3713.eurprd07.prod.outlook.com (2603:10a6:208:19::10) by AM0PR07MB5700.eurprd07.prod.outlook.com (2603:10a6:208:118::22) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3174.13; Thu, 9 Jul 2020 12:49:01 +0000
Received: from AM0PR0702MB3713.eurprd07.prod.outlook.com ([fe80::d1f1:397c:7240:92f1]) by AM0PR0702MB3713.eurprd07.prod.outlook.com ([fe80::d1f1:397c:7240:92f1%7]) with mapi id 15.20.3174.022; Thu, 9 Jul 2020 12:49:01 +0000
From: Mirja Kuehlewind <mirja.kuehlewind@ericsson.com>
To: "quic@ietf.org" <quic@ietf.org>
CC: "Brian Trammell (IETF)" <ietf@trammell.ch>
Subject: New versions of manageability and applicability drafts
Thread-Topic: New versions of manageability and applicability drafts
Thread-Index: AQHWVe9RkyUEgngBhkyX4bG4JT/Nvw==
Date: Thu, 9 Jul 2020 12:49:01 +0000
Message-ID: <954E8C8F-E4ED-4ED7-AE82-13C36D32B442@ericsson.com>
Accept-Language: en-US
Content-Language: en-GB
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
user-agent: Microsoft-MacOutlook/16.37.20051002
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [2003:de:e700:7a00:3d8b:8bff:d80b:599d]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 69f6193d-3be8-4fb4-4a45-08d824067455
x-ms-traffictypediagnostic: AM0PR07MB5700:
x-microsoft-antispam-prvs: <AM0PR07MB57007C753678ADE37936190BF4640@AM0PR07MB5700.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 3yUiOszP7myqA0n4mwkSHS2KbAGN4nLX5ZDqBOPTlr8lwIyFxS/gedXg57+vZ2srtu0DESp75gu1NRlnTj6/e0iKcYM2lKIpa3Wj5OBETTH5SgxhA+U5ioRL0nlbI6XA5a5CjH4eRctGMwlcCqliJHKZa2DGMfFrx4oy04udbhOXS7Tn5Y01yJWzk0XjhYGQVTfquvSMEqBUFB1SIbSFV0g74vWPcKmqqE068cxVRPUHow6X3uMRBdN62rBnJ9thtHq5XWaMO1wdGQfOzvxk+Ifi8edO5R6k/NZunFU53CnQHgP+Bpttb/5BDKBLspW1+N5wcrmwF4mCGGMR21y5+00Fpfi3YaKb4XFhiwl+KeEcUtQjazQIItqTiCZFpaflTbtb7vNNbMaA40v3pvGE7g==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:AM0PR0702MB3713.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(39860400002)(376002)(346002)(136003)(396003)(366004)(36756003)(6916009)(8676002)(44832011)(6486002)(316002)(478600001)(966005)(2616005)(86362001)(2906002)(6506007)(71200400001)(64756008)(83380400001)(5660300002)(186003)(66556008)(33656002)(91956017)(66446008)(4326008)(66946007)(76116006)(66476007)(6512007)(8936002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: Jo5AP48GmvOp1keQMVz97QUXI1r/DXQNyxeLzpwR4dyEZ5lc2Fi/O32mqetjINx/eezC5VMQI9VNdP1N+gaaeWivjzb4z8rD+H2Rbw6MQqvQAMspNcZTPIeY1biYbmTBjZARRHloEWtOl3ZvjnSsJEGwyOZozFYZ6XjYeZMdOKOFQdhc4fkleo85/an5KWoulJLY3XsbTA3jROEcxGNLzGhHgN+B1kilLL6JxhGOZ3zAHLg54vaW9aAyUlh5tCwkfQGxZyS7INRxPbqoVen+iGCJHFL9QmU+0LnWQHa+nCGy3UqFwhS/G7TPE81mKU+wcFoTN/2di6VkFTUipSxQPn/qwR2E7VZhEtQheuXQM1HALa9Mh6s2V6BioHP4xTVJ29VKJgU6rC0iWl0DY3EJYyJDWmt/ar4CHZ5lqtNjE+DHsythsbm8DYZsEqHwhe+hPW0YjfLWUk1s87kePhlDzMJgBD9eEBFo4GJm17ZqmAH39PPMg2Vk0+tTvcYDLMSTacCWl0UEzTlvTAqGlo5F5Oy2QoARL2P34UK8djQSwjI=
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <5140664B93B681429BA3FFC8D8080FFB@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: AM0PR0702MB3713.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 69f6193d-3be8-4fb4-4a45-08d824067455
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jul 2020 12:49:01.2725 (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: 5Z0w/LH7BSKVQ8KQVNCRQQXZY5n0ircoxne4MWGL6s73e8GLOlrx7VeCzdA3qHTHmkKDCfSUrqbjxYkYpd7iHB8oCatxlHghNG1tRhyWs0I=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM0PR07MB5700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/zubNr6u9-OEmtLzt1ejOXF5siiw>
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, 09 Jul 2020 12:49:05 -0000

SGkgYWxsLA0KDQphcyB5b3UgbWF5IGhhdmUgc2VlbiB3ZSB1cGRhdGVkIHRoZSBtYW5hZ2VhYmls
aXR5IGFuZCBhcHBsaWNhYmlsaXR5IGRyYWZ0cy4gV2UgbWFpbmx5IHdlbnQgdGhyb3VnaCB0aGUg
b3BlbiBpc3N1ZXMgbGlzdCBvbiBnaXRodWIgYW5kIHdlcmUgYWJsZSB0byBjbG9zZSBzb21lL21v
c3Qgb2YgdGhlbS4gDQoNCkZvciBtYW5hZ2VhYmlsaXR5IHdlIGRpZCBzb21lIGFsaWdubWVudHMg
d2l0aCB0aGUgdHJhbnNwb3J0IGFuZCBpbnZhcmlhbnRzIGRyYWZ0cywgYXMgd2VsbCBhcyBzb21l
IG5ldy9tb3JlIHRleHQgb24gVURQIHBvbGljaW5nLiBGb3IgYXBwbGljYWJpbGl0eSB0aGUgbWFp
biBuZXcgYWRkaXRpb24gaXMgc29tZSBkaXNjdXNzaW9ucyBhbmQgcG9pbnRlcnMgdG8gdGhlIGh0
dHAgZG9jIGFib3V0IEFMUE4gdXNhZ2UuIFJldmlld3MgYXJlIHdlbGNvbWUhDQoNClRoZXJlIGFy
ZSBhbHNvIGEgZmV3IG9wZW4gaXNzdWVzIGxlZnQgb24gZ2l0aHViLiBBYm91dCBoYWxmIG9mIHRo
ZW0gd2UgbGVmdCBvcGVuIGFzIGEgcmVtaW5kZXIgZm9yIGZpbmFsIGNoZWNrIHdoZW4gdGhlIGRv
Y3VtZW50IGlzIHJlYWR5LiBGb3IgdGhlIG90aGVycywgMyBoYXZlIFBScyB3aGljaCB3ZSBkaWQg
bm90IG1lcmdlIGludG8gdGhpcyB2ZXJzaW9uIGFzIHdlIHdvdWxkIGxpa2UgdG8gZ2V0IGZ1cnRo
ZXIgZmVlZGJhY2sgZmlyc3QuIFBsZWFzZSBoYXZlIGEgbG9vayBhbmQgcHJvdmlkZSBmZWVkYmFj
azoNCg0KIzEwNSBtZW50aW9uIHBvc3NpYmlsaXR5IHRvIGVtYmVkIGxlbmd0aCBpbiBDSUQgYW5k
IHBvaW50IHRvIHF1aWMtbG9hZC1iYWzigKYgDQpodHRwczovL2dpdGh1Yi5jb20vcXVpY3dnL29w
cy1kcmFmdHMvcHVsbC8xMDUNCg0KIzEwNCByZXRyeSBzZXJ2aWNlIGFuZCB2YWxpZGF0aW9uIHRv
a2VuDQpodHRwczovL2dpdGh1Yi5jb20vcXVpY3dnL29wcy1kcmFmdHMvcHVsbC8xMDQNCg0KIzEw
MiBNb3JlIGd1aWRhbmNlIG9uIGlkbGUgdGltZW91dHMNCmh0dHBzOi8vZ2l0aHViLmNvbS9xdWlj
d2cvb3BzLWRyYWZ0cy9wdWxsLzEwMg0KDQpUaGFua3MhDQpCcmlhbiBhbmQgTWlyamENCg0KDQo=


From nobody Thu Jul  9 07:31:26 2020
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 70E2E3A0C00 for <quic@ietfa.amsl.com>; Thu,  9 Jul 2020 07:31:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 SVXapnz1PJpT for <quic@ietfa.amsl.com>; Thu,  9 Jul 2020 07:31:21 -0700 (PDT)
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 E9CDB3A0BFE for <quic@ietf.org>; Thu,  9 Jul 2020 07:31:20 -0700 (PDT)
Received: by mail-wm1-x334.google.com with SMTP id q15so2061640wmj.2 for <quic@ietf.org>; Thu, 09 Jul 2020 07:31: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; bh=mFvuHdobgJry3yiERUYXCMoaOSYhluk/Nhk5qf6gPNc=; b=aI7QQyue+GvKQtY/6DBVJtNyxz3TrSGlHyqnQ32/U+/UxCGGtUFeClXzLPOyl+95UK gImyDNdiSqKj3R7hTo8pIKnj30PSpurOIXA1EWtNDeHkNx7WEcapNtUiANfVi3ZHEZej OJ1y27n7fUu4KgfuHr5FjwwFp5wEF/axt6u6mrUL6OSt0BWH9EqzKoHFPIOJSIVRM3Tc y9Umrn5WV1VQMPg9T0ubdPV1NRpH5N10NAoH9euZHnK+FeGdbBYf/WoVr9E57loeN2ZI XB8LNfYPWoHFQAwZQUCtmqCniy79M0qx3usxjFwb8F0sEtmd72c9qpQitzbWGrj8f2j3 x9Pg==
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=mFvuHdobgJry3yiERUYXCMoaOSYhluk/Nhk5qf6gPNc=; b=X0LNiFJ4ZOGNdh7cdbo5kYBHtuhlhGca1U+Pf9WRht7TEaEriW6zIIwZDvKTo3n6Ax UykaWiI8gl08MIVjmYjwp7RY5mVcrMYFVjMXi6LhLEWeGs+C/gKt2X3Z6WabTg/eae0l auvGKthVrQ2ySg6TjnEZr+AZiY5Mi/eX+7xt4wpNKwLcp+Bb6s8Oy+mKc3eLTOkROXYK yHOfagdU223KnJyTCeZciddxNpny8E6IV+k7YTCOFXlFwhYwrLEy7n2ZAsApVESi3oFT LzK0EEjqStViZMK4AgDXs2/EtAR29FJKYgtnDz3e7IdOITKF0mv/ozVnAKmG2x+0ZZa0 NQqg==
X-Gm-Message-State: AOAM531M3wG0Wdhsj66R7vjDROitRjpUGG+RVD0Vnily1mfMZVZpkHBn ep9cNbIbEblpaoQrK9pbd1JfLo1rKVHsMiCHdUvT/pdt490=
X-Google-Smtp-Source: ABdhPJw0Dsdg49p3fSMONhWMTkXdAa5iEEMfenTWktbtmwETahEpgPIUFwW0ZFvNNpcFNg1SQWQwA49ZiNSHQgIoQSs=
X-Received: by 2002:a1c:2982:: with SMTP id p124mr378831wmp.26.1594305078971;  Thu, 09 Jul 2020 07:31:18 -0700 (PDT)
MIME-Version: 1.0
References: <CALGR9oZ9u=huobnQig0mMPS=-Fu7Mu3q8GHLTBOxd2W5u0h_kw@mail.gmail.com> <CALGR9oa0h3qcFmwqJwfaPQ460ZVpa+URsJmcDKkQuaHwib4Fqg@mail.gmail.com>
In-Reply-To: <CALGR9oa0h3qcFmwqJwfaPQ460ZVpa+URsJmcDKkQuaHwib4Fqg@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Thu, 9 Jul 2020 15:31:07 +0100
Message-ID: <CALGR9oakKv_uwKSQ1EzbKUQF4bdoafyfOLjO9RuxSHwsphHJ=A@mail.gmail.com>
Subject: Re: Working Group Last Call: QUIC protocol drafts
To: QUIC WG <quic@ietf.org>
Cc: Lars Eggert <lars@eggert.org>, Mark Nottingham <mnot@mnot.net>
Content-Type: multipart/alternative; boundary="000000000000e5518605aa0313e1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/awvV8tdPD52XpZvMS-Nm0cGl8B0>
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, 09 Jul 2020 14:31:24 -0000

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

Hello folks,

The WGLC has now concluded.

Hearing no pushback on issue #3661, consensus is declared.

Issues raised during WGLC will be handled in accordance with the Late-Stage
Process [1], starting with triage.

Cheers,
Lars, Lucas and Mark
QUIC WG charis

[1] - see
https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md#late-stag=
e-process
.

On Wed, Jul 1, 2020 at 12:26 PM Lucas Pardue <lucaspardue.24.7@gmail.com>
wrote:

> Reminder: the QUIC WGLC ends on July 8 2020
>
> If you have review comments please raise them in accordance with the
> instructions in the original announcement (attached).
>
> Cheers,
> Lucas, on behalf of the QUIC WG chairs
>
> On Wed, Jun 10, 2020 at 2:36 AM Lucas Pardue <lucaspardue.24.7@gmail.com>
> wrote:
>
>> Hello,
>>
>> After more than three and a half years and substantial discussion, all
>> 845 of the design issues raised against the QUIC protocol drafts have
>> gained consensus or have a proposed resolution. In that time the protoco=
l
>> has been considerably transformed; it has become more secure, much more
>> widely implemented, and has been shown to be interoperable. Both the Cha=
irs
>> and the Editors feel that it is ready to proceed in standardisation.
>>
>> Therefore, this email announces a Working Group Last Call (WGLC) for the
>> following QUIC documents:
>>
>> * QUIC Transport
>>   https://tools.ietf.org/html/draft-ietf-quic-transport-29
>>
>> * QUIC Loss Detection and Congestion Control
>>   https://tools.ietf.org/html/draft-ietf-quic-recovery-29
>>
>> * Using TLS to Secure QUIC
>>   https://tools.ietf.org/html/draft-ietf-quic-tls-29
>>
>> * Version-Independent Properties of QUIC
>>   https://tools.ietf.org/html/draft-ietf-quic-invariants-09
>>
>> * HTTP/3
>>   https://tools.ietf.org/html/draft-ietf-quic-http-29
>>
>> * QPACK Header Compression for HTTP/3
>>   https://tools.ietf.org/html/draft-ietf-quic-qpack-16
>>
>> The WGLC will run for four weeks, ending on 8 July 2020.
>>
>> As a reminder, we have been operating under the Late-Stage Process; see
>> https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md#late-s=
tage-process.
>> In theory, this means that the contents of the drafts above already have
>> consensus. However, the Chairs would like to actively reaffirm that
>> consensus and start the process of wider review through a formal WGLC.
>>
>> Please review the documents above and open issues for your review
>> comments in our repository at https://github.com/quicwg/base-drafts. You
>> may also send comments to quic@ietf.org.
>>
>> Issues raised during WGLC will be handled in accordance with the
>> Late-Stage Process defined in the Contribution Guidelines (see link abov=
e).
>> Please note that design issues that revisit a topic where there's alread=
y
>> declared consensus (see
>> https://github.com/quicwg/base-drafts/issues?q=3Dis%3Aclosed+label%3Ahas=
-consensus)
>> need to provide compelling reasons to warrant reopening the discussion.
>>
>> As part of this WGLC, we seek consensus on the remaining open design
>> issue #3661 =E2=80=9CInclude epoch in the AAD or the nonce?=E2=80=9D (
>> https://github.com/quicwg/base-drafts/issues/3661). The proposed
>> resolution for this issue is to close with no action, which means that t=
he
>> drafts above already reflect this emerging consensus.
>>
>> Subject to the feedback received during this WGLC, a subsequent smaller
>> WGLC may be run in the near future to confirm any changes to the drafts
>> made between now and then.
>>
>> The Applicability and Manageability drafts have some dependencies on the
>> core drafts, so we'll run separate WGLCs for them.
>>
>> Cheers,
>>
>> Lars, Lucas and Mark
>> QUIC WG Chairs
>>
>

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

<div dir=3D"ltr"><div>Hello folks,</div><div><br></div><div>The WGLC has no=
w concluded. <br></div><div><br></div><div>Hearing no pushback on issue #36=
61, consensus is declared.</div><div><br></div><div>Issues raised during WG=
LC will be handled in accordance with the Late-Stage Process [1], starting =
with triage.</div><div><br></div><div>Cheers,<br>Lars, Lucas and Mark<br>QU=
IC WG charis<br><br>[1] - see <a href=3D"https://github.com/quicwg/base-dra=
fts/blob/master/CONTRIBUTING.md#late-stage-process" target=3D"_blank">https=
://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md#late-stage-pro=
cess</a><span></span><span></span>.</div></div><br><div class=3D"gmail_quot=
e"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jul 1, 2020 at 12:26 PM Lu=
cas Pardue &lt;<a href=3D"mailto:lucaspardue.24.7@gmail.com">lucaspardue.24=
.7@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex"><div dir=3D"ltr"><div>Reminder: the QUIC WGLC ends on July 8 20=
20</div><div><br></div><div>If you have review comments please raise them i=
n accordance with the instructions in the original announcement (attached).=
<br></div><div><br></div><div>Cheers,</div><div>Lucas, on behalf of the QUI=
C WG chairs<br></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=
=3D"gmail_attr">On Wed, Jun 10, 2020 at 2:36 AM Lucas Pardue &lt;<a href=3D=
"mailto:lucaspardue.24.7@gmail.com" target=3D"_blank">lucaspardue.24.7@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">Hello,<br><br>After more than three and a half years =
and substantial discussion, all 845 of the design issues raised against the=
 QUIC protocol drafts have gained consensus or have a proposed resolution. =
In that time the protocol has been considerably transformed; it has become =
more secure, much more widely implemented, and has been shown to be interop=
erable. Both the Chairs and the Editors feel that it is ready to proceed in=
 standardisation.<br><br>Therefore, this email announces a Working Group La=
st Call (WGLC) for the following QUIC documents:<br><br>* QUIC Transport<br=
>=C2=A0 <a href=3D"https://tools.ietf.org/html/draft-ietf-quic-transport-29=
" target=3D"_blank">https://tools.ietf.org/html/draft-ietf-quic-transport-2=
9</a><br><br>* QUIC Loss Detection and Congestion Control<br>=C2=A0 <a href=
=3D"https://tools.ietf.org/html/draft-ietf-quic-recovery-29" target=3D"_bla=
nk">https://tools.ietf.org/html/draft-ietf-quic-recovery-29</a><br><br>* Us=
ing TLS to Secure QUIC<br>=C2=A0 <a href=3D"https://tools.ietf.org/html/dra=
ft-ietf-quic-tls-29" target=3D"_blank">https://tools.ietf.org/html/draft-ie=
tf-quic-tls-29</a><br><br>* Version-Independent Properties of QUIC<br>=C2=
=A0 <a href=3D"https://tools.ietf.org/html/draft-ietf-quic-invariants-09" t=
arget=3D"_blank">https://tools.ietf.org/html/draft-ietf-quic-invariants-09<=
/a><br><br>* HTTP/3<br>=C2=A0 <a href=3D"https://tools.ietf.org/html/draft-=
ietf-quic-http-29" target=3D"_blank">https://tools.ietf.org/html/draft-ietf=
-quic-http-29</a><br><br>* QPACK Header Compression for HTTP/3<br>=C2=A0 <a=
 href=3D"https://tools.ietf.org/html/draft-ietf-quic-qpack-16" target=3D"_b=
lank">https://tools.ietf.org/html/draft-ietf-quic-qpack-16</a><br><br>The W=
GLC will run for four weeks, ending on 8 July 2020.<br><br>As a reminder, w=
e have been operating under the Late-Stage Process; see <a href=3D"https://=
github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md#late-stage-proces=
s" target=3D"_blank">https://github.com/quicwg/base-drafts/blob/master/CONT=
RIBUTING.md#late-stage-process</a><span></span><span></span>. In theory, th=
is means that the contents of the drafts above already have consensus. Howe=
ver, the Chairs would like to actively reaffirm that consensus and start th=
e process of wider review through a formal WGLC.<br><br>Please review the d=
ocuments above and open issues for your review comments in our repository a=
t <a href=3D"https://github.com/quicwg/base-drafts" target=3D"_blank">https=
://github.com/quicwg/base-drafts</a>. You may also send comments to <a href=
=3D"mailto:quic@ietf.org" target=3D"_blank">quic@ietf.org</a>.<br><br>Issue=
s raised during WGLC will be handled in accordance with the Late-Stage Proc=
ess defined in the Contribution Guidelines (see link above). Please note th=
at design issues that revisit a topic where there&#39;s already declared co=
nsensus (see <a href=3D"https://github.com/quicwg/base-drafts/issues?q=3Dis=
%3Aclosed+label%3Ahas-consensus" target=3D"_blank">https://github.com/quicw=
g/base-drafts/issues?q=3Dis%3Aclosed+label%3Ahas-consensus</a>) need to pro=
vide compelling reasons to warrant reopening the discussion.<br><br>As part=
 of this WGLC, we seek consensus on the remaining open design issue #3661 =
=E2=80=9CInclude epoch in the AAD or the nonce?=E2=80=9D (<a href=3D"https:=
//github.com/quicwg/base-drafts/issues/3661" target=3D"_blank">https://gith=
ub.com/quicwg/base-drafts/issues/3661</a>). The proposed resolution for thi=
s issue is to close with no action, which means that the drafts above alrea=
dy reflect this emerging consensus.<br><br>Subject to the feedback received=
 during this WGLC, a subsequent smaller WGLC may be run in the near future =
to confirm any changes to the drafts made between now and then.<br><br>The =
Applicability and Manageability drafts have some dependencies on the core d=
rafts, so we&#39;ll run separate WGLCs for them.<br><br>Cheers,<br><br>Lars=
, Lucas and Mark<br>QUIC WG Chairs<br></div>
</blockquote></div></div>
</blockquote></div>

--000000000000e5518605aa0313e1--


From nobody Thu Jul  9 09:11:40 2020
Return-Path: <pravb@microsoft.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D82723A0CC5 for <quic@ietfa.amsl.com>; Thu,  9 Jul 2020 09:11:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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, DKIM_VALID_EF=-0.1, HTML_MESSAGE=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=microsoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id T0LxllH_y47m for <quic@ietfa.amsl.com>; Thu,  9 Jul 2020 09:11:37 -0700 (PDT)
Received: from NAM06-BL2-obe.outbound.protection.outlook.com (mail-eopbgr650115.outbound.protection.outlook.com [40.107.65.115]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D5B443A0CAE for <quic@ietf.org>; Thu,  9 Jul 2020 09:11:36 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=fEOMZzuFBnsxdTb7ME8u5hTHNCdYfGrrHtmBYzzx8uPZFmmIz7cE36cVTGD23ZZNtLR616EOeYYs7Dbra7gsaJGJvE9QXf9sHtqiLVH5AigkWTsFT/cyPMBxhyGOZwpAHK1hfguEl/awSWwfozl0oXJpD8+KQ6YMRjZYMrEv3yni2NUwg1sM3YOdKhGQ6qHLOFG20yXevpv/I/IsjPqTyZ7vINE2lKxFLziP1BsNudc1RAUpJcVdTZGbVf/1dnc/evhvyYpAvqyvDb7FR5pupqKoVTb1BMl00hLv5pitxYzL8WE6pbFIC3qwPWWp9gQDULOgXPJ0Wt8eIBkmUhwM8w==
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=aRFnuG4RoT6eUJefQsZLxCNKZat7Rc9sd4K1oM6jSG0=; b=lz87o9tC5c+wwafywu2Z4UKn6HwpLM84m2hX5GeHZP+xxie3vo2zkV0uITLuqnLaVelCIzyJnOj2wR/CR05fiVEtMt8+hkSKEMjSsOd9aJEsmyKCs1UgRiZ0wRPPOu9w+RSFQaRSbCAiRL/2AmWfbxwCSDivVRRSABgV+3DGJEkng/UQAhhH/9S5FZ7tL+TA15IuD/RE1E6v2P1lYRqpt6w8yqI0zu01baF0hCFad8/bWl9bu1A9XL+6tiV0VIWMK0TlQvJ1WYF3rfb5PWM8dpcTicuVyMdSliEDrUW9+IDF0muvrt8oxoTkZcbcUzIylSjJGCLI6fA8x75tVUgnBw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=aRFnuG4RoT6eUJefQsZLxCNKZat7Rc9sd4K1oM6jSG0=; b=Cuj85m2TfFf6fVtmb6GRHSrazh29gGZoKM2QfR73uLJYxznqdl8Swo9WDrsfSjbfsyx5IPaqGAutJXQd/y+bZGxIPrIVwkLjn7zcGd2XQUl9v3GhGKPJkTocitsQof62pnLaDPyEEGw+RdwBaPlsTAkjWlyvVnDn82OcPB87XLI=
Received: from CH2PR00MB0726.namprd00.prod.outlook.com (2603:10b6:610:ad::12) by CH2PR00MB0694.namprd00.prod.outlook.com (2603:10b6:610:a8::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3216.0; Thu, 9 Jul 2020 16:11:33 +0000
Received: from CH2PR00MB0726.namprd00.prod.outlook.com ([fe80::7562:9640:814e:c7f1]) by CH2PR00MB0726.namprd00.prod.outlook.com ([fe80::7562:9640:814e:c7f1%8]) with mapi id 15.20.3213.000; Thu, 9 Jul 2020 16:11:33 +0000
From: Praveen Balasubramanian <pravb@microsoft.com>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, IETF QUIC WG <quic@ietf.org>
Subject: RE: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
Thread-Topic: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
Thread-Index: AdZVbt/Rv8RxmVSLQP+4+5gZJ/6HOgAXZSqAAA+FIqA=
Date: Thu, 9 Jul 2020 16:11:33 +0000
Message-ID: <CH2PR00MB0726D18611EC030BF548CA0DB6640@CH2PR00MB0726.namprd00.prod.outlook.com>
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <53187d65-f7b9-b99a-f68b-b267303ab399@erg.abdn.ac.uk>
In-Reply-To: <53187d65-f7b9-b99a-f68b-b267303ab399@erg.abdn.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=true; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2020-07-09T16:11:32Z;  MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=4a85eab6-ae5a-4217-a53e-ca165326cbc5; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0
authentication-results: erg.abdn.ac.uk; dkim=none (message not signed) header.d=none;erg.abdn.ac.uk; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [2001:4898:80e8:3:95d5:3f73:f682:d302]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: d235d709-a628-4a5b-c82e-08d82422bf81
x-ms-traffictypediagnostic: CH2PR00MB0694:
x-microsoft-antispam-prvs: <CH2PR00MB0694F1C4C68227053268DEF1B6640@CH2PR00MB0694.namprd00.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8273;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: mZ+ZdhyUDmJUE7qr2nzvz3eCZVHtxDOthgo7zlktgrM2GNDxsVRkvMgOx+tnb360kXgfLDL/sQpbuZWF5Bfa1yDZyucMYpq7+vssAzCKKBd9n7mX1lFWwcuFnSoLrQJsqD4PD/6nLszrGKiAk0MSJBc3ltE4z80Ft1kTsbVji59UAQR1cNqWoG0OpEkQG3tv0RiRhhptE5iTQhSRO7H/iCJa+Kc79ifR4MOG54o4tyhOWsWJlBe3ZJ4J3yVo1gRIaZkVJlUNrSpeiAnwQrhnPno9MSoTcF3wctjLY6AzC3kSoVWsZCiDjRYNXdze8++3
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:CH2PR00MB0726.namprd00.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(396003)(366004)(136003)(376002)(39860400002)(346002)(8936002)(66446008)(66556008)(66476007)(478600001)(66946007)(8990500004)(64756008)(33656002)(76116006)(8676002)(71200400001)(7696005)(10290500003)(52536014)(66574015)(186003)(5660300002)(9686003)(6506007)(53546011)(2906002)(83380400001)(82950400001)(82960400001)(55016002)(296002)(316002)(110136005)(86362001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: KAct7MWQzwaj4sFhgrZydM0Ly0WgzUXJ0++FTxqT1unjEx4X57aTofknmKmWtqbeI8AVGKSNNNeSZagBBwz4EZH8PJ3vmMUJxQjso0k2VTq1L2h3XTkaY0MiKaEXnFiKuzRR95UpO9WHUZrgAMxwINEIsEaT0vKVBNUkjtD8MnRU6XIHGXJfd8z3Bj62C5XC+Jklgeqg4a50XVl8uEMTu1C0dT/lnaLvzQVUS9z7A2a1NRG7vMloOQxgcrDWZqT/41QCb40BzjhmpjTnqZ6pktU+yXRO+FnJzJOUX1ZH7wowc+nQN4fW9BjOt72KLRHVUInU8UPtr+CQKMCt4cwRl6MQzKn/dUGcpd+MqsPePb5+w+pZQfO/w2St+8E/OIL7z6/jHfZYKhJGZRtoQi72abfzsQ1cXNMgyh1qsv2pU5h5i6XwSOf9QUMcT5E72V/ztmZUdX5hBLTFOCwt7RYpN9dJ5+L+PwqueTUAmn7Holj2EmPcw5UuZ9pqaKCecbJzRdh07Bn3SB+iPUnsnmqVs1jur4bzUnAw3gOgsBVTs4I=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CH2PR00MB0726D18611EC030BF548CA0DB6640CH2PR00MB0726namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CH2PR00MB0726.namprd00.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: d235d709-a628-4a5b-c82e-08d82422bf81
X-MS-Exchange-CrossTenant-originalarrivaltime: 09 Jul 2020 16:11:33.1514 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 5QBrbpp+mpuYmg/AKNtyHajSm7a1Z8nRGWwzdJjLaDxrVxNpW3iDtuP1mX7bUHU8kyNdgg3mmAwHiSmvkAFxDpmGZiqJ4BfIVZ/NyfQEfCA=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR00MB0694
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/oEU40rdHrY_TzDUl9Qi48rHE6m4>
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, 09 Jul 2020 16:11:39 -0000

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

Within data center mainly. To hit 40 Gbps line rate you effectively have to=
 batch as much as you can to minimize the CPU processing costs. The burst s=
ize today is capped to 64k in most cases for TCP. Now that we have segmenta=
tion offload for UDP the same should apply. Even for Internet facing traffi=
c, the bursts primarily impact the first hop within the datacenter because =
subsequently you get statistical multiplexing from ToR switch handling traf=
fic forwarding for many flows and ports.

Ok understood about there being no conflict. But I still contend that the M=
UST regarding burst size is way too restrictive. We should allow for experi=
mentation here. Or present data that this is universally bad on all network=
s. Current production use of TCP shows there is no major problems with burs=
ting higher. In fact for low latency same rack scenarios this will boost re=
ceive performance as well due to better opportunity for LRO etc.

From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Sent: Thursday, July 9, 2020 1:39 AM
To: Praveen Balasubramanian <pravb@microsoft.com>; IETF QUIC WG <quic@ietf.=
org>
Subject: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29


Hi Praveen,
On 08/07/2020 22:29, Praveen Balasubramanian wrote:
Section 7.9
"Implementations MUST either use pacing or another method to limit such bur=
sts to the initial congestion window; see Section 7.2."
This seems to preclude use of segmentation offload of sizes greater than IW=
. In datacenters we routinely send bursts that are higher without causing l=
oss.
Is that within data centres? or from data centres to Internet destinations?=
 ... if the latter, how can the sender be sure this is not impacting other =
traffic?

The MUST here seems unnecessary. It also conflicts with the RECOMMENDED in =
an earlier sentence.

I actually don't see this as conflicting. The recommendation in this sectio=
n is to pace. The requirement is that sender limits burst, using some metho=
d, to the size of IW.

Gorry



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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Within data center mainly. To hit 40 Gbps line rate =
you effectively have to batch as much as you can to minimize the CPU proces=
sing costs. The burst size today is capped to 64k in most cases for TCP. No=
w that we have segmentation offload
 for UDP the same should apply. Even for Internet facing traffic, the burst=
s primarily impact the first hop within the datacenter because subsequently=
 you get statistical multiplexing from ToR switch handling traffic forwardi=
ng for many flows and ports.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Ok understood about there being no conflict. But I s=
till contend that the MUST regarding burst size is way too restrictive. We =
should allow for experimentation here. Or present data that this is univers=
ally bad on all networks. Current
 production use of TCP shows there is no major problems with bursting highe=
r. In fact for low latency same rack scenarios this will boost receive perf=
ormance as well due to better opportunity for LRO etc.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Gorry Fairhurst &lt;gorry@erg.abdn.ac.u=
k&gt; <br>
<b>Sent:</b> Thursday, July 9, 2020 1:39 AM<br>
<b>To:</b> Praveen Balasubramanian &lt;pravb@microsoft.com&gt;; IETF QUIC W=
G &lt;quic@ietf.org&gt;<br>
<b>Subject:</b> [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29<o=
:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p>Hi Praveen,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On 08/07/2020 22:29, Praveen Balasubramanian wrote:<=
o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Section 7.9<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&quot;Implementations MUST either use pacing or another method to =
limit such bursts to the initial congestion window; see Section 7.2.&quot;
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">This seems to preclude use of segmentation offload of sizes greate=
r than IW. In datacenters we routinely send bursts that are higher without =
causing loss.
<o:p></o:p></p>
</blockquote>
<p class=3D"MsoNormal">Is that within data centres? or from data centres to=
 Internet destinations? ... if the latter, how can the sender be sure this =
is not impacting other traffic?<br>
<br>
<o:p></o:p></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The MUST here seems unnecessary. It also conflicts with the RECOMM=
ENDED in an earlier sentence.<o:p></o:p></p>
</blockquote>
<p>I actually don't see this as conflicting. The recommendation in this sec=
tion is to pace. The requirement is that sender limits burst, using some me=
thod, to the size of IW.<o:p></o:p></p>
<p>Gorry<o:p></o:p></p>
<p><o:p>&nbsp;</o:p></p>
</div>
</body>
</html>

--_000_CH2PR00MB0726D18611EC030BF548CA0DB6640CH2PR00MB0726namp_--


From jonas.reynders@student.uhasselt.be  Thu Jul  9 04:55:54 2020
Return-Path: <jonas.reynders@student.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 439D43A08C7 for <quic@ietfa.amsl.com>; Thu,  9 Jul 2020 04:55:54 -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, HTML_MESSAGE=0.001, 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=student.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 sck2yFtBH0Jp for <quic@ietfa.amsl.com>; Thu,  9 Jul 2020 04:55:51 -0700 (PDT)
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 71D593A08CA for <quic@ietf.org>; Thu,  9 Jul 2020 04:55:51 -0700 (PDT)
Received: by mail-lj1-x236.google.com with SMTP id q7so2078982ljm.1 for <quic@ietf.org>; Thu, 09 Jul 2020 04:55:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=student.uhasselt.be; s=google; h=mime-version:from:date:message-id:subject:to; bh=AzHC1URd/VuKYGuUiPPPb2L75kIGARUbo8TCoP2R4Hc=; b=WXjC9xib7XY8WP03Na4qlVLFvxqMtxcgD6To2q/k4/77eK+nl+S2vH+ynaxD6J2FYd r3pNh0VzCc9PMyXm+Vzd74pcrPLw4D0h6mfIvBpp+pSNvJdMeFnU/cdEumtHxgQNRi2r 7f2h3XF7f1coNCNRrfEMqALKu2Qs4bNiewvXM=
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=AzHC1URd/VuKYGuUiPPPb2L75kIGARUbo8TCoP2R4Hc=; b=ByWqtnyEqspgFPSY2tZ02njhNKmdldg0AuvLi1DteW58MCqXac29YNcXyXJ8iCONif IQ8CvKPClFeSjFweSpgisJFQZB8+Bcz3VlojcMY6G6nss23pK8+rG3+5bw2KWprQTsT2 PpJYCp4BgyTt87/qwdDhVWJCaDa648B8N92mAzJEgUMUSDBslnNXsJ5rc5igRpBFztbE YcXHe+RL55TmdVQ4lDGl3fGyZDsN96iSgDDzAoBXavyh1yJZL+4Yh/2cXDXnk2Ac0BSE ZB8wYzfyZ2+CYXa/yIRzovCaOOXetLadN/eP0eJ+MkQoUYUa6CTxAaltQzavTaqXBkaE bFTA==
X-Gm-Message-State: AOAM530VEWsb6V80j9lEqx70C0c/YwTgvUBS/AhjZfZipbko/ptrfuX/ A7r23tbBE7UhAFs6iDh2S5x8sd3ch4JZe0m8oUE7LQQoRSQ=
X-Google-Smtp-Source: ABdhPJxo4pCcrYWMu4EWnNsNjsw44TkegJly6dSt7q1oJ0q4gDUbrxYJKK463l34tVAlpHqksISOhhj9RMwfMmhCzbE=
X-Received: by 2002:a2e:9050:: with SMTP id n16mr35361252ljg.376.1594295748816;  Thu, 09 Jul 2020 04:55:48 -0700 (PDT)
MIME-Version: 1.0
From: Jonas Reynders <jonas.reynders@student.uhasselt.be>
Date: Thu, 9 Jul 2020 13:55:35 +0200
Message-ID: <CABC-CqayJAeipEhsTf4h8rkUVQvYLd=1wF4UBMkaYSNMfvgnXw@mail.gmail.com>
Subject: Questions about recovery draft 29
To: quic@ietf.org
Content-Type: multipart/alternative; boundary="000000000000c693c005aa00e762"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/RUtH6HlAd_nZ7eq7ln-t8kwPZe4>
X-Mailman-Approved-At: Thu, 09 Jul 2020 09:22:09 -0700
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, 09 Jul 2020 11:58:14 -0000

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

I have been looking at the recovery draft 29 of QUIC and comparing it to
TCP, specifically the linux implementation in kernel v5.4. I have a couple
of questions about the design choices that differ from TCP in linux.

The first question is in regards to ack-based loss detection where QUIC
uses both a packet-threshold and time-threshold method. Looking at the
linux implementation (kernel v5.4), TCP uses only a time-threshold method
(RACK) as default. From my understanding both methods were used in linux
some time ago, around the time it was clarified to use both methods for
QUIC as well. However since then TCP changed to RACK only as the default,
from what I found out it was due to tests at google detecting a 10%
reduction in recovery latency (reference:
https://patchwork.ozlabs.org/project/netdev/cover/20180516234017.172775-1-y=
cheng@google.com/).
My question is why QUIC still recommends using both methods as default? I
can understand that in a datacenter context, where RTT values are really
low, RACK can struggle due to timers not being fine grained.

My second question is in regards to the time threshold calculation(6.1.2 in
recovery draft). QUIC uses a constant value (9/8) for the time threshold,
whilst in linux an adaptive threshold is used in the form of a reordering
window variable. In the recovery draft it is mentioned that adaptive
thresholds can be used, however it=E2=80=99s not mandatory. Is there a reas=
on why
QUIC doesn=E2=80=99t use the linux method for an adaptive threshold? The dr=
aft also
mentions that reordering can be more common in QUIC and that adaptive
thresholds have the advantage of being more aggressive when there is no
reordering. The same question for the packet threshold, QUIC uses a
constant threshold of 3 packets whilst in linux there is an adaptive
threshold.

My last question is that of merging the TLP and RTO into PTO. If I
understand correctly, this was possible due to probe packet being
ack-eliciting. And, that the time-threshold method would detect loss in a
similar manner to RTO, with the RTO also causing a congestion collapse if
no acks were received for consecutive RTOs. I assume that keeping RTO would
unnecessarily complicate things, is that correct?

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

<div dir=3D"ltr">I have been looking at the recovery draft 29 of QUIC and c=
omparing it to TCP, specifically the linux implementation in kernel v5.4. I=
 have a couple of questions about the design choices that differ from TCP i=
n linux.<br><br>The first question is in regards to ack-based loss detectio=
n where QUIC uses both a packet-threshold and time-threshold method. Lookin=
g at the linux implementation (kernel v5.4), TCP uses only a time-threshold=
 method (RACK) as default. From my understanding both methods were used in =
linux some time ago, around the time it was clarified to use both methods f=
or QUIC as well. However since then TCP changed to RACK only as the default=
, from what I found out it was due to tests at google detecting a 10% reduc=
tion in recovery latency (reference:=C2=A0<a href=3D"https://patchwork.ozla=
bs.org/project/netdev/cover/20180516234017.172775-1-ycheng@google.com/">htt=
ps://patchwork.ozlabs.org/project/netdev/cover/20180516234017.172775-1-yche=
ng@google.com/</a>). My question is why QUIC still recommends using both me=
thods as default? I can understand that in a datacenter context, where RTT =
values are really low, RACK can struggle due to timers not being fine grain=
ed.<div><div><br>My second question is in regards to the time threshold cal=
culation(6.1.2 in recovery draft). QUIC uses a constant value (9/8) for the=
 time threshold, whilst in linux an adaptive threshold is used in the form =
of a reordering window variable. In the recovery draft it is mentioned that=
 adaptive thresholds can be used, however it=E2=80=99s not mandatory. Is th=
ere a reason why QUIC doesn=E2=80=99t use the linux method for an adaptive =
threshold? The draft also mentions that reordering can be more common in QU=
IC and that adaptive thresholds have the advantage of being more aggressive=
 when there is no reordering. The same question for the packet threshold, Q=
UIC uses a constant threshold of 3 packets whilst in linux there is an adap=
tive threshold.<br><br>My last question is that of merging the TLP and RTO =
into PTO. If I understand correctly, this was possible due to probe packet =
being ack-eliciting. And, that the time-threshold method would detect loss =
in a similar manner to RTO, with the RTO also causing a congestion collapse=
 if no acks were received for consecutive RTOs. I assume that keeping RTO w=
ould unnecessarily complicate things, is that correct?=C2=A0<br></div></div=
></div>

--000000000000c693c005aa00e762--


From nobody Thu Jul  9 12:10:35 2020
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 5BA633A0DD3 for <quic@ietfa.amsl.com>; Thu,  9 Jul 2020 12:10:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, 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 DHWJVf99Xg3S for <quic@ietfa.amsl.com>; Thu,  9 Jul 2020 12:10:32 -0700 (PDT)
Received: from mail-vs1-xe31.google.com (mail-vs1-xe31.google.com [IPv6:2607:f8b0:4864:20::e31]) (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 A3C3A3A079C for <quic@ietf.org>; Thu,  9 Jul 2020 12:10:32 -0700 (PDT)
Received: by mail-vs1-xe31.google.com with SMTP id x205so1678640vsc.11 for <quic@ietf.org>; Thu, 09 Jul 2020 12:10:32 -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=b7aZQn2gcSwiSvTMk78rQm9XtdXhbk2mkgwRAMPWmtM=; b=lZbS3Vg6Intq7wOFJUEi6E+z/A8UKdgdYcjA+xcwbWtjuidHYlS1p0D8rGdCbwj3o9 aiY3Ks4/q+IWbQ8Ul8+Nj2ALw1YXnDsLRDxQtukjdKWKKc3APNc0+8Gvikz+Zz4dVVzx 4YJKdXwERUC+aJk5Zspsxk5hb9BwOnadSMQycpv/THHtZBnOYaTzYsl+RU7FLLAfBk+o jUU8lvvqhHTx9M+5XShUhMq1fjBSix2PABk/94B6/EqY87U1SmMDWQiVseou2nOqQuMg huioX5wlZiYMOxx8bc0DCSq5z6hdkx8ZDu6rKFlash4AUrUY0zNzOzV03rrj5XPl9iiI fFPA==
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=b7aZQn2gcSwiSvTMk78rQm9XtdXhbk2mkgwRAMPWmtM=; b=YUGzclm7qAAUNTVsmRnFhGMYYQtqZ/4HJB+/Xka8dnXtLSniZZkcob0pgFzMkAu1sQ LaY2zT0LwEl2jAg5L1bMlGU3IqtL6QK901Fh0EptL2dOenUNhLwvkdPToIQ5AuuziKd2 8UvTMLqgeaxEQ++WlG1XjcKM8SH5RfdlZ8Bphb6eWL4QNsmDD8ng76GiI7MJDL81rvJb zNi6WDvuF/y21R9kOj1ap0MXyfLl4dZkwdciYBLmH5AjjPy4HvkcofnQq7oFlebs527D PGdWo2sJYtmeR8uDptm6TqD70ORsVIQISOeyVh+mtlciFEu+vKpglStLTKpwjFXLoeaf 82bw==
X-Gm-Message-State: AOAM531FxsVAzCXeqdy7KuKPkjkA3rPCcQwzQayoHNNmbI5HU18ux+6+ 1zdBNfKZfINtnJSrl7n5YI2x0eC92zb9smnezSbrJGK+
X-Google-Smtp-Source: ABdhPJx3uhcijMUZnX6EL1BvBdR3gNb265gdf7aJ3I/B8YLIzgkzytaxOsc4CveGZ+dxkI6qRZvEXobmaXvzETslquo=
X-Received: by 2002:a05:6102:20a:: with SMTP id z10mr39520811vsp.213.1594321831326;  Thu, 09 Jul 2020 12:10:31 -0700 (PDT)
MIME-Version: 1.0
References: <CABC-CqayJAeipEhsTf4h8rkUVQvYLd=1wF4UBMkaYSNMfvgnXw@mail.gmail.com>
In-Reply-To: <CABC-CqayJAeipEhsTf4h8rkUVQvYLd=1wF4UBMkaYSNMfvgnXw@mail.gmail.com>
From: Matt Joras <matt.joras@gmail.com>
Date: Thu, 9 Jul 2020 12:10:19 -0700
Message-ID: <CADdTf+jxKyPw_zfJ6FWCz230rXqg83d7rQJhKBteBvoLCut1RQ@mail.gmail.com>
Subject: Re: Questions about recovery draft 29
To: Jonas Reynders <jonas.reynders@student.uhasselt.be>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/RbDblBEhfavXgaRWHHRtU5wA4l4>
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, 09 Jul 2020 19:10:34 -0000

I won't offer specific answers to all your questions as Ian or Jana
likely have better ones, however I'd like to make a general point
about this line of questioning: Linux TCP !=3D IETF TCP, or, said
another way, Implementations and Specifications are not the same
thing. Recall that QUIC is a series of specifications being developed
by the IETF, similar to the myriad RFCs that loosely define "IETF
TCP". Linux's TCP stack is one such interpretation/implementation of
TCP, and while it can inform the decisions of IETF workings, it should
not be an undue determiner of the development of said specifications.
Similarly we have an even wider and more diverse collection of QUIC
interpretations/implementations in various states of maturity and
deployment. Many diverge, sometimes heavily, from the specifications
especially insofar as recovery is concerned. Chrome and us (mvfst) use
BBR as the default congestion controller, others use Cubic or HSTCP or
who knows what else. Chrome, AFAIK has a notion of adaptive reordering
similar to Linux TCP and modifications to the draft-suggested time
thresholds and PTO strategy.

Whether some of these changes should be codified in the QUIC
specifications is a good question. My hope is that these best
practices will gain deployment experience and drive consensus at the
IETF in future iterations of QUIC recovery and encounter fewer
roadblocks than innovations based on TCP have historically
experienced. As it is now though, QUIC's charter, by design, largely
limits us to the adaptation of recovery and congestion control work
that has already gained consensus via other IETF RFCs. That being
said, what we have in the recovery specs may not be the "state of the
art" exactly, but it is still quite good and I would argue has other
significant advantages over what is commonly deployed in TCP, even
Linux TCP.

Matt Joras

On Thu, Jul 9, 2020 at 9:22 AM Jonas Reynders
<jonas.reynders@student.uhasselt.be> wrote:
>
> I have been looking at the recovery draft 29 of QUIC and comparing it to =
TCP, specifically the linux implementation in kernel v5.4. I have a couple =
of questions about the design choices that differ from TCP in linux.
>
> The first question is in regards to ack-based loss detection where QUIC u=
ses both a packet-threshold and time-threshold method. Looking at the linux=
 implementation (kernel v5.4), TCP uses only a time-threshold method (RACK)=
 as default. From my understanding both methods were used in linux some tim=
e ago, around the time it was clarified to use both methods for QUIC as wel=
l. However since then TCP changed to RACK only as the default, from what I =
found out it was due to tests at google detecting a 10% reduction in recove=
ry latency (reference: https://patchwork.ozlabs.org/project/netdev/cover/20=
180516234017.172775-1-ycheng@google.com/). My question is why QUIC still re=
commends using both methods as default? I can understand that in a datacent=
er context, where RTT values are really low, RACK can struggle due to timer=
s not being fine grained.
>
> My second question is in regards to the time threshold calculation(6.1.2 =
in recovery draft). QUIC uses a constant value (9/8) for the time threshold=
, whilst in linux an adaptive threshold is used in the form of a reordering=
 window variable. In the recovery draft it is mentioned that adaptive thres=
holds can be used, however it=E2=80=99s not mandatory. Is there a reason wh=
y QUIC doesn=E2=80=99t use the linux method for an adaptive threshold? The =
draft also mentions that reordering can be more common in QUIC and that ada=
ptive thresholds have the advantage of being more aggressive when there is =
no reordering. The same question for the packet threshold, QUIC uses a cons=
tant threshold of 3 packets whilst in linux there is an adaptive threshold.
>
> My last question is that of merging the TLP and RTO into PTO. If I unders=
tand correctly, this was possible due to probe packet being ack-eliciting. =
And, that the time-threshold method would detect loss in a similar manner t=
o RTO, with the RTO also causing a congestion collapse if no acks were rece=
ived for consecutive RTOs. I assume that keeping RTO would unnecessarily co=
mplicate things, is that correct?


From nobody Fri Jul 10 01:21:10 2020
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 609C63A0EBA for <quic@ietfa.amsl.com>; Fri, 10 Jul 2020 01:21:08 -0700 (PDT)
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, 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 v6alN8-fdlgE for <quic@ietfa.amsl.com>; Fri, 10 Jul 2020 01:21:05 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id 008F13A0EC1 for <quic@ietf.org>; Fri, 10 Jul 2020 01:21:04 -0700 (PDT)
Received: from GF-MacBook-Pro.lan (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id C7D021B000A3; Fri, 10 Jul 2020 09:21:01 +0100 (BST)
Subject: Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
To: Praveen Balasubramanian <pravb@microsoft.com>, IETF QUIC WG <quic@ietf.org>
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <53187d65-f7b9-b99a-f68b-b267303ab399@erg.abdn.ac.uk> <CH2PR00MB0726D18611EC030BF548CA0DB6640@CH2PR00MB0726.namprd00.prod.outlook.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <40818629-e1dc-f0f1-6173-984a8166c7c2@erg.abdn.ac.uk>
Date: Fri, 10 Jul 2020 09:21:00 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <CH2PR00MB0726D18611EC030BF548CA0DB6640@CH2PR00MB0726.namprd00.prod.outlook.com>
Content-Type: multipart/alternative; boundary="------------7F5A35BA621E9AFAB1111B71"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/vRCD2HcWw1gUz7cWbISsV3Q1c4c>
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, 10 Jul 2020 08:21:08 -0000

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

Thanks Praveen,

I'd like to talk more, see below:

On 09/07/2020 17:11, Praveen Balasubramanian wrote:
>
> Within data center mainly. To hit 40 Gbps line rate you effectively 
> have to batch as much as you can to minimize the CPU processing costs. 
> The burst size today is capped to 64k in most cases for TCP. Now that 
> we have segmentation offload for UDP the same should apply. Even for 
> Internet facing traffic, the bursts primarily impact the first hop 
> within the datacenter because subsequently you get statistical 
> multiplexing from ToR switch handling traffic forwarding for many 
> flows and ports.
>
I get this for this use-case and comments on high-speed NICs. I agree 
offload is important.

> Ok understood about there being no conflict. But I still contend that 
> the MUST regarding burst size is way too restrictive. We should allow 
> for experimentation here.
>
I am not sure. The IW spec for TCP was based on evidence back around 
2010, and the IETF agreed in RFC6928 that a burst size of 10 was 
acceptable as an EXP spec for TCP.

I think we can safely refer to that - even perhaps take the 
leap-of-faith that EXP for TCP is equivalent to PS for QUIC, given 
subsequent experience.  I think the IW  **is** the burst size that the 
IETF should specify (because it's dictated by buffering that is expected 
on the path).

I see opportunities here for experimentation and measurement 
opportunities, and new specs can be proposed. Or the Specs can be recast 
with more detail. I also know that practical experience is that many 
people have configured (probably tested, I hope) much larger IW's - and 
I'd hope they also make a reasonable effort to monitor for possible 
interactions with other Internet applications and services (as per 
section 12 of RFC6928).

> Or present data that this is universally bad on all networks.
>
I think you touch on something that the IETF hasn't been great at 
talking about:

I could myself indeed likely produce data this shows this is "bad" in 
some networks that I value, and also show side-effects of collateral 
damage to other flows and adverse effects of line-rate bursts into 
equipment with small buffers. I don't know how useful that would be at all.

The IETF has typically defined a spec for endpoint. The way a modern 
endpoint is implemented can be quite different in a DC from a single 
device connected to the Internet. In a DC, I understand it is common  to 
distribute transport functions to other parts of the network. e.g.: DDOS 
protection could be done on a server; or by a box in front of it - 
similarly what matters to the network CC is the  bursts of traffic that 
leaves a DC within a flow to a local receiver, not what leaves a 
particular server within the DC network - I think in future we may do 
well to consider these differences?

> Current production use of TCP shows there is no major problems with 
> bursting higher. In fact for low latency same rack scenarios this will 
> boost receive performance as well due to better opportunity for LRO etc.
>
It's also possible that QUIC LRO (or whatever) includes some notion of 
per-flow burst-mitigation. Is that impossible?

However, I personally would not hold-up QUIC, to arrive at a new consensus.

Gorry

> *From:* Gorry Fairhurst <gorry@erg.abdn.ac.uk>
> *Sent:* Thursday, July 9, 2020 1:39 AM
> *To:* Praveen Balasubramanian <pravb@microsoft.com>; IETF QUIC WG 
> <quic@ietf.org>
> *Subject:* [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
>
> Hi Praveen,
>
> On 08/07/2020 22:29, Praveen Balasubramanian wrote:
>
>     Section 7.9
>
>     "Implementations MUST either use pacing or another method to limit
>     such bursts to the initial congestion window; see Section 7.2."
>
>     This seems to preclude use of segmentation offload of sizes
>     greater than IW. In datacenters we routinely send bursts that are
>     higher without causing loss.
>
> Is that within data centres? or from data centres to Internet 
> destinations? ... if the latter, how can the sender be sure this is 
> not impacting other traffic?
>
>     The MUST here seems unnecessary. It also conflicts with the
>     RECOMMENDED in an earlier sentence.
>
> I actually don't see this as conflicting. The recommendation in this 
> section is to pace. The requirement is that sender limits burst, using 
> some method, to the size of IW.
>
> Gorry
>

--------------7F5A35BA621E9AFAB1111B71
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: 8bit

<html>
  <head>
    <meta http-equiv="Content-Type" content="text/html;
      charset=windows-1252">
  </head>
  <body>
    <p>Thanks Praveen, <br>
    </p>
    <p>I'd like to talk more, see below:<br>
    </p>
    <div class="moz-cite-prefix">On 09/07/2020 17:11, Praveen
      Balasubramanian wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CH2PR00MB0726D18611EC030BF548CA0DB6640@CH2PR00MB0726.namprd00.prod.outlook.com">
      <meta http-equiv="Content-Type" content="text/html;
        charset=windows-1252">
      <meta name="Generator" content="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;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
      <div class="WordSection1">
        <p class="MsoNormal">Within data center mainly. To hit 40 Gbps
          line rate you effectively have to batch as much as you can to
          minimize the CPU processing costs. The burst size today is
          capped to 64k in most cases for TCP. Now that we have
          segmentation offload for UDP the same should apply. Even for
          Internet facing traffic, the bursts primarily impact the first
          hop within the datacenter because subsequently you get
          statistical multiplexing from ToR switch handling traffic
          forwarding for many flows and ports.
          <o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
      </div>
    </blockquote>
    <p>I get this for this use-case and comments on high-speed NICs. I
      agree offload is important.</p>
    <blockquote type="cite"
cite="mid:CH2PR00MB0726D18611EC030BF548CA0DB6640@CH2PR00MB0726.namprd00.prod.outlook.com">
      <div class="WordSection1">
        <p class="MsoNormal">Ok understood about there being no
          conflict. But I still contend that the MUST regarding burst
          size is way too restrictive. We should allow for
          experimentation here. </p>
      </div>
    </blockquote>
    <p>I am not sure. The IW spec for TCP was based on evidence back
      around 2010, and the IETF agreed in RFC6928 that a burst size of
      10 was acceptable as an EXP spec for TCP. <br>
    </p>
    <p>I think we can safely refer to that - even perhaps take the
      leap-of-faith that EXP for TCP is equivalent to PS for QUIC, given
      subsequent experience.  I think the IW  **is** the burst size that
      the IETF should specify (because it's dictated by buffering that
      is expected on the path).<br>
    </p>
    <p>I see opportunities here for experimentation and measurement
      opportunities, and new specs can be proposed. Or the Specs can be
      recast with more detail. I also know that practical experience is
      that many people have configured (probably tested, I hope) much
      larger IW's - and I'd hope they also make a reasonable effort to
      monitor for possible interactions with other Internet applications
      and services (as per section 12 of RFC6928). <br>
    </p>
    <p> </p>
    <blockquote type="cite"
cite="mid:CH2PR00MB0726D18611EC030BF548CA0DB6640@CH2PR00MB0726.namprd00.prod.outlook.com">
      <div class="WordSection1">
        <p class="MsoNormal">Or present data that this is universally
          bad on all networks. </p>
      </div>
    </blockquote>
    <p>I think you touch on something that the IETF hasn't been great at
      talking about:</p>
    <p>I could myself indeed likely produce data this shows this is
      "bad" in some networks that I value, and also show side-effects of
      collateral damage to other flows and adverse effects of line-rate
      bursts into equipment with small buffers. I don't know how useful
      that would be at all.</p>
    <p>The IETF has typically defined a spec for endpoint. The way a
      modern endpoint is implemented can be quite different in a DC from
      a single device connected to the Internet. In a DC, I understand
      it is common  to distribute transport functions to other parts of
      the network. e.g.: DDOS protection could be done on a server; or
      by a box in front of it - similarly what matters to the network CC
      is the  bursts of traffic that leaves a DC within a flow to a
      local receiver, not what leaves a particular server within the DC
      network - I think in future we may do well to consider these
      differences?<br>
    </p>
    <blockquote type="cite"
cite="mid:CH2PR00MB0726D18611EC030BF548CA0DB6640@CH2PR00MB0726.namprd00.prod.outlook.com">
      <div class="WordSection1">
        <p class="MsoNormal">Current production use of TCP shows there
          is no major problems with bursting higher. In fact for low
          latency same rack scenarios this will boost receive
          performance as well due to better opportunity for LRO etc.
        </p>
      </div>
    </blockquote>
    <p>It's also possible that QUIC LRO (or whatever) includes some
      notion of per-flow burst-mitigation. Is that impossible?</p>
    <p>However, I personally would not hold-up QUIC, to arrive at a new
      consensus.</p>
    <p>Gorry<br>
    </p>
    <blockquote type="cite"
cite="mid:CH2PR00MB0726D18611EC030BF548CA0DB6640@CH2PR00MB0726.namprd00.prod.outlook.com">
      <div class="WordSection1">
        <p class="MsoNormal"><o:p></o:p></p>
        <p class="MsoNormal"><o:p> </o:p></p>
        <div>
          <div style="border:none;border-top:solid #E1E1E1
            1.0pt;padding:3.0pt 0in 0in 0in">
            <p class="MsoNormal"><b>From:</b> Gorry Fairhurst
              <a class="moz-txt-link-rfc2396E" href="mailto:gorry@erg.abdn.ac.uk">&lt;gorry@erg.abdn.ac.uk&gt;</a> <br>
              <b>Sent:</b> Thursday, July 9, 2020 1:39 AM<br>
              <b>To:</b> Praveen Balasubramanian
              <a class="moz-txt-link-rfc2396E" href="mailto:pravb@microsoft.com">&lt;pravb@microsoft.com&gt;</a>; IETF QUIC WG
              <a class="moz-txt-link-rfc2396E" href="mailto:quic@ietf.org">&lt;quic@ietf.org&gt;</a><br>
              <b>Subject:</b> [EXTERNAL] Re: WGLC review of
              draft-ietf-quic-recovery-29<o:p></o:p></p>
          </div>
        </div>
        <p class="MsoNormal"><o:p> </o:p></p>
        <p>Hi Praveen,<o:p></o:p></p>
        <div>
          <p class="MsoNormal">On 08/07/2020 22:29, Praveen
            Balasubramanian wrote:<o:p></o:p></p>
        </div>
        <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
          <p class="MsoNormal"
            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">Section
            7.9<o:p></o:p></p>
          <p class="MsoNormal"
            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">"Implementations
            MUST either use pacing or another method to limit such
            bursts to the initial congestion window; see Section 7.2."
            <o:p></o:p></p>
          <p class="MsoNormal"
            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">This
            seems to preclude use of segmentation offload of sizes
            greater than IW. In datacenters we routinely send bursts
            that are higher without causing loss.
            <o:p></o:p></p>
        </blockquote>
        <p class="MsoNormal">Is that within data centres? or from data
          centres to Internet destinations? ... if the latter, how can
          the sender be sure this is not impacting other traffic?<br>
          <br>
          <o:p></o:p></p>
        <blockquote style="margin-top:5.0pt;margin-bottom:5.0pt">
          <p class="MsoNormal"
            style="mso-margin-top-alt:auto;mso-margin-bottom-alt:auto">The
            MUST here seems unnecessary. It also conflicts with the
            RECOMMENDED in an earlier sentence.<o:p></o:p></p>
        </blockquote>
        <p>I actually don't see this as conflicting. The recommendation
          in this section is to pace. The requirement is that sender
          limits burst, using some method, to the size of IW.<o:p></o:p></p>
        <p>Gorry<o:p></o:p></p>
        <p><o:p> </o:p></p>
      </div>
    </blockquote>
  </body>
</html>

--------------7F5A35BA621E9AFAB1111B71--


From nobody Fri Jul 10 02:09:54 2020
Return-Path: <Markus.Amend@telekom.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 1ECB83A0ED9; Fri, 10 Jul 2020 02:09:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.096
X-Spam-Level: 
X-Spam-Status: No, score=-2.096 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, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, 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=telekom.de
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 7NFZ1KC7LwVJ; Fri, 10 Jul 2020 02:09:46 -0700 (PDT)
Received: from mailout41.telekom.de (mailout41.telekom.de [194.25.225.151]) (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 5AD3B3A0E78; Fri, 10 Jul 2020 02:09:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telekom.de; i=@telekom.de; q=dns/txt; s=dtag1; t=1594372185; x=1625908185; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-transfer-encoding:mime-version; bh=WTP1FRSCjEf66HRZKGHgQhq/segIAjO9ahHzLWAtQBY=; b=F1DqP3dGI5ZxN3ma9ZeeATpsIiLGy/vlu+d+wZLhY7y61A9AiaNFKMhj +pxbA120oeHDrjthOUBXF6R2vOGZLBMVfy5c4HycHIS9wsgE6tCNN8IUI oweFe6dm6EM7UpP+PUfjQT/dTHWATORDQLiiFcFkwCIgor0If8/IdSc7/ LffRAmeLSNHob2SRKW8xMcZWrTCMiSpEQv3wjJo12gR3917weS2+PsPi4 l/9eEFEcdcNGSv36T8j5tYxXXrJKOjZ1WmzKfn4w5bLMp6dEXghQryUba LAWDAjEdDZnBMov2jL3PY7PKIfaLsCQ1c0OkTv0ZKlrfiIEYB6WapHzqk w==;
IronPort-SDR: w8UalDBKZp9xUUSoPL9aBrndD1z2EU6PBxwDVq9F690ggm8Ph5BzOcVUz2E2EtJbIgGtpN8Zat MgeOAzEpupzA==
Received: from qdec94.de.t-internal.com ([10.171.255.41]) by MAILOUT41.dmznet.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES128-GCM-SHA256; 10 Jul 2020 11:09:42 +0200
IronPort-SDR: qJ52WZUxHSbRlc495w9fGjw7YokRy/bK0oBp2Jb0m2PiZHuD3N4OPXltxUcmfp9TQyt568I3iE 2/3J5g4rOrUZobngCZoMFEZfixznQert8=
X-IronPort-AV: E=Sophos;i="5.75,335,1589234400"; d="scan'208";a="149545633"
X-MGA-submission: =?us-ascii?q?MDHfzLu8ZgHNjL6rvFv+GujZlqHIX0XG6DHT0I?= =?us-ascii?q?2jJJffs5nf4Ej6tGcH8OsPFnyuahlxVHgrLr3W+KwZ1vLUUzKZcb/Dcb?= =?us-ascii?q?8CeklLp7X07aImJmTPLoCGPWh5o7Hne4d8+hDlZY2Jv65c1nzU2wc8Fh?= =?us-ascii?q?dC7Cig2Y/kn9PFidWtGNy8Gw=3D=3D?=
Received: from he105712.emea1.cds.t-internal.com ([10.169.118.43]) by QDEC97.de.t-internal.com with ESMTP/TLS/ECDHE-RSA-AES128-SHA256; 10 Jul 2020 11:09:42 +0200
Received: from HE105716.EMEA1.cds.t-internal.com (10.169.118.52) by HE105712.emea1.cds.t-internal.com (10.169.118.43) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 10 Jul 2020 11:09:41 +0200
Received: from HE104164.emea1.cds.t-internal.com (10.171.40.35) by HE105716.EMEA1.cds.t-internal.com (10.169.118.52) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Fri, 10 Jul 2020 11:09:41 +0200
Received: from GER01-LEJ-obe.outbound.protection.outlook.de (51.5.80.19) by O365mail06.telekom.de (172.30.0.233) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Fri, 10 Jul 2020 11:09:38 +0200
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=Le5w0E+B7pz4WbDJd/Gw9cUZGXJ43I9+nZ/QKc8bhrMCXf/Jm5f6WrXQkDeEnIU+Fcj9vFjSlVXZZEk8FmdgrfCDO5i7XAQBVr6TCwb9hImyUsIn6pGLBh7B+q4Rp7Rg/OWTpdA6cO1DdbMNo3wx8xWaOTqf9SJsvOqJ6PCo3qUZFb6RUl501ji/V1HViaHmEYyPqle6RJ2nGyYxXwRiMh7m5VSorivyWijlCDqFyWMGzFCPVIo738TN15AE/QPl02x7MG4MG0D/XXms97GaTviXm4tDxdUIxA1EAhJIFTS3o+gob8G0errXbazxvky1E53F4Iv/oIteQAiq863Biw==
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=WTP1FRSCjEf66HRZKGHgQhq/segIAjO9ahHzLWAtQBY=; b=ldlyYs6YWfvAIt0qDSOd5ogt7FV/XF74Gnuurz/qTmfS2cIfoXrt0sApr7iyBsRWqilXc5tGDo/AJ6p1TBPSG3g8egjWMYDTHO8ctAzJm9sstz8buQ9V3GESB7rPU8HG7sY8h2UvSmz6sMc1XV7qHsY8lMquhXXmlzPLwOWcVkZQl9j574Tb5KCdjGV3vEKEsTLYyRsd+dLowBHPQGk9znL0ieMjiVppJwQfgOCjXTYG8ALeh03KPv7jwPSQNEAb2cudRg1N5wixyjKJZsD9CfE0s+K4UzKOKsRUZiffbiwoV9xMhSQXSecV5bR9nXg5zEiIlIvFO0j9wA7uHx78kw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=telekom.de; dmarc=pass action=none header.from=telekom.de; dkim=pass header.d=telekom.de; arc=none
Received: from LEJPR01MB0490.DEUPRD01.PROD.OUTLOOK.DE (2a01:4180:c012:a::11) by LEJPR01MB0091.DEUPRD01.PROD.OUTLOOK.DE (2a01:4180:c012:5::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3195.9; Fri, 10 Jul 2020 09:09:41 +0000
Received: from LEJPR01MB0490.DEUPRD01.PROD.OUTLOOK.DE ([fe80::d595:7a33:8cac:79b0]) by LEJPR01MB0490.DEUPRD01.PROD.OUTLOOK.DE ([fe80::d595:7a33:8cac:79b0%2]) with mapi id 15.20.3195.009; Fri, 10 Jul 2020 09:09:41 +0000
From: <Markus.Amend@telekom.de>
To: <quic@ietf.org>, <masque@ietf.org>
CC: <Dirk.von-Hugo@telekom.de>
Subject: FW: New Version Notification for draft-amend-iccrg-multipath-reordering-00.txt
Thread-Topic: New Version Notification for draft-amend-iccrg-multipath-reordering-00.txt
Thread-Index: AQHWVVJgfgEAaAUn9E6F2PpxMEuL2akAhrnQ
Date: Fri, 10 Jul 2020 09:09:41 +0000
Message-ID: <LEJPR01MB04904C5EF79B84AC8B04A28AFA650@LEJPR01MB0490.DEUPRD01.PROD.OUTLOOK.DE>
References: <159423152847.21640.733211169724485576@ietfa.amsl.com>
In-Reply-To: <159423152847.21640.733211169724485576@ietfa.amsl.com>
Accept-Language: de-DE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=telekom.de;
x-originating-ip: [164.19.3.230]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 87823f7c-9420-4aa9-0696-08d824b0fab2
x-ms-traffictypediagnostic: LEJPR01MB0091:
x-ms-exchange-transport-forked: True
x-microsoft-antispam-prvs: <LEJPR01MB00916F9A8A86A3CDD0BAB6A0FA650@LEJPR01MB0091.DEUPRD01.PROD.OUTLOOK.DE>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: EPCR4dp9I4qOsJ8gRIbx6DQSMIS0Zq/Uj9tOkH/g4iV3f2aL746/BfFGMUYIz8Nuhiosf/X1v+xq7Sck2K6aIzvlkWY0XTxiKEDA7d8iyzu22ScgCd1l1ke6JL7nPlSYWVWoOywH2mkljPd27E/deN7wKaBbT2RDb+DGZrFAnuQnO9Wpj9Pkt3oxCnExZ3xTdBtKVVpZXx4BBWvvVARnCsloCDNkebjZbnpaHnpAztY1Wz0kWgZfA4SYHYhlfx9sUeCe2JY2oyyt9PV18FUWVu10NNMEEm7RWDKNOVwopgEIqRImScWly5R6oA7gT0tclmb/IThDPHkJ5NRDVMatxC2QokFvkx0EFRT0gXk61tc=
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:LEJPR01MB0490.DEUPRD01.PROD.OUTLOOK.DE; PTR:; CAT:NONE;  SFTY:; SFS:(366004)(136003)(346002)(39860400002)(396003)(376002)(55016002)(966005)(316002)(186003)(8676002)(9686003)(66574015)(2906002)(26005)(33656002)(15650500001)(110136005)(450100002)(8936002)(478600001)(53546011)(5660300002)(76116006)(83380400001)(4326008)(86362001)(71200400001)(66946007)(66446008)(7696005)(66476007)(64756008)(66556008)(107886003); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: oSuVeg07UDWSVObyFXUl4pjbOtPs2kBpCKw+uzLtcrDCEyn3M0zt08pD6XN7V7v4ecoDJRu7qsfz07x2z48BWZzaQOd3Gugq92zWNXbrIOESCQdl9kEHfG4Vq2u94FMsRxKe/f1RFsOK7ozGtcBqNk9Hv69Fn/gsvv5yLD56zAYonwe/CMRn7a2S8H3guvHlLYK8SyM7P8Ai3PeR/joqv76r/U2Ln+8zj6HeMZqkUjRNdElO/iKCHuYUSfdkh7CbxdbQrxZ7+lMRffhYs9wBehtDG0qfeOmlGMWABauY9oIlOz/IL2ns3c0fQvPfqXbC2h2R7OdbS02wXy+zSZLFc8Zvo288YnumySiyjLyPItdPr8R5vk+51rUqXTLlHCxfCpMK6A78xbrnJvhsPKEM080+lXmM2+ZhTBRTyMT+MQoDUIhUo1pC+4g3GAsT90jbCYlJ8P8xb30nW/sPzdTNLiwzMfJCNqrwFc78/MR6fy8=
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: LEJPR01MB0490.DEUPRD01.PROD.OUTLOOK.DE
X-MS-Exchange-CrossTenant-Network-Message-Id: 87823f7c-9420-4aa9-0696-08d824b0fab2
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jul 2020 09:09:41.1290 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: bde4dffc-4b60-4cf6-8b04-a5eeb25f5c4f
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: IBTAy7zyjsgPGXusvkPygn3SPVPtaORuh7QFRdxk+SZp7HoCI/LJ/Mv5YV/GH5RoQRUulYf+JV4J8Ye6NEO/hg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LEJPR01MB0091
X-TM-SNTS-SMTP: 71CE51BDD92B1C262DF0AA6F96E576C541CEE3DD477E9C387352393C679806362000:8
X-OriginatorOrg: telekom.de
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/py6lSmog8Y1sZNKYPQI8x7Epnes>
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, 10 Jul 2020 09:09:48 -0000

RGVhciBhbGwsDQoNCkkgd2FudCB0byBhbm5vdW5jZSB0aGUgYXZhaWxhYmlsaXR5IG9mIGEgbmV3
IGRyYWZ0IGFkZHJlc3NpbmcgdGhlIGNoYWxsZW5nZSBvZiBwYWNrZXQgcmVvcmRlcmluZyBkdWUg
dG8gbXVsdGlwYXRoLiBUaGlzIGRyYWZ0IGluY2x1ZGVzIGNvdW50ZXJtZWFzdXJlcyBsaWtlIHJl
c2VxdWVuY2luZywgcmVjb3ZlcnkgYW5kIHJldHJhbnNtaXNzaW9uIHRlY2huaXF1ZXMsIHN0aWxs
IG9uIGhlYWRsaW5lIGxldmVsLiBUaGUgZHJhZnQgaXMgcGxhY2VkIGF0IElDQ1JHLg0KDQpNdWx0
aXBhdGggUmVvcmRlcmluZyBpcyBhZHJlc3NlZCB0byBiZSBhIGNoYWxsZW5nZSBpbiBodHRwczov
L3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtYm9uYXZlbnR1cmUtcXVpYy1hdHNzcy1vdmVydmll
dy0wMCBhbmQgY2FuIGJlIHZlcmlmaWVkIHdpdGggdGhlIHBxdWljIGltcGxlbWVudGF0aW9uICho
dHRwczovL3BxdWljLm9yZy8pLCBpbiBwYXJ0aWN1bGFyIHdoZW4gdGhlIG11bHRpcGF0aCBhbmQg
ZGF0YWdyYW0gcGx1Z2luIHdpbGwgYmUgY29tYmluZWQuDQoNClBsZWFzZSBmZWVsIGZyZWUgdG8g
Z2l2ZSBtZSBmZWVkYmFjayBhbmQvb3IgY29udHJpYnV0ZS4gVGhlIGRyYWZ0IGlzIG1haW50YWlu
ZWQgYXQgaHR0cHM6Ly9naXRodWIuY29tL21hcmt1c2EvZHJhZnQtcmVvcmRlcmluZy4NCg0KQnIN
Cg0KTWFya3VzDQoNCj4gLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCj4gRnJvbTogaW50ZXJu
ZXQtZHJhZnRzQGlldGYub3JnIDxpbnRlcm5ldC1kcmFmdHNAaWV0Zi5vcmc+DQo+IFNlbnQ6IE1p
dHR3b2NoLCA4LiBKdWxpIDIwMjAgMjA6MDUNCj4gVG86IHZvbiBIdWdvLCBEaXJrIDxEaXJrLnZv
bi1IdWdvQHRlbGVrb20uZGU+OyB2b24gSHVnbywgRGlyayA8RGlyay52b24tDQo+IEh1Z29AdGVs
ZWtvbS5kZT47IEFtZW5kLCBNYXJrdXMgPE1hcmt1cy5BbWVuZEB0ZWxla29tLmRlPjsgQW1lbmQs
DQo+IE1hcmt1cyA8TWFya3VzLkFtZW5kQHRlbGVrb20uZGU+DQo+IFN1YmplY3Q6IE5ldyBWZXJz
aW9uIE5vdGlmaWNhdGlvbiBmb3IgZHJhZnQtYW1lbmQtaWNjcmctbXVsdGlwYXRoLXJlb3JkZXJp
bmctDQo+IDAwLnR4dA0KPiANCj4gDQo+IEEgbmV3IHZlcnNpb24gb2YgSS1ELCBkcmFmdC1hbWVu
ZC1pY2NyZy1tdWx0aXBhdGgtcmVvcmRlcmluZy0wMC50eHQNCj4gaGFzIGJlZW4gc3VjY2Vzc2Z1
bGx5IHN1Ym1pdHRlZCBieSBNYXJrdXMgQW1lbmQgYW5kIHBvc3RlZCB0byB0aGUNCj4gSUVURiBy
ZXBvc2l0b3J5Lg0KPiANCj4gTmFtZToJCWRyYWZ0LWFtZW5kLWljY3JnLW11bHRpcGF0aC1yZW9y
ZGVyaW5nDQo+IFJldmlzaW9uOgkwMA0KPiBUaXRsZToJCU11bHRpcGF0aCBzZXF1ZW5jZSBtYWlu
dGVuYW5jZQ0KPiBEb2N1bWVudCBkYXRlOgkyMDIwLTA3LTA3DQo+IEdyb3VwOgkJSW5kaXZpZHVh
bCBTdWJtaXNzaW9uDQo+IFBhZ2VzOgkJMTANCj4gVVJMOiAgICAgICAgICAgIGh0dHBzOi8vd3d3
LmlldGYub3JnL2ludGVybmV0LWRyYWZ0cy9kcmFmdC1hbWVuZC1pY2NyZy1tdWx0aXBhdGgtDQo+
IHJlb3JkZXJpbmctMDAudHh0DQo+IFN0YXR1czogICAgICAgICBodHRwczovL2RhdGF0cmFja2Vy
LmlldGYub3JnL2RvYy9kcmFmdC1hbWVuZC1pY2NyZy1tdWx0aXBhdGgtDQo+IHJlb3JkZXJpbmcv
DQo+IEh0bWxpemVkOiAgICAgICBodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtYW1l
bmQtaWNjcmctbXVsdGlwYXRoLXJlb3JkZXJpbmctDQo+IDAwDQo+IEh0bWxpemVkOiAgICAgICBo
dHRwczovL2RhdGF0cmFja2VyLmlldGYub3JnL2RvYy9odG1sL2RyYWZ0LWFtZW5kLWljY3JnLW11
bHRpcGF0aC0NCj4gcmVvcmRlcmluZw0KPiANCj4gDQo+IEFic3RyYWN0Og0KPiAgICBUaGlzIGRv
Y3VtZW50IGRpc2N1c3NlcyB0aGUgaXNzdWUgb2YgcGFja2V0IHJlLW9yZGVyaW5nIHdoaWNoIG9j
Y3Vycw0KPiAgICBhcyBhIHNwZWNpZmljIHByb2JsZW0gaW4gbXVsdGktcGF0aCBjb25uZWN0aW9u
cyB3aXRob3V0IHJlbGlhYmxlDQo+ICAgIHRyYW5zcG9ydCBwcm90b2NvbHMgc3VjaCBhcyBUQ1Au
ICBUaGUgdG9waWMgaXMgcmVsZXZhbnQgZm9yIGRldmljZXMNCj4gICAgY29ubmVjdGVkIHZpYSBt
dWx0aXBsZSBhY2Nlc3NlcyB0ZWNobm9sb2dpZXMgdG93YXJkcyB0aGUgbmV0d29yayBhcw0KPiAg
ICBpcyBmb3Jlc2VlbiBlLmcuIHdpdGhpbiBBY2Nlc3MgVHJhZmZpYyBTZWxlY3Rpb24sIFN3aXRj
aGluZywgYW5kDQo+ICAgIFNwbGl0dGluZyAoQVRTU1MpIHNlcnZpY2Ugb2YgM3JkIEdlbmVyYXRp
b24gUGFydG5lcnNoaXAgUHJvamVjdA0KPiAgICAoM0dQUCkgZW5hYmxpbmcgZml4ZWQgbW9iaWxl
IGNvbnZlcmdlZCAoRk1DKSBzY2VuYXJpby4NCj4gDQo+IA0KPiANCj4gDQo+IFBsZWFzZSBub3Rl
IHRoYXQgaXQgbWF5IHRha2UgYSBjb3VwbGUgb2YgbWludXRlcyBmcm9tIHRoZSB0aW1lIG9mIHN1
Ym1pc3Npb24NCj4gdW50aWwgdGhlIGh0bWxpemVkIHZlcnNpb24gYW5kIGRpZmYgYXJlIGF2YWls
YWJsZSBhdCB0b29scy5pZXRmLm9yZy4NCj4gDQo+IFRoZSBJRVRGIFNlY3JldGFyaWF0DQo+IA0K
DQo=


From nobody Fri Jul 10 10:06:25 2020
Return-Path: <pravb@microsoft.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1287E3A00C3 for <quic@ietfa.amsl.com>; Fri, 10 Jul 2020 10:06:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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, DKIM_VALID_EF=-0.1, HTML_MESSAGE=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=microsoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id bWsSb0MynBQY for <quic@ietfa.amsl.com>; Fri, 10 Jul 2020 10:06:21 -0700 (PDT)
Received: from NAM06-DM3-obe.outbound.protection.outlook.com (mail-eopbgr640092.outbound.protection.outlook.com [40.107.64.92]) (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 E8DC83A00B0 for <quic@ietf.org>; Fri, 10 Jul 2020 10:06:20 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=HFScLOtiXLXLDyRg6i/ohYCXLL8bv0KNQMPts+APDlLa5bbrtvQyhecpLOcHhaaQoEGy4qTa5Lg7LOtRTtikF5vDFEcJOLudFHii79en5bAHmZnGibZl89/BtYTWAA3X20I+MWSKoooZ5k2m7Mmm/pGcMe60VcIW4XlAt4NjRx1HGAHefX+jiKdYgRTS/Impu1L0soq86/SaEpkdmgN5YLkkli4ysGtKnQGJe4ObJMCv3f2XiAOjbok/QldUFfMH5le/BZ7RfvK0BS+UfR7OjoVFEVt3gX0vCai1fVd1jbgCcD0+857i7BvP4J9SRbGfS9UaP8yq/iTSpJb2V/AEjA==
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=1joTkBixH1taUzna1L+YnbL54SPPrlZzHFOZmY7b/58=; b=AYnQ7ticpDwHxcUedvoQB+9y4Z8kIfjSI8aVAUQtOahtFv2cPI/TaeLIOuoELW+ZghNx15aYc4KIzYPgjlL6QBZHxGdnpXAJ1cspj4qV1pm9gPTK0n1hcZqII+1qrXZ4xXttPJup++q536fRA3hxpIJO/gd5o/2uevD6PbWNGhGHRKT1Wu2Btz2MdYOqD09M4ZPIX0Hu2094nVPpuzYHp+cFgwO01QmSttsGeTtgXhleJPFEQgHsHWX0G/KtKJc51xnBHlSD8TwddTekZONWq31CT3SD7cI+2en3y32MbOomwXynYxCEtj0mdHZSvttfLch7p08sH/vOrA+jkdBiBw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=1joTkBixH1taUzna1L+YnbL54SPPrlZzHFOZmY7b/58=; b=f4FpPn66JezqcmXsnk6tTZoAcLbM792DyDXy2j8hE5Z3qA5FztAaOzzCro5ViSLtg1RMXDkqiUBLZEriivqRc7MB7wPIkJ0Q+hXdf+yQCDEM8HNV4RsLukJlm8u7iA2SUsfSZQtWUqQ72LD+ctu4xbjPt5U22YDyGz3MeDRKhhw=
Received: from CH2PR00MB0726.namprd00.prod.outlook.com (2603:10b6:610:ad::12) by CH2PR00MB0727.namprd00.prod.outlook.com (2603:10b6:610:ad::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3211.0; Fri, 10 Jul 2020 17:06:19 +0000
Received: from CH2PR00MB0726.namprd00.prod.outlook.com ([fe80::7562:9640:814e:c7f1]) by CH2PR00MB0726.namprd00.prod.outlook.com ([fe80::7562:9640:814e:c7f1%8]) with mapi id 15.20.3213.000; Fri, 10 Jul 2020 17:06:19 +0000
From: Praveen Balasubramanian <pravb@microsoft.com>
To: Neal Cardwell <ncardwell@google.com>, IETF QUIC WG <quic@ietf.org>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>
CC: Yuchung Cheng <ycheng@google.com>
Subject: RE: FW: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
Thread-Topic: FW: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
Thread-Index: AdZVbt/Rv8RxmVSLQP+4+5gZJ/6HOgAXZSqAAA+FIqAAAGCqEAABZq4AAAAkqAAAAOk6AAAs5iOAAAStJtA=
Date: Fri, 10 Jul 2020 17:06:19 +0000
Message-ID: <CH2PR00MB0726F4FE6F8727D01ADB9543B6650@CH2PR00MB0726.namprd00.prod.outlook.com>
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <53187d65-f7b9-b99a-f68b-b267303ab399@erg.abdn.ac.uk> <CH2PR00MB0726D18611EC030BF548CA0DB6640@CH2PR00MB0726.namprd00.prod.outlook.com> <CH2PR00MB072651FB3CFE2942280ABD84B6640@CH2PR00MB0726.namprd00.prod.outlook.com> <CAK6E8=cat86k9zROKquK20ZdOZi20gQknA+-4aN2qAs3wQsNdw@mail.gmail.com> <CAK6E8=fLF51_iMZtXGFdQg1-3cV2iCQr9222Ufzq=do7119kSA@mail.gmail.com> <CH2PR00MB0726376C911F29BEFF3BD1F4B6640@CH2PR00MB0726.namprd00.prod.outlook.com> <CADVnQymw1KFFYRqpOjrfnc-uGFaGdyA+z4KaHmss2qQ=FvvAyg@mail.gmail.com>
In-Reply-To: <CADVnQymw1KFFYRqpOjrfnc-uGFaGdyA+z4KaHmss2qQ=FvvAyg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=true; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2020-07-10T17:06:17Z;  MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=20d0909f-04cd-4699-b40a-81330b157b51; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0
authentication-results: google.com; dkim=none (message not signed) header.d=none;google.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [2001:4898:80e8:3:95d5:3f73:f682:d302]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 682eea28-171c-4faf-4d77-08d824f3906f
x-ms-traffictypediagnostic: CH2PR00MB0727:
x-microsoft-antispam-prvs: <CH2PR00MB072760061DCA39DD0E81D2B0B6650@CH2PR00MB0727.namprd00.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: BshZ2zSxILX9JbERODVqYzd9FyyR7OOtXGAvmVW43tT0QBCR4P0qqSYW2DAsJsoPV2yBLUUPbxAA8L1PETIark7gVZafFrah5zBBdXFzsu68HmSgT9MCZLvmVzA79Xlijxj9ZXWQUy9sGxOVCdC1qTey6hlixb/Yxss3KjakBkIb2tXOfP69F/27lPM/BMkY/mOcDLj57lHEptQRAZ0ALSEP2GwEKEWHWBwy/JZATEmHGmOYsxCKQ6+4GngWcr599FArZ9S4U/eGguSf/uaRey/hbRmNn74Jm6AQxdv77A4JqvVOn5OPbDx2XIBZYGyWsHrpcJwS2L2c0XBqUEpIjWa81zaQP8MBknxAIu77Mm2vZ5KNxCGlJdoUYcxWeEqcjgOdcp0YqH2VzbErqMuQCQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:CH2PR00MB0726.namprd00.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(376002)(366004)(136003)(396003)(39860400002)(346002)(10290500003)(66574015)(7696005)(316002)(71200400001)(6506007)(186003)(478600001)(53546011)(8936002)(166002)(83380400001)(55016002)(110136005)(8676002)(2906002)(5660300002)(82950400001)(82960400001)(8990500004)(52536014)(86362001)(9686003)(33656002)(64756008)(66446008)(4326008)(66476007)(66556008)(76116006)(66946007); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: H/SVv0m0hsFoDmcy397PYeXNlac+Yu8VGjpBCjypNHPLGQ/SYu9F84EYin7/AEqJfaG8awXzKVrYM1Xd8g/qU/hA+fVOtMNnJXK+h668sfw/7bBS3vs5matm9FCqfG0cMgje9nqTOXx7TPyceje+DS6a4p2WL8n+gpNfrqBT1pyCfzNGhPA9yLA4K+F9czEEpsSQ5Nm5rrUbw3CaApEfgJetfqKWbA2CP5ChszwG/CkC4mx3pP5TlapQ19exRLQdgAfaKE3ZJ1n7YdzPjTER15f2Hx2wepH9PNDwjUnkKaeRAdrqX859my3UH6C5s+wsoGy336v9Pk0MK4BGzoRePdyXBFBUrKWb+YhGvofjKGYyeMmsHyvz9tCi5tCFVsBPtO6qwLO5pKslNcl6E7zG14oGdJ71mZaaRVLxwA6UZdEyT+nUjV8PAlz2oEfmtvbKVA11JN1dto0PHvhsCicFB4i0yUUFgBGjx0Hd1/TTncI/EvhYi1PWGeceRjdvhVaFxFAnFuAaPnwOAnkKC7dyUsyTXle68esEr2LWL8IlXdI=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CH2PR00MB0726F4FE6F8727D01ADB9543B6650CH2PR00MB0726namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CH2PR00MB0726.namprd00.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 682eea28-171c-4faf-4d77-08d824f3906f
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jul 2020 17:06:19.1014 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: dc5AH5npDyvOBFmv6UYqUyPXxTkO//8EwUMcTBNVHkF1SJ+XBRlfDdtpcClIAkkg8Unxjw1d1oOFzLnm9n91klcTaspzzrTDxkcbGFA9Cls=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR00MB0727
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/c8ivP9kWXXYWqbhwVL3Al5XlPYQ>
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, 10 Jul 2020 17:06:23 -0000

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

VGhhbmtzIE5lYWwgYW5kIFl1Y2h1bmcuICtxdWljQGlldGYgYW5kIEdvcnJ5DQoNCkZyb206IE5l
YWwgQ2FyZHdlbGwgPG5jYXJkd2VsbEBnb29nbGUuY29tPg0KU2VudDogRnJpZGF5LCBKdWx5IDEw
LCAyMDIwIDc6NTEgQU0NClRvOiBQcmF2ZWVuIEJhbGFzdWJyYW1hbmlhbiA8cHJhdmJAbWljcm9z
b2Z0LmNvbT4NCkNjOiBZdWNodW5nIENoZW5nIDx5Y2hlbmdAZ29vZ2xlLmNvbT4NClN1YmplY3Q6
IFJlOiBGVzogW0VYVEVSTkFMXSBSZTogV0dMQyByZXZpZXcgb2YgZHJhZnQtaWV0Zi1xdWljLXJl
Y292ZXJ5LTI5DQoNClllcywgYSA2NGsgVFNPIHF1YWxpZnkgYXMgYSBidXJzdCBoaWdoZXIgdGhh
biAxMCBwYWNrZXRzLg0KDQpJIGFncmVlIHdpdGggUHJhdmVlbidzIHJlbWFyayB0aGF0ICJ0aGUg
TVVTVCByZWdhcmRpbmcgYnVyc3Qgc2l6ZSBpcyB3YXkgdG9vIHJlc3RyaWN0aXZlIi4NCg0KSSdk
IHN1Z2dlc3Qgc29tZXRoaW5nIGxpa2U6DQoNCg0KICAgSW1wbGVtZW50YXRpb25zIE1VU1QgZWl0
aGVyIHVzZSBwYWNpbmcgb3IgYW5vdGhlciBtZXRob2QgdG8gbGltaXQgc3VjaCBidXJzdHMuDQoN
CiAgIEl0IGlzIFJFQ09NTUVOREVEIHRoYXQgdHJhZmZpYyBvdmVyIHRoZSBwdWJsaWMgSW50ZXJu
ZXQgbGltaXQgYnVyc3RzIHRvIHRoZSBpbml0aWFsDQoNCiAgIGNvbmdlc3Rpb24gd2luZG93OyBz
ZWUgU2VjdGlvbiA3LjI8aHR0cHM6Ly9uYW0wNi5zYWZlbGlua3MucHJvdGVjdGlvbi5vdXRsb29r
LmNvbS8/dXJsPWh0dHBzJTNBJTJGJTJGdG9vbHMuaWV0Zi5vcmclMkZodG1sJTJGZHJhZnQtaWV0
Zi1xdWljLXJlY292ZXJ5LTI5JTIzc2VjdGlvbi03LjImZGF0YT0wMiU3QzAxJTdDcHJhdmIlNDBt
aWNyb3NvZnQuY29tJTdDOWRmM2U1ZjRmMGNhNGU1ODZmMDkwOGQ4MjRlMGEzYWQlN0M3MmY5ODhi
Zjg2ZjE0MWFmOTFhYjJkN2NkMDExZGI0NyU3QzElN0MwJTdDNjM3Mjk5ODk0NTI2NjU3OTA2JnNk
YXRhPXplJTJGN1NwS1VicmRnd0k2bSUyQlM2dUVHU0JnYzJOYXBWdFBuOXZrT1lGalZzJTNEJnJl
c2VydmVkPTA+Lg0KDQoNClRoZSBjdXJyZW50IExpbnV4IFRTTyBzaXppbmcgYWxnb3JpdGhtIHdv
dWxkIGJlIGNvbXBhdGlibGUgd2l0aCBzdWNoIGEgcmVjb21tZW5kYXRpb24gdXAgdG8gcmF0ZXMg
b2YgMTAgKiAxNTAwICogOCAvIC4wMDEgLyAxMF42ID0gMTIwTWJwcy4NCg0KbmVhbA0KDQpPbiBU
aHUsIEp1bCA5LCAyMDIwIGF0IDE6MjYgUE0gUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gPHByYXZi
QG1pY3Jvc29mdC5jb208bWFpbHRvOnByYXZiQG1pY3Jvc29mdC5jb20+PiB3cm90ZToNClllcyBi
dXQgVFNPIHRvIE5JQ3MgdGhhdCBkbyBpdCBpbiBoYXJkd2FyZSBlZmZlY3RpdmVseSBtZWFucyBh
IGJ1cnN0IGJlY2F1c2UgQUZBSUsgaGFyZHdhcmUgZG9lc27igJl0IHBhY2UgdGhvc2Ugb3V0LiBT
byB3b3VsZG7igJl0IDY0ayBUU08gcXVhbGlmeSBhcyBhIGJ1cnN0IGhpZ2hlciB0aGFuIDEwIHBh
Y2tldHMuIEkgYWdyZWUgYSBTSE9VTEQgaXMgbXVjaCBiZXR0ZXIuDQoNCkZyb206IFl1Y2h1bmcg
Q2hlbmcgPHljaGVuZ0Bnb29nbGUuY29tPG1haWx0bzp5Y2hlbmdAZ29vZ2xlLmNvbT4+DQpTZW50
OiBUaHVyc2RheSwgSnVseSA5LCAyMDIwIDk6NTkgQU0NClRvOiBQcmF2ZWVuIEJhbGFzdWJyYW1h
bmlhbiA8cHJhdmJAbWljcm9zb2Z0LmNvbTxtYWlsdG86cHJhdmJAbWljcm9zb2Z0LmNvbT4+DQpD
YzogTmVhbCBDYXJkd2VsbCA8bmNhcmR3ZWxsQGdvb2dsZS5jb208bWFpbHRvOm5jYXJkd2VsbEBn
b29nbGUuY29tPj4NClN1YmplY3Q6IFJlOiBGVzogW0VYVEVSTkFMXSBSZTogV0dMQyByZXZpZXcg
b2YgZHJhZnQtaWV0Zi1xdWljLXJlY292ZXJ5LTI5DQoNCm9oIEkgcmVhZCB0aGUgc2VudGVuY2Ug
dG9vIGZhc3QuIEkgcmVhZCBpdCBhcyAidXNlIHBhY2luZyBvciBhbm90aGVyIG1ldGhvZCAodGhh
dCBib3RoKSB0byBsaW1pdCBidXJzdHMgdG8gdGhlIGluaXRpYWwgd2luZG93Ii4NCg0KSXQgc2Vl
bXMgdGhlIGRyYWZ0IGlzIHNheWluZywgd2l0aG91dCBwYWNpbmcsIHRoZSBidXJzdCBzaG91bGQg
YmUgY2FwcGVkLiBJIHRoaW5rIHRoYXQncyBmcm9tIHRoZSBvbGQgQlNEICJtYXhfYnVyc3QiIGNv
bmZpZyB0byAzID09IG9sZF9JVy4gRm9yIHRoYXQgSSdkIHNheSBJVzEwIHNldHRpbmcgaXMgcmVh
c29uYWJsZS4gQWx0aG91Z2ggTVVTVCBpcyB0b28gc3Ryb25nLiBJIGFncmVlIFNIT1VMRCBpcyBt
b3JlIGFwcHJvcHJpYXRlDQoNCk9uIFRodSwgSnVsIDksIDIwMjAgYXQgOTo1NCBBTSBZdWNodW5n
IENoZW5nIDx5Y2hlbmdAZ29vZ2xlLmNvbTxtYWlsdG86eWNoZW5nQGdvb2dsZS5jb20+PiB3cm90
ZToNCkxpbnV4IHNpemVzIFRTTyAodXB0IHRvIDY0S0IpIGJhc2VkIG9uIHRoZSBzb2NrZXQgcGFj
aW5nIHJhdGUuID4uNUcgcmVhY2hlcyA2NEtCLiB+NjRNYnBzIHByb2R1Y2VzIDE2S0IgPiBJVzEw
LCByZWdhcmRsZXNzIG9mIHRoZSBkZXN0aW5hdGlvbiAoZS5nLiBEQyBvciBub3QpLg0KDQpUaGUg
YXJ0aWZpY2lhbCBJVzEwIFRTTyBjYXAgbWFrZXMgbm8gc2Vuc2UgSU1PIGluIHRoZSBkcmFmdC4g
SSdkIGNoYWxsZW5nZSB0aGUgYXV0aG9ycyB0byBqdXN0aWZ5IHdpdGggZGF0YS4gSWYgYW55dGhp
bmcgdGhlIFRTTyBuZWVkcyB0byBiZSBldmVuIGJpZ2dlciB0aGFuIDY0S0Igb24gaGlnaGVyIHNw
ZWVkIE5JQ3MuDQoNCk9uIFRodSwgSnVsIDksIDIwMjAgYXQgOToxNiBBTSBQcmF2ZWVuIEJhbGFz
dWJyYW1hbmlhbiA8cHJhdmJAbWljcm9zb2Z0LmNvbTxtYWlsdG86cHJhdmJAbWljcm9zb2Z0LmNv
bT4+IHdyb3RlOg0KRG9lcyBMaW51eCBuZXZlciBzZW5kIGEgVFNPIG9mIHNpemUgbW9yZSB0aGFu
IDEwIHBhY2tldHMgdW5kZXIgYW55IGNpcmN1bXN0YW5jZXM/DQoNClRoYW5rcw0KDQpGcm9tOiBQ
cmF2ZWVuIEJhbGFzdWJyYW1hbmlhbg0KU2VudDogVGh1cnNkYXksIEp1bHkgOSwgMjAyMCA5OjEy
IEFNDQpUbzogR29ycnkgRmFpcmh1cnN0IDxnb3JyeUBlcmcuYWJkbi5hYy51azxtYWlsdG86Z29y
cnlAZXJnLmFiZG4uYWMudWs+PjsgSUVURiBRVUlDIFdHIDxxdWljQGlldGYub3JnPG1haWx0bzpx
dWljQGlldGYub3JnPj4NClN1YmplY3Q6IFJFOiBbRVhURVJOQUxdIFJlOiBXR0xDIHJldmlldyBv
ZiBkcmFmdC1pZXRmLXF1aWMtcmVjb3ZlcnktMjkNCg0KV2l0aGluIGRhdGEgY2VudGVyIG1haW5s
eS4gVG8gaGl0IDQwIEdicHMgbGluZSByYXRlIHlvdSBlZmZlY3RpdmVseSBoYXZlIHRvIGJhdGNo
IGFzIG11Y2ggYXMgeW91IGNhbiB0byBtaW5pbWl6ZSB0aGUgQ1BVIHByb2Nlc3NpbmcgY29zdHMu
IFRoZSBidXJzdCBzaXplIHRvZGF5IGlzIGNhcHBlZCB0byA2NGsgaW4gbW9zdCBjYXNlcyBmb3Ig
VENQLiBOb3cgdGhhdCB3ZSBoYXZlIHNlZ21lbnRhdGlvbiBvZmZsb2FkIGZvciBVRFAgdGhlIHNh
bWUgc2hvdWxkIGFwcGx5LiBFdmVuIGZvciBJbnRlcm5ldCBmYWNpbmcgdHJhZmZpYywgdGhlIGJ1
cnN0cyBwcmltYXJpbHkgaW1wYWN0IHRoZSBmaXJzdCBob3Agd2l0aGluIHRoZSBkYXRhY2VudGVy
IGJlY2F1c2Ugc3Vic2VxdWVudGx5IHlvdSBnZXQgc3RhdGlzdGljYWwgbXVsdGlwbGV4aW5nIGZy
b20gVG9SIHN3aXRjaCBoYW5kbGluZyB0cmFmZmljIGZvcndhcmRpbmcgZm9yIG1hbnkgZmxvd3Mg
YW5kIHBvcnRzLg0KDQpPayB1bmRlcnN0b29kIGFib3V0IHRoZXJlIGJlaW5nIG5vIGNvbmZsaWN0
LiBCdXQgSSBzdGlsbCBjb250ZW5kIHRoYXQgdGhlIE1VU1QgcmVnYXJkaW5nIGJ1cnN0IHNpemUg
aXMgd2F5IHRvbyByZXN0cmljdGl2ZS4gV2Ugc2hvdWxkIGFsbG93IGZvciBleHBlcmltZW50YXRp
b24gaGVyZS4gT3IgcHJlc2VudCBkYXRhIHRoYXQgdGhpcyBpcyB1bml2ZXJzYWxseSBiYWQgb24g
YWxsIG5ldHdvcmtzLiBDdXJyZW50IHByb2R1Y3Rpb24gdXNlIG9mIFRDUCBzaG93cyB0aGVyZSBp
cyBubyBtYWpvciBwcm9ibGVtcyB3aXRoIGJ1cnN0aW5nIGhpZ2hlci4gSW4gZmFjdCBmb3IgbG93
IGxhdGVuY3kgc2FtZSByYWNrIHNjZW5hcmlvcyB0aGlzIHdpbGwgYm9vc3QgcmVjZWl2ZSBwZXJm
b3JtYW5jZSBhcyB3ZWxsIGR1ZSB0byBiZXR0ZXIgb3Bwb3J0dW5pdHkgZm9yIExSTyBldGMuDQoN
CkZyb206IEdvcnJ5IEZhaXJodXJzdCA8Z29ycnlAZXJnLmFiZG4uYWMudWs8bWFpbHRvOmdvcnJ5
QGVyZy5hYmRuLmFjLnVrPj4NClNlbnQ6IFRodXJzZGF5LCBKdWx5IDksIDIwMjAgMTozOSBBTQ0K
VG86IFByYXZlZW4gQmFsYXN1YnJhbWFuaWFuIDxwcmF2YkBtaWNyb3NvZnQuY29tPG1haWx0bzpw
cmF2YkBtaWNyb3NvZnQuY29tPj47IElFVEYgUVVJQyBXRyA8cXVpY0BpZXRmLm9yZzxtYWlsdG86
cXVpY0BpZXRmLm9yZz4+DQpTdWJqZWN0OiBbRVhURVJOQUxdIFJlOiBXR0xDIHJldmlldyBvZiBk
cmFmdC1pZXRmLXF1aWMtcmVjb3ZlcnktMjkNCg0KDQpIaSBQcmF2ZWVuLA0KT24gMDgvMDcvMjAy
MCAyMjoyOSwgUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gd3JvdGU6DQpTZWN0aW9uIDcuOQ0KIklt
cGxlbWVudGF0aW9ucyBNVVNUIGVpdGhlciB1c2UgcGFjaW5nIG9yIGFub3RoZXIgbWV0aG9kIHRv
IGxpbWl0IHN1Y2ggYnVyc3RzIHRvIHRoZSBpbml0aWFsIGNvbmdlc3Rpb24gd2luZG93OyBzZWUg
U2VjdGlvbiA3LjIuIg0KVGhpcyBzZWVtcyB0byBwcmVjbHVkZSB1c2Ugb2Ygc2VnbWVudGF0aW9u
IG9mZmxvYWQgb2Ygc2l6ZXMgZ3JlYXRlciB0aGFuIElXLiBJbiBkYXRhY2VudGVycyB3ZSByb3V0
aW5lbHkgc2VuZCBidXJzdHMgdGhhdCBhcmUgaGlnaGVyIHdpdGhvdXQgY2F1c2luZyBsb3NzLg0K
SXMgdGhhdCB3aXRoaW4gZGF0YSBjZW50cmVzPyBvciBmcm9tIGRhdGEgY2VudHJlcyB0byBJbnRl
cm5ldCBkZXN0aW5hdGlvbnM/IC4uLiBpZiB0aGUgbGF0dGVyLCBob3cgY2FuIHRoZSBzZW5kZXIg
YmUgc3VyZSB0aGlzIGlzIG5vdCBpbXBhY3Rpbmcgb3RoZXIgdHJhZmZpYz8NClRoZSBNVVNUIGhl
cmUgc2VlbXMgdW5uZWNlc3NhcnkuIEl0IGFsc28gY29uZmxpY3RzIHdpdGggdGhlIFJFQ09NTUVO
REVEIGluIGFuIGVhcmxpZXIgc2VudGVuY2UuDQoNCkkgYWN0dWFsbHkgZG9uJ3Qgc2VlIHRoaXMg
YXMgY29uZmxpY3RpbmcuIFRoZSByZWNvbW1lbmRhdGlvbiBpbiB0aGlzIHNlY3Rpb24gaXMgdG8g
cGFjZS4gVGhlIHJlcXVpcmVtZW50IGlzIHRoYXQgc2VuZGVyIGxpbWl0cyBidXJzdCwgdXNpbmcg
c29tZSBtZXRob2QsIHRvIHRoZSBzaXplIG9mIElXLg0KDQpHb3JyeQ0KDQoNCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDEx
IDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCWZvbnQtc2l6ZTox
MS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBzcGFu
Lk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0
ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnByZQ0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7
DQoJbXNvLXN0eWxlLWxpbms6IkhUTUwgUHJlZm9ybWF0dGVkIENoYXIiOw0KCW1hcmdpbjowaW47
DQoJZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30NCnNwYW4u
SFRNTFByZWZvcm1hdHRlZENoYXINCgl7bXNvLXN0eWxlLW5hbWU6IkhUTUwgUHJlZm9ybWF0dGVk
IENoYXIiOw0KCW1zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoiSFRNTCBQ
cmVmb3JtYXR0ZWQiOw0KCWZvbnQtZmFtaWx5OkNvbnNvbGFzO30NCnNwYW4uRW1haWxTdHlsZTIw
DQoJe21zby1zdHlsZS10eXBlOnBlcnNvbmFsLXJlcGx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJp
IixzYW5zLXNlcmlmOw0KCWNvbG9yOndpbmRvd3RleHQ7fQ0KLk1zb0NocERlZmF1bHQNCgl7bXNv
LXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1zaXplOjEwLjBwdDsNCglmb250LWZhbWls
eToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpAcGFnZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVp
biAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGluIDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2Vj
dGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28g
OV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+
DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5
b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9v
OnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4t
VVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24x
Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoYW5rcyBOZWFsIGFuZCBZdWNodW5nLiAmIzQzO3F1
aWNAaWV0ZiBhbmQgR29ycnk8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxv
OnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdiBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpz
b2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQgMGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PGI+RnJvbTo8L2I+IE5lYWwgQ2FyZHdlbGwgJmx0O25jYXJkd2VsbEBnb29n
bGUuY29tJmd0OyA8YnI+DQo8Yj5TZW50OjwvYj4gRnJpZGF5LCBKdWx5IDEwLCAyMDIwIDc6NTEg
QU08YnI+DQo8Yj5Ubzo8L2I+IFByYXZlZW4gQmFsYXN1YnJhbWFuaWFuICZsdDtwcmF2YkBtaWNy
b3NvZnQuY29tJmd0Ozxicj4NCjxiPkNjOjwvYj4gWXVjaHVuZyBDaGVuZyAmbHQ7eWNoZW5nQGdv
b2dsZS5jb20mZ3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJlOiBGVzogW0VYVEVSTkFMXSBSZTog
V0dMQyByZXZpZXcgb2YgZHJhZnQtaWV0Zi1xdWljLXJlY292ZXJ5LTI5PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRp
dj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlllcywgYSA2NGsgVFNPIHF1YWxpZnkgYXMgYSBidXJz
dCBoaWdoZXIgdGhhbiAxMCBwYWNrZXRzLjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+SSBhZ3JlZSB3aXRoIFByYXZlZW4ncyByZW1hcmsgdGhhdCAmcXVvdDt0
aGUgTVVTVCByZWdhcmRpbmcgYnVyc3Qgc2l6ZSBpcyB3YXkgdG9vIHJlc3RyaWN0aXZlJnF1b3Q7
LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86
cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5J
J2Qgc3VnZ2VzdCBzb21ldGhpbmcgbGlrZTo8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwcmUg
c3R5bGU9ImJyZWFrLWJlZm9yZTpwYWdlIj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPiZuYnNw
OyZuYnNwOyBJbXBsZW1lbnRhdGlvbnMgTVVTVCBlaXRoZXIgdXNlIHBhY2luZyBvciBhbm90aGVy
IG1ldGhvZCB0byBsaW1pdCBzdWNoIGJ1cnN0cy48bzpwPjwvbzpwPjwvc3Bhbj48L3ByZT4NCjxw
cmUgc3R5bGU9ImJyZWFrLWJlZm9yZTpwYWdlIj48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPiZu
YnNwOyZuYnNwOyBJdCBpcyBSRUNPTU1FTkRFRCB0aGF0IHRyYWZmaWMgb3ZlciB0aGUgcHVibGlj
IEludGVybmV0IGxpbWl0IGJ1cnN0cyB0byB0aGUgaW5pdGlhbDxvOnA+PC9vOnA+PC9zcGFuPjwv
cHJlPg0KPHByZT48c3BhbiBzdHlsZT0iY29sb3I6YmxhY2siPiZuYnNwOyZuYnNwOyBjb25nZXN0
aW9uIHdpbmRvdzsgc2VlIDwvc3Bhbj48YSBocmVmPSJodHRwczovL25hbTA2LnNhZmVsaW5rcy5w
cm90ZWN0aW9uLm91dGxvb2suY29tLz91cmw9aHR0cHMlM0ElMkYlMkZ0b29scy5pZXRmLm9yZyUy
Rmh0bWwlMkZkcmFmdC1pZXRmLXF1aWMtcmVjb3ZlcnktMjklMjNzZWN0aW9uLTcuMiZhbXA7ZGF0
YT0wMiU3QzAxJTdDcHJhdmIlNDBtaWNyb3NvZnQuY29tJTdDOWRmM2U1ZjRmMGNhNGU1ODZmMDkw
OGQ4MjRlMGEzYWQlN0M3MmY5ODhiZjg2ZjE0MWFmOTFhYjJkN2NkMDExZGI0NyU3QzElN0MwJTdD
NjM3Mjk5ODk0NTI2NjU3OTA2JmFtcDtzZGF0YT16ZSUyRjdTcEtVYnJkZ3dJNm0lMkJTNnVFR1NC
Z2MyTmFwVnRQbjl2a09ZRmpWcyUzRCZhbXA7cmVzZXJ2ZWQ9MCI+U2VjdGlvbiA3LjI8L2E+PHNw
YW4gc3R5bGU9ImNvbG9yOmJsYWNrIj4uPG86cD48L286cD48L3NwYW4+PC9wcmU+DQo8cHJlIHN0
eWxlPSJicmVhay1iZWZvcmU6cGFnZSI+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj48bzpwPiZu
YnNwOzwvbzpwPjwvc3Bhbj48L3ByZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGUg
Y3VycmVudCBMaW51eCBUU08gc2l6aW5nIGFsZ29yaXRobSB3b3VsZCBiZSBjb21wYXRpYmxlIHdp
dGggc3VjaCBhIHJlY29tbWVuZGF0aW9uIHVwIHRvIHJhdGVzIG9mIDEwICogMTUwMCAqIDggLyAu
MDAxIC8gMTBeNiA9IDEyME1icHMuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+bmVhbDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIFRodSwgSnVsIDksIDIwMjAgYXQgMToyNiBQTSBQcmF2
ZWVuIEJhbGFzdWJyYW1hbmlhbiAmbHQ7PGEgaHJlZj0ibWFpbHRvOnByYXZiQG1pY3Jvc29mdC5j
b20iPnByYXZiQG1pY3Jvc29mdC5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICND
Q0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDtt
YXJnaW4tdG9wOjUuMHB0O21hcmdpbi1yaWdodDowaW47bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8
ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+WWVzIGJ1dCBUU08gdG8gTklDcyB0
aGF0IGRvIGl0IGluIGhhcmR3YXJlIGVmZmVjdGl2ZWx5IG1lYW5zIGEgYnVyc3QgYmVjYXVzZSBB
RkFJSyBoYXJkd2FyZSBkb2VzbuKAmXQgcGFjZSB0aG9zZSBvdXQuIFNvIHdvdWxkbuKAmXQgNjRr
IFRTTyBxdWFsaWZ5IGFzIGEgYnVyc3QgaGlnaGVyIHRoYW4gMTAgcGFja2V0cy4NCiBJIGFncmVl
IGEgU0hPVUxEIGlzIG11Y2ggYmV0dGVyLiA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTti
b3JkZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxiPkZyb206PC9iPiBZdWNodW5nIENoZW5nICZsdDs8
YSBocmVmPSJtYWlsdG86eWNoZW5nQGdvb2dsZS5jb20iIHRhcmdldD0iX2JsYW5rIj55Y2hlbmdA
Z29vZ2xlLmNvbTwvYT4mZ3Q7DQo8YnI+DQo8Yj5TZW50OjwvYj4gVGh1cnNkYXksIEp1bHkgOSwg
MjAyMCA5OjU5IEFNPGJyPg0KPGI+VG86PC9iPiBQcmF2ZWVuIEJhbGFzdWJyYW1hbmlhbiAmbHQ7
PGEgaHJlZj0ibWFpbHRvOnByYXZiQG1pY3Jvc29mdC5jb20iIHRhcmdldD0iX2JsYW5rIj5wcmF2
YkBtaWNyb3NvZnQuY29tPC9hPiZndDs8YnI+DQo8Yj5DYzo8L2I+IE5lYWwgQ2FyZHdlbGwgJmx0
OzxhIGhyZWY9Im1haWx0bzpuY2FyZHdlbGxAZ29vZ2xlLmNvbSIgdGFyZ2V0PSJfYmxhbmsiPm5j
YXJkd2VsbEBnb29nbGUuY29tPC9hPiZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IEZXOiBb
RVhURVJOQUxdIFJlOiBXR0xDIHJldmlldyBvZiBkcmFmdC1pZXRmLXF1aWMtcmVjb3ZlcnktMjk8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpw
PjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdp
bi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPm9oIEkgcmVhZCB0aGUg
c2VudGVuY2UgdG9vIGZhc3QuIEkgcmVhZCBpdCBhcyAmcXVvdDt1c2UgcGFjaW5nIG9yIGFub3Ro
ZXIgbWV0aG9kICh0aGF0IGJvdGgpIHRvIGxpbWl0IGJ1cnN0cyB0byB0aGUgaW5pdGlhbCB3aW5k
b3cmcXVvdDsuPG86cD48L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4m
bmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+SXQgc2VlbXMgdGhlIGRyYWZ0IGlzIHNheWluZywgd2l0aG91dCBwYWNpbmcsIHRoZSBidXJz
dCBzaG91bGQgYmUgY2FwcGVkLiBJIHRoaW5rIHRoYXQncyBmcm9tIHRoZSBvbGQgQlNEICZxdW90
O21heF9idXJzdCZxdW90OyBjb25maWcgdG8gMyA9PSBvbGRfSVcuIEZvciB0aGF0IEknZCBzYXkg
SVcxMCBzZXR0aW5nIGlzIHJlYXNvbmFibGUuDQogQWx0aG91Z2ggTVVTVCBpcyB0b28gc3Ryb25n
LiBJIGFncmVlIFNIT1VMRCBpcyBtb3JlIGFwcHJvcHJpYXRlPG86cD48L286cD48L3A+DQo8L2Rp
dj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4N
CjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5PbiBUaHUsIEp1bCA5LCAyMDIw
IGF0IDk6NTQgQU0gWXVjaHVuZyBDaGVuZyAmbHQ7PGEgaHJlZj0ibWFpbHRvOnljaGVuZ0Bnb29n
bGUuY29tIiB0YXJnZXQ9Il9ibGFuayI+eWNoZW5nQGdvb2dsZS5jb208L2E+Jmd0OyB3cm90ZTo8
bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2Jv
cmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDtt
YXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1yaWdodDowaW47bWFyZ2lu
LWJvdHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+TGlu
dXggc2l6ZXMgVFNPICh1cHQgdG8gNjRLQikgYmFzZWQgb24gdGhlIHNvY2tldCBwYWNpbmcgcmF0
ZS4gJmd0Oy41RyByZWFjaGVzIDY0S0IuIH42NE1icHMgcHJvZHVjZXMgMTZLQiAmZ3Q7IElXMTAs
IHJlZ2FyZGxlc3Mgb2YgdGhlIGRlc3RpbmF0aW9uIChlLmcuIERDIG9yIG5vdCkuPG86cD48L286
cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5UaGUgYXJ0
aWZpY2lhbCZuYnNwO0lXMTAgVFNPIGNhcCBtYWtlcyBubyBzZW5zZSBJTU8gaW4mbmJzcDt0aGUg
ZHJhZnQuIEknZCBjaGFsbGVuZ2UgdGhlIGF1dGhvcnMgdG8ganVzdGlmeSB3aXRoIGRhdGEuIElm
IGFueXRoaW5nIHRoZSBUU08gbmVlZHMgdG8gYmUgZXZlbiBiaWdnZXIgdGhhbiA2NEtCIG9uIGhp
Z2hlciBzcGVlZA0KIE5JQ3MuPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj5PbiBUaHUsIEp1bCA5LCAyMDIwIGF0IDk6MTYgQU0gUHJhdmVl
biBCYWxhc3VicmFtYW5pYW4gJmx0OzxhIGhyZWY9Im1haWx0bzpwcmF2YkBtaWNyb3NvZnQuY29t
IiB0YXJnZXQ9Il9ibGFuayI+cHJhdmJAbWljcm9zb2Z0LmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGluIDYuMHB0O21hcmdp
bi1sZWZ0OjQuOHB0O21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0OjBpbjttYXJnaW4tYm90
dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5Eb2VzIExp
bnV4IG5ldmVyIHNlbmQgYSBUU08gb2Ygc2l6ZSBtb3JlIHRoYW4gMTAgcGFja2V0cyB1bmRlciBh
bnkgY2lyY3Vtc3RhbmNlcz88bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPlRoYW5rczxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4N
CjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEg
MS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBz
dHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8i
PjxiPkZyb206PC9iPiBQcmF2ZWVuIEJhbGFzdWJyYW1hbmlhbg0KPGJyPg0KPGI+U2VudDo8L2I+
IFRodXJzZGF5LCBKdWx5IDksIDIwMjAgOToxMiBBTTxicj4NCjxiPlRvOjwvYj4gR29ycnkgRmFp
cmh1cnN0ICZsdDs8YSBocmVmPSJtYWlsdG86Z29ycnlAZXJnLmFiZG4uYWMudWsiIHRhcmdldD0i
X2JsYW5rIj5nb3JyeUBlcmcuYWJkbi5hYy51azwvYT4mZ3Q7OyBJRVRGIFFVSUMgV0cgJmx0Ozxh
IGhyZWY9Im1haWx0bzpxdWljQGlldGYub3JnIiB0YXJnZXQ9Il9ibGFuayI+cXVpY0BpZXRmLm9y
ZzwvYT4mZ3Q7PGJyPg0KPGI+U3ViamVjdDo8L2I+IFJFOiBbRVhURVJOQUxdIFJlOiBXR0xDIHJl
dmlldyBvZiBkcmFmdC1pZXRmLXF1aWMtcmVjb3ZlcnktMjk8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvIj5XaXRoaW4gZGF0YSBjZW50ZXIgbWFpbmx5LiBUbyBoaXQg
NDAgR2JwcyBsaW5lIHJhdGUgeW91IGVmZmVjdGl2ZWx5IGhhdmUgdG8gYmF0Y2ggYXMgbXVjaCBh
cyB5b3UgY2FuIHRvIG1pbmltaXplIHRoZSBDUFUgcHJvY2Vzc2luZyBjb3N0cy4gVGhlIGJ1cnN0
IHNpemUgdG9kYXkgaXMgY2FwcGVkIHRvIDY0aw0KIGluIG1vc3QgY2FzZXMgZm9yIFRDUC4gTm93
IHRoYXQgd2UgaGF2ZSBzZWdtZW50YXRpb24gb2ZmbG9hZCBmb3IgVURQIHRoZSBzYW1lIHNob3Vs
ZCBhcHBseS4gRXZlbiBmb3IgSW50ZXJuZXQgZmFjaW5nIHRyYWZmaWMsIHRoZSBidXJzdHMgcHJp
bWFyaWx5IGltcGFjdCB0aGUgZmlyc3QgaG9wIHdpdGhpbiB0aGUgZGF0YWNlbnRlciBiZWNhdXNl
IHN1YnNlcXVlbnRseSB5b3UgZ2V0IHN0YXRpc3RpY2FsIG11bHRpcGxleGluZyBmcm9tIFRvUiBz
d2l0Y2gNCiBoYW5kbGluZyB0cmFmZmljIGZvcndhcmRpbmcgZm9yIG1hbnkgZmxvd3MgYW5kIHBv
cnRzLiA8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPk9rIHVuZGVyc3Rvb2QgYWJvdXQgdGhl
cmUgYmVpbmcgbm8gY29uZmxpY3QuIEJ1dCBJIHN0aWxsIGNvbnRlbmQgdGhhdCB0aGUgTVVTVCBy
ZWdhcmRpbmcgYnVyc3Qgc2l6ZSBpcyB3YXkgdG9vIHJlc3RyaWN0aXZlLiBXZSBzaG91bGQgYWxs
b3cgZm9yIGV4cGVyaW1lbnRhdGlvbiBoZXJlLiBPciBwcmVzZW50DQogZGF0YSB0aGF0IHRoaXMg
aXMgdW5pdmVyc2FsbHkgYmFkIG9uIGFsbCBuZXR3b3Jrcy4gQ3VycmVudCBwcm9kdWN0aW9uIHVz
ZSBvZiBUQ1Agc2hvd3MgdGhlcmUgaXMgbm8gbWFqb3IgcHJvYmxlbXMgd2l0aCBidXJzdGluZyBo
aWdoZXIuIEluIGZhY3QgZm9yIGxvdyBsYXRlbmN5IHNhbWUgcmFjayBzY2VuYXJpb3MgdGhpcyB3
aWxsIGJvb3N0IHJlY2VpdmUgcGVyZm9ybWFuY2UgYXMgd2VsbCBkdWUgdG8gYmV0dGVyIG9wcG9y
dHVuaXR5IGZvciBMUk8NCiBldGMuIDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDph
dXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2IHN0eWxlPSJib3JkZXI6bm9u
ZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGluZzozLjBwdCAwaW4gMGluIDBp
biI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPjxiPkZyb206PC9iPiBHb3JyeSBGYWlyaHVyc3Qg
Jmx0OzxhIGhyZWY9Im1haWx0bzpnb3JyeUBlcmcuYWJkbi5hYy51ayIgdGFyZ2V0PSJfYmxhbmsi
PmdvcnJ5QGVyZy5hYmRuLmFjLnVrPC9hPiZndDsNCjxicj4NCjxiPlNlbnQ6PC9iPiBUaHVyc2Rh
eSwgSnVseSA5LCAyMDIwIDE6MzkgQU08YnI+DQo8Yj5Ubzo8L2I+IFByYXZlZW4gQmFsYXN1YnJh
bWFuaWFuICZsdDs8YSBocmVmPSJtYWlsdG86cHJhdmJAbWljcm9zb2Z0LmNvbSIgdGFyZ2V0PSJf
YmxhbmsiPnByYXZiQG1pY3Jvc29mdC5jb208L2E+Jmd0OzsgSUVURiBRVUlDIFdHICZsdDs8YSBo
cmVmPSJtYWlsdG86cXVpY0BpZXRmLm9yZyIgdGFyZ2V0PSJfYmxhbmsiPnF1aWNAaWV0Zi5vcmc8
L2E+Jmd0Ozxicj4NCjxiPlN1YmplY3Q6PC9iPiBbRVhURVJOQUxdIFJlOiBXR0xDIHJldmlldyBv
ZiBkcmFmdC1pZXRmLXF1aWMtcmVjb3ZlcnktMjk8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9k
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHA+SGkg
UHJhdmVlbiw8bzpwPjwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHls
ZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPk9u
IDA4LzA3LzIwMjAgMjI6MjksIFByYXZlZW4gQmFsYXN1YnJhbWFuaWFuIHdyb3RlOjxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJn
aW4tYm90dG9tOjUuMHB0Ij4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+U2VjdGlvbiA3Ljk8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+JnF1b3Q7SW1wbGVtZW50YXRpb25z
IE1VU1QgZWl0aGVyIHVzZSBwYWNpbmcgb3IgYW5vdGhlciBtZXRob2QgdG8gbGltaXQgc3VjaCBi
dXJzdHMgdG8gdGhlIGluaXRpYWwgY29uZ2VzdGlvbiB3aW5kb3c7IHNlZSBTZWN0aW9uIDcuMi4m
cXVvdDsNCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1t
YXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5UaGlzIHNlZW1z
IHRvIHByZWNsdWRlIHVzZSBvZiBzZWdtZW50YXRpb24gb2ZmbG9hZCBvZiBzaXplcyBncmVhdGVy
IHRoYW4gSVcuIEluIGRhdGFjZW50ZXJzIHdlIHJvdXRpbmVseSBzZW5kIGJ1cnN0cyB0aGF0IGFy
ZSBoaWdoZXIgd2l0aG91dCBjYXVzaW5nIGxvc3MuDQo8bzpwPjwvbzpwPjwvcD4NCjwvYmxvY2tx
dW90ZT4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttYXJnaW4tYm90dG9tOjEyLjBwdCI+SXMgdGhhdCB3aXRoaW4gZGF0YSBjZW50cmVzPyBvciBm
cm9tIGRhdGEgY2VudHJlcyB0byBJbnRlcm5ldCBkZXN0aW5hdGlvbnM/IC4uLiBpZiB0aGUgbGF0
dGVyLCBob3cgY2FuIHRoZSBzZW5kZXIgYmUgc3VyZSB0aGlzIGlzIG5vdCBpbXBhY3Rpbmcgb3Ro
ZXIgdHJhZmZpYz88bzpwPjwvbzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9w
OjUuMHB0O21hcmdpbi1ib3R0b206NS4wcHQiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5UaGUg
TVVTVCBoZXJlIHNlZW1zIHVubmVjZXNzYXJ5LiBJdCBhbHNvIGNvbmZsaWN0cyB3aXRoIHRoZSBS
RUNPTU1FTkRFRCBpbiBhbiBlYXJsaWVyIHNlbnRlbmNlLjxvOnA+PC9vOnA+PC9wPg0KPC9ibG9j
a3F1b3RlPg0KPHA+SSBhY3R1YWxseSBkb24ndCBzZWUgdGhpcyBhcyBjb25mbGljdGluZy4gVGhl
IHJlY29tbWVuZGF0aW9uIGluIHRoaXMgc2VjdGlvbiBpcyB0byBwYWNlLiBUaGUgcmVxdWlyZW1l
bnQgaXMgdGhhdCBzZW5kZXIgbGltaXRzIGJ1cnN0LCB1c2luZyBzb21lIG1ldGhvZCwgdG8gdGhl
IHNpemUgb2YgSVcuPG86cD48L286cD48L3A+DQo8cD5Hb3JyeTxvOnA+PC9vOnA+PC9wPg0KPHA+
Jm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9k
aXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+
DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_CH2PR00MB0726F4FE6F8727D01ADB9543B6650CH2PR00MB0726namp_--


From nobody Fri Jul 10 10:11:33 2020
Return-Path: <pravb@microsoft.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4A43E3A043D for <quic@ietfa.amsl.com>; Fri, 10 Jul 2020 10:11:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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, DKIM_VALID_EF=-0.1, HTML_MESSAGE=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=microsoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RUUc8sWz4Ofo for <quic@ietfa.amsl.com>; Fri, 10 Jul 2020 10:11:29 -0700 (PDT)
Received: from NAM06-DM3-obe.outbound.protection.outlook.com (mail-eopbgr640110.outbound.protection.outlook.com [40.107.64.110]) (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 DE86F3A00E0 for <quic@ietf.org>; Fri, 10 Jul 2020 10:11:28 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=AQALNQ366QR9qSoVUsxcQa6lz0AddT5NqtN0edOns9vSQwncqdmBaYiB6zTMkGapfubxqy5Sb7tSlkdTRDcnZaH0LqX04PVkuOeMNy/641ev86cf1zeXXwnPHc4d9QIBMIxuOhsk1oXU533zLidT38CdpzwFQK/gJJ2Vg1p3xEaoEN31rc88/nwAwf36LkpjKD06RbILHQFnHQjhJmrLhPdl7qhYLg6U0lmbBHQHYLZaPiOB4B0oHYWf6alFACz6MNmSAiE6q+bKuTeEF+EY3vk0WXD+RKd1ScViGT54uI1du257HF7FWuAEo/2HQoFCj5CxYV0dHUr2CB7h0ZFaUA==
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=zuzFS7CzRuVx7D439vYv8gs5saCtWFUEwxf2zD0eCOI=; b=CRqD9Y4aSZ0MQr/P5S/TxT7FO82OV8445LbpT1nDpIUTPwKALrN404e+vWlWnhAqMD28fQ+nCnj9gT1qvBDIOQQDAzoUtXKO+nDUpIUVEajtbvfb2YchC2a7zEGz+7u0z0OIT0CTuIRRf0Exxe2a0H9RTlMZ7kLoQQjR1CZ1UZWpkpzZFgQd9HeqZexwV4L2dpBbus6CJ0MKZQY0nGf8C2lKW/FrJdBeUFrVuJK//Uggjs5b8jl6TK8pMp0NSWOCZ66yNjMv8qlU9GTxbk586mtVDamj/74G1Mc6fZeGX/ZL9tg0DkX7aFcIWyk6n18EO7mKIRuY7eCZw4sgr5QeTw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=zuzFS7CzRuVx7D439vYv8gs5saCtWFUEwxf2zD0eCOI=; b=BilPALL9fqbQe6eNH100vrp6KqdA9oNNcy/Xg+hT4r4BhEhilLDQqQ4NwQxJ/x+k0cDOKMA3M+3dLsV4uSUt4a0EgTO7PeSdtiyZvR9J4gSA/aeiyokUFYAuVZbEht3lTvAJUQpdWadCNjh3d9GAmxwks+4QvW1kS1MIKJmnqYs=
Received: from CH2PR00MB0726.namprd00.prod.outlook.com (2603:10b6:610:ad::12) by CH2PR00MB0726.namprd00.prod.outlook.com (2603:10b6:610:ad::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3213.0; Fri, 10 Jul 2020 17:11:27 +0000
Received: from CH2PR00MB0726.namprd00.prod.outlook.com ([fe80::7562:9640:814e:c7f1]) by CH2PR00MB0726.namprd00.prod.outlook.com ([fe80::7562:9640:814e:c7f1%8]) with mapi id 15.20.3213.000; Fri, 10 Jul 2020 17:11:27 +0000
From: Praveen Balasubramanian <pravb@microsoft.com>
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, IETF QUIC WG <quic@ietf.org>
CC: Neal Cardwell <ncardwell@google.com>, Yuchung Cheng <ycheng@google.com>
Subject: RE: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
Thread-Topic: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
Thread-Index: AdZVbt/Rv8RxmVSLQP+4+5gZJ/6HOgAXZSqAAA+FIqAAIiCEAAASWdaw
Date: Fri, 10 Jul 2020 17:11:27 +0000
Message-ID: <CH2PR00MB07267EBAC2BB08CCE5160EC6B6650@CH2PR00MB0726.namprd00.prod.outlook.com>
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <53187d65-f7b9-b99a-f68b-b267303ab399@erg.abdn.ac.uk> <CH2PR00MB0726D18611EC030BF548CA0DB6640@CH2PR00MB0726.namprd00.prod.outlook.com> <40818629-e1dc-f0f1-6173-984a8166c7c2@erg.abdn.ac.uk>
In-Reply-To: <40818629-e1dc-f0f1-6173-984a8166c7c2@erg.abdn.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=true; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2020-07-10T17:11:25Z;  MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=d3565457-885e-4560-8ca4-b4d01f8f7270; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0
authentication-results: erg.abdn.ac.uk; dkim=none (message not signed) header.d=none;erg.abdn.ac.uk; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [2001:4898:80e8:3:95d5:3f73:f682:d302]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: ffe36e03-cabf-48ba-b187-08d824f447fe
x-ms-traffictypediagnostic: CH2PR00MB0726:
x-microsoft-antispam-prvs: <CH2PR00MB07261FEFC8C9E1667215D74BB6650@CH2PR00MB0726.namprd00.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: C3Xy4VWX9O+YJdiR3w1FiXv+V5kak6Cd3rgLGuihMVvgKpo7qHvGFgrrgk4EHieVZU1UByc9XLNmPHPzg28dfJ7WIsO/+Od4V+PGe3hFB3+zWuaLYky2Asq0vPguqh2MC0Er2n2gc+E78o0/19ZZ+s91s/JQdkuE50t2XQg9zaVeX5MvNoRkmhSW7KnNOVZU7hOnYmozvz9lcXEyJCAh1URO0PYntFij8l2IiAXzRezRDudU6t7CE4KWiSROBaH3PPl+tGY1YYNNHLHNgyiHskqLPGjQgc+eCmJjrdVmeyDItlcP45Aue4saHszJ0QC5
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:CH2PR00MB0726.namprd00.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(136003)(346002)(376002)(39860400002)(396003)(366004)(5660300002)(478600001)(86362001)(64756008)(66556008)(83380400001)(76116006)(186003)(10290500003)(66446008)(7696005)(316002)(66476007)(66946007)(66574015)(4326008)(6506007)(110136005)(52536014)(2906002)(33656002)(8676002)(9686003)(296002)(54906003)(71200400001)(82950400001)(53546011)(8990500004)(8936002)(55016002)(82960400001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: DGfT4VfIKm9ndSL1GHG/i8NnJzgbuOG+U1TYDEMf5jEPSFRCAaWMhc5PeeUig5TBAyjogS06/XXynkRd6mi8WQTRFMw05aIAqPPrWNiHaZA/1J5BLM+vC8ZM9Gxsd1TPWjUBJ4oC5i99Rfu3JqvTDzwwGl+Cvu/ZC6tIB52TeS+6QIm4FlvU6oYMO7mk8wFhmjbuC5gMM/UARB7pttA7r5Lkd+/OXaChiJ1Ri5Vgl+GlVdblwiSGfHInMN+29Gaf5KKkkiIJ2/c/UIBd9IqDjeMySjkGq0syDLLpQFL8quRXToyToOTah4LBNZw2AIqbin4Z7v109jCFTJBV8TDmJd9N3OkOOQDxddx7S5yirMYM2/Ajm4f4a5VpGUKGPtfqQ28mrIU4TGAXCNZAiTByacpV6V6Ce0csMGZs7DVkxb/YGtSy4leGwGQKjLwHaLnBNDxcXABLf7Ss9w/ok3AGXPRIwYt5rNBTae3H5+PujSGAt+GPghEjJLdBT5+MuHFZgbAjg1PnYHPr1tORy1DFDt0rpDqu2xPYSKgaxRSDOlA=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CH2PR00MB07267EBAC2BB08CCE5160EC6B6650CH2PR00MB0726namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CH2PR00MB0726.namprd00.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ffe36e03-cabf-48ba-b187-08d824f447fe
X-MS-Exchange-CrossTenant-originalarrivaltime: 10 Jul 2020 17:11:27.0294 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: /Kd3v9iC3YCHS7bvgPwVdoi4De684fe0w9XDjOh1CqR14munFE1HazV2GNLollPglUhwKtRuZa+3zGk2DA8IJnJ8Tc1gfG3B5RgPlj8pkbU=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR00MB0726
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/HVWkmYzpgLAtaVrpWSqZrDbDdsI>
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, 10 Jul 2020 17:11:33 -0000

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

Precluding bursts higher than 10 packets is simply not viable or practical =
at really high data dates and is a major regression from the way TCP works =
today. QUIC is a general purpose transport and not scoped to the Internet o=
nly. On a side thread around Linux TCP behavior Neal suggested some alterna=
te text to scope this to Internet facing traffic but my contention still ho=
lds that there are many networks where higher bursts are not a problem and =
we should not restrict those use cases.

From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Sent: Friday, July 10, 2020 1:21 AM
To: Praveen Balasubramanian <pravb@microsoft.com>; IETF QUIC WG <quic@ietf.=
org>
Subject: Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29


Thanks Praveen,

I'd like to talk more, see below:
On 09/07/2020 17:11, Praveen Balasubramanian wrote:
Within data center mainly. To hit 40 Gbps line rate you effectively have to=
 batch as much as you can to minimize the CPU processing costs. The burst s=
ize today is capped to 64k in most cases for TCP. Now that we have segmenta=
tion offload for UDP the same should apply. Even for Internet facing traffi=
c, the bursts primarily impact the first hop within the datacenter because =
subsequently you get statistical multiplexing from ToR switch handling traf=
fic forwarding for many flows and ports.


I get this for this use-case and comments on high-speed NICs. I agree offlo=
ad is important.
Ok understood about there being no conflict. But I still contend that the M=
UST regarding burst size is way too restrictive. We should allow for experi=
mentation here.

I am not sure. The IW spec for TCP was based on evidence back around 2010, =
and the IETF agreed in RFC6928 that a burst size of 10 was acceptable as an=
 EXP spec for TCP.

I think we can safely refer to that - even perhaps take the leap-of-faith t=
hat EXP for TCP is equivalent to PS for QUIC, given subsequent experience. =
 I think the IW  **is** the burst size that the IETF should specify (becaus=
e it's dictated by buffering that is expected on the path).

I see opportunities here for experimentation and measurement opportunities,=
 and new specs can be proposed. Or the Specs can be recast with more detail=
. I also know that practical experience is that many people have configured=
 (probably tested, I hope) much larger IW's - and I'd hope they also make a=
 reasonable effort to monitor for possible interactions with other Internet=
 applications and services (as per section 12 of RFC6928).
Or present data that this is universally bad on all networks.

I think you touch on something that the IETF hasn't been great at talking a=
bout:

I could myself indeed likely produce data this shows this is "bad" in some =
networks that I value, and also show side-effects of collateral damage to o=
ther flows and adverse effects of line-rate bursts into equipment with smal=
l buffers. I don't know how useful that would be at all.

The IETF has typically defined a spec for endpoint. The way a modern endpoi=
nt is implemented can be quite different in a DC from a single device conne=
cted to the Internet. In a DC, I understand it is common  to distribute tra=
nsport functions to other parts of the network. e.g.: DDOS protection could=
 be done on a server; or by a box in front of it - similarly what matters t=
o the network CC is the  bursts of traffic that leaves a DC within a flow t=
o a local receiver, not what leaves a particular server within the DC netwo=
rk - I think in future we may do well to consider these differences?
Current production use of TCP shows there is no major problems with burstin=
g higher. In fact for low latency same rack scenarios this will boost recei=
ve performance as well due to better opportunity for LRO etc.

It's also possible that QUIC LRO (or whatever) includes some notion of per-=
flow burst-mitigation. Is that impossible?

However, I personally would not hold-up QUIC, to arrive at a new consensus.

Gorry

From: Gorry Fairhurst <gorry@erg.abdn.ac.uk><mailto:gorry@erg.abdn.ac.uk>
Sent: Thursday, July 9, 2020 1:39 AM
To: Praveen Balasubramanian <pravb@microsoft.com><mailto:pravb@microsoft.co=
m>; IETF QUIC WG <quic@ietf.org><mailto:quic@ietf.org>
Subject: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29


Hi Praveen,
On 08/07/2020 22:29, Praveen Balasubramanian wrote:
Section 7.9
"Implementations MUST either use pacing or another method to limit such bur=
sts to the initial congestion window; see Section 7.2."
This seems to preclude use of segmentation offload of sizes greater than IW=
. In datacenters we routinely send bursts that are higher without causing l=
oss.
Is that within data centres? or from data centres to Internet destinations?=
 ... if the latter, how can the sender be sure this is not impacting other =
traffic?


The MUST here seems unnecessary. It also conflicts with the RECOMMENDED in =
an earlier sentence.

I actually don't see this as conflicting. The recommendation in this sectio=
n is to pace. The requirement is that sender limits burst, using some metho=
d, to the size of IW.

Gorry



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

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">
<head>
<meta http-equiv=3D"Content-Type" content=3D"text/html; charset=3Dus-ascii"=
>
<meta name=3D"Generator" content=3D"Microsoft Word 15 (filtered medium)">
<style><!--
/* Font Definitions */
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	font-size:11.0pt;
	font-family:"Calibri",sans-serif;}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
span.EmailStyle19
	{mso-style-type:personal-reply;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
	{page:WordSection1;}
--></style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext=3D"edit">
<o:idmap v:ext=3D"edit" data=3D"1" />
</o:shapelayout></xml><![endif]-->
</head>
<body lang=3D"EN-US" link=3D"blue" vlink=3D"purple">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Precluding bursts higher than 10 packets is simply n=
ot viable or practical at really high data dates and is a major regression =
from the way TCP works today. QUIC is a general purpose transport and not s=
coped to the Internet only. On a side
 thread around Linux TCP behavior Neal suggested some alternate text to sco=
pe this to Internet facing traffic but my contention still holds that there=
 are many networks where higher bursts are not a problem and we should not =
restrict those use cases.
<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Gorry Fairhurst &lt;gorry@erg.abdn.ac.u=
k&gt; <br>
<b>Sent:</b> Friday, July 10, 2020 1:21 AM<br>
<b>To:</b> Praveen Balasubramanian &lt;pravb@microsoft.com&gt;; IETF QUIC W=
G &lt;quic@ietf.org&gt;<br>
<b>Subject:</b> Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-=
29<o:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p>Thanks Praveen, <o:p></o:p></p>
<p>I'd like to talk more, see below:<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On 09/07/2020 17:11, Praveen Balasubramanian wrote:<=
o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">Within data center mainly. To hit 40 Gbps line rate =
you effectively have to batch as much as you can to minimize the CPU proces=
sing costs. The burst size today is capped to 64k in most cases for TCP. No=
w that we have segmentation offload
 for UDP the same should apply. Even for Internet facing traffic, the burst=
s primarily impact the first hop within the datacenter because subsequently=
 you get statistical multiplexing from ToR switch handling traffic forwardi=
ng for many flows and ports.
<o:p></o:p></p>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
</blockquote>
<p>I get this for this use-case and comments on high-speed NICs. I agree of=
fload is important.<o:p></o:p></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">Ok understood about there being no conflict. But I s=
till contend that the MUST regarding burst size is way too restrictive. We =
should allow for experimentation here.
<o:p></o:p></p>
</blockquote>
<p>I am not sure. The IW spec for TCP was based on evidence back around 201=
0, and the IETF agreed in RFC6928 that a burst size of 10 was acceptable as=
 an EXP spec for TCP.
<o:p></o:p></p>
<p>I think we can safely refer to that - even perhaps take the leap-of-fait=
h that EXP for TCP is equivalent to PS for QUIC, given subsequent experienc=
e.&nbsp; I think the IW&nbsp; **is** the burst size that the IETF should sp=
ecify (because it's dictated by buffering
 that is expected on the path).<o:p></o:p></p>
<p>I see opportunities here for experimentation and measurement opportuniti=
es, and new specs can be proposed. Or the Specs can be recast with more det=
ail. I also know that practical experience is that many people have configu=
red (probably tested, I hope) much
 larger IW's - and I'd hope they also make a reasonable effort to monitor f=
or possible interactions with other Internet applications and services (as =
per section 12 of RFC6928).
<o:p></o:p></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">Or present data that this is universally bad on all =
networks.
<o:p></o:p></p>
</blockquote>
<p>I think you touch on something that the IETF hasn't been great at talkin=
g about:<o:p></o:p></p>
<p>I could myself indeed likely produce data this shows this is &quot;bad&q=
uot; in some networks that I value, and also show side-effects of collatera=
l damage to other flows and adverse effects of line-rate bursts into equipm=
ent with small buffers. I don't know how useful
 that would be at all.<o:p></o:p></p>
<p>The IETF has typically defined a spec for endpoint. The way a modern end=
point is implemented can be quite different in a DC from a single device co=
nnected to the Internet. In a DC, I understand it is common&nbsp; to distri=
bute transport functions to other parts
 of the network. e.g.: DDOS protection could be done on a server; or by a b=
ox in front of it - similarly what matters to the network CC is the&nbsp; b=
ursts of traffic that leaves a DC within a flow to a local receiver, not wh=
at leaves a particular server within
 the DC network - I think in future we may do well to consider these differ=
ences?<o:p></o:p></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">Current production use of TCP shows there is no majo=
r problems with bursting higher. In fact for low latency same rack scenario=
s this will boost receive performance as well due to better opportunity for=
 LRO etc.
<o:p></o:p></p>
</blockquote>
<p>It's also possible that QUIC LRO (or whatever) includes some notion of p=
er-flow burst-mitigation. Is that impossible?<o:p></o:p></p>
<p>However, I personally would not hold-up QUIC, to arrive at a new consens=
us.<o:p></o:p></p>
<p>Gorry<o:p></o:p></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<div>
<div style=3D"border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt 0in =
0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Gorry Fairhurst <a href=3D"mailto:gorry=
@erg.abdn.ac.uk">
&lt;gorry@erg.abdn.ac.uk&gt;</a> <br>
<b>Sent:</b> Thursday, July 9, 2020 1:39 AM<br>
<b>To:</b> Praveen Balasubramanian <a href=3D"mailto:pravb@microsoft.com">&=
lt;pravb@microsoft.com&gt;</a>; IETF QUIC WG
<a href=3D"mailto:quic@ietf.org">&lt;quic@ietf.org&gt;</a><br>
<b>Subject:</b> [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29<o=
:p></o:p></p>
</div>
</div>
<p class=3D"MsoNormal">&nbsp;<o:p></o:p></p>
<p>Hi Praveen,<o:p></o:p></p>
<div>
<p class=3D"MsoNormal">On 08/07/2020 22:29, Praveen Balasubramanian wrote:<=
o:p></o:p></p>
</div>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">Section 7.9<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">&quot;Implementations MUST either use pacing or another method to =
limit such bursts to the initial congestion window; see Section 7.2.&quot;
<o:p></o:p></p>
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">This seems to preclude use of segmentation offload of sizes greate=
r than IW. In datacenters we routinely send bursts that are higher without =
causing loss.
<o:p></o:p></p>
</blockquote>
<p class=3D"MsoNormal">Is that within data centres? or from data centres to=
 Internet destinations? ... if the latter, how can the sender be sure this =
is not impacting other traffic?<br>
<br>
<br>
<o:p></o:p></p>
<blockquote style=3D"margin-top:5.0pt;margin-bottom:5.0pt">
<p class=3D"MsoNormal" style=3D"mso-margin-top-alt:auto;mso-margin-bottom-a=
lt:auto">The MUST here seems unnecessary. It also conflicts with the RECOMM=
ENDED in an earlier sentence.<o:p></o:p></p>
</blockquote>
<p>I actually don't see this as conflicting. The recommendation in this sec=
tion is to pace. The requirement is that sender limits burst, using some me=
thod, to the size of IW.<o:p></o:p></p>
<p>Gorry<o:p></o:p></p>
<p>&nbsp;<o:p></o:p></p>
</blockquote>
</div>
</body>
</html>

--_000_CH2PR00MB07267EBAC2BB08CCE5160EC6B6650CH2PR00MB0726namp_--


From nobody Fri Jul 10 10:53:05 2020
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 A5C153A07C7; Fri, 10 Jul 2020 10:52:57 -0700 (PDT)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: <i-d-announce@ietf.org>
Cc: quic@ietf.org
Subject: I-D Action: draft-ietf-quic-load-balancers-03.txt
X-Test-IDTracker: no
X-IETF-IDTracker: 7.7.0
Auto-Submitted: auto-generated
Precedence: bulk
Reply-To: quic@ietf.org
Message-ID: <159440357754.20177.18134113507839417113@ietfa.amsl.com>
Date: Fri, 10 Jul 2020 10:52:57 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/b35DLJEcnUCFgnnq0tTrGHXVI-8>
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, 10 Jul 2020 17:52:58 -0000

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

        Title           : QUIC-LB: Generating Routable QUIC Connection IDs
        Authors         : Martin Duke
                          Nick Banks
	Filename        : draft-ietf-quic-load-balancers-03.txt
	Pages           : 32
	Date            : 2020-07-10

Abstract:
   QUIC connection IDs allow continuation of connections across address/
   port 4-tuple changes, and can store routing information for stateless
   or low-state load balancers.  They also can prevent linkability of
   connections across deliberate address migration through the use of
   protected communications between client and server.  This creates
   issues for load-balancing intermediaries.  This specification
   standardizes methods for encoding routing information given a small
   set of configuration parameters.  This framework also enables offload
   of other QUIC functions to trusted intermediaries, given the explicit
   cooperation of the QUIC server.


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

There are also htmlized versions available at:
https://tools.ietf.org/html/draft-ietf-quic-load-balancers-03
https://datatracker.ietf.org/doc/html/draft-ietf-quic-load-balancers-03

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


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 Jul 12 00:32:15 2020
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 9EDB33A0E99 for <quic@ietfa.amsl.com>; Sun, 12 Jul 2020 00:32:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=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=mnot.net header.b=oR/O0jLv; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=c/XBdAM5
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 6LeLdWxzDQLS for <quic@ietfa.amsl.com>; Sun, 12 Jul 2020 00:32:11 -0700 (PDT)
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 59B293A0E98 for <quic@ietf.org>; Sun, 12 Jul 2020 00:32:11 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 6F7D95C00AC for <quic@ietf.org>; Sun, 12 Jul 2020 03:32:10 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sun, 12 Jul 2020 03:32:10 -0400
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= fm3; bh=37QR9LveJ5THG/wwYGIPX+DtXcmJHGE5kw7qt3cBVsI=; b=oR/O0jLv wEk3jyHLiCzw8YOEDpDtfKIwPae1Cl3UZf3q8NFNqA3f8x5JovFha5gOlNwt/++X 47uzZImmlZlwKWx9uR9CF4zaPSfMrf+45fVCnAw9aCzTXUQQpWwGlsKGBJWnEQ08 0Ko4otmQECmqEF1H3gf1E6r/9vw21x+Rr0EA0DspzdpwMdXFdemlD1IRq9RIAlyn uquqEhorYXN6AKVcO0GVkaFtBcpCElwtV7JSFkJXRv6WrGtQjdwkD+r8D2YtzB4a JAn1EVaDCIs6cI7pTtUpqtDFslWtnkMaAJ15RSYAG3C+hZ4JxRHPXHrxo6/rWLBq q3+9Oq3L6lXtgw==
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=fm3; bh=37QR9LveJ5THG/wwYGIPX+DtXcmJH GE5kw7qt3cBVsI=; b=c/XBdAM5W3Ds1nWXpGctmxaMhtRJxKmQtg8KgpdxN4oU1 GqPHLGwnFUDRuKQR2I8nEZ7neWt6lChmt08noKHSf9Eb9AyMHu1lmwvF5EzHBMqC QypOw3nW943sxQspnh5V37XCHC19JS2nwiDws44W85GcCTdsdvKvxTSs6naPVE61 brRkW6UlU1ckS5uNnKXNQdg8iPhZiBGKIaLrX6n4TFND2ZXw/Lric5aaxTiTySbS RxACbNvEgRoZeC0bfdHZCv8xkVrzpm/QgJse+OupttIaJbKaqph5s/H+eFyFLOGf YKCOZxJuZFLFWN94JpQnq7Wx2xR6agASTbvugF4Jw==
X-ME-Sender: <xms:erwKX0Wg8ygrbGJQMer6Ghda5YXZ8jADECbp8n1FzzRDYq941k5l5A>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrvdehgddvhecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurheptggghffvufesrgdttdertddtjeenuc fhrhhomheptfgvphhoshhithhorhihucettghtihhvihhthicuufhumhhmrghrhicuueho thcuoeguohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvghtqeenucggtffrrghtthgvrh hnpeekfedvudetjedvfeekheeiveeugfefhfetteevgeffkefffeetffdvleehudeiteen ucffohhmrghinhepghhithhhuhgsrdgtohhmnecukfhppeegtddrkeekrddufeegrdegke enucevlhhushhtvghrufhiiigvpedunecurfgrrhgrmhepmhgrihhlfhhrohhmpeguohgp nhhothgprhgvphhlhiesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:erwKX4lXSy9sEKBfUL98qAB6Pk0SLJy_NtRxtZHzcgpXQxB0JR_4Hw> <xmx:erwKX4azZUsdKN6jnFeuTSprFvpGs8SzreZ2lYSNAAhTHcHk6dJ3nA> <xmx:erwKXzVAA3Kt7yx5Lv9b72Rq-cD1n7HapNAcpi9ar0i-bdbfhFKX5w> <xmx:erwKX1t7Rze6BuGFtiQxpaIpVevS9GizoInMtY5wiidt7lZWaTAlUw>
Received: from fv-az86.internal.cloudapp.net (unknown [40.88.134.48]) by mail.messagingengine.com (Postfix) with ESMTPA id 091363060067 for <quic@ietf.org>; Sun, 12 Jul 2020 03:32:10 -0400 (EDT)
Content-Type: multipart/alternative; boundary="===============7140077714462244909=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: quic@ietf.org
Subject: Weekly github digest (QUIC Activity Summary)
Message-Id: <20200712073210.091363060067@mailuser.nyi.internal>
Date: Sun, 12 Jul 2020 03:32:10 -0400 (EDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/zBcEnnyTP0NnAgWBxCWwx80Ei2w>
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, 12 Jul 2020 07:32:15 -0000

--===============7140077714462244909==
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/-2/=F0=9F=92=AC43)
  6 issues created:
  - Clarification for asymmetric links (return congestion, as well as limit=
 to throughput) (by gorryfair)
    https://github.com/quicwg/base-drafts/issues/3885=20
  - HTTP/1.x is not a TCP mapping (by royfielding)
    https://github.com/quicwg/base-drafts/issues/3883=20
  - How long is a validated address good for? (by martinthomson)
    https://github.com/quicwg/base-drafts/issues/3880=20
  - Ban offering TLS < 1.3 (by ekr)
    https://github.com/quicwg/base-drafts/issues/3878=20
  - Why no minimum Handshake packet size during anti-amplification? (by Mik=
eBishop)
    https://github.com/quicwg/base-drafts/issues/3876 [-recovery]=20
  - Persistent congestion threshold is unreliable during the early stages o=
f a connection (by kazuho)
    https://github.com/quicwg/base-drafts/issues/3875=20

  16 issues received 43 new comments:
  - #3880 How long is a validated address good for? (2 by ianswett, kazuho)
    https://github.com/quicwg/base-drafts/issues/3880 [-transport]=20
  - #3876 Why no minimum Handshake packet size during anti-amplification? (=
3 by MikeBishop, ekr)
    https://github.com/quicwg/base-drafts/issues/3876 [-recovery]=20
  - #3875 Persistent congestion threshold is unreliable during the early st=
ages of a connection (3 by ianswett, marten-seemann, martinthomson)
    https://github.com/quicwg/base-drafts/issues/3875 [-recovery]=20
  - #3860 incorrect error code used for invalid RETIRE_CONNECTION_ID frames=
 (2 by LPardue, ianswett)
    https://github.com/quicwg/base-drafts/issues/3860 [-transport]=20
  - #3852 Are 13.2.3 and 13.2.4 normative or not? (3 by MikeBishop, ianswet=
t)
    https://github.com/quicwg/base-drafts/issues/3852 [-transport]=20
  - #3842 Do I need to reset congestion info when the port changes? (5 by e=
kr, ianswett, janaiyengar, martinthomson)
    https://github.com/quicwg/base-drafts/issues/3842 [-transport]=20
  - #3841 Off-path and on-path (S 9.3.2) (1 by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/3841=20
  - #3834 Remove amplification throttle if the server receives Initial that=
 echoes its high entropy SCID. (4 by MikeBishop, ekr, huitema, ianswett)
    https://github.com/quicwg/base-drafts/issues/3834 [-transport]=20
  - #3833 Consider a specific error when switching to an HTTP/3 connection =
that does not support an extension (3 by LPardue, MikeBishop)
    https://github.com/quicwg/base-drafts/issues/3833 [-http]=20
  - #3832 Don't Stateless Reset probes from IPs you wouldn't talk to (8 by =
MikeBishop, ianswett, igorlord, martinthomson)
    https://github.com/quicwg/base-drafts/issues/3832 [-transport]=20
  - #3831 PTO after handshake completion is not well-defined (1 by kazuho)
    https://github.com/quicwg/base-drafts/issues/3831 [-recovery]=20
  - #3828 Inconsistency regarding future protection of version negoitation =
(1 by martinthomson)
    https://github.com/quicwg/base-drafts/issues/3828 [-invariants]=20
  - #3827 Invariants definition of Unused in Version Negotiation packet (1 =
by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/3827 [-invariants]=20
  - #3808 Versions are for endpoints (1 by LPardue)
    https://github.com/quicwg/base-drafts/issues/3808 [-invariants] [design=
]=20
  - #3800 Coalescing different CIDs for same connection (2 by dtikhonov, nq=
v)
    https://github.com/quicwg/base-drafts/issues/3800 [-transport]=20
  - #3765 disable_active_migration with SPA (3 by LPardue, MikeBishop, igor=
lord)
    https://github.com/quicwg/base-drafts/issues/3765 [-transport] [design]=
=20

  2 issues closed:
  - HTTP/1.x is not a TCP mapping https://github.com/quicwg/base-drafts/iss=
ues/3883 [-http]=20
  - Why no minimum Handshake packet size during anti-amplification? https:/=
/github.com/quicwg/base-drafts/issues/3876 [-recovery]=20

* quicwg/ops-drafts (+2/-9/=F0=9F=92=AC15)
  2 issues created:
  - verify all references to QUIC documents (by britram)
    https://github.com/quicwg/ops-drafts/issues/100 [-applicability] [-mana=
geability]=20
  - DDOS mitigation section should reference LB draft for details on retry =
mechanism (by britram)
    https://github.com/quicwg/ops-drafts/issues/97=20

  10 issues received 15 new comments:
  - #97 DDOS mitigation section should reference LB draft for details on re=
try mechanism (2 by britram, mirjak)
    https://github.com/quicwg/ops-drafts/issues/97 [-manageability]=20
  - #96 Mention accidental invariants and the calculus of blocking (1 by mi=
rjak)
    https://github.com/quicwg/ops-drafts/issues/96 [-manageability]=20
  - #95 Indicate which parts of the draft are v1 specific (1 by mirjak)
    https://github.com/quicwg/ops-drafts/issues/95=20
  - #93 Improve and generalize text on DoS detection and mitigation (2 by b=
ritram)
    https://github.com/quicwg/ops-drafts/issues/93=20
  - #92 CID and length (2 by britram, mirjak)
    https://github.com/quicwg/ops-drafts/issues/92 [-applicability]=20
  - #91 Advice on network state idle timeouts (1 by mirjak)
    https://github.com/quicwg/ops-drafts/issues/91 [-manageability]=20
  - #86 Update to invariants -07 (1 by britram)
    https://github.com/quicwg/ops-drafts/issues/86 [-manageability]=20
  - #79 recommendations for using ALPN in QUIC mappings (1 by britram)
    https://github.com/quicwg/ops-drafts/issues/79 [-applicability]=20
  - #71 Maybe provide guidance on use of advertised idle timeout (1 by mirj=
ak)
    https://github.com/quicwg/ops-drafts/issues/71 [-applicability]=20
  - #40 Reference load balancer draft for address validation token recommen=
dations (3 by britram, mirjak)
    https://github.com/quicwg/ops-drafts/issues/40 [-applicability]=20

  9 issues closed:
  - DDOS mitigation section should reference LB draft for details on retry =
mechanism https://github.com/quicwg/ops-drafts/issues/97 [-manageability]=20
  - recommendations for using ALPN in QUIC mappings https://github.com/quic=
wg/ops-drafts/issues/79 [-applicability]=20
  - Mention accidental invariants and the calculus of blocking https://gith=
ub.com/quicwg/ops-drafts/issues/96 [-manageability]=20
  - Improve and generalize text on DoS detection and mitigation https://git=
hub.com/quicwg/ops-drafts/issues/93=20
  - Update to invariants -07 https://github.com/quicwg/ops-drafts/issues/86=
 [-manageability]=20
  - Advice on network state idle timeouts https://github.com/quicwg/ops-dra=
fts/issues/91 [-manageability]=20
  - Mention accidental invariants and the calculus of blocking https://gith=
ub.com/quicwg/ops-drafts/issues/96 [-manageability]=20
  - Improve and generalize text on DoS detection and mitigation https://git=
hub.com/quicwg/ops-drafts/issues/93=20
  - Should we say something about how to create (integrity-protected) addre=
ss validation token... https://github.com/quicwg/ops-drafts/issues/40 [-app=
licability]=20

* quicwg/load-balancers (+1/-3/=F0=9F=92=AC2)
  1 issues created:
  - Simplify the configuration by merging server-id and zero-pad (by huitem=
a)
    https://github.com/quicwg/load-balancers/issues/41=20

  2 issues received 2 new comments:
  - #35 Using ECB for retry tokens seems sub optimal (1 by martinduke)
    https://github.com/quicwg/load-balancers/issues/35=20
  - #12 Configuration ID might be too small (1 by martinduke)
    https://github.com/quicwg/load-balancers/issues/12 [needs-discussion]=20

  3 issues closed:
  - Using ECB for retry tokens seems sub optimal https://github.com/quicwg/=
load-balancers/issues/35=20
  - Discuss uniqueness of config across load balancers https://github.com/q=
uicwg/load-balancers/issues/27=20
  - Effect on stateless resets https://github.com/quicwg/load-balancers/iss=
ues/9=20



Pull requests
-------------
* quicwg/base-drafts (+4/-1/=F0=9F=92=AC9)
  4 pull requests submitted:
  - http: fix sectiom references into HTTP Semantics (-09) (by reschke)
    https://github.com/quicwg/base-drafts/pull/3891=20
  - qpack: fix HTTP Semantics section ref (by reschke)
    https://github.com/quicwg/base-drafts/pull/3890=20
  - do not refer to HTTP/1 as a TCP mapping (by royfielding)
    https://github.com/quicwg/base-drafts/pull/3884=20
  - Allow endpoints to generate traffic keys asynchronously (by kazuho)
    https://github.com/quicwg/base-drafts/pull/3874=20

  3 pull requests received 9 new comments:
  - #3874 Allow endpoints to generate traffic keys asynchronously (1 by kaz=
uho)
    https://github.com/quicwg/base-drafts/pull/3874=20
  - #3870 Mixing connection IDs is OK (5 by DavidSchinazi, janaiyengar, mar=
tinthomson)
    https://github.com/quicwg/base-drafts/pull/3870 [-transport] [design]=20
  - #3861 change error to PROTOCOL_VIOLATION when receiving an invalid RCID=
 frame (3 by MikeBishop, kazuho, marten-seemann)
    https://github.com/quicwg/base-drafts/pull/3861 [-transport] [design]=20

  1 pull requests merged:
  - do not refer to HTTP/1 as a TCP mapping
    https://github.com/quicwg/base-drafts/pull/3884=20

* quicwg/ops-drafts (+11/-8/=F0=9F=92=AC2)
  11 pull requests submitted:
  - Clarify port selection and recommend ALPN or equivalent (by britram)
    https://github.com/quicwg/ops-drafts/pull/109=20
  - More improvements to QUIC identification (by britram)
    https://github.com/quicwg/ops-drafts/pull/108=20
  - Improvements to section 4.4 on DDoS (by britram)
    https://github.com/quicwg/ops-drafts/pull/107=20
  - Wire image specifics editorial changes (by britram)
    https://github.com/quicwg/ops-drafts/pull/106=20
  - mention possibility to embed length in CID and point to quic-load-bal=
=E2=80=A6 (by mirjak)
    https://github.com/quicwg/ops-drafts/pull/105=20
  - retry service and validation token (by mirjak)
    https://github.com/quicwg/ops-drafts/pull/104=20
  - Recommend longer timeouts (by mirjak)
    https://github.com/quicwg/ops-drafts/pull/103=20
  - More guidance on idle timeouts (by mirjak)
    https://github.com/quicwg/ops-drafts/pull/102=20
  - add ref to load balancers doc (by mirjak)
    https://github.com/quicwg/ops-drafts/pull/101=20
  - Edits on UDP policing section (by mirjak)
    https://github.com/quicwg/ops-drafts/pull/99=20
  - make clear we're serious about invariants (by britram)
    https://github.com/quicwg/ops-drafts/pull/98=20

  2 pull requests received 2 new comments:
  - #105 mention possibility to embed length in CID and point to quic-load-=
bal=E2=80=A6 (1 by mirjak)
    https://github.com/quicwg/ops-drafts/pull/105=20
  - #98 make clear we're serious about invariants (1 by mirjak)
    https://github.com/quicwg/ops-drafts/pull/98=20

  8 pull requests merged:
  - Clarify port selection and recommend ALPN or equivalent
    https://github.com/quicwg/ops-drafts/pull/109=20
  - More improvements to QUIC identification
    https://github.com/quicwg/ops-drafts/pull/108=20
  - Improvements to section 4.4 on DDoS
    https://github.com/quicwg/ops-drafts/pull/107=20
  - Wire image specifics editorial changes
    https://github.com/quicwg/ops-drafts/pull/106=20
  - Recommend longer timeouts
    https://github.com/quicwg/ops-drafts/pull/103=20
  - add ref to load balancers doc
    https://github.com/quicwg/ops-drafts/pull/101=20
  - make clear we're serious about invariants
    https://github.com/quicwg/ops-drafts/pull/98=20
  - DDoS mitigations - linking after NAT rebinding and UDP Policing
    https://github.com/quicwg/ops-drafts/pull/94=20

* quicwg/load-balancers (+2/-3/=F0=9F=92=AC1)
  2 pull requests submitted:
  - Down to one stream cipher algorithm (by martinduke)
    https://github.com/quicwg/load-balancers/pull/40=20
  - Editorial Pass on Triple Stream Cipher (by martinduke)
    https://github.com/quicwg/load-balancers/pull/39=20

  1 pull requests received 1 new comments:
  - #39 Editorial Pass on Triple Stream Cipher (1 by martinduke)
    https://github.com/quicwg/load-balancers/pull/39=20

  3 pull requests merged:
  - Down to one stream cipher algorithm
    https://github.com/quicwg/load-balancers/pull/40=20
  - Describe 3 pass stream cipher.
    https://github.com/quicwg/load-balancers/pull/33=20
  - New Security Considerations
    https://github.com/quicwg/load-balancers/pull/29=20


Repositories tracked by this digest:
-----------------------------------
* https://github.com/quicwg/base-drafts
* https://github.com/quicwg/ops-drafts
* https://github.com/quicwg/datagram
* https://github.com/quicwg/load-balancers
* https://github.com/quicwg/version-negotiation

--===============7140077714462244909==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (QUIC 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 July 12, 2020</h1>

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

<h2>Issues</h2>

<h3>quicwg/base-drafts (+6/-2/=F0=9F=92=AC43)</h3>
  <p class=3D"new">6 issues created:</p>
  <ul>
  <li>#3885 <a href=3D"https://github.com/quicwg/base-drafts/issues/3885">C=
larification for asymmetric links (return congestion, as well as limit to t=
hroughput)</a> (by gorryfair) </li>
 =20
  <li>#3883 <a href=3D"https://github.com/quicwg/base-drafts/issues/3883">H=
TTP/1.x is not a TCP mapping</a> (by royfielding) </li>
 =20
  <li>#3880 <a href=3D"https://github.com/quicwg/base-drafts/issues/3880">H=
ow long is a validated address good for?</a> (by martinthomson) </li>
 =20
  <li>#3878 <a href=3D"https://github.com/quicwg/base-drafts/issues/3878">B=
an offering TLS &lt; 1.3</a> (by ekr) </li>
 =20
  <li>#3876 <a href=3D"https://github.com/quicwg/base-drafts/issues/3876">W=
hy no minimum Handshake packet size during anti-amplification?</a> (by Mike=
Bishop) <span class=3D"label" style=3D"background-color: #fbca04; color: #0=
00000">-recovery</span> </li>
 =20
  <li>#3875 <a href=3D"https://github.com/quicwg/base-drafts/issues/3875">P=
ersistent congestion threshold is unreliable during the early stages of a c=
onnection</a> (by kazuho) </li>
  </ul>

  <p>16 issues received 43 new comments:</p>
  <ul>
  <li>#3880 <a href=3D"https://github.com/quicwg/base-drafts/issues/3880">H=
ow long is a validated address good for?</a> (2 by ianswett, kazuho) <span =
class=3D"label" style=3D"background-color: #fbca04; color: #000000">-transp=
ort</span> </li>
 =20
  <li>#3876 <a href=3D"https://github.com/quicwg/base-drafts/issues/3876">W=
hy no minimum Handshake packet size during anti-amplification?</a> (3 by Mi=
keBishop, ekr) <span class=3D"label" style=3D"background-color: #fbca04; co=
lor: #000000">-recovery</span> </li>
 =20
  <li>#3875 <a href=3D"https://github.com/quicwg/base-drafts/issues/3875">P=
ersistent congestion threshold is unreliable during the early stages of a c=
onnection</a> (3 by ianswett, marten-seemann, martinthomson) <span class=3D=
"label" style=3D"background-color: #fbca04; color: #000000">-recovery</span=
> </li>
 =20
  <li>#3860 <a href=3D"https://github.com/quicwg/base-drafts/issues/3860">i=
ncorrect error code used for invalid RETIRE_CONNECTION_ID frames</a> (2 by =
LPardue, ianswett) <span class=3D"label" style=3D"background-color: #fbca04=
; color: #000000">-transport</span> </li>
 =20
  <li>#3852 <a href=3D"https://github.com/quicwg/base-drafts/issues/3852">A=
re 13.2.3 and 13.2.4 normative or not?</a> (3 by MikeBishop, ianswett) <spa=
n class=3D"label" style=3D"background-color: #fbca04; color: #000000">-tran=
sport</span> </li>
 =20
  <li>#3842 <a href=3D"https://github.com/quicwg/base-drafts/issues/3842">D=
o I need to reset congestion info when the port changes?</a> (5 by ekr, ian=
swett, janaiyengar, martinthomson) <span class=3D"label" style=3D"backgroun=
d-color: #fbca04; color: #000000">-transport</span> </li>
 =20
  <li>#3841 <a href=3D"https://github.com/quicwg/base-drafts/issues/3841">O=
ff-path and on-path (S 9.3.2)</a> (1 by MikeBishop) </li>
 =20
  <li>#3834 <a href=3D"https://github.com/quicwg/base-drafts/issues/3834">R=
emove amplification throttle if the server receives Initial that echoes its=
 high entropy SCID.</a> (4 by MikeBishop, ekr, huitema, ianswett) <span cla=
ss=3D"label" style=3D"background-color: #fbca04; color: #000000">-transport=
</span> </li>
 =20
  <li>#3833 <a href=3D"https://github.com/quicwg/base-drafts/issues/3833">C=
onsider a specific error when switching to an HTTP/3 connection that does n=
ot support an extension</a> (3 by LPardue, MikeBishop) <span class=3D"label=
" style=3D"background-color: #fbca04; color: #000000">-http</span> </li>
 =20
  <li>#3832 <a href=3D"https://github.com/quicwg/base-drafts/issues/3832">D=
on&#x27;t Stateless Reset probes from IPs you wouldn&#x27;t talk to</a> (8 =
by MikeBishop, ianswett, igorlord, martinthomson) <span class=3D"label" sty=
le=3D"background-color: #fbca04; color: #000000">-transport</span> </li>
 =20
  <li>#3831 <a href=3D"https://github.com/quicwg/base-drafts/issues/3831">P=
TO after handshake completion is not well-defined</a> (1 by kazuho) <span c=
lass=3D"label" style=3D"background-color: #fbca04; color: #000000">-recover=
y</span> </li>
 =20
  <li>#3828 <a href=3D"https://github.com/quicwg/base-drafts/issues/3828">I=
nconsistency regarding future protection of version negoitation</a> (1 by m=
artinthomson) <span class=3D"label" style=3D"background-color: #fbca04; col=
or: #000000">-invariants</span> </li>
 =20
  <li>#3827 <a href=3D"https://github.com/quicwg/base-drafts/issues/3827">I=
nvariants definition of Unused in Version Negotiation packet</a> (1 by Mike=
Bishop) <span class=3D"label" style=3D"background-color: #fbca04; color: #0=
00000">-invariants</span> </li>
 =20
  <li>#3808 <a href=3D"https://github.com/quicwg/base-drafts/issues/3808">V=
ersions are for endpoints</a> (1 by LPardue) <span class=3D"label" style=3D=
"background-color: #fbca04; color: #000000">-invariants</span> <span class=
=3D"label" style=3D"background-color: #1d76db; color: #ffffff">design</span=
> </li>
 =20
  <li>#3800 <a href=3D"https://github.com/quicwg/base-drafts/issues/3800">C=
oalescing different CIDs for same connection</a> (2 by dtikhonov, nqv) <spa=
n class=3D"label" style=3D"background-color: #fbca04; color: #000000">-tran=
sport</span> </li>
 =20
  <li>#3765 <a href=3D"https://github.com/quicwg/base-drafts/issues/3765">d=
isable_active_migration with SPA</a> (3 by LPardue, MikeBishop, igorlord) <=
span class=3D"label" style=3D"background-color: #fbca04; color: #000000">-t=
ransport</span> <span class=3D"label" style=3D"background-color: #1d76db; c=
olor: #ffffff">design</span> </li>
  </ul>

  <p>2 issues closed:</p>
  <ul>
  <li>#3883 <a href=3D"https://github.com/quicwg/base-drafts/issues/3883">H=
TTP/1.x is not a TCP mapping</a> <span class=3D"label" style=3D"background-=
color: #fbca04; color: #000000">-http</span> </li>
 =20
  <li>#3876 <a href=3D"https://github.com/quicwg/base-drafts/issues/3876">W=
hy no minimum Handshake packet size during anti-amplification?</a> <span cl=
ass=3D"label" style=3D"background-color: #fbca04; color: #000000">-recovery=
</span> </li>
  </ul>

<h3>quicwg/ops-drafts (+2/-9/=F0=9F=92=AC15)</h3>
  <p class=3D"new">2 issues created:</p>
  <ul>
  <li>#100 <a href=3D"https://github.com/quicwg/ops-drafts/issues/100">veri=
fy all references to QUIC documents</a> (by britram) <span class=3D"label" =
style=3D"background-color: #fbca04; color: #000000">-applicability</span> <=
span class=3D"label" style=3D"background-color: #fbca04; color: #000000">-m=
anageability</span> </li>
 =20
  <li>#97 <a href=3D"https://github.com/quicwg/ops-drafts/issues/97">DDOS m=
itigation section should reference LB draft for details on retry mechanism<=
/a> (by britram) </li>
  </ul>

  <p>10 issues received 15 new comments:</p>
  <ul>
  <li>#97 <a href=3D"https://github.com/quicwg/ops-drafts/issues/97">DDOS m=
itigation section should reference LB draft for details on retry mechanism<=
/a> (2 by britram, mirjak) <span class=3D"label" style=3D"background-color:=
 #fbca04; color: #000000">-manageability</span> </li>
 =20
  <li>#96 <a href=3D"https://github.com/quicwg/ops-drafts/issues/96">Mentio=
n accidental invariants and the calculus of blocking</a> (1 by mirjak) <spa=
n class=3D"label" style=3D"background-color: #fbca04; color: #000000">-mana=
geability</span> </li>
 =20
  <li>#95 <a href=3D"https://github.com/quicwg/ops-drafts/issues/95">Indica=
te which parts of the draft are v1 specific</a> (1 by mirjak) </li>
 =20
  <li>#93 <a href=3D"https://github.com/quicwg/ops-drafts/issues/93">Improv=
e and generalize text on DoS detection and mitigation</a> (2 by britram) </=
li>
 =20
  <li>#92 <a href=3D"https://github.com/quicwg/ops-drafts/issues/92">CID an=
d length</a> (2 by britram, mirjak) <span class=3D"label" style=3D"backgrou=
nd-color: #fbca04; color: #000000">-applicability</span> </li>
 =20
  <li>#91 <a href=3D"https://github.com/quicwg/ops-drafts/issues/91">Advice=
 on network state idle timeouts</a> (1 by mirjak) <span class=3D"label" sty=
le=3D"background-color: #fbca04; color: #000000">-manageability</span> </li>
 =20
  <li>#86 <a href=3D"https://github.com/quicwg/ops-drafts/issues/86">Update=
 to invariants -07</a> (1 by britram) <span class=3D"label" style=3D"backgr=
ound-color: #fbca04; color: #000000">-manageability</span> </li>
 =20
  <li>#79 <a href=3D"https://github.com/quicwg/ops-drafts/issues/79">recomm=
endations for using ALPN in QUIC mappings</a> (1 by britram) <span class=3D=
"label" style=3D"background-color: #fbca04; color: #000000">-applicability<=
/span> </li>
 =20
  <li>#71 <a href=3D"https://github.com/quicwg/ops-drafts/issues/71">Maybe =
provide guidance on use of advertised idle timeout</a> (1 by mirjak) <span =
class=3D"label" style=3D"background-color: #fbca04; color: #000000">-applic=
ability</span> </li>
 =20
  <li>#40 <a href=3D"https://github.com/quicwg/ops-drafts/issues/40">Refere=
nce load balancer draft for address validation token recommendations</a> (3=
 by britram, mirjak) <span class=3D"label" style=3D"background-color: #fbca=
04; color: #000000">-applicability</span> </li>
  </ul>

  <p>9 issues closed:</p>
  <ul>
  <li>#97 <a href=3D"https://github.com/quicwg/ops-drafts/issues/97">DDOS m=
itigation section should reference LB draft for details on retry mechanism<=
/a> <span class=3D"label" style=3D"background-color: #fbca04; color: #00000=
0">-manageability</span> </li>
 =20
  <li>#79 <a href=3D"https://github.com/quicwg/ops-drafts/issues/79">recomm=
endations for using ALPN in QUIC mappings</a> <span class=3D"label" style=
=3D"background-color: #fbca04; color: #000000">-applicability</span> </li>
 =20
  <li>#96 <a href=3D"https://github.com/quicwg/ops-drafts/issues/96">Mentio=
n accidental invariants and the calculus of blocking</a> <span class=3D"lab=
el" style=3D"background-color: #fbca04; color: #000000">-manageability</spa=
n> </li>
 =20
  <li>#93 <a href=3D"https://github.com/quicwg/ops-drafts/issues/93">Improv=
e and generalize text on DoS detection and mitigation</a> </li>
 =20
  <li>#86 <a href=3D"https://github.com/quicwg/ops-drafts/issues/86">Update=
 to invariants -07</a> <span class=3D"label" style=3D"background-color: #fb=
ca04; color: #000000">-manageability</span> </li>
 =20
  <li>#91 <a href=3D"https://github.com/quicwg/ops-drafts/issues/91">Advice=
 on network state idle timeouts</a> <span class=3D"label" style=3D"backgrou=
nd-color: #fbca04; color: #000000">-manageability</span> </li>
 =20
  <li>#96 <a href=3D"https://github.com/quicwg/ops-drafts/issues/96">Mentio=
n accidental invariants and the calculus of blocking</a> <span class=3D"lab=
el" style=3D"background-color: #fbca04; color: #000000">-manageability</spa=
n> </li>
 =20
  <li>#93 <a href=3D"https://github.com/quicwg/ops-drafts/issues/93">Improv=
e and generalize text on DoS detection and mitigation</a> </li>
 =20
  <li>#40 <a href=3D"https://github.com/quicwg/ops-drafts/issues/40">Should=
 we say something about how to create (integrity-protected) address validat=
ion token...</a> <span class=3D"label" style=3D"background-color: #fbca04; =
color: #000000">-applicability</span> </li>
  </ul>

<h3>quicwg/load-balancers (+1/-3/=F0=9F=92=AC2)</h3>
  <p class=3D"new">1 issues created:</p>
  <ul>
  <li>#41 <a href=3D"https://github.com/quicwg/load-balancers/issues/41">Si=
mplify the configuration by merging server-id and zero-pad</a> (by huitema)=
 </li>
  </ul>

  <p>2 issues received 2 new comments:</p>
  <ul>
  <li>#35 <a href=3D"https://github.com/quicwg/load-balancers/issues/35">Us=
ing ECB for retry tokens seems sub optimal</a> (1 by martinduke) </li>
 =20
  <li>#12 <a href=3D"https://github.com/quicwg/load-balancers/issues/12">Co=
nfiguration ID might be too small</a> (1 by martinduke) <span class=3D"labe=
l" style=3D"background-color: #32d5db; color: #000000">needs-discussion</sp=
an> </li>
  </ul>

  <p>3 issues closed:</p>
  <ul>
  <li>#35 <a href=3D"https://github.com/quicwg/load-balancers/issues/35">Us=
ing ECB for retry tokens seems sub optimal</a> </li>
 =20
  <li>#27 <a href=3D"https://github.com/quicwg/load-balancers/issues/27">Di=
scuss uniqueness of config across load balancers</a> </li>
 =20
  <li>#9 <a href=3D"https://github.com/quicwg/load-balancers/issues/9">Effe=
ct on stateless resets</a> </li>
  </ul>



<h2>Pull requests</h2>
<h3>quicwg/base-drafts (+4/-1/=F0=9F=92=AC9)</h3>
  <p class=3D"new">4 pull requests submitted:</p>
  <ul>
  <li>#3891 <a href=3D"https://github.com/quicwg/base-drafts/pull/3891">htt=
p: fix sectiom references into HTTP Semantics (-09)</a> (by reschke) </li>
 =20
  <li>#3890 <a href=3D"https://github.com/quicwg/base-drafts/pull/3890">qpa=
ck: fix HTTP Semantics section ref</a> (by reschke) </li>
 =20
  <li>#3884 <a href=3D"https://github.com/quicwg/base-drafts/pull/3884">do =
not refer to HTTP/1 as a TCP mapping</a> (by royfielding) </li>
 =20
  <li>#3874 <a href=3D"https://github.com/quicwg/base-drafts/pull/3874">All=
ow endpoints to generate traffic keys asynchronously</a> (by kazuho) </li>
  </ul>

  <p>3 pull requests received 9 new comments:</p>
  <ul>
  <li>#3874 <a href=3D"https://github.com/quicwg/base-drafts/pull/3874">All=
ow endpoints to generate traffic keys asynchronously</a> (1 by kazuho) </li>
 =20
  <li>#3870 <a href=3D"https://github.com/quicwg/base-drafts/pull/3870">Mix=
ing connection IDs is OK</a> (5 by DavidSchinazi, janaiyengar, martinthomso=
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>#3861 <a href=3D"https://github.com/quicwg/base-drafts/pull/3861">cha=
nge error to PROTOCOL_VIOLATION when receiving an invalid RCID frame</a> (3=
 by MikeBishop, kazuho, marten-seemann) <span class=3D"label" style=3D"back=
ground-color: #fbca04; color: #000000">-transport</span> <span class=3D"lab=
el" style=3D"background-color: #1d76db; color: #ffffff">design</span> </li>
  </ul>

  <p>1 pull requests merged:</p>
  <ul>
  <li>#3884 <a href=3D"https://github.com/quicwg/base-drafts/pull/3884">do =
not refer to HTTP/1 as a TCP mapping</a> </li>
  </ul>

<h3>quicwg/ops-drafts (+11/-8/=F0=9F=92=AC2)</h3>
  <p class=3D"new">11 pull requests submitted:</p>
  <ul>
  <li>#109 <a href=3D"https://github.com/quicwg/ops-drafts/pull/109">Clarif=
y port selection and recommend ALPN or equivalent</a> (by britram) </li>
 =20
  <li>#108 <a href=3D"https://github.com/quicwg/ops-drafts/pull/108">More i=
mprovements to QUIC identification</a> (by britram) </li>
 =20
  <li>#107 <a href=3D"https://github.com/quicwg/ops-drafts/pull/107">Improv=
ements to section 4.4 on DDoS</a> (by britram) </li>
 =20
  <li>#106 <a href=3D"https://github.com/quicwg/ops-drafts/pull/106">Wire i=
mage specifics editorial changes</a> (by britram) </li>
 =20
  <li>#105 <a href=3D"https://github.com/quicwg/ops-drafts/pull/105">mentio=
n possibility to embed length in CID and point to quic-load-bal=E2=80=A6</a=
> (by mirjak) </li>
 =20
  <li>#104 <a href=3D"https://github.com/quicwg/ops-drafts/pull/104">retry =
service and validation token</a> (by mirjak) </li>
 =20
  <li>#103 <a href=3D"https://github.com/quicwg/ops-drafts/pull/103">Recomm=
end longer timeouts</a> (by mirjak) </li>
 =20
  <li>#102 <a href=3D"https://github.com/quicwg/ops-drafts/pull/102">More g=
uidance on idle timeouts</a> (by mirjak) </li>
 =20
  <li>#101 <a href=3D"https://github.com/quicwg/ops-drafts/pull/101">add re=
f to load balancers doc</a> (by mirjak) </li>
 =20
  <li>#99 <a href=3D"https://github.com/quicwg/ops-drafts/pull/99">Edits on=
 UDP policing section</a> (by mirjak) </li>
 =20
  <li>#98 <a href=3D"https://github.com/quicwg/ops-drafts/pull/98">make cle=
ar we&#x27;re serious about invariants</a> (by britram) </li>
  </ul>

  <p>2 pull requests received 2 new comments:</p>
  <ul>
  <li>#105 <a href=3D"https://github.com/quicwg/ops-drafts/pull/105">mentio=
n possibility to embed length in CID and point to quic-load-bal=E2=80=A6</a=
> (1 by mirjak) </li>
 =20
  <li>#98 <a href=3D"https://github.com/quicwg/ops-drafts/pull/98">make cle=
ar we&#x27;re serious about invariants</a> (1 by mirjak) </li>
  </ul>

  <p>8 pull requests merged:</p>
  <ul>
  <li>#109 <a href=3D"https://github.com/quicwg/ops-drafts/pull/109">Clarif=
y port selection and recommend ALPN or equivalent</a> </li>
 =20
  <li>#108 <a href=3D"https://github.com/quicwg/ops-drafts/pull/108">More i=
mprovements to QUIC identification</a> </li>
 =20
  <li>#107 <a href=3D"https://github.com/quicwg/ops-drafts/pull/107">Improv=
ements to section 4.4 on DDoS</a> </li>
 =20
  <li>#106 <a href=3D"https://github.com/quicwg/ops-drafts/pull/106">Wire i=
mage specifics editorial changes</a> </li>
 =20
  <li>#103 <a href=3D"https://github.com/quicwg/ops-drafts/pull/103">Recomm=
end longer timeouts</a> </li>
 =20
  <li>#101 <a href=3D"https://github.com/quicwg/ops-drafts/pull/101">add re=
f to load balancers doc</a> </li>
 =20
  <li>#98 <a href=3D"https://github.com/quicwg/ops-drafts/pull/98">make cle=
ar we&#x27;re serious about invariants</a> </li>
 =20
  <li>#94 <a href=3D"https://github.com/quicwg/ops-drafts/pull/94">DDoS mit=
igations - linking after NAT rebinding and UDP Policing</a> </li>
  </ul>

<h3>quicwg/load-balancers (+2/-3/=F0=9F=92=AC1)</h3>
  <p class=3D"new">2 pull requests submitted:</p>
  <ul>
  <li>#40 <a href=3D"https://github.com/quicwg/load-balancers/pull/40">Down=
 to one stream cipher algorithm</a> (by martinduke) </li>
 =20
  <li>#39 <a href=3D"https://github.com/quicwg/load-balancers/pull/39">Edit=
orial Pass on Triple Stream Cipher</a> (by martinduke) </li>
  </ul>

  <p>1 pull requests received 1 new comments:</p>
  <ul>
  <li>#39 <a href=3D"https://github.com/quicwg/load-balancers/pull/39">Edit=
orial Pass on Triple Stream Cipher</a> (1 by martinduke) </li>
  </ul>

  <p>3 pull requests merged:</p>
  <ul>
  <li>#40 <a href=3D"https://github.com/quicwg/load-balancers/pull/40">Down=
 to one stream cipher algorithm</a> </li>
 =20
  <li>#33 <a href=3D"https://github.com/quicwg/load-balancers/pull/33">Desc=
ribe 3 pass stream cipher.</a> </li>
 =20
  <li>#29 <a href=3D"https://github.com/quicwg/load-balancers/pull/29">New =
Security Considerations</a> </li>
  </ul>


<h2>Repositories tracked by this digest:</h2>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/quicwg/base-drafts">https://github.com/=
quicwg/base-drafts</a></li>
  <li><a href=3D"https://github.com/quicwg/ops-drafts">https://github.com/q=
uicwg/ops-drafts</a></li>
  <li><a href=3D"https://github.com/quicwg/datagram">https://github.com/qui=
cwg/datagram</a></li>
  <li><a href=3D"https://github.com/quicwg/load-balancers">https://github.c=
om/quicwg/load-balancers</a></li>
  <li><a href=3D"https://github.com/quicwg/version-negotiation">https://git=
hub.com/quicwg/version-negotiation</a></li>
  </ul>
</body>
</html>

--===============7140077714462244909==--


From nobody Mon Jul 13 07:39:32 2020
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id ECCA43A1450 for <quic@ietfa.amsl.com>; Mon, 13 Jul 2020 07:39:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 mt04MRw7SDGG for <quic@ietfa.amsl.com>; Mon, 13 Jul 2020 07:39:23 -0700 (PDT)
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 DFB493A1295 for <quic@ietf.org>; Mon, 13 Jul 2020 07:39:11 -0700 (PDT)
Received: by mail-lf1-x129.google.com with SMTP id g139so9196033lfd.10 for <quic@ietf.org>; Mon, 13 Jul 2020 07:39:11 -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=8LhhUNztJtKYlC0Q0tor4iBbEmLEWEH4AegOXrwK+zE=; b=LDVX1Ayg+6SrOtmrxY4IvwoSq5xsBkXNzg+OKieqBllNQUV6Te/uyWReWZNRUa+9jV TettF6gwMxIqaQtycZ2O0Dv2ah+wtNnoCV2ya+0aABxVl43PVP7L+NUrRS7/MAs/7jDY CTOaujpN6E5jP8000XiwZ4pnBYAV9StIiwBfhhs/B32k+le7Zvdm4fThMiveIqJIKqwK Ydly3r1S6ZRDhH+yqQTtEe6hGsm+s7zchBsVgzuGxRnE3TVIEnZXHwaGgqGiV1gMX5cD wMQ6P9XXMWOdJQusEEAuYmHOvnC5ijTCndyqT9CPjVEuDJ1qQa5Ehr5gIlX5EHWzIUsq gdtA==
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=8LhhUNztJtKYlC0Q0tor4iBbEmLEWEH4AegOXrwK+zE=; b=dnjs2lwK3d3RjzZ+WX20cqxqSKPnB70heZ2nPGGA0ecGujSzzSNINXQqJncfGYitM+ ekKU4zvlAka21jpKZgnaDyRQ3il5EwNfeWy8kalvZO7rKQRbJ2hSw3G5MDRytugdALU+ mILdTYoLfRXgfNYNUmOdvsmH7Ct4diZouWBPiGqBZ77WIZB4GQvxp0pz0cAp1HKsI6Kp JSt+RUXMqtMv67S7WYPn5TEr5yTBKwb5R3z08Z9HqsDVKvABpCWLPbVmMOw0mMT+phd0 FsOA59IVcJu8sIW94jxdeYN1pZPQP1FzRvkI/2bt8YqtyGKmiKfjfg8TNqlFORw38Cdy ICMA==
X-Gm-Message-State: AOAM533RBiKo5wRvDnNKT0MzVz0gguM8aPqVzTs4pgnD8ZJJQkOHFY+f Z9AB2wxYHCO29HFsa0ztk+1+uCr0kspIhEC4Hno=
X-Google-Smtp-Source: ABdhPJw/S/yaGcSmIsQ7sLD6EXlbGGNpxG0GFv+QG49lEW7x232b0DEIkKPV/rzeRQA42aSw6A/oadLhyjuuZysu+3M=
X-Received: by 2002:a19:c4a:: with SMTP id 71mr53410685lfm.27.1594651150028; Mon, 13 Jul 2020 07:39:10 -0700 (PDT)
MIME-Version: 1.0
References: <CABC-CqayJAeipEhsTf4h8rkUVQvYLd=1wF4UBMkaYSNMfvgnXw@mail.gmail.com> <CADdTf+jxKyPw_zfJ6FWCz230rXqg83d7rQJhKBteBvoLCut1RQ@mail.gmail.com>
In-Reply-To: <CADdTf+jxKyPw_zfJ6FWCz230rXqg83d7rQJhKBteBvoLCut1RQ@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 13 Jul 2020 09:38:43 -0500
Message-ID: <CAKKJt-dgEmOtvXR8hVT9qf+YgSe3m9LMUuE6=csU28j+j1V_ZQ@mail.gmail.com>
Subject: Re: Questions about recovery draft 29
To: Matt Joras <matt.joras@gmail.com>
Cc: Jonas Reynders <jonas.reynders@student.uhasselt.be>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000056954905aa53a7ab"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Vq2ZAEzyo3Y9FO1QKPCOeOIO-us>
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, 13 Jul 2020 14:39:30 -0000

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

Just to chime in here, so top-posting.

Matt is correct (that specifications !=3D implementations), but I note that
the transport area has produced, and revised,
https://datatracker.ietf.org/doc/rfc7414/ (A Roadmap for Transmission
Control Protocol (TCP) Specification Documents", that go through what Matt
characterized as the 'myriad RFCs that loosely define "IETF TCP"'

The TCP community used Informational RFCs to document what's a good idea
and what's a bad idea at the per-specification level ("really important to
implement this, that is a really bad idea so don't implement it", because
RFCs were the tools we have.

It might be worth thinking about the form a "QUIC Roadmap" might take,
given that we now have wikis, gitbub, and other tools that could allow the
QUIC roadmap and implementations to be more aware of each other, especially
if this was more granular than "this document".

We talked about this briefly at IETF 106 in TSVAREA. From the minutes at
https://datatracker.ietf.org/meeting/106/materials/minutes-106-tsvarea-02
 ...

   - Ted: Lots of creativity right now. people need to understand what they
   are doing *to* the protocol, not just *with* it. We should write "the
   hitchhiker's guide to QUIC". Intended for all audiences.
   - Mirja: That's what applicability and mgmt docs are for.
   - Ted: That's not what I'm looking for.
   - Spencer: Imagine if TCP roadmap had started before there were 150 RFCs=
!

Did people have thoughts about that?

Best,

Spencer


On Thu, Jul 9, 2020 at 2:10 PM Matt Joras <matt.joras@gmail.com> wrote:

> I won't offer specific answers to all your questions as Ian or Jana
> likely have better ones, however I'd like to make a general point
> about this line of questioning: Linux TCP !=3D IETF TCP, or, said
> another way, Implementations and Specifications are not the same
> thing. Recall that QUIC is a series of specifications being developed
> by the IETF, similar to the myriad RFCs that loosely define "IETF
> TCP". Linux's TCP stack is one such interpretation/implementation of
> TCP, and while it can inform the decisions of IETF workings, it should
> not be an undue determiner of the development of said specifications.
> Similarly we have an even wider and more diverse collection of QUIC
> interpretations/implementations in various states of maturity and
> deployment. Many diverge, sometimes heavily, from the specifications
> especially insofar as recovery is concerned. Chrome and us (mvfst) use
> BBR as the default congestion controller, others use Cubic or HSTCP or
> who knows what else. Chrome, AFAIK has a notion of adaptive reordering
> similar to Linux TCP and modifications to the draft-suggested time
> thresholds and PTO strategy.
>
> Whether some of these changes should be codified in the QUIC
> specifications is a good question. My hope is that these best
> practices will gain deployment experience and drive consensus at the
> IETF in future iterations of QUIC recovery and encounter fewer
> roadblocks than innovations based on TCP have historically
> experienced. As it is now though, QUIC's charter, by design, largely
> limits us to the adaptation of recovery and congestion control work
> that has already gained consensus via other IETF RFCs. That being
> said, what we have in the recovery specs may not be the "state of the
> art" exactly, but it is still quite good and I would argue has other
> significant advantages over what is commonly deployed in TCP, even
> Linux TCP.
>
> Matt Joras
>
> On Thu, Jul 9, 2020 at 9:22 AM Jonas Reynders
> <jonas.reynders@student.uhasselt.be> wrote:
> >
> > I have been looking at the recovery draft 29 of QUIC and comparing it t=
o
> TCP, specifically the linux implementation in kernel v5.4. I have a coupl=
e
> of questions about the design choices that differ from TCP in linux.
> >
> > The first question is in regards to ack-based loss detection where QUIC
> uses both a packet-threshold and time-threshold method. Looking at the
> linux implementation (kernel v5.4), TCP uses only a time-threshold method
> (RACK) as default. From my understanding both methods were used in linux
> some time ago, around the time it was clarified to use both methods for
> QUIC as well. However since then TCP changed to RACK only as the default,
> from what I found out it was due to tests at google detecting a 10%
> reduction in recovery latency (reference:
> https://patchwork.ozlabs.org/project/netdev/cover/20180516234017.172775-1=
-ycheng@google.com/).
> My question is why QUIC still recommends using both methods as default? I
> can understand that in a datacenter context, where RTT values are really
> low, RACK can struggle due to timers not being fine grained.
> >
> > My second question is in regards to the time threshold calculation(6.1.=
2
> in recovery draft). QUIC uses a constant value (9/8) for the time
> threshold, whilst in linux an adaptive threshold is used in the form of a
> reordering window variable. In the recovery draft it is mentioned that
> adaptive thresholds can be used, however it=E2=80=99s not mandatory. Is t=
here a
> reason why QUIC doesn=E2=80=99t use the linux method for an adaptive thre=
shold? The
> draft also mentions that reordering can be more common in QUIC and that
> adaptive thresholds have the advantage of being more aggressive when ther=
e
> is no reordering. The same question for the packet threshold, QUIC uses a
> constant threshold of 3 packets whilst in linux there is an adaptive
> threshold.
> >
> > My last question is that of merging the TLP and RTO into PTO. If I
> understand correctly, this was possible due to probe packet being
> ack-eliciting. And, that the time-threshold method would detect loss in a
> similar manner to RTO, with the RTO also causing a congestion collapse if
> no acks were received for consecutive RTOs. I assume that keeping RTO wou=
ld
> unnecessarily complicate things, is that correct?
>
>

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

<div dir=3D"ltr">Just to chime in here, so top-posting.=C2=A0<div><br></div=
><div>Matt is correct (that specifications !=3D implementations), but I not=
e that the transport area has produced, and revised,=C2=A0<a href=3D"https:=
//datatracker.ietf.org/doc/rfc7414/">https://datatracker.ietf.org/doc/rfc74=
14/</a>=C2=A0(A Roadmap for Transmission Control Protocol (TCP) Specificati=
on Documents&quot;, that go through what Matt characterized as the &#39;myr=
iad RFCs that loosely define &quot;IETF TCP&quot;&#39;</div><div><br></div>=
<div>The TCP community used Informational RFCs to document what&#39;s a goo=
d idea and what&#39;s a bad idea at the per-specification level (&quot;real=
ly important to implement this, that is a really bad idea so don&#39;t impl=
ement it&quot;, because RFCs were the tools we have.=C2=A0</div><div><br></=
div><div>It might be worth thinking about the form a &quot;QUIC Roadmap&quo=
t; might take, given that we now have wikis, gitbub, and other tools=C2=A0t=
hat could allow the QUIC roadmap and implementations to be more aware of ea=
ch other, especially if this was more granular than &quot;this document&quo=
t;.=C2=A0</div><div><br></div><div>We talked about this briefly at IETF 106=
 in TSVAREA. From the minutes at=C2=A0<a href=3D"https://datatracker.ietf.o=
rg/meeting/106/materials/minutes-106-tsvarea-02">https://datatracker.ietf.o=
rg/meeting/106/materials/minutes-106-tsvarea-02</a>=C2=A0...</div><div><ul>=
<li>Ted: Lots of creativity right now. people need to understand what they =
are doing *to* the protocol, not just *with* it. We should write &quot;the =
hitchhiker&#39;s guide to QUIC&quot;. Intended for all audiences.</li><li>M=
irja: That&#39;s what applicability and mgmt docs are for.</li><li>Ted: Tha=
t&#39;s not what I&#39;m looking for.</li><li>Spencer: Imagine if TCP roadm=
ap had started before there were 150 RFCs!<br></li></ul></div><div>Did peop=
le have thoughts about that?=C2=A0</div><div>=C2=A0<br></div><div>Best,</di=
v><div><br></div><div>Spencer</div><div><br></div></div><br><div class=3D"g=
mail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jul 9, 2020 at 2:=
10 PM Matt Joras &lt;<a href=3D"mailto:matt.joras@gmail.com">matt.joras@gma=
il.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"m=
argin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left=
:1ex">I won&#39;t offer specific answers to all your questions as Ian or Ja=
na<br>
likely have better ones, however I&#39;d like to make a general point<br>
about this line of questioning: Linux TCP !=3D IETF TCP, or, said<br>
another way, Implementations and Specifications are not the same<br>
thing. Recall that QUIC is a series of specifications being developed<br>
by the IETF, similar to the myriad RFCs that loosely define &quot;IETF<br>
TCP&quot;. Linux&#39;s TCP stack is one such interpretation/implementation =
of<br>
TCP, and while it can inform the decisions of IETF workings, it should<br>
not be an undue determiner of the development of said specifications.<br>
Similarly we have an even wider and more diverse collection of QUIC<br>
interpretations/implementations in various states of maturity and<br>
deployment. Many diverge, sometimes heavily, from the specifications<br>
especially insofar as recovery is concerned. Chrome and us (mvfst) use<br>
BBR as the default congestion controller, others use Cubic or HSTCP or<br>
who knows what else. Chrome, AFAIK has a notion of adaptive reordering<br>
similar to Linux TCP and modifications to the draft-suggested time<br>
thresholds and PTO strategy.<br>
<br>
Whether some of these changes should be codified in the QUIC<br>
specifications is a good question. My hope is that these best<br>
practices will gain deployment experience and drive consensus at the<br>
IETF in future iterations of QUIC recovery and encounter fewer<br>
roadblocks than innovations based on TCP have historically<br>
experienced. As it is now though, QUIC&#39;s charter, by design, largely<br=
>
limits us to the adaptation of recovery and congestion control work<br>
that has already gained consensus via other IETF RFCs. That being<br>
said, what we have in the recovery specs may not be the &quot;state of the<=
br>
art&quot; exactly, but it is still quite good and I would argue has other<b=
r>
significant advantages over what is commonly deployed in TCP, even<br>
Linux TCP.<br>
<br>
Matt Joras<br>
<br>
On Thu, Jul 9, 2020 at 9:22 AM Jonas Reynders<br>
&lt;<a href=3D"mailto:jonas.reynders@student.uhasselt.be" target=3D"_blank"=
>jonas.reynders@student.uhasselt.be</a>&gt; wrote:<br>
&gt;<br>
&gt; I have been looking at the recovery draft 29 of QUIC and comparing it =
to TCP, specifically the linux implementation in kernel v5.4. I have a coup=
le of questions about the design choices that differ from TCP in linux.<br>
&gt;<br>
&gt; The first question is in regards to ack-based loss detection where QUI=
C uses both a packet-threshold and time-threshold method. Looking at the li=
nux implementation (kernel v5.4), TCP uses only a time-threshold method (RA=
CK) as default. From my understanding both methods were used in linux some =
time ago, around the time it was clarified to use both methods for QUIC as =
well. However since then TCP changed to RACK only as the default, from what=
 I found out it was due to tests at google detecting a 10% reduction in rec=
overy latency (reference: <a href=3D"https://patchwork.ozlabs.org/project/n=
etdev/cover/20180516234017.172775-1-ycheng@google.com/" rel=3D"noreferrer" =
target=3D"_blank">https://patchwork.ozlabs.org/project/netdev/cover/2018051=
6234017.172775-1-ycheng@google.com/</a>). My question is why QUIC still rec=
ommends using both methods as default? I can understand that in a datacente=
r context, where RTT values are really low, RACK can struggle due to timers=
 not being fine grained.<br>
&gt;<br>
&gt; My second question is in regards to the time threshold calculation(6.1=
.2 in recovery draft). QUIC uses a constant value (9/8) for the time thresh=
old, whilst in linux an adaptive threshold is used in the form of a reorder=
ing window variable. In the recovery draft it is mentioned that adaptive th=
resholds can be used, however it=E2=80=99s not mandatory. Is there a reason=
 why QUIC doesn=E2=80=99t use the linux method for an adaptive threshold? T=
he draft also mentions that reordering can be more common in QUIC and that =
adaptive thresholds have the advantage of being more aggressive when there =
is no reordering. The same question for the packet threshold, QUIC uses a c=
onstant threshold of 3 packets whilst in linux there is an adaptive thresho=
ld.<br>
&gt;<br>
&gt; My last question is that of merging the TLP and RTO into PTO. If I und=
erstand correctly, this was possible due to probe packet being ack-elicitin=
g. And, that the time-threshold method would detect loss in a similar manne=
r to RTO, with the RTO also causing a congestion collapse if no acks were r=
eceived for consecutive RTOs. I assume that keeping RTO would unnecessarily=
 complicate things, is that correct?<br>
<br>
</blockquote></div>

--00000000000056954905aa53a7ab--


From nobody Mon Jul 13 09:40:24 2020
Return-Path: <yiannis@selfienetworks.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BDF4D3A1497 for <quic@ietfa.amsl.com>; Mon, 13 Jul 2020 09:40:22 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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=selfienetworks-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 4JLTqg4vnL3E for <quic@ietfa.amsl.com>; Mon, 13 Jul 2020 09:40:21 -0700 (PDT)
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 4A3893A146A for <quic@ietf.org>; Mon, 13 Jul 2020 09:40:21 -0700 (PDT)
Received: by mail-vs1-xe2f.google.com with SMTP id u133so6935353vsc.0 for <quic@ietf.org>; Mon, 13 Jul 2020 09:40:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=selfienetworks-com.20150623.gappssmtp.com; s=20150623; h=mime-version:date:message-id:to:from:subject; bh=fTaCWmq6/clvi9wU6znUFlcdYl/71bQ17auckbUbpIQ=; b=CdlqD7+azy3VsbS+/Vh/BlMZIGOJr0Gj5oUqsgwcxy4sk5Wb4U5ZS5i5oKqu9Q7SE5 bMa+fI+QvOqVYt5Mctt4DCm3e7oUe39i1L7KdPJPaXSmjTDKMF8vpY7QMSNfVZW5JU7y EL16eVq79C4PghdIN9mV14VyVnYeagcLvI+EpDfTOS2HIDbCxRvpY+kT0bFkxYqpEJjw VXXTQ6bdTfKWChgVQdexbcvPAWB41Oc1t+mDazHmSgOUl9j7ARGZgBXvxoonj2Yv/NX+ +dhlEE+mVdCRQBJJB/N/hVwg/0/ygxPFBPP0F/NdHugq8UZ08mmQmwPQ2cWDsbSkGo/j TqOA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:date:message-id:to:from:subject; bh=fTaCWmq6/clvi9wU6znUFlcdYl/71bQ17auckbUbpIQ=; b=NGJxkb9RaGP9S256bvTipzefhmFvLHTcWxWMMk9BQH/mfnGSXvt6+BG4h2WhvS1YVM DQDWev/hemB/VjxBrmH8ECk9Sv/95nxmpP3KAXRQU40bT5iG666z0mqeyfh7Gj1TDLHA siM4ANQnwHDicrQrLq118+K1+01mST/he3szkfA5jup9OwcRqGCuwcMjDEsXHzIZ363n eQdaqg4Wy+uDN+HHMWC7yqt3j8X8jbw2gBwm3C5EVbqm0uPc3qb7tYRR0t9SHpldwC69 EvtRkBERiwKf4rwrJeIDnSqHZnyElNO0cvtzszKVwuYTnD7QXshXzIb8KbG71OrrCznx kjZg==
X-Gm-Message-State: AOAM533ZpOR3E+LJCP0ZDuXNBFXSOww4VAR6mAqf7Xuf5SiyzcfgzYMh B3vY03ZEgHp1200H4decpt3I2NakO8Y=
X-Google-Smtp-Source: ABdhPJxS2VHHjIJ/wyIoVm5kUdHanSRGedTZRihUlM3FhpIZfpsWgUr8BKQfhSCPfo9Q2E4t2k+QAw==
X-Received: by 2002:a67:fd53:: with SMTP id g19mr142225vsr.187.1594658420025;  Mon, 13 Jul 2020 09:40:20 -0700 (PDT)
Received: from localhost (0.92.231.35.bc.googleusercontent.com. [35.231.92.0]) by smtp.gmail.com with ESMTPSA id d123sm2085194vke.43.2020.07.13.09.40.19 for <quic@ietf.org> (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Mon, 13 Jul 2020 09:40:19 -0700 (PDT)
Mime-Version: 1.0
X-Superhuman-Thread-ID: draft00f1db2f06b4c4f0
Date: Mon, 13 Jul 2020 16:40:19 +0000
Message-ID: <kckq833k.c16f8845-8673-4413-8b25-bbf69bc9de4d@we.are.superhuman.com>
To: quic@ietf.org
X-Mailer: Superhuman Desktop (2020-07-10T22:05:59Z)
X-Superhuman-ID: kckqfrer.a7a9fd5a-0eb3-43a8-a566-1b8d95905865
X-Superhuman-Draft-ID: draft001eca4a9bb1ea01
From: "Yiannis Yiakoumis" <yiannis@selfienetworks.com>
Subject: Network Tokens Draft 
Content-Type: multipart/alternative; boundary=123e28ad938f905226403b7a8254264c946bb1c9e43bc2b2b4071d232c3c
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/U4gQb3FIjBlmd_B_RdjCG2qAiB8>
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, 13 Jul 2020 16:40:23 -0000

--123e28ad938f905226403b7a8254264c946bb1c9e43bc2b2b4071d232c3c
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain; charset=UTF-8

This is a draft on "Network Tokens" which enable end users and application =
providers to explicitly coordinate with the network about how their traffic=
 is treated (e.g. to access a QoS service, a zero-rating service, or a fire=
wall whitelist).

https://tools.ietf.org/html/draft-yiakoumis-network-tokens-01

There is also a mailing list in, please sing-up if interested.

https://www.ietf.org/mailman/listinfo/network-tokens

We will present in TSV open meeting in IETF 108 ( Wed=C2=A0July 29th at 1pm=
 UTC), and most likely have a side meeting the day after.

Thanks,

Yiannis
--123e28ad938f905226403b7a8254264c946bb1c9e43bc2b2b4071d232c3c
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8

<html><head></head><body><div><div><div style=3D"display: none; border: 0px=
; width: 0px; height: 0px; overflow: hidden; visibility: hidden;"><img src=
=3D"https://r.superhuman.com/b_tZEW7EML_0pAU2Bbby9-VB22MIAaCV7JKx2Da8_A9Zxs=
fpOvgm8e6_iN2Ik11Rx9pAjYVqnLz__cofXsg6p9tnrNcp_DVs4vBJdxomHXkmmiuBzOvl4K9cY=
sUtx_DN3tw7DxWzEDpUTRuE2v39hC4sKBnsJ27SAW2iObLRnSJd.gif" alt=3D" " width=3D=
"1" height=3D"0" style=3D"display: none; border: 0px; width: 0px; height: 0=
px; overflow: hidden; visibility: hidden;"/><!--                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                                                                           =
                       --></div><div><div class=3D""><div class=3D""><p sty=
le=3D"text-decoration-color:initial;text-decoration-style:initial;margin:0p=
x;" class=3D"">This is a draft on &#34;Network Tokens&#34; which enable end=
 users and application providers to explicitly coordinate with the network =
about how their traffic is treated (e.g. to access a QoS service, a zero-ra=
ting service, or a firewall whitelist). <br/></p><div class=3D""><br/></div=
><p style=3D"text-decoration-color:initial;text-decoration-style:initial;ma=
rgin:0px;" class=3D""><a style=3D"color:rgb(84, 172, 220);text-decoration-c=
olor:initial;text-decoration-style:initial;text-decoration-line:underline;"=
 href=3D"https://tools.ietf.org/html/draft-yiakoumis-network-tokens-01" rel=
=3D"noopener noreferrer" target=3D"_blank">https://tools.ietf.org/html/draf=
t-yiakoumis-network-tokens-01</a><br/></p><p style=3D"text-decoration-color=
:initial;text-decoration-style:initial;margin:0px;" class=3D""><br/></p><di=
v class=3D"">There is also a mailing list in, please sing-up if interested.=
=C2=A0<br/></div><div class=3D""><a style=3D"color:rgb(84, 172, 220);text-d=
ecoration-color:initial;text-decoration-style:initial;text-decoration-line:=
underline;" href=3D"https://www.ietf.org/mailman/listinfo/network-tokens" r=
el=3D"noopener noreferrer" target=3D"_blank">https://www.ietf.org/mailman/l=
istinfo/network-tokens</a><br/></div><p class=3D""><br/></p><p style=3D"tex=
t-decoration-color:initial;text-decoration-style:initial;margin:0px;" class=
=3D"">We will present in TSV open meeting in IETF 108 (<span class=3D"sh-da=
te">Wed=C2=A0July 29th</span>=C2=A0at 1pm UTC), and most likely have a side=
 meeting the day after.=C2=A0<br/></p><p style=3D"text-decoration-color:ini=
tial;text-decoration-style:initial;margin:0px;" class=3D""><br/></p><div cl=
ass=3D"">Thanks,<span class=3D"">=C2=A0</span><br/></div><div class=3D"">Yi=
annis<br/></div></div></div></div></div></div></body></html>
--123e28ad938f905226403b7a8254264c946bb1c9e43bc2b2b4071d232c3c--


From nobody Mon Jul 13 14:51:13 2020
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 F28B53A0C92 for <quic@ietfa.amsl.com>; Mon, 13 Jul 2020 14:51:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level: 
X-Spam-Status: No, score=-17.599 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, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, 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 iLkBEj3MoBgV for <quic@ietfa.amsl.com>; Mon, 13 Jul 2020 14:51:10 -0700 (PDT)
Received: from mail-yb1-xb33.google.com (mail-yb1-xb33.google.com [IPv6:2607:f8b0:4864:20::b33]) (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 F30193A0CBE for <quic@ietf.org>; Mon, 13 Jul 2020 14:50:56 -0700 (PDT)
Received: by mail-yb1-xb33.google.com with SMTP id x138so5602639ybg.9 for <quic@ietf.org>; Mon, 13 Jul 2020 14:50:56 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=VMjJYqfUjUXZNhE9VLGXlKyGeaLqyOWkso5/WEmU7W8=; b=pqEt4BkVnElkWfEYgmyYa/heet1ahJcXDknnNfYQj7n0aggsLj8/1kjMRSmjdgfdUE kh85FU5bL5WHPVBdsK3rkLpG1MNz5D7nRIRvyr80JGTLxqg371pi/Zc7zQvljVga+REW oXpZAhaO0aRmO3qFCVRA7CR401UHH43V16p/xD7wZIxIvZNMxP/GTeVa0mKzuzLy9RAS IyUrt+B7C+yR5t4T0voMbOxoqwb1GNl42aaTyDfuQ/oz5bipqDkQs5oKKJRjcJlwASHI lqEf83M6Yrfy7kksUWk+iUDwogxbMaVFfVE3OPFOXbhZja3rVXkolXXdIWVzXM3UiHso vnMQ==
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=VMjJYqfUjUXZNhE9VLGXlKyGeaLqyOWkso5/WEmU7W8=; b=W18CKA4RD9Bw9b1E2k5bdCvUDcNv3zsM1B/T8cHqEXDnyULuzbflmuhZt/BS7BvpSg P3/3njYpYoP4SkkKKfKFe678V4sROJBr/4q66SnNk/bpQMj/uohtJw5j7pEydv4d3taP E2+Ra4WYeOvLH+KQoFes3CyooXgDitBDQxoRYtjNcYTkVb+wYUFNw+vIXPd+2psj2NRn YDRVtX2IHAtsNNvAJT2GDWEsm6XYPcnd+YEOMQ6qb0SOtqOMaHBO37+WhBRkLvOMqXIc 4tNruNIj17Bq1LXrKJuLug8kGKG51Xpp1CV3zhtVS+9IAYJ+0QZKeok5ipNR11Ub8oxN YElw==
X-Gm-Message-State: AOAM533DLw5v5Cg0W5uvHfipGml/2zaRWPYh2uI4E0j3RpAF2rwZ7fDf SLWqS/+yIoRcA2RLMzuJSIkPSgDDtBwcCviq73MteTS1
X-Google-Smtp-Source: ABdhPJwXPP1eIhVuN2PxQXKXEKQe340Ey1gSq8rox0Xo5H5kC94K0JW7U3HtWJn23kuYX6IYsF6H5ULsJH1EctIemns=
X-Received: by 2002:a25:ba8c:: with SMTP id s12mr3198334ybg.278.1594677055798;  Mon, 13 Jul 2020 14:50:55 -0700 (PDT)
MIME-Version: 1.0
References: <7b0c8566-46eb-490a-8b93-3fe7eb3e9ee4@www.fastmail.com>
In-Reply-To: <7b0c8566-46eb-490a-8b93-3fe7eb3e9ee4@www.fastmail.com>
From: Ian Swett <ianswett@google.com>
Date: Mon, 13 Jul 2020 17:50:44 -0400
Message-ID: <CAKcm_gNNK0tPFsfa2JnnPTyZ8pK9Pc2mPxzeoKFxdwS9Grb8RQ@mail.gmail.com>
Subject: Re: Versions numbers in invariants
To: Martin Thomson <mt@lowentropy.net>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000071c2ba05aa59afdd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/PCu1rCz8W_ldMpv01jKJzz5jfSo>
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, 13 Jul 2020 21:51:12 -0000

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

SGTM.

On Tue, Jun 30, 2020 at 10:33 PM Martin Thomson <mt@lowentropy.net> wrote:

> In my review of QUIC Invariants, I think that I found a promise we might
> not want to keep:
>
> > QUIC versions are identified with a 32-bit integer, encoded in network
> byte order.
>
> Implicit in this is that a packet containing version X is necessarily QUIC
> version X.  That's already not-true in some proposals.
>
> I think that this would be better defined as a field for use by endpoints:
>
> > The Version field contains a 32-bit integer, encoded in network byte
> order.
> > This value can be used by endpoints to identify a QUIC Version.
>
> This is an almost-cosmetic change, but it is a substantive change.  The
> intent is to wind back this promise and allow for the sorts of mappings
> contemplated by the version aliasing proposal.
>
> https://github.com/quicwg/base-drafts/issues/3808 is the issue, with some
> more details.
> https://github.com/quicwg/base-drafts/issues/3785 contains the proposed
> change.
>
>

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

<div dir=3D"ltr">SGTM.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr"=
 class=3D"gmail_attr">On Tue, Jun 30, 2020 at 10:33 PM Martin Thomson &lt;<=
a href=3D"mailto:mt@lowentropy.net">mt@lowentropy.net</a>&gt; wrote:<br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex">In my review of QUIC I=
nvariants, I think that I found a promise we might not want to keep:<br>
<br>
&gt; QUIC versions are identified with a 32-bit integer, encoded in network=
 byte order.<br>
<br>
Implicit in this is that a packet containing version X is necessarily QUIC =
version X.=C2=A0 That&#39;s already not-true in some proposals.<br>
<br>
I think that this would be better defined as a field for use by endpoints:<=
br>
<br>
&gt; The Version field contains a 32-bit integer, encoded in network byte o=
rder.<br>
&gt; This value can be used by endpoints to identify a QUIC Version.<br>
<br>
This is an almost-cosmetic change, but it is a substantive change.=C2=A0 Th=
e intent is to wind back this promise and allow for the sorts of mappings c=
ontemplated by the version aliasing proposal.<br>
<br>
<a href=3D"https://github.com/quicwg/base-drafts/issues/3808" rel=3D"norefe=
rrer" target=3D"_blank">https://github.com/quicwg/base-drafts/issues/3808</=
a> is the issue, with some more details.<br>
<a href=3D"https://github.com/quicwg/base-drafts/issues/3785" rel=3D"norefe=
rrer" target=3D"_blank">https://github.com/quicwg/base-drafts/issues/3785</=
a> contains the proposed change.<br>
<br>
</blockquote></div>

--00000000000071c2ba05aa59afdd--


From nobody Tue Jul 14 09:06:02 2020
Return-Path: <tim.jebb@bt.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D66613A0912 for <quic@ietfa.amsl.com>; Tue, 14 Jul 2020 09:06:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=bt.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 ibqT2CXb81r7 for <quic@ietfa.amsl.com>; Tue, 14 Jul 2020 09:05:59 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [213.121.35.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D31753A091B for <quic@ietf.org>; Tue, 14 Jul 2020 09:05:58 -0700 (PDT)
Received: from tpw09926dag05e.domain1.systemhost.net (10.9.202.20) by BWP09926085.bt.com (10.36.82.116) with Microsoft SMTP Server (version=TLS1_2,  cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Tue, 14 Jul 2020 17:05:55 +0100
Received: from tpw09926dag12e.domain1.systemhost.net (10.9.212.12) by tpw09926dag05e.domain1.systemhost.net (10.9.202.20) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 14 Jul 2020 17:05:55 +0100
Received: from bwp09926084.bt.com (10.36.82.115) by tpw09926dag12e.domain1.systemhost.net (10.9.212.12) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 14 Jul 2020 17:05:55 +0100
Received: from GBR01-CWL-obe.outbound.protection.outlook.com (104.47.20.59) by smtpe1.intersmtp.com (10.36.82.115) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Tue, 14 Jul 2020 17:05:54 +0100
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=bhrfLxVXSY3Iw+dt4N5b5Cl+0PuBqsLkS4HrDRDG/yJtTZ4+ortk9lTj2M+Z2yjbK1RtoWuqUODTJgH7j8W/KUabs8yhtqDvfzvOUJbrV4Pte+ddb08mUS2WsZV0HIVzMUiAdepiaLBU1GoLGELPJFSq6q8k6kTIQ8KMydRSFV1Ta+vgnw8/pHUJSbXzYonEn40PlWgn+f5PzPLN8RvGp2weKai9UbUfcjCfrrjcQOl9ni1XbC8iiV4Fbwm7YxPN00rHl0HOgCGrmvknQheqVXgNfFUilJUxwNAX7PKfMvAePkNEgqZ7sSwKsfaFJYhAhhfR0TWUSD4ke5bWfk65Ig==
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=FTDC4WgIt3zg0ZU20oBQH35FsA8ux8qjTmXWk0kkGWQ=; b=nQ3p5W73N/kN9v7mOBlX+HW43J7OuJGaOjQYKwPwya9DjWZ8KYQbw373tva3oEF1jjE6NxhcHERnlfrIXOQQMv5o2aipUuuimxvwiSAeOCT1MhGR79nZfjr0VUS+cA9WfLGFZ1AkH5mu68qOf71tmIg1/IXseUSTTtPzISQLpbA7SpP87Kqa+KGR5oZdl2/iAMb/z96yCHopsLPfBVvbXSH5bdhEZEqr/mP4uwe+FPO2sZLB3hJiXlIfGH+C5633lWBjLefssw+GOA2pvwVr93AXjRiigogSYYnhlxPb2PjYgDjEYz8mwA9hzFBj18+kKnT1G/apZ5tmIKoMVdv8lw==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=bt.com; dmarc=pass action=none header.from=bt.com; dkim=pass header.d=bt.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bt.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=FTDC4WgIt3zg0ZU20oBQH35FsA8ux8qjTmXWk0kkGWQ=; b=UoeHWA/i9fgtroZIax7ZYS6Z71OcfQf8q9V07oItefFulxhOcwLrsH19kn1VAO0LTYiKY20LvRUT94S1GVcIXbgSADzq5XjlQVTUr7ZbPVYuw2wqaC1/SEtnMLLs/p+pPZAPKK06pbJjJ8ZYbxZfw5WTip8pnEHemHpavldtXZw=
Received: from LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:dc::10) by LNXP123MB2586.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:ac::14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3153.29; Tue, 14 Jul 2020 16:05:53 +0000
Received: from LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM ([fe80::ec07:dcb5:1747:4632]) by LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM ([fe80::ec07:dcb5:1747:4632%7]) with mapi id 15.20.3174.025; Tue, 14 Jul 2020 16:05:53 +0000
From: <tim.jebb@bt.com>
To: <quic@ietf.org>
Subject: Problems verifying sample packet protection in appendix A of Using TLS to Secure QUIC
Thread-Topic: Problems verifying sample packet protection in appendix A of Using TLS to Secure QUIC
Thread-Index: AdZZ60hBgJSiLWoSRDqZxGYKUQVBHw==
Date: Tue, 14 Jul 2020 16:05:53 +0000
Message-ID: <LNXP123MB2460833EC5BC592C8D410EDCF2610@LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=bt.com;
x-originating-ip: [109.150.151.240]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 0083dfa4-4e2f-4c9c-7968-08d8280fc92f
x-ms-traffictypediagnostic: LNXP123MB2586:
x-microsoft-antispam-prvs: <LNXP123MB2586E42C8D4F8CB487418743F2610@LNXP123MB2586.GBRP123.PROD.OUTLOOK.COM>
x-antispam-2: 1
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-forefront-prvs: 0464DBBBC4
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: haCd+ac7Qmq/TrzZ32VCTQMoQrqc/ofJu5iNI/i3ms6mJ2eS6eT5jiaCvi0azQ2iGFL+32h09pk2lXUnaPBf3fMwEF2+NiwX+amXMP9Lcy+cszsUYjSQIZJIVOltCRi0haViID7YLJgou9s429cEAciyEItXZo5dPaMpNUssQhDfWFYjWW5kkjpHUjAGTJ/6VTZmnQYxR2wSR+2kLvnamX8HwOThMaCBHFiuXqBEcyIsyqry6QEErWPD8KP9/RLzJy9Gv+iePkdhl8z1+U9Rn0BwRObviXx/JMxDSFxT7OrpKESAS0xIsj44mOJ1SES7xzULT6FLgkoY/HyXzqW5cMgdxHwP0wegtQtmYb8x0YLh+cLhrBVxl9kGogjovMqDmduPcKZWY6lZkNCsEYLmkw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(376002)(346002)(396003)(39860400002)(366004)(136003)(33656002)(966005)(6506007)(7696005)(16799955002)(186003)(2906002)(478600001)(26005)(8936002)(52536014)(9326002)(66476007)(8676002)(55016002)(76116006)(9686003)(71200400001)(66556008)(66946007)(86362001)(66446008)(64756008)(83380400001)(166002)(6916009)(316002)(5660300002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: JdmDDo/nEmqfajr+B0/WzxtDfwwSlABlPJdDYXg8JhS4L8CeaNBMx3eYwi3HbSglNEgKafRDEKIWrJ0EfLKmJNNaMCKpVcykTAE/W/nrTzkg1UzMEiFxYFzCZDLCU2BxnjqrBK9ibzSRIXClEXH5Wz88/kfnfUSdOv9GUvOmYF+NggJJ9Qns2eu0GCySRrG4cNxTV63FFiVCiJ9RhlrKw+Pj3MzC0HEPT5pICfo4EiAnPozoByO4RA9/AkIPi30fyTraGIyWc9gY4g0i8tmhPax8p+EOuffwOMvOawA+gYYKM6e2Y8nztDTPg5gOkKCMS2iBNpM3hfvvOTnT4Uj3lHG35APRwecu0lmcMs/1gV2g6vkemwbn1qwTAmqUxJlOFvUy4btNWv+Myx0uOeop1mDjW2t+9uZlrOsnDdt4PKwSpkrVcgRxURhkSmUnIkv/SFSCfNwtt0RsY86i3OK0fecJ169xKdB/A6gQvkg6gpkZPQeYDwShhvGGoCmFKIKq
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_LNXP123MB2460833EC5BC592C8D410EDCF2610LNXP123MB2460GBRP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 0083dfa4-4e2f-4c9c-7968-08d8280fc92f
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Jul 2020 16:05:53.6718 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a7f35688-9c00-4d5e-ba41-29f146377ab0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 98nfeRc6UDSlbXp2b+SAbD4FY5EMFjpChtCIt74lgurqpghR+ffFH7O0MQnOu2ei
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LNXP123MB2586
X-OriginatorOrg: bt.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/84tPtT9oTMKo1DQA8Iobuy-cOAM>
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, 14 Jul 2020 16:06:01 -0000

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

Hi,

I'm working through Appendix A of the QUIC TLS doc to check my understandin=
g, but am having trouble decrypting the sample client initial packet.  I'm =
unsure if I've made a silly error or two, or if I've made one or more incor=
rect assumptions.  Or both.

The functions I'm using are the OpenSSL EVP ones.  I'm attempting to follow=
 the recipe here:
https://wiki.openssl.org/index.php/EVP_Authenticated_Encryption_and_Decrypt=
ion#Authenticated_Decryption_using_GCM_mode in conjunction with the draft R=
FC.


EVP_CIPHER_CTX_new()

EVP_DecryptInit_ex(ctx, EVP_aes_128_gcm(), NULL, NULL, NULL)

EVP_DecryptInit_ex(ctx, NULL, NULL, client_key, iv)         where the clien=
t key is 0x175257a31eb09dea9366d8bb79ad80ba and the iv is 0x6b26114b9cba2b6=
3a9e8dd4f

EVP_DecryptUpdate(ctx, NULL, &len, pUnprotectedHeader, headerLength)       =
    where the unprotected header is 0xc3ff00001d088394c8f03e5157080000449e0=
0000002 - this I believe is the Additional Data required

EVP_DecryptUpdate(ctx, decryptedPayload, &len, pPayload, payloadLength-16))=
   here I'm passing in the encrypted payload beginning 0xfb66bc5f and endin=
g 0xe82a4d919d48, length 1162.  I'm assuming that the final 16 bytes of the=
 payload is the authentication tag so am not passing it in here.  Note that=
 if this assumption about the authentication tag is correct, I think it cou=
ld be more clearly stated in the draft RFC.

EVP_CIPHER_CTX_ctrl(ctx, EVP_CTRL_GCM_SET_TAG, 16, tag) where tag is the fi=
nal 16 bytes of the encrypted payload, ie 0x43b1ca70 a2d8d3f7 25ead139 1377=
dcc0

EVP_DecryptFinal_ex(ctx, decryptedPayload + len, &len)

Everything seems OK until the EVP_DecryptFinal_ex() call which fails.

Is there anything obviously wrong with the above?  I've not posted the full=
 source code as I'm not asking people to check my working, I'm really askin=
g if my assumptions are correct, am I using the correct functions, input da=
ta etc.

Thanks in advance

Tim

--_000_LNXP123MB2460833EC5BC592C8D410EDCF2610LNXP123MB2460GBRP_
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;}
pre
	{mso-style-priority:99;
	mso-style-link:"HTML Preformatted Char";
	margin:0cm;
	margin-bottom:.0001pt;
	font-size:10.0pt;
	font-family:"Courier New";}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri",sans-serif;
	color:windowtext;}
span.HTMLPreformattedChar
	{mso-style-name:"HTML Preformatted Char";
	mso-style-priority:99;
	mso-style-link:"HTML Preformatted";
	font-family:"Courier New";
	mso-fareast-language:EN-GB;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-family:"Calibri",sans-serif;
	mso-fareast-language:EN-US;}
@page WordSection1
	{size:612.0pt 792.0pt;
	margin:72.0pt 72.0pt 72.0pt 72.0pt;}
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-GB" link=3D"#0563C1" vlink=3D"#954F72">
<div class=3D"WordSection1">
<p class=3D"MsoNormal">Hi, <o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">I&#8217;m working through Appendix A of the QUIC TLS=
 doc to check my understanding, but am having trouble decrypting the sample=
 client initial packet.&nbsp; I&#8217;m unsure if I&#8217;ve made a silly e=
rror or two, or if I&#8217;ve made one or more incorrect assumptions.&nbsp;
 Or both.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">The functions I&#8217;m using are the OpenSSL EVP on=
es.&nbsp; I&#8217;m attempting to follow the recipe here:<o:p></o:p></p>
<p class=3D"MsoNormal"><a href=3D"https://wiki.openssl.org/index.php/EVP_Au=
thenticated_Encryption_and_Decryption#Authenticated_Decryption_using_GCM_mo=
de">https://wiki.openssl.org/index.php/EVP_Authenticated_Encryption_and_Dec=
ryption#Authenticated_Decryption_using_GCM_mode</a>
 in conjunction with the draft RFC.<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">EVP_CIPHER_CTX_new()<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">EVP_DecryptInit_ex(ctx, EVP_aes_128_gcm(), NULL, NUL=
L, NULL)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">EVP_DecryptInit_ex(ctx, NULL, NULL, client_key, iv) =
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; where the client key is 0x175257=
a31eb09dea9366d8bb79ad80ba and the iv is 0x6b26114b9cba2b63a9e8dd4f<o:p></o=
:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">EVP_DecryptUpdate(ctx, NULL, &amp;len, pUnprotectedH=
eader, headerLength)&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp; where the unprotected header is 0xc3ff00001d088394c8f03e5157080000449=
e00000002 &#8211; this I believe is the Additional Data required<o:p></o:p>=
</p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">EVP_DecryptUpdate(ctx, decryptedPayload, &amp;len, p=
Payload, payloadLength-16))&nbsp;&nbsp; here I&#8217;m passing in the encry=
pted payload beginning 0xfb66bc5f and ending 0xe82a4d919d48, length 1162. &=
nbsp;I&#8217;m assuming that the final 16 bytes of the payload is
 the authentication tag so am not passing it in here.&nbsp; Note that if th=
is assumption about the authentication tag is correct, I think it could be =
more clearly stated in the draft RFC.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">EVP_CIPHER_CTX_ctrl(ctx, EVP_CTRL_GCM_SET_TAG, 16, t=
ag) where tag is the final 16 bytes of the encrypted payload, ie 0x43b1ca70=
 a2d8d3f7 25ead139 1377dcc0<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">EVP_DecryptFinal_ex(ctx, decryptedPayload &#43; len,=
 &amp;len)<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Everything seems OK until the EVP_DecryptFinal_ex() =
call which fails.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Is there anything obviously wrong with the above?&nb=
sp; I&#8217;ve not posted the full source code as I&#8217;m not asking peop=
le to check my working, I&#8217;m really asking if my assumptions are corre=
ct, am I using the correct functions, input data etc.<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Thanks in advance<o:p></o:p></p>
<p class=3D"MsoNormal"><o:p>&nbsp;</o:p></p>
<p class=3D"MsoNormal">Tim<o:p></o:p></p>
</div>
</body>
</html>

--_000_LNXP123MB2460833EC5BC592C8D410EDCF2610LNXP123MB2460GBRP_--


From nobody Tue Jul 14 11:47:18 2020
Return-Path: <nharper@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 3FA4D3A086B for <quic@ietfa.amsl.com>; Tue, 14 Jul 2020 11:47:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level: 
X-Spam-Status: No, score=-17.599 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, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, 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 GscQ0i0ymH69 for <quic@ietfa.amsl.com>; Tue, 14 Jul 2020 11:47:15 -0700 (PDT)
Received: from mail-oi1-x22e.google.com (mail-oi1-x22e.google.com [IPv6:2607:f8b0:4864:20::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 92CA93A0863 for <quic@ietf.org>; Tue, 14 Jul 2020 11:47:15 -0700 (PDT)
Received: by mail-oi1-x22e.google.com with SMTP id r8so14737134oij.5 for <quic@ietf.org>; Tue, 14 Jul 2020 11:47:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=DCCRwK5FVCaec4RAtTxXozKEGBaSAuKlmqjx8o+5+B0=; b=pySpn5baIJTAUiOkSnKkm5BMTFun5VzMrSJAxFtvGYAQ2DpGiIMktSxvbLkFQijo53 WwavM3AJ7HN1zTMSUE02th+9bnYVKFdeR6O6yh3T2vlGkQUdZzQLxTLdRpMxrPxOBcBE cuVA48n0tsmT+wwIG0WunyJilxUb9EWy2341mm5HPeR1DBnRcTut+3yK1hza3W/C2cHo tgDTqPflauiKlnaf8DHzvm03Lq8D8vyniiKMX5AHrSSwmXycEd/77b4W3Ud7f9dcQt4L 2yl7PtmcQ8w2n3p30m3NZJRVNzHVgk5z6kqnTSOPiMQGPqhZcGXO2xr6e3bqdpMOgNZu T/vw==
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=DCCRwK5FVCaec4RAtTxXozKEGBaSAuKlmqjx8o+5+B0=; b=BY79/gPj2+7xnKSHoXNz4jUPDYbKxRX4QFTQ6pJYBhopnpUnvzvs9GjGGlY9Gq/dQK TG3kuPxzcqBNB4ypBasU2/kTIHkFeoTGAb45U0e6vJJyeeKb9Lc1+7siGFaXhQhm7C/B IHtoTwx0lz/Y5df+0JO+ypdHObuFeOmBKhp9b/eW+24Gp82BZaTfliM7Re1gAe/1EZUb VQXkI6KoT3PaTx1uzThSboMkjnx07FAZKmwN+DEqL6SfEzV/DrcQE1vf2NrE8H41Quu+ WvtePOGbdwBXKFA2+gUWgb0XHkqVXat+NuNoN1G7Dp3ZWEOvwKm7TvFRV69cRnSAB4p6 EZBQ==
X-Gm-Message-State: AOAM5322RcDHPv1IxPcBzbXVuMD3CfS2pGL11gnaamS5ZN8CKQO45b4g NIaekbFmdBelLJ0Zhq1Z2fOCz3l5/G4nRlweozhf6A==
X-Google-Smtp-Source: ABdhPJx/qKL0KKBdjc5G2r2IV3JabQk2PQBBnTJ43jLgbmuOYTashQHgzjB+f0H71sKjbtiW+9AgjhTi6XqKo72YbqU=
X-Received: by 2002:aca:b187:: with SMTP id a129mr4650565oif.2.1594752434502;  Tue, 14 Jul 2020 11:47:14 -0700 (PDT)
MIME-Version: 1.0
References: <LNXP123MB2460833EC5BC592C8D410EDCF2610@LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM>
In-Reply-To: <LNXP123MB2460833EC5BC592C8D410EDCF2610@LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM>
From: Nick Harper <nharper@google.com>
Date: Tue, 14 Jul 2020 11:47:03 -0700
Message-ID: <CACdeXi+EUWRGoT7pWrqnEbQK9EoT0ERr7pKFmtOQ3pQZc9wfCw@mail.gmail.com>
Subject: Re: Problems verifying sample packet protection in appendix A of Using TLS to Secure QUIC
To: tim.jebb@bt.com
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005d76d405aa6b3cf6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/2rJ-A9yvyb3Kv6kAJQKk-cM4xT4>
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, 14 Jul 2020 18:47:17 -0000

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

On Tue, Jul 14, 2020 at 9:06 AM <tim.jebb@bt.com> wrote:

> Hi,
>
>
>
> I=E2=80=99m working through Appendix A of the QUIC TLS doc to check my
> understanding, but am having trouble decrypting the sample client initial
> packet.  I=E2=80=99m unsure if I=E2=80=99ve made a silly error or two, or=
 if I=E2=80=99ve made one
> or more incorrect assumptions.  Or both.
>
>
>
> The functions I=E2=80=99m using are the OpenSSL EVP ones.  I=E2=80=99m at=
tempting to
> follow the recipe here:
>
>
> https://wiki.openssl.org/index.php/EVP_Authenticated_Encryption_and_Decry=
ption#Authenticated_Decryption_using_GCM_mode
> in conjunction with the draft RFC.
>
>
>
>
>
> EVP_CIPHER_CTX_new()
>
>
>
> EVP_DecryptInit_ex(ctx, EVP_aes_128_gcm(), NULL, NULL, NULL)
>
>
>
> EVP_DecryptInit_ex(ctx, NULL, NULL, client_key, iv)         where the
> client key is 0x175257a31eb09dea9366d8bb79ad80ba and the iv is
> 0x6b26114b9cba2b63a9e8dd4f
>

You need to compute the nonce from the IV and the packet number. I assume
what the openssl documentation refers to as an IV is actually the nonce as
described in RFC 5116.

>
>
> EVP_DecryptUpdate(ctx, NULL, &len, pUnprotectedHeader,
> headerLength)           where the unprotected header is
> 0xc3ff00001d088394c8f03e5157080000449e00000002 =E2=80=93 this I believe i=
s the
> Additional Data required
>
>
>
> EVP_DecryptUpdate(ctx, decryptedPayload, &len, pPayload,
> payloadLength-16))   here I=E2=80=99m passing in the encrypted payload be=
ginning
> 0xfb66bc5f and ending 0xe82a4d919d48, length 1162.  I=E2=80=99m assuming =
that the
> final 16 bytes of the payload is the authentication tag so am not passing
> it in here.  Note that if this assumption about the authentication tag is
> correct, I think it could be more clearly stated in the draft RFC.
>

This is a quirk of the openssl API unfortunately. An AEAD decryption
operation should take 4 inputs: the key, the nonce, the associated data,
and the ciphertext. The ciphertext, as defined by RFC 5116, includes the
tag. There's no requirement on the structure of an AEAD's ciphertext,
including that some portion of the ciphertext be able to be identified as a
tag. AES-GCM does have this structure where the tag is at the end of the
ciphertext, and unfortunately openssl makes that part of the api for the
AEAD open operation, even though someone using it should never have to know
that detail of the AES-GCM algorithm.

>
>
> EVP_CIPHER_CTX_ctrl(ctx, EVP_CTRL_GCM_SET_TAG, 16, tag) where tag is the
> final 16 bytes of the encrypted payload, ie 0x43b1ca70 a2d8d3f7 25ead139
> 1377dcc0
>
>
>
> EVP_DecryptFinal_ex(ctx, decryptedPayload + len, &len)
>
>
>
> Everything seems OK until the EVP_DecryptFinal_ex() call which fails.
>
>
>
> Is there anything obviously wrong with the above?  I=E2=80=99ve not poste=
d the
> full source code as I=E2=80=99m not asking people to check my working, I=
=E2=80=99m really
> asking if my assumptions are correct, am I using the correct functions,
> input data etc.
>
>
>
> Thanks in advance
>
>
>
> Tim
>

--0000000000005d76d405aa6b3cf6
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 Tue, Jul 14, 2020 at 9:06 AM &lt;<=
a href=3D"mailto:tim.jebb@bt.com">tim.jebb@bt.com</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">





<div lang=3D"EN-GB">
<div>
<p class=3D"MsoNormal">Hi, <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I=E2=80=99m working through Appendix A of the QUIC T=
LS doc to check my understanding, but am having trouble decrypting the samp=
le client initial packet.=C2=A0 I=E2=80=99m unsure if I=E2=80=99ve made a s=
illy error or two, or if I=E2=80=99ve made one or more incorrect assumption=
s.=C2=A0
 Or both.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">The functions I=E2=80=99m using are the OpenSSL EVP =
ones.=C2=A0 I=E2=80=99m attempting to follow the recipe here:<u></u><u></u>=
</p>
<p class=3D"MsoNormal"><a href=3D"https://wiki.openssl.org/index.php/EVP_Au=
thenticated_Encryption_and_Decryption#Authenticated_Decryption_using_GCM_mo=
de" target=3D"_blank">https://wiki.openssl.org/index.php/EVP_Authenticated_=
Encryption_and_Decryption#Authenticated_Decryption_using_GCM_mode</a>
 in conjunction with the draft RFC.<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">EVP_CIPHER_CTX_new()<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">EVP_DecryptInit_ex(ctx, EVP_aes_128_gcm(), NULL, NUL=
L, NULL)<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">EVP_DecryptInit_ex(ctx, NULL, NULL, client_key, iv) =
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 where the client key is 0x175257=
a31eb09dea9366d8bb79ad80ba and the iv is 0x6b26114b9cba2b63a9e8dd4f</p></di=
v></div></blockquote><div><br></div><div>You need to compute the nonce from=
 the IV and the packet number. I assume what the openssl documentation refe=
rs to as an IV is actually the nonce as described in RFC 5116.</div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1p=
x solid rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-GB"><div><p clas=
s=3D"MsoNormal"><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">EVP_DecryptUpdate(ctx, NULL, &amp;len, pUnprotectedH=
eader, headerLength)=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 where the unprotected header is 0xc3ff00001d088394c8f03e515708000044=
9e00000002 =E2=80=93 this I believe is the Additional Data required<u></u><=
u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">EVP_DecryptUpdate(ctx, decryptedPayload, &amp;len, p=
Payload, payloadLength-16))=C2=A0=C2=A0 here I=E2=80=99m passing in the enc=
rypted payload beginning 0xfb66bc5f and ending 0xe82a4d919d48, length 1162.=
=C2=A0 I=E2=80=99m assuming that the final 16 bytes of the payload is
 the authentication tag so am not passing it in here.=C2=A0 Note that if th=
is assumption about the authentication tag is correct, I think it could be =
more clearly stated in the draft RFC.</p></div></div></blockquote><div><br>=
</div><div>This is a quirk of the openssl API unfortunately. An AEAD decryp=
tion operation should take 4 inputs: the key, the nonce, the associated dat=
a, and the ciphertext. The ciphertext, as defined by RFC 5116, includes the=
 tag. There&#39;s no requirement on the structure of an AEAD&#39;s cipherte=
xt, including that some portion of the ciphertext be able to be identified =
as a tag. AES-GCM does have this structure where the tag is at the end of t=
he ciphertext, and unfortunately openssl makes that part of the api for the=
 AEAD open operation, even though someone using it should never have to kno=
w that detail of the AES-GCM algorithm.</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 lang=3D"EN-GB"><div><p class=3D"MsoNormal"><u></u>=
<u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">EVP_CIPHER_CTX_ctrl(ctx, EVP_CTRL_GCM_SET_TAG, 16, t=
ag) where tag is the final 16 bytes of the encrypted payload, ie 0x43b1ca70=
 a2d8d3f7 25ead139 1377dcc0<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">EVP_DecryptFinal_ex(ctx, decryptedPayload + len, &am=
p;len)<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Everything seems OK until the EVP_DecryptFinal_ex() =
call which fails.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Is there anything obviously wrong with the above?=C2=
=A0 I=E2=80=99ve not posted the full source code as I=E2=80=99m not asking =
people to check my working, I=E2=80=99m really asking if my assumptions are=
 correct, am I using the correct functions, input data etc.<u></u><u></u></=
p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Thanks in advance<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Tim<u></u><u></u></p>
</div>
</div>

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

--0000000000005d76d405aa6b3cf6--


From nobody Wed Jul 15 00:24:20 2020
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 459BF3A082C for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 00:24:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=Hcjmsq+H; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=g3+DX9/x
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id pfnMWZVTG-r2 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 00:24:17 -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 B92C23A0829 for <quic@ietf.org>; Wed, 15 Jul 2020 00:24:17 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 05AD35C0160 for <quic@ietf.org>; Wed, 15 Jul 2020 03:24:17 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Wed, 15 Jul 2020 03:24:17 -0400
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=lowentropy.net; h=mime-version:message-id:date:from:to:subject:content-type; s= fm2; bh=7n2Shap/eCn9Cxq+r7YR3eEqBaW1i2yKpreSANRdiq0=; b=Hcjmsq+H ck04wIaBiBz7RxD2/IioHQb7EADGlJqZGn/AGq+LuXc/TFYoaqBHN6cUFedqO7a5 WYzz00Aa8u3bV77WAq5Or30DTWCzZAxz+R0JB+Sqx3yVxx1nGOZylDOJ5idBsDVL 5FghPfy6IRkGPURdl8l3HXgZBhDV83c9X4JqSicxX52Lsl0BI5GBx3K/9FqKG+3h jk0E3Tr+yp3qDXMokuVqDt4NLJAEEob4JxpcFdbIMVApt68z8mWGaT5uwOMk+wsh fBiyLrUTmujLFyce3EB01xQ+bN24OjU8sPpdDqoLbjr0EPBxOlEMaPU95fr+Kqg8 F6Zht13m0SviJw==
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=fm3; bh=7n2Shap/eCn9Cxq+r7YR3eEqBaW1i 2yKpreSANRdiq0=; b=g3+DX9/xAkUUFb/Rhaa+8vj4j0dDSUmb2ImTcezCO4p/o lXiT2hD8FT9O7OjvJ0zSCWVXfRGCmh4A4r6P5ADT8tY7QdhK4JnusyyjLPeDj7TF +zpSm5sqpNU9kKd80t3oPlcKlM6LF0JXcbQ3YNfIpQqGU2VmQBqJmWoPQ1Qf5dDm r7XfWLn72fgGYIoyXe6VIMqq5YIKJD0eDOd5Uo36OWiQo5bNyNLwK2wlJrc+FLEa H2hjiRAiLmYjYrvmYVjUqWiVMpkqivEVImxU96qrIVl9apL82GT/FAtU01dlrRo2 1VNrRSQxU0zx5vf5zZPiGZcJwsjOo/HdmM0z+VFyg==
X-ME-Sender: <xms:IK8OX09kBI_8sdXdI1zcZrjPWMjf57bdefKIpUdUI65EBoKfHG_feA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrfedugdduudelucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefofgggkfffhffvufgtsehttdertd erredtnecuhfhrohhmpedfofgrrhhtihhnucfvhhhomhhsohhnfdcuoehmtheslhhofigv nhhtrhhophihrdhnvghtqeenucggtffrrghtthgvrhhnpeegueehueejvdeiveffhedvke egffekgffgtdetleefkeeffedtjefhtdduvddutdenucffohhmrghinhepghhithhhuhgs rdgtohhmnecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomh epmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:IK8OX8vLxxkae3Uq9DtEDQPULX95_l5NAAhFQ2ffHKGYv-7iK0rRKg> <xmx:IK8OX6B_rltgTXhYt0ioAMAdHbv1UsR6IR_uzrwxTbM1aLwtFL4F-Q> <xmx:IK8OX0eDWXw44nGWShiTe1m01LB9z79E2l-T6GnZEIqXIq2a51EVDw> <xmx:Ia8OX3u7CRaJ6zOghoB2Ob495MG-GpO7HJX1Ted9IhgFFNTx5LjGLg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 985A1E00C1; Wed, 15 Jul 2020 03:24:16 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-613-g8a73ad6-fm-20200709.001-g8a73ad6e
Mime-Version: 1.0
Message-Id: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com>
Date: Wed, 15 Jul 2020 17:23:57 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: quic@ietf.org
Subject: Need your help: different connection IDs in the same datagram
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/JL0UthjhdFQ7h_ysW0LDrdmowlo>
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, 15 Jul 2020 07:24:19 -0000

https://github.com/quicwg/base-drafts/issues/3800 discovered a minor "discrepancy" in our requirements for coalescing packets.  We required that:

* senders not coalesce packets for different connections in the same datagram.

* receivers reject packets with different connection **IDs** in the same datagram.

https://github.com/quicwg/base-drafts/pull/3870/files was the result of a discussion where I was convinced that looser constraints here weren't harmful.  The requirements would identify connections, not connection IDs.

Originally, my inclination was to fix the requirement on the sender to use connection IDs, which would remove some linkability.  But then I was reminded that linkability is already defeated for several reasons.  You can't coalesce outside of the handshake and we require a stable path for the handshake AND long headers include a source connection ID that can be used for linkability.  So the linkability concern is basically lost.

We also learned that some implementations were generating packets while processing incoming packets.  Later they would coalesce these into a datagram that might then have different connection IDs on the packets it contains.

There has been some opposition to the proposed resolution in PR 3870.  

Apparently, for some, having multiple connection IDs in the same datagram complicates processing.  I don't understand this objection.  It seems to me more difficult to retain state across packets than it is to process each atomically.  I was hoping that Christian or Nick can explain more about how this affects them.

Marten also indicated that there was a reason not to allow this, but if I understand that, this is based on some potential for future optimization, which could be conditional on having consistent connection IDs.  If we moved to a scheme that required consistent connection IDs, anyone using that scheme could be required to avoid coalescing different connection IDs.  So this seems more of a theoretical concern.

And - in anticipation of maybe choosing to make senders use a consistent connection ID - if you might be generating coalesced datagrams with different connection IDs in packets, how hard would it be to ensure that these are consistent?  Lars and Ian, I think both of you indicated that you might do this.


From nobody Wed Jul 15 02:12:25 2020
Return-Path: <mauro.cociglio@telecomitalia.it>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 53C153A0365 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 02:12:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-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=telecomitalia.it
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id co7M_RFmXW5y for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 02:12:20 -0700 (PDT)
Received: from mx05.telecomitalia.it (mx05.telecomitalia.it [156.54.232.21]) (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 020AB3A0121 for <quic@ietf.org>; Wed, 15 Jul 2020 02:12:18 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; d=telecomitalia.it; s=selector1; c=relaxed/relaxed;  q=dns/txt; i=@telecomitalia.it; t=1594804335; x=2458717935; h=MIME-Version:From:Date:Message-ID:Subject:To; bh=GzhfOuvISrwJaupQkF+xnhkYKR5KmkUBSAxxF6sJLWU=; b=c7kE1HgimDQ1ECjiM0JC4ZJZMrPlHZO7DU2ZY/lfBWcuNbdej+jLtcGkCvHGWPlo 7Ea4dMKrwjOdjZ4xx+mdHH04WMIt/ZZxMQk5A+NE8SOcnGowisZY+EYOFYo5DVBE PdMVOZQ7OaAzErxyhiR9PDd3WRxu47JhnbRi6YtJqzGUK27TUCO59aJoVtqSSWSW FecSzOlJ2vBBb+plXfAyK6gxifQKMtvgn5Bbx06LNWfeIexWuUpnZRI/vRp0xis6 RYyEbkGYRqDjI3uuvyDcrRgiX3JOq/mynUy2pfIj2hTfTCbnn/VdBmyXNRbXQObj 1URwCQ6KtrXvKvwuEa0Yvw==;
X-AuditID: 0a5a2d15-e41ff70000008cc1-96-5f0ec86febb9
Received: from TELMBXD11BA020.telecomitalia.local ( [10.90.43.45]) by mx05.telecomitalia.it () with SMTP id FF.92.36033.F68CE0F5; Wed, 15 Jul 2020 11:12:15 +0200 (CEST)
From: Cociglio Mauro <mauro.cociglio@telecomitalia.it>
To: "Ruediger.Geib@telekom.de" <Ruediger.Geib@telekom.de>
CC: "ippm@ietf.org" <ippm@ietf.org>, "quic@ietf.org" <quic@ietf.org>, Giuseppe Fioccola <giuseppe.fioccola@huawei.com>, Nilo Massimo <massimo.nilo@telecomitalia.it>, "Bulgarella Fabio (Guest)" <fabio.bulgarella@guest.telecomitalia.it>, "riccardo.sisto@polito.it" <riccardo.sisto@polito.it>
Subject: R: About to measure Explicit Performances on user devices (mobile phones, PCs)
Thread-Topic: About to measure Explicit Performances on user devices (mobile phones, PCs)
Thread-Index: AdZQhy9WxJZw9I9ETrSFmbU5QsD6MAEZxd9wAWYsnkA=
Date: Wed, 15 Jul 2020 09:12:14 +0000
Message-ID: <da0613120a1443d4bec6927a6b49d11c@TELMBXD14BA020.telecomitalia.local>
References: <8c2df3da5f8c4450b272e3224dd23e46@TELMBXD14BA020.telecomitalia.local> <LEXPR01MB1040583A254B9FCEE49FF50D9C670@LEXPR01MB1040.DEUPRD01.PROD.OUTLOOK.DE>
In-Reply-To: <LEXPR01MB1040583A254B9FCEE49FF50D9C670@LEXPR01MB1040.DEUPRD01.PROD.OUTLOOK.DE>
Accept-Language: it-IT, en-US
Content-Language: it-IT
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [62.77.47.76]
x-ti-disclaimer: ADBanner
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFprHIsWRmVeSWpSXmKPExsXCFaWtq5t/gi/e4Pd3Xos1c1YwWfQ8eMds 0bOA2+Ln7Z3sFh+mcTiwerQcecvqsWTJTyaP0yuLPdpeKgSwRHHZpKTmZJalFunbJXBlTDq7 gqWgUbti67K5rA2MD5W7GDk5JARMJI5sn8XWxcjFISSwilGi6cAdFpAEm4CZxJktz9hAbBEB S4k9s5aygxQxC6xkkmjq/cQIkhAWiJQ41LSEEaIoWuLJ8hnsELaVRMuKKUwgNouAqkT/qg+s IDavQKDEwh9TWSC2LWaUeNV3Cmwbp0CMRMvpSWBFjAKyEhN2LwIbyiwgLvFi+gl2iFMFJJbs Oc8MYYtKvHz8jxXCNpDYunQfC4QtL/Fhw3eoGkmJw4c3sUHM0ZO4MXUKlK0tsWzha2aIgwQl Ts58AtYrJKAjcfn+IbYJjOKzkKyehaR9FpL2WUjaFzCyrGIUza0wMNUrSc1JTc7PzSxJzMlM 1Mss2cQIjkJd0R2M21a80TvEyMTBeIhRgoNZSYSXh4s3Xog3JbGyKrUoP76oNCe1+BCjNAeL kjivLTC+hQTSE0tSs1NTC1KLYLJMHJxSDUxzvl13DnkWUWx7mTXv0dvY+AuqHf7ORftmCxdv PPbpwX2jrx2Zt8sebEyck7O6bcO2p/9O/DpTvkvcS/ha0MuyT8EJ5z+W7W/TKNiZneCU4S0i 7fj07M41HM8rSnScAmUvtDJu45mo+IE5c47IRI8n2YZLtgb0znkfsNZO0ljzY1kT87SD6S/X tCZZ6Gu/t7Y9IHl2sb9CyaJDk7+szi63NMybOYVB5dfX5pNcWaFZn77du7v13tlN2YfD889N d7+/deuC7GBrxn2fdypwNkn+dd2Ukh9y/slq8dtv66TeTJMKKmsxlPTfm/86SdV86Y+4XVrN CRvXnzNxX1u6+29tdcDn7e8crd+1zp7Me1VFiaU4I9FQi7moOBEAnrevRjEDAAA=
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/B2cGSfmzTKapBqRy8iSQ765X04o>
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, 15 Jul 2020 09:12:24 -0000

Thanks Ruediger for your interesting comments.
Your suggested option to increase connections with randomly generated perfo=
rmance bits could be applied on connections that originate from users' devi=
ces that have not activated (or have actually deactivated) the explicit mea=
surements.
As you wrote, in this case, connections with "variable" performance bits (e=
ither "random" or "correctly" set) could be the majority and it would be qu=
ite difficult to prioritize this traffic.
Best regards.
Mauro

-----Messaggio originale-----
Da: Ruediger.Geib@telekom.de <Ruediger.Geib@telekom.de>=20
Inviato: mercoled=EC 8 luglio 2020 08:35
A: Cociglio Mauro <mauro.cociglio@telecomitalia.it>
Cc: riccardo.sisto@polito.it; ippm@ietf.org; quic@ietf.org
Oggetto: [EXT] AW: About to measure Explicit Performances on user devices (=
mobile phones, PCs)

Hi Mauro,

You suggest to base activation of the spin bit marking on a terminal config=
uration or on a user decision. That is reasonable, I think. An additional o=
ption is to activate the spin bit randomly on a number of connections. That=
 might help to avoid situations where a set spin bit indicates that the per=
formance of this flow is "rather likely" reported. A bit indicating that a =
flow's performance is likely to be reported to one or more interested parti=
es should be taken as an incentive for preferential treatment.

The number of flows with randomly activated spin bit should be higher than =
those reporting performance, if this option is pursued.

Regards,

Ruediger

-----Urspr=FCngliche Nachricht-----
Von: ippm <ippm-bounces@ietf.org> Im Auftrag von Cociglio Mauro
Gesendet: Freitag, 3. Juli 2020 14:33
An: IETF IPPM WG (ippm@ietf.org) <ippm@ietf.org>; quic@ietf.org
Cc: 'Riccardo Sisto' <riccardo.sisto@polito.it>
Betreff: [ippm] About to measure Explicit Performances on user devices (mob=
ile phones, PCs)

Dear QUIC and IPPM WG members.
=A0
After Spin bit introduction, and now with packet loss measurement proposals=
*, the Explicit Performance Monitoring on client-server protocols (e.g. QUI=
C) becomes an interesting topic for Telco.
Explicit Performance Monitoring enables a passive Observer to measure delay=
 and packet loss only watching the marking (a few bits) of production traff=
ic packets.
=A0
We propose that the first place where to put the Explicit Performance Obser=
ver is on the user device (e.g. mobile phones, PCs).
Main reasons of this choice.
1. Scalability. On the user device there are few connections to monitor.
2. The Observer can monitor both directions: upload and download (inside th=
e network is not always possible).
3. Some measurements, natively not end2end, became E2E (e.g. packet loss Q-=
bit) 4. It's possible to set alarm thresholds on the user device (and to si=
gnal to network probes to monitor only the sessions with impairments, in or=
der to segment the performance measurements and to locate the faults). In t=
his case observers, also embedded into network nodes, need to monitor only =
a limited number of connections (the ones that have problems).
=A0
Of course, to do this, the decision whether to activate the marking=A0(e.g.=
 Spin Bit) or not=A0must be made by=A0the device owner configuring the=A0ap=
plications (e.g. browsers) based on protocols that supports Explicit Perfor=
mance Monitoring (e.g. QUIC).
=A0
All applications should therefore provide for the activation or deactivatio=
n of the marking for the Explicit Performance Monitoring.
=A0
So, from this point of view, in the Client-Server handshake it should be th=
e Client who decides whether the marking is active or not within a session =
and the Server should adapt.
=A0
The performance information thus obtained could then be kept on the user de=
vice or sent to "external bodies" according to the will of the device owner=
..
The main recipient would be the Internet Service Provider (see point 4 of t=
he previous list), but these data could also be of interest to the national=
 regulatory authorities and perhaps others.
=A0
Feedbacks are welcomed.
Best regards.
=A0
Mauro

* Explicit packet loss measurements proposals:
1) https://tools.ietf.org/html/draft-cfb-ippm-spinbit-measurements-02
2) https://tools.ietf.org/html/draft-ferrieuxhamchaoui-quic-lossbits-03

=A0
_____________________
Mauro Cociglio
Telecom Italia-TIM
Via G. Reiss Romoli, 274
10148 - Torino (Italy)
Tel.: +390112285028
Mobile: +393357669751
_____________________
=A0


Questo messaggio e i suoi allegati sono indirizzati esclusivamente alle per=
sone indicate. La diffusione, copia o qualsiasi altra azione derivante dall=
a conoscenza di queste informazioni sono rigorosamente vietate. Qualora abb=
iate ricevuto questo documento per errore siete cortesemente pregati di dar=
ne immediata comunicazione al mittente e di provvedere alla sua distruzione=
, Grazie.=20

This e-mail and any attachments is confidential and may contain privileged =
information intended for the addressee(s) only. Dissemination, copying, pri=
nting or use by anybody else is unauthorised. If you are not the intended r=
ecipient, please delete this message and any attachments and advise the sen=
der by return e-mail, Thanks.=20

Rispetta l'ambiente. Non stampare questa mail se non =E8 necessario.

_______________________________________________
ippm mailing list
ippm@ietf.org
https://www.ietf.org/mailman/listinfo/ippm


From nobody Wed Jul 15 03:28:59 2020
Return-Path: <tim.jebb@bt.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0BC8A3A09B1 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 03:28:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=bt.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 IjOXNIQTFMEF for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 03:28:56 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [213.121.35.71]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 634803A09AC for <quic@ietf.org>; Wed, 15 Jul 2020 03:28:55 -0700 (PDT)
Received: from tpw09926dag15h.domain1.systemhost.net (10.9.212.39) by BWP09926076.bt.com (10.36.82.107) with Microsoft SMTP Server (version=TLS1_2,  cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Wed, 15 Jul 2020 11:28:43 +0100
Received: from tpw09926dag14h.domain1.systemhost.net (10.9.212.38) by tpw09926dag15h.domain1.systemhost.net (10.9.212.39) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 15 Jul 2020 11:28:50 +0100
Received: from bwp09926084.bt.com (10.36.82.115) by tpw09926dag14h.domain1.systemhost.net (10.9.212.38) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 15 Jul 2020 11:28:50 +0100
Received: from GBR01-CWL-obe.outbound.protection.outlook.com (104.47.20.57) by smtpe1.intersmtp.com (10.36.82.115) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Wed, 15 Jul 2020 11:28:47 +0100
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=fEPe96y7+xfxiqBBFlzYwHWy/NRu9k4weljyN2y7LQXa08o56XF8DJ3iooqtY8Z45tuh4bPT3/EBS8iJLUQVlCv0Di05gZdsxdIgciO0na96hJX2oIfwDEz7e8X2gJPa8ZnwopbQao+W6r5LdcZocCqZpNZ1qPfQitnih8amAvPwJdpky6HnWAcfhKMfVHY62IsyXpnkvyXHpxBYr0QaZctXb6xrQprSjFwX2r+w+gU0PvgdUfBOI+Y06FmiLoS3bFY3ujj+srY99hP4yxALW3B2TM2A53xawpEF9gP7dbUIcauRXNC61StAtFWhhrA8Lqhu/aIfqgkidEqEuRikJw==
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=UFPk6127I2rEk1cwfq/pScu5ZjLAQbTouekLwXWLSJo=; b=PxwbgjXKVAyjXgaBSC3y79XOGusujRXH4E9sgKBAKQpetdC27bxPcNkheoTpZ5dUZmT2wUWG3vIwdiMhorgDAB6bglEdbTNqtyIT77Y7CKmuwL4JNxYoQGiOMuDw+Ax2/1q1tLaMU2meP8Nsdac1QKCaTcqTSRqytCHBNeoP7DnEkletdAVvFkqM7OgESuuxdshnUEFfwyQ9loxyqU31FcaLIt6ix4xCfEhzgFSCkU03KoGd4vfw5pxmZ6wtMAw3phZzzPRT1sdvHdAwieQ+gXFN/cmPzsJgmK3X0CMCrTjko75IvPK7NzIO6YuTd4kWx4pVBtC02TfH4LP8HK7Kng==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=bt.com; dmarc=pass action=none header.from=bt.com; dkim=pass header.d=bt.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bt.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=UFPk6127I2rEk1cwfq/pScu5ZjLAQbTouekLwXWLSJo=; b=p9gZv+2xL2p5tHBC98BcGVZ9ino79O8rhPjuyVbyT/lC+AaozR3dAsPzen+CG4q8vfWtGxNAsLrskVyduuAn2in1k+06VUBl27QsiUl24EiMPfTyQEkNngkqzkEeqwH2QTnhNzMQlj4aUO4oS0GIr7iJdJvVLn3rBqxaSVKuDaY=
Received: from LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:dc::10) by LO2P123MB2096.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:c4::13) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3174.20; Wed, 15 Jul 2020 10:28:49 +0000
Received: from LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM ([fe80::ec07:dcb5:1747:4632]) by LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM ([fe80::ec07:dcb5:1747:4632%7]) with mapi id 15.20.3174.026; Wed, 15 Jul 2020 10:28:49 +0000
From: <tim.jebb@bt.com>
To: <nharper@google.com>
CC: <quic@ietf.org>
Subject: RE: Problems verifying sample packet protection in appendix A of Using TLS to Secure QUIC
Thread-Topic: Problems verifying sample packet protection in appendix A of Using TLS to Secure QUIC
Thread-Index: AdZZ60hBgJSiLWoSRDqZxGYKUQVBHwAI+HGAACDP13A=
Date: Wed, 15 Jul 2020 10:28:49 +0000
Message-ID: <LNXP123MB246078C4CFAC7701FF212057F27E0@LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM>
References: <LNXP123MB2460833EC5BC592C8D410EDCF2610@LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM> <CACdeXi+EUWRGoT7pWrqnEbQK9EoT0ERr7pKFmtOQ3pQZc9wfCw@mail.gmail.com>
In-Reply-To: <CACdeXi+EUWRGoT7pWrqnEbQK9EoT0ERr7pKFmtOQ3pQZc9wfCw@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: google.com; dkim=none (message not signed) header.d=none;google.com; dmarc=none action=none header.from=bt.com;
x-originating-ip: [46.208.134.198]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 9b58a089-d5f3-4ecd-1531-08d828a9dcee
x-ms-traffictypediagnostic: LO2P123MB2096:
x-microsoft-antispam-prvs: <LO2P123MB20966A59B3A90E48B89D11A8F27E0@LO2P123MB2096.GBRP123.PROD.OUTLOOK.COM>
x-antispam-2: 1
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: lkLBdGiFbRaW5D8hS4LowdGXHc6D/oo6SEaDZKT0KqIjj8wKxkzUKYTK50/C/qZTDwj2Jk+Lm66c3ZdEhKldY0sBO18q4danwFItTRGq/d0MC/5O1FpwWIlbuoixh5Vn4yTEc0fAeMHB29zb8ejb7QXJqBXybgFx2f4aYdMRJN5qBtqDM5LRtcqtpYuDmp6/vbgiE8BLgsux3IlpOVhz8g044U1vaXsmPtpWjPRXmRiZyxndDbO9+q+7n1s3Tni7RUOWLq6ihs8iP/5RrwZDLB4dwJDM1pTEJ/SxG4WG3bhrHKmgD6g++gArELSABna/getPFEHjwVWhHZb8OhWGHs7JcWKyCS17D6E3LhYecXqvOHZ84AkABlq+CTO1WY/VH/oSZyxs0BqEYqKaF5e2bg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(346002)(39860400002)(376002)(396003)(366004)(136003)(2906002)(6916009)(8936002)(478600001)(66446008)(66556008)(86362001)(966005)(33656002)(6506007)(5660300002)(8676002)(64756008)(186003)(4326008)(53546011)(83380400001)(52536014)(316002)(15650500001)(9686003)(166002)(55016002)(76116006)(26005)(7696005)(16799955002)(66476007)(66946007)(71200400001); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: OHOWFK3pdRhW/+0evN7Fxt9r92p96ltoV5Xi43TE0k/3IxTbOmfDD4Ax/aplxd3hHB4jTmzhss2S9zwbhpbCKksj/f7vplgv8s1PChVeFk6tLsDQZUDCSDVpFXRqGNMO2w+FL84M+GrB6b9LxzJCdfHkUTftkVXxae105rwhdx7cHCeltSqebEmrUwSSwat1KoM/vflUtA7xXMKIFKqEA1zIHdSAVKmiOrAgB+uKooyUbimomAKdcOlBn/xg2vTAaOseuk+vdFu1ALhVh2F3gT79Yr50k2L8x76GutlY1kXp5bUPwU1huoysed9FxXll4fbmp3ZT1MyzGug2j52u+OWK/BZN7x6BNGIH/sB6mxpD2oMWhy5NlB8DbHVk/KiHNMxp42m2SC3qZP3GV/EzvM0i6SfWlfXfmGiErmvzAkqh/UJaT2+B2fo///+t6NqGls+JoeMsYTdL4uw+b/FZyq1EUCDMyTIeJsGI2Iu/hMMrzkNll6dJunv8EuK2hkyQ
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_LNXP123MB246078C4CFAC7701FF212057F27E0LNXP123MB2460GBRP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 9b58a089-d5f3-4ecd-1531-08d828a9dcee
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Jul 2020 10:28:49.3120 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a7f35688-9c00-4d5e-ba41-29f146377ab0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: Co3LtyUkyggjYI3xjjpH+Lv1rfcMx/ojMaxH/HbkHpYuFC8WHC1GPbCfJNlo24ub
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LO2P123MB2096
X-OriginatorOrg: bt.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/yulsMvm_XRW-lXa5Pq5wqJc4PO8>
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, 15 Jul 2020 10:28:58 -0000

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

VGhhbmtzIGZvciB0aGF0IE5pY2ssIHZlcnkgaGVscGZ1bCwgZXZlbiBiZXR0ZXIgbXkgY29kZSBp
cyBub3cgd29ya2luZyDwn5iKDQoNCg0KDQpGcm9tOiBOaWNrIEhhcnBlciA8bmhhcnBlckBnb29n
bGUuY29tPg0KU2VudDogMTQgSnVseSAyMDIwIDE5OjQ3DQpUbzogSmViYixUUixUaW0sVklFIFIg
PHRpbS5qZWJiQGJ0LmNvbT4NCkNjOiBJRVRGIFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc+DQpTdWJq
ZWN0OiBSZTogUHJvYmxlbXMgdmVyaWZ5aW5nIHNhbXBsZSBwYWNrZXQgcHJvdGVjdGlvbiBpbiBh
cHBlbmRpeCBBIG9mIFVzaW5nIFRMUyB0byBTZWN1cmUgUVVJQw0KDQoNCg0KT24gVHVlLCBKdWwg
MTQsIDIwMjAgYXQgOTowNiBBTSA8dGltLmplYmJAYnQuY29tPG1haWx0bzp0aW0uamViYkBidC5j
b20+PiB3cm90ZToNCkhpLA0KDQpJ4oCZbSB3b3JraW5nIHRocm91Z2ggQXBwZW5kaXggQSBvZiB0
aGUgUVVJQyBUTFMgZG9jIHRvIGNoZWNrIG15IHVuZGVyc3RhbmRpbmcsIGJ1dCBhbSBoYXZpbmcg
dHJvdWJsZSBkZWNyeXB0aW5nIHRoZSBzYW1wbGUgY2xpZW50IGluaXRpYWwgcGFja2V0LiAgSeKA
mW0gdW5zdXJlIGlmIEnigJl2ZSBtYWRlIGEgc2lsbHkgZXJyb3Igb3IgdHdvLCBvciBpZiBJ4oCZ
dmUgbWFkZSBvbmUgb3IgbW9yZSBpbmNvcnJlY3QgYXNzdW1wdGlvbnMuICBPciBib3RoLg0KDQpU
aGUgZnVuY3Rpb25zIEnigJltIHVzaW5nIGFyZSB0aGUgT3BlblNTTCBFVlAgb25lcy4gIEnigJlt
IGF0dGVtcHRpbmcgdG8gZm9sbG93IHRoZSByZWNpcGUgaGVyZToNCmh0dHBzOi8vd2lraS5vcGVu
c3NsLm9yZy9pbmRleC5waHAvRVZQX0F1dGhlbnRpY2F0ZWRfRW5jcnlwdGlvbl9hbmRfRGVjcnlw
dGlvbiNBdXRoZW50aWNhdGVkX0RlY3J5cHRpb25fdXNpbmdfR0NNX21vZGUgaW4gY29uanVuY3Rp
b24gd2l0aCB0aGUgZHJhZnQgUkZDLg0KDQoNCkVWUF9DSVBIRVJfQ1RYX25ldygpDQoNCkVWUF9E
ZWNyeXB0SW5pdF9leChjdHgsIEVWUF9hZXNfMTI4X2djbSgpLCBOVUxMLCBOVUxMLCBOVUxMKQ0K
DQpFVlBfRGVjcnlwdEluaXRfZXgoY3R4LCBOVUxMLCBOVUxMLCBjbGllbnRfa2V5LCBpdikgICAg
ICAgICB3aGVyZSB0aGUgY2xpZW50IGtleSBpcyAweDE3NTI1N2EzMWViMDlkZWE5MzY2ZDhiYjc5
YWQ4MGJhIGFuZCB0aGUgaXYgaXMgMHg2YjI2MTE0YjljYmEyYjYzYTllOGRkNGYNCg0KWW91IG5l
ZWQgdG8gY29tcHV0ZSB0aGUgbm9uY2UgZnJvbSB0aGUgSVYgYW5kIHRoZSBwYWNrZXQgbnVtYmVy
LiBJIGFzc3VtZSB3aGF0IHRoZSBvcGVuc3NsIGRvY3VtZW50YXRpb24gcmVmZXJzIHRvIGFzIGFu
IElWIGlzIGFjdHVhbGx5IHRoZSBub25jZSBhcyBkZXNjcmliZWQgaW4gUkZDIDUxMTYuDQoNCkVW
UF9EZWNyeXB0VXBkYXRlKGN0eCwgTlVMTCwgJmxlbiwgcFVucHJvdGVjdGVkSGVhZGVyLCBoZWFk
ZXJMZW5ndGgpICAgICAgICAgICB3aGVyZSB0aGUgdW5wcm90ZWN0ZWQgaGVhZGVyIGlzIDB4YzNm
ZjAwMDAxZDA4ODM5NGM4ZjAzZTUxNTcwODAwMDA0NDllMDAwMDAwMDIg4oCTIHRoaXMgSSBiZWxp
ZXZlIGlzIHRoZSBBZGRpdGlvbmFsIERhdGEgcmVxdWlyZWQNCg0KRVZQX0RlY3J5cHRVcGRhdGUo
Y3R4LCBkZWNyeXB0ZWRQYXlsb2FkLCAmbGVuLCBwUGF5bG9hZCwgcGF5bG9hZExlbmd0aC0xNikp
ICAgaGVyZSBJ4oCZbSBwYXNzaW5nIGluIHRoZSBlbmNyeXB0ZWQgcGF5bG9hZCBiZWdpbm5pbmcg
MHhmYjY2YmM1ZiBhbmQgZW5kaW5nIDB4ZTgyYTRkOTE5ZDQ4LCBsZW5ndGggMTE2Mi4gIEnigJlt
IGFzc3VtaW5nIHRoYXQgdGhlIGZpbmFsIDE2IGJ5dGVzIG9mIHRoZSBwYXlsb2FkIGlzIHRoZSBh
dXRoZW50aWNhdGlvbiB0YWcgc28gYW0gbm90IHBhc3NpbmcgaXQgaW4gaGVyZS4gIE5vdGUgdGhh
dCBpZiB0aGlzIGFzc3VtcHRpb24gYWJvdXQgdGhlIGF1dGhlbnRpY2F0aW9uIHRhZyBpcyBjb3Jy
ZWN0LCBJIHRoaW5rIGl0IGNvdWxkIGJlIG1vcmUgY2xlYXJseSBzdGF0ZWQgaW4gdGhlIGRyYWZ0
IFJGQy4NCg0KVGhpcyBpcyBhIHF1aXJrIG9mIHRoZSBvcGVuc3NsIEFQSSB1bmZvcnR1bmF0ZWx5
LiBBbiBBRUFEIGRlY3J5cHRpb24gb3BlcmF0aW9uIHNob3VsZCB0YWtlIDQgaW5wdXRzOiB0aGUg
a2V5LCB0aGUgbm9uY2UsIHRoZSBhc3NvY2lhdGVkIGRhdGEsIGFuZCB0aGUgY2lwaGVydGV4dC4g
VGhlIGNpcGhlcnRleHQsIGFzIGRlZmluZWQgYnkgUkZDIDUxMTYsIGluY2x1ZGVzIHRoZSB0YWcu
IFRoZXJlJ3Mgbm8gcmVxdWlyZW1lbnQgb24gdGhlIHN0cnVjdHVyZSBvZiBhbiBBRUFEJ3MgY2lw
aGVydGV4dCwgaW5jbHVkaW5nIHRoYXQgc29tZSBwb3J0aW9uIG9mIHRoZSBjaXBoZXJ0ZXh0IGJl
IGFibGUgdG8gYmUgaWRlbnRpZmllZCBhcyBhIHRhZy4gQUVTLUdDTSBkb2VzIGhhdmUgdGhpcyBz
dHJ1Y3R1cmUgd2hlcmUgdGhlIHRhZyBpcyBhdCB0aGUgZW5kIG9mIHRoZSBjaXBoZXJ0ZXh0LCBh
bmQgdW5mb3J0dW5hdGVseSBvcGVuc3NsIG1ha2VzIHRoYXQgcGFydCBvZiB0aGUgYXBpIGZvciB0
aGUgQUVBRCBvcGVuIG9wZXJhdGlvbiwgZXZlbiB0aG91Z2ggc29tZW9uZSB1c2luZyBpdCBzaG91
bGQgbmV2ZXIgaGF2ZSB0byBrbm93IHRoYXQgZGV0YWlsIG9mIHRoZSBBRVMtR0NNIGFsZ29yaXRo
bS4NCg0KRVZQX0NJUEhFUl9DVFhfY3RybChjdHgsIEVWUF9DVFJMX0dDTV9TRVRfVEFHLCAxNiwg
dGFnKSB3aGVyZSB0YWcgaXMgdGhlIGZpbmFsIDE2IGJ5dGVzIG9mIHRoZSBlbmNyeXB0ZWQgcGF5
bG9hZCwgaWUgMHg0M2IxY2E3MCBhMmQ4ZDNmNyAyNWVhZDEzOSAxMzc3ZGNjMA0KDQpFVlBfRGVj
cnlwdEZpbmFsX2V4KGN0eCwgZGVjcnlwdGVkUGF5bG9hZCArIGxlbiwgJmxlbikNCg0KRXZlcnl0
aGluZyBzZWVtcyBPSyB1bnRpbCB0aGUgRVZQX0RlY3J5cHRGaW5hbF9leCgpIGNhbGwgd2hpY2gg
ZmFpbHMuDQoNCklzIHRoZXJlIGFueXRoaW5nIG9idmlvdXNseSB3cm9uZyB3aXRoIHRoZSBhYm92
ZT8gIEnigJl2ZSBub3QgcG9zdGVkIHRoZSBmdWxsIHNvdXJjZSBjb2RlIGFzIEnigJltIG5vdCBh
c2tpbmcgcGVvcGxlIHRvIGNoZWNrIG15IHdvcmtpbmcsIEnigJltIHJlYWxseSBhc2tpbmcgaWYg
bXkgYXNzdW1wdGlvbnMgYXJlIGNvcnJlY3QsIGFtIEkgdXNpbmcgdGhlIGNvcnJlY3QgZnVuY3Rp
b25zLCBpbnB1dCBkYXRhIGV0Yy4NCg0KVGhhbmtzIGluIGFkdmFuY2UNCg0KVGltDQo=

--_000_LNXP123MB246078C4CFAC7701FF212057F27E0LNXP123MB2460GBRP_
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
NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0K
ZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1b
aWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1h
eD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0K
PG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9
IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9k
eSBsYW5nPSJFTi1HQiIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJX
b3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJl
YXN0LWxhbmd1YWdlOkVOLVVTIj5UaGFua3MgZm9yIHRoYXQgTmljaywgdmVyeSBoZWxwZnVsLCBl
dmVuIGJldHRlciBteSBjb2RlIGlzIG5vdyB3b3JraW5nDQo8L3NwYW4+PHNwYW4gc3R5bGU9ImZv
bnQtZmFtaWx5OiZxdW90O1NlZ29lIFVJIEVtb2ppJnF1b3Q7LHNhbnMtc2VyaWY7bXNvLWZhcmVh
c3QtbGFuZ3VhZ2U6RU4tVVMiPiYjMTI4NTIyOzwvc3Bhbj48c3BhbiBzdHlsZT0ibXNvLWZhcmVh
c3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJz
cDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1z
by1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4t
VVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxi
PjxzcGFuIGxhbmc9IkVOLVVTIj5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiPiBO
aWNrIEhhcnBlciAmbHQ7bmhhcnBlckBnb29nbGUuY29tJmd0Ow0KPGJyPg0KPGI+U2VudDo8L2I+
IDE0IEp1bHkgMjAyMCAxOTo0Nzxicj4NCjxiPlRvOjwvYj4gSmViYixUUixUaW0sVklFIFIgJmx0
O3RpbS5qZWJiQGJ0LmNvbSZndDs8YnI+DQo8Yj5DYzo8L2I+IElFVEYgUVVJQyBXRyAmbHQ7cXVp
Y0BpZXRmLm9yZyZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFByb2JsZW1zIHZlcmlmeWlu
ZyBzYW1wbGUgcGFja2V0IHByb3RlY3Rpb24gaW4gYXBwZW5kaXggQSBvZiBVc2luZyBUTFMgdG8g
U2VjdXJlIFFVSUM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48
bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBU
dWUsIEp1bCAxNCwgMjAyMCBhdCA5OjA2IEFNICZsdDs8YSBocmVmPSJtYWlsdG86dGltLmplYmJA
YnQuY29tIj50aW0uamViYkBidC5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICND
Q0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDtt
YXJnaW4tcmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5I
aSwNCjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+SeKAmW0gd29ya2luZyB0aHJvdWdoIEFw
cGVuZGl4IEEgb2YgdGhlIFFVSUMgVExTIGRvYyB0byBjaGVjayBteSB1bmRlcnN0YW5kaW5nLCBi
dXQgYW0gaGF2aW5nIHRyb3VibGUgZGVjcnlwdGluZyB0aGUgc2FtcGxlIGNsaWVudCBpbml0aWFs
IHBhY2tldC4mbmJzcDsgSeKAmW0gdW5zdXJlIGlmIEnigJl2ZSBtYWRlIGEgc2lsbHkNCiBlcnJv
ciBvciB0d28sIG9yIGlmIEnigJl2ZSBtYWRlIG9uZSBvciBtb3JlIGluY29ycmVjdCBhc3N1bXB0
aW9ucy4mbmJzcDsgT3IgYm90aC48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPlRoZSBmdW5j
dGlvbnMgSeKAmW0gdXNpbmcgYXJlIHRoZSBPcGVuU1NMIEVWUCBvbmVzLiZuYnNwOyBJ4oCZbSBh
dHRlbXB0aW5nIHRvIGZvbGxvdyB0aGUgcmVjaXBlIGhlcmU6PG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdp
bi1ib3R0b20tYWx0OmF1dG8iPjxhIGhyZWY9Imh0dHBzOi8vd2lraS5vcGVuc3NsLm9yZy9pbmRl
eC5waHAvRVZQX0F1dGhlbnRpY2F0ZWRfRW5jcnlwdGlvbl9hbmRfRGVjcnlwdGlvbiNBdXRoZW50
aWNhdGVkX0RlY3J5cHRpb25fdXNpbmdfR0NNX21vZGUiIHRhcmdldD0iX2JsYW5rIj5odHRwczov
L3dpa2kub3BlbnNzbC5vcmcvaW5kZXgucGhwL0VWUF9BdXRoZW50aWNhdGVkX0VuY3J5cHRpb25f
YW5kX0RlY3J5cHRpb24jQXV0aGVudGljYXRlZF9EZWNyeXB0aW9uX3VzaW5nX0dDTV9tb2RlPC9h
Pg0KIGluIGNvbmp1bmN0aW9uIHdpdGggdGhlIGRyYWZ0IFJGQy48bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFy
Z2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5F
VlBfQ0lQSEVSX0NUWF9uZXcoKTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+RVZQX0RlY3J5
cHRJbml0X2V4KGN0eCwgRVZQX2Flc18xMjhfZ2NtKCksIE5VTEwsIE5VTEwsIE5VTEwpPG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1t
YXJnaW4tYm90dG9tLWFsdDphdXRvIj5FVlBfRGVjcnlwdEluaXRfZXgoY3R4LCBOVUxMLCBOVUxM
LCBjbGllbnRfa2V5LCBpdikgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5i
c3A7IHdoZXJlIHRoZSBjbGllbnQga2V5IGlzIDB4MTc1MjU3YTMxZWIwOWRlYTkzNjZkOGJiNzlh
ZDgwYmEgYW5kIHRoZSBpdiBpcyAweDZiMjYxMTRiOWNiYTJiNjNhOWU4ZGQ0ZjxvOnA+PC9vOnA+
PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPllvdSBuZWVkIHRvIGNvbXB1dGUgdGhlIG5vbmNlIGZyb20gdGhlIElWIGFuZCB0
aGUgcGFja2V0IG51bWJlci4gSSBhc3N1bWUgd2hhdCB0aGUgb3BlbnNzbCBkb2N1bWVudGF0aW9u
IHJlZmVycyB0byBhcyBhbiBJViBpcyBhY3R1YWxseSB0aGUgbm9uY2UgYXMgZGVzY3JpYmVkIGlu
IFJGQyA1MTE2LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9y
ZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAwY20g
MGNtIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY20iPg0KPGRpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87
bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4t
Ym90dG9tLWFsdDphdXRvIj5FVlBfRGVjcnlwdFVwZGF0ZShjdHgsIE5VTEwsICZhbXA7bGVuLCBw
VW5wcm90ZWN0ZWRIZWFkZXIsIGhlYWRlckxlbmd0aCkmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsm
bmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsgd2hlcmUgdGhlIHVucHJvdGVjdGVk
IGhlYWRlciBpcyAweGMzZmYwMDAwMWQwODgzOTRjOGYwM2U1MTU3MDgwMDAwNDQ5ZTAwMDAwMDAy
IOKAkyB0aGlzIEkgYmVsaWV2ZSBpcw0KIHRoZSBBZGRpdGlvbmFsIERhdGEgcmVxdWlyZWQ8bzpw
PjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1h
bHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPkVWUF9EZWNyeXB0VXBkYXRlKGN0eCwgZGVjcnlwdGVk
UGF5bG9hZCwgJmFtcDtsZW4sIHBQYXlsb2FkLCBwYXlsb2FkTGVuZ3RoLTE2KSkmbmJzcDsmbmJz
cDsgaGVyZSBJ4oCZbSBwYXNzaW5nIGluIHRoZSBlbmNyeXB0ZWQgcGF5bG9hZCBiZWdpbm5pbmcg
MHhmYjY2YmM1ZiBhbmQgZW5kaW5nIDB4ZTgyYTRkOTE5ZDQ4LCBsZW5ndGggMTE2Mi4mbmJzcDsN
CiBJ4oCZbSBhc3N1bWluZyB0aGF0IHRoZSBmaW5hbCAxNiBieXRlcyBvZiB0aGUgcGF5bG9hZCBp
cyB0aGUgYXV0aGVudGljYXRpb24gdGFnIHNvIGFtIG5vdCBwYXNzaW5nIGl0IGluIGhlcmUuJm5i
c3A7IE5vdGUgdGhhdCBpZiB0aGlzIGFzc3VtcHRpb24gYWJvdXQgdGhlIGF1dGhlbnRpY2F0aW9u
IHRhZyBpcyBjb3JyZWN0LCBJIHRoaW5rIGl0IGNvdWxkIGJlIG1vcmUgY2xlYXJseSBzdGF0ZWQg
aW4gdGhlIGRyYWZ0IFJGQy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2Nr
cXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGlzIGlzIGEgcXVpcmsgb2Yg
dGhlIG9wZW5zc2wgQVBJIHVuZm9ydHVuYXRlbHkuIEFuIEFFQUQgZGVjcnlwdGlvbiBvcGVyYXRp
b24gc2hvdWxkIHRha2UgNCBpbnB1dHM6IHRoZSBrZXksIHRoZSBub25jZSwgdGhlIGFzc29jaWF0
ZWQgZGF0YSwgYW5kIHRoZSBjaXBoZXJ0ZXh0LiBUaGUgY2lwaGVydGV4dCwgYXMgZGVmaW5lZCBi
eSBSRkMgNTExNiwgaW5jbHVkZXMgdGhlIHRhZy4gVGhlcmUncyBubyByZXF1aXJlbWVudA0KIG9u
IHRoZSBzdHJ1Y3R1cmUgb2YgYW4gQUVBRCdzIGNpcGhlcnRleHQsIGluY2x1ZGluZyB0aGF0IHNv
bWUgcG9ydGlvbiBvZiB0aGUgY2lwaGVydGV4dCBiZSBhYmxlIHRvIGJlIGlkZW50aWZpZWQgYXMg
YSB0YWcuIEFFUy1HQ00gZG9lcyBoYXZlIHRoaXMgc3RydWN0dXJlIHdoZXJlIHRoZSB0YWcgaXMg
YXQgdGhlIGVuZCBvZiB0aGUgY2lwaGVydGV4dCwgYW5kIHVuZm9ydHVuYXRlbHkgb3BlbnNzbCBt
YWtlcyB0aGF0IHBhcnQgb2YgdGhlIGFwaQ0KIGZvciB0aGUgQUVBRCBvcGVuIG9wZXJhdGlvbiwg
ZXZlbiB0aG91Z2ggc29tZW9uZSB1c2luZyBpdCBzaG91bGQgbmV2ZXIgaGF2ZSB0byBrbm93IHRo
YXQgZGV0YWlsIG9mIHRoZSBBRVMtR0NNIGFsZ29yaXRobS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0ND
Q0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJn
aW4tcmlnaHQ6MGNtIj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJz
cDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+RVZQX0NJUEhFUl9DVFhf
Y3RybChjdHgsIEVWUF9DVFJMX0dDTV9TRVRfVEFHLCAxNiwgdGFnKSB3aGVyZSB0YWcgaXMgdGhl
IGZpbmFsIDE2IGJ5dGVzIG9mIHRoZSBlbmNyeXB0ZWQgcGF5bG9hZCwgaWUgMHg0M2IxY2E3MCBh
MmQ4ZDNmNyAyNWVhZDEzOSAxMzc3ZGNjMDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxl
PSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+RVZQ
X0RlY3J5cHRGaW5hbF9leChjdHgsIGRlY3J5cHRlZFBheWxvYWQgJiM0MzsgbGVuLCAmYW1wO2xl
bik8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286
cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1
dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPkV2ZXJ5dGhpbmcgc2VlbXMgT0sgdW50aWwg
dGhlIEVWUF9EZWNyeXB0RmluYWxfZXgoKSBjYWxsIHdoaWNoIGZhaWxzLjxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21z
by1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+SXMgdGhlcmUgYW55dGhpbmcgb2J2aW91c2x5IHdyb25nIHdpdGggdGhl
IGFib3ZlPyZuYnNwOyBJ4oCZdmUgbm90IHBvc3RlZCB0aGUgZnVsbCBzb3VyY2UgY29kZSBhcyBJ
4oCZbSBub3QgYXNraW5nIHBlb3BsZSB0byBjaGVjayBteSB3b3JraW5nLCBJ4oCZbSByZWFsbHkg
YXNraW5nIGlmIG15IGFzc3VtcHRpb25zIGFyZSBjb3JyZWN0LA0KIGFtIEkgdXNpbmcgdGhlIGNv
cnJlY3QgZnVuY3Rpb25zLCBpbnB1dCBkYXRhIGV0Yy48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJv
dHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPlRoYW5rcyBpbiBhZHZhbmNlPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5UaW08bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvZGl2
Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_LNXP123MB246078C4CFAC7701FF212057F27E0LNXP123MB2460GBRP_--


From nobody Wed Jul 15 04:54:19 2020
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 309A13A0C96 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 04:54:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 TjDZ7CgAcMIH for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 04:54:16 -0700 (PDT)
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 08B0F3A0C98 for <quic@ietf.org>; Wed, 15 Jul 2020 04:54:16 -0700 (PDT)
Received: by mail-lj1-x233.google.com with SMTP id h22so2214836lji.9 for <quic@ietf.org>; Wed, 15 Jul 2020 04:54:15 -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=jWO8cwVLfkhMpvWzkH7sGiyvYHAqebVOnFpu9Dqd2HM=; b=B3/6Kdw/IH1RskoUaa1erW+kwxKWlE+7mri3PWezTUN2s3MQtM7xqL6KK7mhOtD17s UhmSqGWJH0gTyrbOv5lOWFReidNgmeTAB3302OAS0HlLhFV9PeR9zZgff7zsrMuHcdhQ Zlq1jMIOLIgs6hhGLvsspfn5v9oeFLoysmiBOJNX/RlLX1i/iFKIJYuv4XqIO2UUIKaY UJhq89n01DamEgbMReMrYh1yyGY/yspS5KyRdzQ0o6njnACOG8mlTnPwFJY/hFw8XgXQ cD1ZJdX9KFdWSfngMwlRgDB97nHePk6c4xDguw+D1aS7b8dg0FOWsnnAln4TikBJuq1J ghsQ==
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=jWO8cwVLfkhMpvWzkH7sGiyvYHAqebVOnFpu9Dqd2HM=; b=bsxWS6HsyUpLa3k6Wwd6IUYzP4iL+/e5wHwyAsj7o9OtSlE9SN8gIFaM5yzJv/rZMS jCy+amlJ9/Czzlx5Xyi+aMI8WRUFgEAu5vxbgV4w0XCDLxGLCkljhL+ov7tyWTYDJ7Ul 73gV1kWVUU26PA28om1uNHezv+UCmKUeIMTS2aMF9FBauAf9ChnZY2LoRmuaNvEGeFe9 WXFCDCA38Cyz/ALXSqx6ryEhKjmNFNyR98Uw8eF2thxDFMq4C3waZSac5RgvbwYGsNkJ cUcDAgLTeZyJzNlPgFjMKUb9XlKVg1qz/GEZ3YnPXNoK8aglLpY1qkrYmqy0JSPsx3Os 4vvA==
X-Gm-Message-State: AOAM531JIMoat5e+z1yTakVMbRWhW6wzFxdtad+jt5niq2s1HoU24qsM 0GjXVyH3Mk8UdsWE9CQlZ4Ey4er9499f5mYoKEV0HPGkf2U=
X-Google-Smtp-Source: ABdhPJwlrDwUrAfRz48MGtlej8opCgW/FNh2tRJ1HWQzITQ350vQb5iPMMsnoFPdB39oh5YygbqIUVygrH9uq5CMhfc=
X-Received: by 2002:a2e:8707:: with SMTP id m7mr4441070lji.350.1594814054005;  Wed, 15 Jul 2020 04:54:14 -0700 (PDT)
MIME-Version: 1.0
References: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com>
In-Reply-To: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com>
From: Marten Seemann <martenseemann@gmail.com>
Date: Wed, 15 Jul 2020 18:54:02 +0700
Message-ID: <CAOYVs2o4PJmApJ=4BCNTW5agOJOgfvigyQSVhjvnWFCc_arHcQ@mail.gmail.com>
Subject: Re: Need your help: different connection IDs in the same datagram
To: Martin Thomson <mt@lowentropy.net>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002c02aa05aa799586"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/t8mK3nj16CkfvMCV8fBzOJscp28>
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, 15 Jul 2020 11:54:18 -0000

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

Let's have a look where this situation can occur:

During the early stages of the handshake it is not possible: The client
changes its connection ID used for Initial and 0-RTT packets as soon as it
receives a new connection ID provided by the server in a Retry or Initial
packet. The earliest time where a client could possibly coalesce packets
with different connection IDs is after receiving the Server Preferred
Address, and decides (for whatever reason) to not migrate to that address,
but to use that connection ID on the original path (and before the
handshake is confirmed).

The server needs to receive a NEW_CONNECTION_ID frame before it can change
connection IDs. The earliest this can happen is in a 0-RTT packet, so in
principle a server could start using that connection ID in its first flight.

I can see little reason to 1. start using a new connection ID during the
handshake and at the same time 2. to not completely switch to that
connection ID, but instead to continue using both at the same time.
To be clear, it isn't prohibited to use multiple connection IDs at the same
time (and on the same path), it's just that there's no good reason to do
so. I don't think it's too much of a burden to ask implementations that
still decide to do so to make sure that the connection IDs used in a
coalesced packet match, considering that for the receiver it's more
cumbersome to check that all connection IDs are actually valid for this
connection than to just validate that all packets use the same connection
ID.

On Wed, Jul 15, 2020 at 2:24 PM Martin Thomson <mt@lowentropy.net> wrote:

> https://github.com/quicwg/base-drafts/issues/3800 discovered a minor
> "discrepancy" in our requirements for coalescing packets.  We required that:
>
> * senders not coalesce packets for different connections in the same
> datagram.
>
> * receivers reject packets with different connection **IDs** in the same
> datagram.
>
> https://github.com/quicwg/base-drafts/pull/3870/files was the result of a
> discussion where I was convinced that looser constraints here weren't
> harmful.  The requirements would identify connections, not connection IDs.
>
> Originally, my inclination was to fix the requirement on the sender to use
> connection IDs, which would remove some linkability.  But then I was
> reminded that linkability is already defeated for several reasons.  You
> can't coalesce outside of the handshake and we require a stable path for
> the handshake AND long headers include a source connection ID that can be
> used for linkability.  So the linkability concern is basically lost.
>
> We also learned that some implementations were generating packets while
> processing incoming packets.  Later they would coalesce these into a
> datagram that might then have different connection IDs on the packets it
> contains.
>
> There has been some opposition to the proposed resolution in PR 3870.
>
> Apparently, for some, having multiple connection IDs in the same datagram
> complicates processing.  I don't understand this objection.  It seems to me
> more difficult to retain state across packets than it is to process each
> atomically.  I was hoping that Christian or Nick can explain more about how
> this affects them.
>
> Marten also indicated that there was a reason not to allow this, but if I
> understand that, this is based on some potential for future optimization,
> which could be conditional on having consistent connection IDs.  If we
> moved to a scheme that required consistent connection IDs, anyone using
> that scheme could be required to avoid coalescing different connection
> IDs.  So this seems more of a theoretical concern.
>
> And - in anticipation of maybe choosing to make senders use a consistent
> connection ID - if you might be generating coalesced datagrams with
> different connection IDs in packets, how hard would it be to ensure that
> these are consistent?  Lars and Ian, I think both of you indicated that you
> might do this.
>
>

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

<div dir=3D"ltr">Let&#39;s have a look where this situation can occur:<br><=
br>During the early stages of the handshake it is not possible: The client =
changes its connection ID used for Initial and 0-RTT packets as soon as it =
receives a new connection ID provided by the server in a Retry or Initial p=
acket. The earliest time where a client could possibly coalesce packets wit=
h different connection IDs is after receiving the Server Preferred Address,=
 and decides (for whatever reason) to not migrate to that address, but to u=
se that connection ID on the original path (and before the handshake is con=
firmed).<br><br>The server needs to receive a NEW_CONNECTION_ID frame befor=
e it can change connection IDs. The earliest this can happen is in a 0-RTT =
packet, so in principle a server could start using that connection ID in it=
s first flight.<br><br><div>I can see little reason to 1. start using a new=
 connection ID during the handshake and at the same time 2. to not complete=
ly switch to that connection ID, but instead to continue using both at the =
same time.</div><div>To be clear, it isn&#39;t prohibited to use multiple c=
onnection IDs at the same time (and on the same path), it&#39;s just that t=
here&#39;s no good reason to do so. I don&#39;t think it&#39;s too much of =
a burden to ask implementations that still decide to do so to make sure tha=
t the connection IDs used in a coalesced packet match, considering that for=
 the receiver it&#39;s more cumbersome to check that all connection IDs are=
 actually valid for this connection than to just validate that all packets =
use the same connection ID.</div></div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D"gmail_attr">On Wed, Jul 15, 2020 at 2:24 PM Martin Tho=
mson &lt;<a href=3D"mailto:mt@lowentropy.net">mt@lowentropy.net</a>&gt; wro=
te:<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"><a href=3D"h=
ttps://github.com/quicwg/base-drafts/issues/3800" rel=3D"noreferrer" target=
=3D"_blank">https://github.com/quicwg/base-drafts/issues/3800</a> discovere=
d a minor &quot;discrepancy&quot; in our requirements for coalescing packet=
s.=C2=A0 We required that:<br>
<br>
* senders not coalesce packets for different connections in the same datagr=
am.<br>
<br>
* receivers reject packets with different connection **IDs** in the same da=
tagram.<br>
<br>
<a href=3D"https://github.com/quicwg/base-drafts/pull/3870/files" rel=3D"no=
referrer" target=3D"_blank">https://github.com/quicwg/base-drafts/pull/3870=
/files</a> was the result of a discussion where I was convinced that looser=
 constraints here weren&#39;t harmful.=C2=A0 The requirements would identif=
y connections, not connection IDs.<br>
<br>
Originally, my inclination was to fix the requirement on the sender to use =
connection IDs, which would remove some linkability.=C2=A0 But then I was r=
eminded that linkability is already defeated for several reasons.=C2=A0 You=
 can&#39;t coalesce outside of the handshake and we require a stable path f=
or the handshake AND long headers include a source connection ID that can b=
e used for linkability.=C2=A0 So the linkability concern is basically lost.=
<br>
<br>
We also learned that some implementations were generating packets while pro=
cessing incoming packets.=C2=A0 Later they would coalesce these into a data=
gram that might then have different connection IDs on the packets it contai=
ns.<br>
<br>
There has been some opposition to the proposed resolution in PR 3870.=C2=A0=
 <br>
<br>
Apparently, for some, having multiple connection IDs in the same datagram c=
omplicates processing.=C2=A0 I don&#39;t understand this objection.=C2=A0 I=
t seems to me more difficult to retain state across packets than it is to p=
rocess each atomically.=C2=A0 I was hoping that Christian or Nick can expla=
in more about how this affects them.<br>
<br>
Marten also indicated that there was a reason not to allow this, but if I u=
nderstand that, this is based on some potential for future optimization, wh=
ich could be conditional on having consistent connection IDs.=C2=A0 If we m=
oved to a scheme that required consistent connection IDs, anyone using that=
 scheme could be required to avoid coalescing different connection IDs.=C2=
=A0 So this seems more of a theoretical concern.<br>
<br>
And - in anticipation of maybe choosing to make senders use a consistent co=
nnection ID - if you might be generating coalesced datagrams with different=
 connection IDs in packets, how hard would it be to ensure that these are c=
onsistent?=C2=A0 Lars and Ian, I think both of you indicated that you might=
 do this.<br>
<br>
</blockquote></div>

--0000000000002c02aa05aa799586--


From nobody Wed Jul 15 07:19:51 2020
Return-Path: <nibanks@microsoft.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 31D183A0C13 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 07:19:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, 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=microsoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3nRhw31ujfrU for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 07:19:48 -0700 (PDT)
Received: from NAM06-BL2-obe.outbound.protection.outlook.com (mail-eopbgr650125.outbound.protection.outlook.com [40.107.65.125]) (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 853E73A0C3A for <quic@ietf.org>; Wed, 15 Jul 2020 07:19:43 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=PLl3giwA3u192hp9EkwKFMU9M0/47X9qdnbTtfapYIm+kP8Njr+SiHU3MAzTsUYPpxxMTHhH2JmK3sh4/nZ5JGvLmTFh/MoSKx1vMLER2fok/Q3mpPiRHHS4czI5B+cBv7d3CYtnVG5GP0dVlTlyRFeQVAH0Z3FLMS7aHnSfRVTHnuIZrsnnTdL94y8aw8F8RK3YqYzbigI+r3mKOMg658llAHJHREZC8DwjBG7a/puRbmgITlZsDUxBmE6EpxuLWsGYhop252c/bU4xdJ/Z9zIYybSaip26zNMYFetO4EmXFFtJvqw4c+NzXBDwSbrER0QIvw+iQbaMkqEwAzwWig==
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=on2diSG9/0qFMigWg3c1+RTMUhwTucpsytVOt3apZaI=; b=ayI5Jce019aUihlRId9YONH2hpFgtsQwe9b1qxT0ikN05pFlrwZGUwYQTXqlIc01UTugG8kn6CObPDRUnDEVFwMXAhJGtsq8cO+7o48p/bEm3Wm9D7Hi48lg6YH2dII0CdxxuzplIqiRApeWHG1Opzudnlf5P25MK88VLJ72LycoKDhSc59HZvXpcjWw8qXiEEULPeFlUT1xeYa/K3Bgjnu52yfVBWn51f3zVDwjRrq9ZLSOL7BHLzPsi6G7FWMXPRc/AEoBUzbDb7GCdu5KLgJjRfQ11a8+LYX0/hG8GzZ5iuCtWnc5icTKCf2iWVX/IsH1tjEFGljySERKH3N6hA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=on2diSG9/0qFMigWg3c1+RTMUhwTucpsytVOt3apZaI=; b=OhQxPt/PWznMziojhwGuKCgApYu9fEB2vjE0vl9zaSOaUh7+2DcSvofNvJXraoRK/OWzh4UjTNTMHVFkpgLkp5aWklesXtkB5JMw+4TDTRmSyJCGppUT6Oe0ptDXtQexdk2ILoett+4atnrwZMSJwy7luyzrGARPbjpS1PQv5S0=
Received: from DM6PR00MB0767.namprd00.prod.outlook.com (2603:10b6:5:1bc::8) by DM6PR00MB0798.namprd00.prod.outlook.com (2603:10b6:5:20c::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3235.0; Wed, 15 Jul 2020 14:19:38 +0000
Received: from DM6PR00MB0767.namprd00.prod.outlook.com ([fe80::8cde:b3eb:6722:d9f9]) by DM6PR00MB0767.namprd00.prod.outlook.com ([fe80::8cde:b3eb:6722:d9f9%9]) with mapi id 15.20.3236.000; Wed, 15 Jul 2020 14:19:38 +0000
From: Nick Banks <nibanks@microsoft.com>
To: Marten Seemann <martenseemann@gmail.com>, Martin Thomson <mt@lowentropy.net>
CC: QUIC WG <quic@ietf.org>
Subject: RE: Need your help: different connection IDs in the same datagram
Thread-Topic: Need your help: different connection IDs in the same datagram
Thread-Index: AQHWWnj9jl+t0ZAZWEqMGonzhdFIe6kIiFEAgAAlyxA=
Date: Wed, 15 Jul 2020 14:19:38 +0000
Message-ID: <DM6PR00MB07671C4366474017F18BC3D8B37E0@DM6PR00MB0767.namprd00.prod.outlook.com>
References: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com> <CAOYVs2o4PJmApJ=4BCNTW5agOJOgfvigyQSVhjvnWFCc_arHcQ@mail.gmail.com>
In-Reply-To: <CAOYVs2o4PJmApJ=4BCNTW5agOJOgfvigyQSVhjvnWFCc_arHcQ@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=true; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2020-07-15T14:19:31Z;  MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=8d37d2af-4592-42b9-aa11-8b90a8dd298c; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [66.235.1.136]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 0f0989ba-d62c-4650-2dd4-08d828ca1b73
x-ms-traffictypediagnostic: DM6PR00MB0798:
x-microsoft-antispam-prvs: <DM6PR00MB079895BB6BA3B3FD252D6CC9B37E0@DM6PR00MB0798.namprd00.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 2jP5Ve99873MtaJzX5fp1d9gMLaB8fOiRI3OZmXMlJOkAARhszrn+90e7OdMD7yB06PCS73pwXbHM2DP1+QfFanpsX1KPzl+fGig/tF+mwVerS5iVUUCTsjUon95bQqSB78/yNr0MsT0puBgYPlKF2OtXfpskjaSc+iyr7yPb58qCi22K92IMC0+SmuQTNWk8kqWiOh38lFqeiXNkPFtbndnxqwRS0UjDV3Y0S1YjIragLosCVE31y3ICNa16DUOT1cBwH7PMj2PDgip/ZbKRUW6QokbV2FCy3SvNN9qEhluA/Qx+vdUJr0SIYogXqRiifxm0iI82vObXTH8lj9S4YsUv2AI//sPC7jiE0w+DstCT/ZlupUucpEfjsXjRlDJEPZkoW1gTmlLiIXRuDNlLQvkoQcrV9YMLjji+YzvoO7cwTuMRMUcr0YWwauyoGR1wEH9OOKihiCMDfJoBhhgzQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:DM6PR00MB0767.namprd00.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(39860400002)(136003)(376002)(366004)(346002)(396003)(5660300002)(71200400001)(26005)(10290500003)(186003)(110136005)(316002)(86362001)(166002)(966005)(478600001)(55016002)(2906002)(66946007)(83380400001)(66446008)(64756008)(66476007)(66556008)(6506007)(53546011)(7696005)(52536014)(76116006)(9686003)(8936002)(33656002)(8676002)(4326008)(8990500004)(82950400001)(82960400001)(151803002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: US7aKv+IKH/4alEb7575db++J+tuIEcehirvu96FcKQ2d1QDtl/zWQ1fNJsPdbFoVtjYHi3kRQQjibdW870n8vlumQhMOZurng3YGwFJWRO+k5WaAgm3tFNGaSG/AoOQ2k/7DudLsYEKcsZLrdpdYxzynKTAUcq3wpl+vagT5HbTJXgdsvqr2j0KpNVEZL/0eTBcAtHA2HnMP5unHr9odAHzcOVEMhbJHKfSy9tlqvG4YcH1Y+mdY9wQVPkLhtvHr3mdrRJu0H+nIEbgqc67lWpBd9HtTjA2onC6ZxAIU8yNYkA+M3Y7MozCyiWoZD9IGzMlQPaDWwDSDamCfrS2nrDqoWCzdQJahYs4U7xq175j4XHTAVgngiUX0Ue33nkJt5MCJufPImgmGE0rv31jPnk46L9gg2pUO4CTHtj0uzZhjQuRUXYUIjKTpBukOFdolebssiotZyZXe7qWfCxeaVnmalAts6UiAtFNUxYUTTjLhLy7B5xgZkinkj+zA1w/m/8PGZXF5Y54+oHLto7mHyaLyYZgSalXrhXniKNd8ny2kAn07YY4M42ljPalu5g1nOQjIFGphrxibVDMxg1B7cFq6DRdFguvXU5oKx6Etbnur8sqBRXo6FPw+oNAMxgEgPrYXvyoJOkv0absq641Zw==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_DM6PR00MB07671C4366474017F18BC3D8B37E0DM6PR00MB0767namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: DM6PR00MB0767.namprd00.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 0f0989ba-d62c-4650-2dd4-08d828ca1b73
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Jul 2020 14:19:38.1515 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: YhaSQ1vBspyj2lOp0vYB/xq0DoZKTROkiHV4ys8JDPtT+xJWjxvO6z00hEldzImjPvAgv33UgsHNDXqAZdy9JA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: DM6PR00MB0798
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/NhB-rBzsN0t9ArvyrHc0_TgXB8I>
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, 15 Jul 2020 14:19:50 -0000

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

R2VuZXJhbGx5LCBJIGFncmVlIHdpdGggTWFydGVu4oCZcyBjb21tZW50cyB0aGF0IHRoYXQgdGhl
cmUgaXMgbGl0dGxlIHJlYXNvbiB0byB1c2UgbXVsdGlwbGUgY29ubmVjdGlvbnMgSURzIGluIHRo
ZSBzYW1lIGRhdGFncmFtLiBTcGVjaWZpY2FsbHksIGZvciBvdXIgaW1wbGVtZW50YXRpb24sIE1z
UXVpYywgdmFsaWRhdGluZyB0aGUgY29ubmVjdGlvbiBJRCBpbiBlYWNoIHBhY2tldCBpcyBtdWNo
IHNpbXBsZXIgaWYgdGhleeKAmXJlIGFsbCB0aGUgc2FtZS47IG91ciBVRFAgZGF0YWdyYW0gY29u
dGV4dCBzdHJ1Y3R1cmUgaG9sZHMgYSBwb2ludGVyIHRvIHRoZSBmaXJzdCBjb25uZWN0aW9uIElE
IGluIHRoZSBkYXRhZ3JhbSwgc28gYWxsIHRoYXQgbmVlZHMgdG8gYmUgZG9uZSAoZm9yIGVhY2gg
UVVJQyBwYWNrZXQpIGlzIGNvbXBhcmUgdGhlIGN1cnJlbnQgUVVJQyBwYWNrZXTigJlzIGNvbm5l
Y3Rpb24gSUQgdG8gdGhhdCBwb2ludGVyLiBUaGUgbG9naWMgcmVxdWlyZXMgbm8gYWRkaXRpb25h
bCBjb25uZWN0aW9uIHN0YXRlLiBJZiB3ZSBhbGxvd2VkIGFueSBjb25uZWN0aW9uIElEIHRoYXTi
gJlzIHZhbGlkIGZvciB0aGUgY29ubmVjdGlvbiwgdGhlbiB3ZeKAmWQgaGF2ZSB0byBnbyB0byB0
aGUgY29ubmVjdGlvbiBvYmplY3QgYW5kIGRvIGEgbG9va3VwIGVhY2ggdGltZSBpbnN0ZWFkLiBJ
dOKAmXMgZGVmaW5pdGVseSBwb3NzaWJsZSB0byBkbywgYnV0IHJlcXVpcmVzIGEgYml0IG1vcmUg
d29yayAoQ1BVKSBhbmQgc3luY2hyb25pemF0aW9uIG9mIHN0YXRlLiBGb3IgdGhvc2UgcmVhc29u
cywgSeKAmWQgcHJlZmVyIHRvIGtlZXAgdGhlIGNvbm5lY3Rpb24gSURzIGNvbnNpc3RlbnQuDQoN
ClRoYW5rcywNCi0gTmljaw0KDQpGcm9tOiBRVUlDIDxxdWljLWJvdW5jZXNAaWV0Zi5vcmc+IE9u
IEJlaGFsZiBPZiBNYXJ0ZW4gU2VlbWFubg0KU2VudDogV2VkbmVzZGF5LCBKdWx5IDE1LCAyMDIw
IDQ6NTQgQU0NClRvOiBNYXJ0aW4gVGhvbXNvbiA8bXRAbG93ZW50cm9weS5uZXQ+DQpDYzogUVVJ
QyBXRyA8cXVpY0BpZXRmLm9yZz4NClN1YmplY3Q6IFJlOiBOZWVkIHlvdXIgaGVscDogZGlmZmVy
ZW50IGNvbm5lY3Rpb24gSURzIGluIHRoZSBzYW1lIGRhdGFncmFtDQoNCkxldCdzIGhhdmUgYSBs
b29rIHdoZXJlIHRoaXMgc2l0dWF0aW9uIGNhbiBvY2N1cjoNCg0KRHVyaW5nIHRoZSBlYXJseSBz
dGFnZXMgb2YgdGhlIGhhbmRzaGFrZSBpdCBpcyBub3QgcG9zc2libGU6IFRoZSBjbGllbnQgY2hh
bmdlcyBpdHMgY29ubmVjdGlvbiBJRCB1c2VkIGZvciBJbml0aWFsIGFuZCAwLVJUVCBwYWNrZXRz
IGFzIHNvb24gYXMgaXQgcmVjZWl2ZXMgYSBuZXcgY29ubmVjdGlvbiBJRCBwcm92aWRlZCBieSB0
aGUgc2VydmVyIGluIGEgUmV0cnkgb3IgSW5pdGlhbCBwYWNrZXQuIFRoZSBlYXJsaWVzdCB0aW1l
IHdoZXJlIGEgY2xpZW50IGNvdWxkIHBvc3NpYmx5IGNvYWxlc2NlIHBhY2tldHMgd2l0aCBkaWZm
ZXJlbnQgY29ubmVjdGlvbiBJRHMgaXMgYWZ0ZXIgcmVjZWl2aW5nIHRoZSBTZXJ2ZXIgUHJlZmVy
cmVkIEFkZHJlc3MsIGFuZCBkZWNpZGVzIChmb3Igd2hhdGV2ZXIgcmVhc29uKSB0byBub3QgbWln
cmF0ZSB0byB0aGF0IGFkZHJlc3MsIGJ1dCB0byB1c2UgdGhhdCBjb25uZWN0aW9uIElEIG9uIHRo
ZSBvcmlnaW5hbCBwYXRoIChhbmQgYmVmb3JlIHRoZSBoYW5kc2hha2UgaXMgY29uZmlybWVkKS4N
Cg0KVGhlIHNlcnZlciBuZWVkcyB0byByZWNlaXZlIGEgTkVXX0NPTk5FQ1RJT05fSUQgZnJhbWUg
YmVmb3JlIGl0IGNhbiBjaGFuZ2UgY29ubmVjdGlvbiBJRHMuIFRoZSBlYXJsaWVzdCB0aGlzIGNh
biBoYXBwZW4gaXMgaW4gYSAwLVJUVCBwYWNrZXQsIHNvIGluIHByaW5jaXBsZSBhIHNlcnZlciBj
b3VsZCBzdGFydCB1c2luZyB0aGF0IGNvbm5lY3Rpb24gSUQgaW4gaXRzIGZpcnN0IGZsaWdodC4N
CkkgY2FuIHNlZSBsaXR0bGUgcmVhc29uIHRvIDEuIHN0YXJ0IHVzaW5nIGEgbmV3IGNvbm5lY3Rp
b24gSUQgZHVyaW5nIHRoZSBoYW5kc2hha2UgYW5kIGF0IHRoZSBzYW1lIHRpbWUgMi4gdG8gbm90
IGNvbXBsZXRlbHkgc3dpdGNoIHRvIHRoYXQgY29ubmVjdGlvbiBJRCwgYnV0IGluc3RlYWQgdG8g
Y29udGludWUgdXNpbmcgYm90aCBhdCB0aGUgc2FtZSB0aW1lLg0KVG8gYmUgY2xlYXIsIGl0IGlz
bid0IHByb2hpYml0ZWQgdG8gdXNlIG11bHRpcGxlIGNvbm5lY3Rpb24gSURzIGF0IHRoZSBzYW1l
IHRpbWUgKGFuZCBvbiB0aGUgc2FtZSBwYXRoKSwgaXQncyBqdXN0IHRoYXQgdGhlcmUncyBubyBn
b29kIHJlYXNvbiB0byBkbyBzby4gSSBkb24ndCB0aGluayBpdCdzIHRvbyBtdWNoIG9mIGEgYnVy
ZGVuIHRvIGFzayBpbXBsZW1lbnRhdGlvbnMgdGhhdCBzdGlsbCBkZWNpZGUgdG8gZG8gc28gdG8g
bWFrZSBzdXJlIHRoYXQgdGhlIGNvbm5lY3Rpb24gSURzIHVzZWQgaW4gYSBjb2FsZXNjZWQgcGFj
a2V0IG1hdGNoLCBjb25zaWRlcmluZyB0aGF0IGZvciB0aGUgcmVjZWl2ZXIgaXQncyBtb3JlIGN1
bWJlcnNvbWUgdG8gY2hlY2sgdGhhdCBhbGwgY29ubmVjdGlvbiBJRHMgYXJlIGFjdHVhbGx5IHZh
bGlkIGZvciB0aGlzIGNvbm5lY3Rpb24gdGhhbiB0byBqdXN0IHZhbGlkYXRlIHRoYXQgYWxsIHBh
Y2tldHMgdXNlIHRoZSBzYW1lIGNvbm5lY3Rpb24gSUQuDQoNCk9uIFdlZCwgSnVsIDE1LCAyMDIw
IGF0IDI6MjQgUE0gTWFydGluIFRob21zb24gPG10QGxvd2VudHJvcHkubmV0PG1haWx0bzptdEBs
b3dlbnRyb3B5Lm5ldD4+IHdyb3RlOg0KaHR0cHM6Ly9naXRodWIuY29tL3F1aWN3Zy9iYXNlLWRy
YWZ0cy9pc3N1ZXMvMzgwMDxodHRwczovL25hbTA2LnNhZmVsaW5rcy5wcm90ZWN0aW9uLm91dGxv
b2suY29tLz91cmw9aHR0cHMlM0ElMkYlMkZnaXRodWIuY29tJTJGcXVpY3dnJTJGYmFzZS1kcmFm
dHMlMkZpc3N1ZXMlMkYzODAwJmRhdGE9MDIlN0MwMSU3Q25pYmFua3MlNDBtaWNyb3NvZnQuY29t
JTdDNzVkZmU2MDQ2Y2JlNDg5ODUyZDkwOGQ4MjhiNWQ0YmUlN0M3MmY5ODhiZjg2ZjE0MWFmOTFh
YjJkN2NkMDExZGI0NyU3QzElN0MwJTdDNjM3MzA0MTA4NzE4MTE2MjM5JnNkYXRhPWl4ZUZ4ZURq
cDBrekQ4N1NaejNBUGFTQW5Ib0FiUDVLJTJCbDUzVFNFRGZlOCUzRCZyZXNlcnZlZD0wPiBkaXNj
b3ZlcmVkIGEgbWlub3IgImRpc2NyZXBhbmN5IiBpbiBvdXIgcmVxdWlyZW1lbnRzIGZvciBjb2Fs
ZXNjaW5nIHBhY2tldHMuICBXZSByZXF1aXJlZCB0aGF0Og0KDQoqIHNlbmRlcnMgbm90IGNvYWxl
c2NlIHBhY2tldHMgZm9yIGRpZmZlcmVudCBjb25uZWN0aW9ucyBpbiB0aGUgc2FtZSBkYXRhZ3Jh
bS4NCg0KKiByZWNlaXZlcnMgcmVqZWN0IHBhY2tldHMgd2l0aCBkaWZmZXJlbnQgY29ubmVjdGlv
biAqKklEcyoqIGluIHRoZSBzYW1lIGRhdGFncmFtLg0KDQpodHRwczovL2dpdGh1Yi5jb20vcXVp
Y3dnL2Jhc2UtZHJhZnRzL3B1bGwvMzg3MC9maWxlczxodHRwczovL25hbTA2LnNhZmVsaW5rcy5w
cm90ZWN0aW9uLm91dGxvb2suY29tLz91cmw9aHR0cHMlM0ElMkYlMkZnaXRodWIuY29tJTJGcXVp
Y3dnJTJGYmFzZS1kcmFmdHMlMkZwdWxsJTJGMzg3MCUyRmZpbGVzJmRhdGE9MDIlN0MwMSU3Q25p
YmFua3MlNDBtaWNyb3NvZnQuY29tJTdDNzVkZmU2MDQ2Y2JlNDg5ODUyZDkwOGQ4MjhiNWQ0YmUl
N0M3MmY5ODhiZjg2ZjE0MWFmOTFhYjJkN2NkMDExZGI0NyU3QzElN0MwJTdDNjM3MzA0MTA4NzE4
MTI2MjI3JnNkYXRhPXpiMVBVc1lucExxa0VJeUQlMkIzY214U0t0anZpdmIwNW9yNzBYbnFNRlV5
YyUzRCZyZXNlcnZlZD0wPiB3YXMgdGhlIHJlc3VsdCBvZiBhIGRpc2N1c3Npb24gd2hlcmUgSSB3
YXMgY29udmluY2VkIHRoYXQgbG9vc2VyIGNvbnN0cmFpbnRzIGhlcmUgd2VyZW4ndCBoYXJtZnVs
LiAgVGhlIHJlcXVpcmVtZW50cyB3b3VsZCBpZGVudGlmeSBjb25uZWN0aW9ucywgbm90IGNvbm5l
Y3Rpb24gSURzLg0KDQpPcmlnaW5hbGx5LCBteSBpbmNsaW5hdGlvbiB3YXMgdG8gZml4IHRoZSBy
ZXF1aXJlbWVudCBvbiB0aGUgc2VuZGVyIHRvIHVzZSBjb25uZWN0aW9uIElEcywgd2hpY2ggd291
bGQgcmVtb3ZlIHNvbWUgbGlua2FiaWxpdHkuICBCdXQgdGhlbiBJIHdhcyByZW1pbmRlZCB0aGF0
IGxpbmthYmlsaXR5IGlzIGFscmVhZHkgZGVmZWF0ZWQgZm9yIHNldmVyYWwgcmVhc29ucy4gIFlv
dSBjYW4ndCBjb2FsZXNjZSBvdXRzaWRlIG9mIHRoZSBoYW5kc2hha2UgYW5kIHdlIHJlcXVpcmUg
YSBzdGFibGUgcGF0aCBmb3IgdGhlIGhhbmRzaGFrZSBBTkQgbG9uZyBoZWFkZXJzIGluY2x1ZGUg
YSBzb3VyY2UgY29ubmVjdGlvbiBJRCB0aGF0IGNhbiBiZSB1c2VkIGZvciBsaW5rYWJpbGl0eS4g
IFNvIHRoZSBsaW5rYWJpbGl0eSBjb25jZXJuIGlzIGJhc2ljYWxseSBsb3N0Lg0KDQpXZSBhbHNv
IGxlYXJuZWQgdGhhdCBzb21lIGltcGxlbWVudGF0aW9ucyB3ZXJlIGdlbmVyYXRpbmcgcGFja2V0
cyB3aGlsZSBwcm9jZXNzaW5nIGluY29taW5nIHBhY2tldHMuICBMYXRlciB0aGV5IHdvdWxkIGNv
YWxlc2NlIHRoZXNlIGludG8gYSBkYXRhZ3JhbSB0aGF0IG1pZ2h0IHRoZW4gaGF2ZSBkaWZmZXJl
bnQgY29ubmVjdGlvbiBJRHMgb24gdGhlIHBhY2tldHMgaXQgY29udGFpbnMuDQoNClRoZXJlIGhh
cyBiZWVuIHNvbWUgb3Bwb3NpdGlvbiB0byB0aGUgcHJvcG9zZWQgcmVzb2x1dGlvbiBpbiBQUiAz
ODcwLg0KDQpBcHBhcmVudGx5LCBmb3Igc29tZSwgaGF2aW5nIG11bHRpcGxlIGNvbm5lY3Rpb24g
SURzIGluIHRoZSBzYW1lIGRhdGFncmFtIGNvbXBsaWNhdGVzIHByb2Nlc3NpbmcuICBJIGRvbid0
IHVuZGVyc3RhbmQgdGhpcyBvYmplY3Rpb24uICBJdCBzZWVtcyB0byBtZSBtb3JlIGRpZmZpY3Vs
dCB0byByZXRhaW4gc3RhdGUgYWNyb3NzIHBhY2tldHMgdGhhbiBpdCBpcyB0byBwcm9jZXNzIGVh
Y2ggYXRvbWljYWxseS4gIEkgd2FzIGhvcGluZyB0aGF0IENocmlzdGlhbiBvciBOaWNrIGNhbiBl
eHBsYWluIG1vcmUgYWJvdXQgaG93IHRoaXMgYWZmZWN0cyB0aGVtLg0KDQpNYXJ0ZW4gYWxzbyBp
bmRpY2F0ZWQgdGhhdCB0aGVyZSB3YXMgYSByZWFzb24gbm90IHRvIGFsbG93IHRoaXMsIGJ1dCBp
ZiBJIHVuZGVyc3RhbmQgdGhhdCwgdGhpcyBpcyBiYXNlZCBvbiBzb21lIHBvdGVudGlhbCBmb3Ig
ZnV0dXJlIG9wdGltaXphdGlvbiwgd2hpY2ggY291bGQgYmUgY29uZGl0aW9uYWwgb24gaGF2aW5n
IGNvbnNpc3RlbnQgY29ubmVjdGlvbiBJRHMuICBJZiB3ZSBtb3ZlZCB0byBhIHNjaGVtZSB0aGF0
IHJlcXVpcmVkIGNvbnNpc3RlbnQgY29ubmVjdGlvbiBJRHMsIGFueW9uZSB1c2luZyB0aGF0IHNj
aGVtZSBjb3VsZCBiZSByZXF1aXJlZCB0byBhdm9pZCBjb2FsZXNjaW5nIGRpZmZlcmVudCBjb25u
ZWN0aW9uIElEcy4gIFNvIHRoaXMgc2VlbXMgbW9yZSBvZiBhIHRoZW9yZXRpY2FsIGNvbmNlcm4u
DQoNCkFuZCAtIGluIGFudGljaXBhdGlvbiBvZiBtYXliZSBjaG9vc2luZyB0byBtYWtlIHNlbmRl
cnMgdXNlIGEgY29uc2lzdGVudCBjb25uZWN0aW9uIElEIC0gaWYgeW91IG1pZ2h0IGJlIGdlbmVy
YXRpbmcgY29hbGVzY2VkIGRhdGFncmFtcyB3aXRoIGRpZmZlcmVudCBjb25uZWN0aW9uIElEcyBp
biBwYWNrZXRzLCBob3cgaGFyZCB3b3VsZCBpdCBiZSB0byBlbnN1cmUgdGhhdCB0aGVzZSBhcmUg
Y29uc2lzdGVudD8gIExhcnMgYW5kIElhbiwgSSB0aGluayBib3RoIG9mIHlvdSBpbmRpY2F0ZWQg
dGhhdCB5b3UgbWlnaHQgZG8gdGhpcy4NCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCgltYXJnaW4tYm90dG9tOi4wMDAxcHQ7DQoJ
Zm9udC1zaXplOjExLjBwdDsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQph
OmxpbmssIHNwYW4uTXNvSHlwZXJsaW5rDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgljb2xv
cjpibHVlOw0KCXRleHQtZGVjb3JhdGlvbjp1bmRlcmxpbmU7fQ0KLk1zb0NocERlZmF1bHQNCgl7
bXNvLXN0eWxlLXR5cGU6ZXhwb3J0LW9ubHk7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMt
c2VyaWY7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6OC41aW4gMTEuMGluOw0KCW1hcmdp
bjoxLjBpbiAxLjBpbiAxLjBpbiAxLjBpbjt9DQpkaXYuV29yZFNlY3Rpb24xDQoJe3BhZ2U6V29y
ZFNlY3Rpb24xO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFw
ZWRlZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZd
LS0+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+
DQo8bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3ht
bD48IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2
bGluaz0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj5HZW5lcmFsbHksIEkgYWdyZWUgd2l0aCBNYXJ0ZW7igJlzIGNvbW1lbnRzIHRoYXQg
dGhhdCB0aGVyZSBpcyBsaXR0bGUgcmVhc29uIHRvIHVzZSBtdWx0aXBsZSBjb25uZWN0aW9ucyBJ
RHMgaW4gdGhlIHNhbWUgZGF0YWdyYW0uIFNwZWNpZmljYWxseSwgZm9yIG91ciBpbXBsZW1lbnRh
dGlvbiwgTXNRdWljLCB2YWxpZGF0aW5nIHRoZSBjb25uZWN0aW9uIElEIGluIGVhY2ggcGFja2V0
IGlzIG11Y2ggc2ltcGxlciBpZg0KIHRoZXnigJlyZSBhbGwgdGhlIHNhbWUuOyBvdXIgVURQIGRh
dGFncmFtIGNvbnRleHQgc3RydWN0dXJlIGhvbGRzIGEgcG9pbnRlciB0byB0aGUgZmlyc3QgY29u
bmVjdGlvbiBJRCBpbiB0aGUgZGF0YWdyYW0sIHNvIGFsbCB0aGF0IG5lZWRzIHRvIGJlIGRvbmUg
KGZvciBlYWNoIFFVSUMgcGFja2V0KSBpcyBjb21wYXJlIHRoZSBjdXJyZW50IFFVSUMgcGFja2V0
4oCZcyBjb25uZWN0aW9uIElEIHRvIHRoYXQgcG9pbnRlci4gVGhlIGxvZ2ljIHJlcXVpcmVzDQog
bm8gYWRkaXRpb25hbCBjb25uZWN0aW9uIHN0YXRlLiBJZiB3ZSBhbGxvd2VkIGFueSBjb25uZWN0
aW9uIElEIHRoYXTigJlzIHZhbGlkIGZvciB0aGUgY29ubmVjdGlvbiwgdGhlbiB3ZeKAmWQgaGF2
ZSB0byBnbyB0byB0aGUgY29ubmVjdGlvbiBvYmplY3QgYW5kIGRvIGEgbG9va3VwIGVhY2ggdGlt
ZSBpbnN0ZWFkLiBJdOKAmXMgZGVmaW5pdGVseSBwb3NzaWJsZSB0byBkbywgYnV0IHJlcXVpcmVz
IGEgYml0IG1vcmUgd29yayAoQ1BVKSBhbmQgc3luY2hyb25pemF0aW9uDQogb2Ygc3RhdGUuIEZv
ciB0aG9zZSByZWFzb25zLCBJ4oCZZCBwcmVmZXIgdG8ga2VlcCB0aGUgY29ubmVjdGlvbiBJRHMg
Y29uc2lzdGVudC48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VGhhbmtzLDxvOnA+PC9vOnA+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+LSBOaWNrPHN1Yj48bzpwPjwvbzpwPjwvc3ViPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdiBzdHlsZT0i
Ym9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQg
MGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+RnJvbTo8L2I+IFFVSUMgJmx0
O3F1aWMtYm91bmNlc0BpZXRmLm9yZyZndDsgPGI+T24gQmVoYWxmIE9mIDwvYj4NCk1hcnRlbiBT
ZWVtYW5uPGJyPg0KPGI+U2VudDo8L2I+IFdlZG5lc2RheSwgSnVseSAxNSwgMjAyMCA0OjU0IEFN
PGJyPg0KPGI+VG86PC9iPiBNYXJ0aW4gVGhvbXNvbiAmbHQ7bXRAbG93ZW50cm9weS5uZXQmZ3Q7
PGJyPg0KPGI+Q2M6PC9iPiBRVUlDIFdHICZsdDtxdWljQGlldGYub3JnJmd0Ozxicj4NCjxiPlN1
YmplY3Q6PC9iPiBSZTogTmVlZCB5b3VyIGhlbHA6IGRpZmZlcmVudCBjb25uZWN0aW9uIElEcyBp
biB0aGUgc2FtZSBkYXRhZ3JhbTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQiPkxldCdzIGhhdmUgYSBsb29rIHdoZXJlIHRo
aXMgc2l0dWF0aW9uIGNhbiBvY2N1cjo8YnI+DQo8YnI+DQpEdXJpbmcgdGhlIGVhcmx5IHN0YWdl
cyBvZiB0aGUgaGFuZHNoYWtlIGl0IGlzIG5vdCBwb3NzaWJsZTogVGhlIGNsaWVudCBjaGFuZ2Vz
IGl0cyBjb25uZWN0aW9uIElEIHVzZWQgZm9yIEluaXRpYWwgYW5kIDAtUlRUIHBhY2tldHMgYXMg
c29vbiBhcyBpdCByZWNlaXZlcyBhIG5ldyBjb25uZWN0aW9uIElEIHByb3ZpZGVkIGJ5IHRoZSBz
ZXJ2ZXIgaW4gYSBSZXRyeSBvciBJbml0aWFsIHBhY2tldC4gVGhlIGVhcmxpZXN0IHRpbWUgd2hl
cmUgYSBjbGllbnQNCiBjb3VsZCBwb3NzaWJseSBjb2FsZXNjZSBwYWNrZXRzIHdpdGggZGlmZmVy
ZW50IGNvbm5lY3Rpb24gSURzIGlzIGFmdGVyIHJlY2VpdmluZyB0aGUgU2VydmVyIFByZWZlcnJl
ZCBBZGRyZXNzLCBhbmQgZGVjaWRlcyAoZm9yIHdoYXRldmVyIHJlYXNvbikgdG8gbm90IG1pZ3Jh
dGUgdG8gdGhhdCBhZGRyZXNzLCBidXQgdG8gdXNlIHRoYXQgY29ubmVjdGlvbiBJRCBvbiB0aGUg
b3JpZ2luYWwgcGF0aCAoYW5kIGJlZm9yZSB0aGUgaGFuZHNoYWtlIGlzDQogY29uZmlybWVkKS48
YnI+DQo8YnI+DQpUaGUgc2VydmVyIG5lZWRzIHRvIHJlY2VpdmUgYSBORVdfQ09OTkVDVElPTl9J
RCBmcmFtZSBiZWZvcmUgaXQgY2FuIGNoYW5nZSBjb25uZWN0aW9uIElEcy4gVGhlIGVhcmxpZXN0
IHRoaXMgY2FuIGhhcHBlbiBpcyBpbiBhIDAtUlRUIHBhY2tldCwgc28gaW4gcHJpbmNpcGxlIGEg
c2VydmVyIGNvdWxkIHN0YXJ0IHVzaW5nIHRoYXQgY29ubmVjdGlvbiBJRCBpbiBpdHMgZmlyc3Qg
ZmxpZ2h0LjxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkgY2Fu
IHNlZSBsaXR0bGUgcmVhc29uIHRvIDEuIHN0YXJ0IHVzaW5nIGEgbmV3IGNvbm5lY3Rpb24gSUQg
ZHVyaW5nIHRoZSBoYW5kc2hha2UgYW5kIGF0IHRoZSBzYW1lIHRpbWUgMi4gdG8gbm90IGNvbXBs
ZXRlbHkgc3dpdGNoIHRvIHRoYXQgY29ubmVjdGlvbiBJRCwgYnV0IGluc3RlYWQgdG8gY29udGlu
dWUgdXNpbmcgYm90aCBhdCB0aGUgc2FtZSB0aW1lLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VG8gYmUgY2xlYXIsIGl0IGlzbid0IHByb2hpYml0
ZWQgdG8gdXNlIG11bHRpcGxlIGNvbm5lY3Rpb24gSURzIGF0IHRoZSBzYW1lIHRpbWUgKGFuZCBv
biB0aGUgc2FtZSBwYXRoKSwgaXQncyBqdXN0IHRoYXQgdGhlcmUncyBubyBnb29kIHJlYXNvbiB0
byBkbyBzby4gSSBkb24ndCB0aGluayBpdCdzIHRvbyBtdWNoIG9mIGEgYnVyZGVuIHRvIGFzayBp
bXBsZW1lbnRhdGlvbnMgdGhhdCBzdGlsbCBkZWNpZGUgdG8NCiBkbyBzbyB0byBtYWtlIHN1cmUg
dGhhdCB0aGUgY29ubmVjdGlvbiBJRHMgdXNlZCBpbiBhIGNvYWxlc2NlZCBwYWNrZXQgbWF0Y2gs
IGNvbnNpZGVyaW5nIHRoYXQgZm9yIHRoZSByZWNlaXZlciBpdCdzIG1vcmUgY3VtYmVyc29tZSB0
byBjaGVjayB0aGF0IGFsbCBjb25uZWN0aW9uIElEcyBhcmUgYWN0dWFsbHkgdmFsaWQgZm9yIHRo
aXMgY29ubmVjdGlvbiB0aGFuIHRvIGp1c3QgdmFsaWRhdGUgdGhhdCBhbGwgcGFja2V0cyB1c2Ug
dGhlIHNhbWUNCiBjb25uZWN0aW9uIElELjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBXZWQsIEp1bCAxNSwgMjAyMCBhdCAyOjI0IFBNIE1h
cnRpbiBUaG9tc29uICZsdDs8YSBocmVmPSJtYWlsdG86bXRAbG93ZW50cm9weS5uZXQiPm10QGxv
d2VudHJvcHkubmV0PC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9j
a3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0
O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0
OjBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibWFyZ2luLWJvdHRvbToxMi4wcHQi
PjxhIGhyZWY9Imh0dHBzOi8vbmFtMDYuc2FmZWxpbmtzLnByb3RlY3Rpb24ub3V0bG9vay5jb20v
P3VybD1odHRwcyUzQSUyRiUyRmdpdGh1Yi5jb20lMkZxdWljd2clMkZiYXNlLWRyYWZ0cyUyRmlz
c3VlcyUyRjM4MDAmYW1wO2RhdGE9MDIlN0MwMSU3Q25pYmFua3MlNDBtaWNyb3NvZnQuY29tJTdD
NzVkZmU2MDQ2Y2JlNDg5ODUyZDkwOGQ4MjhiNWQ0YmUlN0M3MmY5ODhiZjg2ZjE0MWFmOTFhYjJk
N2NkMDExZGI0NyU3QzElN0MwJTdDNjM3MzA0MTA4NzE4MTE2MjM5JmFtcDtzZGF0YT1peGVGeGVE
anAwa3pEODdTWnozQVBhU0FuSG9BYlA1SyUyQmw1M1RTRURmZTglM0QmYW1wO3Jlc2VydmVkPTAi
IHRhcmdldD0iX2JsYW5rIj5odHRwczovL2dpdGh1Yi5jb20vcXVpY3dnL2Jhc2UtZHJhZnRzL2lz
c3Vlcy8zODAwPC9hPg0KIGRpc2NvdmVyZWQgYSBtaW5vciAmcXVvdDtkaXNjcmVwYW5jeSZxdW90
OyBpbiBvdXIgcmVxdWlyZW1lbnRzIGZvciBjb2FsZXNjaW5nIHBhY2tldHMuJm5ic3A7IFdlIHJl
cXVpcmVkIHRoYXQ6PGJyPg0KPGJyPg0KKiBzZW5kZXJzIG5vdCBjb2FsZXNjZSBwYWNrZXRzIGZv
ciBkaWZmZXJlbnQgY29ubmVjdGlvbnMgaW4gdGhlIHNhbWUgZGF0YWdyYW0uPGJyPg0KPGJyPg0K
KiByZWNlaXZlcnMgcmVqZWN0IHBhY2tldHMgd2l0aCBkaWZmZXJlbnQgY29ubmVjdGlvbiAqKklE
cyoqIGluIHRoZSBzYW1lIGRhdGFncmFtLjxicj4NCjxicj4NCjxhIGhyZWY9Imh0dHBzOi8vbmFt
MDYuc2FmZWxpbmtzLnByb3RlY3Rpb24ub3V0bG9vay5jb20vP3VybD1odHRwcyUzQSUyRiUyRmdp
dGh1Yi5jb20lMkZxdWljd2clMkZiYXNlLWRyYWZ0cyUyRnB1bGwlMkYzODcwJTJGZmlsZXMmYW1w
O2RhdGE9MDIlN0MwMSU3Q25pYmFua3MlNDBtaWNyb3NvZnQuY29tJTdDNzVkZmU2MDQ2Y2JlNDg5
ODUyZDkwOGQ4MjhiNWQ0YmUlN0M3MmY5ODhiZjg2ZjE0MWFmOTFhYjJkN2NkMDExZGI0NyU3QzEl
N0MwJTdDNjM3MzA0MTA4NzE4MTI2MjI3JmFtcDtzZGF0YT16YjFQVXNZbnBMcWtFSXlEJTJCM2Nt
eFNLdGp2aXZiMDVvcjcwWG5xTUZVeWMlM0QmYW1wO3Jlc2VydmVkPTAiIHRhcmdldD0iX2JsYW5r
Ij5odHRwczovL2dpdGh1Yi5jb20vcXVpY3dnL2Jhc2UtZHJhZnRzL3B1bGwvMzg3MC9maWxlczwv
YT4NCiB3YXMgdGhlIHJlc3VsdCBvZiBhIGRpc2N1c3Npb24gd2hlcmUgSSB3YXMgY29udmluY2Vk
IHRoYXQgbG9vc2VyIGNvbnN0cmFpbnRzIGhlcmUgd2VyZW4ndCBoYXJtZnVsLiZuYnNwOyBUaGUg
cmVxdWlyZW1lbnRzIHdvdWxkIGlkZW50aWZ5IGNvbm5lY3Rpb25zLCBub3QgY29ubmVjdGlvbiBJ
RHMuPGJyPg0KPGJyPg0KT3JpZ2luYWxseSwgbXkgaW5jbGluYXRpb24gd2FzIHRvIGZpeCB0aGUg
cmVxdWlyZW1lbnQgb24gdGhlIHNlbmRlciB0byB1c2UgY29ubmVjdGlvbiBJRHMsIHdoaWNoIHdv
dWxkIHJlbW92ZSBzb21lIGxpbmthYmlsaXR5LiZuYnNwOyBCdXQgdGhlbiBJIHdhcyByZW1pbmRl
ZCB0aGF0IGxpbmthYmlsaXR5IGlzIGFscmVhZHkgZGVmZWF0ZWQgZm9yIHNldmVyYWwgcmVhc29u
cy4mbmJzcDsgWW91IGNhbid0IGNvYWxlc2NlIG91dHNpZGUgb2YgdGhlIGhhbmRzaGFrZSBhbmQN
CiB3ZSByZXF1aXJlIGEgc3RhYmxlIHBhdGggZm9yIHRoZSBoYW5kc2hha2UgQU5EIGxvbmcgaGVh
ZGVycyBpbmNsdWRlIGEgc291cmNlIGNvbm5lY3Rpb24gSUQgdGhhdCBjYW4gYmUgdXNlZCBmb3Ig
bGlua2FiaWxpdHkuJm5ic3A7IFNvIHRoZSBsaW5rYWJpbGl0eSBjb25jZXJuIGlzIGJhc2ljYWxs
eSBsb3N0Ljxicj4NCjxicj4NCldlIGFsc28gbGVhcm5lZCB0aGF0IHNvbWUgaW1wbGVtZW50YXRp
b25zIHdlcmUgZ2VuZXJhdGluZyBwYWNrZXRzIHdoaWxlIHByb2Nlc3NpbmcgaW5jb21pbmcgcGFj
a2V0cy4mbmJzcDsgTGF0ZXIgdGhleSB3b3VsZCBjb2FsZXNjZSB0aGVzZSBpbnRvIGEgZGF0YWdy
YW0gdGhhdCBtaWdodCB0aGVuIGhhdmUgZGlmZmVyZW50IGNvbm5lY3Rpb24gSURzIG9uIHRoZSBw
YWNrZXRzIGl0IGNvbnRhaW5zLjxicj4NCjxicj4NClRoZXJlIGhhcyBiZWVuIHNvbWUgb3Bwb3Np
dGlvbiB0byB0aGUgcHJvcG9zZWQgcmVzb2x1dGlvbiBpbiBQUiAzODcwLiZuYnNwOyA8YnI+DQo8
YnI+DQpBcHBhcmVudGx5LCBmb3Igc29tZSwgaGF2aW5nIG11bHRpcGxlIGNvbm5lY3Rpb24gSURz
IGluIHRoZSBzYW1lIGRhdGFncmFtIGNvbXBsaWNhdGVzIHByb2Nlc3NpbmcuJm5ic3A7IEkgZG9u
J3QgdW5kZXJzdGFuZCB0aGlzIG9iamVjdGlvbi4mbmJzcDsgSXQgc2VlbXMgdG8gbWUgbW9yZSBk
aWZmaWN1bHQgdG8gcmV0YWluIHN0YXRlIGFjcm9zcyBwYWNrZXRzIHRoYW4gaXQgaXMgdG8gcHJv
Y2VzcyBlYWNoIGF0b21pY2FsbHkuJm5ic3A7IEkgd2FzIGhvcGluZyB0aGF0IENocmlzdGlhbg0K
IG9yIE5pY2sgY2FuIGV4cGxhaW4gbW9yZSBhYm91dCBob3cgdGhpcyBhZmZlY3RzIHRoZW0uPGJy
Pg0KPGJyPg0KTWFydGVuIGFsc28gaW5kaWNhdGVkIHRoYXQgdGhlcmUgd2FzIGEgcmVhc29uIG5v
dCB0byBhbGxvdyB0aGlzLCBidXQgaWYgSSB1bmRlcnN0YW5kIHRoYXQsIHRoaXMgaXMgYmFzZWQg
b24gc29tZSBwb3RlbnRpYWwgZm9yIGZ1dHVyZSBvcHRpbWl6YXRpb24sIHdoaWNoIGNvdWxkIGJl
IGNvbmRpdGlvbmFsIG9uIGhhdmluZyBjb25zaXN0ZW50IGNvbm5lY3Rpb24gSURzLiZuYnNwOyBJ
ZiB3ZSBtb3ZlZCB0byBhIHNjaGVtZSB0aGF0IHJlcXVpcmVkIGNvbnNpc3RlbnQNCiBjb25uZWN0
aW9uIElEcywgYW55b25lIHVzaW5nIHRoYXQgc2NoZW1lIGNvdWxkIGJlIHJlcXVpcmVkIHRvIGF2
b2lkIGNvYWxlc2NpbmcgZGlmZmVyZW50IGNvbm5lY3Rpb24gSURzLiZuYnNwOyBTbyB0aGlzIHNl
ZW1zIG1vcmUgb2YgYSB0aGVvcmV0aWNhbCBjb25jZXJuLjxicj4NCjxicj4NCkFuZCAtIGluIGFu
dGljaXBhdGlvbiBvZiBtYXliZSBjaG9vc2luZyB0byBtYWtlIHNlbmRlcnMgdXNlIGEgY29uc2lz
dGVudCBjb25uZWN0aW9uIElEIC0gaWYgeW91IG1pZ2h0IGJlIGdlbmVyYXRpbmcgY29hbGVzY2Vk
IGRhdGFncmFtcyB3aXRoIGRpZmZlcmVudCBjb25uZWN0aW9uIElEcyBpbiBwYWNrZXRzLCBob3cg
aGFyZCB3b3VsZCBpdCBiZSB0byBlbnN1cmUgdGhhdCB0aGVzZSBhcmUgY29uc2lzdGVudD8mbmJz
cDsgTGFycyBhbmQgSWFuLCBJIHRoaW5rDQogYm90aCBvZiB5b3UgaW5kaWNhdGVkIHRoYXQgeW91
IG1pZ2h0IGRvIHRoaXMuPG86cD48L286cD48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwv
ZGl2Pg0KPC9ib2R5Pg0KPC9odG1sPg0K

--_000_DM6PR00MB07671C4366474017F18BC3D8B37E0DM6PR00MB0767namp_--


From nobody Wed Jul 15 11:02:48 2020
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 2BF5A3A0874 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 11:02:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 sbZUELF5ygOg for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 11:02:45 -0700 (PDT)
Received: from mail-qt1-x82f.google.com (mail-qt1-x82f.google.com [IPv6:2607:f8b0:4864:20::82f]) (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 CA4D23A0BF1 for <quic@ietf.org>; Wed, 15 Jul 2020 11:02:41 -0700 (PDT)
Received: by mail-qt1-x82f.google.com with SMTP id g13so2425874qtv.8 for <quic@ietf.org>; Wed, 15 Jul 2020 11:02:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=G1TxWxiQTQ0FQgfGH1RrIttXUADdjybDjZuwyWcI0q0=; b=ZjcHQnvKS069XgSvvgQr/fkMgXlXp6BJMrleYGI1/iYpaAkDO9urcyr9KG1z9TJaVY cZwbqAkx4hBuzCfeRq7mFTTHOb9oRo0wmqVGjSBY3bHKjMyIIoCa1V01a3lVwMEwcvvr NgG1U5w4bwB+ECjwA91q5Ik2imwzDIdFJODFi43PIZjFt8e2M2Gv1j5HYkjqBtTjhT/z o7HKuxt03Vy6EPurNHBVOE+p5uX73FfNvtS2xH+YN+YDGHwZ8A3JbUXcnUz+GOseTGYe BADqdOusfbHW4hCyzsOhFUGKnudwZ/K66NRQDmPTx5QC51C+mLocRmli4zn5vM88gFOO gCEw==
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=G1TxWxiQTQ0FQgfGH1RrIttXUADdjybDjZuwyWcI0q0=; b=MJMImfgC6m23qQ7VgiUO6m665oUnJPr3qZYU2XW2/sF2cEll8PuhNBt/icO23k0bwh SKkN5Kb6nHE0oBGDBU8IZiHomAqFtxmzYOVBxwGCdpbXW/9CxfivmneAuenaD20huhHb 4iddUUuwFIq+H2QUVHCyk6qeO2ljbLDWkMjRIdfgyeCFprFMrS4IV+hqv9GDN/A+qWy+ vpLU2nzM7GmTfbovwpC28IFHshdkESYkBETU/cD7Q5lL+qzCKiJ38oO8TFtUwL60a5RR A0CzH6A9sF7P04gBAOSvxgL8KL5t15+FOlXLhdJxOSpfsGEPbWM/IqjgzWJiBl9gHtfI EMCQ==
X-Gm-Message-State: AOAM5309ZrEWYmpnc/JfOsb+E2lg1QfPszwaNL8Z2Cwsrnuda9ospdmg O9HY7uX+wFOxPFQ6J0b4MpvDODArxIx40Q==
X-Google-Smtp-Source: ABdhPJylLq6i5eJ+TP+CFmBVknkcYqsqCl+2oejNu4+uvRQebIAwQ+hv7WPOu98FnF9QpozpKKb5AQ==
X-Received: by 2002:aed:2967:: with SMTP id s94mr1098843qtd.258.1594836160825;  Wed, 15 Jul 2020 11:02:40 -0700 (PDT)
Received: from lubuntu (ool-44c1d219.dyn.optonline.net. [68.193.210.25]) by smtp.gmail.com with ESMTPSA id p36sm4688914qta.0.2020.07.15.11.02.39 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 15 Jul 2020 11:02:40 -0700 (PDT)
Date: Wed, 15 Jul 2020 14:02:32 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: Martin Thomson <mt@lowentropy.net>
Cc: quic@ietf.org
Subject: Re: Need your help: different connection IDs in the same datagram
Message-ID: <20200715180231.GB9808@lubuntu>
Mail-Followup-To: Martin Thomson <mt@lowentropy.net>, quic@ietf.org
References: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/9dHym3C8WHYdfD4ED3W56evNhjw>
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, 15 Jul 2020 18:02:47 -0000

On Wed, Jul 15, 2020 at 05:23:57PM +1000, Martin Thomson wrote:
> There has been some opposition to the proposed resolution in PR 3870.  
> 
> Apparently, for some, having multiple connection IDs in the same
> datagram complicates processing.  I don't understand this objection.
> It seems to me more difficult to retain state across packets than it
> is to process each atomically.  I was hoping that Christian or Nick
> can explain more about how this affects them.

I can provide an example from lsquic.  The datagram is parsed into
QUIC packets in one function, lsquic_engine_packet_in():

  https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_engine.c#L2781L2816

Each QUIC packet is processed by process_packet_in(), where a
connection is looked up:

  https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_engine.c#L1352L1360

The DCID check is performed lsquic_engine_packet_in(), before
process_packet_in() is called:

  https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_engine.c#L2793L2806

The DCID information is readily available in the datagram parsing
loop, while connection information is not.

For lsquic to support the proposed change, it would have to remember
the current connection and then query it whether it is indeed the
owner of the next DCID (A) or look up DCID in the global hash (B):

    conn = NULL;
    while (quic_packet = parse_udp(pointers)) {
        dcid = parse(quic_packet);
        if (conn)
        {
  #if VARIANT_A
            if (!conn_owns_scid(conn, dcid))
  #else
            if (conn != lookup_by_dcid(dcid))
  #endif
                continue;
        }
        conn = process_packet(quic_packet);
    }

Not that it could not be done, of course, but it is both extra work
to modify lsquic and a more inefficient mechanism: what was a simple
CID comparison is now a hash lookup.

That's why I argued [1] for having solid rationale behind the change
rather than a personal preference.

  - Dmitri.

1. https://github.com/quicwg/base-drafts/issues/3800#issuecomment-656851626


From nobody Wed Jul 15 11:12:55 2020
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 EB6043A0EF9 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 11:12:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level: 
X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 BP3HhFWFMMM8 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 11:12:46 -0700 (PDT)
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 3E3803A0E54 for <quic@ietf.org>; Wed, 15 Jul 2020 11:12:40 -0700 (PDT)
Received: by mail-wr1-x435.google.com with SMTP id f7so3767089wrw.1 for <quic@ietf.org>; Wed, 15 Jul 2020 11:12:40 -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;  bh=QLCTk9zn75nMsC5oOuQGyZcMgZ6LwSBMCgJg0NOq98E=; b=sM5rEMlKombOQz47HGU7ia8WYRaHzh/TmicGKsABoJ2Fm8etZ6F5iydqH8LiIpuIri /33RNNKef8p8TxECCLVK6BT9Ks1pT59BulLk8BAPnenA/M1w5oZ4twj+eQdp7c5mi3Xx 5/pu+yqsxYaJ0RDPmHpCVavEe1fJLb/wWeioFM8kZDiVSZ4rHtx69ZsvfwyRwyioYDp1 jx36gLqL8wQs59Hbg6Zgw6H8EGBjj52DuMe7Kja/G/oH05/YET/M3ILRk657dYeCgXnI 6qYwG1bJsDAEXtse90ZlJ1qAyoROa9ppI4mWtE8ixPWjKSM72xefRUYVaxO+yvp3GDMc si7g==
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=QLCTk9zn75nMsC5oOuQGyZcMgZ6LwSBMCgJg0NOq98E=; b=tFwDpIQXkonJ1kIoEB2NqyhR3lYnhIjTnjXF1VrWvh7tbR+1bd9KZf/5/spqORQpz/ 5dHht/+0n74XwnoWcVo3i8UJoxIu5evU3ekHjnBwisWPndDaQYy9sgc68z06fkKYjFkT mVFSl3PtM1pWyYqumL9Sx3ZwboacEP7kGuame3nVOHniEz/o1DUOCGS2zR2XdY3BMR1w 3qAVdpWdA+eP2aRAwTjIUd+r1kIjJTmsvq8wNrxYPx5yDHG3raIIptDuZkbLvZ46/WWK 1iSCfGqOKGF7XFdHYzz9xhq+bOGIp2ZnfrormnEiMDz6nxd7wSMLwPa1EmYbt3bV/j6B 5hOA==
X-Gm-Message-State: AOAM532RznButMc+pwqfbCVqUKjliXu9CHf1hy6y9u3QxJAF9hOqsVeF f8aXImqXj+R8dC6AZFGXLbzH4yp1b21kkskRcdMffA0+L0A=
X-Google-Smtp-Source: ABdhPJzQ6K5dJasfVszx5a1Tu29X0GwG4MJWgUGjUYgqwBdO/4ASJqdSuZ9n7KE+WiFSxWUlPCuQgxdfvtRvXq5J1KA=
X-Received: by 2002:adf:dd81:: with SMTP id x1mr596046wrl.7.1594836758191; Wed, 15 Jul 2020 11:12:38 -0700 (PDT)
MIME-Version: 1.0
References: <43bb1525-0afa-4c4e-a234-f6ccfacbdd29@www.fastmail.com> <a4d7e8cf-5879-6941-e059-5d2f3e67ae86@huitema.net> <58b40fc0-86ad-49e9-bc17-187c38e97f7a@www.fastmail.com> <1d543593-7abc-4a89-93c5-82c464492786@www.fastmail.com> <CACpbDccSB6H9AhmAinia7ojEg1VY-S=dF214wHvZcZkoiL-xFA@mail.gmail.com> <7d549475-249b-4674-9aa8-c2bf9953243b@www.fastmail.com>
In-Reply-To: <7d549475-249b-4674-9aa8-c2bf9953243b@www.fastmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Wed, 15 Jul 2020 19:12:27 +0100
Message-ID: <CALGR9oaHQHJneN2edetGLcq4u4PNF0oAyq9PKc7ZVxz_pXTMGw@mail.gmail.com>
Subject: Re: New confidentiality and integrity limits
To: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000072686405aa7eded4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/rTlTWHHyPMet7NoVMNLt2E3rez4>
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, 15 Jul 2020 18:12:53 -0000

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

Folks,

As mentioned up thread, the proposal for this issue requires a design
change.

Would anyone else care to express opinion in support for, or against, us
spending time on solving this problem in QUICv1. Please comment here or on
the Github issue: https://github.com/quicwg/base-drafts/issues/3788.

Cheers
Lucas

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

<div dir=3D"ltr"><div dir=3D"ltr"><div>Folks,</div><div><br></div><div>As m=
entioned up thread, the proposal for this issue requires a design change.</=
div><div><br></div><div>Would anyone else care to express opinion in suppor=
t for, or against, us spending time on solving this problem in QUICv1. Plea=
se comment here or on the Github issue: <a href=3D"https://github.com/quicw=
g/base-drafts/issues/3788" rel=3D"noreferrer" target=3D"_blank">https://git=
hub.com/quicwg/base-drafts/issues/3788</a>.</div><div><br></div><div>Cheers=
</div><div>Lucas<br></div></div></div>

--00000000000072686405aa7eded4--


From nobody Wed Jul 15 12:31:12 2020
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 AAD273A0E91 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 12:31:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level: 
X-Spam-Status: No, score=-17.599 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, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, 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 Ig91tJJBnzwy for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 12:31:09 -0700 (PDT)
Received: from mail-yb1-xb36.google.com (mail-yb1-xb36.google.com [IPv6:2607:f8b0:4864:20::b36]) (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 0035B3A0C56 for <quic@ietf.org>; Wed, 15 Jul 2020 12:31:08 -0700 (PDT)
Received: by mail-yb1-xb36.google.com with SMTP id y13so1674253ybj.10 for <quic@ietf.org>; Wed, 15 Jul 2020 12:31:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=O7QCeMURXQBB4I1cS949dFHNTIIPV6AeuIX6J8KzMvM=; b=ihYwmuOO+DNBENgWHeNrwcUX0PDsPrWQmLalLZ6/poN3MX2ZFutLz0R9As7HJsrbRT cub1+qr5gU873ALtHPuAsS8AgtYezHhVdh4+8KQQIkX1VtIoevDyTWAyXs4Jbou/l1GD y6s73OOdVuxVr/uPzf6UO2XTt6J07mqmM9UcvkhUWAS58E4CyCa/1AiQLdFBDNEhMC7u AA7jX2pj5lYN/Cta3YBgg+9iQppE1pDLSD07kfKgdwn0NFDimObQXNT20ROSE28jqx5k fqh4OE5xgLsYrmyXSANiyq3zlj5H4Xo78Kvb366+NVl6uueafZ6+/vfyrnIzhJ/BaqgJ l6qg==
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=O7QCeMURXQBB4I1cS949dFHNTIIPV6AeuIX6J8KzMvM=; b=Qk1ZjMBSlP0RPSOaEWdX8l/LEulGE/4Q1tEh+zeU9vFQuWIgcmkKufnQlbQIyxM86C +jDI/JxN28qBhNWRpJ1rVJb8UBYLo6Ys9rYl4fWdEDmYF90UUDnSGhQVrxP1X8bNFnGo BJ8NWnqRlu22lqGSSZkLMLcQEe8o+L5NOrtxNvD2zDesJSpBazW0vkv4zuj2XdZ2wuCd XQ8OrfUy75wBLdXaCHRY/7Dr67vjlzLY1ALTfMB0S//4SJxopWIZ+gz8WEj6ukIv2wp4 7xbiZeciokZMywS0f/KZ/HINu69l5l26BMbYn7Czfq6mXQiOLl0IQ3x3SXWHr2uZe2lx eR2A==
X-Gm-Message-State: AOAM532O61p8+qRBSZQOZZAqrOORMyY9Pp1mcldypAbuzF4IBCNJ1gty uSUVkVsM5dh8kfb0kUu4JzFL0Uexg2baV48GMD30RQ==
X-Google-Smtp-Source: ABdhPJxHYbstNWXJgh6HSS9OEKXZyV1kAAi1N4zlT3YU5K0pCt+dZXa4ilG4ZxZOSHvgV4uB+QgauUpWPoPi2b10M1M=
X-Received: by 2002:a25:da8c:: with SMTP id n134mr770961ybf.389.1594841467721;  Wed, 15 Jul 2020 12:31:07 -0700 (PDT)
MIME-Version: 1.0
References: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com> <20200715180231.GB9808@lubuntu>
In-Reply-To: <20200715180231.GB9808@lubuntu>
From: Ian Swett <ianswett@google.com>
Date: Wed, 15 Jul 2020 15:30:56 -0400
Message-ID: <CAKcm_gPfc3sFy0kuyTzUFk2XFMZ8NdXTd7CuNf0o0v+RXDG=xg@mail.gmail.com>
Subject: Re: Need your help: different connection IDs in the same datagram
To: Martin Thomson <mt@lowentropy.net>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000288c0a05aa7ff7f2"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/XQTLZXrtc3siGfSi5RSqu2isKU8>
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, 15 Jul 2020 19:31:11 -0000

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

I don't think this change would be difficult for our implementation, but I
also don't see it as necessary.  Given where we are in the process, that
alone argues for not changing it I believe.

On Wed, Jul 15, 2020 at 2:02 PM Dmitri Tikhonov <dtikhonov@litespeedtech.com>
wrote:

> On Wed, Jul 15, 2020 at 05:23:57PM +1000, Martin Thomson wrote:
> > There has been some opposition to the proposed resolution in PR 3870.
> >
> > Apparently, for some, having multiple connection IDs in the same
> > datagram complicates processing.  I don't understand this objection.
> > It seems to me more difficult to retain state across packets than it
> > is to process each atomically.  I was hoping that Christian or Nick
> > can explain more about how this affects them.
>
> I can provide an example from lsquic.  The datagram is parsed into
> QUIC packets in one function, lsquic_engine_packet_in():
>
>
> https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_engine.c#L2781L2816
>
> Each QUIC packet is processed by process_packet_in(), where a
> connection is looked up:
>
>
> https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_engine.c#L1352L1360
>
> The DCID check is performed lsquic_engine_packet_in(), before
> process_packet_in() is called:
>
>
> https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_engine.c#L2793L2806
>
> The DCID information is readily available in the datagram parsing
> loop, while connection information is not.
>
> For lsquic to support the proposed change, it would have to remember
> the current connection and then query it whether it is indeed the
> owner of the next DCID (A) or look up DCID in the global hash (B):
>
>     conn = NULL;
>     while (quic_packet = parse_udp(pointers)) {
>         dcid = parse(quic_packet);
>         if (conn)
>         {
>   #if VARIANT_A
>             if (!conn_owns_scid(conn, dcid))
>   #else
>             if (conn != lookup_by_dcid(dcid))
>   #endif
>                 continue;
>         }
>         conn = process_packet(quic_packet);
>     }
>
> Not that it could not be done, of course, but it is both extra work
> to modify lsquic and a more inefficient mechanism: what was a simple
> CID comparison is now a hash lookup.
>
> That's why I argued [1] for having solid rationale behind the change
> rather than a personal preference.
>
>   - Dmitri.
>
> 1.
> https://github.com/quicwg/base-drafts/issues/3800#issuecomment-656851626
>
>

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

<div dir=3D"ltr">I don&#39;t think this change would be difficult for our i=
mplementation, but I also don&#39;t see it as necessary.=C2=A0 Given where =
we are in the process, that alone argues for not changing it I believe.</di=
v><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On W=
ed, Jul 15, 2020 at 2:02 PM Dmitri Tikhonov &lt;<a href=3D"mailto:dtikhonov=
@litespeedtech.com">dtikhonov@litespeedtech.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 Wed, Jul 15, 2020 at 05:2=
3:57PM +1000, Martin Thomson wrote:<br>
&gt; There has been some opposition to the proposed resolution in PR 3870.=
=C2=A0 <br>
&gt; <br>
&gt; Apparently, for some, having multiple connection IDs in the same<br>
&gt; datagram complicates processing.=C2=A0 I don&#39;t understand this obj=
ection.<br>
&gt; It seems to me more difficult to retain state across packets than it<b=
r>
&gt; is to process each atomically.=C2=A0 I was hoping that Christian or Ni=
ck<br>
&gt; can explain more about how this affects them.<br>
<br>
I can provide an example from lsquic.=C2=A0 The datagram is parsed into<br>
QUIC packets in one function, lsquic_engine_packet_in():<br>
<br>
=C2=A0 <a href=3D"https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/=
liblsquic/lsquic_engine.c#L2781L2816" rel=3D"noreferrer" target=3D"_blank">=
https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_e=
ngine.c#L2781L2816</a><br>
<br>
Each QUIC packet is processed by process_packet_in(), where a<br>
connection is looked up:<br>
<br>
=C2=A0 <a href=3D"https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/=
liblsquic/lsquic_engine.c#L1352L1360" rel=3D"noreferrer" target=3D"_blank">=
https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_e=
ngine.c#L1352L1360</a><br>
<br>
The DCID check is performed lsquic_engine_packet_in(), before<br>
process_packet_in() is called:<br>
<br>
=C2=A0 <a href=3D"https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/=
liblsquic/lsquic_engine.c#L2793L2806" rel=3D"noreferrer" target=3D"_blank">=
https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_e=
ngine.c#L2793L2806</a><br>
<br>
The DCID information is readily available in the datagram parsing<br>
loop, while connection information is not.<br>
<br>
For lsquic to support the proposed change, it would have to remember<br>
the current connection and then query it whether it is indeed the<br>
owner of the next DCID (A) or look up DCID in the global hash (B):<br>
<br>
=C2=A0 =C2=A0 conn =3D NULL;<br>
=C2=A0 =C2=A0 while (quic_packet =3D parse_udp(pointers)) {<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 dcid =3D parse(quic_packet);<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 if (conn)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 {<br>
=C2=A0 #if VARIANT_A<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 if (!conn_owns_scid(conn, dcid))<=
br>
=C2=A0 #else<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 if (conn !=3D lookup_by_dcid(dcid=
))<br>
=C2=A0 #endif<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 continue;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 }<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 conn =3D process_packet(quic_packet);<br>
=C2=A0 =C2=A0 }<br>
<br>
Not that it could not be done, of course, but it is both extra work<br>
to modify lsquic and a more inefficient mechanism: what was a simple<br>
CID comparison is now a hash lookup.<br>
<br>
That&#39;s why I argued [1] for having solid rationale behind the change<br=
>
rather than a personal preference.<br>
<br>
=C2=A0 - Dmitri.<br>
<br>
1. <a href=3D"https://github.com/quicwg/base-drafts/issues/3800#issuecommen=
t-656851626" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg=
/base-drafts/issues/3800#issuecomment-656851626</a><br>
<br>
</blockquote></div>

--000000000000288c0a05aa7ff7f2--


From nobody Wed Jul 15 13:31:04 2020
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 950B23A0FA1 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 13:31:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 73La0A3wFNd6 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 13:30:59 -0700 (PDT)
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 700773A0AEF for <quic@ietf.org>; Wed, 15 Jul 2020 13:30:59 -0700 (PDT)
Received: by mail-lj1-x233.google.com with SMTP id x9so4171821ljc.5 for <quic@ietf.org>; Wed, 15 Jul 2020 13:30:59 -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=ck2mIz7tQp6xkjzHrGCz96hiu/Eo9UmIGh4pnzHvm4s=; b=R8FH9RHUMC/EFb2+Mkuf1jq5ejgbsbk5Onxqv68qGYOfeApF0P5x98RK0zKM40hK1I GB/+CGnLrCTxtL7sfuT8xCON/hGn81KGa1INNTcqVPUDhTiiHnB1mFNxDTS+lBvx6Iv5 3+pGae6cDj/M6ZlOZabIXJgmxAIPZ5i+UhWQGm7zzDmxtSjzfYXNOBHga8C/rDl6NN8n u2uaXtwHqoGh4VKQrh5Dqot7PbwdDiO8+zXPgi5i6W41jxKLDSUMp3Wg26/nL+LO91CN bc7SNvAfEza8egQAUz+v+fzoYIUzCysVg6QuXSmd1cgFO9MhXRwHAT5Hdd6k1925/EJd x4Hg==
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=ck2mIz7tQp6xkjzHrGCz96hiu/Eo9UmIGh4pnzHvm4s=; b=dPUZOjpu1ySn1CkBFEQ9F9Zw+1mOfKjt05rnUM0aK4ag2XpkmGXNBBK11yoUhaiYi8 e5SzXFjxxfpMT0aC+d7ycx4yMwtdImuHb1H7kyv0IzxwKxRXBWtJyINKGR98QPfBp7xa cN5GljVWwTMJTmIGmpbBh/xJaVWeFkjkua6g8BDO0OMZjAX3NFCb+M8FDffqdDhRb97I MrBBp+x38HCoqxxlp1OQ1Rtzy0stNqu0670UQvAjKR5+ZgIh8gmUwRvhknxqk4ZaG2Uc vjE4Ls5UE2uGdo345ZSzjzJFgqK30IOrg4XAaswLlr7H1hfjsRFp5apwEByuK+NezCHw yrlQ==
X-Gm-Message-State: AOAM531pdPI4fD8VhPR+dmAo+EBj9gqA4wZigXPvZU7SRv6KVJKXIuCj rZGdrcf2gFQHiI3WqfNb6nz6NaN9uqETLRyi4Gt4hg==
X-Google-Smtp-Source: ABdhPJxxB1cIB1INTu2zmfTRsh2Sd8dyMhE4ureINMLrWK6K4aCckFv1LPf1D6LnNJGDkPz0emXJil5dnE46CP9jCDA=
X-Received: by 2002:a2e:858e:: with SMTP id b14mr411941lji.301.1594845057438;  Wed, 15 Jul 2020 13:30:57 -0700 (PDT)
MIME-Version: 1.0
References: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com> <20200715180231.GB9808@lubuntu> <CAKcm_gPfc3sFy0kuyTzUFk2XFMZ8NdXTd7CuNf0o0v+RXDG=xg@mail.gmail.com>
In-Reply-To: <CAKcm_gPfc3sFy0kuyTzUFk2XFMZ8NdXTd7CuNf0o0v+RXDG=xg@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Wed, 15 Jul 2020 13:30:46 -0700
Message-ID: <CAPDSy+4W7yqyt0musb+R+z6ODwzAhZtUsswbSbuQv5pxH5aDPw@mail.gmail.com>
Subject: Re: Need your help: different connection IDs in the same datagram
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Cc: Martin Thomson <mt@lowentropy.net>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001ed8bd05aa80cde4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/DEXj9MN4LRw3TFgbwKLbTDHCRWY>
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, 15 Jul 2020 20:31:02 -0000

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

As I understand this, the current draft contradicts itself: it allows
senders to coalesce packets with different CIDs, and recommends that
receivers drop them.
I'll second Ian's comment that for us either option will be easy to
implement, but I believe we should fix the contradiction in the draft
before publication.

David

On Wed, Jul 15, 2020 at 12:31 PM Ian Swett <ianswett=
40google.com@dmarc.ietf.org> wrote:

> I don't think this change would be difficult for our implementation, but I
> also don't see it as necessary.  Given where we are in the process, that
> alone argues for not changing it I believe.
>
> On Wed, Jul 15, 2020 at 2:02 PM Dmitri Tikhonov <
> dtikhonov@litespeedtech.com> wrote:
>
>> On Wed, Jul 15, 2020 at 05:23:57PM +1000, Martin Thomson wrote:
>> > There has been some opposition to the proposed resolution in PR 3870.
>> >
>> > Apparently, for some, having multiple connection IDs in the same
>> > datagram complicates processing.  I don't understand this objection.
>> > It seems to me more difficult to retain state across packets than it
>> > is to process each atomically.  I was hoping that Christian or Nick
>> > can explain more about how this affects them.
>>
>> I can provide an example from lsquic.  The datagram is parsed into
>> QUIC packets in one function, lsquic_engine_packet_in():
>>
>>
>> https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_engine.c#L2781L2816
>>
>> Each QUIC packet is processed by process_packet_in(), where a
>> connection is looked up:
>>
>>
>> https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_engine.c#L1352L1360
>>
>> The DCID check is performed lsquic_engine_packet_in(), before
>> process_packet_in() is called:
>>
>>
>> https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_engine.c#L2793L2806
>>
>> The DCID information is readily available in the datagram parsing
>> loop, while connection information is not.
>>
>> For lsquic to support the proposed change, it would have to remember
>> the current connection and then query it whether it is indeed the
>> owner of the next DCID (A) or look up DCID in the global hash (B):
>>
>>     conn = NULL;
>>     while (quic_packet = parse_udp(pointers)) {
>>         dcid = parse(quic_packet);
>>         if (conn)
>>         {
>>   #if VARIANT_A
>>             if (!conn_owns_scid(conn, dcid))
>>   #else
>>             if (conn != lookup_by_dcid(dcid))
>>   #endif
>>                 continue;
>>         }
>>         conn = process_packet(quic_packet);
>>     }
>>
>> Not that it could not be done, of course, but it is both extra work
>> to modify lsquic and a more inefficient mechanism: what was a simple
>> CID comparison is now a hash lookup.
>>
>> That's why I argued [1] for having solid rationale behind the change
>> rather than a personal preference.
>>
>>   - Dmitri.
>>
>> 1.
>> https://github.com/quicwg/base-drafts/issues/3800#issuecomment-656851626
>>
>>

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

<div dir=3D"ltr">As I understand this, the current draft contradicts itself=
: it allows senders to coalesce packets with different CIDs, and recommends=
 that receivers drop them.<div>I&#39;ll second Ian&#39;s comment that for u=
s either option will be easy to implement, but I believe we should fix the =
contradiction in the draft before publication.</div><div><br></div><div>Dav=
id</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmai=
l_attr">On Wed, Jul 15, 2020 at 12:31 PM Ian Swett &lt;ianswett=3D<a href=
=3D"mailto:40google.com@dmarc.ietf.org">40google.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"><div dir=
=3D"ltr">I don&#39;t think this change would be difficult for our implement=
ation, but I also don&#39;t see it as necessary.=C2=A0 Given where we are i=
n the process, that alone argues for not changing it I believe.</div><br><d=
iv class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jul =
15, 2020 at 2:02 PM Dmitri Tikhonov &lt;<a href=3D"mailto:dtikhonov@litespe=
edtech.com" target=3D"_blank">dtikhonov@litespeedtech.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">On Wed, Jul 15, 20=
20 at 05:23:57PM +1000, Martin Thomson wrote:<br>
&gt; There has been some opposition to the proposed resolution in PR 3870.=
=C2=A0 <br>
&gt; <br>
&gt; Apparently, for some, having multiple connection IDs in the same<br>
&gt; datagram complicates processing.=C2=A0 I don&#39;t understand this obj=
ection.<br>
&gt; It seems to me more difficult to retain state across packets than it<b=
r>
&gt; is to process each atomically.=C2=A0 I was hoping that Christian or Ni=
ck<br>
&gt; can explain more about how this affects them.<br>
<br>
I can provide an example from lsquic.=C2=A0 The datagram is parsed into<br>
QUIC packets in one function, lsquic_engine_packet_in():<br>
<br>
=C2=A0 <a href=3D"https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/=
liblsquic/lsquic_engine.c#L2781L2816" rel=3D"noreferrer" target=3D"_blank">=
https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_e=
ngine.c#L2781L2816</a><br>
<br>
Each QUIC packet is processed by process_packet_in(), where a<br>
connection is looked up:<br>
<br>
=C2=A0 <a href=3D"https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/=
liblsquic/lsquic_engine.c#L1352L1360" rel=3D"noreferrer" target=3D"_blank">=
https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_e=
ngine.c#L1352L1360</a><br>
<br>
The DCID check is performed lsquic_engine_packet_in(), before<br>
process_packet_in() is called:<br>
<br>
=C2=A0 <a href=3D"https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/=
liblsquic/lsquic_engine.c#L2793L2806" rel=3D"noreferrer" target=3D"_blank">=
https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_e=
ngine.c#L2793L2806</a><br>
<br>
The DCID information is readily available in the datagram parsing<br>
loop, while connection information is not.<br>
<br>
For lsquic to support the proposed change, it would have to remember<br>
the current connection and then query it whether it is indeed the<br>
owner of the next DCID (A) or look up DCID in the global hash (B):<br>
<br>
=C2=A0 =C2=A0 conn =3D NULL;<br>
=C2=A0 =C2=A0 while (quic_packet =3D parse_udp(pointers)) {<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 dcid =3D parse(quic_packet);<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 if (conn)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 {<br>
=C2=A0 #if VARIANT_A<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 if (!conn_owns_scid(conn, dcid))<=
br>
=C2=A0 #else<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 if (conn !=3D lookup_by_dcid(dcid=
))<br>
=C2=A0 #endif<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 continue;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 }<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 conn =3D process_packet(quic_packet);<br>
=C2=A0 =C2=A0 }<br>
<br>
Not that it could not be done, of course, but it is both extra work<br>
to modify lsquic and a more inefficient mechanism: what was a simple<br>
CID comparison is now a hash lookup.<br>
<br>
That&#39;s why I argued [1] for having solid rationale behind the change<br=
>
rather than a personal preference.<br>
<br>
=C2=A0 - Dmitri.<br>
<br>
1. <a href=3D"https://github.com/quicwg/base-drafts/issues/3800#issuecommen=
t-656851626" rel=3D"noreferrer" target=3D"_blank">https://github.com/quicwg=
/base-drafts/issues/3800#issuecomment-656851626</a><br>
<br>
</blockquote></div>
</blockquote></div>

--0000000000001ed8bd05aa80cde4--


From nobody Wed Jul 15 13:42:52 2020
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 269C43A0FCD for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 13:42:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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=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 u6zE-UrDOcXU for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 13:42:49 -0700 (PDT)
Received: from NAM11-DM6-obe.outbound.protection.outlook.com (mail-dm6nam11on2106.outbound.protection.outlook.com [40.107.223.106]) (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 E50A33A0FC2 for <quic@ietf.org>; Wed, 15 Jul 2020 13:42:48 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=g3SxjcJW3E1eqGO+vnxENu9VLoiSiXxbqRT9YsyiMfY2MzsUiOqDBTk6tqkxwNeBBRVX78yjkVAThAIqeT6vMZ2T2eh+1MDEZw3DlrXHzzkO7QWLOfa9Gm8TttXT59FV+k0JJmwvwhLNYjLN2iVhQoHMVCcbPYBVB1PkUvjRYGrv12SmaOkgBLxuTM0sCR7lVMUDiifoZWCRZy4DfLrWdr7/mDwXwtHLiFKwA/GFBg3hvGr57nnw3eaXlK7nlRJ7RhxoP50Tjf+qti9leZyPvxxzy97z80rZymzB5fagn2rNaSCJHTEP8Hhz6UM3Nc40lSUvDhtLZYWPzv+wiTn3FQ==
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=S62Q9od9rIYEaQRs9Y82CvCfWqiFyok17jWBi0sPQ50=; b=MPDg5KScq55pzTNoz0dX0pbPy/PM3R12Mpg+lr+FNDQq2Dk5yH7KA2iTvKA9di2TcJPwyQLAZoCydqPx3RZn2TRt3WuDeuNzsqWK/fovpLG7MiOjGNU/qM1P2AfBssvEO7uoh2dU7Nm0VZpNIv1kU7cbOuuE5Hinojkb0GK4F1I7CKYpaggfOXKC5m5W2Vyrccwjob3Iod1gVd+iBGTAvTAvifyVcgL7cLIhD8P2vA+CNLZKXjqbQKMzdXUZhbYlX3+huevkRbJJcdSH81ymZ5MdtWXOtRJORLa9a3oeQxVPMqDgQrXtdhTuj0ETCesNmTuNRkQvGho2SfMihcuPbw==
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=S62Q9od9rIYEaQRs9Y82CvCfWqiFyok17jWBi0sPQ50=; b=kMedKzxFSmyrq6wMtkBjEiGFpQGR5y8hL9k2iISgPvfD1gST5kQxjBY6qCH9+efZxRfslna+mT1XWA1fObDmSDX1rOTzpSPMnDbkGWclVkn7XmAxweIcZu83IBpWGp1KRaXSUygpVqSZDVAXUFGcMXE10pQyuN9P9s5khXdY+xA=
Received: from CH2PR22MB2086.namprd22.prod.outlook.com (2603:10b6:610:8c::8) by CH2PR22MB2071.namprd22.prod.outlook.com (2603:10b6:610:5d::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3174.20; Wed, 15 Jul 2020 20:42:47 +0000
Received: from CH2PR22MB2086.namprd22.prod.outlook.com ([fe80::60f5:29ae:6155:6d7e]) by CH2PR22MB2086.namprd22.prod.outlook.com ([fe80::60f5:29ae:6155:6d7e%9]) with mapi id 15.20.3195.018; Wed, 15 Jul 2020 20:42:47 +0000
From: Mike Bishop <mbishop@evequefou.be>
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>, Martin Thomson <mt@lowentropy.net>, IETF QUIC WG <quic@ietf.org>
Subject: RE: Need your help: different connection IDs in the same datagram
Thread-Topic: Need your help: different connection IDs in the same datagram
Thread-Index: AQHWWnkETiF/3SJtf026OFd9pU5BcqkI70YAgAAYswCAAAvogA==
Date: Wed, 15 Jul 2020 20:42:47 +0000
Message-ID: <CH2PR22MB20861D3BEA06EE61AA882245DA7E0@CH2PR22MB2086.namprd22.prod.outlook.com>
References: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com> <20200715180231.GB9808@lubuntu> <CAKcm_gPfc3sFy0kuyTzUFk2XFMZ8NdXTd7CuNf0o0v+RXDG=xg@mail.gmail.com>
In-Reply-To: <CAKcm_gPfc3sFy0kuyTzUFk2XFMZ8NdXTd7CuNf0o0v+RXDG=xg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: dmarc.ietf.org; dkim=none (message not signed) header.d=none;dmarc.ietf.org; dmarc=none action=none header.from=evequefou.be;
x-originating-ip: [72.49.212.17]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: ebfc8414-3479-4dea-234b-08d828ffa204
x-ms-traffictypediagnostic: CH2PR22MB2071:
x-microsoft-antispam-prvs: <CH2PR22MB20715DB26DFC13300F5B009EDA7E0@CH2PR22MB2071.namprd22.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: tsrS7Stbxu7PVtrD0lSdBZB/SjB8ClErfZrqF1g+9lDUjyZ5fHAmmwSr3kTKySf/2mACDfBwRVx4/zDuhkeoY0zOSQMs7p1E7sC8qcn+9S5fVMDV2PubxBs/7yqjBqN3zXagN6/EuzKxp/cUDoJpdK3dsezVc8HtGDv2qyfuF/uVXfPwhhNWIxGh48lBCVcdCms7/9Gkpob49FMj1fpLvf03daZwjx5i2QmU0/rpFzKuckuplAZWMFr4zhsnbQ1n5fwBwF0RkwluE1J3azpn/ETcXDT40ugcT8Wc6txD9X5Bc08KqJXMVhCqSwCm1nOtchjNBTBpkVPeh0YcSVbWZ3zpl2htIhGRtGEJ+32JhyqPBGaq8qa8OSMqHaouGWvZPwtlMSL2litfxOarUPfodYacYaRb8XgMovK64x30iyuGemQQR3mggZVKmATYSipZh2CPtLpNh718yPRHVtXXTw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:CH2PR22MB2086.namprd22.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(346002)(376002)(366004)(396003)(136003)(39830400003)(5660300002)(33656002)(53546011)(55016002)(83380400001)(508600001)(9686003)(6506007)(110136005)(7696005)(76116006)(66946007)(66476007)(64756008)(71200400001)(26005)(66556008)(966005)(8676002)(86362001)(52536014)(186003)(166002)(2906002)(8936002)(316002)(66446008)(151803002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: p/kKqjV8hjbA8eSPgVTgDRGLUZykrUeMMxHXVRbCLpFm3HIFzhxT95frYZQXKWPfVMmuRPS82/Y4n4J2pdBMismVbQO26A3OMM1PBLm45wQTNTM2/iEK9WfFkDmHccviN/MMtchFBXUynZu/pk/CErwOl4P5HuEPLmEBjDU3YKJ2/F78eT1HItbO/koy7Fh5YD6EOvgrX1xTc7Zzvf6qP5pIxZFXQ8BU0+fI0+JcKH9GJvALOhJl/SUgOIQYyd/Kogn2ha33poU/5pxugXK27RQ4kO4pTIKem/A9apLscQ+tev3POj3LELTCAkdcxHH/WBLjE9iuQztQ9bCwjwhRo6640JzFj498aVJGX59sKfgegy4jEOWTfCmJyJaZhZC3Z2Cc6hXMiCH7Q7N2X0q/XUUER18WoDfspMCul+kMJn7yHcBNSrrtUkjlHc56DcRXLwX+iDvrUYLtAY6FRR1YMyEeGGxFm+pRHK1AbfRRP6w=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CH2PR22MB20861D3BEA06EE61AA882245DA7E0CH2PR22MB2086namp_"
MIME-Version: 1.0
X-OriginatorOrg: evequefou.be
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CH2PR22MB2086.namprd22.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ebfc8414-3479-4dea-234b-08d828ffa204
X-MS-Exchange-CrossTenant-originalarrivaltime: 15 Jul 2020 20:42:47.2040 (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: UZ+maGcetyBRo6jJZLsPzqQ09ovDgrZTY07smTMBHglE9zYpHnpTRNHpF5UcYO5W/T1tY/PufpcTGCHmcoO3xw==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR22MB2071
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/quOshGzKbYQof09SQfILImAjiI8>
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, 15 Jul 2020 20:42:51 -0000

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

RnVuZGFtZW50YWxseSwgSSB0aGluayB0aGVyZSBoYXMgdG8gYmUgYSBjaGFuZ2UsIGJlY2F1c2Ug
d2UgY3VycmVudGx5IGhhdmUgYW4gaW5jb25zaXN0ZW50IG1hbmRhdGUg4oCTIG1peGVkLUNJRCBw
YWNrZXRzIGFyZSBhY2NlcHRhYmxlIHRvIHNlbmQsIGJ1dCBTSE9VTEQgYmUgZHJvcHBlZCBvbiBy
ZWNlaXB0Lg0KDQpGaXJzdCwgdGhlcmXigJlzIHRoZSBwcml2YWN5IGFyZ3VtZW50LCBpbiB0aGF0
IHRoZSBDSURzIGluIHRoZSBzYW1lIGRhdGFncmFtIHdpbGwgYmVjb21lIGxpbmtlZCB0byBleHRl
cm5hbCBvYnNlcnZlcnMuICBJIHRoaW5rIE1hcnRlbiBoYXMgYWxyZWFkeSBhcmd1ZWQgY29udmlu
Y2luZ2x5IHdoeSB0aGlzIHdpbGwgYmUgcmFyZSBkdXJpbmcgYSB0eXBpY2FsIGhhbmRzaGFrZTsg
Q2hyaXN0aWFuIGFuZCBLYXp1aG8gaGF2ZSBhcmd1ZWQgdGhhdCBhIHByaXZhY3ktc2Vuc2l0aXZl
IGltcGxlbWVudGF0aW9uIHdpbGwgbmVlZCB0byBkbyBhIENJRCBqdW1wIG9uY2UgdGhlIGhhbmRz
aGFrZSBpcyBjb25maXJtZWQsIGF0IHdoaWNoIHBvaW50IHlvdeKAmXJlIG1vc3RseSBub3QgY29h
bGVzY2luZyBwYWNrZXRzIGFueXdheS4gIFNvIHRoaXMgaXMgYSBtaWxkIGFyZ3VtZW50IGZvciBu
b3QgbWl4aW5nLCBidXQgSSBkb27igJl0IHRoaW5rIGl04oCZcyBkaXNwb3NpdGl2ZS4NCg0KU2Vj
b25kLCB0aGUgaW1wbGVtZW50YXRpb24gYXJndW1lbnRzIGFwcGVhciB0byBib2lsIGRvd24gdG8g
dHdvIGNhbXBzOg0KDQogICogICBJbXBsZW1lbnRhdGlvbiBYIGdlbmVyYXRlcyBwYWNrZXRzIGlu
ZGVwZW5kZW50bHksIHRoZW4gcGFja2FnZXMgdGhlbSBpbnRvIGRhdGFncmFtcy4gIFNpbmNlIGFs
bCBwYWNrZXRzIHdhaXRpbmcgZm9yIHBhY2thZ2luZyBhcmUgZnJvbSB0aGUgc2FtZSBjb25uZWN0
aW9uLCB0aGVyZeKAmXMgY3VycmVudGx5IG5vdGhpbmcgdG8gY2hlY2sgdG8gc2VlIHdoZXRoZXIg
dGhleeKAmXJlIGFsbG93ZWQgaW4gdGhlIHNhbWUgZGF0YWdyYW0uICBSZXF1aXJpbmcgdGhlIENJ
RHMgdG8gbWF0Y2ggd291bGQgcmVxdWlyZSBhIG5ldyBjaGVjayBhbmQgYSBjb2RlIHBhdGggZm9y
IG5vdCBjb2FsZXNjaW5nIHBhY2tldHMgaW4gY2VydGFpbiBjYXNlcy4NCiAgKiAgIEltcGxlbWVu
dGF0aW9uIFkgY29uc3VtZXMgcGFja2V0cyB3aXRoaW4gYSBkYXRhZ3JhbSBpbmRlcGVuZGVudGx5
LCBzbyB0aGUgdmFsaWRhdGlvbiBoYXMgdG8gYmUgZG9uZSBhdCB0aGUgZGF0YWdyYW0gbGV2ZWwg
YmVmb3JlIGRvaW5nIGFueSBwYWNrZXQtbGV2ZWwgYWN0aXZpdGllcy4gIEEgcmVxdWlyZW1lbnQg
dGhhdCBjYW4gYmUgZXZhbHVhdGVkIHNvbGVseSBvbiB0aGUgY29udGVudHMgb2YgdGhlIGRhdGFn
cmFtLCBpbmRlcGVuZGVudCBvZiBhbnkgY29ubmVjdGlvbiBzdGF0ZSwgaXMgbW9yZSBlZmZpY2ll
bnQuDQoNCk9mIHRoZXNlIHR3bywgSSBjdXJyZW50bHkgZmluZCB0aGUgbGF0dGVyIHNsaWdodGx5
IG1vcmUgcGVyc3Vhc2l2ZS4gIFRoZSBmaXJzdCBpcyBhIGNoZWNrIHRoYXQgY2FuIGJlIGRvbmUg
YmV0d2VlbiBwYWNrZXRzIHdpdGhvdXQgbmVlZGluZyB0byBhY2Nlc3MgYW55IGNvbm5lY3Rpb24g
c3RhdGUsIGFuZCB0aGVyZSBhcmUgYWxyZWFkeSBwcmVzdW1hYmx5IGNvZGUgcGF0aHMgZm9yIGhh
bmRsaW5nIHdoZW4gYSB3YWl0aW5nIHBhY2tldCBjYW7igJl0IGdvIGluIHRoZSBkYXRhZ3JhbSBj
dXJyZW50bHkgYmVpbmcgY29uc3RydWN0ZWQgKGUuZy4gaXTigJlzIHRvbyBsYXJnZSB0byBmaXQg
dGhlIHJlbWFpbmluZyBNVFUpLiAgSG93ZXZlciwgSeKAmW0gc3VyZSBzb21lb25lIHdpdGggc3Vj
aCBhbiBpbXBsZW1lbnRhdGlvbiBjb3VsZCB0ZWxsIG1lIHdoeSBpdOKAmXMgbW9yZSBjb21wbGlj
YXRlZCB0aGFuIHRoYXQuICDwn5iKDQoNCk5laXRoZXIgb2YgdGhlIHJlc29sdXRpb25zIHNlZW1z
IG1vcmUgdGVjaG5pY2FsbHkgY29ycmVjdCB0aGFuIHRoZSBvdGhlcjsgd2UganVzdCBuZWVkIHRv
IHBpY2sgb25lLg0KDQpGcm9tOiBRVUlDIDxxdWljLWJvdW5jZXNAaWV0Zi5vcmc+IE9uIEJlaGFs
ZiBPZiBJYW4gU3dldHQNClNlbnQ6IFdlZG5lc2RheSwgSnVseSAxNSwgMjAyMCAzOjMxIFBNDQpU
bzogTWFydGluIFRob21zb24gPG10QGxvd2VudHJvcHkubmV0PjsgSUVURiBRVUlDIFdHIDxxdWlj
QGlldGYub3JnPg0KU3ViamVjdDogUmU6IE5lZWQgeW91ciBoZWxwOiBkaWZmZXJlbnQgY29ubmVj
dGlvbiBJRHMgaW4gdGhlIHNhbWUgZGF0YWdyYW0NCg0KSSBkb24ndCB0aGluayB0aGlzIGNoYW5n
ZSB3b3VsZCBiZSBkaWZmaWN1bHQgZm9yIG91ciBpbXBsZW1lbnRhdGlvbiwgYnV0IEkgYWxzbyBk
b24ndCBzZWUgaXQgYXMgbmVjZXNzYXJ5LiAgR2l2ZW4gd2hlcmUgd2UgYXJlIGluIHRoZSBwcm9j
ZXNzLCB0aGF0IGFsb25lIGFyZ3VlcyBmb3Igbm90IGNoYW5naW5nIGl0IEkgYmVsaWV2ZS4NCg0K
T24gV2VkLCBKdWwgMTUsIDIwMjAgYXQgMjowMiBQTSBEbWl0cmkgVGlraG9ub3YgPGR0aWtob25v
dkBsaXRlc3BlZWR0ZWNoLmNvbTxtYWlsdG86ZHRpa2hvbm92QGxpdGVzcGVlZHRlY2guY29tPj4g
d3JvdGU6DQpPbiBXZWQsIEp1bCAxNSwgMjAyMCBhdCAwNToyMzo1N1BNICsxMDAwLCBNYXJ0aW4g
VGhvbXNvbiB3cm90ZToNCj4gVGhlcmUgaGFzIGJlZW4gc29tZSBvcHBvc2l0aW9uIHRvIHRoZSBw
cm9wb3NlZCByZXNvbHV0aW9uIGluIFBSIDM4NzAuDQo+DQo+IEFwcGFyZW50bHksIGZvciBzb21l
LCBoYXZpbmcgbXVsdGlwbGUgY29ubmVjdGlvbiBJRHMgaW4gdGhlIHNhbWUNCj4gZGF0YWdyYW0g
Y29tcGxpY2F0ZXMgcHJvY2Vzc2luZy4gIEkgZG9uJ3QgdW5kZXJzdGFuZCB0aGlzIG9iamVjdGlv
bi4NCj4gSXQgc2VlbXMgdG8gbWUgbW9yZSBkaWZmaWN1bHQgdG8gcmV0YWluIHN0YXRlIGFjcm9z
cyBwYWNrZXRzIHRoYW4gaXQNCj4gaXMgdG8gcHJvY2VzcyBlYWNoIGF0b21pY2FsbHkuICBJIHdh
cyBob3BpbmcgdGhhdCBDaHJpc3RpYW4gb3IgTmljaw0KPiBjYW4gZXhwbGFpbiBtb3JlIGFib3V0
IGhvdyB0aGlzIGFmZmVjdHMgdGhlbS4NCg0KSSBjYW4gcHJvdmlkZSBhbiBleGFtcGxlIGZyb20g
bHNxdWljLiAgVGhlIGRhdGFncmFtIGlzIHBhcnNlZCBpbnRvDQpRVUlDIHBhY2tldHMgaW4gb25l
IGZ1bmN0aW9uLCBsc3F1aWNfZW5naW5lX3BhY2tldF9pbigpOg0KDQogIGh0dHBzOi8vZ2l0aHVi
LmNvbS9saXRlc3BlZWR0ZWNoL2xzcXVpYy9ibG9iL3YyLjE4LjEvc3JjL2xpYmxzcXVpYy9sc3F1
aWNfZW5naW5lLmMjTDI3ODFMMjgxNg0KDQpFYWNoIFFVSUMgcGFja2V0IGlzIHByb2Nlc3NlZCBi
eSBwcm9jZXNzX3BhY2tldF9pbigpLCB3aGVyZSBhDQpjb25uZWN0aW9uIGlzIGxvb2tlZCB1cDoN
Cg0KICBodHRwczovL2dpdGh1Yi5jb20vbGl0ZXNwZWVkdGVjaC9sc3F1aWMvYmxvYi92Mi4xOC4x
L3NyYy9saWJsc3F1aWMvbHNxdWljX2VuZ2luZS5jI0wxMzUyTDEzNjANCg0KVGhlIERDSUQgY2hl
Y2sgaXMgcGVyZm9ybWVkIGxzcXVpY19lbmdpbmVfcGFja2V0X2luKCksIGJlZm9yZQ0KcHJvY2Vz
c19wYWNrZXRfaW4oKSBpcyBjYWxsZWQ6DQoNCiAgaHR0cHM6Ly9naXRodWIuY29tL2xpdGVzcGVl
ZHRlY2gvbHNxdWljL2Jsb2IvdjIuMTguMS9zcmMvbGlibHNxdWljL2xzcXVpY19lbmdpbmUuYyNM
Mjc5M0wyODA2DQoNClRoZSBEQ0lEIGluZm9ybWF0aW9uIGlzIHJlYWRpbHkgYXZhaWxhYmxlIGlu
IHRoZSBkYXRhZ3JhbSBwYXJzaW5nDQpsb29wLCB3aGlsZSBjb25uZWN0aW9uIGluZm9ybWF0aW9u
IGlzIG5vdC4NCg0KRm9yIGxzcXVpYyB0byBzdXBwb3J0IHRoZSBwcm9wb3NlZCBjaGFuZ2UsIGl0
IHdvdWxkIGhhdmUgdG8gcmVtZW1iZXINCnRoZSBjdXJyZW50IGNvbm5lY3Rpb24gYW5kIHRoZW4g
cXVlcnkgaXQgd2hldGhlciBpdCBpcyBpbmRlZWQgdGhlDQpvd25lciBvZiB0aGUgbmV4dCBEQ0lE
IChBKSBvciBsb29rIHVwIERDSUQgaW4gdGhlIGdsb2JhbCBoYXNoIChCKToNCg0KICAgIGNvbm4g
PSBOVUxMOw0KICAgIHdoaWxlIChxdWljX3BhY2tldCA9IHBhcnNlX3VkcChwb2ludGVycykpIHsN
CiAgICAgICAgZGNpZCA9IHBhcnNlKHF1aWNfcGFja2V0KTsNCiAgICAgICAgaWYgKGNvbm4pDQog
ICAgICAgIHsNCiAgI2lmIFZBUklBTlRfQQ0KICAgICAgICAgICAgaWYgKCFjb25uX293bnNfc2Np
ZChjb25uLCBkY2lkKSkNCiAgI2Vsc2UNCiAgICAgICAgICAgIGlmIChjb25uICE9IGxvb2t1cF9i
eV9kY2lkKGRjaWQpKQ0KICAjZW5kaWYNCiAgICAgICAgICAgICAgICBjb250aW51ZTsNCiAgICAg
ICAgfQ0KICAgICAgICBjb25uID0gcHJvY2Vzc19wYWNrZXQocXVpY19wYWNrZXQpOw0KICAgIH0N
Cg0KTm90IHRoYXQgaXQgY291bGQgbm90IGJlIGRvbmUsIG9mIGNvdXJzZSwgYnV0IGl0IGlzIGJv
dGggZXh0cmEgd29yaw0KdG8gbW9kaWZ5IGxzcXVpYyBhbmQgYSBtb3JlIGluZWZmaWNpZW50IG1l
Y2hhbmlzbTogd2hhdCB3YXMgYSBzaW1wbGUNCkNJRCBjb21wYXJpc29uIGlzIG5vdyBhIGhhc2gg
bG9va3VwLg0KDQpUaGF0J3Mgd2h5IEkgYXJndWVkIFsxXSBmb3IgaGF2aW5nIHNvbGlkIHJhdGlv
bmFsZSBiZWhpbmQgdGhlIGNoYW5nZQ0KcmF0aGVyIHRoYW4gYSBwZXJzb25hbCBwcmVmZXJlbmNl
Lg0KDQogIC0gRG1pdHJpLg0KDQoxLiBodHRwczovL2dpdGh1Yi5jb20vcXVpY3dnL2Jhc2UtZHJh
ZnRzL2lzc3Vlcy8zODAwI2lzc3VlY29tbWVudC02NTY4NTE2MjYNCg==

--_000_CH2PR22MB20861D3BEA06EE61AA882245DA7E0CH2PR22MB2086namp_
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
aXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQpwLk1z
b0xpc3RQYXJhZ3JhcGgsIGxpLk1zb0xpc3RQYXJhZ3JhcGgsIGRpdi5Nc29MaXN0UGFyYWdyYXBo
DQoJe21zby1zdHlsZS1wcmlvcml0eTozNDsNCgltYXJnaW4tdG9wOjBpbjsNCgltYXJnaW4tcmln
aHQ6MGluOw0KCW1hcmdpbi1ib3R0b206MGluOw0KCW1hcmdpbi1sZWZ0Oi41aW47DQoJbWFyZ2lu
LWJvdHRvbTouMDAwMXB0Ow0KCWZvbnQtc2l6ZToxMS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGli
cmkiLHNhbnMtc2VyaWY7fQ0Kc3Bhbi5FbWFpbFN0eWxlMjANCgl7bXNvLXN0eWxlLXR5cGU6cGVy
c29uYWwtY29tcG9zZTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xv
cjp3aW5kb3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1v
bmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCkBwYWdlIFdvcmRTZWN0
aW9uMQ0KCXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4w
aW47fQ0KZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQovKiBMaXN0IERl
ZmluaXRpb25zICovDQpAbGlzdCBsMA0KCXttc28tbGlzdC1pZDoxNDM0NDc2MDQzOw0KCW1zby1s
aXN0LXR5cGU6aHlicmlkOw0KCW1zby1saXN0LXRlbXBsYXRlLWlkczoxMTI2MzU0NTUyIDY3Njk4
Njg5IDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5IDY3Njk4NjkxIDY3Njk4NjkzIDY3Njk4Njg5
IDY3Njk4NjkxIDY3Njk4NjkzO30NCkBsaXN0IGwwOmxldmVsMQ0KCXttc28tbGV2ZWwtbnVtYmVy
LWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ674K3Ow0KCW1zby1sZXZlbC10YWItc3Rv
cDpub25lOw0KCW1zby1sZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDot
LjI1aW47DQoJZm9udC1mYW1pbHk6U3ltYm9sO30NCkBsaXN0IGwwOmxldmVsMg0KCXttc28tbGV2
ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNvLWxldmVsLXRleHQ6bzsNCgltc28tbGV2ZWwt
dGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1p
bmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0KQGxpc3QgbDA6bGV2
ZWwzDQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28tbGV2ZWwtdGV4dDrv
gqc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlv
bjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpXaW5nZGluZ3M7fQ0K
QGxpc3QgbDA6bGV2ZWw0DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxldDsNCgltc28t
bGV2ZWwtdGV4dDrvgrc7DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51
bWJlci1wb3NpdGlvbjpsZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseTpT
eW1ib2w7fQ0KQGxpc3QgbDA6bGV2ZWw1DQoJe21zby1sZXZlbC1udW1iZXItZm9ybWF0OmJ1bGxl
dDsNCgltc28tbGV2ZWwtdGV4dDpvOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1s
ZXZlbC1udW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1m
YW1pbHk6IkNvdXJpZXIgTmV3Ijt9DQpAbGlzdCBsMDpsZXZlbDYNCgl7bXNvLWxldmVsLW51bWJl
ci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CpzsNCgltc28tbGV2ZWwtdGFiLXN0
b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJdGV4dC1pbmRlbnQ6
LS4yNWluOw0KCWZvbnQtZmFtaWx5OldpbmdkaW5nczt9DQpAbGlzdCBsMDpsZXZlbDcNCgl7bXNv
LWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Ou+CtzsNCgltc28t
bGV2ZWwtdGFiLXN0b3A6bm9uZTsNCgltc28tbGV2ZWwtbnVtYmVyLXBvc2l0aW9uOmxlZnQ7DQoJ
dGV4dC1pbmRlbnQ6LS4yNWluOw0KCWZvbnQtZmFtaWx5OlN5bWJvbDt9DQpAbGlzdCBsMDpsZXZl
bDgNCgl7bXNvLWxldmVsLW51bWJlci1mb3JtYXQ6YnVsbGV0Ow0KCW1zby1sZXZlbC10ZXh0Om87
DQoJbXNvLWxldmVsLXRhYi1zdG9wOm5vbmU7DQoJbXNvLWxldmVsLW51bWJlci1wb3NpdGlvbjps
ZWZ0Ow0KCXRleHQtaW5kZW50Oi0uMjVpbjsNCglmb250LWZhbWlseToiQ291cmllciBOZXciO30N
CkBsaXN0IGwwOmxldmVsOQ0KCXttc28tbGV2ZWwtbnVtYmVyLWZvcm1hdDpidWxsZXQ7DQoJbXNv
LWxldmVsLXRleHQ674KnOw0KCW1zby1sZXZlbC10YWItc3RvcDpub25lOw0KCW1zby1sZXZlbC1u
dW1iZXItcG9zaXRpb246bGVmdDsNCgl0ZXh0LWluZGVudDotLjI1aW47DQoJZm9udC1mYW1pbHk6
V2luZ2RpbmdzO30NCm9sDQoJe21hcmdpbi1ib3R0b206MGluO30NCnVsDQoJe21hcmdpbi1ib3R0
b206MGluO30NCi0tPjwvc3R5bGU+PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWRl
ZmF1bHRzIHY6ZXh0PSJlZGl0IiBzcGlkbWF4PSIxMDI2IiAvPg0KPC94bWw+PCFbZW5kaWZdLS0+
PCEtLVtpZiBndGUgbXNvIDldPjx4bWw+DQo8bzpzaGFwZWxheW91dCB2OmV4dD0iZWRpdCI+DQo8
bzppZG1hcCB2OmV4dD0iZWRpdCIgZGF0YT0iMSIgLz4NCjwvbzpzaGFwZWxheW91dD48L3htbD48
IVtlbmRpZl0tLT4NCjwvaGVhZD4NCjxib2R5IGxhbmc9IkVOLVVTIiBsaW5rPSJibHVlIiB2bGlu
az0icHVycGxlIj4NCjxkaXYgY2xhc3M9IldvcmRTZWN0aW9uMSI+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5GdW5kYW1lbnRhbGx5LCBJIHRoaW5rIHRoZXJlIGhhcyB0byBiZSBhIGNoYW5nZSwgYmVj
YXVzZSB3ZSBjdXJyZW50bHkgaGF2ZSBhbiBpbmNvbnNpc3RlbnQgbWFuZGF0ZSDigJMgbWl4ZWQt
Q0lEIHBhY2tldHMgYXJlIGFjY2VwdGFibGUgdG8gc2VuZCwgYnV0IFNIT1VMRCBiZSBkcm9wcGVk
IG9uIHJlY2VpcHQuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkZpcnN0LCB0aGVyZeKAmXMgdGhl
IHByaXZhY3kgYXJndW1lbnQsIGluIHRoYXQgdGhlIENJRHMgaW4gdGhlIHNhbWUgZGF0YWdyYW0g
d2lsbCBiZWNvbWUgbGlua2VkIHRvIGV4dGVybmFsIG9ic2VydmVycy4mbmJzcDsgSSB0aGluayBN
YXJ0ZW4gaGFzIGFscmVhZHkgYXJndWVkIGNvbnZpbmNpbmdseSB3aHkgdGhpcyB3aWxsIGJlIHJh
cmUgZHVyaW5nIGEgdHlwaWNhbCBoYW5kc2hha2U7IENocmlzdGlhbiBhbmQgS2F6dWhvDQogaGF2
ZSBhcmd1ZWQgdGhhdCBhIHByaXZhY3ktc2Vuc2l0aXZlIGltcGxlbWVudGF0aW9uIHdpbGwgbmVl
ZCB0byBkbyBhIENJRCBqdW1wIG9uY2UgdGhlIGhhbmRzaGFrZSBpcyBjb25maXJtZWQsIGF0IHdo
aWNoIHBvaW50IHlvdeKAmXJlIG1vc3RseSBub3QgY29hbGVzY2luZyBwYWNrZXRzIGFueXdheS4m
bmJzcDsgU28gdGhpcyBpcyBhIG1pbGQgYXJndW1lbnQgZm9yIG5vdCBtaXhpbmcsIGJ1dCBJIGRv
buKAmXQgdGhpbmsgaXTigJlzIGRpc3Bvc2l0aXZlLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5T
ZWNvbmQsIHRoZSBpbXBsZW1lbnRhdGlvbiBhcmd1bWVudHMgYXBwZWFyIHRvIGJvaWwgZG93biB0
byB0d28gY2FtcHM6PG86cD48L286cD48L3A+DQo8dWwgc3R5bGU9Im1hcmdpbi10b3A6MGluIiB0
eXBlPSJkaXNjIj4NCjxsaSBjbGFzcz0iTXNvTGlzdFBhcmFncmFwaCIgc3R5bGU9Im1hcmdpbi1s
ZWZ0OjBpbjttc28tbGlzdDpsMCBsZXZlbDEgbGZvMSI+SW1wbGVtZW50YXRpb24gWCBnZW5lcmF0
ZXMgcGFja2V0cyBpbmRlcGVuZGVudGx5LCB0aGVuIHBhY2thZ2VzIHRoZW0gaW50byBkYXRhZ3Jh
bXMuJm5ic3A7IFNpbmNlIGFsbCBwYWNrZXRzIHdhaXRpbmcgZm9yIHBhY2thZ2luZyBhcmUgZnJv
bSB0aGUgc2FtZSBjb25uZWN0aW9uLCB0aGVyZeKAmXMgY3VycmVudGx5IG5vdGhpbmcNCiB0byBj
aGVjayB0byBzZWUgd2hldGhlciB0aGV54oCZcmUgYWxsb3dlZCBpbiB0aGUgc2FtZSBkYXRhZ3Jh
bS4mbmJzcDsgUmVxdWlyaW5nIHRoZSBDSURzIHRvIG1hdGNoIHdvdWxkIHJlcXVpcmUgYSBuZXcg
Y2hlY2sgYW5kIGEgY29kZSBwYXRoIGZvcg0KPGk+bm90PC9pPiBjb2FsZXNjaW5nIHBhY2tldHMg
aW4gY2VydGFpbiBjYXNlcy48bzpwPjwvbzpwPjwvbGk+PGxpIGNsYXNzPSJNc29MaXN0UGFyYWdy
YXBoIiBzdHlsZT0ibWFyZ2luLWxlZnQ6MGluO21zby1saXN0OmwwIGxldmVsMSBsZm8xIj5JbXBs
ZW1lbnRhdGlvbiBZIGNvbnN1bWVzIHBhY2tldHMgd2l0aGluIGEgZGF0YWdyYW0gaW5kZXBlbmRl
bnRseSwgc28gdGhlIHZhbGlkYXRpb24gaGFzIHRvIGJlIGRvbmUgYXQgdGhlIGRhdGFncmFtIGxl
dmVsIGJlZm9yZSBkb2luZyBhbnkgcGFja2V0LWxldmVsIGFjdGl2aXRpZXMuJm5ic3A7IEEgcmVx
dWlyZW1lbnQgdGhhdA0KIGNhbiBiZSBldmFsdWF0ZWQgc29sZWx5IG9uIHRoZSBjb250ZW50cyBv
ZiB0aGUgZGF0YWdyYW0sIGluZGVwZW5kZW50IG9mIGFueSBjb25uZWN0aW9uIHN0YXRlLCBpcyBt
b3JlIGVmZmljaWVudC48bzpwPjwvbzpwPjwvbGk+PC91bD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T2YgdGhlc2UgdHdv
LCBJIGN1cnJlbnRseSBmaW5kIHRoZSBsYXR0ZXIgc2xpZ2h0bHkgbW9yZSBwZXJzdWFzaXZlLiZu
YnNwOyBUaGUgZmlyc3QgaXMgYSBjaGVjayB0aGF0IGNhbiBiZSBkb25lIGJldHdlZW4gcGFja2V0
cyB3aXRob3V0IG5lZWRpbmcgdG8gYWNjZXNzIGFueSBjb25uZWN0aW9uIHN0YXRlLCBhbmQgdGhl
cmUgYXJlIGFscmVhZHkgcHJlc3VtYWJseSBjb2RlIHBhdGhzIGZvciBoYW5kbGluZyB3aGVuIGEg
d2FpdGluZw0KIHBhY2tldCBjYW7igJl0IGdvIGluIHRoZSBkYXRhZ3JhbSBjdXJyZW50bHkgYmVp
bmcgY29uc3RydWN0ZWQgKGUuZy4gaXTigJlzIHRvbyBsYXJnZSB0byBmaXQgdGhlIHJlbWFpbmlu
ZyBNVFUpLiZuYnNwOyBIb3dldmVyLCBJ4oCZbSBzdXJlIHNvbWVvbmUgd2l0aCBzdWNoIGFuIGlt
cGxlbWVudGF0aW9uIGNvdWxkIHRlbGwgbWUgd2h5IGl04oCZcyBtb3JlIGNvbXBsaWNhdGVkIHRo
YW4gdGhhdC4mbmJzcDsNCjxzcGFuIHN0eWxlPSJmb250LWZhbWlseTomcXVvdDtTZWdvZSBVSSBF
bW9qaSZxdW90OyxzYW5zLXNlcmlmIj4mIzEyODUyMjs8L3NwYW4+PG86cD48L286cD48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPk5laXRoZXIgb2YgdGhlIHJlc29sdXRpb25zIHNlZW1zIG1vcmUgdGVjaG5pY2FsbHkg
Y29ycmVjdCB0aGFuIHRoZSBvdGhlcjsgd2UganVzdCBuZWVkIHRvIHBpY2sgb25lLjxvOnA+PC9v
OnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2
IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItdG9wOnNvbGlkICNFMUUxRTEgMS4wcHQ7cGFkZGlu
ZzozLjBwdCAwaW4gMGluIDBpbiI+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48Yj5Gcm9tOjwvYj4g
UVVJQyAmbHQ7cXVpYy1ib3VuY2VzQGlldGYub3JnJmd0OyA8Yj5PbiBCZWhhbGYgT2YgPC9iPg0K
SWFuIFN3ZXR0PGJyPg0KPGI+U2VudDo8L2I+IFdlZG5lc2RheSwgSnVseSAxNSwgMjAyMCAzOjMx
IFBNPGJyPg0KPGI+VG86PC9iPiBNYXJ0aW4gVGhvbXNvbiAmbHQ7bXRAbG93ZW50cm9weS5uZXQm
Z3Q7OyBJRVRGIFFVSUMgV0cgJmx0O3F1aWNAaWV0Zi5vcmcmZ3Q7PGJyPg0KPGI+U3ViamVjdDo8
L2I+IFJlOiBOZWVkIHlvdXIgaGVscDogZGlmZmVyZW50IGNvbm5lY3Rpb24gSURzIGluIHRoZSBz
YW1lIGRhdGFncmFtPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkkgZG9u
J3QgdGhpbmsgdGhpcyBjaGFuZ2Ugd291bGQgYmUgZGlmZmljdWx0IGZvciBvdXIgaW1wbGVtZW50
YXRpb24sIGJ1dCBJIGFsc28gZG9uJ3Qgc2VlIGl0IGFzIG5lY2Vzc2FyeS4mbmJzcDsgR2l2ZW4g
d2hlcmUgd2UgYXJlIGluIHRoZSBwcm9jZXNzLCB0aGF0IGFsb25lIGFyZ3VlcyBmb3Igbm90IGNo
YW5naW5nIGl0IEkgYmVsaWV2ZS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPk9uIFdlZCwgSnVsIDE1LCAyMDIwIGF0IDI6MDIgUE0gRG1pdHJpIFRpa2hvbm92
ICZsdDs8YSBocmVmPSJtYWlsdG86ZHRpa2hvbm92QGxpdGVzcGVlZHRlY2guY29tIj5kdGlraG9u
b3ZAbGl0ZXNwZWVkdGVjaC5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2
Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0ND
Q0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJn
aW4tcmlnaHQ6MGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4tYm90dG9t
OjEyLjBwdCI+T24gV2VkLCBKdWwgMTUsIDIwMjAgYXQgMDU6MjM6NTdQTSAmIzQzOzEwMDAsIE1h
cnRpbiBUaG9tc29uIHdyb3RlOjxicj4NCiZndDsgVGhlcmUgaGFzIGJlZW4gc29tZSBvcHBvc2l0
aW9uIHRvIHRoZSBwcm9wb3NlZCByZXNvbHV0aW9uIGluIFBSIDM4NzAuJm5ic3A7IDxicj4NCiZn
dDsgPGJyPg0KJmd0OyBBcHBhcmVudGx5LCBmb3Igc29tZSwgaGF2aW5nIG11bHRpcGxlIGNvbm5l
Y3Rpb24gSURzIGluIHRoZSBzYW1lPGJyPg0KJmd0OyBkYXRhZ3JhbSBjb21wbGljYXRlcyBwcm9j
ZXNzaW5nLiZuYnNwOyBJIGRvbid0IHVuZGVyc3RhbmQgdGhpcyBvYmplY3Rpb24uPGJyPg0KJmd0
OyBJdCBzZWVtcyB0byBtZSBtb3JlIGRpZmZpY3VsdCB0byByZXRhaW4gc3RhdGUgYWNyb3NzIHBh
Y2tldHMgdGhhbiBpdDxicj4NCiZndDsgaXMgdG8gcHJvY2VzcyBlYWNoIGF0b21pY2FsbHkuJm5i
c3A7IEkgd2FzIGhvcGluZyB0aGF0IENocmlzdGlhbiBvciBOaWNrPGJyPg0KJmd0OyBjYW4gZXhw
bGFpbiBtb3JlIGFib3V0IGhvdyB0aGlzIGFmZmVjdHMgdGhlbS48YnI+DQo8YnI+DQpJIGNhbiBw
cm92aWRlIGFuIGV4YW1wbGUgZnJvbSBsc3F1aWMuJm5ic3A7IFRoZSBkYXRhZ3JhbSBpcyBwYXJz
ZWQgaW50bzxicj4NClFVSUMgcGFja2V0cyBpbiBvbmUgZnVuY3Rpb24sIGxzcXVpY19lbmdpbmVf
cGFja2V0X2luKCk6PGJyPg0KPGJyPg0KJm5ic3A7IDxhIGhyZWY9Imh0dHBzOi8vZ2l0aHViLmNv
bS9saXRlc3BlZWR0ZWNoL2xzcXVpYy9ibG9iL3YyLjE4LjEvc3JjL2xpYmxzcXVpYy9sc3F1aWNf
ZW5naW5lLmMjTDI3ODFMMjgxNiIgdGFyZ2V0PSJfYmxhbmsiPg0KaHR0cHM6Ly9naXRodWIuY29t
L2xpdGVzcGVlZHRlY2gvbHNxdWljL2Jsb2IvdjIuMTguMS9zcmMvbGlibHNxdWljL2xzcXVpY19l
bmdpbmUuYyNMMjc4MUwyODE2PC9hPjxicj4NCjxicj4NCkVhY2ggUVVJQyBwYWNrZXQgaXMgcHJv
Y2Vzc2VkIGJ5IHByb2Nlc3NfcGFja2V0X2luKCksIHdoZXJlIGE8YnI+DQpjb25uZWN0aW9uIGlz
IGxvb2tlZCB1cDo8YnI+DQo8YnI+DQombmJzcDsgPGEgaHJlZj0iaHR0cHM6Ly9naXRodWIuY29t
L2xpdGVzcGVlZHRlY2gvbHNxdWljL2Jsb2IvdjIuMTguMS9zcmMvbGlibHNxdWljL2xzcXVpY19l
bmdpbmUuYyNMMTM1MkwxMzYwIiB0YXJnZXQ9Il9ibGFuayI+DQpodHRwczovL2dpdGh1Yi5jb20v
bGl0ZXNwZWVkdGVjaC9sc3F1aWMvYmxvYi92Mi4xOC4xL3NyYy9saWJsc3F1aWMvbHNxdWljX2Vu
Z2luZS5jI0wxMzUyTDEzNjA8L2E+PGJyPg0KPGJyPg0KVGhlIERDSUQgY2hlY2sgaXMgcGVyZm9y
bWVkIGxzcXVpY19lbmdpbmVfcGFja2V0X2luKCksIGJlZm9yZTxicj4NCnByb2Nlc3NfcGFja2V0
X2luKCkgaXMgY2FsbGVkOjxicj4NCjxicj4NCiZuYnNwOyA8YSBocmVmPSJodHRwczovL2dpdGh1
Yi5jb20vbGl0ZXNwZWVkdGVjaC9sc3F1aWMvYmxvYi92Mi4xOC4xL3NyYy9saWJsc3F1aWMvbHNx
dWljX2VuZ2luZS5jI0wyNzkzTDI4MDYiIHRhcmdldD0iX2JsYW5rIj4NCmh0dHBzOi8vZ2l0aHVi
LmNvbS9saXRlc3BlZWR0ZWNoL2xzcXVpYy9ibG9iL3YyLjE4LjEvc3JjL2xpYmxzcXVpYy9sc3F1
aWNfZW5naW5lLmMjTDI3OTNMMjgwNjwvYT48YnI+DQo8YnI+DQpUaGUgRENJRCBpbmZvcm1hdGlv
biBpcyByZWFkaWx5IGF2YWlsYWJsZSBpbiB0aGUgZGF0YWdyYW0gcGFyc2luZzxicj4NCmxvb3As
IHdoaWxlIGNvbm5lY3Rpb24gaW5mb3JtYXRpb24gaXMgbm90Ljxicj4NCjxicj4NCkZvciBsc3F1
aWMgdG8gc3VwcG9ydCB0aGUgcHJvcG9zZWQgY2hhbmdlLCBpdCB3b3VsZCBoYXZlIHRvIHJlbWVt
YmVyPGJyPg0KdGhlIGN1cnJlbnQgY29ubmVjdGlvbiBhbmQgdGhlbiBxdWVyeSBpdCB3aGV0aGVy
IGl0IGlzIGluZGVlZCB0aGU8YnI+DQpvd25lciBvZiB0aGUgbmV4dCBEQ0lEIChBKSBvciBsb29r
IHVwIERDSUQgaW4gdGhlIGdsb2JhbCBoYXNoIChCKTo8YnI+DQo8YnI+DQombmJzcDsgJm5ic3A7
IGNvbm4gPSBOVUxMOzxicj4NCiZuYnNwOyAmbmJzcDsgd2hpbGUgKHF1aWNfcGFja2V0ID0gcGFy
c2VfdWRwKHBvaW50ZXJzKSkgezxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBkY2lk
ID0gcGFyc2UocXVpY19wYWNrZXQpOzxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBp
ZiAoY29ubik8YnI+DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgezxicj4NCiZuYnNwOyAj
aWYgVkFSSUFOVF9BPGJyPg0KJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJz
cDsgaWYgKCFjb25uX293bnNfc2NpZChjb25uLCBkY2lkKSk8YnI+DQombmJzcDsgI2Vsc2U8YnI+
DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBpZiAoY29ubiAhPSBs
b29rdXBfYnlfZGNpZChkY2lkKSk8YnI+DQombmJzcDsgI2VuZGlmPGJyPg0KJm5ic3A7ICZuYnNw
OyAmbmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgJm5ic3A7ICZuYnNwOyBjb250aW51ZTs8YnI+
DQombmJzcDsgJm5ic3A7ICZuYnNwOyAmbmJzcDsgfTxicj4NCiZuYnNwOyAmbmJzcDsgJm5ic3A7
ICZuYnNwOyBjb25uID0gcHJvY2Vzc19wYWNrZXQocXVpY19wYWNrZXQpOzxicj4NCiZuYnNwOyAm
bmJzcDsgfTxicj4NCjxicj4NCk5vdCB0aGF0IGl0IGNvdWxkIG5vdCBiZSBkb25lLCBvZiBjb3Vy
c2UsIGJ1dCBpdCBpcyBib3RoIGV4dHJhIHdvcms8YnI+DQp0byBtb2RpZnkgbHNxdWljIGFuZCBh
IG1vcmUgaW5lZmZpY2llbnQgbWVjaGFuaXNtOiB3aGF0IHdhcyBhIHNpbXBsZTxicj4NCkNJRCBj
b21wYXJpc29uIGlzIG5vdyBhIGhhc2ggbG9va3VwLjxicj4NCjxicj4NClRoYXQncyB3aHkgSSBh
cmd1ZWQgWzFdIGZvciBoYXZpbmcgc29saWQgcmF0aW9uYWxlIGJlaGluZCB0aGUgY2hhbmdlPGJy
Pg0KcmF0aGVyIHRoYW4gYSBwZXJzb25hbCBwcmVmZXJlbmNlLjxicj4NCjxicj4NCiZuYnNwOyAt
IERtaXRyaS48YnI+DQo8YnI+DQoxLiA8YSBocmVmPSJodHRwczovL2dpdGh1Yi5jb20vcXVpY3dn
L2Jhc2UtZHJhZnRzL2lzc3Vlcy8zODAwI2lzc3VlY29tbWVudC02NTY4NTE2MjYiIHRhcmdldD0i
X2JsYW5rIj4NCmh0dHBzOi8vZ2l0aHViLmNvbS9xdWljd2cvYmFzZS1kcmFmdHMvaXNzdWVzLzM4
MDAjaXNzdWVjb21tZW50LTY1Njg1MTYyNjwvYT48bzpwPjwvbzpwPjwvcD4NCjwvYmxvY2txdW90
ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8L2JvZHk+DQo8L2h0bWw+DQo=

--_000_CH2PR22MB20861D3BEA06EE61AA882245DA7E0CH2PR22MB2086namp_--


From nobody Wed Jul 15 14:17:35 2020
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 EF1223A088F for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 14:17:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level: 
X-Spam-Status: No, score=-17.599 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, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, 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 g-5nvOmN0iUJ for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 14:17:30 -0700 (PDT)
Received: from mail-yb1-xb2c.google.com (mail-yb1-xb2c.google.com [IPv6:2607:f8b0:4864:20::b2c]) (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 6BC563A0885 for <quic@ietf.org>; Wed, 15 Jul 2020 14:17:30 -0700 (PDT)
Received: by mail-yb1-xb2c.google.com with SMTP id y13so1808951ybj.10 for <quic@ietf.org>; Wed, 15 Jul 2020 14:17:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=SUuL6CYRKpqR2IJ6P8MPSo2fVhAC/vrQru1vHmT9374=; b=HfF2lvu7ECaeKsA3EvkNF9Qyyv7a0/BzXwlowO7G0M5UnbBCLjR7YU1TIYSWTlJ28V 0Fq99v/wv3GexfYzbwUNxV+/I5kv7zppNq2zVzISvGtHaeGssIRhjzCm/R1Ziwufj53f h8PHJ3LjtBUatjaRLjsy1SLPnqNpINwnDx1TOkUL3ueYhwdaRiNT/TKbb+Do+X9WDEKu S33vqDhVMRkvzu3vpJ6QoBBraD+Y8fTyHz9nznsqpWaOO7dmY28UN6LLTUmE25uFwVKV TcPAUfTK72zBcpMr6nPBoVjnea7+K1TJGXf/DJKCZfmzf/0W+i3oJBrY1L1ZuVvF5h4q h0jg==
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=SUuL6CYRKpqR2IJ6P8MPSo2fVhAC/vrQru1vHmT9374=; b=iZVJJgnj1RLFNoIMpAwC96XgI/4yw9RqMmPQf+GfYcxwq9DDTzAmYVtUQ115lUegSv E2FSG5GSemKPsmlgWqr7c2BnX/8FrfSnwvjqtM/kYPRLZrOl6da0i//27riUm24c8CSr PbXHXx9Q+jGHiNVm1UULENTHZSrdnKKbgNS2gKamjOMuKlwnFqXfgZIOCm7ZpVnPsbLj CyFpLyZVW8b4BCl9F8LujGzjiSrulIGoziW9gT2d0ywEx+oZ8Wukeyj+8zAu/g8nnqDV h+SaX0GjAEQVHuIljU9OphweOjxoH21Qc4U1m5AMr6WprynqFGTzbIEXkJLewZHJfe6J ekPw==
X-Gm-Message-State: AOAM533iUkVFWA/Aa/lcFO8R2rQNH1z5Qdo/HAJ5dNDZAm6dnzeUpM91 QhCbkWodMH0eupN8DmoDEE6fzCV8ASXPsbeXhcHn/gcE
X-Google-Smtp-Source: ABdhPJyPhqY0Z7tCTlaAnB/4g1zocHVTFzywp3K+lGlyNLINNWZzwtzkUGXeLixpbKcmsIGJQvDAq/7w7cSTlvvQ50E=
X-Received: by 2002:a25:b78a:: with SMTP id n10mr1463574ybh.494.1594847849274;  Wed, 15 Jul 2020 14:17:29 -0700 (PDT)
MIME-Version: 1.0
References: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com> <20200715180231.GB9808@lubuntu> <CAKcm_gPfc3sFy0kuyTzUFk2XFMZ8NdXTd7CuNf0o0v+RXDG=xg@mail.gmail.com> <CH2PR22MB20861D3BEA06EE61AA882245DA7E0@CH2PR22MB2086.namprd22.prod.outlook.com>
In-Reply-To: <CH2PR22MB20861D3BEA06EE61AA882245DA7E0@CH2PR22MB2086.namprd22.prod.outlook.com>
From: Ian Swett <ianswett@google.com>
Date: Wed, 15 Jul 2020 17:17:18 -0400
Message-ID: <CAKcm_gP24=x64QwcCdki-jxFXsLKiTPH8UYFdGOG3H1YJgEbOQ@mail.gmail.com>
Subject: Re: Need your help: different connection IDs in the same datagram
To: Mike Bishop <mbishop@evequefou.be>
Cc: Martin Thomson <mt@lowentropy.net>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000087508605aa8173bd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/b0o4nwxWhZbdjYEG78HIK861VZA>
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, 15 Jul 2020 21:17:33 -0000

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

I forgot there's a contradiction, because I thought we disallowed sending
mixed-CID packets.  So I'd prefer changing to MUST NOT coalesce packets
with different CIDs.  Even if you generate them and then coalesce
them(which we do), that's not that hard to enforce in the coalescing code.

On Wed, Jul 15, 2020 at 4:42 PM Mike Bishop <mbishop@evequefou.be> wrote:

> Fundamentally, I think there has to be a change, because we currently hav=
e
> an inconsistent mandate =E2=80=93 mixed-CID packets are acceptable to sen=
d, but
> SHOULD be dropped on receipt.
>
>
>
> First, there=E2=80=99s the privacy argument, in that the CIDs in the same=
 datagram
> will become linked to external observers.  I think Marten has already
> argued convincingly why this will be rare during a typical handshake;
> Christian and Kazuho have argued that a privacy-sensitive implementation
> will need to do a CID jump once the handshake is confirmed, at which poin=
t
> you=E2=80=99re mostly not coalescing packets anyway.  So this is a mild a=
rgument
> for not mixing, but I don=E2=80=99t think it=E2=80=99s dispositive.
>
>
>
> Second, the implementation arguments appear to boil down to two camps:
>
>    - Implementation X generates packets independently, then packages them
>    into datagrams.  Since all packets waiting for packaging are from the =
same
>    connection, there=E2=80=99s currently nothing to check to see whether =
they=E2=80=99re
>    allowed in the same datagram.  Requiring the CIDs to match would requi=
re a
>    new check and a code path for *not* coalescing packets in certain
>    cases.
>    - Implementation Y consumes packets within a datagram independently,
>    so the validation has to be done at the datagram level before doing an=
y
>    packet-level activities.  A requirement that can be evaluated solely o=
n the
>    contents of the datagram, independent of any connection state, is more
>    efficient.
>
>
>
> Of these two, I currently find the latter slightly more persuasive.  The
> first is a check that can be done between packets without needing to acce=
ss
> any connection state, and there are already presumably code paths for
> handling when a waiting packet can=E2=80=99t go in the datagram currently=
 being
> constructed (e.g. it=E2=80=99s too large to fit the remaining MTU).  Howe=
ver, I=E2=80=99m
> sure someone with such an implementation could tell me why it=E2=80=99s m=
ore
> complicated than that.  =F0=9F=98=8A
>
>
>
> Neither of the resolutions seems more technically correct than the other;
> we just need to pick one.
>
>
>
> *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of * Ian Swett
> *Sent:* Wednesday, July 15, 2020 3:31 PM
> *To:* Martin Thomson <mt@lowentropy.net>; IETF QUIC WG <quic@ietf.org>
> *Subject:* Re: Need your help: different connection IDs in the same
> datagram
>
>
>
> I don't think this change would be difficult for our implementation, but =
I
> also don't see it as necessary.  Given where we are in the process, that
> alone argues for not changing it I believe.
>
>
>
> On Wed, Jul 15, 2020 at 2:02 PM Dmitri Tikhonov <
> dtikhonov@litespeedtech.com> wrote:
>
> On Wed, Jul 15, 2020 at 05:23:57PM +1000, Martin Thomson wrote:
> > There has been some opposition to the proposed resolution in PR 3870.
> >
> > Apparently, for some, having multiple connection IDs in the same
> > datagram complicates processing.  I don't understand this objection.
> > It seems to me more difficult to retain state across packets than it
> > is to process each atomically.  I was hoping that Christian or Nick
> > can explain more about how this affects them.
>
> I can provide an example from lsquic.  The datagram is parsed into
> QUIC packets in one function, lsquic_engine_packet_in():
>
>
> https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic=
_engine.c#L2781L2816
>
> Each QUIC packet is processed by process_packet_in(), where a
> connection is looked up:
>
>
> https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic=
_engine.c#L1352L1360
>
> The DCID check is performed lsquic_engine_packet_in(), before
> process_packet_in() is called:
>
>
> https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic=
_engine.c#L2793L2806
>
> The DCID information is readily available in the datagram parsing
> loop, while connection information is not.
>
> For lsquic to support the proposed change, it would have to remember
> the current connection and then query it whether it is indeed the
> owner of the next DCID (A) or look up DCID in the global hash (B):
>
>     conn =3D NULL;
>     while (quic_packet =3D parse_udp(pointers)) {
>         dcid =3D parse(quic_packet);
>         if (conn)
>         {
>   #if VARIANT_A
>             if (!conn_owns_scid(conn, dcid))
>   #else
>             if (conn !=3D lookup_by_dcid(dcid))
>   #endif
>                 continue;
>         }
>         conn =3D process_packet(quic_packet);
>     }
>
> Not that it could not be done, of course, but it is both extra work
> to modify lsquic and a more inefficient mechanism: what was a simple
> CID comparison is now a hash lookup.
>
> That's why I argued [1] for having solid rationale behind the change
> rather than a personal preference.
>
>   - Dmitri.
>
> 1.
> https://github.com/quicwg/base-drafts/issues/3800#issuecomment-656851626
>
>

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

<div dir=3D"ltr">I forgot there&#39;s a contradiction, because I thought we=
 disallowed sending mixed-CID packets.=C2=A0 So I&#39;d prefer changing to =
MUST NOT coalesce packets with different CIDs.=C2=A0 Even if you generate t=
hem and then coalesce them(which we do), that&#39;s not that hard to enforc=
e in the coalescing code.</div><br><div class=3D"gmail_quote"><div dir=3D"l=
tr" class=3D"gmail_attr">On Wed, Jul 15, 2020 at 4:42 PM Mike Bishop &lt;<a=
 href=3D"mailto:mbishop@evequefou.be">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">





<div lang=3D"EN-US">
<div class=3D"gmail-m_-8679299339673560188WordSection1">
<p class=3D"MsoNormal">Fundamentally, I think there has to be a change, bec=
ause we currently have an inconsistent mandate =E2=80=93 mixed-CID packets =
are acceptable to send, but SHOULD be dropped on receipt.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">First, there=E2=80=99s the privacy argument, in that=
 the CIDs in the same datagram will become linked to external observers.=C2=
=A0 I think Marten has already argued convincingly why this will be rare du=
ring a typical handshake; Christian and Kazuho
 have argued that a privacy-sensitive implementation will need to do a CID =
jump once the handshake is confirmed, at which point you=E2=80=99re mostly =
not coalescing packets anyway.=C2=A0 So this is a mild argument for not mix=
ing, but I don=E2=80=99t think it=E2=80=99s dispositive.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Second, the implementation arguments appear to boil =
down to two camps:<u></u><u></u></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"gmail-m_-8679299339673560188MsoListParagraph" style=3D"margin-=
left:0in">Implementation X generates packets independently, then packages t=
hem into datagrams.=C2=A0 Since all packets waiting for packaging are from =
the same connection, there=E2=80=99s currently nothing
 to check to see whether they=E2=80=99re allowed in the same datagram.=C2=
=A0 Requiring the CIDs to match would require a new check and a code path f=
or
<i>not</i> coalescing packets in certain cases.<u></u><u></u></li><li class=
=3D"gmail-m_-8679299339673560188MsoListParagraph" style=3D"margin-left:0in"=
>Implementation Y consumes packets within a datagram independently, so the =
validation has to be done at the datagram level before doing any packet-lev=
el activities.=C2=A0 A requirement that
 can be evaluated solely on the contents of the datagram, independent of an=
y connection state, is more efficient.<u></u><u></u></li></ul>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Of these two, I currently find the latter slightly m=
ore persuasive.=C2=A0 The first is a check that can be done between packets=
 without needing to access any connection state, and there are already pres=
umably code paths for handling when a waiting
 packet can=E2=80=99t go in the datagram currently being constructed (e.g. =
it=E2=80=99s too large to fit the remaining MTU).=C2=A0 However, I=E2=80=99=
m sure someone with such an implementation could tell me why it=E2=80=99s m=
ore complicated than that.=C2=A0
<span style=3D"font-family:&quot;Segoe UI Emoji&quot;,sans-serif">=F0=9F=98=
=8A</span><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Neither of the resolutions seems more technically co=
rrect than the other; we just need to pick one.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<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>
Ian Swett<br>
<b>Sent:</b> Wednesday, July 15, 2020 3:31 PM<br>
<b>To:</b> Martin Thomson &lt;<a href=3D"mailto:mt@lowentropy.net" target=
=3D"_blank">mt@lowentropy.net</a>&gt;; IETF QUIC WG &lt;<a href=3D"mailto:q=
uic@ietf.org" target=3D"_blank">quic@ietf.org</a>&gt;<br>
<b>Subject:</b> Re: Need your help: different connection IDs in the same da=
tagram<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">I don&#39;t think this change would be difficult for=
 our implementation, but I also don&#39;t see it as necessary.=C2=A0 Given =
where we are in the process, that alone argues for not changing it I believ=
e.<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Wed, Jul 15, 2020 at 2:02 PM Dmitri Tikhonov &lt;=
<a href=3D"mailto:dtikhonov@litespeedtech.com" target=3D"_blank">dtikhonov@=
litespeedtech.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">
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt">On Wed, Jul 15, 2020 at=
 05:23:57PM +1000, Martin Thomson wrote:<br>
&gt; There has been some opposition to the proposed resolution in PR 3870.=
=C2=A0 <br>
&gt; <br>
&gt; Apparently, for some, having multiple connection IDs in the same<br>
&gt; datagram complicates processing.=C2=A0 I don&#39;t understand this obj=
ection.<br>
&gt; It seems to me more difficult to retain state across packets than it<b=
r>
&gt; is to process each atomically.=C2=A0 I was hoping that Christian or Ni=
ck<br>
&gt; can explain more about how this affects them.<br>
<br>
I can provide an example from lsquic.=C2=A0 The datagram is parsed into<br>
QUIC packets in one function, lsquic_engine_packet_in():<br>
<br>
=C2=A0 <a href=3D"https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/=
liblsquic/lsquic_engine.c#L2781L2816" target=3D"_blank">
https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_e=
ngine.c#L2781L2816</a><br>
<br>
Each QUIC packet is processed by process_packet_in(), where a<br>
connection is looked up:<br>
<br>
=C2=A0 <a href=3D"https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/=
liblsquic/lsquic_engine.c#L1352L1360" target=3D"_blank">
https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_e=
ngine.c#L1352L1360</a><br>
<br>
The DCID check is performed lsquic_engine_packet_in(), before<br>
process_packet_in() is called:<br>
<br>
=C2=A0 <a href=3D"https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/=
liblsquic/lsquic_engine.c#L2793L2806" target=3D"_blank">
https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_e=
ngine.c#L2793L2806</a><br>
<br>
The DCID information is readily available in the datagram parsing<br>
loop, while connection information is not.<br>
<br>
For lsquic to support the proposed change, it would have to remember<br>
the current connection and then query it whether it is indeed the<br>
owner of the next DCID (A) or look up DCID in the global hash (B):<br>
<br>
=C2=A0 =C2=A0 conn =3D NULL;<br>
=C2=A0 =C2=A0 while (quic_packet =3D parse_udp(pointers)) {<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 dcid =3D parse(quic_packet);<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 if (conn)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 {<br>
=C2=A0 #if VARIANT_A<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 if (!conn_owns_scid(conn, dcid))<=
br>
=C2=A0 #else<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 if (conn !=3D lookup_by_dcid(dcid=
))<br>
=C2=A0 #endif<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 continue;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 }<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 conn =3D process_packet(quic_packet);<br>
=C2=A0 =C2=A0 }<br>
<br>
Not that it could not be done, of course, but it is both extra work<br>
to modify lsquic and a more inefficient mechanism: what was a simple<br>
CID comparison is now a hash lookup.<br>
<br>
That&#39;s why I argued [1] for having solid rationale behind the change<br=
>
rather than a personal preference.<br>
<br>
=C2=A0 - Dmitri.<br>
<br>
1. <a href=3D"https://github.com/quicwg/base-drafts/issues/3800#issuecommen=
t-656851626" target=3D"_blank">
https://github.com/quicwg/base-drafts/issues/3800#issuecomment-656851626</a=
><u></u><u></u></p>
</blockquote>
</div>
</div>
</div>

</blockquote></div>

--00000000000087508605aa8173bd--


From nobody Wed Jul 15 14:31:20 2020
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 D706F3A0994 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 14:31:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 nPzspBZ1587S for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 14:31:17 -0700 (PDT)
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 346AB3A0993 for <quic@ietf.org>; Wed, 15 Jul 2020 14:31:17 -0700 (PDT)
Received: by mail-lf1-x135.google.com with SMTP id k15so1932470lfc.4 for <quic@ietf.org>; Wed, 15 Jul 2020 14:31:17 -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=Vj+nW3WYzbnP7sPD0GCoUvxu0WqLb/IVVnZwE+wCBzc=; b=PHD2b94HEX/cviOvH3HzolHTY+bHVG79zPjdePdgqChGfjUcmskKwcOTwsknLNKGcO zw493GFQJdDkB6SLxXKbYMdxWJ5ikyv39Oquscuj71mjvUo/huCl2X8JJDSo3C41RQVX GvLySA6BA2uPUN7EMRzg44rpHyW3F8yj0OgSirzTD+vuDqqDgDc+2gH3s2evzQAvsZC3 6gwVReou1HT9YoEzBvlhbXIEhDHZt2wXQn8orBr7ViS90ZId3HULEoCSW94B5vlcjOZW 8z5uicDYsFOIgfvGUn3odvnkHCSpKQenj32GyXoCx1MCAJM6SI4ZIskyZFmPqem0Cfsm vKZA==
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=Vj+nW3WYzbnP7sPD0GCoUvxu0WqLb/IVVnZwE+wCBzc=; b=blMptefNukBqbmKlGfgfna3hOqXt4XGM9xnNTb5aySkn9omEq9tW9dPEJBHom5tH3N EIaIu83rrGP8upr9IJt2lqa64/ACNIQLEC18WraAXUxqbOG+iovds4AeDK9XptdwPIjY EJZCxUluNM4kPcU0q1VyT8zwf450kp3OEG0FckHvTkQ8xKHJvXbcnOqxIBIZwlCQxbkc 2cnmuDVP77OdUsISQQVghOGWa6QZBz/Jm14ihu+FcFN2F0LO/ZAUCNEs57MIoo7cTApY BFaQy68vFSbUdGEkyGGM8R4nrqa1xd7y1G6z+5P9Af0vUErYps/DLRHsoLQ5MU2YqKVK uLLg==
X-Gm-Message-State: AOAM53239/rTqbI+Ag/FH/mw3xyXXGUH78Wx6t7hVDKnlCEFBoG209r8 m55JsPYDRq+90t0H0LqF91zCDuQmzfKcjSXBj91IAA==
X-Google-Smtp-Source: ABdhPJwga6BA0QK4Siw/xQMQbfB6yS+HCg1Zqc2lhkXDKOMlUstR6EgQBPMNpAmlmglmqZJ25U69l4BWXs2Wr2DRDks=
X-Received: by 2002:a19:bc2:: with SMTP id 185mr476352lfl.204.1594848675290; Wed, 15 Jul 2020 14:31:15 -0700 (PDT)
MIME-Version: 1.0
References: <1A5A359E-7F46-49E0-BCFB-65EE718BBF63@eggert.org>
In-Reply-To: <1A5A359E-7F46-49E0-BCFB-65EE718BBF63@eggert.org>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Wed, 15 Jul 2020 14:31:04 -0700
Message-ID: <CAPDSy+7PxSuapjyDDqSf-Tfmrg246J8z6Tsm2Aayjp32EC_6jg@mail.gmail.com>
Subject: Re: Doodle poll for -29 virtual interop event
To: Lars Eggert <lars@eggert.org>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c2e2cd05aa81a494"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/6PCG2dkdq0MNw8__sviGr5PC23w>
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, 15 Jul 2020 21:31:19 -0000

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

Silly question: did I miss the email about when the draft-29 virtual
interop will take place?

David

On Thu, Jun 25, 2020 at 11:50 PM Lars Eggert <lars@eggert.org> wrote:

> Hi,
>
> please fill out https://doodle.com/poll/rif4gd4ib9he2kqc to find the best
> day(s) for a virtual interop on the -29 drafts.
>
> Thanks,
> Lars
>

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

<div dir=3D"ltr">Silly question: did I miss the email about when the draft-=
29 virtual interop will take=C2=A0place?<div><br></div><div>David</div></di=
v><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On T=
hu, Jun 25, 2020 at 11:50 PM Lars Eggert &lt;<a href=3D"mailto:lars@eggert.=
org">lars@eggert.org</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">Hi,<br>
<br>
please fill out <a href=3D"https://doodle.com/poll/rif4gd4ib9he2kqc" rel=3D=
"noreferrer" target=3D"_blank">https://doodle.com/poll/rif4gd4ib9he2kqc</a>=
 to find the best day(s) for a virtual interop on the -29 drafts.<br>
<br>
Thanks,<br>
Lars<br>
</blockquote></div>

--000000000000c2e2cd05aa81a494--


From nobody Wed Jul 15 14:36:33 2020
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 0552D3A0A16 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 14:36:32 -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, 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 Ju6WygXNLm7J for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 14:36:30 -0700 (PDT)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 3B1FB3A0A5E for <quic@ietf.org>; Wed, 15 Jul 2020 14:36:30 -0700 (PDT)
Received: by mail-qt1-x82b.google.com with SMTP id j10so3053315qtq.11 for <quic@ietf.org>; Wed, 15 Jul 2020 14:36:30 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=lp1r1uZFbPutPUVGtqAd7J4wAeTTC40HK0eXv1E0Q0I=; b=hI5+M7QeUK1OS3m2lxV44fp9ZogRr7Jv9B5556Z9tvMthrUhrX595PgH8yxbNjKLPo pf6FivCru94DEhJexTj2HyrNqIdrNASs00/w/7h1VvJ3NOxCeqiwN/62kbQ4A17UzK2r X0FtrmQ3Tw4SvMU9SsuQdM1iovAflGksCst8D/jT7qWGkvjAivDhpdzrfK1taR1eP/Ss wVWSEwAV0TjlGeimAM2haBbdQL1Xg9ZekiCDv3vS3JwaH0p248JAdes0608QmGKMgxvW RybnReYRcyDIUxRiKN+HluADwyY822v2IRrAbcqqV1ScZESz3ooQLJZsqdpSDR+M/viU ANZw==
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=lp1r1uZFbPutPUVGtqAd7J4wAeTTC40HK0eXv1E0Q0I=; b=sMVKOJengpazcVk8WxTn+YUghJivouePn7NpM6vlwx5gDmDeOu/vyuHZyI/1ycPuoH 9tGYGM/1NGmghz7xLG+EEG7zF3kg3t9SPMql4Z1OySMa7N9FfUTR8UgcyXHmO2t3s5Nb jGszoOYqBsTDLztRulyWDuRp3wq+ZcYZ59WatP7uav+naV+hHYROu3VdsTFOywNGGpD5 JVlLJFJLlEUYrqFGG4Ge0L75tsI1ykqSqexJ63E/adPYbh5iuAgInp/1l853L9wC1hYJ KTgQUarVRH+YjwiZBwpgCkREirgyjpwcgt507AYhXDvSl1FLladT2/vBzvi4M0gOisW6 pCeg==
X-Gm-Message-State: AOAM531UByAoYVgerOpEZEyZA0wtx71VTTjDD1NApK/8CG2+nieTGABM fo/WDGc7oWgj+W7UIZzluGBjJg==
X-Google-Smtp-Source: ABdhPJyj2MH4x0ogvURjI9FdEgPEicWT391rQ0005ZlpdHxHhD2psB+vTZj54I9X5MI5sjUcMWMBSg==
X-Received: by 2002:ac8:1baf:: with SMTP id z44mr2012273qtj.129.1594848989119;  Wed, 15 Jul 2020 14:36:29 -0700 (PDT)
Received: from lubuntu (ool-44c1d219.dyn.optonline.net. [68.193.210.25]) by smtp.gmail.com with ESMTPSA id t57sm4703849qtc.91.2020.07.15.14.36.28 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 15 Jul 2020 14:36:28 -0700 (PDT)
Date: Wed, 15 Jul 2020 17:36:24 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: David Schinazi <dschinazi.ietf@gmail.com>
Cc: Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
Subject: Re: Doodle poll for -29 virtual interop event
Message-ID: <20200715213623.GC9808@lubuntu>
Mail-Followup-To: David Schinazi <dschinazi.ietf@gmail.com>, Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
References: <1A5A359E-7F46-49E0-BCFB-65EE718BBF63@eggert.org> <CAPDSy+7PxSuapjyDDqSf-Tfmrg246J8z6Tsm2Aayjp32EC_6jg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAPDSy+7PxSuapjyDDqSf-Tfmrg246J8z6Tsm2Aayjp32EC_6jg@mail.gmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/wnW2GGIx9IxICUNn5W1FcVRyeY8>
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, 15 Jul 2020 21:36:32 -0000

I don't think it was ever sent; at least, I missed it, too.

  - Dmitri.

On Wed, Jul 15, 2020 at 02:31:04PM -0700, David Schinazi wrote:
> Silly question: did I miss the email about when the draft-29 virtual
> interop will take place?
> 
> David
> 
> On Thu, Jun 25, 2020 at 11:50 PM Lars Eggert <lars@eggert.org> wrote:
> 
> > Hi,
> >
> > please fill out https://doodle.com/poll/rif4gd4ib9he2kqc to find the best
> > day(s) for a virtual interop on the -29 drafts.
> >
> > Thanks,
> > Lars
> >


From nobody Wed Jul 15 14:48:27 2020
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 D26153A0C12 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 14:48:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.847
X-Spam-Level: 
X-Spam-Status: No, score=-1.847 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 ZfSTDncGLVwR for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 14:48:24 -0700 (PDT)
Received: from mail-wm1-x332.google.com (mail-wm1-x332.google.com [IPv6:2a00:1450:4864:20::332]) (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 4C65C3A0C0D for <quic@ietf.org>; Wed, 15 Jul 2020 14:48:24 -0700 (PDT)
Received: by mail-wm1-x332.google.com with SMTP id f18so7719770wml.3 for <quic@ietf.org>; Wed, 15 Jul 2020 14:48:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to;  bh=bSRDzuJdcguHhZXJuZfu48krR66xgZFnmufM99P3Yls=; b=odn1XqN8z/43HC19Y9Ls2cXWTRCIvtbdFnwaDtH5sDYfnz7yqZE05zOZgbraoeAHbJ 0xcCV54ewe4V1EzFZ2GgSSdXpxGAcIkoET+6qKfBM33wlK60TF4WrxGIMoBBD6jLHPOi PBzuI5Jrmn7FtDBv4TpTvafJCvJ9jCRYZZfgYfTo10PFigOKT94Trf/+s//mc8vdV3e1 GINJXn/iGr+ksVN5apoDgXrnxObK1iDQoNBN9U6sIpZIVtW10pfixplTxlPcC81SejLi VKnTRhZfr61chBB1aoORNsKw9s7KFiAt7g1Tkqys1FtzFH8naLGs+GIxQG3X/Jmtc7Ke liRg==
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=bSRDzuJdcguHhZXJuZfu48krR66xgZFnmufM99P3Yls=; b=tla5yQOOYfz490Fj+gY5y7Oe5fDJvywJV3gVuFSoMITA+I92E2laVFqyZLmx1a5FB9 Oc14EWTWEjy3b171C2k8NlL6W/3SY8ac8CHqEGh3jWcaJUvspPoY70uAw6OHfBRMQfxa inTLr2uqIvjkMrOC2Ls8y82pW0vz+hzLeO+aijjLkmPq8cDw1J1fhFuL3ezUWT1Sxlw+ WyQzYQxI8pPem+icIMwDh4lXfhDgh6gnxRcvE6IT1PkLinpu87aYMZ2KlTdm/mE6REyq 0L6lOUjO8kuD2cm24d4GOcVEphsbH52mMwbsA8g7B0Nb/iGjbOIlkHx7S+B46Bk4Br/4 MOPw==
X-Gm-Message-State: AOAM532XmZnnPHfZK/GzXdSSZr1OEzfJNv5oUZVwERdiksDJHNdYe3L8 bI3ai56oRjfE9YEsSbM2M413KDGid5TZQ5HBBn8=
X-Google-Smtp-Source: ABdhPJwe043GrkVm/LCWEhSqJ1QfF0KWeO0BB+CLLJenwjDRdWXo+oveAOBc87qicjFDf1QjwUI2I1cGLf2T1ZdLNmU=
X-Received: by 2002:a7b:cb98:: with SMTP id m24mr1518082wmi.98.1594849702709;  Wed, 15 Jul 2020 14:48:22 -0700 (PDT)
MIME-Version: 1.0
References: <1A5A359E-7F46-49E0-BCFB-65EE718BBF63@eggert.org> <CAPDSy+7PxSuapjyDDqSf-Tfmrg246J8z6Tsm2Aayjp32EC_6jg@mail.gmail.com> <20200715213623.GC9808@lubuntu>
In-Reply-To: <20200715213623.GC9808@lubuntu>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Wed, 15 Jul 2020 22:48:14 +0100
Message-ID: <CALGR9oZt5O-vRkXZv9Zoq5UpKKufiJk8GHywew1FFYVmpO_MOQ@mail.gmail.com>
Subject: Re: Doodle poll for -29 virtual interop event
To: David Schinazi <dschinazi.ietf@gmail.com>, Lars Eggert <lars@eggert.org>,  IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000000ff705aa81e2a5"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/xbiaVLzf5mpf5311WK9KFohUkRI>
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, 15 Jul 2020 21:48:26 -0000

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

It seems this poor interop event got a little neglected, apologies.

After a prompt from Martin Duke on 7th July I scanned the poll and
announced the 14th/15th as interop dates into the Slack General channel.
I'd missed the initial poll email myself,  so it didn't register on list of
things to do sorry.

Cheers
Lucas

On Wed, 15 Jul 2020, 22:36 Dmitri Tikhonov, <dtikhonov@litespeedtech.com>
wrote:

> I don't think it was ever sent; at least, I missed it, too.
>
>   - Dmitri.
>
> On Wed, Jul 15, 2020 at 02:31:04PM -0700, David Schinazi wrote:
> > Silly question: did I miss the email about when the draft-29 virtual
> > interop will take place?
> >
> > David
> >
> > On Thu, Jun 25, 2020 at 11:50 PM Lars Eggert <lars@eggert.org> wrote:
> >
> > > Hi,
> > >
> > > please fill out https://doodle.com/poll/rif4gd4ib9he2kqc to find the
> best
> > > day(s) for a virtual interop on the -29 drafts.
> > >
> > > Thanks,
> > > Lars
> > >
>
>

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

<div dir=3D"auto">It seems this poor interop event got a little neglected, =
apologies.<div dir=3D"auto"><br></div><div dir=3D"auto">After a prompt from=
 Martin Duke on 7th July I scanned the poll and announced the 14th/15th as =
interop dates into the Slack General channel. I&#39;d missed the initial po=
ll email myself,=C2=A0 so it didn&#39;t register on list of things to do so=
rry.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Cheers</div><div di=
r=3D"auto">Lucas</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr"=
 class=3D"gmail_attr">On Wed, 15 Jul 2020, 22:36 Dmitri Tikhonov, &lt;<a hr=
ef=3D"mailto:dtikhonov@litespeedtech.com">dtikhonov@litespeedtech.com</a>&g=
t; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">I don&#39;t think it was =
ever sent; at least, I missed it, too.<br>
<br>
=C2=A0 - Dmitri.<br>
<br>
On Wed, Jul 15, 2020 at 02:31:04PM -0700, David Schinazi wrote:<br>
&gt; Silly question: did I miss the email about when the draft-29 virtual<b=
r>
&gt; interop will take place?<br>
&gt; <br>
&gt; David<br>
&gt; <br>
&gt; On Thu, Jun 25, 2020 at 11:50 PM Lars Eggert &lt;<a href=3D"mailto:lar=
s@eggert.org" target=3D"_blank" rel=3D"noreferrer">lars@eggert.org</a>&gt; =
wrote:<br>
&gt; <br>
&gt; &gt; Hi,<br>
&gt; &gt;<br>
&gt; &gt; please fill out <a href=3D"https://doodle.com/poll/rif4gd4ib9he2k=
qc" rel=3D"noreferrer noreferrer" target=3D"_blank">https://doodle.com/poll=
/rif4gd4ib9he2kqc</a> to find the best<br>
&gt; &gt; day(s) for a virtual interop on the -29 drafts.<br>
&gt; &gt;<br>
&gt; &gt; Thanks,<br>
&gt; &gt; Lars<br>
&gt; &gt;<br>
<br>
</blockquote></div>

--000000000000000ff705aa81e2a5--


From nobody Wed Jul 15 15:20:41 2020
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 6246B3A0C71 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 15:20:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 SFh8gNwiWQ7U for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 15:20:38 -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 F20A13A08FC for <quic@ietf.org>; Wed, 15 Jul 2020 15:20:37 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id q7so4604991ljm.1 for <quic@ietf.org>; Wed, 15 Jul 2020 15:20:37 -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=ZCPMPfu68XI3dsse8MplksKGPOiKuTIFwB3Cm7XGpc4=; b=vTyqBoTTB0sk0zvVC68K8ABIwwTbqqUZ4yAVznR00A3loo6ZPE0BM9fs/xg5t1pAoi bYpAJV69Ye2xpiX50GLmy1xWTXA5kboOBsFlMVuwJ3Fu6LbDAGSeHB0bu1O7j3+I9lxj NX0uznUmuybv/1xc5uWnopOX2uosQ7ts6ys2D40yUGiliWQHhdaut3VFnIILXMrYsR9/ xiCXjpqqx8iK3wuFo6TTSkgBl7qWnl3KviB2Ec7r0T3L/5tCKW8SAUDILrhJfDtaDJlL e5FbJqD/2wa4A5lK728lQlDrc1szjawGs4/wtrw70YTZOtcjmDfk88Hxfc+Akt1lqBuh ndfA==
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=ZCPMPfu68XI3dsse8MplksKGPOiKuTIFwB3Cm7XGpc4=; b=BFqi7CShZROFupyyCP5lYCEOyV5TRen+Dho6lkZ4j/+kumfhD/+/VS++SExrZI3A48 cMaq4FlLQTuKgKjhUa9UMM64c8q1C92cLOKRIP7rgdVGhD6bthjl4uM6XR3rC3ImQ/c9 s6Bbm68V9YTdyQaJHYYa4iogiDXYaaEjmSHJWr/lggP2qy2nmQ1+goeFYT42zK8EfM/g BUQ6LXQiOi0QwQhGQQtRcXhDP0p7Hs13Ik3eaaBxsXeb4kBIWWPOFguc+04lO0dSTD2/ U6Oz2qjKX5i2eqEzKYzoEsu1PRclV1u77MYp/WuqnkdMqu0pKwKZAgVnmZCSlXu1cx+5 EI1g==
X-Gm-Message-State: AOAM532lm2I/Fu2u7qHh+sUVZewu/OU2du4jYtgVu2g3NS4Wlzliuqvp /j18gYjOLY1lUp2IdnCVJLCgChu9+ZjFljuUuKw=
X-Google-Smtp-Source: ABdhPJwaAZZ6oHcDVFjjlATVrOpS55BR9WgBtnXR0sf2tTzkR9KC7EZ+jNAaQQ6UcPcfKQfdxeN3DljQgFr+aadWiHQ=
X-Received: by 2002:a2e:8199:: with SMTP id e25mr502108ljg.307.1594851636127;  Wed, 15 Jul 2020 15:20:36 -0700 (PDT)
MIME-Version: 1.0
References: <1A5A359E-7F46-49E0-BCFB-65EE718BBF63@eggert.org> <CAPDSy+7PxSuapjyDDqSf-Tfmrg246J8z6Tsm2Aayjp32EC_6jg@mail.gmail.com> <20200715213623.GC9808@lubuntu> <CALGR9oZt5O-vRkXZv9Zoq5UpKKufiJk8GHywew1FFYVmpO_MOQ@mail.gmail.com>
In-Reply-To: <CALGR9oZt5O-vRkXZv9Zoq5UpKKufiJk8GHywew1FFYVmpO_MOQ@mail.gmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Wed, 15 Jul 2020 15:20:25 -0700
Message-ID: <CAPDSy+78csJtjc1m3+4x7LtFMLT8CJs56s7gPtO-p2YjxdTmQg@mail.gmail.com>
Subject: Re: Doodle poll for -29 virtual interop event
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: Lars Eggert <lars@eggert.org>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000003daab905aa8255ef"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ZZmDEo0Tl4wFSq7whoTISoURVp8>
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, 15 Jul 2020 22:20:40 -0000

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

Ah, that explains why the interop matrix got greener this week :-)

No worries, we'll participate in the next one.

David

On Wed, Jul 15, 2020 at 2:48 PM Lucas Pardue <lucaspardue.24.7@gmail.com>
wrote:

> It seems this poor interop event got a little neglected, apologies.
>
> After a prompt from Martin Duke on 7th July I scanned the poll and
> announced the 14th/15th as interop dates into the Slack General channel.
> I'd missed the initial poll email myself,  so it didn't register on list of
> things to do sorry.
>
> Cheers
> Lucas
>
> On Wed, 15 Jul 2020, 22:36 Dmitri Tikhonov, <dtikhonov@litespeedtech.com>
> wrote:
>
>> I don't think it was ever sent; at least, I missed it, too.
>>
>>   - Dmitri.
>>
>> On Wed, Jul 15, 2020 at 02:31:04PM -0700, David Schinazi wrote:
>> > Silly question: did I miss the email about when the draft-29 virtual
>> > interop will take place?
>> >
>> > David
>> >
>> > On Thu, Jun 25, 2020 at 11:50 PM Lars Eggert <lars@eggert.org> wrote:
>> >
>> > > Hi,
>> > >
>> > > please fill out https://doodle.com/poll/rif4gd4ib9he2kqc to find the
>> best
>> > > day(s) for a virtual interop on the -29 drafts.
>> > >
>> > > Thanks,
>> > > Lars
>> > >
>>
>>

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

<div dir=3D"ltr">Ah, that explains why the interop matrix got greener this =
week :-)<div><br></div><div>No worries, we&#39;ll participate in the next o=
ne.</div><div><br></div><div>David</div></div><br><div class=3D"gmail_quote=
"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jul 15, 2020 at 2:48 PM Luc=
as Pardue &lt;<a href=3D"mailto:lucaspardue.24.7@gmail.com">lucaspardue.24.=
7@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"auto">It seems this poor interop event got a little =
neglected, apologies.<div dir=3D"auto"><br></div><div dir=3D"auto">After a =
prompt from Martin Duke on 7th July I scanned the poll and announced the 14=
th/15th as interop dates into the Slack General channel. I&#39;d missed the=
 initial poll email myself,=C2=A0 so it didn&#39;t register on list of thin=
gs to do sorry.</div><div dir=3D"auto"><br></div><div dir=3D"auto">Cheers</=
div><div dir=3D"auto">Lucas</div></div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D"gmail_attr">On Wed, 15 Jul 2020, 22:36 Dmitri Tikhonov=
, &lt;<a href=3D"mailto:dtikhonov@litespeedtech.com" target=3D"_blank">dtik=
honov@litespeedtech.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">I don&#39;t think it was ever sent; at least, I miss=
ed it, too.<br>
<br>
=C2=A0 - Dmitri.<br>
<br>
On Wed, Jul 15, 2020 at 02:31:04PM -0700, David Schinazi wrote:<br>
&gt; Silly question: did I miss the email about when the draft-29 virtual<b=
r>
&gt; interop will take place?<br>
&gt; <br>
&gt; David<br>
&gt; <br>
&gt; On Thu, Jun 25, 2020 at 11:50 PM Lars Eggert &lt;<a href=3D"mailto:lar=
s@eggert.org" rel=3D"noreferrer" target=3D"_blank">lars@eggert.org</a>&gt; =
wrote:<br>
&gt; <br>
&gt; &gt; Hi,<br>
&gt; &gt;<br>
&gt; &gt; please fill out <a href=3D"https://doodle.com/poll/rif4gd4ib9he2k=
qc" rel=3D"noreferrer noreferrer" target=3D"_blank">https://doodle.com/poll=
/rif4gd4ib9he2kqc</a> to find the best<br>
&gt; &gt; day(s) for a virtual interop on the -29 drafts.<br>
&gt; &gt;<br>
&gt; &gt; Thanks,<br>
&gt; &gt; Lars<br>
&gt; &gt;<br>
<br>
</blockquote></div>
</blockquote></div>

--0000000000003daab905aa8255ef--


From nobody Wed Jul 15 15:41:51 2020
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 4596C3A0A2C for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 15:41:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=N6XwsJ8T; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=RKeow2ES
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id uCLk-OtvwhWu for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 15:41:48 -0700 (PDT)
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 384C83A0A2B for <quic@ietf.org>; Wed, 15 Jul 2020 15:41:48 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id 67B5ACC3 for <quic@ietf.org>; Wed, 15 Jul 2020 18:41:47 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Wed, 15 Jul 2020 18:41:47 -0400
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=fm2; bh=wM6wGFxvT/Bf6zktvADzmXEoK+9c9Hc J/reP6lGDW7s=; b=N6XwsJ8TmelQ9e0tJ6VQNKoVcQaI1fSfuEY3HM29tUJyRpe kgo40PjJk7FcqWm6hbaRSG1btSz3EcVHntAfWSXHFxpk6n6IcIuUMh0wO7ctPuQf NGDmsmihG23TZ6GGYBYRboEM3SfbBpIFnJ3fWAfgrFB6k37y7u9hl/axcK0nH/gK w/C8FZkhfWIpW8BIr/TIvIe3Jl4b7acfZeXf7m7AUAMVGfaJL58+cXI1BC3gaVPM oTw3XvYsuByzTmEf9v1TT6gvS1UF9Ae6W73UUyew1KyDeKaEzumyN2GOnpt8eB+2 1g3xoEcgNwcmMLmstWl0F9F21I0xnkVbOCswoPA==
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=fm3; bh=wM6wGF xvT/Bf6zktvADzmXEoK+9c9HcJ/reP6lGDW7s=; b=RKeow2EShnJod3WTsDO01R natynux/Qass1Z/YPoJS11vA/yvyuGUvInVU1YUEI8HMtBBwX/DhRFTTezwcuEP8 ZeLLncf3zNzWGZ8Dozf0ZK/AA7o00BGY7QNbyjt8VGS1yyCxq5X9Inxu0+LJ4VBz Zs97UdiTr/wr0ETMFOrIQp4s7vBCQmD256RDoCdzd9EtO6LFeK/z3FFi/jsRM8hf tyk11lqA1VfFbWH0s0cZSOGDE9zPPVdixCq60bZHEWWuf6keA5uQP3qaol6KSRNS wdFvyDXAVUBQ7LvUGqz0n9S5Mkiiqiet115KandOgtEHwzS8xBsHhxMxAVkXpcJQ ==
X-ME-Sender: <xms:KoYPXy4Tp-8wNeLRZBiwwX7ojrjrdY4oCnwskfd4TQTL0vjbdi3IcQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrfeefgdduudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif vghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepkeetueeikedtkeelfeekve fhkeffvedvvefgkefgleeugfdvjeejgeffieegtdejnecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:KoYPX76avP9HZk8ZLI13k0d9XqH8GYpFPVMAyyZEjpQAApujVoEvhQ> <xmx:KoYPXxfv3LhqIaBQKfyebiA7ekaDZaczRY5FGZUoPRDeBgn3jKEWEg> <xmx:KoYPX_Li99SjYCx4vJXuyS6JnIVcjVQWJb_2x6X_Mr6JoehBF-5Yjw> <xmx:KoYPX9aKcqwJmvtnCAO-NClIwztHaO6s7ri1lglsPaTXW5lzxTu6PQ>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 9EBC8E00DF; Wed, 15 Jul 2020 18:41:46 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-613-g8a73ad6-fm-20200709.001-g8a73ad6e
Mime-Version: 1.0
Message-Id: <7ee5a352-fef6-44ed-9e82-09194aae366e@www.fastmail.com>
In-Reply-To: <20200715180231.GB9808@lubuntu>
References: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com> <20200715180231.GB9808@lubuntu>
Date: Thu, 16 Jul 2020 08:41:27 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: quic@ietf.org
Subject: Re: Need your help: different connection IDs in the same datagram
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Nq--2qjVtHLkC_I0W4XaJzpT-QU>
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, 15 Jul 2020 22:41:49 -0000

On Thu, Jul 16, 2020, at 04:02, Dmitri Tikhonov wrote:
>   #if VARIANT_A
>             if (!conn_owns_scid(conn, dcid))
>   #else
>             if (conn != lookup_by_dcid(dcid))
# else
             if (false)
#endif

This would also work, would it not?


From nobody Wed Jul 15 15:49:45 2020
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 6D5A83A0AE3 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 15:49:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=nbaR8Thi; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=RKXKgr0N
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 60p3F_TC0kdB for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 15:49:41 -0700 (PDT)
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 C0BCD3A0AB8 for <quic@ietf.org>; Wed, 15 Jul 2020 15:49:41 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.west.internal (Postfix) with ESMTP id E3518D55 for <quic@ietf.org>; Wed, 15 Jul 2020 18:49:40 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Wed, 15 Jul 2020 18:49:41 -0400
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=fm2; bh=Aw+1U17+CloHQ5nYikj0HUFcgatIqxs QBN9EPsCX1AU=; b=nbaR8ThiBeXNd6E0HAZi1rf+q0GZE+jHDHhiIFmkUd3hxa1 rFJzUV4tAC8QQk4/lkNPgTOZmgQFtKZAtusSd+2yjocWMcbK7pBb1RJOaG6gaq5k qu9/PY8Er0HtCXIF/B4vXnlTaez6jEB6+pT1AggJ5bXZ6WrwyEhrFKHFH8AtLl/f lb+aJlyxVv8FKLXxr723Ws1koZJF1km4fvmaF05OdHCPtk5LM5D4IOIFvxJadOFq HAr1xPcrSm8IBV7jVoLXYrP/gAA7tQgHmqF08s7zER1IX+HcGd6HUEPchxp8kGQp cS+gNptKwx+4/cSYab1t54MPN9I67lHnQiuMaRw==
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=fm3; bh=Aw+1U1 7+CloHQ5nYikj0HUFcgatIqxsQBN9EPsCX1AU=; b=RKXKgr0NgPZqjcXFZMBMGZ 8jDSX05gNU3c/9rkIR1ONQikfEVbFqGCXil/LJQ0CqO1l+v35JNAEG6oyiUJ9BeP BP7zXzq+KR3zzfXMa5AYIVedWr2QKNdJi9iOKMpLFDCmEU9Nc8Krdc0kuZHKwyqy e7MwZ3VDghOJnFqTKUO6Pn9pTDnpMT3aazAlhCbjwo8ABaurB2d07CdVx4lTLSTl bguBr9WGQp15afPE3Z1UVkh/4DQSk2br5JVtLLmx+VxuspNE+mflRiwwwmNArn/9 OSQIQdfYnZafnt7NwEMngeFEXS77TSi9n0teMhdZVaTtUP+9HP47AbogVHXqhWrw ==
X-ME-Sender: <xms:BIgPX-FcGdZsUDUoOTnyVcyrP-mcMFHMY_WV1h_c6xLntmdS4qNpNA>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrfeefgddufecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif vghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepkeetueeikedtkeelfeekve fhkeffvedvvefgkefgleeugfdvjeejgeffieegtdejnecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:BIgPX_XNoPdXtvt38EEwQ3Swi34WgqNmZ09OQdElaaRJuge32HKkug> <xmx:BIgPX4InvjO6TnlbvrjmuxlahFT1MT6oEEhdsDa9QqPB6JyNhjucDQ> <xmx:BIgPX4EKMUx2NYVJ72u9xo3CobgArDa9ah1NQ7DIbA6EYqTXmogNdg> <xmx:BIgPX1U8gBJpXklUxnOgIfPZoTBd9RcyCcnfH1EAALCFXg8iRR-PdA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 21321E00DF; Wed, 15 Jul 2020 18:49:40 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-dev0-613-g8a73ad6-fm-20200709.001-g8a73ad6e
Mime-Version: 1.0
Message-Id: <9b265aef-d1bd-47cc-9a1c-677eef223c73@www.fastmail.com>
In-Reply-To: <CAKcm_gP24=x64QwcCdki-jxFXsLKiTPH8UYFdGOG3H1YJgEbOQ@mail.gmail.com>
References: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com> <20200715180231.GB9808@lubuntu> <CAKcm_gPfc3sFy0kuyTzUFk2XFMZ8NdXTd7CuNf0o0v+RXDG=xg@mail.gmail.com> <CH2PR22MB20861D3BEA06EE61AA882245DA7E0@CH2PR22MB2086.namprd22.prod.outlook.com> <CAKcm_gP24=x64QwcCdki-jxFXsLKiTPH8UYFdGOG3H1YJgEbOQ@mail.gmail.com>
Date: Thu, 16 Jul 2020 08:49:20 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: quic@ietf.org
Subject: Re: Need your help: different connection IDs in the same datagram
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/5q9GuuN6QeccUF6ktiM5eJ84B_g>
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, 15 Jul 2020 22:49:45 -0000

On Thu, Jul 16, 2020, at 07:17, Ian Swett wrote:
> I forgot there's a contradiction, because I thought we disallowed 
> sending mixed-CID packets.  So I'd prefer changing to MUST NOT coalesce 
> packets with different CIDs.  Even if you generate them and then 
> coalesce them(which we do), that's not that hard to enforce in the 
> coalescing code.

OK, this is good information.  I had understood that you were concerned that you might violate a requirement to have consistent connection IDs.

Here's one example of how you might:

Client receives server's first flight, which comprises Initial, Handshake, 1-RTT (which includes NEW_CONNECTION_ID, because this is a good time to send that in a lot of cases).  Assume this all comes at once, in a single datagram.

1. Client processes Initial and Handshake.
2. Client generates a Handshake packet (that includes TLS Finished) and sets that aside.  This uses the connection ID from the servers Initial.
3. Client processes 1-RTT.  Sees NEW_CONNECTION_ID, decides to use it.
4. Client generates first application data, and makes a 1-RTT packet using the new connection ID.
5. Client gathers all generated packets and sends them.

Does anyone care about doing this, or something like it? Because if not, I make a new proposal that changes the requirements to:

* Senders MUST ensure that all coalesced packets include the same value for the Destination Connection ID field.
* Receivers SHOULD discard coalesced packets if they are for a different connection than the first; senders MAY discard coalesced packets that contain a different value in the Destination Connection ID field than the first.


From nobody Wed Jul 15 17:00:08 2020
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 3C3513A0B96 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 17:00:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, 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 eqCfE90zJDHm for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 17:00:05 -0700 (PDT)
Received: from mail-qk1-x729.google.com (mail-qk1-x729.google.com [IPv6:2607:f8b0:4864:20::729]) (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 943783A0B95 for <quic@ietf.org>; Wed, 15 Jul 2020 17:00:05 -0700 (PDT)
Received: by mail-qk1-x729.google.com with SMTP id b4so3770923qkn.11 for <quic@ietf.org>; Wed, 15 Jul 2020 17:00:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=s82Pjf/5vBv4h5cdYiYFyA+UySsXWREXkyMxPkFzMmg=; b=jQXFtVIf9rVid40D6KnYHXWS8hto/8no5sRtevlvIcpXKYdHqjgiBY24af/6rA7cDY +FQdznKNIfx9Jih4yPixUVkt2SlKnlMuSKn2RbQYaRDJNjcK9UoG1SgKIElvDZqp7S4l EA6t6crmkUQM1KeYpVs+9dJIfSkjQuHc/KBqiOcgmkqImjUf69X7NtKeEg/cIyYY1MuM OggpMx+a871FXAy/MraLZujsqpIMLTtH8BtSLXQAp+8EvhVHgm9iOGAQIcgNyA32Abu7 1HPTncmMeb6d9bOdx/yc3C9j82dlSsdm/zTIzUXslMZnZCWr06nBCi3OK71SRQbiM995 qgYA==
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=s82Pjf/5vBv4h5cdYiYFyA+UySsXWREXkyMxPkFzMmg=; b=jjCx8MUnqsQLlOPHCwYY3+cVXRSqjsf72nbEfZtKnnuNA8HoTK0Gqs5EvJvht1MSu8 vrJnYWCd9DYnS2V2HJcWOsTXZCM/cgaUp6rdEYEuTeGOoJslJ/SkJGbswFSxjCjiE4I2 /0bsVTmR9wCK8ktlhgPvs2VBDzdfZJa0upFAfH/B4zU8+18nvZlefKpDiXwltOIWz7t4 79Qfo/+f1pAZvHMR7KBtebCi2akjng6eHqyvTAeYjVXjXWQJP78rexGVMYrz8xAqwS0l 8Pi8+utKCEOC69mCC81bgTLaaU2gz0rgDWRFgkokYosUXDxc82+etzeXrtpcFkcljGuM EpDw==
X-Gm-Message-State: AOAM531KiCQcM4Q05wm7WrOPpYXss8RE3uHD9hqBd5CiAnPyez2bQ026 6mwL4ZkkuYLHR45x3Imvmg6xa6SAmOgrmQ==
X-Google-Smtp-Source: ABdhPJzBGgZw/XOHWGYBcmnfLovyS5tVdddt9XkvdXTAJM6G+akZi8w5DsMgI4lQCctrW2j+9FB6mw==
X-Received: by 2002:ae9:de06:: with SMTP id s6mr1586237qkf.44.1594857604092; Wed, 15 Jul 2020 17:00:04 -0700 (PDT)
Received: from lubuntu (ool-44c1d219.dyn.optonline.net. [68.193.210.25]) by smtp.gmail.com with ESMTPSA id k6sm4188012qki.123.2020.07.15.17.00.03 for <quic@ietf.org> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 15 Jul 2020 17:00:03 -0700 (PDT)
Date: Wed, 15 Jul 2020 19:59:58 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: quic@ietf.org
Subject: Re: Need your help: different connection IDs in the same datagram
Message-ID: <20200715235957.GE9808@lubuntu>
Mail-Followup-To: quic@ietf.org
References: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com> <20200715180231.GB9808@lubuntu> <7ee5a352-fef6-44ed-9e82-09194aae366e@www.fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <7ee5a352-fef6-44ed-9e82-09194aae366e@www.fastmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/8Zdg2vjk0GH-qs_2959LpbVIn5E>
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, 16 Jul 2020 00:00:07 -0000

You've lost me a bit, Martin.  Is this the code you aimed for?

    conn = NULL;
    while (quic_packet = parse_udp(pointers)) {
        dcid = parse(quic_packet);
        if (conn)
        {
  #if VARIANT_A
            if (!conn_owns_scid(conn, dcid))
  #elif VARIANT_B
            if (conn != lookup_by_dcid(dcid))
  #else
	    if (false)
  #endif
                continue;
        }
        conn = process_packet(quic_packet);
    }

On Thu, Jul 16, 2020 at 08:41:27AM +1000, Martin Thomson wrote:
> On Thu, Jul 16, 2020, at 04:02, Dmitri Tikhonov wrote:
> >   #if VARIANT_A
> >             if (!conn_owns_scid(conn, dcid))
> >   #else
> >             if (conn != lookup_by_dcid(dcid))
> # else
>              if (false)
> #endif
> 
> This would also work, would it not?
> 


From nobody Wed Jul 15 17:00:40 2020
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 D6F5D3A0B97 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 17:00:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 8GUiNW6OOBGD for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 17:00:36 -0700 (PDT)
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 756EC3A0D12 for <quic@ietf.org>; Wed, 15 Jul 2020 17:00:28 -0700 (PDT)
Received: by mail-lj1-x22f.google.com with SMTP id q7so4935119ljm.1 for <quic@ietf.org>; Wed, 15 Jul 2020 17:00:28 -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=7OXxaLy2MoqAzRPSGxLRIWhXg7l/v3qhYHHoMf6QXhQ=; b=KxZX3oN/Cm5ow9ad4jQ4autDeXOZhGAB6WAcYtUgMqqe69JYqZrT+MdzDNSBQ/Yqoc rcjD/N9ja2haaU8aoap5Ql7LDyatt+OA1MYhvy/1mfQrdn9SW6xmpf24NCdtD+IlEbCU qJTkep/3PfnXh1p1KF8E1rJss6YHT0aKWxV6hGPQFeedgVf20J7nYPrhbbIwbC+rh+1l kmk4PPy0NlO8zhfeCRSzbxJUhDltiMYK20TEcgaMgFAw+egUjd6fjpFjmRccacVOYhgr ROq74P76sYQSa6Mg0gOf/icuLl3R+Z6pfx5Y07tejZv/fsuUQdTO0v7yUXaCYeOl701M WYcg==
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=7OXxaLy2MoqAzRPSGxLRIWhXg7l/v3qhYHHoMf6QXhQ=; b=qkvd+yC4XoRhdiqNJRQf+cdmEJue8g8ThreMjdYMHupSwVVj70wsA9H/EbGt+7wN55 bPUvks/dRwoKDD2Hs6ifTvvyDvQueo1F0bwWbfrqBMyJ12w9rl3COwMuCUAQVQmoxwTv 6jiXIQ4XzAtbLeasly797N5K/0TeiQStD24glm1NElvFdGiiTGBXIO33EDULdZKwSiRD BsQiNskp9SxfpZSYPwMpPYVnJ5bO7dTXeyR6Y0EOm/QTxOKpYN0iUO+HK4RQjT7rb7vu ojgdOx4tTMKQp19jBZpEAVmGQoTjTGgSejKBFF/b64zwYSIfEApmFTY2bLzTGQGuvHvY 2rbQ==
X-Gm-Message-State: AOAM532VyY0UpCnLhAbvvQAHrjKWiuiPJenOk9lYHKd9C82XMVJ9fi0r Pv2lxRcOZKTGNbn2nf5n5xHC7w12xsAvfnjF47SC3Q==
X-Google-Smtp-Source: ABdhPJwdO2a70iBZ6CvTUWbhWLue19ku31V5erlZf2qhPdQFh5EOYtlaJZKbC+2PeUff3sra1poO7N/EUuYz7B/OPsQ=
X-Received: by 2002:a05:651c:550:: with SMTP id q16mr679383ljp.188.1594857626571;  Wed, 15 Jul 2020 17:00:26 -0700 (PDT)
MIME-Version: 1.0
References: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com> <20200715180231.GB9808@lubuntu> <CAKcm_gPfc3sFy0kuyTzUFk2XFMZ8NdXTd7CuNf0o0v+RXDG=xg@mail.gmail.com> <CH2PR22MB20861D3BEA06EE61AA882245DA7E0@CH2PR22MB2086.namprd22.prod.outlook.com> <CAKcm_gP24=x64QwcCdki-jxFXsLKiTPH8UYFdGOG3H1YJgEbOQ@mail.gmail.com> <9b265aef-d1bd-47cc-9a1c-677eef223c73@www.fastmail.com>
In-Reply-To: <9b265aef-d1bd-47cc-9a1c-677eef223c73@www.fastmail.com>
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Wed, 15 Jul 2020 17:00:15 -0700
Message-ID: <CAPDSy+4VkRcHJvgSrr86K56esVvnNXdANJOF=yfe5gmPtd9J5w@mail.gmail.com>
Subject: Re: Need your help: different connection IDs in the same datagram
To: Martin Thomson <mt@lowentropy.net>
Cc: QUIC <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000004c958005aa83ba7c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/LWW3Zd1IyB13eaTSoUcR1BiydlA>
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, 16 Jul 2020 00:00:38 -0000

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

On Wed, Jul 15, 2020 at 3:49 PM Martin Thomson <mt@lowentropy.net> wrote:

> On Thu, Jul 16, 2020, at 07:17, Ian Swett wrote:
> > I forgot there's a contradiction, because I thought we disallowed
> > sending mixed-CID packets.  So I'd prefer changing to MUST NOT coalesce
> > packets with different CIDs.  Even if you generate them and then
> > coalesce them(which we do), that's not that hard to enforce in the
> > coalescing code.
>
> OK, this is good information.  I had understood that you were concerned
> that you might violate a requirement to have consistent connection IDs.
>
> Here's one example of how you might:
>
> Client receives server's first flight, which comprises Initial, Handshake,
> 1-RTT (which includes NEW_CONNECTION_ID, because this is a good time to
> send that in a lot of cases).  Assume this all comes at once, in a single
> datagram.
>
> 1. Client processes Initial and Handshake.
> 2. Client generates a Handshake packet (that includes TLS Finished) and
> sets that aside.  This uses the connection ID from the servers Initial.
> 3. Client processes 1-RTT.  Sees NEW_CONNECTION_ID, decides to use it.
> 4. Client generates first application data, and makes a 1-RTT packet using
> the new connection ID.
> 5. Client gathers all generated packets and sends them.
>
> Does anyone care about doing this, or something like it?


I think we should disallow this unless someone can show it provides real
benefit.
If an implementation supports coalescing, it has to handle cases where the
last
packet doesn't fit so it needs to have code to for example send the
handshake
packet by itself if the 1-RTT packet is too big. Once one has such code,
it's pretty
simple to add a check that also triggers this if the connection IDs differ.
If someone
really cares about not losing the benefits of coalescing, then they can
make sure
that they don't act on NEW_CONNECTION_ID until the handshake is confirmed.


> Because if not, I make a new proposal that changes the requirements to:
>
> * Senders MUST ensure that all coalesced packets include the same value
> for the Destination Connection ID field.
> * Receivers SHOULD discard coalesced packets if they are for a different
> connection than the first; senders MAY discard coalesced packets that
> contain a different value in the Destination Connection ID field than the
> first.
>

I support this proposal.

--0000000000004c958005aa83ba7c
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 Wed, Jul 15, 2020 at 3:49 PM Marti=
n 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 Thu,=
 Jul 16, 2020, at 07:17, Ian Swett wrote:<br>
&gt; I forgot there&#39;s a contradiction, because I thought we disallowed =
<br>
&gt; sending mixed-CID packets.=C2=A0 So I&#39;d prefer changing to MUST NO=
T coalesce <br>
&gt; packets with different CIDs.=C2=A0 Even if you generate them and then =
<br>
&gt; coalesce them(which we do), that&#39;s not that hard to enforce in the=
 <br>
&gt; coalescing code.<br>
<br>
OK, this is good information.=C2=A0 I had understood that you were concerne=
d that you might violate a requirement to have consistent connection IDs.<b=
r>
<br>
Here&#39;s one example of how you might:<br>
<br>
Client receives server&#39;s first flight, which comprises Initial, Handsha=
ke, 1-RTT (which includes NEW_CONNECTION_ID, because this is a good time to=
 send that in a lot of cases).=C2=A0 Assume this all comes at once, in a si=
ngle datagram.<br>
<br>
1. Client processes Initial and Handshake.<br>
2. Client generates a Handshake packet (that includes TLS Finished) and set=
s that aside.=C2=A0 This uses the connection ID from the servers Initial.<b=
r>
3. Client processes 1-RTT.=C2=A0 Sees NEW_CONNECTION_ID, decides to use it.=
<br>
4. Client generates first application data, and makes a 1-RTT packet using =
the new connection ID.<br>
5. Client gathers all generated packets and sends them.<br>
<br>
Does anyone care about doing this, or something like it?</blockquote><div><=
br></div><div>I think we should disallow this unless someone can show it pr=
ovides real benefit.</div><div>If an implementation supports coalescing, it=
 has to handle cases where the last</div><div>packet doesn&#39;t fit so it =
needs to have code to for example send the handshake</div><div>packet by it=
self if the 1-RTT packet is too big. Once one has such code, it&#39;s prett=
y</div><div>simple to add a check that also triggers this if the connection=
 IDs differ. If someone</div><div>really cares about not losing the benefit=
s of coalescing, then they can make sure</div><div>that they don&#39;t act =
on NEW_CONNECTION_ID until the handshake is confirmed.</div><div>=C2=A0</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">Because if not, I make =
a new proposal that changes the requirements to:<br>
<br>
* Senders MUST ensure that all coalesced packets include the same value for=
 the Destination Connection ID field.<br>
* Receivers SHOULD discard coalesced packets if they are for a different co=
nnection than the first; senders MAY discard coalesced packets that contain=
 a different value in the Destination Connection ID field than the first.<b=
r></blockquote><div><br></div><div>I support this proposal.=C2=A0</div></di=
v></div>

--0000000000004c958005aa83ba7c--


From nobody Wed Jul 15 17:11:45 2020
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 A21D23A0BC6 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 17:11:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 YQd1CQ284b7I for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 17:11:42 -0700 (PDT)
Received: from mail-qt1-x82b.google.com (mail-qt1-x82b.google.com [IPv6:2607:f8b0:4864:20::82b]) (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 99E873A0BC5 for <quic@ietf.org>; Wed, 15 Jul 2020 17:11:42 -0700 (PDT)
Received: by mail-qt1-x82b.google.com with SMTP id 6so3487223qtt.0 for <quic@ietf.org>; Wed, 15 Jul 2020 17:11:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=2THC7MsV6uIT1faT0q7GHOQLCtezBe3FPjT+NSI6Hyk=; b=VNVRzHtR23PDi+66u3Pum8AIlFyJ88PYad5QqqT6mnbgfrtdNtCIFemp3VmgmmKppL yBhzqUXdX3FoSFTEv+c/Xz2j+kWX815P1wJYmEIm71KGTvKMyTIXTXcuxdH17TzET6cS 3t32MYDFhcuYjG+/D77q47uOWZV1NGuBObR15F77Kk9J+yTYnq3yaSDd38fd+zNLacJo hRugZxbzRilXA+XEAyoPYWfLnVzCDVijmwlKRGxglo4eP8uwne4tCUXUEkWERKx371Rg YCPKldGHGtHShBaSg2EzUbgz/CeTYx9J932PL6CiYbf06BfTA4An/8iykKTDjZiPkSjF Bctg==
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=2THC7MsV6uIT1faT0q7GHOQLCtezBe3FPjT+NSI6Hyk=; b=h/Zarxxy0nT9TIGj8D1OjPuP+sYsflAFILfrnC3LbUzJyEbC4hsdRoYhvdDxY+Ge4S zznaUxZvWNfBy6C9hAEuU/CKzhoGSfnE5PwgvvnXas62HwB84JaRAeNq61ajMk+ChrsW 2J6GwlT5pCgbSPCl8FNfA4t6qmzC8Nf+WZhj8p9z4lXrr66uJFiOfhO1CfJivXcJVfrA KXdQjdTlIRWV04ejghNjQpWKQriBtI5N+b5FXLQS1ynYErwy2DypnsEzUPxbFTqzIk9p X87HiFuJ6LOCvpnPdP6hTydzWuHuoD5cPgelxDR5SibbM2poCTvCZ0EbReJ7FNdSwAlI loIg==
X-Gm-Message-State: AOAM532kzFI8teZpRgt3/BKrqytj5+koFttZKuLpnBDHsE8aUnX6yS4c bxi0aHki9ACwEGG3CjJSB7HCFGz7E8f3mw==
X-Google-Smtp-Source: ABdhPJy7bRdXs//eOUhR3ooIuHMMNs898PFpD3v8txQiUlDXI1uu+Kp8OswkWoffBhi4pQBz3xBc7g==
X-Received: by 2002:ac8:664c:: with SMTP id j12mr2635536qtp.232.1594858301334;  Wed, 15 Jul 2020 17:11:41 -0700 (PDT)
Received: from lubuntu (ool-44c1d219.dyn.optonline.net. [68.193.210.25]) by smtp.gmail.com with ESMTPSA id 140sm4271672qko.98.2020.07.15.17.11.40 for <quic@ietf.org> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 15 Jul 2020 17:11:40 -0700 (PDT)
Date: Wed, 15 Jul 2020 20:11:35 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: quic@ietf.org
Subject: Re: Need your help: different connection IDs in the same datagram
Message-ID: <20200716001134.GF9808@lubuntu>
Mail-Followup-To: quic@ietf.org
References: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com> <20200715180231.GB9808@lubuntu> <CAKcm_gPfc3sFy0kuyTzUFk2XFMZ8NdXTd7CuNf0o0v+RXDG=xg@mail.gmail.com> <CH2PR22MB20861D3BEA06EE61AA882245DA7E0@CH2PR22MB2086.namprd22.prod.outlook.com> <CAKcm_gP24=x64QwcCdki-jxFXsLKiTPH8UYFdGOG3H1YJgEbOQ@mail.gmail.com> <9b265aef-d1bd-47cc-9a1c-677eef223c73@www.fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <9b265aef-d1bd-47cc-9a1c-677eef223c73@www.fastmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/8S4rxOQ-17J1w7r0unTMVYT2Xxg>
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, 16 Jul 2020 00:11:44 -0000

On Thu, Jul 16, 2020 at 08:49:20AM +1000, Martin Thomson wrote:
> * Receivers SHOULD discard coalesced packets if they are for a different
> connection than the first; senders MAY discard coalesced packets that
                             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> contain a different value in the Destination Connection ID field than
> the first.

I don't understand this.  What do you mean by "*senders* MAY
discard packets?"

  - Dmitri.


From nobody Wed Jul 15 17:29:30 2020
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 0CAAD3A0F0E for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 17:29:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=h7/Qh/H4; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=CyFR1uxp
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id XQT-spdKzewD for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 17:29:28 -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 130243A07D1 for <quic@ietf.org>; Wed, 15 Jul 2020 17:29:28 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 6DA785C00DA for <quic@ietf.org>; Wed, 15 Jul 2020 20:29:27 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Wed, 15 Jul 2020 20:29:27 -0400
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=fm2; bh=bAbaTYR/BikaSYPs0kWG0JzSpdKSuUC FeN1apvj3enw=; b=h7/Qh/H41qhsVhufdFIrnlIOGwU378jickLn1v+rPWAbe+K qBiuK4zog2mk3VRXihWC6kist2fT97eiGS9ihbuQY8mugAhhCArirvszuwtFYW6f apChge5xAElhkC9Q4bRFqA6t6MdqJuYTlihcuWSS1eApjqaG67WdggX6hf5wL5hE jplK5AxMoNMGlee8Fo1XpaZltAJhH2yFkTQqn3pqvZy6WSNbnHTLUbTO8NqTHsor eZcbyi29fvFdnoZ4FADYn29tPgYLoL39PF/y9iumV2sx8J8for3pmcqkkGzULVbg gONIrMNi0NIWmPb4uo+3Jn9Qa8nBxht5cW1C5QQ==
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=fm3; bh=bAbaTY R/BikaSYPs0kWG0JzSpdKSuUCFeN1apvj3enw=; b=CyFR1uxpf8oWy0XjBcwMrO 9HfKTMa8Qps5dytlDOVYq18ygC7cBfQgVXsFjW1HmsObFR5yXDCXI+bznQt6nS4d qEQLMZswRKxnmSlXEEHkK6JWw8hym62umAZVeoDzEtzw6UwEOPnZIixw8DtOQebf iT6fZOiK+YjMYCV68jOUeoxeXHutxS0xLOw1HrmV905ev8NY0czsMu+5jqW6Vfkd xtVkDmEvNzU2F+CZE6GjoBgQZRRdTNLnG9ernRRzeVIt9ysiQVGNsN6I+evlqqO8 PquP56UGFRgQyVRfawCFxeDxZZrdakN7g/GDTBAbdSXWAzVrlyGFU6ulPuamxGhQ ==
X-ME-Sender: <xms:Z58PX50WQA8Czwep7UjtF0wY7el6jM9jbkx2jRiZbH_XJ-sL58nPjQ>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrfeefgdefgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif vghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepkeetueeikedtkeelfeekve fhkeffvedvvefgkefgleeugfdvjeejgeffieegtdejnecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:Z58PXwHLTFkBpdS_jkZ-Tva-tylW84I-czhQ3-NCHUYpcg_H_3X08A> <xmx:Z58PX56tYf4-KG20KhsvXD8oYPD8PIkzl69fOLYIIhgJCGZODLVE8A> <xmx:Z58PX21MHmi8QHeZyI13lqUKK3BX4lBlxsxZQRxqUjMa6mWDwVVEag> <xmx:Z58PXwExSAHx98ZaSmFEQ6HnbV2iD8QIiZCSLCNdI0_MPy0f6XCK-w>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 016D9E00DF; Wed, 15 Jul 2020 20:29:26 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-52-g083df19-fm-idx2020-20200715.003-g083df194
Mime-Version: 1.0
Message-Id: <4f59efcf-0fc6-4e64-ad20-8eb4e1978095@www.fastmail.com>
In-Reply-To: <20200715235957.GE9808@lubuntu>
References: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com> <20200715180231.GB9808@lubuntu> <7ee5a352-fef6-44ed-9e82-09194aae366e@www.fastmail.com> <20200715235957.GE9808@lubuntu>
Date: Thu, 16 Jul 2020 10:29:07 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: quic@ietf.org
Subject: Re: Need your help: different connection IDs in the same datagram
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/PSEdQ8RFaSfhtAKSg1WX1rknnZI>
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, 16 Jul 2020 00:29:29 -0000

On Thu, Jul 16, 2020, at 09:59, Dmitri Tikhonov wrote:
> You've lost me a bit, Martin.  Is this the code you aimed for?
...
>         if (conn)
>         {
>   #if VARIANT_A
>             if (!conn_owns_scid(conn, dcid))
>   #elif VARIANT_B
>             if (conn != lookup_by_dcid(dcid))
>   #else
> 	    if (false)
>   #endif
>                 continue;
>         }
>         conn = process_packet(quic_packet);
>     }

Yeah, the point being that the check here is added at your discretion.  It is possible to rely on the crypto to ensure that the connection rejects anything that isn't intended for it.


From nobody Wed Jul 15 17:32:17 2020
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 0DB383A0F16 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 17:32:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=dRM36WPM; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=YZ6eStV9
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EkW1JdhZhv-G for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 17:32:14 -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 0588C3A0F15 for <quic@ietf.org>; Wed, 15 Jul 2020 17:32:13 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 60D385C00DD for <quic@ietf.org>; Wed, 15 Jul 2020 20:32:13 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Wed, 15 Jul 2020 20:32:13 -0400
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=fm2; bh=E+a7NY7FyiYeZG6dslHr2NoMG1q+792 ttvPmRVXWe0s=; b=dRM36WPMQdGPkf4C6yqEiJ1QY9YzBRA1v1IAMQcB9tgQPi7 e6bQETXc0VGfBToNMEj1YjBPGyxeYqRUXN2/GnSxTl9VhYoa3Si7a4u8N3j92dC0 SyPY3WGNm+AX6J+0O4tMsX0GZS50QZqILWQX4N9VV7bPgK1LbCnvMEjVHDx4Zxli 0rWvgT9hZMkh3Pr2KXfEF8Vl+r0L0eKvyripTimWbVhnfFmzpVC0i8V626nFVB7p 35iJaofpATfwu+bZUB17ATjFv1sdFfLMpMGbaPpNKjTMUIfHth+LGJeKeQMD1iKE zQl/phYv8jwLQ8dF4knZRzZiFyvUpexgMvqzOig==
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=fm3; bh=E+a7NY 7FyiYeZG6dslHr2NoMG1q+792ttvPmRVXWe0s=; b=YZ6eStV9hVUsCpKDCpKu4+ vlAqwvoomRWLdH6/DyOcZDaWkGX4ZTyvgx1GJoUV/FgPoGWAgNfBDRlQASnixKri AGJH9C2RgaGkjZ8OWrpQ/bcNGVy6XZxlFM7F5uB1FiyylxIsvXwZgUIWnetR9NoX 0+shNZ6z7FN2gGRZnsd6zDhBY830QxzItHZFBidcv8S8QWilurtg4cQe2WLC2Xrn WoJFGX84AIDtMq3tOhPAB6kQ1po3ArPvQZr2jzKRWdi+AWLPTmU0fBBoHm9SnWk6 4wN0+EvzPXI9laZfn8TCrPoxPIfq0Q1jpdGj+YFw+xwWR5KkvXrAwH2bHGOKp47g ==
X-ME-Sender: <xms:DKAPX5skSLhCRJockZb0TzedZhEhJ4Vg0bhjm21t9-LdWe39vBI7vw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrfeefgdefgecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif vghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepkeetueeikedtkeelfeekve fhkeffvedvvefgkefgleeugfdvjeejgeffieegtdejnecuvehluhhsthgvrhfuihiivgep udenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:DKAPXyf0dLj2bs2_70daY2PhJ0g7asSZBghpYYGuOAVyyjq2YnVDxA> <xmx:DKAPX8xWe3rt1e8cDOtxWkqAgPIjUvjFn8SE-l-X5o3XsIzlv1Dkqw> <xmx:DKAPXwOpcidua9zTfOP41oy4s8OsICnu8ihQmkteM7dHEtk6QqPY4A> <xmx:DaAPX_cABqhRZMjZfYvIRqE2sY7zKkINJvIOHR0NUBbE73fuuOnPuA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 4C2F3E00DF; Wed, 15 Jul 2020 20:32:12 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-52-g083df19-fm-idx2020-20200715.003-g083df194
Mime-Version: 1.0
Message-Id: <b33786ad-317a-4c33-849f-78c509d89beb@www.fastmail.com>
In-Reply-To: <20200716001134.GF9808@lubuntu>
References: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com> <20200715180231.GB9808@lubuntu> <CAKcm_gPfc3sFy0kuyTzUFk2XFMZ8NdXTd7CuNf0o0v+RXDG=xg@mail.gmail.com> <CH2PR22MB20861D3BEA06EE61AA882245DA7E0@CH2PR22MB2086.namprd22.prod.outlook.com> <CAKcm_gP24=x64QwcCdki-jxFXsLKiTPH8UYFdGOG3H1YJgEbOQ@mail.gmail.com> <9b265aef-d1bd-47cc-9a1c-677eef223c73@www.fastmail.com> <20200716001134.GF9808@lubuntu>
Date: Thu, 16 Jul 2020 10:31:53 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: quic@ietf.org
Subject: Re: Need your help: different connection IDs in the same datagram
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/eWn6J7qyOI2rrh1ZQFrqOHwi5ro>
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, 16 Jul 2020 00:32:15 -0000

On Thu, Jul 16, 2020, at 10:11, Dmitri Tikhonov wrote:
> On Thu, Jul 16, 2020 at 08:49:20AM +1000, Martin Thomson wrote:
> > * Receivers SHOULD discard coalesced packets if they are for a different
> > connection than the first; senders MAY discard coalesced packets that
>                              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> > contain a different value in the Destination Connection ID field than
> > the first.
> 
> I don't understand this.  What do you mean by "*senders* MAY
> discard packets?"

Brain misfire.  That should have been receivers.  Senders are required to make them all the same.


From nobody Wed Jul 15 17:32:55 2020
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 63F453A0F19 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 17:32:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level: 
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, 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 9_MU5it7RFiJ for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 17:32:52 -0700 (PDT)
Received: from mail-qv1-xf30.google.com (mail-qv1-xf30.google.com [IPv6:2607:f8b0:4864:20::f30]) (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 D04863A0F17 for <quic@ietf.org>; Wed, 15 Jul 2020 17:32:51 -0700 (PDT)
Received: by mail-qv1-xf30.google.com with SMTP id p7so1909415qvl.4 for <quic@ietf.org>; Wed, 15 Jul 2020 17:32:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mail-followup-to:references :mime-version:content-disposition:in-reply-to:user-agent; bh=uKLpFnPCBgm0AJJZewjn5O/ox/K81jV9MSb6gVs+gpU=; b=mfjwN3LdEp1+r0GQF+IPoiep1OaJ9/Pkb3Dn4oRZGslERwbv4H6pX12CDEbiAcbDsw fDsMjmyMbl8sL5YxfX9+qq29tONdpOHW//NGHGLxs508WaL0J62YJWZPMBvWy5xfwnSQ U78GutxTbaqsjjs84jfZDstkMNUKfrNmvHp0yOMr1Xk9HC/eDAQTj3pD32fC/18c9bDO qzvIi/Ci+Om/8hOe6utr7A0W4wSAtA9WKxGogyVteRnhFKQoIwCCwma5MqEWChybOI7F iZXILvwSeREGtGfWUSWE6FLuCWF2ZPAV24SqWOQuNfx5DhoNNMV03RDixmQFbTE2sECm Uxrg==
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=uKLpFnPCBgm0AJJZewjn5O/ox/K81jV9MSb6gVs+gpU=; b=T1zuto7Z3h9ZbK/camJ52NjbyMt2sgjdvLs6Ki+zbUMPgFNTyn7nrBUAhi4mqTOzYF dIPCky9i1NReDIoX9WVIMKBGJUqq0cGTfI941VOC8szjneBAE3g5bZnU6km4Gd1X30gq TRibLsEQpDLVv3bezR49/bA6smUUWkXfhG5Okszfkgp2YCIUQ7gHRaf/A+MWjaU9b/dZ E6xDeaKFGqrrlhScEghC/WtDnJhsgN6uGp1AZ4rsEGAw6o8Jvd4y5Bm3NDXtQxVZVJd2 siWrsMH99t2FfGRfzp9/bmLMQAKlRQC07KyWmt9A8E7KBg0x0Df/L+mOF/BA1EjX1eDq jYpA==
X-Gm-Message-State: AOAM530ggJgH3zWs9/zkp0znPJ8JiCDXElnziKTWsMQ6WueJJjxjkW1H YV0bcnp03dVvunByMyR4jMtojX01r71kMg==
X-Google-Smtp-Source: ABdhPJwLmRgor964z66m/uHbcWhRbHV4/8ng0f0WMuy5Lr12nhcirax4u+MMbHQPb7Z9IeqYH9M9Hw==
X-Received: by 2002:ad4:46ea:: with SMTP id h10mr1931288qvw.145.1594859570497;  Wed, 15 Jul 2020 17:32:50 -0700 (PDT)
Received: from lubuntu (ool-44c1d219.dyn.optonline.net. [68.193.210.25]) by smtp.gmail.com with ESMTPSA id y67sm5126468qka.101.2020.07.15.17.32.49 for <quic@ietf.org> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 15 Jul 2020 17:32:50 -0700 (PDT)
Date: Wed, 15 Jul 2020 20:32:44 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: quic@ietf.org
Subject: Re: Need your help: different connection IDs in the same datagram
Message-ID: <20200716003244.GG9808@lubuntu>
Mail-Followup-To: quic@ietf.org
References: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com> <20200715180231.GB9808@lubuntu> <7ee5a352-fef6-44ed-9e82-09194aae366e@www.fastmail.com> <20200715235957.GE9808@lubuntu> <4f59efcf-0fc6-4e64-ad20-8eb4e1978095@www.fastmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <4f59efcf-0fc6-4e64-ad20-8eb4e1978095@www.fastmail.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/mh--QnXdQawItBPKUvjv4BwIDSU>
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, 16 Jul 2020 00:32:53 -0000

On Thu, Jul 16, 2020 at 10:29:07AM +1000, Martin Thomson wrote:
> On Thu, Jul 16, 2020, at 09:59, Dmitri Tikhonov wrote:
> > You've lost me a bit, Martin.  Is this the code you aimed for?
> ....
> >         if (conn)
> >         {
> >   #if VARIANT_A
> >             if (!conn_owns_scid(conn, dcid))
> >   #elif VARIANT_B
> >             if (conn != lookup_by_dcid(dcid))
> >   #else
> > 	    if (false)
> >   #endif
> >                 continue;
> >         }
> >         conn = process_packet(quic_packet);
> >     }
> 
> Yeah, the point being that the check here is added at your discretion.
> It is possible to rely on the crypto to ensure that the connection
> rejects anything that isn't intended for it.

I see.  That's true, this is another way to do it.  On the other hand,
this is even less efficient than a hash lookup.

  - Dmitri.


From nobody Wed Jul 15 18:38:01 2020
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 871853A0883 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 18:37:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 RrjkOILa0-Sp for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 18:37:58 -0700 (PDT)
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 BF50C3A0882 for <quic@ietf.org>; Wed, 15 Jul 2020 18:37:57 -0700 (PDT)
Received: by mail-lj1-x22a.google.com with SMTP id j11so5126106ljo.7 for <quic@ietf.org>; Wed, 15 Jul 2020 18:37:57 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to:cc; bh=f7oZnity7NfS03wjUqDzz19nlUSqohsHQHh97gKZPG4=; b=OpSk+aJuWsvyAde7CFFLUwF3J++iJpQt2ddRjGgSiCj8ftMK8A3MQFoy2afC8rnQxn C8XRU2jnQTmyHdPPSyoZ7OMXASXjmvTOoC4gbCPWceJhWhhkrej0BHkjoDSnwrxhb9ad lE9/twdMOiwOhSied2BX+eZCNXSXfkbCZ/y1DhNmZPvOb9uPX94Y+3k74C2Hqtu6nC8f DuHKEQgYwGnqB5dvdX8k/OcYdkG4pDeeoqaGAp8ioYpnfKn3XbLpVm/JibQrLw5WWqlC Mf5FqzJP7bovJ2Tmg+AazSwKqfUBWsc/mGDEOsiyLTj3QKDHNNNWXcvEJyyvCqUDTQAQ U3jA==
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=f7oZnity7NfS03wjUqDzz19nlUSqohsHQHh97gKZPG4=; b=gc7PKPpOAIr+sVeHj9Hik2+vXcQXNX89HhEeOGiH+GroDh4HIXiuxrpx6TyUn+J6jV jCIyEvXOt7WnCt2WN2NiE58NVNzOiacE2stVZxvmS3v4WZEN2fObwdrfsl2cBS5uzYgb K7ZfT6o/a7Nl+TCNd13LTOr2rkP2Up+EnQCG6HML79Ykrps7kRL77LmHRqiRpVZ69S5h v76VEHhX2xSA5NWZxVGgmL4Kqx6taI8YR3eONeSAvfuY87jWoKtwYS5DM4Jyen5YadNa qrNBnnGxmEeA+etNTf+MIVnXJIINhn1dKxmV3dtsgfCDwUxABMLrHPpZNQQkoui5Z4Uk rWmg==
X-Gm-Message-State: AOAM532S39pdHjIE/yJ+wjvTfkyphFIIR7RjyKM97amqVbcLKqQML80i 7fcSQvRKz1qV8MbIxu29tDtpQOZAuOXuzLgbMJ8=
X-Google-Smtp-Source: ABdhPJxU91Q5uoBAs39JOdyZSKD6dT0+rqY0HEv80f0M/ojbGu7kX+Gj1kesUAx/x9iiwQwBsxvg92gpcKDJLm0Q9zI=
X-Received: by 2002:a2e:b5a8:: with SMTP id f8mr763556ljn.247.1594863475843; Wed, 15 Jul 2020 18:37:55 -0700 (PDT)
MIME-Version: 1.0
From: David Schinazi <dschinazi.ietf@gmail.com>
Date: Wed, 15 Jul 2020 18:37:45 -0700
Message-ID: <CAPDSy+60E2fnuAhN1SPVgs5_b0FW7qnU-N709UmuLBt991w=xA@mail.gmail.com>
Subject: Comments on draft-bider-ssh-quic
To: denis bider <denisbider.ietf@gmail.com>
Cc: QUIC <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f165d505aa851625"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/tj8XA7mYIfA9YGI9yqugnR9TEHQ>
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, 16 Jul 2020 01:38:00 -0000

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

Hi Denis,

Thanks for writing draft-bider-ssh-quic
<https://datatracker.ietf.org/doc/draft-bider-ssh-quic/>!
I've been thinking about SSH over QUIC but never found
the time to actually sit down and write anything.

I have some comments, mainly on QUIC (I know QUIC
better than I know SSH).

I don't think your plan to use QUIC short headers without
long headers is viable. In QUIC, we use long headers to
determine the QUIC version, and also connection IDs.
QUIC won't work without that. I see that you exchange that
information in SSH_QUIC_INIT/SSH_QUIC_REPLY but
that won't work with QUIC load balancers. You're also
reinventing something that already works, which will mean
additional implementation work.

I think it might be simpler to build something closer to
QUICv1. For example, you could reuse the QUIC
CRYPTO stream in INITIAL packets to perform the
SSH key exchange. This would provide multiple features:
- QUIC would handle retransmissions for you
- there is no longer a size limit on those packets

Regarding the obfuscated envelope, I think that's an
interesting feature, but it would be even more useful if
we could define it as an extension to QUIC in general.
That way other application protocols could benefit from it.

All in all, this is really great work, but perhaps it would
benefit from less changes from regular QUIC.

Cheers,
David

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

<div dir=3D"ltr">Hi Denis,<div><br></div><div>Thanks for writing=C2=A0<a hr=
ef=3D"https://datatracker.ietf.org/doc/draft-bider-ssh-quic/">draft-bider-s=
sh-quic</a>!</div><div>I&#39;ve been thinking about SSH over QUIC but never=
 found=C2=A0</div><div>the time to actually sit down and write anything.</d=
iv><div><br></div><div>I have some comments, mainly on QUIC (I know QUIC</d=
iv><div>better than I know SSH).</div><div><br></div><div>I don&#39;t think=
=C2=A0your plan to use QUIC short headers without</div><div>long headers is=
 viable. In QUIC, we use long headers to</div><div>determine the QUIC versi=
on, and also connection IDs.</div><div>QUIC won&#39;t work without that. I =
see that you exchange that</div><div>information in SSH_QUIC_INIT/SSH_QUIC_=
REPLY but</div><div>that won&#39;t work with QUIC load balancers. You&#39;r=
e also</div><div>reinventing something that already=C2=A0works, which will =
mean</div><div>additional implementation work.</div><div><br></div><div>I t=
hink it might be simpler to build something closer to</div><div>QUICv1. For=
 example, you could reuse the QUIC</div><div>CRYPTO stream in INITIAL packe=
ts to perform the</div><div>SSH key exchange. This would provide multiple f=
eatures:</div><div>- QUIC would handle retransmissions for you</div><div>- =
there is no longer a size limit on those packets</div><div><br></div><div>R=
egarding the obfuscated envelope, I think that&#39;s an</div><div>interesti=
ng feature, but it would be even more useful if</div><div>we could define i=
t as an extension to QUIC in general.</div><div>That way other application =
protocols could benefit from it.</div><div><br></div><div>All in all, this =
is really great work, but perhaps it would</div><div>benefit from less chan=
ges from regular QUIC.</div><div><br></div><div>Cheers,</div><div>David</di=
v></div>

--000000000000f165d505aa851625--


From nobody Wed Jul 15 18:40:21 2020
Return-Path: <watsonbladd@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 22B623A08B7 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 18:40:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, 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 megt_6Osxh80 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 18:40:18 -0700 (PDT)
Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D1D413A08B2 for <quic@ietf.org>; Wed, 15 Jul 2020 18:40:17 -0700 (PDT)
Received: by mail-lj1-x22e.google.com with SMTP id s9so5101264ljm.11 for <quic@ietf.org>; Wed, 15 Jul 2020 18:40:17 -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=JGWt+tgtNhEmkvuztL/R3bX5iNtEFsruR1r/bfzu0jA=; b=XJgJnO+vXQ3qB07R5aQ39QyuQnf1Ulqn3DcFwLNi10qPmbJ/W6gxwN0PIY8TLGKjWv yiOjNVb6EDea0kcP8FSRXvadBNlW+22ytWbTrW5kdTbHY8fC9ysAhENPO+7TJ4ykH9MJ OrgnfYTdwrlDXOEUGX2RjfpEV+jZS2qa/iG1anQqNXasNJS/6eXsqvkCoecARS83VlKN guxCRKryE/j3jlt/xF4SVI40vDs/9Mu2uSZLSC8t5j4gWx4s2/CqlEoDDCdMk9lmSH+c FFnHH+SC+nIjjdXvXtxsYfX9CmwYD/AgmKLgTT/xwjpknaTI7p8YiTuXAR1O4DeH23+x hHxw==
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=JGWt+tgtNhEmkvuztL/R3bX5iNtEFsruR1r/bfzu0jA=; b=YwEJdPQAqf5T9+ffgTXgi4dx4YnSQDY8ihYLKY7UnGAxbsjcjrjQF/qnuUUg3kGWfn RORP1R2RnEc21Bk1fUZw0TkvDC+gIcqkTH8nyqhnRQulQCYFQBY/Ql8Zn01kQBw/W4Yu dw9T3EEbW6KbmZcrNN6UqyHeKhjoJPzz0K2JEwGZJOU6ORuC1z6mU7DCk43/IjRxfELL 560JxzA5ps3BoI8dA5IQ7pZ5J2gXz1Q1s61tV7BsthC5rHMCaQB+uH2a14JEPAW4NpbZ c24MQedhomYpP7oQgfviWuL8drnCtNTApSxqlVTdKQrThiiGlfknpNSlurPHY1a8gzpw wOSw==
X-Gm-Message-State: AOAM531Kh+OuZZk8962Wj5zvYnpwyPB2WTAQK0izHk5+OAd1GTUMxvj9 se44IYZvGdR0M9gi0MIPR/zDD56QIQEHK2IpHkwFmV4q
X-Google-Smtp-Source: ABdhPJzP6xVWz8YNhFaSpPqw9ukULJveWrZTF9k1s9mE9e01vSfmz1TAxzKmP+Gasd6ap4YaRj17zcXaIEZdkk7RWlg=
X-Received: by 2002:a2e:1514:: with SMTP id s20mr773639ljd.455.1594863616016;  Wed, 15 Jul 2020 18:40:16 -0700 (PDT)
MIME-Version: 1.0
References: <43bb1525-0afa-4c4e-a234-f6ccfacbdd29@www.fastmail.com> <a4d7e8cf-5879-6941-e059-5d2f3e67ae86@huitema.net> <58b40fc0-86ad-49e9-bc17-187c38e97f7a@www.fastmail.com> <1d543593-7abc-4a89-93c5-82c464492786@www.fastmail.com> <CACpbDccSB6H9AhmAinia7ojEg1VY-S=dF214wHvZcZkoiL-xFA@mail.gmail.com> <7d549475-249b-4674-9aa8-c2bf9953243b@www.fastmail.com> <CALGR9oaHQHJneN2edetGLcq4u4PNF0oAyq9PKc7ZVxz_pXTMGw@mail.gmail.com>
In-Reply-To: <CALGR9oaHQHJneN2edetGLcq4u4PNF0oAyq9PKc7ZVxz_pXTMGw@mail.gmail.com>
From: Watson Ladd <watsonbladd@gmail.com>
Date: Wed, 15 Jul 2020 21:40:03 -0400
Message-ID: <CACsn0c=HkByj0dkwfW+0=n9HzGZ0cZamot6N=AFks3wbnwnWXQ@mail.gmail.com>
Subject: Re: New confidentiality and integrity limits
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: QUIC WG <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Ppd1Fqv0xDeUS4KLkeAKQbVZXYE>
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, 16 Jul 2020 01:40:19 -0000

I do not believe the analysis is correct.

A forgery against a QUIC connection will be checked at one or at most
two keys: the current one and the next one. It is not the case that a
forgery will be attempted against all the keys simultaneously: it will
have to be resent. Perhap I'm missing something about the setting here
that makes this the multiuser and not the singleuser setting.

Sincerely,
Watson


From nobody Wed Jul 15 21:59:03 2020
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 CB6E23A0D3F for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 21:59:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=HSy9KkPk; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=etbS/yPD
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eMowBN9NbClv for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 21:59:00 -0700 (PDT)
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 7F2553A0D3E for <quic@ietf.org>; Wed, 15 Jul 2020 21:59:00 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id BE7855C0144; Thu, 16 Jul 2020 00:58:59 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Thu, 16 Jul 2020 00:58:59 -0400
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=fm2; bh=vvLnez5CSHsKVZOAO8W5O7Kpbpuo7cn 40uCFxL4PArE=; b=HSy9KkPkCxEwz4vID7ykXoq2WTUeEbqUxcj6jPahuyzWf6t TaJu0pOMGsO1N7yfTOdvy5RqxtA2l/DelW9g9W0NLucehRAyY/hyxAOaKbQQSpjp xk5yQSaoRTUUsi5P6oeGaMtYCu85NUb/zwbFByUstw+DwdOMSLov2jCsSUF03a7T zsgxeEqGNYiMLWgoOoNuokOt8aRk2MQi2FttS3spa/QCHAme57MXRzN1Dt2N5UuJ NgUiqHzc+njChZyxSC277BGhrivYjgpX+hxS85tv+nks7C6pyffZ8Uu3gvvKJ/w1 Jed8UbSbl4K1segwLRqNeYD87S4gY469PAObJeQ==
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=fm3; bh=vvLnez 5CSHsKVZOAO8W5O7Kpbpuo7cn40uCFxL4PArE=; b=etbS/yPD+Ww4RnHdIrkvHv UwcNg7FOw2hBSjGOXJL69PD80ZC3cwyEDJmVhRFLOEvzS0033deQTX6FQ1BwBJN9 YX0xsHr2gdeTtthi+DXpVe36idj+yLpgF4rjTkZ2eOb53eOcO6f0OBsY23dcV1Gl jfkKY+1BmUmOEM34KCYc3nVrj3egGNiHt6XDG2PUQCNhQxzNLuEwr87hgfyPoaro EOf8yrmiqko/En2TJ7yzXd8B1hVxnuaFL3uyKlwlGWq9AWUMEAc/txdzn9FtffyI kuLW/LKPCPDagQNxt9o3UfAkxo2P1sgrMpH44ya0Bi2gmx4VdS3uvmAdZJ2cjCdQ ==
X-ME-Sender: <xms:k94PX628iFFfKXk4i_dfUOFC0tM9ON-5Brdg5D7MNeLfDC2CXYmQYg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrfeefgdeklecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif vghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepkeetueeikedtkeelfeekve fhkeffvedvvefgkefgleeugfdvjeejgeffieegtdejnecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:k94PX9HfLc4AEmf2cW66_gARc-eL_BtdvAhi-XMA6BPxCgyESDlREw> <xmx:k94PXy5qqoq3NKYBGQIahfgxdA1pM_LFqs_BDKi3yyfn2s8Ghw7wvg> <xmx:k94PX731PzHJhKg0cqsPUF3x41GI9vF-1ZBoPIDpvXqOhSGPJfRljQ> <xmx:k94PXxQwIbQRI8QDZ5qiaD1cyyb-80keSa4C9m6FfrzVecGeXy2vFg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 455B1E00DF; Thu, 16 Jul 2020 00:58:59 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-52-g083df19-fm-idx2020-20200715.003-g083df194
Mime-Version: 1.0
Message-Id: <19922b1a-a02c-46c9-b441-3806d3f77b89@www.fastmail.com>
In-Reply-To: <CACsn0c=HkByj0dkwfW+0=n9HzGZ0cZamot6N=AFks3wbnwnWXQ@mail.gmail.com>
References: <43bb1525-0afa-4c4e-a234-f6ccfacbdd29@www.fastmail.com> <a4d7e8cf-5879-6941-e059-5d2f3e67ae86@huitema.net> <58b40fc0-86ad-49e9-bc17-187c38e97f7a@www.fastmail.com> <1d543593-7abc-4a89-93c5-82c464492786@www.fastmail.com> <CACpbDccSB6H9AhmAinia7ojEg1VY-S=dF214wHvZcZkoiL-xFA@mail.gmail.com> <7d549475-249b-4674-9aa8-c2bf9953243b@www.fastmail.com> <CALGR9oaHQHJneN2edetGLcq4u4PNF0oAyq9PKc7ZVxz_pXTMGw@mail.gmail.com> <CACsn0c=HkByj0dkwfW+0=n9HzGZ0cZamot6N=AFks3wbnwnWXQ@mail.gmail.com>
Date: Thu, 16 Jul 2020 14:58:33 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: quic@ietf.org, =?UTF-8?Q?Felix_G=C3=BCnther?= <mail@felixguenther.info>
Subject: Re: New confidentiality and integrity limits
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/1eI0BJSTB9BDk_vQwYQHuNPX49M>
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, 16 Jul 2020 04:59:02 -0000

On Thu, Jul 16, 2020, at 11:40, Watson Ladd wrote:
> I do not believe the analysis is correct.
> 
> A forgery against a QUIC connection will be checked at one or at most
> two keys: the current one and the next one. It is not the case that a
> forgery will be attempted against all the keys simultaneously: it will
> have to be resent. Perhap I'm missing something about the setting here
> that makes this the multiuser and not the singleuser setting.

Thanks for checking Watson.

I had exactly the same thought, but was convinced by Felix that the analysis was based on a definition that only considers the number of encryption/verification queries in total. In particular, that the values in results are not limited in any way by which subset of the keys could be tried.

Incidentally, that also supports the view that there is degradation in the confidentiality advantage as you update to different keys.  I note that the PR does not acknowledge this, but maybe it should.

I confess that I'm still not completely confident that the multiuser setting is a good fit for our needs (or even that the threat model is the right one).  This is, in part of the reason you state: the mu setting assumes that the attacker has equal access to all "users" concurrently and the limited number of active keys would seem to make that difficult to exploit.  But I don't know how to prove that this is an acceptable assumption.

What I am confident about is that a conservative approach doesn't hurt a great deal here.  The calculated limits for GCM are high enough - even under the assumptions made - that you have serious problems if you hit them.


From nobody Wed Jul 15 22:09:00 2020
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 5CDA33A0D50 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 22:08:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 2iQG_aM1NXCD for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 22:08:57 -0700 (PDT)
Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (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 B5F553A0D4B for <quic@ietf.org>; Wed, 15 Jul 2020 22:08:56 -0700 (PDT)
Received: by mail-lf1-x131.google.com with SMTP id b30so293535lfj.12 for <quic@ietf.org>; Wed, 15 Jul 2020 22:08:56 -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;  bh=vlORikIBMMXr8O3JZhwcG4hBq5u1GDft2TIae+gDyEc=; b=htJBbFWlAeaFssrPwPQezj3A0P2Ehb8cC8FxstfRk8UaAeDVQJdWCU6wl1AIZCC1zS 14NUhXBRpUFNwjaM27h8DujLpX2aPKMKZcrYfd8k7bo6deVywonH4h2Qq1oePzANAuPG U3OQp1A5MJoDFa+ebzfF6DXWXSy3/08baBKn6fVvh3F4hyRPd683mHtJOIyVzdP9uGfG RTkGski79gKv/8U5lhIie9qre3sgI7BYHqc7uEeZR9Xdk5Iv22ExWex4XSUlYjdXhD2K BhnB5fEx5SecAwSYhOwLAQDtx5+xvBlH31zwzXv5ur+aR2SsQGjL1DmCbvztcce2eqN2 tjWQ==
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=vlORikIBMMXr8O3JZhwcG4hBq5u1GDft2TIae+gDyEc=; b=Z/Gl+aUh5QCNlKWejfiGzpM9Hqx2GQ25J0xQrJA1HAyrmD3BlpEJFjWzejWGsAst5v 9SjN6Ut5WHFZyoXJUiT+934JfoDPNdU+YjLvNNCR7TRqccYMjyJGjJ9IwncjfhjeFnLW UM2sGc5rhPzHuiXvbs+mrjbvXhFaGw0mTSMNnNHejd4GeJmAXSGRT5eaP7AEbp3ScTXV HjjeWCNLqJjtZNnUMy/+5HBznUgUefkxtXjixSbG02FjMAiGUhyAdUqOB5xEJupPKRmZ kIEAlKJI2bqA/R8ELntyFXmxBerl4KdHatrEv58+wnxSOr9bFY7neNkVndZQb/F1fbIZ V2jA==
X-Gm-Message-State: AOAM530MygJcg34c2a2bz31NgpXasxtplDjiWaniT7h3EAmoG6be4c6v ecD/1acr7LboIbr7kZWtsI+rl8vZHF13RwjwEvNsfQno
X-Google-Smtp-Source: ABdhPJzDN7q0Ma8Z9JYASo9F+rQ1f1NwjwO8y63CJusb/XRLz9/dq2nThLJpEqktKTo8XEIwy5UNWzzIe9FbTMYDOlw=
X-Received: by 2002:ac2:4550:: with SMTP id j16mr1191039lfm.37.1594876134484;  Wed, 15 Jul 2020 22:08:54 -0700 (PDT)
MIME-Version: 1.0
References: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com> <20200715180231.GB9808@lubuntu> <7ee5a352-fef6-44ed-9e82-09194aae366e@www.fastmail.com> <20200715235957.GE9808@lubuntu> <4f59efcf-0fc6-4e64-ad20-8eb4e1978095@www.fastmail.com> <20200716003244.GG9808@lubuntu>
In-Reply-To: <20200716003244.GG9808@lubuntu>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Wed, 15 Jul 2020 22:08:43 -0700
Message-ID: <CACpbDceED0kb0Dd3-iCfzFU0At_vb85U2taSZW_3R-WtbRjazQ@mail.gmail.com>
Subject: Re: Need your help: different connection IDs in the same datagram
To: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000074eea605aa8809d0"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/32RAuEPmachLjzgDtO7WXqsx9UE>
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, 16 Jul 2020 05:08:58 -0000

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

The spirit of the text, as far as I remember, _was_ meant to prevent
multiple connections from being coalesced.

The text for a sender prohibits packets from multiple connections being
coalesced.

A receiver can be one of three things:
1. It can compare state across packets within a datagram. In this case, it
can enforce the policy of not coalescing packets from multiple connections.
2. It cannot compare CIDs across packets within a connection, and it
delivers all packets to the connection with the first CID. In this case, if
multiple coalesced packets belong to multiple connections, then subsequent
packets are undecryptable by the chosen connection, and dropped.
3. It cannot compare CIDs across packets within a connection, but it does a
lookup and delivers each coalesced packet to the correct connection. This
violates the SHOULD that PR 3870 proposes, but that is not a MUST, and one
could use this wiggle room if it's difficult to change the implementation.

In all three cases, I don't see that the new behavior in PR 3870 (SHOULD
drop subsequent coalesced packets belonging to a different connection)
makes it harder for any implementation in question. What am I missing?

All that said, I am fine with prohibiting mixing CIDs if that's where we're
leaning.

On Wed, Jul 15, 2020 at 5:33 PM Dmitri Tikhonov <dtikhonov@litespeedtech.com>
wrote:

> On Thu, Jul 16, 2020 at 10:29:07AM +1000, Martin Thomson wrote:
> > On Thu, Jul 16, 2020, at 09:59, Dmitri Tikhonov wrote:
> > > You've lost me a bit, Martin.  Is this the code you aimed for?
> > ....
> > >         if (conn)
> > >         {
> > >   #if VARIANT_A
> > >             if (!conn_owns_scid(conn, dcid))
> > >   #elif VARIANT_B
> > >             if (conn != lookup_by_dcid(dcid))
> > >   #else
> > >         if (false)
> > >   #endif
> > >                 continue;
> > >         }
> > >         conn = process_packet(quic_packet);
> > >     }
> >
> > Yeah, the point being that the check here is added at your discretion.
> > It is possible to rely on the crypto to ensure that the connection
> > rejects anything that isn't intended for it.
>
> I see.  That's true, this is another way to do it.  On the other hand,
> this is even less efficient than a hash lookup.
>
>   - Dmitri.
>
>

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

<div dir=3D"ltr"><div><br></div><div>The spirit of the text, as far as I re=
member, _was_ meant to prevent multiple connections from being coalesced.=
=C2=A0</div><div><br></div><div>The text for a sender prohibits packets fro=
m multiple connections being coalesced.</div><div><br></div><div>A receiver=
 can be one of three things:</div><div>1. It can compare state across packe=
ts within a datagram. In this case, it can enforce the policy of not coales=
cing packets from multiple connections.</div><div>2. It cannot compare CIDs=
 across packets within a connection, and it delivers all packets to the con=
nection with the first CID. In this case, if multiple coalesced packets bel=
ong to multiple connections, then subsequent packets are undecryptable by t=
he chosen connection, and dropped.</div><div>3. It cannot compare CIDs acro=
ss packets within a connection, but it does a lookup and delivers each coal=
esced packet to the correct connection. This violates the SHOULD that PR 38=
70 proposes, but that is not a MUST, and one could use this wiggle room if =
it&#39;s difficult to change the implementation.</div><div><br></div><div>I=
n all three cases, I don&#39;t see that the new behavior in PR 3870 (SHOULD=
 drop subsequent coalesced packets belonging to a different connection) mak=
es it harder for any implementation in question. What am I missing?<br><br>=
All that said, I am fine with prohibiting mixing CIDs if that&#39;s where w=
e&#39;re leaning.</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr=
" class=3D"gmail_attr">On Wed, Jul 15, 2020 at 5:33 PM Dmitri Tikhonov &lt;=
<a href=3D"mailto:dtikhonov@litespeedtech.com">dtikhonov@litespeedtech.com<=
/a>&gt; wrote:<br></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">O=
n Thu, Jul 16, 2020 at 10:29:07AM +1000, Martin Thomson wrote:<br>
&gt; On Thu, Jul 16, 2020, at 09:59, Dmitri Tikhonov wrote:<br>
&gt; &gt; You&#39;ve lost me a bit, Martin.=C2=A0 Is this the code you aime=
d for?<br>
&gt; ....<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0if (conn)<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0{<br>
&gt; &gt;=C2=A0 =C2=A0#if VARIANT_A<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0if (!conn_owns_sci=
d(conn, dcid))<br>
&gt; &gt;=C2=A0 =C2=A0#elif VARIANT_B<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0if (conn !=3D look=
up_by_dcid(dcid))<br>
&gt; &gt;=C2=A0 =C2=A0#else<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0if (false)<br>
&gt; &gt;=C2=A0 =C2=A0#endif<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0cont=
inue;<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0}<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0conn =3D process_packet(quic_pac=
ket);<br>
&gt; &gt;=C2=A0 =C2=A0 =C2=A0}<br>
&gt; <br>
&gt; Yeah, the point being that the check here is added at your discretion.=
<br>
&gt; It is possible to rely on the crypto to ensure that the connection<br>
&gt; rejects anything that isn&#39;t intended for it.<br>
<br>
I see.=C2=A0 That&#39;s true, this is another way to do it.=C2=A0 On the ot=
her hand,<br>
this is even less efficient than a hash lookup.<br>
<br>
=C2=A0 - Dmitri.<br>
<br>
</blockquote></div>

--00000000000074eea605aa8809d0--


From nobody Wed Jul 15 23:40:57 2020
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 90FA63A0F9A for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 23:40:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 2A1w48ugxPws for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 23:40:52 -0700 (PDT)
Received: from mail-ej1-x62b.google.com (mail-ej1-x62b.google.com [IPv6:2a00:1450:4864:20::62b]) (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 559573A0F9C for <quic@ietf.org>; Wed, 15 Jul 2020 23:40:52 -0700 (PDT)
Received: by mail-ej1-x62b.google.com with SMTP id w6so5388568ejq.6 for <quic@ietf.org>; Wed, 15 Jul 2020 23:40:52 -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=xnpycQDCmgZhNCqt+dGjyFhRqZrLPLZG0g2+ESYsAsM=; b=GZqYTL0+BwAdPcdC6SgHDcLTl6ZxH1UIdUEdI0NzNJOaWDw5nPlHSPWFyFpedf8KTn FNJibhSbGqDPQDoidBaKpYNaXr3VI73kUslVmJepy3Gaz59A7XfZkUV4o5cGelSJEnEv fLPWS5Y7ArixRjSnr8rIKlZVZp2X5dZPGZF/e3iO0ZM0xOgLnfaeLZItyAkHzSe4KDdd DSlKkL/+cU6fEPqiGEblFwn9tcANdJ0/aCwPSr5LWGqUGNVOZJqYOGSyoe1nXVnxEKZA mHwmiJ/g2PMlrsgrtkVUhu6OyVpOp38WVG4xCLwtM2/xb8g5DH3gRxik4mzgw2bRb0YY 6sdA==
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=xnpycQDCmgZhNCqt+dGjyFhRqZrLPLZG0g2+ESYsAsM=; b=TtAp0bdH7BIBoacbvt4ytdDE98EjAue3cd7wpflxj4RBeE66x+c6LMkE//udwEjI1i vi8d6Jpnabx/43qMo7uXHnNxueNX2J0gfDH0RrJSMIBiJu5XXgDCPV+qQZujGpiraIkq Gjz8HrQsYLvGsvLoM5u5U9P52ytobqlHeHHNuz0KQK4vt8QGrtnLDxiZCCTsICIgmhEH FRSCVPCmkapjSPIAZdz1RP52IuHTJvZEtxWgU8uBfRT427bTzvNSB7Vns8SoS62AIquI xFeiRFT5lFTSzUy5QSAOlh5w2geVprPKxfFsar/gSGM/6kM84SuQokFdYr/fJ38oZZ1E r0wA==
X-Gm-Message-State: AOAM531AebxNv1glYBCc5/OUi1P2mhSbI4+deY5fo2YdGrEFdIlR84e/ Cc6Oo1YuZUmLOlETT5s2p9r+VZXeQv7rCMIOKJDQCw==
X-Google-Smtp-Source: ABdhPJz2iTwawlXiO/yKzlD1Ca6rTN4OZr+kb0M7AM4Brv3lnQpFw0jcwvWNRjQZHVPWw/N/P9QZrZKGjb8I7ASwnCw=
X-Received: by 2002:a17:906:1ec3:: with SMTP id m3mr2388979ejj.197.1594881650773;  Wed, 15 Jul 2020 23:40:50 -0700 (PDT)
MIME-Version: 1.0
References: <ae21cc02-3357-40c8-a1e9-3966fdf575a5@www.fastmail.com> <20200715180231.GB9808@lubuntu> <CAKcm_gPfc3sFy0kuyTzUFk2XFMZ8NdXTd7CuNf0o0v+RXDG=xg@mail.gmail.com> <CH2PR22MB20861D3BEA06EE61AA882245DA7E0@CH2PR22MB2086.namprd22.prod.outlook.com>
In-Reply-To: <CH2PR22MB20861D3BEA06EE61AA882245DA7E0@CH2PR22MB2086.namprd22.prod.outlook.com>
From: Kazuho Oku <kazuhooku@gmail.com>
Date: Thu, 16 Jul 2020 15:40:39 +0900
Message-ID: <CANatvzxwbF4_oUZusQOXvD4_JNo88fQa6t5kZ9Oo5_2Ok3qWPw@mail.gmail.com>
Subject: Re: Need your help: different connection IDs in the same datagram
To: Mike Bishop <mbishop@evequefou.be>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>,  Martin Thomson <mt@lowentropy.net>, IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000040d1e005aa895221"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Xa4uwCJp5cg6mzwpWFHxH24-vGw>
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, 16 Jul 2020 06:40:56 -0000

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

2020=E5=B9=B47=E6=9C=8816=E6=97=A5(=E6=9C=A8) 5:43 Mike Bishop <mbishop@eve=
quefou.be>:

> Fundamentally, I think there has to be a change, because we currently hav=
e
> an inconsistent mandate =E2=80=93 mixed-CID packets are acceptable to sen=
d, but
> SHOULD be dropped on receipt.
>

+1 to what Mike says here (as well as others).

We need to fix either the send side or the receive side.

Regarding which side to fix, my preference goes to fixing the receive side
(i.e. change the text to allow coalesced QUIC packets using different
DCIDs).

IIUC, that's the extension of our principle that "datagrams" can be routed,
while packets have to be handled individually.

I do understand that some of us want to reduce the cost of checking the
CIDs when their stacks receive a coalesced QUIC packet. I am not sure if
that is worth having an exception on the aforementioned principle. The
performance gain is going to be much smaller than (un)protecting packets or
processing TLS handshake messages contained in the coalesced packets.

All that said, as an implementer, I am fine with either way of fixing it.


>
>
> First, there=E2=80=99s the privacy argument, in that the CIDs in the same=
 datagram
> will become linked to external observers.  I think Marten has already
> argued convincingly why this will be rare during a typical handshake;
> Christian and Kazuho have argued that a privacy-sensitive implementation
> will need to do a CID jump once the handshake is confirmed, at which poin=
t
> you=E2=80=99re mostly not coalescing packets anyway.  So this is a mild a=
rgument
> for not mixing, but I don=E2=80=99t think it=E2=80=99s dispositive.
>
>
>
> Second, the implementation arguments appear to boil down to two camps:
>
>    - Implementation X generates packets independently, then packages them
>    into datagrams.  Since all packets waiting for packaging are from the =
same
>    connection, there=E2=80=99s currently nothing to check to see whether =
they=E2=80=99re
>    allowed in the same datagram.  Requiring the CIDs to match would requi=
re a
>    new check and a code path for *not* coalescing packets in certain
>    cases.
>    - Implementation Y consumes packets within a datagram independently,
>    so the validation has to be done at the datagram level before doing an=
y
>    packet-level activities.  A requirement that can be evaluated solely o=
n the
>    contents of the datagram, independent of any connection state, is more
>    efficient.
>
>
>
> Of these two, I currently find the latter slightly more persuasive.  The
> first is a check that can be done between packets without needing to acce=
ss
> any connection state, and there are already presumably code paths for
> handling when a waiting packet can=E2=80=99t go in the datagram currently=
 being
> constructed (e.g. it=E2=80=99s too large to fit the remaining MTU).  Howe=
ver, I=E2=80=99m
> sure someone with such an implementation could tell me why it=E2=80=99s m=
ore
> complicated than that.  =F0=9F=98=8A
>
>
>
> Neither of the resolutions seems more technically correct than the other;
> we just need to pick one.
>
>
>
> *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of * Ian Swett
> *Sent:* Wednesday, July 15, 2020 3:31 PM
> *To:* Martin Thomson <mt@lowentropy.net>; IETF QUIC WG <quic@ietf.org>
> *Subject:* Re: Need your help: different connection IDs in the same
> datagram
>
>
>
> I don't think this change would be difficult for our implementation, but =
I
> also don't see it as necessary.  Given where we are in the process, that
> alone argues for not changing it I believe.
>
>
>
> On Wed, Jul 15, 2020 at 2:02 PM Dmitri Tikhonov <
> dtikhonov@litespeedtech.com> wrote:
>
> On Wed, Jul 15, 2020 at 05:23:57PM +1000, Martin Thomson wrote:
> > There has been some opposition to the proposed resolution in PR 3870.
> >
> > Apparently, for some, having multiple connection IDs in the same
> > datagram complicates processing.  I don't understand this objection.
> > It seems to me more difficult to retain state across packets than it
> > is to process each atomically.  I was hoping that Christian or Nick
> > can explain more about how this affects them.
>
> I can provide an example from lsquic.  The datagram is parsed into
> QUIC packets in one function, lsquic_engine_packet_in():
>
>
> https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic=
_engine.c#L2781L2816
>
> Each QUIC packet is processed by process_packet_in(), where a
> connection is looked up:
>
>
> https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic=
_engine.c#L1352L1360
>
> The DCID check is performed lsquic_engine_packet_in(), before
> process_packet_in() is called:
>
>
> https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic=
_engine.c#L2793L2806
>
> The DCID information is readily available in the datagram parsing
> loop, while connection information is not.
>
> For lsquic to support the proposed change, it would have to remember
> the current connection and then query it whether it is indeed the
> owner of the next DCID (A) or look up DCID in the global hash (B):
>
>     conn =3D NULL;
>     while (quic_packet =3D parse_udp(pointers)) {
>         dcid =3D parse(quic_packet);
>         if (conn)
>         {
>   #if VARIANT_A
>             if (!conn_owns_scid(conn, dcid))
>   #else
>             if (conn !=3D lookup_by_dcid(dcid))
>   #endif
>                 continue;
>         }
>         conn =3D process_packet(quic_packet);
>     }
>
> Not that it could not be done, of course, but it is both extra work
> to modify lsquic and a more inefficient mechanism: what was a simple
> CID comparison is now a hash lookup.
>
> That's why I argued [1] for having solid rationale behind the change
> rather than a personal preference.
>
>   - Dmitri.
>
> 1.
> https://github.com/quicwg/base-drafts/issues/3800#issuecomment-656851626
>
>

--=20
Kazuho Oku

--00000000000040d1e005aa895221
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">2020=E5=B9=B47=E6=9C=8816=E6=97=A5(=
=E6=9C=A8) 5:43 Mike Bishop &lt;<a href=3D"mailto:mbishop@evequefou.be">mbi=
shop@evequefou.be</a>&gt;:<br></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(204,204,204);padding-left:1ex">





<div lang=3D"EN-US">
<div class=3D"gmail-m_-841099711305584844WordSection1">
<p class=3D"MsoNormal">Fundamentally, I think there has to be a change, bec=
ause we currently have an inconsistent mandate =E2=80=93 mixed-CID packets =
are acceptable to send, but SHOULD be dropped on receipt.</p></div></div></=
blockquote><div><br></div><div>+1 to what Mike says here (as well as others=
).</div><div><br></div><div>We need to fix either the send side or the rece=
ive side.</div><div><br></div><div>Regarding which side to fix, my preferen=
ce goes to fixing the receive side (i.e. change the text to allow coalesced=
 QUIC packets using different DCIDs).</div><div><br></div><div>IIUC, that&#=
39;s the extension of our principle that &quot;datagrams&quot; can be route=
d, while packets have to be handled individually.</div><div><br></div><div>=
I do understand that some of us want to reduce the cost of checking the CID=
s when their stacks receive a coalesced QUIC packet. I am not sure if that =
is worth having an exception on the aforementioned principle. The performan=
ce gain is going to be much smaller than (un)protecting packets or processi=
ng TLS handshake messages contained in the coalesced packets.</div><div><br=
></div><div>All that said, as an implementer, I am fine with either way of =
fixing it.</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;bor=
der-left-color:rgb(204,204,204);padding-left:1ex"><div lang=3D"EN-US"><div =
class=3D"gmail-m_-841099711305584844WordSection1"><p class=3D"MsoNormal"><u=
></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">First, there=E2=80=99s the privacy argument, in that=
 the CIDs in the same datagram will become linked to external observers.=C2=
=A0 I think Marten has already argued convincingly why this will be rare du=
ring a typical handshake; Christian and Kazuho
 have argued that a privacy-sensitive implementation will need to do a CID =
jump once the handshake is confirmed, at which point you=E2=80=99re mostly =
not coalescing packets anyway.=C2=A0 So this is a mild argument for not mix=
ing, but I don=E2=80=99t think it=E2=80=99s dispositive.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Second, the implementation arguments appear to boil =
down to two camps:<u></u><u></u></p>
<ul style=3D"margin-top:0in" type=3D"disc">
<li class=3D"gmail-m_-841099711305584844MsoListParagraph" style=3D"margin-l=
eft:0in">Implementation X generates packets independently, then packages th=
em into datagrams.=C2=A0 Since all packets waiting for packaging are from t=
he same connection, there=E2=80=99s currently nothing
 to check to see whether they=E2=80=99re allowed in the same datagram.=C2=
=A0 Requiring the CIDs to match would require a new check and a code path f=
or
<i>not</i> coalescing packets in certain cases.<u></u><u></u></li><li class=
=3D"gmail-m_-841099711305584844MsoListParagraph" style=3D"margin-left:0in">=
Implementation Y consumes packets within a datagram independently, so the v=
alidation has to be done at the datagram level before doing any packet-leve=
l activities.=C2=A0 A requirement that
 can be evaluated solely on the contents of the datagram, independent of an=
y connection state, is more efficient.<u></u><u></u></li></ul>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Of these two, I currently find the latter slightly m=
ore persuasive.=C2=A0 The first is a check that can be done between packets=
 without needing to access any connection state, and there are already pres=
umably code paths for handling when a waiting
 packet can=E2=80=99t go in the datagram currently being constructed (e.g. =
it=E2=80=99s too large to fit the remaining MTU).=C2=A0 However, I=E2=80=99=
m sure someone with such an implementation could tell me why it=E2=80=99s m=
ore complicated than that.=C2=A0
<span style=3D"font-family:&quot;Segoe UI Emoji&quot;,sans-serif">=F0=9F=98=
=8A</span><u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">Neither of the resolutions seems more technically co=
rrect than the other; we just need to pick one.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border-style:solid none none;border-top-width:1pt;border-top-=
color:rgb(225,225,225);padding:3pt 0in 0in">
<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>
Ian Swett<br>
<b>Sent:</b> Wednesday, July 15, 2020 3:31 PM<br>
<b>To:</b> Martin Thomson &lt;<a href=3D"mailto:mt@lowentropy.net" target=
=3D"_blank">mt@lowentropy.net</a>&gt;; IETF QUIC WG &lt;<a href=3D"mailto:q=
uic@ietf.org" target=3D"_blank">quic@ietf.org</a>&gt;<br>
<b>Subject:</b> Re: Need your help: different connection IDs in the same da=
tagram<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">I don&#39;t think this change would be difficult for=
 our implementation, but I also don&#39;t see it as necessary.=C2=A0 Given =
where we are in the process, that alone argues for not changing it I believ=
e.<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Wed, Jul 15, 2020 at 2:02 PM Dmitri Tikhonov &lt;=
<a href=3D"mailto:dtikhonov@litespeedtech.com" target=3D"_blank">dtikhonov@=
litespeedtech.com</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote style=3D"border-style:none none none solid;border-left-width:1p=
t;border-left-color:rgb(204,204,204);padding:0in 0in 0in 6pt;margin-left:4.=
8pt;margin-right:0in">
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt">On Wed, Jul 15, 2020 at=
 05:23:57PM +1000, Martin Thomson wrote:<br>
&gt; There has been some opposition to the proposed resolution in PR 3870.=
=C2=A0 <br>
&gt; <br>
&gt; Apparently, for some, having multiple connection IDs in the same<br>
&gt; datagram complicates processing.=C2=A0 I don&#39;t understand this obj=
ection.<br>
&gt; It seems to me more difficult to retain state across packets than it<b=
r>
&gt; is to process each atomically.=C2=A0 I was hoping that Christian or Ni=
ck<br>
&gt; can explain more about how this affects them.<br>
<br>
I can provide an example from lsquic.=C2=A0 The datagram is parsed into<br>
QUIC packets in one function, lsquic_engine_packet_in():<br>
<br>
=C2=A0 <a href=3D"https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/=
liblsquic/lsquic_engine.c#L2781L2816" target=3D"_blank">
https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_e=
ngine.c#L2781L2816</a><br>
<br>
Each QUIC packet is processed by process_packet_in(), where a<br>
connection is looked up:<br>
<br>
=C2=A0 <a href=3D"https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/=
liblsquic/lsquic_engine.c#L1352L1360" target=3D"_blank">
https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_e=
ngine.c#L1352L1360</a><br>
<br>
The DCID check is performed lsquic_engine_packet_in(), before<br>
process_packet_in() is called:<br>
<br>
=C2=A0 <a href=3D"https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/=
liblsquic/lsquic_engine.c#L2793L2806" target=3D"_blank">
https://github.com/litespeedtech/lsquic/blob/v2.18.1/src/liblsquic/lsquic_e=
ngine.c#L2793L2806</a><br>
<br>
The DCID information is readily available in the datagram parsing<br>
loop, while connection information is not.<br>
<br>
For lsquic to support the proposed change, it would have to remember<br>
the current connection and then query it whether it is indeed the<br>
owner of the next DCID (A) or look up DCID in the global hash (B):<br>
<br>
=C2=A0 =C2=A0 conn =3D NULL;<br>
=C2=A0 =C2=A0 while (quic_packet =3D parse_udp(pointers)) {<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 dcid =3D parse(quic_packet);<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 if (conn)<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 {<br>
=C2=A0 #if VARIANT_A<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 if (!conn_owns_scid(conn, dcid))<=
br>
=C2=A0 #else<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 if (conn !=3D lookup_by_dcid(dcid=
))<br>
=C2=A0 #endif<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 continue;<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 }<br>
=C2=A0 =C2=A0 =C2=A0 =C2=A0 conn =3D process_packet(quic_packet);<br>
=C2=A0 =C2=A0 }<br>
<br>
Not that it could not be done, of course, but it is both extra work<br>
to modify lsquic and a more inefficient mechanism: what was a simple<br>
CID comparison is now a hash lookup.<br>
<br>
That&#39;s why I argued [1] for having solid rationale behind the change<br=
>
rather than a personal preference.<br>
<br>
=C2=A0 - Dmitri.<br>
<br>
1. <a href=3D"https://github.com/quicwg/base-drafts/issues/3800#issuecommen=
t-656851626" target=3D"_blank">
https://github.com/quicwg/base-drafts/issues/3800#issuecomment-656851626</a=
><u></u><u></u></p>
</blockquote>
</div>
</div>
</div>

</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature">Kazuho Oku</div></div>

--00000000000040d1e005aa895221--


From SRS0=yCwG=A3=felixguenther.info=mail@cdc02.comdc.de  Wed Jul 15 23:47:53 2020
Return-Path: <SRS0=yCwG=A3=felixguenther.info=mail@cdc02.comdc.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 1D41F3A0FB7 for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 23:47:53 -0700 (PDT)
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, HEADER_FROM_DIFFERENT_DOMAINS=0.001, NICE_REPLY_A=-0.001, 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 flQv56cmHock for <quic@ietfa.amsl.com>; Wed, 15 Jul 2020 23:47:51 -0700 (PDT)
Received: from cdc02.comdc.de (cdc02.comdc.de [136.243.4.87]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F4213A0FB6 for <quic@ietf.org>; Wed, 15 Jul 2020 23:47:50 -0700 (PDT)
Received: from cdc02.comdc.de (cdc02.comdc.de.local [127.0.0.1]) by cdc02.comdc.de (Postfix) with ESMTP id 09AEC4F2007D for <quic@ietf.org>; Thu, 16 Jul 2020 08:47:48 +0200 (CEST)
Received: from [192.168.178.33] (160.94.254.84.ftth.as8758.net [84.254.94.160]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: mail@felixguenther.info) by cdc02.comdc.de (Postfix) with ESMTPSA id 7F5824F20079 for <quic@ietf.org>; Thu, 16 Jul 2020 08:47:48 +0200 (CEST)
To: quic@ietf.org
References: <43bb1525-0afa-4c4e-a234-f6ccfacbdd29@www.fastmail.com> <a4d7e8cf-5879-6941-e059-5d2f3e67ae86@huitema.net> <58b40fc0-86ad-49e9-bc17-187c38e97f7a@www.fastmail.com> <1d543593-7abc-4a89-93c5-82c464492786@www.fastmail.com> <CACpbDccSB6H9AhmAinia7ojEg1VY-S=dF214wHvZcZkoiL-xFA@mail.gmail.com> <7d549475-249b-4674-9aa8-c2bf9953243b@www.fastmail.com> <CALGR9oaHQHJneN2edetGLcq4u4PNF0oAyq9PKc7ZVxz_pXTMGw@mail.gmail.com> <CACsn0c=HkByj0dkwfW+0=n9HzGZ0cZamot6N=AFks3wbnwnWXQ@mail.gmail.com> <19922b1a-a02c-46c9-b441-3806d3f77b89@www.fastmail.com>
From: =?UTF-8?Q?Felix_G=c3=bcnther?= <mail@felixguenther.info>
Autocrypt: addr=mail@felixguenther.info; keydata= mQGiBE04qkIRBADtFenVz1DuqethtPkoKAazBeKjyrr5Znbi8mQT1gOrkuli6i0/umf2uJ9V uI6NgjR0uM68UFGIHZlAoWk5Nfo8BTkYsdXl4R08pePmwRwwtq9LALZrGkeLeQtOFdLJt7G2 iQgqq2XpZc9AXW3/+j0I6MmsWMQKCkCA1s6IRLtH+wCgk85oP1adRYaEpi82Z3oG7vztEOkE AMccj8RgnjWcbB13HxxRk2C/4mgLEmCBWO3nmcCPZP5t/5GZSe7Kt5HQoygjxxcro/2e+9wF YsYwLUpHKMOjyvtcU0jLtIv0m6I+GQ3HOz89erVpa7G7EUoEsbQ7FEuyW4mVEaQZ3XE1Mxvp /3Ca1rBJjoxXhxKaDJYWsc5fdO6RA/44xXLdiE2f6NDoTJY7Z97VXUnJskpDNnwePOJyX4GT DwII2kl6JSYOAmkcOpINOSVsS0XDLZpBuKqsibUF/t53BkNfR/aF/BzIUJ5dykqrHvi75aQb ltSum1+kIo8Q6ZI+MzAAwmbqLfuRHZP5y0fjxdHLhfMrvacrNHnaoUWrVbQoRmVsaXggR8O8 bnRoZXIgPG1haWxAZmVsaXhndWVudGhlci5pbmZvPoh8BBMRAgA8AhsjBgsJCAcDAgYVCAIJ CgsEFgIDAQIeAQIXgBYhBCuuSm95RkYbcAFhs1KvAgDT8XAOBQJdE93OAhkBAAoJEFKvAgDT 8XAOVSwAn0QmRYzMtqFZejCnMakizqsaWHJlAJ4jR3nDqw5h3Ct4Xyz1CEQrUdJgz7kEDQRN OKpCEBAA9TNoDOa0PVCAWvt9tw06MUw+D0PoAhkl1jlNEzeNatLDQqf6YehHOgtjpgA8tpul DJUq/o3NN15JsUB1el6oQje644owqhEFD8V02Ns3ZK6hGgBRGupp6RKwg70F4z4ukKwCS789 rZdwaq8t+X37NRUP41Y537kgfN2R1BFLB0A19Qb52nsaneBUSgGLXu39bxDrHounoLjMitJa 10ATRcuRny8eJzAuXI8lCURNjCPWJVjXN3gs+z6sA/ebr2inLQT66WIQZi5Q31BNyPGeaai+ 7t7IbpfkhqnbHATDq6vtM8lCem+rsYc3MtN1W4jQZ59ACI3ieu3MouMoN4W5mp0bjB6oNiO1 TTYD3ZUYBeV7ITX47lag7A9MPzBwbRGdetAN1yU5HDv7mgadei/oFlwC4/hD18kYjuHEUxKi CookZZaPQEMTKjBpHhrphSslTXl/tWmMJBoVsgedghWyf39o8ZOTBsQQ1wHwhO9Dc+fwT/Q2 Bw6jdZSzwQVJG13hg/uC6HqxhYfiKHtsiMuqnb5OIM0qkWa3Q/XtRclokk8elTjHYIIM+HBd i2xjys8D+1gVPI8s4NwPRAjc5m/kAXyzbrbg+p+ZVe3IJTE4M/heShLzsoFrZoroE2T38rvT Wsido/8zJZCxJ+JLAR8p8BYKYBJel/pHsvRFwSYbOEMAAwYP/j905vAZ/MJlLrElQ6eVwU2X IBhFmsOtQcVmh3CZw0QuXMA1AQsQe3KLLJSfBEP8Ljz8/Y9mPNu8wmvhw04Px0o7Ns6yOEuv v4CyQzaZwJGvn0lI4UajS7y4mgGFkd1AmPi1/4el9Yp4my88VlOcSe/macm4+MCIAMDegNLx JzErZgOMQJVdSz4rVYaWToTE/DVvRFkuEZgZNnvIv8G46OCZtnnRFv1XQDouxap2tO8yGBQ+ BxBZXqrXtyeVz1weOBIVHycUxi9kGRQ5M99NfrZuInR1382W9YYhqiVgvmvWEsLZFRoGrh8w 1yVkyxw6IGikWlkwq8TLGVlAiqA8AENZZ9bJJVOn57ld6Dvz8c8UvHpvSpUbt3Y3jf0GJbDn lj4v3ZrIxcI3RmUIGf0CQDSpqrUHppgKwiBPSLLRRQruGw7jzLpMqu7ar+2fhNQB3GLSmygi kdYXROfmIIq0J5g/rZLSFQ1GZmL3S8pqS9sJQh0KZEUE+1PtzAoYUYp9btR5Jo3pbyAn6M/g SNlSNDUwa2Eai6fy3fBu1KT1AYgntLzVyJr2Q/Wd85MjF/a9GI5X8lmnvPSAJ/ofSI/bRjLq yNj6frKLrztFV9ucWhKQoQd4iE9qe284KYqdQq4BZUhO4J2nl2rWbEquoFe9ACdIVBIuRoCH EUrreMG0tdymiEkEGBECAAkFAk04qkICGwwACgkQUq8CANPxcA6jYACfYd8EkV8G70iuPkyA HMZZ8W8lWUoAoJElB4EzU8opYiwQw02HRvW/qYuJ
Subject: Re: New confidentiality and integrity limits
Message-ID: <02f5d291-4b95-7f94-5028-c90f94bd5908@felixguenther.info>
Date: Thu, 16 Jul 2020 08:47:48 +0200
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <19922b1a-a02c-46c9-b441-3806d3f77b89@www.fastmail.com>
Content-Type: text/plain; charset=utf-8
Content-Language: en-US
Content-Transfer-Encoding: 8bit
X-Virus-Scanned: ClamAV using ClamSMTP
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7fGMofxBJSttHpx1XNSqsksqm5Q>
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, 16 Jul 2020 06:49:02 -0000

Hi Watson,

Let me clarify that the multi-user setting does not mean that a forgery
attempt is made against all keys simultaneously -- this model still
counts "try to decrypt 1 ciphertext under 1 key" as 1 forgery attempt.
The important difference is that, for each attempt, you may try a
different key.

While the model is somewhat more general in allowing to go back and
forth between all keys, this of course also captures the QUIC setting
where only few keys are active at any point in time, and are phased
in/out sequentially. I am not aware of an intermediate model, but I
don't think the difference would be huge, plus I strongly agree with
Martin that this conservative over-approximation doesn't hurt much here.

So, the multi-user model is the closest analysis we have to answer the
question:  "What's the advantage of an adversary that tries to inject a
forgery *at some point* in a QUIC connection."
Single-user models cannot answer this question, as they only speak to
forgery attempts under one fixed key, hence don't capture key updates.

I hope this clarifies the need for multi-user bounds.

Cheers,
Felix


On 2020-07-16 06:58 +0200, Martin Thomson <mt@lowentropy.net> wrote:
> On Thu, Jul 16, 2020, at 11:40, Watson Ladd wrote:
>> I do not believe the analysis is correct.
>>
>> A forgery against a QUIC connection will be checked at one or at most
>> two keys: the current one and the next one. It is not the case that a
>> forgery will be attempted against all the keys simultaneously: it will
>> have to be resent. Perhap I'm missing something about the setting here
>> that makes this the multiuser and not the singleuser setting.
> 
> Thanks for checking Watson.
> 
> I had exactly the same thought, but was convinced by Felix that the analysis was based on a definition that only considers the number of encryption/verification queries in total. In particular, that the values in results are not limited in any way by which subset of the keys could be tried.
> 
> Incidentally, that also supports the view that there is degradation in the confidentiality advantage as you update to different keys.  I note that the PR does not acknowledge this, but maybe it should.
> 
> I confess that I'm still not completely confident that the multiuser setting is a good fit for our needs (or even that the threat model is the right one).  This is, in part of the reason you state: the mu setting assumes that the attacker has equal access to all "users" concurrently and the limited number of active keys would seem to make that difficult to exploit.  But I don't know how to prove that this is an acceptable assumption.
> 
> What I am confident about is that a conservative approach doesn't hurt a great deal here.  The calculated limits for GCM are high enough - even under the assumptions made - that you have serious problems if you hit them.
> 


From nobody Thu Jul 16 12:22:40 2020
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 DA0753A0B32 for <quic@ietfa.amsl.com>; Thu, 16 Jul 2020 12:22:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level: 
X-Spam-Status: No, score=-17.599 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, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, 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 P_qHtH9G4Nuw for <quic@ietfa.amsl.com>; Thu, 16 Jul 2020 12:22:37 -0700 (PDT)
Received: from mail-yb1-xb36.google.com (mail-yb1-xb36.google.com [IPv6:2607:f8b0:4864:20::b36]) (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 A422E3A0B2E for <quic@ietf.org>; Thu, 16 Jul 2020 12:22:37 -0700 (PDT)
Received: by mail-yb1-xb36.google.com with SMTP id x9so3371485ybd.4 for <quic@ietf.org>; Thu, 16 Jul 2020 12:22:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YCtU0yNW8buiuKB6C6v90BVdp9oIda1SQsGgAV1jbrI=; b=kQhLYbQ4MH9FwE9uF1lCmbyMbjn4zivZncbxh7wtuUZA3xcO57bk6/giDJOrTcEQq6 Tk1DQj0Q3L4HZ2l3zubRXGcwh3YcLbWtAtqtuNVuztPE8IcDxwwMuhEGzATqNbuiFiw/ bR+gs+Hp1mZHAgb/dW4n+2uq0CsGBBZrAhhQ8uLGCAVt1bXXApycNLigHKyJYkYZHh5f MwIuqCtohO5GQ7a9yUiura+slLk0Fxwj+fMGRdLWmG8eMbGYPA1UWPOF1zv+zE6b+ARL HfBTK8+Tpc4BROD/1l0+zVZX9JzjHH7lqRt5HShpXpnaxcrU8MfU6aN65W2C7coRgnh0 KQOg==
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=YCtU0yNW8buiuKB6C6v90BVdp9oIda1SQsGgAV1jbrI=; b=kRCX9bn1/9a9DvmcZ1K+DluzOnhtwBv0CG6Fg0TXL3aXKbgld1Nvw/GEx6vDuGgVwr BHLerD73DrU/WRCo7zhRxsQQ41Kqrfn5wcWgvNVfVfYm3E0fBQ6g+xQeqxBjFadL1qT2 LoQxvIyIeo1HU8ih6lY2RN/fFUpCw9ep0v6GDncbi8FCiiem7je5Abi+vRFkhwLjVwY4 l2Ye1rGZHAyMrLkjJ3OohZbVAu8792PIe2UukQzNd7HTgByO3ulKz1jA+sYLRsbtq6nv VFoUYP8By0JHMCm3LcmgvSwH6RXNCwFs7Rp0IKpUg8KsXSfnTi5Y0tOWTa8hrx0wRHge 9mJQ==
X-Gm-Message-State: AOAM533LPtCRDAdRSf29xMBT99if1WPb9iAF8246UqSqWiBrQb681C1k Hcu2glvVqskdyZpIBd3IMj1gYUqHrRiahHNnKq0q7V7U1GE=
X-Google-Smtp-Source: ABdhPJxq12F82BpEK1XGyWkCMSVMYexoTIBMcBSGozAgwUnlZi5gDVPk3TT3EeazkwYVScK0AHnJwjc9fMx8dcQQ6jY=
X-Received: by 2002:a25:b78a:: with SMTP id n10mr8490826ybh.494.1594927356672;  Thu, 16 Jul 2020 12:22:36 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <53187d65-f7b9-b99a-f68b-b267303ab399@erg.abdn.ac.uk> <CH2PR00MB0726D18611EC030BF548CA0DB6640@CH2PR00MB0726.namprd00.prod.outlook.com> <40818629-e1dc-f0f1-6173-984a8166c7c2@erg.abdn.ac.uk> <CH2PR00MB07267EBAC2BB08CCE5160EC6B6650@CH2PR00MB0726.namprd00.prod.outlook.com>
In-Reply-To: <CH2PR00MB07267EBAC2BB08CCE5160EC6B6650@CH2PR00MB0726.namprd00.prod.outlook.com>
From: Ian Swett <ianswett@google.com>
Date: Thu, 16 Jul 2020 15:22:24 -0400
Message-ID: <CAKcm_gN=vizG9+kiRiX7BAfcsR1p+Q1FrTtNPXfV5vFATBNQ9Q@mail.gmail.com>
Subject: Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
To: Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, IETF QUIC WG <quic@ietf.org>,  Neal Cardwell <ncardwell@google.com>, Yuchung Cheng <ycheng@google.com>
Content-Type: multipart/alternative; boundary="00000000000089f3ce05aa93f6dd"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/PvzXYkmtyYTjso7M_zJV7y_BDTc>
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, 16 Jul 2020 19:22:40 -0000

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

Thanks for the comments, I filed #3918
<https://github.com/quicwg/base-drafts/issues/3918> and #3919
<https://github.com/quicwg/base-drafts/issues/3919>

For my background, are you aware other transport RFCs have normative
statements that only apply to the public internet?  Also, if you're that
well buffered and the bursts are that large, do you still start with IW10,
or do you start with a larger window?

Thanks, Ian

On Fri, Jul 10, 2020 at 1:11 PM Praveen Balasubramanian <pravb=
40microsoft.com@dmarc.ietf.org> wrote:

> Precluding bursts higher than 10 packets is simply not viable or practical
> at really high data dates and is a major regression from the way TCP works
> today. QUIC is a general purpose transport and not scoped to the Internet
> only. On a side thread around Linux TCP behavior Neal suggested some
> alternate text to scope this to Internet facing traffic but my contention
> still holds that there are many networks where higher bursts are not a
> problem and we should not restrict those use cases.
>
>
>
> *From:* Gorry Fairhurst <gorry@erg.abdn.ac.uk>
> *Sent:* Friday, July 10, 2020 1:21 AM
> *To:* Praveen Balasubramanian <pravb@microsoft.com>; IETF QUIC WG <
> quic@ietf.org>
> *Subject:* Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
>
>
>
> Thanks Praveen,
>
> I'd like to talk more, see below:
>
> On 09/07/2020 17:11, Praveen Balasubramanian wrote:
>
> Within data center mainly. To hit 40 Gbps line rate you effectively have
> to batch as much as you can to minimize the CPU processing costs. The burst
> size today is capped to 64k in most cases for TCP. Now that we have
> segmentation offload for UDP the same should apply. Even for Internet
> facing traffic, the bursts primarily impact the first hop within the
> datacenter because subsequently you get statistical multiplexing from ToR
> switch handling traffic forwarding for many flows and ports.
>
>
>
> I get this for this use-case and comments on high-speed NICs. I agree
> offload is important.
>
> Ok understood about there being no conflict. But I still contend that the
> MUST regarding burst size is way too restrictive. We should allow for
> experimentation here.
>
> I am not sure. The IW spec for TCP was based on evidence back around 2010,
> and the IETF agreed in RFC6928 that a burst size of 10 was acceptable as an
> EXP spec for TCP.
>
> I think we can safely refer to that - even perhaps take the leap-of-faith
> that EXP for TCP is equivalent to PS for QUIC, given subsequent
> experience.  I think the IW  **is** the burst size that the IETF should
> specify (because it's dictated by buffering that is expected on the path).
>
> I see opportunities here for experimentation and measurement
> opportunities, and new specs can be proposed. Or the Specs can be recast
> with more detail. I also know that practical experience is that many people
> have configured (probably tested, I hope) much larger IW's - and I'd hope
> they also make a reasonable effort to monitor for possible interactions
> with other Internet applications and services (as per section 12 of
> RFC6928).
>
> Or present data that this is universally bad on all networks.
>
> I think you touch on something that the IETF hasn't been great at talking
> about:
>
> I could myself indeed likely produce data this shows this is "bad" in some
> networks that I value, and also show side-effects of collateral damage to
> other flows and adverse effects of line-rate bursts into equipment with
> small buffers. I don't know how useful that would be at all.
>
> The IETF has typically defined a spec for endpoint. The way a modern
> endpoint is implemented can be quite different in a DC from a single device
> connected to the Internet. In a DC, I understand it is common  to
> distribute transport functions to other parts of the network. e.g.: DDOS
> protection could be done on a server; or by a box in front of it -
> similarly what matters to the network CC is the  bursts of traffic that
> leaves a DC within a flow to a local receiver, not what leaves a particular
> server within the DC network - I think in future we may do well to consider
> these differences?
>
> Current production use of TCP shows there is no major problems with
> bursting higher. In fact for low latency same rack scenarios this will
> boost receive performance as well due to better opportunity for LRO etc.
>
> It's also possible that QUIC LRO (or whatever) includes some notion of
> per-flow burst-mitigation. Is that impossible?
>
> However, I personally would not hold-up QUIC, to arrive at a new consensus.
>
> Gorry
>
>
>
> *From:* Gorry Fairhurst <gorry@erg.abdn.ac.uk> <gorry@erg.abdn.ac.uk>
> *Sent:* Thursday, July 9, 2020 1:39 AM
> *To:* Praveen Balasubramanian <pravb@microsoft.com> <pravb@microsoft.com>;
> IETF QUIC WG <quic@ietf.org> <quic@ietf.org>
> *Subject:* [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
>
>
>
> Hi Praveen,
>
> On 08/07/2020 22:29, Praveen Balasubramanian wrote:
>
> Section 7.9
>
> "Implementations MUST either use pacing or another method to limit such
> bursts to the initial congestion window; see Section 7.2."
>
> This seems to preclude use of segmentation offload of sizes greater than
> IW. In datacenters we routinely send bursts that are higher without causing
> loss.
>
> Is that within data centres? or from data centres to Internet
> destinations? ... if the latter, how can the sender be sure this is not
> impacting other traffic?
>
>
> The MUST here seems unnecessary. It also conflicts with the RECOMMENDED in
> an earlier sentence.
>
> I actually don't see this as conflicting. The recommendation in this
> section is to pace. The requirement is that sender limits burst, using some
> method, to the size of IW.
>
> Gorry
>
>
>
>

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

<div dir=3D"ltr">Thanks for the comments, I filed <a href=3D"https://github=
.com/quicwg/base-drafts/issues/3918">#3918</a> and <a href=3D"https://githu=
b.com/quicwg/base-drafts/issues/3919">#3919</a>=C2=A0<div><br></div><div>Fo=
r my background, are you=C2=A0aware other transport RFCs have normative sta=
tements that only apply to the public internet?=C2=A0 Also, if you&#39;re t=
hat well buffered and the bursts are that large, do you still start with IW=
10, or do you start with a larger window?</div><div><br></div><div>Thanks, =
Ian</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gma=
il_attr">On Fri, Jul 10, 2020 at 1:11 PM Praveen Balasubramanian &lt;pravb=
=3D<a href=3D"mailto:40microsoft.com@dmarc.ietf.org">40microsoft.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-le=
ft:1ex">





<div lang=3D"EN-US">
<div>
<p class=3D"MsoNormal">Precluding bursts higher than 10 packets is simply n=
ot viable or practical at really high data dates and is a major regression =
from the way TCP works today. QUIC is a general purpose transport and not s=
coped to the Internet only. On a side
 thread around Linux TCP behavior Neal suggested some alternate text to sco=
pe this to Internet facing traffic but my contention still holds that there=
 are many networks where higher bursts are not a problem and we should not =
restrict those use cases.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Gorry Fairhurst &lt;<a href=3D"mailto:g=
orry@erg.abdn.ac.uk" target=3D"_blank">gorry@erg.abdn.ac.uk</a>&gt; <br>
<b>Sent:</b> Friday, July 10, 2020 1:21 AM<br>
<b>To:</b> Praveen Balasubramanian &lt;<a href=3D"mailto:pravb@microsoft.co=
m" target=3D"_blank">pravb@microsoft.com</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: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-=
29<u></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p>Thanks Praveen, <u></u><u></u></p>
<p>I&#39;d like to talk more, see below:<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On 09/07/2020 17:11, Praveen Balasubramanian wrote:<=
u></u><u></u></p>
</div>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt">
<p class=3D"MsoNormal">Within data center mainly. To hit 40 Gbps line rate =
you effectively have to batch as much as you can to minimize the CPU proces=
sing costs. The burst size today is capped to 64k in most cases for TCP. No=
w that we have segmentation offload
 for UDP the same should apply. Even for Internet facing traffic, the burst=
s primarily impact the first hop within the datacenter because subsequently=
 you get statistical multiplexing from ToR switch handling traffic forwardi=
ng for many flows and ports.
<u></u><u></u></p>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
</blockquote>
<p>I get this for this use-case and comments on high-speed NICs. I agree of=
fload is important.<u></u><u></u></p>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt">
<p class=3D"MsoNormal">Ok understood about there being no conflict. But I s=
till contend that the MUST regarding burst size is way too restrictive. We =
should allow for experimentation here.
<u></u><u></u></p>
</blockquote>
<p>I am not sure. The IW spec for TCP was based on evidence back around 201=
0, and the IETF agreed in RFC6928 that a burst size of 10 was acceptable as=
 an EXP spec for TCP.
<u></u><u></u></p>
<p>I think we can safely refer to that - even perhaps take the leap-of-fait=
h that EXP for TCP is equivalent to PS for QUIC, given subsequent experienc=
e.=C2=A0 I think the IW=C2=A0 **is** the burst size that the IETF should sp=
ecify (because it&#39;s dictated by buffering
 that is expected on the path).<u></u><u></u></p>
<p>I see opportunities here for experimentation and measurement opportuniti=
es, and new specs can be proposed. Or the Specs can be recast with more det=
ail. I also know that practical experience is that many people have configu=
red (probably tested, I hope) much
 larger IW&#39;s - and I&#39;d hope they also make a reasonable effort to m=
onitor for possible interactions with other Internet applications and servi=
ces (as per section 12 of RFC6928).
<u></u><u></u></p>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt">
<p class=3D"MsoNormal">Or present data that this is universally bad on all =
networks.
<u></u><u></u></p>
</blockquote>
<p>I think you touch on something that the IETF hasn&#39;t been great at ta=
lking about:<u></u><u></u></p>
<p>I could myself indeed likely produce data this shows this is &quot;bad&q=
uot; in some networks that I value, and also show side-effects of collatera=
l damage to other flows and adverse effects of line-rate bursts into equipm=
ent with small buffers. I don&#39;t know how useful
 that would be at all.<u></u><u></u></p>
<p>The IETF has typically defined a spec for endpoint. The way a modern end=
point is implemented can be quite different in a DC from a single device co=
nnected to the Internet. In a DC, I understand it is common=C2=A0 to distri=
bute transport functions to other parts
 of the network. e.g.: DDOS protection could be done on a server; or by a b=
ox in front of it - similarly what matters to the network CC is the=C2=A0 b=
ursts of traffic that leaves a DC within a flow to a local receiver, not wh=
at leaves a particular server within
 the DC network - I think in future we may do well to consider these differ=
ences?<u></u><u></u></p>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt">
<p class=3D"MsoNormal">Current production use of TCP shows there is no majo=
r problems with bursting higher. In fact for low latency same rack scenario=
s this will boost receive performance as well due to better opportunity for=
 LRO etc.
<u></u><u></u></p>
</blockquote>
<p>It&#39;s also possible that QUIC LRO (or whatever) includes some notion =
of per-flow burst-mitigation. Is that impossible?<u></u><u></u></p>
<p>However, I personally would not hold-up QUIC, to arrive at a new consens=
us.<u></u><u></u></p>
<p>Gorry<u></u><u></u></p>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt">
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<div>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Gorry Fairhurst <a href=3D"mailto:gorry=
@erg.abdn.ac.uk" target=3D"_blank">
&lt;gorry@erg.abdn.ac.uk&gt;</a> <br>
<b>Sent:</b> Thursday, July 9, 2020 1:39 AM<br>
<b>To:</b> Praveen Balasubramanian <a href=3D"mailto:pravb@microsoft.com" t=
arget=3D"_blank">&lt;pravb@microsoft.com&gt;</a>; IETF QUIC WG
<a href=3D"mailto:quic@ietf.org" target=3D"_blank">&lt;quic@ietf.org&gt;</a=
><br>
<b>Subject:</b> [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29<u=
></u><u></u></p>
</div>
</div>
<p class=3D"MsoNormal">=C2=A0<u></u><u></u></p>
<p>Hi Praveen,<u></u><u></u></p>
<div>
<p class=3D"MsoNormal">On 08/07/2020 22:29, Praveen Balasubramanian wrote:<=
u></u><u></u></p>
</div>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt">
<p class=3D"MsoNormal">Section 7.9<u></u><u></u></p>
<p class=3D"MsoNormal">&quot;Implementations MUST either use pacing or anot=
her method to limit such bursts to the initial congestion window; see Secti=
on 7.2.&quot;
<u></u><u></u></p>
<p class=3D"MsoNormal">This seems to preclude use of segmentation offload o=
f sizes greater than IW. In datacenters we routinely send bursts that are h=
igher without causing loss.
<u></u><u></u></p>
</blockquote>
<p class=3D"MsoNormal">Is that within data centres? or from data centres to=
 Internet destinations? ... if the latter, how can the sender be sure this =
is not impacting other traffic?<br>
<br>
<br>
<u></u><u></u></p>
<blockquote style=3D"margin-top:5pt;margin-bottom:5pt">
<p class=3D"MsoNormal">The MUST here seems unnecessary. It also conflicts w=
ith the RECOMMENDED in an earlier sentence.<u></u><u></u></p>
</blockquote>
<p>I actually don&#39;t see this as conflicting. The recommendation in this=
 section is to pace. The requirement is that sender limits burst, using som=
e method, to the size of IW.<u></u><u></u></p>
<p>Gorry<u></u><u></u></p>
<p>=C2=A0<u></u><u></u></p>
</blockquote>
</div>
</div>

</blockquote></div>

--00000000000089f3ce05aa93f6dd--


From nobody Thu Jul 16 14:18:31 2020
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1CACF3A0D03 for <quic@ietfa.amsl.com>; Thu, 16 Jul 2020 14:18:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 dZa1OJ4-C71l for <quic@ietfa.amsl.com>; Thu, 16 Jul 2020 14:18:27 -0700 (PDT)
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 0E5123A0D01 for <quic@ietf.org>; Thu, 16 Jul 2020 14:18:27 -0700 (PDT)
Received: by mail-lj1-x230.google.com with SMTP id r19so9895143ljn.12 for <quic@ietf.org>; Thu, 16 Jul 2020 14:18:26 -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=zDXk9olW+CPcQ9FKW2bnLLQOh0PrB6/j7yWezODHtdU=; b=Z3ZkdP5JTqF6zh1vBlBrc3qAphz9Hc/KZwyEh3zTT7BDLTBMhl6tnZjbvZLgNBejUP azYaAVtyhIRugMCqOkP7+0xWT5xGD3g/xD3XXve6QIX5CrxQ07ojPe3q7eSQiShZ2x4d Iy087hWx+EKnbW6YzD/dNNJaXc6UWAvfGZ3n91ZEt9gI3bLY19GVxQsIWafGBqXv752m CgVZkR7GSrgEkeXq2q9KecZs2EjsDMhB3e7dtwq/Bo0vOydo9a77iGozbPsUMfua2O8y uQNG/Eyz4gUF/bGflbbMGQHvLOrBSfRs8BDipFaxhIQ5Ykymejq1VfYCZ3xsCbj2qmYM 9VWg==
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=zDXk9olW+CPcQ9FKW2bnLLQOh0PrB6/j7yWezODHtdU=; b=sHWoByJyeGD4nyqdPkoBUSGtwXya1/1vCx5cOhOpi4TCGsoDJc0kMy3eHFj9m8+6Bk 9Bq3zt9bB/dhQ3RreRs8mhkP/OxLOalJkp8LkEqK8mfq1xqWw8hp6HFLppALPOFFfcgA DBhmWVVIfHIqt5PvhxXmPhjIQoL4E4sLVFN6QOGDxGI5SW/UChoBtEllRf0P6P1yR0SF eYH9k+PpCfcODGVeaFlewE+CrL48Ke59tr4gz1e6KmxDsRf2rHmKD/UzgVf9Yqy9sSG7 d7y2Bh9Fsj39ARxsN8p2R+YYEx8jVa8qRo9s+x7nebyl1nnU2p8tKv2oEkmAbIimzu/f PVgA==
X-Gm-Message-State: AOAM530rUPeZwe1pg9J57OwAfmiB5pqwqF/b2V/EkZpodU33u+h6Tbdp afRZwEcNwyIwGCzmM0cqEx90aqBqqnLfdDmFuZ4=
X-Google-Smtp-Source: ABdhPJz/lwVUNu8gORBih+LxBIHibr23Ie7KUNWO/X2hxwrnmxYjbPW1TluckZipdyJzvCZDP9EYw34Y8IBYHUVKUxU=
X-Received: by 2002:a2e:9b42:: with SMTP id o2mr2814952ljj.102.1594934305192;  Thu, 16 Jul 2020 14:18:25 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <53187d65-f7b9-b99a-f68b-b267303ab399@erg.abdn.ac.uk> <CH2PR00MB0726D18611EC030BF548CA0DB6640@CH2PR00MB0726.namprd00.prod.outlook.com> <40818629-e1dc-f0f1-6173-984a8166c7c2@erg.abdn.ac.uk> <CH2PR00MB07267EBAC2BB08CCE5160EC6B6650@CH2PR00MB0726.namprd00.prod.outlook.com> <CAKcm_gN=vizG9+kiRiX7BAfcsR1p+Q1FrTtNPXfV5vFATBNQ9Q@mail.gmail.com>
In-Reply-To: <CAKcm_gN=vizG9+kiRiX7BAfcsR1p+Q1FrTtNPXfV5vFATBNQ9Q@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Thu, 16 Jul 2020 16:17:58 -0500
Message-ID: <CAKKJt-c-sp=L7j5--aoEEObMjhcnTE7YVK_NE4YQFGZDtcLhrA@mail.gmail.com>
Subject: Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Cc: Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>,  Gorry Fairhurst <gorry@erg.abdn.ac.uk>, IETF QUIC WG <quic@ietf.org>,  Neal Cardwell <ncardwell@google.com>, Yuchung Cheng <ycheng@google.com>
Content-Type: multipart/alternative; boundary="000000000000b37fb205aa95942a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/-8LczUutQVDGPakFr4Ks_W12YnM>
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, 16 Jul 2020 21:18:29 -0000

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

Hi, Ian,

On Thu, Jul 16, 2020 at 2:22 PM Ian Swett <ianswett=
40google.com@dmarc.ietf.org> wrote:

> Thanks for the comments, I filed #3918
> <https://github..com/quicwg/base-drafts/issues/3918> and #3919
> <https://github.com/quicwg/base-drafts/issues/3919>
>
> For my background, are you aware other transport RFCs have normative
> statements that only apply to the public internet?
>

Tunnels are transport, right? :-)

The earliest RFC I was involved with, that made distinctions about what you
can get away with on the public internet versus in a managed network, was
https://tools.ietf.org/html/rfc7510#section-5. This was negotiated after a
fairly vigorous back-and-forth between transport people and non-transport
people during IETF Last Call.

We put together a design team with a few people to try to work through this
for the myriad other protocols that people wanted to tunnel over UDP, once
and for all.

https://tools.ietf.org/html/rfc8084 was published as a BCP.

I may be forgetting other stuff, of course.

Best,

Spencer


> Also, if you're that well buffered and the bursts are that large, do you
> still start with IW10, or do you start with a larger window?
>
> Thanks, Ian
>
>>

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

<div dir=3D"ltr"><div dir=3D"ltr">Hi, Ian,=C2=A0</div><br><div class=3D"gma=
il_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jul 16, 2020 at 2:2=
2 PM Ian Swett &lt;ianswett=3D<a href=3D"mailto:40google.com@dmarc.ietf.org=
">40google.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(20=
4,204,204);padding-left:1ex"><div dir=3D"ltr">Thanks for the comments, I fi=
led <a href=3D"https://github..com/quicwg/base-drafts/issues/3918" target=
=3D"_blank">#3918</a> and <a href=3D"https://github.com/quicwg/base-drafts/=
issues/3919" target=3D"_blank">#3919</a>=C2=A0<div><br></div><div>For my ba=
ckground, are you=C2=A0aware other transport RFCs have normative statements=
 that only apply to the public internet?=C2=A0 </div></div></blockquote><di=
v><br></div><div>Tunnels are transport, right? :-)</div><div><br></div><div=
>The earliest RFC I was involved with, that made distinctions about what yo=
u can get away with on the public internet versus in a managed network, was=
=C2=A0<a href=3D"https://tools.ietf.org/html/rfc7510#section-5">https://too=
ls.ietf.org/html/rfc7510#section-5</a>. This was negotiated after a fairly =
vigorous back-and-forth between transport people and non-transport people d=
uring IETF Last Call.=C2=A0</div><div><br></div><div>We put together a desi=
gn team with a few people to try to work through this for the myriad other =
protocols that people wanted to tunnel over UDP, once and for all.=C2=A0</d=
iv><div><br></div><div><a href=3D"https://tools.ietf.org/html/rfc8084">http=
s://tools.ietf.org/html/rfc8084</a> was published as a BCP.=C2=A0<br></div>=
<div><br></div><div>I may be forgetting other stuff, of course.</div><div><=
br></div><div>Best,</div><div><br></div><div>Spencer</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 dir=3D"ltr"><div>Als=
o, if you&#39;re that well buffered and the bursts are that large, do you s=
till start with IW10, or do you start with a larger window?</div><div><br><=
/div><div>Thanks, Ian<br></div></div><div class=3D"gmail_quote"><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"><div lang=3D"EN-US"><div><blockquote=
 style=3D"margin-top:5pt;margin-bottom:5pt">
</blockquote>
</div>
</div>

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

--000000000000b37fb205aa95942a--


From nobody Thu Jul 16 18:30:26 2020
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 339EE3A0EC3 for <quic@ietfa.amsl.com>; Thu, 16 Jul 2020 18:30:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 x9ZgRGzZEh4D for <quic@ietfa.amsl.com>; Thu, 16 Jul 2020 18:30:23 -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 80B953A0EC0 for <quic@ietf.org>; Thu, 16 Jul 2020 18:30:23 -0700 (PDT)
Received: by mail-lj1-x232.google.com with SMTP id j11so10685536ljo.7 for <quic@ietf.org>; Thu, 16 Jul 2020 18:30:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YodH6kbkJcypurgBi5jgL00+o4CfYMSJThy6WfeFmx4=; b=sY4vzsIdaosDrx2Wh+eYglPIqkrruc8rMR7GPnzE0chiGIwf0kKNt1gVi2tQnPXhtd 7v1oRTdNL4K5CZsXt3GI58eM3pndPqZdi9RdHy+3+UdFScgnaxAKIixCjIzn4fFZoedn DhMktEVZ1IzrgU0jgVLxgo0jtFOb93iiUQxy7m3xjTD+TUWJqe5q6q6jBM6cvmZwYMYr 5VfT/CO2XwAdljL3nbbM8n8C2Su2nsr0tAEM6RKN0EGEfuKEOktG1+FN9nQn9FA+CNx8 k+DGyq2n/Gu3o0acdh+2bwtvpcPKcRK+a6E1aq8Y2q/kNvfkdpEW1kWaM3X3p4zhHYxW 51AA==
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=YodH6kbkJcypurgBi5jgL00+o4CfYMSJThy6WfeFmx4=; b=sp8URweef6W6BywX77SkokopCfguWt9M4no4AVB+QiW/6ujqJIhm6WWFoFhbpFh/We c0qJe0bc3Z/pXm7hj9TPf1/pR/5KKduJLll24puxQldY8EjuRG/SjcN3yR/qfH3GWOi3 17f83+CthSmBPa8Endzr7xsmgw72g2jj3ZsBBjukKHIlagF4JO8EbLhEPm9dxtcliqak yU04ppuzxy3NVguOdAtjZNRis3NcJ/V8BaiGRlaJj5qFOxPsz9JCt3rQq1ShgdbxvZxv m+tlifGyeigUq/K+tXStVI1TfUiEZJF5inqV3BhGvYXh5d5DFBOSL6nvzUpVywB3bDrj H3xA==
X-Gm-Message-State: AOAM532g7Cs3FXwlbtQXojwIKLbgPeq/qWilS/3CvvrLyDqdTKuS5+LA CSvh4gDdRyIpYUFl3yHovfBb02VIi105zUuZSaM=
X-Google-Smtp-Source: ABdhPJz3mMOY+HMgleM2WZrtMC+Mm361e2e1xf2tZOlTO1ftXCGjz8rwVcoy5cDuO5NEVi4fkkASyIBmwgsarW5IEDI=
X-Received: by 2002:a2e:80cc:: with SMTP id r12mr3654946ljg.344.1594949421433;  Thu, 16 Jul 2020 18:30:21 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <53187d65-f7b9-b99a-f68b-b267303ab399@erg.abdn.ac.uk> <CH2PR00MB0726D18611EC030BF548CA0DB6640@CH2PR00MB0726.namprd00.prod.outlook.com> <40818629-e1dc-f0f1-6173-984a8166c7c2@erg.abdn.ac.uk> <CH2PR00MB07267EBAC2BB08CCE5160EC6B6650@CH2PR00MB0726.namprd00.prod.outlook.com> <CAKcm_gN=vizG9+kiRiX7BAfcsR1p+Q1FrTtNPXfV5vFATBNQ9Q@mail.gmail.com> <CAKKJt-c-sp=L7j5--aoEEObMjhcnTE7YVK_NE4YQFGZDtcLhrA@mail.gmail.com>
In-Reply-To: <CAKKJt-c-sp=L7j5--aoEEObMjhcnTE7YVK_NE4YQFGZDtcLhrA@mail.gmail.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Thu, 16 Jul 2020 18:30:10 -0700
Message-ID: <CACpbDcfrVNtDb3htqnkVqr2OOskUVr_aYTrRvssT_tAgTKqV_g@mail.gmail.com>
Subject: Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>,  Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>,  Gorry Fairhurst <gorry@erg.abdn.ac.uk>, IETF QUIC WG <quic@ietf.org>,  Neal Cardwell <ncardwell@google.com>, Yuchung Cheng <ycheng@google.com>
Content-Type: multipart/alternative; boundary="000000000000b3073805aa99190e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/fkfZsbWnEj6RW13JwjeRo3gUJ5o>
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, 17 Jul 2020 01:30:25 -0000

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

At a high level, the recovery doc is _not_ written with DC environments in
mind. We can make that clear in the document, if that helps. There are
other things as well that won't work well in a DC environment, and I
imagine a separate doc would be helpful here that specifies how QUIC ought
to be tuned for DCs.

On Thu, Jul 16, 2020 at 2:18 PM Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> wrote:

> Hi, Ian,
>
> On Thu, Jul 16, 2020 at 2:22 PM Ian Swett <ianswett=
> 40google.com@dmarc.ietf.org> wrote:
>
>> Thanks for the comments, I filed #3918
>> <https://github..com/quicwg/base-drafts/issues/3918> and #3919
>> <https://github.com/quicwg/base-drafts/issues/3919>
>>
>> For my background, are you aware other transport RFCs have normative
>> statements that only apply to the public internet?
>>
>
> Tunnels are transport, right? :-)
>
> The earliest RFC I was involved with, that made distinctions about what
> you can get away with on the public internet versus in a managed network,
> was https://tools.ietf.org/html/rfc7510#section-5. This was negotiated
> after a fairly vigorous back-and-forth between transport people and
> non-transport people during IETF Last Call.
>
> We put together a design team with a few people to try to work through
> this for the myriad other protocols that people wanted to tunnel over UDP,
> once and for all.
>
> https://tools.ietf.org/html/rfc8084 was published as a BCP.
>
> I may be forgetting other stuff, of course.
>
> Best,
>
> Spencer
>
>
>> Also, if you're that well buffered and the bursts are that large, do you
>> still start with IW10, or do you start with a larger window?
>>
>> Thanks, Ian
>>
>>>

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

<div dir=3D"ltr">At a high level, the recovery doc is _not_ written with DC=
 environments in mind. We can make that clear in the document, if that help=
s. There are other things as well that won&#39;t work well in a DC environm=
ent, and I imagine a separate doc would be helpful here that specifies how =
QUIC ought to be tuned for DCs.</div><br><div class=3D"gmail_quote"><div di=
r=3D"ltr" class=3D"gmail_attr">On Thu, Jul 16, 2020 at 2:18 PM Spencer Dawk=
ins at IETF &lt;<a href=3D"mailto:spencerdawkins.ietf@gmail.com">spencerdaw=
kins.ietf@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><div dir=3D"ltr"><div dir=3D"ltr">Hi, Ian,=C2=A0</div><b=
r><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, =
Jul 16, 2020 at 2:22 PM Ian Swett &lt;ianswett=3D<a href=3D"mailto:40google=
.com@dmarc.ietf.org" target=3D"_blank">40google.com@dmarc.ietf.org</a>&gt; =
wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=
=3D"ltr">Thanks for the comments, I filed <a href=3D"https://github..com/qu=
icwg/base-drafts/issues/3918" target=3D"_blank">#3918</a> and <a href=3D"ht=
tps://github.com/quicwg/base-drafts/issues/3919" target=3D"_blank">#3919</a=
>=C2=A0<div><br></div><div>For my background, are you=C2=A0aware other tran=
sport RFCs have normative statements that only apply to the public internet=
?=C2=A0 </div></div></blockquote><div><br></div><div>Tunnels are transport,=
 right? :-)</div><div><br></div><div>The earliest RFC I was involved with, =
that made distinctions about what you can get away with on the public inter=
net versus in a managed network, was=C2=A0<a href=3D"https://tools.ietf.org=
/html/rfc7510#section-5" target=3D"_blank">https://tools.ietf.org/html/rfc7=
510#section-5</a>. This was negotiated after a fairly vigorous back-and-for=
th between transport people and non-transport people during IETF Last Call.=
=C2=A0</div><div><br></div><div>We put together a design team with a few pe=
ople to try to work through this for the myriad other protocols that people=
 wanted to tunnel over UDP, once and for all.=C2=A0</div><div><br></div><di=
v><a href=3D"https://tools.ietf.org/html/rfc8084" target=3D"_blank">https:/=
/tools.ietf.org/html/rfc8084</a> was published as a BCP.=C2=A0<br></div><di=
v><br></div><div>I may be forgetting other stuff, of course.</div><div><br>=
</div><div>Best,</div><div><br></div><div>Spencer</div><div>=C2=A0</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"><div dir=3D"ltr"><div>Also, =
if you&#39;re that well buffered and the bursts are that large, do you stil=
l start with IW10, or do you start with a larger window?</div><div><br></di=
v><div>Thanks, Ian<br></div></div><div class=3D"gmail_quote"><blockquote cl=
ass=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><blockquote st=
yle=3D"margin-top:5pt;margin-bottom:5pt">
</blockquote>
</div>
</div>

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

--000000000000b3073805aa99190e--


From nobody Fri Jul 17 02:01:07 2020
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 DBE3B3A1594 for <quic@ietfa.amsl.com>; Fri, 17 Jul 2020 02:01:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.913
X-Spam-Level: **
X-Spam-Status: No, score=2.913 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, GB_SUMOF=5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_KAM_HTML_FONT_INVALID=0.01, 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 yO9cZZ9Vcdxn for <quic@ietfa.amsl.com>; Fri, 17 Jul 2020 02:01:05 -0700 (PDT)
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 A54BB3A1593 for <quic@ietf.org>; Fri, 17 Jul 2020 02:01:04 -0700 (PDT)
Received: by mail-lj1-x229.google.com with SMTP id s9so11727342ljm.11 for <quic@ietf.org>; Fri, 17 Jul 2020 02:01:04 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=8xNWMPLV10wRS9XhdvMEUyRoXO1TBg/eoQMlvyJfRF4=; b=IvN91ZzEn+MYx4KpmduhpY7jedNKxbTrPprDVfLIpf381LpdZ+WP35QssIptTMd2T/ 0XQXcHdDXr0yr7UxIKHTwKejjMIqAxlygnzzTvdDYUc5oykcHmH5gSRiwjVr18bLmWYL S558wqDX5iG0sRGqv2LDJ+fh/7j9VA76XJQiUHewxNp00YF0d08Ko9W/d6dGGVXtUX7f yaIEDAyePaHR4YJ16pXKWV5llIjPiRuA0HhEMr5O68z/H7l348Te4wiuLwrdhjm68xu5 PNHzPTGJjLItaJqPEuSVfe72zGmHp66hGA0Pehwb5HT0T7fv+Ul9B9LeQCsWp8SX4bmC EQ5w==
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=8xNWMPLV10wRS9XhdvMEUyRoXO1TBg/eoQMlvyJfRF4=; b=X+WfKi16J7BaidIHj+ykIa4aWA9G9ev88wVn5FKXnhIrVZsOzn1U9CtbRPc7aRxPdp G6Qv2qH+pXuToKd1WcKRf0x8tSEa9QAOj5k3hIFmR12ccR3H4OUzKYknQlP+yusXVxh1 WnF2a8JAMRq6qrD2bCw755qTwyT1IcgCZDSBZeXQcpFO6d6cFt9UbhRZ7YQ5aUWabD+m s1ItAfKHyJqYXJM02zxYFz0FN8M/cafSzPKP6sH+AJU/302TOBAYQb3dN2gK7yqE6bLN M8adXzsdvJSkNVpqowontoxLeyB0OFj0UozwVejvjkbRruio7MTGMpZMg4s8ZEvA7Fwz 0bEg==
X-Gm-Message-State: AOAM530ozq1XzQGJDYmWIqXAAd4Lpj5Z4+6hPGG75WepeqJ+oPqHXU0R Uhged0TiyDIJDgFD+N2j6yC7Cga8tt3JyzoEMnXFxeLk
X-Google-Smtp-Source: ABdhPJx17A8f1lrSuUqeULsgBTbtGfMkUj7mlwlS3dc0UkgxJL/J5WspBIdbN5ukRsT5T2KkkkI1+1BpCt6e+BA30Pc=
X-Received: by 2002:a2e:8056:: with SMTP id p22mr4065812ljg.397.1594976462127;  Fri, 17 Jul 2020 02:01:02 -0700 (PDT)
MIME-Version: 1.0
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Fri, 17 Jul 2020 02:00:51 -0700
Message-ID: <CACpbDcctB0nX2yTxHQEs6UcUCTH0WdfiNAPfpRKe3oH-0aYZYA@mail.gmail.com>
Subject: Handshake processing delays and impact on recovery
To: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000073474f05aa9f65ed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/KBxSt7rv2PIs6RyumXwRJ0KUK6Q>
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, 17 Jul 2020 09:01:07 -0000

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

I'd like to bring this slightly tricky issue under the wg's eyes.
Discussions so far have yielded a strategy that I propose further below.
This summarizes conversations in 3821
<https://github.com/quicwg/base-drafts/issues/3821> and 3874
<https://github.com/quicwg/base-drafts/pull/3874> (and the outcomes might
touch 3889 <https://github.com/quicwg/base-drafts/issues/3889>). The
purpose of this email is to see if we can agree on the strategies outlined
here, so we can move forward on the PR there and/or other associated issues
and PRs.

Problems:

During the handshake, an endpoint can receive packets (carrying data or
acknowledgements) that it cannot decrypt because the requisite keys are not
yet available. This can happen because the crypto machinery at the endpoint
is waiting for earlier packets to be received to yield the keys. Similarly,
a client might not be able to read 1-RTT packets received from the server
because it is waiting for certificate validation to complete.

1.

The assumption in the TLS specification is that when an endpoint is busy
doing something (certificate validation or key generation for instance), it
won't be able to respond to received packets with acknowledgements (Section
4.1.4
<https://quicwg.org/base-drafts/draft-ietf-quic-tls.html#section-4.1.4-1>).

Contrary to the assumption in the spec, Chrome and Firefox both process the
certificate chain asynchronously, and therefore acks handshake packets
immediately, even the ones that arrive after they have started verifying
the certificate chain. But they buffer 1-RTT packets, and therefore the
issue exists for 1-RTT packets.

As a result, there's potential delay, sometimes significant, in responding
to some packets during the handshake. There are two side effects of this.

S1.

First, this means that an endpoint that runs a PTO timer and retransmits
data for 0-RTT and 1-RTT packets while the handshake is still in progress
might be doing this quite unnecessarily. The peer may well have received
this data and have queued it, waiting to be able to decrypt it.

S2.

Second, acks for these packets that are buffered and then later decrypted
and read can be sent much later than when the packets were received at the
peer, causing the ack_delay to potentially be much higher than the
advertised max_ack_delay. The endpoint ignores ack_delay larger than
max_ack_delay, and this inflates the smoothed_rtt and rtt_variance,
potentially inflating the PTO significantly (which can cause handshakes to
fail if the endpoint employs a "handshake timeout" period).


Proposed Solutions:

S1.

To solve the first problem, we already have a condition in the recovery
draft to _not_ arm the PTO on 1-RTT data until the handshake is
complete (Section
6.2.1
<https://quicwg.org/base-drafts/draft-ietf-quic-recovery.html#section-6.2.1-6>).
This is not quite adequate, since it still allows a client to arm a PTO
timer on 1-RTT data on sending a CFIN and 1-RTT data, before ensuring that
the server has received the CFIN. The proposed solution here is to change
this condition from "handshake complete" to "handshake confirmed". Meaning
that an endpoint only arms a PTO timer on 0-RTT or 1-RTT data when it knows
that the peer has the keys necessary to read and write in 1-RTT, and can
therefore respond with an ACK.

We think this holds up, but we'd like to get this under everyone's eyes, to
ensure that the discussion isn't missing subtle deadlock issues.

S2.

To solve the second problem, the proposal is to use ack_delay as reported
by the endpoint that buffers the data appropriately. ack_delay is the
amount of the time the information (regardless of that being the packet
itself or the acknowledgement) being buffered intentionally. For this, we
need the following:

- endpoints MUST report an ack_delay that is the sum of the controlled
delay (i.e. the duration of the data and the ack being buffered)

- endpoints ignore max_ack_delay for acknowledgements of packets that were
sent prior to handshake confirmation. Those are the ones that might have
been buffered at the peer until keys were ready.

In addition, we explicitly recommend endpoints that asynchronously process
handshake messages to buffer 1-RTT packets, instead of dropping them, as
dropping packets has significant impact on congestion control. Note that
this matches what those implementations already do.



Thoughts?


- jana

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

<div dir=3D"ltr"><span id=3D"gmail-docs-internal-guid-ef699920-7fff-eeac-8e=
68-87ae780358aa"><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;ma=
rgin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(=
0,0,0);background-color:transparent;font-variant-numeric:normal;font-varian=
t-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">I&#39;d l=
ike to bring this slightly tricky issue under the wg&#39;s eyes. Discussion=
s so far have yielded a strategy that I propose further below. This summari=
zes conversations in </span><a href=3D"https://github.com/quicwg/base-draft=
s/issues/3821" style=3D"text-decoration-line:none"><span style=3D"font-size=
:11pt;font-family:Arial;background-color:transparent;font-variant-numeric:n=
ormal;font-variant-east-asian:normal;text-decoration-line:underline;vertica=
l-align:baseline;white-space:pre-wrap">3821</span></a><span style=3D"font-s=
ize:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;fo=
nt-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:bas=
eline;white-space:pre-wrap"> and </span><a href=3D"https://github.com/quicw=
g/base-drafts/pull/3874" style=3D"text-decoration-line:none"><span style=3D=
"font-size:11pt;font-family:Arial;background-color:transparent;font-variant=
-numeric:normal;font-variant-east-asian:normal;text-decoration-line:underli=
ne;vertical-align:baseline;white-space:pre-wrap">3874</span></a><span style=
=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:tran=
sparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertical=
-align:baseline;white-space:pre-wrap"> (and the outcomes might touch </span=
><a href=3D"https://github.com/quicwg/base-drafts/issues/3889" style=3D"tex=
t-decoration-line:none"><span style=3D"font-size:11pt;font-family:Arial;bac=
kground-color:transparent;font-variant-numeric:normal;font-variant-east-asi=
an:normal;text-decoration-line:underline;vertical-align:baseline;white-spac=
e:pre-wrap">3889</span></a><span style=3D"font-size:11pt;font-family:Arial;=
color:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;f=
ont-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"=
>). The purpose of this email is to see if we can agree on the strategies o=
utlined here, so we can move forward on the PR there and/or other associate=
d issues and PRs.</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;ma=
rgin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:A=
rial;color:rgb(0,0,0);background-color:transparent;font-weight:700;font-var=
iant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;=
white-space:pre-wrap">Problems:</span></p><br><p dir=3D"ltr" style=3D"line-=
height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt=
;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-varia=
nt-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;wh=
ite-space:pre-wrap">During the handshake, an endpoint can receive packets (=
carrying data or acknowledgements) that it cannot decrypt because the requi=
site keys are not yet available. This can happen because the crypto machine=
ry at the endpoint is waiting for earlier packets to be received to yield t=
he keys. Similarly, a client might not be able to read 1-RTT packets receiv=
ed from the server because it is waiting for certificate validation to comp=
lete.</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt=
;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:r=
gb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-var=
iant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">1.</sp=
an></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-botto=
m:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);bac=
kground-color:transparent;font-variant-numeric:normal;font-variant-east-asi=
an:normal;vertical-align:baseline;white-space:pre-wrap">The assumption in t=
he TLS specification is that when an endpoint is busy doing something (cert=
ificate validation or key generation for instance), it won&#39;t be able to=
 respond to received packets with acknowledgements (</span><a href=3D"https=
://quicwg.org/base-drafts/draft-ietf-quic-tls.html#section-4.1.4-1" style=
=3D"text-decoration-line:none"><span style=3D"font-size:11pt;font-family:Ar=
ial;background-color:transparent;font-variant-numeric:normal;font-variant-e=
ast-asian:normal;text-decoration-line:underline;vertical-align:baseline;whi=
te-space:pre-wrap">Section 4.1.4</span></a><span style=3D"font-size:11pt;fo=
nt-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-=
numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white=
-space:pre-wrap">).</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;=
margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family=
:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:n=
ormal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pr=
e-wrap">Contrary to the assumption in the spec, Chrome and Firefox both pro=
cess the certificate chain asynchronously, and therefore acks handshake pac=
kets immediately, even the ones that arrive after they have started verifyi=
ng the certificate chain. But they buffer 1-RTT packets, and therefore the =
issue exists for 1-RTT packets.</span></p><br><p dir=3D"ltr" style=3D"line-=
height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt=
;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-varia=
nt-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;wh=
ite-space:pre-wrap">As a result, there&#39;s potential delay, sometimes sig=
nificant, in responding to some packets during the handshake. There are two=
 side effects of this.</span></p><br><p dir=3D"ltr" style=3D"line-height:1.=
38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-fam=
ily:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeri=
c:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space=
:pre-wrap">S1.</span></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-to=
p:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;co=
lor:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;fon=
t-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">F=
irst, this means that an endpoint that runs a PTO timer and retransmits dat=
a for 0-RTT and 1-RTT packets while the handshake is still in progress migh=
t be doing this quite unnecessarily. The peer may well have received this d=
ata and have queued it, waiting to be able to decrypt it.=C2=A0</span></p><=
br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0p=
t"><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);backgro=
und-color:transparent;font-variant-numeric:normal;font-variant-east-asian:n=
ormal;vertical-align:baseline;white-space:pre-wrap">S2.</span></p><p dir=3D=
"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span sty=
le=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:tr=
ansparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertic=
al-align:baseline;white-space:pre-wrap">Second, acks for these packets that=
 are buffered and then later decrypted and read can be sent much later than=
 when the packets were received at the peer, causing the ack_delay to poten=
tially be much higher than the advertised max_ack_delay. The endpoint ignor=
es ack_delay larger than max_ack_delay, and this inflates the smoothed_rtt =
and rtt_variance, potentially inflating the PTO significantly (which can ca=
use handshakes to fail if the endpoint employs a &quot;handshake timeout&qu=
ot; period).</span></p><br><br><p dir=3D"ltr" style=3D"line-height:1.38;mar=
gin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Ar=
ial;color:rgb(0,0,0);background-color:transparent;font-weight:700;font-vari=
ant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;w=
hite-space:pre-wrap">Proposed Solutions:</span></p><br><p dir=3D"ltr" style=
=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-=
size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;f=
ont-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:ba=
seline;white-space:pre-wrap">S1.</span></p><p dir=3D"ltr" style=3D"line-hei=
ght:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;fo=
nt-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-=
numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white=
-space:pre-wrap">To solve the first problem, we already have a condition in=
 the recovery draft to _not_ arm the PTO on 1-RTT data until the handshake =
is complete (</span><a href=3D"https://quicwg.org/base-drafts/draft-ietf-qu=
ic-recovery.html#section-6.2.1-6" style=3D"text-decoration-line:none"><span=
 style=3D"font-size:11pt;font-family:Arial;background-color:transparent;fon=
t-variant-numeric:normal;font-variant-east-asian:normal;text-decoration-lin=
e:underline;vertical-align:baseline;white-space:pre-wrap">Section 6.2.1</sp=
an></a><span style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);bac=
kground-color:transparent;font-variant-numeric:normal;font-variant-east-asi=
an:normal;vertical-align:baseline;white-space:pre-wrap">). This is not quit=
e adequate, since it still allows a client to arm a PTO timer on 1-RTT data=
 on sending a CFIN and 1-RTT data, before ensuring that the server has rece=
ived the CFIN. The proposed solution here is to change this condition from =
&quot;handshake complete&quot; to &quot;handshake confirmed&quot;. Meaning =
that an endpoint only arms a PTO timer on 0-RTT or 1-RTT data when it knows=
 that the peer has the keys necessary to read and write in 1-RTT, and can t=
herefore respond with an ACK.</span></p><br><p dir=3D"ltr" style=3D"line-he=
ight:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;f=
ont-family:Arial;color:rgb(0,0,0);background-color:transparent;font-variant=
-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;whit=
e-space:pre-wrap">We think this holds up, but we&#39;d like to get this und=
er everyone&#39;s eyes, to ensure that the discussion isn&#39;t missing sub=
tle deadlock issues.</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38=
;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-famil=
y:Arial;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:=
normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:p=
re-wrap">S2.</span></p><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:=
0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;colo=
r:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-=
variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">To =
solve the second problem, the proposal is to use ack_delay as reported by t=
he endpoint that buffers the data appropriately. ack_delay is the amount of=
 the time the information (regardless of that being the packet itself or th=
e acknowledgement) being buffered intentionally. For this, we need the foll=
owing:</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;margin-top:0p=
t;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;color:=
rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;font-va=
riant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">- end=
points MUST report an ack_delay that is the sum of the controlled delay (i.=
e. the duration of the data and the ack being buffered)</span></p><br><p di=
r=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span=
 style=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-colo=
r:transparent;font-variant-numeric:normal;font-variant-east-asian:normal;ve=
rtical-align:baseline;white-space:pre-wrap">- endpoints ignore max_ack_dela=
y for acknowledgements of packets that were sent prior to handshake confirm=
ation. Those are the ones that might have been buffered at the peer until k=
eys were ready.</span></p><br><p dir=3D"ltr" style=3D"line-height:1.38;marg=
in-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Ari=
al;color:rgb(0,0,0);background-color:transparent;font-variant-numeric:norma=
l;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wr=
ap">In addition, we explicitly recommend endpoints that asynchronously proc=
ess handshake messages to buffer 1-RTT packets, instead of dropping them, a=
s dropping packets has significant impact on congestion control. Note that =
this matches what those implementations already do.</span></p><p dir=3D"ltr=
" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br></p><p di=
r=3D"ltr" style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><br><=
/p><p style=3D"line-height:1.38;margin-top:0pt;margin-bottom:0pt"><span sty=
le=3D"font-size:11pt;font-family:Arial;color:rgb(0,0,0);background-color:tr=
ansparent;font-variant-numeric:normal;font-variant-east-asian:normal;vertic=
al-align:baseline;white-space:pre-wrap">Thoughts?</span></p><p style=3D"lin=
e-height:1.38;margin-top:0pt;margin-bottom:0pt"><span style=3D"font-size:11=
pt;font-family:Arial;color:rgb(0,0,0);background-color:transparent;font-var=
iant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;=
white-space:pre-wrap"><br></span></p><p style=3D"line-height:1.38;margin-to=
p:0pt;margin-bottom:0pt"><span style=3D"font-size:11pt;font-family:Arial;co=
lor:rgb(0,0,0);background-color:transparent;font-variant-numeric:normal;fon=
t-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">-=
 jana</span></p></span></div>

--00000000000073474f05aa9f65ed--


From nobody Fri Jul 17 05:21:39 2020
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4F58F3A0B08 for <quic@ietfa.amsl.com>; Fri, 17 Jul 2020 05:21:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 BGFersCY4Qbj for <quic@ietfa.amsl.com>; Fri, 17 Jul 2020 05:21:36 -0700 (PDT)
Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (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 52B173A0B04 for <quic@ietf.org>; Fri, 17 Jul 2020 05:21:36 -0700 (PDT)
Received: by mail-lf1-x131.google.com with SMTP id y18so5880990lfh.11 for <quic@ietf.org>; Fri, 17 Jul 2020 05:21:36 -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=KaMI0Dyc9+EI8kr3l5nOTntnvT/LwymU0YWRWhHTrOs=; b=f2I2a7ucBr2PcR9MgqZH25805gHc0ipJcvY+r74sQLEdkW8/cG8oOac8a0HlR0bnSJ W+HX8T3JYGcVQKpEvt9zrgUHMBAbG6fWQmPJi60qajMYM0vw0Dks9o2kSzw30b3mPTOJ ohhZUF39+lpeFbcXnKHP9covAlTBWir5gVtRPPQLs/WNQmSBqXpyK18pkJ4/qlqrAlAR jvdDM41jXXY3NAB+xa8BiaVdtpkJob4umnZbng0TCzQr75r3CUMwRyEXakV4PZadXZhJ L0FjpMYu2npGvmR41Rbany5EmgSPgydO2ATxrv0Cqt1o8OA6/JyZz0vetdQz6csNwFqZ T1bQ==
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=KaMI0Dyc9+EI8kr3l5nOTntnvT/LwymU0YWRWhHTrOs=; b=QFHE4+NhCATQVFRA05x4tuEJ+tt+UAJiOoDWD0I+Y2AujyNtAStEs59u5MRxsNsK2m auA4ZwTUwCS7Oez/m8PrJbxmit2qmQQ5FSxTKbkkKpvN2cQlvJGXjri0fySxjyarLXpZ khAaHRbShKIZ+pjs90UqFY8ZGT+YejB9rAZnrhXGwHoc5VK2biT2ls6HppPRHSS+Z9l9 PKDxYF6W3mF/2tcP/F/L3//zYmT3WuLyF9Hmu6dukQSDMT++FspfmIr+efewaCKrES56 aXob+mEnKvtvTfJJvK6CArij2mm5CHKtll8K01VAaN3fps+hak3dA7hUdChWyJd+RTad oYWw==
X-Gm-Message-State: AOAM532T7AQoXZk62cEHf+CO8G2cImeCtKNZ7d+K9w9+LrkZgc3d2IS3 bsBs+q1DKve4ErWMse85aZzLQaPnGBsmbG8IExk=
X-Google-Smtp-Source: ABdhPJwsFV4YEqoM/KEo6Mr40OXJTB3xnC2Enut8gncDHv0lioV2Dkjj0TgqbeerzSD8KBbVeIJN1tlsmQAX/wRnaag=
X-Received: by 2002:ac2:558f:: with SMTP id v15mr4583912lfg.187.1594988494438;  Fri, 17 Jul 2020 05:21:34 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <53187d65-f7b9-b99a-f68b-b267303ab399@erg.abdn.ac.uk> <CH2PR00MB0726D18611EC030BF548CA0DB6640@CH2PR00MB0726.namprd00.prod.outlook.com> <40818629-e1dc-f0f1-6173-984a8166c7c2@erg.abdn.ac.uk> <CH2PR00MB07267EBAC2BB08CCE5160EC6B6650@CH2PR00MB0726.namprd00.prod.outlook.com> <CAKcm_gN=vizG9+kiRiX7BAfcsR1p+Q1FrTtNPXfV5vFATBNQ9Q@mail.gmail.com> <CAKKJt-c-sp=L7j5--aoEEObMjhcnTE7YVK_NE4YQFGZDtcLhrA@mail.gmail.com> <CACpbDcfrVNtDb3htqnkVqr2OOskUVr_aYTrRvssT_tAgTKqV_g@mail.gmail.com>
In-Reply-To: <CACpbDcfrVNtDb3htqnkVqr2OOskUVr_aYTrRvssT_tAgTKqV_g@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Fri, 17 Jul 2020 07:21:08 -0500
Message-ID: <CAKKJt-f76tVoUiAwZrfyOEDG1FPTqbxu0Zg_Or_OymRwaNAwcw@mail.gmail.com>
Subject: Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
To: Jana Iyengar <jri.ietf@gmail.com>
Cc: Ian Swett <ianswett=40google.com@dmarc.ietf.org>,  Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>,  Gorry Fairhurst <gorry@erg.abdn.ac.uk>, IETF QUIC WG <quic@ietf.org>,  Neal Cardwell <ncardwell@google.com>, Yuchung Cheng <ycheng@google.com>
Content-Type: multipart/alternative; boundary="000000000000a1c63105aaa2325f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/HepAbKF3Im5oKmtBjazDiFYxtFk>
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, 17 Jul 2020 12:21:38 -0000

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

Hi, Jana,

On Thu, Jul 16, 2020 at 8:30 PM Jana Iyengar <jri.ietf@gmail.com> wrote:

> At a high level, the recovery doc is _not_ written with DC environments in
> mind. We can make that clear in the document, if that helps. There are
> other things as well that won't work well in a DC environment, and I
> imagine a separate doc would be helpful here that specifies how QUIC ought
> to be tuned for DCs.
>

Two things.

My response to Ian was just about the history of what TSV has come to
expect for encapsulation protocol behaviors in the past half-dozen years
("if you are doing stuff that's not safe on an unmanaged network, this is
what you should do; if you're doing the same thing on a managed network,
this is what you can probably get away with, and please point to your
circuit breaker functionality in case what you're doing turns out to be a
Really Bad Idea" - paraphrasing over a lot of subtilty).

Those documents tended to have both cases in a single document, along with
the rest of the encapsulation protocol, in many cases because the
"unmanaged networks" considerations were being added to a single document
that already described "managed networks" considerations.

Pretty much every conversation I was involved in at QUIC charter time
assumed that we would want to swap recovery functionality in and out over
time without reopening draft-ietf-quic-transport, so having a separate
recovery document was the right thing to do.

Because QUIC already has a separate "safe for unmanaged networks" recovery
document, I think putting other recovery strategies in separate documents
is a fine plan.

Does that make sense?

Best,

Spencer

On Thu, Jul 16, 2020 at 2:18 PM Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
>
>> Hi, Ian,
>>
>> On Thu, Jul 16, 2020 at 2:22 PM Ian Swett <ianswett=
>> 40google.com@dmarc.ietf.org> wrote:
>>
>>> Thanks for the comments, I filed #3918
>>> <https://github..com/quicwg/base-drafts/issues/3918> and #3919
>>> <https://github.com/quicwg/base-drafts/issues/3919>
>>>
>>> For my background, are you aware other transport RFCs have normative
>>> statements that only apply to the public internet?
>>>
>>
>> Tunnels are transport, right? :-)
>>
>> The earliest RFC I was involved with, that made distinctions about what
>> you can get away with on the public internet versus in a managed network,
>> was https://tools.ietf.org/html/rfc7510#section-5. This was negotiated
>> after a fairly vigorous back-and-forth between transport people and
>> non-transport people during IETF Last Call.
>>
>> We put together a design team with a few people to try to work through
>> this for the myriad other protocols that people wanted to tunnel over UDP,
>> once and for all.
>>
>> https://tools.ietf.org/html/rfc8084 was published as a BCP.
>>
>> I may be forgetting other stuff, of course.
>>
>> Best,
>>
>> Spencer
>>
>>
>>> Also, if you're that well buffered and the bursts are that large, do you
>>> still start with IW10, or do you start with a larger window?
>>>
>>> Thanks, Ian
>>>
>>>>

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

<div dir=3D"ltr"><div dir=3D"ltr">Hi, Jana,=C2=A0</div><br><div class=3D"gm=
ail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jul 16, 2020 at 8:=
30 PM Jana Iyengar &lt;<a href=3D"mailto:jri.ietf@gmail.com">jri.ietf@gmail=
.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"mar=
gin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1=
ex"><div dir=3D"ltr">At a high level, the recovery doc is _not_ written wit=
h DC environments in mind. We can make that clear in the document, if that =
helps. There are other things as well that won&#39;t work well in a DC envi=
ronment, and I imagine a separate doc would be helpful here that specifies =
how QUIC ought to be tuned for DCs.</div></blockquote><div><br></div><div>T=
wo things.</div><div><br></div><div>My response to Ian was just about the h=
istory of what TSV has come to expect for encapsulation protocol behaviors =
in the past half-dozen years (&quot;if you are doing stuff that&#39;s not s=
afe on an unmanaged network, this is what you should do; if you&#39;re doin=
g the same thing on a managed network, this is what you can probably get aw=
ay with, and please point to your circuit breaker functionality in case wha=
t you&#39;re doing turns out to be a Really Bad Idea&quot; - paraphrasing o=
ver a lot of subtilty).=C2=A0</div><div><br></div><div>Those documents tend=
ed to have both cases in a single document, along with the rest of the enca=
psulation protocol, in many cases because the &quot;unmanaged networks&quot=
; considerations were being added to a single document that already describ=
ed &quot;managed networks&quot; considerations.=C2=A0</div><div><br></div><=
div>Pretty much every conversation I was involved in at QUIC charter time a=
ssumed that we would want to swap recovery functionality in and out over ti=
me without reopening draft-ietf-quic-transport, so having a separate recove=
ry document was the right thing to do.=C2=A0</div><div><br></div><div>Becau=
se QUIC already has a separate &quot;safe for unmanaged networks&quot; reco=
very document, I think putting other recovery strategies in separate docume=
nts is a fine plan.=C2=A0</div><div><br></div><div>Does that make sense?</d=
iv><div><br></div><div>Best,</div><div><br></div><div>Spencer</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 class=3D"gmai=
l_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jul 16, 2020 at 2:18=
 PM Spencer Dawkins at IETF &lt;<a href=3D"mailto:spencerdawkins.ietf@gmail=
.com" target=3D"_blank">spencerdawkins.ietf@gmail.com</a>&gt; wrote:<br></d=
iv><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;bord=
er-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div =
dir=3D"ltr">Hi, Ian,=C2=A0</div><br><div class=3D"gmail_quote"><div dir=3D"=
ltr" class=3D"gmail_attr">On Thu, Jul 16, 2020 at 2:22 PM Ian Swett &lt;ian=
swett=3D<a href=3D"mailto:40google.com@dmarc.ietf.org" target=3D"_blank">40=
google.com@dmarc.ietf.org</a>&gt; wrote:<br></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"><div dir=3D"ltr">Thanks for the comments, I filed =
<a href=3D"https://github..com/quicwg/base-drafts/issues/3918" target=3D"_b=
lank">#3918</a> and <a href=3D"https://github.com/quicwg/base-drafts/issues=
/3919" target=3D"_blank">#3919</a>=C2=A0<div><br></div><div>For my backgrou=
nd, are you=C2=A0aware other transport RFCs have normative statements that =
only apply to the public internet?=C2=A0 </div></div></blockquote><div><br>=
</div><div>Tunnels are transport, right? :-)</div><div><br></div><div>The e=
arliest RFC I was involved with, that made distinctions about what you can =
get away with on the public internet versus in a managed network, was=C2=A0=
<a href=3D"https://tools.ietf.org/html/rfc7510#section-5" target=3D"_blank"=
>https://tools.ietf.org/html/rfc7510#section-5</a>. This was negotiated aft=
er a fairly vigorous back-and-forth between transport people and non-transp=
ort people during IETF Last Call.=C2=A0</div><div><br></div><div>We put tog=
ether a design team with a few people to try to work through this for the m=
yriad other protocols that people wanted to tunnel over UDP, once and for a=
ll.=C2=A0</div><div><br></div><div><a href=3D"https://tools.ietf.org/html/r=
fc8084" target=3D"_blank">https://tools.ietf.org/html/rfc8084</a> was publi=
shed as a BCP.=C2=A0<br></div><div><br></div><div>I may be forgetting other=
 stuff, of course.</div><div><br></div><div>Best,</div><div><br></div><div>=
Spencer</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 dir=3D"ltr"><div>Also, if you&#39;re that well buffered and the b=
ursts are that large, do you still start with IW10, or do you start with a =
larger window?</div><div><br></div><div>Thanks, Ian<br></div></div><div cla=
ss=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margin:0px 0p=
x 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div l=
ang=3D"EN-US"><div><blockquote style=3D"margin-top:5pt;margin-bottom:5pt">
</blockquote>
</div>
</div>

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

--000000000000a1c63105aaa2325f--


From nobody Fri Jul 17 09:41:56 2020
Return-Path: <pravb@microsoft.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 9F2163A097D for <quic@ietfa.amsl.com>; Fri, 17 Jul 2020 09:41:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level: 
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9,  DKIMWL_WL_HIGH=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, 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=microsoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 3wGyjfxR1zsB for <quic@ietfa.amsl.com>; Fri, 17 Jul 2020 09:41:53 -0700 (PDT)
Received: from NAM06-BL2-obe.outbound.protection.outlook.com (mail-eopbgr650117.outbound.protection.outlook.com [40.107.65.117]) (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 20A1E3A094B for <quic@ietf.org>; Fri, 17 Jul 2020 09:41:52 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=QLimdeQ7KAFlS3FU3Eivww5vpjmhh+5gGd8ODX3rCR7Ub8ob/qcEmOZDQk40bpbdqH6IVvZaD2qpWUqBoxKU/AVEiVHalTPrDJWeF6FFSpw/HWzGm2BeoGLZQUeeJo53NMH3xH5+QlWIJ9iHnCxNQxrYx1tYRDt9B5fmnNSpt+Yh2gh9GQhtFpJ0h6df9h/u18YFBp8CHkKr6nU5hcwEmrSsX6b1u1QN0eH2+J4dwcGu6QsmN/cYdXE3VtLx7aZz6jXP7cf6l6MKJYTZ4bWKiQhjRDTh/EghXbDus9SFzJvQnLHwF0hPh7TbP6fnw7UtCuF3LmJpE5jfB0b8zFROfg==
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=NkBT+v99QfeCs/EU5uuXqXetq+iMDewJglwt8g41UL8=; b=lYPvWjBvkpkamB1mHS/876UGPZ2DdiMXhcpY1qmnx9mYwsicKyyYa9v/Qsgy4HIFWemhKNcW5re5D71gsU7JmXbuQbL1MWkCdM69J1/nIlWSSd/5dTbVIgDz0sBQhB30EpCPGvqFaIEdqGX6CLpta0Vve+6044BwUKTMFL+MXKt32LGxxIPxnKLraN6lUZMHHKlY6LZ6/Ody0+VYidpcC0dauTg0eq5br1/E5JOtaDngYF50gH0E3Q8CcWSNdsaZx6wzI1WexooBz6t6gVNJVq1aJh+7SWSbjvBdeOvNmWHtokVNJfDKwqDt/YVgap3mpiM091mbGoP17q+NkPfw4g==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=NkBT+v99QfeCs/EU5uuXqXetq+iMDewJglwt8g41UL8=; b=juCigefxGmicrZglUUA6lu8tW2PGeIcYzYHzmYBUTTab6JJGwZ+oHiT2NU/6YP9fMe8YOlRa0zP8reb5oxh9Uh65w0jbENpCBqqoTz/RHg4XxZ61Rsyfj/oZt6UrCZ/3TgQP9LvjqRPUieMcRkLeoLqE0KXniaWG4/0gH6pR9U4=
Received: from CH2PR00MB0726.namprd00.prod.outlook.com (2603:10b6:610:ad::12) by CH2PR00MB0809.namprd00.prod.outlook.com (2603:10b6:610:6f::20) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3240.0; Fri, 17 Jul 2020 16:41:51 +0000
Received: from CH2PR00MB0726.namprd00.prod.outlook.com ([fe80::7562:9640:814e:c7f1]) by CH2PR00MB0726.namprd00.prod.outlook.com ([fe80::7562:9640:814e:c7f1%9]) with mapi id 15.20.3238.000; Fri, 17 Jul 2020 16:41:51 +0000
From: Praveen Balasubramanian <pravb@microsoft.com>
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Jana Iyengar <jri.ietf@gmail.com>
CC: Ian Swett <ianswett@google.com>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>, IETF QUIC WG <quic@ietf.org>, Neal Cardwell <ncardwell@google.com>, Yuchung Cheng <ycheng@google.com>
Subject: RE: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
Thread-Topic: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
Thread-Index: AdZVbt/Rv8RxmVSLQP+4+5gZJ/6HOgAXZSqAAA+FIqAAIiCEAAASWdawATJ/KQAABAk/AAAIztgAABa8GQAACH5psA==
Date: Fri, 17 Jul 2020 16:41:51 +0000
Message-ID: <CH2PR00MB0726A8F0BFBED6702448AC40B67C0@CH2PR00MB0726.namprd00.prod.outlook.com>
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <53187d65-f7b9-b99a-f68b-b267303ab399@erg.abdn.ac.uk> <CH2PR00MB0726D18611EC030BF548CA0DB6640@CH2PR00MB0726.namprd00.prod.outlook.com> <40818629-e1dc-f0f1-6173-984a8166c7c2@erg.abdn.ac.uk> <CH2PR00MB07267EBAC2BB08CCE5160EC6B6650@CH2PR00MB0726.namprd00.prod.outlook.com> <CAKcm_gN=vizG9+kiRiX7BAfcsR1p+Q1FrTtNPXfV5vFATBNQ9Q@mail.gmail.com> <CAKKJt-c-sp=L7j5--aoEEObMjhcnTE7YVK_NE4YQFGZDtcLhrA@mail.gmail.com> <CACpbDcfrVNtDb3htqnkVqr2OOskUVr_aYTrRvssT_tAgTKqV_g@mail.gmail.com> <CAKKJt-f76tVoUiAwZrfyOEDG1FPTqbxu0Zg_Or_OymRwaNAwcw@mail.gmail.com>
In-Reply-To: <CAKKJt-f76tVoUiAwZrfyOEDG1FPTqbxu0Zg_Or_OymRwaNAwcw@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=true; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2020-07-17T16:41:49Z;  MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=0d519699-a21a-4472-a0c5-cafe795485f9; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [2001:4898:80e8:1:95d7:3f73:f682:d302]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: ee4e5436-0ff0-42d6-1a59-08d82a704e65
x-ms-traffictypediagnostic: CH2PR00MB0809:
x-microsoft-antispam-prvs: <CH2PR00MB08098E078884C26B7979C83FB67C0@CH2PR00MB0809.namprd00.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: bykbZk559k+nwJDUCTkBCrGGXnacFBMYca7SxumCZKXd1NE5gQLCC0j7/f+HG3lXMJUF8QjPDo4XcLyg1weQtu+SK9sb/LFRAdEt3dgHoSVKRQIMSZRB1ptd+rDrKWpiVOnHd+T3eVtWT4HzhpyU+Q6FPz3Jdpjf1uc7BP66x+67DLs/XZPylVQ8IsR8mtcn+v8gERwvCIg8voBbY67wgCyoVuW/6ysBmTUeCLe1eZaWSuoYuNCaMq6bkzCGpitXNsvblcqusBf28/jkAdbnjz/85of23Q/9jbU9QkNmaazew027G6xGa2wWKgZZRQ2uZ5jJ7Mo7su8KDVlk06/gst4vFYwmnlmpiGmrlpK3/MCLzc6CcL2ny9WzABZoLGOtYnfKGQl9ozg8hIYdoncJGQ==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:CH2PR00MB0726.namprd00.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(39860400002)(396003)(346002)(376002)(136003)(366004)(66574015)(8676002)(7696005)(6506007)(54906003)(966005)(71200400001)(186003)(66446008)(2906002)(83380400001)(53546011)(66556008)(478600001)(66476007)(64756008)(76116006)(66946007)(82950400001)(10290500003)(9686003)(86362001)(316002)(52536014)(82960400001)(4326008)(8936002)(110136005)(166002)(5660300002)(55016002)(8990500004)(33656002); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: JyXHpJRqEckOHwQiRYgrlS8cKoNIcUFn0r8++2n088sRgj+5GiV8xcpMq3l5L1ihLtD6P1IW4k9Q5CXFTurEfCnjfUhCWAeD41h2t/9ODuGmTIsE4VB0EyrA3Whw/jDItMwbCKpZYhVVG6vrMPAwrJD3Jc4T3n4lUbnVibbpOCrGxVIMv5UZ2Q0sDuE/14JAL/iwOxAYmGCv0qUdvkMJ/xJsZYfMbYQqV5WvUtIhEHU6vww+4iAW35SGGh2O5hJ35fHerHtp51kXC/COA1sT1zG5vb68PCP1w47ZDHKnRpA32TPOXwjwadNDee5RowQVZ/I7fp6Isq/zi9g+XeKvgWYvmTDSnX52pFytFOLB6EfoBFJ1z3eWwG0I0pe+pMj0fSm3u2I3bFM89UEwO0d+ze+y3NtSaZKdX6s1udeGqrESzZmMGMR0INvkwPAlnFxHqy2lUdeZxRd9sCPZFtpRnyjrsbiEUuXR/OJYgwTOFdh02iXDODIWqmp+3jv/7KTsJDb5Y+jhFNiM1UAODyK6KQdSrjTOgTjzEtsMJyX8HoPwRy+GFPf/A10ShWEdMoS6ygMVbFQe1mFwV9UK2GbHXCqhhIUc01Bw2Y64v7nYeyChB0ySEyyyE2mWXapRUJwDXlEP/HI6S5A4GO43D2NhvWlA0VoLuKqOyMWAxLxbooaVnMV5zvAWrV37NTxr7scFd0y6l5y9vZ8xstkSg8BwTQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CH2PR00MB0726A8F0BFBED6702448AC40B67C0CH2PR00MB0726namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CH2PR00MB0726.namprd00.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: ee4e5436-0ff0-42d6-1a59-08d82a704e65
X-MS-Exchange-CrossTenant-originalarrivaltime: 17 Jul 2020 16:41:51.1185 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: vJo3bYf5A/EGg+D2WYyjHcEjWzCXYfQm3s1qhPXYo7q4LAbhovs0aOtZ8GTlxa/PAVGDZR38k2LjTC+5/mPV0s2VEUNQrWbfU04poRA0QOs=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR00MB0809
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/g1iBPs0h6XXdHDCg8xGyZTRiF2s>
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, 17 Jul 2020 16:41:56 -0000

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

QUZBSUNUIHRoZXJlIGlzIG5vIFJGQyBmb3IgVENQIHRoYXQgbGltaXRzIGJ1cnN0IHNpemVzIGlu
IGdlbmVyYWwuIEkgZG9u4oCZdCB0aGluayB3ZSBuZWVkIHRvIHNwZWNpYWwgY2FzZSBJbnRlcm5l
dCBhbmQgREMgbmV0d29ya3MuIENoYW5naW5nIHRoZSBsYW5ndWFnZSBmcm9tIGEgTVVTVCB0byBh
IFNIT1VMRCBpcyBzdWZmaWNpZW50IGhlcmUuIEl0IGxlYXZlcyBlbm91Z2ggd2lnZ2xlIHJvb20g
Zm9yIGRlcGxveW1lbnRzIGFuZCBleHBlcmltZW50YXRpb24uDQoNCkkgZG9u4oCZdCBzZWUgdG9v
IG1hbnkgb3RoZXIgY2hhbmdlcyBuZWVkZWQgaW4gcmVjb3ZlcnkgZHJhZnQgZm9yIERDIGVudmly
b25tZW50IHBhcnRpY3VsYXJseSBub3cgdGhhdCB0aGVyZSBpcyBubyBtaW4gcnRvLiBKYW5hLCB3
aGF0IG90aGVyIGNoYW5nZXMgZG8geW91IGhhdmUgaW4gbWluZD8NCg0KRnJvbTogU3BlbmNlciBE
YXdraW5zIGF0IElFVEYgPHNwZW5jZXJkYXdraW5zLmlldGZAZ21haWwuY29tPg0KU2VudDogRnJp
ZGF5LCBKdWx5IDE3LCAyMDIwIDU6MjEgQU0NClRvOiBKYW5hIEl5ZW5nYXIgPGpyaS5pZXRmQGdt
YWlsLmNvbT4NCkNjOiBJYW4gU3dldHQgPGlhbnN3ZXR0QGdvb2dsZS5jb20+OyBQcmF2ZWVuIEJh
bGFzdWJyYW1hbmlhbiA8cHJhdmJAbWljcm9zb2Z0LmNvbT47IEdvcnJ5IEZhaXJodXJzdCA8Z29y
cnlAZXJnLmFiZG4uYWMudWs+OyBJRVRGIFFVSUMgV0cgPHF1aWNAaWV0Zi5vcmc+OyBOZWFsIENh
cmR3ZWxsIDxuY2FyZHdlbGxAZ29vZ2xlLmNvbT47IFl1Y2h1bmcgQ2hlbmcgPHljaGVuZ0Bnb29n
bGUuY29tPg0KU3ViamVjdDogUmU6IFtFWFRFUk5BTF0gUmU6IFdHTEMgcmV2aWV3IG9mIGRyYWZ0
LWlldGYtcXVpYy1yZWNvdmVyeS0yOQ0KDQpIaSwgSmFuYSwNCg0KT24gVGh1LCBKdWwgMTYsIDIw
MjAgYXQgODozMCBQTSBKYW5hIEl5ZW5nYXIgPGpyaS5pZXRmQGdtYWlsLi5jb208bWFpbHRvOmpy
aS5pZXRmQGdtYWlsLmNvbT4+IHdyb3RlOg0KQXQgYSBoaWdoIGxldmVsLCB0aGUgcmVjb3Zlcnkg
ZG9jIGlzIF9ub3RfIHdyaXR0ZW4gd2l0aCBEQyBlbnZpcm9ubWVudHMgaW4gbWluZC4gV2UgY2Fu
IG1ha2UgdGhhdCBjbGVhciBpbiB0aGUgZG9jdW1lbnQsIGlmIHRoYXQgaGVscHMuIFRoZXJlIGFy
ZSBvdGhlciB0aGluZ3MgYXMgd2VsbCB0aGF0IHdvbid0IHdvcmsgd2VsbCBpbiBhIERDIGVudmly
b25tZW50LCBhbmQgSSBpbWFnaW5lIGEgc2VwYXJhdGUgZG9jIHdvdWxkIGJlIGhlbHBmdWwgaGVy
ZSB0aGF0IHNwZWNpZmllcyBob3cgUVVJQyBvdWdodCB0byBiZSB0dW5lZCBmb3IgRENzLg0KDQpU
d28gdGhpbmdzLg0KDQpNeSByZXNwb25zZSB0byBJYW4gd2FzIGp1c3QgYWJvdXQgdGhlIGhpc3Rv
cnkgb2Ygd2hhdCBUU1YgaGFzIGNvbWUgdG8gZXhwZWN0IGZvciBlbmNhcHN1bGF0aW9uIHByb3Rv
Y29sIGJlaGF2aW9ycyBpbiB0aGUgcGFzdCBoYWxmLWRvemVuIHllYXJzICgiaWYgeW91IGFyZSBk
b2luZyBzdHVmZiB0aGF0J3Mgbm90IHNhZmUgb24gYW4gdW5tYW5hZ2VkIG5ldHdvcmssIHRoaXMg
aXMgd2hhdCB5b3Ugc2hvdWxkIGRvOyBpZiB5b3UncmUgZG9pbmcgdGhlIHNhbWUgdGhpbmcgb24g
YSBtYW5hZ2VkIG5ldHdvcmssIHRoaXMgaXMgd2hhdCB5b3UgY2FuIHByb2JhYmx5IGdldCBhd2F5
IHdpdGgsIGFuZCBwbGVhc2UgcG9pbnQgdG8geW91ciBjaXJjdWl0IGJyZWFrZXIgZnVuY3Rpb25h
bGl0eSBpbiBjYXNlIHdoYXQgeW91J3JlIGRvaW5nIHR1cm5zIG91dCB0byBiZSBhIFJlYWxseSBC
YWQgSWRlYSIgLSBwYXJhcGhyYXNpbmcgb3ZlciBhIGxvdCBvZiBzdWJ0aWx0eSkuDQoNClRob3Nl
IGRvY3VtZW50cyB0ZW5kZWQgdG8gaGF2ZSBib3RoIGNhc2VzIGluIGEgc2luZ2xlIGRvY3VtZW50
LCBhbG9uZyB3aXRoIHRoZSByZXN0IG9mIHRoZSBlbmNhcHN1bGF0aW9uIHByb3RvY29sLCBpbiBt
YW55IGNhc2VzIGJlY2F1c2UgdGhlICJ1bm1hbmFnZWQgbmV0d29ya3MiIGNvbnNpZGVyYXRpb25z
IHdlcmUgYmVpbmcgYWRkZWQgdG8gYSBzaW5nbGUgZG9jdW1lbnQgdGhhdCBhbHJlYWR5IGRlc2Ny
aWJlZCAibWFuYWdlZCBuZXR3b3JrcyIgY29uc2lkZXJhdGlvbnMuDQoNClByZXR0eSBtdWNoIGV2
ZXJ5IGNvbnZlcnNhdGlvbiBJIHdhcyBpbnZvbHZlZCBpbiBhdCBRVUlDIGNoYXJ0ZXIgdGltZSBh
c3N1bWVkIHRoYXQgd2Ugd291bGQgd2FudCB0byBzd2FwIHJlY292ZXJ5IGZ1bmN0aW9uYWxpdHkg
aW4gYW5kIG91dCBvdmVyIHRpbWUgd2l0aG91dCByZW9wZW5pbmcgZHJhZnQtaWV0Zi1xdWljLXRy
YW5zcG9ydCwgc28gaGF2aW5nIGEgc2VwYXJhdGUgcmVjb3ZlcnkgZG9jdW1lbnQgd2FzIHRoZSBy
aWdodCB0aGluZyB0byBkby4NCg0KQmVjYXVzZSBRVUlDIGFscmVhZHkgaGFzIGEgc2VwYXJhdGUg
InNhZmUgZm9yIHVubWFuYWdlZCBuZXR3b3JrcyIgcmVjb3ZlcnkgZG9jdW1lbnQsIEkgdGhpbmsg
cHV0dGluZyBvdGhlciByZWNvdmVyeSBzdHJhdGVnaWVzIGluIHNlcGFyYXRlIGRvY3VtZW50cyBp
cyBhIGZpbmUgcGxhbi4NCg0KRG9lcyB0aGF0IG1ha2Ugc2Vuc2U/DQoNCkJlc3QsDQoNClNwZW5j
ZXINCg0KT24gVGh1LCBKdWwgMTYsIDIwMjAgYXQgMjoxOCBQTSBTcGVuY2VyIERhd2tpbnMgYXQg
SUVURiA8c3BlbmNlcmRhd2tpbnMuaWV0ZkBnbWFpbC5jb208bWFpbHRvOnNwZW5jZXJkYXdraW5z
LmlldGZAZ21haWwuLmNvbT4+IHdyb3RlOg0KSGksIElhbiwNCg0KT24gVGh1LCBKdWwgMTYsIDIw
MjAgYXQgMjoyMiBQTSBJYW4gU3dldHQgPGlhbnN3ZXR0PTQwZ29vZ2xlLmNvbUBkbWFyYy5pZXRm
Lm9yZzxtYWlsdG86NDBnb29nbGUuY29tQGRtYXJjLmlldGYub3JnPj4gd3JvdGU6DQpUaGFua3Mg
Zm9yIHRoZSBjb21tZW50cywgSSBmaWxlZCAjMzkxODxodHRwczovL2dpdGh1Yi4uY29tL3F1aWN3
Zy9iYXNlLWRyYWZ0cy9pc3N1ZXMvMzkxOD4gYW5kICMzOTE5PGh0dHBzOi8vbmFtMDYuc2FmZWxp
bmtzLnByb3RlY3Rpb24ub3V0bG9vay5jb20vP3VybD1odHRwcyUzQSUyRiUyRmdpdGh1Yi5jb20l
MkZxdWljd2clMkZiYXNlLWRyYWZ0cyUyRmlzc3VlcyUyRjM5MTkmZGF0YT0wMiU3QzAxJTdDcHJh
dmIlNDBtaWNyb3NvZnQuY29tJTdDM2FlYzRjZGE3NTBkNDliOGE3ZWYwOGQ4MmE0YmY1NTElN0M3
MmY5ODhiZjg2ZjE0MWFmOTFhYjJkN2NkMDExZGI0NyU3QzElN0MwJTdDNjM3MzA1ODUzMDE2NTcw
MzQ2JnNkYXRhPWFrektlbUJTMXcyQVNOdXFmaENmWGpWMFBqa210V0puRDNOS20lMkZXTCUyQkpn
JTNEJnJlc2VydmVkPTA+DQoNCkZvciBteSBiYWNrZ3JvdW5kLCBhcmUgeW91IGF3YXJlIG90aGVy
IHRyYW5zcG9ydCBSRkNzIGhhdmUgbm9ybWF0aXZlIHN0YXRlbWVudHMgdGhhdCBvbmx5IGFwcGx5
IHRvIHRoZSBwdWJsaWMgaW50ZXJuZXQ/DQoNClR1bm5lbHMgYXJlIHRyYW5zcG9ydCwgcmlnaHQ/
IDotKQ0KDQpUaGUgZWFybGllc3QgUkZDIEkgd2FzIGludm9sdmVkIHdpdGgsIHRoYXQgbWFkZSBk
aXN0aW5jdGlvbnMgYWJvdXQgd2hhdCB5b3UgY2FuIGdldCBhd2F5IHdpdGggb24gdGhlIHB1Ymxp
YyBpbnRlcm5ldCB2ZXJzdXMgaW4gYSBtYW5hZ2VkIG5ldHdvcmssIHdhcyBodHRwczovL3Rvb2xz
LmlldGYub3JnL2h0bWwvcmZjNzUxMCNzZWN0aW9uLTU8aHR0cHM6Ly9uYW0wNi5zYWZlbGlua3Mu
cHJvdGVjdGlvbi5vdXRsb29rLmNvbS8/dXJsPWh0dHBzJTNBJTJGJTJGdG9vbHMuaWV0Zi5vcmcl
MkZodG1sJTJGcmZjNzUxMCUyM3NlY3Rpb24tNSZkYXRhPTAyJTdDMDElN0NwcmF2YiU0MG1pY3Jv
c29mdC5jb20lN0MzYWVjNGNkYTc1MGQ0OWI4YTdlZjA4ZDgyYTRiZjU1MSU3QzcyZjk4OGJmODZm
MTQxYWY5MWFiMmQ3Y2QwMTFkYjQ3JTdDMSU3QzAlN0M2MzczMDU4NTMwMTY1ODAzNDEmc2RhdGE9
eVMyWENPTlIzbFp4MTBtZmFqV2JwcENEeXRFMkRNMVk1UWM0cjV1SXl2MCUzRCZyZXNlcnZlZD0w
Pi4gVGhpcyB3YXMgbmVnb3RpYXRlZCBhZnRlciBhIGZhaXJseSB2aWdvcm91cyBiYWNrLWFuZC1m
b3J0aCBiZXR3ZWVuIHRyYW5zcG9ydCBwZW9wbGUgYW5kIG5vbi10cmFuc3BvcnQgcGVvcGxlIGR1
cmluZyBJRVRGIExhc3QgQ2FsbC4NCg0KV2UgcHV0IHRvZ2V0aGVyIGEgZGVzaWduIHRlYW0gd2l0
aCBhIGZldyBwZW9wbGUgdG8gdHJ5IHRvIHdvcmsgdGhyb3VnaCB0aGlzIGZvciB0aGUgbXlyaWFk
IG90aGVyIHByb3RvY29scyB0aGF0IHBlb3BsZSB3YW50ZWQgdG8gdHVubmVsIG92ZXIgVURQLCBv
bmNlIGFuZCBmb3IgYWxsLg0KDQpodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvcmZjODA4NDxo
dHRwczovL25hbTA2LnNhZmVsaW5rcy5wcm90ZWN0aW9uLm91dGxvb2suY29tLz91cmw9aHR0cHMl
M0ElMkYlMkZ0b29scy5pZXRmLm9yZyUyRmh0bWwlMkZyZmM4MDg0JmRhdGE9MDIlN0MwMSU3Q3By
YXZiJTQwbWljcm9zb2Z0LmNvbSU3QzNhZWM0Y2RhNzUwZDQ5YjhhN2VmMDhkODJhNGJmNTUxJTdD
NzJmOTg4YmY4NmYxNDFhZjkxYWIyZDdjZDAxMWRiNDclN0MxJTdDMCU3QzYzNzMwNTg1MzAxNjU4
MDM0MSZzZGF0YT1HT1RKb2JKQzc0ZWVwc29sdExZRHNzRnU0JTJGRThNMUM5N20xNzNKSHdkSDAl
M0QmcmVzZXJ2ZWQ9MD4gd2FzIHB1Ymxpc2hlZCBhcyBhIEJDUC4NCg0KSSBtYXkgYmUgZm9yZ2V0
dGluZyBvdGhlciBzdHVmZiwgb2YgY291cnNlLg0KDQpCZXN0LA0KDQpTcGVuY2VyDQoNCkFsc28s
IGlmIHlvdSdyZSB0aGF0IHdlbGwgYnVmZmVyZWQgYW5kIHRoZSBidXJzdHMgYXJlIHRoYXQgbGFy
Z2UsIGRvIHlvdSBzdGlsbCBzdGFydCB3aXRoIElXMTAsIG9yIGRvIHlvdSBzdGFydCB3aXRoIGEg
bGFyZ2VyIHdpbmRvdz8NCg0KVGhhbmtzLCBJYW4NCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDEx
IDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGluOw0KCWZvbnQtc2l6ZTox
MS4wcHQ7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7fQ0KYTpsaW5rLCBzcGFu
Lk1zb0h5cGVybGluaw0KCXttc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJY29sb3I6Ymx1ZTsNCgl0
ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnNwYW4uRW1haWxTdHlsZTIyDQoJe21zby1zdHls
ZS10eXBlOnBlcnNvbmFsLWNvbXBvc2U7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2Vy
aWY7DQoJY29sb3I6d2luZG93dGV4dDt9DQouTXNvQ2hwRGVmYXVsdA0KCXttc28tc3R5bGUtdHlw
ZTpleHBvcnQtb25seTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjt9DQpAcGFn
ZSBXb3JkU2VjdGlvbjENCgl7c2l6ZTo4LjVpbiAxMS4waW47DQoJbWFyZ2luOjEuMGluIDEuMGlu
IDEuMGluIDEuMGluO30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0K
LS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpl
eHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0
ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6
ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0t
Pg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRU4tVVMiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUi
Pg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkFGQUlD
VCB0aGVyZSBpcyBubyBSRkMgZm9yIFRDUCB0aGF0IGxpbWl0cyBidXJzdCBzaXplcyBpbiBnZW5l
cmFsLiBJIGRvbuKAmXQgdGhpbmsgd2UgbmVlZCB0byBzcGVjaWFsIGNhc2UgSW50ZXJuZXQgYW5k
IERDIG5ldHdvcmtzLiBDaGFuZ2luZyB0aGUgbGFuZ3VhZ2UgZnJvbSBhIE1VU1QgdG8gYSBTSE9V
TEQgaXMgc3VmZmljaWVudCBoZXJlLiBJdCBsZWF2ZXMgZW5vdWdoIHdpZ2dsZSByb29tIGZvciBk
ZXBsb3ltZW50cw0KIGFuZCBleHBlcmltZW50YXRpb24uIDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5JIGRvbuKAmXQgc2VlIHRvbyBtYW55IG90aGVyIGNoYW5nZXMgbmVlZGVkIGluIHJlY292ZXJ5
IGRyYWZ0IGZvciBEQyBlbnZpcm9ubWVudCBwYXJ0aWN1bGFybHkgbm93IHRoYXQgdGhlcmUgaXMg
bm8gbWluIHJ0by4gSmFuYSwgd2hhdCBvdGhlciBjaGFuZ2VzIGRvIHlvdSBoYXZlIGluIG1pbmQ/
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6c29saWQgI0UxRTFFMSAxLjBw
dDtwYWRkaW5nOjMuMHB0IDBpbiAwaW4gMGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPkZy
b206PC9iPiBTcGVuY2VyIERhd2tpbnMgYXQgSUVURiAmbHQ7c3BlbmNlcmRhd2tpbnMuaWV0ZkBn
bWFpbC5jb20mZ3Q7DQo8YnI+DQo8Yj5TZW50OjwvYj4gRnJpZGF5LCBKdWx5IDE3LCAyMDIwIDU6
MjEgQU08YnI+DQo8Yj5Ubzo8L2I+IEphbmEgSXllbmdhciAmbHQ7anJpLmlldGZAZ21haWwuY29t
Jmd0Ozxicj4NCjxiPkNjOjwvYj4gSWFuIFN3ZXR0ICZsdDtpYW5zd2V0dEBnb29nbGUuY29tJmd0
OzsgUHJhdmVlbiBCYWxhc3VicmFtYW5pYW4gJmx0O3ByYXZiQG1pY3Jvc29mdC5jb20mZ3Q7OyBH
b3JyeSBGYWlyaHVyc3QgJmx0O2dvcnJ5QGVyZy5hYmRuLmFjLnVrJmd0OzsgSUVURiBRVUlDIFdH
ICZsdDtxdWljQGlldGYub3JnJmd0OzsgTmVhbCBDYXJkd2VsbCAmbHQ7bmNhcmR3ZWxsQGdvb2ds
ZS5jb20mZ3Q7OyBZdWNodW5nIENoZW5nICZsdDt5Y2hlbmdAZ29vZ2xlLmNvbSZndDs8YnI+DQo8
Yj5TdWJqZWN0OjwvYj4gUmU6IFtFWFRFUk5BTF0gUmU6IFdHTEMgcmV2aWV3IG9mIGRyYWZ0LWll
dGYtcXVpYy1yZWNvdmVyeS0yOTxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+SGksIEphbmEsJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5PbiBUaHUsIEp1bCAxNiwgMjAyMCBhdCA4OjMwIFBNIEphbmEgSXllbmdh
ciAmbHQ7PGEgaHJlZj0ibWFpbHRvOmpyaS5pZXRmQGdtYWlsLmNvbSI+anJpLmlldGZAZ21haWwu
LmNvbTwvYT4mZ3Q7IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBz
dHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5n
OjBpbiAwaW4gMGluIDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPkF0IGEgaGlnaCBsZXZlbCwgdGhlIHJlY292ZXJ5
IGRvYyBpcyBfbm90XyB3cml0dGVuIHdpdGggREMgZW52aXJvbm1lbnRzIGluIG1pbmQuIFdlIGNh
biBtYWtlIHRoYXQgY2xlYXIgaW4gdGhlIGRvY3VtZW50LCBpZiB0aGF0IGhlbHBzLiBUaGVyZSBh
cmUgb3RoZXIgdGhpbmdzIGFzIHdlbGwgdGhhdCB3b24ndCB3b3JrIHdlbGwgaW4gYSBEQyBlbnZp
cm9ubWVudCwgYW5kIEkgaW1hZ2luZSBhIHNlcGFyYXRlIGRvYw0KIHdvdWxkIGJlIGhlbHBmdWwg
aGVyZSB0aGF0IHNwZWNpZmllcyBob3cgUVVJQyBvdWdodCB0byBiZSB0dW5lZCBmb3IgRENzLjxv
OnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj5Ud28gdGhpbmdzLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5NeSByZXNwb25zZSB0byBJYW4gd2FzIGp1c3QgYWJvdXQgdGhl
IGhpc3Rvcnkgb2Ygd2hhdCBUU1YgaGFzIGNvbWUgdG8gZXhwZWN0IGZvciBlbmNhcHN1bGF0aW9u
IHByb3RvY29sIGJlaGF2aW9ycyBpbiB0aGUgcGFzdCBoYWxmLWRvemVuIHllYXJzICgmcXVvdDtp
ZiB5b3UgYXJlIGRvaW5nIHN0dWZmIHRoYXQncyBub3Qgc2FmZSBvbiBhbiB1bm1hbmFnZWQgbmV0
d29yaywgdGhpcyBpcyB3aGF0IHlvdSBzaG91bGQgZG87DQogaWYgeW91J3JlIGRvaW5nIHRoZSBz
YW1lIHRoaW5nIG9uIGEgbWFuYWdlZCBuZXR3b3JrLCB0aGlzIGlzIHdoYXQgeW91IGNhbiBwcm9i
YWJseSBnZXQgYXdheSB3aXRoLCBhbmQgcGxlYXNlIHBvaW50IHRvIHlvdXIgY2lyY3VpdCBicmVh
a2VyIGZ1bmN0aW9uYWxpdHkgaW4gY2FzZSB3aGF0IHlvdSdyZSBkb2luZyB0dXJucyBvdXQgdG8g
YmUgYSBSZWFsbHkgQmFkIElkZWEmcXVvdDsgLSBwYXJhcGhyYXNpbmcgb3ZlciBhIGxvdCBvZiBz
dWJ0aWx0eSkuJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPlRob3NlIGRvY3VtZW50cyB0ZW5kZWQgdG8gaGF2ZSBib3RoIGNhc2VzIGlu
IGEgc2luZ2xlIGRvY3VtZW50LCBhbG9uZyB3aXRoIHRoZSByZXN0IG9mIHRoZSBlbmNhcHN1bGF0
aW9uIHByb3RvY29sLCBpbiBtYW55IGNhc2VzIGJlY2F1c2UgdGhlICZxdW90O3VubWFuYWdlZCBu
ZXR3b3JrcyZxdW90OyBjb25zaWRlcmF0aW9ucyB3ZXJlIGJlaW5nIGFkZGVkIHRvIGEgc2luZ2xl
IGRvY3VtZW50IHRoYXQgYWxyZWFkeSBkZXNjcmliZWQNCiAmcXVvdDttYW5hZ2VkIG5ldHdvcmtz
JnF1b3Q7IGNvbnNpZGVyYXRpb25zLiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5QcmV0dHkgbXVjaCBldmVyeSBjb252ZXJzYXRpb24g
SSB3YXMgaW52b2x2ZWQgaW4gYXQgUVVJQyBjaGFydGVyIHRpbWUgYXNzdW1lZCB0aGF0IHdlIHdv
dWxkIHdhbnQgdG8gc3dhcCByZWNvdmVyeSBmdW5jdGlvbmFsaXR5IGluIGFuZCBvdXQgb3ZlciB0
aW1lIHdpdGhvdXQgcmVvcGVuaW5nIGRyYWZ0LWlldGYtcXVpYy10cmFuc3BvcnQsIHNvIGhhdmlu
ZyBhIHNlcGFyYXRlIHJlY292ZXJ5IGRvY3VtZW50IHdhcw0KIHRoZSByaWdodCB0aGluZyB0byBk
by4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+QmVjYXVzZSBRVUlDIGFscmVhZHkgaGFzIGEgc2VwYXJhdGUgJnF1b3Q7c2FmZSBmb3Ig
dW5tYW5hZ2VkIG5ldHdvcmtzJnF1b3Q7IHJlY292ZXJ5IGRvY3VtZW50LCBJIHRoaW5rIHB1dHRp
bmcgb3RoZXIgcmVjb3Zlcnkgc3RyYXRlZ2llcyBpbiBzZXBhcmF0ZSBkb2N1bWVudHMgaXMgYSBm
aW5lIHBsYW4uJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPkRvZXMgdGhhdCBtYWtlIHNlbnNlPzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rp
dj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5CZXN0LDxvOnA+PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8
L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5TcGVuY2VyPG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNv
bGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0
LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+T24gVGh1LCBKdWwgMTYsIDIwMjAgYXQgMjoxOCBQTSBTcGVuY2VyIERhd2tpbnMgYXQgSUVU
RiAmbHQ7PGEgaHJlZj0ibWFpbHRvOnNwZW5jZXJkYXdraW5zLmlldGZAZ21haWwuLmNvbSIgdGFy
Z2V0PSJfYmxhbmsiPnNwZW5jZXJkYXdraW5zLmlldGZAZ21haWwuY29tPC9hPiZndDsgd3JvdGU6
PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3RlIHN0eWxlPSJib3JkZXI6bm9uZTti
b3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRpbmc6MGluIDBpbiAwaW4gNi4wcHQ7
bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBpbiI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPkhpLCBJYW4sJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBUaHUsIEp1bCAxNiwgMjAyMCBhdCAyOjIyIFBNIElhbiBT
d2V0dCAmbHQ7aWFuc3dldHQ9PGEgaHJlZj0ibWFpbHRvOjQwZ29vZ2xlLmNvbUBkbWFyYy5pZXRm
Lm9yZyIgdGFyZ2V0PSJfYmxhbmsiPjQwZ29vZ2xlLmNvbUBkbWFyYy5pZXRmLm9yZzwvYT4mZ3Q7
IHdyb3RlOjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVy
Om5vbmU7Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBpbiAwaW4gMGlu
IDYuMHB0O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowaW4iPg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPlRoYW5rcyBmb3IgdGhlIGNvbW1lbnRzLCBJIGZpbGVkIDxhIGhyZWY9
Imh0dHBzOi8vZ2l0aHViLi5jb20vcXVpY3dnL2Jhc2UtZHJhZnRzL2lzc3Vlcy8zOTE4IiB0YXJn
ZXQ9Il9ibGFuayI+DQojMzkxODwvYT4gYW5kIDxhIGhyZWY9Imh0dHBzOi8vbmFtMDYuc2FmZWxp
bmtzLnByb3RlY3Rpb24ub3V0bG9vay5jb20vP3VybD1odHRwcyUzQSUyRiUyRmdpdGh1Yi5jb20l
MkZxdWljd2clMkZiYXNlLWRyYWZ0cyUyRmlzc3VlcyUyRjM5MTkmYW1wO2RhdGE9MDIlN0MwMSU3
Q3ByYXZiJTQwbWljcm9zb2Z0LmNvbSU3QzNhZWM0Y2RhNzUwZDQ5YjhhN2VmMDhkODJhNGJmNTUx
JTdDNzJmOTg4YmY4NmYxNDFhZjkxYWIyZDdjZDAxMWRiNDclN0MxJTdDMCU3QzYzNzMwNTg1MzAx
NjU3MDM0NiZhbXA7c2RhdGE9YWt6S2VtQlMxdzJBU051cWZoQ2ZYalYwUGprbXRXSm5EM05LbSUy
RldMJTJCSmclM0QmYW1wO3Jlc2VydmVkPTAiIHRhcmdldD0iX2JsYW5rIj4NCiMzOTE5PC9hPiZu
YnNwOzxvOnA+PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Rm9yIG15
IGJhY2tncm91bmQsIGFyZSB5b3UmbmJzcDthd2FyZSBvdGhlciB0cmFuc3BvcnQgUkZDcyBoYXZl
IG5vcm1hdGl2ZSBzdGF0ZW1lbnRzIHRoYXQgb25seSBhcHBseSB0byB0aGUgcHVibGljIGludGVy
bmV0PyZuYnNwOw0KPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9ibG9ja3F1b3Rl
Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9k
aXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+VHVubmVscyBhcmUgdHJhbnNwb3J0LCBy
aWdodD8gOi0pPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPlRoZSBlYXJsaWVzdCBSRkMgSSB3YXMgaW52b2x2ZWQgd2l0aCwgdGhhdCBtYWRlIGRp
c3RpbmN0aW9ucyBhYm91dCB3aGF0IHlvdSBjYW4gZ2V0IGF3YXkgd2l0aCBvbiB0aGUgcHVibGlj
IGludGVybmV0IHZlcnN1cyBpbiBhIG1hbmFnZWQgbmV0d29yaywgd2FzJm5ic3A7PGEgaHJlZj0i
aHR0cHM6Ly9uYW0wNi5zYWZlbGlua3MucHJvdGVjdGlvbi5vdXRsb29rLmNvbS8/dXJsPWh0dHBz
JTNBJTJGJTJGdG9vbHMuaWV0Zi5vcmclMkZodG1sJTJGcmZjNzUxMCUyM3NlY3Rpb24tNSZhbXA7
ZGF0YT0wMiU3QzAxJTdDcHJhdmIlNDBtaWNyb3NvZnQuY29tJTdDM2FlYzRjZGE3NTBkNDliOGE3
ZWYwOGQ4MmE0YmY1NTElN0M3MmY5ODhiZjg2ZjE0MWFmOTFhYjJkN2NkMDExZGI0NyU3QzElN0Mw
JTdDNjM3MzA1ODUzMDE2NTgwMzQxJmFtcDtzZGF0YT15UzJYQ09OUjNsWngxMG1mYWpXYnBwQ0R5
dEUyRE0xWTVRYzRyNXVJeXYwJTNEJmFtcDtyZXNlcnZlZD0wIiB0YXJnZXQ9Il9ibGFuayI+aHR0
cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzc1MTAjc2VjdGlvbi01PC9hPi4NCiBUaGlzIHdh
cyBuZWdvdGlhdGVkIGFmdGVyIGEgZmFpcmx5IHZpZ29yb3VzIGJhY2stYW5kLWZvcnRoIGJldHdl
ZW4gdHJhbnNwb3J0IHBlb3BsZSBhbmQgbm9uLXRyYW5zcG9ydCBwZW9wbGUgZHVyaW5nIElFVEYg
TGFzdCBDYWxsLiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5XZSBwdXQgdG9nZXRoZXIgYSBkZXNpZ24gdGVhbSB3aXRoIGEgZmV3IHBl
b3BsZSB0byB0cnkgdG8gd29yayB0aHJvdWdoIHRoaXMgZm9yIHRoZSBteXJpYWQgb3RoZXIgcHJv
dG9jb2xzIHRoYXQgcGVvcGxlIHdhbnRlZCB0byB0dW5uZWwgb3ZlciBVRFAsIG9uY2UgYW5kIGZv
ciBhbGwuJm5ic3A7PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxhIGhyZWY9Imh0dHBzOi8vbmFtMDYuc2FmZWxpbmtzLnByb3RlY3Rpb24ub3V0
bG9vay5jb20vP3VybD1odHRwcyUzQSUyRiUyRnRvb2xzLmlldGYub3JnJTJGaHRtbCUyRnJmYzgw
ODQmYW1wO2RhdGE9MDIlN0MwMSU3Q3ByYXZiJTQwbWljcm9zb2Z0LmNvbSU3QzNhZWM0Y2RhNzUw
ZDQ5YjhhN2VmMDhkODJhNGJmNTUxJTdDNzJmOTg4YmY4NmYxNDFhZjkxYWIyZDdjZDAxMWRiNDcl
N0MxJTdDMCU3QzYzNzMwNTg1MzAxNjU4MDM0MSZhbXA7c2RhdGE9R09USm9iSkM3NGVlcHNvbHRM
WURzc0Z1NCUyRkU4TTFDOTdtMTczSkh3ZEgwJTNEJmFtcDtyZXNlcnZlZD0wIiB0YXJnZXQ9Il9i
bGFuayI+aHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL3JmYzgwODQ8L2E+DQogd2FzIHB1Ymxp
c2hlZCBhcyBhIEJDUC4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCI+SSBtYXkgYmUgZm9yZ2V0dGluZyBvdGhlciBzdHVmZiwgb2YgY291
cnNlLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5CZXN0LDxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj5TcGVuY2VyPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9
ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4g
MGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGluIj4NCjxkaXY+
DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+QWxzbywgaWYgeW91J3JlIHRoYXQgd2VsbCBi
dWZmZXJlZCBhbmQgdGhlIGJ1cnN0cyBhcmUgdGhhdCBsYXJnZSwgZG8geW91IHN0aWxsIHN0YXJ0
IHdpdGggSVcxMCwgb3IgZG8geW91IHN0YXJ0IHdpdGggYSBsYXJnZXIgd2luZG93PzxvOnA+PC9v
OnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8
L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGFua3MsIElh
bjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9k
aXY+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_CH2PR00MB0726A8F0BFBED6702448AC40B67C0CH2PR00MB0726namp_--


From nobody Fri Jul 17 13:21:10 2020
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 C61673A08AC for <quic@ietfa.amsl.com>; Fri, 17 Jul 2020 13:21:08 -0700 (PDT)
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, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, HTTPS_HTTP_MISMATCH=0.1, 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 25cxZcZfOr-D for <quic@ietfa.amsl.com>; Fri, 17 Jul 2020 13:21:06 -0700 (PDT)
Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) (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 7D4983A08AA for <quic@ietf.org>; Fri, 17 Jul 2020 13:21:06 -0700 (PDT)
Received: by mail-yb1-xb2d.google.com with SMTP id a15so5073137ybs.8 for <quic@ietf.org>; Fri, 17 Jul 2020 13:21:06 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=dX02mvPdYkAkjpAYR7TQ6tosnPq8xWr7F5E+dDBAnXI=; b=P8vq0cPvZienO6YSkfx5DoQu2Jk36tw6VDdNYPu0lS2tyUJP156HhqFpoFJ4wa0RkN 5kAZLEXSFUcivHdI+LlmBxNbCHojBrWJ7L7Y1Pq2bqWJmR5xonSKTEXEW5kD1YG59DkM QiQfGS2W4FPrrPC51n+uh+p5lTbwMfwbMHSZKoeYdweNoXPHqcY/mE97QtC8ajFuKEgg TH9RBIT6NAn0+mgavPEqOUQIr8G2ReWzT9SmQEgR1CpwpxN1U16CSew7iZnKyctk4MyI RejEZIQhAKJM6fONUr34YmsNNc1EQhWJRnPFuccr3kSRXw7AJOCxW3GS5JKNUpP1rThc EQFQ==
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=dX02mvPdYkAkjpAYR7TQ6tosnPq8xWr7F5E+dDBAnXI=; b=fGtzJ7Uqt0Ui0fo84R/TH66Fy17deRouBH3KOU/DdK5EfhUS3vGDi3ZqeUi5UzrQF4 O4o++FUAG515kprcgIJFP4smQ9tjLJdIot22sDnso3zc9YBnpBfefVYHslsaeOPulam4 lLw1jxGm7wR+XKqs3cJjut/6p2WE7QULOJxMQg9ttvMT6tdEyhMKSo4ayqW/fom0uaAz 3j+KN4EqPNrdS2HwjKmhPE7K3tHO6gTkfAaxVpYox7TZJJ9/pZbB3xCh+EJb8c6UhLan GMl8Jb/M6RWN9fSuHR7sAdUnYDdjyJfLKGhf9kNrRrXExMpxxmMr1xy1cMVd7c+IshMM RkDw==
X-Gm-Message-State: AOAM531mXST5o9HHcvEy2aSfeFE5xazsHtd/zrWJpCgRjxSYKxI764C1 T4Jv2PF/23RC7IR/8AE779fJbdTVzUg7aC+ZxfEJlg==
X-Google-Smtp-Source: ABdhPJzLIkadYUWFjRuz4fK3NvANOvgT9GZCQIiwdiSHdwHhJwoMwQhGEh9ZVnY9AsD/OmBZrQ7OQQSpcpJro/939qg=
X-Received: by 2002:a25:468b:: with SMTP id t133mr17337834yba.77.1595017265173;  Fri, 17 Jul 2020 13:21:05 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <53187d65-f7b9-b99a-f68b-b267303ab399@erg.abdn.ac.uk> <CH2PR00MB0726D18611EC030BF548CA0DB6640@CH2PR00MB0726.namprd00.prod.outlook.com> <40818629-e1dc-f0f1-6173-984a8166c7c2@erg.abdn.ac.uk> <CH2PR00MB07267EBAC2BB08CCE5160EC6B6650@CH2PR00MB0726.namprd00.prod.outlook.com> <CAKcm_gN=vizG9+kiRiX7BAfcsR1p+Q1FrTtNPXfV5vFATBNQ9Q@mail.gmail.com> <CAKKJt-c-sp=L7j5--aoEEObMjhcnTE7YVK_NE4YQFGZDtcLhrA@mail.gmail.com> <CACpbDcfrVNtDb3htqnkVqr2OOskUVr_aYTrRvssT_tAgTKqV_g@mail.gmail.com> <CAKKJt-f76tVoUiAwZrfyOEDG1FPTqbxu0Zg_Or_OymRwaNAwcw@mail.gmail.com> <CH2PR00MB0726A8F0BFBED6702448AC40B67C0@CH2PR00MB0726.namprd00.prod.outlook.com>
In-Reply-To: <CH2PR00MB0726A8F0BFBED6702448AC40B67C0@CH2PR00MB0726.namprd00.prod.outlook.com>
From: Ian Swett <ianswett@google.com>
Date: Fri, 17 Jul 2020 16:20:53 -0400
Message-ID: <CAKcm_gOSEcXxRcPx9zkiN2Aupp1A-qMyc6wP4rvdaxpnTijteQ@mail.gmail.com>
Subject: Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
To: Praveen Balasubramanian <pravb@microsoft.com>
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Jana Iyengar <jri.ietf@gmail.com>,  Gorry Fairhurst <gorry@erg.abdn.ac.uk>, IETF QUIC WG <quic@ietf.org>,  Neal Cardwell <ncardwell@google.com>, Yuchung Cheng <ycheng@google.com>
Content-Type: multipart/alternative; boundary="00000000000080ce4705aaa8e538"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/LGcVdAEoz725MbzIEp2aFgh347I>
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, 17 Jul 2020 20:21:09 -0000

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

Thanks for the follow up comments and the excellent example Spencer.

Praveen, I agree that QUIC shouldn't require as many DC specific changes as
TCP, given it explicitly communicates max_ack_delay and there's no min RTO.

It seems there at least 4 options
1) Do nothing
2) Do nothing, but add a note that if you're on a managed network, some
requirements might not hold.
3) Change the MUST to a SHOULD
4) Use Neal's text or some variation thereof: "Implementations MUST either
use pacing or another method to limit such bursts. It is RECOMMENDED that
traffic over the public Internet limit bursts to the initial congestion
window; see Section 7.2."

I support softening this text some, given Linux today will burst well more
than 10 packets at once if the bandwidth is high enough.  Realistically, to
hit 1Gbps on a 5G network with QUIC, one might have to have bursts larger
than 10 packets, so I'm not sure this is only a DC issue.

I don't like the idea of saying you can change anything in the recovery doc
if you're on a managed network.  Obviously one can, but I'd be concerned
what might result.  Changing the MUST to a SHOULD is easy, but doesn't
provide any guidance on when it's ok to violate.  I'm hesitant to make a
distinction between public and private networks, partially because I do
think there are or will be valid cases for larger bursts on the public
internet.

I'm leaning towards saying you MUST limit bursts to IW unless the pacing
system can't provide enough sending opportunities to send at the rate
specified by the congestion controller.  Thoughts?

On Fri, Jul 17, 2020 at 12:41 PM Praveen Balasubramanian <
pravb@microsoft.com> wrote:

> AFAICT there is no RFC for TCP that limits burst sizes in general. I don=
=E2=80=99t
> think we need to special case Internet and DC networks. Changing the
> language from a MUST to a SHOULD is sufficient here. It leaves enough
> wiggle room for deployments and experimentation.
>
>
>
> I don=E2=80=99t see too many other changes needed in recovery draft for D=
C
> environment particularly now that there is no min rto. Jana, what other
> changes do you have in mind?
>
>
>
> *From:* Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
> *Sent:* Friday, July 17, 2020 5:21 AM
> *To:* Jana Iyengar <jri.ietf@gmail.com>
> *Cc:* Ian Swett <ianswett@google.com>; Praveen Balasubramanian <
> pravb@microsoft.com>; Gorry Fairhurst <gorry@erg.abdn.ac.uk>; IETF QUIC
> WG <quic@ietf.org>; Neal Cardwell <ncardwell@google.com>; Yuchung Cheng <
> ycheng@google.com>
> *Subject:* Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
>
>
>
> Hi, Jana,
>
>
>
> On Thu, Jul 16, 2020 at 8:30 PM Jana Iyengar <jri.ietf@gmail..com
> <jri.ietf@gmail.com>> wrote:
>
> At a high level, the recovery doc is _not_ written with DC environments i=
n
> mind. We can make that clear in the document, if that helps. There are
> other things as well that won't work well in a DC environment, and I
> imagine a separate doc would be helpful here that specifies how QUIC ough=
t
> to be tuned for DCs.
>
>
>
> Two things.
>
>
>
> My response to Ian was just about the history of what TSV has come to
> expect for encapsulation protocol behaviors in the past half-dozen years
> ("if you are doing stuff that's not safe on an unmanaged network, this is
> what you should do; if you're doing the same thing on a managed network,
> this is what you can probably get away with, and please point to your
> circuit breaker functionality in case what you're doing turns out to be a
> Really Bad Idea" - paraphrasing over a lot of subtilty).
>
>
>
> Those documents tended to have both cases in a single document, along wit=
h
> the rest of the encapsulation protocol, in many cases because the
> "unmanaged networks" considerations were being added to a single document
> that already described "managed networks" considerations.
>
>
>
> Pretty much every conversation I was involved in at QUIC charter time
> assumed that we would want to swap recovery functionality in and out over
> time without reopening draft-ietf-quic-transport, so having a separate
> recovery document was the right thing to do.
>
>
>
> Because QUIC already has a separate "safe for unmanaged networks" recover=
y
> document, I think putting other recovery strategies in separate documents
> is a fine plan.
>
>
>
> Does that make sense?
>
>
>
> Best,
>
>
>
> Spencer
>
>
>
> On Thu, Jul 16, 2020 at 2:18 PM Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com <spencerdawkins.ietf@gmail..com>> wrote:
>
> Hi, Ian,
>
>
>
> On Thu, Jul 16, 2020 at 2:22 PM Ian Swett <ianswett=3D
> 40google.com@dmarc.ietf.org> wrote:
>
> Thanks for the comments, I filed #3918
> <https://github..com/quicwg/base-drafts/issues/3918> and #3919
> <https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgith=
ub.com%2Fquicwg%2Fbase-drafts%2Fissues%2F3919&data=3D02%7C01%7Cpravb%40micr=
osoft.com%7C3aec4cda750d49b8a7ef08d82a4bf551%7C72f988bf86f141af91ab2d7cd011=
db47%7C1%7C0%7C637305853016570346&sdata=3DakzKemBS1w2ASNuqfhCfXjV0PjkmtWJnD=
3NKm%2FWL%2BJg%3D&reserved=3D0>
>
>
>
>
> For my background, are you aware other transport RFCs have normative
> statements that only apply to the public internet?
>
>
>
> Tunnels are transport, right? :-)
>
>
>
> The earliest RFC I was involved with, that made distinctions about what
> you can get away with on the public internet versus in a managed network,
> was https://tools.ietf.org/html/rfc7510#section-5
> <https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Ftool=
s.ietf.org%2Fhtml%2Frfc7510%23section-5&data=3D02%7C01%7Cpravb%40microsoft.=
com%7C3aec4cda750d49b8a7ef08d82a4bf551%7C72f988bf86f141af91ab2d7cd011db47%7=
C1%7C0%7C637305853016580341&sdata=3DyS2XCONR3lZx10mfajWbppCDytE2DM1Y5Qc4r5u=
Iyv0%3D&reserved=3D0>.
> This was negotiated after a fairly vigorous back-and-forth between
> transport people and non-transport people during IETF Last Call.
>
>
>
> We put together a design team with a few people to try to work through
> this for the myriad other protocols that people wanted to tunnel over UDP=
,
> once and for all.
>
>
>
> https://tools.ietf.org/html/rfc8084
> <https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Ftool=
s.ietf.org%2Fhtml%2Frfc8084&data=3D02%7C01%7Cpravb%40microsoft.com%7C3aec4c=
da750d49b8a7ef08d82a4bf551%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637=
305853016580341&sdata=3DGOTJobJC74eepsoltLYDssFu4%2FE8M1C97m173JHwdH0%3D&re=
served=3D0>
> was published as a BCP.
>
>
>
> I may be forgetting other stuff, of course.
>
>
>
> Best,
>
>
>
> Spencer
>
>
>
> Also, if you're that well buffered and the bursts are that large, do you
> still start with IW10, or do you start with a larger window?
>
>
>
> Thanks, Ian
>
>

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

<div dir=3D"ltr">Thanks for the follow up comments and the excellent exampl=
e Spencer.<div><br></div><div>Praveen, I agree that QUIC shouldn&#39;t requ=
ire as many DC specific changes as TCP, given it explicitly communicates ma=
x_ack_delay and there&#39;s no min RTO.</div><div><br></div><div>It seems t=
here at least 4 options</div><div>1) Do nothing</div><div>2) Do nothing, bu=
t add a note that if you&#39;re on a managed network, some requirements mig=
ht not hold.</div><div>3) Change the MUST to a SHOULD</div><div>4) Use Neal=
&#39;s text or some variation thereof: &quot;<span style=3D"color:rgb(36,41=
,46);font-family:-apple-system,system-ui,&quot;Segoe UI&quot;,Helvetica,Ari=
al,sans-serif,&quot;Apple Color Emoji&quot;,&quot;Segoe UI Emoji&quot;;font=
-size:14px">Implementations MUST either use pacing or another method to lim=
it such bursts.=C2=A0</span><span style=3D"color:rgb(36,41,46);font-family:=
-apple-system,system-ui,&quot;Segoe UI&quot;,Helvetica,Arial,sans-serif,&qu=
ot;Apple Color Emoji&quot;,&quot;Segoe UI Emoji&quot;;font-size:14px">It is=
 RECOMMENDED that traffic over the public Internet limit bursts to the init=
ial=C2=A0</span><span style=3D"color:rgb(36,41,46);font-family:-apple-syste=
m,system-ui,&quot;Segoe UI&quot;,Helvetica,Arial,sans-serif,&quot;Apple Col=
or Emoji&quot;,&quot;Segoe UI Emoji&quot;;font-size:14px">congestion window=
; see Section 7.2.&quot;</span></div><div><br></div><div>I support softenin=
g this text some, given Linux today will burst well more than 10 packets at=
 once if the bandwidth is high enough.=C2=A0 Realistically, to hit 1Gbps on=
 a 5G network with QUIC, one might have to have bursts larger than 10 packe=
ts, so I&#39;m not sure this is only a DC issue.</div><div><br></div><div>I=
 don&#39;t like the idea of saying you can change anything in the recovery =
doc if you&#39;re on a managed network.=C2=A0 Obviously one can, but I&#39;=
d be concerned what might result.=C2=A0 Changing the MUST to a SHOULD is ea=
sy, but doesn&#39;t provide any guidance on when it&#39;s ok to violate.=C2=
=A0 I&#39;m hesitant to make a distinction between public and private netwo=
rks, partially because I do think there are or will be valid cases for larg=
er bursts on the public internet.</div><div><br></div><div>I&#39;m leaning =
towards saying you MUST limit bursts to IW unless the pacing system can&#39=
;t provide enough sending opportunities to send at the rate specified by th=
e congestion controller.=C2=A0 Thoughts?</div></div><br><div class=3D"gmail=
_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jul 17, 2020 at 12:41=
 PM Praveen Balasubramanian &lt;<a href=3D"mailto:pravb@microsoft.com">prav=
b@microsoft.com</a>&gt; wrote:<br></div><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">





<div lang=3D"EN-US">
<div class=3D"gmail-m_3324191976835009839WordSection1">
<p class=3D"MsoNormal">AFAICT there is no RFC for TCP that limits burst siz=
es in general. I don=E2=80=99t think we need to special case Internet and D=
C networks. Changing the language from a MUST to a SHOULD is sufficient her=
e. It leaves enough wiggle room for deployments
 and experimentation. <u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">I don=E2=80=99t see too many other changes needed in=
 recovery draft for DC environment particularly now that there is no min rt=
o. Jana, what other changes do you have in mind?<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> Spencer Dawkins at IETF &lt;<a href=3D"=
mailto:spencerdawkins.ietf@gmail.com" target=3D"_blank">spencerdawkins.ietf=
@gmail.com</a>&gt;
<br>
<b>Sent:</b> Friday, July 17, 2020 5:21 AM<br>
<b>To:</b> Jana Iyengar &lt;<a href=3D"mailto:jri.ietf@gmail.com" target=3D=
"_blank">jri.ietf@gmail.com</a>&gt;<br>
<b>Cc:</b> Ian Swett &lt;<a href=3D"mailto:ianswett@google.com" target=3D"_=
blank">ianswett@google.com</a>&gt;; Praveen Balasubramanian &lt;<a href=3D"=
mailto:pravb@microsoft.com" target=3D"_blank">pravb@microsoft.com</a>&gt;; =
Gorry Fairhurst &lt;<a href=3D"mailto:gorry@erg.abdn.ac.uk" target=3D"_blan=
k">gorry@erg.abdn.ac.uk</a>&gt;; IETF QUIC WG &lt;<a href=3D"mailto:quic@ie=
tf.org" target=3D"_blank">quic@ietf.org</a>&gt;; Neal Cardwell &lt;<a href=
=3D"mailto:ncardwell@google.com" target=3D"_blank">ncardwell@google.com</a>=
&gt;; Yuchung Cheng &lt;<a href=3D"mailto:ycheng@google.com" target=3D"_bla=
nk">ycheng@google.com</a>&gt;<br>
<b>Subject:</b> Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-=
29<u></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">Hi, Jana,=C2=A0<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, Jul 16, 2020 at 8:30 PM Jana Iyengar &lt;<a =
href=3D"mailto:jri.ietf@gmail.com" target=3D"_blank">jri.ietf@gmail..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>
<p class=3D"MsoNormal">At a high level, the recovery doc is _not_ written w=
ith DC environments in mind. We can make that clear in the document, if tha=
t helps. There are other things as well that won&#39;t work well in a DC en=
vironment, and I imagine a separate doc
 would be helpful here that specifies how QUIC ought to be tuned for DCs.<u=
></u><u></u></p>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Two things.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">My response to Ian was just about the history of wha=
t TSV has come to expect for encapsulation protocol behaviors in the past h=
alf-dozen years (&quot;if you are doing stuff that&#39;s not safe on an unm=
anaged network, this is what you should do;
 if you&#39;re doing the same thing on a managed network, this is what you =
can probably get away with, and please point to your circuit breaker functi=
onality in case what you&#39;re doing turns out to be a Really Bad Idea&quo=
t; - paraphrasing over a lot of subtilty).=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Those documents tended to have both cases in a singl=
e document, along with the rest of the encapsulation protocol, in many case=
s because the &quot;unmanaged networks&quot; considerations were being adde=
d to a single document that already described
 &quot;managed networks&quot; considerations.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Pretty much every conversation I was involved in at =
QUIC charter time assumed that we would want to swap recovery functionality=
 in and out over time without reopening draft-ietf-quic-transport, so havin=
g a separate recovery document was
 the right thing to do.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Because QUIC already has a separate &quot;safe for u=
nmanaged networks&quot; recovery document, I think putting other recovery s=
trategies in separate documents is a fine plan.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Does that make sense?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Best,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Spencer<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<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">On Thu, Jul 16, 2020 at 2:18 PM Spencer Dawkins at I=
ETF &lt;<a href=3D"mailto:spencerdawkins.ietf@gmail..com" target=3D"_blank"=
>spencerdawkins.ietf@gmail.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, Ian,=C2=A0<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, Jul 16, 2020 at 2:22 PM Ian Swett &lt;ianswe=
tt=3D<a href=3D"mailto:40google.com@dmarc.ietf.org" target=3D"_blank">40goo=
gle.com@dmarc.ietf.org</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>
<p class=3D"MsoNormal">Thanks for the comments, I filed <a href=3D"https://=
github..com/quicwg/base-drafts/issues/3918" target=3D"_blank">
#3918</a> and <a href=3D"https://nam06.safelinks.protection.outlook.com/?ur=
l=3Dhttps%3A%2F%2Fgithub.com%2Fquicwg%2Fbase-drafts%2Fissues%2F3919&amp;dat=
a=3D02%7C01%7Cpravb%40microsoft.com%7C3aec4cda750d49b8a7ef08d82a4bf551%7C72=
f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637305853016570346&amp;sdata=3Dakz=
KemBS1w2ASNuqfhCfXjV0PjkmtWJnD3NKm%2FWL%2BJg%3D&amp;reserved=3D0" target=3D=
"_blank">
#3919</a>=C2=A0<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">For my background, are you=C2=A0aware other transpor=
t RFCs have normative statements that only apply to the public internet?=C2=
=A0
<u></u><u></u></p>
</div>
</div>
</blockquote>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Tunnels are transport, right? :-)<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">The earliest RFC I was involved with, that made dist=
inctions about what you can get away with on the public internet versus in =
a managed network, was=C2=A0<a href=3D"https://nam06.safelinks.protection.o=
utlook.com/?url=3Dhttps%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc7510%23section-5=
&amp;data=3D02%7C01%7Cpravb%40microsoft.com%7C3aec4cda750d49b8a7ef08d82a4bf=
551%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637305853016580341&amp;sda=
ta=3DyS2XCONR3lZx10mfajWbppCDytE2DM1Y5Qc4r5uIyv0%3D&amp;reserved=3D0" targe=
t=3D"_blank">https://tools.ietf.org/html/rfc7510#section-5</a>.
 This was negotiated after a fairly vigorous back-and-forth between transpo=
rt people and non-transport people during IETF Last Call.=C2=A0<u></u><u></=
u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">We put together a design team with a few people to t=
ry to work through this for the myriad other protocols that people wanted t=
o tunnel over UDP, once and for all.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><a href=3D"https://nam06.safelinks.protection.outloo=
k.com/?url=3Dhttps%3A%2F%2Ftools.ietf.org%2Fhtml%2Frfc8084&amp;data=3D02%7C=
01%7Cpravb%40microsoft.com%7C3aec4cda750d49b8a7ef08d82a4bf551%7C72f988bf86f=
141af91ab2d7cd011db47%7C1%7C0%7C637305853016580341&amp;sdata=3DGOTJobJC74ee=
psoltLYDssFu4%2FE8M1C97m173JHwdH0%3D&amp;reserved=3D0" target=3D"_blank">ht=
tps://tools.ietf.org/html/rfc8084</a>
 was published as a BCP.=C2=A0<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">I may be forgetting other stuff, of course.<u></u><u=
></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Best,<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Spencer<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal">=C2=A0<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">Also, if you&#39;re that well buffered and the burst=
s are that large, do you still start with IW10, or do you start with a larg=
er window?<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, Ian<u></u><u></u></p>
</div>
</div>
</blockquote>
</div>
</div>
</blockquote>
</div>
</blockquote>
</div>
</div>
</div>
</div>

</blockquote></div>

--00000000000080ce4705aaa8e538--


From nobody Fri Jul 17 15:07:04 2020
Return-Path: <jgh@wizmail.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 DC4173A0965 for <quic@ietfa.amsl.com>; Fri, 17 Jul 2020 15:07:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, NICE_REPLY_A=-0.001, 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=neutral reason="invalid (unsupported algorithm ed25519-sha256)" header.d=wizmail.org header.b=bWK7dDmC; dkim=pass (2048-bit key) header.d=wizmail.org header.b=O176bHOl
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id ajJF5EHirB5i for <quic@ietfa.amsl.com>; Fri, 17 Jul 2020 15:07:01 -0700 (PDT)
Received: from wizmail.org (wizmail.org [IPv6:2a00:1940:107::2:0:0]) (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 CBBF33A0964 for <quic@ietf.org>; Fri, 17 Jul 2020 15:07:00 -0700 (PDT)
DKIM-Signature: v=1; a=ed25519-sha256; q=dns/txt; c=relaxed/relaxed; d=wizmail.org; s=e202001; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:Autocrypt:From:References:To:Subject :From:Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type :Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:List-Post: List-Owner:List-Archive:Autocrypt; bh=orl28HiufHMIHBVWuOLWx3q2WrF+FfZ6ib46SsAy7bA=; b=bWK7dDmCQagIl6DdJPLNXASNX2 2Fk2AxGnXwB/WYIBxQDcs07GY9GE4m5krjQA/8OlfrmJv5soQRoapLqoDUDQ==;
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=wizmail.org ; s=r202001; h=Content-Transfer-Encoding:Content-Type:In-Reply-To: MIME-Version:Date:Message-ID:Autocrypt:From:References:To:Subject:From:Sender :Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:In-Reply-To: References:List-Id:List-Help:List-Unsubscribe:List-Subscribe:List-Post: List-Owner:List-Archive:Autocrypt; bh=orl28HiufHMIHBVWuOLWx3q2WrF+FfZ6ib46SsAy7bA=; b=O176bHOlM01Y2d/bJ4jmyOZFzF cDW5kAtLUxtOONcvlli1/Av3FUr9Y1SzC5fmsIbQAVlK507RkfGgqRL8iLeH8DiSpPXN+sofSHXiA nKWUscRQGdDy31ObxjLmZl/6d5S303ef/aKfoTpX39gaq981jBTaCQnaNTbTroj2lXB/SqSdZPHnh 9stayzwXXtnyTGCieEIR+gXWTv6ZhSr4MLv6jaDUwIxyFgP6jx+awQiYhIGvgEQWWEdz6kw1pvt9J uBABF6i5hJ3CjNZR9qZCNawM7YPm65UTGtIWRz0qnEji4N0/yB61n8sIhPosnZkOVyUUUJjuTglxJ R39x/TWw==;
Authentication-Results: wizmail.org; iprev=pass (vgate18.wizint.net) smtp.remote-ip=2a00:1940:107::1:2f:0; auth=pass (PLAIN) smtp.auth=jgh@wizmail.org
Received: from vgate18.wizint.net ([2a00:1940:107::1:2f:0] helo=lap.dom.ain) by wizmail.org (Exim 4.94.102) (TLS1.3) tls TLS_AES_128_GCM_SHA256 with esmtpsa id 1jwYVN-00Bgjb-15 for quic@ietf.org (return-path <jgh@wizmail.org>); Fri, 17 Jul 2020 22:06:57 +0000
Subject: Re: WGLC review of draft-ietf-quic-recovery-29
To: quic@ietf.org
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com>
From: Jeremy Harris <jgh@wizmail.org>
Autocrypt: addr=jgh@wizmail.org; prefer-encrypt=mutual; keydata= mQENBFWABsQBCADTFfb9EHGGiDel/iFzU0ag1RuoHfL/09z1y7iQlLynOAQTRRNwCWezmqpD p6zDFOf1Ldp0EdEQtUXva5g2lm3o56o+mnXrEQr11uZIcsfGIck7yV/y/17I7ApgXMPg/mcj ifOTM9C7+Ptghf3jUhj4ErYMFQLelBGEZZifnnAoHLOEAH70DENCI08PfYRRG6lZDB09nPW7 vVG8RbRUWjQyxQUWwXuq4gQohSFDqF4NE8zDHE/DgPJ/yFy+wFr2ab90DsE7vOYb42y95keK tTBp98/Y7/2xbzi8EYrXC+291dwZELMHnYLF5sO/fDcrDdwrde2cbZ+wtpJwtSYPNvVxABEB AAG0JkplcmVteSBIYXJyaXMgKG5vbmUpIDxqZ2hAd2l6bWFpbC5vcmc+iQFOBBMBCAA4FiEE qYbzpr1jd9hzCVjevOWMjOQfMt8FAl4WMuMCGwMFCwkIBwIGFQoJCAsCBBYCAwECHgECF4AA CgkQvOWMjOQfMt946ggAvqDr2jvVnGIN2Njnjl2iiKyw4dYdFzNhZgjTaryiV90BftUDxRsB uTVFUC6XU+B13MEgSK0zRDyI5NpEH+JTW539gWlmz2k2WTTmoBsm/js1ELoAjGr/i32SByqm 0fo3JPctn/lc7oTo0muGYvB5xWhTHRlcT9zGTRUb/6ucabVLiJUrcGhS1OqDGq7nvYQpFZdf Dj7hyyrCKrq6YUPRvoq3aWw/o6aPUN8gmJj+h4pB5dMbbNKm7umz4O3RHWceO9JCGYxfC4uh 0k85bgIVb4wtaljBW90YZRU/5zIjD6r2b6rluY55rLulsyT7xAqe14eE1AlRB1og/s4rUtRf 8LkBDQRVgAbEAQgA6YSx2ik6EbkfxO0x3qwYgow2rcAmhEzijk2Ns0QUKWkN9qfxdlyBi0vA nNu/oK2UikOmV9GTeOzvgBchRxfAx/dCF2RaSUd0W/M4F0/I5y19PAzN9XhAmR50cxYRpTpq ulgFJagdxigj1AmNnOHk0V8qFy7Xk8a1wmKI+Ocv2Jr5Wa5aJwTYzwQMh4jvyzc/le32bTbD ezf1xq5y23HTXzXfkg9RDZmyyfEb8spsYLk8gf5GvSXYxxyKEBCei9eugd4YXwh6bfIgtBj2 ZLYvSDJdDaCdNvYyZtyatahHHhAZ+R+UDBp+hauuIl8E7DtUzDVMKVsfKY71e8FSMYyPGQAR AQABiQEfBBgBAgAJBQJVgAbEAhsMAAoJELzljIzkHzLfTegH/Aktgk6zEBXYZBhLQV5i+Inw /FBxZAUQRpjPGS9n1lAU2V0/Jq3UTDiurXD5ylmgr1ryq9JJ7fe9I/w8gIBZh/IYDot8nLYo BXnFQ444pQHgiTKt/LNbWCmIiw2wXR1rXZAPbh2cKt5X3d0MXBBDt0GpkBfnTu4fIADl5Rvq aPOx5vhNMM+LMCAfPkt+yc68fbrtC0hQ3yQkyvkyChmuVJ/C8T8cqvVp5zQ4e9syuwYkYnZP 7ONCnDaHfNzTOB5/7Gxn8i2vLEtBdzBNEvqHEjDorv2RxzosKS2DW8Eye7LWcRrK4Llnk/T/ mpsWwP2JSveS3nbLcLzflnB2e3fvgK65AQ0EXiRPygEIAMP9Z2LRciWF8OoKUbcnA50W0U60 zTBvb7IMm0Rfaeb+s5vk0bX6Hel8i7dxmQvy0yUBrQq/9NYa90MOcm54b9oETtKHcoe63U3i iZc62ERe5dRIr9EG1DAN3SW5fRc5H234mskCdl06ftOJCsXLL1enbunWF8WYQpn8hzsoQqzs klloqd24z8c/+3C5cPjI26hyGFR0W5Q1T8xBMqxgc5W0smyyqDdDs/H1VXrxfQdculDXkM3B EUkeZMsyT7Q8jr8qHv13T1dPCyObP4wXkaOSEtOcBAeF2B1TUVUEhqPzXbG6+oZWgVUKWB8o oHReboJUCkQC8jAIZrr9xpgCMPMAEQEAAYkBPAQYAQgAJhYhBKmG86a9Y3fYcwlY3rzljIzk HzLfBQJeJE/KAhsMBQkB4TOAAAoJELzljIzkHzLfjg4IAM2GxIUaXLfO22z2JWS3byFvfRNS eXLZx2cDokn8AGpzTY+k5mcCkOQVUUz9MuxM50VnrRuBaeH++LfzSghKRWLx2PdJlKzThyFi y23NagSwx4i/R2J8xiPtajZm5SS3slEg1pt3NhgDkkrTQUTHYcf4F0O3YgdoqGKR7m10jqXz gzwQE65Pb0QUX5clxy55oV1pXoq1qjELIYVH9aS8bpI0RE86axHwpOvG4cQrMWZ0tg1txwZ/ DSstczlx7/Ptxfdd+A0x27UhS7ijUuqXx/z8Vh7U/oj/lsVERXyxuUgojD5kkagRLURuYBef CxJ/k6RTKs8juRsbVGfJMmNdfyK4OAReJFQPEgorBgEEAZdVAQUBAQdAPr/8EgFM8AkB/CZz +BGJIezPAdpTYFLvRhsem2GoBicDAQgHiQE8BBgBCAAmFiEEqYbzpr1jd9hzCVjevOWMjOQf Mt8FAl4kVA8CGwwFCQPCZwAACgkQvOWMjOQfMt99PAgApNBPoJog4UKuiP4YP4vvntA4etz8 z7WzVU4uI2ep7++qEaZOafHlSaUILaGag4CSh7KmxrTUjtoJNeX2qx5AQ4pdlNIjMy/V/Z+z 8gJ5vQ3tXglN4P7S6ud6mYKzpGHCvNF2CdzSRa2DRizCy6+sHOrDiH5V7veKE+9LjF+aB9lw PYLeF6Dh4idnxIa3aVwQjAAn3NBYAuhymnqgLgWcrPNaiSP6VIrsu4aCCoeIuc7bCFks6hrR x805g1J6uxixrMu2bW+AbPpRObi5B0pTJhDaLBW1xQgOiwYIAdyu0H2YNMrCBsA0w40UWEIz xrAkJFP/CS+qkjMI47FKq1EzbQ==
Message-ID: <9f57b20d-2eba-b2b9-d8c8-48e019c8952a@wizmail.org>
Date: Fri, 17 Jul 2020 23:06:56 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com>
Content-Type: text/plain; charset=windows-1252
Content-Language: en-GB
Content-Transfer-Encoding: 7bit
X-Pcms-Received-Sender: vgate18.wizint.net ([2a00:1940:107::1:2f:0] helo=lap.dom.ain) with esmtpsa
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/THNAyFpSXZrw5ck97FhXYkQjFaQ>
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, 17 Jul 2020 22:07:03 -0000

On 08/07/2020 22:29, Praveen Balasubramanian wrote:
> Section 7.9
> "Implementations MUST either use pacing or another method to limit such bursts to the initial congestion window; see Section 7.2."
> This seems to preclude use of segmentation offload of sizes greater than IW.. In datacenters we routinely send bursts that are higher without causing loss. The MUST here seems unnecessary. It also conflicts with the RECOMMENDED in an earlier sentence.

There's a way of satisfying both desires: have the NIC handle the
pacing.
-- 
Cheers,
  Jeremy


From nobody Fri Jul 17 19:18:15 2020
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 1A3313A0420 for <quic@ietfa.amsl.com>; Fri, 17 Jul 2020 19:18:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 iSQt21OuKxKN for <quic@ietfa.amsl.com>; Fri, 17 Jul 2020 19:18:12 -0700 (PDT)
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 1AB893A040F for <quic@ietf.org>; Fri, 17 Jul 2020 19:18:12 -0700 (PDT)
Received: by mail-lj1-x22f.google.com with SMTP id j11so14783827ljo.7 for <quic@ietf.org>; Fri, 17 Jul 2020 19:18:11 -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;  bh=+ePqFNW0DTlHvJUwyunCUhC1xrblWLqYCkGF6ABctm0=; b=MbOjQkyf16YWNnnJCvufy6TvqUIa3tQs0ivBQZu3RzAHynOKlaNstTXR4CFgsiCSMd OWAXT/DljIqht4H2VSiQw+t0XM6pIcQVsp4BUEttkRkAmKA5n8HNDlVsnSxyOA2BePTj lYwyplX7OpxGSgL4LlsZEbRXZ+XL3DaDtudzd0BX/Tr86VgtlJCVcb7Y1T5DHWcsmqfn 9hsfPCHdSfgXILieTPDh9u+IgUA3sDzGjFqVPlO/9SKvyT1s41R+xI88qDTbDvI7/SjI lK2cViqHuZCRv8aUjumISD64hsi+XeQx4tonp2ArKpDAak5KMCc4guyzqg6ghb79O6TW FUtQ==
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=+ePqFNW0DTlHvJUwyunCUhC1xrblWLqYCkGF6ABctm0=; b=XvZiPtoTUlCqk/Si1eyEnj1yhRzu+iDOrrtyIP3AuBluRchUiqI3px5HfuAudU7ZDt MivBWuOnt5O9Eam6y0Cboqzv7H79iMWNe1rjlBpX71hQOwlzSVsjZM9CatnR6oZW1FTk uGEujO8fA3/W+H+sVD6+pXmYERIgMyku0ItXM2c/yQevX0rxGtQnE9q8lop8S3bqEf9Z 5ruGUF4vBds4E2T2wQv4jhD4T+y624ZKc/5HOjtX4O0WUaz8JZvOMV/9br0SwL8S7bZb ZgY623j/sFx5wtLT5baqfQeC4jKm9XKjyzkSVbj1mIyIIyCvnL3vVgV72SF7otjmOYpo kVnQ==
X-Gm-Message-State: AOAM531WW6tzyRenpIpy8W+/7C62e7u6gjExmYoFaBKLcE54C/wSJUtN DKqm7O4zVMR+6WtgKzZYa/wnHPh8RfLjX8ukpeisNg==
X-Google-Smtp-Source: ABdhPJy++7ljd1bVaWDpna5xsETHk91GXN6d6fMgPcCr+lpnNG8l96skEhw7zeQC8CNTRAtD0FyS7WrHyzM+qwRkxIU=
X-Received: by 2002:a05:651c:305:: with SMTP id a5mr5339983ljp.387.1595038689810;  Fri, 17 Jul 2020 19:18:09 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <9f57b20d-2eba-b2b9-d8c8-48e019c8952a@wizmail.org>
In-Reply-To: <9f57b20d-2eba-b2b9-d8c8-48e019c8952a@wizmail.org>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Fri, 17 Jul 2020 19:17:58 -0700
Message-ID: <CACpbDccrpHeP5PYGCZky+AN2gC9YSs5gbAzYr4Yrw1LpvHZNiA@mail.gmail.com>
Subject: Re: WGLC review of draft-ietf-quic-recovery-29
To: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000827b1305aaade200"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/kZ_ZmuzE3HZd9vuNhHcRyEex5-k>
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, 18 Jul 2020 02:18:14 -0000

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

There's a protocol question and there's a question of endpoint behavior. In
terms of the protocol itself, yes, there's no real need to distinguish
between Internet and DC environments; we've tried to ensure that the
protocol can be used broadly. My point was that the constants in the spec
were based on what we believe to be true for the public Internet, and not
for DC environments.

That said, perhaps I was a bit too hasty. IW10 and InitialRTT values are
the others I was thinking about, but those are recommendations in the spec,
not requirements. And as Ian notes, there's no minimum timeout anymore.

Perhaps we can have a principle here: recommendations that are specific for
Internet use are just that, and we use SHOULDs for those. IW10 makes sense
based on this, and I would then also be fine with changing the MUST to a
SHOULD. Perhaps we can state this principle upfront.

Ian, I share your hesitation that we don't want to make a distinction
between private and public networks, but we already allow for
implementations to do that with a different IW and Initial RTT. Is it
different when talking about burst limits?


On Fri, Jul 17, 2020 at 3:07 PM Jeremy Harris <jgh@wizmail.org> wrote:

> On 08/07/2020 22:29, Praveen Balasubramanian wrote:
> > Section 7.9
> > "Implementations MUST either use pacing or another method to limit such
> bursts to the initial congestion window; see Section 7.2."
> > This seems to preclude use of segmentation offload of sizes greater than
> IW.. In datacenters we routinely send bursts that are higher without
> causing loss. The MUST here seems unnecessary. It also conflicts with the
> RECOMMENDED in an earlier sentence.
>
> There's a way of satisfying both desires: have the NIC handle the
> pacing.
> --
> Cheers,
>   Jeremy
>
>

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

<div dir=3D"ltr">There&#39;s a protocol question and there&#39;s a question=
 of endpoint behavior. In terms of the protocol itself, yes, there&#39;s no=
 real need to distinguish between Internet and DC environments; we&#39;ve t=
ried to ensure that the protocol can be used broadly. My point was that the=
 constants=C2=A0in the spec were based on what we believe to be true for th=
e public Internet, and not for DC environments.<div><br></div><div>That sai=
d, perhaps I was a bit too hasty. IW10 and InitialRTT values are the others=
 I was thinking about, but those are=C2=A0recommendations in the spec, not =
requirements. And as Ian notes, there&#39;s no minimum timeout anymore.</di=
v><div><br></div><div>Perhaps we can have a principle here: recommendations=
 that are specific for Internet use are just that, and we use SHOULDs for t=
hose. IW10 makes sense based on this, and I would then also be fine with ch=
anging the MUST to a SHOULD. Perhaps we can state this principle upfront.</=
div><div><br></div><div>Ian, I share your hesitation that we don&#39;t want=
 to make a distinction between private and public networks,=C2=A0but we alr=
eady allow for implementations to do that with a different=C2=A0IW and Init=
ial RTT. Is it different when talking about burst limits?</div><div><br></d=
iv></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_att=
r">On Fri, Jul 17, 2020 at 3:07 PM Jeremy Harris &lt;<a href=3D"mailto:jgh@=
wizmail.org">jgh@wizmail.org</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">On 08/07/2020 22:29, Praveen Balasubramanian wr=
ote:<br>
&gt; Section 7.9<br>
&gt; &quot;Implementations MUST either use pacing or another method to limi=
t such bursts to the initial congestion window; see Section 7.2.&quot;<br>
&gt; This seems to preclude use of segmentation offload of sizes greater th=
an IW.. In datacenters we routinely send bursts that are higher without cau=
sing loss. The MUST here seems unnecessary. It also conflicts with the RECO=
MMENDED in an earlier sentence.<br>
<br>
There&#39;s a way of satisfying both desires: have the NIC handle the<br>
pacing.<br>
-- <br>
Cheers,<br>
=C2=A0 Jeremy<br>
<br>
</blockquote></div>

--000000000000827b1305aaade200--


From nobody Fri Jul 17 20:13:36 2020
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 DE7F93A0924 for <quic@ietfa.amsl.com>; Fri, 17 Jul 2020 20:13:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 1UIpH7nvFWG8 for <quic@ietfa.amsl.com>; Fri, 17 Jul 2020 20:13:33 -0700 (PDT)
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 8D4283A08F3 for <quic@ietf.org>; Fri, 17 Jul 2020 20:13:32 -0700 (PDT)
Received: by mail-lj1-x233.google.com with SMTP id q4so14929158lji.2 for <quic@ietf.org>; Fri, 17 Jul 2020 20:13:32 -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=CNJQkVElSbDIrbF9fPIkyv2+/mOEwov6hrH79LR+ObE=; b=gryvfMbNEyt6BcRMQQuPpJZybKGz4ftL14orlmZO9UaDRIpS+sHdqhQxLrg2NUnu9/ t9M0u3PLdx8zk2F/ynBOnZro3+imIcaVpQ8f5oEg7dqkZasJSqLxbeCaAMUlqpRJzZ/d oeN+t/D37u6Moo0tE2HHulhk0gwXUIxWetSnWZWuBhiHxy9CAYLQBBL4R9/vdl7REdGH Qisuy8ViN6L8nDDMC3nS8S9xLrxVbklB54jbGNlyHK8HYD4xNT8peZNp9nbe4vpTHL/d t7jrmrSl6Ewmd/f0uaYAd1/al7oe5qPwJ/A9m/iTfSfNUZuBN2dIo/FTuGTLyYeLtJ4f MQTw==
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=CNJQkVElSbDIrbF9fPIkyv2+/mOEwov6hrH79LR+ObE=; b=F7mn3rYBiofUtJ9y3dECAOs0uPIsFgL0x2mw0xtpxVfRPqo3Yh3K5gj+mxm+j8ZGcE ZrhUHTrd5lAjU6+jHQy+3zo/DQprrKmJy5PiSYhANZae8QiVrNWNeqxARgVhOsHqCDTQ IQg1jtq7XDOzPC9ZqrYkGtOvzhapZdsjqSPlKF9OwZLfMNOdtPf+k/uyZjAmn/vpQ//g CeZKKT0QlTzSusn21oZREtF+MXuR8HzxYjOj7iQ0FuPFVkjtOIhut1BGUWJwSQ2j4Nvj 6xO25yX51A3k7AjH0MVpPTmXMizXPV18uAjr5n5Gce2cWAO04KSIJgarXa5OBM7LGFQm YF6w==
X-Gm-Message-State: AOAM531dNU0wwmqq/0Ng0gHika55X3tcS5pYbD+VPpKfoaf9/NrYJn/S WdNZBBZ9UtYWJKXtA4hW7GtfvDat8bBAdK4I+j8=
X-Google-Smtp-Source: ABdhPJzHhO5vW+jRGNmMWE68w+QGj2pjVNovfCR0SmFGjzQQZ1kidmdUOviBq7qcMG4s29JkFCbdg1K474wuH3jne5g=
X-Received: by 2002:a2e:8783:: with SMTP id n3mr5170395lji.317.1595042010390;  Fri, 17 Jul 2020 20:13:30 -0700 (PDT)
MIME-Version: 1.0
References: <CABC-CqayJAeipEhsTf4h8rkUVQvYLd=1wF4UBMkaYSNMfvgnXw@mail.gmail.com> <CADdTf+jxKyPw_zfJ6FWCz230rXqg83d7rQJhKBteBvoLCut1RQ@mail.gmail.com> <CAKKJt-dgEmOtvXR8hVT9qf+YgSe3m9LMUuE6=csU28j+j1V_ZQ@mail.gmail.com>
In-Reply-To: <CAKKJt-dgEmOtvXR8hVT9qf+YgSe3m9LMUuE6=csU28j+j1V_ZQ@mail.gmail.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Fri, 17 Jul 2020 20:13:19 -0700
Message-ID: <CACpbDcd5gSz9rpj+WzvzUZGCquYWtSAbPpjYOUe7m+voPge_gQ@mail.gmail.com>
Subject: Re: Questions about recovery draft 29
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Matt Joras <matt.joras@gmail.com>, IETF QUIC WG <quic@ietf.org>,  Jonas Reynders <jonas.reynders@student.uhasselt.be>
Content-Type: multipart/alternative; boundary="0000000000006e640c05aaaea80e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/pTx10oO17chq39odBm84XKH5_xY>
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, 18 Jul 2020 03:13:35 -0000

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

Jonas,

I agree with Matt's response overall. I'll add a couple of specific
responses to your questions.

On RACK: RACK's key insight is to use timestamps (and time) instead of TCP
sequence numbers for loss detection. RACK makes time-ordering the basis for
loss detection, instead of sequence number ordering.  This difference is
importnat when thinking about retransmissions, detection of spurious
retransmissions, and such. A big but subtle difference between TCP and QUIC
is that QUIC does not _reuse_ its packet numbers. This was a deliberate
design choice, at least in part to ensure that QUIC's packet numbers
represent time-ordering. As a result, using packet numbers for loss
detection in QUIC is already different than base (non-RACK) TCP.

The rest of it is around making constants adaptive, and as Matt notes, it's
not fully clear yet what the "right" answer here is, and we wanted to leave
room for experimentation here. As we learn more, we entirely expect the
mechanisms in the draft to evolve, first in implementations, and then in
specifications.

- jana


On Mon, Jul 13, 2020 at 7:40 AM Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> wrote:

> Just to chime in here, so top-posting.
>
> Matt is correct (that specifications !=3D implementations), but I note th=
at
> the transport area has produced, and revised,
> https://datatracker.ietf.org/doc/rfc7414/ (A Roadmap for Transmission
> Control Protocol (TCP) Specification Documents", that go through what Mat=
t
> characterized as the 'myriad RFCs that loosely define "IETF TCP"'
>
> The TCP community used Informational RFCs to document what's a good idea
> and what's a bad idea at the per-specification level ("really important t=
o
> implement this, that is a really bad idea so don't implement it", because
> RFCs were the tools we have.
>
> It might be worth thinking about the form a "QUIC Roadmap" might take,
> given that we now have wikis, gitbub, and other tools that could allow th=
e
> QUIC roadmap and implementations to be more aware of each other, especial=
ly
> if this was more granular than "this document".
>
> We talked about this briefly at IETF 106 in TSVAREA. From the minutes at
> https://datatracker.ietf.org/meeting/106/materials/minutes-106-tsvarea-02
>  ...
>
>    - Ted: Lots of creativity right now. people need to understand what
>    they are doing *to* the protocol, not just *with* it. We should write =
"the
>    hitchhiker's guide to QUIC". Intended for all audiences.
>    - Mirja: That's what applicability and mgmt docs are for.
>    - Ted: That's not what I'm looking for.
>    - Spencer: Imagine if TCP roadmap had started before there were 150
>    RFCs!
>
> Did people have thoughts about that?
>
> Best,
>
> Spencer
>
>
> On Thu, Jul 9, 2020 at 2:10 PM Matt Joras <matt.joras@gmail.com> wrote:
>
>> I won't offer specific answers to all your questions as Ian or Jana
>> likely have better ones, however I'd like to make a general point
>> about this line of questioning: Linux TCP !=3D IETF TCP, or, said
>> another way, Implementations and Specifications are not the same
>> thing. Recall that QUIC is a series of specifications being developed
>> by the IETF, similar to the myriad RFCs that loosely define "IETF
>> TCP". Linux's TCP stack is one such interpretation/implementation of
>> TCP, and while it can inform the decisions of IETF workings, it should
>> not be an undue determiner of the development of said specifications.
>> Similarly we have an even wider and more diverse collection of QUIC
>> interpretations/implementations in various states of maturity and
>> deployment. Many diverge, sometimes heavily, from the specifications
>> especially insofar as recovery is concerned. Chrome and us (mvfst) use
>> BBR as the default congestion controller, others use Cubic or HSTCP or
>> who knows what else. Chrome, AFAIK has a notion of adaptive reordering
>> similar to Linux TCP and modifications to the draft-suggested time
>> thresholds and PTO strategy.
>>
>> Whether some of these changes should be codified in the QUIC
>> specifications is a good question. My hope is that these best
>> practices will gain deployment experience and drive consensus at the
>> IETF in future iterations of QUIC recovery and encounter fewer
>> roadblocks than innovations based on TCP have historically
>> experienced. As it is now though, QUIC's charter, by design, largely
>> limits us to the adaptation of recovery and congestion control work
>> that has already gained consensus via other IETF RFCs. That being
>> said, what we have in the recovery specs may not be the "state of the
>> art" exactly, but it is still quite good and I would argue has other
>> significant advantages over what is commonly deployed in TCP, even
>> Linux TCP.
>>
>> Matt Joras
>>
>> On Thu, Jul 9, 2020 at 9:22 AM Jonas Reynders
>> <jonas.reynders@student.uhasselt.be> wrote:
>> >
>> > I have been looking at the recovery draft 29 of QUIC and comparing it
>> to TCP, specifically the linux implementation in kernel v5.4. I have a
>> couple of questions about the design choices that differ from TCP in lin=
ux.
>> >
>> > The first question is in regards to ack-based loss detection where QUI=
C
>> uses both a packet-threshold and time-threshold method. Looking at the
>> linux implementation (kernel v5.4), TCP uses only a time-threshold metho=
d
>> (RACK) as default. From my understanding both methods were used in linux
>> some time ago, around the time it was clarified to use both methods for
>> QUIC as well. However since then TCP changed to RACK only as the default=
,
>> from what I found out it was due to tests at google detecting a 10%
>> reduction in recovery latency (reference:
>> https://patchwork.ozlabs.org/project/netdev/cover/20180516234017.172775-=
1-ycheng@google.com/).
>> My question is why QUIC still recommends using both methods as default? =
I
>> can understand that in a datacenter context, where RTT values are really
>> low, RACK can struggle due to timers not being fine grained.
>> >
>> > My second question is in regards to the time threshold
>> calculation(6.1..2 in recovery draft). QUIC uses a constant value (9/8) =
for
>> the time threshold, whilst in linux an adaptive threshold is used in the
>> form of a reordering window variable. In the recovery draft it is mentio=
ned
>> that adaptive thresholds can be used, however it=E2=80=99s not mandatory=
. Is there
>> a reason why QUIC doesn=E2=80=99t use the linux method for an adaptive t=
hreshold?
>> The draft also mentions that reordering can be more common in QUIC and t=
hat
>> adaptive thresholds have the advantage of being more aggressive when the=
re
>> is no reordering. The same question for the packet threshold, QUIC uses =
a
>> constant threshold of 3 packets whilst in linux there is an adaptive
>> threshold.
>> >
>> > My last question is that of merging the TLP and RTO into PTO. If I
>> understand correctly, this was possible due to probe packet being
>> ack-eliciting. And, that the time-threshold method would detect loss in =
a
>> similar manner to RTO, with the RTO also causing a congestion collapse i=
f
>> no acks were received for consecutive RTOs. I assume that keeping RTO wo=
uld
>> unnecessarily complicate things, is that correct?
>>
>>

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

<div dir=3D"ltr">Jonas,<div><br></div><div>I agree with Matt&#39;s response=
 overall. I&#39;ll add a couple of specific responses to your questions.</d=
iv><div><br></div><div>On RACK: RACK&#39;s key insight is to use timestamps=
 (and time) instead of TCP sequence numbers for loss detection. RACK makes =
time-ordering the basis for loss detection, instead of sequence number orde=
ring.=C2=A0 This difference is importnat=C2=A0when thinking about retransmi=
ssions, detection of spurious retransmissions, and such. A big but subtle d=
ifference between TCP and QUIC is that QUIC does not _reuse_ its packet num=
bers. This was a deliberate design choice, at least in part to ensure that =
QUIC&#39;s packet numbers represent time-ordering. As a result, using packe=
t numbers for loss detection in QUIC is already different than base (non-RA=
CK) TCP.</div><div><br></div><div>The rest of it is around making constants=
 adaptive, and as Matt notes, it&#39;s not fully=C2=A0clear yet what the &q=
uot;right&quot; answer here is, and we wanted to leave room for experimenta=
tion here. As we learn more, we entirely expect the mechanisms in the draft=
 to evolve, first in implementations, and then in specifications.</div><div=
><br></div><div>- jana</div><div><br></div></div><br><div class=3D"gmail_qu=
ote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jul 13, 2020 at 7:40 AM =
Spencer Dawkins at IETF &lt;<a href=3D"mailto:spencerdawkins.ietf@gmail.com=
">spencerdawkins.ietf@gmail.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 dir=3D"ltr">Just to chime in here, so=
 top-posting.=C2=A0<div><br></div><div>Matt is correct (that specifications=
 !=3D implementations), but I note that the transport area has produced, an=
d revised,=C2=A0<a href=3D"https://datatracker.ietf.org/doc/rfc7414/" targe=
t=3D"_blank">https://datatracker.ietf.org/doc/rfc7414/</a>=C2=A0(A Roadmap =
for Transmission Control Protocol (TCP) Specification Documents&quot;, that=
 go through what Matt characterized as the &#39;myriad RFCs that loosely de=
fine &quot;IETF TCP&quot;&#39;</div><div><br></div><div>The TCP community u=
sed Informational RFCs to document what&#39;s a good idea and what&#39;s a =
bad idea at the per-specification level (&quot;really important to implemen=
t this, that is a really bad idea so don&#39;t implement it&quot;, because =
RFCs were the tools we have.=C2=A0</div><div><br></div><div>It might be wor=
th thinking about the form a &quot;QUIC Roadmap&quot; might take, given tha=
t we now have wikis, gitbub, and other tools=C2=A0that could allow the QUIC=
 roadmap and implementations to be more aware of each other, especially if =
this was more granular than &quot;this document&quot;.=C2=A0</div><div><br>=
</div><div>We talked about this briefly at IETF 106 in TSVAREA. From the mi=
nutes at=C2=A0<a href=3D"https://datatracker.ietf.org/meeting/106/materials=
/minutes-106-tsvarea-02" target=3D"_blank">https://datatracker.ietf.org/mee=
ting/106/materials/minutes-106-tsvarea-02</a>=C2=A0...</div><div><ul><li>Te=
d: Lots of creativity right now. people need to understand what they are do=
ing *to* the protocol, not just *with* it. We should write &quot;the hitchh=
iker&#39;s guide to QUIC&quot;. Intended for all audiences.</li><li>Mirja: =
That&#39;s what applicability and mgmt docs are for.</li><li>Ted: That&#39;=
s not what I&#39;m looking for.</li><li>Spencer: Imagine if TCP roadmap had=
 started before there were 150 RFCs!<br></li></ul></div><div>Did people hav=
e thoughts about that?=C2=A0</div><div>=C2=A0<br></div><div>Best,</div><div=
><br></div><div>Spencer</div><div><br></div></div><br><div class=3D"gmail_q=
uote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jul 9, 2020 at 2:10 PM =
Matt Joras &lt;<a href=3D"mailto:matt.joras@gmail.com" target=3D"_blank">ma=
tt.joras@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">I won&#39;t offer specific answers to all your questions =
as Ian or Jana<br>
likely have better ones, however I&#39;d like to make a general point<br>
about this line of questioning: Linux TCP !=3D IETF TCP, or, said<br>
another way, Implementations and Specifications are not the same<br>
thing. Recall that QUIC is a series of specifications being developed<br>
by the IETF, similar to the myriad RFCs that loosely define &quot;IETF<br>
TCP&quot;. Linux&#39;s TCP stack is one such interpretation/implementation =
of<br>
TCP, and while it can inform the decisions of IETF workings, it should<br>
not be an undue determiner of the development of said specifications.<br>
Similarly we have an even wider and more diverse collection of QUIC<br>
interpretations/implementations in various states of maturity and<br>
deployment. Many diverge, sometimes heavily, from the specifications<br>
especially insofar as recovery is concerned. Chrome and us (mvfst) use<br>
BBR as the default congestion controller, others use Cubic or HSTCP or<br>
who knows what else. Chrome, AFAIK has a notion of adaptive reordering<br>
similar to Linux TCP and modifications to the draft-suggested time<br>
thresholds and PTO strategy.<br>
<br>
Whether some of these changes should be codified in the QUIC<br>
specifications is a good question. My hope is that these best<br>
practices will gain deployment experience and drive consensus at the<br>
IETF in future iterations of QUIC recovery and encounter fewer<br>
roadblocks than innovations based on TCP have historically<br>
experienced. As it is now though, QUIC&#39;s charter, by design, largely<br=
>
limits us to the adaptation of recovery and congestion control work<br>
that has already gained consensus via other IETF RFCs. That being<br>
said, what we have in the recovery specs may not be the &quot;state of the<=
br>
art&quot; exactly, but it is still quite good and I would argue has other<b=
r>
significant advantages over what is commonly deployed in TCP, even<br>
Linux TCP.<br>
<br>
Matt Joras<br>
<br>
On Thu, Jul 9, 2020 at 9:22 AM Jonas Reynders<br>
&lt;<a href=3D"mailto:jonas.reynders@student.uhasselt.be" target=3D"_blank"=
>jonas.reynders@student.uhasselt.be</a>&gt; wrote:<br>
&gt;<br>
&gt; I have been looking at the recovery draft 29 of QUIC and comparing it =
to TCP, specifically the linux implementation in kernel v5.4. I have a coup=
le of questions about the design choices that differ from TCP in linux.<br>
&gt;<br>
&gt; The first question is in regards to ack-based loss detection where QUI=
C uses both a packet-threshold and time-threshold method. Looking at the li=
nux implementation (kernel v5.4), TCP uses only a time-threshold method (RA=
CK) as default. From my understanding both methods were used in linux some =
time ago, around the time it was clarified to use both methods for QUIC as =
well. However since then TCP changed to RACK only as the default, from what=
 I found out it was due to tests at google detecting a 10% reduction in rec=
overy latency (reference: <a href=3D"https://patchwork.ozlabs.org/project/n=
etdev/cover/20180516234017.172775-1-ycheng@google.com/" rel=3D"noreferrer" =
target=3D"_blank">https://patchwork.ozlabs.org/project/netdev/cover/2018051=
6234017.172775-1-ycheng@google.com/</a>). My question is why QUIC still rec=
ommends using both methods as default? I can understand that in a datacente=
r context, where RTT values are really low, RACK can struggle due to timers=
 not being fine grained.<br>
&gt;<br>
&gt; My second question is in regards to the time threshold calculation(6.1=
..2 in recovery draft). QUIC uses a constant value (9/8) for the time thres=
hold, whilst in linux an adaptive threshold is used in the form of a reorde=
ring window variable. In the recovery draft it is mentioned that adaptive t=
hresholds can be used, however it=E2=80=99s not mandatory. Is there a reaso=
n why QUIC doesn=E2=80=99t use the linux method for an adaptive threshold? =
The draft also mentions that reordering can be more common in QUIC and that=
 adaptive thresholds have the advantage of being more aggressive when there=
 is no reordering. The same question for the packet threshold, QUIC uses a =
constant threshold of 3 packets whilst in linux there is an adaptive thresh=
old.<br>
&gt;<br>
&gt; My last question is that of merging the TLP and RTO into PTO. If I und=
erstand correctly, this was possible due to probe packet being ack-elicitin=
g. And, that the time-threshold method would detect loss in a similar manne=
r to RTO, with the RTO also causing a congestion collapse if no acks were r=
eceived for consecutive RTOs. I assume that keeping RTO would unnecessarily=
 complicate things, is that correct?<br>
<br>
</blockquote></div>
</blockquote></div>

--0000000000006e640c05aaaea80e--


From nobody Fri Jul 17 20:15:09 2020
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 2D3D83A094A for <quic@ietfa.amsl.com>; Fri, 17 Jul 2020 20:15:07 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 tEFKv2emumZX for <quic@ietfa.amsl.com>; Fri, 17 Jul 2020 20:15:04 -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 4F8143A0948 for <quic@ietf.org>; Fri, 17 Jul 2020 20:15:04 -0700 (PDT)
Received: by mail-lj1-x232.google.com with SMTP id h22so14867001lji.9 for <quic@ietf.org>; Fri, 17 Jul 2020 20:15: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=htiZWFllvIjR6B0Qfb7qyCKBRLRYyS7y3IpSMIX+nTw=; b=O/MMFEz3y8mOdpjaTlHNLq2gRB5+DD7a/nNrq+jIz9zoEnZo8KbopYM+ZlvUBBTDXC ysro9TJsdXUw8xh9RvXxozogeie159xBioGHe4t1oIzkkhMYi6hCcKzbLjA7eBbUWgLd uMxdJdewX4gVFxfAlPbTsOvasMsrxnZuCdOp9vq6Fadqv6rIW5+HBXAdr2rmfNlsQprN kbsiNDC6zTFkgRypkYnctulHeaPLhnCJB9SDJry4fAdG1eXEHn2r92lNMQG1aaVzPaug WrMimLfjxI2p2WUztmMkmsFHFU1Fu1aMA4YuZBfQa4K7Eplcc642Cj1+/ixNUB+1BRkW c+iw==
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=htiZWFllvIjR6B0Qfb7qyCKBRLRYyS7y3IpSMIX+nTw=; b=aLeEEoYN3hRkaI7g1+IcMylKDGglSLdi+tEje97/dCdaiXJqNlnR7PXvtvr/qpAmSO wccL1pwjdwXbo3sCtk8VesumCn4sTYSJZTfkyyFqdNWVUN+3jfqD8YL/h6gxpNtbPlXh 08WWcSTDgYnsWE2X7QQqTTacb/GUZwvq5js6ZjotW4PuwCoyzx7u9O1Dck0PhUSqTF+I anuKJUDivcJs8HCu1ZqR03WgAKuUNoPilWaV7BI2lSM9j/xQ8Mqw0Tl6RE+1Rfwh8AFr Dq4JQDjzEy4+bKlAvHd9wzhtgLQBcM/IspP1TNPx9HpzhZ+H+p5e/2xjJD42Vx+LJNq2 /v6Q==
X-Gm-Message-State: AOAM530rLqXtS5jVtCce2y5pWtCoCjAsCxttkO2TnmNkf9pJmF0hfgyw 1tA360+y1jtM1jqHT4e5v/NUCpYiEDiL8a2r/nY=
X-Google-Smtp-Source: ABdhPJwKbQDQnf4Q2rhc8Of6ockvZCK6vpQJrY8KJVMkVWGu1v3vEz3IAbUVE3BT5z5fBVCkDfrsPJroUhJrKUe+E6c=
X-Received: by 2002:a05:651c:305:: with SMTP id a5mr5399156ljp.387.1595042102328;  Fri, 17 Jul 2020 20:15:02 -0700 (PDT)
MIME-Version: 1.0
References: <CABC-CqayJAeipEhsTf4h8rkUVQvYLd=1wF4UBMkaYSNMfvgnXw@mail.gmail.com> <CADdTf+jxKyPw_zfJ6FWCz230rXqg83d7rQJhKBteBvoLCut1RQ@mail.gmail.com> <CAKKJt-dgEmOtvXR8hVT9qf+YgSe3m9LMUuE6=csU28j+j1V_ZQ@mail.gmail.com>
In-Reply-To: <CAKKJt-dgEmOtvXR8hVT9qf+YgSe3m9LMUuE6=csU28j+j1V_ZQ@mail.gmail.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Fri, 17 Jul 2020 20:14:51 -0700
Message-ID: <CACpbDce=G=ou1F5dQx3r+TbzACrJRkQkKO7OviTHvd2QxFKTyg@mail.gmail.com>
Subject: Re: Questions about recovery draft 29
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Matt Joras <matt.joras@gmail.com>, IETF QUIC WG <quic@ietf.org>,  Jonas Reynders <jonas.reynders@student.uhasselt.be>
Content-Type: multipart/alternative; boundary="000000000000e94f0405aaaead33"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/AHnVBXUiFwIYLKn5l9ZrDv_vE7I>
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, 18 Jul 2020 03:15:07 -0000

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

Spencer,

It's a good idea, but I think it's a bit early to think of a roadmap. The
core protocol components necessary for QUIC are exactly the three documents
we have right now, nothing more. Once we have more extensions, other
changes in more drafts, it might make sense to think of a roadmap.

- jana

On Mon, Jul 13, 2020 at 7:40 AM Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> wrote:

> Just to chime in here, so top-posting.
>
> Matt is correct (that specifications !=3D implementations), but I note th=
at
> the transport area has produced, and revised,
> https://datatracker.ietf.org/doc/rfc7414/ (A Roadmap for Transmission
> Control Protocol (TCP) Specification Documents", that go through what Mat=
t
> characterized as the 'myriad RFCs that loosely define "IETF TCP"'
>
> The TCP community used Informational RFCs to document what's a good idea
> and what's a bad idea at the per-specification level ("really important t=
o
> implement this, that is a really bad idea so don't implement it", because
> RFCs were the tools we have.
>
> It might be worth thinking about the form a "QUIC Roadmap" might take,
> given that we now have wikis, gitbub, and other tools that could allow th=
e
> QUIC roadmap and implementations to be more aware of each other, especial=
ly
> if this was more granular than "this document".
>
> We talked about this briefly at IETF 106 in TSVAREA. From the minutes at
> https://datatracker.ietf.org/meeting/106/materials/minutes-106-tsvarea-02
>  ...
>
>    - Ted: Lots of creativity right now. people need to understand what
>    they are doing *to* the protocol, not just *with* it. We should write =
"the
>    hitchhiker's guide to QUIC". Intended for all audiences.
>    - Mirja: That's what applicability and mgmt docs are for.
>    - Ted: That's not what I'm looking for.
>    - Spencer: Imagine if TCP roadmap had started before there were 150
>    RFCs!
>
> Did people have thoughts about that?
>
> Best,
>
> Spencer
>
>
> On Thu, Jul 9, 2020 at 2:10 PM Matt Joras <matt.joras@gmail.com> wrote:
>
>> I won't offer specific answers to all your questions as Ian or Jana
>> likely have better ones, however I'd like to make a general point
>> about this line of questioning: Linux TCP !=3D IETF TCP, or, said
>> another way, Implementations and Specifications are not the same
>> thing. Recall that QUIC is a series of specifications being developed
>> by the IETF, similar to the myriad RFCs that loosely define "IETF
>> TCP". Linux's TCP stack is one such interpretation/implementation of
>> TCP, and while it can inform the decisions of IETF workings, it should
>> not be an undue determiner of the development of said specifications.
>> Similarly we have an even wider and more diverse collection of QUIC
>> interpretations/implementations in various states of maturity and
>> deployment. Many diverge, sometimes heavily, from the specifications
>> especially insofar as recovery is concerned. Chrome and us (mvfst) use
>> BBR as the default congestion controller, others use Cubic or HSTCP or
>> who knows what else. Chrome, AFAIK has a notion of adaptive reordering
>> similar to Linux TCP and modifications to the draft-suggested time
>> thresholds and PTO strategy.
>>
>> Whether some of these changes should be codified in the QUIC
>> specifications is a good question. My hope is that these best
>> practices will gain deployment experience and drive consensus at the
>> IETF in future iterations of QUIC recovery and encounter fewer
>> roadblocks than innovations based on TCP have historically
>> experienced. As it is now though, QUIC's charter, by design, largely
>> limits us to the adaptation of recovery and congestion control work
>> that has already gained consensus via other IETF RFCs. That being
>> said, what we have in the recovery specs may not be the "state of the
>> art" exactly, but it is still quite good and I would argue has other
>> significant advantages over what is commonly deployed in TCP, even
>> Linux TCP.
>>
>> Matt Joras
>>
>> On Thu, Jul 9, 2020 at 9:22 AM Jonas Reynders
>> <jonas.reynders@student.uhasselt.be> wrote:
>> >
>> > I have been looking at the recovery draft 29 of QUIC and comparing it
>> to TCP, specifically the linux implementation in kernel v5.4. I have a
>> couple of questions about the design choices that differ from TCP in lin=
ux.
>> >
>> > The first question is in regards to ack-based loss detection where QUI=
C
>> uses both a packet-threshold and time-threshold method. Looking at the
>> linux implementation (kernel v5.4), TCP uses only a time-threshold metho=
d
>> (RACK) as default. From my understanding both methods were used in linux
>> some time ago, around the time it was clarified to use both methods for
>> QUIC as well. However since then TCP changed to RACK only as the default=
,
>> from what I found out it was due to tests at google detecting a 10%
>> reduction in recovery latency (reference:
>> https://patchwork.ozlabs.org/project/netdev/cover/20180516234017.172775-=
1-ycheng@google.com/).
>> My question is why QUIC still recommends using both methods as default? =
I
>> can understand that in a datacenter context, where RTT values are really
>> low, RACK can struggle due to timers not being fine grained.
>> >
>> > My second question is in regards to the time threshold
>> calculation(6.1..2 in recovery draft). QUIC uses a constant value (9/8) =
for
>> the time threshold, whilst in linux an adaptive threshold is used in the
>> form of a reordering window variable. In the recovery draft it is mentio=
ned
>> that adaptive thresholds can be used, however it=E2=80=99s not mandatory=
. Is there
>> a reason why QUIC doesn=E2=80=99t use the linux method for an adaptive t=
hreshold?
>> The draft also mentions that reordering can be more common in QUIC and t=
hat
>> adaptive thresholds have the advantage of being more aggressive when the=
re
>> is no reordering. The same question for the packet threshold, QUIC uses =
a
>> constant threshold of 3 packets whilst in linux there is an adaptive
>> threshold.
>> >
>> > My last question is that of merging the TLP and RTO into PTO. If I
>> understand correctly, this was possible due to probe packet being
>> ack-eliciting. And, that the time-threshold method would detect loss in =
a
>> similar manner to RTO, with the RTO also causing a congestion collapse i=
f
>> no acks were received for consecutive RTOs. I assume that keeping RTO wo=
uld
>> unnecessarily complicate things, is that correct?
>>
>>

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

<div dir=3D"ltr">Spencer,<div><br></div><div>It&#39;s a good=C2=A0idea, but=
 I think it&#39;s a bit early to think of a roadmap. The core protocol comp=
onents necessary for QUIC are exactly the three documents we have right now=
, nothing more. Once we have more extensions, other changes in more drafts,=
 it might make sense to think of a roadmap.</div><div><br></div><div>- jana=
</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_=
attr">On Mon, Jul 13, 2020 at 7:40 AM Spencer Dawkins at IETF &lt;<a href=
=3D"mailto:spencerdawkins.ietf@gmail.com">spencerdawkins.ietf@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">Just to chime in here, so top-posting.=C2=A0<div><br></div><di=
v>Matt is correct (that specifications !=3D implementations), but I note th=
at the transport area has produced, and revised,=C2=A0<a href=3D"https://da=
tatracker.ietf.org/doc/rfc7414/" target=3D"_blank">https://datatracker.ietf=
.org/doc/rfc7414/</a>=C2=A0(A Roadmap for Transmission Control Protocol (TC=
P) Specification Documents&quot;, that go through what Matt characterized a=
s the &#39;myriad RFCs that loosely define &quot;IETF TCP&quot;&#39;</div><=
div><br></div><div>The TCP community used Informational RFCs to document wh=
at&#39;s a good idea and what&#39;s a bad idea at the per-specification lev=
el (&quot;really important to implement this, that is a really bad idea so =
don&#39;t implement it&quot;, because RFCs were the tools we have.=C2=A0</d=
iv><div><br></div><div>It might be worth thinking about the form a &quot;QU=
IC Roadmap&quot; might take, given that we now have wikis, gitbub, and othe=
r tools=C2=A0that could allow the QUIC roadmap and implementations to be mo=
re aware of each other, especially if this was more granular than &quot;thi=
s document&quot;.=C2=A0</div><div><br></div><div>We talked about this brief=
ly at IETF 106 in TSVAREA. From the minutes at=C2=A0<a href=3D"https://data=
tracker.ietf.org/meeting/106/materials/minutes-106-tsvarea-02" target=3D"_b=
lank">https://datatracker.ietf.org/meeting/106/materials/minutes-106-tsvare=
a-02</a>=C2=A0...</div><div><ul><li>Ted: Lots of creativity right now. peop=
le need to understand what they are doing *to* the protocol, not just *with=
* it. We should write &quot;the hitchhiker&#39;s guide to QUIC&quot;. Inten=
ded for all audiences.</li><li>Mirja: That&#39;s what applicability and mgm=
t docs are for.</li><li>Ted: That&#39;s not what I&#39;m looking for.</li><=
li>Spencer: Imagine if TCP roadmap had started before there were 150 RFCs!<=
br></li></ul></div><div>Did people have thoughts about that?=C2=A0</div><di=
v>=C2=A0<br></div><div>Best,</div><div><br></div><div>Spencer</div><div><br=
></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail=
_attr">On Thu, Jul 9, 2020 at 2:10 PM Matt Joras &lt;<a href=3D"mailto:matt=
.joras@gmail.com" target=3D"_blank">matt.joras@gmail.com</a>&gt; wrote:<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex">I won&#39;t offer s=
pecific answers to all your questions as Ian or Jana<br>
likely have better ones, however I&#39;d like to make a general point<br>
about this line of questioning: Linux TCP !=3D IETF TCP, or, said<br>
another way, Implementations and Specifications are not the same<br>
thing. Recall that QUIC is a series of specifications being developed<br>
by the IETF, similar to the myriad RFCs that loosely define &quot;IETF<br>
TCP&quot;. Linux&#39;s TCP stack is one such interpretation/implementation =
of<br>
TCP, and while it can inform the decisions of IETF workings, it should<br>
not be an undue determiner of the development of said specifications.<br>
Similarly we have an even wider and more diverse collection of QUIC<br>
interpretations/implementations in various states of maturity and<br>
deployment. Many diverge, sometimes heavily, from the specifications<br>
especially insofar as recovery is concerned. Chrome and us (mvfst) use<br>
BBR as the default congestion controller, others use Cubic or HSTCP or<br>
who knows what else. Chrome, AFAIK has a notion of adaptive reordering<br>
similar to Linux TCP and modifications to the draft-suggested time<br>
thresholds and PTO strategy.<br>
<br>
Whether some of these changes should be codified in the QUIC<br>
specifications is a good question. My hope is that these best<br>
practices will gain deployment experience and drive consensus at the<br>
IETF in future iterations of QUIC recovery and encounter fewer<br>
roadblocks than innovations based on TCP have historically<br>
experienced. As it is now though, QUIC&#39;s charter, by design, largely<br=
>
limits us to the adaptation of recovery and congestion control work<br>
that has already gained consensus via other IETF RFCs. That being<br>
said, what we have in the recovery specs may not be the &quot;state of the<=
br>
art&quot; exactly, but it is still quite good and I would argue has other<b=
r>
significant advantages over what is commonly deployed in TCP, even<br>
Linux TCP.<br>
<br>
Matt Joras<br>
<br>
On Thu, Jul 9, 2020 at 9:22 AM Jonas Reynders<br>
&lt;<a href=3D"mailto:jonas.reynders@student.uhasselt.be" target=3D"_blank"=
>jonas.reynders@student.uhasselt.be</a>&gt; wrote:<br>
&gt;<br>
&gt; I have been looking at the recovery draft 29 of QUIC and comparing it =
to TCP, specifically the linux implementation in kernel v5.4. I have a coup=
le of questions about the design choices that differ from TCP in linux.<br>
&gt;<br>
&gt; The first question is in regards to ack-based loss detection where QUI=
C uses both a packet-threshold and time-threshold method. Looking at the li=
nux implementation (kernel v5.4), TCP uses only a time-threshold method (RA=
CK) as default. From my understanding both methods were used in linux some =
time ago, around the time it was clarified to use both methods for QUIC as =
well. However since then TCP changed to RACK only as the default, from what=
 I found out it was due to tests at google detecting a 10% reduction in rec=
overy latency (reference: <a href=3D"https://patchwork.ozlabs.org/project/n=
etdev/cover/20180516234017.172775-1-ycheng@google.com/" rel=3D"noreferrer" =
target=3D"_blank">https://patchwork.ozlabs.org/project/netdev/cover/2018051=
6234017.172775-1-ycheng@google.com/</a>). My question is why QUIC still rec=
ommends using both methods as default? I can understand that in a datacente=
r context, where RTT values are really low, RACK can struggle due to timers=
 not being fine grained.<br>
&gt;<br>
&gt; My second question is in regards to the time threshold calculation(6.1=
..2 in recovery draft). QUIC uses a constant value (9/8) for the time thres=
hold, whilst in linux an adaptive threshold is used in the form of a reorde=
ring window variable. In the recovery draft it is mentioned that adaptive t=
hresholds can be used, however it=E2=80=99s not mandatory. Is there a reaso=
n why QUIC doesn=E2=80=99t use the linux method for an adaptive threshold? =
The draft also mentions that reordering can be more common in QUIC and that=
 adaptive thresholds have the advantage of being more aggressive when there=
 is no reordering. The same question for the packet threshold, QUIC uses a =
constant threshold of 3 packets whilst in linux there is an adaptive thresh=
old.<br>
&gt;<br>
&gt; My last question is that of merging the TLP and RTO into PTO. If I und=
erstand correctly, this was possible due to probe packet being ack-elicitin=
g. And, that the time-threshold method would detect loss in a similar manne=
r to RTO, with the RTO also causing a congestion collapse if no acks were r=
eceived for consecutive RTOs. I assume that keeping RTO would unnecessarily=
 complicate things, is that correct?<br>
<br>
</blockquote></div>
</blockquote></div>

--000000000000e94f0405aaaead33--


From nobody Sun Jul 19 00:32:19 2020
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 79ED83A0AEA for <quic@ietfa.amsl.com>; Sun, 19 Jul 2020 00:32:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=G7W763+t; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=mO7FKHLI
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id BsWl4m1jINvf for <quic@ietfa.amsl.com>; Sun, 19 Jul 2020 00:32:15 -0700 (PDT)
Received: from wout1-smtp.messagingengine.com (wout1-smtp.messagingengine.com [64.147.123.24]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 47CEF3A0AE8 for <quic@ietf.org>; Sun, 19 Jul 2020 00:32:15 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 6330FD2E for <quic@ietf.org>; Sun, 19 Jul 2020 03:32:14 -0400 (EDT)
Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Sun, 19 Jul 2020 03:32:14 -0400
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= fm3; bh=30NWygYWh2DOltePOJNpgu+xHDNf4k3qu0qp+6ijXoE=; b=G7W763+t zVYNfeIUn4tGkG3nWC82o69zFoOvJB+46J5g1JRfw0vB9o/dB2mqYIdHYzw5P7bY SyL7jmaeuWgwna++JdE+Wtk5SUQmnNK+JDji/SFIOPQB1XA+PbxuaUeooZdBfcW+ NpwSJLo4+B8N6oVDcALiPhuRNFdj1EYEfJoJeJkXknp6GstOu1F2glyGzBwUbo/I ZPUf/WmUW7Pj0cbc7zXjrKd7tUo760vYeAFEMflBuG4hRXLnTyIin10xU/cisawT mZtGE+miykV0CbNq/lbw0OJr16neCdFtxMTGRdCm2+5RGdZecOiX8+CXXdOh48lY 47U/pwWt+t3LdQ==
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=fm3; bh=30NWygYWh2DOltePOJNpgu+xHDNf4 k3qu0qp+6ijXoE=; b=mO7FKHLICwFuBYLTadP33L4WYiiVDnDvFq+sd3CHWoDnV Hs4jlqTLF0e6AkO2p57VpoPrZ/7DiyJMb+FvM7p5G0UUgvWKvnizbmqqxZrW/Mi6 Vnj9vyn45yrDHgPmMs9hVtWoNEnX8sO/HE/y4OkDyG5zee1/YTrbVzjZ5cChfhJi epJDm/n4WQn9KJvs3FKPTMroNz/+HOK6yK/LR0F82JbQWE/AGdKchssG2sb46BzU G8LZdM9IWKjIeowxJYnEkg6rnyvolYGCjSPvSN8ZYUjGX+62GmKOsJKFJNLm/boM PYYwlHMSkQSaUKpalg9u43+1mBP5VlOoruBKzMv4w==
X-ME-Sender: <xms:_fYTX9yiCO-8gRtU4qQlwKiG04bETEzVq9oyAxWt_0qJsIiQikIcrg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrgedtgdduvddtucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtggfhvffusegrtddtredttdejne cuhfhrohhmpeftvghpohhsihhtohhrhicutegtthhivhhithihucfuuhhmmhgrrhihuceu ohhtuceoughopghnohhtpghrvghplhihsehmnhhothdrnhgvtheqnecuggftrfgrthhtvg hrnhepkeefvdduteejvdefkeehieevuefgfefhteetveegffekffefteffvdelheduieet necuffhomhgrihhnpehgihhthhhusgdrtghomhenucfkphephedvrddugeelrdefledrud eikeenucevlhhushhtvghrufhiiigvpedunecurfgrrhgrmhepmhgrihhlfhhrohhmpegu ohgpnhhothgprhgvphhlhiesmhhnohhtrdhnvght
X-ME-Proxy: <xmx:_fYTX9QbxbvQW7bTMTMdMrOpO3V2ZoDeUQSP6v0iDHd2AcQQxbqm2A> <xmx:_fYTX3WpvYDh3m-4AmpELegTY0Eskx2mBTanbHbH5DUR3hTxjzhW9A> <xmx:_fYTX_iwvyk5KqJl5gfrHPClHYfz-o-fOfJbuY0f7jaezeIfag8QBA> <xmx:_vYTXyqg6LXI4xluUBcyS93LF_cMYyN71M4rLwZM5n_CJ3cvwvaMig>
Received: from fv-az131.internal.cloudapp.net (unknown [52.149.39.168]) by mail.messagingengine.com (Postfix) with ESMTPA id 6A9D9328005A for <quic@ietf.org>; Sun, 19 Jul 2020 03:32:13 -0400 (EDT)
Content-Type: multipart/alternative; boundary="===============1411899648396878914=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: quic@ietf.org
Subject: Weekly github digest (QUIC Activity Summary)
Message-Id: <20200719073213.6A9D9328005A@mailuser.nyi.internal>
Date: Sun, 19 Jul 2020 03:32:13 -0400 (EDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/lYmkfL1FpW073LUFXjYYXblVUDY>
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, 19 Jul 2020 07:32:18 -0000

--===============1411899648396878914==
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 (+5/-0/=F0=9F=92=AC30)
  5 issues created:
  - max_ack_delay in recovery pseudocode (by kazu-yamamoto)
    https://github.com/quicwg/base-drafts/issues/3920=20
  - Praveen's WGLC comments (by ianswett)
    https://github.com/quicwg/base-drafts/issues/3919=20
  - Initial window bursts are too small (by ianswett)
    https://github.com/quicwg/base-drafts/issues/3918 [-recovery]=20
  - assertion in OnLossDetectionTimeout of recovery draft (by kazu-yamamoto)
    https://github.com/quicwg/base-drafts/issues/3912=20
  - assertion in GetPtoTimeAndSpace of recovery draft (by kazu-yamamoto)
    https://github.com/quicwg/base-drafts/issues/3910=20

  10 issues received 30 new comments:
  - #3919 Praveen's WGLC comments (1 by kazu-yamamoto)
    https://github.com/quicwg/base-drafts/issues/3919 [-recovery]=20
  - #3918 Initial window bursts are too small (4 by ianswett, janaiyengar)
    https://github.com/quicwg/base-drafts/issues/3918 [-recovery] [post-wgl=
c]=20
  - #3912 assertion in OnLossDetectionTimeout of recovery draft (1 by iansw=
ett)
    https://github.com/quicwg/base-drafts/issues/3912 [post-wglc]=20
  - #3880 How long is a validated address good for? (2 by janaiyengar, mart=
inthomson)
    https://github.com/quicwg/base-drafts/issues/3880 [-transport]=20
  - #3875 Persistent congestion threshold is unreliable during the early st=
ages of a connection (5 by ianswett, janaiyengar, kazuho)
    https://github.com/quicwg/base-drafts/issues/3875 [-recovery]=20
  - #3842 Do I need to reset congestion info when the port changes? (10 by =
DavidSchinazi, huitema, ianswett, janaiyengar, kazuho, nharper)
    https://github.com/quicwg/base-drafts/issues/3842 [-transport]=20
  - #3834 Remove amplification throttle if the server receives Initial that=
 echoes its high entropy SCID. (1 by martinthomson)
    https://github.com/quicwg/base-drafts/issues/3834 [-transport]=20
  - #3831 PTO after handshake completion is not well-defined (1 by kazuho)
    https://github.com/quicwg/base-drafts/issues/3831 [-recovery]=20
  - #3800 Coalescing different CIDs for same connection (4 by ianswett, kaz=
uho, marten-seemann, tatsuhiro-t)
    https://github.com/quicwg/base-drafts/issues/3800 [-transport] [design]=
=20
  - #3788 New confidentiality and integrity limits (1 by DavidSchinazi)
    https://github.com/quicwg/base-drafts/issues/3788 [-tls]=20

* quicwg/load-balancers (+0/-0/=F0=9F=92=AC1)
  1 issues received 1 new comments:
  - #41 Simplify the configuration by merging server-id and zero-pad (1 by =
martinduke)
    https://github.com/quicwg/load-balancers/issues/41=20



Pull requests
-------------
* quicwg/base-drafts (+5/-1/=F0=9F=92=AC20)
  5 pull requests submitted:
  - Replace one-off use of the word "session" when referring to an HTTP/3 c=
onnection (by amirlivneh)
    https://github.com/quicwg/base-drafts/pull/3922=20
  - fixing OnAckReceived of recovery draft (by kazu-yamamoto)
    https://github.com/quicwg/base-drafts/pull/3921=20
  - Byte counting at Congestion avoidance (by junhochoi)
    https://github.com/quicwg/base-drafts/pull/3917=20
  - Acks for 0rtt only after Handshake Complete as in Quic-TLS 4.1.1 (by hu=
itema)
    https://github.com/quicwg/base-drafts/pull/3914=20
  - Fixing recovery pseudocode (by kazu-yamamoto)
    https://github.com/quicwg/base-drafts/pull/3909=20

  5 pull requests received 20 new comments:
  - #3917 Byte counting at Congestion avoidance (1 by ianswett)
    https://github.com/quicwg/base-drafts/pull/3917=20
  - #3914 Acks for 0rtt only after Handshake Complete as in Quic-TLS 4.1.1 =
(1 by huitema)
    https://github.com/quicwg/base-drafts/pull/3914=20
  - #3909 Fixing recovery pseudocode (12 by ianswett, junhochoi, kazu-yamam=
oto, marten-seemann)
    https://github.com/quicwg/base-drafts/pull/3909=20
  - #3889 No RTT samples, no persistent congestion (5 by ianswett, janaiyen=
gar, kazuho, martinthomson)
    https://github.com/quicwg/base-drafts/pull/3889 [-recovery] [design]=20
  - #3874 Allow endpoints to generate traffic keys asynchronously (1 by mar=
tinthomson)
    https://github.com/quicwg/base-drafts/pull/3874 [-recovery] [-tls]=20

  1 pull requests merged:
  - Fixing recovery pseudocode
    https://github.com/quicwg/base-drafts/pull/3909=20

* quicwg/load-balancers (+3/-2/=F0=9F=92=AC0)
  3 pull requests submitted:
  - Rewrite config rotation (by martinduke)
    https://github.com/quicwg/load-balancers/pull/45=20
  - Remove zero padding field (by martinduke)
    https://github.com/quicwg/load-balancers/pull/44=20
  - new stream test vectors (by martinduke)
    https://github.com/quicwg/load-balancers/pull/43=20

  2 pull requests merged:
  - Rewrite config rotation
    https://github.com/quicwg/load-balancers/pull/45=20
  - new stream test vectors
    https://github.com/quicwg/load-balancers/pull/43=20


Repositories tracked by this digest:
-----------------------------------
* https://github.com/quicwg/base-drafts
* https://github.com/quicwg/ops-drafts
* https://github.com/quicwg/datagram
* https://github.com/quicwg/load-balancers
* https://github.com/quicwg/version-negotiation

--===============1411899648396878914==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (QUIC 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 July 19, 2020</h1>

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

<h2>Issues</h2>

<h3>quicwg/base-drafts (+5/-0/=F0=9F=92=AC30)</h3>
  <p class=3D"new">5 issues created:</p>
  <ul>
  <li>#3920 <a href=3D"https://github.com/quicwg/base-drafts/issues/3920">m=
ax_ack_delay in recovery pseudocode</a> (by kazu-yamamoto) </li>
 =20
  <li>#3919 <a href=3D"https://github.com/quicwg/base-drafts/issues/3919">P=
raveen&#x27;s WGLC comments</a> (by ianswett) </li>
 =20
  <li>#3918 <a href=3D"https://github.com/quicwg/base-drafts/issues/3918">I=
nitial window bursts are too small</a> (by ianswett) <span class=3D"label" =
style=3D"background-color: #fbca04; color: #000000">-recovery</span> </li>
 =20
  <li>#3912 <a href=3D"https://github.com/quicwg/base-drafts/issues/3912">a=
ssertion in OnLossDetectionTimeout of recovery draft</a> (by kazu-yamamoto)=
 </li>
 =20
  <li>#3910 <a href=3D"https://github.com/quicwg/base-drafts/issues/3910">a=
ssertion in GetPtoTimeAndSpace of recovery draft</a> (by kazu-yamamoto) </l=
i>
  </ul>

  <p>10 issues received 30 new comments:</p>
  <ul>
  <li>#3919 <a href=3D"https://github.com/quicwg/base-drafts/issues/3919">P=
raveen&#x27;s WGLC comments</a> (1 by kazu-yamamoto) <span class=3D"label" =
style=3D"background-color: #fbca04; color: #000000">-recovery</span> </li>
 =20
  <li>#3918 <a href=3D"https://github.com/quicwg/base-drafts/issues/3918">I=
nitial window bursts are too small</a> (4 by ianswett, janaiyengar) <span c=
lass=3D"label" style=3D"background-color: #fbca04; color: #000000">-recover=
y</span> <span class=3D"label" style=3D"background-color: #d3395a; color: #=
ffffff">post-wglc</span> </li>
 =20
  <li>#3912 <a href=3D"https://github.com/quicwg/base-drafts/issues/3912">a=
ssertion in OnLossDetectionTimeout of recovery draft</a> (1 by ianswett) <s=
pan class=3D"label" style=3D"background-color: #d3395a; color: #ffffff">pos=
t-wglc</span> </li>
 =20
  <li>#3880 <a href=3D"https://github.com/quicwg/base-drafts/issues/3880">H=
ow long is a validated address good for?</a> (2 by janaiyengar, martinthoms=
on) <span class=3D"label" style=3D"background-color: #fbca04; color: #00000=
0">-transport</span> </li>
 =20
  <li>#3875 <a href=3D"https://github.com/quicwg/base-drafts/issues/3875">P=
ersistent congestion threshold is unreliable during the early stages of a c=
onnection</a> (5 by ianswett, janaiyengar, kazuho) <span class=3D"label" st=
yle=3D"background-color: #fbca04; color: #000000">-recovery</span> </li>
 =20
  <li>#3842 <a href=3D"https://github.com/quicwg/base-drafts/issues/3842">D=
o I need to reset congestion info when the port changes?</a> (10 by DavidSc=
hinazi, huitema, ianswett, janaiyengar, kazuho, nharper) <span class=3D"lab=
el" style=3D"background-color: #fbca04; color: #000000">-transport</span> <=
/li>
 =20
  <li>#3834 <a href=3D"https://github.com/quicwg/base-drafts/issues/3834">R=
emove amplification throttle if the server receives Initial that echoes its=
 high entropy SCID.</a> (1 by martinthomson) <span class=3D"label" style=3D=
"background-color: #fbca04; color: #000000">-transport</span> </li>
 =20
  <li>#3831 <a href=3D"https://github.com/quicwg/base-drafts/issues/3831">P=
TO after handshake completion is not well-defined</a> (1 by kazuho) <span c=
lass=3D"label" style=3D"background-color: #fbca04; color: #000000">-recover=
y</span> </li>
 =20
  <li>#3800 <a href=3D"https://github.com/quicwg/base-drafts/issues/3800">C=
oalescing different CIDs for same connection</a> (4 by ianswett, kazuho, ma=
rten-seemann, tatsuhiro-t) <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>#3788 <a href=3D"https://github.com/quicwg/base-drafts/issues/3788">N=
ew confidentiality and integrity limits</a> (1 by DavidSchinazi) <span clas=
s=3D"label" style=3D"background-color: #fbca04; color: #000000">-tls</span>=
 </li>
  </ul>


<h3>quicwg/load-balancers (+0/-0/=F0=9F=92=AC1)</h3>

  <p>1 issues received 1 new comments:</p>
  <ul>
  <li>#41 <a href=3D"https://github.com/quicwg/load-balancers/issues/41">Si=
mplify the configuration by merging server-id and zero-pad</a> (1 by martin=
duke) </li>
  </ul>




<h2>Pull requests</h2>
<h3>quicwg/base-drafts (+5/-1/=F0=9F=92=AC20)</h3>
  <p class=3D"new">5 pull requests submitted:</p>
  <ul>
  <li>#3922 <a href=3D"https://github.com/quicwg/base-drafts/pull/3922">Rep=
lace one-off use of the word &quot;session&quot; when referring to an HTTP/=
3 connection</a> (by amirlivneh) </li>
 =20
  <li>#3921 <a href=3D"https://github.com/quicwg/base-drafts/pull/3921">fix=
ing OnAckReceived of recovery draft</a> (by kazu-yamamoto) </li>
 =20
  <li>#3917 <a href=3D"https://github.com/quicwg/base-drafts/pull/3917">Byt=
e counting at Congestion avoidance</a> (by junhochoi) </li>
 =20
  <li>#3914 <a href=3D"https://github.com/quicwg/base-drafts/pull/3914">Ack=
s for 0rtt only after Handshake Complete as in Quic-TLS 4.1.1</a> (by huite=
ma) </li>
 =20
  <li>#3909 <a href=3D"https://github.com/quicwg/base-drafts/pull/3909">Fix=
ing recovery pseudocode</a> (by kazu-yamamoto) </li>
  </ul>

  <p>5 pull requests received 20 new comments:</p>
  <ul>
  <li>#3917 <a href=3D"https://github.com/quicwg/base-drafts/pull/3917">Byt=
e counting at Congestion avoidance</a> (1 by ianswett) </li>
 =20
  <li>#3914 <a href=3D"https://github.com/quicwg/base-drafts/pull/3914">Ack=
s for 0rtt only after Handshake Complete as in Quic-TLS 4.1.1</a> (1 by hui=
tema) </li>
 =20
  <li>#3909 <a href=3D"https://github.com/quicwg/base-drafts/pull/3909">Fix=
ing recovery pseudocode</a> (12 by ianswett, junhochoi, kazu-yamamoto, mart=
en-seemann) </li>
 =20
  <li>#3889 <a href=3D"https://github.com/quicwg/base-drafts/pull/3889">No =
RTT samples, no persistent congestion</a> (5 by ianswett, janaiyengar, kazu=
ho, martinthomson) <span class=3D"label" style=3D"background-color: #fbca04=
; color: #000000">-recovery</span> <span class=3D"label" style=3D"backgroun=
d-color: #1d76db; color: #ffffff">design</span> </li>
 =20
  <li>#3874 <a href=3D"https://github.com/quicwg/base-drafts/pull/3874">All=
ow endpoints to generate traffic keys asynchronously</a> (1 by martinthomso=
n) <span class=3D"label" style=3D"background-color: #fbca04; color: #000000=
">-recovery</span> <span class=3D"label" style=3D"background-color: #fbca04=
; color: #000000">-tls</span> </li>
  </ul>

  <p>1 pull requests merged:</p>
  <ul>
  <li>#3909 <a href=3D"https://github.com/quicwg/base-drafts/pull/3909">Fix=
ing recovery pseudocode</a> </li>
  </ul>

<h3>quicwg/load-balancers (+3/-2/=F0=9F=92=AC0)</h3>
  <p class=3D"new">3 pull requests submitted:</p>
  <ul>
  <li>#45 <a href=3D"https://github.com/quicwg/load-balancers/pull/45">Rewr=
ite config rotation</a> (by martinduke) </li>
 =20
  <li>#44 <a href=3D"https://github.com/quicwg/load-balancers/pull/44">Remo=
ve zero padding field</a> (by martinduke) </li>
 =20
  <li>#43 <a href=3D"https://github.com/quicwg/load-balancers/pull/43">new =
stream test vectors</a> (by martinduke) </li>
  </ul>


  <p>2 pull requests merged:</p>
  <ul>
  <li>#45 <a href=3D"https://github.com/quicwg/load-balancers/pull/45">Rewr=
ite config rotation</a> </li>
 =20
  <li>#43 <a href=3D"https://github.com/quicwg/load-balancers/pull/43">new =
stream test vectors</a> </li>
  </ul>


<h2>Repositories tracked by this digest:</h2>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/quicwg/base-drafts">https://github.com/=
quicwg/base-drafts</a></li>
  <li><a href=3D"https://github.com/quicwg/ops-drafts">https://github.com/q=
uicwg/ops-drafts</a></li>
  <li><a href=3D"https://github.com/quicwg/datagram">https://github.com/qui=
cwg/datagram</a></li>
  <li><a href=3D"https://github.com/quicwg/load-balancers">https://github.c=
om/quicwg/load-balancers</a></li>
  <li><a href=3D"https://github.com/quicwg/version-negotiation">https://git=
hub.com/quicwg/version-negotiation</a></li>
  </ul>
</body>
</html>

--===============1411899648396878914==--


From nobody Sun Jul 19 13:07:50 2020
Return-Path: <pravb@microsoft.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 440253A082A for <quic@ietfa.amsl.com>; Sun, 19 Jul 2020 13:07:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.1
X-Spam-Level: 
X-Spam-Status: No, score=-2.1 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, DKIM_VALID_EF=-0.1, HTML_MESSAGE=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=microsoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id kN0MdD25FysP for <quic@ietfa.amsl.com>; Sun, 19 Jul 2020 13:07:46 -0700 (PDT)
Received: from NAM06-DM3-obe.outbound.protection.outlook.com (mail-eopbgr640100.outbound.protection.outlook.com [40.107.64.100]) (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 662D03A0828 for <quic@ietf.org>; Sun, 19 Jul 2020 13:07:46 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=HRcOWJDe3UtOxYTOf43ujYrU8JAoip96Zp+P9weu0SCF09OUqI6V90j5xnYrGgJTmX3wb3N3nZeCASLhTJQXstB1OpEN6ZnzBGOzn7xgsgOXakokgnJskgcg2Pi6y5nkdpz0inAWrCj+JXt4QFMez54QUyqEQCRY2qPHRE5HgB+SCJ2PGPljn0zhjpCAaOpo1pLuvAdrX6wsybWZ05HdUr+V3oiLy4S8pyJKd2xeGTkcv3oUpqMmXPoNoOGOduMgNP6epKGWYbPNoU7xo/aNrMcjEpFWh6GeutKbCR/cxSELVizNIHMQGUBq8r/zXV3vRM0WJUPkDogfb7+36Si5Ng==
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=GuL90asAys+0YxOutWy4ydFj4dNHt2ZtzLqazHQ3APk=; b=Zn5nJc/9T5PoT9OgXQ16CGWhGsxBaV0WXdjxc/pUfrr2AFG8cAFt9na/SlV7hqiFfREn23vzEqjwdCSf4gUlIwBWJX9qbeg8jpo/KXotJseJ4Fyz3UckD3ooYoTqYqbrxiymewqQxZebtHobkw+yAksMqaVyNrnZYM1OXzLh6fAN54MLw8IUfLBC7N6x/zMOUKFdC/2H+0F22Bg/C7JDBgcKAHAHurRCznMOH+EzdwfC+uv1HbWZ5qATSj78Ol8WLGBhpuT4J9SpZCgBV/4RkNu2LqjQ43+QkUT1DnZLC90kX8im6Hrl5djD8EkILaX7ryMrzoZyfPOvNIkWk+XwkA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=GuL90asAys+0YxOutWy4ydFj4dNHt2ZtzLqazHQ3APk=; b=gKltMk9VSm4mAlm0XunhGUHEvc+2XJT1Qf9jxedkA0InVnvKyptGdhExCHa77uJJR0s8lp2JqTl1DnHf+uCiXY8I1IbBeI+De9w2FYb2F8ubixmqRyopdzqzuz781PvZT4XlDCR/QH1sw+ifJph+WBZKpzNgJZ0gqcWYob1k+jY=
Received: from CH2PR00MB0726.namprd00.prod.outlook.com (2603:10b6:610:ad::12) by CH2PR00MB0854.namprd00.prod.outlook.com (2603:10b6:610:ad::18) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3249.0; Sun, 19 Jul 2020 20:07:32 +0000
Received: from CH2PR00MB0726.namprd00.prod.outlook.com ([fe80::7562:9640:814e:c7f1]) by CH2PR00MB0726.namprd00.prod.outlook.com ([fe80::7562:9640:814e:c7f1%8]) with mapi id 15.20.3249.000; Sun, 19 Jul 2020 20:07:32 +0000
From: Praveen Balasubramanian <pravb@microsoft.com>
To: Jana Iyengar <jri.ietf@gmail.com>, QUIC WG <quic@ietf.org>
Subject: RE: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
Thread-Topic: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
Thread-Index: AdZVbt/Rv8RxmVSLQP+4+5gZJ/6HOgHF7XUAAAjEaQAAV28pEA==
Date: Sun, 19 Jul 2020 20:07:32 +0000
Message-ID: <CH2PR00MB07269A73542DBC8E51E95519B67A0@CH2PR00MB0726.namprd00.prod.outlook.com>
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <9f57b20d-2eba-b2b9-d8c8-48e019c8952a@wizmail.org> <CACpbDccrpHeP5PYGCZky+AN2gC9YSs5gbAzYr4Yrw1LpvHZNiA@mail.gmail.com>
In-Reply-To: <CACpbDccrpHeP5PYGCZky+AN2gC9YSs5gbAzYr4Yrw1LpvHZNiA@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=true; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2020-07-19T20:07:30Z;  MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=857f2cc5-377c-4bff-ace4-93d409d2e71f; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [2001:4898:80e8:a:95ce:3f73:f682:d302]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: bd8b843e-1a35-43bf-d04c-08d82c1f5f11
x-ms-traffictypediagnostic: CH2PR00MB0854:
x-microsoft-antispam-prvs: <CH2PR00MB08546BA280578397AEB35DF5B67A1@CH2PR00MB0854.namprd00.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: +YMePQzYEs59BIQPvRQEWRoLciGxgcbMfSDGMRWWZMBbzeTYt4b1lwnFIAxMdabsfjBp5WYnGnThd8h0GhWUfcfhbG34uDGTtDWCIZHEQvtpakCcWBSsumEcbpD2BbIGFGKHr4fkzREQxu+2FjCkoPZulQU8APYJVOGwYXJYjAqpPSls1e2r+o4LpSkkQhc60H/XCTXvu/gIvHLGEKY7oNK3NMbsyGqAA4i+/BRtsmvrG9tjC9Lm/1MDE00Mmt7dDWOKxwgeqgE0eMurwqokb/TGZTEhgKPXJcY2BQdnofBVL11DhRQDO2Iu2Ep91EwGXiGyQ91nr4k9ERWaC+BtuA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:CH2PR00MB0726.namprd00.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(366004)(396003)(136003)(39860400002)(346002)(376002)(316002)(8990500004)(71200400001)(33656002)(478600001)(110136005)(64756008)(8676002)(186003)(76116006)(8936002)(66946007)(66476007)(66556008)(5660300002)(86362001)(82960400001)(82950400001)(66446008)(53546011)(6506007)(7696005)(66574015)(55016002)(9686003)(2906002)(10290500003)(52536014)(83380400001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: cd8k/0roAWLBKPs81o+SZWmPNRF/rMWJ+vbR9M7jYZq295WrurYarJJ7WrucuOocyF/LcMPezRn+82EhlBocM9hmWK/dZJFiYfwrIYEQGSIYiI9UAIu8EnYf+QeMarTrjJNfVuUyjgecHmn92g4psaxsOmOKwziqeDUPft6LgO3naYG2ePv6GiIlrfnr+XeMUcSbwI4B+D5WV+MxD/u4KCb5ktVI45XzCNvClxd+8mr/oZKaddcQXibRBB6bu3mykrzEJ/g3mMdjMLRRFVObqx7glJq/2AwNGtOMsG9sBMJy23/Vjc+PJ4kdJI//SQlkBYntDe41ysOKLptUvBKU70DGWCj76XZrjvXxZBL+lJIsaJNQXUe0xUBDmQk7Vroa2DqlfkhQKt9bQ9YlcZZ5rIr12lv59ry0qQlzC8Tf2ZAnrOWukKyeqx97KDCuaS+9/s5bumz3U4wOAYg13NdYttBDgQGpZZ8m1fUeNhV+l+mv7zZQM7JPkncYNMgrz4liEPYlTkh8CvBGuwVA+mBHFuE65KhJsVae7/V7QhL+NpRR4Prh9ogajYwZSdz6NjSgwV6ux95KoyHoAyeCbEEoWLjz3xykNQJw+B2D29yeIaSFqUagBWofiCBNkVN0/iU+0jhjRabwSlioHmbB2iUtVKjpxQ8GdyzuQJPKNaSM+MjeEHYIVA48OPMSB4cTuO2JrshQrUt0cBVLOGO6dakUhw==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_CH2PR00MB07269A73542DBC8E51E95519B67A0CH2PR00MB0726namp_"
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CH2PR00MB0726.namprd00.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: bd8b843e-1a35-43bf-d04c-08d82c1f5f11
X-MS-Exchange-CrossTenant-originalarrivaltime: 19 Jul 2020 20:07:32.1784 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: urBVayjRGv+AmDNyW8Gimyt/QWW4lvfkF9AnfFDlAqNYAaxeiPDKyb+yFYvEdYY7oHyUbkgl5gU2jrGW03C/a5U/7wZlpv+xsviDkEZIx9o=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR00MB0854
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Ay3nbRXIFItsamVbiQkM7waQ6kU>
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, 19 Jul 2020 20:07:48 -0000

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

Pj4gVGhlcmUncyBhIHdheSBvZiBzYXRpc2Z5aW5nIGJvdGggZGVzaXJlczogaGF2ZSB0aGUgTklD
IGhhbmRsZSB0aGUgcGFjaW5nLg0KWWVzIGxldHRpbmcgdGhlIE5JQyBoYW5kbGUgcGFjaW5nIHdp
bGwgbWFrZSBpbXByb3ZlIENQVSBlZmZpY2llbmN5IGFuZCBpbXByb3ZlIGFjY3VyYWN5IGR1ZSB0
byBmaW5lIGdyYWluZWQgaGFyZHdhcmUgdGltZXJzLiBCdXQgdGhhdOKAmXMgaW4gdGhlIGZ1dHVy
ZS4gVG9kYXnigJlzIE5JQ3MgZG9u4oCZdCBwYWNlIGxhcmdlIHNlbmQgb2ZmbG9hZHMgZm9yIFRD
UCBvciBVRFAuDQoNCj4+IFBlcmhhcHMgd2UgY2FuIGhhdmUgYSBwcmluY2lwbGUgaGVyZTogcmVj
b21tZW5kYXRpb25zIHRoYXQgYXJlIHNwZWNpZmljIGZvciBJbnRlcm5ldCB1c2UgYXJlIGp1c3Qg
dGhhdCwgYW5kIHdlIHVzZSBTSE9VTERzIGZvciB0aG9zZS4gSVcxMCBtYWtlcyBzZW5zZSBiYXNl
ZCBvbiB0aGlzLCBhbmQgSSB3b3VsZCB0aGVuIGFsc28gYmUgZmluZSB3aXRoIGNoYW5naW5nIHRo
ZSBNVVNUIHRvIGEgU0hPVUxELiBQZXJoYXBzIHdlIGNhbiBzdGF0ZSB0aGlzIHByaW5jaXBsZSB1
cGZyb250Lg0KSSBsaWtlIHRoZSBpZGVhIG9mIHN0YXRpbmcgdGhhdCBwcmluY2lwbGUgdXAgZnJv
bnQuIFNIT1VMRCB3b3VsZCBiZSBzdWZmaWNpZW50IHJlc29sdXRpb24gZm9yIHRoZSBidXJzdCBz
aXplIGlzc3VlLg0KDQpGcm9tOiBRVUlDIDxxdWljLWJvdW5jZXNAaWV0Zi5vcmc+IE9uIEJlaGFs
ZiBPZiBKYW5hIEl5ZW5nYXINClNlbnQ6IEZyaWRheSwgSnVseSAxNywgMjAyMCA3OjE4IFBNDQpU
bzogUVVJQyBXRyA8cXVpY0BpZXRmLm9yZz4NClN1YmplY3Q6IFtFWFRFUk5BTF0gUmU6IFdHTEMg
cmV2aWV3IG9mIGRyYWZ0LWlldGYtcXVpYy1yZWNvdmVyeS0yOQ0KDQpUaGVyZSdzIGEgcHJvdG9j
b2wgcXVlc3Rpb24gYW5kIHRoZXJlJ3MgYSBxdWVzdGlvbiBvZiBlbmRwb2ludCBiZWhhdmlvci4g
SW4gdGVybXMgb2YgdGhlIHByb3RvY29sIGl0c2VsZiwgeWVzLCB0aGVyZSdzIG5vIHJlYWwgbmVl
ZCB0byBkaXN0aW5ndWlzaCBiZXR3ZWVuIEludGVybmV0IGFuZCBEQyBlbnZpcm9ubWVudHM7IHdl
J3ZlIHRyaWVkIHRvIGVuc3VyZSB0aGF0IHRoZSBwcm90b2NvbCBjYW4gYmUgdXNlZCBicm9hZGx5
LiBNeSBwb2ludCB3YXMgdGhhdCB0aGUgY29uc3RhbnRzIGluIHRoZSBzcGVjIHdlcmUgYmFzZWQg
b24gd2hhdCB3ZSBiZWxpZXZlIHRvIGJlIHRydWUgZm9yIHRoZSBwdWJsaWMgSW50ZXJuZXQsIGFu
ZCBub3QgZm9yIERDIGVudmlyb25tZW50cy4NCg0KVGhhdCBzYWlkLCBwZXJoYXBzIEkgd2FzIGEg
Yml0IHRvbyBoYXN0eS4gSVcxMCBhbmQgSW5pdGlhbFJUVCB2YWx1ZXMgYXJlIHRoZSBvdGhlcnMg
SSB3YXMgdGhpbmtpbmcgYWJvdXQsIGJ1dCB0aG9zZSBhcmUgcmVjb21tZW5kYXRpb25zIGluIHRo
ZSBzcGVjLCBub3QgcmVxdWlyZW1lbnRzLiBBbmQgYXMgSWFuIG5vdGVzLCB0aGVyZSdzIG5vIG1p
bmltdW0gdGltZW91dCBhbnltb3JlLg0KDQpQZXJoYXBzIHdlIGNhbiBoYXZlIGEgcHJpbmNpcGxl
IGhlcmU6IHJlY29tbWVuZGF0aW9ucyB0aGF0IGFyZSBzcGVjaWZpYyBmb3IgSW50ZXJuZXQgdXNl
IGFyZSBqdXN0IHRoYXQsIGFuZCB3ZSB1c2UgU0hPVUxEcyBmb3IgdGhvc2UuIElXMTAgbWFrZXMg
c2Vuc2UgYmFzZWQgb24gdGhpcywgYW5kIEkgd291bGQgdGhlbiBhbHNvIGJlIGZpbmUgd2l0aCBj
aGFuZ2luZyB0aGUgTVVTVCB0byBhIFNIT1VMRC4gUGVyaGFwcyB3ZSBjYW4gc3RhdGUgdGhpcyBw
cmluY2lwbGUgdXBmcm9udC4NCg0KSWFuLCBJIHNoYXJlIHlvdXIgaGVzaXRhdGlvbiB0aGF0IHdl
IGRvbid0IHdhbnQgdG8gbWFrZSBhIGRpc3RpbmN0aW9uIGJldHdlZW4gcHJpdmF0ZSBhbmQgcHVi
bGljIG5ldHdvcmtzLCBidXQgd2UgYWxyZWFkeSBhbGxvdyBmb3IgaW1wbGVtZW50YXRpb25zIHRv
IGRvIHRoYXQgd2l0aCBhIGRpZmZlcmVudCBJVyBhbmQgSW5pdGlhbCBSVFQuIElzIGl0IGRpZmZl
cmVudCB3aGVuIHRhbGtpbmcgYWJvdXQgYnVyc3QgbGltaXRzPw0KDQoNCk9uIEZyaSwgSnVsIDE3
LCAyMDIwIGF0IDM6MDcgUE0gSmVyZW15IEhhcnJpcyA8amdoQHdpem1haWwub3JnPG1haWx0bzpq
Z2hAd2l6bWFpbC5vcmc+PiB3cm90ZToNCk9uIDA4LzA3LzIwMjAgMjI6MjksIFByYXZlZW4gQmFs
YXN1YnJhbWFuaWFuIHdyb3RlOg0KPiBTZWN0aW9uIDcuOQ0KPiAiSW1wbGVtZW50YXRpb25zIE1V
U1QgZWl0aGVyIHVzZSBwYWNpbmcgb3IgYW5vdGhlciBtZXRob2QgdG8gbGltaXQgc3VjaCBidXJz
dHMgdG8gdGhlIGluaXRpYWwgY29uZ2VzdGlvbiB3aW5kb3c7IHNlZSBTZWN0aW9uIDcuMi4iDQo+
IFRoaXMgc2VlbXMgdG8gcHJlY2x1ZGUgdXNlIG9mIHNlZ21lbnRhdGlvbiBvZmZsb2FkIG9mIHNp
emVzIGdyZWF0ZXIgdGhhbiBJVy4uIEluIGRhdGFjZW50ZXJzIHdlIHJvdXRpbmVseSBzZW5kIGJ1
cnN0cyB0aGF0IGFyZSBoaWdoZXIgd2l0aG91dCBjYXVzaW5nIGxvc3MuIFRoZSBNVVNUIGhlcmUg
c2VlbXMgdW5uZWNlc3NhcnkuIEl0IGFsc28gY29uZmxpY3RzIHdpdGggdGhlIFJFQ09NTUVOREVE
IGluIGFuIGVhcmxpZXIgc2VudGVuY2UuDQoNClRoZXJlJ3MgYSB3YXkgb2Ygc2F0aXNmeWluZyBi
b3RoIGRlc2lyZXM6IGhhdmUgdGhlIE5JQyBoYW5kbGUgdGhlDQpwYWNpbmcuDQotLQ0KQ2hlZXJz
LA0KICBKZXJlbXkNCg==

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KLyogU3R5bGUgRGVmaW5pdGlvbnMgKi8NCnAuTXNvTm9ybWFsLCBsaS5Nc29Ob3JtYWws
IGRpdi5Nc29Ob3JtYWwNCgl7bWFyZ2luOjBpbjsNCglmb250LXNpemU6MTEuMHB0Ow0KCWZvbnQt
ZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsN
Cgl7bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9u
OnVuZGVybGluZTt9DQpzcGFuLkVtYWlsU3R5bGUxOA0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25h
bC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5k
b3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0K
CWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmO30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0K
CXtzaXplOjguNWluIDExLjBpbjsNCgltYXJnaW46MS4waW4gMS4waW4gMS4waW4gMS4waW47fQ0K
ZGl2LldvcmRTZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1b
aWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1h
eD0iMTAyNiIgLz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0K
PG86c2hhcGVsYXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9
IjEiIC8+DQo8L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9k
eSBsYW5nPSJFTi1VUyIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJX
b3JkU2VjdGlvbjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+Jmd0OyZndDsgVGhlcmUncyBhIHdh
eSBvZiBzYXRpc2Z5aW5nIGJvdGggZGVzaXJlczogaGF2ZSB0aGUgTklDIGhhbmRsZSB0aGUgcGFj
aW5nLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+WWVzIGxldHRpbmcgdGhl
IE5JQyBoYW5kbGUgcGFjaW5nIHdpbGwgbWFrZSBpbXByb3ZlIENQVSBlZmZpY2llbmN5IGFuZCBp
bXByb3ZlIGFjY3VyYWN5IGR1ZSB0byBmaW5lIGdyYWluZWQgaGFyZHdhcmUgdGltZXJzLiBCdXQg
dGhhdOKAmXMgaW4gdGhlIGZ1dHVyZS4gVG9kYXnigJlzIE5JQ3MgZG9u4oCZdCBwYWNlIGxhcmdl
IHNlbmQgb2ZmbG9hZHMgZm9yIFRDUCBvciBVRFAuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPiZn
dDsmZ3Q7IFBlcmhhcHMgd2UgY2FuIGhhdmUgYSBwcmluY2lwbGUgaGVyZTogcmVjb21tZW5kYXRp
b25zIHRoYXQgYXJlIHNwZWNpZmljIGZvciBJbnRlcm5ldCB1c2UgYXJlIGp1c3QgdGhhdCwgYW5k
IHdlIHVzZSBTSE9VTERzIGZvciB0aG9zZS4gSVcxMCBtYWtlcyBzZW5zZSBiYXNlZCBvbiB0aGlz
LCBhbmQgSSB3b3VsZCB0aGVuIGFsc28gYmUgZmluZSB3aXRoIGNoYW5naW5nIHRoZSBNVVNUIHRv
IGEgU0hPVUxELiBQZXJoYXBzDQogd2UgY2FuIHN0YXRlIHRoaXMgcHJpbmNpcGxlIHVwZnJvbnQu
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5JIGxpa2UgdGhlIGlkZWEgb2Yg
c3RhdGluZyB0aGF0IHByaW5jaXBsZSB1cCBmcm9udC4gU0hPVUxEIHdvdWxkIGJlIHN1ZmZpY2ll
bnQgcmVzb2x1dGlvbiBmb3IgdGhlIGJ1cnN0IHNpemUgaXNzdWUuDQo8bzpwPjwvbzpwPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdiBzdHlsZT0i
Ym9yZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQg
MGluIDBpbiAwaW4iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+RnJvbTo8L2I+IFFVSUMgJmx0
O3F1aWMtYm91bmNlc0BpZXRmLm9yZyZndDsgPGI+T24gQmVoYWxmIE9mIDwvYj4NCkphbmEgSXll
bmdhcjxicj4NCjxiPlNlbnQ6PC9iPiBGcmlkYXksIEp1bHkgMTcsIDIwMjAgNzoxOCBQTTxicj4N
CjxiPlRvOjwvYj4gUVVJQyBXRyAmbHQ7cXVpY0BpZXRmLm9yZyZndDs8YnI+DQo8Yj5TdWJqZWN0
OjwvYj4gW0VYVEVSTkFMXSBSZTogV0dMQyByZXZpZXcgb2YgZHJhZnQtaWV0Zi1xdWljLXJlY292
ZXJ5LTI5PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoZXJlJ3MgYSBw
cm90b2NvbCBxdWVzdGlvbiBhbmQgdGhlcmUncyBhIHF1ZXN0aW9uIG9mIGVuZHBvaW50IGJlaGF2
aW9yLiBJbiB0ZXJtcyBvZiB0aGUgcHJvdG9jb2wgaXRzZWxmLCB5ZXMsIHRoZXJlJ3Mgbm8gcmVh
bCBuZWVkIHRvIGRpc3Rpbmd1aXNoIGJldHdlZW4gSW50ZXJuZXQgYW5kIERDIGVudmlyb25tZW50
czsgd2UndmUgdHJpZWQgdG8gZW5zdXJlIHRoYXQgdGhlIHByb3RvY29sIGNhbiBiZSB1c2VkDQog
YnJvYWRseS4gTXkgcG9pbnQgd2FzIHRoYXQgdGhlIGNvbnN0YW50cyZuYnNwO2luIHRoZSBzcGVj
IHdlcmUgYmFzZWQgb24gd2hhdCB3ZSBiZWxpZXZlIHRvIGJlIHRydWUgZm9yIHRoZSBwdWJsaWMg
SW50ZXJuZXQsIGFuZCBub3QgZm9yIERDIGVudmlyb25tZW50cy48bzpwPjwvbzpwPjwvcD4NCjxk
aXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0K
PGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPlRoYXQgc2FpZCwgcGVyaGFwcyBJIHdhcyBhIGJp
dCB0b28gaGFzdHkuIElXMTAgYW5kIEluaXRpYWxSVFQgdmFsdWVzIGFyZSB0aGUgb3RoZXJzIEkg
d2FzIHRoaW5raW5nIGFib3V0LCBidXQgdGhvc2UgYXJlJm5ic3A7cmVjb21tZW5kYXRpb25zIGlu
IHRoZSBzcGVjLCBub3QgcmVxdWlyZW1lbnRzLiBBbmQgYXMgSWFuIG5vdGVzLCB0aGVyZSdzIG5v
IG1pbmltdW0gdGltZW91dCBhbnltb3JlLjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5QZXJoYXBzIHdlIGNhbiBoYXZlIGEgcHJpbmNpcGxlIGhl
cmU6IHJlY29tbWVuZGF0aW9ucyB0aGF0IGFyZSBzcGVjaWZpYyBmb3IgSW50ZXJuZXQgdXNlIGFy
ZSBqdXN0IHRoYXQsIGFuZCB3ZSB1c2UgU0hPVUxEcyBmb3IgdGhvc2UuIElXMTAgbWFrZXMgc2Vu
c2UgYmFzZWQgb24gdGhpcywgYW5kIEkgd291bGQgdGhlbiBhbHNvIGJlIGZpbmUgd2l0aCBjaGFu
Z2luZyB0aGUgTVVTVCB0byBhIFNIT1VMRC4gUGVyaGFwcw0KIHdlIGNhbiBzdGF0ZSB0aGlzIHBy
aW5jaXBsZSB1cGZyb250LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIj5JYW4sIEkgc2hhcmUgeW91ciBoZXNpdGF0aW9uIHRoYXQgd2UgZG9uJ3Qg
d2FudCB0byBtYWtlIGEgZGlzdGluY3Rpb24gYmV0d2VlbiBwcml2YXRlIGFuZCBwdWJsaWMgbmV0
d29ya3MsJm5ic3A7YnV0IHdlIGFscmVhZHkgYWxsb3cgZm9yIGltcGxlbWVudGF0aW9ucyB0byBk
byB0aGF0IHdpdGggYSBkaWZmZXJlbnQmbmJzcDtJVyBhbmQgSW5pdGlhbCBSVFQuIElzIGl0IGRp
ZmZlcmVudCB3aGVuIHRhbGtpbmcgYWJvdXQgYnVyc3QNCiBsaW1pdHM/PG86cD48L286cD48L3A+
DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwv
cD4NCjwvZGl2Pg0KPC9kaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+T24gRnJpLCBKdWwgMTcs
IDIwMjAgYXQgMzowNyBQTSBKZXJlbXkgSGFycmlzICZsdDs8YSBocmVmPSJtYWlsdG86amdoQHdp
em1haWwub3JnIj5qZ2hAd2l6bWFpbC5vcmc8L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4N
CjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlk
ICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowaW4gMGluIDBpbiA2LjBwdDttYXJnaW4tbGVmdDo0Ljhw
dDttYXJnaW4tcmlnaHQ6MGluIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtYXJnaW4t
Ym90dG9tOjEyLjBwdCI+T24gMDgvMDcvMjAyMCAyMjoyOSwgUHJhdmVlbiBCYWxhc3VicmFtYW5p
YW4gd3JvdGU6PGJyPg0KJmd0OyBTZWN0aW9uIDcuOTxicj4NCiZndDsgJnF1b3Q7SW1wbGVtZW50
YXRpb25zIE1VU1QgZWl0aGVyIHVzZSBwYWNpbmcgb3IgYW5vdGhlciBtZXRob2QgdG8gbGltaXQg
c3VjaCBidXJzdHMgdG8gdGhlIGluaXRpYWwgY29uZ2VzdGlvbiB3aW5kb3c7IHNlZSBTZWN0aW9u
IDcuMi4mcXVvdDs8YnI+DQomZ3Q7IFRoaXMgc2VlbXMgdG8gcHJlY2x1ZGUgdXNlIG9mIHNlZ21l
bnRhdGlvbiBvZmZsb2FkIG9mIHNpemVzIGdyZWF0ZXIgdGhhbiBJVy4uIEluIGRhdGFjZW50ZXJz
IHdlIHJvdXRpbmVseSBzZW5kIGJ1cnN0cyB0aGF0IGFyZSBoaWdoZXIgd2l0aG91dCBjYXVzaW5n
IGxvc3MuIFRoZSBNVVNUIGhlcmUgc2VlbXMgdW5uZWNlc3NhcnkuIEl0IGFsc28gY29uZmxpY3Rz
IHdpdGggdGhlIFJFQ09NTUVOREVEIGluIGFuIGVhcmxpZXIgc2VudGVuY2UuPGJyPg0KPGJyPg0K
VGhlcmUncyBhIHdheSBvZiBzYXRpc2Z5aW5nIGJvdGggZGVzaXJlczogaGF2ZSB0aGUgTklDIGhh
bmRsZSB0aGU8YnI+DQpwYWNpbmcuPGJyPg0KLS0gPGJyPg0KQ2hlZXJzLDxicj4NCiZuYnNwOyBK
ZXJlbXk8bzpwPjwvbzpwPjwvcD4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jv
ZHk+DQo8L2h0bWw+DQo=

--_000_CH2PR00MB07269A73542DBC8E51E95519B67A0CH2PR00MB0726namp_--


From nobody Sun Jul 19 17:11:16 2020
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 4565C3A0BCD for <quic@ietfa.amsl.com>; Sun, 19 Jul 2020 17:11:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=VruUdrg2; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=lIzM1B62
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tFs5g_iKYSvA for <quic@ietfa.amsl.com>; Sun, 19 Jul 2020 17:11:13 -0700 (PDT)
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 18BDD3A0BCC for <quic@ietf.org>; Sun, 19 Jul 2020 17:11:12 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id 948F75C014F for <quic@ietf.org>; Sun, 19 Jul 2020 20:11:11 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Sun, 19 Jul 2020 20:11:11 -0400
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=fm2; bh=FBArCgqxw9Hs06cvjzbs8iPmeLEFP20 1Km5UfNW3/cY=; b=VruUdrg2snH5pBUEWJP3hgzcQR0kkyYbjJXLkx3c5pDdsJs rdQGLsomoF1MtKA8IsXrcnXgeswqt27EN8DHiKfKTz20niJvTWrvnaDTgZSWALef slWjqR3sfxb3JHpteF5bdZMfZWTvNh5JnR5jlejNBhADx0QRerze6ECWnvVdxFTe DqGFVhq9g6pSBLLOEU4h9rh6ul7mlgM10sT9dN5WyCEeUN90CMwE/sjlfCqJEr25 fFV9ZOXnKLVwOa0OBj5pQPyYc2WpikvyOZF0RMQM1/ydwAlxFdMF8Qay1XY/QF3Z R1vYc5d5kqmlj7/BddPuzAY40cme//SXMCiFogw==
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=fm3; bh=FBArCg qxw9Hs06cvjzbs8iPmeLEFP201Km5UfNW3/cY=; b=lIzM1B62d7ZkuPF+eLVnNH OIGsAWSw3C2HHVlFkSgkq00Lg5bc6EKKfKSDrYVWVXH6E5MhIjITO8Gc2mcKqvrN rn/sLpAcav/wKTn6NVJ0qjs/5SDqsMCGWKLRMwhpMtWd+FSTJqm+F0cpSoXwT3o4 pJjO4xD4u/4JWCnKPuOj/b2DaWrlmWqXG7iMBaaxSBdos5dVUenkN2Xu/oVayhnh oAUq5dXyGOCArMS3qt1fW1Yam2MdiFGTxXL+XkwGNZokWUOsL28sMhRISkijMrRw J/aGT1YOhIMoTxCx2feo6Dv6LlFfa6v16S3fi6R7dSU16/yGWxdVJJuaqfVWH5Tw ==
X-ME-Sender: <xms:H-EUXwF_6aZCTBvx-iTEpIA3WjHEz8koq8MuuqqHmr7dGtzZcmT2qw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrgedvgdeffecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif vghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepkeetueeikedtkeelfeekve fhkeffvedvvefgkefgleeugfdvjeejgeffieegtdejnecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:H-EUX5UVaBQiqBs_u1SyyAxxmVnLnmZU4aPRM-rJXJYpPd3LFKrGeQ> <xmx:H-EUX6JmcUYzHMtwvKmbiL0JySE0-yqLYYbSGi-8zElh-P9rinTEUQ> <xmx:H-EUXyGruT7Tg2TWyZFcYPOStVtxCCsmvo9iZXY1CgH9lQ5PeGAXvQ> <xmx:H-EUX_VGrtxn55w7nQgiHPQWAWORu_1C2GybJzjDdNlXVJ5yPlf1Wg>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 373D4E00A8; Sun, 19 Jul 2020 20:11:11 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-52-g083df19-fm-idx2020-20200715.003-g083df194
Mime-Version: 1.0
Message-Id: <28d46380-620a-4448-b471-403048e0117e@www.fastmail.com>
In-Reply-To: <CACpbDcctB0nX2yTxHQEs6UcUCTH0WdfiNAPfpRKe3oH-0aYZYA@mail.gmail.com>
References: <CACpbDcctB0nX2yTxHQEs6UcUCTH0WdfiNAPfpRKe3oH-0aYZYA@mail.gmail.com>
Date: Mon, 20 Jul 2020 10:10:51 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: quic@ietf.org
Subject: Re: Handshake processing delays and impact on recovery
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/r8Ldv7Hwf-6iuqgcuuZtWaxrHAw>
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, 20 Jul 2020 00:11:14 -0000

Hi Jana,

Thanks for writing this up.  I think that this is a good fix, even a necessary one.

On Fri, Jul 17, 2020, at 19:00, Jana Iyengar wrote:
> We think this holds up, but we'd like to get this under everyone's 
> eyes, to ensure that the discussion isn't missing subtle deadlock 
> issues.

I have satisfied myself that this is OK.  The only 1-RTT (or 0-RTT) packet content we depend on to get to "handshake confirmed" is the HANDSHAKE_DONE frame.  As this is sent by the server after confirming the handshake, it will be sent on PTO as normal.  Were this not the case, this would be disastrous as we couldn't rely on this getting through.

> - endpoints ignore max_ack_delay for acknowledgements of packets that 
> were sent prior to handshake confirmation. Those are the ones that 
> might have been buffered at the peer until keys were ready.

For this, endpoints need to retain an additional value: the highest packet number that was sent prior to confirmation (or the lowest packet number sent after confirmation).  It's a little annoying to have to do that, but it seems necessary.


From nobody Mon Jul 20 07:15:17 2020
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 86F7B3A0AFD for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 07:15:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level: 
X-Spam-Status: No, score=-17.599 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, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, 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 eVOUog3YBr5N for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 07:15:13 -0700 (PDT)
Received: from mail-yb1-xb36.google.com (mail-yb1-xb36.google.com [IPv6:2607:f8b0:4864:20::b36]) (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 4B77D3A0AFB for <quic@ietf.org>; Mon, 20 Jul 2020 07:15:13 -0700 (PDT)
Received: by mail-yb1-xb36.google.com with SMTP id 134so8352692ybd.6 for <quic@ietf.org>; Mon, 20 Jul 2020 07:15:13 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=o5FeDvGtENL7BTmS9djfLrH+JfukYR2f8DnKE9loUws=; b=npQVczIcfJ+x9Z1PzPY9SGD8pbakXQR7BL9sc0jlapcNqA10/sTkjm24QhrxCkuCwp 2f7IfVCKqFkjjvfpfbicieLnB+dumt+ID5y7gw9mjrld1CdiWBiuVDT4DYHGHwAsk0hu BtnNCRd0EVhVmiNkmjiKDIQglSgxuEKgCdLL2ULQqtRdf571XLCiF6Yf+xVlXo5OxDnG aZIkdffeIsQLwJ6ULNCij6rKysy/3qlBxlK/RVBTj5/bdleWyILl5UCat9nN1mVV7q16 7scKVjAm7uo2UDDiHUDtnoWvde/Tdg4OVYyFLso8du1a1d/1F5AzBPbFGGWHuKd+yS/l ylCQ==
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=o5FeDvGtENL7BTmS9djfLrH+JfukYR2f8DnKE9loUws=; b=lsa4CsoKmFYJWbYvytM5VwZvCnvHCGPlbEWME7FhNHEC+5pThmFcY6YeJGToNMHtRr vAM7JY0W1ofaKU/NIHQkU7fNYw6PQW/Jq7FeuSquhS1HYjycdBIKaLPsK5mzSFFFmx+h M6zziMEML55dv0X+G3D6s62Xp08e6c/U70acDNQ58nXnhy0BT4qvCU40vmcAJaZknPr3 XzFnwpxDWaI9K3GQ56DOnbbKO5bhtrZw1FPKTY/urq+M1/WGPgoA6TBGBVuZh5wcsuPJ hwYsmLGgFDtFfDKyEof1ahYd3bIbzpN5dH6p6PkigedcfZflPniZvCDcjMKFEP9fL8TZ jrOQ==
X-Gm-Message-State: AOAM530vtCiHToaNjvdCbvFmfZwe8gdOANzz+A+Vn8R/phrkDQlWeHeQ PdKj3MTx+nPdY+7sB905x1uLtr2sE/ys8hBIKoje8Q==
X-Google-Smtp-Source: ABdhPJykQ/crMq3hnVdGGTF/rtwiATXaT07qKFBxdmcltnPsgCA7YwmF7T/pTbiu85dXYBKtKos8byKSXymqcnJVTQI=
X-Received: by 2002:a25:b78a:: with SMTP id n10mr33393175ybh.494.1595254512039;  Mon, 20 Jul 2020 07:15:12 -0700 (PDT)
MIME-Version: 1.0
References: <CABC-CqayJAeipEhsTf4h8rkUVQvYLd=1wF4UBMkaYSNMfvgnXw@mail.gmail.com> <CADdTf+jxKyPw_zfJ6FWCz230rXqg83d7rQJhKBteBvoLCut1RQ@mail.gmail.com> <CAKKJt-dgEmOtvXR8hVT9qf+YgSe3m9LMUuE6=csU28j+j1V_ZQ@mail.gmail.com> <CACpbDce=G=ou1F5dQx3r+TbzACrJRkQkKO7OviTHvd2QxFKTyg@mail.gmail.com>
In-Reply-To: <CACpbDce=G=ou1F5dQx3r+TbzACrJRkQkKO7OviTHvd2QxFKTyg@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Mon, 20 Jul 2020 10:14:59 -0400
Message-ID: <CAKcm_gMsW=AC6_HhzidXgk_qL9Y1K78F8exEytQFYdTNQaq4xg@mail.gmail.com>
Subject: Re: Questions about recovery draft 29
To: Jana Iyengar <jri.ietf@gmail.com>
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, IETF QUIC WG <quic@ietf.org>,  Jonas Reynders <jonas.reynders@student.uhasselt.be>, Matt Joras <matt.joras@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000084cfaf05aae0225e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/1-RUOlH7SKXoPFKmgwcy1TWt6lc>
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, 20 Jul 2020 14:15:16 -0000

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

+1 to Jana's point about QUIC not having a TCP-style sequence number, so
it's always time-based in some sense.

There was a recent discussion of whether adaptive thresholds should be
recommended(Issue #3571 <https://github.com/quicwg/base-drafts/issues/3571>=
)
which I opened after running experiments and enabling adaptive packet
thresholds by default in the Chromium implementation.  The current text
contains the consensus decision to highlight the value of adaptive
reordering, but not make any normative statements.

For TLP and PTO, QUIC recovery started with both, but it added excess
complexity without any recognizable value, so they were merged into PTO.
Even when both TLP and RTO existed in the recovery draft, they were subtly
different from TCP's, so a new mechanism with a new name made sense.

On Fri, Jul 17, 2020 at 11:15 PM Jana Iyengar <jri.ietf@gmail.com> wrote:

> Spencer,
>
> It's a good idea, but I think it's a bit early to think of a roadmap. The
> core protocol components necessary for QUIC are exactly the three documen=
ts
> we have right now, nothing more. Once we have more extensions, other
> changes in more drafts, it might make sense to think of a roadmap.
>
> - jana
>
> On Mon, Jul 13, 2020 at 7:40 AM Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
>
>> Just to chime in here, so top-posting.
>>
>> Matt is correct (that specifications !=3D implementations), but I note t=
hat
>> the transport area has produced, and revised,
>> https://datatracker.ietf..org/doc/rfc7414/
>> <https://datatracker.ietf.org/doc/rfc7414/> (A Roadmap for Transmission
>> Control Protocol (TCP) Specification Documents", that go through what Ma=
tt
>> characterized as the 'myriad RFCs that loosely define "IETF TCP"'
>>
>> The TCP community used Informational RFCs to document what's a good idea
>> and what's a bad idea at the per-specification level ("really important =
to
>> implement this, that is a really bad idea so don't implement it", becaus=
e
>> RFCs were the tools we have.
>>
>> It might be worth thinking about the form a "QUIC Roadmap" might take,
>> given that we now have wikis, gitbub, and other tools that could allow t=
he
>> QUIC roadmap and implementations to be more aware of each other, especia=
lly
>> if this was more granular than "this document".
>>
>> We talked about this briefly at IETF 106 in TSVAREA. From the minutes at
>> https://datatracker.ietf.org/meeting/106/materials/minutes-106-tsvarea-0=
2
>>  ...
>>
>>    - Ted: Lots of creativity right now. people need to understand what
>>    they are doing *to* the protocol, not just *with* it. We should write=
 "the
>>    hitchhiker's guide to QUIC". Intended for all audiences.
>>    - Mirja: That's what applicability and mgmt docs are for.
>>    - Ted: That's not what I'm looking for.
>>    - Spencer: Imagine if TCP roadmap had started before there were 150
>>    RFCs!
>>
>> Did people have thoughts about that?
>>
>> Best,
>>
>> Spencer
>>
>>
>> On Thu, Jul 9, 2020 at 2:10 PM Matt Joras <matt.joras@gmail.com
>> <matt..joras@gmail.com>> wrote:
>>
>>> I won't offer specific answers to all your questions as Ian or Jana
>>> likely have better ones, however I'd like to make a general point
>>> about this line of questioning: Linux TCP !=3D IETF TCP, or, said
>>> another way, Implementations and Specifications are not the same
>>> thing. Recall that QUIC is a series of specifications being developed
>>> by the IETF, similar to the myriad RFCs that loosely define "IETF
>>> TCP". Linux's TCP stack is one such interpretation/implementation of
>>> TCP, and while it can inform the decisions of IETF workings, it should
>>> not be an undue determiner of the development of said specifications.
>>> Similarly we have an even wider and more diverse collection of QUIC
>>> interpretations/implementations in various states of maturity and
>>> deployment. Many diverge, sometimes heavily, from the specifications
>>> especially insofar as recovery is concerned. Chrome and us (mvfst) use
>>> BBR as the default congestion controller, others use Cubic or HSTCP or
>>> who knows what else. Chrome, AFAIK has a notion of adaptive reordering
>>> similar to Linux TCP and modifications to the draft-suggested time
>>> thresholds and PTO strategy.
>>>
>>> Whether some of these changes should be codified in the QUIC
>>> specifications is a good question. My hope is that these best
>>> practices will gain deployment experience and drive consensus at the
>>> IETF in future iterations of QUIC recovery and encounter fewer
>>> roadblocks than innovations based on TCP have historically
>>> experienced. As it is now though, QUIC's charter, by design, largely
>>> limits us to the adaptation of recovery and congestion control work
>>> that has already gained consensus via other IETF RFCs. That being
>>> said, what we have in the recovery specs may not be the "state of the
>>> art" exactly, but it is still quite good and I would argue has other
>>> significant advantages over what is commonly deployed in TCP, even
>>> Linux TCP.
>>>
>>> Matt Joras
>>>
>>> On Thu, Jul 9, 2020 at 9:22 AM Jonas Reynders
>>> <jonas.reynders@student.uhasselt.be> wrote:
>>> >
>>> > I have been looking at the recovery draft 29 of QUIC and comparing it
>>> to TCP, specifically the linux implementation in kernel v5.4. I have a
>>> couple of questions about the design choices that differ from TCP in li=
nux.
>>> >
>>> > The first question is in regards to ack-based loss detection where
>>> QUIC uses both a packet-threshold and time-threshold method. Looking at=
 the
>>> linux implementation (kernel v5.4), TCP uses only a time-threshold meth=
od
>>> (RACK) as default. From my understanding both methods were used in linu=
x
>>> some time ago, around the time it was clarified to use both methods for
>>> QUIC as well. However since then TCP changed to RACK only as the defaul=
t,
>>> from what I found out it was due to tests at google detecting a 10%
>>> reduction in recovery latency (reference:
>>> https://patchwork.ozlabs.org/project/netdev/cover/20180516234017.172775=
-1-ycheng@google.com/).
>>> My question is why QUIC still recommends using both methods as default?=
 I
>>> can understand that in a datacenter context, where RTT values are reall=
y
>>> low, RACK can struggle due to timers not being fine grained.
>>> >
>>> > My second question is in regards to the time threshold
>>> calculation(6.1...2 in recovery draft). QUIC uses a constant value (9/8=
)
>>> for the time threshold, whilst in linux an adaptive threshold is used i=
n
>>> the form of a reordering window variable. In the recovery draft it is
>>> mentioned that adaptive thresholds can be used, however it=E2=80=99s no=
t mandatory.
>>> Is there a reason why QUIC doesn=E2=80=99t use the linux method for an =
adaptive
>>> threshold? The draft also mentions that reordering can be more common i=
n
>>> QUIC and that adaptive thresholds have the advantage of being more
>>> aggressive when there is no reordering. The same question for the packe=
t
>>> threshold, QUIC uses a constant threshold of 3 packets whilst in linux
>>> there is an adaptive threshold.
>>> >
>>> > My last question is that of merging the TLP and RTO into PTO. If I
>>> understand correctly, this was possible due to probe packet being
>>> ack-eliciting. And, that the time-threshold method would detect loss in=
 a
>>> similar manner to RTO, with the RTO also causing a congestion collapse =
if
>>> no acks were received for consecutive RTOs. I assume that keeping RTO w=
ould
>>> unnecessarily complicate things, is that correct?
>>>
>>>

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

<div dir=3D"ltr"><div>+1 to Jana&#39;s point about QUIC not having a TCP-st=
yle sequence number, so it&#39;s always time-based in some sense.<br></div>=
<div><br></div>There was a recent discussion of whether adaptive thresholds=
 should be recommended(<a href=3D"https://github.com/quicwg/base-drafts/iss=
ues/3571">Issue #3571</a>) which I opened after running experiments=C2=A0an=
d enabling adaptive packet thresholds by default in the Chromium implementa=
tion.=C2=A0 The current text contains the consensus decision to highlight t=
he value=C2=A0of adaptive reordering, but not make any normative statements=
.<div><br></div><div>For TLP and PTO, QUIC recovery started with both, but =
it added excess complexity without any recognizable value, so they were mer=
ged into PTO.=C2=A0 Even when both TLP and RTO existed in the recovery=C2=
=A0draft, they were subtly different from TCP&#39;s, so a new mechanism wit=
h a new name made sense.</div></div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Fri, Jul 17, 2020 at 11:15 PM Jana Iyengar=
 &lt;<a href=3D"mailto:jri.ietf@gmail.com">jri.ietf@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"lt=
r">Spencer,<div><br></div><div>It&#39;s a good=C2=A0idea, but I think it&#3=
9;s a bit early to think of a roadmap. The core protocol components necessa=
ry for QUIC are exactly the three documents we have right now, nothing more=
. Once we have more extensions, other changes in more drafts, it might make=
 sense to think of a roadmap.</div><div><br></div><div>- jana</div></div><b=
r><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, =
Jul 13, 2020 at 7:40 AM Spencer Dawkins at IETF &lt;<a href=3D"mailto:spenc=
erdawkins.ietf@gmail.com" target=3D"_blank">spencerdawkins.ietf@gmail.com</=
a>&gt; wrote:<br></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"><d=
iv dir=3D"ltr">Just to chime in here, so top-posting.=C2=A0<div><br></div><=
div>Matt is correct (that specifications !=3D implementations), but I note =
that the transport area has produced, and revised,=C2=A0<a href=3D"https://=
datatracker.ietf.org/doc/rfc7414/" target=3D"_blank">https://datatracker.ie=
tf..org/doc/rfc7414/</a>=C2=A0(A Roadmap for Transmission Control Protocol =
(TCP) Specification Documents&quot;, that go through what Matt characterize=
d as the &#39;myriad RFCs that loosely define &quot;IETF TCP&quot;&#39;</di=
v><div><br></div><div>The TCP community used Informational RFCs to document=
 what&#39;s a good idea and what&#39;s a bad idea at the per-specification =
level (&quot;really important to implement this, that is a really bad idea =
so don&#39;t implement it&quot;, because RFCs were the tools we have.=C2=A0=
</div><div><br></div><div>It might be worth thinking about the form a &quot=
;QUIC Roadmap&quot; might take, given that we now have wikis, gitbub, and o=
ther tools=C2=A0that could allow the QUIC roadmap and implementations to be=
 more aware of each other, especially if this was more granular than &quot;=
this document&quot;.=C2=A0</div><div><br></div><div>We talked about this br=
iefly at IETF 106 in TSVAREA. From the minutes at=C2=A0<a href=3D"https://d=
atatracker.ietf.org/meeting/106/materials/minutes-106-tsvarea-02" target=3D=
"_blank">https://datatracker.ietf.org/meeting/106/materials/minutes-106-tsv=
area-02</a>=C2=A0...</div><div><ul><li>Ted: Lots of creativity right now. p=
eople need to understand what they are doing *to* the protocol, not just *w=
ith* it. We should write &quot;the hitchhiker&#39;s guide to QUIC&quot;. In=
tended for all audiences.</li><li>Mirja: That&#39;s what applicability and =
mgmt docs are for.</li><li>Ted: That&#39;s not what I&#39;m looking for.</l=
i><li>Spencer: Imagine if TCP roadmap had started before there were 150 RFC=
s!<br></li></ul></div><div>Did people have thoughts about that?=C2=A0</div>=
<div>=C2=A0<br></div><div>Best,</div><div><br></div><div>Spencer</div><div>=
<br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gm=
ail_attr">On Thu, Jul 9, 2020 at 2:10 PM Matt Joras &lt;<a href=3D"mailto:m=
att..joras@gmail.com" target=3D"_blank">matt.joras@gmail.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">I won&#39;t off=
er specific answers to all your questions as Ian or Jana<br>
likely have better ones, however I&#39;d like to make a general point<br>
about this line of questioning: Linux TCP !=3D IETF TCP, or, said<br>
another way, Implementations and Specifications are not the same<br>
thing. Recall that QUIC is a series of specifications being developed<br>
by the IETF, similar to the myriad RFCs that loosely define &quot;IETF<br>
TCP&quot;. Linux&#39;s TCP stack is one such interpretation/implementation =
of<br>
TCP, and while it can inform the decisions of IETF workings, it should<br>
not be an undue determiner of the development of said specifications.<br>
Similarly we have an even wider and more diverse collection of QUIC<br>
interpretations/implementations in various states of maturity and<br>
deployment. Many diverge, sometimes heavily, from the specifications<br>
especially insofar as recovery is concerned. Chrome and us (mvfst) use<br>
BBR as the default congestion controller, others use Cubic or HSTCP or<br>
who knows what else. Chrome, AFAIK has a notion of adaptive reordering<br>
similar to Linux TCP and modifications to the draft-suggested time<br>
thresholds and PTO strategy.<br>
<br>
Whether some of these changes should be codified in the QUIC<br>
specifications is a good question. My hope is that these best<br>
practices will gain deployment experience and drive consensus at the<br>
IETF in future iterations of QUIC recovery and encounter fewer<br>
roadblocks than innovations based on TCP have historically<br>
experienced. As it is now though, QUIC&#39;s charter, by design, largely<br=
>
limits us to the adaptation of recovery and congestion control work<br>
that has already gained consensus via other IETF RFCs. That being<br>
said, what we have in the recovery specs may not be the &quot;state of the<=
br>
art&quot; exactly, but it is still quite good and I would argue has other<b=
r>
significant advantages over what is commonly deployed in TCP, even<br>
Linux TCP.<br>
<br>
Matt Joras<br>
<br>
On Thu, Jul 9, 2020 at 9:22 AM Jonas Reynders<br>
&lt;<a href=3D"mailto:jonas.reynders@student.uhasselt.be" target=3D"_blank"=
>jonas.reynders@student.uhasselt.be</a>&gt; wrote:<br>
&gt;<br>
&gt; I have been looking at the recovery draft 29 of QUIC and comparing it =
to TCP, specifically the linux implementation in kernel v5.4. I have a coup=
le of questions about the design choices that differ from TCP in linux.<br>
&gt;<br>
&gt; The first question is in regards to ack-based loss detection where QUI=
C uses both a packet-threshold and time-threshold method. Looking at the li=
nux implementation (kernel v5.4), TCP uses only a time-threshold method (RA=
CK) as default. From my understanding both methods were used in linux some =
time ago, around the time it was clarified to use both methods for QUIC as =
well. However since then TCP changed to RACK only as the default, from what=
 I found out it was due to tests at google detecting a 10% reduction in rec=
overy latency (reference: <a href=3D"https://patchwork.ozlabs.org/project/n=
etdev/cover/20180516234017.172775-1-ycheng@google.com/" rel=3D"noreferrer" =
target=3D"_blank">https://patchwork.ozlabs.org/project/netdev/cover/2018051=
6234017.172775-1-ycheng@google.com/</a>). My question is why QUIC still rec=
ommends using both methods as default? I can understand that in a datacente=
r context, where RTT values are really low, RACK can struggle due to timers=
 not being fine grained.<br>
&gt;<br>
&gt; My second question is in regards to the time threshold calculation(6.1=
...2 in recovery draft). QUIC uses a constant value (9/8) for the time thre=
shold, whilst in linux an adaptive threshold is used in the form of a reord=
ering window variable. In the recovery draft it is mentioned that adaptive =
thresholds can be used, however it=E2=80=99s not mandatory. Is there a reas=
on why QUIC doesn=E2=80=99t use the linux method for an adaptive threshold?=
 The draft also mentions that reordering can be more common in QUIC and tha=
t adaptive thresholds have the advantage of being more aggressive when ther=
e is no reordering. The same question for the packet threshold, QUIC uses a=
 constant threshold of 3 packets whilst in linux there is an adaptive thres=
hold.<br>
&gt;<br>
&gt; My last question is that of merging the TLP and RTO into PTO. If I und=
erstand correctly, this was possible due to probe packet being ack-elicitin=
g. And, that the time-threshold method would detect loss in a similar manne=
r to RTO, with the RTO also causing a congestion collapse if no acks were r=
eceived for consecutive RTOs. I assume that keeping RTO would unnecessarily=
 complicate things, is that correct?<br>
<br>
</blockquote></div>
</blockquote></div>
</blockquote></div>

--00000000000084cfaf05aae0225e--


From nobody Mon Jul 20 08:23:18 2020
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 340FD3A0C4C for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 08:23:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 K4eeVMIBu3nB for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 08:23:15 -0700 (PDT)
Received: from mail-lf1-x136.google.com (mail-lf1-x136.google.com [IPv6:2a00:1450:4864:20::136]) (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 871113A0C4A for <quic@ietf.org>; Mon, 20 Jul 2020 08:23:14 -0700 (PDT)
Received: by mail-lf1-x136.google.com with SMTP id y18so9916498lfh.11 for <quic@ietf.org>; Mon, 20 Jul 2020 08:23:14 -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=j8iFR2Bsap7/HgLv1BwRgonw2lmDKBjgCyf/Sv4Utco=; b=RrlLuBzqsVi7afUyWcWj4GivPVcOzDLDbUQBctV3lmiCD2YOdOfpS94BFuir+DuP5F 4jcuAPHUTBWDE6IsK1ZQGaI4J3z7x8wNM8wVkYRKbmXnCSai/cf4fychwcZAbo9Ds/tz EyRfZ1uhDzSj69L5ra5hk18RomJ6KBeF9+6SG4drZB3ZJ2PzcZZA2owm58nyWeDvjBYD 8AtsHyn6m1rouLy7jZH0AXkVCrQrHGOeEq1bWqJT+J1ApYE4qoBcc9LtlHot31Vz7Kyg CgnRHORtMqu343V31vCK/PfkB7YNuNtOSQid0zf41NarhU9QLOVLrW9hs9Xzoo1UUd0w VnnQ==
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=j8iFR2Bsap7/HgLv1BwRgonw2lmDKBjgCyf/Sv4Utco=; b=UJN+/kV9ze6KZ0rVOjE1wRzmE7BhTMmtT3g9dcwiCiXt/uWsnY7H9qORHulGkfs5GW 1n6jDQAMbzO8Q2mqmb6hPcLvA1OtywtrhkZgO+rv61Ga6GIUGmspBS3khi5NmelE4Gr+ NB8FTMSejYHIgtKB19bChz049qHBdUUTgzuz65iJoI7zJL6LirOutj+6dXuXNS6Z8n0d qr66UUltblSbSlGz6pVfpRDGICjx1CVdojlVnrt/kQRGagCbT07Pvw5zBxODh4Tdujrd 7xwSH3Xcyzmt1kh35Op6QdsFSAUO7CaJ3rMKYLNTAi9qCK7po61QAvRq/rBX8dLr8zRw esFQ==
X-Gm-Message-State: AOAM5332t4Uvj6Y7Qi1RmWx6IMRbYNBob0I1xcMGiPUoieghdJcyY1H/ XqwZ0IvCyrjNQ+ijvcOw/7jbHx+DDwJ9eZyo0yQ=
X-Google-Smtp-Source: ABdhPJxFMS3QzAPFL4kqyQ+Emp3xmg8Aps0usUpBVY7KXRcFuBlztOCl83GVHKkR/GlTH5uZTR3u0HbyTOBBOxL1o1M=
X-Received: by 2002:ac2:4422:: with SMTP id w2mr10999543lfl.152.1595258592581;  Mon, 20 Jul 2020 08:23:12 -0700 (PDT)
MIME-Version: 1.0
References: <CABC-CqayJAeipEhsTf4h8rkUVQvYLd=1wF4UBMkaYSNMfvgnXw@mail.gmail.com> <CADdTf+jxKyPw_zfJ6FWCz230rXqg83d7rQJhKBteBvoLCut1RQ@mail.gmail.com> <CAKKJt-dgEmOtvXR8hVT9qf+YgSe3m9LMUuE6=csU28j+j1V_ZQ@mail.gmail.com> <CACpbDce=G=ou1F5dQx3r+TbzACrJRkQkKO7OviTHvd2QxFKTyg@mail.gmail.com>
In-Reply-To: <CACpbDce=G=ou1F5dQx3r+TbzACrJRkQkKO7OviTHvd2QxFKTyg@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 20 Jul 2020 10:22:46 -0500
Message-ID: <CAKKJt-fD3UdAgi6QL2M7n28hM8vVS3hMFqNQXdKhmWMHcm9Raw@mail.gmail.com>
Subject: Re: Questions about recovery draft 29
To: Jana Iyengar <jri.ietf@gmail.com>
Cc: Matt Joras <matt.joras@gmail.com>, IETF QUIC WG <quic@ietf.org>,  Jonas Reynders <jonas.reynders@student.uhasselt.be>
Content-Type: multipart/alternative; boundary="000000000000bc5c6d05aae11538"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/9cRhMhIh0lp7LiWx-XylR1Bj3E8>
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, 20 Jul 2020 15:23:17 -0000

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

Hi, Jana,

On Fri, Jul 17, 2020 at 10:15 PM Jana Iyengar <jri.ietf@gmail.com> wrote:

> Spencer,
>
> It's a good idea, but I think it's a bit early to think of a roadmap. The
> core protocol components necessary for QUIC are exactly the three documen=
ts
> we have right now, nothing more. Once we have more extensions, other
> changes in more drafts, it might make sense to think of a roadmap.
>

I think we're talking about a race condition between whether we know enough
about QUIC to start a roadmap now that would be useful when the tsunami of
extension proposals arrives (as envisioned in discussions about the NEXT
recharter), or whether that's still mysterious enough that we have no
choice except to wait for extensions (and other draft changes), before we
can produce something useful.

You may very well be right, that we don't have much to say yet, so waiting
is best.

But let's remember that we had this conversation in another year to 18
months, OK? :-)

Best,

Spencer


>
> - jana
>
> On Mon, Jul 13, 2020 at 7:40 AM Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
>
>> Just to chime in here, so top-posting.
>>
>> Matt is correct (that specifications !=3D implementations), but I note t=
hat
>> the transport area has produced, and revised,
>> https://datatracker.ietf.org/doc/rfc7414/ (A Roadmap for Transmission
>> Control Protocol (TCP) Specification Documents", that go through what Ma=
tt
>> characterized as the 'myriad RFCs that loosely define "IETF TCP"'
>>
>> The TCP community used Informational RFCs to document what's a good idea
>> and what's a bad idea at the per-specification level ("really important =
to
>> implement this, that is a really bad idea so don't implement it", becaus=
e
>> RFCs were the tools we have.
>>
>> It might be worth thinking about the form a "QUIC Roadmap" might take,
>> given that we now have wikis, gitbub, and other tools that could allow t=
he
>> QUIC roadmap and implementations to be more aware of each other, especia=
lly
>> if this was more granular than "this document".
>>
>> We talked about this briefly at IETF 106 in TSVAREA. From the minutes at
>> https://datatracker.ietf.org/meeting/106/materials/minutes-106-tsvarea-0=
2
>>  ...
>>
>>    - Ted: Lots of creativity right now. people need to understand what
>>    they are doing *to* the protocol, not just *with* it. We should write=
 "the
>>    hitchhiker's guide to QUIC". Intended for all audiences.
>>    - Mirja: That's what applicability and mgmt docs are for.
>>    - Ted: That's not what I'm looking for.
>>    - Spencer: Imagine if TCP roadmap had started before there were 150
>>    RFCs!
>>
>> Did people have thoughts about that?
>>
>> Best,
>>
>> Spencer
>>
>>
>> On Thu, Jul 9, 2020 at 2:10 PM Matt Joras <matt.joras@gmail.com> wrote:
>>
>>> I won't offer specific answers to all your questions as Ian or Jana
>>> likely have better ones, however I'd like to make a general point
>>> about this line of questioning: Linux TCP !=3D IETF TCP, or, said
>>> another way, Implementations and Specifications are not the same
>>> thing. Recall that QUIC is a series of specifications being developed
>>> by the IETF, similar to the myriad RFCs that loosely define "IETF
>>> TCP". Linux's TCP stack is one such interpretation/implementation of
>>> TCP, and while it can inform the decisions of IETF workings, it should
>>> not be an undue determiner of the development of said specifications.
>>> Similarly we have an even wider and more diverse collection of QUIC
>>> interpretations/implementations in various states of maturity and
>>> deployment. Many diverge, sometimes heavily, from the specifications
>>> especially insofar as recovery is concerned. Chrome and us (mvfst) use
>>> BBR as the default congestion controller, others use Cubic or HSTCP or
>>> who knows what else. Chrome, AFAIK has a notion of adaptive reordering
>>> similar to Linux TCP and modifications to the draft-suggested time
>>> thresholds and PTO strategy.
>>>
>>> Whether some of these changes should be codified in the QUIC
>>> specifications is a good question. My hope is that these best
>>> practices will gain deployment experience and drive consensus at the
>>> IETF in future iterations of QUIC recovery and encounter fewer
>>> roadblocks than innovations based on TCP have historically
>>> experienced. As it is now though, QUIC's charter, by design, largely
>>> limits us to the adaptation of recovery and congestion control work
>>> that has already gained consensus via other IETF RFCs. That being
>>> said, what we have in the recovery specs may not be the "state of the
>>> art" exactly, but it is still quite good and I would argue has other
>>> significant advantages over what is commonly deployed in TCP, even
>>> Linux TCP.
>>>
>>> Matt Joras
>>>
>>> On Thu, Jul 9, 2020 at 9:22 AM Jonas Reynders
>>> <jonas.reynders@student.uhasselt.be> wrote:
>>> >
>>> > I have been looking at the recovery draft 29 of QUIC and comparing it
>>> to TCP, specifically the linux implementation in kernel v5.4. I have a
>>> couple of questions about the design choices that differ from TCP in li=
nux.
>>> >
>>> > The first question is in regards to ack-based loss detection where
>>> QUIC uses both a packet-threshold and time-threshold method. Looking at=
 the
>>> linux implementation (kernel v5.4), TCP uses only a time-threshold meth=
od
>>> (RACK) as default. From my understanding both methods were used in linu=
x
>>> some time ago, around the time it was clarified to use both methods for
>>> QUIC as well. However since then TCP changed to RACK only as the defaul=
t,
>>> from what I found out it was due to tests at google detecting a 10%
>>> reduction in recovery latency (reference:
>>> https://patchwork.ozlabs.org/project/netdev/cover/20180516234017.172775=
-1-ycheng@google.com/).
>>> My question is why QUIC still recommends using both methods as default?=
 I
>>> can understand that in a datacenter context, where RTT values are reall=
y
>>> low, RACK can struggle due to timers not being fine grained.
>>> >
>>> > My second question is in regards to the time threshold
>>> calculation(6.1..2 in recovery draft). QUIC uses a constant value (9/8)=
 for
>>> the time threshold, whilst in linux an adaptive threshold is used in th=
e
>>> form of a reordering window variable. In the recovery draft it is menti=
oned
>>> that adaptive thresholds can be used, however it=E2=80=99s not mandator=
y. Is there
>>> a reason why QUIC doesn=E2=80=99t use the linux method for an adaptive =
threshold?
>>> The draft also mentions that reordering can be more common in QUIC and =
that
>>> adaptive thresholds have the advantage of being more aggressive when th=
ere
>>> is no reordering. The same question for the packet threshold, QUIC uses=
 a
>>> constant threshold of 3 packets whilst in linux there is an adaptive
>>> threshold.
>>> >
>>> > My last question is that of merging the TLP and RTO into PTO. If I
>>> understand correctly, this was possible due to probe packet being
>>> ack-eliciting. And, that the time-threshold method would detect loss in=
 a
>>> similar manner to RTO, with the RTO also causing a congestion collapse =
if
>>> no acks were received for consecutive RTOs. I assume that keeping RTO w=
ould
>>> unnecessarily complicate things, is that correct?
>>>
>>>

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

<div dir=3D"ltr"><div dir=3D"ltr">Hi, Jana,</div><br><div class=3D"gmail_qu=
ote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jul 17, 2020 at 10:15 PM=
 Jana Iyengar &lt;<a href=3D"mailto:jri.ietf@gmail.com">jri.ietf@gmail.com<=
/a>&gt; wrote:<br></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 dir=3D"ltr">Spencer,<div><br></div><div>It&#39;s a good=C2=A0idea, but =
I think it&#39;s a bit early to think of a roadmap. The core protocol compo=
nents necessary for QUIC are exactly the three documents we have right now,=
 nothing more. Once we have more extensions, other changes in more drafts, =
it might make sense to think of a roadmap.</div></div></blockquote><div><br=
></div><div>I think we&#39;re talking about a race condition between whethe=
r we know enough about QUIC to start a roadmap now that would be useful whe=
n the tsunami of extension proposals arrives (as envisioned in discussions =
about the NEXT recharter), or whether that&#39;s still mysterious enough th=
at we have no choice except to wait for extensions (and other draft changes=
), before we can produce something useful.=C2=A0</div><div><br></div><div>Y=
ou may very well be right, that we don&#39;t have much to say yet, so waiti=
ng is best.</div><div><br></div><div>But let&#39;s remember that we had thi=
s conversation in another year to 18 months, OK? :-)</div><div><br></div><d=
iv>Best,</div><div><br></div><div>Spencer</div><div>=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"><div dir=3D"ltr"><div><br></div><div=
>- jana</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D=
"gmail_attr">On Mon, Jul 13, 2020 at 7:40 AM Spencer Dawkins at IETF &lt;<a=
 href=3D"mailto:spencerdawkins.ietf@gmail.com" target=3D"_blank">spencerdaw=
kins.ietf@gmail.com</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quot=
e" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204)=
;padding-left:1ex"><div dir=3D"ltr">Just to chime in here, so top-posting.=
=C2=A0<div><br></div><div>Matt is correct (that specifications !=3D impleme=
ntations), but I note that the transport area has produced, and revised,=C2=
=A0<a href=3D"https://datatracker.ietf.org/doc/rfc7414/" target=3D"_blank">=
https://datatracker.ietf.org/doc/rfc7414/</a>=C2=A0(A Roadmap for Transmiss=
ion Control Protocol (TCP) Specification Documents&quot;, that go through w=
hat Matt characterized as the &#39;myriad RFCs that loosely define &quot;IE=
TF TCP&quot;&#39;</div><div><br></div><div>The TCP community used Informati=
onal RFCs to document what&#39;s a good idea and what&#39;s a bad idea at t=
he per-specification level (&quot;really important to implement this, that =
is a really bad idea so don&#39;t implement it&quot;, because RFCs were the=
 tools we have.=C2=A0</div><div><br></div><div>It might be worth thinking a=
bout the form a &quot;QUIC Roadmap&quot; might take, given that we now have=
 wikis, gitbub, and other tools=C2=A0that could allow the QUIC roadmap and =
implementations to be more aware of each other, especially if this was more=
 granular than &quot;this document&quot;.=C2=A0</div><div><br></div><div>We=
 talked about this briefly at IETF 106 in TSVAREA. From the minutes at=C2=
=A0<a href=3D"https://datatracker.ietf.org/meeting/106/materials/minutes-10=
6-tsvarea-02" target=3D"_blank">https://datatracker.ietf.org/meeting/106/ma=
terials/minutes-106-tsvarea-02</a>=C2=A0...</div><div><ul><li>Ted: Lots of =
creativity right now. people need to understand what they are doing *to* th=
e protocol, not just *with* it. We should write &quot;the hitchhiker&#39;s =
guide to QUIC&quot;. Intended for all audiences.</li><li>Mirja: That&#39;s =
what applicability and mgmt docs are for.</li><li>Ted: That&#39;s not what =
I&#39;m looking for.</li><li>Spencer: Imagine if TCP roadmap had started be=
fore there were 150 RFCs!<br></li></ul></div><div>Did people have thoughts =
about that?=C2=A0</div><div>=C2=A0<br></div><div>Best,</div><div><br></div>=
<div>Spencer</div><div><br></div></div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D"gmail_attr">On Thu, Jul 9, 2020 at 2:10 PM Matt Joras =
&lt;<a href=3D"mailto:matt.joras@gmail.com" target=3D"_blank">matt.joras@gm=
ail.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-lef=
t:1ex">I won&#39;t offer specific answers to all your questions as Ian or J=
ana<br>
likely have better ones, however I&#39;d like to make a general point<br>
about this line of questioning: Linux TCP !=3D IETF TCP, or, said<br>
another way, Implementations and Specifications are not the same<br>
thing. Recall that QUIC is a series of specifications being developed<br>
by the IETF, similar to the myriad RFCs that loosely define &quot;IETF<br>
TCP&quot;. Linux&#39;s TCP stack is one such interpretation/implementation =
of<br>
TCP, and while it can inform the decisions of IETF workings, it should<br>
not be an undue determiner of the development of said specifications.<br>
Similarly we have an even wider and more diverse collection of QUIC<br>
interpretations/implementations in various states of maturity and<br>
deployment. Many diverge, sometimes heavily, from the specifications<br>
especially insofar as recovery is concerned. Chrome and us (mvfst) use<br>
BBR as the default congestion controller, others use Cubic or HSTCP or<br>
who knows what else. Chrome, AFAIK has a notion of adaptive reordering<br>
similar to Linux TCP and modifications to the draft-suggested time<br>
thresholds and PTO strategy.<br>
<br>
Whether some of these changes should be codified in the QUIC<br>
specifications is a good question. My hope is that these best<br>
practices will gain deployment experience and drive consensus at the<br>
IETF in future iterations of QUIC recovery and encounter fewer<br>
roadblocks than innovations based on TCP have historically<br>
experienced. As it is now though, QUIC&#39;s charter, by design, largely<br=
>
limits us to the adaptation of recovery and congestion control work<br>
that has already gained consensus via other IETF RFCs. That being<br>
said, what we have in the recovery specs may not be the &quot;state of the<=
br>
art&quot; exactly, but it is still quite good and I would argue has other<b=
r>
significant advantages over what is commonly deployed in TCP, even<br>
Linux TCP.<br>
<br>
Matt Joras<br>
<br>
On Thu, Jul 9, 2020 at 9:22 AM Jonas Reynders<br>
&lt;<a href=3D"mailto:jonas.reynders@student.uhasselt.be" target=3D"_blank"=
>jonas.reynders@student.uhasselt.be</a>&gt; wrote:<br>
&gt;<br>
&gt; I have been looking at the recovery draft 29 of QUIC and comparing it =
to TCP, specifically the linux implementation in kernel v5.4. I have a coup=
le of questions about the design choices that differ from TCP in linux.<br>
&gt;<br>
&gt; The first question is in regards to ack-based loss detection where QUI=
C uses both a packet-threshold and time-threshold method. Looking at the li=
nux implementation (kernel v5.4), TCP uses only a time-threshold method (RA=
CK) as default. From my understanding both methods were used in linux some =
time ago, around the time it was clarified to use both methods for QUIC as =
well. However since then TCP changed to RACK only as the default, from what=
 I found out it was due to tests at google detecting a 10% reduction in rec=
overy latency (reference: <a href=3D"https://patchwork.ozlabs.org/project/n=
etdev/cover/20180516234017.172775-1-ycheng@google.com/" rel=3D"noreferrer" =
target=3D"_blank">https://patchwork.ozlabs.org/project/netdev/cover/2018051=
6234017.172775-1-ycheng@google.com/</a>). My question is why QUIC still rec=
ommends using both methods as default? I can understand that in a datacente=
r context, where RTT values are really low, RACK can struggle due to timers=
 not being fine grained.<br>
&gt;<br>
&gt; My second question is in regards to the time threshold calculation(6.1=
..2 in recovery draft). QUIC uses a constant value (9/8) for the time thres=
hold, whilst in linux an adaptive threshold is used in the form of a reorde=
ring window variable. In the recovery draft it is mentioned that adaptive t=
hresholds can be used, however it=E2=80=99s not mandatory. Is there a reaso=
n why QUIC doesn=E2=80=99t use the linux method for an adaptive threshold? =
The draft also mentions that reordering can be more common in QUIC and that=
 adaptive thresholds have the advantage of being more aggressive when there=
 is no reordering. The same question for the packet threshold, QUIC uses a =
constant threshold of 3 packets whilst in linux there is an adaptive thresh=
old.<br>
&gt;<br>
&gt; My last question is that of merging the TLP and RTO into PTO. If I und=
erstand correctly, this was possible due to probe packet being ack-elicitin=
g. And, that the time-threshold method would detect loss in a similar manne=
r to RTO, with the RTO also causing a congestion collapse if no acks were r=
eceived for consecutive RTOs. I assume that keeping RTO would unnecessarily=
 complicate things, is that correct?<br>
<br>
</blockquote></div>
</blockquote></div>
</blockquote></div></div>

--000000000000bc5c6d05aae11538--


From nobody Mon Jul 20 09:48:54 2020
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 5CBCD3A0D2B for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 09:48:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level: 
X-Spam-Status: No, score=-17.599 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, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, 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 W777DWnYwVeI for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 09:48:50 -0700 (PDT)
Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) (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 8B5E33A0D29 for <quic@ietf.org>; Mon, 20 Jul 2020 09:48:50 -0700 (PDT)
Received: by mail-yb1-xb2d.google.com with SMTP id v9so8613808ybe.3 for <quic@ietf.org>; Mon, 20 Jul 2020 09:48:50 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=oa2lcPQgB0VT0mdwAhEC51ZTuRUqd2ZnlO1EsPo2Plg=; b=DZaocirvouGvM/jdz13YvGp5aQ6Hw1w8MBKS4HjSK6ud3Qsj9rwj5kxcAhprb1JU5d DPOOPcFMMsPVkHxMIswhM0TlXLX8FJhPlFrupIhlpoWHZiFGOfBByXCMoLeryXmEgysI mR6uGhBO52ZgwxM7GLambHNCsg4dR6chIH3NLi9liCY32booZndFv9M5/S9VQ9nbhq6g eMQ7jraAcqE9fzAsaKiL81Z7ldG2q4V6ZUD5/Vsjurj3cyRoVShXOItE2vMC/s7zhDtf IeaFiyZ2vEtCYVqbRo4jKb5RrMxSKQsFI6comSLzSxE/swBaIZKj0nnTNizvz8Tnexlt vy3A==
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=oa2lcPQgB0VT0mdwAhEC51ZTuRUqd2ZnlO1EsPo2Plg=; b=PZDvDt3o9/iuL+Whps4u2zhP7taf5wIZDTm73X9F+z1EyXANec1v4BSzcGHOE/VbZS sve5dH5EK/worqXy0EHt1NlkHli7y7THB7VRIcrgr+UI+DmEfEfpw9YW+L/F/L+FATmW aUycjJNRrwAGIU86CPIuLXFzHgpFvgR4ij5S39z3dDjkGLO4dv/Q4glGwKeHXm6yqF5c OIEFbBOQxuh9ribTmbr+LoYkpzR2yPTWW6TVTB/ut0/DSQUVtP9HDnUiB8VQWVmzp8Tv mC9Mq0fPyV33V2i5XZ8Kljd8oRFS26eQleAdpZIuF8pdgWojNj/rUwk+OaeyVpzOtvnv GIzg==
X-Gm-Message-State: AOAM532x+8nYAtYZ05ZzmOqKxTsodwhBpGOfVCIefb5Y7u3l01VIZQKt 7MOBdP9vKUohP//82Xu13Wgm5FS+pM6sAHE6yQFSNA==
X-Google-Smtp-Source: ABdhPJwj1uHY2GSjaR86JG8pUsaeHgcvmPqCIFsodb3pj1VYb/TpxkT5V71w+xoIo2UVRyG3KIouelaHrdO4l6b0PDY=
X-Received: by 2002:a25:ba8c:: with SMTP id s12mr33887589ybg.278.1595263729377;  Mon, 20 Jul 2020 09:48:49 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <9f57b20d-2eba-b2b9-d8c8-48e019c8952a@wizmail.org> <CACpbDccrpHeP5PYGCZky+AN2gC9YSs5gbAzYr4Yrw1LpvHZNiA@mail.gmail.com> <CH2PR00MB07269A73542DBC8E51E95519B67A0@CH2PR00MB0726.namprd00.prod.outlook.com>
In-Reply-To: <CH2PR00MB07269A73542DBC8E51E95519B67A0@CH2PR00MB0726.namprd00.prod.outlook.com>
From: Ian Swett <ianswett@google.com>
Date: Mon, 20 Jul 2020 12:48:37 -0400
Message-ID: <CAKcm_gMhRX3NxiW6Primy+UrY44ZahaSO+9kF5CeeN4=XqL2JQ@mail.gmail.com>
Subject: Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
To: Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>
Cc: Jana Iyengar <jri.ietf@gmail.com>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ea1d2e05aae2477d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/6RHGGjQjOQqchYWFr4bwZQCFnRE>
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, 20 Jul 2020 16:48:53 -0000

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

I think it's ok to include burst limits in the set of things we expect may
be different in DCs, but if we do that, I'd prefer to use the RECOMMENDED
rather than SHOULD, since there are a number of SHOULDs which I
believe apply both to the public internet and to DCs.  Then we could add a
note at the top about how there are some values which are RECOMMENDED,
including X, Y and Z, and those recommendations are expected to be good
choices for most, but not all environments.

In terms of text, I'd suggest taking Neal's suggestion and dropping an
explicit mention of the public internet:

Implementations MUST either use pacing or another method to limit such burs=
ts.

It is RECOMMENDED that implementations limit bursts to the initial
congestion window; see Section 7.2
<https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Ftools.=
ietf.org%2Fhtml%2Fdraft-ietf-quic-recovery-29%23section-7.2&data=3D02%7C01%=
7Cpravb%40microsoft.com%7C9df3e5f4f0ca4e586f0908d824e0a3ad%7C72f988bf86f141=
af91ab2d7cd011db47%7C1%7C0%7C637299894526657906&sdata=3Dze%2F7SpKUbrdgwI6m%=
2BS6uEGSBgc2NapVtPn9vkOYFjVs%3D&reserved=3D0>.


On Sun, Jul 19, 2020 at 4:08 PM Praveen Balasubramanian <pravb=3D
40microsoft.com@dmarc.ietf.org> wrote:

> >> There's a way of satisfying both desires: have the NIC handle the
> pacing.
>
> Yes letting the NIC handle pacing will make improve CPU efficiency and
> improve accuracy due to fine grained hardware timers. But that=E2=80=99s =
in the
> future. Today=E2=80=99s NICs don=E2=80=99t pace large send offloads for T=
CP or UDP.
>
>
>
> >> Perhaps we can have a principle here: recommendations that are specifi=
c
> for Internet use are just that, and we use SHOULDs for those. IW10 makes
> sense based on this, and I would then also be fine with changing the MUST
> to a SHOULD. Perhaps we can state this principle upfront.
>
> I like the idea of stating that principle up front. SHOULD would be
> sufficient resolution for the burst size issue.
>
>
>
> *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of * Jana Iyengar
> *Sent:* Friday, July 17, 2020 7:18 PM
> *To:* QUIC WG <quic@ietf.org>
> *Subject:* [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
>
>
>
> There's a protocol question and there's a question of endpoint behavior.
> In terms of the protocol itself, yes, there's no real need to distinguish
> between Internet and DC environments; we've tried to ensure that the
> protocol can be used broadly. My point was that the constants in the spec
> were based on what we believe to be true for the public Internet, and not
> for DC environments.
>
>
>
> That said, perhaps I was a bit too hasty. IW10 and InitialRTT values are
> the others I was thinking about, but those are recommendations in the spe=
c,
> not requirements. And as Ian notes, there's no minimum timeout anymore.
>
>
>
> Perhaps we can have a principle here: recommendations that are specific
> for Internet use are just that, and we use SHOULDs for those. IW10 makes
> sense based on this, and I would then also be fine with changing the MUST
> to a SHOULD. Perhaps we can state this principle upfront.
>
>
>
> Ian, I share your hesitation that we don't want to make a distinction
> between private and public networks, but we already allow for
> implementations to do that with a different IW and Initial RTT. Is it
> different when talking about burst limits?
>
>
>
>
>
> On Fri, Jul 17, 2020 at 3:07 PM Jeremy Harris <jgh@wizmail.org> wrote:
>
> On 08/07/2020 22:29, Praveen Balasubramanian wrote:
> > Section 7.9
> > "Implementations MUST either use pacing or another method to limit such
> bursts to the initial congestion window; see Section 7.2."
> > This seems to preclude use of segmentation offload of sizes greater tha=
n
> IW.. In datacenters we routinely send bursts that are higher without
> causing loss. The MUST here seems unnecessary. It also conflicts with the
> RECOMMENDED in an earlier sentence.
>
> There's a way of satisfying both desires: have the NIC handle the
> pacing.
> --
> Cheers,
>   Jeremy
>
>

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

<div dir=3D"ltr">I think it&#39;s ok to include burst limits in the set of =
things we expect may be different in DCs, but if we do that, I&#39;d prefer=
 to use the RECOMMENDED rather than SHOULD, since there are a number of SHO=
ULDs which I believe=C2=A0apply both to the public internet and to DCs.=C2=
=A0 Then we could add a note at the top about how there are some values whi=
ch are RECOMMENDED, including X, Y and Z, and those recommendations are exp=
ected to be good choices for most, but not all environments.<div><br></div>=
<div>In terms of text, I&#39;d suggest taking Neal&#39;s suggestion and dro=
pping an explicit mention of the public internet:</div><div><br></div><div>=
<pre style=3D"white-space:pre-wrap;margin:0in;font-size:10pt;font-family:&q=
uot;Courier New&quot;;break-before:page"><span style=3D"color:black">Implem=
entations MUST either use pacing or another method to limit such bursts.<u>=
</u><u></u></span></pre><pre style=3D"white-space:pre-wrap;margin:0in;font-=
size:10pt;font-family:&quot;Courier New&quot;;break-before:page"><span styl=
e=3D"color:black">It is RECOMMENDED that implementations limit bursts to th=
e initial </span>congestion window; see <a href=3D"https://nam06.safelinks.=
protection.outlook.com/?url=3Dhttps%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-i=
etf-quic-recovery-29%23section-7.2&amp;data=3D02%7C01%7Cpravb%40microsoft.c=
om%7C9df3e5f4f0ca4e586f0908d824e0a3ad%7C72f988bf86f141af91ab2d7cd011db47%7C=
1%7C0%7C637299894526657906&amp;sdata=3Dze%2F7SpKUbrdgwI6m%2BS6uEGSBgc2NapVt=
Pn9vkOYFjVs%3D&amp;reserved=3D0" target=3D"_blank" style=3D"font-size:10pt"=
>Section 7.2</a><span style=3D"font-size:10pt;color:black">.</span></pre></=
div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_at=
tr">On Sun, Jul 19, 2020 at 4:08 PM Praveen Balasubramanian &lt;pravb=3D<a =
href=3D"mailto:40microsoft.com@dmarc.ietf.org">40microsoft.com@dmarc.ietf.o=
rg</a>&gt; wrote:<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=
">





<div lang=3D"EN-US">
<div class=3D"gmail-m_8197904849400175487WordSection1">
<p class=3D"MsoNormal">&gt;&gt; There&#39;s a way of satisfying both desire=
s: have the NIC handle the pacing.<u></u><u></u></p>
<p class=3D"MsoNormal">Yes letting the NIC handle pacing will make improve =
CPU efficiency and improve accuracy due to fine grained hardware timers. Bu=
t that=E2=80=99s in the future. Today=E2=80=99s NICs don=E2=80=99t pace lar=
ge send offloads for TCP or UDP.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">&gt;&gt; Perhaps we can have a principle here: recom=
mendations that are specific for Internet use are just that, and we use SHO=
ULDs for those. IW10 makes sense based on this, and I would then also be fi=
ne with changing the MUST to a SHOULD. Perhaps
 we can state this principle upfront.<u></u><u></u></p>
<p class=3D"MsoNormal">I like the idea of stating that principle up front. =
SHOULD would be sufficient resolution for the burst size issue.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<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>
Jana Iyengar<br>
<b>Sent:</b> Friday, July 17, 2020 7:18 PM<br>
<b>To:</b> QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">q=
uic@ietf.org</a>&gt;<br>
<b>Subject:</b> [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29<u=
></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">There&#39;s a protocol question and there&#39;s a qu=
estion of endpoint behavior. In terms of the protocol itself, yes, there&#3=
9;s no real need to distinguish between Internet and DC environments; we&#3=
9;ve tried to ensure that the protocol can be used
 broadly. My point was that the constants=C2=A0in the spec were based on wh=
at we believe to be true for the public Internet, and not for DC environmen=
ts.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">That said, perhaps I was a bit too hasty. IW10 and I=
nitialRTT values are the others I was thinking about, but those are=C2=A0re=
commendations in the spec, not requirements. And as Ian notes, there&#39;s =
no minimum timeout anymore.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Perhaps we can have a principle here: recommendation=
s that are specific for Internet use are just that, and we use SHOULDs for =
those. IW10 makes sense based on this, and I would then also be fine with c=
hanging the MUST to a SHOULD. Perhaps
 we can state this principle upfront.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Ian, I share your hesitation that we don&#39;t want =
to make a distinction between private and public networks,=C2=A0but we alre=
ady allow for implementations to do that with a different=C2=A0IW and Initi=
al RTT. Is it different when talking about burst
 limits?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Fri, Jul 17, 2020 at 3:07 PM Jeremy Harris &lt;<a=
 href=3D"mailto:jgh@wizmail.org" target=3D"_blank">jgh@wizmail.org</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">
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt">On 08/07/2020 22:29, Pr=
aveen Balasubramanian wrote:<br>
&gt; Section 7.9<br>
&gt; &quot;Implementations MUST either use pacing or another method to limi=
t such bursts to the initial congestion window; see Section 7.2.&quot;<br>
&gt; This seems to preclude use of segmentation offload of sizes greater th=
an IW.. In datacenters we routinely send bursts that are higher without cau=
sing loss. The MUST here seems unnecessary. It also conflicts with the RECO=
MMENDED in an earlier sentence.<br>
<br>
There&#39;s a way of satisfying both desires: have the NIC handle the<br>
pacing.<br>
-- <br>
Cheers,<br>
=C2=A0 Jeremy<u></u><u></u></p>
</blockquote>
</div>
</div>
</div>

</blockquote></div>

--000000000000ea1d2e05aae2477d--


From nobody Mon Jul 20 14:30:43 2020
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B51A63A0FA5 for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 14:30:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 RPMtVazpCwYe for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 14:30:38 -0700 (PDT)
Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 676AE3A0EA9 for <quic@ietf.org>; Mon, 20 Jul 2020 14:30:38 -0700 (PDT)
Received: by mail-lj1-x22e.google.com with SMTP id e8so21852699ljb.0 for <quic@ietf.org>; Mon, 20 Jul 2020 14:30:38 -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=uPX6RtEuVVaBYggZygCd6Ahi1rJXU7DMb/0y0IDDfME=; b=CJ64r7VJoTNegeJEHGAvHa87kLN9PIdxcYDfO3lrJm5JBeze7CXhN65Ozqjy5tFsl8 8JCkNH93moi4DTVetl7akDSoGuhErWgwDhrr2da4o/qSghWROlXtcqxD2v8G0SnsEWFq cigSxdzRsJ6luVZo4Donwp1E1xtg1OfdQlSG9rxEj4qGAe/vLb55zNCoJUZBne1uPhtH cPOTWU1+Tj4IqXHrjvJCAI6UR92FZu3EiL3oemCsVDH08qiLPsi/YEmMlZnCpicdMCZa Q3zZOIhRHBf2/tTsj7lJaaqUMIpSrzL/z/6b0gu0vbQkzp4Zx7STIv/K9bfjfbfh7Y7g ntzA==
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=uPX6RtEuVVaBYggZygCd6Ahi1rJXU7DMb/0y0IDDfME=; b=rtdPJU2fYg1rdU4oewkP2axd8nQ5iN2g1hWgVfOQztBXiBiC061Id2GQi93Fr3yo0V RNcBD1vmTX88po8/+ZCWq2yyEf61wNRZZEDyPUrlDDdOdwwGxXAwRrsXWAdwgWkHxgki /ago5PcGWQh7mhyAm314mYwvWykc1D1nUuiYfjMs01zlcZ6/TSjb0KSL1FZA4FF61697 Z+Uk7y5o/sN9KruJgYpuBUVmi7a71sFB0CzgPNcUoWy1bJKHbv67251WMzFJwwtxo5p4 jmaYM0w/vliy4Zszlidn/H3qJywAG8EPizFKQzSGd5aqpUrHuolvvfiqMom1GOSNzB14 2dkg==
X-Gm-Message-State: AOAM532WMi61iShsUbBv9+f/8eoM5uES49/ruYcoOl+7wj7Zg/qley/K THW5bZlD6mA1kE1CwPaE84L1SzAiord1cBlGWzo=
X-Google-Smtp-Source: ABdhPJx8rEHl5nsBuLpTgbiKcG/ddI8qUbRJwktnsUJOVdjpsGyFFRTJ8JlwLESgeBOw+q7P/d3Fjca8X2JJkYs18QM=
X-Received: by 2002:a2e:81d7:: with SMTP id s23mr10828109ljg.398.1595280636374;  Mon, 20 Jul 2020 14:30:36 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <9f57b20d-2eba-b2b9-d8c8-48e019c8952a@wizmail.org> <CACpbDccrpHeP5PYGCZky+AN2gC9YSs5gbAzYr4Yrw1LpvHZNiA@mail.gmail.com> <CH2PR00MB07269A73542DBC8E51E95519B67A0@CH2PR00MB0726.namprd00.prod.outlook.com> <CAKcm_gMhRX3NxiW6Primy+UrY44ZahaSO+9kF5CeeN4=XqL2JQ@mail.gmail.com>
In-Reply-To: <CAKcm_gMhRX3NxiW6Primy+UrY44ZahaSO+9kF5CeeN4=XqL2JQ@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 20 Jul 2020 16:30:10 -0500
Message-ID: <CAKKJt-fY92k5ym767GofK+DOMQs=x6dpkwkKOA1cpkUf8Xs+3A@mail.gmail.com>
Subject: Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>
Cc: Praveen Balasubramanian <pravb=40microsoft.com@dmarc.ietf.org>, Jana Iyengar <jri.ietf@gmail.com>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a5f1cf05aae6372a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/dEEaX3B4eYBCzkgBnv2Hcuv6Yg4>
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, 20 Jul 2020 21:30:41 -0000

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

Hi, Ian,

On Mon, Jul 20, 2020 at 11:49 AM Ian Swett <ianswett=3D
40google.com@dmarc.ietf.org> wrote:

> I think it's ok to include burst limits in the set of things we expect ma=
y
> be different in DCs, but if we do that, I'd prefer to use the RECOMMENDED
> rather than SHOULD,
>

Aren't RECOMMENDED and SHOULD equivalent in
https://tools.ietf.org/html/rfc2119?

Or am I misunderstanding your point?

3 <https://tools.ietf.org/html/rfc2119#section-3>. SHOULD   This word,
or the adjective "RECOMMENDED", mean that there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.


Best,

Spencer

since there are a number of SHOULDs which I believe apply both to the
> public internet and to DCs.  Then we could add a note at the top about ho=
w
> there are some values which are RECOMMENDED, including X, Y and Z, and
> those recommendations are expected to be good choices for most, but not a=
ll
> environments.
>
> In terms of text, I'd suggest taking Neal's suggestion and dropping an
> explicit mention of the public internet:
>
> Implementations MUST either use pacing or another method to limit such bu=
rsts.
>
> It is RECOMMENDED that implementations limit bursts to the initial conges=
tion window; see Section 7.2 <https://nam06.safelinks.protection.outlook.co=
m/?url=3Dhttps%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-quic-recovery-29%=
23section-7.2&data=3D02%7C01%7Cpravb%40microsoft.com%7C9df3e5f4f0ca4e586f09=
08d824e0a3ad%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C63729989452665790=
6&sdata=3Dze%2F7SpKUbrdgwI6m%2BS6uEGSBgc2NapVtPn9vkOYFjVs%3D&reserved=3D0>.
>
>
> On Sun, Jul 19, 2020 at 4:08 PM Praveen Balasubramanian <pravb=3D
> 40microsoft.com@dmarc.ietf.org> wrote:
>
>> >> There's a way of satisfying both desires: have the NIC handle the
>> pacing.
>>
>> Yes letting the NIC handle pacing will make improve CPU efficiency and
>> improve accuracy due to fine grained hardware timers. But that=E2=80=99s=
 in the
>> future. Today=E2=80=99s NICs don=E2=80=99t pace large send offloads for =
TCP or UDP.
>>
>>
>>
>> >> Perhaps we can have a principle here: recommendations that are
>> specific for Internet use are just that, and we use SHOULDs for those. I=
W10
>> makes sense based on this, and I would then also be fine with changing t=
he
>> MUST to a SHOULD. Perhaps we can state this principle upfront.
>>
>> I like the idea of stating that principle up front. SHOULD would be
>> sufficient resolution for the burst size issue.
>>
>>
>>
>> *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of * Jana Iyengar
>> *Sent:* Friday, July 17, 2020 7:18 PM
>> *To:* QUIC WG <quic@ietf.org>
>> *Subject:* [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
>>
>>
>>
>> There's a protocol question and there's a question of endpoint behavior.
>> In terms of the protocol itself, yes, there's no real need to distinguis=
h
>> between Internet and DC environments; we've tried to ensure that the
>> protocol can be used broadly. My point was that the constants in the spe=
c
>> were based on what we believe to be true for the public Internet, and no=
t
>> for DC environments.
>>
>>
>>
>> That said, perhaps I was a bit too hasty. IW10 and InitialRTT values are
>> the others I was thinking about, but those are recommendations in the sp=
ec,
>> not requirements. And as Ian notes, there's no minimum timeout anymore.
>>
>>
>>
>> Perhaps we can have a principle here: recommendations that are specific
>> for Internet use are just that, and we use SHOULDs for those. IW10 makes
>> sense based on this, and I would then also be fine with changing the MUS=
T
>> to a SHOULD. Perhaps we can state this principle upfront.
>>
>>
>>
>> Ian, I share your hesitation that we don't want to make a distinction
>> between private and public networks, but we already allow for
>> implementations to do that with a different IW and Initial RTT. Is it
>> different when talking about burst limits?
>>
>>
>>
>>
>>
>> On Fri, Jul 17, 2020 at 3:07 PM Jeremy Harris <jgh@wizmail.org> wrote:
>>
>> On 08/07/2020 22:29, Praveen Balasubramanian wrote:
>> > Section 7.9
>> > "Implementations MUST either use pacing or another method to limit suc=
h
>> bursts to the initial congestion window; see Section 7.2."
>> > This seems to preclude use of segmentation offload of sizes greater
>> than IW.. In datacenters we routinely send bursts that are higher withou=
t
>> causing loss. The MUST here seems unnecessary. It also conflicts with th=
e
>> RECOMMENDED in an earlier sentence.
>>
>> There's a way of satisfying both desires: have the NIC handle the
>> pacing.
>> --
>> Cheers,
>>   Jeremy
>>
>>

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

<div dir=3D"ltr"><div dir=3D"ltr">Hi, Ian,=C2=A0</div><br><div class=3D"gma=
il_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jul 20, 2020 at 11:=
49 AM Ian Swett &lt;ianswett=3D<a href=3D"mailto:40google.com@dmarc.ietf.or=
g">40google.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(2=
04,204,204);padding-left:1ex"><div dir=3D"ltr">I think it&#39;s ok to inclu=
de burst limits in the set of things we expect may be different in DCs, but=
 if we do that, I&#39;d prefer to use the RECOMMENDED rather than SHOULD,</=
div></blockquote><div><br></div><div>Aren&#39;t RECOMMENDED and SHOULD equi=
valent in=C2=A0

<a href=3D"https://tools.ietf.org/html/rfc2119">https://tools.ietf.org/html=
/rfc2119</a>?=C2=A0</div><div><br></div><div>Or am I misunderstanding your =
point?</div><div><br></div><div><pre style=3D"margin-top:0px;margin-bottom:=
0px;color:rgb(0,0,0)"><font size=3D"4"><span class=3D"gmail-h2" style=3D"di=
splay:inline;font-weight:bold"><h2 style=3D"display:inline"><a class=3D"gma=
il-selflink" name=3D"section-3" href=3D"https://tools.ietf.org/html/rfc2119=
#section-3" style=3D"color:black;text-decoration-line:none">3</a>. SHOULD  =
</h2></span> This word, or the adjective &quot;RECOMMENDED&quot;, mean that=
 there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.</font></pre></div>=
<div>=C2=A0</div><div>Best,</div><div><br></div><div>Spencer</div><div><br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"> s=
ince there are a number of SHOULDs which I believe=C2=A0apply both to the p=
ublic internet and to DCs.=C2=A0 Then we could add a note at the top about =
how there are some values which are RECOMMENDED, including X, Y and Z, and =
those recommendations are expected to be good choices for most, but not all=
 environments.<div><br></div><div>In terms of text, I&#39;d suggest taking =
Neal&#39;s suggestion and dropping an explicit mention of the public intern=
et:</div><div><br></div><div><pre style=3D"white-space:pre-wrap;margin:0in;=
font-size:10pt;font-family:&quot;Courier New&quot;;break-before:page"><span=
 style=3D"color:black">Implementations MUST either use pacing or another me=
thod to limit such bursts.<u></u><u></u></span></pre><pre style=3D"white-sp=
ace:pre-wrap;margin:0in;font-size:10pt;font-family:&quot;Courier New&quot;;=
break-before:page"><span style=3D"color:black">It is RECOMMENDED that imple=
mentations limit bursts to the initial </span>congestion window; see <a hre=
f=3D"https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fto=
ols.ietf.org%2Fhtml%2Fdraft-ietf-quic-recovery-29%23section-7.2&amp;data=3D=
02%7C01%7Cpravb%40microsoft.com%7C9df3e5f4f0ca4e586f0908d824e0a3ad%7C72f988=
bf86f141af91ab2d7cd011db47%7C1%7C0%7C637299894526657906&amp;sdata=3Dze%2F7S=
pKUbrdgwI6m%2BS6uEGSBgc2NapVtPn9vkOYFjVs%3D&amp;reserved=3D0" style=3D"font=
-size:10pt" target=3D"_blank">Section 7.2</a><span style=3D"font-size:10pt;=
color:black">.</span></pre></div></div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D"gmail_attr">On Sun, Jul 19, 2020 at 4:08 PM Praveen Ba=
lasubramanian &lt;pravb=3D<a href=3D"mailto:40microsoft.com@dmarc.ietf.org"=
 target=3D"_blank">40microsoft.com@dmarc.ietf.org</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">





<div lang=3D"EN-US">
<div>
<p class=3D"MsoNormal">&gt;&gt; There&#39;s a way of satisfying both desire=
s: have the NIC handle the pacing.<u></u><u></u></p>
<p class=3D"MsoNormal">Yes letting the NIC handle pacing will make improve =
CPU efficiency and improve accuracy due to fine grained hardware timers. Bu=
t that=E2=80=99s in the future. Today=E2=80=99s NICs don=E2=80=99t pace lar=
ge send offloads for TCP or UDP.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">&gt;&gt; Perhaps we can have a principle here: recom=
mendations that are specific for Internet use are just that, and we use SHO=
ULDs for those. IW10 makes sense based on this, and I would then also be fi=
ne with changing the MUST to a SHOULD. Perhaps
 we can state this principle upfront.<u></u><u></u></p>
<p class=3D"MsoNormal">I like the idea of stating that principle up front. =
SHOULD would be sufficient resolution for the burst size issue.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<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>
Jana Iyengar<br>
<b>Sent:</b> Friday, July 17, 2020 7:18 PM<br>
<b>To:</b> QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">q=
uic@ietf.org</a>&gt;<br>
<b>Subject:</b> [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29<u=
></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">There&#39;s a protocol question and there&#39;s a qu=
estion of endpoint behavior. In terms of the protocol itself, yes, there&#3=
9;s no real need to distinguish between Internet and DC environments; we&#3=
9;ve tried to ensure that the protocol can be used
 broadly. My point was that the constants=C2=A0in the spec were based on wh=
at we believe to be true for the public Internet, and not for DC environmen=
ts.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">That said, perhaps I was a bit too hasty. IW10 and I=
nitialRTT values are the others I was thinking about, but those are=C2=A0re=
commendations in the spec, not requirements. And as Ian notes, there&#39;s =
no minimum timeout anymore.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Perhaps we can have a principle here: recommendation=
s that are specific for Internet use are just that, and we use SHOULDs for =
those. IW10 makes sense based on this, and I would then also be fine with c=
hanging the MUST to a SHOULD. Perhaps
 we can state this principle upfront.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Ian, I share your hesitation that we don&#39;t want =
to make a distinction between private and public networks,=C2=A0but we alre=
ady allow for implementations to do that with a different=C2=A0IW and Initi=
al RTT. Is it different when talking about burst
 limits?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Fri, Jul 17, 2020 at 3:07 PM Jeremy Harris &lt;<a=
 href=3D"mailto:jgh@wizmail.org" target=3D"_blank">jgh@wizmail.org</a>&gt; =
wrote:<u></u><u></u></p>
</div>
<blockquote>
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt">On 08/07/2020 22:29, Pr=
aveen Balasubramanian wrote:<br>
&gt; Section 7.9<br>
&gt; &quot;Implementations MUST either use pacing or another method to limi=
t such bursts to the initial congestion window; see Section 7.2.&quot;<br>
&gt; This seems to preclude use of segmentation offload of sizes greater th=
an IW.. In datacenters we routinely send bursts that are higher without cau=
sing loss. The MUST here seems unnecessary. It also conflicts with the RECO=
MMENDED in an earlier sentence.<br>
<br>
There&#39;s a way of satisfying both desires: have the NIC handle the<br>
pacing.<br>
-- <br>
Cheers,<br>
=C2=A0 Jeremy<u></u><u></u></p>
</blockquote>
</div>
</div>
</div>

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

--000000000000a5f1cf05aae6372a--


From nobody Mon Jul 20 14:33:51 2020
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 26D7B3A0FA9 for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 14:33:49 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level: 
X-Spam-Status: No, score=-17.599 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, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, 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 PxPJgm5Hy17H for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 14:33:47 -0700 (PDT)
Received: from mail-yb1-xb2d.google.com (mail-yb1-xb2d.google.com [IPv6:2607:f8b0:4864:20::b2d]) (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 146B33A0FA7 for <quic@ietf.org>; Mon, 20 Jul 2020 14:33:46 -0700 (PDT)
Received: by mail-yb1-xb2d.google.com with SMTP id v9so9005463ybe.3 for <quic@ietf.org>; Mon, 20 Jul 2020 14:33:46 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=j1xatBAiZpnuE8vlXMEGbknMFXVqsHhsh/cArSHD7bI=; b=gqbJ1ib9/psDPJ39M66vGIztC+Xq9YkGGIa6hCpdn0WaDq6aR/SxbjapRmrtHnHJjc RlMoXtfhi4TXxI/9IM0BLs5OebYi8Tk8ALkFlC1WBWU2EtgMINqM0Jd85opF9uP98kce bFYjVcjt3f9cbJVPHv4laVtsp+f4P95DsG/6RhAb9+mnm5U3CjztKZ7dnKwG/gkglQiU Su0HUmkfSfBMaT4xQKD6V+Puj0WqpMmmgi+RDHVfsDD6EKloguYmHKTh3HqthmyQvJuq zfcRCHUFRdIOFU/XDIPX7UwxgogyB1SlkG8CYqg9P55UBeN4/XXL16AnERe5XMubXvfh w3Kw==
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=j1xatBAiZpnuE8vlXMEGbknMFXVqsHhsh/cArSHD7bI=; b=fac2uMuKr5fb8sApbROLXazvR9pcLB1W+Pf22tEQaCJ2ZzuchDlmlnEpzJ/XSF97r1 QgsYF+ZWFugi1w72Vaz6tWCZ0x9MkBABFR3d5CQZTbUiSoNotsn9lUJ5rUT6bAU35ADc iBwy2cFtx5zha4dWc/EAwUmFsSh/VL9IQ2UK5iKS17KT8VDfSLeNFa0VWCSguN4GFPCp NAQ9Uvoeqwjo/VVyw+/usdLsX2rojjo5KlEW+aPuwcfxlTH8DyaCUt6E4R3eyo8utTsb /8UUfpy3dWxhtgFPOHBWTPG7KYdtk6wiejWq2WcwPVauaaHBDO4pdd1wdEKEy0Kpu6Ky KRwA==
X-Gm-Message-State: AOAM5321oA1ViwYe9x7IvVNCjFAM0Ei20oc36kxcgO827ZqvRR8zkNk7 oET7SSRcUrKrenYSneoFD/A/3tvXdhWj0pOQmA/MOw==
X-Google-Smtp-Source: ABdhPJzBZJz59k80T6mmyaahduxs9Z18niZ3BuBIGZVePz3br9d2MwcF4C2kO/bOD9qWaWdwyeAKkKI59JV/jgeXwVc=
X-Received: by 2002:a25:8206:: with SMTP id q6mr37518263ybk.388.1595280825848;  Mon, 20 Jul 2020 14:33:45 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <9f57b20d-2eba-b2b9-d8c8-48e019c8952a@wizmail.org> <CACpbDccrpHeP5PYGCZky+AN2gC9YSs5gbAzYr4Yrw1LpvHZNiA@mail.gmail.com> <CH2PR00MB07269A73542DBC8E51E95519B67A0@CH2PR00MB0726.namprd00.prod.outlook.com> <CAKcm_gMhRX3NxiW6Primy+UrY44ZahaSO+9kF5CeeN4=XqL2JQ@mail.gmail.com> <CAKKJt-fY92k5ym767GofK+DOMQs=x6dpkwkKOA1cpkUf8Xs+3A@mail.gmail.com>
In-Reply-To: <CAKKJt-fY92k5ym767GofK+DOMQs=x6dpkwkKOA1cpkUf8Xs+3A@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Mon, 20 Jul 2020 17:33:34 -0400
Message-ID: <CAKcm_gPyg4QM+mZq_-E-av=u_X4nCWwdDXEH6e9Sjz1d8scEyg@mail.gmail.com>
Subject: Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Cc: Praveen Balasubramanian <pravb@microsoft.com>, Jana Iyengar <jri.ietf@gmail.com>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f19dfb05aae6424d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/D7yWvo23aQN4WcYOmpEIKGl-Rnw>
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, 20 Jul 2020 21:33:49 -0000

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

Most of the items which I felt were somewhat deployment-specific
constants(ie: Initial Window and Initial RTT) are 'RECOMMENDED' in the
current recovery draft, so I thought it'd be preferable to keep that
convention.

On Mon, Jul 20, 2020 at 5:30 PM Spencer Dawkins at IETF <
spencerdawkins.ietf@gmail.com> wrote:

> Hi, Ian,
>
> On Mon, Jul 20, 2020 at 11:49 AM Ian Swett <ianswett=3D
> 40google.com@dmarc.ietf.org> wrote:
>
>> I think it's ok to include burst limits in the set of things we expect
>> may be different in DCs, but if we do that, I'd prefer to use the
>> RECOMMENDED rather than SHOULD,
>>
>
> Aren't RECOMMENDED and SHOULD equivalent in
> https://tools.ietf.org/html/rfc2119?
>
> Or am I misunderstanding your point?
>
> 3 <https://tools.ietf.org/html/rfc2119#section-3>. SHOULD   This word, or=
 the adjective "RECOMMENDED", mean that there
>    may exist valid reasons in particular circumstances to ignore a
>    particular item, but the full implications must be understood and
>    carefully weighed before choosing a different course.
>
>
> Best,
>
> Spencer
>
> since there are a number of SHOULDs which I believe apply both to the
>> public internet and to DCs.  Then we could add a note at the top about h=
ow
>> there are some values which are RECOMMENDED, including X, Y and Z, and
>> those recommendations are expected to be good choices for most, but not =
all
>> environments.
>>
>> In terms of text, I'd suggest taking Neal's suggestion and dropping an
>> explicit mention of the public internet:
>>
>> Implementations MUST either use pacing or another method to limit such b=
ursts.
>>
>> It is RECOMMENDED that implementations limit bursts to the initial conge=
stion window; see Section 7.2 <https://nam06.safelinks.protection.outlook.c=
om/?url=3Dhttps%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-quic-recovery-29=
%23section-7.2&data=3D02%7C01%7Cpravb%40microsoft.com%7C9df3e5f4f0ca4e586f0=
908d824e0a3ad%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6372998945266579=
06&sdata=3Dze%2F7SpKUbrdgwI6m%2BS6uEGSBgc2NapVtPn9vkOYFjVs%3D&reserved=3D0>=
.
>>
>>
>> On Sun, Jul 19, 2020 at 4:08 PM Praveen Balasubramanian <pravb=3D
>> 40microsoft.com@dmarc.ietf.org> wrote:
>>
>>> >> There's a way of satisfying both desires: have the NIC handle the
>>> pacing.
>>>
>>> Yes letting the NIC handle pacing will make improve CPU efficiency and
>>> improve accuracy due to fine grained hardware timers. But that=E2=80=99=
s in the
>>> future. Today=E2=80=99s NICs don=E2=80=99t pace large send offloads for=
 TCP or UDP.
>>>
>>>
>>>
>>> >> Perhaps we can have a principle here: recommendations that are
>>> specific for Internet use are just that, and we use SHOULDs for those. =
IW10
>>> makes sense based on this, and I would then also be fine with changing =
the
>>> MUST to a SHOULD. Perhaps we can state this principle upfront.
>>>
>>> I like the idea of stating that principle up front. SHOULD would be
>>> sufficient resolution for the burst size issue.
>>>
>>>
>>>
>>> *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of * Jana Iyengar
>>> *Sent:* Friday, July 17, 2020 7:18 PM
>>> *To:* QUIC WG <quic@ietf.org>
>>> *Subject:* [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
>>>
>>>
>>>
>>> There's a protocol question and there's a question of endpoint behavior=
.
>>> In terms of the protocol itself, yes, there's no real need to distingui=
sh
>>> between Internet and DC environments; we've tried to ensure that the
>>> protocol can be used broadly. My point was that the constants in the sp=
ec
>>> were based on what we believe to be true for the public Internet, and n=
ot
>>> for DC environments.
>>>
>>>
>>>
>>> That said, perhaps I was a bit too hasty. IW10 and InitialRTT values ar=
e
>>> the others I was thinking about, but those are recommendations in the s=
pec,
>>> not requirements. And as Ian notes, there's no minimum timeout anymore.
>>>
>>>
>>>
>>> Perhaps we can have a principle here: recommendations that are specific
>>> for Internet use are just that, and we use SHOULDs for those. IW10 make=
s
>>> sense based on this, and I would then also be fine with changing the MU=
ST
>>> to a SHOULD. Perhaps we can state this principle upfront.
>>>
>>>
>>>
>>> Ian, I share your hesitation that we don't want to make a distinction
>>> between private and public networks, but we already allow for
>>> implementations to do that with a different IW and Initial RTT. Is it
>>> different when talking about burst limits?
>>>
>>>
>>>
>>>
>>>
>>> On Fri, Jul 17, 2020 at 3:07 PM Jeremy Harris <jgh@wizmail.org> wrote:
>>>
>>> On 08/07/2020 22:29, Praveen Balasubramanian wrote:
>>> > Section 7.9
>>> > "Implementations MUST either use pacing or another method to limit
>>> such bursts to the initial congestion window; see Section 7.2."
>>> > This seems to preclude use of segmentation offload of sizes greater
>>> than IW.. In datacenters we routinely send bursts that are higher witho=
ut
>>> causing loss. The MUST here seems unnecessary. It also conflicts with t=
he
>>> RECOMMENDED in an earlier sentence.
>>>
>>> There's a way of satisfying both desires: have the NIC handle the
>>> pacing.
>>> --
>>> Cheers,
>>>   Jeremy
>>>
>>>

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

<div dir=3D"ltr">Most of the items which I felt were somewhat deployment-sp=
ecific constants(ie: Initial Window and Initial RTT) are &#39;RECOMMENDED&#=
39; in the current recovery draft, so I thought it&#39;d be preferable to k=
eep that convention.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" c=
lass=3D"gmail_attr">On Mon, Jul 20, 2020 at 5:30 PM Spencer Dawkins at IETF=
 &lt;<a href=3D"mailto:spencerdawkins.ietf@gmail.com">spencerdawkins.ietf@g=
mail.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-le=
ft:1ex"><div dir=3D"ltr"><div dir=3D"ltr">Hi, Ian,=C2=A0</div><br><div clas=
s=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jul 20, 202=
0 at 11:49 AM Ian Swett &lt;ianswett=3D<a href=3D"mailto:40google.com@dmarc=
.ietf.org" target=3D"_blank">40google.com@dmarc.ietf.org</a>&gt; wrote:<br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">I =
think it&#39;s ok to include burst limits in the set of things we expect ma=
y be different in DCs, but if we do that, I&#39;d prefer to use the RECOMME=
NDED rather than SHOULD,</div></blockquote><div><br></div><div>Aren&#39;t R=
ECOMMENDED and SHOULD equivalent in=C2=A0

<a href=3D"https://tools.ietf.org/html/rfc2119" target=3D"_blank">https://t=
ools.ietf.org/html/rfc2119</a>?=C2=A0</div><div><br></div><div>Or am I misu=
nderstanding your point?</div><div><br></div><div><pre style=3D"margin-top:=
0px;margin-bottom:0px;color:rgb(0,0,0)"><font size=3D"4"><span style=3D"dis=
play:inline;font-weight:bold"><h2 style=3D"display:inline"><a name=3D"m_-56=
1907519085294557_section-3" href=3D"https://tools.ietf.org/html/rfc2119#sec=
tion-3" style=3D"color:black;text-decoration-line:none" target=3D"_blank">3=
</a>. SHOULD  </h2></span> This word, or the adjective &quot;RECOMMENDED&qu=
ot;, mean that there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.</font></pre></div>=
<div>=C2=A0</div><div>Best,</div><div><br></div><div>Spencer</div><div><br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"> s=
ince there are a number of SHOULDs which I believe=C2=A0apply both to the p=
ublic internet and to DCs.=C2=A0 Then we could add a note at the top about =
how there are some values which are RECOMMENDED, including X, Y and Z, and =
those recommendations are expected to be good choices for most, but not all=
 environments.<div><br></div><div>In terms of text, I&#39;d suggest taking =
Neal&#39;s suggestion and dropping an explicit mention of the public intern=
et:</div><div><br></div><div><pre style=3D"white-space:pre-wrap;margin:0in;=
font-size:10pt;font-family:&quot;Courier New&quot;;break-before:page"><span=
 style=3D"color:black">Implementations MUST either use pacing or another me=
thod to limit such bursts.<u></u><u></u></span></pre><pre style=3D"white-sp=
ace:pre-wrap;margin:0in;font-size:10pt;font-family:&quot;Courier New&quot;;=
break-before:page"><span style=3D"color:black">It is RECOMMENDED that imple=
mentations limit bursts to the initial </span>congestion window; see <a hre=
f=3D"https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fto=
ols.ietf.org%2Fhtml%2Fdraft-ietf-quic-recovery-29%23section-7.2&amp;data=3D=
02%7C01%7Cpravb%40microsoft.com%7C9df3e5f4f0ca4e586f0908d824e0a3ad%7C72f988=
bf86f141af91ab2d7cd011db47%7C1%7C0%7C637299894526657906&amp;sdata=3Dze%2F7S=
pKUbrdgwI6m%2BS6uEGSBgc2NapVtPn9vkOYFjVs%3D&amp;reserved=3D0" style=3D"font=
-size:10pt" target=3D"_blank">Section 7.2</a><span style=3D"font-size:10pt;=
color:black">.</span></pre></div></div><br><div class=3D"gmail_quote"><div =
dir=3D"ltr" class=3D"gmail_attr">On Sun, Jul 19, 2020 at 4:08 PM Praveen Ba=
lasubramanian &lt;pravb=3D<a href=3D"mailto:40microsoft.com@dmarc.ietf.org"=
 target=3D"_blank">40microsoft.com@dmarc.ietf.org</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">





<div lang=3D"EN-US">
<div>
<p class=3D"MsoNormal">&gt;&gt; There&#39;s a way of satisfying both desire=
s: have the NIC handle the pacing.<u></u><u></u></p>
<p class=3D"MsoNormal">Yes letting the NIC handle pacing will make improve =
CPU efficiency and improve accuracy due to fine grained hardware timers. Bu=
t that=E2=80=99s in the future. Today=E2=80=99s NICs don=E2=80=99t pace lar=
ge send offloads for TCP or UDP.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">&gt;&gt; Perhaps we can have a principle here: recom=
mendations that are specific for Internet use are just that, and we use SHO=
ULDs for those. IW10 makes sense based on this, and I would then also be fi=
ne with changing the MUST to a SHOULD. Perhaps
 we can state this principle upfront.<u></u><u></u></p>
<p class=3D"MsoNormal">I like the idea of stating that principle up front. =
SHOULD would be sufficient resolution for the burst size issue.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<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>
Jana Iyengar<br>
<b>Sent:</b> Friday, July 17, 2020 7:18 PM<br>
<b>To:</b> QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">q=
uic@ietf.org</a>&gt;<br>
<b>Subject:</b> [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29<u=
></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">There&#39;s a protocol question and there&#39;s a qu=
estion of endpoint behavior. In terms of the protocol itself, yes, there&#3=
9;s no real need to distinguish between Internet and DC environments; we&#3=
9;ve tried to ensure that the protocol can be used
 broadly. My point was that the constants=C2=A0in the spec were based on wh=
at we believe to be true for the public Internet, and not for DC environmen=
ts.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">That said, perhaps I was a bit too hasty. IW10 and I=
nitialRTT values are the others I was thinking about, but those are=C2=A0re=
commendations in the spec, not requirements. And as Ian notes, there&#39;s =
no minimum timeout anymore.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Perhaps we can have a principle here: recommendation=
s that are specific for Internet use are just that, and we use SHOULDs for =
those. IW10 makes sense based on this, and I would then also be fine with c=
hanging the MUST to a SHOULD. Perhaps
 we can state this principle upfront.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Ian, I share your hesitation that we don&#39;t want =
to make a distinction between private and public networks,=C2=A0but we alre=
ady allow for implementations to do that with a different=C2=A0IW and Initi=
al RTT. Is it different when talking about burst
 limits?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Fri, Jul 17, 2020 at 3:07 PM Jeremy Harris &lt;<a=
 href=3D"mailto:jgh@wizmail.org" target=3D"_blank">jgh@wizmail.org</a>&gt; =
wrote:<u></u><u></u></p>
</div>
<blockquote>
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt">On 08/07/2020 22:29, Pr=
aveen Balasubramanian wrote:<br>
&gt; Section 7.9<br>
&gt; &quot;Implementations MUST either use pacing or another method to limi=
t such bursts to the initial congestion window; see Section 7.2.&quot;<br>
&gt; This seems to preclude use of segmentation offload of sizes greater th=
an IW.. In datacenters we routinely send bursts that are higher without cau=
sing loss. The MUST here seems unnecessary. It also conflicts with the RECO=
MMENDED in an earlier sentence.<br>
<br>
There&#39;s a way of satisfying both desires: have the NIC handle the<br>
pacing.<br>
-- <br>
Cheers,<br>
=C2=A0 Jeremy<u></u><u></u></p>
</blockquote>
</div>
</div>
</div>

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

--000000000000f19dfb05aae6424d--


From nobody Mon Jul 20 15:11:19 2020
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 175EC3A1020 for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 15:11:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 obj9E_6LCHFA for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 15:11:15 -0700 (PDT)
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 5E3593A0F8E for <quic@ietf.org>; Mon, 20 Jul 2020 15:11:15 -0700 (PDT)
Received: by mail-lf1-x135.google.com with SMTP id k17so10570411lfg.3 for <quic@ietf.org>; Mon, 20 Jul 2020 15:11:15 -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=q7j5VYLkfIZRUPS5nQif53y0H64c9/jBjTbV7b5sES4=; b=QQqxQbfUQqJZaorUUScN1grq69seIvSi5ma63ZLLjkGKDkCf45kMDqNVkEWbTnCBB4 s+6sj1NFnZ8XpgH00kkNh1ANDdLhsHm2fRKZ3pqBP0dt/cMWZ1h+lKauwjq0+FAbo++G R+VthGC2mjhzW+X90MzoELRzXUiKPR3r7P9Zsiza5KySEvNr4k55B4KVT/0/e1PX0NsK a20uFbuRynNqqDgMOwNdfG48AeaMr6tV/Ymn6H5SdHW3U/NEQNRAbsM31fI07o0f42Fc mt3jyNEMri8dzUCH9FC+WZxO0kwFDfwU/UedpCl4Etzn7wTr41G3usNQcGFLQ/yEN31X ycTw==
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=q7j5VYLkfIZRUPS5nQif53y0H64c9/jBjTbV7b5sES4=; b=LFqFjU0xQKkYUDQZipSAg1B192XXOPOpbZd5IIahTYXoPO3t7bQMNmi17PLCaOmioS 9ib0eYegx4kVevh+7WFKNinfZdbZk90pruBCYEcIxa+D/um/0Wi1z3tI1hufmIOOc16v Azzsc6S/KaK29lJh7IDmhyrlmFGJ0UDu5ezxfYmLt61bqQsQVuinkFdGWHR3y3AmoHXP dprAzHrAes7Md8NyaOWL/av8S595ApdlUVMCZCA9so2Bfc5WB0tu6Rw5RjIVHhe47TFS VKSkhP6fXGe9FWPadmhhfxqRB6DjzcMxQEbZg2950VSKlSra8LEPEskkTKjAMIb4UkOG paXA==
X-Gm-Message-State: AOAM531WiUMOuQ3JT9sjAorrVV8eirIVWYY2Pw6nK9eHQBx2j6Ci8+5i 3Hw6IeulDZNxUYXKqrZIABpWwyPq9f4SzVa3dw4=
X-Google-Smtp-Source: ABdhPJzj+m9OhcfsCzJ1ZtHMHHf5E44HMEAb5scJj6pYfWpPrxT+JG19qgSuY/jfwzaZpvFNhtNl3O0a8GSF8GnMwVA=
X-Received: by 2002:ac2:4ec4:: with SMTP id p4mr11583115lfr.157.1595283073430;  Mon, 20 Jul 2020 15:11:13 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <9f57b20d-2eba-b2b9-d8c8-48e019c8952a@wizmail.org> <CACpbDccrpHeP5PYGCZky+AN2gC9YSs5gbAzYr4Yrw1LpvHZNiA@mail.gmail.com> <CH2PR00MB07269A73542DBC8E51E95519B67A0@CH2PR00MB0726.namprd00.prod.outlook.com> <CAKcm_gMhRX3NxiW6Primy+UrY44ZahaSO+9kF5CeeN4=XqL2JQ@mail.gmail.com> <CAKKJt-fY92k5ym767GofK+DOMQs=x6dpkwkKOA1cpkUf8Xs+3A@mail.gmail.com> <CAKcm_gPyg4QM+mZq_-E-av=u_X4nCWwdDXEH6e9Sjz1d8scEyg@mail.gmail.com>
In-Reply-To: <CAKcm_gPyg4QM+mZq_-E-av=u_X4nCWwdDXEH6e9Sjz1d8scEyg@mail.gmail.com>
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Mon, 20 Jul 2020 17:11:01 -0500
Message-ID: <CAKKJt-fmqjXJEUHzFT0yBXE0sLvOPcnM-oCBDZfgZQNgerRt8g@mail.gmail.com>
Subject: Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
To: Ian Swett <ianswett@google.com>
Cc: Praveen Balasubramanian <pravb@microsoft.com>, Jana Iyengar <jri.ietf@gmail.com>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e8772305aae6c856"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/H6DzPYKGPZFen0Hxvv1esZgWPyU>
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, 20 Jul 2020 22:11:18 -0000

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

Hi, Ian,

On Mon, Jul 20, 2020, 16:33 Ian Swett <ianswett@google.com> wrote:

> Most of the items which I felt were somewhat deployment-specific
> constants(ie: Initial Window and Initial RTT) are 'RECOMMENDED' in the
> current recovery draft, so I thought it'd be preferable to keep that
> convention.
>

Thanks for helping me understand - this is a stylistic change.

I've had a couple of conversations outside of QUIC recently with people who
were interpreting the two terms somewhat differently, so thought it a good
time to ask.

Best,

Spencer

>
> On Mon, Jul 20, 2020 at 5:30 PM Spencer Dawkins at IETF <
> spencerdawkins.ietf@gmail.com> wrote:
>
>> Hi, Ian,
>>
>> On Mon, Jul 20, 2020 at 11:49 AM Ian Swett <ianswett=3D
>> 40google.com@dmarc.ietf.org> wrote:
>>
>>> I think it's ok to include burst limits in the set of things we expect
>>> may be different in DCs, but if we do that, I'd prefer to use the
>>> RECOMMENDED rather than SHOULD,
>>>
>>
>> Aren't RECOMMENDED and SHOULD equivalent in
>> https://tools.ietf.org/html/rfc2119?
>>
>> Or am I misunderstanding your point?
>>
>> 3 <https://tools.ietf.org/html/rfc2119#section-3>. SHOULD   This word, o=
r the adjective "RECOMMENDED", mean that there
>>    may exist valid reasons in particular circumstances to ignore a
>>    particular item, but the full implications must be understood and
>>    carefully weighed before choosing a different course.
>>
>>
>> Best,
>>
>> Spencer
>>
>> since there are a number of SHOULDs which I believe apply both to the
>>> public internet and to DCs.  Then we could add a note at the top about =
how
>>> there are some values which are RECOMMENDED, including X, Y and Z, and
>>> those recommendations are expected to be good choices for most, but not=
 all
>>> environments.
>>>
>>> In terms of text, I'd suggest taking Neal's suggestion and dropping an
>>> explicit mention of the public internet:
>>>
>>> Implementations MUST either use pacing or another method to limit such =
bursts.
>>>
>>> It is RECOMMENDED that implementations limit bursts to the initial cong=
estion window; see Section 7.2 <https://nam06.safelinks.protection.outlook.=
com/?url=3Dhttps%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-quic-recovery-2=
9%23section-7.2&data=3D02%7C01%7Cpravb%40microsoft.com%7C9df3e5f4f0ca4e586f=
0908d824e0a3ad%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637299894526657=
906&sdata=3Dze%2F7SpKUbrdgwI6m%2BS6uEGSBgc2NapVtPn9vkOYFjVs%3D&reserved=3D0=
>.
>>>
>>>
>>> On Sun, Jul 19, 2020 at 4:08 PM Praveen Balasubramanian <pravb=3D
>>> 40microsoft.com@dmarc.ietf.org> wrote:
>>>
>>>> >> There's a way of satisfying both desires: have the NIC handle the
>>>> pacing.
>>>>
>>>> Yes letting the NIC handle pacing will make improve CPU efficiency and
>>>> improve accuracy due to fine grained hardware timers. But that=E2=80=
=99s in the
>>>> future. Today=E2=80=99s NICs don=E2=80=99t pace large send offloads fo=
r TCP or UDP.
>>>>
>>>>
>>>>
>>>> >> Perhaps we can have a principle here: recommendations that are
>>>> specific for Internet use are just that, and we use SHOULDs for those.=
 IW10
>>>> makes sense based on this, and I would then also be fine with changing=
 the
>>>> MUST to a SHOULD. Perhaps we can state this principle upfront.
>>>>
>>>> I like the idea of stating that principle up front. SHOULD would be
>>>> sufficient resolution for the burst size issue.
>>>>
>>>>
>>>>
>>>> *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of * Jana Iyengar
>>>> *Sent:* Friday, July 17, 2020 7:18 PM
>>>> *To:* QUIC WG <quic@ietf.org>
>>>> *Subject:* [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
>>>>
>>>>
>>>>
>>>> There's a protocol question and there's a question of endpoint
>>>> behavior. In terms of the protocol itself, yes, there's no real need t=
o
>>>> distinguish between Internet and DC environments; we've tried to ensur=
e
>>>> that the protocol can be used broadly. My point was that the constants=
 in
>>>> the spec were based on what we believe to be true for the public Inter=
net,
>>>> and not for DC environments.
>>>>
>>>>
>>>>
>>>> That said, perhaps I was a bit too hasty. IW10 and InitialRTT values
>>>> are the others I was thinking about, but those are recommendations in =
the
>>>> spec, not requirements. And as Ian notes, there's no minimum timeout
>>>> anymore.
>>>>
>>>>
>>>>
>>>> Perhaps we can have a principle here: recommendations that are specifi=
c
>>>> for Internet use are just that, and we use SHOULDs for those. IW10 mak=
es
>>>> sense based on this, and I would then also be fine with changing the M=
UST
>>>> to a SHOULD. Perhaps we can state this principle upfront.
>>>>
>>>>
>>>>
>>>> Ian, I share your hesitation that we don't want to make a distinction
>>>> between private and public networks, but we already allow for
>>>> implementations to do that with a different IW and Initial RTT. Is it
>>>> different when talking about burst limits?
>>>>
>>>>
>>>>
>>>>
>>>>
>>>> On Fri, Jul 17, 2020 at 3:07 PM Jeremy Harris <jgh@wizmail.org> wrote:
>>>>
>>>> On 08/07/2020 22:29, Praveen Balasubramanian wrote:
>>>> > Section 7.9
>>>> > "Implementations MUST either use pacing or another method to limit
>>>> such bursts to the initial congestion window; see Section 7.2."
>>>> > This seems to preclude use of segmentation offload of sizes greater
>>>> than IW.. In datacenters we routinely send bursts that are higher with=
out
>>>> causing loss. The MUST here seems unnecessary. It also conflicts with =
the
>>>> RECOMMENDED in an earlier sentence.
>>>>
>>>> There's a way of satisfying both desires: have the NIC handle the
>>>> pacing.
>>>> --
>>>> Cheers,
>>>>   Jeremy
>>>>
>>>>

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

<div dir=3D"auto"><div>Hi, Ian,<br><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Mon, Jul 20, 2020, 16:33 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:0 0 0 .8ex;border-le=
ft:1px #ccc solid;padding-left:1ex"><div dir=3D"ltr">Most of the items whic=
h I felt were somewhat deployment-specific constants(ie: Initial Window and=
 Initial RTT) are &#39;RECOMMENDED&#39; in the current recovery draft, so I=
 thought it&#39;d be preferable to keep that convention.</div></blockquote>=
</div></div><div dir=3D"auto"><br></div><div dir=3D"auto">Thanks for helpin=
g me understand - this is a stylistic change.</div><div dir=3D"auto"><br></=
div><div dir=3D"auto">I&#39;ve had a couple of conversations outside of QUI=
C recently with people who were interpreting the two terms somewhat differe=
ntly, so thought it a good time to ask.</div><div dir=3D"auto"><br></div><d=
iv dir=3D"auto">Best,</div><div dir=3D"auto"><br></div><div dir=3D"auto">Sp=
encer</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;padd=
ing-left:1ex"><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmai=
l_attr">On Mon, Jul 20, 2020 at 5:30 PM Spencer Dawkins at IETF &lt;<a href=
=3D"mailto:spencerdawkins.ietf@gmail.com" target=3D"_blank" rel=3D"noreferr=
er">spencerdawkins.ietf@gmail.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 dir=3D"ltr"><div dir=3D"ltr">Hi, Ian,=
=C2=A0</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_=
attr">On Mon, Jul 20, 2020 at 11:49 AM Ian Swett &lt;ianswett=3D<a href=3D"=
mailto:40google.com@dmarc.ietf.org" target=3D"_blank" rel=3D"noreferrer">40=
google.com@dmarc.ietf.org</a>&gt; wrote:<br></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"><div dir=3D"ltr">I think it&#39;s ok to include bu=
rst limits in the set of things we expect may be different in DCs, but if w=
e do that, I&#39;d prefer to use the RECOMMENDED rather than SHOULD,</div><=
/blockquote><div><br></div><div>Aren&#39;t RECOMMENDED and SHOULD equivalen=
t in=C2=A0

<a href=3D"https://tools.ietf.org/html/rfc2119" target=3D"_blank" rel=3D"no=
referrer">https://tools.ietf.org/html/rfc2119</a>?=C2=A0</div><div><br></di=
v><div>Or am I misunderstanding your point?</div><div><br></div><div><pre s=
tyle=3D"margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><font size=3D"4"=
><span style=3D"display:inline;font-weight:bold"><h2 style=3D"display:inlin=
e"><a name=3D"m_-7104407681243286268_m_-561907519085294557_section-3" href=
=3D"https://tools.ietf.org/html/rfc2119#section-3" style=3D"color:black;tex=
t-decoration-line:none" target=3D"_blank" rel=3D"noreferrer">3</a>. SHOULD =
 </h2></span> This word, or the adjective &quot;RECOMMENDED&quot;, mean tha=
t there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.</font></pre></div>=
<div>=C2=A0</div><div>Best,</div><div><br></div><div>Spencer</div><div><br>=
</div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;b=
order-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"> s=
ince there are a number of SHOULDs which I believe=C2=A0apply both to the p=
ublic internet and to DCs.=C2=A0 Then we could add a note at the top about =
how there are some values which are RECOMMENDED, including X, Y and Z, and =
those recommendations are expected to be good choices for most, but not all=
 environments.<div><br></div><div>In terms of text, I&#39;d suggest taking =
Neal&#39;s suggestion and dropping an explicit mention of the public intern=
et:</div><div><br></div><div><pre style=3D"white-space:pre-wrap;margin:0in;=
font-size:10pt;font-family:&quot;Courier New&quot;;break-before:page"><span=
 style=3D"color:black">Implementations MUST either use pacing or another me=
thod to limit such bursts.<u></u><u></u></span></pre><pre style=3D"white-sp=
ace:pre-wrap;margin:0in;font-size:10pt;font-family:&quot;Courier New&quot;;=
break-before:page"><span style=3D"color:black">It is RECOMMENDED that imple=
mentations limit bursts to the initial </span>congestion window; see <a hre=
f=3D"https://nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fto=
ols.ietf.org%2Fhtml%2Fdraft-ietf-quic-recovery-29%23section-7.2&amp;data=3D=
02%7C01%7Cpravb%40microsoft.com%7C9df3e5f4f0ca4e586f0908d824e0a3ad%7C72f988=
bf86f141af91ab2d7cd011db47%7C1%7C0%7C637299894526657906&amp;sdata=3Dze%2F7S=
pKUbrdgwI6m%2BS6uEGSBgc2NapVtPn9vkOYFjVs%3D&amp;reserved=3D0" style=3D"font=
-size:10pt" target=3D"_blank" rel=3D"noreferrer">Section 7.2</a><span style=
=3D"font-size:10pt;color:black">.</span></pre></div></div><br><div class=3D=
"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Sun, Jul 19, 2020 at=
 4:08 PM Praveen Balasubramanian &lt;pravb=3D<a href=3D"mailto:40microsoft.=
com@dmarc.ietf.org" target=3D"_blank" rel=3D"noreferrer">40microsoft.com@dm=
arc.ietf.org</a>&gt; wrote:<br></div><blockquote class=3D"gmail_quote" styl=
e=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);paddin=
g-left:1ex">





<div lang=3D"EN-US">
<div>
<p class=3D"MsoNormal">&gt;&gt; There&#39;s a way of satisfying both desire=
s: have the NIC handle the pacing.<u></u><u></u></p>
<p class=3D"MsoNormal">Yes letting the NIC handle pacing will make improve =
CPU efficiency and improve accuracy due to fine grained hardware timers. Bu=
t that=E2=80=99s in the future. Today=E2=80=99s NICs don=E2=80=99t pace lar=
ge send offloads for TCP or UDP.<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<p class=3D"MsoNormal">&gt;&gt; Perhaps we can have a principle here: recom=
mendations that are specific for Internet use are just that, and we use SHO=
ULDs for those. IW10 makes sense based on this, and I would then also be fi=
ne with changing the MUST to a SHOULD. Perhaps
 we can state this principle upfront.<u></u><u></u></p>
<p class=3D"MsoNormal">I like the idea of stating that principle up front. =
SHOULD would be sufficient resolution for the burst size issue.
<u></u><u></u></p>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div style=3D"border-right:none;border-bottom:none;border-left:none;border-=
top:1pt solid rgb(225,225,225);padding:3pt 0in 0in">
<p class=3D"MsoNormal"><b>From:</b> QUIC &lt;<a href=3D"mailto:quic-bounces=
@ietf.org" target=3D"_blank" rel=3D"noreferrer">quic-bounces@ietf.org</a>&g=
t; <b>On Behalf Of </b>
Jana Iyengar<br>
<b>Sent:</b> Friday, July 17, 2020 7:18 PM<br>
<b>To:</b> QUIC WG &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank" r=
el=3D"noreferrer">quic@ietf.org</a>&gt;<br>
<b>Subject:</b> [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29<u=
></u><u></u></p>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<p class=3D"MsoNormal">There&#39;s a protocol question and there&#39;s a qu=
estion of endpoint behavior. In terms of the protocol itself, yes, there&#3=
9;s no real need to distinguish between Internet and DC environments; we&#3=
9;ve tried to ensure that the protocol can be used
 broadly. My point was that the constants=C2=A0in the spec were based on wh=
at we believe to be true for the public Internet, and not for DC environmen=
ts.<u></u><u></u></p>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">That said, perhaps I was a bit too hasty. IW10 and I=
nitialRTT values are the others I was thinking about, but those are=C2=A0re=
commendations in the spec, not requirements. And as Ian notes, there&#39;s =
no minimum timeout anymore.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Perhaps we can have a principle here: recommendation=
s that are specific for Internet use are just that, and we use SHOULDs for =
those. IW10 makes sense based on this, and I would then also be fine with c=
hanging the MUST to a SHOULD. Perhaps
 we can state this principle upfront.<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
<div>
<p class=3D"MsoNormal">Ian, I share your hesitation that we don&#39;t want =
to make a distinction between private and public networks,=C2=A0but we alre=
ady allow for implementations to do that with a different=C2=A0IW and Initi=
al RTT. Is it different when talking about burst
 limits?<u></u><u></u></p>
</div>
<div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
</div>
</div>
<p class=3D"MsoNormal"><u></u>=C2=A0<u></u></p>
<div>
<div>
<p class=3D"MsoNormal">On Fri, Jul 17, 2020 at 3:07 PM Jeremy Harris &lt;<a=
 href=3D"mailto:jgh@wizmail.org" target=3D"_blank" rel=3D"noreferrer">jgh@w=
izmail.org</a>&gt; wrote:<u></u><u></u></p>
</div>
<blockquote>
<p class=3D"MsoNormal" style=3D"margin-bottom:12pt">On 08/07/2020 22:29, Pr=
aveen Balasubramanian wrote:<br>
&gt; Section 7.9<br>
&gt; &quot;Implementations MUST either use pacing or another method to limi=
t such bursts to the initial congestion window; see Section 7.2.&quot;<br>
&gt; This seems to preclude use of segmentation offload of sizes greater th=
an IW.. In datacenters we routinely send bursts that are higher without cau=
sing loss. The MUST here seems unnecessary. It also conflicts with the RECO=
MMENDED in an earlier sentence.<br>
<br>
There&#39;s a way of satisfying both desires: have the NIC handle the<br>
pacing.<br>
-- <br>
Cheers,<br>
=C2=A0 Jeremy<u></u><u></u></p>
</blockquote>
</div>
</div>
</div>

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

--000000000000e8772305aae6c856--


From nobody Mon Jul 20 17:31:14 2020
Return-Path: <jupiter.hce@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 8A9A23A1215 for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 17:31:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, 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 pDyA2_j_xtAW for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 17:31:11 -0700 (PDT)
Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) (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 46AE33A1219 for <quic@ietf.org>; Mon, 20 Jul 2020 17:31:11 -0700 (PDT)
Received: by mail-ej1-x62d.google.com with SMTP id f12so19853992eja.9 for <quic@ietf.org>; Mon, 20 Jul 2020 17:31:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=uq413mqgQXML87lfA+QpMYoPd3ItbZfzkv7nqK56Buo=; b=EOHMFnIBCPorhdLh4nQFPoy8CmHZ6i7LG371gGuinePTG4glg1zmsqgjJfsDRiy2Zx 6gQcWGzqn2x7Xd8mWuen7F3Xc7L6DgGUAeGIQ3TiOhhAA56jcmv1QkSheem5ugkmTJC8 py8jZDrcUyFnb71ET49g63x1tAF0GXK3jz5+CfXgYxFva4MBcuq2PCl1uhVY7Vc95i8E 2GzSxe7RqlQ7V7sHYGAJgw/JG/V0MmFhYqYS2bkrxjtfbGJYOpukuPHzSHWHp2YiD3gU LjKRDoJkVCCAijRaLVKv7uqMYEW1CA8XIp1YgAwEYoPBHwBPTX4WyOgX92azMAl3m4Xm JXEw==
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=uq413mqgQXML87lfA+QpMYoPd3ItbZfzkv7nqK56Buo=; b=EEOMG0bUiMt/+hriibxaKBNtdhOzM6RMmDwpabtupHp4F5Smi6vgqafDDmiIHxnLAk LUEmGtACFXUpgELwPyYfPVqFL1NEE8a0ycCne3dROuirzmunJb1DMTLvGgRKd2V6AADa aI/jhvwj2/h3ehzKDIuPjoHon8ROncFQd4r2rIOl7SdpjcPo90bkJGt5oWp66RTYSgnh Tc0sHELOCmNakT4L7NqtkK9z0IT+J9agAM077kyR44DQRYGG+LYZoy4b+/Dexn4oH6zb 4Qxhla8Etl4l7S/NGb413pnJIcUiWpasjEOyYGrysu3B6WCxRiXBWMUNApGXWZK+R8bb 8jGw==
X-Gm-Message-State: AOAM530MwPfdLuuGIPJE/G53gSZEMBcTO7lUKSxQfFBJQlDtHVey7JKR 8/dIUrGOD+3i08If3GfiEKXNd9UN0u4q5Vrit2RLfpF7
X-Google-Smtp-Source: ABdhPJzrbe2rT/+0j9qDo2eaDmt8bNUvZjLLv+/NoDqNaHEJAqwPAf7UTtGr/+eJtfBu+dbns42QaIG7DMhzSqtiZY0=
X-Received: by 2002:a17:906:26c3:: with SMTP id u3mr22414125ejc.483.1595291469728;  Mon, 20 Jul 2020 17:31:09 -0700 (PDT)
MIME-Version: 1.0
From: Jupiter <jupiter.hce@gmail.com>
Date: Tue, 21 Jul 2020 10:30:32 +1000
Message-ID: <CAA=hcWS0V8ipsoAEFK3ejdA++Vzi+czth37=ntP4mnt8d=mtRg@mail.gmail.com>
Subject: Small size of core QUIC library to replace TCP for embedded system
To: quic <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/k5a1IgBIOAIH14_eWpSs6XPjC24>
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, 21 Jul 2020 00:31:13 -0000

Hi,

I am looking for a slim backbone core QUIC library to replace TCP stack.

Here are core features currently I am using TCP, I am wondering if
there is a QUIC open source library can be used or to be further
developed to replace following TCP key functionality

- Replace Boost ASIO TCP by QUIC for socket communication between the
device and Cloud services.

- Use (Address)-restricted-cone NAT

- Use TCP TLS

The major issue when I looked at Google and other QUIC source is
because it supports HTTPS, the size is too large, it is not
modularized, Some open source claimed the library can be used by
adding or removing options, the reality is most of the QUIC libraries
are designed based on HTTPS in mind, it is hard to have a clean small
size QUIC core functions above.

I have to admit my knowledge about QUIC is limited, but I am a
programmer, I am keen to participate a modular QUIC open source
development for embedded system, here are options:

- Take an existing QUIC library (C/C++)

- Fork a QUIC Git source to develop a slim C/C++ QUIC for the embedded system.

- Start from scratch based on reference of some QUIC library

Appreciate your advice and suggestions.

Thank you.

Kind regards,

jupiter




--
"A man can fail many times, but he isn't a failure until he begins to
blame somebody else."
-- John Burroughs


From nobody Mon Jul 20 17:53:22 2020
Return-Path: <nibanks@microsoft.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0520B3A123B for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 17:53:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.101
X-Spam-Level: 
X-Spam-Status: No, score=-2.101 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, DKIM_VALID_EF=-0.1, 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=microsoft.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id grUTTmnF5Dgq for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 17:53:19 -0700 (PDT)
Received: from NAM06-BL2-obe.outbound.protection.outlook.com (mail-eopbgr650138.outbound.protection.outlook.com [40.107.65.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 8FC593A1238 for <quic@ietf.org>; Mon, 20 Jul 2020 17:53:19 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=gPvMfB4NvN5a4AClpNDqC08CisitHAAHpIcKsv6yObnl4884p3erqoySM9qzwNNdwYRuQMjdkTYGP6hcomA97gGZ6OXTJjEuWpaAJjRTOy9819H/CAdgd3pWU2r3ge+NdynXsH4dvF+B6oW0O0FCMS9thJNxgQ+6cbUAZzs7BlYesIoNBuirQ9WA8Fr1OgbdWTGeSFXRR1HmYjRh5Ot8pwnkt8tkOfcAT/oYXsikccDw6+T2vg4WHBq00cmOMn+g6Wu1qo6UQoAGmYk5ROFgov5ms8y2UKCul5beHsOWdmTJjn3X3LKqTKyPFg3YXyar1Ps6Pv1oZCwqFUhRB+u1Fg==
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=y9t7GuKF9jSk4vUn8XkvqIjKLlNmSz0DebXh6vXGcKw=; b=V0bj+NORPsKHuVPzTbTpquWG7c9P4oudwoPdusEVLJvN0gLHt3HnP07+xUYzyCgxIkhv6HKBs45JzLrO/vKcW9UfXGbzWmCzKznc4dyJu2T37qM/iELbhFFw0M74U3P5Gpb+PboYav6vUO2F1sqzLqkJY5CCw9rYqVZZxWyXI/ms7FuTK4/xtdbge8ADn91/owaoRdRAv+MI0zIUBrBSZT8m9YlP+wlcNPHx753jSOHz02Vcc/Q1jbHG/hWO89Dl9tvoCXPocMvensCvp2wiybVV7EUYlYCA9ZJtv8QUZWc+qyzP0NMOGAcDbR+ZhnpcsCPqHTamr5lHV5sd/O9vuA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=microsoft.com; dmarc=pass action=none header.from=microsoft.com; dkim=pass header.d=microsoft.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=selector2; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=y9t7GuKF9jSk4vUn8XkvqIjKLlNmSz0DebXh6vXGcKw=; b=OkSZ0JB1PhzLJiX1IU1FbM6RLB800Mfp/jTKmlm/s7i1tfLItyHyzI4s5LlyG2k+dLR4Qrf2vvZ4RtocUSlbAeNYnjNjy1+KI7O8NPAYtz3KmQ070rxzw4Gw4pfypxPShR9BTirY5eSG3gYD2TPg+ZQX9tZMGU6PvRksbXkc0q4=
Received: from CH2PR00MB0764.namprd00.prod.outlook.com (2603:10b6:610:63::8) by CH2PR00MB0853.namprd00.prod.outlook.com (2603:10b6:610:ad::16) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3253.0; Tue, 21 Jul 2020 00:53:18 +0000
Received: from CH2PR00MB0764.namprd00.prod.outlook.com ([fe80::9d6f:a1a9:1d2e:9c32]) by CH2PR00MB0764.namprd00.prod.outlook.com ([fe80::9d6f:a1a9:1d2e:9c32%3]) with mapi id 15.20.3252.000; Tue, 21 Jul 2020 00:53:17 +0000
From: Nick Banks <nibanks@microsoft.com>
To: Jupiter <jupiter.hce@gmail.com>, quic <quic@ietf.org>
Subject: RE: Small size of core QUIC library to replace TCP for embedded system
Thread-Topic: Small size of core QUIC library to replace TCP for embedded system
Thread-Index: AQHWXvZp3uq7gVE72UKmbppHgOE7C6kRNCvA
Date: Tue, 21 Jul 2020 00:53:17 +0000
Message-ID: <CH2PR00MB07647EEBC9795A9BE3801C13B3780@CH2PR00MB0764.namprd00.prod.outlook.com>
References: <CAA=hcWS0V8ipsoAEFK3ejdA++Vzi+czth37=ntP4mnt8d=mtRg@mail.gmail.com>
In-Reply-To: <CAA=hcWS0V8ipsoAEFK3ejdA++Vzi+czth37=ntP4mnt8d=mtRg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
msip_labels: MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Enabled=true; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SetDate=2020-07-21T00:53:13Z;  MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Method=Standard; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_Name=Internal; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_SiteId=72f988bf-86f1-41af-91ab-2d7cd011db47; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ActionId=408994c0-3b45-438a-bcb5-554c1e225ebc; MSIP_Label_f42aa342-8706-4288-bd11-ebb85995028c_ContentBits=0
authentication-results: gmail.com; dkim=none (message not signed) header.d=none;gmail.com; dmarc=none action=none header.from=microsoft.com;
x-originating-ip: [66.235.1.136]
x-ms-publictraffictype: Email
x-ms-office365-filtering-ht: Tenant
x-ms-office365-filtering-correlation-id: 327fc4dd-14e1-416f-ea6c-08d82d107513
x-ms-traffictypediagnostic: CH2PR00MB0853:
x-microsoft-antispam-prvs: <CH2PR00MB0853A6964B5D70BB22FC3A2FB3781@CH2PR00MB0853.namprd00.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:10000;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: TIo0zKrkoQ4I6ifE2c+IIfjBVaSU5Ph9FqxuVi4mWWjOO39pvfZ5tIydIUaJBR55HdVlx0mfhb1ospAqcN/I6MT9JakF+EJgraDL360s36WYvAUmJDr7GK23i0kJSgWOsWmt8CnlnWZ80A0QrOkviqbmyKsRGwZTQj1YpPJi0XZMgPWZc3s/6Wg+WReFljfZfJnL1W8MvGT3COeqBFWSrzfVBCi1qfUjWAmTXuJiO/X2igy6EdPeQWwjEOii9xko42RRU18VYjzApXvBTdwKK3Py90eyFt1I3r2Meudg/tZ+1UQKyTBnKodMckfrIDT4Lumn7niolx4D05VUfCeMwZdThxubKCBSgCZswzS+uueoT0FEay7PeZapgs+GLITR8YVPCfwfFCwsx2C4CoDsdw==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:CH2PR00MB0764.namprd00.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(346002)(39860400002)(366004)(376002)(396003)(136003)(55016002)(8936002)(7696005)(10290500003)(83380400001)(110136005)(53546011)(2906002)(186003)(66446008)(71200400001)(66556008)(64756008)(6506007)(76116006)(66476007)(26005)(66946007)(33656002)(86362001)(316002)(52536014)(478600001)(8990500004)(8676002)(5660300002)(82950400001)(9686003)(82960400001); DIR:OUT; SFP:1102; 
x-ms-exchange-antispam-messagedata: dY0LwyiC8HOQP6L0k7rf968qeUTfUDa/SGWKzSkgwSWbnxMOugye5zwGspcIDAlVu0qmOeNza3Kgp5II/PXJl8xy9HuAMwI74zvfg2uXYtpMVVOMkaKFLYrgWHA1MVvV+e4B1hLvYwivDgs0Q04qnA1SWU/g5uygXShirSiSWBnsj5ETGFKZ3C0+bOeZB7zVlWROpYoT3RxG7LFYgDc6U87R6sMcozJeV3t7lEKWpk1lKI9MzrC7dBi7nJkN6mbMRbfmHEkTGKWk9V3ljjAWGksgbF+4RuzyI05MaGPBPFND9WQEdH90cJodOWV54a9PSQ8EmuaGTbbnUzbq3XbdREfYZTdtZzN4e/Hn+aWoao/YlWCE4ZeXV+LHaXMw3SIzxD6QNUeuezJHE22UCSyml4C9sBnG6h0N/zguCKChZ+SzSFAN0rzQr1v1pUWVyOnr4iziDvt/ZtrPG0uWFuMrV7k0xnt8k5O4xkYaz77h76ohXuDlgx5fhqp74JEdryueyQVV3Ie3mni7tsdrbLR1Ms4QXtOcNpWBUTxQd8R6vfG/n2SVAfc0WQT/DM7R8gZQL10iTS7nYWMHakxZ+0i2NyHpiMnbV5pMa4AB+aM6MeP1vvwWZ/CQEz/XZZQzp2aCp9cyCIyYOmqEf/xJWz7IWA==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: microsoft.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: CH2PR00MB0764.namprd00.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 327fc4dd-14e1-416f-ea6c-08d82d107513
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jul 2020 00:53:17.8975 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 72f988bf-86f1-41af-91ab-2d7cd011db47
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: 7n9zUlr+T+S8dN9KiNRK5a/pSz0REhsO8Bu5l7VgxSuz8HbKiDz7C1DTDNLe6JE6HQOgYRE2qkkyaJ30ir2WCg==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CH2PR00MB0853
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/oQ2HRo3GMNVXasjnBsvX5Zd--Yc>
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, 21 Jul 2020 00:53:21 -0000

SGVsbG8hDQoNCkZlZWwgZnJlZSB0byB0YWtlIGEgbG9vayBhdCBNc1F1aWMgKGh0dHBzOi8vZ2l0
aHViLmNvbS9taWNyb3NvZnQvbXNxdWljKS4gSXQncyB3cml0dGVuIGluIEMgYW5kIGlzIHB1cmVs
eSBhIFFVSUMgaW1wbGVtZW50YXRpb24gKG5vIEhUVFAvMykuIFdlJ3ZlIG5vdCBuZWNlc3Nhcmls
eSB0YXJnZXRlZCBpdCBmb3IgZW1iZWRkZWQgc3lzdGVtcyBhbmQgSSBjYW4ndCB0ZWxsIHlvdSBv
ZmYtaGFuZCBob3cgc21hbGwgdGhlIGxpYnJhcnkgd2lsbCBlbmQgdXAgYmVpbmcgaW4geW91ciBz
Y2VuYXJpby4gSWYgeW91IHRyeSBpdCBvdXQgYW5kIGZpbmQgYW55IHNwZWNpZmljIHByb2JsZW1z
LCBmZWVsIGZyZWUgdG8gb3BlbiBpc3N1ZXMgYW5kIHdlIGNhbiBkaXNjdXNzIGZpeGluZyB0aGVt
Lg0KDQpUaGFua3MsDQotIE5pY2sNCg0KLS0tLS1PcmlnaW5hbCBNZXNzYWdlLS0tLS0NCkZyb206
IFFVSUMgPHF1aWMtYm91bmNlc0BpZXRmLm9yZz4gT24gQmVoYWxmIE9mIEp1cGl0ZXINClNlbnQ6
IE1vbmRheSwgSnVseSAyMCwgMjAyMCA1OjMxIFBNDQpUbzogcXVpYyA8cXVpY0BpZXRmLm9yZz4N
ClN1YmplY3Q6IFNtYWxsIHNpemUgb2YgY29yZSBRVUlDIGxpYnJhcnkgdG8gcmVwbGFjZSBUQ1Ag
Zm9yIGVtYmVkZGVkIHN5c3RlbQ0KDQpIaSwNCg0KSSBhbSBsb29raW5nIGZvciBhIHNsaW0gYmFj
a2JvbmUgY29yZSBRVUlDIGxpYnJhcnkgdG8gcmVwbGFjZSBUQ1Agc3RhY2suDQoNCkhlcmUgYXJl
IGNvcmUgZmVhdHVyZXMgY3VycmVudGx5IEkgYW0gdXNpbmcgVENQLCBJIGFtIHdvbmRlcmluZyBp
ZiB0aGVyZSBpcyBhIFFVSUMgb3BlbiBzb3VyY2UgbGlicmFyeSBjYW4gYmUgdXNlZCBvciB0byBi
ZSBmdXJ0aGVyIGRldmVsb3BlZCB0byByZXBsYWNlIGZvbGxvd2luZyBUQ1Aga2V5IGZ1bmN0aW9u
YWxpdHkNCg0KLSBSZXBsYWNlIEJvb3N0IEFTSU8gVENQIGJ5IFFVSUMgZm9yIHNvY2tldCBjb21t
dW5pY2F0aW9uIGJldHdlZW4gdGhlIGRldmljZSBhbmQgQ2xvdWQgc2VydmljZXMuDQoNCi0gVXNl
IChBZGRyZXNzKS1yZXN0cmljdGVkLWNvbmUgTkFUDQoNCi0gVXNlIFRDUCBUTFMNCg0KVGhlIG1h
am9yIGlzc3VlIHdoZW4gSSBsb29rZWQgYXQgR29vZ2xlIGFuZCBvdGhlciBRVUlDIHNvdXJjZSBp
cyBiZWNhdXNlIGl0IHN1cHBvcnRzIEhUVFBTLCB0aGUgc2l6ZSBpcyB0b28gbGFyZ2UsIGl0IGlz
IG5vdCBtb2R1bGFyaXplZCwgU29tZSBvcGVuIHNvdXJjZSBjbGFpbWVkIHRoZSBsaWJyYXJ5IGNh
biBiZSB1c2VkIGJ5IGFkZGluZyBvciByZW1vdmluZyBvcHRpb25zLCB0aGUgcmVhbGl0eSBpcyBt
b3N0IG9mIHRoZSBRVUlDIGxpYnJhcmllcyBhcmUgZGVzaWduZWQgYmFzZWQgb24gSFRUUFMgaW4g
bWluZCwgaXQgaXMgaGFyZCB0byBoYXZlIGEgY2xlYW4gc21hbGwgc2l6ZSBRVUlDIGNvcmUgZnVu
Y3Rpb25zIGFib3ZlLg0KDQpJIGhhdmUgdG8gYWRtaXQgbXkga25vd2xlZGdlIGFib3V0IFFVSUMg
aXMgbGltaXRlZCwgYnV0IEkgYW0gYSBwcm9ncmFtbWVyLCBJIGFtIGtlZW4gdG8gcGFydGljaXBh
dGUgYSBtb2R1bGFyIFFVSUMgb3BlbiBzb3VyY2UgZGV2ZWxvcG1lbnQgZm9yIGVtYmVkZGVkIHN5
c3RlbSwgaGVyZSBhcmUgb3B0aW9uczoNCg0KLSBUYWtlIGFuIGV4aXN0aW5nIFFVSUMgbGlicmFy
eSAoQy9DKyspDQoNCi0gRm9yayBhIFFVSUMgR2l0IHNvdXJjZSB0byBkZXZlbG9wIGEgc2xpbSBD
L0MrKyBRVUlDIGZvciB0aGUgZW1iZWRkZWQgc3lzdGVtLg0KDQotIFN0YXJ0IGZyb20gc2NyYXRj
aCBiYXNlZCBvbiByZWZlcmVuY2Ugb2Ygc29tZSBRVUlDIGxpYnJhcnkNCg0KQXBwcmVjaWF0ZSB5
b3VyIGFkdmljZSBhbmQgc3VnZ2VzdGlvbnMuDQoNClRoYW5rIHlvdS4NCg0KS2luZCByZWdhcmRz
LA0KDQpqdXBpdGVyDQoNCg0KDQoNCi0tDQoiQSBtYW4gY2FuIGZhaWwgbWFueSB0aW1lcywgYnV0
IGhlIGlzbid0IGEgZmFpbHVyZSB1bnRpbCBoZSBiZWdpbnMgdG8gYmxhbWUgc29tZWJvZHkgZWxz
ZS4iDQotLSBKb2huIEJ1cnJvdWdocw0KDQo=


From nobody Mon Jul 20 19:07:18 2020
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 EB55B3A12D0 for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 19:07:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-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 Szd7kv7yMFBW for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 19:07:15 -0700 (PDT)
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 EB6393A12CE for <quic@ietf.org>; Mon, 20 Jul 2020 19:07:14 -0700 (PDT)
Received: by mail-lj1-x230.google.com with SMTP id s9so22323703ljm.11 for <quic@ietf.org>; Mon, 20 Jul 2020 19:07:14 -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=6YkmfTYM8woM2cWOKs2X5y1C9YaEe1hs8UqyT3FbtJ0=; b=kh/aLikqT5rV27Zy311gGjBooKRQKMPH1fvvkqyzI5IcOzIMA9WzAMNxCDzbqoAcwo X55GhZuUCVm880V4Xr9U2U5CCRrzir+ATaStEDDD7wAtc5+pAN7icLg1nb0eAsoLwOmy paqkSAIxndr+yb3GnuHn0njVaElS2Syt9A+1dkcSSYZbeS9oN3aF4fsmbXzrxzAH2ell 0WtspBz4Qlla5gCr4r6tClC5Im2Pvdatxi64fiySUb1Nw6bIFL96He8GPzSQTrKfqAtT jYJ+6Njt179N/c6mOedPd1JuWKA6bwG7dPhqub4Xluw5m1KCqUr+jzeN7cesRqaq3v5z fbYw==
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=6YkmfTYM8woM2cWOKs2X5y1C9YaEe1hs8UqyT3FbtJ0=; b=UP/Po42iT5pJ75PF/92s3KbxuGXf9SJJgKPdzzWV/arJHgzA/dUNyK3JOCjXDO/Cr7 X2aJRfG27QiPc0jFtXLH3Jd/KzRVt5Uz2S/k5BC06/4uMktpZwrsL3NUpDdAEKLcOZ9m AfqocP8buDO2QFkDGhL5nLfW+8SkpBwY/xST2RDnv7TB+DgvPWC3wBcA2OsIU9u74Sjz cktJmpzkHgSMRYRSHC1immridqT9lvssbj78g7CyT0KbU4apqNpoE1W8G70LJfhmbEC0 moP06DitteVbhZ+OQIpJ3rxh5Aw41t0WscWqcBTfwaRRfpBGYPlXMhmRPw0O3AsTmEk/ rUmw==
X-Gm-Message-State: AOAM531vEdthsiZ1lY+7W4kZMlCgehtVU+prNZyD2BskAd+BzgMX1O5x Rkr2Bg193MnxV6enesW1y0AHQKpqRrTU3DekRofj5w==
X-Google-Smtp-Source: ABdhPJykvhJuTHT6a6crwKkqnycnOx8bIGjRh+39orP7stmnUrferMHozkYX/SfhCYlO/ppEkfrYuqtTNxkQ+kyBS2I=
X-Received: by 2002:a2e:8804:: with SMTP id x4mr11711367ljh.56.1595297232792;  Mon, 20 Jul 2020 19:07:12 -0700 (PDT)
MIME-Version: 1.0
References: <CACpbDcctB0nX2yTxHQEs6UcUCTH0WdfiNAPfpRKe3oH-0aYZYA@mail.gmail.com> <28d46380-620a-4448-b471-403048e0117e@www.fastmail.com>
In-Reply-To: <28d46380-620a-4448-b471-403048e0117e@www.fastmail.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Mon, 20 Jul 2020 19:07:01 -0700
Message-ID: <CACpbDcf0i0fEnD3VeLx=dW8hZNf1esDPy8P6v3UD+Y9Gh6b2Dg@mail.gmail.com>
Subject: Re: Handshake processing delays and impact on recovery
To: Martin Thomson <mt@lowentropy.net>
Cc: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000df328d05aaea149d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/qqAP9FZnoctFLGNR4F30Lp-h010>
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, 21 Jul 2020 02:07:17 -0000

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

Thanks, Martin.


> > We think this holds up, but we'd like to get this under everyone's
> > eyes, to ensure that the discussion isn't missing subtle deadlock
> > issues.
>
> I have satisfied myself that this is OK.  The only 1-RTT (or 0-RTT) packet
> content we depend on to get to "handshake confirmed" is the HANDSHAKE_DONE
> frame.  As this is sent by the server after confirming the handshake, it
> will be sent on PTO as normal.  Were this not the case, this would be
> disastrous as we couldn't rely on this getting through.
>

Yes, this is perhaps the most delicate part of this change. As you say, at
that point, the server is at "handshake confirmed", and will therefore arm
the PTO timer for the HANDSHAKE_DONE frame.

One way to think about this would be that the server cannot read 1-RTT
packets (including ACK frames) until it has read the CFIN. The client
retransmits this on a PTO, since this is in Handshake space and not in
Application space, until it gets an ACK for it or receives HANDSHAKE_DONE.
The server's Application PTO does not do any good until it has received the
CFIN. So the client drives the machinery at this point.

One receiving the CFIN, the server moves to "handshake confirmed" and can
now arm a PTO for the HANDSHAKE_DONE that it sends next. So now, the server
drives the machinery. Once HANDSHAKE_DONE is received by the client, it is
free to set PTO on subsequent 1-RTT packets it sends.


> > - endpoints ignore max_ack_delay for acknowledgements of packets that
> > were sent prior to handshake confirmation. Those are the ones that
> > might have been buffered at the peer until keys were ready.
>
> For this, endpoints need to retain an additional value: the highest packet
> number that was sent prior to confirmation (or the lowest packet number
> sent after confirmation).  It's a little annoying to have to do that, but
> it seems necessary.
>

Agreed.

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

<div dir=3D"ltr"><div dir=3D"ltr">Thanks, Martin.</div><div class=3D"gmail_=
quote"><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">&=
gt; We think this holds up, but we&#39;d like to get this under everyone&#3=
9;s <br>
&gt; eyes, to ensure that the discussion isn&#39;t missing subtle deadlock =
<br>
&gt; issues.<br>
<br>
I have satisfied myself that this is OK.=C2=A0 The only 1-RTT (or 0-RTT) pa=
cket content we depend on to get to &quot;handshake confirmed&quot; is the =
HANDSHAKE_DONE frame.=C2=A0 As this is sent by the server after confirming =
the handshake, it will be sent on PTO as normal.=C2=A0 Were this not the ca=
se, this would be disastrous as we couldn&#39;t rely on this getting throug=
h.<br></blockquote><div><br></div><div>Yes, this is perhaps the most delica=
te part of this change. As you say, at that point, the server is at &quot;h=
andshake confirmed&quot;, and will therefore arm the PTO timer for the HAND=
SHAKE_DONE frame.<br><br></div><div>One way to think about this would be th=
at the server cannot read 1-RTT packets (including ACK frames) until it has=
 read the CFIN. The client retransmits this on a PTO, since this is in Hand=
shake space and not in Application space, until it gets an ACK for it or re=
ceives HANDSHAKE_DONE. The server&#39;s Application PTO does not do any goo=
d=C2=A0until it has received the CFIN. So the client drives the machinery a=
t this point.</div><div><br></div><div>One receiving the CFIN, the server m=
oves to &quot;handshake confirmed&quot; and can now arm a PTO for the HANDS=
HAKE_DONE that it sends next. So now, the server drives the machinery. Once=
 HANDSHAKE_DONE is received by the client, it is free to set PTO on subsequ=
ent 1-RTT packets it sends.</div><div>=C2=A0<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">
&gt; - endpoints ignore max_ack_delay for acknowledgements of packets that =
<br>
&gt; were sent prior to handshake confirmation. Those are the ones that <br=
>
&gt; might have been buffered at the peer until keys were ready.<br>
<br>
For this, endpoints need to retain an additional value: the highest packet =
number that was sent prior to confirmation (or the lowest packet number sen=
t after confirmation).=C2=A0 It&#39;s a little annoying to have to do that,=
 but it seems necessary.<br></blockquote><div><br></div><div>Agreed.</div><=
div>=C2=A0</div></div></div>

--000000000000df328d05aaea149d--


From nobody Mon Jul 20 20:11:39 2020
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 269E43A1342 for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 20:11:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 bntB4NpLhzpR for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 20:11:36 -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 3638B3A1340 for <quic@ietf.org>; Mon, 20 Jul 2020 20:11:36 -0700 (PDT)
Received: by mail-lj1-x232.google.com with SMTP id z24so22421512ljn.8 for <quic@ietf.org>; Mon, 20 Jul 2020 20:11:36 -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=RIEunUDGVrhfLF71csWAS6AFrju4Ot2QdCHuZ8gut54=; b=XB3H8JaLO6cUxp/42VJnHxa37lymDY57XDsoojT/Ypa7krdog20gQCRAKpOR0cfkIJ H6qlTif0scBoWv1VpgFFiuk18u7pHCLio9sEU96sigdwfPsNgYHD7IpreN0fybcY4tWb s/wF3WbenGEFdrbOe5bdFprJZQUvXuMeleKZKhcuueX6w+hNu/+v0z+QPOyzYKn1mbdG 9vpgONwHMnnmaj65/hlD2ykcBlPq7qilov8xqrn8bQJ8gglDynVW5GSsN07gkr/WHuNB h06cHoUgXw8vmol1wMz7zSm6QzyEbvvqLpLmOXIHwU4ygRBUfHYMx2ddG8H8lb9rmIhL x2hQ==
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=RIEunUDGVrhfLF71csWAS6AFrju4Ot2QdCHuZ8gut54=; b=kSIoLwf4/ZS3VcrsuNdlmG/Q/1NpAN/kPk+rf+koDnZNVBgK/bwmu3Z2Z95PjTc5eb IUxeXh18HsWsriqjxwqzVsZFXluokZ3EWVS0F9q7ZHgSWe8fSaZA8xs6FrbBkGUnorhJ tjpevVKs0BUIrKja1521My3uULdAit4o4U6o9aXyvwBdgXWDADbifaUDqPD6pp2xk4jZ pm6hG4t9BsBwverBqsclydaAH5vYmU1dv8vHx+WoxazijRDdTec8hHMoAbRqBPMDmOsw RVWoR4Jcqoh1KrehGHsca32ZRYWCQNaim+WC09XCFhYabgaF7mECOpiSmY8nKlIJCNzd /S9w==
X-Gm-Message-State: AOAM532bxtJuiX56F4B+SitBlEv+Mhl9yuZJK0WPEVwXMkpxB8rnm6/o dvHwvrGdIXv93KYebPUXwDjmIRrjdbUhaRQMK6sUcLhG
X-Google-Smtp-Source: ABdhPJzk42whmdfYfJ4V/X01JDhHaGdabY+IkNNakxOhgV7URB7J00cG/UxbzyFQNn+mDvKFrzcqSkVrsU36YK2XxpI=
X-Received: by 2002:a2e:808a:: with SMTP id i10mr10714668ljg.400.1595301094319;  Mon, 20 Jul 2020 20:11:34 -0700 (PDT)
MIME-Version: 1.0
References: <CAA=hcWS0V8ipsoAEFK3ejdA++Vzi+czth37=ntP4mnt8d=mtRg@mail.gmail.com> <CH2PR00MB07647EEBC9795A9BE3801C13B3780@CH2PR00MB0764.namprd00.prod.outlook.com>
In-Reply-To: <CH2PR00MB07647EEBC9795A9BE3801C13B3780@CH2PR00MB0764.namprd00.prod.outlook.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Mon, 20 Jul 2020 20:11:23 -0700
Message-ID: <CACpbDceOzxMY1JOJc75i6ORjbDMq-qRPyMZa+cWUEP2gNzvZLQ@mail.gmail.com>
Subject: Re: Small size of core QUIC library to replace TCP for embedded system
To: Nick Banks <nibanks=40microsoft.com@dmarc.ietf.org>
Cc: Jupiter <jupiter.hce@gmail.com>, quic <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000009688305aaeafbda"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/VYJXjBXbqXEY43LCdPyTnOij38M>
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, 21 Jul 2020 03:11:38 -0000

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

Hi Jupiter,

You might consider the various implementations listed at
https://github.com/quicwg/base-drafts/wiki/Implementations. All the
implementers are on this list, so you should be able to reach them here.

- jana

On Mon, Jul 20, 2020 at 5:53 PM Nick Banks <nibanks=
40microsoft.com@dmarc.ietf.org> wrote:

> Hello!
>
> Feel free to take a look at MsQuic (https://github.com/microsoft/msquic).
> It's written in C and is purely a QUIC implementation (no HTTP/3). We've
> not necessarily targeted it for embedded systems and I can't tell you
> off-hand how small the library will end up being in your scenario. If you
> try it out and find any specific problems, feel free to open issues and we
> can discuss fixing them.
>
> Thanks,
> - Nick
>
> -----Original Message-----
> From: QUIC <quic-bounces@ietf.org> On Behalf Of Jupiter
> Sent: Monday, July 20, 2020 5:31 PM
> To: quic <quic@ietf.org>
> Subject: Small size of core QUIC library to replace TCP for embedded system
>
> Hi,
>
> I am looking for a slim backbone core QUIC library to replace TCP stack.
>
> Here are core features currently I am using TCP, I am wondering if there
> is a QUIC open source library can be used or to be further developed to
> replace following TCP key functionality
>
> - Replace Boost ASIO TCP by QUIC for socket communication between the
> device and Cloud services.
>
> - Use (Address)-restricted-cone NAT
>
> - Use TCP TLS
>
> The major issue when I looked at Google and other QUIC source is because
> it supports HTTPS, the size is too large, it is not modularized, Some open
> source claimed the library can be used by adding or removing options, the
> reality is most of the QUIC libraries are designed based on HTTPS in mind,
> it is hard to have a clean small size QUIC core functions above.
>
> I have to admit my knowledge about QUIC is limited, but I am a programmer,
> I am keen to participate a modular QUIC open source development for
> embedded system, here are options:
>
> - Take an existing QUIC library (C/C++)
>
> - Fork a QUIC Git source to develop a slim C/C++ QUIC for the embedded
> system.
>
> - Start from scratch based on reference of some QUIC library
>
> Appreciate your advice and suggestions.
>
> Thank you.
>
> Kind regards,
>
> jupiter
>
>
>
>
> --
> "A man can fail many times, but he isn't a failure until he begins to
> blame somebody else."
> -- John Burroughs
>
>

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

<div dir=3D"ltr">Hi Jupiter,<div><br></div><div>You might consider the vari=
ous implementations listed at=C2=A0<a href=3D"https://github.com/quicwg/bas=
e-drafts/wiki/Implementations">https://github.com/quicwg/base-drafts/wiki/I=
mplementations</a>. All the implementers are on this list, so you should be=
 able to reach them here.</div><div><br></div><div>- jana</div></div><br><d=
iv class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jul =
20, 2020 at 5:53 PM Nick Banks &lt;nibanks=3D<a href=3D"mailto:40microsoft.=
com@dmarc.ietf.org">40microsoft.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">Hello!<br>
<br>
Feel free to take a look at MsQuic (<a href=3D"https://github.com/microsoft=
/msquic" rel=3D"noreferrer" target=3D"_blank">https://github.com/microsoft/=
msquic</a>). It&#39;s written in C and is purely a QUIC implementation (no =
HTTP/3). We&#39;ve not necessarily targeted it for embedded systems and I c=
an&#39;t tell you off-hand how small the library will end up being in your =
scenario. If you try it out and find any specific problems, feel free to op=
en issues and we can discuss fixing them.<br>
<br>
Thanks,<br>
- Nick<br>
<br>
-----Original Message-----<br>
From: QUIC &lt;<a href=3D"mailto:quic-bounces@ietf.org" target=3D"_blank">q=
uic-bounces@ietf.org</a>&gt; On Behalf Of Jupiter<br>
Sent: Monday, July 20, 2020 5:31 PM<br>
To: quic &lt;<a href=3D"mailto:quic@ietf.org" target=3D"_blank">quic@ietf.o=
rg</a>&gt;<br>
Subject: Small size of core QUIC library to replace TCP for embedded system=
<br>
<br>
Hi,<br>
<br>
I am looking for a slim backbone core QUIC library to replace TCP stack.<br=
>
<br>
Here are core features currently I am using TCP, I am wondering if there is=
 a QUIC open source library can be used or to be further developed to repla=
ce following TCP key functionality<br>
<br>
- Replace Boost ASIO TCP by QUIC for socket communication between the devic=
e and Cloud services.<br>
<br>
- Use (Address)-restricted-cone NAT<br>
<br>
- Use TCP TLS<br>
<br>
The major issue when I looked at Google and other QUIC source is because it=
 supports HTTPS, the size is too large, it is not modularized, Some open so=
urce claimed the library can be used by adding or removing options, the rea=
lity is most of the QUIC libraries are designed based on HTTPS in mind, it =
is hard to have a clean small size QUIC core functions above.<br>
<br>
I have to admit my knowledge about QUIC is limited, but I am a programmer, =
I am keen to participate a modular QUIC open source development for embedde=
d system, here are options:<br>
<br>
- Take an existing QUIC library (C/C++)<br>
<br>
- Fork a QUIC Git source to develop a slim C/C++ QUIC for the embedded syst=
em.<br>
<br>
- Start from scratch based on reference of some QUIC library<br>
<br>
Appreciate your advice and suggestions.<br>
<br>
Thank you.<br>
<br>
Kind regards,<br>
<br>
jupiter<br>
<br>
<br>
<br>
<br>
--<br>
&quot;A man can fail many times, but he isn&#39;t a failure until he begins=
 to blame somebody else.&quot;<br>
-- John Burroughs<br>
<br>
</blockquote></div>

--00000000000009688305aaeafbda--


From nobody Mon Jul 20 22:08:03 2020
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 8DE603A127F for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 22:08:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.902
X-Spam-Level: **
X-Spam-Status: No, score=2.902 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, GB_SUMOF=5, HTML_MESSAGE=0.001, 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 eBSi0QXpEcrp for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 22:08:00 -0700 (PDT)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (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 CEA6C3A106D for <quic@ietf.org>; Mon, 20 Jul 2020 22:07:59 -0700 (PDT)
Received: by mail-lf1-x12b.google.com with SMTP id i80so10939066lfi.13 for <quic@ietf.org>; Mon, 20 Jul 2020 22:07:59 -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=qUJtU8syxmkOU7fhR38aC3fFFG/XF9z9OBoTjaGMxBo=; b=WB6fF6uYatbwJYXdnBdGUMf6BAscQD2ZRiuDaNk53mLcszDDUWnj1xjnu5f544pQU+ 0N8DmT6lRhUpTPMl0q90YP2iJlwLgk2Kb62Gbipu/xbOkxR8AN1yITdFO2Vz9d0HMsXU WfiAUHunY1mV0DAMNXhxPCjqVkm790dGEl+FyA1jMsVfqGl1421yCuFVwMxfSBBkSdOb tSMycWC6NiEHqN6LWihFF/FmSDRF9qhwCYr9birir+G9WW37SNTAwbcIAde+PzWtZIP2 JPwO8/kcPdFCGqW+M+V2y79tY1PBdZLfxaBLA9XQkAo2zAl3BeM35DgSdY2hY3eCtkPs iMgQ==
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=qUJtU8syxmkOU7fhR38aC3fFFG/XF9z9OBoTjaGMxBo=; b=tuMRQ8Zp+1qb/N1NIVHGr6Y6a67eeU2/BYxg8V9C4pa/cBFun/KQW3yRm6RXp6vcrm DFuGXqWr9HvXz0bhxrMfnImOjRRq3FlOFQ0xanBqTMttCNths0juzAPzJs3ibVPUpAdw HsaiJSaAPBXK0kz821E17eKvuCVe9gFjtLx1TvYQAMhOt3QekBamiLzRfWWZntcrzkBs Fn+iEXxFkaU90iA/4IZ1mukxKwSAiw7vjzTWA4AQoPa3F0rG1EX19wWscoG1eNH7aG7U wNprcohxitT8PsebkCpT8SykZjYXg/YLjMKxuoa7qOb/+UAtbWZvSg2HZmU25PxYrYTj IRxA==
X-Gm-Message-State: AOAM532XMUykAzB4vVcARQ1UozThc0ykMoXr2e2nRfIeuIOiHXduJIOd +wXplHuYyyusbBBJStt7cyfD2HQCStSZvbRpWUo=
X-Google-Smtp-Source: ABdhPJw/xA/fE49lqqHKkn2LTqaK4JchvZ7yWpln+6vZ8SCeXlDnJ5+VL/mG0wfmaaEAWOEZfgqpWKIXCBK38L/8TEQ=
X-Received: by 2002:a05:6512:3a5:: with SMTP id v5mr11499258lfp.138.1595308077651;  Mon, 20 Jul 2020 22:07:57 -0700 (PDT)
MIME-Version: 1.0
References: <CACpbDcctB0nX2yTxHQEs6UcUCTH0WdfiNAPfpRKe3oH-0aYZYA@mail.gmail.com> <28d46380-620a-4448-b471-403048e0117e@www.fastmail.com> <CACpbDcf0i0fEnD3VeLx=dW8hZNf1esDPy8P6v3UD+Y9Gh6b2Dg@mail.gmail.com>
In-Reply-To: <CACpbDcf0i0fEnD3VeLx=dW8hZNf1esDPy8P6v3UD+Y9Gh6b2Dg@mail.gmail.com>
From: Marten Seemann <martenseemann@gmail.com>
Date: Tue, 21 Jul 2020 12:07:45 +0700
Message-ID: <CAOYVs2rw4txSQw+dMkMKAw_E_REpXeUfrHj4-nvkhQOR=509Og@mail.gmail.com>
Subject: Re: Handshake processing delays and impact on recovery
To: Jana Iyengar <jri.ietf@gmail.com>
Cc: Martin Thomson <mt@lowentropy.net>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000469c4c05aaec9bab"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/-3_PEaE54KSWRbkbDhFOukSaOZI>
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, 21 Jul 2020 05:08:02 -0000

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

> To solve the second problem, the proposal is to use ack_delay as reported
by the endpoint that buffers the data appropriately. ack_delay is the
amount of the time the information (regardless of that being the packet
itself or the acknowledgement) being buffered intentionally. For this, we
need the following:
> - endpoints MUST report an ack_delay that is the sum of the controlled
delay (i.e. the duration of the data and the ack being buffered)
> - endpoints ignore max_ack_delay for acknowledgements of packets that
were sent prior to handshake confirmation. Those are the ones that might
have been buffered at the peer until keys were ready.

It took me a while to convince myself that this is ok. The danger I saw
here is that an adversarial endpoint might misreport the ack_delay to trick
the peer into coming up with an RTT estimate that's significantly shorter
than the actual RTT.
The reason why this attack doesn't work is that the only variables that
make use of the ack_delay are smoothed_rtt and rttvar. Specifically,
latest_rtt is just the difference between sending the packet and receipt of
the acknowledgment, and min_rtt is the minimum value of all latest_rtt
values measured. The ack_delay is only applied to the measurement of
smoothed_rtt if it doesn't lower the value below min_rtt.
Consequently, this means that a server reporting an ack_delay in the ACK
for the ClientHello won't have any effect.


On Tue, Jul 21, 2020 at 9:07 AM Jana Iyengar <jri.ietf@gmail.com> wrote:

> Thanks, Martin.
>
>
>> > We think this holds up, but we'd like to get this under everyone's
>> > eyes, to ensure that the discussion isn't missing subtle deadlock
>> > issues.
>>
>> I have satisfied myself that this is OK.  The only 1-RTT (or 0-RTT)
>> packet content we depend on to get to "handshake confirmed" is the
>> HANDSHAKE_DONE frame.  As this is sent by the server after confirming the
>> handshake, it will be sent on PTO as normal.  Were this not the case, this
>> would be disastrous as we couldn't rely on this getting through.
>>
>
> Yes, this is perhaps the most delicate part of this change. As you say, at
> that point, the server is at "handshake confirmed", and will therefore arm
> the PTO timer for the HANDSHAKE_DONE frame.
>
> One way to think about this would be that the server cannot read 1-RTT
> packets (including ACK frames) until it has read the CFIN. The client
> retransmits this on a PTO, since this is in Handshake space and not in
> Application space, until it gets an ACK for it or receives HANDSHAKE_DONE.
> The server's Application PTO does not do any good until it has received the
> CFIN. So the client drives the machinery at this point.
>
> One receiving the CFIN, the server moves to "handshake confirmed" and can
> now arm a PTO for the HANDSHAKE_DONE that it sends next. So now, the server
> drives the machinery. Once HANDSHAKE_DONE is received by the client, it is
> free to set PTO on subsequent 1-RTT packets it sends.
>
>
>> > - endpoints ignore max_ack_delay for acknowledgements of packets that
>> > were sent prior to handshake confirmation. Those are the ones that
>> > might have been buffered at the peer until keys were ready.
>>
>> For this, endpoints need to retain an additional value: the highest
>> packet number that was sent prior to confirmation (or the lowest packet
>> number sent after confirmation).  It's a little annoying to have to do
>> that, but it seems necessary.
>>
>
> Agreed.
>
>

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

<div dir=3D"ltr">&gt; To solve the second problem, the proposal is to use a=
ck_delay as reported by the endpoint that buffers the data appropriately. a=
ck_delay is the amount of the time the information (regardless of that bein=
g the packet itself or the acknowledgement) being buffered intentionally. F=
or this, we need the following:<br>&gt; - endpoints MUST report an ack_dela=
y that is the sum of the controlled delay (i.e. the duration of the data an=
d the ack being buffered)<br><div>&gt; - endpoints ignore max_ack_delay for=
 acknowledgements of packets that were sent prior to handshake confirmation=
. Those are the ones that might have been buffered at the peer until keys w=
ere ready.</div><div><br></div><div>It took me a while to convince myself t=
hat this is ok. The danger I saw here is that an adversarial endpoint might=
 misreport the ack_delay to trick the peer into coming up with an RTT estim=
ate that&#39;s significantly shorter than the actual RTT.</div><div>The rea=
son why this attack doesn&#39;t work is that the only variables that make u=
se of the ack_delay are smoothed_rtt and rttvar. Specifically, latest_rtt i=
s just the difference between sending the packet and receipt of the acknowl=
edgment, and min_rtt is the minimum value of all latest_rtt values measured=
. The ack_delay is only applied to the measurement of smoothed_rtt if it do=
esn&#39;t lower the value below min_rtt.</div><div>Consequently, this means=
 that a server reporting an ack_delay in the ACK for the ClientHello won&#3=
9;t have any effect.<br></div><div><br></div></div><br><div class=3D"gmail_=
quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jul 21, 2020 at 9:07 A=
M Jana Iyengar &lt;<a href=3D"mailto:jri.ietf@gmail.com">jri.ietf@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"><div dir=3D"ltr">Thanks, Martin.</div><div class=3D"gmail_=
quote"><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">&=
gt; We think this holds up, but we&#39;d like to get this under everyone&#3=
9;s <br>
&gt; eyes, to ensure that the discussion isn&#39;t missing subtle deadlock =
<br>
&gt; issues.<br>
<br>
I have satisfied myself that this is OK.=C2=A0 The only 1-RTT (or 0-RTT) pa=
cket content we depend on to get to &quot;handshake confirmed&quot; is the =
HANDSHAKE_DONE frame.=C2=A0 As this is sent by the server after confirming =
the handshake, it will be sent on PTO as normal.=C2=A0 Were this not the ca=
se, this would be disastrous as we couldn&#39;t rely on this getting throug=
h.<br></blockquote><div><br></div><div>Yes, this is perhaps the most delica=
te part of this change. As you say, at that point, the server is at &quot;h=
andshake confirmed&quot;, and will therefore arm the PTO timer for the HAND=
SHAKE_DONE frame.<br><br></div><div>One way to think about this would be th=
at the server cannot read 1-RTT packets (including ACK frames) until it has=
 read the CFIN. The client retransmits this on a PTO, since this is in Hand=
shake space and not in Application space, until it gets an ACK for it or re=
ceives HANDSHAKE_DONE. The server&#39;s Application PTO does not do any goo=
d=C2=A0until it has received the CFIN. So the client drives the machinery a=
t this point.</div><div><br></div><div>One receiving the CFIN, the server m=
oves to &quot;handshake confirmed&quot; and can now arm a PTO for the HANDS=
HAKE_DONE that it sends next. So now, the server drives the machinery. Once=
 HANDSHAKE_DONE is received by the client, it is free to set PTO on subsequ=
ent 1-RTT packets it sends.</div><div>=C2=A0<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">
&gt; - endpoints ignore max_ack_delay for acknowledgements of packets that =
<br>
&gt; were sent prior to handshake confirmation. Those are the ones that <br=
>
&gt; might have been buffered at the peer until keys were ready.<br>
<br>
For this, endpoints need to retain an additional value: the highest packet =
number that was sent prior to confirmation (or the lowest packet number sen=
t after confirmation).=C2=A0 It&#39;s a little annoying to have to do that,=
 but it seems necessary.<br></blockquote><div><br></div><div>Agreed.</div><=
div>=C2=A0</div></div></div>
</blockquote></div>

--000000000000469c4c05aaec9bab--


From nobody Mon Jul 20 23:40:10 2020
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 C79D23A1446 for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 23:40:08 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=eggert.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 T18QZ_1VOl1S for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 23:40:07 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:0:35:211:32ff:fe22:186f]) (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 6179C3A0EE1 for <quic@ietf.org>; Mon, 20 Jul 2020 23:40:07 -0700 (PDT)
Received: from [IPv6:2a00:ac00:0:35:e9f7:316e:5e24:9364] (unknown [IPv6:2a00:ac00:0:35:e9f7:316e:5e24:9364]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 045B065080D; Tue, 21 Jul 2020 09:39:58 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1595313599; bh=Xax684b63ITeM5iauvGOEn2LJutwPHH+lcn+EahQfLE=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=I+ZnZ+Fz2yikP04FiXCqzmXg6BM7dz4Ncp3M0DTRMj9DC69Jbf4ydBFZAeUu3p+il 5Zxuhz9I6DdPfzSPdQmZAbtow/m1M3K0E1ux5+xNoGizlrxjuuz30xsS7WhKYFG+A0 X3A9wNy+3RaKVwHglqyJbTj8iS38Q8qjpAwRew7A=
From: Lars Eggert <lars@eggert.org>
Message-Id: <1C514B96-9AAA-40B3-93EC-3DCDFAF72A93@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_4A619E0A-CA0A-4D54-96F0-1236C58234C4"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: Re: Small size of core QUIC library to replace TCP for embedded system
Date: Tue, 21 Jul 2020 09:39:58 +0300
In-Reply-To: <CAA=hcWS0V8ipsoAEFK3ejdA++Vzi+czth37=ntP4mnt8d=mtRg@mail.gmail.com>
Cc: quic <quic@ietf.org>
To: Jupiter <jupiter.hce@gmail.com>
References: <CAA=hcWS0V8ipsoAEFK3ejdA++Vzi+czth37=ntP4mnt8d=mtRg@mail.gmail.com>
X-MailScanner-ID: 045B065080D.A1FF7
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Q-XNnJfONBgpOnF3bdx7tQ_JOJ0>
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, 21 Jul 2020 06:40:09 -0000

--Apple-Mail=_4A619E0A-CA0A-4D54-96F0-1236C58234C4
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 2020-7-21, at 3:30, Jupiter <jupiter.hce@gmail.com> wrote:
> I am looking for a slim backbone core QUIC library to replace TCP =
stack.

you don't really say what type of device you are targeting, so it's a =
bit difficult to respond in detail.

But I did port my quant QUIC stack (https://github.com/NTAP/quant) to =
Particle DeviceOS and RIOT, and ran some client-only measurements on a =
Particle Argon and an ESP32. There's a writeup in =
https://eggert.org/papers/2020-ndss-quic-iot.pdf, slides in =
https://github.com/t2trg/2020-ietf107/blob/master/slides/22-towards-securi=
ng-the-internet-of-things-with-quic.pdf. (There was also a recording of =
the T2TRG talk, but it doesn't seem to be uploaded to GitHub yet.)

It should be reasonably straightforward to add a packet I/O backend for =
other IoT platforms to warpcore, (https://github.com/NTAP/warpcore) =
which is quant's packet I/O library. I had been considering Zephyr =
support, but ran out of time.

Note: quant is a research effort and not meant for production.

Lars

--Apple-Mail=_4A619E0A-CA0A-4D54-96F0-1236C58234C4
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAl8Wjb4ACgkQVLXDCb9w
wVcZMxAAzGsTlMldeTON9JVdn5ryjXhMF/P50I87LY+g02gdhJH8c9VG03ZUFjK6
27ZZvCq6/H44AbXzXJBMKRTzKi4L0Hvv4vPdwBv7T5d132dORQyElq5XwTOlNnmT
F7kr03bMWJcKtqTIj0BnkerUxEciuYAjj2lozAyokCvTTc9wlXfZCg7xSlR/alXE
62RnmdO8V4XDV4OlXBLSASDU6IzrWteJ5FiXT3nc0gc8UNXBGpN53RUDnpK1qCwL
y7/IPPanB6GRwHe1tFrEDPO/KZZ+ct1KG59sZwcKkU37iVbpO5Z/0iuCFzqXfHyz
Xx4mf/ulvgXeCacR/pHl2/xopK/q6Q51/lPaWke8Ly7hYEAtN+hHiQ1BYEoqxL0k
q6WBccxd6G163GVunnZqaObKm3/Nv5GKsHHdrdXqldLjTxz3bYmTHLVWlNQCpNKj
Aa+RVOkJikG/fGZYQzdgq+01q8HeAAnObo0pAz3lTLOIoZ2mnioBvuqyltU4O8SR
G2eKLajOUbw+PTXxiKuUJc33W8uNtFVm5dFkqf1PW07Hi11Uq17DqHR7DFNuwqfs
nG7W7qwm6m0xjw1KzlXOXfXDIalbCyqWIW4bRRoeXqzbRTOt0WSVEW8YkvDfnIdX
wBpQto0h/tVRxkn3ORBuUAhAE9Uw39YpmChOE7JXWMEiBJLVH4g=
=Ss2r
-----END PGP SIGNATURE-----

--Apple-Mail=_4A619E0A-CA0A-4D54-96F0-1236C58234C4--


From nobody Mon Jul 20 23:50:04 2020
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 C26F33A0EE7 for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 23:50:02 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=eggert.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 izjmBpNEiBb7 for <quic@ietfa.amsl.com>; Mon, 20 Jul 2020 23:50:01 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:0:35:211:32ff:fe22:186f]) (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 1685A3A0E9E for <quic@ietf.org>; Mon, 20 Jul 2020 23:50:01 -0700 (PDT)
Received: from [IPv6:2a00:ac00:0:35:e9f7:316e:5e24:9364] (unknown [IPv6:2a00:ac00:0:35:e9f7:316e:5e24:9364]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 4FB88650833; Tue, 21 Jul 2020 09:49:51 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1595314191; bh=hZcBl8Mo2Y+92e5U0GKGwug2iVvYbbC9mfPpaV3vwlI=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=zfApQKRhgDcnDDmLIKK+fqknyVf4V1y+CkzkJckcQTptjymaKH6UBdc8N1WCsyZCd TZ4QViBpamM6kc95kpLw07+qN+Xk2X9mnJ78w49/oBlbQkCa/A3wP+DFkHOlfLUJqh yHnzjkL5RMRNJZPkLPGvLftyeqJWyyXIMwdzpt7Y=
From: Lars Eggert <lars@eggert.org>
Message-Id: <04697AEF-461E-46C8-B1EC-B15D462B8B7E@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_13C38EE8-85C9-4181-81D5-810FB6C1A20D"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: Re: New confidentiality and integrity limits
Date: Tue, 21 Jul 2020 09:49:51 +0300
In-Reply-To: <02f5d291-4b95-7f94-5028-c90f94bd5908@felixguenther.info>
Cc: quic@ietf.org
To: =?utf-8?Q?Felix_G=C3=BCnther?= <mail@felixguenther.info>
References: <43bb1525-0afa-4c4e-a234-f6ccfacbdd29@www.fastmail.com> <a4d7e8cf-5879-6941-e059-5d2f3e67ae86@huitema.net> <58b40fc0-86ad-49e9-bc17-187c38e97f7a@www.fastmail.com> <1d543593-7abc-4a89-93c5-82c464492786@www.fastmail.com> <CACpbDccSB6H9AhmAinia7ojEg1VY-S=dF214wHvZcZkoiL-xFA@mail.gmail.com> <7d549475-249b-4674-9aa8-c2bf9953243b@www.fastmail.com> <CALGR9oaHQHJneN2edetGLcq4u4PNF0oAyq9PKc7ZVxz_pXTMGw@mail.gmail.com> <CACsn0c=HkByj0dkwfW+0=n9HzGZ0cZamot6N=AFks3wbnwnWXQ@mail.gmail.com> <19922b1a-a02c-46c9-b441-3806d3f77b89@www.fastmail.com> <02f5d291-4b95-7f94-5028-c90f94bd5908@felixguenther.info>
X-MailScanner-ID: 4FB88650833.A100A
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/mP10Rh4j7T8CyLlBnkA-dOFHEfU>
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, 21 Jul 2020 06:50:03 -0000

--Apple-Mail=_13C38EE8-85C9-4181-81D5-810FB6C1A20D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

Thanks, Felix.

Watson, does this address your comments? (Chairs are trying to push =
#3788 to resolution.)

Thanks,
Lars

On 2020-7-16, at 9:47, Felix G=C3=BCnther <mail@felixguenther.info> =
wrote:
>=20
> Hi Watson,
>=20
> Let me clarify that the multi-user setting does not mean that a =
forgery
> attempt is made against all keys simultaneously -- this model still
> counts "try to decrypt 1 ciphertext under 1 key" as 1 forgery attempt.
> The important difference is that, for each attempt, you may try a
> different key.
>=20
> While the model is somewhat more general in allowing to go back and
> forth between all keys, this of course also captures the QUIC setting
> where only few keys are active at any point in time, and are phased
> in/out sequentially. I am not aware of an intermediate model, but I
> don't think the difference would be huge, plus I strongly agree with
> Martin that this conservative over-approximation doesn't hurt much =
here.
>=20
> So, the multi-user model is the closest analysis we have to answer the
> question:  "What's the advantage of an adversary that tries to inject =
a
> forgery *at some point* in a QUIC connection."
> Single-user models cannot answer this question, as they only speak to
> forgery attempts under one fixed key, hence don't capture key updates.
>=20
> I hope this clarifies the need for multi-user bounds.
>=20
> Cheers,
> Felix
>=20
>=20
> On 2020-07-16 06:58 +0200, Martin Thomson <mt@lowentropy.net> wrote:
>> On Thu, Jul 16, 2020, at 11:40, Watson Ladd wrote:
>>> I do not believe the analysis is correct.
>>>=20
>>> A forgery against a QUIC connection will be checked at one or at =
most
>>> two keys: the current one and the next one. It is not the case that =
a
>>> forgery will be attempted against all the keys simultaneously: it =
will
>>> have to be resent. Perhap I'm missing something about the setting =
here
>>> that makes this the multiuser and not the singleuser setting.
>>=20
>> Thanks for checking Watson.
>>=20
>> I had exactly the same thought, but was convinced by Felix that the =
analysis was based on a definition that only considers the number of =
encryption/verification queries in total. In particular, that the values =
in results are not limited in any way by which subset of the keys could =
be tried.
>>=20
>> Incidentally, that also supports the view that there is degradation =
in the confidentiality advantage as you update to different keys.  I =
note that the PR does not acknowledge this, but maybe it should.
>>=20
>> I confess that I'm still not completely confident that the multiuser =
setting is a good fit for our needs (or even that the threat model is =
the right one).  This is, in part of the reason you state: the mu =
setting assumes that the attacker has equal access to all "users" =
concurrently and the limited number of active keys would seem to make =
that difficult to exploit.  But I don't know how to prove that this is =
an acceptable assumption.
>>=20
>> What I am confident about is that a conservative approach doesn't =
hurt a great deal here.  The calculated limits for GCM are high enough - =
even under the assumptions made - that you have serious problems if you =
hit them.
>>=20
>=20


--Apple-Mail=_13C38EE8-85C9-4181-81D5-810FB6C1A20D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAl8WkA8ACgkQVLXDCb9w
wVfmtRAAvAAhbNNaBSkd8AHp27evMVxhHGBw3exiA4pkrsFbh3n7/Jx+JdaHfwnp
VQWrfW8CJIWK9BHsQowLmIuzNcoqxR/j6krekyBgwr5PzePdwBAVhulRfWTJFsR/
4BL3+7Y9IBnJzA8wWfwIKSQU+6KQhl03Q/yM1B9aGgbB3b8Nro7d2Ysq/ZcZByms
UhtPyUblRRs61+bKQf6ppuzC9oQu9+70DuBaG0rzLITIzBrxcVLp8+iUNuYeL7Bs
93OnZLZdAHVUBvYSrceLzNK2TqwnZob6AWY8XRROnjF1FkKGaJ5NLhrdVhZYe8S9
JbXr1C4WEG5Yori9L46MXTfP/QyR8CDYaXUuXB/sQIzwoFhkJBjRIJjhNYR4/eP6
0U7pZksSHCzqfBS56HCbpeXMlKdWoav5vl5K/L2yjUi4BbJPoB8DHf12oqYsv2uB
2nlwuEwAvK6fm126V0eddR8DkjflgOqjSkAzArBBtE7aNfBIl53yRuFjYWscq5Gs
cAsFEDp9EVn5vqKo/IweWM3miO9a58iduh5NFwOqFKVzGCG3J3ObSH1M6A9AFw7F
wat5x1IIJc3BSBpxc9O1y2EVUe2DZxsbrWRnYPUZo0aechDkipALB9xVZmChQqUy
r1hA0QRctK6hcaSzQEfqHER15KivIpvneZ0SbR7SZIJOi9oN1XU=
=cSaZ
-----END PGP SIGNATURE-----

--Apple-Mail=_13C38EE8-85C9-4181-81D5-810FB6C1A20D--


From nobody Tue Jul 21 01:18:19 2020
Return-Path: <jupiter.hce@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 089993A14E9 for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 01:18:17 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, 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 xUmWO9t5ISjU for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 01:18:15 -0700 (PDT)
Received: from mail-ej1-x644.google.com (mail-ej1-x644.google.com [IPv6:2a00:1450:4864:20::644]) (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 86A8E3A14E1 for <quic@ietf.org>; Tue, 21 Jul 2020 01:18:15 -0700 (PDT)
Received: by mail-ej1-x644.google.com with SMTP id lx13so20796258ejb.4 for <quic@ietf.org>; Tue, 21 Jul 2020 01:18:15 -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=HsRwnpNfNEYiGrlCuRRFhezTxtlm1AYP1dR5JxN0wHM=; b=YAOH9CHW4WmBdeWHhmEQq2qYcC/xF3JyJL5IBJdijgpT7p3Q9xrFYDE/9C/a+PzvBt 26PXm44R6c2RTOcD3x6mWOoQEtWGNEZBuMTm6reKXF42qpTcibG+wgwaL57jYmUn/tbJ VrZF0qdkaed7aHbnTx8eqizRh39D+7EDaaApPF2Ynew4gKTFwkZd/NDqhSJuxtWhOY/4 PDEzMjqsiqILyL6aMnkocWTJXDxxGc77SUqYAgii5YUI/UFMxOZlusTVs4rpinf9o1j7 rWRwfN296PMnA+lbrKZomxv9TyJYt/umozKXXAGfQC5k7SmMClEko87ad4qGefjkq3uA Vm7g==
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=HsRwnpNfNEYiGrlCuRRFhezTxtlm1AYP1dR5JxN0wHM=; b=Auf6Ghu/Q0hudUKZehvCYb6zMjus31fHyKL0n56wFMxePUtki3Jmh3SyVjPbzfm7GJ W1hW9CZ/6epJ7hzpioLJW9Au0sQxAxU/9v7rrBashpA6g1FnYFHYrigDqtNVr4gpAW88 96BKE0BQ1A5smh9Y82t/XxD58A6FMeyurBTWIPxzxuJ1I5GIRk13b351BX4JgOE8Un8y Pj7ivF54j/m8jNfwl5+zc07ZAMCP965cgCrJkffBf6Lenf4WwN1Z7ybU3j0s6MwqneTR 6tyibmK7FkxO5+cx8CORCN2pTso9xIRyn3/MFKRg9G313Z6y7CAINMraAX1ADTNd9bvQ bl+w==
X-Gm-Message-State: AOAM530TIUUDLaFoCIiEz92Jvvws2B13Wj3e77LwCQhTbhmX5zG7/Wf4 9uQOZjVSJya+M7xQmK1YS9kJdAzTfIMEqbXtJNVMLBn9
X-Google-Smtp-Source: ABdhPJzOzBzwn6oO2IurVzgMgJgEP+0OEakzaJ9tiGZsIqDxkq80jky2UlX2snCZiU1tuGZkjoE1vktos/MtJJQdL3I=
X-Received: by 2002:a50:e60d:: with SMTP id y13mr24382550edm.225.1595319492902;  Tue, 21 Jul 2020 01:18:12 -0700 (PDT)
MIME-Version: 1.0
References: <CAA=hcWS0V8ipsoAEFK3ejdA++Vzi+czth37=ntP4mnt8d=mtRg@mail.gmail.com> <1C514B96-9AAA-40B3-93EC-3DCDFAF72A93@eggert.org>
In-Reply-To: <1C514B96-9AAA-40B3-93EC-3DCDFAF72A93@eggert.org>
From: Jupiter <jupiter.hce@gmail.com>
Date: Tue, 21 Jul 2020 18:17:36 +1000
Message-ID: <CAA=hcWTP7mVo1yyr8wQrgNuA40Tr5=XcrqJiebtVa7Km=2sLzw@mail.gmail.com>
Subject: Re: Small size of core QUIC library to replace TCP for embedded system
To: Lars Eggert <lars@eggert.org>
Cc: quic <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/HmtMzLKkQ72XpOnSCBLx6eHRkzs>
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, 21 Jul 2020 08:18:17 -0000

Thanks Lars and all responses, I am very grateful for all of your kind
comments and advice.

On 7/21/20, Lars Eggert <lars@eggert.org> wrote:
> you don't really say what type of device you are targeting, so it's a bit
> difficult to respond in detail.

Sorry for neglecting that part, I am running Linux on iMX6ULZ using
all sorts of open source libraries in C and C++.

> But I did port my quant QUIC stack (https://github.com/NTAP/quant) to
> Particle DeviceOS and RIOT, and ran some client-only measurements on a
> Particle Argon and an ESP32. There's a writeup in
> https://eggert.org/papers/2020-ndss-quic-iot.pdf, slides in
> https://github.com/t2trg/2020-ietf107/blob/master/slides/22-towards-securing-the-internet-of-things-with-quic.pdf.
> (There was also a recording of the T2TRG talk, but it doesn't seem to be
> uploaded to GitHub yet.)

Thanks for the links, I have to admit, my QUIC knowledge is limited, I
thought QUIC should be a user space program, anything talking to low
layers through Linux kernel API, seems you have to alter Ethernet RX /
TX for QUIC, does that mean you have to alter WiFi or other media
communications as well? My WiFi is currently supported by Linux open
source mwifiex.

> It should be reasonably straightforward to add a packet I/O backend for
> other IoT platforms to warpcore, (https://github.com/NTAP/warpcore) which is
> quant's packet I/O library. I had been considering Zephyr support, but ran
> out of time.

Looks very good, I suppose I should be able to run it on an Ubuntu 18
laptop, right?

> Note: quant is a research effort and not meant for production.

Understood, let me see if I can make some contributions for the project.


Thank you.

Kind regards,

jupiter


--
"A man can fail many times, but he isn't a failure until he begins to
blame somebody else."
-- John Burroughs


From nobody Tue Jul 21 01:26:42 2020
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 5CCDB3A15D0 for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 01:26:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=eggert.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 qg9l2_Mf5j1O for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 01:26:39 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:0:35:211:32ff:fe22:186f]) (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 822273A15CF for <quic@ietf.org>; Tue, 21 Jul 2020 01:26:39 -0700 (PDT)
Received: from [IPv6:2a00:ac00:0:35:e9f7:316e:5e24:9364] (unknown [IPv6:2a00:ac00:0:35:e9f7:316e:5e24:9364]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 5B3F5643F60; Tue, 21 Jul 2020 11:26:29 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1595319989; bh=t57jqrPq1HvqEDPdOv23BBZKecl/LmGkzXgdmQv16Fk=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=0AVs1noKZ01NETOwbYjEJWEHRFiLHitv/FH9XXDix5wUMDMjUk+xB2/9PzIuSQixu 4D/MNrpFFstbK8wpBmbYM14QTTymQl5GemmIZNrNMD3dNmxtMiLAxnyuwK+O0rkgs0 qdJU86JhNN0vMxIeAuOV1gTtHtQ5jOqq6oTw2hL8=
From: Lars Eggert <lars@eggert.org>
Message-Id: <F384B33C-70F8-45EF-AB5C-30D0A145659A@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_FDAD78C0-6493-47F2-B2FD-475BED90032B"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: Re: Small size of core QUIC library to replace TCP for embedded system
Date: Tue, 21 Jul 2020 11:26:29 +0300
In-Reply-To: <CAA=hcWTP7mVo1yyr8wQrgNuA40Tr5=XcrqJiebtVa7Km=2sLzw@mail.gmail.com>
Cc: quic <quic@ietf.org>
To: Jupiter <jupiter.hce@gmail.com>
References: <CAA=hcWS0V8ipsoAEFK3ejdA++Vzi+czth37=ntP4mnt8d=mtRg@mail.gmail.com> <1C514B96-9AAA-40B3-93EC-3DCDFAF72A93@eggert.org> <CAA=hcWTP7mVo1yyr8wQrgNuA40Tr5=XcrqJiebtVa7Km=2sLzw@mail.gmail.com>
X-MailScanner-ID: 5B3F5643F60.A4669
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/rqK3sm_a2zPUsslz7HeBdLQfvVo>
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, 21 Jul 2020 08:26:41 -0000

--Apple-Mail=_FDAD78C0-6493-47F2-B2FD-475BED90032B
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 2020-7-21, at 11:17, Jupiter <jupiter.hce@gmail.com> wrote:
> I am running Linux on iMX6ULZ using
> all sorts of open source libraries in C and C++.

if your hardware can run Linux, most of the current open source stacks =
(see https://github.com/quicwg/base-drafts/wiki/Implementations) should =
be small enough to work. But I wouldn't call it an embedded system =
then...

> Thanks for the links, I have to admit, my QUIC knowledge is limited, I
> thought QUIC should be a user space program, anything talking to low
> layers through Linux kernel API,

That is how most implementations work, correct.

But constrained-resource embedded devices at the low end often can't run =
Linux or another full-fledged OS. Many hence link together an =
application with only the required bits of a library OS (RIOT, Zephyr, =
FreeRTOS & derivatives) and run that statically on bare metal.

> seems you have to alter Ethernet RX /
> TX for QUIC, does that mean you have to alter WiFi or other media
> communications as well? My WiFi is currently supported by Linux open
> source mwifiex.

You do not need to do this for QUIC, only when you want to run on =
embedded boards that don't have a capable-enough Socket API interface.

>> It should be reasonably straightforward to add a packet I/O backend =
for
>> other IoT platforms to warpcore, (https://github.com/NTAP/warpcore) =
which is
>> quant's packet I/O library. I had been considering Zephyr support, =
but ran
>> out of time.
>=20
> Looks very good, I suppose I should be able to run it on an Ubuntu 18
> laptop, right?

It will run on Linux without changes (my public test server runs =
Ubuntu).

Lars


--Apple-Mail=_FDAD78C0-6493-47F2-B2FD-475BED90032B
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAl8WprUACgkQVLXDCb9w
wVfbjQ//bsap76n3zf+ZJix2YOmRy2/DRAn9R+YXBEPzchHPT2gxnYwKc3Rc2j2w
PDPfxwqNXPFq/HOtSWDqAu6ulwFV7ciOULSc10mqqT2D7BS7Etpfw4757+WgVxRU
9QynEDya2SVhg2EBXHU+ptzP0AAUe3e40s4uGyMNwvsUN0HZ+hR5hLgUaSf0b2cA
K+T1EVOhF3JymRzcOwOXHlfmnFN7aRNjetEPZlkRCHK4Lj5JYO6v6CwdFU9eKQTM
p4f/ZQHwiEV5fykHaxQOXLFzCA9V5uQpClaRjp+zIB/qGAxGKfZ7mmsg/nM0y2NK
CtU/YLCQsomFv7NXe9osBVIkkAz0BL2NJ7a0PhYcy17UGA+QW6IeuTgJ0hyZX1VA
73WSyJ9zUpXO/6ePI8PTvhDtzSWCB43856fUSW1Y6ejpsIRSiSEx8xnZuTLXB0oX
4WG8TG7akIXgrMJodvv+oBID2QuEZ0XKXwCbVG0Y/IGLs+YF8elM/kf1N+cn0zgl
HnscHcFbAoroh9wihfy+H64gfocvB3v0KaW7b+/HPI3lSCnpXF0Zk1+D5Q4McbjZ
MIDKjYOWc3kD/HTOTWHHO/hvod98b6H8n8Q/kfbYP2jls0iK9VrAxlyZyGauFYxT
n9sk6Db2gBNv8UUwkFblEAUVY4wh6M6wwtQSq32rcnky0msyIZs=
=sdQj
-----END PGP SIGNATURE-----

--Apple-Mail=_FDAD78C0-6493-47F2-B2FD-475BED90032B--


From nobody Tue Jul 21 03:57:03 2020
Return-Path: <jupiter.hce@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 54F163A0A4F for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 03:57:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, 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 ry9N_ZIF_C3E for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 03:57:00 -0700 (PDT)
Received: from mail-ej1-x635.google.com (mail-ej1-x635.google.com [IPv6:2a00:1450:4864:20::635]) (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 F0AF73A0A36 for <quic@ietf.org>; Tue, 21 Jul 2020 03:56:59 -0700 (PDT)
Received: by mail-ej1-x635.google.com with SMTP id n22so18263220ejy.3 for <quic@ietf.org>; Tue, 21 Jul 2020 03:56:59 -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=b1cGaMMTAqk8yTf9tRVtsMY+CR/NeM/US9buP1XYyjY=; b=pafegytsRbwcYnnqOwbNWlqygYFpc8QzW9bs+0GiC9+4BWYjEsdnqUWLgaP2R6KYyp vR/HQq2hOBbiXeKcmWNHol3RcFtykxxaepuT261IhLMpB1UeC7kF1hrDOR7YGSnQCErM +ompSZGcQF/A6SzQSDONQPTqtEBkZ93RNGn5dFJctzOWZgom+ZqauVr4JHmSWvXxQGuo lkWXV1u58uzN/r1ECJqmLbj7PK6xphW53AfoNo0hdr6mSSAlqa1XAHbv1GYmb4p452bK qcgZbx16UmQFS18iKlKW6eoMBXUusArIbMn8i5cbAu220P26kjUteox8JFttOS8lrWnj DrzA==
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=b1cGaMMTAqk8yTf9tRVtsMY+CR/NeM/US9buP1XYyjY=; b=ekKG+eebuXev8MfbCRFVtuqxHzeseX+c8In+XM+0VlXNoVxKsBDKoaDwAJ65vzg935 hw9fRELLDNyw/Vt356u5hzgOJuoMJwLV7TeOtYorynbYbrWFqxSkwVnZCIChWJw4/bF0 GaUmQZjcoOeL0XjLDyCx7H1PuTEZQ71geZ0I21L11g51vEoqRWOJX1ut4U4QeCdqgYci 4i3eaUZLfQZwoatMXG+AZOxYb1AW7/xlm9QPRuX3Q0kuL4NrdVM1KHncZYEyefCvfVBE hkiMnVxVfI2Dacvyk5EdIJGtGg5KFo0jI6OEHjLSVb7R90U8pXl+Cfv+KbySrgGmyNZb T+Ug==
X-Gm-Message-State: AOAM53221fcGUNxVICJnIPfQncsMmFB7kirTOHY5L8F1iEYFsLsPd6KY cN8mfSHUynMBp1KI4V/ZfQ4Mej+t8a1pgcI7DxXSoGWJCCwW7Q==
X-Google-Smtp-Source: ABdhPJxcNYQxEnKJ/HLRA+3CFxHH28ddggr4ChHPauSTn9yVQXzhvcFCm+D+ct8v4iHrAniFNEub9RWr2QTgND9GTio=
X-Received: by 2002:a17:907:40f5:: with SMTP id no5mr24269979ejb.149.1595329018512;  Tue, 21 Jul 2020 03:56:58 -0700 (PDT)
MIME-Version: 1.0
References: <CAA=hcWS0V8ipsoAEFK3ejdA++Vzi+czth37=ntP4mnt8d=mtRg@mail.gmail.com> <1C514B96-9AAA-40B3-93EC-3DCDFAF72A93@eggert.org> <CAA=hcWTP7mVo1yyr8wQrgNuA40Tr5=XcrqJiebtVa7Km=2sLzw@mail.gmail.com> <F384B33C-70F8-45EF-AB5C-30D0A145659A@eggert.org>
In-Reply-To: <F384B33C-70F8-45EF-AB5C-30D0A145659A@eggert.org>
From: Jupiter <jupiter.hce@gmail.com>
Date: Tue, 21 Jul 2020 20:56:22 +1000
Message-ID: <CAA=hcWQ60GH2TnjvqBEGvVQ1whxNYwEWjQ+b9FW948GKvN570Q@mail.gmail.com>
Subject: Re: Small size of core QUIC library to replace TCP for embedded system
To: Lars Eggert <lars@eggert.org>
Cc: quic <quic@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/NNrht_Yx1olsRWePSoh4ild1qrI>
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, 21 Jul 2020 10:57:01 -0000

Hi Lars,

On 7/21/20, Lars Eggert <lars@eggert.org> wrote:
> if your hardware can run Linux, most of the current open source stacks (see
> https://github.com/quicwg/base-drafts/wiki/Implementations) should be small
> enough to work. But I wouldn't call it an embedded system then...

Sorry for not being clear, I should say Linux embedded system at the
beginning. Although I would say the time for embedded systems with 8M
Flash and 64KRAM has been long gone :-), I still have to manage the
resources for meaning full network stacks and applications.

> But constrained-resource embedded devices at the low end often can't run
> Linux or another full-fledged OS. Many hence link together an application
> with only the required bits of a library OS (RIOT, Zephyr, FreeRTOS &
> derivatives) and run that statically on bare metal.

With all due respect, unless you are working on IoT for tiny devices
cannot run Linux, it is 2020, hardware is cheaper, software
development is expensive, Linux and open source become dominant force
in contemporary embedded system, your Android mobile phone is an
embedded system running Linux :-), Sorry let's stop it, we are too far
off topic.

> You do not need to do this for QUIC, only when you want to run on embedded
> boards that don't have a capable-enough Socket API interface.

Good to know, fair to say your git source is for RTOS statically on
bare metal, I was there a long time before :-).

> It will run on Linux without changes (my public test server runs Ubuntu).

I'll try it, thanks Lars.


jupiter

--
"A man can fail many times, but he isn't a failure until he begins to
blame somebody else."
-- John Burroughs


From nobody Tue Jul 21 08:42:41 2020
Return-Path: <tim.jebb@bt.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E15963A0B3A for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 08:42:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=bt.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 pkcxhVUT6rrC for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 08:42:35 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [213.121.35.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4421B3A0B39 for <quic@ietf.org>; Tue, 21 Jul 2020 08:42:34 -0700 (PDT)
Received: from tpw09926dag13h.domain1.systemhost.net (10.9.212.37) by BWP09926078.bt.com (10.36.82.109) with Microsoft SMTP Server (version=TLS1_2,  cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Tue, 21 Jul 2020 16:42:31 +0100
Received: from tpw09926dag03f.domain1.systemhost.net (10.9.202.22) by tpw09926dag13h.domain1.systemhost.net (10.9.212.37) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Tue, 21 Jul 2020 16:42:31 +0100
Received: from bwp09926077.bt.com (10.36.82.108) by tpw09926dag03f.domain1.systemhost.net (10.9.202.22) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Tue, 21 Jul 2020 16:42:31 +0100
Received: from GBR01-LO2-obe.outbound.protection.outlook.com (104.47.21.51) by smtpe1.intersmtp.com (10.36.82.108) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Tue, 21 Jul 2020 16:42:29 +0100
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=TB6TvTBnmNCNnCNzpFXaYx9SlRGxS6yS+M+EEGp5YaONiVXWgrOmkJFMudBeu2gN+dGfZgvt/c7p7A1TcRSFtPel/FHOkRcQMdYti3+HzSNyghaBspbTHNghU3NIetlmjtd+DKO7uV38j6vGH6aq1i0VgHt5JoqpWSp5nCXdt13f9W2RtZwcI/1frQj0mWsOas67mdUfbJYeZKpGS7pkDzdZ1iuIDYXD3lMUMOZhAPIM2HHCCCl8QTwLYI7hFELEg9xQB2QLQiI8o3COCTgtqI6LerqTt3pP+PvTeoyx5ZEs2a7C4ORS4QEVwcFQLkfNVmE0jA1EkVc7okgMmQwb2A==
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=VPOddNIK1j1LrYK7TLMB2AMeJTHew9eMkaQfErie2vE=; b=l59V5eJE/NssIrqeKjoP/0VSrsFGMl0nxowZdcJ4vNPtzNouJjZUA9uz44xSY6aijA4yhhXFvNTcSswruVh+EgZodQHMavMckQ/1FHbFF3or45WC1Tarbke11Lo1i5qAu7aCfi3n1fQuUSKBgxNfxTQhRjc32YZjaXAbBlvfMxZNN8HTG0oWLWUSkoSMJFTELR50aVQ4wXSfrt8RHoOot/5UqSjTdjxgTR0w7yli74gcg4UoX2bDARlfC3zL0lJwNgL0uPnZ4r130XGIrX+S4VAEoBwJtttcRgt0T4kU5OF/leAcNh9uIZte/ZvomNGqUmoxQ92Q7M+llZ/KzM2S4Q==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=bt.com; dmarc=pass action=none header.from=bt.com; dkim=pass header.d=bt.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bt.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=VPOddNIK1j1LrYK7TLMB2AMeJTHew9eMkaQfErie2vE=; b=o5hknBzWPxIb/rKx0wUPa1VgONQu2Uf/qfv4kx4OyaeOi5vQzm/G8vNEFtcwSN+j02PCy/JOzcW4oVTkptNqNkSlv0lMHDXGfpC6aDsHqn9JefJy7dlpll10ht2C7Ff0TDm4Imxdmyhb0/ZvvE/pJMA1lw+WzJ51JdIx7WI8iI4=
Received: from LO2P123MB2462.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:ce::21) by LO3P123MB3147.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:b0::10) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3195.18; Tue, 21 Jul 2020 15:42:30 +0000
Received: from LO2P123MB2462.GBRP123.PROD.OUTLOOK.COM ([fe80::d403:1ac2:35d2:73ff]) by LO2P123MB2462.GBRP123.PROD.OUTLOOK.COM ([fe80::d403:1ac2:35d2:73ff%7]) with mapi id 15.20.3195.026; Tue, 21 Jul 2020 15:42:30 +0000
From: <tim.jebb@bt.com>
To: <nharper@google.com>
CC: <quic@ietf.org>
Subject: RE: Problems verifying sample packet protection in appendix A of Using TLS to Secure QUIC
Thread-Topic: Problems verifying sample packet protection in appendix A of Using TLS to Secure QUIC
Thread-Index: AdZZ60hBgJSiLWoSRDqZxGYKUQVBHwAI+HGAAVk5nPA=
Date: Tue, 21 Jul 2020 15:42:30 +0000
Message-ID: <LO2P123MB2462F4CDAD99B8E3DAA39F9FF2780@LO2P123MB2462.GBRP123.PROD.OUTLOOK.COM>
References: <LNXP123MB2460833EC5BC592C8D410EDCF2610@LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM> <CACdeXi+EUWRGoT7pWrqnEbQK9EoT0ERr7pKFmtOQ3pQZc9wfCw@mail.gmail.com>
In-Reply-To: <CACdeXi+EUWRGoT7pWrqnEbQK9EoT0ERr7pKFmtOQ3pQZc9wfCw@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: google.com; dkim=none (message not signed) header.d=none;google.com; dmarc=none action=none header.from=bt.com;
x-originating-ip: [31.51.248.139]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 7348e916-edf0-41ae-a9c3-08d82d8cad9c
x-ms-traffictypediagnostic: LO3P123MB3147:
x-microsoft-antispam-prvs: <LO3P123MB31470D7F9EB8C452A6D4BB7BF2780@LO3P123MB3147.GBRP123.PROD.OUTLOOK.COM>
x-antispam-2: 1
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: flj7skstaEHWoL0Koj7dOScPPpehrWdwcVqkQAcqDNPi9ktie7AN0LdU3XPThE3CwyD+q3rU79FcnFC5v5YY7xpLqbMhnTFq+X0w21j8lyk1NyVqYPDhXZC76gKEwu/kXHOgcop7FMiomK0L/edLCqvYIHrOevA+Mpnex/I23Jf+SOQklWRv7n7pUU/gzj2je+eSZAfvyLOKz0MLWkbDRTU3DRc6APUQvriH1aWpfvbMR517vLBkv4SLagLE6Cp/tJFUKiIUaNoo9TxDXuRoLTLYdTgILGVnVicS3fTejO+xPM2FxNEnZhGzhanvh9pw+QdjxK5OtAEAEjg7mT2InkTme5nBgjyzjJM9ISj5jsCNuEDAMdLtpl4rhhJcH9ETmB/Ss1SnIzw/Raaxg6pSaA==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:LO2P123MB2462.GBRP123.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(366004)(136003)(346002)(39860400002)(396003)(376002)(6506007)(71200400001)(8676002)(26005)(55236004)(186003)(7696005)(66946007)(64756008)(66476007)(66556008)(76116006)(66446008)(478600001)(966005)(83380400001)(16799955002)(166002)(4326008)(6916009)(53546011)(2906002)(316002)(8936002)(55016002)(9326002)(52536014)(9686003)(33656002)(15650500001)(86362001)(5660300002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: 1KxGTF25S6PoUhyj7SXMAqIG0zaiVtXw6SqgQEmiS1zR3VHNiewmhUlXZlcZWGWMcn+crDs8/THVDCbaD3pQojkSXLvSNI61puG8qjAismlHW0BQiHo7QDJI+Fz9kuG5dldT21p1S4LQZEXAnB6w3VoitPPKABzWkux2ISInsdc1ywDqIgK9JIoXr/y2cEq9GC/RgLvys0O0VOQHnvJHb95de2ZMf3rp4S0yqbmtp510GNx/6KDw0P6lAzfjgwD/Jm/Xga5uYYKRNyGOv7W/vkc4seNYEnNZJmtBU16CX7VXBWXF88ZRJqjLZo0I60/tWetsS19Q09hY9VKHW9pjiCxnzvnBR+cVTsQRoEIMX5Ksckx08UB9W0xFaFQk63dSYIoVpSTOWNpvl60IOEy3IeJhiYU6m2Dx2zzFGLO2irL61y1tXu81nAVNHxSEHIQjU2/YUYfEHp+6BMEnmtR9ht/IvWpftFqdpxvLvOSPsJU=
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_LO2P123MB2462F4CDAD99B8E3DAA39F9FF2780LO2P123MB2462GBRP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: LO2P123MB2462.GBRP123.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 7348e916-edf0-41ae-a9c3-08d82d8cad9c
X-MS-Exchange-CrossTenant-originalarrivaltime: 21 Jul 2020 15:42:30.3592 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a7f35688-9c00-4d5e-ba41-29f146377ab0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: i5FdhaTE0otYzDP085YqdMLgcJIKEL5HNw3ey9SoRO0VNqrt9mFtB0RplYcnRG4Q
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LO3P123MB3147
X-OriginatorOrg: bt.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/AmDlglk1cXqsvKiasxDAyw6lRBs>
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, 21 Jul 2020 15:42:39 -0000

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

SGksDQoNClVuZm9ydHVuYXRlbHkgSeKAmW0gc3RpbGwgaGF2aW5nIHByb2JsZW1zIHJlbW92aW5n
IHBhY2tldCBwcm90ZWN0aW9uLg0KDQpBbHRob3VnaCBJIGNhbiBub3cgc3VjY2Vzc2Z1bGx5IHBy
b2Nlc3MgdGhlIHNhbXBsZSBwYWNrZXQgaW4gdGhlIGRyYWZ0IFJGQyAodGhhbmtzIHRvIE5pY2sp
LCBteSBmaXJzdCBhdHRlbXB0IGF0IGEgY2FwdHVyZWQgcGFja2V0IGlzIGZhaWxpbmcgKHVzaW5n
IHRoZSBzYW1lIGNvZGUpLiAgSSBjYW7igJl0IHNlZSB3aGVyZSBJ4oCZbSBnb2luZyB3cm9uZy4g
IEl04oCZcyB0aGUgaGVhZGVyIHByb3RlY3Rpb24gcmVtb3ZhbCBJ4oCZbSBoYXZpbmcgcHJvYmxl
bXMgd2l0aC4NCg0KSWYgaXTigJlzIG5vdCB0b28gbXVjaCB0byBhc2ssIHdvdWxkIGFueW9uZSBi
ZSBpbiBhIHBvc2l0aW9uIHRvIHByb2Nlc3MgdGhlIGNsaWVudCBpbml0aWFsIHBhY2tldCBiZWxv
dywgYW5kIGdpdmUgdGhlIGludGVybWVkaWF0ZSB2YWx1ZXMgYWxvbmcgdGhlIGxpbmVzIG9mIHRo
b3NlIGdpdmVuIGluIGFwcGVuZGl4IEE/DQoNClRoZSBwYWNrZXQgaXMNCg0KdWludDhfdCBwcm90
ZWN0ZWRfZnJhbWUxWzMwMl0gPQ0KezB4YzgsMHhmZiwweDAwLDB4MDAsMHgxYiwweDExLDB4NzYs
MHhmOCwweDFhLDB4NTUsMHg4OCwweGIyLDB4ZjIsMHg1YywweDVhLDB4YjYsDQoweGRiLDB4ZDQs
MHg2MSwweGE4LDB4ZDcsMHg0OSwweGUxLDB4MDMsMHhjNSwweGVmLDB4MDIsMHgwMCwweDQxLDB4
MTAsMHhiMCwweGJkLA0KMHgxNCwweDA0LDB4ZjUsMHgzNSwweDE3LDB4N2YsMHhjYiwweGNmLDB4
ZDUsMHhmMCwweDZkLDB4MjQsMHhmZiwweGRlLDB4NjYsMHhlZCwNCjB4ZjEsMHgwZCwweGY3LDB4
OTIsMHgwNSwweDY2LDB4NmIsMHgxOCwweDUxLDB4MTgsMHg5ZiwweDU0LDB4YTAsMHg5MiwweDdk
LDB4ZjIsDQoweDMwLDB4YjUsMHhjYiwweGQ3LDB4YzksMHg2ZCwweGU2LDB4YzUsMHg3NiwweGU1
LDB4NTksMHg0MiwweDIzLDB4MWUsMHhjOCwweDUzLA0KMHg5ZiwweGYyLDB4ODIsMHhlMiwweGNm
LDB4ZDcsMHg1MywweDgzLDB4OGIsMHgxMiwweDUzLDB4Y2UsMHgxOSwweDVjLDB4ZDYsMHgzMiwN
CjB4MjIsMHg1ZCwweGUwLDB4Y2EsMHgyZSwweDM3LDB4NDIsMHhjMSwweGRhLDB4MDgsMHg0ZCww
eGE0LDB4ZDEsMHgxOCwweGM3LDB4NzUsDQoweDdjLDB4M2MsMHhhZSwweDNiLDB4ZjYsMHg5NSww
eGEyLDB4YzYsMHg4MywweDk5LDB4OTcsMHg5ZiwweDk4LDB4MGQsMHhkYiwweGE2LA0KMHhhOSww
eDc3LDB4YmQsMHhiYSwweDMxLDB4MjAsMHhiMiwweDhiLDB4ZTgsMHgwZSwweDBiLDB4ZTksMHhl
MCwweDg5LDB4M2YsMHgwNSwNCjB4OGQsMHhkZCwweDhkLDB4N2IsMHhlMywweDkwLDB4ZGUsMHhk
NiwweDY4LDB4NzksMHg2MiwweDhkLDB4NDcsMHhiNywweDQ3LDB4NzgsDQoweDE3LDB4NGUsMHg5
ZSwweDY1LDB4OTMsMHhjZSwweDgxLDB4MTcsMHhiZiwweDVmLDB4NGIsMHgxNiwweGI4LDB4OGQs
MHhlMywweDQ4LA0KMHg0ZiwweDk3LDB4N2UsMHgyMiwweGRlLDB4ZDgsMHg2ZSwweGIyLDB4OWIs
MHgwMCwweGJkLDB4YTQsMHhhNCwweGZiLDB4NzQsMHg5YywNCjB4ZWUsMHg4MywweDI5LDB4ZDYs
MHhmMSwweDMyLDB4YjMsMHg5MSwweGJiLDB4NmUsMHg5YSwweDkzLDB4NzEsMHg2MSwweGM0LDB4
ZDksDQoweGViLDB4MzAsMHgyZiwweDQzLDB4NzMsMHgyMCwweGU0LDB4NzgsMHgyOSwweGZmLDB4
ZTcsMHgxOSwweDExLDB4OTcsMHhlOCwweDMzLA0KMHhkNSwweDQ3LDB4ZDEsMHg2ZSwweGMxLDB4
ZGMsMHg5MSwweDBmLDB4ZDYsMHhmZSwweGFjLDB4NjQsMHg5NCwweDk5LDB4MDAsMHhiOSwNCjB4
OTEsMHg3OSwweGY2LDB4MWMsMHgxMSwweDg1LDB4NDQsMHhkMSwweDlmLDB4NTYsMHhiZSwweDNm
LDB4NGYsMHg1MiwweGE3LDB4MmMsDQoweDUyLDB4M2QsMHgyYiwweDQxLDB4ZTAsMHg0MiwweGE3
LDB4NGMsMHhiYywweDMxLDB4ZDQsMHhiMywweGE0LDB4NTUsMHhkZSwweGNlLA0KMHgwYywweGJl
LDB4OWQsMHgyOSwweDU5LDB4ZGYsMHhmOCwweGZiLDB4NTMsMHgwYywweDY0LDB4MmUsMHhiNSww
eDJkLDB4YTQsMHgzZCwNCjB4ZWEsMHhmOSwweDkwLDB4OGMsMHgxYiwweDBiLDB4ZDUsMHgwZCww
eDQ0LDB4NTksMHhlMCwweGU0LDB4NzQsMHg4NX07DQoNCkZyb206IE5pY2sgSGFycGVyIDxuaGFy
cGVyQGdvb2dsZS5jb20+DQpTZW50OiAxNCBKdWx5IDIwMjAgMTk6NDcNClRvOiBKZWJiLFRSLFRp
bSxWSUUgUiA8dGltLmplYmJAYnQuY29tPg0KQ2M6IElFVEYgUVVJQyBXRyA8cXVpY0BpZXRmLm9y
Zz4NClN1YmplY3Q6IFJlOiBQcm9ibGVtcyB2ZXJpZnlpbmcgc2FtcGxlIHBhY2tldCBwcm90ZWN0
aW9uIGluIGFwcGVuZGl4IEEgb2YgVXNpbmcgVExTIHRvIFNlY3VyZSBRVUlDDQoNCg0KDQpPbiBU
dWUsIEp1bCAxNCwgMjAyMCBhdCA5OjA2IEFNIDx0aW0uamViYkBidC5jb208bWFpbHRvOnRpbS5q
ZWJiQGJ0LmNvbT4+IHdyb3RlOg0KSGksDQoNCknigJltIHdvcmtpbmcgdGhyb3VnaCBBcHBlbmRp
eCBBIG9mIHRoZSBRVUlDIFRMUyBkb2MgdG8gY2hlY2sgbXkgdW5kZXJzdGFuZGluZywgYnV0IGFt
IGhhdmluZyB0cm91YmxlIGRlY3J5cHRpbmcgdGhlIHNhbXBsZSBjbGllbnQgaW5pdGlhbCBwYWNr
ZXQuICBJ4oCZbSB1bnN1cmUgaWYgSeKAmXZlIG1hZGUgYSBzaWxseSBlcnJvciBvciB0d28sIG9y
IGlmIEnigJl2ZSBtYWRlIG9uZSBvciBtb3JlIGluY29ycmVjdCBhc3N1bXB0aW9ucy4gIE9yIGJv
dGguDQoNClRoZSBmdW5jdGlvbnMgSeKAmW0gdXNpbmcgYXJlIHRoZSBPcGVuU1NMIEVWUCBvbmVz
LiAgSeKAmW0gYXR0ZW1wdGluZyB0byBmb2xsb3cgdGhlIHJlY2lwZSBoZXJlOg0KaHR0cHM6Ly93
aWtpLm9wZW5zc2wub3JnL2luZGV4LnBocC9FVlBfQXV0aGVudGljYXRlZF9FbmNyeXB0aW9uX2Fu
ZF9EZWNyeXB0aW9uI0F1dGhlbnRpY2F0ZWRfRGVjcnlwdGlvbl91c2luZ19HQ01fbW9kZSBpbiBj
b25qdW5jdGlvbiB3aXRoIHRoZSBkcmFmdCBSRkMuDQoNCg0KRVZQX0NJUEhFUl9DVFhfbmV3KCkN
Cg0KRVZQX0RlY3J5cHRJbml0X2V4KGN0eCwgRVZQX2Flc18xMjhfZ2NtKCksIE5VTEwsIE5VTEws
IE5VTEwpDQoNCkVWUF9EZWNyeXB0SW5pdF9leChjdHgsIE5VTEwsIE5VTEwsIGNsaWVudF9rZXks
IGl2KSAgICAgICAgIHdoZXJlIHRoZSBjbGllbnQga2V5IGlzIDB4MTc1MjU3YTMxZWIwOWRlYTkz
NjZkOGJiNzlhZDgwYmEgYW5kIHRoZSBpdiBpcyAweDZiMjYxMTRiOWNiYTJiNjNhOWU4ZGQ0Zg0K
DQpZb3UgbmVlZCB0byBjb21wdXRlIHRoZSBub25jZSBmcm9tIHRoZSBJViBhbmQgdGhlIHBhY2tl
dCBudW1iZXIuIEkgYXNzdW1lIHdoYXQgdGhlIG9wZW5zc2wgZG9jdW1lbnRhdGlvbiByZWZlcnMg
dG8gYXMgYW4gSVYgaXMgYWN0dWFsbHkgdGhlIG5vbmNlIGFzIGRlc2NyaWJlZCBpbiBSRkMgNTEx
Ni4NCg0KRVZQX0RlY3J5cHRVcGRhdGUoY3R4LCBOVUxMLCAmbGVuLCBwVW5wcm90ZWN0ZWRIZWFk
ZXIsIGhlYWRlckxlbmd0aCkgICAgICAgICAgIHdoZXJlIHRoZSB1bnByb3RlY3RlZCBoZWFkZXIg
aXMgMHhjM2ZmMDAwMDFkMDg4Mzk0YzhmMDNlNTE1NzA4MDAwMDQ0OWUwMDAwMDAwMiDigJMgdGhp
cyBJIGJlbGlldmUgaXMgdGhlIEFkZGl0aW9uYWwgRGF0YSByZXF1aXJlZA0KDQpFVlBfRGVjcnlw
dFVwZGF0ZShjdHgsIGRlY3J5cHRlZFBheWxvYWQsICZsZW4sIHBQYXlsb2FkLCBwYXlsb2FkTGVu
Z3RoLTE2KSkgICBoZXJlIEnigJltIHBhc3NpbmcgaW4gdGhlIGVuY3J5cHRlZCBwYXlsb2FkIGJl
Z2lubmluZyAweGZiNjZiYzVmIGFuZCBlbmRpbmcgMHhlODJhNGQ5MTlkNDgsIGxlbmd0aCAxMTYy
LiAgSeKAmW0gYXNzdW1pbmcgdGhhdCB0aGUgZmluYWwgMTYgYnl0ZXMgb2YgdGhlIHBheWxvYWQg
aXMgdGhlIGF1dGhlbnRpY2F0aW9uIHRhZyBzbyBhbSBub3QgcGFzc2luZyBpdCBpbiBoZXJlLiAg
Tm90ZSB0aGF0IGlmIHRoaXMgYXNzdW1wdGlvbiBhYm91dCB0aGUgYXV0aGVudGljYXRpb24gdGFn
IGlzIGNvcnJlY3QsIEkgdGhpbmsgaXQgY291bGQgYmUgbW9yZSBjbGVhcmx5IHN0YXRlZCBpbiB0
aGUgZHJhZnQgUkZDLg0KDQpUaGlzIGlzIGEgcXVpcmsgb2YgdGhlIG9wZW5zc2wgQVBJIHVuZm9y
dHVuYXRlbHkuIEFuIEFFQUQgZGVjcnlwdGlvbiBvcGVyYXRpb24gc2hvdWxkIHRha2UgNCBpbnB1
dHM6IHRoZSBrZXksIHRoZSBub25jZSwgdGhlIGFzc29jaWF0ZWQgZGF0YSwgYW5kIHRoZSBjaXBo
ZXJ0ZXh0LiBUaGUgY2lwaGVydGV4dCwgYXMgZGVmaW5lZCBieSBSRkMgNTExNiwgaW5jbHVkZXMg
dGhlIHRhZy4gVGhlcmUncyBubyByZXF1aXJlbWVudCBvbiB0aGUgc3RydWN0dXJlIG9mIGFuIEFF
QUQncyBjaXBoZXJ0ZXh0LCBpbmNsdWRpbmcgdGhhdCBzb21lIHBvcnRpb24gb2YgdGhlIGNpcGhl
cnRleHQgYmUgYWJsZSB0byBiZSBpZGVudGlmaWVkIGFzIGEgdGFnLiBBRVMtR0NNIGRvZXMgaGF2
ZSB0aGlzIHN0cnVjdHVyZSB3aGVyZSB0aGUgdGFnIGlzIGF0IHRoZSBlbmQgb2YgdGhlIGNpcGhl
cnRleHQsIGFuZCB1bmZvcnR1bmF0ZWx5IG9wZW5zc2wgbWFrZXMgdGhhdCBwYXJ0IG9mIHRoZSBh
cGkgZm9yIHRoZSBBRUFEIG9wZW4gb3BlcmF0aW9uLCBldmVuIHRob3VnaCBzb21lb25lIHVzaW5n
IGl0IHNob3VsZCBuZXZlciBoYXZlIHRvIGtub3cgdGhhdCBkZXRhaWwgb2YgdGhlIEFFUy1HQ00g
YWxnb3JpdGhtLg0KDQpFVlBfQ0lQSEVSX0NUWF9jdHJsKGN0eCwgRVZQX0NUUkxfR0NNX1NFVF9U
QUcsIDE2LCB0YWcpIHdoZXJlIHRhZyBpcyB0aGUgZmluYWwgMTYgYnl0ZXMgb2YgdGhlIGVuY3J5
cHRlZCBwYXlsb2FkLCBpZSAweDQzYjFjYTcwIGEyZDhkM2Y3IDI1ZWFkMTM5IDEzNzdkY2MwDQoN
CkVWUF9EZWNyeXB0RmluYWxfZXgoY3R4LCBkZWNyeXB0ZWRQYXlsb2FkICsgbGVuLCAmbGVuKQ0K
DQpFdmVyeXRoaW5nIHNlZW1zIE9LIHVudGlsIHRoZSBFVlBfRGVjcnlwdEZpbmFsX2V4KCkgY2Fs
bCB3aGljaCBmYWlscy4NCg0KSXMgdGhlcmUgYW55dGhpbmcgb2J2aW91c2x5IHdyb25nIHdpdGgg
dGhlIGFib3ZlPyAgSeKAmXZlIG5vdCBwb3N0ZWQgdGhlIGZ1bGwgc291cmNlIGNvZGUgYXMgSeKA
mW0gbm90IGFza2luZyBwZW9wbGUgdG8gY2hlY2sgbXkgd29ya2luZywgSeKAmW0gcmVhbGx5IGFz
a2luZyBpZiBteSBhc3N1bXB0aW9ucyBhcmUgY29ycmVjdCwgYW0gSSB1c2luZyB0aGUgY29ycmVj
dCBmdW5jdGlvbnMsIGlucHV0IGRhdGEgZXRjLg0KDQpUaGFua3MgaW4gYWR2YW5jZQ0KDQpUaW0N
Cg==

--_000_LO2P123MB2462F4CDAD99B8E3DAA39F9FF2780LO2P123MB2462GBRP_
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
by1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlm
Ow0KCWNvbG9yOndpbmRvd3RleHQ7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5
cGU6cGVyc29uYWwtY29tcG9zZTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsN
Cgljb2xvcjp3aW5kb3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4
cG9ydC1vbmx5Ow0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlmOw0KCW1zby1mYXJl
YXN0LWxhbmd1YWdlOkVOLVVTO30NCkBwYWdlIFdvcmRTZWN0aW9uMQ0KCXtzaXplOjYxMi4wcHQg
NzkyLjBwdDsNCgltYXJnaW46NzIuMHB0IDcyLjBwdCA3Mi4wcHQgNzIuMHB0O30NCmRpdi5Xb3Jk
U2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlvbjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBt
c28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVsdHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYi
IC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBl
bGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlkbWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0K
PC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2VuZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0i
RU4tR0IiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJwbGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rp
b24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5n
dWFnZTpFTi1VUyI+SGksPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwv
bzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZh
cmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPlVuZm9ydHVuYXRlbHkgSeKAmW0gc3RpbGwgaGF2aW5nIHBy
b2JsZW1zIHJlbW92aW5nIHBhY2tldCBwcm90ZWN0aW9uLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpF
Ti1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5BbHRob3VnaCBJIGNhbiBu
b3cgc3VjY2Vzc2Z1bGx5IHByb2Nlc3MgdGhlIHNhbXBsZSBwYWNrZXQgaW4gdGhlIGRyYWZ0IFJG
QyAodGhhbmtzIHRvIE5pY2spLCBteSBmaXJzdCBhdHRlbXB0IGF0IGEgY2FwdHVyZWQgcGFja2V0
IGlzIGZhaWxpbmcgKHVzaW5nIHRoZSBzYW1lIGNvZGUpLiZuYnNwOyBJIGNhbuKAmXQgc2VlIHdo
ZXJlIEnigJltIGdvaW5nIHdyb25nLiZuYnNwOw0KIEl04oCZcyB0aGUgaGVhZGVyIHByb3RlY3Rp
b24gcmVtb3ZhbCBJ4oCZbSBoYXZpbmcgcHJvYmxlbXMgd2l0aC48bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3Vh
Z2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+SWYgaXTigJlzIG5v
dCB0b28gbXVjaCB0byBhc2ssIHdvdWxkIGFueW9uZSBiZSBpbiBhIHBvc2l0aW9uIHRvIHByb2Nl
c3MgdGhlIGNsaWVudCBpbml0aWFsIHBhY2tldCBiZWxvdywgYW5kIGdpdmUgdGhlIGludGVybWVk
aWF0ZSB2YWx1ZXMgYWxvbmcgdGhlIGxpbmVzIG9mIHRob3NlIGdpdmVuIGluIGFwcGVuZGl4IEE/
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6
RU4tVVMiPlRoZSBwYWNrZXQgaXMgPG86cD4NCjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJtc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+dWludDhfdCBwcm90ZWN0ZWRfZnJhbWUxWzMw
Ml0gPQ0KPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj57MHhjOCwweGZmLDB4MDAsMHgwMCww
eDFiLDB4MTEsMHg3NiwweGY4LDB4MWEsMHg1NSwweDg4LDB4YjIsMHhmMiwweDVjLDB4NWEsMHhi
Niw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjB4ZGIsMHhkNCwweDYxLDB4YTgsMHhkNyww
eDQ5LDB4ZTEsMHgwMywweGM1LDB4ZWYsMHgwMiwweDAwLDB4NDEsMHgxMCwweGIwLDB4YmQsPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1z
by1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4weDE0LDB4MDQsMHhmNSwweDM1LDB4MTcsMHg3Ziww
eGNiLDB4Y2YsMHhkNSwweGYwLDB4NmQsMHgyNCwweGZmLDB4ZGUsMHg2NiwweGVkLDxvOnA+PC9v
OnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFy
ZWFzdC1sYW5ndWFnZTpFTi1VUyI+MHhmMSwweDBkLDB4ZjcsMHg5MiwweDA1LDB4NjYsMHg2Yiww
eDE4LDB4NTEsMHgxOCwweDlmLDB4NTQsMHhhMCwweDkyLDB4N2QsMHhmMiw8bzpwPjwvbzpwPjwv
c3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3Qt
bGFuZ3VhZ2U6RU4tVVMiPjB4MzAsMHhiNSwweGNiLDB4ZDcsMHhjOSwweDZkLDB4ZTYsMHhjNSww
eDc2LDB4ZTUsMHg1OSwweDQyLDB4MjMsMHgxZSwweGM4LDB4NTMsPG86cD48L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1
YWdlOkVOLVVTIj4weDlmLDB4ZjIsMHg4MiwweGUyLDB4Y2YsMHhkNywweDUzLDB4ODMsMHg4Yiww
eDEyLDB4NTMsMHhjZSwweDE5LDB4NWMsMHhkNiwweDMyLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4N
CjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpF
Ti1VUyI+MHgyMiwweDVkLDB4ZTAsMHhjYSwweDJlLDB4MzcsMHg0MiwweGMxLDB4ZGEsMHgwOCww
eDRkLDB4YTQsMHhkMSwweDE4LDB4YzcsMHg3NSw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMi
PjB4N2MsMHgzYywweGFlLDB4M2IsMHhmNiwweDk1LDB4YTIsMHhjNiwweDgzLDB4OTksMHg5Nyww
eDlmLDB4OTgsMHgwZCwweGRiLDB4YTYsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4weGE5
LDB4NzcsMHhiZCwweGJhLDB4MzEsMHgyMCwweGIyLDB4OGIsMHhlOCwweDBlLDB4MGIsMHhlOSww
eGUwLDB4ODksMHgzZiwweDA1LDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+MHg4ZCwweGRk
LDB4OGQsMHg3YiwweGUzLDB4OTAsMHhkZSwweGQ2LDB4NjgsMHg3OSwweDYyLDB4OGQsMHg0Nyww
eGI3LDB4NDcsMHg3OCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjB4MTcsMHg0ZSwweDll
LDB4NjUsMHg5MywweGNlLDB4ODEsMHgxNywweGJmLDB4NWYsMHg0YiwweDE2LDB4YjgsMHg4ZCww
eGUzLDB4NDgsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNw
YW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4weDRmLDB4OTcsMHg3ZSwweDIy
LDB4ZGUsMHhkOCwweDZlLDB4YjIsMHg5YiwweDAwLDB4YmQsMHhhNCwweGE0LDB4ZmIsMHg3NCww
eDljLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+MHhlZSwweDgzLDB4MjksMHhkNiwweGYx
LDB4MzIsMHhiMywweDkxLDB4YmIsMHg2ZSwweDlhLDB4OTMsMHg3MSwweDYxLDB4YzQsMHhkOSw8
bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0i
bXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjB4ZWIsMHgzMCwweDJmLDB4NDMsMHg3MywweDIw
LDB4ZTQsMHg3OCwweDI5LDB4ZmYsMHhlNywweDE5LDB4MTEsMHg5NywweGU4LDB4MzMsPG86cD48
L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1m
YXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4weGQ1LDB4NDcsMHhkMSwweDZlLDB4YzEsMHhkYywweDkx
LDB4MGYsMHhkNiwweGZlLDB4YWMsMHg2NCwweDk0LDB4OTksMHgwMCwweGI5LDxvOnA+PC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFz
dC1sYW5ndWFnZTpFTi1VUyI+MHg5MSwweDc5LDB4ZjYsMHgxYywweDExLDB4ODUsMHg0NCwweGQx
LDB4OWYsMHg1NiwweGJlLDB4M2YsMHg0ZiwweDUyLDB4YTcsMHgyYyw8bzpwPjwvbzpwPjwvc3Bh
bj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFu
Z3VhZ2U6RU4tVVMiPjB4NTIsMHgzZCwweDJiLDB4NDEsMHhlMCwweDQyLDB4YTcsMHg0YywweGJj
LDB4MzEsMHhkNCwweGIzLDB4YTQsMHg1NSwweGRlLDB4Y2UsPG86cD48L286cD48L3NwYW4+PC9w
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdl
OkVOLVVTIj4weDBjLDB4YmUsMHg5ZCwweDI5LDB4NTksMHhkZiwweGY4LDB4ZmIsMHg1MywweDBj
LDB4NjQsMHgyZSwweGI1LDB4MmQsMHhhNCwweDNkLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1V
UyI+MHhlYSwweGY5LDB4OTAsMHg4YywweDFiLDB4MGIsMHhkNSwweDBkLDB4NDQsMHg1OSwweGUw
LDB4ZTQsMHg3NCwweDg1fTs8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+Jm5ic3A7
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxiPjxzcGFuIGxhbmc9IkVO
LVVTIj5Gcm9tOjwvc3Bhbj48L2I+PHNwYW4gbGFuZz0iRU4tVVMiPiBOaWNrIEhhcnBlciAmbHQ7
bmhhcnBlckBnb29nbGUuY29tJmd0Ow0KPGJyPg0KPGI+U2VudDo8L2I+IDE0IEp1bHkgMjAyMCAx
OTo0Nzxicj4NCjxiPlRvOjwvYj4gSmViYixUUixUaW0sVklFIFIgJmx0O3RpbS5qZWJiQGJ0LmNv
bSZndDs8YnI+DQo8Yj5DYzo8L2I+IElFVEYgUVVJQyBXRyAmbHQ7cXVpY0BpZXRmLm9yZyZndDs8
YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFByb2JsZW1zIHZlcmlmeWluZyBzYW1wbGUgcGFja2V0
IHByb3RlY3Rpb24gaW4gYXBwZW5kaXggQSBvZiBVc2luZyBUTFMgdG8gU2VjdXJlIFFVSUM8bzpw
PjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpw
PjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286
cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9w
Pg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5PbiBUdWUsIEp1bCAxNCwgMjAy
MCBhdCA5OjA2IEFNICZsdDs8YSBocmVmPSJtYWlsdG86dGltLmplYmJAYnQuY29tIj50aW0uamVi
YkBidC5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVv
dGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFk
ZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNt
Ij4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5IaSwNCjxvOnA+PC9vOnA+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRv
O21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNs
YXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2lu
LWJvdHRvbS1hbHQ6YXV0byI+SeKAmW0gd29ya2luZyB0aHJvdWdoIEFwcGVuZGl4IEEgb2YgdGhl
IFFVSUMgVExTIGRvYyB0byBjaGVjayBteSB1bmRlcnN0YW5kaW5nLCBidXQgYW0gaGF2aW5nIHRy
b3VibGUgZGVjcnlwdGluZyB0aGUgc2FtcGxlIGNsaWVudCBpbml0aWFsIHBhY2tldC4mbmJzcDsg
SeKAmW0gdW5zdXJlIGlmIEnigJl2ZSBtYWRlIGEgc2lsbHkNCiBlcnJvciBvciB0d28sIG9yIGlm
IEnigJl2ZSBtYWRlIG9uZSBvciBtb3JlIGluY29ycmVjdCBhc3N1bXB0aW9ucy4mbmJzcDsgT3Ig
Ym90aC48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPlRoZSBmdW5jdGlvbnMgSeKAmW0gdXNp
bmcgYXJlIHRoZSBPcGVuU1NMIEVWUCBvbmVzLiZuYnNwOyBJ4oCZbSBhdHRlbXB0aW5nIHRvIGZv
bGxvdyB0aGUgcmVjaXBlIGhlcmU6PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
IiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1
dG8iPjxhIGhyZWY9Imh0dHBzOi8vd2lraS5vcGVuc3NsLm9yZy9pbmRleC5waHAvRVZQX0F1dGhl
bnRpY2F0ZWRfRW5jcnlwdGlvbl9hbmRfRGVjcnlwdGlvbiNBdXRoZW50aWNhdGVkX0RlY3J5cHRp
b25fdXNpbmdfR0NNX21vZGUiIHRhcmdldD0iX2JsYW5rIj5odHRwczovL3dpa2kub3BlbnNzbC5v
cmcvaW5kZXgucGhwL0VWUF9BdXRoZW50aWNhdGVkX0VuY3J5cHRpb25fYW5kX0RlY3J5cHRpb24j
QXV0aGVudGljYXRlZF9EZWNyeXB0aW9uX3VzaW5nX0dDTV9tb2RlPC9hPg0KIGluIGNvbmp1bmN0
aW9uIHdpdGggdGhlIGRyYWZ0IFJGQy48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6
YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0i
bXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNw
OzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5FVlBfQ0lQSEVSX0NUWF9u
ZXcoKTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJn
aW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwv
bzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6
YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+RVZQX0RlY3J5cHRJbml0X2V4KGN0eCwg
RVZQX2Flc18xMjhfZ2NtKCksIE5VTEwsIE5VTEwsIE5VTEwpPG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdp
bi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFs
dDphdXRvIj5FVlBfRGVjcnlwdEluaXRfZXgoY3R4LCBOVUxMLCBOVUxMLCBjbGllbnRfa2V5LCBp
dikgJm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7Jm5ic3A7IHdoZXJlIHRoZSBj
bGllbnQga2V5IGlzIDB4MTc1MjU3YTMxZWIwOWRlYTkzNjZkOGJiNzlhZDgwYmEgYW5kIHRoZSBp
diBpcyAweDZiMjYxMTRiOWNiYTJiNjNhOWU4ZGQ0ZjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8
L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZu
YnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPllvdSBu
ZWVkIHRvIGNvbXB1dGUgdGhlIG5vbmNlIGZyb20gdGhlIElWIGFuZCB0aGUgcGFja2V0IG51bWJl
ci4gSSBhc3N1bWUgd2hhdCB0aGUgb3BlbnNzbCBkb2N1bWVudGF0aW9uIHJlZmVycyB0byBhcyBh
biBJViBpcyBhY3R1YWxseSB0aGUgbm9uY2UgYXMgZGVzY3JpYmVkIGluIFJGQyA1MTE2LjxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7Ym9yZGVy
LWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0O21hcmdp
bi1sZWZ0OjQuOHB0O21hcmdpbi1yaWdodDowY20iPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0
b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij5FVlBfRGVjcnlwdFVwZGF0ZShjdHgsIE5VTEwsICZhbXA7bGVuLCBwVW5wcm90ZWN0ZWRIZWFk
ZXIsIGhlYWRlckxlbmd0aCkmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJzcDsmbmJz
cDsmbmJzcDsmbmJzcDsmbmJzcDsgd2hlcmUgdGhlIHVucHJvdGVjdGVkIGhlYWRlciBpcyAweGMz
ZmYwMDAwMWQwODgzOTRjOGYwM2U1MTU3MDgwMDAwNDQ5ZTAwMDAwMDAyIOKAkyB0aGlzIEkgYmVs
aWV2ZSBpcw0KIHRoZSBBZGRpdGlvbmFsIERhdGEgcmVxdWlyZWQ8bzpwPjwvbzpwPjwvcD4NCjxw
IGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFy
Z2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20t
YWx0OmF1dG8iPkVWUF9EZWNyeXB0VXBkYXRlKGN0eCwgZGVjcnlwdGVkUGF5bG9hZCwgJmFtcDts
ZW4sIHBQYXlsb2FkLCBwYXlsb2FkTGVuZ3RoLTE2KSkmbmJzcDsmbmJzcDsgaGVyZSBJ4oCZbSBw
YXNzaW5nIGluIHRoZSBlbmNyeXB0ZWQgcGF5bG9hZCBiZWdpbm5pbmcgMHhmYjY2YmM1ZiBhbmQg
ZW5kaW5nIDB4ZTgyYTRkOTE5ZDQ4LCBsZW5ndGggMTE2Mi4mbmJzcDsNCiBJ4oCZbSBhc3N1bWlu
ZyB0aGF0IHRoZSBmaW5hbCAxNiBieXRlcyBvZiB0aGUgcGF5bG9hZCBpcyB0aGUgYXV0aGVudGlj
YXRpb24gdGFnIHNvIGFtIG5vdCBwYXNzaW5nIGl0IGluIGhlcmUuJm5ic3A7IE5vdGUgdGhhdCBp
ZiB0aGlzIGFzc3VtcHRpb24gYWJvdXQgdGhlIGF1dGhlbnRpY2F0aW9uIHRhZyBpcyBjb3JyZWN0
LCBJIHRoaW5rIGl0IGNvdWxkIGJlIG1vcmUgY2xlYXJseSBzdGF0ZWQgaW4gdGhlIGRyYWZ0IFJG
Qy48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5UaGlzIGlzIGEgcXVpcmsgb2YgdGhlIG9wZW5zc2wgQVBJ
IHVuZm9ydHVuYXRlbHkuIEFuIEFFQUQgZGVjcnlwdGlvbiBvcGVyYXRpb24gc2hvdWxkIHRha2Ug
NCBpbnB1dHM6IHRoZSBrZXksIHRoZSBub25jZSwgdGhlIGFzc29jaWF0ZWQgZGF0YSwgYW5kIHRo
ZSBjaXBoZXJ0ZXh0LiBUaGUgY2lwaGVydGV4dCwgYXMgZGVmaW5lZCBieSBSRkMgNTExNiwgaW5j
bHVkZXMgdGhlIHRhZy4gVGhlcmUncyBubyByZXF1aXJlbWVudA0KIG9uIHRoZSBzdHJ1Y3R1cmUg
b2YgYW4gQUVBRCdzIGNpcGhlcnRleHQsIGluY2x1ZGluZyB0aGF0IHNvbWUgcG9ydGlvbiBvZiB0
aGUgY2lwaGVydGV4dCBiZSBhYmxlIHRvIGJlIGlkZW50aWZpZWQgYXMgYSB0YWcuIEFFUy1HQ00g
ZG9lcyBoYXZlIHRoaXMgc3RydWN0dXJlIHdoZXJlIHRoZSB0YWcgaXMgYXQgdGhlIGVuZCBvZiB0
aGUgY2lwaGVydGV4dCwgYW5kIHVuZm9ydHVuYXRlbHkgb3BlbnNzbCBtYWtlcyB0aGF0IHBhcnQg
b2YgdGhlIGFwaQ0KIGZvciB0aGUgQUVBRCBvcGVuIG9wZXJhdGlvbiwgZXZlbiB0aG91Z2ggc29t
ZW9uZSB1c2luZyBpdCBzaG91bGQgbmV2ZXIgaGF2ZSB0byBrbm93IHRoYXQgZGV0YWlsIG9mIHRo
ZSBBRVMtR0NNIGFsZ29yaXRobS48bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUg
c3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGlu
ZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0LjhwdDttYXJnaW4tcmlnaHQ6MGNtIj4N
CjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9w
LWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+RVZQX0NJUEhFUl9DVFhfY3RybChjdHgsIEVWUF9D
VFJMX0dDTV9TRVRfVEFHLCAxNiwgdGFnKSB3aGVyZSB0YWcgaXMgdGhlIGZpbmFsIDE2IGJ5dGVz
IG9mIHRoZSBlbmNyeXB0ZWQgcGF5bG9hZCwgaWUgMHg0M2IxY2E3MCBhMmQ4ZDNmNyAyNWVhZDEz
OSAxMzc3ZGNjMDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1z
by1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8
bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRv
cC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+RVZQX0RlY3J5cHRGaW5hbF9l
eChjdHgsIGRlY3J5cHRlZFBheWxvYWQgJiM0MzsgbGVuLCAmYW1wO2xlbik8bzpwPjwvbzpwPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bztt
c28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFz
cz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1i
b3R0b20tYWx0OmF1dG8iPkV2ZXJ5dGhpbmcgc2VlbXMgT0sgdW50aWwgdGhlIEVWUF9EZWNyeXB0
RmluYWxfZXgoKSBjYWxsIHdoaWNoIGZhaWxzLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
SXMgdGhlcmUgYW55dGhpbmcgb2J2aW91c2x5IHdyb25nIHdpdGggdGhlIGFib3ZlPyZuYnNwOyBJ
4oCZdmUgbm90IHBvc3RlZCB0aGUgZnVsbCBzb3VyY2UgY29kZSBhcyBJ4oCZbSBub3QgYXNraW5n
IHBlb3BsZSB0byBjaGVjayBteSB3b3JraW5nLCBJ4oCZbSByZWFsbHkgYXNraW5nIGlmIG15IGFz
c3VtcHRpb25zIGFyZSBjb3JyZWN0LA0KIGFtIEkgdXNpbmcgdGhlIGNvcnJlY3QgZnVuY3Rpb25z
LCBpbnB1dCBkYXRhIGV0Yy48bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPlRoYW5rcyBpbiBh
ZHZhbmNlPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5UaW08bzpwPjwvbzpwPjwvcD4NCjwv
ZGl2Pg0KPC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8L2Rpdj4NCjwvZGl2Pg0KPC9kaXY+DQo8L2Jv
ZHk+DQo8L2h0bWw+DQo=

--_000_LO2P123MB2462F4CDAD99B8E3DAA39F9FF2780LO2P123MB2462GBRP_--


From nobody Tue Jul 21 10:02:58 2020
Return-Path: <paul@redbarn.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 152683A0C1C for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 10:02:57 -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, 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 HxJIYtCayWF1 for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 10:02:55 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [24.104.150.213]) (using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 977E43A0C17 for <quic@ietf.org>; Tue, 21 Jul 2020 10:02:55 -0700 (PDT)
Received: from linux-9daj.localnet (dhcp-183.access.rits.tisf.net [24.104.150.183]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (1024 bits) server-digest SHA256) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 713B8C3F16 for <quic@ietf.org>; Tue, 21 Jul 2020 17:02:55 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: quic@ietf.org
Subject: Re: Small size of core QUIC library to replace TCP for embedded system
Date: Tue, 21 Jul 2020 17:02:54 +0000
Message-ID: <2499749.AO4zfZtjs8@linux-9daj>
Organization: none
In-Reply-To: <CAA=hcWQ60GH2TnjvqBEGvVQ1whxNYwEWjQ+b9FW948GKvN570Q@mail.gmail.com>
References: <CAA=hcWS0V8ipsoAEFK3ejdA++Vzi+czth37=ntP4mnt8d=mtRg@mail.gmail.com> <F384B33C-70F8-45EF-AB5C-30D0A145659A@eggert.org> <CAA=hcWQ60GH2TnjvqBEGvVQ1whxNYwEWjQ+b9FW948GKvN570Q@mail.gmail.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/nuhCas8szvz1w-6z-43A7aoJCxQ>
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, 21 Jul 2020 17:02:57 -0000

On Tuesday, 21 July 2020 10:56:22 UTC Jupiter wrote:
> Hi Lars,
> 
> On 7/21/20, Lars Eggert <lars@eggert.org> wrote:
> > ...
> > https://github.com/quicwg/base-drafts/wiki/Implementations)
> > ...
> 
> Sorry for not being clear, I should say Linux embedded system at the
> beginning. Although I would say the time for embedded systems with 8M
> Flash and 64KRAM has been long gone :-), I still have to manage the
> resources for meaning full network stacks and applications.

i realize that this has been declared off-topic, but you've raised a question 
that your /quicwg/ URI above does not answer.

for privilege separation reasons, sockets have been kernel objects. this has 
facilitated logging and filtering for regulatory, policy, ad-blocking, malware 
filtering, and so on. user mode code has not historically been able to form a 
connection without a "connect" system call, where policy could be enforced by 
the kernel. as an example, "raw" sockets necessary to implement user-mode TCP 
have historically been restricted to processes running with elevated 
privilege.

in some environments this will be an invariant, and UDP sockets will be made 
to require elevated privileges, precisely so as to give the kernel a chance to 
log and filter connection attempts according to local policy. in that 
environment, a kernel-resident QUIC implementation will be needed, so that 
something like a "connect" system call can still exist. i do not expect this 
to save memory, because shared libraries are equal in size to kernel modules. 
but as a place to put an ad-blocker or other edge-device connection policy, a 
kernel-resident QUIC implementation is going to be required in some places.

my question is, has any QUIC implementor been thinking along these lines? i 
believe that the parameters to a QUIC "connect" syscall would be larger and 
more numerous than for a TCP or SCTP or UDP "connect" syscall, for example.

-- 
Paul



From nobody Tue Jul 21 12:38:24 2020
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 443363A0855 for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 12:38:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 2.903
X-Spam-Level: **
X-Spam-Status: No, score=2.903 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, GB_SUMOF=5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, 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 2e5E1Fi7I_bJ for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 12:38:22 -0700 (PDT)
Received: from mail-lf1-x12b.google.com (mail-lf1-x12b.google.com [IPv6:2a00:1450:4864:20::12b]) (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 C09C23A0857 for <quic@ietf.org>; Tue, 21 Jul 2020 12:38:21 -0700 (PDT)
Received: by mail-lf1-x12b.google.com with SMTP id i19so7086631lfj.8 for <quic@ietf.org>; Tue, 21 Jul 2020 12:38:21 -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=ufy48TZdejYI6QP6bv2QcaOxprhlmyCoHm6n9TRLSNw=; b=VrtF74Xp3O2SUqOMWnfb0NOGsGnS9mateI4zCU7z8ElBeS1XUKCaJmj7/7F4V6ijB9 6UegWCKhlJiArUncuHbmEJuNNXEvQkUJh4MIMlxY0Zg+mJ+ZgWaIzmxKFFW0LpD4TwmF 28PQ6PArh6wPtlDC+M39y602Rsr2mX66OUrT0re0Hew2xhQXTfdkaDKLHfxX34vFbXzV JhWeT2cp9XyHLAU/jYgXZna6z0MhiCdQc9IbyOpUYpg0E95dleQDLpAIS2JaIhQmc3bJ rBsqOStcgJeOClVUMMTJUeqwZMiOkhYnY6WTV7emLgrMHf7p7+Wbuc4xgye1pSRpxRQu TMOg==
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=ufy48TZdejYI6QP6bv2QcaOxprhlmyCoHm6n9TRLSNw=; b=aYfDmJ3UVyPSwZ3v9WdsDWHoMHP9mNNQfmVaTymYXSZKV+bud6fD4iaGdIAOaXYMLn 2LPjgSqZWfqfT1NpTi5SwdLPogm4QKY4sD8saX9CnxjImayx9hnPf1TrDjEHw3Bu8VMb 5m7ytfHf+UuwP46dqtlm4NIbFlMGRPz44wr7I336fpUeHNJgBuFPMyrqQ8ONCjQnhGFd UW1NZQho3sN6bSU6Aa1ap88r+Fmx0yrjLTFOlr4aHuskg7jdmCXZh/E6jnv+bp6rESAA XxQWwVgue92JCwJ/SRCoL1lJcgT3eCgvG+jx/tZ5jwGP+eIc0sNd9uT/XpsAG4xuvQvi f0IQ==
X-Gm-Message-State: AOAM532wS1JzQjdysc7Miot1SEwz/ouIhgfKR8wkunpUgEj7JeHo1vGN +Qpl0ZiBxkcaXI4UncgWFrOwSsUhq5IiUF14bPs=
X-Google-Smtp-Source: ABdhPJzvYxb8n3IlLMLAyxKUWbx4APATEGUzmsIWVssOcJNnIPjho3wsBnfXYCSSnmW2+hARI4HaR7LWGUzicVqdx6A=
X-Received: by 2002:ac2:4c09:: with SMTP id t9mr14172451lfq.34.1595360299819;  Tue, 21 Jul 2020 12:38:19 -0700 (PDT)
MIME-Version: 1.0
References: <CACpbDcctB0nX2yTxHQEs6UcUCTH0WdfiNAPfpRKe3oH-0aYZYA@mail.gmail.com> <28d46380-620a-4448-b471-403048e0117e@www.fastmail.com> <CACpbDcf0i0fEnD3VeLx=dW8hZNf1esDPy8P6v3UD+Y9Gh6b2Dg@mail.gmail.com> <CAOYVs2rw4txSQw+dMkMKAw_E_REpXeUfrHj4-nvkhQOR=509Og@mail.gmail.com>
In-Reply-To: <CAOYVs2rw4txSQw+dMkMKAw_E_REpXeUfrHj4-nvkhQOR=509Og@mail.gmail.com>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Tue, 21 Jul 2020 12:38:08 -0700
Message-ID: <CACpbDccyQV1gdaXkKaWkTkDck7-zZ+9kXtdw=5KNEUXNaTwbqg@mail.gmail.com>
Subject: Re: Handshake processing delays and impact on recovery
To: Marten Seemann <martenseemann@gmail.com>
Cc: Martin Thomson <mt@lowentropy.net>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000f5a9a905aaf8c37f"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Xj6HbhiOE-vqjUOXu60qg13hMN8>
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, 21 Jul 2020 19:38:23 -0000

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

On Mon, Jul 20, 2020 at 10:07 PM Marten Seemann <martenseemann@gmail.com>
wrote:

> > To solve the second problem, the proposal is to use ack_delay as
> reported by the endpoint that buffers the data appropriately. ack_delay is
> the amount of the time the information (regardless of that being the packet
> itself or the acknowledgement) being buffered intentionally. For this, we
> need the following:
> > - endpoints MUST report an ack_delay that is the sum of the controlled
> delay (i.e. the duration of the data and the ack being buffered)
> > - endpoints ignore max_ack_delay for acknowledgements of packets that
> were sent prior to handshake confirmation. Those are the ones that might
> have been buffered at the peer until keys were ready.
>
> It took me a while to convince myself that this is ok. The danger I saw
> here is that an adversarial endpoint might misreport the ack_delay to trick
> the peer into coming up with an RTT estimate that's significantly shorter
> than the actual RTT.
> The reason why this attack doesn't work is that the only variables that
> make use of the ack_delay are smoothed_rtt and rttvar. Specifically,
> latest_rtt is just the difference between sending the packet and receipt of
> the acknowledgment, and min_rtt is the minimum value of all latest_rtt
> values measured. The ack_delay is only applied to the measurement of
> smoothed_rtt if it doesn't lower the value below min_rtt.
> Consequently, this means that a server reporting an ack_delay in the ACK
> for the ClientHello won't have any effect.
>

Yes, thanks for noting this, Marten. That protection is exactly the point
of using only observed values for min_rtt -- the peer cannot reduce that
value below what is observed.

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

<div dir=3D"ltr"><div dir=3D"ltr">On Mon, Jul 20, 2020 at 10:07 PM Marten S=
eemann &lt;<a href=3D"mailto:martenseemann@gmail.com">martenseemann@gmail.c=
om</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(20=
4,204,204);padding-left:1ex"><div dir=3D"ltr">&gt; To solve the second prob=
lem, the proposal is to use ack_delay as reported by the endpoint that buff=
ers the data appropriately. ack_delay is the amount of the time the informa=
tion (regardless of that being the packet itself or the acknowledgement) be=
ing buffered intentionally. For this, we need the following:<br>&gt; - endp=
oints MUST report an ack_delay that is the sum of the controlled delay (i.e=
. the duration of the data and the ack being buffered)<br><div>&gt; - endpo=
ints ignore max_ack_delay for acknowledgements of packets that were sent pr=
ior to handshake confirmation. Those are the ones that might have been buff=
ered at the peer until keys were ready.</div><div><br></div><div>It took me=
 a while to convince myself that this is ok. The danger I saw here is that =
an adversarial endpoint might misreport the ack_delay to trick the peer int=
o coming up with an RTT estimate that&#39;s significantly shorter than the =
actual RTT.</div><div>The reason why this attack doesn&#39;t work is that t=
he only variables that make use of the ack_delay are smoothed_rtt and rttva=
r. Specifically, latest_rtt is just the difference between sending the pack=
et and receipt of the acknowledgment, and min_rtt is the minimum value of a=
ll latest_rtt values measured. The ack_delay is only applied to the measure=
ment of smoothed_rtt if it doesn&#39;t lower the value below min_rtt.</div>=
<div>Consequently, this means that a server reporting an ack_delay in the A=
CK for the ClientHello won&#39;t have any effect.</div></div></blockquote><=
div><br></div><div>Yes, thanks for noting this, Marten. That protection is =
exactly the point of using only observed values for min_rtt -- the peer can=
not reduce that value below what is observed.</div></div></div>

--000000000000f5a9a905aaf8c37f--


From nobody Tue Jul 21 15:19:35 2020
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 AA2333A0B2A for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 15:19:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -12.6
X-Spam-Level: 
X-Spam-Status: No, score=-12.6 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, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, GB_SUMOF=5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=no 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 198kw4WfB8kk for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 15:19:32 -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 682563A0B27 for <quic@ietf.org>; Tue, 21 Jul 2020 15:19:32 -0700 (PDT)
Received: by mail-yb1-xb2a.google.com with SMTP id x138so10754494ybg.9 for <quic@ietf.org>; Tue, 21 Jul 2020 15:19:32 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=/zZ3kI+C+TSCRQ0AfnXhWKqPFtS6N9QRn7Mc5h5KI+Q=; b=d01OmXt60hVT6Z+VeUAeW+PgR5ysbo/pOrKGGhTnbrnCXpDei2ZVMLj+KlJKFIKZP2 cKS/J5ANa4/S86XDludNweE7DmUqA3TSgYZL6lQk9CpJ1SS7pbxHBM0LaEIXXsrEFCA3 hn5tcJWaZagKYWmguAXDXZXTF8wDfiCuNMoJjJN7eRgLtXRyrK7Zj9Qms7rBy/CVUnXF /urDlMTA3FQy9COnbmCBBDi9PN4mG0Jhv8SDk65mCTlT53SQxgEjFpfCc5sML1iMNCrn 2kkupFqxUWIeHpdcG7l2gbRGKuEnhYBJO7F56Yidokuwb74Mp7r9ytIUEOTthtIJgcxC Vq0w==
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=/zZ3kI+C+TSCRQ0AfnXhWKqPFtS6N9QRn7Mc5h5KI+Q=; b=oqVxjVNTp6m/29l6FD8dZp7XdOJtfYhHYexXuFc8BLlv87x0oLHaUYVGqB5EwPAJXS lIz1RlFYmg3ofq5EEJJi7XIXl6/c5ZH2GvO8cKOBMOvt/+h9rFbmAYZ2sVdnCKYac/52 qdkLbWLea+Up5YfK4K4ld8PfzRIozwPKcaVRP5xWb3p4+ifGP/pSbVC4knN/qGSpYeQl SQzOhy2MT6I77YO5ZEr7gz3rkoZY+v1VnVADsvZ0U24maWqd7NAs2sxEFW03/e19nGCw vmXJCuIHrycFMPjiQorV3T5PyywEHovaO6M07G1+8BX//8IIViEpY/8bT8xzgofrEsfC +9uQ==
X-Gm-Message-State: AOAM530Bao5WK4pJ3worw28eKDMhcp4QRvjBLNvwb5ggfqsQ3jC1zLrD aNu29AZ1RU3sYwYLLfZ46AwdXBzuuzXr/tqYDdnNcA==
X-Google-Smtp-Source: ABdhPJyYoHxDaWurjmaRlHd/uhPurhvM9T1714JqNYU2ou9t5k+G65CaonUwkQ3qTkZXPcepouRkzTn60Gt2TOyUbT0=
X-Received: by 2002:a25:ba8c:: with SMTP id s12mr43395603ybg.278.1595369971299;  Tue, 21 Jul 2020 15:19:31 -0700 (PDT)
MIME-Version: 1.0
References: <CACpbDcctB0nX2yTxHQEs6UcUCTH0WdfiNAPfpRKe3oH-0aYZYA@mail.gmail.com> <28d46380-620a-4448-b471-403048e0117e@www.fastmail.com> <CACpbDcf0i0fEnD3VeLx=dW8hZNf1esDPy8P6v3UD+Y9Gh6b2Dg@mail.gmail.com> <CAOYVs2rw4txSQw+dMkMKAw_E_REpXeUfrHj4-nvkhQOR=509Og@mail.gmail.com> <CACpbDccyQV1gdaXkKaWkTkDck7-zZ+9kXtdw=5KNEUXNaTwbqg@mail.gmail.com>
In-Reply-To: <CACpbDccyQV1gdaXkKaWkTkDck7-zZ+9kXtdw=5KNEUXNaTwbqg@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Tue, 21 Jul 2020 18:19:19 -0400
Message-ID: <CAKcm_gNEXUVqnK8LY_DF6DNZ419oysrE_0+DzdyD6243c4QiwQ@mail.gmail.com>
Subject: Re: Handshake processing delays and impact on recovery
To: Jana Iyengar <jri.ietf@gmail.com>
Cc: Marten Seemann <martenseemann@gmail.com>, QUIC WG <quic@ietf.org>,  Martin Thomson <mt@lowentropy.net>
Content-Type: multipart/alternative; boundary="0000000000006d2b3705aafb049c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/iWOk5sltJ0uy11nolowEC6v3too>
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, 21 Jul 2020 22:19:34 -0000

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

I'm not in love with us relying so strongly on HANDSHAKE_DONE, but I think
it works as intended.

One suggestion I'd make is to keep the SHOULD around coalescing Handshake
and 1-RTT packets when PTO is armed, even if it's prior to handshake
confirmed.  That can be worked out on the PR.

On Tue, Jul 21, 2020 at 3:38 PM Jana Iyengar <jri.ietf@gmail.com> wrote:

> On Mon, Jul 20, 2020 at 10:07 PM Marten Seemann <martenseemann@gmail.com>
> wrote:
>
>> > To solve the second problem, the proposal is to use ack_delay as
>> reported by the endpoint that buffers the data appropriately. ack_delay is
>> the amount of the time the information (regardless of that being the packet
>> itself or the acknowledgement) being buffered intentionally. For this, we
>> need the following:
>> > - endpoints MUST report an ack_delay that is the sum of the controlled
>> delay (i.e.. the duration of the data and the ack being buffered)
>> > - endpoints ignore max_ack_delay for acknowledgements of packets that
>> were sent prior to handshake confirmation. Those are the ones that might
>> have been buffered at the peer until keys were ready.
>>
>> It took me a while to convince myself that this is ok. The danger I saw
>> here is that an adversarial endpoint might misreport the ack_delay to trick
>> the peer into coming up with an RTT estimate that's significantly shorter
>> than the actual RTT.
>> The reason why this attack doesn't work is that the only variables that
>> make use of the ack_delay are smoothed_rtt and rttvar. Specifically,
>> latest_rtt is just the difference between sending the packet and receipt of
>> the acknowledgment, and min_rtt is the minimum value of all latest_rtt
>> values measured. The ack_delay is only applied to the measurement of
>> smoothed_rtt if it doesn't lower the value below min_rtt.
>> Consequently, this means that a server reporting an ack_delay in the ACK
>> for the ClientHello won't have any effect.
>>
>
> Yes, thanks for noting this, Marten. That protection is exactly the point
> of using only observed values for min_rtt -- the peer cannot reduce that
> value below what is observed.
>

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

<div dir=3D"ltr">I&#39;m not in love with us relying so strongly on HANDSHA=
KE_DONE, but I think it works as intended.<div><br></div><div>One suggestio=
n I&#39;d make is to keep the SHOULD around coalescing Handshake and 1-RTT =
packets when PTO is armed, even if it&#39;s prior to handshake confirmed.=
=C2=A0 That can be worked out on the PR.</div></div><br><div class=3D"gmail=
_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Tue, Jul 21, 2020 at 3:38 =
PM Jana Iyengar &lt;<a href=3D"mailto:jri.ietf@gmail.com">jri.ietf@gmail.co=
m</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"><div dir=3D"ltr">On Mon, Jul 20, 2020 at 10:07 PM Marten =
Seemann &lt;<a href=3D"mailto:martenseemann@gmail.com" target=3D"_blank">ma=
rtenseemann@gmail.com</a>&gt; wrote:<br></div><div class=3D"gmail_quote"><b=
lockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-le=
ft:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr">&gt; To so=
lve the second problem, the proposal is to use ack_delay as reported by the=
 endpoint that buffers the data appropriately. ack_delay is the amount of t=
he time the information (regardless of that being the packet itself or the =
acknowledgement) being buffered intentionally. For this, we need the follow=
ing:<br>&gt; - endpoints MUST report an ack_delay that is the sum of the co=
ntrolled delay (i.e.. the duration of the data and the ack being buffered)<=
br><div>&gt; - endpoints ignore max_ack_delay for acknowledgements of packe=
ts that were sent prior to handshake confirmation. Those are the ones that =
might have been buffered at the peer until keys were ready.</div><div><br><=
/div><div>It took me a while to convince myself that this is ok. The danger=
 I saw here is that an adversarial endpoint might misreport the ack_delay t=
o trick the peer into coming up with an RTT estimate that&#39;s significant=
ly shorter than the actual RTT.</div><div>The reason why this attack doesn&=
#39;t work is that the only variables that make use of the ack_delay are sm=
oothed_rtt and rttvar. Specifically, latest_rtt is just the difference betw=
een sending the packet and receipt of the acknowledgment, and min_rtt is th=
e minimum value of all latest_rtt values measured. The ack_delay is only ap=
plied to the measurement of smoothed_rtt if it doesn&#39;t lower the value =
below min_rtt.</div><div>Consequently, this means that a server reporting a=
n ack_delay in the ACK for the ClientHello won&#39;t have any effect.</div>=
</div></blockquote><div><br></div><div>Yes, thanks for noting this, Marten.=
 That protection is exactly the point of using only observed values for min=
_rtt -- the peer cannot reduce that value below what is observed.</div></di=
v></div>
</blockquote></div>

--0000000000006d2b3705aafb049c--


From nobody Tue Jul 21 19:00:25 2020
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 EED793A0839 for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 19:00:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level: 
X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 4P89fXNzG_Jy for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 19:00:22 -0700 (PDT)
Received: from mail-wm1-x32d.google.com (mail-wm1-x32d.google.com [IPv6:2a00:1450:4864:20::32d]) (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 539CE3A0838 for <quic@ietf.org>; Tue, 21 Jul 2020 19:00:22 -0700 (PDT)
Received: by mail-wm1-x32d.google.com with SMTP id w3so437803wmi.4 for <quic@ietf.org>; Tue, 21 Jul 2020 19:00:22 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to:cc; bh=ehrAE4fKXZ5r3G04gOOAMx+iY1GZMnyvlai7H5rRDW0=; b=qm4kx9Rh8EBi8GNBjm/DQ14tNPTcDYvpvt4ZwSiW6dO44OTqkmnF1HcMvCv1uQ5hRF 9nZXXpr3cdwDYtRYzVYrLrXWnXHOKnlVp5B7JEaZOxMGohhbPhyoN9zQ+qHYQ8d/NcDL zGdOhyDBNkOUUKyvQ5gyfs6wnrWAPry3meqIUwStJgVAYy/Xk4/Ku7QEkmK9prcvpcYc xNNZBIaO/zN8JhQzQnV/AVt3EFavJ7Z8DQvqNIW0VgWClx6mOTNKdsRmboB/4PIyzMfL mTOtUmOPYAY3U2jjjb6DgfGgwVd6XLNbngCkLHQF83xGa2sGGIKIhlt02FDCJSgj8WxU Za2A==
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=ehrAE4fKXZ5r3G04gOOAMx+iY1GZMnyvlai7H5rRDW0=; b=ATSJQV+lwE3Lj6eQ3ZjBqUvvmbBhdNgSzqhqHw8Ezilea3dOpcO9zd7gLvYnMGbQOB de94U2GnL62Vcam0fq4gqHCNMUrCT4lFDWrNMXw6KE6hLiPK+hkyJtZ4FyY7qPlexVTP cqKTMtXlp4KDK00j+paprAx8qety9eYQ7OqWm9WCKP2cEnwvFZM4vtO/DE1TvE+FUcNK JMCrhwnEpsuqpgTQpqJxMhIg5/+3HyFEdQ/XVYc4S+wFCy2QtAAMMkQI6jXAG++oFJrR 23UV0CbHE1qJ0g2pgoA2zVQjRqgWxI1X3B1EQU7lEw4aINExfwd3x2nkxhEiSf7Pd/YA eLuQ==
X-Gm-Message-State: AOAM531wgM0hrwWqdpbZq9Vd9k04YYjRP+9RyIWIgdWQYKCDrhyW/gB9 rRDXBsiFuhbN/8KyWuqfcyISEmgkbzSKl+/li+/5g9OYjos=
X-Google-Smtp-Source: ABdhPJwMk4o823O3shAh7h9CiORXHhyohbRBzQv8Cmw7wsIbRd82XWJvrpitJPoxCLUN3q+pdawvezAE9smtzPJ+7js=
X-Received: by 2002:a1c:750a:: with SMTP id o10mr6654897wmc.165.1595383220351;  Tue, 21 Jul 2020 19:00:20 -0700 (PDT)
MIME-Version: 1.0
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Wed, 22 Jul 2020 03:00:09 +0100
Message-ID: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com>
Subject: Consensus call for Late-Stage documents, pre-IETF 108 edition
To: QUIC WG <quic@ietf.org>
Cc: Lars Eggert <lars@eggert.org>, Mark Nottingham <mnot@mnot.net>
Content-Type: multipart/alternative; boundary="00000000000021371905aafe1a5c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Mv_DLKXKJ-QOF5fCD2OzclX1mVc>
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, 22 Jul 2020 02:00:24 -0000

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

Folks,

The following issues have proposals for resolution, and discussion so far
seems
to support consensus to accept them. Therefore, we are starting a 1-week
consensus call. If you object to a proposal, 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 proposals once the call
concludes.

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


* #3880: How long is a validated address good for?
  The proposal is to lose with no action.

* #3875: Persistent congestion threshold is unreliable during the early
stages of a connection
  The proposal is <https://github.com/quicwg/base-drafts/pull/3889>

* #3860: incorrect error code used for invalid RETIRE_CONNECTION_ID frames
  The proposal is <https://github.com/quicwg/base-drafts/pull/3861>

* #3845: What does "MUST reduce" mean?
  The proposal is https://github.com/quicwg/base-drafts/pull/3864

* #3842: Do I need to reset congestion info when the port changes?
  The proposal is to close with no action.

* #3834: Remove amplification throttle if the server receives Initial that
echoes its high entropy SCID.
  The proposal is <https://github.com/quicwg/base-drafts/pull/3924>

* #3808: Versions are for endpoints
  The proposal is <https://github.com/quicwg/base-drafts/pull/3785>

* #3800: Coalescing different CIDs for same connection
  The proposal is <https://github.com/quicwg/base-drafts/pull/3930>

Cheers,
Lars, Lucas and Mark
QUIC WG Chairs

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

<div dir=3D"ltr"><div><div>Folks,</div><div><br></div><div>The following is=
sues have proposals for resolution, and discussion so far seems</div>to sup=
port consensus to accept them. Therefore, we are starting a 1-week consensu=
s call. If you object to a proposal, please do so on the issue or<br>in res=
ponse to this message (changing the Subject appropriately!). Absent any<br>=
pushback, we&#39;ll direct the editors to incorporate proposals once the ca=
ll concludes.<br><br>See &lt;<a href=3D"https://github.com/quicwg/base-draf=
ts/projects/5">https://github.com/quicwg/base-drafts/projects/5</a>&gt; for=
 the current state of<br>issues in the Late Stage process, itself defined a=
t<br>&lt;<a href=3D"https://github.com/quicwg/base-drafts/blob/master/CONTR=
IBUTING.md">https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.=
md</a>&gt;.<br><br><br>* #3880: How long is a validated address good for?<b=
r>=C2=A0 The proposal is to lose with no action.<br><br>* #3875: Persistent=
 congestion threshold is unreliable during the early stages of a connection=
<br>=C2=A0 The proposal is &lt;<a href=3D"https://github.com/quicwg/base-dr=
afts/pull/3889">https://github.com/quicwg/base-drafts/pull/3889</a>&gt;<br>=
<br>* #3860: incorrect error code used for invalid RETIRE_CONNECTION_ID fra=
mes<br>=C2=A0 The proposal is &lt;<a href=3D"https://github.com/quicwg/base=
-drafts/pull/3861">https://github.com/quicwg/base-drafts/pull/3861</a>&gt;<=
br><br>* #3845: What does &quot;MUST reduce&quot; mean?<br>=C2=A0 The propo=
sal is <a href=3D"https://github.com/quicwg/base-drafts/pull/3864">https://=
github.com/quicwg/base-drafts/pull/3864</a><br><br>* #3842: Do I need to re=
set congestion info when the port changes?<br>=C2=A0 The proposal is to clo=
se with no action.<br><br>* #3834: Remove amplification throttle if the ser=
ver receives Initial that echoes its high entropy SCID.<br>=C2=A0 The propo=
sal is &lt;<a href=3D"https://github.com/quicwg/base-drafts/pull/3924">http=
s://github.com/quicwg/base-drafts/pull/3924</a>&gt;<br><br>* #3808: Version=
s are for endpoints<br>=C2=A0 The proposal is &lt;<a href=3D"https://github=
.com/quicwg/base-drafts/pull/3785">https://github.com/quicwg/base-drafts/pu=
ll/3785</a>&gt;<br><br>* #3800: Coalescing different CIDs for same connecti=
on<br>=C2=A0 The proposal is &lt;<a href=3D"https://github.com/quicwg/base-=
drafts/pull/3930">https://github.com/quicwg/base-drafts/pull/3930</a>&gt;<b=
r><br></div><div>Cheers,</div><div>Lars, Lucas and Mark<br></div><div>QUIC =
WG Chairs<br></div></div>

--00000000000021371905aafe1a5c--


From nobody Tue Jul 21 20:12:34 2020
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 3DF7B3A0A13 for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 20:12:32 -0700 (PDT)
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, 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 7yf80KHtTLdY for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 20:12:30 -0700 (PDT)
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 620173A0A0C for <quic@ietf.org>; Tue, 21 Jul 2020 20:12:30 -0700 (PDT)
Received: by mail-lj1-x22c.google.com with SMTP id r19so853944ljn.12 for <quic@ietf.org>; Tue, 21 Jul 2020 20:12:30 -0700 (PDT)
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=75WkLZGQtbzZ5Lgvq6n2rYgzt7wpBcA0GTYqSYEWVrk=; b=BL/f34FkgpXRZuGaMMSc7+gDzzl004gN1YHDInkv5E2e2Z7Th+e9127otrVTWGkPSU OvigC4VDSLrbibgVmS2WVoNr1LiwBuzYy4Nljl6GWwxjhkH7VYPRrsfQbhqFsjWKyL15 MQdS7qNV4Zgdf11o5F+XAXTHKvrkIQlUDXEvG/q8AzoAR+MXrro0Cv+feUq+sgdvplSV jgeDNdIkjfhZY63OMLT10k0fWn8X83ypeoHL7lwabwNOAeQnj5MDYF2TzZMyLNkesUvv Nzz1CxFlV0g4BKqp1Nqt+mvjHEGoLvidKs66szEi77qF05tFobmCNFbjwkbq3N/OeSJd Rzkw==
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=75WkLZGQtbzZ5Lgvq6n2rYgzt7wpBcA0GTYqSYEWVrk=; b=fgfUmIm7oQwQPTG18QzXiScvn1+RDgZ/HrIi329Ko5lf8Lcwgyrn+Rch8abPacgxla E4sEXC+VomRiMcfVZEyR+olayfHmIxDRY8cv54YTJ7/FUv0ndGWaQcaKbR5XMBmxhrn5 WzbT5nrnVZGbGo812zyY/qhyeGzvFGUS9JnHFarntvJ7eogeIPcmHaWqFRXK+0M5tubJ 4mSB292EaQocQAkgyvJY00xmUbncBAg0D3TBfscgq0O/hNwYSY/7SudeEY6jHy0aVjSF uUEASHrHrH9+Wci/Ilt1EEW9Mr+ezrYNO5NFyh9mgW3ByYK2GbnglA+wI7Zm9CA0b2O2 veug==
X-Gm-Message-State: AOAM533KXocdffID4HJ/iB5KHUF3JA8K4pghHgDDKWNBzcBT63K+Hqij aSIoddNftvg307iExEJW0VpGEOmER6+aHnAxQOxz9A==
X-Google-Smtp-Source: ABdhPJzGD35zIUkfyfOmNiRqXXqddXiT+l1kTF7GplJUkDiajRxcwQ5U25kyFtf9azTYBLDlDV1NziU/xIlw3bhjbbo=
X-Received: by 2002:a2e:999a:: with SMTP id w26mr13628960lji.371.1595387548498;  Tue, 21 Jul 2020 20:12:28 -0700 (PDT)
MIME-Version: 1.0
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com>
In-Reply-To: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Tue, 21 Jul 2020 20:11:52 -0700
Message-ID: <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com>
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
To: Lucas Pardue <lucaspardue.24.7@gmail.com>
Cc: QUIC WG <quic@ietf.org>, Lars Eggert <lars@eggert.org>, Mark Nottingham <mnot@mnot.net>
Content-Type: multipart/alternative; boundary="0000000000001b964d05aaff1ce4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/pwsYrpJwVNX3TrvvA66G6JoPHdY>
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, 22 Jul 2020 03:12:32 -0000

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

On Tue, Jul 21, 2020 at 7:00 PM Lucas Pardue <lucaspardue.24.7@gmail.com>
wrote:

> Folks,
>
> The following issues have proposals for resolution, and discussion so far
> seems
> to support consensus to accept them. Therefore, we are starting a 1-week
> consensus call. If you object to a proposal, 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 proposals once the call
> concludes.
>
> 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>.
>
>
> * #3880: How long is a validated address good for?
>   The proposal is to lose with no action.
>
> * #3875: Persistent congestion threshold is unreliable during the early
> stages of a connection
>   The proposal is <https://github.com/quicwg/base-drafts/pull/3889>
>
> * #3860: incorrect error code used for invalid RETIRE_CONNECTION_ID frames
>   The proposal is <https://github.com/quicwg/base-drafts/pull/3861>
>
> * #3845: What does "MUST reduce" mean?
>   The proposal is https://github.com/quicwg/base-drafts/pull/3864
>
> * #3842: Do I need to reset congestion info when the port changes?
>   The proposal is to close with no action.
>

Assuming I understand this proposal, I object to this resolution. I do not
believe that the current text is appropriate.

As I said, I don't have a strong opinion about the outcome, but we
shouldn't just hint to people that they should ignore the port.

-Ekr

--0000000000001b964d05aaff1ce4
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 Tue, Jul 21, 2020 at 7:00 PM Lucas=
 Pardue &lt;<a href=3D"mailto:lucaspardue.24.7@gmail.com">lucaspardue.24.7@=
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"><div><div>Folks,</div><div><br></div><div>The f=
ollowing issues have proposals for resolution, and discussion so far seems<=
/div>to support consensus to accept them. Therefore, we are starting a 1-we=
ek consensus call. If you object to a proposal, please do so on the issue o=
r<br>in response to this message (changing the Subject appropriately!). Abs=
ent any<br>pushback, we&#39;ll direct the editors to incorporate proposals =
once the call concludes.<br><br>See &lt;<a href=3D"https://github.com/quicw=
g/base-drafts/projects/5" target=3D"_blank">https://github.com/quicwg/base-=
drafts/projects/5</a>&gt; for the current state of<br>issues in the Late St=
age process, itself defined at<br>&lt;<a href=3D"https://github.com/quicwg/=
base-drafts/blob/master/CONTRIBUTING.md" target=3D"_blank">https://github.c=
om/quicwg/base-drafts/blob/master/CONTRIBUTING.md</a>&gt;.<br><br><br>* #38=
80: How long is a validated address good for?<br>=C2=A0 The proposal is to =
lose with no action.<br><br>* #3875: Persistent congestion threshold is unr=
eliable during the early stages of a connection<br>=C2=A0 The proposal is &=
lt;<a href=3D"https://github.com/quicwg/base-drafts/pull/3889" target=3D"_b=
lank">https://github.com/quicwg/base-drafts/pull/3889</a>&gt;<br><br>* #386=
0: incorrect error code used for invalid RETIRE_CONNECTION_ID frames<br>=C2=
=A0 The proposal is &lt;<a href=3D"https://github.com/quicwg/base-drafts/pu=
ll/3861" target=3D"_blank">https://github.com/quicwg/base-drafts/pull/3861<=
/a>&gt;<br><br>* #3845: What does &quot;MUST reduce&quot; mean?<br>=C2=A0 T=
he proposal is <a href=3D"https://github.com/quicwg/base-drafts/pull/3864" =
target=3D"_blank">https://github.com/quicwg/base-drafts/pull/3864</a><br><b=
r>* #3842: Do I need to reset congestion info when the port changes?<br>=C2=
=A0 The proposal is to close with no action.<br></div></div></blockquote><d=
iv><br></div><div>Assuming I understand this proposal, I object to this res=
olution. I do not believe that the current text is appropriate.</div><div><=
br></div><div>As I said, I don&#39;t have a strong opinion about the outcom=
e, but we shouldn&#39;t just hint to people that they should ignore the por=
t.<br></div><div><br> </div><div>-Ekr</div></div></div>

--0000000000001b964d05aaff1ce4--


From nobody Tue Jul 21 23:10:53 2020
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 105A73A0E23 for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 23:10:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=eggert.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 Shf0Pjas-_R4 for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 23:10:50 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 168443A0E24 for <quic@ietf.org>; Tue, 21 Jul 2020 23:10:50 -0700 (PDT)
Received: from [IPv6:2a00:ac00:0:35:b1a0:61d5:fc38:9118] (unknown [IPv6:2a00:ac00:0:35:b1a0:61d5:fc38:9118]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 842F46503FD; Wed, 22 Jul 2020 09:10:44 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1595398244; bh=JbufiifmCWt6FkW9eAruXcMh4F8BY2DPNZYZypjCtcM=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=tgjzMkeS96wNCFkmj9fM6gFPC8iUnxglEzWc2g68B7T+u5Elh1cftpQvip+bO6fnv vL54eBs1hZXdcjZrsMqXUca9proKFrSJLhTR/kjeap+4CTYlzxnKtFqPLF9WINctEJ BW8TD7A0OLoLPXdBp2el07Kjc1TVQvJ3gqVexuAs=
From: Lars Eggert <lars@eggert.org>
Message-Id: <FA2F8CAC-60D8-405D-8FB1-984675AF953A@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_471EF00E-72E4-4F05-AFA0-FA3AC40EE3BC"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: Re: Small size of core QUIC library to replace TCP for embedded system
Date: Wed, 22 Jul 2020 09:10:44 +0300
In-Reply-To: <CAA=hcWQ60GH2TnjvqBEGvVQ1whxNYwEWjQ+b9FW948GKvN570Q@mail.gmail.com>
Cc: quic <quic@ietf.org>
To: Jupiter <jupiter.hce@gmail.com>
References: <CAA=hcWS0V8ipsoAEFK3ejdA++Vzi+czth37=ntP4mnt8d=mtRg@mail.gmail.com> <1C514B96-9AAA-40B3-93EC-3DCDFAF72A93@eggert.org> <CAA=hcWTP7mVo1yyr8wQrgNuA40Tr5=XcrqJiebtVa7Km=2sLzw@mail.gmail.com> <F384B33C-70F8-45EF-AB5C-30D0A145659A@eggert.org> <CAA=hcWQ60GH2TnjvqBEGvVQ1whxNYwEWjQ+b9FW948GKvN570Q@mail.gmail.com>
X-MailScanner-ID: 842F46503FD.A36C9
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/DOfrEgKZ3iSuRvf44_MZOIRhPSI>
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, 22 Jul 2020 06:10:52 -0000

--Apple-Mail=_471EF00E-72E4-4F05-AFA0-FA3AC40EE3BC
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 2020-7-21, at 13:56, Jupiter <jupiter.hce@gmail.com> wrote:
> Good to know, fair to say your git source is for RTOS statically on
> bare metal, I was there a long time before :-).

actually, it's not. I *ported* quant to embedded OSs, which was pretty =
doable since the packet I/O stuff was already factored out into =
warpcore. But quant as a QUIC stack runs fine on POSIX.

(Warpcore is a kernel bypass IP/UDP stack with a focus on datacenter =
usage, not IoT. But it has a POSIX backend as well as kernel-bypass =
support.)

Lars

--Apple-Mail=_471EF00E-72E4-4F05-AFA0-FA3AC40EE3BC
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAl8X2GQACgkQVLXDCb9w
wVdWhBAAukVyB9dG5OLAycdYHdgWmcrrBXuE0exUMg656sIQOIwRZeqC3eghmthW
Ne1hYzdD4LzDXZMszR5pPp1a1/e8Mn703q+uwWkXQfR1BUQepvomnk5zttJuhrYC
3jIDQeOdaoBuV5MlWsiVbepp3sURwdxh6E65EmRu3NeGi3yA5JKLWu4GogDjurpb
GPNlTic/4WkeTl4BgiKFQY2+9Y3XSdei1TqS61nXCCqsWxRUrpVbsRrqm496JUtR
Dm3YDpoLvim09+zuLwRBMbPsuvLdWI45x09EoEWGYKsWCJNOkAgqgr8CdZUQEuDn
EO84iRdIj+ZBcqg7vuaIHGZr3pw6ht60rgvEupcPf9v4vN0HeYrTyHF1ZCCauJTR
a8ZIE+HLCYaEjY3Gx3Ty8NYc+BZoHMN64D7XPxYshKNeWQPDw+1Zcmah7nHjFV62
JmTcsbz68mubl/gfIGmq4ulTzwUENzLH3ym6p/T4fPcFnjqJtlDOy9fmmpCcF/SN
/IRFv808IpAaOzWuRuihBoBSe5w7Bcy/wtbOsNGGuvd8lvW4mofHXQeB0ZVAf9hU
fGXWFYSzytgnIDhe6wgmJ3rqPqDWmm0zo1DwqNHg/PHEKbmF0DnBoMaWMxNpFx4c
HZGzknD7mAerqzg8FEtO0zRl4GOeYu7kK+T7OhDkXc/+eHENJNQ=
=OHPa
-----END PGP SIGNATURE-----

--Apple-Mail=_471EF00E-72E4-4F05-AFA0-FA3AC40EE3BC--


From nobody Tue Jul 21 23:17:48 2020
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 11DB13A0E30 for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 23:17:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=eggert.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 j0OBFoVykaZL for <quic@ietfa.amsl.com>; Tue, 21 Jul 2020 23:17:43 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:0:35:211:32ff:fe22:186f]) (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 3D9203A0E2F for <quic@ietf.org>; Tue, 21 Jul 2020 23:17:43 -0700 (PDT)
Received: from [IPv6:2a00:ac00:0:35:b1a0:61d5:fc38:9118] (unknown [IPv6:2a00:ac00:0:35:b1a0:61d5:fc38:9118]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 7DF2265072D; Wed, 22 Jul 2020 09:17:35 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1595398655; bh=o1CKTVl36fEatuDWVt3VXiUh11d/wkxF4fQDj5dn/Sg=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=FUgHmSu2wcJq2q/kCO8DvhmuEXR6peoHoIZWkBWjHfOLvq4FQ+Ov+zmSkAhHXu8xq 0wBYW+7NTuePvZlCK9odfrQuEjXdcg5zds7fPHMfshPUgPx+TNCZYwiTaNaE3XnA50 YAtI6LJETvFpxx7aAGQepJ7kAjqcJ4gojLBOQo10=
From: Lars Eggert <lars@eggert.org>
Message-Id: <3D493D2B-BC8D-4CE9-B189-48770C3FA06F@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_14C625FF-C365-43DF-80ED-EEEAAA578165"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: QUIC API (was: Re: Small size of core QUIC library to replace TCP for embedded system)
Date: Wed, 22 Jul 2020 09:17:33 +0300
In-Reply-To: <2499749.AO4zfZtjs8@linux-9daj>
Cc: quic <quic@ietf.org>
To: Paul Vixie <paul@redbarn.org>
References: <CAA=hcWS0V8ipsoAEFK3ejdA++Vzi+czth37=ntP4mnt8d=mtRg@mail.gmail.com> <F384B33C-70F8-45EF-AB5C-30D0A145659A@eggert.org> <CAA=hcWQ60GH2TnjvqBEGvVQ1whxNYwEWjQ+b9FW948GKvN570Q@mail.gmail.com> <2499749.AO4zfZtjs8@linux-9daj>
X-MailScanner-ID: 7DF2265072D.A4B5D
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/GqPJv1rSMPa4doFtZJ_9AeCltXM>
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, 22 Jul 2020 06:17:47 -0000

--Apple-Mail=_14C625FF-C365-43DF-80ED-EEEAAA578165
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 2020-7-21, at 20:02, Paul Vixie <paul@redbarn.org> wrote:
> my question is, has any QUIC implementor been thinking along these =
lines? i
> believe that the parameters to a QUIC "connect" syscall would be =
larger and
> more numerous than for a TCP or SCTP or UDP "connect" syscall, for =
example.

most QUIC implementations have an API that is at a high level pretty =
similar to the socket API, but different in all the details. And they =
are all different from each other.

Since you asked about a "connect" equivalent, here is what some of the C =
stacks offer:

quant: =
https://github.com/NTAP/quant/blob/master/lib/include/quant/quant.h#L110-L=
118

msquic: =
https://github.com/microsoft/msquic/blob/master/src/inc/msquic.h#L745-L757=


quicly: =
https://github.com/h2o/quicly/blob/master/include/quicly.h#L892-L900

Pretty different.

Lars

--Apple-Mail=_14C625FF-C365-43DF-80ED-EEEAAA578165
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAl8X2f0ACgkQVLXDCb9w
wVeuKg/7BdtQ7zD6qwwSFHU3dA/drPmlMpK8JXn7czcvYqxPTr2lAJXJ5quYDuL7
pr5AvvSMWNRTczumeucPLYtYM/YQyyzzq0Owo2ArG2GoQRRZmTnUEjShHyS1W1XD
Y9zc2u/ZQe2+dur1tgjren4CeX4l/OTeUo7X2D07pwApNbqxiPIMbj0QPubBrJBn
nwZoiV9LDmS4PSremTAt8/hswdIPZ57p8GFGwqDw9Ac2+ySPzQoYoH6lNsGpfE6a
S54Fvwh8K6eNfWU0QLoaD1ALhw+Yg3+DS1kKjiOYEVabnB++iAap0BZCVFnXNyRx
yBLVkB43MN6KzKzXqf+l3BvqpsIma27EGKKHv38ExHdf/pTzAuQuXmMVj32Xgv4i
QCx6+BNkHGU+Fa+t2KGzOTPr0JmR8AFo9QgY+BDOF1H+GR02HeAC48YLSvuJLIEY
A0L3mn5UfPCVtzSyWhKBc6kPRwg6UWTKPXxfUpAc2yNndIFrOE+NrFH4s4EUBwYn
/hCwEwlptYWlepgQcEFqBV0WzJp8IgAKukT+214NiOKAiy/rQWjhNEkbqGiUE/Nb
3wjhJbQz3F+QDiFcgtvVx8jAZ55Umw+u+/EK1WOIScr0CP4ZJl61vnQkoXSNcxbE
NsGTMJGCdZ/Gl8xqSRqPDYspJ7LdwZgqdxdzlXsXzdJycjF058o=
=UNBk
-----END PGP SIGNATURE-----

--Apple-Mail=_14C625FF-C365-43DF-80ED-EEEAAA578165--


From nobody Wed Jul 22 00:36:27 2020
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 EC5863A0F10 for <quic@ietfa.amsl.com>; Wed, 22 Jul 2020 00:36:25 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=eggert.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 bOu8W8SBhQj1 for <quic@ietfa.amsl.com>; Wed, 22 Jul 2020 00:36:24 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:0:35:211:32ff:fe22:186f]) (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 768FF3A0F12 for <quic@ietf.org>; Wed, 22 Jul 2020 00:36:24 -0700 (PDT)
Received: from [IPv6:2a00:ac00:0:35:b1a0:61d5:fc38:9118] (unknown [IPv6:2a00:ac00:0:35:b1a0:61d5:fc38:9118]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 022826508BA; Wed, 22 Jul 2020 10:36:17 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1595403378; bh=tC9NUXFAKfs2M5Qv+jCjSMuYFZ+qzrP/dRphu9fcCz0=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=hFOVDAytZOP4Qgs59xKaA/fodkAdKoX8EFXURwwKrnzVzPesSmKzzelOOpfZVXiDX zKyZKwd9qyFTAjSTyry7NkzzlHue7aQS9mJilUYeWMwjdcnqH4gQgHy2ABzKm15LG4 PkJlfLDGsrPca+I7PY54gY5Oe2zhoF82kjBC6/cs=
From: Lars Eggert <lars@eggert.org>
Message-Id: <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_7BFC2886-2CEC-4014-BBD5-6647C0B23BB2"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
Date: Wed, 22 Jul 2020 10:36:17 +0300
In-Reply-To: <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com>
Cc: Lucas Pardue <lucaspardue.24.7@gmail.com>, QUIC WG <quic@ietf.org>, Mark Nottingham <mnot@mnot.net>
To: Eric Rescorla <ekr@rtfm.com>
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com>
X-MailScanner-ID: 022826508BA.A174D
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/p_YI9qrwaFicett7DAHDHbqucms>
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, 22 Jul 2020 07:36:26 -0000

--Apple-Mail=_7BFC2886-2CEC-4014-BBD5-6647C0B23BB2
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 2020-7-22, at 6:11, Eric Rescorla <ekr@rtfm.com> wrote:
> As I said, I don't have a strong opinion about the outcome, but we =
shouldn't just hint to people that they should ignore the port.

existing protocols basically just broke when a port or IP address =
changed (e.g., a NAT rebinding happened). So how to respond to this is =
something that we don't have existing IETF practice for AFAIK.

The conservative approach would be to mandate a CC reset on any change =
to the four-tuple, since it indicates a possible path change.

For clients in consumer access networks behind CPE NATs, that =
conservative approach is probably too conservative, since the =
CC-relevant properties of the path are unlikely to have changed if just =
the source port changed.

On the other hand, with client side CGNs and server-side BALBs (big-ass =
load balancers...) a port change now maybe is more indicative of a path =
change. But it's not clear that this path change is more likely to =
affect the CC-relevant path characteristics.

One final thing I'll point out is that all IETF transports have been =
happily ignoring at least one path change indication since forever - =
there is no mandated reaction to any change in the received IP TTL, and =
I'm also unaware of any implementation reacting to IP TTL changes (which =
would indicate a change in path length, something that probably would =
lead to CC-relevant changes in path characteristics.)

That, together with the observation that CC will react to a path change =
anyway after an RTT due to loss/marks, leads me to believe we're =
probably OK to not reset CC on a port change. It might mean that we're =
sending for about an RTT at a rate that is too high in some rare (?) =
cases, but in the vast majority of cases, we'd avoid needless =
performance degradations.

YMMV.

Lars

--Apple-Mail=_7BFC2886-2CEC-4014-BBD5-6647C0B23BB2
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAl8X7HEACgkQVLXDCb9w
wVdPFw//cBW7yVh2skqT/a54hsqn+i5Ll0LX4ple2y+lX0yH8nR9j9iCyyzWYXsV
RsQ6n9F7zWRxzLMO/pKAnPkiE59ATbMrR9meIILCkUfnnEHBs6k5Iduflr27qTuh
mMlgQnnxIDyu+VuObXSFKd3KnPnTf3DJL6wIaIUR0aWKo778Esib6b5nJpJUQXd8
0yuxw4OWyxZvENcsmFZFxLDSvSI82I0hfEhrkKK5ivz5SEHaDway4axwYvM35ZXS
dZnin23Eqvh7jpeQgB8StWi8rcWUk8SoeB9K8xpepq4Zo3M5VruwsPmD+LrfKd9q
caaY1t2+ZcUm0RVK8KrMfnmpxzSapLbrrFF6n3ZtZW6Sqv8oOyHjLEm4ILKc8aOU
HGSNYQ0rG5rZU6+z8cTBYSs1dYIlNzCkGf6+fER84o8D8DTM8VP5z1NyIDJtN6Eu
dcpdIEC8t90Quzzt9KEmLejK9+vGMT/STmK8VTsOZIn6/HzeweoaXZNGrMqzB9ZE
LPQqOJBBdAeEBsby/q18tTSGDT125YTE6zFIFuTS5qFSGYiuqRlba96e0BZhSbaZ
/cEpgHFxmjajVaLhnaYeB+dL4sG6VHCPWBBECB9QJDMy8SaB5bu+wFDCY5xdHkaF
aPmGRYAFAKdnGVsvLIGO3jy9R576czI0YweB9GnEDj07CC95BWQ=
=61Pl
-----END PGP SIGNATURE-----

--Apple-Mail=_7BFC2886-2CEC-4014-BBD5-6647C0B23BB2--


From nobody Wed Jul 22 05:38:58 2020
Return-Path: <watsonbladd@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 399163A0B27 for <quic@ietfa.amsl.com>; Wed, 22 Jul 2020 05:38:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 BlcEwOR14qjJ for <quic@ietfa.amsl.com>; Wed, 22 Jul 2020 05:38:55 -0700 (PDT)
Received: from mail-lf1-x131.google.com (mail-lf1-x131.google.com [IPv6:2a00:1450:4864:20::131]) (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 424C43A0B1B for <quic@ietf.org>; Wed, 22 Jul 2020 05:38:55 -0700 (PDT)
Received: by mail-lf1-x131.google.com with SMTP id i19so1213524lfj.8 for <quic@ietf.org>; Wed, 22 Jul 2020 05:38:55 -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=cwIYBSFbY44LDVwgwdoFV6wgv3WPNiWSnWTSXT+DZuY=; b=INSyqyis9VHnyG/uLQMo27bsTCjNA4YhUJ/xBX/I8JL70Z98JRkiNS7k0XRFq50Afp 65Re7lnCpQ9pufT7skL+W7SwDXWdXow+iFVYuHuRCOOAqmRayEfMizHo02wJDMAIrpoe US22uG4dgbKFXKh1LoZzNI95T8C95fpepG7D7fxIINYrAODtKLkO675y0l0WBkiQ+qrm DnmeOTZdYxxLaYLYMkHtPKTCSci41Zo4u9RWCgs5jYnmdW4WV02zBTROiZe5vBs3e0K7 xOM/3pIanMIW9FhlVCBR85Bubiw4feHs9D/TP7rKF/ewpJBpSUGNzEfcgAjdJqJXFwS1 lxrQ==
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=cwIYBSFbY44LDVwgwdoFV6wgv3WPNiWSnWTSXT+DZuY=; b=GH5JIyN9gPgLwR0Xc07oulSquhAeL02F5Lt4e0ofeFEhXFv/JZxBQhgiZgcM5pC/s6 b4AkYcR5zixs3PMPR6twkZccMEc7pLluTSveMDt7JPre6ymsTUep/HDc1uQ7Au/Bj57G h/HwFEBLNAAWSnfGKIMT83dsO+aS3GIJypAmK0GHL8SB+wgl6owFHA323eKwNsgLnCho wE4vIWtif/UdxmNPdrgPoDiUPir/+3bkrPgOLxRm1XZjSOdPIbMK3T+YCqV/fw5LDzbN pNUJAqobdTA/VXQNvzA23KxQG7BHzHjlS3cSx4EpnQpwKCzqjUpo1KmL1OQwfjpcGe7H SkAQ==
X-Gm-Message-State: AOAM530rmN6ZG7G3dqxdvF/VUBiG1IDobKpd02hd7c67yISBW2kFSUKf Y2txSjtp3dByDbTaH8eoKLFZUn9GYyQeiiEblgqwFTud
X-Google-Smtp-Source: ABdhPJyP+Y4iTJ81T3tG82QgHXA+V6cV3k+my2DtTfJ0mO114/LE7pkpcHMPn5RaAjV+ZCTClkzU7z0RWvftt3kjgew=
X-Received: by 2002:a05:6512:3249:: with SMTP id c9mr16117993lfr.216.1595421533523;  Wed, 22 Jul 2020 05:38:53 -0700 (PDT)
MIME-Version: 1.0
References: <43bb1525-0afa-4c4e-a234-f6ccfacbdd29@www.fastmail.com> <a4d7e8cf-5879-6941-e059-5d2f3e67ae86@huitema.net> <58b40fc0-86ad-49e9-bc17-187c38e97f7a@www.fastmail.com> <1d543593-7abc-4a89-93c5-82c464492786@www.fastmail.com> <CACpbDccSB6H9AhmAinia7ojEg1VY-S=dF214wHvZcZkoiL-xFA@mail.gmail.com> <7d549475-249b-4674-9aa8-c2bf9953243b@www.fastmail.com> <CALGR9oaHQHJneN2edetGLcq4u4PNF0oAyq9PKc7ZVxz_pXTMGw@mail.gmail.com> <CACsn0c=HkByj0dkwfW+0=n9HzGZ0cZamot6N=AFks3wbnwnWXQ@mail.gmail.com> <19922b1a-a02c-46c9-b441-3806d3f77b89@www.fastmail.com> <02f5d291-4b95-7f94-5028-c90f94bd5908@felixguenther.info> <04697AEF-461E-46C8-B1EC-B15D462B8B7E@eggert.org>
In-Reply-To: <04697AEF-461E-46C8-B1EC-B15D462B8B7E@eggert.org>
From: Watson Ladd <watsonbladd@gmail.com>
Date: Wed, 22 Jul 2020 08:38:42 -0400
Message-ID: <CACsn0cm8QUgKmHeJH52YgYCR9294N2Cez5_Qg7ZMtEkRdWgJvA@mail.gmail.com>
Subject: Re: New confidentiality and integrity limits
To: Lars Eggert <lars@eggert.org>
Cc: =?UTF-8?Q?Felix_G=C3=BCnther?= <mail@felixguenther.info>,  IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000c5d44905ab0705b3"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/KPtYqIz2GUbgfLObh2YfDKUHnbg>
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, 22 Jul 2020 12:38:57 -0000

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

On Tue, Jul 21, 2020, 2:50 AM Lars Eggert <lars@eggert.org> wrote:

> Thanks, Felix.
>
> Watson, does this address your comments? (Chairs are trying to push #3788
> to resolution.)
>

Yes. I am still confused but it's clear I need to think harder about multi
user.


> Thanks,
> Lars
>
> On 2020-7-16, at 9:47, Felix G=C3=BCnther <mail@felixguenther.info> wrote=
:
> >
> > Hi Watson,
> >
> > Let me clarify that the multi-user setting does not mean that a forgery
> > attempt is made against all keys simultaneously -- this model still
> > counts "try to decrypt 1 ciphertext under 1 key" as 1 forgery attempt.
> > The important difference is that, for each attempt, you may try a
> > different key.
> >
> > While the model is somewhat more general in allowing to go back and
> > forth between all keys, this of course also captures the QUIC setting
> > where only few keys are active at any point in time, and are phased
> > in/out sequentially. I am not aware of an intermediate model, but I
> > don't think the difference would be huge, plus I strongly agree with
> > Martin that this conservative over-approximation doesn't hurt much here=
.
> >
> > So, the multi-user model is the closest analysis we have to answer the
> > question:  "What's the advantage of an adversary that tries to inject a
> > forgery *at some point* in a QUIC connection."
> > Single-user models cannot answer this question, as they only speak to
> > forgery attempts under one fixed key, hence don't capture key updates.
> >
> > I hope this clarifies the need for multi-user bounds.
> >
> > Cheers,
> > Felix
> >
> >
> > On 2020-07-16 06:58 +0200, Martin Thomson <mt@lowentropy.net> wrote:
> >> On Thu, Jul 16, 2020, at 11:40, Watson Ladd wrote:
> >>> I do not believe the analysis is correct.
> >>>
> >>> A forgery against a QUIC connection will be checked at one or at most
> >>> two keys: the current one and the next one. It is not the case that a
> >>> forgery will be attempted against all the keys simultaneously: it wil=
l
> >>> have to be resent. Perhap I'm missing something about the setting her=
e
> >>> that makes this the multiuser and not the singleuser setting.
> >>
> >> Thanks for checking Watson.
> >>
> >> I had exactly the same thought, but was convinced by Felix that the
> analysis was based on a definition that only considers the number of
> encryption/verification queries in total. In particular, that the values =
in
> results are not limited in any way by which subset of the keys could be
> tried.
> >>
> >> Incidentally, that also supports the view that there is degradation in
> the confidentiality advantage as you update to different keys.  I note th=
at
> the PR does not acknowledge this, but maybe it should.
> >>
> >> I confess that I'm still not completely confident that the multiuser
> setting is a good fit for our needs (or even that the threat model is the
> right one).  This is, in part of the reason you state: the mu setting
> assumes that the attacker has equal access to all "users" concurrently an=
d
> the limited number of active keys would seem to make that difficult to
> exploit.  But I don't know how to prove that this is an acceptable
> assumption.
> >>
> >> What I am confident about is that a conservative approach doesn't hurt
> a great deal here.  The calculated limits for GCM are high enough - even
> under the assumptions made - that you have serious problems if you hit th=
em.
> >>
> >
>
>

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

<div dir=3D"auto"><div><br><br><div class=3D"gmail_quote"><div dir=3D"ltr" =
class=3D"gmail_attr">On Tue, Jul 21, 2020, 2:50 AM Lars Eggert &lt;<a href=
=3D"mailto:lars@eggert.org">lars@eggert.org</a>&gt; wrote:<br></div><blockq=
uote class=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc =
solid;padding-left:1ex">Thanks, Felix.<br>
<br>
Watson, does this address your comments? (Chairs are trying to push #3788 t=
o resolution.)<br></blockquote></div></div><div dir=3D"auto"><br></div><div=
 dir=3D"auto">Yes. I am still confused but it&#39;s clear I need to think h=
arder about multi user.</div><div dir=3D"auto"><br></div><div dir=3D"auto">=
<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
Thanks,<br>
Lars<br>
<br>
On 2020-7-16, at 9:47, Felix G=C3=BCnther &lt;<a href=3D"mailto:mail@felixg=
uenther.info" target=3D"_blank" rel=3D"noreferrer">mail@felixguenther.info<=
/a>&gt; wrote:<br>
&gt; <br>
&gt; Hi Watson,<br>
&gt; <br>
&gt; Let me clarify that the multi-user setting does not mean that a forger=
y<br>
&gt; attempt is made against all keys simultaneously -- this model still<br=
>
&gt; counts &quot;try to decrypt 1 ciphertext under 1 key&quot; as 1 forger=
y attempt.<br>
&gt; The important difference is that, for each attempt, you may try a<br>
&gt; different key.<br>
&gt; <br>
&gt; While the model is somewhat more general in allowing to go back and<br=
>
&gt; forth between all keys, this of course also captures the QUIC setting<=
br>
&gt; where only few keys are active at any point in time, and are phased<br=
>
&gt; in/out sequentially. I am not aware of an intermediate model, but I<br=
>
&gt; don&#39;t think the difference would be huge, plus I strongly agree wi=
th<br>
&gt; Martin that this conservative over-approximation doesn&#39;t hurt much=
 here.<br>
&gt; <br>
&gt; So, the multi-user model is the closest analysis we have to answer the=
<br>
&gt; question:=C2=A0 &quot;What&#39;s the advantage of an adversary that tr=
ies to inject a<br>
&gt; forgery *at some point* in a QUIC connection.&quot;<br>
&gt; Single-user models cannot answer this question, as they only speak to<=
br>
&gt; forgery attempts under one fixed key, hence don&#39;t capture key upda=
tes.<br>
&gt; <br>
&gt; I hope this clarifies the need for multi-user bounds.<br>
&gt; <br>
&gt; Cheers,<br>
&gt; Felix<br>
&gt; <br>
&gt; <br>
&gt; On 2020-07-16 06:58 +0200, Martin Thomson &lt;<a href=3D"mailto:mt@low=
entropy.net" target=3D"_blank" rel=3D"noreferrer">mt@lowentropy.net</a>&gt;=
 wrote:<br>
&gt;&gt; On Thu, Jul 16, 2020, at 11:40, Watson Ladd wrote:<br>
&gt;&gt;&gt; I do not believe the analysis is correct.<br>
&gt;&gt;&gt; <br>
&gt;&gt;&gt; A forgery against a QUIC connection will be checked at one or =
at most<br>
&gt;&gt;&gt; two keys: the current one and the next one. It is not the case=
 that a<br>
&gt;&gt;&gt; forgery will be attempted against all the keys simultaneously:=
 it will<br>
&gt;&gt;&gt; have to be resent. Perhap I&#39;m missing something about the =
setting here<br>
&gt;&gt;&gt; that makes this the multiuser and not the singleuser setting.<=
br>
&gt;&gt; <br>
&gt;&gt; Thanks for checking Watson.<br>
&gt;&gt; <br>
&gt;&gt; I had exactly the same thought, but was convinced by Felix that th=
e analysis was based on a definition that only considers the number of encr=
yption/verification queries in total. In particular, that the values in res=
ults are not limited in any way by which subset of the keys could be tried.=
<br>
&gt;&gt; <br>
&gt;&gt; Incidentally, that also supports the view that there is degradatio=
n in the confidentiality advantage as you update to different keys.=C2=A0 I=
 note that the PR does not acknowledge this, but maybe it should.<br>
&gt;&gt; <br>
&gt;&gt; I confess that I&#39;m still not completely confident that the mul=
tiuser setting is a good fit for our needs (or even that the threat model i=
s the right one).=C2=A0 This is, in part of the reason you state: the mu se=
tting assumes that the attacker has equal access to all &quot;users&quot; c=
oncurrently and the limited number of active keys would seem to make that d=
ifficult to exploit.=C2=A0 But I don&#39;t know how to prove that this is a=
n acceptable assumption.<br>
&gt;&gt; <br>
&gt;&gt; What I am confident about is that a conservative approach doesn&#3=
9;t hurt a great deal here.=C2=A0 The calculated limits for GCM are high en=
ough - even under the assumptions made - that you have serious problems if =
you hit them.<br>
&gt;&gt; <br>
&gt; <br>
<br>
</blockquote></div></div></div>

--000000000000c5d44905ab0705b3--


From nobody Wed Jul 22 07:48:16 2020
Return-Path: <ted.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 898963A0766 for <quic@ietfa.amsl.com>; Wed, 22 Jul 2020 07:48:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 Bu27DKgtOLkH for <quic@ietfa.amsl.com>; Wed, 22 Jul 2020 07:48:12 -0700 (PDT)
Received: from mail-oo1-xc31.google.com (mail-oo1-xc31.google.com [IPv6:2607:f8b0:4864:20::c31]) (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 BE9DA3A05A0 for <quic@ietf.org>; Wed, 22 Jul 2020 07:48:12 -0700 (PDT)
Received: by mail-oo1-xc31.google.com with SMTP id w1so466890ooj.2 for <quic@ietf.org>; Wed, 22 Jul 2020 07:48:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=p9ORCNyieU/yRCy43F0O8tnupHGOhl7PPD9T9rkPT+k=; b=SAa9yU5hQIJlEg42AN/oYCG3j+4yavO2kFNpw9Hg6HhkVGZgSgxK0Yps++i2Ey3rGB E5YiizmqgPVXiqZet7HSr1iGV+rKb0cja5Yx0AwJrHFKn4URWMVcwIwBAZOAEJ2jDzYK awe6mZUEJ12s6K65+3+7ZlEDaBdfV+1vZbOktHMSBP1rx1m3SpZsRQ6KXcLsuWBuDB/W LHuHXSg3vhor7xATCYAWqx7/aENEC8rdfgpScEZyZoROdLHtE43MuSrVVBK6ee7kC5r2 lfTJs7x0ATOcJIy3vAyEkNvNBDJVcrBmYYAg5KFqiYIvDzZ0dr/A5aAHp+VdOsuBs0Uc Tqbg==
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=p9ORCNyieU/yRCy43F0O8tnupHGOhl7PPD9T9rkPT+k=; b=i1yfnimm4pIdCXRDI3hrCNbCuXSPTb5eEMToNA2tHx2U61jI5wtRxUD6iRUbs42tk6 1A4aHh8ZkvjBMzqR2CIJSrs9YU/sHMNq/fauQxY1FGprUv92XAx8oO0DXbhbBGoZLARK oxSFwlVO1w8CTgsiRtwnwxQLeCCYAM8RU6Q0ulJvhZvcL/ShjIVna2ubchQdVKDUMzG5 HJ+TQutQNTQlcCQYU5POH5R/ix+QjL/znln3iz12s5IPvnVa5TPB1eMWDfKX3xGqhYBQ PsS1mviIQjWaZr4Cm84TAgLJFtZR+9WC1ZvE1fHEAVXfVBKmsN4/6FAv/j/slvwln/60 xgiw==
X-Gm-Message-State: AOAM532JSrhuZ/WbSU8frUN7fzXy6h4lzeIeixhJpFiLyQu1IugD2E6I 1Dh9x0kYkoXYxFb9UB44qeaawqFTv8IluMZGA6A=
X-Google-Smtp-Source: ABdhPJzY56ONjNEooc9Errp2khvNsroLazriFKCu4kvC5EaHsErKuhoWdjSDEdvvyUKkvX/EsRSprSgHUCUgp6zB1QQ=
X-Received: by 2002:a4a:ae07:: with SMTP id z7mr301659oom.25.1595429291925; Wed, 22 Jul 2020 07:48:11 -0700 (PDT)
MIME-Version: 1.0
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com> <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org>
In-Reply-To: <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Wed, 22 Jul 2020 07:47:45 -0700
Message-ID: <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com>
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
To: Lars Eggert <lars@eggert.org>
Cc: Eric Rescorla <ekr@rtfm.com>, Mark Nottingham <mnot@mnot.net>, QUIC WG <quic@ietf.org>, Lucas Pardue <lucaspardue.24.7@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000035a50205ab08d465"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/n5GSzN7Wf6F2U-DxL73eOE3vJ5k>
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, 22 Jul 2020 14:48:15 -0000

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

If ekr's objections is that this is a hint, rather than more explicit, we
can incorporate Lars' point by a minor adjustment of the text:

OLD:

On confirming a peer's ownership of its new address, an endpoint MUST
immediately reset the congestion controller and round-trip time estimator
for
the new path to initial values (see Sections A.3 and B.3 in
{{QUIC-RECOVERY}})
unless it has knowledge that a previous send rate or round-trip time
estimate is
valid for the new path. For instance, an endpoint might infer that a change
in
only the client's port number is indicative of a NAT rebinding, meaning
that the
new path is likely to have similar bandwidth and round-trip time.


NEW:

On confirming a peer's ownership of its new address, an endpoint SHOULD
reset the congestion controller and round-trip time estimator for the new
path to
initial values (see Sections A.3 and B.3 in {{QUIC-RECOVERY}}) unless the
change is only to the client's port number.  Because port-only changes
are commonly the result of NAT rebinding or other middlebox activity,
the client MAY retain its estimation of the path bandwidth and round-trip
time
in those cases.  A conservative implementation may also revert to initial
values
in this case.

That shifts it from hint territory to explicit resolution.

regards,

Ted


On Wed, Jul 22, 2020 at 12:36 AM Lars Eggert <lars@eggert.org> wrote:

> Hi,
>
> On 2020-7-22, at 6:11, Eric Rescorla <ekr@rtfm.com> wrote:
> > As I said, I don't have a strong opinion about the outcome, but we
> shouldn't just hint to people that they should ignore the port.
>
> existing protocols basically just broke when a port or IP address changed
> (e.g., a NAT rebinding happened). So how to respond to this is something
> that we don't have existing IETF practice for AFAIK.
>
> The conservative approach would be to mandate a CC reset on any change to
> the four-tuple, since it indicates a possible path change.
>
> For clients in consumer access networks behind CPE NATs, that conservative
> approach is probably too conservative, since the CC-relevant properties of
> the path are unlikely to have changed if just the source port changed.
>
> On the other hand, with client side CGNs and server-side BALBs (big-ass
> load balancers...) a port change now maybe is more indicative of a path
> change. But it's not clear that this path change is more likely to affect
> the CC-relevant path characteristics.
>
> One final thing I'll point out is that all IETF transports have been
> happily ignoring at least one path change indication since forever - there
> is no mandated reaction to any change in the received IP TTL, and I'm also
> unaware of any implementation reacting to IP TTL changes (which would
> indicate a change in path length, something that probably would lead to
> CC-relevant changes in path characteristics.)
>
> That, together with the observation that CC will react to a path change
> anyway after an RTT due to loss/marks, leads me to believe we're probably
> OK to not reset CC on a port change. It might mean that we're sending for
> about an RTT at a rate that is too high in some rare (?) cases, but in the
> vast majority of cases, we'd avoid needless performance degradations.
>
> YMMV.
>
> Lars
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><div>If ekr&#39;s objections is that this=
 is a hint, rather than more explicit, we can incorporate Lars&#39; point b=
y a minor adjustment of the text:</div><div><br></div><div>OLD: <br></div><=
div><br></div><div>On confirming a peer&#39;s ownership of its new address,=
 an endpoint MUST<br>
immediately reset the congestion controller and round-trip time estimator f=
or<br>
the new path to initial values (see Sections A.3 and B.3 in {{QUIC-RECOVERY=
}})<br>
unless it has knowledge that a previous send rate or round-trip time estima=
te is<br>
valid for the new path.  For instance, an endpoint might infer that a chang=
e in<br>
only the client&#39;s port number is indicative of a NAT rebinding, meaning=
 that the<br>
new path is likely to have similar bandwidth and round-trip time.</div><div=
><br></div><div><br></div><div>NEW:</div><div><br></div><div>On confirming =
a peer&#39;s ownership of its new address, an endpoint SHOULD<br>reset the =
congestion controller and round-trip time estimator for the new path to <br=
></div><div>initial values (see Sections A.3 and B.3 in {{QUIC-RECOVERY}}) =
unless the <br></div><div>change is only to the client&#39;s port number.=
=C2=A0 Because port-only changes</div><div>are commonly the result of NAT r=
ebinding or other middlebox activity, <br><div>the client MAY retain its es=
timation of the path bandwidth and round-trip time</div><div>in those cases=
.=C2=A0 A conservative implementation may also revert to initial values</di=
v><div>in this case.</div><div><br></div><div>That shifts it from hint terr=
itory to explicit resolution.</div><div><br></div><div>regards,</div><div><=
br></div><div>Ted<br></div></div><div><br></div></div><br><div class=3D"gma=
il_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jul 22, 2020 at 12:=
36 AM Lars Eggert &lt;<a href=3D"mailto:lars@eggert.org">lars@eggert.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,=
<br>
<br>
On 2020-7-22, at 6:11, Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com" ta=
rget=3D"_blank">ekr@rtfm.com</a>&gt; wrote:<br>
&gt; As I said, I don&#39;t have a strong opinion about the outcome, but we=
 shouldn&#39;t just hint to people that they should ignore the port.<br>
<br>
existing protocols basically just broke when a port or IP address changed (=
e.g., a NAT rebinding happened). So how to respond to this is something tha=
t we don&#39;t have existing IETF practice for AFAIK.<br>
<br>
The conservative approach would be to mandate a CC reset on any change to t=
he four-tuple, since it indicates a possible path change.<br>
<br>
For clients in consumer access networks behind CPE NATs, that conservative =
approach is probably too conservative, since the CC-relevant properties of =
the path are unlikely to have changed if just the source port changed.<br>
<br>
On the other hand, with client side CGNs and server-side BALBs (big-ass loa=
d balancers...) a port change now maybe is more indicative of a path change=
. But it&#39;s not clear that this path change is more likely to affect the=
 CC-relevant path characteristics.<br>
<br>
One final thing I&#39;ll point out is that all IETF transports have been ha=
ppily ignoring at least one path change indication since forever - there is=
 no mandated reaction to any change in the received IP TTL, and I&#39;m als=
o unaware of any implementation reacting to IP TTL changes (which would ind=
icate a change in path length, something that probably would lead to CC-rel=
evant changes in path characteristics.)<br>
<br>
That, together with the observation that CC will react to a path change any=
way after an RTT due to loss/marks, leads me to believe we&#39;re probably =
OK to not reset CC on a port change. It might mean that we&#39;re sending f=
or about an RTT at a rate that is too high in some rare (?) cases, but in t=
he vast majority of cases, we&#39;d avoid needless performance degradations=
.<br>
<br>
YMMV.<br>
<br>
Lars<br>
</blockquote></div></div>

--00000000000035a50205ab08d465--


From nobody Wed Jul 22 09:45:40 2020
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 181D93A0AE3 for <quic@ietfa.amsl.com>; Wed, 22 Jul 2020 09:45:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.895
X-Spam-Level: 
X-Spam-Status: No, score=-1.895 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_BLOCKED=0.001, 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 j_uiA65VGb_a for <quic@ietfa.amsl.com>; Wed, 22 Jul 2020 09:45:37 -0700 (PDT)
Received: from mail-lf1-x12d.google.com (mail-lf1-x12d.google.com [IPv6:2a00:1450:4864:20::12d]) (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 06DE93A0AD6 for <quic@ietf.org>; Wed, 22 Jul 2020 09:45:37 -0700 (PDT)
Received: by mail-lf1-x12d.google.com with SMTP id u25so1707239lfm.1 for <quic@ietf.org>; Wed, 22 Jul 2020 09:45:36 -0700 (PDT)
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=2FFcAq4vF7r1l2IALOeecNM6lVM9EVJysgtzbqx5vmo=; b=kKBssdbP1jgznwKaFlcfSIZTLPtgZMrdFHhD/+1poCWxGCgO4PUgHn1jTObJAEw/R0 QT9lGKhnH9pMIleTK/tgJJOvXlbrdjoUjK3yMd/e6Cf8DxAyDFdj+zF1zAthKgnXr5qS xzqyW+rK7amUKs5yN3FyvUaXYOD6pyhchrkHxk/3GN60mj4hR1MWK03RnW2ta8QBu+te O441KbmLPBcv4/WTLwJFa2D0zgR+YRWXHZ4lUzcjasiH7sFt0HbWkITJzL737P4rRnr9 qenMDOhjZ6ZGiJ5bieoZ/Dt52v/W4+IAc3PaNSQBWhjMGdV8fLYxEaphQiUHyq/F89KT ZluQ==
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=2FFcAq4vF7r1l2IALOeecNM6lVM9EVJysgtzbqx5vmo=; b=jz014cHbNS650dxek/KgtHowFDqka6zPLW1u99W89x/yPOQcnK7WnucmZGSCALUlAH bepAnCg0pokZnqagzILBtaHGtPoO6ZxdfTX6gnV4/IPjkYFIMgah2XOZZGqIhb2dUVDd kGuV/Vex0ZtupSIl6BI6fkfEUaXutV+K0Pg2y/BTOqQ5T564K1h3qcxRvkrsfADf43oC sW4vtvBSyNKTToIukQbpB39ekcODpWbU9LIb7zp4r66gsSWw2o+SiFpQU7yDl1HFkgKV 3xPjThmYopjUQyjMGZvPc0cHGftX29ByFB3U5UG3CdZDsvKuZO2NSqxjW1M4FWrHlSAG M5Gg==
X-Gm-Message-State: AOAM531fuGyC6d99ZnPy0YNK6FkezOHrhWd2xYxY3C7DScUu0U+f21AA PjFHgdt5lsQH2dI8HwBiNwMzXC3Uj9TUc5eG72GNCQ==
X-Google-Smtp-Source: ABdhPJw4jzzGJKzDOQozFPqDI+BEOZl8MmSrywQEC7px+68B5+4zsT0iQI+eGltoDF+KvR4sEDgenboHUzgBjfW1R5w=
X-Received: by 2002:a05:6512:3156:: with SMTP id s22mr130185lfi.140.1595436335093;  Wed, 22 Jul 2020 09:45:35 -0700 (PDT)
MIME-Version: 1.0
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com> <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org> <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com>
In-Reply-To: <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com>
From: Eric Rescorla <ekr@rtfm.com>
Date: Wed, 22 Jul 2020 09:44:58 -0700
Message-ID: <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com>
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
To: Ted Hardie <ted.ietf@gmail.com>
Cc: Lars Eggert <lars@eggert.org>, Mark Nottingham <mnot@mnot.net>, QUIC WG <quic@ietf.org>, Lucas Pardue <lucaspardue.24.7@gmail.com>
Content-Type: multipart/alternative; boundary="00000000000003edfc05ab0a7841"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/9THxgRysNVKqzcb5OZPLyUnipoM>
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, 22 Jul 2020 16:45:39 -0000

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

Ted's proposal would be acceptable to me.

-Ekr


On Wed, Jul 22, 2020 at 7:48 AM Ted Hardie <ted.ietf@gmail.com> wrote:

> If ekr's objections is that this is a hint, rather than more explicit, we
> can incorporate Lars' point by a minor adjustment of the text:
>
> OLD:
>
> On confirming a peer's ownership of its new address, an endpoint MUST
> immediately reset the congestion controller and round-trip time estimator
> for
> the new path to initial values (see Sections A.3 and B.3 in
> {{QUIC-RECOVERY}})
> unless it has knowledge that a previous send rate or round-trip time
> estimate is
> valid for the new path. For instance, an endpoint might infer that a
> change in
> only the client's port number is indicative of a NAT rebinding, meaning
> that the
> new path is likely to have similar bandwidth and round-trip time.
>
>
> NEW:
>
> On confirming a peer's ownership of its new address, an endpoint SHOULD
> reset the congestion controller and round-trip time estimator for the new
> path to
> initial values (see Sections A.3 and B.3 in {{QUIC-RECOVERY}}) unless the
> change is only to the client's port number.  Because port-only changes
> are commonly the result of NAT rebinding or other middlebox activity,
> the client MAY retain its estimation of the path bandwidth and round-trip
> time
> in those cases.  A conservative implementation may also revert to initial
> values
> in this case.
>
> That shifts it from hint territory to explicit resolution.
>
> regards,
>
> Ted
>
>
> On Wed, Jul 22, 2020 at 12:36 AM Lars Eggert <lars@eggert.org> wrote:
>
>> Hi,
>>
>> On 2020-7-22, at 6:11, Eric Rescorla <ekr@rtfm.com> wrote:
>> > As I said, I don't have a strong opinion about the outcome, but we
>> shouldn't just hint to people that they should ignore the port.
>>
>> existing protocols basically just broke when a port or IP address changed
>> (e.g., a NAT rebinding happened). So how to respond to this is something
>> that we don't have existing IETF practice for AFAIK.
>>
>> The conservative approach would be to mandate a CC reset on any change to
>> the four-tuple, since it indicates a possible path change.
>>
>> For clients in consumer access networks behind CPE NATs, that
>> conservative approach is probably too conservative, since the CC-relevant
>> properties of the path are unlikely to have changed if just the source port
>> changed.
>>
>> On the other hand, with client side CGNs and server-side BALBs (big-ass
>> load balancers...) a port change now maybe is more indicative of a path
>> change. But it's not clear that this path change is more likely to affect
>> the CC-relevant path characteristics.
>>
>> One final thing I'll point out is that all IETF transports have been
>> happily ignoring at least one path change indication since forever - there
>> is no mandated reaction to any change in the received IP TTL, and I'm also
>> unaware of any implementation reacting to IP TTL changes (which would
>> indicate a change in path length, something that probably would lead to
>> CC-relevant changes in path characteristics.)
>>
>> That, together with the observation that CC will react to a path change
>> anyway after an RTT due to loss/marks, leads me to believe we're probably
>> OK to not reset CC on a port change. It might mean that we're sending for
>> about an RTT at a rate that is too high in some rare (?) cases, but in the
>> vast majority of cases, we'd avoid needless performance degradations.
>>
>> YMMV.
>>
>> Lars
>>
>

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

<div dir=3D"ltr"><div>Ted&#39;s proposal would be acceptable to me.</div><d=
iv><br></div><div>-Ekr</div><div><br></div></div><br><div class=3D"gmail_qu=
ote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jul 22, 2020 at 7:48 AM =
Ted Hardie &lt;<a href=3D"mailto:ted.ietf@gmail.com">ted.ietf@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"><div dir=3D"ltr"><div>If ekr&#39;s objections is that this is =
a hint, rather than more explicit, we can incorporate Lars&#39; point by a =
minor adjustment of the text:</div><div><br></div><div>OLD: <br></div><div>=
<br></div><div>On confirming a peer&#39;s ownership of its new address, an =
endpoint MUST<br>
immediately reset the congestion controller and round-trip time estimator f=
or<br>
the new path to initial values (see Sections A.3 and B.3 in {{QUIC-RECOVERY=
}})<br>
unless it has knowledge that a previous send rate or round-trip time estima=
te is<br>
valid for the new path.  For instance, an endpoint might infer that a chang=
e in<br>
only the client&#39;s port number is indicative of a NAT rebinding, meaning=
 that the<br>
new path is likely to have similar bandwidth and round-trip time.</div><div=
><br></div><div><br></div><div>NEW:</div><div><br></div><div>On confirming =
a peer&#39;s ownership of its new address, an endpoint SHOULD<br>reset the =
congestion controller and round-trip time estimator for the new path to <br=
></div><div>initial values (see Sections A.3 and B.3 in {{QUIC-RECOVERY}}) =
unless the <br></div><div>change is only to the client&#39;s port number.=
=C2=A0 Because port-only changes</div><div>are commonly the result of NAT r=
ebinding or other middlebox activity, <br><div>the client MAY retain its es=
timation of the path bandwidth and round-trip time</div><div>in those cases=
.=C2=A0 A conservative implementation may also revert to initial values</di=
v><div>in this case.</div><div><br></div><div>That shifts it from hint terr=
itory to explicit resolution.</div><div><br></div><div>regards,</div><div><=
br></div><div>Ted<br></div></div><div><br></div></div><br><div class=3D"gma=
il_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jul 22, 2020 at 12:=
36 AM Lars Eggert &lt;<a href=3D"mailto:lars@eggert.org" target=3D"_blank">=
lars@eggert.org</a>&gt; wrote:<br></div><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">Hi,<br>
<br>
On 2020-7-22, at 6:11, Eric Rescorla &lt;<a href=3D"mailto:ekr@rtfm.com" ta=
rget=3D"_blank">ekr@rtfm.com</a>&gt; wrote:<br>
&gt; As I said, I don&#39;t have a strong opinion about the outcome, but we=
 shouldn&#39;t just hint to people that they should ignore the port.<br>
<br>
existing protocols basically just broke when a port or IP address changed (=
e.g., a NAT rebinding happened). So how to respond to this is something tha=
t we don&#39;t have existing IETF practice for AFAIK.<br>
<br>
The conservative approach would be to mandate a CC reset on any change to t=
he four-tuple, since it indicates a possible path change.<br>
<br>
For clients in consumer access networks behind CPE NATs, that conservative =
approach is probably too conservative, since the CC-relevant properties of =
the path are unlikely to have changed if just the source port changed.<br>
<br>
On the other hand, with client side CGNs and server-side BALBs (big-ass loa=
d balancers...) a port change now maybe is more indicative of a path change=
. But it&#39;s not clear that this path change is more likely to affect the=
 CC-relevant path characteristics.<br>
<br>
One final thing I&#39;ll point out is that all IETF transports have been ha=
ppily ignoring at least one path change indication since forever - there is=
 no mandated reaction to any change in the received IP TTL, and I&#39;m als=
o unaware of any implementation reacting to IP TTL changes (which would ind=
icate a change in path length, something that probably would lead to CC-rel=
evant changes in path characteristics.)<br>
<br>
That, together with the observation that CC will react to a path change any=
way after an RTT due to loss/marks, leads me to believe we&#39;re probably =
OK to not reset CC on a port change. It might mean that we&#39;re sending f=
or about an RTT at a rate that is too high in some rare (?) cases, but in t=
he vast majority of cases, we&#39;d avoid needless performance degradations=
.<br>
<br>
YMMV.<br>
<br>
Lars<br>
</blockquote></div></div>
</blockquote></div>

--00000000000003edfc05ab0a7841--


From nobody Wed Jul 22 10:48:31 2020
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 D987A3A08CC for <quic@ietfa.amsl.com>; Wed, 22 Jul 2020 10:48:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.698
X-Spam-Level: 
X-Spam-Status: No, score=-0.698 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 yZY0rB67T2kA for <quic@ietfa.amsl.com>; Wed, 22 Jul 2020 10:48:28 -0700 (PDT)
Received: from mail-il1-x12f.google.com (mail-il1-x12f.google.com [IPv6:2607:f8b0:4864:20::12f]) (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 B44433A08CB for <quic@ietf.org>; Wed, 22 Jul 2020 10:48:28 -0700 (PDT)
Received: by mail-il1-x12f.google.com with SMTP id t4so2060355iln.1 for <quic@ietf.org>; Wed, 22 Jul 2020 10:48:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=AN1mDXvlG1bc1UNjB7LUbqUYE4YRZGmeMFKPAggjOy0=; b=cF6jdlSRcxN1nawYawZPIpjw8c76eGdj8ekzWPB/frxEpr97kQ93IX388kaVB91K23 g7CP6oyuf8/7PgtDhO0LxOlBoD31M1ueI2KyAbMaMm+rgkbEZUeMZH8UGfbkGvUNuj3g h5/IqG8zNddBK/yQvZaBmWz4EvoqKsOKTdtv1EdVLDvZpmvglP1vdYxt0aOOGUcR0gEV aKHGov5iCwRJAvngXSF20/k+PKMho3fWn5+lRjhtAOdOic0WAxZSXoHmz7BzXqHRsP3k smjj76LSLimxTJVHl/H1WSkIyjCOmfkru6ldLXLIifkAGe3GjZt4q/xbhRvG/sboRpi1 fhog==
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=AN1mDXvlG1bc1UNjB7LUbqUYE4YRZGmeMFKPAggjOy0=; b=GUs2qr/eA1bQyBkAEiMSsy4wLsH5kz9JpgA4vpVV9/pbYASe4Erw/iWo/9AbQxwU0m hTzNIWAmueSK4SI8QT3yW4ZX/rq4miUS/etyTLna70q+u6ENJOII7Kc+8FXvAoEaAMjU cb7OOi8ZItCZD5LcGfJjuMe2r3f/lyV6kY0C7PYgr1G10BNDtuF4EA0Sac+lwxVaVxnU LRoF5a8AE+h2WquMiuFq8j0sohCB0c/3LL8V52QowqwhV0Vo9i0oYxW0v1dnGnOFiE4I s8KvQ8aLDGI8EURNWlEF58ms80SUyZ2Ss18mzkTAVM7dNlYu3hpTgDwO0ymf//XNmL2f AQdA==
X-Gm-Message-State: AOAM533yFSlxczKGRW/nWBRor5n6hK4pBgnXNrTpjDm45ObOnvMmcUnG 1ytBeWuiJCnoafS7CIaJWhUSUm0KIowK0HnJTPrcj6aa
X-Google-Smtp-Source: ABdhPJwQSnNjNdNT/x5ABkcAoyDg1AJoY3RK+0P2aYV3MPZ4NSKfA9+78B1IdEshYvFSNvzpBpIHAMY8Oh2mt1p/q+U=
X-Received: by 2002:a92:db01:: with SMTP id b1mr973354iln.249.1595440107641; Wed, 22 Jul 2020 10:48:27 -0700 (PDT)
MIME-Version: 1.0
From: Martin Duke <martin.h.duke@gmail.com>
Date: Wed, 22 Jul 2020 10:48:16 -0700
Message-ID: <CAM4esxQWjU_QoqAns2DSAAGCaaiOJu0n9JeVvmgYUB2cARoYoQ@mail.gmail.com>
Subject: QUIC-LB open source repo available
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000e0619105ab0b589c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/BsNbR9Geuzafys_epTVlLCNZB4w>
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, 22 Jul 2020 17:48:30 -0000

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

Hello,

I've finally worn down enough lawyers to open-source my QUIC-LB code:
https://github.com/f5networks/quic-lb.git

Please have a look. It's ported over from our data plane microkernel, so
there are some weird C commands but it compiles in Ubuntu.

Martin

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

<div dir=3D"ltr">Hello,<div><br></div><div>I&#39;ve finally worn down enoug=
h lawyers to open-source my QUIC-LB code:</div><div><a href=3D"https://gith=
ub.com/f5networks/quic-lb.git">https://github.com/f5networks/quic-lb.git</a=
></div><div><br></div><div>Please have a look. It&#39;s ported over from ou=
r data plane microkernel, so there are some weird C commands but it compile=
s in Ubuntu.</div><div><br></div><div>Martin</div></div>

--000000000000e0619105ab0b589c--


From nobody Wed Jul 22 12:43:34 2020
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 8D6EB3A0861 for <quic@ietfa.amsl.com>; Wed, 22 Jul 2020 12:43:33 -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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, 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 zFsfZcK1e8Ix for <quic@ietfa.amsl.com>; Wed, 22 Jul 2020 12:43:31 -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 68E2E3A082F for <quic@ietf.org>; Wed, 22 Jul 2020 12:43:31 -0700 (PDT)
Received: from xse428.mail2web.com ([66.113.197.174] helo=xse.mail2web.com) by mx169.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1jyKeD-000mir-5B for quic@ietf.org; Wed, 22 Jul 2020 21:43:26 +0200
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 4BBm955sZqzP7J for <quic@ietf.org>; Wed, 22 Jul 2020 12:43:21 -0700 (PDT)
Received: from [10.5.2.31] (helo=xmail09.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 1jyKe9-0007S1-Me for quic@ietf.org; Wed, 22 Jul 2020 12:43:21 -0700
Received: (qmail 20762 invoked from network); 22 Jul 2020 19:43:21 -0000
Received: from unknown (HELO [192.168.1.107]) (Authenticated-user:_huitema@huitema.net@[172.58.43.134]) (envelope-sender <huitema@huitema.net>) by xmail09.myhosting.com (qmail-ldap-1.03) with ESMTPA for <lucaspardue.24.7@gmail.com>; 22 Jul 2020 19:43:20 -0000
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
To: Eric Rescorla <ekr@rtfm.com>, Ted Hardie <ted.ietf@gmail.com>
Cc: Lars Eggert <lars@eggert.org>, Mark Nottingham <mnot@mnot.net>, QUIC WG <quic@ietf.org>, Lucas Pardue <lucaspardue.24.7@gmail.com>
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com> <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org> <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com> <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com>
From: Christian Huitema <huitema@huitema.net>
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mDMEXtavGxYJKwYBBAHaRw8BAQdA1ou9A5MHTP9N3jfsWzlDZ+jPnQkusmc7sfLmWVz1Rmu0 J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PoiWBBMWCAA+FiEEw3G4 Nwi4QEpAAXUUELAmqKBYtJQFAl7WrxsCGwMFCQlmAYAFCwkIBwIGFQoJCAsCBBYCAwECHgEC F4AACgkQELAmqKBYtJQbMwD/ebj/qnSbthC/5kD5DxZ/Ip0CGJw5QBz/+fJp3R8iAlsBAMjK r2tmyWyJz0CUkVG24WaR5EAJDvgwDv8h22U6QVkAuDgEXtavGxIKKwYBBAGXVQEFAQEHQJoM 6MUAIqpoqdCIiACiEynZf7nlJg2Eu0pXIhbUGONdAwEIB4h+BBgWCAAmFiEEw3G4Nwi4QEpA AXUUELAmqKBYtJQFAl7WrxsCGwwFCQlmAYAACgkQELAmqKBYtJRm2wD7BzeK5gEXSmBcBf0j BYdSaJcXNzx4yPLbP4GnUMAyl2cBAJzcsR4RkwO4dCRqM9CHpVJCwHtbUDJaa55//E0kp+gH
Message-ID: <7b5c104c-36b6-3fe1-4e5b-0e42cc9e2b36@huitema.net>
Date: Wed, 22 Jul 2020 12:43:21 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------69C8CA2AE2785716F4EB6D43"
Content-Language: en-US
X-Originating-IP: 66.113.197.174
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/gcnlw0bN4ZX/cCaR95pQ7tQtUF1ypSDasLI4SayDByyq9LIhVUZbR67CQ7/vm /hHDJU4RXkTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDcnqpk5VeF3xR4kF6iVwRtbgN zB/4Jkrw1eDLcif59fszSuMHPLVZvLNOwN5rVpUNU7Tmz6iKnkQL9gqsxD347235Nhqq+/HvroPq 8GSPg+60/QPNqXybIny9WGhadIo/1Ofn8DBBgDynfYj8uZOR2ryme9ldZJ7uNXfg/GfS8fUvP/L5 rCqHDsKZM+xa1iwJX+gRCHfMVnsAk591zk0uilUI+ZL4xWiN8NS6C+dmX6OEdA4u1aThyWrQ/ou2 +v/lmX4Em37yFgrCB6NHRn1g+f3uncIqYSL3lhh5c81YyJqFoLZMmkWsaurVZfvqROaDnDtHb8z5 dpPkEuJ8Snwqla7jUnW3hy14Yji8fo+4xCnSRo4Rcu5Z37rMuDjCny5fE9ykbJ7I9co1MAEE3ruN Xsm8UJsAPvDcVSKtDCYkioPY5Qx4fJOk03R5fJtf/Dv/dkIzS7m4GUpXCY1Y3j3ilQ8EW2aDkYIa 2M5pALviQra5n1qAU0VTFRks+evUvJt4cT+Y/W7XixFpst4JJaOWk2WYWZklmQWcks6m3uEEh4Yx iMxSpkvqIEtRL3s4ePxvne6Agjui5gKB/Byw/yqfyPKY2AXNZGS5G93aGyH8MqMlOQRMVMd0HCeT skOZ5TL8EgBzO2N8W+D9hoCS1s3CqjXg724gFzhHYUe+7aKm0vXf5SWGL+ryYYWrBrQkvWAdTi+J 2sBvM/O0p+zizleC4va6FPcpDHjXMKZJK8+chia8f00y7fhd1S09XptghsgW7cTs80/2FnZg/IMs IAdedSzLrjsyfTPCYbMCLdmf5h2vfxw3Qvb2Glio5Cia/9Kfg4kJ0WtAYbrpe3OOAtQNb87OBHCz Hbokiue7PjVB1S6AQRz4SqXhOP5fdiQt7lu5Jm5nk4BSgYHOJJgUtm67rBRli6kULE5BQDZnPvvF VsQ=
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/3lul7Wkvmk4Nm7V_yJJDv4VUsAY>
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, 22 Jul 2020 19:43:34 -0000

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

Sounds good to me too.

-- Christian Huitema

On 7/22/2020 9:44 AM, Eric Rescorla wrote:
> Ted's proposal would be acceptable to me.
>
> -Ekr
>
>
> On Wed, Jul 22, 2020 at 7:48 AM Ted Hardie <ted.ietf@gmail.com
> <mailto:ted.ietf@gmail.com>> wrote:
>
>     If ekr's objections is that this is a hint, rather than more
>     explicit, we can incorporate Lars' point by a minor adjustment of
>     the text:
>
>     OLD:
>
>     On confirming a peer's ownership of its new address, an endpoint MUST
>     immediately reset the congestion controller and round-trip time
>     estimator for
>     the new path to initial values (see Sections A.3 and B.3 in
>     {{QUIC-RECOVERY}})
>     unless it has knowledge that a previous send rate or round-trip
>     time estimate is
>     valid for the new path. For instance, an endpoint might infer that
>     a change in
>     only the client's port number is indicative of a NAT rebinding,
>     meaning that the
>     new path is likely to have similar bandwidth and round-trip time.
>
>
>     NEW:
>
>     On confirming a peer's ownership of its new address, an endpoint
>     SHOULD
>     reset the congestion controller and round-trip time estimator for
>     the new path to
>     initial values (see Sections A.3 and B.3 in {{QUIC-RECOVERY}})
>     unless the
>     change is only to the client's port number.  Because port-only changes
>     are commonly the result of NAT rebinding or other middlebox activity,
>     the client MAY retain its estimation of the path bandwidth and
>     round-trip time
>     in those cases..  A conservative implementation may also revert to
>     initial values
>     in this case.
>
>     That shifts it from hint territory to explicit resolution.
>
>     regards,
>
>     Ted
>
>
>     On Wed, Jul 22, 2020 at 12:36 AM Lars Eggert <lars@eggert.org
>     <mailto:lars@eggert.org>> wrote:
>
>         Hi,
>
>         On 2020-7-22, at 6:11, Eric Rescorla <ekr@rtfm.com
>         <mailto:ekr@rtfm.com>> wrote:
>         > As I said, I don't have a strong opinion about the outcome,
>         but we shouldn't just hint to people that they should ignore
>         the port.
>
>         existing protocols basically just broke when a port or IP
>         address changed (e.g., a NAT rebinding happened). So how to
>         respond to this is something that we don't have existing IETF
>         practice for AFAIK.
>
>         The conservative approach would be to mandate a CC reset on
>         any change to the four-tuple, since it indicates a possible
>         path change.
>
>         For clients in consumer access networks behind CPE NATs, that
>         conservative approach is probably too conservative, since the
>         CC-relevant properties of the path are unlikely to have
>         changed if just the source port changed.
>
>         On the other hand, with client side CGNs and server-side BALBs
>         (big-ass load balancers...) a port change now maybe is more
>         indicative of a path change.. But it's not clear that this
>         path change is more likely to affect the CC-relevant path
>         characteristics.
>
>         One final thing I'll point out is that all IETF transports
>         have been happily ignoring at least one path change indication
>         since forever - there is no mandated reaction to any change in
>         the received IP TTL, and I'm also unaware of any
>         implementation reacting to IP TTL changes (which would
>         indicate a change in path length, something that probably
>         would lead to CC-relevant changes in path characteristics.)
>
>         That, together with the observation that CC will react to a
>         path change anyway after an RTT due to loss/marks, leads me to
>         believe we're probably OK to not reset CC on a port change. It
>         might mean that we're sending for about an RTT at a rate that
>         is too high in some rare (?) cases, but in the vast majority
>         of cases, we'd avoid needless performance degradations..
>
>         YMMV.
>
>         Lars
>

--------------69C8CA2AE2785716F4EB6D43
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>Sounds good to me too.</p>
    <p>-- Christian Huitema<br>
    </p>
    <div class="moz-cite-prefix">On 7/22/2020 9:44 AM, Eric Rescorla
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div>Ted's proposal would be acceptable to me.</div>
        <div><br>
        </div>
        <div>-Ekr</div>
        <div><br>
        </div>
      </div>
      <br>
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Wed, Jul 22, 2020 at 7:48
          AM Ted Hardie &lt;<a href="mailto:ted.ietf@gmail.com"
            moz-do-not-send="true">ted.ietf@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 dir="ltr">
            <div dir="ltr">
              <div>If ekr's objections is that this is a hint, rather
                than more explicit, we can incorporate Lars' point by a
                minor adjustment of the text:</div>
              <div><br>
              </div>
              <div>OLD: <br>
              </div>
              <div><br>
              </div>
              <div>On confirming a peer's ownership of its new address,
                an endpoint MUST<br>
                immediately reset the congestion controller and
                round-trip time estimator for<br>
                the new path to initial values (see Sections A.3 and B.3
                in {{QUIC-RECOVERY}})<br>
                unless it has knowledge that a previous send rate or
                round-trip time estimate is<br>
                valid for the new path. For instance, an endpoint might
                infer that a change in<br>
                only the client's port number is indicative of a NAT
                rebinding, meaning that the<br>
                new path is likely to have similar bandwidth and
                round-trip time.</div>
              <div><br>
              </div>
              <div><br>
              </div>
              <div>NEW:</div>
              <div><br>
              </div>
              <div>On confirming a peer's ownership of its new address,
                an endpoint SHOULD<br>
                reset the congestion controller and round-trip time
                estimator for the new path to <br>
              </div>
              <div>initial values (see Sections A.3 and B.3 in
                {{QUIC-RECOVERY}}) unless the <br>
              </div>
              <div>change is only to the client's port number.  Because
                port-only changes</div>
              <div>are commonly the result of NAT rebinding or other
                middlebox activity, <br>
                <div>the client MAY retain its estimation of the path
                  bandwidth and round-trip time</div>
                <div>in those cases..  A conservative implementation may
                  also revert to initial values</div>
                <div>in this case.</div>
                <div><br>
                </div>
                <div>That shifts it from hint territory to explicit
                  resolution.</div>
                <div><br>
                </div>
                <div>regards,</div>
                <div><br>
                </div>
                <div>Ted<br>
                </div>
              </div>
              <div><br>
              </div>
            </div>
            <br>
            <div class="gmail_quote">
              <div dir="ltr" class="gmail_attr">On Wed, Jul 22, 2020 at
                12:36 AM Lars Eggert &lt;<a
                  href="mailto:lars@eggert.org" target="_blank"
                  moz-do-not-send="true">lars@eggert.org</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">Hi,<br>
                <br>
                On 2020-7-22, at 6:11, Eric Rescorla &lt;<a
                  href="mailto:ekr@rtfm.com" target="_blank"
                  moz-do-not-send="true">ekr@rtfm.com</a>&gt; wrote:<br>
                &gt; As I said, I don't have a strong opinion about the
                outcome, but we shouldn't just hint to people that they
                should ignore the port.<br>
                <br>
                existing protocols basically just broke when a port or
                IP address changed (e.g., a NAT rebinding happened). So
                how to respond to this is something that we don't have
                existing IETF practice for AFAIK.<br>
                <br>
                The conservative approach would be to mandate a CC reset
                on any change to the four-tuple, since it indicates a
                possible path change.<br>
                <br>
                For clients in consumer access networks behind CPE NATs,
                that conservative approach is probably too conservative,
                since the CC-relevant properties of the path are
                unlikely to have changed if just the source port
                changed.<br>
                <br>
                On the other hand, with client side CGNs and server-side
                BALBs (big-ass load balancers...) a port change now
                maybe is more indicative of a path change.. But it's not
                clear that this path change is more likely to affect the
                CC-relevant path characteristics.<br>
                <br>
                One final thing I'll point out is that all IETF
                transports have been happily ignoring at least one path
                change indication since forever - there is no mandated
                reaction to any change in the received IP TTL, and I'm
                also unaware of any implementation reacting to IP TTL
                changes (which would indicate a change in path length,
                something that probably would lead to CC-relevant
                changes in path characteristics.)<br>
                <br>
                That, together with the observation that CC will react
                to a path change anyway after an RTT due to loss/marks,
                leads me to believe we're probably OK to not reset CC on
                a port change. It might mean that we're sending for
                about an RTT at a rate that is too high in some rare (?)
                cases, but in the vast majority of cases, we'd avoid
                needless performance degradations..<br>
                <br>
                YMMV.<br>
                <br>
                Lars<br>
              </blockquote>
            </div>
          </div>
        </blockquote>
      </div>
    </blockquote>
  </body>
</html>

--------------69C8CA2AE2785716F4EB6D43--


From nobody Wed Jul 22 17:36:47 2020
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 020B83A0A86 for <quic@ietfa.amsl.com>; Wed, 22 Jul 2020 17:36:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.12
X-Spam-Level: 
X-Spam-Status: No, score=-2.12 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, 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=BgW9Gckz; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=i8d5f3V/
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 4tb6H6splHMK for <quic@ietfa.amsl.com>; Wed, 22 Jul 2020 17:36:44 -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 5D5CA3A0A87 for <quic@ietf.org>; Wed, 22 Jul 2020 17:36:44 -0700 (PDT)
Received: from compute2.internal (compute2.nyi.internal [10.202.2.42]) by mailout.nyi.internal (Postfix) with ESMTP id DBDDC5C00C5 for <quic@ietf.org>; Wed, 22 Jul 2020 20:36:42 -0400 (EDT)
Received: from imap2 ([10.202.2.52]) by compute2.internal (MEProxy); Wed, 22 Jul 2020 20:36:42 -0400
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=fm2; bh=4Xui95SE4X4arUwQWVJRkW13vQzjjaZ uIRhopEaBH+k=; b=BgW9GckzW2xo3mbzEPHWvuK5MWzRxZLtQaNL4BnloN43ND3 JaNH83giRv3OD932qKC4Z8fQGZDXxT4lFx64iBn2pfBFdenQZqif17orRIF19ZnP mqaQndbm9CFFGNxGNIWrQ6jEBts4QA5v4Z+BVquZ9FbCgp5pseTb9pANhxSFqbFE XGkAda3NDloP2/kd/uheGZKcVbvU2Nd9bMP150RlzIEintNY8Gw6PB8hC/AOQ9zk GtW8dw9oPC+4xJZUUnRjQS7/zFiIwBF9+RnUvdv4GcYLoutL78B/NnRqCw7T4V2F 3L6OyNOi1SmhP3ay4QJkYGeoY8nVXP4hu3TT4mw==
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=fm3; bh=4Xui95 SE4X4arUwQWVJRkW13vQzjjaZuIRhopEaBH+k=; b=i8d5f3V/aGLtH8bJF3ywa5 bs4hXY0l2bwOX9vuYUt7leR17RYa7hcZvffuqGTlcmW30u7jilrInlMHxkWZ/iQt mSD7lsVtsCz6nn7g+5GYisJUo1qoBwjWfrKh6iMQRjFzftfBi1LEfKgZcSo9KLCY OdAVh8tzHcsB7v2yg1nV1xL1zjE4wJ8xjN0bQ807pov0QLOjgaxUTKuSpNttQDNU 0RCE+ZyhZRaccgwWXcVyoFgW3IX2QZJT2qPfLuk5MuQI+KFUANW3ZXpYS2sOgbYc WZsRP6uy7flXImILfGy4R+gly9bGZrVfdg+wkDDNPvhD1UA/UOnmbjkQg5eSf+mQ ==
X-ME-Sender: <xms:mtsYX59tRTwNPJxIHQEMafmUO5jyoNbR3hUsu9HA-TxLAlU1m08ARw>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrhedtgdefkecutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecunecujfgurhepofgfggfkjghffffhvffutgesthdtre dtreertdenucfhrhhomhepfdforghrthhinhcuvfhhohhmshhonhdfuceomhhtsehlohif vghnthhrohhphidrnhgvtheqnecuggftrfgrthhtvghrnhepkeetueeikedtkeelfeekve fhkeffvedvvefgkefgleeugfdvjeejgeffieegtdejnecuvehluhhsthgvrhfuihiivgep tdenucfrrghrrghmpehmrghilhhfrhhomhepmhhtsehlohifvghnthhrohhphidrnhgvth
X-ME-Proxy: <xmx:mtsYX9uilkKPQUQVqx3lw436qN1WaHster4MJfs9dm7KIpTLQkynBg> <xmx:mtsYX3BxuLMGZ0ZtDF2Ox6huVSUgL2guksj477nQczpJR4dE97pX-w> <xmx:mtsYX9dYljNtebXxfaeoBTVN6qmZhCBKEgF_4DUsvaQIwm3_z1Pg6A> <xmx:mtsYXwtaFHnXCR9eeoZnUs-py091OpqkopNP_eRrh_VZ24KbaAc-oA>
Received: by mailuser.nyi.internal (Postfix, from userid 501) id 685DDE00A8; Wed, 22 Jul 2020 20:36:42 -0400 (EDT)
X-Mailer: MessagingEngine.com Webmail Interface
User-Agent: Cyrus-JMAP/3.3.0-92-g11c785d-fm-20200721.004-g11c785d5
Mime-Version: 1.0
Message-Id: <74ef5430-8e3f-4b6b-b81f-b25443e975b4@www.fastmail.com>
In-Reply-To: <7b5c104c-36b6-3fe1-4e5b-0e42cc9e2b36@huitema.net>
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com> <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org> <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com> <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com> <7b5c104c-36b6-3fe1-4e5b-0e42cc9e2b36@huitema.net>
Date: Thu, 23 Jul 2020 10:36:23 +1000
From: "Martin Thomson" <mt@lowentropy.net>
To: quic@ietf.org
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
Content-Type: text/plain
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/wlgxbfQZ-5naB5gXPUaPr-JQ1AI>
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, 23 Jul 2020 00:36:46 -0000

Is the intent to avoid talking about what knowledge an endpoint might use to decide to transfer state?

On Thu, Jul 23, 2020, at 05:43, Christian Huitema wrote:
> Sounds good to me too.
> 
> -- Christian Huitema
> 
> On 7/22/2020 9:44 AM, Eric Rescorla wrote:
> > Ted's proposal would be acceptable to me.
> > 
> > -Ekr
> > 
> > 
> > On Wed, Jul 22, 2020 at 7:48 AM Ted Hardie <ted.ietf@gmail.com> wrote:
> >> If ekr's objections is that this is a hint, rather than more explicit, we can incorporate Lars' point by a minor adjustment of the text:
> >> 
> >> OLD: 
> >> 
> >> On confirming a peer's ownership of its new address, an endpoint MUST
> >> immediately reset the congestion controller and round-trip time estimator for
> >> the new path to initial values (see Sections A.3 and B.3 in {{QUIC-RECOVERY}})
> >> unless it has knowledge that a previous send rate or round-trip time estimate is
> >> valid for the new path. For instance, an endpoint might infer that a change in
> >> only the client's port number is indicative of a NAT rebinding, meaning that the
> >> new path is likely to have similar bandwidth and round-trip time.
> >> 
> >> 
> >> NEW:
> >> 
> >> On confirming a peer's ownership of its new address, an endpoint SHOULD
> >> reset the congestion controller and round-trip time estimator for the new path to 
> >> initial values (see Sections A.3 and B.3 in {{QUIC-RECOVERY}}) unless the 
> >> change is only to the client's port number.  Because port-only changes
> >> are commonly the result of NAT rebinding or other middlebox activity, 
> >> the client MAY retain its estimation of the path bandwidth and round-trip time
> >> in those cases..  A conservative implementation may also revert to initial values
> >> in this case.
> >> 
> >> That shifts it from hint territory to explicit resolution.
> >> 
> >> regards,
> >> 
> >> Ted
> >> 
> >> 
> >> On Wed, Jul 22, 2020 at 12:36 AM Lars Eggert <lars@eggert.org> wrote:
> >>> Hi,
> >>> 
> >>> On 2020-7-22, at 6:11, Eric Rescorla <ekr@rtfm.com> wrote:
> >>> > As I said, I don't have a strong opinion about the outcome, but we shouldn't just hint to people that they should ignore the port.
> >>> 
> >>> existing protocols basically just broke when a port or IP address changed (e.g., a NAT rebinding happened). So how to respond to this is something that we don't have existing IETF practice for AFAIK.
> >>> 
> >>> The conservative approach would be to mandate a CC reset on any change to the four-tuple, since it indicates a possible path change.
> >>> 
> >>> For clients in consumer access networks behind CPE NATs, that conservative approach is probably too conservative, since the CC-relevant properties of the path are unlikely to have changed if just the source port changed.
> >>> 
> >>> On the other hand, with client side CGNs and server-side BALBs (big-ass load balancers...) a port change now maybe is more indicative of a path change.. But it's not clear that this path change is more likely to affect the CC-relevant path characteristics.
> >>> 
> >>> One final thing I'll point out is that all IETF transports have been happily ignoring at least one path change indication since forever - there is no mandated reaction to any change in the received IP TTL, and I'm also unaware of any implementation reacting to IP TTL changes (which would indicate a change in path length, something that probably would lead to CC-relevant changes in path characteristics.)
> >>> 
> >>> That, together with the observation that CC will react to a path change anyway after an RTT due to loss/marks, leads me to believe we're probably OK to not reset CC on a port change. It might mean that we're sending for about an RTT at a rate that is too high in some rare (?) cases, but in the vast majority of cases, we'd avoid needless performance degradations..
> >>> 
> >>> YMMV.
> >>> 
> >>> Lars


From nobody Wed Jul 22 22:43:56 2020
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 BFB5E3A0820 for <quic@ietfa.amsl.com>; Wed, 22 Jul 2020 22:43:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=eggert.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 G2EdqEN2n8Uy for <quic@ietfa.amsl.com>; Wed, 22 Jul 2020 22:43:53 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 827A33A081F for <quic@ietf.org>; Wed, 22 Jul 2020 22:43:53 -0700 (PDT)
Received: from [IPv6:2a00:ac00:0:35:c64:9a85:72f7:4fc2] (unknown [IPv6:2a00:ac00:0:35:c64:9a85:72f7:4fc2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 422C061F21E; Thu, 23 Jul 2020 08:43:46 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1595483026; bh=X1c8bnEQKLToVZ/hn8DVPXDO9fTlAAGrMORl3qag82s=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=qs9rIxMLSrvv4JKw8myU3mczNkQY+ZMVK6ApGXJHiC3LPcP/pUCAO/m+uVeNZARbn ykXnD973YnSA8HHN7sutz9By1xNh0sbv/IecQ4TUvKyUdjCMr4lWkq3W5xDWHC2NYA e/joCu/pv4NuMIVnXNYc30LwMfjKIR9WBMh8m2qY=
From: Lars Eggert <lars@eggert.org>
Message-Id: <02CB5B6C-3711-442C-8996-D7C65E587B9C@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_56F97A72-46CD-47F3-B134-4844340B8E36"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
Date: Thu, 23 Jul 2020 08:43:45 +0300
In-Reply-To: <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com>
Cc: Ted Hardie <ted.ietf@gmail.com>, Mark Nottingham <mnot@mnot.net>, QUIC WG <quic@ietf.org>, Lucas Pardue <lucaspardue.24.7@gmail.com>
To: Eric Rescorla <ekr@rtfm.com>
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com> <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org> <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com> <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com>
X-MailScanner-ID: 422C061F21E.A32C8
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Hjb8t5QxS_sIwAXyB5UI-4TpEJQ>
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, 23 Jul 2020 05:43:55 -0000

--Apple-Mail=_56F97A72-46CD-47F3-B134-4844340B8E36
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 2020-7-22, at 19:44, Eric Rescorla <ekr@rtfm.com> wrote:
> Ted's proposal would be acceptable to me.

I've done a small PR based on Ted's proposed text in =
https://github.com/quicwg/base-drafts/pull/3945

Lars

--Apple-Mail=_56F97A72-46CD-47F3-B134-4844340B8E36
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAl8ZI5EACgkQVLXDCb9w
wVd53A//ToB6E2KE9NxaEEsKbh/4H+Py4ezH/SKm9T8TRbbJB/rA8kuX2VXHRQAs
kg0grxISiFd59o3SlBY46AiVWClITqxlU0p/JClSwJe9yyQe5UB0aGKR0nVFls8J
Agcsszi08MGeK6JfpSFwpK8mtGWczBJJugUGLCYRSfKPmJxPxSrgKhHpdjc76La6
dtNMIsumHY6B26MMvLKrkP2lKByFHDEuRTYvezg2O5bF5H2suoovt7Oyt92z4Y/5
4n6tfr35Ef6Wm8Mwd4H4KQYiQbpyIDRbMPYHSFBxLmtXLaxlnRiKLdGjfuxoTFZn
MR5EsBS6ukZ9Zn9Pr7jesyF2FLaXbwXHUGEs4chKH/9gUje1d5gAFpMW2a3dMPmm
YAh2bq2Ymm/2GTZVHPYrOz4PrCcST9QNRG8aEOt/9RPwtuvFCd6ETEL8HBKudRiS
WrzV0xnBvi8TSu4iiWsHpXcTJgMkeIW3xa8tNAIlC5Rg/ClOamN7CuhskO7IR8hW
9qzU2uKVs3p+KqiU5yCLqejm7zQZUEGHwjCBfzjZhVNzqKn4Y/inFi1gOyb7siQB
VdsNZsD1sRF0cx/Pn4+ukb5jQ7uc6QChWeWZOfAXWW+Hijmh/x+JnKVm7a3tOrZu
TB9mrCBYCXIkYLEPdhA+X3DpjQkrQm7I9GsYZwAp17+qT/9EcFQ=
=PhEU
-----END PGP SIGNATURE-----

--Apple-Mail=_56F97A72-46CD-47F3-B134-4844340B8E36--


From nobody Thu Jul 23 00:09:35 2020
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 00C6B3A09AB for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 00:09:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, 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 w86q6d06edRs for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 00:09:32 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id 0D9A03A080A for <quic@ietf.org>; Thu, 23 Jul 2020 00:09:31 -0700 (PDT)
Received: from GF-MacBook-Pro.lan (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 166C11B0013F; Thu, 23 Jul 2020 08:09:28 +0100 (BST)
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
To: Martin Thomson <mt@lowentropy.net>, quic@ietf.org
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com> <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org> <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com> <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com> <7b5c104c-36b6-3fe1-4e5b-0e42cc9e2b36@huitema.net> <74ef5430-8e3f-4b6b-b81f-b25443e975b4@www.fastmail.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <32c098c3-24e4-1d7c-fdf5-33761adacfa8@erg.abdn.ac.uk>
Date: Thu, 23 Jul 2020 08:09:26 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <74ef5430-8e3f-4b6b-b81f-b25443e975b4@www.fastmail.com>
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/OoY_71fmBBArmGMPb6Tazb9HWw4>
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, 23 Jul 2020 07:09:34 -0000

I think this change is wrong from a congestion control perspective. To 
me this appears a significant congestion control change from  the 
current practice of IETF protocols, which make a conservative reaction.

See below:

On 23/07/2020 01:36, Martin Thomson wrote:
> Is the intent to avoid talking about what knowledge an endpoint might use to decide to transfer state?
>
> On Thu, Jul 23, 2020, at 05:43, Christian Huitema wrote:
>> Sounds good to me too.
>>
>> -- Christian Huitema
>>
>> On 7/22/2020 9:44 AM, Eric Rescorla wrote:
>>> Ted's proposal would be acceptable to me.
>>>
>>> -Ekr
>>>
>>>
>>> On Wed, Jul 22, 2020 at 7:48 AM Ted Hardie <ted.ietf@gmail.com> wrote:
>>>> If ekr's objections is that this is a hint, rather than more explicit, we can incorporate Lars' point by a minor adjustment of the text:
>>>>
>>>> OLD:
>>>>
>>>> On confirming a peer's ownership of its new address, an endpoint MUST
>>>> immediately reset the congestion controller and round-trip time estimator for
>>>> the new path to initial values (see Sections A.3 and B.3 in {{QUIC-RECOVERY}})
>>>> unless it has knowledge that a previous send rate or round-trip time estimate is
>>>> valid for the new path. For instance, an endpoint might infer that a change in
>>>> only the client's port number is indicative of a NAT rebinding, meaning that the
>>>> new path is likely to have similar bandwidth and round-trip time.
>>>>
>>>>
>>>> NEW:
>>>>
>>>> On confirming a peer's ownership of its new address, an endpoint SHOULD
>>>> reset the congestion controller and round-trip time estimator for the new path to
>>>> initial values (see Sections A.3 and B.3 in {{QUIC-RECOVERY}}) unless the
>>>> change is only to the client's port number.  Because port-only changes
>>>> are commonly the result of NAT rebinding or other middlebox activity,
>>>> the client MAY retain its estimation of the path bandwidth and round-trip time
>>>> in those cases..  A conservative implementation may also revert to initial values
>>>> in this case.
>>>>
>>>> That shifts it from hint territory to explicit resolution.
>>>>
>>>> regards,
>>>>
>>>> Ted
>>>>
>>>>
>>>> On Wed, Jul 22, 2020 at 12:36 AM Lars Eggert <lars@eggert.org> wrote:
>>>>> Hi,
>>>>>
>>>>> On 2020-7-22, at 6:11, Eric Rescorla <ekr@rtfm.com> wrote:
>>>>>> As I said, I don't have a strong opinion about the outcome, but we shouldn't just hint to people that they should ignore the port.
>>>>> existing protocols basically just broke when a port or IP address changed (e.g., a NAT rebinding happened). So how to respond to this is something that we don't have existing IETF practice for AFAIK.
>>>>>
>>>>> The conservative approach would be to mandate a CC reset on any change to the four-tuple, since it indicates a possible path change.
>>>>>
>>>>> For clients in consumer access networks behind CPE NATs, that conservative approach is probably too conservative, since the CC-relevant properties of the path are unlikely to have changed if just the source port changed.
>>>>>
>>>>> On the other hand, with client side CGNs and server-side BALBs (big-ass load balancers...) a port change now maybe is more indicative of a path change.. But it's not clear that this path change is more likely to affect the CC-relevant path characteristics.
>>>>>
>>>>> One final thing I'll point out is that all IETF transports have been happily ignoring at least one path change indication since forever - there is no mandated reaction to any change in the received IP TTL, and I'm also unaware of any implementation reacting to IP TTL changes (which would indicate a change in path length, something that probably would lead to CC-relevant changes in path characteristics.)
I agree with Lars that devices have traditionally ignored TTL/Hop Count 
changes, based on the assumption that small route changes don't have 
large impact - however, an important difference is that the proposed 
change modifies the input information that can be used to deterime the 
IP forwarding path in relation to traffic classification/queuing (e.g. 
SFQ) and set of devices on path.
>>>>> That, together with the observation that CC will react to a path change anyway after an RTT due to loss/marks, leads me to believe we're probably OK to not reset CC on a port change. It might mean that we're sending for about an RTT at a rate that is too high in some rare (?) cases, but in the vast majority of cases, we'd avoid needless performance degradations..
>>>>>
>>>>> YMMV.
>>>>>
>>>>> Lars

I thought the point that NAPT was common point had been discussed in 
QUIC before, and was noted that there are devices on path that change 
the forwrading path and hence congestion conditions based on the flow's 
port value. ECMP is a not that uncommon example, other load ballancing 
can also change the path. I understood that QUIC was seeking to avoid 
defining new congestion control approaches, and this proposal would seem 
to move in that direction.

Once a new path has been confirmed and the RTT discovered, I would 
expect there are actually opportunities to utilise the previous path 
information to quickly more to restore the ratye, but I think that 
simply ignoring such a path change can make a seriously wrong congetsion 
assumption - especially when accompanied by a significant RTT change.

Gorry


From nobody Thu Jul 23 00:22:44 2020
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 F18693A09C5 for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 00:22:41 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=eggert.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 dmQruQbDH1O9 for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 00:22:40 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 E5DFD3A09C4 for <quic@ietf.org>; Thu, 23 Jul 2020 00:22:39 -0700 (PDT)
Received: from [IPv6:2a00:ac00:0:35:c64:9a85:72f7:4fc2] (unknown [IPv6:2a00:ac00:0:35:c64:9a85:72f7:4fc2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 27DDD604660; Thu, 23 Jul 2020 10:22:32 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1595488952; bh=Z9ZhR8Khyy8QDWaPrQnCcud+BqVikh6kUKW+h4PHRdc=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=luKx5IZxeNLUj9vy8YqOAuKCKBj2nX6kClVlLU14BDbHuzaA4mCx2FRgWX+KFJZT0 jPODROD4mD90Ts7PEzKgB+q7xLuP+MCqAqcXTdwIt6b7Wb4Sgsp/OANplYgEBspe+c nmU5s9IXP4iDUDPMoHaI4vF0rNA6HtZvwKKP2MlM=
From: Lars Eggert <lars@eggert.org>
Message-Id: <FA3E4F14-570C-4A28-A2C8-EA2B3937E614@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_69E98048-1D7E-4183-B1C1-24F9B2B066FB"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
Date: Thu, 23 Jul 2020 10:22:31 +0300
In-Reply-To: <32c098c3-24e4-1d7c-fdf5-33761adacfa8@erg.abdn.ac.uk>
Cc: Martin Thomson <mt@lowentropy.net>, quic@ietf.org
To: Gorry Fairhust <gorry@erg.abdn.ac.uk>
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com> <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org> <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com> <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com> <7b5c104c-36b6-3fe1-4e5b-0e42cc9e2b36@huitema.net> <74ef5430-8e3f-4b6b-b81f-b25443e975b4@www.fastmail.com> <32c098c3-24e4-1d7c-fdf5-33761adacfa8@erg.abdn.ac.uk>
X-MailScanner-ID: 27DDD604660.A82EE
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/eHaJhYRjj03RJmLVGpZNvIc2fPw>
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, 23 Jul 2020 07:22:42 -0000

--Apple-Mail=_69E98048-1D7E-4183-B1C1-24F9B2B066FB
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 2020-7-23, at 10:09, Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:
> I thought the point that NAPT was common point had been discussed in =
QUIC before, and was noted that there are devices on path that change =
the forwrading path and hence congestion conditions based on the flow's =
port value. ECMP is a not that uncommon example, other load ballancing =
can also change the path.

but with ECMP, SFQ and similar schemes, the intent it spread the load =
equally over a set of candidate paths. So, assuming some level of =
utilization, all those candidate paths should have more-or-less similar =
path characteristics?

I agree that in general, a path change should cause a CC state reset, =
but in this specific case, I think we can make some assumptions (like =
the above) that may make it OK to not do that.

Lars

--Apple-Mail=_69E98048-1D7E-4183-B1C1-24F9B2B066FB
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAl8ZOrcACgkQVLXDCb9w
wVdwVw/+PxLm51yfPv+nmb3Yjt9FmUiYydoqqjqF22NWO2XWh2ysBpzZWJZhnz5v
NaqVfbzsaEzHaj/qO5Nx9nuu2l8986NM+U4ZxtEz8xMeQFweJFpEQS+nqoTwLktS
FrQi8mG+FXQAA8uvJiPrDd4UxRo1Z6q0OQiMrwju4H/fMRtMtDlY1k0875SRmcNE
25rc0a2pU8D2y5i+vwo7TGZWUL3qKdsOiOHRG5HA78k9O/YHPA7GDWCxyrE4+FJs
t7cx3k00npDoL9eWH6NFC/Ee7R2ecqgsPPJlskoSl+Wuw09zI24NIMyGBxn5PpaP
8UdqjL8rAY92yrtas8/PpDlnwQF4LUKgzqKMqC99fM/ZACNqg8SS5tdL3a7k+6vQ
WWANq1y3VAKFaJcGIleJ3Y3+OqmjwsfHE80PUeSk5gHo4kJfrCnkXMvN6Cqebtph
bGYObLjCrBF0ey8ZN/4jHqboaP1CGnxGw4YtHzEJYqkDd+r9BQiHoG4zkJLbWAs/
ANnBDEDkthsmDofSSzeGg+QuJNjvYFoJJcd8m0wVdVjilUXZGzFvVdS6guBBiB0S
VoLNPpLwMYOKOZQtMFbXawCSvNBij44ig4Ir000LsC6OTEgcnIt+bTfjeHx/XLFO
6l4mAQ2X0s1J7TQRWyKaFONcN4MBHQUyClZFdQL/wxZahpTTXwg=
=uAMc
-----END PGP SIGNATURE-----

--Apple-Mail=_69E98048-1D7E-4183-B1C1-24F9B2B066FB--


From nobody Thu Jul 23 00:34:48 2020
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 505C03A09CC for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 00:34:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, 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 fjhKOgGE-xSb for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 00:34:45 -0700 (PDT)
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 9860E3A09C6 for <quic@ietf.org>; Thu, 23 Jul 2020 00:34:45 -0700 (PDT)
Received: from GF-MacBook-Pro.lan (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id D15EE1B0023F; Thu, 23 Jul 2020 08:34:40 +0100 (BST)
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
To: Lars Eggert <lars@eggert.org>
Cc: quic@ietf.org, Martin Thomson <mt@lowentropy.net>
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com> <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org> <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com> <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com> <7b5c104c-36b6-3fe1-4e5b-0e42cc9e2b36@huitema.net> <74ef5430-8e3f-4b6b-b81f-b25443e975b4@www.fastmail.com> <32c098c3-24e4-1d7c-fdf5-33761adacfa8@erg.abdn.ac.uk> <FA3E4F14-570C-4A28-A2C8-EA2B3937E614@eggert.org>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <0ee0a444-3910-3e71-54aa-581431495648@erg.abdn.ac.uk>
Date: Thu, 23 Jul 2020 08:34:40 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <FA3E4F14-570C-4A28-A2C8-EA2B3937E614@eggert.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/sqejpz3ISOe6_bA_u-rkb5X-LgI>
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, 23 Jul 2020 07:34:47 -0000

See below,

On 23/07/2020 08:22, Lars Eggert wrote:
> Hi,
>
> On 2020-7-23, at 10:09, Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:
>> I thought the point that NAPT was common point had been discussed in QUIC before, and was noted that there are devices on path that change the forwrading path and hence congestion conditions based on the flow's port value. ECMP is a not that uncommon example, other load ballancing can also change the path.
> but with ECMP, SFQ and similar schemes, the intent it spread the load equally over a set of candidate paths.
>   So, assuming some level of utilization, all those candidate paths should have more-or-less similar path characteristics?

If you consider all paths equal, then sure, but how can you make that 
assumption?

If you assume this can only happen when the chosen paths have similar 
condictions, then I'd have to agree - but how can it be assumed that 
paths have equivalent unused capacity?

These methods often hash based on port, IP, and maybe other fields to 
select a queue - There are a finite set of queues, a rehash results in 
the traffic moving queue ... to chooses a different path or queue within 
the device. This mapping is statistical, this matters more if the 
multiplexing is low and a port change results in unbalance across 
quques/paths.

> I agree that in general, a path change should cause a CC state reset, but in this specific case, I think we can make some assumptions (like the above) that may make it OK to not do that.
>
> Lars

I still think this is a new CC decision, and the charter explicitly says 
that this version of QUIC will not make new congestion controllers.

Gorry


From nobody Thu Jul 23 00:42:40 2020
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 A5BEA3A0866 for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 00:42:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=eggert.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 uHXqdjPGUf8y for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 00:42:37 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 AA97B3A076C for <quic@ietf.org>; Thu, 23 Jul 2020 00:42:36 -0700 (PDT)
Received: from [IPv6:2a00:ac00:0:35:c64:9a85:72f7:4fc2] (unknown [IPv6:2a00:ac00:0:35:c64:9a85:72f7:4fc2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 4A1D86046B5; Thu, 23 Jul 2020 10:42:28 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1595490148; bh=gjz+q4hX7ItIXfLQUtcmAoPlRA7tXA/zhFg+n9D0CFM=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=W4bGNKSHqZCEJ7lBxXRdl/Wj8qfIrvuDeNT24KFXmCW7+EdDi2aun9pjTJriKUJrl O9jVbAyyNAp3KEDWtBcn12ooUa/96l70jK2k/MsOysjB4qK4WE2Lc8iK/kxOdn+aC0 fKbd8baUbmLIRmSmKZWYG6Nc/K1UKTpSwdi3lsQM=
From: Lars Eggert <lars@eggert.org>
Message-Id: <3644F334-F148-4FF5-AE86-015C073871AC@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_AB404ECA-69AD-4D0A-9F73-8A9D9CECBA71"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
Date: Thu, 23 Jul 2020 10:42:26 +0300
In-Reply-To: <0ee0a444-3910-3e71-54aa-581431495648@erg.abdn.ac.uk>
Cc: QUIC WG <quic@ietf.org>, Martin Thomson <mt@lowentropy.net>
To: Gorry Fairhust <gorry@erg.abdn.ac.uk>
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com> <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org> <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com> <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com> <7b5c104c-36b6-3fe1-4e5b-0e42cc9e2b36@huitema.net> <74ef5430-8e3f-4b6b-b81f-b25443e975b4@www.fastmail.com> <32c098c3-24e4-1d7c-fdf5-33761adacfa8@erg.abdn.ac.uk> <FA3E4F14-570C-4A28-A2C8-EA2B3937E614@eggert.org> <0ee0a444-3910-3e71-54aa-581431495648@erg.abdn.ac.uk>
X-MailScanner-ID: 4A1D86046B5.A36B4
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/sbDp808mOFPDP4ELUlLGLjL-b7E>
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, 23 Jul 2020 07:42:39 -0000

--Apple-Mail=_AB404ECA-69AD-4D0A-9F73-8A9D9CECBA71
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 2020-7-23, at 10:34, Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:
> These methods often hash based on port, IP, and maybe other fields to =
select a queue - There are a finite set of queues, a rehash results in =
the traffic moving queue ... to chooses a different path or queue within =
the device. This mapping is statistical, this matters more if the =
multiplexing is low and a port change results in unbalance across =
quques/paths.

I agree this is mostly a concern for low-mux'ing cases when a single =
rehash can create significant imbalance. How common are such =
deployments, and how much of a problem is such a temporary imbalance =
(the CC will adjust quickly). Esp. compared to forcing slow-start after =
every NAT rebind.

Lars

--Apple-Mail=_AB404ECA-69AD-4D0A-9F73-8A9D9CECBA71
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAl8ZP2IACgkQVLXDCb9w
wVe/2Q/+J8+33dps0J4UAL/QNQxSPAk3TGv4k6SDZ78ItQkUhV+2eCOc4JnkzAKx
avSDwpotDxCrOX7QjH6u8v/FFQTPI0glCeQ+Hpm0jqlBTCYybQcpliBrUltHtqHI
p0s3tT0aku/pMV5SKPxZ6DhBGIgkBdWxsRid7/GHtOnXcyYZh/J1Vd3NI3oaH7UN
CuCzTlSgm/N/lx7G54kkZ/XFu8OR48ReW7iUdSNuug4dw5kJqNyen4Pp4uX1cqsV
ZlUhAOBeZZuQeGsGeS3AZQ3fB9EdC9oY7XmJmsR1O2zO/AWsyE2q9BIM8XXD45RD
rySq5EjUfRZRDGCRk4/ywA/LbN2gq/1PZ7nO+STQB/+y2tiC5vMtuilrYNfEd2ds
rE9/gOZL0PEjwUWQ/izV4YgZEdzY+HP5+UVLDt9z0y3rgjNQFo62FQdJ6K0scy35
MqkwFwut8pryqhU3/jdOy37DnnVfwEDv8N5tGsSpQUsytB3M/7xCxrDrNvaaDDpU
qqB0Z2VK1WTVlnLhd/HY/lwFRZKj6f0md1O53Z+3iydVt+KIg8BF2WGdG5lCC/1/
mpt+nrZVgOQZl2fUWtZyyjYg9qUpatmhhdeq52hFhg1l21Djm0XZldU+b8b5PZTa
RqTJHJQ9xH5K/yAB4yRXMJ3a+4aemzSvi07ZPOF3UJ0otm5FK/A=
=Q2dP
-----END PGP SIGNATURE-----

--Apple-Mail=_AB404ECA-69AD-4D0A-9F73-8A9D9CECBA71--


From nobody Thu Jul 23 01:31:49 2020
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 466283A0A52 for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 01:31:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, 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 WEvqyKPBotRT for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 01:31:45 -0700 (PDT)
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 76CA03A0A50 for <quic@ietf.org>; Thu, 23 Jul 2020 01:31:45 -0700 (PDT)
Received: from GF-MacBook-Pro.lan (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 404791B0023F for <quic@ietf.org>; Thu, 23 Jul 2020 09:31:43 +0100 (BST)
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
To: quic@ietf.org
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com> <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org> <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com> <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com> <7b5c104c-36b6-3fe1-4e5b-0e42cc9e2b36@huitema.net> <74ef5430-8e3f-4b6b-b81f-b25443e975b4@www.fastmail.com> <32c098c3-24e4-1d7c-fdf5-33761adacfa8@erg.abdn.ac.uk> <FA3E4F14-570C-4A28-A2C8-EA2B3937E614@eggert.org> <0ee0a444-3910-3e71-54aa-581431495648@erg.abdn.ac.uk> <3644F334-F148-4FF5-AE86-015C073871AC@eggert.org>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <01cf1f47-d9e5-c0dc-ef1d-0c641b4cd025@erg.abdn.ac.uk>
Date: Thu, 23 Jul 2020 09:31:42 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <3644F334-F148-4FF5-AE86-015C073871AC@eggert.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 8bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/lAdy2apJPpmjTplDRRF9Or8znJ0>
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, 23 Jul 2020 08:31:47 -0000

On 23/07/2020 08:42, Lars Eggert wrote:
> Hi,
>
> On 2020-7-23, at 10:34, Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:
>> These methods often hash based on port, IP, and maybe other fields to select a queue - There are a finite set of queues, a rehash results in the traffic moving queue ... to chooses a different path or queue within the device. This mapping is statistical, this matters more if the multiplexing is low and a port change results in unbalance across quques/paths.
> I agree this is mostly a concern for low-mux'ing cases when a single rehash can create significant imbalance. How common are such deployments,
Sounds like interesting research for PANRG: How could we obtain that 
data for the general Internet? Specifically do you know of measurement 
campaigns that looked at this across different types of network path?
> and how much of a problem is such a temporary imbalance (the CC will adjust quickly).

Maybe, or is it true?  The reaction and impact depends on how QUIC's 
congestion controller deals with path changes (significant changes in 
capacity) esp when accompanined by RTT changes.

I could  suggest a test case where flows are divided in the network 
between two paths - one shorter RTT, one longer RTT and more 
constrained. A change in path results in traffic using wrong path 
assumptions. QUIC's Loss Recovery and Congestion reaction are timer 
based, and this timing information is wrong after a change, and the CC 
decision is also wrong. TCP wouldn't have done that.

> Esp. compared to forcing slow-start after every NAT rebind.
>
> Lars

If you say you wish to avoid slow-start after NAPT rebind, then I think 
this is a significant change to CC behviour relative to other IETF 
transport protocols, and is not similar to what Reno-TCP would do.

If you only reset QUIC's RTT estimator, that could be sufficent, 
especially if the port change didn't result in changes in capacity. It 
does however stand the risk that CC overshoots the capacity and the flow 
might suffer more. Reseting both until you confirm the new transport 
path seems safer in a PS, and is what the Recovery Draft currently says.

However, once the RTT is reset following this port change, a new path 
RTT is then established by the QUIC CC, I'd expect that the CC can then 
make informed decisions about what to do using the observed RTT. That 
could be slkow start. It would also seem reasonable that an endpoint 
that knows this RTT is the same as previous could then use this as a 
reasonable sign to become more aggressive than slow-start, perhaps 
restoring the CC state. To me, that sounds a lot like the case where a 
congestion-controller "thinks" it has evidence where there might be more 
capacity, but the endpoint isn't sure (as in Section 7.10, albeit in 
that case for other reasons... but there still needs some safety when 
there is significant path change). This sounds like a way the IETF could 
examine, and if we figure out the details, I expect this might work well 
for QUIC?

Gorry




From nobody Thu Jul 23 01:43:12 2020
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 8CD693A0A80 for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 01:43:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=eggert.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 8QAElLRiNE09 for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 01:43:10 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [IPv6:2a00:ac00:0:35:211:32ff:fe22:186f]) (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 12FD93A0A7E for <quic@ietf.org>; Thu, 23 Jul 2020 01:43:10 -0700 (PDT)
Received: from [IPv6:2a00:ac00:0:35:c64:9a85:72f7:4fc2] (unknown [IPv6:2a00:ac00:0:35:c64:9a85:72f7:4fc2]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 09D706047B7; Thu, 23 Jul 2020 11:43:03 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1595493784; bh=a4jLttwB4J6jpCc8BOn2hZYPU0bSRIYcdaMcj8aAUZU=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=0002bhOqEDu3E4sSD/QiVqZLsI7q1fbDgn7jBSU/IkQaUHatYjTqRVrHSA3AwIgNm uJHhbyjP3uUBX45V+KLyOKOoyuvtIKCBQQqjDFbmEcU6CbBTOt/is2r11AW+0HJx5N l3oVRT7h6rRlI+AipMPMHLqHnESBtbX31wxMwCZ4=
From: Lars Eggert <lars@eggert.org>
Message-Id: <A2387EEC-32EF-4A22-B34E-4F91E570AFC3@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_CEF8E21D-EA06-4E75-971D-E0CE29337D6D"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
Date: Thu, 23 Jul 2020 11:43:01 +0300
In-Reply-To: <01cf1f47-d9e5-c0dc-ef1d-0c641b4cd025@erg.abdn.ac.uk>
Cc: quic@ietf.org
To: Gorry Fairhust <gorry@erg.abdn.ac.uk>
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com> <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org> <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com> <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com> <7b5c104c-36b6-3fe1-4e5b-0e42cc9e2b36@huitema.net> <74ef5430-8e3f-4b6b-b81f-b25443e975b4@www.fastmail.com> <32c098c3-24e4-1d7c-fdf5-33761adacfa8@erg.abdn.ac.uk> <FA3E4F14-570C-4A28-A2C8-EA2B3937E614@eggert.org> <0ee0a444-3910-3e71-54aa-581431495648@erg.abdn.ac.uk> <3644F334-F148-4FF5-AE86-015C073871AC@eggert.org> <01cf1f47-d9e5-c0dc-ef1d-0c641b4cd025@erg.abdn.ac.uk>
X-MailScanner-ID: 09D706047B7.A4317
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/65fLDpMj9YPBmS2tl0fpNPalom4>
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, 23 Jul 2020 08:43:12 -0000

--Apple-Mail=_CEF8E21D-EA06-4E75-971D-E0CE29337D6D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

On 2020-7-23, at 11:31, Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:
> If you say you wish to avoid slow-start after NAPT rebind, then I =
think this is a significant change to CC behviour relative to other IETF =
transport protocols, and is not similar to what Reno-TCP would do.

how so? Current IETF transport protocols don't even survive a NAT =
rebind.

> If you only reset QUIC's RTT estimator, that could be sufficent, =
especially if the port change didn't result in changes in capacity. It =
does however stand the risk that CC overshoots the capacity and the flow =
might suffer more. Reseting both until you confirm the new transport =
path seems safer in a PS, and is what the Recovery Draft currently says.

Actually, you should have an RTT sample from a new path anyway, since =
you need to do a PATH_CHALLENGE/PATH_RESPONSE exchange.

In terms of CC overshoot, if that happens, it will lead to drops/marks =
being reported within one RTT, which will cause the right thing to =
happen.

> However, once the RTT is reset following this port change, a new path =
RTT is then established by the QUIC CC, I'd expect that the CC can then =
make informed decisions about what to do using the observed RTT. That =
could be slkow start. It would also seem reasonable that an endpoint =
that knows this RTT is the same as previous could then use this as a =
reasonable sign to become more aggressive than slow-start, perhaps =
restoring the CC state. To me, that sounds a lot like the case where a =
congestion-controller "thinks" it has evidence where there might be more =
capacity, but the endpoint isn't sure (as in Section 7.10, albeit in =
that case for other reasons... but there still needs some safety when =
there is significant path change). This sounds like a way the IETF could =
examine, and if we figure out the details, I expect this might work well =
for QUIC?

It's of course possible to invent more clever schemes to determine =
whether CC/RTT state should be reused after a port change. But my belief =
at the moment is that reuse would not be catastrophic. Sure, there will =
be cases where CC overshoots, but I am unconvinced this will be a =
serious/frequent issue.

Lars

PS: I'll pause myself for a bit, to let others respond.

--Apple-Mail=_CEF8E21D-EA06-4E75-971D-E0CE29337D6D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAl8ZTZUACgkQVLXDCb9w
wVf+LBAAvpcXf57f5yST+vt3nS98PwoeDSYZlca5Marb1FEY81R67q2oqNNIhP0t
hTQbrnyYQTK0t7073W89QN1vSBfUHngRA8gRPIN+AfjPjv1+r7lEzEiXmwpg92bi
dMMSyg5Cw4CPT/rqwLMBtXbBtAllpL23srpGT51SdaIUEA760UGSimBiL/sOmBcm
G4vXbS8r72vH62SRiazsAA8SfuWIk5VfaJExUMJyNb/9xqlXNMgipLbmhcPGwV2Y
Qh+bHk2pDTGvdgr0xHztfjg2XdgLs/1b/e8s3f3ukrrJ8f3sssLhNLkSyqO0j0Bp
NKuG4CPqpf2XlaCBQv1HJ3WnwJROKdoKZ5+ShvaLj+wKdSLb2SombkleJ2csnZfK
MyzJVh1Oebb//31tkf1kR0o+r1+GwNGoLhFB+v+ta56M5BuPnDWLUbWfiKTBHEO6
gjDg7cC+Bnru7MOg15VjuCwm6yeX4+1K6PEkcN7pTWN8q91MeBCZUWgAlt1ywNxA
wpuyjGdk9EIb3BaT4jiiDgVi4jkGz5C1fMsZhPltFaeo7kWqkd/oXlj+XOoNY61M
Kw3YoE8AOEDBixYzBwhtEwvNSqTjYVnqKUQNC9NJvmzvbGmUhizQKKgNzE1c9aTH
D2KFLoVXAyZ9cr/a8AxZ84dU+MnuHA/VvG4TYyuO8pmGeiAHS+U=
=mBA5
-----END PGP SIGNATURE-----

--Apple-Mail=_CEF8E21D-EA06-4E75-971D-E0CE29337D6D--


From nobody Thu Jul 23 02:07:32 2020
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 230833A0AAF for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 02:07:31 -0700 (PDT)
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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, 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 OCw-q9v0Z4Op for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 02:07:28 -0700 (PDT)
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 EFAD53A0AAD for <quic@ietf.org>; Thu, 23 Jul 2020 02:07:27 -0700 (PDT)
Received: from GF-MacBook-Pro.lan (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 56A461B001BF; Thu, 23 Jul 2020 10:07:20 +0100 (BST)
Subject: Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Ian Swett <ianswett@google.com>
Cc: Jana Iyengar <jri.ietf@gmail.com>, Praveen Balasubramanian <pravb@microsoft.com>, QUIC WG <quic@ietf.org>
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <9f57b20d-2eba-b2b9-d8c8-48e019c8952a@wizmail.org> <CACpbDccrpHeP5PYGCZky+AN2gC9YSs5gbAzYr4Yrw1LpvHZNiA@mail.gmail.com> <CH2PR00MB07269A73542DBC8E51E95519B67A0@CH2PR00MB0726.namprd00.prod.outlook.com> <CAKcm_gMhRX3NxiW6Primy+UrY44ZahaSO+9kF5CeeN4=XqL2JQ@mail.gmail.com> <CAKKJt-fY92k5ym767GofK+DOMQs=x6dpkwkKOA1cpkUf8Xs+3A@mail.gmail.com> <CAKcm_gPyg4QM+mZq_-E-av=u_X4nCWwdDXEH6e9Sjz1d8scEyg@mail.gmail.com> <CAKKJt-fmqjXJEUHzFT0yBXE0sLvOPcnM-oCBDZfgZQNgerRt8g@mail.gmail.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <114a0e70-fe91-9cf9-e4e8-5f7d074eac5c@erg.abdn.ac.uk>
Date: Thu, 23 Jul 2020 10:07:19 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <CAKKJt-fmqjXJEUHzFT0yBXE0sLvOPcnM-oCBDZfgZQNgerRt8g@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------F00F07E29402F3A2544FFB2E"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/-hVQbnp6SFGjv9m3JXlPB7FQJ30>
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, 23 Jul 2020 09:07:31 -0000

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

I'd like to argue a little more for something like the current text we 
arrived at:

"Implementations MUST either
    use pacing or another method to limit such bursts to the initial
    congestion window;"

I've been watching, and have comments see below:

On 20/07/2020 23:11, Spencer Dawkins at IETF wrote:
> Hi, Ian,
>
> On Mon, Jul 20, 2020, 16:33 Ian Swett <ianswett@google.com 
> <mailto:ianswett@google.com>> wrote:
>
>     Most of the items which I felt were somewhat deployment-specific
>     constants(ie: Initial Window and Initial RTT) are 'RECOMMENDED' in
>     the current recovery draft, so I thought it'd be preferable to
>     keep that convention.
>
>
> Thanks for helping me understand - this is a stylistic change.
>
> I've had a couple of conversations outside of QUIC recently with 
> people who were interpreting the two terms somewhat differently, so 
> thought it a good time to ask.
>
> Best,
>
> Spencer
>
>
>     On Mon, Jul 20, 2020 at 5:30 PM Spencer Dawkins at IETF
>     <spencerdawkins.ietf@gmail.com
>     <mailto:spencerdawkins.ietf@gmail.com>> wrote:
>
>         Hi, Ian,
>
>         On Mon, Jul 20, 2020 at 11:49 AM Ian Swett
>         <ianswett=40google.com@dmarc.ietf.org
>         <mailto:40google.com@dmarc.ietf.org>> wrote:
>
>             I think it's ok to include burst limits in the set of
>             things we expect may be different in DCs, but if we do
>             that, I'd prefer to use the RECOMMENDED rather than SHOULD,
>
>
>         Aren't RECOMMENDED and SHOULD equivalent in
>         https://tools.ietf.org/html/rfc2119?
>
>         Or am I misunderstanding your point?
>
>
>             3 <https://tools.ietf.org/html/rfc2119#section-3>. SHOULD
>
>         This word, or the adjective "RECOMMENDED", mean that there may
>         exist valid reasons in particular circumstances to ignore a
>         particular item, but the full implications must be understood
>         and carefully weighed before choosing a different course.
>
>         Best,
>
>         Spencer
>
>             since there are a number of SHOULDs which I believe apply
>             both to the public internet and to DCs.  Then we could add
>             a note at the top about how there are some values which
>             are RECOMMENDED, including X, Y and Z, and those
>             recommendations are expected to be good choices for most,
>             but not all environments.
>
>             In terms of text, I'd suggest taking Neal's suggestion and
>             dropping an explicit mention of the public internet:
>
>             Implementations MUST either use pacing or another method
>             to limit such bursts.
>
>             It is RECOMMENDED that implementations limit bursts to the
>             initial congestion window; seeSection 7.2  <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-quic-recovery-29%23section-7.2&data=02%7C01%7Cpravb%40microsoft.com%7C9df3e5f4f0ca4e586f0908d824e0a3ad%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637299894526657906&sdata=ze%2F7SpKUbrdgwI6m%2BS6uEGSBgc2NapVtPn9vkOYFjVs%3D&reserved=0>.
>
>
>             On Sun, Jul 19, 2020 at 4:08 PM Praveen Balasubramanian
>             <pravb=40microsoft.com@dmarc.ietf.org
>             <mailto:40microsoft.com@dmarc.ietf.org>> wrote:
>
>                 >> There's a way of satisfying both desires: have the
>                 NIC handle the pacing.
>
>                 Yes letting the NIC handle pacing will make improve
>                 CPU efficiency and improve accuracy due to fine
>                 grained hardware timers. But that’s in the future.
>                 Today’s NICs don’t pace large send offloads for TCP or
>                 UDP.
>
>                 >> Perhaps we can have a principle here:
>                 recommendations that are specific for Internet use are
>                 just that, and we use SHOULDs for those. IW10 makes
>                 sense based on this, and I would then also be fine
>                 with changing the MUST to a SHOULD. Perhaps we can
>                 state this principle upfront.
>
>                 I like the idea of stating that principle up front.
>                 SHOULD would be sufficient resolution for the burst
>                 size issue.
>
>                 *From:* QUIC <quic-bounces@ietf.org
>                 <mailto:quic-bounces@ietf.org>> *On Behalf Of * Jana
>                 Iyengar
>                 *Sent:* Friday, July 17, 2020 7:18 PM
>                 *To:* QUIC WG <quic@ietf.org <mailto:quic@ietf.org>>
>                 *Subject:* [EXTERNAL] Re: WGLC review of
>                 draft-ietf-quic-recovery-29
>
>                 There's a protocol question and there's a question of
>                 endpoint behavior. In terms of the protocol itself,
>                 yes, there's no real need to distinguish between
>                 Internet and DC environments; we've tried to ensure
>                 that the protocol can be used broadly. My point was
>                 that the constants in the spec were based on what we
>                 believe to be true for the public Internet, and not
>                 for DC environments.
>
>                 That said, perhaps I was a bit too hasty. IW10 and
>                 InitialRTT values are the others I was thinking about,
>                 but those are recommendations in the spec, not
>                 requirements. And as Ian notes, there's no minimum
>                 timeout anymore.
>
>                 Perhaps we can have a principle here: recommendations
>                 that are specific for Internet use are just that, and
>                 we use SHOULDs for those.
>
I don't agree, see below.
>
>                 IW10 makes sense based on this, and I would then also
>                 be fine with changing the MUST to a SHOULD. Perhaps we
>                 can state this principle upfront.
>
>                 Ian, I share your hesitation that we don't want to
>                 make a distinction between private and public
>                 networks, but we already allow for implementations to
>                 do that with a different IW and Initial RTT. Is it
>                 different when talking about burst limits?
>
>                 On Fri, Jul 17, 2020 at 3:07 PM Jeremy Harris
>                 <jgh@wizmail.org <mailto:jgh@wizmail.org>> wrote:
>
>                     On 08/07/2020 22:29, Praveen Balasubramanian wrote:
>                     > Section 7.9
>                     > "Implementations MUST either use pacing or
>                     another method to limit such bursts to the initial
>                     congestion window; see Section 7.2."
>                     > This seems to preclude use of segmentation
>                     offload of sizes greater than IW.. In datacenters
>                     we routinely send bursts that are higher without
>                     causing loss. The MUST here seems unnecessary. It
>                     also conflicts with the RECOMMENDED in an earlier
>                     sentence.
>
>                     There's a way of satisfying both desires: have the
>                     NIC handle the
>                     pacing.
>                     -- 
>                     Cheers,
>                       Jeremy
>

I am unsure that trying to differentiate DC from ISP-Edge from Enterprise Server
or anything else will help in the spec. Sure, guidance may differ - but I'd like
to think (???) the IETF Spec describes the "Internet case, which
is expected to be good choices for most, but not all environments... and if a system distributes
functions within your own network segment then that's your decision - and yes,
and doing this in NICs would be great ... although NICs also can generate bursts
when transports pace at a higher level...

The pacing/burst-limiting could happen in various ways by various actors, but
that's not the way transport Specs are written, I thought that's why we ended-up with
"other methods".

For me at least, it was a conscious decision to not to explicitly make this "10 packets",
because an endpoint sender that made an informed decision to use a larger IW
has at the same time decided to configure in a way that expects the network path can safely
support this burst size. I expect this matters most when the
connection sending rate is low (see below). But we missed something.

I think the suggested addition from Ian, could really help a lot:
"unless the pacing system can't provide enough sending opportunities to send at the rate specified by the congestion controller."

- This would make the language less clear, but I think in a very good way, because I agree that as the connection **sending** rate increases (and hence also the CC understanding of
the path characteristics), the effect of bursts might be expected to be less significant. At higher rates queues in devices clear more quickly, and buffering 1mS (or whatever) of data, buffers more.

Can we discuss that proposal more?

Gorry


--------------F00F07E29402F3A2544FFB2E
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>I'd like to argue a little more for something like the current
      text we arrived at:</p>
    <pre class="newpage">"Implementations MUST either
   use pacing or another method to limit such bursts to the initial
   congestion window;"

I've been watching, and have comments see below:

</pre>
    <div class="moz-cite-prefix">On 20/07/2020 23:11, Spencer Dawkins at
      IETF wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAKKJt-fmqjXJEUHzFT0yBXE0sLvOPcnM-oCBDZfgZQNgerRt8g@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="auto">
        <div>Hi, Ian,<br>
          <br>
          <div class="gmail_quote">
            <div dir="ltr" class="gmail_attr">On Mon, Jul 20, 2020,
              16:33 Ian Swett &lt;<a href="mailto:ianswett@google.com"
                moz-do-not-send="true">ianswett@google.com</a>&gt;
              wrote:<br>
            </div>
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div dir="ltr">Most of the items which I felt were
                somewhat deployment-specific constants(ie: Initial
                Window and Initial RTT) are 'RECOMMENDED' in the current
                recovery draft, so I thought it'd be preferable to keep
                that convention.</div>
            </blockquote>
          </div>
        </div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Thanks for helping me understand - this is a
          stylistic change.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">I've had a couple of conversations outside of
          QUIC recently with people who were interpreting the two terms
          somewhat differently, so thought it a good time to ask.</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Best,</div>
        <div dir="auto"><br>
        </div>
        <div dir="auto">Spencer</div>
        <div dir="auto">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
              <div class="gmail_quote">
                <div dir="ltr" class="gmail_attr">On Mon, Jul 20, 2020
                  at 5:30 PM Spencer Dawkins at IETF &lt;<a
                    href="mailto:spencerdawkins.ietf@gmail.com"
                    target="_blank" rel="noreferrer"
                    moz-do-not-send="true">spencerdawkins.ietf@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 dir="ltr">
                    <div dir="ltr">Hi, Ian, </div>
                    <br>
                    <div class="gmail_quote">
                      <div dir="ltr" class="gmail_attr">On Mon, Jul 20,
                        2020 at 11:49 AM Ian Swett &lt;ianswett=<a
                          href="mailto:40google.com@dmarc.ietf.org"
                          target="_blank" rel="noreferrer"
                          moz-do-not-send="true">40google.com@dmarc.ietf.org</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 dir="ltr">I think it's ok to include burst
                          limits in the set of things we expect may be
                          different in DCs, but if we do that, I'd
                          prefer to use the RECOMMENDED rather than
                          SHOULD,</div>
                      </blockquote>
                      <div><br>
                      </div>
                      <div>Aren't RECOMMENDED and SHOULD equivalent in 
                        <a href="https://tools.ietf.org/html/rfc2119"
                          target="_blank" rel="noreferrer"
                          moz-do-not-send="true">https://tools.ietf.org/html/rfc2119</a>? </div>
                      <div><br>
                      </div>
                      <div>Or am I misunderstanding your point?</div>
                      <div><br>
                      </div>
                      <div>
                        <pre style="margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><font size="4"><span style="display:inline;font-weight:bold"><h2 style="display:inline"><a name="m_-7104407681243286268_m_-561907519085294557_section-3" href="https://tools.ietf.org/html/rfc2119#section-3" style="color:black;text-decoration-line:none" target="_blank" rel="noreferrer" moz-do-not-send="true">3</a>. SHOULD  </h2></span> This word, or the adjective "RECOMMENDED", mean that there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.</font></pre>
                      </div>
                      <div> </div>
                      <div>Best,</div>
                      <div><br>
                      </div>
                      <div>Spencer</div>
                      <div><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 dir="ltr"> since there are a number of
                          SHOULDs which I believe apply both to the
                          public internet and to DCs.  Then we could add
                          a note at the top about how there are some
                          values which are RECOMMENDED, including X, Y
                          and Z, and those recommendations are expected
                          to be good choices for most, but not all
                          environments.
                          <div><br>
                          </div>
                          <div>In terms of text, I'd suggest taking
                            Neal's suggestion and dropping an explicit
                            mention of the public internet:</div>
                          <div><br>
                          </div>
                          <div>
                            <pre style="white-space:pre-wrap;margin:0in;font-size:10pt;font-family:&quot;Courier New&quot;;break-before:page"><span style="color:black">Implementations MUST either use pacing or another method to limit such bursts.</span></pre>
                            <pre style="white-space:pre-wrap;margin:0in;font-size:10pt;font-family:&quot;Courier New&quot;;break-before:page"><span style="color:black">It is RECOMMENDED that implementations limit bursts to the initial </span>congestion window; see <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-quic-recovery-29%23section-7.2&amp;data=02%7C01%7Cpravb%40microsoft.com%7C9df3e5f4f0ca4e586f0908d824e0a3ad%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637299894526657906&amp;sdata=ze%2F7SpKUbrdgwI6m%2BS6uEGSBgc2NapVtPn9vkOYFjVs%3D&amp;reserved=0" style="font-size:10pt" target="_blank" rel="noreferrer" moz-do-not-send="true">Section 7.2</a><span style="font-size:10pt;color:black">.</span></pre>
                          </div>
                        </div>
                        <br>
                        <div class="gmail_quote">
                          <div dir="ltr" class="gmail_attr">On Sun, Jul
                            19, 2020 at 4:08 PM Praveen Balasubramanian
                            &lt;pravb=<a
                              href="mailto:40microsoft.com@dmarc.ietf.org"
                              target="_blank" rel="noreferrer"
                              moz-do-not-send="true">40microsoft.com@dmarc.ietf.org</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 lang="EN-US">
                              <div>
                                <p class="MsoNormal">&gt;&gt; There's a
                                  way of satisfying both desires: have
                                  the NIC handle the pacing.</p>
                                <p class="MsoNormal">Yes letting the NIC
                                  handle pacing will make improve CPU
                                  efficiency and improve accuracy due to
                                  fine grained hardware timers. But
                                  that’s in the future. Today’s NICs
                                  don’t pace large send offloads for TCP
                                  or UDP.</p>
                                <p class="MsoNormal"> </p>
                                <p class="MsoNormal">&gt;&gt; Perhaps we
                                  can have a principle here:
                                  recommendations that are specific for
                                  Internet use are just that, and we use
                                  SHOULDs for those. IW10 makes sense
                                  based on this, and I would then also
                                  be fine with changing the MUST to a
                                  SHOULD. Perhaps we can state this
                                  principle upfront.</p>
                                <p class="MsoNormal">I like the idea of
                                  stating that principle up front.
                                  SHOULD would be sufficient resolution
                                  for the burst size issue.
                                </p>
                                <p class="MsoNormal"> </p>
                                <div
style="border-right:none;border-bottom:none;border-left:none;border-top:1pt
                                  solid rgb(225,225,225);padding:3pt 0in
                                  0in">
                                  <p class="MsoNormal"><b>From:</b> QUIC
                                    &lt;<a
                                      href="mailto:quic-bounces@ietf.org"
                                      target="_blank" rel="noreferrer"
                                      moz-do-not-send="true">quic-bounces@ietf.org</a>&gt;
                                    <b>On Behalf Of </b>
                                    Jana Iyengar<br>
                                    <b>Sent:</b> Friday, July 17, 2020
                                    7:18 PM<br>
                                    <b>To:</b> QUIC WG &lt;<a
                                      href="mailto:quic@ietf.org"
                                      target="_blank" rel="noreferrer"
                                      moz-do-not-send="true">quic@ietf.org</a>&gt;<br>
                                    <b>Subject:</b> [EXTERNAL] Re: WGLC
                                    review of
                                    draft-ietf-quic-recovery-29</p>
                                </div>
                                <p class="MsoNormal"> </p>
                                <div>
                                  <p class="MsoNormal">There's a
                                    protocol question and there's a
                                    question of endpoint behavior. In
                                    terms of the protocol itself, yes,
                                    there's no real need to distinguish
                                    between Internet and DC
                                    environments; we've tried to ensure
                                    that the protocol can be used
                                    broadly. My point was that the
                                    constants in the spec were based on
                                    what we believe to be true for the
                                    public Internet, and not for DC
                                    environments.</p>
                                  <div>
                                    <p class="MsoNormal"> </p>
                                  </div>
                                  <div>
                                    <p class="MsoNormal">That said,
                                      perhaps I was a bit too hasty.
                                      IW10 and InitialRTT values are the
                                      others I was thinking about, but
                                      those are recommendations in the
                                      spec, not requirements. And as Ian
                                      notes, there's no minimum timeout
                                      anymore.</p>
                                  </div>
                                  <div>
                                    <p class="MsoNormal"> </p>
                                  </div>
                                  <div>
                                    <p class="MsoNormal">Perhaps we can
                                      have a principle here:
                                      recommendations that are specific
                                      for Internet use are just that,
                                      and we use SHOULDs for those. </p>
                                  </div>
                                </div>
                              </div>
                            </div>
                          </blockquote>
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </blockquote>
              </div>
            </blockquote>
          </div>
        </div>
      </div>
    </blockquote>
    I don't agree, see below.<br>
    <blockquote type="cite"
cite="mid:CAKKJt-fmqjXJEUHzFT0yBXE0sLvOPcnM-oCBDZfgZQNgerRt8g@mail.gmail.com">
      <div dir="auto">
        <div dir="auto">
          <div class="gmail_quote">
            <blockquote class="gmail_quote" style="margin:0 0 0
              .8ex;border-left:1px #ccc solid;padding-left:1ex">
              <div class="gmail_quote">
                <blockquote class="gmail_quote" style="margin:0px 0px
                  0px 0.8ex;border-left:1px solid
                  rgb(204,204,204);padding-left:1ex">
                  <div dir="ltr">
                    <div class="gmail_quote">
                      <blockquote class="gmail_quote" style="margin:0px
                        0px 0px 0.8ex;border-left:1px solid
                        rgb(204,204,204);padding-left:1ex">
                        <div class="gmail_quote">
                          <blockquote class="gmail_quote"
                            style="margin:0px 0px 0px
                            0.8ex;border-left:1px solid
                            rgb(204,204,204);padding-left:1ex">
                            <div lang="EN-US">
                              <div>
                                <div>
                                  <div>
                                    <p class="MsoNormal">IW10 makes
                                      sense based on this, and I would
                                      then also be fine with changing
                                      the MUST to a SHOULD. Perhaps we
                                      can state this principle upfront.</p>
                                  </div>
                                  <div>
                                    <p class="MsoNormal"> </p>
                                  </div>
                                  <div>
                                    <p class="MsoNormal">Ian, I share
                                      your hesitation that we don't want
                                      to make a distinction between
                                      private and public networks, but
                                      we already allow for
                                      implementations to do that with a
                                      different IW and Initial RTT. Is
                                      it different when talking about
                                      burst limits?</p>
                                  </div>
                                  <div>
                                    <p class="MsoNormal"> </p>
                                  </div>
                                </div>
                                <p class="MsoNormal"> </p>
                                <div>
                                  <div>
                                    <p class="MsoNormal">On Fri, Jul 17,
                                      2020 at 3:07 PM Jeremy Harris &lt;<a
                                        href="mailto:jgh@wizmail.org"
                                        target="_blank" rel="noreferrer"
                                        moz-do-not-send="true">jgh@wizmail.org</a>&gt;
                                      wrote:</p>
                                  </div>
                                  <blockquote>
                                    <p class="MsoNormal"
                                      style="margin-bottom:12pt">On
                                      08/07/2020 22:29, Praveen
                                      Balasubramanian wrote:<br>
                                      &gt; Section 7.9<br>
                                      &gt; "Implementations MUST either
                                      use pacing or another method to
                                      limit such bursts to the initial
                                      congestion window; see Section
                                      7.2."<br>
                                      &gt; This seems to preclude use of
                                      segmentation offload of sizes
                                      greater than IW.. In datacenters
                                      we routinely send bursts that are
                                      higher without causing loss. The
                                      MUST here seems unnecessary. It
                                      also conflicts with the
                                      RECOMMENDED in an earlier
                                      sentence.<br>
                                      <br>
                                      There's a way of satisfying both
                                      desires: have the NIC handle the<br>
                                      pacing.<br>
                                      -- <br>
                                      Cheers,<br>
                                        Jeremy</p>
                                  </blockquote>
                                </div>
                              </div>
                            </div>
                          </blockquote>
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </blockquote>
              </div>
            </blockquote>
          </div>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <pre class="newpage">I am unsure that trying to differentiate DC from ISP-Edge from Enterprise Server
or anything else will help in the spec. Sure, guidance may differ - but I'd like
to think (???) the IETF Spec describes the "Internet case, which
is expected to be good choices for most, but not all environments... and if a system distributes
functions within your own network segment then that's your decision - and yes,
and doing this in NICs would be great ... although NICs also can generate bursts 
when transports pace at a higher level... 

The pacing/burst-limiting could happen in various ways by various actors, but
that's not the way transport Specs are written, I thought that's why we ended-up with 
"other methods".

For me at least, it was a conscious decision to not to explicitly make this "10 packets", 
because an endpoint sender that made an informed decision to use a larger IW 
has at the same time decided to configure in a way that expects the network path can safely 
support this burst size. I expect this matters most when the
connection sending rate is low (see below). But we missed something.

I think the suggested addition from Ian, could really help a lot:
"unless the pacing system can't provide enough sending opportunities to send at the rate specified by the congestion controller."

- This would make the language less clear, but I think in a very good way, because I agree that as the connection **sending** rate increases (and hence also the CC understanding of
the path characteristics), the effect of bursts might be expected to be less significant. At higher rates queues in devices clear more quickly, and buffering 1mS (or whatever) of data, buffers more. 

Can we discuss that proposal more?

Gorry
</pre>
  </body>
</html>

--------------F00F07E29402F3A2544FFB2E--


From nobody Thu Jul 23 02:11:06 2020
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 4DF303A0ABB for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 02:11:04 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, 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 4jzX1vYbTaIc for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 02:11:03 -0700 (PDT)
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 DE88C3A0AB4 for <quic@ietf.org>; Thu, 23 Jul 2020 02:11:02 -0700 (PDT)
Received: from GF-MacBook-Pro.lan (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id E4C691B001BF; Thu, 23 Jul 2020 10:10:59 +0100 (BST)
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
To: Lars Eggert <lars@eggert.org>
Cc: quic@ietf.org
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com> <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org> <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com> <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com> <7b5c104c-36b6-3fe1-4e5b-0e42cc9e2b36@huitema.net> <74ef5430-8e3f-4b6b-b81f-b25443e975b4@www.fastmail.com> <32c098c3-24e4-1d7c-fdf5-33761adacfa8@erg.abdn.ac.uk> <FA3E4F14-570C-4A28-A2C8-EA2B3937E614@eggert.org> <0ee0a444-3910-3e71-54aa-581431495648@erg.abdn.ac.uk> <3644F334-F148-4FF5-AE86-015C073871AC@eggert.org> <01cf1f47-d9e5-c0dc-ef1d-0c641b4cd025@erg.abdn.ac.uk> <A2387EEC-32EF-4A22-B34E-4F91E570AFC3@eggert.org>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <d6a93b29-cb10-e34f-352b-db354d956280@erg.abdn.ac.uk>
Date: Thu, 23 Jul 2020 10:10:58 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <A2387EEC-32EF-4A22-B34E-4F91E570AFC3@eggert.org>
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7w0Ul1VYGwzyqs1VAY3q2yixJX8>
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, 23 Jul 2020 09:11:04 -0000

Hi,

On 23/07/2020 09:43, Lars Eggert wrote:
> Hi,
>
> On 2020-7-23, at 11:31, Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:
>> If you say you wish to avoid slow-start after NAPT rebind, then I think this is a significant change to CC behviour relative to other IETF transport protocols, and is not similar to what Reno-TCP would do.
> how so? Current IETF transport protocols don't even survive a NAT rebind.
They all slow-start.
>
>> If you only reset QUIC's RTT estimator, that could be sufficent, especially if the port change didn't result in changes in capacity. It does however stand the risk that CC overshoots the capacity and the flow might suffer more. Reseting both until you confirm the new transport path seems safer in a PS, and is what the Recovery Draft currently says.
> Actually, you should have an RTT sample from a new path anyway, since you need to do a PATH_CHALLENGE/PATH_RESPONSE exchange.
Right.
>
> In terms of CC overshoot, if that happens, it will lead to drops/marks being reported within one RTT, which will cause the right thing to happen.
Not that fast in all cases?
>> However, once the RTT is reset following this port change, a new path RTT is then established by the QUIC CC, I'd expect that the CC can then make informed decisions about what to do using the observed RTT. That could be slkow start. It would also seem reasonable that an endpoint that knows this RTT is the same as previous could then use this as a reasonable sign to become more aggressive than slow-start, perhaps restoring the CC state. To me, that sounds a lot like the case where a congestion-controller "thinks" it has evidence where there might be more capacity, but the endpoint isn't sure (as in Section 7.10, albeit in that case for other reasons... but there still needs some safety when there is significant path change). This sounds like a way the IETF could examine, and if we figure out the details, I expect this might work well for QUIC?
> It's of course possible to invent more clever schemes to determine whether CC/RTT state should be reused after a port change. But my belief at the moment is that reuse would not be catastrophic. Sure, there will be cases where CC overshoots, but I am unconvinced this will be a serious/frequent issue.
>
> Lars
>
> PS: I'll pause myself for a bit, to let others respond.

I'd like that discussion also... this is new & interesting...

Gorry


From nobody Thu Jul 23 11:47:14 2020
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 34D863A0C9F for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 11:47:13 -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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, 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 SUfjL0Gk0jmX for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 11:47:12 -0700 (PDT)
Received: from mx43-out1.antispamcloud.com (mx43-out1.antispamcloud.com [138.201.61.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AFEEF3A0C4A for <quic@ietf.org>; Thu, 23 Jul 2020 11:47:09 -0700 (PDT)
Received: from xse100.mail2web.com ([66.113.196.100] helo=xse.mail2web.com) by mx165.antispamcloud.com with esmtp (Exim 4.92) (envelope-from <huitema@huitema.net>) id 1jygF9-000tqj-QO for quic@ietf.org; Thu, 23 Jul 2020 20:47:05 +0200
Received: from xsmtp22.mail2web.com (unknown [10.100.68.61]) by xse.mail2web.com (Postfix) with ESMTPS id 4BCLsZ2J3Hz2rrX for <quic@ietf.org>; Thu, 23 Jul 2020 11:46:58 -0700 (PDT)
Received: from [10.5.2.15] (helo=xmail05.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 1jygF8-0007en-6Q for quic@ietf.org; Thu, 23 Jul 2020 11:46:58 -0700
Received: (qmail 3115 invoked from network); 23 Jul 2020 18:46:57 -0000
Received: from unknown (HELO [192.168.1.107]) (Authenticated-user:_huitema@huitema.net@[172.58.43.134]) (envelope-sender <huitema@huitema.net>) by xmail05.myhosting.com (qmail-ldap-1.03) with ESMTPA for <mt@lowentropy.net>; 23 Jul 2020 18:46:57 -0000
To: Lars Eggert <lars@eggert.org>, Gorry Fairhust <gorry@erg.abdn.ac.uk>
Cc: QUIC WG <quic@ietf.org>, Martin Thomson <mt@lowentropy.net>
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com> <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org> <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com> <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com> <7b5c104c-36b6-3fe1-4e5b-0e42cc9e2b36@huitema.net> <74ef5430-8e3f-4b6b-b81f-b25443e975b4@www.fastmail.com> <32c098c3-24e4-1d7c-fdf5-33761adacfa8@erg.abdn.ac.uk> <FA3E4F14-570C-4A28-A2C8-EA2B3937E614@eggert.org> <0ee0a444-3910-3e71-54aa-581431495648@erg.abdn.ac.uk> <3644F334-F148-4FF5-AE86-015C073871AC@eggert.org>
From: Christian Huitema <huitema@huitema.net>
Autocrypt: addr=huitema@huitema.net; prefer-encrypt=mutual; keydata= mDMEXtavGxYJKwYBBAHaRw8BAQdA1ou9A5MHTP9N3jfsWzlDZ+jPnQkusmc7sfLmWVz1Rmu0 J0NocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0PoiWBBMWCAA+FiEEw3G4 Nwi4QEpAAXUUELAmqKBYtJQFAl7WrxsCGwMFCQlmAYAFCwkIBwIGFQoJCAsCBBYCAwECHgEC F4AACgkQELAmqKBYtJQbMwD/ebj/qnSbthC/5kD5DxZ/Ip0CGJw5QBz/+fJp3R8iAlsBAMjK r2tmyWyJz0CUkVG24WaR5EAJDvgwDv8h22U6QVkAuDgEXtavGxIKKwYBBAGXVQEFAQEHQJoM 6MUAIqpoqdCIiACiEynZf7nlJg2Eu0pXIhbUGONdAwEIB4h+BBgWCAAmFiEEw3G4Nwi4QEpA AXUUELAmqKBYtJQFAl7WrxsCGwwFCQlmAYAACgkQELAmqKBYtJRm2wD7BzeK5gEXSmBcBf0j BYdSaJcXNzx4yPLbP4GnUMAyl2cBAJzcsR4RkwO4dCRqM9CHpVJCwHtbUDJaa55//E0kp+gH
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
Message-ID: <c28e05f6-637d-9183-11db-f8daa8b9e7c4@huitema.net>
Date: Thu, 23 Jul 2020 11:46:57 -0700
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <3644F334-F148-4FF5-AE86-015C073871AC@eggert.org>
Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="iKGI0yqBdPgpfECRN7bhlUaAIPNKBZ317"
X-Originating-IP: 66.113.196.100
X-Spampanel-Domain: xsmtpout.mail2web.com
X-Spampanel-Username: 66.113.196.100/32
Authentication-Results: antispamcloud.com; auth=pass smtp.auth=66.113.196.100/32@xsmtpout.mail2web.com
X-Spampanel-Outgoing-Class: ham
X-Spampanel-Outgoing-Evidence: Combined (0.06)
X-Recommended-Action: accept
X-Filter-ID: Mvzo4OR0dZXEDF/gcnlw0bN4ZX/cCaR95pQ7tQtUF1ypSDasLI4SayDByyq9LIhVwvqCnoCzIMxx cK3dmWAY/UTNWdUk1Ol2OGx3IfrIJKywOmJyM1qr8uRnWBrbSAGDcnqpk5VeF3xR4kF6iVwRtbgN zB/4Jkrw1eDLcif59fsI50dXFKDqEMh2AAzAdoU5U7Tmz6iKnkQL9gqsxD347235Nhqq+/HvroPq 8GSPg+60/QPNqXybIny9WGhadIo/WSlmRJUKMrJ+ahcq82ahPryme9ldZJ7uNXfg/GfS8fXOC4kn OJkMS8NGDKsP9r3Khy7LI0kfFnXdPP6btp4oBeJDeKRq5oPj2hFJhLx+qI3HlR3ootg7OlA3N5WN re/oppAGOX5cHTu1yz4pRT/9FGrxEaaKeSxe0Wrx6M4G5/WoLsdfEoJI0BNUQ4KpaNyNCwGqOUcw rXf55E8Tb8bmXq4yH8StrboPphDtmrtUkwkDMc9xayd+oZJo2heFY+g6kVWClPVvbW5lVyQanRxw 5rdY2rW50fd1ekaDpmIWc1Vmt3mnxMTQMQWbvBqEXskTQn6USYs98Imn+lZXe3dwYfgVB1xo6dCf BaU/iegBU8aUJfluQqfeAjECBQJTOQmpO7d6CDlWuQmnn8BRF01Cm0lp7yPqtzbP+0yi5RYbydIn dLDoft3gQzSYknam2p7RRtZL+RcVylNt/Xabq9oLs6zNjLvclnGzlTC8ZgkR3laIWqvAxiBHuIuS y5fCAlEkJ4c2pukl0P19e8QH3YrtPlACVO3tx78u0bG7If2TCVToC9jhOddqBfwcZ+DpisSDVzOz K7x3y6AqURyjPjZ6KznzSXChKWk/itcbicJsIPfz7d1Fe52vb2pe5EJ6a2Umfqb5R4VemuUI6bcE ARsm0De6PaZO6/JToEyx4tmc5OljkPSpPXAVjl2oMr8a1xm0wfXUFMjTH2DyD8i5kO5bZlYFvf25 LVONYbYifH5OzZCwIgD/xDehea09OpnwSuobZrrGExMR7eTbBjMGDKI3ijhhJn7Muv/NHXl0o++8 3wM=
X-Report-Abuse-To: spam@quarantine11.antispamcloud.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/j7XyfDstN63ZwBIsSkeHI_MPGR0>
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, 23 Jul 2020 18:47:13 -0000

This is an OpenPGP/MIME signed message (RFC 4880 and 3156)
--iKGI0yqBdPgpfECRN7bhlUaAIPNKBZ317
Content-Type: multipart/mixed; boundary="RUG6Hq6F71gftMyzRUjISmtJ7KfJtgrzU";
 protected-headers="v1"
From: Christian Huitema <huitema@huitema.net>
To: Lars Eggert <lars@eggert.org>, Gorry Fairhust <gorry@erg.abdn.ac.uk>
Cc: QUIC WG <quic@ietf.org>, Martin Thomson <mt@lowentropy.net>
Message-ID: <c28e05f6-637d-9183-11db-f8daa8b9e7c4@huitema.net>
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com>
 <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com>
 <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org>
 <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com>
 <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com>
 <7b5c104c-36b6-3fe1-4e5b-0e42cc9e2b36@huitema.net>
 <74ef5430-8e3f-4b6b-b81f-b25443e975b4@www.fastmail.com>
 <32c098c3-24e4-1d7c-fdf5-33761adacfa8@erg.abdn.ac.uk>
 <FA3E4F14-570C-4A28-A2C8-EA2B3937E614@eggert.org>
 <0ee0a444-3910-3e71-54aa-581431495648@erg.abdn.ac.uk>
 <3644F334-F148-4FF5-AE86-015C073871AC@eggert.org>
In-Reply-To: <3644F334-F148-4FF5-AE86-015C073871AC@eggert.org>

--RUG6Hq6F71gftMyzRUjISmtJ7KfJtgrzU
Content-Type: multipart/alternative;
 boundary="------------A5F1E4FF7688CD9931BBA6FC"
Content-Language: en-US

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

On 7/23/2020 12:42 AM, Lars Eggert wrote:

> Hi,
>
> On 2020-7-23, at 10:34, Gorry Fairhurst <gorry@erg.abdn.ac.uk> wrote:
>> These methods often hash based on port, IP, and maybe other fields to =
select a queue - There are a finite set of queues, a rehash results in th=
e traffic moving queue ... to chooses a different path or queue within th=
e device. This mapping is statistical, this matters more if the multiplex=
ing is low and a port change results in unbalance across quques/paths.
> I agree this is mostly a concern for low-mux'ing cases when a single re=
hash can create significant imbalance. How common are such deployments, a=
nd how much of a problem is such a temporary imbalance (the CC will adjus=
t quickly). Esp. compared to forcing slow-start after every NAT rebind.


Gorry, Lars, where can we find data on the NAT behavior and the relation
between NAT rebinding and routing paths? In home routers, NAT rebinding
typically only change if the session is quiet for some time. Do we
observe a different behavior with CGNAT?

-- Christian Huitema


--------------A5F1E4FF7688CD9931BBA6FC
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable

<html>
  <head>
    <meta http-equiv=3D"Content-Type" content=3D"text/html;
      charset=3Dwindows-1252">
  </head>
  <body>
    <p>On 7/23/2020 12:42 AM, Lars Eggert wrote:<br>
    </p>
    <blockquote type=3D"cite"
      cite=3D"mid:3644F334-F148-4FF5-AE86-015C073871AC@eggert.org">
      <pre class=3D"moz-quote-pre" wrap=3D"">Hi,

On 2020-7-23, at 10:34, Gorry Fairhurst <a class=3D"moz-txt-link-rfc2396E=
" href=3D"mailto:gorry@erg.abdn.ac.uk" moz-do-not-send=3D"true">&lt;gorry=
@erg.abdn.ac.uk&gt;</a> wrote:
</pre>
      <blockquote type=3D"cite" style=3D"color: #000000;">
        <pre class=3D"moz-quote-pre" wrap=3D"">These methods often hash b=
ased on port, IP, and maybe other fields to select a queue - There are a =
finite set of queues, a rehash results in the traffic moving queue ... to=
 chooses a different path or queue within the device. This mapping is sta=
tistical, this matters more if the multiplexing is low and a port change =
results in unbalance across quques/paths.
</pre>
      </blockquote>
      <pre class=3D"moz-quote-pre" wrap=3D"">I agree this is mostly a con=
cern for low-mux'ing cases when a single rehash can create significant im=
balance. How common are such deployments, and how much of a problem is su=
ch a temporary imbalance (the CC will adjust quickly). Esp. compared to f=
orcing slow-start after every NAT rebind.</pre>
    </blockquote>
    <p><br>
    </p>
    <p>Gorry, Lars, where can we find data on the NAT behavior and the
      relation between NAT rebinding and routing paths? In home routers,
      NAT rebinding typically only change if the session is quiet for
      some time. Do we observe a different behavior with CGNAT? <br>
    </p>
    <p>-- Christian Huitema<br>
    </p>
  </body>
</html>

--------------A5F1E4FF7688CD9931BBA6FC--

--RUG6Hq6F71gftMyzRUjISmtJ7KfJtgrzU--

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

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

iHUEARYIAB0WIQTDcbg3CLhASkABdRQQsCaooFi0lAUCXxnbIQAKCRAQsCaooFi0
lDNIAQCDwWyzItbakhY6Ku9l660lAahBakL/DqwXL3d3/pVefwD/bXXtzCk+qsRz
XWRprFFAOW0bydvP1RR+QWfBsBXGeA4=
=kTBW
-----END PGP SIGNATURE-----

--iKGI0yqBdPgpfECRN7bhlUaAIPNKBZ317--


From nobody Thu Jul 23 14:02:29 2020
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 933C43A0DC4 for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 14:02:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 bN-e8zhMnPuc for <quic@ietfa.amsl.com>; Thu, 23 Jul 2020 14:02:19 -0700 (PDT)
Received: from mail-lf1-x12f.google.com (mail-lf1-x12f.google.com [IPv6:2a00:1450:4864:20::12f]) (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 46B513A0DB0 for <quic@ietf.org>; Thu, 23 Jul 2020 14:02:19 -0700 (PDT)
Received: by mail-lf1-x12f.google.com with SMTP id m15so3384578lfp.7 for <quic@ietf.org>; Thu, 23 Jul 2020 14:02:19 -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=3e03V5IP4JBxm7zifWSMYr/f1wyPqAPzXgB49CGeTCM=; b=ml7H7MCHwwzGoyN3gW2VtpyEuHL11rGmGAC+asSSuBuzyEz/wb7BxE4iTBSeSS8dgg raQQPpb62QxIpab/b3ZFKr2Ks71pz62qBxod7nCIRCkjWzXe8ibx/tKuwhUx+KFTZe8e UrJrwm0VB2elMGKBuZZuK6Pt/tGSI0rfrTMR+8bl4eqgkJRyFbm1HUmRHI2UoWtgNC59 RC+gCoJzfzRWQmfc5lzbw8bLOViYZSj8zM9ee0gh47Mu4zZi2ml8m7GZ1sBcbBBxQAoE SoRJ4sqUvqcZEfEChrfjm6MjRX3OUoebtvZilK/EP3t+o159GQXXqQ4PwzckZIxsYk+r V9Rg==
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=3e03V5IP4JBxm7zifWSMYr/f1wyPqAPzXgB49CGeTCM=; b=shoOjrrepGqBiUawyfosnaoi5JHmrrztIfx8bzgtqlpWlaVPRYVp+4TJeo6b8hBmYj eerkW3OF4N7fSa2e89smdeJtBKvIpr+XknNgrp5Q3zfAzC7dMwU43orbTfFfEg9mqU6j HjBeufPebADk8DE+yoSyuVqbDnpNS+B0CYb5XxJ+G7MW16VH0AVRJXw6qiM+JPO96EuW RO8Vxc3wsAZ+5k7nmTPypadgDVMdyv9YwfYBO8DVlHfMYQLmwryKR9tJRZQUdKKGae3Z 0hid9x1XUKtctpoV7C5V3p/s9sBHMZnaAvo3sFrt30NoUJAis+Pm2ShC5I0qqSwohF3Z zKpw==
X-Gm-Message-State: AOAM530xnEwrD9RdnCbFTdpWFqSs4+15L/Sg0KxJP/iTHOBC/PzYCMNV tw88woYfgaQkIdIiClW+0zh8yPUIs3iE1Jaa6e0=
X-Google-Smtp-Source: ABdhPJyLtvN8R6q7i24zY/ri78EEIp03lf1KyDZhmeiN8YqpoWwrWz4czlULF0Sfcp4GmQv/yf1QTQkIwSH7wM3xCpM=
X-Received: by 2002:a19:8015:: with SMTP id b21mr3104613lfd.206.1595538137453;  Thu, 23 Jul 2020 14:02:17 -0700 (PDT)
MIME-Version: 1.0
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com> <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org> <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com> <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com> <7b5c104c-36b6-3fe1-4e5b-0e42cc9e2b36@huitema.net> <74ef5430-8e3f-4b6b-b81f-b25443e975b4@www.fastmail.com> <32c098c3-24e4-1d7c-fdf5-33761adacfa8@erg.abdn.ac.uk> <FA3E4F14-570C-4A28-A2C8-EA2B3937E614@eggert.org> <0ee0a444-3910-3e71-54aa-581431495648@erg.abdn.ac.uk> <3644F334-F148-4FF5-AE86-015C073871AC@eggert.org> <c28e05f6-637d-9183-11db-f8daa8b9e7c4@huitema.net>
In-Reply-To: <c28e05f6-637d-9183-11db-f8daa8b9e7c4@huitema.net>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Thu, 23 Jul 2020 14:02:06 -0700
Message-ID: <CACpbDcc86pgVpcN7DHb2s8aRGjzCC4RNjYPnGyDHhUCWg-G9zA@mail.gmail.com>
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
To: Christian Huitema <huitema@huitema.net>
Cc: Lars Eggert <lars@eggert.org>, Gorry Fairhust <gorry@erg.abdn.ac.uk>, QUIC WG <quic@ietf.org>, Martin Thomson <mt@lowentropy.net>
Content-Type: multipart/alternative; boundary="000000000000e8980105ab222bf1"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/nbMYFzvdvPP-jy1pHZMpAs8dab8>
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, 23 Jul 2020 21:02:27 -0000

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

I'm happy with the resolution that Ted proposed and Lars wrote up in PR 394=
5
<https://github.com/quicwg/base-drafts/pull/3945>.

We should not forget that endpoints will do what they choose to do on this
particular issue. It's perfectly reasonable to assume that port changes are
infrequent and do not reflect a path change commonly. In the rare case that
it happens and in the rarer case that it is in fact a path change, both
congestion controllers and RTT estimators are adaptive. The text in the PR
captures this possibility. That reflects reality and is an adequately
cautious recommendation, IMO.

On Thu, Jul 23, 2020 at 11:47 AM Christian Huitema <huitema@huitema.net>
wrote:

> On 7/23/2020 12:42 AM, Lars Eggert wrote:
>
> Hi,
>
> On 2020-7-23, at 10:34, Gorry Fairhurst <gorry@erg.abdn.ac.uk> <gorry@erg=
.abdn.ac.uk> wrote:
>
> These methods often hash based on port, IP, and maybe other fields to sel=
ect a queue - There are a finite set of queues, a rehash results in the tra=
ffic moving queue ... to chooses a different path or queue within the devic=
e. This mapping is statistical, this matters more if the multiplexing is lo=
w and a port change results in unbalance across quques/paths.
>
> I agree this is mostly a concern for low-mux'ing cases when a single reha=
sh can create significant imbalance. How common are such deployments, and h=
ow much of a problem is such a temporary imbalance (the CC will adjust quic=
kly). Esp. compared to forcing slow-start after every NAT rebind.
>
>
> Gorry, Lars, where can we find data on the NAT behavior and the relation
> between NAT rebinding and routing paths? In home routers, NAT rebinding
> typically only change if the session is quiet for some time. Do we observ=
e
> a different behavior with CGNAT?
>
> -- Christian Huitema
>

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

<div dir=3D"ltr">I&#39;m happy with the resolution that Ted proposed and La=
rs wrote up in <a href=3D"https://github.com/quicwg/base-drafts/pull/3945">=
PR 3945</a>.<div><br></div><div>We should not forget that endpoints will do=
 what they choose to do on this particular issue. It&#39;s perfectly reason=
able to assume that port changes are infrequent and do not reflect a path c=
hange commonly. In the rare case that it happens and in the rarer case that=
 it is in fact a path change, both congestion controllers and RTT estimator=
s are adaptive. The text in the PR captures this possibility. That reflects=
 reality and is an adequately cautious recommendation, IMO.</div></div><br>=
<div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Ju=
l 23, 2020 at 11:47 AM Christian Huitema &lt;<a href=3D"mailto:huitema@huit=
ema.net">huitema@huitema.net</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">
 =20
   =20
 =20
  <div>
    <p>On 7/23/2020 12:42 AM, Lars Eggert wrote:<br>
    </p>
    <blockquote type=3D"cite">
      <pre>Hi,

On 2020-7-23, at 10:34, Gorry Fairhurst <a href=3D"mailto:gorry@erg.abdn.ac=
.uk" target=3D"_blank">&lt;gorry@erg.abdn.ac.uk&gt;</a> wrote:
</pre>
      <blockquote type=3D"cite" style=3D"color:rgb(0,0,0)">
        <pre>These methods often hash based on port, IP, and maybe other fi=
elds to select a queue - There are a finite set of queues, a rehash results=
 in the traffic moving queue ... to chooses a different path or queue withi=
n the device. This mapping is statistical, this matters more if the multipl=
exing is low and a port change results in unbalance across quques/paths.
</pre>
      </blockquote>
      <pre>I agree this is mostly a concern for low-mux&#39;ing cases when =
a single rehash can create significant imbalance. How common are such deplo=
yments, and how much of a problem is such a temporary imbalance (the CC wil=
l adjust quickly). Esp. compared to forcing slow-start after every NAT rebi=
nd.</pre>
    </blockquote>
    <p><br>
    </p>
    <p>Gorry, Lars, where can we find data on the NAT behavior and the
      relation between NAT rebinding and routing paths? In home routers,
      NAT rebinding typically only change if the session is quiet for
      some time. Do we observe a different behavior with CGNAT? <br>
    </p>
    <p>-- Christian Huitema<br>
    </p>
  </div>

</blockquote></div>

--000000000000e8980105ab222bf1--


From nobody Fri Jul 24 00:30:49 2020
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 383B23A0ACB for <quic@ietfa.amsl.com>; Fri, 24 Jul 2020 00:30:48 -0700 (PDT)
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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, 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 1snO2aDrwbr3 for <quic@ietfa.amsl.com>; Fri, 24 Jul 2020 00:30:46 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id F36103A0AC8 for <quic@ietf.org>; Fri, 24 Jul 2020 00:30:40 -0700 (PDT)
Received: from GF-MacBook-Pro.lan (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id 25B9F1B00062; Fri, 24 Jul 2020 08:30:33 +0100 (BST)
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
To: Jana Iyengar <jri.ietf@gmail.com>, Christian Huitema <huitema@huitema.net>
Cc: Lars Eggert <lars@eggert.org>, QUIC WG <quic@ietf.org>, Martin Thomson <mt@lowentropy.net>
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com> <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org> <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com> <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com> <7b5c104c-36b6-3fe1-4e5b-0e42cc9e2b36@huitema.net> <74ef5430-8e3f-4b6b-b81f-b25443e975b4@www.fastmail.com> <32c098c3-24e4-1d7c-fdf5-33761adacfa8@erg.abdn.ac.uk> <FA3E4F14-570C-4A28-A2C8-EA2B3937E614@eggert.org> <0ee0a444-3910-3e71-54aa-581431495648@erg.abdn.ac.uk> <3644F334-F148-4FF5-AE86-015C073871AC@eggert.org> <c28e05f6-637d-9183-11db-f8daa8b9e7c4@huitema.net> <CACpbDcc86pgVpcN7DHb2s8aRGjzCC4RNjYPnGyDHhUCWg-G9zA@mail.gmail.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <5114fe5a-30b1-bcdf-7d1e-70b34697a9c0@erg.abdn.ac.uk>
Date: Fri, 24 Jul 2020 08:30:31 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <CACpbDcc86pgVpcN7DHb2s8aRGjzCC4RNjYPnGyDHhUCWg-G9zA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------B5B7F0146141C847E498E95D"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/tLLocFkGO-OsuEhW7V7crpciYl0>
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, 24 Jul 2020 07:30:48 -0000

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


On 23/07/2020 22:02, Jana Iyengar wrote:
> I'm happy with the resolution that Ted proposed and Lars wrote up in 
> PR 3945 <https://github.com/quicwg/base-drafts/pull/3945>.
>
> We should not forget that endpoints will do what they choose to do on 
> this particular issue. It's perfectly reasonable to assume that port 
> changes are infrequent and do not reflect a path change commonly. In 
> the rare case that it happens and in the rarer case that it is in fact 
> a path change, both congestion controllers and RTT estimators are 
> adaptive. The text in the PR captures this possibility. That reflects 
> reality and is an adequately cautious recommendation, IMO.
>
As you expect I don't agree this is cautious: optimising for an 
infrequent/rare case is not cautious, it introduces more chance of 
undesriable side effects on paths that actually are different.

There seems to me to be little impact in re-initialising the RTT 
estimator, there's an initial handshake for the new path from which this 
can be initialised.

Christian: I also would love to see data about the frequency and 
pathology, but don't know of any.

Gorry

> On Thu, Jul 23, 2020 at 11:47 AM Christian Huitema 
> <huitema@huitema.net <mailto:huitema@huitema.net>> wrote:
>
>     On 7/23/2020 12:42 AM, Lars Eggert wrote:
>
>>     Hi,
>>
>>     On 2020-7-23, at 10:34, Gorry Fairhurst<gorry@erg.abdn.ac.uk>  <mailto:gorry@erg.abdn.ac..uk>  wrote:
>>>     These methods often hash based on port, IP, and maybe other fields to select a queue - There are a finite set of queues, a rehash results in the traffic moving queue ... to chooses a different path or queue within the device. This mapping is statistical, this matters more if the multiplexing is low and a port change results in unbalance across quques/paths.
>>     I agree this is mostly a concern for low-mux'ing cases when a single rehash can create significant imbalance. How common are such deployments, and how much of a problem is such a temporary imbalance (the CC will adjust quickly). Esp. compared to forcing slow-start after every NAT rebind.
>
>
>     Gorry, Lars, where can we find data on the NAT behavior and the
>     relation between NAT rebinding and routing paths? In home routers,
>     NAT rebinding typically only change if the session is quiet for
>     some time. Do we observe a different behavior with CGNAT?
>
>     -- Christian Huitema
>

--------------B5B7F0146141C847E498E95D
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 23/07/2020 22:02, Jana Iyengar
      wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CACpbDcc86pgVpcN7DHb2s8aRGjzCC4RNjYPnGyDHhUCWg-G9zA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">I'm happy with the resolution that Ted proposed and
        Lars wrote up in <a
          href="https://github.com/quicwg/base-drafts/pull/3945"
          moz-do-not-send="true">PR 3945</a>.
        <div><br>
        </div>
        <div>We should not forget that endpoints will do what they
          choose to do on this particular issue. It's perfectly
          reasonable to assume that port changes are infrequent and do
          not reflect a path change commonly. In the rare case that it
          happens and in the rarer case that it is in fact a path
          change, both congestion controllers and RTT estimators are
          adaptive. The text in the PR captures this possibility. That
          reflects reality and is an adequately cautious recommendation,
          IMO.</div>
      </div>
      <br>
    </blockquote>
    <p>As you expect I don't agree this is cautious: optimising for an
      infrequent/rare case is not cautious, it introduces more chance of
      undesriable side effects on paths that actually are different. <br>
    </p>
    <p>There seems to me to be little impact in re-initialising the RTT
      estimator, there's an initial handshake for the new path from
      which this can be initialised.</p>
    <p>Christian: I also would love to see data about the frequency and
      pathology, but don't know of any.<br>
    </p>
    <p>Gorry<br>
    </p>
    <blockquote type="cite"
cite="mid:CACpbDcc86pgVpcN7DHb2s8aRGjzCC4RNjYPnGyDHhUCWg-G9zA@mail.gmail.com">
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Thu, Jul 23, 2020 at 11:47
          AM Christian Huitema &lt;<a href="mailto:huitema@huitema.net"
            moz-do-not-send="true">huitema@huitema.net</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>
            <p>On 7/23/2020 12:42 AM, Lars Eggert wrote:<br>
            </p>
            <blockquote type="cite">
              <pre>Hi,

On 2020-7-23, at 10:34, Gorry Fairhurst <a href="mailto:gorry@erg.abdn.ac..uk" target="_blank" moz-do-not-send="true">&lt;gorry@erg.abdn.ac.uk&gt;</a> wrote:
</pre>
              <blockquote type="cite" style="color:rgb(0,0,0)">
                <pre>These methods often hash based on port, IP, and maybe other fields to select a queue - There are a finite set of queues, a rehash results in the traffic moving queue ... to chooses a different path or queue within the device. This mapping is statistical, this matters more if the multiplexing is low and a port change results in unbalance across quques/paths.
</pre>
              </blockquote>
              <pre>I agree this is mostly a concern for low-mux'ing cases when a single rehash can create significant imbalance. How common are such deployments, and how much of a problem is such a temporary imbalance (the CC will adjust quickly). Esp. compared to forcing slow-start after every NAT rebind.</pre>
            </blockquote>
            <p><br>
            </p>
            <p>Gorry, Lars, where can we find data on the NAT behavior
              and the relation between NAT rebinding and routing paths?
              In home routers, NAT rebinding typically only change if
              the session is quiet for some time. Do we observe a
              different behavior with CGNAT? <br>
            </p>
            <p>-- Christian Huitema<br>
            </p>
          </div>
        </blockquote>
      </div>
    </blockquote>
  </body>
</html>

--------------B5B7F0146141C847E498E95D--


From nobody Fri Jul 24 00:47:11 2020
Return-Path: <magnus.westerlund@ericsson.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id C43033A0B33 for <quic@ietfa.amsl.com>; Fri, 24 Jul 2020 00:47:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.102
X-Spam-Level: 
X-Spam-Status: No, score=-2.102 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, DKIM_VALID_EF=-0.1, RCVD_IN_MSPIKE_H2=-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=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 eQHo2fSBQ3wG for <quic@ietfa.amsl.com>; Fri, 24 Jul 2020 00:47:06 -0700 (PDT)
Received: from EUR04-HE1-obe.outbound.protection.outlook.com (mail-eopbgr70085.outbound.protection.outlook.com [40.107.7.85]) (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 2DB983A0B32 for <quic@ietf.org>; Fri, 24 Jul 2020 00:47:06 -0700 (PDT)
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=JZgw9VfdpRq0XgzLndhCrWbJFXfNlxiqwmRMLzWyAKU68gNPtxEFaI13ilQ4Dwxe+6sHUoo+ssfLKoWzbYsGcH1lhs2dMFdBGSJYVUZnY+nkk0ayCbeUGPwPuO6jwSbFq2NDZqP4hMglWKy8eExYA7jJm72j5KWMecGPBcKHoOkmQy+yl4KHVWo7LQRCx2CQFjbJK9m5Gl+fJCyDUX4VdZHit622L545rtJ0TW+ucJAMa85g6N24q0aM1/vBH7tN6Igq5UzM4Cusa2Ag8KZz/d8bNodD2kJbTc4efyOqJ/nJvk91Wa0jbSm1jgFt5mdekIONMgGGja5puVi3Eq6CGA==
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=rAcpBj+oP8qp81q+hH4GJCphkC2PMpQ/agjfCS6l5zY=; b=Qlo5Qen28u7EdLmU8el4lVwWZNK4VzSMGZcfJ80e4kBdu6NyUEc5i3CK6afDgrQYwTAZT1WVp3nCuPbiC/06+ldPMoDd9qacPBTe9LVy2tOKcB0KZHs4LWhg+EkVE/Vl4WMip4oL8Y7CIqOStOLVxvqO1+waIn9+x4US8D50ySSd8FvMk3gjxpTx3K1smb5iEEOMUJgLQju/cggWiD8ejcyQnuyr8rk4/VgzQ+5ZRl8BL0Ac8LdM1VOwE25JmmlLUyh1w9xHNv+tPEw5Q8UArFEEXywaQF+Xx+DyFZi0LXyrcRJAu7g9neMNoYlGAH/FfHM4rX/TPa79vv9oIAjkzQ==
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=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=rAcpBj+oP8qp81q+hH4GJCphkC2PMpQ/agjfCS6l5zY=; b=juOLFT+rX9YJBv8CBJZG0hzPzVrO+dgPK3d2uBF3hir1n6rsHoZKZ31oofDHfQi4AiXUTKxA2xuz3TF6jHaAi0NQP2fbxOvf2bURYk0ltefDY8bII7cQB6QS5k1szpsFr3l8iyq10SXxK5RIffzhX+VrVxBIv6gFfA47F5x0dIA=
Received: from HE1PR0702MB3772.eurprd07.prod.outlook.com (2603:10a6:7:8e::14) by HE1PR0701MB2458.eurprd07.prod.outlook.com (2603:10a6:3:71::12) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3239.9; Fri, 24 Jul 2020 07:47:03 +0000
Received: from HE1PR0702MB3772.eurprd07.prod.outlook.com ([fe80::546c:3b3:9193:3351]) by HE1PR0702MB3772.eurprd07.prod.outlook.com ([fe80::546c:3b3:9193:3351%6]) with mapi id 15.20.3216.016; Fri, 24 Jul 2020 07:47:03 +0000
From: Magnus Westerlund <magnus.westerlund@ericsson.com>
To: "huitema@huitema.net" <huitema@huitema.net>, "jri.ietf@gmail.com" <jri.ietf@gmail.com>
CC: "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "mt@lowentropy.net" <mt@lowentropy.net>, "lars@eggert.org" <lars@eggert.org>, "quic@ietf.org" <quic@ietf.org>
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
Thread-Topic: Consensus call for Late-Stage documents, pre-IETF 108 edition
Thread-Index: AQHWX8vkK2gaMVOHYk+y4egls1510akS7BkAgABJ4ICAAHiNgIAAIMAAgAAx14CAAFHggIAAbdEAgAADqICAAANlAIAAAisAgAC5qoCAACXDAIAAtDEA
Date: Fri, 24 Jul 2020 07:47:03 +0000
Message-ID: <337cd3d0841e9d94a034aa2402ac2a030af550f8.camel@ericsson.com>
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com> <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org> <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com> <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com> <7b5c104c-36b6-3fe1-4e5b-0e42cc9e2b36@huitema.net> <74ef5430-8e3f-4b6b-b81f-b25443e975b4@www.fastmail.com> <32c098c3-24e4-1d7c-fdf5-33761adacfa8@erg.abdn.ac.uk> <FA3E4F14-570C-4A28-A2C8-EA2B3937E614@eggert.org> <0ee0a444-3910-3e71-54aa-581431495648@erg.abdn.ac.uk> <3644F334-F148-4FF5-AE86-015C073871AC@eggert.org> <c28e05f6-637d-9183-11db-f8daa8b9e7c4@huitema.net> <CACpbDcc86pgVpcN7DHb2s8aRGjzCC4RNjYPnGyDHhUCWg-G9zA@mail.gmail.com>
In-Reply-To: <CACpbDcc86pgVpcN7DHb2s8aRGjzCC4RNjYPnGyDHhUCWg-G9zA@mail.gmail.com>
Accept-Language: sv-SE, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Evolution 3.28.5-0ubuntu0.18.04.2 
authentication-results: huitema.net; dkim=none (message not signed) header.d=none;huitema.net; dmarc=none action=none header.from=ericsson.com;
x-originating-ip: [158.174.130.202]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: b344c818-2bf8-49f4-6bb9-08d82fa5c181
x-ms-traffictypediagnostic: HE1PR0701MB2458:
x-microsoft-antispam-prvs: <HE1PR0701MB245808BB97869ECE514FDD7495770@HE1PR0701MB2458.eurprd07.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: CPr9Ev1fP3fPd9xcm4BVXFCDFmZ36eRYu4iHrlGOTMod+KlS5fNKRBFjl4gOrprX6JpQzo0Q1DTwqUp4QZ/ajEJz9OmFfxHgf1Fss99DM7mPO9y3x0E5bd3GFlXogdwI5Z1yN2yZnLRD8lWb090UrJC7fXDodyD4yzs5PLk/4fG6FzE7puMiXa4kw5CUfJmE69Kgoa2cAjMIka1V5F3fsQ8jOuSXXuswJ6v0PXMXhHwaGgMOL9DFXZGJE57FSuBJSrknuovTxUM89PvHNi07FfNcfMDb2tCmK5a4p+iyDDVxWhE4aur59wA1aU4htofGRBwECgu+kM4JX6rJdSQ7Phd0QjL7NVlug3qwC9Kvp5LDliNay9uQMe4CPlFF6Lm+
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:HE1PR0702MB3772.eurprd07.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(366004)(346002)(376002)(136003)(39860400002)(396003)(186003)(2906002)(44832011)(6512007)(8936002)(5660300002)(2616005)(26005)(54906003)(86362001)(8676002)(76116006)(64756008)(36756003)(110136005)(66446008)(66946007)(4326008)(316002)(83380400001)(66556008)(6506007)(478600001)(4001150100001)(71200400001)(66476007)(53546011)(6486002)(99106002); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: AwwUEilhYWjntVd228ACDvmdflArPV8q5hdLhuEPcxxDa25nW9NRB3KESTiQQ+awOn4mhjAZfXLmAJg9UHMLETNdWXevu6J+wvcyPTSoSIuv8KKBLR8j0KRjNv31PH9bQMBD1Ti2hKByHDyaqPW2puGbCrpt91/EWdVOB9l2MTG0zYrXTvyQqF9BJJmueXSeTo5NhgC0Kw4N/9R+mQlzcB0VaHkjDOa77DHCfQFHXOnIIg/xXrzT+6MfD/+nStYYXCfBJdZHETZYUPR65SSg/JGEQewncDg9S0XL1MxpQZTtqfgB7hozUcVVvHysOxzHLdnhA2U45suf2dN/+TPuviuXpLLfgCBo8gIu0dHzAaYkOYQd7RMVJTvhbj3M7o5kcriMJqol75bsYKDAQrqa8StPpLRn8B4IfurmF+LHtOaHry4USuJieWqrJXvk+4ooe5PJLHqMbmVnLrOzvTCcjeUwgIXoxzSBN+ahmSd4yaEM8DJ8bc0H0x8axXnS8hkg4eprLwO9mkwxP0zyc+p7mxQ6Oa8mqGMIegF5Cz8d39xRkQaIHZWqXy0KVURWW1xinU8GcAMyPROaDdZYrtIcskzXMXQAEjRBA0PrW+uzkulDjtvKySmZRC1w/QNWeu/1DtChJcmFRXWAG2Q31dj8zw==
x-ms-exchange-transport-forked: True
Content-Type: text/plain; charset="utf-8"
Content-ID: <726BFF9440C0D548A356BC775DB8B4B6@eurprd07.prod.outlook.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
X-OriginatorOrg: ericsson.com
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: HE1PR0702MB3772.eurprd07.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: b344c818-2bf8-49f4-6bb9-08d82fa5c181
X-MS-Exchange-CrossTenant-originalarrivaltime: 24 Jul 2020 07:47:03.3869 (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: RrgnZm2X5zpvvFkOGt4TnqHox+Xmfh5iXQ61wTLHFf/Xpf7/E/U0xolQCcMf/Rdu9DMR1I6Sjq+P3CkadN35xT5vSokdNRcveLp8L0oKOnc=
X-MS-Exchange-Transport-CrossTenantHeadersStamped: HE1PR0701MB2458
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/TVdVqBNbzthfNyi_e0QngSwRtDc>
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, 24 Jul 2020 07:47:11 -0000

SGksDQoNClNvIGlmIEkgdW5kZXJzdGFuZCB0aGlzIGNvcnJlY3RseSB3ZSBoYXZlIGEgY291cGxl
IG9mIGRpZmZlcmVudCByZWFzb25zIGZvcg0KcmVhc29ucyBmb3IgdGhlIHBvcnQgY2hhbmdlIHRv
IG9jY3VyLg0KDQpOQVQgYmluZGluZyB0aW1lcyBvdXQ6IEluIHRoaXMgY2FzZSB0aGUgQ0Mgc3Rh
dGUgc2hvdWxkIGFsc28gaGF2ZSBiZWVuIGFnZWQgYXMNCnRoZSBRVUlDIGNvbm5lY3Rpb24gaGFz
IG5vdCBzZW50IGFueXRoaW5nIGZvciBtYW55IHNlY29uZHMuIEkgd291bGQgdGhpbmsgYQ0KbWlu
aW1hbCBvZiA1IHNlY29uZHMsIGxpa2VseSBhdCBsZWFzdCAzMCBzZWNvbmRzIG9mIGluYWN0aXZp
dHkgZm9yIGFuDQplc3RhYmxpc2hlZCBRVUlDIGNvbm5lY3Rpb24gYXMgaXQgd2lsbCBoYXZlIGdv
dHRlbiB0aGUgTkFUIGludG8gYSBiaS1kaXJlY3Rpb25hbCANClVEUCBmbG93IHN0YXRlLCByYXRo
ZXIgdGhhbiBhIG9uZSBvZiByZXF1ZXN0IHJlc3BvbnNlIHN0YXRlLCBsaWtlIGZvciBOQVRzIHdp
dGgNCkROUyBiaW5kaW5nIHJlY292ZXJ5IG9wdGltaXphdGlvbnMuDQoNCk5BVCBiaW5kaW5nIGxv
c3QgaW4gcmVzdGFydCBvciBjcmFzaCBvZiBOQVQgZGV2aWNlOiBJbiB0aGlzIGNhc2UgaXQgaXMg
bGlrZWx5DQp0aGF0IGFuIGFjdGl2ZSBjb25uZWN0aW9uIGhhdmUgbG9zdCBzZXZlcmFsIHBhY2tl
dHMgb24gdGhlIG9sZCBwb3J0IGJlZm9yZSB0aGUNCm1pZ3JhdGlvbiBoYXBwZW5zLiBXaWxsIHRo
b3NlIGxvc3NlcyBiZSByZXByZXNlbnRlZCBpbiB0aGUgbWlncmF0ZWQgQ0Mgc3RhdGU/IA0KQW4N
CnNlbWkgYWN0aXZlIGNvbm5lY3Rpb24gbWF5IGhhdmUgbm90IGxvc3QgYW55IHBhY2tldHMgYW5k
IGluIHdvcnN0IGNhc2UgaGFkIGENCmZhaXJseSBsYXJnZSB3aW5kb3csIHRoZW4gd2VudCBxdWl0
ZSBzb21lIGZldyBzZWNvbmRzIHdpbGwgdGhlIE5BVCBkZXZpY2UNCnJlY292ZXJzIGFuZCB0aHVz
IGEgbGltaXRlZCBhZ2luZyBvZiBDQyBzdGF0ZSBjb3VsZCBoYXZlIG9jY3VycmVkLiANCg0KTkFU
IGxvc3QgYmluZGluZyB0byByZXNvdXJjZSBleGhhdXN0aW9uOiBJbiBjYXNlIG9mIGFuIGF0dGFj
ayBvciBzaW1wbHkNCm92ZXJ3aGVsbWluZyBhbW91bnRzIG9mIGZsb3dzIHRoZSBOQVQgZXhoYXVz
dCBpdHMgcmVzb3VyY2VzIGFuZCBzdGFydHMgcmVjeWNsaW5nDQp0aGUgYmluZGluZ3MgdGhhdCBo
YWQgbG9uZ2VzdCB0aW1lIHNpbmNlIGxhc3QgdXNlLiBUaGF0IGNvdWxkIGluIHdvcnN0IGNhc2UN
CmNhdXNlIGZyZXF1ZW50IHJlYmluZGluZ3MuIEkgd291bGQgc2F5IHRoaXMgaXMgYnJva2VuIE5B
VCBkZXZpY2UgdGhhdCBpcyBiZXR0ZXINCm9mIHJlZnVzaW5nIGJpbmRpbmdzIGluIHRoaXMgc2Nl
bmFyaW8gdGhhbiBtYWtpbmcgZXhpc3RpbmcgYmluZGluZ3MgYnJlYWtpbmcuIA0KDQpDaGFuZ2Ug
b2YgYXR0YWNobWVudCBwb2ludCBiZWhpbmQgYSBDR05BVDogQSBub2RlIGNvdWxkIHBvdGVudGlh
bGx5IGNoYW5nZSBpdHMNCmxvY2FsIElQIGFkZHJlc3MgYnV0IHN0YXkgYmVoaW5kIHRoZSBzYW1l
IENHTkFULiBUaGUgTkFUIHdpbGwgY3JlYXRlIG5ldyBiaW5kaW5nDQphcyBpdCBkb2Vzbid0IGtu
b3cgdGhhdCB0aGlzIGlzIHRoZSBzYW1lIGRldmljZS4gVGhpcyByZXByZXNlbnRzIGFuIGFjdHVh
bCBwYXRoDQpjaGFuZ2UuIEl0IGRvZXNuJ3QgYXBwZWFyIHRoZSBtb3N0IGxpa2VseSBzY2VuYXJp
bywgYnV0IGNvdWxkIG9jY3VyIGZvciBleGFtcGxlDQppZiBJIG1vdmUgZnJvbSBteSBob21lIHdp
ZmkgdG8gbXkgZnJpbmRseSBuZWlnaGJvdXJzIHdpZmkgd2hpY2ggSSBhbHNvIGF0dGFjaA0KYW5k
IHdlIHVzZSB0aGUgc2FtZSBJU1AuIA0KDQpEb2VzIGFueW9uZSBoYXZlIGEgc2NlbmFyaW8gd2hl
cmUgYSBwb3J0IGNoYW5nZSB3b3VsZCBhY3R1YWxseSBvY2N1cnIgd2hlbiB0aGUNClFVSUMgY29u
ZW5jdGlvbiBpcyB0cmFuc21pdHRpbmcgYXQgYW55IHNpZ25pZmljbmF0IHJhdGUgYW5kIHRoZSBw
b3J0IGNoYW5nZQ0Kd291bGQgbm90IGluY3VyciBwYWNrZXQgbG9zcyBvciBzZWNvbmRzIG9mIHRo
ZSBwYXRoIGJlaW5nIGJsb2NrZWQ/IA0KDQpUbyBtZSBpdCBhcHBlYXJzIHRoYXQgdGhlIHNjZW5h
cmlvcyBJIGNhbiB0aGluayBvZiBhbGwgd291bGQgcmVzdWx0IGluDQpzaWduaWZpY25hdCByZWR1
Y3Rpb24gb2YgYWxsb3dhYmxlIHRyYW5zbWlzc2lvbiByYXRlIGFueXdheS4gSGF2ZSBJIG1pc3Nl
ZA0Kc29tZXRoaW5nIHJlbGV2YW50IGhlcmU/IA0KDQoNCkNoZWVycw0KDQpNYWdudXMgV2VzdGVy
bHVuZA0KDQoNCk9uIFRodSwgMjAyMC0wNy0yMyBhdCAxNDowMiAtMDcwMCwgSmFuYSBJeWVuZ2Fy
IHdyb3RlOg0KPiBJJ20gaGFwcHkgd2l0aCB0aGUgcmVzb2x1dGlvbiB0aGF0IFRlZCBwcm9wb3Nl
ZCBhbmQgTGFycyB3cm90ZSB1cCBpbiBQUiAzOTQ1Lg0KPiANCj4gV2Ugc2hvdWxkIG5vdCBmb3Jn
ZXQgdGhhdCBlbmRwb2ludHMgd2lsbCBkbyB3aGF0IHRoZXkgY2hvb3NlIHRvIGRvIG9uIHRoaXMN
Cj4gcGFydGljdWxhciBpc3N1ZS4gSXQncyBwZXJmZWN0bHkgcmVhc29uYWJsZSB0byBhc3N1bWUg
dGhhdCBwb3J0IGNoYW5nZXMgYXJlDQo+IGluZnJlcXVlbnQgYW5kIGRvIG5vdCByZWZsZWN0IGEg
cGF0aCBjaGFuZ2UgY29tbW9ubHkuIEluIHRoZSByYXJlIGNhc2UgdGhhdCBpdA0KPiBoYXBwZW5z
IGFuZCBpbiB0aGUgcmFyZXIgY2FzZSB0aGF0IGl0IGlzIGluIGZhY3QgYSBwYXRoIGNoYW5nZSwg
Ym90aA0KPiBjb25nZXN0aW9uIGNvbnRyb2xsZXJzIGFuZCBSVFQgZXN0aW1hdG9ycyBhcmUgYWRh
cHRpdmUuIFRoZSB0ZXh0IGluIHRoZSBQUg0KPiBjYXB0dXJlcyB0aGlzIHBvc3NpYmlsaXR5LiBU
aGF0IHJlZmxlY3RzIHJlYWxpdHkgYW5kIGlzIGFuIGFkZXF1YXRlbHkgY2F1dGlvdXMNCj4gcmVj
b21tZW5kYXRpb24sIElNTy4NCj4gDQo+IE9uIFRodSwgSnVsIDIzLCAyMDIwIGF0IDExOjQ3IEFN
IENocmlzdGlhbiBIdWl0ZW1hIDxodWl0ZW1hQGh1aXRlbWEubmV0Pg0KPiB3cm90ZToNCj4gPiBP
biA3LzIzLzIwMjAgMTI6NDIgQU0sIExhcnMgRWdnZXJ0IHdyb3RlOg0KPiA+ID4gSGksDQo+ID4g
PiANCj4gPiA+IE9uIDIwMjAtNy0yMywgYXQgMTA6MzQsIEdvcnJ5IEZhaXJodXJzdCA8Z29ycnlA
ZXJnLmFiZG4uYWMudWs+IHdyb3RlOg0KPiA+ID4gPiBUaGVzZSBtZXRob2RzIG9mdGVuIGhhc2gg
YmFzZWQgb24gcG9ydCwgSVAsIGFuZCBtYXliZSBvdGhlciBmaWVsZHMgdG8NCj4gPiA+ID4gc2Vs
ZWN0IGEgcXVldWUgLSBUaGVyZSBhcmUgYSBmaW5pdGUgc2V0IG9mIHF1ZXVlcywgYSByZWhhc2gg
cmVzdWx0cyBpbg0KPiA+ID4gPiB0aGUgdHJhZmZpYyBtb3ZpbmcgcXVldWUgLi4uIHRvIGNob29z
ZXMgYSBkaWZmZXJlbnQgcGF0aCBvciBxdWV1ZSB3aXRoaW4NCj4gPiA+ID4gdGhlIGRldmljZS4g
VGhpcyBtYXBwaW5nIGlzIHN0YXRpc3RpY2FsLCB0aGlzIG1hdHRlcnMgbW9yZSBpZiB0aGUNCj4g
PiA+ID4gbXVsdGlwbGV4aW5nIGlzIGxvdyBhbmQgYSBwb3J0IGNoYW5nZSByZXN1bHRzIGluIHVu
YmFsYW5jZSBhY3Jvc3MNCj4gPiA+ID4gcXVxdWVzL3BhdGhzLg0KPiA+ID4gDQo+ID4gPiBJIGFn
cmVlIHRoaXMgaXMgbW9zdGx5IGEgY29uY2VybiBmb3IgbG93LW11eCdpbmcgY2FzZXMgd2hlbiBh
IHNpbmdsZQ0KPiA+ID4gcmVoYXNoIGNhbiBjcmVhdGUgc2lnbmlmaWNhbnQgaW1iYWxhbmNlLiBI
b3cgY29tbW9uIGFyZSBzdWNoIGRlcGxveW1lbnRzLA0KPiA+ID4gYW5kIGhvdyBtdWNoIG9mIGEg
cHJvYmxlbSBpcyBzdWNoIGEgdGVtcG9yYXJ5IGltYmFsYW5jZSAodGhlIENDIHdpbGwNCj4gPiA+
IGFkanVzdCBxdWlja2x5KS4gRXNwLiBjb21wYXJlZCB0byBmb3JjaW5nIHNsb3ctc3RhcnQgYWZ0
ZXIgZXZlcnkgTkFUDQo+ID4gPiByZWJpbmQuDQo+ID4gDQo+ID4gR29ycnksIExhcnMsIHdoZXJl
IGNhbiB3ZSBmaW5kIGRhdGEgb24gdGhlIE5BVCBiZWhhdmlvciBhbmQgdGhlIHJlbGF0aW9uDQo+
ID4gYmV0d2VlbiBOQVQgcmViaW5kaW5nIGFuZCByb3V0aW5nIHBhdGhzPyBJbiBob21lIHJvdXRl
cnMsIE5BVCByZWJpbmRpbmcNCj4gPiB0eXBpY2FsbHkgb25seSBjaGFuZ2UgaWYgdGhlIHNlc3Np
b24gaXMgcXVpZXQgZm9yIHNvbWUgdGltZS4gRG8gd2Ugb2JzZXJ2ZSBhDQo+ID4gZGlmZmVyZW50
IGJlaGF2aW9yIHdpdGggQ0dOQVQ/IA0KPiA+IC0tIENocmlzdGlhbiBIdWl0ZW1hDQotLSANCkNo
ZWVycw0KDQpNYWdudXMgV2VzdGVybHVuZCANCg0KDQotLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tDQpOZXR3b3Jrcywg
RXJpY3Nzb24gUmVzZWFyY2gNCi0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0NCkVyaWNzc29uIEFCICAgICAgICAgICAg
ICAgICB8IFBob25lICArNDYgMTAgNzE0ODI4Nw0KVG9yc2hhbW5zZ2F0YW4gMjMgICAgICAgICAg
IHwgTW9iaWxlICs0NiA3MyAwOTQ5MDc5DQpTRS0xNjQgODAgU3RvY2tob2xtLCBTd2VkZW4gfCBt
YWlsdG86IG1hZ251cy53ZXN0ZXJsdW5kQGVyaWNzc29uLmNvbQ0KLS0tLS0tLS0tLS0tLS0tLS0t
LS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLS0tLQ0KDQoN
Cg==


From nobody Fri Jul 24 02:41:13 2020
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 8C4EF3A0DC3 for <quic@ietfa.amsl.com>; Fri, 24 Jul 2020 02:41:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level: 
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 tx0iGySkKE1M for <quic@ietfa.amsl.com>; Fri, 24 Jul 2020 02:41:09 -0700 (PDT)
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 B6DA93A0DC9 for <quic@ietf.org>; Fri, 24 Jul 2020 02:41:07 -0700 (PDT)
X-IronPort-AV: E=Sophos; i="5.75,390,1589241600"; d="scan'208,217"; a="36571115"
X-IPAS-Result: =?us-ascii?q?A2FbAAD0qhpf/wEBeApgDgwBAQEBAQEBAQEBAwEBAQESA?= =?us-ascii?q?QEBAQICAQEBAUeBQ4EjWIEKFIEzCoQpkRqKA4lwgiuFbAsBAQEBAQEBAQErD?= =?us-ascii?q?AQBAYRMAheCDCU4EwIQAQEBBQEBAQEBBgIBAQIChkUMhksCAQMdBgpFAgUQA?= =?us-ascii?q?gEIDRUdAwICAh8RFBECBAENBQiDH4F+TQM9rSmBMhqEIQGECQ2CHAaBOAGBZ?= =?us-ascii?q?IRcgi+GHoERQ4IfLj6BBIEWQgKBYRUfgmAzggsiBJJahlWbXU4HgU2BE4MIh?= =?us-ascii?q?U6MIIUUgQuQSwOOBJIOh1yCUIJhlBVOgS0zGieDNVAXAo42GIECAQmCQooYP?= =?us-ascii?q?nQ3AgYBBwEBAwmOHiyBCYERAQE?=
X-URL-LookUp-ScanningError: 1
From: Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>
To: 'Gorry Fairhurst' <gorry@erg.abdn.ac.uk>, Jana Iyengar <jri.ietf@gmail.com>, Christian Huitema <huitema@huitema.net>
CC: Lars Eggert <lars@eggert.org>, QUIC WG <quic@ietf.org>, Martin Thomson <mt@lowentropy.net>, "'emile.stephan@orange.com'" <emile.stephan@orange.com>
Subject: RE: Consensus call for Late-Stage documents, pre-IETF 108 edition
Thread-Topic: Consensus call for Late-Stage documents, pre-IETF 108 edition
Thread-Index: AQHWYYxPmGai3cYa5U+kWY74sRfMOakWdiUQ
Date: Fri, 24 Jul 2020 09:41:04 +0000
Message-ID: <F3B0A07CFD358240926B78A680E166FF1EDE5799@TW-MBX-P03.cnesnet.ad.cnes.fr>
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com> <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org> <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com> <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com> <7b5c104c-36b6-3fe1-4e5b-0e42cc9e2b36@huitema.net> <74ef5430-8e3f-4b6b-b81f-b25443e975b4@www.fastmail.com> <32c098c3-24e4-1d7c-fdf5-33761adacfa8@erg.abdn.ac.uk> <FA3E4F14-570C-4A28-A2C8-EA2B3937E614@eggert.org> <0ee0a444-3910-3e71-54aa-581431495648@erg.abdn.ac.uk> <3644F334-F148-4FF5-AE86-015C073871AC@eggert.org> <c28e05f6-637d-9183-11db-f8daa8b9e7c4@huitema.net> <CACpbDcc86pgVpcN7DHb2s8aRGjzCC4RNjYPnGyDHhUCWg-G9zA@mail.gmail.com> <5114fe5a-30b1-bcdf-7d1e-70b34697a9c0@erg.abdn.ac.uk>
In-Reply-To: <5114fe5a-30b1-bcdf-7d1e-70b34697a9c0@erg.abdn.ac.uk>
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-25560.006
x-tm-as-result: No--25.550600-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: multipart/alternative; boundary="_000_F3B0A07CFD358240926B78A680E166FF1EDE5799TWMBXP03cnesnet_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/jmiLof89EBXQlRh7TVZW9aiEvTo>
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, 24 Jul 2020 09:41:12 -0000

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

DQpEZSA6IFFVSUMgPHF1aWMtYm91bmNlc0BpZXRmLm9yZz4gRGUgbGEgcGFydCBkZSBHb3JyeSBG
YWlyaHVyc3QNCkVudm95w6kgOiB2ZW5kcmVkaSAyNCBqdWlsbGV0IDIwMjAgMDk6MzENCsOAIDog
SmFuYSBJeWVuZ2FyIDxqcmkuaWV0ZkBnbWFpbC5jb20+OyBDaHJpc3RpYW4gSHVpdGVtYSA8aHVp
dGVtYUBodWl0ZW1hLm5ldD4NCkNjIDogTGFycyBFZ2dlcnQgPGxhcnNAZWdnZXJ0Lm9yZz47IFFV
SUMgV0cgPHF1aWNAaWV0Zi5vcmc+OyBNYXJ0aW4gVGhvbXNvbiA8bXRAbG93ZW50cm9weS5uZXQ+
DQpPYmpldCA6IFJlOiBDb25zZW5zdXMgY2FsbCBmb3IgTGF0ZS1TdGFnZSBkb2N1bWVudHMsIHBy
ZS1JRVRGIDEwOCBlZGl0aW9uDQoNCg0KDQpPbiAyMy8wNy8yMDIwIDIyOjAyLCBKYW5hIEl5ZW5n
YXIgd3JvdGU6DQpJJ20gaGFwcHkgd2l0aCB0aGUgcmVzb2x1dGlvbiB0aGF0IFRlZCBwcm9wb3Nl
ZCBhbmQgTGFycyB3cm90ZSB1cCBpbiBQUiAzOTQ1PGh0dHBzOi8vZ2l0aHViLmNvbS9xdWljd2cv
YmFzZS1kcmFmdHMvcHVsbC8zOTQ1Pi4NCg0KV2Ugc2hvdWxkIG5vdCBmb3JnZXQgdGhhdCBlbmRw
b2ludHMgd2lsbCBkbyB3aGF0IHRoZXkgY2hvb3NlIHRvIGRvIG9uIHRoaXMgcGFydGljdWxhciBp
c3N1ZS4gSXQncyBwZXJmZWN0bHkgcmVhc29uYWJsZSB0byBhc3N1bWUgdGhhdCBwb3J0IGNoYW5n
ZXMgYXJlIGluZnJlcXVlbnQgYW5kIGRvIG5vdCByZWZsZWN0IGEgcGF0aCBjaGFuZ2UgY29tbW9u
bHkuIEluIHRoZSByYXJlIGNhc2UgdGhhdCBpdCBoYXBwZW5zIGFuZCBpbiB0aGUgcmFyZXIgY2Fz
ZSB0aGF0IGl0IGlzIGluIGZhY3QgYSBwYXRoIGNoYW5nZSwgYm90aCBjb25nZXN0aW9uIGNvbnRy
b2xsZXJzIGFuZCBSVFQgZXN0aW1hdG9ycyBhcmUgYWRhcHRpdmUuIFRoZSB0ZXh0IGluIHRoZSBQ
UiBjYXB0dXJlcyB0aGlzIHBvc3NpYmlsaXR5LiBUaGF0IHJlZmxlY3RzIHJlYWxpdHkgYW5kIGlz
IGFuIGFkZXF1YXRlbHkgY2F1dGlvdXMgcmVjb21tZW5kYXRpb24sIElNTy4NCg0KDQpBcyB5b3Ug
ZXhwZWN0IEkgZG9uJ3QgYWdyZWUgdGhpcyBpcyBjYXV0aW91czogb3B0aW1pc2luZyBmb3IgYW4g
aW5mcmVxdWVudC9yYXJlIGNhc2UgaXMgbm90IGNhdXRpb3VzLCBpdCBpbnRyb2R1Y2VzIG1vcmUg
Y2hhbmNlIG9mIHVuZGVzcmlhYmxlIHNpZGUgZWZmZWN0cyBvbiBwYXRocyB0aGF0IGFjdHVhbGx5
IGFyZSBkaWZmZXJlbnQuDQoNClRoZXJlIHNlZW1zIHRvIG1lIHRvIGJlIGxpdHRsZSBpbXBhY3Qg
aW4gcmUtaW5pdGlhbGlzaW5nIHRoZSBSVFQgZXN0aW1hdG9yLCB0aGVyZSdzIGFuIGluaXRpYWwg
aGFuZHNoYWtlIGZvciB0aGUgbmV3IHBhdGggZnJvbSB3aGljaCB0aGlzIGNhbiBiZSBpbml0aWFs
aXNlZC4NCg0KW05LXSBUaGVyZSBhcmUgY2FzZXMgd2hlcmUgcmVzdW1pbmcgdGhlIGNvbm5lY3Rp
b24gd2l0aCBwcmV2aW91c2x5IHN0b3JlZCBkYXRhIHJhdGUgaXMgdmVyeSB1c2VmdWwgKHNlZSB0
aGUgMC1SVFQgZHJhZnQgZm9yIFNBVENPTSBjb21tdW5pY2F0aW9ucyB1c2UgY2FzZSkuIEhvd2V2
ZXIsIHRoZXJlIGFyZSByaXNrcyB0aGF0IG5ldHdvcmsgY29uZGl0aW9ucyBoYXZlIGNoYW5nZWQg
KHRoaXMgbWF5IGJlIHRydWVyIGZvciB0aGUgMC1SVFQgIGNhc2UgdGhhbiB0aGUgTkFUIHJlYmlu
ZCBjYXNlKS4gSG93IGFib3V0IGEgcmVjb21tZW5kYXRpb24gZm9yIGEg4oCcc2FmZSBqdW1waW5n
IGJhY2sgdG8gcHJldmlvdXNseSBzdG9yZWQgZGF0YSByYXRl4oCdID8gV2UgaGF2ZSBwcm9wb3Nl
ZCBhIHN0cmF3bWFuIGFsZ29yaXRobSBpbiB0aGUgMC1SVFQgZHJhZnQgKGluIHRoZSBBcHBlbmRp
eCkgdGhhdCBjb3VsZCBiZSByZWxldmFudCBpbiB0aGlzIGNhc2UuDQoNCk15IDJjdHMsDQoNCk5p
Y28NCg0KQ2hyaXN0aWFuOiBJIGFsc28gd291bGQgbG92ZSB0byBzZWUgZGF0YSBhYm91dCB0aGUg
ZnJlcXVlbmN5IGFuZCBwYXRob2xvZ3ksIGJ1dCBkb24ndCBrbm93IG9mIGFueS4NCg0KR29ycnkN
Ck9uIFRodSwgSnVsIDIzLCAyMDIwIGF0IDExOjQ3IEFNIENocmlzdGlhbiBIdWl0ZW1hIDxodWl0
ZW1hQGh1aXRlbWEubmV0PG1haWx0bzpodWl0ZW1hQGh1aXRlbWEubmV0Pj4gd3JvdGU6DQoNCk9u
IDcvMjMvMjAyMCAxMjo0MiBBTSwgTGFycyBFZ2dlcnQgd3JvdGU6DQoNCkhpLA0KDQoNCg0KT24g
MjAyMC03LTIzLCBhdCAxMDozNCwgR29ycnkgRmFpcmh1cnN0IDxnb3JyeUBlcmcuYWJkbi5hYy51
az48bWFpbHRvOmdvcnJ5QGVyZy5hYmRuLmFjLi51az4gd3JvdGU6DQoNClRoZXNlIG1ldGhvZHMg
b2Z0ZW4gaGFzaCBiYXNlZCBvbiBwb3J0LCBJUCwgYW5kIG1heWJlIG90aGVyIGZpZWxkcyB0byBz
ZWxlY3QgYSBxdWV1ZSAtIFRoZXJlIGFyZSBhIGZpbml0ZSBzZXQgb2YgcXVldWVzLCBhIHJlaGFz
aCByZXN1bHRzIGluIHRoZSB0cmFmZmljIG1vdmluZyBxdWV1ZSAuLi4gdG8gY2hvb3NlcyBhIGRp
ZmZlcmVudCBwYXRoIG9yIHF1ZXVlIHdpdGhpbiB0aGUgZGV2aWNlLiBUaGlzIG1hcHBpbmcgaXMg
c3RhdGlzdGljYWwsIHRoaXMgbWF0dGVycyBtb3JlIGlmIHRoZSBtdWx0aXBsZXhpbmcgaXMgbG93
IGFuZCBhIHBvcnQgY2hhbmdlIHJlc3VsdHMgaW4gdW5iYWxhbmNlIGFjcm9zcyBxdXF1ZXMvcGF0
aHMuDQoNCkkgYWdyZWUgdGhpcyBpcyBtb3N0bHkgYSBjb25jZXJuIGZvciBsb3ctbXV4J2luZyBj
YXNlcyB3aGVuIGEgc2luZ2xlIHJlaGFzaCBjYW4gY3JlYXRlIHNpZ25pZmljYW50IGltYmFsYW5j
ZS4gSG93IGNvbW1vbiBhcmUgc3VjaCBkZXBsb3ltZW50cywgYW5kIGhvdyBtdWNoIG9mIGEgcHJv
YmxlbSBpcyBzdWNoIGEgdGVtcG9yYXJ5IGltYmFsYW5jZSAodGhlIENDIHdpbGwgYWRqdXN0IHF1
aWNrbHkpLiBFc3AuIGNvbXBhcmVkIHRvIGZvcmNpbmcgc2xvdy1zdGFydCBhZnRlciBldmVyeSBO
QVQgcmViaW5kLg0KDQoNCg0KR29ycnksIExhcnMsIHdoZXJlIGNhbiB3ZSBmaW5kIGRhdGEgb24g
dGhlIE5BVCBiZWhhdmlvciBhbmQgdGhlIHJlbGF0aW9uIGJldHdlZW4gTkFUIHJlYmluZGluZyBh
bmQgcm91dGluZyBwYXRocz8gSW4gaG9tZSByb3V0ZXJzLCBOQVQgcmViaW5kaW5nIHR5cGljYWxs
eSBvbmx5IGNoYW5nZSBpZiB0aGUgc2Vzc2lvbiBpcyBxdWlldCBmb3Igc29tZSB0aW1lLiBEbyB3
ZSBvYnNlcnZlIGEgZGlmZmVyZW50IGJlaGF2aW9yIHdpdGggQ0dOQVQ/DQoNCi0tIENocmlzdGlh
biBIdWl0ZW1hDQo=

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

PGh0bWwgeG1sbnM6dj0idXJuOnNjaGVtYXMtbWljcm9zb2Z0LWNvbTp2bWwiIHhtbG5zOm89InVy
bjpzY2hlbWFzLW1pY3Jvc29mdC1jb206b2ZmaWNlOm9mZmljZSIgeG1sbnM6dz0idXJuOnNjaGVt
YXMtbWljcm9zb2Z0LWNvbTpvZmZpY2U6d29yZCIgeG1sbnM6bT0iaHR0cDovL3NjaGVtYXMubWlj
cm9zb2Z0LmNvbS9vZmZpY2UvMjAwNC8xMi9vbW1sIiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcv
VFIvUkVDLWh0bWw0MCI+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIg
Y29udGVudD0idGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjxtZXRhIG5hbWU9IkdlbmVyYXRv
ciIgY29udGVudD0iTWljcm9zb2Z0IFdvcmQgMTUgKGZpbHRlcmVkIG1lZGl1bSkiPg0KPHN0eWxl
PjwhLS0NCi8qIEZvbnQgRGVmaW5pdGlvbnMgKi8NCkBmb250LWZhY2UNCgl7Zm9udC1mYW1pbHk6
IkNhbWJyaWEgTWF0aCI7DQoJcGFub3NlLTE6MiA0IDUgMyA1IDQgNiAzIDIgNDt9DQpAZm9udC1m
YWNlDQoJe2ZvbnQtZmFtaWx5OkNhbGlicmk7DQoJcGFub3NlLTE6MiAxNSA1IDIgMiAyIDQgMyAy
IDQ7fQ0KQGZvbnQtZmFjZQ0KCXtmb250LWZhbWlseTpDb25zb2xhczsNCglwYW5vc2UtMToyIDEx
IDYgOSAyIDIgNCAzIDIgNDt9DQovKiBTdHlsZSBEZWZpbml0aW9ucyAqLw0KcC5Nc29Ob3JtYWws
IGxpLk1zb05vcm1hbCwgZGl2Lk1zb05vcm1hbA0KCXttYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0
b206LjAwMDFwdDsNCglmb250LXNpemU6MTIuMHB0Ow0KCWZvbnQtZmFtaWx5OiJUaW1lcyBOZXcg
Um9tYW4iLHNlcmlmO30NCmE6bGluaywgc3Bhbi5Nc29IeXBlcmxpbmsNCgl7bXNvLXN0eWxlLXBy
aW9yaXR5Ojk5Ow0KCWNvbG9yOmJsdWU7DQoJdGV4dC1kZWNvcmF0aW9uOnVuZGVybGluZTt9DQph
OnZpc2l0ZWQsIHNwYW4uTXNvSHlwZXJsaW5rRm9sbG93ZWQNCgl7bXNvLXN0eWxlLXByaW9yaXR5
Ojk5Ow0KCWNvbG9yOnB1cnBsZTsNCgl0ZXh0LWRlY29yYXRpb246dW5kZXJsaW5lO30NCnANCgl7
bXNvLXN0eWxlLXByaW9yaXR5Ojk5Ow0KCW1zby1tYXJnaW4tdG9wLWFsdDphdXRvOw0KCW1hcmdp
bi1yaWdodDowY207DQoJbXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG87DQoJbWFyZ2luLWxlZnQ6
MGNtOw0KCWZvbnQtc2l6ZToxMi4wcHQ7DQoJZm9udC1mYW1pbHk6IlRpbWVzIE5ldyBSb21hbiIs
c2VyaWY7fQ0KcHJlDQoJe21zby1zdHlsZS1wcmlvcml0eTo5OTsNCgltc28tc3R5bGUtbGluazoi
UHLDqWZvcm1hdMOpIEhUTUwgQ2FyIjsNCgltYXJnaW46MGNtOw0KCW1hcmdpbi1ib3R0b206LjAw
MDFwdDsNCglmb250LXNpemU6MTAuMHB0Ow0KCWZvbnQtZmFtaWx5OiJDb3VyaWVyIE5ldyI7fQ0K
cC5tc29ub3JtYWwwLCBsaS5tc29ub3JtYWwwLCBkaXYubXNvbm9ybWFsMA0KCXttc28tc3R5bGUt
bmFtZTptc29ub3JtYWw7DQoJbXNvLW1hcmdpbi10b3AtYWx0OmF1dG87DQoJbWFyZ2luLXJpZ2h0
OjBjbTsNCgltc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0bzsNCgltYXJnaW4tbGVmdDowY207DQoJ
Zm9udC1zaXplOjEyLjBwdDsNCglmb250LWZhbWlseToiVGltZXMgTmV3IFJvbWFuIixzZXJpZjt9
DQpzcGFuLlByZm9ybWF0SFRNTENhcg0KCXttc28tc3R5bGUtbmFtZToiUHLDqWZvcm1hdMOpIEhU
TUwgQ2FyIjsNCgltc28tc3R5bGUtcHJpb3JpdHk6OTk7DQoJbXNvLXN0eWxlLWxpbms6IlByw6lm
b3JtYXTDqSBIVE1MIjsNCglmb250LWZhbWlseTpDb25zb2xhczt9DQpzcGFuLkVtYWlsU3R5bGUy
MQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25hbC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJy
aSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5kb3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21z
by1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0KCWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29y
ZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3OTIuMHB0Ow0KCW1hcmdpbjo3MC44NXB0IDcwLjg1
cHQgNzAuODVwdCA3MC44NXB0O30NCmRpdi5Xb3JkU2VjdGlvbjENCgl7cGFnZTpXb3JkU2VjdGlv
bjE7fQ0KLS0+PC9zdHlsZT48IS0tW2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlZGVmYXVs
dHMgdjpleHQ9ImVkaXQiIHNwaWRtYXg9IjEwMjYiIC8+DQo8L3htbD48IVtlbmRpZl0tLT48IS0t
W2lmIGd0ZSBtc28gOV0+PHhtbD4NCjxvOnNoYXBlbGF5b3V0IHY6ZXh0PSJlZGl0Ij4NCjxvOmlk
bWFwIHY6ZXh0PSJlZGl0IiBkYXRhPSIxIiAvPg0KPC9vOnNoYXBlbGF5b3V0PjwveG1sPjwhW2Vu
ZGlmXS0tPg0KPC9oZWFkPg0KPGJvZHkgbGFuZz0iRlIiIGxpbms9ImJsdWUiIHZsaW5rPSJwdXJw
bGUiPg0KPGRpdiBjbGFzcz0iV29yZFNlY3Rpb24xIj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5OiZxdW90O0NhbGlicmkmcXVv
dDssc2Fucy1zZXJpZjttc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286
cD48L3NwYW4+PC9wPg0KPGRpdj4NCjxkaXYgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci10b3A6
c29saWQgI0UxRTFFMSAxLjBwdDtwYWRkaW5nOjMuMHB0IDBjbSAwY20gMGNtIj4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxiPjxzcGFuIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+RGUmbmJzcDs6PC9zcGFuPjwvYj48c3Bh
biBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWYiPiBRVUlDICZsdDtxdWljLWJvdW5jZXNAaWV0Zi5vcmcmZ3Q7DQo8Yj5EZSBs
YSBwYXJ0IGRlPC9iPiBHb3JyeSBGYWlyaHVyc3Q8YnI+DQo8Yj5FbnZvecOpJm5ic3A7OjwvYj4g
dmVuZHJlZGkgMjQganVpbGxldCAyMDIwIDA5OjMxPGJyPg0KPGI+w4AmbmJzcDs6PC9iPiBKYW5h
IEl5ZW5nYXIgJmx0O2pyaS5pZXRmQGdtYWlsLmNvbSZndDs7IENocmlzdGlhbiBIdWl0ZW1hICZs
dDtodWl0ZW1hQGh1aXRlbWEubmV0Jmd0Ozxicj4NCjxiPkNjJm5ic3A7OjwvYj4gTGFycyBFZ2dl
cnQgJmx0O2xhcnNAZWdnZXJ0Lm9yZyZndDs7IFFVSUMgV0cgJmx0O3F1aWNAaWV0Zi5vcmcmZ3Q7
OyBNYXJ0aW4gVGhvbXNvbiAmbHQ7bXRAbG93ZW50cm9weS5uZXQmZ3Q7PGJyPg0KPGI+T2JqZXQm
bmJzcDs6PC9iPiBSZTogQ29uc2Vuc3VzIGNhbGwgZm9yIExhdGUtU3RhZ2UgZG9jdW1lbnRzLCBw
cmUtSUVURiAxMDggZWRpdGlvbjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjwvZGl2Pg0KPC9kaXY+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxwPjxvOnA+Jm5i
c3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPk9uIDIzLzA3LzIwMjAg
MjI6MDIsIEphbmEgSXllbmdhciB3cm90ZTo8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2Nr
cXVvdGUgc3R5bGU9Im1hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLWJvdHRvbTo1LjBwdCI+DQo8ZGl2
Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+SSdtIGhhcHB5IHdpdGggdGhlIHJlc29sdXRpb24gdGhh
dCBUZWQgcHJvcG9zZWQgYW5kIExhcnMgd3JvdGUgdXAgaW4NCjxhIGhyZWY9Imh0dHBzOi8vZ2l0
aHViLmNvbS9xdWljd2cvYmFzZS1kcmFmdHMvcHVsbC8zOTQ1Ij5QUiAzOTQ1PC9hPi4gPG86cD48
L286cD48L3A+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4mbmJzcDs8L286cD48
L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5XZSBzaG91bGQgbm90IGZv
cmdldCB0aGF0IGVuZHBvaW50cyB3aWxsIGRvIHdoYXQgdGhleSBjaG9vc2UgdG8gZG8gb24gdGhp
cyBwYXJ0aWN1bGFyIGlzc3VlLiBJdCdzIHBlcmZlY3RseSByZWFzb25hYmxlIHRvIGFzc3VtZSB0
aGF0IHBvcnQgY2hhbmdlcyBhcmUgaW5mcmVxdWVudCBhbmQgZG8gbm90IHJlZmxlY3QgYSBwYXRo
IGNoYW5nZSBjb21tb25seS4gSW4gdGhlIHJhcmUgY2FzZSB0aGF0IGl0IGhhcHBlbnMNCiBhbmQg
aW4gdGhlIHJhcmVyIGNhc2UgdGhhdCBpdCBpcyBpbiBmYWN0IGEgcGF0aCBjaGFuZ2UsIGJvdGgg
Y29uZ2VzdGlvbiBjb250cm9sbGVycyBhbmQgUlRUIGVzdGltYXRvcnMgYXJlIGFkYXB0aXZlLiBU
aGUgdGV4dCBpbiB0aGUgUFIgY2FwdHVyZXMgdGhpcyBwb3NzaWJpbGl0eS4gVGhhdCByZWZsZWN0
cyByZWFsaXR5IGFuZCBpcyBhbiBhZGVxdWF0ZWx5IGNhdXRpb3VzIHJlY29tbWVuZGF0aW9uLCBJ
TU8uPG86cD48L286cD48L3A+DQo8L2Rpdj4NCjwvZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Jsb2NrcXVvdGU+DQo8cD5BcyB5b3UgZXhwZWN0IEkg
ZG9uJ3QgYWdyZWUgdGhpcyBpcyBjYXV0aW91czogb3B0aW1pc2luZyBmb3IgYW4gaW5mcmVxdWVu
dC9yYXJlIGNhc2UgaXMgbm90IGNhdXRpb3VzLCBpdCBpbnRyb2R1Y2VzIG1vcmUgY2hhbmNlIG9m
IHVuZGVzcmlhYmxlIHNpZGUgZWZmZWN0cyBvbiBwYXRocyB0aGF0IGFjdHVhbGx5IGFyZSBkaWZm
ZXJlbnQuDQo8bzpwPjwvbzpwPjwvcD4NCjxwPlRoZXJlIHNlZW1zIHRvIG1lIHRvIGJlIGxpdHRs
ZSBpbXBhY3QgaW4gcmUtaW5pdGlhbGlzaW5nIHRoZSBSVFQgZXN0aW1hdG9yLCB0aGVyZSdzIGFu
IGluaXRpYWwgaGFuZHNoYWtlIGZvciB0aGUgbmV3IHBhdGggZnJvbSB3aGljaCB0aGlzIGNhbiBi
ZSBpbml0aWFsaXNlZC48bzpwPjwvbzpwPjwvcD4NCjxwPjxiPjxpPjxzcGFuIGxhbmc9IkVOLVVT
IiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7
LHNhbnMtc2VyaWYiPltOS10gVGhlcmUgYXJlIGNhc2VzIHdoZXJlIHJlc3VtaW5nIHRoZSBjb25u
ZWN0aW9uIHdpdGggcHJldmlvdXNseSBzdG9yZWQgZGF0YSByYXRlIGlzIHZlcnkgdXNlZnVsIChz
ZWUgdGhlIDAtUlRUIGRyYWZ0IGZvciBTQVRDT00gY29tbXVuaWNhdGlvbnMgdXNlIGNhc2UpLiBI
b3dldmVyLCB0aGVyZQ0KIGFyZSByaXNrcyB0aGF0IG5ldHdvcmsgY29uZGl0aW9ucyBoYXZlIGNo
YW5nZWQgKHRoaXMgbWF5IGJlIHRydWVyIGZvciB0aGUgMC1SVFQmbmJzcDsgY2FzZSB0aGFuIHRo
ZSBOQVQgcmViaW5kIGNhc2UpLiBIb3cgYWJvdXQgYSByZWNvbW1lbmRhdGlvbiBmb3IgYSDigJxz
YWZlIGp1bXBpbmcgYmFjayB0byBwcmV2aW91c2x5IHN0b3JlZCBkYXRhIHJhdGXigJ0gPyBXZSBo
YXZlIHByb3Bvc2VkIGEgc3RyYXdtYW4gYWxnb3JpdGhtIGluIHRoZSAwLVJUVCBkcmFmdA0KIChp
biB0aGUgQXBwZW5kaXgpIHRoYXQgY291bGQgYmUgcmVsZXZhbnQgaW4gdGhpcyBjYXNlLiA8bzpw
PjwvbzpwPjwvc3Bhbj48L2k+PC9iPjwvcD4NCjxwPjxiPjxpPjxzcGFuIGxhbmc9IkVOLVVTIiBz
dHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWlseTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNh
bnMtc2VyaWYiPk15IDJjdHMsDQo8bzpwPjwvbzpwPjwvc3Bhbj48L2k+PC9iPjwvcD4NCjxwPjxi
PjxpPjxzcGFuIGxhbmc9IkVOLVVTIiBzdHlsZT0iZm9udC1zaXplOjExLjBwdDtmb250LWZhbWls
eTomcXVvdDtDYWxpYnJpJnF1b3Q7LHNhbnMtc2VyaWYiPk5pY28gJm5ic3A7PC9zcGFuPjwvaT48
L2I+PHNwYW4gbGFuZz0iRU4tVVMiIHN0eWxlPSJmb250LXNpemU6MTEuMHB0O2ZvbnQtZmFtaWx5
OiZxdW90O0NhbGlicmkmcXVvdDssc2Fucy1zZXJpZiI+PG86cD48L286cD48L3NwYW4+PC9wPg0K
PHA+Q2hyaXN0aWFuOiBJIGFsc28gd291bGQgbG92ZSB0byBzZWUgZGF0YSBhYm91dCB0aGUgZnJl
cXVlbmN5IGFuZCBwYXRob2xvZ3ksIGJ1dCBkb24ndCBrbm93IG9mIGFueS48bzpwPjwvbzpwPjwv
cD4NCjxwPkdvcnJ5PG86cD48L286cD48L3A+DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRv
cDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCI+T24gVGh1LCBKdWwgMjMsIDIwMjAgYXQgMTE6NDcgQU0gQ2hyaXN0aWFuIEh1aXRl
bWEgJmx0OzxhIGhyZWY9Im1haWx0bzpodWl0ZW1hQGh1aXRlbWEubmV0Ij5odWl0ZW1hQGh1aXRl
bWEubmV0PC9hPiZndDsgd3JvdGU6PG86cD48L286cD48L3A+DQo8L2Rpdj4NCjxibG9ja3F1b3Rl
IHN0eWxlPSJib3JkZXI6bm9uZTtib3JkZXItbGVmdDpzb2xpZCAjQ0NDQ0NDIDEuMHB0O3BhZGRp
bmc6MGNtIDBjbSAwY20gNi4wcHQ7bWFyZ2luLWxlZnQ6NC44cHQ7bWFyZ2luLXJpZ2h0OjBjbSI+
DQo8ZGl2Pg0KPHA+T24gNy8yMy8yMDIwIDEyOjQyIEFNLCBMYXJzIEVnZ2VydCB3cm90ZTo8bzpw
PjwvbzpwPjwvcD4NCjxibG9ja3F1b3RlIHN0eWxlPSJtYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1i
b3R0b206NS4wcHQiPg0KPHByZT5IaSw8bzpwPjwvbzpwPjwvcHJlPg0KPHByZT48bzpwPiZuYnNw
OzwvbzpwPjwvcHJlPg0KPHByZT5PbiAyMDIwLTctMjMsIGF0IDEwOjM0LCBHb3JyeSBGYWlyaHVy
c3QgPGEgaHJlZj0ibWFpbHRvOmdvcnJ5QGVyZy5hYmRuLmFjLi51ayIgdGFyZ2V0PSJfYmxhbmsi
PiZsdDtnb3JyeUBlcmcuYWJkbi5hYy51ayZndDs8L2E+IHdyb3RlOjxvOnA+PC9vOnA+PC9wcmU+
DQo8YmxvY2txdW90ZSBzdHlsZT0ibWFyZ2luLXRvcDo1LjBwdDttYXJnaW4tYm90dG9tOjUuMHB0
Ij4NCjxwcmU+PHNwYW4gc3R5bGU9ImNvbG9yOmJsYWNrIj5UaGVzZSBtZXRob2RzIG9mdGVuIGhh
c2ggYmFzZWQgb24gcG9ydCwgSVAsIGFuZCBtYXliZSBvdGhlciBmaWVsZHMgdG8gc2VsZWN0IGEg
cXVldWUgLSBUaGVyZSBhcmUgYSBmaW5pdGUgc2V0IG9mIHF1ZXVlcywgYSByZWhhc2ggcmVzdWx0
cyBpbiB0aGUgdHJhZmZpYyBtb3ZpbmcgcXVldWUgLi4uIHRvIGNob29zZXMgYSBkaWZmZXJlbnQg
cGF0aCBvciBxdWV1ZSB3aXRoaW4gdGhlIGRldmljZS4gVGhpcyBtYXBwaW5nIGlzIHN0YXRpc3Rp
Y2FsLCB0aGlzIG1hdHRlcnMgbW9yZSBpZiB0aGUgbXVsdGlwbGV4aW5nIGlzIGxvdyBhbmQgYSBw
b3J0IGNoYW5nZSByZXN1bHRzIGluIHVuYmFsYW5jZSBhY3Jvc3MgcXVxdWVzL3BhdGhzLjxvOnA+
PC9vOnA+PC9zcGFuPjwvcHJlPg0KPC9ibG9ja3F1b3RlPg0KPHByZT5JIGFncmVlIHRoaXMgaXMg
bW9zdGx5IGEgY29uY2VybiBmb3IgbG93LW11eCdpbmcgY2FzZXMgd2hlbiBhIHNpbmdsZSByZWhh
c2ggY2FuIGNyZWF0ZSBzaWduaWZpY2FudCBpbWJhbGFuY2UuIEhvdyBjb21tb24gYXJlIHN1Y2gg
ZGVwbG95bWVudHMsIGFuZCBob3cgbXVjaCBvZiBhIHByb2JsZW0gaXMgc3VjaCBhIHRlbXBvcmFy
eSBpbWJhbGFuY2UgKHRoZSBDQyB3aWxsIGFkanVzdCBxdWlja2x5KS4gRXNwLiBjb21wYXJlZCB0
byBmb3JjaW5nIHNsb3ctc3RhcnQgYWZ0ZXIgZXZlcnkgTkFUIHJlYmluZC48bzpwPjwvbzpwPjwv
cHJlPg0KPC9ibG9ja3F1b3RlPg0KPHA+PG86cD4mbmJzcDs8L286cD48L3A+DQo8cD5Hb3JyeSwg
TGFycywgd2hlcmUgY2FuIHdlIGZpbmQgZGF0YSBvbiB0aGUgTkFUIGJlaGF2aW9yIGFuZCB0aGUg
cmVsYXRpb24gYmV0d2VlbiBOQVQgcmViaW5kaW5nIGFuZCByb3V0aW5nIHBhdGhzPyBJbiBob21l
IHJvdXRlcnMsIE5BVCByZWJpbmRpbmcgdHlwaWNhbGx5IG9ubHkgY2hhbmdlIGlmIHRoZSBzZXNz
aW9uIGlzIHF1aWV0IGZvciBzb21lIHRpbWUuIERvIHdlIG9ic2VydmUgYSBkaWZmZXJlbnQgYmVo
YXZpb3Igd2l0aCBDR05BVD8NCjxvOnA+PC9vOnA+PC9wPg0KPHA+LS0gQ2hyaXN0aWFuIEh1aXRl
bWE8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0KPC9ibG9ja3F1b3RlPg0KPC9kaXY+DQo8L2Jsb2Nr
cXVvdGU+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_F3B0A07CFD358240926B78A680E166FF1EDE5799TWMBXP03cnesnet_--


From nobody Fri Jul 24 11:01:46 2020
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 93F373A1132 for <quic@ietfa.amsl.com>; Fri, 24 Jul 2020 11:01:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level: 
X-Spam-Status: No, score=-17.599 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, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, 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 jy4LiKrbHR67 for <quic@ietfa.amsl.com>; Fri, 24 Jul 2020 11:01:35 -0700 (PDT)
Received: from mail-yb1-xb44.google.com (mail-yb1-xb44.google.com [IPv6:2607:f8b0:4864:20::b44]) (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 2F92C3A1104 for <quic@ietf.org>; Fri, 24 Jul 2020 11:01:35 -0700 (PDT)
Received: by mail-yb1-xb44.google.com with SMTP id m200so959121ybf.10 for <quic@ietf.org>; Fri, 24 Jul 2020 11:01:35 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=19Ic3bFcSGXusdq3YNGcASnDomWYaV51JlW/PTFuoL8=; b=kAp8Ln+ltyUdgfssVcqnaijQVm3UjAhl3NlJODo1UooL/PzDW/pYIxguOeKvM79Z28 5CdydMClmZH6bsF+5D2zwwjSyj7P0d03ga+ioRENYFDiVR/X4i89Yjk/h1Wa0bFa2WDK 5dHRsT9aOZkFM5bWNvC7oE1FdjyDizbvjVS/iG3achqhH/2YldVifT29t8XugkrCQqPN qITJOFNgqcUVoC8T2CuTGlexP1UkQCqrNJg7CFNe4PfTrBXADVIVbJRxYi7d8yNPf+oT VZ7OYP5t+6sp/lFGafOLJStXEQ3ficpeVgQMFnlVGz0Lz29kcgoGpet6zBorZBGmg5nb 9Zzg==
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=19Ic3bFcSGXusdq3YNGcASnDomWYaV51JlW/PTFuoL8=; b=SGYtepVF40vh5uMOUevAkFAxjnpfhdNjV12jLUkVmaTXmrbtKHCLG3OlMgG/E1vE33 6YwLB5YaEy85EZiiv6oRIexu/5DV4FKkc6eNRgOGv24gbNbCNG/W75nk4wTWiB9iiIwD x/QY6IVJcRVHUILoyDX46S+yq2emX1Bfvug4tnxd/XgaC4ECdOqByaAB1FSQZjU1uZju Y5jyftlUFL35OapZcbCQqth5lNW8dux1MMr0HkwVtoW/GTQsqYf4cAX2BNdO/EgxY4T2 rUe04wWFZFiq3MngBP56JTuUvNulqVIMhIM1Xs0NZzPNbHVq2dhaE0IcujLEaLxMzTuK KXPA==
X-Gm-Message-State: AOAM530773zm8cNfPiELTAfWJYO4slnn7bDCNTFLOFY5k46As5NPXr9x w8VUBLW465G8UGS2YBmvRgsW8b0bswsHVenF2ClMXw==
X-Google-Smtp-Source: ABdhPJwLOS9PjmxzW6dvstr+t9ZXJt6jLfjNRFQgHnm+NP81O8qaQXDPTRruCOyOqGL8fcJepN6kEqQjcO3fMD1B5GY=
X-Received: by 2002:a25:3106:: with SMTP id x6mr15587711ybx.364.1595613693923;  Fri, 24 Jul 2020 11:01:33 -0700 (PDT)
MIME-Version: 1.0
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com> <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org> <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com> <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com> <7b5c104c-36b6-3fe1-4e5b-0e42cc9e2b36@huitema.net> <74ef5430-8e3f-4b6b-b81f-b25443e975b4@www.fastmail.com> <32c098c3-24e4-1d7c-fdf5-33761adacfa8@erg.abdn.ac.uk> <FA3E4F14-570C-4A28-A2C8-EA2B3937E614@eggert.org> <0ee0a444-3910-3e71-54aa-581431495648@erg.abdn.ac.uk> <3644F334-F148-4FF5-AE86-015C073871AC@eggert.org> <c28e05f6-637d-9183-11db-f8daa8b9e7c4@huitema.net> <CACpbDcc86pgVpcN7DHb2s8aRGjzCC4RNjYPnGyDHhUCWg-G9zA@mail.gmail.com> <337cd3d0841e9d94a034aa2402ac2a030af550f8.camel@ericsson.com>
In-Reply-To: <337cd3d0841e9d94a034aa2402ac2a030af550f8.camel@ericsson.com>
From: Ian Swett <ianswett@google.com>
Date: Fri, 24 Jul 2020 14:01:22 -0400
Message-ID: <CAKcm_gM73QaQ_eruoy7YNnrhUF_G+SNPzFxA99RF=m7yCa98Sw@mail.gmail.com>
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
To: Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org>
Cc: "huitema@huitema.net" <huitema@huitema.net>, "jri.ietf@gmail.com" <jri.ietf@gmail.com>,  "gorry@erg.abdn.ac.uk" <gorry@erg.abdn.ac.uk>, "lars@eggert.org" <lars@eggert.org>, "quic@ietf.org" <quic@ietf.org>,  "mt@lowentropy.net" <mt@lowentropy.net>
Content-Type: multipart/alternative; boundary="0000000000006d662805ab33c35d"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/AEx5ooZouLC9VWqD5g_kt15aIug>
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, 24 Jul 2020 18:01:45 -0000

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

I'm happy with the direction of the PR.

I don't think it's possible to compare this to TCP, since in TCP if the NAT
hole is dropped, the connection is closed.

Magnus, I'm not sure change of attachment behind a CGN is very likely based
on where I've seen CGN deployed.  Also, it'd require migration from Wifi to
Wifi, which is a lot less common than Wifi to Cell or Cell to Wifi.  But
even so, two physically adjacent wireless networks on the same ISP probably
have more in common than not.

There's a very real cost to re-entering slow-start, not just in terms of
time, but also in terms of the packet loss and bufferbloat it tends to
cause.  Congestion controllers are virtually always sending at the wrong
rate, so this comes down to whether continuing with the existing estimates
are better than starting over.  In the case of a port change, I think it's
a very good bet that the existing estimates are better.

One additional note: Clients MUST change Connection ID if they
intentionally migrate, so a server can use the lack of CID change as a
signal that it was likely an NAT or other unintended path change.

Ian


On Fri, Jul 24, 2020 at 3:47 AM Magnus Westerlund <magnus.westerlund=
40ericsson.com@dmarc.ietf.org> wrote:

> Hi,
>
> So if I understand this correctly we have a couple of different reasons for
> reasons for the port change to occur.
>
> NAT binding times out: In this case the CC state should also have been
> aged as
> the QUIC connection has not sent anything for many seconds. I would think a
> minimal of 5 seconds, likely at least 30 seconds of inactivity for an
> established QUIC connection as it will have gotten the NAT into a
> bi-directional
> UDP flow state, rather than a one of request response state, like for NATs
> with
> DNS binding recovery optimizations.
>
> NAT binding lost in restart or crash of NAT device: In this case it is
> likely
> that an active connection have lost several packets on the old port before
> the
> migration happens. Will those losses be represented in the migrated CC
> state?
> An
> semi active connection may have not lost any packets and in worst case had
> a
> fairly large window, then went quite some few seconds will the NAT device
> recovers and thus a limited aging of CC state could have occurred.
>
> NAT lost binding to resource exhaustion: In case of an attack or simply
> overwhelming amounts of flows the NAT exhaust its resources and starts
> recycling
> the bindings that had longest time since last use. That could in worst case
> cause frequent rebindings. I would say this is broken NAT device that is
> better
> of refusing bindings in this scenario than making existing bindings
> breaking.
>
> Change of attachment point behind a CGNAT: A node could potentially change
> its
> local IP address but stay behind the same CGNAT. The NAT will create new
> binding
> as it doesn't know that this is the same device. This represents an actual
> path
> change. It doesn't appear the most likely scenario, but could occur for
> example
> if I move from my home wifi to my frindly neighbours wifi which I also
> attach
> and we use the same ISP.
>
> Does anyone have a scenario where a port change would actually occurr when
> the
> QUIC conenction is transmitting at any significnat rate and the port change
> would not incurr packet loss or seconds of the path being blocked?
>
> To me it appears that the scenarios I can think of all would result in
> significnat reduction of allowable transmission rate anyway. Have I missed
> something relevant here?
>
>
> Cheers
>
> Magnus Westerlund
>
>
> On Thu, 2020-07-23 at 14:02 -0700, Jana Iyengar wrote:
> > I'm happy with the resolution that Ted proposed and Lars wrote up in PR
> 3945.
> >
> > We should not forget that endpoints will do what they choose to do on
> this
> > particular issue. It's perfectly reasonable to assume that port changes
> are
> > infrequent and do not reflect a path change commonly. In the rare case
> that it
> > happens and in the rarer case that it is in fact a path change, both
> > congestion controllers and RTT estimators are adaptive. The text in the
> PR
> > captures this possibility. That reflects reality and is an adequately
> cautious
> > recommendation, IMO.
> >
> > On Thu, Jul 23, 2020 at 11:47 AM Christian Huitema <huitema@huitema.net>
> > wrote:
> > > On 7/23/2020 12:42 AM, Lars Eggert wrote:
> > > > Hi,
> > > >
> > > > On 2020-7-23, at 10:34, Gorry Fairhurst <gorry@erg.abdn.ac.uk>
> wrote:
> > > > > These methods often hash based on port, IP, and maybe other fields
> to
> > > > > select a queue - There are a finite set of queues, a rehash
> results in
> > > > > the traffic moving queue ... to chooses a different path or queue
> within
> > > > > the device. This mapping is statistical, this matters more if the
> > > > > multiplexing is low and a port change results in unbalance across
> > > > > quques/paths.
> > > >
> > > > I agree this is mostly a concern for low-mux'ing cases when a single
> > > > rehash can create significant imbalance. How common are such
> deployments,
> > > > and how much of a problem is such a temporary imbalance (the CC will
> > > > adjust quickly). Esp. compared to forcing slow-start after every NAT
> > > > rebind.
> > >
> > > Gorry, Lars, where can we find data on the NAT behavior and the
> relation
> > > between NAT rebinding and routing paths? In home routers, NAT rebinding
> > > typically only change if the session is quiet for some time. Do we
> observe a
> > > different behavior with CGNAT?
> > > -- Christian Huitema
> --
> Cheers
>
> Magnus Westerlund
>
>
> ----------------------------------------------------------------------
> Networks, Ericsson Research
> ----------------------------------------------------------------------
> Ericsson AB                 | Phone  +46 10 7148287
> <+46%2010%20714%2082%2087>
> Torshamnsgatan 23           | Mobile +46 73 0949079
> <+46%2073%20094%2090%2079>
> SE-164 80 Stockholm, Sweden | mailto: magnus.westerlund@ericsson.com
> ----------------------------------------------------------------------
>
>
>

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

<div dir=3D"ltr">I&#39;m happy with the direction of the PR.<div><br></div>=
<div>I don&#39;t think it&#39;s possible=C2=A0to compare this to TCP, since=
 in TCP if the NAT hole is dropped, the connection is closed.</div><div><br=
></div><div>Magnus, I&#39;m not sure change of attachment behind a CGN is v=
ery likely based on where I&#39;ve seen CGN deployed.=C2=A0 Also, it&#39;d =
require migration from Wifi to Wifi, which is a lot less common than Wifi t=
o Cell or Cell to Wifi.=C2=A0 But even so, two physically adjacent wireless=
 networks on the same ISP probably have more in common than not.</div><div>=
<br></div><div>There&#39;s a very real cost to re-entering slow-start, not =
just in terms of time, but also in terms of the packet loss and bufferbloat=
 it tends to cause.=C2=A0 Congestion controllers are virtually always sendi=
ng at the wrong rate, so this comes down to whether continuing with the exi=
sting estimates are better than starting over.=C2=A0 In the case of a port =
change, I think it&#39;s a very good bet that the existing estimates are be=
tter.</div><div><br></div><div>One additional note: Clients MUST change Con=
nection ID if they intentionally migrate, so a server can use the lack of C=
ID change as a signal that it was likely an NAT or other unintended path ch=
ange.</div><div><br></div><div></div><div>Ian</div><div><br></div></div><br=
><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Fri, J=
ul 24, 2020 at 3:47 AM Magnus Westerlund &lt;magnus.westerlund=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,<br>
<br>
So if I understand this correctly we have a couple of different reasons for=
<br>
reasons for the port change to occur.<br>
<br>
NAT binding times out: In this case the CC state should also have been aged=
 as<br>
the QUIC connection has not sent anything for many seconds. I would think a=
<br>
minimal of 5 seconds, likely at least 30 seconds of inactivity for an<br>
established QUIC connection as it will have gotten the NAT into a bi-direct=
ional <br>
UDP flow state, rather than a one of request response state, like for NATs =
with<br>
DNS binding recovery optimizations.<br>
<br>
NAT binding lost in restart or crash of NAT device: In this case it is like=
ly<br>
that an active connection have lost several packets on the old port before =
the<br>
migration happens. Will those losses be represented in the migrated CC stat=
e? <br>
An<br>
semi active connection may have not lost any packets and in worst case had =
a<br>
fairly large window, then went quite some few seconds will the NAT device<b=
r>
recovers and thus a limited aging of CC state could have occurred. <br>
<br>
NAT lost binding to resource exhaustion: In case of an attack or simply<br>
overwhelming amounts of flows the NAT exhaust its resources and starts recy=
cling<br>
the bindings that had longest time since last use. That could in worst case=
<br>
cause frequent rebindings. I would say this is broken NAT device that is be=
tter<br>
of refusing bindings in this scenario than making existing bindings breakin=
g. <br>
<br>
Change of attachment point behind a CGNAT: A node could potentially change =
its<br>
local IP address but stay behind the same CGNAT. The NAT will create new bi=
nding<br>
as it doesn&#39;t know that this is the same device. This represents an act=
ual path<br>
change. It doesn&#39;t appear the most likely scenario, but could occur for=
 example<br>
if I move from my home wifi to my frindly neighbours wifi which I also atta=
ch<br>
and we use the same ISP. <br>
<br>
Does anyone have a scenario where a port change would actually occurr when =
the<br>
QUIC conenction is transmitting at any significnat rate and the port change=
<br>
would not incurr packet loss or seconds of the path being blocked? <br>
<br>
To me it appears that the scenarios I can think of all would result in<br>
significnat reduction of allowable transmission rate anyway. Have I missed<=
br>
something relevant here? <br>
<br>
<br>
Cheers<br>
<br>
Magnus Westerlund<br>
<br>
<br>
On Thu, 2020-07-23 at 14:02 -0700, Jana Iyengar wrote:<br>
&gt; I&#39;m happy with the resolution that Ted proposed and Lars wrote up =
in PR 3945.<br>
&gt; <br>
&gt; We should not forget that endpoints will do what they choose to do on =
this<br>
&gt; particular issue. It&#39;s perfectly reasonable to assume that port ch=
anges are<br>
&gt; infrequent and do not reflect a path change commonly. In the rare case=
 that it<br>
&gt; happens and in the rarer case that it is in fact a path change, both<b=
r>
&gt; congestion controllers and RTT estimators are adaptive. The text in th=
e PR<br>
&gt; captures this possibility. That reflects reality and is an adequately =
cautious<br>
&gt; recommendation, IMO.<br>
&gt; <br>
&gt; On Thu, Jul 23, 2020 at 11:47 AM Christian Huitema &lt;<a href=3D"mail=
to:huitema@huitema.net" target=3D"_blank">huitema@huitema.net</a>&gt;<br>
&gt; wrote:<br>
&gt; &gt; On 7/23/2020 12:42 AM, Lars Eggert wrote:<br>
&gt; &gt; &gt; Hi,<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; On 2020-7-23, at 10:34, Gorry Fairhurst &lt;<a href=3D"mailt=
o:gorry@erg.abdn.ac.uk" target=3D"_blank">gorry@erg.abdn.ac.uk</a>&gt; wrot=
e:<br>
&gt; &gt; &gt; &gt; These methods often hash based on port, IP, and maybe o=
ther fields to<br>
&gt; &gt; &gt; &gt; select a queue - There are a finite set of queues, a re=
hash results in<br>
&gt; &gt; &gt; &gt; the traffic moving queue ... to chooses a different pat=
h or queue within<br>
&gt; &gt; &gt; &gt; the device. This mapping is statistical, this matters m=
ore if the<br>
&gt; &gt; &gt; &gt; multiplexing is low and a port change results in unbala=
nce across<br>
&gt; &gt; &gt; &gt; quques/paths.<br>
&gt; &gt; &gt; <br>
&gt; &gt; &gt; I agree this is mostly a concern for low-mux&#39;ing cases w=
hen a single<br>
&gt; &gt; &gt; rehash can create significant imbalance. How common are such=
 deployments,<br>
&gt; &gt; &gt; and how much of a problem is such a temporary imbalance (the=
 CC will<br>
&gt; &gt; &gt; adjust quickly). Esp. compared to forcing slow-start after e=
very NAT<br>
&gt; &gt; &gt; rebind.<br>
&gt; &gt; <br>
&gt; &gt; Gorry, Lars, where can we find data on the NAT behavior and the r=
elation<br>
&gt; &gt; between NAT rebinding and routing paths? In home routers, NAT reb=
inding<br>
&gt; &gt; typically only change if the session is quiet for some time. Do w=
e observe a<br>
&gt; &gt; different behavior with CGNAT? <br>
&gt; &gt; -- Christian Huitema<br>
-- <br>
Cheers<br>
<br>
Magnus Westerlund <br>
<br>
<br>
----------------------------------------------------------------------<br>
Networks, Ericsson Research<br>
----------------------------------------------------------------------<br>
Ericsson AB=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| =
Phone=C2=A0 <a href=3D"tel:+46%2010%20714%2082%2087" value=3D"+46107148287"=
 target=3D"_blank">+46 10 7148287</a><br>
Torshamnsgatan 23=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0| Mobile <a href=
=3D"tel:+46%2073%20094%2090%2079" value=3D"+46730949079" target=3D"_blank">=
+46 73 0949079</a><br>
SE-164 80 Stockholm, Sweden | mailto: <a href=3D"mailto:magnus.westerlund@e=
ricsson.com" target=3D"_blank">magnus.westerlund@ericsson.com</a><br>
----------------------------------------------------------------------<br>
<br>
<br>
</blockquote></div>

--0000000000006d662805ab33c35d--


From nobody Fri Jul 24 18:42:47 2020
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 309E73A07E7 for <quic@ietfa.amsl.com>; Fri, 24 Jul 2020 18:42:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 QkQ22WDb2pEa for <quic@ietfa.amsl.com>; Fri, 24 Jul 2020 18:42:43 -0700 (PDT)
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 2385E3A07E6 for <quic@ietf.org>; Fri, 24 Jul 2020 18:42:43 -0700 (PDT)
Received: by mail-lj1-x233.google.com with SMTP id x9so11773337ljc.5 for <quic@ietf.org>; Fri, 24 Jul 2020 18:42:43 -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=9Pidj/jB+i149SaBOzAMF7XfKZ6UL7ZVFEIjXjzOwGU=; b=qvZl4lxxkWo7RHkEwT8zTR93nl5WzS0CC6N2H+OYtYMoRNJjD78ld22+vHEQfeE1q6 vlCn/yZhuBWgfuzEC0FBPF8tCNUmMIdoCLd96UUejtOZQkb98nEVzkno9EMjjTDyrpch 6NBw7AbTWv+FqP/ZN7uKHsG872F3ZyHf2PA2eu+WsFDBE0zN6FQ2yomL/c26R97V7qZu ptb/ak8vCT6EnmD6JB6zxMa+XqvFuKuAhvlAzmfD1aspCuHFt8nzzV402vguVwrJdOvr AJP5s37vOCnwpSYiZQ1nKte/wEAYIhx/oLxiO2Ey/9J8BsCGZOmNCEad0RHEvKVEyrQq 9v4Q==
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=9Pidj/jB+i149SaBOzAMF7XfKZ6UL7ZVFEIjXjzOwGU=; b=OhouGDnSKJGYJ6ecpZV/R6lcs9y3PJqT0eql8DEggY6FfaIOaZO0yObA1CB6tBESOa 27AJE5Gw6ifYSJAfOtSKSXEBJY5o6/8OBMP2CU+Cbf90AeRxL6VkPeukEehS/DwKlkHL /w4xX+WUgNWFHe2HbHnLYmwnJAXvIk+kD6749dxMKYVNn5iQhNoBBhHeZgJa35q2Yui4 TU0HwO6Qbo4MItzRB1kF4OCc3KVct9Qn6CQZztu7MnUysElYa7QZlHinm+zmfRuHJ2Eg j3qmZ34UiPNAq1df0jX2KfozGxcv2ghElLyiapXT8sZ81TF0/rXfpDoWfM+DMD+74Z8h HRDw==
X-Gm-Message-State: AOAM530UivXSMdupPi9ZZi+kQ68WmKOidcPbRTQKI7DShufxm2jL4Za6 /WVCOUclfpyqVpXI5AqZhtBO73ZP8vdRIYcOQ+8=
X-Google-Smtp-Source: ABdhPJzEXc50DSnkdeLpguP/L4UtrrRV4wjMSLqt5Tx858EXGK4Sbmg6DOCrRTY7Cby8RWcqrOEwaUyGaYNsGWBSVuE=
X-Received: by 2002:a2e:8783:: with SMTP id n3mr5021081lji.317.1595641361180;  Fri, 24 Jul 2020 18:42:41 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <9f57b20d-2eba-b2b9-d8c8-48e019c8952a@wizmail.org> <CACpbDccrpHeP5PYGCZky+AN2gC9YSs5gbAzYr4Yrw1LpvHZNiA@mail.gmail.com> <CH2PR00MB07269A73542DBC8E51E95519B67A0@CH2PR00MB0726.namprd00.prod.outlook.com> <CAKcm_gMhRX3NxiW6Primy+UrY44ZahaSO+9kF5CeeN4=XqL2JQ@mail.gmail.com> <CAKKJt-fY92k5ym767GofK+DOMQs=x6dpkwkKOA1cpkUf8Xs+3A@mail.gmail.com> <CAKcm_gPyg4QM+mZq_-E-av=u_X4nCWwdDXEH6e9Sjz1d8scEyg@mail.gmail.com> <CAKKJt-fmqjXJEUHzFT0yBXE0sLvOPcnM-oCBDZfgZQNgerRt8g@mail.gmail.com> <114a0e70-fe91-9cf9-e4e8-5f7d074eac5c@erg.abdn.ac.uk>
In-Reply-To: <114a0e70-fe91-9cf9-e4e8-5f7d074eac5c@erg.abdn.ac.uk>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Fri, 24 Jul 2020 18:42:30 -0700
Message-ID: <CACpbDcdXVN4BU5Zs823GYXteXmZEEYaVv1Adv7FGdEgMqJTsOg@mail.gmail.com>
Subject: Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Ian Swett <ianswett@google.com>,  Praveen Balasubramanian <pravb@microsoft.com>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000085b0dc05ab3a3446"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/Z9uvP7VZusJk6iqDoOQJF-rAPpM>
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, 25 Jul 2020 01:42:46 -0000

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

Gorry,

That's not the only case where you don't want to pace. If I know (and I
have a production network where this is true) that the network can absorb a
larger burst. What is the argument to make this a MUST when even the value
of the Initial Window (of 10) is a SHOULD?

- jana

On Thu, Jul 23, 2020 at 2:07 AM Gorry Fairhurst <gorry@erg.abdn.ac.uk>
wrote:

> I'd like to argue a little more for something like the current text we
> arrived at:
>
> "Implementations MUST either
>    use pacing or another method to limit such bursts to the initial
>    congestion window;"
>
> I've been watching, and have comments see below:
>
>
> On 20/07/2020 23:11, Spencer Dawkins at IETF wrote:
>
> Hi, Ian,
>
> On Mon, Jul 20, 2020, 16:33 Ian Swett <ianswett@google.com> wrote:
>
>> Most of the items which I felt were somewhat deployment-specific
>> constants(ie: Initial Window and Initial RTT) are 'RECOMMENDED' in the
>> current recovery draft, so I thought it'd be preferable to keep that
>> convention.
>>
>
> Thanks for helping me understand - this is a stylistic change.
>
> I've had a couple of conversations outside of QUIC recently with people
> who were interpreting the two terms somewhat differently, so thought it a
> good time to ask.
>
> Best,
>
> Spencer
>
>>
>> On Mon, Jul 20, 2020 at 5:30 PM Spencer Dawkins at IETF <
>> spencerdawkins.ietf@gmail.com> wrote:
>>
>>> Hi, Ian,
>>>
>>> On Mon, Jul 20, 2020 at 11:49 AM Ian Swett <ianswett=3D
>>> 40google.com@dmarc.ietf.org> wrote:
>>>
>>>> I think it's ok to include burst limits in the set of things we expect
>>>> may be different in DCs, but if we do that, I'd prefer to use the
>>>> RECOMMENDED rather than SHOULD,
>>>>
>>>
>>> Aren't RECOMMENDED and SHOULD equivalent in
>>> https://tools.ietf.org/html/rfc2119?
>>>
>>> Or am I misunderstanding your point?
>>>
>>> 3 <https://tools.ietf.org/html/rfc2119#section-3>. SHOULD   This word, =
or the adjective "RECOMMENDED", mean that there
>>>    may exist valid reasons in particular circumstances to ignore a
>>>    particular item, but the full implications must be understood and
>>>    carefully weighed before choosing a different course.
>>>
>>>
>>> Best,
>>>
>>> Spencer
>>>
>>> since there are a number of SHOULDs which I believe apply both to the
>>>> public internet and to DCs.  Then we could add a note at the top about=
 how
>>>> there are some values which are RECOMMENDED, including X, Y and Z, and
>>>> those recommendations are expected to be good choices for most, but no=
t all
>>>> environments.
>>>>
>>>> In terms of text, I'd suggest taking Neal's suggestion and dropping an
>>>> explicit mention of the public internet:
>>>>
>>>> Implementations MUST either use pacing or another method to limit such=
 bursts.
>>>>
>>>> It is RECOMMENDED that implementations limit bursts to the initial con=
gestion window; see Section 7.2 <https://nam06.safelinks.protection.outlook=
.com/?url=3Dhttps%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-quic-recovery-=
29%23section-7.2&data=3D02%7C01%7Cpravb%40microsoft.com%7C9df3e5f4f0ca4e586=
f0908d824e0a3ad%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C63729989452665=
7906&sdata=3Dze%2F7SpKUbrdgwI6m%2BS6uEGSBgc2NapVtPn9vkOYFjVs%3D&reserved=3D=
0>.
>>>>
>>>>
>>>> On Sun, Jul 19, 2020 at 4:08 PM Praveen Balasubramanian <pravb=3D
>>>> 40microsoft.com@dmarc.ietf.org> wrote:
>>>>
>>>>> >> There's a way of satisfying both desires: have the NIC handle the
>>>>> pacing.
>>>>>
>>>>> Yes letting the NIC handle pacing will make improve CPU efficiency an=
d
>>>>> improve accuracy due to fine grained hardware timers. But that=E2=80=
=99s in the
>>>>> future. Today=E2=80=99s NICs don=E2=80=99t pace large send offloads f=
or TCP or UDP.
>>>>>
>>>>>
>>>>>
>>>>> >> Perhaps we can have a principle here: recommendations that are
>>>>> specific for Internet use are just that, and we use SHOULDs for those=
. IW10
>>>>> makes sense based on this, and I would then also be fine with changin=
g the
>>>>> MUST to a SHOULD. Perhaps we can state this principle upfront.
>>>>>
>>>>> I like the idea of stating that principle up front. SHOULD would be
>>>>> sufficient resolution for the burst size issue.
>>>>>
>>>>>
>>>>>
>>>>> *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of * Jana Iyengar
>>>>> *Sent:* Friday, July 17, 2020 7:18 PM
>>>>> *To:* QUIC WG <quic@ietf.org>
>>>>> *Subject:* [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
>>>>>
>>>>>
>>>>>
>>>>> There's a protocol question and there's a question of endpoint
>>>>> behavior. In terms of the protocol itself, yes, there's no real need =
to
>>>>> distinguish between Internet and DC environments; we've tried to ensu=
re
>>>>> that the protocol can be used broadly. My point was that the constant=
s in
>>>>> the spec were based on what we believe to be true for the public Inte=
rnet,
>>>>> and not for DC environments.
>>>>>
>>>>>
>>>>>
>>>>> That said, perhaps I was a bit too hasty. IW10 and InitialRTT values
>>>>> are the others I was thinking about, but those are recommendations in=
 the
>>>>> spec, not requirements. And as Ian notes, there's no minimum timeout
>>>>> anymore.
>>>>>
>>>>>
>>>>>
>>>>> Perhaps we can have a principle here: recommendations that are
>>>>> specific for Internet use are just that, and we use SHOULDs for those=
.
>>>>>
>>>> I don't agree, see below.
>
> IW10 makes sense based on this, and I would then also be fine with
>>>>> changing the MUST to a SHOULD. Perhaps we can state this principle up=
front.
>>>>>
>>>>>
>>>>>
>>>>> Ian, I share your hesitation that we don't want to make a distinction
>>>>> between private and public networks, but we already allow for
>>>>> implementations to do that with a different IW and Initial RTT. Is it
>>>>> different when talking about burst limits?
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Fri, Jul 17, 2020 at 3:07 PM Jeremy Harris <jgh@wizmail.org> wrote=
:
>>>>>
>>>>> On 08/07/2020 22:29, Praveen Balasubramanian wrote:
>>>>> > Section 7.9
>>>>> > "Implementations MUST either use pacing or another method to limit
>>>>> such bursts to the initial congestion window; see Section 7.2."
>>>>> > This seems to preclude use of segmentation offload of sizes greater
>>>>> than IW.. In datacenters we routinely send bursts that are higher wit=
hout
>>>>> causing loss. The MUST here seems unnecessary. It also conflicts with=
 the
>>>>> RECOMMENDED in an earlier sentence.
>>>>>
>>>>> There's a way of satisfying both desires: have the NIC handle the
>>>>> pacing.
>>>>> --
>>>>> Cheers,
>>>>>   Jeremy
>>>>>
>>>>>
> I am unsure that trying to differentiate DC from ISP-Edge from Enterprise=
 Server
> or anything else will help in the spec. Sure, guidance may differ - but I=
'd like
> to think (???) the IETF Spec describes the "Internet case, which
> is expected to be good choices for most, but not all environments... and =
if a system distributes
> functions within your own network segment then that's your decision - and=
 yes,
> and doing this in NICs would be great ... although NICs also can generate=
 bursts
> when transports pace at a higher level...
>
> The pacing/burst-limiting could happen in various ways by various actors,=
 but
> that's not the way transport Specs are written, I thought that's why we e=
nded-up with
> "other methods".
>
> For me at least, it was a conscious decision to not to explicitly make th=
is "10 packets",
> because an endpoint sender that made an informed decision to use a larger=
 IW
> has at the same time decided to configure in a way that expects the netwo=
rk path can safely
> support this burst size. I expect this matters most when the
> connection sending rate is low (see below). But we missed something.
>
> I think the suggested addition from Ian, could really help a lot:
> "unless the pacing system can't provide enough sending opportunities to s=
end at the rate specified by the congestion controller."
>
> - This would make the language less clear, but I think in a very good way=
, because I agree that as the connection **sending** rate increases (and he=
nce also the CC understanding of
> the path characteristics), the effect of bursts might be expected to be l=
ess significant. At higher rates queues in devices clear more quickly, and =
buffering 1mS (or whatever) of data, buffers more.
>
> Can we discuss that proposal more?
>
> Gorry
>
>

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

<div dir=3D"ltr">Gorry,<div><br></div><div>That&#39;s not the only case whe=
re you don&#39;t want to pace. If I know (and I have a production network w=
here this is true) that the network can absorb a larger burst. What is the =
argument to make this a MUST when even the value of the Initial Window (of =
10) is a SHOULD?</div><div><br></div><div>- jana</div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jul 23, 2020=
 at 2:07 AM Gorry Fairhurst &lt;<a href=3D"mailto:gorry@erg.abdn.ac.uk">gor=
ry@erg.abdn.ac.uk</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">
 =20
   =20
 =20
  <div>
    <p>I&#39;d like to argue a little more for something like the current
      text we arrived at:</p>
    <pre>&quot;Implementations MUST either
   use pacing or another method to limit such bursts to the initial
   congestion window;&quot;

I&#39;ve been watching, and have comments see below:

</pre>
    <div>On 20/07/2020 23:11, Spencer Dawkins at
      IETF wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"auto">
        <div>Hi, Ian,<br>
          <br>
          <div class=3D"gmail_quote">
            <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jul 20, 2020,
              16:33 Ian Swett &lt;<a href=3D"mailto:ianswett@google.com" ta=
rget=3D"_blank">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 dir=3D"ltr">Most of the items which I felt were
                somewhat deployment-specific constants(ie: Initial
                Window and Initial RTT) are &#39;RECOMMENDED&#39; in the cu=
rrent
                recovery draft, so I thought it&#39;d be preferable to keep
                that convention.</div>
            </blockquote>
          </div>
        </div>
        <div dir=3D"auto"><br>
        </div>
        <div dir=3D"auto">Thanks for helping me understand - this is a
          stylistic change.</div>
        <div dir=3D"auto"><br>
        </div>
        <div dir=3D"auto">I&#39;ve had a couple of conversations outside of
          QUIC recently with people who were interpreting the two terms
          somewhat differently, so thought it a good time to ask.</div>
        <div dir=3D"auto"><br>
        </div>
        <div dir=3D"auto">Best,</div>
        <div dir=3D"auto"><br>
        </div>
        <div dir=3D"auto">Spencer</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:1px solid rgb(204,204,204);padding-left:1ex"><br>
              <div class=3D"gmail_quote">
                <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jul 20, 2020
                  at 5:30 PM Spencer Dawkins at IETF &lt;<a href=3D"mailto:=
spencerdawkins.ietf@gmail.com" rel=3D"noreferrer" target=3D"_blank">spencer=
dawkins.ietf@gmail.com</a>&gt;
                  wrote:<br>
                </div>
                <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
                  <div dir=3D"ltr">
                    <div dir=3D"ltr">Hi, Ian,=C2=A0</div>
                    <br>
                    <div class=3D"gmail_quote">
                      <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jul 20,
                        2020 at 11:49 AM Ian Swett &lt;ianswett=3D<a href=
=3D"mailto:40google.com@dmarc.ietf.org" rel=3D"noreferrer" target=3D"_blank=
">40google.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">
                        <div dir=3D"ltr">I think it&#39;s ok to include bur=
st
                          limits in the set of things we expect may be
                          different in DCs, but if we do that, I&#39;d
                          prefer to use the RECOMMENDED rather than
                          SHOULD,</div>
                      </blockquote>
                      <div><br>
                      </div>
                      <div>Aren&#39;t RECOMMENDED and SHOULD equivalent in=
=C2=A0
                        <a href=3D"https://tools.ietf.org/html/rfc2119" rel=
=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/rfc2119</a>?=
=C2=A0</div>
                      <div><br>
                      </div>
                      <div>Or am I misunderstanding your point?</div>
                      <div><br>
                      </div>
                      <div>
                        <pre style=3D"margin-top:0px;margin-bottom:0px;colo=
r:rgb(0,0,0)"><font size=3D"4"><span style=3D"display:inline;font-weight:bo=
ld"><h2 style=3D"display:inline"><a name=3D"m_6172066709575264695_m_-710440=
7681243286268_m_-561907519085294557_section-3" href=3D"https://tools.ietf.o=
rg/html/rfc2119#section-3" style=3D"color:black;text-decoration-line:none" =
rel=3D"noreferrer" target=3D"_blank">3</a>. SHOULD  </h2></span> This word,=
 or the adjective &quot;RECOMMENDED&quot;, mean that there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.</font></pre>
                      </div>
                      <div>=C2=A0</div>
                      <div>Best,</div>
                      <div><br>
                      </div>
                      <div>Spencer</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"> since there are a number of
                          SHOULDs which I believe=C2=A0apply both to the
                          public internet and to DCs.=C2=A0 Then we could a=
dd
                          a note at the top about how there are some
                          values which are RECOMMENDED, including X, Y
                          and Z, and those recommendations are expected
                          to be good choices for most, but not all
                          environments.
                          <div><br>
                          </div>
                          <div>In terms of text, I&#39;d suggest taking
                            Neal&#39;s suggestion and dropping an explicit
                            mention of the public internet:</div>
                          <div><br>
                          </div>
                          <div>
                            <pre style=3D"white-space:pre-wrap;margin:0in;f=
ont-size:10pt;font-family:&quot;Courier New&quot;;break-before:page"><span =
style=3D"color:black">Implementations MUST either use pacing or another met=
hod to limit such bursts.</span></pre>
                            <pre style=3D"white-space:pre-wrap;margin:0in;f=
ont-size:10pt;font-family:&quot;Courier New&quot;;break-before:page"><span =
style=3D"color:black">It is RECOMMENDED that implementations limit bursts t=
o the initial </span>congestion window; see <a href=3D"https://nam06.safeli=
nks.protection.outlook.com/?url=3Dhttps%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdra=
ft-ietf-quic-recovery-29%23section-7.2&amp;data=3D02%7C01%7Cpravb%40microso=
ft.com%7C9df3e5f4f0ca4e586f0908d824e0a3ad%7C72f988bf86f141af91ab2d7cd011db4=
7%7C1%7C0%7C637299894526657906&amp;sdata=3Dze%2F7SpKUbrdgwI6m%2BS6uEGSBgc2N=
apVtPn9vkOYFjVs%3D&amp;reserved=3D0" style=3D"font-size:10pt" rel=3D"norefe=
rrer" target=3D"_blank">Section 7.2</a><span style=3D"font-size:10pt;color:=
black">.</span></pre>
                          </div>
                        </div>
                        <br>
                        <div class=3D"gmail_quote">
                          <div dir=3D"ltr" class=3D"gmail_attr">On Sun, Jul
                            19, 2020 at 4:08 PM Praveen Balasubramanian
                            &lt;pravb=3D<a href=3D"mailto:40microsoft.com@d=
marc.ietf.org" rel=3D"noreferrer" target=3D"_blank">40microsoft.com@dmarc.i=
etf.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"=
>
                            <div lang=3D"EN-US">
                              <div>
                                <p class=3D"MsoNormal">&gt;&gt; There&#39;s=
 a
                                  way of satisfying both desires: have
                                  the NIC handle the pacing.</p>
                                <p class=3D"MsoNormal">Yes letting the NIC
                                  handle pacing will make improve CPU
                                  efficiency and improve accuracy due to
                                  fine grained hardware timers. But
                                  that=E2=80=99s in the future. Today=E2=80=
=99s NICs
                                  don=E2=80=99t pace large send offloads fo=
r TCP
                                  or UDP.</p>
                                <p class=3D"MsoNormal">=C2=A0</p>
                                <p class=3D"MsoNormal">&gt;&gt; Perhaps we
                                  can have a principle here:
                                  recommendations that are specific for
                                  Internet use are just that, and we use
                                  SHOULDs for those. IW10 makes sense
                                  based on this, and I would then also
                                  be fine with changing the MUST to a
                                  SHOULD. Perhaps we can state this
                                  principle upfront.</p>
                                <p class=3D"MsoNormal">I like the idea of
                                  stating that principle up front.
                                  SHOULD would be sufficient resolution
                                  for the burst size issue.
                                </p>
                                <p class=3D"MsoNormal">=C2=A0</p>
                                <div style=3D"border-right:none;border-bott=
om:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt =
0in 0in">
                                  <p class=3D"MsoNormal"><b>From:</b> QUIC
                                    &lt;<a href=3D"mailto:quic-bounces@ietf=
.org" rel=3D"noreferrer" target=3D"_blank">quic-bounces@ietf.org</a>&gt;
                                    <b>On Behalf Of </b>
                                    Jana Iyengar<br>
                                    <b>Sent:</b> Friday, July 17, 2020
                                    7:18 PM<br>
                                    <b>To:</b> QUIC WG &lt;<a href=3D"mailt=
o:quic@ietf.org" rel=3D"noreferrer" target=3D"_blank">quic@ietf.org</a>&gt;=
<br>
                                    <b>Subject:</b> [EXTERNAL] Re: WGLC
                                    review of
                                    draft-ietf-quic-recovery-29</p>
                                </div>
                                <p class=3D"MsoNormal">=C2=A0</p>
                                <div>
                                  <p class=3D"MsoNormal">There&#39;s a
                                    protocol question and there&#39;s a
                                    question of endpoint behavior. In
                                    terms of the protocol itself, yes,
                                    there&#39;s no real need to distinguish
                                    between Internet and DC
                                    environments; we&#39;ve tried to ensure
                                    that the protocol can be used
                                    broadly. My point was that the
                                    constants=C2=A0in the spec were based o=
n
                                    what we believe to be true for the
                                    public Internet, and not for DC
                                    environments.</p>
                                  <div>
                                    <p class=3D"MsoNormal">=C2=A0</p>
                                  </div>
                                  <div>
                                    <p class=3D"MsoNormal">That said,
                                      perhaps I was a bit too hasty.
                                      IW10 and InitialRTT values are the
                                      others I was thinking about, but
                                      those are=C2=A0recommendations in the
                                      spec, not requirements. And as Ian
                                      notes, there&#39;s no minimum timeout
                                      anymore.</p>
                                  </div>
                                  <div>
                                    <p class=3D"MsoNormal">=C2=A0</p>
                                  </div>
                                  <div>
                                    <p class=3D"MsoNormal">Perhaps we can
                                      have a principle here:
                                      recommendations that are specific
                                      for Internet use are just that,
                                      and we use SHOULDs for those. </p>
                                  </div>
                                </div>
                              </div>
                            </div>
                          </blockquote>
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </blockquote>
              </div>
            </blockquote>
          </div>
        </div>
      </div>
    </blockquote>
    I don&#39;t agree, see below.<br>
    <blockquote type=3D"cite">
      <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:1px solid rgb(204,204,204);padding-left:1ex">
              <div class=3D"gmail_quote">
                <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
                  <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 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 lang=3D"EN-US">
                              <div>
                                <div>
                                  <div>
                                    <p class=3D"MsoNormal">IW10 makes
                                      sense based on this, and I would
                                      then also be fine with changing
                                      the MUST to a SHOULD. Perhaps we
                                      can state this principle upfront.</p>
                                  </div>
                                  <div>
                                    <p class=3D"MsoNormal">=C2=A0</p>
                                  </div>
                                  <div>
                                    <p class=3D"MsoNormal">Ian, I share
                                      your hesitation that we don&#39;t wan=
t
                                      to make a distinction between
                                      private and public networks,=C2=A0but
                                      we already allow for
                                      implementations to do that with a
                                      different=C2=A0IW and Initial RTT. Is
                                      it different when talking about
                                      burst limits?</p>
                                  </div>
                                  <div>
                                    <p class=3D"MsoNormal">=C2=A0</p>
                                  </div>
                                </div>
                                <p class=3D"MsoNormal">=C2=A0</p>
                                <div>
                                  <div>
                                    <p class=3D"MsoNormal">On Fri, Jul 17,
                                      2020 at 3:07 PM Jeremy Harris &lt;<a =
href=3D"mailto:jgh@wizmail.org" rel=3D"noreferrer" target=3D"_blank">jgh@wi=
zmail.org</a>&gt;
                                      wrote:</p>
                                  </div>
                                  <blockquote>
                                    <p class=3D"MsoNormal" style=3D"margin-=
bottom:12pt">On
                                      08/07/2020 22:29, Praveen
                                      Balasubramanian wrote:<br>
                                      &gt; Section 7.9<br>
                                      &gt; &quot;Implementations MUST eithe=
r
                                      use pacing or another method to
                                      limit such bursts to the initial
                                      congestion window; see Section
                                      7.2.&quot;<br>
                                      &gt; This seems to preclude use of
                                      segmentation offload of sizes
                                      greater than IW.. In datacenters
                                      we routinely send bursts that are
                                      higher without causing loss. The
                                      MUST here seems unnecessary. It
                                      also conflicts with the
                                      RECOMMENDED in an earlier
                                      sentence.<br>
                                      <br>
                                      There&#39;s a way of satisfying both
                                      desires: have the NIC handle the<br>
                                      pacing.<br>
                                      -- <br>
                                      Cheers,<br>
                                      =C2=A0 Jeremy</p>
                                  </blockquote>
                                </div>
                              </div>
                            </div>
                          </blockquote>
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </blockquote>
              </div>
            </blockquote>
          </div>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <pre>I am unsure that trying to differentiate DC from ISP-Edge from Ent=
erprise Server
or anything else will help in the spec. Sure, guidance may differ - but I&#=
39;d like
to think (???) the IETF Spec describes the &quot;Internet case, which
is expected to be good choices for most, but not all environments... and if=
 a system distributes
functions within your own network segment then that&#39;s your decision - a=
nd yes,
and doing this in NICs would be great ... although NICs also can generate b=
ursts=20
when transports pace at a higher level...=20

The pacing/burst-limiting could happen in various ways by various actors, b=
ut
that&#39;s not the way transport Specs are written, I thought that&#39;s wh=
y we ended-up with=20
&quot;other methods&quot;.

For me at least, it was a conscious decision to not to explicitly make this=
 &quot;10 packets&quot;,=20
because an endpoint sender that made an informed decision to use a larger I=
W=20
has at the same time decided to configure in a way that expects the network=
 path can safely=20
support this burst size. I expect this matters most when the
connection sending rate is low (see below). But we missed something.

I think the suggested addition from Ian, could really help a lot:
&quot;unless the pacing system can&#39;t provide enough sending opportuniti=
es to send at the rate specified by the congestion controller.&quot;

- This would make the language less clear, but I think in a very good way, =
because I agree that as the connection **sending** rate increases (and henc=
e also the CC understanding of
the path characteristics), the effect of bursts might be expected to be les=
s significant. At higher rates queues in devices clear more quickly, and bu=
ffering 1mS (or whatever) of data, buffers more.=20

Can we discuss that proposal more?

Gorry
</pre>
  </div>

</blockquote></div>

--00000000000085b0dc05ab3a3446--


From nobody Sun Jul 26 00:32:25 2020
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 16D4F3A0BF6 for <quic@ietfa.amsl.com>; Sun, 26 Jul 2020 00:32:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.119
X-Spam-Level: 
X-Spam-Status: No, score=-2.119 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=RoR0PRpx; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=AGm/C0oE
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id yBF7wqAicpHd for <quic@ietfa.amsl.com>; Sun, 26 Jul 2020 00:32:20 -0700 (PDT)
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 2E5EA3A0BF4 for <quic@ietf.org>; Sun, 26 Jul 2020 00:32:20 -0700 (PDT)
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.west.internal (Postfix) with ESMTP id 4D7E3C1F for <quic@ietf.org>; Sun, 26 Jul 2020 03:32:19 -0400 (EDT)
Received: from mailfrontend2 ([10.202.2.163]) by compute1.internal (MEProxy); Sun, 26 Jul 2020 03:32:19 -0400
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= fm3; bh=SofxTpvjjsYagoA2lurn7sbg0TA6EwOqxOZ4Mjsjn9Q=; b=RoR0PRpx xkCmFjyndU/Nre8pM/lWuNylYbziK+JikQYiMp8hl6gLpk7JPyeEGrMBCw25mkjv pdJfMugTdHH/kQiLEEY1fe+UTOIOtqTkknOrwAb38JS7xHOHFgV+PekUm/4mDRvJ PF+Z6JhmiwFdW64lFX0zrySHZgV5HPxAqv1qGJBFxFJYxR/37Qf/0d/7kIpe3cPE tGtHB8KRGcOmdIIJDusTX9/HoCuZE+A36SE9VzJhdT/5o28lrvtK5x/qqa0SBaFi 9rZUSkiwdTPIqNf/ynjxaH6UOpL+3b/n2lbtL54eh5YFAFKHAdm/u9JDKGZ02K7B usysqKmOx9PTZw==
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=fm3; bh=SofxTpvjjsYagoA2lurn7sbg0TA6E wOqxOZ4Mjsjn9Q=; b=AGm/C0oELMup8xy29iozI2ASV50XDm0BTpfg3F2LY77s/ 3MruzNGm36enn1z+AYJrIcdunowgy6lH90jvnVo9XmNRdWodpt1ozkq15U+Dmrhd ConMYawZJYDRV19sjCLnfn9l1zAUqkFih/sIvjfJ9m2T4jZFdyvnsIrzOrCp1jOY WQ3ngQJJv6B/cXTttSE/9wzVbJEIKs5AXFr3uv3bczoTZNcGieAG1jSyS/aTmaGt cw03uHJQbdYbqRopX9i5B+RiGskGtjIwtSfa5ogkVHemOFq0QjtnwP5DfrbIvS4W xotrlfxkD3XHV/myvOTj9pgSoNmuED/l3H8LIthDw==
X-ME-Sender: <xms:gjEdXzrUuq89B_1rMllDoUJMBV2GyxkzekIwkyuTZurkonzhC-VOAg>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgeduiedrheeigdduudehucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpegtggfhvffusegrtddtredttdejne cuhfhrohhmpeftvghpohhsihhtohhrhicutegtthhivhhithihucfuuhhmmhgrrhihuceu ohhtuceoughopghnohhtpghrvghplhihsehmnhhothdrnhgvtheqnecuggftrfgrthhtvg hrnhepkeefvdduteejvdefkeehieevuefgfefhteetveegffekffefteffvdelheduieet necuffhomhgrihhnpehgihhthhhusgdrtghomhenucfkphephedvrddujeehrddvudeird dvudeknecuvehluhhsthgvrhfuihiivgepudenucfrrghrrghmpehmrghilhhfrhhomhep ughopghnohhtpghrvghplhihsehmnhhothdrnhgvth
X-ME-Proxy: <xmx:gjEdX9qUpubNz_4-hfJ6dpPs0Khr-m4322yeUrmKmGL1DYtapbRHKA> <xmx:gjEdXwOVARtNCenNmO-fFIYPKR00eBxEALVlCe5OBO2TLmEoiaYKGA> <xmx:gjEdX26QNCmmkFerK0xBxpzaRmhBm1Rw0DO2cuq-WAfR3Nw50zp3ng> <xmx:gjEdX3gvfQUhjOAfk3drLoaL04VgxnSG3pnVm4HJBdHSll-B6R6bsw>
Received: from fv-az134.internal.cloudapp.net (unknown [52.175.216.218]) by mail.messagingengine.com (Postfix) with ESMTPA id 6460A30600A6 for <quic@ietf.org>; Sun, 26 Jul 2020 03:32:18 -0400 (EDT)
Content-Type: multipart/alternative; boundary="===============3166579684992273856=="
MIME-Version: 1.0
From: Repository Activity Summary Bot <do_not_reply@mnot.net>
To: quic@ietf.org
Subject: Weekly github digest (QUIC Activity Summary)
Message-Id: <20200726073218.6460A30600A6@mailuser.nyi.internal>
Date: Sun, 26 Jul 2020 03:32:18 -0400 (EDT)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/eI03F5aQGWzXcxxsGmwQ-ySRaq0>
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, 26 Jul 2020 07:32:23 -0000

--===============3166579684992273856==
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 (+7/-1/=F0=9F=92=AC51)
  7 issues created:
  - Suggest endpoints may recognize acks after loss is declared (by kazuho)
    https://github.com/quicwg/base-drafts/issues/3956=20
  - HTTP/2 Settings reservation isn't called out (by MikeBishop)
    https://github.com/quicwg/base-drafts/issues/3954 [-http]=20
  - Including ACK delay in packet loss detection time threshold (by djc)
    https://github.com/quicwg/base-drafts/issues/3951=20
  - Reno does not require window reduction on loss (by janaiyengar)
    https://github.com/quicwg/base-drafts/issues/3944=20
  - Congestion window reduction should be based on size of inflight (by jan=
aiyengar)
    https://github.com/quicwg/base-drafts/issues/3943 [-recovery]=20
  - Starting persistent congestion on a ack-eliciting packet (by martinthom=
son)
    https://github.com/quicwg/base-drafts/issues/3941=20
  - It's unclear if persistent congestion is a per-PN-space property (by ka=
zuho)
    https://github.com/quicwg/base-drafts/issues/3939=20

  13 issues received 51 new comments:
  - #3956 Suggest endpoints may recognize acks after loss is declared (4 by=
 ianswett, janaiyengar, martinthomson)
    https://github.com/quicwg/base-drafts/issues/3956 [-recovery] [post-wgl=
c]=20
  - #3954 HTTP/2 Settings reservation isn't called out (2 by LPardue, MikeB=
ishop)
    https://github.com/quicwg/base-drafts/issues/3954 [-http] [post-wglc]=20
  - #3951 Including ACK delay in packet loss detection time threshold (4 by=
 Ralith, ianswett, janaiyengar, martinthomson)
    https://github.com/quicwg/base-drafts/issues/3951 [post-wglc]=20
  - #3944 Reno does not require window reduction on loss (1 by ianswett)
    https://github.com/quicwg/base-drafts/issues/3944 [-recovery] [design] =
[post-wglc]=20
  - #3943 Congestion window reduction should be based on size of inflight (=
9 by ianswett, janaiyengar, junhochoi, kazuho)
    https://github.com/quicwg/base-drafts/issues/3943 [-recovery] [post-wgl=
c]=20
  - #3941 Starting persistent congestion on a ack-eliciting packet (4 by ja=
naiyengar, kazuho, marten-seemann, martinthomson)
    https://github.com/quicwg/base-drafts/issues/3941 [-recovery] [post-wgl=
c]=20
  - #3939 It's unclear if persistent congestion is a per-PN-space property =
(7 by janaiyengar, kazuho, marten-seemann)
    https://github.com/quicwg/base-drafts/issues/3939 [-recovery]=20
  - #3937 unclear definition of persistent congestion (3 by goelvidhi, kazu=
ho, larseggert)
    https://github.com/quicwg/base-drafts/issues/3937 [-recovery]=20
  - #3932 Servers are not expected to validate multiple paths simultaneousl=
y (4 by ekinnear, ianswett, kazuho)
    https://github.com/quicwg/base-drafts/issues/3932 [-transport] [post-wg=
lc]=20
  - #3927 Reset min_rtt on persistent congestion (5 by kazuho, marten-seema=
nn, martinthomson)
    https://github.com/quicwg/base-drafts/issues/3927 [-recovery]=20
  - #3892 MUST requirement on bursts smaller than IW is too restrictive (2 =
by ianswett, larseggert)
    https://github.com/quicwg/base-drafts/issues/3892 [-recovery] [post-wgl=
c]=20
  - #3842 Do I need to reset congestion info when the port changes? (2 by l=
arseggert)
    https://github.com/quicwg/base-drafts/issues/3842 [-transport] [design]=
 [proposal-ready]=20
  - #3834 Remove amplification throttle if the server receives Initial that=
 echoes its high entropy SCID. (4 by martinthomson, mikkelfj)
    https://github.com/quicwg/base-drafts/issues/3834 [-transport] [design]=
 [proposal-ready]=20

  1 issues closed:
  - Congestion window reduction should be based on size of inflight https:/=
/github.com/quicwg/base-drafts/issues/3943 [-recovery] [post-wglc]=20

* quicwg/load-balancers (+1/-1/=F0=9F=92=AC0)
  1 issues created:
  - A little confused about configuration agent (by william-zk)
    https://github.com/quicwg/load-balancers/issues/46=20

  1 issues closed:
  - Simplify the configuration by merging server-id and zero-pad https://gi=
thub.com/quicwg/load-balancers/issues/41=20



Pull requests
-------------
* quicwg/base-drafts (+12/-0/=F0=9F=92=AC5)
  12 pull requests submitted:
  - fix typo: s/an proxy/a proxy/ (by bencebeky)
    https://github.com/quicwg/base-drafts/pull/3958=20
  - Don't retransmit lost packets that are acked later (by janaiyengar)
    https://github.com/quicwg/base-drafts/pull/3957=20
  - Clarify HTTP/2 setting parameter reservation (by MikeBishop)
    https://github.com/quicwg/base-drafts/pull/3955 [-http] [design]=20
  - Application can reset stream or close connection even if no error occur=
s. (by bencebeky)
    https://github.com/quicwg/base-drafts/pull/3953=20
  - Move transport error codes to a separate subsection. (by bencebeky)
    https://github.com/quicwg/base-drafts/pull/3952=20
  - Fix spelling and style consistency nits (by larseggert)
    https://github.com/quicwg/base-drafts/pull/3950=20
  - Fix spelling and style consistency nits (by larseggert)
    https://github.com/quicwg/base-drafts/pull/3949=20
  - Fix spelling and style consistency nits (by larseggert)
    https://github.com/quicwg/base-drafts/pull/3948=20
  - Fix spelling and style consistency nits (by larseggert)
    https://github.com/quicwg/base-drafts/pull/3947=20
  - Fix spelling and style consistency nits (by larseggert)
    https://github.com/quicwg/base-drafts/pull/3946=20
  - Word-smithed version of Ted's resolution to #3842 from the mailing list=
 (by larseggert)
    https://github.com/quicwg/base-drafts/pull/3945=20
  - clarify that persistent congestion is a contigous loss across all PN sp=
aces (by kazuho)
    https://github.com/quicwg/base-drafts/pull/3940=20

  4 pull requests received 5 new comments:
  - #3945 Word-smithed version of Ted's resolution to #3842 from the mailin=
g list (1 by ekr)
    https://github.com/quicwg/base-drafts/pull/3945=20
  - #3940 clarify that persistent congestion is a contigous loss across all=
 PN spaces (1 by kazuho)
    https://github.com/quicwg/base-drafts/pull/3940=20
  - #3936 sender SHOULD limit bursts (1 by janaiyengar)
    https://github.com/quicwg/base-drafts/pull/3936 [-recovery] [design]=20
  - #3889 No RTT samples, no persistent congestion (2 by janaiyengar, mjora=
s)
    https://github.com/quicwg/base-drafts/pull/3889 [-recovery] [design]=20

* quicwg/ops-drafts (+0/-0/=F0=9F=92=AC1)
  1 pull requests received 1 new comments:
  - #104 retry service and validation token (1 by mirjak)
    https://github.com/quicwg/ops-drafts/pull/104=20

* quicwg/load-balancers (+0/-1/=F0=9F=92=AC0)
  1 pull requests merged:
  - Remove zero padding field
    https://github.com/quicwg/load-balancers/pull/44=20


Repositories tracked by this digest:
-----------------------------------
* https://github.com/quicwg/base-drafts
* https://github.com/quicwg/ops-drafts
* https://github.com/quicwg/datagram
* https://github.com/quicwg/load-balancers
* https://github.com/quicwg/version-negotiation

--===============3166579684992273856==
Content-Type: text/html; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable

<!doctype html>
<html lang=3D"en">
<head>
<meta charset=3D"utf-8">
<title>Weekly github digest (QUIC 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 July 26, 2020</h1>

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

<h2>Issues</h2>

<h3>quicwg/base-drafts (+7/-1/=F0=9F=92=AC51)</h3>
  <p class=3D"new">7 issues created:</p>
  <ul>
  <li>#3956 <a href=3D"https://github.com/quicwg/base-drafts/issues/3956">S=
uggest endpoints may recognize acks after loss is declared</a> (by kazuho) =
</li>
 =20
  <li>#3954 <a href=3D"https://github.com/quicwg/base-drafts/issues/3954">H=
TTP/2 Settings reservation isn&#x27;t called out</a> (by MikeBishop) <span =
class=3D"label" style=3D"background-color: #fbca04; color: #000000">-http</=
span> </li>
 =20
  <li>#3951 <a href=3D"https://github.com/quicwg/base-drafts/issues/3951">I=
ncluding ACK delay in packet loss detection time threshold</a> (by djc) </l=
i>
 =20
  <li>#3944 <a href=3D"https://github.com/quicwg/base-drafts/issues/3944">R=
eno does not require window reduction on loss</a> (by janaiyengar) </li>
 =20
  <li>#3943 <a href=3D"https://github.com/quicwg/base-drafts/issues/3943">C=
ongestion window reduction should be based on size of inflight</a> (by jana=
iyengar) <span class=3D"label" style=3D"background-color: #fbca04; color: #=
000000">-recovery</span> </li>
 =20
  <li>#3941 <a href=3D"https://github.com/quicwg/base-drafts/issues/3941">S=
tarting persistent congestion on a ack-eliciting packet</a> (by martinthoms=
on) </li>
 =20
  <li>#3939 <a href=3D"https://github.com/quicwg/base-drafts/issues/3939">I=
t&#x27;s unclear if persistent congestion is a per-PN-space property</a> (b=
y kazuho) </li>
  </ul>

  <p>13 issues received 51 new comments:</p>
  <ul>
  <li>#3956 <a href=3D"https://github.com/quicwg/base-drafts/issues/3956">S=
uggest endpoints may recognize acks after loss is declared</a> (4 by ianswe=
tt, janaiyengar, martinthomson) <span class=3D"label" style=3D"background-c=
olor: #fbca04; color: #000000">-recovery</span> <span class=3D"label" style=
=3D"background-color: #d3395a; color: #ffffff">post-wglc</span> </li>
 =20
  <li>#3954 <a href=3D"https://github.com/quicwg/base-drafts/issues/3954">H=
TTP/2 Settings reservation isn&#x27;t called out</a> (2 by LPardue, MikeBis=
hop) <span class=3D"label" style=3D"background-color: #fbca04; color: #0000=
00">-http</span> <span class=3D"label" style=3D"background-color: #d3395a; =
color: #ffffff">post-wglc</span> </li>
 =20
  <li>#3951 <a href=3D"https://github.com/quicwg/base-drafts/issues/3951">I=
ncluding ACK delay in packet loss detection time threshold</a> (4 by Ralith=
, ianswett, janaiyengar, martinthomson) <span class=3D"label" style=3D"back=
ground-color: #d3395a; color: #ffffff">post-wglc</span> </li>
 =20
  <li>#3944 <a href=3D"https://github.com/quicwg/base-drafts/issues/3944">R=
eno does not require window reduction on loss</a> (1 by ianswett) <span cla=
ss=3D"label" style=3D"background-color: #fbca04; color: #000000">-recovery<=
/span> <span class=3D"label" style=3D"background-color: #1d76db; color: #ff=
ffff">design</span> <span class=3D"label" style=3D"background-color: #d3395=
a; color: #ffffff">post-wglc</span> </li>
 =20
  <li>#3943 <a href=3D"https://github.com/quicwg/base-drafts/issues/3943">C=
ongestion window reduction should be based on size of inflight</a> (9 by ia=
nswett, janaiyengar, junhochoi, kazuho) <span class=3D"label" style=3D"back=
ground-color: #fbca04; color: #000000">-recovery</span> <span class=3D"labe=
l" style=3D"background-color: #d3395a; color: #ffffff">post-wglc</span> </l=
i>
 =20
  <li>#3941 <a href=3D"https://github.com/quicwg/base-drafts/issues/3941">S=
tarting persistent congestion on a ack-eliciting packet</a> (4 by janaiyeng=
ar, kazuho, marten-seemann, martinthomson) <span class=3D"label" style=3D"b=
ackground-color: #fbca04; color: #000000">-recovery</span> <span class=3D"l=
abel" style=3D"background-color: #d3395a; color: #ffffff">post-wglc</span> =
</li>
 =20
  <li>#3939 <a href=3D"https://github.com/quicwg/base-drafts/issues/3939">I=
t&#x27;s unclear if persistent congestion is a per-PN-space property</a> (7=
 by janaiyengar, kazuho, marten-seemann) <span class=3D"label" style=3D"bac=
kground-color: #fbca04; color: #000000">-recovery</span> </li>
 =20
  <li>#3937 <a href=3D"https://github.com/quicwg/base-drafts/issues/3937">u=
nclear definition of persistent congestion</a> (3 by goelvidhi, kazuho, lar=
seggert) <span class=3D"label" style=3D"background-color: #fbca04; color: #=
000000">-recovery</span> </li>
 =20
  <li>#3932 <a href=3D"https://github.com/quicwg/base-drafts/issues/3932">S=
ervers are not expected to validate multiple paths simultaneously</a> (4 by=
 ekinnear, ianswett, kazuho) <span class=3D"label" style=3D"background-colo=
r: #fbca04; color: #000000">-transport</span> <span class=3D"label" style=
=3D"background-color: #d3395a; color: #ffffff">post-wglc</span> </li>
 =20
  <li>#3927 <a href=3D"https://github.com/quicwg/base-drafts/issues/3927">R=
eset min_rtt on persistent congestion</a> (5 by kazuho, marten-seemann, mar=
tinthomson) <span class=3D"label" style=3D"background-color: #fbca04; color=
: #000000">-recovery</span> </li>
 =20
  <li>#3892 <a href=3D"https://github.com/quicwg/base-drafts/issues/3892">M=
UST requirement on bursts smaller than IW is too restrictive</a> (2 by ians=
wett, larseggert) <span class=3D"label" style=3D"background-color: #fbca04;=
 color: #000000">-recovery</span> <span class=3D"label" style=3D"background=
-color: #d3395a; color: #ffffff">post-wglc</span> </li>
 =20
  <li>#3842 <a href=3D"https://github.com/quicwg/base-drafts/issues/3842">D=
o I need to reset congestion info when the port changes?</a> (2 by larsegge=
rt) <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> <span class=3D"label" style=3D"background=
-color: #c5def5; color: #000000">proposal-ready</span> </li>
 =20
  <li>#3834 <a href=3D"https://github.com/quicwg/base-drafts/issues/3834">R=
emove amplification throttle if the server receives Initial that echoes its=
 high entropy SCID.</a> (4 by martinthomson, mikkelfj) <span class=3D"label=
" style=3D"background-color: #fbca04; color: #000000">-transport</span> <sp=
an class=3D"label" style=3D"background-color: #1d76db; color: #ffffff">desi=
gn</span> <span class=3D"label" style=3D"background-color: #c5def5; color: =
#000000">proposal-ready</span> </li>
  </ul>

  <p>1 issues closed:</p>
  <ul>
  <li>#3943 <a href=3D"https://github.com/quicwg/base-drafts/issues/3943">C=
ongestion window reduction should be based on size of inflight</a> <span cl=
ass=3D"label" style=3D"background-color: #fbca04; color: #000000">-recovery=
</span> <span class=3D"label" style=3D"background-color: #d3395a; color: #f=
fffff">post-wglc</span> </li>
  </ul>

<h3>quicwg/load-balancers (+1/-1/=F0=9F=92=AC0)</h3>
  <p class=3D"new">1 issues created:</p>
  <ul>
  <li>#46 <a href=3D"https://github.com/quicwg/load-balancers/issues/46">A =
little confused about configuration agent</a> (by william-zk) </li>
  </ul>


  <p>1 issues closed:</p>
  <ul>
  <li>#41 <a href=3D"https://github.com/quicwg/load-balancers/issues/41">Si=
mplify the configuration by merging server-id and zero-pad</a> </li>
  </ul>



<h2>Pull requests</h2>
<h3>quicwg/base-drafts (+12/-0/=F0=9F=92=AC5)</h3>
  <p class=3D"new">12 pull requests submitted:</p>
  <ul>
  <li>#3958 <a href=3D"https://github.com/quicwg/base-drafts/pull/3958">fix=
 typo: s/an proxy/a proxy/</a> (by bencebeky) </li>
 =20
  <li>#3957 <a href=3D"https://github.com/quicwg/base-drafts/pull/3957">Don=
&#x27;t retransmit lost packets that are acked later</a> (by janaiyengar) <=
/li>
 =20
  <li>#3955 <a href=3D"https://github.com/quicwg/base-drafts/pull/3955">Cla=
rify HTTP/2 setting parameter reservation</a> (by MikeBishop) <span class=
=3D"label" style=3D"background-color: #fbca04; color: #">-http</span> <span=
 class=3D"label" style=3D"background-color: #1d76db; color: #">design</span=
> </li>
 =20
  <li>#3953 <a href=3D"https://github.com/quicwg/base-drafts/pull/3953">App=
lication can reset stream or close connection even if no error occurs.</a> =
(by bencebeky) </li>
 =20
  <li>#3952 <a href=3D"https://github.com/quicwg/base-drafts/pull/3952">Mov=
e transport error codes to a separate subsection.</a> (by bencebeky) </li>
 =20
  <li>#3950 <a href=3D"https://github.com/quicwg/base-drafts/pull/3950">Fix=
 spelling and style consistency nits</a> (by larseggert) </li>
 =20
  <li>#3949 <a href=3D"https://github.com/quicwg/base-drafts/pull/3949">Fix=
 spelling and style consistency nits</a> (by larseggert) </li>
 =20
  <li>#3948 <a href=3D"https://github.com/quicwg/base-drafts/pull/3948">Fix=
 spelling and style consistency nits</a> (by larseggert) </li>
 =20
  <li>#3947 <a href=3D"https://github.com/quicwg/base-drafts/pull/3947">Fix=
 spelling and style consistency nits</a> (by larseggert) </li>
 =20
  <li>#3946 <a href=3D"https://github.com/quicwg/base-drafts/pull/3946">Fix=
 spelling and style consistency nits</a> (by larseggert) </li>
 =20
  <li>#3945 <a href=3D"https://github.com/quicwg/base-drafts/pull/3945">Wor=
d-smithed version of Ted&#x27;s resolution to #3842 from the mailing list</=
a> (by larseggert) </li>
 =20
  <li>#3940 <a href=3D"https://github.com/quicwg/base-drafts/pull/3940">cla=
rify that persistent congestion is a contigous loss across all PN spaces</a=
> (by kazuho) </li>
  </ul>

  <p>4 pull requests received 5 new comments:</p>
  <ul>
  <li>#3945 <a href=3D"https://github.com/quicwg/base-drafts/pull/3945">Wor=
d-smithed version of Ted&#x27;s resolution to #3842 from the mailing list</=
a> (1 by ekr) </li>
 =20
  <li>#3940 <a href=3D"https://github.com/quicwg/base-drafts/pull/3940">cla=
rify that persistent congestion is a contigous loss across all PN spaces</a=
> (1 by kazuho) </li>
 =20
  <li>#3936 <a href=3D"https://github.com/quicwg/base-drafts/pull/3936">sen=
der SHOULD limit bursts</a> (1 by janaiyengar) <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>#3889 <a href=3D"https://github.com/quicwg/base-drafts/pull/3889">No =
RTT samples, no persistent congestion</a> (2 by janaiyengar, mjoras) <span =
class=3D"label" style=3D"background-color: #fbca04; color: #000000">-recove=
ry</span> <span class=3D"label" style=3D"background-color: #1d76db; color: =
#ffffff">design</span> </li>
  </ul>


<h3>quicwg/ops-drafts (+0/-0/=F0=9F=92=AC1)</h3>

  <p>1 pull requests received 1 new comments:</p>
  <ul>
  <li>#104 <a href=3D"https://github.com/quicwg/ops-drafts/pull/104">retry =
service and validation token</a> (1 by mirjak) </li>
  </ul>


<h3>quicwg/load-balancers (+0/-1/=F0=9F=92=AC0)</h3>


  <p>1 pull requests merged:</p>
  <ul>
  <li>#44 <a href=3D"https://github.com/quicwg/load-balancers/pull/44">Remo=
ve zero padding field</a> </li>
  </ul>


<h2>Repositories tracked by this digest:</h2>
<ul class=3D"repos">
  <li><a href=3D"https://github.com/quicwg/base-drafts">https://github.com/=
quicwg/base-drafts</a></li>
  <li><a href=3D"https://github.com/quicwg/ops-drafts">https://github.com/q=
uicwg/ops-drafts</a></li>
  <li><a href=3D"https://github.com/quicwg/datagram">https://github.com/qui=
cwg/datagram</a></li>
  <li><a href=3D"https://github.com/quicwg/load-balancers">https://github.c=
om/quicwg/load-balancers</a></li>
  <li><a href=3D"https://github.com/quicwg/version-negotiation">https://git=
hub.com/quicwg/version-negotiation</a></li>
  </ul>
</body>
</html>

--===============3166579684992273856==--


From nobody Mon Jul 27 07:06:38 2020
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 CBBA43A19CB for <quic@ietfa.amsl.com>; Mon, 27 Jul 2020 07:06:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level: 
X-Spam-Status: No, score=-17.599 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, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, 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 ktY_omD1s7an for <quic@ietfa.amsl.com>; Mon, 27 Jul 2020 07:06:31 -0700 (PDT)
Received: from mail-yb1-xb29.google.com (mail-yb1-xb29.google.com [IPv6:2607:f8b0:4864:20::b29]) (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 7A4423A19C8 for <quic@ietf.org>; Mon, 27 Jul 2020 07:06:21 -0700 (PDT)
Received: by mail-yb1-xb29.google.com with SMTP id g6so8791299ybo.11 for <quic@ietf.org>; Mon, 27 Jul 2020 07:06:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rd043wfLfXosBggmi8ZRsURDclpjy+gEpegX4oQxM0w=; b=rcJxV1h0oXmSsk7xsl6zOsIx1A5yifMtawWQlE3oYYU5V+QsIECIEjZ6xXVCChchKP /IduKJcexXcLKTQU1oBDI71dbJISTp3CvkfYmXsyGT7KSe0QScrWCL3vSiTLMn3xyWu5 f80GvnjCTfQMsvM5hFJp5eozTnYc46ERQHpm3irEO3jrXEBSLJE5ZQ1c2bFBINJVi+2n nqkyyqnShOqU+L+umMNf32bDZtXkeGGSdDZpJV9HmV0WpeXg0JXvYfAIA3XeylPc4oYp 8S8fqqhxat8AfijcC6BGxeSPD1Z+MOF4Te2duxLgqT9+RxzUG3OQ3WdSYZa7t+SCh1kh 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=rd043wfLfXosBggmi8ZRsURDclpjy+gEpegX4oQxM0w=; b=UwlKmNDHVBNHdcOnwIkDESfcWYxMtrgcE2oSF2pItsnHi5I86aGNIAGlQT28YJXAdU RuLTwWdCMB8nK3qVCAc19z0FMFc+rxBwrzLfEtvUci27gP/IIGz9ocf4eg17DwVHzvdV fTrrNDtWHgmzOzH2/FN36J1paM+oX1MGPfgeYcs+kt4SbCkBRjSgtFTUQuy3iVCA6nE8 CyGijhoMwEJ7obGAAziMM+Sc+LvlO1n6N5vAbItuqr2bGnBEa8DbDhYGJ9QtBJYX1Sss Gg1FDSL/aaoxEez+v6HeNvGk7XoCQODCgBN9PJ4+/LF0vhTuA+sONt3wZcY5M7nMluJA xouA==
X-Gm-Message-State: AOAM530wBHjAG/cUFvtn9tXaoljCGhg3MfHUuZBfJvVmD0GzlPGmVIJB GsbsCOwYXBLIUXCFjKPeW2Do+9zjeOK8I4gXFi2SZg==
X-Google-Smtp-Source: ABdhPJyd14yEim58fxG1NSTuZAzFuiwbt459AD703fhRSMjovVSmQjWuMd2ybWdaFOInC1NcbY6AECk8Vq5Vf1/dkQM=
X-Received: by 2002:a25:b78a:: with SMTP id n10mr34189339ybh.494.1595858780098;  Mon, 27 Jul 2020 07:06:20 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <9f57b20d-2eba-b2b9-d8c8-48e019c8952a@wizmail.org> <CACpbDccrpHeP5PYGCZky+AN2gC9YSs5gbAzYr4Yrw1LpvHZNiA@mail.gmail.com> <CH2PR00MB07269A73542DBC8E51E95519B67A0@CH2PR00MB0726.namprd00.prod.outlook.com> <CAKcm_gMhRX3NxiW6Primy+UrY44ZahaSO+9kF5CeeN4=XqL2JQ@mail.gmail.com> <CAKKJt-fY92k5ym767GofK+DOMQs=x6dpkwkKOA1cpkUf8Xs+3A@mail.gmail.com> <CAKcm_gPyg4QM+mZq_-E-av=u_X4nCWwdDXEH6e9Sjz1d8scEyg@mail.gmail.com> <CAKKJt-fmqjXJEUHzFT0yBXE0sLvOPcnM-oCBDZfgZQNgerRt8g@mail.gmail.com> <114a0e70-fe91-9cf9-e4e8-5f7d074eac5c@erg.abdn.ac.uk> <CACpbDcdXVN4BU5Zs823GYXteXmZEEYaVv1Adv7FGdEgMqJTsOg@mail.gmail.com>
In-Reply-To: <CACpbDcdXVN4BU5Zs823GYXteXmZEEYaVv1Adv7FGdEgMqJTsOg@mail.gmail.com>
From: Ian Swett <ianswett@google.com>
Date: Mon, 27 Jul 2020 10:06:08 -0400
Message-ID: <CAKcm_gPZN8aUREo=xZe4g0mPeubJvqJMUTWcuQQGOFAmRAFWwA@mail.gmail.com>
Subject: Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
To: Jana Iyengar <jri.ietf@gmail.com>
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>,  Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>,  Praveen Balasubramanian <pravb@microsoft.com>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000b384ad05ab6cd312"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/fYrDn5P4Cpd98wM-3AuiU-tbiRg>
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, 27 Jul 2020 14:06:35 -0000

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

For me, two things make "MUST, unless" or something along those lines
preferable for me.
1) Infinite limits make me concerned.
2) QUIC doesn't specify Slow Start After Idle and to me that seems safe
only because it requires pacing and/or limiting bursts.

But I agree the difference between "MUST unless" and SHOULD is small, so I
think this is a case for adding some extra text about why it's not a strict
MUST.

PS: I'll get back to the PR today, sorry for the delay.

On Fri, Jul 24, 2020 at 9:42 PM Jana Iyengar <jri.ietf@gmail.com> wrote:

> Gorry,
>
> That's not the only case where you don't want to pace. If I know (and I
> have a production network where this is true) that the network can absorb=
 a
> larger burst. What is the argument to make this a MUST when even the valu=
e
> of the Initial Window (of 10) is a SHOULD?
>
> - jana
>
> On Thu, Jul 23, 2020 at 2:07 AM Gorry Fairhurst <gorry@erg.abdn.ac.uk>
> wrote:
>
>> I'd like to argue a little more for something like the current text we
>> arrived at:
>>
>> "Implementations MUST either
>>    use pacing or another method to limit such bursts to the initial
>>    congestion window;"
>>
>> I've been watching, and have comments see below:
>>
>>
>> On 20/07/2020 23:11, Spencer Dawkins at IETF wrote:
>>
>> Hi, Ian,
>>
>> On Mon, Jul 20, 2020, 16:33 Ian Swett <ianswett@google.com> wrote:
>>
>>> Most of the items which I felt were somewhat deployment-specific
>>> constants(ie: Initial Window and Initial RTT) are 'RECOMMENDED' in the
>>> current recovery draft, so I thought it'd be preferable to keep that
>>> convention.
>>>
>>
>> Thanks for helping me understand - this is a stylistic change.
>>
>> I've had a couple of conversations outside of QUIC recently with people
>> who were interpreting the two terms somewhat differently, so thought it =
a
>> good time to ask.
>>
>> Best,
>>
>> Spencer
>>
>>>
>>> On Mon, Jul 20, 2020 at 5:30 PM Spencer Dawkins at IETF <
>>> spencerdawkins.ietf@gmail.com> wrote:
>>>
>>>> Hi, Ian,
>>>>
>>>> On Mon, Jul 20, 2020 at 11:49 AM Ian Swett <ianswett=3D
>>>> 40google.com@dmarc.ietf.org> wrote:
>>>>
>>>>> I think it's ok to include burst limits in the set of things we expec=
t
>>>>> may be different in DCs, but if we do that, I'd prefer to use the
>>>>> RECOMMENDED rather than SHOULD,
>>>>>
>>>>
>>>> Aren't RECOMMENDED and SHOULD equivalent in
>>>> https://tools.ietf.org/html/rfc2119?
>>>>
>>>> Or am I misunderstanding your point?
>>>>
>>>> 3 <https://tools.ietf.org/html/rfc2119#section-3>. SHOULD   This word,=
 or the adjective "RECOMMENDED", mean that there
>>>>    may exist valid reasons in particular circumstances to ignore a
>>>>    particular item, but the full implications must be understood and
>>>>    carefully weighed before choosing a different course.
>>>>
>>>>
>>>> Best,
>>>>
>>>> Spencer
>>>>
>>>> since there are a number of SHOULDs which I believe apply both to the
>>>>> public internet and to DCs.  Then we could add a note at the top abou=
t how
>>>>> there are some values which are RECOMMENDED, including X, Y and Z, an=
d
>>>>> those recommendations are expected to be good choices for most, but n=
ot all
>>>>> environments.
>>>>>
>>>>> In terms of text, I'd suggest taking Neal's suggestion and dropping a=
n
>>>>> explicit mention of the public internet:
>>>>>
>>>>> Implementations MUST either use pacing or another method to limit suc=
h bursts.
>>>>>
>>>>> It is RECOMMENDED that implementations limit bursts to the initial co=
ngestion window; see Section 7.2 <https://nam06.safelinks.protection.outloo=
k.com/?url=3Dhttps%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-quic-recovery=
-29%23section-7.2&data=3D02%7C01%7Cpravb%40microsoft.com%7C9df3e5f4f0ca4e58=
6f0908d824e0a3ad%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C6372998945266=
57906&sdata=3Dze%2F7SpKUbrdgwI6m%2BS6uEGSBgc2NapVtPn9vkOYFjVs%3D&reserved=
=3D0>.
>>>>>
>>>>>
>>>>> On Sun, Jul 19, 2020 at 4:08 PM Praveen Balasubramanian <pravb=3D
>>>>> 40microsoft.com@dmarc.ietf.org> wrote:
>>>>>
>>>>>> >> There's a way of satisfying both desires: have the NIC handle the
>>>>>> pacing.
>>>>>>
>>>>>> Yes letting the NIC handle pacing will make improve CPU efficiency
>>>>>> and improve accuracy due to fine grained hardware timers. But that=
=E2=80=99s in the
>>>>>> future. Today=E2=80=99s NICs don=E2=80=99t pace large send offloads =
for TCP or UDP.
>>>>>>
>>>>>>
>>>>>>
>>>>>> >> Perhaps we can have a principle here: recommendations that are
>>>>>> specific for Internet use are just that, and we use SHOULDs for thos=
e. IW10
>>>>>> makes sense based on this, and I would then also be fine with changi=
ng the
>>>>>> MUST to a SHOULD. Perhaps we can state this principle upfront.
>>>>>>
>>>>>> I like the idea of stating that principle up front. SHOULD would be
>>>>>> sufficient resolution for the burst size issue.
>>>>>>
>>>>>>
>>>>>>
>>>>>> *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of * Jana Iyengar
>>>>>> *Sent:* Friday, July 17, 2020 7:18 PM
>>>>>> *To:* QUIC WG <quic@ietf.org>
>>>>>> *Subject:* [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
>>>>>>
>>>>>>
>>>>>>
>>>>>> There's a protocol question and there's a question of endpoint
>>>>>> behavior. In terms of the protocol itself, yes, there's no real need=
 to
>>>>>> distinguish between Internet and DC environments; we've tried to ens=
ure
>>>>>> that the protocol can be used broadly. My point was that the constan=
ts in
>>>>>> the spec were based on what we believe to be true for the public Int=
ernet,
>>>>>> and not for DC environments.
>>>>>>
>>>>>>
>>>>>>
>>>>>> That said, perhaps I was a bit too hasty. IW10 and InitialRTT values
>>>>>> are the others I was thinking about, but those are recommendations i=
n the
>>>>>> spec, not requirements. And as Ian notes, there's no minimum timeout
>>>>>> anymore.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Perhaps we can have a principle here: recommendations that are
>>>>>> specific for Internet use are just that, and we use SHOULDs for thos=
e.
>>>>>>
>>>>> I don't agree, see below.
>>
>> IW10 makes sense based on this, and I would then also be fine with
>>>>>> changing the MUST to a SHOULD. Perhaps we can state this principle u=
pfront.
>>>>>>
>>>>>>
>>>>>>
>>>>>> Ian, I share your hesitation that we don't want to make a distinctio=
n
>>>>>> between private and public networks, but we already allow for
>>>>>> implementations to do that with a different IW and Initial RTT. Is i=
t
>>>>>> different when talking about burst limits?
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Fri, Jul 17, 2020 at 3:07 PM Jeremy Harris <jgh@wizmail.org>
>>>>>> wrote:
>>>>>>
>>>>>> On 08/07/2020 22:29, Praveen Balasubramanian wrote:
>>>>>> > Section 7.9
>>>>>> > "Implementations MUST either use pacing or another method to limit
>>>>>> such bursts to the initial congestion window; see Section 7.2."
>>>>>> > This seems to preclude use of segmentation offload of sizes greate=
r
>>>>>> than IW.. In datacenters we routinely send bursts that are higher wi=
thout
>>>>>> causing loss. The MUST here seems unnecessary. It also conflicts wit=
h the
>>>>>> RECOMMENDED in an earlier sentence.
>>>>>>
>>>>>> There's a way of satisfying both desires: have the NIC handle the
>>>>>> pacing.
>>>>>> --
>>>>>> Cheers,
>>>>>>   Jeremy
>>>>>>
>>>>>>
>> I am unsure that trying to differentiate DC from ISP-Edge from Enterpris=
e Server
>> or anything else will help in the spec. Sure, guidance may differ - but =
I'd like
>> to think (???) the IETF Spec describes the "Internet case, which
>> is expected to be good choices for most, but not all environments... and=
 if a system distributes
>> functions within your own network segment then that's your decision - an=
d yes,
>> and doing this in NICs would be great ... although NICs also can generat=
e bursts
>> when transports pace at a higher level...
>>
>> The pacing/burst-limiting could happen in various ways by various actors=
, but
>> that's not the way transport Specs are written, I thought that's why we =
ended-up with
>> "other methods".
>>
>> For me at least, it was a conscious decision to not to explicitly make t=
his "10 packets",
>> because an endpoint sender that made an informed decision to use a large=
r IW
>> has at the same time decided to configure in a way that expects the netw=
ork path can safely
>> support this burst size. I expect this matters most when the
>> connection sending rate is low (see below). But we missed something.
>>
>> I think the suggested addition from Ian, could really help a lot:
>> "unless the pacing system can't provide enough sending opportunities to =
send at the rate specified by the congestion controller."
>>
>> - This would make the language less clear, but I think in a very good wa=
y, because I agree that as the connection **sending** rate increases (and h=
ence also the CC understanding of
>> the path characteristics), the effect of bursts might be expected to be =
less significant. At higher rates queues in devices clear more quickly, and=
 buffering 1mS (or whatever) of data, buffers more.
>>
>> Can we discuss that proposal more?
>>
>> Gorry
>>
>>

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

<div dir=3D"ltr"><div>For me, two things make &quot;MUST, unless&quot; or s=
omething along those lines preferable for me.</div><div>1) Infinite limits =
make me concerned.</div><div>2) QUIC doesn&#39;t specify Slow Start After I=
dle and to me that seems safe only because it requires pacing and/or limiti=
ng bursts.</div><div><br></div><div>But I agree the difference between &quo=
t;MUST unless&quot; and SHOULD is small, so I think this is a case for addi=
ng some extra text about why it&#39;s not a strict MUST.</div><div><br></di=
v><div>PS: I&#39;ll get back to the PR today, sorry for the delay.</div></d=
iv><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On =
Fri, Jul 24, 2020 at 9:42 PM Jana Iyengar &lt;<a href=3D"mailto:jri.ietf@gm=
ail.com">jri.ietf@gmail.com</a>&gt; wrote:<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"><div dir=3D"ltr">Gorry,<div><br></div><div>That&=
#39;s not the only case where you don&#39;t want to pace. If I know (and I =
have a production network where this is true) that the network can absorb a=
 larger burst. What is the argument to make this a MUST when even the value=
 of the Initial Window (of 10) is a SHOULD?</div><div><br></div><div>- jana=
</div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_=
attr">On Thu, Jul 23, 2020 at 2:07 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;border-left:1px solid rgb(204,204,204);padding-left:1ex">
 =20
   =20
 =20
  <div>
    <p>I&#39;d like to argue a little more for something like the current
      text we arrived at:</p>
    <pre>&quot;Implementations MUST either
   use pacing or another method to limit such bursts to the initial
   congestion window;&quot;

I&#39;ve been watching, and have comments see below:

</pre>
    <div>On 20/07/2020 23:11, Spencer Dawkins at
      IETF wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"auto">
        <div>Hi, Ian,<br>
          <br>
          <div class=3D"gmail_quote">
            <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jul 20, 2020,
              16:33 Ian Swett &lt;<a href=3D"mailto:ianswett@google.com" ta=
rget=3D"_blank">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 dir=3D"ltr">Most of the items which I felt were
                somewhat deployment-specific constants(ie: Initial
                Window and Initial RTT) are &#39;RECOMMENDED&#39; in the cu=
rrent
                recovery draft, so I thought it&#39;d be preferable to keep
                that convention.</div>
            </blockquote>
          </div>
        </div>
        <div dir=3D"auto"><br>
        </div>
        <div dir=3D"auto">Thanks for helping me understand - this is a
          stylistic change.</div>
        <div dir=3D"auto"><br>
        </div>
        <div dir=3D"auto">I&#39;ve had a couple of conversations outside of
          QUIC recently with people who were interpreting the two terms
          somewhat differently, so thought it a good time to ask.</div>
        <div dir=3D"auto"><br>
        </div>
        <div dir=3D"auto">Best,</div>
        <div dir=3D"auto"><br>
        </div>
        <div dir=3D"auto">Spencer</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:1px solid rgb(204,204,204);padding-left:1ex"><br>
              <div class=3D"gmail_quote">
                <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jul 20, 2020
                  at 5:30 PM Spencer Dawkins at IETF &lt;<a href=3D"mailto:=
spencerdawkins.ietf@gmail.com" rel=3D"noreferrer" target=3D"_blank">spencer=
dawkins.ietf@gmail.com</a>&gt;
                  wrote:<br>
                </div>
                <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
                  <div dir=3D"ltr">
                    <div dir=3D"ltr">Hi, Ian,=C2=A0</div>
                    <br>
                    <div class=3D"gmail_quote">
                      <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jul 20,
                        2020 at 11:49 AM Ian Swett &lt;ianswett=3D<a href=
=3D"mailto:40google.com@dmarc.ietf.org" rel=3D"noreferrer" target=3D"_blank=
">40google.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">
                        <div dir=3D"ltr">I think it&#39;s ok to include bur=
st
                          limits in the set of things we expect may be
                          different in DCs, but if we do that, I&#39;d
                          prefer to use the RECOMMENDED rather than
                          SHOULD,</div>
                      </blockquote>
                      <div><br>
                      </div>
                      <div>Aren&#39;t RECOMMENDED and SHOULD equivalent in=
=C2=A0
                        <a href=3D"https://tools.ietf.org/html/rfc2119" rel=
=3D"noreferrer" target=3D"_blank">https://tools.ietf.org/html/rfc2119</a>?=
=C2=A0</div>
                      <div><br>
                      </div>
                      <div>Or am I misunderstanding your point?</div>
                      <div><br>
                      </div>
                      <div>
                        <pre style=3D"margin-top:0px;margin-bottom:0px;colo=
r:rgb(0,0,0)"><font size=3D"4"><span style=3D"display:inline;font-weight:bo=
ld"><h2 style=3D"display:inline"><a name=3D"m_-138022109493467158_m_6172066=
709575264695_m_-7104407681243286268_m_-561907519085294557_section-3" href=
=3D"https://tools.ietf.org/html/rfc2119#section-3" style=3D"color:black;tex=
t-decoration-line:none" rel=3D"noreferrer" target=3D"_blank">3</a>. SHOULD =
 </h2></span> This word, or the adjective &quot;RECOMMENDED&quot;, mean tha=
t there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.</font></pre>
                      </div>
                      <div>=C2=A0</div>
                      <div>Best,</div>
                      <div><br>
                      </div>
                      <div>Spencer</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"> since there are a number of
                          SHOULDs which I believe=C2=A0apply both to the
                          public internet and to DCs.=C2=A0 Then we could a=
dd
                          a note at the top about how there are some
                          values which are RECOMMENDED, including X, Y
                          and Z, and those recommendations are expected
                          to be good choices for most, but not all
                          environments.
                          <div><br>
                          </div>
                          <div>In terms of text, I&#39;d suggest taking
                            Neal&#39;s suggestion and dropping an explicit
                            mention of the public internet:</div>
                          <div><br>
                          </div>
                          <div>
                            <pre style=3D"white-space:pre-wrap;margin:0in;f=
ont-size:10pt;font-family:&quot;Courier New&quot;;break-before:page"><span =
style=3D"color:black">Implementations MUST either use pacing or another met=
hod to limit such bursts.</span></pre>
                            <pre style=3D"white-space:pre-wrap;margin:0in;f=
ont-size:10pt;font-family:&quot;Courier New&quot;;break-before:page"><span =
style=3D"color:black">It is RECOMMENDED that implementations limit bursts t=
o the initial </span>congestion window; see <a href=3D"https://nam06.safeli=
nks.protection.outlook.com/?url=3Dhttps%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdra=
ft-ietf-quic-recovery-29%23section-7.2&amp;data=3D02%7C01%7Cpravb%40microso=
ft.com%7C9df3e5f4f0ca4e586f0908d824e0a3ad%7C72f988bf86f141af91ab2d7cd011db4=
7%7C1%7C0%7C637299894526657906&amp;sdata=3Dze%2F7SpKUbrdgwI6m%2BS6uEGSBgc2N=
apVtPn9vkOYFjVs%3D&amp;reserved=3D0" style=3D"font-size:10pt" rel=3D"norefe=
rrer" target=3D"_blank">Section 7.2</a><span style=3D"font-size:10pt;color:=
black">.</span></pre>
                          </div>
                        </div>
                        <br>
                        <div class=3D"gmail_quote">
                          <div dir=3D"ltr" class=3D"gmail_attr">On Sun, Jul
                            19, 2020 at 4:08 PM Praveen Balasubramanian
                            &lt;pravb=3D<a href=3D"mailto:40microsoft.com@d=
marc.ietf.org" rel=3D"noreferrer" target=3D"_blank">40microsoft.com@dmarc.i=
etf.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"=
>
                            <div lang=3D"EN-US">
                              <div>
                                <p class=3D"MsoNormal">&gt;&gt; There&#39;s=
 a
                                  way of satisfying both desires: have
                                  the NIC handle the pacing.</p>
                                <p class=3D"MsoNormal">Yes letting the NIC
                                  handle pacing will make improve CPU
                                  efficiency and improve accuracy due to
                                  fine grained hardware timers. But
                                  that=E2=80=99s in the future. Today=E2=80=
=99s NICs
                                  don=E2=80=99t pace large send offloads fo=
r TCP
                                  or UDP.</p>
                                <p class=3D"MsoNormal">=C2=A0</p>
                                <p class=3D"MsoNormal">&gt;&gt; Perhaps we
                                  can have a principle here:
                                  recommendations that are specific for
                                  Internet use are just that, and we use
                                  SHOULDs for those. IW10 makes sense
                                  based on this, and I would then also
                                  be fine with changing the MUST to a
                                  SHOULD. Perhaps we can state this
                                  principle upfront.</p>
                                <p class=3D"MsoNormal">I like the idea of
                                  stating that principle up front.
                                  SHOULD would be sufficient resolution
                                  for the burst size issue.
                                </p>
                                <p class=3D"MsoNormal">=C2=A0</p>
                                <div style=3D"border-right:none;border-bott=
om:none;border-left:none;border-top:1pt solid rgb(225,225,225);padding:3pt =
0in 0in">
                                  <p class=3D"MsoNormal"><b>From:</b> QUIC
                                    &lt;<a href=3D"mailto:quic-bounces@ietf=
.org" rel=3D"noreferrer" target=3D"_blank">quic-bounces@ietf.org</a>&gt;
                                    <b>On Behalf Of </b>
                                    Jana Iyengar<br>
                                    <b>Sent:</b> Friday, July 17, 2020
                                    7:18 PM<br>
                                    <b>To:</b> QUIC WG &lt;<a href=3D"mailt=
o:quic@ietf.org" rel=3D"noreferrer" target=3D"_blank">quic@ietf.org</a>&gt;=
<br>
                                    <b>Subject:</b> [EXTERNAL] Re: WGLC
                                    review of
                                    draft-ietf-quic-recovery-29</p>
                                </div>
                                <p class=3D"MsoNormal">=C2=A0</p>
                                <div>
                                  <p class=3D"MsoNormal">There&#39;s a
                                    protocol question and there&#39;s a
                                    question of endpoint behavior. In
                                    terms of the protocol itself, yes,
                                    there&#39;s no real need to distinguish
                                    between Internet and DC
                                    environments; we&#39;ve tried to ensure
                                    that the protocol can be used
                                    broadly. My point was that the
                                    constants=C2=A0in the spec were based o=
n
                                    what we believe to be true for the
                                    public Internet, and not for DC
                                    environments.</p>
                                  <div>
                                    <p class=3D"MsoNormal">=C2=A0</p>
                                  </div>
                                  <div>
                                    <p class=3D"MsoNormal">That said,
                                      perhaps I was a bit too hasty.
                                      IW10 and InitialRTT values are the
                                      others I was thinking about, but
                                      those are=C2=A0recommendations in the
                                      spec, not requirements. And as Ian
                                      notes, there&#39;s no minimum timeout
                                      anymore.</p>
                                  </div>
                                  <div>
                                    <p class=3D"MsoNormal">=C2=A0</p>
                                  </div>
                                  <div>
                                    <p class=3D"MsoNormal">Perhaps we can
                                      have a principle here:
                                      recommendations that are specific
                                      for Internet use are just that,
                                      and we use SHOULDs for those. </p>
                                  </div>
                                </div>
                              </div>
                            </div>
                          </blockquote>
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </blockquote>
              </div>
            </blockquote>
          </div>
        </div>
      </div>
    </blockquote>
    I don&#39;t agree, see below.<br>
    <blockquote type=3D"cite">
      <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:1px solid rgb(204,204,204);padding-left:1ex">
              <div class=3D"gmail_quote">
                <blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0=
px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
                  <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 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 lang=3D"EN-US">
                              <div>
                                <div>
                                  <div>
                                    <p class=3D"MsoNormal">IW10 makes
                                      sense based on this, and I would
                                      then also be fine with changing
                                      the MUST to a SHOULD. Perhaps we
                                      can state this principle upfront.</p>
                                  </div>
                                  <div>
                                    <p class=3D"MsoNormal">=C2=A0</p>
                                  </div>
                                  <div>
                                    <p class=3D"MsoNormal">Ian, I share
                                      your hesitation that we don&#39;t wan=
t
                                      to make a distinction between
                                      private and public networks,=C2=A0but
                                      we already allow for
                                      implementations to do that with a
                                      different=C2=A0IW and Initial RTT. Is
                                      it different when talking about
                                      burst limits?</p>
                                  </div>
                                  <div>
                                    <p class=3D"MsoNormal">=C2=A0</p>
                                  </div>
                                </div>
                                <p class=3D"MsoNormal">=C2=A0</p>
                                <div>
                                  <div>
                                    <p class=3D"MsoNormal">On Fri, Jul 17,
                                      2020 at 3:07 PM Jeremy Harris &lt;<a =
href=3D"mailto:jgh@wizmail.org" rel=3D"noreferrer" target=3D"_blank">jgh@wi=
zmail.org</a>&gt;
                                      wrote:</p>
                                  </div>
                                  <blockquote>
                                    <p class=3D"MsoNormal" style=3D"margin-=
bottom:12pt">On
                                      08/07/2020 22:29, Praveen
                                      Balasubramanian wrote:<br>
                                      &gt; Section 7.9<br>
                                      &gt; &quot;Implementations MUST eithe=
r
                                      use pacing or another method to
                                      limit such bursts to the initial
                                      congestion window; see Section
                                      7.2.&quot;<br>
                                      &gt; This seems to preclude use of
                                      segmentation offload of sizes
                                      greater than IW.. In datacenters
                                      we routinely send bursts that are
                                      higher without causing loss. The
                                      MUST here seems unnecessary. It
                                      also conflicts with the
                                      RECOMMENDED in an earlier
                                      sentence.<br>
                                      <br>
                                      There&#39;s a way of satisfying both
                                      desires: have the NIC handle the<br>
                                      pacing.<br>
                                      -- <br>
                                      Cheers,<br>
                                      =C2=A0 Jeremy</p>
                                  </blockquote>
                                </div>
                              </div>
                            </div>
                          </blockquote>
                        </div>
                      </blockquote>
                    </div>
                  </div>
                </blockquote>
              </div>
            </blockquote>
          </div>
        </div>
      </div>
    </blockquote>
    <p><br>
    </p>
    <pre>I am unsure that trying to differentiate DC from ISP-Edge from Ent=
erprise Server
or anything else will help in the spec. Sure, guidance may differ - but I&#=
39;d like
to think (???) the IETF Spec describes the &quot;Internet case, which
is expected to be good choices for most, but not all environments... and if=
 a system distributes
functions within your own network segment then that&#39;s your decision - a=
nd yes,
and doing this in NICs would be great ... although NICs also can generate b=
ursts=20
when transports pace at a higher level...=20

The pacing/burst-limiting could happen in various ways by various actors, b=
ut
that&#39;s not the way transport Specs are written, I thought that&#39;s wh=
y we ended-up with=20
&quot;other methods&quot;.

For me at least, it was a conscious decision to not to explicitly make this=
 &quot;10 packets&quot;,=20
because an endpoint sender that made an informed decision to use a larger I=
W=20
has at the same time decided to configure in a way that expects the network=
 path can safely=20
support this burst size. I expect this matters most when the
connection sending rate is low (see below). But we missed something.

I think the suggested addition from Ian, could really help a lot:
&quot;unless the pacing system can&#39;t provide enough sending opportuniti=
es to send at the rate specified by the congestion controller.&quot;

- This would make the language less clear, but I think in a very good way, =
because I agree that as the connection **sending** rate increases (and henc=
e also the CC understanding of
the path characteristics), the effect of bursts might be expected to be les=
s significant. At higher rates queues in devices clear more quickly, and bu=
ffering 1mS (or whatever) of data, buffers more.=20

Can we discuss that proposal more?

Gorry
</pre>
  </div>

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

--000000000000b384ad05ab6cd312--


From nobody Mon Jul 27 07:30:43 2020
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 AA9163A1A0B for <quic@ietfa.amsl.com>; Mon, 27 Jul 2020 07:30:41 -0700 (PDT)
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, HTML_MESSAGE=0.001, NICE_REPLY_A=-0.001, 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 us8YaG2NI-sv for <quic@ietfa.amsl.com>; Mon, 27 Jul 2020 07:30:38 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [137.50.19.135]) by ietfa.amsl.com (Postfix) with ESMTP id A53EC3A1B2D for <quic@ietf.org>; Mon, 27 Jul 2020 07:29:32 -0700 (PDT)
Received: from GF-MacBook-Pro.lan (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id EA1151B00127; Mon, 27 Jul 2020 15:29:06 +0100 (BST)
Subject: Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
To: Ian Swett <ianswett@google.com>, Jana Iyengar <jri.ietf@gmail.com>
Cc: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, Praveen Balasubramanian <pravb@microsoft.com>, QUIC WG <quic@ietf.org>
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <9f57b20d-2eba-b2b9-d8c8-48e019c8952a@wizmail.org> <CACpbDccrpHeP5PYGCZky+AN2gC9YSs5gbAzYr4Yrw1LpvHZNiA@mail.gmail.com> <CH2PR00MB07269A73542DBC8E51E95519B67A0@CH2PR00MB0726.namprd00.prod.outlook.com> <CAKcm_gMhRX3NxiW6Primy+UrY44ZahaSO+9kF5CeeN4=XqL2JQ@mail.gmail.com> <CAKKJt-fY92k5ym767GofK+DOMQs=x6dpkwkKOA1cpkUf8Xs+3A@mail.gmail.com> <CAKcm_gPyg4QM+mZq_-E-av=u_X4nCWwdDXEH6e9Sjz1d8scEyg@mail.gmail.com> <CAKKJt-fmqjXJEUHzFT0yBXE0sLvOPcnM-oCBDZfgZQNgerRt8g@mail.gmail.com> <114a0e70-fe91-9cf9-e4e8-5f7d074eac5c@erg.abdn.ac.uk> <CACpbDcdXVN4BU5Zs823GYXteXmZEEYaVv1Adv7FGdEgMqJTsOg@mail.gmail.com> <CAKcm_gPZN8aUREo=xZe4g0mPeubJvqJMUTWcuQQGOFAmRAFWwA@mail.gmail.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <4bd2186e-21c5-a084-5ef6-aad2f64892b5@erg.abdn.ac.uk>
Date: Mon, 27 Jul 2020 15:28:51 +0100
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:68.0) Gecko/20100101 Thunderbird/68.10.0
MIME-Version: 1.0
In-Reply-To: <CAKcm_gPZN8aUREo=xZe4g0mPeubJvqJMUTWcuQQGOFAmRAFWwA@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------1627F8D37727C9AE816986A9"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/UdQGGX2amMBE4g7LjiaKYr40nB4>
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, 27 Jul 2020 14:30:42 -0000

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


On 27/07/2020 15:06, Ian Swett wrote:
> For me, two things make "MUST, unless" or something along those lines 
> preferable for me.
> 1) Infinite limits make me concerned.
> 2) QUIC doesn't specify Slow Start After Idle and to me that seems 
> safe only because it requires pacing and/or limiting bursts.
>
> But I agree the difference between "MUST unless" and SHOULD is small, 
> so I think this is a case for adding some extra text about why it's 
> not a strict MUST.
>
> PS: I'll get back to the PR today, sorry for the delay.
>
Great. I'll look forward to reading that new text.

> On Fri, Jul 24, 2020 at 9:42 PM Jana Iyengar <jri.ietf@gmail.com 
> <mailto:jri.ietf@gmail.com>> wrote:
>
>     Gorry,
>
>     That's not the only case where you don't want to pace. If I know
>     (and I have a production network where this is true) that the
>     network can absorb a larger burst. What is the argument to make
>     this a MUST when even the value of the Initial Window (of 10) is a
>     SHOULD?
>
>     - jana
>

In answer to Jana, if you know the path has specific capabilities - 
which is pretty much what I'd expect in an DC or any other "constrained 
environment", the normal Internet guidance isn't necessarily appropiate. 
Generally that is not what IETF specs target.

Gorry

>     On Thu, Jul 23, 2020 at 2:07 AM Gorry Fairhurst
>     <gorry@erg.abdn.ac.uk <mailto:gorry@erg.abdn.ac.uk>> wrote:
>
>         I'd like to argue a little more for something like the current
>         text we arrived at:
>
>         "Implementations MUST either
>             use pacing or another method to limit such bursts to the initial
>             congestion window;"
>
>         I've been watching, and have comments see below:
>
>         On 20/07/2020 23:11, Spencer Dawkins at IETF wrote:
>>         Hi, Ian,
>>
>>         On Mon, Jul 20, 2020, 16:33 Ian Swett <ianswett@google.com
>>         <mailto:ianswett@google.com>> wrote:
>>
>>             Most of the items which I felt were somewhat
>>             deployment-specific constants(ie: Initial Window and
>>             Initial RTT) are 'RECOMMENDED' in the current recovery
>>             draft, so I thought it'd be preferable to keep that
>>             convention.
>>
>>
>>         Thanks for helping me understand - this is a stylistic change.
>>
>>         I've had a couple of conversations outside of QUIC recently
>>         with people who were interpreting the two terms somewhat
>>         differently, so thought it a good time to ask.
>>
>>         Best,
>>
>>         Spencer
>>
>>
>>             On Mon, Jul 20, 2020 at 5:30 PM Spencer Dawkins at IETF
>>             <spencerdawkins.ietf@gmail.com
>>             <mailto:spencerdawkins.ietf@gmail.com>> wrote:
>>
>>                 Hi, Ian,
>>
>>                 On Mon, Jul 20, 2020 at 11:49 AM Ian Swett
>>                 <ianswett=40google.com@dmarc.ietf.org
>>                 <mailto:40google.com@dmarc.ietf.org>> wrote:
>>
>>                     I think it's ok to include burst limits in the
>>                     set of things we expect may be different in DCs,
>>                     but if we do that, I'd prefer to use the
>>                     RECOMMENDED rather than SHOULD,
>>
>>
>>                 Aren't RECOMMENDED and SHOULD equivalent in
>>                 https://tools.ietf.org/html/rfc2119?
>>
>>                 Or am I misunderstanding your point?
>>
>>
>>                     3
>>                     <https://tools.ietf.org/html/rfc2119#section-3>.
>>                     SHOULD
>>
>>                 This word, or the adjective "RECOMMENDED", mean that
>>                 there may exist valid reasons in particular
>>                 circumstances to ignore a particular item, but the
>>                 full implications must be understood and carefully
>>                 weighed before choosing a different course.
>>
>>                 Best,
>>
>>                 Spencer
>>
>>                     since there are a number of SHOULDs which I
>>                     believe apply both to the public internet and to
>>                     DCs.  Then we could add a note at the top about
>>                     how there are some values which are RECOMMENDED,
>>                     including X, Y and Z, and those recommendations
>>                     are expected to be good choices for most, but not
>>                     all environments.
>>
>>                     In terms of text, I'd suggest taking Neal's
>>                     suggestion and dropping an explicit mention of
>>                     the public internet:
>>
>>                     Implementations MUST either use pacing or another
>>                     method to limit such bursts.
>>
>>                     It is RECOMMENDED that implementations limit
>>                     bursts to the initial congestion window; seeSection 7.2  <https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-quic-recovery-29%23section-7.2&data=02%7C01%7Cpravb%40microsoft.com%7C9df3e5f4f0ca4e586f0908d824e0a3ad%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637299894526657906&sdata=ze%2F7SpKUbrdgwI6m%2BS6uEGSBgc2NapVtPn9vkOYFjVs%3D&reserved=0>.
>>
>>
>>                     On Sun, Jul 19, 2020 at 4:08 PM Praveen
>>                     Balasubramanian
>>                     <pravb=40microsoft.com@dmarc.ietf.org
>>                     <mailto:40microsoft.com@dmarc.ietf.org>> wrote:
>>
>>                         >> There's a way of satisfying both desires:
>>                         have the NIC handle the pacing.
>>
>>                         Yes letting the NIC handle pacing will make
>>                         improve CPU efficiency and improve accuracy
>>                         due to fine grained hardware timers. But
>>                         that’s in the future. Today’s NICs don’t pace
>>                         large send offloads for TCP or UDP.
>>
>>                         >> Perhaps we can have a principle here:
>>                         recommendations that are specific for
>>                         Internet use are just that, and we use
>>                         SHOULDs for those. IW10 makes sense based on
>>                         this, and I would then also be fine with
>>                         changing the MUST to a SHOULD. Perhaps we can
>>                         state this principle upfront.
>>
>>                         I like the idea of stating that principle up
>>                         front. SHOULD would be sufficient resolution
>>                         for the burst size issue.
>>
>>                         *From:* QUIC <quic-bounces@ietf.org
>>                         <mailto:quic-bounces@ietf.org>> *On Behalf Of
>>                         * Jana Iyengar
>>                         *Sent:* Friday, July 17, 2020 7:18 PM
>>                         *To:* QUIC WG <quic@ietf.org
>>                         <mailto:quic@ietf.org>>
>>                         *Subject:* [EXTERNAL] Re: WGLC review of
>>                         draft-ietf-quic-recovery-29
>>
>>                         There's a protocol question and there's a
>>                         question of endpoint behavior. In terms of
>>                         the protocol itself, yes, there's no real
>>                         need to distinguish between Internet and DC
>>                         environments; we've tried to ensure that the
>>                         protocol can be used broadly. My point was
>>                         that the constants in the spec were based on
>>                         what we believe to be true for the public
>>                         Internet, and not for DC environments.
>>
>>                         That said, perhaps I was a bit too hasty.
>>                         IW10 and InitialRTT values are the others I
>>                         was thinking about, but those
>>                         are recommendations in the spec, not
>>                         requirements. And as Ian notes, there's no
>>                         minimum timeout anymore.
>>
>>                         Perhaps we can have a principle here:
>>                         recommendations that are specific for
>>                         Internet use are just that, and we use
>>                         SHOULDs for those.
>>
>         I don't agree, see below.
>>
>>                         IW10 makes sense based on this, and I would
>>                         then also be fine with changing the MUST to a
>>                         SHOULD. Perhaps we can state this principle
>>                         upfront.
>>
>>                         Ian, I share your hesitation that we don't
>>                         want to make a distinction between private
>>                         and public networks, but we already allow for
>>                         implementations to do that with a
>>                         different IW and Initial RTT. Is it different
>>                         when talking about burst limits?
>>
>>                         On Fri, Jul 17, 2020 at 3:07 PM Jeremy Harris
>>                         <jgh@wizmail.org <mailto:jgh@wizmail.org>> wrote:
>>
>>                             On 08/07/2020 22:29, Praveen
>>                             Balasubramanian wrote:
>>                             > Section 7.9
>>                             > "Implementations MUST either use pacing
>>                             or another method to limit such bursts to
>>                             the initial congestion window; see
>>                             Section 7.2."
>>                             > This seems to preclude use of
>>                             segmentation offload of sizes greater
>>                             than IW.. In datacenters we routinely
>>                             send bursts that are higher without
>>                             causing loss. The MUST here seems
>>                             unnecessary. It also conflicts with the
>>                             RECOMMENDED in an earlier sentence.
>>
>>                             There's a way of satisfying both desires:
>>                             have the NIC handle the
>>                             pacing.
>>                             -- 
>>                             Cheers,
>>                               Jeremy
>>
>
>         I am unsure that trying to differentiate DC from ISP-Edge from Enterprise Server
>         or anything else will help in the spec. Sure, guidance may differ - but I'd like
>         to think (???) the IETF Spec describes the "Internet case, which
>         is expected to be good choices for most, but not all environments... and if a system distributes
>         functions within your own network segment then that's your decision - and yes,
>         and doing this in NICs would be great ... although NICs also can generate bursts
>         when transports pace at a higher level...
>
>         The pacing/burst-limiting could happen in various ways by various actors, but
>         that's not the way transport Specs are written, I thought that's why we ended-up with
>         "other methods".
>
>         For me at least, it was a conscious decision to not to explicitly make this "10 packets",
>         because an endpoint sender that made an informed decision to use a larger IW
>         has at the same time decided to configure in a way that expects the network path can safely
>         support this burst size. I expect this matters most when the
>         connection sending rate is low (see below). But we missed something.
>
>         I think the suggested addition from Ian, could really help a lot:
>         "unless the pacing system can't provide enough sending opportunities to send at the rate specified by the congestion controller."
>
>         - This would make the language less clear, but I think in a very good way, because I agree that as the connection **sending** rate increases (and hence also the CC understanding of
>         the path characteristics), the effect of bursts might be expected to be less significant. At higher rates queues in devices clear more quickly, and buffering 1mS (or whatever) of data, buffers more.
>
>         Can we discuss that proposal more?
>
>         Gorry
>

--------------1627F8D37727C9AE816986A9
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 27/07/2020 15:06, Ian Swett wrote:<br>
    </div>
    <blockquote type="cite"
cite="mid:CAKcm_gPZN8aUREo=xZe4g0mPeubJvqJMUTWcuQQGOFAmRAFWwA@mail.gmail.com">
      <meta http-equiv="content-type" content="text/html; charset=UTF-8">
      <div dir="ltr">
        <div>For me, two things make "MUST, unless" or something along
          those lines preferable for me.</div>
        <div>1) Infinite limits make me concerned.</div>
        <div>2) QUIC doesn't specify Slow Start After Idle and to me
          that seems safe only because it requires pacing and/or
          limiting bursts.</div>
        <div><br>
        </div>
        <div>But I agree the difference between "MUST unless" and SHOULD
          is small, so I think this is a case for adding some extra text
          about why it's not a strict MUST.</div>
        <div><br>
        </div>
        <div>PS: I'll get back to the PR today, sorry for the delay.</div>
      </div>
      <br>
    </blockquote>
    <p>Great. I'll look forward to reading that new text.</p>
    <blockquote type="cite"
cite="mid:CAKcm_gPZN8aUREo=xZe4g0mPeubJvqJMUTWcuQQGOFAmRAFWwA@mail.gmail.com">
      <div class="gmail_quote">
        <div dir="ltr" class="gmail_attr">On Fri, Jul 24, 2020 at 9:42
          PM Jana Iyengar &lt;<a href="mailto:jri.ietf@gmail.com"
            moz-do-not-send="true">jri.ietf@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 dir="ltr">Gorry,
            <div><br>
            </div>
            <div>That's not the only case where you don't want to pace.
              If I know (and I have a production network where this is
              true) that the network can absorb a larger burst. What is
              the argument to make this a MUST when even the value of
              the Initial Window (of 10) is a SHOULD?</div>
            <div><br>
            </div>
            <div>- jana</div>
          </div>
          <br>
        </blockquote>
      </div>
    </blockquote>
    <br>
    <p>In answer to Jana, if you know the path has specific capabilities
      - which is pretty much what I'd expect in an DC or any other
      "constrained environment", the normal Internet guidance isn't
      necessarily appropiate. Generally that is not what IETF specs
      target. <br>
    </p>
    <p>Gorry</p>
    <blockquote type="cite"
cite="mid:CAKcm_gPZN8aUREo=xZe4g0mPeubJvqJMUTWcuQQGOFAmRAFWwA@mail.gmail.com">
      <div class="gmail_quote">
        <blockquote class="gmail_quote" style="margin:0px 0px 0px
          0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
          <div class="gmail_quote">
            <div dir="ltr" class="gmail_attr">On Thu, Jul 23, 2020 at
              2:07 AM Gorry Fairhurst &lt;<a
                href="mailto:gorry@erg.abdn.ac.uk" target="_blank"
                moz-do-not-send="true">gorry@erg.abdn.ac.uk</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>
                <p>I'd like to argue a little more for something like
                  the current text we arrived at:</p>
                <pre>"Implementations MUST either
   use pacing or another method to limit such bursts to the initial
   congestion window;"

I've been watching, and have comments see below:

</pre>
                <div>On 20/07/2020 23:11, Spencer Dawkins at IETF wrote:<br>
                </div>
                <blockquote type="cite">
                  <div dir="auto">
                    <div>Hi, Ian,<br>
                      <br>
                      <div class="gmail_quote">
                        <div dir="ltr" class="gmail_attr">On Mon, Jul
                          20, 2020, 16:33 Ian Swett &lt;<a
                            href="mailto:ianswett@google.com"
                            target="_blank" moz-do-not-send="true">ianswett@google.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 dir="ltr">Most of the items which I felt
                            were somewhat deployment-specific
                            constants(ie: Initial Window and Initial
                            RTT) are 'RECOMMENDED' in the current
                            recovery draft, so I thought it'd be
                            preferable to keep that convention.</div>
                        </blockquote>
                      </div>
                    </div>
                    <div dir="auto"><br>
                    </div>
                    <div dir="auto">Thanks for helping me understand -
                      this is a stylistic change.</div>
                    <div dir="auto"><br>
                    </div>
                    <div dir="auto">I've had a couple of conversations
                      outside of QUIC recently with people who were
                      interpreting the two terms somewhat differently,
                      so thought it a good time to ask.</div>
                    <div dir="auto"><br>
                    </div>
                    <div dir="auto">Best,</div>
                    <div dir="auto"><br>
                    </div>
                    <div dir="auto">Spencer</div>
                    <div dir="auto">
                      <div class="gmail_quote">
                        <blockquote class="gmail_quote"
                          style="margin:0px 0px 0px
                          0.8ex;border-left:1px solid
                          rgb(204,204,204);padding-left:1ex"><br>
                          <div class="gmail_quote">
                            <div dir="ltr" class="gmail_attr">On Mon,
                              Jul 20, 2020 at 5:30 PM Spencer Dawkins at
                              IETF &lt;<a
                                href="mailto:spencerdawkins.ietf@gmail.com"
                                rel="noreferrer" target="_blank"
                                moz-do-not-send="true">spencerdawkins.ietf@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 dir="ltr">
                                <div dir="ltr">Hi, Ian, </div>
                                <br>
                                <div class="gmail_quote">
                                  <div dir="ltr" class="gmail_attr">On
                                    Mon, Jul 20, 2020 at 11:49 AM Ian
                                    Swett &lt;ianswett=<a
                                      href="mailto:40google.com@dmarc.ietf.org"
                                      rel="noreferrer" target="_blank"
                                      moz-do-not-send="true">40google.com@dmarc.ietf.org</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 dir="ltr">I think it's ok to
                                      include burst limits in the set of
                                      things we expect may be different
                                      in DCs, but if we do that, I'd
                                      prefer to use the RECOMMENDED
                                      rather than SHOULD,</div>
                                  </blockquote>
                                  <div><br>
                                  </div>
                                  <div>Aren't RECOMMENDED and SHOULD
                                    equivalent in  <a
                                      href="https://tools.ietf.org/html/rfc2119"
                                      rel="noreferrer" target="_blank"
                                      moz-do-not-send="true">https://tools.ietf.org/html/rfc2119</a>? </div>
                                  <div><br>
                                  </div>
                                  <div>Or am I misunderstanding your
                                    point?</div>
                                  <div><br>
                                  </div>
                                  <div>
                                    <pre style="margin-top:0px;margin-bottom:0px;color:rgb(0,0,0)"><font size="4"><span style="display:inline;font-weight:bold"><h2 style="display:inline"><a name="m_-138022109493467158_m_6172066709575264695_m_-7104407681243286268_m_-561907519085294557_section-3" href="https://tools.ietf.org/html/rfc2119#section-3" style="color:black;text-decoration-line:none" rel="noreferrer" target="_blank" moz-do-not-send="true">3</a>. SHOULD  </h2></span> This word, or the adjective "RECOMMENDED", mean that there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.</font></pre>
                                  </div>
                                  <div> </div>
                                  <div>Best,</div>
                                  <div><br>
                                  </div>
                                  <div>Spencer</div>
                                  <div><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 dir="ltr"> since there are a
                                      number of SHOULDs which I
                                      believe apply both to the public
                                      internet and to DCs.  Then we
                                      could add a note at the top about
                                      how there are some values which
                                      are RECOMMENDED, including X, Y
                                      and Z, and those recommendations
                                      are expected to be good choices
                                      for most, but not all
                                      environments.
                                      <div><br>
                                      </div>
                                      <div>In terms of text, I'd suggest
                                        taking Neal's suggestion and
                                        dropping an explicit mention of
                                        the public internet:</div>
                                      <div><br>
                                      </div>
                                      <div>
                                        <pre style="white-space:pre-wrap;margin:0in;font-size:10pt;font-family:&quot;Courier New&quot;;break-before:page"><span style="color:black">Implementations MUST either use pacing or another method to limit such bursts.</span></pre>
                                        <pre style="white-space:pre-wrap;margin:0in;font-size:10pt;font-family:&quot;Courier New&quot;;break-before:page"><span style="color:black">It is RECOMMENDED that implementations limit bursts to the initial </span>congestion window; see <a href="https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-quic-recovery-29%23section-7.2&amp;data=02%7C01%7Cpravb%40microsoft.com%7C9df3e5f4f0ca4e586f0908d824e0a3ad%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637299894526657906&amp;sdata=ze%2F7SpKUbrdgwI6m%2BS6uEGSBgc2NapVtPn9vkOYFjVs%3D&amp;reserved=0" style="font-size:10pt" rel="noreferrer" target="_blank" moz-do-not-send="true">Section 7.2</a><span style="font-size:10pt;color:black">.</span></pre>
                                      </div>
                                    </div>
                                    <br>
                                    <div class="gmail_quote">
                                      <div dir="ltr" class="gmail_attr">On
                                        Sun, Jul 19, 2020 at 4:08 PM
                                        Praveen Balasubramanian
                                        &lt;pravb=<a
                                          href="mailto:40microsoft.com@dmarc.ietf.org"
                                          rel="noreferrer"
                                          target="_blank"
                                          moz-do-not-send="true">40microsoft.com@dmarc.ietf.org</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 lang="EN-US">
                                          <div>
                                            <p class="MsoNormal">&gt;&gt;
                                              There's a way of
                                              satisfying both desires:
                                              have the NIC handle the
                                              pacing.</p>
                                            <p class="MsoNormal">Yes
                                              letting the NIC handle
                                              pacing will make improve
                                              CPU efficiency and improve
                                              accuracy due to fine
                                              grained hardware timers.
                                              But that’s in the future.
                                              Today’s NICs don’t pace
                                              large send offloads for
                                              TCP or UDP.</p>
                                            <p class="MsoNormal"> </p>
                                            <p class="MsoNormal">&gt;&gt;
                                              Perhaps we can have a
                                              principle here:
                                              recommendations that are
                                              specific for Internet use
                                              are just that, and we use
                                              SHOULDs for those. IW10
                                              makes sense based on this,
                                              and I would then also be
                                              fine with changing the
                                              MUST to a SHOULD. Perhaps
                                              we can state this
                                              principle upfront.</p>
                                            <p class="MsoNormal">I like
                                              the idea of stating that
                                              principle up front. SHOULD
                                              would be sufficient
                                              resolution for the burst
                                              size issue. </p>
                                            <p class="MsoNormal"> </p>
                                            <div
style="border-right:none;border-bottom:none;border-left:none;border-top:1pt
                                              solid
                                              rgb(225,225,225);padding:3pt
                                              0in 0in">
                                              <p class="MsoNormal"><b>From:</b>
                                                QUIC &lt;<a
                                                  href="mailto:quic-bounces@ietf.org"
                                                  rel="noreferrer"
                                                  target="_blank"
                                                  moz-do-not-send="true">quic-bounces@ietf.org</a>&gt;
                                                <b>On Behalf Of </b>
                                                Jana Iyengar<br>
                                                <b>Sent:</b> Friday,
                                                July 17, 2020 7:18 PM<br>
                                                <b>To:</b> QUIC WG &lt;<a
href="mailto:quic@ietf.org" rel="noreferrer" target="_blank"
                                                  moz-do-not-send="true">quic@ietf.org</a>&gt;<br>
                                                <b>Subject:</b>
                                                [EXTERNAL] Re: WGLC
                                                review of
                                                draft-ietf-quic-recovery-29</p>
                                            </div>
                                            <p class="MsoNormal"> </p>
                                            <div>
                                              <p class="MsoNormal">There's
                                                a protocol question and
                                                there's a question of
                                                endpoint behavior. In
                                                terms of the protocol
                                                itself, yes, there's no
                                                real need to distinguish
                                                between Internet and DC
                                                environments; we've
                                                tried to ensure that the
                                                protocol can be used
                                                broadly. My point was
                                                that the constants in
                                                the spec were based on
                                                what we believe to be
                                                true for the public
                                                Internet, and not for DC
                                                environments.</p>
                                              <div>
                                                <p class="MsoNormal"> </p>
                                              </div>
                                              <div>
                                                <p class="MsoNormal">That
                                                  said, perhaps I was a
                                                  bit too hasty. IW10
                                                  and InitialRTT values
                                                  are the others I was
                                                  thinking about, but
                                                  those
                                                  are recommendations in
                                                  the spec, not
                                                  requirements. And as
                                                  Ian notes, there's no
                                                  minimum timeout
                                                  anymore.</p>
                                              </div>
                                              <div>
                                                <p class="MsoNormal"> </p>
                                              </div>
                                              <div>
                                                <p class="MsoNormal">Perhaps
                                                  we can have a
                                                  principle here:
                                                  recommendations that
                                                  are specific for
                                                  Internet use are just
                                                  that, and we use
                                                  SHOULDs for those. </p>
                                              </div>
                                            </div>
                                          </div>
                                        </div>
                                      </blockquote>
                                    </div>
                                  </blockquote>
                                </div>
                              </div>
                            </blockquote>
                          </div>
                        </blockquote>
                      </div>
                    </div>
                  </div>
                </blockquote>
                I don't agree, see below.<br>
                <blockquote type="cite">
                  <div dir="auto">
                    <div dir="auto">
                      <div class="gmail_quote">
                        <blockquote class="gmail_quote"
                          style="margin:0px 0px 0px
                          0.8ex;border-left:1px solid
                          rgb(204,204,204);padding-left:1ex">
                          <div class="gmail_quote">
                            <blockquote class="gmail_quote"
                              style="margin:0px 0px 0px
                              0.8ex;border-left:1px solid
                              rgb(204,204,204);padding-left:1ex">
                              <div dir="ltr">
                                <div class="gmail_quote">
                                  <blockquote class="gmail_quote"
                                    style="margin:0px 0px 0px
                                    0.8ex;border-left:1px solid
                                    rgb(204,204,204);padding-left:1ex">
                                    <div class="gmail_quote">
                                      <blockquote class="gmail_quote"
                                        style="margin:0px 0px 0px
                                        0.8ex;border-left:1px solid
                                        rgb(204,204,204);padding-left:1ex">
                                        <div lang="EN-US">
                                          <div>
                                            <div>
                                              <div>
                                                <p class="MsoNormal">IW10
                                                  makes sense based on
                                                  this, and I would then
                                                  also be fine with
                                                  changing the MUST to a
                                                  SHOULD. Perhaps we can
                                                  state this principle
                                                  upfront.</p>
                                              </div>
                                              <div>
                                                <p class="MsoNormal"> </p>
                                              </div>
                                              <div>
                                                <p class="MsoNormal">Ian,
                                                  I share your
                                                  hesitation that we
                                                  don't want to make a
                                                  distinction between
                                                  private and public
                                                  networks, but we
                                                  already allow for
                                                  implementations to do
                                                  that with a
                                                  different IW and
                                                  Initial RTT. Is it
                                                  different when talking
                                                  about burst limits?</p>
                                              </div>
                                              <div>
                                                <p class="MsoNormal"> </p>
                                              </div>
                                            </div>
                                            <p class="MsoNormal"> </p>
                                            <div>
                                              <div>
                                                <p class="MsoNormal">On
                                                  Fri, Jul 17, 2020 at
                                                  3:07 PM Jeremy Harris
                                                  &lt;<a
                                                    href="mailto:jgh@wizmail.org"
                                                    rel="noreferrer"
                                                    target="_blank"
                                                    moz-do-not-send="true">jgh@wizmail.org</a>&gt;
                                                  wrote:</p>
                                              </div>
                                              <blockquote>
                                                <p class="MsoNormal"
                                                  style="margin-bottom:12pt">On
                                                  08/07/2020 22:29,
                                                  Praveen
                                                  Balasubramanian wrote:<br>
                                                  &gt; Section 7.9<br>
                                                  &gt; "Implementations
                                                  MUST either use pacing
                                                  or another method to
                                                  limit such bursts to
                                                  the initial congestion
                                                  window; see Section
                                                  7.2."<br>
                                                  &gt; This seems to
                                                  preclude use of
                                                  segmentation offload
                                                  of sizes greater than
                                                  IW.. In datacenters we
                                                  routinely send bursts
                                                  that are higher
                                                  without causing loss.
                                                  The MUST here seems
                                                  unnecessary. It also
                                                  conflicts with the
                                                  RECOMMENDED in an
                                                  earlier sentence.<br>
                                                  <br>
                                                  There's a way of
                                                  satisfying both
                                                  desires: have the NIC
                                                  handle the<br>
                                                  pacing.<br>
                                                  -- <br>
                                                  Cheers,<br>
                                                    Jeremy</p>
                                              </blockquote>
                                            </div>
                                          </div>
                                        </div>
                                      </blockquote>
                                    </div>
                                  </blockquote>
                                </div>
                              </div>
                            </blockquote>
                          </div>
                        </blockquote>
                      </div>
                    </div>
                  </div>
                </blockquote>
                <p><br>
                </p>
                <pre>I am unsure that trying to differentiate DC from ISP-Edge from Enterprise Server
or anything else will help in the spec. Sure, guidance may differ - but I'd like
to think (???) the IETF Spec describes the "Internet case, which
is expected to be good choices for most, but not all environments... and if a system distributes
functions within your own network segment then that's your decision - and yes,
and doing this in NICs would be great ... although NICs also can generate bursts 
when transports pace at a higher level... 

The pacing/burst-limiting could happen in various ways by various actors, but
that's not the way transport Specs are written, I thought that's why we ended-up with 
"other methods".

For me at least, it was a conscious decision to not to explicitly make this "10 packets", 
because an endpoint sender that made an informed decision to use a larger IW 
has at the same time decided to configure in a way that expects the network path can safely 
support this burst size. I expect this matters most when the
connection sending rate is low (see below). But we missed something.

I think the suggested addition from Ian, could really help a lot:
"unless the pacing system can't provide enough sending opportunities to send at the rate specified by the congestion controller."

- This would make the language less clear, but I think in a very good way, because I agree that as the connection **sending** rate increases (and hence also the CC understanding of
the path characteristics), the effect of bursts might be expected to be less significant. At higher rates queues in devices clear more quickly, and buffering 1mS (or whatever) of data, buffers more. 

Can we discuss that proposal more?

Gorry
</pre>
              </div>
            </blockquote>
          </div>
        </blockquote>
      </div>
    </blockquote>
  </body>
</html>

--------------1627F8D37727C9AE816986A9--


From nobody Mon Jul 27 10:28:06 2020
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 9AA7B3A1B3A for <quic@ietfa.amsl.com>; Mon, 27 Jul 2020 10:28:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 jqp-QhZK-XPr for <quic@ietfa.amsl.com>; Mon, 27 Jul 2020 10:27:58 -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 96A5B3A1B14 for <quic@ietf.org>; Mon, 27 Jul 2020 10:27:57 -0700 (PDT)
Received: by mail-lj1-x22d.google.com with SMTP id b25so18151556ljp.6 for <quic@ietf.org>; Mon, 27 Jul 2020 10:27:57 -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=fwBPUo4v2tSHXi5NV4KVbb9aentlFNdjiwhMdFKf7aw=; b=IacZASnio1d4cghnUnxUbuUAHVVQjm1WfiQW4JfIzgVK8mL84NpVc14ZDMPaUNkLCe 7th7dkmqy7Bjr6s0o0rjbejIzIWeq567/WAXcVz+63fascebx3PRoHweS/gozdfsZwkV 3TUopG5UHTebjsPYSgMi4D6GWWhKq5t+k3FM8LLrDAnx8VSvfB1GsxpTow19cGKY8pSR ZsAmi/nMe0h/MQgVsW16MmDwTMrdzkJd1c/qk4zMpbqK2orrCKnj8kIcb16csiVXaAfp WBVLUiyOhrqFDqbJFAXDCxRm192dKAPuH8dxRhq9nFfrwPPcNy0ID5wfpopx45Tez6p2 OsxQ==
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=fwBPUo4v2tSHXi5NV4KVbb9aentlFNdjiwhMdFKf7aw=; b=O+QCmbksK2x84SbrgPChW/rAsEa9UoN4IMMCvf8AAxcBeLzWxZsjFTjJPNxuOR1pve AckpSeDPih8ZjonsGYqkmPVnm35CkonP/LxaFgfkhEZ5MH98VaoDy+//EK8DtdlIc0we +G6PbVpeYVV+hntHHJjkoHgr2BWsM9wQp6yzh2AZIRLRrxG0dQPzbp6SRDKsWMOV9Qs3 7f+uGl6W0wdqFW0p3q+3xt+wSyylcNl/zE3vSB1KRR/dZwoWOuIQWUcNbVgZYnVdvniE QChydGSMoDaeBbI5KdUoRkpNTfWPHNDlbBRE9otiy7j9P04OemCjYTfduQo4apNh4KEd iJfw==
X-Gm-Message-State: AOAM530oRs9a9LSw0hfBL6cIoL9dRMMliTybWFe0QUc73XoufRbCUEJ5 odmBk7N+Gm+3e9l+zmLseZN9I/jgO/8MR2V043g=
X-Google-Smtp-Source: ABdhPJxkqPlyZQRx57st6U6pjYyZliLm7sfZ4k8fiImQecqnN+UmmhHzh+3bwvNcDKYOzv5Ur8hWY29csFx+uci8wz0=
X-Received: by 2002:a2e:808a:: with SMTP id i10mr9785550ljg.400.1595870875489;  Mon, 27 Jul 2020 10:27:55 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR00MB073663726DB5AFE6885D0A6BB6670@MN2PR00MB0736.namprd00.prod.outlook.com> <9f57b20d-2eba-b2b9-d8c8-48e019c8952a@wizmail.org> <CACpbDccrpHeP5PYGCZky+AN2gC9YSs5gbAzYr4Yrw1LpvHZNiA@mail.gmail.com> <CH2PR00MB07269A73542DBC8E51E95519B67A0@CH2PR00MB0726.namprd00.prod.outlook.com> <CAKcm_gMhRX3NxiW6Primy+UrY44ZahaSO+9kF5CeeN4=XqL2JQ@mail.gmail.com> <CAKKJt-fY92k5ym767GofK+DOMQs=x6dpkwkKOA1cpkUf8Xs+3A@mail.gmail.com> <CAKcm_gPyg4QM+mZq_-E-av=u_X4nCWwdDXEH6e9Sjz1d8scEyg@mail.gmail.com> <CAKKJt-fmqjXJEUHzFT0yBXE0sLvOPcnM-oCBDZfgZQNgerRt8g@mail.gmail.com> <114a0e70-fe91-9cf9-e4e8-5f7d074eac5c@erg.abdn.ac.uk> <CACpbDcdXVN4BU5Zs823GYXteXmZEEYaVv1Adv7FGdEgMqJTsOg@mail.gmail.com> <CAKcm_gPZN8aUREo=xZe4g0mPeubJvqJMUTWcuQQGOFAmRAFWwA@mail.gmail.com> <4bd2186e-21c5-a084-5ef6-aad2f64892b5@erg.abdn.ac.uk>
In-Reply-To: <4bd2186e-21c5-a084-5ef6-aad2f64892b5@erg.abdn.ac.uk>
From: Jana Iyengar <jri.ietf@gmail.com>
Date: Mon, 27 Jul 2020 10:27:44 -0700
Message-ID: <CACpbDce2eXDMFm2=WG9Dqt4Owe8KfWTWdbhNsNR-hZjJYTtY8A@mail.gmail.com>
Subject: Re: [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-29
To: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Cc: Ian Swett <ianswett@google.com>,  Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>,  Praveen Balasubramanian <pravb@microsoft.com>, QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a41b5205ab6fa4aa"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/sApnwI0lnO-ivLQDudhCs9YyS14>
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, 27 Jul 2020 17:28:04 -0000

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

Ian,

I've changed the text in PR to reflect your suggestion in the discussion
here: https://github.com/quicwg/base-drafts/pull/3936.

- jana

On Mon, Jul 27, 2020 at 7:29 AM Gorry Fairhurst <gorry@erg.abdn.ac.uk>
wrote:

>
> On 27/07/2020 15:06, Ian Swett wrote:
>
> For me, two things make "MUST, unless" or something along those lines
> preferable for me.
> 1) Infinite limits make me concerned.
> 2) QUIC doesn't specify Slow Start After Idle and to me that seems safe
> only because it requires pacing and/or limiting bursts.
>
> But I agree the difference between "MUST unless" and SHOULD is small, so =
I
> think this is a case for adding some extra text about why it's not a stri=
ct
> MUST.
>
> PS: I'll get back to the PR today, sorry for the delay.
>
> Great. I'll look forward to reading that new text.
>
> On Fri, Jul 24, 2020 at 9:42 PM Jana Iyengar <jri.ietf@gmail.com> wrote:
>
>> Gorry,
>>
>> That's not the only case where you don't want to pace. If I know (and I
>> have a production network where this is true) that the network can absor=
b a
>> larger burst. What is the argument to make this a MUST when even the val=
ue
>> of the Initial Window (of 10) is a SHOULD?
>>
>> - jana
>>
>>
> In answer to Jana, if you know the path has specific capabilities - which
> is pretty much what I'd expect in an DC or any other "constrained
> environment", the normal Internet guidance isn't necessarily appropiate.
> Generally that is not what IETF specs target.
>
> Gorry
>
> On Thu, Jul 23, 2020 at 2:07 AM Gorry Fairhurst <gorry@erg.abdn.ac.uk>
>> wrote:
>>
>>> I'd like to argue a little more for something like the current text we
>>> arrived at:
>>>
>>> "Implementations MUST either
>>>    use pacing or another method to limit such bursts to the initial
>>>    congestion window;"
>>>
>>> I've been watching, and have comments see below:
>>>
>>>
>>> On 20/07/2020 23:11, Spencer Dawkins at IETF wrote:
>>>
>>> Hi, Ian,
>>>
>>> On Mon, Jul 20, 2020, 16:33 Ian Swett <ianswett@google.com> wrote:
>>>
>>>> Most of the items which I felt were somewhat deployment-specific
>>>> constants(ie: Initial Window and Initial RTT) are 'RECOMMENDED' in the
>>>> current recovery draft, so I thought it'd be preferable to keep that
>>>> convention.
>>>>
>>>
>>> Thanks for helping me understand - this is a stylistic change.
>>>
>>> I've had a couple of conversations outside of QUIC recently with people
>>> who were interpreting the two terms somewhat differently, so thought it=
 a
>>> good time to ask.
>>>
>>> Best,
>>>
>>> Spencer
>>>
>>>>
>>>> On Mon, Jul 20, 2020 at 5:30 PM Spencer Dawkins at IETF <
>>>> spencerdawkins.ietf@gmail.com> wrote:
>>>>
>>>>> Hi, Ian,
>>>>>
>>>>> On Mon, Jul 20, 2020 at 11:49 AM Ian Swett <ianswett=3D
>>>>> 40google.com@dmarc.ietf.org> wrote:
>>>>>
>>>>>> I think it's ok to include burst limits in the set of things we
>>>>>> expect may be different in DCs, but if we do that, I'd prefer to use=
 the
>>>>>> RECOMMENDED rather than SHOULD,
>>>>>>
>>>>>
>>>>> Aren't RECOMMENDED and SHOULD equivalent in
>>>>> https://tools.ietf.org/html/rfc2119?
>>>>>
>>>>> Or am I misunderstanding your point?
>>>>>
>>>>> 3 <https://tools.ietf.org/html/rfc2119#section-3>. SHOULD   This word=
, or the adjective "RECOMMENDED", mean that there
>>>>>    may exist valid reasons in particular circumstances to ignore a
>>>>>    particular item, but the full implications must be understood and
>>>>>    carefully weighed before choosing a different course.
>>>>>
>>>>>
>>>>> Best,
>>>>>
>>>>> Spencer
>>>>>
>>>>> since there are a number of SHOULDs which I believe apply both to the
>>>>>> public internet and to DCs.  Then we could add a note at the top abo=
ut how
>>>>>> there are some values which are RECOMMENDED, including X, Y and Z, a=
nd
>>>>>> those recommendations are expected to be good choices for most, but =
not all
>>>>>> environments.
>>>>>>
>>>>>> In terms of text, I'd suggest taking Neal's suggestion and dropping
>>>>>> an explicit mention of the public internet:
>>>>>>
>>>>>> Implementations MUST either use pacing or another method to limit su=
ch bursts.
>>>>>>
>>>>>> It is RECOMMENDED that implementations limit bursts to the initial c=
ongestion window; see Section 7.2 <https://nam06.safelinks.protection.outlo=
ok.com/?url=3Dhttps%3A%2F%2Ftools.ietf.org%2Fhtml%2Fdraft-ietf-quic-recover=
y-29%23section-7.2&data=3D02%7C01%7Cpravb%40microsoft.com%7C9df3e5f4f0ca4e5=
86f0908d824e0a3ad%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C637299894526=
657906&sdata=3Dze%2F7SpKUbrdgwI6m%2BS6uEGSBgc2NapVtPn9vkOYFjVs%3D&reserved=
=3D0>.
>>>>>>
>>>>>>
>>>>>> On Sun, Jul 19, 2020 at 4:08 PM Praveen Balasubramanian <pravb=3D
>>>>>> 40microsoft.com@dmarc.ietf.org> wrote:
>>>>>>
>>>>>>> >> There's a way of satisfying both desires: have the NIC handle th=
e
>>>>>>> pacing.
>>>>>>>
>>>>>>> Yes letting the NIC handle pacing will make improve CPU efficiency
>>>>>>> and improve accuracy due to fine grained hardware timers. But that=
=E2=80=99s in the
>>>>>>> future. Today=E2=80=99s NICs don=E2=80=99t pace large send offloads=
 for TCP or UDP.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> >> Perhaps we can have a principle here: recommendations that are
>>>>>>> specific for Internet use are just that, and we use SHOULDs for tho=
se. IW10
>>>>>>> makes sense based on this, and I would then also be fine with chang=
ing the
>>>>>>> MUST to a SHOULD. Perhaps we can state this principle upfront.
>>>>>>>
>>>>>>> I like the idea of stating that principle up front. SHOULD would be
>>>>>>> sufficient resolution for the burst size issue.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> *From:* QUIC <quic-bounces@ietf.org> *On Behalf Of * Jana Iyengar
>>>>>>> *Sent:* Friday, July 17, 2020 7:18 PM
>>>>>>> *To:* QUIC WG <quic@ietf.org>
>>>>>>> *Subject:* [EXTERNAL] Re: WGLC review of draft-ietf-quic-recovery-2=
9
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> There's a protocol question and there's a question of endpoint
>>>>>>> behavior. In terms of the protocol itself, yes, there's no real nee=
d to
>>>>>>> distinguish between Internet and DC environments; we've tried to en=
sure
>>>>>>> that the protocol can be used broadly. My point was that the consta=
nts in
>>>>>>> the spec were based on what we believe to be true for the public In=
ternet,
>>>>>>> and not for DC environments.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> That said, perhaps I was a bit too hasty. IW10 and InitialRTT value=
s
>>>>>>> are the others I was thinking about, but those are recommendations =
in the
>>>>>>> spec, not requirements. And as Ian notes, there's no minimum timeou=
t
>>>>>>> anymore.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Perhaps we can have a principle here: recommendations that are
>>>>>>> specific for Internet use are just that, and we use SHOULDs for tho=
se.
>>>>>>>
>>>>>> I don't agree, see below.
>>>
>>> IW10 makes sense based on this, and I would then also be fine with
>>>>>>> changing the MUST to a SHOULD. Perhaps we can state this principle =
upfront.
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Ian, I share your hesitation that we don't want to make a
>>>>>>> distinction between private and public networks, but we already all=
ow for
>>>>>>> implementations to do that with a different IW and Initial RTT. Is =
it
>>>>>>> different when talking about burst limits?
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> On Fri, Jul 17, 2020 at 3:07 PM Jeremy Harris <jgh@wizmail.org>
>>>>>>> wrote:
>>>>>>>
>>>>>>> On 08/07/2020 22:29, Praveen Balasubramanian wrote:
>>>>>>> > Section 7.9
>>>>>>> > "Implementations MUST either use pacing or another method to limi=
t
>>>>>>> such bursts to the initial congestion window; see Section 7.2."
>>>>>>> > This seems to preclude use of segmentation offload of sizes
>>>>>>> greater than IW.. In datacenters we routinely send bursts that are =
higher
>>>>>>> without causing loss. The MUST here seems unnecessary. It also conf=
licts
>>>>>>> with the RECOMMENDED in an earlier sentence.
>>>>>>>
>>>>>>> There's a way of satisfying both desires: have the NIC handle the
>>>>>>> pacing.
>>>>>>> --
>>>>>>> Cheers,
>>>>>>>   Jeremy
>>>>>>>
>>>>>>>
>>> I am unsure that trying to differentiate DC from ISP-Edge from Enterpri=
se Server
>>> or anything else will help in the spec. Sure, guidance may differ - but=
 I'd like
>>> to think (???) the IETF Spec describes the "Internet case, which
>>> is expected to be good choices for most, but not all environments... an=
d if a system distributes
>>> functions within your own network segment then that's your decision - a=
nd yes,
>>> and doing this in NICs would be great ... although NICs also can genera=
te bursts
>>> when transports pace at a higher level...
>>>
>>> The pacing/burst-limiting could happen in various ways by various actor=
s, but
>>> that's not the way transport Specs are written, I thought that's why we=
 ended-up with
>>> "other methods".
>>>
>>> For me at least, it was a conscious decision to not to explicitly make =
this "10 packets",
>>> because an endpoint sender that made an informed decision to use a larg=
er IW
>>> has at the same time decided to configure in a way that expects the net=
work path can safely
>>> support this burst size. I expect this matters most when the
>>> connection sending rate is low (see below). But we missed something.
>>>
>>> I think the suggested addition from Ian, could really help a lot:
>>> "unless the pacing system can't provide enough sending opportunities to=
 send at the rate specified by the congestion controller."
>>>
>>> - This would make the language less clear, but I think in a very good w=
ay, because I agree that as the connection **sending** rate increases (and =
hence also the CC understanding of
>>> the path characteristics), the effect of bursts might be expected to be=
 less significant. At higher rates queues in devices clear more quickly, an=
d buffering 1mS (or whatever) of data, buffers more.
>>>
>>> Can we discuss that proposal more?
>>>
>>> Gorry
>>>
>>>

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

<div dir=3D"ltr">Ian,<div><br></div><div>I&#39;ve changed the text in PR to=
 reflect your suggestion in the discussion here:=C2=A0<a href=3D"https://gi=
thub.com/quicwg/base-drafts/pull/3936">https://github.com/quicwg/base-draft=
s/pull/3936</a>.</div><div><br></div><div>- jana</div></div><br><div class=
=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jul 27, 2020=
 at 7:29 AM Gorry Fairhurst &lt;<a href=3D"mailto:gorry@erg.abdn.ac.uk">gor=
ry@erg.abdn.ac.uk</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">
 =20
   =20
 =20
  <div>
    <p><br>
    </p>
    <div>On 27/07/2020 15:06, Ian Swett wrote:<br>
    </div>
    <blockquote type=3D"cite">
     =20
      <div dir=3D"ltr">
        <div>For me, two things make &quot;MUST, unless&quot; or something =
along
          those lines preferable for me.</div>
        <div>1) Infinite limits make me concerned.</div>
        <div>2) QUIC doesn&#39;t specify Slow Start After Idle and to me
          that seems safe only because it requires pacing and/or
          limiting bursts.</div>
        <div><br>
        </div>
        <div>But I agree the difference between &quot;MUST unless&quot; and=
 SHOULD
          is small, so I think this is a case for adding some extra text
          about why it&#39;s not a strict MUST.</div>
        <div><br>
        </div>
        <div>PS: I&#39;ll get back to the PR today, sorry for the delay.</d=
iv>
      </div>
      <br>
    </blockquote>
    <p>Great. I&#39;ll look forward to reading that new text.</p>
    <blockquote type=3D"cite">
      <div class=3D"gmail_quote">
        <div dir=3D"ltr" class=3D"gmail_attr">On Fri, Jul 24, 2020 at 9:42
          PM Jana Iyengar &lt;<a href=3D"mailto:jri.ietf@gmail.com" target=
=3D"_blank">jri.ietf@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">Gorry,
            <div><br>
            </div>
            <div>That&#39;s not the only case where you don&#39;t want to p=
ace.
              If I know (and I have a production network where this is
              true) that the network can absorb a larger burst. What is
              the argument to make this a MUST when even the value of
              the Initial Window (of 10) is a SHOULD?</div>
            <div><br>
            </div>
            <div>- jana</div>
          </div>
          <br>
        </blockquote>
      </div>
    </blockquote>
    <br>
    <p>In answer to Jana, if you know the path has specific capabilities
      - which is pretty much what I&#39;d expect in an DC or any other
      &quot;constrained environment&quot;, the normal Internet guidance isn=
&#39;t
      necessarily appropiate. Generally that is not what IETF specs
      target. <br>
    </p>
    <p>Gorry</p>
    <blockquote type=3D"cite">
      <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 class=3D"gmail_quote">
            <div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jul 23, 2020 at
              2:07 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;border-left:1px solid rgb(204,204,204);padding-left:1ex">
              <div>
                <p>I&#39;d like to argue a little more for something like
                  the current text we arrived at:</p>
                <pre>&quot;Implementations MUST either
   use pacing or another method to limit such bursts to the initial
   congestion window;&quot;

I&#39;ve been watching, and have comments see below:

</pre>
                <div>On 20/07/2020 23:11, Spencer Dawkins at IETF wrote:<br=
>
                </div>
                <blockquote type=3D"cite">
                  <div dir=3D"auto">
                    <div>Hi, Ian,<br>
                      <br>
                      <div class=3D"gmail_quote">
                        <div dir=3D"ltr" class=3D"gmail_attr">On Mon, Jul
                          20, 2020, 16:33 Ian Swett &lt;<a href=3D"mailto:i=
answett@google.com" target=3D"_blank">ianswett@google.com</a>&gt;
                          wrote:<br>
                        </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 dir=3D"ltr">Most of the items which I felt
                            were somewhat deployment-specific
                            constants(ie: Initial Window and Initial
                            RTT) are &#39;RECOMMENDED&#39; in the current
                            recovery draft, so I thought it&#39;d be
                            preferable to keep that convention.</div>
                        </blockquote>
                      </div>
                    </div>
                    <div dir=3D"auto"><br>
                    </div>
                    <div dir=3D"auto">Thanks for helping me understand -
                      this is a stylistic change.</div>
                    <div dir=3D"auto"><br>
                    </div>
                    <div dir=3D"auto">I&#39;ve had a couple of conversation=
s
                      outside of QUIC recently with people who were
                      interpreting the two terms somewhat differently,
                      so thought it a good time to ask.</div>
                    <div dir=3D"auto"><br>
                    </div>
                    <div dir=3D"auto">Best,</div>
                    <div dir=3D"auto"><br>
                    </div>
                    <div dir=3D"auto">Spencer</div>
                    <div dir=3D"auto">
                      <div 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"><=
br>
                          <div class=3D"gmail_quote">
                            <div dir=3D"ltr" class=3D"gmail_attr">On Mon,
                              Jul 20, 2020 at 5:30 PM Spencer Dawkins at
                              IETF &lt;<a href=3D"mailto:spencerdawkins.iet=
f@gmail.com" rel=3D"noreferrer" target=3D"_blank">spencerdawkins.ietf@gmail=
.com</a>&gt;
                              wrote:<br>
                            </div>
                            <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 dir=3D"ltr">
                                <div dir=3D"ltr">Hi, Ian,=C2=A0</div>
                                <br>
                                <div class=3D"gmail_quote">
                                  <div dir=3D"ltr" class=3D"gmail_attr">On
                                    Mon, Jul 20, 2020 at 11:49 AM Ian
                                    Swett &lt;ianswett=3D<a href=3D"mailto:=
40google.com@dmarc.ietf.org" rel=3D"noreferrer" target=3D"_blank">40google.=
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">
                                    <div dir=3D"ltr">I think it&#39;s ok to
                                      include burst limits in the set of
                                      things we expect may be different
                                      in DCs, but if we do that, I&#39;d
                                      prefer to use the RECOMMENDED
                                      rather than SHOULD,</div>
                                  </blockquote>
                                  <div><br>
                                  </div>
                                  <div>Aren&#39;t RECOMMENDED and SHOULD
                                    equivalent in=C2=A0 <a href=3D"https://=
tools.ietf.org/html/rfc2119" rel=3D"noreferrer" target=3D"_blank">https://t=
ools.ietf.org/html/rfc2119</a>?=C2=A0</div>
                                  <div><br>
                                  </div>
                                  <div>Or am I misunderstanding your
                                    point?</div>
                                  <div><br>
                                  </div>
                                  <div>
                                    <pre style=3D"margin-top:0px;margin-bot=
tom:0px;color:rgb(0,0,0)"><font size=3D"4"><span style=3D"display:inline;fo=
nt-weight:bold"><h2 style=3D"display:inline"><a name=3D"m_84096080676026832=
70_m_-138022109493467158_m_6172066709575264695_m_-7104407681243286268_m_-56=
1907519085294557_section-3" href=3D"https://tools.ietf.org/html/rfc2119#sec=
tion-3" style=3D"color:black;text-decoration-line:none" rel=3D"noreferrer" =
target=3D"_blank">3</a>. SHOULD  </h2></span> This word, or the adjective &=
quot;RECOMMENDED&quot;, mean that there
   may exist valid reasons in particular circumstances to ignore a
   particular item, but the full implications must be understood and
   carefully weighed before choosing a different course.</font></pre>
                                  </div>
                                  <div>=C2=A0</div>
                                  <div>Best,</div>
                                  <div><br>
                                  </div>
                                  <div>Spencer</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"> since there are a
                                      number of SHOULDs which I
                                      believe=C2=A0apply both to the public
                                      internet and to DCs.=C2=A0 Then we
                                      could add a note at the top about
                                      how there are some values which
                                      are RECOMMENDED, including X, Y
                                      and Z, and those recommendations
                                      are expected to be good choices
                                      for most, but not all
                                      environments.
                                      <div><br>
                                      </div>
                                      <div>In terms of text, I&#39;d sugges=
t
                                        taking Neal&#39;s suggestion and
                                        dropping an explicit mention of
                                        the public internet:</div>
                                      <div><br>
                                      </div>
                                      <div>
                                        <pre style=3D"white-space:pre-wrap;=
margin:0in;font-size:10pt;font-family:&quot;Courier New&quot;;break-before:=
page"><span style=3D"color:black">Implementations MUST either use pacing or=
 another method to limit such bursts.</span></pre>
                                        <pre style=3D"white-space:pre-wrap;=
margin:0in;font-size:10pt;font-family:&quot;Courier New&quot;;break-before:=
page"><span style=3D"color:black">It is RECOMMENDED that implementations li=
mit bursts to the initial </span>congestion window; see <a href=3D"https://=
nam06.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Ftools.ietf.org%=
2Fhtml%2Fdraft-ietf-quic-recovery-29%23section-7.2&amp;data=3D02%7C01%7Cpra=
vb%40microsoft.com%7C9df3e5f4f0ca4e586f0908d824e0a3ad%7C72f988bf86f141af91a=
b2d7cd011db47%7C1%7C0%7C637299894526657906&amp;sdata=3Dze%2F7SpKUbrdgwI6m%2=
BS6uEGSBgc2NapVtPn9vkOYFjVs%3D&amp;reserved=3D0" style=3D"font-size:10pt" r=
el=3D"noreferrer" target=3D"_blank">Section 7.2</a><span style=3D"font-size=
:10pt;color:black">.</span></pre>
                                      </div>
                                    </div>
                                    <br>
                                    <div class=3D"gmail_quote">
                                      <div dir=3D"ltr" class=3D"gmail_attr"=
>On
                                        Sun, Jul 19, 2020 at 4:08 PM
                                        Praveen Balasubramanian
                                        &lt;pravb=3D<a href=3D"mailto:40mic=
rosoft.com@dmarc.ietf.org" rel=3D"noreferrer" target=3D"_blank">40microsoft=
.com@dmarc.ietf.org</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>
                                            <p class=3D"MsoNormal">&gt;&gt;
                                              There&#39;s a way of
                                              satisfying both desires:
                                              have the NIC handle the
                                              pacing.</p>
                                            <p class=3D"MsoNormal">Yes
                                              letting the NIC handle
                                              pacing will make improve
                                              CPU efficiency and improve
                                              accuracy due to fine
                                              grained hardware timers.
                                              But that=E2=80=99s in the fut=
ure.
                                              Today=E2=80=99s NICs don=E2=
=80=99t pace
                                              large send offloads for
                                              TCP or UDP.</p>
                                            <p class=3D"MsoNormal">=C2=A0</=
p>
                                            <p class=3D"MsoNormal">&gt;&gt;
                                              Perhaps we can have a
                                              principle here:
                                              recommendations that are
                                              specific for Internet use
                                              are just that, and we use
                                              SHOULDs for those. IW10
                                              makes sense based on this,
                                              and I would then also be
                                              fine with changing the
                                              MUST to a SHOULD. Perhaps
                                              we can state this
                                              principle upfront.</p>
                                            <p class=3D"MsoNormal">I like
                                              the idea of stating that
                                              principle up front. SHOULD
                                              would be sufficient
                                              resolution for the burst
                                              size issue. </p>
                                            <p class=3D"MsoNormal">=C2=A0</=
p>
                                            <div style=3D"border-right:none=
;border-bottom:none;border-left:none;border-top:1pt solid rgb(225,225,225);=
padding:3pt 0in 0in">
                                              <p class=3D"MsoNormal"><b>Fro=
m:</b>
                                                QUIC &lt;<a href=3D"mailto:=
quic-bounces@ietf.org" rel=3D"noreferrer" target=3D"_blank">quic-bounces@ie=
tf.org</a>&gt;
                                                <b>On Behalf Of </b>
                                                Jana Iyengar<br>
                                                <b>Sent:</b> Friday,
                                                July 17, 2020 7:18 PM<br>
                                                <b>To:</b> QUIC WG &lt;<a h=
ref=3D"mailto:quic@ietf.org" rel=3D"noreferrer" target=3D"_blank">quic@ietf=
.org</a>&gt;<br>
                                                <b>Subject:</b>
                                                [EXTERNAL] Re: WGLC
                                                review of
                                                draft-ietf-quic-recovery-29=
</p>
                                            </div>
                                            <p class=3D"MsoNormal">=C2=A0</=
p>
                                            <div>
                                              <p class=3D"MsoNormal">There&=
#39;s
                                                a protocol question and
                                                there&#39;s a question of
                                                endpoint behavior. In
                                                terms of the protocol
                                                itself, yes, there&#39;s no
                                                real need to distinguish
                                                between Internet and DC
                                                environments; we&#39;ve
                                                tried to ensure that the
                                                protocol can be used
                                                broadly. My point was
                                                that the constants=C2=A0in
                                                the spec were based on
                                                what we believe to be
                                                true for the public
                                                Internet, and not for DC
                                                environments.</p>
                                              <div>
                                                <p class=3D"MsoNormal">=C2=
=A0</p>
                                              </div>
                                              <div>
                                                <p class=3D"MsoNormal">That
                                                  said, perhaps I was a
                                                  bit too hasty. IW10
                                                  and InitialRTT values
                                                  are the others I was
                                                  thinking about, but
                                                  those
                                                  are=C2=A0recommendations =
in
                                                  the spec, not
                                                  requirements. And as
                                                  Ian notes, there&#39;s no
                                                  minimum timeout
                                                  anymore.</p>
                                              </div>
                                              <div>
                                                <p class=3D"MsoNormal">=C2=
=A0</p>
                                              </div>
                                              <div>
                                                <p class=3D"MsoNormal">Perh=
aps
                                                  we can have a
                                                  principle here:
                                                  recommendations that
                                                  are specific for
                                                  Internet use are just
                                                  that, and we use
                                                  SHOULDs for those. </p>
                                              </div>
                                            </div>
                                          </div>
                                        </div>
                                      </blockquote>
                                    </div>
                                  </blockquote>
                                </div>
                              </div>
                            </blockquote>
                          </div>
                        </blockquote>
                      </div>
                    </div>
                  </div>
                </blockquote>
                I don&#39;t agree, see below.<br>
                <blockquote type=3D"cite">
                  <div dir=3D"auto">
                    <div dir=3D"auto">
                      <div 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 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 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 class=3D"gmail_quote">
                                      <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>
                                            <div>
                                              <div>
                                                <p class=3D"MsoNormal">IW10
                                                  makes sense based on
                                                  this, and I would then
                                                  also be fine with
                                                  changing the MUST to a
                                                  SHOULD. Perhaps we can
                                                  state this principle
                                                  upfront.</p>
                                              </div>
                                              <div>
                                                <p class=3D"MsoNormal">=C2=
=A0</p>
                                              </div>
                                              <div>
                                                <p class=3D"MsoNormal">Ian,
                                                  I share your
                                                  hesitation that we
                                                  don&#39;t want to make a
                                                  distinction between
                                                  private and public
                                                  networks,=C2=A0but we
                                                  already allow for
                                                  implementations to do
                                                  that with a
                                                  different=C2=A0IW and
                                                  Initial RTT. Is it
                                                  different when talking
                                                  about burst limits?</p>
                                              </div>
                                              <div>
                                                <p class=3D"MsoNormal">=C2=
=A0</p>
                                              </div>
                                            </div>
                                            <p class=3D"MsoNormal">=C2=A0</=
p>
                                            <div>
                                              <div>
                                                <p class=3D"MsoNormal">On
                                                  Fri, Jul 17, 2020 at
                                                  3:07 PM Jeremy Harris
                                                  &lt;<a href=3D"mailto:jgh=
@wizmail.org" rel=3D"noreferrer" target=3D"_blank">jgh@wizmail.org</a>&gt;
                                                  wrote:</p>
                                              </div>
                                              <blockquote>
                                                <p class=3D"MsoNormal" styl=
e=3D"margin-bottom:12pt">On
                                                  08/07/2020 22:29,
                                                  Praveen
                                                  Balasubramanian wrote:<br=
>
                                                  &gt; Section 7.9<br>
                                                  &gt; &quot;Implementation=
s
                                                  MUST either use pacing
                                                  or another method to
                                                  limit such bursts to
                                                  the initial congestion
                                                  window; see Section
                                                  7.2.&quot;<br>
                                                  &gt; This seems to
                                                  preclude use of
                                                  segmentation offload
                                                  of sizes greater than
                                                  IW.. In datacenters we
                                                  routinely send bursts
                                                  that are higher
                                                  without causing loss.
                                                  The MUST here seems
                                                  unnecessary. It also
                                                  conflicts with the
                                                  RECOMMENDED in an
                                                  earlier sentence.<br>
                                                  <br>
                                                  There&#39;s a way of
                                                  satisfying both
                                                  desires: have the NIC
                                                  handle the<br>
                                                  pacing.<br>
                                                  -- <br>
                                                  Cheers,<br>
                                                  =C2=A0 Jeremy</p>
                                              </blockquote>
                                            </div>
                                          </div>
                                        </div>
                                      </blockquote>
                                    </div>
                                  </blockquote>
                                </div>
                              </div>
                            </blockquote>
                          </div>
                        </blockquote>
                      </div>
                    </div>
                  </div>
                </blockquote>
                <p><br>
                </p>
                <pre>I am unsure that trying to differentiate DC from ISP-E=
dge from Enterprise Server
or anything else will help in the spec. Sure, guidance may differ - but I&#=
39;d like
to think (???) the IETF Spec describes the &quot;Internet case, which
is expected to be good choices for most, but not all environments... and if=
 a system distributes
functions within your own network segment then that&#39;s your decision - a=
nd yes,
and doing this in NICs would be great ... although NICs also can generate b=
ursts=20
when transports pace at a higher level...=20

The pacing/burst-limiting could happen in various ways by various actors, b=
ut
that&#39;s not the way transport Specs are written, I thought that&#39;s wh=
y we ended-up with=20
&quot;other methods&quot;.

For me at least, it was a conscious decision to not to explicitly make this=
 &quot;10 packets&quot;,=20
because an endpoint sender that made an informed decision to use a larger I=
W=20
has at the same time decided to configure in a way that expects the network=
 path can safely=20
support this burst size. I expect this matters most when the
connection sending rate is low (see below). But we missed something.

I think the suggested addition from Ian, could really help a lot:
&quot;unless the pacing system can&#39;t provide enough sending opportuniti=
es to send at the rate specified by the congestion controller.&quot;

- This would make the language less clear, but I think in a very good way, =
because I agree that as the connection **sending** rate increases (and henc=
e also the CC understanding of
the path characteristics), the effect of bursts might be expected to be les=
s significant. At higher rates queues in devices clear more quickly, and bu=
ffering 1mS (or whatever) of data, buffers more.=20

Can we discuss that proposal more?

Gorry
</pre>
              </div>
            </blockquote>
          </div>
        </blockquote>
      </div>
    </blockquote>
  </div>

</blockquote></div>

--000000000000a41b5205ab6fa4aa--


From nobody Tue Jul 28 00:04:36 2020
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 3C5EA3A0861 for <quic@ietfa.amsl.com>; Tue, 28 Jul 2020 00:04:34 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=eggert.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 vGq2hjJJ-8Cs for <quic@ietfa.amsl.com>; Tue, 28 Jul 2020 00:04:33 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 045A03A09EB for <quic@ietf.org>; Tue, 28 Jul 2020 00:04:32 -0700 (PDT)
Received: from [IPv6:2a00:ac00:4000:400:e077:d81a:af4b:b5a0] (unknown [IPv6:2a00:ac00:4000:400:e077:d81a:af4b:b5a0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id BCE3B612BBC for <quic@ietf.org>; Tue, 28 Jul 2020 10:04:24 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1595919864; bh=/J4xHen9wuxlZZQTQviDkoQf2sW0VrqNl9UFnHCXx44=; h=From:Reply-To:Subject:Date:To; b=UAY4W8lAIj7tik0aebEeSEycH8iAxoxjyUOQmgR1beipvPPv+ZmGfZXTQqrS1J3DW LOY7RZ2kNuMitFJI0NpWGNNNN7YSr7fvsP8uttRLEWaSxeryw01nnlNo+7aMbvoOY8 Miz+8oMUORWWe9UrHTY2Jy53RLD4C4/z5d97Qupo=
From: Lars Eggert <lars@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_E8EE5A89-045D-42C1-9A75-74C5E4B1DD96"; protocol="application/pgp-signature"; micalg=pgp-sha512
Reply-To: WG Chairs <quic-chairs@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: Wanted: Minute takers
Message-Id: <F5461A2C-70BA-4D88-BF04-2F86E1337F1B@eggert.org>
Date: Tue, 28 Jul 2020 10:04:24 +0300
To: QUIC WG <quic@ietf.org>
X-MailScanner-ID: BCE3B612BBC.A74AB
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/V7315HH_F1MihbwLP39SJf2mrIA>
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, 28 Jul 2020 07:04:35 -0000

--Apple-Mail=_E8EE5A89-045D-42C1-9A75-74C5E4B1DD96
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

Hi,

we're looking for some volunteers to minute tomorrow's WG meeting!

Thanks,
Lars

--Apple-Mail=_E8EE5A89-045D-42C1-9A75-74C5E4B1DD96
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAl8fzfgACgkQVLXDCb9w
wVcFtw//W2pRiSvFWS4Jw33HRI/2gJhhOWRyKEx1JtV1OxHRan8bb0qO62SaQykQ
MoxDP8rJgzC0zlQ4zwSC86uW6+VxnHpfET3tOAZ7O+AopvMYrD8Z5lBIMgNinye9
w59BGEI/1Ltj8reMrnCNcdHeSIGgIKMMcV2fn5em2NEcglJeGG+b8GFGuHbHj7YP
owZ9j8Pos/fJFrPy9qffnKEc6P5X4PFwyOW7yO+JAEqvVGN/s/iGJPWbBj2NyS9U
4ItKLdOvK7Vz6NBnStDf3FFWMRDChSCbC2iz/2S6xQY2jE9it5IDLulPImUl0v+D
YMfYLCITwZHBGfwm9SQrOcOqF3wGHEkQfEihGStsp4GZPRV1ySAXkXisJ4vVcb33
/JvyphIieY3Zy/3ludSensXmCsAWZ5RHDkqCNoaQjMnEYjdMblVWNzJSvXGk2on7
fSeukJ+rtEwrTCItF3FoO9PrgrJoqFjcr7AMFbszMOJRNvncsXE2TrDGcywW5T4u
yTUnnHcZHWyCX2UCjjIA4GQJ1T/It+sh0gmQiHpSR2gbDP8sZV6y76gI6kWUGcRs
D4K/ReRYnesdjtYlDnylmSrAhFusZ+NHUp2DqPbgIvsazu9nWdSVz9kXQbcK2kHk
FKDMw5ITmVTxhk9RJWvtOEDECfCM8mS5mu0lU7dncRAUchDIf7Q=
=Uq22
-----END PGP SIGNATURE-----

--Apple-Mail=_E8EE5A89-045D-42C1-9A75-74C5E4B1DD96--


From nobody Tue Jul 28 23:05:04 2020
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 A05BC3A0FEC for <quic@ietfa.amsl.com>; Tue, 28 Jul 2020 23:05:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=eggert.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 5HXevzVPBws6 for <quic@ietfa.amsl.com>; Tue, 28 Jul 2020 23:05:00 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 81E3C3A0FEA for <quic@ietf.org>; Tue, 28 Jul 2020 23:05:00 -0700 (PDT)
Received: from [IPv6:2a00:ac00:4000:400:d404:4033:1b4e:8603] (unknown [IPv6:2a00:ac00:4000:400:d404:4033:1b4e:8603]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id AC1CE642D6A for <quic@ietf.org>; Wed, 29 Jul 2020 09:04:52 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1596002692; bh=+hw6/TVT5LTda6ccY+VyPee87WkAjSpRUhaNTkG9Wr4=; h=From:Reply-To:Subject:Date:References:To:In-Reply-To; b=R9xuw+50i5LgLbZ81hU6iX11adwQ7c6ueYcYZB0NiWsOcsO1aHMSdpT6GobIwWw6i YDrkfe+bh5XH2L/IEphSdSmRKuAgvQAWCAznF/deUQNWEoiLxXzHaeNU8qMH6eYkD+ deEhpaquzjAIij6O51BD6XCLGjq774l5mOhCxs3w=
From: Lars Eggert <lars@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_87BA6252-4152-4EAC-880B-B75342B26645"; protocol="application/pgp-signature"; micalg=pgp-sha512
Reply-To: WG Chairs <quic-chairs@ietf.org>
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: Re: Wanted: Minute takers
Date: Wed, 29 Jul 2020 09:04:52 +0300
References: <F5461A2C-70BA-4D88-BF04-2F86E1337F1B@eggert.org>
To: QUIC WG <quic@ietf.org>
In-Reply-To: <F5461A2C-70BA-4D88-BF04-2F86E1337F1B@eggert.org>
Message-Id: <42547F0D-EA27-47D6-8A88-AB76737103F7@eggert.org>
X-MailScanner-ID: AC1CE642D6A.A3A2A
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/ri2FTtqtTi6nncZIeBHqHMtFh58>
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, 29 Jul 2020 06:05:02 -0000

--Apple-Mail=_87BA6252-4152-4EAC-880B-B75342B26645
Content-Transfer-Encoding: 7bit
Content-Type: text/plain;
	charset=us-ascii

	On 2020-7-28, at 10:04, Lars Eggert <lars@eggert.org> wrote:
> we're looking for some volunteers to minute tomorrow's WG meeting!

Still looking.

Thanks,
Lars

--Apple-Mail=_87BA6252-4152-4EAC-880B-B75342B26645
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAl8hEYQACgkQVLXDCb9w
wVck5g/+Lm7ENjzR9nrOGa+mLkpvR6wDwxId0CTlh+9FeXzIPOiJFX0KH686RH6N
5t+AVCOXn3J8lmK2E8l6fkyMavsy2QP0lV9gO/ugs6DqB8QZtkQ7835cr6Ny8Obc
IASq4QHc+2Hw1kkkIlYLoRUBladIl32nOarZoI4vSuOsZWrAyV0ggm+u1fJbuvZn
kTRgKwt7y0EHQnS5JJzfZYIDhLo3PtQ9PIFndA74QJzxDEPJ9AWhP3d+ugVWGU1t
eUUOJKej3CzSI1rKTxZ34qZEbEa909nNONkYr2qubqQdSjpZ4Ix+eSv8FZRJ4VSu
WqUbwEcaByrMbIU7ksy76DKN7ohemrAJ1SQNWjp3saBXhcx4/QSD2gZ5GztoXXM8
Qs3yn/gIEqRBjZkCjaNWM8EQnhI9tPix+h7CCmz8ujMp/T0eknXmdT17bJbnKbXC
6P3/02F0vy4JLchx78KnTx63Pt7kdDbDg/gr/yTBEm7D/ti0umiZ4UXVMMKODKB8
/XgWoZAQsc0C7j7RHF8eWuu9rTBNHwxCHxYZ6rXfHA5OrEKfIiDR4ktNJCero3+G
/L7EC8DN2FpKUzLZDGz2lyJHr4f3RxiAcSiCs04HvCkeBArDnQ62t0uYGKtFWBI7
OFX2CUDTANv/TNIwY/PzcvXrKRNGJ9xpB4I/bBIovGY0Lu/b9UI=
=rkmU
-----END PGP SIGNATURE-----

--Apple-Mail=_87BA6252-4152-4EAC-880B-B75342B26645--


From nobody Wed Jul 29 05:36:17 2020
Return-Path: <tim.jebb@bt.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 869DF3A0A4D for <quic@ietfa.amsl.com>; Wed, 29 Jul 2020 05:36:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.098
X-Spam-Level: 
X-Spam-Status: No, score=-1.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, MISSING_HEADERS=1.021, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=bt.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 gpMkqRiHQqzW for <quic@ietfa.amsl.com>; Wed, 29 Jul 2020 05:36:13 -0700 (PDT)
Received: from smtpe1.intersmtp.com (smtpe1.intersmtp.com [213.121.35.73]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id AD5DA3A0A49 for <quic@ietf.org>; Wed, 29 Jul 2020 05:36:12 -0700 (PDT)
Received: from tpw09926dag07e.domain1.systemhost.net (10.9.202.34) by BWP09926078.bt.com (10.36.82.109) with Microsoft SMTP Server (version=TLS1_2,  cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Wed, 29 Jul 2020 13:35:59 +0100
Received: from tpw09926dag13g.domain1.systemhost.net (10.9.212.29) by tpw09926dag07e.domain1.systemhost.net (10.9.202.34) with Microsoft SMTP Server (TLS) id 15.0.1395.4; Wed, 29 Jul 2020 13:36:09 +0100
Received: from bwp09926080.bt.com (10.36.82.111) by tpw09926dag13g.domain1.systemhost.net (10.9.212.29) with Microsoft SMTP Server (TLS) id 15.0.1395.4 via Frontend Transport; Wed, 29 Jul 2020 13:36:09 +0100
Received: from GBR01-LO2-obe.outbound.protection.outlook.com (104.47.21.53) by smtpe1.intersmtp.com (10.36.82.111) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384_P256) id 15.1.1713.5; Wed, 29 Jul 2020 13:36:07 +0100
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=SmUFgyXsIXP5VeKvnn80m1wuX8jmCgViNuSqkl/7nCdfeZABLOzmy3EwiJV3aDppG/ixVpg72YnYT3IFMONr0x4F9K1h09LegZj9nkFrNUt3EAUmh1Mz0FSTiOAccd72UMgSyC+V2ZBeR1B8ai/FhEQU/fSPFujP06tVbVqOSiOM3vjK7bMHjZU0hjpxkg/WX1c0HvrtzW859CioI4jOnGef4xqrqucDzjsOJc9zBayUa7QlmqgYptg5F9cBbDJb2OLgK0SfCgRxqWuEL9t033fRyjzd/oZSYi6loe+PUEfO/JlStVt9U2I4fCU11Ipvk3cyUfwQuWDEyBhHn9BrBQ==
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=s/PO47AX01/JJaJZA2feZvte5Oea8dfUNP/0kWzTrBc=; b=TNND5x9xNwPlsaH1qRYwOQJnEK7FVeXIsm/yV6WgTbB32vAKivWZA/44CcRqZEh/O/lENroCJR1r7A/RbBxqduF3BdepbH0Behj0KzYkRu97DkDyfUFq3sPL2YwdderbWrtBZ8apHaweviEejC4kxYvpleDIHge3119W06DmG5MYUYFaSFq8+3KSVnUtqnqN4wRlA31nwpreYWGUKqstWcZgoJswbDtos/fRXPlHHeYGU7ZQxxDtN3DPbLeTehEI6GRadg6KYpqCHWn9Y06BondFa/zz43Cx4GY4Do7z7I38k0pI8iCj1Z/vUKkZDmkNtatd47HGzOXl/QZmAO5prg==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=bt.com; dmarc=pass action=none header.from=bt.com; dkim=pass header.d=bt.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bt.com; s=selector1; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=s/PO47AX01/JJaJZA2feZvte5Oea8dfUNP/0kWzTrBc=; b=Ctb1x43KkalWKA8h49ize0nrtDxhB/Gl1hoXJelDwqHCJXsTaRi97kIWTMvfRZoq8vK5c7eFiR2nXK1/tx7fPFR46w5w2KEES0VVC2iMLRKWV0aJeaM3lfIqPbBklqfJyroMUYz/lGXVWP+44Kl1set+Jcd6acsNFNd+Oirf4Xw=
Received: from LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:dc::10) by LO3P123MB3580.GBRP123.PROD.OUTLOOK.COM (2603:10a6:600:10a::9) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3239.16; Wed, 29 Jul 2020 12:36:08 +0000
Received: from LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM ([fe80::ec07:dcb5:1747:4632]) by LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM ([fe80::ec07:dcb5:1747:4632%7]) with mapi id 15.20.3239.016; Wed, 29 Jul 2020 12:36:08 +0000
From: <tim.jebb@bt.com>
CC: <quic@ietf.org>
Subject: RE: Problems verifying sample packet protection in appendix A of Using TLS to Secure QUIC
Thread-Topic: Problems verifying sample packet protection in appendix A of Using TLS to Secure QUIC
Thread-Index: AdZZ60hBgJSiLWoSRDqZxGYKUQVBHwAI+HGAAVk5nPABjDC4QA==
Date: Wed, 29 Jul 2020 12:36:08 +0000
Message-ID: <LNXP123MB2460A8EB35971933082835C3F2700@LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM>
References: <LNXP123MB2460833EC5BC592C8D410EDCF2610@LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM> <CACdeXi+EUWRGoT7pWrqnEbQK9EoT0ERr7pKFmtOQ3pQZc9wfCw@mail.gmail.com> <LO2P123MB2462F4CDAD99B8E3DAA39F9FF2780@LO2P123MB2462.GBRP123.PROD.OUTLOOK.COM>
In-Reply-To: <LO2P123MB2462F4CDAD99B8E3DAA39F9FF2780@LO2P123MB2462.GBRP123.PROD.OUTLOOK.COM>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
authentication-results: ietf.org; dkim=none (message not signed) header.d=none;ietf.org; dmarc=none action=none header.from=bt.com;
x-originating-ip: [31.51.248.139]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1fac3b16-5ce7-40bf-e774-08d833bbf7cb
x-ms-traffictypediagnostic: LO3P123MB3580:
x-microsoft-antispam-prvs: <LO3P123MB35805063F21D73CA30963BC7F2700@LO3P123MB3580.GBRP123.PROD.OUTLOOK.COM>
x-antispam-2: 1
x-ms-oob-tlc-oobclassifiers: OLM:9508;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: SwHyZdJPCiIoL9HlmM3t7SaBFjfOfOpCwN7dBaN0zIgv+/Ao7Cwn9v0wJZHRNplRWool8Nbx6gHr91Us2KRnCvimEI6+HaPQ+VhEGZ8Odkxmd5LGDI5qxnSEaoVNuj5YctDyhOChftUgzbuLS2c8VRbjEP6La/16Nl+MZJ5ONHaPE5eU4+kFp7ldMZfH5CNduh6FNSkNefP16oFSo4/bHevVHmOgxb8t80OwOP4DKz0E+RP6q9Bv22Bqv+Hrdox4SJtaPxzJmtX+n4w/Q8faNwRbNiaC8yoxXsx30p47t8zUPvjFDB3rOXbDFUDSn6xZbUaLcDzEn229IZEk2vADz7uZ0nkB9DGmzP6NjXpwDuEAL5dyh36RjWaZPM2HN2TAuLHqKs5DYT9LdamCpseM0w==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(376002)(366004)(39860400002)(396003)(346002)(136003)(186003)(33656002)(16799955002)(71200400001)(52536014)(5660300002)(53546011)(109986005)(6506007)(4326008)(26005)(478600001)(55236004)(316002)(64756008)(66946007)(66556008)(66446008)(66476007)(166002)(966005)(76116006)(83380400001)(86362001)(55016002)(15650500001)(2906002)(8936002)(7696005)(8676002)(9686003); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: jW+6vaKe+mbEoVanstiH4K2ReiI+T31GCihJvnf+BQQghkBh9Q3Z8kWliXYFlesuBnpfHUAvgewzJ+bYSy92cwyEBbRPblebgamFgYMxscLu5azgeCLRfrR1bxfaXJi/lr6sy3ffYRZ2y/q3ASJaVs2lHF9CNNJ3PXFwBxhPY3hWJ4PcdMGDzV5r7G9R4x8pVtMGUeFGGLhgsqmSKWh12VSGd19JnvHqu9zUclrZKmrpe5LvFsS2R7y+/7hkOd45KLsSrYes95hLMZqGqxIrfI7KIXsYCmIrxP1Xw3fVKXikAumcrLcNREjSm8vrGCa7r+lg8U9T445XfP2frpzkcNz4iwD4FqHnsU3h+34VNFdRaLYuuUF9k6yYA831prWawMHzAa1SkDVE/a6k1liMlQAqRQHs/iPip+bzs01YVVSRtCyEBwPdNhqMWX00wfqnOOE44ZuR/w79U3qfwk8tyxh+go2q0b4fncNOftfvhTwql08MvsmF5YZGCQ6V9iT0Mfw9N05pMiYcyiKSrr/uV/pRCBuVs2ghym8hdO/0/CxPznXFeJfQ2c7OnRSB1julvGXpep52Ba8sIx6U9iyi1UfawwVnIKS1AJYgz3Db5HIsq+B55/OUHK50IoK7riyTQ+eR2NFLLJY5WLLVYT80KA==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_LNXP123MB2460A8EB35971933082835C3F2700LNXP123MB2460GBRP_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: LNXP123MB2460.GBRP123.PROD.OUTLOOK.COM
X-MS-Exchange-CrossTenant-Network-Message-Id: 1fac3b16-5ce7-40bf-e774-08d833bbf7cb
X-MS-Exchange-CrossTenant-originalarrivaltime: 29 Jul 2020 12:36:08.1202 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: a7f35688-9c00-4d5e-ba41-29f146377ab0
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: TDuP2zltbeVeenTZ1J0MmSHH/7N+jYzHwMHcn4fuomaDGp2Ht1KyJox9OGPQYQvt
X-MS-Exchange-Transport-CrossTenantHeadersStamped: LO3P123MB3580
X-OriginatorOrg: bt.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/FaQyeHz85TIotzDpvbE0wAs7_eQ>
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, 29 Jul 2020 12:36:16 -0000

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

SnVzdCBhbiB1cGRhdGU6ICBJ4oCZdmUgZ290IHRvIHRoZSBib3R0b20gb2YgbXkgcHJvYmxlbTog
IEkgaGFkbuKAmXQgcmVhbGlzZWQgdGhhdCB0aGUgc2FsdCBjaGFuZ2VzIGJldHdlZW4gZHJhZnRz
IG9mIHRoZSBSRkMhDQoNCkZyb206IHRpbS5qZWJiQGJ0LmNvbSA8dGltLmplYmJAYnQuY29tPg0K
U2VudDogMjEgSnVseSAyMDIwIDE2OjQzDQpUbzogbmhhcnBlckBnb29nbGUuY29tDQpDYzogcXVp
Y0BpZXRmLm9yZw0KU3ViamVjdDogUkU6IFByb2JsZW1zIHZlcmlmeWluZyBzYW1wbGUgcGFja2V0
IHByb3RlY3Rpb24gaW4gYXBwZW5kaXggQSBvZiBVc2luZyBUTFMgdG8gU2VjdXJlIFFVSUMNCg0K
SGksDQoNClVuZm9ydHVuYXRlbHkgSeKAmW0gc3RpbGwgaGF2aW5nIHByb2JsZW1zIHJlbW92aW5n
IHBhY2tldCBwcm90ZWN0aW9uLg0KDQpBbHRob3VnaCBJIGNhbiBub3cgc3VjY2Vzc2Z1bGx5IHBy
b2Nlc3MgdGhlIHNhbXBsZSBwYWNrZXQgaW4gdGhlIGRyYWZ0IFJGQyAodGhhbmtzIHRvIE5pY2sp
LCBteSBmaXJzdCBhdHRlbXB0IGF0IGEgY2FwdHVyZWQgcGFja2V0IGlzIGZhaWxpbmcgKHVzaW5n
IHRoZSBzYW1lIGNvZGUpLiAgSSBjYW7igJl0IHNlZSB3aGVyZSBJ4oCZbSBnb2luZyB3cm9uZy4g
IEl04oCZcyB0aGUgaGVhZGVyIHByb3RlY3Rpb24gcmVtb3ZhbCBJ4oCZbSBoYXZpbmcgcHJvYmxl
bXMgd2l0aC4NCg0KSWYgaXTigJlzIG5vdCB0b28gbXVjaCB0byBhc2ssIHdvdWxkIGFueW9uZSBi
ZSBpbiBhIHBvc2l0aW9uIHRvIHByb2Nlc3MgdGhlIGNsaWVudCBpbml0aWFsIHBhY2tldCBiZWxv
dywgYW5kIGdpdmUgdGhlIGludGVybWVkaWF0ZSB2YWx1ZXMgYWxvbmcgdGhlIGxpbmVzIG9mIHRo
b3NlIGdpdmVuIGluIGFwcGVuZGl4IEE/DQoNClRoZSBwYWNrZXQgaXMNCg0KdWludDhfdCBwcm90
ZWN0ZWRfZnJhbWUxWzMwMl0gPQ0KezB4YzgsMHhmZiwweDAwLDB4MDAsMHgxYiwweDExLDB4NzYs
MHhmOCwweDFhLDB4NTUsMHg4OCwweGIyLDB4ZjIsMHg1YywweDVhLDB4YjYsDQoweGRiLDB4ZDQs
MHg2MSwweGE4LDB4ZDcsMHg0OSwweGUxLDB4MDMsMHhjNSwweGVmLDB4MDIsMHgwMCwweDQxLDB4
MTAsMHhiMCwweGJkLA0KMHgxNCwweDA0LDB4ZjUsMHgzNSwweDE3LDB4N2YsMHhjYiwweGNmLDB4
ZDUsMHhmMCwweDZkLDB4MjQsMHhmZiwweGRlLDB4NjYsMHhlZCwNCjB4ZjEsMHgwZCwweGY3LDB4
OTIsMHgwNSwweDY2LDB4NmIsMHgxOCwweDUxLDB4MTgsMHg5ZiwweDU0LDB4YTAsMHg5MiwweDdk
LDB4ZjIsDQoweDMwLDB4YjUsMHhjYiwweGQ3LDB4YzksMHg2ZCwweGU2LDB4YzUsMHg3NiwweGU1
LDB4NTksMHg0MiwweDIzLDB4MWUsMHhjOCwweDUzLA0KMHg5ZiwweGYyLDB4ODIsMHhlMiwweGNm
LDB4ZDcsMHg1MywweDgzLDB4OGIsMHgxMiwweDUzLDB4Y2UsMHgxOSwweDVjLDB4ZDYsMHgzMiwN
CjB4MjIsMHg1ZCwweGUwLDB4Y2EsMHgyZSwweDM3LDB4NDIsMHhjMSwweGRhLDB4MDgsMHg0ZCww
eGE0LDB4ZDEsMHgxOCwweGM3LDB4NzUsDQoweDdjLDB4M2MsMHhhZSwweDNiLDB4ZjYsMHg5NSww
eGEyLDB4YzYsMHg4MywweDk5LDB4OTcsMHg5ZiwweDk4LDB4MGQsMHhkYiwweGE2LA0KMHhhOSww
eDc3LDB4YmQsMHhiYSwweDMxLDB4MjAsMHhiMiwweDhiLDB4ZTgsMHgwZSwweDBiLDB4ZTksMHhl
MCwweDg5LDB4M2YsMHgwNSwNCjB4OGQsMHhkZCwweDhkLDB4N2IsMHhlMywweDkwLDB4ZGUsMHhk
NiwweDY4LDB4NzksMHg2MiwweDhkLDB4NDcsMHhiNywweDQ3LDB4NzgsDQoweDE3LDB4NGUsMHg5
ZSwweDY1LDB4OTMsMHhjZSwweDgxLDB4MTcsMHhiZiwweDVmLDB4NGIsMHgxNiwweGI4LDB4OGQs
MHhlMywweDQ4LA0KMHg0ZiwweDk3LDB4N2UsMHgyMiwweGRlLDB4ZDgsMHg2ZSwweGIyLDB4OWIs
MHgwMCwweGJkLDB4YTQsMHhhNCwweGZiLDB4NzQsMHg5YywNCjB4ZWUsMHg4MywweDI5LDB4ZDYs
MHhmMSwweDMyLDB4YjMsMHg5MSwweGJiLDB4NmUsMHg5YSwweDkzLDB4NzEsMHg2MSwweGM0LDB4
ZDksDQoweGViLDB4MzAsMHgyZiwweDQzLDB4NzMsMHgyMCwweGU0LDB4NzgsMHgyOSwweGZmLDB4
ZTcsMHgxOSwweDExLDB4OTcsMHhlOCwweDMzLA0KMHhkNSwweDQ3LDB4ZDEsMHg2ZSwweGMxLDB4
ZGMsMHg5MSwweDBmLDB4ZDYsMHhmZSwweGFjLDB4NjQsMHg5NCwweDk5LDB4MDAsMHhiOSwNCjB4
OTEsMHg3OSwweGY2LDB4MWMsMHgxMSwweDg1LDB4NDQsMHhkMSwweDlmLDB4NTYsMHhiZSwweDNm
LDB4NGYsMHg1MiwweGE3LDB4MmMsDQoweDUyLDB4M2QsMHgyYiwweDQxLDB4ZTAsMHg0MiwweGE3
LDB4NGMsMHhiYywweDMxLDB4ZDQsMHhiMywweGE0LDB4NTUsMHhkZSwweGNlLA0KMHgwYywweGJl
LDB4OWQsMHgyOSwweDU5LDB4ZGYsMHhmOCwweGZiLDB4NTMsMHgwYywweDY0LDB4MmUsMHhiNSww
eDJkLDB4YTQsMHgzZCwNCjB4ZWEsMHhmOSwweDkwLDB4OGMsMHgxYiwweDBiLDB4ZDUsMHgwZCww
eDQ0LDB4NTksMHhlMCwweGU0LDB4NzQsMHg4NX07DQoNCkZyb206IE5pY2sgSGFycGVyIDxuaGFy
cGVyQGdvb2dsZS5jb208bWFpbHRvOm5oYXJwZXJAZ29vZ2xlLmNvbT4+DQpTZW50OiAxNCBKdWx5
IDIwMjAgMTk6NDcNClRvOiBKZWJiLFRSLFRpbSxWSUUgUiA8dGltLmplYmJAYnQuY29tPG1haWx0
bzp0aW0uamViYkBidC5jb20+Pg0KQ2M6IElFVEYgUVVJQyBXRyA8cXVpY0BpZXRmLm9yZzxtYWls
dG86cXVpY0BpZXRmLm9yZz4+DQpTdWJqZWN0OiBSZTogUHJvYmxlbXMgdmVyaWZ5aW5nIHNhbXBs
ZSBwYWNrZXQgcHJvdGVjdGlvbiBpbiBhcHBlbmRpeCBBIG9mIFVzaW5nIFRMUyB0byBTZWN1cmUg
UVVJQw0KDQoNCg0KT24gVHVlLCBKdWwgMTQsIDIwMjAgYXQgOTowNiBBTSA8dGltLmplYmJAYnQu
Y29tPG1haWx0bzp0aW0uamViYkBidC5jb20+PiB3cm90ZToNCkhpLA0KDQpJ4oCZbSB3b3JraW5n
IHRocm91Z2ggQXBwZW5kaXggQSBvZiB0aGUgUVVJQyBUTFMgZG9jIHRvIGNoZWNrIG15IHVuZGVy
c3RhbmRpbmcsIGJ1dCBhbSBoYXZpbmcgdHJvdWJsZSBkZWNyeXB0aW5nIHRoZSBzYW1wbGUgY2xp
ZW50IGluaXRpYWwgcGFja2V0LiAgSeKAmW0gdW5zdXJlIGlmIEnigJl2ZSBtYWRlIGEgc2lsbHkg
ZXJyb3Igb3IgdHdvLCBvciBpZiBJ4oCZdmUgbWFkZSBvbmUgb3IgbW9yZSBpbmNvcnJlY3QgYXNz
dW1wdGlvbnMuICBPciBib3RoLg0KDQpUaGUgZnVuY3Rpb25zIEnigJltIHVzaW5nIGFyZSB0aGUg
T3BlblNTTCBFVlAgb25lcy4gIEnigJltIGF0dGVtcHRpbmcgdG8gZm9sbG93IHRoZSByZWNpcGUg
aGVyZToNCmh0dHBzOi8vd2lraS5vcGVuc3NsLm9yZy9pbmRleC5waHAvRVZQX0F1dGhlbnRpY2F0
ZWRfRW5jcnlwdGlvbl9hbmRfRGVjcnlwdGlvbiNBdXRoZW50aWNhdGVkX0RlY3J5cHRpb25fdXNp
bmdfR0NNX21vZGUgaW4gY29uanVuY3Rpb24gd2l0aCB0aGUgZHJhZnQgUkZDLg0KDQoNCkVWUF9D
SVBIRVJfQ1RYX25ldygpDQoNCkVWUF9EZWNyeXB0SW5pdF9leChjdHgsIEVWUF9hZXNfMTI4X2dj
bSgpLCBOVUxMLCBOVUxMLCBOVUxMKQ0KDQpFVlBfRGVjcnlwdEluaXRfZXgoY3R4LCBOVUxMLCBO
VUxMLCBjbGllbnRfa2V5LCBpdikgICAgICAgICB3aGVyZSB0aGUgY2xpZW50IGtleSBpcyAweDE3
NTI1N2EzMWViMDlkZWE5MzY2ZDhiYjc5YWQ4MGJhIGFuZCB0aGUgaXYgaXMgMHg2YjI2MTE0Yjlj
YmEyYjYzYTllOGRkNGYNCg0KWW91IG5lZWQgdG8gY29tcHV0ZSB0aGUgbm9uY2UgZnJvbSB0aGUg
SVYgYW5kIHRoZSBwYWNrZXQgbnVtYmVyLiBJIGFzc3VtZSB3aGF0IHRoZSBvcGVuc3NsIGRvY3Vt
ZW50YXRpb24gcmVmZXJzIHRvIGFzIGFuIElWIGlzIGFjdHVhbGx5IHRoZSBub25jZSBhcyBkZXNj
cmliZWQgaW4gUkZDIDUxMTYuDQoNCkVWUF9EZWNyeXB0VXBkYXRlKGN0eCwgTlVMTCwgJmxlbiwg
cFVucHJvdGVjdGVkSGVhZGVyLCBoZWFkZXJMZW5ndGgpICAgICAgICAgICB3aGVyZSB0aGUgdW5w
cm90ZWN0ZWQgaGVhZGVyIGlzIDB4YzNmZjAwMDAxZDA4ODM5NGM4ZjAzZTUxNTcwODAwMDA0NDll
MDAwMDAwMDIg4oCTIHRoaXMgSSBiZWxpZXZlIGlzIHRoZSBBZGRpdGlvbmFsIERhdGEgcmVxdWly
ZWQNCg0KRVZQX0RlY3J5cHRVcGRhdGUoY3R4LCBkZWNyeXB0ZWRQYXlsb2FkLCAmbGVuLCBwUGF5
bG9hZCwgcGF5bG9hZExlbmd0aC0xNikpICAgaGVyZSBJ4oCZbSBwYXNzaW5nIGluIHRoZSBlbmNy
eXB0ZWQgcGF5bG9hZCBiZWdpbm5pbmcgMHhmYjY2YmM1ZiBhbmQgZW5kaW5nIDB4ZTgyYTRkOTE5
ZDQ4LCBsZW5ndGggMTE2Mi4gIEnigJltIGFzc3VtaW5nIHRoYXQgdGhlIGZpbmFsIDE2IGJ5dGVz
IG9mIHRoZSBwYXlsb2FkIGlzIHRoZSBhdXRoZW50aWNhdGlvbiB0YWcgc28gYW0gbm90IHBhc3Np
bmcgaXQgaW4gaGVyZS4gIE5vdGUgdGhhdCBpZiB0aGlzIGFzc3VtcHRpb24gYWJvdXQgdGhlIGF1
dGhlbnRpY2F0aW9uIHRhZyBpcyBjb3JyZWN0LCBJIHRoaW5rIGl0IGNvdWxkIGJlIG1vcmUgY2xl
YXJseSBzdGF0ZWQgaW4gdGhlIGRyYWZ0IFJGQy4NCg0KVGhpcyBpcyBhIHF1aXJrIG9mIHRoZSBv
cGVuc3NsIEFQSSB1bmZvcnR1bmF0ZWx5LiBBbiBBRUFEIGRlY3J5cHRpb24gb3BlcmF0aW9uIHNo
b3VsZCB0YWtlIDQgaW5wdXRzOiB0aGUga2V5LCB0aGUgbm9uY2UsIHRoZSBhc3NvY2lhdGVkIGRh
dGEsIGFuZCB0aGUgY2lwaGVydGV4dC4gVGhlIGNpcGhlcnRleHQsIGFzIGRlZmluZWQgYnkgUkZD
IDUxMTYsIGluY2x1ZGVzIHRoZSB0YWcuIFRoZXJlJ3Mgbm8gcmVxdWlyZW1lbnQgb24gdGhlIHN0
cnVjdHVyZSBvZiBhbiBBRUFEJ3MgY2lwaGVydGV4dCwgaW5jbHVkaW5nIHRoYXQgc29tZSBwb3J0
aW9uIG9mIHRoZSBjaXBoZXJ0ZXh0IGJlIGFibGUgdG8gYmUgaWRlbnRpZmllZCBhcyBhIHRhZy4g
QUVTLUdDTSBkb2VzIGhhdmUgdGhpcyBzdHJ1Y3R1cmUgd2hlcmUgdGhlIHRhZyBpcyBhdCB0aGUg
ZW5kIG9mIHRoZSBjaXBoZXJ0ZXh0LCBhbmQgdW5mb3J0dW5hdGVseSBvcGVuc3NsIG1ha2VzIHRo
YXQgcGFydCBvZiB0aGUgYXBpIGZvciB0aGUgQUVBRCBvcGVuIG9wZXJhdGlvbiwgZXZlbiB0aG91
Z2ggc29tZW9uZSB1c2luZyBpdCBzaG91bGQgbmV2ZXIgaGF2ZSB0byBrbm93IHRoYXQgZGV0YWls
IG9mIHRoZSBBRVMtR0NNIGFsZ29yaXRobS4NCg0KRVZQX0NJUEhFUl9DVFhfY3RybChjdHgsIEVW
UF9DVFJMX0dDTV9TRVRfVEFHLCAxNiwgdGFnKSB3aGVyZSB0YWcgaXMgdGhlIGZpbmFsIDE2IGJ5
dGVzIG9mIHRoZSBlbmNyeXB0ZWQgcGF5bG9hZCwgaWUgMHg0M2IxY2E3MCBhMmQ4ZDNmNyAyNWVh
ZDEzOSAxMzc3ZGNjMA0KDQpFVlBfRGVjcnlwdEZpbmFsX2V4KGN0eCwgZGVjcnlwdGVkUGF5bG9h
ZCArIGxlbiwgJmxlbikNCg0KRXZlcnl0aGluZyBzZWVtcyBPSyB1bnRpbCB0aGUgRVZQX0RlY3J5
cHRGaW5hbF9leCgpIGNhbGwgd2hpY2ggZmFpbHMuDQoNCklzIHRoZXJlIGFueXRoaW5nIG9idmlv
dXNseSB3cm9uZyB3aXRoIHRoZSBhYm92ZT8gIEnigJl2ZSBub3QgcG9zdGVkIHRoZSBmdWxsIHNv
dXJjZSBjb2RlIGFzIEnigJltIG5vdCBhc2tpbmcgcGVvcGxlIHRvIGNoZWNrIG15IHdvcmtpbmcs
IEnigJltIHJlYWxseSBhc2tpbmcgaWYgbXkgYXNzdW1wdGlvbnMgYXJlIGNvcnJlY3QsIGFtIEkg
dXNpbmcgdGhlIGNvcnJlY3QgZnVuY3Rpb25zLCBpbnB1dCBkYXRhIGV0Yy4NCg0KVGhhbmtzIGlu
IGFkdmFuY2UNCg0KVGltDQo=

--_000_LNXP123MB2460A8EB35971933082835C3F2700LNXP123MB2460GBRP_
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
by1zdHlsZS10eXBlOnBlcnNvbmFsOw0KCWZvbnQtZmFtaWx5OiJDYWxpYnJpIixzYW5zLXNlcmlm
Ow0KCWNvbG9yOndpbmRvd3RleHQ7fQ0Kc3Bhbi5FbWFpbFN0eWxlMTkNCgl7bXNvLXN0eWxlLXR5
cGU6cGVyc29uYWw7DQoJZm9udC1mYW1pbHk6IkNhbGlicmkiLHNhbnMtc2VyaWY7DQoJY29sb3I6
d2luZG93dGV4dDt9DQpzcGFuLkVtYWlsU3R5bGUyMQ0KCXttc28tc3R5bGUtdHlwZTpwZXJzb25h
bC1yZXBseTsNCglmb250LWZhbWlseToiQ2FsaWJyaSIsc2Fucy1zZXJpZjsNCgljb2xvcjp3aW5k
b3d0ZXh0O30NCi5Nc29DaHBEZWZhdWx0DQoJe21zby1zdHlsZS10eXBlOmV4cG9ydC1vbmx5Ow0K
CWZvbnQtc2l6ZToxMC4wcHQ7fQ0KQHBhZ2UgV29yZFNlY3Rpb24xDQoJe3NpemU6NjEyLjBwdCA3
OTIuMHB0Ow0KCW1hcmdpbjo3Mi4wcHQgNzIuMHB0IDcyLjBwdCA3Mi4wcHQ7fQ0KZGl2LldvcmRT
ZWN0aW9uMQ0KCXtwYWdlOldvcmRTZWN0aW9uMTt9DQotLT48L3N0eWxlPjwhLS1baWYgZ3RlIG1z
byA5XT48eG1sPg0KPG86c2hhcGVkZWZhdWx0cyB2OmV4dD0iZWRpdCIgc3BpZG1heD0iMTAyNiIg
Lz4NCjwveG1sPjwhW2VuZGlmXS0tPjwhLS1baWYgZ3RlIG1zbyA5XT48eG1sPg0KPG86c2hhcGVs
YXlvdXQgdjpleHQ9ImVkaXQiPg0KPG86aWRtYXAgdjpleHQ9ImVkaXQiIGRhdGE9IjEiIC8+DQo8
L286c2hhcGVsYXlvdXQ+PC94bWw+PCFbZW5kaWZdLS0+DQo8L2hlYWQ+DQo8Ym9keSBsYW5nPSJF
Ti1HQiIgbGluaz0iYmx1ZSIgdmxpbms9InB1cnBsZSI+DQo8ZGl2IGNsYXNzPSJXb3JkU2VjdGlv
bjEiPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1
YWdlOkVOLVVTIj5KdXN0IGFuIHVwZGF0ZTombmJzcDsgSeKAmXZlIGdvdCB0byB0aGUgYm90dG9t
IG9mIG15IHByb2JsZW06ICZuYnNwO0kgaGFkbuKAmXQgcmVhbGlzZWQgdGhhdCB0aGUgc2FsdCBj
aGFuZ2VzIGJldHdlZW4gZHJhZnRzIG9mIHRoZSBSRkMhPG86cD48L286cD48L3NwYW4+PC9wPg0K
PHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVO
LVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+DQo8ZGl2Pg0KPGRpdiBzdHlsZT0iYm9y
ZGVyOm5vbmU7Ym9yZGVyLXRvcDpzb2xpZCAjRTFFMUUxIDEuMHB0O3BhZGRpbmc6My4wcHQgMGNt
IDBjbSAwY20iPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PGI+PHNwYW4gbGFuZz0iRU4tVVMiPkZy
b206PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJFTi1VUyI+IHRpbS5qZWJiQGJ0LmNvbSAmbHQ7dGlt
LmplYmJAYnQuY29tJmd0Ow0KPGJyPg0KPGI+U2VudDo8L2I+IDIxIEp1bHkgMjAyMCAxNjo0Mzxi
cj4NCjxiPlRvOjwvYj4gbmhhcnBlckBnb29nbGUuY29tPGJyPg0KPGI+Q2M6PC9iPiBxdWljQGll
dGYub3JnPGJyPg0KPGI+U3ViamVjdDo8L2I+IFJFOiBQcm9ibGVtcyB2ZXJpZnlpbmcgc2FtcGxl
IHBhY2tldCBwcm90ZWN0aW9uIGluIGFwcGVuZGl4IEEgb2YgVXNpbmcgVExTIHRvIFNlY3VyZSBR
VUlDPG86cD48L286cD48L3NwYW4+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiPjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4g
c3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj5IaSw8bzpwPjwvbzpwPjwvc3Bhbj48
L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3Vh
Z2U6RU4tVVMiPjxvOnA+Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+VW5mb3J0dW5hdGVs
eSBJ4oCZbSBzdGlsbCBoYXZpbmcgcHJvYmxlbXMgcmVtb3ZpbmcgcGFja2V0IHByb3RlY3Rpb24u
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj48bzpwPiZuYnNwOzwvbzpwPjwvc3Bhbj48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6
RU4tVVMiPkFsdGhvdWdoIEkgY2FuIG5vdyBzdWNjZXNzZnVsbHkgcHJvY2VzcyB0aGUgc2FtcGxl
IHBhY2tldCBpbiB0aGUgZHJhZnQgUkZDICh0aGFua3MgdG8gTmljayksIG15IGZpcnN0IGF0dGVt
cHQgYXQgYSBjYXB0dXJlZCBwYWNrZXQgaXMgZmFpbGluZyAodXNpbmcgdGhlIHNhbWUgY29kZSku
Jm5ic3A7IEkgY2Fu4oCZdCBzZWUgd2hlcmUgSeKAmW0gZ29pbmcgd3JvbmcuJm5ic3A7DQogSXTi
gJlzIHRoZSBoZWFkZXIgcHJvdGVjdGlvbiByZW1vdmFsIEnigJltIGhhdmluZyBwcm9ibGVtcyB3
aXRoLjxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0
eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+
PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1
YWdlOkVOLVVTIj5JZiBpdOKAmXMgbm90IHRvbyBtdWNoIHRvIGFzaywgd291bGQgYW55b25lIGJl
IGluIGEgcG9zaXRpb24gdG8gcHJvY2VzcyB0aGUgY2xpZW50IGluaXRpYWwgcGFja2V0IGJlbG93
LCBhbmQgZ2l2ZSB0aGUgaW50ZXJtZWRpYXRlIHZhbHVlcyBhbG9uZyB0aGUgbGluZXMgb2YgdGhv
c2UgZ2l2ZW4gaW4gYXBwZW5kaXggQT88bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0i
TXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjxvOnA+
Jm5ic3A7PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxl
PSJtc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+VGhlIHBhY2tldCBpcyA8bzpwPg0KPC9vOnA+
PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFz
dC1sYW5ndWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj51aW50
OF90IHByb3RlY3RlZF9mcmFtZTFbMzAyXSA9DQo8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMi
PnsweGM4LDB4ZmYsMHgwMCwweDAwLDB4MWIsMHgxMSwweDc2LDB4ZjgsMHgxYSwweDU1LDB4ODgs
MHhiMiwweGYyLDB4NWMsMHg1YSwweGI2LDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNz
PSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+MHhk
YiwweGQ0LDB4NjEsMHhhOCwweGQ3LDB4NDksMHhlMSwweDAzLDB4YzUsMHhlZiwweDAyLDB4MDAs
MHg0MSwweDEwLDB4YjAsMHhiZCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNv
Tm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjB4MTQsMHgw
NCwweGY1LDB4MzUsMHgxNywweDdmLDB4Y2IsMHhjZiwweGQ1LDB4ZjAsMHg2ZCwweDI0LDB4ZmYs
MHhkZSwweDY2LDB4ZWQsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4weGYxLDB4MGQsMHhm
NywweDkyLDB4MDUsMHg2NiwweDZiLDB4MTgsMHg1MSwweDE4LDB4OWYsMHg1NCwweGEwLDB4OTIs
MHg3ZCwweGYyLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxz
cGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+MHgzMCwweGI1LDB4Y2IsMHhk
NywweGM5LDB4NmQsMHhlNiwweGM1LDB4NzYsMHhlNSwweDU5LDB4NDIsMHgyMywweDFlLDB4Yzgs
MHg1Myw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBz
dHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjB4OWYsMHhmMiwweDgyLDB4ZTIsMHhj
ZiwweGQ3LDB4NTMsMHg4MywweDhiLDB4MTIsMHg1MywweGNlLDB4MTksMHg1YywweGQ2LDB4MzIs
PG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9
Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4weDIyLDB4NWQsMHhlMCwweGNhLDB4MmUsMHgz
NywweDQyLDB4YzEsMHhkYSwweDA4LDB4NGQsMHhhNCwweGQxLDB4MTgsMHhjNywweDc1LDxvOnA+
PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28t
ZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+MHg3YywweDNjLDB4YWUsMHgzYiwweGY2LDB4OTUsMHhh
MiwweGM2LDB4ODMsMHg5OSwweDk3LDB4OWYsMHg5OCwweDBkLDB4ZGIsMHhhNiw8bzpwPjwvbzpw
Pjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVh
c3QtbGFuZ3VhZ2U6RU4tVVMiPjB4YTksMHg3NywweGJkLDB4YmEsMHgzMSwweDIwLDB4YjIsMHg4
YiwweGU4LDB4MGUsMHgwYiwweGU5LDB4ZTAsMHg4OSwweDNmLDB4MDUsPG86cD48L286cD48L3Nw
YW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxh
bmd1YWdlOkVOLVVTIj4weDhkLDB4ZGQsMHg4ZCwweDdiLDB4ZTMsMHg5MCwweGRlLDB4ZDYsMHg2
OCwweDc5LDB4NjIsMHg4ZCwweDQ3LDB4YjcsMHg0NywweDc4LDxvOnA+PC9vOnA+PC9zcGFuPjwv
cD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFn
ZTpFTi1VUyI+MHgxNywweDRlLDB4OWUsMHg2NSwweDkzLDB4Y2UsMHg4MSwweDE3LDB4YmYsMHg1
ZiwweDRiLDB4MTYsMHhiOCwweDhkLDB4ZTMsMHg0OCw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8
cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4t
VVMiPjB4NGYsMHg5NywweDdlLDB4MjIsMHhkZSwweGQ4LDB4NmUsMHhiMiwweDliLDB4MDAsMHhi
ZCwweGE0LDB4YTQsMHhmYiwweDc0LDB4OWMsPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xh
c3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4w
eGVlLDB4ODMsMHgyOSwweGQ2LDB4ZjEsMHgzMiwweGIzLDB4OTEsMHhiYiwweDZlLDB4OWEsMHg5
MywweDcxLDB4NjEsMHhjNCwweGQ5LDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJN
c29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+MHhlYiww
eDMwLDB4MmYsMHg0MywweDczLDB4MjAsMHhlNCwweDc4LDB4MjksMHhmZiwweGU3LDB4MTksMHgx
MSwweDk3LDB4ZTgsMHgzMyw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48c3BhbiBzdHlsZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjB4ZDUsMHg0Nyww
eGQxLDB4NmUsMHhjMSwweGRjLDB4OTEsMHgwZiwweGQ2LDB4ZmUsMHhhYywweDY0LDB4OTQsMHg5
OSwweDAwLDB4YjksPG86cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+
PHNwYW4gc3R5bGU9Im1zby1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4weDkxLDB4NzksMHhmNiww
eDFjLDB4MTEsMHg4NSwweDQ0LDB4ZDEsMHg5ZiwweDU2LDB4YmUsMHgzZiwweDRmLDB4NTIsMHhh
NywweDJjLDxvOnA+PC9vOnA+PC9zcGFuPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFu
IHN0eWxlPSJtc28tZmFyZWFzdC1sYW5ndWFnZTpFTi1VUyI+MHg1MiwweDNkLDB4MmIsMHg0MSww
eGUwLDB4NDIsMHhhNywweDRjLDB4YmMsMHgzMSwweGQ0LDB4YjMsMHhhNCwweDU1LDB4ZGUsMHhj
ZSw8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj48c3BhbiBzdHls
ZT0ibXNvLWZhcmVhc3QtbGFuZ3VhZ2U6RU4tVVMiPjB4MGMsMHhiZSwweDlkLDB4MjksMHg1OSww
eGRmLDB4ZjgsMHhmYiwweDUzLDB4MGMsMHg2NCwweDJlLDB4YjUsMHgyZCwweGE0LDB4M2QsPG86
cD48L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PHNwYW4gc3R5bGU9Im1z
by1mYXJlYXN0LWxhbmd1YWdlOkVOLVVTIj4weGVhLDB4ZjksMHg5MCwweDhjLDB4MWIsMHgwYiww
eGQ1LDB4MGQsMHg0NCwweDU5LDB4ZTAsMHhlNCwweDc0LDB4ODV9OzxvOnA+PC9vOnA+PC9zcGFu
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiPjxzcGFuIHN0eWxlPSJtc28tZmFyZWFzdC1sYW5n
dWFnZTpFTi1VUyI+PG86cD4mbmJzcDs8L286cD48L3NwYW4+PC9wPg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PGI+PHNwYW4gbGFuZz0iRU4tVVMiPkZyb206PC9zcGFuPjwvYj48c3BhbiBsYW5nPSJF
Ti1VUyI+IE5pY2sgSGFycGVyICZsdDs8YSBocmVmPSJtYWlsdG86bmhhcnBlckBnb29nbGUuY29t
Ij5uaGFycGVyQGdvb2dsZS5jb208L2E+Jmd0Ow0KPGJyPg0KPGI+U2VudDo8L2I+IDE0IEp1bHkg
MjAyMCAxOTo0Nzxicj4NCjxiPlRvOjwvYj4gSmViYixUUixUaW0sVklFIFIgJmx0OzxhIGhyZWY9
Im1haWx0bzp0aW0uamViYkBidC5jb20iPnRpbS5qZWJiQGJ0LmNvbTwvYT4mZ3Q7PGJyPg0KPGI+
Q2M6PC9iPiBJRVRGIFFVSUMgV0cgJmx0OzxhIGhyZWY9Im1haWx0bzpxdWljQGlldGYub3JnIj5x
dWljQGlldGYub3JnPC9hPiZndDs8YnI+DQo8Yj5TdWJqZWN0OjwvYj4gUmU6IFByb2JsZW1zIHZl
cmlmeWluZyBzYW1wbGUgcGFja2V0IHByb3RlY3Rpb24gaW4gYXBwZW5kaXggQSBvZiBVc2luZyBU
TFMgdG8gU2VjdXJlIFFVSUM8bzpwPjwvbzpwPjwvc3Bhbj48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIj48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05v
cm1hbCI+PG86cD4mbmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
PjxvOnA+Jm5ic3A7PC9vOnA+PC9wPg0KPGRpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij5PbiBUdWUsIEp1bCAxNCwgMjAyMCBhdCA5OjA2IEFNICZsdDs8YSBocmVmPSJtYWlsdG86dGlt
LmplYmJAYnQuY29tIj50aW0uamViYkBidC5jb208L2E+Jmd0OyB3cm90ZTo8bzpwPjwvbzpwPjwv
cD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRlci1sZWZ0OnNv
bGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJnaW4tbGVmdDo0
LjhwdDttYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1yaWdodDowY207bWFyZ2luLWJvdHRvbTo1LjBw
dCI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+SGksDQo8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBj
bGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdp
bi1ib3R0b20tYWx0OmF1dG8iPknigJltIHdvcmtpbmcgdGhyb3VnaCBBcHBlbmRpeCBBIG9mIHRo
ZSBRVUlDIFRMUyBkb2MgdG8gY2hlY2sgbXkgdW5kZXJzdGFuZGluZywgYnV0IGFtIGhhdmluZyB0
cm91YmxlIGRlY3J5cHRpbmcgdGhlIHNhbXBsZSBjbGllbnQgaW5pdGlhbCBwYWNrZXQuJm5ic3A7
IEnigJltIHVuc3VyZSBpZiBJ4oCZdmUgbWFkZSBhIHNpbGx5DQogZXJyb3Igb3IgdHdvLCBvciBp
ZiBJ4oCZdmUgbWFkZSBvbmUgb3IgbW9yZSBpbmNvcnJlY3QgYXNzdW1wdGlvbnMuJm5ic3A7IE9y
IGJvdGguPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1h
cmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+
PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFs
dDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj5UaGUgZnVuY3Rpb25zIEnigJltIHVz
aW5nIGFyZSB0aGUgT3BlblNTTCBFVlAgb25lcy4mbmJzcDsgSeKAmW0gYXR0ZW1wdGluZyB0byBm
b2xsb3cgdGhlIHJlY2lwZSBoZXJlOjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1h
bCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDph
dXRvIj48YSBocmVmPSJodHRwczovL3dpa2kub3BlbnNzbC5vcmcvaW5kZXgucGhwL0VWUF9BdXRo
ZW50aWNhdGVkX0VuY3J5cHRpb25fYW5kX0RlY3J5cHRpb24jQXV0aGVudGljYXRlZF9EZWNyeXB0
aW9uX3VzaW5nX0dDTV9tb2RlIiB0YXJnZXQ9Il9ibGFuayI+aHR0cHM6Ly93aWtpLm9wZW5zc2wu
b3JnL2luZGV4LnBocC9FVlBfQXV0aGVudGljYXRlZF9FbmNyeXB0aW9uX2FuZF9EZWNyeXB0aW9u
I0F1dGhlbnRpY2F0ZWRfRGVjcnlwdGlvbl91c2luZ19HQ01fbW9kZTwvYT4NCiBpbiBjb25qdW5j
dGlvbiB3aXRoIHRoZSBkcmFmdCBSRkMuPG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9y
bWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0
OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9
Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJz
cDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2lu
LXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+RVZQX0NJUEhFUl9DVFhf
bmV3KCk8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7PG86cD48
L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0
OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPkVWUF9EZWNyeXB0SW5pdF9leChjdHgs
IEVWUF9hZXNfMTI4X2djbSgpLCBOVUxMLCBOVUxMLCBOVUxMKTxvOnA+PC9vOnA+PC9wPg0KPHAg
Y2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJn
aW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29O
b3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1h
bHQ6YXV0byI+RVZQX0RlY3J5cHRJbml0X2V4KGN0eCwgTlVMTCwgTlVMTCwgY2xpZW50X2tleSwg
aXYpICZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyB3aGVyZSB0aGUg
Y2xpZW50IGtleSBpcyAweDE3NTI1N2EzMWViMDlkZWE5MzY2ZDhiYjc5YWQ4MGJhIGFuZCB0aGUg
aXYgaXMgMHg2YjI2MTE0YjljYmEyYjYzYTllOGRkNGY8bzpwPjwvbzpwPjwvcD4NCjwvZGl2Pg0K
PC9kaXY+DQo8L2Jsb2NrcXVvdGU+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCI+PG86cD4m
bmJzcDs8L286cD48L3A+DQo8L2Rpdj4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIj5Zb3Ug
bmVlZCB0byBjb21wdXRlIHRoZSBub25jZSBmcm9tIHRoZSBJViBhbmQgdGhlIHBhY2tldCBudW1i
ZXIuIEkgYXNzdW1lIHdoYXQgdGhlIG9wZW5zc2wgZG9jdW1lbnRhdGlvbiByZWZlcnMgdG8gYXMg
YW4gSVYgaXMgYWN0dWFsbHkgdGhlIG5vbmNlIGFzIGRlc2NyaWJlZCBpbiBSRkMgNTExNi48bzpw
PjwvbzpwPjwvcD4NCjwvZGl2Pg0KPGJsb2NrcXVvdGUgc3R5bGU9ImJvcmRlcjpub25lO2JvcmRl
ci1sZWZ0OnNvbGlkICNDQ0NDQ0MgMS4wcHQ7cGFkZGluZzowY20gMGNtIDBjbSA2LjBwdDttYXJn
aW4tbGVmdDo0LjhwdDttYXJnaW4tdG9wOjUuMHB0O21hcmdpbi1yaWdodDowY207bWFyZ2luLWJv
dHRvbTo1LjBwdCI+DQo8ZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJt
c28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+Jm5ic3A7
PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10
b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPkVWUF9EZWNyeXB0VXBkYXRl
KGN0eCwgTlVMTCwgJmFtcDtsZW4sIHBVbnByb3RlY3RlZEhlYWRlciwgaGVhZGVyTGVuZ3RoKSZu
YnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNwOyZuYnNw
OyB3aGVyZSB0aGUgdW5wcm90ZWN0ZWQgaGVhZGVyIGlzIDB4YzNmZjAwMDAxZDA4ODM5NGM4ZjAz
ZTUxNTcwODAwMDA0NDllMDAwMDAwMDIg4oCTIHRoaXMgSSBiZWxpZXZlIGlzDQogdGhlIEFkZGl0
aW9uYWwgRGF0YSByZXF1aXJlZDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIg
c3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRv
Ij4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28t
bWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+RVZQX0RlY3J5
cHRVcGRhdGUoY3R4LCBkZWNyeXB0ZWRQYXlsb2FkLCAmYW1wO2xlbiwgcFBheWxvYWQsIHBheWxv
YWRMZW5ndGgtMTYpKSZuYnNwOyZuYnNwOyBoZXJlIEnigJltIHBhc3NpbmcgaW4gdGhlIGVuY3J5
cHRlZCBwYXlsb2FkIGJlZ2lubmluZyAweGZiNjZiYzVmIGFuZCBlbmRpbmcgMHhlODJhNGQ5MTlk
NDgsIGxlbmd0aCAxMTYyLiZuYnNwOw0KIEnigJltIGFzc3VtaW5nIHRoYXQgdGhlIGZpbmFsIDE2
IGJ5dGVzIG9mIHRoZSBwYXlsb2FkIGlzIHRoZSBhdXRoZW50aWNhdGlvbiB0YWcgc28gYW0gbm90
IHBhc3NpbmcgaXQgaW4gaGVyZS4mbmJzcDsgTm90ZSB0aGF0IGlmIHRoaXMgYXNzdW1wdGlvbiBh
Ym91dCB0aGUgYXV0aGVudGljYXRpb24gdGFnIGlzIGNvcnJlY3QsIEkgdGhpbmsgaXQgY291bGQg
YmUgbW9yZSBjbGVhcmx5IHN0YXRlZCBpbiB0aGUgZHJhZnQgUkZDLjxvOnA+PC9vOnA+PC9wPg0K
PC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjxkaXY+DQo8cCBjbGFzcz0iTXNvTm9ybWFs
Ij48bzpwPiZuYnNwOzwvbzpwPjwvcD4NCjwvZGl2Pg0KPGRpdj4NCjxwIGNsYXNzPSJNc29Ob3Jt
YWwiPlRoaXMgaXMgYSBxdWlyayBvZiB0aGUgb3BlbnNzbCBBUEkgdW5mb3J0dW5hdGVseS4gQW4g
QUVBRCBkZWNyeXB0aW9uIG9wZXJhdGlvbiBzaG91bGQgdGFrZSA0IGlucHV0czogdGhlIGtleSwg
dGhlIG5vbmNlLCB0aGUgYXNzb2NpYXRlZCBkYXRhLCBhbmQgdGhlIGNpcGhlcnRleHQuIFRoZSBj
aXBoZXJ0ZXh0LCBhcyBkZWZpbmVkIGJ5IFJGQyA1MTE2LCBpbmNsdWRlcyB0aGUgdGFnLiBUaGVy
ZSdzIG5vIHJlcXVpcmVtZW50DQogb24gdGhlIHN0cnVjdHVyZSBvZiBhbiBBRUFEJ3MgY2lwaGVy
dGV4dCwgaW5jbHVkaW5nIHRoYXQgc29tZSBwb3J0aW9uIG9mIHRoZSBjaXBoZXJ0ZXh0IGJlIGFi
bGUgdG8gYmUgaWRlbnRpZmllZCBhcyBhIHRhZy4gQUVTLUdDTSBkb2VzIGhhdmUgdGhpcyBzdHJ1
Y3R1cmUgd2hlcmUgdGhlIHRhZyBpcyBhdCB0aGUgZW5kIG9mIHRoZSBjaXBoZXJ0ZXh0LCBhbmQg
dW5mb3J0dW5hdGVseSBvcGVuc3NsIG1ha2VzIHRoYXQgcGFydCBvZiB0aGUgYXBpDQogZm9yIHRo
ZSBBRUFEIG9wZW4gb3BlcmF0aW9uLCBldmVuIHRob3VnaCBzb21lb25lIHVzaW5nIGl0IHNob3Vs
ZCBuZXZlciBoYXZlIHRvIGtub3cgdGhhdCBkZXRhaWwgb2YgdGhlIEFFUy1HQ00gYWxnb3JpdGht
LjxvOnA+PC9vOnA+PC9wPg0KPC9kaXY+DQo8YmxvY2txdW90ZSBzdHlsZT0iYm9yZGVyOm5vbmU7
Ym9yZGVyLWxlZnQ6c29saWQgI0NDQ0NDQyAxLjBwdDtwYWRkaW5nOjBjbSAwY20gMGNtIDYuMHB0
O21hcmdpbi1sZWZ0OjQuOHB0O21hcmdpbi10b3A6NS4wcHQ7bWFyZ2luLXJpZ2h0OjBjbTttYXJn
aW4tYm90dG9tOjUuMHB0Ij4NCjxkaXY+DQo8ZGl2Pg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5
bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4m
bmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFy
Z2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+RVZQX0NJUEhFUl9D
VFhfY3RybChjdHgsIEVWUF9DVFJMX0dDTV9TRVRfVEFHLCAxNiwgdGFnKSB3aGVyZSB0YWcgaXMg
dGhlIGZpbmFsIDE2IGJ5dGVzIG9mIHRoZSBlbmNyeXB0ZWQgcGF5bG9hZCwgaWUgMHg0M2IxY2E3
MCBhMmQ4ZDNmNyAyNWVhZDEzOSAxMzc3ZGNjMDxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1z
b05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9t
LWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0
eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+
RVZQX0RlY3J5cHRGaW5hbF9leChjdHgsIGRlY3J5cHRlZFBheWxvYWQgKyBsZW4sICZhbXA7bGVu
KTxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4t
dG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpw
PjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwiIHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0
bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0byI+RXZlcnl0aGluZyBzZWVtcyBPSyB1bnRpbCB0
aGUgRVZQX0RlY3J5cHRGaW5hbF9leCgpIGNhbGwgd2hpY2ggZmFpbHMuPG86cD48L286cD48L3A+
DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNvLW1hcmdpbi10b3AtYWx0OmF1dG87bXNv
LW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPiZuYnNwOzxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj5JcyB0aGVyZSBhbnl0aGluZyBvYnZpb3VzbHkgd3Jvbmcgd2l0aCB0aGUg
YWJvdmU/Jm5ic3A7IEnigJl2ZSBub3QgcG9zdGVkIHRoZSBmdWxsIHNvdXJjZSBjb2RlIGFzIEni
gJltIG5vdCBhc2tpbmcgcGVvcGxlIHRvIGNoZWNrIG15IHdvcmtpbmcsIEnigJltIHJlYWxseSBh
c2tpbmcgaWYgbXkgYXNzdW1wdGlvbnMgYXJlIGNvcnJlY3QsDQogYW0gSSB1c2luZyB0aGUgY29y
cmVjdCBmdW5jdGlvbnMsIGlucHV0IGRhdGEgZXRjLjxvOnA+PC9vOnA+PC9wPg0KPHAgY2xhc3M9
Ik1zb05vcm1hbCIgc3R5bGU9Im1zby1tYXJnaW4tdG9wLWFsdDphdXRvO21zby1tYXJnaW4tYm90
dG9tLWFsdDphdXRvIj4mbmJzcDs8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+VGhhbmtzIGluIGFkdmFuY2U8bzpwPjwvbzpwPjwvcD4NCjxwIGNsYXNzPSJNc29Ob3JtYWwi
IHN0eWxlPSJtc28tbWFyZ2luLXRvcC1hbHQ6YXV0bzttc28tbWFyZ2luLWJvdHRvbS1hbHQ6YXV0
byI+Jm5ic3A7PG86cD48L286cD48L3A+DQo8cCBjbGFzcz0iTXNvTm9ybWFsIiBzdHlsZT0ibXNv
LW1hcmdpbi10b3AtYWx0OmF1dG87bXNvLW1hcmdpbi1ib3R0b20tYWx0OmF1dG8iPlRpbTxvOnA+
PC9vOnA+PC9wPg0KPC9kaXY+DQo8L2Rpdj4NCjwvYmxvY2txdW90ZT4NCjwvZGl2Pg0KPC9kaXY+
DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_LNXP123MB2460A8EB35971933082835C3F2700LNXP123MB2460GBRP_--


From nobody Wed Jul 29 05:56:01 2020
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 3930A3A0A9F for <quic@ietfa.amsl.com>; Wed, 29 Jul 2020 05:55:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.848
X-Spam-Level: 
X-Spam-Status: No, score=-1.848 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-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=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 1cQ2puosATBT for <quic@ietfa.amsl.com>; Wed, 29 Jul 2020 05:55:57 -0700 (PDT)
Received: from mail-wr1-x429.google.com (mail-wr1-x429.google.com [IPv6:2a00:1450:4864:20::429]) (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 E1AF83A0A9C for <quic@ietf.org>; Wed, 29 Jul 2020 05:55:56 -0700 (PDT)
Received: by mail-wr1-x429.google.com with SMTP id z18so17987768wrm.12 for <quic@ietf.org>; Wed, 29 Jul 2020 05:55:56 -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=8zOYpRMmxe0pAs159iZCr0W6Wxzt0fJPomJ1nH9kPA4=; b=qKn0QXmOoX/lGoyIuM2V9rE2jc9Ar7cIOsLwk7Q7BvNFyrHrn5lfBWPQ9/p1PePsWQ Hhw3icxjWcbvN/Ojj1D82gq+/yHzP/d93tK80o0rz3ZNzGP8wTBsHoCEsJ6EDpDIRUg5 OPl2RjN8LSR7cLBKAyDLD3QN9ZdIgFfv3kO+iQIoTzxJX9/gholCs/epNbKncACCRrZg Uy/xKSnPL2TgZ8Cl0tIeUIoNZd6bn0ZQis5oMfXMkMiBaT6CrFDosT+Bc3XbesRdDKgK /gzTuJuQE8fMqu/EXtdELeFV5Z9euqshGOlSxVPSdVRkxGYMxi2j/e7KftxsmNLgq0uk x0mg==
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=8zOYpRMmxe0pAs159iZCr0W6Wxzt0fJPomJ1nH9kPA4=; b=XM+u7mkFFYv0xfnDilIU34Nl4vEhQC8rCJIRDjswUoegm7wkNOBWgXMHZem7MIhYWW no7i9GYuN+b3tBpchxYdwxekjxzDPABJOlIoaM5c4ml821E2xJ/986IiBrd+DPSjNoR1 5DwBRKLJpTv0enC1HQ/2Gv+ChUo9t3Tr9o/0scGPaBpoLVl0VOhLFA5FZUJfdPrG2Odk nZzxGPlCykIzbafZ5Hsc3cBcXYbz1gE/7a727t6tJquSMr2j1cojbO1BEVxTPZxr/UhG Ws+cwtXozP7qNF0qdaRLI3UlOM3yLot2klaf6KlzucLvBhqzX54Ktp6ouwMpZqfMdB83 B2ew==
X-Gm-Message-State: AOAM531ZKGRXKdPqBTN0Dm1MiQPzA1PQdwHJGW2UK4yqxYy2RDwpLhP7 gMIn0PhoeVxW3xbaSQnOSDLi4btNLKdXQKeuXuOWYwlR
X-Google-Smtp-Source: ABdhPJwroIPAeKsSz6mNJ2+LGgsAWn9sKs4PJX6K/PCQ1gN0S47UpQPjlvPlo1FROyLi0/3S2GGjWxG3fhKfm/zIfiE=
X-Received: by 2002:a5d:480b:: with SMTP id l11mr28203433wrq.85.1596027355074;  Wed, 29 Jul 2020 05:55:55 -0700 (PDT)
MIME-Version: 1.0
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com>
In-Reply-To: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Wed, 29 Jul 2020 13:55:44 +0100
Message-ID: <CALGR9oavNjk4ti=J1_mA6FA-Leg7cNAAHw-uHzVDGb1N04NSpw@mail.gmail.com>
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
To: QUIC WG <quic@ietf.org>
Cc: Lars Eggert <lars@eggert.org>, Mark Nottingham <mnot@mnot.net>
Content-Type: multipart/alternative; boundary="0000000000008d159605ab9413e4"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/UR7KSfY8rgRnvjwy5x8GaYrGBu8>
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, 29 Jul 2020 12:56:00 -0000

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

Hi folks,

The consensus call has now ended.

We saw some pushback on the proposed resolution to #3842. Discussion on an
alternative proposal is continuing so we'll run this issue through the
Late-Stage process again.

There appears to be no pushback on the other issues, so consensus is
declared.

Kind regards
Lars, Lucas and Mark
QUIC WG Chairs

On Wed, Jul 22, 2020 at 3:00 AM Lucas Pardue <lucaspardue.24.7@gmail.com>
wrote:

> Folks,
>
> The following issues have proposals for resolution, and discussion so far
> seems
> to support consensus to accept them. Therefore, we are starting a 1-week
> consensus call. If you object to a proposal, 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 proposals once the call
> concludes.
>
> 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>.
>
>
> * #3880: How long is a validated address good for?
>   The proposal is to lose with no action.
>
> * #3875: Persistent congestion threshold is unreliable during the early
> stages of a connection
>   The proposal is <https://github.com/quicwg/base-drafts/pull/3889>
>
> * #3860: incorrect error code used for invalid RETIRE_CONNECTION_ID frames
>   The proposal is <https://github.com/quicwg/base-drafts/pull/3861>
>
> * #3845: What does "MUST reduce" mean?
>   The proposal is https://github.com/quicwg/base-drafts/pull/3864
>
> * #3842: Do I need to reset congestion info when the port changes?
>   The proposal is to close with no action.
>
> * #3834: Remove amplification throttle if the server receives Initial that
> echoes its high entropy SCID.
>   The proposal is <https://github.com/quicwg/base-drafts/pull/3924>
>
> * #3808: Versions are for endpoints
>   The proposal is <https://github.com/quicwg/base-drafts/pull/3785>
>
> * #3800: Coalescing different CIDs for same connection
>   The proposal is <https://github.com/quicwg/base-drafts/pull/3930>
>
> Cheers,
> Lars, Lucas and Mark
> QUIC WG Chairs
>

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

<div dir=3D"ltr"><div dir=3D"ltr"><div>Hi folks,</div><div><br></div><div>T=
he consensus call has now ended.<br><br></div><div>We saw some pushback on =
the proposed resolution to #3842. Discussion on an alternative proposal is =
continuing so we&#39;ll run this issue through the Late-Stage process again=
.</div><div><br></div><div>There appears to be no pushback on the other iss=
ues, so consensus is declared.</div><div><br></div><div>Kind regards</div><=
div>Lars, Lucas and Mark</div><div>QUIC WG Chairs<br></div></div><br><div c=
lass=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jul 22, =
2020 at 3:00 AM Lucas Pardue &lt;<a href=3D"mailto:lucaspardue.24.7@gmail.c=
om">lucaspardue.24.7@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"><div><div>Folks,</div><div><=
br></div><div>The following issues have proposals for resolution, and discu=
ssion so far seems</div>to support consensus to accept them. Therefore, we =
are starting a 1-week consensus call. If you object to a proposal, please d=
o so on the issue or<br>in response to this message (changing the Subject a=
ppropriately!). Absent any<br>pushback, we&#39;ll direct the editors to inc=
orporate proposals once the call concludes.<br><br>See &lt;<a href=3D"https=
://github.com/quicwg/base-drafts/projects/5" target=3D"_blank">https://gith=
ub.com/quicwg/base-drafts/projects/5</a>&gt; for the current state of<br>is=
sues in the Late Stage process, itself defined at<br>&lt;<a href=3D"https:/=
/github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md" target=3D"_blan=
k">https://github.com/quicwg/base-drafts/blob/master/CONTRIBUTING.md</a>&gt=
;.<br><br><br>* #3880: How long is a validated address good for?<br>=C2=A0 =
The proposal is to lose with no action.<br><br>* #3875: Persistent congesti=
on threshold is unreliable during the early stages of a connection<br>=C2=
=A0 The proposal is &lt;<a href=3D"https://github.com/quicwg/base-drafts/pu=
ll/3889" target=3D"_blank">https://github.com/quicwg/base-drafts/pull/3889<=
/a>&gt;<br><br>* #3860: incorrect error code used for invalid RETIRE_CONNEC=
TION_ID frames<br>=C2=A0 The proposal is &lt;<a href=3D"https://github.com/=
quicwg/base-drafts/pull/3861" target=3D"_blank">https://github.com/quicwg/b=
ase-drafts/pull/3861</a>&gt;<br><br>* #3845: What does &quot;MUST reduce&qu=
ot; mean?<br>=C2=A0 The proposal is <a href=3D"https://github.com/quicwg/ba=
se-drafts/pull/3864" target=3D"_blank">https://github.com/quicwg/base-draft=
s/pull/3864</a><br><br>* #3842: Do I need to reset congestion info when the=
 port changes?<br>=C2=A0 The proposal is to close with no action.<br><br>* =
#3834: Remove amplification throttle if the server receives Initial that ec=
hoes its high entropy SCID.<br>=C2=A0 The proposal is &lt;<a href=3D"https:=
//github.com/quicwg/base-drafts/pull/3924" target=3D"_blank">https://github=
.com/quicwg/base-drafts/pull/3924</a>&gt;<br><br>* #3808: Versions are for =
endpoints<br>=C2=A0 The proposal is &lt;<a href=3D"https://github.com/quicw=
g/base-drafts/pull/3785" target=3D"_blank">https://github.com/quicwg/base-d=
rafts/pull/3785</a>&gt;<br><br>* #3800: Coalescing different CIDs for same =
connection<br>=C2=A0 The proposal is &lt;<a href=3D"https://github.com/quic=
wg/base-drafts/pull/3930" target=3D"_blank">https://github.com/quicwg/base-=
drafts/pull/3930</a>&gt;<br><br></div><div>Cheers,</div><div>Lars, Lucas an=
d Mark<br></div><div>QUIC WG Chairs<br></div></div>
</blockquote></div></div>

--0000000000008d159605ab9413e4--


From nobody Wed Jul 29 06:43:49 2020
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 48C1F3A0B24 for <quic@ietfa.amsl.com>; Wed, 29 Jul 2020 06:43:48 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=eggert.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 VBDSrGs4BtTd for <quic@ietfa.amsl.com>; Wed, 29 Jul 2020 06:43:47 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 D459A3A0B26 for <quic@ietf.org>; Wed, 29 Jul 2020 06:43:46 -0700 (PDT)
Received: from [IPv6:2a00:ac00:4000:400:d404:4033:1b4e:8603] (unknown [IPv6:2a00:ac00:4000:400:d404:4033:1b4e:8603]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id E817B612C32; Wed, 29 Jul 2020 16:43:28 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1596030209; bh=4EB0vHy7D88/OY2DNBbGGTujO7gyTFkX3Tk0tsB/w+Y=; h=From:Subject:Date:In-Reply-To:Cc:To:References; b=rKXQpEprnsgyHAAbnrdsfo+fcWbSUlkp3k4ylB2WmtjCMHUVMWaHZ/NAYb57tPSdE uZD2gPFqZpks94qzOmDmhL8jQ12OIoBI6zdEdPGqCj2v6TbKq9pu0cxVHMPnl2XF48 RI6hGQS9KyIt6ospnvDI0w+tlHT1naA8c3OqxS1Q=
From: Lars Eggert <lars@eggert.org>
Message-Id: <C177F5BA-40A8-4493-96FA-12BC53FF61A3@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_F11E381F-5EBA-4472-8489-B442AD31809D"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: Re: Consensus call for Late-Stage documents, pre-IETF 108 edition
Date: Wed, 29 Jul 2020 16:43:27 +0300
In-Reply-To: <CAKcm_gM73QaQ_eruoy7YNnrhUF_G+SNPzFxA99RF=m7yCa98Sw@mail.gmail.com>
Cc: Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org>, Gorry Fairhust <gorry@erg.abdn.ac.uk>, "jri.ietf@gmail.com" <jri.ietf@gmail.com>, "huitema@huitema.net" <huitema@huitema.net>, "quic@ietf.org" <quic@ietf.org>, "mt@lowentropy.net" <mt@lowentropy.net>
To: Ian Swett <ianswett=40google.com@dmarc.ietf.org>
References: <CALGR9obkGENj_Brk5D29Z6HB-yq9TbPLjUXSNbotAZJ0LRHgSg@mail.gmail.com> <CABcZeBMQNX_qbXT_qCmyWuXdLeL2=ar0u9yKB=c8M7=WNB4oVQ@mail.gmail.com> <1909E24B-73CC-4129-9B64-F0A3BE2D74D7@eggert.org> <CA+9kkMCRfhNayN5jM5g3Ckwst4GGxR++be5p7ea1jYkE3MbzqA@mail.gmail.com> <CABcZeBOcZd9=Th4T=rm0i+EGnG1i8bjembf20ungVYaDSpjusQ@mail.gmail.com> <7b5c104c-36b6-3fe1-4e5b-0e42cc9e2b36@huitema.net> <74ef5430-8e3f-4b6b-b81f-b25443e975b4@www.fastmail.com> <32c098c3-24e4-1d7c-fdf5-33761adacfa8@erg.abdn.ac.uk> <FA3E4F14-570C-4A28-A2C8-EA2B3937E614@eggert.org> <0ee0a444-3910-3e71-54aa-581431495648@erg.abdn.ac.uk> <3644F334-F148-4FF5-AE86-015C073871AC@eggert.org> <c28e05f6-637d-9183-11db-f8daa8b9e7c4@huitema.net> <CACpbDcc86pgVpcN7DHb2s8aRGjzCC4RNjYPnGyDHhUCWg-G9zA@mail.gmail.com> <337cd3d0841e9d94a034aa2402ac2a030af550f8.camel@ericsson.com> <CAKcm_gM73QaQ_eruoy7YNnrhUF_G+SNPzFxA99RF=m7yCa98Sw@mail.gmail.com>
X-MailScanner-ID: E817B612C32.A113B
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/OqjoaIj1u0kdhpxaORC2dHmD2nA>
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, 29 Jul 2020 13:43:48 -0000

--Apple-Mail=_F11E381F-5EBA-4472-8489-B442AD31809D
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 2020-7-24, at 21:01, Ian Swett <ianswett=3D40google.com@dmarc.ietf.org>=
 wrote:
> One additional note: Clients MUST change Connection ID if they =
intentionally migrate, so a server can use the lack of CID change as a =
signal that it was likely an NAT or other unintended path change.

If I modified #3842 to take this into account, would that address =
people's concerns? Something like:

"...unless the only change is the other endpoint's port number ***and =
the connection ID did not change***" (new text between ***)

Thanks,
Lars

--Apple-Mail=_F11E381F-5EBA-4472-8489-B442AD31809D
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAl8hfP8ACgkQVLXDCb9w
wVflCw//dA4FrKIaqdvQyRquZxMNnd4bPGyCdZP9LzrtjsDtskZWyQ9+9wlf20qq
0pN+hZXVfmqd9jpR6VRBRDinXOH61MLIEQWlyLsQhxZuWo8mva50QA6d7vgEXHjC
fgsnXxDJY7fjQyJyMbA/4uGi64wDVKkhrwfZAWMLsFnk/CwMv4ygNFC9p5sAzirZ
kDmdxbD6eSRZLIwwC0ZfUNRA+uHBMtAYnL6GLWTeUmBxSJNFRrSW0wSbA23panf5
+UpakNH/Vp5eaeCfKrTQKe7VrrygblDWuYF4Pxlb2CgAIJlkXLM60IGV29Q+W4T0
K5MbtgYK3UHigTSYK5XjOyCwmLJi/Kqoe/pbJGZVM1J6i+uydx37xvj94X4pY2nS
uxromXZBvoVwkRfCjNTXkKOx5nTAK6ruvhfS6NYImK6pzs/qHWMVmXCI2e4p9aJ/
uptMaKBNYTyP1CsC6WeK9tiKET2BvLYqEqslFrdyXoTwWUexO+uRyPlbZfYg6vPG
1vcmnZw5EeuIlwtH1ETaaQ7r+wT8jjcU/FG3TZzBYTLGX3NO2cIuytl2QaRthVGp
tTwgLWcarxhroO5ksQWARGpbDPeVOZzi2vjDrueKYaa8XFya5JTaiA/oX4AbtBXN
oyh672CABFWoyB7VRrDPZc74lH8BQpK8f4n+vRcnlFlkr3RraQg=
=ayAx
-----END PGP SIGNATURE-----

--Apple-Mail=_F11E381F-5EBA-4472-8489-B442AD31809D--


From nobody Wed Jul 29 11:59:56 2020
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 489013A0E33 for <quic@ietfa.amsl.com>; Wed, 29 Jul 2020 11:59:55 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 JrzOgKIdAks3 for <quic@ietfa.amsl.com>; Wed, 29 Jul 2020 11:59:53 -0700 (PDT)
Received: from mail-il1-x12c.google.com (mail-il1-x12c.google.com [IPv6:2607:f8b0:4864:20::12c]) (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 266F53A0E32 for <quic@ietf.org>; Wed, 29 Jul 2020 11:59:53 -0700 (PDT)
Received: by mail-il1-x12c.google.com with SMTP id i138so14431401ild.9 for <quic@ietf.org>; Wed, 29 Jul 2020 11:59:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=gJojP76ybR7cdQKS4+VPqY0sle7NEDFsCwsmadjyE/M=; b=GEZkueNL9kP4JbWMX2/i66ieJkGiWUaz2vx/keXtLSQV90dlQ1l0T4VpzTcYVk3jdE xqdcy4XSgBOHTWpAVl8HyB3ufWkFvwgWk2PiGLcRvZcu9TOySFwG/6HvR7f3SMspcslS 1SJUtJLgynjDd1oPVQ1U8749NnEad8H+izijjxA7yDJbyOTj48DF79p8Z5dTdb1yysqJ tTNGFul1mYVdl4azXEtSj6T5hjYTMzZ4rbEfd5mFZQ0ecBmh1hZzO35QKlFo16L8D2ke c1QqUi/eMn1NYFUThWlQTwdL6ASsIeBYEYDEkeLUJYYydigrmG3+c3yfLUVqeS+yyhWQ oeuQ==
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=gJojP76ybR7cdQKS4+VPqY0sle7NEDFsCwsmadjyE/M=; b=HNcOiT7bE+I2Y8ohTOyTMVQuFTvbO8Igy8vEdimfjpxefZ+DlBUjRPJFcGQj1Day5O cFaz9KLBoLYmZTlxhAqdPnM8yXtx+GTWhKt2HDz9JkLJPRn2sPX374J3cvvQsj0RutUl 95QE+E2utoAgmpirXvvaizA8Iqzm5Eks0lOFacdeU1ulMFXvxu8o1qRNr8w42AN1WXbC LFUOaaAkz7/fsZsvosnxVNpsXlT662F7THILpKkPHYsGaH+6xHl2RcLbWQAAi4Ld5aqt G1Zd0uUWw3UrAqAfDk0hzMpEIpUF6lMYzjz6ESra4qz446MfnIPJ8D7E/FljzV+ad7uZ UCJw==
X-Gm-Message-State: AOAM530FchLfrUeMtqaZmOJq4fATIRjVi03U1aB6Kvz1fQF0w0V6aeNu EWjIaRGcO8YZngboGrGKb3OyjYX5cXIgWrxK7Z+gOrJu
X-Google-Smtp-Source: ABdhPJw/UN7FpGfYERqaC2oNiK3CS0lf0YCeU110vvUsBUNbG3svKMJm/PRUcEBwUjRgPkGo0OiJ3uGCGaezWLbR4Hc=
X-Received: by 2002:a05:6e02:c6b:: with SMTP id f11mr6536293ilj.272.1596049192132;  Wed, 29 Jul 2020 11:59:52 -0700 (PDT)
MIME-Version: 1.0
From: Martin Duke <martin.h.duke@gmail.com>
Date: Wed, 29 Jul 2020 11:59:41 -0700
Message-ID: <CAM4esxR82Nwv3LgEv_Wx-ExAvbt88gSPB=YkV97iy8F9t_uGPw@mail.gmail.com>
Subject: Consensus to delete Obfuscated CID?
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002423fd05ab992918"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/llvU3t9pXsUmClYD0QRQ0urrOZc>
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, 29 Jul 2020 18:59:55 -0000

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

The sense of the room today was that the Obfuscated CID algorithm was
perhaps the worst of all worlds: complicated and fake-secure. I got
feedback that if we're going to be insecure, just do so explicitly with
plaintext.

Before I delete a ton of text and code, are there any objections to doing
this?

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

<div dir=3D"ltr">The sense of the room today was that the Obfuscated CID al=
gorithm was perhaps the worst of all worlds: complicated and fake-secure. I=
 got feedback that if we&#39;re going to be insecure, just do so explicitly=
 with plaintext.<div><br></div><div>Before I delete a ton of text and code,=
 are there any objections to doing this?</div></div>

--0000000000002423fd05ab992918--


From nobody Wed Jul 29 12:03:49 2020
Return-Path: <nharper@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 1E35C3A0E36 for <quic@ietfa.amsl.com>; Wed, 29 Jul 2020 12:03:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.6
X-Spam-Level: 
X-Spam-Status: No, score=-17.6 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, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, 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 FMjTEsf7yHZJ for <quic@ietfa.amsl.com>; Wed, 29 Jul 2020 12:03:46 -0700 (PDT)
Received: from mail-ot1-x32b.google.com (mail-ot1-x32b.google.com [IPv6:2607:f8b0:4864:20::32b]) (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 2E9703A0E50 for <quic@ietf.org>; Wed, 29 Jul 2020 12:02:58 -0700 (PDT)
Received: by mail-ot1-x32b.google.com with SMTP id a65so9125546otc.8 for <quic@ietf.org>; Wed, 29 Jul 2020 12:02:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kr9VI2+A4pzlkcTBM8JWA5ST3vOZlCjLQmEwtp/jJ9w=; b=o/aztz0AEDRMsi7E+HN7A8rySzVh7npw0BsCMOPpDAuivlfjcc3GitRyyd/iGu3oGN vKI1ze4wXWx3wZuAeI8wgudhgPpKDZ8okCsjsNvdrp8/3zvpisLJKCSMSqzzjMTdqO8B fdeThzaZkzJOV5BmZPnl1TwQ9+8PZ7f8qAjde5JlZbPcOKwei2Pn2LdpyqV36ip/79sK Fj6NKPS2pVgcuBWgdLyojuEhCh0eqiCLuYnrEMUToyww8xB8EbYjPWgYJc/PAToFmctd TlvfvUyf6Sp0ruxIiorY8d1NZVU8aTgdp/X7UNbew7oavNl3d1QFqBJNVc/qAWhRsILC uwoQ==
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=kr9VI2+A4pzlkcTBM8JWA5ST3vOZlCjLQmEwtp/jJ9w=; b=tjYzHy8UIGfwZApFENSCM0FFEeMjiAFWikR4VVqQcP6BUc0KO/BmVTRpb0iT/fE8P7 SVIOm4YcK63d90MYz62ht+jkMiOiVtRWRmhA/z2Qzo4v88w2hHnh7Y3uc1c4dUzyQbsA eQ/HRtftwxMJSt6aE0wmsEGuV9tg3BFx/n6G7QEAI1bAKz2ad69amcrZ70/rDuh8zvyL z/zN43HN3HSRw1UxI+ZPImI3lJ6Ifh94widzDs7uhzamq5nzBxXBJ5ETfSxtUCHlsnSB rTgJPMuij89jcTenCGUg+hoF1kR14YdwMjgWNLBTLVOvL9OGF2uy8CzeZrDrOspVk4Me xtZg==
X-Gm-Message-State: AOAM5304UiEhJncsdJ/lYaLZtRn2u5KdzEsUa6bOrB+i93NhH4YuA37u Mx6MecbwNTr/JmXKLqWmM7JY0mqwVj5DDycrrhZ9Cg==
X-Google-Smtp-Source: ABdhPJw0A24HGsIDe5ljju2XLGjvTd1TR0VmS5aM7lwzLZYllX8LAWt6EeSlxPLX5B6XdiU5oZ8Du9M8XNA92tlsnpo=
X-Received: by 2002:a05:6830:1d6c:: with SMTP id l12mr29336164oti.275.1596049376786;  Wed, 29 Jul 2020 12:02:56 -0700 (PDT)
MIME-Version: 1.0
References: <CAM4esxR82Nwv3LgEv_Wx-ExAvbt88gSPB=YkV97iy8F9t_uGPw@mail.gmail.com>
In-Reply-To: <CAM4esxR82Nwv3LgEv_Wx-ExAvbt88gSPB=YkV97iy8F9t_uGPw@mail.gmail.com>
From: Nick Harper <nharper@google.com>
Date: Wed, 29 Jul 2020 12:02:45 -0700
Message-ID: <CACdeXiJiRLyJP+pAVwBMZNxcqQuRRakkgzFqKTVvMY9z17BW=w@mail.gmail.com>
Subject: Re: Consensus to delete Obfuscated CID?
To: Martin Duke <martin.h.duke@gmail.com>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000261e6505ab99344a"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/n-T_69-HS6AFowUaj62kEPHGrJs>
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, 29 Jul 2020 19:03:47 -0000

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

Let's delete it.

On Wed, Jul 29, 2020 at 12:00 PM Martin Duke <martin.h.duke@gmail.com>
wrote:

> The sense of the room today was that the Obfuscated CID algorithm was
> perhaps the worst of all worlds: complicated and fake-secure. I got
> feedback that if we're going to be insecure, just do so explicitly with
> plaintext.
>
> Before I delete a ton of text and code, are there any objections to doing
> this?
>

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

<div dir=3D"ltr">Let&#39;s delete it.</div><br><div class=3D"gmail_quote"><=
div dir=3D"ltr" class=3D"gmail_attr">On Wed, Jul 29, 2020 at 12:00 PM Marti=
n Duke &lt;<a href=3D"mailto:martin.h.duke@gmail.com">martin.h.duke@gmail.c=
om</a>&gt; wrote:<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=
"><div dir=3D"ltr">The sense of the room today was that the Obfuscated CID =
algorithm was perhaps the worst of all worlds: complicated and fake-secure.=
 I got feedback that if we&#39;re going to be insecure, just do so explicit=
ly with plaintext.<div><br></div><div>Before I delete a ton of text and cod=
e, are there any objections to doing this?</div></div>
</blockquote></div>

--000000000000261e6505ab99344a--


From nobody Wed Jul 29 12:06:16 2020
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 4D2603A0E34 for <quic@ietfa.amsl.com>; Wed, 29 Jul 2020 12:06:15 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 DEGYpVfgjQi4 for <quic@ietfa.amsl.com>; Wed, 29 Jul 2020 12:06:14 -0700 (PDT)
Received: from mail-io1-xd34.google.com (mail-io1-xd34.google.com [IPv6:2607:f8b0:4864:20::d34]) (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 1C3343A0E3C for <quic@ietf.org>; Wed, 29 Jul 2020 12:06:14 -0700 (PDT)
Received: by mail-io1-xd34.google.com with SMTP id a5so10442103ioa.13 for <quic@ietf.org>; Wed, 29 Jul 2020 12:06:14 -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=qoQHZ1pjXh16nPMpYHCzRSgB/WoDBWBqYPK09+qnHdI=; b=aplTucPQ8BwlPqxeCVsA38bM87r7kXq7AtncItCJ9N6U0NfeVEjQPns9d5hTk7nxIc OoDax0vfRBzb0PUvCV25ZwEuIrnb7LQnsCv4w3+jVfF8lTF0vScgd0zZERmDlAFS+eH9 nUgWNzyiyv8JgaRu5+vA3+MQTjZ+LUUtfUTbjQxa2cUh+//l0ZFVj/e+BjiFe3OvJqHj 4ltjvpfHkNq53tKfF54kZgbJvMHVbh6r9n0XaaaMb0UoA5PdL9Zqsq1uSRpzyhP5n5W9 UR1Z4AjujE+WZJ/H1zWsUcAx8wDNyrISLSMRXpz1k8RgyHe5r8Gzk1X9U567zESbk16D gMYQ==
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=qoQHZ1pjXh16nPMpYHCzRSgB/WoDBWBqYPK09+qnHdI=; b=kVbDK98QFB0iGjRT4it1YT9KB0y9kM2rltRiBNZneIQ3iSGRl6jtFj4CPWKxgEl8vU RSVsIc5Q1zVcIFs2hu2J6dwvTfjGda5i8H3OWx1tH83ZskZDoOGAx3OCJELGcJbmtj1L qTiSMbRsb07LN89ZSJ5dlmsOrYb/gKygjb/DariHcjMFsL6+4LWjXC44mDMJUo1UBAoz xMtzyFEJYy1LWcHyiOjltcawE724JJchPGBzL+WHjgEeGC8q7dJgS/Vtj27oaJwkx1gK WtXIJHGxmXOP1V6RioqwQpMjvCx3Tu3/EJsvpFo8s25G6WBNzrsc4xooxmGUl5ZSB0aN y18g==
X-Gm-Message-State: AOAM5329s+Px394IuL4e6mFLOYeU2LhRstU494ELMH+Gs1/tZKFaHRaX vyCC6doRAXujdsiTBJy2AosuJvVfo66V5Zbgr9c=
X-Google-Smtp-Source: ABdhPJwHCGEsiif1rIFKCOigoOci0gzTKZRDfEKP3TvqFVX11VavUkwaGceY3wA6Zs8Suo5xanb+wcYUKStLiVRdQq0=
X-Received: by 2002:a6b:e216:: with SMTP id z22mr19763523ioc.97.1596049573481;  Wed, 29 Jul 2020 12:06:13 -0700 (PDT)
MIME-Version: 1.0
References: <CAM4esxR82Nwv3LgEv_Wx-ExAvbt88gSPB=YkV97iy8F9t_uGPw@mail.gmail.com> <CACdeXiJiRLyJP+pAVwBMZNxcqQuRRakkgzFqKTVvMY9z17BW=w@mail.gmail.com>
In-Reply-To: <CACdeXiJiRLyJP+pAVwBMZNxcqQuRRakkgzFqKTVvMY9z17BW=w@mail.gmail.com>
From: Martin Duke <martin.h.duke@gmail.com>
Date: Wed, 29 Jul 2020 12:05:59 -0700
Message-ID: <CAM4esxQJSNNFjN=6BL29rSa96HNjg4wbrQ1tFGdm0uov7k6N6g@mail.gmail.com>
Subject: Re: Consensus to delete Obfuscated CID?
To: Nick Harper <nharper@google.com>
Cc: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000df12e405ab993fc9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/kt5o1MdgJUovk04Nka1NKsC9zHs>
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, 29 Jul 2020 19:06:15 -0000

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

I forgot to add that you can comment in the issue as well.

https://github.com/quicwg/load-balancers/issues/47

On Wed, Jul 29, 2020 at 12:02 PM Nick Harper <nharper@google.com> wrote:

> Let's delete it.
>
> On Wed, Jul 29, 2020 at 12:00 PM Martin Duke <martin.h.duke@gmail.com>
> wrote:
>
>> The sense of the room today was that the Obfuscated CID algorithm was
>> perhaps the worst of all worlds: complicated and fake-secure. I got
>> feedback that if we're going to be insecure, just do so explicitly with
>> plaintext.
>>
>> Before I delete a ton of text and code, are there any objections to doing
>> this?
>>
>

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

<div dir=3D"ltr">I forgot to add that you can comment in the issue as well.=
<div><br></div><div><a href=3D"https://github.com/quicwg/load-balancers/iss=
ues/47">https://github.com/quicwg/load-balancers/issues/47</a>=C2=A0=C2=A0<=
br></div></div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gma=
il_attr">On Wed, Jul 29, 2020 at 12:02 PM Nick Harper &lt;<a href=3D"mailto=
:nharper@google.com">nharper@google.com</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"><div dir=3D"ltr">Let&#39;s delete it=
.</div><br><div class=3D"gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr"=
>On Wed, Jul 29, 2020 at 12:00 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></div><blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8e=
x;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"=
>The sense of the room today was that the Obfuscated CID algorithm was perh=
aps the worst of all worlds: complicated and fake-secure. I got feedback th=
at if we&#39;re going to be insecure, just do so explicitly with plaintext.=
<div><br></div><div>Before I delete a ton of text and code, are there any o=
bjections to doing this?</div></div>
</blockquote></div>
</blockquote></div>

--000000000000df12e405ab993fc9--


From nobody Wed Jul 29 15:25:12 2020
Return-Path: <spencerdawkins.ietf@gmail.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6D4143A0886 for <quic@ietfa.amsl.com>; Wed, 29 Jul 2020 15:25:10 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 0LDX0MWHS0K0 for <quic@ietfa.amsl.com>; Wed, 29 Jul 2020 15:25:08 -0700 (PDT)
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 15BA13A087F for <quic@ietf.org>; Wed, 29 Jul 2020 15:25:07 -0700 (PDT)
Received: by mail-lj1-x22a.google.com with SMTP id r19so26724461ljn.12 for <quic@ietf.org>; Wed, 29 Jul 2020 15:25:07 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025;  h=mime-version:from:date:message-id:subject:to; bh=jEHuKA9Nwv+e486K8ZvBvLFR5AIFWaeBz1s5wlCnwys=; b=pBTT4NZ5l1fIG5/VB+xdF+KzQa1u8ffeXZkgh1bjX3NLBQu5rQplMk/WqRF1orod2u fVxsGBXAzIjQHqXGMdlI9q7IuIcxIrOVLlhXNIfNp8QC4ioyMgvJ1SrEX3xrw41AJAOq KAQLNXC+mLYHPgf599WFUqs6sppNlujS/LhyTn/6mggTAiKK7ZxoQrjLY5leGbQ84Nrl R9TEEIjdVbWr+faT7GKb9bJ5scgeqnbxJAyrMvLNF+Rpx74+29OOfvARsAVhIAVdJSwq I5TiLKvBe456V6UfCFHmj4EepxINkV7q2DS3C+2i/YcMRw+isiKK2iDR8BnXUi5DmYk+ QCrw==
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=jEHuKA9Nwv+e486K8ZvBvLFR5AIFWaeBz1s5wlCnwys=; b=JWAvc0M9ukVVQbFXyJBvrdAIF3y5+s9XCNrkL1kjMOPB5p6+UZYS3sPsbEeBvQ9B3O LR2AuDq+TU35ZsRpRD/lASULB+aEAzhEibc/9x2rTOP5FX9VGAAzXv0wgOQDge6m67vi MXvTKeP+Gx+McdFLQQLiCsDGXplhsxKRNJeciZbFwKiJYL69TJKnb9tdESbqO65ZWibt Gqk/8PhnsUAN+itCXz1Dx9uG68zlsNuFLsziYRtvu8O1i8CQX6fUpxjwN5DvbpCClRyk SIDFmflqKsyugYSY11HXja9bFcRTFr8M9Dq9ESUIL+VySQ6mK/QYCg2IrESpvVcu2fJ4 cTKg==
X-Gm-Message-State: AOAM533ytTzNZhlQlSMJCTiLJbJHVrHr3oaGHQD3CajVmCVU6E2YACdK f6cO9ITpbWGWmVBw8bI8Rcdu6ZmqmQK+y4KhiQ4l2mYv
X-Google-Smtp-Source: ABdhPJyQ6Uo3zdDQ8CXT3V+AKlPSfRLHEYQYKxhTaivqU6+y45U+H2wpPyEW+Qsr/oJNPW1WI4sVLCZQeHBV9WEfuWg=
X-Received: by 2002:a2e:a583:: with SMTP id m3mr6282ljp.135.1596061505020; Wed, 29 Jul 2020 15:25:05 -0700 (PDT)
MIME-Version: 1.0
From: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>
Date: Wed, 29 Jul 2020 17:24:38 -0500
Message-ID: <CAKKJt-cMF1ptFHNJk_hG+oo5Jo2_x-tNixsMFte1GXGK9g23Fw@mail.gmail.com>
Subject: Translating Spencer's answers to questions on the ATSSS update in QUIC today
To: IETF QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000000be6da05ab9c079b"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/mQF-XXylzN45N_NcRigTE5Ok9Po>
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, 29 Jul 2020 22:25:11 -0000

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

Because the questions I was asked were REALLY important, I went back
through the excellent notes and made some clarifications.

The questions I was asked, and my answers, now read as follows:

   - Jana Iyengar: there=E2=80=99s a race condition: is 3GPP actually doing=
 work on
   things here in QUIC to make this work?
   - Spencer Dawkins: no, absolutely not. I skipped over the bottom of
   slide 2, which said that the participants on the draft want to do work i=
n
   the IETF and 3GPP agrees with that. =E2=80=9CRace conditions=E2=80=9D ar=
e mainly between
   3GPP deadlines and IETF momentum. This is not new, but now we=E2=80=99re=
 coupled
   more closely with 3GPP than we=E2=80=99ve been for other recent 3GPP dep=
endencies
   on IETF work.
   - David Schinazi: I=E2=80=99ve seen discussion about 3GPP MPQUIC, impres=
sion is
   that outsiders are thinking: yes, 3GPP is doing MPQUIC, it=E2=80=99s hap=
pening! But
   they clearly are not=E2=80=A6 this work needs to be done in the IETF. We=
 should
   really clear up that confusion, because right now it=E2=80=99s a mess
   - Spencer Dawkins: I understand the confusion, part of this is race
   condition between how quickly we are moving in the IETF and how quickly
   people outside the IETF seem to need what we=E2=80=99re specifying.

There was a parallel conversation in jabber that I wasn't following in
parallel, but since I'm already typing, I'll reproduce that here:

[12:35:06] <Martin Thomson> Does this mean that 3GPP will do the work if
the IETF does not?

(Answer is the same as I gave Jana above)

[12:38:03] <Alissa Cooper> We should probably get this sorted via our
liaisons
[12:38:21] <Mirja K=C3=BChlewind> 3GPP is not working on MPQUIC but they ci=
te
the MPQUIC draft
[12:38:39] <Martin Thomson> Mirja, does that mean that they intend to
*depend* on that draft?
[12:38:45] <Jana Iyengar> I think David's point is about signaling, but I
don't know if we can really sort out what people say to the world about
what _they believe_ is actually happening
[12:38:48] <Mirja K=C3=BChlewind> they are aware that this is not a working
group item but the quic charter says that quic will work on it...

I'm not sure whether Martin Duk's next line was in this context, but based
on timing, I'm including it for completeness :-)

[12:39:00] <Martin Duke> bummer

I answered Alissa on her point about liaisons

[12:40:34] <spencerdawkins> @Alissa, understood. We can send information to
3GPP at any moment as participants, but 3GPP can only send formal liaisons
back from plenaries. We're working to tie that more closely together on
this specific topic, but liaisons will be fine for heavy lifting.

By this I meant that in discussions during SA#88 in early July, it was
decided that SA2 could also send liaisons to IETF after SA2 plenaries,
rather than waiting for SA plenaries, which happen only four times per
year.

Every improvement is an improvement.

I hope this is helpful.

Best,

Spencer

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

<div dir=3D"ltr">Because the questions I was asked were REALLY important, I=
 went back through the excellent notes and made some clarifications.<div><b=
r></div><div>The questions I was asked, and my answers, now read as=C2=A0fo=
llows:</div><div><ul><li>Jana Iyengar: there=E2=80=99s a race condition: is=
 3GPP actually doing work on things here in QUIC to make this work?<br></li=
><li>Spencer Dawkins: no, absolutely not. I skipped over the bottom of slid=
e 2, which said that the participants on the draft want to do work in the I=
ETF and 3GPP agrees with that. =E2=80=9CRace conditions=E2=80=9D are mainly=
 between 3GPP deadlines and IETF momentum. This is not new, but now we=E2=
=80=99re coupled more closely with 3GPP than we=E2=80=99ve been for other r=
ecent 3GPP dependencies on IETF work.<br></li><li>David Schinazi: I=E2=80=
=99ve seen discussion about 3GPP MPQUIC, impression is that outsiders are t=
hinking: yes, 3GPP is doing MPQUIC, it=E2=80=99s happening! But they clearl=
y are not=E2=80=A6 this work needs to be done in the IETF. We should really=
 clear up that confusion, because right now it=E2=80=99s a mess<br></li><li=
>Spencer Dawkins: I understand the confusion, part of this is race conditio=
n between how quickly we are moving in the IETF and how quickly people outs=
ide the IETF seem to need what we=E2=80=99re specifying.<br></li></ul><div>=
There was a parallel conversation in jabber that I wasn&#39;t following in =
parallel, but since I&#39;m already typing, I&#39;ll reproduce that here:</=
div></div><div><br></div><div>[12:35:06] &lt;Martin Thomson&gt; Does this m=
ean that 3GPP will do the work if the IETF does not?</div><div><br></div><d=
iv>(Answer is the same as I gave Jana above)</div><div><br>[12:38:03] &lt;A=
lissa Cooper&gt; We should probably get this sorted via our liaisons</div><=
div>[12:38:21] &lt;Mirja K=C3=BChlewind&gt; 3GPP is not working on MPQUIC b=
ut they cite the MPQUIC draft<br>[12:38:39] &lt;Martin Thomson&gt; Mirja, d=
oes that mean that they intend to *depend* on that draft?<br>[12:38:45] &lt=
;Jana Iyengar&gt; I think David&#39;s point is about signaling, but I don&#=
39;t know if we can really sort out what people say to the world about what=
 _they believe_ is actually happening<br>[12:38:48] &lt;Mirja K=C3=BChlewin=
d&gt; they are aware that this is not a working group item but the quic cha=
rter says that quic will work on it...<br><br></div><div>I&#39;m not sure w=
hether Martin Duk&#39;s next line was in this context, but based on timing,=
 I&#39;m including it for completeness :-)</div><div><br></div><div>[12:39:=
00] &lt;Martin Duke&gt; bummer=C2=A0=C2=A0<br></div><div><br></div><div>I a=
nswered Alissa on her point about liaisons</div><div><br></div><div>[12:40:=
34] &lt;spencerdawkins&gt; @Alissa, understood. We can send information to =
3GPP at any moment as participants, but 3GPP can only send formal liaisons =
back from plenaries. We&#39;re working to tie that more closely together on=
 this specific topic, but liaisons will be fine for heavy lifting.</div><di=
v><br></div><div>By this I meant that in discussions during SA#88 in early =
July, it was decided that SA2 could also send liaisons to IETF after SA2 pl=
enaries, rather than waiting for SA plenaries, which happen only four times=
 per year.=C2=A0</div><div><br></div><div>Every improvement is an improveme=
nt.=C2=A0</div><div><br></div><div>I hope this is helpful.=C2=A0</div><div>=
<br></div><div>Best,</div><div><br></div><div>Spencer</div></div>

--0000000000000be6da05ab9c079b--


From nobody Thu Jul 30 00:17:45 2020
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 0295B3A0EFC for <quic@ietfa.amsl.com>; Thu, 30 Jul 2020 00:17:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=eggert.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 O7GmfbKHmjYp for <quic@ietfa.amsl.com>; Thu, 30 Jul 2020 00:17:41 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 827183A0EA5 for <quic@ietf.org>; Thu, 30 Jul 2020 00:17:41 -0700 (PDT)
Received: from [IPv6:2a00:ac00:4000:400:c19b:720a:bbc2:99dd] (unknown [IPv6:2a00:ac00:4000:400:c19b:720a:bbc2:99dd]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id C16A36126AA for <quic@ietf.org>; Thu, 30 Jul 2020 10:17:30 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1596093450; bh=IW/CjSlqvLkPsUDdi+MBvLAyTT1dGQZaZyS6xx+nFP4=; h=From:Subject:Date:To; b=KW+7aJJqd224c3XPhCFboJDd8YEkpv0VxeHZ3UWtxGHLr0BIQud7CPjzt3TEz7d2s zfolo2wTdqNNWzxybYKDuwUqiDFkWG9oWoCsY2HSno09SmXHyLg7H7RUIh/0Jhto6D cwvPvN23eboo/LpQRpLfcIMAVRCXyBPZau+n7MzU=
From: Lars Eggert <lars@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_01B79412-098C-4129-91E2-E297ECD39858"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: Draft meeting minutes available, please check
Message-Id: <28F921C6-76E9-4DF6-B49A-86FC69E848D9@eggert.org>
Date: Thu, 30 Jul 2020 10:17:30 +0300
To: QUIC WG <quic@ietf.org>
X-MailScanner-ID: C16A36126AA.A30D2
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/CjKbgOwLE8dcZuqdwMfZDJ8Pocc>
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, 30 Jul 2020 07:17:43 -0000

--Apple-Mail=_01B79412-098C-4129-91E2-E297ECD39858
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

Hi,

thanks to out note takers Brian and Robin, our draft minutes from =
yesterday's WG meeting are uploaded to the datatracker and GitHub at =
https://github.com/quicwg/wg-materials/blob/master/ietf108/agenda.md

Please check the minutes and send corrections, ideally as PRs against =
the GitHub version.

Thanks,
Lars

--Apple-Mail=_01B79412-098C-4129-91E2-E297ECD39858
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAl8idAoACgkQVLXDCb9w
wVc28g//RQlxUE/D1y+R/pnJaFRbUYUUOFM3sRu5imutjUdVgrHf18ohYQaVBcr5
Rqv+m97FQlNoGCbaF0EBp0zGgEd7iggs4V3nf5VAYmYkc4DZgXxhtasmTHbew0HU
iyc9gbqqmG10kLX7Ro9lUuJd4PRRjPkjLN8l3FGE1eOuXMqGOsjdjN8ASWnbc2Gx
fAD+2JH6e2+6ZZH2kIEJyB23tVMXuxEa/qSgGFxpA3emJ4WjDc6H99jLzTe2t4UM
LlvfZPaXmpwVzuUhHey0SaIflCj+bwZS/Z/NU9jKebIfqD4hJ6lnQkylINDo8XPI
m7hFVNGdzbB2Be1ASuG/wWfdA+6MI24Qmk/0H/oyq7iHn5zUDwFi9kQ7dDtZHwqx
dGiwdI8lEe7rwGhlVXxgRTZuFoRfusexYsvgEIg0vYCXqyZfkxEAEccY5GxyMVij
oMZQ2EioQNU86bMKoq3viDYpaobboLnZdEFwQ1q4VkauJTbKYD/4aYS0W/56ZU5+
GW2ZyVNoIKDl/55FHflW9M9RjskgMm1u/UQkWuycLYaySGV8rtjvErA94/VNXO0p
XozM/TLO8+CVXMzOVsse4/q9pjr/iTNlfQYexwkpmMwrFbQhXrTfgSgJx7SsD8vT
UGDC314qYgHed8/Jt68s6w9rSRZcnmTIvExQ0CPM4ws0GBzbQRo=
=CoXP
-----END PGP SIGNATURE-----

--Apple-Mail=_01B79412-098C-4129-91E2-E297ECD39858--


From nobody Thu Jul 30 00:18:17 2020
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 283E13A0F0D for <quic@ietfa.amsl.com>; Thu, 30 Jul 2020 00:18:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level: 
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, 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=eggert.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 b4OphRqd-_Ur for <quic@ietfa.amsl.com>; Thu, 30 Jul 2020 00:18:14 -0700 (PDT)
Received: from mail.eggert.org (mail.eggert.org [91.190.195.94]) (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 36D3F3A0F1D for <quic@ietf.org>; Thu, 30 Jul 2020 00:18:14 -0700 (PDT)
Received: from [IPv6:2a00:ac00:4000:400:c19b:720a:bbc2:99dd] (unknown [IPv6:2a00:ac00:4000:400:c19b:720a:bbc2:99dd]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.eggert.org (Postfix) with ESMTPSA id 97ACB6126AA for <quic@ietf.org>; Thu, 30 Jul 2020 10:18:06 +0300 (EEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=eggert.org; s=dkim; t=1596093486; bh=adofsG/hpSp4KslNgLRezQqzJn5mlHhOb9dqEJ2X3ao=; h=From:Subject:Date:References:To:In-Reply-To; b=ivIYK30xRNrPWhET25/9MztuffVipNDCteGLqk2pFVVY+iUAbuJ3TON0zI2bwnPkP /6fBLrlooQjRBzEKXejHEU25TmT2k+DjNJWbI4x7UtPNP2lKuZOWDtzBrmLq6rL/Ss HjjWydTaGbo1iyRUZaU7CWYwj00H2Knuw/nBpHYM=
From: Lars Eggert <lars@eggert.org>
Content-Type: multipart/signed; boundary="Apple-Mail=_AE0FD77D-3B18-45BA-89F5-0B21FDB6F3BE"; protocol="application/pgp-signature"; micalg=pgp-sha512
Mime-Version: 1.0 (Mac OS X Mail 13.4 \(3608.120.23.2.1\))
Subject: Re: Draft meeting minutes available, please check
Date: Thu, 30 Jul 2020 10:18:06 +0300
References: <28F921C6-76E9-4DF6-B49A-86FC69E848D9@eggert.org>
To: QUIC WG <quic@ietf.org>
In-Reply-To: <28F921C6-76E9-4DF6-B49A-86FC69E848D9@eggert.org>
Message-Id: <6B11B195-37D4-43FA-803D-DCE188660CC1@eggert.org>
X-MailScanner-ID: 97ACB6126AA.A3FC9
X-MailScanner: Found to be clean
X-MailScanner-From: lars@eggert.org
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/o9_HUt0_6F5_yqTUVbWBz9ifLtk>
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, 30 Jul 2020 07:18:16 -0000

--Apple-Mail=_AE0FD77D-3B18-45BA-89F5-0B21FDB6F3BE
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=us-ascii

On 2020-7-30, at 10:17, Lars Eggert <lars@eggert.org> wrote:
> https://github.com/quicwg/wg-materials/blob/master/ietf108/agenda.md

Sigh. I meant =
https://github.com/quicwg/wg-materials/blob/master/ietf108/minutes.md

Lars

--Apple-Mail=_AE0FD77D-3B18-45BA-89F5-0B21FDB6F3BE
Content-Transfer-Encoding: 7bit
Content-Disposition: attachment;
	filename=signature.asc
Content-Type: application/pgp-signature;
	name=signature.asc
Content-Description: Message signed with OpenPGP

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

iQIzBAEBCgAdFiEEmpq0ZpSoejRmyhheVLXDCb9wwVcFAl8idC4ACgkQVLXDCb9w
wVe9yg//bF0607uIM2LdXQ9C078jE5FBdvmKVQeldkv8yCzuqACbtlOCiC2/CNjQ
/6AmSWU3QN/2fGQeZKJDGunzkkMY4BAEN50LaSxVnzCrsmD6EV0nhZNme0I/F/TC
hV5FViqRbkSY4quCiCZIn6HkpD5ayu2+HLVVuqcfExSwBmjTSg04QQn/0qxeGWeJ
aiOIN+ZzosPRF94mRMb1nKQEEiVUE46LSm/H0yjr+GvbUUAh0A081GXCOAEqFRGC
7ebfEKkm4DisN+0k9dpEdrKvuEoO093LohKqwVq7CdqlATUWFNQJLlJV0t/fKv4L
S7Gj4/Ry5GZTddqzCAQ5ebUnHk+r1YL5XHomYobm1MC9oKqHl3TW0TJmdDEpPwtA
SYDhQZt+PtLgdIj4T/gBq2PicKaGu7Jzy68bdejmsj3BmeyMbpB+1sFJga5txksT
e9ejzenhWGr5EGK0nqIeRAP6CE1pVIyynOoQjPVD+w+ewxgocP2JZgiBGXSUfNDc
KZB30flyfw61U5G91IS4b9j/H9yuM146ryN2Cgic3srwZ41+rAAqn36h0YAdBOrD
6RTNzt0CNDHYSrk2X8hG+soaUofr72+7b52Un4PEgGKRDDG90/gMibWgCoe5ANln
4H2tGgAwSzXlJMbwtXNo6XrQe6yHZRqvPTslbvk7VHIVxQcm50A=
=V5PX
-----END PGP SIGNATURE-----

--Apple-Mail=_AE0FD77D-3B18-45BA-89F5-0B21FDB6F3BE--


From nobody Thu Jul 30 05:34:06 2020
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 389773A1260 for <quic@ietfa.amsl.com>; Thu, 30 Jul 2020 05:34:03 -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, 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 eR8J6eub5D4L for <quic@ietfa.amsl.com>; Thu, 30 Jul 2020 05:34:01 -0700 (PDT)
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 C1CE13A11EA for <quic@ietf.org>; Thu, 30 Jul 2020 05:33:51 -0700 (PDT)
Received: by mail-qt1-x835.google.com with SMTP id w9so20133343qts.6 for <quic@ietf.org>; Thu, 30 Jul 2020 05:33:51 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=litespeedtech-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:subject:message-id:mail-followup-to:mime-version :content-disposition:user-agent; bh=Q22LV2f2gJ3krqBdBJMgi72t2YJewwDSC3vJchd1J9o=; b=p7rWzIBTmAoQ+nZtTU7wYG3n1jh70lDICHrvkLkEn9l/8DmFrVMbtcRJxlu2l5rzy9 cndhTiNk6FmBo8Wt6ppyuGVHuWZ3dMijzsvl7vDWNuNEQrBh2L0LBF6ZnlR3DIXBrIj2 YCh/bXMh189frX1F2cNclvLqL1jZm3VQHEk/mTscssBsm2joDhpnit2hZKD/5LbGc7iB 0E2FqOupu6qVupbUJtHA6c+8mDoBp83xX0ycJf435o09bbW+bI9fPrMHi8TmlElcEfSo Iu80omag63qbvDgbBrqwls0YknAeudaRoP75ItsT09tMp0mGdHoh222jAMZc2w4r7k9b 5HrQ==
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=Q22LV2f2gJ3krqBdBJMgi72t2YJewwDSC3vJchd1J9o=; b=ExkPbzYxyHQUh43n4cD4zwT23hXXzwPMYK/eOlo3fxEYyDPYCzqvvaiatehZUrEZN0 5E0wgoSlljfTeEDHuyf5mCSBzCYU9IcxSw0nLCIGrY+aO5a1IaplkY8qjW4qijlPXnEJ Wr0ooo8rP6IK91A3FaLyNVT/1YYJfM2U+TcuSjIHYBeVcGtKYvOl54db3q6lZupUniG6 G7Io3GWj566g3Vy3/PiEYikJcWsLMTaYDGHhCUY5rTQ7zQhhmOfHd9cy2tFOd2wAqmNW s7eRQqWzoMq1TpAMLo7Ym3CdvfX1izwKsKfiT2XGEfro2Mt2HdV3jHVRimmd7avQLt/y 7O7w==
X-Gm-Message-State: AOAM5324rVbmvVz/6rHWl+2zuxHKvQEqdgxKJjU49LRiw5AmwQIHYZ4U ns60aCK2tmm8W9JwPugGy422384uYk8=
X-Google-Smtp-Source: ABdhPJy0NkUZJM3F9X6fdVfMNN2bud9iElHCvtR7t/6TrHjcO1R9MAV7tJ6SYdKY6U59z2X+C8deXQ==
X-Received: by 2002:ac8:4252:: with SMTP id r18mr2511260qtm.334.1596112430419;  Thu, 30 Jul 2020 05:33:50 -0700 (PDT)
Received: from lubuntu (ool-44c1d219.dyn.optonline.net. [68.193.210.25]) by smtp.gmail.com with ESMTPSA id r188sm3971873qkd.70.2020.07.30.05.33.49 for <quic@ietf.org> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 30 Jul 2020 05:33:49 -0700 (PDT)
Date: Thu, 30 Jul 2020 08:33:40 -0400
From: Dmitri Tikhonov <dtikhonov@litespeedtech.com>
To: IETF QUIC WG <quic@ietf.org>
Subject: The QUIC Bit Grease: not just for Google
Message-ID: <20200730123339.GB28907@lubuntu>
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.10.1 (2018-07-13)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/PfDvIqV18iu_NqOmY4n5c2a_nrY>
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, 30 Jul 2020 12:34:06 -0000

Hello,

I was just reviewing the minutes and came across the QUIC Bit Grease
discussion [1].  I wanted to point out that there is at least one
more server vendor -- LiteSpeed Technologies -- that supports Google
QUIC and uses the QUIC bit to differentiate between gQUIC and QUIC.

  - Dmitri.

1. https://codimd.ietf.org/notes-ietf-108-quic#Greasing-the-QUIC-Bit-draft


From nobody Thu Jul 30 07:18:27 2020
Return-Path: <jonathan.lennox@8x8.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2B3E33A11C0 for <quic@ietfa.amsl.com>; Thu, 30 Jul 2020 07:18:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level: 
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, 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=8x8.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 HebyDq-yt7xn for <quic@ietfa.amsl.com>; Thu, 30 Jul 2020 07:18:20 -0700 (PDT)
Received: from mail-qk1-x734.google.com (mail-qk1-x734.google.com [IPv6:2607:f8b0:4864:20::734]) (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 F0FEB3A11C7 for <quic@ietf.org>; Thu, 30 Jul 2020 07:18:19 -0700 (PDT)
Received: by mail-qk1-x734.google.com with SMTP id l64so18896896qkb.8 for <quic@ietf.org>; Thu, 30 Jul 2020 07:18:19 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=8x8.com; s=googlemail;  h=from:mime-version:subject:message-id:date:cc:to; bh=F4OpgJS4/SB2fmGfO4PjYwyfkMcVFhK+cD/Uz4M434k=; b=pT5Ps/DWuGuuHfPdiGcEjfdvq5PStCamzb+6nm6ftVANUUyEoaFqlnNgYgyXv75TgE hBol3nMCukoGk+mE327FuvA7tcbUQCmZEn5t9EPip0jYThIdyzmSBn3UxJxhqFCzS67+ NoaNBqX1HOi1QZ0FfEf0N/DovQnlRQ1DbLWPg=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:mime-version:subject:message-id:date:cc:to; bh=F4OpgJS4/SB2fmGfO4PjYwyfkMcVFhK+cD/Uz4M434k=; b=Rz/ihA//ne0+D/sFCvU4Jd1yzSQ1zNTez/hN8bk49WDaqLNzaUqDsliVGz14Z3o13E HIsuDOLUISc510DJUa0sRdYIIApJ1DpDA1RPDjTw0OPVMacZebPrzi8kI+LnxS1Fs5S9 yhpCNaV3fjzf1yQoSg7tMmazFjro0F2nGcDQtzadKmeO98bwXalmlennjLxs+2AY0LLE +fXksF1UgOGbR1406TXlln0tXQ5d1xeLTVuf0dnXpV71hP6m0BH9pbV5vomz0fElvBse 5fdkU75JAthWRRyDODP9jEOQTJMPf0brmNyT0EJaRSssTSZDlP/js6YHD8loX1Gc4pSJ 6cyA==
X-Gm-Message-State: AOAM531xkqOYX2k6gZ61rDtUN+qUP/LTXxwoPPfVs7n+Nz1gAAs+Zamk rITfoUCX1beK5vTJNVHmXbTdCTmxA6f9aA==
X-Google-Smtp-Source: ABdhPJxUUnNfTtZpiKigwEV5Rdycc+835mdnSLrO4epTpF/lKYp4fkap9cW0cQ9qVlvcRd6NXuWOzg==
X-Received: by 2002:ae9:e857:: with SMTP id a84mr40866336qkg.100.1596118698957;  Thu, 30 Jul 2020 07:18:18 -0700 (PDT)
Received: from ?IPv6:2601:86:101:74d0:e502:46de:2133:6bac? ([2601:86:101:74d0:e502:46de:2133:6bac]) by smtp.gmail.com with ESMTPSA id 6sm4045014qkj.134.2020.07.30.07.18.18 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Thu, 30 Jul 2020 07:18:18 -0700 (PDT)
From: Jonathan Lennox <jonathan.lennox@8x8.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3A51E179-BEBF-4574-91C6-79BE51EB98EF"
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.15\))
Subject: Call for Adoption: Multiplexing Scheme Updates for QUIC
Message-Id: <C9AA3682-17B8-43EC-BC22-58F37904AD23@8x8.com>
Date: Thu, 30 Jul 2020 10:18:17 -0400
Cc: quic@ietf.org
To: avt@ietf.org
X-Mailer: Apple Mail (2.3445.104.15)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/4_GlVssiWEZLTxn2F7bcy8BOr1w>
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, 30 Jul 2020 14:18:23 -0000

--Apple-Mail=_3A51E179-BEBF-4574-91C6-79BE51EB98EF
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
	charset=utf-8

(Note this mail is Cc=E2=80=99d to quic@ietf.org <mailto:quic@ietf.org>; =
please keep discussion on avt@ietf.org <mailto:avt@ietf.org>.)

This is a call for adoption in the AVTCore working group of the document =
=E2=80=9CMultiplexing Scheme Updates for QUIC=E2=80=9D, =
https://tools.ietf.org/html/draft-aboba-avtcore-rfc7983bis-00 =
<https://tools.ietf.org/html/draft-aboba-avtcore-rfc7983bis-00> , as the =
basis for a working group item, along with an appropriate milestone.

As a summary for those unfamiliar with the document, it updates RFC 7983 =
to document how QUIC can be demultiplexed from STUN, DTLS, RTP, and =
other protocols common in WebRTC and WebRTC-like systems.

If you have opinions on whether this document should be adopted, please =
respond to the AVTCore mailing list by Friday, August 14th.

Technical comments on the document itself are also always welcome, of =
course!

Thanks,

Jonathan Lennox
AVTCore co-chair


--Apple-Mail=_3A51E179-BEBF-4574-91C6-79BE51EB98EF
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"">(Note=
 this mail is Cc=E2=80=99d to <a href=3D"mailto:quic@ietf.org" =
class=3D"">quic@ietf.org</a>; please keep discussion on <a =
href=3D"mailto:avt@ietf.org" class=3D"">avt@ietf.org</a>.)<div =
class=3D""><br class=3D""></div><div class=3D"">This is a call for =
adoption in the AVTCore working group of the document =E2=80=9CMultiplexin=
g Scheme Updates for QUIC=E2=80=9D,&nbsp;<a =
href=3D"https://tools.ietf.org/html/draft-aboba-avtcore-rfc7983bis-00" =
class=3D"">https://tools.ietf.org/html/draft-aboba-avtcore-rfc7983bis-00</=
a>&nbsp;, as the basis for a working group item, along with an =
appropriate milestone.</div><div class=3D""><br class=3D""></div><div =
class=3D"">As a summary for those unfamiliar with the document, it =
updates RFC 7983 to document how QUIC can be demultiplexed from STUN, =
DTLS, RTP, and other protocols common in WebRTC and WebRTC-like =
systems.</div><div class=3D""><br class=3D""></div><div class=3D"">If =
you have opinions on whether this document should be adopted, please =
respond to the AVTCore mailing list by Friday, August 14th.</div><div =
class=3D""><br class=3D""></div><div class=3D"">Technical comments on =
the document itself are also always welcome, of course!</div><div =
class=3D""><br class=3D""></div><div class=3D"">Thanks,</div><div =
class=3D""><br class=3D""></div><div class=3D"">Jonathan =
Lennox</div><div class=3D"">AVTCore co-chair</div><div class=3D""><br =
class=3D""></div></body></html>=

--Apple-Mail=_3A51E179-BEBF-4574-91C6-79BE51EB98EF--


From nobody Thu Jul 30 10:59:17 2020
Return-Path: <gsalguei@cisco.com>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 5A3ED3A0FFE; Thu, 30 Jul 2020 10:58:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.619
X-Spam-Level: 
X-Spam-Status: No, score=-9.619 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com header.b=WczsHOar; dkim=pass (1024-bit key) header.d=cisco.onmicrosoft.com header.b=pKIpsjHN
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id PC4fJeYinRZy; Thu, 30 Jul 2020 10:58:45 -0700 (PDT)
Received: from rcdn-iport-9.cisco.com (rcdn-iport-9.cisco.com [173.37.86.80]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 420163A0E7E; Thu, 30 Jul 2020 10:58:45 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=5381; q=dns/txt; s=iport; t=1596131925; x=1597341525; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=D25fmb6QEWl1x2Dq5pIHzftXAalj73skRd7g7P4UjOU=; b=WczsHOarGHqctEMhBaJIfHC82V2KFZZO37y85LHAvFppDcLCg1M2rG/H bs/McJS1InnvEv5qznBJeVDjepNUZ29bxEbeLZjnEWK6nfDh5a+oMXlXg 8lFlqzcLRDNjhee7FAwSyhOzzuvoaPOTXZjjzHTRrwZgHynl61CLZNTaY A=;
IronPort-PHdr: =?us-ascii?q?9a23=3ACYoMMhNmqUuZ77g9PyYl6mtXPHoupqn0MwgJ65?= =?us-ascii?q?Eul7NJdOG58o//OFDEvKw13g/ZDcPQ7PcXw+bVsqW1X2sG7N7BtX0Za5VDWl?= =?us-ascii?q?cDjtlehA0vBsOJSCiZZP7nZiA3BoJOAVli+XzoYVgFXs35Yg6arni79zVHHB?= =?us-ascii?q?L5OEJ8Lfj0HYiHicOx2qiy9pTfbh8OiiC6ZOZ5LQ69qkPascxFjA=3D=3D?=
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0ADCACACSNf/49dJa1gHQEBAQEJARI?= =?us-ascii?q?BBQUBggqBUlEHb1gvLAqEK4NGA6FEhGyCUwNVCwEBAQwBARgBCgoCBAEBhEw?= =?us-ascii?q?CF4IXAiQ4EwIDAQELAQEFAQEBAgEGBG2FXAyFcgIEAQEQCwYdAQEsCwEPAgE?= =?us-ascii?q?IBDsDAgICJQsUEQIEDgUigwQBgX5NAy4BDqVSAoE5iGF2gTKDAQEBBYE3AoE?= =?us-ascii?q?Rgk0Ygg4DBoE4gm+DX4Y/GoFBP4ERJxyCTT6CXAEBA4E6AQEfLoJpM4ItknK?= =?us-ascii?q?GXYtWkGYKgl+IW5EkAx6Ce4lLky6RHQyLKZEWg1YCBAIEBQIOAQEFgWojgVd?= =?us-ascii?q?wFTsqAYI+PhIXAg2OH4NxhRSFQnQ3AgYBBwEBAwl8jksBgRABAQ?=
X-IronPort-AV: E=Sophos;i="5.75,415,1589241600";  d="scan'208,217";a="715167967"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by rcdn-iport-9.cisco.com with ESMTP/TLS/DHE-RSA-SEED-SHA; 30 Jul 2020 17:58:44 +0000
Received: from XCH-RCD-003.cisco.com (xch-rcd-003.cisco.com [173.37.102.13]) by rcdn-core-7.cisco.com (8.15.2/8.15.2) with ESMTPS id 06UHwis1024069 (version=TLSv1.2 cipher=AES256-SHA bits=256 verify=FAIL); Thu, 30 Jul 2020 17:58:44 GMT
Received: from xhs-aln-002.cisco.com (173.37.135.119) by XCH-RCD-003.cisco.com (173.37.102.13) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 30 Jul 2020 12:58:44 -0500
Received: from xhs-rcd-001.cisco.com (173.37.227.246) by xhs-aln-002.cisco.com (173.37.135.119) with Microsoft SMTP Server (TLS) id 15.0.1497.2; Thu, 30 Jul 2020 12:58:43 -0500
Received: from NAM10-DM6-obe.outbound.protection.outlook.com (72.163.14.9) by xhs-rcd-001.cisco.com (173.37.227.246) with Microsoft SMTP Server (TLS) id 15.0.1497.2 via Frontend Transport; Thu, 30 Jul 2020 12:58:43 -0500
ARC-Seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=ZoZbbcbkQn9jait2c6lXEPEXlJn3ps8DMIXr2Ld0JKaTeNJMdlWeNXuSJQdYFNPzEhrnaFK6jE1DNA8VZEzm2T7vtcIjkcHRRUIA+KoxFHv84v7VdI7rcAVSIqLSImr0NpwCFUpAwFASv48H6RWhu+9mL2jlEBCDNXe/gab+k17Y09O2mB+goR2jkKmr/3ZtEzJtOSnJubqoLvJHvIYZuggoHY4++gEeN6MsRV/HzmISdgjCTJEM5nueQ95MAW9L0sRsN4ey/jqoAkNSkH7oqSusWmZRMMPwST6lYYKEZxJkf6vbFqMOREfxpaauhyZFNx572ND0ZSiPZHDRfZYJKg==
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=D25fmb6QEWl1x2Dq5pIHzftXAalj73skRd7g7P4UjOU=; b=D2KFuke7uOiwCFk2zNl97rGJsDuGMbMfvoKYy9uUKSmQagE5ISskmhINo8ukwL+uteIEDSvKBrX1EVLBt7Z+eGG5syHt67SG+LesY7Xumh6Wt4EbQLCIyn5wiB5EIZCIM2XqxL5eMHANMhbUXJ9+Q+mZfQKM6YxVrvU9ETjk+af1NW2XzrQuaR00nfYf0wyay1gWA4KV0+bVTSyFPzDUd1/GH/Ys1PwpZ3yidY4CtNGGWXiczFJ5iU4kS7fxEWTJunblIqUsCIwHb1ne8c87VTyJWMILG368WQcJ2sos0EbGDVBQkyOBww3uKb7XFf+PWzTXOXg1ZmUtK7MTMls9DA==
ARC-Authentication-Results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=cisco.com; dmarc=pass action=none header.from=cisco.com; dkim=pass header.d=cisco.com; arc=none
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cisco.onmicrosoft.com;  s=selector2-cisco-onmicrosoft-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-SenderADCheck; bh=D25fmb6QEWl1x2Dq5pIHzftXAalj73skRd7g7P4UjOU=; b=pKIpsjHNsQmI0Bh63kurTPT5zmARvf+tkQ2np0SESw+QTI87tn+r+N0qTd4Dfy8WPY6ll9lhocMsFHm/EP155/fvWjCqxT3traIJqHFFvbxrcV60tS5Fb5MOqjlzeeMdFPOu4L8yq8WAkzwRo7X0XDUgBRN9rtIyGdC4D4Ej7sg=
Received: from BL0PR11MB2930.namprd11.prod.outlook.com (2603:10b6:208:73::25) by BL0PR11MB2961.namprd11.prod.outlook.com (2603:10b6:208:76::23) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384) id 15.20.3239.17; Thu, 30 Jul 2020 17:58:42 +0000
Received: from BL0PR11MB2930.namprd11.prod.outlook.com ([fe80::e922:73a6:5a44:8a72]) by BL0PR11MB2930.namprd11.prod.outlook.com ([fe80::e922:73a6:5a44:8a72%7]) with mapi id 15.20.3216.034; Thu, 30 Jul 2020 17:58:42 +0000
From: "Gonzalo Salgueiro (gsalguei)" <gsalguei@cisco.com>
To: Jonathan Lennox <jonathan.lennox@8x8.com>
CC: "avt@ietf.org" <avt@ietf.org>, "quic@ietf.org" <quic@ietf.org>
Subject: Re: [AVTCORE] Call for Adoption: Multiplexing Scheme Updates for QUIC
Thread-Topic: [AVTCORE] Call for Adoption: Multiplexing Scheme Updates for QUIC
Thread-Index: AQHWZnxwooaDlhS+iEK+cjn7KW/vWKkgaSMA
Date: Thu, 30 Jul 2020 17:58:41 +0000
Message-ID: <4D78061C-F37D-4C4F-90EB-D0D15D195A44@cisco.com>
References: <C9AA3682-17B8-43EC-BC22-58F37904AD23@8x8.com>
In-Reply-To: <C9AA3682-17B8-43EC-BC22-58F37904AD23@8x8.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-mailer: Apple Mail (2.3608.120.23.2.1)
authentication-results: 8x8.com; dkim=none (message not signed) header.d=none;8x8.com; dmarc=none action=none header.from=cisco.com;
x-originating-ip: [104.182.55.116]
x-ms-publictraffictype: Email
x-ms-office365-filtering-correlation-id: 1cf9ec1c-1a0d-46c1-f824-08d834b23220
x-ms-traffictypediagnostic: BL0PR11MB2961:
x-microsoft-antispam-prvs: <BL0PR11MB2961BC72265336677BE07D64C7710@BL0PR11MB2961.namprd11.prod.outlook.com>
x-ms-oob-tlc-oobclassifiers: OLM:8882;
x-ms-exchange-senderadcheck: 1
x-microsoft-antispam: BCL:0;
x-microsoft-antispam-message-info: 2NffERi2HdP2PTSGjmtjG5MO+yRe71X9TQUjno04p7E2cglmS+1X+mQmE4XcajmaAB5Pb/oGgfIFVi1Diu8vhewjTc/lm9bNLSiQ+gx8Z5CM4Ddf4pBXwtyxovTn+kMa24vQ+Qv4OV5DkCfTyv+m7EFRn0WxdBVkqWUp+FWrfeH4CuoD/dJ+W/ekB9rBC8YIHP1xHcN6FU3Eevhzk47qBZIYc/g2qSyLFJGfoL3mCBCgsLXOSLNz4SgqH9rlY/GGNztj1jnnQ5igz7xfZDnatcWBGJh4FKtgQC4Ezl6v5c5/mO0SAlzajXTQDeLznytdiIfCDS4w0mf/z0hkeHyNXNXrKOzvCAd1dmjoR/ZQZoTXCCifNLiK50SjMvhUna+amvctzI1/YJcTRbprqJNRjg==
x-forefront-antispam-report: CIP:255.255.255.255; CTRY:; LANG:en; SCL:1; SRV:;  IPV:NLI; SFV:NSPM; H:BL0PR11MB2930.namprd11.prod.outlook.com; PTR:; CAT:NONE;  SFTY:; SFS:(4636009)(366004)(376002)(39860400002)(136003)(396003)(346002)(8676002)(33656002)(83380400001)(71200400001)(8936002)(4326008)(966005)(6916009)(316002)(54906003)(15650500001)(6486002)(36756003)(166002)(5660300002)(86362001)(6506007)(26005)(186003)(6512007)(66446008)(66946007)(53546011)(66556008)(2906002)(66476007)(478600001)(64756008)(2616005)(76116006); DIR:OUT; SFP:1101; 
x-ms-exchange-antispam-messagedata: NKiMxFbmdhwOwQ02ICelc0ME0S2wSEqbE+jkWxDqwS7VLd5JiVQFxSgGuKICuxBQhW7CG3il3bsZdY7SqlC1kZCSDf2G0Drepm6Pgj2ZpO02zwoG3n/T2d6DFiirAEpF56wFsS4htFltX+diPCUrYW4n1m47Grtmk/1eEJjuFnqSa2alDZkZYUeexlmLoPAuNx91m1POU1kf/tVoDM0tSlXpQTwNODfPYCmXBBLPXNKiCBdUrJA2zaPcDKGEuNr9KIHh/ztYPljdeIRnEiK4Z07FNuoz38MYRDeSqs3Kl1umECac8f4rvmyHuOzQ/o+J5npHvhqZu8biCXMRQ9kvJdWIAxtCM2vJvcYFuXwkZGq1lPy3QCArIlpASsdc2RkW+ureEZu33AZMoKt38ttDCu8BFGe8Q6vTQHkpqMld/yfxvroAa20VrDPaG3LYiradtoz4JpDfbXiI2rGAC1l3nWjuk5OB+yqc6ilsFFfTwFKYTu9tox5kbEhD1ZBdKpUodHU1XJlaVUwj/q9k9cFBmkgPMGOasHiOlUR8m+jWfdQgSQZUiFDKUe/CjamWMW2H6AtvntRuv1h75/9VeQQtRnSgyv/rYOlrjY9HiSHsxBCBydsn3ZqYDlhoz3+xV70R+QCDtRojfwphddO8bJGZxQ==
x-ms-exchange-transport-forked: True
Content-Type: multipart/alternative; boundary="_000_4D78061CF37D4C4F90EBD0D15D195A44ciscocom_"
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-AuthAs: Internal
X-MS-Exchange-CrossTenant-AuthSource: BL0PR11MB2930.namprd11.prod.outlook.com
X-MS-Exchange-CrossTenant-Network-Message-Id: 1cf9ec1c-1a0d-46c1-f824-08d834b23220
X-MS-Exchange-CrossTenant-originalarrivaltime: 30 Jul 2020 17:58:41.3445 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 5ae1af62-9505-4097-a69a-c1553ef7840e
X-MS-Exchange-CrossTenant-mailboxtype: HOSTED
X-MS-Exchange-CrossTenant-userprincipalname: bSiIyu0qAF7eNePjC1Ls8m5A6V4iqQRidT53qr0PKx88e+iJPhEqnIcOaxV30q5Zn6fhVe0iMLWldM9KfzPKrA==
X-MS-Exchange-Transport-CrossTenantHeadersStamped: BL0PR11MB2961
X-OriginatorOrg: cisco.com
X-Outbound-SMTP-Client: 173.37.102.13, xch-rcd-003.cisco.com
X-Outbound-Node: rcdn-core-7.cisco.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/XTEvyRaeqz5lGynqO5b48ScjnB4>
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, 30 Jul 2020 17:58:48 -0000

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

SSBzdXBwb3J0IGFkb3B0aW9uIGJ5IHRoZSBXRy4NCg0KQ2hlZXJzLA0KDQpHb256YWxvDQoNCk9u
IEp1bCAzMCwgMjAyMCwgYXQgMTA6MTggQU0sIEpvbmF0aGFuIExlbm5veCA8am9uYXRoYW4ubGVu
bm94QDh4OC5jb208bWFpbHRvOmpvbmF0aGFuLmxlbm5veEA4eDguY29tPj4gd3JvdGU6DQoNCihO
b3RlIHRoaXMgbWFpbCBpcyBDY+KAmWQgdG8gcXVpY0BpZXRmLm9yZzxtYWlsdG86cXVpY0BpZXRm
Lm9yZz47IHBsZWFzZSBrZWVwIGRpc2N1c3Npb24gb24gYXZ0QGlldGYub3JnPG1haWx0bzphdnRA
aWV0Zi5vcmc+LikNCg0KVGhpcyBpcyBhIGNhbGwgZm9yIGFkb3B0aW9uIGluIHRoZSBBVlRDb3Jl
IHdvcmtpbmcgZ3JvdXAgb2YgdGhlIGRvY3VtZW50IOKAnE11bHRpcGxleGluZyBTY2hlbWUgVXBk
YXRlcyBmb3IgUVVJQ+KAnSwgaHR0cHM6Ly90b29scy5pZXRmLm9yZy9odG1sL2RyYWZ0LWFib2Jh
LWF2dGNvcmUtcmZjNzk4M2Jpcy0wMCAsIGFzIHRoZSBiYXNpcyBmb3IgYSB3b3JraW5nIGdyb3Vw
IGl0ZW0sIGFsb25nIHdpdGggYW4gYXBwcm9wcmlhdGUgbWlsZXN0b25lLg0KDQpBcyBhIHN1bW1h
cnkgZm9yIHRob3NlIHVuZmFtaWxpYXIgd2l0aCB0aGUgZG9jdW1lbnQsIGl0IHVwZGF0ZXMgUkZD
IDc5ODMgdG8gZG9jdW1lbnQgaG93IFFVSUMgY2FuIGJlIGRlbXVsdGlwbGV4ZWQgZnJvbSBTVFVO
LCBEVExTLCBSVFAsIGFuZCBvdGhlciBwcm90b2NvbHMgY29tbW9uIGluIFdlYlJUQyBhbmQgV2Vi
UlRDLWxpa2Ugc3lzdGVtcy4NCg0KSWYgeW91IGhhdmUgb3BpbmlvbnMgb24gd2hldGhlciB0aGlz
IGRvY3VtZW50IHNob3VsZCBiZSBhZG9wdGVkLCBwbGVhc2UgcmVzcG9uZCB0byB0aGUgQVZUQ29y
ZSBtYWlsaW5nIGxpc3QgYnkgRnJpZGF5LCBBdWd1c3QgMTR0aC4NCg0KVGVjaG5pY2FsIGNvbW1l
bnRzIG9uIHRoZSBkb2N1bWVudCBpdHNlbGYgYXJlIGFsc28gYWx3YXlzIHdlbGNvbWUsIG9mIGNv
dXJzZSENCg0KVGhhbmtzLA0KDQpKb25hdGhhbiBMZW5ub3gNCkFWVENvcmUgY28tY2hhaXINCg0K
X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18NCkF1ZGlvL1Zp
ZGVvIFRyYW5zcG9ydCBDb3JlIE1haW50ZW5hbmNlDQphdnRAaWV0Zi5vcmc8bWFpbHRvOmF2dEBp
ZXRmLm9yZz4NCmh0dHBzOi8vd3d3LmlldGYub3JnL21haWxtYW4vbGlzdGluZm8vYXZ0DQoNCg==

--_000_4D78061CF37D4C4F90EBD0D15D195A44ciscocom_
Content-Type: text/html; charset="utf-8"
Content-ID: <0A0EF58828622144919A53AF8030C66E@namprd11.prod.outlook.com>
Content-Transfer-Encoding: base64

PGh0bWw+DQo8aGVhZD4NCjxtZXRhIGh0dHAtZXF1aXY9IkNvbnRlbnQtVHlwZSIgY29udGVudD0i
dGV4dC9odG1sOyBjaGFyc2V0PXV0Zi04Ij4NCjwvaGVhZD4NCjxib2R5IHN0eWxlPSJ3b3JkLXdy
YXA6IGJyZWFrLXdvcmQ7IC13ZWJraXQtbmJzcC1tb2RlOiBzcGFjZTsgbGluZS1icmVhazogYWZ0
ZXItd2hpdGUtc3BhY2U7IiBjbGFzcz0iIj4NCkkgc3VwcG9ydCBhZG9wdGlvbiBieSB0aGUgV0cu
DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5DaGVl
cnMsPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFz
cz0iIj5Hb256YWxvPGJyIGNsYXNzPSIiPg0KPGRpdj48YnIgY2xhc3M9IiI+DQo8YmxvY2txdW90
ZSB0eXBlPSJjaXRlIiBjbGFzcz0iIj4NCjxkaXYgY2xhc3M9IiI+T24gSnVsIDMwLCAyMDIwLCBh
dCAxMDoxOCBBTSwgSm9uYXRoYW4gTGVubm94ICZsdDs8YSBocmVmPSJtYWlsdG86am9uYXRoYW4u
bGVubm94QDh4OC5jb20iIGNsYXNzPSIiPmpvbmF0aGFuLmxlbm5veEA4eDguY29tPC9hPiZndDsg
d3JvdGU6PC9kaXY+DQo8YnIgY2xhc3M9IkFwcGxlLWludGVyY2hhbmdlLW5ld2xpbmUiPg0KPGRp
diBjbGFzcz0iIj4NCjxkaXYgc3R5bGU9IndvcmQtd3JhcDogYnJlYWstd29yZDsgLXdlYmtpdC1u
YnNwLW1vZGU6IHNwYWNlOyBsaW5lLWJyZWFrOiBhZnRlci13aGl0ZS1zcGFjZTsiIGNsYXNzPSIi
Pg0KKE5vdGUgdGhpcyBtYWlsIGlzIENj4oCZZCB0byA8YSBocmVmPSJtYWlsdG86cXVpY0BpZXRm
Lm9yZyIgY2xhc3M9IiI+cXVpY0BpZXRmLm9yZzwvYT47IHBsZWFzZSBrZWVwIGRpc2N1c3Npb24g
b24NCjxhIGhyZWY9Im1haWx0bzphdnRAaWV0Zi5vcmciIGNsYXNzPSIiPmF2dEBpZXRmLm9yZzwv
YT4uKQ0KPGRpdiBjbGFzcz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+
VGhpcyBpcyBhIGNhbGwgZm9yIGFkb3B0aW9uIGluIHRoZSBBVlRDb3JlIHdvcmtpbmcgZ3JvdXAg
b2YgdGhlIGRvY3VtZW50IOKAnE11bHRpcGxleGluZyBTY2hlbWUgVXBkYXRlcyBmb3IgUVVJQ+KA
nSwmbmJzcDs8YSBocmVmPSJodHRwczovL3Rvb2xzLmlldGYub3JnL2h0bWwvZHJhZnQtYWJvYmEt
YXZ0Y29yZS1yZmM3OTgzYmlzLTAwIiBjbGFzcz0iIj5odHRwczovL3Rvb2xzLmlldGYub3JnL2h0
bWwvZHJhZnQtYWJvYmEtYXZ0Y29yZS1yZmM3OTgzYmlzLTAwPC9hPiZuYnNwOywNCiBhcyB0aGUg
YmFzaXMgZm9yIGEgd29ya2luZyBncm91cCBpdGVtLCBhbG9uZyB3aXRoIGFuIGFwcHJvcHJpYXRl
IG1pbGVzdG9uZS48L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8
ZGl2IGNsYXNzPSIiPkFzIGEgc3VtbWFyeSBmb3IgdGhvc2UgdW5mYW1pbGlhciB3aXRoIHRoZSBk
b2N1bWVudCwgaXQgdXBkYXRlcyBSRkMgNzk4MyB0byBkb2N1bWVudCBob3cgUVVJQyBjYW4gYmUg
ZGVtdWx0aXBsZXhlZCBmcm9tIFNUVU4sIERUTFMsIFJUUCwgYW5kIG90aGVyIHByb3RvY29scyBj
b21tb24gaW4gV2ViUlRDIGFuZCBXZWJSVEMtbGlrZSBzeXN0ZW1zLjwvZGl2Pg0KPGRpdiBjbGFz
cz0iIj48YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjxkaXYgY2xhc3M9IiI+SWYgeW91IGhhdmUgb3Bp
bmlvbnMgb24gd2hldGhlciB0aGlzIGRvY3VtZW50IHNob3VsZCBiZSBhZG9wdGVkLCBwbGVhc2Ug
cmVzcG9uZCB0byB0aGUgQVZUQ29yZSBtYWlsaW5nIGxpc3QgYnkgRnJpZGF5LCBBdWd1c3QgMTR0
aC48L2Rpdj4NCjxkaXYgY2xhc3M9IiI+PGJyIGNsYXNzPSIiPg0KPC9kaXY+DQo8ZGl2IGNsYXNz
PSIiPlRlY2huaWNhbCBjb21tZW50cyBvbiB0aGUgZG9jdW1lbnQgaXRzZWxmIGFyZSBhbHNvIGFs
d2F5cyB3ZWxjb21lLCBvZiBjb3Vyc2UhPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxiciBjbGFzcz0i
Ij4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5UaGFua3MsPC9kaXY+DQo8ZGl2IGNsYXNzPSIiPjxi
ciBjbGFzcz0iIj4NCjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj5Kb25hdGhhbiBMZW5ub3g8L2Rpdj4N
CjxkaXYgY2xhc3M9IiI+QVZUQ29yZSBjby1jaGFpcjwvZGl2Pg0KPGRpdiBjbGFzcz0iIj48YnIg
Y2xhc3M9IiI+DQo8L2Rpdj4NCjwvZGl2Pg0KX19fX19fX19fX19fX19fX19fX19fX19fX19fX19f
X19fX19fX19fX19fX19fX188YnIgY2xhc3M9IiI+DQpBdWRpby9WaWRlbyBUcmFuc3BvcnQgQ29y
ZSBNYWludGVuYW5jZTxiciBjbGFzcz0iIj4NCjxhIGhyZWY9Im1haWx0bzphdnRAaWV0Zi5vcmci
IGNsYXNzPSIiPmF2dEBpZXRmLm9yZzwvYT48YnIgY2xhc3M9IiI+DQpodHRwczovL3d3dy5pZXRm
Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2F2dDxiciBjbGFzcz0iIj4NCjwvZGl2Pg0KPC9ibG9ja3F1
b3RlPg0KPC9kaXY+DQo8YnIgY2xhc3M9IiI+DQo8L2Rpdj4NCjwvYm9keT4NCjwvaHRtbD4NCg==

--_000_4D78061CF37D4C4F90EBD0D15D195A44ciscocom_--


From nobody Thu Jul 30 16:36:02 2020
Return-Path: <juberti@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 71DFB3A126C for <quic@ietfa.amsl.com>; Thu, 30 Jul 2020 16:35:40 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level: 
X-Spam-Status: No, score=-17.599 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, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, 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 de3nXNSSy5NA for <quic@ietfa.amsl.com>; Thu, 30 Jul 2020 16:35:37 -0700 (PDT)
Received: from mail-il1-x130.google.com (mail-il1-x130.google.com [IPv6:2607:f8b0: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 B7B7B3A126A for <quic@ietf.org>; Thu, 30 Jul 2020 16:35:37 -0700 (PDT)
Received: by mail-il1-x130.google.com with SMTP id c16so12143039ils.8 for <quic@ietf.org>; Thu, 30 Jul 2020 16:35:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=fBnTVxo2nI4+drBjOoG25aMqW8a52ataZDBpG70L/6w=; b=KOFtdgXWvYL19tkLzEFADNLVZfXuKXYzOtGAsNnLIJ23iCN+3e0UJZiWZhtNQXxMWD QPguLjQo9THvLewDrf+aVbq0N/DME8ZmfYVp326iONMn81J0gD4Bivf+JqnCEnbTUmfw xPtyVaqC8jjBTA7CHSAA+/t2gfq/r2pYA3B9RMHwesXtE2yxs7Fbskxc2xuW500ZfU3O 88qZ0bo9utWQ6ZXrVQtjcZ+nbpYG1onD2xP9qoESBLdtjiGjYZEjrxBBAicifE1AmVet lT+P+iJtB1XVVQQVmjiGe2/FgoG4pp7LBkwNDcKJLqybSWwv9yM91mf21/2MIwFSC80A wo0A==
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=fBnTVxo2nI4+drBjOoG25aMqW8a52ataZDBpG70L/6w=; b=NVjW5uQ7CCYUiE93gffe8ixZivEuVqY9tFDYnIgF6BHUVJmNDRlNaWGqtEWxgxzBx2 bl/R95nPhP8PUfTpEq8pk9xGCfw8SnbrX9SngIQDuH8kgX7iFQmrxTf1KcGIe+PGLWlX zPOcvewjYApDJs36lzAjP+8j9iZMjdrG2Ez5OgTkvJxhILP0cnjp5HRVy+pd5sgwaMbr UIc8DoE7frutjoVxQHlx9jOa4063xqHcIRgQc7ghMy0B1ZPeigxC70US+I6PccWcToGV KnPsYsZXzNE0vErm7KXSMdLeqJBD1fvO+72vAg2VKzP62Le3iyXFXoheRJB9zT07m4B+ bwJw==
X-Gm-Message-State: AOAM533yYJWhtqI05I8rwU0g01r5pzE5/R8WnFKR2ebpWzJy14JGnZI4 9Jl+1w8cQhErggVWnSjCY1f8D0L7clZSSh9f5HG4xxUBhHc=
X-Google-Smtp-Source: ABdhPJyRgMBS5xo2/KtOkt/GcNZ0q0Aqy7Jzo6j4fc7gzCoyg4q1ZEb7jCuG5z/ZQZJLapJruj0kH1j9iGlYS/hBexE=
X-Received: by 2002:a92:c530:: with SMTP id m16mr1046949ili.300.1596152136802;  Thu, 30 Jul 2020 16:35:36 -0700 (PDT)
MIME-Version: 1.0
References: <C9AA3682-17B8-43EC-BC22-58F37904AD23@8x8.com> <4D78061C-F37D-4C4F-90EB-D0D15D195A44@cisco.com>
In-Reply-To: <4D78061C-F37D-4C4F-90EB-D0D15D195A44@cisco.com>
From: Justin Uberti <juberti@google.com>
Date: Thu, 30 Jul 2020 16:35:25 -0700
Message-ID: <CAOJ7v-2JqDoxcEC0D_YXzgybeS2jkYpVOh0Ehp-WboXvZus9tQ@mail.gmail.com>
Subject: Re: [AVTCORE] Call for Adoption: Multiplexing Scheme Updates for QUIC
To: "Gonzalo Salgueiro (gsalguei)" <gsalguei=40cisco.com@dmarc.ietf.org>
Cc: Jonathan Lennox <jonathan.lennox@8x8.com>, "quic@ietf.org" <quic@ietf.org>, "avt@ietf.org" <avt@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000001f9cfa05abb12131"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/7-ceKYsqm1ck7_BsDkfRv_4oCaI>
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, 30 Jul 2020 23:35:41 -0000

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

I support adoption by the WG.

On Thu, Jul 30, 2020 at 10:58 AM Gonzalo Salgueiro (gsalguei) <gsalguei=3D
40cisco.com@dmarc.ietf.org> wrote:

> I support adoption by the WG.
>
> Cheers,
>
> Gonzalo
>
> On Jul 30, 2020, at 10:18 AM, Jonathan Lennox <jonathan.lennox@8x8.com>
> wrote:
>
> (Note this mail is Cc=E2=80=99d to quic@ietf.org; please keep discussion =
on
> avt@ietf.org.)
>
> This is a call for adoption in the AVTCore working group of the document
> =E2=80=9CMultiplexing Scheme Updates for QUIC=E2=80=9D,
> https://tools.ietf.org/html/draft-aboba-avtcore-rfc7983bis-00 , as the
> basis for a working group item, along with an appropriate milestone.
>
> As a summary for those unfamiliar with the document, it updates RFC 7983
> to document how QUIC can be demultiplexed from STUN, DTLS, RTP, and other
> protocols common in WebRTC and WebRTC-like systems.
>
> If you have opinions on whether this document should be adopted, please
> respond to the AVTCore mailing list by Friday, August 14th.
>
> Technical comments on the document itself are also always welcome, of
> course!
>
> Thanks,
>
> Jonathan Lennox
> AVTCore co-chair
>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>
>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>

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

<div dir=3D"ltr">I support=C2=A0adoption by the WG.</div><br><div class=3D"=
gmail_quote"><div dir=3D"ltr" class=3D"gmail_attr">On Thu, Jul 30, 2020 at =
10:58 AM Gonzalo Salgueiro (gsalguei) &lt;gsalguei=3D<a href=3D"mailto:40ci=
sco.com@dmarc.ietf.org">40cisco.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">



<div style=3D"overflow-wrap: break-word;">
I support adoption by the WG.
<div><br>
</div>
<div>Cheers,</div>
<div><br>
</div>
<div>Gonzalo<br>
<div><br>
<blockquote type=3D"cite">
<div>On Jul 30, 2020, at 10:18 AM, Jonathan Lennox &lt;<a href=3D"mailto:jo=
nathan.lennox@8x8.com" target=3D"_blank">jonathan.lennox@8x8.com</a>&gt; wr=
ote:</div>
<br>
<div>
<div style=3D"overflow-wrap: break-word;">
(Note this mail is Cc=E2=80=99d to <a href=3D"mailto:quic@ietf.org" target=
=3D"_blank">quic@ietf.org</a>; please keep discussion on
<a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.org</a>.)
<div><br>
</div>
<div>This is a call for adoption in the AVTCore working group of the docume=
nt =E2=80=9CMultiplexing Scheme Updates for QUIC=E2=80=9D,=C2=A0<a href=3D"=
https://tools.ietf.org/html/draft-aboba-avtcore-rfc7983bis-00" target=3D"_b=
lank">https://tools.ietf.org/html/draft-aboba-avtcore-rfc7983bis-00</a>=C2=
=A0,
 as the basis for a working group item, along with an appropriate milestone=
.</div>
<div><br>
</div>
<div>As a summary for those unfamiliar with the document, it updates RFC 79=
83 to document how QUIC can be demultiplexed from STUN, DTLS, RTP, and othe=
r protocols common in WebRTC and WebRTC-like systems.</div>
<div><br>
</div>
<div>If you have opinions on whether this document should be adopted, pleas=
e respond to the AVTCore mailing list by Friday, August 14th.</div>
<div><br>
</div>
<div>Technical comments on the document itself are also always welcome, of =
course!</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Jonathan Lennox</div>
<div>AVTCore co-chair</div>
<div><br>
</div>
</div>
_______________________________________________<br>
Audio/Video Transport Core Maintenance<br>
<a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/avt</a><br>
</div>
</blockquote>
</div>
<br>
</div>
</div>

_______________________________________________<br>
Audio/Video Transport Core Maintenance<br>
<a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/avt</a><br>
</blockquote></div>

--0000000000001f9cfa05abb12131--


From nobody Thu Jul 30 17:13:54 2020
Return-Path: <agouaillard@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 B91783A1288; Thu, 30 Jul 2020 17:13:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.097
X-Spam-Level: 
X-Spam-Status: No, score=-2.097 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, 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 JZiC5_2ImhGJ; Thu, 30 Jul 2020 17:13:48 -0700 (PDT)
Received: from mail-il1-x12d.google.com (mail-il1-x12d.google.com [IPv6:2607:f8b0:4864:20::12d]) (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 9AA8D3A1283; Thu, 30 Jul 2020 17:13:48 -0700 (PDT)
Received: by mail-il1-x12d.google.com with SMTP id i138so18098445ild.9; Thu, 30 Jul 2020 17:13:48 -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=WGVyti3gJoNU0nVJ6d7JAGEgLNL1pVf4B+IUKofMai0=; b=kg9H20bgfnBggzT92tNc1Z4iWlFd8ZCYpsm0qoXiwonc9HbXBUb1T1wHI7nq1dnptv ESj9LtdEuDPUFC5GgJTc/bv/BvVVDp70+8OUfibBsYTOOqBX0HqyL1z8ZOWcZ/iiG3Po KYYFCN2bl5tc7MIO1V5PmmT3/XaVpv5SPn4XDMWVjROPW9yQZgGfRTE3jhpeCYLBSd/g X0Jt9RDn6HQGQdkvDmLCud77XnzLKKx8qwymm9rsGS59R2DhFmhqFbUiyKNVmdNT8YUr sQrHIpA3+b5uuXFomj2DE229x5ao6w8+deCHacUlFFX1XhnlKRkkgTAds6xpOUPZpwFv phag==
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=WGVyti3gJoNU0nVJ6d7JAGEgLNL1pVf4B+IUKofMai0=; b=V0jqG9B516yOCRMQFBo36PiItJj9TWAw1zoSkrI6Q72l7zXJEUBOUJa6JLoy4dspRe rlWG402kRE2+6D5oGh84nvhNMcvhGDHVVgXuSdaQrhVq0hElCZiSD7kxQmtYtKFos76S Sk6ib2BtCAV5QsFM0L3kIZOWDbPXeZZGUw65UJMjyqVPGjqESBXBfydvXN14DBOEmuMk gFpCbjjoG7TBq5rpDFRhGjuRD+i5uvI+tZCCkRrC7OgGWREqeJ/Bo08QyfIvhd3fmSMM FIn0H0VyTkdnTW+k34RmcbRW7nYKFbNpPI8kcg0gJklfEwaws/R+4L1VcaJIWHS8r3Kt 2Hzg==
X-Gm-Message-State: AOAM530pTyvg2vBC3GjnM3xiwfQj/L0osEea3ubArYrs+XNGHYbXOlRh AFNKWwulbHXGfP7khH3zZrKaVgEbpK4he4eG4oJGDjUM8is=
X-Google-Smtp-Source: ABdhPJypUPmpUGiEX40/A6GHLTWD2D/jsgbUMFjwRMubSN3S/Uh3afeaNmPZOQA4J2vaqz0vXtO82t/oMDUF8fun5is=
X-Received: by 2002:a92:6a07:: with SMTP id f7mr1112281ilc.271.1596154427838;  Thu, 30 Jul 2020 17:13:47 -0700 (PDT)
MIME-Version: 1.0
References: <C9AA3682-17B8-43EC-BC22-58F37904AD23@8x8.com> <4D78061C-F37D-4C4F-90EB-D0D15D195A44@cisco.com> <CAOJ7v-2JqDoxcEC0D_YXzgybeS2jkYpVOh0Ehp-WboXvZus9tQ@mail.gmail.com>
In-Reply-To: <CAOJ7v-2JqDoxcEC0D_YXzgybeS2jkYpVOh0Ehp-WboXvZus9tQ@mail.gmail.com>
From: Alexandre GOUAILLARD <agouaillard@gmail.com>
Date: Fri, 31 Jul 2020 08:13:36 +0800
Message-ID: <CAHgZEq5wAP0EKS7-Ovnq5A87HS9oyB6aw9pnX0TRuJWPJcqr0w@mail.gmail.com>
Subject: Re: [AVTCORE] Call for Adoption: Multiplexing Scheme Updates for QUIC
To: Justin Uberti <juberti=40google.com@dmarc.ietf.org>
Cc: "Gonzalo Salgueiro (gsalguei)" <gsalguei=40cisco.com@dmarc.ietf.org>, "quic@ietf.org" <quic@ietf.org>,  Jonathan Lennox <jonathan.lennox@8x8.com>, "avt@ietf.org" <avt@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000ad969805abb1a920"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/S9ylCzdwuMNYJ_Ph2imcJVvqLP4>
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, 31 Jul 2020 00:13:51 -0000

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

I support adoption of RFC 7983bis as a WG work item.

On Fri, Jul 31, 2020 at 7:35 AM Justin Uberti <juberti=3D
40google.com@dmarc.ietf.org> wrote:

> I support adoption by the WG.
>
> On Thu, Jul 30, 2020 at 10:58 AM Gonzalo Salgueiro (gsalguei) <gsalguei=
=3D
> 40cisco.com@dmarc.ietf.org> wrote:
>
>> I support adoption by the WG.
>>
>> Cheers,
>>
>> Gonzalo
>>
>> On Jul 30, 2020, at 10:18 AM, Jonathan Lennox <jonathan.lennox@8x8.com>
>> wrote:
>>
>> (Note this mail is Cc=E2=80=99d to quic@ietf.org; please keep discussion=
 on
>> avt@ietf.org.)
>>
>> This is a call for adoption in the AVTCore working group of the document
>> =E2=80=9CMultiplexing Scheme Updates for QUIC=E2=80=9D,
>> https://tools.ietf.org/html/draft-aboba-avtcore-rfc7983bis-00 , as the
>> basis for a working group item, along with an appropriate milestone..
>>
>> As a summary for those unfamiliar with the document, it updates RFC 7983
>> to document how QUIC can be demultiplexed from STUN, DTLS, RTP, and othe=
r
>> protocols common in WebRTC and WebRTC-like systems.
>>
>> If you have opinions on whether this document should be adopted, please
>> respond to the AVTCore mailing list by Friday, August 14th.
>>
>> Technical comments on the document itself are also always welcome, of
>> course!
>>
>> Thanks,
>>
>> Jonathan Lennox
>> AVTCore co-chair
>>
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>>
>>
>> _______________________________________________
>> Audio/Video Transport Core Maintenance
>> avt@ietf.org
>> https://www.ietf.org/mailman/listinfo/avt
>>
> _______________________________________________
> Audio/Video Transport Core Maintenance
> avt@ietf.org
> https://www.ietf.org/mailman/listinfo/avt
>


--=20
Alex. Gouaillard, PhD, PhD, MBA
---------------------------------------------------------------------------=
---------
President - CoSMo Software Consulting, Singapore
---------------------------------------------------------------------------=
---------
sg.linkedin.com/agouaillard

   -

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

<div dir=3D"ltr"><div dir=3D"ltr">I support adoption of RFC 7983bis as a WG=
 work item.=C2=A0<br></div></div><br><div class=3D"gmail_quote"><div dir=3D=
"ltr" class=3D"gmail_attr">On Fri, Jul 31, 2020 at 7:35 AM Justin Uberti &l=
t;juberti=3D<a href=3D"mailto:40google.com@dmarc.ietf.org">40google.com@dma=
rc.ietf.org</a>&gt; wrote:<br></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(204,204,204);padding-left:1ex"><div dir=3D"ltr">I sup=
port=C2=A0adoption by the WG.</div><br><div class=3D"gmail_quote"><div dir=
=3D"ltr" class=3D"gmail_attr">On Thu, Jul 30, 2020 at 10:58 AM Gonzalo Salg=
ueiro (gsalguei) &lt;gsalguei=3D<a href=3D"mailto:40cisco.com@dmarc.ietf.or=
g" target=3D"_blank">40cisco.com@dmarc.ietf.org</a>&gt; wrote:<br></div><bl=
ockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-lef=
t-width:1px;border-left-style:solid;border-left-color:rgb(204,204,204);padd=
ing-left:1ex">



<div>
I support adoption by the WG.
<div><br>
</div>
<div>Cheers,</div>
<div><br>
</div>
<div>Gonzalo<br>
<div><br>
<blockquote type=3D"cite">
<div>On Jul 30, 2020, at 10:18 AM, Jonathan Lennox &lt;<a href=3D"mailto:jo=
nathan.lennox@8x8.com" target=3D"_blank">jonathan.lennox@8x8.com</a>&gt; wr=
ote:</div>
<br>
<div>
<div>
(Note this mail is Cc=E2=80=99d to <a href=3D"mailto:quic@ietf.org" target=
=3D"_blank">quic@ietf.org</a>; please keep discussion on
<a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.org</a>.)
<div><br>
</div>
<div>This is a call for adoption in the AVTCore working group of the docume=
nt =E2=80=9CMultiplexing Scheme Updates for QUIC=E2=80=9D,=C2=A0<a href=3D"=
https://tools.ietf.org/html/draft-aboba-avtcore-rfc7983bis-00" target=3D"_b=
lank">https://tools.ietf.org/html/draft-aboba-avtcore-rfc7983bis-00</a>=C2=
=A0,
 as the basis for a working group item, along with an appropriate milestone=
..</div>
<div><br>
</div>
<div>As a summary for those unfamiliar with the document, it updates RFC 79=
83 to document how QUIC can be demultiplexed from STUN, DTLS, RTP, and othe=
r protocols common in WebRTC and WebRTC-like systems.</div>
<div><br>
</div>
<div>If you have opinions on whether this document should be adopted, pleas=
e respond to the AVTCore mailing list by Friday, August 14th.</div>
<div><br>
</div>
<div>Technical comments on the document itself are also always welcome, of =
course!</div>
<div><br>
</div>
<div>Thanks,</div>
<div><br>
</div>
<div>Jonathan Lennox</div>
<div>AVTCore co-chair</div>
<div><br>
</div>
</div>
_______________________________________________<br>
Audio/Video Transport Core Maintenance<br>
<a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" target=3D"_blank">htt=
ps://www.ietf.org/mailman/listinfo/avt</a><br>
</div>
</blockquote>
</div>
<br>
</div>
</div>

_______________________________________________<br>
Audio/Video Transport Core Maintenance<br>
<a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/avt</a><br>
</blockquote></div>
_______________________________________________<br>
Audio/Video Transport Core Maintenance<br>
<a href=3D"mailto:avt@ietf.org" target=3D"_blank">avt@ietf.org</a><br>
<a href=3D"https://www.ietf.org/mailman/listinfo/avt" rel=3D"noreferrer" ta=
rget=3D"_blank">https://www.ietf.org/mailman/listinfo/avt</a><br>
</blockquote></div><br clear=3D"all"><div><br></div>-- <br><div dir=3D"ltr"=
 class=3D"gmail_signature"><div dir=3D"ltr"><div><div dir=3D"ltr"><div dir=
=3D"ltr"><div dir=3D"ltr">Alex. Gouaillard, PhD, PhD, MBA<div>-------------=
-----------------------------------------------------------------------</di=
v><div>President - CoSMo Software Consulting, Singapore</div><div>---------=
---------------------------------------------------------------------------=
</div><div><a href=3D"http://sg.linkedin.com/agouaillard" target=3D"_blank"=
>sg.linkedin.com/agouaillard</a></div><div><ul style=3D"margin:0px;padding:=
0px 0px 8px;border:0px;outline:0px;font-size:12px;font-family:Helvetica,Ari=
al,sans-serif;vertical-align:baseline;list-style:none;line-height:17px;disp=
lay:table-cell;width:504px;color:rgb(51,51,51)"><li style=3D"margin:0px;pad=
ding:8px 12px 2px 0px;border:0px;outline:0px;font-style:inherit;font-size:1=
1px;font-family:inherit;vertical-align:baseline;font-variant-ligatures:inhe=
rit;font-variant-caps:inherit;font-variant-numeric:inherit;font-variant-alt=
ernates:inherit;font-variant-east-asian:inherit;line-height:1.2em"><dl styl=
e=3D"margin:0px;padding:0px;border:0px;outline:0px;font-style:inherit;font-=
family:inherit;vertical-align:baseline;font-variant-ligatures:inherit;font-=
variant-caps:inherit;font-variant-numeric:inherit;font-variant-alternates:i=
nherit;font-variant-east-asian:inherit;line-height:inherit;word-wrap:break-=
word"><br></dl></li></ul></div></div></div></div></div></div></div>

--000000000000ad969805abb1a920--

