s agnostic on which protocol would be used to implement the 'Managed address configuration' (see Section 3.4.3), but at least by now, and for the foreseeable future, the DHCPv6 is the managed protocol. The main pull for DHCPv6 technology comes Deploying IPv6 in 3GPP Networks from specific deployments, such as in enterprises, where managed address configuration schemes are commonly preferred by the network administrators. 3.5.1 Stateless Address Autoconfiguration In this section, we introduce the procedure for IPv6 SLAAC, which is the main mechanism for hosts to number themselves [41, 73]. The stateless approach is always required for link-local address configuration, and it is a lighter procedure for global address autoconfiguration than the DHCPv6. The SLAAC essentially has to be supported by all general-purpose IPv6 hosts. Other kinds of nodes, such as routers, special build hosts, or hosts in specific deployment scenarios, may be managed with manual address configuration or with DHCPv6-only. The overall operation of SLAAC is illustrated in Figure 3.15 and briefly described herein before we discuss some of the details in more depth. The figure illustrates how a router is sending unsolicited Router Advertisements before the example's host is attached to a link (first message). Once a host joins a link, it first selects an IID for itself, creates a link-local IPv6 address, and does DAD for it (not shown in the figure). The host sends a Router Solicitation as it proceeds to configure more information for itself (the second message shown), in order to receive Router Advertisement faster and from all routers. Router Solicitation also ensures that received Router Advertisements are complete, as unsolicited Router Advertisements do not have to contain all the information [41]. After the host receives solicited, or unsolicited, Router Advertisement back (the third message shown), it combines the IPv6 prefix received from the Router Advertisement with the IID that the host has chosen. The host needs to perform DAD for t