Re: [tsvwg] L4S DSCP (was: L4S drafts: Next Steps)

Kyle Rose <krose@krose.org> Fri, 26 March 2021 12:55 UTC

Return-Path: <krose@krose.org>
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 91E513A1DF7 for <tsvwg@ietfa.amsl.com>; Fri, 26 Mar 2021 05:55:19 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 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, 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=krose.org
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 aNrhBDmZM2-s for <tsvwg@ietfa.amsl.com>; Fri, 26 Mar 2021 05:55:13 -0700 (PDT)
Received: from mail-yb1-xb30.google.com (mail-yb1-xb30.google.com [IPv6:2607:f8b0:4864:20::b30]) (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 59BA43A1E08 for <tsvwg@ietf.org>; Fri, 26 Mar 2021 05:55:12 -0700 (PDT)
Received: by mail-yb1-xb30.google.com with SMTP id 8so5709398ybc.13 for <tsvwg@ietf.org>; Fri, 26 Mar 2021 05:55:12 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=krose.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=kLqfOmVeZi+2dnUGejoZLsVWFRKcfIb6FvsSPYXRzvU=; b=Qb0Uuz6MCJFDa9CGfBfapf9brI851px4UsM/04hOp0sovuoLukqgw6NnP1N1/Vz5JG tm/tCfZQV2tVLNXl/lERJaKZ+p7ArrC/gdaJafqWDixFQ79GJxL+8MpfWOx2hSZc0zhM jpTkmVrbF6LkhkX05mp3V2NLRvG3IDzAoZE/4=
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=kLqfOmVeZi+2dnUGejoZLsVWFRKcfIb6FvsSPYXRzvU=; b=dWZ8lJQwLJFFpQJCYZFvL+Xulri+HH5YH3yBVWDSn1sUIv3JZspoFH00i8nzn/qrpl 0jX7CIPt3gSbsFyhJNGTHsUg79N+ACqbWEhHIZi4zVbYaZZWz211YdT/CqMey0kCkLIg vEgowI7ndQYvZBi4MhxT1MXgo5Tjh50qBs6iyy8a6zvZgXjmqDRx2JBXAQevVH7sXoOM 5vpWHf0DFhTIc2NO+W6Ezil/kL0gcS3oG6wHDI90W5NwdlBrXNFkz2zUCbf+EEoUECTr TqzAHHydA8iNpVsEKksldtzoYCidSXttHYkALmNdAuAC13jCx0j1AX1hmhembWZPqjRW Dxuw==
X-Gm-Message-State: AOAM530911c+VE86v/9WyWjaU48Y7o9wgWr9Kd6tBTv4MKU5Z3ucjJUB gChsI9gF+CfhIg1wLRSG3930pv9Je/VDwiq5jo1tBg==
X-Google-Smtp-Source: ABdhPJxP1GWTz1AhT5Vp+0IbBBBMp/AOcFQAL4LYMieTkt93I08Y9iQl9EVsv+aSPmR0fRx/xzvLRqoYb0pZ0JueeQs=
X-Received: by 2002:a25:ca52:: with SMTP id a79mr20208025ybg.248.1616763310876; Fri, 26 Mar 2021 05:55:10 -0700 (PDT)
MIME-Version: 1.0
References: <MN2PR19MB404527384A1B1DD9CFC2A3D983659@MN2PR19MB4045.namprd19.prod.outlook.com> <6f0ac4bf-bd1a-65cd-1d40-a97d4aa71aab@bobbriscoe.net> <7B4426F9-E1C5-4F88-A264-0D54C809D523@gmail.com> <AM8PR07MB74761AFC8F5BE0F9573DFF32B9629@AM8PR07MB7476.eurprd07.prod.outlook.com> <6481E606-2458-49D7-B580-8DF7B93494FD@gmx.de> <AM8PR07MB747675E421F0B7A6246C67BEB9619@AM8PR07MB7476.eurprd07.prod.outlook.com> <9A9D4AC3-43F0-4778-839B-E1E247A3C5FA@gmx.de> <AM8PR07MB7476026EA3AA7AD49622B296B9619@AM8PR07MB7476.eurprd07.prod.outlook.com>
In-Reply-To: <AM8PR07MB7476026EA3AA7AD49622B296B9619@AM8PR07MB7476.eurprd07.prod.outlook.com>
From: Kyle Rose <krose@krose.org>
Date: Fri, 26 Mar 2021 08:54:58 -0400
Message-ID: <CAJU8_nUgNa-W4wf2Vb8sUUqv4XUsSFdVQFUWwrTGw0gDshahiQ@mail.gmail.com>
To: "De Schepper, Koen (Nokia - BE/Antwerp)" <koen.de_schepper@nokia-bell-labs.com>
Cc: Sebastian Moeller <moeller0@gmx.de>, Bob Briscoe <in@bobbriscoe.net>, tsvwg IETF list <tsvwg@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000d4dc1305be700a02"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/0SraM4jMX78-G3MA4SbrTemsH0s>
Subject: Re: [tsvwg] L4S DSCP (was: L4S drafts: Next Steps)
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: Fri, 26 Mar 2021 12:55:20 -0000

On Fri, Mar 26, 2021, 8:30 AM De Schepper, Koen (Nokia - BE/Antwerp) <
koen.de_schepper@nokia-bell-labs.com> wrote:

> I understood the goal of your proposal. But before diving into the details
> of a DiffServ-based proposals, I'm taking a step back asking: Is using
> DiffServ an option at all.


Why wouldn't it be? The point of the proposal AIUI is to require networks
to take action to explicitly opt-in to this experiment. Given the DiffServ
bleaching that occurs by default at network boundaries, operators that take
no action will not find themselves ambushed by novel behavior.

This approach allows for experimenting with ECT(1) as a classifier in a
safe (contained, time-limited) way, thus allowing a path toward universal
deployment (i.e., removing the DSCP guard) if the experiment is successful
without requiring standardization and rollout of end-to-end DiffServ. And
it does so (a) without permanently burning the ECT(1) code point if the
experiment fails, and (b) in an opt-in manner that greatly reduces the
potential for unintended side effects on classic traffic.

This seems to me like the obvious path toward consensus on an experimental
deployment aimed at gathering real-world experience without first
committing to something unproven.

Kyle