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

bind 9.3结合mysql数据库

            +-+-+       +-+-+
            | H2|       | H3|
            +---+       +---+
  
  
  H1, H2, H3 - 6DNAC Clients
  H4         - 6DNAC Server
  R1         - Router
  
  
                  <Figure: 6 Example of 6DNAC Topology>
  
  
  Figure 7 shows the 6DNAC Server implemented on a router R1. In this
  case a single 6DNAC server can serve multiple links for automatic
  configuration of the domain name. This topology also has flexibility
  of using DAD packets with Router Alert option instead of sending DAD
  packets to all nodes multicast address. The routers are required to
  process all the packets with Router Alert option as per [2711].

  In case of Home Networks, R1 is will acts as a Home Gateway (CPE)
  connected to ISP. R1 delegates the prefix from the ISP edge router.
  After delegating the prefix the CPE can advertise the DNS Zone suffix
  along with the prefix information to the nodes on the links to which
  the router is connected to. Note that the R1 must be configured with
  the DNS Zone suffix Information manually. 




Park & Madanapalli             Expires October 2003            [Page 11]

INTERNET-DRAFT     IPv6 Extensions for DNS Plug and Play      April 2003
  
                         +---+       +---+ 
                         | H3+       | H4|
                         +-+-+       +-+-+
                           |           |
                           |   LINK2   |
      +---+             ---+--------+--+--          +----------+
      | H1|                         |               |DNS Server|
      +-+-+                         |               +----+-----+
        |                        +--+-+           -------/
        |         LINK 1         |    |          /
     ---+-----+------------------+ R1 +---------+
              |                  |    |      DDNS UPDATE
              |                  +----+
            +-+-+             6DNAC Server
            | H2|
            +---+
  
  
  H1, H2 - 6DNAC Clients on Link1
  H3, H4 - 6DNAC Clients on Link2
  R1     - Router with 6DNAC Server, serving both Link1 and Link2
  
  
       <Figure: 7 Example of 6DNAC Server serving multiple links>
  
  
  7.2. 6DNAC Operational Scenarios
  
  This section provides message sequence charts for various 6DNAC
  operational scenarios assuming that the 6DNAC Server is implemented
  on a router. All the scenarios assume that the normal boot up time
  stateless address autoconfiguration of Link Local address derived
  from the Interface Identifier has been completed successfully. And
  it is also assumed that the router is already configured with the
  DNS Zone Suffix Information.

  
  Legend:
  
  6DNAC-A, B, C  : 6DNAC Clients
  6DNAC-S        : 6DNAC Server/Router
  DAD            : Duplicate Address Detection
  DFQDND         : Duplicate Domain Name Detection
  DNS-S          : DNS Server
  
  
  7.2.1. Domain Name Registration-Successful Case 

  This scenario starts when a 6DNAC Client receives RA message with
  DNS Zone Suffix and other parameters including address prefix as
  specified in NDP [2461] and wants configure its IPv6 address (Global
  or Site Local) and domain name. It is Assumed that the 
  DupAddrDetectTransmits is set to 1.




Park & Madanapalli             Expires October 2003            [Page 12]

INTERNET-DRAFT     IPv6 Extensions for DNS Plug and Play      April 2003
  
   +---------+      +---------+      +---------+
   | 6DNAC-C |      | 6DNAC-S |      |  DNS-S  |
   +----+----+      +----+----+      +----+----+
        |                |                |
        |     RA with    |                |
        | DNS Suffix Opt |                |
        |<---------------|                |
        |       #1       |                |
        |---+            |                |
  Construct |#2          |                |
    FQDN    |            |                |
        |<--+            |                |
DAD/DFQDND Starts        |                |
        |                |                |
        |                |                |
        |    NS With     |                |
        |    FQDN Opt    |                |
        |--------------->|                |
        |       #3       |                |
        |                |                |
        |                |------+         |
        |          Create FQDN  | #4      |
        |            <FQDN,C>   |         |
        |                |<-----+         |
        |                |                |
        |                |  Register FQDN |
        |                |--------------->|
        |                |       #5       |
        |   #6           |                |
        |--------+       |                |
   No Response   |       |                |
  DFQDND-Success |       |                |
        |<-------+       |                |
        |                |                |
        |                |                |
        v                V                v  


          <Figure: 8 Domain Name Generation and Registration>
           
  
  #1. 6DNAC Server (Router) sends out router advertisement with DNS
      Suffix information along with other parameters as specified in
      NDP [2461].
  
  #2. 6DNAC Client processes the router advertisement and constructs
      the FQDN by prefixing hostname to the DNS Zone Suffix. It also
      constructs IPv6 address from the autoconfiguration prefix
      information option.

  #3. 6DNAC Client starts duplicate address & FQDN detection for the
      IPv6 address & FQDN constructed and sends out a Neighbor
      Solicitation message with FQDN option. 

      Note that the DAD packets must be addressed to all nodes multicast
      address if Router Alert option is not used. 
      
Park & Madanapalli             Expires October 2003            [Page 13]

INTERNET-DRAFT     IPv6 Extensions for DNS Plug and Play      April 2003          

  #4. 6DNAC Server processes the Neighbor Solicitation message sent by
      6DNAC Client as part of duplicate FQDN detection procedure and
      creates a FQDN entry in its FQDN Cache (assuming that there is no
      entry <FQDN,C>), where C is Link Layer Address of the 6DNAC Client.

  #5.  6DNAC Server then registers FQDN and corresponding IPv6 address
       through the existing protocol DDNS UPDATE.

  #6.  6DNAC Client times out and observes that there is no response to
       defend its duplicate FQDN detection procedure and the node is
       successful in configuring its domain name.
  
  Note that, Stateless Address Autoconfiguration DAD procedure is not
  depicted in the following message sequence chart, which simultaneously
  happens along with duplicate FQDN detection.
  

  7.2.2. Domain Name Registration-with DupAddrDetectTransmits=2 

  This scenario starts when a 6DNAC Client receives RA message with
  DNS Zone Suffix and other parameters including address prefix as
  specified in NDP [2461] and wants configure its IPv6 address (Global
  or Site Local) and domain name. The node is configured with 
  DupAddrDetectTransmits = 2 for reliability in delivering DAD messages.

































Park & Madanapalli             Expires October 2003            [Page 14]

INTERNET-DRAFT     IPv6 Extensions for DNS Plug and Play      April 2003 

   +---------+      +---------+      +---------+
   | 6DNAC-C |      | 6DNAC-S |      |  DNS-S  |
   +----+----+      +----+----+      +----+----+
        |                |                |
        |     RA with    |                |
        | DNS Suffix Opt |                |
        |<---------------|                |
        |       #1       |                |
        |---+            |                |
  Construct |#2          |                |
    FQDN    |            |                |
        |<--+            |                |
DAD/DFQDND Starts        |                |
        |                |                |
        |                |                |
        |    NS With     |                |
        |    FQDN Opt    |                |
        |--------------->|                |
        |       #3       |                |
        |                |                |
        |                |------+         |
        |          Create FQDN  | #4      |
        |            <FQDN,C>   |         |
        |                |<-----+         |
        |                |                |
        |                |  Register FQDN |
        |                |--------------->|
        |                |       #5       |
        |    NS With     |                |
        |    FQDN Opt    |                |
        |--------------->|                |
        |      #6        |                |
        |                |                |
        |          Lookup FQDN            |
        |          Entry exists           |
        |                |------+         |
        |             Ignore    | #7      |
        |                |<-----+         |
        |   #8           |                |
        |--------+       |                |
   No Response   |       |                |
  DFQDND-Success |       |                |
        |<-------+       |                |
        |                |                |
        |                |                |
        v                V                v  

  
  
            <Figure: 9 Verification of duplicated Domain Name>


  Steps from #1 to #5 are same as that of scenario.7.2.1.
  
  #6. 6DNAC Client sends out second Neighbor Solicitation message with
      FQDN option as part of duplicate FQDN detection.
      
Park & Madanapalli             Expires October 2003            [Page 15]

INTERNET-DRAFT     IPv6 Extensions for DNS Plug and Play      April 2003      

  #7. 6DNAC Server receives and observes that the FQDN Cache exactly
      matches with that of the NS information and ignores the NS message.

  #8. 6DNAC Client times out and observes that there is no response to
      defend its duplicate FQDN detection procedure and the node is
      successful in configuring its domain name..

  
  7.2.3. Domain Name Registration-Defend Case 

  This scenario starts when two 6DNAC Client receive RA message with
  DNS Zone Suffix and other parameters including address prefix as
  specified in NDP [2461] and both the nodes want configure their IPv6
  address (Global or Site Local) and domain name. In this scenario both
  the nodes want to have same domain name.