From: Dave Taht <dave.taht@gmail.com>
To: "Rodney W. Grimes" <4bone@gndrsh.dnsmgr.net>
Cc: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] more edge cases for ecn?
Date: Sun, 19 Sep 2021 09:26:47 -0700 [thread overview]
Message-ID: <CAA93jw6HOAqu8U8SpzCRq443RaAJr3yj1piM3Tnvnd7-YLSMrA@mail.gmail.com> (raw)
In-Reply-To: <202109191621.18JGL3Wv037836@gndrsh.dnsmgr.net>
I am very happy to hear someone other than us, is going to tackle
this, and discuss it in this talk.
Usually the problem is the other way around, standards not keeping up
with linux.
On Sun, Sep 19, 2021 at 9:21 AM Rodney W. Grimes
<4bone@gndrsh.dnsmgr.net> wrote:
>
> > 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
--
Fixing Starlink's Latencies: https://www.youtube.com/watch?v=c9gLo6Xrwgw
Dave Täht CEO, TekLibre, LLC
prev parent reply other threads:[~2021-09-19 16:27 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
2021-09-19 16:26 ` Dave Taht [this message]
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=CAA93jw6HOAqu8U8SpzCRq443RaAJr3yj1piM3Tnvnd7-YLSMrA@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=4bone@gndrsh.dnsmgr.net \
--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