[Make-wifi-fast] Fwd: [NetDev-People] 0x14: nutsnbolts, What to do with 1/2 a bit? L4S, SCE, or ?

[Make-wifi-fast] Fwd: [NetDev-People] 0x14: nutsnbolts, What to do with 1/2 a bit? L4S, SCE, or ?

[Dave Taht]

---------- Forwarded message ---------
From: Jamal Hadi Salim via people <people@netdevconf.info>
Date: Sat, Feb 8, 2020 at 6:30 AM
Subject: [NetDev-People] 0x14: nutsnbolts, What to do with 1/2 a bit?
L4S, SCE, or ?
To: people <people@netdevconf.org>
Cc: <prog-committee-0x14@netdevconf.info>



Imagine you have only one more bit left in the world! Scratch
that. Imagine there is only a half bit left in the world.
Then imagine there are multiple causes vying for this half bit.
Who would you give it to and why?

Yes, these things happen;-> A lot easier when it is between developers
and a lot harder when it is to decide a standard that shall be cast
in stone. The Internet Engineering Task Force (ietf) Transport Area
Working Group (tsvwg) has such a struggle going.
There are presently 2 proposals before for the last unused code point
in the IPv4/6 header - one by the Low Latency Low Loss Scalable
throughput (L4S) folks (see Netdev 0x13 for L4S talks) and another
from the Some Congestion Experienced (SCE) folks.

In this talk, Rodney Grimes will describe the two solutions and their
prototype kernel implementations; what changes are made to both TCP and
IP layers, etc.

Rod is then going to pose the $1M question and solicit feedback:
is one approach better than the other or do we need a new outlook?

More info:
https://netdevconf.info/0x14/session.html?talk-what-to-do-with-half-a-bit-L4S-SCE-or-what

Reminder, registration is now open and early bird is still in effect.
https://netdevconf.info/0x14/registration.html

DT> It's more of a multi-billion dollar question, in my mind. And the
jury's still out as to where this works or not. Certainly on wifi I
don't see much benefit to anything more than rfc3168 at this point,
and would have liked far more folk to have been turning it on that
just apple to sort the bugs out. But I do concede that either SCE or
L4S style signalling has some benefit in the DC. In between, on other
tech, danged if I know. I'm really looking forward to the mmwave preso
also at this netdevconf, as the first exploration of what the internet
looks like at higher, flaky frequencies. I keep hoping starlink will
present somewhere as well.

There were (from my perspective) worrying things about slow
convergence times, gross rtt-unfairness in either approach in the last
set of l4S vs SCE  benchmarks I saw, and I keep hoping for a published
rrul test.

https://github.com/heistp/sce-l4s-bakeoff#scenario-3

To what little extent I've focused on this over the past year, was to
try and get a grip on the size of the RFC3168 and dctcp style
deployments, and to try and get a grip on how L4S style traffic would
actually look like in relation to the kinds of traffic I care more
about. I look forward to an update. and there are a remarkable number
of other presentations about advanced congestion control techniques at
this conference. I wasn't planning to go... still might not... but if
y'all do, try and catch the below talk.

I'd certainly like more folk to be experimenting with these two ideas
before they are cast in stone.


cheers,
jamal
_______________________________________________
people mailing list
people@netdevconf.org
https://lists.netdevconf.info/cgi-bin/mailman/listinfo/people


--
Make Music, Not War

Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729