From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <4bone@gndrsh.dnsmgr.net> Received: from gndrsh.dnsmgr.net (br1.CN84in.dnsmgr.net [69.59.192.140]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 279B03B29D for ; Sun, 19 Sep 2021 12:21:07 -0400 (EDT) Received: from gndrsh.dnsmgr.net (localhost [127.0.0.1]) by gndrsh.dnsmgr.net (8.13.3/8.13.3) with ESMTP id 18JGL3k4037837; Sun, 19 Sep 2021 09:21:04 -0700 (PDT) (envelope-from 4bone@gndrsh.dnsmgr.net) Received: (from 4bone@localhost) by gndrsh.dnsmgr.net (8.13.3/8.13.3/Submit) id 18JGL3Wv037836; Sun, 19 Sep 2021 09:21:03 -0700 (PDT) (envelope-from 4bone) From: "Rodney W. Grimes" <4bone@gndrsh.dnsmgr.net> Message-Id: <202109191621.18JGL3Wv037836@gndrsh.dnsmgr.net> In-Reply-To: To: Dave Taht Date: Sun, 19 Sep 2021 09:21:03 -0700 (PDT) CC: ECN-Sane X-Mailer: ELM [version 2.4ME+ PL121h (25)] MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Type: text/plain; charset=US-ASCII Subject: Re: [Ecn-sane] more edge cases for ecn? X-BeenThere: ecn-sane@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: Discussion of explicit congestion notification's impact on the Internet List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 19 Sep 2021 16:21:07 -0000 > https://linuxplumbersconf.org/event/11/contributions/943/ Dave, The people that wrote this need to be informed about how to use the RFC's and the IETF datatracker. First and formost they start off CITING rfc1349 which has been OBSOLETED by RFC2474, in 1998 no less, so anything and everthing refering to rfc1349 is refering to the wrong document. Saying there is a "conflict" between two documents when one was obsoleted by the other is just non-sense. The fact that LINUX still has RFC1349 TOS stuff in it is what is "conflicted", not the RFC's. Linux continues to use and support a now 23 year obsoleted model of the byte being discussed. This lack of following the updates in the standards is infact causing the current ECN usage some issues. I'll note that at least FreeBSD, and I believe the other BSD's have some vestigaes of this stuff around, but it is not in use as far as I can tell. Ie, there are defines, but nothing is using them. And IIRC the one bit that is defanitly different no longer even has a define. Regards, Rod Grimes > Dave T?ht CEO, TekLibre, LLC -- Rod Grimes rgrimes@freebsd.org