From: Dave Taht <dave.taht@gmail.com>
To: Mikael Abrahamsson <swmike@swm.pp.se>
Cc: Dave Taht <dave@taht.net>, Cake List <cake@lists.bufferbloat.net>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cake] [Cerowrt-devel] https://tools.ietf.org/html/draft-ietf-tsvwg-le-phb-06 is in last call
Date: Mon, 4 Feb 2019 02:23:53 -0800 [thread overview]
Message-ID: <CAA93jw4iU-yDmPqHe6ByFmFVy3YjUBUtFGz5+JqH29=zQ4OBsQ@mail.gmail.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1902040806280.23912@uplift.swm.pp.se>
On Sun, Feb 3, 2019 at 11:11 PM Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>
> 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.
I support this document. I note sqm and cake are the *only* QOS
systems out there that have ever bothered to pay attention to the
diffserv standards. I don't think netduma's "anti-bufferbloat" does,
nor does the mq, prio, etc qdiscs in linux.
>
> 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."
It's not a please. It's a three way contract with network services,
isps, and users. And of these, the users request should be paramount.
short of a lawsuit I don't see any way comcast can be coerced to
remove the *one* line in their cmts config files that remarks traffic.
... but hey, miracles happen.
passing CS1 through to wifi really sucks. Bleaching all diffserv from
comcast at the edge makes sense until that miracle happens.
>
> 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.
I agree. CS1 has caused no end of trouble for a good idea.
> 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.
I do not like that the standard allows for total starvation. I would
prefer it had a minimum of 5%.
>
> --
> Mikael Abrahamsson email: swmike@swm.pp.se
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
--
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-205-9740
next prev parent reply other threads:[~2019-02-04 10:24 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-03 18:39 [Cake] " Dave Taht
2019-02-03 20:02 ` [Cake] [Cerowrt-devel] " Jonathan Morton
2019-02-03 22:42 ` David P. Reed
2019-02-04 0:17 ` Dave Taht
2019-02-04 1:12 ` Jonathan Morton
2019-02-04 6:02 ` Mikael Abrahamsson
2019-02-04 6:58 ` Dave Taht
2019-02-04 7:11 ` Mikael Abrahamsson
2019-02-04 10:23 ` Dave Taht [this message]
2019-02-04 10:34 ` Mikael Abrahamsson
2019-02-04 10:40 ` Dave Taht
2019-08-21 15:07 ` [Cake] " Dave Taht
2019-08-21 16:38 ` Kevin Darbyshire-Bryant
2019-08-21 16:52 ` [Cake] [Cerowrt-devel] " 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/cake.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw4iU-yDmPqHe6ByFmFVy3YjUBUtFGz5+JqH29=zQ4OBsQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dave@taht.net \
--cc=swmike@swm.pp.se \
/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