[Fecframe] RFC 6681 on Raptor Forward Error Correction (FEC) Schemes for FECFRAME

rfc-editor@rfc-editor.org Tue, 14 August 2012 16:27 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: fecframe@ietfa.amsl.com
Delivered-To: fecframe@ietfa.amsl.com
Received: from localhost (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id EE58B21F86E1; Tue, 14 Aug 2012 09:27:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.995
X-Spam-Status: No, score=-101.995 tagged_above=-999 required=5 tests=[AWL=0.005, 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 YpOTYwns7X0c; Tue, 14 Aug 2012 09:27:37 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id 8AF1421F869F; Tue, 14 Aug 2012 09:27:37 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id C0356B1E002; Tue, 14 Aug 2012 09:26:12 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120814162612.C0356B1E002@rfc-editor.org>
Date: Tue, 14 Aug 2012 09:26:12 -0700 (PDT)
Cc: fecframe@ietf.org, rfc-editor@rfc-editor.org
Subject: [Fecframe] RFC 6681 on Raptor Forward Error Correction (FEC) Schemes for FECFRAME
X-BeenThere: fecframe@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Discussion of FEC Framework <fecframe.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/fecframe>, <mailto:fecframe-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/fecframe>
List-Post: <mailto:fecframe@ietf.org>
List-Help: <mailto:fecframe-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/fecframe>, <mailto:fecframe-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 14 Aug 2012 16:27:38 -0000

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

        RFC 6681

        Title:      Raptor Forward Error Correction (FEC) 
                    Schemes for FECFRAME 
        Author:     M. Watson, T. Stockhammer,
                    M. Luby
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2012
        Mailbox:    watsonm@netflix.com, 
        Pages:      22
        Characters: 46372
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-fecframe-raptor-11.txt

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

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 the 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 the protection of arbitrary packet flows,
two that are optimized for small source blocks, and two for the
protection of a single flow that already contains a sequence number.
Repair data may be sent over arbitrary datagram transport (e.g., UDP)

This document is a product of the FEC Framework 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