Raptor FEC Schemes for FECFRAME
draft-ietf-fecframe-raptor-08

The information below is for an old version of the document
Document Type Active Internet-Draft (fecframe WG)
Last updated 2011-12-16 (latest revision 2011-11-24)
Replaces draft-watson-fecframe-raptor
Stream IETF
Intended RFC status Proposed Standard
Formats plain text pdf html
Stream WG state WG Document
Document shepherd None
IESG IESG state AD Evaluation::AD Followup
Telechat date
Responsible AD David Harrington
IESG note Greg Shepherd (gjshep@gmail.com) is the document shepherd.
Send notices to fecframe-chairs@tools.ietf.org, draft-ietf-fecframe-raptor@tools.ietf.org
FEC Framework                                                  M. Watson
Internet-Draft                                                   Netflix
Intended status:  Standards Track                         T. Stockhammer
Expires:  August 27, 2012                                 Nomor Research
                                                                 M. Luby
                                                   Qualcomm Incorporated
                                                       February 24, 2012

                    Raptor FEC Schemes for FECFRAME
                     draft-ietf-fecframe-raptor-08

Abstract

   This document describes Fully-Specified Forward Error Correction
   (FEC) Schemes for the Raptor and RaptorQ codes and their application
   to reliable delivery of media streams in the context of FEC
   Framework.  The Raptor and RaptorQ codes are systematic codes, where
   a number of repair symbols are generated from a set of source symbols
   and sent in one or more repair flows in addition to the source
   symbols that are sent to the receiver(s) within a source flow.  The
   Raptor and RaptorQ codes offer close to optimal protection against
   arbitrary packet losses at a low computational complexity.  Six FEC
   Schemes are defined, two for protection of arbitrary packet flows,
   two that are optimised for small source blocks and another two for
   protection of a single flow that already contains a sequence number.
   Repair data may be sent over arbitrary datagram transport (e.g.  UDP)
   or using RTP.

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

Watson, et al.           Expires August 27, 2012                [Page 1]
Internet-Draft              Raptor FEC Scheme              February 2012

   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.

   This document may contain material from IETF Documents or IETF
   Contributions published or made publicly available before November
   10, 2008.  The person(s) controlling the copyright in some of this
   material may not have granted the IETF Trust the right to allow
   modifications of such material outside the IETF Standards Process.
   Without obtaining an adequate license from the person(s) controlling
   the copyright in such materials, this document may not be modified
   outside the IETF Standards Process, and derivative works of it may
   not be created outside the IETF Standards Process, except to format
   it for publication as an RFC or to translate it into languages other
   than English.

Watson, et al.           Expires August 27, 2012                [Page 2]
Internet-Draft              Raptor FEC Scheme              February 2012

Table of Contents

   1.  Introduction . . . . . . . . . . . . . . . . . . . . . . . . .  5
   2.  Document Outline . . . . . . . . . . . . . . . . . . . . . . .  6
   3.  Requirements Notation  . . . . . . . . . . . . . . . . . . . .  6
   4.  Definitions and Abbreviations  . . . . . . . . . . . . . . . .  6
     4.1.  Definitions  . . . . . . . . . . . . . . . . . . . . . . .  7
     4.2.  Abbreviations  . . . . . . . . . . . . . . . . . . . . . .  7
   5.  General procedures for Raptor FEC Schemes  . . . . . . . . . .  7
   6.  Raptor FEC Schemes for arbitrary packet flows  . . . . . . . .  9
     6.1.  Introduction . . . . . . . . . . . . . . . . . . . . . . .  9
     6.2.  Formats and Codes  . . . . . . . . . . . . . . . . . . . .  9
       6.2.1.  FEC Framework Configuration Information  . . . . . . .  9
Show full document text