Outsourcing Home Network Authoritative Naming Service
draft-mglt-homenet-front-end-naming-delegation-04

 
Document
Type Replaced Internet-Draft (homenet WG)
Last updated 2014-09-03 (latest revision 2014-07-04)
Replaced by draft-ietf-homenet-front-end-naming-delegation
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html
Stream
WG state Adopted by a WG
Document shepherd No shepherd assigned
IESG
IESG state Replaced by draft-ietf-homenet-front-end-naming-delegation
Telechat date
Responsible AD (None)
Send notices to (None)

Email authors IPR References Referenced by Nits Search lists

This Internet-Draft is no longer active. A copy of the expired Internet-Draft can be found at
https://www.ietf.org/archive/id/draft-mglt-homenet-front-end-naming-delegation-04.txt

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 results 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 associates 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.

Authors

Daniel Migault (daniel.migault@orange.com)
Wouter Cloetens (wouter.cloetens@softathome.com)
Chris Griffiths (cgriffiths@dyn.com)
Ralf Weber (ralf.weber@nominum.com)

(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)