Re: [dtn-interest] Question

Vint Cerf <vint@google.com> Mon, 28 January 2013 00:11 UTC

Return-Path: <vint@google.com>
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 F003621F866E for <dtn-interest@ietfa.amsl.com>; Sun, 27 Jan 2013 16:11:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -101.377
X-Spam-Level:
X-Spam-Status: No, score=-101.377 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, J_CHICKENPOX_43=0.6, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
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 t10D5APOh3nw for <dtn-interest@ietfa.amsl.com>; Sun, 27 Jan 2013 16:11:19 -0800 (PST)
Received: from mail-ia0-x22b.google.com (mail-ia0-x22b.google.com [IPv6:2607:f8b0:4001:c02::22b]) by ietfa.amsl.com (Postfix) with ESMTP id D77B321F8583 for <dtn-interest@irtf.org>; Sun, 27 Jan 2013 16:11:18 -0800 (PST)
Received: by mail-ia0-f171.google.com with SMTP id z13so3451556iaz.30 for <dtn-interest@irtf.org>; Sun, 27 Jan 2013 16:11:18 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=Y711BzQeTrdyz5oKqLEylu4PkfkpIqDg4jqNIKwqLRo=; b=M6u1TpsHaGT7r+5Oq3SUDaqEojlvYbGwWY/mYtP+61V4sF3eDke/Dfn20c377hHXv3 Ttv8xvxmTJgkUqaOi9vUoyAEPlKGeZaw49VRTbJfR+zoZvk9FIpkRWPtz+ocWceLXj7Q c5u1eE0ZIMguhgHZUKCsB0NGc7EfD1vU90eXoLM3RvStfeoobilCLksGZPiQ5ZKORA+E pZMlss7K/zd13V4oBUTRnddQHAM5WexHUqJymTv3kCu6yfj2197MdG9+i2/3yV7rFNhO 4/1En9dfsoUTciqFqE5F5QSqPgAdsMu9gO9daNNfM29oFchVQO3wxWmTZfD15Z9fYdTM BaYw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type:x-gm-message-state; bh=Y711BzQeTrdyz5oKqLEylu4PkfkpIqDg4jqNIKwqLRo=; b=HSMgMsmsRul9pVkJ5PkjFCkz3LSpYgtwjJawYZZP0z3NCmspZ6qXFd6nhMnpRywCrs ggmqEK0DQxlMht56tFQ1RKiUrGMSUt2jsctlMpfQ2ZGTfWY7UVT240FXwlDXH+VPepeU 2WSLvhbaJl5S9p6Xeh4vBEhM6o1xS7K2bFbRXZmL52GgBUzMmAAQ9ukbSP8cG6AlSiuK Rc13O2zzQKpeDn5giGl7lw2631ulBMW5XLfAp8MQPkUhO29qqtJP6e2H+4jyek/piPA1 HPAAjR3e84icTerWYmHgR/7634NNPKArCf5NjrZM9JtInHsRN30MRL57bUfl8usPB4nt qC4A==
MIME-Version: 1.0
X-Received: by 10.42.202.84 with SMTP id fd20mr7747531icb.20.1359331878036; Sun, 27 Jan 2013 16:11:18 -0800 (PST)
Received: by 10.231.92.65 with HTTP; Sun, 27 Jan 2013 16:11:17 -0800 (PST)
In-Reply-To: <64406.115.242.217.223.1359331248.squirrel@www.nmsworks.co.in>
References: <60540.115.242.217.223.1359305486.squirrel@www.nmsworks.co.in> <A5BEAD028815CB40A32A5669CF737C3B23574324@ap-embx-sp40.RES.AD.JPL> <64406.115.242.217.223.1359331248.squirrel@www.nmsworks.co.in>
Date: Sun, 27 Jan 2013 19:11:17 -0500
Message-ID: <CAHxHggdt4MgK4Uwro6gXrrr+aqgkzGRpmwo8_1zFDYn0Z9DQhQ@mail.gmail.com>
From: Vint Cerf <vint@google.com>
To: sitaraman@nmsworks.co.in
Content-Type: multipart/alternative; boundary="20cf300e5323b8e48104d44e1d97"
X-Gm-Message-State: ALoCoQlp3N7L/AwlQa7k+o8jVQEZmD1l3a8Br/+SZQcn0g7tJ/jPtb0iBPx/fUqEAm6wKAIseb/ho7WLnpYDrDWcZZFnNlLxWVFkrQ3Z+ee2XExzxkSj+G0i8ZQC2DLZxYqCbfTdtkrvLMEe0ULjuFS9v7JiawMVCrJBp+DzhXUf9feMocwuQSZx0w89oQba1mtk/A7U4yzb
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:11:20 -0000

If it is 10s of days and there are no intermediate nodes, you are talking
about a long-delay one-hop link. This is what the Deep Space Network has to
deal with all the time. Forward error correction is your friend in these
cases. Repeated transmissions are possible but for systems like the DSN,
you only get to point to the destination at certain times (when "contact"
is feasible and when you are scheduled to transmit or receive - it is a
huge scheduling challenge since the DSN resource is potentially
over-subscribed). If the probability of loss is relatively low except for
noise, forward error correction may be enough to reduce loss probability in
which case one would not retransmit until no response is obtained after the
round trip time has expired. One of the reasons the IPN is attractive is
that it can position messages closer to destination and recover from
forward hop failures more quickly.

Your scenario of "packet loss" in 4 days on a one hop link is a bit weird
because you can't conclude loss until the signal gets to the receiver.

v



On Sun, Jan 27, 2013 at 7:00 PM, <sitaraman@nmsworks.co.in> wrote:

> 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.
>
> _______________________________________________
> dtn-interest mailing list
> dtn-interest@irtf.org
> https://www.irtf.org/mailman/listinfo/dtn-interest
>