ich traffic is destined to them without actively inspecting the traffic content at the IP layer. The evolved bearer hooks into the Packet Data Convergence Protocol (PDCP) [13], which operates between the UE and the evolved Node B (eNodeB). There are still several unused PDCP Protocol Data Unit (PDU) type codes that can be utilized. We could reserve two or three more types for the evolved bearer purposes, that is one type for the eNodeB terminated/breakout traffic and one for the SGW terminated/breakout traffic. The PGW terminated traffic could use existing PDCP PDU type numbers. This approach would be conservative on the Radio Access Bearer (RAB) level, since no new bearer is needed for new addresses or eNodeB/SGW terminated traffic. We would still need one additional S1-U to represent the SGW terminated/breakout traffic. This could be a fair compromise to RAB consumption and also reduce the overall signaling. The eNodeB can do the traffic differentiation for local consumption or for forwarding to bearers heading to PGWs and SGWs without an IP lookup. The issue of link-layer addressing, or rather the lack of it, still remains. Having a proper link-layer addressing makes the integration of IPv6 simpler from the UE IP stack point of view, since IPv6 was designed to work best over multicast enabled links with link-layer addresses. A straightforward solution would be mapping either PDCP PDU type codes (for data packets) to link-layer addresses or agree on a common link-layer addressing scheme for a UE, eNodeB, SGW, and PGW. The link-layer addressing does not mean that the address would be a real physical layer-2 address of each node on the evolved bearer link. The purpose is to allow easier mapping of IP flows and IPv6 prefixes to the proper PDCP PDU types and radio level constructs, thus the link-layer is merely a conceptual construct with known name space where the address implicitly contains the information of the network node where the traffic is to be terminated. Table 6.1 shows what the link- layer address mapp