Re: Rechartering QUIC for Post Version 1 Work

Lucas Pardue <lucaspardue.24.7@gmail.com> Tue, 26 January 2021 17:27 UTC

Return-Path: <lucaspardue.24.7@gmail.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 DFA243A0C00 for <quic@ietfa.amsl.com>; Tue, 26 Jan 2021 09:27:28 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.053
X-Spam-Level:
X-Spam-Status: No, score=0.053 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 4MZdUPq_S-pL for <quic@ietfa.amsl.com>; Tue, 26 Jan 2021 09:27:27 -0800 (PST)
Received: from mail-ej1-x633.google.com (mail-ej1-x633.google.com [IPv6:2a00:1450:4864:20::633]) (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 5A8E03A0BE9 for <quic@ietf.org>; Tue, 26 Jan 2021 09:27:24 -0800 (PST)
Received: by mail-ej1-x633.google.com with SMTP id hs11so24128688ejc.1 for <quic@ietf.org>; Tue, 26 Jan 2021 09:27:24 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=wjZVCnTqqYfK0dTGOg2pI+btgchZASTlx9pVfBRXJAw=; b=GVv7PmLXqu+r7XnCovgU7/VfW8GCGyigG1akxY89DOJAwX6RxcHEhHp1zHLMLotZbi 8iOTj2y5d1YaC0v4EDiBQdFrfkjLxzflBT5tcEIlD8CgOzYNIUB7C7Vw2KY/1AMcGCV8 uMfh26R1HcJLxHLPssubYeA8JJCTmNp5n/jSPrJO+C2PCVFXzZeKJrkAbu82RI5mztqN pWzVCb6e38z/voXlSjGPTUh2tz6tVjEUKUU80LHhjTGimr86wMHCJfeAJlFl/Wn2xTJK 7hq4JL5zdP2jUKCIBoe9sqB7j/bpdvNbnaBBlA4m/D2urr2iaQpmpgohEXsBhy/0N/jT 2Bbg==
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; bh=wjZVCnTqqYfK0dTGOg2pI+btgchZASTlx9pVfBRXJAw=; b=KyL+WLRh3lLXpDBort57fmkgvV5uyYJxS+qnjjs4WWM0KkfV50TgzQ57kDQtXfE56X eC3FQsMAngCSGdQbBf4LcZyKTa923wBDLwykLPwki+TloeIN1tYcN+ds3q8ItW0UwTtZ earSvBS++q+W6NUWdZ+R64hGeGKRbnaHUM7N/oWaD7DNtVQ8nmNC9TqSKyzkF9E4kLbW 6UG36Q2B4+zNlKaGUXjyE9mW7k4tMBhZHgpYCvCL0EY4KTOjMID8U9iLbN4Gm/Ws3V3b azHIkuQV96vxuOfgy7W5ecbttN1Dd108zVBWFAru9bXn/JEctzvYJoZygMVDkqJLFDLy Pk+Q==
X-Gm-Message-State: AOAM530NpLMbTxFo/BR6qLMlTl7OPrETHvKznHoetpX4wFKpFrdKwtJt M4QXdG0P1J5SglWKd8sY00y2tjSlg6hZAxXkf+V6F5O13yI=
X-Google-Smtp-Source: ABdhPJzOXhFvZaaPU28wWZ+LeOgFfChopU1UsxKlTKdr6ofuAO20jh8BvNjJPCnK79/n7oJ+Qc/C/S3+r40qD1EpqkE=
X-Received: by 2002:a17:906:ff43:: with SMTP id zo3mr4085873ejb.542.1611682042684; Tue, 26 Jan 2021 09:27:22 -0800 (PST)
MIME-Version: 1.0
References: <CALGR9oaXpZp87ujmkDAO6Tuy=m-s8qKDY9-azpm_PhVAMfkq9A@mail.gmail.com> <20210126170048.GB364092@okhta> <D01160E4-C89E-4DF5-B0A7-C5138E33D9C1@eggert.org> <20210126170932.GC364092@okhta>
In-Reply-To: <20210126170932.GC364092@okhta>
From: Lucas Pardue <lucaspardue.24.7@gmail.com>
Date: Tue, 26 Jan 2021 17:27:11 +0000
Message-ID: <CALGR9oaO8Q7TC9zyajM20gZkZPR1cRDSv-SeDqo0MfaQbgfAjg@mail.gmail.com>
Subject: Re: Rechartering QUIC for Post Version 1 Work
To: QUIC WG <quic@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000a5299405b9d0f772"
Archived-At: <https://mailarchive.ietf.org/arch/msg/quic/d9YyTfg0dqInsM8Smkc_VWT_zo8>
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, 26 Jan 2021 17:27:29 -0000

Hi Dmitri,

On Tue, Jan 26, 2021 at 5:10 PM Dmitri Tikhonov <dtikhonov@litespeedtech.com>
wrote:

> I would dispense with examples and use precedent.  That is, the second
> work area is listed simply as "QUIC deployability" in the charter.  Then,
> the WG picks up (say) the load balancer draft based on the applicability
> of the "deployability" rule.  This establishes precedent what types of
> work items the deployability work area covers.  The precedent is used in
> the future to figure out which new work items are applicable and which
> are not.
>

my 2c as an individual:

The Applicability, Manageability and Load Balancer documents are all
already adopted by the QUIC WG, under current or previous charters. They
address the work area of deployability. Arguably, they help *use* the QUIC
protocol rather than extend or modify it. A loss bits specification
possibly requires extension of the QUIC protocol, with the intent to
improve manageability. Such work is likely to span the extension and
deployability work areas.

Waiting for the new documents to get proposed and adopted, as a new
precedent for future work in this area doesn't IMO help much. We already
have precedents, which I trust the WG to be capable of applying without
being too literal.

Cheers,
Lucas