Re: [Bloat] [Ecn-sane] [iccrg] Fwd: [tcpPrague] Implementation and experimentation of TCP Prague/L4S hackaton at IETF104

For enterprise networks interconnection to the cloud (public or private) can be done with e2e DSCP marking. This is just part of products available at AWS/Azure w/ or w/o their own interconnection network (direct connect, express route) and used regularly to ameliorate QoS of RTC applications such

Re: [Bloat] [Ecn-sane] [iccrg] Fwd: [tcpPrague] Implementation and experimentation of TCP Prague/L4S hackaton at IETF104

Hi Michael, thanks for the pointer. Looking forward to the talk... Regards Roland On 23.03.19 at 18:48 Michael Welzl wrote: > Hi, > > I’ll do what academics do and add our own data point, below: > >> On Mar 23, 2019, at 4:19 PM, Roland Bless > > wrote: >> >> Hi

Re: [Bloat] [Ecn-sane] [iccrg] Fwd: [tcpPrague] Implementation and experimentation of TCP Prague/L4S hackaton at IETF104

Hi Jonathan, On 23.03.19 at 16:03 Jonathan Morton wrote: >> On 23 Mar, 2019, at 11:02 am, Mikael Abrahamsson wrote: >> >> On Sat, 23 Mar 2019, Roland Bless wrote: >> >>> I suggest to use an additional DSCP to mark L4S packets. >> >> DSCP doesn't work end-to-end on the Internet, so what you're

Re: [Bloat] [Ecn-sane] [iccrg] Fwd: [tcpPrague] Implementation and experimentation of TCP Prague/L4S hackaton at IETF104

Hi Mikael, On 23.03.19 at 18:16 Mikael Abrahamsson wrote: > On Sat, 23 Mar 2019, Roland Bless wrote: > >> It's true that DSCPs may be remarked, but RFC 2474 >> already stated >> >>   Packets received with an unrecognized codepoint SHOULD be forwarded >>   as if they were marked for the Default

Re: [Bloat] [Ecn-sane] can we setup a "how to get this into existing networks" get-together in Prague coming week?

On Sat, 23 Mar 2019, Jonathan Morton wrote: Heated agreement from over here, despite my preference for flow isolation. Plain old AQM can be orders of magnitude better than a dumb FIFO. In my testing, FIFO with RED was already huge improvement over just plain FIFO. Configuring 1GE shaping

Re: [Bloat] [Ecn-sane] [iccrg] Fwd: [tcpPrague] Implementation and experimentation of TCP Prague/L4S hackaton at IETF104

Our paper has some data - again, fig. 4. That’s an AS level analysis, for the data that we had (which wasn’t huge - a couple thousand paths). For the majority of measurements, the DSCP survived more than 1 AS hop; in case of IPv6, the majority survived more than 2. Cheers, Michael > On Mar

Re: [Bloat] [Ecn-sane] can we setup a "how to get this into existing networks" get-together in Prague coming week?

> On 23 Mar, 2019, at 7:00 am, Holland, Jake wrote: > > I agree even getting some regular basic CE-marking stuff deployed > would probably be really cool if it can be done sanely. Heated agreement from over here, despite my preference for flow isolation. Plain old AQM can be orders of

Re: [Bloat] [Ecn-sane] [iccrg] Fwd: [tcpPrague] Implementation and experimentation of TCP Prague/L4S hackaton at IETF104

On Sat, 23 Mar 2019, Luca Muscariello wrote: It the app runs in the cloud and the cloud has direct peering links to your branch office or SP most likely DSCP works. Do you have numbers to back this statement up? In my experience direct peering links has nothing to do with this, instead

Re: [Bloat] [Ecn-sane] [iccrg] Fwd: [tcpPrague] Implementation and experimentation of TCP Prague/L4S hackaton at IETF104

WebEx, WebRTC they use it. QoS works. To answer the question in the title of Michael’s paper. It the app runs in the cloud and the cloud has direct peering links to your branch office or SP most likely DSCP works. And going back to Roland’s proposal, it seems the most natural approach instead of

Re: [Bloat] [Ecn-sane] [iccrg] Fwd: [tcpPrague] Implementation and experimentation of TCP Prague/L4S hackaton at IETF104

Hi, I’ll do what academics do and add our own data point, below: > On Mar 23, 2019, at 4:19 PM, Roland Bless wrote: > > Hi Mikael, > > On 23.03.19 at 11:02 Mikael Abrahamsson wrote: >> On Sat, 23 Mar 2019, Roland Bless wrote: >> >>> I suggest to use an additional DSCP to mark L4S packets. >>

Re: [Bloat] [Cerowrt-devel] Fwd: [104all] IETF 104 Remote Participation Information

Dave Taht wrote: > I would really like more folk to remotely attend the tsvwg wg meeting, > which is this monday: meetecho runs in any modern webrtc browser, no downloads. > 16:10-18:10Monday Afternoon session II Prague time. and you can also watch it on youtube a few days later,

Re: [Bloat] [Ecn-sane] [iccrg] Fwd: [tcpPrague] Implementation and experimentation of TCP Prague/L4S hackaton at IETF104

Hi Mikael, On 23.03.19 at 11:02 Mikael Abrahamsson wrote: > On Sat, 23 Mar 2019, Roland Bless wrote: > >> I suggest to use an additional DSCP to mark L4S packets. > > DSCP doesn't work end-to-end on the Internet, so what you're suggesting > isn't a workable solution. It's true that DSCPs may

Re: [Bloat] [Ecn-sane] [iccrg] Fwd: [tcpPrague] Implementation and experimentation of TCP Prague/L4S hackaton at IETF104

> On 23 Mar, 2019, at 11:02 am, Mikael Abrahamsson wrote: > > On Sat, 23 Mar 2019, Roland Bless wrote: > >> I suggest to use an additional DSCP to mark L4S packets. > > DSCP doesn't work end-to-end on the Internet, so what you're suggesting isn't > a workable solution. An interesting

[Bloat] Just recorded "It GPLs me" on the #BufferBoat.

https://youtu.be/0gx_r5ohYaA With an explanation of where and when it came from at the end. I've also got a pretty decent recording of "One first landing - a song for spacex" going... while fitting in some hacking on tcptrace and xplot. -- Dave Täht CTO, TekLibre, LLC http://www.teklibre.com

Re: [Bloat] [Ecn-sane] [iccrg] Fwd: [tcpPrague] Implementation and experimentation of TCP Prague/L4S hackaton at IETF104

On Sat, 23 Mar 2019, Roland Bless wrote: I suggest to use an additional DSCP to mark L4S packets. DSCP doesn't work end-to-end on the Internet, so what you're suggesting isn't a workable solution. -- Mikael Abrahamssonemail: swm...@swm.pp.se

Re: [Bloat] [Ecn-sane] [iccrg] Fwd: [tcpPrague] Implementation and experimentation of TCP Prague/L4S hackaton at IETF104

+1 On Sat, Mar 23, 2019 at 9:02 AM Roland Bless wrote: > Hi, > > On 22.03.19 at 19:28 Victor Hou wrote: > > > Broadcom has been deeply involved in developing the Low Latency DOCSIS > > cable industry specification that Bob Briscoe mentioned. We concur with > > the L4S use of ECT(1). L4S can

Re: [Bloat] [Ecn-sane] [iccrg] Fwd: [tcpPrague] Implementation and experimentation of TCP Prague/L4S hackaton at IETF104

Hi, On 22.03.19 at 19:28 Victor Hou wrote: > Broadcom has been deeply involved in developing the Low Latency DOCSIS > cable industry specification that Bob Briscoe mentioned.  We concur with > the L4S use of ECT(1).  L4S can be implemented either in a dual-queue or > an fq implementation. SCE

Re: [Bloat] [Ecn-sane] can we setup a "how to get this into existing networks" get-together in Prague coming week?

On 2019-03-21, 11:32, "Mikael Abrahamsson" wrote: I'll be at the IETF meeting monday-friday coming week, can we set up a meeting with some interested parties and actually have a "how do we get this into networks" kind of meeting. It would not be "my mechanism is better than