%% You should probably cite rfc8681 instead of this I-D. @techreport{ietf-tsvwg-rlc-fec-scheme-03, number = {draft-ietf-tsvwg-rlc-fec-scheme-03}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-tsvwg-rlc-fec-scheme/03/}, author = {Vincent Roca and Belkacem Teibi}, title = {{Sliding Window Random Linear Code (RLC) Forward Erasure Correction (FEC) Schemes for FECFRAME}}, pagetotal = 30, year = 2018, month = may, day = 7, abstract = {This document describes two fully-specified Forward Erasure Correction (FEC) Schemes for Sliding Window Random Linear Codes (RLC), one for RLC over GF(2) (binary case), a second one for RLC over GF(2\textasciicircum{}\textasciicircum{}8), both of them with the possibility of controlling the code density. They can protect arbitrary media streams along the lines defined by FECFRAME extended to sliding window FEC codes. These sliding window FEC codes rely on an encoding window that slides over the source symbols, generating new repair symbols whenever needed. Compared to block FEC codes, these sliding window FEC codes offer key advantages with real-time flows in terms of reduced FEC- related latency while often providing improved packet erasure recovery capabilities.}, }