Re: [tsvwg] Gorry Fairhurst Individual thoughts on choosing whether/how to advance ECN work.

Bob Briscoe <ietf@bobbriscoe.net> Sat, 23 May 2020 23:53 UTC

Return-Path: <ietf@bobbriscoe.net>
X-Original-To: tsvwg@ietfa.amsl.com
Delivered-To: tsvwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 2F0163A0F72 for <tsvwg@ietfa.amsl.com>; Sat, 23 May 2020 16:53:58 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.098
X-Spam-Level:
X-Spam-Status: No, score=-2.098 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, SPF_HELO_FAIL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=bobbriscoe.net
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 zfu7bsCaSK5j for <tsvwg@ietfa.amsl.com>; Sat, 23 May 2020 16:53:55 -0700 (PDT)
Received: from cl3.bcs-hosting.net (cl3.bcs-hosting.net [3.11.37.202]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0722C3A0F71 for <tsvwg@ietf.org>; Sat, 23 May 2020 16:53:54 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Type:In-Reply-To:MIME-Version:Date: Message-ID:From:References:Cc:To:Subject:Sender:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Id: List-Help:List-Unsubscribe:List-Subscribe:List-Post:List-Owner:List-Archive; bh=hSywMn6Mc024oanTaaj13DjstrE7EMILclvZXgnO+c0=; b=jxxYO2zl2WHWwBCKLv17K3zJM kqXmRKo2kbaZd//EOLVJHitJGfrdrQ3T+J4Xsmu9zVg3nqWxlJXioKw5vinA4x0Cq4PX8UZ4ZeIBS SkkJQV3NjsIRx5Y63mHzRF43jvAoXuQ4tgGBtMh0xlI5FwyHBE46d/AdNHJYMT8ePzyDiT7HMWGNR UqLuajkE37R4tt9Yc1YkQoK3ouu14WgZBGiIPuk19hG3HMJ3hrIK5rxN4/ue4ocFBGvMo9ab4sXKA jaSUGA3PFps3LXtmFBktmQWxIOWx67bOaxsmV8KUTU2cCTyJpgtfuEnFJzqyZzTW4xGIYrhUk4oJa l9PbyNhOg==;
Received: from [31.185.135.128] (port=55008 helo=[192.168.0.6]) by cl3.bcs-hosting.net with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.93) (envelope-from <ietf@bobbriscoe.net>) id 1jcdxg-00EzZX-Mz; Sun, 24 May 2020 00:53:52 +0100
To: Sebastian Moeller <moeller0@gmx.de>
Cc: tsvwg@ietf.org
References: <dbc71da6-70f1-7369-1d2d-f08fb3b08b69@erg.abdn.ac.uk> <21483444.sDhFMENYeD@linux-9daj> <a85600da-e69f-9190-7ca1-d23a7e7246f9@bobbriscoe.net> <3267993.nvHYsSR2bi@linux-9daj> <dd8e3896-2951-537f-e3d1-9954c93348dd@bobbriscoe.net> <67CBAA42-BD37-4A19-B650-68F511FC244A@gmx.de>
From: Bob Briscoe <ietf@bobbriscoe.net>
Message-ID: <af3e6272-c04d-9e81-763c-e690ed521749@bobbriscoe.net>
Date: Sun, 24 May 2020 00:53:51 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1
MIME-Version: 1.0
In-Reply-To: <67CBAA42-BD37-4A19-B650-68F511FC244A@gmx.de>
Content-Type: multipart/alternative; boundary="------------255C07FBB775494BC6CDE5B6"
Content-Language: en-GB
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - cl3.bcs-hosting.net
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - bobbriscoe.net
X-Get-Message-Sender-Via: cl3.bcs-hosting.net: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: cl3.bcs-hosting.net: in@bobbriscoe.net
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/k-ryJ8ax-eaNSkdtja63yRxuvUU>
Subject: Re: [tsvwg] Gorry Fairhurst Individual thoughts on choosing whether/how to advance ECN work.
X-BeenThere: tsvwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Transport Area Working Group <tsvwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsvwg/>
List-Post: <mailto:tsvwg@ietf.org>
List-Help: <mailto:tsvwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsvwg>, <mailto:tsvwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Sat, 23 May 2020 23:53:59 -0000

Sebastian,

On 23/05/2020 16:33, Sebastian Moeller wrote:
> Bob,
>
>
>> On May 23, 2020, at 17:07, Bob Briscoe <ietf@bobbriscoe.net> wrote:
>> [...]
>>
>> Another explanation is that L4S enables new interactive applications that are currently infeasible over the WAN.
> 	[SM] I have asked this before, but I am happy if I get a response this time: Which novel applications are possible now that the queuing delay has been reduced from ~10ms (fq_codel/cake, measured under real life traffic conditions on life internet access links) to ~1ms (L4S. dual queue coupled AQM under laboratory conditions)? This is the state of the art you compare against, not multiple 100s milliseconds of latency-under-load.

As explained in the email you are responding to, tail latency is 
important for real-time. The 10ms you report for FQ_CoDel is roughly its 
90th percentile queue latency, which is an irrelevant metric for 
real-time (if the stream was being rendered after the 90%ile delay, 10% 
of the packets would arrive too late to be rendered).

In http://bobbriscoe.net/presents/2004ietf/202005L4S-brief.pdf (slide 4) 
I've used the 99.9th percentile delay for the rendering deadline, which 
reduces the fraction of packets that cannot be used to 0.1%.
In the experiment reported in slide 3 you'll see the P99.9 latencies are 
32ms for FQ_CoDel and 4.5ms for L4S. On slide 4 this is translated into 
reach in fibre, taking the generally accepted 50ms max delay for 
'responsive feel' and subtracting application and OS delays.


See the link I put in the email you are responding to for the list, 
repeated here:
     http://bobbriscoe.net/presents/2004ietf/202005L4S-brief.pdf
To be clear, I'm not advocating these. I'm merely justifying my 
assertion about applications that are not currently possible. 
Personally, I'm not excited by gadgetry and social distancing.

Of course, we can't predict what other new applications will be 
developed once this amount of tail latency is removed over the wide 
area. Also, please bear in mind that I cannot generally pass on 
information about product plans.


The original L4S teams from Alcatel-Lucent and Simula demonstrated a 
number of these applications at the Multimedia System 2016 conference: 
“Ultra-Low Delay for All: Live Experience, Live Analysis 
<https://riteproject.files.wordpress.com/2015/10/uld4all-demo_mmsys.pdf>“, 
Proc. ACM Multimedia Systems; Demo Session (May 2016).
Particularly cloud-rendered panoramic camera control and cloud-rendered 
VR goggles, were run at the conference over DCTCP and L4S with emulated 
wide-area round trip delay.

Over today's state of the art AQMs, the delay is too inconsistent to 
rely on doing any of the following real-time interactive applications 
over wide area distances, or rendered remotely (e.g. in the cloud), 
rather than just confined to a LAN or metropolitan area:
* cloud-rendered interactive control (like this: 
https://riteproject.eu/dctth/#1511dispatchwg )
* remote presence,
* interactive real-time remote control or supervisory monitoring of 
cameras, drones, machinery (oil rigs, power plants, machine shops, 
cranes, ), medical procedures, using (high res.) video to monitor what 
is being controlled.
* interactive light-field experiences


> 	Note, how for this question, I accept your claim of 1ms queueing delay even though testing indicates that this does not hold under all traffic patterns one is prone to encounter on a real internet access link (e.g. congestion on the reverse path). But really which application can not tolerate this additional 9ms of delay, yet is still a viable idea to deploy over the open internet? I note that real time control applications/reaction-time bound game services like google stadia and nvidia gforce now, are already deployed in today's internet, there really is nothing novel left as far as I can see

[BB] The novelty isn't the ability to demonstrate a "concept 
application" in a marketing video; it's large numbers of real people 
actually being able to use it over the wide area for extended periods, 
without getting stressed, sick, or exhausted. And with just their 
regular Internet, rather than having to set up special network 
arrangements, or a special reserved session.

In the case of industrial or professional applications, quite often it's 
the ability for expertise to be deployed to a far-flung or inaccessible 
site instantly that would be the novel aspect, without experts or 
supervisors having to already sit on-call close by the site.



Bob

> 	Thanks in advance for the list of relevant new use-cases.





>
> Best Regards
> 	Sebastian

-- 
________________________________________________________________
Bob Briscoe                               http://bobbriscoe.net/