[Rmt] RFC 3453 on The Use of Forward Error Correction (FEC) in Reliable Multicast
rfc-editor@rfc-editor.org Tue, 24 December 2002 19:06 UTC
Received: from www1.ietf.org (ietf.org [132.151.1.19] (may be forged)) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11588 for <rmt-archive@odin.ietf.org>; Tue, 24 Dec 2002 14:06:02 -0500 (EST)
Received: (from mailnull@localhost) by www1.ietf.org (8.11.6/8.11.6) id gBOJA3C01206 for rmt-archive@odin.ietf.org; Tue, 24 Dec 2002 14:10:03 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBOJA3J01203 for <rmt-web-archive@optimus.ietf.org>; Tue, 24 Dec 2002 14:10:03 -0500
Received: from www1.ietf.org (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11574 for <rmt-web-archive@ietf.org>; Tue, 24 Dec 2002 14:05:31 -0500 (EST)
Received: from www1.ietf.org (localhost.localdomain [127.0.0.1]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBOJ86J01145; Tue, 24 Dec 2002 14:08:06 -0500
Received: from ietf.org (odin.ietf.org [132.151.1.176]) by www1.ietf.org (8.11.6/8.11.6) with ESMTP id gBOJ7wJ01120 for <rmt@optimus.ietf.org>; Tue, 24 Dec 2002 14:07:58 -0500
Received: from gamma.isi.edu (ietf-mx.ietf.org [132.151.6.1]) by ietf.org (8.9.1a/8.9.1a) with ESMTP id OAA11553; Tue, 24 Dec 2002 14:03:26 -0500 (EST)
Received: from ISI.EDU (jet.isi.edu [128.9.160.87]) by gamma.isi.edu (8.11.6/8.11.2) with ESMTP id gBOJ6UD11146; Tue, 24 Dec 2002 11:06:30 -0800 (PST)
Message-Id: <200212241906.gBOJ6UD11146@gamma.isi.edu>
To: IETF-Announce:;
Cc: rfc-editor@rfc-editor.org, rmt@ietf.org
From: rfc-editor@rfc-editor.org
Mime-Version: 1.0
Content-Type: Multipart/Mixed; Boundary="NextPart"
Date: Tue, 24 Dec 2002 11:06:30 -0800
Subject: [Rmt] RFC 3453 on The Use of Forward Error Correction (FEC) in Reliable Multicast
Sender: rmt-admin@ietf.org
Errors-To: rmt-admin@ietf.org
X-BeenThere: rmt@ietf.org
X-Mailman-Version: 2.0.12
Precedence: bulk
List-Unsubscribe: <https://www1.ietf.org/mailman/listinfo/rmt>, <mailto:rmt-request@ietf.org?subject=unsubscribe>
List-Id: Reliable Multicast Transport <rmt.ietf.org>
List-Post: <mailto:rmt@ietf.org>
List-Help: <mailto:rmt-request@ietf.org?subject=help>
List-Subscribe: <https://www1.ietf.org/mailman/listinfo/rmt>, <mailto:rmt-request@ietf.org?subject=subscribe>
A new Request for Comments is now available in online RFC libraries. RFC 3453 Title: The Use of Forward Error Correction in Reliable Multicast Author(s): M. Luby, L. Vicisano, J. Gemmell, L. Rizzo, M. Handley, J. Crowcroft Status: Informational Date: December 2002 Mailbox: luby@digitalfountain.com, lorenzo@cisco.com, jgemmell@microsoft.com, luigi@iet.unipi.it, mjh@aciri.org, Jon.Crowcroft@cl.cam.ac.uk Pages: 18 Characters: 46853 Updates/Obsoletes/See Also: None I-D Tag: draft-ietf-rmt-info-fec-03.txt URL: ftp://ftp.rfc-editor.org/in-notes/rfc3453.txt This memo describes the use of Forward Error Correction (FEC) codes to efficiently provide and/or augment reliability for one-to-many reliable data transport using IP multicast. One of the key properties of FEC codes in this context is the ability to use the same packets containing FEC data to simultaneously repair different packet loss patterns at multiple receivers. Different classes of FEC codes and some of their basic properties are described and terminology relevant to implementing FEC in a reliable multicast protocol is introduced. Examples are provided of possible abstract formats for packets carrying FEC. This document is a product of the Reliable Multicast Transport Working Group of the IETF. This memo provides information for the Internet community. It does not specify an Internet standard of any kind. Distribution of this memo is unlimited. This announcement is sent to the IETF list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST@IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info@RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should be addressed to either the author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless specifically noted otherwise on the RFC itself, all RFCs are for unlimited distribution.echo Submissions for Requests for Comments should be sent to RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC Authors, for further information. Joyce K. Reynolds and Sandy Ginoza USC/Information Sciences Institute ... Below is the data which will enable a MIME compliant Mail Reader implementation to automatically retrieve the ASCII version of the RFCs.