%% You should probably cite draft-ietf-tsvwg-fecframe-ext instead of this I-D. @techreport{roca-tsvwg-fecframev2-04, number = {draft-roca-tsvwg-fecframev2-04}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-roca-tsvwg-fecframev2/04/}, author = {Vincent Roca and Ali C. Begen}, title = {{Forward Error Correction (FEC) Framework Extension to Sliding Window Codes}}, pagetotal = 20, year = 2017, month = jun, day = 27, abstract = {RFC 6363 describes a framework for using Forward Error Correction (FEC) codes with applications in public and private IP networks to provide protection against packet loss. The framework supports applying FEC to arbitrary packet flows over unreliable transport and is primarily intended for real-time, or streaming, media. However FECFRAME as per RFC 6363 is restricted to block FEC codes. The present document extends FECFRAME to support FEC Codes based on a sliding encoding window, in addition to Block FEC Codes, in a backward compatible way. During multicast/broadcast real-time content delivery, the use of sliding window codes significantly improves robustness in harsh environments, with less repair traffic and lower FEC-related added latency.}, }