RFC 9265: Forward Erasure Correction (FEC) Coding and Congestion Control in Transport
In plain English — editorial summary, not part of the RFC
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.
Document record
- Document ID
- RFC9265
- Published
- July 2022
- Authors
- N. Kuhn; E. Lochin; F. Michel; M. Welzl
- Status
- INFORMATIONAL
- Stream
- IRTF
- Area
- —
- Pages
- 21
- Also known as
- —
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 9600TRansparent Interconnection of Lots of Links (TRILL): Explicit Congestion Notification (ECN) SupportCurrent
August 2024
- RFC 9681IS-IS Fast FloodingCurrent
November 2024
- RFC 7893Pseudowire Congestion ConsiderationsCurrent
June 2016
- RFC 3742Limited Slow-Start for TCP with Large Congestion WindowsCurrent
March 2004
- RFC 3450Asynchronous Layered Coding (ALC) Protocol InstantiationObsoleted
December 2002
- RFC 3448TCP Friendly Rate Control (TFRC): Protocol SpecificationObsoleted
January 2003
- RFC 2887The Reliable Multicast Design Space for Bulk Data TransferCurrent
August 2000
- RFC 1951DEFLATE Compressed Data Format Specification version 1.3Current
May 1996
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?