Re: [EToSat] Re-chartering for extension work

Ian Swett <ianswett@google.com> Tue, 17 December 2019 17:37 UTC

MIME-Version: 1.0
References: <A56547B6-2E3B-4ABE-8C9B-BA9ACC489FB2@mnot.net> <F3B0A07CFD358240926B78A680E166FF1ED2D685@TW-MBX-P03.cnesnet.ad.cnes.fr>
In-Reply-To: <F3B0A07CFD358240926B78A680E166FF1ED2D685@TW-MBX-P03.cnesnet.ad.cnes.fr>
From: Ian Swett <ianswett@google.com>
Date: Tue, 17 Dec 2019 12:37:07 -0500
Message-ID: <CAKcm_gPek4kV5zwigiCC8+1FimPM1Ss5-KHvDrQjZA-u04nDPA@mail.gmail.com>
To: Kuhn Nicolas <Nicolas.Kuhn@cnes.fr>
Cc: Mark Nottingham <mnot@mnot.net>, Lars Eggert <lars@eggert.org>, "Gorry (erg)" <gorry@erg.abdn.ac.uk>, "etosat@ietf.org" <etosat@ietf.org>, IETF QUIC WG <quic@ietf.org>, "emile.stephan@orange.com" <emile.stephan@orange.com>
Content-Type: multipart/alternative; boundary="000000000000ae17200599e9c7d9"
Archived-At: <https://mailarchive.ietf.org/arch/msg/etosat/KSEah24yXt8AwT4NVPiEktyAMOA>
Subject: Re: [EToSat] Re-chartering for extension work
Precedence: list

I think the satellite use case is an important one, but I have a number of
concerns with the approach in that draft, so I don't believe it's ready for
adoption.

On Tue, Dec 17, 2019 at 12:29 PM Kuhn Nicolas <Nicolas.Kuhn@cnes.fr> wrote:

> 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/
>
>

Re: [EToSat] Re-chartering for extension work Kuhn Nicolas
Re: [EToSat] Re-chartering for extension work Ian Swett
Re: [EToSat] Re-chartering for extension work Christian Huitema
Re: [EToSat] BDP parameters draft (was: Re-charte… Christian Huitema
Re: [EToSat] Re-chartering for extension work Lars Eggert
Re: [EToSat] Re-chartering for extension work Kuhn Nicolas
Re: [EToSat] Re-chartering for extension work Kuhn Nicolas
Re: [EToSat] BDP parameters draft (was: Re-charte… Kuhn Nicolas
Re: [EToSat] BDP parameters draft (was: Re-charte… Kuhn Nicolas