On Wed, 5 Mar 2003, Bill Manning wrote:
> As a co-author of a couple of previous DNS discovery IDs, I would
> have to agree that as postulated, the current DNS discovery work
> has pretty much been OBE. (overtaken by events)
> There have been two distinct BOFs on this idea in the last five years
> so I don't think another BOF will be very productive.

I assume those BOFs were for IPv4?

When considering DNS discovery in IPv6 context, we need to consider the 
scope of such discovery -- ie. where it is expected to be used, and 
possible subsequent configuration methods.

As I see it, DNS discovery can either be:

 1) "all that you need"
 2) "the first step"

In the first model, you need no other information.  When you've completed 
DNS discovery, that's it.  This is a very valid scenario in e.g. mobile 
environments, when visiting networks (for example, at IETF's, I run dhcpv4 
*only* to get the DNS address :-( ).

In the second model, you generally want to obtain also other information.  
This typically applies to non-visiting networks, like an enterprise LAN.
The question becomes which tool is used (or fits best) in getting that 
information.  If you need/want to use DHCPv6 (stateful or stateless) for 
that, no use having a separate mechanism for DNS and the rest.

The critical thing in the 2nd model is whether DNS resolvers enable some 
config mechanisms: they certainly enable being able to surf to the home 
page of your own (or enterprise) from where you can obtain some values, 
scripts which give you the configuration you want etc.  But perhaps more 
importantly, you could place configuration details in the DNS, in some 
format.

So, basically if one believes roaming users or DNS-based configuration 
would be nice, some easy DNS resolver configuration mechanism would be 
"very nice".

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings

--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page:                      http://playground.sun.com/ipng
FTP archive:                      ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------

Reply via email to