[Fecframe] RFC 6682 on RTP Payload Format for Raptor Forward Error Correction (FEC)

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 [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 10BF621F870F; Tue, 14 Aug 2012 09:27:50 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.995
X-Spam-Level:
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 ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hbgZCfHqPrYw; Tue, 14 Aug 2012 09:27:49 -0700 (PDT)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2001:1890:123a::1:2f]) by ietfa.amsl.com (Postfix) with ESMTP id A6EFC21F86F8; Tue, 14 Aug 2012 09:27:49 -0700 (PDT)
Received: by rfc-editor.org (Postfix, from userid 30) id D7014B1E005; Tue, 14 Aug 2012 09:26:24 -0700 (PDT)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20120814162624.D7014B1E005@rfc-editor.org>
Date: Tue, 14 Aug 2012 09:26:24 -0700 (PDT)
Cc: fecframe@ietf.org, rfc-editor@rfc-editor.org
Subject: [Fecframe] RFC 6682 on RTP Payload Format for Raptor Forward Error Correction (FEC)
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:50 -0000

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

        
        RFC 6682

        Title:      RTP Payload Format for Raptor 
                    Forward Error Correction (FEC) 
        Author:     M. Watson, T. Stockhammer,
                    M. Luby
        Status:     Standards Track
        Stream:     IETF
        Date:       August 2012
        Mailbox:    watsonm@netflix.com, 
                    stockhammer@nomor.de, 
                    luby@qualcomm.com
        Pages:      18
        Characters: 35386
        Updates/Obsoletes/SeeAlso:   None

        I-D Tag:    draft-ietf-fecframe-rtp-raptor-07.txt

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

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.  [STANDARDS-TRACK]

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
  http://www.ietf.org/mailman/listinfo/ietf-announce
  http://mailman.rfc-editor.org/mailman/listinfo/rfc-dist

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