DHCPv6 Options for Homenet Naming Architecture
This is an older version of an Internet-Draft whose latest revision state is "Active".
Expired & archived
|Authors||Daniel Migault , Tomek Mrugalski , Chris Griffiths , Ralf Weber , Wouter Cloetens|
|Last updated||2016-04-21 (Latest revision 2015-10-19)|
|RFC stream||Internet Engineering Task Force (IETF)|
DNSDIR Telechat review (of -21) by R. Gieben Ready w/nits
ARTART Last Call review (of -21) by Bron Gondwana Ready w/nits
GENART Last Call review (of -21) by Ines Robles Ready w/nits
|Additional resources||Mailing list discussion|
|Stream||WG state||WG Document|
|Send notices to||(None)|
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Customer Premises Equipment (CPE) devices are usually constrained devices with reduced network and CPU capabilities. As such, a CPE exposing the authoritative naming service for its home network on the Internet may become vulnerable to resource exhaustion attacks. One way to avoid exposing CPE is to outsource the authoritative service to a third party, e.g. ISP. Such an outsource requires setting up an architecture which may be inappropriate for most end users. This document defines DHCPv6 options so any agnostic CPE can automatically proceed to the appropriate configuration and outsource the authoritative naming service for the home network. In most cases, the outsourcing mechanism is transparent for the end user.
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)