Re: (dictionary or not) Re: [dtn-security] 00 version of the Bundle Security Protocol Spec.

Michael Demmer <> Wed, 25 May 2005 15:37 UTC

Received: from pisco (pisco.CS.Berkeley.EDU []) by (8.11.6/8.11.6) with ESMTP id j4PFbdV30624 for <>; Wed, 25 May 2005 08:37:39 -0700
Received: from demmer by pisco with local (Exim 4.50) id 1Daxwx-0003ts-Hr; Wed, 25 May 2005 08:37:39 -0700
Date: Wed, 25 May 2005 08:37:39 -0700
From: Michael Demmer <>
Cc: "Susan F. Symington" <>, "'Howard Weiss'" <>
Subject: Re: (dictionary or not) Re: [dtn-security] 00 version of the Bundle Security Protocol Spec.
Message-ID: <>
References: <> <> <> <>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <>
User-Agent: Mutt/1.4.2i
X-Mailman-Version: 2.0.13
Precedence: bulk
List-Unsubscribe: <>, <>
List-Id: DTN Security Discussion <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
List-Archive: <>

> I guess that that's possible, but I'd be for getting started
> without the dictionary and changing to use it later if it
> makes sense than.

That'd be ok with me I guess -- though for the reference
implementation at least, it should be pretty easy to use it since I'll
have helper functions and the like for stuffing URIs in and out of the

> But since you've suggested it: what's the easy way to encode
> the optional src and/or optional dest optionally using the
> dictionary? (I'm just not up to speed on how the dictionary
> encoding currently works.)

The dictionary part is a blob of consecutive null-terminated
strings of total length <= 64K. Encoding a scheme:ssp is therefore a
pair of offsets, one for the scheme and one for the ssp, that indicate
the first byte of the string in the dictionary.