3.2. Network part, also known as prefix
Designers defined some address types and left a lot of scope for future definitions as currently unknown requirements arise. RFC 2373 [July 1998] / IP Version 6 Addressing Architecture defines the current addressing scheme but there is already a new draft available: draft-ietf-ipngwg-addr-arch-*.txt.
Now lets take a look at the different types of prefixes (and therefore address types):
3.2.1. Link local address type
These are special addresses which will only be valid on a link of an interface. Using this address as destination the packet would never pass through a router. It's used for link communications such as:
They begin with ( where "x" is any hex character, normally "0")
fe8x: <- currently the only one in use.
An address with this prefix is found on each IPv6-enabled interface after stateless auto-configuration (which is normally always the case).
3.2.2. Site local address type
These are addresses similar to the RFC 1918 / Address Allocation for Private Internets in IPv4 today, with the added advantage that everyone who use this address type has the capability to use the given 16 bits for a maximum number of 65536 subnets. Comparable with the 10.0.0.0/8 in IPv4 today.
Another advantage: because it's possible to assign more than one address to an interface with IPv6, you can also assign such a site local address in addition to a global one.
It begins with:
fecx: <- most commonly used.
(where "x" is any hex character, normally "0")
Note that there are discussions going on in deprecating this kind of addresses because there are several issues. Read the current draft for more: draft-ietf-ipv6-deprecate-site-local-XY.txt.
For test in labs, such addresses are still a good choice in my humble opinion.
3.2.3. Global address type "(Aggregatable) global unicast"
Today, there is one global address type defined (the first design, called "provider based," was thrown away some years ago RFC 1884 / IP Version 6 Addressing Architecture [obsolete], you will find some remains in older Linux kernel sources).
It begins with (x are hex characters)
Note: the prefix "aggregatable" is thrown away in current drafts.
There are some further subtypes defined, see below:
184.108.40.206. 6bone test addresses
These were the first global addresses which were defined and in use. They all start with
A special 6bone test address which will be never be globally unique begins with
and is mostly shown in examples, because if real addresses are shown, its possible for someone to do a copy & paste to their configuration files. Thus inadvertently causing duplicates on a globally unique address. This would cause serious problems for the original host (e.g. getting answer packets for request that were never sent).
You can still apply for one of these prefixes, see here How to join 6bone. Also some tunnel brokers still distribute 6bone test address prefixes.
220.127.116.11. Assigned by provider for hierarchical routing
These addresses are delegated to Internet service providers (ISP) and begin with
Prefixes to major (backbone owning) ISPs (also known as LIRs) are delegated by local registries and currently they got a prefix with length 32 assigned.
Any ISP customer can get a prefix with length 48.
18.104.22.168. Addresses reserved for examples and documentation
Currently, two address ranges are reserved for examples and documentation:
These address ranges should be filtered based on source addresses and should NOT be routed on border routers to the internet, if possible.
3.2.4. Multicast addresses
Multicast addresses are used for related services.
They alway start with (xx is the scope value)
They are split into scopes and types:
22.214.171.124. Multicast scopes
Multicast scope is a parameter to specify the maximum distance a multicast packet can travel from the sending entity.
Currently, the following regions (scopes) are defined:
ffx1: node-local, packets never leave the node.
ffx2: link-local, packets are never forwarded by routers, so they never leave the specified link.
ffx5: site-local, packets never leave the site.
ffx8: organization-local, packets never leave the organization (not so easy to implement, must be covered by routing protocol).
ffxe: global scope.
others are reserved
126.96.36.199. Multicast types
There are many types already defined/reserved (see RFC 2373 / IP Version 6 Addressing Architecture for details). Some examples are:
All Nodes Address: ID = 1h, addresses all hosts on the local node (ff01:0:0:0:0:0:0:1) or the connected link (ff02:0:0:0:0:0:0:1).
All Routers Address: ID = 2h, addresses all routers on the local node (ff01:0:0:0:0:0:0:2), on the connected link (ff02:0:0:0:0:0:0:2), or on the local site (ff05:0:0:0:0:0:0:2)
188.8.131.52. Solicited node link-local multicast address
Special multicast address used as destination address in neighborhood discovery, because unlike in IPv4, ARP no longer exists in IPv6.
An example of this address looks like
Used prefix shows that this is a link-local multicast address. The suffix is generated from the destination address. In this example, a packet should be sent to address "fe80::1234", but the network stack doesn't know the current layer 2 MAC address. It replaces the upper 104 bits with "ff02:0:0:0:0:1:ff00::/104" and leaves the lower 24 bits untouched. This address is now used `on-link' to find the corresponding node which has to send a reply containing its layer 2 MAC address.
3.2.5. Anycast addresses
Anycast addresses are special addresses and are used to cover things like nearest DNS server, nearest DHCP server, or similar dynamic groups. Addresses are taken out of the unicast address space (aggregatable global or site-local at the moment). The anycast mechanism (client view) will be handled by dynamic routing protocols.
Note: Anycast addresses cannot be used as source addresses, they are only used as destination addresses.
184.108.40.206. Subnet-router anycast address
A simple example for an anycast address is the subnet-router anycast address. Assuming that a node has the following global assigned IPv6 address:
3ffe:ffff:100:f101:210:a4ff:fee3:9566/64 <- Node's address
The subnet-router anycast address will be created blanking the suffix (least significant 64 bits) completely:
3ffe:ffff:100:f101::/64 <- subnet-router anycast address