datatracker.ietf.org
Sign In
Version 4.02, 2012-04-26
Report a bug

RTP Payload Format for Raptor FEC
draft-ietf-fecframe-rtp-raptor-07

Active Internet-Draft (fecframe WG)
Document Stream: IETF
Last updated: 2012-02-24
Replaces: draft-watson-fecframe-rtp-raptor
Intended RFC status:Proposed Standard
Other versions: plain text, pdf, html

IETF State: WG Document (fecframe)
Document shepherd:

IESG State: RFC Ed Queue
RFC Editor State: EDIT REF
Responsible AD:Martin Stiemerling
IESG Note:Greg Shepherd (gjshep@gmail.com) is the document shepherd.

FEC Framework Working Group                                    M. Watson
Internet-Draft                                                   Netflix
Intended status: Standards Track                          T. Stockhammer
Expires: August 27, 2012                                  Nomor Research
                                                                 M. Luby
                                                   Qualcomm Incorporated
                                                       February 24, 2012

                   RTP Payload Format for Raptor FEC
                   draft-ietf-fecframe-rtp-raptor-07

Abstract

   This document specifies an RTP Payload Format for Forward Error
   Correction repair data produced by the Raptor FEC Schemes.  Raptor
   FEC Schemes are specified for use with the IETF FEC Framework which
   supports transport of repair data over both UDP and RTP.  This
   document specifies the Payload Format which is required for the use
   of RTP to carry Raptor repair flows.

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 August 27, 2012.

Copyright Notice

   Copyright (c) 2012 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

Watson, et al.           Expires August 27, 2012                [Page 1]
Internet-Draft        RTP Payload Format for Raptor        February 2012

   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.  Conventions, Definitions and Acronyms  . . . . . . . . . . . .  4
   3.  Media Format Background  . . . . . . . . . . . . . . . . . . .  5
   4.  Payload Format . . . . . . . . . . . . . . . . . . . . . . . .  6
     4.1.  RTP Header Usage . . . . . . . . . . . . . . . . . . . . .  6
     4.2.  Payload Header . . . . . . . . . . . . . . . . . . . . . .  6
     4.3.  Payload Data . . . . . . . . . . . . . . . . . . . . . . .  6
   5.  Congestion Control Considerations  . . . . . . . . . . . . . .  7
   6.  Media Types  . . . . . . . . . . . . . . . . . . . . . . . . .  8
     6.1.  Registration of the application/raptorfec media type . . .  8
       6.1.1.  Media Type Definition  . . . . . . . . . . . . . . . .  8
     6.2.  Registration of the video/raptorfec media type . . . . . .  9
       6.2.1.  Media Type Definition  . . . . . . . . . . . . . . . .  9
     6.3.  Registration of the audio/raptorfec media type . . . . . . 11
       6.3.1.  Media Type Definition  . . . . . . . . . . . . . . . . 11
     6.4.  Registration of the text/raptorfec media type  . . . . . . 13
       6.4.1.  Media Type Definition  . . . . . . . . . . . . . . . . 13
   7.  Mapping to SDP . . . . . . . . . . . . . . . . . . . . . . . . 15
   8.  Offer/Answer considerations  . . . . . . . . . . . . . . . . . 16
   9.  Declarative SDP Considerations . . . . . . . . . . . . . . . . 17
   10. Repair Flow Generation and Recovery Procedures . . . . . . . . 18
     10.1. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 18
     10.2. Repair Packet Construction . . . . . . . . . . . . . . . . 18
     10.3. Usage of RTCP  . . . . . . . . . . . . . . . . . . . . . . 18
     10.4. Source Packet Reconstruction . . . . . . . . . . . . . . . 19
   11. Session Description Protocol (SDP) Example . . . . . . . . . . 20
   12. IANA Considerations  . . . . . . . . . . . . . . . . . . . . . 21
   13. Security Considerations  . . . . . . . . . . . . . . . . . . . 22
   14. References . . . . . . . . . . . . . . . . . . . . . . . . . . 23
     14.1. Normative References . . . . . . . . . . . . . . . . . . . 23
     14.2. Informative References . . . . . . . . . . . . . . . . . . 24