Re: [tsvwg] Gorry Fairhurst Individual thoughts on choosing whether/howto advance ECN work.

Paul Vixie <paul@redbarn.org> Sat, 23 May 2020 23:49 UTC

Return-Path: <paul@redbarn.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 B94093A103E for <tsvwg@ietfa.amsl.com>; Sat, 23 May 2020 16:49:53 -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, 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 mxr4Hcujgc3y for <tsvwg@ietfa.amsl.com>; Sat, 23 May 2020 16:49:51 -0700 (PDT)
Received: from family.redbarn.org (family.redbarn.org [IPv6:2001:559:8000:cd::5]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8BE5C3A0FE1 for <tsvwg@ietf.org>; Sat, 23 May 2020 16:49:42 -0700 (PDT)
Received: from linux-9daj.localnet (vixp1.redbarn.org [24.104.150.140]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by family.redbarn.org (Postfix) with ESMTPSA id 7399BB074A; Sat, 23 May 2020 23:49:40 +0000 (UTC)
From: Paul Vixie <paul@redbarn.org>
To: Ilpo Järvinen <ilpo.jarvinen@cs.helsinki.fi>, tsvwg@ietf.org
Cc: Gorry Fairhurst <gorry@erg.abdn.ac.uk>, Joseph Touch <touch@strayalpha.com>, tsvwg@ietf.org, Sebastian Moeller <moeller0@gmx.de>
Date: Sat, 23 May 2020 23:49:39 +0000
Message-ID: <4546339.5God0RhuhZ@linux-9daj>
Organization: none
In-Reply-To: <C59E1B15-DED6-491F-8D46-5E2F81CF31B4@gmx.de>
References: <dbc71da6-70f1-7369-1d2d-f08fb3b08b69@erg.abdn.ac.uk> <5D7C2E01-F71D-441B-B611-2D156947C14E@gmx.de> <C59E1B15-DED6-491F-8D46-5E2F81CF31B4@gmx.de>
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/sPBa8DtZEL05Ra5icUnt8qRbjGE>
Subject: Re: [tsvwg] Gorry Fairhurst Individual thoughts on choosing whether/howto advance ECN work.
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, 23 May 2020 23:49:59 -0000

On Saturday, 23 May 2020 22:09:21 UTC Sebastian Moeller wrote:
> ...
> 
> I hope you agree that there is no clear significant complexity difference
> between L4S and fq_codel if measured by lines of code. I am not claiming
> that that is an ideal measure, but it sure beats lines of pseudocode.

complexity is better measured in terms of state variables and transitions; 
there's nothing published i can find which compares these two competing 
approaches in those terms, and so i'm inclined to think in terms of network 
carried vs. edge carried complexity. it's the placement in this case, not the 
magnitude, that concerns me. i liked the fq_codel approach because it helped 
immediately and measurably at every increment of deployment, nobody had to 
deploy on faith as in ipv6 and dnssec that benefits would come later when 
others also deployed. so if you're counting fan boys, i'm an edge-complexity 
guy, even if the mass of all those edges each carrying all that flow state is 
higher overall than a smart-core approach.

i realize that nobody is proposing the fr/atm model (cir, br, per flow) but i 
still get cold chills down my spine when i hear a proposal for core complexity 
-- of whatever kind.

-- 
Paul