Re: [tsvwg] Consensus call on ECT(1)

Dan Siemon <dan@coverfire.com> Mon, 18 May 2020 16:46 UTC

Return-Path: <dan@coverfire.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 07BCF3A08CF for <tsvwg@ietfa.amsl.com>; Mon, 18 May 2020 09:46:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.197
X-Spam-Level:
X-Spam-Status: No, score=-0.197 tagged_above=-999 required=5 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, SPF_HELO_NONE=0.001, SPF_NONE=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=coverfire.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 zrLRhMWIQEKn for <tsvwg@ietfa.amsl.com>; Mon, 18 May 2020 09:46:38 -0700 (PDT)
Received: from mail-qt1-x82d.google.com (mail-qt1-x82d.google.com [IPv6:2607:f8b0:4864:20::82d]) (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 F3DC53A089C for <tsvwg@ietf.org>; Mon, 18 May 2020 09:46:37 -0700 (PDT)
Received: by mail-qt1-x82d.google.com with SMTP id i68so8645671qtb.5 for <tsvwg@ietf.org>; Mon, 18 May 2020 09:46:37 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=coverfire.com; s=google; h=message-id:subject:from:to:date:in-reply-to:references:user-agent :mime-version:content-transfer-encoding; bh=BkUZQMBW+N8tXQiq301qyIXhxPI5bNg/uadA7+VUKw4=; b=VKWpiSdkiHt+b1InlmiuwhIrsqXdpAgx5rtb83O5b5AK09uQfVWJGf+xrc64RajPRu MJ0gRp4/NXpcrn1rYXdV95UokF5DqgCNFKVrxHyRQWanQv5HjlUKWSyqFUmjh1F9qQxS AzioxbB2BkcpZZGHkpysd91X2FbS65XOYE8waaHqR3UlcU52iTQA1OU2Xtic6wiXlj80 /chIWqf6uohXkvK6I87snJAsWQEf2BWstJSaRZ2Zxz2e4O7LxF3KYowXmVRkgs0xHtAN PZATjM9r0gVnikHYTblA+2GC+vEAsCXBibMnI+883h5gV1aeweSevLjnXvmcDBtH4Xrt I8wA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=BkUZQMBW+N8tXQiq301qyIXhxPI5bNg/uadA7+VUKw4=; b=jUbDeOpMv3i5uD5lKiuHMP+qg7+GyTzKxjqN99CsWyS2hpWjlh2Zr8meIJndL3dldW 1F9j8vzFJqzrRQRe+ppD6IW7F51A+fhjgqv0ISig86iaWijRkB8KGwHuUbx/LObuHRMN 02VLhwulu/HFaT6Y973GnQZEBAZhwTio9lzstRRi8Ib1e1wcFAVQTbP+VQSjVW8Phrif IyN4bxqXzNNQzSIf/WWquBV+uRBjh5R+cWO2Gy/jZruq09MPdfGJjISp9L7vUqpnArjC 3KwdgmmXJ9Q+4AerwwFeEOEbKUIDRmy7ShUD/rZzRIZDwHqic9Qyr+hirgupMuBscp3j 9GZw==
X-Gm-Message-State: AOAM5317khBdjQT6iWyd3pkpA5+IzvabdaYabl7Fq5yj8C362bfDBSIB eWzJ8KzjCkNW+iavYwzZMvd1EA==
X-Google-Smtp-Source: ABdhPJynFUCw097KsWdJxLLM6W0VwPVl/GaihL5oQ7dVg+RIREL9K11c5nCHi4J70iKQMYHN1qf9FA==
X-Received: by 2002:ac8:794c:: with SMTP id r12mr8574401qtt.46.1589820396780; Mon, 18 May 2020 09:46:36 -0700 (PDT)
Received: from neptune.home ([2607:f2c0:e56e:256:ad5a:b70c:ebcc:2794]) by smtp.gmail.com with ESMTPSA id g20sm8474290qki.75.2020.05.18.09.46.35 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 18 May 2020 09:46:35 -0700 (PDT)
Message-ID: <340746314cecb1f7bf944b22ab10be20bac969b0.camel@coverfire.com>
From: Dan Siemon <dan@coverfire.com>
To: Wesley Eddy <wes@mti-systems.com>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Date: Mon, 18 May 2020 12:46:34 -0400
In-Reply-To: <46720ce0-ffcb-e97f-3e2d-6b5274b73b15@mti-systems.com>
References: <46720ce0-ffcb-e97f-3e2d-6b5274b73b15@mti-systems.com>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.36.2 (3.36.2-1.fc32)
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/1Urp1z-hjnZAl9sWojFyhh_T5Rk>
Subject: Re: [tsvwg] Consensus call on ECT(1)
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: Mon, 18 May 2020 16:46:42 -0000

Long time lurker, first time contributor so I'm not sure if that means
my vote counts or not...

My vote is #3 (more testing) because I don't have a complete enough
understanding of L4S to be firmly against it and I don't fully
understand the tunnel marking implications. Second choice is ECT as
output.

My interest and concern in this comes from the point of view of a
vendor [1] that offers traffic management solutions for the fixed
wireless market [2]. We use FQ-CoDel but at this point have not widely
enabled ECN (the little experimentation we've done looks promising).

My rational is as follows:
* One of the reasons that DSCP hasn't taken off, in addition to the
coordination problem, is that without per-subscriber isolation, it will
be gamed. I do not understand why a new classification scheme would not
suffer the same fate.
* The improvement with a modern AQM is already dramatic.
* It's "weird" that in the "ECT(1) as input" option, of the four ECN
combinations, three are related to congestion control and one is a
special, 'DSCP doesn't work so we stole it for classification' value.
Explaining that outside of this forum may not be fun.
* SCE (ECT(1) as output) is more intuitive to me.
* Most fixed wireless networks are flat IP with little tunnelling and
use simple equipment that I'm skeptical will adopt L4S. These networks
host millions of subscribers in the U.S. alone.

[1] - https://www.preseem.com
[2] - https://www.wispa.org/what_is_a_wisp.php

On Mon, 2020-05-04 at 14:15 -0400, Wesley Eddy wrote:
>  In this email thread, please state, concisely, which of the
> following viewpoints on ECT(1) you prefer. Please have extended
> discussion in a different thread. If you are uncomfortable sharing
> your opinion on the list, you may email the tsvwg chairs directly (
> tsvwg-chairs@ietf.org). 
> 
> If you did not attend the 27 April interim, please watch the meeting
> video [https://www.youtube.com/watch?v=dw3YKyeFxQU] for context on
> this question.
> 
> I support using ECT(1) as an input signal to the network. This is the
> approach consistent with the current L4S drafts. This position does
> not mean that there are no remaining issues with L4S, but that the
> remaining issues can be resolved by continued WG effort on the
> current drafts.
> I support using ECT(1) as an output signal from the network. This is
> consistent with SCE. If you believe L4S will not be safe for the
> internet without significant architectural changes, you are in this
> group.
> There is a specific test or tests I need to see before making a
> decision about ECT(1). Please be specific about the tests in your
> response.
> 
> Please submit your opinion by 5/18/2020.
> 
>