Skip to main content

Bundle Protocol Erasure Coding Extension
draft-zinky-dtnrg-erasure-coding-extension-00

Document Type Expired Internet-Draft (individual)
Expired & archived
Authors John Zinky , Armando L. Caro , Gregory Stein
Last updated 2013-02-24 (Latest revision 2012-08-23)
Replaces draft-irtf-dtnrg-zinky-erasure-coding-extension
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 describes an extension to the Delay and Disruption Tolerant Networking (DTN) Bundle Protocol specification [RFC5050] which describes a protocol that enables the transfer of relatively large Data Objects over disrupted networks. The Erasure Coding Extension is a mechanism that extends the ability of the existing DTN bundle fragmentation mechanism to handle situations where bundles have a high probability of being dropped. An example use case is a situation where no communication contact period will ever be long enough to send the whole Data Object. In this case the object must be partitioned into smaller chunks and these chunks are sent in multiple bundles. The Erasure Coding Extension provides a recovery mechanism that allows many of these bundles to be dropped and still allow the whole Data Object to be successfully sent. This document describes an Erasure Coding Extension Block and a framework for integrating Forward Error Correction (FEC) into the bundle protocol. The Erasure Coding Extension is designed to support multiple FEC schemes and content object types. This is the framework document for a series of documents about erasure coding for DTN. Companion documents describe specific FEC schemes [RandBinary] and specific Data Object types [EcObjects].

Authors

John Zinky
Armando L. Caro
Gregory Stein

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)