Re: 64bit MAC addresses and SLAAC

[Philip Homburg <[e-mail]>]

> - the router still needs the resolution. There's stuff in
> draft-ietf-6man-grand and/or RFC 8505 for that.  - handling mobility
> vs. anycast. There's stuff in draft-ietf-rift-rift-12#section-4.3.3.3
> for that.  - all NBMAs are not hub and spoke so there's a routing
> game to trigger. There's stuff in draft-ietf-roll-unaware-leaves
> for that.  - still need to feed the mapping server for the overlay.
> There's stuff in draft-thubert-6man-unicast-lookup for that.  -
> zerotrust / SAVI is also missing and SEND did not cut it. There's
> stuff in draft-ietf-6lo-ap-nd for that.
> 
> For more detaiuls, there's draft-thubert-6man-ipv6-over-wireless,
> just let you go over it and comment if you really care.

Link address resolution can be solved to colocating a DHPCv6 relay with the
router. The relay can maintain IPv6 address to link layer address mappings
and inject those into the router's neighbor cache.

It seems to me that letting a host generate an address using SLAAC and then
forcing the host to register the address somewhere is just all of the work that
DHCPv6 does with none of the benefits.

Of course, if DHCPv6 would be allowed to have a default router option, then the
use of multicast could be reduced even further.