Re: [tsvwg] I-D Action: draft-ietf-tsvwg-l4s-arch-09.txt

Bob Briscoe <ietf@bobbriscoe.net> Fri, 21 May 2021 20:41 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 480EF3A1FD2 for <tsvwg@ietfa.amsl.com>; Fri, 21 May 2021 13:41:29 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.434
X-Spam-Level:
X-Spam-Status: No, score=-1.434 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, NICE_REPLY_A=-0.001, SPF_HELO_NONE=0.001, SPF_SOFTFAIL=0.665, URIBL_BLOCKED=0.001] autolearn=no 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 aEFGt-9GJcSJ for <tsvwg@ietfa.amsl.com>; Fri, 21 May 2021 13:41:25 -0700 (PDT)
Received: from mail-ssdrsserver2.hosting.co.uk (mail-ssdrsserver2.hosting.co.uk [185.185.85.90]) (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 D874E3A1FD1 for <tsvwg@ietf.org>; Fri, 21 May 2021 13:41:24 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bobbriscoe.net; s=default; h=Content-Transfer-Encoding:Content-Type: In-Reply-To:MIME-Version:Date:Message-ID:From:References:To:Subject:Sender: Reply-To:Cc: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=Q29Z2cemwEdGQ/33zLz21+iKH02TFQQdaOpBDisuFKc=; b=6owrp4Yu7GGqsbyWFKwrLYQKUk U43dIoelr1hW49USfUU3HKUCfvzLDP+KPH9Hivf33A3i983r9KJ6UO1h233HrNpDXKIQHjkXy+7vt ofxeAVu+j6eHwbQFv71zWWcv7tMx6hAUsgjdB6XwKC6hoNFEMVqfQZ1chZTXO6aAiPLPAdW3c/BW5 Ap27Duitrtv1VlLoW/xa7spUyFF+msYZ+nyCDLFnt4MFeW3TUlP6dLf7bFMOmVZf8NRdvT7W9+Gmh 1Bhdp4uMwQcHEOxUxXVTN5q0XXYb59YeBqRBlQbBSxhZtTkRyHsaTeWCmR5+9dYg8hVcr5POl5k/D KcYdW2IA==;
Received: from 67.153.238.178.in-addr.arpa ([178.238.153.67]:42444 helo=[192.168.1.11]) by ssdrsserver2.hosting.co.uk with esmtpsa (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from <ietf@bobbriscoe.net>) id 1lkBxb-0004oQ-M4 for tsvwg@ietf.org; Fri, 21 May 2021 21:41:23 +0100
To: tsvwg@ietf.org
References: <162162932056.27302.15737191186307924684@ietfa.amsl.com>
From: Bob Briscoe <ietf@bobbriscoe.net>
Message-ID: <5bff94bb-9e96-f369-2531-34910556c2df@bobbriscoe.net>
Date: Fri, 21 May 2021 21:41:21 +0100
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1
MIME-Version: 1.0
In-Reply-To: <162162932056.27302.15737191186307924684@ietfa.amsl.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Content-Language: en-GB
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - ssdrsserver2.hosting.co.uk
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: ssdrsserver2.hosting.co.uk: authenticated_id: in@bobbriscoe.net
X-Authenticated-Sender: ssdrsserver2.hosting.co.uk: in@bobbriscoe.net
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/vYpBmfnT3oAAJLxrNpaUXXkPUZE>
Subject: Re: [tsvwg] I-D Action: draft-ietf-tsvwg-l4s-arch-09.txt
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: Fri, 21 May 2021 20:41:29 -0000

tsvwg,

We just updated l4s-arch to keep it consistent with the changes in 
ecn-l4s-id posted earlier today.

Pretty much only:
* ultra-low delay -> very low delay
* corrected x-refs to sections in ecn-l4s-id that have moved
* updated refs.

Also l4s-arch-08 expired a couple of days ago.


Bob

On 21/05/2021 21:35, internet-drafts@ietf.org wrote:
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the Transport Area Working Group WG of the IETF.
>
>          Title           : Low Latency, Low Loss, Scalable Throughput (L4S) Internet Service: Architecture
>          Authors         : Bob Briscoe
>                            Koen De Schepper
>                            Marcelo Bagnulo
>                            Greg White
> 	Filename        : draft-ietf-tsvwg-l4s-arch-09.txt
> 	Pages           : 41
> 	Date            : 2021-05-21
>
> Abstract:
>     This document describes the L4S architecture, which enables Internet
>     applications to achieve Low queuing Latency, Low Loss, and Scalable
>     throughput (L4S).  The insight on which L4S is based is that the root
>     cause of queuing delay is in the congestion controllers of senders,
>     not in the queue itself.  The L4S architecture is intended to enable
>     _all_ Internet applications to transition away from congestion
>     control algorithms that cause queuing delay, to a new class of
>     congestion controls that induce very little queuing, aided by
>     explicit congestion signaling from the network.  This new class of
>     congestion control can provide low latency for capacity-seeking
>     flows, so applications can achieve both high bandwidth and low
>     latency.
>
>     The architecture primarily concerns incremental deployment.  It
>     defines mechanisms that allow the new class of L4S congestion
>     controls to coexist with 'Classic' congestion controls in a shared
>     network.  These mechanisms aim to ensure that the latency and
>     throughput performance using an L4S-compliant congestion controller
>     is usually much better (and never worse) than the performance would
>     have been using a 'Classic' congestion controller, and that competing
>     flows continuing to use 'Classic' controllers are typically not
>     impacted by the presence of L4S.  These characteristics are important
>     to encourage adoption of L4S congestion control algorithms and L4S
>     compliant network elements.
>
>     The L4S architecture consists of three components: network support to
>     isolate L4S traffic from classic traffic; protocol features that
>     allow network elements to identify L4S traffic; and host support for
>     L4S congestion controls.
>
>
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-tsvwg-l4s-arch/
>
> There is also an htmlized version available at:
> https://datatracker.ietf.org/doc/html/draft-ietf-tsvwg-l4s-arch-09
>
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-tsvwg-l4s-arch-09
>
>
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
>
>

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