On Thu, 2010-07-08 at 15:22 +1000, Robin Whittle wrote: > In (msg07061 - "Re: [rrg] ILNPv6 Mobility problem") Steven Blake wrote: > > > Name one modern device that doesn't have a unique hardware ID that > > could be used to form a global-scope EUI-64? > > What really matters is whether this is a reasonable basis for the future. > > Since not every host has or will have a MAC address, your proposed > algorithm would need to work from a variety of different types of > hardware ID.
All IEEE technologies have native EUI-48s (mappable to modified EUI-64) or EUI-64s, to my knowledge. That is not going to change in my lifetime. Home Plug and G.hn also appear to have MAC addresses, as does Bluetooth. Cellular has IMEI (3GPP technologies) or MEID (3GPP2 technologies). Both are uniquely mappable to EUI-64 (see http://tools.ietf.org/html/draft-dupont-ipv6-imei-10). Not sure why this didn't progress to RFC, but possibly because 3GPP and 3GPP2 have put a mapping in their own specs. ATM AALs do not have MAC addresses (boo hoo). SONET/SDH/OTN does not have a MAC address, but most SONET ports are not mobile. You can be sure that any box with a SONET port has a management Ethernet port. Am I missing something? It is IMHO reasonable to suppose that anyone designing new link layers is going to try to accommodate IPv6 SLAAC. Regards, // Steve _______________________________________________ rrg mailing list [email protected] http://www.irtf.org/mailman/listinfo/rrg
