Hi Jari: In case of PMIPv6, we need the interface ID allocation for PMIv6 domain-wide usage. We may not be able tie this to a specific EUI-64 identifier derived from a MAC identifier of any individual MAG hosting this configuration. But, if your recommendation is to tie the IPv6 interface identifier to the reserved link-layer identifier (the other IANA action), that should be fine. But, the reserved block that Suresh has in his spec is not tied to any EUI-64 block ? That implies, we need an interface ID allocation from a new block ? Or, recommend the node to generate the interface ID based on the reserved Mac address and not allocate from the block Suresh created ? Hope, I'm not missing the point. Regards Sri On 9/18/11 11:35 PM, "Jari Arkko" <jari.arkko@xxxxxxxxx> wrote: > Following up with a personal comment. > > The draft allocates an interface ID and an EUI-64 MAC identifier from the IANA > block. These are two separate, unrelated allocations. > > The main criticism in RFC 5453 for making additional interface ID allocations > is that old implementations do not know about them and may collide when making > an allocation. I'm wondering if it would be better to allocate an interface ID > that is based on the allocated EUI-64 identifier per RFC 2464? Then we would > at least use the same format as other interface IDs and a collision would > likely mean inappropriate use of the IANA EUI-64 identifiers. Note that > privacy and cryptographic addresses set the u/l bit to zero, whereas EUI-64 > interface IDs usually have it at one. Sri's draft is silent on what kind of > number should be allocated for the interface ID, perhaps some guidance here > would be useful. > > Not that collisions are likely in 2^64 space anyway, maybe I'm worried about > nothing. > > Jari > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > ipv6@xxxxxxxx > Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- _______________________________________________ Ietf mailing list Ietf@xxxxxxxx https://www.ietf.org/mailman/listinfo/ietf