From: Pete Heist <pete@heistp.net>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Jonathan Morton <chromatix99@gmail.com>,
Mikael Abrahamsson <swmike@swm.pp.se>,
Jonathan Foulkes <jfoulkes@evenroute.com>,
"ecn-sane@lists.bufferbloat.net" <ecn-sane@lists.bufferbloat.net>,
Dave Taht <dave@taht.net>, "tsvwg@ietf.org" <tsvwg@ietf.org>
Subject: Re: [Ecn-sane] is FQ actually widely deployed?
Date: Mon, 22 Jul 2019 14:02:00 -0400 [thread overview]
Message-ID: <E715CEEC-EF5C-4E1C-933E-F3B462B332A1@heistp.net> (raw)
In-Reply-To: <87sgqy3sqh.fsf@toke.dk>
> On Jul 22, 2019, at 1:05 PM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
>
> Jonathan Morton <chromatix99@gmail.com> writes:
>
>>> On 22 Jul, 2019, at 10:14 am, Mikael Abrahamsson <swmike@swm.pp.se> wrote:
>>>
>>> Do we have numbers on how much FQ is actually out there? If we don't,
>>> can we measure it? Anyone know of devices shipping or being designed
>>> that does FQ of some kind?
>>
>> There's also a large French ISP which has done fq_codel on its last
>> mile for quite some time.
>
> I am aware of at least two Danish and one Norwegian ISP that have
> deployed FQ-CoDel-based shapers either as their customer shapers in the
> backend or on CPEs.
In Czech, I’m aware at least of two WISPs that use it. It’s a good bet there
are more, as a company has popped up specifically targeting WISPs which
uses passive monitoring and fq_codel to measure and improve customer
qoe. It doesn’t take too much searching to find them.
next prev parent reply other threads:[~2019-07-22 18:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-22 14:14 Mikael Abrahamsson
2019-07-22 15:20 ` Jonathan Morton
2019-07-22 17:05 ` Toke Høiland-Jørgensen
2019-07-22 18:02 ` Pete Heist [this message]
2019-07-23 5:32 ` Mikael Abrahamsson
2019-07-23 5:57 ` Sebastian Moeller
2019-07-23 6:06 ` Jonathan Morton
2019-07-22 22:14 ` Jonathan Foulkes
2019-07-22 22:24 ` Jonathan Morton
2019-07-22 17:09 ` Dave Taht
2019-07-23 5:34 ` Mikael Abrahamsson
2019-07-23 6:13 ` Sebastian Moeller
2019-07-23 6:21 ` Mikael Abrahamsson
2019-07-23 10:57 ` 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=E715CEEC-EF5C-4E1C-933E-F3B462B332A1@heistp.net \
--to=pete@heistp.net \
--cc=chromatix99@gmail.com \
--cc=dave@taht.net \
--cc=ecn-sane@lists.bufferbloat.net \
--cc=jfoulkes@evenroute.com \
--cc=swmike@swm.pp.se \
--cc=toke@toke.dk \
--cc=tsvwg@ietf.org \
/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