IETF Logo Mail Archive

Re: [tsvwg] Review comments on a careful read of the L4S ID

Steven Blake <slblake@petri-meat.com> Sat, 08 May 2021 16:23 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 A10A83A1E6F for <tsvwg@ietfa.amsl.com>; Sat, 8 May 2021 09:23:47 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, 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 IXjFcrnCSYGB for <tsvwg@ietfa.amsl.com>; Sat, 8 May 2021 09:23:44 -0700 (PDT)
Received: from crocodile.elm.relay.mailchannels.net (crocodile.elm.relay.mailchannels.net [23.83.212.45]) (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 9CEEF3A1E6E for <tsvwg@ietf.org>; Sat, 8 May 2021 09:23:44 -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 7CA6F10185E; Sat, 8 May 2021 16:23:43 +0000 (UTC)
Received: from eagle.tchmachines.com (100-96-27-184.trex.outbound.svc.cluster.local [100.96.27.184]) (Authenticated sender: totalchoicehosting) by relay.mailchannels.net (Postfix) with ESMTPA id 97E891019DB; Sat, 8 May 2021 16:23:42 +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.96.27.184 (trex/6.2.1); Sat, 08 May 2021 16:23:43 +0000
X-MC-Relay: Neutral
X-MailChannels-SenderId: totalchoicehosting|x-authuser|slblake+petri-meat.com@eagle.tchmachines.com
X-MailChannels-Auth-Id: totalchoicehosting
X-Eyes-Tasty: 31fa4b2149a4a410_1620491023092_1273396376
X-MC-Loop-Signature: 1620491023092:190225224
X-MC-Ingress-Time: 1620491023092
Received: from [136.56.88.61] (port=56342 helo=axion.home.arpa) by eagle.tchmachines.com with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from <slblake@petri-meat.com>) id 1lfPjw-00048B-3b; Sat, 08 May 2021 12:23:41 -0400
Message-ID: <34873ea1d924756b0b3385dac4edfc1eca181868.camel@petri-meat.com>
From: Steven Blake <slblake@petri-meat.com>
To: "C. M. Heard" <heard@pobox.com>, Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Cc: TSVWG <tsvwg@ietf.org>
Date: Sat, 08 May 2021 12:23:40 -0400
In-Reply-To: <CACL_3VHaheyR=4GKL4BNYprXxEubMkA49WQKQ3uzn=WZVgYusg@mail.gmail.com>
References: <634676ca-272d-d616-c352-b38446cf7aab@erg.abdn.ac.uk> <a97fa9fd-3721-af32-a486-7c966d7d108c@tomh.org> <MN2PR19MB40458998C271D5227886866183589@MN2PR19MB4045.namprd19.prod.outlook.com> <1323d4b6-326e-f35d-b481-4921d5f52b8e@erg.abdn.ac.uk> <5F9FF409-67B8-4F47-8587-260C2130AD99@gmx.de> <8a4129f5-e449-7237-e664-3a04b4177f1b@erg.abdn.ac.uk> <491B6198-346D-4F16-B5D5-3D475B2E09FA@gmx.de> <5ee8f2b4-28a3-d24a-d6f7-caa3b8e22756@erg.abdn.ac.uk> <CACL_3VHaheyR=4GKL4BNYprXxEubMkA49WQKQ3uzn=WZVgYusg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="=-VRebsTX9b+UgsOIWpzu6"
User-Agent: Evolution 3.34.4 (3.34.4-1.fc31)
MIME-Version: 1.0
X-AuthUser: slblake+petri-meat.com@eagle.tchmachines.com
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/Viuygx6QEtcjRx-A4X-kGpX__d0>
Subject: Re: [tsvwg] Review comments on a careful read of the L4S ID
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: Sat, 08 May 2021 16:23:48 -0000

On Sat, 2021-05-08 at 08:15 -0700, C. M. Heard wrote:
> On Fri, May 7, 2021 at 11:22 PM Gorry Fairhurst  wrote:
> > [GF] You seem to keep arguing in a direction that would result in 
> > 
> > obsoleting RFC3168 before we progress L4S, but I don't agree this 
> > 
> > ordering is needed. The proposal I see is that the deployment
> > takes 
> > 
> > place and then the IETF has the option to decide what happens next.
> 
> Seeing the word ***deployment*** instead of the word ***experiment***
> in the last sentence above,  I have to agree with Sebastian on this
> point.
> 
> Mike Heard  
>  

Which is why people keep arguing that the L4S "deployment" needs to be
isolated to networks that are confirmed to not be deploying RFC 3168
ECN, because L4S and RFC 3168 ECN are incompatible.


Regards,





  
  


// Steve

v2.23.0 | Report a Bug | By Email