Re: Rechartering QUIC for Post Version 1 Work

Christian Huitema <> Fri, 29 January 2021 17:50 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id F2CC23A11CD for <>; Fri, 29 Jan 2021 09:50:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.89
X-Spam-Status: No, score=-1.89 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, T_SPF_PERMERROR=0.01] autolearn=ham autolearn_force=no
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id 2k5NolQ6MltH for <>; Fri, 29 Jan 2021 09:50:19 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 6B06D3A11CC for <>; Fri, 29 Jan 2021 09:50:19 -0800 (PST)
Received: from ([] by with esmtp (Exim 4.92) (envelope-from <>) id 1l5XuP-000LKq-4C for; Fri, 29 Jan 2021 18:50:15 +0100
Received: from (unknown []) by (Postfix) with ESMTPS id 4DS4cJ0c8tzL8P for <>; Fri, 29 Jan 2021 09:50:08 -0800 (PST)
Received: from [] ( by with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.92) (envelope-from <>) id 1l5XuJ-0008MY-Ud for; Fri, 29 Jan 2021 09:50:07 -0800
Received: (qmail 27273 invoked from network); 29 Jan 2021 17:50:06 -0000
Received: from unknown (HELO []) ([]) (envelope-sender <>) by (qmail-ldap-1.03) with ESMTPA for <>; 29 Jan 2021 17:50:05 -0000
Subject: Re: Rechartering QUIC for Post Version 1 Work
To: Lars Eggert <>, Spencer Dawkins at IETF <>
Cc: Roberto Peon <>, IETF QUIC WG <>
References: <> <20210126170048.GB364092@okhta> <> <20210126170932.GC364092@okhta> <> <20210126184815.GD364092@okhta> <> <> <> <> <> <> <>
From: Christian Huitema <>
Message-ID: <>
Date: Fri, 29 Jan 2021 09:50:04 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:78.0) Gecko/20100101 Thunderbird/78.6.1
MIME-Version: 1.0
In-Reply-To: <>
Content-Type: text/plain; charset="windows-1252"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-US
Authentication-Results:; auth=pass smtp.auth=
X-Spampanel-Outgoing-Class: unsure
X-Spampanel-Outgoing-Evidence: Combined (0.15)
X-Recommended-Action: accept
X-Filter-ID: Pt3MvcO5N4iKaDQ5O6lkdGlMVN6RH8bjRMzItlySaT9WLQux0N3HQm8ltz8rnu+BPUtbdvnXkggZ 3YnVId/Y5jcf0yeVQAvfjHznO7+bT5x6h2yQpzTslcOqazQkKtAFKj/EwzSHE5FGYwwjsNRPCBev 1UoFBfmVxF7Ux9fTBNzmD6wdmZPcItWbGe10hXJtXL4FsauCVkDjmcYJdU3yWp7KuHNaaKdg7iBE ZefdsNUFWKwa/wzJUjmazeC7Imca9EJlxFy1R8PRglwPYpBBuRQ6V51u76v35b1wNe/MvdIN+Yj9 JT+HIE3AciYbXmyy2+J9PgaoF8SQHto3le4zsHTaeQtlKubP6iUTjj6yPARK6buALVaA782LKxg6 vRmng8N1aLhXqdc+jC1RcnVud53D5caUhbVtvqItBqoizkFDWJmcqHKssKxaylFamaV+b9tZ+C5y Oc2YAGkaEP1NO+wd68fWg8M/DqNJnyxK7mcdCu2mlibEyS19RfuR8H5R17NirEYyqwqMBGrw8ELi qOyD7UxtOMuKFjzK5zsiVohMBqzR52YHar/IFGqdBj1a6IupC5RqLj/k6/wmh+zu68PH12Bh87aa 4YfZs104p87OifVovUq7COge14oi3y0trSOIPpeqwlm2NDGXIJ2x7EtekSh8Zhx/YtERKbWN8E65 bJwwfOCWa1Hfd26B3Yz3u2vx3xkVscjuhlyZByM3r8IeGq4RRh5M7nLD0EqYqp34OeaqZehAskg9 zMpCZ4Qt99CwkyNW5oJ+r5LYXcMk4hEVniihuDwEGDcmr6e3OPQHxzUOEv9x2JozDVWpGqOvfz8h 2tj4aloLqSd3UIr8MXjI60oLXcuhwUdHWP/Eha4NXjcKR5LZIKCLB6H6mfAkwD/3EaCPu1onFa0d n3u5ipIcWpgD1+MrllsO2WsRFClic0YV1E3cK088GNIeQjFlPE48k6wYOikXD7qYhWAa7+c6+0Xs DVtCAGQDUwTZWAv0dxCqGRQPPGR7vmqZQrQOZJ0Q4x+0GOxZvoENDONKwTepoEV8JoWhfuVs2p92 abOQTjYr4mblZJIFx02/rieoYQ012X/617XXv8LOWWL/2TEvuGslKTrRIXcXpFg5ivY=
Archived-At: <>
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Fri, 29 Jan 2021 17:50:21 -0000

On 1/29/2021 12:24 AM, Lars Eggert wrote:
> Hi,
> On 2021-1-29, at 2:03, Spencer Dawkins at IETF <> wrote:
>> I THINK I'm reading this as the QUIC working group requesting groups that realize that their applications require QUIC extensions to consult with the QUIC working group, and seek review. Is that the intention?
> yes.
>> I'd expect that to be stronger, simply because (based on experiences with protocols like SIP) popular protocols tend to collect applications from people who don't understand the underlying protocol as well as the people who are responsible for the underlying protocol. If you can say "but you can accomplish the same thing by using QUIC as it is now", sooner rather than later, that would probably make everyone's lives simpler.
> ...
>> So, maybe that could say something like "are encouraged to consult with the QUIC WG and obtain early review of proposals, thereby avoiding late surprises"?
> I'm proposing a text change based on this suggestion in

To Spencer's point, I shall observe that the extension mechanisms of 
QUIC are in fact very powerful. Case in point, I just completed an 
implementation of two multipath drafts in Picoquic, both keyed by the 
negotiation of transport options. I also did study the "unreliable 
deliveries" scenario, and it could certainly be deployed through the 
parameter negotiation mechanism. The role of the IETF there is to 
distinguish between experiments and standards.

Pretty much anyone with a keyboard and a github repo can fork one of the 
open source implementations of QUIC and experiment with a new 
functionality. The only downside is that if negotiation fails the 
application has to live with the limitations of QUIC V1, such as single 
path instead of multipath, or reliable delivery instead of immediate 
delivery. To go from there to wide scale deployment, the supporters need 
to convince enough other parties. Hence the need for some kind of standard.

There is an obvious role for the IETF there. In theory, going through 
the standardization crucible will result in better extensions, avoid 
replicating existing work, review security issues, etc. But I am worried 
about time scales. The work on draft-liu-multipath-quic started in 
October, and we see two implementations 4 months later, and we could see 
coordinated deployments within a few more months. Compare that to the 
median time of getting something done in an IETF WG, more than 3 years. 
There are solid chances that by the time the WG concludes the industry 
has already converged on a solution, redundancy with other standards be 

That's what worries about the charter. How do we match the time scale of 
standardization with the potentially high speed of defining them?

-- Christian Huitema