IPv4 supports four different classes of addresses, which are Anycast, Broadcast, Multicast, and Unicast. While the term Anycast has not been used in previous chapters in this guide, it is important to remember that Anycast addresses are not special types of addresses. Instead, an Anycast address is simply an IP address that is assigned to multiple interfaces. Common examples of technologies that use Anycast addressing include IP Multicast implementations, and 6to4 relay implementation.

NOTE: 6to4 is a transition mechanism for migrating from IPv4 to IPv6. 6to4 will be described in detail later in this chapter.

With Anycast addressing, devices use the common address that is closest to them based on the routing protocol metric. The next closest address is then used in the event that the primary address is no longer reachable. This concept is illustrated in the below fig.

Referencing the above fig, both R1 and R2 have a Loopback 254 interface that is configured using a common address: 15.1.1.254/32. This prefix is then advertised dynamically via EIGRP. By default, both R1 and R2 will prefer the 15.1.1.254/32 prefix via their respective Loopback interfaces as that is a directly connected subnet. Therefore, the common address used will never result in a conflict on either router.

Assuming normal EIGRP metric calculation, routers R3 and R5 will prefer the Anycast address advertised by router R1 due to the lower IGP metric. Similarly, R4 and R6 will prefer the Anycast address advertised by router R2 due to the lower IGP metric. In the event that either router R1 or R2 fails, the remaining routers in the network will use the Anycast address advertised by the remaining router. When using Anycast addressing, organizations can either use a Unicast address in RFC 1918 address space or within their public block.

NOTE: You are not expected to implement any Anycast addressing or solutions in the current ROUTE exam. However, it is important to be familiar with the concept.

At this level, IPv4 Broadcast, Multicast, and Unicast addresses require no further explanation and will not be described in any additional detail in this chapter or in the remainder of this guide. While IPv4 supports these four different types of addresses, IPv6 does away with the Broadcast addresses and instead only supports the following types of addresses:

• Link-Local Addresses
• Site-Local Addresses
• Aggregate Global Unicast Addresses
• Multicast Addresses
• Anycast Addresses
• Loopback Addresses
• Unspecified Addresses

Link-Local Addresses

IPv6 Link-Local can only be used on the local link, i.e. a shared segment between devices, and are automatically assigned to each interface when IPv6 is enabled on that interface.  These addresses are assigned from the Link-Local prefix FE80::/10. Keep in mind that FE80::/10 is the equivalent of FE80:0:0:0:0:0:0:0/10, which can also be represented as FE80:0000:0000:0000:0000:0000:0000:0000/10. To complete the address, bits 11 through 64 are set to 0 and the interface Extended Unique Identifier 64 (EUI-64) is appended to the Link Local address as the low-order 64 bits. The EUI-64 is comprised of the 24-bit manufacturer ID assigned by the IEEE and the 40-bit value assigned by that manufacturer to its products. EUI-64 addressing is described in greater detail later in this chapter when we learn about configuring IPv6 addresses. This format of a Link Local address is illustrated in the below fig.

Link-Local addresses are unique in that they do not change once assigned to an interface. This means that if an interface is assigned both a public IPv6 address (e.g. 2001:1000::1/64) if that public IPv6 prefix was changed (i.e. 2001:2000::1/64) the Link Local address would not change. This allows the host or router to remain reachable while global IPv6 Internet addresses change.

Site-Local Addresses

Site-Local addresses are Unicast addresses that are used only within a site. Unlike Link-Local addresses, Site-Local address must be manually configured on network devices. These addresses are the IPv6 equivalent of the private IPv4 address space defined in RFC 1918 and can be used by organizations that do not have globally routable IPv6 address space. These addresses are not routable on the IPv6 Internet.

While it is possible to perform NAT for IPv6, it is not recommended; hence the reason for the much larger IPv6 addresses. Site-Local addresses are comprised of the FEC0::/10 prefix, a 54-bit Subnet ID and an interface identifier in the EUI-64 format used by Link-Local addresses. While the 54-bits in a Link-Local address are set to a value of 0, the same 54-bits in Site-Local addresses are used to create different IPv6 prefixes (up to 254). The format of the Site-Local address is illustrated in the below fig:

NOTE: Because IPv6 devices can be assigned multiple addresses, it is important to know that Site-Local addresses can be assigned to a router interface (for example) in conjunction with globally routable IPv6 Internet addresses.

Aggregate Global Unicast Addresses

Aggregate Global Unicast Addresses are the IPv6 addresses used for generic IPv6 traffic as well as for the IPv6 Internet. These are similar to the public addresses used in IPv4.  From a network addressing point of view, each IPv6 Global Unicast Address is comprised of three main sections: the prefix received from the provider (48-bit in length), the site prefix (16-bit in length) and the host portion (64-bit in length). This makes the 128-bit address used in IPv6.

As we learned earlier in this chapter, the provider assigned prefix is assigned to an organization by an IPv6 provider. By default, these prefixes use /48 prefix lengths. In addition to this, these prefixes are assigned from the IPv6 address space (i.e. the /32 prefix lengths) that are owned by the provider. Each provider will own its own IPv6 address space and the IPv6 prefix assigned by one provider cannot be used on the network of another provider.

Within a site, administrators can then subnet the provider assigned 48-bit prefix into 64-bit site prefixes, by using bits 49-64 for subnetting, allowing for 65,535 different subnets for use within their network. The host portion of an IPv6 address represents the network device or host on the IPv6 subnet. This is represented by the low-order 64-bits of the IPv6 address.

Aggregate Global Unicast Addresses for IPv6 are assigned by the Internet Assigned Numbers Authority (IANA) and fall within the IPv6 prefix 2000::/3. This allows for a range of Aggregate Global Unicast Addresses from 2000 to 3FFF as is shown in Table 8-4:

NOTE: The 6to4 transition addresses and the 6bone prefix are described later in this guide.

Within the range of IPv6 Global Aggregate Unicast addresses, a special experimental range is reserved. This range is the ORCHID address range. ORCHID Addresses are non-routed IPv6 addresses used for Cryptographic Hash Identifiers. These addresses use the IPv6 prefix 2001:10::/28. ORCHID is an acronym for Overlay Routable Cryptographic Hash Identifiers, and is defined in RFC 4843. Going into detail on ORCHID addresses is beyond the scope of the current ROUTE exam and will not be included in this chapter or the remainder of this guide.

Multicast Addresses

The Multicast addresses used in IPv6 are derived from the FF00::/8 IPv6 prefix. In IP version 6, Multicast operates in a different manner than that of Multicast in IPv4. IP Multicast is used extensively in IPv6 and replaces IPv4 protocols such as the Address Resolution Protocol (ARP). In addition to this, Multicast is used in IPv6 for prefix advertisements and renumbering, as well as for Duplicate Address Detection (DAD). These concepts are all described later in this chapter.

Multicast packets in IPv6 do not use the TTL value to restrict such packets to the local network segment. Instead, the scoping is defined within the Multicast address itself via the use of the Scope field. IPv6 nodes on a network segment listen to Multicast and may even send Multicast packets to exchange information. This allows all nodes on an IPv6 segment to know about all other neighbors on that same segment. The format of Multicast addresses used in IPv6 networks is illustrated in the fig below:

As illustrated in the above, the format of the IPv6 Multicast address is slightly different from the formats of the other IPv6 addresses we have learned about up until this point.  The first 8 bits of the IPv6 Multicast address represent the Multicast prefix FF::/8. The Flag field in the IPv6 Multicast address is used to indicate the type of Multicast address. There are two defined types of IPv6 Multicast address: permanent and temporary.

Permanent IPv6 Multicast addresses are assigned by IANA while the temporary IPv6 Multicast addresses can be used in pre-deployment Multicast testing.  The Flag field may contain one of two possible values, as illustrated and described in the Table below:

Because IPv6 does not use ARP, Solicited-Node Multicast Addresses are used by network hosts and routers to learn the Data Link addresses of neighboring devices. This allows for the conversion and sending of IPv6 packets to IPv6 hosts and routers as frames. Duplicate Address Detection (DAD) is a part of the IPv6 Neighbor Discovery Protocol, which is described in detail later in this chapter. DAD simply allows a device to validate whether or not an IPv6 address is already in use on the local segment before it configures the address as its own using Autoconfiguration. In essence, it provides a similar function to Gratuitous ARP used in IPv4. Solicited-Node Multicast Addresses are defined by the IPv6 prefix FF02::1:FF00:0000/104. These addresses are comprised of the FF02::1:FF00:0000/104 prefix in conjunction with the low-order 24-bits of the Unicast or Anycast address.  The fig below shows the format of these IPv6 addresses:

In a manner similar to IPv4 Multicast mapping for Ethernet, IPv6 also uses a unique means to map Layer 3 IPv6 Multicast addresses to Layer 2 Multicast addresses. Multicast mapping in IPv6 is enabled by appending the low-order 32-bit of a Multicast address to the 16-bit prefix 33:33, which is the defined Multicast Ethernet prefix for IPv6 networks. This is illustrated in Figure 8-11 for the all routers on the Interface-Local scope prefix FF01::2:

NOTE: While IPv6 Multicast addresses have been included in this chapter, keep in mind that you are not required to implement any Multicast solutions in the current ROUTE exam. In fact, IP Multicast, for both IPv4 and IPv6, is excluded from the scope of the current ROUTE exam.

Anycast Addresses

Anycast, which was described earlier in this section, can be described simply as one-to-nearest communication because the nearest common address, based on routing protocol metrics, will always be preferred by the local device. In IPv6, Anycast addresses use Global Unicast, Site-Local or even Link-Local addresses. However, there is an Anycast address reserved for special use. This special address is referred to as the Subnet-Router Anycast Address. The Subnet-Router Anycast Address is formed with the subnets 64-bit Unicast prefix, with the remaining 64 bits set to zero, for example: 2001:1a2b:1111:d7e5:0000:0000:000:0000. These addresses are typically used by protocols such as Mobile IPv6, which was described earlier in this chapter.

Loopback Addresses

Loopback addresses used in IPv6 are used in the same manner as in IPv4. Each device has one IPv6 Loopback address, which is comparable to the 127.0.0.1 Loopback address used in IPv4, and this address is used by the device itself. IPv6 Loopback addresses use the prefix ::1, which can be represented as 0000:0000:0000:0000:0000:0000:0000:0001 in the preferred address format. This means that in Loopback addresses, all bits are set to 0 except for the last bit which is always set to 1. These addresses are always automatically assigned when IPv6 is enabled on a device and can never be changed.

Unspecified Addresses

In IPv6 addressing, unspecified addresses are simply Unicast addresses that are not assigned to any interface. These addresses indicate the absence of an IPv6 address and are used for special purposes that include IPv6 DHCP and DAD. Unspecified addresses are represented by all 0 values in the IPv6 address and can be written using the :: prefix. In the preferred format, these addresses are represented as 0000:0000:0000:0000:0000:0000:0000:0000.