[iccrg] Fwd: [nwcrg] RFC 9265 on Forward Erasure Correction (FEC) Coding and Congestion Control in Transport

Perhaps this is of interest to this group too…

Cheers,
Michael


> Begin forwarded message:
> 
> From: rfc-editor@rfc-editor.org
> Subject: [nwcrg] RFC 9265 on Forward Erasure Correction (FEC) Coding and Congestion Control in Transport
> Date: July 26, 2022 at 6:59:14 PM GMT+2
> To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org, irtf-announce@irtf.org
> Cc: rfc-editor@rfc-editor.org, drafts-update-ref@iana.org, nwcrg@irtf.org
> Resent-From: <michawe@ifi.uio.no>
> 
> 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
> 
> _______________________________________________
> nwcrg mailing list
> nwcrg@irtf.org
> https://www.irtf.org/mailman/listinfo/nwcrg