nhancements are out of the scope of Homenet. Borrowing the IETF working group charter, topics that will be addressed include: (Automated) prefix configuration for routers; the configuration concerns the home network internal routers as well as the customer edge router [33]. There are multi- ple approaches based on prefix delegation and DHCPv6 [34, 35], possibly extending IPv6 NDP, or routing protocols [36]. Managing routing; when there are multiple subnets, the home network internal routing has to be accomplished somehow [37]. It is not possible to rely on just default routes all the time. Name resolution; how can we discover name servers and get that provisioned to every host within the home work, naming internal nodes, and how can we manage possible naming delegation and reverse zones [38, 39]? Service discovery; there are ways to discover network services on a link scope but how can we extend that to multiple subnets and non-trivial topologies [40]? Network security; there needs to be at least minimum level of built-in security properties in a home network [41]. Also it may not be trivial to dynamically discover 'security boundaries' within the home network. It has been envisioned that future IPv6 enabled residential home networks are not topologically trivial, and the services that people would like to deploy intentionally or unintentionally on those actually lean towards properly segmented networks with all the complexity that it brings. Current IPv4 and often NAT-based home networks tend to work out of box, even when there are nested NAT devices in the network (but obviously these networks suffer from the connectivity limitations caused by translation, such as limited visibility between network segments). IPv6 is still a relatively young technology, especially when it comes to 'clueless' consumers and their home networks with all their variety of (badly behaving) networking devices. And all has to work just fine with zero configuration from the consumer point of view. There is still some work to do. The fir