Unique local address

In December 1995, the IPv6 address block fec0::/10 was reserved for site-local addresses,[2] that could be used within a "site" for private IPv6 networks. However, insufficient definition of the term site led to confusion over the governing routing rules.

In September 2004, the Internet Engineering Task Force (IETF) deprecated the definition of this address range,[3] and postulated solutions to its problems. The special behaviour for this type of addresses as required at that time[4] was lifted in 2006 and the block returned to regular global unicast.[5]

In October 2005, the IETF reserved the address block fc00::/7 for use in private IPv6 networks and defined the associated term unique local addresses.[1]

Unique local addresses use prefix fc00::/7, extended with an 'L' bit which indicates that the address is locally assigned. This splits the address block in two equally sized halves, fc00::/8 and fd00::/8.

The prefix field contains the binary value 1111110. The L bit is one for locally assigned addresses; the address range with L set to zero is currently not defined. The random field is chosen randomly once, at the inception of the /48 routing prefix.

The block with L = 0, fc00::/8 is currently not defined.[lower-alpha 1] It has been proposed that an allocation authority manage it, but this has not gained acceptance in the IETF.[6][7][8]

The block with L = 1, or locally assigned addresses, fd00::/8 is divided into /48 prefixes, formed by setting the forty bits following the prefix fd00/8 to a randomly generated bit string. This results in the format fdxx:xxxx:xxxx::/48 for a prefix in this range. RFC 4193 offers a suggestion for generating the random identifier to obtain a minimum-quality result if the user does not have access to a good source of random numbers.

Prefixes in the range fd00::/8 have similar characteristics as those of the IPv4 private address ranges: They are not allocated by an address registry and may be used in networks by anyone without outside involvement. They are not guaranteed to be globally unique. Reverse Domain Name System (DNS) entries (in ip6.arpa) for fd00::/8 ULAs cannot be delegated in the global DNS.

As fd00::/8 ULAs are not meant to be routed outside their administrative domain (site or organization), administrators of interconnecting networks normally do not need to worry about the uniqueness of ULA prefixes. However, if networks require routing ULAs between each other in the event of a merger, for example, the risk of address collision is small if the RFC 4193 selection algorithm was used.

SixXS attempted to maintain a voluntary registration database for fd00::/8 ULA prefixes to reduce the risk of different organisations using identical prefixes.[9] When the SixXS services were discontinued on 6 June 2017, the database became read-only.

On 6 December 2020, the Swiss based company 'ungleich' announced to revive the IPv6 ULA registry based on the original SixXS database, citing user demands for a ULA registry.[10]

For the range fc00::/8, different design decisions have been proposed and submitted to the IETF,[6][8] trading the risk of non-uniqueness for the requirement that the range be managed by a central allocation authority. However, such attempts at standardizing this range have not resulted in a Request for Comments.[6][7][8]

• Link-local address

• Stockebrand, Benedikt (2006). IPv6 in Practice. ISBN 978-3-540-24524-7.
• "Public ULA registration database". SixXS. (readonly since SixXS sunset, 6 June 2017)
• "ULA draft proposal" (PDF). ARIN. 2004. Archived from the original (PDF) on 2008-12-05.
• Internet Draft "Considerations For Using Unique Local Addresses". IETF. 2017.