>> I am not clear what aspect of the semantics of u==1 and the >> relationship to EUI-64 is a dead duck. Currently, if you see >> something with u==1, you know it was made from an EUI-64. > > Actually, you don't. You know that it looks as if it was made in > Modified EUI-64 format, but you don't know that there is a genuine MAC > address behind it. You can apply heuristics (like "Is 0xFFFE present?" > and "Is the OUI an IEEE-assigned value?") but that's all. > > Also, u==0 does not imply that it is not Modified EUI-64. The examples > in RFC 4291 all use EUI-64 with u==0, i.e. Modified EUI-64 with u==1, > but those are only examples. > > In the end all you have is 64 meaningless bits, as far as I can tell.
well, not entirely meaningless, eh? :) we do line packets to go back and forth. i hate to sound like a broken record, but magic bits are almost never worth the pain. randy -------------------------------------------------------------------- IETF IPv6 working group mailing list ipv6@ietf.org Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
