Re: Re-chartering for extension work

Olivier Bonaventure <olivier.bonaventure@tessares.net> Fri, 20 December 2019 08:40 UTC

Return-Path: <olivier.bonaventure@tessares.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 74572120129 for <quic@ietfa.amsl.com>; Fri, 20 Dec 2019 00:40:41 -0800 (PST)
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, RCVD_IN_DNSWL_NONE=-0.0001, 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=tessares-net.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 vORWj9IuAMLC for <quic@ietfa.amsl.com>; Fri, 20 Dec 2019 00:40:38 -0800 (PST)
Received: from mail-wr1-x430.google.com (mail-wr1-x430.google.com [IPv6:2a00:1450:4864:20::430]) (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 AE71A120091 for <quic@ietf.org>; Fri, 20 Dec 2019 00:40:37 -0800 (PST)
Received: by mail-wr1-x430.google.com with SMTP id t2so8591217wrr.1 for <quic@ietf.org>; Fri, 20 Dec 2019 00:40:37 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=tessares-net.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=HA7sqI9qFRHpQrkEPX9AHT/s8DMVzHiLOepYZNZO8dw=; b=vXNgjHSa5FDMkjT0h27DYC0d1Xgaw4CVb7yX5SkLNzFXv1NCz9lxI8GugXpifKl9Nd tkCg8EB+ehGKnDXlFqX8ETzvB7+Qso6uhLzhqEIo5ExkMtnVEbJNkJkHqtdK45BjM4bd rkor25xuELe5tmiXQLndPu206o663aVp0jQyI0sUEVE9/hzgGAgfz6w//T57aaTEqkcg zS0OJ0FMsfzXEZsuSHEVlURhwuA84RMoYVF5DbXhGApy1mQ6SgNAMXs7VrXLG5Eb3A2i kyrtyp26s4Kua9K1KY3zAO34K4usFUATsAEGbMsoDhXdjDlx4BPez+YoGbNGkjh9ZO7I geIw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=HA7sqI9qFRHpQrkEPX9AHT/s8DMVzHiLOepYZNZO8dw=; b=ltvZhN1zNDrUpy6N3EIwkT+KhqhdigMsPHY0ifaTNKKVFfKQVFy66uNjqlUAtRWjPD mQFVsk83MxXOeyT+OTnTRx4Zwts/2zYhhGRBUPlRHtEc5w+HoyR4rL/J4GGsHzoPvtPJ RxWjsZ2HEfAURdmydGInu/J6tKNGaSfUulnApAf1m9Z3CYaepdu2Kv3KnnDzXUswcTOe mLT1RQp4Kbab25skGKLCnGKcfOhyKJtw/+utwIRglAlU+xK5DhTqHjMbo2Gac9M07g3S DpkPOnGg6CJimaj22W8CmDFILVbk01s7pNQtxcoDyTmmCndRTqE0tW5F6HHN6y1NBihh rsew==
X-Gm-Message-State: APjAAAVI7ta/GCyaWCtiBMnwk5LVMderlLmZ1V6K4o4dNWTWjO0HHrtv OUvNUYeV32PYlI/wkhAY1ORR1aFFz4u0NqtdzZ+xz9EErpY/JsprX2nHv2ye5JPZ3JEaQCFz
X-Google-Smtp-Source: APXvYqwdwtDHbZ1DYVBB0WJ52El7u+CHlwgkrhz3B/abS+j1RypwyM+e3N5jS1Ne2GMijixqQnArpw==
X-Received: by 2002:adf:f604:: with SMTP id t4mr411031wrp.33.1576831235999; Fri, 20 Dec 2019 00:40:35 -0800 (PST)
Received: from ?IPv6:2001:6a8:308f:2:4:3cec:cd70:33ea? ([2001:6a8:308f:2:4:3cec:cd70:33ea]) by smtp.gmail.com with ESMTPSA id x1sm8836355wru.50.2019.12.20.00.40.34 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 20 Dec 2019 00:40:34 -0800 (PST)
From: Olivier Bonaventure <olivier.bonaventure@tessares.net>
Message-Id: <2265E0F8-1B85-4500-9A59-425395F4604E@tessares.net>
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
Subject: Re: Re-chartering for extension work
Date: Fri, 20 Dec 2019 09:40:33 +0100
In-Reply-To: <1575ae9dcdcade6a8ec68289fd6b735eae04ed32.camel@ericsson.com>
Cc: "roni.even@huawei.com" <roni.even@huawei.com>, "mnot@mnot.net" <mnot@mnot.net>, "lars@eggert.org" <lars@eggert.org>, "quic@ietf.org" <quic@ietf.org>
To: Magnus Westerlund <magnus.westerlund=40ericsson.com@dmarc.ietf.org>
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>
X-Mailer: Apple Mail (2.3445.104.11)
Content-Type: multipart/alternative; boundary="Apple-Mail=_8048723E-4407-4E98-B45D-253F7E443623"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/VXMAhiRhZsAhaRCs-Bi0_ALZ0P8>
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, 20 Dec 2019 08:40:41 -0000

Magnus,

> 
> I want to give my input as AD into this process. We are intentionally keeping
> this rechartering very narrow in scope and do not intended to open up for
> general extension adoption in the WG at this moment. The extensions currently on
> call for adoption is selected set which appears important, tractable and with
> clear scope. However, the primary focus will remain on finishing the core
> specification of version 1 of QUIC. The chairs have my full confidence in
> managing the process and are communicating with us ADs regularly. 

I agree, the working group should focus its energy on the charter items and minor additions.

> 
> As Mark stated before discussion of future extensions can occurr if time
> permits, we will also consider other ways of enabling the discussion like a QUIC
> dispatch session. However, as v1 finish we will take a new look at the QUIC WG
> charter and do a more thourgh recharter at that stage. That discussion will then
> happen in the context of the discussion that will have occurred between now and
> then. However, starting v2, how to handle both bigger and smaller extensions to
> the protocol and any additional guidance documents needed will clearly need
> changes to the charter. 
> 

The QUIC design brings a lot of flexibility that could enable the definition of a wide range of very useful extensions in many different scenarios. Several drafts have been proposed in this direction, but it is possible to be more generic as described in the Pluginized QUIC paper that was presented at SIGCOMM’20 (see https://www.pquic.org <https://www.pquic.org/>)

I think that it could be useful for the evolution of QUIC to encourage the exploration of new extensions and organise a process where there extensions that would be scheduled for v2 or beyond could be discussed. This could be an informal mailing list, side meetings well announced in advance with a call for contributions, … There is energy in the community to also work on extending and we should try to encourage that without interfering with the QUIC WG charter.

Best regards,


Olivier


-- 


Disclaimer: https://www.tessares.net/mail-disclaimer/ 
<https://www.tessares.net/mail-disclaimer/>