Re: [v6tc] Issue 2: service discovery: automatic or manual?

> On Tue, 2005-01-18 at 04:21 -0800, Alain Durand wrote:
>> On Jan 18, 2005, at 3:37 AM, Miguel Angel Diaz wrote:
>> >>> of course, you first has to know your public IPv4 address ;-) It
>> >>> doesn't matter if you have one or more NAT levels, the only thing is
>> >>> to find out your final public address. There are several ways to do 
>> >>> it
>> >>> and one of the most used is the STUN protocol, RFC 3489.
>> >>
>> >> I was expecting this answer. Can you now tell how to discover which
>> >> stun server to use?
>> >>
>> >
>> > I see where you want to arrive: the stun server discovery is an issue 
>> > itself, but currently there are several public stun servers deployed 
>> > all over the world and they are available for free to all the users. 
>> > Just some of them:
>> >
>> > stun01.sipphone.com,
>> > stun.voxgratia.org,
>> > stun1.vovida.org,
>> > stun.fwdnet.net,
>> > stun.intervivo.net
>> >
>> > Why don't use them?
>> 
>> Simply because hardcoding names like that in implementations that need 
>> to be
>> maintained for 10-20 years is a bad thing.
> 
> Not even mentioning the abuse of resources provided by others.
> 
> And what is the use of using a STUN in the first place, if it cannot be
> reached you are dead in the water.

With pings or traceroutes the STUN protocol could be avoided. Even better, trying to reverse the IP of the ISP gateway (first hop from the customer's network) would be a nice solution to discover the ISP's domain name.

Regards
Miguel

**********************************
Madrid 2003 Global IPv6 Summit
Presentations and videos on line at:
http://www.ipv6-es.com

This electronic message contains information which may be privileged or confidential. The information is intended to be for the use of the individual(s) named above. If you are not the intended recipient be aware that any disclosure, copying, distribution or use of the contents of this information, including attached files, is prohibited.