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
interface
Click on the red underlined text to get to the source
... IPv6 addresses are 128-bit identifiers for interfaces and sets of
interfaces (where "interface ...
... identifiers for interfaces and sets of
interfaces (where "interface" is as defined in Section 2 of [IPV6]).
...
... interfaces and sets of
interfaces (where "interface" is as defined in Section 2 of [IPV6]).
There are three types of addresses ...
... Unicast: An identifier for a single interface. A packet sent to a
unicast address is delivered to the interface ...
... single interface. A packet sent to a
unicast address is delivered to the interface identified
by that address.
...
... Anycast: An identifier for a set of interfaces (typically
belonging to different nodes). A packet sent to an
...
... nodes). A packet sent to an
anycast address is delivered to one of the interfaces
identified by that address (the "nearest" one, according
...
... Multicast: An identifier for a set of interfaces (typically
belonging to different nodes). A packet sent to a
...
... nodes). A packet sent to a
multicast address is delivered to all interfaces
identified by that address.
...
... An IPv6 unicast address refers to a single interface. Since each
interface belongs to a single node ...
... unicast address refers to a single interface. Since each
interface belongs to a single node, any of that node's interfaces ...
... interface belongs to a single node, any of that node's interfaces'
unicast addresses may be used as an identifier ...
... node.
All interfaces are required to have at least one Link-Local unicast
address (see Section 2.8 for additional required addresses ...
... unicast
address (see Section 2.8 for additional required addresses). A
single interface may also have multiple IPv6 addresses of any type
(unicast ...
... Unicast addresses with a
scope greater than link-scope are not needed for interfaces that are
not used as the origin or destination of any IPv6 packets ...
... neighbors. This is sometimes convenient for point-to-point
interfaces. There is one exception to this addressing model:
...
... unicast address or a set of unicast addresses may be assigned to
multiple physical interfaces if the implementation treats the
multiple physical interfaces as one interface ...
... multiple physical interfaces if the implementation treats the
multiple physical interfaces as one interface when presenting it
to the internet ...
... physical interfaces if the implementation treats the
multiple physical interfaces as one interface when presenting it
to the internet layer ...
... internet layer. This is useful for load-sharing over
multiple physical interfaces.
Currently, IPv6 ...
... +-------------------------------+---------------------------------+
| subnet prefix | interface ID |
+-------------------------------+---------------------------------+
...
... Interface Identifiers ...
... IPv6 unicast addresses are used to identify
interfaces on a link. They are required to be unique within a subnet
prefix. It is recommended that the same interface identifier ...
... 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 ...
... nodes on a link. They may also be unique over
a broader scope. In some cases, an interface's identifier will be
derived directly from that interface ...
... interface's identifier will be
derived directly from that interface's link-layer address. The same
interface identifier ...
... interface's link-layer address. The same
interface identifier may be used on multiple interfaces on a single
node ...
... link-layer address. The same
interface identifier may be used on multiple interfaces on a single
node, as long as they are attached to different subnets ...
... 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 ...
... unicast addresses, except those that start with the binary
value 000, Interface IDs are required to be 64 bits long and to be
constructed in Modified EUI-64 ...
...
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 ...
... 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 ...
... IPv6 nodes are not required to validate that interface identifiers
created with modified EUI-64 ...
... 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 ...
... node to send an IPv6 packet to itself. It must
not be assigned to any physical interface. It is treated as having
Link-Local scope, and may be thought of as the Link-Local ...
... Link-Local scope, and may be thought of as the Link-Local unicast
address of a virtual interface (typically called the "loopback
interface") to an imaginary link that goes nowhere.
...
... Link-Local unicast
address of a virtual interface (typically called the "loopback
interface") to an imaginary link that goes nowhere.
...
... routing prefix | subnet ID | interface ID |
+------------------------+-----------+----------------------------+
...
... identifier of a link within the site, and the
interface ID is as defined in Section 2.5.1.
All Global Unicast ...
... start with binary
000 have a 64-bit interface ID field (i.e., n + m = 64), formatted as
described in Section 2.5.1. Global Unicast addresses ...
... binary 000 have no such constraint on the size or structure of the
interface ID field.
Examples of Global Unicast ...
... starting with a binary value
other than 000 (and therefore having a 64-bit interface ID field) can
be found in [GLOBAL].
...
... 64 bits |
+----------+-------------------------+----------------------------+
|1111111010| 0 | interface ID |
+----------+-------------------------+----------------------------+
...
... +----------+-------------------------+----------------------------+
|1111111011| subnet ID | interface ID |
+----------+-------------------------+----------------------------+
...
... anycast address is an address that is assigned to more than
one interface (typically belonging to different nodes), with the
property that a packet sent to an anycast address ...
... property that a packet sent to an anycast address is routed to the
"nearest" interface having that address, according to the routing
protocols' measure of distance.
...
... unicast addresses. When a
unicast address is assigned to more than one interface, thus turning
it into an anycast address, the nodes ...
... address that identifies the topological region in which all
interfaces belonging to that anycast address reside. Within the
region identified by P, the anycast address ...
... anycast address is syntactically
the same as a unicast address for an interface on the link with the
interface identifier ...
... address is an identifier for a group of interfaces
(typically on different nodes). An interface ...
... interfaces
(typically on different nodes). An interface may belong to any
number of multicast groups. Multicast addresses ...
...
0 reserved
1 Interface-Local scope
2 Link-Local scope
...
...
Interface-Local scope spans only a single interface on a node
and is useful only for loopback ...
...
FF01:0:0:0:0:0:0:101 means all NTP servers on the same interface
(i.e., the same node) as the sender ...
... group of all IPv6 routers,
within scope 1 (interface-local), 2 (link-local), or 5 (site-local).
...
... A node is required to compute and join (on the appropriate interface)
the associated Solicited-Node multicast addresses ...
... anycast addresses that have been configured for the node's interfaces
(manually or automatically).
...
... Anycast addresses that have been
configured for the node's interfaces (manually or
automatically).
...
... Subnet-Router Anycast addresses for all interfaces for which
it is configured to act as a router.
...
... 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.
...
... EUI-64 identifier to an
interface identifier is to invert the "u" (universal/local) bit. An
example is a globally unique IEEE ...
... bits of the manufacturer-
selected extension identifier. The IPv6 interface identifier would
be of the form:
...
... bits of the manufacturer-
selected extension identifier. The interface identifier would be of
the form:
...
... IEEE 802 48-bit MAC addresses are available (on an interface or
a node), an implementation may use them to create ...
... 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 ...
... 8-bit node identifier of hexadecimal value 0x4F results in
the following interface identifier:
|0 1|1 3|3 4|4 6|
...
... links and configured
tunnels. Interface identifiers that are unique within a subnet
prefix must be chosen.
...
... 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 ...
... approach is to use a universal interface identifier from another
interface or one that is assigned to the node itself. When using
this approach, no other interface ...
... interface or one that is assigned to the node itself. When using
this approach, no other interface connecting the same node to the
same subnet prefix ...
... 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
...
... a manner such that it does not change after a reboot of a node or if
interfaces are added or deleted from the node.
...
... algorithm is link and implementation
dependent. The details on forming interface identifiers are defined
in the appropriate "IPv6 over <link ...
... 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
...
... - 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 ...