From: "Rodney W. Grimes" <4bone@gndrsh.dnsmgr.net>
To: Dave Taht <dave.taht@gmail.com>
Cc: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] more edge cases for ecn?
Date: Sun, 19 Sep 2021 09:21:03 -0700 (PDT) [thread overview]
Message-ID: <202109191621.18JGL3Wv037836@gndrsh.dnsmgr.net> (raw)
In-Reply-To: <CAA93jw5hC8npAeJtCB45qNDY1nfK2RdNfzv93S_XPi+cNAceOA@mail.gmail.com>
> 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
next prev parent reply other threads:[~2021-09-19 16:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-18 19:26 Dave Taht
2021-09-19 16:21 ` Rodney W. Grimes [this message]
2021-09-19 16:26 ` Dave Taht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/ecn-sane.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=202109191621.18JGL3Wv037836@gndrsh.dnsmgr.net \
--to=4bone@gndrsh.dnsmgr.net \
--cc=dave.taht@gmail.com \
--cc=ecn-sane@lists.bufferbloat.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox