rfc9407v3.txt | rfc9407.txt | |||
---|---|---|---|---|
Internet Research Task Force (IRTF) J. Detchart | Internet Research Task Force (IRTF) J. Detchart | |||
Request for Comments: 9407 ISAE-SUPAERO | Request for Comments: 9407 ISAE-SUPAERO | |||
Category: Experimental E. Lochin | Category: Experimental E. Lochin | |||
ISSN: 2070-1721 ENAC | ISSN: 2070-1721 ENAC | |||
J. Lacan | J. Lacan | |||
ISAE-SUPAERO | ISAE-SUPAERO | |||
V. Roca | V. Roca | |||
INRIA | INRIA | |||
May 2023 | June 2023 | |||
Tetrys: An On-the-Fly Network Coding Protocol | Tetrys: An On-the-Fly Network Coding Protocol | |||
Abstract | Abstract | |||
This document describes Tetrys, which is an on-the-fly network coding | This document describes Tetrys, which is an on-the-fly network coding | |||
protocol that can be used to transport delay-sensitive and loss- | protocol that can be used to transport delay-sensitive and loss- | |||
sensitive data over a lossy network. Tetrys may recover from | sensitive data over a lossy network. Tetrys may recover from | |||
erasures within an RTT-independent delay thanks to the transmission | erasures within an RTT-independent delay thanks to the transmission | |||
of coded packets. This document is a record of the experience gained | of coded packets. This document is a record of the experience gained | |||
skipping to change at line 104 ¶ | skipping to change at line 104 ¶ | |||
Authors' Addresses | Authors' Addresses | |||
1. Introduction | 1. Introduction | |||
This document is a product of and represents the collaborative work | This document is a product of and represents the collaborative work | |||
and consensus of the Coding for Efficient NetWork Communications | and consensus of the Coding for Efficient NetWork Communications | |||
Research Group (NWCRG). It is not an IETF product or an IETF | Research Group (NWCRG). It is not an IETF product or an IETF | |||
standard. | standard. | |||
This document describes Tetrys, which is an on-the-fly network coding | This document describes Tetrys, which is an on-the-fly network coding | |||
protocol that can be used to transport delay-sensitive and and loss- | protocol that can be used to transport delay-sensitive and loss- | |||
sensitive data over a lossy network. Network codes were introduced | sensitive data over a lossy network. Network codes were introduced | |||
in the early 2000s [AHL-00] to address the limitations of | in the early 2000s [AHL-00] to address the limitations of | |||
transmission over the Internet (delay, capacity, and packet loss). | transmission over the Internet (delay, capacity, and packet loss). | |||
While network codes have seen some deployment fairly recently in the | While network codes have seen some deployment fairly recently in the | |||
Internet community, the use of application-layer erasure codes in the | Internet community, the use of application-layer erasure codes in the | |||
IETF has already been standardized in the RMT [RFC5052] [RFC5445] and | IETF has already been standardized in the RMT [RFC5052] [RFC5445] and | |||
FECFRAME [RFC8680] Working Groups. The protocol presented here may | FECFRAME [RFC8680] Working Groups. The protocol presented here may | |||
be seen as a network-coding extension to standard unicast transport | be seen as a network-coding extension to standard unicast transport | |||
protocols (or even multicast or anycast with a few modifications). | protocols (or even multicast or anycast with a few modifications). | |||
The current proposal may be considered a combination of network | The current proposal may be considered a combination of network | |||
End of changes. 2 change blocks. | ||||
2 lines changed or deleted | 2 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |