Would such a rendezvous service work if their were NATs between each of the 
participants and the service itself (regardless of whether it is hosted on a NAT or 
not)? If so, wouldn't such a solution alter peer-to-peer to become a hub-and-spoke 
service requiring ISP mediation in the Internet case as opposed to peer-to-peer?

-----Original Message-----
From: David T. Perkins [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, January 31, 2001 3:41 PM
To: Michael Richardson; [EMAIL PROTECTED]
Subject: Re: [midcom] WG scope/deliverables 


HI,

On the list below, I believe that peer-to-peer applications like
napster can work in a NAT world. All you need is a registration
and rendezvous service to put the two peers together. This can
be part of the box that also provides the NAT service. 

At 05:54 PM 1/31/2001 -0500, Michael Richardson wrote:

>  NAT's work for web surfing. No dispute here.
>
>  NAT's make the Internet into TV.
>
>  NAT's suck for napster-type applications.
>  It was napster like (e.g. peer-to-peer) things that made the Internet
>popular. Based upon some data on "web ready cell phones" being used primarily
>to send text messages (e.g. do "peer-to-peer" type things), I'd say that
>the love for NATs will very soon decline.
>
>   :!mcr!:            |  Solidum Systems Corporation, http://www.solidum.com
>   Michael Richardson 

Regards,
/david t. perkins

Reply via email to