RTP Payload Format for Flexible Forward Error Correction (FEC)
draft-ietf-payload-flexible-fec-scheme-01

The information below is for an old version of the document
Document Type Active Internet-Draft (payload WG)
Last updated 2016-02-17 (latest revision 2015-10-19)
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Additional URLs
- Mailing list discussion
Stream WG state WG Document (wg milestone: May 2018 - Submit RTP Payload F... )
Document shepherd Roni Even
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to "Roni Even" <roni.even@mail01.huawei.com>
PAYLOAD                                                         V. Singh
Internet-Draft                                   Nemu Dialogue System Oy
Intended status: Standards Track                                A. Begen
Expires: April 21, 2016
                                                               M. Zanaty
                                                                   Cisco
                                                              G. Mandyam
                                              Qualcomm Innovation Center
                                                        October 19, 2015

     RTP Payload Format for Flexible Forward Error Correction (FEC)
               draft-ietf-payload-flexible-fec-scheme-01

Abstract

   This document defines new RTP payload formats for the Forward Error
   Correction (FEC) packets that are generated by the non-interleaved
   and interleaved parity codes from a source media encapsulated in RTP.
   These parity codes are systematic codes, where a number of repair
   symbols are generated from a set of source symbols.  These repair
   symbols are sent in a repair flow separate from the source flow that
   carries the source symbols.  The non-interleaved and interleaved
   parity codes offer a good protection against random and bursty packet
   losses, respectively, at a cost of decent complexity.  The RTP
   payload formats that are defined in this document address the
   scalability issues experienced with the earlier specifications
   including RFC 2733, RFC 5109 and SMPTE 2022-1, and offer several
   improvements.  Due to these changes, the new payload formats are not
   backward compatible with the earlier specifications, but endpoints
   that do not implement the scheme can still work by simply ignoring
   the FEC packets.

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

Singh, et al.            Expires April 21, 2016                 [Page 1]
Internet-Draft      RTP Payload Format for Parity FEC       October 2015

   This Internet-Draft will expire on April 21, 2016.

Copyright Notice

   Copyright (c) 2015 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
   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
     1.1.  Use Cases for 1-D FEC Protection  . . . . . . . . . . . .   6
     1.2.  Use Cases for 2-D Parity FEC Protection . . . . . . . . .   7
     1.3.  Overhead Computation  . . . . . . . . . . . . . . . . . .   9
   2.  Requirements Notation . . . . . . . . . . . . . . . . . . . .   9
   3.  Definitions and Notations . . . . . . . . . . . . . . . . . .  10
     3.1.  Definitions . . . . . . . . . . . . . . . . . . . . . . .  10
     3.2.  Notations . . . . . . . . . . . . . . . . . . . . . . . .  10
   4.  Packet Formats  . . . . . . . . . . . . . . . . . . . . . . .  10
     4.1.  Source Packets  . . . . . . . . . . . . . . . . . . . . .  10
     4.2.  Repair Packets  . . . . . . . . . . . . . . . . . . . . .  10
   5.  Payload Format Parameters . . . . . . . . . . . . . . . . . .  14
     5.1.  Media Type Registration . . . . . . . . . . . . . . . . .  14
       5.1.1.  Registration of audio/flexfec . . . . . . . . . . . .  15
       5.1.2.  Registration of video/flexfec . . . . . . . . . . . .  16
       5.1.3.  Registration of text/flexfec  . . . . . . . . . . . .  17
       5.1.4.  Registration of application/flexfec . . . . . . . . .  19
     5.2.  Mapping to SDP Parameters . . . . . . . . . . . . . . . .  20
       5.2.1.  Offer-Answer Model Considerations . . . . . . . . . .  21
       5.2.2.  Declarative Considerations  . . . . . . . . . . . . .  21
   6.  Protection and Recovery Procedures  . . . . . . . . . . . . .  22
     6.1.  Overview  . . . . . . . . . . . . . . . . . . . . . . . .  22
Show full document text