g solutions are part of the 'normal' IPv6 routing, address selection (see Section 3.5.4), and next-hop selection (see Section 3.4.6) procedures with minimal administrative overheads. With working Internet connectivity to specific operator services, independent of the used access network, it is possible to view the IPv6 traffic offloading solutions as ordinary IPv6 suite components that virtually all IPv6 implemen- tations have to support, and for which no access technology specific enhancements are needed. 6.1.3 IP-friendly Offloading Solutions We have experimented with three IP-friendly approaches to achieving an IP traffic offloading solution for multiple interfaced UEs with network side control for the offloading policies. The first approach builds on the top of DHCPv6. The second approach builds on top of IPv6 Neighbor Discovery Protocol (NDP), and the third approach extends the second solution with IPv4 capabilities. The IP-friendly solutions try to conform to a 'pure IP' view and have specifically designed Split-UEs in mind. None of the solutions aim at guaranteeing that the offloading policy provided by the network would work in all possible cases. More important is that the UE always has Internet connectivity, meaning that none of the used access networks should be a walled garden. The three solutions have several aspects in common: They rely on IPv6 features when possible. No 3GPP-specific extensions are required. They primarily target UEs with cellular 3GPP access. A GGSN or a PGW is used as the policy coordinator in the operator network. Cellular 3GPP radio is considered a trusted access and hence used to deliver offloading policies. When the 3GPP access is not available there is obviously nothing to offload either. They are designed to benefit from multiple interfaces. The offloading policies are typically in the form of offload everything except a few selected destination networks. Deploying IPv6 in 3GPP Networks DHCPv6 server A Route rules Service 1 WLAN live network Internet 3GPP live network Route