Simple Forward Error Correction (FEC) Schemes
draft-luby-rmt-bb-fec-supp-simple-00
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Michael Luby | ||
| Last updated | 2004-06-08 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
This document introduces some Forward Error Correction (FEC) schemes that supplement the FEC schemes described in RFC 3452 [4] and RFC 3695 [5]. The primary benefits of these additional FEC schemes are that they are designed for reliable bulk delivery of objects using a simpler FEC Payload ID, and in particular they can be used to deliver objects without using any explicit source block structure. Thus, they allow simpler delivery with less packet header overhead.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)