here the application set is very limited (for instance temperature or electricity meter reading), or the application is set and operated by the same party. The latter case includes operator services like Internet Protocol Television (IPTV), Voice over IP (VoIP), services provided by IMS or other walled garden services. Restricting the generic Internet access use case to IPv6-only services would, as of now, be too limiting because a major portion of Internet services are still accessible only via IPv4. Although IPv6 transition is moving forward at a steady pace, it will most probably still take a significant time before IPv4 Internet access can be completely removed from a normal user. That said, it is possible to use IPv6-only PDN Connection for a UE as long as the connection to the IPv4 portion of the Internet can be guaranteed. Practically, this means that the UE, including all applications used in it, is IPv6 capable and the network provides translation services between IPv6 and IPv4. The IPv6 to IPv4 translation enables the connectivity to the IPv4 services in the Internet regardless of the IP version that the UE is using. We described a suitable tool for protocol translation, NAT64, in Section 5.3.3. This use case is not very different from the Internet access much of the users get, where the UE gets a private RFC 1918 address, and a NAT44 is used. In an IPv6-only use case, IPv4 applications could also be supported by providing Network Address Translation from IPv4 to IPv6 (NAT46) within the UE. In this case, the UE internal NAT46 would provide an IPv4 address to the applications, and thus create an illusion of IPv4 access. However, as discussed, access to IPv4 services will still be needed for the foreseeable future. Supporting the access to IPv4 services for the IPv4 applications would require double translation. We discuss double translation in the following section. 5.4.4 Double Translation The requirement of the IPv6-only approach to have all applications IPv6 enabled is a tough request. Some operating 