1 / 8

NAT: Two Purposes for Transition

NAT: Two Purposes for Transition. Share IPv4 addresses: NAT44 Connect IPv X hosts to IPv Y hosts : NAT64. 1. Share IPv4 Addresses. Still lots of IPv4 content School websites, day care websites, ... Still lots of IPv4 applications Skype, IP televisions

nessa
Télécharger la présentation

NAT: Two Purposes for 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. NAT: Two Purposes for Transition • Share IPv4 addresses: NAT44 • Connect IPvXhosts to IPvYhosts: NAT64 IETF82 - INTAREA

  2. 1. Share IPv4 Addresses • Still lots of IPv4 content • School websites, day care websites, ... • Still lots of IPv4 applications • Skype, IP televisions • Not enough IPv4 addresses • dual stack consumes IPv4 address at the same rate • NAT is not perfect. NAT at edge to minimize impact. • NAT Purpose 1: share IPv4 addresses among hosts IPv4-only long tail IETF82 - INTAREA

  3. Address Sharing Gone Bad Source: Shin Miyakawa, NTT Communications IETF82 - INTAREA

  4. IPv4 Address Sharing Technologies IPv4 Address Run-Out Obtain IPv4 Addresses (RIR, address broker) IPv4 IPv4 Address Sharing CGN, NAT44, SD-NAT DualStack Lite 6rd+ CGN 4rd/dIVI native 6rd IPv6 IETF82 - INTAREA

  5. 2. Connect IPvX to IPvY • NAT Purpose 2: connect IPv6 to IPv4 IPv4 IPv6 NAT64 IPv4-only hosts IPv6-only hosts IETF82 - INTAREA

  6. Connecting IPvX hosts to IPvYhosts • NAT64 is not perfect • IPv6 and IPv4 are not compatible • Fragmentation (IPv4: network fragments, IPv6: hosts fragment) • minimum MTU (IPv4: 576, IPv6: 1280) • IPv4 options versus IPv6 extensions • Like NAT44: • NAT64 can also bring Application Layer Gateway (ALG) issues • Complicates troubleshooting and abuse handling IETF82 - INTAREA

  7. IPv6 Transition: Tunnel or Translate? translate tunnel native routing best worst IETF82 - INTAREA

  8. Conclusion • IPv4 address sharing (NAT, A+P, other) • Necessary to keep business running • Necessary to keep users happy (long tail IPv4) • But is never ideal • Native IPv6 > tunneling > NAT • Focus on mechanisms that move towards IPv6 • Simple to operate • Stateless IETF82 - INTAREA

More Related