draft-ietf-6lo-nd-gaao authors, Looking at https://datatracker.ietf.org/doc/html/draft-ietf-6lo-nd-gaao-11 again, I still think that a better choice would be to reuse DHCPv6 instead of adding the new GAAO option.
Appendix A.3 shows that in terms of bytes and messages, DHCPv6 with Rapid Commit is essentially as efficient as GAAO. The remaining inefficiency mentioned in the draft is that currently, DHCPv6 SOLICITs are sent to multicast addresses. This is easy to fix: define a well-known anycast address for the DHCPv6 server to use in 6lo deployments (as Esko mentioned at the mic). That will be exactly as efficient as the GAAO option if the server is on the first-hop router. But it could also optionally (or in the future) support scenarios where the server is not in the first-hop router. There is already an M bit in the RA that I think could be used to signal support for this. This seems better than the GAAO option because it does not require defining a new protocol and provides additional flexibility. If I'm missing something, or if we do not take this approach for some other reason, the draft should explain why. Cheers, Lorenzo
_______________________________________________ 6lo mailing list -- [email protected] To unsubscribe send an email to [email protected]
