IETF Logo Mail Archive

Re: Re-chartering for extension work

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

Return-Path: <ianswett@google.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 1B058120C71 for <quic@ietfa.amsl.com>; Tue, 17 Dec 2019 09:37:24 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.499
X-Spam-Level:
X-Spam-Status: No, score=-17.499 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 wdks2Rlr2L_a for <quic@ietfa.amsl.com>; Tue, 17 Dec 2019 09:37:22 -0800 (PST)
Received: from mail-wm1-x32b.google.com (mail-wm1-x32b.google.com [IPv6:2a00:1450:4864:20::32b]) (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 061E2120C63 for <quic@ietf.org>; Tue, 17 Dec 2019 09:37:22 -0800 (PST)
Received: by mail-wm1-x32b.google.com with SMTP id p17so4155974wmb.0 for <quic@ietf.org>; Tue, 17 Dec 2019 09:37:21 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=pYC3RtHuve//TKBYtRRBCV5W082RarepNh3ZAdiCfEw=; b=o2j/HJGVNDBMwXTLsy+M7CVHKtCeGGJQ+8NL/Y5les7hfCtlAE5gLu3Jv0DbIfzqZG KKwoGE5oFG02DACxTn8rmf/wYbO8jkGdNG9CB2WXa/6sKAlTMAsx0r8ci7c8KiH/2Y6z 7e7/qTxklTnNb37O8OzWW7UIjrTn8oXaaMHByujXLiu4ntuLXwgsSBas8ALyjNgdoSJM kV6iUq6tSHVRibOMRBWRptcBy9hGklwYvNausUFXj2NTuALjQnfoetfrjxS9Y0iq5AYK SOUnuk65NVcsKqSXZtOJcQVi+y+0j5R2dyskUywZPVS4HyXsR3ugcH5+z6ikx9NuJk/k 4Vdw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=pYC3RtHuve//TKBYtRRBCV5W082RarepNh3ZAdiCfEw=; b=YmtdNR3EhdzWqFax/NZRHufEluyRoGZigx94wuT+sHzlp1wq3eSuian/vxYaLH0Gor e5eevmYTQCsx+dklRNnNlkIB/rerUj5QRavFT1EoDBz5+aZN/pqZPfZDxCGHYBd/731j QbHE+jVWkcve8j3SoLvI3aZerrCipXUARv26DbsKt0lqhYAqwx/0vedYz4hlrtVIGE4H Vtw59xzrzPAutb7umor8wi0xM2yLh3FvI5OFKaqtBGTC4A4sgzMbfANOWfoXiErOqYnI 7G6GbAa1iD2ZAt73B7sCK8ay6nn3b/YcXS6obMCbi+jd0S05wP8vM6lYuaqUYv6YjJyz 87Gw==
X-Gm-Message-State: APjAAAVLVBF95h61bYwPti6oSE1F0Vx6P+LYuSmJiLcVu6jbYNZvkJ5r N+fvDHci7yCF5zqCkp1jvuZHWeti5viD14dVLB6i4g==
X-Google-Smtp-Source: APXvYqwslvGck3EfpEcCZedFHV9UpP0Ti2sopmyrN4RuIyOg4/fN8iKbULF1bsPl1qsrNytHhY+ptGI0hZyrQmYdeuc=
X-Received: by 2002:a1c:dc85:: with SMTP id t127mr6793864wmg.16.1576604240026; Tue, 17 Dec 2019 09:37:20 -0800 (PST)
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>
Subject: Re: Re-chartering for extension work
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/quic/_rm-FOHmCP2j32880ePE1pUrTxg>
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: Tue, 17 Dec 2019 17:37:24 -0000

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

v2.23.0 | Report a Bug | By Email