IETF Logo Mail Archive

Re: [EToSat] Re-chartering for extension work

Kuhn Nicolas <Nicolas.Kuhn@cnes.fr> Tue, 17 December 2019 17:28 UTC

Return-Path: <Nicolas.Kuhn@cnes.fr>
X-Original-To: etosat@ietfa.amsl.com
Delivered-To: etosat@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 68D5312088D; Tue, 17 Dec 2019 09:28:58 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, 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 Rm65OD-K4VDU; Tue, 17 Dec 2019 09:28:56 -0800 (PST)
Received: from mx1.cnes.fr (mx1.cnes.fr [194.199.174.200]) (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 1C1EF120845; Tue, 17 Dec 2019 09:28:53 -0800 (PST)
X-IronPort-AV: E=Sophos;i="5.69,326,1571702400"; d="scan'208";a="12986528"
X-IPAS-Result: A2FaAADkDvld/wIBeAplGQEBAQEBAQEBAQEBAQEBAQEBEQEBAQEBAQEBAQEBgX6BdCxZE1QhEioKlTKbLwkBAQEBAQEBAQEvBQECAQGEQAKCGSQ4EwIQAQEBBAEBAQEBBQIBAQICaYRrTAyGNAIBAQJ5EAIBBQMNARQkMiUCBAENBQiDG4J3D69cGoQgAQMCAoYQBoE2gWWMTYERR4JMPoI+JgEBAQKBYoNAgiwElwuXegeBQHeCQoRtjnx3gUyHdoQuA4tfjk2BRocKlA4jgVgzGidMgjgBM1ARjk0BCIccO4U/RDABEIEPCI9IAYEPAQE
X-URL-LookUp-ScanningError: 1
From: Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>
To: 'Mark Nottingham' <mnot@mnot.net>, 'Lars Eggert' <lars@eggert.org>
CC: "'etosat@ietf.org'" <etosat@ietf.org>, 'IETF QUIC WG' <quic@ietf.org>, "'Gorry (erg)'" <gorry@erg.abdn.ac.uk>, "emile.stephan@orange.com" <emile.stephan@orange.com>
Thread-Topic: Re-chartering for extension work
Thread-Index: AQHVsGtooBlSsn3ccUyRkmXHeRMv76e+nGiw
Date: Tue, 17 Dec 2019 17:27:49 +0000
Deferred-Delivery: Tue, 17 Dec 2019 17:28:08 +0000
Message-ID: <F3B0A07CFD358240926B78A680E166FF1ED2D685@TW-MBX-P03.cnesnet.ad.cnes.fr>
References: <A56547B6-2E3B-4ABE-8C9B-BA9ACC489FB2@mnot.net>
In-Reply-To: <A56547B6-2E3B-4ABE-8C9B-BA9ACC489FB2@mnot.net>
Accept-Language: fr-FR, en-US
Content-Language: fr-FR
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-tm-as-product-ver: SMEX-11.0.0.4255-8.100.1062-25110.000
x-tm-as-result: No--19.192900-0.000000-31
x-tm-as-user-approved-sender: Yes
x-tm-as-user-blocked-sender: No
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/etosat/_w2QIebrFZWot4lBzJAxXwTcm4c>
Subject: Re: [EToSat] Re-chartering for extension work
X-BeenThere: etosat@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "The EToSat list is a non-WG mailing list used to discuss performance implications of running encrypted transports such as QUIC over satellite." <etosat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/etosat>, <mailto:etosat-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/etosat/>
List-Post: <mailto:etosat@ietf.org>
List-Help: <mailto:etosat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/etosat>, <mailto:etosat-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 17 Dec 2019 17:28:58 -0000

Hi Mark, Lars,

Many meetings discussed the impacts of QUIC encryption on satellite Performance-enhancing proxy (PEP) and the benefit of exchanging additional transport parameters.
draft-kuhn-quic-0rtt-bdp was mentioned as a possible extension during « Quick QUIC Update » presentation.

We have updated draft-kuhn-quic-0rtt-bdp-05 as an extension of QUIC.
We propose to include it in the re-chartering discussion.

Regards,
Nicolas, Emile and Gorry

https://datatracker.ietf.org/meeting/106/materials/slides-106-tsvarea-quick-quic-update-mark-nottingham-00.pdf 
https://tools.ietf.org/html/draft-kuhn-quic-0rtt-bdp-05 

-----Message d'origine-----
De : QUIC <quic-bounces@ietf.org> De la part de Mark Nottingham
Envoyé : mercredi 11 décembre 2019 22:38
À : IETF QUIC WG <quic@ietf.org>
Cc : Lars Eggert <lars@eggert.org>
Objet : 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/

v2.23.0 | Report a Bug | By Email