DHCPv6 Options for Homenet Naming Architecture
draft-ietf-homenet-naming-architecture-dhc-options-04

Document Type Expired Internet-Draft (homenet WG)
Last updated 2017-02-16 (latest revision 2016-08-15)
Replaces draft-mglt-homenet-naming-architecture-dhc-options
Stream IETF
Intended RFC status (None)
Formats
Expired & archived
plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state Expired
Consensus Boilerplate Unknown
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-ietf-homenet-naming-architecture-dhc-options-04.txt

Abstract

Home network devices are usually constrained devices with reduced network and CPU capabilities. As such, a home network device exposing the authoritative naming service for its home network on the Internet may become vulnerable to resource exhaustion attacks. One way to avoid exposing these devices is to outsource the authoritative service to a third party, e.g. ISP. The Homenet Naming Authority (HNA) is the designated device in charge of outsourcing the service to a third party, which requires setting up an architecture. Such settings may be inappropriate for most end users. This document defines DHCPv6 options so any agnostic HNA 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.

Authors

Daniel Migault (daniel.migault@ericsson.com)
Tomek Mrugalski (tomasz.mrugalski@gmail.com)
Chris Griffiths (cgriffiths@gmail.com)
Ralf Weber (ralf.weber@nominum.com)
Wouter Cloetens (wouter.cloetens@softathome.com)

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