idnits 2.17.1 draft-ietf-rmt-bb-fec-07.txt: Skipping this file; it looks like a tombstone file to me. -------------------------------------------------------------------------------- 1 A new Request for Comments is now available in online RFC libraries. 3 RFC 3452 5 Title: Forward Error Correction Building Block 6 Author(s): M. Luby, L. Vicisano, J. Gemmell, L. Rizzo, 7 M. Handley, J. Crowcroft 8 Status: Experimental 9 Date: December 2002 10 Mailbox: luby@digitalfountain.com, lorenzo@cisco.com, 11 jgemmell@microsoft.com, luigi@iet.unipi.it, 12 mjh@aciri.org, Jon.Crowcroft@cl.cam.ac.uk 13 Pages: 16 14 Characters: 38368 15 Updates/Obsoletes/See Also: None 17 I-D Tag: draft-ietf-rmt-bb-fec-07.txt 19 URL: ftp://ftp.rfc-editor.org/in-notes/rfc3452.txt 21 This document generally describes how to use Forward Error Correction 22 (FEC) codes to efficiently provide and/or augment reliability for data 23 transport. The primary focus of this document is the application of 24 FEC codes to one-to-many reliable data transport using IP 25 multicast. This document describes what information is needed to 26 identify a specific FEC code, what information needs to be 27 communicated out-of-band to use the FEC code, and what information is 28 needed in data packets to identify the encoding symbols they carry. 29 The procedures for specifying FEC codes and registering them with the 30 Internet Assigned Numbers Authority (IANA) are also described. This 31 document should be read in conjunction with and uses the terminology 32 of the companion document titled, "The Use of Forward Error Correction 33 (FEC) in Reliable Multicast". 35 This document is a product of the Reliable Multicast Transport Working 36 Group of the IETF. 38 This memo defines an Experimental Protocol for the Internet community. 39 It does not specify an Internet standard of any kind. Discussion and 40 suggestions for improvement are requested. Distribution of this memo 41 is unlimited. 43 This announcement is sent to the IETF list and the RFC-DIST list. 44 Requests to be added to or deleted from the IETF distribution list 45 should be sent to IETF-REQUEST@IETF.ORG. Requests to be 46 added to or deleted from the RFC-DIST distribution list should 47 be sent to RFC-DIST-REQUEST@RFC-EDITOR.ORG. 49 Details on obtaining RFCs via FTP or EMAIL may be obtained by sending 50 an EMAIL message to rfc-info@RFC-EDITOR.ORG with the message body 51 help: ways_to_get_rfcs. For example: 53 To: rfc-info@RFC-EDITOR.ORG 54 Subject: getting rfcs 56 help: ways_to_get_rfcs 58 Requests for special distribution should be addressed to either the 59 author of the RFC in question, or to RFC-Manager@RFC-EDITOR.ORG. Unless 60 specifically noted otherwise on the RFC itself, all RFCs are for 61 unlimited distribution.echo 62 Submissions for Requests for Comments should be sent to 63 RFC-EDITOR@RFC-EDITOR.ORG. Please consult RFC 2223, Instructions to RFC 64 Authors, for further information.