IPv6 Home Network Front End Naming Delegation
draft-mglt-homenet-front-end-naming-delegation-01

The information below is for an old version of the document
Document Type Expired Internet-Draft (individual)
Last updated 2013-05-10 (latest revision 2012-11-06)
Replaced by draft-ietf-homenet-front-end-naming-delegation
Stream (None)
Intended RFC status (None)
Formats
Expired & archived
pdf htmlized 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-homenet-front-end-naming-delegation-01.txt

Abstract

CPEs are designed to provide IP connectivity to the Home Network. Most of the CPEs are also providing the IP addresses of the nodes of the Home Network. This makes CPEs good candidates for hosting the Naming Service that would make devices reachable from the Home Network but also from the Internet. CPEs have not been designed to host a Naming Service reachable from the Internet. This would expose the CPEs and the Home Network to resource exhaustion which would result in making the Home Network unreachable, and most probably would also affect the Home Network inner communications. This document describes an Front End Naming Architecture where the CPEs manage the DNS(SEC) zone for its Home Network, and outsource the zone to Public Server for resolution coming from the Internet. The goal of the document is first to describe a Naming Architecture that fulfills Home Network Naming requirements without exposing the CPE to resource exhaustion. Then we intend the CPEs to be easily configured by the End Users, and describe the necessary information the End User is expect to provide to the CPE.

Authors

Daniel Migault (mglt.ietf@gmail.com)
Wouter Cloetens (wouter.cloetens@softathome.com)
Philippe Lemordant (philippe.lemordant@orange.com)
Chris Griffiths (chris_griffiths@cable.comcast.com)

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