[tsvwg] Scope of the L4S Experiment (was: Guard DSCP)

"C. M. Heard" <heard@pobox.com> Tue, 04 May 2021 04:39 UTC

Return-Path: <heard@pobox.com>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4B6933A241C for <tsvwg@ietfa.amsl.com>; Mon, 3 May 2021 21:39:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.099
X-Spam-Level:
X-Spam-Status: No, score=-2.099 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_MSPIKE_H2=-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 (1024-bit key) header.d=pobox.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 p0AvEUjvkCoU for <tsvwg@ietfa.amsl.com>; Mon, 3 May 2021 21:39:54 -0700 (PDT)
Received: from pb-smtp2.pobox.com (pb-smtp2.pobox.com [64.147.108.71]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E45023A241B for <tsvwg@ietf.org>; Mon, 3 May 2021 21:39:53 -0700 (PDT)
Received: from pb-smtp2.pobox.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 89EA7C42D1 for <tsvwg@ietf.org>; Tue, 4 May 2021 00:39:51 -0400 (EDT) (envelope-from heard@pobox.com)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=pobox.com; h= mime-version:references:in-reply-to:from:date:message-id:subject :to:cc:content-type; s=sasl; bh=lX12RcJo82EngE5jQ+Miqb1iFAYPt9zX Ak/2+gSF5WM=; b=on9M1XJj47188QhZAaVFYGVGbv79sl4/TNAXadylz15PQiQE 5eH2fBlo5u2BXWW5Pt1mjPVRKa66aR1+n9/PNdRXyOafQuoB3j7Z3gQo/chRoExS vFOhSFUrVGwws6Qk/TBttgmC7l7Gtl/L7Dm+JVNPLSaKifuL5UgE975+Ax8=
Received: from pb-smtp2.nyi.icgroup.com (unknown [127.0.0.1]) by pb-smtp2.pobox.com (Postfix) with ESMTP id 812B9C42D0 for <tsvwg@ietf.org>; Tue, 4 May 2021 00:39:51 -0400 (EDT) (envelope-from heard@pobox.com)
Received: from mail-il1-f177.google.com (unknown [209.85.166.177]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pb-smtp2.pobox.com (Postfix) with ESMTPSA id 12CE9C42CF for <tsvwg@ietf.org>; Tue, 4 May 2021 00:39:51 -0400 (EDT) (envelope-from heard@pobox.com)
Received: by mail-il1-f177.google.com with SMTP id y10so5389067ilv.0 for <tsvwg@ietf.org>; Mon, 03 May 2021 21:39:51 -0700 (PDT)
X-Gm-Message-State: AOAM530JV85z1fu+fS7N26TX7IxSzOMN2uqWorL3A+6b3Db2XxyH2RoH /ACgzYF0k5qyNd3nrQYstEChCbdBy19+3CgmYQE=
X-Google-Smtp-Source: ABdhPJyzoTVEEJrK87Qhy5gpgs2aQLudrQCtoke5SyaygwGG0FQv41cP9nEqA+V4dnnO9YZZgI9dGEmov66n5XeonzM=
X-Received: by 2002:a92:7510:: with SMTP id q16mr18448033ilc.291.1620103190543; Mon, 03 May 2021 21:39:50 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR19MB4045D7179410986A46C3E30783469@MN2PR19MB4045.namprd19.prod.outlook.com> <458e847061d1dd6a45bfa5bec046d201e88c8075.camel@heistp.net> <CACL_3VE3rfmAZewOCWTzfC5A9v7c2HgZ8NAxdt_5qKg5Rn0QNQ@mail.gmail.com> <a9e0781559a0ca4fcf02c225b67d3037bc56ea8f.camel@heistp.net> <02DBC945-B1D5-4A70-8906-E48831951C5C@gmx.de> <CACL_3VF8Nt-fH9RwncFVVvwicuON7A_R6JU8Y_OXqBwTOpdmKw@mail.gmail.com> <64AC29EE-2576-41C4-8411-7C66518A3853@gmail.com> <CACL_3VG3M-jFOHkCPCinnDP3G=gYU_0nnDz5Qwi9BJ501PrZFg@mail.gmail.com> <MN2PR19MB404525C9FD6052D0A195F44683429@MN2PR19MB4045.namprd19.prod.outlook.com> <CACL_3VGDd80FeqrH+8_2+Chbh-cT9-bpW-gfH7itSgXN3=_cbA@mail.gmail.com> <MN2PR19MB4045FE83AE49A3317476A6BD83419@MN2PR19MB4045.namprd19.prod.outlook.com>
In-Reply-To: <MN2PR19MB4045FE83AE49A3317476A6BD83419@MN2PR19MB4045.namprd19.prod.outlook.com>
From: "C. M. Heard" <heard@pobox.com>
Date: Mon, 03 May 2021 21:39:39 -0700
X-Gmail-Original-Message-ID: <CACL_3VEmgtk3XvNmshwmTf10pP99iGP9bTk5XpQ+iKDuCRhn-w@mail.gmail.com>
Message-ID: <CACL_3VEmgtk3XvNmshwmTf10pP99iGP9bTk5XpQ+iKDuCRhn-w@mail.gmail.com>
To: "Black, David" <David.Black@dell.com>
Cc: TSVWG <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000002c019205c179ab28"
X-Pobox-Relay-ID: C38D13E2-AC92-11EB-B898-74DE23BA3BAF-06080547!pb-smtp2.pobox.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/pdX-AjpNnxOEznIuP2oxPYoGgqA>
Subject: [tsvwg] Scope of the L4S Experiment (was: Guard DSCP)
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 04 May 2021 04:39:58 -0000

On Tue, Apr 27, 2021 at 3:57 PM Black, David wrote:

> the appropriate L4S experiment scope may be sets of
> cooperating/participating networks rather than the (originally envisioned)
> Internet as a whole.
>

I had certainly understood the intended scope to be sets of
cooperating/participating networks rather than the Internet as a whole. How
could it possibly be otherwise, with a change in the semantics of CE that
is incompatible with existing standards, without at the same time
obsoleting those standards?

When Differentiated Services was introduced by RFC 2474, the existing TOS
standard was obsoleted, based on good evidence that it was unused (there
was only one implementation of TOS routing, IIRC, and negligible
deployment). It didn't get introduced as an experiment.

When the original experimental incarnation of ECN was specified by RFC
2481, it could be introduced as an internet-wide experiment because prior
standardized uses of the field had been obsoleted on good evidence of
non-use, and there was good evidence that harm would not be caused to
deployed systems.

The evidence presented here strongly suggests to me that L4S is not benign
to existing standards. If it is to be used experimentally, it must be
contained. If it is to be used internet-wide, then existing incompatible
uses should be obsoleted.

One or the other, please. Don't deploy L4S internet-wide and call it
experimental.

Mike Heard

>