NAT64 marcelo bagnulo, Philip Matthews, Iljitsch van Beijnum IETF 72 - Dublin.

Slides:



Advertisements
Similar presentations
IPv4/IPv6 Coexistence and Transition: Requirements for solutions draft-bagnulo-v6ops-6man-nat64-pb-statement-01 M. Bagnulo, F. Baker v6ops WG - IETF71.
Advertisements

DNS46 for the IPv4/IPv6 Stateless Translator
Applications Test Results in MIF environment draft-zheng-mif-apps-test-02.txt IETF 81 Quebec City.
NAT, firewalls and IPv6 Christian Huitema Architect, Windows Networking Microsoft Corporation.
IPv4 - IPv6 Integration and Coexistence Strategies Warakorn Sae-Tang Network Specialist Professional Service Department A Subsidiary.
Transitioning to IPv6 April 15,2005 Presented By: Richard Moore PBS Enterprise Technology.
December 5, 2007 CS-622 IPv6: The Next Generation 1 IPv6 The Next Generation Saroj Patil Nadine Sundquist Chuck Short CS622-F2007 University of Colorado,
Project by: Palak Baid (pb2358) Gaurav Pandey (gip2103) Guided by: Jong Yul Kim.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 W. Schulte Chapter 5: Network Address Translation for IPv4  Connecting.
Implementing IPv6 Module B 8: Implementing IPv6
IPv6 The Next Generation Presented by Anna La Mura Jens Waldecker.
© 2007 Cisco Systems, Inc. All rights reserved.ICND2 v1.0—7-1 Address Space Management Transitioning to IPv6.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Lecture15: Network Address Translation for IPv4 Connecting Networks.
1 Teredo - Tunneling IPv6 through NATs Date: Speaker: Quincy Wu National Chiao Tung University.
IPv4 & IPv6 Coexistence & Migration Joe Zhao SW2 Great China R&D Center ZyXEL Communications, Inc.
Enabling IPv6 in Corporate Intranet Networks
17/10/031 Summary Peer to peer applications and IPv6 Microsoft Three-Degrees IPv6 transition mechanisms used by Three- Degrees: 6to4 Teredo.
1 DSMIP6 Support QUALCOMM Inc. Jun Wang, George Cherian, Masa Shirota Notice.
1 Internet Protocol Version 6 (IPv6) What the caterpillar calls the end of the world, nature calls a butterfly. - Anonymous.
Module 4: Configuring Network Connectivity
Understanding Internet Protocol
Configuring and Troubleshooting Network Connections
1 Address Selection, Failure Detection and Recovery in MULTI6 draft-arkko-multi6dt-failure-detection-00.txt Multi6 Design Team -- Jari Arkko, Marcelo Bagnulo,
An Overview of IPv6 Transition/Co-existence Technologies Fernando Gont UTN/FRH LACNOG 2010 Sao Paulo, Brazil, October 19-22, 2010.
Module 4: Configuring Network Connectivity
DNS and DHCP in Dual Stack Networks Lawrence E. Hughes Chairman, InfoWeapons Inc.
Transition Mechanisms for Ipv6 Hosts and Routers RFC2893 By Michael Pfeiffer.
Notes for IPv6 Terrance Lee. Transition Mechanisms for IPv6 Hosts and Routers (RFC 2893)
IP/ICMP Translation Algorithm (IIT) Xing Li, Congxiao Bao, Fred Baker
IPv6 Using IPv6 and IPv4 Integration and Co-existence.
資 管 Lee Lesson 11 Coexistence and Migration. 資 管 Lee Lesson Objectives Coexistence and migration overview Coexistence mechanisms ◦ Dual Stack ◦ Tunneling.
Support Protocols and Technologies. Topics Filling in the gaps we need to make for IP forwarding work in practice – Getting IP addresses (DHCP) – Mapping.
Network Address Translation (NAT)
CSE 8343 Group 3 Advanced OS Inter Operability Between IPv4 and IPv6 Team Members Aman Preet Singh Rohit Singh Nipun Aggarwal Chirag Shah Eugene Novak.
Coexistence and Migration
9/11/2015Home Networking1 Bob.test Have Road Runner Unhappy about reports of constant probes of machines Policy decision –I want to prevent unauthorized.
Connecting Networks © 2004 Cisco Systems, Inc. All rights reserved. Exploring How IP Address Protocols Work INTRO v2.0—4-1.
Operating Systems Lesson 10. Networking Communications protocol is the set of standard rules for ◦ Data representation ◦ Signaling ◦ Authentication ◦
IPv6 and IPv4 Coexistence Wednesday, October 07, 2015 IPv6 and IPv4 Coexistence Motorola’s Views for Migration and Co-existence of 3GPP2 Networks to Support.
IPv4/IPv6 Coexistence Scenarios - Requirements for Translation Mechanisms. draft-ietf-v6ops-nat64-pb-statement-req-01 M. Bagnulo, F. Baker, I. van Beijnum.
Sharing a single IPv4 address among many broadband customers
IPv6, the Protocol of the Future, Today Mathew Harris.
Private Network Addresses IP addresses in a private network can be assigned arbitrarily. – Not registered and not guaranteed to be globally unique Generally,
The Implementation of 6TALK Yong-Geun Hong The 1 st GLOBAL IPv6 Summit in AP
Ch 6: IPv6 Deployment Last modified Topics 6.3 Transition Mechanisms 6.4 Dual Stack IPv4/IPv6 Environments 6.5 Tunneling.
Company Confidential 1 ICMPv6 Echo Replies for Teredo Clients draft-denis-icmpv6-generation-for-teredo-00 behave, IETF#75 Stockholm Teemu Savolainen.
How to connect to the Internet 1998/12/09 KEIO University, JAPAN Mikiyo
An Update on Multihoming in IPv6 Report on IETF Activity RIPE IPv6 Working Group 22 Sept 2004 RIPE 49 Geoff Huston, APNIC.
© 2008 Cisco Systems, Inc. All rights reserved.Cisco ConfidentialPresentation_ID 1 Chapter 11: Network Address Translation for IPv4 Routing And Switching.
Guidance of Using Unique Local Addresses draft-liu-v6ops-ula-usage-analysis-05 draft-liu-v6ops-ula-usage-analysis-05 Bing Liu(speaker), Sheng Jiang, Cameron.
IP addresses IPv4 and IPv6. IP addresses (IP=Internet Protocol) Each computer connected to the Internet must have a unique IP address.
IPv4/IPv6 Coexistence Framework Prefixing/Encap/Translation (PET) draft-cui-softwire-pet-01 draft-cui-softwire-pet64-00 Yong Cui, Mingwei Xu, Shengling.
W&L Page 1 CCNA CCNA Training 3.4 Describe the technological requirements for running IPv6 in conjunction with IPv4 Jose Luis Flores /
1 Computer Networks IPv6. 2 Motivation The primary motivation from changing the IP datagram format is to increase the size of the useable address space.
Default Address Selection for IPv6 Richard Draves May 31, 2001 Redmond Interim IPv6 WG Meeting draft-ietf-ipngwg-default-addr-select-04.
Default Address Selection for IPv6 Richard Draves March 19, 2001 Minneapolis IETF Meeting draft-ietf-ipngwg-default-addr-select-03.
DNS64 draft-bagnulo-behave-dns64-01 m. bagnulo, P. Matthews, I. van Beijnum, A. Sullivan, M. Endo IETF 73 - Mineapolis.
IETF 81 th Rapid Transition of IPv4 contents to be IPv6-accessible draft-sunq-v6ops-contents-transition-02 Q. Sun, C. Xie, Q. Liu, X. Li, J. Qin and D.
IPv6 Security Issues Georgios Koutepas, NTUA IPv6 Technology and Advanced Services Oct.19, 2004.
IPv6 Transition Mechanisms - 6DISS Workshop - 5 March 2006 IPv6 Transition Mechanisms, their Security and Management Georgios Koutepas National Technical.
CCNA4-1 Chapter 7-1 IP Addressing Services Scaling Networks With Network Address Translation (NAT)
Configuring NAT. Configuring Static NAT There are two basic tasks to perform when configuring static NAT translations: Create the mapping between the.
HIP-Based NAT Traversal in P2P-Environments
Understand IPv6 Part 2 LESSON 3.3_B Networking Fundamentals.
Chapter 6 Exploring IPv6.
Introducing To Networking
Default Address Selection for IPv6
New Solutions For Scaling The Internet Address Space
CSCI {4,6}900: Ubiquitous Computing
An Update on Multihoming in IPv6 Report on IETF Activity
Presentation transcript:

NAT64 marcelo bagnulo, Philip Matthews, Iljitsch van Beijnum IETF 72 - Dublin

Application scenario IPv6 Only host IPv6 Only host IPv4 Only Host IPv4 Only Host NAT64 -Communications initiated by the v6-only host -Compatible with ICE -No support for communications initiated by the v4 only side without previous action from the v6 side (i.e. No support for v6 only servers, beyond the creation of static mappings) -No changes required in any host for basic functionality -Supports communications initiated using the FQDN (of the v4 node) using DNS64

Overview NAT64 v6 v4 DNS64 DNS H6 IP6 H4 IP4 IPT AAAA RR for FQDN(H4) ?

Overview NAT64 v6 v4 DNS64 DNS H6 IP6 H4 IP4 IPT AAAA RR for FQDN(H4) ?

Overview NAT64 v6 v4 DNS64 DNS H6 IP6 H4 IP4 IPT AAAA RR for FQDN(H4) ? enpty

Overview NAT64 v6 v4 DNS64 DNS H6 IP6 H4 IP4 IPT AAAA RR for FQDN(H4) ? A RR for FQDN(H4) ?

Overview NAT64 v6 v4 DNS64 DNS H6 IP6 H4 IP4 IPT AAAA RR for FQDN(H4) ? A RR for FQDN(H4) ? IP4

Overview NAT64 v6 v4 DNS64 DNS H6 IP6 H4 IP4 IPT Synthetizes AAAA RR as Pref::/96+IPv4

Overview NAT64 v6 v4 DNS64 DNS H6 IP6 H4 IP4 IPT AAAA RR Pref:IP4

Overview NAT64 v6 v4 DNS64 DNS H6 IP6 H4 IP4 IPT Src: IP6,s Dest: Pref:IP4,d Src: IP6,s Dest: Pref:IP4,d

Overview NAT64 v6 v4 DNS64 DNS H6 IP6 H4 IP4 IPT IP6,s T,t

Overview NAT64 v6 v4 DNS64 DNS H6 IP6 H4 IP4 IPT Src: T,t Dest: IP4,d Src: T,t Dest: IP4,d

Comparison with NATPT (RFC2766) NAT64 only supports v6 initiated communications – NATPT supports both v4 and v6 initiated, requiring a set of cumbersome techniques NAT64 and DNS64 are completelly decoupled – No relation between the NAT64 state and the synthetic RR – DNS64 preserves DNS semantics, DNS responses are valid irrespectivly of the path used by data packets NAT64 allows to preffer native connectivity over translated connectivity NAT64 is compatible with DNSSec NAT64 supports some modes of IPSec NAT64 is fully specified, compatible with behave requirements

A couple of design questions

What prefix to use to map v4 addresses in v6 land? Option 1: Local prefix – We use a prefix /96 obtained from the site’s block – Differnet prefixes for different nat64 boxes in the same site Option 2: global prefix – Candidates: V4mapped prefix V4compatible prefix A new global prefix assigned by IANA

Implication 1: global translated addresses If we use a global prefix, we have a globally unique RR that represent translated addresses Less problems with DNS, DNSSec No need to configure the local prefix in DNS64

Implication 2: communication with dual stack Local Prefix: Translated addresses are represented as one of the site’s address – Need other means to distinguish them: EDNS0 option Only upgraded dual stack can use it: apps that break with nats may break NAT64 v6 v4 DNS64 DNS H6 IP6 H4 IP4 IPT AAAA RR Pref:IP4 EDNS0

Implication 2: Communications with dual stack Global prefix: – V4mapped prefix: Automatically less preferred due to rfc3484 policy Windows vista, Macos, Linux, don’t use it on the wire – V4 compatible prefix Automatcially less preferred compared to native v6, but more preferred than v4 (represented as v4 mapped) Windows vista, macos, linux send packets to this prefix – Other global prefix from IANA More rpeferred than v4 Longest prefix match rule in rfc3484 could help (if not deprecated)

Implication 3: routing fluctuations Failure in intra site routing fluctuations NAT64_1 v6 v4 DNS64 DNS H6 IP6 H4 IP4 NAT64_2

Implication 3: routing fluctuations Failure in intra site routing fluctuations NAT64_1 v6 v4 DNS64 DNS H6 IP6 H4 IP4 NAT64_2

Implication 3: routing fluctuations Failure in intra site routing fluctuations NAT64_1 v6 v4 DNS64 DNS H6 IP6 H4 IP4 NAT64_2

Endpoint independence vs. Higher utilization of v4 addresses Endpoint independence requires mappings are: (srcIP6,srcp) (T,t) Address and port dependent mapping are: (srcIP6,srcp,dstIP6,dstp) (T,t,dstIP4,dstp’) Can we afford endpoint independence in v6?