Raptor Forward Error Correction Scheme For Object Delivery
Contents |
Research October 2007 Raptor Forward Error Correction Scheme for Object Delivery Status of This Memo 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. Abstract This document describes a Fully-Specified Forward Error Correction (FEC) scheme, corresponding to FEC Encoding ID 1, for the Raptor forward error
Raptor Code Tutorial
correction code and its application to reliable delivery of data objects. Raptor is a fountain code, i.e., as many encoding symbols as needed raptorq implementation can be generated by the encoder on-the-fly from the source symbols of a source block of data. The decoder is able to recover the source block from any set of encoding symbols only slightly more raptorq forward error correction scheme for object delivery in number than the number of source symbols. The Raptor code described here is a systematic code, meaning that all the source symbols are among the encoding symbols that can be generated. Luby, et al. Standards Track [Page 1] RFC 5053 Raptor FEC Scheme October 2007 Table of Contents 1. Introduction . . . . . . .
Raptorq Qualcomm
. . . . . . . . . . . . . . . . . . 3 2. Requirements Notation . . . . . . . . . . . . . . . . . . . . 3 3. Formats and Codes . . . . . . . . . . . . . . . . . . . . . . 3 3.1. FEC Payload IDs . . . . . . . . . . . . . . . . . . . . . 3 3.2. FEC Object Transmission Information (OTI) . . . . . . . . 4 3.2.1. Mandatory . . . .
Rfc 6330
. . . . . . . . . . . . . . . . . . 4 3.2.2. Common . . . . . . . . . . . . . . . . . . . . . . . . 4 3.2.3. Scheme-Specific . . . . . . . . . . . . . . . . . . . 5 4. Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4.1. Content Delivery Protocol Requirements . . . . . . . . . . 5 4.2. Example Parameter Derivation Algorithm . . . . . . . . . . 6 5. Raptor FEC Code Specification . . . . . . . . . . . . . . . . 8 5.1. Definitions, Symbols, and Abbreviations . . . . . . . . . 8 5.1.1. Definitions . . . . . . . . . . . . . . . . . . . . . 8 5.1.2. Symbols . . . . . . . . . . . . . . . . . . . . . . . 9 5.1.3. Abbreviations . . . . . . . . . . . . . . . . . . . . 11 5.2. Overview . . . . . . . . . . . . . . . . . . . . . . . . . 11 5.3. Object Delivery . . . . . . . . . . . . . . . . . . . . . 12 5.3.1. Source Block Construction . . . . . . . . . . . . . . 12 5.3.2. Encoding Packet Construction . . . . . . . . . . . . . 14 5.4. Systematic Raptor Encoder . . . . . . . . . . . . . .
Server Failure: The name server was unable to process http://www.rfc-base.org/rfc-5053.html this query. This means that the cache was not able to resolve the hostname presented in the URL. Check if the address is correct. Your cache administrator is webmaster. Generated Tue, 25 Oct 2016 19:01:38 GMT by s_nt6 (squid/3.5.20)
Service Registration for Instant Messaging (IM) Services Next message: [rfc-dist] RFC 5051 on i; unicode-casemap - Simple Unicode Collation Algorithm Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] A https://www.rfc-editor.org/pipermail/rfc-dist/2007-October/001780.html new Request for Comments is now available in online RFC libraries. RFC 5053 Title: Raptor Forward Error Correction Scheme for Object Delivery Author: M. Luby, A. Shokrollahi, M. Watson, T. Stockhammer Status: Standards Track Date: October 2007 Mailbox: luby at digitalfountain.com, amin.shokrollahi at epfl.ch, mark at digitalfountain.com, stockhammer at nomor.de Pages: 46 Characters: 113743 Updates/Obsoletes/SeeAlso: None I-D Tag: draft-ietf-rmt-bb-fec-raptor-object-09.txt URL: http://www.rfc-editor.org/rfc/rfc5053.txt This document describes a Fully-Specified Forward forward error Error Correction (FEC) scheme, corresponding to FEC Encoding ID 1, for the Raptor forward error correction code and its application to reliable delivery of data objects. Raptor is a fountain code, i.e., as many encoding symbols as needed can be generated by the encoder on-the-fly from the source symbols of a source block of data. The decoder is able to recover the source block from any set of forward error correction encoding symbols only slightly more in number than the number of source symbols. The Raptor code described here is a systematic code, meaning that all the source symbols are among the encoding symbols that can be generated. [STANDARDS TRACK] This document is a product of the Reliable Multicast Transport 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 list and the RFC-DIST list. Requests to be added to or deleted from the IETF distribution list should be sent to IETF-REQUEST at IETF.ORG. Requests to be added to or deleted from the RFC-DIST distribution list should be sent to RFC-DIST-REQUEST at RFC-EDITOR.ORG. Details on obtaining RFCs via FTP or EMAIL may be obtained by sending an EMAIL message to rfc-info at RFC-EDITOR.ORG with the message body help: ways_to_get_rfcs. For example: To: rfc-info at RFC-EDITOR.ORG Subject: getting rfcs help: ways_to_get_rfcs Requests for special distribution should b