[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


To: Jim Reid <jim@rfc1035.com>
CC: bill <bmanning@karoshi.com>, Alain Durand <Alain.Durand@sun.com>, itojun@iijlab.net, dnsop@cafax.se
From: Masataka Ohta <mohta@necom830.hpcl.titech.ac.jp>
Date: Thu, 13 Nov 2003 05:10:54 +0900
In-Reply-To: <19715.1068657470@gromit.rfc1035.com>
Sender: owner-dnsop@cafax.se
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)
Subject: Re: well-known addresses / was DNS discovery

Jim Reid;
 
>     bill> 	Ohta-san, would you be comfortable with 200,000,000
>     bill> devices being shipped with the IP address 131.112.32.188
>     bill> (the address of one of your organizations nameservers) being
>     bill> burned into eeprom?
> 
>     bill> 	Yes, I know we do it now and it reduces the level of
>     bill> effort in getting new features deployed, but in -EVERY-
>     bill> case, the use of well known addresses has caused problems.
> 
> Like Netgear hard-wiring the address of a University of Wisconsin NTP
> server into the firmware of ther products. Every one of those boxes
> sends an NTP request once a second to that UoW server.

That is not an argument applicable to addresses dedicated to anycast.

With anycast, that someone send something to an address
and that someone send something to a server are different
things. Read a section on scoping in my draft.

						Masataka Ohta


#----------------------------------------------------------------------
# To unsubscribe, send a message to <dnsop-request@cafax.se>.

Home | Date list | Subject list