
Received: from gateway0.EECS.Berkeley.EDU (gateway0.EECS.Berkeley.EDU [169.229.60.93]) by maillists.intel-research.net (8.13.8/8.13.7) with ESMTP id m1KNrwu3002979 for <dtn-users@mailman.dtnrg.org>; Wed, 20 Feb 2008 15:53:59 -0800
Received: from zabar.research.intel-research.net (bldmz-nat-161-164.berkeley.intel-research.net [12.155.161.164]) (authenticated bits=0) by gateway0.EECS.Berkeley.EDU (8.14.2/8.13.5) with ESMTP id m1KNuA0N016439 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 20 Feb 2008 15:56:11 -0800 (PST)
Message-Id: <868CC648-9D71-48E4-9AE2-BAC46FE1B703@cs.berkeley.edu>
From: Michael Demmer <demmer@cs.berkeley.edu>
To: dtn-users <dtn-users@mailman.dtnrg.org>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
X-Applemailsentby: demmer
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 20 Feb 2008 15:56:04 -0800
X-Mailer: Apple Mail (2.919.2)
Subject: [dtn-users] new branches in mercurial tree(s)
X-BeenThere: dtn-users@mailman.dtnrg.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dtn-users mailing list <dtn-users@mailman.dtnrg.org>
List-Id: dtn-users mailing list <dtn-users.mailman.dtnrg.org>
List-Unsubscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-users>, <mailto:dtn-users-request@mailman.dtnrg.org?subject=unsubscribe>
List-Archive: <http://maillists.intel-research.net/pipermail/dtn-users>
List-Post: <mailto:dtn-users@mailman.dtnrg.org>
List-Help: <mailto:dtn-users-request@mailman.dtnrg.org?subject=help>
List-Subscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-users>, <mailto:dtn-users-request@mailman.dtnrg.org?subject=subscribe>
X-List-Received-Date: Wed, 20 Feb 2008 23:54:00 -0000

I've recently updated the DTN2 mercurial source tree with some  
branches and figured it warranted a heads-up to the people on the list.

First, DTN2, the 'session' branch contains initial support for a DTN  
session layer as a framework to implement pull-based DTN applications,  
i.e. where an application requests content that is then generated on- 
demand as opposed to having a sender always pushing the content. The  
current implementation supports both unicast and multicast sessions,  
but is quite limited.

Second, in oasys and DTN2, the 'apr-port' branch contains the  
beginnings of a rework of oasys to use the apache portable runtime  
library and thereby make a future port of the DTN software to Windows.

Feel free to email me off-list if you have questions about the above  
or any problems working with mercurial and branches.

-m


Received: from blv-smtpout-01.boeing.com (blv-smtpout-01.boeing.com [130.76.32.69]) by maillists.intel-research.net (8.13.8/8.13.7) with ESMTP id m1C0Th9m022254 for <dtn-users@mailman.dtnrg.org>; Mon, 11 Feb 2008 16:29:43 -0800
Received: from slb-av-01.boeing.com (slb-av-01.boeing.com [129.172.13.4]) by blv-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id m1C0Ue84008939 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for <dtn-users@mailman.dtnrg.org>; Mon, 11 Feb 2008 16:30:50 -0800 (PST)
Received: from slb-av-01.boeing.com (localhost [127.0.0.1]) by slb-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id m1C0UeWv007534 for <dtn-users@mailman.dtnrg.org>; Mon, 11 Feb 2008 16:30:40 -0800 (PST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by slb-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id m1C0Udhb007494 for <dtn-users@mailman.dtnrg.org>; Mon, 11 Feb 2008 16:30:40 -0800 (PST)
Received: from XCH-NW-8V2.nw.nos.boeing.com ([130.247.55.70]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830);  Mon, 11 Feb 2008 16:30:39 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Mon, 11 Feb 2008 16:30:12 -0800
Message-ID: <7770DA26FD19034E9CEB45ED93620C55067431AB@XCH-NW-8V2.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: End-To-End Delivery Receipt Problem Using dtncp and dtncpd
Thread-Index: Achq1LAvWGpJMtv/QHOO94Kgchs/xACNc6Kg
From: "Smith, Brian J" <Brian.J.Smith4@boeing.com>
To: <dtn-users@mailman.dtnrg.org>
X-OriginalArrivalTime: 12 Feb 2008 00:30:39.0227 (UTC) FILETIME=[7E1404B0:01C86D0E]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by maillists.intel-research.net id m1C0Th9m022254
Subject: [dtn-users] End-To-End Delivery Receipt Problem Using dtncp and dtncpd
X-BeenThere: dtn-users@mailman.dtnrg.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dtn-users mailing list <dtn-users@mailman.dtnrg.org>
List-Id: dtn-users mailing list <dtn-users.mailman.dtnrg.org>
List-Unsubscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-users>, <mailto:dtn-users-request@mailman.dtnrg.org?subject=unsubscribe>
List-Archive: <http://maillists.intel-research.net/pipermail/dtn-users>
List-Post: <mailto:dtn-users@mailman.dtnrg.org>
List-Help: <mailto:dtn-users-request@mailman.dtnrg.org?subject=help>
List-Subscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-users>, <mailto:dtn-users-request@mailman.dtnrg.org?subject=subscribe>
X-List-Received-Date: Tue, 12 Feb 2008 00:29:44 -0000

I did some more investigation, and I think I've solved my problem.  I
block and wait for a receipt to be delivered with dtn_recv(...).  If a
receipt is delivered, compare the receipt destination URI and the bundle
source destination URI, if they don't match then I loop, blocking and
waiting for a receipt to be delivered until the receipt destination URI
equals the bundle source destination URI.  The important thing is to
make sure that the bundle source destination URI is always unique.  I
cut and pasted an excerpt from the dtncp.c source file below.  In
hindsight it appears that Michael answered this question in the response
to my question last month, "How to Differentiate Bundle Reception,
Bundle Forwarding, and End-To-End Delivery Receipts", by using different
EID's to parse message receipts.  Doh!  Sorry about that.

...

if (delivery_receipts)
{
    memset(&reply_spec, 0, sizeof(reply_spec));
    memset(&reply_payload, 0, sizeof(reply_payload));

   // now we block waiting for the echo reply
   if ((ret = dtn_recv(handle, &reply_spec, DTN_PAYLOAD_MEM,
&reply_payload, -1)) < 0)
   {
      fprintf(stderr, "error getting reply: %d (%s)\n", ret,
dtn_strerror(dtn_errno(handle)));
     exit(1);
   }

   // My modification starts here
   printf("reply_spec.dest.uri: %s\n", reply_spec.dest.uri);
   printf("bundle_spec.source.uri: %s\n", bundle_spec.source.uri);

   while(strcmp(reply_spec.dest.uri, bundle_spec.source.uri) != 0)
   {
      // now we block waiting for the echo reply
      if ((ret = dtn_recv(handle, &reply_spec, DTN_PAYLOAD_MEM,
&reply_payload, -1)) < 0)
      {
            fprintf(stderr, "error getting reply: %d (%s)\n", ret,
dtn_strerror(dtn_errno(handle)));
            exit(1);
      }
   	printf("reply_spec.dest.uri: %s\n", reply_spec.dest.uri);
   	printf("bundle_spec.source.uri: %s\n", bundle_spec.source.uri);
   }
   // My modification ends here

...

______________________________________________ 
From: 	Smith, Brian J  
Sent:	Friday, February 08, 2008 8:32 PM
To:	'dtn-users@mailman.dtnrg.org'
Cc:	Smith, Brian J
Subject:	End-To-End Delivery Receipt Problem Using dtncp and
dtncpd

I'm having some trouble figuring out which end-to-end delivery receipts
correspond to a particular bundle.  I have four computers with DTN
installed on them.  I use the first computer <DTN_HOST1> to send out
three different bundles using three separate instances of dtncp.  The
other three computers <DTN_HOST2>, <DTN_HOST3>, and <DTN_HOST4> have the
dtncpd daemon running on them waiting for bundles to be delivered. I
send out three bundles with end-to-end delivery receipt flags set using
dtncp from <DTN_HOST1> to the other three computers running dtncpd
<DTN_HOST2>, <DTN_HOST3>, and <DTN_HOST4>.  The first two DTN
destinations <DTN_HOST2> and <DTN_HOST3> are not currently reachable
from <DTN_HOST1>, so the bundles are stored locally and those instances
of dtncp block waiting for an end-to-end delivery receipt.  I then send
out the third bundle to <DTN_HOST4> which is reachable.  At this point
all four dtncp instances on <DTN_HOST1> exit and claim to have received
end-to-end delivery receipts, even though the first two bundles have
still not been delivered.  What do I need to do so that I can tell which
end-to-end delivery receipt corresponds to a particular bundle?  Thank
you in advance, I really appreciate the help!  Below is a summary of how
I have things set up on each computer:

*****<DTN_HOST2>*****

$ DTN2/apps/dtncpd/dtncpd   /home/host2/dtn/incoming

*****<DTN_HOST3>*****

$ DTN2/apps/dtncpd/dtncpd   /home/host3/dtn/incoming

*****<DTN_HOST4>*****

$ DTN2/apps/dtncpd/dtncpd   /home/host4/dtn/incoming

*****<DTN_HOST1>*****

On xterm 1:
$ DTN2/apps/dtncp/dtncp -D /home/bs/test2 dtn://host2.dtn
...blocks waiting for DTN_HOST2 to become reachable

On xterm 2:
$ DTN2/apps/dtncp/dtncp -D /home/bs/test3  dtn://host3.dtn
...blocks waiting for DTN_HOST3 to become reachable

On xterm 3:
$ DTN2/apps/dtncp/dtncp -D /home/bs/test4  dtn://host4.dtn
...all dtncp instances receive notification that their bundle was
delivered and exits, even though this was the only bundle successfully
delivered 





Received: from slb-smtpout-01.boeing.com (slb-smtpout-01.boeing.com [130.76.64.48]) by maillists.intel-research.net (8.13.8/8.13.7) with ESMTP id m194VTtF014133 for <dtn-users@mailman.dtnrg.org>; Fri, 8 Feb 2008 20:31:29 -0800
Received: from stl-av-01.boeing.com (stl-av-01.boeing.com [192.76.190.6]) by slb-smtpout-01.ns.cs.boeing.com (8.14.0/8.14.0/8.14.0/SMTPOUT) with ESMTP id m194WOTg002592 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=FAIL) for <dtn-users@mailman.dtnrg.org>; Fri, 8 Feb 2008 20:32:24 -0800 (PST)
Received: from stl-av-01.boeing.com (localhost [127.0.0.1]) by stl-av-01.boeing.com (8.14.0/8.14.0/DOWNSTREAM_RELAY) with ESMTP id m194WNuQ008215 for <dtn-users@mailman.dtnrg.org>; Fri, 8 Feb 2008 22:32:23 -0600 (CST)
Received: from XCH-NWBH-11.nw.nos.boeing.com (xch-nwbh-11.nw.nos.boeing.com [130.247.55.84]) by stl-av-01.boeing.com (8.14.0/8.14.0/UPSTREAM_RELAY) with ESMTP id m194WJf8008166 for <dtn-users@mailman.dtnrg.org>; Fri, 8 Feb 2008 22:32:23 -0600 (CST)
Received: from XCH-NW-8V2.nw.nos.boeing.com ([130.247.55.70]) by XCH-NWBH-11.nw.nos.boeing.com with Microsoft SMTPSVC(6.0.3790.1830);  Fri, 8 Feb 2008 20:32:20 -0800
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Date: Fri, 8 Feb 2008 20:31:50 -0800
Message-ID: <7770DA26FD19034E9CEB45ED93620C550664BCB4@XCH-NW-8V2.nw.nos.boeing.com>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: End-To-End Delivery Receipt Problem Using dtncp and dtncpd
Thread-Index: Achq1LAvWGpJMtv/QHOO94Kgchs/xA==
From: "Smith, Brian J" <Brian.J.Smith4@boeing.com>
To: <dtn-users@mailman.dtnrg.org>
X-OriginalArrivalTime: 09 Feb 2008 04:32:20.0809 (UTC) FILETIME=[C2749390:01C86AD4]
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by maillists.intel-research.net id m194VTtF014133
Cc: "Smith, Brian J" <Brian.J.Smith4@boeing.com>
Subject: [dtn-users] End-To-End Delivery Receipt Problem Using dtncp and dtncpd
X-BeenThere: dtn-users@mailman.dtnrg.org
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To: dtn-users mailing list <dtn-users@mailman.dtnrg.org>
List-Id: dtn-users mailing list <dtn-users.mailman.dtnrg.org>
List-Unsubscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-users>, <mailto:dtn-users-request@mailman.dtnrg.org?subject=unsubscribe>
List-Archive: <http://maillists.intel-research.net/pipermail/dtn-users>
List-Post: <mailto:dtn-users@mailman.dtnrg.org>
List-Help: <mailto:dtn-users-request@mailman.dtnrg.org?subject=help>
List-Subscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-users>, <mailto:dtn-users-request@mailman.dtnrg.org?subject=subscribe>
X-List-Received-Date: Sat, 09 Feb 2008 04:31:30 -0000

I'm having some trouble figuring out which end-to-end delivery receipts
correspond to a particular bundle.  I have four computers with DTN
installed on them.  I use the first computer <DTN_HOST1> to send out
three different bundles using three separate instances of dtncp.  The
other three computers <DTN_HOST2>, <DTN_HOST3>, and <DTN_HOST4> have the
dtncpd daemon running on them waiting for bundles to be delivered. I
send out three bundles with end-to-end delivery receipt flags set using
dtncp from <DTN_HOST1> to the other three computers running dtncpd
<DTN_HOST2>, <DTN_HOST3>, and <DTN_HOST4>.  The first two DTN
destinations <DTN_HOST2> and <DTN_HOST3> are not currently reachable
from <DTN_HOST1>, so the bundles are stored locally and those instances
of dtncp block waiting for an end-to-end delivery receipt.  I then send
out the third bundle to <DTN_HOST4> which is reachable.  At this point
all four dtncp instances on <DTN_HOST1> exit and claim to have received
end-to-end delivery receipts, even though the first two bundles have
still not been delivered.  What do I need to do so that I can tell which
end-to-end delivery receipt corresponds to a particular bundle?  Thank
you in advance, I really appreciate the help!  Below is a summary of how
I have things set up on each computer:

*****<DTN_HOST2>*****

$ DTN2/apps/dtncpd/dtncpd   /home/host2/dtn/incoming

*****<DTN_HOST3>*****

$ DTN2/apps/dtncpd/dtncpd   /home/host3/dtn/incoming

*****<DTN_HOST4>*****

$ DTN2/apps/dtncpd/dtncpd   /home/host4/dtn/incoming

*****<DTN_HOST1>*****

On xterm 1:
$ DTN2/apps/dtncp/dtncp -D /home/bs/test2 dtn://host2.dtn
...blocks waiting for DTN_HOST2 to become reachable

On xterm 2:
$ DTN2/apps/dtncp/dtncp -D /home/bs/test3  dtn://host3.dtn
...blocks waiting for DTN_HOST3 to become reachable

On xterm 3:
$ DTN2/apps/dtncp/dtncp -D /home/bs/test4  dtn://host4.dtn
...all dtncp instances receive notification that their bundle was
delivered and exits, even though this was the only bundle successfully
delivered 




