
From nobody Tue Apr  5 15:39:14 2016
Return-Path: <ietf@bobbriscoe.net>
X-Original-To: tsv-area@ietfa.amsl.com
Delivered-To: tsv-area@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 4EE1E12D0A2 for <tsv-area@ietfa.amsl.com>; Tue,  5 Apr 2016 15:39:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.901
X-Spam-Level: 
X-Spam-Status: No, score=-1.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
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 C6X3Y0OnvN_3 for <tsv-area@ietfa.amsl.com>; Tue,  5 Apr 2016 15:39:10 -0700 (PDT)
Received: from server.dnsblock1.com (server.dnsblock1.com [85.13.236.178]) (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 BE00D12D09D for <tsv-area@ietf.org>; Tue,  5 Apr 2016 15:39:10 -0700 (PDT)
Received: from dhcp-b315.meeting.ietf.org ([31.133.179.21]:49984) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.86_1) (envelope-from <ietf@bobbriscoe.net>) id 1anZcq-0007S8-KV; Tue, 05 Apr 2016 23:39:08 +0100
To: Martin Stiemerling <mls.ietf@gmail.com>, Spencer DAWKINS <spencerdawkins.ietf@gmail.com>, Mirja Kuehlewind <ietf@kuehlewind.net>, tsv-area IETF list <tsv-area@ietf.org>
From: Bob Briscoe <ietf@bobbriscoe.net>
Subject: current and future hot topics in TSV
Message-ID: <57043E89.2000508@bobbriscoe.net>
Date: Tue, 5 Apr 2016 23:39:05 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8; format=flowed
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - server.dnsblock1.com
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: server.dnsblock1.com: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: server.dnsblock1.com: in@bobbriscoe.net
Archived-At: <http://mailarchive.ietf.org/arch/msg/tsv-area/94GDeofMOdi4mMR4fWnW54WAdC8>
X-BeenThere: tsv-area@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: IETF Transport and Services Area Mailing List <tsv-area.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tsv-area/>
List-Post: <mailto:tsv-area@ietf.org>
List-Help: <mailto:tsv-area-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tsv-area>, <mailto:tsv-area-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Apr 2016 22:39:13 -0000

TSV ADs, TSV-Area follks,

Apologies, I missed tsvarea this afternoon (preparing slides, and I 
missed my alarm).
I understand the session on current and future hot topics in TSV was 
rather short.
Maybe the two sentences above are related ;)

1. I think the DualQ Coupled AQM is an important development, not just 
cos we've got cool low queuing delay for all traffic out of it, but...

...because it is an "incrementally deployable clean slate" that is 
interesting enough to network operators that it could get deployed.

What I mean is, it's a incrementally deployable queue isolated from 
existing traffic in which we could develop new congestion control 
together with new network behaviour.
Obviously, new host & network capabilities have to be deployable 
independent of the other, but there is a window of deployment 
opportunity for new ideas....

For instance, if a new slow-start needs a new signal from the 
bottleneck, that could be included in the initial spec for the L4S 
queue, so there would be no need to cater for L4S queues without that 
signal. Of course, you would have to cater for non-L4S bottlenecks 
still, but if you were getting signs you were in an L4S bottleneck, this 
could be powerful.

2. The L4S activity itself would involve new TSV standardisation 
activity across 3 WGs (not to mention new implementation activity).
We're planning on outlining this in the L4S Bar Bof on Thu 9am 
(advertised earlier today on this ML).

Slide 4 of our slides about L4S (tomorrow in tsvwg) shows the three 
areas needing standardisation (AQM, TSVWG & TCPM)
http://bobbriscoe.net/presents/1604ietf/1604briscoe-tsvwg-ecn-l4s-id.pdf

There's also potential for loads of new activity evolving scalable TCP 
(TCP Prague/DCTCP).
I prepared the following table for the TCPM chairs listing all this:
http://bobbriscoe.net/presents/1604ietf/tcp-prague-todo.pdf


Cheers



Bob

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

