Re: [dtn-interest] RG "last call" on draft-irtf-dtnrg-cbhe

"Eddy, Wesley M. (GRC-RCN0)[Verizon]" <wesley.m.eddy@nasa.gov> Wed, 11 March 2009 13:57 UTC

Received: from ndmsnpf01.ndc.nasa.gov (ndmsnpf01.ndc.nasa.gov [198.117.0.121]) by maillists.intel-research.net (8.13.8/8.13.8) with ESMTP id n2BDv8K6012714 for <dtn-interest@mailman.dtnrg.org>; Wed, 11 Mar 2009 06:57:08 -0700
Received: from ndjsppt03.ndc.nasa.gov (ndjsppt03.ndc.nasa.gov [198.117.1.102]) by ndmsnpf01.ndc.nasa.gov (Postfix) with ESMTP id AA57394F9; Wed, 11 Mar 2009 08:39:11 -0500 (CDT)
Received: from ndjshub02.ndc.nasa.gov (ndjshub02.ndc.nasa.gov [198.117.4.161] (may be forged)) by ndjsppt03.ndc.nasa.gov (8.14.1/8.14.1) with ESMTP id n2BDd42t032475; Wed, 11 Mar 2009 08:39:14 -0500
Received: from NDJSSCC01.ndc.nasa.gov ([198.117.4.166]) by ndjshub02.ndc.nasa.gov ([198.117.4.161]) with mapi; Wed, 11 Mar 2009 08:39:11 -0500
From: "Eddy, Wesley M. (GRC-RCN0)[Verizon]" <wesley.m.eddy@nasa.gov>
To: "L.Wood@surrey.ac.uk" <L.Wood@surrey.ac.uk>, "stephen.farrell@cs.tcd.ie" <stephen.farrell@cs.tcd.ie>
Date: Wed, 11 Mar 2009 08:38:17 -0500
Thread-Topic: [dtn-interest] RG "last call" on draft-irtf-dtnrg-cbhe
Thread-Index: Acmh2kY4KqtSXxeXRROmpemFL5jRjgAH+Z7rABS4AWA=
Message-ID: <C304DB494AC0C04C87C6A6E2FF5603DB220C9F0032@NDJSSCC01.ndc.nasa.gov>
References: <49B01FCB.2010405@cs.tcd.ie> <49B6F6F6.8040209@cs.tcd.ie> <4835AFD53A246A40A3B8DA85D658C4BE7B0F28@EVS-EC1-NODE4.surrey.ac.uk>
In-Reply-To: <4835AFD53A246A40A3B8DA85D658C4BE7B0F28@EVS-EC1-NODE4.surrey.ac.uk>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by maillists.intel-research.net id n2BDv8K6012714
Cc: "dtn-interest@mailman.dtnrg.org" <dtn-interest@mailman.dtnrg.org>
Subject: Re: [dtn-interest] RG "last call" on draft-irtf-dtnrg-cbhe
X-BeenThere: dtn-interest@maillists.intel-research.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Delay Tolerant Networking Interest List <dtn-interest.maillists.intel-research.net>
List-Unsubscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-interest>, <mailto:dtn-interest-request@maillists.intel-research.net?subject=unsubscribe>
List-Archive: <http://maillists.intel-research.net/pipermail/dtn-interest>
List-Post: <mailto:dtn-interest@maillists.intel-research.net>
List-Help: <mailto:dtn-interest-request@maillists.intel-research.net?subject=help>
List-Subscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-interest>, <mailto:dtn-interest-request@maillists.intel-research.net?subject=subscribe>
X-List-Received-Date: Wed, 11 Mar 2009 13:57:09 -0000

>-----Original Message-----
>From: dtn-interest-bounces@maillists.intel-research.net 
>[mailto:dtn-interest-bounces@maillists.intel-research.net] On 
>Behalf Of L.Wood@surrey.ac.uk
>Sent: Tuesday, March 10, 2009 11:48 PM
>
>> #0, I guess I'm left wondering if this is the only spec 
>needed to implement a
>> CL for space DTNs? If so, cool. If not, would it be better 
>if it were?
>
>Stephen,
>
>weren't you in Minneapolis, where two very different 
>approaches to space DTNs
>and implementations, using two different convergence layers - 
>based on LTP
>(over CFDP over CCSDS) and based on Saratoga (over UDP/IP over HDLC) -
>were presented, based on actual in-space testing results?
>
>http://tools.ietf.org/html/draft-wood-dtnrg-saratoga
>
>The presentations there are a clear indication that more than 
>the cbhe spec
>is needed to implement a convergence layer for space.
>
>Perhaps you could look at finalising the meeting minutes 
>(draft not archived) or
>finalising the proceedings of the Minneapolis meeting (draft very hard
>to find) to refresh your memory.
>


I don't think this RG should be worrying about "space DTNs" and
trying to tailor for them ... there are other groups actively
doing that, and the discussion should be taken to them, in my
opinion.

I think the root problem here is just that "space DTNs" aren't
some homogenous class of DTNs.  The requirements for unmanned
near-Earth versus deep space are different, and when you factor
in the envisioned lunar scenarios with more ad-hoc connectivity
and richer options for infrastructure, the requirements and
assumptions are MUCH different.  It's like saying you're doing
something for "wireless links" without specifying if you mean
low-rate/low-power PAN, free-space optical, cellular, etc;
unproductively unspecific.

CBHE may be useful in the broader set of DTNs that contain links
with either constrained bandwidth or very short contact times,
which includes underwater/submarine (at least) in addition to
deep space.  Since it may be applicable in multiple domains, it
makes sense to me to publish it from DTNRG, but it will only
greatly confuse matters if we say we're doing it for "space DTNs";
instead focus on the properties of links/networks that it's an
optimization for.

---------------------------
Wes Eddy
Network & Systems Architect
Verizon FNS / NASA GRC
Office: (216) 433-6682
---------------------------