Re: [dtn-interest] Question

"Ivancic, William D. (GRC-RHN0)" <william.d.ivancic@nasa.gov> Tue, 29 January 2013 16:54 UTC

Return-Path: <william.d.ivancic@nasa.gov>
X-Original-To: dtn-interest@ietfa.amsl.com
Delivered-To: dtn-interest@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 8254421F84F6 for <dtn-interest@ietfa.amsl.com>; Tue, 29 Jan 2013 08:54:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.039
X-Spam-Level:
X-Spam-Status: No, score=-4.039 tagged_above=-999 required=5 tests=[AWL=-2.440, BAYES_00=-2.599, GB_SUMOF=5, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id RVhy3UQcqwq5 for <dtn-interest@ietfa.amsl.com>; Tue, 29 Jan 2013 08:54:16 -0800 (PST)
Received: from ndmsnpf01.ndc.nasa.gov (ndmsnpf01.ndc.nasa.gov [198.117.0.121]) by ietfa.amsl.com (Postfix) with ESMTP id 7E45E21F84DC for <dtn-interest@irtf.org>; Tue, 29 Jan 2013 08:54:16 -0800 (PST)
Received: from ndjsppt02.ndc.nasa.gov (ndjsppt02.ndc.nasa.gov [198.117.1.101]) by ndmsnpf01.ndc.nasa.gov (Postfix) with ESMTP id C58662600A1; Tue, 29 Jan 2013 10:54:14 -0600 (CST)
Received: from ndjshub04.ndc.nasa.gov (ndjshub04-pub.ndc.nasa.gov [198.117.1.34]) by ndjsppt02.ndc.nasa.gov (8.14.5/8.14.5) with ESMTP id r0TGsEgP026125; Tue, 29 Jan 2013 10:54:14 -0600
Received: from NDJSSCC07.ndc.nasa.gov ([198.117.4.178]) by ndjshub04.ndc.nasa.gov ([10.202.202.163]) with mapi; Tue, 29 Jan 2013 10:54:14 -0600
From: "Ivancic, William D. (GRC-RHN0)" <william.d.ivancic@nasa.gov>
To: Daniel Ellard <dellard@bbn.com>, "dtn-interest@irtf.org" <dtn-interest@irtf.org>
Date: Tue, 29 Jan 2013 10:54:41 -0600
Thread-Topic: [dtn-interest] Question
Thread-Index: Ac39znjjdWqkTuaAQDy1i+ZvlZsZSwActvDl
Message-ID: <CD2D6901.FB02%william.d.ivancic@nasa.gov>
In-Reply-To: <51073E0E.5040807@bbn.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-Entourage/13.11.0.110726
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10432:5.9.8327, 1.0.431, 0.0.0000 definitions=2013-01-29_06:2013-01-29, 2013-01-29, 1970-01-01 signatures=0
Subject: Re: [dtn-interest] Question
X-BeenThere: dtn-interest@irtf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." <dtn-interest.irtf.org>
List-Unsubscribe: <https://www.irtf.org/mailman/options/dtn-interest>, <mailto:dtn-interest-request@irtf.org?subject=unsubscribe>
List-Archive: <http://www.irtf.org/mail-archive/web/dtn-interest>
List-Post: <mailto:dtn-interest@irtf.org>
List-Help: <mailto:dtn-interest-request@irtf.org?subject=help>
List-Subscribe: <https://www.irtf.org/mailman/listinfo/dtn-interest>, <mailto:dtn-interest-request@irtf.org?subject=subscribe>
X-List-Received-Date: Tue, 29 Jan 2013 16:54:17 -0000

I think a lot of work in reliable multicasts has foundations in tornado
codes such as digital fountain.  They may be using non-proprietary stuff
here.

http://en.wikipedia.org/wiki/Tornado_code

Interleaving helps with gaps.

That being said, most of this discussion  is related to reliable transport
(convergence layer) more so than store and forward.

Will

******************************
William D. Ivancic
Phone 216-433-3494
Fax 216-433-8705
Networking Lab 216-433-2620
Mobile 440-503-4892
http://roland.grc.nasa.gov/~ivancic



> From: Daniel Ellard <dellard@bbn.com>
> Date: Mon, 28 Jan 2013 21:12:14 -0600
> To: "dtn-interest@irtf.org" <dtn-interest@irtf.org>
> Subject: Re: [dtn-interest] Question
> 
> On 1/28/13 8:44 PM, sitaraman@nmsworks.co.in wrote:
>> I did, and my understanding is it is an erasure code  with a larger margin
>> of error allowed for the signal can be recovered from a subset of the
>> encoded signals...so it still cant handle losses?
> 
> It is correct that a "digital fountain" is an instance of a forward
> error-correcting code.
> 
> As such, it has the property that it encodes a string of data D of
> length N as a set of much smaller strings e0, e1, ..., eX such that
> the original string D can be reconstructed from any subset of e0,
> e1, ... eX if the sum of the lengths of each e in the subset is
> greater or equal to N.  (an "efficient" FEC is one such that any
> subset of length N will suffice; my recollection is that fountain
> codes are not guaranteed to be efficient, but are generally within a
> small margin of it.)  It is possible to choose an encoding method to
> make each e computable independently of the rest, and the set of all
> possible e's for a given D practically unlimited.
> 
> The sender can continuously compute and transmit e's, and as soon as
> the receiver receives enough e's, the receiver is successful.  It
> doesn't matter how many e's are lost en route (or which are lost) as
> long as enough arrive eventually.
> 
> Fountain codes are one example of a FEC with this property, but the
> last time I checked (which was a while ago, admittedly) they had two
> drawbacks: first, the efficient implementations were protected by
> patents, and second, they weren't well-described or available as
> open-source.  Perhaps that has changed.
> 
> In any case, if you want to understand the basic theory of efficient
> FECs, Rabin's "Information Dispersal Algorithm", based on polynomial
> interpolation, is a good place to start.  For implementations of
> related codes that can be implemented efficiently, James Plank's
> work on erasure codes for storage is the most practical work of
> which I am aware.
> 
> -Dan
> 
> -- 
> Daniel Ellard, Ph.D.
> Senior Scientist, Network Research
> Raytheon BBN Technologies
> dellard@bbn.com
> 
> _______________________________________________
> dtn-interest mailing list
> dtn-interest@irtf.org
> https://www.irtf.org/mailman/listinfo/dtn-interest