Re: [tcpm] [Ecn-sane] [tsvwg] ECN CE that was ECT(0) incorrectly classified as L4S

Dave Taht <dave.taht@gmail.com> Fri, 02 August 2019 12:05 UTC

Return-Path: <dave.taht@gmail.com>
X-Original-To: tcpm@ietfa.amsl.com
Delivered-To: tcpm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 6C3F5120033; Fri, 2 Aug 2019 05:05:20 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id V3Qx1XViRT0y; Fri, 2 Aug 2019 05:05:18 -0700 (PDT)
Received: from mail-io1-xd2f.google.com (mail-io1-xd2f.google.com [IPv6:2607:f8b0:4864:20::d2f]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E59BB120098; Fri, 2 Aug 2019 05:05:17 -0700 (PDT)
Received: by mail-io1-xd2f.google.com with SMTP id z3so10456131iog.0; Fri, 02 Aug 2019 05:05:17 -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:content-transfer-encoding; bh=uSL4TGlvuu4pKXyLhZOhuwiD3IgXXnsXPdrn5o2a5N8=; b=kOYGilnjtR5yWw+zdIctZoG0wdotYtW200UaZglETVVoyDBfPwC5lr2zcpDFMRoORM t4mJmWrP5U46YAlqC7auym6qrDGCwfTsCdKTKBggRbVMcCCqr1ObDeJMDWVQZJscMyHu 8KlPJcl847yN7BAufL5zBLwv0Y4Yr/GeOnJOV81V7C9ckHTwyB2E2fbnBCM4JojRpURe hZA7kTHYIc6gzSEPXTpeeP6sR8jv1oF89LlRPmaZ2bwGaHx4dNngokUB8lP9GKD1lBVL zvuj503ard8J1ZSRE/R+ilhJUn9xAkMVAOQBuIQUNh270apaFd+Lsx7oRgMtruktsvzF uhsQ==
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:content-transfer-encoding; bh=uSL4TGlvuu4pKXyLhZOhuwiD3IgXXnsXPdrn5o2a5N8=; b=tpfVmFkhT2sTsu8BjG2MDPh+vi36Bjj2nZ4cOeBkHoELCDlC9jbasCgsb3FlYkZ3U2 e7VDHuEmYzLS80glvTX7p2QLmbtxDzg4FOXSWelF7Lz5j+RtZJdc4tF7JcOxonQcbEPq gbC0C9MdjuZ8uTG8AWxGHAATNNsENaiMCozWv12ssIkc6UZp4SA/sSk4d0mT5Ptv6sKj h5qrOUqDdt7gJCpn18tluy9hzqYov38JnKZrp3OvcD3UB/NuXjFOamceDusbUs5atvC5 7ixR831rkUv8/Ohx38nLowdoRK41ys8DE8ukB0I3NEaMvOUxbRfgoRDztJT28SCii/qU J5qQ==
X-Gm-Message-State: APjAAAUs6pMpbXKNujjIOeJ6Xd8MVO9As8rs5otMI+671v86nIeIjeLE rLM1gyAvcRLkifTT4elcEBNwl+8lHOyKFUVgmqs=
X-Google-Smtp-Source: APXvYqy9TMUMgMZE7E1PHijIhKB201vaKmndpJX0y4Ca/agrKHG6jmXYQNdA7HEgEAIaVJsNFB2JqVQKZN/yRHNccYE=
X-Received: by 2002:a6b:790a:: with SMTP id i10mr24038762iop.150.1564747516991; Fri, 02 Aug 2019 05:05:16 -0700 (PDT)
MIME-Version: 1.0
References: <24f7b15a-129f-ca44-60e0-32c7d23eadf4@bobbriscoe.net> <E54BA49C-0790-48B4-82BB-4C0F3FE3FB20@gmail.com> <FRXPR01MB0710085AE4AEFA896819AFA69CD90@FRXPR01MB0710.DEUPRD01.PROD.OUTLOOK.DE> <0FD0931A-3035-4F65-BC91-E0267DF6537B@gmail.com> <CAA93jw6SZ1US8=_7D2NYozWUWsni5EJR+Z-TK=OLYgfgbFPX8w@mail.gmail.com>
In-Reply-To: <CAA93jw6SZ1US8=_7D2NYozWUWsni5EJR+Z-TK=OLYgfgbFPX8w@mail.gmail.com>
From: Dave Taht <dave.taht@gmail.com>
Date: Fri, 2 Aug 2019 05:05:04 -0700
Message-ID: <CAA93jw5L6EuErD46yGMZhnp+gho8e=Y_Ep7TyLwstUcBZ2VVRQ@mail.gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: Ruediger.Geib@telekom.de, tcpm IETF list <tcpm@ietf.org>, ECN-Sane <ecn-sane@lists.bufferbloat.net>, tsvwg IETF list <tsvwg@ietf.org>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://mailarchive.ietf.org/arch/msg/tcpm/pE56mmwDU7M22Po7gc1b1-Nso8Y>
Subject: Re: [tcpm] [Ecn-sane] [tsvwg] ECN CE that was ECT(0) incorrectly classified as L4S
X-BeenThere: tcpm@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: TCP Maintenance and Minor Extensions Working Group <tcpm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpm>, <mailto:tcpm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpm/>
List-Post: <mailto:tcpm@ietf.org>
List-Help: <mailto:tcpm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpm>, <mailto:tcpm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 02 Aug 2019 12:05:20 -0000

On Fri, Aug 2, 2019 at 4:10 AM Dave Taht <dave.taht@gmail.com>; wrote:
>
> On Fri, Aug 2, 2019 at 2:47 AM Jonathan Morton <chromatix99@gmail.com>; wrote:
> >
> > > On 2 Aug, 2019, at 9:29 am, <Ruediger.Geib@telekom.de>; <Ruediger.Geib@telekom.de>; wrote:
> > >
> > > Hi Jonathan,
> > >
> > > could you provide a real world example of links which are consecutively narrower than sender access links?
> > >
> > > I could figure out a small campus network which has a bottleneck at the Internet access and a second one connecting the terminal equipment. But in a small campus network, the individual terminal could very well have a higher LAN access bandwidth, than the campus - Internet connection (and then there's only one bottleneck again).
> > >
> > > There may be a tradeoff between simplicity and general applicability. Awareness of that tradeoff is important. To me, simplicity is the design aim.
> >
> > A progressive narrowing of effective link capacity is very common in consumer Internet access.  Theoretically you can set up a chain of almost unlimited length of consecutively narrowing bottlenecks, such that a line-rate burst injected at the wide end will experience queuing at every intermediate node.  In practice you can expect typically three or more potentially narrowing points:
>
> 0: Container and vm users are frequently using htb + something to keep
> their bandwidths under control.
>
> 0.5: Cloudy providers use "something" to also rate limit traffic.
> Policers and shapers, I assume.

Stuff in the cloud thus far is looking quite jittery; sub-ms marking
thresholds do not look feasible. I have no idea what sorts of
software jitter and burstyness exist in NFV and ddpk based implementatons.

>
> > 1: Core to Access network peering.  Most responsible ISPs regularly upgrade these links to minimise congestion, subject to cost effectiveness.  Some consumer ISPs however are less responsible, and permit regular congestion here, often on a daily and/or weekly cycle according to demand.  Even the responsible ones may experience short-term congestion here due to exceptional events.  Even if the originating server's NIC is slower than the peering link, queuing may occur here if the link is congested overall due to statistical multiplexing.
> >
> > 2: Access to Backhaul provisioning shaper.  Many ISPs have a provisioning shaper to handle "poverty tariffs" with deliberately limited capacity.  It may also be used to impose a sanity check on inbound traffic bursts, to limit backhaul network traffic to that actually deliverable to the customer (especially when the backhaul network is itself subcontracted on a gigabytes-carried basis, as is common in the UK).  In the ADSL context it's often called a BRAS.
> >
> > 3: Backhaul to head-end device.  Generally the backhaul network is sized to support many head-end devices, each of which serves some number of consumer last-mile links.  I'm being deliberately generic here; it could be a CMTS on a cable network, a DSLAM in a phone exchange, a cell tower, or a long-range wifi hub.  In many cases the head-end device shares several subscribers' lines over a common last-mile medium, so there is still some statistical multiplexing.  In the particular case of a cell tower, the subscriber usually gets less link capacity (due to propagation conditions) than his tariff limit.

There are also bursts here from the vpn crypto engine.

> > 4: CPE bufferbloat mitigation shaper.  This is *post-last-mile* ingress shaping, with AQM and FQ, to reduce the effects of the still-ubiquitous dumb FIFOs on the above bottlenecks, especially the head-end device.  The IQrouter is a ready-made CPE device which does this.

I would say "inbound shaper" to be clear. And its far, far wider than
just that commercial product, Nearly everyone using this stuff
shapes both in and outbound - be it untangle, netduma, asus "adaptive
qos", edgerouter's or eero's sqm implemention, all of openwrt, dd-wrt,
and deratives, bsd-based pfsense and opfsense, preseem does a bump in
the wire for WISPs, streamboost, I think the list of off the shelf
home router qos systems that shape inbound is well above 80-90%, and
users have been trained to turn it on in both directions
and off only when they run out of cpu. We see new product sales driven
by the cpu cost of having to shape inbound, too.

Policers have become quite useless in the past decade.

> >
> > 5: LAN, wifi, or powerline link.  Most people now have GigE, but 100base-TX is still in use in cheaper CPE and some low-end

I'd so love to see powerline gain fq and AQM. I see it used a lot in
busy apt buildings to drag stuff from room to room. It can be *awful*

>computers, and this will be a further bottleneck in cases where the last mile is faster.  For example, the Raspberry Pi has only just upgraded to GigE in its latest versions, and used 100base-TX before.  Wifi is also a likely bottleneck, especially if the mobile station is on the opposite side of the house from the base CPE, and is additionally a "bursty MAC" with heavy aggregation.  Some CPE now runs airtime-fairness and FQ-AQM on wifi to help manage that.

"some" includes most of qca's ath9k or ath10k products. (40% of the AP
market?) Prominently known fq-codel for wifi users are ~3m chromebook
users and ~3m google wifi, (
http://flent-newark.bufferbloat.net/~d/Airtime%20based%20queue%20limit%20for%20FQ_CoDel%20in%20wireless%20interface.pdf
) and nearly everyone else in the 802.11s meshy market... meraki is a
known sfq + codel user... starting in 2014...

A large number of wifi APs and p2p links oft have a faster wifi speed
than their 100base-tx link, and thus use the ethernet (with either a
short fifo or fq_codel) to smooth the bursts out. I can point to a few
ubnt products that I know a bit too much about. There's also some
802.11ad and ay.... there is a quite remarkable amount of 100base-tx
gear still being deployed.

If it helps any to those here doing simulation, long ago I put a
"slot" and statistical distribution of busty mac delay feature into
netem. I can say now that that was used to help guide the development
of google "stadia", and certainly "slotting" is a MAJOR tool that I'd
plug into the SCE work to better emulate the real orld behaviors of
bursty macs. google has collected WAY more examples characterizing
real world micro(bursts) than I could ever deal with, and I hope they
publish that data someday for others to use.

> >
> > I think the above collection is not at all exotic.  Not all of these will apply in every case, or at all times in any given case, but it is certainly possible for all five to apply consecutively.

For bursty.

> >  - Jonathan Morton
> > _______________________________________________
> > Ecn-sane mailing list
> > Ecn-sane@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/ecn-sane
>
>
>
> --
>
> Dave Täht
> CTO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-831-205-9740



-- 

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