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

The information below is for an old version of the document
Document Type Active Internet-Draft (payload WG)
Last updated 2018-03-05
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... )
Revised I-D Needed - Issue raised by WGLC
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                                                        M. Zanaty
Internet-Draft                                                     Cisco
Intended status: Standards Track                                V. Singh
Expires: September 6, 2018                                  callstats.io
                                                                A. Begen
                                                         Networked Media
                                                              G. Mandyam
                                              Qualcomm Innovation Center
                                                           March 5, 2018

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

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 FEC repair
   packets are generated from a set of source packets.  These repair
   packets are sent in a redundancy RTP stream separate from the source
   RTP stream that carries the source packets.  RTP source packets that
   were lost in transmission can be reconstructed using the source and
   repair packets that were received.  The non-interleaved and
   interleaved parity codes which are defined in this specification
   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
   this specification can still work by simply ignoring the FEC repair
   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 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

Zanaty, et al.          Expires September 6, 2018               [Page 1]
Internet-Draft      RTP Payload Format for Parity FEC         March 2018

   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 September 6, 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
     1.1.  Parity Codes  . . . . . . . . . . . . . . . . . . . . . .   4
       1.1.1.  1-D Non-interleaved (Row) FEC Protection  . . . . . .   5
       1.1.2.  1-D Interleaved (Column) FEC Protection . . . . . . .   5
       1.1.3.  Use Cases for 1-D FEC Protection  . . . . . . . . . .   6
       1.1.4.  2-D (Row and Column) FEC Protection . . . . . . . . .   8
       1.1.5.  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 . . . . . . . . . . . . . . . . . .  16
     5.1.  Media Type Registration - Parity Codes  . . . . . . . . .  16
       5.1.1.  Registration of audio/flexfec . . . . . . . . . . . .  16
       5.1.2.  Registration of video/flexfec . . . . . . . . . . . .  18
       5.1.3.  Registration of text/flexfec  . . . . . . . . . . . .  19
Show full document text