|
|||||||||||
|
Re: [Hipsec-rg] Some comments on draft-ahrenholz-hiprg-dht-01
From: Ahrenholz, Jeffrey M <jeffrey.m.ahrenholz(at)boeing.com>
Date: Wed Aug 08 2007 - 11:17:44 EDT
> Protection for this could be done with modifications to the Yes, the second option of modifying the DHT server to verify signatures is also covered in Section 3.2 of the draft. > Both of these approaches need modifications to bamboo code. Requiring So in summary of our last few emails, we have the following options:
Options 1-3 are already covered in draft-ahrenholz-hiprg-dht-01. As Tom wrote in his reply, we should sketch out some requirements. Maybe this draft should cover options 1-3 (or 1-2?) (with mention of the other options), with the goal of using OpenDHT for interoperability and easy deployment. I need to look at the drafts Philip referenced. This draft could refer to a separate, more advanced HIP-aware DHT draft, that could deal with options 4 and 5. Maybe in the advanced draft a subset of the HIP hosts themselves are running an integrated HIP-aware DHT in a P2P fashion. -Jeff Hipsec-rg mailing list Hipsec-rg@listserv.cybertrust.com https://listserv.cybertrust.com/mailman/listinfo/hipsec-rg Received on Wed Aug 8 11:18:13 2007 This archive was generated by hypermail 2.1.8 : Mon Oct 29 2007 - 14:16:02 EDT |
||||||||||
|
|||||||||||