I have several technical and organizational comments regarding this
document.
The document states:
"Thus, it is recommended to implement also other mechanisms for
overriding this default, for example: manual configuration, L2
mechanisms and/or DHCPv6."
I think that it should be required (a MUST) that nodes that
implement this specification provide a method to override the
default values manually.
The document should also specify whether the default DNS addresses
will or won't be considered part of the DNS server list when DNS
server addresses are configured via other means. For example, if
a host receives a single DNS server address via DHCP, will it
fall-back to using these well-known addresses if the DNS server
at the DCHP-configured address fails to respond?
Listing anything as a "last resort" is problematic, because there
may be something that comes along later that should only be
used if this fails. Instead, I would like to see this document
explicitly define how this mechanism does/doesn't interoperate
with other mechanisms (DHCP, SLP, manual configuration).
The document also states:
"d) Having an "announcement" protocol that the DNS resolver could
use to advertize the host route to the nearby router. Details of
such a protocols are out of scope of this document, but something
similar to [MLD] is possible."
In my opinion, this section points out one major weakness with
this approach. We _still_ need some way to configure the location
of DNS servers in the network... Today, we do that on hosts (often
using DHCP to provide the information, effectively moving the
configuration to the DHCP server). This draft proposes moving
that knowledge off of hosts and DHCP servers, and into the routing
system, but it doesn't actually specify how the routing system
will get the information.
Margaret
--------------------------------------------------------------------
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]
--------------------------------------------------------------------
