RFC 9330 on Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture
rfc-editor@rfc-editor.org Fri, 20 January 2023 05:08 UTC
Return-Path: <wwwrun@rfcpa.amsl.com>
X-Original-To: ietf-announce@ietfa.amsl.com
Delivered-To: ietf-announce@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id B3EC3C151531; Thu, 19 Jan 2023 21:08:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.648
X-Spam-Level:
X-Spam-Status: No, score=-6.648 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.25, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_PASS=-0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=unavailable autolearn_force=no
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id KvkRqSibCx0F; Thu, 19 Jan 2023 21:08:51 -0800 (PST)
Received: from rfcpa.amsl.com (rfc-editor.org [50.223.129.200]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F34D9C14E514; Thu, 19 Jan 2023 21:08:50 -0800 (PST)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id C142D55A35; Thu, 19 Jan 2023 21:08:50 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
Subject: RFC 9330 on Low Latency, Low Loss, and Scalable Throughput (L4S) Internet Service: Architecture
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, tsvwg@ietf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20230120050850.C142D55A35@rfcpa.amsl.com>
Date: Thu, 19 Jan 2023 21:08:50 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/vVwPN23ImM_vsxDjO7kLwStujyQ>
X-BeenThere: ietf-announce@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: "IETF announcement list. No discussions." <ietf-announce.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ietf-announce/>
List-Post: <mailto:ietf-announce@ietf.org>
List-Help: <mailto:ietf-announce-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ietf-announce>, <mailto:ietf-announce-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 20 Jan 2023 05:08:55 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9330
Title: Low Latency, Low Loss, and
Scalable Throughput (L4S) Internet Service:
Architecture
Author: B. Briscoe, Ed.,
K. De Schepper,
M. Bagnulo,
G. White
Status: Informational
Stream: IETF
Date: January 2023
Mailbox: ietf@bobbriscoe.net,
koen.de_schepper@nokia.com,
marcelo@it.uc3m.es,
g.white@cablelabs.com
Pages: 36
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-ietf-tsvwg-l4s-arch-20.txt
URL: https://www.rfc-editor.org/info/rfc9330
DOI: 10.17487/RFC9330
This document describes the L4S architecture, which enables Internet
applications to achieve low queuing latency, low congestion loss, and
scalable throughput control. L4S is based on the insight that the
root cause of queuing delay is in the capacity-seeking 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 and instead adopt a new class of congestion
controls that can seek capacity with very little queuing. These are
aided by a modified form of Explicit Congestion Notification (ECN)
from the network. With this new architecture, applications can have
both low latency and high throughput.
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. The aim is for L4S latency and throughput to be usually much
better (and rarely worse) while typically not impacting Classic
performance.
This document is a product of the Transport Area Working Group Working Group of the IETF.
INFORMATIONAL: This memo provides information for the Internet community.
It does not specify an Internet standard of any kind. Distribution of
this memo is unlimited.
This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
For searching the RFC series, see https://www.rfc-editor.org/search
For downloading RFCs, see https://www.rfc-editor.org/retrieve/bulk
Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org. Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.
The RFC Editor Team
Association Management Solutions, LLC