ees the evolved bearer as one link with one or more routers on it. The PGW router is always present due to default bearer establishment to the PGW. The eNodeB and/or the SGW routers may be active based on the network side configuration. The UE learns about the evolved bearer routers by receiving a Router Advertisement from them, either unsolicited or after sending an Router Solicitation. Each of the Router Advertisements may contain at most one PIO including a prefix for the UE to configure its addresses. The Router Advertisement from the PGW router must contain a PIO with a prefix but the PIOs from other evolved routers may not. At minimum, the UE learns the link-local addresses of the evolved routers and their router preferences. Each evolved bearer router may have its own view of their preference. In a case where the UE received multiple PIOs from different routers on an evolved bearer, the UE can obviously configure multiple addresses on its interface. When the UE has to select a source address for its outgoing traffic, the standard default source address selection as defined by IETF applies [10]. The UE may also have up to three default routers on the evolved bearer. The default router is entirely based on the existing IPv6 rules and practices [18, 9, 19]. In the selection of the Interface IDentifiers (IIDs) the UE can still follow the existing 3GPP specifications. Using the evolved bearer solution, a network operator can easily utilize RFC 4191 [9] router preferences and more specific routes to choose which of the three routers visible to the UE is to be used as the most preferred default router. For instance, the operator can configure an eNodeB to be the high priority default, a SGW to be the mid-priority default, and a PGW to be the low-priority default gateway. This will easily, and using standard IPv6 machinery, tell the UE which route to use for default traffic. There is a certain network deployment issue here. What happens if the UE decides to send traffic to an arbitrary destination via a next-hop r