Discovery Protocol for generic host configuration. We believe that the final deployed IP traffic offloading solution will likely be a mixture of existing technologies standardized in 3GPP, in IETF, and what modern IP stacks can do. It is unlikely that mainstream operating systems' IP stack would implement 3GPP specific technologies - some third-party dialer software may then add those missing elements. For the future, however, we believe that it would be useful to do further research on how Deploying IPv6 in 3GPP Networks dedicated routing protocols could be adapted to provide routing information for the end nodes. Use of routing protocols might provide more scalable architecture, perhaps even providing improved multi-interfacing properties for the end nodes. 6.2 Evolving 3GPP Bearers to Multiple Prefixes and Next-hop Routers 6.2.1 Background and Motivation The 3GPP Evolved Packet System (EPS) [1] Bearer and connectivity model from the IP point of view has remained unchanged practically since the birth of GPRS. The connec- tivity model boils down to a handful of technical and architectural assumptions, which have remained untouched for reasons such as thinking that what 3GPP created is some- thing unique to the cellular access, and from a fear of threatening the established service models. For instance, to add a new IP address or IPv6 prefix, an additional connection between the UE and the network has to be created instead of just adding IP addresses to an existing interface. This essentially turns the UE into a multi-interfaced host. In 3GPP architecture a gateway node, a PGW, provides access to an external PDN. The gateway node is located in the mobile operator core network (home or visited) and anchors the UE and its connection both mobility and IP topology-wise. The 3GPP's connectivity model worked fine as long as IPv4 was the only realistic IP version and UEs were traditional phones (see Section 2.6.1). The phones had a single radio access technology, a limited openness to the IP stack for applications and a