Re: [dtn-security] 00 version of the Bundle Security Protocol Spec.

Howard Weiss <howard.weiss@sparta.com> Thu, 02 June 2005 11:42 UTC

Received: from M4.sparta.com (IDENT:CxQKeaJqsmoGAN4Z51n3F8bQt7spO4id@M4.sparta.com [157.185.61.2]) by webbie.berkeley.intel-research.net (8.11.6/8.11.6) with ESMTP id j52BgQV31565 for <dtn-security@mailman.dtnrg.org>; Thu, 2 Jun 2005 04:42:26 -0700
Received: from Beta5.sparta.com (beta5.sparta.com [157.185.63.21]) by M4.sparta.com (8.13.1/8.13.1) with ESMTP id j52BgDTA003978; Thu, 2 Jun 2005 06:42:13 -0500
Received: from columbia.sparta.com ([157.185.80.32]) by Beta5.sparta.com (8.12.11/8.12.11) with ESMTP id j52BgDfh009708; Thu, 2 Jun 2005 06:42:13 -0500
Received: from [127.0.0.1] (testjk3.columbia.ads.sparta.com [157.185.81.160]) by columbia.sparta.com (8.12.10+Sun/8.12.10) with ESMTP id j52Bg76i009779; Thu, 2 Jun 2005 07:42:13 -0400 (EDT)
Message-ID: <429EF08F.2010108@sparta.com>
Date: Thu, 02 Jun 2005 07:42:07 -0400
From: Howard Weiss <howard.weiss@sparta.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
To: Scott Burleigh <Scott.Burleigh@jpl.nasa.gov>
CC: dtn-security@mailman.dtnrg.org, 'Stephen Farrell' <stephen.farrell@cs.tcd.ie>, "'Susan F. Symington'" <susan@mitre.org>
Subject: Re: [dtn-security] 00 version of the Bundle Security Protocol Spec.
References: <200506011452.j51Eq1W19612@smtp-bedford.mitre.org> <429E4F93.4010502@jpl.nasa.gov>
In-Reply-To: <429E4F93.4010502@jpl.nasa.gov>
Content-Type: multipart/alternative; boundary="------------010103060304030206000502"
Sender: dtn-security-admin@mailman.dtnrg.org
Errors-To: dtn-security-admin@mailman.dtnrg.org
X-BeenThere: dtn-security@mailman.dtnrg.org
X-Mailman-Version: 2.0.13
Precedence: bulk
Reply-To: dtn-security@mailman.dtnrg.org
List-Unsubscribe: <http://mailman.dtnrg.org/mailman/listinfo/dtn-security>, <mailto:dtn-security-request@mailman.dtnrg.org?subject=unsubscribe>
List-Id: DTN Security Discussion <dtn-security.mailman.dtnrg.org>
List-Post: <mailto:dtn-security@mailman.dtnrg.org>
List-Help: <mailto:dtn-security-request@mailman.dtnrg.org?subject=help>
List-Subscribe: <http://mailman.dtnrg.org/mailman/listinfo/dtn-security>, <mailto:dtn-security-request@mailman.dtnrg.org?subject=subscribe>
List-Archive: <http://mailman.dtnrg.org/pipermail/dtn-security/>

Scott,

Scott Burleigh wrote:

>>>
>> agree that the extension headers should be documented and explained 
>> in the
>> security spec, but how are we going to make sure that whatever type 
>> value is
>> assigned to these headers doesn't conflict with a type chosen for use 
>> in the
>> bundle protocol or for use in another extension header? I was 
>> envisioning us
>> placing the header types that we know of in a table in the Bundle 
>> Protocol
>> so when folks make up new headers, they would be aware of which types 
>> are
>> already reserved for use. If we don't have a master list of header types
>> somewhere, then we at least need a master list of documents that 
>> contain all
>> header types.
>>
> Yes, this is going to be a problem that we'll have to solve somehow.  
> But I don't think having a master list in the Bundle Protocol spec is 
> the answer: at some point that document is going to need to be an RFC, 
> and we don't want to have to be submitting new versions of that RFC 
> every time we come up with a new extension header.  Some sort of 
> central naming and numbering authority is needed; if not IANA, then 
> we'll need to find another or invent our own.

At least for now, it sounds like this should be a separate DTN "assigned 
header numbers" ID/RFC so that it can easily be re-issued when needed 
rather than muddying the waters of the Bundle Protocol spec.  It 
probably should end up being an IANA function at some point - maybe when 
DTNRG moves out of the IRTF and becomes DTNWG in the IETF?

Howie

-- 
Howard Weiss
SPARTA, Inc.
7075 Samuel Morse Drive
Columbia, MD 21046
410.872.1515 x201
410.872.8079 (fax)