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
node
Click on the red underlined text to get to the source
... identifier for a set of interfaces (typically
belonging to different nodes). A packet sent to an
anycast address is delivered to one of the interfaces ...
... identifier for a set of interfaces (typically
belonging to different nodes). A packet sent to a
multicast address is delivered to all interfaces ...
... single interface. Since each
interface belongs to a single node, any of that node's interfaces'
...
... 3. An alternative form that is sometimes more convenient when dealing
with a mixed environment of IPv4 and IPv6 nodes is
x:x:x:x:x:x:d.d.d.d, where the 'x's are the hexadecimal values of
the six high-order 16-bit ...
... 2001:0DB8:0000:0000:0000:0000:0000:0CD3
When writing both a node address and a prefix of that node ...
... subnet prefix), the two can be combined as follows:
the node address 2001:0DB8:0:CD30:123:4567:89AB:CDEF
and its subnet ...
... the future.
IPv6 nodes may have considerable or little knowledge of the internal
structure of the IPv6 address, depending on the role ...
... structure of the IPv6 address, depending on the role the node plays
(for instance, host versus router ...
... (for instance, host versus router). At a minimum, a node may
consider that unicast addresses (including its own) have no internal
...
... 128 bits |
+-----------------------------------------------------------------+
| node address |
+-----------------------------------------------------------------+
...
... Except for the knowledge of the subnet boundary discussed in the
previous paragraphs, nodes should not make any assumptions about the
structure of an IPv6 address.
...
... subnet
prefix. It is recommended that the same 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 ...
... interface identifier may be used on multiple interfaces on a single
node, as long as they are attached to different subnets.
...
... much simpler 0:0:0:1, 0:0:0:2, etc.
IPv6 nodes are not required to validate that interface identifiers
...
... address 0:0:0:0:0:0:0:0 is called the unspecified address. It
must never be assigned to any node. It indicates the absence of an
address. One example of its use is in the Source Address ...
... loopback address.
It may be used by a node to send an IPv6 packet to itself. It must
not be assigned to any physical interface ...
... address must not be used as the source address in IPv6
packets that are sent outside of a single node. An IPv6 packet with
a destination address ...
... destination address of loopback must never be sent outside of a
single node and must never be forwarded by an IPv6 router. A packet
...
... address type is used to represent the addresses of
IPv4 nodes as IPv6 addresses. The format of the "IPv4-mapped IPv6
address ...
... 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 is routed to the
...
... interface, thus turning
it into an anycast address, the nodes to which the address is
assigned must be explicitly configured to know that it is an anycast
address ...
... Router anycast address is intended to be used for
applications where a node needs to communicate with any one of the
set of routers.
...
... group of interfaces
(typically on different nodes). An interface may belong to any
number of multicast groups ...
... Interface-Local scope spans only a single interface on a node
and is useful only for loopback transmission of multicast ...
... multicast address.
Nodes must not originate a packet to a multicast address whose scop
field contains the reserved value 0; if such a packet is received, it
...
... multicast address whose scop
field contains the reserved value 0; if such a packet is received, it
must be silently dropped. Nodes should not originate a packet to a
multicast address whose scop field contains the reserved value F; if
...
... The above multicast addresses identify the group of all IPv6 nodes,
within scope 1 (interface-local) or 2 (link-local ...
... Address: FF02:0:0:0:0:1:FFXX:XXXX
Solicited-Node multicast address are computed as a function of a
node ...
... Node multicast address are computed as a function of a
node's unicast and anycast addresses. A Solicited-Node ...
... node's unicast and anycast addresses. A Solicited-Node multicast
address is formed by taking the low-order 24 bits of an address ...
... FF02:0:0:0:0:1:FFFF:FFFF
For example, the Solicited-Node multicast address corresponding to
the IPv6 address ...
... prefixes associated with different aggregations)
will map to the same Solicited-Node address, thereby reducing the
number of multicast addresses ...
... join (on the appropriate interface)
the associated Solicited-Node multicast addresses for all unicast and
...
... unicast and
anycast addresses that have been configured for the node's interfaces
(manually or automatically).
...
... Unicast and Anycast addresses that have been
configured for the node's interfaces (manually or
automatically).
...
... multicast addresses defined in Section 2.7.1.
o The Solicited-Node multicast address for each of its unicast and
...
...
Depending on the characteristics of a specific link or node, there
are a number of approaches for creating Modified EUI-64 format
...
... 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.
...
... 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:
...
... interface identifier from another
interface or one that is assigned to the node itself. When using
this approach, no other interface connecting the same node ...
... node itself. When using
this approach, no other interface connecting the same node to the
same subnet prefix may use the same identifier ...
... prefix-unique interface identifier should be generated in
a manner such that it does not change after a reboot of a node or if
interfaces are added or deleted ...
... appeal. Changes include the following:
- Added clarification to Section 2.5 that nodes should make no
assumptions about the structure of an IPv6 address.
...
... bit set to one (1) as universal.
- Added clarification to Section 2.5.1 that IPv6 nodes are not
required to validate that interface identifiers ...