Generic Application Programming Interface (API) for Sliding Window FEC Codes
draft-roca-nwcrg-generic-fec-api-01

The information below is for an old version of the document
Document Type Active Internet-Draft (individual)
Last updated 2018-03-21
Stream (None)
Intended RFC status (None)
Formats pdf htmlized 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)
NWCRG                                                      V. Roca (Ed.)
Internet-Draft                                                     INRIA
Intended status: Informational                               J. Detchart
Expires: September 22, 2018                               ISAE - Supaero
                                                                C. Adjih
                                                                   INRIA
                                                             M. Pedersen
                                                           Steinwurf ApS
                                                                I. Swett
                                                                  Google
                                                          March 21, 2018

 Generic Application Programming Interface (API) for Sliding Window FEC
                                 Codes
                  draft-roca-nwcrg-generic-fec-api-01

Abstract

   This document introduces a generic Application Programming Interface
   (API) for sliding window FEC codes.  This API is meant to be
   compatible with any sliding window FEC code.  It defines the core
   procedures and functions meant to control the codec (i.e.,
   implementation of the FEC code), but leaves out all upper layer
   aspects that are the responsibility of the application or protocol
   making use of the codec.  As a consequence, this is not an API for a
   FEC Scheme since certain mechanisms that must be defined by any FEC
   Scheme (e.g., signalling and FEC Payload IDs) are the responsibility
   of the caller instead of being addressed by the codec.  A goal of
   this document is to pave the way for a future open-source
   implementation of such codes, another goal is to simplify the
   development of content delivery protocols that rely on sliding window
   FEC codes for robust transmissions.

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."

Roca (Ed.), et al.     Expires September 22, 2018               [Page 1]
Internet-Draft                 Generic API                    March 2018

   This Internet-Draft will expire on September 22, 2018.

Copyright Notice

   Copyright (c) 2018 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
   (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  . . . . . . . . . . . . . . . . . . . . . . . .   3
   2.  Definitions and Abbreviations . . . . . . . . . . . . . . . .   3
   3.  AL-FEC Codes and Mechanisms Considered by the Generic API . .   4
     3.1.  Mechanisms Considered or Ignored by the API . . . . . . .   5
   4.  Generic API Proposal  . . . . . . . . . . . . . . . . . . . .   5
     4.1.  General definitions (Sender and Receiver) . . . . . . . .   5
     4.2.  Encoder . . . . . . . . . . . . . . . . . . . . . . . . .   6
     4.3.  Decoder . . . . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Security Considerations . . . . . . . . . . . . . . . . . . .   6
   6.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .   7
   7.  Acknowledgments . . . . . . . . . . . . . . . . . . . . . . .   7
   8.  References  . . . . . . . . . . . . . . . . . . . . . . . . .   7
     8.1.  Normative References  . . . . . . . . . . . . . . . . . .   7
     8.2.  Informative References  . . . . . . . . . . . . . . . . .   7
   Appendix A.  Existing APIs  . . . . . . . . . . . . . . . . . . .   8
     A.1.  Morten API proposal . . . . . . . . . . . . . . . . . . .   8
       A.1.1.  Encoder . . . . . . . . . . . . . . . . . . . . . . .   8
       A.1.2.  Decoder . . . . . . . . . . . . . . . . . . . . . . .  11
     A.2.  Jonathan API proposal . . . . . . . . . . . . . . . . . .  14
     A.3.  Cedric API proposal . . . . . . . . . . . . . . . . . . .  19
     A.4.  Ian API proposal  . . . . . . . . . . . . . . . . . . . .  20
Show full document text