IP Version 6 (IPv6) Advantages and Transitions

1. IP Version 6 (IPv6)Advantages and Transitions Pat R. Calhoun Carl Williams Sun Microsystems

2. Introduction • This contribution is intended to provide 3GPP2 members with an introduction to IP version 6. • This contribution will discuss the advantages of IPv6, as well as the different transition tools available.

3. Why is IPv6 needed?

4. IPv4 problems • 1. Running out of Internet addresses ... • Stops Internet growth for existing users • Prevents use of the Internet for new users • Internet Routing today is inefficient for Internet Service Providers (ISPs) • Forces users to use NAT • Loss of the end-to-end principle for networking

5. IPv4 problems • 2. System Management • Labour intensive, complex, slow & error prone • Subscriber Networks cannot be dynamically renumbered or configured • 3. Security • 4. Bandwidth Reservation / Resource Metering • Need to schedule bandwidth for select time • Pay or Charge only for what is used

6. The “Transparency” Principle has been lost ... • Internet “Transparency” concept • Transparent transmission of datagrams • Addresses are unique • Datagrams are not touched in transit • End-Systems handle naming, error detection, error recovery, security • Applications are designed with this principle in mind

7. The “Transparency” Principle has been lost ... • In today’s world we are loosing Transparency • Private addresses • Network Address Translators (NATs) • Intranet growth • Firewalls • Applications sometime fail completely or have to be designed without this basic principle

8. Will IPv4 last forever? • How long can we ignore these problems? • IPv4 address space will run out • There is an engineering limit to the amount of retrofitting that can be applied to IPv4 • Need to regain some “Transparency” • A natural evolution from IPv4 is required • Designed with extensibility and scalability in mind

9. IPv6 Benefits - Short Term • Increased Address Space • Efficient addressing and routing topology • NAT is not Required • Architecture • Optimized for 64 bit architecture • Efficient and Extensible IP datagram • Improved Host and Router Discovery • Multicast • Enhancements for Quality of Service (QOS) and for Mobile Networking • Plug and Play • Dynamic Address Autoconfiguration (Stateless, Stateful) • Dynamic Renumbering of Networks • Security

10. IPv6 benefits - Long Term • Dynamic Rehoming of Applications • Mobility • Quality of Service for end-to-end networking. • Extensible to support new features for applications • Voice over IP (VoIP), Video, Network Management, Mobility, Network Appliances • Other functions still evolving from the extensibility of the architecture.

11. IPv4 versus IPv6 Key Features 665,570,793,348,866,943,898,599 IPv6 Addresses /m2 of the Earth Surface IPv4 IPv6

12. IPv6 Status - Implementations • Host Implementations • Sun, Compaq, HP, IBM, Mentat, Microsoft, Linux, BSDI, INRIA, FreeBSD, NetBSD, SGI, WIDE etc • Router Implementations • 3com, Cisco, Bay Networks, Hitachi, Nokia, Sumitomo Electric, Telebit, Merit etc • Recent Product Announcements (MSFT, CISCO) • Some shipping in products today • Sun Solaris 8 • IBM AIX 4.3 • Telebit http://playground.sun.com/pub/ipng/html/ipng-main.html

13. IPv6 TODAY: 6Bone http://6bone.net/ • A Public Test bed for IPv6 and it’s related protocols • To Assist in the Evolution and Deployment of IPv6 • IPv6 Sites are connected to each other • over IPv4 (IPv6 tunnelled in IPv4) • over native IPv6 links • 28+ Implementations on the 6Bone • Hosts • Sun Solaris 8, COMPAQ’s TRU64 UNIX and OpenVMS, Hitachi NR60, IBM AIX, Inria BSD, Linux, SICS HP-UX, UNH for BSD, NRL for BSD, WIDE Hydrangea for BSD, WIDE ZETA for BSD, WIDE v6d, Microsoft Research • Routers • Bay, Cisco, Fujitsu LR550, Hitachi NR60, Inria BSD, Linux, Merit MRT, NRL for BSD, Telebit, WIDE Hydrangea for BSD, WIDE ZETA for BSD, WIDE v6d

14. IPv6 TODAYGrowing World-wide • 469 Registered IPv6 Sites on the 6Bone - October 1999 • US and Canada 123 ((107)) (95) • Europe 252 ((187)) (160) • Asia Pacific 75 ((51)) (43) • Latin America 16 ((4)) (1) • Africa 3 ((3)) (0) • Countries 42 ((41)) (35) ((352)) (299) (( )) Values in March 1999 ( ) Values in August 1998

15. IPv6 TODAY: 6REN • The 6REN is a voluntary coordination initiative of Research and Education Networks that provide production IPv6 transit service • To facilitate high quality, high performance, and operationally robust IPv6 networks. • Participation is free and open to all Research and Education Networks that provide IPv6 service. • Other for-profit and not-for-profit IPv6 networks are also encouraged to participate. • Join the 6REN Initiative • See the new web site for the 6REN http://www.6ren.net/

16. IPv6 FORUM • A world-wide consortium of leading Internet vendors and Research and Education Networks • The IPv6 FORUM mission • To promote IPv6 in order to create a higher quality and more secure Next Generation Internet. • The FORUM works closely with the Internet Engineering Task Force (IETF) which is responsible for the IPv6 technical specifications • 66 ‘Founding Members’ http://www.ipv6forum.com/

17. IPv6 Standardization Internet Draft Where in the standardization process is IPv6? Proposed Standard (RFC) Yes Technically complete and stable? Draft Standard (RFC) Yes Multiple Interoperable Implemen- tations Internet Standard (RFC) Significant Operational Experience? Yes Platform - 6bone 6ren, vBNS etc. 3GPP2?

18. IPv6 - IPv4 Interoperation

19. Facts of Life IPv4 and IPv6 • Facts: • Millions of nodes are running IPv4 today • Some nodes will never upgrade to IPv6 • Large investment in IPv4 applications • Consequences: • IPv4 and IPv6 will coexist for an extended period. • For ever? • Great care has been taken to ensure that hosts and routers can be upgraded to IPv6 independently. • Transition must prevent isolation of IPv4 nodes.

20. Facts of Life for a Successful Deployment • No disruption • IPv6 and IPv4 Router + Hosts can interoperate • Incremental upgrade / Deployment • IPv6 routers and hosts can be deployed in an Intranet in a highly diffused and incremental fashion • Low start-up costs • Transition should be as easy as possible for end-users, system administrators, and network operators • No Flag Days.

21. Mechanisms for transition • Many tools and proposals available • IETF Ngtrans Working Group working on Roadmap documents • Basic Transition tools • Dual Stack • Tunnels • Translations • packet header translations and ALG’s • Others

22. IPv4 IPv6 Basic transition tools:Dual Stacks and Tunnels • Defines: • Two Mechanisms • Dual IP layer - providing complete support for both IPv4 and IPv6 in hosts and routers. • Tunnels to encapsulate IPv6 packets within IPv4 headers and to carry them over IPv4 routing infrastructures. • An IPv6 addressing structure that embeds IPv4 addresses within IPv6 addresses RFC 1933 Transition Mechanisms for IPv6 Hosts and Routers

23. IPv4 Address Mapping • IPv4-Mapped IPv6 Address • a node that is not IPv6-capable • Reachable using the IPv4 Routing Infrastructure 0000:0000:0000:0000:0000:0000:FFFF:<IPv4 Address> ::FFFF:10.21.32.43

24. TCP IPv4 IPv6 TCP TCP IPv4 IPv6 Dual-IP Stacks • IPv4 address acquired • via IPv4 mechanisms • IPv6 address acquired • via stateless or stateful configuration IPv4 IPv6

25. TCP IPv4 IPv6 Applications: IPv6-IPv4 Interoperability • IPv6 enabled applications and the TCP/UDP transport protocols run on both IP versions IPv6 enabled app

26. IPv6 in IPv4 Tunnelling • Mechanism of encapsulating IPv6 packets within IPv4 • So that they can be carried across IPv4 routing infrastructures • Tunnelling process: • Encapsulation • Decapsulation • Tunnel configuration information

27. IPv6 Encapsulated Packet inside IPv4 Header IPv4 Protocol ID 41 (decimal) IPv6 in IPv4 Tunnel IPv6 Packet IPv4 Header IPv6 Packet

28. Automatic Tunnel (1) Source Host A Destination Host B IPv6/v4 IPv6 only Router R1 Router R2 IPv4 B IPv6 B IPv6 B IPv6/v4 IPv4only Data Data IPv4 Network IPv4 B IPv4 IPv6 IPv6 B Data

29. Automatic Tunnel (2) Source Host A Destination Host B IPv6/v4 IPv6/v4 Router R1 Router R2 IPv4 only IPv4 only IPv4 Network IPv4 B IPv6 B Data

30. Configured Tunnel Source Host A Destination Host B IPv6 only IPv6 only Router R1 Router R2 IPv6 B IPv6 B IPv6/v4 IPv4/v6 Data Data IPv4 Network IPv4 R2 IPv6 B Data

31. Methods of communication between IPv4 and IPv6 nodes • SIIT (Stateless IP/ICMP Translator) • This proposal is stateless, and does packet-by-packet translation, which eliminates the single point of failure • NAT-PT (Network Address Translation – Protocol Translation) • This proposal requires a stateful NAT server • SOCKS64 (Socks-based IPv6/IPv4 Gateway mechanism) • This proposal requires socks client on the mobile

32. Application - Issues • Many IPv4 applications • assume the IP host address is fixed 32 bits • IPv4 APIs make the IP Address visible to an application • Some Applications make use of IP Addresses for Indexing within the Application

33. Application - Solutions • Make No Code Changes • Can only Access Nodes with IPv4 Addresses • For example using the IPv4 Part of the Hybrid Stack • Only use IPv4 features • Change Code to use IPv6 API • Can Access Hosts with IPv4 and IPv6 Addresses • Can exploit IPv6 features

34. The risk • If 3G is as successful as we believe it will be, what would happen if requests for addresses were denied. • Although there are still addresses left, they are very difficult to obtain. • It doesn’t seem logical to create a standard that may never be deployable.

35. What should we do? • Clearly, IPv6 must be on our radar. • 3GPP2 should create an ad-hoc group to investigate the remaining issues with IPv6 deployment. • The outcome could require standardization work, that could be done within the IETF.

36. Suggestion • One approach we could take is to support an IPv6 core network, and maintain support IPv4 mobiles. • This would reduce the pain of transition in the future. • If our request for IPv4 is denied, we can still deploy IPv6 clients.

37. Why bother? • Renumbering will occur in the future, we might as well get the networks ready for it. • In moving towards IPv6, we would gain a tremendous amount of support from the IETF. • Since these networks do not exist today, they are the ideal candidates for IPv6.

38. ..and what if we don’t? • Some networks, especially the European and Asian networks will have great difficulty in allocating IPv4 addresses. • If we don’t all move towards IPv6, we will have fragmented IPv4 and IPv6 networks, which could complicate inter-domain roaming.

39. Conclusion • IPv6 will occur. • We need to be ready for it, and even be pro-active. • We should setup an ad-hoc group to study IPv6. • This would minimize risk should requests for IPv4 addresses be denied.