Re: [dtn-interest] FW: Results of IETF-conflict review for draft-irtf-dtnrg-tcp-clayer-08

"Burleigh, Scott C (312G)" <> Tue, 25 February 2014 16:10 UTC

Return-Path: <>
Received: from localhost ( []) by (Postfix) with ESMTP id 72A901A00B4 for <>; Tue, 25 Feb 2014 08:10:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at
X-Spam-Flag: NO
X-Spam-Score: -4.746
X-Spam-Status: No, score=-4.746 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, RP_MATCHES_RCVD=-0.547] autolearn=ham
Received: from ([]) by localhost ( []) (amavisd-new, port 10024) with ESMTP id zh9aDhTBMrVX for <>; Tue, 25 Feb 2014 08:10:13 -0800 (PST)
Received: from ( []) by (Postfix) with ESMTP id 1D6051A0174 for <>; Tue, 25 Feb 2014 08:10:11 -0800 (PST)
Received: from ( []) by (Sentrion-MTA-4.3.1/Sentrion-MTA-4.3.1) with ESMTP id s1PG9kAG021132 (using TLSv1/SSLv3 with cipher AES128-SHA (128 bits) verified NO); Tue, 25 Feb 2014 08:09:48 -0800
Received: from AP-EMBX-SP40.RES.AD.JPL ([]) by ap-ehub-sp02.RES.AD.JPL ([fe80::dd85:7b07:1e36:7e3c%15]) with mapi id 14.03.0174.001; Tue, 25 Feb 2014 08:10:06 -0800
From: "Burleigh, Scott C (312G)" <>
To: "Ivancic, William D. (GRC-RHN0)" <>, Vint Cerf <>, "" <>
Thread-Topic: [dtn-interest] FW: Results of IETF-conflict review for draft-irtf-dtnrg-tcp-clayer-08
Thread-Index: AQHPMgbXZ/gRhpbuR0u4CAYMrZe3iZrGOYYAgAAEewCAAEZ+AP//lmag
Date: Tue, 25 Feb 2014 16:10:05 +0000
Message-ID: <A5BEAD028815CB40A32A5669CF737C3B422FFBD4@ap-embx-sp40.RES.AD.JPL>
References: <> <>
In-Reply-To: <>
Accept-Language: en-US
Content-Language: en-US
x-originating-ip: []
Content-Type: multipart/alternative; boundary="_000_A5BEAD028815CB40A32A5669CF737C3B422FFBD4apembxsp40RESAD_"
MIME-Version: 1.0
X-AUTH: Authorized
Cc: dtn-interest <>
Subject: Re: [dtn-interest] FW: Results of IETF-conflict review for draft-irtf-dtnrg-tcp-clayer-08
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "The Delay-Tolerant Networking Research Group \(DTNRG\) - Announce." <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Tue, 25 Feb 2014 16:10:17 -0000

DTN has been in (limited) operational use on the International Space Station since 2009, conveying data from on-board biology experiments to a lab at the University of Colorado, Boulder.  DTN will become part of the operational infrastructure of ISS, available for use by all payload systems, sometime in 2015 when ISS change request 013799 is completed.

Will, you are correct that the tests of DTN over laser comm were among DTN nodes residing in machines on the ground: each bundle was sent from one bundle protocol agent via the laser link to the satellite and echoed (at link layer) back down to another BPA on Earth.  The bundles traversed cislunar distance, but there was no bundle protocol agent on the satellite.


From: dtn-interest [] On Behalf Of Ivancic, William D. (GRC-RHN0)
Sent: Tuesday, February 25, 2014 5:55 AM
To: Vint Cerf;
Cc: dtn-interest
Subject: Re: [dtn-interest] FW: Results of IETF-conflict review for draft-irtf-dtnrg-tcp-clayer-08

Are there any known "Operational" deployments of DTN?  I no NASA is investigating DTN, be we still do not have what I would call an Operational deployment.

Also, LTE is a connected network.  How would DTN help here?  Dropbox and email work pretty well in this situation as does text messaging and even voice conversations (with voice mail when disconnected).

Note, to the best of my knowledge, there was no high-rate DTN deployed on the Lunar Laser Communication Demonstration (LLCD).  Rather, DTN was sent over the link from one ground DTN agent to another.  I'm not sure at what rate.

William D. Ivancic
Phone 216-433-3494
Fax 216-433-8705
Networking Lab 216-433-2620
Mobile 440-503-4892

From: Vint Cerf <<>>
Date: Tuesday, February 25, 2014 4:43 AM
To: "<>" <<>>
Cc: dtn-interest <<>>
Subject: Re: [dtn-interest] FW: Results of IETF-conflict review for draft-irtf-dtnrg-tcp-clayer-08

there is a lot more TCP and IP network readily available than others so, statistically, this is not a surprise. I anticipate that LTE may prove another supporting environment. Of course, there continues to be work in deep space such as the latest laser comm tests to/from the moon at 600 Mb/s.


On Tue, Feb 25, 2014 at 4:27 AM, <<>> wrote:

the impression I've gained is that most bundle protocol use is over TCP - that is,
rather than being a compatibility mechanism, TCP is the dominant transport for the
bundle protocol.

Are there any statistics or metrics of use that can shed light here?


Lloyd Wood
From: Vint Cerf [<>]
Sent: 25 February 2014 08:51
To: Wood L  Dr (Electronic Eng)
Cc: dtn-interest
Subject: Re: [dtn-interest] FW: Results of IETF-conflict review for draft-irtf-dtnrg-tcp-clayer-08

This makes it possible to support applications end to end over DTN including the Internet.
It is a compatibility mechanism.


On Tue, Feb 25, 2014 at 3:23 AM, <<><<>>> wrote:
Congratulations to  DTNRG on reaching the below milestone in getting
this draft well on the way to being published.

It's been a long delay since draft-demmer-dtnrg-tcp-clayer-00.txt in October
2006, but defining how the bundle protocol is carried over TCP will go a long
way to improving support for networked communications under the very
difficult disrupted and delay-tolerant network conditions when TCP break...
um. Ah.

Lloyd Wood
From: IETF-Announce [<><<>>] On Behalf Of The IESG [<><<>>]
Sent: 24 February 2014 17:40
To: Lars Eggert;<><<>>;<><<>>
Cc:<><<>>; The IESG;<><<>>
Subject: Results of IETF-conflict review for draft-irtf-dtnrg-tcp-clayer-08

The IESG has completed a review of draft-irtf-dtnrg-tcp-clayer-08
consistent with RFC5742.

The IESG has no problem with the publication of 'Delay Tolerant
Networking TCP Convergence Layer Protocol'
<draft-irtf-dtnrg-tcp-clayer-08.txt> as an Experimental RFC.

The IESG has concluded that there is no conflict between this document
and IETF work.

The IESG would also like the IRTF to review the comments in the
datatracker related to this document and determine whether or not they
merit incorporation into the document. Comments may exist in both the
ballot and the history log.

The IESG review is documented at:

A URL of the reviewed Internet Draft is:

The process for such documents is described in RFC 5743

Thank you,

The IESG Secretary

dtn-interest mailing list<><<>>