[tcpPrague] New L4S problem statement: draft-briscoe-tsvwg-aqm-tcpm-rmcat-l4s-problem-00.txt

Bob Briscoe <ietf@bobbriscoe.net> Fri, 03 June 2016 16:19 UTC

Return-Path: <ietf@bobbriscoe.net>
X-Original-To: tcpprague@ietfa.amsl.com
Delivered-To: tcpprague@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id AE09912D590 for <tcpprague@ietfa.amsl.com>; Fri, 3 Jun 2016 09:19:32 -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=unavailable 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 qUHDrZgRz4Za for <tcpprague@ietfa.amsl.com>; Fri, 3 Jun 2016 09:19:31 -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 C389212B031 for <tcpPrague@ietf.org>; Fri, 3 Jun 2016 09:09:33 -0700 (PDT)
Received: from 148.58.125.91.dyn.plus.net ([91.125.58.148]:50827 helo=[192.168.0.10]) by server.dnsblock1.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.87) (envelope-from <ietf@bobbriscoe.net>) id 1b8rf9-00015s-AS; Fri, 03 Jun 2016 17:09:31 +0100
References: <20160603155257.1438.57036.idtracker@ietfa.amsl.com>
To: TCP Prague List <tcpPrague@ietf.org>
From: Bob Briscoe <ietf@bobbriscoe.net>
Message-ID: <5751ABBA.8030707@bobbriscoe.net>
Date: Fri, 03 Jun 2016 17:09:30 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.8.0
MIME-Version: 1.0
In-Reply-To: <20160603155257.1438.57036.idtracker@ietfa.amsl.com>
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/tcpprague/BZXs87T2aAJBvB4Sr1hhGJx1SxM>
Cc: marcelo bagnulo braun <marcelo@it.uc3m.es>, "De Schepper, Koen (Koen)" <koen.de_schepper@nokia.com>
Subject: [tcpPrague] New L4S problem statement: draft-briscoe-tsvwg-aqm-tcpm-rmcat-l4s-problem-00.txt
X-BeenThere: tcpprague@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "To coordinate implementation and standardisation of TCP Prague across platforms. TCP Prague will be an evolution of DCTCP designed to live alongside other TCP variants and derivatives." <tcpprague.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/tcpprague>, <mailto:tcpprague-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/tcpprague/>
List-Post: <mailto:tcpprague@ietf.org>
List-Help: <mailto:tcpprague-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/tcpprague>, <mailto:tcpprague-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 03 Jun 2016 16:19:32 -0000

Folks,

We've just posted a problem statement for the proposed L4S BoF (or 
mini-BoF, or whatever it will end up as).
We put every affected WG in the filename string of the draft!

It's nearly all there, except some parts are in bullet form, so we can 
improve it over the next couple of weeks.
In particular there is space for use-cases to be added, where we've 
currently only bullet listed some ideas.

Please send comments and suggested text to add, to the tcpprague list, 
of offlist if you prefer.



Bob

On 03/06/16 16:52, internet-drafts@ietf.org wrote:
> A new version of I-D, draft-briscoe-tsvwg-aqm-tcpm-rmcat-l4s-problem-00.txt
> has been successfully submitted by Bob Briscoe and posted to the
> IETF repository.
>
> Name:		draft-briscoe-tsvwg-aqm-tcpm-rmcat-l4s-problem
> Revision:	00
> Title:		Low Latency, Low Loss, Scalable Throughput (L4S) Internet Service: Problem Statement
> Document date:	2016-06-03
> Group:		Individual Submission
> Pages:		17
> URL:            https://www.ietf.org/internet-drafts/draft-briscoe-tsvwg-aqm-tcpm-rmcat-l4s-problem-00.txt
> Status:         https://datatracker.ietf.org/doc/draft-briscoe-tsvwg-aqm-tcpm-rmcat-l4s-problem/
> Htmlized:       https://tools.ietf.org/html/draft-briscoe-tsvwg-aqm-tcpm-rmcat-l4s-problem-00
>
>
> Abstract:
>     This document motivates a new service that the Internet could provide
>     to eventually replace best efforts for all traffic: Low Latency, Low
>     Loss, Scalable throughput (L4S).  It is becoming common for all (or
>     most) applications being run by a user at any one time to require low
>     latency, but the only solution the IETF can offer for ultra-low
>     queuing latency is Diffserv, which only offers low latency for some
>     packets at the expense of others.  Diffserv has also proved hard to
>     deploy widely end-to-end.
>
>     In contrast, a zero-config incrementally deployable solution has been
>     demonstrated that keeps average queuing delay under a millisecond for
>     _all_ applications even under very heavy load; and it keeps
>     congestion loss to zero.  At the same time it solves the long-running
>     problem with the scalability of TCP throughput.  Even with a high
>     capacity broadband access, the resulting performance under load is
>     remarkably and consistently improved for applications such as
>     interactive video, conversational video, voice, Web, gaming, instant
>     messaging, remote desktop and cloud-based apps.  This document
>     explains the underlying problems that have been preventing the
>     Internet from enjoying such performance improvements.  It then
>     outlines the parts necessary for a solution and the steps that will
>     be needed to standardize them.
>
>                                                                                    
>
>
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
>
> The IETF Secretariat
>

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