📄 draft-park-ipv6-extensions-dns-pnp-00.txt
字号:
Park & Madanapalli Expires October 2003 [Page 16]INTERNET-DRAFT IPv6 Extensions for DNS Plug and Play April 2003 +---------+ +---------+ +---------+ +---------+ | 6DNAC-A | | 6DNAC-S | | 6DNAC-B | | DNS-S | +----+----+ +----+----+ +----+----+ +----+----+ | | | | | RA with | RA with | | | DNS Suffix Opt | DNS Suffix Opt | | |<---------------|--------------->| | | #1 | #1 | | |---+ | |---+ | Construct | #2 | Construct | #2 | FQDN | | FQDN | | |<--+ | |<--+ | DAD/DFQDND Starts | DAD/DFQDND Starts | | | <DELAYED> | | | | | | NS with | | | | FQDN Opt | | | |--------------->| | | | #3 | | | | No Entry | | | |------+ | | | Create FQDN | #4 | | | <FQDN,A> | | | | |<-----+ | | | | | | | | Register FQDN #5 | | |-------------------------------->| | | | | | | NS with | | | | FQDN Opt | | | |<---------------| | | | #6 | | | |------+ | | | FQDN is in use| | | | Defend DFQDND| #7 | | | |<-----+ | | | | | | | | NA with | | | | D-flag Set | | | |--------------->| | | | #8 | | |------+ | |---+ | No Response | #9 | Enter | #10 | DFQDND Success| | Retry Mode| | |<-----+ | |<--+ | | | | | v v v v <Figure: 10 Multiple Hosts Requesting Same Domain Name>Park & Madanapalli Expires October 2003 [Page 17]INTERNET-DRAFT IPv6 Extensions for DNS Plug and Play April 2003 #1. 6DNAC Server (Router) sends out router advertisement with DNS Suffix information. #2. 6DNAC Clients A&B process the router advertisement and construct their FQDN by prefixing hostname to the DNS Zone Suffix. They also construct IPv6 address from the autoconfiguration prefix information option. When each host is trying to go for DAD, all hosts must have random delay to avoid the traffic congestion according to [2461]. So here it is assumed that 6DNAC Client-A starts DAD first and 6DNAC Client-B starts DAD later. #3. 6DNAC Client-A starts duplicate address & FQDN detection for the IPv6 address & FQDN constructed and sends out a Neighbor Solicitation message with FQDN option. #4. 6DNAC Server processes the Neighbor Solicitation message sent by 6DNAC Client-A as part of duplicate FQDN detection procedure and creates a FQDN entry in its FQDN Cache (assuming that there is no entry <FQDN,A>), where A is Link Layer Address of the 6DNAC Client-A. #5. 6DNAC Server then registers FQDN and corresponding IPv6 address through the existing protocol DDNS UPDATE. #6. 6DNAC Client-B starts duplicate address & FQDN detection for the IPv6 address & FQDN constructed and sends out a Neighbor Solicitation message with FQDN option. #7. 6DNAC Server processes the Neighbor Solicitation message sent by 6DNAC Client-B as part of duplicate FQDN detection procedure and finds that the domain name is already in use by the 6DNAC Client-A. Hence, concludes to defend the duplicate FQDN detection of 6DNAC Client-B. #8. 6DNAC Server sends out Neighbor Advertisement message with FQDN option to 6DNAC Client-B to defend its duplicate FQDN detection. #9. 6DNAC Client-A 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. #10. 6DNAC Client-B observes that there is a NA with FQDN option indicating that the domain name is duplicate and enters Retry Mode. In retry mode, 6DNAC Client constructs another FQDN based on Host Naming Algorithm. The number of retries is defined by the administrator and must be a configurable value. Park & Madanapalli Expires October 2003 [Page 18]INTERNET-DRAFT IPv6 Extensions for DNS Plug and Play April 2003 7.2.4. Domain Name Registration in Retry Mode Pre-Conditions: 1. Duplicate Address Detection has succeeded 2. Duplicate FQDN Detection FAILED 3. FQDN is the first FQDN one constructed and FAILED 4. FQDN2 is the second FQDN to be constructed 5. The Neighbor Solicitation in the 'Retry Mode' carries unspecified address in its target field (NS*). +---------+ +---------+ +---------+ | 6DNAC-C | | 6DNAC-S | | DNS-S | +----+----+ +----+----+ +----+----+ | | | |--------+ | | Construct | #1 | | new FQDN2 | | | |<-------+ | | | | | DFQDND Restarts | | | | | | | | | NS* With | | | FQDN Opt | | |--------------->| | | #2 | | | | | | No Entry | | |------+ | | Create FQDN | #3 | | <FQDN2,C> | | | |<-----+ | | | | | | Register FQDN2 | | |--------------->| | | #4 | | | | |--------+ | | No Response | #5 | | DFQDND-Success | | | |<-------+ | | | | | v V v <Figure: 11 Regeneration of Domain Name> Park & Madanapalli Expires October 2003 [Page 19]INTERNET-DRAFT IPv6 Extensions for DNS Plug and Play April 2003 #1. 6DNAC Client constructs the FQDN again as per Host Naming Algorithm, the DNS Zone Suffix, and it is FQDN2. #2. It then starts Duplicate Detection only for Domain Name. 6DNAC Client sends out NS with FQDN option and unspecified target address. #3. 6DNAC Server processes the Retry Mode NS message and finds that the FQDN2 is not in use and creates Cache entry as <FQDN2, C>. #4. It then starts registration procedures with the DNS Server. #5. Meanwhile, 6DNAC Client timesout and observes that there is no defending NA for its DFQDND NS sent out and successfully configures its domain name. 7.2.5. Domain Name Registration when DAD Fails Duplicate domain name detection and subsequent registration starts if and only if the DAD for IPv6 address succeeds. If the DAD for IPv6 address fails then no actions are taken for domain name. When DAD fails for stateless address autoconfiguration, then the domain configuration starts only when the address has been configured using Stateful Address Configuration methods and the node is going on DAD for this address. 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.Park & Madanapalli Expires October 2003 [Page 20]INTERNET-DRAFT IPv6 Extensions for DNS Plug and Play April 2003 +---------+ +---------+ +---------+ +---------+ | 6DNAC-A | | 6DNAC-S | | 6DNAC-B | | DNS-S | +----+----+ +----+----+ +----+----+ +----+----+ | | | | | | | | | RA with | | | | DNS Suffix Opt | | | |<---------------| | | | #1 | | | |-----+ | | | Construct | | | | FQDN& | #2 | | | IPv6 Addr | | | | |<----+ | | | DAD/DFQDND Starts | | | | | | | | | | | | NS with | | | | FQDN Opt | | | |--------------->+--------------->| | | #3 | #3 | | | No Entry | | | |------+ | | | Create FQDN | | | | <FQDN,A> | #4 | | | |<-----+ | | | | | | | | |------+ | | | My IPv6 Addr| #5 | | | |<-----+ | | | Defend DAD | | | | with NA | | |<---------------+<---------------| | | #6 | #6 | | | Entry | | | |------+ | | | Delete FQDN | #7 | | | |<-----+ | | | | | | |----+ | | | DAD Failed | #8 | | | Stop DFQDND | | | | |<---+ | | | | | | | v v v v <Figure: 12 DAD failure> #1. 6DNAC Server sends out Router Advertisement to 6DNAC Client-A. #2. 6DNAC Client-A constructs IPv6 Address based on the prefix and FQDN as per Host Naming Algorithm. #3. It then starts Duplicate address & FQDN Detection, for the newly constructed IPv6 address and FQDN, and sends out DAD/DFQDND NS with FQDN option.
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -