From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oi1-x22e.google.com (mail-oi1-x22e.google.com [IPv6:2607:f8b0:4864:20::22e]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id B3FB93CB37 for ; Sat, 23 Mar 2019 17:04:48 -0400 (EDT) Received: by mail-oi1-x22e.google.com with SMTP id w139so4238964oie.9 for ; Sat, 23 Mar 2019 14:04:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=xAz5Rrk4KFsiIv8CSyiiU7MH8ek3WZ1fi0rhm3oCd0Q=; b=oHZbSUs7UsDEEcTj3sCLmKfismPnZdPbrCVhcJGkKq1fUaR0QpjxsZiNZ9sFpbDb7R QlKn2UmmrjIRYCltH2HB/1cpc2VzMZbafQ34EAFmzakWSTgslwxTphkYhmxMQL8qvq5C fDc1L50KXkGBglJ7wkC85Fip5ZuCOueCxdXfEmtpTSgaGFvWTzgoJSDJxCjcz/cDpFTC W7fe1M1cOBj48vBcuqs1ERZzuG5PflRLoSm2tgJiHnPkq8dVVHJkuL7QTlzrnoXud5Fr bhI8iuswwqlMBnrOnmYQtXEage6XzS17lSdtn7KFEZ82YTCoq8xuruwzjYISVJLP6M4V W+aQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=xAz5Rrk4KFsiIv8CSyiiU7MH8ek3WZ1fi0rhm3oCd0Q=; b=cMEOsfj0dO0M/1F7USdrCzsvARmPjYOrYf+B570S4KXBphqCBUqiudiLDwW4Kd8k+S 9QAEL75EJroWgRNAgY2QsbD++1YnYSyslf5HOiUv6yWrtQV4gmYceLy1YeldBETfcpJl 2XPZgbJR7+U3WrReOckdFzMamQe7lHOP65NujYYJwfpuJ43hcq7Q1H6QLWSz9jTkkqZS LLMreQDL+5LbJH50NHMWdnww0WoD+WGz9fnD7FlmaSXiAc6bb+yqqdmA53nji9FU9IQ+ 8PgFmT73iznydv8aEZ1jZdmlxxgP4/C/+mevNRSBPI7M8qiestI19auup52ewkuz/I9a 9ykA== X-Gm-Message-State: APjAAAV0oEhpEheRV388Srr18YgB1FI6GWzXKUZnrLNOQlpKo3a2DRor OP3WY9Vrm/XLlL8CJZUHMDjVHSxZKRibA8uaj48= X-Google-Smtp-Source: APXvYqzgHByUxsjkB8FDr/iCmZyrKgS291uXQiDyc3XLA9lU7DOGmh4fm8I2PeDo9yvKZpWQJCvdh3MvmT/fSn37aRQ= X-Received: by 2002:aca:550c:: with SMTP id j12mr6717969oib.52.1553375087853; Sat, 23 Mar 2019 14:04:47 -0700 (PDT) MIME-Version: 1.0 References: <2c8ad5fe4be5c52ad1a3c2bf7f91a09a@mail.gmail.com> <00674bef-877b-3ccc-9c8e-e7e06ee8e1cd@kit.edu> <00a6bc91-22f2-8971-cec9-8aed615d632b@kit.edu> In-Reply-To: From: Luca Muscariello Date: Sat, 23 Mar 2019 22:04:35 +0100 Message-ID: To: Mikael Abrahamsson Cc: Michael Welzl , Victor Hou , bloat Content-Type: multipart/alternative; boundary="0000000000005086270584c95215" Subject: Re: [Bloat] [Ecn-sane] [iccrg] Fwd: [tcpPrague] Implementation and experimentation of TCP Prague/L4S hackaton at IETF104 X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 23 Mar 2019 21:04:48 -0000 --0000000000005086270584c95215 Content-Type: text/plain; charset="UTF-8" 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 key. 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 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@swm.pp.se > --0000000000005086270584c95215 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
For enterprise networks interconnection to the cloud (publ= ic 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.=C2=A0
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 runni= ng in the cloud.

Even in case a branch office is c= onnected using SD-WAN, DSCP is tunnelled by it, and transparently for the a= pplication.

If working from home, the quality of p= eering of an SP to cloud providers is key.=C2=A0
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 <swmi= ke@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=C2=A0 =C2=A0 email: swmike@swm.pp.se
--0000000000005086270584c95215--