Forward Error Correction Fec Building Block
Univ. Pisa M. Handley ICIR J. Crowcroft Cambridge Univ. December 2002 Forward Error Correction (FEC) Building Block Status of this Memo This memo defines an Experimental Protocol for the Internet community. It does not specify an Internet standard of any kind. Discussion and suggestions for improvement are requested. Distribution of this memo is unlimited. Copyright Notice Copyright (C) The Internet Society (2002). All Rights Reserved. Abstract This document generally describes how to use Forward Error Correction (FEC) codes to efficiently provide and/or augment reliability for data transport. The primary focus of this document is the application of FEC codes to one-to-many reliable data transport using IP multicast. This document describes what information is needed to identify a specific FEC code, what information needs to be communicated out-of-band to use the FEC code, and what information is needed in data packets to identify the encoding symbols they carry. The procedures for specifying FEC codes and registering them with the Internet Assigned Numbers Authority (IANA) are also described. This document should be read in conjunction with and uses the terminology of the companion document titled, "The Use of Forward Error Correction (FEC) in Reliable Multicast". Luby, et. al. Experimental [Page 1] RFC 3452 FEC Building Block December 2002 Table of Contents 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . 2 2. Rationale. . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Functionality. . . . . . . . . . . . . . . . . . . . . . . 3 3.1 FEC Encoding ID and FEC Instance ID. . . . . . . . . . . 5 3.2 FEC Payload ID and FEC Object Transmission Information . 6 4. Applicability Statement . . . . . . . . . . . . . . . . . 7 5. Packet Header Fields . . . . . . . . . . . . .
2011 Forward Error Correction (FEC) Framework Abstract This document describes a framework for using Forward Error Correction (FEC) codes with applications in public and private IP networks to provide protection against packet loss. The framework supports applying FEC to arbitrary packet flows over unreliable transport and is primarily intended for real-time, or streaming, media. This framework can be used to define Content Delivery Protocols that provide FEC for streaming media delivery or other packet flows. Content Delivery Protocols defined using this framework can support any FEC scheme (and associated FEC codes) that is compliant with various requirements defined in this document. Thus, Content Delivery Protocols can https://tools.ietf.org/html/rfc3452 be defined that are not specific to a particular FEC scheme, and FEC schemes can be defined that are not specific to a particular Content Delivery Protocol. Status of This Memo This is an Internet Standards Track document. This document is a product of the Internet Engineering Task Force (IETF). It represents the consensus of the IETF community. It has received public review and has been approved for publication https://tools.ietf.org/html/rfc6363 by the Internet Engineering Steering Group (IESG). Further information on Internet Standards is available in Section2 of RFC 5741. Information about the current status of this document, any errata, and how to provide feedback on it may be obtained at http://www.rfc-editor.org/info/rfc6363. Watson, et al. Standards Track [Page 1] RFC 6363 FEC Framework October 2011 Copyright Notice Copyright (c) 2011 IETF Trust and the persons identified as the document authors. All rights reserved. This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (http://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Simplified BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Simplified BSD License. This document may contain material from IETF Documents or IETF Contributions published or made publicly available before November 10, 2008. The person(s) controlling the copyright in some of this material may not have granted the IETF Trust the right to allow modifications of such material outside the IETF Standards Process. Without obtaining an adeq
bulk data transfer over IP multicast. This document defines a framework for the definition of the information that needs to be communicated in order to use http://www.rfc-base.org/rfc-5052.html an FEC code for bulk data transfer, in addition to the encoded data itself, and for definition of formats and codes for communication of that information. Both information communicated with the encoded data itself and information that needs to be communicated 'out-of-band' are considered. The procedures for specifying new FEC codes, defining the information communication requirements associated with those codes and registering forward error them with the Internet Assigned Numbers Authority (IANA) are also described.The requirements on Content Delivery Protocols that wish to use FEC codes defined within this framework are also defined. The companion document titled "The Use of Forward Error Correction (FEC) in Reliable Multicast" describes some applications of FEC codes for delivering content. This document obsoletes RFC 3452. RFC 5052 introduction This forward error correction document describes how to use Forward Error Correction (FEC) codes to provide support for reliable delivery of content within the context of a Content Delivery Protocol (CDP). This document describes a building block as defined in [10], specifically Section 4.2 of that document, and follows the general guidelines provided in [5]. Download links Click here to download RFC 5052: TXT format PDF format (coming soon) Related Request for Comments RFC 3453 - The Use of Forward Error Correction (FEC) in Reliable Multicast RFC 3452 - Forward Error Correction (FEC) Building Block RFC 3269 - and Protocol Instantiation documents RFC 3048 RFC 2434 - Guidelines for Writing an IANA Considerations Section in RFCs RFC 2357 RFC 2119 - Key words for use in RFCs to Indicate Requirement Levels Popular RFCs HTTP/1.1 Protocol - RFC 2616 Uniform Resource Locator URL - RFC 1738 TCP Protocol - RFC 793 Transport Layer Security Protocol - RFC 5246 eMail - RFC 2822 SMTP Protocol - RFC 5321 SIP Protocol - RFC 3261 FTP Protocol - RFC 959 RTP Protocol - RFC 3550 ©2015 RFC-Base.org - all rights reserved.