Re: purpose of m/o bit

["da Silva, Ron" <rdasilva at va.rr.com>]

There are nine scenarios, right?

1) RA w/auto-conf, M off, O off
2) RA w/auto-conf, M on, O off
3) RA w/auto-conf, M off, O on
4) RA w/auto-conf, M on, O on
5) RA w/o auto-conf, M off, O off
6) RA w/o auto-conf, M on, O off
7) RA w/o auto-conf, M off, O on
8) RA w/o auto-conf, M on, O on
9) No RA

>From a cable deployment perspective, I would expect...

1) CM stateless auto-conf from advertised route(s)
2) CM stateless auto-conf from advertised route(s) plus DHCPv6 for
additional address(es)
3) CM stateless auto-conf from advertised route(s) plus DHCPv6 for
addition info
4) CM stateless auto-conf from advertised route(s) plus DHCPv6 for
additional address(es) and additional info
5) same behavior as #9 below ?
6) DHCPv6 for address(es) only
7) DHCPv6 for additional info only
8) DHCPv6 for address(es) and additional info
9) CM stateless auto-conf link local address followed by DHCPv6 for
additional address(es) and/or other info (same behavior as #5)

This seems way to complicated though, and it would be much more
deterministic for a CM to simply do #4 in all cases which would make the
M/O bits useless.

-ron

--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6 at ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------