Subject: Re: [dtn-interest] Bundle Authentication vs. Bundle error detection
From: Lloyd Wood <[email-masked]>
To: Peter Lovell <[email-masked]>
Cc: [email-masked], Lloyd Wood <[email-masked]>
Date: Mon, 29 Jun 2009 15:13:10 +0100
List-Id: Delay Tolerant Networking Interest List <dtn-interest.maillists.intel-research.net>

On 26 Jun 2009, at 17:11, Peter Lovell wrote:
>
> I don't think the authors were suggesting that the PIB checksum scheme
> be used for single-hop error detection. It's more useful in  
> detecting an
> error at some intermediate point without waiting for the bundle to  
> reach
> its destination.

Intermediate points such as a custodian node, as custody transfer and  
the
source node abdicating responsibility for delivery and deleting its  
copy shouldn't
be done without an assurance that the custodian has an accurate copy.
Speeding up resends is a bonus.

A worked example of this is in our 'A Bundle of Problems' paper.

L.

DTN work: http://info.ee.surrey.ac.uk/Personal/L.Wood/saratoga/

<http://info.surrey.ac.uk/Personal/L.Wood/><[email-masked]>

Date: Mon, 29 Jun 2009 12:33:36 +0300
From: Teemu <[email-masked]>
To: Minh Nguyen <[email-masked]>, Elwyn Davies <[email-masked]>
Cc: [email-masked]
Subject: Re: [dtn-interest] To run DTN on Nokia N810

Hi,

The packages at http://www.netlab.tkk.fi/tutkimus/dtn/dttalkie/ have been
tested to work on N810. IIRC they contain only the dtnd daemon and none of
the apps. I have a packaged build for N810 from the mercurial repo that
includes all the apps as well, if you want it just send me an email.

Cheers,
-Teemu

On 29.6.2009 0.47, "Minh Nguyen" <[email-masked]> wrote:

> Many thanks, I've also found useful link; It could be help us for installing
> DTN on N810
> 
> http://www.netlab.tkk.fi/tutkimus/dtn/dttalkie/
> 
> Another question, Does DTN2 run on Windows/Cygwin?
> It is annouced in DTN2 source code that the code does not run yet in CygWin
> 
> Does any have success run DTN2 on Cygwin?
> 
> Many thanks,
> -Minh
> 
> On Sun, Jun 28, 2009 at 12:18 PM, Elwyn Davies <[email-masked]> wrote:
>> Hi.
>> 
>> I built the most recent DTN2 code a couple of weeks ago and ran some basic
>> tests.
>> 
>> No problems immediately apart from the amount of 'disk' needed - strip the
>> daemon which is otherwise 25MB! �I was thinking about reorganizing my N810 to
>> allow programs to be stored on the built-in memory card which by default does
>> not allow program execution.
>> 
>> I had more fun building the Python api adaptor. �The Python distutils
>> accesses the Makefile in the usr/lib/python2.5/config directory and pulls the
>> compiler specs (CC macros etc) that are then used to build the Python
>> extension module from the makefile. �Unfortunately the Python tools in
>> scratchbox explicitly use the host compiler toolchain which is of course
>> wrong. �The only way I found to fix this was to explicitly edit the makefile
>> to change the macros. �It was sufficient to change the CC and CXX macros at
>> lines 32 and 33 in /opt/scratchbox/tools/lib/python2.3/config/Makefile.
>> 
>> CC=gcc
>> #CC= � � � � � �/scratchbox/compilers/host-gcc/bin/gcc
>> -specs=/scratchbox/compilers/host-gcc/host-gcc.specs -pthread
>> CXX= � �g++
>> #CXX= � � � � � /scratchbox/compilers/host-gcc/bin/g++
>> -specs=/scratchbox/compilers/host-gcc/host-gcc.specs -pthread
>> 
>> I haven't had much opportunity to test the results yet.
>> 
>> I am currently developing a Python application (email adaptor) and will have
>> more info in a couple of weeks.
>> 
>> Regards,
>> Elwyn
>> 
>> 
>> Kurtis Heimerl wrote:
>>> I've done it. I'm not sure about the recent difficulties people have
>>> had in compiling DTN2, but maybe 6 months ago compiling and running it
>>> in scratchbox went off without a hitch.
>>> 
>>> On Sun, Jun 28, 2009 at 1:33 AM, Minh Nguyen<[email-masked]> wrote:
>>>  �
>>>> Hi All,
>>>> Does anyone have experience in running DTN daemon on N810 Nokia Tablet?
>>>> 
>>>> Thanks in advance,
>>>> 
>>>> --
>>>> Minh Nguyen
>>>> +33 6 65 76 44 60
>>>> 
>>>> 
>>>> _______________________________________________
>>>> dtn-interest mailing list
>>>> [email-masked]
>>>> http://maillists.intel-research.net/mailman/listinfo/dtn-interest
>>>> 
>>>> 
>>>>  � �
>>> _______________________________________________
>>> dtn-interest mailing list
>>> [email-masked]
>>> http://maillists.intel-research.net/mailman/listinfo/dtn-interest
>>>  �
>> 
> 
> 

From: Lloyd Wood <[email-masked]>
To: Minh Nguyen <[email-masked]>
Date: Sun, 28 Jun 2009 23:32:38 +0100
Cc: DTN interest <[email-masked]>, Lloyd Wood <[email-masked]>
Subject: Re: [dtn-interest] To run DTN on Nokia N810

Your question is more suited to the dtn-users list.

Using cygwin for anything networking-related is unwise. No IPv6,  
multicast doesn't work, libraries and functions are missing, etc etc.  
Get a real unix box if you don't want to spend hours wondering if the  
problems you see are due to dtn2 or due to cygwin.

see
http://maillists.intel-research.net/pipermail/dtn-users/2008-January/000726.html

you're on your own.

On 28 Jun 2009, at 22:47, Minh Nguyen wrote:

> Many thanks, I've also found useful link; It could be help us for  
> installing DTN on N810
>
> http://www.netlab.tkk.fi/tutkimus/dtn/dttalkie/
>
> Another question, Does DTN2 run on Windows/Cygwin?
> It is annouced in DTN2 source code that the code does not run yet in  
> CygWin
>
> Does any have success run DTN2 on Cygwin?
>
> Many thanks,
> -Minh
>
> On Sun, Jun 28, 2009 at 12:18 PM, Elwyn Davies <[email-masked]>  
> wrote:
> Hi.
>
> I built the most recent DTN2 code a couple of weeks ago and ran some  
> basic tests.
>
> No problems immediately apart from the amount of 'disk' needed -  
> strip the daemon which is otherwise 25MB!  I was thinking about  
> reorganizing my N810 to allow programs to be stored on the built-in  
> memory card which by default does not allow program execution.
>
> I had more fun building the Python api adaptor.  The Python  
> distutils accesses the Makefile in the usr/lib/python2.5/config  
> directory and pulls the compiler specs (CC macros etc) that are then  
> used to build the Python extension module from the makefile.   
> Unfortunately the Python tools in scratchbox explicitly use the host  
> compiler toolchain which is of course wrong.  The only way I found  
> to fix this was to explicitly edit the makefile to change the  
> macros.  It was sufficient to change the CC and CXX macros at lines  
> 32 and 33 in /opt/scratchbox/tools/lib/python2.3/config/Makefile.
>
> CC=gcc
> #CC=            /scratchbox/compilers/host-gcc/bin/gcc -specs=/ 
> scratchbox/compilers/host-gcc/host-gcc.specs -pthread
> CXX=    g++
> #CXX=           /scratchbox/compilers/host-gcc/bin/g++ -specs=/ 
> scratchbox/compilers/host-gcc/host-gcc.specs -pthread
>
> I haven't had much opportunity to test the results yet.
>
> I am currently developing a Python application (email adaptor) and  
> will have more info in a couple of weeks.
>
> Regards,
> Elwyn
>
>
> Kurtis Heimerl wrote:
> I've done it. I'm not sure about the recent difficulties people have
> had in compiling DTN2, but maybe 6 months ago compiling and running it
> in scratchbox went off without a hitch.
>
> On Sun, Jun 28, 2009 at 1:33 AM, Minh Nguyen<[email-masked]> wrote:
>
> Hi All,
> Does anyone have experience in running DTN daemon on N810 Nokia  
> Tablet?
>
> Thanks in advance,
>
> --
> Minh Nguyen
> +33 6 65 76 44 60
>
>
> _______________________________________________
> dtn-interest mailing list
> [email-masked]
> http://maillists.intel-research.net/mailman/listinfo/dtn-interest
>
>
>
> _______________________________________________
> dtn-interest mailing list
> [email-masked]
> http://maillists.intel-research.net/mailman/listinfo/dtn-interest
>
>
>
>
>
> -- 
> Minh Nguyen
> +33 6 65 76 44 60
>
> _______________________________________________
> dtn-interest mailing list
> [email-masked]
> http://maillists.intel-research.net/mailman/listinfo/dtn-interest

DTN work: http://info.ee.surrey.ac.uk/Personal/L.Wood/saratoga/

<http://info.surrey.ac.uk/Personal/L.Wood/><[email-masked]>

Date: Sun, 28 Jun 2009 23:47:25 +0200
From: Minh Nguyen <[email-masked]>
To: Elwyn Davies <[email-masked]>
Cc: [email-masked]
Subject: Re: [dtn-interest] To run DTN on Nokia N810

--000e0cd24caaee9807046d6f84d9
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Many thanks, I've also found useful link; It could be help us for installing
DTN on N810

http://www.netlab.tkk.fi/tutkimus/dtn/dttalkie/

Another question, Does DTN2 run on Windows/Cygwin?
It is annouced in DTN2 source code that the code does not run yet in CygWin

Does any have success run DTN2 on Cygwin?

Many thanks,
-Minh

On Sun, Jun 28, 2009 at 12:18 PM, Elwyn Davies <[email-masked]> wrote:

> Hi.
>
> I built the most recent DTN2 code a couple of weeks ago and ran some basic
> tests.
>
> No problems immediately apart from the amount of 'disk' needed - strip the
> daemon which is otherwise 25MB!  I was thinking about reorganizing my N810
> to allow programs to be stored on the built-in memory card which by default
> does not allow program execution.
>
> I had more fun building the Python api adaptor.  The Python distutils
> accesses the Makefile in the usr/lib/python2.5/config directory and pulls
> the compiler specs (CC macros etc) that are then used to build the Python
> extension module from the makefile.  Unfortunately the Python tools in
> scratchbox explicitly use the host compiler toolchain which is of course
> wrong.  The only way I found to fix this was to explicitly edit the makefile
> to change the macros.  It was sufficient to change the CC and CXX macros at
> lines 32 and 33 in /opt/scratchbox/tools/lib/python2.3/config/Makefile.
>
> CC=gcc
> #CC=            /scratchbox/compilers/host-gcc/bin/gcc
> -specs=/scratchbox/compilers/host-gcc/host-gcc.specs -pthread
> CXX=    g++
> #CXX=           /scratchbox/compilers/host-gcc/bin/g++
> -specs=/scratchbox/compilers/host-gcc/host-gcc.specs -pthread
>
> I haven't had much opportunity to test the results yet.
>
> I am currently developing a Python application (email adaptor) and will
> have more info in a couple of weeks.
>
> Regards,
> Elwyn
>
>
> Kurtis Heimerl wrote:
>
>> I've done it. I'm not sure about the recent difficulties people have
>> had in compiling DTN2, but maybe 6 months ago compiling and running it
>> in scratchbox went off without a hitch.
>>
>> On Sun, Jun 28, 2009 at 1:33 AM, Minh Nguyen<[email-masked]> wrote:
>>
>>
>>> Hi All,
>>> Does anyone have experience in running DTN daemon on N810 Nokia Tablet?
>>>
>>> Thanks in advance,
>>>
>>> --
>>> Minh Nguyen
>>> +33 6 65 76 44 60
>>>
>>>
>>> _______________________________________________
>>> dtn-interest mailing list
>>> [email-masked]
>>> http://maillists.intel-research.net/mailman/listinfo/dtn-interest
>>>
>>>
>>>
>>>
>> _______________________________________________
>> dtn-interest mailing list
>> [email-masked]
>> http://maillists.intel-research.net/mailman/listinfo/dtn-interest
>>
>>
>
>

-- 
Minh Nguyen
+33 6 65 76 44 60

--000e0cd24caaee9807046d6f84d9
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Many thanks, I&#39;ve also found useful link; It could be help us for insta=
lling DTN on N810<br><br><a href=3D"http://www.netlab.tkk.fi/tutkimus/dtn/d=
ttalkie/">http://www.netlab.tkk.fi/tutkimus/dtn/dttalkie/</a><br><br>Anothe=
r question, Does DTN2 run on Windows/Cygwin? <br>
It is annouced in DTN2 source code that the code does not run yet in CygWin=
<br><br>Does any have success run DTN2 on Cygwin?<br><br>Many thanks,<br>-M=
inh<br><br><div class=3D"gmail_quote">On Sun, Jun 28, 2009 at 12:18 PM, Elw=
yn Davies <span dir=3D"ltr">&lt;<a href=3D"mailto:[email-masked]">elwy=
[email-masked]</a>&gt;</span> wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hi.<br>
<br>
I built the most recent DTN2 code a couple of weeks ago and ran some basic =
tests.<br>
<br>
No problems immediately apart from the amount of &#39;disk&#39; needed - st=
rip the daemon which is otherwise 25MB! =C2=A0I was thinking about reorgani=
zing my N810 to allow programs to be stored on the built-in memory card whi=
ch by default does not allow program execution.<br>

<br>
I had more fun building the Python api adaptor. =C2=A0The Python distutils =
accesses the Makefile in the usr/lib/python2.5/config directory and pulls t=
he compiler specs (CC macros etc) that are then used to build the Python ex=
tension module from the makefile. =C2=A0Unfortunately the Python tools in s=
cratchbox explicitly use the host compiler toolchain which is of course wro=
ng. =C2=A0The only way I found to fix this was to explicitly edit the makef=
ile to change the macros. =C2=A0It was sufficient to change the CC and CXX =
macros at lines 32 and 33 in /opt/scratchbox/tools/lib/python2.3/config/Mak=
efile.<br>

<br>
CC=3Dgcc<br>
#CC=3D =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0/scratchbox/compilers/host-=
gcc/bin/gcc -specs=3D/scratchbox/compilers/host-gcc/host-gcc.specs -pthread=
<br>
CXX=3D =C2=A0 =C2=A0g++<br>
#CXX=3D =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 /scratchbox/compilers/host-gcc/b=
in/g++ -specs=3D/scratchbox/compilers/host-gcc/host-gcc.specs -pthread<br>
<br>
I haven&#39;t had much opportunity to test the results yet.<br>
<br>
I am currently developing a Python application (email adaptor) and will hav=
e more info in a couple of weeks.<br>
<br>
Regards,<br><font color=3D"#888888">
Elwyn</font><div><div></div><div class=3D"h5"><br>
<br>
Kurtis Heimerl wrote:<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I&#39;ve done it. I&#39;m not sure about the recent difficulties people hav=
e<br>
had in compiling DTN2, but maybe 6 months ago compiling and running it<br>
in scratchbox went off without a hitch.<br>
<br>
On Sun, Jun 28, 2009 at 1:33 AM, Minh Nguyen&lt;<a href=3D"mailto:skminh@gm=
ail.com" target=3D"_blank">[email-masked]</a>&gt; wrote:<br>
 =C2=A0<br>
<blockquote class=3D"gmail_quote" style=3D"border-left: 1px solid rgb(204, =
204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi All,<br>
Does anyone have experience in running DTN daemon on N810 Nokia Tablet?<br>
<br>
Thanks in advance,<br>
<br>
--<br>
Minh Nguyen<br>
+33 6 65 76 44 60<br>
<br>
<br>
_______________________________________________<br>
dtn-interest mailing list<br>
<a href=3D"mailto:[email-masked]" target=3D"_bla=
nk">[email-masked]</a><br>
<a href=3D"http://maillists.intel-research.net/mailman/listinfo/dtn-interes=
t" target=3D"_blank">http://maillists.intel-research.net/mailman/listinfo/d=
tn-interest</a><br>
<br>
<br>
 =C2=A0 =C2=A0<br>
</blockquote>
_______________________________________________<br>
dtn-interest mailing list<br>
<a href=3D"mailto:[email-masked]" target=3D"_bla=
nk">[email-masked]</a><br>
<a href=3D"http://maillists.intel-research.net/mailman/listinfo/dtn-interes=
t" target=3D"_blank">http://maillists.intel-research.net/mailman/listinfo/d=
tn-interest</a><br>
 =C2=A0<br>
</blockquote>
<br>
</div></div></blockquote></div><br><br clear=3D"all"><br>-- <br>Minh Nguyen=
<br>+33 6 65 76 44 60<br><br>

--000e0cd24caaee9807046d6f84d9--

Date: Sun, 28 Jun 2009 11:18:00 +0100
From: Elwyn Davies <[email-masked]>
To: Kurtis Heimerl <[email-masked]>
Cc: [email-masked]
Subject: Re: [dtn-interest] To run DTN on Nokia N810

Hi.

I built the most recent DTN2 code a couple of weeks ago and ran some 
basic tests.

No problems immediately apart from the amount of 'disk' needed - strip 
the daemon which is otherwise 25MB!  I was thinking about reorganizing 
my N810 to allow programs to be stored on the built-in memory card which 
by default does not allow program execution.

I had more fun building the Python api adaptor.  The Python distutils 
accesses the Makefile in the usr/lib/python2.5/config directory and 
pulls the compiler specs (CC macros etc) that are then used to build the 
Python extension module from the makefile.  Unfortunately the Python 
tools in scratchbox explicitly use the host compiler toolchain which is 
of course wrong.  The only way I found to fix this was to explicitly 
edit the makefile to change the macros.  It was sufficient to change the 
CC and CXX macros at lines 32 and 33 in 
/opt/scratchbox/tools/lib/python2.3/config/Makefile.

CC=gcc
#CC=            /scratchbox/compilers/host-gcc/bin/gcc 
-specs=/scratchbox/compilers/host-gcc/host-gcc.specs -pthread
CXX=    g++
#CXX=           /scratchbox/compilers/host-gcc/bin/g++ 
-specs=/scratchbox/compilers/host-gcc/host-gcc.specs -pthread

I haven't had much opportunity to test the results yet.

I am currently developing a Python application (email adaptor) and will 
have more info in a couple of weeks.

Regards,
Elwyn

Kurtis Heimerl wrote:
> I've done it. I'm not sure about the recent difficulties people have
> had in compiling DTN2, but maybe 6 months ago compiling and running it
> in scratchbox went off without a hitch.
>
> On Sun, Jun 28, 2009 at 1:33 AM, Minh Nguyen<[email-masked]> wrote:
>   
>> Hi All,
>> Does anyone have experience in running DTN daemon on N810 Nokia Tablet?
>>
>> Thanks in advance,
>>
>> --
>> Minh Nguyen
>> +33 6 65 76 44 60
>>
>>
>> _______________________________________________
>> dtn-interest mailing list
>> [email-masked]
>> http://maillists.intel-research.net/mailman/listinfo/dtn-interest
>>
>>
>>     
> _______________________________________________
> dtn-interest mailing list
> [email-masked]
> http://maillists.intel-research.net/mailman/listinfo/dtn-interest
>   

Sender: [email-masked]
Date: Sun, 28 Jun 2009 01:49:36 -0700
From: Kurtis Heimerl <[email-masked]>
To: Minh Nguyen <[email-masked]>
Cc: [email-masked]
Subject: Re: [dtn-interest] To run DTN on Nokia N810

I've done it. I'm not sure about the recent difficulties people have
had in compiling DTN2, but maybe 6 months ago compiling and running it
in scratchbox went off without a hitch.

On Sun, Jun 28, 2009 at 1:33 AM, Minh Nguyen<[email-masked]> wrote:
> Hi All,
> Does anyone have experience in running DTN daemon on N810 Nokia Tablet?
>
> Thanks in advance,
>
> --
> Minh Nguyen
> +33 6 65 76 44 60
>
>
> _______________________________________________
> dtn-interest mailing list
> [email-masked]
> http://maillists.intel-research.net/mailman/listinfo/dtn-interest
>
>

Date: Sun, 28 Jun 2009 10:33:57 +0200
From: Minh Nguyen <[email-masked]>
To: [email-masked]
Subject: [dtn-interest] To run DTN on Nokia N810

--000e0cd2474039c3b6046d646f15
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi All,
Does anyone have experience in running DTN daemon on N810 Nokia Tablet?

Thanks in advance,

-- 
Minh Nguyen
+33 6 65 76 44 60

--000e0cd2474039c3b6046d646f15
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

Hi All,<br>Does anyone have experience in running DTN daemon on N810 Nokia Tablet?<br><br>Thanks in advance,<br clear="all"><br>-- <br>Minh Nguyen<br>+33 6 65 76 44 60<br><br>

--000e0cd2474039c3b6046d646f15--

From: Hans Kruse <[email-masked]>
To: "Ivancic, William D. (GRC-RHN0)" <[email-masked]>
Date: Fri, 26 Jun 2009 14:44:24 -0400
Cc: Delay Tolerant Networking Interest List <[email-masked]>
Subject: Re: [dtn-interest] Planning for the Disconnectathon

--Apple-Mail-3--700791225
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

Will, when you are able to, send me the snapshot and I will prepare a  
set of pages on the dtnrg wiki.

On Jun 26, 2009, at 2:23 PM, Ivancic, William D. (GRC-RHN0) wrote:

> During the NASA internal multi-center tests, we utilize an internal  
> wiki to update configurations.  This was very useful for  
> establishing static routing and such.  Perhaps the DTNRG wiki could  
> be used in a similar fashion.    I would attach a small snapshot to  
> show what we put in for multi-center interoperability debugging, but  
> the site appears to currently be down.
>

Hans Kruse, Professor
J. Warren McClure School of Information and Telecommunication Systems
Adjunct Associate Professor of Electrical Engineering and Computer  
Science
292 Lindley Hall, Ohio University, Athens, OH, 45701
740-593-4891 voice, 740-593-4889 fax

--Apple-Mail-3--700791225
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">Will, when you are able to, =
send me the snapshot and I will prepare a set of pages on the dtnrg =
wiki.<div><br><div><div>On Jun 26, 2009, at 2:23 PM, Ivancic, William D. =
(GRC-RHN0) wrote:</div><br class=3D"Apple-interchange-newline"><blockquote=
 type=3D"cite"><span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; color: rgb(0, 0, 0); font-family: Helvetica; font-size: =
medium; font-style: normal; font-variant: normal; font-weight: normal; =
letter-spacing: normal; line-height: normal; orphans: 2; text-align: =
auto; text-indent: 0px; text-transform: none; white-space: normal; =
widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; =
-webkit-border-vertical-spacing: 0px; =
-webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: =
auto; -webkit-text-stroke-width: 0px; "><div style=3D"margin-right: 0in; =
margin-left: 0in; font-size: 12pt; font-family: 'Times New Roman', =
serif; margin-top: 0in; margin-bottom: 0.0001pt; "><span =
style=3D"font-size: 11pt; font-family: Calibri, sans-serif; color: =
rgb(31, 73, 125); ">During the NASA internal multi-center tests, we =
utilize an internal wiki to update configurations.&nbsp; This was very =
useful for establishing static routing and such.&nbsp; Perhaps the DTNRG =
wiki could be used in a similar fashion.&nbsp;&nbsp;&nbsp; I would =
attach a small snapshot to show what we put in for multi-center =
interoperability debugging, but the site appears to currently be =
down.<o:p></o:p></span></div></span><br =
class=3D"Apple-interchange-newline"></blockquote></div><br><div> <span =
class=3D"Apple-style-span" style=3D"border-collapse: separate; =
border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: Helvetica; =
font-size: 12px; font-style: normal; font-variant: normal; font-weight: =
normal; letter-spacing: normal; line-height: normal; text-align: auto; =
-khtml-text-decorations-in-effect: none; text-indent: 0px; =
-apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><div =
style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; "><p style=3D"margin: 0.0px 0.0px =
0.0px 0.0px"><font face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica">Hans Kruse, Professor</font></p><p style=3D"margin: 0.0px =
0.0px 0.0px 0.0px"><font face=3D"Helvetica" size=3D"3" style=3D"font: =
12.0px Helvetica">J. Warren McClure School of Information and =
Telecommunication Systems</font></p><p style=3D"margin: 0.0px 0.0px =
0.0px 0.0px"><font face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica">Adjunct Associate Professor of Electrical Engineering and =
Computer Science</font></p><p style=3D"margin: 0.0px 0.0px 0.0px =
0.0px"><font face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica">292 Lindley Hall, Ohio University, Athens, OH, =
45701</font></p><p style=3D"margin: 0.0px 0.0px 0.0px 0.0px"><font =
face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica">740-593-4891 voice, 740-593-4889 fax</font></p></div><br =
class=3D"Apple-interchange-newline"></span> =
</div><br></div></body></html>=

--Apple-Mail-3--700791225--

From: "Ivancic, William D. (GRC-RHN0)" <[email-masked]>
To: "[email-masked]" <[email-masked]>
Date: Fri, 26 Jun 2009 13:40:20 -0500
Accept-Language: en-US
acceptlanguage: en-US
Subject: [dtn-interest] Stockholm Meeting Topics

Assuming my travel gets approved, I can take a few minutes to discuss the DTN Network Management Requirements Draft

I could also discuss briefly NASA's internal multi-center network configuration and current test to date.

Regardless, I think we should discuss the need for a common API for DTN-2, ION and whatever else comes along (Spindle-3, etc...) so we can write common applications like dtn-ping, dtn-traceroute, dth-perf, etcetera.

Naming and Binding (early, late, partial, complete) - continued discussions on this (not just the syntax, but actual concepts of operations and how this stuff would really be deployed and work).
Of course, a great start for such discussions is:
http://tools.ietf.org/html/draft-pbasu-dtnrg-naming-00

/Will

From: "Ivancic, William D. (GRC-RHN0)" <[email-masked]>
To: Hans Kruse <[email-masked]>, Daniel Ellard <[email-masked]>
Date: Fri, 26 Jun 2009 13:23:28 -0500
Accept-Language: en-US
acceptlanguage: en-US
Cc: "[email-masked]" <[email-masked]>
Subject: Re: [dtn-interest] Planning for the Disconnectathon

--_000_3A5AA67A8B120B48825BFFCF5443856137E3974C29NDJSSCC03ndcn_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

I am planning on being in Stockholm Sunday - Friday returning Saturday, Aug=
ust 1.  Originally , and currently I am scheduled to return July 31, but IR=
TF is meeting July 31.

I may bring a build on my laptop virtual machine, but, it may actually make=
 more sense to work from the NASA DTNbone machines as the addresses are alr=
eady known and this would move the DTNbone farther along.

During the NASA internal multi-center tests, we utilize an internal wiki to=
 update configurations.  This was very useful for establishing static routi=
ng and such.  Perhaps the DTNRG wiki could be used in a similar fashion.   =
 I would attach a small snapshot to show what we put in for multi-center in=
teroperability debugging, but the site appears to currently be down.

It would probably be very useful to test TCPCL if the ION and DTN-2  modifi=
cations are complete by that time.

Will

******************************
William D. Ivancic
Phone 216-433-3494
Fax 216-433-8705
Networking Lab 216-433-2620
DTN Lab 216-433-2981
Mobile 440-503-4892
http://roland.grc.nasa.gov/~ivancic
From: [email-masked] [mailto:dtn-interes=
[email-masked]] On Behalf Of Hans Kruse
Sent: Friday, June 26, 2009 1:40 PM
To: Daniel Ellard
Cc: [email-masked]
Subject: Re: [dtn-interest] Planning for the Disconnectathon

I will not be in Stockholm.  We will likely send one person to the BBN site=
.   I plan to participate remotely working with the three DTNbone nodes we =
have up, as well any part of the network management infrastructure that we =
may be able to get in place by that time.

I had the same question as Will -- have we picked the specific day or day(s=
)?

On Jun 25, 2009, at 9:10 AM, Daniel Ellard wrote:

It's time to make concrete plans for the "Disconnectathon"
that we proposed for the end of the July (located split
between the IETF meeting in Stockholm and BBN in Cambridge).
The goal of the event is to demonstrate interoperability
between DTN implementations.

The key questions are:

1.  Are you planning to attend?  Which location?  (I need to
get a head count for each location, so if you're speaking
for a group of people, please tell me how many heads there are)

2.  Are you planning to bring an implementation of the DTN
stack?  (Note that it's not strictly necessary to "bring" a
node physically, but there needs to be an instance or two
accessible from the internet.)

3.  What applications can we/should we run at the
Disconnectathon?  Do you have applications you can
contribute and/or are you interested in collaborating to
develop such applications?

If possible, please answer soon, even if you don't have all
the answers yet, so we can gauge interest and begin planning.

Thanks,
          -Dan

--
Daniel Ellard, Ph.D.
Senior Scientist, Network Research
BBN Technologies
10 Moulton Street
Cambridge, MA 02138
[email-masked]<mailto:[email-masked]>
_______________________________________________
dtn-interest mailing list
[email-masked]
http://maillists.intel-research.net/mailman/listinfo/dtn-interest

Hans Kruse, Professor

J. Warren McClure School of Information and Telecommunication Systems

Adjunct Associate Professor of Electrical Engineering and Computer Science

292 Lindley Hall, Ohio University, Athens, OH, 45701

740-593-4891 voice, 740-593-4889 fax

--_000_3A5AA67A8B120B48825BFFCF5443856137E3974C29NDJSSCC03ndcn_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:Helvetica;
	panose-1:2 11 6 4 2 2 2 2 2 4;}
@font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Tahoma;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
p
	{mso-style-priority:99;
	mso-margin-top-alt:auto;
	margin-right:0in;
	mso-margin-bottom-alt:auto;
	margin-left:0in;
	font-size:12.0pt;
	font-family:"Times New Roman","serif";}
span.apple-tab-span
	{mso-style-name:apple-tab-span;}
span.apple-style-span
	{mso-style-name:apple-style-span;}
span.EmailStyle20
	{mso-style-type:personal-reply;
	font-family:"Calibri","sans-serif";
	color:#1F497D;}
.MsoChpDefault
	{mso-style-type:export-only;
	font-size:10.0pt;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple style=3D'word-wrap: break-wor=
d;
-webkit-nbsp-mode: space;-webkit-line-break: after-white-space'>

<div class=3DSection1>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>I am planning on being in Stockholm Sunday &#8211; Friday re=
turning
Saturday, August 1.&nbsp; Originally , and currently I am scheduled to retu=
rn
July 31, but IRTF is meeting July 31.&nbsp; &nbsp;<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>I may bring a build on my laptop virtual machine, but, it ma=
y
actually make more sense to work from the NASA DTNbone machines as the
addresses are already known and this would move the DTNbone farther along.<=
o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>During the NASA internal multi-center tests, we utilize an
internal wiki to update configurations.&nbsp; This was very useful for
establishing static routing and such.&nbsp; Perhaps the DTNRG wiki could be
used in a similar fashion.&nbsp;&nbsp;&nbsp; I would attach a small snapsho=
t to
show what we put in for multi-center interoperability debugging, but the si=
te appears
to currently be down.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>It would probably be very useful to test TCPCL if the ION an=
d
DTN-2 &nbsp;modifications are complete by that time.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'>Will<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:11.0pt;font-family:"Calibri",=
"sans-serif";
color:#1F497D'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;color:#1F497D'>*******=
***********************<br>
William D. Ivancic<br>
Phone 216-433-3494<br>
Fax 216-433-8705<br>
Networking Lab 216-433-2620<br>
DTN Lab 216-433-2981<br>
Mobile 440-503-4892<br>
<a href=3D"http://roland.grc.nasa.gov/~ivancic">http://roland.grc.nasa.gov/=
~ivancic</a></span><span
style=3D'font-size:11.0pt;font-family:"Calibri","sans-serif";color:#1F497D'=
><o:p></o:p></span></p>

<div style=3D'border:none;border-left:solid blue 1.5pt;padding:0in 0in 0in =
4.0pt'>

<div>

<div style=3D'border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in =
0in 0in'>

<p class=3DMsoNormal><b><span style=3D'font-size:10.0pt;font-family:"Tahoma=
","sans-serif"'>From:</span></b><span
style=3D'font-size:10.0pt;font-family:"Tahoma","sans-serif"'>
[email-masked]
[mailto:[email-masked]] <b>On Behalf Of =
</b>Hans
Kruse<br>
<b>Sent:</b> Friday, June 26, 2009 1:40 PM<br>
<b>To:</b> Daniel Ellard<br>
<b>Cc:</b> [email-masked]<br>
<b>Subject:</b> Re: [dtn-interest] Planning for the Disconnectathon<o:p></o=
:p></span></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>I will not be in Stockholm. &nbsp;We will likely send =
one
person to the BBN site. &nbsp; I plan to participate remotely working with =
the
three DTNbone nodes we have up, as well any part of the network management
infrastructure that we may be able to get in place by that time.<o:p></o:p>=
</p>

<div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

<div>

<p class=3DMsoNormal>I had the same question as Will -- have we picked the
specific day or day(s)?<o:p></o:p></p>

<div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div>

<div>

<p class=3DMsoNormal>On Jun 25, 2009, at 9:10 AM, Daniel Ellard wrote:<o:p>=
</o:p></p>

</div>

<p class=3DMsoNormal><br>
<br>
<o:p></o:p></p>

<div>

<p class=3DMsoNormal>It's time to make concrete plans for the
&quot;Disconnectathon&quot;<br>
that we proposed for the end of the July (located split<br>
between the IETF meeting in Stockholm and BBN in Cambridge).<br>
The goal of the event is to demonstrate interoperability<br>
between DTN implementations.<br>
<br>
The key questions are:<br>
<br>
1. &nbsp;Are you planning to attend? &nbsp;Which location? &nbsp;(I need to=
<br>
get a head count for each location, so if you're speaking<br>
for a group of people, please tell me how many heads there are)<br>
<br>
2. &nbsp;Are you planning to bring an implementation of the DTN<br>
stack? &nbsp;(Note that it's not strictly necessary to &quot;bring&quot; a<=
br>
node physically, but there needs to be an instance or two<br>
accessible from the internet.)<br>
<br>
3. &nbsp;What applications can we/should we run at the<br>
Disconnectathon? &nbsp;Do you have applications you can<br>
contribute and/or are you interested in collaborating to<br>
develop such applications?<br>
<br>
If possible, please answer soon, even if you don't have all<br>
the answers yet, so we can gauge interest and begin planning.<br>
<br>
Thanks,<br>
<span class=3Dapple-tab-span>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbs=
p;&nbsp; </span>-Dan<br>
<br>
-- <br>
Daniel Ellard, Ph.D.<br>
Senior Scientist, Network Research<br>
BBN Technologies<br>
10 Moulton Street<br>
Cambridge, MA 02138<br>
<a href=3D"mailto:[email-masked]">[email-masked]</a><br>
_______________________________________________<br>
dtn-interest mailing list<br>
[email-masked]<br>
http://maillists.intel-research.net/mailman/listinfo/dtn-interest<o:p></o:p=
></p>

</div>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<div>

<div>

<p style=3D'margin:0in;margin-bottom:.0001pt'><span style=3D'font-size:9.0p=
t;
font-family:"Helvetica","sans-serif";color:black'>Hans Kruse, Professor<o:p=
></o:p></span></p>

<p style=3D'margin:0in;margin-bottom:.0001pt'><span style=3D'font-size:9.0p=
t;
font-family:"Helvetica","sans-serif";color:black'>J. Warren McClure School =
of
Information and Telecommunication Systems<o:p></o:p></span></p>

<p style=3D'margin:0in;margin-bottom:.0001pt'><span style=3D'font-size:9.0p=
t;
font-family:"Helvetica","sans-serif";color:black'>Adjunct Associate Profess=
or
of Electrical Engineering and Computer Science<o:p></o:p></span></p>

<p style=3D'margin:0in;margin-bottom:.0001pt'><span style=3D'font-size:9.0p=
t;
font-family:"Helvetica","sans-serif";color:black'>292 Lindley Hall, Ohio Un=
iversity,
Athens, OH, 45701<o:p></o:p></span></p>

<p style=3D'margin:0in;margin-bottom:.0001pt'><span style=3D'font-size:9.0p=
t;
font-family:"Helvetica","sans-serif";color:black'>740-593-4891 voice,
740-593-4889 fax<o:p></o:p></span></p>

</div>

<p class=3DMsoNormal><span style=3D'font-size:9.0pt;font-family:"Helvetica"=
,"sans-serif";
color:black'><br>
<br>
</span><o:p></o:p></p>

</div>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

</div>

</div>

</div>

</div>

</body>

</html>

--_000_3A5AA67A8B120B48825BFFCF5443856137E3974C29NDJSSCC03ndcn_--

From: Hans Kruse <[email-masked]>
To: Daniel Ellard <[email-masked]>
Date: Fri, 26 Jun 2009 13:40:00 -0400
Cc: "[email-masked]" <[email-masked]>
Subject: Re: [dtn-interest] Planning for the Disconnectathon

--Apple-Mail-1--704655135
Content-Type: text/plain;
	charset=US-ASCII;
	format=flowed;
	delsp=yes
Content-Transfer-Encoding: 7bit

I will not be in Stockholm.  We will likely send one person to the BBN  
site.   I plan to participate remotely working with the three DTNbone  
nodes we have up, as well any part of the network management  
infrastructure that we may be able to get in place by that time.

I had the same question as Will -- have we picked the specific day or  
day(s)?

On Jun 25, 2009, at 9:10 AM, Daniel Ellard wrote:

> It's time to make concrete plans for the "Disconnectathon"
> that we proposed for the end of the July (located split
> between the IETF meeting in Stockholm and BBN in Cambridge).
> The goal of the event is to demonstrate interoperability
> between DTN implementations.
>
> The key questions are:
>
> 1.  Are you planning to attend?  Which location?  (I need to
> get a head count for each location, so if you're speaking
> for a group of people, please tell me how many heads there are)
>
> 2.  Are you planning to bring an implementation of the DTN
> stack?  (Note that it's not strictly necessary to "bring" a
> node physically, but there needs to be an instance or two
> accessible from the internet.)
>
> 3.  What applications can we/should we run at the
> Disconnectathon?  Do you have applications you can
> contribute and/or are you interested in collaborating to
> develop such applications?
>
> If possible, please answer soon, even if you don't have all
> the answers yet, so we can gauge interest and begin planning.
>
> Thanks,
> 	-Dan
>
> -- 
> Daniel Ellard, Ph.D.
> Senior Scientist, Network Research
> BBN Technologies
> 10 Moulton Street
> Cambridge, MA 02138
> [email-masked]
> _______________________________________________
> dtn-interest mailing list
> [email-masked]
> http://maillists.intel-research.net/mailman/listinfo/dtn-interest

Hans Kruse, Professor
J. Warren McClure School of Information and Telecommunication Systems
Adjunct Associate Professor of Electrical Engineering and Computer  
Science
292 Lindley Hall, Ohio University, Athens, OH, 45701
740-593-4891 voice, 740-593-4889 fax

--Apple-Mail-1--704655135
Content-Type: text/html;
	charset=US-ASCII
Content-Transfer-Encoding: quoted-printable

<html><body style=3D"word-wrap: break-word; -webkit-nbsp-mode: space; =
-webkit-line-break: after-white-space; ">I will not be in Stockholm. =
&nbsp;We will likely send one person to the BBN site. &nbsp; I plan to =
participate remotely working with the three DTNbone nodes we have up, as =
well any part of the network management infrastructure that we may be =
able to get in place by that time.<div><br></div><div>I had the same =
question as Will -- have we picked the specific day or =
day(s)?<br><div><br><div><div>On Jun 25, 2009, at 9:10 AM, Daniel Ellard =
wrote:</div><br class=3D"Apple-interchange-newline"><blockquote =
type=3D"cite"><div>It's time to make concrete plans for the =
"Disconnectathon"<br>that we proposed for the end of the July (located =
split<br>between the IETF meeting in Stockholm and BBN in =
Cambridge).<br> The goal of the event is to demonstrate =
interoperability<br>between DTN implementations.<br><br>The key =
questions are:<br><br>1. &nbsp;Are you planning to attend? &nbsp;Which =
location? &nbsp;(I need to<br>get a head count for each location, so if =
you're speaking<br>for a group of people, please tell me how many heads =
there are)<br><br>2. &nbsp;Are you planning to bring an implementation =
of the DTN<br>stack? &nbsp;(Note that it's not strictly necessary to =
"bring" a<br>node physically, but there needs to be an instance or =
two<br>accessible from the internet.)<br><br>3. &nbsp;What applications =
can we/should we run at the<br>Disconnectathon? &nbsp;Do you have =
applications you can<br>contribute and/or are you interested in =
collaborating to<br>develop such applications?<br><br>If possible, =
please answer soon, even if you don't have all<br>the answers yet, so we =
can gauge interest and begin planning.<br><br>Thanks,<br><span =
class=3D"Apple-tab-span" style=3D"white-space:pre">	=
</span>-Dan<br><br>-- <br>Daniel Ellard, Ph.D.<br>Senior Scientist, =
Network Research<br>BBN Technologies<br>10 Moulton Street<br>Cambridge, =
MA 02138<br><a =
href=3D"mailto:[email-masked]">[email-masked]</a><br>___________________=
____________________________<br>dtn-interest mailing =
list<br>[email-masked]<br>http://maillists.inte=
l-research.net/mailman/listinfo/dtn-interest<br></div></blockquote></div><=
br><div> <span class=3D"Apple-style-span" style=3D"border-collapse: =
separate; border-spacing: 0px 0px; color: rgb(0, 0, 0); font-family: =
Helvetica; font-size: 12px; font-style: normal; font-variant: normal; =
font-weight: normal; letter-spacing: normal; line-height: normal; =
text-align: auto; -khtml-text-decorations-in-effect: none; text-indent: =
0px; -apple-text-size-adjust: auto; text-transform: none; orphans: 2; =
white-space: normal; widows: 2; word-spacing: 0px; "><div =
style=3D"word-wrap: break-word; -khtml-nbsp-mode: space; =
-khtml-line-break: after-white-space; "><p style=3D"margin: 0.0px 0.0px =
0.0px 0.0px"><font face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica">Hans Kruse, Professor</font></p><p style=3D"margin: 0.0px =
0.0px 0.0px 0.0px"><font face=3D"Helvetica" size=3D"3" style=3D"font: =
12.0px Helvetica">J. Warren McClure School of Information and =
Telecommunication Systems</font></p><p style=3D"margin: 0.0px 0.0px =
0.0px 0.0px"><font face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica">Adjunct Associate Professor of Electrical Engineering and =
Computer Science</font></p><p style=3D"margin: 0.0px 0.0px 0.0px =
0.0px"><font face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica">292 Lindley Hall, Ohio University, Athens, OH, =
45701</font></p><p style=3D"margin: 0.0px 0.0px 0.0px 0.0px"><font =
face=3D"Helvetica" size=3D"3" style=3D"font: 12.0px =
Helvetica">740-593-4891 voice, 740-593-4889 fax</font></p></div><br =
class=3D"Apple-interchange-newline"></span> =
</div><br></div></div></body></html>=

--Apple-Mail-1--704655135--

From: Peter Lovell <[email-masked]>
To: "Ivancic, William D. (GRC-RHN0)" <[email-masked]>, [email-masked]
Date: Fri, 26 Jun 2009 12:11:44 -0400
Subject: Re: [dtn-interest] Bundle Authentication vs. Bundle error detection

Hi Will,

On Fri, Jun 26, 2009, Ivancic, William D. (GRC-RHN0)
<[email-masked]> wrote:

>Reading the Bundle Security Specification 
>http://tools.ietf.org/html/draft-irtf-dtnrg-bundle-security-08
>
>And the Bundle Checksum Specification
>http://tools.ietf.org/html/draft-irtf-dtnrg-bundle-checksum-05
>
>I was wondering if some clarification is needed in either or both of
>these documents.

Quite likely :)

>The Bundle Authentication Block (BAB) "protects a bundle on a "hop-by-
>hop" basis and other security blocks may be protecting over several hops
>or end-to-end, whenever both are present the BAB MUST form the "outer"
>layer of protection - that is, the BAB MUST always be calculated and
>added to the bundle after all other security blocks have been calculated
>and added to the bundle."

True. BAB must always be the outermost layer.
>
>However the bundle checksum utilizes the Payload Integrity Block (PIB)
>which would be inside the BAB.  

Also true. BABs, if present, must always "wrap" the entire bundle.
Although the block actually follows the primary, it logically wraps the
whole bundle with the exception of its own result.

>Thus, should it be stated somewhere that if the BAB is used, 
>the PIB is not needed if the PIB is being used for hop-by-hop 
>error detection only. 

I don't think the authors were suggesting that the PIB checksum scheme
be used for single-hop error detection. It's more useful in detecting an
error at some intermediate point without waiting for the bundle to reach
its destination. It can also detect errors introduced within an
intermediate node. While it can be used for a single-hop check, its
advantage comes with multi-hop checking.

>It seems like most existing systems (non-bundle protocol) have the
>checksum as the last wrapper.  Thus, following that convention, one 
>would have the PIB calculations include the BAB.

Think of BAB as a hop-by-hop checksum and PIB-checksum as end-to-end
checksum. In some cases, intermediate nodes will add blocks to the
bundle and these aren't protected by the PIB-checksum that was applied
earlier on. So there is a place for both.

Cheers.....Peter

From: "Symington, Susan F." <[email-masked]>
To: "Ivancic, William D. (GRC-RHN0)" <[email-masked]>, "[email-masked]" <[email-masked]>
Date: Fri, 26 Jun 2009 12:07:16 -0400
Accept-Language: en-US
acceptlanguage: en-US
Subject: Re: [dtn-interest] Bundle Authentication vs. Bundle error detection

The BAB must be the outer wrapper of the bundle because it only lasts for the duration of a single hop. If the PIB authenticator were calculated over the BAB and the PIB were to persist in the bundle more than a single hop, then the PIB would not authenticate, because the BAB that was in the bundle when the PIB was created would not be the same as the BAB that is in the bundle when the PIB is validated.

-susan
*****************************************************************
Susan Symington
The MITRE Corporation
[email-masked]
703-983-7209 (voice)
703-983-7142 (fax)
******************************************************************

>-----Original Message-----
>From: [email-masked] [mailto:dtn-
>[email-masked]] On Behalf Of Ivancic,
>William D. (GRC-RHN0)
>Sent: Friday, June 26, 2009 11:28 AM
>To: [email-masked]
>Subject: [dtn-interest] Bundle Authentication vs. Bundle error detection
>
>Reading the Bundle Security Specification
>http://tools.ietf.org/html/draft-irtf-dtnrg-bundle-security-08
>
>And the Bundle Checksum Specification
>http://tools.ietf.org/html/draft-irtf-dtnrg-bundle-checksum-05
>
>I was wondering if some clarification is needed in either or both of
>these documents.
>
>The Bundle Authentication Block (BAB) "protects a bundle on a "hop-by-
>hop" basis and other security blocks may be protecting over several hops
>or end-to-end, whenever both are present the BAB MUST form the "outer"
>layer of protection - that is, the BAB MUST always be calculated and
>added to the bundle after all other security blocks have been calculated
>and added to the bundle."
>
>However the bundle checksum utilizes the Payload Integrity Block (PIB)
>which would be inside the BAB.  Thus, should it be stated somewhere that
>if the BAB is used, the PIB is not needed if the PIB is being used for
>hop-by-hop error detection only. Although I am not so sure this is a
>true statement.  Perhaps local policy may state that one may still be
>willing to do something with a bundle even if authentication fails.
>
>It seems like most existing systems (non-bundle protocol) have the
>checksum as the last wrapper.  Thus, following that convention, one
>would have the PIB calculations include the BAB.
>
>
>******************************
>William D. Ivancic
>Phone 216-433-3494
>Fax 216-433-8705
>Networking Lab 216-433-2620
>DTN Lab 216-433-2981
>Mobile 440-503-4892
>http://roland.grc.nasa.gov/~ivancic
>
>
>_______________________________________________
>dtn-interest mailing list
>[email-masked]
>http://maillists.intel-research.net/mailman/listinfo/dtn-interest

From: Peter Lovell <[email-masked]>
To: "Ivancic, William D. (GRC-RHN0)" <[email-masked]>, [email-masked]
Date: Fri, 26 Jun 2009 11:52:19 -0400
Subject: Re: [dtn-interest] Bundle Authentication

Hi Will,

this part of things was set up before I became associated with dtn so I
can't offer an explanation of how we came to be where we are.

There's no requirement to do BA using HMAC, only that the BA1
ciphersuite do it this way. One could create a new ciphersuite, BA7 for
the sake of example, and define it to use a different keying scheme.
Perhaps use an ephemeral key for HMACing and then encrypt that with the
public key of the intended recipient. Only the recipient can decrypt the
key and then verify the bundle. 

Group keying would work in the BA1 HMAC ciphersuite. The key is not not
required to be one-to-one unique, just shared between the nodes that
need it. If it is one-to-one unique then it can serve as additional
validation of the node, but that's not required for BA. We're just
verifying that the bundle came from a source we know about and that it
hasn't been modified. A group key would be a good solution for certain
scenarios.

In some operational schemes I'd expect that nodes would establish short-
term shared keys for BA1 but exactly how to do that is not addressed in
any current specification. This is akin to the IPsec scenario you describe. 

Cheers.....Peter

On Fri, Jun 26, 2009, Ivancic, William D. (GRC-RHN0)
<[email-masked]> wrote:

>I'm taking yet another look at the DTN security specification and I have
>the following question.
>
>The bundle authentication block is for hop-by-hop authentication.  The
>specification indicates that "The BAB ciphersuite is based on shared
>secrets using HMAC."  And later indicates "The variant of HMAC to be
>used is HMAC-SHA1 as defined in [RFC2104]."
>
>So this requires that a shared secret get distributed somehow to those
>two bundle agents.  One would hope this shared secret is only between
>two unique systems if one wants to identify the previous hop source,
>otherwise, what good is it.  
>
> *  Is the reason for using a symmetric key for processing?
> *  Is the thought process here more along the lines of IPsec session
>keys negotiated via IKE or IKEv2?  (I would think negotiation of session
>keys in a disconnected network is extremely DTN network specific where
>it might work if you know disconnection is more of the form of
>disruption for short periods of time.)
>
>Also, one is  likely to be using asymmetric keys to wrap symmetric keys
>for key distribution.  If so, why not have the ability to authenticate
>using asymmetric keys such as is done with email?  It seems to me that
>his should be a viable option for hop-by-hop authentication for many
>instances and may simply the amount of keying material that has to be
>managed.  
>
>On the other hand, I think operationally one may not care what the
>previous hop source unique identity is.  Rather, I would like to know if
>the bundle originate from a trusted community - in which case I may
>decide to believe the routing protocols or simply be willing to store
>and forward bundles from various communities, but not from others.  Or
>course, this is sort of a naming and aggregation issue - (how does one
>aggregate naming?).  Anyway, it seems like one may find the Bundle
>Integrity Block more useful than the Bundle Authentication Block even to
>validate routing.  It may be easier to manage with something more along
>the lines of a shared group keys.  
>
>
>These thought come from contemplating how one might manage the following
>space scenario.  Lunar rover is US owned as is the Operations Center for
>the Lunar Rover.  The rover communicates to a relay satellite owned by
>India and India dumps the transmission through a Japanese ground
>station.  It seems like one may have an easier time validating
>certificates via some multi-organizational cross validation agreement
>than distributing shared secret keys. 
>
>
>******************************
>William D. Ivancic
>Phone 216-433-3494
>Fax 216-433-8705
>Networking Lab 216-433-2620
>DTN Lab 216-433-2981
>Mobile 440-503-4892
>http://roland.grc.nasa.gov/~ivancic 

From: "Ivancic, William D. (GRC-RHN0)" <[email-masked]>
To: "[email-masked]" <[email-masked]>
Date: Fri, 26 Jun 2009 10:28:09 -0500
Accept-Language: en-US
acceptlanguage: en-US
Subject: [dtn-interest] Bundle Authentication vs. Bundle error detection

Reading the Bundle Security Specification 
http://tools.ietf.org/html/draft-irtf-dtnrg-bundle-security-08

And the Bundle Checksum Specification
http://tools.ietf.org/html/draft-irtf-dtnrg-bundle-checksum-05

I was wondering if some clarification is needed in either or both of these documents.

The Bundle Authentication Block (BAB) "protects a bundle on a "hop-by-hop" basis and other security blocks may be protecting over several hops or end-to-end, whenever both are present the BAB MUST form the "outer" layer of protection - that is, the BAB MUST always be calculated and added to the bundle after all other security blocks have been calculated and added to the bundle."

However the bundle checksum utilizes the Payload Integrity Block (PIB) which would be inside the BAB.  Thus, should it be stated somewhere that if the BAB is used, the PIB is not needed if the PIB is being used for hop-by-hop error detection only. Although I am not so sure this is a true statement.  Perhaps local policy may state that one may still be willing to do something with a bundle even if authentication fails.

It seems like most existing systems (non-bundle protocol) have the checksum as the last wrapper.  Thus, following that convention, one  would have the PIB calculations include the BAB.

******************************
William D. Ivancic
Phone 216-433-3494
Fax 216-433-8705
Networking Lab 216-433-2620
DTN Lab 216-433-2981
Mobile 440-503-4892
http://roland.grc.nasa.gov/~ivancic 

From: "Ivancic, William D. (GRC-RHN0)" <[email-masked]>
To: "[email-masked]" <[email-masked]>
Date: Fri, 26 Jun 2009 09:56:29 -0500
Accept-Language: en-US
acceptlanguage: en-US
Subject: [dtn-interest] Bundle Authentication

I'm taking yet another look at the DTN security specification and I have the following question.

The bundle authentication block is for hop-by-hop authentication.  The specification indicates that "The BAB ciphersuite is based on shared secrets using HMAC."  And later indicates "The variant of HMAC to be used is HMAC-SHA1 as defined in [RFC2104]."

So this requires that a shared secret get distributed somehow to those two bundle agents.  One would hope this shared secret is only between two unique systems if one wants to identify the previous hop source, otherwise, what good is it.  

 *  Is the reason for using a symmetric key for processing?
 *  Is the thought process here more along the lines of IPsec session keys negotiated via IKE or IKEv2?  (I would think negotiation of session keys in a disconnected network is extremely DTN network specific where it might work if you know disconnection is more of the form of disruption for short periods of time.)

Also, one is  likely to be using asymmetric keys to wrap symmetric keys for key distribution.  If so, why not have the ability to authenticate using asymmetric keys such as is done with email?  It seems to me that his should be a viable option for hop-by-hop authentication for many instances and may simply the amount of keying material that has to be managed.  

On the other hand, I think operationally one may not care what the previous hop source unique identity is.  Rather, I would like to know if the bundle originate from a trusted community - in which case I may decide to believe the routing protocols or simply be willing to store and forward bundles from various communities, but not from others.  Or course, this is sort of a naming and aggregation issue - (how does one aggregate naming?).  Anyway, it seems like one may find the Bundle Integrity Block more useful than the Bundle Authentication Block even to validate routing.  It may be easier to manage with something more along the lines of a shared group keys.  

These thought come from contemplating how one might manage the following space scenario.  Lunar rover is US owned as is the Operations Center for the Lunar Rover.  The rover communicates to a relay satellite owned by India and India dumps the transmission through a Japanese ground station.  It seems like one may have an easier time validating certificates via some multi-organizational cross validation agreement than distributing shared secret keys. 

******************************
William D. Ivancic
Phone 216-433-3494
Fax 216-433-8705
Networking Lab 216-433-2620
DTN Lab 216-433-2981
Mobile 440-503-4892
http://roland.grc.nasa.gov/~ivancic 

Date: Fri, 26 Jun 2009 12:46:40 +0100
From: Stephen Farrell <[email-masked]>
Cc: "[email-masked]" <[email-masked]>
Subject: Re: [dtn-interest] Planning for the Disconnectathon

I'll be there, and most likely Alex as well.

We can play about with the DTN2 builds we're doing for
N4C.

If no-one else has it, I have a build of the IBR-DTN
that I might try against some others. (UDP CL onlu, the
TCP CL there isn't finished afaik)

We can probably bring up some small bits of kit, send
requests:-)

I don't think there's anyone planning to do anything
with LTP, but we could do that too if someone wants.

S.

Teemu K�rkk�inen wrote:
> Hi,
> 
> 1. I'm planning to attend in Stockholm.
> 
> 2. I will bring a Java and ObjC implementations of the TCPCL and  
> bundle parsing. (No routing etc.)
> 
> 3. Sending images inside bundles is something simple we already have  
> implemented.
> 
> Cheers,
> -Teemu
> 
> On 25.6.2009, at 16.10, Daniel Ellard <[email-masked]> wrote:
> 
>> It's time to make concrete plans for the "Disconnectathon"
>> that we proposed for the end of the July (located split
>> between the IETF meeting in Stockholm and BBN in Cambridge).
>> The goal of the event is to demonstrate interoperability
>> between DTN implementations.
>>
>> The key questions are:
>>
>> 1.  Are you planning to attend?  Which location?  (I need to
>> get a head count for each location, so if you're speaking
>> for a group of people, please tell me how many heads there are)
>>
>> 2.  Are you planning to bring an implementation of the DTN
>> stack?  (Note that it's not strictly necessary to "bring" a
>> node physically, but there needs to be an instance or two
>> accessible from the internet.)
>>
>> 3.  What applications can we/should we run at the
>> Disconnectathon?  Do you have applications you can
>> contribute and/or are you interested in collaborating to
>> develop such applications?
>>
>> If possible, please answer soon, even if you don't have all
>> the answers yet, so we can gauge interest and begin planning.
>>
>> Thanks,
>>    -Dan
>>
>> -- 
>> Daniel Ellard, Ph.D.
>> Senior Scientist, Network Research
>> BBN Technologies
>> 10 Moulton Street
>> Cambridge, MA 02138
>> [email-masked]
>> _______________________________________________
>> dtn-interest mailing list
>> [email-masked]
>> http://maillists.intel-research.net/mailman/listinfo/dtn-interest
> _______________________________________________
> dtn-interest mailing list
> [email-masked]
> http://maillists.intel-research.net/mailman/listinfo/dtn-interest
> 

From: =?utf-8?Q?Teemu_K=C3=A4rkk=C3=A4inen?= <[email-masked]>
To: Daniel Ellard <[email-masked]>
Date: Fri, 26 Jun 2009 14:37:16 +0300
Cc: "[email-masked]" <[email-masked]>
Subject: Re: [dtn-interest] Planning for the Disconnectathon

Hi,

1. I'm planning to attend in Stockholm.

2. I will bring a Java and ObjC implementations of the TCPCL and  
bundle parsing. (No routing etc.)

3. Sending images inside bundles is something simple we already have  
implemented.

Cheers,
-Teemu

On 25.6.2009, at 16.10, Daniel Ellard <[email-masked]> wrote:

> It's time to make concrete plans for the "Disconnectathon"
> that we proposed for the end of the July (located split
> between the IETF meeting in Stockholm and BBN in Cambridge).
> The goal of the event is to demonstrate interoperability
> between DTN implementations.
>
> The key questions are:
>
> 1.  Are you planning to attend?  Which location?  (I need to
> get a head count for each location, so if you're speaking
> for a group of people, please tell me how many heads there are)
>
> 2.  Are you planning to bring an implementation of the DTN
> stack?  (Note that it's not strictly necessary to "bring" a
> node physically, but there needs to be an instance or two
> accessible from the internet.)
>
> 3.  What applications can we/should we run at the
> Disconnectathon?  Do you have applications you can
> contribute and/or are you interested in collaborating to
> develop such applications?
>
> If possible, please answer soon, even if you don't have all
> the answers yet, so we can gauge interest and begin planning.
>
> Thanks,
>    -Dan
>
> -- 
> Daniel Ellard, Ph.D.
> Senior Scientist, Network Research
> BBN Technologies
> 10 Moulton Street
> Cambridge, MA 02138
> [email-masked]
> _______________________________________________
> dtn-interest mailing list
> [email-masked]
> http://maillists.intel-research.net/mailman/listinfo/dtn-interest

Date: Fri, 26 Jun 2009 08:51:34 +0000 (GMT)
From: Scott Fowler <[email-masked]>
To: [email-masked]
Subject: [dtn-interest] IEEE NGWS 2009

--0-1264954169-1246006294=:35296
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable

The First International Conference on Next Generation Wireless Systems will=
 be held on October 12 ~ 14, 2009, Melbourne, Australia.=0A=0ANGWS 2009 wil=
l be the most comprehensive conference focused on the various aspects of ad=
vances in Next Generation Wireless Systems. Our Conference provides a chanc=
e for academic and industry professionals to discuss recent progress in the=
 area of Next Generation Wireless Systems.=0AThe goal of this conference is=
 to bring together the researchers from academia and industry as well as pr=
actitioners to share ideas, problems and solutions relating to the multifac=
eted aspects of the Wireless Systems.=0A=0AAll accepted and registered pape=
rs will be included in the conference proceeding published by IEEE CS (as a=
 Short Paper, 4 pages. Indexed by EI). And most presented papers at the con=
ference, after revision and extension, will be included in CCIS (as a Full =
Paper, at least 12 pages. New LNCS sister-series, indexed by EI). And some =
papers selected will be included in some journals (pending).=0AThis confere=
nce will be organized and hosted by SERSC.=0A=0ASpecial Issue=0A=0ADistingu=
ished papers accepted and presented in NGWS 2008, after further revisions, =
will be published in the special issues of the following international jour=
nals:=0A=0ASecurity and Communication Networks (Wiley and Sons)=0AJournal o=
f Internet Technology (SCIE)=0AInternational Journal of Hybrid Information =
Technology=0AInternational Journal of Future Generation Communication and N=
etworking=0AInternational Journal of Multimedia and Ubiquitous Engineering=
=0A=0ATOPICS=0A=0AThe main topics include but will not be limited to: (Exce=
llent surveying works in these areas are welcome, too.)=0A=0A=E2=80=A2    M=
obility Management=0A=E2=80=A2    Cross-layer schemes and optimizations=0A=
=E2=80=A2    End-to-End Quality of service support=0A=E2=80=A2    Mobility =
Management=0A=E2=80=A2    Handoff Techniques=0A=E2=80=A2    Resource manage=
ment and admission control=0A=E2=80=A2    QoS routing and signaling=0A=E2=
=80=A2    QoS management in heterogeneous wireless systems=0A=E2=80=A2    W=
ireless Mesh Networks=0A=E2=80=A2    Pricing and Charging Models=0A=E2=80=
=A2    Multimedia delivery over wireless networks=0A=E2=80=A2    Security a=
nd Privacy in wireless systems=0A=E2=80=A2    Performance evaluation of wir=
eless systems and protocols=0A=E2=80=A2    Mobil Ad-hoc Networks=0A=E2=80=
=A2    Wireless Sensor Networks=0A=E2=80=A2    Energy and power management =
in wireless systems=0A=E2=80=A2    Next Generation Wireless Systems=0A=E2=
=80=A2    Mobile Broadband Wireless Access=0A=E2=80=A2    Wireless Internet=
 and All-IP integration=0A=E2=80=A2    Location based services and tracking=
=0A=E2=80=A2    Wireless network testbeds and applications=0A=E2=80=A2    W=
ireless LANs and PANs, WiMAX=0A=E2=80=A2    RFID protocols and systems=0A=
=E2=80=A2    Traffic Control and Engineering=0A=E2=80=A2    3G, 4G, and bey=
ond systems=0A=E2=80=A2    Experimental wireless systems and trials=0A=E2=
=80=A2    Cognitive radio networks=0A=E2=80=A2    Interworking heterogeneou=
s wired/wireless networks=0A=E2=80=A2    Middleware support for wireless sy=
stems=0A =0A=0A=0AEvery submitted paper will be carefully reviewed by at le=
ast two members of the International Program Committee. The problematic (bo=
rderline) papers will be additionally evaluated by the members of the Inter=
national Advisory Board and the Chairs of the conference.=0A=0AAll accepted=
 and registered papers will be included in the conference proceeding publis=
hed by IEEE CS (as a Short Paper, 4 pages. Indexed by EI). And most present=
ed papers at the conference, after revision and extension, will be included=
 in CCIS (as a Full Paper, at least 12 pages. New LNCS sister-series, index=
ed by EI).=0A=0APaper Submission=0A=0AAll papers should be submitted by onl=
ine system for review with IEEE CS paper format (at least 4 pages).=0A=0APl=
ease use IEEE CS paper format: ftp://pubftp.computer.org/press/outgoing/pro=
ceedings/format.pdf=0A=0AAll submissions should be done at: http://submissi=
on.sersc.org/NGWS2009/=0A=0A=0ADates and Deadlines=0A=0ASubmission of paper=
 : 5th July, 2009=0A=0ANotification of acceptance : 8th August, 2009=0A=0AS=
ubmission of the camera ready: 23rd August, 2009=0A=0ARegular Registration:=
 8th August-28th August, 2009=0A=0A=0ACommittee=0A=0A=0ASteering Co-Chairs:=
=0A=0ATai-hoon Kim, Hannam Unviersity, Korea=0A=0AByeongho Kang, University=
 of Tasmania, Australia=0A=0A=0AGeneral Co-Chairs:=0A=0ANaveen Chilamkurti,=
 La Trobe University, Australia=0A=0AHsiao-Hwa Chen, National Cheng Kung Un=
iversity, Taiwan=0A=0A=0AProgram Co-Chairs:=0A=0ASang-Soo Yeo, Hannam Unive=
rsity, Korea=0A=0ASherali Zeadally, University of the District of Columbia,=
 USA=0A=0A=0AInternational Advisory Board:=0A=0AWai Chi Fang, NASA JPL, USA=
=0A=0AJong Hyuk Park, Kyungnam University, Korea=0A=0ARuay-Shiung Chang, Na=
tional Dong Hwa University, Taiwan=0A=0A=0APublicity Co-Chairs:=0A=0ALaura =
Rusu, La Trobe University, Australia=0A=0AAvinash Srinivasan, Bloomsburg Un=
iversity, Pennsylvania, USA=0A=0AScott Fowler, Aston University, United Kin=
gdom=0A=0A=0AProgram Committee:=0Ahttp://www.sersc.org/NGWS2009/comm.php=0A=
=0ASubmission System: http://submission.sersc.org/NGWS2009/=0A=0AFor genera=
l enquiries about NGWS 2009 Conference or in case of any difficulty, please=
 contact:=0A=0AThe NGWS Secretariat=0AScience & Engineering Research Suppor=
t Center, Korea.=0AEmail: [email-masked]=0ATel: +82 42 629 8386=0AFax: +=
82 42 624 2205=0A=0A=0A=0A      
--0-1264954169-1246006294=:35296
Content-Type: text/html; charset=utf-8
Content-Transfer-Encoding: quoted-printable

<html><head><style type=3D"text/css"><!-- DIV {margin:0px;} --></style></he=
ad><body><div style=3D"font-family:times new roman,new york,times,serif;fon=
t-size:12pt"><div>The First International Conference on Next Generation Wir=
eless Systems will be held on October 12 ~ 14, 2009, Melbourne, Australia.<=
br><br>NGWS 2009 will be the most comprehensive conference focused on the v=
arious aspects of advances in Next Generation Wireless Systems. Our Confere=
nce provides a chance for academic and industry professionals to discuss re=
cent progress in the area of Next Generation Wireless Systems.<br>The goal =
of this conference is to bring together the researchers from academia and i=
ndustry as well as practitioners to share ideas, problems and solutions rel=
ating to the multifaceted aspects of the Wireless Systems.<br><br>All accep=
ted and registered papers will be included in the conference proceeding pub=
lished by IEEE CS (as a Short Paper, 4 pages. Indexed by EI). And most
 presented papers at the conference, after revision and extension, will be =
included in CCIS (as a Full Paper, at least 12 pages. New LNCS sister-serie=
s, indexed by EI). And some papers selected will be included in some journa=
ls (pending).<br>This conference will be organized and hosted by SERSC.<br>=
<br>Special Issue<br><br>Distinguished papers accepted and presented in NGW=
S 2008, after further revisions, will be published in the special issues of=
 the following international journals:<br><br>Security and Communication Ne=
tworks (Wiley and Sons)<br>Journal of Internet Technology (SCIE)<br>Interna=
tional Journal of Hybrid Information Technology<br>International Journal of=
 Future Generation Communication and Networking<br>International Journal of=
 Multimedia and Ubiquitous Engineering<br><br>TOPICS<br><br>The main topics=
 include but will not be limited to: (Excellent surveying works in these ar=
eas are welcome, too.)<br><br>=E2=80=A2&nbsp;&nbsp;&nbsp; Mobility
 Management<br>=E2=80=A2&nbsp;&nbsp;&nbsp; Cross-layer schemes and optimiza=
tions<br>=E2=80=A2&nbsp;&nbsp;&nbsp; End-to-End Quality of service support<=
br>=E2=80=A2&nbsp;&nbsp;&nbsp; Mobility Management<br>=E2=80=A2&nbsp;&nbsp;=
&nbsp; Handoff Techniques<br>=E2=80=A2&nbsp;&nbsp;&nbsp; Resource managemen=
t and admission control<br>=E2=80=A2&nbsp;&nbsp;&nbsp; QoS routing and sign=
aling<br>=E2=80=A2&nbsp;&nbsp;&nbsp; QoS management in heterogeneous wirele=
ss systems<br>=E2=80=A2&nbsp;&nbsp;&nbsp; Wireless Mesh Networks<br>=E2=80=
=A2&nbsp;&nbsp;&nbsp; Pricing and Charging Models<br>=E2=80=A2&nbsp;&nbsp;&=
nbsp; Multimedia delivery over wireless networks<br>=E2=80=A2&nbsp;&nbsp;&n=
bsp; Security and Privacy in wireless systems<br>=E2=80=A2&nbsp;&nbsp;&nbsp=
; Performance evaluation of wireless systems and protocols<br>=E2=80=A2&nbs=
p;&nbsp;&nbsp; Mobil Ad-hoc Networks<br>=E2=80=A2&nbsp;&nbsp;&nbsp; Wireles=
s Sensor Networks<br>=E2=80=A2&nbsp;&nbsp;&nbsp; Energy and power managemen=
t in wireless systems<br>=E2=80=A2&nbsp;&nbsp;&nbsp; Next Generation Wirele=
ss
 Systems<br>=E2=80=A2&nbsp;&nbsp;&nbsp; Mobile Broadband Wireless Access<br=
>=E2=80=A2&nbsp;&nbsp;&nbsp; Wireless Internet and All-IP integration<br>=
=E2=80=A2&nbsp;&nbsp;&nbsp; Location based services and tracking<br>=E2=80=
=A2&nbsp;&nbsp;&nbsp; Wireless network testbeds and applications<br>=E2=80=
=A2&nbsp;&nbsp;&nbsp; Wireless LANs and PANs, WiMAX<br>=E2=80=A2&nbsp;&nbsp=
;&nbsp; RFID protocols and systems<br>=E2=80=A2&nbsp;&nbsp;&nbsp; Traffic C=
ontrol and Engineering<br>=E2=80=A2&nbsp;&nbsp;&nbsp; 3G, 4G, and beyond sy=
stems<br>=E2=80=A2&nbsp;&nbsp;&nbsp; Experimental wireless systems and tria=
ls<br>=E2=80=A2&nbsp;&nbsp;&nbsp; Cognitive radio networks<br>=E2=80=A2&nbs=
p;&nbsp;&nbsp; Interworking heterogeneous wired/wireless networks<br>=E2=80=
=A2&nbsp;&nbsp;&nbsp; Middleware support for wireless systems<br>&nbsp;<br>=
<br><br>Every submitted paper will be carefully reviewed by at least two me=
mbers of the International Program Committee. The problematic (borderline) =
papers will be additionally evaluated by the members of the
 International Advisory Board and the Chairs of the conference.<br><br>All =
accepted and registered papers will be included in the conference proceedin=
g published by IEEE CS (as a Short Paper, 4 pages. Indexed by EI). And most=
 presented papers at the conference, after revision and extension, will be =
included in CCIS (as a Full Paper, at least 12 pages. New LNCS sister-serie=
s, indexed by EI).<br><br>Paper Submission<br><br>All papers should be subm=
itted by online system for review with IEEE CS paper format (at least 4 pag=
es).<br><br>Please use IEEE CS paper format: ftp://pubftp.computer.org/pres=
s/outgoing/proceedings/format.pdf<br><br><span>All submissions should be do=
ne at: <a target=3D"_blank" href=3D"http://submission.sersc.org/NGWS2009/">=
http://submission.sersc.org/NGWS2009/</a></span><br><br><br>Dates and Deadl=
ines<br><br>Submission of paper : 5th July, 2009<br><br>Notification of acc=
eptance : 8th August, 2009<br><br>Submission of the camera ready: 23rd
 August, 2009<br><br>Regular Registration: 8th August-28th August, 2009<br>=
<br><br>Committee<br><br><br>Steering Co-Chairs:<br><br>Tai-hoon Kim, Hanna=
m Unviersity, Korea<br><br>Byeongho Kang, University of Tasmania, Australia=
<br><br><br>General Co-Chairs:<br><br>Naveen Chilamkurti, La Trobe Universi=
ty, Australia<br><br>Hsiao-Hwa Chen, National Cheng Kung University, Taiwan=
<br><br><br>Program Co-Chairs:<br><br>Sang-Soo Yeo, Hannam University, Kore=
a<br><br>Sherali Zeadally, University of the District of Columbia, USA<br><=
br><br>International Advisory Board:<br><br>Wai Chi Fang, NASA JPL, USA<br>=
<br>Jong Hyuk Park, Kyungnam University, Korea<br><br>Ruay-Shiung Chang, Na=
tional Dong Hwa University, Taiwan<br><br><br>Publicity Co-Chairs:<br><br>L=
aura Rusu, La Trobe University, Australia<br><br>Avinash Srinivasan, Blooms=
burg University, Pennsylvania, USA<br><br>Scott Fowler, Aston University, U=
nited Kingdom<br><br><br>Program Committee:<br><span><a
 target=3D"_blank" href=3D"http://www.sersc.org/NGWS2009/comm.php">http://w=
ww.sersc.org/NGWS2009/comm.php</a></span><br><br><span>Submission System: <=
a target=3D"_blank" href=3D"http://submission.sersc.org/NGWS2009/">http://s=
ubmission.sersc.org/NGWS2009/</a></span><br><br>For general enquiries about=
 NGWS 2009 Conference or in case of any difficulty, please contact:<br><br>=
The NGWS Secretariat<br>Science &amp; Engineering Research Support Center, =
Korea.<br>Email: [email-masked]<br>Tel: +82 42 629 8386<br>Fax: +82 42 6=
24 2205<br></div></div><br>=0A=0A=0A=0A      </body></html>
--0-1264954169-1246006294=:35296--

Date: Thu, 25 Jun 2009 22:39:06 +0300
From: [email-masked]
To: [email-masked]
Subject: Re: [dtn-interest] Planning for the Disconnectathon

Hi,

we have (still quite primitive) BPA, and TCPCL implementation for S60  
smartphones. I'm currently enhancing those. Also we have DT-Talkie for  
S60 under development - Maemo version working with DTN2 is already  
there. So I'll be interested in the Stockholm hackathon, and hopefully  
get the code in good shape in time.

Anssi
Research assistant @ HUT

Lainaus Daniel Ellard <[email-masked]>:

> It's time to make concrete plans for the "Disconnectathon"
> that we proposed for the end of the July (located split
> between the IETF meeting in Stockholm and BBN in Cambridge).
>  The goal of the event is to demonstrate interoperability
> between DTN implementations.
>
> The key questions are:
>
> 1.  Are you planning to attend?  Which location?  (I need to
> get a head count for each location, so if you're speaking
> for a group of people, please tell me how many heads there are)
>
> 2.  Are you planning to bring an implementation of the DTN
> stack?  (Note that it's not strictly necessary to "bring" a
> node physically, but there needs to be an instance or two
> accessible from the internet.)
>
> 3.  What applications can we/should we run at the
> Disconnectathon?  Do you have applications you can
> contribute and/or are you interested in collaborating to
> develop such applications?
>
> If possible, please answer soon, even if you don't have all
> the answers yet, so we can gauge interest and begin planning.
>
> Thanks,
> 	-Dan
>
> --
> Daniel Ellard, Ph.D.
> Senior Scientist, Network Research
> BBN Technologies
> 10 Moulton Street
> Cambridge, MA 02138
> [email-masked]
> _______________________________________________
> dtn-interest mailing list
> [email-masked]
> http://maillists.intel-research.net/mailman/listinfo/dtn-interest
>

Date: Thu, 25 Jun 2009 12:33:27 -0400
From: Andrew Sullivan <[email-masked]>
To: [email-masked]
Subject: Re: [dtn-interest] Planning for the Disconnectathon

On Thu, Jun 25, 2009 at 09:10:27AM -0400, Daniel Ellard wrote:
> It's time to make concrete plans for the "Disconnectathon"
> that we proposed for the end of the July (located split
> between the IETF meeting in Stockholm and BBN in Cambridge).
>  The goal of the event is to demonstrate interoperability
> between DTN implementations.

I was just the other day having some mail exchanges with Jeorg on this
topic.  I volunteered to help with organizing this on the Stockholm
end.  I will be there.  I do not have an independent implementation of
the stack or anything of the sort.  I'm willing to bring such tiny
amounts of equipment as I have, and perform any grunt work needed.

A

-- 
Andrew Sullivan
[email-masked]
Shinkuro, Inc.

From: "Ivancic, William D. (GRC-RHN0)" <[email-masked]>
To: Daniel Ellard <[email-masked]>, "[email-masked]" <[email-masked]>
Date: Thu, 25 Jun 2009 09:42:42 -0500
Accept-Language: en-US
acceptlanguage: en-US
Subject: Re: [dtn-interest] Planning for the Disconnectathon

Dan,

What day(s)?  DTNRG currently is scheduled to meet on Friday, July 31.

NASA has been running DTN interoperability between DTN-2 and ION on our internal testbeds.  Currently the only thing that is interoperable between ION and DTN-2 is DTN-2 naming scheme using static routes over UDP.  

Ohio University is working on the TCPCL for ION and DTN-2.

JPL is working on the ability to at least sort of map DTN-2 to an ION naming scheme to do contract graph routing and the LTP configuration of ION are expected to change soon.

What we really need is an common API for applications.

Has anybody coded for the newly proposed naming scheme?  But, I think if one does not understand a naming scheme, one can dump it which means there is no real scheme here, just syntax.  
http://tools.ietf.org/html/draft-irtf-dtnrg-dtn-uri-scheme-00

Will

******************************
William D. Ivancic
Phone 216-433-3494
Fax 216-433-8705
Networking Lab 216-433-2620
DTN Lab 216-433-2981
Mobile 440-503-4892
http://roland.grc.nasa.gov/~ivancic 

>-----Original Message-----
>From: [email-masked] [mailto:dtn-
>[email-masked]] On Behalf Of Daniel
>Ellard
>Sent: Thursday, June 25, 2009 9:10 AM
>To: [email-masked]
>Subject: [dtn-interest] Planning for the Disconnectathon
>
>It's time to make concrete plans for the "Disconnectathon"
>that we proposed for the end of the July (located split
>between the IETF meeting in Stockholm and BBN in Cambridge).
> The goal of the event is to demonstrate interoperability
>between DTN implementations.
>
>The key questions are:
>
>1.  Are you planning to attend?  Which location?  (I need to
>get a head count for each location, so if you're speaking
>for a group of people, please tell me how many heads there are)
>
>2.  Are you planning to bring an implementation of the DTN
>stack?  (Note that it's not strictly necessary to "bring" a
>node physically, but there needs to be an instance or two
>accessible from the internet.)
>
>3.  What applications can we/should we run at the
>Disconnectathon?  Do you have applications you can
>contribute and/or are you interested in collaborating to
>develop such applications?
>
>If possible, please answer soon, even if you don't have all
>the answers yet, so we can gauge interest and begin planning.
>
>Thanks,
>	-Dan
>
>--
>Daniel Ellard, Ph.D.
>Senior Scientist, Network Research
>BBN Technologies
>10 Moulton Street
>Cambridge, MA 02138
>[email-masked]
>_______________________________________________
>dtn-interest mailing list
>[email-masked]
>http://maillists.intel-research.net/mailman/listinfo/dtn-interest

Date: Thu, 25 Jun 2009 09:10:27 -0400
From: Daniel Ellard <[email-masked]>
Organization: BBN Technologies
To: "[email-masked]" <[email-masked]>
Subject: [dtn-interest] Planning for the Disconnectathon

It's time to make concrete plans for the "Disconnectathon"
that we proposed for the end of the July (located split
between the IETF meeting in Stockholm and BBN in Cambridge).
 The goal of the event is to demonstrate interoperability
between DTN implementations.

The key questions are:

1.  Are you planning to attend?  Which location?  (I need to
get a head count for each location, so if you're speaking
for a group of people, please tell me how many heads there are)

2.  Are you planning to bring an implementation of the DTN
stack?  (Note that it's not strictly necessary to "bring" a
node physically, but there needs to be an instance or two
accessible from the internet.)

3.  What applications can we/should we run at the
Disconnectathon?  Do you have applications you can
contribute and/or are you interested in collaborating to
develop such applications?

If possible, please answer soon, even if you don't have all
the answers yet, so we can gauge interest and begin planning.

Thanks,
	-Dan

-- 
Daniel Ellard, Ph.D.
Senior Scientist, Network Research
BBN Technologies
10 Moulton Street
Cambridge, MA 02138
[email-masked]

From: "Suganthe R C" <[email-masked]>
To: "[email-masked]" <[email-masked]>
Date: 24 Jun 2009 06:12:47 +0000
Subject: [dtn-interest] A little gift - Suganthe
Reply-To: Suganthe R C <[email-masked]>

Suganthe R C belongs to Skoost and sent you a little gift.

Click below to collect your gift:
http://www.skoost.com/fun?dtn%2Dinterest%40mailman%2Edtnrg%2Eorg/20546819/5

P.S. This is a safe and innocent gift that Suganthe R C
sent from Skoost, the free goodies website.

This e-mail was sent to [email-masked] on 6/24/2009 7:10:59 AM
on behalf of Suganthe R C ([email-masked])

From: "Eddy, Wesley M. (GRC-MS00)[Verizon]" <[email-masked]>
To: "[email-masked]" <[email-masked]>
Date: Tue, 23 Jun 2009 09:23:01 -0500
Accept-Language: en-US
acceptlanguage: en-US
Cc: Rui Chilro <[email-masked]>
Subject: [dtn-interest] FW: simple sugestions to draft-irtf-dtnrg-sdnv-01...

I received permission from Rui to reply to this on the DTNRG list:

>-----Original Message-----
>From: Rui Chilro [mailto:[email-masked]]
>Sent: Wednesday, June 17, 2009 10:14 PM
>To: [email-masked]
>Subject: simple sugestions to draft-irtf-dtnrg-sdnv-01...
>
> ...
>
>I've read your draft about SDNV representation and have 2 simple
>sugestions
>to:
>- while i was doing an implementation in PHP the decompression didn't
>return
>the right values in the end. after the debuging steps i noticed that the
>padded 0 changed the result. so i suggest that adding some indication
>about
>the added bits to complete the representation would help to understand
>the
>examples

We do have some text about zero-padding at the end of section 2, but do
you think it needs to be more clear or the point repeated in the decoding
description?

>- i understand that the code is just an example but since this is to be
>inserted in rush environments, the validation of the initial SDNV number
>(mod 8=0) in the decoding would prevent further problems, spare future
>processing of the string.

Ok; I guess the goal is just to skip quickly through any left zero-padding
within the encoding.  This seems reasonable to add.

>the idea was proposed back on the first draft of the DTN so i wonder why
>it
>was never put to RFC?
>
>Thanks for the oportunity and hope this helps

SDNVs are part of RFC 5050 and 5325, but they gloss over some of the
motivations and detailed discussion of SDNVs that this draft covers; as
discussed in the draft, there were alternative encodings with some
trade-offs that were discussed in the DTNRG, but the design decisions
that wound up codified in the protocols are not discussed outside the
SDNV draft.

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

From: "Ivancic, William D. (GRC-RHN0)" <[email-masked]>
To: "[email-masked]" <[email-masked]>
Date: Mon, 22 Jun 2009 15:09:48 -0500
Accept-Language: en-US
acceptlanguage: en-US
Subject: [dtn-interest] Network Management Subgroup - Teleconference Meeting Notes for 22 June 2009

DTN Network Management - Collaborators
Meeting Notes for
Monday, June 22, 2009
1:00 - 2:00 EST (18:00 - 19:00 UTC)

A teleconference was held on Monday, June 22, 2009.
These notes are to document this teleconference.

The next teleconference will be Monday, July 6. 

Participants
=============
•	BBN - Cambridge
•	Hans Kruse  - Ohio University
•	Will Ivancic, Jim McKim – NASA Glenn
•	Scott Burleigh – NASA JPL
•	Keith Scott – MITRE
•	Simon.Perreault – Viagenie
•	Lloyd Wood

Agenda
=========
* Feedback on Requirements Document.
http://www.ietf.org/internet-drafts/draft-ivancic-dtnrg-network-management-reqs-00.txt
 - So far little input.  Some question of SHOULDs maybe should be changed to MUSTs.
 - Currently modifications to grammar and such have been worked but have not been submitted yet pending further modifications
 - Perhaps a discussion in Stockholm (my foreign travel has been submitted and I think will be approved).

* Jim McKim (NASA Glenn) - Summary of SNMP work and MIB modifications

* Other issues

=============================
Requirements Document Discussion
-	Ivancic:  Changed order such that requirements come before DTN Characteristics
o	Kruse:  Seems to flow fine in that order
-	Kruse: Document jumps into requirements without an explanation of what the think a network management system is.  We probably should define what we view as a DTN network management system from operations to end system.
-	General Network Management versus Bundle Protocol specific:
o	In order to make this usable for other disconnected technologies, not just the RFC4838 RFC5050 view perhaps indicate requirements that are 5050-based and those that are really generic.
o	Scenarios are definitely generic to and store-and-forward implementation.
-	Kruse:  All the currently specified key parameters for the TCPCL are currently optional.  
o	Ivancic: Used what was in internet drafts as starting point for discussion and open to suggestions.

Network Management Implementation
-	Jim McKim reported that he has been working with BBNs proposed MIBs and found issues that required some modifications
o	Some variables used the same OID and had to be corrected accordingly.
o	Used smilint to evaluate DTN MIBs
o	Add more definition to particular MIBs (e.g. Unsigned integer, long integer, etc...)
o	IMPORTANT NOTE:  SNMP has character restriction of 256 bytes which may cause issues for long URI lengths.
-	BBN is also working MIBs implementation for Spindle III and will get in touch with Jim McKim to discuss lessons learned by both parties.
-	Ohio University has two teams looking at DTN Network Management
o	One team is looking at how to take current SNMP network management platforms and make them work for DTN
	One main issue is SNMP default assumes ip-address-based systems whereas DTN is name-based.
o	Second team is looking at deployment of snmp gateway where the gateway sits between and snmp manager and DTN end systems and does the necessary conversion to bride between the operations of an IP-base snmp network management system and a DTN-based system.
	BBN is looking as something similar and will be getting in touch with OU in order to reduce or eliminate duplication.
Other
-	Ivancic: Quarried group regarding who has done remote operations an configuration. 
o	Most on the teleconference had, and understand the pain we will be experiencing in the future.
o	Multiple parties indicated they have locked themselves out of the remote system.
	This is a Major Concern – how to recover from foreseen, unforeseen mistakes – we know it will happen as many of us have done so.

/Will

Date: Mon, 22 Jun 2009 16:44:22 +0200
From: Anders Lindgren <[email-masked]>
To: [email-masked], [email-masked]
Subject: [dtn-interest] Call for Participation: ExtremeCom 2009

CALL FOR PARTICIPATION
ExtremeCom 2009 - The Midnight Sun Expedition
http://extremecom.org/

The Extreme Workshop on Communication (ExtremeCom) intends to bring
together researchers and practitioners in areas related to delay
tolerant networks and other networking paradigms for rural and remote
areas, in order to gain experience and insight into the challenges
that such environments pose for the network and the users.

We are happy to announce that the registration for the ExtremeCom 2009
workshop is now open. Please go to the workshop web page at
http://extremecom.org/ to register. Please also make sure that you
carefully read the information about local arrangements and travel
arrangements.

Due to limited local resources and the need to conduct the workshop in
harmony with the local population, attendance will be limited. Thus,
we encourage people to register as soon as possible.

We are very much looking forward to seeing you in Padjelanta in August.

Best regards,

Anders and Ben, general co-chairs ExtremeCom 2009

Date: Thu, 18 Jun 2009 09:23:22 -0700 (PDT)
From: [email-masked]
To: [email-masked]
Cc: [email-masked]
Subject: [dtn-interest] Draft Response Version one
Reply-To: [email-masked]

--0-392600852-1245342202=:72341
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

Dear, Esteemed DTN=A0Forum Professionals
=A0
=A0 As I start to read=A0the new draft=A0of material which was presented to=
 the forum within the past two weeks I have a question in relation towards =
the DTNRG bundles package, and=A0the high-propagation-delay networking envi=
ronement of deep space.=A0 First, when these environments are interrupted=
=A0 they are=A0monitored by the CRC within the TCP and the networking layer=
 itself so my guess would be to=A0base the IP table or tables deployment sc=
heduling=A0off both of these=A0 forms of error correction / flow control mo=
reover; these TCP handshakes are what I would primarily base these IP sched=
ules off of and utilize the CRC to provide business continuity in the form =
of fault-tolerance=A0by the utilization of the redundancy check itself sinc=
e it would be beneficial to the whole IP stack and the communication=A0proc=
essing itself.=A0=A0=A0
=A0 Secondly, as I read further into the document are the MER UHF transmiss=
ions in particular MER B=A0Sol 450 =A0based on=A0 lack of solar activity su=
ch as sunspots or solar flares.=A0 The reason I am asking this is due in pa=
rt to the inability to transmit when high levels of=A0 solar activity occur=
 thuse, making the transmissions less robust in relation in towards Mbits a=
re recieved based on the DTE/DFE link created by the actual transmissions.=
=A0 Does the Link 1 protocol govern the fault-tolerance I was speaking upon=
 in the above text or s it a separate function which is only available when=
 data collecting? Also does the link 1 protocol ever have the vulnerability=
 within the WTLS of being deficient in regards=A0to the initialization vect=
or (IV)=A0and MAC within WEP?=A0 I will be sending more datum in regards to=
wards the Draft in the near future to the forum as continue to read more in=
formatics which encompass DTN.
=A0
Very Respectfully=A0=A0=A0=20

Savanted1=A9Mr. Garrett Hord=20
Towson University Computer Science / Mathematics
ACFE Associate Member
ACP International
Infragard Baltimore Chapter
__|__=20
-@--@--(_)--@--X--=20
[email-masked]
[email-masked]
[email-masked]
Engineering Science To Watch All Networks
http://www.securitytalks.com http://spaces.msn.com/members/savantedlyspeaki=
ng/
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
FOR OFFICIAL USE ONLY: This message may contain personnel data or informati=
on covered by the Privacy Act of 1974. Please ensure this information is pr=
otected from unauthorized access and/or disclosure.=20
This electronic message contains information which may be privileged and/or=
 confidential. The information is intended for use only by the individual(s=
) or entity named/indicated above. If you are not the identified/intended r=
ecipient, be aware that any disclosure, copying, distribution, or use of th=
e contents of this message/information is prohibited.=0A=0A=0A      
--0-392600852-1245342202=:72341
Content-Type: text/html; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

<table cellspacing=3D"0" cellpadding=3D"0" border=3D"0" ><tr><td valign=3D"=
top" style=3D"font: inherit;"><DIV id=3Dyiv95708150>
<DIV>Dear, Esteemed DTN&nbsp;Forum Professionals</DIV>
<DIV>&nbsp;</DIV>
<DIV>&nbsp; As I start to read&nbsp;the new draft&nbsp;of material which wa=
s presented to the forum within the past two weeks I have a question in rel=
ation towards the DTNRG bundles package, and&nbsp;the high-propagation-dela=
y networking environement of deep space.&nbsp; First, when these environmen=
ts are interrupted&nbsp; they are&nbsp;monitored by the CRC within the TCP =
and the networking layer itself so my guess would be to&nbsp;base the IP ta=
ble or tables deployment scheduling&nbsp;off both of these&nbsp; forms of e=
rror correction / flow control moreover; these TCP handshakes are what I wo=
uld primarily base these IP schedules off of and utilize the CRC to provide=
 business continuity in the form of fault-tolerance&nbsp;by the utilization=
 of the redundancy check itself since it would be beneficial to the whole I=
P stack and the communication&nbsp;processing itself.&nbsp;&nbsp;&nbsp;</DI=
V>
<DIV>&nbsp; Secondly, as I read further into the document are the MER UHF t=
ransmissions in particular MER B&nbsp;Sol 450 &nbsp;based on&nbsp; lack of =
solar activity such as sunspots or solar flares.&nbsp; The reason I am aski=
ng this is due in part to the inability to transmit when high levels of&nbs=
p; solar activity occur thuse, making the transmissions less robust in rela=
tion in towards Mbits are recieved based on the DTE/DFE link created by the=
 actual transmissions.&nbsp; Does the Link 1 protocol govern the fault-tole=
rance I was speaking upon in the above text or s it a separate function whi=
ch is only available when data collecting? Also does the link 1 protocol ev=
er have the vulnerability within the WTLS of being deficient in regards&nbs=
p;to the initialization vector (IV)&nbsp;and MAC within WEP?&nbsp; I will b=
e sending more datum in regards towards the Draft in the near future to the=
 forum as continue to read more informatics which encompass
 DTN.</DIV>
<DIV>&nbsp;</DIV>
<DIV>Very Respectfully&nbsp;&nbsp;&nbsp; <BR><BR>Savanted1=A9Mr. Garrett Ho=
rd <BR>Towson University Computer Science / Mathematics<BR>ACFE Associate M=
ember<BR>ACP International<BR>Infragard Baltimore Chapter<BR>__|__ <BR>-@--=
@--(_)--@--X-- <BR>[email-masked]<BR>[email-masked]<BR>savanted=
[email-masked]<BR>Engineering Science To Watch All Networks<BR>http://www.s=
ecuritytalks.com http://spaces.msn.com/members/savantedlyspeaking/<BR>=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D<BR>FOR OFFI=
CIAL USE ONLY: This message may contain personnel data or information cover=
ed by the Privacy Act of 1974. Please ensure this information is protected =
from unauthorized access and/or disclosure. <BR>This electronic message con=
tains information which may be privileged and/or confidential. The informat=
ion is intended for use only by the individual(s) or entity named/indicated=
 above. If you are not the identified/intended recipient, be
 aware that any disclosure, copying, distribution, or use of the contents o=
f this message/information is prohibited.</DIV></DIV></td></tr></table><br>=
=0A=0A=0A=0A      
--0-392600852-1245342202=:72341--

Date: Thu, 18 Jun 2009 10:59:53 +0100
From: Paulo Mendes <[email-masked]>
To: [email-masked]
Subject: [dtn-interest] CFP: U-NET'09 (User-provided networking) workshop, co-located with ACM CoNext

(Appologies if you get this twice)

ACM U-NET'09 � User-provided Networking: Challenges and Opportunities
Co-located with ACM CoNEXT 2009
Rome, Italy, December 1, 2009
http://conferences.sigcomm.org/co-next/2009/workshops/unet/

Submission Deadline: July 17, 2009
Submit at: http://edas.info/N7753

*(Now with a Technical Panel)*

*Motivation*

This workshop is dedicated to the debate of concepts, challenges, and 
opportunities concerning user-provided networking, i.e., scenarios where 
users cooperate by sharing wireless resources as well as Internet services.
To provide a specific example that relates to Internet access 
(connectivity), the end-user (or a community of end-users) is a 
micro-operator in the sense that he/she shares his/her subscribed 
broadband Internet access based on some form of incentive scheme. In 
addition, the end-user may or may not provide other network 
functionality such as local mobility management, or persistent storage 
and forwarding services. This new role is disruptive in what concerns 
Internet service models, since there is no distinction between what is 
today known as end-user device and network device: in the future, 
end-user devices will actively participate as part of the network. In 
contrast, the Internet has been up to now mostly the means for end-users 
to obtain some form of network service, originally related to 
connectivity, person-to-person communication, or information retrieval. 
Such user-centric provider role is also disruptive given that the 
regular network boundaries of trust have to be extended in a way that 
should mimic social behavior: there is the need to form networks of 
trust in order to accommodate a robust network growth, given that the 
key to such growth is the willingness to cooperate.

Another disruptive aspect of user-provided networking is that due to the 
nature of the wireless media and the way that humans move, support for 
intermittent connectivity as well as fast and transparent roaming 
between micro-operators needs to be considered. Finally, and given that 
user-provided networking spreads dynamically having as network elements 
regular end-user devices, there is the need to consider cases where 
information is opportunistically relayed instead of routed based on 
topological information.

Due to the disruptive aspects mentioned, user-provided networking seem 
to have the potential to provide a paradigm shift in Internet 
communication models, given that such novel functionality allow wireless 
networks to operate in a completely autonomic way and also given that 
the end-user becomes a provider of Internet services (e.g. connectivity) 
based upon cooperation incentives or rewards and based upon his/her own 
mobility and social patterns. Services are established on the fly, and 
do not necessarily imply the use of multihop technology or routing. For 
instance, connectivity may be, in most cases, simply relayed.

The workshop program will include presentations of peer-reviewed papers 
and a discussion panel with guests from industry and academia. We 
envision U-NET as a forum aiming to ignite a debate concerning technical 
challenges and impact (negatively or positively) that user-provided 
networking may have on Internet communication models.

*Topics*

U-NET'09 solicits high quality technical contributions within the 
context of user-provided networking. Topics of interest include but are 
not limited to:

* Challenges and opportunities for access providers.
* Impact on Internet architectures.
* Internet connectivity.
* Trust models, incentives to share broadband access.
* Human behaviour and mobility patterns.
* Self-organization.
* Wireless cooperation.

Papers submitted are expected to be highly innovative and may 
incorporate early stage ideas; position papers (clearly identified as 
such) pointing to new directions and capable of generating discussion 
are also welcome. Submission must be original and not already published 
in any other conference proceeding or journal. Proceedings of the 
workshop will be published in the ACM Digital Library.

*Technical Panel Discussion*

U-NET'09 aims to be a forum to debate the technical challenges and 
impact of deploying user-provided networking technology. For this 
propose, this first edition of U-NET will host a technical discussion 
panel constituted by:

* Shivendra S. Panwar, Professor at Polytechnic Institute of New York 
University, USA
* James Kempft, Senior Architect at Ericsson Research, USA
* David Kennedy, Director at Eurescom GmbH, Germany
* Jordi Vallejo, CTO at FON Wireless Ltd, Spain
* David Trossen, Chief Researcher at British Telecom Innovate, United 
Kingdom

*Submissions*

Submitted papers must be at most 6 (six) pages long (including figures, 
tables and references) in the standard ACM double column format. All 
text must use font sizes of 10 points or larger. Longer submissions will 
not be reviewed. The review process is single-blind. Submissions will be 
done via EDAS at http://edas.info/N7753.

*Important Dates*

Submissions due: July 17, 2009
Notification of acceptance: September 4, 2009
Camera ready version due: October 1, 2009
Workshop date: December 1, 2009

*Program Committee*

PC Chairs

Paulo Mendes, INESC Porto, Portugal
Olivier Marc�, Alcatel-Lucent Bell Labs, France

Technical Program Committee

Rute Sofia, INESC Porto, Portugal
Andr� Z�quete, University of Aveiro, Portugal
Vassilis Kostakos, University of Madeira, Portugal
Jon Crowcroft, University of Cambridge, United Kingdom
Cecilia Mascolo, University of Cambridge, United Kingdom
Eiko Yoneki, University of Cambridge, United Kingdom
Dirk Trossen, British Telecom Innovate, United Kingdom
Prosper Chemouli, France Telecom, France
Martin May, Thomson Paris Research Laboratory, France
Karen Sollins, MIT, USA
Lixia Zhang, UCLA, USA
James Kempf, Ericsson Research, USA
Dipankar Raychaudhuri, Rutgders University, USA
Bernhard Plattner, ETH, Switzerland
George Polyzos, Athens University of Economics and Business, Greece
Maria Papadopouli, FORTH/University of Creete, Greece
Anand Prasand, NEC, Japan
Gunnar Karlsson, KTH, Sweden
Yevgeni Koucheryavy, Tampere University of Technology, Finland
Marcus Brunner, NEC, Germany
Petri M�h�nen, RWTH Aachen University, Germany

-- 
-----------------------------------------------------
Paulo Mendes, Ph.D
Area Leader, Internet Architectures and Networking
Telecommunication and Multimedia Unit
INESC Porto
Tel. +351 22 209 4264
Fax. +351 22 209 4050
http://ian.inescporto.pt

Content-class: urn:content-classes:message
Date: Wed, 17 Jun 2009 18:04:06 +0100
From: <[email-masked]>
To: <[email-masked]>
Subject: [dtn-interest] Deadline Extension - E-DTN '09: Workshop on the Emergence of Delay-/Disruption-Tolerant Networking

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9EF6D.9FD8565D
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Dear colleagues,

please check the new hard submission deadline for E-DTN '09.

Thanks,
Ioannis Psaras.

************************************************************************
CALL FOR PAPERS

Workshop on the Emergence of Delay-/Disruption-Tolerant Networks (E-DTN)

Technically Sponsored by IEEE

NEW IMPORTANT DATES:

Paper-submission Deadline: July 6, 2009
Acceptance Notification: July 31, 2009

Dates: TBA
October, 2009, St.-Petersburg, Russia
(in conjunction with ICUMT 2009)
[Web: http://www.e-dtn.org/]
************************************************************************

Networking research for challenged environments has attracted
a lot of attention lately. Numerous attractive protocols have
been proposed, which are expected to network places and devices that
currently do not have the opportunity of "going online". Such
environments reside at the edges of the current Internet infrastructure.
For example, public and private transport vehicles, underwater, =
satellite and
deep-space networks are potential DTN deployments of interest.
Communication in the above-mentioned challenged environments is usually
infrastructureless and consists mainly of mobile battery-powered
devices. Moreover, mobility patterns are usually unknown, making
connectivity periods between DTN-nodes intermittent and opportunistic.
To achieve communication in such environments one has to deal with
several performance tradeoffs, such as end-to-end delivery delay and
energy consumption, or reliability and storage congestion.
Since, in most cases, end-to-end connectivity does not exist (hence the
difference from ad hoc networking) current Internet protocols
fail permanently.

Although there have already been a lot of research proposals for
routing, (storage) congestion control, error control and
application design for such networks, the IRTF has
focused mainly on the Bundle Protocol (BP); BP is an application
layer protocol that does not include the appropriate functionalities to
deal with issues such as routing or storage congestion, for example. =
That
said, DTN research and its future directions seem to lack a stable
basis. For example, it is not clear yet if a "one-fits-all" protocol
stack will be deployed, or if such an approach is feasible at all.
In contrast, several different protocols that each would suit the needs
of its specific architecture/setup would need to be able to =
interoperate.

This workshop seeks novel ideas in the form of preliminary or =
work-in-progress
results as well as mature research papers for Delay-/Disruption
Tolerant Networks. We also encourage position papers that address and=20
criticize the past, current and future trends of DTN research and are=20
intended to trigger discussions on the whole spectrum of DTNs.=20
Topics include but are not limited to:

- DTN Routing
- Congestion and Storage Congestion Control
- Resource Sharing in DTN environments
- Network Coding techniques for DTNs
- Application Development
- DTN Management Platforms
- Error and Flow Control
- Experiences and Measurements from DTN testbeds
- Privacy and Security of Information in DTNs
- DTN Simulators and related tools
- Performance Evaluation and Metrics for DTN Research
- Performance and Design Tradeoffs for DTN Algorithms and Protocols
- Social Networking through DTNs
- Satellite Constellations and DTNs
- Naming/Addressing and interoperability issues with the Internet =
architecture
- DTN Architectures:
-- Satellite Communications
-- Deep-space Communications
-- Underwater Communications
-- Connectivity in Developing Countries
-- Communication in Public and Private Transport Vehicles

NEW IMPORTANT DATES:

Paper-submission Deadline: July 6, 2009
Acceptance Notification: July 31, 2009

SUBMISSION GUIDELINES:

Submitted papers must be original in content, not published or=20
submitted to another workshop, conference or journal.

Page-limits are as follows:
Position Papers: 2 pages,
Work-in-Progress Papers: 4 pages and
Full Papers: 6 pages.

Authors should prepare a PDF file following the IEEE single-spaced,=20
double-column page-style, using 10 pt size fonts on 8.5X11 inch pages.=20
Page-limits include text, figures, references and appendices.=20

A selection of the best papers will be invited for a special issue on =
the=20
Emergence of Delay-/Disruption-Tolerant Networks in the Journal of=20
Internet Engineering [http://www.jie-online.org].

WORKSHOP CHAIRS

General Co-Chairs:
	* Vassilis Tsaoussidis, Democritus University of Thrace, Greece/MIT, =
USA
	* Saverio Mascolo, Polytechnic of Bari, Italy

TPC Co-Chairs:
	* Lefteris Mamatas, University College London, UK
	* Ioannis Psaras, University of Surrey, UK

Workshop TPC:
	* Scott Burleigh, NASA/JPL, USA
	* Wei Koong Chai, UCL, UK=20
	* Stylianos Dimitriou, Democritus University of Thrace, Greece
	* Wesley Eddy, Verizon/NASA GRC, USA
        * Zygmunt Haas, Cornell University, USA=20
	* Peter Holliday, Cisco Systems, Australia
	* Pan Hui, Deutsche Telekom Laboratories, Germany
	* Merkourios Karaliopoulos, ETH Zurich, Switzerland=20
	* Lefteris Mamatas, UCL, UK
	* Saverio Mascolo, Politecnico di Bari, Italy
	* Ibrahim Matta, Boston University, USA=20
	* Paulo Mendes, INESC-Porto, Portugal=20
	* Panagiotis Papadimitriou, Lancaster University, UK=20
	* Giorgos Papastergiou, Hellenic Aerospace Industry, Greece
	* Ioannis Psaras, University of Surrey, UK
	* Christos V. Samaras, Democritus University of Thrace, Greece
	* Keith Scott, MITRE Corporation, USA=20
	* Dimitrios Serpanos, University of Patras, Greece
	* Thrasyvoulos Spyropoulos, ETH Zurich, Switzerland=20
	* Vassilis Tsaoussidis, Democritus University of Thrace, Greece/MIT, =
USA
	* Lloyd Wood, University of Surrey/Cisco Systems, UK=20
	* Eiko Yoneki, University of Cambridge, UK
	* Chi Zhang, Juniper Networks, USA

------_=_NextPart_001_01C9EF6D.9FD8565D
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>Deadline Extension - E-DTN '09: Workshop on the Emergence of  =
Delay-/Disruption-Tolerant Networking</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Dear colleagues,<BR>
<BR>
please check the new hard submission deadline for E-DTN '09.<BR>
<BR>
Thanks,<BR>
Ioannis Psaras.<BR>
<BR>
************************************************************************<=
BR>
CALL FOR PAPERS<BR>
<BR>
Workshop on the Emergence of Delay-/Disruption-Tolerant Networks =
(E-DTN)<BR>
<BR>
Technically Sponsored by IEEE<BR>
<BR>
NEW IMPORTANT DATES:<BR>
<BR>
Paper-submission Deadline: July 6, 2009<BR>
Acceptance Notification: July 31, 2009<BR>
<BR>
Dates: TBA<BR>
October, 2009, St.-Petersburg, Russia<BR>
(in conjunction with ICUMT 2009)<BR>
[Web: <A HREF=3D"http://www.e-dtn.org/">http://www.e-dtn.org/</A>]<BR>
************************************************************************<=
BR>
<BR>
Networking research for challenged environments has attracted<BR>
a lot of attention lately. Numerous attractive protocols have<BR>
been proposed, which are expected to network places and devices that<BR>
currently do not have the opportunity of &quot;going online&quot;. =
Such<BR>
environments reside at the edges of the current Internet =
infrastructure.<BR>
For example, public and private transport vehicles, underwater, =
satellite and<BR>
deep-space networks are potential DTN deployments of interest.<BR>
Communication in the above-mentioned challenged environments is =
usually<BR>
infrastructureless and consists mainly of mobile battery-powered<BR>
devices. Moreover, mobility patterns are usually unknown, making<BR>
connectivity periods between DTN-nodes intermittent and =
opportunistic.<BR>
To achieve communication in such environments one has to deal with<BR>
several performance tradeoffs, such as end-to-end delivery delay and<BR>
energy consumption, or reliability and storage congestion.<BR>
Since, in most cases, end-to-end connectivity does not exist (hence =
the<BR>
difference from ad hoc networking) current Internet protocols<BR>
fail permanently.<BR>
<BR>
Although there have already been a lot of research proposals for<BR>
routing, (storage) congestion control, error control and<BR>
application design for such networks, the IRTF has<BR>
focused mainly on the Bundle Protocol (BP); BP is an application<BR>
layer protocol that does not include the appropriate functionalities =
to<BR>
deal with issues such as routing or storage congestion, for example. =
That<BR>
said, DTN research and its future directions seem to lack a stable<BR>
basis. For example, it is not clear yet if a &quot;one-fits-all&quot; =
protocol<BR>
stack will be deployed, or if such an approach is feasible at all.<BR>
In contrast, several different protocols that each would suit the =
needs<BR>
of its specific architecture/setup would need to be able to =
interoperate.<BR>
<BR>
This workshop seeks novel ideas in the form of preliminary or =
work-in-progress<BR>
results as well as mature research papers for Delay-/Disruption<BR>
Tolerant Networks. We also encourage position papers that address =
and<BR>
criticize the past, current and future trends of DTN research and =
are<BR>
intended to trigger discussions on the whole spectrum of DTNs.<BR>
Topics include but are not limited to:<BR>
<BR>
- DTN Routing<BR>
- Congestion and Storage Congestion Control<BR>
- Resource Sharing in DTN environments<BR>
- Network Coding techniques for DTNs<BR>
- Application Development<BR>
- DTN Management Platforms<BR>
- Error and Flow Control<BR>
- Experiences and Measurements from DTN testbeds<BR>
- Privacy and Security of Information in DTNs<BR>
- DTN Simulators and related tools<BR>
- Performance Evaluation and Metrics for DTN Research<BR>
- Performance and Design Tradeoffs for DTN Algorithms and Protocols<BR>
- Social Networking through DTNs<BR>
- Satellite Constellations and DTNs<BR>
- Naming/Addressing and interoperability issues with the Internet =
architecture<BR>
- DTN Architectures:<BR>
-- Satellite Communications<BR>
-- Deep-space Communications<BR>
-- Underwater Communications<BR>
-- Connectivity in Developing Countries<BR>
-- Communication in Public and Private Transport Vehicles<BR>
<BR>
<BR>
NEW IMPORTANT DATES:<BR>
<BR>
Paper-submission Deadline: July 6, 2009<BR>
Acceptance Notification: July 31, 2009<BR>
<BR>
SUBMISSION GUIDELINES:<BR>
<BR>
Submitted papers must be original in content, not published or<BR>
submitted to another workshop, conference or journal.<BR>
<BR>
Page-limits are as follows:<BR>
Position Papers: 2 pages,<BR>
Work-in-Progress Papers: 4 pages and<BR>
Full Papers: 6 pages.<BR>
<BR>
Authors should prepare a PDF file following the IEEE single-spaced,<BR>
double-column page-style, using 10 pt size fonts on 8.5X11 inch =
pages.<BR>
Page-limits include text, figures, references and appendices.<BR>
<BR>
A selection of the best papers will be invited for a special issue on =
the<BR>
Emergence of Delay-/Disruption-Tolerant Networks in the Journal of<BR>
Internet Engineering [<A =
HREF=3D"http://www.jie-online.org">http://www.jie-online.org</A>].<BR>
<BR>
WORKSHOP CHAIRS<BR>
<BR>
General Co-Chairs:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Vassilis Tsaoussidis, =
Democritus University of Thrace, Greece/MIT, USA<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Saverio Mascolo, =
Polytechnic of Bari, Italy<BR>
<BR>
TPC Co-Chairs:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Lefteris Mamatas, =
University College London, UK<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Ioannis Psaras, University =
of Surrey, UK<BR>
<BR>
Workshop TPC:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Scott Burleigh, NASA/JPL, =
USA<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Wei Koong Chai, UCL, UK<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Stylianos Dimitriou, =
Democritus University of Thrace, Greece<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Wesley Eddy, Verizon/NASA =
GRC, USA<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Zygmunt Haas, Cornell =
University, USA<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Peter Holliday, Cisco =
Systems, Australia<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Pan Hui, Deutsche Telekom =
Laboratories, Germany<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Merkourios Karaliopoulos, =
ETH Zurich, Switzerland<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Lefteris Mamatas, UCL, =
UK<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Saverio Mascolo, =
Politecnico di Bari, Italy<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Ibrahim Matta, Boston =
University, USA<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Paulo Mendes, INESC-Porto, =
Portugal<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Panagiotis Papadimitriou, =
Lancaster University, UK<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Giorgos Papastergiou, =
Hellenic Aerospace Industry, Greece<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Ioannis Psaras, University =
of Surrey, UK<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Christos V. Samaras, =
Democritus University of Thrace, Greece<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Keith Scott, MITRE =
Corporation, USA<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Dimitrios Serpanos, =
University of Patras, Greece<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Thrasyvoulos Spyropoulos, =
ETH Zurich, Switzerland<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Vassilis Tsaoussidis, =
Democritus University of Thrace, Greece/MIT, USA<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Lloyd Wood, University of =
Surrey/Cisco Systems, UK<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Eiko Yoneki, University of =
Cambridge, UK<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Chi Zhang, Juniper =
Networks, USA</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C9EF6D.9FD8565D--

From: Farzana Yasmeen <[email-masked]>
To: <[email-masked]>
Date: Fri, 12 Jun 2009 16:13:28 +0900 (JST)
Subject: [dtn-interest] DTNSim2 documentation

Hello,

Can anyone guide me to where I may find documentation regarding the DTNSim2 simulator?
All I could find for the moment was this:
http://watwire.uwaterloo.ca/DTN/sim/

Any feedback would be appreciated.

Thanks and regards,
Farzana Yasmeen

From: "Symington, Susan F." <[email-masked]>
To: DTN <[email-masked]>
Date: Thu, 11 Jun 2009 14:43:08 -0400
Accept-Language: en-US
acceptlanguage: en-US
Subject: [dtn-interest] FW: New Version Notification for draft-irtf-dtnrg-bundle-previous-hop-block-07

DTNRG members:

I just revised the Previous Hop Insertion Block I-D to use more precise language when referring to EIDs, as pointed out in comments by Scott Burleigh and Wesley Eddie. (Thank you for your input, gentlemen.)

Since the DTNRG, the Previous Hop Insertion Block I-D has been updated to state that the previous hop block can identify the EID of an endpoint of which the node inserting the block is a member in one of two ways:
1) either using the EID reference count and references field, or
2) using block-specific scheme name and SSP fields.

A node can use the EID reference count and references field to reference the EID only if that EID is already in the dictionary; a node cannot put an EID into the dictionary if the only block that is going to reference it is the previous hop block.

-susan

*****************************************************************
Susan Symington
The MITRE Corporation
[email-masked]
703-983-7209 (voice)
703-983-7142 (fax)
******************************************************************
>-----Original Message-----
>From: IETF I-D Submission Tool [mailto:[email-masked]]
>Sent: Thursday, June 11, 2009 2:36 PM
>To: Symington, Susan F.
>Subject: New Version Notification for draft-irtf-dtnrg-bundle-previous-
>hop-block-07
>
>
>A new version of I-D, draft-irtf-dtnrg-bundle-previous-hop-block-07.txt
>has been successfuly submitted by Susan Symington and posted to the IETF
>repository.
>
>Filename:	 draft-irtf-dtnrg-bundle-previous-hop-block
>Revision:	 07
>Title:		 Delay-Tolerant Networking Previous Hop Insertion
>Block
>Creation_date:	 2009-06-11
>WG ID:		 Independent Submission
>Number_of_pages: 12
>
>Abstract:
>This document defines an extension block that may be used with the
>Bundle Protocol [refs.DTNBP] within the context of a Delay-Tolerant
>Network architecture [refs.DTNarch].  This Previous Hop Insertion
>Block is designed to be inserted by a forwarding node to provide the
>endpoint identifier (EID) of an endpoint of which the forwarding node
>is a member so that this EID may be conveyed to the next-hop
>receiving node.  Knowledge of an EID of an endpoint of which a
>previous-hop node is a member may be required in some circumstances
>to support certain routing protocols (e.g., flood routing).  The
>Previous Hop Insertion block is always removed from the bundle by the
>receiving node so that its duration within the bundle lasts for
>exactly one hop.  This document defines the format and processing of
>this Previous Hop Insertion Block.
>
>
>
>The IETF Secretariat.
>

Content-class: urn:content-classes:message
Date: Mon, 8 Jun 2009 14:44:50 +0100
From: <[email-masked]>
To: <[email-masked]>
Subject: [dtn-interest] Reminder: E-DTN '09: Workshop on the Emergence of Delay-/Disruption-Tolerant Networking

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9E83F.4B9B7D9D
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

************************************************************************
CALL FOR PAPERS

Workshop on the Emergence of Delay-/Disruption-Tolerant Networks (E-DTN)

Technically Sponsored by IEEE

Dates: TBA
October, 2009, St.-Petersburg, Russia
(in conjunction with ICUMT 2009)
[Web: http://www.e-dtn.org/]
************************************************************************

Networking research for challenged environments has attracted
a lot of attention lately. Numerous attractive protocols have
been proposed, which are expected to network places and devices that
currently do not have the opportunity of =93going online=94. Such
environments reside at the edges of the current Internet infrastructure.
For example, public and private transport vehicles, underwater, =
satellite and
deep-space networks are potential DTN deployments of interest.
Communication in the above-mentioned challenged environments is usually
infrastructureless and consists mainly of mobile battery-powered
devices. Moreover, mobility patterns are usually unknown, making
connectivity periods between DTN-nodes intermittent and opportunistic.
To achieve communication in such environments one has to deal with
several performance tradeoffs, such as end-to-end delivery delay and
energy consumption, or reliability and storage congestion.
Since, in most cases, end-to-end connectivity does not exist (hence the
difference from ad hoc networking) current Internet protocols
fail permanently.

Although there have already been a lot of research proposals for
routing, (storage) congestion control, error control and
application design for such networks, the IRTF has
focused mainly on the Bundle Protocol (BP); BP is an application
layer protocol that does not include the appropriate functionalities to
deal with issues such as routing or storage congestion, for example. =
That
said, DTN research and its future directions seem to lack a stable
basis. For example, it is not clear yet if a =93one-fits-all=94 protocol
stack will be deployed, or if such an approach is feasible at all.
In contrast, several different protocols that each would suit the needs
of its specific architecture/setup would need to be able to =
interoperate.

This workshop seeks novel ideas in the form of preliminary or =
work-in-progress
results as well as mature research papers for Delay-/Disruption
Tolerant Networks. We also encourage position papers that address and=20
criticize the past, current and future trends of DTN research and are=20
intended to trigger discussions on the whole spectrum of DTNs.=20
Topics include but are not limited to:

- DTN Routing
- Congestion and Storage Congestion Control
- Resource Sharing in DTN environments
- Network Coding techniques for DTNs
- Application Development
- DTN Management Platforms
- Error and Flow Control
- Experiences and Measurements from DTN testbeds
- Privacy and Security of Information in DTNs
- DTN Simulators and related tools
- Performance Evaluation and Metrics for DTN Research
- Performance and Design Tradeoffs for DTN Algorithms and Protocols
- Social Networking through DTNs
- Satellite Constellations and DTNs
- Naming/Addressing and interoperability issues with the Internet =
architecture
- DTN Architectures:
-- Satellite Communications
-- Deep-space Communications
-- Underwater Communications
-- Connectivity in Developing Countries
-- Communication in Public and Private Transport Vehicles

IMPORTANT DATES:

Abstract-registration Deadline: June 15, 2009
Paper-submission Deadline: June 20, 2009
Acceptance Notification: July 31, 2009

SUBMISSION GUIDELINES:

Submitted papers must be original in content, not published or=20
submitted to another workshop, conference or journal.

Page-limits are as follows:
Position Papers: 2 pages,
Work-in-Progress Papers: 4 pages and
Full Papers: 6 pages.

Authors should prepare a PDF file following the IEEE single-spaced,=20
double-column page-style, using 10 pt size fonts on 8.5X11 inch pages.=20
Page-limits include text, figures, references and appendices.=20

A selection of the best papers will be invited for a special issue on =
the=20
Emergence of Delay-/Disruption-Tolerant Networks in the Journal of=20
Internet Engineering [http://www.jie-online.org].

WORKSHOP CHAIRS

General Co-Chairs:
	* Vassilis Tsaoussidis, Democritus University of Thrace, Greece/MIT, =
USA
	* Saverio Mascolo, Polytechnic of Bari, Italy

TPC Co-Chairs:
	* Lefteris Mamatas, University College London, UK
	* Ioannis Psaras, University of Surrey, UK

Workshop TPC:
	* Scott Burleigh, NASA/JPL, USA
	* Wei Koong Chai, UCL, UK=20
	* Stylianos Dimitriou, Democritus University of Thrace, Greece
	* Wesley Eddy, Verizon/NASA GRC, USA
        * Zygmunt Haas, Cornell University, USA=20
	* Peter Holliday, Cisco Systems, Australia
	* Pan Hui, Deutsche Telekom Laboratories, Germany
	* Merkourios Karaliopoulos, ETH Zurich, Switzerland=20
	* Lefteris Mamatas, UCL, UK
	* Saverio Mascolo, Politecnico di Bari, Italy
	* Ibrahim Matta, Boston University, USA=20
	* Paulo Mendes, INESC-Porto, Portugal=20
	* Panagiotis Papadimitriou, Lancaster University, UK=20
	* Giorgos Papastergiou, Hellenic Aerospace Industry, Greece
	* Ioannis Psaras, University of Surrey, UK
	* Christos V. Samaras, Democritus University of Thrace, Greece
	* Keith Scott, MITRE Corporation, USA=20
	* Dimitrios Serpanos, University of Patras, Greece
	* Thrasyvoulos Spyropoulos, ETH Zurich, Switzerland=20
	* Vassilis Tsaoussidis, Democritus University of Thrace, Greece/MIT, =
USA
	* Lloyd Wood, University of Surrey/Cisco Systems, UK=20
	* Eiko Yoneki, University of Cambridge, UK
	* Chi Zhang, Juniper Networks, USA

------_=_NextPart_001_01C9E83F.4B9B7D9D
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>Reminder: E-DTN '09: Workshop on the Emergence of =
Delay-/Disruption-Tolerant Networking</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<BR>

<P><FONT =
SIZE=3D2>****************************************************************=
********<BR>
CALL FOR PAPERS<BR>
<BR>
Workshop on the Emergence of Delay-/Disruption-Tolerant Networks =
(E-DTN)<BR>
<BR>
Technically Sponsored by IEEE<BR>
<BR>
Dates: TBA<BR>
October, 2009, St.-Petersburg, Russia<BR>
(in conjunction with ICUMT 2009)<BR>
[Web: <A HREF=3D"http://www.e-dtn.org/">http://www.e-dtn.org/</A>]<BR>
************************************************************************<=
BR>
<BR>
Networking research for challenged environments has attracted<BR>
a lot of attention lately. Numerous attractive protocols have<BR>
been proposed, which are expected to network places and devices that<BR>
currently do not have the opportunity of &#147;going online&#148;. =
Such<BR>
environments reside at the edges of the current Internet =
infrastructure.<BR>
For example, public and private transport vehicles, underwater, =
satellite and<BR>
deep-space networks are potential DTN deployments of interest.<BR>
Communication in the above-mentioned challenged environments is =
usually<BR>
infrastructureless and consists mainly of mobile battery-powered<BR>
devices. Moreover, mobility patterns are usually unknown, making<BR>
connectivity periods between DTN-nodes intermittent and =
opportunistic.<BR>
To achieve communication in such environments one has to deal with<BR>
several performance tradeoffs, such as end-to-end delivery delay and<BR>
energy consumption, or reliability and storage congestion.<BR>
Since, in most cases, end-to-end connectivity does not exist (hence =
the<BR>
difference from ad hoc networking) current Internet protocols<BR>
fail permanently.<BR>
<BR>
Although there have already been a lot of research proposals for<BR>
routing, (storage) congestion control, error control and<BR>
application design for such networks, the IRTF has<BR>
focused mainly on the Bundle Protocol (BP); BP is an application<BR>
layer protocol that does not include the appropriate functionalities =
to<BR>
deal with issues such as routing or storage congestion, for example. =
That<BR>
said, DTN research and its future directions seem to lack a stable<BR>
basis. For example, it is not clear yet if a &#147;one-fits-all&#148; =
protocol<BR>
stack will be deployed, or if such an approach is feasible at all.<BR>
In contrast, several different protocols that each would suit the =
needs<BR>
of its specific architecture/setup would need to be able to =
interoperate.<BR>
<BR>
This workshop seeks novel ideas in the form of preliminary or =
work-in-progress<BR>
results as well as mature research papers for Delay-/Disruption<BR>
Tolerant Networks. We also encourage position papers that address =
and<BR>
criticize the past, current and future trends of DTN research and =
are<BR>
intended to trigger discussions on the whole spectrum of DTNs.<BR>
Topics include but are not limited to:<BR>
<BR>
- DTN Routing<BR>
- Congestion and Storage Congestion Control<BR>
- Resource Sharing in DTN environments<BR>
- Network Coding techniques for DTNs<BR>
- Application Development<BR>
- DTN Management Platforms<BR>
- Error and Flow Control<BR>
- Experiences and Measurements from DTN testbeds<BR>
- Privacy and Security of Information in DTNs<BR>
- DTN Simulators and related tools<BR>
- Performance Evaluation and Metrics for DTN Research<BR>
- Performance and Design Tradeoffs for DTN Algorithms and Protocols<BR>
- Social Networking through DTNs<BR>
- Satellite Constellations and DTNs<BR>
- Naming/Addressing and interoperability issues with the Internet =
architecture<BR>
- DTN Architectures:<BR>
-- Satellite Communications<BR>
-- Deep-space Communications<BR>
-- Underwater Communications<BR>
-- Connectivity in Developing Countries<BR>
-- Communication in Public and Private Transport Vehicles<BR>
<BR>
IMPORTANT DATES:<BR>
<BR>
Abstract-registration Deadline: June 15, 2009<BR>
Paper-submission Deadline: June 20, 2009<BR>
Acceptance Notification: July 31, 2009<BR>
<BR>
SUBMISSION GUIDELINES:<BR>
<BR>
Submitted papers must be original in content, not published or<BR>
submitted to another workshop, conference or journal.<BR>
<BR>
Page-limits are as follows:<BR>
Position Papers: 2 pages,<BR>
Work-in-Progress Papers: 4 pages and<BR>
Full Papers: 6 pages.<BR>
<BR>
Authors should prepare a PDF file following the IEEE single-spaced,<BR>
double-column page-style, using 10 pt size fonts on 8.5X11 inch =
pages.<BR>
Page-limits include text, figures, references and appendices.<BR>
<BR>
A selection of the best papers will be invited for a special issue on =
the<BR>
Emergence of Delay-/Disruption-Tolerant Networks in the Journal of<BR>
Internet Engineering [<A =
HREF=3D"http://www.jie-online.org">http://www.jie-online.org</A>].<BR>
<BR>
WORKSHOP CHAIRS<BR>
<BR>
General Co-Chairs:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Vassilis Tsaoussidis, =
Democritus University of Thrace, Greece/MIT, USA<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Saverio Mascolo, =
Polytechnic of Bari, Italy<BR>
<BR>
TPC Co-Chairs:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Lefteris Mamatas, =
University College London, UK<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Ioannis Psaras, University =
of Surrey, UK<BR>
<BR>
Workshop TPC:<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Scott Burleigh, NASA/JPL, =
USA<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Wei Koong Chai, UCL, UK<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Stylianos Dimitriou, =
Democritus University of Thrace, Greece<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Wesley Eddy, Verizon/NASA =
GRC, USA<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Zygmunt Haas, Cornell =
University, USA<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Peter Holliday, Cisco =
Systems, Australia<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Pan Hui, Deutsche Telekom =
Laboratories, Germany<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Merkourios Karaliopoulos, =
ETH Zurich, Switzerland<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Lefteris Mamatas, UCL, =
UK<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Saverio Mascolo, =
Politecnico di Bari, Italy<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Ibrahim Matta, Boston =
University, USA<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Paulo Mendes, INESC-Porto, =
Portugal<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Panagiotis Papadimitriou, =
Lancaster University, UK<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Giorgos Papastergiou, =
Hellenic Aerospace Industry, Greece<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Ioannis Psaras, University =
of Surrey, UK<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Christos V. Samaras, =
Democritus University of Thrace, Greece<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Keith Scott, MITRE =
Corporation, USA<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Dimitrios Serpanos, =
University of Patras, Greece<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Thrasyvoulos Spyropoulos, =
ETH Zurich, Switzerland<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Vassilis Tsaoussidis, =
Democritus University of Thrace, Greece/MIT, USA<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Lloyd Wood, University of =
Surrey/Cisco Systems, UK<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Eiko Yoneki, University of =
Cambridge, UK<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; * Chi Zhang, Juniper =
Networks, USA<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C9E83F.4B9B7D9D--

Content-class: urn:content-classes:message
Date: Mon, 8 Jun 2009 10:12:32 +0100
From: <[email-masked]>
To: <[email-masked]>
Cc: [email-masked]
Subject: [dtn-interest] Bundle Protocol Agent

This is a multi-part message in MIME format.

------_=_NextPart_001_01C9E819.A4891BBB
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

Hi,=20
There is a document about details on Bundle Protocol Agent (BPA) which =
defines the requirements of BPA for bundle specifications and security =
purposes [Bundle Plugin Architecture] ..   The Bundle plugin =
architecture document however, does not provide reference for document =
containing detailed requirements of BPA .. Can any one please help me to =
find that document..=20

thanks..

regards,
Nasir=20

------_=_NextPart_001_01C9E819.A4891BBB
Content-Type: text/html;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV=3D"Content-Type" CONTENT=3D"text/html; =
charset=3Diso-8859-1">
<META NAME=3D"Generator" CONTENT=3D"MS Exchange Server version =
6.5.7653.38">
<TITLE>Bundle Protocol Agent</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Hi,<BR>
There is a document about details on Bundle Protocol Agent (BPA) which =
defines the requirements of BPA for bundle specifications and security =
purposes [Bundle Plugin Architecture] ..&nbsp;&nbsp; The Bundle plugin =
architecture document however, does not provide reference for document =
containing detailed requirements of BPA .. Can any one please help me to =
find that document..<BR>
<BR>
thanks..<BR>
<BR>
regards,<BR>
Nasir<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C9E819.A4891BBB--

Date: Fri, 5 Jun 2009 21:56:46 -0400
From: Victor lyamtsev <[email-masked]>
To: [email-masked]
Subject: [dtn-interest] DTN architecture questions

Hello,
Some questions regarding DTN building blocks in general, and DTN2
implementation in particular...

Some document mentions "bundle layer", where application data are
fragmented into the data fragments for "bundling". Does it belong to
DTN implementaion, or should that be handled in application outside of
DTN?
I saw few papers with some notion of  "intelligent layer" to make
selection of routing method depending on network conditions. Does DTN
implementation contain some "intelligent layer", or is it external to
DTN implementation?
Would that be a right terminology to talk about "network convergence
layers", when I am asking about routing methods available in DTN
implementation?
Which routing methods are available in DTN2 ?
Which convergence layers are supported under DTN implementation (
except transport) ? What would be the purpose of the link convergence
layer, for example?
i mean DTN2 when i mention DTN implementation...
Thank you,
-V

From: "Ivancic, William D. (GRC-RHN0)" <[email-masked]>
To: "[email-masked]" <[email-masked]>
Date: Fri, 5 Jun 2009 20:27:17 -0500
Accept-Language: en-US
acceptlanguage: en-US
Subject: [dtn-interest] FW: New Version Notification for draft-ivancic-dtnrg-network-management-reqs-00

I finally got around to completing at least draft 0 of the network management requirements document.  I did not proofread much of Sections 3 and 4 as I wanted to at least get the material out for comment as I will be unable to work much on this the next two weeks.

I am open for constructive criticism suggestions/corrections and additions.  I will be checking my emails and will try and update the document with your input.

/Will

 

>-----Original Message-----
>From: IETF I-D Submission Tool [mailto:[email-masked]]
>Sent: Friday, June 05, 2009 9:21 PM
>To: Ivancic, William D. (GRC-RHN0)
>Cc: Ivancic, William D. (GRC-RHN0)
>Subject: New Version Notification for draft-ivancic-dtnrg-network-
>management-reqs-00
>
>
>A new version of I-D, draft-ivancic-dtnrg-network-management-reqs-00.txt
>has been successfuly submitted by Will Ivancic and posted to the IETF
>repository.
>
>Filename:	 draft-ivancic-dtnrg-network-management-reqs
>Revision:	 00
>Title:		 Delay/Disruption Tolerant Networking - Network
>Management Requirements
>Creation_date:	 2009-06-05
>WG ID:		 Independent Submission
>Number_of_pages: 26
>
>Abstract:
>This document contains four main sections.  The first section provide
>some a short introduction of what Delay (or Disruption or
>Disconnected) Networking is.  The second section describes various
>DTN operational environments.  The third section provides
>requirements and desired properties for managing Delay and Disruption
>Tolerant Networks.  The fourth section describes characteristics that
>can be found in DTN systems and suggests items that should be
>considered for monitoring and/or configuration.
>
>
>
>The IETF Secretariat.
>

Sender: [email-masked]
From: Michael Demmer <[email-masked]>
Date: Fri, 5 Jun 2009 08:41:01 -0700
To: Delay Tolerant Networking Interest List <[email-masked]>
Subject: [dtn-interest] economist article on interplanetary DTN

--0016e645b7687ec754046b9bb970
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

http://www.economist.com/research/articlesBySubject/displayStory.cfm?story_id=13725833&amp;subjectID=348963&amp;fsrc=nwl

-m

--0016e645b7687ec754046b9bb970
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<a href=3D"http://www.economist.com/research/articlesBySubject/displayStory=
.cfm?story_id=3D13725833&amp;amp;subjectID=3D348963&amp;amp;fsrc=3Dnwl">htt=
p://www.economist.com/research/articlesBySubject/displayStory.cfm?story_id=
=3D13725833&amp;amp;subjectID=3D348963&amp;amp;fsrc=3Dnwl</a><br>

<br>-m<br><br>

--0016e645b7687ec754046b9bb970--

From: "Symington, Susan F." <[email-masked]>
To: DTN <[email-masked]>
Date: Thu, 4 Jun 2009 11:50:10 -0400
Accept-Language: en-US
acceptlanguage: en-US
Subject: [dtn-interest] DTN I-Ds in last call

--_000_F5830D8920D7BA4DB8BCFE1DC57164AC0233712C27IMCMBX2MITREO_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

Folks,

In response to comments that I received at our last DTNRG meeting in March,=
 I revised three drafts that are in last call:

draft-irtf-dtnrg-bundle-metadata-block-03<https://datatracker.ietf.org/draf=
ts/draft-irtf-dtnrg-bundle-metadata-block/> [draft<http://tools.ietf.org/ht=
ml/draft-irtf-dtnrg-bundle-metadata-block>]
draft-irtf-dtnrg-bundle-previous-hop-block-06<https://datatracker.ietf.org/=
drafts/draft-irtf-dtnrg-bundle-previous-hop-block/> [draft<http://tools.iet=
f.org/html/draft-irtf-dtnrg-bundle-previous-hop-block>]
draft-irtf-dtnrg-bundle-retrans-block-05<https://datatracker.ietf.org/draft=
s/draft-irtf-dtnrg-bundle-retrans-block/> [draft<http://tools.ietf.org/html=
/draft-irtf-dtnrg-bundle-retrans-block>]

The only comments I've received were from Scott and Wesley regarding termin=
ology that has to be cleaned up in the Previous Hop Block draft, which I am=
 happy to do. This is not controversial.

Does anyone else have any comments on these drafts? Now that they have been=
 revised per the directions I received at the March meeting, are they to yo=
ur liking?  Two months have passed since I posted the revised drafts. Is yo=
ur silence to be interpreted as consent?

If these docs are okay with you, then saying so would be helpful for the re=
st of us to know.

Thanks.

-susan

*****************************************************************
Susan Symington
The MITRE Corporation
[email-masked]
703-983-7209 (voice)
703-983-7142 (fax)
******************************************************************

--_000_F5830D8920D7BA4DB8BCFE1DC57164AC0233712C27IMCMBX2MITREO_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable

<html xmlns:v=3D"urn:schemas-microsoft-com:vml" xmlns:o=3D"urn:schemas-micr=
osoft-com:office:office" xmlns:w=3D"urn:schemas-microsoft-com:office:word" =
xmlns:m=3D"http://schemas.microsoft.com/office/2004/12/omml" xmlns=3D"http:=
//www.w3.org/TR/REC-html40">

<head>
<meta http-equiv=3DContent-Type content=3D"text/html; charset=3Dus-ascii">
<meta name=3DGenerator content=3D"Microsoft Word 12 (filtered medium)">
<style>
<!--
 /* Font Definitions */
 @font-face
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
	{font-family:Calibri;
	panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
	{font-family:Verdana;
	panose-1:2 11 6 4 3 5 4 4 2 4;}
 /* Style Definitions */
 p.MsoNormal, li.MsoNormal, div.MsoNormal
	{margin:0in;
	margin-bottom:.0001pt;
	font-size:11.0pt;
	font-family:"Calibri","sans-serif";}
a:link, span.MsoHyperlink
	{mso-style-priority:99;
	color:blue;
	text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
	{mso-style-priority:99;
	color:purple;
	text-decoration:underline;}
span.EmailStyle17
	{mso-style-type:personal-compose;
	font-family:"Calibri","sans-serif";
	color:windowtext;}
.MsoChpDefault
	{mso-style-type:export-only;}
@page Section1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
div.Section1
	{page:Section1;}
-->
</style>
<!--[if gte mso 9]><xml>
 <o:shapedefaults v:ext=3D"edit" spidmax=3D"1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
 <o:shapelayout v:ext=3D"edit">
  <o:idmap v:ext=3D"edit" data=3D"1" />
 </o:shapelayout></xml><![endif]-->
</head>

<body lang=3DEN-US link=3Dblue vlink=3Dpurple>

<div class=3DSection1>

<p class=3DMsoNormal>Folks, <o:p></o:p></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal>In response to comments that I received at our last DT=
NRG
meeting in March, I revised three drafts that are in last call:<o:p></o:p><=
/p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Verdana",=
"sans-serif"'><a
href=3D"https://datatracker.ietf.org/drafts/draft-irtf-dtnrg-bundle-metadat=
a-block/">draft-irtf-dtnrg-bundle-metadata-block-03</a>
[<a href=3D"http://tools.ietf.org/html/draft-irtf-dtnrg-bundle-metadata-blo=
ck">draft</a>]</span><o:p></o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Verdana",=
"sans-serif"'><a
href=3D"https://datatracker.ietf.org/drafts/draft-irtf-dtnrg-bundle-previou=
s-hop-block/">draft-irtf-dtnrg-bundle-previous-hop-block-06</a>
[<a href=3D"http://tools.ietf.org/html/draft-irtf-dtnrg-bundle-previous-hop=
-block">draft</a>]<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Verdana",=
"sans-serif"'><a
href=3D"https://datatracker.ietf.org/drafts/draft-irtf-dtnrg-bundle-retrans=
-block/">draft-irtf-dtnrg-bundle-retrans-block-05</a>
[<a href=3D"http://tools.ietf.org/html/draft-irtf-dtnrg-bundle-retrans-bloc=
k">draft</a>]<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Verdana",=
"sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Verdana",=
"sans-serif"'>The
only comments I&#8217;ve received were from Scott and Wesley regarding
terminology that has to be cleaned up in the Previous Hop Block draft, whic=
h I
am happy to do. This is not controversial.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Verdana",=
"sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Verdana",=
"sans-serif"'>Does
anyone else have any comments on these drafts? Now that they have been revi=
sed
per the directions I received at the March meeting, are they to your liking=
?&nbsp;
Two months have passed since I posted the revised drafts. Is your silence t=
o be
interpreted as consent?<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Verdana",=
"sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Verdana",=
"sans-serif"'>If
these docs are okay with you, then saying so would be helpful for the rest =
of
us to know.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Verdana",=
"sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Verdana",=
"sans-serif"'>Thanks.<o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Verdana",=
"sans-serif"'><o:p>&nbsp;</o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Verdana",=
"sans-serif"'>-susan<o:p></o:p></span></p>

<p class=3DMsoNormal><o:p>&nbsp;</o:p></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>***************************************************************=
**</span><span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p=
></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Courier N=
ew"'>Susan
Symington</span><span style=3D'font-size:12.0pt;font-family:"Times New Roma=
n","serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Courier N=
ew"'>The
MITRE Corporation</span><span style=3D'font-size:12.0pt;font-family:"Times =
New Roman","serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Courier N=
ew"'>[email-masked]</span><span
style=3D'font-size:12.0pt;font-family:"Times New Roman","serif"'><o:p></o:p=
></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Courier N=
ew"'>703-983-7209
(voice)</span><span style=3D'font-size:12.0pt;font-family:"Times New Roman"=
,"serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:12.0pt;font-family:"Courier N=
ew"'>703-983-7142
(fax)</span><span style=3D'font-size:12.0pt;font-family:"Times New Roman","=
serif"'><o:p></o:p></span></p>

<p class=3DMsoNormal><span style=3D'font-size:10.0pt;font-family:"Arial","s=
ans-serif"'>***************************************************************=
***</span><o:p></o:p></p>

</div>

</body>

</html>

--_000_F5830D8920D7BA4DB8BCFE1DC57164AC0233712C27IMCMBX2MITREO_--

From: "Ivancic, William D. (GRC-RHN0)" <[email-masked]>
To: "[email-masked]" <[email-masked]>
Date: Tue, 2 Jun 2009 12:48:01 -0500
Accept-Language: en-US
acceptlanguage: en-US
Subject: [dtn-interest] Network Management

I am working on completing the DTN Requirements Document.  I hope to have it out this week.  

Regarding TCP, Bluetooth and Removable storage convergence layers.  Are there any particular parameters on these convergence layers that people look at to aid in debugging and network management.  

Feel free to respond to the list or directly to me.  Thanks,

/Will

Date: Mon, 1 Jun 2009 23:12:01 -0400 (EDT)
From: "Balasubramaniyan, Vijay A" <[email-masked]>
To: [email-masked]
Subject: [dtn-interest] Final CFP NPSec 2009, Abstract Submission Deadline June 8th, 2009

[Apologies if you receive multiple copies of this CFP]

Submission deadline is 1 week away.

                              CALL FOR PAPERS (Final)
                                NPSec 2009
                 5th Workshop on Secure Network Protocols
                      In conjunction with ICNP 2009
                             October 13, 2009
                        Princeton, New Jersey, USA
                   http://www.gtisc.gatech.edu/npsec09/

Scope:
The 5th workshop on Secure Network Protocols (NPSec) is a one-day event
held in conjunction with with the 17th IEEE International Conference on
Network Protocols (ICNP 2009). NPSec focuses on two general areas.  
The first focus is on the development and analysis of secure or hardened
protocols for the operation (establishment and maintenance) of network
infrastructure, including such targets as secure multidomain, ad hoc, sensor
or overlay networks, or other related target areas.  This can include new
protocols, enhancements to existing protocols, protocol analysis, and new
attacks on existing protocols.  The second focus is on employing such secure
network protocols to create or enhance network applications. Examples include
collaborative firewalls, incentive strategies for multiparty networks, and
deployment strategies to enable secure applications.  

NPSec 2009 particularly welcomes new ideas on security in the context of
future Internet design, such as architectural considerations for future
Internet security and new primitives for supporting secure network protocol
and application design.  

Topics of interest include but are not limited to:
1. security in future Internet architectures
 - role of security in future architectures
 - integrating security into future protocols and applications
2. secure and/or resilient network protocols, e.g.:
- internetworking/routing
- MANETs
- LANs and WLANs
- mobile/cellular data networks
- p2p and other overlay networks
- federated trust systems
- sensor networks
3. vulnerabilities of existing protocols and applications (both theoretical and case studies), including attacks
4. key distribution/management
5. intrusion detection and response
6. incentive systems for p2p systems and MANETs routing
7. secure protocol configuration and deployment

Important Dates:
Abstract submission: June 8, 2009
Paper submission: June 15, 2009
Notification of acceptance: July 15, 2009
Camera ready version: August 5, 2009

NPSEC Steering Committee:
Sonia Fahmy, Purdue University (chair)
George Kesidis, Penn State University
Cristina Nita-Rotaru, Purdue University
Gene Tsudik, UC Irvine

Program Co-Chairs:
Jelena Mirkovic, USC/ISI
Xiaowei Yang, Duke University

Web and Proceedings Chair:
Vijay A. Balasubramaniyan, Georgia Tech.

Technical Program Committee:
Daniel Massey, Colorado State University
Jun Li, University of Oregon
Peter Reiher, UCLA
Beichuan Zhang, University of Arizona
Young Cho, USC/ISI
Mukesh Singhal, University of Kentucky
Minseok Kwon, Rochester Institute of Technology
Lan Wang, University of Memphis
Y. Charlie Hu, Purdue University
Minaxi Gupta, Indiana University
Dan Pei, AT\&T Research
Bogdan Carbunar, Motorola Research
Ted Faber, USC/ISI
Jia Wang, AT\&T Research
Landon Cox, Duke University
Jean-Pierre Hubaux, EPFL
Stephan Bohacek, University of Delaware
Reza Curtmola, New Jersey Institute of Technology
Brent Kang, University of North Carolina
Bryan Ford, Max Planck Institute for Software Systems

Date: Mon, 01 Jun 2009 09:47:03 -0400
From: Tad Kollar <[email-masked]>
To: "Ivancic, William D. (GRC-RHN0)" <[email-masked]>
Cc: "[email-masked]" <[email-masked]>, "[email-masked]" <[email-masked]>
Subject: Re: [dtn-interest] FW:  Maximum delay with netem

This is a multi-part message in MIME format.
--------------080606060404020904040904
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

I last looked at this issue back in kernel version 2.6.16. Things may 
have changed, but at that time, delay was stored as a 32-bit unsigned 
integer that represented nanoseconds (even though that kernel could not 
create a delay in increments any smaller than 1ms), which of course has 
a limit of 2^32 - 1. However, at some point there was a signed operation 
which resulted in a maximum reliable value of 2^31 - 1, or roughly 
2147s. If a value was entered that was too large, the resulting delay 
would be nearly random since part of the number was lost. If you 
attempted to use it anyway, it would occasionally cause the kernel to crash.

To address the issue I wrote a patch to the kernel which stored the 
delay value as a 64-bit unsigned int and forced all operations on it to 
be unsigned. IIRC, that allowed for a maximum delay of over 584 billion 
years. The largest value I tested with was around 60 minutes. The patch 
is still available at http://channel-emulator.grc.nasa.gov but I'd be 
surprised to see that it could be applied to a recent kernel without 
some work.

Tad

Ivancic, William D. (GRC-RHN0) wrote:
> Tad,
>
> Perhaps you can provide some insight to Paul regarding netem.
>
>
> Will
>
> Paul, checkout 
> http://channel-emulator.grc.nasa.gov/wiki/index.php?ChannelEmulator
>
>
>
>
> ******************************
> William D. Ivancic
> Phone 216-433-3494
> Fax 216-433-8705
> Networking Lab 216-433-2620
> DTN Lab 216-433-2981
> Mobile 440-503-4892
> http://roland.grc.nasa.gov/~ivancic 
>   
>> -----Original Message-----
>> From: [email-masked] [mailto:dtn-
>> [email-masked]] On Behalf Of Paul
>> Tomlinson
>> Sent: Monday, June 01, 2009 5:08 AM
>> To: [email-masked]
>> Subject: [dtn-interest] Maximum delay with netem
>>
>> Hi,
>> I've been experimenting with both DTN2 & ION using the netem module in
>> the Linux 2.6 kernel to create delays. As my experiments have got
>> bolder I've found the maximum delay with netem  is lower than I
>> thought. I'm wondering if anyone else has found this and either knows
>> a way to increase the value or or has an alternative FOSS tool?
>>
>> Details, I've found that the max value is around 2900 seconds (it
>> varies) even if a larger value is asked for, eg:
>>
>> sudo tc qdisc add dev eth2 root netem delay 7200s
>>
>> sudo tc qdisc show dev eth2
>> qdisc netem 8001: root limit 1000 delay 2905.0s
>>
>> This is on Linux Ubuntu 8.04.1 with a 2.6.24-21-generic kernel
>> (running as VMware Fusion virtual machines on an iMac). I found
>> similar results on Fedora 7.  I had thought, based on a non-
>> authoritative source, that the maximum delay was 23^2 -1 ms which is
>> about 71 minutes.
>>
>> Cheers,
>>
>> Paul Tomlinson
>> MSc student
>> _______________________________________________
>> dtn-interest mailing list
>> [email-masked]
>> http://maillists.intel-research.net/mailman/listinfo/dtn-interest
>>     
>
>   

-- 
*Thaddeus J. Kollar* 	*Fax:* 216-433-8000
DB Consulting Group, Inc. <http://www.dbconsultinggroup.com> 	*Phone:* 
216-433-5105
NASA Glenn Research Center <http://www.grc.nasa.gov> 	*Mailstop:* 142-3

--------------080606060404020904040904
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
  <meta content="text/html;charset=ISO-8859-1" http-equiv="Content-Type">
  <title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
<font face="Arial">I last looked at this issue back in kernel version
2.6.16. Things may have changed, but at that time, delay was stored as
a 32-bit unsigned integer that represented nanoseconds (even though
that kernel could not create a delay in increments any smaller than
1ms), which of course has a limit of 2^32 - 1. However, at some point
there was a signed operation which resulted in a maximum reliable value
of 2^31 - 1, or roughly 2147s. If a value was entered that was too
large, the resulting delay would be nearly random since part of the
number was lost. If you attempted to use it anyway, it would
occasionally cause the kernel to crash.<br>
<br>
To address the issue I wrote a patch to the kernel which stored the
delay value as a 64-bit unsigned int and forced all operations on it to
be unsigned. IIRC, that allowed for a maximum delay of over 584 billion
years. The largest value I tested with was around 60 minutes. The patch
is still available at <a class="moz-txt-link-freetext" href="http://channel-emulator.grc.nasa.gov">http://channel-emulator.grc.nasa.gov</a> but I'd be
surprised to see that it could be applied to a recent kernel without
some work.<br>
<br>
Tad<br>
</font><br>
Ivancic, William D. (GRC-RHN0) wrote:
<blockquote
 cite="mid:[email-masked]"
 type="cite">
  <pre wrap="">Tad,

Perhaps you can provide some insight to Paul regarding netem.

Will

Paul, checkout 
<a class="moz-txt-link-freetext" href="http://channel-emulator.grc.nasa.gov/wiki/index.php?ChannelEmulator">http://channel-emulator.grc.nasa.gov/wiki/index.php?ChannelEmulator</a>

******************************
William D. Ivancic
Phone 216-433-3494
Fax 216-433-8705
Networking Lab 216-433-2620
DTN Lab 216-433-2981
Mobile 440-503-4892
<a class="moz-txt-link-freetext" href="http://roland.grc.nasa.gov/~ivancic">http://roland.grc.nasa.gov/~ivancic</a> 
  </pre>
  <blockquote type="cite">
    <pre wrap="">-----Original Message-----
From: <a class="moz-txt-link-abbreviated" href="mailto:[email-masked]">[email-masked]</a> [<a class="moz-txt-link-freetext" href="mailto:dtn">mailto:dtn</a>-
<a class="moz-txt-link-abbreviated" href="mailto:[email-masked]">[email-masked]</a>] On Behalf Of Paul
Tomlinson
Sent: Monday, June 01, 2009 5:08 AM
To: <a class="moz-txt-link-abbreviated" href="mailto:[email-masked]">[email-masked]</a>
Subject: [dtn-interest] Maximum delay with netem

Hi,
I've been experimenting with both DTN2 &amp; ION using the netem module in
the Linux 2.6 kernel to create delays. As my experiments have got
bolder I've found the maximum delay with netem  is lower than I
thought. I'm wondering if anyone else has found this and either knows
a way to increase the value or or has an alternative FOSS tool?

Details, I've found that the max value is around 2900 seconds (it
varies) even if a larger value is asked for, eg:

sudo tc qdisc add dev eth2 root netem delay 7200s

sudo tc qdisc show dev eth2
qdisc netem 8001: root limit 1000 delay 2905.0s

This is on Linux Ubuntu 8.04.1 with a 2.6.24-21-generic kernel
(running as VMware Fusion virtual machines on an iMac). I found
similar results on Fedora 7.  I had thought, based on a non-
authoritative source, that the maximum delay was 23^2 -1 ms which is
about 71 minutes.

Cheers,

Paul Tomlinson
MSc student
_______________________________________________
dtn-interest mailing list
<a class="moz-txt-link-abbreviated" href="mailto:[email-masked]">[email-masked]</a>
<a class="moz-txt-link-freetext" href="http://maillists.intel-research.net/mailman/listinfo/dtn-interest">http://maillists.intel-research.net/mailman/listinfo/dtn-interest</a>
    </pre>
  </blockquote>
  <pre wrap=""><!---->
  </pre>
</blockquote>
<br>
<div class="moz-signature">-- <br>
<table
 style="border: 3px double black; font-family: Arial,Helvetica; font-size: 9pt;"
 cellpadding="2" cellspacing="0">
  <tbody>
    <tr style="background-color: rgb(224, 224, 224);">
      <td
 style="font-family: Lucida Handwriting,Arial,Helvetica; font-size: 10pt;"><b>Thaddeus
J. Kollar</b></td>
      <td style="padding-left: 15px;"><b>Fax:</b> 216-433-8000</td>
    </tr>
    <tr>
      <td style="font-family: Gill Sans,Arial,Helvetica;"><a
 href="http://www.dbconsultinggroup.com">DB Consulting Group, Inc.</a></td>
      <td style="padding-left: 15px;"><b>Phone:</b> 216-433-5105</td>
    </tr>
    <tr style="background-color: rgb(224, 224, 224);">
      <td><a href="http://www.grc.nasa.gov">NASA Glenn Research Center</a></td>
      <td style="padding-left: 15px;"><b>Mailstop:</b> 142-3</td>
    </tr>
  </tbody>
</table>
</div>
</body>
</html>

--------------080606060404020904040904--

From: "Ivancic, William D. (GRC-RHN0)" <[email-masked]>
To: "Kollar, Thaddeus J. (GRC-V000)[DB Consulting Group, Inc.]" <[email-masked]>
Date: Mon, 1 Jun 2009 07:52:47 -0500
Accept-Language: en-US
acceptlanguage: en-US
Cc: "[email-masked]" <[email-masked]>, "[email-masked]" <[email-masked]>
Subject: [dtn-interest] FW:  Maximum delay with netem

Tad,

Perhaps you can provide some insight to Paul regarding netem.

Will

Paul, checkout 
http://channel-emulator.grc.nasa.gov/wiki/index.php?ChannelEmulator

******************************
William D. Ivancic
Phone 216-433-3494
Fax 216-433-8705
Networking Lab 216-433-2620
DTN Lab 216-433-2981
Mobile 440-503-4892
http://roland.grc.nasa.gov/~ivancic 
>-----Original Message-----
>From: [email-masked] [mailto:dtn-
>[email-masked]] On Behalf Of Paul
>Tomlinson
>Sent: Monday, June 01, 2009 5:08 AM
>To: [email-masked]
>Subject: [dtn-interest] Maximum delay with netem
>
>Hi,
>I've been experimenting with both DTN2 & ION using the netem module in
>the Linux 2.6 kernel to create delays. As my experiments have got
>bolder I've found the maximum delay with netem  is lower than I
>thought. I'm wondering if anyone else has found this and either knows
>a way to increase the value or or has an alternative FOSS tool?
>
>Details, I've found that the max value is around 2900 seconds (it
>varies) even if a larger value is asked for, eg:
>
>sudo tc qdisc add dev eth2 root netem delay 7200s
>
>sudo tc qdisc show dev eth2
>qdisc netem 8001: root limit 1000 delay 2905.0s
>
>This is on Linux Ubuntu 8.04.1 with a 2.6.24-21-generic kernel
>(running as VMware Fusion virtual machines on an iMac). I found
>similar results on Fedora 7.  I had thought, based on a non-
>authoritative source, that the maximum delay was 23^2 -1 ms which is
>about 71 minutes.
>
>Cheers,
>
>Paul Tomlinson
>MSc student
>_______________________________________________
>dtn-interest mailing list
>[email-masked]
>http://maillists.intel-research.net/mailman/listinfo/dtn-interest

Date: Mon, 01 Jun 2009 13:48:45 +0100
From: Elwyn Davies <[email-masked]>
To: DTN <[email-masked]>
Subject: [dtn-interest] DTN3: Finger trouble

Hi.

You may have received a mail with the subject line "DTN3" last night. 

Please ignore it.  It was sent in error and the file it contains is not 
useful - it is corrupted in some way.

Apologies for any inconvenience caused.

A real version of this code should be coming shortly - the author has 
unfortuately been taken ill.

Regards,
Elwyn

From: Paul Tomlinson <[email-masked]>
To: [email-masked]
Date: Mon, 1 Jun 2009 10:07:32 +0100
Subject: [dtn-interest] Maximum delay with netem

Hi,
I've been experimenting with both DTN2 & ION using the netem module in  
the Linux 2.6 kernel to create delays. As my experiments have got  
bolder I've found the maximum delay with netem  is lower than I  
thought. I'm wondering if anyone else has found this and either knows  
a way to increase the value or or has an alternative FOSS tool?

Details, I've found that the max value is around 2900 seconds (it  
varies) even if a larger value is asked for, eg:

sudo tc qdisc add dev eth2 root netem delay 7200s

sudo tc qdisc show dev eth2
qdisc netem 8001: root limit 1000 delay 2905.0s

This is on Linux Ubuntu 8.04.1 with a 2.6.24-21-generic kernel  
(running as VMware Fusion virtual machines on an iMac). I found  
similar results on Fedora 7.  I had thought, based on a non- 
authoritative source, that the maximum delay was 23^2 -1 ms which is  
about 71 minutes.

Cheers,

Paul Tomlinson
MSc student