1 - 2 - 3 - 4 - 6 - 8 - A - B - C - D - E - F - G - H - I - J - L - M - N - O - P - R - S - T - U - V - W
identifier
Click on the red underlined text to get to the source
... example, "subnet". When this name is used with the term "ID" for
identifier after the name (e.g., "subnet ID"), it refers to the
contents of the named field. When it is used with the term "prefix ...
... Interface Identifiers ...
... interfaces on a link. They are required to be unique within a subnet
prefix. It is recommended that the same interface identifier not be
assigned to different nodes on a link ...
... link. They may also be unique over
a broader scope. In some cases, an interface's identifier will be
derived directly from that interface's link-layer address ...
... interface's link-layer address. The same
interface identifier may be used on multiple interfaces on a single
node ...
... subnets.
Note that the uniqueness of interface identifiers is independent of
the uniqueness of IPv6 addresses. For example, a Global Unicast ...
... address may be created with a local scope interface identifier and a
Link-Local address may be created ...
... Link-Local address may be created with a universal scope interface
identifier.
For all unicast addresses ...
...
Modified EUI-64 format-based interface identifiers may have universal
scope when derived from a universal token (e.g., IEEE 802 ...
...
Modified EUI-64 format interface identifiers are formed by inverting
the "u" bit (universal/local bit ...
... interface identifier from IEEE EUI-64 identifiers. In
the resulting Modified EUI-64 format, the "u" bit ...
... company_id. Appendix A, "Creating Modified EUI-64 Format
Interface Identifiers", provides examples on the creation of Modified
EUI-64 format-based interface identifiers ...
... Interface Identifiers", provides examples on the creation of Modified
EUI-64 format-based interface identifiers.
The motivation for inverting the "u" bit ...
...
The motivation for inverting the "u" bit when forming an interface
identifier is to make it easy for system administrators to hand
configure non-global identifiers ...
... interface
identifier is to make it easy for system administrators to hand
configure non-global identifiers when hardware tokens are not
...
... IPv6 nodes are not required to validate that interface identifiers
created with modified EUI-64 ...
... bit in the Modified EUI-64 format
identifier is to allow development of future technology that can take
advantage of interface identifiers with universal scope.
...
... identifier is to allow development of future technology that can take
advantage of interface identifiers with universal scope.
The details of forming interface identifiers ...
... interface identifiers with universal scope.
The details of forming interface identifiers are defined in the
appropriate "IPv6 over <link ...
... IEEE, "Guidelines for 64-bit Global Identifier (EUI-64) Registration Authority", http://standards.ieee.org/regauth/oui/tutorials/EUI64.html, March 1997. ...
... Appendix A: Creating Modified EUI-64 Format Interface Identifiers ...
... are a number of approaches for creating Modified EUI-64 format
interface identifiers. This appendix describes some of these
approaches.
...
... The only change needed to transform an IEEE EUI-64 identifier to an
interface identifier is to invert the "u" (universal/local) bit ...
... EUI-64 identifier to an
interface identifier is to invert the "u" (universal/local) bit. An
example is a globally unique IEEE ...
... bit, and "m" is the bits of the manufacturer-
selected extension identifier. The IPv6 interface identifier would
be of the form:
...
... bits of the manufacturer-
selected extension identifier. The IPv6 interface identifier would
be of the form:
...
... IEEE 48-bit MAC identifier. This is to insert two octets, with
hexadecimal values of 0xFF and 0xFE (see the Note at the end of
appendix), in the middle of the 48-bit ...
... bit, and "m" is the bits of the manufacturer-
selected extension identifier. The interface identifier would be of
the form:
...
... bits of the manufacturer-
selected extension identifier. The interface identifier would be of
the form:
...
... a node), an implementation may use them to create interface
identifiers due to their availability and uniqueness properties.
Links ...
... There are a number of types of links that have link-layer interface
identifiers other than IEEE EUI-64 or IEEE 802 ...
... create a Modified EUI-64
format identifier is to take the link identifier (e.g., the LocalTalk
8-bit ...
... EUI-64
format identifier is to take the link identifier (e.g., the LocalTalk
8-bit node identifier ...
... link identifier (e.g., the LocalTalk
8-bit node identifier) and zero fill it to the left. For example, a
LocalTalk 8-bit node identifier ...
... node identifier) and zero fill it to the left. For example, a
LocalTalk 8-bit node identifier of hexadecimal value 0x4F results in
the following interface identifier:
...
... 8-bit node identifier of hexadecimal value 0x4F results in
the following interface identifier:
|0 1|1 3|3 4|4 6|
...
... There are a number of links that do not have any type of built-in
identifier. The most common of these are serial links and configured
tunnels ...
... links and configured
tunnels. Interface identifiers that are unique within a subnet
prefix must be chosen.
...
... subnet
prefix must be chosen.
When no built-in identifier is available on a link, the preferred
approach is to use a universal interface identifier ...
... identifier is available on a link, the preferred
approach is to use a universal interface identifier from another
interface or one that is assigned to the node ...
... node to the
same subnet prefix may use the same identifier.
If there is no universal interface identifier ...
... identifier.
If there is no universal interface identifier available for use on
the link, the implementation needs to create ...
... the link, the implementation needs to create a local-scope interface
identifier. The only requirement is that it be unique within a
subnet prefix ...
... The subnet-prefix-unique interface identifier should be generated in
a manner such that it does not change after a reboot of a node or if
...
... algorithm is link and implementation
dependent. The details on forming interface identifiers are defined
in the appropriate "IPv6 over <link ...
... starting
with an IEEE EUI-48 identifier. The incorrect value was used
in earlier versions of the specification due to a
...
... IEEE MAC-48 and
EUI-48 identifiers.
This document purposely continues the use of 0xFF and 0xFE
...
... This document purposely continues the use of 0xFF and 0xFE
because it meets the requirements for IPv6 interface
identifiers (i.e., that they must be unique on the link), IEEE
...
... IEEE
EUI-48 and MAC-48 identifiers are syntactically equivalent, and
that it doesn't cause any problems in practice.
...
... - Changed the text in Section 2.5.1 and Appendix A to refer to
the Modified EUI-64 format interface identifiers with the "u"
bit set to one (1) as universal.
...
... IPv6 nodes are not
required to validate that interface identifiers created in
Modified EUI-64 ...