cups. If the wireless part (the PDN Connection) is provisioned dynamically then the delegated prefixes are also dynamically assigned, which most likely leads to a frequent disturbing renumbering in the home network. This would be unacceptable. Therefore, static PDN Connection address assignment linked to static prefix delegation is more likely to be a requirement when using, for example, LTE connectivity as a cable replacement. According to Section 4.4.5 the static addressing in 3GPP specifications is not entirely a 'done deal' as of now. There is still some work to do, at least in 3GPP. 3GPP Release-10 is still quite ahead of normal mobile operator release cycles, which means that the DHCPv6 Prefix Delegation may take some time before it actually materi- alizes. Of course it is always possible that a specific feature gets cherry picked to earlier software releases. In a meanwhile, it is very possible that the LTE or 3G connections as cable replacements for CPEs are stuck with a single /64 IPv6 prefix and no mobile network side support for DHCPv6 for any parameter configuration. This would make an 'interesting' (read challenging) residential home network deployment scenario, for example, for the following reasons: The 3GPP link model requires the /64 IPv6 prefix to be also configured in the Wide Area Network (WAN) link side of the CPE. There has been related discussion in the context of tethering with 3GPP UEs, where a single /64 IPv6 prefix is used on both sides of a UE [48]. The Neighbor Discovery Proxy [49] is not really usable in the home network side, since loop free topologies cannot be guaranteed. DNS server information comes dynamically from the mobile operator using non-IP technologies where it then needs to be propagated further into the home network. The /64 IPv6 prefix may change every time the cellular WAN link goes down and comes up again. The inadequate numbering resources/possibilities might lead to fallback solutions and promote a deployment of IPv6 NAT, which would be unfortunate at best. 6.3.3 