plications, though. The most obvious implication is the additional equipment that is needed. When transla- tion such as NAT64 is used, the NAT64 equipment has to be installed. The dimensioning of the NAT64 infrastructure has to be done carefully. Usually, when a new service or technology is introduced, the amount of data traffic is small at first, and grows over time. With NAT64, at the beginning of the transition, the amount of IPv4 content is high. The data amounts should diminish over time as the transition moves forward. Therefore, the peak capacity of the translation equipment is needed at the beginning, and then the IPv6 Transition Mechanisms for 3GPP Networks need for the capacity falls gradually over time. Obviously, whether the real deployment actually follows this trend depends strongly on the operator. In any case, as the IPv6 transition moves forward and content becomes increasingly available over IPv6, the use of translation will decrease. New equipment has also to be configured and maintained. Therefore, there is a clear new overhead for the operator's operational people. In addition, as we described in Section 5.2.1 how, with a NAT64, a DNS64 has to be set up as well. Where NAT64 can be new a equipment and a new system, DNS64 has to be added to the operator's DNS infrastructure. We described earlier in Section 5.2.1, how modifications made by DNS64 to DNS responses have implications both for protocols like DNSSEC, and also for the UE itself. These are no real implications for the network, but there are for the end user equip- ment. The problem with these implications is that different equipment, and even different software versions, can be differently affected. Therefore, the user experiences can vary. 5.5.5 Transition Support in the Transport Plane We described some of the implications to the transport plane, and thus, to the operator's internal infrastructure network in Section 5.5.2. However, there are also implications for the higher layers - the GTP. For instance, there can be a handover situa