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

Luca Muscariello luca.muscariello at gmail.com
Sat Mar 23 17:04:35 EDT 2019

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 as WebEx,
Skype for business, WebRTC.
As I said, peering is key and cloud providers are doing that very well.
With the current widespread of SaaS and IaaS your app is likely running in
the cloud.

Even in case a branch office is connected using SD-WAN, DSCP is tunnelled
by it, and transparently for the application.

If working from home, the quality of peering of an SP to cloud providers is
I'd say that the Cloud and the decline of transit networks have facilitated
DSCP e2e.

On Sat, Mar 23, 2019 at 7:40 PM Mikael Abrahamsson <swmike at swm.pp.se> wrote:

> 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 remaking is done
> equally at the customer edge and peering/transit edge respectively.
> --
> Mikael Abrahamsson    email: swmike at swm.pp.se
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.bufferbloat.net/pipermail/bloat/attachments/20190323/083ce228/attachment-0002.html>

More information about the Bloat mailing list