DHCP DNS Public Authoritative Server Option
draft-mglt-dhc-public-authoritative-server-option-00

Document Type Expired Internet-Draft (individual)
Last updated 2014-01-06 (latest revision 2013-07-05)
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream Stream state (No stream defined)
Consensus Boilerplate Unknown
RFC Editor Note (None)
IESG IESG state Expired
Telechat date
Responsible AD (None)
Send notices to (None)

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-dhc-public-authoritative-server-option-00.txt

Abstract

The home network naming architecture as described in [I-D.mglt-homenet-front-end-naming-delegation] requires a complex naming configuration on the CPE. This configuration MAY not be handled easily by the average end user. Furthermore, such misconfiguration MAY result in making home network unreachable. This document proposes a DHCP option that provides the CPE all necessary parameters to set up the home network naming architecture. First, this DHCP option provides automatic configuration and avoids most end users' misconfigurations. Most average end users may not require specific configuration, and their ISP default configuration MAY fully address their needs. In that case, the naming homenet architecture configuration will be completely transparent to the end users. Then, saving naming configuration outside the CPE, makes it resilient to change of CPE or CPE upgrades. Such configuration may also be configured by the end user, via the customer area of their ISP.

Authors

Daniel Migault (mglt.ietf@gmail.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.)