DHCP Options for Homenet Naming Architecture
draft-ietf-homenet-naming-architecture-dhc-options-00

The information below is for an old version of the document
Document Type Active Internet-Draft (homenet WG)
Last updated 2014-09-19
Replaces draft-mglt-homenet-naming-architecture-dhc-options
Stream IETF
Intended RFC status (None)
Formats plain text pdf html bibtex
Stream WG state WG Document
Document shepherd No shepherd assigned
IESG IESG state I-D Exists
Consensus Boilerplate Unknown
Telechat date
Responsible AD (None)
Send notices to (None)
HOMENET                                                  D. Migault (Ed)
Internet-Draft                                                    Orange
Intended status: Standards Track                             W. Cloetens
Expires: March 22, 2015                                       SoftAtHome
                                                            C. Griffiths
                                                                     Dyn
                                                                R. Weber
                                                                 Nominum
                                                      September 18, 2014

              DHCP Options for Homenet Naming Architecture
       draft-ietf-homenet-naming-architecture-dhc-options-00.txt

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.

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/.

   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."

Migault (Ed), et al.     Expires March 22, 2015                 [Page 1]
Internet-DraftDHCP Options for Homenet Naming ArchitectureSeptember 2014

   This Internet-Draft will expire on March 22, 2015.

Copyright Notice

   Copyright (c) 2014 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 . . . . . . . . . . . . . . . . . . . .   3
   2.  Terminology . . . . . . . . . . . . . . . . . . . . . . . . .   3
   3.  Introduction  . . . . . . . . . . . . . . . . . . . . . . . .   4
   4.  Protocol Overview . . . . . . . . . . . . . . . . . . . . . .   6
   5.  Securing the exchanges  . . . . . . . . . . . . . . . . . . .   8
   6.  DNS Zones Update Mechanisms . . . . . . . . . . . . . . . . .   9
     6.1.  Data subjected to update  . . . . . . . . . . . . . . . .   9
     6.2.  Master / Slave Synchronization versus DNS Update  . . . .   9
     6.3.  Setting Master / Slave Synchronization  . . . . . . . . .  10
     6.4.  Master / Slave Synchronization: CPE / Public
           Authoritative Name Server Set . . . . . . . . . . . . . .  10
     6.5.  Master / Slave Synchronization: CPE / Reverse Public
           Authoritative Name Server Set . . . . . . . . . . . . . .  11
   7.  DNS Zone Update Data  . . . . . . . . . . . . . . . . . . . .  11
     7.1.  DNS Homenet Zone Template . . . . . . . . . . . . . . . .  11
     7.2.  DNS Homenet Zone  . . . . . . . . . . . . . . . . . . . .  12
   8.  Payload Description . . . . . . . . . . . . . . . . . . . . .  12
     8.1.  Security Field  . . . . . . . . . . . . . . . . . . . . .  12
     8.2.  Update Field  . . . . . . . . . . . . . . . . . . . . . .  13
     8.3.  DHCP Public Key Option  . . . . . . . . . . . . . . . . .  14
     8.4.  DHCP Zone Template Option . . . . . . . . . . . . . . . .  14
     8.5.  DHCP Public Authoritative Name Server Set Option  . . . .  15
     8.6.  DHCP Reverse Public Authoritative Name Server Set Option   16
Show full document text