nchored prefix is guaranteed to remain the same. The evolved bearer still builds on top of the existing EPS Bearer but only for the part that concerns the default bearer. Therefore, following details need to be understood: The evolved bearer supports PDN Types IPv6 and IPv4v6, but not IPv4. The evolved bearer fate-shares the default EPS Bearer. When the default bearer is activated, the eNodeB and SGW 'routers' along with their respective setup procedures, depending on operator's configuration, may activate and start advertising their presence Deploying IPv6 in 3GPP Networks and prefixes on the link. Also, when the default bearer gets deleted, anything related to the eNodeB and SGW routers and their addressing is deleted as well. There is no dedicated bearer concept for differentiated QoS handling for the evolved bearer, except for the bearer that concerns the PGW terminated/breakout traffic. That part remains unmodified from the EPS Bearer. IPv4 addressing is still possible but only for the PGW terminated traffic and when the PDN Type IPv4v6 is used. Neither eNodeB nor SGW terminated/breakout traffic have support for native IPv4. The evolved bearer inherits the 3GPP PDN Connection assumptions on how IPv6 addresses are configured [15, 16]. That means that the SLAAC [17] is the only way to configure an address and a single Prefix Information Option (PIO) [18] can be present in a Router Advertisement received from a router. The advertised /64 IPv6 prefix always has the 'L'-flag set to zero in a PIO. The lifetimes in Router Advertisement Prefix Information Options (PIOs) originated by the eNodeB and SGW do not need to be set to infinity, because both of those termina- tion/breakout points may be under different management from the PGW. The eNodeB part of the evolved bearer is the most independent, and changes in there can be implemented without impacting the rest of the 3GPP system. Multicast Considerations Although the evolved bearer is modeled as an NBMA resembling link, we need to define how multicast works over i