cess network to the second, MAG '2' of the second access network learns from the LMA what is the HNP that should be advertised to the MN. The mobility between accesses can be further divided into two categories: inter-access mobility and intra-access mobility. Inter-access mobility refers to scenarios where the access networks, between which the MN changes, are using different technologies, or are otherwise seen by the MN as different points of network attachment (for example, WLAN networks with different SSIDs). The intra-access mobility refers to scenarios where, from the MN's point of view, the point of network attachment does not change. An example of intra-access mobility is MN changing between WLAN access points while being connected to the same SSID. While the original PMIPv6's idea of providing mobility without any host impacts sounded tempting, the reality proved to be more complex. The PMIPv6 can indeed ensure that the same HNP is available in the new access link that the MN moves to, but while that works for intra-access mobility scenarios, it is unfortunately not enough to provide mobility also for inter-access scenarios. The inter-access scenarios are problematic, Deploying IPv6 in 3GPP Networks because several operating systems are not prepared for such address stability provided by PMIPv6. For example, if the handover between two access networks is done in a break-before-make manner, some operating systems release configured IPv6 addresses at the instant of the first access network being disconnected, and even if the same IPv6 address is configured again a moment later from the second access network, all transport layer sessions have already been terminated and hence seamless mobility is not achieved. In some operating systems, sockets are strictly bound to network interfaces, and hence even if address stability would be maintained, the sockets are unable to switch using the second interface. Furthermore, in the case of make-before-break, many operating systems refuse to configure the same IPv6 add