draft-park-ipv6-extensions-dns-pnp-00.txt

bind 9.3结合mysql数据库

  
  
  
  INTERNET-DRAFT                                       S. Daniel Park
  Expires: October 2003                              Syam Madanapalli
  File:                                           SAMSUNG Electronics
  draft-park-ipv6-extensions-dns-pnp-00.txt                April 2003
  
  
  
  
                 IPv6 Extensions for DNS Plug and Play
  
  
  
  Status of This Memo   
  
  This document is an Internet-Draft and is in full conformance with
  all provisions of Section 10 of RFC2026.

  Internet-Drafts are working documents of the Internet Engineering
  Task Force (IETF), its areas, and its working groups. Note that
  other groups may also distribute working documents as
  Internet-Drafts.

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

  The list of current Internet-Drafts can be accessed at
  http://www.ietf.org/ietf/1id-abstracts.txt

  The list of Internet-Draft Shadow Directories can be accessed at
  http://www.ietf.org/shadow.html.
  
  
  
  Abstract  
  
  This document proposes automatic configuration of domain name (FQDN)
  for IPv6 nodes using Domain Name Auto-Configuration (called 6DNAC) as
  a part of IPv6 plug and play feature. 6DNAC allows the automatic
  registration of domain name and corresponding IPv6 Addresses with
  the DNS server. In order to provide 6DNAC function, Neighbor Discovery
  Protocol [2461] will be used. Moreover, 6DNAC does not require any
  changes to the existing DNS system.
  
  
  Table of Contents 
  
  1.       Introduction .............................................  3
  2.       Terminology ..............................................  3
  3.       6DNAC Design Principles ..................................  4
  4.       6DNAC Overview ...........................................  4
  5.       6DNAC Requirements .......................................  5
  5.1.     6DANR Client Requirements ................................  5
  5.2.     6DNAC Server Requirements ................................  6
    
Park & Madanapalli             Expires October 2003             [Page 1]

INTERNET-DRAFT     IPv6 Extensions for DNS Plug and Play      April 2003    
    
  6.       6DNAC Messages and Option Formats ........................  6
  6.1.     Router Advertisement (RA) Message Format .................  6
  6.2.     Neighbor Solicitation (NS) Message Format ................  7
  6.3.     Neighbor Advertisement (NA) Message Format ...............  8
  6.4.     Option Formats ...........................................  8
  6.4.1.   DNS Zone Suffix Information Option Format ................  8
  6.4.2.   Domain Name (FQDN) Option Format .........................  9
  6.4.3.   Router Alert Option for 6DNAC ............................ 10
  7.       6DNAC Operation .......................................... 10
  7.1.     6DNAC Network Topology ................................... 11
  7.2.     6DNAC Operational Scenarios .............................. 12
  7.2.1.   Domain Name Registration-Success Case .................... 12
  7.2.2.   Domain Name Registration-with DupAddrDetectTransmits=2.... 14
  7.2.3.   Domain Name Registration-Defend Case ..................... 16
  7.2.4.   Domain Name Registration in Retry Mode ................... 19
  7.2.5.   Domain Name Registration when DAD Fails .................. 20
  7.3.     DNS Zone Suffix Discovery and FQDN Construction .......... 22
  7.3.1.   Sending Router Advertisement Messages .................... 22
  7.3.2.   Processing Router Advertisement Messages ................. 22
  7.3.3.   FQDN Lifetime expiry ..................................... 23
  7.3.4.   Host Naming Algorithm .................................... 23
  7.4.     Duplicate Domain Name Detection .......................... 23
  7.4.1.   DAD with All Nodes Multicast Address ..................... 24
  7.4.1.1. Sending Neighbor Solicitation Messages ................... 24
  7.4.1.2. Processing Neighbor Solicitation Messages ................ 24
  7.4.1.3. Sending Neighbor Advertisement Messages .................. 25
  7.4.1.4. Processing Neighbor Advertisement Messages ............... 25
  7.4.1.5. Pros and Cons ............................................ 25
  7.4.2.   DAD with Router Alert Option for 6DNAC ................... 25
  7.4.2.1. Sending Neighbor Solicitation Messages ................... 25
  7.4.2.2. Processing Neighbor Solicitation Messages ................ 26
  7.4.2.3. Sending Neighbor Advertisement Messages .................. 26
  7.4.2.4. Processing Neighbor Advertisement Messages ............... 26
  7.4.2.5. Pros and Cons ............................................ 26
  7.4.3.   Explicit Detection of Duplicate Domain Name .............. 26
  7.4.3.1. Sending Neighbor Solicitation Messages ................... 26
  7.4.3.2. Processing Neighbor Solicitation Messages ................ 26
  7.4.3.3. Sending Neighbor Advertisement Messages .................. 27
  7.4.3.4. Processing Neighbor Advertisement Messages ............... 27
  7.4.3.5. Pros and Cons ............................................ 27
  7.4.4.   Retry Mode for Re-registering Domain Name ................ 27
  7.5.     Domain Name Registration ................................. 27
  8.       Security Consideration ................................... 27
  9.       IANA Consideration ....................................... 28
  10.      Acknowledgement .......................................... 28
  11.      Intellectual Property .................................... 28
  12.      Copyright ................................................ 28
  13.      References ............................................... 29
  14.      Author's Addresses ....................................... 30








Park & Madanapalli             Expires October 2003             [Page 2]

INTERNET-DRAFT     IPv6 Extensions for DNS Plug and Play      April 2003  
  
  1. Introduction 
  
  Today, most networks use DNS[1034][1035] for convenience. In case of
  IPv6, DNS is more important element because of IPv6 long addresses
  which are difficult to remember. In addition, small networks like home
  networks using IPv6, should be able to make network easily without
  manual configuration. Also, these small networks may not have DHCP
  Server, DNS Server etc. that are used to configure the network. This
  document discusses IPv6 Domain Name Auto-Configuration(6DNAC) procedure
  for generating and registering the Domain Name and IPv6 addresses with
  the DNS Server automatically. In order to use 6DNAC, IPv6 nodes are
  required to implement lightweight functions specified in this document.
  6DNAC can be applied to all defined IPv6 unicast addresses except Link
  local IPv6 addresses, viz: Site-local and Global addresses.
  
  6DNAC uses Neighbor Discovery Protocol [2461] with new additions
  (defined in section 6) and DAD procedures for generating and 
  registering the Domain Name with the DNS server automatically.
  
  
  2. Terminology

  6DNAC         - IPv6 Domain Name Auto Configuration. It can provide
                  IPv6 hosts with Domain Name Generation and 
                  Registration automatically.
  
  6DNAC Client  - An IPv6 node that can generate its own unique Domain
                  Name. Section 3 identifies the new requirements that
                  6DNAC places on an IPv6 node to be a 6DNAC node.
                  
  6DNAC Server  - An IPv6 node that can collect and registrate Domain
                  Name and IPv6 addresses automatically. 6DNAC server
                  uses the information from the DAD operation messages
                  with newly defined options for the registration of the 
                  Domain Name and IPv6 Addresses. Section 3 identifies
                  the new requirements that 6DNAC places on an IPv6 
                  node to be a 6DNAC server. Also 6DNAC server can have 
                  various other functions depending on network 
                  environment and the network operator. For instance 
                  6DNAC Server can acts as a Gateway as well Home Server
                  in Home Networks.
 
  DAD           - Duplicate Address Detection (is defined [2461]) 
  
  DFQDND        - Duplicate Domain Name Detection

  FQDN          - Fully Qualified Domain Name - FQDN and Domain Name are 
                  used interchangeably in this document.
  
  NA            - Neighbor Advertisement message (is defined [2461]) 
  
  NS            - Neighbor Solicitation message (is defined [2461])

  RA            - Router Advertisement message (is defined [2461]) 

  SLAAC         - Stateless Address Autoconfiguration [2462].

Park & Madanapalli             Expires October 2003             [Page 3]

INTERNET-DRAFT     IPv6 Extensions for DNS Plug and Play      April 2003  
  
  3. 6DNAC Design Principles
  
  This section discusses the design principles of 6DNAC mechanism.
  
  1. The new procedures for plug and play DNS should not cause changes
     to existing DNS system. 6DNAC requires lightweight functions to be 
     implemented only at the client side of the DNS system, and uses the 
     existing DDNS UPDATE [2136] to communicate with DNS Servers.
  
  2. Introducing a new protocol will always introduce new problems. 
     6DNAC uses the existing protocols NDP [2461] with minor extensions 
     for generating and registering the domain name automatically 
     without defining a new protocol
  
  3. Reusing proven and well understood design principles/patterns 
     will always yield a robust system. 6DNAC is based on IPv6 Address 
     Auotoconfiguration principle, where routers advertise the prefix
     and host adds the interface ID to the prefix and forms the IPv6 
     address. Domain Name (FQDN) also contains two parts: host name 
     and DNS zone suffix. Routers can advertise the DNS zone suffix 
     on a particular link in Router Advertisements (RA Messages) and 
     hosts can prefix their preferred host name to the DNS zone suffix
     and form the fully qualified domain name. Also the detection of
     duplicate domain name is similar to Duplicate Address Detection
     (DAD) and can be part of DAD operation itself.
  
  
  4. 6DNAC Overview
  
  6DNAC proposes minor extensions to NDP [2461] for automatic generation
  and registration of domain name with the DNS server. It introduces two
  new options: DNS Zone Suffix and Fully Qualified Domain Name. DNS Zone
  Suffix option is carried in Router Advertisement (RA) messages for
  notifying IPv6 nodes about the valid DNS Zone Suffix on the link and
  FQDN option in Neighbor Solicitation (NS) and Neighbor Advertisement
  (NA) messages to detect duplicate domain name. 6DNAC consists of two
  components: 6DNAC Client and 6DNAC Server. 6DNAC Clients generate the
  domain name based on DNS Zone Suffix using Host Naming Algorithm (see
  section 7.3.1) and 6DNAC Server collects and registers the DNS
  information with the DNS Server on behalf of 6DNAC Clients.

  The automatic configuration of domain name using 6DNAC consists of
  three parts.

     - DNS Zone Suffix Discovery and FQDN Construction:

       IPv6 Nodes collect DNS Zone Suffix information from Router
       Advertisements and constructs FQDN by prefixing host name to the
       DNS Zone Suffix. The IPv6 Nodes are required to implement Host 
       Naming Algorithm for generating host part of the FQDN in the 
       absence of administrator.

  Generation of node's FQDN within the node itself has advantages. Nodes
  can provide forward and reverse name lookups independent of the DNS
  System by sending queries directly to IPv6 nodes [NIQ]. Moreover Domain
  Name is some thing that is owned by the node.

Park & Madanapalli             Expires October 2003             [Page 4]

INTERNET-DRAFT     IPv6 Extensions for DNS Plug and Play      April 2003
  
     - Duplicate Domain Name Detection

       All nodes are expected to go for DAD for all new IPv6 unicast
       addresses, regardless of whether they are obtained through 
       stateful, stateless or manual configuration. 6DNAC uses the DAD 
       messages with new option for carrying the Domain Name along with 
       the new IPv6 Address. 6DNAC Server captures this information and
       updates DNS Server provided that the IPv6 Address and its domain
       name are not duplicate. If the domain name is already in use, 
       the 6DNAC server replies to the sender with FQDN Option in NA 
       message indicating that the domain name is duplicate. Then the
       node is expected to generate another domain name using host 
       naming algorithm and go for DAD. This time the DAD is only for
       duplicate domain name detection (DFQDND). In order to avoid
       confusion with the normal NDP processing, the target address 
       field of the NS message must carry the unspecified address 
       in retry mode.  This can be repeated depending on number of
       retries defined by the administrator in the host naming algorithm.

  
     - Domain Name Registration

       6DNAC Server detects the DNS information (IPv6 Address and 
       corresponding FQDN) from DAD/DFQDND messages and updates DNS 
       Server using existing protocol DDNS UPDATE [2136] provided that
       the IPv6 Address and its domain name are not duplicate.
  
  If an IPv6 Address is duplicate, the IPv6 node cannot perform
  stateless address autoconfiguration repeatedly. Unlike IPv6 stateless 
  address autoconfiguration, 6DNAC allows the automatic configuration of
  domain name repeatedly if the domain name is duplicate depending on 
  number of retries defined by the administrator in the host naming 
  algorithm.
  
  
  5. 6DNAC Requirements 
  
  Depending on the 6DNAC functionality, the IPv6 nodes implement, they
  are called either 6DNAC Clients or 6DNAC Servers. The following 
  sections lists the requirements that the 6DNAC Client and 6DNAC server
  must support.
   
   
  5.1. 6DANC Client Requirements
  
        - 6DNAC Client must recognize and process the following NDP 
          extensions

              - DNS Zone Suffix option in RA messages for generating its
                domain name (FQDN).

              - Domain Name option in NS and NA messages for detecting 
                the duplicate domain name
 
 
 

Park & Madanapalli             Expires October 2003             [Page 5]

INTERNET-DRAFT     IPv6 Extensions for DNS Plug and Play      April 2003 
  
        - It must generate its domain name (FQDN) based on the DNS 
          suffix that it got from the router advertisement. And it must 
          have a host naming algorithm for generating the host part of
          the FQDN.

        - If NA message is received with unspecified target address and
          FQDN option, then the node must treat that the domain is 
          duplicate.
  
  
  5.2. 6DNAC Server Requirements