datatracker.ietf.org
Sign in
Version 5.3.0, 2014-04-12
Report a bug

IPv6 Home Network Naming Delegation
draft-mglt-homenet-front-end-naming-delegation-03

Document type: Active Internet-Draft (individual)
Document stream: No stream defined
Last updated: 2013-10-20
Intended RFC status: Unknown
Other versions: plain text, pdf, xml, html

Stream State:No stream defined
Document shepherd: No shepherd assigned

IESG State: I-D Exists
Responsible AD: (None)
Send notices to: No addresses provided

HOMENET                                                  D. Migault (Ed)
Internet-Draft                                                    Orange
Intended status: Standards Track                             W. Cloetens
Expires: April 23, 2014                                       SoftAtHome
                                                            C. Griffiths
                                                                     Dyn
                                                                R. Weber
                                                                 Nominum
                                                        October 20, 2013

                  IPv6 Home Network Naming Delegation
         draft-mglt-homenet-front-end-naming-delegation-03.txt

Abstract

   CPEs are designed to provide IP connectivity to home networks.  Most
   CPEs assigns IP addresses to the nodes of the home network which
   makes it a good candidate for hosting the naming service.  With IPv6,
   the naming service makes nodes reachable from the home network as
   well as from the Internet.

   However, CPEs have not been designed to host such a naming service
   exposed on the Internet.  This MAY expose the CPEs to resource
   exhaustion which would make the home network unreachable, and most
   probably would also affect the home network inner communications.

   In addition, DNSSEC management and configuration may not be well
   understood or mastered by regular end users.  Misconfiguration MAY
   also results in naming service disruption, thus these end users MAY
   prefer to rely on third party naming providers.

   This document describes a homenet naming architecture where the CPEs
   manage the DNS zone associates to its home network, and outsource
   both DNSSEC management and naming service on the Internet to a third
   party designated as the Public Authoritative Servers.

Status of This Memo

   This Internet-Draft is submitted in full conformance with the
   provisions of BCP 78 and BCP 79.

   Internet-Drafts are working documents of the Internet Engineering
   Task Force (IETF).  Note that other groups may also distribute
   working documents as Internet-Drafts.  The list of current Internet-
   Drafts is at http://datatracker.ietf.org/drafts/current/.

Migault (Ed), et al.     Expires April 23, 2014                 [Page 1]
Internet-Draft       Home Network Naming Delegation         October 2013

   Internet-Drafts are draft documents valid for a maximum of six months
   and may be updated, replaced, or obsoleted by other documents at any
   time.  It is inappropriate to use Internet-Drafts as reference
   material or to cite them other than as "work in progress."

   This Internet-Draft will expire on April 23, 2014.

Copyright Notice

   Copyright (c) 2013 IETF Trust and the persons identified as the
   document authors.  All rights reserved.

   This document is subject to BCP 78 and the IETF Trust's Legal
   Provisions Relating to IETF Documents
   (http://trustee.ietf.org/license-info) in effect on the date of
   publication of this document.  Please review these documents
   carefully, as they describe your rights and restrictions with respect
   to this document.  Code Components extracted from this document must
   include Simplified BSD License text as described in Section 4.e of
   the Trust Legal Provisions and are provided without warranty as
   described in the Simplified BSD License.

Table of Contents

   1.  Requirements notation . . . . . . . . . . . . . . . . . . . .   2
   2.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Architecture Overview . . . . . . . . . . . . . . . . . . . .   5
   5.  Architecture Description  . . . . . . . . . . . . . . . . . .   7
     5.1.  CPE and Public Authoritative Servers Synchronization  . .   8
       5.1.1.  Synchronization with a Hidden Master  . . . . . . . .   8
       5.1.2.  Securing Synchronization  . . . . . . . . . . . . . .   9
     5.2.  DNS Homenet Zone configuration  . . . . . . . . . . . . .  10
     5.3.  DNSSEC outsourcing configuration  . . . . . . . . . . . .  12
     5.4.  CPE Security Policies . . . . . . . . . . . . . . . . . .  13
   6.  Homenet Naming Configuration  . . . . . . . . . . . . . . . .  13
   7.  Security Considerations . . . . . . . . . . . . . . . . . . .  14
     7.1.  Names are less secure than IP addresses . . . . . . . . .  14
     7.2.  Names are less volatile than IP addresses . . . . . . . .  15
   8.  IANA Considerations . . . . . . . . . . . . . . . . . . . . .  15
   9.  Acknowledgment  . . . . . . . . . . . . . . . . . . . . . . .  15
   10. References  . . . . . . . . . . . . . . . . . . . . . . . . .  16
     10.1.  Normative References . . . . . . . . . . . . . . . . . .  16

[include full document text]