Hi Fernando,
> What's removed is the corresponding text, not the bits. See page 19 of
> RFC 4861: the bits are still there.
>
In RFC4862, Appendix C there is one point:
Removed the text regarding the M and O flags, considering the
maturity of implementations and operational experiences.
ManagedFlag and OtherConfigFlag were removed accordingly. (Note
that this change does not mean the use of these flags is
deprecated.)
Not sure how to interprete this. Perhapts I am just missing a link,
but M and O flag in RFC 4861 doesn't tell how to do SLAAC, e.g. when
the nameserver should be determined by DHCPv6-server.
>
>> They don't even longer exist, but still
>> exist?
>
> I'm curious about why the corresponding text was removed. In particular
> when at the time (2007) the DNS options was not yet widely implemented,
> and hence you *needed* DHCPv6 to learn the addresses of recursive DNS
> servers dynamically.
>
I am still very curious which address a client should use, if the O or
M flag is set, to find a DHCPv6 server.
Cheers,
Dominik
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
