[Fecframe] I-D Action: draft-ietf-fecframe-rtp-raptor-07.txt

internet-drafts@ietf.org Fri, 24 February 2012 13:27 UTC

Return-Path: <internet-drafts@ietf.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 6A99221F8748; Fri, 24 Feb 2012 05:27:32 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.587
X-Spam-Status: No, score=-102.587 tagged_above=-999 required=5 tests=[AWL=0.012, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id KNNsBZQaY8Ln; Fri, 24 Feb 2012 05:27:32 -0800 (PST)
Received: from ietfa.amsl.com (localhost []) by ietfa.amsl.com (Postfix) with ESMTP id 0A79921F862F; Fri, 24 Feb 2012 05:27:32 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 3.64p2
Message-ID: <20120224132732.15074.26725.idtracker@ietfa.amsl.com>
Date: Fri, 24 Feb 2012 05:27:32 -0800
Cc: fecframe@ietf.org
Subject: [Fecframe] I-D Action: draft-ietf-fecframe-rtp-raptor-07.txt
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: Fri, 24 Feb 2012 13:27:32 -0000

A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the FEC Framework Working Group of the IETF.

	Title           : RTP Payload Format for Raptor FEC
	Author(s)       : Mark Watson
                          Thomas Stockhammer
                          Michael Luby
	Filename        : draft-ietf-fecframe-rtp-raptor-07.txt
	Pages           : 25
	Date            : 2012-02-24

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

A URL for this Internet-Draft is:

Internet-Drafts are also available by anonymous FTP at:

This Internet-Draft can be retrieved at: