Duncan,
Vijay-
The only thing I could find is that it's just standard practice to
use FF
FE.. For example, if you use privacy extensions then there is no FF FE
because its address is hashed right?
No, there is no FF FE because the IIDs created by RFC4941 have local
significance. From section 3.2.1:
3. Take the leftmost 64-bits of the MD5 digest and set bit 6 (the
leftmost bit is numbered 0) to zero. This creates an interface
identifier with the universal/local bit indicating local significance
only.
IIDs with local significance only need to be unique on the link.
Suggest reading the IID relateds sections and appendix in RFC4291.
I think it's just a 16 bit filler for a
MAC 48.. See below from the IEEE:
http://standards.ieee.org/regauth/oui/tutorials/EUI64.html
The FFEE is used to extend an EUI-48 to an EUI-64. It is defined in
the Section titled "Encapsulated EUI-48 values". Namely, "A unique
EUI-64 value is generated by concatenating the company_id, an FFFE
valued label, and the extension identifier values".
Even RFC 4291 didn't really go into much detail either..
http://www.ietf.org/rfc/rfc4291.txt
RFC4291 references the above mentioned EUI64.html document.
Bob
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
