[Rmt] RFC 6330 on RaptorQ Forward Error Correction Scheme for Object Delivery

rfc-editor@rfc-editor.org Fri, 12 August 2011 23:56 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: rmt@ietfa.amsl.com
Delivered-To: rmt@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 4470A21F8AED; Fri, 12 Aug 2011 16:56:39 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.254
X-Spam-Status: No, score=-102.254 tagged_above=-999 required=5 tests=[AWL=-0.254, BAYES_00=-2.599, J_CHICKENPOX_93=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id VlK7n8TAmBJ7; Fri, 12 Aug 2011 16:56:38 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id CE20221F8AEC; Fri, 12 Aug 2011 16:56:38 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id 749B198C233; Fri, 12 Aug 2011 16:57:17 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20110812235717.749B198C233@rfc-editor.org>
Date: Fri, 12 Aug 2011 16:57:17 -0700 (PDT)
Cc: rmt@ietf.org, rfc-editor@rfc-editor.org
Subject: [Rmt] RFC 6330 on RaptorQ Forward Error Correction Scheme for Object Delivery
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/rmt>, <mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/rmt>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/rmt>, <mailto:rmt-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 12 Aug 2011 23:56:39 -0000

A new Request for Comments is now available in online RFC libraries.

        RFC 6330

        Title:      RaptorQ Forward Error Correction Scheme 
                    for Object Delivery 
        Author:     M. Luby, A. Shokrollahi,
                    M. Watson, T. Stockhammer,
                    L. Minder
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2011
        Mailbox:    luby@qualcomm.com, 
                    watsonm@netflix.com,  stockhammer@nomor.de, 
        Pages:      69
        Characters: 169852
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-rmt-bb-fec-raptorq-06.txt

        URL:        http://www.rfc-editor.org/rfc/rfc6330.txt

This document describes a Fully-Specified Forward Error Correction
(FEC) scheme, corresponding to FEC Encoding ID 6, for the RaptorQ FEC
code and its application to reliable delivery of data objects.

RaptorQ codes are a new family of codes that provide superior
flexibility, support for larger source block sizes, and better coding
efficiency than Raptor codes in RFC 5053.  RaptorQ is also a fountain
code, i.e., as many encoding symbols as needed can be generated on
the fly by the encoder from the source symbols of a source block of
data.  The decoder is able to recover the source block from almost
any set of encoding symbols of sufficient cardinality -- in most
cases, a set of cardinality equal to the number of source symbols is
sufficient; in rare cases, a set of cardinality slightly more than
the number of source symbols is required.

The RaptorQ code described here is a systematic code, meaning that
all the source symbols are among the encoding symbols that can be
generated.  [STANDARDS-TRACK]

This document is a product of the Reliable Multicast Transport Working Group of the IETF.

This is now a Proposed Standard Protocol.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/rfcsearch.html.
For downloading RFCs, see http://www.rfc-editor.org/rfc.html.

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC