Re: [PANRG] Updated text on ECN: draft-irtf-panrg-what-not-to-do-19 to be ...

Gorry Fairhurst <gorry@erg.abdn.ac.uk> Wed, 24 March 2021 15:52 UTC

Return-Path: <gorry@erg.abdn.ac.uk>
X-Original-To: panrg@ietfa.amsl.com
Delivered-To: panrg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id A6F523A2F45; Wed, 24 Mar 2021 08:52:15 -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, HTML_MESSAGE=0.001, NICE_REPLY_A=-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 U3g02CZdf8uc; Wed, 24 Mar 2021 08:52:13 -0700 (PDT)
Received: from pegasus.erg.abdn.ac.uk (pegasus.erg.abdn.ac.uk [IPv6:2001:630:42:150::2]) by ietfa.amsl.com (Postfix) with ESMTP id 29B9C3A2F43; Wed, 24 Mar 2021 08:52:13 -0700 (PDT)
Received: from GF-MBP-2.lan (fgrpf.plus.com [212.159.18.54]) by pegasus.erg.abdn.ac.uk (Postfix) with ESMTPSA id B6A281B000FF; Wed, 24 Mar 2021 15:52:05 +0000 (GMT)
To: Spencer Dawkins at IETF <spencerdawkins.ietf@gmail.com>, panrg@irtf.org
Cc: panrg-chairs <panrg-chairs@irtf.org>, irtf-chair@irtf.org
References: <d072512f-ed66-bb8b-7338-58ed720210a2@erg.abdn.ac.uk> <CAKKJt-c7ZopV5pYredyLjd1o=vwVKzCOm+ccHx9oYCLK1U4aKA@mail.gmail.com> <CAKKJt-eW=6GARREi+=v21cP+RQP8iFm-_j-rcotHG0oW_-iHqQ@mail.gmail.com> <CAKKJt-czPFBBeqNCRvOq+hhXJ7Bu_zetNuisEdff6ouhg2kjBg@mail.gmail.com>
From: Gorry Fairhurst <gorry@erg.abdn.ac.uk>
Message-ID: <cc230e1d-e215-c53e-aafe-6497168f6728@erg.abdn.ac.uk>
Date: Wed, 24 Mar 2021 15:52:05 +0000
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:78.0) Gecko/20100101 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <CAKKJt-czPFBBeqNCRvOq+hhXJ7Bu_zetNuisEdff6ouhg2kjBg@mail.gmail.com>
Content-Type: multipart/alternative; boundary="------------EA116C03C849184343863705"
Content-Language: en-GB
Archived-At: <https://mailarchive.ietf.org/arch/msg/panrg/hh3Y3Eg_vVZ8BbELXo55OchvXKQ>
Subject: Re: [PANRG] Updated text on ECN: draft-irtf-panrg-what-not-to-do-19 to be ...
X-BeenThere: panrg@irtf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "Path Aware Networking \(Proposed\) Research Group discussion list" <panrg.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/panrg>, <mailto:panrg-request@irtf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/panrg/>
List-Post: <mailto:panrg@irtf.org>
List-Help: <mailto:panrg-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/panrg>, <mailto:panrg-request@irtf.org?subject=subscribe>
X-List-Received-Date: Wed, 24 Mar 2021 15:52:16 -0000

Thanks for doing this Spencer!

This particular bit doesn't seem to read correctly:

On 24/03/2021 14:45, Spencer Dawkins at IETF wrote:
> *During discussion of ECN at {{PANRG-110}}, we noted that "you get one 
> chance to get it right" isn't quite correct today, because so 
> operating systems on so many host systems are frequently updated, 
> which was not at all true in the early 2000s. We think that these 
> restatements of the ECN Lessons Learned are more useful for current 
> implementers: *

Is there a sprurious "so"?

- I think the argument that OS "*are frequently updated" does not sit so 
well with me. True, there are many updates that simply were not as often 
in the early 2000s. It's still quite painful introducing innovation in 
some parts of the OS.
*

*- Also perhaps more important, QUIC argued these were not enough to 
allow innovation so moved to userland stacks.
*

*I wonder then whether the words "operating systems" are actually better 
written as "protocol stacks"?*

*Gorry
*