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
Bit
Click on the red underlined text to get to the source
...
1. The preferred form is x:x:x:x:x:x:x:x, where the 'x's are one to
four hexadecimal digits of the eight 16-bit pieces of the address.
Examples:
...
... IPv6
addresses, it will be common for addresses to contain long strings
of zero bits. In order to make writing addresses containing zero
bits ...
... bits. In order to make writing addresses containing zero
bits easier, a special syntax is available to compress the zeros.
The use of "::" indicates one or more groups of 16 bits ...
... bits easier, a special syntax is available to compress the zeros.
The use of "::" indicates one or more groups of 16 bits of zeros.
The "::" can only appear once in an address. The "::" can also be
...
... 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 pieces of the address, and the 'd's are
...
... address, and the 'd's are
the decimal values of the four low-order 8-bit pieces of the
address (standard IPv4 ...
... prefix-length is a decimal value specifying how many of the
leftmost contiguous bits of the address comprise
the prefix ...
... prefix.
For example, the following are legal representations of the 60-bit
prefix 20010DB80000CD3 (hexadecimal):
...
...
2001:0DB8:0:CD3/60 may drop leading zeros, but not trailing
zeros, within any 16-bit chunk of the address
...
...
The type of an IPv6 address is identified by the high-order bits of
the address, as follows:
...
... IPv6 notation Section
------------ ------------- ------------- -------
Unspecified 00...0 (128 bits) ::/128 2.5.2
Loopback 00...1 (128 bits ...
... 128 bits) ::/128 2.5.2
Loopback 00...1 (128 bits) ::1/128 2.5.3
Multicast 11111111 FF00::/8 2.7
...
... unicast addresses are aggregatable with prefixes of arbitrary
bit-length, similar to IPv4 addresses under Classless Inter-Domain
Routing.
...
... structure:
| 128 bits |
+-----------------------------------------------------------------+
| node ...
... n:
| n bits | 128-n bits |
+-------------------------------+---------------------------------+
...
...
| n bits | 128-n bits |
+-------------------------------+---------------------------------+
| subnet prefix ...
... start with the binary
value 000, Interface IDs are required to be 64 bits long and to be
constructed in Modified EUI-64 format.
...
... EUI-64 format interface identifiers are formed by inverting
the "u" bit (universal/local bit in IEEE EUI-64 ...
... interface identifiers are formed by inverting
the "u" bit (universal/local bit in IEEE EUI-64 terminology) when
...
... identifiers. In
the resulting Modified EUI-64 format, the "u" bit is set to one (1)
to indicate universal scope, and it is set to zero (0) to indicate
...
...
written in Internet standard bit-order, where "u" is the
universal/local bit, "g" is the individual/group ...
... Internet standard bit-order, where "u" is the
universal/local bit, "g" is the individual/group bit, and "c" is the
...
... group bit, and "c" is the
bits of the company_id. Appendix A, "Creating Modified EUI-64 Format
...
... interface identifiers.
The motivation for inverting the "u" bit when forming an interface
identifier is to make it easy for system administrators to hand
...
...
| n bits | m bits | 128-n-m bits |
+------------------------+-----------+----------------------------+
...
... | n bits | m bits | 128-n-m bits |
+------------------------+-----------+----------------------------+
| global routing ...
... addresses other than those that 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 starting with a binary value
other than 000 (and therefore having a 64-bit interface ID field) can
be found in [GLOBAL ...
... IPv6 addresses are defined that carry an IPv4 address in
the low-order 32 bits of the address. These are the "IPv4-Compatible
...
... follows:
| 80 bits | 16 | 32 bits |
+--------------------------------------+--------------------------+
...
...
| 80 bits | 16 | 32 bits |
+--------------------------------------+--------------------------+
|0000..............................0000|0000| IPv4 address ...
... IPv6
address" is as follows:
| 80 bits | 16 | 32 bits |
+--------------------------------------+--------------------------+
...
...
| 80 bits | 16 | 32 bits |
+--------------------------------------+--------------------------+
|0000..............................0000|FFFF| IPv4 address ...
... | 10 |
| bits | 54 bits | 64 bits |
+----------+-------------------------+----------------------------+
...
... | bits | 54 bits | 64 bits |
+----------+-------------------------+----------------------------+
|1111111010| 0 | interface ID ...
... | 10 |
| bits | 54 bits | 64 bits |
+----------+-------------------------+----------------------------+
...
... | bits | 54 bits | 64 bits |
+----------+-------------------------+----------------------------+
|1111111011| subnet ...
... follows:
| n bits | 128-n bits |
+------------------------------------------------+----------------+
...
...
| n bits | 128-n bits |
+------------------------------------------------+----------------+
| subnet prefix ...
... format:
| 8 | 4 | 4 | 112 bits |
+------ -+----+----+---------------------------------------------+
|11111111|flgs|scop| group ...
... RFC3956].
scop is a 4-bit multicast scope value used to limit the scope of
the multicast group ...
... anycast addresses. A Solicited-Node multicast
address is formed by taking the low-order 24 bits of an address
(unicast ...
... (unicast or anycast) and appending those bits to the prefix
FF02:0:0:0:0:1:FF00::/104 resulting in a multicast address ...
... the IPv6 address 4037::01:800:200E:8C6C is FF02::1:FF0E:8C6C. IPv6
addresses that differ only in the high-order bits (e.g., due to
multiple high-order prefixes associated with different aggregations ...
... identifier to an
interface identifier is to invert the "u" (universal/local) bit. An
example is a globally unique IEEE EUI-64 ...
... +----------------+----------------+----------------+----------------+
where "c" is the bits of the assigned company_id, "0" is the value of
the universal/local bit ...
... bits of the assigned company_id, "0" is the value of
the universal/local bit to indicate universal scope, "g" is
individual/group bit ...
... bit to indicate universal scope, "g" is
individual/group bit, and "m" is the bits of the manufacturer-
selected extension identifier ...
... individual/group bit, and "m" is the bits of the manufacturer-
selected extension identifier. The IPv6 interface identifier ...
... +----------------+----------------+----------------+----------------+
The only change is inverting the value of the universal/local bit.
Links ...
... 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 MAC (between the company_id
...
... +----------------+----------------+----------------+
where "c" is the bits of the assigned company_id, "0" is the value of
the universal/local bit ...
... bits of the assigned company_id, "0" is the value of
the universal/local bit to indicate Global scope, "g" is
individual/group bit ...
... bit to indicate Global scope, "g" is
individual/group bit, and "m" is the bits of the manufacturer-
selected extension identifier ...
... individual/group bit, and "m" is the bits of the manufacturer-
selected extension identifier. The interface identifier ...
... identifier is to take the link identifier (e.g., the LocalTalk
8-bit node identifier) and zero fill it to the left. For example, a
LocalTalk 8-bit ...
... 8-bit 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 ...
... +----------------+----------------+----------------+----------------+
Note that this results in the universal/local bit set to "0" to
indicate local scope.
...
... EUI-64 format interface identifiers with the "u"
bit set to one (1) as universal.
- Added clarification to Section 2.5.1 that IPv6 nodes ...
... created in
Modified EUI-64 format with the "u" bit set to one are unique.
o Changed the reference indicated in Section 2.5.4 "Global Unicast ...