All Intel® Ethernet adapters have EUI-48* identifiers. As far as I know, common applications that make use of EUI-64* identifiers, such as IPv6, easily convert the EUI-48 identifier to EUI-64. Therefore devices with EUI-48 identifiers should be automatically compatible with applications uing EUI-64.
Are you running into a situation where you require EUI-64 identifiers to work?
We are working on to give support for IPv6 in our application. When we query MAC address on IPV6 we are getting EUI-48 address fprmat. We are looking for such hardware that gives EUI-64 address format on IPV6. Is that application has to do the conversion on identifying IPV6? If Yes then, What about this conversion if we end up on such hardware that gives EUI-64 format address?
To be compatible with both EUI-48 or EUI-64, an application will have to recognize both formats and do the proper conversions. According to a PacketLife blog entry, EUI-64 in IPv6, when IPv6 converts MAC-48 address to EUI-64 it adds reserved bytes that identify the EUI-64 number as having been converted from the MAC address. No future EUI-64 identifier can use those same bytes because they are reserved. That way, there should be no problem between devices identified using EUI-48 when mixed with devices using EUI-64.