Hi, it's not really clear to me what (particular) problem we are trying to solve here. I don't think that it's a good idea to introduce a structure into the IID. The IID space is usually flat and the u- and g-bit semantics are only relevant in the IEEE EUI format. It's clear that we map them somehow into the IID if creating a modified EUI-64 as IID, but I don't think that we should derive something _from_ the IID (yes, I know that also RFC4941 cares about setting the u-bit, but it's not really clear that we gain anything from it?).
I briefly read into the 4rd draft, but it's not entirely clear to me whether other solutions don't exist. Maybe there are other means to get the context knowledge that this particular IPv6 address has a special structure encoded somehow. Regards, Roland -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
