Hi,
Here is the text I propose to send to the RFC-Editor to resolve the
issue. Take a look and let me know it is is OK.
Thanks,
Bob
Appendix A: Creating Modified EUI-64 Format Interface Identifiers
.........
Links or Nodes with IEEE 802 48-bit MACs
[EUI64] defines a method to create an IEEE EUI-64 identifier
from an
IEEE 48-bit MAC identifier. This is to insert two octets, with
hexadecimal values of 0xFF and 0xFE, in the middle of the 48-bit
MAC
s/0xFE,/0xFE (see the Note at the end of appendix),/
(between the company_id and vendor-supplied id). An example is the
48-bit IEEE MAC with Global scope:
|0 1|1 3|3 4|
|0 5|6 1|2 7|
+----------------+----------------+----------------+
|cccccc0gcccccccc|ccccccccmmmmmmmm|mmmmmmmmmmmmmmmm|
+----------------+----------------+----------------+
where "c" is the bits of the assigned company_id, "0" is the
value of
the universal/local bit to indicate Global scope, "g" is
individual/group bit, and "m" is the bits of the manufacturer-
selected extension identifier. The interface identifier would
be of
the form:
|0 1|1 3|3 4|
4 6|
|0 5|6 1|2 7|
8 3|
+----------------+----------------+----------------
+----------------+
|cccccc1gcccccccc|cccccccc11111111|11111110mmmmmmmm|
mmmmmmmmmmmmmmmm|
+----------------+----------------+----------------
+----------------+
When IEEE 802 48-bit MAC addresses are available (on an
interface or
a node), an implementation may use them to create interface
identifiers due to their availability and uniqueness properties.
.....
Add:
Add to the end of the appendix:
Note: [EUI-64] actually defines 0xFF and 0xFF as the bits to be
inserted to create an IEEE EUI-64 identifier from an IEEE MAC-48
identifier. The 0xFF and 0xFE values are used when starting with an
IEEE EUI-48 identifier. The incorrect value was used in earlier
versions of the specification due to an misunderstanding about the
differences between IEEE MAC-48 and EUI-48 identifiers.
This document purposely continues the use of 0xFF and 0xFE
because it meets
the requirements for IPv6 interface identifiers, specifically that
they must be unique on the link, and that it doesn't cause any
problems in practice. If in the future, a new link type is invented
that uses IEEE EUI-48 and MAC-48 identifiers on the same link, the
0xFF and 0xFF values could be used to convert the EUI-48 identifiers
for use as IPv6 interface identifiers to avoid any potential for
duplicate interface identifiers.
--------------------------------------------------------------------
IETF IPv6 working group mailing list
[email protected]
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
