[p2p-sip] P2PSIP, Kademlia and caching

gregd at research.panasonic.com (Greg Daley) Mon, 29 May 2006 04:06 UTC

From: "gregd at research.panasonic.com"
Date: Mon, 29 May 2006 00:06:30 -0400
Subject: [p2p-sip] P2PSIP, Kademlia and caching
In-Reply-To: <447826BF.5020500@telecomitalia.it>
References: <001d01c680e2$1b53f890$2800a8c0@DSX400> <447826BF.5020500@telecomitalia.it>
Message-ID: <447A7346.1080102@research.panasonic.com>

Hi Enrico,

Enrico Marocco wrote:
> Henry,
> 
>> ...or (2) just to start, one can use openDHT as an emerging _DHT service_.
> 
> Is an external DHT service really different from a traditional location
> service (e.g. a SIP registrar or a dynamic DNS service)?  I can
> understand it only as a temporary solution; if the location service
> wasn't distributed across SIP UAs, would this work have any real value?

There are two logically distinct roles:

SIP UA (perhaps with the ability to access the P2P location service)

and

distributed P2P location storage (for example, using DHT).

These may end up being on the same box, but there's no
logical constraint for them to be.  I mean: it's just a
data storage service, for small blobs of data.


>> I guess we need to evaluate the criteria what to use in the DHT layer. 
>> SIP in the DHT layer is wrong IMHO. This is explained in:
>>
>> http://www.p2psip.org/drafts/draft-shim-sipping-p2p-arch-00.txt  
> 
> Perhaps you mean:
> http://www.ietf.org/internet-drafts/draft-johnston-sipping-p2p-ipcom-02.txt
> 
> The list in sec. 8 is arguable IMHO, but now it's not time for
> discussing how to transport bits.

Actually, I think he meant the former.

Greg