Re: [tsvwg] L4S related activity in 3GPP

Sebastian Moeller <> Sun, 10 November 2019 10:51 UTC

Return-Path: <>
Received: from localhost (localhost []) by (Postfix) with ESMTP id DECBD1200FA; Sun, 10 Nov 2019 02:51:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -1.648
X-Spam-Status: No, score=-1.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=no autolearn_force=no
Authentication-Results: (amavisd-new); dkim=pass (1024-bit key)
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id jFzr15uB0Fkq; Sun, 10 Nov 2019 02:51:19 -0800 (PST)
Received: from ( []) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by (Postfix) with ESMTPS id 3A5A01200E6; Sun, 10 Nov 2019 02:51:19 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple;; s=badeba3b8450; t=1573383030; bh=Gq4jc+TWm13sxAYCL8RBauEz+gpOlriIZZd6nKs5bok=; h=X-UI-Sender-Class:Subject:From:In-Reply-To:Date:Cc:References:To; b=BxjxlvWm7DcMoBHdttYHsUkVjYWDfuq8q4hy43anCQJBAPFFfK/N/LFGIguIH+rZm z8MDgGYfKqNf5AXdHkg1Cc72N05I2tlLYJ2BFR8TWMyzbBWVhOYZHNwzsYk3/ij7Sa F40CzJUb/9FltgCdFoR2YtGOS/sNtgentd5AL3yA=
X-UI-Sender-Class: 01bb95c1-4bf8-414a-932a-4f6e2808ef9c
Received: from hms-beagle2.lan ([]) by (mrgmx005 []) with ESMTPSA (Nemesis) id 1N8XPn-1hpenE3lsv-014SBq; Sun, 10 Nov 2019 11:50:30 +0100
Content-Type: text/plain; charset=utf-8
Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\))
From: Sebastian Moeller <>
In-Reply-To: <>
Date: Sun, 10 Nov 2019 11:50:27 +0100
Cc: Ingemar Johansson S <>, "" <>, "" <>, "" <>, "" <>, "Bob Briscoe (" <>
Content-Transfer-Encoding: quoted-printable
Message-Id: <>
References: <> <> <> <> <>
To: Ingemar Johansson S <>
X-Mailer: Apple Mail (2.3445.104.11)
X-Provags-ID: V03:K1:rURuN/YPktGyBpt/9o+JHftR05B+ZCYItu0OsGXIPGb98cdMsKm 6hq6zcNu1e/l1v2+XGfNDSJuh6PJFy3tIXLNQmwLyPtbHjMkqsS3anRjH6y+SrNYrmZdMdf Wbs5La23TLsR7VtQzKUrGyQc1/Qzrt95FmQsSLxtuUjbW7Frk5SfOKt4QE6lKg1paEsouea ZTCOTc53ZraAtpstW7J3g==
X-UI-Out-Filterresults: notjunk:1;V03:K0:qJFJDfFunLY=:7RhnYDVj3eRtyclsk4iPF+ WnrZYgfjSbALO58ak8IpcK8hloaFp876tYmbDt3FUj9ZHNywf7xIGw/A6srO2JM+4o6iIND+u W6kEYV7KxXL0ElQO/d+xtACfjX+Efiyv9QVMnZKOCcNZ+gAn1bbytT+PjzoAqBFgf+FLRVzxi kiAavZ8pigltiCi/6p5DBoRxqy4AhUBBbtBW+Aqa8CcigFx8WL/fpWG9LNxEfol79bLWPbKXO u4H65LxqD235G9by3sBUIBQv1WZeKxIL9Otsydvi+oTBT6wbk10PMwrgCjd8bSpUCNUla3XoL 6mTbtb1Fsy+Lwkle/TvorLMt2M4QU1LoFaLxntW3r+pvow6c4yIRJGWIUIhQrzcE/+ydo/jXA giDMof+S754DeTav66rLAT0FErR366aTj0md02e46TW68S4qJoyOQJhXoV8TMxgzReq6Tfe3U +pmhJOinbVSfg0/8vyiUr0GwProDZ1Ovmb8+YQ90k8VnDwFWo8d4hn2K/nlHGIsNtHMlr2o4P oHi9DPWCvRL1inQz9xzHJ4A+gEt5fuTTJQrBP1YLo5BbFUhgl2ga/hwp64xUzYMowV6WBP8at 7bzUKiZURatlQ6jNpjlDVYaQKHYD4YI1hxsLjukg43KFul2Dr6SOOyrLOKmv08mfRGdHA4sBD aGrgFTo+9Xxic5SDf+IfSmNU4/sz79lhEX8Eb/RTC22BBHKyBI5LJ1sGmM1xKkEXkIIUXwQ8t 4gZTAf9PT3EbJD1b82WcWBoZl3Ovp6TSjD9KymgFxChRzjn+BhTVAeSUqG5X1ZFEh+NBEINZk s6Sbq7VXCSfVQ3yP2Ub3iEgGfeap0JWontxxUsooqd2FJc4xwUz7PmAgfITOBvbf5OuHc725q rCXX0w1gio/zU7JfPJKtiBv5Tl3OclmdEQDoAx2UTtbqv2UUhFW2/NoKrza93QEHikPjcxrAo siIBwX83OBPDH4c88wgqidpPqBRSd7VdqjvcgIcm52S4jXzL8iXjZL7rMvtLsmYsa83AopTzW 6tHMTlANU+zSBewTws+6z3YvLHkVlFUsIZB+IGRx90bVKAopQjgddTPEF1+gSQa1N8SeArca7 DQMx2+WiMMzttzsFCKHOwp62pTN7vn9uIUuOb3DnaeY5Iz7ctPr31KjFmaKvAwP13LuIVqVP/ O3wt2+rkJYWfIcS3hjkIwsrGiOix2BBKGyGodkhaCViN1Aj8Z85jt0YzSsp/+Kqn/To3Ot/M8 s8BD/ebr0aYaJfhZo3hdtGed2NrRReJg9c3YEZg8kaiSsIcHgPpVwSS3n4dzE+Tv7nFDQMS8c B0b5Kt1fptrOEtpgPBfaIfIFauYm8DVA3OIeKfMyQ1hOjzaRQPJWhetTKjFdlWNxkIftoloof 1yIKRQfQ8I3zpDL0swhX3VPr9WxcmS7gaKYeWp+NcYHYI71xdAbowlwIm4ErEy76RgnUYczma oKUfNle9avLC+1+SkJyOICShtYRjkg48bZF+QfBJF8t7h+2k0owXn+lf4/XBiKyQ6rBSd384U dSQ==
Archived-At: <>
Subject: Re: [tsvwg] L4S related activity in 3GPP
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Sun, 10 Nov 2019 10:51:22 -0000

Hi Ingemar,

> On Nov 10, 2019, at 11:20, Ingemar Johansson S <> wrote:
> Hi Sebastian
> Please see inline
> /Ingemar
>> -----Original Message-----
>> From: Sebastian Moeller <>
>> Sent: den 9 november 2019 21:38
>> To: Ingemar Johansson S <>
>> Cc: Ingemar Johansson S
>> <>rg>;;
>>;;; Bob Briscoe
>> ( <>
>> Subject: Re: [tsvwg] L4S related activity in 3GPP
>> Dear Ingemar,
>> more in-line below.
>>> On Nov 9, 2019, at 20:24, Ingemar Johansson S
>> <> wrote:
>>> Hi Sebastian
>>> Please see inline below
>>> /Ingemar
>>>> -----Original Message-----
>>>> From: Sebastian Moeller <>
>>>> Sent: den 9 november 2019 18:13
>>>> To: Ingemar Johansson S
>>>> <>
>>>> Cc:;;; Ingemar Johansson
>>>> S <>om>;
>>>> Subject: Re: [tsvwg] L4S related activity in 3GPP
>>>> Dear Ingemar,
>>>> thanks for posting this. I read "This document describes an Active
>>>> Queue Management mechanism, ‘L4S’, that can support low-latency
>>>> services in a way that does not degrade the performance of other
>>>> traffic." and I wonder whether 3GPP has run any experiments to
>>>> confirm/support this claim, that you are willing to share?
>>> [IJ] We have done simulation studies with our proprietary 4G/5G system
>> simulation tools but I can not disclose the results from these.
>> 	[SM] Ah, I see, not posting internal data is fine, but by all means, go and
>> perform real-world measurements as well with all the parts you actually want to
>> roll-out (in other words testing with dctcp for example is scientifically
>> interesting, unless you expect your users to actually use dctcp on your links).
> [IJ] I hope to have data to show later on

	[SM] Excellent, looking forward to that.

>>>> Sidenote: in the powerpoint file it says about L4s " Standardized in
>>>> IETF [1]", which seems premature, in the process of being
>>>> standardized seems a better description of the status quo...
>>> [IJ] Yes, you are right about this, it should have been "Subject to
>> standardization..."
>> 	[SM] Fair enough, as much as I regret to say it, standardization is quite
>> likely.
>>>> I ask about test data from your side as the recent test data is quite
>>>> sobering from a number of angles, including quality of isolation:
>>> [IJ] First of all the outline of the proposal for L4S in 5G is to use separate radio
>> bearers for L4S and classic (or normal or non-L4S) traffic. This means that it is
>> the 5G QoS framework and the scheduling in the RAN (Radio Access Network)
>> that dictates the fairness.
>> 	[SM] Sounds like a workable approach, that side steps the dualQ
>> implementation/theory issues.
> [IJ] The proposed approach for 5G is for practical reasons, we believe that it is more implementation and standardization friendly as it will utilize the existing QoS framework as much as possible. 

	[SM] Well, what ever the rationale, by avoiding the insufficiently isolating DualQ AQM you will save yourself from a number of headaches; I simply assume that you implement stricter airtime sharing between the two bearers than dualQ, and if you err you err on the side of conserving normal traffic (unlike DualQ's "L4S first" approach). But you still are saddled with L4S poor choice of ECT(1) as heuristic to separate L4S from non-L4S traffic. Calling that aETC(1) classifier seems plain wrong, as classifier implies strict separation.

Best Regards

>>> But of course there are wireline transport link in the core network that may be
>> using DualQ when that becomes commercially available. The bitrates over these
>> links are however likely to be considerably higher than 50Mbps.
>> 	That does not matter, the issue is not the limit of 50 Mbps, but the fact
>> that dualQ, at last the current implementation in conjunction with the current
>> TCP prague implementation, simply do not reliably and robustly do what the rfc
>> draft claims. My fear is that dualQ, with its weak coupling vie marking
>> probabilities, simply is a design, that only guarantees approximate fairness. In
>> other words I doubt that dualQ works as a naive reading of the RFC implies. But
>> if I  understood Bob correct, the only gurantee he is willing to give is L4S does
>> not starve non-L4S traffic. Which IMHO is not sufficient to merit inflicting the
>> L4S experiment on the wider internet. Now, that is not my call to make, but the
>> IETF process allows me t voice my concerns, and I just use this opportunity in an
>> attempt to minimize undesired side-effects on the "normal" internet.
>>>> 	Looking at the current L4S tests from the various testbeds I see
>>>> severe breakdown of the promised isolation between bulk and the
>>>> "low-latency" queue, apparently making the current implementation, if
>>>> not the concept itself IMHO unfit for release into the wider
>>>> internet, before these issues have been sufficiently addressed.
>>>> Especially the observation that the weighted scheduler built in as a
>>>> safety mechanism in the dualQ aqm seems to trigger considerably more
>>>> often than expected/predicted from reading the dualQ draft (giving
>>>> 1/16 of the bandwidth to on of two classes _might_ be justified as a
>>>> temporary stop- gap measure in extremely unlikely cases, but this
>>>> already triggers in a simple one-flow-per queue scenario at low RTTs). In
>> short it currently looks like the "does not degrade performance of other traffic"
>> part is not yet finished.
>>>> 	To illustrate my criticism, here is a link to a test comparing the
>>>> simplest functionality test imaginable, running one L4S-style and one
>>>> non-L4S-style TCP connection through the L4S dual queue AQM at a
>>>> intranet like RTT (nomnally 0ms, but in reality):
>>>> 0cc47ad93e1c-6acfac650abe7f09&q=1&e=6cd6c372-b712-46be-8b10-
>>>> 22955dec7b38&
>>>> testing%2Fkey_plots%2Fbatch-l4s-s1-2-cubic-vs-prague-50Mbit-0ms_var.p
>>>> ng As can be seen the L4S flow (labeled prague) ends up very quickly
>>>> taking ~90% of the available bandwidth, leaving only 10% to the
>>>> non-L4S flow (labeled cubic), wit increasing RTT this bias gets less
>>>> extreme, but even at 80ms the prague flow still gets around 1.5 times
>>>> the bandwidth of the cubic flow
>>>> (
>>>> 0cc47ad93e1c-56d0590db27309ef&q=1&e=6cd6c372-b712-46be-8b10-
>>>> 22955dec7b38&
>>>> testing%2Fkey_plots%2Fbatch-l4s-s1-2-cubic-vs-prague-50Mbit-80ms_var.
>>>> png), indicating an RTT dependent performance degradation for "other
>>>> traffic". Test from another testbed confirm the break-down of
>>>> fairness between L4S and non- L4S traffic at short RTTs
>>>> (
>>>> 0b995f26-5710b074-0cc47ad93e1c-418920d155a62bf0&q=1&e=6cd6c372-
>>>> b712-46be-8b10-
>>>> 22955dec7b38&
>> l4s-
>>>> bakeoff%2Fbakeoff-2019-09-13T045427-r1%2Fl4s-s1-2%2Fbatch-l4s-s1-2-
>>>> cubic-vs-prague-50Mbit-0ms_fixed.png).
>>> [IJ] I understand that the 0 RTT results can be because the congestion window
>> is only a few segments large (my guess is ~3 to 4 segments ?). I know that this is
>> a problem with e.g. DCTCP.  The question is whether this is a permanent
>> problem or something that will be solved over time?.
>> 	[SM] With DualQ, I assume it is a structural problem, instead of
>> designing this as a robust system with two fair sharing queues it does its clever
>> "indirect coupling" via marking/dropping probabilities. Have a look at
>> 869a17b5b21b-e4edb2934547a534&q=1&e=314d9ef9-5cc0-4c98-a599-
>> 59f030e6cb2f&
>> bakeoff%2Fbakeoff-2019-09-13T045427-r1%2Fl4s-s2-2%2Fbatch-l4s-s2-2-
>> cubic-vs-prague-50Mbit-10ms_fixed.png for how sharing in a FQ system looks.
>> Even with the leaky ECT(1) as classifier abuse it shoukd be simple to fair queue
>> between EXT(1) and not ECH(1) flows and have robust separation. This is not
>> rocket science, and mostly, as far as I can tell a solved problem.
>>> What is more interesting to me and what makes L4S attractive for the use
>> cases outlined in the 3GPP contributions, is the very low queue delay with L4S.
>> 	[SM] Well, I believe low queueing delay can be achieved without dualQ
>> and without abusing the ECT(1) codepoint as a classifier (the desired classifier
>> requires one complete independent bit, ECT(1) is just 1/2 of a bit, and hence has
>> failure modes in separating L4S-style flows and non-L4S flows). The idea of using
>> the finer-grained congestion signaling of DCTCP over the wider internet seems
>> sane see the SCE draft proposal as an alternative that would/will allow dctcp-
>> style ECN signaling over the internet in a truly backward compatible fashion...
>>> There are other promising features with L4S. One being that it can enable
>> congestion control algorithms to quickly grab free capacity.
>> 	[SM] When you say L4S, do you mean the congestion signaling? Then
>> should have you covered,
>> without the nasty side-effects of the current L4S proposal. Or do you mean the
>> actual congestion controller as implemented in TCP prague?
>>> 5G access can have large variations in link throughput for example related to
>> dual connectivity and L4S can be helpful here as well.
>> 	[SM] Dealing better with variable rate links is certainly desirable, but I
>> am not sure that DualQ/TCP Prague really are the best or only tools for that
>> purpose. At least not until all of the kinks are ironed out. Again, none of this is
>> my call to make, so all I am voicing is my educated subjective assessments.
>> Best Regards
>> 	Sebastian
>>>> 	Personally, I can not help thinking that it might be better to first
>>>> make sure there is a complete, real-world tested implementation that
>>>> reliably demonstrates that dualQ delivers the required isolation
>>>> between the two traffic classes and that the L4S approach actually
>>>> delivers the reported reliable low latency performance under adverse
>>>> real-world conditions while not degrading the performance of other traffic,
>> before trying to codify L4S into RFCs.
>>>> Best Regards
>>>> 	Sebastian
>>>>> On Nov 9, 2019, at 17:00, Ingemar Johansson S
>>>> <> wrote:
>>>>> Gentlepeople!
>>>>> This 3GPP SA2 contribution is recently submitted
>>>>> 47
>>>>> ad93e1c-77a60175f8460bc6&q=1&e=6cd6c372-b712-46be-8b10-
>>>> 22955dec7b38&u=
>>>> _Reno%
>>>>> Title “5QI values for efficient handling of
>>>>> congestion control marked IP packets”
>>>>> The contribution introduces L4S to the SA2 audience and explains
>>>>> where the
>>>> technology is useful. The contribution also proposes a method to bake
>>>> L4S into the 5G QoS framework.
>>>>> If agenda time permits, it will be discussed at the SA WG2 meeting
>>>>> in Reno on
>>>> Nov 18-22, hopefully with good results.
>>>>> Also a RAN2 contribution was submitted and discussed at an earlier
>>>>> RAN2
>>>> meeting.
>>>>> 47
>>>>> ad93e1c-f387514c9f633599&q=1&e=6cd6c372-b712-46be-8b10-
>>>> 22955dec7b38&u=
>>>> 07bis%2F
>>>>> Enjoy
>>>>> /Ingemar
>>>>> ================================
>>>>> Ingemar Johansson  M.Sc.
>>>>> Master Researcher
>>>>> Ericsson Research
>>>>> Network Protocols & E2E Performance
>>>>> Labratoriegränd 11
>>>>> 971 28, Luleå, Sweden
>>>>> Phone +46-1071 43042
>>>>> SMS/MMS +46-73 078 3289
>>>>>     The best way to find out if you  can trust somebody is to trust
>>>>> them
>>>>>             Ernest Hemingway
>>>>> =================================