1 / 20

IPv6 and IPv4 Interoperation and Transition

IPv6 and IPv4 Interoperation and Transition. Tony Hain co-chair IETF ngtrans WG alh-ietf@tndh.net. Agenda. Transition issues ngtrans tool set Environments Summary. Transition issues. Islands vs. Integrated Automated vs. Managed Applications Long process. 2001. 2005. 2002. 2003.

lark
Télécharger la présentation

IPv6 and IPv4 Interoperation and Transition

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. IPv6 and IPv4 Interoperation and Transition Tony Hain co-chair IETF ngtrans WG alh-ietf@tndh.net

  2. Agenda • Transition issues • ngtrans tool set • Environments • Summary

  3. Transition issues • Islands vs. Integrated • Automated vs. Managed • Applications • Long process

  4. 2001 2005 2002 2003 2004 2000 2006 2007 Q1 Q1 Q1 Q1 Q1 Q1 Q1 Q1 Q2 Q2 Q2 Q2 Q2 Q2 Q2 Q2 Q3 Q3 Q3 Q3 Q3 Q3 Q3 Q3 Q4 Q4 Q4 Q4 Q4 Q4 Q4 Q4 • Early adopter IPv6 Timeline(A pragmatic projection) • Application porting <= Duration 3+ years => • ISP adoption <= Duration 3+ years => • Consumer adoption <= Duration 5+ years => • Enterprise adoption <= Duration3+ years =>

  5. Tools – Dual Stack IPv6 Enabled • Primary tool • Allows continued 'normal' operation with IPv4-only nodes • Address selection rules generally prefer IPv6 • DSTM variant allows temporary use of IPv4 pool IPv4-Only IPv6 Enabled

  6. Tools – Tunneling IPv6 Enabled • Nodes view IPv4 network as a logical NBMA link-layer • May be used in conjunction with dual-stack IPv4-Only IPv6 Enabled

  7. Tunneling Mechanisms (operationally challenging) • Configured • Prearranged addresses for both IPv4 & IPv6, manually configured • Tunnel Broker • Builds on configured tunnel via IPv4 auth scheme to establish mapping ; typically default route • 6over4 • Any address, but requires IPv4 multicast for ND • Automatic • Host-to-host – IPv4 address embedded in low 32 bits with prefix ::/96 • Requires injecting IPv4 BGP table into IPv6 routing

  8. System Administered Locally Administered SLA  (16bits) UDP port (16bits) Locally Administered SLA  (16bits) FP  (16bits) FP  (16bits) ISATAP EUI64-OUI Interface ID (64bits) Interface ID (64bits) IPv4 ID (32bits) 00100010 00100010 MAC derived or Locally Administered or Random Provider administered 0000:5EFE MAC derived or Locally Administered or Random 6to4 IPv4 (32bits) Any (48bits) IPv4 (32bits) Provider Administered Provider Administered Provider Administered ISATAP Teredo Tunneling Mechanisms (Unicast Address Formats)

  9. Tools – Translation IPv6 Enabled • Allows for the case where some components are IPv6-only while others are IPv4-only • Tool of last resort • Pay attention to scaling properties • Same application issues as IPv4/IPv4 translation IPv4-Only

  10. Stateful Translation Mechanisms • NAT-PT • Address & protocol translation • TRT • Transport layer relay • Socks • Application layer gateway • IGMP / MLD proxy • Joins opposing groups & maps addresses

  11. Stateless Translation Mechanisms • SIIT • Address & protocol translation • BIS • Augmentation between IPv4 stack & device driver • BIA • Supports IPv4 apps over IPv6 stack

  12. Tools – BGP tunnel • Service provider can incrementally upgrade PE routers with active customers • Sites are connected to Dual Stack MP-BGP-speaking edge router • Transport across the IPv4 core can be any tunneling mechanism

  13. Tools – Services • DNS • DNS-ALG in NAT-PT distorts perception • Referral chain consistency with resolver • Remember glue & reverse records for IPv6 • SMTP • Create MX records for both IPv4 & IPv6 on dual-stack • DNS failure on AAAA may cause mail requeue • DHCP • Spec about finished; products will follow • Prefix allocation current driver

  14. Environments Service Provider Enterprise Unmanaged

  15. Environments – Unmanaged • No administrative staff to manage configuration or policies • Devices need to be plug-n-play appliances • Tool automation a primary concern

  16. Environments – Managed Enterprise • Dedicated management staff & tools • Network & hosts share administrative policies • Applications will likely require recertification

  17. Environments – Managed Service Provider • Network has different administrative policies than connected hosts or networks • Interaction with Peer networks may require translation • Services as Dual-stack • Distributed tunnel relay services to minimize overhead Tunnel Relay NAT-PT AAA DNS SMTP

  18. Summary • Transition will not be a quick process • Tool set goal : minimize interdependence • Dual-stack & Tunneling before Translation • Recognize environment characteristics • Applications will drive deployments

  19. Questions?

More Related