50 likes | 115 Views
This presentation discusses the challenges in networks transitioning to both IPv4 and IPv6, impacting stack quality with various technologies. It addresses issues like telling dual-stack hosts which protocol to use and for which destinations. The presentation emphasizes considerations for a smoother transition and addresses concerns over potential breakages in existing technologies.
E N D
Joint Sunset4/DHCSummary IETF 87 DHC WG Berlin, Germany Thursday, 1 August, 2013
Problem Statement • Many networks will have both IPv4 and IPv6, but with varying transition technologies affecting the quality of those stacks • “real” IPv4 (no NAT) • CGN IPv4 (potentially broken for some apps) • NAT64/DNS64 (also potentially breaks things) • IPv6 (only) • How do you tell dual-stack hosts which to use/avoid? • For which destinations? • With which protocol(s)? • Happy Eyeballs helps, but can be non-deterministic
draft-ietf-dhc-dhcpv4-over-dhcpv6 • Presentation to be repeated later today • Conclusion: • No specific objections or comments
draft-ietf-dhc-v4configuration • Presentation to be repeated later today • Implementation details discussion • Minor clarification on requirements regarding future v4 options
draft-wing-dhc-dns-reconfigure • Presentation to be repeated later today • A bit misleading name, generic mechanism for more than just DNS • Lots of discussion about: • Multiple relays • State management and recovery • What constitutes a valid address? • Concern: not easy to detect deprecated addr