Forward Error Correction (FEC) Framework Extension to Sliding Window Codes
draft-ietf-tsvwg-fecframe-ext-06

• Status
• IESG evaluation record
• IESG writeups
• Email expansions
• History

• Versions
• 00
• 01
• 02
• 03
• 04
• 05
• 06

TSVWG                                                            V. Roca
Internet-Draft                                                     INRIA
Updates: 6363 (if approved)                                     A. Begen
Intended status: Standards Track                         Networked Media
Expires: March 23, 2019                               September 19, 2018

  Forward Error Correction (FEC) Framework Extension to Sliding Window
                                 Codes
                    draft-ietf-tsvwg-fecframe-ext-06

Abstract

   RFC 6363 describes a framework for using Forward Error Correction
   (FEC) codes 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 updates 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.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at https://datatracker.ietf.org/drafts/current/.

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on March 23, 2019.

Copyright Notice

   Copyright (c) 2018 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

Roca & Begen             Expires March 23, 2019                 [Page 1]
Internet-Draft           FEC Framework Extension          September 2018

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (https://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   2
   2.  Definitions and Abbreviations . . . . . . . . . . . . . . . .   4
   3.  Summary of Architecture Overview  . . . . . . . . . . . . . .   7
   4.  Procedural Overview . . . . . . . . . . . . . . . . . . . . .  10
     4.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .  10
     4.2.  Sender Operation with Sliding Window FEC Codes  . . . . .  10
     4.3.  Receiver Operation with Sliding Window FEC Codes  . . . .  13
   5.  Protocol Specification  . . . . . . . . . . . . . . . . . . .  15
     5.1.  General . . . . . . . . . . . . . . . . . . . . . . . . .  15
     5.2.  FEC Framework Configuration Information . . . . . . . . .  16
     5.3.  FEC Scheme Requirements . . . . . . . . . . . . . . . . .  16
   6.  Feedback  . . . . . . . . . . . . . . . . . . . . . . . . . .  16
   7.  Transport Protocols . . . . . . . . . . . . . . . . . . . . .  17
   8.  Congestion Control  . . . . . . . . . . . . . . . . . . . . .  17
   9.  Implementation Status . . . . . . . . . . . . . . . . . . . .  17
   10. Security Considerations . . . . . . . . . . . . . . . . . . .  17
   11. Operations and Management Considerations  . . . . . . . . . .  18
   12. IANA Considerations . . . . . . . . . . . . . . . . . . . . .  18
   13. Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  18
   14. References  . . . . . . . . . . . . . . . . . . . . . . . . .  18
     14.1.  Normative References . . . . . . . . . . . . . . . . . .  18
     14.2.  Informative References . . . . . . . . . . . . . . . . .  18
   Appendix A.  About Sliding Encoding Window Management (non
                Normative) . . . . . . . . . . . . . . . . . . . . .  20
   Authors' Addresses  . . . . . . . . . . . . . . . . . . . . . . .  21

1.  Introduction

   Many applications need to transport a continuous stream of packetized
   data from a source (sender) to one or more destinations (receivers)
   over networks that do not provide guaranteed packet delivery.  In
   particular packets may be lost, which is strictly the focus of this
   document: we assume that transmitted packets are either lost (e.g.,