
Received: from M4.sparta.com (M4.sparta.com [157.185.61.2]) by maillists.intel-research.net (8.13.8/8.13.7) with ESMTP id m33CRs46005941 for <dtn-security@mailman.dtnrg.org>; Thu, 3 Apr 2008 05:27:55 -0700
Received: from Beta5.sparta.com (beta5.sparta.com [157.185.63.21]) by M4.sparta.com (8.13.5/8.13.5) with ESMTP id m33CYgXZ003526; Thu, 3 Apr 2008 07:34:42 -0500
Received: from nemo.columbia.ads.sparta.com (nemo.columbia.sparta.com [157.185.80.75]) by Beta5.sparta.com (8.12.11/8.13.1) with ESMTP id m33CYgrN026691; Thu, 3 Apr 2008 07:34:42 -0500
Received: from [192.168.4.98] ([157.185.80.253]) by nemo.columbia.ads.sparta.com with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 3 Apr 2008 08:34:41 -0400
From: "Peter Lovell" <peter.lovell@sparta.com>
To: <M.Bhutta@surrey.ac.uk>, "dtn security" <dtn-security@mailman.dtnrg.org>
Date: Thu, 3 Apr 2008 08:34:40 -0400
Message-Id: <20080403123440.45673365@127.0.0.1>
In-Reply-To: <676D5FD21A8EEC4591C13839BF2A14B9F166F1@EVS-EC1-NODE4.surrey.ac.uk>
References: <676D5FD21A8EEC4591C13839BF2A14B9F166F1@EVS-EC1-NODE4.surrey.ac.uk>
X-Mailer: CTM PowerMail version 5.6.3 build 4504 English (intel) <http://www.ctmdev.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
X-OriginalArrivalTime: 03 Apr 2008 12:34:41.0724 (UTC) FILETIME=[16E43FC0:01C89587]
X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-3.0 (M4.sparta.com [157.185.61.2]); Thu, 03 Apr 2008 07:34:42 -0500 (CDT)
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by maillists.intel-research.net id m33CRs46005941
Subject: Re: [dtn-security] security layer
X-BeenThere: dtn-security@mailman.dtnrg.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DTN Security Discussion <dtn-security.mailman.dtnrg.org>
List-Unsubscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-security>, <mailto:dtn-security-request@mailman.dtnrg.org?subject=unsubscribe>
List-Archive: <http://maillists.intel-research.net/pipermail/dtn-security>
List-Post: <mailto:dtn-security@mailman.dtnrg.org>
List-Help: <mailto:dtn-security-request@mailman.dtnrg.org?subject=help>
List-Subscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-security>, <mailto:dtn-security-request@mailman.dtnrg.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2008 12:27:56 -0000

On Thu, Apr 3, 2008, M.Bhutta@surrey.ac.uk <M.Bhutta@surrey.ac.uk> wrote:

>Hello, 
>When we design a secure system, the security should be provided at each
>layer to make a good secure system. 
>If we develop a system on top of DTN based network, then which layer
>will be best suitable to provide security extensions.  
>
>Suppose, we have underlying sensor network and on top DTN as overlay
>network, which layer we should provide the security services 
>for such system.  I think, to get benefits like, generic solution, we
>should introduce security extensions to bundle layer ... 
>
>                             Bundle Layer 
>                              Security 
>                             Transport Layer 
>                             Network Layer
>                             Data Link Layer 
>                             Physical Layer  
>
>Please comment on this and appropriate suggestions for building a
>security architecture for overlay network on top of sensor networks. 
>
>Nasir

Hi Nasir,

if you're looking to add security extensions to the bundle layer itself,
these documents are a good place to start.

http://www.ietf.org/internet-drafts/draft-irtf-dtnrg-sec-overview-04.txt
http://www.ietf.org/internet-drafts/draft-irtf-dtnrg-bundle-security-05.txt

Regards.....Peter




Received: from mail83.messagelabs.com (mail83.messagelabs.com [195.245.231.83]) by maillists.intel-research.net (8.13.8/8.13.7) with SMTP id m33Bh4Cj002256 for <dtn-security@mailman.dtnrg.org>; Thu, 3 Apr 2008 04:43:05 -0700
X-VirusChecked: Checked
X-Env-Sender: M.Bhutta@surrey.ac.uk
X-Msg-Ref: server-3.tower-83.messagelabs.com!1207223357!46450915!39
X-StarScan-Version: 5.5.12.14.2; banners=-,-,-
X-Originating-IP: [131.227.102.140]
Received: (qmail 6047 invoked from network); 3 Apr 2008 11:49:45 -0000
Received: from ads40.surrey.ac.uk (HELO ads40.surrey.ac.uk) (131.227.102.140) by server-3.tower-83.messagelabs.com with SMTP; 3 Apr 2008 11:49:45 -0000
Received: from EVS-EC1-NODE4.surrey.ac.uk ([131.227.102.139]) by ads40.surrey.ac.uk with Microsoft SMTPSVC(6.0.3790.3959);  Thu, 3 Apr 2008 12:49:39 +0100
X-MimeOLE: Produced By Microsoft Exchange V6.5
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C89580.CBEB4252"
Date: Thu, 3 Apr 2008 12:49:38 +0100
Message-ID: <676D5FD21A8EEC4591C13839BF2A14B9F166F1@EVS-EC1-NODE4.surrey.ac.uk>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: security layer 
Thread-Index: AciVgMuhUBb6lLUyRmWNlNlgXapscQ==
From: <M.Bhutta@surrey.ac.uk>
To: <dtn-security@mailman.dtnrg.org>
X-OriginalArrivalTime: 03 Apr 2008 11:49:39.0245 (UTC) FILETIME=[CC16ADD0:01C89580]
Subject: [dtn-security] security layer
X-BeenThere: dtn-security@mailman.dtnrg.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DTN Security Discussion <dtn-security.mailman.dtnrg.org>
List-Unsubscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-security>, <mailto:dtn-security-request@mailman.dtnrg.org?subject=unsubscribe>
List-Archive: <http://maillists.intel-research.net/pipermail/dtn-security>
List-Post: <mailto:dtn-security@mailman.dtnrg.org>
List-Help: <mailto:dtn-security-request@mailman.dtnrg.org?subject=help>
List-Subscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-security>, <mailto:dtn-security-request@mailman.dtnrg.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2008 11:43:07 -0000

This is a multi-part message in MIME format.

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

Hello,=20
When we design a secure system, the security should be provided at each =
layer to make a good secure system.=20
If we develop a system on top of DTN based network, then which layer =
will be best suitable to provide security extensions. =20

Suppose, we have underlying sensor network and on top DTN as overlay =
network, which layer we should provide the security services=20
for such system.  I think, to get benefits like, generic solution, we =
should introduce security extensions to bundle layer ...=20

                             Bundle Layer=20
                              Security=20
                             Transport Layer=20
                             Network Layer
                             Data Link Layer=20
                             Physical Layer =20

Please comment on this and appropriate suggestions for building a =
security architecture for overlay network on top of sensor networks.=20

Nasir


------_=_NextPart_001_01C89580.CBEB4252
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.7652.24">
<TITLE>security layer </TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->

<P><FONT SIZE=3D2>Hello,<BR>
When we design a secure system, the security should be provided at each =
layer to make a good secure system.<BR>
If we develop a system on top of DTN based network, then which layer =
will be best suitable to provide security extensions.&nbsp;<BR>
<BR>
Suppose, we have underlying sensor network and on top DTN as overlay =
network, which layer we should provide the security services<BR>
for such system.&nbsp; I think, to get benefits like, generic solution, =
we should introduce security extensions to bundle layer ...<BR>
<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; Bundle Layer<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp;&nbsp; Security<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; Transport Layer<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; Network Layer<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; Data Link Layer<BR>
&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&=
nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&n=
bsp;&nbsp;&nbsp;&nbsp; Physical Layer&nbsp;<BR>
<BR>
Please comment on this and appropriate suggestions for building a =
security architecture for overlay network on top of sensor networks.<BR>
<BR>
Nasir<BR>
<BR>
</FONT>
</P>

</BODY>
</HTML>
------_=_NextPart_001_01C89580.CBEB4252--


Received: from gateway0.EECS.Berkeley.EDU (gateway0.EECS.Berkeley.EDU [169.229.60.93]) by maillists.intel-research.net (8.13.8/8.13.7) with ESMTP id m332CSQ6000742; Wed, 2 Apr 2008 19:12:28 -0700
Received: from zabar.research.intel-research.net (bldmz-nat-161-164.berkeley.intel-research.net [12.155.161.164]) (authenticated bits=0) by gateway0.EECS.Berkeley.EDU (8.14.2/8.13.5) with ESMTP id m332JCAX013277 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 2 Apr 2008 19:19:13 -0700 (PDT)
From: Michael Demmer <demmer@cs.berkeley.edu>
To: Delay Tolerant Networking Interest List <dtn-interest@mailman.dtnrg.org>,  dtn-security <dtn-security@mailman.dtnrg.org>, dtn-users mailing list <dtn-users@mailman.dtnrg.org>
In-Reply-To: <F6C959D0-BD79-4AFC-AC8A-A109B2D842BE@cs.berkeley.edu>
References: <20080331223048.GA27216@firebird1.grc.nasa.gov> <47F1C779.3050302@jpl.nasa.gov> <A3A356E39B867E4380966B0EB600C28FE36380@NDJSEVS23A.ndc.nasa.gov> <47F2524D.9080507@jpl.nasa.gov> <47F25726.9090606@masaka.cs.ohiou.edu> <47F26124.2010800@jpl.nasa.gov> <47F270A2.6010104@masaka.cs.ohiou.edu> <47F29820.4020502@jpl.nasa.gov> <47F2A307.4030907@masaka.cs.ohiou.edu> <47F2AD86.5050705@jpl.nasa.gov> <003d01c89443$c6831c20$53895460$@com> <47F2BB7C.1080309@jpl.nasa.gov> <006901c8944e$0c385f00$24a91d00$@com> <47F3A0DB.3080202@bbn.com> <200804021609.m32G9Xu06193@cisco.com> <47F3B761.1010808@cs.tcd.ie> <699BE83D-98F2-43DE-B467-374B7206CD19@cs.berkeley.edu> <64AFAE11-A6F8-4CF6-951D-0D2E2F3E6B35@cs.berkeley.edu> <F6C959D0-BD79-4AFC-AC8A-A109B2D842BE@cs.berkeley.edu>
Message-Id: <231C40CD-2EF6-4C8B-954A-A28B12F9F4EC@cs.berkeley.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
X-Applemailsentby: demmer
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 2 Apr 2008 19:19:06 -0700
X-Mailer: Apple Mail (2.919.2)
Subject: Re: [dtn-security] [dtn-interest] list reply-to (was: Re: DTN Time Sync Issues)
X-BeenThere: dtn-security@mailman.dtnrg.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DTN Security Discussion <dtn-security.mailman.dtnrg.org>
List-Unsubscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-security>, <mailto:dtn-security-request@mailman.dtnrg.org?subject=unsubscribe>
List-Archive: <http://maillists.intel-research.net/pipermail/dtn-security>
List-Post: <mailto:dtn-security@mailman.dtnrg.org>
List-Help: <mailto:dtn-security-request@mailman.dtnrg.org?subject=help>
List-Subscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-security>, <mailto:dtn-security-request@mailman.dtnrg.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2008 02:12:32 -0000

Sorry, I should clarify this a bit:

I changed the mailing list configuration so that it does no Reply-To  
munging at all. Any Reply-To headers that are set by the poster are  
left intact, but no Reply-To headers are added by the mailing list  
itself.

-mike


On Apr 2, 2008, at 6:47 PM, Michael Demmer wrote:
>
> Given that no-one seems to prefer the current behavior, I've modified
> the mailing list configuration so that the Reply-To defaults to send
> only to the poster rather than to the whole list.
>
> I've done the same on the dtn-users and dtn-security lists as well.
>
> -mike
>
>
> On Apr 2, 2008, at 6:04 PM, Kevin Fall wrote:
>> I don't really recall having a preference one way or another....
>>
>> - K
>>
>> On Apr 2, 2008, at Apr 212:02 PMPDT, Michael Demmer wrote:
>>
>>>>> Can this behaviour be changed? It's been annoying me for _months_.
>>>>
>>>> I've no problem with that. Anyone else care?
>>>>
>>>> S. (Who doesn't manage the list as it happens.)
>>>
>>> I'd be happy to make the change, as I have access to the list
>>> administrative interface.
>>>
>>> I think I remember that when we set up the list, Kevin had a
>>> preference for the current default behavior, so I'd like to hear his
>>> opinion before making the change. I think he's on vacation this week
>>> so we'll see when he replies.
>>>
>>> -m
>>>
>>>
>>> _______________________________________________
>>> dtn-interest mailing list
>>> dtn-interest@mailman.dtnrg.org
>>> http://maillists.intel-research.net/mailman/listinfo/dtn-interest
>>>
>>
>> _______________________________________________
>> dtn-interest mailing list
>> dtn-interest@mailman.dtnrg.org
>> http://maillists.intel-research.net/mailman/listinfo/dtn-interest
>
> _______________________________________________
> dtn-interest mailing list
> dtn-interest@mailman.dtnrg.org
> http://maillists.intel-research.net/mailman/listinfo/dtn-interest



Received: from gateway0.EECS.Berkeley.EDU (gateway0.EECS.Berkeley.EDU [169.229.60.93]) by maillists.intel-research.net (8.13.8/8.13.7) with ESMTP id m331eQvV031212; Wed, 2 Apr 2008 18:40:26 -0700
Received: from zabar.research.intel-research.net (bldmz-nat-161-164.berkeley.intel-research.net [12.155.161.164]) (authenticated bits=0) by gateway0.EECS.Berkeley.EDU (8.14.2/8.13.5) with ESMTP id m331l9xG013051 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NOT); Wed, 2 Apr 2008 18:47:11 -0700 (PDT)
From: Michael Demmer <demmer@cs.berkeley.edu>
To: Delay Tolerant Networking Interest List <dtn-interest@mailman.dtnrg.org>
In-Reply-To: <64AFAE11-A6F8-4CF6-951D-0D2E2F3E6B35@cs.berkeley.edu>
References: <20080331223048.GA27216@firebird1.grc.nasa.gov> <47F1C779.3050302@jpl.nasa.gov> <A3A356E39B867E4380966B0EB600C28FE36380@NDJSEVS23A.ndc.nasa.gov> <47F2524D.9080507@jpl.nasa.gov> <47F25726.9090606@masaka.cs.ohiou.edu> <47F26124.2010800@jpl.nasa.gov> <47F270A2.6010104@masaka.cs.ohiou.edu> <47F29820.4020502@jpl.nasa.gov> <47F2A307.4030907@masaka.cs.ohiou.edu> <47F2AD86.5050705@jpl.nasa.gov> <003d01c89443$c6831c20$53895460$@com> <47F2BB7C.1080309@jpl.nasa.gov> <006901c8944e$0c385f00$24a91d00$@com> <47F3A0DB.3080202@bbn.com> <200804021609.m32G9Xu06193@cisco.com> <47F3B761.1010808@cs.tcd.ie> <699BE83D-98F2-43DE-B467-374B7206CD19@cs.berkeley.edu> <64AFAE11-A6F8-4CF6-951D-0D2E2F3E6B35@cs.berkeley.edu>
Message-Id: <F6C959D0-BD79-4AFC-AC8A-A109B2D842BE@cs.berkeley.edu>
Content-Type: text/plain; charset=US-ASCII; format=flowed; delsp=yes
Content-Transfer-Encoding: 7bit
X-Applemailsentby: demmer
Mime-Version: 1.0 (Apple Message framework v919.2)
Date: Wed, 2 Apr 2008 18:47:04 -0700
X-Mailer: Apple Mail (2.919.2)
Cc: dtn-security <dtn-security@mailman.dtnrg.org>, dtn-users mailing list <dtn-users@mailman.dtnrg.org>
Subject: Re: [dtn-security] [dtn-interest] list reply-to (was: Re: DTN Time Sync Issues)
X-BeenThere: dtn-security@mailman.dtnrg.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: DTN Security Discussion <dtn-security.mailman.dtnrg.org>
List-Unsubscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-security>, <mailto:dtn-security-request@mailman.dtnrg.org?subject=unsubscribe>
List-Archive: <http://maillists.intel-research.net/pipermail/dtn-security>
List-Post: <mailto:dtn-security@mailman.dtnrg.org>
List-Help: <mailto:dtn-security-request@mailman.dtnrg.org?subject=help>
List-Subscribe: <http://maillists.intel-research.net/mailman/listinfo/dtn-security>, <mailto:dtn-security-request@mailman.dtnrg.org?subject=subscribe>
X-List-Received-Date: Thu, 03 Apr 2008 01:40:27 -0000

Given that no-one seems to prefer the current behavior, I've modified  
the mailing list configuration so that the Reply-To defaults to send  
only to the poster rather than to the whole list.

I've done the same on the dtn-users and dtn-security lists as well.

-mike


On Apr 2, 2008, at 6:04 PM, Kevin Fall wrote:
> I don't really recall having a preference one way or another....
>
> - K
>
> On Apr 2, 2008, at Apr 212:02 PMPDT, Michael Demmer wrote:
>
>>>> Can this behaviour be changed? It's been annoying me for _months_.
>>>
>>> I've no problem with that. Anyone else care?
>>>
>>> S. (Who doesn't manage the list as it happens.)
>>
>> I'd be happy to make the change, as I have access to the list
>> administrative interface.
>>
>> I think I remember that when we set up the list, Kevin had a
>> preference for the current default behavior, so I'd like to hear his
>> opinion before making the change. I think he's on vacation this week
>> so we'll see when he replies.
>>
>> -m
>>
>>
>> _______________________________________________
>> dtn-interest mailing list
>> dtn-interest@mailman.dtnrg.org
>> http://maillists.intel-research.net/mailman/listinfo/dtn-interest
>>
>
> _______________________________________________
> dtn-interest mailing list
> dtn-interest@mailman.dtnrg.org
> http://maillists.intel-research.net/mailman/listinfo/dtn-interest


