Re: [dtn-interest] Question

sitaraman@nmsworks.co.in Mon, 28 January 2013 00:02 UTC

Return-Path: <sitaraman@nmsworks.co.in>
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 90D6E21F86EA for <dtn-interest@ietfa.amsl.com>; Sun, 27 Jan 2013 16:02:59 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.99
X-Spam-Level:
X-Spam-Status: No, score=-1.99 tagged_above=-999 required=5 tests=[AWL=0.009, BAYES_00=-2.599, J_CHICKENPOX_43=0.6]
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 BmsnWRuzTKke for <dtn-interest@ietfa.amsl.com>; Sun, 27 Jan 2013 16:02:58 -0800 (PST)
Received: from indlocal.nmsworks.co.in (nmsworks.co.in [14.140.238.3]) by ietfa.amsl.com (Postfix) with ESMTP id 7EB4E21F84DE for <dtn-interest@irtf.org>; Sun, 27 Jan 2013 16:02:58 -0800 (PST)
Received: from www.nmsworks.co.in (localhost [127.0.0.1]) by indlocal.nmsworks.co.in (8.13.8/8.13.8) with ESMTP id r0S00liD020498; Mon, 28 Jan 2013 05:30:48 +0530
Received: from 115.242.217.223 (SquirrelMail authenticated user sitaraman) by www.nmsworks.co.in with HTTP; Mon, 28 Jan 2013 05:30:48 +0530 (IST)
Message-ID: <64406.115.242.217.223.1359331248.squirrel@www.nmsworks.co.in>
In-Reply-To: <A5BEAD028815CB40A32A5669CF737C3B23574324@ap-embx-sp40.RES.AD.JPL>
References: <60540.115.242.217.223.1359305486.squirrel@www.nmsworks.co.in> <A5BEAD028815CB40A32A5669CF737C3B23574324@ap-embx-sp40.RES.AD.JPL>
Date: Mon, 28 Jan 2013 05:30:48 +0530
From: sitaraman@nmsworks.co.in
To: "Burleigh, Scott C (313B)" <scott.c.burleigh@jpl.nasa.gov>
User-Agent: SquirrelMail/1.0
MIME-Version: 1.0
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit
X-Priority: 3 (Normal)
Importance: Normal
X-NMSWorks-MailScanner-Information: Please contact the ISP for more information
X-NMSWorks-MailScanner-ID: r0S00liD020498
X-NMSWorks-MailScanner: Found to be clean
X-NMSWorks-MailScanner-SpamCheck: not spam (whitelisted), SpamAssassin (not cached, score=-2.9, required 4, autolearn=not spam, ALL_TRUSTED -1.00, BAYES_00 -1.90)
X-NMSWorks-MailScanner-From: sitaraman@nmsworks.co.in
Cc: "dtn-interest@irtf.org" <dtn-interest@irtf.org>
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: Mon, 28 Jan 2013 00:02:59 -0000

Hi Scott,
 Thanks for the help in understanding all this. I still have a question in
mind. For arguments sake consider the scenario where it takes 10s of days
for message to reach from source to destination and there is no
intermediate node. (If i understood Vint right the other day in the talk
at Chennai,  this is on the works for messages to a star ion pumps and
all! so hoping this is still a relevant case)Say a packet loss happens 4
days down the road. How long would the source wait to decide to resend
from its store?
Sitaraman
> Hi, Sitaraman.  It's correct to state that DTN is based on potentially
> prolonged, potentially non-volatile storage at forwarding points (the
> original source and all routers along the end-to-end path) and on
> potential retransmission at all forwarding points.
>
> But forwarding points other than the original source are features of
> specific topologies, not mandatory elements of the architecture.
> Disruption in communication between the endpoints of a long-delay
> source-destination pair is handled by storage and retransmission, both at
> the source and also at whatever other nodes may be involved in the
> communication.  Intermediate nodes are not required in order to make DTN
> work.
>
> For example, in the DINET experiment in 2008 we did DTN communication
> between nodes on Earth and a node aboard the Deep Impact flyby spacecraft
> in interplanetary space, 10-15 million miles away.  There were disruptions
> -- lapses in connectivity -- lasting several days, but DTN had no
> difficulty handling them despite the fact that there were no intermediate
> nodes between the spacecraft and the data sources and sinks on Earth.
>
> Scott
>
> -----Original Message-----
> From: dtn-interest-bounces@irtf.org [mailto:dtn-interest-bounces@irtf.org]
> On Behalf Of sitaraman@nmsworks.co.in
> Sent: Sunday, January 27, 2013 8:51 AM
> To: dtn-interest@irtf.org
> Subject: [dtn-interest] Question
>
> Hi,
>  Is it correct to state that DTN adopts a store and forward mechansim and
> gets around delay and disruption by having intermediate nodes retransmit
> on failure indication from its immediate neighbor? If this is true is it
> correct to state that fundamentally, the problem of disruption in long
> delay source-destination pair is not handled, but is solved by
> essentially reducing the said distance by having intermediate nodes
> storing and forwarding thereby acting as a "virtual" or "proxy" source
> and destinations?
>  Thanks
> Sitaraman
>
>
> --
> This message has been scanned for viruses and dangerous content by
> MailScanner, and is believed to be clean.
>
> _______________________________________________
> dtn-interest mailing list
> dtn-interest@irtf.org
> https://www.irtf.org/mailman/listinfo/dtn-interest
>
> --
> This message has been scanned for viruses and
> dangerous content by MailScanner, and is
> believed to be clean.
>
>



-- 
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.