FECFRAMEv2: Adding Sliding Encoding Window Capabilities to the FEC Framework: Problem Position
draft-roca-nwcrg-fecframev2-problem-position-03

Document Type Active Internet-Draft (individual)
Last updated 2016-11-14
Stream (None)
Intended RFC status (None)
Formats plain text xml pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state I-D Exists
Telechat date
Responsible AD (None)
Send notices to (None)
IRTF Network Coding Research Group (NWCRG)                       V. Roca
Internet-Draft                                                     INRIA
Intended status: Informational                         November 14, 2016
Expires: May 18, 2017

   FECFRAMEv2: Adding Sliding Encoding Window Capabilities to the FEC
                      Framework: Problem Position
            draft-roca-nwcrg-fecframev2-problem-position-03

Abstract

   The Forward Error Correction (FEC) Framework (or FECFRAME) (RFC 6363)
   has been defined by the FECFRAME IETF WG to enable the use of FEC
   Encoding with real-time flows in a flexible manner.  The original
   FECFRAME specification only considers the use of block FEC codes,
   wherein the input flow(s) is(are) segmented into a sequence of blocks
   and FEC encoding performed independently on a per-block basis.  This
   document discusses an extension of FECFRAME in order to enable a
   sliding (potentially elastic) window encoding of the input flow(s),
   using convolutional FEC codes for the erasure channel, as an
   alternative to block FEC codes.

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 http://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 May 18, 2017.

Copyright Notice

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

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of

Roca                      Expires May 18, 2017                  [Page 1]
Internet-Draft        FECFRAMEv2: Problem Position         November 2016

   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.  Notations, Definitions and Abbreviations  . . . . . . . . . .   4
     2.1.  Requirements Notation . . . . . . . . . . . . . . . . . .   4
     2.2.  Definitions . . . . . . . . . . . . . . . . . . . . . . .   4
   3.  Key features of FECFRAME  . . . . . . . . . . . . . . . . . .   5
     3.1.  FECFRAME is more a shim layer than a protocol
           instantiation . . . . . . . . . . . . . . . . . . . . . .   6
     3.2.  FECFRAME is highly flexible . . . . . . . . . . . . . . .   6
     3.3.  Details are in each FEC Scheme  . . . . . . . . . . . . .   6
     3.4.  FECFRAME needs session-level description  . . . . . . . .   7
   4.  Application of FECFRAME (RFC 6363) to network coding use-
       cases: a discussion . . . . . . . . . . . . . . . . . . . . .   7
     4.1.  Block versus convolutional codes  . . . . . . . . . . . .   7
     4.2.  End-to-end versus in-network re-coding  . . . . . . . . .   8
     4.3.  Single versus multi-sources, intra versus inter-flows
           coding  . . . . . . . . . . . . . . . . . . . . . . . . .   8
     4.4.  Single versus multi-paths . . . . . . . . . . . . . . . .   8
   5.  Architectural considerations for FECFRAMEv2 . . . . . . . . .   9
     5.1.  FECFRAMEv2 in sliding encoding window mode  . . . . . . .   9
     5.2.  ADU(I) to source symbol mapping . . . . . . . . . . . . .  11
     5.3.  Sliding encoding window management  . . . . . . . . . . .  12
     5.4.  Encoding Symbol Identifiers (ESI) . . . . . . . . . . . .  13
     5.5.  Block and convolutional co-existence in a given
           FECFRAMEv2 session  . . . . . . . . . . . . . . . . . . .  14
   6.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
   7.  Privacy Considerations  . . . . . . . . . . . . . . . . . . .  15
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   9.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .  15
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  15
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  15
     10.2.  Informative References . . . . . . . . . . . . . . . . .  16
Show full document text