IETF Logo Mail Archive

RE: Re-chartering for extension work

"Roni Even (A)" <roni.even@huawei.com> Thu, 19 December 2019 07:25 UTC

Return-Path: <roni.even@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 2EEFD120026 for <quic@ietfa.amsl.com>; Wed, 18 Dec 2019 23:25:12 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.2
X-Spam-Level:
X-Spam-Status: No, score=-4.2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_MED=-2.3, SPF_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 W9dv940yuQfu for <quic@ietfa.amsl.com>; Wed, 18 Dec 2019 23:25:10 -0800 (PST)
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 D9476120018 for <quic@ietf.org>; Wed, 18 Dec 2019 23:25:09 -0800 (PST)
Received: from LHREML713-CAH.china.huawei.com (unknown [172.18.7.108]) by Forcepoint Email with ESMTP id 083AA8DAD5D863617187; Thu, 19 Dec 2019 07:25:08 +0000 (GMT)
Received: from DGGEMM424-HUB.china.huawei.com (10.1.198.41) by LHREML713-CAH.china.huawei.com (10.201.108.36) with Microsoft SMTP Server (TLS) id 14.3.408.0; Thu, 19 Dec 2019 07:25:07 +0000
Received: from DGGEMM526-MBX.china.huawei.com ([169.254.8.101]) by dggemm424-hub.china.huawei.com ([10.1.198.41]) with mapi id 14.03.0439.000; Thu, 19 Dec 2019 15:25:04 +0800
From: "Roni Even (A)" <roni.even@huawei.com>
To: Lars Eggert <lars@eggert.org>
CC: Magnus Westerlund <magnus.westerlund@ericsson.com>, Mark Nottingham <mnot@mnot.net>, "ilubashe@akamai.com" <ilubashe@akamai.com>, "quic@ietf.org" <quic@ietf.org>
Subject: RE: Re-chartering for extension work
Thread-Topic: Re-chartering for extension work
Thread-Index: AQHVsGthwQYlvsKzDkalKC49qw+Rnqe2D8QAgAAC9YCAAAPbgIAAAG8AgAAHYACAABf9gIAADEGAgABrEACACVYLAIAATutAgAA1K4CAAI61EA==
Date: Thu, 19 Dec 2019 07:25:03 +0000
Message-ID: <6E58094ECC8D8344914996DAD28F1CCD27D36582@dggemm526-mbx.china.huawei.com>
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> <18FA3A15-D580-43FD-A64C-E12E79D91419@mnot.net> <6E58094ECC8D8344914996DAD28F1CCD27D35044@dggemm526-mbx.china.huawei.com> <1575ae9dcdcade6a8ec68289fd6b735eae04ed32.camel@ericsson.com> <6E58094ECC8D8344914996DAD28F1CCD27D3512A@dggemm526-mbx.china.huawei.com> <c98ddfd008714672857833383153efb7@ustx2ex-dag1mb5.msg.corp.akamai.com> <28639c145dae9d10c3bbc8328aa93ea4feb8a7de.camel@ericsson.com> <6E58094ECC8D8344914996DAD28F1CCD27D363CE@dggemm526-mbx.china.huawei.com> <A1301332-955C-43AE-9A18-5132B073CCAF@eggert.org>
In-Reply-To: <A1301332-955C-43AE-9A18-5132B073CCAF@eggert.org>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [10.210.168.6]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-CFilter-Loop: Reflected
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/qMuxCOs8veXbn2XHF4GN8v_p6YU>
X-BeenThere: quic@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Main mailing list of the IETF QUIC working group <quic.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/quic>, <mailto:quic-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/quic/>
List-Post: <mailto:quic@ietf.org>
List-Help: <mailto:quic-request@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, 19 Dec 2019 07:25:12 -0000

Hi Lars,
I am probably having problem with understanding the difference between milestones and charter.

My understanding is the you adopt a draft to serve as the initial document addressing a milestone. The WG decides to create a milestone based on the charter, the charter provides general goals.  I would prefer if the charter will say that the WG will work on extending the QUIC protocol to address the applicability and manageability of the QUIC protocol as a general transport protocol.

Roni


> -----Original Message-----
> From: Lars Eggert [mailto:lars@eggert.org]
> Sent: Thursday, December 19, 2019 8:42 AM
> To: Roni Even (A)
> Cc: Magnus Westerlund; Mark Nottingham; ilubashe@akamai.com;
> quic@ietf.org
> Subject: Re: Re-chartering for extension work
> 
> Hi,
> 
> On 2019-12-18, at 21:33, Roni Even (A) <roni.even@huawei.com> wrote:
> > I am confused, I was not asking for adoption of the work but to have it in
> the charter so it can be discussed on the list and worked upon without being
> contested as non-chartered work. This is at least my understanding about
> the difference between the charter and adoption
> 
> only work items that the WG has consensus in terms of eventually shipping
> them go into the charter. We then usually can adopt individual drafts as
> starting points for those chartered items.
> 
> We're parallelizing things at the moment to some degree, by running the
> adoption calls in parallel to the recharter, since we're on an accelerated
> timeline. I'm sorry if this is confusing.
> 
> Lars

v2.23.0 | Report a Bug | By Email