Discussion of explicit congestion notification's impact on the Internet
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Luca Muscariello <luca.muscariello@gmail.com>,
	Mikael Abrahamsson <swmike@swm.pp.se>
Cc: "ecn-sane\@lists.bufferbloat.net"
	<ecn-sane@lists.bufferbloat.net>,
	bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Ecn-sane] [Bloat] [iccrg] Fwd: [tcpPrague] Implementation and experimentation of TCP Prague/L4S hackaton at IETF104
Date: Sun, 17 Mar 2019 22:51:31 +0100	[thread overview]
Message-ID: <87tvg1tbj0.fsf@toke.dk> (raw)
In-Reply-To: <CAHx=1M7UhVUeQijT0v68F0OJDyyX9QBfHZKuRBDfLFKsZWSMfQ@mail.gmail.com>

Luca Muscariello <luca.muscariello@gmail.com> writes:

> To me there is substantial difference from something like fq_codel or
> fq_pie where service differentiation is largely implicit
> and approches largely based on explicit marking.
>
> Approaches based on marking face technical and non technical challenges
> that have been largely mentioned in these lists.
>
> Fq_codel has a ton of litterature behind both theoretical and experimental
> and it is something very close to optimality, in terms of completion time
> and latency.
>
> Fq_codel also incentivizes the development of better congestion control as
> the reward is immediate. It also makes  Internet performance
> predictable.
>
> Once we know that, the logical approach would be to try to approximate that
> thing when the full mechanism is not possible because of a variety of
> limitations.
>
> This is the case in some DC switches that implement AFD+priority fair
> queueing at 40Gbps.
>
> Fq_codel has an outstanding footprint in terms of deployment.
> Iliad deployed SFQ in 2005 nation wide and Fq_codel as soon as it was
> available in France and is the second largest ISP.
> Iliad/Free  controls the development of both the home GW and the DSLAM.
> They have recently started to commercialize 10Gbps to the home using
> switched Ethernet.
> I’m very tempted to test it.
>
> Kudos to them for being able to prove it is possible as long as you control
> the development of your equipment.
>
> A logical next step  to me seems to push chipcos to build fq_codel in
> silicon.
> It is totally feasible.
>
> If on the other hand we say that we can achieve all fq_codel provides with
> current chipsets we’ll never create the incentives to make progress.

+100!

-Toke

  reply	other threads:[~2019-03-17 21:51 UTC|newest]

Thread overview: 63+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <AM0PR07MB48198660539171737E4CCAB1E0730@AM0PR07MB4819.eurprd07.prod.outlook.com>
     [not found] ` <d91a6a71-5898-9571-2a02-0d9d83839615@bobbriscoe.net>
2019-03-15 10:46   ` [Ecn-sane] " Dave Taht
     [not found]     ` <1E80578D-A589-4CA0-9015-B03B63042355@gmx.de>
2019-03-15 14:06       ` [Ecn-sane] [Bloat] " Dave Taht
2019-03-15 15:52         ` Sebastian Moeller
2019-03-15 17:01           ` David P. Reed
2019-03-15 17:45             ` Sebastian Moeller
2019-03-15 18:36             ` Mikael Abrahamsson
2019-03-15 19:23               ` Sebastian Moeller
2019-03-15 19:32               ` Jonathan Morton
2019-03-15 19:44                 ` David P. Reed
2019-03-15 20:13                   ` Jonathan Morton
2019-03-15 23:43                     ` David P. Reed
2019-03-16  1:26                       ` Jonathan Morton
2019-03-16  7:38                       ` Sebastian Moeller
2019-03-16 18:56                         ` Michael Richardson
2019-03-15 20:28                 ` Jonathan Foulkes
2019-03-15 20:31                   ` Dave Taht
2019-03-15 23:45                     ` David P. Reed
2019-03-16  9:42                       ` Michael Welzl
2019-03-16 10:08                         ` Sebastian Moeller
2019-03-16 10:23                           ` Nils Andreas Svee
2019-03-16 14:55                             ` Jonathan Foulkes
2019-03-16 21:38               ` Holland, Jake
2019-03-16 21:57                 ` Vint Cerf
2019-03-16 22:03                   ` Dave Taht
2019-03-16 22:05                   ` Holland, Jake
2019-03-17 18:07                   ` David P. Reed
2019-03-17 18:05                     ` Vint Cerf
2019-03-19  4:44                     ` Greg White
2019-03-19  5:35                       ` Jonathan Morton
2019-03-19  5:52                         ` Greg White
2019-03-19  7:10                           ` Jonathan Morton
2019-03-19  8:07                             ` Sebastian Moeller
2019-03-19  8:50                       ` Sebastian Moeller
2019-03-19 23:59                       ` Dave Taht
2019-03-20 10:17                         ` Sebastian Moeller
     [not found]                     ` <5458c216-07b9-5b06-a381-326de49b53e0@bobbriscoe.net>
     [not found]                       ` <AC14ACBB-A7CC-40E0-882C-2519D05ADC05@akamai.com>
     [not found]                         ` <5C9296E1.4010703@erg.abdn.ac.uk>
     [not found]                           ` <F62C4839-0489-475F-AD8F-58913EEEEC0F@gmail.com>
     [not found]                             ` <FDA48F4C-415B-4B8E-9CC7-2AAAD4DC3BE8@cablelabs.com>
2019-03-20 22:12                               ` [Ecn-sane] [Bloat] [tsvwg] " Sebastian Moeller
2019-03-20 22:31                                 ` Jonathan Morton
2019-03-20 22:56                                   ` Sebastian Moeller
2019-03-20 23:03                                     ` Jonathan Morton
2019-03-20 23:11                                     ` Holland, Jake
2019-03-20 23:28                                       ` Jonathan Morton
2019-03-21  8:15                                         ` Mikael Abrahamsson
2019-03-21  8:31                                           ` Mikael Abrahamsson
2019-03-20 23:30                                       ` Sebastian Moeller
2019-03-21  0:15                                         ` Holland, Jake
2019-03-16 22:03                 ` [Ecn-sane] [Bloat] " Jonathan Morton
2019-03-16 22:09                 ` Sebastian Moeller
2019-03-17 14:06                 ` Mikael Abrahamsson
2019-03-17 17:37                   ` Loganaden Velvindron
2019-03-17 17:40                     ` Toke Høiland-Jørgensen
2019-03-17 17:44                     ` Mikael Abrahamsson
2019-03-17 18:00                       ` Dave Taht
2019-03-17 19:38                     ` Rodney W. Grimes
2019-03-17 20:50                   ` Luca Muscariello
2019-03-17 21:51                     ` Toke Høiland-Jørgensen [this message]
2019-03-18  4:26                     ` Mikael Abrahamsson
2019-03-16  4:04             ` Jonathan Morton
2019-03-16  4:51               ` Dave Taht
2019-03-15 18:07         ` Mikael Abrahamsson
2019-03-15 14:27       ` Jonathan Morton
2019-03-15 14:44         ` Sebastian Moeller
2019-03-15 15:49           ` Jonathan Morton
2019-03-15 21:34     ` Wesley Eddy

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=87tvg1tbj0.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=bloat@lists.bufferbloat.net \
    --cc=ecn-sane@lists.bufferbloat.net \
    --cc=luca.muscariello@gmail.com \
    --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