ddressing or IPv4 routers. 7) Do not change the existing gateway selection procedures and logic. It must still be possible to select a PGW from a visited or a home network, and whether a Serving Gateway (SGW) is collocated with the PGW must not affect the solution. 8) Realize local breakout functionality using a single bearer without a Network Address Translation (NAT). 9) Multiple address functionality should not increase the number of EPS Bearers and should be conservative on additional signaling. Evolved Bearer Link Model The evolved bearer 'single pipe' has several 'leaking points', next-hop routers, and topological areas. Each next-hop router can contribute with its own IPv6 resources and breakout traffic sent directly to it. Even if all the routers are on the same evolved bearer link, they do not really see or reach each other. Link scoped multicast traffic is a good Deploying IPv6 in 3GPP Networks example. There will always be a 'default' PDN Connection and bearer between the UE and the PGW, and this connection also provides network based mobility for the addresses anchored to it. The rest of the 'leaking points' attach to the activated evolved bearer if they SO wish. As stated earlier, the new evolved bearer mimics the NBMA link model for IPv6 [12]. Therefore, only unicast packet delivery at lower layers is supported, although all nodes consisting of the UE and the routers are on the same logical link. The UE learns the presence of all routers through normal IPv6 Neighbor Discovery Protocol means, and the routers on the link know the only end host on the link based on the bearer setup signaling. Obviously, there has to be means at the lower layers - namely at the Non-Access Stratum (NAS) protocol layer - to differentiate between nodes. Therefore, there is a need for link- layer addressing or an equivalent concept. Link-layer addressing is currently absent from 3GPP links. The link-layer address or its equivalent concept is needed for intermediate routers on the evolved bearer link to efficiently detect wh