Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: "ecn-sane@lists.bufferbloat.net" <ecn-sane@lists.bufferbloat.net>,
	 bloat <bloat@lists.bufferbloat.net>
Subject: [Ecn-sane] can we setup a "how to get this into existing networks" get-together in Prague coming week?
Date: Thu, 21 Mar 2019 11:31:39 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1903211121530.3161@uplift.swm.pp.se> (raw)

On Thu, 21 Mar 2019, Mikael Abrahamsson wrote:

> Btw, in 
> http://1ukcym66nom10cmylunctf84-wpengine.netdna-ssl.com/wp-content/uploads/2018/11/TR-156_Issue-2-1.pdf 
> 5.2.x you can see how scheduling is done. If you'd like something like 
> that changed then anything new needs to go into documents like these in 
> order to get further deplyment.

Btw, I reached out to some people here at the BBF about doing 
anti-bufferbloat in this context and getting this into the documents, and 
there is no reason why this can't be introduced.

Now, the proposal needs to be "reasonable" and implementable, so if 
someone would be interested in work like that I'd like to hear from you. I 
have taken initiative in trying to come up with configuration guidance for 
operators for their existing equipment, and that could be a way forward.

So this won't be "put CAKE or FQ_CODEL everywhere", but instead introduce 
configuration guidance regarding bufferbloat, best common practice for 
different deployment scenarios etc. Let's not try to boil the ocean right 
away, but let's try to point industry in the right direction. BBF creates 
documents that architects networks that connects ~1B households, so 
whatever we come up with could benefit lots of people.

I understand that for some people here this will seem like stone age 
primive mechanisms, but it's still better than doing nothing at all (which 
is often the case). It would especially be beneficial to get similar 
guidance from several organisations (CableLabs and BBF would be two that 
immediately comes to mind).

I'll be at the IETF meeting monday-friday coming week, can we set up a 
meeting with some interested parties and actually have a "how do we get 
this into networks" kind of meeting. It would not be "my mechanism is 
better than yours" meeting, I'm not interested in that in this context.

I'm interested in "what can we do to improve the situation in the next 1-2 
years including installed base".

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

             reply	other threads:[~2019-03-21 10:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-21 10:31 Mikael Abrahamsson [this message]
2019-03-23  6:00 ` Holland, Jake
2019-03-23 19:01   ` Jonathan Morton
2019-03-23 19:12     ` Mikael Abrahamsson
2019-03-26 11:06       ` Holland, Jake
2019-03-26 13:20         ` Mikael Abrahamsson

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=alpine.DEB.2.20.1903211121530.3161@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=bloat@lists.bufferbloat.net \
    --cc=chromatix99@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