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

Anna Brunström <anna.brunstrom@kau.se> Mon, 18 May 2020 22:03 UTC

Return-Path: <anna.brunstrom@kau.se>
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 A89693A03FF for <tsvwg@ietfa.amsl.com>; Mon, 18 May 2020 15:03:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.199
X-Spam-Level:
X-Spam-Status: No, score=-0.199 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_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=kau.se
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 Ab6lKXPKJxnr for <tsvwg@ietfa.amsl.com>; Mon, 18 May 2020 15:03:30 -0700 (PDT)
Received: from smtp1.kau.se (smtp1.kau.se [130.243.21.250]) by ietfa.amsl.com (Postfix) with ESMTP id 9B7473A00E0 for <tsvwg@ietf.org>; Mon, 18 May 2020 15:03:29 -0700 (PDT)
Received: from e-mailfilter01.sunet.se (e-mailfilter01.sunet.se [192.36.171.201]) by smtp1.kau.se (Postfix) with ESMTP id 92B5F18501E1 for <tsvwg@ietf.org>; Tue, 19 May 2020 00:03:27 +0200 (CEST)
Received: from Exch-A3.personal.kau (exch-a3.kau.se [130.243.19.84]) by e-mailfilter01.sunet.se (8.14.4/8.14.4/Debian-8+deb8u2) with ESMTP id 04IM3Q0N043426 (version=TLSv1/SSLv3 cipher=ECDHE-RSA-AES256-SHA384 bits=256 verify=FAIL) for <tsvwg@ietf.org>; Tue, 19 May 2020 00:03:26 +0200
Received: from Exch-A1.personal.kau (130.243.19.82) by Exch-A3.personal.kau (130.243.19.84) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384) id 15.1.1847.3; Tue, 19 May 2020 00:03:20 +0200
Received: from Exch-A1.personal.kau ([fe80::7862:a3d3:1cba:9754]) by Exch-A1.personal.kau ([fe80::7862:a3d3:1cba:9754%2]) with mapi id 15.01.1847.009; Tue, 19 May 2020 00:03:20 +0200
From: Anna Brunström <anna.brunstrom@kau.se>
To: "tsvwg@ietf.org" <tsvwg@ietf.org>
Thread-Topic: [tsvwg] Consensus call on ECT(1)
Thread-Index: AdYiR5HJvW/9BAylSICGz300RD4M9wLBorcQ
Date: Mon, 18 May 2020 22:03:20 +0000
Message-ID: <0ef652f9b46540be8f0932dce7e6ad58@kau.se>
References: <HE1PR07MB3131400D823BD0CC3190B852C2A60@HE1PR07MB3131.eurprd07.prod.outlook.com>
In-Reply-To: <HE1PR07MB3131400D823BD0CC3190B852C2A60@HE1PR07MB3131.eurprd07.prod.outlook.com>
Accept-Language: en-US, sv-SE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.243.27.149]
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Bayes-Prob: 0.9999 (Score 5, tokens from: outbound, outbound-kau-se:default, kau-se:default, base:default, @@RPTN)
X-p0f-Info: os=Windows 7 or 8, link=Ethernet or modem
X-CanIt-Geo: No geolocation information available for fe80::7862:a3d3:1cba:9754
X-CanItPRO-Stream: outbound-kau-se:outbound (inherits from outbound-kau-se:default, kau-se:default, base:default)
X-Canit-Stats-ID: 092Em3qzi - bcd9a7246fd3 - 20200519
X-Antispam-Training-Forget: https://mailfilter.sunet.se/canit/b.php?c=f&i=092Em3qzi&m=bcd9a7246fd3&rlm=outbound-kau-se&t=20200519
X-Antispam-Training-Nonspam: https://mailfilter.sunet.se/canit/b.php?c=n&i=092Em3qzi&m=bcd9a7246fd3&rlm=outbound-kau-se&t=20200519
X-Antispam-Training-Phish: https://mailfilter.sunet.se/canit/b.php?c=p&i=092Em3qzi&m=bcd9a7246fd3&rlm=outbound-kau-se&t=20200519
X-Antispam-Training-Spam: https://mailfilter.sunet.se/canit/b.php?c=s&i=092Em3qzi&m=bcd9a7246fd3&rlm=outbound-kau-se&t=20200519
X-CanIt-Archive-Cluster: PfMRe/vJWMiXwM2YIH5BVExnUnw
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed; d=kau.se; h=from:to :subject:date:message-id:references:in-reply-to:content-type :content-transfer-encoding:mime-version; s=canit; bh=+kU6qsc+c72 75FbZPdFkethHlAqaOVWAu7jAP4Tr6uU=; b=WyWolgTs3rzEWC2HoqSOS+gc+kc dtkcU80N55RPjMoKB7nkRFFjIb1qdhjN/TwcVQoQP0r+mikx4/pjn8O2xnu/zkSS Gq31W4vZ8EDoMCbH5wVHuSZ6PWLFeH0FKbCTwtKTifiFe9v8G6Ek+Lk8qRDWAyRp iqiDzzWtbvBbGKwXQtxdvipG+8Mor7wUBLsPzUeXOezDt4BbpzhGxQ0Ke+xE4WWe t1UEoesOJ9eMCsGJIlrdm/RgwiX2vCYIxZbi1YWusaLMxOtrL5EZjUqTEcNZYZhf ZVoctsSvWTKWakxHf9p2bX7U0y7DbhDe8Z9rV9LvrvETrUgTLfvPaefWc8w==
X-Scanned-By: CanIt (www . roaringpenguin . com)
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/gfVQbOgCF8gOb_NTCKU6J-LhI1o>
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 22:03:33 -0000

Hi,

As the question is phrased I support option 1, but with some flavour of option 3.

I believe ECT(1) has greater potential as an input signal to the network than as an output signal, but I believe more work and testing is needed to understand how much of this potential we may be able to realize in different real network scenarios.  

Best Regards,
Anna

-----Original Message-----
> Date: Mon, 4 May 2020 14:15:07 -0400
> From: Wesley Eddy <wes@mti-systems.com>
> To: "tsvwg@ietf.org" <tsvwg@ietf.org>
> Subject: [tsvwg] Consensus call on ECT(1)
> Message-ID: <46720ce0-ffcb-e97f-3e2d-6b5274b73b15@mti-systems.com>
> Content-Type: text/plain; charset="utf-8"; Format="flowed"
> 
> **
> 
> *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.
> 
> 
>  1.
> 
>     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.
> 
>  2.
> 
>     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.
> 
>  3.
> 
>     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.
> 
> *