Re: [dtn-security] Re(2): Traffic Analysis Protection

Rajesh Krishnan <> Thu, 13 March 2008 21:04 UTC

Received: from ( []) by (8.13.8/8.13.7) with ESMTP id m2DL3x7h005634 for <>; Thu, 13 Mar 2008 14:04:00 -0700
Received: from ([]) by with esmtp (Exim 4.60) (envelope-from <>) id 1JZufC-0000Cc-3L for; Thu, 13 Mar 2008 17:08:34 -0400
From: Rajesh Krishnan <>
To: DTN Security Discussion <>
In-Reply-To: <20080313201414.439710226@>
References: <> <> <20080313201414.439710226@>
Content-Type: text/plain
Organization: BBN Technologies
Date: Thu, 13 Mar 2008 17:08:33 -0400
Message-Id: <1205442513.7198.78.camel@z>
Mime-Version: 1.0
X-Mailer: Evolution 2.10.1
Content-Transfer-Encoding: 7bit
Subject: Re: [dtn-security] Re(2): Traffic Analysis Protection
X-Mailman-Version: 2.1.9
Precedence: list
Reply-To:, DTN Security Discussion <>
List-Id: DTN Security Discussion <>
List-Unsubscribe: <>, <>
List-Archive: <>
List-Post: <>
List-Help: <>
List-Subscribe: <>, <>
X-List-Received-Date: Thu, 13 Mar 2008 21:04:01 -0000

Hi Peter,

> As you say, bundle-in-bundle encapsulation is a solution but ... you
> have to have *some* addressing *somewhere*.  

Agreed that this is typically true. Here is a fun thought though.

As a corner case, in small lightly-loaded networks, we could encrypt
messages with no "addresses" and share them epidemically or via other
addressless routing means.  If a node is able to decrypt it, then it is
for a specific endpoint on that node.  Otherwise it just passes it
along.  Extreme case of late binding.

The BP requires the source endpoint ID to be present to create a unique
ID.  By using a common source endpoint ID and by allocating the bundle
sequence space among nodes (doable in lightly loaded, small networks) we
could go "address-less".

Best Regards,