1 / 7

DHCPv6 Dynamic Reconfigure draft-wing-dhc-dns-reconfigure-02

DHCPv6 Dynamic Reconfigure draft-wing-dhc-dns-reconfigure-02. P.Patil , M.Boucadair , T.Reddy , D.Wing IETF-88 Presenter: Shwetha Bhandari. Updates from 01-02. Option from Relay in Relay- Forw to indicate if client is single/dual stacked

keanu
Download Presentation

DHCPv6 Dynamic Reconfigure draft-wing-dhc-dns-reconfigure-02

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. DHCPv6 Dynamic Reconfiguredraft-wing-dhc-dns-reconfigure-02 P.Patil, M.Boucadair, T.Reddy, D.Wing IETF-88 Presenter: ShwethaBhandari DHCPv6 Dynamic Reconfigure

  2. Updates from 01-02 • Option from Relay in Relay-Forw to indicate if client is single/dual stacked • Generic message from Relay to indicate host mode transitions to the server • IPv4 to Dual-Stack • IPv6 to Dual-Stack • Dual-Stack to IPv4 • Dual-Stack to IPv6 • DHCPv6 Server acts accordingly on the generic message DHCPv6 Dynamic Reconfigure

  3. Problem • Hosts connected to a network may be IPv4-only, IPv6-only or dual-stack • Returning generic configuration to all such hosts may not be optimal and in some cases may raise complications • Typical examples with problems are • Provide a DNS server to an IPv6-only host, while DNS64 is required • Provision a DNS64 server to a dual-stack host DHCPv6 Dynamic Reconfigure

  4. Focus on a Use Case • Avoid unnecessary NAT64 by influencing the host's DNS server selection to use: • DNS64 when IPv6-only • Normal DNS when dual-stack • Static configuration is sub-optimal in heterogeneous environments and during host mode transitions DHCPv6 Dynamic Reconfigure

  5. Relay-Forward NAS (DHCP Relay) DHCP Server DHCP Client IPv4 Stack Initializes DHCP Request Relay Forward Relay Reply DHCP Response Transition to Dual-Stack DHCP Request Relay Forward w/ Dual-Stack indication Relay Reply DHCP Response DHCPv6 Dynamic Reconfigure

  6. Reconfigure-Request NAS (DHCP Relay) DHCP Server DHCP Client Relay detects transition Dual Stack host Transitions to IPv4/6 only Reconfigure Request w/ Dual-Stack transition indication Reconfigure-Reply Relay Reply (Reconfigure) Reconfigure DHCPv6 Dynamic Reconfigure

  7. Next Steps • This is a missing piece of work • Request adoption by the WG DHCPv6 Dynamic Reconfigure

More Related