[dtn-interest] Communcation Patterns in DTN
sitaraman@nmsworks.co.in Sun, 27 January 2013 17: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 B167121F85FC for <dtn-interest@ietfa.amsl.com>; Sun, 27 Jan 2013 09:02:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.251
X-Spam-Level:
X-Spam-Status: No, score=-2.251 tagged_above=-999 required=5 tests=[AWL=0.348, BAYES_00=-2.599]
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 edWuf2C42BeW for <dtn-interest@ietfa.amsl.com>; Sun, 27 Jan 2013 09:02:55 -0800 (PST)
Received: from indlocal.nmsworks.co.in (nmsworks.co.in [14.140.238.3]) by ietfa.amsl.com (Postfix) with ESMTP id C9FE521F84E9 for <dtn-interest@irtf.org>; Sun, 27 Jan 2013 09:02:54 -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 r0RH0m2r014129; Sun, 27 Jan 2013 22:30:48 +0530
Received: from 115.242.217.223 (SquirrelMail authenticated user sitaraman) by www.nmsworks.co.in with HTTP; Sun, 27 Jan 2013 22:30:48 +0530 (IST)
Message-ID: <60600.115.242.217.223.1359306048.squirrel@www.nmsworks.co.in>
Date: Sun, 27 Jan 2013 22:30:48 +0530
From: sitaraman@nmsworks.co.in
To: dtn-interest@irtf.org
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: r0RH0m2r014129
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
Subject: [dtn-interest] Communcation Patterns in DTN
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: Sun, 27 Jan 2013 17:02:55 -0000
Hi, Communications can be of at least a couple of patterns, single request and single/multiple response type or a more interactive mulitple request - mulitple response type. The latter could be a challenge in DTN scenarios and may be needed in manned missons especially or interactive experiments. Would it be worthwhile investigating communications in such scenarios. Say, we could look at if responses to several response possibility to a given question be sent bundled together therefore saving time on the overall communication. The intermediate nodes could have learnt about the behavior of the destinations and could proactively request further communication from the source if the set of responses dont fit in any of the available. Wondering if some sort of "compute while commute" phiolosophy exists, that is the routers now no longer serve only the routing function but can also act as "proxies" for the destination? These however is a mixture of language processing and networking and not purely networking protocol issue... Sitaraman -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.