RFC 9265 on Forward Erasure Correction (FEC) Coding and Congestion Control in Transport
rfc-editor@rfc-editor.org Tue, 26 July 2022 17:00 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 B7E9AC16ED02 for <ietf-announce@ietfa.amsl.com>; Tue, 26 Jul 2022 10:00:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.66
X-Spam-Level:
X-Spam-Status: No, score=-1.66 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HEADER_FROM_DIFFERENT_DOMAINS=0.248, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=no 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 9EYF_YaH1kDS for <ietf-announce@ietfa.amsl.com>; Tue, 26 Jul 2022 10:00:17 -0700 (PDT)
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 A6D16C16ECB6 for <ietf-announce@ietf.org>; Tue, 26 Jul 2022 09:59:14 -0700 (PDT)
Received: by rfcpa.amsl.com (Postfix, from userid 499) id 9B9036AB0A; Tue, 26 Jul 2022 09:59:14 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
Subject: RFC 9265 on Forward Erasure Correction (FEC) Coding and Congestion Control in Transport
From: rfc-editor@rfc-editor.org
Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, nwcrg@irtf.org
Content-type: text/plain; charset="UTF-8"
Message-Id: <20220726165914.9B9036AB0A@rfcpa.amsl.com>
Date: Tue, 26 Jul 2022 09:59:14 -0700
Archived-At: <https://mailarchive.ietf.org/arch/msg/ietf-announce/PmJYhAP2H6y9wRyJHX5_HTJWU8s>
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: Tue, 26 Jul 2022 17:00:21 -0000
A new Request for Comments is now available in online RFC libraries.
RFC 9265
Title: Forward Erasure Correction (FEC) Coding
and Congestion Control in Transport
Author: N. Kuhn,
E. Lochin,
F. Michel,
M. Welzl
Status: Informational
Stream: IRTF
Date: July 2022
Mailbox: nicolas.kuhn.ietf@gmail.com,
emmanuel.lochin@enac.fr,
francois.michel@uclouvain.be,
michawe@ifi.uio.no
Pages: 21
Updates/Obsoletes/SeeAlso: None
I-D Tag: draft-irtf-nwcrg-coding-and-congestion-12.txt
URL: https://www.rfc-editor.org/info/rfc9265
DOI: 10.17487/RFC9265
Forward Erasure Correction (FEC) is a reliability mechanism that is
distinct and separate from the retransmission logic in reliable
transfer protocols such as TCP. FEC coding can help deal with losses
at the end of transfers or with networks having non-congestion
losses. However, FEC coding mechanisms should not hide congestion
signals. This memo offers a discussion of how FEC coding and
congestion control can coexist. Another objective is to encourage the
research community to also consider congestion control aspects when
proposing and comparing FEC coding solutions in communication
systems.
This document is the product of the Coding for Efficient Network
Communications Research Group (NWCRG). The scope of the document is
end-to-end communications; FEC coding for tunnels is out of the scope
of the document.
This document is a product of the Coding for Efficient Network Communications Research Group of the IRTF.
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, rfc-dist and IRTF-Announce lists.To subscribe or unsubscribe, see
https://www.ietf.org/mailman/listinfo/ietf-announce
https://mailman.rfc-editor.org/mailman/listinfo/rfc-dist
https://www.irtf.org/mailman/listinfo/irtf-announce
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