Browse Prior Art Database

RTP Payload Format for Raptor Forward Error Correction (FEC) (RFC6682)

IP.com Disclosure Number: IPCOM000220906D
Publication Date: 2012-Aug-15
Document File: 36 page(s) / 36K

Publishing Venue

The IP.com Prior Art Database

Related People

M. Watson: AUTHOR [+3]

Abstract

The FEC Framework [RFC6363] defines a general framework for the use of Forward Error Correction in association with arbitrary packet flows, including flows over UDP and RTP [RFC3550]. Forward Error Correction operates by generating redundant data packets ("repair data") that can be sent independently from the original flow. At a receiver, the original flow can be reconstructed provided a sufficient set of redundant data packets and possibly original data packets are received.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 8% of the total text.

Internet Engineering Task Force (IETF)                         M. Watson Request for Comments: 6682                                       Netflix Category: Standards Track                                 T. Stockhammer ISSN: 2070-1721                                           Nomor Research                                                                  M. Luby                                                    Qualcomm Incorporated                                                              August 2012

       RTP Payload Format for Raptor Forward Error Correction (FEC)

Abstract

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

Status of This Memo

   This is an Internet Standards Track document.

   This document is a product of the Internet Engineering Task Force    (IETF).  It represents the consensus of the IETF community.  It has    received public review and has been approved for publication by    the Internet Engineering Steering Group (IESG).  Further    information on Internet Standards is available in Section 2 of    RFC 5741.

   Information about the current status of this document, any    errata, and how to provide feedback on it may be obtained at    http://www.rfc-editor.org/info/rfc6682.

Watson, et al.               Standards Track                    [Page 1]
 RFC 6682              RTP Payload Format for Raptor          August 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    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 Acr...