[p2p-sip] Fwd: what's wrong with DNS?

ag at ag-projects.com (Adrian Georgescu) Wed, 29 November 2006 19:58 UTC

From: "ag at ag-projects.com"
Date: Wed, 29 Nov 2006 20:58:24 +0100
Subject: [p2p-sip] Fwd: what's wrong with DNS?
In-Reply-To: <02de01c713ef$6628cd50$640fa8c0@cis.neustar.com>
References: <02de01c713ef$6628cd50$640fa8c0@cis.neustar.com>
Message-ID: <0BA3F014-8AC0-4071-B81B-100D28C98E3E@ag-projects.com>

>> Except, of course, use DNS.
> I expect we'll use DNS.  We haven't talked a lot, for example,  
> about WHAT,
> EXACTLY, you get from the DHT.  Is it a domain name or an IP  
> address?  I'd
> think it was a domain name, and you use DNS to resolve that to an IP
> address.  No consensus on that, and it hasn't come up yet.

The DNS can solve only the address resolution of the non-NAT-ed peer.  
One needs
more than dynamic DNS to merge a self-organizing network with SIP
functionality. No DNS server will be able to do parallel and serial
forking, aggregate presence information, NAT traversal, buddy list
synchronization among devices, redirect for not online to name a few
things one needs in the day-to-day communications. DNS is good for
bootstrap and and for providing global addressable URIs.

I think the WG should concentrate on a methodology of how to make a  
generic lookup
for a given resource when you have a list of boot strap nodes.  
Something like:

1. Use DNS or other bootstrap method to find a live peer in the P2P  
network
2. Perform a lookup function to the node to find a resource/service  
for a specific user in the P2P network

Example:

lookup sip_proxy for user at example.com
lookup voicemail for user at example.com
lookup storage for user at example.com
..

Adrian