%% You should probably cite rfc9526 instead of this I-D. @techreport{ietf-homenet-front-end-naming-delegation-02, number = {draft-ietf-homenet-front-end-naming-delegation-02}, type = {Internet-Draft}, institution = {Internet Engineering Task Force}, publisher = {Internet Engineering Task Force}, note = {Work in Progress}, url = {https://datatracker.ietf.org/doc/draft-ietf-homenet-front-end-naming-delegation/02/}, author = {Daniel Migault and Wouter Cloetens and Chris Griffiths and Ralf Weber}, title = {{Outsourcing Home Network Authoritative Naming Service}}, pagetotal = 33, year = 2015, month = may, day = 4, abstract = {CPEs are designed to provide IP connectivity to home networks. Most CPEs assign IP addresses to the nodes of the home network which makes it a good candidate for hosting the naming service. With IPv6, the naming service makes nodes reachable from the home network as well as from the Internet. However, CPEs have not been designed to host such a naming service exposed on the Internet. This may expose the CPEs to resource exhaustion which would make the home network unreachable, and most probably would also affect the home network inner communications. In addition, DNSSEC management and configuration may not be well understood or mastered by regular end users. Misconfiguration may also result in naming service disruption, thus these end users may prefer to rely on third party naming providers. This document describes a homenet naming architecture where the CPEs manage the DNS zone associated to its home network, and outsources the naming service and eventually the DNSSEC management on the Internet to a third party designated as the Public Authoritative Servers.}, }