address used when M or O bit is set
On Wed, 2012-04-04 at 16:12 +0200, Fernando Gont wrote:
> 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 th
On Wed, 2012-04-04 at 16:12 +0200, Fernando Gont wrote:
> 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.
At Wed, 4 Apr 2012 16:38:45 +0200,
Dominik Elsbroek wrote:
> > 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
>
Hi Jeremy,
The DHCPv6 client on a host will use its link-local address as the
source address and ff02::1:2 as the destination address.
Cheers
Suresh
On 04/04/2012 10:50 AM, Duncan, Jeremy wrote:
> ---I am still very curious which address a client should use, if the O or
> M flag is set, to find
Dominik,
The M and O flags are defined in RFC4861. They are not removed (or deprecated).
Bob
On Apr 4, 2012, at 6:55 AM, Dominik Elsbroek wrote:
> Hi all,
>
> the discussion on the mailing list titled "RA "requires" DHCPv6 ?" is
> quite confusingto me since RFC 4862 states, the flags M and O
---I am still very curious which address a client should use, if the O or
M flag is set, to find a DHCPv6 server.
The server listens on ff02::1:2 and/or ff02::1:3
0101001101100101011011010111011001010111001000100100011001101001
Jeremy Duncan
Senior Director, IPv6 Network Architect Sal
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.
Hi, Dominik,
On 04/04/2012 03:55 PM, Dominik Elsbroek wrote:
> the discussion on the mailing list titled "RA "requires" DHCPv6 ?" is
> quite confusingto me since RFC 4862 states, the flags M and O are
> removed, but not deprecated.
What's removed is the corresponding text, not the bits. See page
