Re: Rechartering QUIC for Post Version 1 Work

David Schinazi <> Wed, 27 January 2021 01:21 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id 1B30B3A0EF4 for <>; Tue, 26 Jan 2021 17:21:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -2.097
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: (amavisd-new); dkim=pass (2048-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id CfakZOvYErGC for <>; Tue, 26 Jan 2021 17:21:17 -0800 (PST)
Received: from ( [IPv6:2607:f8b0:4864:20::102e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 7EE6C3A0EF0 for <>; Tue, 26 Jan 2021 17:21:17 -0800 (PST)
Received: by with SMTP id s24so284068pjp.5 for <>; Tue, 26 Jan 2021 17:21:17 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=zOGqepTtWTODyNl4B4Sj8N8rYJaZl/2Mdmzos8aSawY=; b=XFFp4ZC5fw+pT87Wxry+QeWGDCOI47tx2OSg/guD2e+aMBDiY+e1H3+d53xHhal93C EYXfZzx9cL2sClNkPjWz/NIO7WfiMS1rrdhCXQZRJu9cZAETrJOwyL1QSkZh5ylY/8yk IJ5M+txmLI/dcfKx552Q9bp9nueJ3JPBYgKUSYToMx3utXRp6PcIDNI6BoxAn++auwxA tdf0O0tsDQJuOXOfQMX94qhCrmrUqbSa0czIVtm52O6vtkrq1E5XxXPBZaSBwhq2xK+s 6py+HilT0hz1BYvLs+2qJpSBUpRTANzA6F/D/iEANSutPq4UsFd6eunAFMNn2lgHN3EU UyXw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=zOGqepTtWTODyNl4B4Sj8N8rYJaZl/2Mdmzos8aSawY=; b=nD4wLeIAnaOZlPjcUfQ/e6DU7PubuInZz2vrItiiwkmflvA7lB2a2ROH3r5UC9rzar c2W7RLdTI5Z/6q/DAUjQQ1n8W9qDbvTyeoK4v4l5JuiTtKGDcQAbQyqU1r1erYM/XMih GigqQFMK/NceuFBUvYrocMcR8P6qQrZ86anTW1Ps7sxreouTW62RCTkcDVKeRZElX7XP fvCkoVM5dsZxx8WgPJleQZKNX632VnnnvKc8Rp7a+85CrMmieD4os1USAJxnub3OwYH5 tpdLuFJZmlrdPkir0HgovVS4P9z2S6y0NQ9xsiyKU6/CYfWOlp3KqCiSK4K3zD6HcadO Clhg==
X-Gm-Message-State: AOAM533Rn9Xh7VWDjUxgXTYhilLOelYlrR72WDajVcdlUUw3kfha8OrR I1bv2jxBf6Co4aNrvdsIKq52aM1xENga/GgsQIc=
X-Google-Smtp-Source: ABdhPJwBMAFFiwI6UnPLZcMKneC2vPy6v5tmqunTkv7bxj3F0QWIzKEktO9ymYKIYUtDo9o/gCb6OlDDGeG2RRNpGZQ=
X-Received: by 2002:a17:902:8216:b029:dc:1e79:e74c with SMTP id x22-20020a1709028216b02900dc1e79e74cmr8456233pln.5.1611710476877; Tue, 26 Jan 2021 17:21:16 -0800 (PST)
MIME-Version: 1.0
References: <> <20210126170048.GB364092@okhta> <> <20210126170932.GC364092@okhta> <> <20210126184815.GD364092@okhta> <> <> <>
In-Reply-To: <>
From: David Schinazi <>
Date: Tue, 26 Jan 2021 17:21:05 -0800
Message-ID: <>
Subject: Re: Rechartering QUIC for Post Version 1 Work
To: Lucas Pardue <>
Content-Type: multipart/alternative; boundary="00000000000074845c05b9d79695"
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: Wed, 27 Jan 2021 01:21:20 -0000

Thanks for your reply, Lucas. Responses inline.

On Tue, Jan 26, 2021 at 4:56 PM Lucas Pardue <>

> Hi David,
> Thanks for the feedback. I've responded in-line, and some of that text
> responds to points Ian raised too.
> On Tue, Jan 26, 2021 at 9:54 PM David Schinazi <>
> wrote:
>> I'm supportive of the overall direction of this rechartering, with some
>> concerns though:
>> 1) multipath is not mentioned in this charter - based on the
>> conversations we've had over the past months, I think we should be explicit
>> about whether multipath is in or out of scope
> The intention was that the new charter would allow the group, as the focal
> point for QUIC-related things, to consider work such as multipath QUIC. The
> guidance for discussion of multipath is still the same as Lars' sent to the
> WG in November [1]. To borrow a bit of that, we still feel it premature to
> adopt an proposal as a work item.

I see your point, I'm OK with not precluding multipath as long as the
guidance from November still holds. But then again, a recharter could be
seen as invalidating prior charter-related decisions so being explicit
could be useful here.

There's an interesting contrast between this point and your second point.
> It seems there's a balance between being specific and appearing not open to
> new ideas.

>From my perspective, multipath was important enough of a topic to warrant
its own interim a few months back which isn't true of any of our extensions
- so I guess that's where I'd draw the line in terms of mentioning
something or not?

> 2) +1 to Ian and Dmitri's comments about mentioning current examples in a
>> way that seems to preclude other extensions, we could remove the examples
>> to help clarify
> (previously I commented as an individual, but now with a chair hat on) If
> 3 people have the same comment, it's likely a sign that some polishing up
> of the text would help. Specific suggestions always appreciated.

I liked Dmitri's proposal to remove the examples. If we want to include
examples that are in scope, I'd suggest also including examples of what's
not in scope to make it clear that neither list is exhaustive.

> 3) I was surprised by "Extensions intended for Standards Track need to
>> have general applicability to multiple application protocols." and I don't
>> think our charter should preclude these. We shouldn't ban standard-track
>> protocols that require a QUIC extension to function properly. Perhaps
>> another way we could phrase this would be to say that "The QUIC WG is only
>> chartered to work on extensions that have general applicability to multiple
>> application protocols. Extensions that are specific to an application
>> protocol should be defined in the WG responsible for that protocol, in
>> consultation with the QUIC WG." -- without stating anything about Standards
>> track.
> I'd like Lars or Magnus to respond to this point too. IIUC the intention
> of the text is to say that QUIC transport extensions that wish to be
> adopted by this group under Standards Track, should apply broadly. An
> extension designed for only one specific use, and which the authors do not
> wish to spend time considering design changes that would permit
> more-general usage, isn't a great use of the WGs time trying to
> standardise. However, the QUIC WG is a good venue to catalog such work as
> Informational or Experimental. I don't believe we want to prevent QUIC
> extensions that are specific to a use from being developed as Standards
> Track elsewhere in the IETF.

I love bikeshedding document tracks as much as the next person, but I don't
think that needs to be litigated in the charter - the charter should help
us decide what we allocate WG time for - if an extension is not seen as
valuable by the WG, I don't think it's worth it to spend WG time to publish
it as experimental or informational. Either we care about the extension or
we don't, right?

> 4) It seems off to me to simultaneously declare HTTP/3 logging in-scope
>> and HTTP/3 out-of-scope. I think qlog is useful, but if we want to use it
>> outside of the QUIC transport protocol then maybe it should live in another
>> WG.
> That's one (fair) interpretation. The intent here is to make it clear that
> the QUIC WG no longer owns the HTTP/3 application mapping, as always
> intended. qlog doesn't change protocols so working on that falls into the
> deployment working area. I expect a large part of the QUIC WG population,
> to start with, will be made up of deployers of HTTP/3. So while there has
> been some discussion on the most suitable home for qlog and splitting the
> drafts up [2], keeping them developed in a single WG would seem like the
> best way to channel effort and attention of active deployers. If others
> have a strong sense that is not the case they should speak up.

Members of the QUIC implementers community have been attending other
QUIC-adjacent working groups, so I don't think placing them in QUIC will
impact implementation energy. I'd even argue that placing these in QUIC
might constrain them to QUIC instead of also encouraging other protocols.
If someone were to write a draft about how to use qlog with SCTP, would it
belong in the QUIC WG?

5) "Maintenance and evolution of the QUIC base specifications" isn't very
>> clear to me - does that mean that working on future versions of QUIC is in
>> or out of scope?
> The full paragraph states:
> " Maintenance and evolution of the QUIC base specifications that describe
> its invariants, core transport mechanisms, security and privacy, loss
> detection and recovery, congestion control, version and extension
> negotiation, etc. This includes the specification of new versions of QUIC,
> if necessary."
> I think that's clear but if you have some suggestions to improve it we'll
> take a look.

Nope, that is very clear - I must have missed it which is my fault.

But now I'm realizing that the "if necessary" in that last sentence might
be interpreted differently by various folks when we start wondering what
features should go into QUIC v2. I'd suggest just removing the "if


> Lucas
> [1] -
> [2] -