RE: RFC 5006 status

["STARK, BARBARA H (ATTLABS)" <bs7652@att.com>]

> I can see utility in the *limited* extension of RDNSS to standards
> track, because it allows zero-configuration hosts on IPv6 networks
> where all the routers advertise O=0 to have some hope of resolving
> domain names after joining them.  They don't get that today, and I
> don't see a good way to use DHCP to do anything about that.

I'm confused by this O=0 proposal. I thought the O flag was intended to
announce that there was a DHCP server available with other (non-IA)
configuration info, including NTP, SIP server, DNS, etc. Is this
suggesting that the O flag be used exclusively to announce the
availability of DNS info in DHCPv6, and not any other config info?
Should clients just guess whether DHCPv6 is available for non-IA,
non-DNS info? Is it suggesting that if clients do not support RFC5006
for getting DNS info (but do support DHCPv6), that they not be given a
hint that a DHCPv6 server is available that might have other config
info? Or, with O=0, would there be a simultaneous proposal that support
for RFC5006 be mandatory in clients?

Just trying to understand this, since I've seen it suggested before, and
can't quite figure out the full range of expected behavior in the wild
frontier of IPv6 home networks.
Barbara