DHCP Options for Homenet Naming Architecture
draft-mglt-homenet-naming-architecture-dhc-options-02
Document | Type |
Replaced Internet-Draft
(homenet WG)
Expired & archived
|
|
---|---|---|---|
Authors | Daniel Migault , Wouter Cloetens , Chris Griffiths , Ralf Weber | ||
Last updated | 2014-09-03 (Latest revision 2014-07-02) | ||
Replaced by | draft-ietf-homenet-naming-architecture-dhc-options | ||
RFC stream | Internet Engineering Task Force (IETF) | ||
Intended RFC status | (None) | ||
Formats | |||
Additional resources | Mailing list discussion | ||
Stream | WG state | Adopted by a WG | |
Document shepherd | (None) | ||
IESG | IESG state | Replaced by draft-ietf-homenet-naming-architecture-dhc-options | |
Consensus boilerplate | Unknown | ||
Telechat date | (None) | ||
Responsible AD | (None) | ||
Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
CPEs are usually constraint devices with reduced network and CPU capacities. As such, a CPE hosting on the Internet the authoritative naming service for its home network may become vulnerable to resource exhaustion attacks. One way to avoid exposing CPE is to outsource the authoritative service to a third party. This third party can be the ISP or any other independent third party. Outsourcing the authoritative naming service to a third party requires setting up an architecture which may be unappropriated for most end users. To leverage this issue, this document proposes DHCP Options so any agnostic CPE can automatically proceed to the appropriated configuration and outsource the authoritative naming service for the home network. This document shows that in most cases, these DHCP Options make outsourcing to a third party (be it the ISP or any ISP independent service provider) transparent for the end user.
Authors
Daniel Migault
Wouter Cloetens
Chris Griffiths
Ralf Weber
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)