A host can be configured with a list of DNS recursive resolvers
through the DHCPv6 "DNS Recursive Name Server" option [RFC3646].
This option can be passed to a host through a subset of DHCPv6
[RFC3736]. Two alternative mechanisms are under consideration:
the use of well-known addresses [21] and the use of Router
Advertisements to convey the information [22].
No consensus has been reached as of this writing (April 2004).
What does the WG think about this -- That is,
Do you have a problem with the above wording?
Someone who isn't aware of the issue (and if we assume everyone is, why include any text?) might take this to mean that using DHCP is the way to go and/or without problems, which IMO isn't the case. I think working it something like "In situations where DHCPv6 is available, a host can discover a list of DNS resolvers through [...] Ways to discover or configure DNS resolvers in situations where DHCPv6 isn't available or appropriate are under consideration [...]".
If we feel it's necessary to provide guidance to implementers it would be good to say something about well-known addresses, as this solution has the interesting property that it can largely implemented before it's standardized. Pretty much all that's needed is a global list of DNS servers that is called upon when no "local" (specific to the active configuration, those of you who use a Mac know what I mean) information is available. Obviously the list should be empty at this time.
. dnsop resources:_____________________________________________________ web user interface: http://darkwing.uoregon.edu/~llynch/dnsop.html mhonarc archive: http://darkwing.uoregon.edu/~llynch/dnsop/index.html
