IETF Logo Mail Archive

Re: [tsvwg] Adoption call for draft-white-tsvwg-l4sops - to conclude 24th March 2021

Steven Blake <slblake@petri-meat.com> Fri, 26 March 2021 02:22 UTC

Return-Path: <slblake@petri-meat.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 02C443A150B for <tsvwg@ietfa.amsl.com>; Thu, 25 Mar 2021 19:22:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_MSPIKE_H2=-0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 9CUS7vAWXO_I for <tsvwg@ietfa.amsl.com>; Thu, 25 Mar 2021 19:22:18 -0700 (PDT)
Received: from quail.birch.relay.mailchannels.net (quail.birch.relay.mailchannels.net [23.83.209.151]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 338373A150A for <tsvwg@ietf.org>; Thu, 25 Mar 2021 19:22:18 -0700 (PDT)
X-Sender-Id: totalchoicehosting|x-authuser|slblake+petri-meat.com@eagle.tchmachines.com
Received: from relay.mailchannels.net (localhost [127.0.0.1]) by relay.mailchannels.net (Postfix) with ESMTP id D8BE73418C1; Fri, 26 Mar 2021 02:22:16 +0000 (UTC)
Received: from eagle.tchmachines.com (100-98-55-5.trex.outbound.svc.cluster.local [100.98.55.5]) (Authenticated sender: totalchoicehosting) by relay.mailchannels.net (Postfix) with ESMTPA id 5950F34186A; Fri, 26 Mar 2021 02:22:14 +0000 (UTC)
X-Sender-Id: totalchoicehosting|x-authuser|slblake+petri-meat.com@eagle.tchmachines.com
Received: from eagle.tchmachines.com (eagle.tchmachines.com [208.76.80.20]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384) by 100.98.55.5 (trex/6.1.1); Fri, 26 Mar 2021 02:22:16 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: totalchoicehosting|x-authuser|slblake+petri-meat.com@eagle.tchmachines.com
X-MailChannels-Auth-Id: totalchoicehosting
X-Celery-Coil: 1648c53e402726dd_1616725336594_172061075
X-MC-Loop-Signature: 1616725336594:132785139
X-MC-Ingress-Time: 1616725336594
Received: from [136.56.88.61] (port=38294 helo=axion.home.arpa) by eagle.tchmachines.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94) (envelope-from <slblake@petri-meat.com>) id 1lPc72-0002Ys-L0; Thu, 25 Mar 2021 22:22:12 -0400
Message-ID: <1987273c692c3c9f6f63219a9d998f4b1b4f4d22.camel@petri-meat.com>
From: Steven Blake <slblake@petri-meat.com>
To: Bob Briscoe <ietf@bobbriscoe.net>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Date: Thu, 25 Mar 2021 22:22:12 -0400
In-Reply-To: <296c7a3b-15fc-5a30-efc0-cdc27a176db3@bobbriscoe.net>
References: <e9da704b-7705-baf9-a82c-39d4fe4e7ef1@erg.abdn.ac.uk> <98c8af7ffd471d6c353006c92c7deb3c28441557.camel@petri-meat.com> <0958b1c7-f4d2-ac7c-c127-b6fefef8f554@bobbriscoe.net> <18b86be43d62ea0a7dc55c760a50818dc68234ef.camel@petri-meat.com> <296c7a3b-15fc-5a30-efc0-cdc27a176db3@bobbriscoe.net>
Content-Type: text/plain; charset="UTF-8"
User-Agent: Evolution 3.34.4 (3.34.4-1.fc31)
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
X-AuthUser: slblake+petri-meat.com@eagle.tchmachines.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/mbGcVmPcaKbzkZrOi-RaaDGDDt8>
Subject: Re: [tsvwg] Adoption call for draft-white-tsvwg-l4sops - to conclude 24th March 2021
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 02:22:20 -0000

On Thu, 2021-03-25 at 09:26 +0000, Bob Briscoe wrote:

> [BB] There is a common belief that, if any RFC3168 FIFO AQMs exist,
> they 
> will be rare. But Jake and Jonathan raised the concern that it still 
> needs to be possible to deploy RFC3168 routers from now onwards. In
> that 
> case, operators that *don't wish to participate* would be updating
> their 
> config, and l4sops then gives router developers ideas for how they
> might 
> be able to prevent an existing implementation of RFC3168 from acting
> on 
> ECT(1), given an ECN implementation is likely to be hard-coded
> against 
> the ECN codepoints.

RFC-3168 ECN is a feature that router vendors have been shipping for
about two decades. Unless and until the IETF deprecates RFC-3168 (or
vendors EOL the feature), it should remain perfectly safe for operators
to enable it without having to track whatever experimental RFCs IETF
decides to publish, or without having to install patch releases.

All IMHO.


Regards,

// Steve

v2.23.0 | Report a Bug | By Email