Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: "Rodney W. Grimes" <4bone@gndrsh.dnsmgr.net>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Dave Taht <dave.taht@gmail.com>,
	Cake List <cake@lists.bufferbloat.net>,
	ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] [Cake]   l4s kernel submission
Date: Sat, 16 Oct 2021 09:58:14 -0700 (PDT)	[thread overview]
Message-ID: <202110161658.19GGwEm2051661@gndrsh.dnsmgr.net> (raw)
In-Reply-To: <95231AF9-DCCA-4D41-9BF4-8F55307F45F6@gmail.com>

Jonathan, etc,

I went fishing down the rabbit hole and think I see
how the masses have been brainwashed about L4S, at
least partially.  It might be worth spending some
effort to "debunk" the claims in the paper:
	https://bobbriscoe.net/projects/latency/dctth_journal_draft20190726.pdf

I am EXTREAMLY concerned about the following miss leading
assertions by the authors:
	"
BEGIN-QUOTE
V.  DEPLOYMENTCONSIDERATIONS
  A.  Standardization Requirements
    The IETF has taken on L4S standardization work [13]. [19]
    considers the pros and cons of various candidate identifiers for
    L4S  and  finds  that  none  are  without  problems,  but  proposes
    ECT(1)  as  the  least  worst.  As  a  consequence,  the  IETF  has
    updated the ECN standard at the IP layer (v4 and v6) to make
    the ECT(1) codepoint available for experimentation [7].

 [7]   BLACK, D.   Relaxing  Restrictions  on  Explicit  Congestion  Notification
      (ECN) Experimentation.  Request for Comments RFC8311, RFC Editor,Jan. 2018
END-QUOTE


My problem with this "claim" is that it is made in the name of
the IETF, which is not true.  Bob Briscoe and others are who
are making these claims, the IETF has NOT yet spoken formally
on L4S.

Though RFC8311 DOES relax the restrictions, Bob etc al, make it
sound as if L4S is a done deal.

Regards,
Rod

> > On 15 Oct, 2021, at 1:17 am, Dave Taht <dave.taht@gmail.com> wrote:
> > 
> >> You can also subscribe to Linux lists by importing the mails from Lore,
> >> as one of the replies in the thread above pointed out. Been meaning to
> >> switch to that myself, but haven't gotten around to it yet...
> > 
> > I attempted to subscribe again, nothing happened.
> > 
> > figuring out lore... is too much work for today. I'd rather hammer
> > small things into oblivion on my boat.
> > 
> > please feel free to pass along my comments and the sce teams findings
> > into that thread.
> 
> https://lore.kernel.org/all/308C88C6-D465-4D50-8038-416119A3535C@gmail.com/
> 
> I haven't yet posted a link to the WGLC Objections document.  I will if it seem s necessary to do so.
> 
>  - Jonathan Morton
> _______________________________________________
> Ecn-sane mailing list
> Ecn-sane@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/ecn-sane
> 
> 

-- 
Rod Grimes                                                 rgrimes@freebsd.org

  parent reply	other threads:[~2021-10-16 16:58 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14 20:06 [Ecn-sane] " Dave Taht
2021-10-14 20:31 ` [Ecn-sane] [Cake] " Sebastian Moeller
2021-10-14 21:27   ` Dave Taht
2021-10-14 21:44     ` Toke Høiland-Jørgensen
2021-10-14 22:00       ` Dave Taht
2021-10-14 22:10         ` Toke Høiland-Jørgensen
2021-10-14 22:17           ` Dave Taht
2021-10-16  8:04             ` Jonathan Morton
2021-10-16  8:38               ` Sebastian Moeller
2021-10-16  8:54                 ` Jonathan Morton
2021-10-16 10:29                   ` Sebastian Moeller
2021-10-16 12:49                   ` Sebastian Moeller
2021-10-16 16:58               ` Rodney W. Grimes [this message]
2021-10-16 21:01             ` Dave Taht
2021-10-18 13:02               ` Toke Høiland-Jørgensen
2021-10-19  2:45                 ` Dave Taht
2021-10-19 11:19                   ` Toke Høiland-Jørgensen
2021-10-19 13:30                     ` Dave Taht
2021-10-19 13:34                       ` Sebastian Moeller
2021-10-19 14:16                         ` 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=202110161658.19GGwEm2051661@gndrsh.dnsmgr.net \
    --to=4bone@gndrsh.dnsmgr.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --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