If M-Policy is 1, the host SHOULD invoke Host Configuration Behaviour
for address and other configuration information, regardless of the
change of the state variables. The host SHOULD NOT invoke
Information Configuration Behaviour regardless of O-Policy. Note,
however, that if the available DHCPv6 servers only provide the
service for the Information Configuration Behaviour, the host will
even not be able to configure other configuration parameters than
addresses. Thus, it is generally inadvisable to set M-Policy to 1,
unless there is a particular reason to do so.
==> is it really true that if a full DHCPv6 client is initiated, and
the server is 'stateless', the DHCPv6 client doesn't get back the
That would seem to be a big problem for DHCPv6 deployment if servers
are stateless, and I think someone has claimed that this shouldn't be
If the text you wrote is correct, that would mean that to get robust
behaviour, the host would have to either rely that the capabilities of
the DHCPv6 servers match those that are advertised in the route
advertisements, or to always just "prepare for the worst" by firing
off a parallel information-request as well.
And then it would seem to make sense for prudent DHCPv6 implementers
to do everything they can to ensure they'll receive information-reply
from stateful servers as well.. because that's better than nothing,
and better than relying on how the bits in RAs have been configured!