[tsvwg] Last Call: <draft-ietf-tsvwg-l4s-arch-18.txt> (Low Latency, Low Loss, Scalable Throughput (L4S) Internet Service: Architecture) to Informational RFC

The IESG <iesg-secretary@ietf.org> Thu, 07 July 2022 21:23 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: The IESG <iesg-secretary@ietf.org>
To: IETF-Announce <ietf-announce@ietf.org>
Auto-Submitted: auto-generated
Precedence: bulk
CC: Wesley Eddy <wes@mti-systems.com>, draft-ietf-tsvwg-l4s-arch@ietf.org, martin.h.duke@gmail.com, tsvwg-chairs@ietf.org, tsvwg@ietf.org, wes@mti-systems.com
Reply-To: last-call@ietf.org
Sender: iesg-secretary@ietf.org
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
Message-ID: <165722899022.61236.9517081173073942075@ietfa.amsl.com>
Date: Thu, 07 Jul 2022 14:23:10 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/tsvwg/WHzkUZXtpPIKtDkNBbd1RraTxkY>
Subject: [tsvwg] Last Call: <draft-ietf-tsvwg-l4s-arch-18.txt> (Low Latency, Low Loss, Scalable Throughput (L4S) Internet Service: Architecture) to Informational RFC

The IESG has received a request from the Transport Area Working Group WG
(tsvwg) to consider the following document: - 'Low Latency, Low Loss,
Scalable Throughput (L4S) Internet Service:
   Architecture'
  <draft-ietf-tsvwg-l4s-arch-18.txt> as Informational RFC

The IESG plans to make a decision in the next few weeks, and solicits final
comments on this action. Please send substantive comments to the
last-call@ietf.org mailing lists by 2022-07-21. Exceptionally, comments may
be sent to iesg@ietf.org instead. In either case, please retain the beginning
of the Subject line to allow automated sorting.

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.  With the L4S architecture all Internet
   applications could (but do not have to) transition away from
   congestion control algorithms that cause substantial queuing delay,
   to a new class of congestion controls that induce very little
   queuing, aided by explicit congestion signalling from the network.
   This new class of congestion controls 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 rarely worse) than 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 file can be obtained via
https://datatracker.ietf.org/doc/draft-ietf-tsvwg-l4s-arch/



No IPR declarations have been submitted directly on this I-D.

[tsvwg] Last Call: <draft-ietf-tsvwg-l4s-arch-18.… The IESG