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
link
Click on the red underlined text to get to the source
...
All interfaces are required to have at least one Link-Local unicast
address (see Section 2.8 for additional required addresses). A
...
... multicast) or scope. Unicast addresses with a
scope greater than link-scope are not needed for interfaces that are
not used as the origin or destination ...
... IPv4 model in that a subnet prefix is
associated with one link. Multiple subnet prefixes may be assigned
to the same link ...
... Multicast 11111111 FF00::/8 2.7
Link-Local unicast 1111111010 FE80::/10 2.5.6
Global Unicast ...
... site-local unicast (deprecated, see Section 2.5.7),
and Link-Local unicast. There are also some special-purpose subtypes
of Global Unicast ...
... host (but still rather simple) may
additionally be aware of subnet prefix(es) for the link(s) it is
attached to, where different addresses may have different values for
...
... 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 not be
...
... interface identifier not be
assigned to different nodes on a link. They may also be unique over
a broader scope. In some cases, an interface's identifier ...
... identifier will be
derived directly from that interface's link-layer address. The same
interface identifier may be used on multiple interfaces ...
... created with a local scope interface identifier and a
Link-Local address may be created with a universal scope interface
identifier.
...
... EUI64]) or may have local scope where a
global token is not available (e.g., serial links, tunnel end-points)
...
... hardware tokens are not
available. This is expected to be the case for serial links and
tunnel end-points ...
... interface identifiers are defined in the
appropriate "IPv6 over <link>" specification, such as "IPv6 over
Ethernet ...
... not be assigned to any physical interface. It is treated as having
Link-Local scope, and may be thought of as the Link-Local unicast
address of a virtual interface ...
... physical interface. It is treated as having
Link-Local scope, and may be thought of as the Link-Local unicast
address of a virtual interface (typically called the "loopback
interface ...
... unicast
address of a virtual interface (typically called the "loopback
interface") to an imaginary link that goes nowhere.
The loopback ...
... structured) value assigned to a site (a cluster of subnets/links),
the subnet ID is an identifier ...
... the subnet ID is an identifier of a link within the site, and the
interface ID is as defined in Section 2.5.1.
...
...
Link-Local addresses are for use on a single link. Link-Local
addresses have the following format:
...
...
Link-Local addresses are for use on a single link. Link-Local
addresses have the following format:
...
... Link-Local addresses are for use on a single link. Link-Local
addresses have the following format:
| 10 |
...
... +----------+-------------------------+----------------------------+
Link-Local addresses are designed to be used for addressing on a
single link ...
... Link-Local addresses are designed to be used for addressing on a
single link for purposes such as automatic address configuration,
neighbor discovery ...
...
Routers must not forward any packets with Link-Local source or
destination addresses to other links ...
... anycast address is the prefix that
identifies a specific link. This anycast address is syntactically
the same as a unicast address ...
... the same as a unicast address for an interface on the link with the
interface identifier set to zero ...
... 1 Interface-Local scope
2 Link-Local scope
3 reserved
4 Admin-Local scope
...
... multicast.
Link-Local multicast scope spans the same topological region as
the corresponding unicast ...
... identifying itself:
o Its required Link-Local address for each interface.
...
...
Depending on the characteristics of a specific link or node, there
are a number of approaches for creating Modified EUI-64 ...
... interface
identifiers due to their availability and uniqueness properties.
Links with Other Kinds of Identifiers
...
... Identifiers
There are a number of types of links that have link-layer interface
identifiers other than IEEE ...
...
There are a number of types of links that have link-layer interface
identifiers other than IEEE EUI-64 ...
... EUI-64
format identifier is to take the link identifier (e.g., the LocalTalk
8-bit node identifier ...
... indicate local scope.
Links without Identifiers
...
... Identifiers
There are a number of links that do not have any type of built-in
identifier. The most common of these are serial links ...
... links that do not have any type of built-in
identifier. The most common of these are serial links and configured
tunnels. Interface identifiers ...
...
When no built-in identifier is available on a link, the preferred
approach is to use a universal interface identifier from another
...
... If there is no universal interface identifier available for use on
the link, the implementation needs to create a local-scope interface
identifier. The only requirement ...
...
The selection of the appropriate algorithm is link and implementation
dependent. The details on forming interface identifiers are defined
...
... interface identifiers are defined
in the appropriate "IPv6 over <link>" specification. It is strongly
recommended that a collision detection algorithm be implemented as
...
... because it meets the requirements for IPv6 interface
identifiers (i.e., that they must be unique on the link), IEEE
EUI-48 and MAC ...