Re: Re-chartering for extension work

Mark Nottingham <mnot@mnot.net> Thu, 12 December 2019 07:15 UTC

Return-Path: <mnot@mnot.net>
X-Original-To: quic@ietfa.amsl.com
Delivered-To: quic@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 24971120115 for <quic@ietfa.amsl.com>; Wed, 11 Dec 2019 23:15:34 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.7
X-Spam-Level:
X-Spam-Status: No, score=-2.7 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=mnot.net header.b=FE2GNFQx; dkim=pass (2048-bit key) header.d=messagingengine.com header.b=toeUnMdJ
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id g2P6o2fyw-UJ for <quic@ietfa.amsl.com>; Wed, 11 Dec 2019 23:15:32 -0800 (PST)
Received: from out4-smtp.messagingengine.com (out4-smtp.messagingengine.com [66.111.4.28]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 4F2851200FD for <quic@ietf.org>; Wed, 11 Dec 2019 23:15:32 -0800 (PST)
Received: from compute3.internal (compute3.nyi.internal [10.202.2.43]) by mailout.nyi.internal (Postfix) with ESMTP id A050A2248D; Thu, 12 Dec 2019 02:15:31 -0500 (EST)
Received: from mailfrontend1 ([10.202.2.162]) by compute3.internal (MEProxy); Thu, 12 Dec 2019 02:15:31 -0500
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=mnot.net; h= content-type:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; s=fm1; bh=2 fqhrBijV5KhlHOWaOh9dLjuhQ/TPxqJ39UFUJQqkhs=; b=FE2GNFQxeDBR28pg5 NxxrWOOeoqGwsgXAjis3pwjuOlv9bKb4xHrQ4qGqWwRfAE8ytg02Apqm7Us81hMU pkR00z+167zZymPyNgqXphPtYD9TtdzR+F9tIqv5LOEef/ZTOrJFOMA3FG2XUhXf zkrHlH46I51cQbaPSIzlmIDYAfPaeNYKXsxZUuKXQkNU7pKtQzudfgL8rbWYjh9n hKyqh4hhbuuy7f7YfbTcuow3t2GiKBql+UTyewj3DAuf4u0Y3WVpZuvDgOGWBBEd BI5SJG4nyqZ2jb6SJu533muUZAcUxjJirx1H8pKmC65TOy4pcvOhiX4nRTiVSAiG WfmcA==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-proxy:x-me-proxy:x-me-sender:x-me-sender :x-sasl-enc; s=fm1; bh=2fqhrBijV5KhlHOWaOh9dLjuhQ/TPxqJ39UFUJQqk hs=; b=toeUnMdJqwJw+j+6MqKe3pSexh6VQnkQdyrDUvOxufnczdvrHCikiPLTw Bsg9e1Dq5FAvnpFNV2LFkC1cReydI7NBDRjYyi9na3phRorxnwDaBurrhNmtdhKA qua77hKAiEoCT1XUe1JR6oCDKiIEO5YWoscfKa6W+XccIDPaULI7/X1oY4w5j1dY EPh8zgaJLqszcxZRtajKr9izszOTfno9clGgDl9b8NE7aWhhZ6IOJSAiEuaJnB/q bMtbqbu6HgR0CpnGKplVWPupPfN0hZLdgHyOh6QVbUzlMEd+HD79ALnmAe6uCeTL K0K4fofdDWS3rODn4nQo/17VPrlKg==
X-ME-Sender: <xms:EunxXbJRmeUFGQe09S_H1s8cqUwGSe7JlQ27n9-fz2PAGsHWhcao3Q>
X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedufedrudeliedguddtfecutefuodetggdotefrod ftvfcurfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfgh necuuegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmd enucfjughrpegtggfuhfgjfffgkfhfvffosehtqhhmtdhhtddvnecuhfhrohhmpeforghr khcupfhothhtihhnghhhrghmuceomhhnohhtsehmnhhothdrnhgvtheqnecuffhomhgrih hnpehivghtfhdrohhrghdpmhhnohhtrdhnvghtnecukfhppeduudelrddujedrudehkedr vdehudenucfrrghrrghmpehmrghilhhfrhhomhepmhhnohhtsehmnhhothdrnhgvthenuc evlhhushhtvghrufhiiigvpedt
X-ME-Proxy: <xmx:EunxXRh_5_VT4BViBgGPYbmo5VIYhIVCEQnwBlGwV0XEbCzc-3gUMQ> <xmx:EunxXeQHRX3xlzg6reKTmghxN2OCrvJ2lZxnY6xlPbpVWv3DTjVwEw> <xmx:EunxXe6WFeFAxEo2DzF39vJWD8-ROb7d_1gN2yj9Bxt9XvqmbEYudg> <xmx:E-nxXdAlEHL4WHGJm5jLsISwrCXLf0egG1XVQLjZ-dIgkWJ7Hjrdfg>
Received: from attitudadjuster.mnot.net (unknown [119.17.158.251]) by mail.messagingengine.com (Postfix) with ESMTPA id 59D8480060; Thu, 12 Dec 2019 02:15:29 -0500 (EST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 13.0 \(3601.0.10\))
Subject: Re: Re-chartering for extension work
From: Mark Nottingham <mnot@mnot.net>
In-Reply-To: <6E58094ECC8D8344914996DAD28F1CCD27D34FD8@dggemm526-mbx.china.huawei.com>
Date: Thu, 12 Dec 2019 18:15:26 +1100
Cc: IETF QUIC WG <quic@ietf.org>, Lars Eggert <lars@eggert.org>
Content-Transfer-Encoding: quoted-printable
Message-Id: <18FA3A15-D580-43FD-A64C-E12E79D91419@mnot.net>
References: <A56547B6-2E3B-4ABE-8C9B-BA9ACC489FB2@mnot.net> <6E58094ECC8D8344914996DAD28F1CCD27D34F98@dggemm526-mbx.china.huawei.com> <A51C42AD-6D1C-432D-99B4-8BB0FB824348@mnot.net> <6E58094ECC8D8344914996DAD28F1CCD27D34FD8@dggemm526-mbx.china.huawei.com>
To: "Roni Even (A)" <roni.even@huawei.com>
X-Mailer: Apple Mail (2.3601.0.10)
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/24LmGI2nQaYfeUgsELXHizZQF5E>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@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, 12 Dec 2019 07:15:34 -0000


> On 12 Dec 2019, at 6:13 pm, Roni Even (A) <roni.even@huawei.com> wrote:
> 
> HI Mark,
> I looked at your response to Jana, I do not have a better text suggestion but I think that adding specific extensions can be discussed by asking the WG to create a new milestone. Yet I understand that the charter should be clear about what is in scope for the WG. I think that maybe the charter should also say that the WG can direct proposal for new work to another WG (sort of dispatch for QUIC).

That's been discussed (at the Transport Area meeting in Singapore); we might try an experiment where we do something like that in Vancouver, but it's not clear that *this* WG should be the locus of quic-dispatchy things quite yet.

Cheers,


> One other thing, I think that when asking for adoption of a document you are asking to create a milestone and adopt the document as the initial document to address the milestone. 
> Sorry for sounding like someone whose focus is on the process and not the content.
> 
> Roni
> 
>> -----Original Message-----
>> From: Mark Nottingham [mailto:mnot@mnot.net]
>> Sent: Thursday, December 12, 2019 9:00 AM
>> To: Roni Even (A)
>> Cc: IETF QUIC WG; Lars Eggert
>> Subject: Re: Re-chartering for extension work
>> 
>> Hi Roni,
>> 
>> See my response to Jana regarding naming of extensions.
>> 
>> Regarding milestones - yes, we'll do that when the rest of the changes go
>> through. Thanks for the reminder.
>> 
>> Cheers,
>> 
>> 
>>> On 12 Dec 2019, at 5:49 pm, Roni Even (A) <roni.even@huawei.com>
>> wrote:
>>> 
>>> Hi Mark,
>>> I am not sure why you need to name extensions in the charter. I think that
>> the extension work in the charter should be general and the discussion about
>> specific ones would be about creating a new milestone.
>>> 
>>> BTW: maybe it will be good to update the milestones
>>> 
>>> Roni Even
>>> 
>>>> -----Original Message-----
>>>> From: QUIC [mailto:quic-bounces@ietf.org] On Behalf Of Mark
>>>> Nottingham
>>>> Sent: Wednesday, December 11, 2019 11:38 PM
>>>> To: IETF QUIC WG
>>>> Cc: Lars Eggert
>>>> Subject: Re-chartering for extension work
>>>> 
>>>> We've just put out Calls for Adoption for extensions to QUICv1, as we
>>>> believe that the group has some capacity to discuss them as it
>>>> finishes work on the core protocol.
>>>> 
>>>> However, our charter [1] precludes work on at least some extensions.
>>>> The specific text in question is:
>>>> 
>>>> """
>>>> Extensions that will support partial reliability, and negotiation and
>>>> use of Forward Error Correction schemes, are out of scope in this
>>>> version of the working group charter.
>>>> """
>>>> 
>>>> *If* we do decide we'd like to adopt, we'll need to update it to
>>>> something
>>>> like:
>>>> 
>>>> """
>>>> Additionally, the Working Group will deliver [ adopted extensions ].
>>>> The Working Group may consider other extension work, but adopting
>>>> further extensions requires updating this charter.
>>>> """
>>>> 
>>>> Please take a look and discuss any concerns; we'll be asking our ADs
>>>> for such a modification (with appropriate changes to the list of
>>>> extensions adopted) once our Calls for Adoption complete.
>>>> 
>>>> Cheers,
>>>> 
>>>> 1. https://datatracker.ietf.org/wg/quic/about/
>>>> 
>>>> --
>>>> Mark Nottingham   https://www.mnot.net/
>>> 
>> 
>> --
>> Mark Nottingham   https://www.mnot.net/
> 

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