Aren't we putting the cart before the horse? An IANA registry cannot be the only way to avoid collisions. An address allocation program may take into account the state of the registry at the time the code is written, but is seldom updated after that. Just getting a number allocated by IANA will not prevent competing use of that number for other purposes.
Agreed. But there is not much we can do about this.
There is a well established way to reserve MAC addresses, using a range of identifiers assigned to IANA. There is also a well established way to derive IPv6 interface identifiers from MAC addresses. It has been specified for over 10 years, and you can be sure that all IPv6 implementations abide by it. If RFC 2526 and RFC 4214 followed that framework, there would not be any problem. So, should we not instead go update these two RFC?
Not really. You are assuming here that all IIDs are generated from MAC addresses. IIDs can be generated using other methods like CGA, Privacy Addresses etc. Hence reserving a range of MACs/OUIs is not sufficient.
Thanks Suresh -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
