Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: Dave Taht <dave@taht.net>
Cc: Cake List <cake@lists.bufferbloat.net>,
	 cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] [Cake] https://tools.ietf.org/html/draft-ietf-tsvwg-le-phb-06 is in last call
Date: Mon, 4 Feb 2019 08:11:39 +0100 (CET)	[thread overview]
Message-ID: <alpine.DEB.2.20.1902040806280.23912@uplift.swm.pp.se> (raw)
In-Reply-To: <87k1ig6nwd.fsf@taht.net>

On Sun, 3 Feb 2019, Dave Taht wrote:

> Well, (I just checked, let me know if you want the captures) comcast 
> still re-marks all codepoints it does not recognize, to become CS1, 
> including this one. So the smartest thing a comcast customer can do is 
> wash it out on entrance to their domain.

If I didn't think we ever could change things, I wouldn't support 
documents like these.

The idea is to go to the ISP community and say "Please treat LE as BE in 
your core/peering links, and only act on it on the customer access shaper 
(optional). Please don't bleach it."

000001 has never been in use before, so the hope is that people will allow 
this to happen. CS1 has had different meanings over time so it's harder to 
handle.

The problem with CAKE/FQ and background traffic is that it can't tell if 
there is congestion or not, and things like LEDBAT can't backoff and try 
to avoid causing congestion. So your previous email about allowing some 
congestion to take place on LE would be good as then protocols that try to 
avoid causing congestion would have a way to do so.

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

  reply	other threads:[~2019-02-04  7:11 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-03 18:39 [Cerowrt-devel] " Dave Taht
2019-02-03 20:02 ` Jonathan Morton
2019-02-03 22:42 ` David P. Reed
2019-02-04  0:17   ` Dave Taht
2019-02-04  1:12   ` [Cerowrt-devel] [Cake] " Jonathan Morton
2019-02-04  6:02   ` [Cerowrt-devel] " Mikael Abrahamsson
2019-02-04  6:58     ` [Cerowrt-devel] [Cake] " Dave Taht
2019-02-04  7:11       ` Mikael Abrahamsson [this message]
2019-02-04 10:23         ` Dave Taht
2019-02-04 10:34           ` Mikael Abrahamsson
2019-02-04 10:40             ` Dave Taht
2019-08-21 15:07 ` [Cerowrt-devel] " Dave Taht
2019-08-21 16:38   ` [Cerowrt-devel] [Cake] " Kevin Darbyshire-Bryant
2019-08-21 16:52     ` Dave Taht
2019-08-22  6:11       ` 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/cerowrt-devel.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.1902040806280.23912@uplift.swm.pp.se \
    --to=swmike@swm.pp.se \
    --cc=cake@lists.bufferbloat.net \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dave@taht.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